BSC6900 UMTS Performance Counter Reference (V900R017C10 - 02) (PDF) - en

BSC6900 UMTS
V900R017C10
Performance Counter Reference

Issue
03
Date
2015-06-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. 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 03 (2015-06-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
BSC6900 UMTS
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
Solution Version
BSC6900
V900R017C10
RAN17.1
Intended Audience
This document is intended for:
l
Network planners
System engineers
Field engineers
Shift operators
Site maintainers
Network operators
Change History
For detailed performance counter changes, see the release notes.
Document Structure
Figure 1 shows the document structure.
Issue 03 (2015-06-30)

ii
BSC6900 UMTS
About This Document
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
Obj
ect
Ty
pe
Issue 03 (2015-06-30)
Description
Overvi
ew
Definition and function of a object type.

iii
BSC6900 UMTS
Item
Description
Functio
n
SubSet
s
Function subsets contained in a object type.
Fun
ctio
n
Set
Functio
nSet
Name
Name of the function set.
Fun
ctio
n
Sub
set
Overvi
ew
Definition of a function subset and the flowchart for measuring related

counters.
Counte
rs
Counters contained in a function subset.
Counte
r
Relatio
nship
A table that lists parent counters and their child counters in a table. Note that
the child counters listed in the table cover only typical scenarios. That is,
some scenarios are not covered by any counter. Therefore, the value of a
parent counter is larger than or equal to the sum of the values of its child
counters. Some counters may not be involved in any counter relationship.
Counte
r ID
A string of digits that uniquely

identifies a counter.
Counte
r Name
Name of a counter. It is composed of

a string of uppercase letters,
lowercase letters, and dots.
Counte
r
Descri
ption
A phrase that provides a simple

description about a counter.
Descri
ption
Detailed description about a counter.
Measur
ement
Point
Condition for triggering counter measurement.
Formul
a
Relationship among counters.
Unit
Unit of a counter.
Related
Feature
s
Features related to a counter. The "-" in Related Features stands for not
involved, such as intermediate counters.
Co
unt
er
Issue 03 (2015-06-30)
About This Document
One function set contains one or more function subsets.
Related intermediate counters are

described in Counter ID, Counter
Name and Counter Description.
Intermediate counter is invisible on
the U2000 GUI. Invisible counters
are internal sampling points used for
calculating the visible counters
inside the U2000.

iv
BSC6900 UMTS
Contents
Contents
About This Document.....................................................................................................................ii
1 UMTS Radio Network Related Measurement.........................................................................1
1.1 Measurement of CNOperator Performance(CNOPERATOR).......................................................................................2
1.1.1 Algorithm Measurement per PLMN(ALGO.PLMN.RNC)........................................................................................2
1.1.2 RAB Setup Measurement per PLMN(RAB.Estab.PLMN.RNC)................................................................................3
1.1.3 RAB Release Measurement per PLMN(RAB.Rel.PLMN.RNC)................................................................................9
1.1.4 Traffic Measurement per PLMN(TRAFF.LOAD.PLMN.RNC)...............................................................................16
1.2 Measurement of CPUS Subsystem Performance(CPUS).............................................................................................45
1.2.1 CPUS Subsystem Measurement(CPUS)...................................................................................................................45
1.3 Measurement of GTP-U Performance(GTPU).............................................................................................................97
1.3.1 GTP-U Measurement(GTPU)....................................................................................................................................97
1.4 Measurement of Iu Interface Performance(IU)..........................................................................................................109
1.4.1 CS Signaling Measurement per Iu Interface(CS.SIG.IU).......................................................................................110
1.4.2 CS Traffic Measurement per Iu Interface(CS.TRF.IU)...........................................................................................136
1.4.3 MBMS Measurement per Iu Interface(MBMS.IU).................................................................................................140
1.4.4 MOCN Measurement per Iu Interface(MOCN.IU).................................................................................................145
1.4.5 NAS Signaling Measurement per Iu Interface(NAS.IU).........................................................................................153
1.4.6 PS Signaling Measurement per Iu Interface(PS.SIG.IU)........................................................................................171
1.4.7 PS Traffic Measurement per Iu Interface(PS.TRF.IU)............................................................................................219
1.4.8 SCCP Measurement per Iu Interface(SIG.SCCP.IU)..............................................................................................237
1.5 Measurement of Iur Interface Performance(IUR)......................................................................................................244
1.5.1 DRNC Measurement per Iur Interface(DRNC.IUR)...............................................................................................244
1.5.2 Reserved Counter Measurement per Iur Interface(RESERVE.IUR)......................................................................290
1.5.3 SCCP Measurement per Iur Interface(SIG.SCCP.IUR)..........................................................................................292
1.5.4 SRNC Measurement per Iur Interface(SRNC.IUR)................................................................................................298
1.5.5 Traffic Measurement per Iur Interface(TRFFIC.IUR)............................................................................................378
1.6 Measurement of MPU Subsystem Performance(MPU).............................................................................................395
1.6.1 MPU Subsystem Measurement(MPU)....................................................................................................................396
1.7 Measurement of NodeB Performance(NODEB)........................................................................................................398
1.7.1 Algorithm Measurement per NodeB(ALGO.NODEB)...........................................................................................398
1.8 Measurement of Load Sharing Node Performance(NODESHARE)..........................................................................420
1.8.1 RAB Measurement per Load Sharing Node(RAB.NODESHARE)........................................................................420
Issue 03 (2015-06-30)

BSC6900 UMTS
Contents
1.8.2 RRC Measurement per Load Sharing Node(RRC.NODESHARE)........................................................................441

1.8.3 Traffic Measurement per Load Sharing Node(TRAFFIC.NODESHARE).............................................................456
1.9 Measurement of NodeB-Level CNOperator Performance(PLMN_NodeB)..............................................................481
1.9.1 NodeB-Level CNOperator Measurement(PLMN.NodeB)......................................................................................481
1.10 Measurement of RNC Performance(RNC)...............................................................................................................486
1.10.1 Algorithm Measurement per RNC(ALGO.RNC).................................................................................................487
1.10.2 AMR Service Measurement <per RNC>(AMR.RNC)..........................................................................................496
1.10.3 CBS Measurement <per RNC>(CBS.RNC)..........................................................................................................502
1.10.4 RIM Message Through eCoordinator Measurement per RNC <per RNC>(ECO.RIM.RNC).............................509
1.10.5 Hard Handover Measurement <per RNC>(HHO.RNC).......................................................................................534
1.10.6 CS Inter-RAT Handover Measurement <per RNC>(IRATHO.Cs.RNC).............................................................542
1.10.7 PS Inter-RAT Handover Measurement <per RNC>(IRATHO.PS.RNC).............................................................558
1.10.8 LCS Service Measurement <per RNC>(LCS.RNC).............................................................................................570
1.10.9 Paging Measurement <per RNC>(PAGE.RNC)...................................................................................................588
1.10.10 PDCP Measurement(PDCPGTPU.RNC)............................................................................................................633
1.10.11 CS RAB Setup Measurement <per RNC>(RAB.EstabCS.RNC)........................................................................637
1.10.12 PS RAB Setup Measurement <per RNC>(RAB.EstabPS.RNC)........................................................................645
1.10.13 CS RAB Modification Measurement <per RNC>(RAB.ModCs.RNC)..............................................................674
1.10.14 PS RAB Modification Measurement <per RNC>(RAB.ModPs.RNC)...............................................................679
1.10.15 Multi-RAB Service Measurement <per RNC>(RAB.MultiRab.RNC)...............................................................685
1.10.16 RAB Release Measurement <per RNC>(RAB.RelAbnormal.RNC)..................................................................687
1.10.17 CS RAB Release Measurement <per RNC>(RAB.RelCs.RNC)........................................................................707
1.10.18 PS RAB Release Measurement <per RNC>(RAB.RelPs.RNC).........................................................................710
1.10.19 RB Procedure Measurement <per RNC>(RB.RNC)...........................................................................................713
1.10.20 TRNC Relocation Measurement(Relocation.Drnc.RNC)...................................................................................740
1.10.21 SRNC Relocation Measurement(Relocation.Srnc.RNC)....................................................................................763
1.10.22 RLC Measurement <per RNC>(RLC.RNC).......................................................................................................802
1.10.23 IMS Measurement <per RNC>(RNC.IMS).........................................................................................................808
1.10.24 RRC Connection Release Measurement <per RNC>(RRC.Rel.RNC)...............................................................813
1.10.25 RRC Connection Setup Measurement <per RNC>(RRC.Setup.RNC)...............................................................823
1.10.26 RRC Status Measurement <per RNC>(RRC.STATE)........................................................................................832
1.10.27 Soft Handover Measurement <per RNC>(SHO.RNC).......................................................................................836
1.10.28 Security Mode Measurement <per RNC>(SM.RNC).........................................................................................847
1.10.29 Traffic Measurement <per RNC>(TRAFF.LOAD.RNC)...................................................................................857
1.11 Measurement of ROAMCNOperator Performance(ROAM_CNOPERATOR).......................................................879
1.11.1 Roaming UE Registration Measurement Under MOCN(MOCN.ROAM.CNOPERATOR)................................879
1.12 Measurement of Cell Performance(UCELL)............................................................................................................881
1.12.1 Algorithm Measurement <per Cell>(ALGO.Cell)................................................................................................884
1.12.2 Algorithm Measurement 2 <per Cell>(ALGO2.Cell).........................................................................................1029
1.12.3 BLER Measurement <per Cell>(BLER.Cell).....................................................................................................1142
1.12.4 BOOST Measurement <per Cell>(BOOST.CELL)............................................................................................1166
Issue 03 (2015-06-30)

vi
BSC6900 UMTS
Contents
1.12.5 CBS Measurement <per Cell>(CBS.Cell)...........................................................................................................1194

1.12.6 Common Channel Measurement <per Cell>(CCH.Cell)....................................................................................1197
1.12.7 Cell Update Measurement <per Cell>(CELLUPDATE.Cell).............................................................................1201
1.12.8 Measurement of Channel Reconfiguration to DCH <per Cell>(Channel.Upswitch.Cell)..................................1263
1.12.9 Compressed Mode Measurement <per Cell>(CM.Cell)......................................................................................1317
1.12.10 CS Service Quality Measurement <per Cell>(CSService.Cell)........................................................................1330
1.12.11 EFACH Measurement <per Cell>(EFACH.Cell)..............................................................................................1465
1.12.12 EPCH Measurement <per Cell>(EPCH.Cell)...................................................................................................1496
1.12.13 ERACH Measurement <per Cell>(ERACH.Cell).............................................................................................1498
1.12.14 Voice Quality EVQI Measurement <per Cell>(EVQI.CELL)..........................................................................1517
1.12.15 Hard Handover Measurement <per Cell>(HHO.Cell)......................................................................................1545
1.12.16 HSDPA Measurement <per Cell>(HSDPA.Cell)..............................................................................................1675
1.12.17 HSUPA Measurement <per Cell>(HSUPA.Cell)..............................................................................................1784
1.12.18 Inter-RAT Handover Measurement <per Cell>(INTRAT.HO.Cell).................................................................1940
1.12.19 Iu Singaling Connection Release Measurement<per Cell>(IU.Sig.Rel.Cell)...................................................2110
1.12.20 Iub Interface Measurement <per Cell>(IUB.Cell)............................................................................................2127
1.12.21 LCS Service Measurement <per Cell>(LCS.CELL).........................................................................................2162
1.12.22 MBMS Measurement <per Cell>(MBMS.Cell)................................................................................................2166
1.12.23 RRC MR Measurement <per Cell>(MEAR.Report.Cell).................................................................................2187
1.12.24 Paging Measurement <per Cell>(PAGE.CELL)...............................................................................................2268
1.12.25 Parking Measurement<per Cell>(Parking.Cell)................................................................................................2296
1.12.26 CNOperator Measurement <per Cell>(PLMN.CELL)......................................................................................2319
1.12.27 PS service quality Measurement <per Cell>(PSService.Cell)...........................................................................2335
1.12.28 PTT Measurement <per Cell>(PTT.Cell)..........................................................................................................2421
1.12.29 QoS Measurement <per Cell>(QOS.Cell).........................................................................................................2469
1.12.30 CS RAB Setup Measurement <per Cell>(RAB.EstabCS.Cell).........................................................................2537
1.12.31 PS RAB Setup Measurement <per Cell>(RAB.EstabPS.Cell)..........................................................................2587
1.12.32 CS RAB Setup Failure Measurement <per Cell>(RAB.EstFailCs.Cell)...........................................................2620
1.12.33 PS RAB Setup Failure Measurement <per Cell>(RAB.EstFailPs.Cell)...........................................................2655
1.12.34 CS RAB Modification Measurement <per Cell>(RAB.ModCs.Cell)...............................................................2689
1.12.35 PS RAB Modification Measurement <per Cell>(RAB.ModPs.Cell)................................................................2696
1.12.36 Multi-RAB Service Measurement <per Cell>(RAB.MultiRab.Cell)................................................................2704
1.12.37 RAB Release Measurement <per Cell>(RAB.RelAbnormal.Cell)...................................................................2763
1.12.38 RB Procedure Measurement <per Cell>(RB.Cell)............................................................................................2908
1.12.39 Reserved Counter Measurement <per Cell>(RESERVE.Cell).........................................................................3010
1.12.40 RLC Measurement <per Cell>(RLC.Cell)........................................................................................................3019
1.12.41 RRC Connection Release Measurement <per Cell>(RRC.Rel.Cell)................................................................3031
1.12.42 RRC Connection Setup Measurement <per Cell>(RRC.Setup.Cell)................................................................3044
1.12.43 RRC Connection Reject Measurement <per Cell>(RRC.SetupFail.Cell).........................................................3158
1.12.44 RRC Status Measurement <per Cell>(RRC.State.Cell)....................................................................................3199
1.12.45 UE Capability Measurement <per Cell>(RRC.UECapab.Cell)........................................................................3203
Issue 03 (2015-06-30)

vii
BSC6900 UMTS
Contents
1.12.46 TX and RX Power Measurement <per Cell>(RTWPTCP.Cell)........................................................................3214

1.12.47 Soft Handover Measurement <per Cell>(SHO.Cell)........................................................................................3255
1.12.48 Target SIR Measurement <per Cell>(SIR.Cell)................................................................................................3285
1.12.49 SPI Measurement <per Cell>(SPI.Cell)............................................................................................................3291
1.12.50 Traffic Volume and Data Rate Measurement <per Cell>(THRUPUT.Cell).....................................................3343
1.12.51 Traffic Measurement <per Cell>(TRFFIC.Cell)...............................................................................................3409
1.12.52 UL Interoperability Measurement <per Cell>(U2LTE.HO.Cell)......................................................................3435
1.12.53 URA Update Measurement <per Cell>(URAUPDATE.Cell)...........................................................................3487
1.12.54 Video Service Quality Measurement <per Cell>(VIDEO.CELL)....................................................................3492
1.12.55 WLAN Measurement <per Cell>(WLAN.Cell)................................................................................................3515
1.13 Measurement of UMTS Cell-to-GSM Cell Handover Performance(UCELL_GCELL)........................................3519
1.13.1 UMTS Cell-to-GSM Cell Handover Measurement(IRATHO.Gcell).................................................................3519
1.14 Measurement of UMTS Cell-to-LTE Cell Handover Performance(UCELL_LCELL).........................................3537
1.14.1 UMTS Cell-to-LTE Cell Handover Measurement(IRATHO.Lcell)...................................................................3537
1.15 Measurement of UMTS Cell-to-UMTS Cell Handover Performance(UCELL_NCELL).....................................3553
1.15.1 UMTS Cell-to-UMTS Cell Handover Measurement(CELL.Ncell)....................................................................3553
1.16 Measurement of UMTS DSP Performance(UDSP)...............................................................................................3602
1.16.1 DSP Measurement(DSP).....................................................................................................................................3602
1.17 Measurement of UMTS NIU DSP Performance(UNIUDSP)................................................................................3606
1.17.1 UMTS NIU DSP Performance Measurement(UNIUDSP).................................................................................3606
2 Transport Network Related Measurement.........................................................................3626

2.1 Measurement of AAL2Path Performance(AAL2PATH).........................................................................................3637
2.1.1 AAL2 Path Measurement(AAL2PATH)...............................................................................................................3637
2.2 Measurement of AAL2Path ATM Layer Performance(AAL2PATH_PVCLAYER)..............................................3641
2.2.1 AAL2Path ATM Layer Measurement(AAL2PATH.PVCLAYER).....................................................................3642
2.3 Measurement of AAL2Path VCL PM Performance(AAL2PATH_VCLPM).........................................................3647
2.3.1 AAL2Path VCL PM Measurement(AAL2PATH.VCLPM).................................................................................3648
2.4 Measurement of IP Transport Adjacent Node Connection Performance(ANI_IP)..................................................3656
2.4.1 IP Transport Adjacent Node Connection Measurement(ANIIPCONN)...............................................................3657
2.4.2 IP Transport Adjacent Node Resource Operation Measurement(ANIIPTRM)....................................................3662
2.5 Measurement of QAAL2 Adjacent Node Performance(ANI_QAAL2)...................................................................3668
2.5.1 QAAL2 Measurement(QAAL2)............................................................................................................................3668
2.6 Measurement of Dual-Stack Transport Adjacent Node Performance(ANI_QAAL2_IP)........................................3696
2.6.1 Dual-Stack Transport Adjacent Node IP Part Measurement(IPPART)................................................................3696
2.6.2 Dual-Stack Transport Adjacent Node Measurement(QAAL2IP)..........................................................................3705
2.6.3 Dual-Stack Transport Adjacent Node QAAL2 Part Measurement(QAAL2PART).............................................3710
2.7 Measurement of ATM Logical Port Performance(ATM_LOGIC_PORT)..............................................................3738
2.7.1 ATM Logical Port Measurement(ATM.LOGIC.PORT).......................................................................................3738
2.8 Measurement of Channelized Optical Port Performance(CHANNELIZED_OPTICAL_PORT)...........................3744
2.8.1 Channelized Optical Port Measurement(CHANNELIZED.OPTICAL.PORT)....................................................3744
2.9 Measurement of E1/T1 Port Bit Error Performance(E1T1_ES)...............................................................................3745
Issue 03 (2015-06-30)

viii
BSC6900 UMTS
Contents
2.9.1 E1/T1 Port Bit Error Measurement(E1T1_ES).....................................................................................................3746

2.10 Measurement of E1/T1 Electrical Port Performance(ELECT)...............................................................................3756
2.10.1 E1/T1 Electrical Port Measurement(ELECT).....................................................................................................3756
2.11 Measurement of FE/GE Ethernet Port Performance(FEGE)..................................................................................3764
2.11.1 FE/GE Ethernet Port Measurement(FEGE)........................................................................................................3764
2.12 Measurement of Integrated Firewall Performance(FIREWALL)..........................................................................3781
2.12.1 Packetfilter Measurement(PACKETFILTER.FIREWALL)...............................................................................3781
2.13 Measurement of Fractional ATM Link Performance(FRACATMLNK)...............................................................3783
2.13.1 Fractional ATM Link Measurement(FRACATMLNK)......................................................................................3783
2.14 Measurement of Fractioanl IMA Link Performance(FRACIMALNK).................................................................3792
2.14.1 Fractional IMA Link Measurement(FRACIMALNK)........................................................................................3793
2.15 Measurement of IMA Group Performance(IMAGRP)...........................................................................................3798
2.15.1 IMA Group Measurement(IMAGRP).................................................................................................................3799
2.16 Measurement of IMA Link Performance(IMALNK).............................................................................................3810
2.16.1 IMA Link Measurement(IMALNK)...................................................................................................................3810
2.17 Measurement of Interface Board for Transport Resource Management Result Performance(INT_TRM)............3820
2.17.1 Interface Board Admit Measurement(INT.TRM.ADMIT).................................................................................3820
2.17.2 Interface Board Flow Resource Usage Measurement(INT.TRM.FLOW)..........................................................3831
2.18 Measurement of IPoA Link Performance(IPOALNK)...........................................................................................3838
2.18.1 IPoA Link Measurement(IPOALNK).................................................................................................................3838
2.19 Measurement of IPoAPVC VCL PM Performance(IPOAPVC_VCLPM)............................................................3845
2.19.1 IPoAPVC VCL PM Measurement(IPOAPVC.VCLPM)....................................................................................3846
2.20 Measurement of IP Path Performance(IPPATH)...................................................................................................3854
2.20.1 IPPath Measurement(IPPATH)...........................................................................................................................3854
2.21 Measurement of IPPath IP Layer Performance(IPPATH_IPLAYER)...................................................................3866
2.21.1 IPPath IP Layer Measurement(IPPATH.IPLAYER)..........................................................................................3866
2.22 Measurement of IPPath PM Performance(IPPATH_PM)......................................................................................3876
2.22.1 IPPM Measurement(IPPATH.PM)......................................................................................................................3876
2.23 Measurement of IPPath RTP Performance(IPPATH_RTP)...................................................................................3884
2.23.1 IPPath RTP Measurement(IPPATH.RTP)..........................................................................................................3884
2.24 Measurement of Transmission Resource Pool Adjacent Node Performance(IPPOOL_ADJNODE)....................3895
2.24.1 Transmission Resource Pool Adjacent Node User-Plane Traffic Measurement(IPPOOL.ADJNODE.IPLAYER)
........................................................................................................................................................................................3896
2.24.2 Transmission Resource Pool Adjacent Node IP Transmission Quality Measurement(IPPOOL.ADJNODE)
........................................................................................................................................................................................3901
2.25 Measurement of Transmission Resource Pool IPPM Performance(IPPOOL_PM)...............................................3911
2.25.1 Transmission Resource Pool IPPM Measurement(IPPOOL.PM).......................................................................3911
2.26 Measurement of Transmission Resource Pool IP Address RTP Performance(IPPOOL_RTP).............................3920
2.26.1 Transmission Resource Pool IP Address RTP Measurement(IPPOOL.RTP).....................................................3921
2.27 Measurement of Transmission Resource Pool Local IP Address Performance(IPPOOL_SIP).............................3932
2.27.1 Transmission Resource Pool Local IP Address IP Layer Measurement(IPPOOL.SIP.IPLAYER)....................3932
2.27.2 Transmission Resource Pool Local IP Address Transmission Quality Measurement(IPPOOL.SIP).................3937
Issue 03 (2015-06-30)

ix
BSC6900 UMTS
Contents
2.28 Measurement of Iur-p Link Performance(IURPLNK)...........................................................................................3939

2.28.1 Iur-p Link Measurement(IURPLNK)..................................................................................................................3939
2.29 Measurement of Local IP Address Performance(LOCAL_IPADDRESS)............................................................3954
2.29.1 Local IP Address IP Layer Measurement(LOCAL.IPADDRESS.IPLAYER)...................................................3954
2.30 Measurement of Logic Port Performance(LOGIC_PORT)....................................................................................3960
2.30.1 Logical Port Measurement(LOGIC.PORT)........................................................................................................3961
2.31 Measurement of Logic Port Queue Performance(LOGIC_PORT_QUEUE).........................................................3971
2.31.1 Logical Port Queue Measurement(LOGIC.PORT.QUEUE)...............................................................................3972
2.32 Measurement of M3UA Destination Entity Performance(M3UA_DE).................................................................3976
2.32.1 M3UA Destination Entity Measurement(M3UA.DE).........................................................................................3976
2.33 Measurement of M3UA Link Performance(M3UA_LNK)....................................................................................3979
2.33.1 M3UA Link Measurement(M3UA.LNK)...........................................................................................................3979
2.34 Measurement of M3UA Link Set Performance(M3UA_LNK_SET)....................................................................3984
2.34.1 M3UA Link Set Measurement(M3UA.LNKSET)..............................................................................................3984
2.35 Measurement of MP Group Performance(MLPPP)...............................................................................................3986
2.35.1 MP Group Measurement(MLPPP)......................................................................................................................3987
2.36 Measurement of MP Queue Performance(MLPPP_QUEUE)................................................................................3998
2.36.1 MP Queue Measurement(MLPPP.QUEUE).......................................................................................................3999
2.37 Measurement of MTP3 Destination Signaling Point Performance(MTP3_DSP)..................................................4004
2.37.1 MTP3 DSP Measurement(MTP3.DSP)...............................................................................................................4004
2.38 Measurement of MTP3 Link Performance(MTP3_LNK)......................................................................................4007
2.38.1 MTP3 Link Measurement(MTP3.LNK)..............................................................................................................4007
2.39 Measurement of MTP3 Link Set Performance(MTP3_LNK_SET).......................................................................4025
2.39.1 MTP3 Link Set Measurement(MTP3.LNKSET)................................................................................................4025
2.40 Measurement of Non-Channelized Optical Port Performance(NON_CHANNELIZED_OPTICAL_PORT)......4027
2.40.1 Non-Channelized Optical Port Measurement(NON.CHANNELIZED.OPTICAL.PORT)................................4028
2.40.2 Maximum UOI Data Rate Measurement(UOI.BOARD)....................................................................................4037
2.41 Measurement of NodeB OAM Flow Performance(OAM_FLOW)........................................................................4039
2.41.1 NodeB OAM Flow Measurement(OAM.FLOW)...............................................................................................4039
2.42 Measurement of PPP Link Performance(PPP).......................................................................................................4046
2.42.1 PPP Link Measurement(PPP)..............................................................................................................................4046
2.43 Measurement of PPP Link Queue Performance(PPP_QUEUE)............................................................................4057
2.43.1 PPP Link Queue Measurement(PPP.QUEUE)....................................................................................................4057
2.44 Measurement of SAAL Link Performance(SAAL_LNK).....................................................................................4062
2.44.1 SAAL Link Measurement(SAAL.LNK).............................................................................................................4062
2.45 Measurement of SAAL Link ATM Layer Performance(SAALLNK_PVCLAYER)............................................4076
2.45.1 SAAL link ATM Layer Measurement(SAALLNK.PVCLAYER).....................................................................4076
2.46 Measurement of SAAL VCL PM Performance(SAALLNK_VCLPM)................................................................4084
2.46.1 SAAL Link VCL PM Measurement(SAALLNK.VCLPM)................................................................................4085
2.47 Measurement of SCCP OSP Performance(SCCP).................................................................................................4093
2.47.1 SCCP OSP Measurement(SCCP)........................................................................................................................4093
Issue 03 (2015-06-30)

BSC6900 UMTS
Contents
2.48 Measurement of SCTP Link Performance(SCTPLNK).........................................................................................4119

2.48.1 SCTP IP Measurement(SCTPIP).........................................................................................................................4119
2.48.2 SCTP Link Measurement(SCTPLNK)................................................................................................................4127
2.49 Measurement of SCTP Link IP Layer Performance(SCTPLNK_IPLAYER).......................................................4131
2.49.1 SCTP Link IP Layer Measurement(SCTPLNK.IPLAYER)...............................................................................4132
2.50 Measurement of SDH Performance(SDH).............................................................................................................4136
2.50.1 SDH Measurement(SDH)....................................................................................................................................4136
2.51 Measurement of Trunk Group Performance(Trunk)..............................................................................................4139
2.51.1 Trunk Group Measurement(Trunk).....................................................................................................................4139
2.52 Measurement of TWAMP Performance(TWAMP)...............................................................................................4154
2.52.1 TWAMP Transport Link Measurement(TransportLink.TWAMP).....................................................................4155
2.53 Measurement of UNI Link Performance(UNILNK)..............................................................................................4163
2.53.1 UNI Link Measurement(UNILNK).....................................................................................................................4163
2.54 Measurement of VC Cross Connection Performance(VCACROSS).....................................................................4171
2.54.1 VC Cross Connection Measurement(VCACROSS)............................................................................................4171
3 Hardware Platform Related Measurement.........................................................................4180

3.1 Measurement of ASU Subsystem Performance(ASU).............................................................................................4181
3.1.1 ASU Subsystem Measurement(ASU)...................................................................................................................4181
3.2 Measurement of DEU Subsystem Performance(DEU)............................................................................................4185
3.2.1 DEU Subsystem Measurement(DEU)...................................................................................................................4185
3.3 Measurement of DEU DSP Performance(DEUDSP)...............................................................................................4189
3.3.1 DEU DSP Measurement(DEUDSP)......................................................................................................................4189
3.4 Measurement of DPU Subsystem Performance(DPU).............................................................................................4191
3.4.1 DPU Subsystem Measurement(DPU)...................................................................................................................4191
3.5 Measurement of Inter-Subrack Traffic Performance(FRAME_FLUX)...................................................................4195
3.5.1 Inter-Subrack Traffic Measurement(FRAME.FLUX)...........................................................................................4195
3.6 Measurement of GCU Subsystem Performance(GCU)............................................................................................4199
3.6.1 GCU Subsystem Measurement(GCU)...................................................................................................................4200
3.7 Measurement of Interface Board Subsystem Performance(INT).............................................................................4204
3.7.1 Interface Board Subsystem Measurement(INT)....................................................................................................4204
3.8 Measurement of NIU DSP Performance(NDSP).....................................................................................................4211
3.8.1 NIU DSP Measurement(NDSP)............................................................................................................................4211
3.9 Measurement of NIU Subsystem Performance(NIU)...............................................................................................4214
3.9.1 NIU Subsystem Measurement(NIU).....................................................................................................................4214
3.10 Measurement of RNC Node Performance(RNCNODE)........................................................................................4218
3.10.1 Reserved Counter Measurement <per RNCNODE>(RESERVE.RNCNODE)..................................................4219
3.10.2 RNC Node Traffic Measurement(TRAFFIC.RNCNODE).................................................................................4220
3.11 Measurement of SCU Subsystem Performance(SCU)...........................................................................................4222
3.11.1 SCU Subsystem Measurement(SCU)..................................................................................................................4222
3.12 Measurement of XPU Subsystem Performance(XPU)...........................................................................................4226
3.12.1 XPU Subsystem Measurement(XPU).................................................................................................................4226
Issue 03 (2015-06-30)

xi
BSC6900 UMTS
Contents
Index..............................................................................................................................................4233
Issue 03 (2015-06-30)

xii
BSC6900 UMTS
1 UMTS Radio Network Related Measurement
UMTS Radio Network Related

Measurement
About This Chapter

The following measurements are UMTS Radio Network Related Measurement.
1.1 Measurement of CNOperator Performance(CNOPERATOR)
1.2 Measurement of CPUS Subsystem Performance(CPUS)
1.3 Measurement of GTP-U Performance(GTPU)
1.4 Measurement of Iu Interface Performance(IU)
1.5 Measurement of Iur Interface Performance(IUR)
1.6 Measurement of MPU Subsystem Performance(MPU)
1.7 Measurement of NodeB Performance(NODEB)
1.8 Measurement of Load Sharing Node Performance(NODESHARE)
1.9 Measurement of NodeB-Level CNOperator Performance(PLMN_NodeB)
1.10 Measurement of RNC Performance(RNC)
1.11 Measurement of ROAMCNOperator Performance(ROAM_CNOPERATOR)
1.12 Measurement of Cell Performance(UCELL)
1.13 Measurement of UMTS Cell-to-GSM Cell Handover Performance(UCELL_GCELL)
1.14 Measurement of UMTS Cell-to-LTE Cell Handover Performance(UCELL_LCELL)
1.15 Measurement of UMTS Cell-to-UMTS Cell Handover Performance(UCELL_NCELL)
1.16 Measurement of UMTS DSP Performance(UDSP)
1.17 Measurement of UMTS NIU DSP Performance(UNIUDSP)
Issue 03 (2015-06-30)

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
Algorithm Measurement per PLMN
RAB.Estab.PLMN.RNC
RAB Setup Measurement per PLMN
RAB.Rel.PLMN.RNC
RAB Release Measurement per PLMN
TRAFF.LOAD.PLMN.RNC
Traffic Measurement per PLMN
1.1.1 Algorithm Measurement per PLMN(ALGO.PLMN.RNC)

Overview
Measurement is used to measure active algorithm of RNC for each Operator.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73394050
VS.PI.HSDPA.TR
BNum.PLMN.RNC
Number of TRBs of
HSDPA Service on
Which Packet
Inspection (PI) Takes
Effect for RNC
BSC6900
V900R012
Counter Relationship
None
Issue 03 (2015-06-30)

BSC6900 UMTS
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
MN.RNC
Number of TRBs of HSDPA

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

Subscribed Service
1.1.2 RAB Setup Measurement 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.
Issue 03 (2015-06-30)

BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67196186
VS.RAB.AttEstab.
AMR.PLMN.RNC
Number of AMR CS
RABs Establishment
Requests for
Operator
Earlier than
BSC6900
V900R011
67196187
VS.RAB.SuccEstab
.AMR.PLMN.RNC
Number of AMR CS
RABs Successfully
Established for
Operator(WB+NB)
Earlier than
BSC6900
V900R011
67196188
VS.RAB.AttEstab.
CS64.PLMN.RNC
Number of 64kbit/s
CS Conversational
Service RABs
Establishment
Requests for
Operator
Earlier than
BSC6900
V900R011
67196189
VS.RAB.SuccEstab
.CS64.PLMN.RNC
Number of 64kbit/s
CS Conversational
Service RABs
Successfully
Established for
Operator
Earlier than
BSC6900
V900R011
67196190
VS.RAB.AttEstab.
PS.PLMN.RNC
Number of PS RABs
Establishment
Requests for
Operator
Earlier than
BSC6900
V900R011
67196191
VS.RAB.SuccEstab
.PS.PLMN.RNC
Number of PS RABs
Successfully
Established for
Operator
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

BSC6900 UMTS
Number of RABs Requested to Establish for each Operator

Counters
Counter ID
Counter Name
Counter Description
67196186
VS.RAB.AttEstab.AMR.PL
MN.RNC
Number of AMR CS RABs

Establishment Requests for
Operator
67196188
VS.RAB.AttEstab.CS64.PL
MN.RNC
Number of 64kbit/s CS
Conversational Service
RABs Establishment
Requests for Operator
67196190
VS.RAB.AttEstab.PS.PLM
N.RNC
Number of PS RABs
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 preceding counters comply
with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

BSC6900 UMTS
Figure 1-1 RAB setup procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstab.AMR.PL
MN.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010501
Conversational QoS Class

VS.RAB.AttEstab.CS64.PL
MN.RNC
WRFD-021311
WRFD-010501
MOCN Introduction
Package
Issue 03 (2015-06-30)

BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstab.PS.PLM
N.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
Connection and Radio
Access Bearer Establishment
and Release
Number of Successfully Established RABs for each Operator

Counters
Counter ID
Counter Name
Counter Description
67196187
VS.RAB.SuccEstab.AMR.P
LMN.RNC
Number of AMR CS RABs

Successfully Established for
Operator(WB+NB)
67196189
VS.RAB.SuccEstab.CS64.P
LMN.RNC
RABs Successfully
Established for Operator
67196191
VS.RAB.SuccEstab.PS.PL
MN.RNC
Number of PS RABs
Operator
Description
The measurement items provide the number of RABs successfully established according to
different types of service for each operator, as shown below.The preceding counters comply
Issue 03 (2015-06-30)
Counter Name
Description
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

BSC6900 UMTS
Measurement point
The measurement is triggered at point B as shown in the figure.If the RNC finds that some RABs
have been successfully set up after receiving a RADIO BEARER SETUP COMPLETE message
from the UE, the RNC measures the items when the RNC sends RAB ASSIGNMENT
RESPONSE message to CN according to the types of service for each operator.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstab.AMR.P
LMN.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010501
Issue 03 (2015-06-30)

BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstab.CS64.P
LMN.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010501

VS.RAB.SuccEstab.PS.PL
MN.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.1.3 RAB Release Measurement 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196192
VS.RAB.AbnormR
el.AMR.PLMN.RN
C
Number of
Abnormally
Released AMR CS
RABs for Operator
Earlier than
BSC6900
V900R011
67196193
VS.RAB.NormRel.
AMR.PLMN.RNC
Number of Normally
Released AMR CS
RABs for Operator
Earlier than
BSC6900
V900R011
67196194
VS.RAB.AbnormR
el.CS64.PLMN.RN
C
Number of
Abnormally
Released 64kbit/s CS
Conversational
Service RABs for
Operator
Earlier than
BSC6900
V900R011
67196195
VS.RAB.NormRel.
CS64.PLMN.RNC
Number of Normally
Conversational
Service RABs for
Operator
Earlier than
BSC6900
V900R011

BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67196196
VS.RAB.AbnormR
el.PS.PLMN.RNC
Number of
Abnormally
Released PS RABs
for Operator
Earlier than
BSC6900
V900R011
67196197
VS.RAB.NormRel.
PS.PLMN.RNC
Number of Normally
Released PS RABs
for Operator
Earlier than
BSC6900
V900R011
None
Number of Abnormally Released RABs for each Operator

Counters
Counter ID
Counter Name
Counter Description
67196192
VS.RAB.AbnormRel.AMR.
PLMN.RNC
Number of Abnormally
Released AMR CS RABs for
Operator
67196194
VS.RAB.AbnormRel.CS64.
PLMN.RNC
RABs for Operator
67196196
VS.RAB.AbnormRel.PS.PL
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.The preceding counters comply with section "8.2 RAB
Assignment" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.RAB.AbnormRel.AMR.PLMN.RNC
Number of abnormally released AMR service

RABs for each operator(narrowband and

10
BSC6900 UMTS
Counter Name
Description
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.
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
Issue 03 (2015-06-30)

11
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
Figure 1-5 Iu connection release procedure
Issue 03 (2015-06-30)

12
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
PLMN.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010501

PLMN.RNC
WRFD-021311
WRFD-010501
MOCN Introduction
Package
VS.RAB.AbnormRel.PS.PL
MN.RNC
WRFD-021311
WRFD-010510
MOCN Introduction
Package
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Normally Released RABs for each Operator

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196193
VS.RAB.NormRel.AMR.PL
MN.RNC
Number of Normally
Released AMR CS RABs for
Operator
67196195
VS.RAB.NormRel.CS64.PL
MN.RNC
Number of Normally
RABs for Operator
67196197
VS.RAB.NormRel.PS.PLM
N.RNC
Number of Normally
Released PS RABs for
Operator

13
BSC6900 UMTS
Description
The measurement items take statistics of the number of normally released RABs of different
type services for each Operator.The preceding counters comply with section "8.2 RAB
Counter Name
Description
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.
Issue 03 (2015-06-30)

14
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.
Figure 1-7 RAB release procedure (successful operation)
Formula
None
Unit
None
Issue 03 (2015-06-30)

15
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.AMR.PL
MN.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010501

VS.RAB.NormRel.CS64.PL
MN.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010501

VS.RAB.NormRel.PS.PLM
N.RNC
WRFD-021311
MOCN Introduction
Package
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.1.4 Traffic Measurement per PLMN(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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203962
VS.CSLoad.Erlang
.Equiv.PLMN.RNC
Equivalent CS
Erlang for RNC per
Operator
Earlier than
BSC6900
V900R011
67192511
VS.CSLoad.MaxEr
lang.Equiv.PLMN.
RNC
Maximum
equivalent CS Erlang
for RNC per
Operator
Earlier than
BSC6900
V900R011
67204145
VS.R99PSLoad.UL
Thruput.PLMN.R
NC
Uplink PS R99
Traffic for RNC per
Operator
Earlier than
BSC6900
V900R011
67193010
VS.R99PSLoad.Ma
xULThruput.PLM
N.RNC
Maximum Uplink PS
R99 Traffic for RNC
per Operator
Earlier than
BSC6900
V900R011

16
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204146
VS.R99PSLoad.DL
Thruput.PLMN.R
NC
Downlink PS R99
Traffic for RNC per
Operator
Earlier than
BSC6900
V900R011
67193013
VS.R99PSLoad.Ma
xDLThruput.PLM
N.RNC
Maximum Downlink
PS R99 Traffic for
RNC per Operator
Earlier than
BSC6900
V900R011
67204147
VS.HSDPAPSLoad
.DLThruput.PLM
N.RNC
Downlink PS
HSDPA Traffic for
RNC per Operator
Earlier than
BSC6900
V900R011
67193016
VS.HSDPAPSLoad
.MaxDLThruput.P
LMN.RNC
Maximum Downlink
PS HSDPA Traffic
for RNC per
Operator
Earlier than
BSC6900
V900R011
67204148
VS.HSUPAPSLoad
.ULThruput.PLM
N.RNC
Uplink PS HSUPA
Traffic for RNC per
Operator
Earlier than
BSC6900
V900R011
67193019
VS.HSUPAPSLoad
.MaxULThruput.P
LMN.RNC
Maximum Uplink PS
HSUPA Traffic for
RNC per Operator
Earlier than
BSC6900
V900R011
67204149
VS.MBMSPSLoad.
DLThruput.PLMN
.RNC
Downlink PS MBMS
Traffic for RNC per
Operator
Earlier than
BSC6900
V900R011
67193022
VS.MBMSPSLoad.
MaxDLThruput.P
LMN.RNC
Maximum Downlink
PS MBMS Traffic
for RNC per
Operator
Earlier than
BSC6900
V900R011
67204835
VS.AMR.Erlang.E
quiv.PLMN.RNC
Equivalent Erlang of
CS AMR Service for
RNC per Operator
Earlier than
BSC6900
V900R011
67204836
VS.VP.Erlang.Equi
v.PLMN.RNC
64kbit/s CS Service
for RNC per
Operator
Earlier than
BSC6900
V900R011
67204840
VS.PS.CellDchUEs.
PLMN
Number of
Cell_DCH UEs in PS
Domain for RNC per
Operator
Earlier than
BSC6900
V900R011

17
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394023
VS.PSLoad.MaxTh
ruput.PLMN.RNC
Maximum Total
Throughout of UL
and DL PS Services
per Operator for
RNC
BSC6900
V900R012
73410502
VS.PSLoad.Thrup
ut.PLMN.RNC
Average Total
Throughput of UL
and DL PS Services
per Operator for
RNC
BSC6900
V900R012
73440109
VS.PS.CellFachUE
s.PLMN
Number of
Cell_FACH UEs in
PS Domain for RNC
per Operator
BSC6900
V900R012
73429112
VS.AMR.SMLESS
CrstVoice.Erlang.E
quiv.PLMN.RNC
Equivalent Erlang
Consumed by AMR
Voice Services
Using the Seamless
Crystal Voice
Feature for RNC (per
Operator)
BSC6900
V900R017C00
73429115
VS.AMR.SMLESS
CrstVoice.MaxErla
ng.Equiv.PLMN.R
NC
Maximum
Equivalent Erlang
Consumed by AMR
Voice Services
Using the Seamless
Crystal Voice
Feature for RNC (per
Operator)
BSC6900
V900R017C00
73445320
VS.PSLoad.TCPPr
oxy.DLThruput.PL
MN.RNC
Amount of DL PS
Traffic Using TCP
Proxy for RNC (Per
Operator)
BSC6900
V900R017C00
73429285
VS.PSLoad.TCPPr
oxy.MaxDLThrupu
t.PLMN.RNC
Maximum Amount
of DL PS Traffic
Using TCP Proxy for
RNC (Per Operator)
BSC6900
V900R017C00
73445322
VS.PSLoad.TCP.D
LThruput.PLMN.
RNC
Amount of DL PS
Traffic of TCP
Services for RNC
(Per Operator)
BSC6900
V900R017C00

18
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73446319
VS.AMR.CrstVoic
eDeepCover.Erlang
.Equiv.PLMN.RNC
AMR Services Using
Crystal Voice in
Deep Coverage for
RNC (per Operator)
BSC6900
V900R017C10
73430145
VS.AMR.CrstVoic
eDeepCover.MaxE
rlang.Equiv.PLMN
.RNC
Maximum
AMR Services Using
Crystal Voice in
Deep Coverage for
RNC (per Operator)
BSC6900
V900R017C10
73446340
VS.RadioAwaredV
ideo.Thruput.PLM
N.RNC
Traffic of Video
Services based on
RAN-Initiated
Service Awareness
for RNC (per
Operator)
BSC6900
V900R017C10
None
Equivalent Erlang of CS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67203962
VS.CSLoad.Erlang.Equiv.P
LMN.RNC
Equivalent CS Erlang for

RNC per Operator
Description
This measurement item provides the equivalent Erlang values of all services in the CS domain
of the RNC for each Operator. The item is measured only when the RAN sharing function or
MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of all services in the
CS domain for each Operator every five seconds. At the end of the measurement period, the
RNC calculates the mean sample (divide the accumulated value by the sampling times), include
the equivalent Erlang of all radio links of Soft Handover.Each time a CS domain service is
Issue 03 (2015-06-30)

19
BSC6900 UMTS
admitted, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent
Erlang of the CS domain of the RNC. Each time a CS domain service is released, the RNC
decreases the equivalent Erlang of the CS domain of the RNC.
Formula
None
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
LMN.RNC
WRFD-021304
RAN Sharing Introduction

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Independent License Control
Maximum Equivalent Erlang of CS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67192511
VS.CSLoad.MaxErlang.Equ
iv.PLMN.RNC
Maximum equivalent CS
Erlang for RNC per Operator
Description
This measurement item provides the maximum equivalent Erlang values of all services in the
CS domain of the RNC for each Operator. The item is measured only when the RAN sharing
function or MOCN function is switched on.
Measurement point
The RNC periodically takes the samples of the equivalent Erlang values of all services in the
CS domain for each Operator every five seconds and calculates the maximum, include the
equivalent Erlang of all radio links of Soft Handover.Each time a CS domain service is admitted,
the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of
the CS domain of the RNC. Each time a CS domain service is released, the RNC decreases the
equivalent Erlang of the CS domain of the RNC.
Issue 03 (2015-06-30)

20
BSC6900 UMTS
Formula
None
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
iv.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Uplink Traffic of R99 PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67204145
VS.R99PSLoad.ULThruput.
PLMN.RNC
Uplink PS R99 Traffic for

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
Issue 03 (2015-06-30)

21
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Maximum Uplink Traffic of R99 PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67193010
VS.R99PSLoad.MaxULThr
uput.PLMN.RNC
Maximum Uplink PS R99

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

22
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
uput.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Downlink Traffic of R99 PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67204146
VS.R99PSLoad.DLThruput.
PLMN.RNC
Downlink PS R99 Traffic for

RNC per Operator
Description
This measurement item provides the downlink traffic of all the R99 services in the PS domain
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
Issue 03 (2015-06-30)

23
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Maximum Downlink Traffic of R99 PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67193013
VS.R99PSLoad.MaxDLThr
uput.PLMN.RNC
Maximum Downlink PS R99

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
Issue 03 (2015-06-30)

24
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
uput.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Downlink Traffic of HSDPA PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67204147
VS.HSDPAPSLoad.DLThru
put.PLMN.RNC
Downlink PS HSDPA
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
Issue 03 (2015-06-30)

25
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
put.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Maximum Downlink Traffic of HSDPA PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67193016
VS.HSDPAPSLoad.MaxDL
Thruput.PLMN.RNC
Maximum Downlink PS
HSDPA Traffic for RNC per
Operator
Description
This measurement item provides the maximum downlink traffic of all the HSDPA services in
the PS domain of the RNC for each Operator. The item is measured only when the RAN sharing
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
Issue 03 (2015-06-30)

26
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
Thruput.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Uplink Traffic of HSUPA PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67204148
VS.HSUPAPSLoad.ULThru
put.PLMN.RNC
Uplink PS HSUPA Traffic

for RNC per Operator
Description
This measurement item provides the uplink traffic of all the HSUPA services in the PS domain
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
Issue 03 (2015-06-30)

27
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
put.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Maximum Uplink Traffic of HSUPA PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67193019
VS.HSUPAPSLoad.MaxUL
Thruput.PLMN.RNC
Maximum Uplink PS
HSUPA Traffic for RNC per
Operator
Description
This measurement item provides the maximum uplink traffic of all the HSUPA services in the
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
Issue 03 (2015-06-30)

28
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
Thruput.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Downlink Traffic of MBMS or IMB PS Domain of RNC for each Operator

Counters
Counter ID
Counter Name
Counter Description
67204149
VS.MBMSPSLoad.DLThru
put.PLMN.RNC
Downlink PS MBMS Traffic

for RNC per Operator
Description
This measurement item provides the downlink traffic of all the MBMS or IMB services in the
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
Issue 03 (2015-06-30)

29
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
put.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Maximum Downlink Traffic of MBMS or IMB PS Domain of RNC for each

Operator
Counters
Counter ID
Counter Name
Counter Description
67193022
VS.MBMSPSLoad.MaxDL
Thruput.PLMN.RNC
Maximum Downlink PS
MBMS Traffic for RNC per
Operator
Description
This measurement item provides the maximum downlink traffic of all the MBMS or IMB
services in the PS domain of the RNC for each Operator. The item is measured only when the
RAN sharing function or MOCN function is switched on.
Measurement point
MBMS or IMB services in the PS domain for each Operator every five seconds. At the end of
the measurement period, the RNC calculates the maximum sample value.The downlink traffic
of all the MBMS or IMB services in the PS domain refers to the traffic measured at the RLC
layer. The data does not include the RLC head data.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

30
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMSPSLoad.MaxDL
Thruput.PLMN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
WRFD-010616
MOCN Introduction
Package
MBMS Introduction
Package
Equivalent Erlang of CS Domain AMR Service of RNC for each Operator

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

31
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AMR.Erlang.Equiv.PL
MN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Equivalent Erlang of CS Domain CS 64kbit/s Conversational Service of RNC for

each Operator
Counters
Counter ID
Counter Name
Counter Description
67204836
VS.VP.Erlang.Equiv.PLMN
.RNC
Equivalent Erlang of 64kbit/

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

32
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.VP.Erlang.Equiv.PLMN
.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
The Number of Cell_DCH UEs in PS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

33
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.CellDchUEs.PLMN
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Maximum Total Throughout of UL and DL PS Services per Operator for RNC

Counters
Counter ID
Counter Name
Counter Description
73394023
VS.PSLoad.MaxThruput.PL
MN.RNC
Maximum Total Throughout

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

34
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.PSLoad.MaxThruput.PL
MN.RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Average Total Throughput of UL and DL PS Services per Operator for RNC

Counters
Counter ID
Counter Name
Counter Description
73410502
VS.PSLoad.Thruput.PLMN.
RNC
Average Total Throughput of

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

35
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.PSLoad.Thruput.PLMN.
RNC
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
The Number of Cell_FACH UEs in PS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

36
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.CellFachUEs.PLMN
WRFD-021304

Package
WRFD-021311
WRFD-02130404
MOCN Introduction
Package
Equivalent Erlang Consumed by AMR Voice Services Using the Seamless Crystal
Voice Feature for RNC (per Operator)
Counters
Counter ID
Counter Name
Counter Description
73429112
VS.AMR.SMLESSCrstVoic
e.Erlang.Equiv.PLMN.RNC
Equivalent Erlang
Consumed by AMR Voice
Services Using the Seamless
Crystal Voice Feature for
RNC (per Operator)
Description
This counter provides the equivalent Erlang consumed by CS AMR voice services (AMR-WB
and AMR-NB voice services) using the seamless crystal voice feature of an operator in an RNC.
This counter applies only to the scenario where the RAN sharing or multi-operator core network
(MOCN) feature is enabled. This counter does not apply to the UEs whose best cells are under
the DRNC.
Measurement point
This counter is measured on a per operator basis in an RNC. The system takes samples of the
equivalent Erlang consumed by CS AMR voice services using the seamless crystal voice feature
every five seconds in a measurement period. At the end of a measurement period, the system
obtains the value of this counter by dividing the accumulated sampling value in the period by
the number of times sampled. The counter value includes the equivalent Erlang consumed by
CS AMR voice services on all RLs during a soft handover. When a UE initiates a CS AMR
voice service and the service uses the seamless crystal voice feature, the system converts the CS
rate into the equivalent Erlang and increases the equivalent Erlang accordingly. When a CS
AMR voice service is released or the seamless crystal voice feature is deactivated for a CS AMR
voice service, the system decreases equivalent Erlang accordingly.
Formula
None
Issue 03 (2015-06-30)

37
BSC6900 UMTS
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
e.Erlang.Equiv.PLMN.RNC
WRFD-170201
Seamless Crystal Voice
Maximum Equivalent Erlang Consumed by AMR Voice Services Using the

Seamless Crystal Voice Feature for RNC (per Operator)
Counters
Counter ID
Counter Name
Counter Description
73429115
e.MaxErlang.Equiv.PLMN.
RNC
Maximum Equivalent Erlang

RNC (per Operator)
Description
This counter provides the maximum equivalent Erlang consumed by CS AMR voice services
(AMR-WB and AMR-NB voice services) using the seamless crystal voice feature of an operator
in an RNC. This counter applies only to the scenario where the RAN sharing or MOCN feature
is enabled. This counter does not apply to the UEs whose best cells are under the DRNC.
Measurement point
This counter is measured on a per operator basis in an RNC. The system takes samples of the
equivalent Erlang consumed by CS AMR voice services using the seamless crystal voice feature
every five seconds in a measurement period. At the end of a measurement period, the system
obtains the maximum equivalent Erlang consumed by CS AMR voice services using the
seamless crystal voice feature of an operator in an RNC. This maximum value includes the
equivalent Erlang consumed by CS AMR voice services on all RLs during a soft handover. When
a UE initiates a CS AMR voice service and the service uses the seamless crystal voice feature,
the system converts the CS rate into the equivalent Erlang and increases the equivalent Erlang
accordingly. When a CS AMR voice service is released or the seamless crystal voice feature is
deactivated for a CS AMR voice service, the system decreases equivalent Erlang accordingly.
Formula
None
Issue 03 (2015-06-30)

38
BSC6900 UMTS
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
e.MaxErlang.Equiv.PLMN.
RNC
WRFD-170201
Amount of DL PS Traffic Using TCP Proxy for RNC (Per Operator)

Counters
Counter ID
Counter Name
Counter Description
73445320
VS.PSLoad.TCPProxy.DLT
hruput.PLMN.RNC
Amount of DL PS Traffic
Using TCP Proxy for RNC
(Per Operator)
Description
This counter provides the amount of DL PS traffic that uses TCP proxy on the RNC. This counter
is measured on a per operator basis. It is measured only when the RAN sharing or multi-operator
core network (MOCN) feature is enabled.
Measurement point
The system takes samples of the amount of DL PS traffic (unit: kbit/s) that belongs to a certain
operator and uses the TCP proxy function every five seconds in a measurement period. At the
end of the measurement period, the RNC obtains the value of this counter by dividing the
accumulated traffic volume by the number of times sampled. This counter is measured at the
RLC layer. It includes soft handover traffic and excludes RLC headers.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

39
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
hruput.PLMN.RNC
WRFD-170202
TCP Proxy
Maximum Amount of DL PS Traffic Using TCP Proxy for RNC (Per Operator)
Counters
Counter ID
Counter Name
Counter Description
73429285
VS.PSLoad.TCPProxy.Max
DLThruput.PLMN.RNC
Maximum Amount of DL PS
Traffic Using TCP Proxy for
RNC (Per Operator)
Description
This counter provides the maximum amount of DL PS traffic that uses the TCP proxy function
on the RNC. This counter is measured on a per operator basis. It is measured only when the
RAN sharing or MOCN feature is enabled.
Measurement point
The system takes samples of the amount of DL PS traffic (unit: kbit/s) that belongs to a certain
operator and uses the TCP proxy function every five seconds in a measurement period. At the
end of the measurement period, the RNC obtains the maximum amount of DL PS traffic that
belongs to a certain operator and uses the TCP proxy function. This counter is measured at the
RLC layer. It includes soft handover traffic and excludes RLC headers.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
DLThruput.PLMN.RNC
WRFD-170202
TCP Proxy

40
BSC6900 UMTS
Amount of DL PS Traffic of TCP Services for RNC (Per Operator)

Counters
Counter ID
Counter Name
Counter Description
73445322
VS.PSLoad.TCP.DLThrupu
t.PLMN.RNC
Amount of DL PS Traffic of
TCP Services for RNC (Per
Operator)
Description
This counter provides the amount of DL PS traffic of the TCP services on the RNC. This counter
is measured on a per operator basis. It is measured only when the RAN sharing or MOCN feature
is enabled.
Measurement point
The system takes samples of the amount of DL PS traffic (unit: kbit/s) of the TCP services that
belong to a certain operator every five seconds in a measurement period. At the end of the
measurement period, the RNC obtains the value of this counter by dividing the accumulated
traffic volume by the number of times sampled. This counter is measured at the RLC layer. It
includes soft handover traffic and excludes RLC headers.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
t.PLMN.RNC
WRFD-170202
TCP Proxy

41
BSC6900 UMTS
Equivalent Erlang of AMR Services Using Crystal Voice in Deep Coverage for RNC
(per Operator)
Counters
Counter ID
Counter Name
Counter Description
73446319
VS.AMR.CrstVoiceDeepCo
ver.Erlang.Equiv.PLMN.RN
C
Equivalent Erlang of AMR

Services Using Crystal Voice
in Deep Coverage for RNC
(per Operator)
Description
This counter provides the equivalent Erlang of CS AMR services (AMR-WB and AMR-NB)
that use the Crystal Voice in Deep Coverage feature of an operator on an RNC. This counter
applies only to the scenario where the RAN sharing or MOCN feature is enabled. This counter
does not apply to the UEs whose best cells are under the DRNC.
Measurement point
The system samples the equivalent Erlang of CS AMR services that use the Crystal Voice in
Deep Coverage feature every five seconds of an operator on the RNC in a measurement period.
At the end of the measurement period, the system obtains the value of this counter by dividing
the accumulated value by the number of times sampled. The counter value includes the
equivalent Erlang on all links during soft handovers.When a CS AMR service is being
established and the Crystal Voice in Deep Coverage feature is enabled, the service rate of the
CS AMR service is converted to the equivalent Erlang, which is then calculated into this counter.
When a CS AMR service is being released or this feature is disabled for a CS AMR service, the
service rate is converted to the equivalent Erlang, which is then subtracted from this counter.
Formula
None
Unit
Erl
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ver.Erlang.Equiv.PLMN.RN
C
WRFD-171201
Crystal Voice in Deep

Coverage

42
BSC6900 UMTS
Maximum Equivalent Erlang of AMR Services Using Crystal Voice in Deep

Coverage for RNC (per Operator)
Counters
Counter ID
Counter Name
Counter Description
73430145
ver.MaxErlang.Equiv.PLM
N.RNC

of AMR Services Using
Coverage for RNC (per
Operator)
Description
(AMR-WB and AMR-NB voice services) that use the Crystal Voice in Deep Coverage feature
of an operator in an RNC. This counter applies only to the scenario where the RAN sharing or
MOCN feature is enabled. This counter does not apply to the UEs whose best cells are under
the DRNC.
Measurement point
Deep Coverage feature every five seconds of an operator on the RNC in a measurement period.
At the end of the measurement period, the system obtains the maximum equivalent Erlang of
AMR services using Crystal Voice in Deep Coverage.The counter value includes the equivalent
Erlang on all links during soft handovers.When a CS AMR service is being established and the
Crystal Voice in Deep Coverage feature is enabled, the service rate of the CS AMR service is
converted to the equivalent Erlang, which is then calculated into this counter. When a CS AMR
service is being released or this feature is disabled for a CS AMR service, the service rate is
converted to the equivalent Erlang, which is then subtracted from this counter.
Formula
None
Unit
Erl
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ver.MaxErlang.Equiv.PLM
N.RNC
WRFD-171201

Coverage

43
BSC6900 UMTS
Traffic of Video Services based on RAN-Initiated Service Awareness for RNC (per
Operator)
Counters
Counter ID
Counter Name
Counter Description
73446340
VS.RadioAwaredVideo.Thr
uput.PLMN.RNC
Traffic of Video Services

based on RAN-Initiated
Service Awareness for RNC
(per Operator)
Description
This counter provides the amount of traffic of uplink and downlink video services based on
RAN-initiated service awareness for an operator on the RNC.This counter is measured only
when the video service measurement function is enabled together with the RAN sharing or
MOCN feature. For details about the video service measurement function, see Radio-Aware
Video Precedence Feature Parameter Description.
Measurement point
The system samples the traffic (unit: kbit/s) of uplink and downlink video services based on
RAN-initiated service awareness every 5s in a measurement period. At the end of the
measurement period, the system divides the accumulated traffic by the number of times sampled
to obtain the traffic of uplink and downlink video services based on RAN-initiated service
awareness in this measurement period. This counter is measured on a per operator basis. The
traffic of video services is measured at the RLC layer, including the traffic of retransmitted video
packets and the video traffic of UEs during soft handovers and excluding RLC headers.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
uput.PLMN.RNC
WRFD-171210
Radio-Aware Video
Precedence

44
BSC6900 UMTS
1.2 Measurement of CPUS Subsystem 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/SPUc board has eight subsystems. In addition, an
SPUa subsystem and an SPUb/SPUc subsystem have different processing capabilities.
The CPUS measurement is performed only to assess the performance of a single CPUS
subsystem.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
CPUS
CPUS Subsystem Measurement
1.2.1 CPUS Subsystem Measurement(CPUS)

Overview
The CPUS subsystem measurement provides the performance of a single CPUS in terms of the
number of setup and release times of different services, and the number of times that each type
of messages are discarded due to flow control.
If the value of a flow control-related counter increases dramatically in a period, check whether
a signaling storm has occurred in the corresponding period.
Issue 03 (2015-06-30)

45
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203413
VS.CSLoad.Erlang
.Equiv.CPUS
Equivalent CS
Conversational
Erlang for CPUS
Earlier than
BSC6900
V900R011
67193077
VS.RRC.AttConnE
stab.CPUS
Number of RRC
Connection Requests
for CPUS
Earlier than
BSC6900
V900R011
67193078
VS.RRC.SuccConn
Estab.CPUS
Number of
Successful RRC
Connection
Establishments for
CPUS
Earlier than
BSC6900
V900R011
67193079
VS.RAB.AttEstab.
AMR.CPUS
Number of CS AMR
RAB Establishing
Requests for CPUS
Earlier than
BSC6900
V900R011
67193080
VS.RAB.SuccEstab
.AMR.CPUS
Number of CS AMR
RABs Successfully
Established for
CPUS
Earlier than
BSC6900
V900R011
67193081
VS.RAB.AttEstab.
CS64.CPUS
Number of CS
64kbit/s RAB
Establishing
Requests for CPUS
Earlier than
BSC6900
V900R011
67193082
VS.RAB.SuccEstab
.CS64.CPUS
Number of CS
64kbit/s RABs
Successfully
Established for
CPUS
Earlier than
BSC6900
V900R011
67193083
VS.HSDPA.RAB.A
ttEstab.CPUS
Number of HSDPA
RAB Establishing
Requests for CPUS
Earlier than
BSC6900
V900R011
67193084
VS.HSDPA.RAB.S
uccEstab.CPUS
Number of HSDPA
RABs Successfully
Established for
CPUS
Earlier than
BSC6900
V900R011
67193085
VS.HSUPA.RAB.A
ttEstab.CPUS
Number of HSUPA
RAB Establishing
Requests for CPUS
Earlier than
BSC6900
V900R011

46
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193086
VS.HSUPA.RAB.S
uccEstab.CPUS
Number of HSUPA
RABs Successfully
Established for
CPUS
Earlier than
BSC6900
V900R011
67193087
VS.RAB.AttEstabP
S.CPUS
Number of PS RAB
Establishing
Requests for CPUS
Earlier than
BSC6900
V900R011
67193088
VS.RAB.SuccEstab
PS.CPUS
Number of PS RABs
Successfully
Established for
CPUS
Earlier than
BSC6900
V900R011
67193089
VS.RAB.AbnormR
el.AMR.CPUS
Number of
Abnormally
Released CS AMR
RABs for CPUS
Earlier than
BSC6900
V900R011
67193090
VS.RAB.NormRel.
AMR.CPUS
Number of Normally
Released CS AMR
RABs for CPUS
Earlier than
BSC6900
V900R011
67193091
VS.RAB.AbnormR
el.CS64.CPUS
Number of
Abnormally
Released CS 64kbit/s
RABs for CPUS
Earlier than
BSC6900
V900R011
67193092
VS.RAB.NormRel.
CS64.CPUS
Number of Normally
Released CS 64kbit/s
RABs for CPUS
Earlier than
BSC6900
V900R011
67193093
VS.RAB.AbnormR
el.PS.CPUS
Number of
Abnormally
Released PS RABs
for CPUS
Earlier than
BSC6900
V900R011
67193094
VS.RAB.NormRel.
PS.CPUS
Number of Normally
Released PS RABs
for CPUS
Earlier than
BSC6900
V900R011
73421896
VS.CBS.FC.Disc.N
um.CPUS
Number of CBS
Requests Discarded
Due to Flow Control
for CPUS Subsystem
BSC6900
V900R012
73421897
VS.CBS.FC.Disc.Ti
me.CPUS
Duration of CBS
Flow Control for
CPUS Subsystem
BSC6900
V900R012

47
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421898
VS.Paging.FC.Disc.
Num.CPUS
Number of Paging
Messages Discarded
Due to Flow Control
for CPUS Subsystem
BSC6900
V900R012
73421899
VS.Paging.FC.Disc.
Time.CPUS
Duration of Paging
Message Flow
Control for CPUS
Subsystem
BSC6900
V900R012
73421900
VS.CU.FC.Disc.Nu
m.CPUS
Number of Cell
Update Requests
Discarded Due to
Flow Control for
CPUS Subsystem
BSC6900
V900R012
73421901
VS.CU.FC.Disc.Ti
me.CPUS
Duration of Cell
Update Flow Control
for CPUS Subsystem
BSC6900
V900R012
73423464
VS.RRC.FC.Disc.N
um.CallShock.CPU
S
Number of
Discarded RRC
Connection Requests
Due to Burst Traffic
for CPUS Subsystem
BSC6900
V900R013
73423465
VS.RRC.FC.Disc.N
um.MPU.CPUS
Number of
Discarded RRC
Connection Requests
Due to MPU
Overload for CPUS
Subsystem
BSC6900
V900R013
73423466
VS.RRC.FC.Disc.N
um.RRCQueue.CP
US
Number of
Discarded RRC
Connection Requests
Due to RRC Queue
Overflow for CPUS
Subsystem
BSC6900
V900R013
73423467
VS.RRC.FC.Disc.N
um.CPU.CPUS
Number of
Discarded RRC
Connection Requests
Due to High CPU
Usage for CPUS
Subsystem
BSC6900
V900R013

48
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421890
VS.LowPriRRC.F
C.Disc.Num.CPUS
Number of LowPriority RRC

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

Requests Discarded
Due to Flow Control
for CPUS Subsystem
BSC6900
V900R012
73421892
VS.HighPriRRC.F
C.Disc.Num.CPUS
Number of HighPriority RRC

Requests Discarded
Due to Flow Control
for CPUS Subsystem
BSC6900
V900R012
73421893
VS.LowPriRRC.F
C.Disc.Time.CPUS
Duration of
Rejection of LowPriority RRC
Requests Due to
Flow Control for
CPUS Subsystem
BSC6900
V900R012
73421894
VS.NormPriRRC.F
C.Disc.Time.CPUS
Duration of
Rejection of NormalPriority RRC
Requests Due to
Flow Control for
CPUS Subsystem
BSC6900
V900R012
73421895
VS.HighPriRRC.F
C.Disc.Time.CPUS
Duration of
Rejection of HighPriority RRC
Requests Due to
Flow Control for
CPUS Subsystem
BSC6900
V900R012
73423921
VS.LowPriCu.FC.
Disc.Num.CPU
Number of LowPriority CELL

UPDATE Messages
Discarded Because
CPU Usage Exceeds
the Threshold for
CPUS Subsystem
BSC6900
V900R014

49
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423923
VS.MidPriCu.FC.
Disc.Num.CPU
Number of MediumPriority CELL

UPDATE Messages
Discarded Because
CPU Usage Exceeds
the Threshold for
CPUS Subsystem
BSC6900
V900R014
73423924
VS.HighPriCu.FC.
Disc.Num.CPU
Number of HighPriority CELL

UPDATE Messages
Discarded Because
CPU Usage Exceeds
the Threshold for
CPUS Subsystem
BSC6900
V900R014
73423925
VS.LowPriCu.FC.
Disc.Num.Queue
Number of LowPriority CELL

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

UPDATE Messages
Discarded Due to
RRC Queue
Overflow for CPUS
Subsystem
BSC6900
V900R014
73423927
VS.HighPriCu.FC.
Disc.Num.Queue
Number of HighPriority CELL

UPDATE Messages
Discarded Due to
RRC Queue
Overflow for CPUS
Subsystem
BSC6900
V900R014
73423928
VS.Traffic.Report4
A.CellDch.Disc.Nu
m.UpLink.FC
Number of
Discarded UL Event
4A Measurement
Reports on PS BE
Traffic in the
CELL_DCH State in
a CPUS
BSC6900
V900R014

50
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423929
VS.Traffic.Report4
A.CellDch.Disc.Nu
m.DownLink.FC
Number of
Discarded DL Event
4A Measurement
Reports on PS BE
Traffic in the
CELL_DCH State in
a CPUS
BSC6900
V900R014
73423930
VS.Throughput.Re
port4A.Disc.Num.
UpLink.FC
Number of
Discarded UL Event
4A Measurement
Reports on
Throughput for UEs
in the CELL_DCH
State in a CPUS
BSC6900
V900R014
73423931
VS.Traffic.Report4
A.CellFach.Disc.Nu
m.UpLink.FC
Number of
Discarded UL Event
4A Measurement
Reports on PS BE
Traffic in the
CELL_FACH State
in a CPUS
BSC6900
V900R014
73423932
VS.Traffic.Report4
A.CellFach.Disc.Nu
m.DownLink.FC
Number of
Discarded DL Event
4A Measurement
Reports on PS BE
Traffic in the
CELL_FACH State
in a CPUS
BSC6900
V900R014
73424215
VS.RRC.FC.Num.
CPU.CPUS
Number of RRC
CONNECTION
REQUESTS Under
Flow Control Due to
High CPU Usage for
CPUS Subsystem
BSC6900
V900R014
73424216
VS.RRC.FC.Num.
RRCQueue.CPUS
Number of RRC
CONNECTION
REQUESTS Under
Flow Control Due to
RRC Queue
Overflow for CPUS
Subsystem
BSC6900
V900R014

51
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424217
VS.RRC.FC.Num.
MPU.CPUS
Number of RRC
CONNECTION
REQUESTS Under
Flow Control Due to
MPU Overload for
CPUS Subsystem
BSC6900
V900R014
73424218
VS.RRC.FC.Num.
CallShock.CPUS
Number of RRC
CONNECTION
REQUESTS Under
Flow Control Due to
Burst Traffic for
CPUS Subsystem
BSC6900
V900R014
73424219
VS.RRC.CONV.F
C.Num.CPU.CPUS
Number of RRC
CONNECTION
REQUESTS for CS
Services Under Flow
Control Due to High
CPU Usage for
CPUS Subsystem
BSC6900
V900R014
73424220
VS.RRC.CONV.F
C.Num.RRCQueue
.CPUS
Number of RRC
CONNECTION
REQUESTS for CS
Services Under Flow
Control Due to RRC
Queue Overflow for
CPUS Subsystem
BSC6900
V900R014
73424221
VS.RRC.CONV.F
C.Num.MPU.CPU
S
Number of RRC
CONNECTION
REQUESTS for CS
Services Under Flow
Control Due to MPU
Overload for CPUS
Subsystem
BSC6900
V900R014
73424222
VS.RRC.CONV.F
C.Num.CallShock.
CPUS
Number of RRC
CONNECTION
REQUESTS for CS
Services Under Flow
Control Due to Burst
Traffic for CPUS
Subsystem
BSC6900
V900R014

52
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424482
VS.RRC.CONV.F
C.Num.INT.CPUS
Number of RRC
CONNECTION
REQUESTS for CS
Services in a CPUS
Subsystem Under
Flow Control
Triggered by
Interface-Board CPU
Overload
BSC6900
V900R014
73424483
VS.RRC.FC.Num.I
NT.CPUS
Number of RRC
CONNECTION
REQUESTS in a
CPUS Subsystem
Under Flow Control
Triggered by
Interface-Board CPU
Overload
BSC6900
V900R014
73424484
VS.IurUpLinkSig.
Disc.Num.CPU.CP
US
Number of
Discarded IurInterface Uplink
Signalling Messages
in a CPUS
Subsystem Under
Flow Control
Triggered by CPU
Overload
BSC6900
V900R014
73424485
VS.IurDownLinkSi
g.Disc.Num.CPU.C
PUS
Number of
Discarded IurInterface Downlink
Signalling Messages
in a CPUS
Subsystem Under
Flow Control
Triggered by CPU
Overload
BSC6900
V900R014
73428945
VS.IRATHO.AttRe
locPrepInCS.FC.R
ej.Num.CPUS
Number of Rejected
Preparation
Attempts for
Incoming Inter-RAT
CS Handovers due to
Flow Control for
CPUS Subsystem
BSC6900
V900R016C00

53
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428946
VS.IRATHO.AttRe
locPrepInPS.FC.Re
j.Num.CPUS
Number of Rejected
Preparation
Attempts for
Incoming Inter-RAT
PS Handovers due to
Flow Control for
CPUS Subsystem
BSC6900
V900R016C00
73430295
VS.SHO.FC.Num.
CPU.CPUS
Number of Soft
Handovers
Discarded in Flow
Control Due to High
CPU Usage of A
CPUS Subsystem
BSC6900
V900R017C10
The Counter greater than the sum of its Sub Counters
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
Measurement of CS-Domain Equivalent Erlang of Each Subsystem in the RNC

Counters
Counter ID
Counter Name
Counter Description
67203413
VS.CSLoad.Erlang.Equiv.C
PUS
Equivalent CS
Conversational Erlang for
CPUS
Description
This measurement counter provides the equivalent Erlang of all CS-domain services of each
subsystem in the RNC.
Issue 03 (2015-06-30)

54
BSC6900 UMTS
Measurement point
The RNC takes samples on the equivalent Erlang of all CS-domain services of each subsystem
in the RNC every five seconds. At the end of the measurement period, the RNC divides the
accumulated value of all sampling data in the measurement period by the number of sampling
times to obtain the equivalent Erlang of all CS-domain services of each subsystem in the RNC,
include the equivalent Erlang of all radio links of Soft Handover.When a CS-domain service
accesses the RNC, the service rate is converted into equivalent Erlang, and then the CS-domain
equivalent Erlang of the corresponding subsystem in the current RNC is increased. When a CSdomain service is released from the RNC, the service rate is converted into equivalent Erlang,
and then the Erlang of the corresponding subsystem in the current RNC is decreased.
Formula
None
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
VS.CSLoad.Erlang.Equiv.C
PUS
WRFD-040100
Flow Control
Number of RRC Connection Requests in the CPUS subsystem

Counters
Counter ID
Counter Name
Counter Description
67193077
VS.RRC.AttConnEstab.CP
US
Number of RRC Connection

Requests for CPUS
Description
This measurement counter provides the number of RRC CONNECTION REQUEST messages
processed by the RNC in the CPUS subsystem, excluding cases that such request is rejected
because of redirection based on specific services, redirection based on inter-RAT and interfrequency distance, redirection based on weakcoverage, redirection based on macro & micro
joint inter-frequency, or UE capability-based inter-frequency redirection.This counter does not
include the RRC connection setup requests in the Directed Signalling Connection Reestablishment (DSCR) procedure triggered by the overlapping of the RRC connection setup
procedure and cell update procedure.This counter complies with section "8.1.3 RRC connection
establishment" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

55
BSC6900 UMTS
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. This
counter excludes the number of rejected RRC connection requests caused by service-based
redirection, inter-RAT and inter-frequency distance-based redirection, weakcoverage-based
redirection, macro & micro joint inter-frequency redirection, UE capability-based interfrequency redirection and the number of RRC connection requests discarded during flow control.
The measurement is triggered in the CPUS subsystem.This counter does not include the RRC
connection setup requests in the Directed Signalling Connection Re-establishment (DSCR)
procedure triggered by the overlapping of the RRC connection setup procedure and cell update
procedure.
Figure 1-8 RRC connection setup process
Formula
None
Unit
None
Issue 03 (2015-06-30)

56
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnEstab.CP
US
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Successful RRC Connection Setups in the CPUS subsystem

Counters
Counter ID
Counter Name
Counter Description
67193078
VS.RRC.SuccConnEstab.C
PUS
Number of Successful RRC

Connection Establishments
for CPUS
Description
This measurement counter provides the number of RRC CONNECTION SETUP COMPLETE
messages received by the RNC in the CPUS subsystem.This counter complies with section "8.1.3
RRC connection establishment" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

57
BSC6900 UMTS
Figure 1-9 RRC connection setup process
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
PUS
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

58
BSC6900 UMTS
Number of CS RAB Requests in the CPUS subsystem

Counters
Counter ID
Counter Name
Counter Description
67193079
VS.RAB.AttEstab.AMR.CP
US
Number of CS AMR RAB

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

CPUS
67193083
VS.HSDPA.RAB.AttEstab.
CPUS
Number of HSDPA RAB

CPUS
67193085
VS.HSUPA.RAB.AttEstab.
CPUS
Number of HSUPA RAB

CPUS
67193087
VS.RAB.AttEstabPS.CPUS
Number of PS RAB
CPUS
Description
These measurement counters provide the number of RAB requests in the CPUS subsystem
according to the service type.The counter VS.RAB.AttEstab.AMR.CPUS includes narrowband
and wideband AMR services.The preceding counters comply with section "8.2 RAB
Counter Name
Description
VS.RAB.AttEstab.AMR.CPUS
Number of CS AMR RAB Establishing

Requests. Includeing narrowband and
wideband AMR services.
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.
Issue 03 (2015-06-30)

59
BSC6900 UMTS
Counter Name
Description
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.
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
Formula
None
Unit
None
Issue 03 (2015-06-30)

60
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstab.AMR.CP
US
WRFD-010501
VS.RAB.AttEstab.CS64.CP
US
WRFD-010501
CPUS
WRFD-01061008
Interactive and Background

Traffic Class on HSDPA
WRFD-010630
Streaming Traffic Class on

HSDPA
CPUS
WRFD-01061206
WRFD-010632

Traffic Class on HSUPA
HSUPA
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of CS RABs successfully established in the CPUS subsystem

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193080
VS.RAB.SuccEstab.AMR.C
PUS
Number of CS AMR RABs

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

CPUS
67193086
VS.HSUPA.RAB.SuccEstab
.CPUS
Number of HSUPA RABs

CPUS
67193088
VS.RAB.SuccEstabPS.CPU
S
Number of PS RABs
CPUS

61
BSC6900 UMTS
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.The preceding counters comply with section "8.2 RAB Assignment"
in 3GPP TS 25.413 (v10.10.0).
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
Formula
None
Unit
None
Issue 03 (2015-06-30)

62
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstab.AMR.C
PUS
WRFD-010501
VS.RAB.SuccEstab.CS64.C
PUS
WRFD-010501
.CPUS
WRFD-01061008

WRFD-010630

HSDPA
.CPUS
WRFD-01061206
WRFD-010632

HSUPA
VS.RAB.SuccEstabPS.CPU
S
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RABs Abnormally Released in the CPUS subsystem

Counters
Counter ID
Counter Name
Counter Description
67193089
CPUS
Released CS AMR RABs for
CPUS
67193091
CPUS
Released CS 64kbit/s RABs
for CPUS
67193093
VS.RAB.AbnormRel.PS.CP
US
Released PS RABs for CPUS
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.The
preceding counters comply with section "8.3 RAB Release Request" in 3GPP TS 25.413
(v10.10.0).
Issue 03 (2015-06-30)

63
BSC6900 UMTS
Measurement point
Connection Release", reference to 3GPP TS 25.413),the RNC measures the items by the service
type in the corresponding CPUS subsystem.
Issue 03 (2015-06-30)

64
BSC6900 UMTS
Issue 03 (2015-06-30)

65
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CPUS
WRFD-010501
CPUS
WRFD-010501
VS.RAB.AbnormRel.PS.CP
US
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RABs Normally Released in the CPUS subsystem

Counters
Counter ID
Counter Name
Counter Description
67193090
VS.RAB.NormRel.AMR.CP
US
Number of Normally
Released CS AMR RABs for
CPUS
67193092
VS.RAB.NormRel.CS64.CP
US
Number of Normally
Released CS 64kbit/s RABs
for CPUS
67193094
VS.RAB.NormRel.PS.CPU
S
Number of Normally
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
Issue 03 (2015-06-30)

66
BSC6900 UMTS
VS.RAB.NormRel.AMR.CPUS includes narrowband and wideband AMR services.The

preceding counters comply with section "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
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.
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.
Issue 03 (2015-06-30)

67
BSC6900 UMTS
Figure 1-16 RAB assignment release procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.AMR.CP
US
WRFD-010501
VS.RAB.NormRel.CS64.CP
US
WRFD-010501
VS.RAB.NormRel.PS.CPU
S
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

68
BSC6900 UMTS
Number of CBS Requests Discarded Due to Flow Control for CPUS Subsystem
Counters
Counter ID
Counter Name
Counter Description
73421896
VS.CBS.FC.Disc.Num.CPU
S
Number of CBS Requests

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

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421897
VS.CBS.FC.Disc.Time.CPU
S
Duration of CBS Flow


69
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
Counter Name
Feature ID
Feature Name
VS.CBS.FC.Disc.Time.CPU
S
WRFD-040100
Flow Control
Number of Paging Messages Discarded Due to Flow Control for CPUS Subsystem
Counters
Counter ID
Counter Name
Counter Description
73421898
VS.Paging.FC.Disc.Num.C
PUS
Number of Paging Messages

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.
Issue 03 (2015-06-30)

70
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging.FC.Disc.Num.C
PUS
WRFD-040100
Flow Control
Duration of Paging Message Flow Control for CPUS Subsystem

Counters
Counter ID
Counter Name
Counter Description
73421899
VS.Paging.FC.Disc.Time.C
PUS
Duration of Paging Message

Flow Control for CPUS
Subsystem
Description
This counter provides the duration of paging message flow control in the CPUS subsystem.
Measurement point
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
Issue 03 (2015-06-30)

71
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging.FC.Disc.Time.C
PUS
WRFD-040100
Flow Control
Number of Cell Update Requests Discarded Due to Flow Control for CPUS
Subsystem
Counters
Counter ID
Counter Name
Counter Description
73421900
Number of Cell Update

Requests Discarded Due to
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-040100
Flow Control

72
BSC6900 UMTS
Duration of Cell Update Flow Control for CPUS Subsystem

Counters
Counter ID
Counter Name
Counter Description
73421901
VS.CU.FC.Disc.Time.CPU
S
Duration of Cell Update

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
Counter Name
Feature ID
Feature Name
VS.CU.FC.Disc.Time.CPU
S
WRFD-040100
Flow Control
Number of Discarded RRC Connection Requests Due to Various Flow Control

Functions
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423464
VS.RRC.FC.Disc.Num.Call
Shock.CPUS
Number of Discarded RRC

Connection Requests Due to
Burst Traffic for CPUS
Subsystem

73
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73423465
VS.RRC.FC.Disc.Num.MP
U.CPUS

MPU Overload for CPUS
Subsystem
73423466
VS.RRC.FC.Disc.Num.RR
CQueue.CPUS

RRC Queue Overflow for
CPUS Subsystem
73423467
VS.RRC.FC.Disc.Num.CPU
.CPUS

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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Disc.Num.Call
Shock.CPUS
WRFD-040100
Flow Control

74
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Disc.Num.MP
U.CPUS
WRFD-040100
Flow Control
VS.RRC.FC.Disc.Num.RR
CQueue.CPUS
WRFD-040100
Flow Control
VS.RRC.FC.Disc.Num.CPU
.CPUS
WRFD-040100
Flow Control
Number of Various Priority RRC Requests Discarded Due to Flow Control for
CPUS Subsystem
Counters
Counter ID
Counter Name
Counter Description
73421890
VS.LowPriRRC.FC.Disc.Nu
m.CPUS
Number of Low-Priority
RRC Requests Discarded
Due to Flow Control for
CPUS Subsystem
73421891
VS.NormPriRRC.FC.Disc.N
um.CPUS
Number of Normal-Priority
CPUS Subsystem
73421892
VS.HighPriRRC.FC.Disc.N
um.CPUS
Number of High-Priority
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. The preceding counters comply
with section "10.2.36 RRC CONNECTION REJECT" in 3GPP TS 25.331 (v12.1.0).
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
REJECT message. Otherwise, the RNC discards the RRC CONNECTION REQUEST message
Issue 03 (2015-06-30)

75
BSC6900 UMTS
directly and measures the number of discarded RRC connection requests for the corresponding
service priority.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LowPriRRC.FC.Disc.Nu
m.CPUS
WRFD-040100
Flow Control
VS.NormPriRRC.FC.Disc.N
um.CPUS
WRFD-040100
Flow Control
VS.HighPriRRC.FC.Disc.N
um.CPUS
WRFD-040100
Flow Control
Duration of Rejection of Various Priority RRC Requests Due to Flow Control for
CPUS Subsystem
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421893
VS.LowPriRRC.FC.Disc.Ti
me.CPUS
Duration of Rejection of
Low-Priority RRC Requests
CPUS Subsystem
73421894
VS.NormPriRRC.FC.Disc.T
ime.CPUS
Normal-Priority RRC
Requests Due to Flow
73421895
VS.HighPriRRC.FC.Disc.Ti
me.CPUS
High-Priority RRC Requests
CPUS Subsystem

76
BSC6900 UMTS
Description
These counters provide the duration for which the RRC connection requests of various priorities
are rejected because of flow control. The preceding counters comply with section "10.2.36 RRC
CONNECTION REJECT" in 3GPP TS 25.331 (v12.1.0).
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
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.LowPriRRC.FC.Disc.Ti
me.CPUS
WRFD-040100
Flow Control
VS.NormPriRRC.FC.Disc.T
ime.CPUS
WRFD-040100
Flow Control
VS.HighPriRRC.FC.Disc.Ti
me.CPUS
WRFD-040100
Flow Control
Number of Various Priority CELL_UPDATE Messages Discarded Because CPU

Usage Exceeds the Threshold in a CPUS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423921
VS.LowPriCu.FC.Disc.Num
.CPU
CELL UPDATE Messages
Discarded Because CPU
Usage Exceeds the Threshold
for CPUS Subsystem

77
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73423923
VS.MidPriCu.FC.Disc.Num
.CPU
Number of Medium-Priority
for CPUS Subsystem
73423924
VS.HighPriCu.FC.Disc.Nu
m.CPU
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). The preceding counters comply with section
"10.2.7 CELL UPDATE" in 3GPP TS 25.331 (v12.1.0).
The following table lists the disuse statements.
Issue 03 (2015-06-30)
Counter Name
Disuse Statement
VS.LowPriCu.FC.Disc.Num.CPU
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.
VS.MidPriCu.FC.Disc.Num.CPU

73424232) and

78
BSC6900 UMTS
Counter Name
Disuse Statement
VS.HighPriCu.FC.Disc.Num.CPU

73424232) and
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
Formula
None
Issue 03 (2015-06-30)

79
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.CPU
WRFD-040100
Flow Control
.CPU
WRFD-040100
Flow Control
m.CPU
WRFD-040100
Flow Control
Number of Various Priority CELL_UPDATE Messages Discarded Due to Queuebased Shaping in a CPUS
Counters
Counter ID
Counter Name
Counter Description
73423925
.Queue
Discarded Due to RRC
Queue Overflow for CPUS
Subsystem
73423926
.Queue
Number of Medium-Priority
Subsystem
73423927
m.Queue
Subsystem
Description
These counters provide the number of CELL_UPDATE messages discarded due to queue-based
shaping in a CPU subsystem (CPUS). The preceding counters comply with section "10.2.7 CELL
UPDATE" in 3GPP TS 25.331 (v12.1.0).
The following table lists the disuse statements.
Issue 03 (2015-06-30)

80
BSC6900 UMTS
Counter Name
Disuse Statement
VS.LowPriCu.FC.Disc.Num.Queue

replaced by the counters:
VS.CU.FC.Num.RRCQueue (ID 73424919)
and VS.CU.CONV.FC.Num.RRCQueue (ID
VS.MidPriCu.FC.Disc.Num.Queue

VS.HighPriCu.FC.Disc.Num.Queue

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.
Issue 03 (2015-06-30)

81
BSC6900 UMTS
Figure 1-18 Flow Control on CELL_UPDATE Messages Due to Queue-based Shaping
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.Queue
WRFD-040100
Flow Control
.Queue
WRFD-040100
Flow Control
m.Queue
WRFD-040100
Flow Control

82
BSC6900 UMTS
Number of Discarded Event 4A Measurement Reports on PS BE Traffic in the

CELL_DCH State
Counters
Counter ID
Counter Name
Counter Description
73423928
VS.Traffic.Report4A.CellD
ch.Disc.Num.UpLink.FC
Number of Discarded UL
Event 4A Measurement
Reports on PS BE Traffic in
the CELL_DCH State in a
CPUS
73423929
ch.Disc.Num.DownLink.FC
Number of Discarded DL
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. The preceding counters
comply with section "14.4 Traffic Volume Measurements" in 3GPP TS 25.331 (v12.1.0).
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.
Issue 03 (2015-06-30)

83
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-040100
Flow Control
WRFD-040100
Flow Control

84
BSC6900 UMTS
Number of Discarded UL Event 4A Measurement Reports on Throughput for UEs

in the CELL_DCH State
Counters
Counter ID
Counter Name
Counter Description
73423930
VS.Throughput.Report4A.D
isc.Num.UpLink.FC
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. This counter
complies with section "11.1 Traffic volume measurement for dynamic radio bearer control" in
3GPP TS 25.321 (v11.5.0).
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
Issue 03 (2015-06-30)

85
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Throughput.Report4A.D
isc.Num.UpLink.FC
WRFD-040100
Flow Control
Number of Discarded Event 4A Measurement Reports on PS BE Traffic in the

CELL_FACH State
Counters
Counter ID
Counter Name
Counter Description
73423931
VS.Traffic.Report4A.CellFa
the CELL_FACH State in a
CPUS
73423932
Number of Discarded DL
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. The preceding
counters comply with section "14.4 Traffic Volume Measurements" in 3GPP TS 25.331
(v12.1.0).
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.
Issue 03 (2015-06-30)

86
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-040100
Flow Control
WRFD-040100
Flow Control

87
BSC6900 UMTS
Number of FlowControl RRC Connection Requests Due to FlowControl for CPUS

Subsystem
Counters
Counter ID
Counter Name
Counter Description
73424215
VS.RRC.FC.Num.CPU.CP
US
Number of RRC
CONNECTION
REQUESTS Under Flow
Control Due to High CPU
Usage for CPUS Subsystem
73424216
VS.RRC.FC.Num.RRCQue
ue.CPUS
Number of RRC
CONNECTION
REQUESTS Under Flow
Control Due to RRC Queue
Overflow for CPUS
Subsystem
73424217
VS.RRC.FC.Num.MPU.CP
US
Number of RRC
CONNECTION
REQUESTS Under Flow
Control Due to MPU
Overload for CPUS
Subsystem
73424218
VS.RRC.FC.Num.CallShoc
k.CPUS
Number of RRC
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
Issue 03 (2015-06-30)

88
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Num.CPU.CP
US
WRFD-040100
Flow Control
ue.CPUS
WRFD-040100
Flow Control
VS.RRC.FC.Num.MPU.CP
US
WRFD-040100
Flow Control
VS.RRC.FC.Num.CallShoc
k.CPUS
WRFD-040100
Flow Control
Number of FlowControl RT RRC Connection Requests Due to FlowControl for

CPUS Subsystem
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424219
VS.RRC.CONV.FC.Num.C
PU.CPUS
Number of RRC
CONNECTION
REQUESTS for CS Services
Under Flow Control Due to
High CPU Usage for CPUS
Subsystem
73424220
VS.RRC.CONV.FC.Num.R
RCQueue.CPUS
Number of RRC
CONNECTION
RRC Queue Overflow for
CPUS Subsystem
73424221
VS.RRC.CONV.FC.Num.M
PU.CPUS
Number of RRC
CONNECTION
MPU Overload for CPUS
Subsystem
73424222
allShock.CPUS
Number of RRC
CONNECTION
Burst Traffic for CPUS
Subsystem

89
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
Counter Name
Feature ID
Feature Name
PU.CPUS
WRFD-040100
Flow Control
RCQueue.CPUS
WRFD-040100
Flow Control
PU.CPUS
WRFD-040100
Flow Control
allShock.CPUS
WRFD-040100
Flow Control
Number of RRC CONNECTION REQUESTS for CS Services in a CPUS Subsystem

Under Flow Control Triggered by Interface-Board CPU Overload
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424482
VS.RRC.CONV.FC.Num.I
NT.CPUS
Number of RRC
CONNECTION
in a CPUS Subsystem Under
Flow Control Triggered by
Interface-Board CPU
Overload

90
BSC6900 UMTS
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.
requests for CS voice services during flow control caused by interface-board central processing
unit (CPU) overload in a CPU subsystem (CPUS).
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
NT.CPUS
WRFD-040100
Flow Control
Number of RRC CONNECTION REQUESTS in a CPUS Subsystem Under Flow

Control Triggered by Interface-Board CPU Overload
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424483
VS.RRC.FC.Num.INT.CPU
S
Number of RRC
CONNECTION
REQUESTS in a CPUS
Subsystem Under Flow
Control Triggered by
Interface-Board CPU
Overload

91
BSC6900 UMTS
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
This counter measures the number of rejected RRC connection setup requests during flow control
caused by interface-board CPU overload in a CPU subsystem (CPUS).
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Num.INT.CPU
S
WRFD-040100
Flow Control
Number of Discarded Iur-Interface Uplink Signalling Messages in a CPUS

Subsystem Under Flow Control Triggered by CPU Overload
Counters
Counter ID
Counter Name
Counter Description
73424484
VS.IurUpLinkSig.Disc.Num
.CPU.CPUS
Number of Discarded IurInterface Uplink Signalling

Messages in a CPUS
Subsystem Under Flow
Control Triggered by CPU
Overload
Description
This counter measures the number of discarded uplink signalling message during flow control
caused by central processing unit (CPU) overload in a CPU subsystem (CPUS).
Issue 03 (2015-06-30)

92
BSC6900 UMTS
Measurement point
This counter measures the number of discarded UPLINK SIGNALLING TRANSFER
INDICATION messages during flow control caused by central processing unit (CPU) overload
in a CPU subsystem (CPUS). The measurement is triggered when a CPUS receives an uplink
signalling message from a neighboring RNC and discards the message due to CPU overload in
the CPUS.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IurUpLinkSig.Disc.Num
.CPU.CPUS
WRFD-040100
Flow Control
Number of Discarded Iur-Interface Downlink Signalling Messages in a CPUS

Subsystem Under Flow Control Triggered by CPU Overload
Counters
Counter ID
Counter Name
Counter Description
73424485
VS.IurDownLinkSig.Disc.N
um.CPU.CPUS
Number of Discarded IurInterface Downlink

Signalling Messages in a
CPUS Subsystem Under
Flow Control Triggered by
CPU Overload
Description
This counter measures the number of discarded downlink signaling messages during flow control
caused by central processing unit (CPU) overload in a CPU subsystem (CPUS).
Measurement point
The measurement is triggered when a CPU subsystem (CPUS) receives any of the following
messages and discards the message due to CPU overload in the CPUS: RADIO LINK SETUP
REQUEST PAGING REQUEST COMMON TRANSPORT CHANNEL RESOURCES
Issue 03 (2015-06-30)

93
BSC6900 UMTS
REQUEST This counter measures the number of discarded downlink signaling messages during
flow control caused by central processing unit (CPU) overload in a CPUS.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IurDownLinkSig.Disc.N
um.CPU.CPUS
WRFD-040100
Flow Control
Number of Rejected Preparation Attempts for Incoming Inter-RAT CS Handovers

due to Flow Control for CPUS Subsystem
Counters
Counter ID
Counter Name
Counter Description
73428945
VS.IRATHO.AttRelocPrepI
nCS.FC.Rej.Num.CPUS
Number of Rejected
Preparation Attempts for
Incoming Inter-RAT CS
Handovers due to Flow
Description
This counter measures the number of rejected preparation attempts for incoming inter-RAT CS
handovers due to flow control in a CPUS subsystem.
Measurement point
After receiving a RELOCATION REQUEST message from the CS CN, the CPUS subsystem
determines whether the message is for incoming inter-RAT handover preparation attempts. If
so and the flow control function is started for incoming inter-RAT handovers, the RNC returns
a RELOCATION FAILURE to the CN and this counter is increased by one.
Formula
None
Issue 03 (2015-06-30)

94
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
nCS.FC.Rej.Num.CPUS
WRFD-040100
Flow Control
Number of Rejected Preparation Attempts for Incoming Inter-RAT PS Handovers

due to Flow Control for CPUS Subsystem
Counters
Counter ID
Counter Name
Counter Description
73428946
nPS.FC.Rej.Num.CPUS
Number of Rejected
Incoming Inter-RAT PS
Handovers due to Flow
Description
This counter measures the number of rejected preparation attempts for incoming inter-RAT PS
handovers due to flow control in a CPUS subsystem.
Measurement point
After receiving a RELOCATION REQUEST message from the PS CN, the CPUS subsystem
determines whether the message is for incoming inter-RAT handover preparation attempts. If
so and the flow control function is started for incoming inter-RAT handovers, the RNC returns
a RELOCATION FAILURE to the CN and this counter is increased by one.
Formula
None
Unit
None
Issue 03 (2015-06-30)

95
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
nPS.FC.Rej.Num.CPUS
WRFD-040100
Flow Control
Number of Soft Handovers Discarded in Flow Control Due to High CPU Usage of
A CPUS Subsystem
Counters
Counter ID
Counter Name
Counter Description
73430295
VS.SHO.FC.Num.CPU.CP
US
Number of Soft Handovers

Discarded in Flow Control
Due to High CPU Usage of A
CPUS Subsystem
Description
This counter measures the number of soft handovers (SHOs) discarded in flow control because
the CPU usage of a subsystem exceeds the flow control threshold.
Measurement point
When a subsystem receives a 1X measurement report from the UE, the RNC decides whether
to initiate an SHO procedure based on the SHO flow control algorithm if the subsystem is in the
SHO flow control state. If the RNC decides not to initiate an SHO procedure, this counter is
incremented by one.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.FC.Num.CPU.CP
US
WRFD-040100
Flow Control

96
BSC6900 UMTS
1.3 Measurement of GTP-U Performance(GTPU)

Overview
GTPU measurement (GTPU) is used to measure the general performance of data transfer
procedures of the GPRS Tunneling Protocol for User Plane (GTP-U). The GTPU measurement
consists of only one function subset.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
GTPU
GTP-U Measurement
1.3.1 GTP-U Measurement(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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67178509
VS.GTPU.Pkt.Tx
Number of UL
Packets Sent by
GTP-U
Earlier than
BSC6900
V900R011
67178512
VS.GTPU.Pkt.Rx
Number of DL
Packets Received by
GTP-U
Earlier than
BSC6900
V900R011
67199477
VS.GTPU.BytesPkt
.Tx
Number of UL Bytes
Sent by GTP-U
Earlier than
BSC6900
V900R011
67199478
VS.GTPU.BytesPkt
.Rx
Number of DL Bytes
Received by GTP-U
Earlier than
BSC6900
V900R011
67204158
VS.GTPU.PktNum
Conv.Tx
Number of UL
Session Service
Packets Sent by
GTPU
Earlier than
BSC6900
V900R011

97
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204159
VS.GTPU.PktNum
Conv.Rx
Number of DL
Session Service
Packets Received by
GTPU
Earlier than
BSC6900
V900R011
67204160
VS.GTPU.PktNum
Str.Tx
Number of UL
Streaming Service
Packets Sent by
GTPU
Earlier than
BSC6900
V900R011
67204161
VS.GTPU.PktNum
Str.Rx
Number of DL
Streaming Service
Packets Received by
GTPU
Earlier than
BSC6900
V900R011
67204162
VS.GTPU.PktNum
Int.Tx
Number of UL
Interactive Service
Packets Sent by
GTPU
Earlier than
BSC6900
V900R011
67204163
VS.GTPU.PktNum
Int.Rx
Number of DL
Interactive Service
Packets Received by
GTPU
Earlier than
BSC6900
V900R011
67204164
VS.GTPU.PktNum
Bkg.Tx
Number of UL
Background Service
Packets Sent by
GTPU
Earlier than
BSC6900
V900R011
67204165
VS.GTPU.PktNum
Bkg.Rx
Number of DL
Background Service
Packets Received by
GTP
Earlier than
BSC6900
V900R011
67192326
VS.GTPU.BytesMb
ms.Rx
Number of MBMS
Service Bytes
Received by GTP-U
Earlier than
BSC6900
V900R011
73424012
VS.GTPU.EchoRsp
.Tx
Number of Echo
Response Packets
Sent by the GTP-U
BSC6900
V900R014
73424013
VS.GTPU.EchoRsp
.Rx
Number of Echo
Response Packets
Received by the
GTP-U
BSC6900
V900R014
73424014
VS.GTPU.EchoRe
q.Tx
Number of Echo
Request Packets Sent
by the GTP-U
BSC6900
V900R014

98
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73424015
VS.GTPU.EchoRe
q.Rx
Number of Echo
Request Packets
Received by the
GTP-U
BSC6900
V900R014
73424016
VS.GTPU.ErrInd.
Tx
Number of Error
Indication Packets
Sent by the GTP-U
BSC6900
V900R014
73424017
VS.GTPU.ErrInd.
Rx
Number of Error
Indication Packets
Received by the
GTP-U
BSC6900
V900R014
the Counter greater than the sum of its Sub Counters
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
Number of UL Packets Sent by GTP-U

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67178509
VS.GTPU.Pkt.Tx
Number of UL Packets Sent

by GTP-U

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

Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)

100
BSC6900 UMTS
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.GTPU.Pkt.Rx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counter ID
Counter Name
Counter Description
67199477
VS.GTPU.BytesPkt.Tx
Number of UL Bytes Sent by

GTP-U
Number of UL Bytes Sent by GTP-U

Counters
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,the GTP-U header is not included.
Measurement point
This counter is incremented by one each time the RNC sends a data packet or control packet to
Formula
None
Unit
byte
Issue 03 (2015-06-30)

101
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.GTPU.BytesPkt.Tx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of DL Bytes Received by GTP-U

Counters
Counter ID
Counter Name
Counter Description
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,the GTP-U header is not included.
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.GTPU.BytesPkt.Rx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

102
BSC6900 UMTS
Counters Related to the Number of Service PDUs Sent by GTP-U

Counters
Counter ID
Counter Name
Counter Description
67204158
Number of UL Session
Service Packets Sent by
GTPU
67204160
Number of UL Streaming
GTPU
67204162
Number of UL Interactive
GTPU
67204164
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-010503
Interactive QoS Class
WRFD-010504
Background QoS Class

103
BSC6900 UMTS
Counters Related to the Number of Service PDUs Received by GTP-U

Counters
Counter ID
Counter Name
Counter Description
67204159
Number of DL Session
Service Packets Received by
GTPU
67204161
Number of DL Streaming
GTPU
67204163
Number of DL Interactive
GTPU
67204165
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-010503
WRFD-010504

104
BSC6900 UMTS
Number of MBMS or IMB Service Bytes Received by GTP-U

Counters
Counter ID
Counter Name
Counter Description
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
Counter Name
Feature ID
Feature Name
VS.GTPU.BytesMbms.Rx
WRFD-010616
MBMS Introduction
Package
Number of Echo Response Packets Sent by the GTP-U

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424012
VS.GTPU.EchoRsp.Tx
Number of Echo Response

Packets Sent by the GTP-U

105
BSC6900 UMTS
Description
This counter provides the number of Echo Response packets sent by the GTP-U on the RNC
side.
Measurement point
This counter is incremented by one each time the RNC sends an Echo Response packet to the
Formula
None
Unit
packet
Related Features
None
Number of Echo Response Packets Received by the GTP-U

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

106
BSC6900 UMTS
Related Features
None
Number of Echo Request Packets Sent by the GTP-U

Counters
Counter ID
Counter Name
Counter Description
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
Number of Echo Request Packets Received by the GTP-U

Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)

107
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
Number of Error Indication Packets Sent by the GTP-U

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

108
BSC6900 UMTS
Number of Error Indication Packets Received by the GTP-U

Counters
Counter ID
Counter Name
Counter Description
73424017
VS.GTPU.ErrInd.Rx

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
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
CS.SIG.IU
CS Signaling Measurement per Iu Interface
CS.TRF.IU
CS Traffic Measurement per Iu Interface
MBMS.IU
MBMS Measurement per Iu Interface

109
BSC6900 UMTS
FunctionSubSet
FunctionSubSet Name
MOCN.IU
MOCN Measurement per Iu Interface
NAS.IU
NAS Signaling Measurement per Iu Interface
PS.SIG.IU
PS Signaling Measurement per Iu Interface
PS.TRF.IU
PS Traffic Measurement per Iu Interface
SIG.SCCP.IU
SCCP Measurement per Iu Interface
1.4.1 CS Signaling Measurement per Iu Interface(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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67176449
VS.IU.ResetCS.Tx
Number of RESET
Messages Sent by
RNC to CN in CS
Domain
Earlier than
BSC6900
V900R011
67176453
VS.IU.ResetCS.Rx
Number of RESET
Messages Received
by RNC from CN in
CS Domain
Earlier than
BSC6900
V900R011
67189920
VS.IU.SIG.AttConnEstabCS
Number of INITIAL
UE MESSAGE
Messages Sent by
RNC to CN in CS
Domain
Earlier than
BSC6900
V900R011
67176546
VS.IU.RelReqCS.s
um
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in CS
Domain
Earlier than
BSC6900
V900R011

110
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67176552
VS.IU.RelCmdCS.s
um
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
CS Domain
Earlier than
BSC6900
V900R011
67176529
VS.IU.ErrInd.CS.T
x
Number of ERROR
INDICATION
Messages Sent by
RNC to CN in CS
Domain
Earlier than
BSC6900
V900R011
67176531
VS.IU.ErrInd.CS.
Rx
Number of ERROR
INDICATION
Messages Received
by RNC from CN in
CS Domain
Earlier than
BSC6900
V900R011
67176549
VS.IU.RelReqCS.I
ngChkFail
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in CS
Domain (Repeated
Integrity Checking
Failure)
Earlier than
BSC6900
V900R011
67176550
VS.IU.RelReqCS.Si
gConnRel
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in CS
Domain (UE
Signaling
Connection Release)
Earlier than
BSC6900
V900R011
67176551
VS.IU.RelReqCS.R
adConnUELost
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in CS
Domain (Radio
Connection With UE
Lost)
Earlier than
BSC6900
V900R011

111
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67176553
VS.IU.RelCmdCS.
RelocSucc
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
CS Domain
(Relocation Success)
Earlier than
BSC6900
V900R011
67176554
VS.IU.RelCmdCS.
NormRel
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
CS Domain (Normal
Release)
Earlier than
BSC6900
V900R011
67176555
VS.IU.RelCmdCS.
UTRANGen
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
CS Domain
(UTRAN Generated)
Earlier than
BSC6900
V900R011
67176556
VS.IU.RelCmdCS.
RelocCan
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
CS Domain
(Relocation
Cancelled)
Earlier than
BSC6900
V900R011
67176557
VS.IU.RelCmdCS.
NoRAB
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
CS Domain (No
Remaining RAB)
Earlier than
BSC6900
V900R011
67176573
VS.Iu.RelReqCS.R
IPFail
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in CS
Domain (Failure in
the Radio Interface
Procedure)
Earlier than
BSC6900
V900R011

112
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190182
VS.IU.RelReqCS.P
reempt
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in CS
Domain (RAB
Preempted)
Earlier than
BSC6900
V900R011
67192538
VS.IU.LdBalRtCS.
IMSI
Number of Times
that CS Load
Balancing is
Performed by IMSI
Users
Earlier than
BSC6900
V900R011
67192539
VS.IU.LdBalRtCS.
InValidNRI
Number of Times
that CS Load
Balancing is
Performed by TMSI
Users Due to Invalid
NRI
Earlier than
BSC6900
V900R011
67192540
VS.IU.LdBalRtCS.
IMEI
Number of Times
that CS Load
Balancing is
Performed by IMEI
Users
Earlier than
BSC6900
V900R011
67193095
VS.IU.FlowCtrl.Dis
cInitDT.CS
Number of
Discarded CS Initial
UE Messages when
Signaling Flow
Control is Triggered
Earlier than
BSC6900
V900R011
67196234
VS.IU.RelReqCS.N
etworkOpt
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in CS
Domain (VP
Forbiddance)
Earlier than
BSC6900
V900R011
73424970
VS.IU.CS.Paging
Number of Paging
Messages Received
by RNC from CN in
CS Domain
BSC6900
V900R014

113
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73425021
VS.IU.RanInfoReq.
Rx
Number of RAN
INFORMATION
REQUEST
Messages Received
by RNC from CN
BSC6900
V900R014
73425022
VS.IU.RanInfo.Tx
Number of RAN
INFORMATION
Messages Sent by
RNC to CN
BSC6900
V900R014
73430073
VS.IU.FlowCtrl.Dis
cInitDT.CS.CNRANAPOverLoad
Number of CS Initial
Direct Transfer
Messages Discarded
by RNC When the
CN RANAP is
overloaded
BSC6900
V900R017C10
None
Number of RESET Messages Initiated by RNC to CS Domain

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.26.2.2
Reset Procedure Initiated from the UTRAN" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

114
BSC6900 UMTS
Figure 1-22 CS domain reset procedure initiated by the RNC (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.ResetCS.Tx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RESET Messages Received by RNC from CS Domain

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67176453
VS.IU.ResetCS.Rx

Received by RNC from CN
in CS Domain

115
BSC6900 UMTS
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.This counter complies with section
"8.26.2.1 Reset Procedure Initiated from the CN" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC receives a
RESET message from the CS domain, it measures this counter.
Figure 1-23 CS domain reset procedure initiated by the CN (successful operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.ResetCS.Rx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

116
BSC6900 UMTS
Number of INITIAL UE MESSAGE Messages from RNC to CS Domain

Counters
Counter ID
Counter Name
Counter Description
67189920
Number of INITIAL UE
MESSAGE Messages Sent
by RNC to CN in CS Domain
Description
This measurement counter takes statistics of the number of INITIAL UE MESSAGE messages
that the RNC sends to the CS domain. The RNC measures this counter according to the CN
nodes.This counter complies with section "8.22 Initial UE Message" in 3GPP TS 25.413
(v10.10.0).
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
Formula
None
Unit
None
Issue 03 (2015-06-30)

117
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of IU RELEASE REQUEST Messages from RNC to CS Domain

Counters
Counter ID
Counter Name
Counter Description
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.This counter
complies with section "8.4 Iu Release Request" in 3GPP TS 25.413 (v10.10.0).
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.
Figure 1-25 Iu release procedure (successful operation)
Issue 03 (2015-06-30)

118
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RelReqCS.sum
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of IU RELEASE COMMAND Messages from CS Domain to RNC

Counters
Counter ID
Counter Name
Counter Description
67176552
VS.IU.RelCmdCS.sum
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.This counter complies with section "8.5 Iu Release" in 3GPP TS 25.413
(v10.10.0).
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.
Issue 03 (2015-06-30)

119
BSC6900 UMTS
The measurement is triggered at point A as shown in the figure. In the CN-initiated Iu release
the RNC measures this counter.
Figure 1-27 Iu release procedure initiated by the CN (successful operation)
Formula
None
Issue 03 (2015-06-30)

120
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RelCmdCS.sum
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of ERROR INDICATION Messages from RNC to CS Domain

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.27 Error Indication" in 3GPP TS 25.413 (v10.10.0).
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
Issue 03 (2015-06-30)

121
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.ErrInd.CS.Tx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of ERROR INDICATION Messages from CS Domain to RNC

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section
"8.27 Error Indication" in 3GPP TS 25.413 (v10.10.0).
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.
Figure 1-29 Error indication procedure initiated by the CN
Issue 03 (2015-06-30)

122
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.ErrInd.CS.Rx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of IU RELEASE REQUEST Messages from RNC to CS Domain for

Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67176549
VS.IU.RelReqCS.IngChkFail
(Repeated Integrity
Checking Failure)
67176550
VS.IU.RelReqCS.SigConnRel
(UE Signaling Connection
Release)
67176551
VS.IU.RelReqCS.RadConnUELost
(Radio Connection With UE
Lost)
67176573
VS.Iu.RelReqCS.RIPFail
(Failure in the Radio
Interface Procedure)

123
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67190182
VS.IU.RelReqCS.Preempt
(RAB Preempted)
67196234
VS.IU.RelReqCS.NetworkOpt
(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.The preceding counters comply with section "8.4 Iu Release Request" in
3GPP TS 25.413 (v10.10.0).
Measurement point
RELEASE REQUEST message to the CS domain, it measures these counters according to
different causes.
Issue 03 (2015-06-30)

124
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RelReqCS.IngChkFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelReqCS.SigConnRel
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelReqCS.RadConnUELost
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
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.NetworkOpt
WRFD-020130
Videophone Service
Restriction

125
BSC6900 UMTS
Number of IU RELEASE COMMAND Messages from CS Domain to RNC for

Different Causes
Counters
Counter ID
Counter Name
Counter Description
67176553
VS.IU.RelCmdCS.RelocSucc
COMMAND Messages
in CS Domain (Relocation
Success)
67176554
VS.IU.RelCmdCS.NormRel
COMMAND Messages
in CS Domain (Normal
Release)
67176555
VS.IU.RelCmdCS.UTRANGen
COMMAND Messages
in CS Domain (UTRAN
Generated)
67176556
VS.IU.RelCmdCS.RelocCan
COMMAND Messages
in CS Domain (Relocation
Cancelled)
67176557
VS.IU.RelCmdCS.NoRAB
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.The preceding counters comply with section "8.5 Iu Release" in 3GPP TS 25.413
(v10.10.0).
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.
Issue 03 (2015-06-30)

126
BSC6900 UMTS
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.
Formula
None
Issue 03 (2015-06-30)

127
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RelCmdCS.RelocSucc
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelCmdCS.NormRel
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelCmdCS.UTRANGen
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelCmdCS.RelocCan
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelCmdCS.NoRAB
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Load Balancing of the MSC Pool on the CS Domain

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192538
VS.IU.LdBalRtCS.IMSI
Number of Times that CS

Load Balancing is Performed
by IMSI Users
67192539
VS.IU.LdBalRtCS.InValidNRI

by TMSI Users Due to
Invalid NRI
67192540
VS.IU.LdBalRtCS.IMEI

by IMEI Users

128
BSC6900 UMTS
Description
The measurement counters provide the number of times that the UEs perform load balancing on
the CS domain during CN node selection when the RNC processes the initial direct transfer
message.The preceding counters comply with section "4.5 Load Balancing" in 3GPP TS 23.236
(v10.3.0).
Counter Name
Description
Number of times that the CS CN is selected

for load balancing by using the IMSI route
parameter.
Number of times that load balancing is

triggered due to invalid NRI route parameter,
connection failure to the CN node
corresponding to the route parameter, or the
flow control of the CN node corresponding to
the route parameter.
Number of times that the 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
Issue 03 (2015-06-30)

129
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-021306
Iu Flex Load Distribution

Management
WRFD-021306

Management
WRFD-021306

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

Domain)
Counters
Counter ID
Counter Name
Counter Description
67193095
VS.IU.FlowCtrl.DiscInitDT.
CS
Number of Discarded CS
Initial UE Messages when
Signaling Flow Control is
Triggered
Description
This measurement counter provides the number of initial UE messages discarded under the flow
control when the RNC receives the CS initial direct transfer messages.
Measurement point
The measurement is triggered when the RNC receives an INITIAL DIRECT TRANSFER
message from a UE and then discards this message because the RNC finds that the Iu-CS
interface is under flow control, as shown by point A in the following figure. After that, the RNC
does not send the INITIAL UE MESSAGE to the CN.
Figure 1-34 Process of discarding INITIAL DIRECT TRANSFER message
Issue 03 (2015-06-30)

130
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CS
WRFD-040100
Flow Control
Number of Paging Messages Received by RNC from CN in CS Domain

Counters
Counter ID
Counter Name
Counter Description
73424970
VS.IU.CS.Paging

in CS Domain
Description
This counter provides the number of PAGING messages that the RNC receives from the CS
domain based on the corresponding CN node.This counter complies with section "8.15 Paging"
in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

131
BSC6900 UMTS
Figure 1-35 Paging messages sent from the CN to the UE
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.CS.Paging
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-010302
Paging UE in CELL_FACH,
CELL_DCH State (Type 2)
Number of RAN INFORMATION REQUEST Messages Received by RNC from

CN
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425021
VS.IU.RanInfoReq.Rx
Number of RAN
INFORMATION
REQUEST Messages

132
BSC6900 UMTS
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.This counter complies with section "8.34.2.2 Direct Information
Transfer initiated from the CN" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure. This counter is incremented by
one each time the RNC receives a RANAP DERECT INFORMATION TRANSER message
whose type is RAN INFORMATION REQUEST.
Figure 1-36 Procedure for directly sending messages over the Iu interface
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RanInfoReq.Rx
WRFD-140224
Fast CS Fallback Based on

RIM
WRFD-150231
RIM Based UMTS Target

Cell Selection for LTE
Issue 03 (2015-06-30)

133
BSC6900 UMTS
Number of RAN INFORMATION Messages Sent by RNC to CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.34.2.1 Direct Information
Transfer initiated from the RNC" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure. This counter is incremented by
one each time the RNC receives a RANAP DERECT INFORMATION TRANSER message
whose type is RAN INFORMATION.
Figure 1-37 Procedure for directly sending messages over the Iu interface
Formula
None
Unit
None
Issue 03 (2015-06-30)

134
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RanInfo.Tx
WRFD-140224

RIM
WRFD-150231

Number of CS Initial Direct Transfer Messages Discarded by RNC When the CN

RANAP is overloaded
Counters
Counter ID
Counter Name
Counter Description
73430073
CS.CNRANAPOverLoad
Number of CS Initial Direct

Transfer Messages
Discarded by RNC When the
CN RANAP is overloaded
Description
This counter provides the number of CS Initial Direct Transfer messages discarded by the RNC
when the CN RANAP is overloaded.The preceding counter complies with section 8.25
"Overload Control" in 3GPP TS 25.413 (V10.10.0).
Measurement point
The measurement is triggered at point A in the following figure. If the RNC receives a RANAP
OVERLOAD message from the CS domain of the CN and flow control is triggered over the Iu
interface, the RNC may discard an Initial Direct Transfer message from the UE and does not
send an Initial UE Message to the CN. Under this circumstance, this counter is measured at point
A.
Figure 1-38 Initial Direct Transfer message discarded due to flow control upon CN RANAP
overload
Issue 03 (2015-06-30)

135
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CS.CNRANAPOverLoad
WRFD-040100
Flow Control
1.4.2 CS Traffic Measurement per Iu Interface(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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199469
VS.IuCS.BytesPayl
dConv.Rx
Number of DL Bytes
of CS Conversational
Service on Iu-CS
Interface
Earlier than
BSC6900
V900R011
67199470
VS.IuCS.BytesPayl
dStr.Rx
Number of DL Bytes
of CS Streaming
Service on Iu-CS
Interface
Earlier than
BSC6900
V900R011
67199473
VS.IuCS.BytesPayl
dConv.Tx
Number of UL Bytes
Service on Iu-CS
Interface
Earlier than
BSC6900
V900R011
67199474
VS.IuCS.BytesPayl
dStr.Tx
Number of UL Bytes
of CS Streaming
Service on Iu-CS
Interface
Earlier than
BSC6900
V900R011

136
BSC6900 UMTS
None
Number of DL Bytes of CS Conversational Service on Iu Interface

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

137
BSC6900 UMTS
Number of DL Bytes of CS Streaming Service on Iu Interface

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

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199473
VS.IuCS.BytesPayldConv.T
x
Number of UL Bytes of CS
Iu-CS Interface

138
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
Counter Name
Feature ID
Feature Name
VS.IuCS.BytesPayldConv.T
x
WRFD-010501
Number of UL Bytes of CS Streaming Service on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67199474
VS.IuCS.BytesPayldStr.Tx
Streaming Service on Iu-CS
Interface
Description
This counter provides the number of UL payload bytes of CS streaming service data on the IuCS interface received by the RNC.It includes the data at the application layer and excludes the
IuUP header.
Measurement point
When receiving the UL CS streaming service data on the Iu-CS interface, the RNC measures
Issue 03 (2015-06-30)

139
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuCS.BytesPayldStr.Tx
WRFD-010502
Streaming QoS Class
1.4.3 MBMS Measurement per Iu Interface(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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192077
VS.IU.MBMS.Start
Number of MBMS
Service
Establishment
Attempts
Earlier than
BSC6900
V900R011
67192078
VS.IU.MBMS.Succ
Number of
Successful MBMS
Service
Establishments
Earlier than
BSC6900
V900R011
67192079
VS.IU.MBMS.Fail
Number of Failed
MBMS Service
Establishments
Earlier than
BSC6900
V900R011
67192080
VS.IU.MBMS.Fail.
NoRsrc
Number of Failed
MBMS Service
Establishments Due
to No Resource
Earlier than
BSC6900
V900R011
67192081
VS.IU.MBMS.Fail.
NNSF
Number of Failed
MBMS Service
Establishments Due
to NNSF
Earlier than
BSC6900
V900R011

140
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67192082
VS.IU.MBMS.Fail.
IuUpFail
Number of Failed
MBMS Service
Establishments Due
to Iu User Plane
Failure
Earlier than
BSC6900
V900R011
67192083
VS.IU.MBMS.Fail.
IuSigFail
Number of Failed
MBMS Service
Establishments Due
to Iu Signaling
Connection Failure
Earlier than
BSC6900
V900R011
None
Total Number of MBMS or IMB Service

Counters
Counter ID
Counter Name
Counter Description
67192077
VS.IU.MBMS.Start

Establishment Attempts
Description
This measurement item takes statistics of the number of MBMS or IMB service establishments.
Measurement point
The measurement is triggered at point A, as shown in the figure. The measurement is triggered
when the RNC receives an MBMS SESSION START message from the PS domain.
Figure 1-39 MBMS session (success procedure)
Issue 03 (2015-06-30)

141
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.MBMS.Start
WRFD-010616
MBMS Introduction
Package
Number of Successful MBMS or IMB Service

Counters
Counter ID
Counter Name
Counter Description
67192078
VS.IU.MBMS.Succ
Number of Successful
MBMS Service
Establishments
Description
This measurement item takes statistics of the number of successful MBMS or IMB service
establishments.
Measurement point
The measurement is triggered at point B, as shown in the figure. The measurement is triggered
when the RNC successfully establishes the MBMS or IMB service and sends an MBMS
SESSION START RESPONSE message to the PS domain.
Figure 1-40 3-17 MBMS session (success procedure)
Issue 03 (2015-06-30)

142
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.MBMS.Succ
WRFD-010616
MBMS Introduction
Package
Number of MBMS or IMB Service Setup Failures on the Iu Interface Due to

Different Causes
Counters
Counter ID
Counter Name
Counter Description
67192079
VS.IU.MBMS.Fail
Number of Failed MBMS

Service Establishments
67192080
VS.IU.MBMS.Fail.NoRsrc

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

to NNSF
67192082
VS.IU.MBMS.Fail.IuUpFail

to Iu User Plane Failure
67192083
VS.IU.MBMS.Fail.IuSigFail

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.
Issue 03 (2015-06-30)

143
BSC6900 UMTS
Measurement point
The measurement is triggered at point B in the figure. When the RNC fails to set up an MBMS
or IMB service, it sends an RANAP MBMS SESSION START FAILURE message to the PS
CN and measures the corresponding counter based on the failure cause.
Figure 1-41 MBMS session (failure procedure)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
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.IuSigFail
WRFD-010616
MBMS Introduction
Package

144
BSC6900 UMTS
1.4.4 MOCN Measurement per Iu Interface(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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193097
VS.IU.MOCN.CsPs
Coordination
Number of
Redirection
Requests from CN
(CS/PS Coordination
Required)
Earlier than
BSC6900
V900R011
67193098
VS.IU.MOCN.LocAreaNotAllowed
Number of
Redirection
Requests from CN
(Location Area Not
Allowed)
Earlier than
BSC6900
V900R011
67193099
VS.IU.MOCN.Plm
nNotAllowed
Number of
Redirection
Requests from CN
(PLMN Not
Allowed)
Earlier than
BSC6900
V900R011
67193100
VS.IU.MOCN.Roa
mNotAllowed
Number of
Redirection
Requests from CN
(Roaming Not
Allowed in this
Location Area)
Earlier than
BSC6900
V900R011
67193101
VS.IU.MOCN.NoSuitableCell
Number of
Redirection
Requests from CN
(No Suitable Cell in
Location Area)
Earlier than
BSC6900
V900R011
67193102
VS.IU.MOCN.Gpr
sServicesNotAllowed
Number of
Redirection
Requests from CN
(GPRS Services Not
Allowed in this
PLMN)
Earlier than
BSC6900
V900R011

145
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430148
VS.IU.MOCN.NetworkFailure
Number of
Redirection
Requests from CN
(Network failure)
BSC6900
V900R017C10
73430149
VS.IU.MOCN.Not
AuthorizedforthisCSG
Number of
Redirection
Requests from CN
(Not authorized for
this CSG)
BSC6900
V900R017C10
73430747
VS.IU.MOCN.ULD
T.RedirectFlag
Number of Times the

UL RNCAP
DIRECT
TRANSFER
Message Contains
the Redirect attempt
flag IE
BSC6900
V900R017C10
73430748
VS.IU.MOCN.DLD
T.RedirectCMP
Number of Times the

DL RNCAP
DIRECT
TRANSFER
Message Contains
the Redirection
complete IE
BSC6900
V900R017C10
73430749
VS.IU.MOCN.ULD
T.SelectedPLMN
Number of Times the

UL RNCAP
DIRECT
TRANSFER
Message Contains
the Selected PLMN
IE
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

146
BSC6900 UMTS
Number of Redirect for Different Causes

Counters
Counter ID
Counter Name
Counter Description
67193097
VS.IU.MOCN.CsPsCoordination
Number of Redirection
Requests from CN (CS/PS
Coordination Required)
67193098
Requests from CN (Location
Area Not Allowed)
67193099
VS.IU.MOCN.PlmnNotAllowed
Requests from CN (PLMN
Not Allowed)
67193100
VS.IU.MOCN.RoamNotAllowed
Requests from CN (Roaming
Not Allowed in this Location
Area)
67193101
Requests from CN (No
Suitable Cell in Location
Area)
67193102
VS.IU.MOCN.GprsServicesNotAllowed
Requests from CN (GPRS
Services Not Allowed in this
PLMN)
73430148
Requests from CN (Network
failure)
73430149
VS.IU.MOCN.NotAuthorizedforthisCSG
Requests from CN (Not
authorized for this CSG)
Description
The measurement counters provide the number of Redirect in the scenario of the MOCN for
different causes.The preceding counters comply with section "9.2.3.36 Redirection Indication"
in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

147
BSC6900 UMTS
Figure 1-42 Process of INIT UE MESSAGE Redirect
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.MOCN.CsPsCoordination
WRFD-021311
MOCN Introduction
Package
WRFD-021311
MOCN Introduction
Package
VS.IU.MOCN.PlmnNotAllowed
WRFD-021311
MOCN Introduction
Package
VS.IU.MOCN.RoamNotAllowed
WRFD-021311
MOCN Introduction
Package
WRFD-021311
MOCN Introduction
Package
VS.IU.MOCN.GprsServicesNotAllowed
WRFD-021311
MOCN Introduction
Package
WRFD-021311
MOCN Introduction
Package

148
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.IU.MOCN.NotAuthorizedforthisCSG
WRFD-021311
MOCN Introduction
Package
Number of Times the UL RNCAP DIRECT TRANSFER Message Contains the

Redirect attempt flag IE
Counters
Counter ID
Counter Name
Counter Description
73430747
VS.IU.MOCN.ULDT.RedirectFlag
Number of Times the UL

RNCAP DIRECT
TRANSFER Message
Contains the Redirect
attempt flag IE
Description
This counter provides the number of times the RNC includes the "Redirect attempt flag" IE in
the UL RNCAP DIRECT TRANSFER message from a non-supporting UE. This counter
complies with 3GPP TS 25.413 (V11.3.0). For details, see section 8.22 "Initial UE Message" in
this TS. Non-supporting UEs are those that cannot decode the PLMN information of multiple
operators in the system information in MOCN networking. For details about non-supporting
UEs, see section 3.1 "Definitions" in 3GPP TS 23.251 (V6.0.0).
Measurement point
The measurement is triggered at point A in figure 1. In MOCN networking, a non-supporting
UE cannot notify the RNC of the selected PLMN. The RNC then includes the "Redirect attempt
flag" IE in the UL RNCAP DIRECT TRANSFER message. When a UL RNCAP DIRECT
TRANSFER message sent by the RNC contains the "Redirect attempt flag" IE, this counter is
measured on the corresponding Iu interface.
Issue 03 (2015-06-30)

149
BSC6900 UMTS
Figure 1-43 Transmission of a UL RNCAP DIRECT TRANSFER message
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.MOCN.ULDT.RedirectFlag
WRFD-021311
MOCN Introduction
Package

150
BSC6900 UMTS
Number of Times the DL RNCAP DIRECT TRANSFER Message Contains the

Redirection complete IE
Counters
Counter ID
Counter Name
Counter Description
73430748
VS.IU.MOCN.DLDT.RedirectCMP
Number of Times the DL

RNCAP DIRECT
TRANSFER Message
Contains the Redirection
complete IE
Description
This counter provides the number of times the CN includes the "Redirection complete" IE in the
DL RNCAP DIRECT TRANSFER message after receiving a UL RNCAP DIRECT
TRANSFER message with the "Redirect attempt flag" IE. This counter complies with 3GPP TS
25.413 (V11.3.0). For details, see section 9.1.34 "DIRECT TRANSFER" in this TS.
Measurement point
The measurement is triggered at point B in figure 1. In MOCN networking, when the RNC
receives a DL RNCAP DIRECT TRANSFER message with the "Redirection complete" IE after
sending a UL RNCAP DIRECT TRANSFER message with the "Redirect attempt flag" IE, this
counter is measured on the corresponding Iu interface.
Figure 1-44 Reception of a DL RNCAP DIRECT TRANSFER message
Issue 03 (2015-06-30)

151
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.MOCN.DLDT.RedirectCMP
WRFD-021311
MOCN Introduction
Package
Number of Times the UL RNCAP DIRECT TRANSFER Message Contains the

Selected PLMN IE
Counters
Counter ID
Counter Name
Counter Description
73430749
VS.IU.MOCN.ULDT.SelectedPLMN

RNCAP DIRECT
TRANSFER Message
Contains the Selected PLMN
IE
Description
This counter provides the number of times the RNC selects a CN node for processing a UL
RNCAP DIRECT TRANSFER message based on the "selected PLMN" IE received from the
UE. This counter complies with 3GPP TS 23.251 (V6.0.0). For details, see section 7.1.5
"Supporting UEs in a MOCN configuration" in this TS.
Measurement point
The measurement is triggered at point A in figure 1. In MOCN networking, a supporting UE
notifies the RNC of the selected PLMN. The RNC then includes the "selected PLMN" IE in the
UL RNCAP DIRECT TRANSFER message. When a UL RNCAP DIRECT TRANSFER
message sent by the RNC contains the "selected PLMN" IE, this counter is measured on the
corresponding Iu interface.
Issue 03 (2015-06-30)

152
BSC6900 UMTS
Figure 1-45 Transmission of a UL RNCAP DIRECT TRANSFER message
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.MOCN.ULDT.SelectedPLMN
WRFD-021311
MOCN Introduction
Package
1.4.5 NAS Signaling Measurement per Iu Interface(NAS.IU)

Overview
The function subset Non-Access Stratum (NAS) Signaling Measurement on the Iu Interface
measures the number of NAS interactions on the Iu interface. The method of measuring NASrelated counters on the RNC are different from those on the CN,and the later prevails.
Issue 03 (2015-06-30)

153
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423785
VS.IU.MM.LocUp
d.Req
Number of Location
Area Update
Requests Forwarded
by the RNC to the CN
BSC6900
V900R014
73423786
VS.IU.MM.LocUp
d.Acc
Number of Accepted
Location Area
Update Requests
Received by the
RNC from the CN
BSC6900
V900R014
73423788
VS.IU.GMM.RAU.
Acc
Number of Accepted
Routing Area Update
Requests Received
by the RNC from the
CN
BSC6900
V900R014
73423789
VS.IU.GMM.Attac
h.Req
Number of Attach
Requests Forwarded
BSC6900
V900R014
73423790
VS.IU.GMM.Attac
h.Acc
Number of Accepted
Attach Requests
Received by the
RNC from the CN
BSC6900
V900R014
73423791
VS.IU.GMM.PDP
Act.Req
Number of PDP
Activation Requests
Forwarded by the
RNC to the CN
BSC6900
V900R014
73423792
VS.IU.GMM.PDP
Act.Acc
Number of Accepted
PDP Activation
Requests Received
by the RNC from the
CN
BSC6900
V900R014
73423793
VS.IU.Sevice.Req
Number of Service
Setup Requests
Forwarded by the
RNC to the CN
BSC6900
V900R014
73423794
VS.IU.Sevice.Rej
Number of Rejected
Service Setup
Requests Received
by the RNC from the
CN
BSC6900
V900R014

154
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73423795
VS.IU.Auth.Req
Number of
Authentication
Requests Received
by the RNC from the
CN
BSC6900
V900R014
73423796
VS.IU.Auth.Rsp
Number of
Authentication
Responses
Forwarded by the
RNC to the CN
BSC6900
V900R014
73423797
VS.IU.SecModeCm
d.Num
Number of
SECURITY MODE
COMMAND
Messages Received
by the RNC from the
CN
BSC6900
V900R014
73423798
VS.IU.SecModeCm
p.Num
Number of
SECURITY MODE
COMPLETE
Messages Forwarded
BSC6900
V900R014
73423799
VS.IU.GMM.RAU.
Req
Number of Routing
Area Update
Requests Forwarded
BSC6900
V900R014
73430750
VS.IU.IdentityReq.
IMSI
Number of
IDENTITY
REQUEST
Messages for
Querying IMSI
BSC6900
V900R017C10
73430751
VS.IU.Routing.TM
SI
Number of (P)TMSIbased CN Route

Selections
BSC6900
V900R017C10
73430752
VS.IU.Routing.IMSI
Number of IMSIbased CN Route

Selections
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

155
BSC6900 UMTS
Number of Messages Forwarded by the RNC to the CN

Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)
Counter Name
Description
VS.IU.MM.LocUpd.Req
This counter complies with section "4.4.4

Generic Location Updating procedure" in
3GPP TS 24.008 (v10.12.0).

GPRS attach procedure" in 3GPP TS 24.008
(v10.12.0).
This counter complies with section "6.1.3.1

PDP context activation" in 3GPP TS 24.008
(v10.12.0).
VS.IU.Sevice.Req

Service Request procedure (Iu mode only)"
in 3GPP TS 24.008 (v10.12.0).

156
BSC6900 UMTS
Counter Name
Description
VS.IU.GMM.RAU.Req

Routing area updating procedure" in 3GPP
TS 24.008 (v10.12.0).
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.
Figure 1-46 Process of INIT UE MESSAGE Direct TRANSFER
Formula
None
Unit
None
Issue 03 (2015-06-30)

157
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.MM.LocUpd.Req
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
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
Number of Messages Forwarded by the RNC from the CN

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
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

158
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
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.
Counter Name
Description
VS.IU.MM.LocUpd.Acc

Generic Location Updating procedure" in
3GPP TS 24.008 (v10.12.0).
VS.IU.GMM.RAU.Acc

Routing area updating procedure" in 3GPP
TS 24.008 (v10.12.0).

GPRS attach procedure" in 3GPP TS 24.008
(v10.12.0).
This counter complies with section "6.1.3.1

PDP context activation" in 3GPP TS 24.008
(v10.12.0).
VS.IU.Sevice.Rej

Service Request procedure (Iu mode only)"
in 3GPP TS 24.008 (v10.12.0).
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC forwards the
UE a DIRECT TRANSFER message sent by the CN, the RNC decodes the message and
determines the message type based on decoding result. This counter is measured in the
corresponding CN node based on the message type.
Issue 03 (2015-06-30)

159
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
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
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

160
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.IU.Sevice.Rej
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Authentication Requests Received by the RNC from the CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "4.3.2 Authentication procedure" in 3GPP TS 24.008
(v10.12.0).
Measurement point
The measurement is triggered at point B as shown in the figure. The measurement is triggered
when the RNC receives a DIRECT TRANSFER message sent by the CN and determines that
this message is an authentication request based on the message decoding result. In this case, this
counter is incremented by one in the corresponding CN node.
Issue 03 (2015-06-30)

161
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.Auth.Req
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Authentication Responses Forwarded by the RNC to the CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "4.3.2 Authentication procedure" in 3GPP TS 24.008
(v10.12.0).
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.
Issue 03 (2015-06-30)

162
BSC6900 UMTS
Figure 1-49 Process of Direct TRANSFER
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.Auth.Rsp
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of SECURITY MODE COMMAND Messages Received by the RNC from

the CN
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423797
VS.IU.SecModeCmd.Num
Number of SECURITY
MODE COMMAND
Messages Received by the
RNC from the CN

163
BSC6900 UMTS
Description
This counter provides the number of SECURITY MODE COMMAND messages received by
the RNC from the CN.This counter complies with section "8.18 Security Mode Control" in 3GPP
TS 25.413 (v10.10.0).
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.
Figure 1-50 Security mode control procedure (CN to RNC)
Formula
None
Unit
None
Issue 03 (2015-06-30)

164
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.SecModeCmd.Num
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of SECURITY MODE COMPLETE Messages Forwarded by the RNC to

the CN
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.18 Security Mode Control" in 3GPP
TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

165
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.SecModeCmp.Num
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

166
BSC6900 UMTS
Number of IDENTITY REQUEST Messages for Querying IMSI

Counters
Counter ID
Counter Name
Counter Description
73430750
VS.IU.IdentityReq.IMSI
Number of IDENTITY
REQUEST Messages for
Querying IMSI
Description
This counter provides the number of times the RNC receives from the CN an IDENTITY
REQUEST message for querying the IMSI. This counter complies with 3GPP TS 24.008
(V6.0.0). For details, see section 9.2.10 "Identity request" in this TS.
Measurement point
The measurement is triggered at point A in figure 1. When the RNC receives from the CN an
IDENTITY REQUEST message where the value of "Identity type" is IMSI, this counter is
Figure 1-52 RNC receiving an IDENTITY REQUEST message
Formula
None
Issue 03 (2015-06-30)

167
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.IdentityReq.IMSI
WRFD-021311
MOCN Introduction
Package
Number of (P)TMSI-based CN Route Selections

Counters
Counter ID
Counter Name
Counter Description
73430751
VS.IU.Routing.TMSI
Number of (P)TMSI-based
CN Route Selections
Description
This counter provides the number of times the RNC selects a CN node for processing an Initial
UE Message based on the network resource identifier (NRI) in the temporary mobile subscriber
identity (TMSI) or packet temporary mobile subscriber identity (PTMSI). This counter complies
with 3GPP TS 25.331 (V6.0.0). For details, see section 8.1.8 "Initial Direct Transfer" in this TS.
Measurement point
The measurement is triggered at point A in figure 1. When the RNC selects a CN node for
processing an Initial UE Message based on the NRI in the IMSI or PTMSI, this counter is
Issue 03 (2015-06-30)

168
BSC6900 UMTS
Figure 1-53 RNC selecting a CN node for processing the Initial UE Message
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.Routing.TMSI
WRFD-021311
MOCN Introduction
Package
Number of IMSI-based CN Route Selections

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430752
VS.IU.Routing.IMSI
Number of IMSI-based CN
Route Selections

169
BSC6900 UMTS
Description
This counter provides the number of times the RNC selects a CN node for processing an Initial
UE Message based on the international mobile subscriber identity (IMSI). This counter complies
with 3GPP TS 25.331 (V6.0.0). For details, see section 8.1.8 "Initial Direct Transfer" in this TS.
Measurement point
The measurement is triggered at point A in figure 1. When the RNC selects a CN node for
processing an Initial UE Message based on the IMSI, this counter is measured on the
corresponding Iu interface.
Figure 1-54 RNC selecting a CN node for processing the Initial UE Message
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.Routing.IMSI
WRFD-021311
MOCN Introduction
Package

170
BSC6900 UMTS
1.4.6 PS Signaling Measurement per Iu Interface(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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67176481
VS.IU.ResetPS.Tx
Number of RESET
Messages Sent by
RNC to CN in PS
Domain
Earlier than
BSC6900
V900R011
67176485
VS.IU.ResetPS.Rx
Number of RESET
Messages Received
by RNC from CN in
PS Domain
Earlier than
BSC6900
V900R011
67189921
VS.IU.SIG.AttConnEstabPS
Number of INITIAL
UE MESSAGE
Messages Sent by
RNC to CN in PS
Domain
Earlier than
BSC6900
V900R011
67176559
VS.IU.RelReqPS.su
m
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in PS
Domain
Earlier than
BSC6900
V900R011
67176565
VS.IU.RelCmdPS.s
um
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
PS Domain
Earlier than
BSC6900
V900R011
67176530
VS.IU.ErrInd.PS.T
x
Number of ERROR
INDICATION
Messages Sent by
RNC to CN in PS
Domain
Earlier than
BSC6900
V900R011

171
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67176532
VS.IU.ErrInd.PS.R
x
Number of ERROR
INDICATION
Messages Received
by RNC from CN in
PS Domain
Earlier than
BSC6900
V900R011
67176561
VS.IU.RelReqPS.U
srInact
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in PS
Domain (User
Inactive)
Earlier than
BSC6900
V900R011
67176562
VS.IU.RelReqPS.In
gChkFail
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in PS
Domain (Repeated
Integrity Checking
Failure)
Earlier than
BSC6900
V900R011
67176563
VS.IU.RelReqPS.Si
gConnRel
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in PS
Domain (UE
Signaling
Connection Release)
Earlier than
BSC6900
V900R011
67176564
VS.IU.RelReqPS.U
ELost
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in PS
Domain (RL Out of
Synchronization)
Earlier than
BSC6900
V900R011
67176566
VS.IU.RelCmdPS.
RelocSucc
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
PS Domain
(Relocation Success)
Earlier than
BSC6900
V900R011

172
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67176567
VS.IU.RelCmdPS.
NormRel
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
PS Domain (Normal
Release)
Earlier than
BSC6900
V900R011
67176568
VS.IU.RelCmdPS.
UTRANGen
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
PS Domain (UTRAN
Generated)
Earlier than
BSC6900
V900R011
67176569
VS.IU.RelCmdPS.
RelocCanl
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
PS Domain
(Relocation
Cancelled)
Earlier than
BSC6900
V900R011
67176570
VS.IU.RelCmdPS.
NoRAB
Number of IU
RELEASE
COMMAND
Messages Received
by RNC from CN in
PS Domain (No
Remaining RAB)
Earlier than
BSC6900
V900R011
67176574
VS.Iu.RelReqPS.RI
PFail
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in PS
Domain (Failure in
the Radio Interface
Procedure)
Earlier than
BSC6900
V900R011
67190183
VS.IU.RelReqPS.P
reempt
Number of IU
RELEASE
REQUEST
Messages Sent by
RNC to CN in PS
Domain (RAB
Preempted)
Earlier than
BSC6900
V900R011

173
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192541
VS.IU.Load.Route
PS.IMSI
Number of
Performed PS Load
Balancing by IMSI
Users
Earlier than
BSC6900
V900R011
67192542
VS.IU.Load.Route
PS.NRI
Number of
Performed PS Load
Balancing by TMSI
Users Due to Invalid
NRI
Earlier than
BSC6900
V900R011
67192543
VS.IU.Load.Route
PS.IMEI
Number of
Performed PS Load
Balancing by IMEI
Users
Earlier than
BSC6900
V900R011
67193096
VS.IU.FlowCtrl.Dis
c.InitDT.PS
Number of
Discarded PS Initial
UE Messages when
Signaling Flow
Control is Triggered
Earlier than
BSC6900
V900R011
73424971
VS.IU.PS.Paging
Number of Paging
Messages Received
by RNC from CN in
PS Domain
BSC6900
V900R014
73426319
VS.IU.RIM.L2U.SI
.Req
Number of RIM
Requests from the
eNodeB to the RNC
(System
Information)
BSC6900
V900R015C00
73426320
VS.IU.RIM.L2U.SI
.Resp
Number of RIM
Response Messages
from the RNC to the
eNodeB (System
Information)
BSC6900
V900R015C00
73426321
VS.IU.RIM.L2U.SI
.Update
Number of RIM
Update Messages
from the RNC to the
eNodeB (System
Information)
BSC6900
V900R015C00

174
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426322
VS.IU.RIM.L2U.SI
.Update.ACK
Number of RIM
acknowledgement
messages from the
eNodeB to the RNC
(System
Information)
BSC6900
V900R015C00
73426323
VS.IU.RIM.L2U.L
oad.Req
Number of RIM
Requests from the
eNodeB to the RNC
(Load Information)
BSC6900
V900R015C00
73426324
VS.IU.RIM.L2U.L
oad.Resp
Number of RIM
Response Messages
from the RNC to the
eNodeB (Load
Information)
BSC6900
V900R015C00
73426325
VS.IU.RIM.L2U.L
oad.Update
Number of RIM
Update Messages
from the RNC to the
eNodeB (Load
Information)
BSC6900
V900R015C00
73426326
VS.IU.RIM.L2U.L
oad.Update.ACK
Number of RIM
Acknowledgement
Messages from the
eNodeB to the RNC
(Load Information)
BSC6900
V900R015
73427901
VS.IU.RIM.U2L.L
oad.Req
Number of RIM
Requests from the
RNC to the eNodeB
(Load Information)
for Cell
BSC6900
V900R016
73427902
VS.IU.RIM.U2L.L
oad.Resp
Number of RIM
Responses from the
eNodeB to the RNC
(Load Information)
for Cell
BSC6900
V900R016C00
73428262
VS.IU.RIM.U2L.L
oad.Update
Number of RIM
Update Messages
from the eNodeB to
the RNC (Load
Information) for Cell
BSC6900
V900R016C00

175
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430074
VS.IU.FlowCtrl.Dis
cInitDT.PS.CNRANAPOverLoad
Number of PS Initial
Direct Transfer
Messages Discarded
by RNC When the
CN RANAP is
overloaded
BSC6900
V900R017C10
73430226
VS.IU.RIM.L2U.SI
.Fail
Number of Times the

RNC Fail to Process
the RIM Requests
from the eNodeB
(System
Information)
BSC6900
V900R017C10
73430227
VS.IU.RIM.L2U.L
oad.Fail
Number of Times the

RNC Fail to Process
the RIM Requests
from the eNodeB
(Load Information)
BSC6900
V900R017C10
None
Number of RESET Messages Initiated by RNC to PS Domain

Counters
Counter ID
Counter Name
Counter Description
67176481
VS.IU.ResetPS.Tx

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.This counter
complies with section "8.26.2.2 Reset Procedure Initiated from the UTRAN" in 3GPP TS 25.413
(v10.10.0).
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
Issue 03 (2015-06-30)

176
BSC6900 UMTS
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-55 PS domain reset procedure initiated by the RNC (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.ResetPS.Tx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RESET Messages Received by RNC from PS Domain

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67176485
VS.IU.ResetPS.Rx

in PS Domain

177
BSC6900 UMTS
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.This counter
complies with section "8.26.2.1 Reset Procedure Initiated from the CN" in 3GPP TS 25.413
(v10.10.0).
Measurement point
RESET message from the PS domain, it measures this counter.
Figure 1-56 PS domain reset procedure initiated by the CN (successful operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.ResetPS.Rx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

178
BSC6900 UMTS
Number of INITIAL UE MESSAGE Messages from RNC to PS Domain

Counters
Counter ID
Counter Name
Counter Description
67189921
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.This counter complies with section "8.22 Initial UE Message" in 3GPP TS 25.413
(v10.10.0).
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
Issue 03 (2015-06-30)

179
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of IU RELEASE REQUEST Messages from RNC to PS Domain

Counters
Counter ID
Counter Name
Counter Description
67176559
VS.IU.RelReqPS.sum
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.This counter
complies with section "8.4 Iu Release Request" in 3GPP TS 25.413 (v10.10.0).
Measurement point
RELEASE REQUEST message to the PS domain, it measures this counter.
Issue 03 (2015-06-30)

180
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RelReqPS.sum
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of IU RELEASE COMMAND Messages from PS Domain to RNC

Counters
Counter ID
Counter Name
Counter Description
67176565
VS.IU.RelCmdPS.sum
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.This counter complies
with section "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B, as shown in the figure. In the RNC-initiated Iu release
procedure, when the RNC receives an IU RELEASE COMMAND message from the PS domain,
it measures this counter.
Issue 03 (2015-06-30)

181
BSC6900 UMTS
The measurement is triggered at point A, as shown in the figure. In the CN-initiated Iu release
it measures this counter.
Formula
None
Issue 03 (2015-06-30)

182
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RelCmdPS.sum
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of ERROR INDICATION Messages from RNC to PS Domain

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.27 Error Indication"
in 3GPP TS 25.413 (v10.10.0).
Measurement point
INDICATION message to the PS domain, it measures this counter.
Figure 1-61 Error indication procedure initiated by the RNC
Issue 03 (2015-06-30)

183
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.ErrInd.PS.Tx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of ERROR INDICATION Messages from PS Domain to RNC

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies
with section "8.27 Error Indication" in 3GPP TS 25.413 (v10.10.0).
Measurement point
ERROR INDICATION message from the PS domain, it measures this counter according to the
CN nodes.
Figure 1-62 Error indication procedure initiated by the CN
Issue 03 (2015-06-30)

184
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.ErrInd.PS.Rx
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of IU RELEASE REQUEST Messages from RNC to PS Domain for

Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67176561
VS.IU.RelReqPS.UsrInact
(User Inactive)
67176562
VS.IU.RelReqPS.IngChkFail
(Repeated Integrity
Checking Failure)
67176563
VS.IU.RelReqPS.SigConnRel
Release)
67176564
VS.IU.RelReqPS.UELost
(RL Out of Synchronization)

185
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67176574
VS.Iu.RelReqPS.RIPFail
67190183
VS.IU.RelReqPS.Preempt
(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.The preceding counters comply with section "8.4 Iu Release Request" in
3GPP TS 25.413 (v10.10.0).
Measurement point
RELEASE REQUEST message to the PS domain, it measures these counters according to
different causes.
Issue 03 (2015-06-30)

186
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RelReqPS.UsrInact
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelReqPS.IngChkFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelReqPS.SigConnRel
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
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

187
BSC6900 UMTS
Number of IU RELEASE COMMAND Messages from PS Domain to RNC for

Different Causes
Counters
Counter ID
Counter Name
Counter Description
67176566
VS.IU.RelCmdPS.RelocSucc
COMMAND Messages
in PS Domain (Relocation
Success)
67176567
VS.IU.RelCmdPS.NormRel
COMMAND Messages
in PS Domain (Normal
Release)
67176568
VS.IU.RelCmdPS.UTRANGen
COMMAND Messages
in PS Domain (UTRAN
Generated)
67176569
VS.IU.RelCmdPS.RelocCanl
COMMAND Messages
in PS Domain (Relocation
Cancelled)
67176570
VS.IU.RelCmdPS.NoRAB
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.The preceding counters comply with section "8.5 Iu
Release" in 3GPP TS 25.413 (v10.10.0).
Measurement point
1) The measurement is triggered at point B, as shown in the figure. In the RNC-initiated Iu
release procedure, when the RNC receives an IU RELEASE COMMAND message from the PS
domain, it measures these counters.
Issue 03 (2015-06-30)

188
BSC6900 UMTS
2) The measurement is triggered at point A, as shown in the figure. In the CN-initiated Iu release
it measures these counters.
Formula
None
Issue 03 (2015-06-30)

189
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RelCmdPS.RelocSucc
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelCmdPS.NormRel
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelCmdPS.UTRANGen
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelCmdPS.RelocCanl
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IU.RelCmdPS.NoRAB
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Load Balancing of the MSC Pool on the PS Domain

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192541
VS.IU.Load.RoutePS.IMSI
Number of Performed PS
Load Balancing by IMSI
Users
67192542
VS.IU.Load.RoutePS.NRI
Load Balancing by TMSI
Users Due to Invalid NRI
67192543
VS.IU.Load.RoutePS.IMEI
Load Balancing by IMEI
Users

190
BSC6900 UMTS
Description
The measurement counters provide the number of times that the UEs perform load balancing on
the PS domain during CN node selection when the RNC processes the initial direct transfer
message.The preceding counters comply with section "4.5 Load Balancing" in 3GPP TS 23.236
(v10.3.0).
Counter Name
Description
Number of times that the PS CN is selected

for load balancing by using the IMSI route
parameter.
Number of times that load balancing is

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

for load balancing by using the IMEI route
parameter.
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
Issue 03 (2015-06-30)

191
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-021306

Management
WRFD-021306

Management
WRFD-021306

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

Domain)
Counters
Counter ID
Counter Name
Counter Description
67193096
VS.IU.FlowCtrl.Disc.InitDT
.PS
Number of Discarded PS
Initial UE Messages when
Signaling Flow Control is
Triggered
Description
This measurement counter provides the number of initial UE messages discarded under the
SCCP flow control when the RNC receives the PS initial direct transfer message.
Measurement point
The measurement is triggered when the RNC receives an INITIAL DIRECT TRANSFER
message from a UE and then discards this message because the RNC finds that the Iu-PS interface
is under flow control. Then, the RNC does not send the INITIAL UE MESSAGE message to
the CN.
Figure 1-67 Process of discarding INITIAL DIRECT TRANSFER message
Issue 03 (2015-06-30)

192
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.FlowCtrl.Disc.InitDT
.PS
WRFD-040100
Flow Control
Number of Paging Messages Received by RNC from CN in PS Domain

Counters
Counter ID
Counter Name
Counter Description
73424971
VS.IU.PS.Paging

in PS Domain
Description
This measurement counter provides the number of PAGING messages that the PS domain sends
to the RNC according to respective CN nodes.This counter complies with section "8.15 Paging"
in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

193
BSC6900 UMTS
Figure 1-68 Paging messages sent from the CN to the UE
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.PS.Paging
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-010302
Number of RIM Requests from the eNodeB to the RNC (System Information)
Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

194
BSC6900 UMTS
and RAN-INFORMATION-REQUEST/Multiple Report.This counter complies with section

"8.34 Direct Information Transfer" in 3GPP TS 25.413 (v10.10.0).
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 message with
system information from the eNodeB on the Iu interface.
Figure 1-69 RIM message procedure(single mode)

1 when the RNC receives the RAN-INFORMATION-REQUEST/Multiple Report message with
system information from the eNodeB on the Iu interface.
Issue 03 (2015-06-30)

195
BSC6900 UMTS
Figure 1-70 RIM message procedure(Multiple mode)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.SI.Req
WRFD-140224

RIM

196
BSC6900 UMTS
Number of RIM Response Messages from the RNC to the eNodeB (System
Information)
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section
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 message with
system information on the Iu interface.
Issue 03 (2015-06-30)

197
BSC6900 UMTS

1 when the RNC sends to the eNodeB the RAN-INFORMATION/Multiple Report-Initial
message with system information on the Iu interface.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.SI.Resp
WRFD-140224

RIM

198
BSC6900 UMTS
Number of RIM Update Messages from the RNC to the eNodeB (System
Information)
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.34 Direct Information Transfer" in 3GPP TS
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point C as shown in Figure 2. This counter is incremented by
1 when the RNC sends to the eNodeB the RAN-INFORMATION/Multiple Report message with
system information on the Iu interface.
Issue 03 (2015-06-30)

199
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.SI.Update
WRFD-140224

RIM

200
BSC6900 UMTS
Number of RIM acknowledgement messages from the eNodeB to the RNC (System
Information)
Counters
Counter ID
Counter Name
Counter Description
73426322
VS.IU.RIM.L2U.SI.Update.
ACK
Number of RIM
acknowledgement messages
Description
This counter provides the number of RIM acknowledgement messages with system information
the RNC receives from the eNodeB.This counter complies with section "8.34 Direct Information
Transfer" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

201
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.SI.Update.
ACK
WRFD-140224

RIM

202
BSC6900 UMTS
Number of RIM Requests from the eNodeB to the RNC (Load Information)
Counters
Counter ID
Counter Name
Counter Description
73426323
VS.IU.RIM.L2U.Load.Req

(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.This counter complies with section "8.34
Direct Information Transfer" in 3GPP TS 25.413 (v10.10.0).
Measurement point
1 when the RNC receives the RAN-INFORMATION-REQUEST/Single Report message with
load information from the eNodeB on the Iu interface.

1 when the RNC receives the RAN-INFORMATION-REQUEST/Multiple Report message with
load information from the eNodeB on the Iu interface.
Issue 03 (2015-06-30)

203
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.Load.Req
WRFD-150231


204
BSC6900 UMTS
Number of RIM Response Messages from the RNC to the eNodeB (Load
Information)
Counters
Counter ID
Counter Name
Counter Description
73426324
VS.IU.RIM.L2U.Load.Resp

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.This counter complies with section
Measurement point
1 when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report message with
load information on the Iu interface.
Issue 03 (2015-06-30)

205
BSC6900 UMTS

message with load information on the Iu interface.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.Load.Resp
WRFD-150231


206
BSC6900 UMTS
Number of RIM Update Messages from the RNC to the eNodeB (Load Information)
Counters
Counter ID
Counter Name
Counter Description
73426325
VS.IU.RIM.L2U.Load.Update

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.This
counter complies with section "8.34 Direct Information Transfer" in 3GPP TS 25.413 (v10.10.0).
Measurement point
message with load information on the Iu interface.
Issue 03 (2015-06-30)

207
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.Load.Update
WRFD-150231


208
BSC6900 UMTS
Number of RIM Acknowledgement Messages from the eNodeB to the RNC (Load
Information)
Counters
Counter ID
Counter Name
Counter Description
73426326
VS.IU.RIM.L2U.Load.Upda
te.ACK
Number of RIM
Acknowledgement
Messages from the eNodeB
to the RNC (Load
Information)
Description
This counter provides the number of RIM acknowledgement messages with load information
the RNC receives from the eNodeB.This counter complies with section "8.34 Direct Information
Measurement point
1 when the RNC receives the RAN-INFORMATION-ACK message with load information from
the eNodeB on the Iu interface.
Issue 03 (2015-06-30)

209
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.Load.Upda
te.ACK
WRFD-150231


210
BSC6900 UMTS
Number of RIM Requests from the RNC to the eNodeB (Load Information)
Counters
Counter ID
Counter Name
Counter Description
73427901
VS.IU.RIM.U2L.Load.Req

from the RNC to the eNodeB
(Load Information) for Cell
Description
This counter provides the number of RAN-INFORMATION-REQUEST/Multiple Report
messages sent from the RNC to the eNodeB. The RNC sends such messages to request LTE cell
load information from the eNodeB.This counter complies with section "8.34 Direct Information
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RANINFORMATION-REQUEST/Multiple Report message to the eNodeB on the Iu interface to
request LTE cell load information from the eNodeB. In this case, this counter is incremented by
one.
Figure 1-81 RIM message procedure
Issue 03 (2015-06-30)

211
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
Number of RIM Responses from the eNodeB to the RNC (Load Information)
Counters
Counter ID
Counter Name
Counter Description
73427902
VS.IU.RIM.U2L.Load.Resp
Number of RIM Responses

(Load Information) for Cell
Description
This counter provides the number of RAN-INFORMATION/Multiple Report-Initial messages
sent from the eNodeB to the RNC. Such messages include LTE cell load information.This
counter complies with section "8.34 Direct Information Transfer" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a RANINFORMATION/Multiple Report-Initial message from the eNodeB on the Iu interface and the
message includes LTE cell load information. In this case, this counter is incremented by one.
Issue 03 (2015-06-30)

212
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
Number of RIM Update Messages from the eNodeB to the RNC (Load Information)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428262
VS.IU.RIM.U2L.Load.Update

to the RNC (Load
Information) for Cell

213
BSC6900 UMTS
Description
This counter provides the number of RAN-INFORMATION/Multiple Report messages sent
from the eNodeB to the RNC. Such messages include LTE cell load information.This counter
complies with section "8.34 Direct Information Transfer" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives a RANINFORMATION/Multiple Report message from the eNodeB on the Iu interface and the message
includes LTE cell load information. In this case, this counter is incremented by one.
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

214
BSC6900 UMTS
Number of PS Initial Direct Transfer Messages Discarded by RNC When the CN

RANAP is overloaded
Counters
Counter ID
Counter Name
Counter Description
73430074
PS.CNRANAPOverLoad
Number of PS Initial Direct

Transfer Messages
Discarded by RNC When the
CN RANAP is overloaded
Description
This counter provides the number of PS Initial Direct Transfer messages discarded by the RNC
when the CN RANAP is overloaded.The preceding counter complies with section 8.25
"Overload Control" in 3GPP TS 25.413 (V10.10.0).
Measurement point
The measurement is triggered at point A in the following figure. If the RNC receives a RANAP
OVERLOAD message from the PS domain of the CN and flow control is triggered over the Iu
interface, the RNC may discard an Initial Direct Transfer message from the UE and does not
send an Initial UE Message to the CN. Under this circumstance, this counter is measured at point
A.
Figure 1-84 Initial Direct Transfer message discarded due to flow control upon CN RANAP
overload
Formula
None
Unit
None
Issue 03 (2015-06-30)

215
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
PS.CNRANAPOverLoad
WRFD-040100
Flow Control
Number of Times the RNC Fail to Process the RIM Requests from the eNodeB
Counters
Counter ID
Counter Name
Counter Description
73430226
VS.IU.RIM.L2U.SI.Fail
Number of Times the RNC

Fail to Process the RIM
Requests from the eNodeB
Description
This counter provides the number of times the RNC fails to process the RAN-INFORMATIONREQUEST/Single Report or RAN-INFORMATION-REQUEST/Multiple Report message sent
by the LTE side over the Iu interface for UMTS system information. This counter complies with
3GPP TS 48.018 (V10.10.0). For details about this counter, see section 8c.2 "RIM procedures"
in this TS.
Measurement point
When the RNC fails to process the RAN-INFORMATION-REQUEST/Single Report message
that is sent by the LTE side over the Iu interface for UMTS system information, this counter is
increased by one. This counter is measured at point A as shown in Figure 1.
Figure 1-85 RNC failing to process RIM request from the LTE side(single mode)
Issue 03 (2015-06-30)

216
BSC6900 UMTS
When the RNC fails to process the RAN-INFORMATION-REQUEST/Multiple Report

message that is sent by the LTE side over the Iu interface for UMTS system information, this
counter is increased by one. This counter is measured at point A as shown in Figure 2.
Figure 1-86 RNC failing to process RIM request from the LTE side(multiple mode)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.SI.Fail
WRFD-140224

RIM
WRFD-150231

Issue 03 (2015-06-30)

217
BSC6900 UMTS
(Load Information)
Counters
Counter ID
Counter Name
Counter Description
73430227
VS.IU.RIM.L2U.Load.Fail

(Load Information)
Description
by the LTE side over the Iu interface for UMTS load information. This counter complies with
3GPP TS 48.018 (V10.10.0). For details about this counter, see section 8c.2 "RIM procedures"
in this TS.
Measurement point
When the RNC fails to process the RAN-INFORMATION-REQUEST/Single Report that
requests load information from the LTE side, this counter is increased by one.This counter is
measured at point A as shown in Figure 1.
Figure 1-87 RNC failing to process RIM request from the LTE side(single mode)
When the RNC fails to process the RAN-INFORMATION-REQUEST/Multiple Report that

requests load information from the LTE side, this counter is increased by one.This counter is
measured at point A as shown in Figure 2.
Issue 03 (2015-06-30)

218
BSC6900 UMTS
Figure 1-88 RNC failing to process RIM request from the LTE side(multiple mode)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RIM.L2U.Load.Fail
WRFD-140224

RIM
WRFD-150231

1.4.7 PS Traffic Measurement per Iu Interface(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.
Issue 03 (2015-06-30)

219
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203893
VS.IuPS.BytesPayl
dConv.Tx
Number of UL Bytes
of PS Conversational
Service on Iu-PS
Interface
Earlier than
BSC6900
V900R011
67203894
VS.IuPS.BytesPayl
dStr.Tx
Number of UL Bytes
of PS Streaming
Service on Iu-PS
Interface
Earlier than
BSC6900
V900R011
67203897
VS.IuPS.BytesPayl
dIntact.Tx
Number of UL Bytes
of PS Interactive
Service on Iu-PS
Interface
Earlier than
BSC6900
V900R011
67203898
VS.IuPS.BytesPayl
dBgrd.Tx
Number of UL Bytes
of PS Background
Service on Iu-PS
Interface
Earlier than
BSC6900
V900R011
67203895
VS.IuPS.BytesPayl
dConv.Rx
Number of DL Bytes
Service on Iu-PS
Interface
Earlier than
BSC6900
V900R011
67203896
VS.IuPS.BytesPayl
dStr.Rx
Number of DL Bytes
of PS Streaming
Service on Iu-PS
Interface
Earlier than
BSC6900
V900R011
67203899
VS.IuPS.BytesPayl
dIntact.Rx
Number of DL Bytes
of PS Interactive
Service on Iu-PS
Interface
Earlier than
BSC6900
V900R011
67203900
VS.IuPS.BytesPayl
dBgrd.Rx
Number of DL Bytes
of PS Background
Service on Iu-PS
Interface
Earlier than
BSC6900
V900R011
67204829
VS.IuPS.GoldenBE
.Bytes.Tx
Number of UL Bytes
of PS BE Service for
Golden Subscriber
on Iu-PS Interface
Earlier than
BSC6900
V900R011
67204830
VS.IuPS.SilverBE.
Bytes.Tx
Number of UL Bytes
Silver Subscriber on
Iu-PS Interface
Earlier than
BSC6900
V900R011

220
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204831
VS.IuPS.CopperB
E.Bytes.Tx
Number of UL Bytes
Copper Subscriber
on Iu-PS Interface
Earlier than
BSC6900
V900R011
67204832
VS.IuPS.GoldenBE
.Bytes.Rx
Number of DL Bytes
Golden Subscriber
on Iu-PS Interface
Earlier than
BSC6900
V900R011
67204833
VS.IuPS.SilverBE.
Bytes.Rx
Number of DL Bytes
Silver Subscriber on
Iu-PS Interface
Earlier than
BSC6900
V900R011
67204834
VS.IuPS.CopperB
E.Bytes.Rx
Number of DL Bytes
Copper Subscriber
on Iu-PS Interface
Earlier than
BSC6900
V900R011
73441084
VS.IuPS.BytesPayl
dHTTP.Rx
Total HTTP Traffic

Volume on the RNC
BSC6900
V900R013
73441081
VS.IuPS.BytesPayl
dP2P.Rx
Total P2P Traffic

Volume on the RNC
BSC6900
V900R013
73441082
VS.IuPS.BytesPayl
dSubs.Rx
Total Traffic Volume

of all Subscribed
Services on the RNC
BSC6900
V900R013
73441083
VS.IuPS.BytesPayl
dUndefined.Rx
Total Traffic Volume

of Undefined
Services on the RNC
BSC6900
V900R013
73426124
VS.IuPS.BytesPayl
dUnawareness.RX
Traffic Volume of
Services Cannot Be
Identified by the
RNC on Downlink
BSC6900
V900R015C00
None
Issue 03 (2015-06-30)

221
BSC6900 UMTS
Number of UL Bytes of PS Conversational Service on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67203893
VS.IuPS.BytesPayldConv.T
x
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
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldConv.T
x
WRFD-010501
Number of UL Bytes of PS Streaming Service on Iu Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67203894
VS.IuPS.BytesPayldStr.Tx
Streaming Service on Iu-PS
Interface

222
BSC6900 UMTS
Description
This counter provides the number of UL payload bytes of PS streaming service data on the IuPS interface sent by the RNC. The value of this counter includes the bytes of application layer
Measurement point
When receiving the UL PS streaming service data on the Iu-PS interface, the RNC measures the
counter according to different Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldStr.Tx
WRFD-010502
Streaming QoS Class
Number of UL Bytes of PS Interactive Service on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67203897
VS.IuPS.BytesPayldIntact.T
x
Interactive Service on Iu-PS
Interface
Description
This counter provides the number of UL payload bytes of PS interactive service data on the IuPS interface sent by the RNC. The value of this counter includes the bytes of application layer
Measurement point
When receiving the UL PS interactive service data on the Iu-PS interface, the RNC measures
Issue 03 (2015-06-30)

223
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldIntact.T
x
WRFD-010503
Number of UL Bytes of PS Background Service on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67203898
VS.IuPS.BytesPayldBgrd.T
x
Background Service on IuPS Interface
Description
This counter provides the number of UL payload bytes of PS background service data on the IuPS interface sent by the RNC. The value of this counter includes the bytes of application layer
Measurement point
When receiving the UL PS background service data on the Iu-PS interface, the RNC measures
Formula
None
Unit
byte
Issue 03 (2015-06-30)

224
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldBgrd.T
x
WRFD-010504
Number of DL Bytes of PS Conversational Service on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67203895
VS.IuPS.BytesPayldConv.R
x
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldConv.R
x
WRFD-010501

225
BSC6900 UMTS
Number of DL Bytes of PS Streaming Service on Iu Interface

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

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67203899
VS.IuPS.BytesPayldIntact.R
x
Interactive Service on Iu-PS
Interface

226
BSC6900 UMTS
Description
This counter provides the number of DL payload bytes of PS interactive service data on the IuPS interface received by the RNC. The value of this counter includes the bytes of application
Measurement point
When receiving the DL PS interactive service data on the Iu-PS interface, the RNC measures
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldIntact.R
x
WRFD-010503
Number of DL Bytes of PS Background Service on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67203900
VS.IuPS.BytesPayldBgrd.R
x
Background Service on IuPS Interface
Description
This counter provides the number of DL payload bytes of PS background service data on the IuPS interface received by the RNC. The value of this counter includes the bytes of application
Measurement point
When receiving the DL PS background service data on the Iu-PS interface, the RNC measures
Issue 03 (2015-06-30)

227
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldBgrd.R
x
WRFD-010504
Number of UL Bytes of PS BE Service for Golden Subscriber on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67204829
VS.IuPS.GoldenBE.Bytes.T
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
Issue 03 (2015-06-30)

228
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.GoldenBE.Bytes.T
x
WRFD-020806
Differentiated Service Based

on SPI Weight
Number of UL Bytes of PS BE Service for Silver Subscriber on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67204830
VS.IuPS.SilverBE.Bytes.Tx
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IuPS.SilverBE.Bytes.Tx
WRFD-020806

on SPI Weight

229
BSC6900 UMTS
Number of UL Bytes of PS BE Service for Copper Subscriber on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67204831
VS.IuPS.CopperBE.Bytes.T
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
Counter Name
Feature ID
Feature Name
VS.IuPS.CopperBE.Bytes.T
x
WRFD-020806

on SPI Weight
Number of DL Bytes of PS BE Service for Golden Subscriber on Iu Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204832
VS.IuPS.GoldenBE.Bytes.R
x

230
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
Counter Name
Feature ID
Feature Name
VS.IuPS.GoldenBE.Bytes.R
x
WRFD-020806

on SPI Weight
Number of DL Bytes of PS BE Service for Silver Subscriber on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67204833
VS.IuPS.SilverBE.Bytes.Rx
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
Issue 03 (2015-06-30)

231
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.SilverBE.Bytes.Rx
WRFD-020806

on SPI Weight
Number of DL Bytes of PS BE Service for Copper Subscriber on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67204834
VS.IuPS.CopperBE.Bytes.R
x
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
Issue 03 (2015-06-30)

232
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.CopperBE.Bytes.R
x
WRFD-020806

on SPI Weight
Total HTTP Traffic Volume on the RNC

Counters
Counter ID
Counter Name
Counter Description
73441084
VS.IuPS.BytesPayldHTTP.
Rx
Total HTTP Traffic Volume

on the RNC
Description
This counter provides the number of bytes of downlink HTTP services received on the Iu-PS
interface of the RNC. It includes the data at the application layer and excludes the GTP-U header.
The HTTP service type is identified by service awareness when the Web Browsing Acceleration
feature is enabled.
Measurement point
The 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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldHTTP.
Rx
WRFD-020132
Web browsing acceleration

233
BSC6900 UMTS
Total P2P Traffic Volume on the RNC

Counters
Counter ID
Counter Name
Counter Description
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
This measurement is triggered on different Iu-PS interfaces when the RNC receives the downlink
P2P traffic data on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldP2P.Rx
WRFD-020133
P2P Downloading Rate

Control during Busy Hour
Total Traffic Volume of all Subscribed Services on the RNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441082
VS.IuPS.BytesPayldSubs.R
x
Total Traffic Volume of all

Subscribed Services on the
RNC

234
BSC6900 UMTS
Description
This counter provides the number of bytes of downlink subscribed services received on the IuPS interface of the RNC. It includes the data at the application layer and excludes the GTPU
header. The subscribed service is defined by the Quality Improvement for Subscribed Service
feature.
Measurement point
data of subscribed services on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldSubs.R
x
WRFD-020128

Subscribed Service
Total Traffic Volume of Undefined Services on the RNC

Counters
Counter ID
Counter Name
Counter Description
73441083
VS.IuPS.BytesPayldUndefin
ed.Rx
Total Traffic Volume of

Undefined Services on the
RNC
Description
This counter provides the number of bytes of downlink undefined services received on the IuPS interface of the RNC. It includes the data at the application layer and excludes the GTP-U
header. Undefined services are services other than the HTTP services, P2P services, subscribed
services, and unidentified services. Examples of undefined services are video and VoIP.
If the Web browsing acceleration feature is not enabled, the traffic of HTTP services is also
measured by this counter. If the P2P Downloading Rate Control during Busy Hour feature is not
enabled, the traffic of P2P services is also measured by this counter.
Issue 03 (2015-06-30)

235
BSC6900 UMTS
Measurement point
data of undefined services on Iu-PS interfaces.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldUndefin
ed.Rx
WRFD-020132
WRFD-020133

WRFD-020128

Subscribed Service
Traffic Volume of Services Cannot Be Identified by the RNC on Downlink

Counters
Counter ID
Counter Name
Counter Description
73426124
VS.IuPS.BytesPayldUnawar
eness.RX
Traffic Volume of Services

Cannot Be Identified by the
RNC on Downlink
Description
This counter provides the number of bytes of downlink unidentified services received on the IuPS interface of the RNC. It includes the data at the application layer and excludes the GTPU
header. Unidentified services are those whose service type cannot be identified by service
awareness.
Measurement point
The measurement is triggered when the RNC receives downlink service data on the Iu-PS
interface. The traffic volume is measured on each Iu-PS interface separately.
Formula
None
Issue 03 (2015-06-30)

236
BSC6900 UMTS
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IuPS.BytesPayldUnawar
eness.RX
WRFD-020132
WRFD-020133

WRFD-020128

Subscribed Service
1.4.8 SCCP Measurement per 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195049
VS.IU.SCCP.Tx.Co
n.Req
Number of SCCP
Connection Requests
Sent to the CN
Through the Iu
Interface
Earlier than
BSC6900
V900R011
67195050
VS.IU.SCCP.Tx.Co
n.Succ
Number of
Successful SCCP
Connection Requests
Sent to the CN
Through the Iu
Interface
Earlier than
BSC6900
V900R011
67195051
VS.IU.SCCP.Rx.C
on.Req
Number of SCCP
Connection Requests
from the CN
Through the Iu
Interface
Earlier than
BSC6900
V900R011

237
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67195052
VS.IU.SCCP.Rx.C
on.Succ
Number of
Successful SCCP
Connection Requests
from the CN
Through the Iu
Interface
Earlier than
BSC6900
V900R011
None
Number of SCCP Connection Requests Sent by the RNC to the CN Through the Iu
Interface
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "1.2.1
Connection establishment" in ITU-T Q714.
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.
Issue 03 (2015-06-30)

238
BSC6900 UMTS
Figure 1-89 SCCP connection procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.SCCP.Tx.Con.Req
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

239
BSC6900 UMTS
Number of Successful SCCP Connection Requests Sent by the RNC to the CN

Through the Iu Interface
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "1.2.1
Measurement point
one when the local RNC RANAP receives a Connection Confirm (CC) message from the CN
after sending a Connection Request (CR) message to the CN.
Formula
None
Issue 03 (2015-06-30)

240
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.SCCP.Tx.Con.Succ
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of SCCP Connection Requests Received by the RNC from the CN Through
the Iu Interface
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "1.2.1 Connection
establishment" in ITU-T Q714.
Measurement point
The measurement is triggered at point A as shown in the figure. In the measurement period, the
counter is incremented by one when the RNC RANAP receives a SCCP CR message from the
CN.
Issue 03 (2015-06-30)

241
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.SCCP.Rx.Con.Req
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

242
BSC6900 UMTS
Number of Successful SCCP Connection Requests Received by the RNC from the
CN Through the Iu Interface
Counters
Counter ID
Counter Name
Counter Description
67195052
VS.IU.SCCP.Rx.Con.Succ

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.This counter complies with section "1.2.1
Measurement point
one when the local RNC RANAP sends a Connection Confirm (CC) message to the CN after
receiving a Connection Request (CR) message from the CN.
Formula
None
Issue 03 (2015-06-30)

243
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
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.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
DRNC.IUR
DRNC Measurement per Iur Interface
RESERVE.IUR
Reserved Counter Measurement per Iur

Interface
SIG.SCCP.IUR
SCCP Measurement per Iur Interface
SRNC.IUR
SRNC Measurement per Iur Interface
TRFFIC.IUR
Traffic Measurement per Iur Interface
1.5.1 DRNC Measurement per 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.
Issue 03 (2015-06-30)

244
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179009
VS.SHO.ErrIndIur
.Rx
Number of Error
Indication Messages
Received on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
67179010
VS.SHO.ErrIndIur
.Tx
Number of Error
Indication Messages
Sent on Iur Interface
for DRNC
Earlier than
BSC6900
V900R011
67179089
VS.SHO.AttRLSet
upIur.Rx
Number of Radio
Link Setup Requests
on Iur Interface for
DRNC
Earlier than
BSC6900
V900R011
67179090
VS.SHO.SuccRLSe
tupIur.Tx
Number of
Successful Radio
Link Setups on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
67179092
VS.SHO.FailRLSet
upIur.HW.Tx
Number of Failed
Radio Link Setups on
Iur Interface for
DRNC (Device
Fault)
Earlier than
BSC6900
V900R011
67179093
VS.SHO.FailRLSet
upIur.CongTx
Number of Failed
Iur Interface for
DRNC (Congestion)
Earlier than
BSC6900
V900R011
67179094
VS.SHO.FailRLSet
upIur.CfgUTx
Number of Failed
Iur Interface for
DRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67179096
VS.SHO.AttRLDel
Iur.Rx
Number of Radio
Link Deletion
Requests on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
67179097
VS.SHO.SuccRLD
elIur.Tx
Number of
Successful Radio
Link Deletions on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011

245
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179098
VS.SHO.AttRLAd
dIur.Rx
Number of Radio
Link Addition
Requests on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
67179099
VS.SHO.SuccRLA
ddIur.Tx
Number of
Successful Radio
Link Additions on
Iur Interface for
DRNC
Earlier than
BSC6900
V900R011
67179100
VS.SHO.FailRLAd
dIur.OM.Tx
Number of Failed
Radio Link
Additions on Iur
Interface for DRNC
(OM Intervention)
Earlier than
BSC6900
V900R011
67179101
VS.SHO.FailRLAd
dIur.HW.Tx
Number of Failed
Radio Link
Additions on Iur
Interface for DRNC
(Device Fault)
Earlier than
BSC6900
V900R011
67179102
VS.SHO.FailRLAd
dIur.Cong.Tx
Number of Failed
Radio Link
Additions on Iur
Interface for DRNC
(Congestion)
Earlier than
BSC6900
V900R011
67179103
VS.SHO.FailRLAd
dIur.CfgUnsTx
Number of Failed
Radio Link
Additions on Iur
Interface for DRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67179105
VS.SHO.AttRLRec
fgIur.Rx
Number of Radio
Link Synchronous
Reconfiguration
Requests on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
67179106
VS.SHO.SuccRLR
ecfgIur.Tx
Number of
Successful Radio
Link Synchronous
Reconfigurations on
Iur Interface for
DRNC
Earlier than
BSC6900
V900R011

246
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179109
VS.SHO.FailRLRe
cfgIur.CongTx
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
DRNC (Congestion)
Earlier than
BSC6900
V900R011
67179110
VS.SHO.FailRLRe
cfgIur.CfgUTx
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
DRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67179107
VS.SHO.FailRLRe
cfgIur.OM.Tx
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
DRNC (OM
Intervention)
Earlier than
BSC6900
V900R011
67179108
VS.SHO.FailRLRe
cfgIur.HW.Tx
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
DRNC (Device
Fault)
Earlier than
BSC6900
V900R011
67192579
VS.SHO.FailRLRe
cfgIur.TransCongRx
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
DRNC (Transport
Resource
Unavailable)
Earlier than
BSC6900
V900R011
67192580
VS.SHO.FailRLSet
upIur.TransCongTx
Number of Failed
Iur Interface for
DRNC (Transport
Resource
Unavailable)
Earlier than
BSC6900
V900R011

247
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192581
VS.SHO.FailRLAd
dIur.TransCong.T
x
Number of Failed
Radio Link
Additions on Iur
Interface for DRNC
(Transport Resource
Unavailable)
Earlier than
BSC6900
V900R011
67179112
VS.SHO.CancelRL
RecfgIur.Rx
Number of Radio
Link Synchronous
Reconfiguration
Cancellations on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
67179113
VS.SHO.RLFail.Tx
Number of Radio
Link Failures on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
67179114
VS.SHO.RLFail.O
M.Tx
Number of Radio
Interface for DRNC
(OM Intervention)
Earlier than
BSC6900
V900R011
67179115
VS.SHO.RLFail.H
W.Tx
Number of Radio
Interface for DRNC
(Device Fault)
Earlier than
BSC6900
V900R011
67179116
VS.SHO.RLFail.Sy
ncFail.Tx
Number of Radio
Interface for DRNC
(Synchronization
Failure)
Earlier than
BSC6900
V900R011
67179117
VS.SHO.RLFail.Cf
gUnsup.Tx
Number of Radio
Interface for DRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67190048
VS.SHO.RLFail.Ot
her.Tx
Number of Radio
Interface for DRNC
(Other Reasons)
Earlier than
BSC6900
V900R011
67179118
VS.SHO.RLRestor
e.Tx
Number of Radio
Link Restorations on
Iur Interface for
DRNC
Earlier than
BSC6900
V900R011

248
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179119
VS.IUR.AttComTraChResDRNC
Number of Common
Transport Channel
Resource Requests
DRNC
Earlier than
BSC6900
V900R011
67179120
VS.IUR.SuccComTraChResDRNC
Number of Common
Transport Channel
Resource Responses
DRNC
Earlier than
BSC6900
V900R011
67179121
VS.IUR.FailCTCR
DRNC.NotSupp
Number of Common
Transport Channel
Resource Failures
Due to Transport
Resource
Unavailable on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
67179122
VS.IUR.AttRelCoTrChResDRNC
Number of Common
Transport Channel
Resource Release
Requests on Iur
Interface for DRNC
Earlier than
BSC6900
V900R011
73423641
VS.SHO.FailRLSet
upIur.NodeBReHo
st.Tx
Number of Failed
Iur interface for
DRNC (NodeB
Rehoming)
BSC6900
V900R014
73423642
VS.SHO.FailRLAd
dIur.NodeBReHost
.Tx
Number of Failed
Radio Link
Additions on Iur
interface for DRNC
(NodeB Rehoming)
BSC6900
V900R014
73429236
VS.ExtdPaging1.At
t.Idle.CS.DRNC
Number of Extended
Paging Attempts
Triggered by CS
Conversational
Services to Page UEs
in Idle Mode over the
Iur Interface for
DRNC
BSC6900
V900R017C00

249
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430082
VS.Paging.Parallel.
Request.Iur
Number of Parallel
Paging Procedure
Requests Received
by an RNC over the
Iur Interface
BSC6900
V900R017C10
73430178
VS.Paging.Parallel.
Att.Iur
Number of Times the

RNC Initiates a
Paging Procedure
After Receiving a
Parallel Paging
Request over Iur
Interface
BSC6900
V900R017C10
Each counter's value equals the sum of its subcounters' values
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
Number of ERROR INDICATION Messages Received by the RNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179009
VS.SHO.ErrIndIur.Rx

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.This counter complies with section "8.5.1 Error Indication" in 3GPP TS
25.423 (v10.10.0).
Issue 03 (2015-06-30)

250
BSC6900 UMTS
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-93 Error indication receiving procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.ErrIndIur.Rx
WRFD-020203
Inter RNC Soft Handover
Number of ERROR INDICATION Messages Sent by the RNC on Iur Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179010
VS.SHO.ErrIndIur.Tx

Messages Sent on Iur
Interface for DRNC

251
BSC6900 UMTS
Description
This counter provides the number of ERROR INDICATION messages sent on the Iur interface
for the DRNC.This counter complies with section "8.5.1 Error Indication" in 3GPP TS 25.423
(v10.10.0).
Measurement point
INDICATION message to another RNC, it measures this item.
Figure 1-94 Error indication sending procedure on the Iur interface
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.ErrIndIur.Tx
WRFD-020203

252
BSC6900 UMTS
Number of Requests to Establish a Radio Link Received by DRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.3.1 Radio Link Setup" in
3GPP TS 25.423 (v10.10.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC receives a
RADIO LINK SETUP REQUEST message from the SRNC, it measures this item on each Iur
interface.
Figure 1-95 Radio Link setup procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Issue 03 (2015-06-30)

253
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLSetupIur.Rx
WRFD-020203
Number of Successful Radio Link Establishments by DRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179090
VS.SHO.SuccRLSetupIur.T
x
Number of Successful Radio

Link Setups on Iur Interface
for DRNC
Description
This measurement item takes statistics of the number of successful radio link establishments by
a DRNC on the Iur interface.This counter complies with section "8.3.1.2 Successful Operation"
in 3GPP TS 25.423 (v10.10.0).
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.
Issue 03 (2015-06-30)

254
BSC6900 UMTS
The measurement is triggered at point B, as shown in the figure. When the DRNC sends the
SRNC a RADIO LINK SETUP FAILURE message and the message indicates that there are
successfully established radio links, this item is measured on each Iur interface.
Figure 1-97 Radio Link setup procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLSetupIur.T
x
WRFD-020203
Number of Radio Links Unsuccessfully Established by DRNC on Iur Interface for

Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179092
VS.SHO.FailRLSetupIur.H
W.Tx
Number of Failed Radio Link

Setups on Iur Interface for
DRNC (Device Fault)

255
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67179093
VS.SHO.FailRLSetupIur.Co
ngTx

DRNC (Congestion)
67179094
VS.SHO.FailRLSetupIur.Cf
gUTx

DRNC (Configuration
Unsupported)
67192580
VS.SHO.FailRLSetupIur.Tr
ansCongTx

DRNC (Transport Resource
Unavailable)
73423641
VS.SHO.FailRLSetupIur.No
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.This counter complies with section
"8.3.1.3 Unsuccessful Operation" in 3GPP TS 25.423 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
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

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)

256
BSC6900 UMTS
Counter Name
Description
VS.SHO.FailRLSetupIur.CfgUTx

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

because of insufficient RNC transmission
capability (cause value: Transport Resource
Unavailable)
VS.SHO.FailRLSetupIur.NodeBReHost.Tx

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-98 Radio Link setup procedure on the Iur interface (failed operation)
Formula
None
Issue 03 (2015-06-30)

257
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
W.Tx
WRFD-020203
ngTx
WRFD-020203
gUTx
WRFD-020203
ansCongTx
WRFD-020203
deBReHost.Tx
WRFD-020203
WRFD-040202
RNC Node Redundancy
Number of Radio Links to Be Deleted by DRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.3.3.2 Successful Operation"
in 3GPP TS 25.423 (v10.10.0).
Measurement point
RADIO LINK DELETION REQUEST message from the SRNC, this item shall be measured
on each Iur interface.
Issue 03 (2015-06-30)

258
BSC6900 UMTS
Figure 1-99 Radio Link deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLDelIur.Rx
WRFD-020203
Number of Successful Radio Link Deletions by DRNC on Iur Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179097
VS.SHO.SuccRLDelIur.Tx

Link Deletions on Iur
Interface for DRNC

259
BSC6900 UMTS
Description
This measurement item takes statistics of the number of successful radio link deletions by a
DRNC on the Iur interface.This counter complies with section "8.3.3.2 Successful Operation"
in 3GPP TS 25.423 (v10.10.0).
Measurement point
SRNC a RADIO LINK DELETION RESPONSE message, this item shall be measured on each
Iur interface.
Figure 1-100 RL deletion procedure (successful operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLDelIur.Tx
WRFD-020203

260
BSC6900 UMTS
Number of Radio Link Addition Requests by DRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179098
VS.SHO.AttRLAddIur.Rx

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.This counter complies with section "8.3.2.2 Successful Operation" in
3GPP TS 25.423 (v10.10.0).
Measurement point
RADIO LINK ADDITION REQUEST message from the SRNC, this item shall be measured
Figure 1-101 Radio Link addition procedure (successful operation)
Formula
None
Unit
None
Issue 03 (2015-06-30)

261
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLAddIur.Rx
WRFD-020203
Number of Successful Radio Link Additions on DRNC Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179099
VS.SHO.SuccRLAddIur.Tx

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.This counter complies with section "8.3.2.2 Successful Operation"
in 3GPP TS 25.423 (v10.10.0).
Measurement point
The measurement is triggered at point B, as shown in the figure, when the DRNC sends the
SRNC a RADIO LINK ADDITION RESPONSE message, this item shall be measured on each
Iur interface..
Figure 1-102 Radio Link addition procedure (successful operation)
Issue 03 (2015-06-30)

262
BSC6900 UMTS
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-103 Radio Link addition procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLAddIur.Tx
WRFD-020203
Number of Failed Radio Links Additions by DRNC on Iur Interface for Different
Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179100
VS.SHO.FailRLAddIur.OM
.Tx

Additions on Iur Interface for
DRNC (OM Intervention)

263
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67179101
VS.SHO.FailRLAddIur.HW
.Tx

DRNC (Device Fault)
67179102
VS.SHO.FailRLAddIur.Con
g.Tx

DRNC (Congestion)
67179103
VS.SHO.FailRLAddIur.Cfg
UnsTx

DRNC (Configuration
Unsupported)
67192581
VS.SHO.FailRLAddIur.Tra
nsCong.Tx

DRNC (Transport Resource
Unavailable)
73423642
VS.SHO.FailRLAddIur.Nod
eBReHost.Tx

Additions on Iur interface for
DRNC (NodeB Rehoming)
Description
The measurement items provide the number of failed radio link additions by a DRNC on the Iur
interface according to different causes.This counter complies with section "8.3.2.3 Unsuccessful
Operation" in 3GPP TS 25.423 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
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

DRNC on Iur interface because of hardware
failure (cause value: Hardware Failure)

264
BSC6900 UMTS
Counter Name
Description
VS.SHO.FailRLAddIur.Cong.Tx

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

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

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.
Issue 03 (2015-06-30)

265
BSC6900 UMTS
Figure 1-104 Radio Link addition procedure on the Iur interface (failed operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.FailRLAddIur.OM
.Tx
WRFD-020203
.Tx
WRFD-020203
g.Tx
WRFD-020203
UnsTx
WRFD-020203
nsCong.Tx
WRFD-020203
eBReHost.Tx
WRFD-020203
WRFD-040202
RNC Node Redundancy

266
BSC6900 UMTS
Number of Radio Links to Be Reconfigured by DRNC

Counters
Counter ID
Counter Name
Counter Description
67179105
VS.SHO.AttRLRecfgIur.Rx

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.This counter complies with section "8.3.4.2 Successful
Measurement point
RADIO LINK RECONFIGURATION PREPARE message, this item shall be measured on each
Iur interface.
Figure 1-105 Radio Link synchronous reconfiguration preparation procedure (successful
operation)
Formula
None
Issue 03 (2015-06-30)

267
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLRecfgIur.Rx
WRFD-020203
Number of Radio Links Successfully Reconfigured by DRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179106
VS.SHO.SuccRLRecfgIur.T
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.This counter complies with section "8.3.4.2
Successful Operation" in 3GPP TS 25.423 (v10.10.0).
Measurement point
The measurement is triggered at point C, as shown in the figure. When the DRNC receives a
RADIO LINK RECONFIGURATION COMMIT message from the SRNC, this item shall be
measured on each Iur interface.
Issue 03 (2015-06-30)

268
BSC6900 UMTS
Figure 1-106 Successful radio link synchronous reconfiguration procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLRecfgIur.T
x
WRFD-020203

269
BSC6900 UMTS
Number of Failed Radio Link Synchronous Reconfigurations by DRNC on Iur

Interface for Different Causes
Counters
Counter ID
Counter Name
Counter Description
67179107
VS.SHO.FailRLRecfgIur.O
M.Tx

Synchronous
Interface for DRNC (OM
Intervention)
67179109
VS.SHO.FailRLRecfgIur.C
ongTx

Synchronous
Interface for DRNC
(Congestion)
67179110
VS.SHO.FailRLRecfgIur.Cf
gUTx

Synchronous
Interface for DRNC
(Configuration
Unsupported)
67179108
VS.SHO.FailRLRecfgIur.H
W.Tx

Synchronous
Interface for DRNC (Device
Fault)
67192579
VS.SHO.FailRLRecfgIur.Tr
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.The preceding counters comply
with section "8.3.4.3 Unsuccessful Operation" in 3GPP TS 25.423 (v10.10.0).
Issue 03 (2015-06-30)

270
BSC6900 UMTS
Counter Name
Description
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)
VS.SHO.FailRLRecfgIur.CongTx

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

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

because of hardware failure (cause value:
Hardware Failure)
VS.SHO.FailRLRecfgIur.TransCongRx

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.
Issue 03 (2015-06-30)

271
BSC6900 UMTS
Figure 1-107 Synchronized RL reconfiguration procedure (failed operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.FailRLRecfgIur.O
M.Tx
WRFD-020203
ongTx
WRFD-020203
gUTx
WRFD-020203
W.Tx
WRFD-020203
VS.SHO.FailRLRecfgIur.Tr
ansCongRx
WRFD-020203

272
BSC6900 UMTS
Number of Radio Links with Reconfiguration Canceled by the DRNC over Iur
Counters
Counter ID
Counter Name
Counter Description
67179112
VS.SHO.CancelRLRecfgIur
.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.This counter complies with section "8.3.6
Synchronised Radio Link Reconfiguration Cancellation" in 3GPP TS 25.423 (v10.10.0).
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-108 Radio link reconfiguration cancellation procedure over Iur
Issue 03 (2015-06-30)

273
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.Rx
WRFD-020203
Number of Radio Link Failures on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179113
VS.SHO.RLFail.Tx

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.This counter complies with section "8.3.9 Radio Link Failure" in 3GPP TS 25.423
(v10.10.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC sends a RADIO
LINK FAILURE INDICATION message to the SRNC, this item shall be measured on each Iur
interface.
Issue 03 (2015-06-30)

274
BSC6900 UMTS
Figure 1-109 RL failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.RLFail.Tx
WRFD-020203
Number of Failed Radio Links on Iur Interface for Different Causes

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179114
VS.SHO.RLFail.OM.Tx

DRNC (OM Intervention)

275
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67179115
VS.SHO.RLFail.HW.Tx

DRNC (Device Fault)
67179116
VS.SHO.RLFail.SyncFail.T
x

DRNC (Synchronization
Failure)
67179117
VS.SHO.RLFail.CfgUnsup.
Tx

DRNC (Configuration
Unsupported)
67190048

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.This counter complies with section "8.3.9 Radio Link Failure" in 3GPP TS 25.423
(v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.SHO.RLFail.OM.Tx
Number of failed radio links on Iur Interface

Because of OM Intervention (OM
Intervention)
VS.SHO.RLFail.HW.Tx

Because of Hardware Failure (Hardware
Failure)
VS.SHO.RLFail.SyncFail.Tx

Because of Synchronization Failure
(Synchronization Failure)
VS.SHO.RLFail.CfgUnsup.Tx

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)

276
BSC6900 UMTS
Counter Name
Description

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-110 Radio Link failure procedure on the Iur interface
Formula
None
Unit
None
Issue 03 (2015-06-30)

277
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.RLFail.OM.Tx
WRFD-020203
VS.SHO.RLFail.HW.Tx
WRFD-020203
VS.SHO.RLFail.SyncFail.T
x
WRFD-020203
VS.SHO.RLFail.CfgUnsup.
Tx
WRFD-020203
WRFD-020203
Number of RADIO LINK RESTORE INDICATION Messages sent by DRNC on

Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67179118
VS.SHO.RLRestore.Tx

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.This counter complies with section
"8.3.10 Radio Link Restoration" in 3GPP TS 25.423 (v10.10.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When the DRNC sends the
SRNC a RADIO LINK RESTORE INDICATION message, this item shall be measured on each
Iur interface.
Issue 03 (2015-06-30)

278
BSC6900 UMTS
Figure 1-111 Radio Link restoration procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.RLRestore.Tx
WRFD-020203
Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST

Messages Received by DRNC on Iur Interface
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179119
Number of Common
Transport Channel Resource
Requests on Iur Interface for
DRNC

279
BSC6900 UMTS
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-112 Common transport channel resources initialization procedure on the Iur interface
Formula
None
Unit
None
Issue 03 (2015-06-30)

280
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010802
Inter RNC Cell Update
Number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE

Messages Sent by DRNC on Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67179120
Number of Common
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.
Issue 03 (2015-06-30)

281
BSC6900 UMTS
Figure 1-113 Common transport channel resources initialization procedure on the Iur interface
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010802

282
BSC6900 UMTS
Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE

Messages sent by DRNC on the Iur Interface due to Transport Resource
Unavailable
Counters
Counter ID
Counter Name
Counter Description
67179121
VS.IUR.FailCTCRDRNC.N
otSupp
Number of Common
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-114 Common transport channel resources failure procedure on the Iur interface
Issue 03 (2015-06-30)

283
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUR.FailCTCRDRNC.N
otSupp
WRFD-010802
Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE

REQUEST Messages Received by DRNC on Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67179122
Number of Common
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.
Issue 03 (2015-06-30)

284
BSC6900 UMTS
Figure 1-115 Common transport channel resources release procedure on the Iur interface
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010802

285
BSC6900 UMTS
Number of Extended Paging Attempts Triggered by CS Conversational Services to

Page UEs in Idle Mode over the Iur Interface for DRNC
Counters
Counter ID
Counter Name
Counter Description
73429236
VS.ExtdPaging1.Att.Idle.CS
.DRNC
Number of Extended Paging

Attempts Triggered by CS
Conversational Services to
Page UEs in Idle Mode over
the Iur Interface for DRNC
Description
This counter provides the number of extended paging attempts triggered by CS conversational
services to page UEs in idle mode over the Iur interface in an extended LAC. This counter is
measured on the Iur interface for the DRNC.
Measurement point
The measurement is triggered at point A in figure 1. When the RNC receives a PAGING message
with the cause value "Terminating Conversational Call" from the CN, the RNC sends the paging
message to the DRNC over the Iur interface if the RNC determines to send the paging message
in an extended LA, the extended LA is under the DRNC, and the UE to be paged is in idle mode.
This counter is measured on the Iur interface for the DRNC.
Figure 1-116 An extended paging attempt triggered by CS conversational services to page UEs
in idle mode over the Iur interface for DRNC
Issue 03 (2015-06-30)

286
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.DRNC
WRFD-170104
Seamless Paging
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of Parallel Paging Procedure Requests Received by an RNC over the Iur
Interface
Counters
Counter ID
Counter Name
Counter Description
73430082
VS.Paging.Parallel.Request.
Iur
Number of Parallel Paging

Procedure Requests
Received by an RNC over the
Iur Interface
Description
This counter provides the number of parallel paging procedure requests received by an RNC
over the Iur interface.
Measurement point
The measurement is triggered at point A in the figure. When the DRNC receives a DIRECT
INFORMATION TRANSFER message from the SRNC over the Iur interface, requesting the
DRNC to initiate a parallel paging procedure, this counter is measured on the DRNC.
Issue 03 (2015-06-30)

287
BSC6900 UMTS
Figure 1-117 Parallel paging procedure over the Iur interface
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging.Parallel.Request.
Iur
WRFD-171202
Ultrafast CS Call Setup
Number of Times the RNC Initiates a Paging Procedure After Receiving a Parallel
Paging Request over Iur Interface
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430178
VS.Paging.Parallel.Att.Iur

Initiates a Paging Procedure
After Receiving a Parallel
Paging Request over Iur
Interface

288
BSC6900 UMTS
Description
This counter provides the number of times the RNC initiates a paging procedure after receiving
a parallel paging request over Iur interface.
Measurement point
This counter provides the number of times the parallel paging procedure is initiated by an RNC
over the Iur interface. The measurement is triggered at point A in the figure. When the DRNC
receives a DIRECT INFORMATION TRANSFER message from the SRNC over the Iur
interface, requesting the DRNC to initiate a parallel paging procedure, this counter is measured
after the DRNC sends a PAGING TYPE 1 message to the UE to initiate a parallel paging
procedure.
Figure 1-118 Parallel paging request procedure over the Iur interface
Formula
None
Unit
None
Issue 03 (2015-06-30)

289
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging.Parallel.Att.Iur
WRFD-171202
1.5.2 Reserved Counter Measurement per Iur Interface

(RESERVE.IUR)
Overview
Reserved counter for Iur interface.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423446
VS.Reserve.Counte
r1.Iur
Reserved counter 1
for Iur interface
BSC6900
V900R013
73423447
VS.Reserve.Counte
r2.Iur
Reserved counter 2
for Iur interface
BSC6900
V900R013
73423448
VS.Reserve.Counte
r3.Iur
Reserved counter 3
for Iur interface
BSC6900
V900R013
73423449
VS.Reserve.Counte
r4.Iur
Reserved counter 4
for Iur interface
BSC6900
V900R013
73423450
VS.Reserve.Counte
r5.Iur
Reserved counter 5
for Iur interface
BSC6900
V900R013
73423451
VS.Reserve.Counte
r6.Iur
Reserved counter 6
for Iur interface
BSC6900
V900R013
73423452
VS.Reserve.Counte
r7.Iur
Reserved counter 7
for Iur interface
BSC6900
V900R013
73423453
VS.Reserve.Counte
r8.Iur
Reserved counter 8
for Iur interface
BSC6900
V900R013
73423454
VS.Reserve.Counte
r9.Iur
Reserved counter 9
for Iur interface
BSC6900
V900R013
73423455
VS.Reserve.Counte
r10.Iur
Reserved counter 10
for Iur interface
BSC6900
V900R013

290
BSC6900 UMTS
None
Reserved counters for Iur interface

Counters
Counter ID
Counter Name
Counter Description
73423446
VS.Reserve.Counter1.Iur
Reserved counter 1 for Iur

interface
73423447

interface
73423448

interface
73423449

interface
73423450

interface
73423451

interface
73423452

interface
73423453

interface
73423454

interface
73423455

interface
Description
Reserved counters for Iur interface.
Measurement point
Reserved counters for Iur interface.
Formula
None
Issue 03 (2015-06-30)

291
BSC6900 UMTS
Unit
None
Related Features
None
1.5.3 SCCP Measurement per Iur Interface(SIG.SCCP.IUR)

Overview
Measurement related to SCCP for Iur interface provides the counters related to the numbers of
the local-RNC-initiated SCCP connection requests, local-RNC-initiated successful SCCP
connection requests, peer-RNC-initiated SCCP connection requests, and peer-RNC-initiated
successful SCCP connection requests.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67195053
VS.IUR.SCCP.Tx.
Con.Req
Number of SCCP
Connection Requests
Sent to Other RNC
Through the Iur
Interface
Earlier than
BSC6900
V900R011
67195054
VS.IUR.SCCP.Tx.
Con.Succ
Number of
Successful SCCP
Connection Requests
Sent to Other RNC
Through the Iur
Interface
Earlier than
BSC6900
V900R011
67195055
VS.IUR.SCCP.Rx.
Con.Req
Number of SCCP
Connection Requests
from Other RNC
Through the Iur
Interface
Earlier than
BSC6900
V900R011
67195056
VS.IUR.SCCP.Rx.
Con.Succ
Number of
Successful SCCP
Connection Requests
from Other RNC
Through the Iur
Interface
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

292
BSC6900 UMTS
Number of SCCP Connection Requests Sent by the Local RNC to the Peer RNC
Through the Iur Interface
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "1.2.1 Connection establishment" in ITU-T Q714.
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-119 SCCP connection requests sent by the local RNC to the peer RNC
Issue 03 (2015-06-30)

293
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUR.SCCP.Tx.Con.Req
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Successful SCCP Connection Requests Sent by the Local RNC to the
Peer RNC Through the Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67195054
VS.IUR.SCCP.Tx.Con.Succ

Interface
Description
This counter provides the successful number of SCCP connection requests sent by the local RNC
to the peer RNC.This counter complies with section "1.2.1 Connection establishment" in ITUT Q714.
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.
Issue 03 (2015-06-30)

294
BSC6900 UMTS
Figure 1-120 Successful SCCP connection requests sent by the local RNC to the peer RNC
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IUR.SCCP.Tx.Con.Succ
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

295
BSC6900 UMTS
Number of SCCP Connection Requests Received by the Local RNC from the Peer
RNC Through the Iur Interface
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "1.2.1 Connection establishment" in ITU-T
Q714.
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-121 SCCP connection requests received by the local RNC from the peer RNC
Issue 03 (2015-06-30)

296
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUR.SCCP.Rx.Con.Req
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Successful SCCP Connection Requests Received by the Local RNC

from the Peer RNC Through the Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67195056
VS.IUR.SCCP.Rx.Con.Succ

Interface
Description
This counter provides the number of successful SCCP connection requests received by the local
RNC from the peer RNC.This counter complies with section "1.2.1 Connection establishment"
in ITU-T Q714.
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.
Issue 03 (2015-06-30)

297
BSC6900 UMTS
Figure 1-122 Successful SCCP connection requests received by the local RNC from the peer
RNC
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUR.SCCP.Rx.Con.Succ
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.5.4 SRNC Measurement per 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
Issue 03 (2015-06-30)

298
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179025
VS.SHO.AttRLSet
upIur.Tx
Number of Radio
Link Setup Requests
on Iur Interface from
SRNC
Earlier than
BSC6900
V900R011
67179026
VS.SHO.SuccRLSe
tupIur.Rx
Number of Radio
Links Successfully
Set Up on the Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
67179028
VS.SHO.FailRLSet
upIur.HW.Rx
Number of Radio
Link Setup Failures
SRNC (Device
Fault)
Earlier than
BSC6900
V900R011
67179029
VS.SHO.FailRLSet
upIur.Cong.Rx
Number of Radio
Link Setup Failures
SRNC (Congestion)
Earlier than
BSC6900
V900R011
67179030
VS.SHO.FailRLSet
upIur.CfgUnsupp.
Rx
Number of Radio
Link Setup Failures
SRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67192577
VS.SHO.FailRLSet
upIur.TransCong.
Rx
Number of Radio
Link Setup Failures
SRNC (Transport
Resource
Unavailable)
Earlier than
BSC6900
V900R011
67192578
VS.SHO.FailRLAd
dIur.TransCong.R
x
Number of Radio
Link Addition
Failures on Iur
Interface for SRNC
(Transport Resource
Unavailable)
Earlier than
BSC6900
V900R011

299
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179032
VS.SHO.AttRLDel
Iur.Tx
Number of Radio
Links Deleted on Iur
Interface for SRNC
BSC6900
V900R012
67179033
VS.SHO.SuccRLD
elIur.Rx
Number of
Successful deleted
Radio Links on Iur
Interface for SRNC
BSC6900
V900R012
67179035
VS.SHO.AttRLAd
dIur.Tx
Number of Radio
Link Addition
Requests on Iur
Interface from SRNC
Earlier than
BSC6900
V900R011
67179036
VS.SHO.SuccRLA
ddIur.Rx
Number of
Successful Radio
Link Additions on
Iur Interface for
SRNC
Earlier than
BSC6900
V900R011
67179038
VS.SHO.FailRLAd
dIur.HW.Rx
Number of Failed
Radio Link
Additions on Iur
Interface for SRNC
(Device Fault)
Earlier than
BSC6900
V900R011
67179039
VS.SHO.FailRLAd
dIur.Cong.Rx
Number of Failed
Radio Link
Additions on Iur
Interface for SRNC
(Congestion)
Earlier than
BSC6900
V900R011
67179040
VS.SHO.FailRLAd
dIur.CfgUnsupp.R
x
Number of Failed
Radio Link
Additions on Iur
Interface for SRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67179042
VS.SHO.AttRLRec
fgIur.Tx
Number of Radio
Link
Reconfiguration
Requests on Iur
Interface from SRNC
Earlier than
BSC6900
V900R011

300
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179043
VS.SHO.SuccRLR
ecfgIur.Rx
Number of
Successful Radio
Link
Reconfigurations on
Iur Interface for
SRNC
Earlier than
BSC6900
V900R011
67179045
VS.SHO.FailRLRe
cfgIur.HW.Rx
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
SRNC (Device
Fault)
Earlier than
BSC6900
V900R011
67179046
VS.SHO.FailRLRe
cfgIur.Cong.Rx
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
SRNC (Congestion)
Earlier than
BSC6900
V900R011
67179047
VS.SHO.FailRLRe
cfgIur.CfgUnsupp.
Rx
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
SRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67179048
VS.SHO.FailRLRe
cfgIur.NoReply
Number of Failed
Radio Link
Synchronous
Reconfigurations on
Iur Interface for
SRNC (No
Response)
Earlier than
BSC6900
V900R011
67179051
VS.SHO.RLFailIn
dIur.Rx
Number of Radio
Interface for SRNC
Earlier than
BSC6900
V900R011
67179053
VS.SHO.RLFailIur
.HW.Rx
Number of Radio
Interface for SRNC
(Device Fault)
Earlier than
BSC6900
V900R011

301
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179054
VS.SHO.RLFailIur
.SyncFail.Rx
Number of Radio
Interface for SRNC
(Synchronization
Failure)
Earlier than
BSC6900
V900R011
67179055
VS.SHO.RLFailIur
.CfgUnsup.Rx
Number of Radio
Interface for SRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67179056
VS.SHO.RLRestor
eIur.Rx
Number of Radio
Link Restorations on
Iur Interface for
SRNC
Earlier than
BSC6900
V900R011
67179061
VS.SHO.Att.Iur
Number of Soft
Handovers Initiated
by SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67179062
VS.SHO.Succ.Iur
Number of
Successful Soft
Handovers Initiated
by SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67179057
VS.AttCommTrCh
ResIur.Tx
Number of Common
Transport Channel
Resource Requests
Sent by SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67179058
VS.SuccCommTrC
hResIur.Rx
Number of Common
Transport Channel
Resource Responses
Received by SRNC
on Iur Interface
Earlier than
BSC6900
V900R011
67179059
VS.FailCommTrC
hResIur.NotSupp.
Rx
Number of Common
Transport Channel
Resource Failures
Due to Transport
Resource
Unavailable on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011

302
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179060
VS.AttRelCommTr
ChResIur.Tx
Number of Common
Transport Channel
Resource Release
Requests on Iur
Interface from SRNC
Earlier than
BSC6900
V900R011
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)
Earlier than
BSC6900
V900R011
67191850
VS.RAB.NormRel.
PS.CCH.Iur
Number of PS RABs
Normally Released
SRNC (CCH User
Only)
Earlier than
BSC6900
V900R011
67191858
VS.RAB.NormRel.
AMR.Iur
Number of Normally
Released AMR
RABs on Iur
Interface for SRNC
(not including WBAMR)
Earlier than
BSC6900
V900R011
67191859
VS.RAB.AbnormR
el.AMR.Iur
Number of
Abnormally
Released AMR
RABs on Iur
Interface for SRNC
(not including WBAMR)
Earlier than
BSC6900
V900R011
67191860
VS.RAB.AbnormR
el.CS64.Iur
Number of CS
Conversational
RABs Abnormally
Released on the
SRNC Iur Interface
for SRNC
(Conversational with
DL Max Bitrate as
64kbit/s)
Earlier than
BSC6900
V900R011

303
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191865
VS.RAB.AbnormR
el.PS.CCH.Iur
Number of PS RABs
Abnormally
Released on Iur
Interface for SRNC
(CCH User Only)
Earlier than
BSC6900
V900R011
67194987
VS.RAB.NormRel.
CS.Str.Iur
Number of CS
Streaming RABs
Normally Released
SRNC
Earlier than
BSC6900
V900R011
67194988
VS.RAB.NormRel.
PS.Conv.Iur
Number of RABs
Normally Released
for PS
Conversational
Services on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
67194989
VS.RAB.NormRel.
PS.Str.Iur
Number of RABs
Normally Released
for PS Streaming
Services on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
67194990
VS.RAB.NormRel.
HSDPA.Iur
Number of Normally
Released HSDSCHCarried RABs on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
67194991
VS.RAB.NormRel.
HSUPA.Iur
Number of EDCHCarried RABs

Normally Released
SRNC
Earlier than
BSC6900
V900R011
67194997
VS.RAB.AbnormR
el.CS.Str.Iur
Number of CS
Streaming RABs
Abnormally
Released on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
67194998
VS.RAB.AbnormR
el.PS.Conv.Iur
Number of RABs
Abnormally
Released for PS
Conversational
Services on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011

304
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194999
VS.RAB.AbnormR
el.PS.Str.Iur
Number of RABs
Abnormally
Released for PS
Streaming Services
SRNC
Earlier than
BSC6900
V900R011
67195000
VS.RAB.AbnormR
el.HSDPA.Iur
Number of
HSDSCH-Carried
RABs Abnormally
Released on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
67195001
VS.RAB.AbnormR
el.HSUPA.Iur
Number of EDCHCarried RABs

Abnormally
Released on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
67179050
VS.SHO.CancelRL
RecfgIur.Tx
Number of Radio
Link Synchronous
Reconfiguration
Interface for SRNC
Earlier than
BSC6900
V900R011
67196206
VS.RAB.NormRel.
CS.HSPA.Conv.Iur
Number of HSPACarried CS
Conversational
RABs Normally
Released on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
67196207
VS.RAB.AbnormR
el.CS.HSPA.Conv.I
ur
Number of HSPACarried CS
Conversational
RABs Abnormally
Released on Iur
Interface for SRNC
Earlier than
BSC6900
V900R011
73403815
VS.RAB.AbnormR
el.AMRWB.Iur
Number of CS
AMRWB RABs
Abnormally
Released on the
SRNC Iur Interface
for SRNC
BSC6900
V900R012

305
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403816
VS.RAB.NormRel.
AMRWB.Iur
Number of CS
AMRWB RABs
Normally Released
on the SRNC Iur
Interface for SRNC
BSC6900
V900R012
73393847
VS.RAB.NormRel.
PS.BE.Iur
Number of PS BE
RABs Normally
Released on Iur
Interface for SRNC
BSC6900
V900R012
73393848
VS.RAB.AbnormR
el.PS.BE.Iur
Number of PS BE
RABs Abnormally
Released on Iur
Interface for SRNC
BSC6900
V900R012
73421884
VS.RAB.NormRel.
PS.PCH.Iur
Number of Normally
Released PS RABs
that Are in
CELL_PCH or
URA_PCH State on
Iur Interface for
SRNC
BSC6900
V900R012
73421885
VS.RAB.AbnormR
el.PS.PCH.Iur
Number of
Abnormally
Released PS RABs
that Are in
CELL_PCH or
URA_PCH State on
Iur Interface for
SRNC
BSC6900
V900R012
73423384
VS.RRC.AttConnR
elCCCH.DSCR.Iur
Number of RRC
Connection Releases
(CCCH) Sent by the
SRNC over the Iur
Interface due to
DSCR
BSC6900
V900R013
73423385
VS.RRC.AttConnR
elDCCH.DSCR.Iur
Number of RRC
Connection Releases
(DCCH) Sent by the
SRNC over the Iur
Interface due to
DSCR
BSC6900
V900R013

306
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73423639
VS.SHO.FailRLSet
upIur.NodeBReHo
st.Rx
Number of Radio
Link Setup Failures
on Iur interface for
SRNC (NodeB
Rehoming)
BSC6900
V900R014
73423640
VS.SHO.FailRLAd
dIur.NodeBReHost
.Rx
Number of Failed
Radio Link
Additions on Iur
interface for SRNC
(NodeB Rehoming)
BSC6900
V900R014
73428358
VS.SHO.FailRLSet
upIur.NoReply
Number of Radio
Links That Fail to Be
Set up by the SRNC
over the Iur Interface
(No Response from
the DRNC)
BSC6900
V900R016
73428359
VS.SHO.FailRLAd
dIur.NoReply
Number of Radio
Added by the SRNC
over the Iur Interface
(No Response from
the DRNC)
BSC6900
V900R016
he Counter greater than the sum of its Sub Counters
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
Issue 03 (2015-06-30)
VS.RAB.NormRel.PS.CCH.Iur
VS.RAB.NormRel.PS.PCH.Iur
VS.RAB.AbnormRel.PS.CCH.Iur
VS.RAB.AbnormRel.PS.PCH.Iur

307
BSC6900 UMTS
Number of Radio Links Requested to Establish by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179025
VS.SHO.AttRLSetupIur.Tx

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.This counter complies with section "8.3.1 Radio Link Setup" in
3GPP TS 25.423 (v10.10.0).
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
Issue 03 (2015-06-30)

308
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLSetupIur.Tx
WRFD-020203
Number of Radio Links Successfully Established by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179026
VS.SHO.SuccRLSetupIur.R
x
Number of Radio Links

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.This counter complies with section "8.3.1.2 Successful Operation"
in 3GPP TS 25.423 (v10.10.0).
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.
Issue 03 (2015-06-30)

309
BSC6900 UMTS
RADIO LINK SETUP FAILURE message from the DRNC and the message indicates that there
are successfully established radio links, the RNC measures this item on each Iur interface.
Figure 1-125 Radio Link setup failure procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLSetupIur.R
x
WRFD-020203
Number of Failed Radio Link Establishments by SRNC on Iur Interface for

Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179028
W.Rx

SRNC (Device Fault)

310
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67179029
ng.Rx

SRNC (Congestion)
67179030
gUnsupp.Rx

SRNC (Configuration
Unsupported)
67192577
ansCong.Rx

SRNC (Transport Resource
Unavailable)
73423639
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.The preceding counters comply with section "8.3.1.3
Unsuccessful Operation" in 3GPP TS 25.423 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
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

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)

311
BSC6900 UMTS
Counter Name
Description
VS.SHO.FailRLSetupIur.CfgUnsupp.Rx

caused by Improper Configurations on Iur
interface for SRNC (cause value: Combining
not Supported, UL Spreading Factor not
VS.SHO.FailRLSetupIur.TransCong.Rx

caused by Transport Resource Unavailable
on Iur interface for SRNC (cause value:
Transport Resource Unavailable)
VS.SHO.FailRLSetupIur.NodeBReHost.Rx

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-126 Radio Link setup failure procedure on the Iur interface
Formula
None
Unit
None
Issue 03 (2015-06-30)

312
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
W.Rx
WRFD-020203
ng.Rx
WRFD-020203
gUnsupp.Rx
WRFD-020203
ansCong.Rx
WRFD-020203
deBReHost.Rx
WRFD-020203
WRFD-040202
RNC Node Redundancy
Number of Radio Links Deleted on Iur Interface for SRNC

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.3.3.2 Successful Operation" in 3GPP TS 25.423
(v10.10.0).
Measurement point
LINK DELETION REQUEST message to the DRNC, the SRNC measures this item on each
Iur interface.
Issue 03 (2015-06-30)

313
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLDelIur.Tx
WRFD-020203
Number of Successful deleted Radio Links on Iur Interface for SRNC

Counters
Counter ID
Counter Name
Counter Description
67179033
VS.SHO.SuccRLDelIur.Rx
deleted Radio Links on Iur
Interface for SRNC
Description
This measurement item provides the number of successful deleted radio links on the Iur interface
for SRNC.This counter complies with section "8.3.3.2 Successful Operation" in 3GPP TS 25.423
(v10.10.0).
Issue 03 (2015-06-30)

314
BSC6900 UMTS
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
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLDelIur.Rx
WRFD-020203
Number of Radio Links Requested to Add by SRNC on Iur Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179035
VS.SHO.AttRLAddIur.Tx

Addition Requests on Iur
Interface from SRNC

315
BSC6900 UMTS
Description
add on the Iur interface.This counter complies with section "8.3.2.2 Successful Operation" in
3GPP TS 25.423 (v10.10.0).
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-129 Radio Link addition procedure on the Iur interface (successful operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLAddIur.Tx
WRFD-020203

316
BSC6900 UMTS
Number of Radio Links Successfully Added by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179036
VS.SHO.SuccRLAddIur.Rx

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.This counter complies with section "8.3.2.2 Successful Operation"
in 3GPP TS 25.423 (v10.10.0).
Measurement point
RADIO LINK ADDITION RESPONSE message from the DRNC, the SRNC measures the item
Figure 1-130 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.
Issue 03 (2015-06-30)

317
BSC6900 UMTS
Figure 1-131 Radio Link addition procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLAddIur.Rx
WRFD-020203
Number of Failed Radio Link Additions for Different Causes on Iur Interface for
SRNC
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179038
.Rx

SRNC (Device Fault)

318
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192578
nsCong.Rx

Addition Failures on Iur
Interface for SRNC
(Transport Resource
Unavailable)
67179039
g.Rx

SRNC (Congestion)
67179040
Unsupp.Rx

SRNC (Configuration
Unsupported)
73423640
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.The preceding counters comply with section "8.3.2.3 Unsuccessful
Issue 03 (2015-06-30)
Counter Name
Description
VS.SHO.FailRLAddIur.HW.Rx

by hardware failure on Iur interface for SRNC
(cause value: Hardware Failure)
VS.SHO.FailRLAddIur.TransCong.Rx

by insufficient RNC transmission capability
on Iur interface for SRNC (cause value:
Transport Resource Unavailable)
VS.SHO.FailRLAddIur.Cong.Rx

by insufficient RNC capability on Iur
Operator Use, Control Processing Overload,
Not enough User Plane Processing Resources
or Transport Resource Unavailable)

319
BSC6900 UMTS
Counter Name
Description
VS.SHO.FailRLAddIur.CfgUnsupp.Rx

by improper configurations on Iur interface
for SRNC (cause value: Combining not
Supported, UL Spreading Factor not
VS.SHO.FailRLAddIur.NodeBReHost.Rx

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
Figure 1-132 Radio Link addition procedure (failed operation)
Formula
None
Unit
None
Issue 03 (2015-06-30)

320
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
.Rx
WRFD-020203
nsCong.Rx
WRFD-020203
g.Rx
WRFD-020203
Unsupp.Rx
WRFD-020203
eBReHost.Rx
WRFD-040202
RNC Node Redundancy
WRFD-020203
Number of Radio Links Requested to Reconfigure by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179042
VS.SHO.AttRLRecfgIur.Tx

Reconfiguration Requests on
Iur Interface from SRNC
Description
reconfigure on the Iur interface.This counter complies with section "8.3.4.2 Successful
Measurement point
LINK RECONFIGURATION PREPARE message to the DRNC, the SRNC measures this item
Issue 03 (2015-06-30)

321
BSC6900 UMTS
Figure 1-133 Synchronized radio link reconfiguration procedure on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLRecfgIur.Tx
WRFD-020203
Number of Radio Links Successfully Reconfigured by SRNC on Iur Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179043
VS.SHO.SuccRLRecfgIur.R
x

Link Reconfigurations on Iur
Interface for SRNC

322
BSC6900 UMTS
Description
This measurement item takes statistics of the number of radio links successfully reconfigured
by the SRNC.This counter complies with section "8.3.4.2 Successful Operation" in 3GPP TS
25.423 (v10.10.0).
Measurement point
The measurement is triggered at point C, as shown in the figure. When the SRNC sends a RADIO
LINK RECONFIGURATION COMMIT message to the DRNC, if there is an indication of
successfully reconfigured radio links in the message, the SRNC measures this item on each Iur
interface.
Figure 1-134 Synchronized radio link reconfiguration commit procedure (successful operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLRecfgIur.R
x
WRFD-020203

323
BSC6900 UMTS
Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur Interface

for Different Causes
Counters
Counter ID
Counter Name
Counter Description
67179045
W.Rx

Synchronous
Interface for SRNC (Device
Fault)
67179046
ong.Rx

Synchronous
Interface for SRNC
(Congestion)
67179047
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.This counter complies with section "8.3.4.3
Issue 03 (2015-06-30)
Counter Name
Description
VS.SHO.FailRLRecfgIur.HW.Rx
Number of failed radio link reconfigurations

by hardware failure on Iur interface for SRNC
(cause value: Hardware Failure)

324
BSC6900 UMTS
Counter Name
Description
VS.SHO.FailRLRecfgIur.Cong.Rx

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)
VS.SHO.FailRLRecfgIur.CfgUnsupp.Rx

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-135 Synchronized radio link reconfiguration procedure on the Iur interface (failed
operation)
Issue 03 (2015-06-30)

325
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
W.Rx
WRFD-020203
ong.Rx
WRFD-020203
gUnsupp.Rx
WRFD-020203
Number of Radio Links Unsuccessfully Reconfigured by SRNC on Iur Interface

for No Response
Counters
Counter ID
Counter Name
Counter Description
67179048
VS.SHO.FailRLRecfgIur.N
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.This counter complies with section "8.3.4.3
Measurement point
The measurement is triggered at point A as shown in the figure. When the SRNC sends a RADIO
LINK RECONFIGURATION PREPARE message to the DRNC, the SRNC starts the timer to
wait for the response message from the DRNC. If the SRNC does not receive a response message
until the timer expires, it triggers the the measurement of this item on each Iur interface.
Issue 03 (2015-06-30)

326
BSC6900 UMTS
Figure 1-136 Radio Link synchronous reconfiguration preparation procedure (failed operation)
(no reply)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.FailRLRecfgIur.N
oReply
WRFD-020203

327
BSC6900 UMTS
Number of Failed Radio Links of SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179051

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.This counter complies with section "8.3.9
Radio Link Failure" in 3GPP TS 25.423 (v10.10.0).
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
Issue 03 (2015-06-30)

328
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020203
Number of Failed Radio Links of SRNC on Iur Interface for Different Causes
Counters
Counter ID
Counter Name
Counter Description
67179053

SRNC (Device Fault)
67179054
VS.SHO.RLFailIur.SyncFai
l.Rx

SRNC (Synchronization
Failure)
67179055
VS.SHO.RLFailIur.CfgUns
up.Rx

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.This counter
complies with section "8.3.9 Radio Link Failure" in 3GPP TS 25.423 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
Number of failed radio links of SRNC on Iur

interface because of hardware failure (cause
value: Hardware Failure)
VS.SHO.RLFailIur.SyncFail.Rx

interface because of synchronization failure
(cause value: Synchronization Failure)

329
BSC6900 UMTS
Counter Name
Description
VS.SHO.RLFailIur.CfgUnsup.Rx

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
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020203
VS.SHO.RLFailIur.SyncFai
l.Rx
WRFD-020203

330
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.SHO.RLFailIur.CfgUns
up.Rx
WRFD-020203
Number of Radio Links Restored by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179056
VS.SHO.RLRestoreIur.Rx

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.This counter complies with section "8.3.10 Radio Link Restoration" in 3GPP
TS 25.423 (v10.10.0).
Measurement point
RADIO LINK RESTORE INDICATION message from the DRNC, the SRNC measures this
item on each Iur interface.
Figure 1-139 Radio Link restoration procedure
Formula
None
Issue 03 (2015-06-30)

331
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.RLRestoreIur.Rx
WRFD-020203
Number of Soft Handovers Initiated by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179061
VS.SHO.Att.Iur

Initiated by SRNC on Iur
Interface
Description
This measurement item takes statistics of the number of soft handovers initiated by the SRNC
on Iur Interface.This counter complies with section "8.3.4 Synchronised Radio Link
Reconfiguration Preparation" in 3GPP TS 25.423 (v10.10.0).
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-140 Active set update procedure (successful operation)
Issue 03 (2015-06-30)

332
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.Att.Iur
WRFD-020203
Number of Successful Soft Handovers Initiated by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67179062
VS.SHO.Succ.Iur
Number of Successful Soft

Handovers Initiated by
SRNC on Iur Interface
Description
This counter provides the number of successful soft handovers initiated by the SRNC on the Iur
interface.This counter complies with section "8.3.4 Synchronised Radio Link Reconfiguration
Preparation" in 3GPP TS 25.423 (v10.10.0).
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 counter shall be measured on each Iur interface.
Figure 1-141 Active set update procedure (successful operation)
Issue 03 (2015-06-30)

333
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.Succ.Iur
WRFD-020203
Number of COMMON TRANSPORT CHANNEL RESOURCES REQUEST

Messages Sent by SRNC on Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67179057
VS.AttCommTrChResIur.T
x
Number of Common
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.
Issue 03 (2015-06-30)

334
BSC6900 UMTS
Figure 1-142 Initialization procedure of common transport channel resources on the Iur interface
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttCommTrChResIur.T
x
WRFD-010802
Number of COMMON TRANSPORT CHANNEL RESOURCES RESPONSE

Messages Received by SRNC on Iur Interface
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179058
VS.SuccCommTrChResIur.
Rx
Number of Common
Responses Received by
SRNC on Iur Interface

335
BSC6900 UMTS
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-143 Initialization procedure of common transport channel resources on the Iur interface
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SuccCommTrChResIur.
Rx
WRFD-010802

336
BSC6900 UMTS
Number of COMMON TRANSPORT CHANNEL RESOURCES FAILURE

Messages Received by SRNC on Iur Interface Due to Transport Resource
Unavailable
Counters
Counter ID
Counter Name
Counter Description
67179059
VS.FailCommTrChResIur.N
otSupp.Rx
Number of Common
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.
Figure 1-144 Common transport channel resource failure procedure on the Iur interface
Issue 03 (2015-06-30)

337
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.FailCommTrChResIur.N
otSupp.Rx
WRFD-010802
Number of COMMON TRANSPORT CHANNEL RESOURCES RELEASE

REQUEST Messages of SRNC on Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67179060
VS.AttRelCommTrChResIu
r.Tx
Number of Common
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-145 Common transport channel resource release procedure on the Iur interface
Issue 03 (2015-06-30)

338
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRelCommTrChResIu
r.Tx
WRFD-010802
Number of PS RABs Normally Released on CCH (FACH or PCH) for SRNC (Iur
Interface)
Counters
Counter ID
Counter Name
Counter Description
67191850
VS.RAB.NormRel.PS.CCH.
Iur
Number of PS RABs
Normally Released on Iur
Interface for SRNC (CCH
User Only)
Description
When the best cell is under a DRNC, these measurement items take statistics of the number of
RABs normally released on CCH (FACH or PCH) on the SRNC IUR interface.This counter
complies with section "8.2 RAB Assignment" and "8.5 Iu Release" in 3GPP TS 25.413
(v10.10.0).
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.
Issue 03 (2015-06-30)

339
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.
Issue 03 (2015-06-30)

340
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.PS.CCH.
Iur
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

341
BSC6900 UMTS
Number of Normally Released CS RABs According to Different Service on the IUR

interface
Counters
Counter ID
Counter Name
Counter Description
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
r
Number of CS Streaming
RABs Normally Released on
73403816
VS.RAB.NormRel.AMRW
B.Iur
Number of CS AMRWB
the SRNC Iur Interface for
SRNC
Description
RABs normally released by the DRNC according to different service on the SRNC IUR
interface.The preceding counters comply with section "8.2 RAB Assignment" and "8.5 Iu
Measurement point
Issue 03 (2015-06-30)

342
BSC6900 UMTS
Issue 03 (2015-06-30)

343
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.AMR.Iur
WRFD-010501
VS.RAB.NormRel.CS64.Iur
WRFD-010501
VS.RAB.NormRel.CS.Str.Iu
r
WRFD-010502
Streaming QoS Class
VS.RAB.NormRel.AMRW
B.Iur
WRFD-010613
AMR-WB (Adaptive Multi

Rate Wide Band)
WRFD-010501
Issue 03 (2015-06-30)

344
BSC6900 UMTS
Number of Abnormally Released CS RABs According to Different Service on

SRNC Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67191859
Iur
Released AMR RABs on Iur
Interface for SRNC(not
including WB-AMR)
67191860
Iur
Number of CS
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
.Iur
RABs Abnormally Released
on Iur Interface for SRNC
73403815
VS.RAB.AbnormRel.AMR
WB.Iur
Number of CS AMRWB
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.The preceding counters comply with section "8.2 RAB Assignment" and "8.5 Iu
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.
Issue 03 (2015-06-30)

345
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
The measurement is triggered at point A as shown in the figure. The SRNC sends to the CN an
Issue 03 (2015-06-30)

346
BSC6900 UMTS
Figure 1-152 Iu connection release procedure triggered by the RNC
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Iur
WRFD-010501
Iur
WRFD-010501
.Iur
WRFD-010502
Streaming QoS Class
WB.Iur
WRFD-010613

Rate Wide Band)
WRFD-010501
Issue 03 (2015-06-30)

347
BSC6900 UMTS
Number of PS RABs Abnormally Released on CCH (FACH or PCH) for SRNC (Iur
Interface)
Counters
Counter ID
Counter Name
Counter Description
67191865
VS.RAB.AbnormRel.PS.CC
H.Iur
Number of PS RABs
Abnormally Released on Iur
Interface for SRNC (CCH
User Only)
Description
abnormally released PS RABs beared on CCH on the SRNC IUR interface.This counter complies
with section "8.2 RAB Assignment" and "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
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.
cell, The SRNC RNC sends to the CN a RAB RELEASE REQUEST message due to exception.If
Issue 03 (2015-06-30)

348
BSC6900 UMTS
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
Issue 03 (2015-06-30)

349
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
H.Iur
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Normally Released PS RABs According to Different Service on the IUR

interface
Counters
Counter ID
Counter Name
Counter Description
67194988
VS.RAB.NormRel.PS.Conv
.Iur
Number of RABs Normally

Released for PS
Conversational Services on
67194989
VS.RAB.NormRel.PS.Str.Iu
r

Released for PS Streaming
Services on Iur Interface for
SRNC
73393847
VS.RAB.NormRel.PS.BE.Iu
r
Number of PS BE RABs
Interface for SRNC
Description
RABs normally released by the DRNC according to service types in PS domain on the SRNC
IUR interface.The preceding counters comply with section "8.2 RAB Assignment" and "8.5 Iu
Measurement point
Issue 03 (2015-06-30)

350
BSC6900 UMTS
is "User Inactivity","Normal Release","Successful Relocation" or "Network Optimization", or
according to service types in PS domain on Iur Interface.
Signalling Connection Release" ,the RNC measures each item according to service types in PS
domain on Iur Interface.
Issue 03 (2015-06-30)

351
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.Iur
WRFD-010501
VS.RAB.NormRel.PS.Str.Iu
r
WRFD-010502
Streaming QoS Class
VS.RAB.NormRel.PS.BE.Iu
r
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010503
WRFD-010504

Issue 03 (2015-06-30)

352
BSC6900 UMTS
Number of Normally Released HSPA RABs on Iur Interface for SRNC

Counters
Counter ID
Counter Name
Counter Description
67194990
VS.RAB.NormRel.HSDPA.
Iur
Number of Normally
Released HSDSCH-Carried
RABs on Iur Interface for
SRNC
67194991
VS.RAB.NormRel.HSUPA.
Iur
Number of EDCH-Carried
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.The preceding counters comply
with section "8.2 RAB Assignment" and "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

353
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.HSDPA.
Iur
WRFD-010651
HSDPA over Iur

354
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.HSUPA.
Iur
WRFD-010635
HSUPA over Iur
Number of Abnormally Released PS RABs According to Different Service Type on

SRNC Iur Interface
Counters
Counter ID
Counter Name
Counter Description
67194998
VS.RAB.AbnormRel.PS.Co
nv.Iur
Number of RABs
Abnormally Released for PS
67194999
VS.RAB.AbnormRel.PS.Str
.Iur
Number of RABs
Streaming Services on Iur
Interface for SRNC
73393848
VS.RAB.AbnormRel.PS.BE
.Iur
Number of PS BE RABs
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.The preceding counters
comply with section "8.2 RAB Assignment" and "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
Measurement point
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN a RAB
RELEASE REQUEST message. If the RNC receives from the CN a RAB ASSIGNMENT
REQUEST message which contains a cause value of abnormal release (a cause value except
"User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE
Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then the SRNC
measures the corresponding counter on the Iur interface according to the service types in PS
domain.
Issue 03 (2015-06-30)

355
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.
As shown in point A of the figure, when an exception occurs, the SRNC sends the CN an IU
Issue 03 (2015-06-30)

356
BSC6900 UMTS
domain.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
nv.Iur
WRFD-010501
.Iur
WRFD-010502
Streaming QoS Class
.Iur
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010503
WRFD-010504

Issue 03 (2015-06-30)

357
BSC6900 UMTS
Number of Abnormally Released HSPA-Carried RABs on SRNC Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67195000
VS.RAB.AbnormRel.HSDP
A.Iur
Number of HSDSCHCarried RABs Abnormally

Released on Iur Interface for
SRNC
67195001
VS.RAB.AbnormRel.HSUP
A.Iur
Number of EDCH-Carried
Description
abnormally released RABs according to different bearer types on the SRNC IUR interface.The
preceding counters comply with section "8.2 RAB Assignment" and "8.5 Iu Release" in 3GPP
TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

358
BSC6900 UMTS
Issue 03 (2015-06-30)

359
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.HSDP
A.Iur
WRFD-010651
HSDPA over Iur
VS.RAB.AbnormRel.HSUP
A.Iur
WRFD-010635
HSUPA over Iur
Number of RLs with Reconfiguration Canceled by the SRNC over Iur

Counters
Counter ID
Counter Name
Counter Description
67179050
.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.This counter complies with section "8.3.6 Synchronised
Radio Link Reconfiguration Cancellation" in 3GPP TS 25.423 (v10.10.0).
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.
Issue 03 (2015-06-30)

360
BSC6900 UMTS
Figure 1-166 Radio link reconfiguration cancellation procedure over Iur
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.Tx
WRFD-020203
Number of CS Conversational RABs carried on HSPA Normally Released on Iur

Interface for SRNC
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196206
VS.RAB.NormRel.CS.HSP
A.Conv.Iur
Number of HSPA-Carried
CS Conversational RABs
Interface for SRNC

361
BSC6900 UMTS
Description
CS Conversational RABs carried on HSPA normally released by the DRNC according to
different service on the SRNC IUR interface.This counter complies with section "8.2 RAB
Assignment" and "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
Measurement point
Issue 03 (2015-06-30)

362
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
A.Conv.Iur
WRFD-010619
WRFD-010651
CS voice over HSPA/HSPA

+
WRFD-010635
HSDPA over Iur

HSUPA over Iur
Issue 03 (2015-06-30)

363
BSC6900 UMTS
Number of CS Conversational RABs carried on HSPA Abnormally Released on Iur

Interface for SRNC
Counters
Counter ID
Counter Name
Counter Description
67196207
VS.RAB.AbnormRel.CS.HS
PA.Conv.Iur
Number of HSPA-Carried
CS Conversational RABs
Interface for SRNC
Description
abnormally released CS RABs carried on HSPA on the SRNC IUR interface.This counter
complies with section "8.2 RAB Assignment" and "8.5 Iu Release" in 3GPP TS 25.413
(v10.10.0).
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
Issue 03 (2015-06-30)

364
BSC6900 UMTS
RELEASE COMMAND message(with the cause other than "User Inactivity","Normal

The measurement is triggered at point A as shown in the figure. The SRNC sends to the CN an
Issue 03 (2015-06-30)

365
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
PA.Conv.Iur
WRFD-010619
WRFD-010651

+
WRFD-010635
HSDPA over Iur

HSUPA over Iur
Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State

Counters
Counter ID
Counter Name
Counter Description
73421884
VS.RAB.NormRel.PS.PCH.
Iur
Number of Normally
Released PS RABs that Are
in CELL_PCH or URA_PCH
State on Iur Interface for
SRNC
Description
This counter provides the number of normally released PS RABs that are in CELL_PCH or
URA_PCH state on the Iur interface if the UE camps on a cell under the DRNC. The release of
RABs in URA_PCH state is measured in the last cell that the UE camps on before entering the
URA_PCH state.This counter complies with section "8.2 RAB Assignment" and "8.5 Iu Release"
in 3GPP TS 25.413 (v10.10.0).
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
Issue 03 (2015-06-30)

366
BSC6900 UMTS
COMMAND message, then the counter is measured on the Iur interface if the UE camps on a
cell under the DRNC.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.PS.PCH.
Iur
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

367
BSC6900 UMTS
Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH

State on Iur Interface for SRNC
Counters
Counter ID
Counter Name
Counter Description
73421885
VS.RAB.AbnormRel.PS.PC
H.Iur
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.This counter complies with section "8.2 RAB Assignment" and "8.5 Iu Release"
in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

368
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.
on a cell under the DRNC and a failure occurs, the SRNC sends the CN an IU RELEASE
abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation",
or "Network Optimization", for details, see 3GPP TS 25.413), the SNRC measures a counter on
the Iur interface according to the RAB type.
Issue 03 (2015-06-30)

369
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
H.Iur
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Releases (CCCH) Sent by the SRNC over the Iur
Interface due to DSCR
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423384
VS.RRC.AttConnRelCCCH
.DSCR.Iur

Releases (CCCH) Sent by the
SRNC over the Iur Interface
due to DSCR

370
BSC6900 UMTS
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).This counter complies with section "8.2.2 Downlink Signalling Transfer" in 3GPP TS
25.423 (v10.10.0).
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-176 RRC connection release procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

371
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnRelCCCH
.DSCR.Iur
WRFD-021400
Direct Signaling Connection

Re-establishment (DSCR)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Releases (DCCH) Sent by the SRNC over the Iur
Interface due to DSCR
Counters
Counter ID
Counter Name
Counter Description
73423385
VS.RRC.AttConnRelDCCH
.DSCR.Iur

Releases (DCCH) Sent by the
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).This counter complies with section "8.2.2 Downlink Signalling Transfer" in 3GPP TS
25.423 (v10.10.0).
Measurement point
an RRC CONNECTION RELEASE (DCCH) message over the Iur interface because of DSCR.
Issue 03 (2015-06-30)

372
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnRelDCCH
.DSCR.Iur
WRFD-021400

WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

373
BSC6900 UMTS
Number of Radio Links That Fail to Be Set up by the SRNC over the Iur Interface
(No Response from the DRNC)
Counters
Counter ID
Counter Name
Counter Description
73428358
Reply
Number of Radio Links That

Fail to Be Set up by the
(No Response from the
DRNC)
Description
This counter provides the number of radio links that fail to be set up by the SRNC over the Iur
interface due to no response from the DRNC.This counter complies with section "8.3.1.4
Abnormal Conditions" in 3GPP TS 25.423 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. The SRNC sends a
RADIO LINK SETUP REQUEST message to the DRNC and then the SRNC starts a timer. If
the SRNC does not receive a response from the DRNC before the timer expires, this counter is
updated over the Iur interface based on the number of radio links that fail to be set up.
Issue 03 (2015-06-30)

374
BSC6900 UMTS
Figure 1-178 Radio link setup failure over the Iur interface due to no response from the DRNC
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Reply
WRFD-020203

375
BSC6900 UMTS
Number of Radio Links That Fail to Be Added by the SRNC over the Iur Interface
(No Response from the DRNC)
Counters
Counter ID
Counter Name
Counter Description
73428359
VS.SHO.FailRLAddIur.No
Reply

Fail to Be Added by the
(No Response from the
DRNC)
Description
This counter provides the number of radio links that fail to be added by the SRNC over the Iur
interface due to no response from the DRNC.This counter complies with section "8.3.2.4
Abnormal Conditions" in 3GPP TS 25.423 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. The SRNC sends a
RADIO LINK ADDITION REQUEST message to the DRNC and then the SRNC starts a timer.
If the SRNC does not receive a response from the DRNC before the timer expires, this counter
is updated over the Iur interface based on the number of radio links that fail to be added.
Issue 03 (2015-06-30)

376
BSC6900 UMTS
Figure 1-179 Radio link addition failure over the Iur interface due to no response from the
DRNC
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.FailRLAddIur.No
Reply
WRFD-020203

377
BSC6900 UMTS
1.5.5 Traffic Measurement per Iur Interface(TRFFIC.IUR)

Overview
The Iur interface traffic measurement is used to measure the uplink (UL) and downlink (DL)
signaling flows on the Iur interface and the UL and DL data streams in the CS and PS domains.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199487
VS.SRNCIurBytes
SigDCH.Rx
Number of UL Bytes
of Signaling Data
Received by SRNC
on DCH of Iur
Interface
Earlier than
BSC6900
V900R011
67199488
VS.SRNCIurBytes
SigDCH.Tx
Number of DL Bytes
of Signaling Data
Sent by SRNC on
DCH of Iur Interface
Earlier than
BSC6900
V900R011
67199497
VS.SRNCIurBytes
PSR99Conv.Rx
Number of UL Bytes
of PS R99
Conversational
Service Received by
SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67199498
VS.SRNCIurBytes
PSR99Str.Rx
Number of UL Bytes
of PS R99 Streaming
Service Received by
SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67199499
VS.SRNCIurBytes
PSR99Int.Rx
Number of UL Bytes
of PS R99 Interactive
Service Received by
SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67199500
VS.SRNCIurBytes
PSR99Bkg.Rx
Number of UL Bytes
of PS R99
Background Service
Received by SRNC
on Iur Interface
Earlier than
BSC6900
V900R011

378
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199501
VS.SRNCIurBytes
PSR99Conv.Tx
Number of DL Bytes
of PS R99
Conversational
Service Sent by
SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67199502
VS.SRNCIurBytes
PSR99Str.Tx
Number of DL Bytes
of PS R99 Streaming
Service Sent by
SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67199503
VS.SRNCIurBytes
PSR99Int.Tx
Number of DL Bytes
Service Sent by
SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67199504
VS.SRNCIurBytes
PSR99Bkg.Tx
Number of DL Bytes
of PS R99
Background Service
Sent by SRNC on Iur
Interface
Earlier than
BSC6900
V900R011
67199489
VS.SRNCIurBytes
CSConv.Rx
Number of UL Bytes
Service Received by
SRNC on DCH of Iur
Interface
Earlier than
BSC6900
V900R011
67199490
VS.SRNCIurBytes
CSStr.Rx
Number of UL Bytes
of CS Streaming
Service Received by
SRNC on DCH of Iur
Interface
Earlier than
BSC6900
V900R011
67199493
VS.SRNCIurBytes
CSConv.Tx
Number of DL Bytes
Service Sent by
SRNC on DCH of Iur
Interface
Earlier than
BSC6900
V900R011
67199494
VS.SRNCIurBytes
CSStr.Tx
Number of DL Bytes
of CS Streaming
Service Sent by
SRNC on DCH of Iur
Interface
Earlier than
BSC6900
V900R011

379
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199505
VS.DRNCIurBytes
DCH.Tx
Number of UL Bytes
Sent by DRNC on
DCH of Iur Interface
Earlier than
BSC6900
V900R011
67199506
VS.DRNCIurBytes
DCH.Rx
Number of DL Bytes
Received by DRNC
Over DCH FP on the
Iur Interface
Earlier than
BSC6900
V900R011
73410465
VS.SRNCIurBytes
PSConvHSUPA.Rx
Number of bytes of
PS HSUPA
conversational
service in SRNC for
IUR
BSC6900
V900R012
73410466
VS.SRNCIurBytes
PSStrHSUPA.Rx
Number of bytes of
PS HSUPA
streaming service in
SRNC for IUR
BSC6900
V900R012
73410467
VS.SRNCIurBytes
PSIntHSUPA.Rx
Number of bytes of
PS HSUPA
interactive service in
SRNC for IUR
BSC6900
V900R012
73410470
VS.SRNCIurBytes
PSBkgHSUPA.Rx
Number of bytes of
PS HSUPA
background service
in SRNC for IUR
BSC6900
V900R012
73410471
VS.SRNCIurBytes
PSConvHSDPA.Tx
Number of bytes of
PS HSDPA
conversational
service in SRNC for
IUR
BSC6900
V900R012
73410472
VS.SRNCIurBytes
PSStrHSDPA.Tx
Number of bytes of
PS HSDPA
streaming service in
SRNC for IUR
BSC6900
V900R012
73410473
VS.SRNCIurBytes
PSIntHSDPA.Tx
Number of bytes of
PS HSDPA
interactive service in
SRNC for IUR
BSC6900
V900R012
73410474
VS.SRNCIurBytes
PSBkgHSDPA.Tx
Number of bytes of
PS HSDPA
background service
in SRNC for IUR
BSC6900
V900R012

380
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73410476
VS.SRNCIurBytes
CSConvHSDPA.Tx
Number of bytes of
CS HSDPA
conversational
service in SRNC for
IUR
BSC6900
V900R012
73410478
VS.DRNCIurBytes
HSDPA.Rx
Number of bytes of
HSDPA services in
DRNC for IUR
BSC6900
V900R012
73410479
VS.SRNCIurBytes
SigHSDPA.Tx
Number of HSDPA
Signaling Bytes on
Iur Interface in
SRNC
BSC6900
V900R012
73410480
VS.SRNCIurBytes
SigHSUPA.Rx
Number of HSUPA
Signaling Bytes on
Iur Interface in
SRNC
BSC6900
V900R012
73410481
VS.SRNCIurBytes
CSConvHSUPA.Rx
Number of bytes of
CS HSUPA
conversational
service in SRNC for
IUR
BSC6900
V900R012
None
Number of UL Bytes of Signaling Data Received by SRNC on DCH of Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67199487
VS.SRNCIurBytesSigDCH.
Rx
Number of UL Bytes of
Signaling Data Received by
SRNC on DCH of Iur
Interface
Description
This counter provides the number of UL bytes of signaling data that the SRNC receives from
the DRNC on the DCH FP of the Iur interface.
Issue 03 (2015-06-30)

381
BSC6900 UMTS
Measurement point
When receiving UL signaling data on the signaling bearer DCH FP (excluding the EDCH FP)
of the Iur interface, the SRNC measures this counter. The value of this counter does not include
the number of bytes of FP headers and this counter is measured separately on different Iur
interfaces.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
Rx
WRFD-021000
Transport Channel
Management
Number of DL Bytes of Signaling Data Sent by SRNC on DCH of Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67199488
Tx
Number of DL Bytes of
Signaling Data Sent by
SRNC on DCH of Iur
Interface
Description
This counter provides the number of DL bytes of signaling data that the SRNC sends to the
DRNC on the DCH FP of the Iur interface.
Measurement point
When sending DL signaling data to the DRNC on the signaling bearer DCH FP (excluding the
HS-DSCH FP) of the Iur interface, the SRNC measures this counter. The value of this counter
does not include the number of bytes of FP headers and this counter is measured separately on
different Iur interfaces.
Formula
None
Issue 03 (2015-06-30)

382
BSC6900 UMTS
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
Tx
WRFD-021000
Transport Channel
Management
Number of Bytes of UL PS R99 Services Received by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67199497
VS.SRNCIurBytesPSR99Co
nv.Rx
R99 Conversational Service
Received by SRNC on Iur
Interface
67199498
VS.SRNCIurBytesPSR99Str
.Rx
R99 Streaming Service
Interface
67199499
VS.SRNCIurBytesPSR99Int
.Rx
R99 Interactive Service
Interface
67199500
VS.SRNCIurBytesPSR99Bk
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.
Issue 03 (2015-06-30)

383
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
nv.Rx
WRFD-010501
.Rx
WRFD-010502
Streaming QoS Class
.Rx
WRFD-010503
g.Rx
WRFD-010504
Number of Bytes of DL PS R99 Services Sent by SRNC on Iur Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199501
nv.Tx
R99 Conversational Service
Sent by SRNC on Iur
Interface
67199502
.Tx
R99 Streaming Service Sent
by SRNC on Iur Interface
67199503
.Tx
R99 Interactive Service Sent
by SRNC on Iur Interface
67199504
g.Tx
R99 Background Service
Sent by SRNC on Iur
Interface

384
BSC6900 UMTS
Description
These counters provide the number of bytes of DL PS R99 service data that the SRNC sends to
the DRNC on the DCH FP of the Iur interface based on the service type.
Measurement point
The measurement is triggered based on the service type when the SRNC sends data of PS R99
services to the DRNC over the DCH FP on the Iur interface. The measured data excludes FP
headers and the counters are measured separately on different Iur interfaces.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
nv.Tx
WRFD-010501
.Tx
WRFD-010502
Streaming QoS Class
.Tx
WRFD-010503
g.Tx
WRFD-010504
Number of Bytes of UL CS Services Received by SRNC over DCH on Iur Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199489
VS.SRNCIurBytesCSConv.
Rx
Received by SRNC on DCH
of Iur Interface
67199490
VS.SRNCIurBytesCSStr.Rx
Streaming Service Received
by SRNC on DCH of Iur
Interface

385
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
Counter Name
Feature ID
Feature Name
Rx
WRFD-010501
VS.SRNCIurBytesCSStr.Rx
WRFD-010502
Streaming QoS Class
Number of Bytes of DL CS Services Sent by SRNC over DCH on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
67199493
Tx
Conversational Service Sent
by SRNC on DCH of Iur
Interface
67199494
VS.SRNCIurBytesCSStr.Tx
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.
Issue 03 (2015-06-30)

386
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
Counter Name
Feature ID
Feature Name
Tx
WRFD-010501
VS.SRNCIurBytesCSStr.Tx
WRFD-010502
Streaming QoS Class
Number of UL Bytes Sent by DRNC on DCH of Iur Interface

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

387
BSC6900 UMTS
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.DRNCIurBytesDCH.Tx
WRFD-021000
Transport Channel
Management
Number of DL Bytes Received by DRNC on DCH of Iur Interface

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRNCIurBytesDCH.Rx
WRFD-021000
Transport Channel
Management

388
BSC6900 UMTS
Number of Bytes of PS HSUPA Services Received by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
73410465
VS.SRNCIurBytesPSConv
HSUPA.Rx
Number of bytes of PS
HSUPA conversational
service in SRNC for IUR
73410466
VS.SRNCIurBytesPSStrHS
UPA.Rx
HSUPA streaming service in
SRNC for IUR
73410467
VS.SRNCIurBytesPSIntHS
UPA.Rx
HSUPA interactive service in
SRNC for IUR
73410470
VS.SRNCIurBytesPSBkgH
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
HSUPA.Rx
WRFD-010617
VoIP over HSPA/HSPA+
WRFD-010501
UPA.Rx
WRFD-010635
HSUPA over Iur

389
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
UPA.Rx
WRFD-010635
HSUPA over Iur
SUPA.Rx
WRFD-010635
HSUPA over Iur
Number of Bytes of PS HSDPA Services Received by SRNC on Iur Interface

Counters
Counter ID
Counter Name
Counter Description
73410471
HSDPA.Tx
HSDPA conversational
73410472
DPA.Tx
HSDPA streaming service in
SRNC for IUR
73410473
DPA.Tx
HSDPA interactive service in
SRNC for IUR
73410474
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
Issue 03 (2015-06-30)

390
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
HSDPA.Tx
WRFD-010617
WRFD-010501
DPA.Tx
WRFD-010651
HSDPA over Iur
DPA.Tx
WRFD-010651
HSDPA over Iur
SDPA.Tx
WRFD-010651
HSDPA over Iur
Number of bytes of CS HSDPA conversational service in SRNC for IUR

Counters
Counter ID
Counter Name
Counter Description
73410476
VS.SRNCIurBytesCSConv
HSDPA.Tx
Number of bytes of CS
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
Issue 03 (2015-06-30)

391
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
HSDPA.Tx
WRFD-010619

+
Number of bytes of HSDPA services in DRNC for IUR

Counters
Counter ID
Counter Name
Counter Description
73410478
VS.DRNCIurBytesHSDPA.
Rx
Number of bytes of HSDPA

services in DRNC for IUR
Description
This counter provides the DL bytes of the DRNC HSDSCH service. The byte are sent by the
SRNC.
Measurement point
The measurement is triggered when the DRNC receives DL MAC PDUs over the HSDSCH FP
on the Iur interface. The FP header is not included. The measurement is performed respectively
on the basis of Iur interfaces.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRNCIurBytesHSDPA.
Rx
WRFD-010651
HSDPA over Iur

392
BSC6900 UMTS
Number of HSDPA Signaling Bytes on Iur Interface in SRNC

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

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73410480
VS.SRNCIurBytesSigHSUP
A.Rx
Number of HSUPA
Signaling Bytes on Iur
Interface in SRNC

393
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
Counter Name
Feature ID
Feature Name
VS.SRNCIurBytesSigHSUP
A.Rx
WRFD-010635
HSUPA over Iur
WRFD-010636
SRB over HSUPA
Number of bytes of CS HSUPA conversational service in SRNC for IUR

Counters
Counter ID
Counter Name
Counter Description
73410481
HSUPA.Rx
Number of bytes of CS
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
Issue 03 (2015-06-30)

394
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
HSUPA.Rx
WRFD-010619

+
1.6 Measurement of MPU Subsystem 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/SPUc board has eight subsystems. In addition, an
SPUa subsystem and an SPUb/SPUc subsystem have different processing capabilities.
The MPU measurement is performed only to assess the performance of a single MPU subsystem.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
MPU
MPU Subsystem Measurement

395
BSC6900 UMTS
1.6.1 MPU Subsystem Measurement(MPU)

Overview
The MPU measurement is used to assess the running performance of an MPU subsystem in the
RNC.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67204521
VS.PSLoad.ULThr
uput.MPU
Throughput of PS
Uplink Data for
MPU
Earlier than
BSC6900
V900R011
67204522
VS.PSLoad.DLThr
uput.MPU
Throughput of PS
Downlink Data for
MPU
Earlier than
BSC6900
V900R011
None
Throughput of PS Uplink Data for MPU

Counters
Counter ID
Counter Name
Counter Description
67204521
VS.PSLoad.ULThruput.MP
U
Throughput of PS Uplink
Data for MPU
Description
This counter provides the total uplink PS throughput in the MPU subsystem, including
retransmitted data. This counter is measured at the Radio Link Control (RLC) layer, whereas
RLC headers are not measured. During soft handovers, the throughput is measured before the
RNC combines the traffic on each link.
Measurement point
The RNC takes samples on the uplink traffic of all PS services every five seconds in the specified
measurement period. At the end of the measurement period, the RNC divides the accumulated
uplink traffic by the sampling duration to obtain the uplink PS throughput of the MPU in the
measurement period.
Issue 03 (2015-06-30)

396
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PSLoad.ULThruput.MP
U
WRFD-040100
Flow Control
Throughput of PS Downlink Data for MPU

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

397
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.PSLoad.DLThruput.MP
U
WRFD-040100
Flow Control
1.7 Measurement of NodeB Performance(NODEB)

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

Overview
The NodeB algorithm measurement involves the Iub congestion measurement, NodeB
unavailability measurement, dynamic spectrum sharing measurement, and 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.
Counters providing NodeB credit resource consumption for UE admission are number of times
the uplink credit resource utilization for UE admission of a NodeB is in a certain range, downlink
NodeB credit resource consumption for UE admission, and NodeB credit usage when CE
Issue 03 (2015-06-30)

398
BSC6900 UMTS
Overbooking is enabled. With these counters, you can determine whether to expand CE resources
and you can locate CE-related faults.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192134
VS.IUB.UL.Cong.
Num
Number of Iub UL
Congestions
Earlier than
BSC6900
V900R011
67192135
VS.IUB.DL.Cong.
Num
Number of Iub DL
Congestions
Earlier than
BSC6900
V900R011
67203854
VS.IUB.UL.Cong.T
ime
Duration of Iub UL
Congestion
Earlier than
BSC6900
V900R011
67203855
VS.IUB.DL.Cong.T
ime
Duration of Iub DL
Congestion
Earlier than
BSC6900
V900R011
67203853
VS.NodeB.UnavailTime
Duration of NodeB
Unavailability
Earlier than
BSC6900
V900R011
73441119
VS.DSS.NodeB.Act
.Duration
Total Dynamic
Spectrum Sharing
(DSS) Activation
Duration
BSC6900
V900R013
73423295
VS.DSS.NodeB.Act
.Num
Number of Received
Dynamic Spectrum
Sharing (DSS)
BSC6900
V900R013
73423296
VS.DSS.NodeB.Nor
malDeAct.Num
Number of Normal
Spectrum
Withdrawals
BSC6900
V900R013
73423297
VS.DSS.NodeB.Urg
entDeAct.Num
Number of Urgent
Spectrum
Withdrawals
BSC6900
V900R013
73423298
VS.DSS.NodeB.Ab
normalDeAct.Num
Number of
Abnormal Spectrum
Withdrawals
BSC6900
V900R013
73441218
VS.NodeB.ULCred
itUsed.Mean
Average NodeB
Uplink Credit Usage
When CE
Overbooking Is
Enabled for NodeB
BSC6900
V900R014

399
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424007
VS.NodeB.ULCred
itUsed.Max
Maximum NodeB
Uplink Credit Usage
When CE
Overbooking Is
Enabled for NodeB
BSC6900
V900R014
73424008
VS.NodeB.ULCred
itUsed.Min
Minimum NodeB
Uplink Credit Usage
When CE
Overbooking Is
Enabled for NodeB
BSC6900
V900R014
73426948
VS.NodeB.ULCreditUsage.0
Number of Times the

Uplink NodeB Credit
Resource Utilization
for UE Admission Is
Between 0 per mill
(Included) and 250
per mill
BSC6900
V900R015
73426949
Number of Times the

Uplink NodeB Credit
for UE Admission Is
Between 250 per mill
(Included) and 500
per mill
BSC6900
V900R015
73426950
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 550
per mill
BSC6900
V900R015
73426951
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 600
per mill
BSC6900
V900R015

400
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426952
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 650
per mill
BSC6900
V900R015
73426953
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 700
per mill
BSC6900
V900R015
73426954
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 750
per mill
BSC6900
V900R015
73426955
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 800
per mill
BSC6900
V900R015
73426956
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 850
per mill
BSC6900
V900R015
73426957
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 900
per mill
BSC6900
V900R015

401
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426958
Number of Times the

Uplink NodeB Credit
for UE Admission Is
(Included) and 950
per mill
BSC6900
V900R015
73426959
Number of Times the

Uplink NodeB Credit
for UE Admission Is
Greater than or Equal
to 950 per mill
BSC6900
V900R015
73443299
VS.NodeB.DLCred
itUsed.Mean
Average Downlink
NodeB Credit
Resource
Consumption for UE
Admission
BSC6900
V900R015
73426963
VS.NodeB.DLCred
itUsed.Max
Maximum Downlink
NodeB Credit
Resource
Consumption for UE
Admission
BSC6900
V900R015
73426964
VS.NodeB.DLCred
itUsed.Min
Minimum Downlink
NodeB Credit
Resource
Consumption for UE
Admission
BSC6900
V900R015
73428316
VS.NodeB.DLCreditUsage.0
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
between 0 per mill
(Included) and 250
per mill
BSC6900
V900R015
73428317
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
between 250 per mill
(Included) and 500
per mill
BSC6900
V900R015

402
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428318
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 550
per mill
BSC6900
V900R015
73428319
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 600
per mill
BSC6900
V900R015
73428320
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 650
per mill
BSC6900
V900R015
73428321
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 700
per mill
BSC6900
V900R015
73428322
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 750
per mill
BSC6900
V900R015

403
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428323
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 800
per mill
BSC6900
V900R015
73428324
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 850
per mill
BSC6900
V900R015
73428325
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 900
per mill
BSC6900
V900R015
73428326
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is
(Included) and 950
per mill
BSC6900
V900R015
73428327
Number of Times
That NodeB
Downlink Credit
Usage for UE
Admission Is Is
to 950 per mill
BSC6900
V900R016
None
Issue 03 (2015-06-30)

404
BSC6900 UMTS
Number of UL or DL Congestions on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
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
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IUB.UL.Cong.Num
WRFD-020106
Load Reshuffling
VS.IUB.DL.Cong.Num
WRFD-020106
Load Reshuffling

405
BSC6900 UMTS
Time of UL or DL Congestions on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
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
Counter Name
Feature ID
Feature Name
VS.IUB.UL.Cong.Time
WRFD-020106
Load Reshuffling
VS.IUB.DL.Cong.Time
WRFD-020106
Load Reshuffling
Counter ID
Counter Name
Counter Description
67203853
Duration of NodeB
Unavailability
NodeB Unavailability Time

Counters
Issue 03 (2015-06-30)

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

Counters
Counter ID
Counter Name
Counter Description
73441119
VS.DSS.NodeB.Act.Duration
Total Dynamic Spectrum

Sharing (DSS) Activation
Duration
Description
This counter provides the duration when Dynamic Spectrum Sharing (DSS) is activated for a
NodeB.
Measurement point
The measurement starts when a NodeB receives a spectrum activation command and stops when
the NodeB receives a spectrum deactivation command. At the end of the measurement period,
DSS activation duration is accumulated in this NodeB.
Issue 03 (2015-06-30)

407
BSC6900 UMTS
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.DSS.NodeB.Act.Duration
MRFD-221802
GSM and UMTS Dynamic

Spectrum Sharing(UMTS)
Number of Received Dynamic Spectrum Sharing (DSS)

Counters
Counter ID
Counter Name
Counter Description
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.
Formula
None
Unit
None
Issue 03 (2015-06-30)

408
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.DSS.NodeB.Act.Num
MRFD-221802

Number of Normal Spectrum Withdrawals

Counters
Counter ID
Counter Name
Counter Description
73423296
VS.DSS.NodeB.NormalDe
Act.Num
Number of Normal Spectrum

Withdrawals
Description
This counter provides the number of received commands that instruct a NodeB in a normal
spectrum withdrawal.
Measurement point
spectrum deactivation command that instructs it in a normal spectrum withdrawal.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DSS.NodeB.NormalDe
Act.Num
MRFD-221802


409
BSC6900 UMTS
Number of Urgent Spectrum Withdrawals

Counters
Counter ID
Counter Name
Counter Description
73423297
VS.DSS.NodeB.UrgentDeA
ct.Num
Number of Urgent Spectrum

Withdrawals
Description
This counter provides the number of received commands that instruct a NodeB in an urgent
spectrum withdrawal.
Measurement point
spectrum deactivation command that instructs it in an urgent spectrum withdrawal.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DSS.NodeB.UrgentDeA
ct.Num
MRFD-221802

Number of Abnormal Spectrum Withdrawals

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423298
VS.DSS.NodeB.AbnormalD
eAct.Num
Number of Abnormal
Spectrum Withdrawals

410
BSC6900 UMTS
Description
This counter provides the number of times that connections between the RNC and the U2000
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 U2000.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DSS.NodeB.AbnormalD
eAct.Num
MRFD-221802

NodeB Credit Usage When CE Overbooking Is Enabled

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441218
VS.NodeB.ULCreditUsed.
Mean
Average NodeB Uplink

Credit Usage When CE
Overbooking Is Enabled for
NodeB
73424007
Max
Maximum NodeB Uplink

NodeB
73424008
Min
Minimum NodeB Uplink

NodeB

411
BSC6900 UMTS
Description
These counters measure the average, maximum, and minimum NodeB credit usage when CE
Overbooking is enabled. When CE Overbooking is disabled, the measurement result is 0.
Measurement point
The RNC takes samples of the NodeB credit usage when CE Overbooking is enabled in a
measurement period of 5s. At the end of the measurement period, the RNC obtains the maximum
and minimum NodeB credit usage, and then divides the accumulated NodeB credit usage by the
number of samples to obtain the average NodeB credit usage in the measurement period.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Mean
WRFD-140212
CE Overbooking
Max
WRFD-140212
CE Overbooking
Min
WRFD-140212
CE Overbooking
Number of Times the Uplink Credit Resource Utilization for UE Admission of a

NodeB Is in a Certain Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426948
VS.NodeB.ULCreditUsage.
0
Number of Times the Uplink

NodeB Credit Resource
Utilization for UE Admission
Is Between 0 per mill
(Included) and 250 per mill

412
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426949
1

73426950
2

73426951
3

73426952
4

73426953
5

73426954
6

73426955
7

73426956
8


413
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426957
9

73426958
10

73426959
11

Is Greater than or Equal to
950 per mill
Description
These counters provide the number of times the uplink credit resource utilization for UE
admission of a NodeB is in a certain range. You can divide the value of one counter by the sum
of values of these counters to obtain the proportion of a certain range to the total ranges in a
measurement period.
Measurement point
The RNC samples the uplink NodeB credit resource consumption for UE admission every 5
seconds. The RNC divides a sample result by the maximum quantity of available uplink NodeB
credit resources to obtain the uplink NodeB credit resource utilization. After this, a certain
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
0
WRFD-020101
Admission Control

414
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
1
WRFD-020101
Admission Control
2
WRFD-020101
Admission Control
3
WRFD-020101
Admission Control
4
WRFD-020101
Admission Control
5
WRFD-020101
Admission Control
6
WRFD-020101
Admission Control
7
WRFD-020101
Admission Control
8
WRFD-020101
Admission Control
9
WRFD-020101
Admission Control
10
WRFD-020101
Admission Control
11
WRFD-020101
Admission Control
Downlink NodeB Credit Resource Consumption for UE Admission

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73443299
VS.NodeB.DLCreditUsed.
Mean
Average Downlink NodeB

Credit Resource
Consumption for UE
Admission
73426963
Max
Maximum Downlink NodeB

Credit Resource
Consumption for UE
Admission

415
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426964
Min
Minimum Downlink NodeB

Credit Resource
Consumption for UE
Admission
Description
These counters provide the average, maximum, and minimum downlink NodeB credit resource
consumption for UE admission.
Measurement point
The RNC samples the downlink NodeB credit resource consumption for UE admission every 5
seconds. At the end of a measurement period, the RNC determines the maximum and minimum
downlink NodeB credit resource consumption in the period. The RNC divides the accumulated
consumption in the period by the number of samples to obtain the average downlink NodeB
credit resource consumption in the period.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Mean
WRFD-020101
Admission Control
Max
WRFD-020101
Admission Control
Min
WRFD-020101
Admission Control

416
BSC6900 UMTS
Number of Times That NodeB Downlink Credit Usage Falls in to Different Value
Ranges
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428316
VS.NodeB.DLCreditUsage.
0
Number of Times That

NodeB Downlink Credit
Usage for UE Admission Is
between 0 per mill(Included)
and 250 per mill
73428317
1

73428318
2

73428319
3

73428320
4

73428321
5

73428322
6


417
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428323
7

73428324
8

73428325
9

73428326
10

73428327
11

Usage for UE Admission Is Is
Greater than or Equal to 950
per mill
Description
These counters measure the number of times that NodeB downlink credit usage for UE admission
falls in to different value ranges in a measurement period. The percentage of a value range in a
measurement period can be calculated by dividing the measurement times in this value range
by the total number of measurement times. For example, Percentage of [0 per mille, 250 per
mille ) = VS.NodeB.DLCreditUsage.0/(Sum of VS.NodeB.DLCreditUsage.0 through
VS.NodeB.DLCreditUsage.11)
Measurement point
The RNC takes samples of NodeB credit resources occupied by UEs in the downlink every 5
seconds in a measurement period, and then divides the sample values by the maximum allowed
NodeB credit resources to obtain the downlink credit usage (measured in millesimal ). The RNC
then calculates the number of times that the downlink credit usage falls in to different value
ranges.
Issue 03 (2015-06-30)

418
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
0
WRFD-020101
Admission Control
1
WRFD-020101
Admission Control
2
WRFD-020101
Admission Control
3
WRFD-020101
Admission Control
4
WRFD-020101
Admission Control
5
WRFD-020101
Admission Control
6
WRFD-020101
Admission Control
7
WRFD-020101
Admission Control
8
WRFD-020101
Admission Control
9
WRFD-020101
Admission Control
10
WRFD-020101
Admission Control
11
WRFD-020101
Admission Control

419
BSC6900 UMTS
1.8 Measurement of Load Sharing Node Performance

(NODESHARE)
Overview
This measurement object measures the performance of load sharing users between physical
RNCs.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
RAB.NODESHARE
RAB Measurement per Load Sharing Node
RRC.NODESHARE
RRC Measurement per Load Sharing Node
TRAFFIC.NODESHARE
Traffic Measurement per Load Sharing Node
1.8.1 RAB Measurement per Load Sharing Node

(RAB.NODESHARE)
Overview
This function subset provides RAB measurement for UEs whose load is shared between physical
RNC nodes.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426004
VS.RAB.AttEstab
CS.Conv.NodeShare
Number of CS RAB
Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Conversational
Service)
BSC6900
V900R015C00

420
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426005
VS.RAB.SuccEstab
CS.Conv.NodeShare
Number of
Successful CS RAB
Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Conversational
Service)
BSC6900
V900R015C00
73426006
VS.RAB.AttEstabP
S.Bkg.NodeShare
Number of PS RAB
Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Background
Service)
BSC6900
V900R015C00
73426007
VS.RAB.AttEstabP
S.Int.NodeShare
Number of PS RAB
Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Interactive Service)
BSC6900
V900R015C00
73426008
VS.RAB.SuccEstab
PS.Bkg.NodeShare
Number of
Successful PS RAB
Assignment
Requests for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
(Background
Service)
BSC6900
V900R015C00
73426009
VS.RAB.SuccEstab
PS.Int.NodeShare
Number of
Successful PS RAB
assignment Requests
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
(Interactive Service)
BSC6900
V900R015C00

421
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426010
VS.RAB.AbnormR
el.CS.RF.NodeShare
Number of CS RABs
Released
Abnormally due to
Radio Link Failure
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73426011
VS.RAB.AbnormR
el.PS.RF.NodeShare
Number of PS RABs
Released
Abnormally due to
Radio Link Failure
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73426012
VS.RAB.AbnormR
el.CS.NodeShare
Number of CS RABs
Released
Abnormally for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73426013
VS.RAB.AbnormR
el.PS.NodeShare
Number of PS RABs
Released
Abnormally for UEs
Whose Load Is
Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73426014
VS.RAB.NormRel.
CS.NodeShare
Number of CS RABs
Released Normally
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73426015
VS.RAB.NormRel.
PS.NodeShare
Number of PS RABs
Released Normally
for UEs Whose Load
Is Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
None
Issue 03 (2015-06-30)

422
BSC6900 UMTS
Number of CS RAB Assignment Requests for UEs Whose Load Is Shared Between
Physical RNC Nodes (Conversational Service)
Counters
Counter ID
Counter Name
Counter Description
73426004
VS.RAB.AttEstabCS.Conv.
NodeShare
Number of CS RAB
Assignment Requests for
UEs Whose Load Is Shared
Between Physical RNC
Nodes (Conversational
Service)
Description
This function subset provides the number of CS RAB assignment requests for UEs whose load
is shared between physical RNC nodes.This counter complies with section "8.2 RAB
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-180 RAB setup procedure (successful operation)
Issue 03 (2015-06-30)

423
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
NodeShare
WRFD-150211
RNC in Pool Load Sharing
Number of Successful CS RAB Assignment Requests for UEs Whose Load Is

Shared Between Physical RNC Nodes (Conversational Service)
Counters
Counter ID
Counter Name
Counter Description
73426005
VS.RAB.SuccEstabCS.Con
v.NodeShare
Number of Successful CS
RAB Assignment Requests
for UEs Whose Load Is
Shared Between Physical
RNC Nodes (Conversational
Service)
Description
This function subset provides the number of successful CS RAB assignment requests for UEs
whose load is shared between physical RNC nodes.This counter complies with section "8.2 RAB
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.
Issue 03 (2015-06-30)

424
BSC6900 UMTS
The figure shows the access procedure of a CS called party after the parallel handling of the
alerting procedure is enabled. The measurement is triggered at point B in the figure. When the
RNC receives a RADIO BEARER SETUP COMPLETE message from the UE, this counter is
measured based on the CS service type and RNC physical node if the UE load is shared by
different RNCs.
Issue 03 (2015-06-30)

425
BSC6900 UMTS
Figure 1-182 Parallel handling of the alerting and RAB setup procedures
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
v.NodeShare
WRFD-150211
WRFD-171202

426
BSC6900 UMTS
Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between
Physical RNC Nodes (Background Service)
Counters
Counter ID
Counter Name
Counter Description
73426006
VS.RAB.AttEstabPS.Bkg.N
odeShare
Number of PS RAB
Nodes (Background Service)
73426007
VS.RAB.AttEstabPS.Int.No
deShare
Number of PS RAB
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.The preceding counters comply with section "8.2 RAB
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.
Issue 03 (2015-06-30)

427
BSC6900 UMTS
Figure 1-183 Successful RAB setup procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabPS.Bkg.N
odeShare
WRFD-150211
VS.RAB.AttEstabPS.Int.No
deShare
WRFD-150211

428
BSC6900 UMTS
Number of Successful PS RAB Assignment Requests for UEs Whose Load Is

Shared Between Physical RNC Nodes (Background Service)
Counters
Counter ID
Counter Name
Counter Description
73426008
VS.RAB.SuccEstabPS.Bkg.
NodeShare
Number of Successful PS
RAB Assignment Requests
RNC Nodes (Background
Service)
73426009
VS.RAB.SuccEstabPS.Int.N
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.The preceding counters comply with section
"8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
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 PS service type and
physical RNC node if the UE load is shared between physical RNC nodes.
Issue 03 (2015-06-30)

429
BSC6900 UMTS
Figure 1-184 PS RAB setup procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
NodeShare
WRFD-150211
VS.RAB.SuccEstabPS.Int.N
odeShare
WRFD-150211

430
BSC6900 UMTS
Number of CS RABs Released Abnormally due to Radio Link Failure for UEs
Whose Load Is Shared Between Physical RNC Nodes
Counters
Counter ID
Counter Name
Counter Description
73426010
VS.RAB.AbnormRel.CS.RF
.NodeShare
Number of CS RABs
Released Abnormally due to
Radio Link Failure for UEs
Whose Load Is Shared
Nodes
73426011
VS.RAB.AbnormRel.PS.RF
.NodeShare
Number of PS RABs
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.The preceding counters comply with
section "8.2 RAB Assignment" ,"8.3 RAB Release Request","8.4 Iu Release Request" and "8.5
Iu Release" in 3GPP TS 25.413 (v10.10.0).
Measurement point
This measurement is triggered at point A shown in the figure. When radio link failure occurs,
the RNC sends a RAB RELEASE REQUEST message to the CN with the cause value of "Radio
Connection With UE Lost" or "Failure in the Radio Interface Procedure." Then, when the RNC
receives a RAB ASSIGNMENT REQUEST message from the CN with a cause value other than
"User Inactivity," "Normal Release," "Successful Relocation," and "Network Optimization,"
this counter is measured based on the service domain and the physical RNC node if the UE load
is shared between physical RNC nodes. For details on cause values indicating a normal release,
see 3GPP TS 25.413.
Issue 03 (2015-06-30)

431
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.
Issue 03 (2015-06-30)

432
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.
Issue 03 (2015-06-30)

433
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.NodeShare
WRFD-150211
.NodeShare
WRFD-150211

434
BSC6900 UMTS
Number of CS RABs Released Abnormally for UEs Whose Load Is Shared Between
Physical RNC Nodes
Counters
Counter ID
Counter Name
Counter Description
73426012
VS.RAB.AbnormRel.CS.No
deShare
Number of CS RABs
Released Abnormally for
Nodes
73426013
VS.RAB.AbnormRel.PS.No
deShare
Number of PS RABs
Released Abnormally for
Nodes
Description
This counter provides the number of RABs released abnormally for UEs whose load is shared
between physical RNC nodes.The preceding counters comply with section "8.2 RAB
Assignment" ,"8.3 RAB Release Request","8.4 Iu Release Request" and "8.5 Iu Release" in
3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

435
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.
Issue 03 (2015-06-30)

436
BSC6900 UMTS
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.
Issue 03 (2015-06-30)

437
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.CS.No
deShare
WRFD-150211
VS.RAB.AbnormRel.PS.No
deShare
WRFD-150211

438
BSC6900 UMTS
Number of CS RABs Released Normally for UEs Whose Load Is Shared Between
Physical RNC Nodes
Counters
Counter ID
Counter Name
Counter Description
73426014
VS.RAB.NormRel.CS.NodeShare
Number of CS RABs
Released Normally for UEs
Nodes
73426015
VS.RAB.NormRel.PS.NodeShare
Number of PS RABs
Released Normally for UEs
Nodes
Description
This counter provides the number of RABs released normally for UEs whose load is shared
between physical RNC nodes.The preceding counters comply with section "8.2 RAB
3GPP TS 25.413 (v10.10.0).
Measurement point
This measurement is triggered at point A shown in the figure. After receiving an IU RELEASE
COMMAND message from the CN, the RNC releases the corresponding RAB and then sends
an IU RELEASE COMPLETE message to the CN. If the release cause in the IU RELEASE
COMMAND message is "User Inactivity," "Normal Release," "Successful Relocation," or
"Network Optimization," or if the RNC has sent a release request with the cause value of "User
Inactivity," "Network Optimization," or "UE Generated Signalling Connection Release" before
the RNC receives the IU RELEASE COMMAND message, then this counter is measured based
physical RNC nodes.
Issue 03 (2015-06-30)

439
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 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.
Issue 03 (2015-06-30)

440
BSC6900 UMTS
Figure 1-192 Successful RAB release procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.CS.NodeShare
WRFD-150211
VS.RAB.NormRel.PS.NodeShare
WRFD-150211
1.8.2 RRC Measurement per Load Sharing Node

(RRC.NODESHARE)
Overview
This function subset provides RRC measurement for UEs whose load is shared between physical
RNC nodes.
Issue 03 (2015-06-30)

441
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426016
VS.RRC.AttConnE
stab.NodeShare
Number of RRC
Connection Requests
Sent by UEs Whose
Load Is Shared
Between Physical
RNC Nodes
BSC6900
V900R015C00
73426017
VS.RRC.SuccConn
Estab.NodeShare
Number of
Successful RRC
Connection Requests
Sent by UEs Whose
Load Is Shared
Between Physical
RNC Nodes
BSC6900
V900R015C00
73426018
VS.RRC.ConnEsta
bTimeMax.CellDC
H.NodeShare
Maximum Delay in
Setting Up RRC
Connection for UEs
in CELL_DCH State
Whose Load Is
Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73426020
VS.RRC.ConnEsta
bTimeMax.CellFA
CH.NodeShare
Maximum Delay in
Setting Up RRC
Connection for UEs
in CELL_FACH
State Whose Load Is
Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73426019
VS.RRC.ConnEsta
bTimeMean.CellD
CH.NodeShare
Average Delay in
Setting Up RRC
Connection for UEs
in CELL_DCH State
Whose Load Is
Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73426021
VS.RRC.ConnEsta
bTimeMean.CellF
ACH.NodeShare
Average Delay in
Setting Up RRC
Connection for UEs
in CELL_FACH
State Whose Load Is
Shared Between
Physical RNC Nodes
BSC6900
V900R015C00

442
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426167
VS.LoadSharedAct
iveUEs.NodeShare
Number of UEs
Whose Load Is
Shared Between
Physical RNC Nodes
BSC6900
V900R015C00
73444452
VS.UPLoadShared
ActiveUEs.NodeShare
Number of UEs
Whose Load Is
Shared Between the
UPs of Physical
RNCs
BSC6900
V900R016C00
73430310
VS.LoadSharedAct
iveUEs.Max.NodeShare
Maximum Number
of UEs Whose Load
Is Shared Between
Physical RNC Nodes
for RNC
BSC6900
V900R017C10
73430311
VS.UPLoadShared
ActiveUEs.Max.No
deShare
Maximum Number
of UEs Whose Load
Is Shared Between
the UPs of Physical
RNC Nodes for RNC
BSC6900
V900R017C10
73446361
VS.LoadSharedCel
lPCHUEs.NodeShare
Number of
CELL_PCH UEs
Whose Load Is
Shared Between
Physical RNC Nodes
for RNC
BSC6900
V900R017C10
73446362
VS.LoadSharedUr
aPCHUEs.NodeShare
Number of
URA_PCH UEs
Whose Load Is
Shared Between
Physical RNC Nodes
for RNC
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

443
BSC6900 UMTS
Number of RRC Connection Requests Sent by UEs Whose Load Is Shared Between
Physical RNC Nodes
Counters
Counter ID
Counter Name
Counter Description
73426016
VS.RRC.AttConnEstab.NodeShare

Requests Sent by UEs Whose
Load Is Shared Between
Physical RNC Nodes
Description
This counter provides the number of RRC connection requests sent by UEs whose load is shared
between physical RNC nodes.This counter does not include the RRC connection setup requests
in the Directed Signalling Connection Re-establishment (DSCR) procedure triggered by the
overlapping of the RRC connection setup procedure and cell update procedure.This counter
complies with section "8.1.3 RRC connection establishment" in 3GPP TS 25.331 (v10.13.0).
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.This counter does not include the RRC
procedure.
Figure 1-193 Procedure for successful RRC connection setup
Issue 03 (2015-06-30)

444
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnEstab.NodeShare
WRFD-150211
Number of Successful RRC Connection Requests Sent by UEs Whose Load Is

Shared Between Physical RNC Nodes
Counters
Counter ID
Counter Name
Counter Description
73426017
VS.RRC.SuccConnEstab.N
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.This counter complies with section "8.1.3 RRC
connection establishment" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

445
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.SuccConnEstab.N
odeShare
WRFD-150211

446
BSC6900 UMTS
Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is
Counters
Counter ID
Counter Name
Counter Description
73426018
VS.RRC.ConnEstabTimeM
ax.CellDCH.NodeShare
Maximum Delay in Setting

Up RRC Connection for UEs
in CELL_DCH State Whose
Physical RNC Nodes
73426019
ean.CellDCH.NodeShare
Average Delay in Setting Up

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.
Counter ID
Counter Name
Counter Description
73426180
VS.RRC.ConnEstabTime.C
ellDCH.NodeShare.Cum
Cumulative Duration of
Setting Up RRC Connection
for UEs in CELL_DCH State
Nodes
73426181
ellDCH.NodeShare.Sample
Number of Samples in
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.The preceding counters comply with
section "8.1.3 RRC connection establishment" in 3GPP TS 25.331 (v10.13.0).
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
Issue 03 (2015-06-30)

447
BSC6900 UMTS
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.
Formula
VS.RRC.ConnEstabTimeMean.CellDCH.NodeShare =
[VS.RRC.ConnEstabTime.CellDCH.NodeShare.Cum]/
[VS.RRC.ConnEstabTime.CellDCH.NodeShare.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ax.CellDCH.NodeShare
WRFD-150211
ean.CellDCH.NodeShare
WRFD-150211

448
BSC6900 UMTS
Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is
Counters
Counter ID
Counter Name
Counter Description
73426020
ax.CellFACH.NodeShare
Maximum Delay in Setting

Up RRC Connection for UEs
in CELL_FACH State
Nodes
73426021
ean.CellFACH.NodeShare
Average Delay in Setting Up

RRC Connection for UEs in
CELL_FACH State Whose
Physical RNC Nodes
specific formulas.
Counter ID
Counter Name
Counter Description
73426182
ellFACH.NodeShare.Cum
Cumulative Duration of
for UEs in CELL_FACH
State Whose Load Is Shared
Nodes
73426183
ellFACH.NodeShare.Sample
Number of Samples in
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.The preceding counters
comply with section "8.1.3 RRC connection establishment" in 3GPP TS 25.331 (v10.13.0).
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
Issue 03 (2015-06-30)

449
BSC6900 UMTS
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.
Formula
VS.RRC.ConnEstabTimeMean.CellFACH.NodeShare =
[VS.RRC.ConnEstabTime.CellFACH.NodeShare.Cum]/
[VS.RRC.ConnEstabTime.CellFACH.NodeShare.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ax.CellFACH.NodeShare
WRFD-150211
ean.CellFACH.NodeShare
WRFD-150211

450
BSC6900 UMTS
Number of UEs Whose Load Is Shared Between Physical RNC Nodes

Counters
Counter ID
Counter Name
Counter Description
73426167
VS.LoadSharedActiveUEs.
NodeShare
Number of UEs Whose Load

Is Shared Between Physical
RNC Nodes
Description
This counter provides the number of UEs whose load is shared between physical RNC nodes.
Measurement point
The RNC takes samples of UEs which are in CELL_DCH and CELL_FACH states after the
logic RNC shares the load with the overflow RNC every five seconds. Then, the RNC adds the
numbers of UEs in CELL_DCH and CELL_FACH states. At the end of the measurement period,
the RNC divides the accumulated value on every sampling point in the measurement period by
the number of samples to obtain the number of UEs whose load is shared between physical RNC
nodes. NOTE: This counter is measured only on the master physical RNC corresponding to the
logic RNC.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
NodeShare
WRFD-150211

451
BSC6900 UMTS
Number of UEs Whose Load Is Shared Between the UPs of Physical RNCs
Counters
Counter ID
Counter Name
Counter Description
73444452
VS.UPLoadSharedActiveU
Es.NodeShare
Number of UEs Whose Load

Is Shared Between the UPs of
Physical RNCs
Description
This counter provides the number of UEs whose load is shared between the user planes (UPs)
of different physical RNCs.
Measurement point
The system takes samples of UEs that are in the CELL_DCH and CELL_FACH states and whose
load is forwarded to the UP of an overflow RNC for processing every five seconds. At the end
of a measurement period, the RNC divides the accumulated value in the period by the number
of sampling times to obtain the number of UEs whose load is shared between the UPs of different
physical RNCs. This counter is measured only on the master RNC.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Es.NodeShare
WRFD-150211

452
BSC6900 UMTS
Maximum Number of UEs Whose Load Is Shared Between Physical RNC Nodes
for RNC
Counters
Counter ID
Counter Name
Counter Description
73430310
Max.NodeShare
Maximum Number of UEs

Nodes for RNC
Description
This counter provides the maximum number of UEs whose load is shared between physical RNC
nodes in an RNC.
Measurement point
The system samples the number of UEs in the CELL_DCH and CELL_FACH states whose
services are taken over by an overflow RNC every five seconds in a measurement period. At the
end of the measurement period, the system uses the maximum number as the value of this
counter.NOTE: This counter is measured only on the master physical RNC corresponding to the
logic RNC.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Max.NodeShare
WRFD-150211

453
BSC6900 UMTS
Maximum Number of UEs Whose Load Is Shared Between the UPs of Physical RNC
Nodes for RNC
Counters
Counter ID
Counter Name
Counter Description
73430311
Es.Max.NodeShare

Between the UPs of Physical
RNC Nodes for RNC
Description
This counter provides the maximum number of UEs whose load is shared between the user planes
(UPs) of physical RNC nodes in an RNC.
Measurement point
The system samples the number of UEs in the CELL_DCH and CELL_FACH states whose
services are taken over by the UP of an overflow RNC every five seconds in a measurement
period. At the end of the measurement period, the system uses the maximum number as the value
of this counter. NOTE: This counter is measured only on the master physical RNC corresponding
to the logic RNC.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Es.Max.NodeShare
WRFD-150211

454
BSC6900 UMTS
Number of CELL_PCH UEs Whose Load Is Shared Between Physical RNC Nodes
for RNC
Counters
Counter ID
Counter Name
Counter Description
73446361
VS.LoadSharedCellPCHUE
s.NodeShare
Number of CELL_PCH UEs

Nodes for RNC
Description
This counter provides the number of UEs in the CELL_PCH state whose signaling data or data
services are shared between the physical RNC nodes in an RNC.
Measurement point
The system samples the number of UEs in the CELL_PCH state whose services are taken over
by an overflow RNC every five seconds in a measurement period. At the end of the measurement
period, the system obtains the value of this counter by dividing the accumulated number by the
number of times sampled. NOTE: This counter is measured only on the master physical RNC
corresponding to the logic RNC.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LoadSharedCellPCHUE
s.NodeShare
WRFD-150211

455
BSC6900 UMTS
Number of URA_PCH UEs Whose Load Is Shared Between Physical RNC Nodes
for RNC
Counters
Counter ID
Counter Name
Counter Description
73446362
VS.LoadSharedUraPCHUEs
.NodeShare
Number of URA_PCH UEs

Nodes for RNC
Description
This counter provides the number of UEs in the URA_PCH state whose signaling data or data
services are shared between the physical RNC nodes in an RNC.
Measurement point
The system samples the number of UEs in the URA_PCH state whose services are taken over
by an overflow RNC every five seconds in a measurement period. At the end of the measurement
period, the system obtains the value of this counter by dividing the accumulated number by the
number of times sampled.NOTE: This counter is measured only on the master physical RNC
corresponding to the logic RNC.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LoadSharedUraPCHUEs
.NodeShare
WRFD-150211
1.8.3 Traffic Measurement per Load Sharing Node

(TRAFFIC.NODESHARE)
Overview
This counter measures the traffic volume of a load sharing node. The counter is incremented
when RNC in Pool supports user-plane load sharing. Depending on whether Iub user-plane data
Issue 03 (2015-06-30)

456
BSC6900 UMTS
passes through the Iur-p interface, user-plane load sharing has the following cases: Case 1: Iub
user-plane data is transferred from the overflow RNC and does not pass through the Iur-p
interface. Case 2: Iub user-plane data is transferred from the master RNC and passes through
the Iur-p interface. Depending on whether Iur user-plane data passes through the Iur-p interface,
user-plane load sharing has the following cases. Case 3: Iur user-plane data is transferred from
the overflow RNC and does not pass through the Iur-p interface. Case 4: Iur user-plane data is
transferred from the master RNC and passes through the Iur-p interface.
Figure 1-197 RNC in Pool load sharing on the user plane
Issue 03 (2015-06-30)

457
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73443320
VS.CSLoad.Erlang
.Equiv.NodeShare
Average Equivalent
Erlangs Consumed
by CS Load Sharing
Users Between
Physical RNC Nodes
for an RNC
BSC6900
V900R015C01
73443321
VS.R99PSLoad.DL
Thruput.NodeShare
DL R99 Average
Traffic of Load
Sharing Users
Between Physical
RNC Nodes for an
RNC in the PS
Domain
BSC6900
V900R015C01
73443322
VS.R99PSLoad.UL
Thruput.NodeShare
UL R99 Average
Traffic of Load
Sharing Users
Between Physical
RNC Nodes in the PS
Domain
BSC6900
V900R015C01
73443323
VS.HSDPAPSLoad
.DLThruput.NodeShare
HSDPA Average
Traffic of Load
Sharing Users
Between Physical
RNC Nodes for an
RNC in the PS
Domain
BSC6900
V900R015C01
73443324
VS.HSUPAPSLoad
.ULThruput.NodeShare
HSUPA Average
Traffic of Load
Sharing Users
Between Physical
RNC Nodes for an
RNC in the PS
Domain
BSC6900
V900R015C01
73443325
VS.Iurp.IubBytesD
CH.Tx.NodeShare
DL Iub DCH Traffic

Passing Through the
Iur-p Interface of
Load Sharing Users
Between Physical
RNC Nodes for an
RNC
BSC6900
V900R015C01

458
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73443326
VS.Iurp.IubBytesH
SDPA.Tx.NodeShare
Iub HSDPA Traffic

Passing Through the
Iur-p Interface of
Load Sharing Users
Between Physical
RNC Nodes for an
RNC
BSC6900
V900R015C01
73443327
VS.Iurp.IubBytesD
CH.Rx.NodeShare
UL Iub DCH Traffic

Passing Through the
Iur-p Interface of
Load Sharing Users
Between Physical
RNC Nodes for an
RNC
BSC6900
V900R015C01
73443328
VS.Iurp.IubBytesH
SUPA.Rx.NodeShare
Iub HSUPA Traffic

Passing Through the
Iur-p Interface of
Load Sharing Users
Between Physical
RNC Nodes for an
RNC
BSC6900
V900R015C01
73443329
VS.Iurp.IurBytesD
CH.Tx.NodeShare
DL Iur DCH Traffic

Passing Through the
Iur-p Interface of
Load Sharing Users
Between Physical
RNC Nodes for an
RNC
BSC6900
V900R015C01
73443330
VS.Iurp.IurBytesH
SDPA.Tx.NodeShare
Iur HSDPA Traffic

Passing Through the
Iur-p Interface of
Load Sharing Users
Between Physical
RNC Nodes for an
RNC
BSC6900
V900R015C01
73443331
VS.Iurp.IurBytesD
CH.Rx.NodeShare
Iur DCH Traffic

Passing Through the
Iur-p Interface of
Load Sharing Users
Between Physical
RNC Nodes for an
RNC
BSC6900
V900R015C01

459
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73443332
VS.Iurp.IurBytesH
SUPA.Rx.NodeShare
Iur HSUPA Traffic

Passing Through the
Iur-p Interface of
Load Sharing Users
Between Physical
RNC Nodes for an
RNC
BSC6900
V900R015C01
73430312
VS.CSLoad.MaxEr
lang.Equiv.NodeShare
Maximum
CS Services Shared
Between Physical
RNC Nodes for RNC
BSC6900
V900R017C10
73430313
VS.R99PSLoad.Ma
xDLThruput.NodeShare
Maximum DL
Traffic of R99 PS
Services Shared
Between Physical
RNC Nodes for RNC
BSC6900
V900R017C10
73430314
VS.R99PSLoad.Ma
xULThruput.NodeShare
Maximum UL
Traffic of R99 PS
Services Shared
Between Physical
RNC Nodes for RNC
BSC6900
V900R017C10
73430315
VS.HSDPAPSLoad
.MaxDLThruput.N
odeShare
Maximum Traffic of
HSDPA PS Services
Shared Between
Physical RNC Nodes
for RNC
BSC6900
V900R017C10
73430316
VS.HSUPAPSLoad
.MaxULThruput.N
odeShare
Maximum Traffic of
HSUPA PS Services
Shared Between
Physical RNC Nodes
for RNC
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

460
BSC6900 UMTS
Average Equivalent Erlangs Consumed by CS Load Sharing Users Between

Physical RNC Nodes for an RNC
Counters
Counter ID
Counter Name
Counter Description
73443320
VS.CSLoad.Erlang.Equiv.N
odeShare
Average Equivalent Erlangs

Consumed by CS Load
Sharing Users Between
Physical RNC Nodes for an
RNC
Description
This counter measures the average equivalent Erlangs consumed by load sharing users between
the physical RNC nodes for an RNC on the user plane in the CS domain.
Measurement point
During a measurement period, the RNC samples the equivalent Erlangs of services in the CS
domain during every sampling period of 5 seconds. These services belong to the UEs that are
shifted from the master RNC of a logical RNC to the corresponding overflow RNC due to userplane load sharing. After the end of the measurement period, the RNC divides the accumulated
equivalent Erlangs by the number of sampling times to obtain the value of this counter, including
equivalent Erlangs of all links for the soft handover. Each time a CS service is admitted, its rate
is converted to equivalent Erlangs and equivalent Erlangs consumed by CS services under the
serving RNC are incremented. Each time a CS service is released, its rate is converted to
equivalent Erlangs and equivalent Erlangs consumed by CS services under the serving RNC are
reduced.
Formula
None
Unit
Erl
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.CSLoad.Erlang.Equiv.N
odeShare
WRFD-150211

461
BSC6900 UMTS
DL R99 Average Traffic of Load Sharing Users Between Physical RNC Nodes for
an RNC in the PS Domain
Counters
Counter ID
Counter Name
Counter Description
73443321
NodeShare
DL R99 Average Traffic of

Load Sharing Users Between
RNC in the PS Domain
Description
This counter measures the downlink R99 average traffic of load sharing users between physical
RNC nodes for an RNC on the user plane in the PS domain.
Measurement point
During a measurement period, the RNC samples the downlink R99 Traffic in the PS domain
during every sampling period of 5 seconds. The Traffic belongs to the UEs that are shifted from
the master RNC of a logical RNC to the corresponding overflow RNC due to user-plane load
sharing. After the end of the measurement period, the RNC divides the accumulated downlink
Traffic by the number of sampling times to obtain the value of this counter. Downlink R99
Traffic in the PS domain refers to data traffic excluding RLC headers that are measured by the
RLC layer. RLC retransmission traffic and soft handover traffic are included.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
NodeShare
WRFD-150211

462
BSC6900 UMTS
UL R99 Average Traffic of Load Sharing Users Between Physical RNC Nodes in
the PS Domain
Counters
Counter ID
Counter Name
Counter Description
73443322
NodeShare
UL R99 Average Traffic of

Physical RNC Nodes in the
PS Domain
Description
This counter measures the uplink R99 average traffic of load sharing users between physical
RNC nodes for an RNC on the user plane in the PS domain.
Measurement point
During a measurement period, the RNC samples the uplink R99 traffic in the PS domain during
every sampling period of 5 seconds. The traffic belongs to the UEs that are shifted from the
master RNC of a logical RNC to the corresponding overflow RNC due to user-plane load sharing.
After the end of the measurement period, the RNC divides the accumulated uplink traffic by the
number of sampling times to obtain the value of this counter. Uplink R99 traffic in the PS domain
refers to data traffic excluding RLC headers that are measured by the RLC layer. RLC
retransmission traffic and soft handover traffic are included.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
NodeShare
WRFD-150211

463
BSC6900 UMTS
HSDPA Average Traffic of Load Sharing Users Between Physical RNC Nodes for
Counters
Counter ID
Counter Name
Counter Description
73443323
put.NodeShare
HSDPA Average Traffic of

Description
This counter measures the HSDPA average traffic of load sharing users between physical RNC
nodes for an RNC on the user plane in the PS domain.
Measurement point
During a measurement period, the RNC samples the HSDPA traffic in the PS domain during
After the end of the measurement period, the RNC divides the accumulated traffic by the number
of sampling times to obtain the value of this counter. HSDPA traffic in the PS domain refers to
data traffic excluding RLC headers that are measured by the RLC layer. RLC retransmission
traffic and soft handover traffic are included.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
put.NodeShare
WRFD-150211

464
BSC6900 UMTS
HSUPA Average Traffic of Load Sharing Users Between Physical RNC Nodes for
Counters
Counter ID
Counter Name
Counter Description
73443324
put.NodeShare
HSUPA Average Traffic of

Description
This counter measures the HSUPA average traffic of load sharing users between physical RNC
nodes for an RNC on the user plane in the PS domain.
Measurement point
During a measurement period, the RNC samples the HSUPA traffic in the PS domain during
After the end of the measurement period, the RNC divides the accumulated traffic by the number
of sampling times to obtain the value of this counter. HSUPA traffic in the PS domain refers to
data traffic excluding RLC headers that are measured by the RLC layer. RLC retransmission
traffic and soft handover traffic are included.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
put.NodeShare
WRFD-150211

465
BSC6900 UMTS
DL Iub DCH Traffic Passing Through the Iur-p Interface of Load Sharing Users
Between Physical RNC Nodes for an RNC
Counters
Counter ID
Counter Name
Counter Description
73443325
VS.Iurp.IubBytesDCH.Tx.N
odeShare
DL Iub DCH Traffic Passing

Through the Iur-p Interface
of Load Sharing Users
Nodes for an RNC
Description
This counter measures the downlink Iub DCH traffic (including the service data and signaling
data) that needs to pass through the Iur-p interface of load sharing users between physical RNC
nodes for an RNC on the user plane.
Measurement point
As shown in the figure, physical RNCs (P_RNC1 and P_RNC2) form a pool that supports userplane load sharing. This measurement is triggered when P_RNC2 sends to P_RNC1 downlink
Iub DCH FP data over the Iur-p interface at point A. The FP header is not measured.
Figure 1-198 Procedure of downlink Iub DCH data passing through the Iur-p interface
Formula
None
Issue 03 (2015-06-30)

466
BSC6900 UMTS
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.Iurp.IubBytesDCH.Tx.N
odeShare
WRFD-150211
Iub HSDPA Traffic Passing Through the Iur-p Interface of Load Sharing Users
Counters
Counter ID
Counter Name
Counter Description
73443326
VS.Iurp.IubBytesHSDPA.T
x.NodeShare
Iub HSDPA Traffic Passing

Nodes for an RNC
Description
This counter measures the Iub HSDPA traffic (including the service data and signaling data)
that needs to pass through the Iur-p interface of load sharing users between physical RNC nodes
for an RNC on the user plane.
Measurement point
As shown in the figure, physical RNCs (P_RNC1 and P_RNC2) form a pool that supports userplane load sharing. This measurement is triggered when P_RNC2 sends to P_RNC1 Iub HSDSCH FP data over the Iur-p interface at point A. The FP header is not measured.
Issue 03 (2015-06-30)

467
BSC6900 UMTS
Figure 1-199 Procedure of Iub HSDPA data passing through the Iur-p interface
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.Iurp.IubBytesHSDPA.T
x.NodeShare
WRFD-150211
UL Iub DCH Traffic Passing Through the Iur-p Interface of Load Sharing Users
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73443327
VS.Iurp.IubBytesDCH.Rx.N
odeShare
UL Iub DCH Traffic Passing

Nodes for an RNC

468
BSC6900 UMTS
Description
This counter measures the uplink Iub DCH traffic (including the service data and signaling data)
Measurement point
As shown in the figure, physical RNCs (P_RNC1 and P_RNC2) form a pool that supports userplane load sharing. This measurement is triggered when P_RNC2 receives from P_RNC1 uplink
Iub DCH FP data over the Iur-p interface at point A. The FP header is not measured.
Figure 1-200 Procedure of uplink Iub DCH data passing through the Iur-p interface
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Iurp.IubBytesDCH.Rx.N
odeShare
WRFD-150211

469
BSC6900 UMTS
Iub HSUPA Traffic Passing Through the Iur-p Interface of Load Sharing Users
Counters
Counter ID
Counter Name
Counter Description
73443328
VS.Iurp.IubBytesHSUPA.R
x.NodeShare
Iub HSUPA Traffic Passing

Nodes for an RNC
Description
This counter measures the Iub HSUPA traffic (including the service data and signaling data)
Measurement point
As shown in the figure, physical RNCs (P_RNC1 and P_RNC2) form a pool that supports userplane load sharing. This measurement is triggered when P_RNC2 receives from P_RNC1 Iub
EDCH FP data over the Iur-p interface at point A. The FP header is not measured.
Figure 1-201 Procedure of Iub HSUPA data passing through the Iur-p interface
Formula
None
Issue 03 (2015-06-30)

470
BSC6900 UMTS
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.Iurp.IubBytesHSUPA.R
x.NodeShare
WRFD-150211
DL Iur DCH Traffic Passing Through the Iur-p Interface of Load Sharing Users
Counters
Counter ID
Counter Name
Counter Description
73443329
VS.Iurp.IurBytesDCH.Tx.N
odeShare
DL Iur DCH Traffic Passing

Nodes for an RNC
Description
This counter measures the downlink Iur DCH traffic (including the service data and signaling
data) that needs to pass through the Iur-p interface of load sharing users between physical RNC
nodes for an RNC on the user plane.
Measurement point
As shown in the figure, physical RNCs (P_RNC1 and P_RNC2) form a pool that supports userplane load sharing. This measurement is triggered when P_RNC2 sends to P_RNC1 downlink
Iur DCH FP data over the Iur-p interface at point A. The FP header is not measured.
Issue 03 (2015-06-30)

471
BSC6900 UMTS
Figure 1-202 Procedure of downlink Iur DCH data passing through the Iur-p interface
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.Iurp.IurBytesDCH.Tx.N
odeShare
WRFD-150211
Iur HSDPA Traffic Passing Through the Iur-p Interface of Load Sharing Users
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73443330
VS.Iurp.IurBytesHSDPA.Tx
.NodeShare
Iur HSDPA Traffic Passing

Nodes for an RNC

472
BSC6900 UMTS
Description
This counter measures the Iur HSDPA traffic (including the service data and signaling data) that
needs to pass through the Iur-p interface of load sharing users between physical RNC nodes for
an RNC on the user plane.
Measurement point
As shown in the figure, physical RNCs (P_RNC1 and P_RNC2) form a pool that supports userplane load sharing. This measurement is triggered when P_RNC2 sends to P_RNC1 Iur HSDSCH FP data over the Iur-p interface at point A. The FP header is not measured.
Figure 1-203 Procedure of Iur HSDPA data passing through the Iur-p interface
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Iurp.IurBytesHSDPA.Tx
.NodeShare
WRFD-150211

473
BSC6900 UMTS
Iur DCH Traffic Passing Through the Iur-p Interface of Load Sharing Users
Counters
Counter ID
Counter Name
Counter Description
73443331
VS.Iurp.IurBytesDCH.Rx.N
odeShare
Iur DCH Traffic Passing

Nodes for an RNC
Description
This counter measures the uplink Iur DCH traffic (including the service data and signaling data)
Measurement point
As shown in the figure, physical RNCs (P_RNC1 and P_RNC2) form a pool that supports userplane load sharing. This measurement is triggered when P_RNC2 receives from P_RNC1 uplink
Iur DCH FP data over the Iur-p interface at point A. The FP header is not measured.
Figure 1-204 Procedure of uplink Iur DCH data passing through the Iur-p interface
Formula
None
Issue 03 (2015-06-30)

474
BSC6900 UMTS
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.Iurp.IurBytesDCH.Rx.N
odeShare
WRFD-150211
Iur HSUPA Traffic Passing Through the Iur-p Interface of Load Sharing Users
Counters
Counter ID
Counter Name
Counter Description
73443332
VS.Iurp.IurBytesHSUPA.R
x.NodeShare
Iur HSUPA Traffic Passing

Nodes for an RNC
Description
This counter measures the Iur HSUPA traffic (including the service data and signaling data) that
needs to pass through the Iur-p interface of load sharing users between physical RNC nodes for
an RNC on the user plane.
Measurement point
As shown in the figure, physical RNCs (P_RNC1 and P_RNC2) form a pool that supports userplane load sharing. This measurement is triggered when P_RNC2 receives from P_RNC1 Iur
EDCH FP data over the Iur-p interface at point A. The FP header is not measured.
Issue 03 (2015-06-30)

475
BSC6900 UMTS
Figure 1-205 Procedure of Iur HSUPA data passing through the Iur-p interface
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.Iurp.IurBytesHSUPA.R
x.NodeShare
WRFD-150211
Maximum Equivalent Erlang of CS Services Shared Between Physical RNC Nodes

for RNC
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430312
iv.NodeShare

of CS Services Shared
Nodes for RNC

476
BSC6900 UMTS
Description
This counter provides the maximum equivalent Erlang of the CS services that are shared between
the UPs of physical RNC nodes in an RNC.
Measurement point
The system samples the equivalent Erlang of the CS services that are taken over by the UP of
another RNC every five seconds in a measurement period. At the end of the measurement period,
the system uses the maximum equivalent Erlang as the value of this counter. During the
measurement, whenever a CS service is admitted, its rate is converted to the equivalent Erlang,
which is then added to the equivalent Erlang of the RNC; whenever a CS service is released, its
rate is converted to the equivalent Erlang, which is then subtracted from the equivalent Erlang
of the RNC. The sampled value includes that equivalent Erlang of the radio links (RLs) during
soft handovers.
Formula
None
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
iv.NodeShare
WRFD-150211
Maximum DL Traffic of R99 PS Services Shared Between Physical RNC Nodes for
RNC
Counters
Counter ID
Counter Name
Counter Description
73430313
uput.NodeShare
Maximum DL Traffic of R99

PS Services Shared Between
Physical RNC Nodes for
RNC
Description
This counter provides the maximum downlink traffic of the R99 PS services that are shared
between the UPs of physical RNC nodes in an RNC.
Issue 03 (2015-06-30)

477
BSC6900 UMTS
Measurement point
The system samples the downlink traffic of the R99 PS services that are taken over by the UP
of another RNC every five seconds in a measurement period. At the end of the measurement
period, the system uses the maximum downlink traffic as the value of this counter. The downlink
traffic of R99 PS services is measured at the RLC layer, including the traffic of retransmitted
data and the traffic of all RLs during soft handovers and excluding RLC headers.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
uput.NodeShare
WRFD-150211
Maximum UL Traffic of R99 PS Services Shared Between Physical RNC Nodes for
RNC
Counters
Counter ID
Counter Name
Counter Description
73430314
uput.NodeShare
Maximum UL Traffic of R99

RNC
Description
This counter provides the maximum uplink traffic of the R99 PS services that are shared between
Measurement point
The system samples the uplink traffic of the R99 PS services that are taken over by the UP of
another RNC every five seconds in a measurement period. At the end of the measurement period,
the system uses the maximum uplink traffic as the value of this counter. The uplink traffic of
R99 PS services is measured at the RLC layer, including the traffic of retransmitted data and the
traffic of all RLs during soft handovers and excluding RLC headers.
Issue 03 (2015-06-30)

478
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
uput.NodeShare
WRFD-150211
Maximum Traffic of HSDPA PS Services Shared Between Physical RNC Nodes for
RNC
Counters
Counter ID
Counter Name
Counter Description
73430315
Thruput.NodeShare
Maximum Traffic of HSDPA

RNC
Description
This counter provides the maximum traffic of the HSDPA PS services that are shared between
Measurement point
The system samples the traffic of the HSDPA PS services that are taken over by the UP of another
RNC every five seconds in a measurement period. At the end of the measurement period, the
system uses the maximum traffic as the value of this counter. The traffic of HSDPA PS services
is measured at the RLC layer, including the traffic of retransmitted data and excluding RLC
headers.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

479
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
Thruput.NodeShare
WRFD-150211
Maximum Traffic of HSUPA PS Services Shared Between Physical RNC Nodes for
RNC
Counters
Counter ID
Counter Name
Counter Description
73430316
Thruput.NodeShare
Maximum Traffic of HSUPA

RNC
Description
This counter provides the maximum traffic of the HSUPA PS services that are shared between
Measurement point
The system samples the traffic of the HSUPA PS services that are taken over by the UP of another
RNC every five seconds in a measurement period. At the end of the measurement period, the
system uses the maximum traffic as the value of this counter. The traffic of HSUPA PS services
is measured at the RLC layer, including the traffic of retransmitted data and the traffic of all RLs
during soft handovers and excluding RLC headers.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Thruput.NodeShare
WRFD-150211

480
BSC6900 UMTS
1.9 Measurement of NodeB-Level CNOperator Performance

(PLMN_NodeB)
Overview
Measurement of NodeB-Level CNOperator Performance
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
PLMN.NodeB
NodeB-Level CNOperator Measurement
1.9.1 NodeB-Level CNOperator Measurement(PLMN.NodeB)

Overview
On the RNC side, measurements are performed at the NodeB level on a per operator basis.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425875
VS.NodeB.LDR.UL
.BERateDown.PL
MN
Number of UEs With

Decreased BE
Service Rate in the
Case of UL Credit
Resource
Congestion for
Operator
BSC6900
V900R015
73425876
VS.NodeB.ULCred
itUsed.Mean.PLM
N
Average NodeB
Credit Consumption
of an Operator in the
Uplink
BSC6900
V900R015
73425879
VS.NodeB.ULCred
itUsed.Max.PLMN
Maximum NodeB
Credit Consumption
Uplink
BSC6900
V900R015
73425880
VS.NodeB.DLCred
itUsed.Mean.PLM
N
Average NodeB
Credit Consumption
Downlink
BSC6900
V900R015

481
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73425883
VS.NodeB.DLCred
itUsed.Max.PLMN
Maximum NodeB
Credit Consumption
Downlink
BSC6900
V900R015
None
Number of UEs With Decreased BE Service Rate in the Case of UL Credit Resource
Congestion for Operator
Counters
Counter ID
Counter Name
Counter Description
73425875
VS.NodeB.LDR.UL.BERate
Down.PLMN
Number of UEs With

Decreased BE Service Rate
in the Case of UL Credit
Resource Congestion for
Operator
Description
This counter measures the number of UEs with decreased BE service rate when the uplink credit
resources for the operator of the UE are in basic congestion state and load reshuffling (LDR) is
triggered for the UEs of the operator.
Measurement point
When the uplink credit resources for an operator are in basic congestion state, the RNC decreases
the rates of UEs that belong to the operator and are performing the best effort (BE) service. This
counter is increased by one each time the RNC decreases the rate of a UE performing the BE
service.
Formula
None
Unit
None
Issue 03 (2015-06-30)

482
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.NodeB.LDR.UL.BERate
Down.PLMN
WRFD-150214
MOCN Independent CE
Resource Allocation
Average NodeB Credit Consumption of an Operator in the Uplink

Counters
Counter ID
Counter Name
Counter Description
73425876
Mean.PLMN
Average NodeB Credit

Consumption of an Operator
in the Uplink
Description
This counter measures the average NodeB credit consumption of an operator in the uplink.
Measurement point
The RNC takes samples of the NodeB credit resources occupied by the UEs of an operator in
the uplink every 5 seconds in a measurement period. At the end of the measurement period, the
RNC obtains the value of this counter by dividing the accumulated NodeB credit consumption
by the number of sampling times.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Mean.PLMN
WRFD-150214
MOCN Independent CE
Resource Allocation

483
BSC6900 UMTS
Maximum NodeB Credit Consumption of an Operator in the Uplink

Counters
Counter ID
Counter Name
Counter Description
73425879
Max.PLMN
Maximum NodeB Credit

in the Uplink
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
Counter Name
Feature ID
Feature Name
Max.PLMN
WRFD-150214
MOCN Independent CE
Resource Allocation
Average NodeB Credit Consumption of an Operator in the Downlink

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425880
Mean.PLMN
Average NodeB Credit

in the Downlink

484
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Mean.PLMN
WRFD-150214
MOCN Independent CE
Resource Allocation
Maximum NodeB Credit Consumption of an Operator in the Downlinke1

Counters
Counter ID
Counter Name
Counter Description
73425883
Max.PLMN
Maximum NodeB Credit

in the Downlink
Description
This counter measures the maximum NodeB credit consumption of an operator in the downlink.
Measurement point
the RNC obtains the maximum NodeB credit consumption of the operator in the downlink.
Issue 03 (2015-06-30)

485
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Max.PLMN
WRFD-150214
MOCN Independent CE
Resource Allocation
1.10 Measurement of RNC Performance(RNC)

Overview
The RNC performance measurement (RNC) is used to measure the overall performance of the
basic signaling procedures of the RNC. It includes only one measurement set, that is, RNC
performance measurement (RNC).
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
ALGO.RNC
Algorithm Measurement per RNC
AMR.RNC
AMR Service Measurement <per RNC>
CBS.RNC
CBS Measurement <per RNC>
ECO.RIM.RNC
RIM Message Through eCoordinator

Measurement per RNC <per RNC>
HHO.RNC
Hard Handover Measurement <per RNC>
IRATHO.Cs.RNC
CS Inter-RAT Handover Measurement <per

RNC>
IRATHO.PS.RNC
PS Inter-RAT Handover Measurement <per

RNC>
LCS.RNC
LCS Service Measurement <per RNC>
PAGE.RNC
Paging Measurement <per RNC>
PDCPGTPU.RNC
PDCP Measurement
RAB.EstabCS.RNC
CS RAB Setup Measurement <per RNC>

486
BSC6900 UMTS
FunctionSubSet
FunctionSubSet Name
RAB.EstabPS.RNC
PS RAB Setup Measurement <per RNC>
RAB.ModCs.RNC
CS RAB Modification Measurement <per

RNC>
RAB.ModPs.RNC
PS RAB Modification Measurement <per

RNC>
RAB.MultiRab.RNC
Multi-RAB Service Measurement <per

RNC>
RAB.RelAbnormal.RNC
RAB Release Measurement <per RNC>
RAB.RelCs.RNC
CS RAB Release Measurement <per RNC>
RAB.RelPs.RNC
PS RAB Release Measurement <per RNC>
RB.RNC
RB Procedure Measurement <per RNC>
Relocation.Drnc.RNC
TRNC Relocation Measurement
Relocation.Srnc.RNC
SRNC Relocation Measurement
RLC.RNC
RLC Measurement <per RNC>
RNC.IMS
IMS Measurement <per RNC>
RRC.Rel.RNC
RRC Connection Release Measurement <per

RNC>
RRC.Setup.RNC
RRC Connection Setup Measurement <per

RNC>
RRC.STATE
RRC Status Measurement <per RNC>
SHO.RNC
Soft Handover Measurement <per RNC>
SM.RNC
Security Mode Measurement <per RNC>
TRAFF.LOAD.RNC
Traffic Measurement <per RNC>
1.10.1 Algorithm Measurement per RNC(ALGO.RNC)

Overview
This function subset measures the counters related to the RNC-level radio resource management
algorithm, including the counters related to the Automatic NodeB and Cell Allocation in the
RNC feature.The BSC6900 dynamically allocates the NodeBs, Cells, NCPs, and CCPs based
on the CPU load of CP subsystems, Dynamic NodeB and Cell allocation can fully implement
load balancing on the CP.
Issue 03 (2015-06-30)

487
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425557
VS.AutoHoming.At
tCell
Number of Dynamic
Cell Redistribution
Attempts from One
Subsystem to
Another
BSC6900
V900R016C00
73425558
VS.AutoHoming.S
uccCell
Number of
Successful Dynamic
Cell Redistributions
from One Subsystem
to Another
BSC6900
V900R016C00
73425559
VS.AutoHoming.At
tIubcp
Number of Dynamic
NCP/CCP
Redistribution
Attempts from One
Subsystem to
Another
BSC6900
V900R016C00
73425560
VS.AutoHoming.S
uccIubcp
Number of
Successful Dynamic
NCP/CCP
Redistributions from
One Subsystem to
Another
BSC6900
V900R016C00
73425561
VS.AutoHoming.At
tNodeB
Number of Dynamic
NodeB
Redistribution
Attempts from One
Subsystem to
Another
BSC6900
V900R016C00
73425562
VS.AutoHoming.S
uccNodeB
Number of
Successful Dynamic
NodeB
Redistributions from
One Subsystem to
Another
BSC6900
V900R016C00
73428524
VS.RAU.Req.CSF
B.Delay.RNC
Number of Times the

RNC Forwards the
RAU Requests from
CSFB UEs at a
Delayed Time
BSC6900
V900R016C00

488
BSC6900 UMTS
None
Number of Cell/NodeB/NCP/CCP Redistribution Attempts from One Subsystem

to Another
Counters
Counter ID
Counter Name
Counter Description
73425557
VS.AutoHoming.AttCell
Number of Dynamic Cell

Redistribution Attempts
from One Subsystem to
Another
73425559
VS.AutoHoming.AttIubcp
Number of Dynamic NCP/

CCP Redistribution
Attempts from One
Subsystem to Another
73425561
VS.AutoHoming.AttNodeB
Number of Dynamic NodeB

Redistribution Attempts
from One Subsystem to
Another
Description
The RNC automatically redistributes Cells, NodeBs, or IUBCPs in a highly loaded subsystem
to a low-loaded subsystem based on the CPU usage. The counters measure the number of
dynamic Cell/NodeB/IUBCP redistribution attempts between control plane (CP) subsystems at
the RNC level. Iub control ports (IUBCPs) include NodeB control ports (NCPs) and
communication control ports (CCPs).
Measurement point
The measurement is triggered and the corresponding counter is incremented by one when the
RNC sends a cell/NodeB/NCP/CCP redistribution request message to the operation and
maintenance unit (OMU).
Formula
None
Unit
None
Issue 03 (2015-06-30)

489
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AutoHoming.AttCell
WRFD-141103
Automatic NodeB and Cell

Allocation in the RNC
VS.AutoHoming.AttIubcp
WRFD-141103

VS.AutoHoming.AttNodeB
WRFD-141103

Number of Successful Dynamic Cell/NodeB/NCP/CCP Redistributions from One

Counters
Counter ID
Counter Name
Counter Description
73425558
VS.AutoHoming.SuccCell
Dynamic Cell
Redistributions from One
73425560
VS.AutoHoming.SuccIubcp
Dynamic NCP/CCP
73425562
VS.AutoHoming.SuccNodeB
Dynamic NodeB
Description
The RNC automatically redistributes Cells, NodeBs, or IUBCPs in a highly loaded subsystem
to a low-loaded subsystem based on the CPU usage. The counters measure the number of
successful dynamic Cell/NodeB/IUBCP redistribution between control plane (CP) subsystems
at the RNC level. Iub control ports (IUBCPs) include NodeB control ports (NCPs) and
communication control ports (CCPs).
Measurement point
The measurement is triggered and the corresponding counter is incremented by one when the
RNC receives from the OMU the redistribution response message indicating a successful
redistribution of a cell, NodeB, or NCP/CCP.
Issue 03 (2015-06-30)

490
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AutoHoming.SuccCell
WRFD-141103

VS.AutoHoming.SuccIubcp
WRFD-141103

VS.AutoHoming.SuccNodeB
WRFD-141103

Number of Times the RNC Forwards the RAU Requests from CSFB UEs at a
Delayed Time
Counters
Counter ID
Counter Name
Counter Description
73428524
VS.RAU.Req.CSFB.Delay.
RNC

Forwards the RAU Requests
from CSFB UEs at a Delayed
Time
Description
This counter measures the number of times the RNC forwards routing area update requests from
CSFB UEs to the CN at a delayed time.This counter complies with section "4.7.5 Routing area
updating procedure" in 3GPP TS 24.008 (v10.12.0).
Measurement point
When receiving a routing area update request from a UE in PS-handover-based CSFB, the RNC
waits until the CS RAB is set up and then forwards the routing area update request to the CN.
The measurement is triggered at point B in figure 1after the RNC forwards the routing area
update request to the CN.
Issue 03 (2015-06-30)

491
BSC6900 UMTS
Figure 1-206 Procedure for delayed routing area update for CSFB UEs
When receiving a routing area update request from a UE in redirection-based CSFB, the RNC
waits until the CS RAB is set up and then forwards the routing area update request to the CN.
The measurement is triggered at point B in figure 2 after the RNC forwards the routing area
update request to the CN.
Issue 03 (2015-06-30)

492
BSC6900 UMTS
When receiving a routing area update request from a UE in redirection-based CSFB, the RNC
forwards the routing area update request to the CN if Delayed Routing Area Update Timer for
CSFB UEs has expired but the CS RAB has not been set up. The measurement is triggered at
point B in figure 3 after the RNC forwards the routing area update request to the CN.
Issue 03 (2015-06-30)

493
BSC6900 UMTS
When receiving a routing area update request from a UE in PS-handover-based CSFB, the RNC
forwards the routing area update request to the CN if Delayed Routing Area Update Timer for
CSFB UEs has expired but the CS RAB has not been set up. The measurement is triggered at
point B in figure 4 after the RNC forwards the routing area update request to the CN.
Issue 03 (2015-06-30)

494
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAU.Req.CSFB.Delay.
RNC
WRFD-140224

RIM
WRFD-140102
CS Fallback Guarantee for

LTE Emergency Calls
Issue 03 (2015-06-30)

495
BSC6900 UMTS
1.10.2 AMR Service Measurement <per RNC>(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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202488
VS.RB.AMR.UL.
5.9.RNC
Average Number of
AMR Service Users
With UL Rate of 5.9
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202489
VS.RB.AMR.DL.
10.2.RNC
Average Number of
AMR Service Users
With DL Rate of 10.2
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202490
VS.RB.AMR.DL.
12.2.RNC
Average Number of
AMR Service Users
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202491
VS.RB.AMR.DL.
4.75.RNC
Average Number of
AMR Service Users
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202492
VS.RB.AMR.DL.
5.15.RNC
Average Number of
AMR Service Users
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202493
VS.RB.AMR.DL.
5.9.RNC
Average Number of
AMR Service Users
With DL Rate of 5.9
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202494
VS.RB.AMR.DL.
7.4.RNC
Average Number of
AMR Service Users
With DL Rate of 7.4
Kbit/s for RNC
Earlier than
BSC6900
V900R011

496
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202495
VS.RB.AMR.DL.
7.95.RNC
Average Number of
AMR Service Users
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202496
VS.RB.AMR.UL.
10.2.RNC
Average Number of
AMR Service Users
With UL Rate of 10.2
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202497
VS.RB.AMR.UL.
12.2.RNC
Average Number of
AMR Service Users
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202498
VS.RB.AMR.UL.
4.75.RNC
Average Number of
AMR Service Users
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202499
VS.RB.AMR.UL.
5.15.RNC
Average Number of
AMR Service Users
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202500
VS.RB.AMR.UL.
7.4.RNC
Average Number of
AMR Service Users
With UL Rate of 7.4
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202501
VS.RB.AMR.UL.
7.95.RNC
Average Number of
AMR Service Users
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202562
VS.RB.AMR.UL.
6.7.RNC
Average Number of
AMR Service Users
With UL Rate of 6.7
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202563
VS.RB.AMR.DL.
6.7.RNC
Average Number of
AMR Service Users
With DL Rate of 6.7
Kbit/s for RNC
Earlier than
BSC6900
V900R011
73422074
VS.AMR.DLSilent.
Num
Number of Times
That Silence Is
Detected in
Downlink for AMR
Calls per RNC
BSC6900
V900R012

497
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73422075
VS.AMR.ULSilent.
Num
Number of Times
That Silence Is
Detected in Uplink
for AMR Calls per
RNC
BSC6900
V900R012
None
The Average Number of AMR Users with Different UL and DL Rates

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
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

Service Users With UL Rate
67202489

67202490

67202492

67202493

67202494

67202495


498
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67202496

67202497

67202498

67202499

67202500

67202501

67202562

67202563

Description
These counters provide the average number of AMR users with different UL and DL rates in
the RNC.
Measurement point
The number of AMR users with each UL or DL rate is sampled every five seconds in the RNC.
At the end of the measurement period, the value of each counter is obtained as follows: dividing
the accumulated value of each sampling point by the number of sampling times.
Formula
None
Unit
None
Issue 03 (2015-06-30)

499
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
Number of Times That Silence Is Detected in Downlink for AMR Calls per RNC
Counters
Counter ID
Counter Name
Counter Description
73422074
VS.AMR.DLSilent.Num

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.
Issue 03 (2015-06-30)

500
BSC6900 UMTS
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 20% for three consecutive measurement periods (a
measurement period lasts two seconds), the RNC considers that silence is detected during the
call. Only one silence can be calculated for a call, regardless of the number of times that silence
is detected during the call.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AMR.DLSilent.Num
WRFD-010501
Number of Times That Silence Is Detected in Uplink for AMR Calls per RNC
Counters
Counter ID
Counter Name
Counter Description
73422075
VS.AMR.ULSilent.Num

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 20% 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.
Issue 03 (2015-06-30)

501
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AMR.ULSilent.Num
WRFD-010501
1.10.3 CBS Measurement <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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426311
VS.ETWS.WriteRe
place
Number of ETWSrelated WRITEREPLACE

Messages Received
by the RNC
BSC6900
V900R015C00
73426312
VS.ETWS.WriteRe
placeFail
Number of ETWSrelated WRITEREPLACE

FAILURE Messages
Sent by the RNC
BSC6900
V900R015C00
73430678
VS.CBS.WriteRepl
ace.RNC
Number of WRITEREPLACE
Messages Received
by an RNC from the
CBC
BSC6900
V900R017C10

502
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430679
VS.CBS.WriteRepl
aceFail.RNC
Number of WRITEREPLACE
FAILURE Messages
Sent to the CBC per
RNC
BSC6900
V900R017C10
Counter
Sub Counter
VS.CBS.WriteReplace.RNC
VS.ETWS.WriteReplace
VS.CBS.WriteReplaceFail.RNC
VS.ETWS.WriteReplaceFail
Number of ETWS-related WRITE-REPLACE Messages Received by the RNC

Counters
Counter ID
Counter Name
Counter Description
73426311
Number of ETWS-related
WRITE-REPLACE
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.This counter complies with section "8.2 WriteReplace" in 3GPP TS 25.419 (v11.1.0).
Measurement point
The measurement is triggered at point A as shown in the figure when the RNC receives a WRITEREPLACE message carrying the Paging ETWS Indicator information element, which indicates
that the CBC initiates an ETWS warning process. CBC is short for cell broadcast center.
Issue 03 (2015-06-30)

503
BSC6900 UMTS
Figure 1-210 Message interactions for a successful ETWS warning process
The measurement is triggered at point A as shown in the figure when the RNC receives a WRITEREPLACE message carrying the Paging ETWS Indicator information element, which indicates
that the CBC initiates an ETWS warning process.
Figure 1-211 Message interactions for a failed ETWS warning process
Issue 03 (2015-06-30)

504
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-150234
Earthquake and Tsunami

Warning System (ETWS)
Number of ETWS-related WRITE-REPLACE FAILURE Messages Sent by the RNC

Counters
Counter ID
Counter Name
Counter Description
73426312
WRITE-REPLACE
FAILURE Messages Sent by
the RNC
Description
This counter provides the number of WRITE-REPLACE FAILURE messages sent by the RNC
in response to the WRITE-REPLACE message that carry the Paging ETWS Indicator
information element.This counter complies with section "8.2.3 Unsuccessful Operation" in
3GPP TS 25.419 (v11.1.0).
Measurement point
The measurement is triggered at point B as shown in the figure when the RNC sends the CBC
a WRITE-REPLACE FAILURE message in response to the WRITE-REPLACE message
carrying the Paging ETWS Indicator information element. The WRITE-REPLACE FAILURE
message indicates a failed ETWS warning process.
Issue 03 (2015-06-30)

505
BSC6900 UMTS
Figure 1-212 Message interactions for a failed ETWS warning process
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-150234

Number of WRITE-REPLACE Messages Received by an RNC from the CBC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430678
Number of WRITEREPLACE Messages

Received by an RNC from
the CBC

506
BSC6900 UMTS
Description
This counter provides the number of WRITE-REPLACE messages received by an RNC from
the CBC. This counter complies with 3GPP TS 25.419 (V11.1.0). For details about this counter,
see section 8.2 "Write-Replace" in this TS.
Measurement point
The measurement is triggered at point A in figure. This counter is measured when the RNC
receives a WRITE-REPLACE message from the CBC.
Figure 1-213 Successful reception of a WRITE-REPLACE message
Formula
None
Unit
None
Issue 03 (2015-06-30)

507
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-150234

WRFD-011000
Cell Broadcast Service
Number of WRITE-REPLACE FAILURE Messages Sent to the CBC per RNC

Counters
Counter ID
Counter Name
Counter Description
73430679
VS.CBS.WriteReplaceFail.
RNC
Number of WRITEREPLACE FAILURE

Messages Sent to the CBC
per RNC
Description
This counter provides the number of WRITE-REPLACE FAILURE messages sent by an RNC
to the CBC. This counter complies with 3GPP TS 25.419 (V11.1.0). For details about this
counter, see section 8.2 "Write-Replace" in this TS.
Measurement point
The measurement is triggered at point A in figure. This counter is measured when the RNC sends
a WRITE-REPLACE FAILURE message to the CBC.
Figure 1-214 Transmission of a WRITE-REPLACE FAILURE message
Issue 03 (2015-06-30)

508
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CBS.WriteReplaceFail.
RNC
WRFD-150234

WRFD-011000
1.10.4 RIM Message Through eCoordinator Measurement per RNC

<per RNC>(ECO.RIM.RNC)
Overview
The WCDMA system can exchange RIM messages with the LTE and GSM systems through
the CN or eCoordinator. The RIM procedure is controlled by the RIM_ON_ECO_SWITCH
(eCoordinator Supporting RIM Procedure) in the SET URRCTRLSWITCH command. When
this switch is set to on, the WCDMA system exchanges RIM messages with the LTE and GSM
systems through the eCoordinator. This function subset measures counters related to RIM
messages transmitted through the eCoordinator.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428748
VS.ECO.RIM.U2L.
Load.Req
Number of RIM
Requests from the
RNC to the eNodeB
through the
eCoordinator (Load
Information)
BSC6900
V900R016C00
73428749
VS.ECO.RIM.U2L.
Load.Resp
Number of RIM
response from the
eNodeB to the RNC
through the
eCoordinator (Load
Information)
BSC6900
V900R016C00

509
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428750
VS.ECO.RIM.U2L.
Load.Update
Number of RIM
Update Messages
from the eNodeB to
the RNC through the
eCoordinator (Load
Information)
BSC6900
V900R016C00
73428751
VS.ECO.RIM.L2U.
SI.Req
Number of RIM
Requests from the
eNodeB to the RNC
through the
eCoordinator
(System
Information)
BSC6900
V900R016C00
73428752
VS.ECO.RIM.L2U.
SI.Resp
Number of RIM
Response Messages
from the RNC to the
eNodeB through the
eCoordinator
(System
Information)
BSC6900
V900R016C00
73428753
VS.ECO.RIM.L2U.
SI.Update
Number of RIM
Update Messages
from the RNC to the
eNodeB through the
eCoordinator
(System
Information)
BSC6900
V900R016C00
73428754
VS.ECO.RIM.L2U.
SI.Update.ACK
Number of RIM
acknowledgement
messages from the
eNodeB to the RNC
through the
eCoordinator
(System
Information)
BSC6900
V900R016C00
73428755
VS.ECO.RIM.L2U.
Load.Req
Number of RIM
Requests from the
eNodeB to the RNC
through the
eCoordinator(Load
Information)
BSC6900
V900R016C00

510
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428756
VS.ECO.RIM.L2U.
Load.Resp
Number of RIM
Response Messages
from the RNC to the
eNodeB through the
eCoordinator (Load
Information)
BSC6900
V900R016C00
73428757
VS.ECO.RIM.L2U.
Load.Update
Number of RIM
Update Messages
from the RNC to the
eNodeB through the
eCoordinator(Load
Information)
BSC6900
V900R016C00
73428758
VS.ECO.RIM.L2U.
Load.Update.ACK
Number of RIM
Acknowledgement
Messages from the
eNodeB to the RNC
through the
eCoordinator(Load
Information)
BSC6900
V900R016C00
73430228
VS.ECO.RIM.L2U.
SI.Fail
Number of Times the

RNC Fail to Process
the RIM Requests
from the eNodeB
Through the
eCoordinator
(System
Information)
BSC6900
V900R017C10
73430229
VS.ECO.RIM.L2U.
Load.Fail
Number of Times the

RNC Fail to Process
the RIM Requests
from the eNodeB
Through the
eCoordinator (Load
Information)
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

511
BSC6900 UMTS
Number of RIM Requests from the RNC to the eNodeB through the eCoordinator
(Load Information)
Counters
Counter ID
Counter Name
Counter Description
73428748
VS.ECO.RIM.U2L.Load.Re
q

from the RNC to the eNodeB
through the eCoordinator
(Load Information)
Description
This counter provides the number of RIM messages requesting LTE cell load information sent
from the RNC to the eNodeB through the eCoordinator.
Measurement point
one when the RNC sends to the eNodeB a RAN-INFORMATION-REQUEST/Single Report
message through the eCoordinator to request LTE cell load information.
Issue 03 (2015-06-30)

512
BSC6900 UMTS

one when the RNC sends to the eNodeB a RAN-INFORMATION-REQUEST/Multiple Report
message through the eCoordinator to request LTE cell load information.
Figure 1-216 RIM message procedure(multiple mode)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
q
MRFD-090211
eCoordinator based RIM

process optimization

513
BSC6900 UMTS
Number of RIM response from the eNodeB to the RNC through the eCoordinator
(Load Information)
Counters
Counter ID
Counter Name
Counter Description
73428749
sp
Number of RIM response

(Load Information)
Description
This counter provides the number of RIM response message with LTE cell load information sent
from the eNodeB to the RNC through the eCoordinator.
Measurement point
one when the RNC receives a RAN-INFORMATION/Single Report message including LTE
cell load information from the eNodeB through the eCoordinator.
Issue 03 (2015-06-30)

514
BSC6900 UMTS

one when the RNC receives a RAN-INFORMATION/Multiple Report-Initial message including
LTE cell load information from the eNodeB through the eCoordinator.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
sp
MRFD-090211


515
BSC6900 UMTS
Number of RIM Update Messages from the eNodeB to the RNC through the
eCoordinator (Load Information)
Counters
Counter ID
Counter Name
Counter Description
73428750
VS.ECO.RIM.U2L.Load.Up
date

to the RNC through the
eCoordinator (Load
Information)
Description
This counter provides the number of RIM update messages with load information sent from the
eNodeB to the RNC through the eCoordinator.
Measurement point
one when the RNC receives a RAN-INFORMATION(excluding Multiple Report-Initial
message) that contains LTE cell load updating information from the eNodeB through the
eCoordinator.
Issue 03 (2015-06-30)

516
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ECO.RIM.U2L.Load.Up
date
MRFD-090211

Number of RIM Requests from the eNodeB to the RNC through the eCoordinator
Counters
Counter ID
Counter Name
Counter Description
73428751
VS.ECO.RIM.L2U.SI.Req

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
one when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report message with system information from the
eNodeB through the eCoordinator.
Issue 03 (2015-06-30)

517
BSC6900 UMTS
Figure 1-220 RIM message procedure (single mode)

one when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report message with system information from the
eNodeB through the eCoordinator.
Figure 1-221 RIM message procedure (multiple mode)
Issue 03 (2015-06-30)

518
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ECO.RIM.L2U.SI.Req
WRFD-140224

RIM
MRFD-090211

Number of RIM Response Messages from the RNC to the eNodeB through the
eCoordinator(System Information)
Counters
Counter ID
Counter Name
Counter Description
73428752
VS.ECO.RIM.L2U.SI.Resp

the eNodeB through the
eCoordinator(System
Information)
Description
This counter provides the number of RIM response messages with system information the RNC
sends to the eNodeB through the eCoordinator. The RIM response messages include RANINFORMATION/Single Report and RAN-INFORMATION/Multiple Report-Initial.
Measurement point
one when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RANINFORMATION/Multiple Report-Initial message with system information through the
eCoordinator.
Issue 03 (2015-06-30)

519
BSC6900 UMTS

one when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RANINFORMATION/Multiple Report-Initial message with system information through the
eCoordinator.
Issue 03 (2015-06-30)

520
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ECO.RIM.L2U.SI.Resp
WRFD-140224

RIM
MRFD-090211

Number of RIM Update Messages from the RNC to the eNodeB through the
eCoordinator(System Information)
Counters
Counter ID
Counter Name
Counter Description
73428753
VS.ECO.RIM.L2U.SI.Update

eCoordinator(System
Information)
Description
This counter provides the number of RIM update messages with system information the RNC
sends to the eNodeB through the eCoordinator. The RAN-INFORMATION/Multiple ReportInitial message is excluded.
Measurement point
one when the RNC sends to the eNodeB the RAN-INFORMATION/Multiple Report message
with system information through the eCoordinator.
Issue 03 (2015-06-30)

521
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ECO.RIM.L2U.SI.Update
WRFD-140224

RIM
MRFD-090211

Issue 03 (2015-06-30)

522
BSC6900 UMTS
Number of RIM acknowledgement messages from the eNodeB to the RNC through
the eCoordinator (System Information)
Counters
Counter ID
Counter Name
Counter Description
73428754
VS.ECO.RIM.L2U.SI.Upda
te.ACK
Number of RIM
acknowledgement messages
Description
This counter provides the number of RIM acknowledgement messages with system information
the RNC receives from the eNodeB through the eCoordinator.
Measurement point
one when the RNC receives the RAN-INFORMATION-ACK message with system information
from the eNodeB through the eCoordinator.
Issue 03 (2015-06-30)

523
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ECO.RIM.L2U.SI.Upda
te.ACK
WRFD-140224

RIM
MRFD-090211

Number of RIM Requests from the eNodeB to the RNC through the eCoordinator
(Load Information)
Counters
Counter ID
Counter Name
Counter Description
73428755
VS.ECO.RIM.L2U.Load.Re
q

(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
one when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report message with load information from the eNodeB
through the eCoordinator.
Issue 03 (2015-06-30)

524
BSC6900 UMTS

one when the RNC receives the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report message with load information from the eNodeB
through the eCoordinator.
Issue 03 (2015-06-30)

525
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
q
WRFD-150231

MRFD-090211

Number of RIM Response Messages from the RNC to the eNodeB through the
eCoordinator (Load Information)
Counters
Counter ID
Counter Name
Counter Description
73428756
sp

eCoordinator (Load
Information)
Description
This counter provides the number of RIM response messages with load information the RNC
sends to the eNodeB through the eCoordinator. The RIM response messages include RANINFORMATION/Single Report and RAN-INFORMATION/Multiple Report-Initial.
Measurement point
one when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RANINFORMATION/Multiple Report-Initial message with load information through the
eCoordinator.
Issue 03 (2015-06-30)

526
BSC6900 UMTS

one when the RNC sends to the eNodeB the RAN-INFORMATION/Single Report or RANINFORMATION/Multiple Report-Initial message with load information through the
eCoordinator.
Issue 03 (2015-06-30)

527
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
sp
WRFD-150231

MRFD-090211

Number of RIM Update Messages from the RNC to the eNodeB through the
eCoordinator(Load Information)
Counters
Counter ID
Counter Name
Counter Description
73428757
VS.ECO.RIM.L2U.Load.Up
date

eCoordinator(Load
Information)
Description
This counter provides the number of RIM update messages with load information the RNC sends
to the eNodeB through the eCoordinator. The RAN-INFORMATION/Multiple Report-Initial
message is excluded.
Measurement point
one when the RNC sends to the eNodeB the RAN-INFORMATION/Multiple Report message
with load information through the eCoordinator.
Issue 03 (2015-06-30)

528
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
date
WRFD-150231

MRFD-090211

Issue 03 (2015-06-30)

529
BSC6900 UMTS
Number of RIM Acknowledgement Messages from the eNodeB to the RNC

through the eCoordinator(Load Information)
Counters
Counter ID
Counter Name
Counter Description
73428758
date.ACK
Number of RIM
Acknowledgement
to the RNC through the
eCoordinator(Load
Information)
Description
This counter provides the number of RIM acknowledgement messages with load information
the RNC receives from the eNodeB through the eCoordinator.
Measurement point
one when the RNC receives the RAN-INFORMATION-ACK message with load information
from the eNodeB through the eCoordinator.
Issue 03 (2015-06-30)

530
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
date.ACK
WRFD-150231

MRFD-090211

Through the eCoordinator (System Information)
Counters
Counter ID
Counter Name
Counter Description
73430228
VS.ECO.RIM.L2U.SI.Fail

Through the eCoordinator
Description
by the LTE side through the eCoordinator for UMTS system information. This counter complies
with 3GPP TS 48.018 (V10.10.0). For details about this counter, see section 8c.2 "RIM
procedures" in this TS.
Measurement point
When the RNC fails to process the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report that requests UMTS system information and is
received from the LTE side through the eCoordinator, this counter is increased by one.This
counter is measured at point A.
Issue 03 (2015-06-30)

531
BSC6900 UMTS
Figure 1-232 RNC failing to processing the RIM request message received from the LTE side
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ECO.RIM.L2U.SI.Fail
WRFD-140224

RIM
WRFD-150231

Issue 03 (2015-06-30)

532
BSC6900 UMTS
Through the eCoordinator (Load Information)
Counters
Counter ID
Counter Name
Counter Description
73430229
VS.ECO.RIM.L2U.Load.Fa
il

Through the eCoordinator
(Load Information)
Description
by the LTE side through the eCoordinator for UMTS load information. This counter complies
with 3GPP TS 48.018 (V10.10.0). For details about this counter, see section 8c.2 "RIM
Measurement point
When the RNC fails to process the RAN-INFORMATION-REQUEST/Single Report or RANINFORMATION-REQUEST/Multiple Report that requests load information and is received
from the LTE side through the eCoordinator, this counter is increased by one.This counter is
measured at point A.
Figure 1-233 RNC failing to processing the RIM request message received from the LTE side
Issue 03 (2015-06-30)

533
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ECO.RIM.L2U.Load.Fa
il
WRFD-140224

RIM
WRFD-150231

1.10.5 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
Issue 03 (2015-06-30)

534
BSC6900 UMTS
RECONFIGURATION FAILURE message, RADIO BEARER RECONFIGURATION

FAILURE message, RADIO BEARER SETUP FAILURE message, or RADIO BEARER
RELEASE FAILURE message in the source cell before the hard handover or the RNC does not
receive the response message from the UE before the timer expires, the hard handover fails.
Hard Handover Measurement per RNC measures the number of intra-frequency and interfrequency hard handovers separately at the RNC level. Hard handovers with relocation are not
measured.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67192284
VS.HHO.AttIntraF
req.RNC
Number of IntraFrequency Hard

Handover Requests
for RNC
Earlier than
BSC6900
V900R011
67175428
VS.HHO.AttInterF
req.RNC
Number of InterFrequency Hard

Handover Requests
for RNC
Earlier than
BSC6900
V900R011
67175429
VS.HHO.SuccInter
Freq.RNC
Number of
Successful InterFrequency Hard
Handovers for RNC
Earlier than
BSC6900
V900R011
67192285
VS.HHO.SuccIntra
Freq.RNC
Number of
Successful IntraFrequency Hard
Handovers for RNC
Earlier than
BSC6900
V900R011
None
Number of Intra-Frequency Hard Handover Requests

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192284
VS.HHO.AttIntraFreq.RNC
Number of Intra-Frequency
Hard Handover Requests for
RNC

535
BSC6900 UMTS
Description
This counter provides the number of intra-frequency hard handover requests initiated by the
RNC.This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered in point B as shown in the following figure, taking the PHYSICAL
CHANNEL RECONFIGURATION message as an example. When initiating the intrafrequency hard handover, the RNC establishes RL and then sends the RADIO LINK SETUP
REQUEST message to the NodeB. After the RNC receives the RADIO LINK SETUP
RESPONSE message indicating a successful RL establishment, the RNC sends the PHYSICAL
CHANNEL RECONFIGURATION message to the UE. In this case, the RNC measures the
counter.
Figure 1-234 Successful hard handover procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

536
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.AttIntraFreq.RNC
WRFD-020301
Intra Frequency Hard

Handover
Number of Inter-Frequency Hard Handover Requests

Counters
Counter ID
Counter Name
Counter Description
67175428
VS.HHO.AttInterFreq.RNC
Number of Inter-Frequency
Hard Handover Requests for
RNC
Description
This counter provides the number of inter-frequency hard handover requests initiated by the
(v10.13.0).
Measurement point
The measurement is triggered in point B as shown in the following figure, taking the PHYSICAL
CHANNEL RECONFIGURATION message as an example. When initiating the interfrequency hard handover, the RNC establishes RL and then sends the RADIO LINK SETUP
REQUEST message to the NodeB. After the RNC receives the RADIO LINK SETUP
RESPONSE message indicating a successful RL establishment, the RNC sends the PHYSICAL
CHANNEL RECONFIGURATION message to the UE. In this case, the RNC measures the
counter.
Issue 03 (2015-06-30)

537
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.AttInterFreq.RNC
WRFD-020302
Inter Frequency Hard

Handover Based on
Coverage
WRFD-020304

Handover Based on DL QoS
Issue 03 (2015-06-30)

538
BSC6900 UMTS
Number of Successful Inter-Frequency Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67175429
VS.HHO.SuccInterFreq.RN
C
Number of Successful InterFrequency Hard Handovers

for RNC
Description
This counter provides the number of successful inter-frequency hard handovers initiated by the
(v10.13.0).
Measurement point
The measurement is triggered at point C as shown in the following figure, taking the PHYSICAL
CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard
handover, when the RNC receives the PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from the UE, the inter-frequency hard handover succeeds. In this case,
the RNC measures the counter.
Issue 03 (2015-06-30)

539
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.SuccInterFreq.RN
C
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Successful Intra-Frequency Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67192285
VS.HHO.SuccIntraFreq.RN
C
Number of Successful IntraFrequency Hard Handovers

for RNC
Description
This counter provides the number of successful intra-frequency hard handovers initiated by the
(v10.13.0).
Measurement point
CHANNEL RECONFIGURATION message as an example. During the intra-frequency hard
COMPLETE message from the UE, the intra-frequency hard handover succeeds. In this case,
the RNC measures the counter.
Issue 03 (2015-06-30)

540
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HHO.SuccIntraFreq.RN
C
WRFD-020301

Handover

541
BSC6900 UMTS
1.10.6 CS Inter-RAT Handover Measurement <per RNC>

(IRATHO.Cs.RNC)
Overview
This function subset measures the CS inter-RAT handover between WCDMA and GSM at the
RNC level. The CS inter-RAT handover is classified into CS outgoing inter-RAT handover and
CS incoming inter-RAT handover.
The measurement of CS outgoing inter-RAT handover measures the handover from WCDMA
to GSM at the RNC level. CS outgoing inter-RAT handover can be divided into two phases: the
handover preparation phase and the handover execution phase. The handover preparation phase
starts from the time when the RNC makes the decision of CS outgoing inter-RAT handover and
sends a RELOCATION REQUIRED message to the CN, to the time when the RNC receives a
RELOCATION COMMAND message from the CN. If the handover preparation phase is
completed successfully, the outgoing inter-RAT handover execution phase is initiated when the
RNC sends a HANDOVER FROM UTRAN COMMAND message to the UE. The outgoing
inter-RAT handover execution phase lasts until the RNC receives an IU RELEASE COMMAND
message from the CN.
The measurement of CS incoming inter-RAT handover measures the handover from GSM to
WCDMA at the RNC level. CS incoming inter-RAT handover can be divided into two phases:
the handover preparation phase and the handover execution phase. The handover preparation
phase starts from the time when the RNC allocates resources for the UE after receiving a
RELOCATION REQUEST message, to the time when the RNC sends a RELOCATION
REQUEST ACKNOWLEDGE message to the CN. After the handover preparation phase ends,
the handover execution phase starts. If the handover from GSM to WCDMA is completed
successfully, the UE sends a HANDOVER TO UTRAN COMPLETE message to the RNC.
Then the RNC sends a RELOCATION COMPLETE message to the CN, and the handover
execution phase is completed successfully.
Issue 03 (2015-06-30)

542
BSC6900 UMTS
Figure 1-238 Flow chart of CS outgoing inter-RAT handover
Table 1 describes the measurement points shown in Figure1.
Issue 03 (2015-06-30)
Measurement points
Description
VS.IRATHO.AttRelocPrepOutCS.RNC
543
BSC6900 UMTS
Measurement points
Description
VS.IRATHO.SuccRelocPrepOutCS.RNC
VS.IRATHO.AttOutCS.RNC
VS.IRATHO.SuccOutCS.RNC
Figure 1-239 Flow chart of CS incoming inter-RAT
Issue 03 (2015-06-30)

544
BSC6900 UMTS

Measurement points
Description
VS.IRATHO.AttRelocPrepInCS.RNC
VS.IRATHO.SuccRelocPrepInCS.RNC
VS.IRATHO.AttInCS.RNC
VS.IRATHO.SuccInCS.RNC
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67176008
VS.IRATHO.AttIn
CS.RNC
Number of CS
Incoming Inter-RAT
Handover Attempts
for RNC
Earlier than
BSC6900
V900R011
67175945
VS.IRATHO.AttO
utCS.RNC
Number of CS
Outgoing Inter-RAT
Handover Attempts
for RNC
Earlier than
BSC6900
V900R011
67190398
VS.IRATHO.AttRe
locPrepOutCS.RN
C
Number of CS
Outgoing Inter-RAT
Handover
Preparation
Attempts for RNC
Earlier than
BSC6900
V900R011
67190311
VS.IRATHO.AttRe
locPrepInCS.RNC
Number of CS
Incoming Inter-RAT
Handover
Preparation
Attempts for RNC
Earlier than
BSC6900
V900R011
67190312
VS.IRATHO.Succ
RelocPrepInCS.RN
C
Number of
Successful
Preparations for CS
Incoming Inter-RAT
Handover for RNC
Earlier than
BSC6900
V900R011
67190399
VS.IRATHO.Succ
OutCS.RNC
Number of
Successful CS
Outgoing Inter-RAT
Handovers for RNC
Earlier than
BSC6900
V900R011

545
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67190400
VS.IRATHO.Succ
RelocPrepOutCS.R
NC
Number of
Successful
Preparations for CS
Outgoing Inter-RAT
Handover for RNC
Earlier than
BSC6900
V900R011
67190314
VS.IRATHO.SuccI
nCS.RNC
Number of
Successful CS
Incoming Inter-RAT
Handovers for RNC
Earlier than
BSC6900
V900R011
None
Number of CS Outgoing Inter-RAT Handover Preparation Attempts

Counters
Counter ID
Counter Name
Counter Description
67190398
VS.IRATHO.AttRelocPrep
OutCS.RNC
Number of CS Outgoing
Inter-RAT Handover
RNC
Description
This counter provides the number of CS outgoing inter-RAT handover preparation attempts in
the RNC.This counter complies with section "8.6 Relocation Preparation" in 3GPP TS 25.413
(v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a
RELOCATION REQUIRED message to the CN during the CS outgoing inter-RAT handover.
Issue 03 (2015-06-30)

546
BSC6900 UMTS
Figure 1-240 Normal CS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OutCS.RNC
WRFD-020303
Inter-RAT Handover Based

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

547
BSC6900 UMTS
Number of Successful Preparations for CS Outgoing Inter-RAT Handover

Counters
Counter ID
Counter Name
Counter Description
67190400
VS.IRATHO.SuccRelocPre
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.This counter complies with section "8.6 Relocation Preparation" in 3GPP
TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC receives a
RELOCATION COMMAND message from the CN during the CS outgoing inter-RAT
handover.
Issue 03 (2015-06-30)

548
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
pOutCS.RNC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of CS Outgoing Inter-RAT Handover Attempts

Counters
Counter ID
Counter Name
Counter Description
67175945
VS.IRATHO.AttOutCS.RN
C
Inter-RAT Handover
Attempts for RNC
Description
This counter provides the number of CS outgoing inter-RAT handover attempts in the RNC.This
counter complies with section "8.3.7 Inter-RAT handover from UTRAN" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends a
HANDOVER FROM UTRAN COMMAND message to the UE during the CS outgoing interRAT handover.
Issue 03 (2015-06-30)

549
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttOutCS.RN
C
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

550
BSC6900 UMTS
Number of Successful CS Outgoing Inter-RAT Handovers

Counters
Counter ID
Counter Name
Counter Description
67190399
VS.IRATHO.SuccOutCS.R
NC
Outgoing Inter-RAT
Handovers for RNC
Description
This counter provides the number of successful CS outgoing inter-RAT handovers in the
RNC.This counter complies with section "8.3.7 Inter-RAT handover from UTRAN" in 3GPP
TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

551
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
NC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of CS Incoming Inter-RAT Handover Preparation Attempts

Counters
Counter ID
Counter Name
Counter Description
67190311
nCS.RNC
Number of CS Incoming
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.
Issue 03 (2015-06-30)

552
BSC6900 UMTS
Figure 1-244 Normal incoming inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
nCS.RNC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

553
BSC6900 UMTS
Number of Successful Preparations for CS Incoming Inter-RAT Handover

Counters
Counter ID
Counter Name
Counter Description
67190312
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.This counter complies with section "8.7 Relocation Resource Allocation"
in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends a
RELOCATION REQUEST ACKNOWLEDGE message to the CN during the CS incoming
inter-RAT handover.
Issue 03 (2015-06-30)

554
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
pInCS.RNC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of CS Incoming Inter-RAT Handover Attempts

Counters
Counter ID
Counter Name
Counter Description
67176008
Inter-RAT Handover
Attempts for RNC
Description
This counter provides the number of CS incoming inter-RAT handover attempts in the RNC.This
counter complies with section "8.3.6 Inter-RAT handover to UTRAN" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives a
HANDOVER TO UTRAN COMPLETE message from the UE, or when the RNC receives a
RADIO LINK RESTORE INDICATION message from the Node B after sending a
RELOCATION REQUEST ACKNOWLEDGE message to the CN and finishing the preparation
for CS inter-RAT handover during the CS incoming inter-RAT handover. Only one of the two
messages triggers the measurement. There is no repeated measurement.
Issue 03 (2015-06-30)

555
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

556
BSC6900 UMTS
Number of Successful CS Incoming Inter-RAT Handovers

Counters
Counter ID
Counter Name
Counter Description
67190314
VS.IRATHO.SuccInCS.RN
C
Incoming Inter-RAT
Handovers for RNC
Description
This counter provides the number of successful CS incoming inter-RAT handovers in the
RNC.This counter complies with section "8.3.6 Inter-RAT handover to UTRAN" in 3GPP TS
25.331 (v10.13.0).
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
Issue 03 (2015-06-30)

557
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccInCS.RN
C
WRFD-020303

on Coverage
WRFD-020305

on Service
WRFD-020306

on Load
1.10.7 PS Inter-RAT Handover Measurement <per RNC>

(IRATHO.PS.RNC)
Overview
The measurement of PS inter-RAT handover measures the inter-RAT handover between
WCDMA and another RAT from the perspective of the RNC. According to different initiators,
PS outgoing inter-RAT handovers can be classified into two types:
PS inter-RAT handovers initiated by UEs and PS inter-RAT handovers initiated by the RNC.
After a UE sets up PS services in WCDMA, if the UE is in the CELL_FACH, CELL_PCH, or
URA_PCH state and the UE initiates a cell reselection from WCDMA to another RAT, the
handover is called PS inter-RAT handover initiated by the UE. If the UE is in the CELL_DCH
state, and the RNC initiates a CELL CHANGE ORDER FROM UTRAN procedure from
WCDMA to another RAT, the handover is called PS inter-RAT handover initiated by the RNC.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67176098
VS.IRATHO.AttO
utPSUTRAN.RNC
Number of PS
Outgoing Inter-RAT
Handover Attempts
Initiated by RNC for
RNC
Earlier than
BSC6900
V900R011
67176100
VS.IRATHO.Succ
OutPSUTRAN.RN
C
Number of
Successful PS
Outgoing Inter-RAT
Handovers Initiated
by RNC for RNC
Earlier than
BSC6900
V900R011

558
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67190316
VS.IRATHO.AttO
utPSUE.RNC
Number of PS
Outgoing Inter-RAT
Handover Attempts
Initiated by UE for
RNC
Earlier than
BSC6900
V900R011
67176102
VS.IRATHO.Succ
OutPSUE.RNC
Number of
Successful PS
Outgoing Inter-RAT
Handovers Initiated
by UE for RNC
Earlier than
BSC6900
V900R011
73424356
VS.L2U.AttRelocP
repInPS.Emerg.RN
C
Number of LTE-toUMTS PS Handover

Attempts Caused by
the CSFB of an LTE
Emergency Call for
RNC
BSC6900
V900R014
73424357
VS.L2U.SuccReloc
InPS.Emerg.RNC
Number of
Successful LTE-toUMTS PS
Handovers Caused
by the CSFB of an
LTE Emergency Call
for RNC
BSC6900
V900R014
73426204
VS.L2U.SuccReloc
PrepInPS.Emerg.R
NC
Number of
Successful LTE-toUMTS PS Handover
Preparations Caused
by the CSFB of LTE
Emergency Calls for
RNC
BSC6900
V900R015C00
None
Issue 03 (2015-06-30)

559
BSC6900 UMTS
Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC

Counters
Counter ID
Counter Name
Counter Description
67176098
VS.IRATHO.AttOutPSUTR
AN.RNC
Number of PS Outgoing
Inter-RAT Handover
Attempts Initiated by RNC
for RNC
Description
This counter provides the number of attempts of PS outgoing inter-RAT handover initiated by
the RNC.This counter complies with section "8.3.11 Inter-RAT cell change order from UTRAN"
in 3GPP TS 25.331 (v10.13.0).
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-248 Successful PS outgoing inter-RAT handover initiated by the RNC
Issue 03 (2015-06-30)

560
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
AN.RNC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC

Counters
Counter ID
Counter Name
Counter Description
67176100
VS.IRATHO.SuccOutPSUT
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.This counter complies with section "8.3.11 Inter-RAT cell change order from UTRAN"
in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends the IU
RELEASE COMPLETE message after receiving the IU RELEASE COMMAND message with
the cause value of "Successful Relocation", "Normal Release", or "Network Optimization"
during the PS outgoing inter-RAT handover. In this case, the PS outgoing inter-RAT handover
succeeds and the counter is measured.
Issue 03 (2015-06-30)

561
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RAN.RNC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

562
BSC6900 UMTS
Number of PS Outgoing Inter-RAT Handover Attempts Initiated by UE

Counters
Counter ID
Counter Name
Counter Description
67190316
VS.IRATHO.AttOutPSUE.
RNC
Inter-RAT Handover
Attempts Initiated by UE for
RNC
Description
This counter provides the number of attempts of Cell Reselection in inter-RAT initiated by the
UE in the RNC.This counter complies with section "8.3.9 Inter-RAT cell reselection from
UTRAN" in 3GPP TS 25.331 (v10.13.0).
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 inter-RAT network according to the cell reselection criteria.
After entering the inter-RAT network through the reselection, the UE re-establishes PS services.
During the re-establishment process, through SRNS CONTEXT REQUEST, the 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-250 PS outgoing inter-RAT handover initiated by the UE
Issue 03 (2015-06-30)

563
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttOutPSUE.
RNC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE

Counters
Counter ID
Counter Name
Counter Description
67176102
VS.IRATHO.SuccOutPSUE
.RNC
Outgoing Inter-RAT
Handovers Initiated by UE
for RNC
Description
This counter provides the number of successful of Cell Reselection in inter-RAT initiated by
the UE in the RNC.This counter complies with section "8.3.9 Inter-RAT cell reselection from
UTRAN" in 3GPP TS 25.331 (v10.13.0).
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. If the SRNS CONTEXT REQUEST message
in the procedure does not carry the RAT type or carries a RAT type other than UTRAN,the PS
outgoing inter-RAT handover initiated by the UE succeeds and the counter is measured.
Issue 03 (2015-06-30)

564
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccOutPSUE
.RNC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

565
BSC6900 UMTS
Number of LTE-to-UMTS PS Handover Attempts Caused by the CSFB of an LTE

Emergency Call for RNC
Counters
Counter ID
Counter Name
Counter Description
73424356
VS.L2U.AttRelocPrepInPS.
Emerg.RNC
Number of LTE-to-UMTS
PS Handover Attempts
Caused by the CSFB of an
LTE Emergency Call for
RNC
Description
This counter measures the number of LTE-to-UMTS PS handover in preparation attempts caused
by the CS fallback (CSFB) of an LTE emergency call at the RNC level.This counter complies
with section "8.3.6 Inter-RAT handover to UTRAN" in 3GPP TS 25.331 (v10.13.0).
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-252 Emergency call signaling procedure on the LTE side
Issue 03 (2015-06-30)

566
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Emerg.RNC
WRFD-140102

LTE Emergency Calls
Number of Successful LTE-to-UMTS PS Handovers Caused by the CSFB of an LTE

Emergency Call for RNC
Counters
Counter ID
Counter Name
Counter Description
73424357
VS.L2U.SuccRelocInPS.Em
erg.RNC
Number of Successful LTEto-UMTS PS Handovers

Caused by the CSFB of an
LTE Emergency Call for
RNC
Description
This counter measures the number of successful LTE-to-UMTS PS handovers caused by the CS
fallback (CSFB) of an LTE emergency call at the RNC level.This counter complies with section
"8.3.6 Inter-RAT handover to UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point D shown in figure 1, when the RNC sends the CN a
RELOCATION COMPLETE message in which the corresponding UE information contains
CSFB High Priority. In this case, this counter is incremented by one in the RNC.
Issue 03 (2015-06-30)

567
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.L2U.SuccRelocInPS.Em
erg.RNC
WRFD-140102

LTE Emergency Calls

568
BSC6900 UMTS
Number of Successful LTE-to-UMTS PS Handover Preparations Caused by the

CSFB of LTE Emergency Calls for RNC
Counters
Counter ID
Counter Name
Counter Description
73426204
VS.L2U.SuccRelocPrepInP
S.Emerg.RNC
Number of Successful LTEto-UMTS PS Handover

Preparations Caused by the
CSFB of LTE Emergency
Calls for RNC
Description
This counter measures the number of successful preparations for LTE-to-UMTS PS handovers
caused by the CSFB of LTE emergency calls.This counter complies with section "8.7 Relocation
Resource Allocation" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

569
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
S.Emerg.RNC
WRFD-140102

LTE Emergency Calls
1.10.8 LCS Service Measurement <per RNC>(LCS.RNC)

Overview
When the RNC receives a LOCATION REPORTING CONTROL message from the CN, it
utilizes different positioning methods to determine the position of a UE according to the
combinations of various factors.
The UE positioning methods include:
CELLID method, OTDOA method, Assisted GPS (AGPS) method.
Hybrid positioning method, including AGPS, OTDOA and CELLID methods.
After determining the appropriate positioning method, the RNC shall send positioning
measurement request to the NodeB or UE to obtain the measurement results used for the UE
position calculation. These positioning measurements include:
UE-assisted CELLID measurements, UE-assisted OTDOA measurements, UE-assisted AGPS
measurements, UE-based AGPS measurements, RTT measurements.
When the RNC receives a LOCATION RELATED DATA REQUEST message from the CN,
it determines the location-related assistance data according to the requested data type and sends
the data in the ASSISTANCE DATA DELIVERY message to the UE. If the data transmission
is successful, the RNC indicates the successful delivery to the CN in the LOCATION RELATED
DATA RESPONSE message. If the data delivery fails, the RNC indicates failure to the CN in
the LOCATION RELATED DATA FAILURE message.
Location-related assistance data is mainly used for a UE to determine its own position. The types
of assistance data presently supported by the RNC include:
AGPS assistance data, OTDOA assistance data.
Issue 03 (2015-06-30)

570
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190216
VS.LCS.AsstGpsDataTransDel
Number of Times
that RNC
Successfully Sends
GPS Assistance Data
to CN
Earlier than
BSC6900
V900R011
67181025
VS.LCS.QoSAccur
Met
Number of Location
Reports with
Position Estimate
Satisfying the
Requested Accuracy
for RNC
Earlier than
BSC6900
V900R011
67176209
VS.LCS.Agps.Att
Number of the
positioning attempt
of the different
location method
(AGPS) for RNC
Earlier than
BSC6900
V900R011
67176211
VS.LCS.Otdoa.Att
Number of OTDOA
Based Positioning
Procedures for RNC
Earlier than
BSC6900
V900R011
67176214
VS.LCS.AttCsa
Number of Requests
for Positioning upon
Change of Service
Area for RNC
Earlier than
BSC6900
V900R011
67176213
VS.LCS.AttDir
Number of Direct
Positioning Requests
for RNC
Earlier than
BSC6900
V900R011
67176218
VS.LCS.SuccCsa
Number of
Successful Location
Report upon Change
of Service Area for
RNC
Earlier than
BSC6900
V900R011
67176217
VS.LCS.SuccDir
Number of
Successful Direct
Location Reports for
RNC
Earlier than
BSC6900
V900R011
73404075
VS.LCS.CellIdRtt.
Att
Number of the
positioning attempt
of the different
location method
(CELLID + RTT) for
RNC
BSC6900
V900R012

571
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73404076
VS.LCS.CellCenter
.Att
Number of the
positioning attempt
of the different
location method
(CELLID CENTER)
for RNC
BSC6900
V900R012
73404077
VS.LCS.CellCenter
.Succ
Number of the
successful
positioning of the
different location
method (CELL
CENTER) for RNC
BSC6900
V900R012
73404078
VS.LCS.CellIdRtt.
Succ
Number of the
successful
positioning of the
different location
method (CELLID +
RTT) for RNC
BSC6900
V900R012
73404079
VS.LCS.Otdoa.Suc
c
Number of the
successful
positioning of the
different location
method (OTDOA)
for RNC
BSC6900
V900R012
73404080
VS.LCS.Agps.Succ
Number of the
successful
positioning of the
different location
method (AGPS) for
RNC
BSC6900
V900R012
73394012
VS.LCS.SasMode.
Att
Number of the
positioning attempt
of using SAS centric
mode for RNC
BSC6900
V900R012
73394013
VS.LCS.SasMode.S
ucc
Number of the
successful
positioning of using
SAS centric mode for
RNC
BSC6900
V900R012
73423867
VS.LCS.Utdoa.Att
Number of U-TDOA
Positioning Attempts
for RNC
BSC6900
V900R013

572
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73423868
VS.LCS.Utdoa.Suc
c
Number of
Successful U-TDOA
Positionings for
RNC
BSC6900
V900R013
Counter
Sub Counter
VS.LCS.SasMode.Att
VS.LCS.Utdoa.Att
VS.LCS.SasMode.Succ
VS.LCS.Utdoa.Succ
Number of Successful Provisions of GPS Assistance Data

Counters
Counter ID
Counter Name
Counter Description
67190216
Number of Times that RNC

Successfully Sends GPS
Assistance Data to CN
Description
This measurement item takes statistics of the number of times that the RNC successfully provides
the Global Positioning System assistance data after receiving the LOCATION RELATED
DATA REQUEST message from the CN. This counter complies with section "10.3 GPS
assistance data" in 3GPP TS 25.305 (v12.0.0).
Measurement point
The measurement is triggered at point A as shown in figure. When the RNC receives from the
CN a LOCATION RELATED DATA REQUEST message in which the IE "Location Related
Data Request Type" is set to "Dedicated Assistance Data for Assisted GPS", the RNC measures
this item when it responds with a LOCATION RELATED DATA RESPONSE message to the
CN.
Issue 03 (2015-06-30)

573
BSC6900 UMTS
Figure 1-255 Location related data request procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020803
A-GPS Based LCS
Number of Positioning Reports Meeting Accuracy Requirement

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67181025
VS.LCS.QoSAccurMet
Number of Location Reports

with Position Estimate
Satisfying the Requested
Accuracy for RNC

574
BSC6900 UMTS
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. This counter complies
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-256 Location reporting procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

575
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.QoSAccurMet
WRFD-020801
WRFD-020802
Cell ID + RTT Function

Based LCS
WRFD-020803
OTDOA Based LCS

A-GPS Based LCS
Number of Positioning Requests with Different Event Types

Counters
Counter ID
Counter Name
Counter Description
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. The preceding counters comply with section "8.19 Location
Reporting Control" in 3GPP TS 25.413 (v12.1.0).
Counter Name
Description
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.
Issue 03 (2015-06-30)

576
BSC6900 UMTS
Figure 1-257 Location reporting control procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.AttDir
WRFD-020801
WRFD-020802

Based LCS
WRFD-020803
OTDOA Based LCS

A-GPS Based LCS
VS.LCS.AttCsa
WRFD-020801
WRFD-020802

Based LCS
WRFD-020803
OTDOA Based LCS

A-GPS Based LCS
Issue 03 (2015-06-30)

577
BSC6900 UMTS
Number of Successful Positioning Reports with Different Event Types

Counters
Counter ID
Counter Name
Counter Description
67176217
VS.LCS.SuccDir
Number of Successful Direct

Location Reports for RNC
67176218
VS.LCS.SuccCsa
Location Report upon
Change of Service Area for
RNC
Description
These measurement items take statistics of the number of successful positioning reports sent by
the RNC to the CN. These reports have different event types. The preceding counters comply
with section "8.19 Location Reporting Control" in 3GPP TS 25.413 (v12.1.0).
Counter Name
Description
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.
Issue 03 (2015-06-30)

578
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.SuccDir
WRFD-020801
WRFD-020802

Based LCS
WRFD-020803
OTDOA Based LCS

A-GPS Based LCS
VS.LCS.SuccCsa
WRFD-020801
WRFD-020802

Based LCS
WRFD-020803
OTDOA Based LCS

A-GPS Based LCS
Issue 03 (2015-06-30)

579
BSC6900 UMTS
Number of the positioning attempt of the different location method for RNC
Counters
Counter ID
Counter Name
Counter Description
73404076
VS.LCS.CellCenter.Att
Number of the positioning

attempt of the different
location method (CELLID
CENTER) for RNC
67176209
VS.LCS.Agps.Att

location method (AGPS) for
RNC
67176211
VS.LCS.Otdoa.Att
Number of OTDOA Based

Positioning Procedures for
RNC
73404075
VS.LCS.CellIdRtt.Att

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. The preceding counters comply with section "4.3 Standard UE
Positioning Methods" in 3GPP TS 25.305 (v12.0.0).
Counter Name
Description
VS.LCS.Agps.Att
AGPS
VS.LCS.Otdoa.Att
OTDOA
Measurement point
LOCATION REPORTING CONTROL message from the CN and determines a positioning
method.
Issue 03 (2015-06-30)

580
BSC6900 UMTS
Figure 1-259 Location reporting control procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.CellCenter.Att
WRFD-020801

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

Based LCS
WRFD-020807
Iupc Interface for LCS

service
Issue 03 (2015-06-30)

581
BSC6900 UMTS
Number of the successful positioning of the different location method for RNC
Counters
Counter ID
Counter Name
Counter Description
73404077
VS.LCS.CellCenter.Succ
Number of the successful

positioning of the different
location method (CELL
CENTER) for RNC
73404078
VS.LCS.CellIdRtt.Succ

location method (CELLID +
RTT) for RNC
73404079
VS.LCS.Otdoa.Succ

location method (OTDOA)
for RNC
73404080
VS.LCS.Agps.Succ

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. The preceding counters comply with section "4.3 Standard UE
Positioning Methods" in 3GPP TS 25.305 (v12.0.0).
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.
Issue 03 (2015-06-30)

582
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.CellCenter.Succ
WRFD-020801

Based LCS
VS.LCS.CellIdRtt.Succ
WRFD-020801

Based LCS
WRFD-020807

service
Issue 03 (2015-06-30)
VS.LCS.Otdoa.Succ
WRFD-020802
OTDOA Based LCS
VS.LCS.Agps.Succ
WRFD-020803
A-GPS Based LCS
WRFD-020807

service

583
BSC6900 UMTS
Number of the times that the location in SAS centric mode is used in the RNC
Counters
Counter ID
Counter Name
Counter Description
73394012
VS.LCS.SasMode.Att

attempt of using SAS centric
mode for RNC
73394013
VS.LCS.SasMode.Succ

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. The preceding counters comply with section "5.2 Functional Description of UTRAN UE
Positioning related elements" in 3GPP TS 25.305 (v12.0.0).
Measurement point
SAS is an abbreviation for Stand-Alone SMLC. It provides auxiliary data for location and
performs related calculation. The interface between the RNC and the SAS is the Iu-PS interface.
This counter helps assessing the success rate of SAS centric location on the Iu-PC interface. The
measurement of VS.LCS.SasMode.Att is triggered at point A as shown in the figure, when the
RNC sends the SAS an IUPC POSITION INITIATION REQUEST message. The measurement
of VS.LCS.SasMode.Succ is triggered at point B, when the RNC receives from the SAS a
POSITION INITIATION RESPONSE message that contains the location result.
Figure 1-261 SAS location procedure
Issue 03 (2015-06-30)

584
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.SasMode.Att
WRFD-020807

service
VS.LCS.SasMode.Succ
WRFD-020807

service
Number of U-TDOA Positioning Attempts

Counters
Counter ID
Counter Name
Counter Description
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. This counter complies with section "4.3 Standard UE Positioning
Methods" in 3GPP TS 25.305 (v12.0.0).
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.
Issue 03 (2015-06-30)

585
BSC6900 UMTS
Figure 1-262 U-TDOA positioning procedure in SAS centric mode
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.Utdoa.Att
WRFD-020802
OTDOA Based LCS
Number of Successful U-TDOA Positionings

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423868
VS.LCS.Utdoa.Succ
Number of Successful UTDOA Positionings for RNC

586
BSC6900 UMTS
Description
This counter provides the number of successful U-TDOA positionings under an RNC. This
counter complies with section "4.3 Standard UE Positioning Methods" in 3GPP TS 25.305
(v12.0.0).
Measurement point
In SAS centric mode, the measurement is triggered at point D as shown in the figure. This counter
is incremented by one when the RNC receives a PCAP POSITION INITIATION RESPONSE
message and the following conditions are both met:
1. The RNC receives a PCAP POSITION ACTIVATION REQUEST message that designates
the U-TDOA positioning method from the SAS at a point of time between point A when a PCAP
POSITION INITIATION REQUEST message is received and point D when a PCAP POSITION
INITIATION RESPONSE message is received.
2. At point C, the RNC sends the SAS a PCAP POSITION ACTIVATION RESPONSE message
that contains UE's U-TDOA positioning information.
Figure 1-263 U-TDOA positioning procedure in SAS centric mode
Formula
None
Unit
None
Issue 03 (2015-06-30)

587
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.Utdoa.Succ
WRFD-020802
OTDOA Based LCS
1.10.9 Paging Measurement <per RNC>(PAGE.RNC)

Overview
To page an UE, the CN sends a PAGING message to the RNC. Then, the RNC sends a PAGING
TYPE 1 message or a PAGING TYPE 2 message to the UE according to the status of the UE.
If the paged UE is in idle mode, CELL_PCH state or URA_PCH state, the RNC shall send a
PAGING TYPE 1 message on the PCH to the cell in the paged area. If the UE is in CELL_PCH
state and EPCH is supported by the network and the UE, the RNC sends a PAGING TYPE 2
message to the cells in the paging area. If the UE is in CELL_FACH or CELL_DCH state, the
RNC shall send a PAGING TYPE 2 message to the UE on the DCCH.
In addition, the UTRAN can send a PAGING TYPE 1 message to an UE in idle mode,
CELL_PCH state or URA_PCH state for system information update. Also, the UTRAN can
send a PAGING TYPE 1 message to an UE in CELL_PCH or URA_PCH state for UE state
transition to support data transmission.
If the paged UE is in idle mode, it will send a RRC CONNECTION REQUEST message to the
RNC after receiving a PAGING TYPE 1 message. If the UE is in CELL_PCH or URA_PCH
state, it will send a CELL UPDATE message with the cell update cause of "paging response" to
the RNC after it receives a PAGING TYPE 1 message.
For more information, refer to 3GPP TS 25.331 and 3GPP TS 25.413.
When the parallel handling of the paging procedure is enabled, the RNC can page UEs in idle
mode, CELL_PCH, or URA_PCH state at a time before it receives the PAGING message from
the CS domain of the CN.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174402
VS.RANAP.Paging
.Att.IdleUE
Number of CN
Pagings to Idle UE
for RNC
Earlier than
BSC6900
V900R011
67174403
VS.RANAP.Paging
.Succ.IdleUE
Number of
Successful CN
Pagings to Idle UE
for RNC
Earlier than
BSC6900
V900R011

588
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174405
VS.UTRAN.Paging
1.Att
Number of UTRANOriginated PAGING

TYPE 1 Messages
for RNC
Earlier than
BSC6900
V900R011
67174404
VS.UTRAN.Paging
2.Att
Number of PAGING
TYPE 2 Messages
for RNC
Earlier than
BSC6900
V900R011
67174406
VS.UTRAN.SuccPage1
Number of
Successful
Responses to
PAGING TYPE 1
Messages for RNC
Earlier than
BSC6900
V900R011
67193711
VS.RANAP.CsPagi
ng.Att
Number of CN
Paging Requests of
CS Domain for RNC
Earlier than
BSC6900
V900R011
67193712
VS.RANAP.PsPagi
ng.Att
Number of CN
Paging Requests of
PS Domain for RNC
Earlier than
BSC6900
V900R011
67193713
VS.RANAP.CsPagi
ng.Loss
Number of
Unsuccessful CN
Paging Requests of
CS Domain for RNC
Earlier than
BSC6900
V900R011
67192714
VS.RANAP.PsPagi
ng.Loss
Number of
Unsuccessful CN
Paging Requests of
PS Domain for RNC
Earlier than
BSC6900
V900R011
73394071
VS.Paging1.Succ.P
TT.RNC
Number of
Successful PAGING
TYPE 1 Message
Responses from PTT
UEs Received by
RNC
BSC6900
V900R012
73394072
VS.Paging1.Att.PT
T.RNC
Number of RNCOriginated PAGING

TYPE 1 Messages to
PTT UEs
BSC6900
V900R012
73428436
VS.RANAP.ConvP
aging.Att.IdleUE
Number of Paging
Attempts Initiated by
the CN to Page UEs
in Idle Mode due to
Conversational
Services
BSC6900
V900R016C00

589
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428437
VS.RANAP.ConvP
aging.Succ.IdleUE
Number of
Successful Paging
Initiated by the CN to
Page UEs in Idle
Mode due to
Conversational
Services
BSC6900
V900R016C00
73428438
VS.UTRAN.Paging
1.Att.PCHUE.DataTrans
Number of Paging
the UTRAN to Page
UEs in the
CELL_PCH/
URA_PCH State due
to PS Data
Transmission
BSC6900
V900R016C00
73428439
VS.UTRAN.Paging
1.Succ.PCHUE.DataTrans
Number of
Successful Paging
Initiated by the
UTRAN to Page UEs
in the CELL_PCH/
URA_PCH State due
to PS Data
Transmission
BSC6900
V900R016C00
73428440
VS.UTRAN.Paging
1.Att.PCHUE.First
Number of Paging
the UTRAN to Page
UEs in the
CELL_PCH/
URA_PCH State
BSC6900
V900R016C00
73428441
VS.RANAP.Paging
1.Att.PCHUE
Number of Paging
the CN to Page UEs
in the CELL_PCH/
URA_PCH State
BSC6900
V900R016C00
73428442
VS.RANAP.Paging
1.Succ.PCHUE
Number of
Successful Paging
Initiated by the CN to
Page UEs in the
CELL_PCH/
URA_PCH State
BSC6900
V900R016C00
73428443
VS.UTRAN.SuccPaging2
Number of Response
Messages to the
PAGING TYPE 2
Message
BSC6900
V900R016C00

590
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73429229
VS.ExtdPaging1.At
t.Idle.CS
Number of Extended
Paging Attempts
Triggered by CS
Conversational
in Idle Mode for
RNC
BSC6900
V900R017C00
73429231
VS.ExtdPaging1.Su
cc.Idle.CS
Number of
Successful Extended
Pagings Triggered by
CS Conversational
in Idle Mode for
RNC
BSC6900
V900R017C00
73430079
VS.Paging.Parallel.
Att
Number of Attempts
to Initiate the Parallel
Paging Procedure for
RNC
BSC6900
V900R017C10
73430080
VS.Paging.Parallel.
Succ
Number of Times the

Parallel Paging
Procedure Is
Successfully
Initiated for RNC
BSC6900
V900R017C10
73430081
VS.Paging.Parallel.
Invalid
Number of Times the

Parallel Paging
Procedure Fails to Be
Initiated for RNC
BSC6900
V900R017C10
73430332
VS.RANAP.Paging
.Att.ParallelTrans
Number of
Redundant Paging
Messages in Parallel
Paging Procedures
for RNC
BSC6900
V900R017C10
Issue 03 (2015-06-30)
Counter
Sub Counter
VS.UTRAN.Paging1.Att.PCHUE.First
VS.UTRAN.Paging1.Att.PCHUE.DataTrans

591
BSC6900 UMTS
Counter
Sub Counter
VS.UTRAN.SuccPage1
VS.UTRAN.Paging1.Succ.PCHUE.DataTrans
Number of Paging Messages to UE

Counters
Counter ID
Counter Name
Counter Description
67174402
VS.RANAP.Paging.Att.Idle
UE
Number of CN Pagings to
Idle UE for RNC
Description
This measurement counter takes statistics of the number of PAGING TYPE 1 messages from
the RNC to the UEs in idle mode after it receives the PAGING messages from the CN.This
counter complies with section "8.1.2 Paging" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives a
PAGING message from the CN, and if the paged UE is in idle mode, the RNC sends a PAGING
TYPE 1 message to the cell in the paged area. In this case, the RNC measures this counter.
Figure 1-264 Number of Paging Messages to UEs in Idle Mode
Issue 03 (2015-06-30)

592
BSC6900 UMTS
The measurement is triggered at point A in the figure. During a parallel paging procedure, if the
UE to be paged is in Idle mode, the RNC sends a PAGING TYPE 1 message in the paging area.
If the RNC receives a PAGING message from the CN before the timer set to protect the parallel
paging procedure expires, this counter is measured.
Figure 1-265 Paging procedure for the UE in idle mode
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.Paging.Att.Idle
UE
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-171202
Issue 03 (2015-06-30)

593
BSC6900 UMTS
Number of Successful Paging Messages to UE

Counters
Counter ID
Counter Name
Counter Description
67174403
VS.RANAP.Paging.Succ.Idl
eUE
Number of Successful CN
Pagings to Idle UE for RNC
Description
This measurement counter takes statistics of the number of RRC CONNECTION REQUEST
messages from the UEs to the RNC that has sent a PAGING TYPE 1 messages to page the UEs
in idle mode.This counter complies with section "8.1.3 RRC connection establishment" in 3GPP
TS 25.331 (v10.13.0).
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-266 Number of Paging Messages to UEs in Idle Mode
Issue 03 (2015-06-30)

594
BSC6900 UMTS
The measurement is triggered at point A in the figure. After triggering a parallel paging
procedure, the RNC receives an RRC CONNECTION REQUEST message with the cause value
"Terminating Conversational Call" from the UE. If the RNC receives a PAGING message from
the CN before the timer set to protect the parallel paging procedure expires, this counter is
measured.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.Paging.Succ.Idl
eUE
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-171202
Issue 03 (2015-06-30)

595
BSC6900 UMTS
Number of RNC-Originated PAGING TYPE 1 Messages

Counters
Counter ID
Counter Name
Counter Description
67174405
VS.UTRAN.Paging1.Att
Number of UTRANOriginated PAGING TYPE 1

Messages for RNC
Description
This measurement counter takes statistics of the number of PAGING TYPE 1 messages
originated by the RNC for triggering the state transition of an UE in CELL_PCH or URA_PCH
state. Statistics taken by this item excludes the number of PAGING TYPE 1 messages that the
RNC originates for the modification of system information.This counter complies with section
"8.1.2 Paging" in 3GPP TS 25.331 (v10.13.0).
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.
Figure 1-268 Response of an UE in CELL_PCH or URA_PCH state to the PAGING TYPE 1
message
Issue 03 (2015-06-30)

596
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of PAGING TYPE 2 Messages

Counters
Counter ID
Counter Name
Counter Description
67174404
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. This counter complies with section "8.1.2 Paging" in 3GPP
TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

597
BSC6900 UMTS
Figure 1-269 Procedure of CN paging UE in CELL_FACH or CELL_DCH state
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010302
Number of Successful Responses to PAGING TYPE 1 Messages

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67174406
VS.UTRAN.SuccPage1
Responses to PAGING
TYPE 1 Messages for RNC

598
BSC6900 UMTS
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.
This counter complies with section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331
(v10.13.0).
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.
Figure 1-270 Response of an UE in CELL_PCH or URA_PCH state to the PAGING TYPE 1
message
Formula
None
Unit
None
Issue 03 (2015-06-30)

599
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.UTRAN.SuccPage1
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of CS-Oriented PAGING Messages from the CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.1.2 Paging" in 3GPP TS 25.331
(v10.13.0).
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-271 Procedure of paging from the CN
Issue 03 (2015-06-30)

600
BSC6900 UMTS
The measurement is triggered at point A in the figure. After triggering a parallel paging
procedure, if the RNC receives a PAGING message from the CN before the timer set to protect
the parallel paging procedure expires, this counter is measured.
Figure 1-272 Parallel paging procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.CsPaging.Att
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-010302
WRFD-171202
Issue 03 (2015-06-30)

601
BSC6900 UMTS
Number of PS-Oriented PAGING Messages from the CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.1.2 Paging" in 3GPP TS 25.331
(v10.13.0).
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.
Formula
None
Issue 03 (2015-06-30)

602
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.PsPaging.Att
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-010302
Number of Failures to Respond to CS-Oriented PAGING Messages from the CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.1.2 Paging"
in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives from
the CN a PAGING message in which the CN Domain Indicator IE indicates the CS domain, the
measurement of this counter is triggered if the RNC does not send a Paging type 1 or Paging
type 2 message. The reason why the RNC does not send a Paging type 1 or Paging type 2 message
might be Iu flow control, or high CPU usage. If the RNC does not respond to a paging message
that is consecutively retransmitted, the RNC counts it only once.
Issue 03 (2015-06-30)

603
BSC6900 UMTS
The measurement is triggered at point A in the figure. The RNC triggers a parallel paging
procedure but does not send a PAGING TYPE 1 message to the UE. If the RNC receives a
PAGING message from the CN before the timer set to protect the parallel paging procedure
expires, this counter is measured. The RNC does not send a PAGING TYPE 1 message to the
UE due to various reasons, such as flow control over the Iu interface and high CPU load. If the
RNC does not respond to multiple consecutive retransmitted PAGING messages (including
parallel paging procedures and repeated paging on the CN side), this counter is measured only
once.
Issue 03 (2015-06-30)

604
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.CsPaging.Loss
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-010302
WRFD-171202
Issue 03 (2015-06-30)

605
BSC6900 UMTS
Number of Failures to Respond to PS-Oriented PAGING Messages from the CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.1.2 Paging"
in 3GPP TS 25.331 (v10.13.0).
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.
Formula
None
Issue 03 (2015-06-30)

606
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.PsPaging.Loss
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-010302
Number of CELL UPDATE Messages from PTT UEs as Paging Response Received
by RNC
Counters
Counter ID
Counter Name
Counter Description
73394071
VS.Paging1.Succ.PTT.RNC
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.This counter complies with
section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331 (v10.13.0).
Measurement point
This measurement is triggered at point B as shown in the figure, when the RNC receives from
the PTT UE a CELL UPDATE message with a cause value of "paging response".
Issue 03 (2015-06-30)

607
BSC6900 UMTS
Figure 1-277 Procedure for UEs in CELL_PCH or URA_PCH state to respond to the PAGING
TYPE 1 message
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging1.Succ.PTT.RNC
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-020134
Push to Talk
Issue 03 (2015-06-30)

608
BSC6900 UMTS
Number of RNC-Originated PAGING TYPE 1 Messages to PTT UEs in CELL_PCH

or URA_PCH state
Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.1.2 Paging" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC automatically
sends a PAGING TYPE 1 message to the PTT UEs in CELL_PCH or URA_PCH state. The
PAGING TYPE 1 message sent by the RNC due to system information change are not measured
in this counter.
Figure 1-278 Procedure for UEs in CELL_PCH or URA_PCH state to respond to the PAGING
TYPE 1 message
Issue 03 (2015-06-30)

609
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging1.Att.PTT.RNC
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-020134
Push to Talk
Number of Paging Attempts Initiated by the CN to Page UEs in Idle Mode due to
Conversational Services
Counters
Counter ID
Counter Name
Counter Description
73428436
VS.RANAP.ConvPaging.At
t.IdleUE
Number of Paging Attempts

Initiated by the CN to Page
UEs in Idle Mode due to
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC after the
RNC receives from the CN a PAGING message with the cause value of "Terminating
Conversational Call" to page UEs in idle mode.This counter complies with section "8.1.2
Paging" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point B shown in the following figure. Upon receiving from
the CN a PAGING message with the cause value of "Terminating Conversational Call" to page
UEs in idle mode, the RNC sends a PAGING TYPE 1 message to cells in the paging area. In
this case, this counter is increased by one.
Issue 03 (2015-06-30)

610
BSC6900 UMTS
Figure 1-279 Procedure for the CN to page UEs in idle mode due to conversational services
UE to be paged is in idle mode, the RNC sends a PAGING TYPE 1 message in the paging area.
If the RNC receives a PAGING message from the CN before the timer set to protect the parallel
paging procedure expires, this counter is measured.
Issue 03 (2015-06-30)

611
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.ConvPaging.At
t.IdleUE
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-171202
Number of Successful Paging Initiated by the CN to Page UEs in Idle Mode due to
Counters
Counter ID
Counter Name
Counter Description
73428437
VS.RANAP.ConvPaging.Su
cc.IdleUE
Paging Initiated by the CN to
Page UEs in Idle Mode due to
Description
This counter measures the number of RRC CONNECTION REQUEST messages returned by
the UE after the UE in idle mode receives from the RNC a PAGING TYPE 1 message with the
cause value of "Terminating Conversational Call."This counter complies with section "8.1.3
Measurement point
The measurement is triggered at point C shown in the following figure. When the RNC receives
from the UE an RRC CONNECTION REQUEST message with the cause value of "Terminating
Conversational Call", this counter is increased by one.
Issue 03 (2015-06-30)

612
BSC6900 UMTS
Figure 1-281 Procedure for the CN to page UEs in idle mode due to conversational services
UE to be paged is in idle mode, the RNC sends a PAGING TYPE 1 message in the paging area.
When the RNC receives an RRC CONNECTION REQUEST message with the cause value
"Terminating Conversational Call" from the UE and receives a PAGING message from the CN
before the timer set to protect the parallel paging procedure expires, this counter is measured.
Issue 03 (2015-06-30)

613
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.ConvPaging.Su
cc.IdleUE
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-171202
Number of Paging Attempts Initiated by the UTRAN to Page UEs in the

CELL_PCH/URA_PCH State due to PS Data Transmission
Counters
Counter ID
Counter Name
Counter Description
73428438
VS.UTRAN.Paging1.Att.PC
HUE.DataTrans

Initiated by the UTRAN to
Page UEs in the CELL_PCH/
URA_PCH State due to PS
Data Transmission
Description
This counter measures the number of PAGING TYPE 1 messages initiated by the RNC to page
UEs in the CELL_PCH/URA_PCH state due to PS data transmission. UEs in the CELL_PCH/
URA_PCH state cannot transmit data and the RNC must first send the UE a Paging Type 1
message to instruct the UE to perform a state transition. Retransmitted PAGING TYPE 1
messages are not measured.This counter complies with section "8.1.2 Paging" in 3GPP TS
25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A shown in the following figure. When the RNC needs
to send PS data to the UE in the CELL_PCH/URA_PCH state, the RNC sends the UE a PAGING
TYPE 1 message. In this case, this counter is increased by one. Retransmitted PAGING TYPE
1 messages are not measured.
Issue 03 (2015-06-30)

614
BSC6900 UMTS
Figure 1-283 Procedure for the UTRAN to page UEs in the CELL_PCH or URA_PCH state
due to PS data transmission
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
HUE.DataTrans
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of Successful Paging Initiated by the UTRAN to Page UEs in the

CELL_PCH/URA_PCH State due to PS Data Transmission
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428439
VS.UTRAN.Paging1.Succ.P
CHUE.DataTrans
Paging Initiated by the
UTRAN to Page UEs in the
CELL_PCH/URA_PCH
State due to PS Data
Transmission

615
BSC6900 UMTS
Description
This counter measures the number of CELL UPDATE messages returned by the UE after the
UE in the CELL_PCH or URA_PCH state receives from the RNC a PAGING TYPE 1 message
due to PS data transmission. Upon receiving a PAGING TYPE 1 message from the RNC, the
UE in the CELL_PCH/URA_PCH state responds with a CELL UPDATE message with the cause
value of "paging response".This counter complies with section "8.1.3 RRC connection
Measurement point
The measurement is triggered at point B shown in the following figure. When the RNC receives
a CELL UPDATE message with the cause value of "paging response" from a UE in the
CELL_PCH or URA_PCH state, this counter is increased by one.
Figure 1-284 Procedure for the UTRAN to page UEs in the CELL_PCH or URA_PCH state
due to PS data transmission
Formula
None
Unit
None
Issue 03 (2015-06-30)

616
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.UTRAN.Paging1.Succ.P
CHUE.DataTrans
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of Paging Attempts Initiated by the UTRAN to Page UEs in the

CELL_PCH/URA_PCH State
Counters
Counter ID
Counter Name
Counter Description
73428440
HUE.First

Initiated by the UTRAN to
URA_PCH State
Description
This counter measures the number of PAGING TYPE 1 messages initiated by the RNC to page
UEs in the CELL_PCH/URA_PCH state. Retransmitted PAGING TYPE 1 messages and
PAGING TYPE 1 messages triggered by system information modifications are not
measured.This counter complies with section "8.1.2 Paging" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A shown in the following figure. When the RNC sends
the UE a PAGING TYPE 1 message, this counter is increased by one. Retransmitted PAGING
TYPE 1 messages are not measured.
Figure 1-285 Procedure for the UTRAN to page UEs in the CELL_PCH/URA_PCH state
Issue 03 (2015-06-30)

617
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
HUE.First
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of Paging Attempts Initiated by the CN to Page UEs in the CELL_PCH/

URA_PCH State
Counters
Counter ID
Counter Name
Counter Description
73428441
VS.RANAP.Paging1.Att.PC
HUE

Initiated by the CN to Page
UEs in the CELL_PCH/
URA_PCH State
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC after
receiving from the CN a PAGING message to page UEs in the CELL_PCH/URA_PCH state.
Retransmitted PAGING TYPE 1 messages are not measured.This counter complies with section
"8.1.2 Paging" in 3GPP TS 25.331 (v10.13.0).
Measurement point
the CN a PAGING message to page UEs in the CELL_PCH/URA_PCH state, the RNC sends
a PAGING TYPE 1 message to cells in the paging area. In this case, this counter is increased
by one. Retransmitted PAGING TYPE 1 messages are not measured.
Issue 03 (2015-06-30)

618
BSC6900 UMTS
Figure 1-286 Procedure for the CN to page UEs in the CELL_PCH/URA_PCH state
UE to be paged is in the CELL_PCH or URA_PCH state, the RNC sends a PAGING TYPE 1
message in the paging area. If the RNC receives a PAGING message from the CN before the
timer set to protect the parallel paging procedure expires, this counter is measured. The
retransmitted PAGING messages are not measured.
Issue 03 (2015-06-30)

619
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.Paging1.Att.PC
HUE
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-171202
Number of Successful Paging Initiated by the CN to Page UEs in the CELL_PCH/

URA_PCH State
Counters
Counter ID
Counter Name
Counter Description
73428442
VS.RANAP.Paging1.Succ.P
CHUE
Paging Initiated by the CN to
URA_PCH State
Description
This counter measures the number of CELL UPDATE messages returned by the UE for the
PAGING TYPE 1 message after the RNC receives from the CN a PAGING message to page
UEs in the CELL_PCH/URA_PCH state.This counter complies with section "8.1.3 RRC
Measurement point
The measurement is triggered at point C shown in the following figure. When the RNC receives
from the UE a CELL UPDATE message with the cause value of "uplink data transmission" or
"paging response", this counter is increased by one.
Issue 03 (2015-06-30)

620
BSC6900 UMTS
Figure 1-288 Procedure for the CN to page UEs in the CELL_PCH/URA_PCH state
The measurement is triggered at point A in the figure. During a parallel paging procedure, the
RNC receives a CELL UPDATE message with the cause value "uplink data transmission" or
"paging response". If the RNC receives a PAGING message from the CN before the timer set
to protect the parallel paging procedure expires, this counter is measured.
Issue 03 (2015-06-30)

621
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.Paging1.Succ.P
CHUE
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-171202
Number of Response Messages to the PAGING TYPE 2 Message

Counters
Counter ID
Counter Name
Counter Description
73428443
Number of Response
Messages to the PAGING
TYPE 2 Message
Description
This counter measures the number of INITIAL DIRECT TRANSFER messages returned by the
UE for the PAGING TYPE 2 message after the RNC receives a PAGING message from the CN
to page UEs in the CELL_FACH/CELL_DCH state.This counter complies with section "8.1.3
Measurement point
the CN a PAGING message to page UEs in the CELL_FACH/CELL_DCH state, the RNC sends
the UE a PAGING TYPE 2 message. If the UE responds with an INITIAL DIRECT TRANSFER
message, this counter is increased by one.
Issue 03 (2015-06-30)

622
BSC6900 UMTS
Figure 1-290 Procedure for the CN to page UEs in the CELL_FACH/CELL_DCH state
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010302
Number of Extended Paging Attempts Triggered by CS Conversational Services to

Page UEs in Idle Mode for RNC
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73429229
Number of Extended Paging

Attempts Triggered by CS
Conversational Services to
Page UEs in Idle Mode for
RNC

623
BSC6900 UMTS
Description
This counter provides the number of extended paging attempts triggered by CS conversational
services to page UEs in idle mode in an extended location area (LA) of an RNC. This counter
is measured on the RNC that sends extended paging messages in the extended LA.
Measurement point
with the cause value "Terminating Conversational Call" from the CN, this counter is measured
on the RNC if the RNC determines to send paging messages in the extended LA and the UE to
be paged is in idle mode.
in idle mode under the SRNC
with the cause value "Terminating Conversational Call" over the Iur interface, this counter is
measured on the RNC if the RNC determines to send paging messages in the extended LA and
the UE to be paged is in idle mode.
Issue 03 (2015-06-30)

624
BSC6900 UMTS
in idle mode under the DRNC
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-170104
Seamless Paging
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)

625
BSC6900 UMTS
Number of Successful Extended Pagings Triggered by CS Conversational Services

to Page UEs in Idle Mode for RNC
Counters
Counter ID
Counter Name
Counter Description
73429231
VS.ExtdPaging1.Succ.Idle.
CS
Extended Pagings Triggered
by CS Conversational
Services to Page UEs in Idle
Mode for RNC
Description
This counter provides the number of times the RNC successfully receives an RRC Connection
Request message with the cause value "Terminating Conversational Call" from a UE in a cell
that does not belong to the LAC carried in the paging message after sending paging messages
triggered by CS conversational services to page a UE in idle mode in the extended LA. This
counter is measured on the RNC that sends paging messages.
Measurement point
The measurement is triggered at point B in the following figure. After sending PAGING TYPE1
messages in the extended LA, the RNC receives an RRC Connection Request message with the
cause value "Terminating Conversational Call" from a UE before the specified timer expires.
Under this circumstance, the RNC determines that the extended paging is successful, and the
value of this counter is increased by one on the RNC that receives the RRC Connection Request
message.
Figure 1-293 A successful extended paging triggered by CS conversational services to page
UEs in idle mode for RNC
Issue 03 (2015-06-30)

626
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ExtdPaging1.Succ.Idle.
CS
WRFD-170104
Seamless Paging
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of Attempts to Initiate the Parallel Paging Procedure for RNC

Counters
Counter ID
Counter Name
Counter Description
73430079
VS.Paging.Parallel.Att
Number of Attempts to
Initiate the Parallel Paging
Procedure for RNC
Description
This counter provides the number of attempts to initiate the parallel paging procedure for RNC.
Measurement point
The measurement is triggered at point A in the figure when the RNC sends a PAGING TYPE
1 message to the UE to initiate a parallel paging procedure.
Issue 03 (2015-06-30)

627
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Paging.Parallel.Att
WRFD-171202

628
BSC6900 UMTS
Number of Times the Parallel Paging Procedure Is Successfully Initiated for RNC
Counters
Counter ID
Counter Name
Counter Description
73430080
VS.Paging.Parallel.Succ
Number of Times the Parallel

Paging Procedure Is
Successfully Initiated for
RNC
Description
This counter provides the number of times the parallel paging procedure is successfully initiated
in an RNC.
Measurement point
The measurement is triggered at point B in the figure. After sending a PAGING TYPE 1 message
to the UE to initiate a parallel paging procedure, if the RNC receives an RRC CONNECTION
REQUEST or CELL UPDATE message from the UE before the paging protection timer expires,
this counter is measured.
Issue 03 (2015-06-30)

629
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging.Parallel.Succ
WRFD-171202
Number of Times the Parallel Paging Procedure Fails to Be Initiated for RNC
Counters
Counter ID
Counter Name
Counter Description
73430081
VS.Paging.Parallel.Invalid
Number of Times the Parallel

Paging Procedure Fails to Be
Initiated for RNC
Description
This counter provides the number of times the parallel paging procedure fails to be initiated in
an RNC.
Measurement point
The measurement is triggered at point A in the figure. After sending a PAGING TYPE 1 message
to the UE to initiate a parallel paging procedure, if the RNC does not receive a PAGING message
from the CN before the paging protection timer expires, this counter is measured.
Issue 03 (2015-06-30)

630
BSC6900 UMTS
Figure 1-296 Parallel paging procedure (timer expired)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging.Parallel.Invalid
WRFD-171202
Number of Redundant Paging Messages in Parallel Paging Procedures for RNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430332
VS.RANAP.Paging.Att.ParallelTrans
Number of Redundant
Paging Messages in Parallel
Paging Procedures for RNC

631
BSC6900 UMTS
Description
This counter provides the number of redundant paging messages in parallel paging procedures
in an RNC. This counter complies with 3GPP TS 25.331 (V11.7.0). For details, see section 8.1.2
"Paging" in this TS.
Measurement point
The measurement is triggered at point A in the following figure. After receiving a paging request
message from the CN, the RNC determines to trigger a parallel paging procedure and sends a
PAGING TYPE 1 message for the UE in idle mode together with a PAGING TYPE 1 message
for the UE in the CELL_PCH or URA_PCH state or a PAGING TYPE 2 message. Under these
circumstances, this counter is measured.
Formula
None
Unit
None
Issue 03 (2015-06-30)

632
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RANAP.Paging.Att.ParallelTrans
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-010302
1.10.10 PDCP Measurement(PDCPGTPU.RNC)

Overview
The RNC-based PDCP measurement focuses on the Robust Header Compression (ROHC) of
PDCP headers.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67204484
VS.PDCP.DL.ROH
C.HdrCompressRa
tio
Compression Rate of
DL Packet Header
Through ROHC
Compression
Earlier than
BSC6900
V900R011
67204485
VS.PDCP.DL.ROH
C.PktCompressRatio
Compression Rate of
DL Packets After
ROHC Compression
Earlier than
BSC6900
V900R011
67204486
VS.PDCP.UL.ROH
C.FailDecompRatio
Decompression
Failure Rate of UL
Packets Through
ROHC Algorithm
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

633
BSC6900 UMTS
Compression Ratio of DL Packet Headers Under ROHC

Counters
Counter ID
Counter Name
Counter Description
67204484
VS.PDCP.DL.ROHC.HdrC
ompressRatio
Compression Rate of DL
Packet Header Through
ROHC Compression
Description
This measurement item takes statistics of the ratio of the packet header size after all downlink
PS packets undergo Robust Header Compression (ROHC) to the header size before the ROHC
during a measurement period in the RNC. This measurement item is valid when the ROHC
algorithm is configured.
Measurement point
When a PDCP entity receives a downlink packet, it judges whether the packet is configured with
ROHC. If the packet is not configured with ROHC, the PDCP entity does not report this
measurement item. If the packet is configured with ROHC, the PDCP entity goes through the
sub-headers of the packet to obtain the chain size before adding the size to the item DL Packet
Header Size before Compression. After the compression, the PDCP entity then adds the new
sub-header chain size to the item DL Packet Header Size after Compression.
At the end of the measurement period, the PDCP entity reports the two item values to the
performance function subset and resets the two items. Then the performance function subset
calculates the compression ratio of the downlink packet headers under ROHC based on the
reported values of DL Packet Header Size before Compression and DL Packet Header Size after
Compression.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PDCP.DL.ROHC.HdrC
ompressRatio
WRFD-010617

634
BSC6900 UMTS
Compression Ratio of DL Packets Under ROHC

Counters
Counter ID
Counter Name
Counter Description
67204485
VS.PDCP.DL.ROHC.PktCo
mpressRatio
Compression Rate of DL
Packets After ROHC
Compression
Description
This measurement item takes statistics of the ratio of the packet size after all downlink PS packets
undergo Robust Header Compression (ROHC) to the packet size before the ROHC during a
measurement period in the RNC. This measurement item is valid when the ROHC algorithm is
configured.
Measurement point
When a PDCP entity receives a downlink packet, it judges whether the packet is configured with
ROHC. If the packet is not configured with ROHC, the PDCP entity does not report this
measurement item. If the packet is configured with ROHC, the number of compressed downlink
packets increases by one. Meanwhile, the PDCP entity adds the initial packet size to the item
DL Packet Size before Compression. After the compression, it adds the packet size to the item
DL Packet Size after Compression. At the end of the measurement period, the PDCP entity
reports the two item values to the performance function subset and resets the two items. Then
the performance function subset calculates the compression ratio of the downlink packets under
ROHC based on the reported values of DL Packet Size before Compression and DL Packet Size
after Compression. Both service data and packet headers are measured.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PDCP.DL.ROHC.PktCo
mpressRatio
WRFD-010617

635
BSC6900 UMTS
Ratio of UL ROHC Decompression Failures to Total UL ROHC Decompression

Operations
Counters
Counter ID
Counter Name
Counter Description
67204486
VS.PDCP.UL.ROHC.FailDecompRatio
Decompression Failure Rate

of UL Packets Through
ROHC Algorithm
Description
This measurement item takes statistics of the ratio of the number of UL PS packets failing to be
decompressed by Robust Header Compression (ROHC) to the total number of UL packets
undergoing ROHC decompression during a measurement period in the RNC. This measurement
item is valid when the ROHC algorithm is configured.
Measurement point
When a PDCP entity receives an uplink packet, it judges whether the packet is configured with
ROHC. If the packet is configured with ROHC, the value of the item Number of Uplink Packets
to Be Decompressed increases by 1. Then, if the decompression fails, the value of the item
Number of UL Packets Failing to Be Decompressed increases by 1. At the end of the
measurement period, the PDCP entity reports the two item values to the performance function
subset and resets the two items. Then, the performance function subset calculates the ratio of
Number of Uplink Packets Failing to Be Decompressed to Number of UL Packets to Be
Decompressed.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PDCP.UL.ROHC.FailDecompRatio
WRFD-010617

636
BSC6900 UMTS
1.10.11 CS RAB Setup Measurement <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. After the parallel handling of the
alerting and RAB setup procedures is introduced, the RNC sends a RAB ASSIGNMENT
RESPONSE message to the CN in an earlier time for RB setup over the Uu interface.
If the RB setup over the Uu interface fails, the RNC sends a message to the CN to release the
connection over the Iu interface.
The differences between the existing RAB setup procedure and the RAB setup procedure in
parallel with the alerting procedure are as follows:
1. In the existing RAB setup procedure, after receiving an RB SETUP COMPLETE message
from the UE, the RNC sends a RAB ASSIGNMENT RESPONSE message. In the parallel RAB
setup procedure, the RNC sends an RB SETUP message to the UE to trigger the RB setup
procedure, and in addition the RNC sends a RAB ASSIGNMENT RESPONSE message to the
CN at an earlier time.
2. In the existing RAB setup procedure, if the RB setup fails, the RNC sends an IU RELEASE
REQUEST or RAB ASSIGNMENT RESPONSE message to the CN, indicating the RB setup
failure. In the parallel RAB setup procedure, if the RB setup fails, the RNC sends an IU
RELEASE REQUEST message to the CN to release the connection over the Iu interface.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174721
VS.RAB.AttEstab
CS.Conv.RNC
Number of CS
Conversational RAB
Establishment
Attempts for RNC
Earlier than
BSC6900
V900R011

637
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67174722
VS.RAB.AttEstab
CS.Str.RNC
Number of CS
Streaming RAB
Establishment
Attempts for RNC
Earlier than
BSC6900
V900R011
67199791
VS.RAB.Num.CS.
Mean
Mean Number of CS
RABs for RNC
Earlier than
BSC6900
V900R011
67196235
VS.RAB.AttEstab
CS.VPLimit.RNC
Number of
Attempted 64kbit/s
CS RAB
Establishments in a
Cell Where 64kbit/s
CS Service is
Forbidden for RNC
Earlier than
BSC6900
V900R011
73394064
VS.RAB.SuccEstab
CS.Conv.RNC
Number of
Successful RAB
Establishments for
CS Conversational
Services for RNC
BSC6900
V900R012
73394065
VS.RAB.SuccEstab
CS.Str.RNC
Number of
Successful CS
Streaming RAB
Establishments for
RNC
BSC6900
V900R012
None
Number of CS RABs Requested to Establish

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67174721
RNC
Number of CS
Conversational RAB
Establishment Attempts for
RNC
67174722
VS.RAB.AttEstabCS.Str.R
NC
RAB Establishment
Attempts for RNC

638
BSC6900 UMTS
Description
This counter provides the number of CS RABs establishment requests in the RNC according to
different services.The preceding counters comply with section "8.2 RAB Assignment" in 3GPP
TS 25.413 (v10.10.0).
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
Issue 03 (2015-06-30)

639
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
RNC
WRFD-010501
VS.RAB.AttEstabCS.Str.R
NC
WRFD-010502
Streaming QoS Class
Counter ID
Counter Name
Counter Description
67199791
VS.RAB.Num.CS.Mean
Mean Number of CS RABs

for RNC
Mean Number of CS RABs

Counters
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.Num.CS.Mean
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

640
BSC6900 UMTS
Number of CS VP RABs requested to establish in cell where VP is forbidden

Counters
Counter ID
Counter Name
Counter Description
67196235
VS.RAB.AttEstabCS.VPLi
mit.RNC
Number of Attempted
64kbit/s CS RAB
Establishments in a Cell
Where 64kbit/s CS Service is
Forbidden for RNC
Description
This counter provides the number of RAB setup requests for VP services when the VP call is
limited.This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
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.
Figure 1-299 RAB assignment procedure (successful operation)
Issue 03 (2015-06-30)

641
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabCS.VPLi
mit.RNC
WRFD-020130
Videophone Service
Restriction
Number of Successful RAB Establishments for CS Services

Counters
Counter ID
Counter Name
Counter Description
73394064
v.RNC
Number of Successful RAB

Establishments for CS
Conversational Services for
RNC
73394065
VS.RAB.SuccEstabCS.Str.R
NC
Streaming RAB
Establishments for RNC
Description
These counters provide the number of successful RAB establishments for different CS services
in the RNC.The preceding counters comply with section "8.2 RAB Assignment" in 3GPP TS
25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

642
BSC6900 UMTS
The measurement is triggered at point B in the figure. After the parallel handling of the alerting
and RAB setup procedures is enabled, the RNC sends an RAB ASSIGNMENT RESPONSE
message at a time earlier than before. When the RNC receives a RADIO BEARER SETUP
COMPLETE message, this counter is measured.
Issue 03 (2015-06-30)

643
BSC6900 UMTS
Figure 1-301 RAB setup procedure that is in parallel with the alerting procedure
Formula
None
Issue 03 (2015-06-30)

644
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
v.RNC
WRFD-010501
WRFD-171202
VS.RAB.SuccEstabCS.Str.R
NC
WRFD-010502
Streaming QoS Class
1.10.12 PS RAB Setup Measurement <per RNC>

(RAB.EstabPS.RNC)
Overview
The CN in PS domain initiates the radio access bearer setup procedure by sending a RAB
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174785
VS.RAB.AttEstabP
S.Bkg.RNC
Number of PS
Background RAB
Establishment
Attempts for RNC
Earlier than
BSC6900
V900R011
67174788
VS.RAB.AttEstabP
S.Conv.RNC
Number of PS
Conversational RAB
Establishment
Attempts for RNC
Earlier than
BSC6900
V900R011

645
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174787
VS.RAB.AttEstabP
S.Int.RNC
Number of PS
Interactive RAB
Establishment
Attempts for RNC
Earlier than
BSC6900
V900R011
67174786
VS.RAB.AttEstabP
S.Str.RNC
Number of PS
Streaming RAB
Establishment
Attempts for RNC
Earlier than
BSC6900
V900R011
67174812
VS.RAB.EstabPS.
CellFACH.MaxTi
me
Maximum Duration
of PS RAB
Establishments
Mapped on CCH for
RNC
Earlier than
BSC6900
V900R011
67199679
VS.RAB.EstabPS.
CellFACH.MeanTime
Mean Duration of PS
RAB Establishments
Mapped on CCH for
RNC
Earlier than
BSC6900
V900R011
67174809
VS.RAB.EstabPS.
CellDCH.MaxTime
Maximum Duration
of PS RAB
Establishments
Mapped on DCH for
RNC
Earlier than
BSC6900
V900R011
67199427
VS.RAB.EstabPS.
CellDCH.MeanTim
e
Mean Duration of PS
RAB Establishments
Mapped on DCH for
RNC
Earlier than
BSC6900
V900R011
67174827
VS.RAB.AttEstPS
Bkg0.32.RNC
Number of PS
Background RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
[0,32]kbit/s)
Earlier than
BSC6900
V900R011
67174830
VS.RAB.AttEstabP
S.Bkg.
144.384.RNC
Number of PS
Background RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(144,384]kbit/s)
Earlier than
BSC6900
V900R011

646
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174828
VS.RAB.AttEstabP
S.Bkg.32.64.RNC
Number of PS
Background RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(32,64]kbit/s)
Earlier than
BSC6900
V900R011
67174829
VS.RAB.AttEstabP
S.Bkg.64.144.RNC
Number of PS
Background RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(64,144]kbit/s)
Earlier than
BSC6900
V900R011
67174831
VS.RAB.AttEstabP
S.Bkg.Mor384.RN
C
Number of PS
Background RAB
Establishment
Attempts for RNC
(Max DL Bit Rate
More Than 384kbit/
s)
Earlier than
BSC6900
V900R011
67174815
VS.RAB.AttEstabP
S.Conv.0.32.RNC
Number of PS
Conversational RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
[0,32]kbit/s)
Earlier than
BSC6900
V900R011
67174816
VS.RAB.AttEstabP
S.Conv.Mor32.RN
C
Number of PS
Conversational RAB
Establishment
Attempts for RNC
(Max DL Bit Rate
More Than 32kbit/s)
Earlier than
BSC6900
V900R011
67174822
VS.RAB.AttEstabP
S.Int.0.32.RNC
Number of PS
Interactive RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
[0,32]kbit/s)
Earlier than
BSC6900
V900R011
67174825
VS.RAB.AttEstabP
S.Int.144.384.RNC
Number of PS
Interactive RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(144,384]kbit/s)
Earlier than
BSC6900
V900R011

647
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174823
VS.RAB.AttEstabP
S.Int.32.64.RNC
Number of PS
Interactive RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(32,64]kbit/s)
Earlier than
BSC6900
V900R011
67174824
VS.RAB.AttEstabP
S.Int.64.144.RNC
Number of PS
Interactive RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(64,144]kbit/s)
Earlier than
BSC6900
V900R011
67174826
VS.RAB.AttEstabP
S.Int.Mor384.RNC
Number of PS
Interactive RAB
Establishment
Attempts for RNC
(Max DL Bit Rate
More Than 384kbit/
s)
Earlier than
BSC6900
V900R011
67174817
VS.RAB.AttEstabP
S.Str.0.32.RNC
Number of PS
Streaming RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
[0,32]kbit/s)
Earlier than
BSC6900
V900R011
67174818
VS.RAB.AttEstabP
S.Str.32.64.RNC
Number of PS
Streaming RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(32,64]kbit/s)
Earlier than
BSC6900
V900R011
67174820
VS.RAB.AttEstabP
S.Str.144.384.RNC
Number of PS
Streaming RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(144,384]kbit/s)
Earlier than
BSC6900
V900R011
67174819
VS.RAB.AttEstabP
S.Str.64.144.RNC
Number of PS
Streaming RAB
Establishment
Attempts for RNC
(Max DL Bit Rate in
(64,144]kbit/s)
Earlier than
BSC6900
V900R011

648
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174821
VS.RAB.AttEstabP
S.Str.Mor384
Number of PS
Streaming RAB
Establishment
Attempts for RNC
(Max DL Bit Rate
More Than 384kbit/
s)
Earlier than
BSC6900
V900R011
67174844
VS.RAB.SuccEstab
PS.Bkg.0.32.RNC
Number of
Successful PS
Background RAB
Establishments for
RNC (Max DL Bit
Rate in [0,32]kbit/s)
Earlier than
BSC6900
V900R011
67174847
VS.RAB.SuccEstab
PS.Bkg.
144.384.RNC
Number of
Successful PS
Background RAB
Establishments for
RNC (Max DL Bit
Rate in (144,384]
kbit/s)
Earlier than
BSC6900
V900R011
67174845
VS.RAB.SuccEstab
PS.Bkg.32.64.RNC
Number of
Successful PS
Background RAB
Establishments for
RNC (Max DL Bit
Rate in (32,64]kbit/s)
Earlier than
BSC6900
V900R011
67174846
VS.RAB.SuccEstab
PS.Bkg.
64.144.RNC
Number of
Successful PS
Background RAB
Establishments for
RNC (Max DL Bit
Rate in (64,144]kbit/
s)
Earlier than
BSC6900
V900R011
67174832
VS.RAB.SuccEstab
PS.Conv.0.32.RNC
Number of
Successful PS
Conversational RAB
Establishments for
RNC (Max DL Bit
Earlier than
BSC6900
V900R011

649
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174833
VS.RAB.SuccEstab
PS.Conv.Mor32.R
NC
Number of
Successful PS
Conversational RAB
Establishments for
RNC (Max DL Bit
Rate More Than
32kbit/s)
Earlier than
BSC6900
V900R011
67174838
VS.RAB.SuccEstab
PS.Str.Mor384.RN
C
Number of
Successful PS
Streaming RAB
Establishments for
RNC (Max DL Bit
Rate More Than
384kbit/s)
Earlier than
BSC6900
V900R011
67174839
VS.RAB.SuccEstab
PS.Int.0.32.RNC
Number of
Successful PS
Interactive RAB
Establishments for
RNC (Max DL Bit
Earlier than
BSC6900
V900R011
67174842
VS.RAB.SuccEstab
PS.Int.
144.384.RNC
Number of
Successful PS
Interactive RAB
Establishments for
RNC (Max DL Bit
Rate in (144,384]
kbit/s)
Earlier than
BSC6900
V900R011
67174840
VS.RAB.SuccEstab
PS.Int.32.64.RNC
Number of
Successful PS
Interactive RAB
Establishments for
RNC (Max DL Bit
Earlier than
BSC6900
V900R011
67174841
VS.RAB.SuccEstab
PS.Int.64.144.RNC
Number of
Successful PS
Interactive RAB
Establishments for
RNC (Max DL Bit
s)
Earlier than
BSC6900
V900R011

650
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174843
VS.RAB.SuccEstab
PS.Int.Mor384.RN
C
Number of
Successful PS
Interactive RAB
Establishments for
RNC (Max DL Bit
Rate More Than
384kbit/s)
Earlier than
BSC6900
V900R011
67174848
VS.RAB.SuccEstab
PS.Bkg.Mor384.R
NC
Number of
Successful PS
Background RAB
Establishments for
RNC (Max DL Bit
Rate More Than
384kbit/s)
Earlier than
BSC6900
V900R011
67174834
VS.RAB.SuccEstab
.PS.Str.0.32.RNC
Number of
Successful PS
Streaming RAB
Establishments for
RNC (Max DL Bit
Earlier than
BSC6900
V900R011
67174837
VS.RAB.SuccEstab
.PS.Str.
144.384.RNC
Number of
Successful PS
Streaming RAB
Establishments for
RNC (Max DL Bit
Rate in (144,384]
kbit/s)
Earlier than
BSC6900
V900R011
67174835
VS.RAB.SuccEstab
.PS.Str.32.64.RNC
Number of
Successful PS
Streaming RAB
Establishments for
RNC (Max DL Bit
Earlier than
BSC6900
V900R011
67174836
VS.RAB.SuccEstab
.PS.Str.64.144.RNC
Number of
Successful PS
Streaming RAB
Establishments for
RNC (Max DL Bit
s)
Earlier than
BSC6900
V900R011
67199790
VS.RAB.Num.PS.
Mean
Mean Number of PS
RABs for RNC
Earlier than
BSC6900
V900R011

651
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67196304
VS.RAB.SuccEstab
.PS.0kbps.RNC
Number of PS RABs
Established
Successfully with 0
kbit/s for RNC
Earlier than
BSC6900
V900R011
73394066
VS.RAB.SuccEstab
PS.Bkg.RNC
Number of
Successful RAB
Establishments for
PS Background
Services for RNC
BSC6900
V900R012
73394067
VS.RAB.SuccEstab
PS.Str.RNC
Number of
Successful RAB
Establishments for
PS Streaming
Services for RNC
BSC6900
V900R012
73394068
VS.RAB.SuccEstab
PS.Conv.RNC
Number of
Successful RAB
Establishments for
PS Conversational
Services for RNC
BSC6900
V900R012
73394069
VS.RAB.SuccEstab
PS.Int.RNC
Number of
Successful RAB
Establishments for
PS Interactive
Services for RNC
BSC6900
V900R012
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
Issue 03 (2015-06-30)

652
BSC6900 UMTS
Counter
Sub Counter
VS.RAB.AttEstabPS.Int.RNC
VS.RAB.AttEstabPS.Int.0.32.RNC
VS.RAB.AttEstabPS.Int.Mor384.RNC
VS.RAB.AttEstabPS.Str.RNC
VS.RAB.AttEstabPS.Str.0.32.RNC
VS.RAB.AttEstabPS.Str.Mor384
VS.RAB.SuccEstabPS.Bkg.RNC
VS.RAB.SuccEstabPS.Bkg.0.32.RNC
VS.RAB.SuccEstabPS.Bkg.Mor384.RNC
VS.RAB.SuccEstabPS.Conv.RNC
VS.RAB.SuccEstabPS.Conv.0.32.RNC
VS.RAB.SuccEstabPS.Conv.Mor32.RNC
VS.RAB.SuccEstabPS.Str.RNC
VS.RAB.SuccEstabPS.Str.Mor384.RNC
VS.RAB.SuccEstab.PS.Str.0.32.RNC
VS.RAB.SuccEstabPS.Int.RNC
VS.RAB.SuccEstabPS.Int.0.32.RNC
VS.RAB.SuccEstabPS.Int.Mor384.RNC
Issue 03 (2015-06-30)

653
BSC6900 UMTS
Counters Related to the Number of PS RAB Setup Requests for Different Services
Counters
Counter ID
Counter Name
Counter Description
67174788
VS.RAB.AttEstabPS.Conv.
RNC
Number of PS
Conversational RAB
RNC
67174785
VS.RAB.AttEstabPS.Bkg.R
NC
Number of PS Background
RAB Establishment
Attempts for RNC
67174787
VS.RAB.AttEstabPS.Int.RN
C
Number of PS Interactive
RAB Establishment
Attempts for RNC
67174786
VS.RAB.AttEstabPS.Str.RN
C
Number of PS Streaming
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.The preceding counters comply with section "8.2
RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
Measurement point
the SGSN a RAB ASSIGNMENT REQUEST message about the PS domain, the RNC measures
these items according to different types of services.
Issue 03 (2015-06-30)

654
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
RNC
WRFD-010501
VS.RAB.AttEstabPS.Bkg.R
NC
WRFD-010504
VS.RAB.AttEstabPS.Int.RN
C
WRFD-010503

655
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabPS.Str.RN
C
WRFD-010502
Streaming QoS Class
Counter ID
Counter Name
Counter Description
67174812
VS.RAB.EstabPS.CellFAC
H.MaxTime
Maximum Duration of PS
RAB Establishments
Mapped on CCH for RNC
67199679
H.MeanTime
Mean Duration of PS RAB

Establishments Mapped on
CCH for RNC
67174809
VS.RAB.EstabPS.CellDCH.
MaxTime
RAB Establishments
Mapped on DCH for RNC
67199427
MeanTime

DCH for RNC
Signaling Delay of PS RAB Setup

Counters
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67174810
Cum
Cumulative Duration of PS
RAB Establishments
67174811
Sample
Number of Samples
Recorded for Duration of PS
RAB Establishments
67174813
H.Cum
Cumulative Duration of PS
RAB Establishments
Mapped on CCH for RNC
67174814
H.Sample
Number of Samples of
Duration of PS RAB
CCH for RNC

656
BSC6900 UMTS
Description
These measurement items take statistics of the signaling delay of PS RAB setup from different
angles.The preceding counters comply with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
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-303 Flow chart of successful RAB setup
Formula
VS.RAB.EstabPS.CellFACH.MeanTime = [VS.RAB.EstabPS.CellFACH.Cum]/
[VS.RAB.EstabPS.CellFACH.Sample]
Issue 03 (2015-06-30)

657
BSC6900 UMTS
VS.RAB.EstabPS.CellDCH.MeanTime = [VS.RAB.EstabPS.CellDCH.Cum]/
[VS.RAB.EstabPS.CellDCH.Sample]
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
H.MaxTime
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
H.MeanTime
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
MaxTime
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
MeanTime
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counters Related to the Number of PS RAB Setup Requests for Different

Maximum Downlink Bit rates
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67174815
0.32.RNC
Number of PS
Conversational RAB
RNC (Max DL Bit Rate in
[0,32]kbit/s)
67174827
VS.RAB.AttEstPSBkg0.32.
RNC
RAB Establishment
Attempts for RNC (Max DL
Bit Rate in [0,32]kbit/s)

658
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67174830
VS.RAB.AttEstabPS.Bkg.
144.384.RNC
RAB Establishment
Bit Rate in (144,384]kbit/s)
67174828
32.64.RNC
RAB Establishment
67174829
64.144.RNC
RAB Establishment
67174831
VS.RAB.AttEstabPS.Bkg.M
or384.RNC
RAB Establishment
Bit Rate More Than 384kbit/
s)
67174816
Mor32.RNC
Number of PS
Conversational RAB
RNC (Max DL Bit Rate More
Than 32kbit/s)
67174822
VS.RAB.AttEstabPS.Int.
0.32.RNC
RAB Establishment
67174825
144.384.RNC
RAB Establishment
67174823
32.64.RNC
RAB Establishment
67174824
64.144.RNC
RAB Establishment
67174826
VS.RAB.AttEstabPS.Int.Mo
r384.RNC
RAB Establishment
s)

659
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67174817
VS.RAB.AttEstabPS.Str.
0.32.RNC
RAB Establishment
67174818
32.64.RNC
RAB Establishment
67174820
144.384.RNC
RAB Establishment
67174819
64.144.RNC
RAB Establishment
67174821
VS.RAB.AttEstabPS.Str.Mo
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.The
preceding counters comply with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
Measurement point
the SGSN a RAB ASSIGNMENT REQUEST message about the PS domain, the RNC measures
these items according to different types of services.
Issue 03 (2015-06-30)

660
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
0.32.RNC
WRFD-010501
VS.RAB.AttEstPSBkg0.32.
RNC
WRFD-010504
144.384.RNC
WRFD-010504

661
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
32.64.RNC
WRFD-010504
64.144.RNC
WRFD-010504
VS.RAB.AttEstabPS.Bkg.M
or384.RNC
WRFD-010504
Mor32.RNC
WRFD-010501
0.32.RNC
WRFD-010503
144.384.RNC
WRFD-010503
32.64.RNC
WRFD-010503
64.144.RNC
WRFD-010503
VS.RAB.AttEstabPS.Int.Mo
r384.RNC
WRFD-010503
0.32.RNC
WRFD-010502
Streaming QoS Class
32.64.RNC
WRFD-010502
Streaming QoS Class
144.384.RNC
WRFD-010502
Streaming QoS Class
64.144.RNC
WRFD-010502
Streaming QoS Class
VS.RAB.AttEstabPS.Str.Mo
r384
WRFD-010502
Streaming QoS Class

662
BSC6900 UMTS
Counters Related to the Number of Successful PS RAB Setups for Different

Maximum Downlink Bit Rates
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67174832
VS.RAB.SuccEstabPS.Conv
.0.32.RNC
Conversational RAB
(Max DL Bit Rate in [0,32]
kbit/s)
67174844
0.32.RNC
Background RAB
kbit/s)
67174847
144.384.RNC
Background RAB
(Max DL Bit Rate in
(144,384]kbit/s)
67174845
32.64.RNC
Background RAB
(Max DL Bit Rate in (32,64]
kbit/s)
67174846
64.144.RNC
Background RAB
kbit/s)
67174833
.Mor32.RNC
Conversational RAB
(Max DL Bit Rate More Than
32kbit/s)
67174838
VS.RAB.SuccEstabPS.Str.
Mor384.RNC
Streaming RAB
384kbit/s)

663
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67174839
VS.RAB.SuccEstabPS.Int.
0.32.RNC
Interactive RAB
kbit/s)
67174842
144.384.RNC
Interactive RAB
(Max DL Bit Rate in
(144,384]kbit/s)
67174840
32.64.RNC
Interactive RAB
kbit/s)
67174841
64.144.RNC
Interactive RAB
kbit/s)
67174843
Mor384.RNC
Interactive RAB
384kbit/s)
67174848
Mor384.RNC
Background RAB
384kbit/s)
67174834
VS.RAB.SuccEstab.PS.Str.
0.32.RNC
Streaming RAB
kbit/s)
67174837
144.384.RNC
Streaming RAB
(Max DL Bit Rate in
(144,384]kbit/s)

664
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67174835
32.64.RNC
Streaming RAB
kbit/s)
67174836
64.144.RNC
Streaming RAB
kbit/s)
Description
These counters provide the number of times that the PS RAB is set up successfully for different
maximum downlink bit rates.The preceding counters comply with section "8.2 RAB
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC receives from
an UE a RADIO BEARER SETUP COMPLETE message about the PS domain, the RNC
measures these items according to types of services and maximum downlink bit rates.
Issue 03 (2015-06-30)

665
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.0.32.RNC
WRFD-010501
0.32.RNC
WRFD-010504
144.384.RNC
WRFD-010504

666
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
32.64.RNC
WRFD-010504
64.144.RNC
WRFD-010504
.Mor32.RNC
WRFD-010501
VS.RAB.SuccEstabPS.Str.
Mor384.RNC
WRFD-010502
Streaming QoS Class
0.32.RNC
WRFD-010503
144.384.RNC
WRFD-010503
32.64.RNC
WRFD-010503
64.144.RNC
WRFD-010503
Mor384.RNC
WRFD-010503
Mor384.RNC
WRFD-010504
0.32.RNC
WRFD-010502
Streaming QoS Class
144.384.RNC
WRFD-010502
Streaming QoS Class
32.64.RNC
WRFD-010502
Streaming QoS Class
64.144.RNC
WRFD-010502
Streaming QoS Class
Counter ID
Counter Name
Counter Description
67199790
VS.RAB.Num.PS.Mean
Mean Number of PS RABs

for RNC
Mean Number of PS RABs

Counters
Issue 03 (2015-06-30)

667
BSC6900 UMTS
Description
This counter provides the average number of PS RABs in the RNC within a measurement period.
Measurement point
The RNC periodically samples (sampling periodicity is 5 seconds) the number of PS RABs. At
the end of the measurement period, the RNC divides the total number of PS RABs by the number
of samples to obtain the average number of PS RABs.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Num.PS.Mean
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Times of PS RAB established successfully with 0kbps for RNC

Counters
Counter ID
Counter Name
Counter Description
67196304
VS.RAB.SuccEstab.PS.
0kbps.RNC
Number of PS RABs
Established Successfully
with 0 kbit/s for RNC
Description
This counter provides the number of times that a UE accesses the network successfully through
the 0 Kbit/s RAB in the RNC during the procedures of RAB establishment, RAB modification,
Cell update, incoming inter-RAT handover, relocation (UE involved), and hard handover.This
counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

668
BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in Figure 1. During a RAB setup procedure,
when the RNC receives a RADIO BEARER SETUP COMPLETE message from the 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 Figure 2. During a RAB modification

procedure, when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE
message from the UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Figure 1-307 RAB modification procedure
The measurement is triggered at point A as shown in Figure 3. During a cell update procedure,
when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message
from the UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Issue 03 (2015-06-30)

669
BSC6900 UMTS
Figure 1-308 Cell update procedure
The measurement is triggered at point A as shown in Figure 4. During a relocation (UE involved)
procedure, when the RNC sends a RELOCATION COMPLETE message to the CN, it measures
this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Figure 1-309 Relocation (UE involved) procedure
The measurement is triggered at point A as shown in Figure 5. During a hard handover procedure,
when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message from the UE, it measures this counter in the RNC if the rate of the RAB is 0 Kbit/s.
Issue 03 (2015-06-30)

670
BSC6900 UMTS
Figure 1-310 Hard handover procedure
The measurement is triggered at point D as shown in Figure 6. During an incoming inter-RAT

handover procedure, when the target radio network controller (TRNC) sends a RELOCATION
COMPLETE message to the CN, it measures this counter in the TRNC if the rate of the RAB
is 0 Kbit/s.
Figure 1-311 Incoming inter-RAT handover procedure
Issue 03 (2015-06-30)

671
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstab.PS.
0kbps.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Successful RAB Establishments for PS Services

Counters
Counter ID
Counter Name
Counter Description
73394066
RNC

Establishments for PS
Background Services for
RNC
73394067
VS.RAB.SuccEstabPS.Str.R
NC

Streaming Services for RNC
73394068
.RNC

RNC
73394069
VS.RAB.SuccEstabPS.Int.R
NC

Interactive Services for RNC
Description
These counters provide the number of RAB establishments for different PS services in the
RNC.The preceding counters comply with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
Issue 03 (2015-06-30)

672
BSC6900 UMTS
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.
Figure 1-312 PS RAB setup procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
RNC
WRFD-010504

673
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabPS.Str.R
NC
WRFD-010502
Streaming QoS Class
.RNC
WRFD-010501
VS.RAB.SuccEstabPS.Int.R
NC
WRFD-010503
1.10.13 CS RAB Modification Measurement <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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174725
VS.RAB.AttModC
S.Conv.RNC
Number of RAB
Modification
Requests for CS
Conversational
Services for RNC
Earlier than
BSC6900
V900R011
67174726
VS.RAB.AttModC
S.Str.RNC
Number of RAB
Modification
Requests for CS
Streaming Services
for RNC
Earlier than
BSC6900
V900R011
67174728
VS.RAB.SuccMod
CS.Str.RNC
Number of
Successful RAB
Modifications for CS
Streaming Services
for RNC
Earlier than
BSC6900
V900R011

674
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67203800
VS.RAB.ModReqC
S.VP.Fallback.RN
C
Number of VP
Services Fallen Back
to AMR Services for
RNC
Earlier than
BSC6900
V900R011
67174727
VS.RAB.SuccMod
CS.Conv.RNC
Number of
Successful RAB
Conversational
Services for RNC
Earlier than
BSC6900
V900R011
None
Number of CS RAB Modification Requests

Counters
Counter ID
Counter Name
Counter Description
67174725
VS.RAB.AttModCS.Conv.R
NC
Number of RAB
Modification Requests for
CS Conversational Services
for RNC
67174726
VS.RAB.AttModCS.Str.RN
C
Number of RAB
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.The preceding counters comply with section "8.2 RAB Assignment"
in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

675
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AttModCS.Conv.R
NC
WRFD-010501
VS.RAB.AttModCS.Str.RN
C
WRFD-010502
Streaming QoS Class

676
BSC6900 UMTS
Number of VP Services Fallen Back to AMR Services

Counters
Counter ID
Counter Name
Counter Description
67203800
VS.RAB.ModReqCS.VP.Fa
llback.RNC
Number of VP Services
Fallen Back to AMR
Services for RNC
Description
This counter provides the number of times that the RNC triggers the fallback of the VP service
to the AMR service.This counter complies with section "8.2 RAB Assignment" in 3GPP TS
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends to the CN
a RAB MODIFICATION REQUEST message to request that the VP services fall back to AMR
services.
Formula
None
Unit
None
Issue 03 (2015-06-30)

677
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.ModReqCS.VP.Fa
llback.RNC
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306
WRFD-021200

on Service
on Load
HCS (Hierarchical Cell
Structure)
Number of Successful CS RAB Modifications

Counters
Counter ID
Counter Name
Counter Description
67174727
VS.RAB.SuccModCS.Conv.
RNC

RNC
67174728
VS.RAB.SuccModCS.Str.R
NC

Description
These counters provide the number of times that the RAB is modified successfully for CS
services in the RNC based on the service type.The preceding counters comply with section "8.2
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.
Issue 03 (2015-06-30)

678
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccModCS.Conv.
RNC
WRFD-010501
VS.RAB.SuccModCS.Str.R
NC
WRFD-010502
Streaming QoS Class
1.10.14 PS RAB Modification Measurement <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.
Issue 03 (2015-06-30)

679
BSC6900 UMTS
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174793
RAB.AttModPS.Co
nv.RNC
Number of RAB
Modification
Requests for PS
Conversational
Services for RNC
Earlier than
BSC6900
V900R011
67174794
RAB.AttModPS.St
r.RNC
Number of RAB
Modification
Requests for PS
Streaming Services
for RNC
Earlier than
BSC6900
V900R011
67174795
RAB.AttModPS.In
t.RNC
Number of RAB
Modification
Requests for PS
Interactive Services
for RNC
Earlier than
BSC6900
V900R011
67174796
RAB.AttModPS.Bg
rd.RNC
Number of RAB
Modification
Requests for PS
Background
Services for RNC
Earlier than
BSC6900
V900R011
67174798
VS.RAB.SuccMod
PS.Str.RNC
Number of
Successful RAB
Modifications for PS
Streaming Services
for RNC
Earlier than
BSC6900
V900R011
67174797
VS.RAB.SuccMod
PS.Conv.RNC
Number of
Successful RAB
Conversational
Services for RNC
Earlier than
BSC6900
V900R011

680
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67174799
VS.RAB.SuccMod
PS.Int.RNC
Number of
Successful RAB
for RNC
Earlier than
BSC6900
V900R011
67174800
VS.RAB.SuccMod
PS.Bkg.RNC
Number of
Successful RAB
Background
Services for RNC
Earlier than
BSC6900
V900R011
None
Number of PS RAB Modification Requests

Counters
Counter ID
Counter Name
Counter Description
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.The preceding counters comply with section "8.2 RAB Assignment"
in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

681
BSC6900 UMTS
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.
Figure 1-316 PS RAB modification procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
RAB.AttModPS.Conv.RNC
WRFD-010501
RAB.AttModPS.Str.RNC
WRFD-010502
Streaming QoS Class
RAB.AttModPS.Int.RNC
WRFD-010503
RAB.AttModPS.Bgrd.RNC
WRFD-010504

682
BSC6900 UMTS
Number of Successful PS RAB Modifications

Counters
Counter ID
Counter Name
Counter Description
67174797
VS.RAB.SuccModPS.Conv.
RNC

RNC
67174798
VS.RAB.SuccModPS.Str.R
NC

67174799
VS.RAB.SuccModPS.Int.R
NC

67174800
VS.RAB.SuccModPS.Bkg.
RNC

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.The preceding counters comply with section "8.2
Measurement point
CN a RAB ASSIGNMENT RESPONSE message after receiving from the UE a RADIO
BEARER RECONFIGURATION COMPLETE message, it measures this counter based on the
service type if the RAB is for PS services.
Issue 03 (2015-06-30)

683
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.SuccModPS.Conv.
RNC
WRFD-010501
VS.RAB.SuccModPS.Str.R
NC
WRFD-010502
Streaming QoS Class
VS.RAB.SuccModPS.Int.R
NC
WRFD-010503
VS.RAB.SuccModPS.Bkg.
RNC
WRFD-010504

684
BSC6900 UMTS
1.10.15 Multi-RAB Service Measurement <per RNC>

(RAB.MultiRab.RNC)
Overview
Multi-RAB measurement includes:
Measurement of the number of UEs with multiple RABs.
Multiple RABs can be multiple CS domain RABs, multiple PS domain RABs or the
combinations of CS domain and PS domain RABs. The combinations of RABs can be denoted
by abbreviations. For example:
1CS+1PS indicates that there are concurrently one CS domain RAB and one PS domain RAB.
1CS+2PS indicates that there are concurrently one CS domain RAB and two PS domain RABs.
2CS indicates that there are concurrently two CS domain RABs.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67199688
VS.MultRAB.0CS.
2PS.RNC
Number of UEs with

2PS RABs for RNC
Earlier than
BSC6900
V900R011
67199684
VS.MultRAB.
1CS1PS.RNC
Number of UEs with

1CS+1PS RABs for
RNC
Earlier than
BSC6900
V900R011
67199685
VS.MultRAB.
1CS2PS.RNC
Number of UEs with

1CS+2PS RABs for
RNC
Earlier than
BSC6900
V900R011
67199690
VS.MultRAB.
0CS3PS.RNC
Number of UEs with

0CS+3PS RABs for
RNC
Earlier than
BSC6900
V900R011
67199695
VS.MultRAB.
1CS3PS.RNC
Number of UEs with

1CS+3PS RABs for
RNC
Earlier than
BSC6900
V900R011
67204757
VS.MultRAB.
0CS4PS.RNC
Number of UEs with

0CS+4PS RABs for
RNC
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

685
BSC6900 UMTS
Mean Number of UEs with Multi-RABs in RNC

Counters
Counter ID
Counter Name
Counter Description
67199688
VS.MultRAB.0CS.
2PS.RNC
Number of UEs with 2PS

RABs for RNC
67199684
VS.MultRAB.1CS1PS.RNC
Number of UEs with 1CS

+1PS RABs for RNC
67199685

+2PS RABs for RNC
67199690

+3PS RABs for RNC
67199695

+3PS RABs for RNC
67204757

+4PS RABs for RNC
Description
These measurement item take statistics of the average number of UEs with multi RABs in the
(v10.13.0).
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MultRAB.0CS.
2PS.RNC
WRFD-01061501
Combination of Two PS
Services

686
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-01060902
Combination of One CS
Service and One PS Service
WRFD-01061502
Service and Two PS Services
WRFD-01061503
Combination of Three PS
Services
WRFD-01061504
Service and Three PS
Services
WRFD-01061505
Combination of Four PS
Services
1.10.16 RAB Release Measurement <per RNC>

(RAB.RelAbnormal.RNC)
Overview
The RAB release can be classified into the following types:
1) The RAB release initiated by the RNC. When the RNC detects that the UE has no data to
transmit for a long period or the RNC is faulty (for example, the SRB resets or the AAL2 link
on the Iu interface is faulty), the RNC sends to the CN a RAB RELEASE REQUEST message
to release the RAB or an IU RELEASE REQUEST message to release the Iu connection. If the
cause value is "User Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization", the RAB release is considered as normal release; otherwise, the RAB release is
considered as abnormal release. For details, see the middle of the figure.
2) The RAB release initiated by the CN. The RNC initiates the RAB release by sending the RAB
ASSIGNMENT REQUEST message and initiates the Iu connection release by sending the IU
RELEASE COMMAND message. All the RAB releases initiated by the CN are considered as
normal releases. For details, see the left part of the figure.
3) The RAB release initiated by the UE. The UE initiates the RAB release by sending the
SIGNALING CONNECTION RELEASE INDICATION message. According to the domain
information in the message, the RNC sends an IU RELEASE REQUEST message to the CN
node (SGSN or MSC) to release the Iu connection. After the Iu connection is released, the RNC
initiates the RRC release if no Iu connection exists in another domain. All the RAB releases
initiated by the UE are considered as normal releases. For details, see the right part of the figure.
Note: If the Iu interface is reset, released services will be regarded as being normally released.
The sub procedures mentioned in figure 1 are as following.
Issue 03 (2015-06-30)

687
BSC6900 UMTS
Figure 1-318 Flow chart of Drop
Issue 03 (2015-06-30)

688
BSC6900 UMTS
Figure 1-319 Sub flow chart of Drop
Issue 03 (2015-06-30)
Measurement points
Description
VS.RAB.AbnormRel.CS.RNC,
VS.RAB.AbnormRel.CS.RF.RNC,
VS.RAB.AbnormRel.AMR.RNC,
VS.RAB.AbnormRel.CS64.RNC
VS.RAB.NormRel.CS.RNC,
VS.RAB.NormRel.CS.UEGen.RNC,
VS.RAB.NormRel.VPLimit.RNC

689
BSC6900 UMTS
Measurement points
Description
VS.RAB.NormRel.PS.RNC,
VS.RAB.NormRel.PS.UEGen.RNC,
VS.RAB.NormRel.PS.0kbps.Timeout.RNC
VS.RAB.AbnormRel.PS.RNC,
VS.RAB.AbnormRel.PS.RF.RNC
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174954
VS.RAB.AbnormR
el.CS.RF.RNC
Number of CS RABs
Abnormally
Released due to RF
cause for RNC
Earlier than
BSC6900
V900R011
67174955
VS.RAB.AbnormR
el.PS.RF.RNC
Number of PS RABs
Abnormally
Released due to RF
cause for RNC
Earlier than
BSC6900
V900R011
67174963
VS.RAB.AbnormR
el.CS.RNC
Number of CS RABs
Abnormally
Released for RNC
Earlier than
BSC6900
V900R011
67174964
VS.RAB.AbnormR
el.PS.RNC
Number of PS RABs
Abnormally
Released for RNC
Earlier than
BSC6900
V900R011
67174965
VS.RAB.NormRel.
CS.RNC
Number of CS RABs
Normally Released
for RNC
Earlier than
BSC6900
V900R011
67174966
VS.RAB.NormRel.
PS.RNC
Number of PS RABs
Normally Released
for RNC
Earlier than
BSC6900
V900R011
67190454
VS.RAB.NormRel.
CS.UEGen.RNC
Number of CS RABs
Normally Released
for RNC (UE
Generated Signaling
Connection Release)
Earlier than
BSC6900
V900R011
67190455
VS.RAB.NormRel.
PS.UEGen.RNC
Number of PS RABs
Normally Released
for RNC (UE
Generated Signaling
Connection Release)
Earlier than
BSC6900
V900R011

690
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67174951
VS.RAB.AbnormR
el.AMR.RNC
Number of CS RABs
Abnormally
Released for RNC
(AMR)
Earlier than
BSC6900
V900R011
67174952
VS.RAB.AbnormR
el.CS64.RNC
Number of CS RABs
Abnormally
Released for RNC
(64kbit/s
Conversational
Services)
Earlier than
BSC6900
V900R011
67196236
VS.RAB.NormRel.
VPLimit.RNC
Number of 64kbit/s
CS RABs Normally
Released for RNC
Due to 64kbit/s CS
Service Forbiddance
in Target Cell
Earlier than
BSC6900
V900R011
67196305
VS.RAB.NormRel.
PS.
0kbps.Timeout.RN
C
Number of PS RABs
of 0 kbit/s Released
for Failed to Rate up
for RNC
Earlier than
BSC6900
V900R011
Counter
Sub Counter
VS.RAB.NormRel.PS.RNC
VS.RAB.NormRel.PS.0kbps.Timeout.RNC
VS.RAB.NormRel.PS.UEGen.RNC
VS.RAB.AbnormRel.PS.RNC
VS.RAB.AbnormRel.PS.RF.RNC
VS.RAB.NormRel.CS.RNC
VS.RAB.NormRel.CS.UEGen.RNC
VS.RAB.AbnormRel.CS.RNC
VS.RAB.AbnormRel.AMR.RNC
VS.RAB.AbnormRel.CS64.RNC
VS.RAB.AbnormRel.CS.RNC
Issue 03 (2015-06-30)
VS.RAB.AbnormRel.CS.RF.RNC

691
BSC6900 UMTS
Number of RABs Abnormally Released for RNC

Counters
Counter ID
Counter Name
Counter Description
67174963
VS.RAB.AbnormRel.CS.R
NC
Number of CS RABs
Abnormally Released for
RNC
67174964
VS.RAB.AbnormRel.PS.RN
C
Number of PS RABs
RNC
Description
These counters provide the number of RABs abnormally released in the RNC according to the
domain types.The preceding counters comply with section "8.2 RAB Assignment" ,"8.3 RAB
Release Request","8.4 Iu Release Request" and "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

692
BSC6900 UMTS
As shown in point A of the figure, when an exception occurs, the RNC sends the CN a RAB
As shown in point A of the figure, when an exception occurs, the RNC sends the CN an IU
Issue 03 (2015-06-30)

693
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.CS.R
NC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.PS.RN
C
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

694
BSC6900 UMTS
Number of Released RABs due to RF cause

Counters
Counter ID
Counter Name
Counter Description
67174954
.RNC
Number of CS RABs
Abnormally Released due to
RF cause for RNC
67174955
.RNC
Number of PS RABs
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.The preceding counters comply with section "8.2 RAB Assignment" ,"8.3 RAB
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.
Issue 03 (2015-06-30)

695
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.
Issue 03 (2015-06-30)

696
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

697
BSC6900 UMTS
Number of Abnormally Released CS RABs

Counters
Counter ID
Counter Name
Counter Description
67174951
RNC
Number of CS RABs
RNC (AMR)
67174952
RNC
Number of CS RABs
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.The preceding counters comply with section "8.2 RAB
3GPP TS 25.413 (v10.10.0).
Measurement point
Connection Release", reference to 3GPP TS 25.413), the RNC measures the items by the types
of services.
Issue 03 (2015-06-30)

698
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.
Issue 03 (2015-06-30)

699
BSC6900 UMTS
Release", reference to 3GPP TS 25.413), the RNC measures the items by the types of services.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
RNC
WRFD-010501
RNC
WRFD-010501

700
BSC6900 UMTS
Number of Normally Released RABs

Counters
Counter ID
Counter Name
Counter Description
67174965
Number of CS RABs
Normally Released for RNC
67174966
Number of PS RABs
67196236
VS.RAB.NormRel.VPLimit.
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.The preceding counters comply with section "8.2 RAB Assignment" ,"8.3
RAB Release Request","8.4 Iu Release Request" and "8.5 Iu Release" in 3GPP TS 25.413
(v10.10.0).
Counter Name
Description
Number of normally released CS VP RABs

triggered by RNC(with cause of "Network
Optimization") because VP is forbidden in
target cell
Measurement point
Optimization" or "UE Generated Signalling Connection Release", the RNC measures these items
by the CN domains.
Issue 03 (2015-06-30)

701
BSC6900 UMTS
Signalling Connection Release" ,the RNC measures these items by the CN domains.
Issue 03 (2015-06-30)

702
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.VPLimit.
RNC
WRFD-020130
Videophone Service
Restriction
Number of Released RABs Triggered by RNC Due to UE Signaling Connection

Release
Counters
Counter ID
Counter Name
Counter Description
67190454
VS.RAB.NormRel.CS.UEG
en.RNC
Number of CS RABs
(UE Generated Signaling
Connection Release)
67190455
VS.RAB.NormRel.PS.UEG
en.RNC
Number of PS RABs
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.The preceding counters
Issue 03 (2015-06-30)

703
BSC6900 UMTS
comply with section "8.4 Iu Release Request" and "8.5 Iu Release" in 3GPP TS 25.413
(v10.10.0).
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.CS.UEG
en.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.PS.UEG
en.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

704
BSC6900 UMTS
Times of PS RAB of 0kbps released for failing to rate up before timer expiry
Counters
Counter ID
Counter Name
Counter Description
67196305
VS.RAB.NormRel.PS.
0kbps.Timeout.RNC
Number of PS RABs of 0
kbit/s Released for Failed to
Rate up for RNC
Description
This measurement item provides the times of releasing RAB of 0kbps for failing to rate up before
timer expiry in RNC level.This counter complies with section "8.2 RAB Assignment" ,"8.3 RAB
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.
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.
Issue 03 (2015-06-30)

705
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.PS.
0kbps.Timeout.RNC
WRFD-021101
Dynamic Channel
Configuration Control
(DCCC)

706
BSC6900 UMTS
1.10.17 CS RAB Release Measurement <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
Counter ID
Counter Name
Counter
Description
Original Release
67192101
VS.RAB.AttRelCS.
RNC
Number of CS RAB
Release Attempts for
RNC
BSC6900
V900R012
67192102
VS.RAB.SuccRelC
S.RNC
Number of
Successful CS RAB
Releases for RNC
Earlier than
BSC6900
V900R011
None
Number of CS RABs Requested to Release

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

707
BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from
the CN a RAB ASSIGNMENT REQUEST message indicating that a CS RAB needs to be
released. In this case, this counter is measured in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AttRelCS.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

708
BSC6900 UMTS
Number of Successful CS RAB Releases

Counters
Counter ID
Counter Name
Counter Description
67192102
VS.RAB.SuccRelCS.RNC
RAB Releases for RNC
Description
This counter provides the number of times that a RAB for CS services is released successfully
in the RNC.This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends to the CN
a RAB ASSIGNMENT RESPONSE message indicating that the RAB release succeeds and the
RAB is for CS services.
Issue 03 (2015-06-30)

709
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccRelCS.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.10.18 PS RAB Release Measurement <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
Counter ID
Counter Name
Counter
Description
Original Release
67192104
VS.RAB.SuccRelP
S.RNC
Number of
Successful PS RAB
Releases for RNC
Earlier than
BSC6900
V900R011
73394107
VS.RAB.AttRelPS.
RNC
Number of PS RAB
RNC
BSC6900
V900R012
None
Issue 03 (2015-06-30)

710
BSC6900 UMTS
Number of Successful PS RAB Releases

Counters
Counter ID
Counter Name
Counter Description
67192104
VS.RAB.SuccRelPS.RNC
RAB Releases for RNC
Description
This counter provides the number of times that a RAB for PS services is released successfully
in the RNC.This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends to the CN
a RAB ASSIGNMENT RESPONSE message indicating that the RAB release succeeds and the
RAB is for PS services.
Issue 03 (2015-06-30)

711
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccRelPS.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RABs Requested to Release

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

712
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttRelPS.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.10.19 RB Procedure Measurement <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
Issue 03 (2015-06-30)

713
BSC6900 UMTS
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202577
VS.RB.PS.Conv.D
L.8.RNC
Average Number of
RBs for PS R99
Conversational
Services with DL
Rate of 8 Kbit/s for
RNC
Earlier than
BSC6900
V900R011
67202580
VS.RB.PS.Conv.D
L.16.RNC
Average Number of
RBs for PS R99
Conversational
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202583
VS.RB.PS.Conv.D
L.32.RNC
Average Number of
RBs for PS R99
Conversational
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202586
VS.RB.PS.Conv.D
L.64.RNC
Average Number of
RBs for PS R99
Conversational
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202589
VS.RB.PS.Conv.U
L.8.RNC
Average Number of
RBs for PS R99
Conversational
Services with UL
RNC
Earlier than
BSC6900
V900R011

714
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202592
VS.RB.PS.Conv.U
L.16.RNC
Average Number of
RBs for PS R99
Conversational
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202595
VS.RB.PS.Conv.U
L.32.RNC
Average Number of
RBs for PS R99
Conversational
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202598
VS.RB.PS.Conv.U
L.64.RNC
Average Number of
RBs for PS R99
Conversational
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202604
VS.RB.PS.Str.DL.
144.RNC
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 144
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202607
VS.RB.PS.Str.DL.
128.RNC
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 128
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202610
VS.RB.PS.Str.DL.
64.RNC
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 64
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202613
VS.RB.PS.Str.DL.
32.RNC
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 32
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202616
VS.RB.PS.Str.DL.
16.RNC
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 16
Kbit/s for RNC
Earlier than
BSC6900
V900R011

715
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202619
VS.RB.PS.Str.DL.
8.RNC
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 8
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202625
VS.RB.PS.Str.UL.
144.RNC
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 144
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202628
VS.RB.PS.Str.UL.
128.RNC
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 128
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202631
VS.RB.PS.Str.UL.
64.RNC
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 64
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202634
VS.RB.PS.Str.UL.
32.RNC
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 32
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202637
VS.RB.PS.Str.UL.
16.RNC
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 16
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202640
VS.RB.PS.Str.UL.
8.RNC
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 8
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202643
VS.RB.PS.Int.DL.
384.RNC
Average Number of
RBs for PS R99
with DL Rate of 384
Kbit/s for RNC
Earlier than
BSC6900
V900R011

716
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202646
VS.RB.PS.Int.DL.
256.RNC
Average Number of
RBs for PS R99
with DL Rate of 256
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202649
VS.RB.PS.Int.DL.
144.RNC
Average Number of
RBs for PS R99
with DL Rate of 144
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202652
VS.RB.PS.Int.DL.
128.RNC
Average Number of
RBs for PS R99
with DL Rate of 128
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202655
VS.RB.PS.Int.DL.
64.RNC
Average Number of
RBs for PS R99
with DL Rate of 64
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202658
VS.RB.PS.Int.DL.
32.RNC
Average Number of
RBs for PS R99
with DL Rate of 32
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202661
VS.RB.PS.Int.DL.
16.RNC
Average Number of
RBs for PS R99
with DL Rate of 16
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202664
VS.RB.PS.Int.DL.
8.RNC
Average Number of
RBs for PS R99
with DL Rate of 8
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202667
VS.RB.PS.Int.UL.
384.RNC
Average Number of
RBs for PS R99
with UL Rate of 384
Kbit/s for RNC
Earlier than
BSC6900
V900R011

717
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202670
VS.RB.PS.Int.UL.
256.RNC
Average Number of
RBs for PS R99
with UL Rate of 256
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202673
VS.RB.PS.Int.UL.
144.RNC
Average Number of
RBs for PS R99
with UL Rate of 144
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202676
VS.RB.PS.Int.UL.
128.RNC
Average Number of
RBs for PS R99
with UL Rate of 128
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202679
VS.RB.PS.Int.UL.
64.RNC
Average Number of
RBs for PS R99
with UL Rate of 64
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202682
VS.RB.PS.Int.UL.
32.RNC
Average Number of
RBs for PS R99
with UL Rate of 32
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202685
VS.RB.PS.Int.UL.
16.RNC
Average Number of
RBs for PS R99
with UL Rate of 16
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202688
VS.RB.PS.Int.UL.
8.RNC
Average Number of
RBs for PS R99
with UL Rate of 8
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202691
VS.RB.PS.Bkg.DL.
384.RNC
Average Number of
RBs for PS R99
Background
Services with DL
RNC
Earlier than
BSC6900
V900R011

718
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202694
VS.RB.PS.Bkg.DL.
256.RNC
Average Number of
RBs for PS R99
Background
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202697
VS.RB.PS.Bkg.DL.
144.RNC
Average Number of
RBs for PS R99
Background
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202700
VS.RB.PS.Bkg.DL.
128.RNC
Average Number of
RBs for PS R99
Background
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202703
VS.RB.PS.Bkg.DL.
64.RNC
Average Number of
RBs for PS R99
Background
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202706
VS.RB.PS.Bkg.DL.
32.RNC
Average Number of
RBs for PS R99
Background
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202709
VS.RB.PS.Bkg.DL.
16.RNC
Average Number of
RBs for PS R99
Background
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202712
VS.RB.PS.Bkg.DL.
8.RNC
Average Number of
RBs for PS R99
Background
Services with DL
RNC
Earlier than
BSC6900
V900R011

719
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202715
VS.RB.PS.Bkg.UL.
384.RNC
Average Number of
RBs for PS R99
Background
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202718
VS.RB.PS.Bkg.UL.
256.RNC
Average Number of
RBs for PS R99
Background
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202721
VS.RB.PS.Bkg.UL.
144.RNC
Average Number of
RBs for PS R99
Background
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202724
VS.RB.PS.Bkg.UL.
128.RNC
Average Number of
RBs for PS R99
Background
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202727
VS.RB.PS.Bkg.UL.
64.RNC
Average Number of
RBs for PS R99
Background
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202730
VS.RB.PS.Bkg.UL.
32.RNC
Average Number of
RBs for PS R99
Background
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202733
VS.RB.PS.Bkg.UL.
16.RNC
Average Number of
RBs for PS R99
Background
Services with UL
RNC
Earlier than
BSC6900
V900R011

720
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202736
VS.RB.PS.Bkg.UL.
8.RNC
Average Number of
RBs for PS R99
Background
Services with UL
RNC
Earlier than
BSC6900
V900R011
67202739
VS.RB.CS.Str.DL.
57.6.RNC
Average Number of
RBs for CS
Streaming Services
with DL Rate of 57.6
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202748
VS.RB.CS.Str.UL.
57.6.RNC
Average Number of
RBs for CS
Streaming Services
with UL Rate of 57.6
Kbit/s for RNC
Earlier than
BSC6900
V900R011
67202766
VS.RB.CS.Conv.D
L.64.RNC
Average Number of
RBs for CS
Conversational
Services with DL
RNC
Earlier than
BSC6900
V900R011
67202778
VS.RB.CS.Conv.U
L.64.RNC
Average Number of
RBs for CS
Conversational
Services with UL
RNC
Earlier than
BSC6900
V900R011
67192444
VS.DRD.RB.D2H.
Att.RNC
Number of DCH-toHSDPA Directed

Retry Attempts for
RNC
Earlier than
BSC6900
V900R011
67192445
VS.DRD.RB.D2H.S
ucc.RNC
Number of
Successful DCH-toHSDPA Directed
Retry for RNC
Earlier than
BSC6900
V900R011
67202601
VS.RB.PS.Str.DL.
256.384.RNC
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 256
Kbit/s or 384 Kbit/s
for RNC
Earlier than
BSC6900
V900R011

721
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202622
VS.RB.PS.Str.UL.
256.384.RNC
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 256
for RNC
Earlier than
BSC6900
V900R011
67204798
VS.RB.PS.Conv.D
L.38.8.RNC
Average Number of
RBs for PS R99
Conversational
Services with DL
Rate of 38.8 Kbit/s
for RNC
Earlier than
BSC6900
V900R011
67204799
VS.RB.PS.Conv.D
L.39.2.RNC
Average Number of
RBs for PS R99
Conversational
Services with DL
Rate of 39.2 Kbit/s
for RNC
Earlier than
BSC6900
V900R011
67204800
VS.RB.PS.Conv.D
L.40.RNC
Average Number of
RBs for PS R99
Conversational
Services with DL
RNC
Earlier than
BSC6900
V900R011
67204801
VS.RB.PS.Conv.D
L.42.8.RNC
Average Number of
RBs for PS R99
Conversational
Services with DL
Rate of 42.8 Kbit/s
for RNC
Earlier than
BSC6900
V900R011
67204802
VS.RB.PS.Conv.U
L.38.8.RNC
Average Number of
RBs for PS R99
Conversational
Services with UL
Rate of 38.8 Kbit/s
for RNC
Earlier than
BSC6900
V900R011
67204803
VS.RB.PS.Conv.U
L.39.2.RNC
Average Number of
RBs for PS R99
Conversational
Services with UL
Rate of 39.2 Kbit/s
for RNC
Earlier than
BSC6900
V900R011

722
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204804
VS.RB.PS.Conv.U
L.40.RNC
Average Number of
RBs for PS R99
Conversational
Services with UL
RNC
Earlier than
BSC6900
V900R011
67204805
VS.RB.PS.Conv.U
L.42.8.RNC
Average Number of
RBs for PS R99
Conversational
Services with UL
Rate of 42.8 Kbit/s
for RNC
Earlier than
BSC6900
V900R011
None
Counters Related to the Average Number of RBs for PS R99 Conversational

Services
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
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.
16.RNC

Kbit/s for RNC
67202583
VS.RB.PS.Conv.DL.
32.RNC

Kbit/s for RNC
67202586
VS.RB.PS.Conv.DL.
64.RNC

Kbit/s for RNC

723
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202589
VS.RB.PS.Conv.UL.8.RNC

Services with UL Rate of 8
Kbit/s for RNC
67202592
VS.RB.PS.Conv.UL.
16.RNC

Kbit/s for RNC
67202595
VS.RB.PS.Conv.UL.
32.RNC

Kbit/s for RNC
67202598
VS.RB.PS.Conv.UL.
64.RNC

Kbit/s for RNC
67204798
VS.RB.PS.Conv.DL.
38.8.RNC

Services with DL Rate of
38.8 Kbit/s for RNC
67204799
VS.RB.PS.Conv.DL.
39.2.RNC

39.2 Kbit/s for RNC
67204800
VS.RB.PS.Conv.DL.
40.RNC

Kbit/s for RNC
67204801
VS.RB.PS.Conv.DL.
42.8.RNC

42.8 Kbit/s for RNC
67204802
VS.RB.PS.Conv.UL.
38.8.RNC

Services with UL Rate of
38.8 Kbit/s for RNC
67204803
VS.RB.PS.Conv.UL.
39.2.RNC

39.2 Kbit/s for RNC

724
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67204804
VS.RB.PS.Conv.UL.
40.RNC

Kbit/s for RNC
67204805
VS.RB.PS.Conv.UL.
42.8.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. The preceding counters comply with section "8.2.2
Reconfiguration procedures" in 3GPP TS 25.331 (v12.1.0).
Measurement point
The number of RBs for each type of PS R99 conversational services is sampled periodically
(sampling periodicity is 5 seconds) in the RNC. At the end of the measurement period, the value
of each counter is obtained as follows: dividing the accumulated value of each sampling point
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RB.PS.Conv.DL.8.RNC
WRFD-010501
VS.RB.PS.Conv.DL.
16.RNC
WRFD-010501
VS.RB.PS.Conv.DL.
32.RNC
WRFD-010501
VS.RB.PS.Conv.DL.
64.RNC
WRFD-010501
VS.RB.PS.Conv.UL.8.RNC
WRFD-010501

725
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RB.PS.Conv.UL.
16.RNC
WRFD-010501
VS.RB.PS.Conv.UL.
32.RNC
WRFD-010501
VS.RB.PS.Conv.UL.
64.RNC
WRFD-010501
VS.RB.PS.Conv.DL.
38.8.RNC
WRFD-010501
VS.RB.PS.Conv.DL.
39.2.RNC
WRFD-010501
VS.RB.PS.Conv.DL.
40.RNC
WRFD-010501
VS.RB.PS.Conv.DL.
42.8.RNC
WRFD-010501
VS.RB.PS.Conv.UL.
38.8.RNC
WRFD-010501
VS.RB.PS.Conv.UL.
39.2.RNC
WRFD-010501
VS.RB.PS.Conv.UL.
40.RNC
WRFD-010501
VS.RB.PS.Conv.UL.
42.8.RNC
WRFD-010501
Counters Related to the Average Number of PS R99 Interactive Service RBs

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202643
VS.RB.PS.Int.DL.384.RNC

PS R99 Interactive Services
with DL Rate of 384 Kbit/s
for RNC
67202646

for RNC

726
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202649

for RNC
67202652

for RNC
67202655

with DL Rate of 64 Kbit/s for
RNC
67202658

RNC
67202661

RNC
67202664

RNC
67202667
VS.RB.PS.Int.UL.384.RNC

with UL Rate of 384 Kbit/s
for RNC
67202670

for RNC
67202673

for RNC
67202676

for RNC

727
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67202679

with UL Rate of 64 Kbit/s for
RNC
67202682

RNC
67202685

RNC
67202688

RNC
Description
These counters provide the average number of RBs for PS R99 interactive services in the uplink
or downlink. The preceding counters comply with section "8.2.2 Reconfiguration procedures"
in 3GPP TS 25.331 (v12.1.0).
Measurement point
The number of RBs for each type of PS R99 interactive services is sampled periodically
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010503
WRFD-010503

728
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
Counters Related to the Average Number of PS R99 Backgroud Service RBs

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202691
VS.RB.PS.Bkg.DL.
384.RNC

PS R99 Background Services
for RNC
67202694
VS.RB.PS.Bkg.DL.
256.RNC

for RNC
67202697
VS.RB.PS.Bkg.DL.
144.RNC

for RNC

729
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202700
VS.RB.PS.Bkg.DL.
128.RNC

for RNC
67202703
VS.RB.PS.Bkg.DL.64.RNC

RNC
67202706

RNC
67202709

RNC
67202712

RNC
67202715
VS.RB.PS.Bkg.UL.
384.RNC

for RNC
67202718
VS.RB.PS.Bkg.UL.
256.RNC

for RNC
67202721
VS.RB.PS.Bkg.UL.
144.RNC

for RNC
67202724
VS.RB.PS.Bkg.UL.
128.RNC

for RNC
67202727
VS.RB.PS.Bkg.UL.64.RNC

RNC

730
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67202730

RNC
67202733

RNC
67202736

RNC
Description
These counters provide the average number of RBs for PS R99 background services in the uplink
in 3GPP TS 25.331 (v12.1.0).
Measurement point
The number of RBs for each type of PS R99 backgroud services is sampled periodically
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RB.PS.Bkg.DL.
384.RNC
WRFD-010504
VS.RB.PS.Bkg.DL.
256.RNC
WRFD-010504
VS.RB.PS.Bkg.DL.
144.RNC
WRFD-010504

731
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RB.PS.Bkg.DL.
128.RNC
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
VS.RB.PS.Bkg.UL.
384.RNC
WRFD-010504
VS.RB.PS.Bkg.UL.
256.RNC
WRFD-010504
VS.RB.PS.Bkg.UL.
144.RNC
WRFD-010504
VS.RB.PS.Bkg.UL.
128.RNC
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
Counters Related to the Average Number of CS Streaming Service RBs

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202739
VS.RB.CS.Str.DL.
57.6.RNC

CS Streaming Services with
DL Rate of 57.6 Kbit/s for
RNC
67202748
VS.RB.CS.Str.UL.
57.6.RNC

UL Rate of 57.6 Kbit/s for
RNC

732
BSC6900 UMTS
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. The preceding counters comply with section "8.2.2
Measurement point
The RNC periodically takes a sample (sampling periodicity is 5 seconds) from the number of
RBs in the CS domain at each of the UL and DL rates of the streaming service. At the end of
the measurement period, the RNC divides the accumulated number of RBs at one bit rate by the
number of samples to obtain the mean number of such RBs.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RB.CS.Str.DL.
57.6.RNC
WRFD-010502
Streaming QoS Class
VS.RB.CS.Str.UL.
57.6.RNC
WRFD-010502
Streaming QoS Class
Counters Related to the Average Number of CS Conversational Service RBs

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202766
VS.RB.CS.Conv.DL.
64.RNC

RNC
67202778
VS.RB.CS.Conv.UL.
64.RNC

RNC

733
BSC6900 UMTS
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. The preceding counters comply with section
"8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v12.1.0).
Measurement point
The number of RBs for conversational services are sampled periodically (sampling periodicity
is 5 seconds) in the RNC. At the end of the measurement period, the value of each counter is
obtained as follows: dividing the accumulated value of each sampling point by the number of
sampling times.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RB.CS.Conv.DL.
64.RNC
WRFD-010501
VS.RB.CS.Conv.UL.
64.RNC
WRFD-010501
Number of DCH-to-HSDPA Directed Retry Attempts

Counters
Counter ID
Counter Name
Counter Description
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.
This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v12.1.0).
Issue 03 (2015-06-30)

734
BSC6900 UMTS
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-338 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.
Figure 1-339 RB reconfiguration procedure (successful operation)
Issue 03 (2015-06-30)

735
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RB.D2H.Att.RNC
WRFD-01061112
HSDPA DRD
WRFD-02040001
Intra System Direct Retry
Number of Successful DCH-to-HSDPA Directed Retry

Counters
Counter ID
Counter Name
Counter Description
67192445
VS.DRD.RB.D2H.Succ.RN
C
Number of Successful DCHto-HSDPA Directed Retry

for RNC
Description
This counter provides the number of times that the directed retry from DCH to HSDPA succeeds
in the RNC. This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP
TS 25.331 (v12.1.0).
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.
Issue 03 (2015-06-30)

736
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.RB.D2H.Succ.RN
C
WRFD-01061112
HSDPA DRD
WRFD-02040001

737
BSC6900 UMTS
Counters Related to the Average Number of PS R99 Streaming Service RBs

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202601
VS.RB.PS.Str.DL.
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

for RNC
67202607

for RNC
67202610

RNC
67202613

RNC
67202616

RNC
67202619

RNC
67202625
VS.RB.PS.Str.UL.144.RNC

for RNC
67202628

for RNC

738
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67202631

RNC
67202634

RNC
67202637

RNC
67202640

RNC
67202622
VS.RB.PS.Str.UL.
256.384.RNC

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
in 3GPP TS 25.331 (v12.1.0).
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
Issue 03 (2015-06-30)

739
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RB.PS.Str.DL.
256.384.RNC
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.UL.
256.384.RNC
WRFD-010502
Streaming QoS Class
1.10.20 TRNC Relocation Measurement(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"
Issue 03 (2015-06-30)

740
BSC6900 UMTS
relocation, the TRNC receives the reconfiguration response from the UE after successful
relocation preparation.
The reconfiguration procedure involves the following messages: RADIO BEARER SETUP
COMPLETE , RADIO BEARER RECONFIGURATION COMPLETE , RADIO BEARER
RELEASE COMPLETE , TRANSPORT CHANNEL RECONFIGURATION COMPLETE ,
and PHYSICAL CHANNEL RECONFIGURATION COMPLETE .
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67175893
VS.DRELOC.FailE
xec.Cong
Number of Failed
Relocation
Executions for
TRNC (Resources
Unavailable)
Earlier than
BSC6900
V900R011
67175894
VS.DRELOC.FailE
xec.Unsp
Number of Failed
Relocation
Executions for
TRNC (Protocol
Cause)
Earlier than
BSC6900
V900R011
67190207
VS.DRELOC.FailP
rep.IuRel
Number of Failed
Relocation
Preparations Due to
Reception of IU
Release Command
for TRNC
Earlier than
BSC6900
V900R011
67175881
VS.DRELOC.FailP
rep.NAS
Number of Failed
Relocation
Preparations for
TRNC (NAS Cause)
Earlier than
BSC6900
V900R011
67175879
VS.DRELOC.FailP
rep.RNL
Number of Failed
Relocation
Preparations for
TRNC (Radio
Network Layer
Cause)
Earlier than
BSC6900
V900R011
67175880
VS.DRELOC.FailP
rep.TNL
Number of Failed
Relocation
Preparations for
TRNC (Transport
Layer Cause)
Earlier than
BSC6900
V900R011

741
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190208
VS.TRELOC.AttE
xecUEInvol
Number of
Relocation
Execution Attempts
for TRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67190209
VS.TRELOC.AttE
xecUENotInvol
Number of
Relocation
Execution Attempts
for TRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67190212
VS.TRELOC.SuccExecUENotInvol
Number of
Successful
Relocation
Executions for
TRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67190213
VS.TRELOC.SuccExecUEInvol
Number of
Successful
Relocation
Executions for
TRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67191091
RELOC.AttResAllocUEInvolPS
Number of PS
Relocation Resource
Allocation Attempts
for TRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67191092
RELOC.AttResAllocUENotInvolPS
Number of PS
Relocation Resource
Allocation Attempts
for TRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67191097
RELOC.SuccResAl
locUEInvolPS
Number of
Successful PS
Relocation Resource
Allocations for
TRNC (UE
Involved)
Earlier than
BSC6900
V900R011

742
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191098
RELOC.SuccResAl
locUENotInvolPS
Number of
Successful PS
Relocation Resource
Allocations for
TRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67191099
RELOC.FailResAll
ocUEInvolPS.CiphUnSupp
Number of Failed PS
Relocation
Preparations for
TRNC (UE
Involved)
(Requested
Ciphering and/or
Integrity Protection
Algorithms Not
Supported)
Earlier than
BSC6900
V900R011
67191100
RELOC.FailResAll
ocUENotInvolPS.C
iphUnSupp
Number of Failed PS
Relocation
Preparations for
TRNC (UE Not
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)
Earlier than
BSC6900
V900R011
67191101
RELOC.FailResAll
ocUEInvolPS.ResUnavail
Number of Failed PS
Relocation
Preparations for
TRNC (UE
Involved) (No
Resources
Available)
Earlier than
BSC6900
V900R011
67191102
RELOC.FailResAll
ocUENotInvolPS.R
esUnavail
Number of Failed PS
Relocation
Preparations for
TRNC (UE Not
Involved) (No
Resources
Available)
Earlier than
BSC6900
V900R011

743
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191107
RELOC.AttResAllocUEInvolCS
Number of CS
Relocation Resource
Allocation Attempts
for TRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67191108
RELOC.AttResAllocUENotInvolCS
Number of CS
Relocation Resource
Allocation Attempts
for TRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67191113
RELOC.SuccResAl
locUEInvolCS
Number of
Successful CS
Relocation Resource
Allocations for
TRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67191114
RELOC.SuccResAl
locUENotInvolCS
Number of
Successful CS
Relocation Resource
Allocations for
TRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67191115
RELOC.FailResAll
ocUEInvolCS.CiphUnSupp
Number of Failed CS
Relocation
Preparations for
TRNC (UE
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)
Earlier than
BSC6900
V900R011
67191116
RELOC.FailResAll
ocUENotInvolCS.C
iphUnSupp
Number of Failed CS
Relocation
Preparations for
TRNC (UE Not
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)
Earlier than
BSC6900
V900R011

744
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67191117
RELOC.FailResAll
ocUENotInvolCS.R
esUnavail
Number of Failed CS
Relocation
Preparations for
TRNC (UE Not
Involved) (No
Resources
Available)
Earlier than
BSC6900
V900R011
73423643
VS.DRELOC.FailP
rep.NodeBReHost
Number of Failed
Relocation
Preparations for
TRNC (NodeB
Rehoming)
BSC6900
V900R014
73424478
VS.TRELOC.SuccExecUEInvolCS
Number of
Successful CS
Relocations for
TRNC (UE
Involved)
BSC6900
V900R014
73424479
VS.TRELOC.SuccExecUEInvolPS
Number of
Successful PS
Relocations for
TRNC (UE
Involved)
BSC6900
V900R014
73424480
VS.TRELOC.SuccExecUENotInvolCS
Number of
Successful CS
Relocations for
TRNC (UE Not
Involved)
BSC6900
V900R014
73424481
VS.TRELOC.SuccExecUENotInvolPS
Number of
Successful PS
Relocations for
TRNC (UE Not
Involved)
BSC6900
V900R014
None
Issue 03 (2015-06-30)

745
BSC6900 UMTS
Counters Related to the Number of Failed Relocation Executions for Different

Causes for TRNC
Counters
Counter ID
Counter Name
Counter Description
67175893
VS.DRELOC.FailExec.Con
g
Number of Failed Relocation

Executions for TRNC
(Resources Unavailable)
67175894
VS.DRELOC.FailExec.Uns
p

Executions for TRNC
(Protocol Cause)
Description
These counters provide the number of failed relocation executions in the TRNC according to
different failure causes.The preceding counters comply with section "8.1.4 RRC connection
release" in 3GPP TS 25.331 (v10.13.0) and "8.7 Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
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-342 Failed TRNC relocation execution procedure
Issue 03 (2015-06-30)

746
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRELOC.FailExec.Con
g
WRFD-020605
SRNS Relocation
Introduction Package
VS.DRELOC.FailExec.Uns
p
WRFD-020605
SRNS Relocation
Number of Failed Relocation Resource Allocations Due to Reception of IU Release

Command for TRNC
Counters
Counter ID
Counter Name
Counter Description
67190207
VS.DRELOC.FailPrep.IuRel

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.This counter complies with
section "8.7 Relocation Resource Allocation" and "8.5 Iu Release" in 3GPP TS 25.413
(v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the following figure. When the TRNC
receives an IU RELEASE COMMAND message from the CN during the relocation preparation,
the relocation preparation fails. In this case, the TRNC measures the counter.
Issue 03 (2015-06-30)

747
BSC6900 UMTS
Figure 1-343 Failed resource allocation for TRNC relocation due to reception of IU release
command
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRELOC.FailPrep.IuRel
WRFD-020605
SRNS Relocation
Number of Failed Relocation Resource Allocations for TRNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67175881
VS.DRELOC.FailPrep.NAS

Preparations for TRNC
(NAS Cause)

748
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67175879
VS.DRELOC.FailPrep.RNL

(Radio Network Layer
Cause)
67175880
VS.DRELOC.FailPrep.TNL

(Transport Layer Cause)
67191099
RELOC.FailResAllocUEInv
olPS.CiphUnSupp
Number of Failed PS
Relocation Preparations for
TRNC (UE Involved)
(Requested Ciphering and/or
Algorithms Not Supported)
67191100
RELOC.FailResAllocUENo
tInvolPS.CiphUnSupp
Number of Failed PS
TRNC (UE Not Involved)
67191101
olPS.ResUnavail
Number of Failed PS
TRNC (UE Involved) (No
Resources Available)
67191102
tInvolPS.ResUnavail
Number of Failed PS
(No Resources Available)
67191115
olCS.CiphUnSupp
Number of Failed CS
TRNC (UE Involved)
67191116
tInvolCS.CiphUnSupp
Number of Failed CS
67191117
tInvolCS.ResUnavail
Number of Failed CS

749
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73423643
VS.DRELOC.FailPrep.NodeBReHost

(NodeB Rehoming)
Description
These counters provide the numbers of failed relocation resource allocations for the TRNC based
on failure causes.The preceding counters comply with section "8.7 Relocation Resource
Allocation" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure. During a relocation preparation,
when the relocation resource allocation fails, the TRNC sends a RELOCATION FAILURE
message to the CN. In this case, the TRNC measures the related counter based on failure causes.
Figure 1-344 Failed resource allocation procedure for TRNC relocation
Formula
None
Unit
None
Issue 03 (2015-06-30)

750
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.DRELOC.FailPrep.NAS
WRFD-020605
SRNS Relocation
VS.DRELOC.FailPrep.RNL
WRFD-020605
SRNS Relocation
VS.DRELOC.FailPrep.TNL
WRFD-020605
SRNS Relocation
olPS.CiphUnSupp
WRFD-020605
SRNS Relocation
tInvolPS.CiphUnSupp
WRFD-020605
SRNS Relocation
olPS.ResUnavail
WRFD-020605
SRNS Relocation
tInvolPS.ResUnavail
WRFD-020605
SRNS Relocation
olCS.CiphUnSupp
WRFD-020605
SRNS Relocation
tInvolCS.CiphUnSupp
WRFD-020605
SRNS Relocation
tInvolCS.ResUnavail
WRFD-020605
SRNS Relocation
VS.DRELOC.FailPrep.NodeBReHost
WRFD-040202
RNC Node Redundancy
WRFD-020605
SRNS Relocation
Number of Reconfiguration Completions During Relocation for TRNC (UE

Involved)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190208
VS.TRELOC.AttExecUEInvol
Number of Relocation
Execution Attempts for
TRNC (UE Involved)

751
BSC6900 UMTS
Description
This counter provides the number of TRNC reconfiguration completions during the relocation
(UE involved).This counter complies with section "8.9 Relocation Complete" in 3GPP TS
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the following figure, taking the RADIO
BEARER RECONFIGURATION COMPLETE message as an example. During the relocation
(UE involved), the TRNC measures the counter when receiving a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE.
Figure 1-345 Reconfiguration procedure during the TRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.TRELOC.AttExecUEInvol
WRFD-020605
SRNS Relocation

752
BSC6900 UMTS
Number of Relocation Execution Attempts for TRNC (UE Not Involved)

Counters
Counter ID
Counter Name
Counter Description
67190209
VS.TRELOC.AttExecUENotInvol
Description
This counter provides the number of TRNC relocation execution attempts during the relocation
(UE not involved).This counter complies with section "8.9 Relocation Complete" in 3GPP TS
25.413 (v10.10.0).
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-346 TRNC relocation execution procedure (UE not involved)
Formula
None
Issue 03 (2015-06-30)

753
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.TRELOC.AttExecUENotInvol
WRFD-020605
SRNS Relocation
Number of Successful Relocation Executions for TRNC (UE Not Involved)

Counters
Counter ID
Counter Name
Counter Description
67190212
Relocation Executions for
Description
These counters provide the number of successful TRNC relocation executions during the
relocation (UE not involved).This counter complies with section "8.9 Relocation Complete" in
3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. When the TRNC
relocation is complete, the TRNC sends a RELOCATION COMPLETE message to the CN. In
this case, the TRNC measures the related counters according to different relocation types. If the
UE connects to both the CS domain and the PS domain at the same time, the related counters
are increased by one respectively every time the TRNC sends a RELOCATION COMPLETE
message to the CNs in the CS domain and PS domain.
Issue 03 (2015-06-30)

754
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020605
SRNS Relocation
Number of Successful Relocation Executions for TRNC (UE Involved)

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190213
TRNC (UE Involved)

755
BSC6900 UMTS
Description
These counters provide the number of successful TRNC relocation executions during the
relocation (UE involved).This counter complies with section "8.9 Relocation Complete" in 3GPP
TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. When the TRNC
relocation is complete, the TRNC sends a RELOCATION COMPLETE message to the CN. In
this case, the TRNC measures the related counters according to different relocation types. If the
UE connects to both the CS domain and the PS domain at the same time, the related counters
are increased by one respectively every time the TRNC sends a RELOCATION COMPLETE
message to the CNs in the CS domain and PS domain.
Figure 1-348 Reconfiguration procedure during the TRNC relocation (UE involved)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020605
SRNS Relocation

756
BSC6900 UMTS
Number of Relocation Resource Allocation Attempts for TRNC

Counters
Counter ID
Counter Name
Counter Description
67191091
Number of PS Relocation
Resource Allocation
Attempts for TRNC (UE
Involved)
67191092
Resource Allocation
Attempts for TRNC (UE Not
Involved)
67191107
Number of CS Relocation
Resource Allocation
Attempts for TRNC (UE
Involved)
67191108
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.The preceding counters comply with section "8.7 Relocation
Measurement point
The measurement is triggered at point A as shown in the figure. When the TRNC receives a
RELOCATION REQUEST message from the CS domain or PS domain in the CN, the TRNC
measures the related counter based on relocation types.
Issue 03 (2015-06-30)

757
BSC6900 UMTS
Figure 1-349 TRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation

758
BSC6900 UMTS
Number of Successful Relocation Resource Allocations for TRNC

Counters
Counter ID
Counter Name
Counter Description
67191097
RELOC.SuccResAllocUEInvolPS
Relocation Resource
Allocations for TRNC (UE
Involved)
67191098
RELOC.SuccResAllocUENotInvolPS
Relocation Resource
Not Involved)
67191113
RELOC.SuccResAllocUEInvolCS
Relocation Resource
Involved)
67191114
RELOC.SuccResAllocUENotInvolCS
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.The preceding counters comply with section
"8.7 Relocation Resource Allocation" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure. When the relocation resource
allocation is complete, the TRNC sends a RELOCATION REQUEST ACKNOWLEDGE
message to the CS domain or PS domain in the CN. In this case, the TRNC measures the related
counter based on relocation types.
Issue 03 (2015-06-30)

759
BSC6900 UMTS
Figure 1-350 TRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
RELOC.SuccResAllocUEInvolPS
WRFD-020605
SRNS Relocation
RELOC.SuccResAllocUENotInvolPS
WRFD-020605
SRNS Relocation
RELOC.SuccResAllocUEInvolCS
WRFD-020605
SRNS Relocation
RELOC.SuccResAllocUENotInvolCS
WRFD-020605
SRNS Relocation

760
BSC6900 UMTS
Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE

Involved)
Counters
Counter ID
Counter Name
Counter Description
73424478
Relocations for TRNC (UE
Involved)
73424479
Involved)
Description
These counters measure the number of successful target RNC (TRNC) relocations.The preceding
counters comply with section "8.9 Relocation Complete" in 3GPP TS 25.413 (v10.10.0).
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-351 Reconfiguration during a TRNC relocation (UE Involved)
Issue 03 (2015-06-30)

761
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
Number of Successful TRNC Relocations in the CS Domain and PS Domain (UE

Not Involved)
Counters
Counter ID
Counter Name
Counter Description
73424480
Not Involved)
73424481
Not Involved)
Description
These counters measure the number of successful target RNC (TRNC) relocations.The preceding
counters comply with section "8.9 Relocation Complete" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B shown in figure 1 when the TRNC sends a
RELOCATION COMPLETE message to the CN upon completing a relocation. In this case,
these counters are measured based on the service type.
Issue 03 (2015-06-30)

762
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
1.10.21 SRNC Relocation Measurement(Relocation.Srnc.RNC)

Overview
SRNC relocation involves two stages: SRNC relocation preparation and SRNC relocation
execution.
SRNC relocation preparation involves the following messages: RELOCATION REQUIRED
message, RELOCATION COMMAND message, and RELOCATION FAILURE message.
Issue 03 (2015-06-30)

763
BSC6900 UMTS
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190184
VS.RELOC.AttPre
pUEInvolCS.TimeCrit
Number of CS
Relocation
Preparation
Attempts for SRNC
(UE Involved) (Time
Critical Relocation)
Earlier than
BSC6900
V900R011
67190185
VS.RELOC.AttPre
pUEInvolCS.RF
Number of CS
Relocation
Preparation
Attempts for SRNC
(UE Involved)
(Relocation
Desirable for Radio
Reasons)
Earlier than
BSC6900
V900R011
67190186
RELOC.AttPrepUEInvolCS
Number of CS
Relocation
Preparation
Attempts for SRNC
(UE Involved)
Earlier than
BSC6900
V900R011

764
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190187
VS.RELOC.SuccPr
epUEInvolCS.Time
Crit
Number of
Successful CS
Relocation
Preparations for
SRNC (UE
Involved) (Time
Earlier than
BSC6900
V900R011
67190188
VS.RELOC.SuccPr
epUEInvolCS.RF
Number of
Successful CS
Relocation
Preparations for
SRNC (UE
Involved)
(Relocation
Desirable for Radio
Reasons)
Earlier than
BSC6900
V900R011
67190189
RELOC.SuccPrepUEInvolCS
Number of
Successful CS
Relocation
Preparations for
SRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67190192
RELOC.FailPrepU
EInvolCS.CiphUnSupp
Number of Failed CS
Relocation
Preparations for
SRNC (UE
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)
Earlier than
BSC6900
V900R011
67175739
RELOC.FailPrepU
EInvolCS.TrelocprepExp
Number of Failed CS
Relocation
Preparations for
SRNC (UE
Involved)
(Trelocprep Expiry)
Earlier than
BSC6900
V900R011

765
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67175740
RELOC.FailPrepU
EInvolCS.TgtSysUnsupp
Number of Failed CS
Relocation
Preparations for
SRNC (UE
Involved)
(Relocation Not
Supported in Target
RNC or Target
System)
Earlier than
BSC6900
V900R011
67190193
RELOC.FailPrepU
EInvolCS.TgtNotAllow
Number of Failed CS
Relocation
Preparations for
SRNC (UE
Involved)
(Relocation Target
Not Allowed)
Earlier than
BSC6900
V900R011
67190194
RELOC.FailPrepU
EInvolCS.ResUnavail
Number of Failed CS
Relocation
Preparations for
SRNC (UE
Involved) (No
Resources
Available)
Earlier than
BSC6900
V900R011
67190195
RELOC.FailPrepU
EInvolCS.Unsp
Number of Failed CS
Relocation
Preparations for
SRNC (UE
Involved)
(Unspecified
Failure)
Earlier than
BSC6900
V900R011
67175799
VS.SRELOC.FailE
xec.CfgUnsupp
Number of Failed
Relocation
Executions During
Reconfiguration for
SRNC
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67175800
VS.SRELOC.FailE
xec.PhyChFail
Number of Failed
Relocation
Executions During
Reconfiguration for
SRNC (Physical
Channel Failure)
Earlier than
BSC6900
V900R011

766
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67175802
VS.SRELOC.FailE
xec.InvCfg
Number of Failed
Relocation
Executions During
Reconfiguration for
SRNC (Invalid
Configuration)
Earlier than
BSC6900
V900R011
67175803
VS.SRELOC.FailE
xec.CfgIncomp
Number of Failed
Relocation
Executions During
Reconfiguration for
SRNC
(Configuration
Incomplete)
Earlier than
BSC6900
V900R011
67192140
VS.SRELOC.FailE
xecPS.Expire
Number of Failed
SRNC Relocation
Executions Due to
Timer Expiry for IU
Release Command
for SRNC (PS
Domain)
Earlier than
BSC6900
V900R011
67192141
VS.SRELOC.FailE
xecCS.Expire
Number of Failed
SRNC Relocation
Executions Due to
Timer Expiry for IU
Release Command
for SRNC (CS
Domain)
Earlier than
BSC6900
V900R011
67192142
VS.SRELOC.AttE
xecUENotInvolPS
Number of PS
Relocation
Execution Attempts
for SRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67192143
VS.SRELOC.AttE
xecUENotInvolCS
Number of CS
Relocation
Execution Attempts
for SRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67175805
VS.SRELOC.FailE
xec.IuRel
Number of Failed
Relocation
Executions Due to
Reception of IU
Release Command
for SRNC
Earlier than
BSC6900
V900R011

767
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191047
VS.RELOC.AttPre
pUENotInvolCS.Ti
meCrit
Number of CS
Relocation
Preparation
Attempts for SRNC
(UE Not Involved)
(Time Critical
Relocation)
Earlier than
BSC6900
V900R011
67191048
VS.RELOC.AttPre
pUENotInvolCS.R
F
Number of CS
Relocation
Preparation
Attempts for SRNC
(UE Not Involved)
(Relocation
Desirable for Radio
Reasons)
Earlier than
BSC6900
V900R011
67191049
RELOC.AttPrepU
ENotInvolCS
Number of CS
Relocation
Preparation
Attempts for SRNC
(UE Not Involved)
Earlier than
BSC6900
V900R011
67191050
VS.RELOC.SuccPr
epUENotInvolCS.T
imeCrit
Number of
Successful CS
Relocation
Preparations for
SRNC (UE Not
Involved) (Time
Earlier than
BSC6900
V900R011
67191051
VS.RELOC.SuccPr
epUENotInvolCS.R
F
Number of
Successful CS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation
Desirable for Radio
Reasons)
Earlier than
BSC6900
V900R011
67191052
RELOC.SuccPrepUENotInvolCS
Number of
Successful CS
Relocation
Preparations for
SRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011

768
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191053
RELOC.FailPrepU
ENotInvolCS.CiphUnSupp
Number of Failed CS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)
Earlier than
BSC6900
V900R011
67191054
RELOC.FailPrepU
ENotInvolCS.TrelocprepExp
Number of Failed CS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Trelocprep Expiry)
Earlier than
BSC6900
V900R011
67191055
RELOC.FailPrepU
ENotInvolCS.TgtS
ysUnsupp
Number of Failed CS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation Not
Supported in Target
RNC or Target
System)
Earlier than
BSC6900
V900R011
67191056
RELOC.FailPrepU
ENotInvolCS.TgtN
otAllow
Number of Failed CS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation Target
Not Allowed)
Earlier than
BSC6900
V900R011
67191058
RELOC.FailPrepU
ENotInvolCS.ResUnavail
Number of Failed CS
Relocation
Preparations for
SRNC (UE Not
Involved) (No
Resources
Available)
Earlier than
BSC6900
V900R011

769
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191059
RELOC.FailPrepU
ENotInvolCS.Unsp
Number of Failed CS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Unspecified
Failure)
Earlier than
BSC6900
V900R011
67191060
VS.RELOC.AttPre
pUEInvolPS.TimeCrit
Number of PS
Relocation
Preparation
Attempts for SRNC
(UE Involved) (Time
Earlier than
BSC6900
V900R011
67191061
VS.RELOC.AttPre
pUENotInvolPS.Ti
meCrit
Number of PS
Relocation
Preparation
Attempts for SRNC
(UE Not Involved)
(Time Critical
Relocation)
Earlier than
BSC6900
V900R011
67191062
VS.RELOC.AttPre
pUEInvolPS.RF
Number of PS
Relocation
Preparation
Attempts for SRNC
(UE Involved)
(Relocation
Desirable for Radio
Reasons)
Earlier than
BSC6900
V900R011
67191063
VS.RELOC.AttPre
pUENotInvolPS.R
F
Number of PS
Relocation
Preparation
Attempts for SRNC
(UE Not Involved)
(Relocation
Desirable for Radio
Reasons)
Earlier than
BSC6900
V900R011
67191064
RELOC.AttPrepUEInvolPS
Number of PS
Relocation
Preparation
Attempts for SRNC
(UE Involved)
Earlier than
BSC6900
V900R011

770
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191065
RELOC.AttPrepU
ENotInvolPS
Number of PS
Relocation
Preparation
Attempts for SRNC
(UE Not Involved)
Earlier than
BSC6900
V900R011
67191066
VS.RELOC.SuccPr
epUEInvolPS.Time
Crit
Number of
Successful PS
Relocation
Preparations for
SRNC (UE
Involved) (Time
Earlier than
BSC6900
V900R011
67191067
VS.RELOC.SuccPr
epUENotInvolPS.T
imeCrit
Number of
Successful PS
Relocation
Preparations for
SRNC (UE Not
Involved) (Time
Earlier than
BSC6900
V900R011
67191068
VS.RELOC.SuccPr
epUEInvolPS.RF
Number of
Successful PS
Relocation
Preparations for
SRNC (UE
Involved)
(Relocation
Desirable for Radio
Reasons)
Earlier than
BSC6900
V900R011
67191069
VS.RELOC.SuccPr
epUENotInvolPS.R
F
Number of
Successful PS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation
Desirable for Radio
Reasons)
Earlier than
BSC6900
V900R011
67191070
RELOC.SuccPrepUEInvolPS
Number of
Successful PS
Relocation
Preparations for
SRNC (UE
Involved)
Earlier than
BSC6900
V900R011

771
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191071
RELOC.SuccPrepUENotInvolPS
Number of
Successful PS
Relocation
Preparations for
SRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67191072
RELOC.FailPrepU
EInvolPS.CiphUnSupp
Number of Failed PS
Relocation
Preparations for
SRNC (UE
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)
Earlier than
BSC6900
V900R011
67191073
RELOC.FailPrepU
ENotInvolPS.CiphUnSupp
Number of Failed PS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Requested
Ciphering and/or
Algorithms Not
Supported)
Earlier than
BSC6900
V900R011
67191074
RELOC.FailPrepU
EInvolPS.TrelocprepExp
Number of Failed PS
Relocation
Preparations for
SRNC (UE
Involved)
(Trelocprep Expiry)
Earlier than
BSC6900
V900R011
67191075
RELOC.FailPrepU
ENotInvolPS.TrelocprepExp
Number of Failed PS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Trelocprep Expiry)
Earlier than
BSC6900
V900R011

772
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191076
RELOC.FailPrepU
EInvolPS.TgtSysUnsupp
Number of Failed PS
Relocation
Preparations for
SRNC (UE
Involved)
(Relocation Not
Supported in Target
RNC or Target
System)
Earlier than
BSC6900
V900R011
67191077
RELOC.FailPrepU
ENotInvolPS.TgtSy
sUnsupp
Number of Failed PS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation Not
Supported in Target
RNC or Target
System)
Earlier than
BSC6900
V900R011
67191078
RELOC.FailPrepU
EInvolPS.TgtNotAllow
Number of Failed PS
Relocation
Preparations for
SRNC (UE
Involved)
(Relocation Target
Not Allowed)
Earlier than
BSC6900
V900R011
67191079
RELOC.FailPrepU
ENotInvolPS.TgtN
otAllow
Number of Failed PS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation Target
Not Allowed)
Earlier than
BSC6900
V900R011
67191082
RELOC.FailPrepU
EInvolPS.ResUnavail
Number of Failed PS
Relocation
Preparations for
SRNC (UE
Involved) (No
Resources
Available)
Earlier than
BSC6900
V900R011

773
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191083
RELOC.FailPrepU
ENotInvolPS.ResUnavail
Number of Failed PS
Relocation
Preparations for
SRNC (UE Not
Involved) (No
Resources
Available)
Earlier than
BSC6900
V900R011
67191084
RELOC.FailPrepU
EInvolPS.Unsp
Number of Failed PS
Relocation
Preparations for
SRNC (UE
Involved)
(Unspecified
Failure)
Earlier than
BSC6900
V900R011
67191085
RELOC.FailPrepU
ENotInvolPS.Unsp
Number of Failed PS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Unspecified
Failure)
Earlier than
BSC6900
V900R011
67192683
VS.SRELOC.AttE
xecUEInvolCS
Number of CS
Relocation
Execution Attempts
for SRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67192684
VS.SRELOC.AttE
xecUEInvolPS
Number of PS
Relocation
Execution Attempts
for SRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67192685
VS.SRELOC.SuccExecUEInvolCS
Number of
Successful CS
Relocation
Executions for
SRNC (UE
Involved)
Earlier than
BSC6900
V900R011
67192686
VS.SRELOC.SuccExecUEInvolPS
Number of
Successful PS
Relocation
Executions for
SRNC (UE
Involved)
Earlier than
BSC6900
V900R011

774
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192687
VS.SRELOC.SuccExecUENonInvolCS
Number of
Successful CS
Relocation
Executions for
SRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
67192688
VS.SRELOC.SuccExecUENonInvolPS
Number of
Successful PS
Relocation
Executions for
SRNC (UE Not
Involved)
Earlier than
BSC6900
V900R011
73423644
RELOC.FailPrepU
EInvolCS.NodeBReHost
Number of Failed CS
Relocation
Preparations for
SRNC (UE
Involved) (NodeB
Rehoming)
BSC6900
V900R014
73423645
RELOC.FailPrepU
EInvolPS.NodeBReHost
Number of Failed PS
Relocation
Preparations for
SRNC (UE
Involved) (NodeB
Rehoming)
BSC6900
V900R014
73430324
RELOC.FailPrepU
ENotInvolCS.TgtF
ail
Number of Failed CS
Relocation
Preparations for
SRNC (UE Not
Involved)
(Relocation failure in
target CN/RNC or
target system)
BSC6900
V900R017C10
73430325
RELOC.FailPrepU
ENotInvolPS.TgtF
ail
Number of Failed PS
Relocation
Preparations for
SRNC (UE Not
Involved)
target CN/RNC or
target system)
BSC6900
V900R017C10

775
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430326
RELOC.FailPrepU
EInvolCS.TgtFail
Number of Failed CS
Relocation
Preparations for
SRNC (UE
Involved)
target CN/RNC or
target system)
BSC6900
V900R017C10
73430327
RELOC.FailPrepU
EInvolPS.TgtFail
Number of Failed PS
Relocation
Preparations for
SRNC (UE
Involved)
target CN/RNC or
target system)
BSC6900
V900R017C10
None
Number of Relocation Preparation Attempts Due to Different Causes for SRNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190184
VS.RELOC.AttPrepUEInvo
lCS.TimeCrit
SRNC (UE Involved) (Time
67190185
lCS.RF
SRNC (UE Involved)
(Relocation Desirable for
Radio Reasons)
67191047
VS.RELOC.AttPrepUENotI
nvolCS.TimeCrit
SRNC (UE Not Involved)
(Time Critical Relocation)

776
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67191048
nvolCS.RF
Radio Reasons)
67191060
lPS.TimeCrit
67191061
nvolPS.TimeCrit
67191062
lPS.RF
SRNC (UE Involved)
Radio Reasons)
67191063
nvolPS.RF
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.The preceding counters
comply with section "8.6 Relocation Preparation" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the following figure. When the SRNC
sends a RELOCATION REQUIRED message to the CN in the CS or PS domain, the SRNC
measures the related counters based on different causes if the relocation request type is "UE
involved" or "UE not involved."
Issue 03 (2015-06-30)

777
BSC6900 UMTS
Figure 1-353 SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
lCS.TimeCrit
WRFD-020605
SRNS Relocation
lCS.RF
WRFD-020605
SRNS Relocation
nvolCS.TimeCrit
WRFD-020605
SRNS Relocation
nvolCS.RF
WRFD-020605
SRNS Relocation
lPS.TimeCrit
WRFD-020605
SRNS Relocation
nvolPS.TimeCrit
WRFD-020605
SRNS Relocation

778
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
lPS.RF
WRFD-020605
SRNS Relocation
nvolPS.RF
WRFD-020605
SRNS Relocation
Number of Relocation Preparation Attempts for SRNC

Counters
Counter ID
Counter Name
Counter Description
67190186
SRNC (UE Involved)
67191049
RELOC.AttPrepUENotInvolCS
67191064
SRNC (UE Involved)
67191065
RELOC.AttPrepUENotInvolPS
Description
These counters provide the numbers of CS or PS relocation preparation attempts initiated by the
SRNC based on the relocation type.The preceding counters comply with section "8.6 Relocation
Measurement point
The measurement is triggered at point A as shown in the figure. When the SRNC sends a
RELOCATION REQUIRED message to the CS domain or PS domain in the CN, the SRNC
measures the related counter based on relocation types and CN domains.
Issue 03 (2015-06-30)

779
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020605
SRNS Relocation
RELOC.AttPrepUENotInvolCS
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
RELOC.AttPrepUENotInvolPS
WRFD-020605
SRNS Relocation

780
BSC6900 UMTS
Number of Successful Relocation Preparations Due to Different Causes for SRNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190187
VS.RELOC.SuccPrepUEInv
olCS.TimeCrit
67190188
olCS.RF
SRNC (UE Involved)
Radio Reasons)
67191050
VS.RELOC.SuccPrepUENo
tInvolCS.TimeCrit
67191051
tInvolCS.RF
Radio Reasons)
67191066
olPS.TimeCrit
67191067
tInvolPS.TimeCrit
67191068
olPS.RF
SRNC (UE Involved)
Radio Reasons)
67191069
tInvolPS.RF
Radio Reasons)

781
BSC6900 UMTS
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.The preceding counters
comply with section "8.6 Relocation Preparation" in 3GPP TS 25.413 (v10.10.0).
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
olCS.TimeCrit
WRFD-020605
SRNS Relocation

782
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
olCS.RF
WRFD-020605
SRNS Relocation
tInvolCS.TimeCrit
WRFD-020605
SRNS Relocation
tInvolCS.RF
WRFD-020605
SRNS Relocation
olPS.TimeCrit
WRFD-020605
SRNS Relocation
tInvolPS.TimeCrit
WRFD-020605
SRNS Relocation
olPS.RF
WRFD-020605
SRNS Relocation
tInvolPS.RF
WRFD-020605
SRNS Relocation
Number of Successful Relocation Preparations for SRNC

Counters
Counter ID
Counter Name
Counter Description
67190189
SRNC (UE Involved)
67191052
67191070
SRNC (UE Involved)
67191071
Description
These counters provide the numbers of successful CS or PS relocation preparations initiated by
the SRNC based on the relocation type.The preceding counters comply with section "8.6
Relocation Preparation" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

783
BSC6900 UMTS
Measurement point
The measurement is triggered at point B as shown in the figure. After the SRNC initiates a
relocation procedure, the outgoing relocation preparation succeeds if the SRNC receives a
RELOCATION COMMAND message from the CS domain or PS domain in the CN. In this
case, the SRNC measures the related counter based on relocation types and CN domains.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation

784
BSC6900 UMTS
Number of Failed Relocation Preparations Due to Different Causes for SRNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190192
RELOC.FailPrepUEInvolC
S.CiphUnSupp
Number of Failed CS
SRNC (UE Involved)
67175739
S.TrelocprepExp
Number of Failed CS
SRNC (UE Involved)
(Trelocprep Expiry)
67175740
S.TgtSysUnsupp
Number of Failed CS
SRNC (UE Involved)
(Relocation Not Supported in
Target RNC or Target
System)
67190193
S.TgtNotAllow
Number of Failed CS
SRNC (UE Involved)
(Relocation Target Not
Allowed)
67190194
S.ResUnavail
Number of Failed CS
SRNC (UE Involved) (No
67190195
S.Unsp
Number of Failed CS
SRNC (UE Involved)
(Unspecified Failure)
67191053
RELOC.FailPrepUENotInv
olCS.CiphUnSupp
Number of Failed CS
67191054
olCS.TrelocprepExp
Number of Failed CS
(Trelocprep Expiry)

785
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67191055
olCS.TgtSysUnsupp
Number of Failed CS
System)
67191056
olCS.TgtNotAllow
Number of Failed CS
Allowed)
67191058
olCS.ResUnavail
Number of Failed CS
67191059
olCS.Unsp
Number of Failed CS
67191072
RELOC.FailPrepUEInvolPS
.CiphUnSupp
Number of Failed PS
SRNC (UE Involved)
67191073
olPS.CiphUnSupp
Number of Failed PS
67191074
.TrelocprepExp
Number of Failed PS
SRNC (UE Involved)
(Trelocprep Expiry)
67191075
olPS.TrelocprepExp
Number of Failed PS
(Trelocprep Expiry)

786
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67191076
.TgtSysUnsupp
Number of Failed PS
SRNC (UE Involved)
System)
67191077
olPS.TgtSysUnsupp
Number of Failed PS
System)
67191078
.TgtNotAllow
Number of Failed PS
SRNC (UE Involved)
Allowed)
67191079
olPS.TgtNotAllow
Number of Failed PS
Allowed)
67191082
.ResUnavail
Number of Failed PS
SRNC (UE Involved) (No
67191083
olPS.ResUnavail
Number of Failed PS
67191084
.Unsp
Number of Failed PS
SRNC (UE Involved)
67191085
olPS.Unsp
Number of Failed PS
73423644
S.NodeBReHost
Number of Failed CS
SRNC (UE Involved)
(NodeB Rehoming)

787
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73423645
.NodeBReHost
Number of Failed PS
SRNC (UE Involved)
(NodeB Rehoming)
73430324
olCS.TgtFail
Number of Failed CS
(Relocation failure in target
CN/RNC or target system)
73430325
olPS.TgtFail
Number of Failed PS
73430326
S.TgtFail
Number of Failed CS
SRNC (UE Involved)
73430327
.TgtFail
Number of Failed PS
SRNC (UE Involved)
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.The preceding counters
comply with section "8.6.3 Unsuccessful Operation" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

788
BSC6900 UMTS
Figure 1-357 Failed SRNC relocation preparation procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
S.CiphUnSupp
WRFD-020605
SRNS Relocation
S.TrelocprepExp
WRFD-020605
SRNS Relocation
S.TgtSysUnsupp
WRFD-020605
SRNS Relocation
S.TgtNotAllow
WRFD-020605
SRNS Relocation
S.ResUnavail
WRFD-020605
SRNS Relocation
S.Unsp
WRFD-020605
SRNS Relocation
olCS.CiphUnSupp
WRFD-020605
SRNS Relocation

789
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
olCS.TrelocprepExp
WRFD-020605
SRNS Relocation
olCS.TgtSysUnsupp
WRFD-020605
SRNS Relocation
olCS.TgtNotAllow
WRFD-020605
SRNS Relocation
olCS.ResUnavail
WRFD-020605
SRNS Relocation
olCS.Unsp
WRFD-020605
SRNS Relocation
.CiphUnSupp
WRFD-020605
SRNS Relocation
olPS.CiphUnSupp
WRFD-020605
SRNS Relocation
.TrelocprepExp
WRFD-020605
SRNS Relocation
olPS.TrelocprepExp
WRFD-020605
SRNS Relocation
.TgtSysUnsupp
WRFD-020605
SRNS Relocation
olPS.TgtSysUnsupp
WRFD-020605
SRNS Relocation
.TgtNotAllow
WRFD-020605
SRNS Relocation
olPS.TgtNotAllow
WRFD-020605
SRNS Relocation
.ResUnavail
WRFD-020605
SRNS Relocation
olPS.ResUnavail
WRFD-020605
SRNS Relocation
.Unsp
WRFD-020605
SRNS Relocation
olPS.Unsp
WRFD-020605
SRNS Relocation
S.NodeBReHost
WRFD-040202
RNC Node Redundancy
WRFD-020605
SRNS Relocation

790
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
.NodeBReHost
WRFD-040202
RNC Node Redundancy
WRFD-020605
SRNS Relocation
olCS.TgtFail
WRFD-020605
SRNS Relocation
olPS.TgtFail
WRFD-020605
SRNS Relocation
S.TgtFail
WRFD-020605
SRNS Relocation
.TgtFail
WRFD-020605
SRNS Relocation
Counters Related to the Number of Failed Relocation Executions During

Reconfiguration for Different Causes for SRNC
Counters
Counter ID
Counter Name
Counter Description
67175799
VS.SRELOC.FailExec.Cfg
Unsupp

Executions During
Reconfiguration for SRNC
(Configuration
Unsupported)
67175800
VS.SRELOC.FailExec.Phy
ChFail

Executions During
(Physical Channel Failure)
67175802
VS.SRELOC.FailExec.InvC
fg

Executions During
(Invalid Configuration)
67175803
VS.SRELOC.FailExec.CfgI
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.The preceding counters comply with section
Issue 03 (2015-06-30)

791
BSC6900 UMTS
"8.6 Relocation Preparation" in 3GPP TS 25.413 (v10.10.0) and section "8.2 Radio Bearer
control procedures" in 3GPP TS 25.331 (v10.13.0).
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-358 Failed SRNC relocation procedure during the reconfiguration (UE involved)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRELOC.FailExec.Cfg
Unsupp
WRFD-020605
SRNS Relocation

792
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.SRELOC.FailExec.Phy
ChFail
WRFD-020605
SRNS Relocation
VS.SRELOC.FailExec.InvC
fg
WRFD-020605
SRNS Relocation
VS.SRELOC.FailExec.CfgI
ncomp
WRFD-020605
SRNS Relocation
Counters Related to the Number of Failed SRNC Relocation Executions Due to

Timer Expiry for IU Release Command for SRNC
Counters
Counter ID
Counter Name
Counter Description
67192140
VS.SRELOC.FailExecPS.E
xpire
Number of Failed SRNC

Relocation Executions Due
to Timer Expiry for IU
Release Command for SRNC
(PS Domain)
67192141
VS.SRELOC.FailExecCS.E
xpire
Number of Failed SRNC

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.The preceding counters comply with section "8.7 Relocation Resource Allocation" and
"8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the following figure. After sending a
RELOCATION COMMIT message (during the relocation that the UE is not involved), the
SRNC starts the timer to wait for the IU RELEASE COMMAND message. If the SRNC does
not receive an IU RELEASE COMMAND message before the timer expires, the SRNC sends
an IU RELEASE REQUEST message to the CN. In addition, the SRNC measures the related
counter according to different domain types.
Issue 03 (2015-06-30)

793
BSC6900 UMTS
Figure 1-359 Failed SRNC relocation execution procedure due to timer expiry for IU release
command (UE not involved)
The measurement is triggered at point A as shown in the following figure. After sending a
reconfiguration message to the UE (during the relocation that the UE is involved. The following
figure takes the RADIO BEARER RECONFIGURATION message as an example), the SRNC
starts the timer to wait for the IU RELEASE COMMAND message. If the SRNC does not receive
an IU RELEASE COMMAND message before the timer expires, the SRNC sends an IU
RELEASE REQUEST message to the CN. In addition, the SRNC measures the related counter
according to different domain types.
Issue 03 (2015-06-30)

794
BSC6900 UMTS
Figure 1-360 Failed SRNC relocation execution procedure due to timer expiry for IU release
command (UE involved)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRELOC.FailExecPS.E
xpire
WRFD-020605
SRNS Relocation
VS.SRELOC.FailExecCS.E
xpire
WRFD-020605
SRNS Relocation

795
BSC6900 UMTS
Counters Related to the Number of Relocation Execution Attempts for SRNC (UE
Not Involved)
Counters
Counter ID
Counter Name
Counter Description
67192142
VS.SRELOC.AttExecUENotInvolPS
67192143
VS.SRELOC.AttExecUENotInvolCS
Description
These counters provide the number of relocation execution attempts initiated by the SRNC
during the relocation according to different domain types.The preceding counters comply with
section "8.2.3 Relocation Commit" in 3GPP TS 25.423 (v10.10.0).
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-361 SRNC relocation execution procedure (UE not involved)
Issue 03 (2015-06-30)

796
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SRELOC.AttExecUENotInvolPS
WRFD-020605
SRNS Relocation
VS.SRELOC.AttExecUENotInvolCS
WRFD-020605
SRNS Relocation
Number of Failed Relocation Executions Due to Reception of IU Release Command

for SRNC
Counters
Counter ID
Counter Name
Counter Description
67175805
VS.SRELOC.FailExec.IuRel

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."This counter
complies with section "8.7 Relocation Resource Allocation" and "8.5 Iu Release" in 3GPP TS
25.413 (v10.10.0).
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."
Issue 03 (2015-06-30)

797
BSC6900 UMTS
Figure 1-362 Failed SRNC relocation execution procedure (reception of IU release command)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SRELOC.FailExec.IuRel
WRFD-020605
SRNS Relocation
Counters Related to the Number of Reconfiguration Attempts During Relocation

Execution for SRNC ( UE Involved)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192683
VS.SRELOC.AttExecUEInvolCS
SRNC (UE Involved)

798
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192684
VS.SRELOC.AttExecUEInvolPS
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.The preceding counters comply
with section "8.6 Relocation Preparation" in 3GPP TS 25.413 (v10.10.0) and section "8.2 Radio
Bearer control procedures" in 3GPP TS 25.331 (v10.13.0).
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-363 Reconfiguration procedure during the SRNC relocation (UE involved)
Formula
None
Unit
None
Issue 03 (2015-06-30)

799
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SRELOC.AttExecUEInvolCS
WRFD-020605
SRNS Relocation
VS.SRELOC.AttExecUEInvolPS
WRFD-020605
SRNS Relocation
Number of Successful Relocation Executions for SRNC

Counters
Counter ID
Counter Name
Counter Description
67192685
SRNC (UE Involved)
67192686
SRNC (UE Involved)
67192687
67192688
Description
These counters provide the numbers of successful relocation executions (UE involved or UE
not involved) initiated by the SRNC based on different CN domains.The preceding counters
comply with section "8.7 Relocation Resource Allocation" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

800
BSC6900 UMTS
Figure 1-364 Successful SRNC relocation procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation
WRFD-020605
SRNS Relocation

801
BSC6900 UMTS
1.10.22 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202533
RLC.NbrBlocksSe
nt.TM
Number of PDUs
Sent by TM RLCs for
RNC
Earlier than
BSC6900
V900R011
67202534
RLC.NbrBlocksSe
nt.AM
Number of PDUs
Sent by AM RLCs
for RNC
Earlier than
BSC6900
V900R011
67202535
RLC.NbrBlocksSe
nt.UM
Number of PDUs
Sent by UM RLCs
for RNC
Earlier than
BSC6900
V900R011
67202536
RLC.NbrBlocksRe
ceived.TM
Number of PDUs
Received by TM
RLCs for RNC
Earlier than
BSC6900
V900R011
67202537
RLC.NbrBlocksRe
ceived.AM
Number of PDUs
Received by AM
RLCs for RNC
Earlier than
BSC6900
V900R011
67202538
RLC.NbrBlocksRe
ceived.UM
Number of PDUs
Received by UM
RLCs for RNC
Earlier than
BSC6900
V900R011
67202539
RLC.DiscardedBlocksByRNC
Number of PDUs
Discarded by RLCs
for RNC
Earlier than
BSC6900
V900R011
67202540
RLC.RetransmittedBlocksToUE
Number of PDUs
Retransmitted by
RLCs for RNC
Earlier than
BSC6900
V900R011
67204246
RLC.NbrBlocksRe
ceived.AM.1
Number of PDUs
with the Size Smaller
than 336 bit
Received by RLCs In
Acknowledged
Mode Carried by
TRB
BSC6900
V900R012

802
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204247
RLC.NbrBlocksRe
ceived.AM.2
Number of PDUs
with the Size Greater
than or Equal to 336
bit Received by
RLCs In
Acknowledged
Mode Carried by
TRB
BSC6900
V900R012
None
Number of Packets Sent at the RLC Layer

Counters
Counter ID
Counter Name
Counter Description
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.The measured data include retransmitted data in AM model.
Measurement point
These counters are incremented by one each time the RLC layer on the RNC side sends a packet.
Formula
None
Unit
packet
Issue 03 (2015-06-30)

803
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
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
Number of Packets Received at the RLC Layer

Counters
Counter ID
Counter Name
Counter Description
67202536
RLC.NbrBlocksReceived.T
M
Number of PDUs Received

by TM RLCs for RNC
67202537
RLC.NbrBlocksReceived.A
M

by AM RLCs for RNC
67202538
RLC.NbrBlocksReceived.U
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.The measured data include retransmitted data in AM model.
Measurement point
These counters are incremented by one each time the RLC layer on the RNC receives a packet.
Formula
None
Unit
packet
Issue 03 (2015-06-30)

804
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
RLC.NbrBlocksReceived.T
M
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
M
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RLC.NbrBlocksReceived.U
M
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Packets Discarded by All RLCs in RNC

Counters
Counter ID
Counter Name
Counter Description
67202539
Number of PDUs Discarded

by RLCs for RNC
Description
This measurement item takes statistics of the number of packets discarded by all the RLCs in
the RNC.The measured data include retransmitted data.
Measurement point
The measurement is triggered when an RLC discards a packet.
Formula
None
Unit
packet
Issue 03 (2015-06-30)

805
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Packets Retransmitted by All RLCs in AM Mode in RNC

Counters
Counter ID
Counter Name
Counter Description
67202540
Number of PDUs
Retransmitted by RLCs for
RNC
Description
This counter provides the number of PDUs that are retransmitted by the RLC in AM mode in
the RNC. It excludes the number of PDUs that are automatically retransmitted by the RLC.
Measurement point
The measurement is triggered when an RLC in AM mode retransmits a packet.
Formula
None
Unit
packet
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

806
BSC6900 UMTS
Number of PDUs with the Size Smaller than 336 bit Received by RLCs In
Acknowledged Mode Carried by TRB
Counters
Counter ID
Counter Name
Counter Description
67204246
M.1
Number of PDUs with the

Size Smaller than 336 bit
Received by RLCs In
Acknowledged Mode
Carried by TRB
Description
This counter provides the number of PDUs with the size smaller than 336 bit received by RLCs
in acknowledged mode carried by the traffic radio bearer (TRB).The measured data include
retransmitted data.
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
M.1
WRFD-010695
UL Layer 2 Improvement

807
BSC6900 UMTS
Number of PDUs with the Size Greater than or Equal to 336 bit Received by RLCs
In Acknowledged Mode Carried by TRB
Counters
Counter ID
Counter Name
Counter Description
67204247
M.2
Number of PDUs with the

Size Greater than or Equal to
336 bit Received by RLCs In
Acknowledged Mode
Carried by TRB
Description
This counter provides the number of PDUs with the size greater than or equal to 336 bit received
by RLCs in acknowledged mode carried by the traffic radio bearer (TRB).The measured data
include retransmitted data.
Measurement point
This counter is measured at the RNC when RLCs in acknowledge mode carried by the TRB
receive a PDU with the size greater than or equal to 336 bit.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
M.2
WRFD-010695
UL Layer 2 Improvement
1.10.23 IMS Measurement <per RNC>(RNC.IMS)

Overview
A new CN domain, known as IMS domain, is introduced into the system architecture of 3GPP
R5.
Issue 03 (2015-06-30)

808
BSC6900 UMTS
With the UTRAN PS features and PS CN, the IMS domain provides various standard services,
such as packet call and IP multimedia conference. In addition, it can also provide real time or
approximate real time voice, data and video communications, such as PTT service.
Seen from the access network, the IMS service is carried by two PS RABs. One carries the
Session Initiation Protocol (SIP) of the IMS signaling, and the other carries IMS application.
Both RABs have their own service features.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202541
VS.RABCmb.Num
IMS.Str8.8
Number of IMS_PoC
Users in the Statistic
Period for RNC
Earlier than
BSC6900
V900R011
67202542
VS.RABCmb.Num
IMS.Con8.8
Number of
IMS_VoIP Users in
the Statistic Period
for RNC
Earlier than
BSC6900
V900R011
67202546
VS.IMS.NumSigUs
er
Number of IMS
Period for RNC
Earlier than
BSC6900
V900R011
67203417
VS.RABCmb.IMSSigCon16.42.8
Number of IMS
Period for RNC
(Signaling at 16kbit/s
and Services at
42.8kbit/s)
Earlier than
BSC6900
V900R011
67203418
VS.RABCmb.IMSSigCon16.32
Number of IMS
Period for RNC
and Services at
32kbit/s)
Earlier than
BSC6900
V900R011
67203419
Number of IMS
Period for RNC
and Services at
64kbit/s)
Earlier than
BSC6900
V900R011
67203420
Number of IMS
Period for RNC
and Services at
16kbit/s)
Earlier than
BSC6900
V900R011

809
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67203421
Number of IMS
Period for RNC
and Services at
32kbit/s)
Earlier than
BSC6900
V900R011
67203422
Number of IMS
Period for RNC
and Services at
16kbit/s)
Earlier than
BSC6900
V900R011
None
Mean Number of UEs Setting Up Different IMS Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202541
VS.RABCmb.NumIMS.Str8
.8
Number of IMS_PoC Users

in the Statistic Period for
RNC
67202542
VS.RABCmb.NumIMS.Con
8.8
Number of IMS_VoIP Users

in the Statistic Period for
RNC
67203417
Number of IMS Users in the

Statistic Period for RNC
(Signaling at 16kbit/s and
Services at 42.8kbit/s)
67203418

Services at 32kbit/s)
67203419


810
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67203420

67203421

67203422

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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RABCmb.NumIMS.Str8
.8
WRFD-010617
VS.RABCmb.NumIMS.Con
8.8
WRFD-010617
WRFD-010617
WRFD-010617

811
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010617
WRFD-010617
WRFD-010617
WRFD-010617
Number of UEs Setting Up IMS Services

Counters
Counter ID
Counter Name
Counter Description
67202546
VS.IMS.NumSigUser

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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IMS.NumSigUser
WRFD-010617

812
BSC6900 UMTS
1.10.24 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174454
VS.RRC.AttConnR
el.RNC
Number of RRC
Connection Releases
for RNC
Earlier than
BSC6900
V900R011
67174641
VS.RRC.AttConnR
el.Norm.RNC
Number of RRC
Connection Releases
due to Normal Event
for RNC
Earlier than
BSC6900
V900R011
67190072
VS.RRC.AttConnR
el.Cong.RNC
Number of RRC
Connection Releases
due to Congestion for
RNC
Earlier than
BSC6900
V900R011
67190073
VS.RRC.AttConnR
el.Preempt.RNC
Number of RRC
Connection Releases
due to Preemption
for RNC
Earlier than
BSC6900
V900R011
67190074
VS.RRC.AttConnR
el.UsrInact.RNC
Number of RRC
Connection Releases
due to User Inactivity
for RNC
Earlier than
BSC6900
V900R011
67190075
VS.RRC.AttConnR
el.ReEstRej.RNC
Number of RRC
Connection Releases
due to Reestablishment Reject
for RNC
Earlier than
BSC6900
V900R011
67190076
VS.RRC.AttConnR
el.DSCR.RNC
Number of RRC
Connection Releases
due to Directed
Signaling
Connection Reestablishment for
RNC
Earlier than
BSC6900
V900R011

813
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67174647
VS.RRC.AttConnR
el.Unspec.RNC
Number of RRC
Connection Releases
due to Unspecified
Causes for RNC
Earlier than
BSC6900
V900R011
73421937
VS.RRC.AttConRe
l.SCRI.DF2P.NoRe
ply.RNC
Number of RRC
Releases Due to
Failure in the UE
State Transition to
CELL_PCH
Triggered by
Signaling
Connection Release
Indication
BSC6900
V900R012
73423382
VS.RRC.AttConnR
el.DSCR.SRNC
Number of RRC
Connection Releases
Triggered by SRNC
Due to DSCR
BSC6900
V900R013
73423383
VS.RRC.AttConnR
el.DSCR.DRNC
Number of RRC
Connection Releases
Triggered by DRNC
Due to DSCR
BSC6900
V900R013
None
Number of RRC Connection Releases

Counters
Counter ID
Counter Name
Counter Description
67174454
VS.RRC.AttConnRel.RNC

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.This counter complies with section "8.1.4 RRC connection release" in
3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

814
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnRel.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

815
BSC6900 UMTS
Counters Related to the Number of RRC Connection Releases due to Different

Causes
Counters
Counter ID
Counter Name
Counter Description
67174641
VS.RRC.AttConnRel.Norm.
RNC

Releases due to Normal
Event for RNC
67190072
VS.RRC.AttConnRel.Cong.
RNC

Releases due to Congestion
for RNC
67190073
VS.RRC.AttConnRel.Preem
pt.RNC

Releases due to Preemption
for RNC
67190074
VS.RRC.AttConnRel.UsrIn
act.RNC

Releases due to User
Inactivity for RNC
67190075
VS.RRC.AttConnRel.ReEst
Rej.RNC

Releases due to Reestablishment Reject for
RNC
67190076
VS.RRC.AttConnRel.DSCR
.RNC

Releases due to Directed
Signaling Connection Reestablishment for RNC
67174647
VS.RRC.AttConnRel.Unspe
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.The preceding counters comply with section "8.1.4 RRC
connection release" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC initiates the
RRC connection release procedure, the RNC sends a RRC CONNECTION RELEASE message
to the UE. These counters are measured on the RNC side when a RRN CONNECTION
RELEASE message with the corresponding cause is sent to the UE. For details, see section
10.3.3.32 in 3GPP TS 25.331.
Issue 03 (2015-06-30)

816
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnRel.Norm.
RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.AttConnRel.Cong.
RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.AttConnRel.Preem
pt.RNC
WRFD-010505
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

817
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnRel.UsrIn
act.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.AttConnRel.ReEst
Rej.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
.RNC
WRFD-021400

WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.AttConnRel.Unspe
c.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Releases Due to Failure in the UE State Transition to CELL_PCH

Triggered by Signaling Connection Release Indication
Counters
Counter ID
Counter Name
Counter Description
73421937
VS.RRC.AttConRel.SCRI.D
F2P.NoReply.RNC
Number of RRC Releases

Due to Failure in the UE State
Transition to CELL_PCH
Triggered by Signaling
Connection Release
Indication
Description
This counter provides the number of times that an RRC connection is released because no UE
response is received after the RNC sends a RADIO BEAR RECONFIGURATION or
PHYSICAL CHANNEL RECONFIGURATION message to the UE, instructing the UE to
transfer to the CELL_PCH state.This counter complies with section "8.1.4 RRC connection
release" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

818
BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in the figure. After receiving the
SIGNALLING CONNECTION RELEASE INDICATION message from the UE, the RNC
sends a RADIO BEAR RECONFIGURATION or PHYSICAL CHANNEL
RECONFIGURATION message to the UE, instructing the UE to transfer to the CELL_PCH
state. If no response from the UE is received before the timer expires, the RNC releases the RRC
connection and measure this counter.
Figure 1-367 RB reconfiguration or Physical Channel reconfiguration failure procedure (UE no
response)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.AttConRel.SCRI.D
F2P.NoReply.RNC
WRFD-020500
Enhanced Fast Dormancy

819
BSC6900 UMTS
Number of RRC Connection Releases Triggered by SRNC Due to DSCR

Counters
Counter ID
Counter Name
Counter Description
73423382
.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).This
counter complies with section "8.1.4 RRC connection release" in 3GPP TS 25.331 (v10.13.0).
Measurement point
an RRC CONNECTION RELEASE message because of DSCR.
Formula
None
Issue 03 (2015-06-30)

820
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.SRNC
WRFD-021400

WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Releases Triggered by DRNC Due to DSCR

Counters
Counter ID
Counter Name
Counter Description
73423383
.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).This
counter complies with section "8.1.4 RRC connection release" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

821
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.DRNC
WRFD-021400

WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

822
BSC6900 UMTS
1.10.25 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 counter of RRC connection setup attempts and rejects does not include service-based
redirections, inter-RAT and inter-frequency distance-based redirections, weakcoverage-based
redirections, macro & micro joint inter-frequency redirections and the number of RRC
connection requests discarded during flow control.
In addition, the number of RRC connection setup attempts do not include the attempts in the
Directed Signalling Connection Re-establishment (DSCR) procedure triggered by the
overlapping of the RRC connection setup procedure and cell update procedure.
During the resource admission and radio link setup process, if DRD is configured when resource
admission and radio link setup fail and the configured DRD succeeds, the measurement is
triggered in the target cell for the UE. If the configured DRD fails, the measurement is triggered
in the source cell for the UE.
Note that the measurement is not triggered for RRC CONNECTION REQUEST messages
retransmitted by the UE.
The following figure shows the measurement points of the counters.
Issue 03 (2015-06-30)

823
BSC6900 UMTS
Figure 1-370 Flow chart of RRC connection setup
Issue 03 (2015-06-30)

824
BSC6900 UMTS

Measurement points
Description
VS.RRC.AttConnEstab.RNC,
VS.RRC.AttConnEstab.Msg.RNC,
VS.RRC.AttConnEstab.CellDCH.RNC,
VS.RRC.AttConnEstab.CellFACH.RNC
See:RRC.Setup.Cell
VS.RRC.SuccConnEstab.RNC,
VS.RRC.SuccConnEstab.CellFACH.RNC,
VS.RRC.SuccConnEstab.CellDCH.RNC
See:RRC.Setup.Cell
E~L
See:RRC.SetupFail.Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67174450
VS.RRC.AttConnE
stab.RNC
Number of RRC
Connection Requests
Processed by RNC
Earlier than
BSC6900
V900R011
67174449
VS.RRC.AttConnE
stab.Msg.RNC
Total Number of
RRC Connection
Requests Received
by RNC
Earlier than
BSC6900
V900R011
67174689
VS.RRC.AttConnE
stab.CellDCH.RNC
Number of RRC
Connection Requests
for RNC (UE Target
State of
CELL_DCH)
Earlier than
BSC6900
V900R011
67174705
VS.RRC.AttConnE
stab.CellFACH.RN
C
Number of RRC
Connection Requests
for RNC (UE Target
State of
CELL_FACH)
Earlier than
BSC6900
V900R011
67174452
VS.RRC.SuccConn
Estab.RNC
Number of
Successful RRC
Connection
Establishments for
RNC
Earlier than
BSC6900
V900R011

825
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67174706
VS.RRC.SuccConn
Estab.CellFACH.R
NC
Number of
Successful RRC
Connection
Establishments on
CELL_FACH
Earlier than
BSC6900
V900R011
67174691
VS.RRC.SuccConn
Estab.CellDCH.RN
C
Number of
Successful RRC
Connection
Establishments on
CELL_DCH
Earlier than
BSC6900
V900R011
Counter
Sub Counter
VS.RRC.AttConnEstab.Msg.RNC
VS.RRC.AttConnEstab.RNC

Counter
Sub Counter
VS.RRC.AttConnEstab.RNC
VS.RRC.AttConnEstab.CellDCH.RNC
VS.RRC.AttConnEstab.CellFACH.RNC
VS.RRC.SuccConnEstab.RNC
VS.RRC.SuccConnEstab.CellFACH.RNC
VS.RRC.SuccConnEstab.CellDCH.RNC
Counters Related to the Number of RRC Connection Requests Processed by RNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67174450
VS.RRC.AttConnEstab.RN
C

Requests Processed by RNC
67174689
VS.RRC.AttConnEstab.Cell
DCH.RNC

Requests for RNC (UE
Target State of CELL_DCH)

826
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67174705
FACH.RNC

Requests for RNC (UE
Target State of
CELL_FACH)
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, weakcoverage-based redirection, macro & micro
joint inter-frequency redirection, UE capability-based inter-frequency redirection and the
number of RRC connection requests discarded during flow control. In addition,These counters
do not include the RRC connection setup requests in the Directed Signalling Connection Reestablishment (DSCR) procedure triggered by the overlapping of the RRC connection setup
procedure and cell update procedure.The preceding counters comply with section "8.1.3 RRC
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives a RRC
CONNECTION REQUEST message from the UE. These counters exclude the number of
rejected RRC connection requests caused by service-based redirection, inter-RAT and interfrequency distance-based redirection, weakcoverage-based redirection, macro & micro joint
inter-frequency redirection, UE capability-based inter-frequency redirection and the number of
RRC connection requests discarded during flow control. These counters do not include the RRC
procedure.Note that the measurement is not triggered for a RRC CONNECTION REQUEST
message that is retransmitted by the UE in the RRC connection setup procedure.
Issue 03 (2015-06-30)

827
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnEstab.RN
C
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
DCH.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
FACH.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

828
BSC6900 UMTS
Total Number of RRC Connection Requests Received by RNC

Counters
Counter ID
Counter Name
Counter Description
67174449
VS.RRC.AttConnEstab.Msg
.RNC
Total Number of RRC

Connection Requests
Received by RNC
Description
This counter provides the total number of RRC CONNECTION REQUEST messages received
by the RNC from the UE, including the retransmitted ones in the RRC connection setup
procedure.This counter complies with section "8.1.3 RRC connection establishment" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
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 in the RRC connection
setup procedure are all measured by the RNC.
Issue 03 (2015-06-30)

829
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counters Related to the Number of Successful RRC Connection Establishments

Counters
Counter ID
Counter Name
Counter Description
67174452
VS.RRC.SuccConnEstab.R
NC

for RNC
67174706
VS.RRC.SuccConnEstab.Ce
llFACH.RNC

on CELL_FACH
67174691
llDCH.RNC

on CELL_DCH
Description
These counters provide the number of RRC CONNECTION SETUP COMPLETE messages
sent from the UE to the RNC.The preceding counters comply with section "8.1.3 RRC
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.
Issue 03 (2015-06-30)

830
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.SuccConnEstab.R
NC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
llFACH.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
llDCH.RNC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

831
BSC6900 UMTS
1.10.26 RRC Status Measurement <per RNC>(RRC.STATE)

Overview
This function subset provides the average number of UEs in different RRC connection states in
the RNC.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67199465
VS.CellDCHUEs.R
NC
Number of UEs in
CELL_DCH State
for RNC
Earlier than
BSC6900
V900R011
67199466
VS.CellFACHUEs.
RNC
Number of UEs in
CELL_FACH State
for RNC
Earlier than
BSC6900
V900R011
67199467
VS.CellPCHUEs.R
NC
Number of UEs in
CELL_PCH State for
RNC
Earlier than
BSC6900
V900R011
67199468
VS.UraPCHUEs.R
NC
Number of UEs in
URA_PCH State for
RNC
Earlier than
BSC6900
V900R011
73410506
VS.UraPCHUEs.P
TT.RNC
Average Number of
PTT UEs with RRC
Connection State of
URA_PCH for RNC
BSC6900
V900R012
73441130
VS.UraEPCHUEs.
RNC
Average Number of
UEs in the
URA_PCH State and
Carried on the EPCH
for RNC
BSC6900
V900R013
None
Issue 03 (2015-06-30)

832
BSC6900 UMTS
Counters Related to the Number of UEs in Different RRC Connection States for
RNC
Counters
Counter ID
Counter Name
Counter Description
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.The
preceding counters comply with section "7.2.2 UTRA RRC Connected mode" in 3GPP TS
25.331 (v10.13.0).
Measurement point
The system periodically takes samples of the number of UEs in each RRC connection state every
five seconds. At the end of the measurement period, by dividing the accumulated value of sample
data in the period by the number of samples, the average number of UEs in each RRC connection
state in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.CellDCHUEs.RNC
WRFD-010202
UE State in Connected Mode

(CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH)

833
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.CellFACHUEs.RNC
WRFD-010202

URA-PCH, CELL-FACH)
VS.CellPCHUEs.RNC
WRFD-010202

URA-PCH, CELL-FACH)
VS.UraPCHUEs.RNC
WRFD-010202

URA-PCH, CELL-FACH)
Number of PTT UEs in URA_PCH State for RNC

Counters
Counter ID
Counter Name
Counter Description
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.This counter
complies with section "7.2.2 UTRA RRC Connected mode" in 3GPP TS 25.331 (v10.13.0).
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
Issue 03 (2015-06-30)

834
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.UraPCHUEs.PTT.RNC
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-020134
Push to Talk
Average Number of UEs in the URA_PCH State and Carried on the EPCH for RNC
Counters
Counter ID
Counter Name
Counter Description
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.UraEPCHUEs.RNC
WRFD-020134
Push to Talk

835
BSC6900 UMTS
1.10.27 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67175268
VS.SoHO.Att.RNC
Number of Softer
Handovers Initiated
by RNC for RNC
Earlier than
BSC6900
V900R011
67175266
VS.SHO.Att.RNC
Number of Soft
Handovers Initiated
by RNC for RNC
Earlier than
BSC6900
V900R011
67175267
VS.SHO.Succ.RNC
Number of
Successful Soft
Handovers Initiated
by RNC for RNC
Earlier than
BSC6900
V900R011
67175269
VS.SoHO.Succ.RN
C
Number of
Successful Softer
Handovers Initiated
by RNC for RNC
Earlier than
BSC6900
V900R011
67199432
VS.SHO.AS.1.RNC
Mean Number of
UEs with One Radio
Link for RNC
Earlier than
BSC6900
V900R011
67199434
VS.SHO.AS.
2Soft.RNC
Mean Number of
UEs with Two
Uncombined Radio
Links for RNC
Earlier than
BSC6900
V900R011

836
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67199437
VS.SHO.AS.
3Soft2Softer.RNC
Mean Number of
UEs with Three
Radio Links and Two
Combined for RNC
Earlier than
BSC6900
V900R011
67199436
VS.SHO.AS.
3Soft.RNC
Mean Number of
UEs with Three
Uncombined Radio
Links for RNC
Earlier than
BSC6900
V900R011
67199433
VS.SHO.AS.
2Softer.RNC
Mean Number of
UEs with Two
Combined Radio
Links for RNC
Earlier than
BSC6900
V900R011
67199435
VS.SHO.AS.
3Softer.RNC
Mean Number of
UEs with Three
Combined Radio
Links for RNC
Earlier than
BSC6900
V900R011
67203933
VS.SHO.AS.4.RNC
Mean Number of
UEs with Four Radio
Links for RNC
Earlier than
BSC6900
V900R011
67203934
VS.SHO.AS.5.RNC
Mean Number of
UEs with Five Radio
Links for RNC
Earlier than
BSC6900
V900R011
67203935
VS.SHO.AS.6.RNC
Mean Number of
UEs with Six Radio
Links for RNC
Earlier than
BSC6900
V900R011
67175283
VS.SHO.Drop.RN
C
Number of Call
Drops Due to Soft
Handover Failures
for RNC
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

837
BSC6900 UMTS
Number of Softer Handover Attempts

Counters
Counter ID
Counter Name
Counter Description
67175268
VS.SoHO.Att.RNC
Number of Softer Handovers

Initiated by RNC for RNC
Description
This counter provides the number of softer handover attempts in the RNC.This counter complies
with section "8.3.4 Active set update" in 3GPP TS 25.331 (v10.13.0).
Measurement point
one each time the RNC sends an ACTIVE SET UPDATE message to the UE during the softer
handover procedure.
Figure 1-374 Successful soft handover procedure
Issue 03 (2015-06-30)

838
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SoHO.Att.RNC
WRFD-020201
Intra Node B Softer

Handover
WRFD-020202
Intra RNC Soft Handover
Number of Soft Handover Attempts

Counters
Counter ID
Counter Name
Counter Description
67175266
VS.SHO.Att.RNC

Initiated by RNC for RNC
Description
These counters provide the number of soft handover (including softer handover) attempts in the
RNC.This counter complies with section "8.3.4 Active set update" in 3GPP TS 25.331
(v10.13.0).
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.
Issue 03 (2015-06-30)

839
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.Att.RNC
WRFD-020202
WRFD-020203

840
BSC6900 UMTS
Number of Successful Soft Handovers

Counters
Counter ID
Counter Name
Counter Description
67175267
VS.SHO.Succ.RNC

for RNC
Description
This counter provides the number of successful soft handovers (including softer handovers) in
the RNC.This counter complies with section "8.3.4 Active set update" in 3GPP TS 25.331
(v10.13.0).
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 successful, and the
RNC measures this counter.
Issue 03 (2015-06-30)

841
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.Succ.RNC
WRFD-020202
WRFD-020203
Number of Successful Softer Handovers

Counters
Counter ID
Counter Name
Counter Description
67175269
VS.SoHO.Succ.RNC
Number of Successful Softer

for RNC
Description
This counter provides the number of successful softer handovers in the RNC.This counter
complies with section "8.3.4 Active set update" in 3GPP TS 25.331 (v10.13.0).
Measurement point
an ACTIVE SET UPDATE COMPLETE message from the UE during the softer handover
procedure, the softer handover is considered successful, and the RNC measures this counter.
Issue 03 (2015-06-30)

842
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SoHO.Succ.RNC
WRFD-020201
Intra Node B Softer

Handover
WRFD-020202
Issue 03 (2015-06-30)

843
BSC6900 UMTS
Mean Number of UEs with One to Six Radio Link

Counters
Counter ID
Counter Name
Counter Description
67199432
VS.SHO.AS.1.RNC
Mean Number of UEs with

One Radio Link for RNC
67199434
VS.SHO.AS.2Soft.RNC

Two Uncombined Radio
Links for RNC
67199437
VS.SHO.AS.
3Soft2Softer.RNC

Three Radio Links and Two
Combined for RNC
67199436
VS.SHO.AS.3Soft.RNC

Three Uncombined Radio
Links for RNC
67199433
VS.SHO.AS.2Softer.RNC

Two Combined Radio Links
for RNC
67199435

Three Combined Radio
Links for RNC
67203933
VS.SHO.AS.4.RNC

Four Radio Links for RNC
67203934
VS.SHO.AS.5.RNC

Five Radio Links for RNC
67203935
VS.SHO.AS.6.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.The preceding counters comply with section "8.3.4 Active set
update" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

844
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AS.1.RNC
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
VS.SHO.AS.
3Soft2Softer.RNC
WRFD-020202
WRFD-020203
VS.SHO.AS.3Soft.RNC
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
VS.SHO.AS.2Soft.RNC
VS.SHO.AS.4.RNC
VS.SHO.AS.5.RNC
VS.SHO.AS.6.RNC
Number of Call Drops due to Soft Handover Failures

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67175283
VS.SHO.Drop.RNC
Number of Call Drops Due to

Soft Handover Failures for
RNC

845
BSC6900 UMTS
Description
This counter provides the number of call drops caused by soft handover failures in the RNC.This
counter complies with section "8.3.4 Active set update" in 3GPP TS 25.331 (v10.13.0).
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-378 A failed soft handover (timer expiry)
Formula
None
Unit
None
Issue 03 (2015-06-30)

846
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.Drop.RNC
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020203
1.10.28 Security Mode Measurement <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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190317
VS.IU.AttSecMode
Number of
SECURITY MODE
COMMAND
Messages Received
by RNC from CN
Earlier than
BSC6900
V900R011
67190318
VS.IU.SuccSecMode
Number of
SECURITY MODE
COMPLETE
Messages Sent by
RNC to CN
Earlier than
BSC6900
V900R011
67190319
VS.IU.RejSecMd.R
nl
Number of
SECURITY MODE
REJECT Messages
Sent by RNC to CN
(Radio Network
Layer Cause)
Earlier than
BSC6900
V900R011
67190320
VS.IU.RejSecMd.T
nl
Number of
SECURITY MODE
REJECT Messages
Sent by RNC to CN
(Transport Layer
Cause)
Earlier than
BSC6900
V900R011

847
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67190321
VS.IU.RejSecMd.N
AS
Number of
SECURITY MODE
REJECT Messages
Sent by RNC to CN
(NAS Cause)
Earlier than
BSC6900
V900R011
67190323
VS.IU.RejSecMd.U
nsp
Number of
SECURITY MODE
REJECT Messages
Sent by RNC to CN
(Unspecified
Failure)
Earlier than
BSC6900
V900R011
67190324
VS.UU.AttSecMod
e
Number of
SECURITY MODE
COMMAND
Messages Sent by
RNC to UE
Earlier than
BSC6900
V900R011
67190325
VS.UU.SuccSecMode
Number of
SECURITY MODE
COMPLETE
Messages Received
by RNC from UE
Earlier than
BSC6900
V900R011
None
Number of SECURITY MODE COMMAND Messages Received by RNC from CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.18 Security
Mode Control" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

848
BSC6900 UMTS
Measurement point
SECURITY MODE COMMAND message from the CN, the RNC measures this item.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.AttSecMode
WRFD-011401

849
BSC6900 UMTS
Number of SECURITY MODE COMPLETE Messages Sent from RNC to CN

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.18 Security Mode
Control" in 3GPP TS 25.413 (v10.10.0).
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.
security mode procedure is enabled. This counter is measured at point B when the RNC receives
a SECURITY MODE COMPLETE message from the UE.
Issue 03 (2015-06-30)

850
BSC6900 UMTS
Figure 1-381 Parallel handling of the security mode and RAB setup procedures
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.SuccSecMode
WRFD-011401
WRFD-171202

851
BSC6900 UMTS
Number of SECURITY MODE REJECT Messages Sent from RNC to CN for

Different Causes
Counters
Counter ID
Counter Name
Counter Description
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.The preceding counters
comply with section "8.18 Security Mode Control" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends the CN
a SECURITY MODE REJECT message, the RNC measures these items according to different
failure causes.
Issue 03 (2015-06-30)

852
BSC6900 UMTS
Figure 1-382 Security mode rejection procedure
security mode procedure is enabled. The measurement is triggered at point B when the RNC
sends an IU RELEASE REQUEST message to the CN after the security mode procedure fails
over the Uu interface. This counter is measured based on different causes.
Figure 1-383 Failed parallel handling of the security mode and RAB setup procedures
Issue 03 (2015-06-30)

853
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.RejSecMd.Rnl
WRFD-011401
WRFD-171202
WRFD-011401
WRFD-171202
WRFD-011401
WRFD-171202
WRFD-011401
WRFD-171202
VS.IU.RejSecMd.Tnl
VS.IU.RejSecMd.NAS
VS.IU.RejSecMd.Unsp
Number of SECURITY MODE COMMAND Messages Sent from RNC to UE

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.1.12 Security
mode control" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

854
BSC6900 UMTS
Figure 1-384 Security mode control procedure (RNC to UE)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.UU.AttSecMode
WRFD-011401
Number of SECURITY MODE COMPLETE Messages Received by RNC from UE

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190325
VS.UU.SuccSecMode
Number of SECURITY
MODE COMPLETE
Messages Received by RNC
from UE

855
BSC6900 UMTS
Description
This measurement item takes statistics of the number of SECURITY MODE COMPLETE
messages that the RNC receives from the UE.This counter complies with section "8.1.12 Security
mode control" in 3GPP TS 25.331 (v10.13.0).
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-385 Security mode control procedure (RNC to UE)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.UU.SuccSecMode
WRFD-011401

856
BSC6900 UMTS
1.10.29 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202970
VS.CSLoad.Erlang
.Equiv.RNC
Equivalent CS
Conversational
Erlang for RNC
Earlier than
BSC6900
V900R011
67192086
VS.CSLoad.MaxEr
lang.Equiv.RNC
Maximum
equivalent CS
Conversational
Erlang for RNC
Earlier than
BSC6900
V900R011
67204135
VS.R99PSLoad.UL
Thruput.RNC
Throughput of
Uplink PS R99
Traffic for RNC
Earlier than
BSC6900
V900R011
67192985
VS.R99PSLoad.Ma
xULThruput.RNC
Maximum
Throughput of
Uplink PS R99
Traffic for RNC
Earlier than
BSC6900
V900R011
67204136
VS.R99PSLoad.DL
Thruput.RNC
Throughput of
Downlink PS R99
Traffic for RNC
Earlier than
BSC6900
V900R011
67192988
VS.R99PSLoad.Ma
xDLThruput.RNC
Maximum
Throughput of
Downlink PS R99
Traffic for RNC
Earlier than
BSC6900
V900R011
67204137
VS.HSDPAPSLoad
.DLThruput.RNC
Throughput of PS
HSDPA Traffic for
RNC
Earlier than
BSC6900
V900R011
67192991
VS.HSDPAPSLoad
.MaxDLThruput.R
NC
Maximum
Throughput of PS
HSDPA Traffic for
RNC
Earlier than
BSC6900
V900R011
67204138
VS.HSUPAPSLoad
.ULThruput.RNC
Throughput of PS
HSUPA Traffic for
RNC
Earlier than
BSC6900
V900R011

857
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192994
VS.HSUPAPSLoad
.MaxULThruput.R
NC
Maximum
Throughput of PS
HSUPA Traffic for
RNC
Earlier than
BSC6900
V900R011
67204139
VS.MBMSPSLoad.
DLThruput.RNC
Throughput of PS
MBMS Traffic for
RNC
Earlier than
BSC6900
V900R011
67192997
VS.MBMSPSLoad.
MaxDLThruput.R
NC
Maximum
Throughput of PS
MBMS Traffic for
RNC
Earlier than
BSC6900
V900R011
73410501
VS.PSLoad.Thrup
ut.RNC
Average Total
Throughout of UL
and DL PS Services
for RNC
BSC6900
V900R012
73394059
VS.PSLoad.MaxTh
ruput.RNC
Maximum Total
Throughout of UL
and DL PS Services
for RNC
BSC6900
V900R012
73394070
VS.CS.Erlang.RNC
Erlang of CS
Services for RNC
BSC6900
V900R012
73429108
VS.AMR.SMLESS
CrstVoice.Erlang.E
quiv.RNC
Equivalent Erlang
Consumed by AMR
Voice Services
Using the Seamless
Crystal Voice
Feature for RNC
BSC6900
V900R017C00
73429111
VS.AMR.SMLESS
CrstVoice.MaxErla
ng.Equiv.RNC
Maximum
Equivalent Erlang
Consumed by AMR
Voice Services
Using the Seamless
Crystal Voice
Feature for RNC
BSC6900
V900R017C00
73445317
VS.PSLoad.TCPPr
oxy.DLThruput.R
NC
Amount of DL PS
Traffic Using TCP
Proxy for RNC
BSC6900
V900R017C00
73429276
VS.PSLoad.TCPPr
oxy.MaxDLThrupu
t.RNC
Maximum Amount
of DL PS Traffic
Using TCP Proxy for
RNC
BSC6900
V900R017C00

858
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73445319
VS.PSLoad.TCP.D
LThruput.RNC
Amount of DL PS
Traffic of TCP
Services for RNC
BSC6900
V900R017C00
73446317
VS.AMR.CrstVoic
eDeepCover.Erlang
.Equiv.RNC
AMR Services Using
Crystal Voice in
Deep Coverage for
RNC
BSC6900
V900R017C10
73430140
VS.AMR.CrstVoic
eDeepCover.MaxE
rlang.Equiv.RNC
Maximum
AMR Services Using
Crystal Voice in
Deep Coverage for
RNC
BSC6900
V900R017C10
73446342
VS.RadioAwaredV
ideo.Thruput.RNC
Traffic of Video
Services based on
RAN-Initiated
Service Awareness
for RNC
BSC6900
V900R017C10
None
Equivalent Erlang of CS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
67202970
VS.CSLoad.Erlang.Equiv.R
NC
Equivalent CS
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
Issue 03 (2015-06-30)

859
BSC6900 UMTS
accumulated equivalent Erlang values by the number of samples to obtain the mean equivalent
Erlang values of all the services in the CS domain, include the equivalent Erlang of all radio
links of Soft Handover.Each time a CS domain service is established, the RNC converts its rate
to the equivalent Erlang, and then increases the equivalent Erlang of the CS domain in the current
RNC. Each time a CS domain service is released, the RNC converts its rate to the equivalent
Erlang and decreases the equivalent Erlang of the CS domain in the current RNC.
Formula
None
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
VS.CSLoad.Erlang.Equiv.R
NC
MRFD-210403
License Management
Maximum Equivalent Erlang of CS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
67192086
iv.RNC
Maximum equivalent CS
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.
Issue 03 (2015-06-30)

860
BSC6900 UMTS
Formula
None
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
iv.RNC
MRFD-210403
License Management
Counter ID
Counter Name
Counter Description
67204135
RNC
Throughput of Uplink PS
R99 Traffic for RNC
UL Traffic of R99 PS Domain in RNC

Counters
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
Issue 03 (2015-06-30)

861
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
RNC
MRFD-210403
License Management
Maximum UL Traffic of R99 PS Domain in RNC

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

862
BSC6900 UMTS
DL Traffic of R99 PS Domain in RNC

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

863
BSC6900 UMTS
Maximum DL Traffic of R99 PS Domain in RNC

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

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204137
put.RNC
Throughput of PS HSDPA
Traffic for RNC

864
BSC6900 UMTS
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
Counter Name
Feature ID
Feature Name
put.RNC
WRFD-010610
HSDPA Introduction
Package
Maximum DL Traffic of HSDPA PS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
67192991
Thruput.RNC
Maximum Throughput of PS
HSDPA Traffic for RNC
Description
This measurement item provides the maximum downlink traffic of all the HSDPA services in
the PS domain within the RNC. The item is measured only when the RAN sharing function and
Issue 03 (2015-06-30)

865
BSC6900 UMTS
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
Counter Name
Feature ID
Feature Name
Thruput.RNC
WRFD-010610
HSDPA Introduction
Package
UL Traffic of HSUPA PS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
67204138
put.RNC
Throughput of PS HSUPA
Traffic for RNC
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.
Issue 03 (2015-06-30)

866
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
put.RNC
WRFD-010612
HSUPA Introduction
Package
Maximum UL Traffic of HSUPA PS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
67192994
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
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
Issue 03 (2015-06-30)

867
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
Thruput.RNC
WRFD-010612
HSUPA Introduction
Package
DL Traffic of MBMS or IMB PS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
67204139
put.RNC
Throughput of PS MBMS
Traffic for RNC
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
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
put.RNC
WRFD-010616
MBMS Introduction
Package

868
BSC6900 UMTS
Maximum DL Traffic of MBMS or IMB PS Domain in RNC

Counters
Counter ID
Counter Name
Counter Description
67192997
VS.MBMSPSLoad.MaxDL
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
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMSPSLoad.MaxDL
Thruput.RNC
WRFD-010616
MBMS Introduction
Package
Average Total Throughout of UL and DL PS Services for RNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73410501
VS.PSLoad.Thruput.RNC
Average Total Throughout of

UL and DL PS Services for
RNC

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

Counters
Counter ID
Counter Name
Counter Description
73394059
VS.PSLoad.MaxThruput.R
NC
Maximum Total Throughout

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.
Issue 03 (2015-06-30)

870
BSC6900 UMTS
Measurement point
The total throughput of uplink and downlink PS services in the RNC is sampled periodically
every five seconds. At the end of the measurement period, the maximum throughput is obtained.
The RLC header is not included and the retransmission data is included in the counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PSLoad.MaxThruput.R
NC
MRFD-210403
License Management
Counter ID
Counter Name
Counter Description
73394070
VS.CS.Erlang.RNC
Erlang of CS Services for

RNC
Erlang of CS Services for RNC

Counters
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
Issue 03 (2015-06-30)

871
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CS.Erlang.RNC
MRFD-210403
License Management
Equivalent Erlang Consumed by AMR Voice Services Using the Seamless Crystal
Voice Feature for RNC
Counters
Counter ID
Counter Name
Counter Description
73429108
e.Erlang.Equiv.RNC
Equivalent Erlang
RNC
Description
This counter provides the equivalent Erlang consumed by CS AMR voice services (AMR-WB
and AMR-NB voice services) using the seamless crystal voice feature in an RNC. This counter
applies only to the scenario where the RAN sharing and MOCN features are both disabled. This
counter does not apply to the UEs whose best cells are under the DRNC.
Measurement point
The system takes samples of the equivalent Erlang consumed by CS AMR voice services using
the seamless crystal voice feature every five seconds in a measurement period. At the end of a
measurement period, the system obtains the value of this counter by dividing the accumulated
sampling value in the period by the number of times sampled. The counter value includes the
equivalent Erlang consumed by CS AMR voice services on all RLs during a soft handover. When
a UE initiates a CS AMR voice service and the service uses the seamless crystal voice feature,
the system converts the CS rate into the equivalent Erlang and increases the equivalent Erlang
accordingly. When a CS AMR voice service is released or the seamless crystal voice feature is
deactivated for a CS AMR voice service, the system decreases equivalent Erlang accordingly.
Formula
None
Unit
Erl
Issue 03 (2015-06-30)

872
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
e.Erlang.Equiv.RNC
WRFD-170201
Maximum Equivalent Erlang Consumed by AMR Voice Services Using the

Seamless Crystal Voice Feature for RNC
Counters
Counter ID
Counter Name
Counter Description
73429111
e.MaxErlang.Equiv.RNC

RNC
Description
(AMR-WB and AMR-NB voice services) using the seamless crystal voice feature in an RNC.
This counter applies only to the scenario where the RAN sharing and MOCN features are both
disabled. This counter does not apply to the UEs whose best cells are under the DRNC.
Measurement point
The system takes samples of the equivalent Erlang consumed by CS AMR voice services using
the seamless crystal voice feature every five seconds in a measurement period. At the end of a
measurement period, the system obtains the maximum equivalent Erlang consumed by CS AMR
voice services using the seamless crystal voice feature in an RNC. This maximum value includes
the equivalent Erlang consumed by CS AMR voice services on all RLs during a soft handover.
When a UE initiates a CS AMR voice service and the service uses the seamless crystal voice
feature, the system converts the CS rate into the equivalent Erlang and increases the equivalent
Erlang accordingly. When a CS AMR voice service is released or the seamless crystal voice
feature is deactivated for a CS AMR voice service, the system decreases equivalent Erlang
accordingly.
Formula
None
Unit
Erl
Issue 03 (2015-06-30)

873
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
e.MaxErlang.Equiv.RNC
WRFD-170201
Amount of DL PS Traffic Using TCP Proxy for RNC

Counters
Counter ID
Counter Name
Counter Description
73445317
hruput.RNC
Amount of DL PS Traffic
Using TCP Proxy for RNC
Description
This counter provides the amount of DL PS traffic that uses TCP proxy on the RNC. It is
measured only when the RAN sharing and MOCN features are both disabled.
Measurement point
The RNC takes samples of the amount of DL PS traffic (unit: kbit/s) that uses the TCP proxy
function every five seconds in a measurement period. At the end of the measurement period, the
RNC obtains the value of this counter by dividing the accumulated traffic volume by the number
of times sampled. This counter is measured at the RLC layer. It includes soft handover traffic
and excludes RLC headers.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
hruput.RNC
WRFD-170202
TCP Proxy

874
BSC6900 UMTS
Maximum Amount of DL PS Traffic Using TCP Proxy for RNC

Counters
Counter ID
Counter Name
Counter Description
73429276
DLThruput.RNC
Maximum Amount of DL PS
Traffic Using TCP Proxy for
RNC
Description
This counter provides the maximum amount of DL PS traffic that uses TCP proxy on the RNC.
It is measured only when the RAN sharing and MOCN features are both disabled.
Measurement point
The RNC takes samples of the amount of DL PS traffic (unit: kbit/s) that uses the TCP proxy
function every five seconds in a measurement period. At the end of the measurement period, the
RNC obtains the maximum amount of DL PS traffic that uses the TCP proxy function. This
counter is measured at the RLC layer. It includes soft handover traffic and excludes RLC headers.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
DLThruput.RNC
WRFD-170202
TCP Proxy
Amount of DL PS Traffic of TCP Services for RNC

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73445319
t.RNC
Amount of DL PS Traffic of
TCP Services for RNC

875
BSC6900 UMTS
Description
This counter provides the amount of DL PS traffic of the TCP services on the RNC. It is measured
only when the RAN sharing and MOCN features are both disabled.
Measurement point
The RNC takes samples of the amount of DL PS traffic (unit: kbit/s) of TCP services every five
seconds in a measurement period. At the end of the measurement period, the RNC obtains the
value of this counter by dividing the accumulated traffic volume by the number of times sampled.
This counter is measured at the RLC layer. It includes soft handover traffic and excludes RLC
headers.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
t.RNC
WRFD-170202
TCP Proxy
Equivalent Erlang of AMR Services Using Crystal Voice in Deep Coverage for RNC
Counters
Counter ID
Counter Name
Counter Description
73446317
ver.Erlang.Equiv.RNC
Equivalent Erlang of AMR

Services Using Crystal Voice
in Deep Coverage for RNC
Description
This counter provides the equivalent Erlang of CS AMR services (AMR-WB and AMR-NB)
that use the Crystal Voice in Deep Coverage feature in an RNC. This counter is measured only
when both the RAN sharing and MOCN features are disabled. This counter does not apply to
the UEs whose best cells are under the DRNC.
Measurement point
Deep Coverage feature every five seconds in a measurement period. At the end of the
Issue 03 (2015-06-30)

876
BSC6900 UMTS
value by the number of times sampled. The counter value includes the equivalent Erlang on all
links during soft handovers. When a CS AMR service is being established and the Crystal Voice
in Deep Coverage feature is enabled, the service rate of the CS AMR service is converted to the
equivalent Erlang, which is then calculated into this counter. When a CS AMR service is being
released or this feature is disabled for a CS AMR service, the service rate is converted to the
equivalent Erlang, which is then subtracted from this counter.
Formula
None
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
ver.Erlang.Equiv.RNC
WRFD-171201

Coverage
Maximum Equivalent Erlang of AMR Services Using Crystal Voice in Deep

Coverage for RNC
Counters
Counter ID
Counter Name
Counter Description
73430140
ver.MaxErlang.Equiv.RNC

of AMR Services Using
Coverage for RNC
Description
This counter provides the maximum equivalent Erlang of CS AMR services (AMR-WB and
AMR-NB) that use the Crystal Voice in Deep Coverage feature in an RNC. This counter is
measured only when both the RAN sharing and MOCN features are disabled. This counter does
not apply to the UEs whose best cells are under the DRNC.
Measurement point
Deep Coverage feature every five seconds in a measurement period. At the end of the
measurement period, the system obtains the maximum equivalent Erlang of AMR services using
Crystal Voice in Deep Coverage.The counter value includes the equivalent Erlang on all links
Issue 03 (2015-06-30)

877
BSC6900 UMTS
during soft handovers. When a CS AMR service is being established and the Crystal Voice in
Deep Coverage feature is enabled, the service rate of the CS AMR service is converted to the
equivalent Erlang, which is then calculated into this counter. When a CS AMR service is being
released or this feature is disabled for a CS AMR service, the service rate is converted to the
equivalent Erlang, which is then subtracted from this counter.
Formula
None
Unit
Erl
Related Features
Counter Name
Feature ID
Feature Name
ver.MaxErlang.Equiv.RNC
WRFD-171201

Coverage
Traffic of Video Services based on RAN-Initiated Service Awareness for RNC

Counters
Counter ID
Counter Name
Counter Description
73446342
uput.RNC
Traffic of Video Services

based on RAN-Initiated
Service Awareness for RNC
Description
This counter provides the amount of traffic of uplink and downlink video services based on
RAN-initiated service awareness on the RNC. This counter is measured only when the video
service measurement function is enabled but the RAN sharing and MOCN features are both
disabled. For details about the video service measurement function, see Radio-Aware Video
Precedence Feature Parameter Description.
Measurement point
The system samples the traffic (unit: kbit/s) of uplink and downlink video services based on
RAN-initiated service awareness every 5s in a measurement period. At the end of the
measurement period, the system divides the accumulated traffic by the number of times sampled
to obtain the traffic of uplink and downlink video services based on RAN-initiated service
awareness in this measurement period. The traffic of video services is measured at the RLC
layer, including the traffic of retransmitted video packets and the video traffic of UEs during
soft handovers and excluding RLC headers.
Issue 03 (2015-06-30)

878
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
uput.RNC
WRFD-171210
Radio-Aware Video
Precedence
1.11 Measurement of ROAMCNOperator Performance

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

Under MOCN
1.11.1 Roaming UE Registration Measurement Under MOCN

(MOCN.ROAM.CNOPERATOR)
Overview
Roaming UE registration measurement under MOCN provides the number of times that a
roaming UE is registered in an operator under the MOCN after the roaming UE starts the CS or
PS registration.
Issue 03 (2015-06-30)

879
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73423374
VS.Roam.Cnoperat
or.MOCN.Num
Number of Roaming
UEs that Is
Registered In Local
Operator Under
MOCN for the First
Time
BSC6900
V900R013
None
Number of Roaming UEs that Is Registered In Local Operator Under MOCN for
the First Time
Counters
Counter ID
Counter Name
Counter Description
73423374
VS.Roam.Cnoperator.MOC
N.Num
Number of Roaming UEs

that Is Registered In Local
Operator Under MOCN for
the First Time
Description
This counter provides the number of times that a roaming UE is registered in the local operator
under the MOCN to indicate that when the operator of the roaming UE has signed the roaming
contract with multiple operators under the MOCN, the RNC routes the roaming UEs to different
operators according to the preset proportion.This counter complies with section "7.1.4 Nonsupporting UEs in a MOCN configuration" in 3GPP TS 23.251 (v6.0.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving an
RRC setup request from a roaming UE with the cause value indicating registration, the RNC
starts the MOCN roaming. This counter is measured when the RNC receives an RANAP
DIRECT TRANSFER message containing the Redirection Complete IE from the CN.
Issue 03 (2015-06-30)

880
BSC6900 UMTS
Figure 1-386 INIT UE MESSAGE Redirect procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Roam.Cnoperator.MOC
N.Num
WRFD-02131106
Routing Roaming UEs in

Proportion
1.12 Measurement of Cell Performance(UCELL)

Overview
The measurement object type CELL is used to measure the performance of a cell. The cell
belongs to the RNC and contains one measurement set: CELL.
Issue 03 (2015-06-30)

881
BSC6900 UMTS
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
ALGO.Cell
Algorithm Measurement <per Cell>
ALGO2.Cell
Algorithm Measurement 2 <per Cell>
BLER.Cell
BLER Measurement <per Cell>
BOOST.CELL
BOOST Measurement <per Cell>
CBS.Cell
CBS Measurement <per Cell>
CCH.Cell
Common Channel Measurement <per Cell>
CELLUPDATE.Cell
Cell Update Measurement <per Cell>
Channel.Upswitch.Cell
Measurement of Channel Reconfiguration to

DCH <per Cell>
CM.Cell
Compressed Mode Measurement <per Cell>
CSService.Cell
CS Service Quality Measurement <per Cell>
EFACH.Cell
EFACH Measurement <per Cell>
EPCH.Cell
EPCH Measurement <per Cell>
ERACH.Cell
ERACH Measurement <per Cell>
EVQI.CELL
Voice Quality EVQI 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
Inter-RAT Handover Measurement <per

Cell>
IU.Sig.Rel.Cell
Iu Singaling Connection Release

Measurement<per Cell>
IUB.Cell
Iub Interface Measurement <per Cell>
LCS.CELL
LCS Service Measurement <per Cell>
MBMS.Cell
MBMS Measurement <per Cell>
MEAR.Report.Cell
RRC MR Measurement <per Cell>
PAGE.CELL
Paging Measurement <per Cell>
Parking.Cell
Parking Measurement<per Cell>
PLMN.CELL
CNOperator Measurement <per Cell>

882
BSC6900 UMTS
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
PSService.Cell
PS service quality Measurement <per Cell>
PTT.Cell
PTT Measurement <per Cell>
QOS.Cell
QoS Measurement <per Cell>
RAB.EstabCS.Cell
CS RAB Setup Measurement <per Cell>
RAB.EstabPS.Cell
PS RAB Setup Measurement <per Cell>
RAB.EstFailCs.Cell
CS RAB Setup Failure Measurement <per

Cell>
RAB.EstFailPs.Cell
PS RAB Setup Failure Measurement <per

Cell>
RAB.ModCs.Cell
CS RAB Modification Measurement <per

Cell>
RAB.ModPs.Cell
PS RAB Modification Measurement <per

Cell>
RAB.MultiRab.Cell
Multi-RAB Service Measurement <per Cell>
RAB.RelAbnormal.Cell
RAB Release Measurement <per Cell>
RB.Cell
RB Procedure Measurement <per Cell>
RESERVE.Cell
Reserved Counter Measurement <per Cell>
RLC.Cell
RLC Measurement <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 Status Measurement <per Cell>
RRC.UECapab.Cell
UE Capability Measurement <per Cell>
RTWPTCP.Cell
TX and RX Power Measurement <per Cell>
SHO.Cell
Soft Handover Measurement <per Cell>
SIR.Cell
Target SIR Measurement <per Cell>
SPI.Cell
SPI Measurement <per Cell>
THRUPUT.Cell
Traffic Volume and Data Rate Measurement

<per Cell>
TRFFIC.Cell
Traffic Measurement <per Cell>

883
BSC6900 UMTS
FunctionSubSet
FunctionSubSet Name
U2LTE.HO.Cell
UL Interoperability Measurement <per Cell>
URAUPDATE.Cell
URA Update Measurement <per Cell>
VIDEO.CELL
Video Service Quality Measurement <per

Cell>
WLAN.Cell
WLAN Measurement <per Cell>
1.12.1 Algorithm Measurement <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. When the
amount of radio resources occupied by a cell exceeds the basic congestion threshold, the cell
enters the basic congestion state. In this case, the RNC performs load reshuffling actions in the
cell to reduce the cell load and increase the access success rate.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180678
VS.AMR.DL.Rate
Up
Number of DL Rate
Increases for AMR
Services for Cell
Earlier than
BSC6900
V900R011
67190519
VS.AMR.DL.RateDown
Number of DL Rate
Decreases for AMR
Services for Cell
Earlier than
BSC6900
V900R011
67190520
VS.AMR.UL.Rate
Up
Number of UL Rate
Increases for AMR
Services for Cell
Earlier than
BSC6900
V900R011
67180677
VS.AMR.UL.RateDown
Number of UL Rate
Decreases for AMR
Services for Cell
Earlier than
BSC6900
V900R011
67180675
VS.DCCC.Succ.F2
D
Number of
Successful Channel
Conversions from
FACH to DCH for
Cell
Earlier than
BSC6900
V900R011

884
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180676
VS.DCCC.Succ.D2
F
Number of
Successful Channel
Conversions from
DCHs to FACHs for
Cell
Earlier than
BSC6900
V900R011
67192583
VS.DCCC.Att.F2P
Number of State
Transfer Attempts
from CELL_FACH
to CELL_PCH for
Cell
Earlier than
BSC6900
V900R011
67192584
VS.DCCC.Succ.F2
P
Number of
Successful State
Transfers from
CELL_FACH to
CELL_PCH for Cell
Earlier than
BSC6900
V900R011
67192587
VS.DCCC.AttDow
nsizing.DL.Thr
Number of Downlink
DCH DCCC
Downsizing
Attempts Based on
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011
67192588
VS.DCCC.SuccDo
wnsizing.DL.Thr
Number of
Successful DL DCH
DCCC Downsizings
Based on
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011
67192589
VS.DCCC.AttDow
nsizing.DL.Cov
Number of Downlink
DCH DCCC
Downsizing
Attempts Based on
Coverage (QoS) for
Cell
Earlier than
BSC6900
V900R011
67192590
VS.DCCC.SuccDo
wnsizing.DL.Cov
Number of
Successful DL DCH
DCCC Downsizings
Based on Coverage
(QoS) for Cell
Earlier than
BSC6900
V900R011

885
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192591
VS.DCCC.AttDow
nsizing.DL.Cong
Number of Downlink
DCH DCCC
Downsizing
Attempts Based on
Resource
Congestion
Algorithm for Cell
Earlier than
BSC6900
V900R011
67192592
VS.DCCC.SuccDo
wnsizing.DL.Cong
Number of
Successful DL DCH
DCCC Downsizings
Based on Resource
Congestion
Algorithm for Cell
Earlier than
BSC6900
V900R011
67189852
VS.LCC.OLC.UL.
Num
Number of UL
Overload
Congestions for Cell
Earlier than
BSC6900
V900R011
67189853
VS.LCC.OLC.DL.
Num
Number of DL
Overload
Earlier than
BSC6900
V900R011
67203402
VS.LCC.OLC.UL.
Time
Duration of UL
Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67203403
VS.LCC.OLC.DL.
Time
Duration of DL
Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67191150
VS.LCC.OLC.HSD
PA.UserRel
Number of HSDPA
UEs Released Due to
Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67192549
VS.LCC.OLC.D2C
Number of UEs
Transferring BE
Service to Common
Channel in Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67203991
VS.LCC.LDR.Tim
e.ULPower
Duration of Cell in
LDR State Due to UL
Power Congestion
for Cell
Earlier than
BSC6900
V900R011
67203992
VS.LCC.LDR.Tim
e.DLPower
Duration of Cell in
LDR State Due to DL
Power Congestion
for Cell
Earlier than
BSC6900
V900R011

886
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203993
VS.LCC.LDR.Tim
e.DLCode
Duration of Cell in
LDR State Due to DL
Code Resource
Congestion for Cell
Earlier than
BSC6900
V900R011
67203994
VS.LCC.LDR.Tim
e.ULCE
Duration of Cell in
LDR State Due to UL
CE Resource
Congestion
Earlier than
BSC6900
V900R011
67203995
VS.LCC.LDR.Tim
e.DLCE
Duration of Cell in
LDR State Due to DL
CE Resource
Congestion
Earlier than
BSC6900
V900R011
67203996
VS.LCC.LDR.Tim
e.ULIub
Duration of Cell in
LDR State Due to UL
Iub Transmission
Resource
Congestion for Cell
Earlier than
BSC6900
V900R011
67203997
VS.LCC.LDR.Tim
e.DLIub
Duration of Cell in
LDR State Due to DL
Iub Transmission
Resource
Congestion for Cell
Earlier than
BSC6900
V900R011
67192637
VS.LCC.LDR.Num
.ULPower
Number of Times a
Cell Is in LDR State
Due to UL Power
Congestion for Cell
Earlier than
BSC6900
V900R011
67192638
VS.LCC.LDR.Num
.DLPower
Number of Times a
Due to DL Power
Congestion for Cell
Earlier than
BSC6900
V900R011
67192639
VS.LCC.LDR.Num
.DLCode
Number of Times a
Due to DL Code
Resource
Congestion for Cell
Earlier than
BSC6900
V900R011
67192640
VS.LCC.LDR.Num
.ULCE
Number of Times a
Due to UL CE
Resource
Congestion for Cell
Earlier than
BSC6900
V900R011

887
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192641
VS.LCC.LDR.Num
.DLCE
Number of Times a
Due to DL CE
Resource
Congestion for Cell
Earlier than
BSC6900
V900R011
67192642
VS.LCC.LDR.Num
.ULIub
Number of Times a
Due to UL Iub
Transmission
Resource
Congestion for Cell
Earlier than
BSC6900
V900R011
67192643
VS.LCC.LDR.Num
.DLIub
Number of Times a
Due to DL Iub
Transmission
Resource
Congestion for Cell
Earlier than
BSC6900
V900R011
67192644
VS.LCC.LDR.HSU
PA.InterFreq
Number of HSUPA
UEs Performing
Inter-Frequency
Load Handovers in
Basic Congestion for
Cell
Earlier than
BSC6900
V900R011
67192645
VS.LCC.LDR.HSU
PA.InterRATPS
Number of HSUPA
UEs Performing PS
Inter-RAT Handover
in Basic Congestion
for Cell
Earlier than
BSC6900
V900R011
67192646
VS.LCC.OLC.UL.
TF
Number of UEs
Performing BE
Service TF Control
in UL Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67192647
VS.LCC.OLC.UL.
UserRel
Number of UEs
Released Due to UL
Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67192648
VS.LCC.OLC.HSU
PA.UserRel
Number of HSUPA
UEs Released during
Overload
Congestion for Cell
Earlier than
BSC6900
V900R011

888
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192649
VS.LCC.OLC.DL.
TF
Number of UEs
Performing BE
Service TF Control
in DL Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67192650
VS.LCC.OLC.DL.
UserRel
Number of UEs
Released Due to DL
Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67192916
VS.RAC.NewCallR
eq.Fail.HSDPANu
m.Cong
Number of Failed
Admissions Due to
HSDPA User
Number Exceeding
Threshold During
RAB Establishment
for Cell
Earlier than
BSC6900
V900R011
67192917
VS.RAC.NewCallR
eq.Fail.HSUPANu
m.Cong
Number of Failed
Admissions Due to
HSUPA User
Number Exceeding
Threshold During
RAB Establishment
for Cell
Earlier than
BSC6900
V900R011
67192937
VS.RAC.NewCallR
eq.Preempt.Cong
Number of
Preemptions During
RAB Establishment
for Cell
Earlier than
BSC6900
V900R011
67192939
VS.RAC.SHO.Fail.
ULPower.Cong
Number of Failed
Requests for UL
Power Resources
During SHO for Cell
Earlier than
BSC6900
V900R011
67192940
VS.RAC.SHO.Fail.
DLPower.Cong
Number of Failed
Requests for DL
Power Resources
During SHO for Cell
Earlier than
BSC6900
V900R011
67192918
VS.RAC.SHO.Fail.
Code.Cong
Number of Failed
Requests for Code
Resources During
SHO for Cell
Earlier than
BSC6900
V900R011

889
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192919
VS.RAC.SHO.Fail.
ULIUBBand.Cong
Number of Failed
Requests for UL Iub
Transmission
Resources During
SHO for Cell
Earlier than
BSC6900
V900R011
67192920
VS.RAC.SHO.Fail.
DLIUBBand.Cong
Number of Failed
Requests for DL Iub
Transmission
Resources During
SHO for Cell
Earlier than
BSC6900
V900R011
67192921
VS.RAC.SHO.Fail.
HSUPANum.Cong
Number of Failed
Admissions Due to
HSUPA User
Number Exceeding
Threshold During
SHO for Cell
Earlier than
BSC6900
V900R011
67192943
VS.RAC.DCCC.Fa
il.ULPower.Cong
Number of Failed
Requests for UL
Power Resources
During DCCC for
Cell
Earlier than
BSC6900
V900R011
67192944
VS.RAC.DCCC.Fa
il.DLPower.Cong
Number of Failed
Requests for DL
Power Resources
During DCCC for
Cell
Earlier than
BSC6900
V900R011
67192922
VS.RAC.DCCC.Fa
il.Code.Cong
Number of Failed
Requests for DL
Code Resources
During DCCC for
Cell
Earlier than
BSC6900
V900R011
67192923
VS.RAC.TrChSwit
ch.Fail.ULCE.Con
g
Number of Failed
Requests for UL CE
Resources During
Channel Type
Switch for Cell
Earlier than
BSC6900
V900R011
67192924
VS.RAC.TrChSwit
ch.Fail.DLCE.Con
g
Number of Failed
Requests for DL CE
Resources During
Channel Type
Switch for Cell
Earlier than
BSC6900
V900R011

890
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192945
VS.RAC.TrChSwit
ch.Fail.ULPower.C
ong
Number of Failed
Requests for UL
Power Resources
During Channel
Type Switch for Cell
Earlier than
BSC6900
V900R011
67192946
VS.RAC.TrChSwit
ch.Fail.DLPower.C
ong
Number of Failed
Requests for DL
Power Resources
During Channel
Earlier than
BSC6900
V900R011
67192925
VS.RAC.TrChSwit
ch.Fail.Code.Cong
Number of Failed
Requests for Code
Resources During
Channel Type
Switch for Cell
Earlier than
BSC6900
V900R011
67192926
VS.RAC.TrChSwit
ch.Fail.ULIUBBan
d.Cong
Number of Failed
Requests for UL Iub
Transmission
Resources During
Channel Type
Switch for Cell
Earlier than
BSC6900
V900R011
67192927
VS.RAC.TrChSwit
ch.Fail.DLIUBBan
d.Cong
Number of Failed
Requests for DL Iub
Transmission
Resources During
Channel Type
Switch for Cell
Earlier than
BSC6900
V900R011
67192928
VS.RAC.TrChSwit
ch.Fail.HSDPANu
m.Cong
Number of Failed
Admissions Due to
HSDPA User
Number Exceeding
Threshold During
Channel Type
Switch for Cell
Earlier than
BSC6900
V900R011
67192929
VS.RAC.TrChSwit
ch.Fail.HSUPANu
m.Cong
Number of Failed
Admissions Due to
HSUPA User
Number Exceeding
Threshold During
Channel Type
Switch for Cell
Earlier than
BSC6900
V900R011

891
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192941
VS.RAC.HHO.Fail
.ULPower.Cong
Number of Failed
Requests for UL
Power Resources
During HHO for Cell
Earlier than
BSC6900
V900R011
67192942
VS.RAC.HHO.Fail
.DLPower.Cong
Number of Failed
Requests for DL
Power Resources
During HHO for Cell
Earlier than
BSC6900
V900R011
67192930
VS.RAC.HHO.Fail
.ULIUBBand.Cong
Number of Failed
Requests for UL Iub
Transmission
Resources During
HHO for Cell
Earlier than
BSC6900
V900R011
67192931
VS.RAC.HHO.Fail
.DLIUBBand.Cong
Number of Failed
Requests for DL Iub
Transmission
Resources During
HHO for Cell
Earlier than
BSC6900
V900R011
67192932
VS.RAC.HHO.Fail
.HSDPANum.Cong
Number of Failed
Admissions Due to
HSDPA User
Number Exceeding
Threshold During
HHO for Cell
Earlier than
BSC6900
V900R011
67192933
VS.RAC.HHO.Fail
.HSUPANum.Cong
Number of Failed
Admissions Due to
HSUPA User
Number Exceeding
Threshold During
HHO for Cell
Earlier than
BSC6900
V900R011
67192938
VS.RAC.HHO.Pre
empt.Cong
Number of
Preemptions During
HHO for Cell
Earlier than
BSC6900
V900R011
67194970
VS.LCC.OLC.MB
MS.PTM.RBRel
Number of MBMS
PTM Service
Releases in Overload
Congestion for Cell
Earlier than
BSC6900
V900R011
67194971
VS.LCC.OLC.MB
MS.PTP.RBRel
Number of MBMS
PTP Service
Releases in Overload
Congestion for Cell
Earlier than
BSC6900
V900R011

892
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190435
VS.LCC.LDR.InterFreq
Number of UEs
Performing InterFrequency Load
Handovers in Basic
Congestion for Cell
Earlier than
BSC6900
V900R011
67191151
VS.LCC.LDR.HSD
PA.InterFreq
Number of HSDPA
UEs Performing
Inter-Frequency
Load Handovers in
Cell
Earlier than
BSC6900
V900R011
67190436
VS.LCC.LDR.UL.
BERateDown
Number of UEs
Performing BE
Service Downsizing
in UL Basic
Congestion
Earlier than
BSC6900
V900R011
67190437
VS.LCC.LDR.DL.
BERateDown
Number of UEs
Performing BE
Service Downsizing
in DL Basic
Congestion
Earlier than
BSC6900
V900R011
67190438
VS.LCC.LDR.UL.
QosReNego
Number of UEs
Performing
Uncontrollable RealTime Service QoS
Renegotiation in UL
Cell
Earlier than
BSC6900
V900R011
67190439
VS.LCC.LDR.DL.
QosReNego
Number of UEs
Performing
Uncontrollable RealTime Service QoS
Renegotiation in DL
Cell
Earlier than
BSC6900
V900R011
67190440
VS.LCC.LDR.InterRATCS
Number of UEs
Performing CS InterRAT Handovers in
Cell
Earlier than
BSC6900
V900R011

893
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190441
VS.LCC.LDR.InterRATPS
Number of UEs
Performing PS InterRAT Handovers in
Cell
Earlier than
BSC6900
V900R011
67191152
VS.LCC.LDR.HSD
PA.InterRATPS
Number of HSDPA
UEs Performing PS
Inter-RAT
Handovers in Basic
Congestion for Cell
Earlier than
BSC6900
V900R011
67192426
VS.LCC.LDR.AM
RRateUL
Number of UEs
Performing AMR
Rate Decrease in UL
Cell
Earlier than
BSC6900
V900R011
67192427
VS.LCC.LDR.AM
RRateDL
Number of UEs
Performing AMR
Rate Decrease in DL
Cell
Earlier than
BSC6900
V900R011
67192397
VS.LCC.LDR.Cod
eAdj.Att
Number of UEs
Performing Code
Adjustment
Attempts in DL
Cell
Earlier than
BSC6900
V900R011
67192398
VS.LCC.LDR.Mb
msPowerDec
Number of MBMS
Services Performing
Power Decreasing in
Cell
Earlier than
BSC6900
V900R011
67189856
VS.PUC.High.Offs
et.Updt
Number of Qoffset
Updates Due to
Heavy Load for Cell
Earlier than
BSC6900
V900R011
67189857
VS.PUC.Light.Offs
et.Updt
Number of Qoffset
Updates Due to Light
Load for Cell
Earlier than
BSC6900
V900R011
67189858
VS.PUC.Norm.Offs
et.Updt
Number of Qoffset
Updates Due to
Normal Load for Cell
Earlier than
BSC6900
V900R011

894
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190442
VS.PUC.Light.IntS
rch.Updt
Number of
Sintersearch Updates
Due to Light Load
for Cell
Earlier than
BSC6900
V900R011
67190443
VS.PUC.Norm.IntS
rch.Updt
Number of
Due to Normal Load
for Cell
Earlier than
BSC6900
V900R011
67190444
VS.PUC.High.IntS
rch.Updt
Number of
Due to Heavy Load
for Cell
Earlier than
BSC6900
V900R011
67189859
VS.RAC.HHO.Fail
.Code.Cong
Number of Failed
Requests for Code
Resources During
HHO for Cell
Earlier than
BSC6900
V900R011
67181079
VS.RAC.HHOCallAcc
Number of
Successful Cell
Resource Requests
During HHO for Cell
Earlier than
BSC6900
V900R011
67181074
VS.RAC.HHOCallReq
Number of Cell
Resource Requests
During HHO for Cell
Earlier than
BSC6900
V900R011
67181076
VS.RAC.NewCallAcc
Number of
Successful Cell
Resource Requests
During RAB
Establishment for
Cell
Earlier than
BSC6900
V900R011
67181071
VS.RAC.NewCallReq
Number of Cell
Resource Requests
During RAB
Establishment for
Cell
Earlier than
BSC6900
V900R011
67181078
VS.RAC.ReconfigCallAcc
Number of
Successful Cell
Resource Requests
Due to UE RAB
Reconfiguration for
Cell
Earlier than
BSC6900
V900R011

895
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67181073
VS.RAC.ReconfigCallReq
Number of Cell
Resource Requests
Due to UE RAB
Reconfiguration for
Cell
Earlier than
BSC6900
V900R011
67181077
VS.RAC.SHOCallAcc
Number of
Successful Cell
Resource Requests
During SHO for Cell
Earlier than
BSC6900
V900R011
67181072
VS.RAC.SHOCallReq
Number of Cell
Resource Requests
During SHO for Cell
Earlier than
BSC6900
V900R011
67181080
VS.RAC.TrChSwit
chCallAcc
Number of
Successful Cell
Resource Requests
During Channel
Earlier than
BSC6900
V900R011
67181075
VS.RAC.TrChSwit
chCallReq
Number of Cell
Resource Requests
During Channel
Earlier than
BSC6900
V900R011
67199664
VS.RAC.DL.EqvUserNum
Mean Number of DL
Equivalent Voice
UEs in CEL_DCH
State for Cell
Earlier than
BSC6900
V900R011
67199663
VS.RAC.UL.EqvUserNum
Mean Number of UL
Equivalent Voice
UEs in CEL_DCH
State for Cell
Earlier than
BSC6900
V900R011
67204134
VS.Cell.DynShutD
own.Time
Duration of Cell
Dynamic Shutdown
Due to Automatic
Shutdown for Cell
BSC6900
V900R012
67199736
VS.Cell.UnavailTime
Cell Unavailability
Duration
Earlier than
BSC6900
V900R011
67202567
VS.LC.ULCreditU
sed.Mean
Mean Usage of UL
Credit for Cell
Earlier than
BSC6900
V900R011

896
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191165
VS.LC.ULCreditU
sed.Max
Maximum Usage of
UL Credit for Cell
Earlier than
BSC6900
V900R011
67191166
VS.LC.ULCreditU
sed.Min
Minimum Usage of
UL Credit for Cell
Earlier than
BSC6900
V900R011
67202570
VS.LC.DLCreditU
sed.Mean
Mean Usage of DL
Credit for Cell
Earlier than
BSC6900
V900R011
67191167
VS.LC.DLCreditU
sed.Max
Maximum Usage of
DL Credit for Cell
Earlier than
BSC6900
V900R011
67191168
VS.LC.DLCreditU
sed.Min
Minimum Usage of
DL Credit for Cell
Earlier than
BSC6900
V900R011
67202917
VS.CellBreath.CPI
CHMin.Time
Duration of
Minimum Values of
CPICH Power Due to
Cell Breathing for
Cell
Earlier than
BSC6900
V900R011
67202918
VS.CellBreath.CPI
CHMax.Time
Duration of
Maximum Values of
CPICH Power Due to
Cell Breathing for
Cell
Earlier than
BSC6900
V900R011
67190846
VS.CellBreath.CPI
CHUp
Number of Upward
CPICH Power
Adjustments Due to
Cell Breathing for
Cell
Earlier than
BSC6900
V900R011
67190847
VS.CellBreath.CPI
CHDown
Number of
Downward CPICH
Power Adjustments
Due to Cell
Breathing for Cell
Earlier than
BSC6900
V900R011
67202919
VS.CellBreath.TC
PUnder.Time
Duration of TCP
Smaller Than Cell
Breathing Lower
Threshold for Cell
Earlier than
BSC6900
V900R011

897
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202920
VS.CellBreath.TC
POver.Time
Duration of TCP
Greater Than Cell
Breathing Upper
Threshold for Cell
Earlier than
BSC6900
V900R011
67202921
VS.CPICH.MeanP
wr
Average CPICH
Power for Cell
BSC6900
V900R013
67190706
VS.DCCC.D2C.Att
Number of Dynamic
Channel Conversion
Attempts from DCHs
to FACHs for Cell
Earlier than
BSC6900
V900R011
67190707
VS.DCCC.C2D.Att
Number of Dynamic
Channel Conversion
Attempts from
FACHs to DCHs for
Cell
Earlier than
BSC6900
V900R011
67192001
VS.AMRWB.DLR
ateUp
Number of Increases
of DL Rate for AMR
WB Speech Service
Earlier than
BSC6900
V900R011
67192002
VS.AMRWB.DLR
ateDown
Number of
Decreases of DL
Rate for AMR WB
Speech Service
Earlier than
BSC6900
V900R011
67192003
VS.AMRWB.ULR
ateUp
Number of Increases
of UL Rate for AMR
WB Speech Service
Earlier than
BSC6900
V900R011
67192004
VS.AMRWB.ULR
ateDown
Number of
Decreases of UL
Rate for AMR WB
Speech Service
Earlier than
BSC6900
V900R011
67191839
VS.RAC.DCCC.Fa
il.ULCE.Cong
Number of Failed
Requests for UL CE
Resources During
DCCC for Cell
Earlier than
BSC6900
V900R011
67191840
VS.RAC.DCCC.Fa
il.DLCE.Cong
Number of Failed
Requests for DL CE
Resources During
DCCC for Cell
Earlier than
BSC6900
V900R011
67191841
VS.RAC.SHO.Fail.
ULCE.Cong
Number of Failed
Requests for UL CE
Resources During
SHO for Cell
Earlier than
BSC6900
V900R011

898
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191842
VS.RAC.SHO.Fail.
DLCE.Cong
Number of Failed
Requests for DL CE
Resources During
SHO for Cell
Earlier than
BSC6900
V900R011
67192492
VS.RAC.HHO.Fail
.ULCE.Cong
Number of Failed
Requests for UL CE
Resources During
HHO for Cell
Earlier than
BSC6900
V900R011
67192493
VS.RAC.HHO.Fail
.DLCE.Cong
Number of Failed
Requests for DL CE
Resources During
HHO for Cell
Earlier than
BSC6900
V900R011
67191843
VS.RAC.NewCallR
eq.Fail.ULCE.Con
g
Number of Failed
Requests for Uplink
CE Resources
During RAB
Establishment for
Cell
Earlier than
BSC6900
V900R011
67191844
VS.RAC.NewCallR
eq.Fail.DLCE.Con
g
Number of Failed
Requests for
Downlink CE
Resources During
RAB Establishment
for Cell
Earlier than
BSC6900
V900R011
67184359
VS.DCCC.AttUpsi
zing.E2E.Thr
Number of UL
EDCH-EDCH
DCCC Upsizing
Attempts Based on
the Throughput or
RLC BO for Cell
Earlier than
BSC6900
V900R011
67196026
VS.DCCC.AttDow
nsizing.E2E.Thr
Number of UL
EDCH-EDCH
DCCC Downsizing
Attempts Based on
the Throughput or
RLC BO for Cell
Earlier than
BSC6900
V900R011
67196027
VS.DCCC.SuccUps
izing.E2E.Thr
Number of
Successful UL
EDCH-EDCH
DCCC Upsizings
Based on the
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011

899
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196028
VS.DCCC.SuccDo
wnsizing.E2E.Thr
Number of
Successful UL
EDCH-EDCH
DCCC Downsizings
Based on the
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011
67195992
VS.LCC.HSDPA.C
odeAdj.Att
Number of UEs
Performing Code
Adjustment Based on
HSDPA for Cell
BSC6900
V900R012
67196029
VS.LCC.LDR.HSU
PA.InterRATCS
Number of HSUPA
UEs Performing CS
Inter-RAT
Handovers in Basic
Congestion for Cell
Earlier than
BSC6900
V900R011
67196030
VS.LCC.LDR.HSD
PA.InterRATCS
Number of HSDPA
UEs Performing CS
Inter-RAT
Handovers in Basic
Congestion for Cell
Earlier than
BSC6900
V900R011
67192585
VS.DCCC.AttUpsi
zing.DL.Thr
Number of DL DCH
DCCC Upsizing
Attempts Based on
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011
67192586
VS.DCCC.SuccUps
izing.DL.Thr
Number of
Successful DL DCH
DCCC Upsizings
Based on
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011
67192593
VS.DCCC.AttUpsi
zing.UL.Thr
Number of UL DCH
DCCC Upsizing
Attempts Based on
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011
67192594
VS.DCCC.SuccUps
izing.UL.Thr
Number of
Successful UL DCH
DCCC Upsizings
Based on
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011

900
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192595
VS.DCCC.AttDow
nsizing.UL.Thr
Number of UL DCH
DCCC Downsizing
Attempts Based on
the Throughput or
RLC BO for Cell
Earlier than
BSC6900
V900R011
67192596
VS.DCCC.SuccDo
wnsizing.UL.Thr
Number of
Successful UL DCH
DCCC Downsizings
Based on
Throughput or RLC
BO for Cell
Earlier than
BSC6900
V900R011
67196032
VS.DCCC.AttDow
nsizing.UL.Cov
Number of UL DCH
DCCC Downsizing
Attempts Based on
the Coverage (QoS)
for Cell
Earlier than
BSC6900
V900R011
67196033
VS.DCCC.SuccDo
wnsizing.UL.Cov
Number of
Successful UL DCH
DCCC Downsizings
Based on Coverage
(QoS) for Cell
Earlier than
BSC6900
V900R011
67196034
VS.DCCC.AttDow
nsizing.UL.Cong
Number of UL DCH
DCCC Downsizing
Attempts Based on
the Resource
Congestion
Algorithm for Cell
Earlier than
BSC6900
V900R011
67196035
VS.DCCC.SuccDo
wnsizing.UL.Cong
Number of
Successful UL DCH
DCCC Downsizings
Based on Resource
Congestion
Algorithm for Cell
Earlier than
BSC6900
V900R011
67193409
VS.LCC.LDR.Cod
eAdj.Succ
Number of UEs
Performing
Successful Code
Adjustment in DL
Cell
Earlier than
BSC6900
V900R011

901
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193410
VS.LCC.HSDPA.C
odeAdj.Succ
Number of UEs
Performing
Successful Code
Adjustment Based on
HSDPA for Cell
Earlier than
BSC6900
V900R011
67204837
VS.Cell.UnavailTi
me.Sys
Duration of Cell
Unavailability Due
to System Faults for
Cell
Earlier than
BSC6900
V900R011
67204838
VS.Cell.HSDPA.Un
availTime
Duration of HSDPA
Service
Unavailability Due
to System Fault for
Cell
Earlier than
BSC6900
V900R011
67204839
VS.Cell.HSUPA.Un
availTime
Duration of HSUPA
Service
Unavailability Due
to System Fault for
Cell
BSC6900
V900R012
73403799
VS.DCCC.P2F.Att
Number of Attempts
to transfer state from
CELL_PCH to
CELL_FACH for
cell
BSC6900
V900R012
73403800
VS.DCCC.P2F.Suc
c
Number of
Successful state
transfer from
CELL_PCH to
CELL_FACH for
cell
BSC6900
V900R012
73403801
VS.DCCC.P2URA
P
Number of state
transfer from
CELL_PCH to
URA_PCH for cell
BSC6900
V900R012
73403802
VS.DCCC.URAP2
F.Att
Number of Attempts
URA_PCH to
CELL_FACH for
cell
BSC6900
V900R012

902
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403803
VS.DCCC.URAP2
F.Succ
Number of
successful state
transfer from
URA_PCH to
CELL_FACH in the
best cell.
BSC6900
V900R012
73393802
VS.DynClose.CellDel
Number of Cell
Deletions Due to
Dynamic Cell
Shutdown
BSC6900
V900R012
73393803
VS.DynOpen.CellSetup
Number of Cell
Setup Due to
Dynamic Cell
Shutdown
BSC6900
V900R012
73393961
VS.RAC.NewCallR
eq.Fail.ULPower.C
ong
Number of Failed
Requests for Uplink
Power Resources in
the RAB Setup
Procedure for Cell
BSC6900
V900R012
73393962
VS.RAC.NewCallR
eq.Fail.DLPower.C
ong
Number of Failed
Requests for
Downlink Power
Resources in the
RAB Setup
Procedure for Cell
BSC6900
V900R012
73393963
VS.RAC.NewCallR
eq.Fail.Code.Cong
Number of Failed
Requests for Code
Resources in the
RAB Setup
Procedure for Cell
BSC6900
V900R012
73393964
VS.RAC.NewCallR
eq.Fail.ULIUBBan
d.Cong
Number of Failed
Requests for Uplink
Iub Bandwidth
Resources in the
RAB Setup
Procedure for Cell
BSC6900
V900R012
73393965
VS.RAC.NewCallR
eq.Fail.DLIUBBan
d.Cong
Number of Failed
Requests for
Downlink Iub
Bandwidth
Resources in the
RAB Setup
Procedure for Cell
BSC6900
V900R012

903
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421765
VS.DCCC.D2P.Att
Number of State
Transfer Attempts
from CELL_DCH to
CELL_PCH for Cell
BSC6900
V900R012
73421766
VS.DCCC.D2P.Suc
c
Number of
Successful State
Transfers from
CELL_DCH to
CELL_PCH for Cell
BSC6900
V900R012
73421767
VS.DCCC.FastDor
mUe.DF2P.Att
Number of State
Transfer Attempts
from CELL_DCH or
CELL_FACH to
CELL_PCH for
FAST
DORMANCY user
for Cell
BSC6900
V900R012
73421768
VS.DCCC.FastDor
mUe.DF2P.Succ
Number of
Successful State
Transfers from
CELL_DCH or
CELL_FACH to
CELL_PCH for
FAST
DORMANCY user
for Cell
BSC6900
V900R012
73439971
VS.FACH.DTCH.
CONG.TIME
Congestion Duration
of DTCHs Carried
over FACHs for Cell
BSC6900
V900R012
73421933
VS.DCCC.P2D.Att
Number of Attempts
CELL_PCH to
CELL_DCH for cell
BSC6900
V900R012
73421934
VS.DCCC.P2D.Suc
c
Number of
Successful state
transfer from
CELL_PCH to
CELL_DCH for cell
BSC6900
V900R012
73421935
VS.DCCC.URAP2
D.Att
Number of Attempts
URA_PCH to
CELL_DCH for cell
BSC6900
V900R012

904
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421936
VS.DCCC.URAP2
D.Succ
Number of
successful state
transfer from
URA_PCH to
CELL_DCH in the
best cell.
BSC6900
V900R012
73422068
VS.DCCC.P2D.DR
D.Att
Number of Attempts
of CELL_PCH/
URA_PCH-toCELL_DCH State
Transition Together
with DRD for Cell
BSC6900
V900R012
73422069
VS.DCCC.P2D.DR
D.Succ
Number of
Successful
CELL_PCH/
Transitions Together
with DRDs for Cell
BSC6900
V900R012
73423313
VS.ULB.CPICH.A
djustNum
Number of CPICH
Power Adjustments
Based on RTWP for
Cell
BSC6900
V900R013
73441123
VS.ULB.CPICHMi
n.Time
Duration of PCPICH
Power Under
Minimum RTWP
Threshold
BSC6900
V900R013
73422160
VS.HSDPA.H2P.At
t
Number of State
Transfer Attempts
from CELL_DCH to
CELL_PCH or
URA_PCH for Cell
for HSDPA service
BSC6900
V900R012
73422161
VS.HSDPA.H2P.Su
cc
Number of
Successful Times
That a UE
Performing HSDPA
Services Transits to
CELL_PCH or
URA_PCH State for
cell
BSC6900
V900R012

905
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73422162
VS.HSUPA.E2P.At
t
Number of Attempts
for a UE Performing
HSUPA Services to
Transit to
CELL_PCH or
URA_PCH State for
Cell
BSC6900
V900R012
73422163
VS.HSUPA.E2P.Su
cc
Number of
Successful Times
That a UE
Performing HSUPA
CELL_PCH or
URA_PCH State for
cell
BSC6900
V900R012
73422164
VS.PSR99.D2P.Att
Number of Attempts
for a UE Performing
PS R99 Services to
Transit to
CELL_PCH or
URA_PCH State for
Cell
BSC6900
V900R012
73422165
VS.PSR99.D2P.Suc
c
Number of
Successful Times
That a UE
Performing PS R99
CELL_PCH or
URA_PCH State for
cell
BSC6900
V900R012
73423357
VS.HSUPAR99.Un
fairness
Number of Times
That PS R99 Service
Rate Is Found to Be
Higher than HSUPA
Service Rate
BSC6900
V900R013
73423358
VS.HSUPAR99.Un
fairness.R99BERateDown
Number of PS R99
BE Rate Reduction
Requests Triggered
by Unfairness
Between PS R99
Service Rate and
HSUPA Service Rate
BSC6900
V900R013

906
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73411191
VS.NodeB.CPU.Co
ng.Dur
Duration of CPU
Resource
Insufficiency
Reported by NodeB
for Cell
BSC6900
V900R013
73439970
VS.FACH.DCCH.
CONG.TIME
Congestion Duration
of DCCHs Carried
over FACHs for Cell
BSC6900
V900R012
73424009
VS.FACH.CCCH.
CONG.TIME
Congestion Duration
of CCCHs Carried
over FACHs for Cell
BSC6900
V900R014
73427917
VS.LCC.LDR.AM
RSfRecfg
Number of UEs
Involved in AMRWB SF
Reconfiguration
When a Cell Is in the
Basic Congestion
State
BSC6900
V900R016C00
Each counter's value is greater than the sum of its subcounters' values
Counter
Sub Counter
VS.LCC.LDR.HSDPA.InterFreq
VS.LCC.LDR.HSUPA.InterFreq
VS.LCC.LDR.HSDPA.InterRATPS
VS.LCC.LDR.HSUPA.InterRATPS
VS.LCC.LDR.HSDPA.InterRATCS
VS.LCC.LDR.HSUPA.InterRATCS
Issue 03 (2015-06-30)

907
BSC6900 UMTS
Number of DL Rate Adjustments for AMR Services

Counters
Counter ID
Counter Name
Counter Description
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. The preceding counters
comply with section "6.5.3 Iu Rate Control procedure" in 3GPP TS 25.415 (v9.0.0).
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.
Issue 03 (2015-06-30)

908
BSC6900 UMTS
Figure 1-387 DL AMR rate adjustment procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
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

909
BSC6900 UMTS
Number of Uplink Rate Adjustments for AMR Services

Counters
Counter ID
Counter Name
Counter Description
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
67192003
VS.AMRWB.ULRateUp
Number of Increases of UL
Service
67192004
VS.AMRWB.ULRateDown
Number of Decreases of UL
Service
Description
These counters provide the number of times the UL rate of AMR-NB/AMR-WB services is
adjusted upward and downward. The preceding counters comply with section "8.2.5 Transport
format combination control" in 3GPP TS 25.331 (v9.3.0).
Measurement point
The measurement is triggered at point A as shown in the following figure. The RNC sends the
UE a TRANSPORT FORMAT COMBINATION CONTROL message, requesting the UE to
increase or decrease the uplink rate of the ongoing AMR-NB/AMR-WB service. The increase
or decrease is successful if the RNC does not receive a TRANSPORT FORMAT
COMBINATION CONTROL FAILURE message from the UE. In this case, a specific counter
is incremented by one in the best cell of the UE.
Issue 03 (2015-06-30)

910
BSC6900 UMTS
Figure 1-388 UL AMR rate adjustment procedure
The measurement is triggered at point A as shown in Figure 2. When code resources are
congested, the RNC sends the UE a RADIO BEARER RECONFIGURATION message,
requesting the UE to decrease the uplink rate of the ongoing AMR-WB service. This is to
alleviate the congestion. When the decrease is successful, the UE responds with a RADIO
BEARER RECONFIGURATION COMPLETE message. In this case, the
VS.AMRWB.ULRateDown counter is incremented by one in the best cell of the UE.
Figure 1-389 UL AMR-WB RB reconfiguration procedure
Issue 03 (2015-06-30)

911
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
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.ULRateUp
WRFD-020701
AMR/WB-AMR Speech
Rates Control
VS.AMRWB.ULRateDown
WRFD-020701
AMR/WB-AMR Speech
Rates Control
Counters Related to the Number of Successful Dynamic Channel Conversions

Between DCH and FACH
Counters
Counter ID
Counter Name
Counter Description
67180675
VS.DCCC.Succ.F2D
Channel Conversions from
FACH to DCH for Cell
67180676
VS.DCCC.Succ.D2F
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. The preceding counters comply with section "8.2 Radio Bearer control
procedures" in 3GPP TS 25.331 (v9.3.0).
Issue 03 (2015-06-30)

912
BSC6900 UMTS
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-390 Dynamic channel conversion procedure (RB reconfiguration)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.Succ.F2D
WRFD-021101
Dynamic Channel
(DCCC)
VS.DCCC.Succ.D2F
WRFD-021101
Dynamic Channel
(DCCC)

913
BSC6900 UMTS
Number of State Transfer Attempts from CELL_FACH to CELL_PCH

Counters
Counter ID
Counter Name
Counter Description
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. This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.331 (v9.3.0).
Measurement point
The measurement is triggered at point A, as shown in the following figure. When the RNC sends
a RADIO BEARER RECONFIGURATION or PHYSICAL CHANNEL
RECONFIGURATION message to a UE, instructing the UE to transfer from the CELL_FACH
state to the CELL_PCH state, this counter is incremented by one in the cell where the UE is
camping.
Figure 1-391 RB reconfiguration and physical channel reconfiguration procedure
Issue 03 (2015-06-30)

914
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.Att.F2P
WRFD-021101
Dynamic Channel
(DCCC)
Number of Successful State Transfers from CELL_FACH to CELL_PCH

Counters
Counter ID
Counter Name
Counter Description
67192584
VS.DCCC.Succ.F2P
Number of Successful State

Transfers from
CELL_FACH to
CELL_PCH for Cell
Description
This counter provides the number of successful state transitions from CELL_FACH to
CELL_PCH in a cell. This counter complies with section "8.2 Radio Bearer control procedures"
in 3GPP TS 25.331 (v9.3.0).
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.
Issue 03 (2015-06-30)

915
BSC6900 UMTS
Figure 1-392 RB reconfiguration and physical channel reconfiguration procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.Succ.F2P
WRFD-021101
Dynamic Channel
(DCCC)

916
BSC6900 UMTS
Counters Related to the Number of Downlink DCH DCCC Downsizing Attempts

Based on Different Strategies
Counters
Counter ID
Counter Name
Counter Description
67192587
VS.DCCC.AttDownsizing.
DL.Thr
Number of Downlink DCH

DCCC Downsizing Attempts
Based on Throughput or RLC
BO for Cell
67192589
DL.Cov

Based on Coverage (QoS) for
Cell
67192591
DL.Cong

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. The preceding counters comply with
section "8.2 Radio Bearer control procedures" in 3GPP TS 25.331 (v9.3.0).
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending the
RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the related
counter based on different DCCC strategies in the best cell where the UE camps on if downlink
services are carried on the DCH before and after the reconfiguration.
Issue 03 (2015-06-30)

917
BSC6900 UMTS
Figure 1-393 RB reconfiguration procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
DL.Thr
WRFD-021101
Dynamic Channel
(DCCC)
DL.Cov
WRFD-021101
Dynamic Channel
(DCCC)
DL.Cong
WRFD-021101
Dynamic Channel
(DCCC)

918
BSC6900 UMTS
Counters Related to the Number of Successful DL DCH DCCC Downsizings Based

on Different DCCC Strategies
Counters
Counter ID
Counter Name
Counter Description
67192588
VS.DCCC.SuccDownsizing.
DL.Thr
Number of Successful DL
DCH DCCC Downsizings
BO for Cell
67192590
DL.Cov
Cell
67192592
DL.Cong
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. The preceding counters comply with
Measurement point
The measurement is triggered at point B in the following figure. After sending a RADIO
BEARER RECONFIGURATION message to the UE, the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE. If downlink services are carried on
the DCH before and after the reconfiguration, the related counters are measured based on
different DCCC strategies in the best cell.
Issue 03 (2015-06-30)

919
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
DL.Thr
WRFD-021101
Dynamic Channel
(DCCC)
DL.Cov
WRFD-021101
Dynamic Channel
(DCCC)
DL.Cong
WRFD-021101
Dynamic Channel
(DCCC)

920
BSC6900 UMTS
Counters Related to the Number of UL or DL Overload Congestion

Counters
Counter ID
Counter Name
Counter Description
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. The preceding counters comply with section "8.2.9 Common Measurement
Reporting" in 3GPP TS 25.433 (v9.3.0).
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-395 Common measurement report procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

921
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.LCC.OLC.UL.Num
WRFD-020107
Overload Control
VS.LCC.OLC.DL.Num
WRFD-020107
Overload Control
Counters Related to the Duration of UL or DL Overload Congestion

Counters
Counter ID
Counter Name
Counter Description
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
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.OLC.UL.Time
WRFD-020107
Overload Control
VS.LCC.OLC.DL.Time
WRFD-020107
Overload Control

922
BSC6900 UMTS
Number of UEs Transferring BE Service to Common Channel in Overload

Congestion
Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.OLC.D2C
WRFD-020107
Overload Control

923
BSC6900 UMTS
Counters Related to the Duration of Cell in LDR State Due to Congestion of

Various Resources
Counters
Counter ID
Counter Name
Counter Description
67203991
VS.LCC.LDR.Time.ULPower
Duration of Cell in LDR

State Due to UL Power
Congestion for Cell
67203992
VS.LCC.LDR.Time.DLPow
er

State Due to DL Power
Congestion for Cell
67203993
VS.LCC.LDR.Time.DLCod
e

State Due to DL Code
Resource Congestion for Cell
67203994
VS.LCC.LDR.Time.ULCE

State Due to UL CE Resource
Congestion
67203995
VS.LCC.LDR.Time.DLCE

State Due to DL CE Resource
Congestion
67203996
VS.LCC.LDR.Time.ULIub

State Due to UL Iub
Transmission Resource
Congestion for Cell
67203997
VS.LCC.LDR.Time.DLIub

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
Issue 03 (2015-06-30)

924
BSC6900 UMTS
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.Time.ULPower
WRFD-020106
Load Reshuffling
VS.LCC.LDR.Time.DLPow
er
WRFD-020106
Load Reshuffling
VS.LCC.LDR.Time.DLCod
e
WRFD-020106
Load Reshuffling
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
Counters Related to the Number of Times a Cell Is in LDR State Due to Congestion
of Various Resources
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192637
VS.LCC.LDR.Num.ULPower
Number of Times a Cell Is in

LDR State Due to UL Power
Congestion for Cell
67192638
VS.LCC.LDR.Num.DLPow
er

LDR State Due to DL Power
Congestion for Cell
67192639
VS.LCC.LDR.Num.DLCod
e

LDR State Due to DL Code
67192640
VS.LCC.LDR.Num.ULCE

LDR State Due to UL CE
67192641
VS.LCC.LDR.Num.DLCE

LDR State Due to DL CE

925
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192642
VS.LCC.LDR.Num.ULIub

LDR State Due to UL Iub
Congestion for Cell
67192643
VS.LCC.LDR.Num.DLIub

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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.Num.ULPower
WRFD-020106
Load Reshuffling
VS.LCC.LDR.Num.DLPow
er
WRFD-020106
Load Reshuffling
VS.LCC.LDR.Num.DLCod
e
WRFD-020106
Load Reshuffling
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

926
BSC6900 UMTS
Counters Related to the Number of UEs Performing BE Service TF Control in

Overload Congestion
Counters
Counter ID
Counter Name
Counter Description
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

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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.OLC.UL.TF
WRFD-020107
Overload Control
VS.LCC.OLC.DL.TF
WRFD-020107
Overload Control

927
BSC6900 UMTS
Counters Related to the Number of UEs Released Due to Overload Congestion

Counters
Counter ID
Counter Name
Counter Description
67192647
VS.LCC.OLC.UL.UserRel
Number of UEs Released

Due to UL Overload
Congestion for Cell
67191150
VS.LCC.OLC.HSDPA.User
Rel
Number of HSDPA UEs

Released Due to Overload
Congestion for Cell
67192648
VS.LCC.OLC.HSUPA.User
Rel
Number of HSUPA UEs

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.
Issue 03 (2015-06-30)

928
BSC6900 UMTS
Figure 1-396 User release procedure for Cell in congestion state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.OLC.UL.UserRel
WRFD-020107
Overload Control
VS.LCC.OLC.HSDPA.User
Rel
WRFD-020107
Overload Control
VS.LCC.OLC.HSUPA.User
Rel
WRFD-020107
Overload Control
VS.LCC.OLC.DL.UserRel
WRFD-020107
Overload Control

929
BSC6900 UMTS
Number of Failed Requests for various Resources During RAB Establishment for
Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192916
VS.RAC.NewCallReq.Fail.
HSDPANum.Cong
Number of Failed
Admissions Due to HSDPA
User Number Exceeding
Threshold During RAB
Establishment for Cell
67192917
HSUPANum.Cong
Number of Failed
Admissions Due to HSUPA
Threshold During RAB
67191843
ULCE.Cong
Number of Failed Requests

for Uplink CE Resources
During RAB Establishment
for Cell
67191844
DLCE.Cong

for Downlink CE Resources
for Cell
73393961
ULPower.Cong

for Uplink Power Resources
in the RAB Setup Procedure
for Cell
73393962
DLPower.Cong

for Downlink Power
Resources in the RAB Setup
Procedure for Cell
73393963
Code.Cong

for Code Resources in the
RAB Setup Procedure for
Cell
73393964
ULIUBBand.Cong

for Uplink Iub Bandwidth
Procedure for Cell
73393965
DLIUBBand.Cong

for Downlink Iub Bandwidth
Procedure for Cell

930
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.
Counter Name
Description
VS.RAC.NewCallReq.Fail.HSUPANum.Co
ng
This counter measure the number of failed

admissions due to HSUPA user number
exceeding threshold during RAB
establishment for cell.
Measurement point
The measurement is triggered at point A as shown in Figure 1. After receiving the RAB
ASSIGNMENT REQUEST message from the CN, the RNC initiates the admission procedure
to request different resources. If the resource request fails, the RNC measures these counters in
the cell where the admission fails according to the limited resource type.
Figure 1-397 RAB assignment request admission failure
Formula
None
Issue 03 (2015-06-30)

931
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
HSDPANum.Cong
WRFD-01061003
HSDPA Admission Control
HSUPANum.Cong
WRFD-01061202
HSUPA Admission Control
ULCE.Cong
WRFD-020101
Admission Control
DLCE.Cong
WRFD-020101
Admission Control
ULPower.Cong
WRFD-020101
Admission Control
DLPower.Cong
WRFD-020101
Admission Control
Code.Cong
WRFD-020101
Admission Control
ULIUBBand.Cong
WRFD-020101
Admission Control
DLIUBBand.Cong
WRFD-020101
Admission Control
Number of Preemptions During RAB Establishment

Counters
Counter ID
Counter Name
Counter Description
67192937
VS.RAC.NewCallReq.Pree
mpt.Cong
Number of Preemptions
for Cell
Description
This counter provides the number of service preemptions in a cell during the RAB establishment.
Issue 03 (2015-06-30)

932
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-398 RAB assignment request admission failure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAC.NewCallReq.Pree
mpt.Cong
WRFD-010505

933
BSC6900 UMTS
Number of Failed Requests for various Resources During SHO for Cell
Counters
Counter ID
Counter Name
Counter Description
67192939
VS.RAC.SHO.Fail.ULPowe
r.Cong

for UL Power Resources
During SHO for Cell
67192940
VS.RAC.SHO.Fail.DLPowe
r.Cong

for DL Power Resources
During SHO for Cell
67192918
VS.RAC.SHO.Fail.Code.Co
ng

for Code Resources During
SHO for Cell
67192919
VS.RAC.SHO.Fail.ULIUB
Band.Cong

for UL Iub Transmission
Resources During SHO for
Cell
67192920
VS.RAC.SHO.Fail.DLIUB
Band.Cong

for DL Iub Transmission
Resources During SHO for
Cell
67192921
VS.RAC.SHO.Fail.HSUPA
Num.Cong
Number of Failed
Threshold During SHO for
Cell
67191841
VS.RAC.SHO.Fail.ULCE.C
ong

for UL CE Resources During
SHO for Cell
67191842
VS.RAC.SHO.Fail.DLCE.C
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
the primary carrier.
Issue 03 (2015-06-30)

934
BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in Figure 1. After receiving the
MEASUREMENT REPORT message from the UE, the RNC initiates the admission procedure
to request different resources if the RNC decides to perform soft handover. If the resource request
fails, the RNC measures the related counter in the cell where the admission fails according to
the limited resource type.
Figure 1-399 admission failure in soft handover
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAC.SHO.Fail.ULPowe
r.Cong
WRFD-020101
Admission Control
VS.RAC.SHO.Fail.DLPowe
r.Cong
WRFD-020101
Admission Control
VS.RAC.SHO.Fail.Code.Co
ng
WRFD-020101
Admission Control
VS.RAC.SHO.Fail.ULIUB
Band.Cong
WRFD-020101
Admission Control
VS.RAC.SHO.Fail.DLIUB
Band.Cong
WRFD-020101
Admission Control

935
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAC.SHO.Fail.HSUPA
Num.Cong
WRFD-01061202
VS.RAC.SHO.Fail.ULCE.C
ong
WRFD-020101
Admission Control
VS.RAC.SHO.Fail.DLCE.C
ong
WRFD-020101
Admission Control
Number of Failed Requests for various Resources During DCCC for Cell
Counters
Counter ID
Counter Name
Counter Description
67192943
VS.RAC.DCCC.Fail.ULPo
wer.Cong

During DCCC for Cell
67192944
VS.RAC.DCCC.Fail.DLPo
wer.Cong

67192922
VS.RAC.DCCC.Fail.Code.
Cong

for DL Code Resources
67191839
VS.RAC.DCCC.Fail.ULCE.
Cong

DCCC for Cell
67191840
VS.RAC.DCCC.Fail.DLCE.
Cong

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.
Issue 03 (2015-06-30)

936
BSC6900 UMTS
Figure 1-400 admission failure in DCCC procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAC.DCCC.Fail.ULPo
wer.Cong
WRFD-020101
Admission Control
VS.RAC.DCCC.Fail.DLPo
wer.Cong
WRFD-020101
Admission Control
VS.RAC.DCCC.Fail.Code.
Cong
WRFD-020101
Admission Control
VS.RAC.DCCC.Fail.ULCE.
Cong
WRFD-020101
Admission Control
VS.RAC.DCCC.Fail.DLCE.
Cong
WRFD-020101
Admission Control

937
BSC6900 UMTS
Counters Related to the Number of Failed Requests for Different Resources During
Channel Type Switch
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192923
VS.RAC.TrChSwitch.Fail.U
LCE.Cong

Channel Type Switch for
Cell
67192924
VS.RAC.TrChSwitch.Fail.D
LCE.Cong

Cell
67192945
LPower.Cong

During Channel Type Switch
for Cell
67192946
LPower.Cong

During Channel Type Switch
for Cell
67192925
VS.RAC.TrChSwitch.Fail.C
ode.Cong

Cell
67192926
LIUBBand.Cong

Resources During Channel
67192927
LIUBBand.Cong

Resources During Channel
67192928
VS.RAC.TrChSwitch.Fail.H
SDPANum.Cong
Number of Failed
Threshold During Channel
67192929
SUPANum.Cong
Number of Failed
Threshold During Channel

938
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-401 admission control failure
Formula
None
Unit
None
Issue 03 (2015-06-30)

939
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
LCE.Cong
WRFD-020101
Admission Control
LCE.Cong
WRFD-020101
Admission Control
LPower.Cong
WRFD-020101
Admission Control
LPower.Cong
WRFD-020101
Admission Control
VS.RAC.TrChSwitch.Fail.C
ode.Cong
WRFD-020101
Admission Control
LIUBBand.Cong
WRFD-020101
Admission Control
LIUBBand.Cong
WRFD-020101
Admission Control
SDPANum.Cong
WRFD-01061003
SUPANum.Cong
WRFD-01061202
Number of Failed Requests for various Resources During HHO for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192941
VS.RAC.HHO.Fail.ULPow
er.Cong

During HHO for Cell
67192942
VS.RAC.HHO.Fail.DLPow
er.Cong

During HHO for Cell
67192930
VS.RAC.HHO.Fail.ULIUB
Band.Cong

Resources During HHO for
Cell

940
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192931
VS.RAC.HHO.Fail.DLIUB
Band.Cong

Resources During HHO for
Cell
67192932
VS.RAC.HHO.Fail.HSDPA
Num.Cong
Number of Failed
Threshold During HHO for
Cell
67192933
VS.RAC.HHO.Fail.HSUPA
Num.Cong
Number of Failed
Threshold During HHO for
Cell
67189859
VS.RAC.HHO.Fail.Code.C
ong

HHO for Cell
67192492
VS.RAC.HHO.Fail.ULCE.
Cong

HHO for Cell
67192493
VS.RAC.HHO.Fail.DLCE.
Cong

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.
Issue 03 (2015-06-30)

941
BSC6900 UMTS
Figure 1-402 admission control failure in hard handover
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAC.HHO.Fail.ULPow
er.Cong
WRFD-020101
Admission Control
VS.RAC.HHO.Fail.DLPow
er.Cong
WRFD-020101
Admission Control
VS.RAC.HHO.Fail.ULIUB
Band.Cong
WRFD-020101
Admission Control
VS.RAC.HHO.Fail.DLIUB
Band.Cong
WRFD-020101
Admission Control
VS.RAC.HHO.Fail.HSDPA
Num.Cong
WRFD-01061003
VS.RAC.HHO.Fail.HSUPA
Num.Cong
WRFD-01061202
VS.RAC.HHO.Fail.Code.C
ong
WRFD-020101
Admission Control
VS.RAC.HHO.Fail.ULCE.
Cong
WRFD-020101
Admission Control

942
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAC.HHO.Fail.DLCE.
Cong
WRFD-020101
Admission Control
Number of Preemptions During HHO

Counters
Counter ID
Counter Name
Counter Description
67192938
VS.RAC.HHO.Preempt.Con
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-403 admission control failure in hard handover
Formula
None
Issue 03 (2015-06-30)

943
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.HHO.Preempt.Con
g
WRFD-010505
Number of MBMS PTM or PTP Service Releases in Overload Congestion

Counters
Counter ID
Counter Name
Counter Description
67194970
VS.LCC.OLC.MBMS.PTM.
RBRel
Number of MBMS PTM

Service Releases in Overload
Congestion for Cell
67194971
VS.LCC.OLC.MBMS.PTP.
RBRel
Number of MBMS PTP

Service Releases in Overload
Congestion for Cell
Description
These counters provide the number of times that the MBMS PTM or PTP service is released
when the cell is in overload congestion.
Measurement point
When the cell is in overload congestion and the MBMS PTM or PTP service release is triggered,
the RNC measures these counters.
Formula
None
Unit
None
Issue 03 (2015-06-30)

944
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.LCC.OLC.MBMS.PTM.
RBRel
WRFD-020107
Overload Control
VS.LCC.OLC.MBMS.PTP.
RBRel
WRFD-020107
Overload Control
Counters Related to the Number of UEs Performing Inter-Frequency Load

Handovers in Basic Congestion
Counters
Counter ID
Counter Name
Counter Description
67190435

Inter-Frequency Load
Handovers in Basic
Congestion for Cell
67192644
Number of HSUPA UEs

Performing Inter-Frequency
Load Handovers in Basic
Congestion for Cell
67191151
Number of HSDPA UEs

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 interfrequency handovers. VS.LCC.LDR.HSDPA.InterFreq is used to measure the number of
HSDPA UEs performing inter-frequency handovers. For DC-HSDPA users, this counter is
measured only in the cell with the primary carrier. VS.LCC.LDR.HSUPA.InterFreq is used to
measure the number of HSUPA UEs performing inter-frequency handovers.For DC-HSUPA
users, this counter is measured only in the cell with the primary carrier.
Measurement point
When the cell is in basic congestion, VS.LCC.LDR.InterFreq is measured in the cell where the
UE camps on every time the RNC selects a UE to perform inter-frequency handover. If the RNC
selects an HSDPA UE, VS.LCC.LDR.HSDPA.InterFreq is measured in the cell where the UE
camps on. If the RNC selects an HSUPA UE, VS.LCC.LDR.HSUPA.InterFreq is measured in
the cell where the UE camps on.
Issue 03 (2015-06-30)

945
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020103
Inter Frequency Load

Balance
WRFD-020103

Balance
WRFD-020103

Balance
Counters Related to the Number of UEs Performing BE Service Downsizing in

Basic Congestion
Counters
Counter ID
Counter Name
Counter Description
67190436
VS.LCC.LDR.UL.BERateDown

BE Service Downsizing in
UL Basic Congestion
67190437
VS.LCC.LDR.DL.BERateDown

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. The preceding counters comply with section
"8.2 Radio Bearer control procedures" in 3GPP TS 25.331 (v9.3.0).
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
Issue 03 (2015-06-30)

946
BSC6900 UMTS
the following figure. The RNC measures the related counter in the cell where the UE camps on
according to the UL or DL congestion.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.UL.BERateDown
WRFD-020106
Load Reshuffling
VS.LCC.LDR.DL.BERateDown
WRFD-020106
Load Reshuffling

947
BSC6900 UMTS
Counters Related to the Number of UEs Performing Uncontrollable Real-Time

Service QoS Renegotiation in Basic Congestion
Counters
Counter ID
Counter Name
Counter Description
67190438
VS.LCC.LDR.UL.QosReNego

Uncontrollable Real-Time
Service QoS Renegotiation
in UL Basic Congestion for
Cell
67190439
VS.LCC.LDR.DL.QosReNego

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. The preceding counters comply with section "8.30 RAB Modification
Request" in 3GPP TS 25.413 (v9.3.0).
Measurement point
The measurement is triggered at point A as shown in the following figure. When the cell is in
basic congestion, the RNC selects certain UEs to perform QoS renegotiation. At the same time,
the RNC sends the RAB MODIFY REQUEST message to the CN. In this case, the RNC
measures the related counter in the cell where the UE camps on according to the UL or DL
congestion.
Figure 1-405 Uncontrollable real-time service QoS renegotiation procedure
Issue 03 (2015-06-30)

948
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.UL.QosReNego
WRFD-020106
Load Reshuffling
VS.LCC.LDR.DL.QosReNego
WRFD-020106
Load Reshuffling
Counters Related to the Number of UEs Performing CS Inter-RAT Handovers in

Basic Congestion
Counters
Counter ID
Counter Name
Counter Description
67190440

CS Inter-RAT Handovers in
Basic Congestion for Cell
67196029
Number of HSUPA UEs

Performing CS Inter-RAT
Handovers in Basic
Congestion for Cell
67196030
Number of HSDPA UEs

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
Issue 03 (2015-06-30)

949
BSC6900 UMTS
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
Counter Name
Feature ID
Feature Name
WRFD-020306

on Load
WRFD-020306

on Load
WRFD-020306

on Load
Counters Related to the Number of UEs Performing PS Inter-RAT Handovers in

Basic Congestion
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190441

PS Inter-RAT Handovers in
67192645
Number of HSUPA UEs

Performing PS Inter-RAT
Handover in Basic
Congestion for Cell

950
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67191152
Number of HSDPA UEs

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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020306

on Load
WRFD-020306

on Load
WRFD-020306

on Load

951
BSC6900 UMTS
Counters Related to the Number of UEs Performing AMR Rate Decrease in Basic
Congestion
Counters
Counter ID
Counter Name
Counter Description
67192426
VS.LCC.LDR.AMRRateUL

AMR Rate Decrease in UL
67192427
VS.LCC.LDR.AMRRateDL

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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.AMRRateUL
WRFD-020106
Load Reshuffling
VS.LCC.LDR.AMRRateDL
WRFD-020106
Load Reshuffling

952
BSC6900 UMTS
Number of UEs Performing Code Adjustment Attempts in DL Basic Congestion

for Cell
Counters
Counter ID
Counter Name
Counter Description
67192397
VS.LCC.LDR.CodeAdj.Att

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
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.CodeAdj.Att
WRFD-020106
Load Reshuffling

953
BSC6900 UMTS
Number of MBMS Services Performing Power Decreasing in Basic Congestion

Counters
Counter ID
Counter Name
Counter Description
67192398
VS.LCC.LDR.MbmsPowerDec
Number of MBMS Services

Performing Power
Decreasing in Basic
Congestion for Cell
Description
When the cell is in basic congestion, the RNC selects certain MBMS services to perform power
decreasing. This counter provides the number of MBMS services performing power decreasing
in a cell.
Measurement point
When the cell is in basic congestion, the RNC measures the counter in the cell where the MBMS
service is processed every time the RNC selects an MBMS service to perform power decreasing.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.MbmsPowerDec
WRFD-020106
Load Reshuffling
Counters Related to the Number of Qoffset Updates Due to Load Level Change
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189856
VS.PUC.High.Offset.Updt
Number of Qoffset Updates

Due to Heavy Load for Cell

954
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67189857
VS.PUC.Light.Offset.Updt

Due to Light Load for Cell
67189858
VS.PUC.Norm.Offset.Updt

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 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. The preceding counters comply
with section "8.2.16 System Information Update" in 3GPP TS 25.433 (v9.3.0).
Measurement point
The measurement is triggered at point A shown in the following figure. The RNC measures the
related counter when updating Qoffset in SIB 11 according to the change in the cell load level
in the common measurement report.
Issue 03 (2015-06-30)

955
BSC6900 UMTS
Figure 1-406 Qoffset update procedure (based on load)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PUC.High.Offset.Updt
WRFD-020105
Potential User Control
VS.PUC.Light.Offset.Updt
WRFD-020105
VS.PUC.Norm.Offset.Updt
WRFD-020105

956
BSC6900 UMTS
Counters Related to the Number of Sintersearch Updates Due to Cell Load Change
Counters
Counter ID
Counter Name
Counter Description
67190444
VS.PUC.High.IntSrch.Updt
Number of Sintersearch
Updates Due to Heavy Load
for Cell
67190442
VS.PUC.Light.IntSrch.Updt
Updates Due to Light Load
for Cell
67190443
VS.PUC.Norm.IntSrch.Updt
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. The preceding counters comply with section "8.2.16 System
Information Update" in 3GPP TS 25.433 (v9.3.0).
Measurement point
The measurement is triggered at point A shown in the following figure. The RNC measures the
related counter when updating Sintersearch in SIB 3 according to the change in the cell load
level in the common measurement report.
Issue 03 (2015-06-30)

957
BSC6900 UMTS
Figure 1-407 Sintersearch update procedure (based on load)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PUC.High.IntSrch.Updt
WRFD-020105
VS.PUC.Light.IntSrch.Updt
WRFD-020105
VS.PUC.Norm.IntSrch.Updt
WRFD-020105

958
BSC6900 UMTS
Number of Successful Cell Resource Requests During HHO

Counters
Counter ID
Counter Name
Counter Description
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-408 Successful handover admission
Formula
None
Unit
None
Issue 03 (2015-06-30)

959
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.HHOCallAcc
WRFD-020101
Admission Control
Number of Cell Resource Requests During HHO

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

960
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.HHOCallReq
WRFD-020101
Admission Control
Number of Successful Cell Resource Requests During RAB Establishment

Counters
Counter ID
Counter Name
Counter Description
67181076
VS.RAC.NewCallAcc

RAB Establishment for Cell
Description
This counter provides the number of successful cell resource requests during the RAB
establishment.
Measurement point
The measurement is triggered at point B as shown in the Figure1. After receiving the RAB
ASSIGNMENT REQUEST message from the CN, the RNC requests cell resources for the UE.
In this case, the counter will be measured in the cell in which the resources(E.g. Iub bandwidth,
CE, power, code, user number etc.) are assigned successfully. If the assignments succeed in
more than one cell(E.g. in SHO or DRD case.), the RNC measures the counter in every cell in
which the assignments succeed.
Issue 03 (2015-06-30)

961
BSC6900 UMTS
Figure 1-410 Successful admission during the RAB establishment
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAC.NewCallAcc
WRFD-020101
Admission Control

962
BSC6900 UMTS
Number of Cell Resource Requests During RAB Establishment

Counters
Counter ID
Counter Name
Counter Description
67181071
VS.RAC.NewCallReq

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-411 Successful admission during the RAB establishment
Formula
None
Unit
None
Issue 03 (2015-06-30)

963
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.NewCallReq
WRFD-020101
Admission Control
Number of Successful Cell Resource Requests due to UE Service Reconfiguration

(Cell)
Counters
Counter ID
Counter Name
Counter Description
67181078

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-412 RAB reconfiguration procedure
Issue 03 (2015-06-30)

964
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020101
Admission Control
Number of Cell Resource Requests due to UE Service Reconfiguration (Cell)

Counters
Counter ID
Counter Name
Counter Description
67181073

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-413 RAB reconfiguration procedure
Issue 03 (2015-06-30)

965
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020101
Admission Control
Number of Successful Cell Resource Requests During SHO

Counters
Counter ID
Counter Name
Counter Description
67181077
VS.RAC.SHOCallAcc

SHO for Cell
Description
After receiving an intra-frequency measurement report from the UE, the RNC requests cell
resources for a successful soft handover to a new cell. This counter provides the number of
successful cell resource requests in the target cell where the UE is handed over during a soft
handover.
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving the
MEASUREMENT REPORT message from the UE, the RNC requests cell resources for soft
handover to a new cell. If the request succeeds, the RNC measures the counter in the target cell
for handover. If the request for multiple cells' resources succeeds, the RNC measures the counter
in each cell.
Issue 03 (2015-06-30)

966
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.SHOCallAcc
WRFD-020101
Admission Control
Number of Cell Resource Requests During SHO

Counters
Counter ID
Counter Name
Counter Description
67181072
VS.RAC.SHOCallReq

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.
Issue 03 (2015-06-30)

967
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
Counter Name
Feature ID
Feature Name
VS.RAC.SHOCallReq
WRFD-020101
Admission Control
Number of Successful Cell Resource Requests During Channel Type Switch

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67181080
VS.RAC.TrChSwitchCallAcc

Cell

968
BSC6900 UMTS
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.When the PERFENH_CHTYPE_CHG_PFM_OPT_SWITCH under the
PerfEnhanceSwitch2 parameter in the SET UNBMPARA command is set to off, this counter
does not include channel type switching between HSPA and DCH. When the
PERFENH_CHTYPE_CHG_PFM_OPT_SWITCH under the PerfEnhanceSwitch2 parameter
in the SET UNBMPARA command is set to on, this counter includes channel type switching
between HSPA and DCH.
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-416 admission success
Formula
None
Unit
None
Issue 03 (2015-06-30)

969
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.TrChSwitchCallAcc
WRFD-020101
Admission Control
Number of Cell Resource Requests During Channel Type Switch

Counters
Counter ID
Counter Name
Counter Description
67181075
VS.RAC.TrChSwitchCallReq

Requests During Channel
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 cell resource requests in a cell during the channel type change. Only the number of
cell resource requests in a cell during the channel type change is measured.When the
in the SET UNBMPARA command is set to off, this counter does not include channel type
switching between HSPA and DCH. When the
in the SET UNBMPARA command is set to on, this counter includes channel type switching
between HSPA and DCH.
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-417 admission control in channel type switch
Issue 03 (2015-06-30)

970
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.TrChSwitchCallReq
WRFD-020101
Admission Control
Counters Related to the Mean Number of Equivalent Voice UEs in CEL_DCH State
Counters
Counter ID
Counter Name
Counter Description
67199663
Mean Number of UL
Equivalent Voice UEs in
CEL_DCH State for Cell
67199664
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
Issue 03 (2015-06-30)

971
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020101
Admission Control
WRFD-020101
Admission Control
Duration of Cell Dynamic Shutdown Due to Automatic Shutdown

Counters
Counter ID
Counter Name
Counter Description
67204134
VS.Cell.DynShutDown.Tim
e
Duration of Cell Dynamic

Shutdown Due to Automatic
Shutdown for Cell
Description
This counter provides the duration of cell dynamic shutdown when the cell dynamic shutdown
algorithm takes effect.
Measurement point
After a cell is set up, the RNC measures the accumulated duration of cell dynamic shutdown in
the measurement period.
Formula
None
Unit
s
Issue 03 (2015-06-30)

972
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.Cell.DynShutDown.Tim
e
WRFD-020117
Multi-Carrier Switch off

Based on Traffic Load
WRFD-020122

Based on QoS
Cell Unavailability Duration caused by O&M (Cell)

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Cell.UnavailTime
WRFD-031000

973
BSC6900 UMTS
Counters Related to the Cell Credit Usage

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

974
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
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
Counters Related to the Duration of Max and Min Values of CPICH Power Due to
Cell Breathing
Counters
Counter ID
Counter Name
Counter Description
67202917
VS.CellBreath.CPICHMin.
Time
Duration of Minimum
Values of CPICH Power Due
to Cell Breathing for Cell
67202918
VS.CellBreath.CPICHMax.
Time
Duration of Maximum
Values of CPICH Power Due
to Cell Breathing for Cell
Description
These counters provide the duration of maximum or minimum value of P-CPICH power due to
the downlink load-based dynamic adjustment of P-CPICH algorithm in a cell. Note: 1. The
downlink load-based dynamic adjustment of P-CPICH algorithm refers to the TCP-based intrafrequency load balancing algorithm or load-based dynamic adjustment of P-CPICH algorithm.
2. The preceding two algorithms mutually exclude each other. When the two algorithms are
enabled at the same time, the load-based dynamic adjustment of P-CPICH algorithm takes
precedence. 3. If the two algorithms are disabled in the measurement period, the value of this
counter is zero.
Measurement point
When the downlink cell power load in a cell is heavy according to the load level specified by
the dynamic adjustment of P-CPICH algorithm, the RNC needs to reduce the power of P-CPICH.
However, if the power of P-CPICH reaches the minimum value, the P-CPICH power cannot be
reduced. The controlling RNC (CRNC) measures the accumulated duration of the minimum
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
Issue 03 (2015-06-30)

975
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 maximum value of P-CPICH power for a cell in the measurement
period.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.CellBreath.CPICHMin.
Time
WRFD-020104
Intra Frequency Load

Balance
VS.CellBreath.CPICHMax.
Time
WRFD-020104

Balance
Counters Related to the Number of CPICH Power Adjustments Due to Cell

Breathing
Counters
Counter ID
Counter Name
Counter Description
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 loadbased dynamic adjustment of P-CPICH algorithm in a cell.
Measurement point
When the downlink cell power load in a cell is heavy according to the load level specified by
the dynamic adjustment of P-CPICH algorithm, the RNC needs to reduce the power of P-CPICH.
Issue 03 (2015-06-30)

976
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
Counter Name
Feature ID
Feature Name
VS.CellBreath.CPICHUp
WRFD-020104

Balance
VS.CellBreath.CPICHDown
WRFD-020104

Balance
Counters Related to the Duration of TCP Underload and Overload

Counters
Counter ID
Counter Name
Counter Description
67202919
VS.CellBreath.TCPUnder.T
ime
Duration of TCP Smaller

Than Cell Breathing Lower
Threshold for Cell
67202920
VS.CellBreath.TCPOver.Ti
me
Duration of TCP Greater

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
Issue 03 (2015-06-30)

977
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
Counter Name
Feature ID
Feature Name
VS.CellBreath.TCPUnder.T
ime
WRFD-020104

Balance
VS.CellBreath.TCPOver.Ti
me
WRFD-020104

Balance
Counter ID
Counter Name
Counter Description
67202921
VS.CPICH.MeanPwr
Average CPICH Power for

Cell
Average CPICH Power for Cell

Counters
Description
This counter provides the average P-CPICH power in a cell. Note: When the dynamic adjustment
of P-CPICH algorithm (including the RTWP/TCP-based intra-frequency load balancing
algorithm and load-based dynamic adjustment of P-CPICH algorithm) is enabled, the RNC
adjusts P-CPICH power based on cell load. This counter is measured based on the adjusted PCPICH power.
Issue 03 (2015-06-30)

978
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
Counter Name
Feature ID
Feature Name
VS.CPICH.MeanPwr
WRFD-020101
Admission Control
Counters Related to the Number of Dynamic Channel Conversion Attempts

Between DCHs and FACHs
Counters
Counter ID
Counter Name
Counter Description
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. The preceding counters comply with section "8.2
Radio Bearer control procedures" in 3GPP TS 25.331 (v9.3.0).
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
Issue 03 (2015-06-30)

979
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.C2D.Att
WRFD-021101
Dynamic Channel
(DCCC)
VS.DCCC.D2C.Att
WRFD-021101
Dynamic Channel
(DCCC)

980
BSC6900 UMTS
Counters Related to the Number of UL EDCH DCCC Attempts Based on

Throughput or RLC BO
Counters
Counter ID
Counter Name
Counter Description
67184359
VS.DCCC.AttUpsizing.E2E
.Thr
Number of UL EDCHEDCH DCCC Upsizing

Attempts Based on the
Throughput or RLC BO for
Cell
67196026
VS.DCCC.AttDownsizing.E
2E.Thr
Number of UL EDCHEDCH 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. The preceding counters comply with section "8.2 Radio
Measurement point
RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counters
based on decreases and increases in BE services due to different DCCC strategies in HSUPA
serving cell if uplink services are carried on the E-DCH before and after the reconfiguration.
Issue 03 (2015-06-30)

981
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.AttUpsizing.E2E
.Thr
WRFD-01061208
HSUPA DCCC
VS.DCCC.AttDownsizing.E
2E.Thr
WRFD-01061208
HSUPA DCCC

982
BSC6900 UMTS
Counters Related to the Number of Successful UL EDCH DCCC Operations Based

on Throughput or RLC BO
Counters
Counter ID
Counter Name
Counter Description
67196027
VS.DCCC.SuccUpsizing.E2
E.Thr
Number of Successful UL
EDCH-EDCH DCCC
Upsizings Based on the
Cell
67196028
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. The preceding counters comply with section
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.
Issue 03 (2015-06-30)

983
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.SuccUpsizing.E2
E.Thr
WRFD-01061208
HSUPA DCCC
E2E.Thr
WRFD-01061208
HSUPA DCCC

984
BSC6900 UMTS
Number of UEs Performing Code Adjustment Based on HSDPA

Counters
Counter ID
Counter Name
Counter Description
67195992
VS.LCC.HSDPA.CodeAdj.
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.
Figure 1-421 Physical channel reconfiguration
Formula
None
Issue 03 (2015-06-30)

985
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Att
WRFD-020108
Code Resource Management
Number of UL or DL DCH DCCC Upsizing Attempts Based on Throughput or RLC

BO
Counters
Counter ID
Counter Name
Counter Description
67192585
VS.DCCC.AttUpsizing.DL.
Thr
Number of DL DCH DCCC

Upsizing Attempts Based on
Cell
67192593
VS.DCCC.AttUpsizing.UL.
Thr
Number of UL DCH DCCC

Upsizing Attempts Based on
Cell
Description
This counter provides the number of rate increase attempts for uplink or 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. This counter complies with section
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 uplink or downlink
Issue 03 (2015-06-30)

986
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.AttUpsizing.DL.
Thr
WRFD-021101
Dynamic Channel
(DCCC)
VS.DCCC.AttUpsizing.UL.
Thr
WRFD-021101
Dynamic Channel
(DCCC)

987
BSC6900 UMTS
Number of Successful UL or DL DCH DCCC Upsizings Based on Throughput or

RLC BO
Counters
Counter ID
Counter Name
Counter Description
67192586
VS.DCCC.SuccUpsizing.D
L.Thr
DCH DCCC Upsizings
BO for Cell
67192594
VS.DCCC.SuccUpsizing.U
L.Thr
DCH DCCC Upsizings
BO for Cell
Description
This counter provides the number of successful times the RNC increases uplink or 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. This counter complies with
Measurement point
measures the counter based on different DCCC strategies in the best cell where the UE camps
on if uplink or downlink services are carried on the DCH before and after the reconfiguration.
Issue 03 (2015-06-30)

988
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.SuccUpsizing.D
L.Thr
WRFD-021101
Dynamic Channel
(DCCC)
VS.DCCC.SuccUpsizing.U
L.Thr
WRFD-021101
Dynamic Channel
(DCCC)

989
BSC6900 UMTS
Counters Related to the Number of UL DCH DCCC Downsizing Attempts Based

on Different Strategies
Counters
Counter ID
Counter Name
Counter Description
67192595
UL.Thr

Downsizing Attempts Based
on the Throughput or RLC
BO for Cell
67196032
UL.Cov

on the Coverage (QoS) for
Cell
67196034
UL.Cong

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. The preceding
counters comply with section "8.2 Radio Bearer control procedures" in 3GPP TS 25.331 (v9.3.0).
Measurement point
counter based on different DCCC strategies in the best cell where the UE camps on if uplink
Issue 03 (2015-06-30)

990
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
UL.Thr
WRFD-021101
Dynamic Channel
(DCCC)
UL.Cov
WRFD-021101
Dynamic Channel
(DCCC)
UL.Cong
WRFD-021101
Dynamic Channel
(DCCC)

991
BSC6900 UMTS
Counters Related to the Number of Successful UL DCH DCCC Downsizings Based

on Different Strategies
Counters
Counter ID
Counter Name
Counter Description
67192596
UL.Thr
BO for Cell
67196033
UL.Cov
Cell
67196035
UL.Cong
Based on Resource
Cell
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. The
preceding counters comply with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.331 (v9.3.0).
Measurement point
counter based on different DCCC strategies in the best cell where the UE camps on if uplink
Issue 03 (2015-06-30)

992
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
UL.Thr
WRFD-021101
Dynamic Channel
(DCCC)
UL.Cov
WRFD-021101
Dynamic Channel
(DCCC)
UL.Cong
WRFD-021101
Dynamic Channel
(DCCC)

993
BSC6900 UMTS
Number of UEs Performing Successful Code Adjustment in DL Basic Congestion

Counters
Counter ID
Counter Name
Counter Description
67193409
VS.LCC.LDR.CodeAdj.Suc
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
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.CodeAdj.Suc
c
WRFD-020108

994
BSC6900 UMTS
Number of UEs Performing Successful Code Adjustment Based on HSDPA

Counters
Counter ID
Counter Name
Counter Description
67193410
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. This counter
complies with section "8.2 Radio Bearer control procedures" in 3GPP TS 25.331 (v9.3.0).
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.
Figure 1-426 Physical channel reconfiguration
Formula
None
Issue 03 (2015-06-30)

995
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Succ
WRFD-020108
Duration of Cell Unavailability Due to System Faults

Counters
Counter ID
Counter Name
Counter Description
67204837
VS.Cell.UnavailTime.Sys
Duration of Cell
Unavailability Due to System
Faults for Cell
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
Issue 03 (2015-06-30)

996
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.Cell.UnavailTime.Sys
WRFD-031000
Duration of HSPA Service Unavailability Due to System Fault

Counters
Counter ID
Counter Name
Counter Description
67204838
VS.Cell.HSDPA.UnavailTime
Duration of HSDPA Service

Fault for Cell
67204839
VS.Cell.HSUPA.UnavailTime
Duration of HSUPA Service

Fault for Cell
Description
These counters provide the duration of HSPA service unavailability due to system faults of the
RNC in a cell. These counters are not measured when the whole cell is unavailable. For DCHSDPA users, these counters are measured only in the primary cell. System faults are caused
by various reasons, such as HSUPA and HSDPA channels fail to be set up or the state of HSUPA
and HSDPA channels change from available to unavailable.
Measurement point
In a measurement period, after a cell is set up, the RNC measures the duration of HSPA service
unavailability in a cell provided that the HSPA service is not barred through the LMT.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Cell.HSDPA.UnavailTime
WRFD-031000

997
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.Cell.HSUPA.UnavailTime
WRFD-031000
Number of Attempts to transfer state from CELL_PCH or URA_PCH to

CELL_FACH for cell
Counters
Counter ID
Counter Name
Counter Description
73403799
VS.DCCC.P2F.Att
transfer state from
CELL_PCH to
CELL_FACH for cell
73403802
VS.DCCC.URAP2F.Att
transfer state from
URA_PCH to CELL_FACH
for cell
Description
This counter provides the number of state transition attempts from CELL_PCH or URA_PCH
to CELL_FACH in the cell. This counter complies with section "8.2 Radio Bearer control
Measurement point
The measurement is triggered at point B as shown in the figure. The RNC measures the counter
in the best cell where the UE camps when the UE tries to transit from CELL_PCH or URA_PCH
to CELL_FACH after receiving a CELL UPDATE CONFIRM message from the RNC.
Figure 1-427 Cell update
Issue 03 (2015-06-30)

998
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.P2F.Att
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-021101
Dynamic Channel
(DCCC)
VS.DCCC.URAP2F.Att
WRFD-010202
WRFD-021101

URA-PCH, CELL-FACH)
Dynamic Channel
(DCCC)
Number of Successful state transfer from CELL_PCH or URA_PCH to CELL_FACH

for cell
Counters
Counter ID
Counter Name
Counter Description
73403800
VS.DCCC.P2F.Succ
Number of Successful state

transfer from CELL_PCH to
CELL_FACH for cell
73403803
VS.DCCC.URAP2F.Succ
Number of successful state

transfer from URA_PCH to
CELL_FACH in the best cell.
Description
This counter provides the number of successful state transitions from CELL_PCH or URA_PCH
to CELL_FACH in the best cell. This counter complies with section "8.2 Radio Bearer control
Issue 03 (2015-06-30)

999
BSC6900 UMTS
Measurement point
The measurement is triggered at point C as shown in the figure 1.After sending a CELL UPDATE
CONFIRM message to a UE, the RNC measures the counter in the best cell where the UE camps
if the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message
from the UE and the UE transits from CELL_PCH or URA_PCH to CELL_FACH.
if the RNC receives a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message
from the UE and the UE transits from CELL_PCH or URA_PCH to CELL_FACH.
Issue 03 (2015-06-30)

1000
BSC6900 UMTS
if the RNC receives a UTRAN MOBILITY INFORMATION CONFIRM message from the UE
and the UE transits from CELL_PCH or URA_PCH to CELL_FACH.
if the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from
the UE and the UE transits from CELL_PCH or URA_PCH to CELL_FACH.
Issue 03 (2015-06-30)

1001
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.P2F.Succ
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-021101
Dynamic Channel
(DCCC)
VS.DCCC.URAP2F.Succ
WRFD-010202
WRFD-021101

URA-PCH, CELL-FACH)
Dynamic Channel
(DCCC)
Number of state transfer from CELL_PCH to URA_PCH for cell

Counters
Counter ID
Counter Name
Counter Description
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. This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP
TS 25.331 (v9.3.0).
Measurement point
The measurement is triggered at point B as shown in the figure. The RNC measures the counter
in the best cell where the UE camps when the UE tries to transit from CELL_PCH to URA_PCH
after the RNC receives a CELL UPDATE message from the UE and responds a CELL UPDATE
CONFIRM message.
Issue 03 (2015-06-30)

1002
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.P2URAP
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-021101
Dynamic Channel
(DCCC)
Number of Cell Deletions or Establishments Due to Dynamic Cell Shutdown

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393802
VS.DynClose.CellDel
Number of Cell Deletions

Due to Dynamic Cell
Shutdown

1003
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73393803
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
Related Features
Counter Name
Feature ID
Feature Name
VS.DynClose.CellDel
WRFD-020117

WRFD-020122

Based on QoS
WRFD-020117
WRFD-020122

Based on QoS
Issue 03 (2015-06-30)

1004
BSC6900 UMTS
Number of State Transfer Attempts from CELL_DCH to CELL_PCH for Cell

Counters
Counter ID
Counter Name
Counter Description
73421765
VS.DCCC.D2P.Att

Attempts from CELL_DCH
to CELL_PCH for Cell
Description
This counter provides the number of state transition attempts from CELL_DCH to CELL_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. This counter complies with section "8.2 Radio Bearer control
Measurement point
RADIO BEARER RECONFIGURATION message to the UE, the RNC measures the counter
in the best cell where the UE camps on if the state is transited from CELL_DCH to CELL_PCH.
Issue 03 (2015-06-30)

1005
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.D2P.Att
WRFD-010202

URA-PCH, CELL-FACH)
Number of Successful State Transfers from CELL_DCH to CELL_PCH for Cell

Counters
Counter ID
Counter Name
Counter Description
73421766
VS.DCCC.D2P.Succ

Transfers from CELL_DCH
to CELL_PCH for Cell
Description
This counter provides the number of successful state transitions from CELL_DCH to
CELL_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. This counter complies with section "8.2 Radio Bearer
control procedures" in 3GPP TS 25.331 (v9.3.0).
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.
Issue 03 (2015-06-30)

1006
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.D2P.Succ
WRFD-010202

URA-PCH, CELL-FACH)

1007
BSC6900 UMTS
Number of State Transfer Attempts from CELL_DCH or CELL_FACH to

CELL_PCH for FAST DORMANCY user for Cell
Counters
Counter ID
Counter Name
Counter Description
73421767
VS.DCCC.FastDormUe.DF
2P.Att

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. This counter complies with section
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.
Figure 1-435 physical channel reconfiguration procedure
Issue 03 (2015-06-30)

1008
BSC6900 UMTS
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
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
2P.Att
WRFD-020500

1009
BSC6900 UMTS
Number of Successful State Transfers from CELL_DCH or CELL_FACH to

CELL_PCH for FAST DORMANCY user
Counters
Counter ID
Counter Name
Counter Description
73421768
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. This counter
Measurement point
The measurement is triggered at point B as shown in the following figure. When the RNC
receives a message from a UE supporting the fast dormancy feature, indicating that the UE has
transited from the CELL_FACH or CELL_DCH state to the CELL_PCH state, this counter is
incremented by one in the cell where the UE is camping. When a UE in the CELL_DCH state
performs a soft handover or softer handover, the counter is measured in the best cell in the active
set for soft handovers. The best cell is obtained before the state transition.
Issue 03 (2015-06-30)

1010
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
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
2P.Succ
WRFD-020500

1011
BSC6900 UMTS
Number of Attempts to transfer state from CELL_PCH or URA_PCH to CELL_DCH

for cell
Counters
Counter ID
Counter Name
Counter Description
73421933
VS.DCCC.P2D.Att
transfer state from
CELL_PCH to CELL_DCH
for cell
73421935
VS.DCCC.URAP2D.Att
transfer state from
URA_PCH to CELL_DCH
for cell
Description
to CELL_DCH in the cell. This counter complies with section "8.2 Radio Bearer control
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a
CELL UPDATE CONFIRM message, the RNC measures the counter in the cell where the UE
camps on before the state transition, if the UE tries to transit from CELL_PCH or URA_PCH
to CELL_DCH.
Issue 03 (2015-06-30)

1012
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.P2D.Att
WRFD-010202

URA-PCH, CELL-FACH)
VS.DCCC.URAP2D.Att
WRFD-010202

URA-PCH, CELL-FACH)
Number of Successful state transfer from CELL_PCH or URA_PCH to CELL_DCH

for cell
Counters
Counter ID
Counter Name
Counter Description
73421934
VS.DCCC.P2D.Succ
Number of Successful state

transfer from CELL_PCH to
CELL_DCH for cell
73421936
VS.DCCC.URAP2D.Succ
Number of successful state

transfer from URA_PCH to
CELL_DCH in the best cell.
Description
to CELL_DCH in the cell. This counter complies with section "8.2 Radio Bearer control
Measurement point
The measurement is triggered at point C 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 or URA_PCH to CELL_DCH.
Issue 03 (2015-06-30)

1013
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.P2D.Succ
WRFD-010202

URA-PCH, CELL-FACH)
VS.DCCC.URAP2D.Succ
WRFD-010202

URA-PCH, CELL-FACH)

1014
BSC6900 UMTS
Number of Attempts of CELL_PCH/URA_PCH-to-CELL_DCH State Transition

Together with DRD for Cell
Counters
Counter ID
Counter Name
Counter Description
73422068
VS.DCCC.P2D.DRD.Att
Number of Attempts of
CELL_PCH/URA_PCH-toCELL_DCH State Transition
Together with DRD for Cell
Description
This counter provides the number of times the RNC attempts to trigger the state transition from
CELL_PCH or URA_PCH to CELL_DCH together with DRD in a cell. This counter complies
with section "8.2 Radio Bearer control procedures" in 3GPP TS 25.331 (v9.3.0).
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends the UE a
CELL UPDATE CONFIRM message, instructing the UE to transfer its state from CELL_PCH
or URA_PCH to CELL_DCH and to trigger DRD, this counter is measured in the cell that the
UE camps on when sending the CELL UPDATE message.
Issue 03 (2015-06-30)

1015
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.P2D.DRD.Att
WRFD-010202

URA-PCH, CELL-FACH)
Number of Successful CELL_PCH/URA_PCH-to-CELL_DCH State Transitions

Together with DRDs for Cell
Counters
Counter ID
Counter Name
Counter Description
73422069
VS.DCCC.P2D.DRD.Succ
CELL_PCH/URA_PCH-toCELL_DCH State
Transitions Together with
DRDs for Cell
Description
This counter provides the number of times a UE successfully transit its state from CELL_PCH
or URA_PCH to CELL_DCH together with DRDs in a cell. This counter complies with section
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.
Issue 03 (2015-06-30)

1016
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.P2D.DRD.Succ
WRFD-010202

URA-PCH, CELL-FACH)
Number of CPICH Power Adjustments Based on RTWP for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423313
VS.ULB.CPICH.AdjustNum
Number of CPICH Power

Adjustments Based on
RTWP for Cell

1017
BSC6900 UMTS
Description
This counter provides the number of power adjustments of the Common Pilot Channel (CPICH)
triggered by the RTWP-based uplink intra-frequency load balancing algorithm. RTWP is short
for Received Total Wideband Power (RTWP).
Measurement point
At point A as shown in the figure, When RTWP is higher than a certain threshold, the RNC
needs to decrease CPICH power. When RTWP is lower than a certain threshold, the RNC needs
to increase CPICH power. This counter provides the accumulated number of CPICH power
adjustments in a measurement period in a cell.
Figure 1-443 Cell reconfiguration procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ULB.CPICH.AdjustNum
WRFD-020104

Balance

1018
BSC6900 UMTS
Duration of PCPICH Power Under Minimum RTWP Threshold

Counters
Counter ID
Counter Name
Counter Description
73441123
VS.ULB.CPICHMin.Time
Duration of PCPICH Power

Under Minimum RTWP
Threshold
Description
This counter provides the duration of CPICH power being lower than Min Transmit Power of
P-CPICH when the CPICH power is adjusted by the RTWP-based uplink intra-frequency load
balancing algorithm.
Measurement point
The measurement starts when CPICH power is adjusted to be lower than Min Transmit Power
of P-CPICH and stops when CPICH power is adjusted to be higher than Min Transmit Power
of PCPICH. This counter is the accumulated value of such durations in the measurement period.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ULB.CPICHMin.Time
WRFD-020104

Balance

1019
BSC6900 UMTS
Number of State Transfer Attempts from CELL_DCH to CELL_PCH or URA_PCH

for Cell for PS service
Counters
Counter ID
Counter Name
Counter Description
73422160
VS.HSDPA.H2P.Att

to CELL_PCH or URA_PCH
for Cell for HSDPA service
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
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 services attempts to transit from
the CELL_DCH state to the CELL_PCH or URA_PCH state. This counter complies with section
Measurement point
The measurement is triggered at point A in the following figure. When the RNC sends an RB
reconfiguration message to a UE, requesting the UE to switch from the CELL_DCH state to the
CELL_PCH or URA_PCH state in the PS domain, this counter is measured based on the bearer
channel type in the best cell for the UE. For multi-carrier users, this counter is measured only
in the primary cell.
Issue 03 (2015-06-30)

1020
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSDPA.H2P.Att
WRFD-01061111
HSDPA State Transition
VS.HSUPA.E2P.Att
WRFD-010202

URA-PCH, CELL-FACH)
VS.PSR99.D2P.Att
WRFD-010202

URA-PCH, CELL-FACH)

1021
BSC6900 UMTS
Number of Successful Times That a UE Performing PS Services Transits to

CELL_PCH or URA_PCH State for cell
Counters
Counter ID
Counter Name
Counter Description
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
73422163
VS.HSUPA.E2P.Succ

That a UE Performing
HSUPA Services Transits to
CELL_PCH or URA_PCH
State for cell
73422165
VS.PSR99.D2P.Succ

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 services successfully transits
from the CELL_DCH state to the CELL_PCH or URA_PCH state. This counter complies with
Measurement point
The measurement is triggered at point B in the following figure. When the RNC receives an RB
reconfiguration complete message from a UE, indicating that the UE has switched from the
CELL_DCH state to the CELL_PCH or URA_PCH state in the PS domain, this counter is
measured based on the bearer channel type in the best cell for the UE. For multi-carrier users,
this counter is measured only in the primary cell.
Issue 03 (2015-06-30)

1022
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSDPA.H2P.Succ
WRFD-01061111
VS.HSUPA.E2P.Succ
WRFD-010202

URA-PCH, CELL-FACH)
VS.PSR99.D2P.Succ
WRFD-010202

URA-PCH, CELL-FACH)

1023
BSC6900 UMTS
Number of Times That PS R99 Service Rate Is Found to Be Higher than HSUPA
Service Rate
Counters
Counter ID
Counter Name
Counter Description
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. This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.331 (v9.3.0).
Measurement point
This counter is increased by one each time the PS R99 service rate is found to be higher than
the HSUPA service rate in the period of time specified by the fairness period timer length
parameter.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPAR99.Unfairness
WRFD-020131
Optimization of R99 and

HSUPA Users Fairness

1024
BSC6900 UMTS
Number of PS R99 BE Rate Reduction Requests Triggered by Unfairness Between

PS R99 Service Rate and HSUPA Service Rate
Counters
Counter ID
Counter Name
Counter Description
73423358
VS.HSUPAR99.Unfairness.
R99BERateDown
Number of PS R99 BE Rate

Reduction Requests
Triggered by Unfairness
Between PS R99 Service
Rate and HSUPA Service
Rate
Description
This counter provides the number of times that PS R99 BE users are selected for rate reduction
in the cell in the case that the PS R99 BE service rate is found to be higher than the HSUPA
service rate.
Measurement point
The measurement is triggered at point A shown in figure 1. When the RNC determines that the
PS R99 service rate is higher than the HSUPA service rate in an HSUPA cell, the RNC reduces
the rate of certain R99 BE users. The measurement is triggered in the best HSUPA cell when
the RNC sends a RADIO BERER RECONFIGURATION message to the UE.
Issue 03 (2015-06-30)

1025
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPAR99.Unfairness.
R99BERateDown
WRFD-020131
Optimization of R99 and

HSUPA Users Fairness
Duration of CPU Resource Insufficiency Reported by NodeB

Counters
Counter ID
Counter Name
Counter Description
73411191
VS.NodeB.CPU.Cong.Dur
Duration of CPU Resource

Insufficiency Reported by
NodeB for Cell
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
Issue 03 (2015-06-30)

1026
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.NodeB.CPU.Cong.Dur
WRFD-040100
Flow Control
Congestion Duration of DCCHs, DTCHs and CCCHs Carried over FACHs for Cell
Counters
Counter ID
Counter Name
Counter Description
73439970
VS.FACH.DCCH.CONG.TI
ME
Congestion Duration of
DCCHs Carried over FACHs
for Cell
73439971
VS.FACH.DTCH.CONG.TI
ME
DTCHs Carried over FACHs
for Cell
73424009
VS.FACH.CCCH.CONG.TI
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
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
Issue 03 (2015-06-30)

1027
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.FACH.DCCH.CONG.TI
ME
WRFD-010202

URA-PCH, CELL-FACH)
VS.FACH.DTCH.CONG.TI
ME
WRFD-010202

URA-PCH, CELL-FACH)
VS.FACH.CCCH.CONG.TI
ME
WRFD-010202

URA-PCH, CELL-FACH)
Number of UEs Involved in AMR-WB SF Reconfiguration When a Cell Is in the

Basic Congestion State
Counters
Counter ID
Counter Name
Counter Description
73427917
VS.LCC.LDR.AMRSfRecfg
Number of UEs Involved in

AMR-WB SF
Reconfiguration When a Cell
Is in the Basic Congestion
State
Description
When the code resources of a cell are in the basic congestion state and the AMR-WB SF
reconfiguration action is allowed in the cell (achieved by running the ADD UCELLLDR or
MOD UCELLLDR command), the RNC performs AMR-WB SF reconfiguration on UEs that
process AMR-WB services and help save code resources after data rates are reduced. This
counter provides the number of UEs involved in AMR-WB SF reconfiguration in a cell. This
counter can reflect AMR-WB performance.
Measurement point
This counter is incremented by one every time the RNC involves one UE in AMR-WB SF
reconfiguration in a cell that is in the basic congestion state.
Formula
None
Issue 03 (2015-06-30)

1028
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.AMRSfRecfg
WRFD-020701
AMR/WB-AMR Speech
Rates Control
1.12.2 Algorithm Measurement 2 <per 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.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441210
VS.SirDist.OLPC.
User
Number of UEs
Using OLPC
Enhancement Based
on SIRerror
Distribution for Cell
BSC6900
V900R013
73441212
VS.BackGroundNo
ise.Mean
Average Uplink
Background Noise in
a Cell
BSC6900
V900R014
73423948
VS.BackGroundNo
ise.Update
Number of
Automatic Uplink
Background Noise
Updates in a Cell
BSC6900
V900R014
73441215
VS.BackGroundNo
ise.Max
Maximum Uplink
Background Noise in
a Cell
BSC6900
V900R014
73423955
VS.RAC.TrChSwit
ch.Fail.DCCH.Con
g.F2D
Counters Related to
the Failed Number of
F2D Process
Triggered by DCCH
Congestion
BSC6900
V900R014

1029
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423956
VS.RAC.TrChSwit
ch.Fail.DCCH.Con
g.D2F
Counters Related to
D2F Process
Triggered by DCCH
Congestion
BSC6900
V900R014
73423957
VS.RAC.TrChSwit
ch.Fail.DSP.Overlo
ad.D2F
Counters Related to
D2F Process
Triggered by DSP
Overload
BSC6900
V900R014
73423994
VS.HSUPA.TgtRoTInc
Number of times the

RoT value is
increased
BSC6900
V900R014
73423995
VS.HSUPA.TgtRo
TDec
Number of times the

RoT value is
decreased
BSC6900
V900R014
73424209
VS.HSUPA.TTI2to
10.ADMCE.Succ
Number of
Successful TTI
Switchovers Based
on Admitted CEs
During RB
Reconfiguration in a
Cell(2ms to 10ms)
BSC6900
V900R014
73424210
VS.HSUPA.TTI2to
10.COVER.Succ
Number of
Successful TTI
Switchovers Based
on Coverage During
RB Reconfiguration
in a Cell(2ms to
10ms)
BSC6900
V900R014
73424211
VS.HSUPA.TTI2to
10.ResRTWP.Succ
Number of
Successful TTI
Switchovers Based
on RTWP During RB
Cell(2ms to 10ms)
BSC6900
V900R014

1030
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424212
VS.HSUPA.TTI2to
10.ResUsedCE.Suc
c
Number of
Successful TTI
Switchovers Based
on Number of
Occupied CEs
During RB
Cell(2ms to 10ms)
BSC6900
V900R014
73424214
VS.RABEstabE2D.
COVER.Succ
Number of Times
HSUPA UEs
Processing BE
Services Succeed in
Setting Up RABs
over the DCH in
Case of Weak
Coverage
BSC6900
V900R014
73441241
VS.AC.CongCtl.M
eanAcBarNum.Abo
veR6.PS
Mean Number of PS
Access Classes
Restricted Due to
Cell Resource
Congestion (R6 or
Later)
BSC6900
V900R014
73441243
VS.AC.CongCtl.M
eanAcBarNum.UnderR5
Mean Number of
Access Classes
Restricted Due to
Cell Resource
Congestion (R5 or
Earlier)
BSC6900
V900R014
73441244
VS.AC.CongCtl.M
eanAcBarNum.Abo
veR6.CS
Mean Number of CS
Access Classes
Restricted Due to
Cell Resource
Congestion (R6 or
Later)
BSC6900
V900R014
73441245
VS.AC.CongCtl.Ti
me
Duration of Access
Class Restriction
Triggered by Cell
Resource
Congestion
BSC6900
V900R014
73441246
VS.LCC.CLB.CS.I
nterFreq
Number of CS UEs
Involved in InterFrequency Loadbased Handovers in a
CS CLB Cell
BSC6900
V900R014

1031
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441247
VS.LCC.CLB.PS.I
nterFreq
Number of PS UEs
Involved in InterFrequency Loadbased Handovers in a
PS CLB Cell
BSC6900
V900R014
73424471
VS.HSUPA.TTI2to
10.ResIUB.Succ
Number of
Successful TTI
Switchovers Based
on Iub Resources
During RB
Cell(2ms to 10ms)
BSC6900
V900R014
73424472
VS.HSDPA.DynCf
gAtt.LongCQI
Number of Attempts
to Configure a Long
CQI Feedback
Period for a Cell
BSC6900
V900R014
73424473
VS.HSDPA.DynCf
gAtt.ShortCQI
Number of Attempts
to Configure a Short
CQI Feedback
Period for a Cell
BSC6900
V900R014
73424474
VS.ULBler.BE.Lar
ge
Number of Attempts
to Configure BLER
in a Congested Cell
BSC6900
V900R014
73424475
VS.ULBler.BE.Sm
all
Number of Attempts
to Configure BLER
in a Normal Cell
BSC6900
V900R014
73424760
VS.RAB.SpecialUs
er.AbnormRel.CS
Number of CS RABs
Abnormally
Released for Special
UEs for Cell
BSC6900
V900R014
73424761
VS.RAB.SpecialUs
er.NormRel.CS
Number of CS RABs
Normally Released
for Special UEs for
Cell
BSC6900
V900R014
73441505
VS.MeanULActual
PowerLoad
Mean Uplink Actual

Cell Load
BSC6900
V900R014
73424787
VS.MaxULActualPowerLoad
Max Uplink Actual

Cell Load
BSC6900
V900R014
73424788
VS.MinULActualPowerLoad
Min Uplink Actual

Cell Load
BSC6900
V900R014

1032
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424896
VS.DCCC.Att.F2U
Number of
CELL_FACH to
URA_PCH State
Transition Attempts
for Cell
BSC6900
V900R014
73424897
VS.DCCC.Succ.F2
U
Number of
Successful
CELL_FACH to
URA_PCH State
Transitions for Cell
BSC6900
V900R014
73424898
VS.DCCC.Att.D2U
Number of
CELL_DCH to
URA_PCH State
Transition Attempts
for Cell
BSC6900
V900R014
73424899
VS.DCCC.Succ.D2
U
Number of
Successful
CELL_DCH to
URA_PCH State
BSC6900
V900R014
73424900
VS.HSUPA.SmallR
snAdj.TTI2ms
Times That Small

Target
Retransmission
Numbers Are
Adjusted for HSUPA
2 ms TTI UEs for
Cell
BSC6900
V900R016C00
73424901
VS.HSUPA.SmallR
snAdj.TTI10ms
Times That Small

Target
Retransmission
Numbers Are
Adjusted for HSUPA
10 ms TTI UEs for
Cell
BSC6900
V900R016C00
73425824
VS.DL.DPCH.Opti
PilotPOAttNum
Number of Pilot PO
Optimization
Attempts in the DL
DPCH for Cell
BSC6900
V900R015C00
73425825
VS.DL.DPCH.NormalPilotPOAttNu
m
Number of Normal
Pilot PO Attempts in
the DL DPCH for
Cell
BSC6900
V900R015C00

1033
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426173
VS.TotalDesense.N
um
Total number of
times a micro cell
transits to the total
desensitization state
BSC6900
V900R015C00
73426176
VS.TotalDesense.Ti
me
Total time periods of

the total
for a micro cell
BSC6900
V900R015C00
73426179
VS.MeanDesensePwr
Average
desensitization
intensity for a micro
cell
BSC6900
V900R015C00
73426283
VS.LCG.ULCredit
Usage.Mean
Average Uplink
Credit Usage of LCG
for Cell
BSC6900
V900R015C00
73426284
VS.LCG.ULCredit
Usage.Max
Maximum Uplink
Credit Usage of LCG
for Cell
BSC6900
V900R015C00
73426333
VS.DCCC.Att.F2D.
AfterP2F
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
BSC6900
V900R015C00
73426334
VS.DCCC.Succ.F2
D.AfterP2F
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
BSC6900
V900R015C00

1034
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73443289
VS.Random.Access
.ACKNum.Mean
Average Number of
Acknowledged
PRACH Preambles
and Granted
Common E-DCH
Resources During
Random Access in a
Cell
BSC6900
V900R015C01
73426799
VS.AttRlReEst.CS
Number of Call
Reestablishment
Attempts for CS
Services for Cell
BSC6900
V900R015C01
73426800
VS.SuccRlReEst.C
S
Number of
Successful Call
Reestablishments for
CS Services for Cell
BSC6900
V900R015C01
73426804
VS.AttRlReEst.PS
Number of Call
Reestablishment
Attempts for PS
Services for Cell
BSC6900
V900R015C01
73426805
VS.SuccRlReEst.P
S
Number of
Successful Call
Reestablishments for
PS Services for Cell
BSC6900
V900R015C01
73428168
VS.PSR99.P2D.Att
Number of P2D State

Transition Attempts
for Cell (UL and DL
Carried on DCH)
BSC6900
V900R016C00
73428169
VS.PSR99.P2D.Suc
c
Number of P2D State

Transition Success
for Cell (UL and DL
Carried on DCH)
BSC6900
V900R016C00
73428170
VS.HSDPA.P2H.At
t
Number of P2D State

Transition Attempts
for Cell (DL Carried
on HSDPA)
BSC6900
V900R016C00
73428171
VS.HSDPA.P2H.Su
cc
Number of P2D State

Transition Success
on HSDPA)
BSC6900
V900R016C00

1035
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428172
VS.HSUPA.P2E.At
t
Number of P2D State

Transition Attempts
for Cell (UL Carried
on HSUPA)
BSC6900
V900R016C00
73428173
VS.HSUPA.P2E.Su
cc
Number of P2D State

Transition Success
on HSUPA)
BSC6900
V900R016C00
73428328
VS.LCG.ULCreditUsage.0
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
between 0 per mill
(Included) and 250
per mill
BSC6900
V900R016C00
73428329
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 500
per mill
BSC6900
V900R016C00
73428330
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 550
per mill
BSC6900
V900R016C00
73428331
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 600
per mill
BSC6900
V900R016C00
73428332
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 650
per mill
BSC6900
V900R016C00

1036
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428333
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 700
per mill
BSC6900
V900R016C00
73428334
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 750
per mill
BSC6900
V900R016C00
73428335
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 800
per mill
BSC6900
V900R016C00
73428336
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 850
per mill
BSC6900
V900R016C00
73428337
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 900
per mill
BSC6900
V900R016C00
73428338
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is
(Included) and 950
per mill
BSC6900
V900R016C00

1037
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428339
Number of Times
That LCG Uplink
Credit Usage for UE
Admission Is Greater
than or Equal to 950
per mill
BSC6900
V900R016C00
73428444
VS.HSPA.ServCellChg.
1A1COptTrig
Number of HSPA
Serving Cell
Changes Triggered
by Event 1A or 1C
for Cell
BSC6900
V900R016C00
73428445
1DOptTrig
Number of HSPA
Serving Cell
Changes Triggered
by Event 1D for Cell
BSC6900
V900R016C00
73428521
VS.Cell.UnavailTi
me.NodeBBLK
Duration of Cell
Unavailability due to
NodeB Blocking
BSC6900
V900R016C00
73428525
VS.U2LProhibited.
SPID.Coverage
Number of Times
That Coverage-based
UMTS-to-LTE
Redirections or
Handovers Are
Prohibited due to
SPID Reasons
BSC6900
V900R016C00
73428526
VS.FastU2LProhib
ited.SPID
Number of Times
That UMTS-to-LTE
Fast Returns or
Quick Cell
Reselections Are
Prohibited due to
SPID Reasons
BSC6900
V900R016C00
73444379
VS.RAC.AdjUlTot
alEqUserNum.Mea
n
Average Number of
Adjusted Uplink
Equivalent Users for
Cell
BSC6900
V900R016C00
73428534
VS.RAC.AdjUlTot
alEqUserNum.Max
Maximum Number
of Adjusted Uplink
Cell
BSC6900
V900R016C00

1038
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428535
VS.RAC.AdjUlTot
alEqUserNum.Min
Minimum Number of
Adjusted Uplink
Cell
BSC6900
V900R016C00
73428628
VS.UMI.Dedicated
Pri.UMTS.High
Number of Times
that UMTS Is
Configured as the
Highest Frequency
Priority
BSC6900
V900R016C00
73428629
VS.UMI.Dedicated
Pri.LTE.High
Number of Times
that LTE Is
Configured as the
Highest Frequency
Priority
BSC6900
V900R016C00
73428638
VS.RAC.UL.EqvUs
erNum.Max
Maximum Number
of Uplink Equivalent
Users on All DCHs
for Cell
BSC6900
V900R016C00
73428639
VS.RAC.DL.EqvUs
erNum.Max
Maximum Number
of Downlink
Equivalent Users on
All DCHs for Cell
BSC6900
V900R016C00
73428759
VS.RAC.Platinum.
Preempt.Cong
Number of
Preemptions for
Platinum User
BSC6900
V900R016C00
73428797
VS.U2LProhibited.
SPID.Service
Number of Times
That Service-based
UMTS-to-LTE
Redirections or
Handovers Are
Prohibited due to
SPID Reasons
BSC6900
V900R016C00
73428798
VS.U2LProhibited.
SPID.Load
Number of Times
That Load-based
U2L Redirections or
Handovers Are
Prohibited due to
SPID Reasons
BSC6900
V900R016C00

1039
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428885
VS.DCCC.Fail.F2D
.AfterP2F.Cong
Number of Failed
State Transitions
from CELL_PCH/
URA_PCH to
CELL_FACH and
then to CELL_DCH
for Existing Data
Transmission
Requirements Due to
Resource
Congestion for Cell
BSC6900
V900R016C00
73428886
VS.AMRNB.DL.Ra
teUp.Tcp
Number of Times
That Downlink Rate
Increase Is Triggered
for NB-AMR
Services for Cell
(Triggered by
Downlink Transmit
Power)
BSC6900
V900R016C00
73428887
VS.AMRNB.DL.Ra
teDown.Tcp
Number of Times
That Downlink Rate
Reduction Is
Triggered for NBAMR Services for
Cell (Triggered by
Downlink Transmit
Power)
BSC6900
V900R016C00
73428888
VS.AMRWB.DL.R
ateUp.Tcp
Number of Times
That Downlink Rate
for WB-AMR
Services for Cell
(Triggered by
Downlink Transmit
Power)
BSC6900
V900R016C00
73428889
VS.AMRWB.DL.R
ateDown.Tcp
Number of Times
That Downlink Rate
Reduction Is
Triggered for WBAMR Services for
Cell (Triggered by
Downlink Transmit
Power)
BSC6900
V900R016C00

1040
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428890
VS.AMRNB.UL.Ra
teUp.UeTxPwr
Number of Times
That Uplink Rate
for NB-AMR
Services for Cell
(Triggered by UE
Transmit Power)
BSC6900
V900R016C00
73428891
VS.AMRNB.UL.Ra
teDown.UeTxPwr
Number of Times
That Uplink Rate
Reduction Is
Cell (Triggered by
UE Transmit Power)
BSC6900
V900R016C00
73428892
VS.AMRWB.UL.R
ateUp.UeTxPwr
Number of Times
That Uplink Rate
for WB-AMR
Services for Cell
(Triggered by UE
Transmit Power)
BSC6900
V900R016C00
73428893
VS.AMRWB.UL.R
ateDown.UeTxPwr
Number of Times
That Uplink Rate
Reduction Is
Cell (Triggered by
UE Transmit Power)
BSC6900
V900R016C00
73428894
VS.AMRNB.UL.Ra
teUp.TRFO
Number of Times
That Uplink Rate
for NB-AMR
Services for Cell
(Based on TrFO)
BSC6900
V900R016C00
73428895
VS.AMRNB.UL.Ra
teDown.TRFO
Number of Times
That Uplink Rate
Reduction Is
Cell (Based on
TrFO)
BSC6900
V900R016C00

1041
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428896
VS.AMRWB.UL.R
ateUp.TRFO
Number of Times
That Uplink Rate
for WB-AMR
Services for Cell
(Based on TrFO)
BSC6900
V900R016C00
73428897
VS.AMRWB.UL.R
ateDown.TRFO
Number of Times
That Uplink Rate
Reduction Is
Cell (Based on
TrFO)
BSC6900
V900R016C00
73428898
VS.LCC.LDR.AM
RWBRateUL
Number of Times
That Rate Reduction
Is Performed for
WB-AMR Services
due to Uplink Basic
Congestion for Cell
BSC6900
V900R016C00
73428899
VS.LCC.LDR.AM
RWBRateDL
Number of Times
That Rate Reduction
Is Performed for
WB-AMR Services
due to Downlink
Cell
BSC6900
V900R016C00
73428900
VS.AirLoad.Conge
stion.Num
Number of Times the

Air Interface Load
Enters the Congested
State for Cell
BSC6900
V900R016C00
73428901
VS.AirLoad.Conge
stion.Time
Time During Which

the Air Interface
Load Is in the
Congested State for
Cell
BSC6900
V900R016C00
73444481
VS.Cell.HspaCom
mChCodeNotOpti
mum.Time
Duration During
Which HSPA
Common Channel
Codes Are in the
Non-Optimum State
for Cell
BSC6900
V900R016C00

1042
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429233
VS.RAC.RRCReq.
Preempt.Cong
Number of
Preemptions
Performed During an
RRC Connection
Setup Procedure for
Cell
BSC6900
V900R017C00
73429234
VS.RAC.F2D.Pree
mpt.Cong
Number of
Preemptions
Performed During an
F2D Procedure for
Cell
BSC6900
V900R017C00
73429235
VS.RAC.P2D.Pree
mpt.Cong
Number of
Preemptions
Performed During a
P2D Procedure for
Cell
BSC6900
V900R017C00
73446349
VS.RAB.Mean.GB
R.DL.Throughput.
0
Mean Number of
RABs Configured
with the GBR
Management Policy
in DL Throughput
Range 0 for Cell
BSC6900
V900R017C10
73446350
VS.RAB.Mean.GB
R.DL.Throughput.
1
Mean Number of
RABs Configured
with the GBR
Management Policy
in DL Throughput
Range 1 for Cell
BSC6900
V900R017C10
73446351
VS.RAB.Mean.GB
R.DL.Throughput.
2
Mean Number of
RABs Configured
with the GBR
Management Policy
in DL Throughput
Range 2 for Cell
BSC6900
V900R017C10
73446352
VS.RAB.Mean.GB
R.DL.Throughput.
3
Mean Number of
RABs Configured
with the GBR
Management Policy
in DL Throughput
Range 3 for Cell
BSC6900
V900R017C10

1043
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73446353
VS.RAB.Mean.GB
R.DL.Throughput.
4
Mean Number of
RABs Configured
with the GBR
Management Policy
in DL Throughput
Range 4 for Cell
BSC6900
V900R017C10
73446354
VS.RAB.Mean.GB
R.DL.Throughput.
5
Mean Number of
RABs Configured
with the GBR
Management Policy
in DL Throughput
Range 5 for Cell
BSC6900
V900R017C10
73446355
VS.RAB.Mean.GB
R.DL.Throughput.
6
Mean Number of
RABs Configured
with the GBR
Management Policy
in DL Throughput
Range 6 for Cell
BSC6900
V900R017C10
73430283
VS.AbnormUE.Be
Thrup.D2F.Att
Number of
Throughput-based
D2F State Transition
Attempts Made by
UEs with
Abnormally Low
Throughput for Cell
BSC6900
V900R017C10
73430284
VS.AbnormUE.Be
Thrup.D2F.Succ
Number of
Successful
Throughput-based
D2F State
Transitions by UEs
with Abnormally
Low Throughput for
Cell
BSC6900
V900R017C10
73430321
VS.LoadAndEcNo
Based.P2D.Att
Number of P2D State

Transition Attempts
based on Load and
Ec/N0 for Cell
BSC6900
V900R017C10
73430322
VS.LoadAndEcNo
Based.P2D.Succ
Number of
Successful P2D State
Transitions based on
Load and Ec/N0 for
Cell
BSC6900
V900R017C10

1044
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430361
VS.RlReEst.D2F.A
tt
Number of
CELL_DCH-toCELL_FACH
Reconfiguration and
Reestablishment
Attempts for Cell
BSC6900
V900R017C10
73430362
VS.RlReEst.D2F.S
ucc
Number of
Successful
Reconfiguration and
Reestablishment
Attempts for Cell
BSC6900
V900R017C10
None
Average Number of UEs Using OLPC Enhancement Based on SIRerror

Distribution
Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)

1045
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SirDist.OLPC.User
WRFD-020503
Outer Loop Power Control
Average and Maximum Uplink Background Noise

Counters
Counter ID
Counter Name
Counter Description
73441212
VS.BackGroundNoise.Mean
Average Uplink Background

Noise in a Cell
73441215
VS.BackGroundNoise.Max
Maximum Uplink
Background Noise in a Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73423946
VS.BackGroundNoise.CUM
Accumulated Totally
Background Noise for Cell
73423947
VS.BackGroundNoise.SAM
PLE
Number of the Background

Noise for Cell
Description
These counters provide the average and maximum uplink background noise, respectively, in a
cell.
Measurement point
the NodeB a COMMON MEASUREMENT REPORT message about the RTWP of a cell every
1s. RNC calculates the uplink background noise of cell according to measurement report and
Issue 03 (2015-06-30)

1046
BSC6900 UMTS
sample times added. At the end of a measurement period, the average uplink background noise
is obtained by dividing the accumulated value by the sample number. The maximum uplink
background noise is also obtained at the end of the measurement period.
Formula
VS.BackGroundNoise.Mean = ([VS.BackGroundNoise.CUM]/
[VS.BackGroundNoise.SAMPLE]-{1121})/{10}
Unit
dBm
Related Features
Counter Name
Feature ID
Feature Name
VS.BackGroundNoise.Mean
WRFD-020102
Load Measurement
VS.BackGroundNoise.Max
WRFD-020102
Load Measurement
Number of Automatic Uplink Background Noise Updates

Counters
Counter ID
Counter Name
Counter Description
73423948
VS.BackGroundNoise.Update
Number of Automatic Uplink

Background Noise Updates
in a Cell
Description
This counter provides the number of automatic uplink background noise updates in a cell.
Issue 03 (2015-06-30)

1047
BSC6900 UMTS
Measurement point
The measurement is triggered when the RNC makes a decision on a cell background noise update
during the period when the algorithm for automatic uplink background noise updates takes effect.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.BackGroundNoise.Update
WRFD-020102
Load Measurement
Counters Related to the Number of Failed in Channal Transfering Process

Counters
Counter ID
Counter Name
Counter Description
73423955
CCH.Cong.F2D
Counters Related to the

Failed Number of F2D
Process Triggered by DCCH
Congestion
73423956
CCH.Cong.D2F

Failed Number of D2F
Process Triggered by DCCH
Congestion
73423957
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.
The preceding counters comply with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.331 (v9.3.0).
Issue 03 (2015-06-30)

1048
BSC6900 UMTS
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
Related Features
Counter Name
Feature ID
Feature Name
CCH.Cong.F2D
WRFD-020101
Admission Control
CCH.Cong.D2F
WRFD-020101
Admission Control
SP.Overload.D2F
WRFD-020101
Admission Control
Number of RoT adjustments in an HSUPA cell

Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)

1049
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.TgtRoTInc
WRFD-140211
Dynamic Target RoT

Adjustment
VS.HSUPA.TgtRoTDec
WRFD-140211
Dynamic Target RoT

Adjustment
Number of Successful TTI Switchovers with Various Causes During RB

Reconfiguration in a Cell(2ms to 10ms)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424209
VS.HSUPA.TTI2to10.ADM
CE.Succ
Number of Successful TTI

Switchovers Based on
Admitted CEs During RB
Reconfiguration in a Cell
(2ms to 10ms)
73424210
VS.HSUPA.TTI2to10.COV
ER.Succ

Coverage During RB
(2ms to 10ms)
73424211
VS.HSUPA.TTI2to10.ResR
TWP.Succ

RTWP During RB
(2ms to 10ms)
73424212
VS.HSUPA.TTI2to10.ResU
sedCE.Succ

Number of Occupied CEs
During RB Reconfiguration
in a Cell(2ms to 10ms)

1050
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73424471
VS.HSUPA.TTI2to10.ResI
UB.Succ

Switchovers Based on Iub
Resources During RB
(2ms to 10ms)
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. The preceding counters comply with
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-448 RB reconfig procedure
Issue 03 (2015-06-30)

1051
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.TTI2to10.ADM
CE.Succ
WRFD-01061404
HSUPA 2ms/10ms TTI

Handover
VS.HSUPA.TTI2to10.COV
ER.Succ
WRFD-010690
TTI Switch for BE Services

Based on Coverage
WRFD-01061404
HSUPA 2ms/10ms TTI

Handover
VS.HSUPA.TTI2to10.ResR
TWP.Succ
WRFD-01061404
HSUPA 2ms/10ms TTI

Handover
VS.HSUPA.TTI2to10.ResU
sedCE.Succ
WRFD-01061404
HSUPA 2ms/10ms TTI

Handover
VS.HSUPA.TTI2to10.ResI
UB.Succ
WRFD-01061404
HSUPA 2ms/10ms TTI

Handover
Number of Times HSUPA UEs Processing BE Services Succeed in Setting Up RABs

over the DCH in Case of Weak Coverage
Counters
Counter ID
Counter Name
Counter Description
73424214
VS.RABEstabE2D.COVER.
Succ
Number of Times HSUPA

UEs Processing BE Services
Succeed in Setting Up RABs
over the DCH in Case of
Weak Coverage
Description
This counter provides the number of times HSUPA UEs processing BE services succeed in
setting up RABs over the DCH in case of weak coverage.
Issue 03 (2015-06-30)

1052
BSC6900 UMTS
Measurement point
At measure point B shown in the following figure, the RNC receives a RADIO BEARER SETUP
COMPLETE message from the UE and sends an RAB ASSIGNMENT RESPONSE message
to the CN. The UEs eventually succeed in setting up the RABs over the DCH due to a small Ec/
N0 even through conditions for setting up the RABs over the E-DCH has been met. In such a
case, this counter in the serving cell is increased by one.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RABEstabE2D.COVER.
Succ
WRFD-01061208
HSUPA DCCC

1053
BSC6900 UMTS
Mean Number of Access Classes Restricted Due to Cell Resource Congestion

Counters
Counter ID
Counter Name
Counter Description
73441241
VS.AC.CongCtl.MeanAcBa
rNum.AboveR6.PS
Mean Number of PS Access

Classes Restricted Due to
Cell Resource Congestion
(R6 or Later)
73441243
rNum.UnderR5
Mean Number of Access

(R5 or Earlier)
73441244
rNum.AboveR6.CS
Mean Number of CS Access

(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. The preceding counters comply with section "5.3.1.2 Access Control" in 3GPP TS
25.304 (v10.0.0).
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
Issue 03 (2015-06-30)

1054
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
rNum.AboveR6.PS
WRFD-140213
Intelligent Access Class

Control
rNum.UnderR5
WRFD-140213

Control
rNum.AboveR6.CS
WRFD-140213

Control
Duration of Access Class Restriction Triggered by Cell Resource Congestion

Counters
Counter ID
Counter Name
Counter Description
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. This counter complies with section "5.3.1.2 Access Control" in 3GPP TS 25.304
(v10.0.0).
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
Issue 03 (2015-06-30)

1055
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AC.CongCtl.Time
WRFD-140213

Control
Number of UEs Involved in Inter-Frequency Load-based Handovers in a CLB Cell

Counters
Counter ID
Counter Name
Counter Description
73441246
VS.LCC.CLB.CS.InterFreq
Number of CS UEs Involved

in Inter-Frequency Loadbased Handovers in a CS
CLB Cell
73441247
VS.LCC.CLB.PS.InterFreq
Number of PS UEs Involved

in Inter-Frequency Loadbased 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
Issue 03 (2015-06-30)

1056
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.LCC.CLB.CS.InterFreq
WRFD-140217
Balancing Based on
Configurable Load
Threshold
VS.LCC.CLB.PS.InterFreq
WRFD-140217
Balancing Based on
Configurable Load
Threshold
Number of Attempts to Configure CQI Feedback Period for a Cell

Counters
Counter ID
Counter Name
Counter Description
73424472
VS.HSDPA.DynCfgAtt.Lon
gCQI
Configure a Long CQI
Feedback Period for a Cell
73424473
VS.HSDPA.DynCfgAtt.Sho
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
Issue 03 (2015-06-30)

1057
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.DynCfgAtt.Lon
gCQI
WRFD-140215
Dynamic Configuration of
HSDPA CQI Feedback
Period
VS.HSDPA.DynCfgAtt.Sho
rtCQI
WRFD-140215
Dynamic Configuration of
HSDPA CQI Feedback
Period
Number of Attempts to Configure BLER in a Congested or Normal Cell

Counters
Counter ID
Counter Name
Counter Description
73424474
VS.ULBler.BE.Large
Configure BLER in a
Congested Cell
73424475
VS.ULBler.BE.Small
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
Issue 03 (2015-06-30)

1058
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.ULBler.BE.Large
WRFD-140216
Load-based Uplink Target

BLER Configuration
VS.ULBler.BE.Small
WRFD-140216
Load-based Uplink Target

BLER Configuration
Number of CS RABs Abnormally Released for Special UEs for Cell

Counters
Counter ID
Counter Name
Counter Description
73424760
VS.RAB.SpecialUser.Abnor
mRel.CS
Number of CS RABs
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. This
counter complies with section "8.3 RAB Release Request" in 3GPP TS 25.413 (v10.3.0).
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.
Issue 03 (2015-06-30)

1059
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.
Issue 03 (2015-06-30)

1060
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.
Issue 03 (2015-06-30)

1061
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.SpecialUser.Abnor
mRel.CS
WRFD-140205
Voice Service Experience

Improvement for Weak
Reception UEs

1062
BSC6900 UMTS
Number of CS RABs Normally Released for Special UEs for Cell

Counters
Counter ID
Counter Name
Counter Description
73424761
VS.RAB.SpecialUser.Norm
Rel.CS
Number of CS RABs
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. This counter complies with section "8.3 RAB Release Request" in 3GPP TS 25.413
(v10.3.0).
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.
Issue 03 (2015-06-30)

1063
BSC6900 UMTS
If the IU RELEASE COMMAND message indicates the reason is "User Inactivity","Normal
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.SpecialUser.Norm
Rel.CS
WRFD-140205
Voice Service Experience

Improvement for Weak
Reception UEs

1064
BSC6900 UMTS
Uplink Actual Cell Load

Counters
Counter ID
Counter Name
Counter Description
73441505
VS.MeanULActualPowerLoad
Mean Uplink Actual Cell

Load
73424787
Max Uplink Actual Cell

Load
73424788
Min Uplink Actual Cell Load
Description
These counters measure the average, maximum, and minimum uplink actual cell load in a cell.
These counters indicate the percentage of the uplink actual cell load in the received total
wideband power (RTWP).
Measurement point
The measurement is triggered at point A shown in figure 1 when the RNC receives a COMMON
MEASUREMENT REPORT message containing the RTWP for a cell. In this case, this counter
is calculated based on the measurement results contained in the message and the measurement
period is 5s. At the end of the measurement period, the RNC measures the maximum and
minimum uplink actual cell load and divides the accumulated value by the number of samples
to obtain the average uplink actual cell load.
Formula
None
Issue 03 (2015-06-30)

1065
BSC6900 UMTS
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.MeanULActualPowerLoad
WRFD-020102
Load Measurement
WRFD-020102
Load Measurement
WRFD-020102
Load Measurement
Number of CELL_FACH to URA_PCH State Transition Attempts

Counters
Counter ID
Counter Name
Counter Description
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
TS 25.331 (v9.3.0).
Measurement point
The measurement is triggered at point A as shown in the following figure. When sending a
RADIO BEARER RECONFIGURATION message, instructing the UE to transit from the
CELL_FACH state to the URA_PCH state, the RNC measures the counter in the best cell where
the UE camps on before the state transition.
Issue 03 (2015-06-30)

1066
BSC6900 UMTS
Figure 1-456 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.
Issue 03 (2015-06-30)

1067
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.Att.F2U
WRFD-021101
Dynamic Channel
(DCCC)
Number of Successful CELL_FACH to URA_PCH State Transitions

Counters
Counter ID
Counter Name
Counter Description
73424897
VS.DCCC.Succ.F2U
CELL_FACH to URA_PCH
State Transitions for Cell
Description
URA_PCH in the cell. This counter complies with section "8.2 Radio Bearer control procedures"
in 3GPP TS 25.331 (v9.3.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. When receiving a
RADIO BEARER RECONFIGURATION COMPLETE message, indicating that the UE has
transited from the CELL_FACH state to the URA_PCH state, the RNC measures the counter in
the best cell where the UE camps on before the state transition.
Issue 03 (2015-06-30)

1068
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.
Issue 03 (2015-06-30)

1069
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.Succ.F2U
WRFD-021101
Dynamic Channel
(DCCC)
Number of CELL_DCH to URA_PCH State Transition Attempts

Counters
Counter ID
Counter Name
Counter Description
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
TS 25.331 (v9.3.0).
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.
Issue 03 (2015-06-30)

1070
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.Att.D2U
WRFD-021101
Dynamic Channel
(DCCC)

1071
BSC6900 UMTS
Number of Successful CELL_DCH to URA_PCH State Transitions

Counters
Counter ID
Counter Name
Counter Description
73424899
VS.DCCC.Succ.D2U
CELL_DCH to URA_PCH
Description
This counter provides the number of successful state transitions from CELL_DCH to URA_PCH
TS 25.331 (v9.3.0).
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.
Issue 03 (2015-06-30)

1072
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DCCC.Succ.D2U
WRFD-021101
Dynamic Channel
(DCCC)
Times That Small Target Retransmission Numbers Are Adjusted for HSUPA 2 ms
or 10 ms TTI UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73424900
VS.HSUPA.SmallRsnAdj.T
TI2ms
Times That Small Target

Retransmission Numbers
Are Adjusted for HSUPA 2
ms TTI UEs for Cell
73424901
TI10ms
Times That Small Target

Retransmission Numbers
Are Adjusted for HSUPA 10
ms TTI UEs for Cell
Description
This counter is used to evaluate the activation rate of the Adaptive Adjustment of HSUPA Small
Target Retransmissions feature.
Issue 03 (2015-06-30)
Counter Name
Description
VS.HSUPA.SmallRsnAdj.TTI2ms
This counter measures the number of times

that small target retransmission numbers are
adjusted for HSUPA 2 ms TTI UEs in a cell.

1073
BSC6900 UMTS
Counter Name
Description
VS.HSUPA.SmallRsnAdj.TTI10ms

that small target retransmission numbers are
adjusted for HSUPA 10 ms TTI UEs in a cell.
Measurement point
The measurement is triggered in the HSUPA serving cell when the RNC adjusts the small target
retransmission numbers if HSUPA 2 ms or 10 ms TTI UEs meet the conditions for small target
retransmission number adjustments. That is, the throughput of HSUPA 2 ms or 10ms TTI UEs
meets the event 4A/4B threshold and the cell uplink load is limited.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
TI2ms
WRFD-140222
Adaptive Adjustment of
HSUPA Small Target
Retransmissions
TI10ms
WRFD-140222
Adaptive Adjustment of
HSUPA Small Target
Retransmissions
Number of Pilot PO Optimization Attempts in the DL DPCH for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425824
VS.DL.DPCH.OptiPilotPOAttNum
Number of Pilot PO
Optimization Attempts in the
DL DPCH for Cell

1074
BSC6900 UMTS
Description
This counter measures the number of the attempts to optimize the pilot PO in the best cell in a
measurement period. This counter complies with section "5.2 Downlink power" in 3GPP TS
25.214 (v10.2.0).
Measurement point
This counter measures the number of the attempts to optimize the pilot PO in the downlink
DPCH in the best cell in a measurement period. The optimization attempt occurs during physical
parameter change procedures at the physical layer, including radio bearer (RB) setups, RB
reconfigurations, cell updates, and hard handovers.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DL.DPCH.OptiPilotPOAttNum
WRFD-150230
DPCH Pilot Power

Adjustment
Number of Normal Pilot PO Attempts in the DL DPCH for Cell

Counters
Counter ID
Counter Name
Counter Description
73425825
VS.DL.DPCH.NormalPilotPOAttNum
Number of Normal Pilot PO

Attempts in the DL DPCH
for Cell
Description
This counter measures the number of the attempts to configure a normal pilot PO in the best cell
in a measurement period. This counter complies with section "5.2 Downlink power" in 3GPP
TS 25.214 (v10.2.0).
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
Issue 03 (2015-06-30)

1075
BSC6900 UMTS
handover H2D fallback, hard handover with relocation, inter-RAT incoming handover, P2D
state transition, DCCC F2D state transition, F2D state transition due to service establishment,
DRD procedure for HSPA retry, or RAB establishment for DRD to other cells.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DL.DPCH.NormalPilotPOAttNum
WRFD-150230
DPCH Pilot Power

Adjustment
Total number of times a micro cell transits to the total desensitization state
Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

1076
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.TotalDesense.Num
WRFD-150201
Macro & Micro Co-carrier

Uplink Interference Control
WRFD-15020103
Micro Cell Dynamic Rx

Sensitivity Control
Total time periods of the total desensitization state for a micro cell
Counters
Counter ID
Counter Name
Counter Description
73426176
VS.TotalDesense.Time
Total time periods of the total

desensitization state for a
micro cell
Description
This counter indicates the total time periods of the total desensitization state for a micro cell.
Measurement point
This counter starts to measure the time period of the total desensitization state when the micro
cell transits from partial desensitization to total desensitization and stops the measurement when
the micro cell transits from total desensitization to partial desensitization. This counter is equal
to the sum of the time periods of the total desensitization state.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.TotalDesense.Time
WRFD-150201

WRFD-15020103

Sensitivity Control
Issue 03 (2015-06-30)

1077
BSC6900 UMTS
Average desensitization intensity for a micro cell

Counters
Counter ID
Counter Name
Counter Description
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
changed. In addition, the RNC reports the current desensitization intensity to the platform every
minute. The average desensitization intensity is equal to the sum of reported desensitization
intensity values divided by the number of reports in a measurement period.
Formula
None
Unit
dBm
Related Features
Counter Name
Feature ID
Feature Name
VS.MeanDesensePwr
WRFD-150201

WRFD-15020103

Sensitivity Control
Issue 03 (2015-06-30)

1078
BSC6900 UMTS
Average and Maximum Uplink Credit Usage of LCG for Cell

Counters
Counter ID
Counter Name
Counter Description
73426283
VS.LCG.ULCreditUsage.M
ean
Average Uplink Credit

Usage of LCG for Cell
73426284
ax
Maximum Uplink Credit

Usage of LCG for Cell
Description
These counters provide the average and maximum uplink credit usage of the local cell group
(LCG) where the cell belongs. Note: The CE-related counters measured at the RNC have
different values from these measured at the NodeB. CE-related counters measured at the RNC
are mainly used to estimate the access capability and are measured based on the number of CEs
consumed in the access strategy. CE-related counters measured at the NodeB are mainly used
to calculate the CEs that are actually used. In addition, the sampling period of the CE-related
counters measured at the RNC is 5s, which is different from that of the CE-related counters
measured at the NodeB (2 ms). Therefore, the counter values are not comparable, extremely
when the NodeB dynamic CE function is enabled.
Measurement point
The system samples the uplink credit usage of the logical cell group (LCG) every 5s. At the end
of the measurement period, the maximum uplink credit usage of the LCG for the cell is obtained.
The average uplink credit usage of the LCG for the cell equals to accumulated value of the credit
usage at the sampling points divided by the number of sampling times.Counters related to CE
resource measurement by the RNC are different from those related to CE resource measurement
by the NodeB in that: The counters related to CE resource measurement by the RNC estimate
the access capabilities based on the CE resources consumed by the admission policy, while the
counters related to CE resource measurement by the NodeB estimate the actual CE usage and
indicate the CE resources available for connected UEs. When the dynamic CE function is enabled
on the NodeB, the values of the counters related to CE resource measurement by the RNC are
quite different from the counters related to CE resource measurement by the NodeB.The RNC
measures the related counters every 5 s, while the NodeB measures the related counters every
2 ms TTI.
Formula
None
Unit
per mill
Issue 03 (2015-06-30)

1079
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
ean
WRFD-140212
CE Overbooking
ax
WRFD-140212
CE Overbooking
Number of State Transition Attempts from CELL_PCH or URA_PCH to

CELL_FACH and then to CELL_DCH Due to Data Transmission Requirements for
Cell
Counters
Counter ID
Counter Name
Counter Description
73426333
VS.DCCC.Att.F2D.AfterP2
F
Number of State Transition

Attempts from CELL_PCH
or URA_PCH to
CELL_FACH and then to
CELL_DCH Due to Data
Transmission Requirements
for Cell
Description
This counter measures the number of state transition attempts from CELL_PCH or URA_PCH
or CELL_FACH and then to CELL_DCH due to data transmission requirements in a cell. This
counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS 25.331
(v9.3.0).
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" and
meanwhile without the Establishment cause IE 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.
Issue 03 (2015-06-30)

1080
BSC6900 UMTS
Figure 1-462 RB Reconfiguration procedure after cell update procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.Att.F2D.AfterP2
F
WRFD-021101
Dynamic Channel
(DCCC)

1081
BSC6900 UMTS
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
Counter ID
Counter Name
Counter Description
73426334
VS.DCCC.Succ.F2D.AfterP
2F

Transitions from
CELL_PCH or URA_PCH to
CELL_DCH Due to Data
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. This
(v9.3.0).
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" and
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.
Issue 03 (2015-06-30)

1082
BSC6900 UMTS
Figure 1-463 RB Reconfiguration procedure after cell update procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.Succ.F2D.AfterP
2F
WRFD-021101
Dynamic Channel
(DCCC)

1083
BSC6900 UMTS
Average Number of Acknowledged PRACH Preambles and Granted Common EDCH Resources During Random Access in a Cell
Counters
Counter ID
Counter Name
Counter Description
73443289
VS.Random.Access.ACKN
um.Mean
Average Number of
Acknowledged PRACH
Preambles and Granted
Common E-DCH Resources
During Random Access in a
Cell
Description
This counter provides the average number of acknowledged PRACH preambles and granted
common E-DCH resources during random access in a cell. This counter complies with section
"8.2.9 Common Measurement Reporting" in 3GPP TS 25.433(v10.2.0).
Measurement point
Upon receiving a COMMON MEASUREMENT REPORT message, the RNC reads the number
of acknowledged PRACH preambles and granted common E-DCH resources during random
access in a specific cell. Then, the RNC sums the number of acknowledged PRACH preambles
and granted common E-DCH resources during random access in the cell within a measurement
period. After this, the RNC divides the sum by the number of COMMON MEASUREMENT
REPORT messages received within the measurement period. The measurement is triggered at
point A as shown in the following figure.
Formula
None
Issue 03 (2015-06-30)

1084
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Random.Access.ACKN
um.Mean
WRFD-151201
Adaptive RACH
Number of Call Reestablishment Attempts for CS Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73426799
VS.AttRlReEst.CS
Number of Call
Reestablishment Attempts
for CS Services for Cell
Description
This counter measures the number of call reestablishment attempts for CS services in the best
cell. This counter complies with section "8.3.18 Radio Link Activation" in 3GPP TS 25.413
(v10.3.0) and "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331 (v9.3.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When a call reestablishment is
triggered for CS services because of an exception, for example, signaling RLC reset, the RNC
sends a RADIO LINK ACTIVATION COMMAND message to the NodeB or sends a RADIO
LINK DELETION REQUEST message to the DRNC. This counter is measured in the best cell
where the call reestablishment is triggered.
Issue 03 (2015-06-30)

1085
BSC6900 UMTS
Figure 1-465 Call reestablishment procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRlReEst.CS
WRFD-140103
Call Reestablishment
Number of Successful Call Reestablishments for CS Services for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426800
VS.SuccRlReEst.CS
Number of Successful Call

Reestablishments for CS
Services for Cell

1086
BSC6900 UMTS
Description
This counter measures the number of successful call reestablishments for CS services in the best
Measurement point
During a CS call reestablishment procedure, the RNC determines that the CS call reestablishment
procedure is successful upon receiving the response message from a UE after sending a CELL
UPDATE CONFIRM message to the UE. The measurement is triggered after the RNC receives
a response message, for example, TRANSPORT CHANNEL RECONFIGURATION
COMPLETE, from the UE, as shown by point B in the following figure. This counter is measured
in the best cell of the UE where the call reestablishment is triggered.
The UE responds with one of the following messages after receiving a CELL UPDATE
CONFIRM message:
UTRAN MOBILITY INFORMATION CONFIRM
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RELEASE COMPLETE.
Issue 03 (2015-06-30)

1087
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccRlReEst.CS
WRFD-140103
Number of Call Reestablishment Attempts for PS Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73426804
VS.AttRlReEst.PS
Number of Call
for PS Services for Cell
Description
This counter measures the number of call reestablishment attempts for PS services in the best
Measurement point
The measurement is triggered at point A, as shown in the figure. When a call reestablishment is
triggered for PS services because of an exception, for example, signaling RLC reset, the RNC
sends a RADIO LINK ACTIVATION COMMAND message to the NodeB or sends a RADIO
LINK DELETION REQUEST message to the DRNC. This counter is measured in the best cell
where the call reestablishment is triggered.
Issue 03 (2015-06-30)

1088
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRlReEst.PS
WRFD-140103
Number of Successful Call Reestablishments for PS Services for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426805
VS.SuccRlReEst.PS
Number of Successful Call

Reestablishments for PS
Services for Cell

1089
BSC6900 UMTS
Description
This counter measures the number of successful call reestablishments for PS services in the best
Measurement point
During a PS call reestablishment procedure, the RNC determines that the PS call reestablishment
procedure is successful upon receiving the response message from a UE after sending a CELL
UPDATE CONFIRM message to the UE. The measurement is triggered after the RNC receives
a response message, for example, TRANSPORT CHANNEL RECONFIGURATION
COMPLETE, from the UE, as shown by point B in the following figure. This counter is measured
in the best cell of the UE where the call reestablishment is triggered.
The UE responds with one of the following messages after receiving a CELL UPDATE
CONFIRM message:
Issue 03 (2015-06-30)

1090
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccRlReEst.PS
WRFD-140103
Number of P2D State Transition Attempts for Cell (on Different Channels)
Counters
Counter ID
Counter Name
Counter Description
73428168
VS.PSR99.P2D.Att
Number of P2D State

Transition Attempts for Cell
(UL and DL Carried on
DCH)
73428170
VS.HSDPA.P2H.Att
Number of P2D State

(DL Carried on HSDPA)
73428172
VS.HSUPA.P2E.Att
Number of P2D State

(UL Carried on HSUPA)
Description
These counters measure the number of state transition attempts from CELL_PCH or URA_PCH
to CELL_DCH (on different channels) in a cell. The preceding counters comply with section
"8.3.1 Cell and URA update procedures" in 3GPP TS 25.331 (v9.3.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.PSR99.P2D.Att
This counter measures the state transition

attempts from CELL_PCH or URA_PCH to
CELL_DCH in a cell. This counter applies
only to UEs whose uplink and downlink are
carried on the DCH after the state transition.

1091
BSC6900 UMTS
Counter Name
Description
VS.HSDPA.P2H.Att

only to UEs whose downlink is carried on
HSDPA channels after the state transition.
VS.HSUPA.P2E.Att

only to UEs whose uplink is carried on
HSUPA channels after the state transition.
Measurement point
The measurement is triggered at point B in the figure. When a UE transitions from the
CELL_PCH or URA_PCH state to the CELL_DCH state: - VS.PSR99.P2D.Att is measured in
the cell where the UE sends the CELL UPDATE message if the uplink and downlink are carried
on the DCH after the state transition. - VS.HSDPA.P2H.Att is measured in the cell where the
UE sends the CELL UPDATE message if the downlink is carried on HSDPA channels after the
state transition. - VS.HSUPA.P2E.Att is measured in the cell where the UE sends the CELL
UPDATE message if the uplink is carried on HSUPA channels after the state transition.
Figure 1-469 cell update procedure
Issue 03 (2015-06-30)

1092
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.PSR99.P2D.Att
WRFD-010202

URA-PCH, CELL-FACH)
VS.HSDPA.P2H.Att
WRFD-010202

URA-PCH, CELL-FACH)
VS.HSUPA.P2E.Att
WRFD-010202

URA-PCH, CELL-FACH)
Number of P2D State Transition Success for Cell (on Different Channels)
Counters
Counter ID
Counter Name
Counter Description
73428169
VS.PSR99.P2D.Succ
Number of P2D State

Transition Success for Cell
(UL and DL Carried on
DCH)
73428171
VS.HSDPA.P2H.Succ
Number of P2D State

(DL Carried on HSDPA)
73428173
VS.HSUPA.P2E.Succ
Number of P2D State

(UL Carried on HSUPA)
Description
These counters measure the number of state transition success from CELL_PCH or URA_PCH
to CELL_DCH (on different channels) in a cell. The preceding counters comply with section
Issue 03 (2015-06-30)

1093
BSC6900 UMTS
Counter Name
Description
VS.PSR99.P2D.Succ

success from CELL_PCH or URA_PCH to
only to UEs whose uplink and downlink are
carried on the DCH after the state transition.
VS.HSDPA.P2H.Succ

only to UEs whose downlink is carried on
HSDPA channels after the state transition.
VS.HSUPA.P2E.Succ

only to UEs whose uplink is carried on
HSUPA channels after the state transition.
Measurement point
The measurement is triggered at point B in the figure. When a UE transitions from the
CELL_PCH or URA_PCH state to the CELL_DCH state and success: - VS.PSR99.P2D.Succ
is measured in the cell where the UE sends the CELL UPDATE message if the uplink and
downlink are carried on the DCH after the state transition. - VS.HSDPA.P2H.Succ is measured
in the cell where the UE sends the CELL UPDATE message if the downlink is carried on HSDPA
channels after the state transition. - VS.HSUPA.P2E.Succ is measured in the cell where the UE
sends the CELL UPDATE message if the uplink is carried on HSUPA channels after the state
transition.
Issue 03 (2015-06-30)

1094
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PSR99.P2D.Succ
WRFD-010202

URA-PCH, CELL-FACH)
VS.HSDPA.P2H.Succ
WRFD-010202

URA-PCH, CELL-FACH)
VS.HSUPA.P2E.Succ
WRFD-010202

URA-PCH, CELL-FACH)

1095
BSC6900 UMTS
Number of Times That LCG Uplink Credit Usage for UE Admission Falls into a
Certain Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428328
Number of Times That LCG

Uplink Credit Usage for UE
Admission Is between 0 per
mill(Included) and 250 per
mill
73428329

Admission Is between 250
per mill(Included) and 500
per mill
73428330

per mill
73428331

per mill
73428332

per mill
73428333

per mill
73428334

per mill

1096
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428335

per mill
73428336

per mill
73428337

per mill
73428338

per mill
73428339

Admission Is Greater than or
Equal to 950 per mill
Description
These counters measure the number of times that the uplink credit usage for UE admission for
the local cell group (LCG) to which the current cell belongs falls in to different value ranges in
a measurement period. The percentage of a value range in a measurement period can be
calculated by dividing the measurement times in this value range by the total number of
measurement times. For example, Percentage of [0 per mille, 250 per mille ) =
VS.LCG.ULCreditUsage.0/(Sum of VsS.LCG.ULCreditUsage.0 through
VS.LCG.ULCreditUsage.11).
Measurement point
The RNC takes samples of LCG credit usage (measured in millesimal) in the uplink every 5
seconds in a measurement period. At the end of the measurement period, the RNC calculates
the distribution of uplink credit usage of the LCG to which the current cell belongs. Note: RNClevel CE-related counters have different usage from NodeB-level CE-related counters. RNClevel CE-related counters are mainly used to estimate the access capability and are measured
based on the number of CEs consumed by the access policy. NodeB-level CE-related counters
are mainly used to calculate the actual CE usage, which can directly reflect the CE resources
consumed by UEs in connected mode. These two types of counters differ greatly from each
Issue 03 (2015-06-30)

1097
BSC6900 UMTS
other, especially when the NodeB dynamic CE function is enabled. In addition, the measurement
period of RNC-level CE-related counters is 5 seconds, which is different from that of NodeBlevel CE-related counters (2 ms). Therefore, these two types of counters are not comparable.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
WRFD-020101
Admission Control
Number of HSPA Serving Cell Changes Triggered by Event 1A or 1C for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428444
1A1COptTrig
Number of HSPA Serving

Cell Changes Triggered by
Event 1A or 1C for Cell

1098
BSC6900 UMTS
Description
This counter measures the number of times that the RNC immediately initiates HSPA serving
cell changes after a soft handover triggered by the measurement report for event 1A or 1C in a
cell. This counter complies with section "8.4.1 Measurement control" in 3GPP TS 25.331
(v9.3.0).
Measurement point
When the switch for immediate HSPA serving cell change is set to on, the RNC adds a target
cell for soft handover after receiving a measurement report for event 1A or 1C. If both of the
target cell and the current cell meet the conditions for this switch, the RNC uses the target cell
as the new HSPA serving cell and measures the number of immediate HSPA serving cell changes
in the current cell.
Figure 1-471 Measurement reporting procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
1A1COptTrig
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061204
HSUPA Mobility
Management
Issue 03 (2015-06-30)

1099
BSC6900 UMTS
Number of HSPA Serving Cell Changes Triggered by Event 1D for Cell

Counters
Counter ID
Counter Name
Counter Description
73428445
1DOptTrig
Number of HSPA Serving

Cell Changes Triggered by
Event 1D for Cell
Description
This counter measures the number of times that the RNC initiates HSPA serving cell changes
after the RNC receives a measurement report mistakenly reported by a UE for event 1D,
indicating that there is a cell whose signal quality is better than the current cell. This counter
complies with section "8.4.1 Measurement control" in 3GPP TS 25.331 (v9.3.0).
Measurement point
When the switch for immediate HSPA serving cell change is set to on, the RNC adds a target
cell for soft handover after receiving a measurement report for event 1A or 1C. If both of the
target cell and the current cell meet the conditions for this switch, the RNC uses the target cell
as the new HSPA serving cell and measures the number of immediate HSPA serving cell changes
in the current cell.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1100
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
1DOptTrig
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061204
HSUPA Mobility
Management
Duration of Cell Unavailability due to NodeB Blocking

Counters
Counter ID
Counter Name
Counter Description
73428521
VS.Cell.UnavailTime.NodeBBLK
Duration of Cell
Unavailability due to NodeB
Blocking
Description
This counter measures the duration of cell unavailability due to NodeB blocking using the BLK
UNODEB command. If a cell and a NodeB are blocked at the same time due to operation and
maintenance (O&M), the duration of cell unavailability caused by O&M (VS.Cell.UnavailTime)
is not measured.
Measurement point
After a cell is set up, services in the cell will become unavailable if the BLK UNODEB command
is executed to block the NodeB to which the cell belongs. In this case, this cell is considered
unavailable and the RNC measures the duration of cell unavailability in a measurement period.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Cell.UnavailTime.NodeBBLK
WRFD-031000

1101
BSC6900 UMTS
Number of Times That Coverage-based UMTS-to-LTE Redirections or Handovers

Are Prohibited due to SPID Reasons
Counters
Counter ID
Counter Name
Counter Description
73428525
VS.U2LProhibited.SPID.Co
verage

Coverage-based UMTS-toLTE Redirections or
Handovers Are Prohibited
due to SPID Reasons
Description
This counter measures the number of times that coverage-based UMTS-to-LTE redirections or
handovers are prohibited due to SPID reasons. This counter complies with section "16.1.8
Subscriber Profile ID for RAT/Frequency Priority" in 3GPP TS 36.300 (v9.0.0).
Measurement point
The measurement is triggered at point A shown in Figure 1. When a coverage-based UMTS-toLTE handover is triggered for a UE, the RNC prohibits the handover if the SPID-based handover
indication (specified by SPIDBasedHandoverInd) is set to NO for the UE. In this case, this
counter is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

1102
BSC6900 UMTS
Figure 1-473 Prohibited Coverage-based U2L Handovers due to SPID Reasons
The measurement is triggered at point A shown in Figure 2. When a coverage-based UMTS-toLTE redirection is triggered for a UE, the RNC prohibits the redirection if the SPID-based
handover indication (specified by SPIDBasedHandoverInd) is set to NO for the UE. In this case,
this counter is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

1103
BSC6900 UMTS
Figure 1-474 Prohibited Coverage-based U2L Redirections due to SPID Reasons
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.U2LProhibited.SPID.Co
verage
WRFD-160270
SPID-Based Management on
Camping Strategies

1104
BSC6900 UMTS
Number of Times That UMTS-to-LTE Fast Returns or Quick Cell Reselections Are
Prohibited due to SPID Reasons
Counters
Counter ID
Counter Name
Counter Description
73428526
VS.FastU2LProhibited.SPI
D

UMTS-to-LTE Fast Returns
or Quick Cell Reselections
Are Prohibited due to SPID
Reasons
Description
This counter measures the number of times that UMTS-to-LTE fast returns or quick cell
reselections are prohibited due to SPID reasons. This counter complies with section "16.1.8
Measurement point
The measurement is triggered at point A shown in the following figure. When the CN sends the
RNC an IU RELEASE COMMAND message after a service release, this counter is measured
in the following two scenarios: 1. After services of a CSFB UE are released in the UMTS
network, CN send IU RELEASE COMMAND message,the RNC determines the frequencies
and frequency priority carried in the dedicated priority information based on the SPID of the
UE. If the priority of the UMTS frequency is higher than that of the LTE frequency, the RNC
prohibits the fast return function for the UE. In this case, this counter is measured in the best
cell that the UE camps on. 2. When a UE completes PS data transmission in the UMTS network,
CN send IU RELEASE COMMAND message,the RNC determines the frequencies and
frequency priority carried in the dedicated priority information based on the SPID of the UE. If
the priority of the UMTS frequency is higher than that of the LTE frequency, the RNC prohibits
the quick cell reselection function for the UE. In this case, this counter is measured in the best
cell that the UE camps on.
Issue 03 (2015-06-30)

1105
BSC6900 UMTS
Figure 1-475 Prohibited UMTS-to-LTE Fast Returns or Quick Cell Reselections due to SPID
Dedicated Priority
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.FastU2LProhibited.SPI
D
WRFD-160270
Camping Strategies

1106
BSC6900 UMTS
Total Number of Adjusted Uplink Equivalent Users for Cell

Counters
Counter ID
Counter Name
Counter Description
73444379
VS.RAC.AdjUlTotalEqUser
Num.Mean
Average Number of Adjusted

Uplink Equivalent Users for
Cell
73428534
Num.Max
Maximum Number of
Adjusted Uplink Equivalent
Users for Cell
73428535
Num.Min
Minimum Number of
Adjusted Uplink Equivalent
Users for Cell
Description
When the RTWP-based Dynamic UL Total Equivalent User Adjustment Switch is set to on, the
RNC dynamically adjusts the total number of uplink equivalent users in a cell. These counters
measure the average, maximum, and minimum numbers of adjusted uplink equivalent users in
a cell.
Measurement point
The RNC takes samples of the total number of adjusted equivalent users every 5 seconds in a
measurement period. At the end of the measurement period, the RNC obtains the average number
of adjusted uplink equivalent users by dividing the accumulated value by the number of sampling
times. The RNC obtains the maximum number of adjusted uplink equivalent users among all
the sampled values. The RNC obtains the minimum number of adjusted uplink equivalent users
among all the sampled values.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Num.Mean
WRFD-020101
Admission Control

1107
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
Num.Max
WRFD-020101
Admission Control
Num.Min
WRFD-020101
Admission Control
Number of Times that UMTS and LTE Are Configured as the Highest Frequency
Priority
Counters
Counter ID
Counter Name
Counter Description
73428628
VS.UMI.DedicatedPri.UMT
S.High
Number of Times that UMTS

Is Configured as the Highest
Frequency Priority
73428629
VS.UMI.DedicatedPri.LTE.
High
Number of Times that LTE Is

Configured as the Highest
Frequency Priority
Description
These counters provide the numbers of times that UMTS and LTE frequencies are configured
as the highest-priority frequencies in the SPID-based dedicated priority information in a cell.
The SPID-based dedicated priority information is carried in the UTRAN Mobility Information
messages sent to multimode UEs. The preceding counters comply with section "8.6.7.23
Dedicated Priority Information" in 3GPP TS 25.331 (v9.3.0).
Measurement point
The measurement is triggered at point A in figure. The VS.UMI.DedicatedPri.UMTS.High
counter is increased by one each time the RNC sends a UTRAN Mobility Information message
to a UE and the message contains the SPID-based dedicated priority information in which a
UMTS frequency is configured as the highest-priority frequency in a cell. The
VS.UMI.DedicatedPri.LTE.High counter is increased by one each time the RNC sends a
UTRAN Mobility Information message to a UE and the message contains the SPID-based
dedicated priority information in which an LTE frequency is configured as the highest-priority
frequency in a cell.
Issue 03 (2015-06-30)

1108
BSC6900 UMTS
Figure 1-476 Dedicated priorities procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.UMI.DedicatedPri.UMT
S.High
WRFD-160270
Camping Strategies
VS.UMI.DedicatedPri.LTE.
High
WRFD-160270
Camping Strategies
Maximum Number of Equivalent Users on All DCHs for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428638
VS.RAC.UL.EqvUserNum.
Max
Maximum Number of Uplink

Equivalent Users on All
DCHs for Cell
73428639
VS.RAC.DL.EqvUserNum.
Max
Maximum Number of
Downlink Equivalent Users
on All DCHs for Cell

1109
BSC6900 UMTS
Description
These counters measure the maximum number of uplink and downlink equivalent users in the
CELL_DCH state in a cell.
Measurement point
The RNC takes samples of the numbers of uplink and downlink users on all DCHs every 5
seconds in a measurement period. At the end of the measurement period, the RNC takes the
maximum and minimum uplink and downlink sampling numbers as the values for these counters.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.UL.EqvUserNum.
Max
WRFD-020101
Admission Control
VS.RAC.DL.EqvUserNum.
Max
WRFD-020101
Admission Control
Number of Preemptions for Platinum User

Counters
Counter ID
Counter Name
Counter Description
73428759
VS.RAC.Platinum.Preempt.
Cong
Number of Preemptions for

Platinum User
Description
This counter measures the number of times that preemption is performed by platinum users
during cell admission.
Measurement point
Platinum users will preempt resources of lower-priority users based on the configured service
priority if platinum users fail to apply for resources during procedures such as service setups,
service modification, and handovers. This counter is measured in cells where resource
application by platinum users failed.
Issue 03 (2015-06-30)

1110
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.Platinum.Preempt.
Cong
WRFD-010505
WRFD-150204
Platinum User Prioritizing
Number of Times That Service-based UMTS-to-LTE Redirections or Handovers

Are Prohibited due to SPID Reasons
Counters
Counter ID
Counter Name
Counter Description
73428797
VS.U2LProhibited.SPID.Ser
vice

Service-based UMTS-toLTE Redirections or
due to SPID Reasons
Description
This counter measures the number of times that UMTS-to-LTE fast returns or quick cell
reselections are prohibited due to SPID reasons. This counter complies with section "16.1.8
Measurement point
The measurement is triggered at point A shown in Figure 1. When a service-based UMTS-toLTE handover is triggered for a UE, the RNC prohibits the handover if the SPID-based handover
indication (specified by SPIDBasedHandoverInd) is set to NO for the UE. In this case, this
counter is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

1111
BSC6900 UMTS
Figure 1-477 Prohibited Service-based U2L Handovers due to SPID Reasons
The measurement is triggered at point A shown in Figure 2. When a service-based UMTS-toLTE redirection is triggered for a UE, the RNC prohibits the redirection if the SPID-based
handover indication (specified by SPIDBasedHandoverInd) is set to NO for the UE. In this case,
Issue 03 (2015-06-30)

1112
BSC6900 UMTS
Figure 1-478 Prohibited Service-based U2L Redirections due to SPID Reasons
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.U2LProhibited.SPID.Ser
vice
WRFD-160270
Camping Strategies

1113
BSC6900 UMTS
Number of Times That Load-based U2L Redirections or Handovers Are Prohibited

due to SPID Reasons
Counters
Counter ID
Counter Name
Counter Description
73428798
VS.U2LProhibited.SPID.Lo
ad
Number of Times That Loadbased U2L Redirections or

due to SPID Reasons
Description
This counter measures the number of times that load-based UMTS to LTE redirections or
handovers are prohibited due to SPID reasons. This counter complies with section "16.1.8
Measurement point
When the load-based UMTS to LTE redirection or handover algorithm selects a UE for LDR
actions, if the SPID-based handover indication (specified by SPIDBasedHandoverInd) is set to
NO for the UE, the UE cannot be redirected or handed over from the UMTS network to the LTE
network. In this case, this counter is measured in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.U2LProhibited.SPID.Lo
ad
WRFD-160270
Camping Strategies

1114
BSC6900 UMTS
Number of Failed State Transitions from CELL_PCH/URA_PCH to CELL_FACH

and then to CELL_DCH for Existing Data Transmission Requirements Due to
Counters
Counter ID
Counter Name
Counter Description
73428885
VS.DCCC.Fail.F2D.AfterP2
F.Cong
Number of Failed State

Transitions from
CELL_PCH/URA_PCH to
CELL_DCH for Existing
Data Transmission
Requirements Due to
Description
This counter measures the number of failed state transitions from CELL_PCH or URA_PCH to
CELL_FACH and then to CELL_DACH triggered by existing data transmission requirements
in resource congestion scenarios in a cell. This counter helps evaluate the congestion of resources
that are used to perform admission during the state transitions triggered by existing data
transmission requirements. This counter complies with section "8.3 RRC connection mobility
Measurement point
The measurement is triggered at point A in the following figure. When receiving a CELL
UPDATE message with the cause value "uplink data transmission" or "paging response" and
state, the RNC waits until the cell update is complete and switches the UE from the CELL_FACH
state to the CELL_DCH state. If the admission of the state transition fails due to resource
congestion, this counter is measured in the serving cell after the cell update.
Issue 03 (2015-06-30)

1115
BSC6900 UMTS
Figure 1-479 Admission failure for F2D state transition after P2F-triggered cell update
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DCCC.Fail.F2D.AfterP2
F.Cong
WRFD-020101
Admission Control
WRFD-010202

URA-PCH, CELL-FACH)

1116
BSC6900 UMTS
Number of Times That Downlink Rate Adjustment Is Triggered for AMR Services
for Cell (Triggered by Downlink Transmit Power)
Counters
Counter ID
Counter Name
Counter Description
73428886
VS.AMRNB.DL.RateUp.Tc
p

Downlink Rate Increase Is
Triggered for NB-AMR
Services for Cell (Triggered
by Downlink Transmit
Power)
73428887
VS.AMRNB.DL.RateDown.
Tcp

Downlink Rate Reduction Is
Power)
73428888
VS.AMRWB.DL.RateUp.T
cp

Downlink Rate Increase Is
Triggered for WB-AMR
Power)
73428889
VS.AMRWB.DL.RateDown
.Tcp

Downlink Rate Reduction Is
Power)
Description
These counters measure the number of times that the RNC triggers downlink rate increase or
reduction for NB-AMR or WB-AMR services using the link stability-based Adaptive MultiRate Control (AMRC) function (triggered by downlink transmit power) in a cell. The preceding
counters comply with section "6.5.3 Iu Rate Control procedure" in 3GPP TS 25.415 (v9.0.0).
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC triggers
the link stability-based AMRC function for downlink rate adjustment after receiving an IUB
TCP report from the NodeB. This counter is measured in the best cell of the UE based on the
service type (NB-AMR or WB-AMR) and rate adjustment type (rate increase or reduction).
Issue 03 (2015-06-30)

1117
BSC6900 UMTS
Figure 1-480 Downlink rate adjustment triggered for AMR services (triggered by downlink
transmit power)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AMRNB.DL.RateUp.Tc
p
WRFD-020701
AMR/WB-AMR Speech
Rates Control
VS.AMRNB.DL.RateDown.
Tcp
WRFD-020701
AMR/WB-AMR Speech
Rates Control
VS.AMRWB.DL.RateUp.T
cp
WRFD-020701
AMR/WB-AMR Speech
Rates Control
VS.AMRWB.DL.RateDown
.Tcp
WRFD-020701
AMR/WB-AMR Speech
Rates Control

1118
BSC6900 UMTS
Number of Times That Uplink Rate Adjustment Is Triggered for AMR Services for
Cell (Triggered by UE Transmit Power)
Counters
Counter ID
Counter Name
Counter Description
73428890
VS.AMRNB.UL.RateUp.Ue
TxPwr

Uplink Rate Increase Is
by UE Transmit Power)
73428891
VS.AMRNB.UL.RateDown.
UeTxPwr

Uplink Rate Reduction Is
73428892
VS.AMRWB.UL.RateUp.U
eTxPwr

73428893
VS.AMRWB.UL.RateDown
.UeTxPwr

Description
These counters measure the number of times that the RNC triggers the uplink rate increase or
reduction for NB-AMR or WB-AMR services using the link stability-based Adaptive MultiRate Control (AMRC) function (triggered by UE transmit power) in a cell. The preceding
counters comply with section "8.2.5 Transport format combination control" in 3GPP TS 25.331
(v9.3.0).
Measurement point
the link stability-based AMRC function for uplink rate adjustment after receiving an event 6X
report from a UE. This counter is measured in the best cell of the UE based on the service type
(NB-AMR or WB-AMR) and rate adjustment type (rate increase or reduction).
Issue 03 (2015-06-30)

1119
BSC6900 UMTS
Figure 1-481 Uplink rate adjustment triggered for AMR services (triggered by UE transmit
power)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AMRNB.UL.RateUp.Ue
TxPwr
WRFD-020701
AMR/WB-AMR Speech
Rates Control
UeTxPwr
WRFD-020701
AMR/WB-AMR Speech
Rates Control
VS.AMRWB.UL.RateUp.U
eTxPwr
WRFD-020701
AMR/WB-AMR Speech
Rates Control
.UeTxPwr
WRFD-020701
AMR/WB-AMR Speech
Rates Control

1120
BSC6900 UMTS
Number of Times That Uplink Rate Adjustment Is Triggered for AMR Services for
Cell (Based on TrFO)
Counters
Counter ID
Counter Name
Counter Description
73428894
VS.AMRNB.UL.RateUp.T
RFO

Services for Cell (Based on
TrFO)
73428895
TRFO

TrFO)
73428896
VS.AMRWB.UL.RateUp.T
RFO

TrFO)
73428897
.TRFO

TrFO)
Description
These counters measure the number of times that the RNC triggers uplink rate increase or
reduction for NB-AMR or WB-AMR services using the TrFO-based Adaptive Multi-Rate
Control (AMRC) function in a cell. The preceding counters comply with section "8.2.5 Transport
format combination control" in 3GPP TS 25.331 (v9.3.0).
Measurement point
the TrFO-based AMRC function for uplink rate adjustment after receiving an IUUP RATE
CONTROL message from the CN. This counter is measured in the best cell of the UE.
Issue 03 (2015-06-30)

1121
BSC6900 UMTS
Figure 1-482 Uplink rate adjustment triggered for AMR services (based on TrFO)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AMRNB.UL.RateUp.T
RFO
WRFD-020701
AMR/WB-AMR Speech
Rates Control
TRFO
WRFD-020701
AMR/WB-AMR Speech
Rates Control
VS.AMRWB.UL.RateUp.T
RFO
WRFD-020701
AMR/WB-AMR Speech
Rates Control
.TRFO
WRFD-020701
AMR/WB-AMR Speech
Rates Control

1122
BSC6900 UMTS
Number of Times That Rate Reduction Is Performed for WB-AMR Services due to
Counters
Counter ID
Counter Name
Counter Description
73428898
VS.LCC.LDR.AMRWBRateUL
Number of Times That Rate

Reduction Is Performed for
WB-AMR Services due to
Uplink Basic Congestion for
Cell
73428899
VS.LCC.LDR.AMRWBRateDL
Number of Times That Rate

Reduction Is Performed for
WB-AMR Services due to
Downlink Basic Congestion
for Cell
Description
When a cell is in basic congestion state, the RNC selects certain WB-AMR UEs to perform rate
reduction. These counters measure the number of times that uplink or downlink rate reductions
are performed for AMR services based on the uplink or downlink cell congestion state,
respectively. The preceding counters comply with section "6.5.3 Iu Rate Control procedure" in
3GPP TS 25.415 (v9.0.0).
Measurement point
When a cell is in basic congestion state, the RNC selects certain WB-AMR UEs to perform rate
reduction. In this case, this counter is measured in the cell to which the UE belongs based on
the uplink or downlink cell congestion state, respectively.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.AMRWBRateUL
WRFD-020701
AMR/WB-AMR Speech
Rates Control

1123
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.LCC.LDR.AMRWBRateDL
WRFD-020701
AMR/WB-AMR Speech
Rates Control
Number of Times the Air Interface Load Enters the Congested State for Cell
Counters
Counter ID
Counter Name
Counter Description
73428900
VS.AirLoad.Congestion.Nu
m
Number of Times the Air

Interface Load Enters the
Congested State for Cell
Description
This counter provides the number of times the air interface load enters the congested state in a
cell. The air interface load includes the downlink non-HSPA load, uplink received total wideband
power (RTWP) load, and DCH user number.
Measurement point
The RNC determines whether the air interface load enters the congested state based on the
downlink non-HSPA load, uplink RTWP load, and DCH user number. This counter is measured
on a per cell basis at the end of a measurement period.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AirLoad.Congestion.Nu
m
WRFD-020102
Load Measurement

1124
BSC6900 UMTS
Time During Which the Air Interface Load Is in the Congested State for Cell
Counters
Counter ID
Counter Name
Counter Description
73428901
VS.AirLoad.Congestion.Ti
me
Time During Which the Air

Interface Load Is in the
Congested State for Cell
Description
This counter provides the period of time during which the air interface load is in the congested
state in a cell. The air interface load includes the downlink non-HSPA load, uplink RTWP load,
and DCH user number.
Measurement point
At the end of a measurement period, the RNC accumulates the period of time during which the
air interface load of a cell is in the congested state.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.AirLoad.Congestion.Ti
me
WRFD-020102
Load Measurement
Duration During Which HSPA Common Channel Codes Are in the Non-Optimum
State for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444481
VS.Cell.HspaCommChCode
NotOptimum.Time
Duration During Which

HSPA Common Channel
Codes Are in the NonOptimum State for Cell

1125
BSC6900 UMTS
Description
This counter measures the duration during which HSPA common channel codes are in the nonoptimum state in a cell. HSPA common channel codes include HSSCCH codes, EAGCH codes,
and ERGCH codes. After the HSDPA or HSUPA feature is enabled when a cell has no R99
users, HSPA common channel codes allocated by the RNC are mapped to downlink R99 channel
codes whose SF is 16. These codes and an adjacent downlink R99 channel code whose SF is 16
form the theoretical optimum code range. The non-optimum state indicates that HSPA common
channel codes are not within the theoretical optimum code range.
Measurement point
The RNC takes samples of HSPA common channel code allocation every 5 second in a cell. At
the end of each measurement period, the RNC obtains the accumulated duration during which
the HSPA common channel codes are in the non-optimum state. After the HSDPA or HSUPA
feature is enabled when a cell has no R99 users, HSPA common channel codes allocated by the
RNC are mapped to downlink R99 channel codes whose SF is 16. These codes and an adjacent
downlink R99 channel code whose SF is 16 form the theoretical optimum code range. For cells
enabled with the HSDPA feature, when the allocated HSSCCH codes are not within the
theoretical optimum code range, the RNC increments this counter by one. For cells enabled with
the HSUPA feature, when the allocated EAGCH or ERGCH codes are not within the theoretical
optimum code range, the RNC increments this counter by one.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Cell.HspaCommChCode
NotOptimum.Time
WRFD-010612
HSUPA Introduction
Package

1126
BSC6900 UMTS
Number of Preemptions Performed During an RRC Connection Setup Procedure

for Cell
Counters
Counter ID
Counter Name
Counter Description
73429233
VS.RAC.RRCReq.Preempt.
Cong
Performed During an RRC
Connection Setup Procedure
for Cell
Description
This counter measures the number of times that preemption is performed during an RRC
connection setup procedure in a cell. The measurement of this counter complies with descriptions
in section 8.1.3 "RRC connection reestablishment" in 3GPP TS 25.331 (V9.3.0).
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving an RRC
CONNECTION REQUEST message from a UE, if resource application for the RRC connection
setup fails, the RNC triggers resource preemption and increments this counter by one in the cell
where the preemption is performed.
Figure 1-483 RRC connection setup procedure
Issue 03 (2015-06-30)

1127
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.RRCReq.Preempt.
Cong
WRFD-010505
Number of Preemptions Performed During an F2D Procedure for Cell

Counters
Counter ID
Counter Name
Counter Description
73429234
VS.RAC.F2D.Preempt.Con
g
Performed During an F2D
Procedure for Cell
Description
This counter measures the number of times that preemption is performed during a CELL_FACH
to CELL_DCH (F2D) state transition in a cell. The measurement of this counter complies with
descriptions in section 8.2.2 "Reconfiguration procedures" in 3GPP TS 25.331 (V9.3.0).
Measurement point
The measurement is triggered at point A shown in the following figure. During a CELL_FACH
to CELL_DCH state transition, if resource application for the F2D procedure fails, the RNC
triggers resource preemption and increments this counter by one in the cell where the preemption
is performed.
Issue 03 (2015-06-30)

1128
BSC6900 UMTS
Figure 1-484 F2D procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAC.F2D.Preempt.Con
g
WRFD-010505

1129
BSC6900 UMTS
Number of Preemptions Performed During a P2D Procedure for Cell

Counters
Counter ID
Counter Name
Counter Description
73429235
VS.RAC.P2D.Preempt.Con
g
Performed During a P2D
Procedure for Cell
Description
This counter measures the number of times that preemption is performed during a CELL_PCH/
URA_PCH to CELL_DCH (P2D) state transition in a cell. The measurement of this counter
complies with descriptions in section 8.3.1 "Cell and URA update procedures" in 3GPP TS
25.331 (V9.3.0).
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving a CELL
UPDATE message from a UE, the RNC attempts to transit the UE from the CELL_PCH/
URA_PCH state to the CELL_DCH state. If resource application for the P2D procedure fails,
the RNC triggers resource preemption and increments this counter by one in the cell where the
preemption is performed.
Issue 03 (2015-06-30)

1130
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.P2D.Preempt.Con
g
WRFD-010505
Mean Number of RABs Configured with the GBR Management Policy in Each DL
Throughput Range for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73446349
VS.RAB.Mean.GBR.DL.Th
roughput.0
Mean Number of RABs

Configured with the GBR
Management Policy in DL
Throughput Range 0 for Cell
73446350
roughput.1
Mean Number of RABs

73446351
roughput.2
Mean Number of RABs

73446352
roughput.3
Mean Number of RABs

73446353
roughput.4
Mean Number of RABs


1131
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73446354
roughput.5
Mean Number of RABs

73446355
roughput.6
Mean Number of RABs

Description
These counters provide the mean number of RABs that are configured with the GBR
management policy in each downlink throughput range in the best cell.
Measurement point
The system samples the number of RABs that are configured with the GBR management policy
in each downlink throughput range every 1s in a measurement period. At the end of the
measurement period, the system obtains the mean RABs that are configured with the GBR
management policy in each downlink throughput range by dividing the accumulated value by
the measurement period. There are seven downlink throughput ranges, which are listed as
follows: Downlink throughput range 0 (0, 256 kbit/s) Downlink throughput range 1 [256 kbit/
s, 512 kbit/s) Downlink throughput range 2 [512 kbit/s, 1 Mbit/s) Downlink throughput range 3
[1 Mbit/s, 2 Mbit/s) Downlink throughput range 4 [2 Mbit/s, 3 Mbit/s) Downlink throughput
range 5 [3 Mbit/s, 4 Mbit/s) Downlink throughput range 6 (greater than or equal to 4 Mbit/s)
The downlink throughput of an RAB is calculated as follows: The system samples the downlink
throughput of an RAB every 1s in a measurement period and obtains the accumulated downlink
throughput at the end of the measurement period. The system also calculates the total data
transmission time in the measurement period. At the end of the measurement period, the system
obtains the downlink throughput of the RAB by dividing the accumulated downlink throughput
by the total data transmission time. DSCP short for differentiated services code point. For details
about the DSCP, see RFC 791. The CN performs the service awareness function and uses the
DSCP value contained in IP headers to indicate the service types. The RAN performs mapping
and determines whether the service requires the GBR management policy based on the received
DSCP value.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1132
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
roughput.0
MRFD-101401
UL Unified Video Steering
roughput.1
MRFD-101401
roughput.2
MRFD-101401
roughput.3
MRFD-101401
roughput.4
MRFD-101401
roughput.5
MRFD-101401
roughput.6
MRFD-101401
Number of Throughput-based D2F State Transition Attempts Made by UEs with

Abnormally Low Throughput for Cell
Counters
Counter ID
Counter Name
Counter Description
73430283
VS.AbnormUE.BeThrup.D2
F.Att
Number of Throughputbased D2F State Transition

Attempts Made by UEs with
Abnormally Low
Throughput for Cell
Description
This counter measures the number of throughput-based CELL_DCH to CELL_FACH state
transition attempts made by UEs with abnormally low throughput in the best cell. This counter
complies with 3GPP TS 25.331(v11.1.0). For details, see section "B.3 UTRA RRC Connected
Mode States and Transitions" in this TS. Note: UEs with abnormally low throughput are defined
as follows: Within the duration specified by the state transition timer, if both the uplink and
downlink throughputs of a UE measured at the RLC layer are lower than the throughput
measurement-based low throughput threshold and data exists in the UE's cache, this UE is
considered as a UE with abnormally low throughput. For details about the state transition timer
and low throughput threshold, see State Transition Feature Parameter Description.
Issue 03 (2015-06-30)

1133
BSC6900 UMTS
Measurement point
As shown at point A in the following figure, the RNC triggers throughput-based state transition
from CELL_DCH to CELL_FACH for a UE with abnormally low throughput. After the RNC
sends the UE a RADIO BEARER RECONFIGURATION message, this counter is measured in
the best cell to which the UE belongs before the state transition is complete.
Figure 1-486 Throughput-based D2F state transitions by UEs with abnormally low throughput
in a cell
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
F.Att
WRFD-010202

URA-PCH, CELL-FACH)

1134
BSC6900 UMTS
Number of Successful Throughput-based D2F State Transitions by UEs with

Abnormally Low Throughput for Cell
Counters
Counter ID
Counter Name
Counter Description
73430284
F.Succ
Throughput-based D2F State
Transitions by UEs with
Abnormally Low
Throughput for Cell
Description
This counter measures the number of successful throughput-based state transitions by UEs with
abnormally low throughput in a cell. This counter complies with 3GPP TS 25.331(v11.1.0). For
details, see section "B.3 UTRA RRC Connected Mode States and Transitions" in this TS. Note:
UEs with abnormally low throughput are defined as follows: Within the duration specified by
the state transition timer, if both the uplink and downlink throughputs of a UE measured at the
RLC layer are lower than the throughput measurement-based low throughput threshold and data
exists in the UE's cache, this UE is considered as a UE with abnormally low throughput. For
details about the state transition timer and low throughput threshold, see State Transition Feature
Parameter Description.
Measurement point
As shown at point B in the following figure, the RNC triggers throughput-based state transition
from CELL_DCH to CELL_FACH for a UE with abnormally low throughput and then sends
the UE a RADIO BEARER RECONFIGURATION message. After the RNC receives from the
UE a RADIO BEARER RECONFIGURATION COMPLETE message, this counter is measured
in the best cell to which the UE belongs before the state transition is complete.
Issue 03 (2015-06-30)

1135
BSC6900 UMTS
Figure 1-487 Throughput-based D2F state transitions by UEs with abnormally low throughput
in a cell
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
F.Succ
WRFD-010202

URA-PCH, CELL-FACH)
Number of P2D State Transition Attempts based on Load and Ec/N0 for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430321
VS.LoadAndEcNoBased.P2
D.Att
Number of P2D State

Transition Attempts based on
Load and Ec/N0 for Cell

1136
BSC6900 UMTS
Description
This counter provides the number of P2D state transition attempts based on cell load and Ec/N0
in a cell. P2D state transitions refer to the state transitions from the CELL_PCH and URA_PCH
states to the CELL_DCH state. This counter complies with 3GPP TS 25.331 (V9.3.0). For details
about this counter, see section 8.2 "Radio Bearer control procedures" in this TS.
Measurement point
The measurement is triggered at point B in figure 1. This counter is measured in the cell on
which the UE camps before the state transition when the following conditions are met: The RNC
receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging
response" from a UE in the CELL_PCH or URA_PCH state and returns a CELL UPDATE
CONFIRM message to the UE;The cell update procedure is triggered based on the cell load and
Ec/N0 to switch the UE to the CELL_DCH state. The load and Ec/N0-based P2D state transition
is triggered when the following conditions are both met: (1)The actual uplink service load of the
cell is lower than or equal to Min. UL Actual Load State for P2D and the current downlink load
of the cell is lower than or equal to Min. DL Non-HSPA Power Load State for P2D. Note: The
load states specified by Min. UL Actual Load State for P2D and Min. DL Non-HSPA Power
Load State for P2D parameters are listed as follows: light state, normal state, loaded state, heavy
state, and overload state. (2)The Ec/N0 is greater than or equal to the Ec/N0 threshold for P2D
state transitions.
Formula
None
Issue 03 (2015-06-30)

1137
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
D.Att
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-021101
Dynamic Channel
(DCCC)
Number of Successful P2D State Transitions based on Load and Ec/N0 for Cell
Counters
Counter ID
Counter Name
Counter Description
73430322
D.Succ
Number of Successful P2D

State Transitions based on
Load and Ec/N0 for Cell
Description
This counter provides the number of successful P2D state transitions based on cell load and Ec/
N0 in a cell. P2D state transitions refer to the state transitions from the CELL_PCH and
URA_PCH states to the CELL_DCH state. This counter complies with 3GPP TS 25.331
(V9.3.0). For details about this counter, see section 8.2 "Radio Bearer control procedures" in
this TS.
Measurement point
The measurement is triggered at point C in figure 1. This counter is measured in the cell on
which the UE camps before the state transition when the following conditions are met:The RNC
receives a CELL UPDATE message with the cause value "uplink data transmission" or "paging
response" from a UE in the CELL_PCH or URA_PCH state and later the RNC receives a RADIO
BEARER RECONFIGURATION COMPLETE message from the UE;The cell update
procedure is triggered based on the cell load and Ec/N0 to switch the UE to the CELL_DCH
state. The load and Ec/N0-based P2D state transition is triggered when the following conditions
are both met: (1)The actual uplink service load of the cell is lower than or equal to Min. UL
Actual Load State for P2D and the current downlink load of the cell is lower than or equal to
Min. DL Non-HSPA Power Load State for P2D. Note: The load states specified by Min. UL
Actual Load State for P2D and Min. DL Non-HSPA Power Load State for P2D parameters are
listed as follows: light state, normal state, loaded state, heavy state, and overload state. (2)The
Ec/N0 is greater than or equal to the Ec/N0 threshold for P2D state transitions.
Issue 03 (2015-06-30)

1138
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
D.Succ
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-021101
Dynamic Channel
(DCCC)
Issue 03 (2015-06-30)

1139
BSC6900 UMTS
Number of CELL_DCH-to-CELL_FACH Reconfiguration and Reestablishment

Attempts for Cell
Counters
Counter ID
Counter Name
Counter Description
73430361
VS.RlReEst.D2F.Att
Number of CELL_DCH-toCELL_FACH
Reconfiguration and
for Cell
Description
This counter provides the number of CELL_DCH-to-CELL_FACH reconfiguration and
reestablishment attempts in the best cell. A CELL_DCH-to-CELL_FACH reconfiguration and
reestablishment procedure is triggered when the following conditions are met: (1) All the radio
links (RLs) for a UE are out-of-synchronization or the TRB for a UE is reset. (2) A CELL_DCHto-CELL_FACH state transition is triggered to reestablish the UE's connection. This counter
complies with 3GPP TS 25.331 (V11.7.0). For details, see section 8.2.2 "Reconfiguration
Measurement point
The measurement is triggered at point A in the following figure. When the requirements of the
CELL_DCH-to-CELL_FACH reconfiguration and reestablishment procedure are met, this
counter is measured in the best cell for the UE before this procedure. This is done if the UE
performs a CELL_DCH-to-CELL_FACH state transition after receiving a RADIO BEARER
RECONFIGURATION message from the RNC. For details about the reconfiguration and
reestablishment procedure, see Call Reestablishment Feature Parameter Description.
Figure 1-490 translating
Issue 03 (2015-06-30)

1140
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RlReEst.D2F.Att
WRFD-021101
Dynamic Channel
(DCCC)
Number of Successful CELL_DCH-to-CELL_FACH Reconfiguration and

Reestablishment Attempts for Cell
Counters
Counter ID
Counter Name
Counter Description
73430362
VS.RlReEst.D2F.Succ
Reconfiguration and
for Cell
Description
This counter provides the number of successful CELL_DCH-to-CELL_FACH reconfiguration
and reestablishment attempts in the best cell. A CELL_DCH-to-CELL_FACH reconfiguration
and reestablishment procedure is triggered when the following conditions are met: (1) All the
radio links (RLs) for a UE are out-of-synchronization or the TRB for a UE is reset. (2) A
CELL_DCH-to-CELL_FACH state transition is triggered to reestablish the UE's connection.
This counter complies with 3GPP TS 25.331 (V11.7.0). For details, see section 8.2.2
"Reconfiguration procedures" in this TS.
Measurement point
The measurement is triggered at point B in the following figure. When the RNC receives a
RADIO BEARER RECONFIGURATION COMPLETE message from a UE during a
CELL_DCH-to-CELL_FACH reconfiguration and reestablishment procedure, this counter is
Issue 03 (2015-06-30)

1141
BSC6900 UMTS
measured in the best cell for the UE before this procedure. For details about the reconfiguration
and reestablishment procedure, see Call Reestablishment Feature Parameter Description.
Figure 1-491 translating
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RlReEst.D2F.Succ
WRFD-021101
Dynamic Channel
(DCCC)
1.12.3 BLER Measurement <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.
Issue 03 (2015-06-30)

1142
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199797
VS.ULBler.AMR
UL BLER of AMR
Services for Cell
Earlier than
BSC6900
V900R011
67184402
VS.ULBler.AMR.E
rrTB
Number of TBs with

UL CRCI Error for
AMR Services for
Cell
Earlier than
BSC6900
V900R011
67184403
VS.ULBler.AMR.S
ample
Number of BLER
Samplings for AMR
Services for Cell
Earlier than
BSC6900
V900R011
73394082
VS.ULBler.CS64
UL BLER of CS 64
Kbit/s
Conversational
Services on DCH for
Cell
BSC6900
V900R012
73394083
VS.ULBler.CS64.E
rrTB
Number of TBs with

UL CRCI Error for
CS 64 Kbit/s
Conversational
Services for Cell
BSC6900
V900R012
73394084
VS.ULBler.CS64.S
ample
Number of BLER
Samplings for CS 64
Kbit/s
Conversational
Services for Cell
BSC6900
V900R012
67199806
VS.ULBler.PS.BE.
DCH.8
UL BLER of PS 8
Kbit/s BE Services
on DCH for Cell
Earlier than
BSC6900
V900R011
67184420
VS.ULBler.PS.BE.
DCH.8.ErrTB
Number of TBs with

UL CRCI Error for
PS 8 Kbit/s BE
Services for Cell
Earlier than
BSC6900
V900R011
67184421
VS.ULBler.PS.BE.
DCH.8.Sample
Sampling Times of
BLER for PS 8 Kbit/
s BE Services for
Cell
Earlier than
BSC6900
V900R011
67199807
VS.ULBler.PS.BE.
DCH.16
UL BLER of PS 16
Kbit/s BE Services
on DCH for Cell
Earlier than
BSC6900
V900R011

1143
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67184422
VS.ULBler.PS.BE.
DCH.16.ErrTB
Number of TBs with

UL CRCI Error for
PS 16 Kbit/s BE
Services for Cell
Earlier than
BSC6900
V900R011
67184423
VS.ULBler.PS.BE.
DCH.16.Sample
Sampling Times of
BLER for PS 16
Kbit/s BE Services
for Cell
Earlier than
BSC6900
V900R011
67199808
VS.ULBler.PS.BE.
DCH.32
UL BLER of PS 32
Kbit/s BE Services
on DCH for Cell
Earlier than
BSC6900
V900R011
67184424
VS.ULBler.PS.BE.
DCH.32.ErrTB
Number of TBs with

UL CRCI Error for
PS 32 Kbit/s BE
Services for Cell
Earlier than
BSC6900
V900R011
67184425
VS.ULBler.PS.BE.
DCH.32.Sample
Sampling Times of
BLER for PS 32
Kbit/s BE Services
for Cell
Earlier than
BSC6900
V900R011
67199809
VS.ULBler.PS.BE.
DCH.64
UL BLER of PS 64
Kbit/s BE Services
on DCH for Cell
Earlier than
BSC6900
V900R011
67184426
VS.ULBler.PS.BE.
DCH.64.ErrTB
Number of TBs with

UL CRCI Error for
PS 64 Kbit/s BE
Services for Cell
Earlier than
BSC6900
V900R011
67184427
VS.ULBler.PS.BE.
DCH.64.Sample
Sampling Times of
BLER for PS 64
Kbit/s BE Services
for Cell
Earlier than
BSC6900
V900R011
67199810
VS.ULBler.PS.BE.
DCH.128
UL BLER of PS 128
Kbit/s BE Services
on DCH for Cell
Earlier than
BSC6900
V900R011
67184428
VS.ULBler.PS.BE.
DCH.128.ErrTB
Number of TBs with

UL CRCI Error for
PS 128 Kbit/s BE
Services for Cell
Earlier than
BSC6900
V900R011
67184429
VS.ULBler.PS.BE.
DCH.128.Sample
Sampling Times of
BLER for PS 128
Kbit/s BE Services
for Cell
Earlier than
BSC6900
V900R011

1144
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199811
VS.ULBler.PS.BE.
DCH.144
UL BLER of PS 144
Kbit/s BE Services
on DCH for Cell
Earlier than
BSC6900
V900R011
67184430
VS.ULBler.PS.BE.
DCH.144.ErrTB
Number of TBs with

UL CRCI Error for
PS 144 Kbit/s BE
Services for Cell
Earlier than
BSC6900
V900R011
67184431
VS.ULBler.PS.BE.
DCH.144.Sample
Sampling Times of
BLER for PS 144
Kbit/s BE Services
for Cell
Earlier than
BSC6900
V900R011
67199812
VS.ULBler.PS.BE.
DCH.256
UL BLER of PS 256
Kbit/s BE Services
on DCH for Cell
Earlier than
BSC6900
V900R011
67184432
VS.ULBler.PS.BE.
DCH.256.ErrTB
Number of TBs with

UL CRCI Error for
PS 256 Kbit/s BE
Services for Cell
Earlier than
BSC6900
V900R011
67184433
VS.ULBler.PS.BE.
DCH.256.Sample
Sampling Times of
BLER for PS 256
Kbit/s BE Services
for Cell
Earlier than
BSC6900
V900R011
67199813
VS.ULBler.PS.BE.
DCH.384
UL BLER of PS 384
Kbit/s BE Services
on DCH for Cell
Earlier than
BSC6900
V900R011
67184434
VS.ULBler.PS.BE.
DCH.384.ErrTB
Number of TBs with

UL CRCI Error for
PS 384 Kbit/s BE
Services for Cell
Earlier than
BSC6900
V900R011
67184435
VS.ULBler.PS.BE.
DCH.384.Sample
Sampling Times of
BLER for PS 384
Kbit/s BE Services
for Cell
Earlier than
BSC6900
V900R011
67202429
VS.ULBLer.Out.A
MR
Rate of Duration that

UL BLER of AMR
Services Exceeds
Target Value for Cell
Earlier than
BSC6900
V900R011

1145
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394085
VS.ULBler.Out.CS
64

UL BLER of CS 64
Kbit/s
Conversational
Services on DCH
Exceeds Target
Value for Cell
BSC6900
V900R012
67202439
VS.ULBler.Out.PS.
BE.DCH.8

UL BLER of PS 8
Kbit/s BE Services
on DCH Exceeds
Earlier than
BSC6900
V900R011
67202440
VS.ULBler.Out.PS.
BE.DCH.16

UL BLER of PS 16
Kbit/s BE Services
on DCH Exceeds
Earlier than
BSC6900
V900R011
67202441
VS.ULBler.Out.PS.
BE.DCH.32

UL BLER of PS 32
Kbit/s BE Services
on DCH Exceeds
Earlier than
BSC6900
V900R011
67202442
VS.ULBler.Out.PS.
BE.DCH.64

UL BLER of PS 64
Kbit/s BE Services
on DCH Exceeds
Earlier than
BSC6900
V900R011
67202443
VS.ULBler.Out.PS.
BE.DCH.128

UL BLER of PS 128
Kbit/s BE Services
on DCH Exceeds
Earlier than
BSC6900
V900R011
67202444
VS.ULBler.Out.PS.
BE.DCH.144

UL BLER of PS 144
Kbit/s BE Services
on DCH Exceeds
Earlier than
BSC6900
V900R011
67202445
VS.ULBler.Out.PS.
BE.DCH.256

UL BLER of PS 256
Kbit/s BE Services
on DCH Exceeds
Earlier than
BSC6900
V900R011

1146
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202446
VS.ULBler.Out.PS.
BE.DCH.384

UL BLER of PS 384
Kbit/s BE Services
on DCH Exceeds
Earlier than
BSC6900
V900R011
67202447
VS.ULBler.PS.BE.
RACH
UL BLER of PS 8
Kbit/s BE Service on
RACH for Cell
Earlier than
BSC6900
V900R011
67189898
VS.ULBler.PS.BE.
RACH.ErrTB
Number of Error
Blocks of PS 8 kbit/s
BE Services on
RACH for Cell
BSC6900
V900R012
67189899
VS.ULBler.PS.BE.
RACH.Sample
Number of PS 8 kbit/
s BE Service
Samplings on RACH
for Cell
BSC6900
V900R012
67204479
VS.Voice.VQI.Goo
d.TimeRate

AMR Speech
Quality is GOOD for
Cell
Earlier than
BSC6900
V900R011
67204480
VS.Voice.VQI.Acce
pt.TimeRate

AMR Speech
Quality is ACCEPT
for Cell
Earlier than
BSC6900
V900R011
67204481
VS.Voice.VQI.Bad.
TimeRate

AMR Speech
Quality is BAD for
Cell
Earlier than
BSC6900
V900R011
73410495
VS.ULBler.PS.Con
v
UL BLER of PS
Conversational
Services on DCH for
Cell
BSC6900
V900R012
73394040
VS.ULBler.PS.Con
v.ErrTB
Number of TBs with

UL CRCI Error for
PS Conversational
Services for Cell
BSC6900
V900R012
73394041
VS.ULBler.PS.Con
v.Sample
Sampling Times of
BLER for PS
Conversational
Services for Cell
BSC6900
V900R012

1147
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73410496
VS.ULBler.PS.Str
UL BLER of PS
Streaming Services
on DCH for Cell
BSC6900
V900R012
73394042
VS.ULBler.PS.Str.
ErrTB
Number of TBs with

UL CRCI Error for
PS Streaming
Services for Cell
BSC6900
V900R012
73394043
VS.ULBler.PS.Str.
Sample
Sampling Times of
BLER for PS
Streaming Services
for Cell
BSC6900
V900R012
73410497
VS.ULBler.Out.PS.
Conv

UL BLER of PS
Conversational
Services on DCH
Exceeds Target
Value for Cell
BSC6900
V900R012
73410498
VS.ULBler.Out.PS.
Str

UL BLER of PS
Streaming Services
on DCH Exceeds
BSC6900
V900R012
73441535
VS.Voice.VQI.Poor
.TimeRate

AMR Speech
Quality is POOR for
Cell
BSC6900
V900R014
73441536
VS.Voice.VQI.Exce
llent.TimeRate

AMR Speech
Quality is
EXCELLENT for
Cell
BSC6900
V900R014
73442310
VS.Voice.VQI.Aver
age
Average VQI for

AMR Services
BSC6900
V900R015C00
73444480
VS.ULBler.AMRW
B
UL BLER of AMRWB Services for Cell
BSC6900
V900R016C00
73428905
VS.ULBler.AMRW
B.ErrTB
Number of TBs with

UL CRCI Error for
AMR-WB Services
for Cell
BSC6900
V900R016C00

1148
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428906
VS.ULBler.AMRW
B.Sample
Number of BLER
Samplings for AMRWB Services for Cell
BSC6900
V900R016C00
73430781
VS.ULBler.DEU.A
MRNB.ErrTB
Number of TBs That

Fail UL CRC After
DEU Processing for
AMR-NB Services
on the DCH for Cell
BSC6900
V900R017C10
73430782
VS.ULBler.DEU.A
MRWB.ErrTB
Number of TBs That

Fail UL CRC After
DEU Processing for
AMR-WB Services
on the DCH for Cell
BSC6900
V900R017C10
None
Percentage of Duration When UL BLER on DCH Exceeds Target Value for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202429
VS.ULBLer.Out.AMR
Rate of Duration that UL

BLER of AMR Services
Exceeds Target Value for
Cell
73394085
VS.ULBler.Out.CS64

BLER of CS 64 Kbit/s
DCH Exceeds Target Value
for Cell
67202439
VS.ULBler.Out.PS.BE.DC
H.8

BLER of PS 8 Kbit/s BE
Services on DCH Exceeds
67202440
H.16


1149
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67202441
H.32

67202442
H.64

67202443
H.128

67202444
H.144

67202445
H.256

67202446
H.384

73410497
VS.ULBler.Out.PS.Conv

BLER of PS Conversational
73410498
VS.ULBler.Out.PS.Str

BLER of PS Streaming
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189862
VS.ULBler.Out.AMR.OutTime
Duration that UL BLER of

AMR Speech Services
Reaches Target Value for
Cell

1150
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189870
VS.ULBler.Out.CSRT.
64.OutTime

CS 64 kbit/s Real-Time
Services Reaches Target
Value for Cell
67189890
VS.ULBler.Out.PSNrt.DCH
.128.OutTime

PS 128 kbit/s Non-RealTime Services on DCH
Cell
67189892
.144.OutTime

Cell
67189884
.16.OutTime

PS 16 kbit/s Non-Real-Time
Value for Cell
67189894
.256.OutTime

Cell
67189886
.32.OutTime

Services on DCH Reaches
67189896
.384.OutTime

Cell
67189888
.64.OutTime

Services on DCH Reaches
67189882
.8.OutTime

Value for Cell

1151
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394044
VS.ULBler.PS.Conv.OutTime

PS Conversational Services
Cell
73394045
VS.ULBler.PS.Str.OutTime

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.
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]
Issue 03 (2015-06-30)

1152
BSC6900 UMTS
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ULBLer.Out.AMR
WRFD-020503
VS.ULBler.Out.CS64
WRFD-020503
H.8
WRFD-020503
H.16
WRFD-020503
H.32
WRFD-020503
H.64
WRFD-020503
H.128
WRFD-020503
H.144
WRFD-020503
H.256
WRFD-020503
H.384
WRFD-020503
VS.ULBler.Out.PS.Conv
WRFD-020503
VS.ULBler.Out.PS.Str
WRFD-020503

1153
BSC6900 UMTS
UL BLER of Services on RACH or DCH for Cell

Counters
Counter ID
Counter Name
Counter Description
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
Services on DCH for Cell
67199807
67199808
67199809
67199810
VS.ULBler.PS.BE.DCH.
128
UL BLER of PS 128 Kbit/s

BE Services on DCH for Cell
67199811
144

67199812
256

67199813
384

73410495
VS.ULBler.PS.Conv
UL BLER of PS
DCH for Cell
73410496
VS.ULBler.PS.Str
UL BLER of PS Streaming
73444480
VS.ULBler.AMRWB
UL BLER of AMR-WB
Services for Cell
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/
Issue 03 (2015-06-30)

1154
BSC6900 UMTS
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, the AMR-WB service, CS 64 kbit/s conversational service, PS
conversational service, PS streaming service, and PS BE service.
Formula
VS.ULBler.PS.BE.RACH = [VS.ULBler.PS.BE.RACH.ErrTB]/
([VS.ULBler.PS.BE.RACH.Sample]*{5})
VS.ULBler.AMR = [VS.ULBler.AMR.ErrTB]/([VS.ULBler.AMR.Sample]*{5})
VS.ULBler.CS64 = [VS.ULBler.CS64.ErrTB]/([VS.ULBler.CS64.Sample]*{5})
VS.ULBler.PS.BE.DCH.8 = [VS.ULBler.PS.BE.DCH.8.ErrTB]/([VS.ULBler.PS.BE.DCH.
8.Sample]*{5})
VS.ULBler.PS.BE.DCH.16 = [VS.ULBler.PS.BE.DCH.16.ErrTB]/
([VS.ULBler.PS.BE.DCH.16.Sample]*{5})
VS.ULBler.PS.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})
VS.ULBler.AMRWB = [VS.ULBler.AMRWB.ErrTB]/([VS.ULBler.AMRWB.Sample]*
{5})
Unit
%
Issue 03 (2015-06-30)

1155
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.ULBler.PS.BE.RACH
WRFD-020503
VS.ULBler.AMR
WRFD-020503
VS.ULBler.CS64
WRFD-020503
WRFD-020503
WRFD-020503
WRFD-020503
WRFD-020503
128
WRFD-020503
144
WRFD-020503
256
WRFD-020503
384
WRFD-020503
VS.ULBler.PS.Conv
WRFD-020503
VS.ULBler.PS.Str
WRFD-020503
VS.ULBler.AMRWB
WRFD-010613

Rate Wide Band)
Number of TBs with UL CRCI Errors for Services on RACH or DCH for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189898
VS.ULBler.PS.BE.RACH.E
rrTB
Number of Error Blocks of

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

1156
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73394083
VS.ULBler.CS64.ErrTB

CRCI Error for CS 64 Kbit/s
Cell
67184420
8.ErrTB

CRCI Error for PS 8 Kbit/s
BE Services for Cell
67184422
16.ErrTB

67184424
32.ErrTB

67184426
64.ErrTB

67184428
128.ErrTB

CRCI Error for PS 128 Kbit/
s BE Services for Cell
67184430
144.ErrTB

67184432
256.ErrTB

67184434
384.ErrTB

73394040
VS.ULBler.PS.Conv.ErrTB

CRCI Error for PS
Cell
73394042
VS.ULBler.PS.Str.ErrTB

CRCI Error for PS Streaming
Services for Cell
73428905
VS.ULBler.AMRWB.ErrTB

CRCI Error for AMR-WB
Services for Cell

1157
BSC6900 UMTS
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, the AMR-WB 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. The
VS.ULBler.AMRWB.ErrTB counter applies only to the AMR-WB service. Counters
VS.ULBler.AMR.ErrTB, VS.ULBler.AMRWB.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
These counters are measured based on the CRCI, as shown by point A in figure 1.
Figure 1-492 Counter measurement
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ULBler.PS.BE.RACH.E
rrTB
WRFD-020503
VS.ULBler.AMR.ErrTB
WRFD-020503
VS.ULBler.CS64.ErrTB
WRFD-020503
8.ErrTB
WRFD-020503
16.ErrTB
WRFD-020503

1158
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
32.ErrTB
WRFD-020503
64.ErrTB
WRFD-020503
128.ErrTB
WRFD-020503
144.ErrTB
WRFD-020503
256.ErrTB
WRFD-020503
384.ErrTB
WRFD-020503
VS.ULBler.PS.Conv.ErrTB
WRFD-020503
VS.ULBler.PS.Str.ErrTB
WRFD-020503
VS.ULBler.AMRWB.ErrTB
WRFD-010613

Rate Wide Band)
Number of UL BLER Samplings for Services on the RACH or DCH for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189899
VS.ULBler.PS.BE.RACH.S
ample
Number of PS 8 kbit/s BE
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

for CS 64 Kbit/s
Cell
67184421
8.Sample
Sampling Times of BLER for

PS 8 Kbit/s BE Services for
Cell
67184423
16.Sample

Cell

1159
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67184425
32.Sample

Cell
67184427
64.Sample

Cell
67184429
128.Sample

PS 128 Kbit/s BE Services
for Cell
67184431
144.Sample

for Cell
67184433
256.Sample

for Cell
67184435
384.Sample

for Cell
73394041
VS.ULBler.PS.Conv.Sample

PS Conversational Services
for Cell
73394043
VS.ULBler.PS.Str.Sample

PS Streaming Services for
Cell
73428906
VS.ULBler.AMRWB.Sample

for AMR-WB 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, the AMR-WB 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. The VS.ULBler.AMRWB.Sample counter applies only to the
AMR-WB service. Counters VS.ULBler.AMR.Sample, VS.ULBler.AMRWB.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
Issue 03 (2015-06-30)

1160
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ULBler.PS.BE.RACH.S
ample
WRFD-020503
VS.ULBler.AMR.Sample
WRFD-020503
VS.ULBler.CS64.Sample
WRFD-020503
8.Sample
WRFD-020503
16.Sample
WRFD-020503
32.Sample
WRFD-020503
64.Sample
WRFD-020503
128.Sample
WRFD-020503
144.Sample
WRFD-020503
256.Sample
WRFD-020503
384.Sample
WRFD-020503
VS.ULBler.PS.Conv.Sample
WRFD-020503
VS.ULBler.PS.Str.Sample
WRFD-020503
VS.ULBler.AMRWB.Sample
WRFD-010613

Rate Wide Band)

1161
BSC6900 UMTS
Percentage of Duration for AMR Voice Quality Being at A Level to Total Call
Duration for Cell
Counters
Counter ID
Counter Name
Counter Description
73441536
VS.Voice.VQI.Excellent.Ti
meRate
Rate of Duration that AMR

Speech Quality is
EXCELLENT for Cell
67204479
VS.Voice.VQI.Good.TimeRate

Speech Quality is GOOD for
Cell
67204480
VS.Voice.VQI.Accept.Time
Rate

Speech Quality is ACCEPT
for Cell
67204481
VS.Voice.VQI.Bad.TimeRate

Speech Quality is BAD for
Cell
73441535
VS.Voice.VQI.Poor.TimeRate

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 default mapping between the measured VQI, actual VQI, and QoS
quality levels is as follows:
[500, 400) = [5, 4) = Excellent
[400, 300) = [4, 3) = Good
[300, 200) = [3, 2) = Accept
[200, 100) = [2, 1) = Poor
[100, 0) = [1, 0) = Bad
The thresholds can be set by running the SET USQICOUNT command.
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.
Issue 03 (2015-06-30)

1162
BSC6900 UMTS
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.Voice.VQI.Excellent.Ti
meRate
WRFD-010501
VS.Voice.VQI.Good.TimeRate
WRFD-010501
VS.Voice.VQI.Accept.Time
Rate
WRFD-010501
VS.Voice.VQI.Bad.TimeRate
WRFD-010501
VS.Voice.VQI.Poor.TimeRate
WRFD-010501
Counter ID
Counter Name
Counter Description
73442310
VS.Voice.VQI.Average
Average VQI for AMR

Services
Average VQI for AMR Services

Counters
Description
This counter provides the average uplink VQI for narrowband and broadband AMR services in
the best cell. The measured VQI ranges from 0 to 500. The actual VQI equals the measured VQI
divided by 100 and ranges from 0 to 5.
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.
Issue 03 (2015-06-30)

1163
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Voice.VQI.Average
WRFD-010501
Number of TBs That Fail UL CRC After DEU Processing for AMR-NB Services on
the DCH for Cell
Counters
Counter ID
Counter Name
Counter Description
73430781
VS.ULBler.DEU.AMRNB.
ErrTB
Number of TBs That Fail UL

CRC After DEU Processing
for AMR-NB Services on the
DCH for Cell
Description
This counter provides the number of TBs that fail the UL cyclic redundancy check indicator
(CRCI) after AMR-NB services on the DCH in the best cell are processed by the DEU.
Measurement point
When AMR-NB services are carried on the DCH and the number of AMR-NB TBs received in
the uplink reaches a specified sampling window (500 TBs), this counter is measured in the best
cell.
When the DEU board is not configured, this counter is measured based on the CRCI, as shown
by point A in figure 1.
Figure 1-493 Counter measurement when the DEU board is not configured
Issue 03 (2015-06-30)

1164
BSC6900 UMTS
When the DEU board is configured, this counter is measured based on the CRCI, as shown by
point A in figure 2.
Figure 1-494 Counter measurement when the DEU board is configured
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ULBler.DEU.AMRNB.
ErrTB
WRFD-170201
WRFD-171201

Coverage
Number of TBs That Fail UL CRC After DEU Processing for AMR-WB Services on
the DCH for Cell
Counters
Counter ID
Counter Name
Counter Description
73430782
VS.ULBler.DEU.AMRWB.
ErrTB
Number of TBs That Fail UL

CRC After DEU Processing
for AMR-WB Services on
the DCH for Cell
Description
This counter provides the number of TBs that fail the UL cyclic redundancy check indicator
(CRCI) after AMR-WB services on the DCH in the best cell are processed by the DEU.
Issue 03 (2015-06-30)

1165
BSC6900 UMTS
Measurement point
When AMR-WB services are carried on the DCH and the number of AMR-WB TBs received
in the uplink reaches a specified sampling window (500 TBs), this counter is measured in the
best cell.
When the DEU board is not configured, this counter is measured based on the CRCI, as shown
by point A in figure 1.
Figure 1-495 Counter measurement when the DEU board is not configured
When the DEU board is configured, this counter is measured based on the CRCI, as shown by
point A in figure 2.
Figure 1-496 Counter measurement when the DEU board is configured
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ULBler.DEU.AMRWB.
ErrTB
WRFD-170201
WRFD-171201

Coverage
1.12.4 BOOST Measurement <per Cell>(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
Issue 03 (2015-06-30)

1166
BSC6900 UMTS
BOOST traffic. This function subset is effective only when the UMTS-UMTS Dual Terminal
Downlink BOOST feature is enabled.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424977
VS.BOOST.UU.An
chor.DL.R99.Bytes
Number of R99
Downlink Bytes of
UU BOOST Anchor
for Cell
BSC6900
V900R014
73441547
VS.BOOST.UU.An
chor.DL.R99.Mean
Throughput
Mean Throughput of
R99 Downlink of UU
BOOST Anchor for
Cell
BSC6900
V900R014
73424979
VS.BOOST.UU.An
chor.DL.HSDPA.B
ytes
Number of HSDPA
Downlink Bytes of
UU BOOST Anchor
for Cell
BSC6900
V900R014
73441548
VS.BOOST.UU.An
chor.DL.HSDPA.M
eanThroughput
Mean Throughput of
HSDPA Downlink of
UU BOOST Anchor
for Cell
BSC6900
V900R014
73424981
VS.BOOST.UU.An
chor.UL.R99.Bytes
Number of R99
Uplink Bytes of UU
BOOST Anchor for
Cell
BSC6900
V900R014
73441549
VS.BOOST.UU.An
chor.UL.R99.Mean
Throughput
Mean Throughput of
R99 Uplink of UU
BOOST Anchor for
Cell
BSC6900
V900R014
73424983
VS.BOOST.UU.An
chor.UL.HSUPA.B
ytes
Number of HSUPA
Uplink Bytes of UU
BOOST Anchor for
Cell
BSC6900
V900R014
73441550
VS.BOOST.UU.An
chor.UL.HSUPA.M
eanThroughput
Mean Throughput of
HSUPA Uplink of
UU BOOST Anchor
for Cell
BSC6900
V900R014
73424985
VS.BOOST.UU.Br
anch.DL.R99.Bytes
Number of R99
Downlink Bytes of
UU BOOST Branch
for Cell
BSC6900
V900R014

1167
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441551
VS.BOOST.UU.Br
anch.DL.R99.Mean
Throughput
Mean Throughput of
R99 Downlink of UU
BOOST Branch for
Cell
BSC6900
V900R014
73424987
VS.BOOST.UU.Br
anch.DL.HSDPA.B
ytes
Number of HSDPA
Downlink Bytes of
UU BOOST Branch
for Cell
BSC6900
V900R014
73441552
VS.BOOST.UU.Br
anch.DL.HSDPA.
MeanThroughput
Mean Throughput of
HSDPA Downlink of
UU BOOST Branch
for Cell
BSC6900
V900R014
73424989
VS.BOOST.UU.Br
anch.UL.R99.Bytes
Number of R99
Uplink Bytes of UU
BOOST Branch for
Cell
BSC6900
V900R014
73441553
VS.BOOST.UU.Br
anch.UL.R99.Mean
Throughput
Mean Throughput of
R99 Uplink of UU
BOOST Branch for
Cell
BSC6900
V900R014
73424991
VS.BOOST.UU.Br
anch.UL.HSUPA.B
ytes
Number of HSUPA
Uplink Bytes of UU
BOOST Branch for
Cell
BSC6900
V900R014
73441554
VS.BOOST.UU.Br
anch.UL.HSUPA.
MeanThroughput
Mean Throughput of
HSUPA Uplink of
UU BOOST Branch
for Cell
BSC6900
V900R014
73424993
VS.BOOST.UU.BP
LCapRprtInd
Number of UU
BOOST BPL
Capability Indication
Messages Received
for Cell
BSC6900
V900R014
73424994
VS.BOOST.UU.BP
LCapRsp.Succ
Number of
Successful
Responses to UU
BOOST BPL
Messages
Transmitted for Cell
BSC6900
V900R014

1168
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73424995
VS.BOOST.UU.BP
LInfoRprtInd
Number of UU
BOOST BPL User
Information
Indication Messages
Received for Cell
BSC6900
V900R014
73424996
VS.BOOST.UU.BP
LInfoRsp.Succ
Number of
Successful
Responses to UU
BOOST BPL User
Information
Indication Messages
BSC6900
V900R014
73424997
VS.BOOST.UU.BP
LRel
Number of UU
BOOST BPL
Release Messages
BSC6900
V900R014
73424998
VS.BOOST.UU.Su
ccEstab
Number of
Successful UU
BOOST Setups for
Cell
BSC6900
V900R014
73424999
VS.BOOST.UU.An
chor.NormRel
Number of Normal
UU BOOST Anchor
Releases for Cell
BSC6900
V900R014
73425000
VS.BOOST.UU.Br
anch.NormRel
Number of Normal
UU BOOST Branch
Releases for Cell
BSC6900
V900R014
73441555
VS.BOOST.UU.An
chorUEs.Mean
Average Number of
UU BOOST Anchor
UEs for Cell
BSC6900
V900R014
73441556
VS.BOOST.UU.Br
anchUEs.Mean
Average Number of
UU BOOST Branch
UEs for Cell
BSC6900
V900R014
None
Issue 03 (2015-06-30)

1169
BSC6900 UMTS
Number of R99 Downlink Bytes of UU BOOST Anchor for Cell

Counters
Counter ID
Counter Name
Counter Description
73424977
VS.BOOST.UU.Anchor.DL
.R99.Bytes
Number of R99 Downlink

Bytes of UU BOOST Anchor
for Cell
Description
This counter provides the total RLC traffic volume transmitted by PS services of UU BOOST
anchor UEs on downlink R99 channels in cells in the active set. RLC headers and retransmitted
data are not included.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including
the DCH and FACH) and there is downlink data transmission, the RNC measures the number
of all bytes (data of all service types) transmitted on the downlink RLC layer of cells in the active
set. RLC headers and retransmitted data are not included.
Formula
None
Unit
byte
Related Features
None
Mean Throughput of R99 Downlink of UU BOOST Anchor for Cell

Counters
Counter ID
Counter Name
Counter Description
73441547
.R99.MeanThroughput
Mean Throughput of R99

Downlink of UU BOOST
Anchor for Cell
specific formulas.
Issue 03 (2015-06-30)

1170
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73424978
.R99.Time
Duration of R99 Downlink

Sending Data of UU BOOST
Anchor for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST anchor UEs
transmitted on downlink R99 channels of cells in the active set.
Measurement point
When downlink PS RABs of UU BOOST anchor UEs are carried over R99 channels (including
the DCH and FACH) and there is downlink data transmission, the RNC measures the total actual
data transmission time and number of all transmitted bytes of cells in the active set. At the end
of a measurement period, the RNC measures this item by dividing the number of all transmitted
bytes by the total actual data transmission time. In soft handover scenarios, the RNC measures
this item of each cell in the active set separately.
Formula
VS.BOOST.UU.Anchor.DL.R99.MeanThroughput =
[VS.BOOST.UU.Anchor.DL.R99.Bytes]*{8}/[VS.BOOST.UU.Anchor.DL.R99.Time]
Unit
kbit/s
Related Features
None
Number of HSDPA Downlink Bytes of UU BOOST Anchor for Cell

Counters
Counter ID
Counter Name
Counter Description
73424979
.HSDPA.Bytes
Number of HSDPA
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.
Issue 03 (2015-06-30)

1171
BSC6900 UMTS
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
Mean Throughput of HSDPA Downlink of UU BOOST Anchor for Cell

Counters
Counter ID
Counter Name
Counter Description
73441548
.HSDPA.MeanThroughput
Mean Throughput of HSDPA

Anchor for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73424980
.HSDPA.Time
Duration of HSDPA
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
Issue 03 (2015-06-30)

1172
BSC6900 UMTS
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
Number of R99 Uplink Bytes of UU BOOST Anchor for Cell

Counters
Counter ID
Counter Name
Counter Description
73424981
VS.BOOST.UU.Anchor.UL
.R99.Bytes
Number of R99 Uplink Bytes

of UU BOOST Anchor for
Cell
Description
This counter provides the total RLC traffic volume received by PS services of UU BOOST
anchor UEs on uplink R99 channels in cells in the active set. RLC headers and retransmitted
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
Issue 03 (2015-06-30)

1173
BSC6900 UMTS
Related Features
None
Mean Throughput of R99 Uplink of UU BOOST Anchor for Cell

Counters
Counter ID
Counter Name
Counter Description
73441549
.R99.MeanThroughput

Uplink of UU BOOST
Anchor for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73424982
.R99.Time
Duration of R99 Uplink

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 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
Issue 03 (2015-06-30)

1174
BSC6900 UMTS
Related Features
None
Number of HSUPA Uplink Bytes of UU BOOST Anchor for Cell

Counters
Counter ID
Counter Name
Counter Description
73424983
.HSUPA.Bytes
Number of HSUPA Uplink

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
Unit
byte
Related Features
None
Mean Throughput of HSUPA Uplink of UU BOOST Anchor for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441550
.HSUPA.MeanThroughput
Mean Throughput of HSUPA

Uplink of UU BOOST
Anchor for Cell

1175
BSC6900 UMTS
specific formulas.
Counter ID
Counter Name
Counter Description
73424984
.HSUPA.Time
Duration of HSUPA Uplink

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]
Unit
kbit/s
Related Features
None
Number of R99 Downlink Bytes of UU BOOST Branch for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424985
VS.BOOST.UU.Branch.DL.
R99.Bytes

Bytes of UU BOOST Branch
for Cell

1176
BSC6900 UMTS
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
Mean Throughput of R99 Downlink of UU BOOST Branch for Cell

Counters
Counter ID
Counter Name
Counter Description
73441551
R99.MeanThroughput

Branch for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73424986
R99.Time
Duration of R99 Downlink

Sending Data of UU BOOST
Branch for Cell
Description
This counter provides the mean throughput rate of PS services of UU BOOST branch UEs
transmitted on downlink R99 channels of cells in the active set.
Issue 03 (2015-06-30)

1177
BSC6900 UMTS
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
Number of HSDPA Downlink Bytes of UU BOOST Branch for Cell

Counters
Counter ID
Counter Name
Counter Description
73424987
HSDPA.Bytes
Number of HSDPA
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
Issue 03 (2015-06-30)

1178
BSC6900 UMTS
Unit
byte
Related Features
None
Mean Throughput of HSDPA Downlink of UU BOOST Branch for Cell

Counters
Counter ID
Counter Name
Counter Description
73441552
HSDPA.MeanThroughput
Mean Throughput of HSDPA

Branch for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73424988
HSDPA.Time
Duration of HSDPA
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]
Issue 03 (2015-06-30)

1179
BSC6900 UMTS
Unit
kbit/s
Related Features
None
Number of R99 Uplink Bytes of UU BOOST Branch for Cell

Counters
Counter ID
Counter Name
Counter Description
73424989
VS.BOOST.UU.Branch.UL.
R99.Bytes
Number of R99 Uplink Bytes

of UU BOOST Branch for
Cell
Description
branch UEs on uplink R99 channels in cells in the active set. RLC headers and retransmitted
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
Issue 03 (2015-06-30)

1180
BSC6900 UMTS
Mean Throughput of R99 Uplink of UU BOOST Branch for Cell

Counters
Counter ID
Counter Name
Counter Description
73441553
R99.MeanThroughput

Uplink of UU BOOST
Branch for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73424990
R99.Time
Duration of R99 Uplink

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
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
Issue 03 (2015-06-30)

1181
BSC6900 UMTS
Number of HSUPA Uplink Bytes of UU BOOST Branch for Cell

Counters
Counter ID
Counter Name
Counter Description
73424991
HSUPA.Bytes
Number of HSUPA Uplink

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
Related Features
None
Mean Throughput of HSUPA Uplink of UU BOOST Branch for Cell

Counters
Counter ID
Counter Name
Counter Description
73441554
HSUPA.MeanThroughput
Mean Throughput of HSUPA

Uplink of UU BOOST
Branch for Cell
specific formulas.
Issue 03 (2015-06-30)

1182
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73424992
HSUPA.Time
Duration of HSUPA Uplink

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
Related Features
None
Number of UU BOOST BPL Capability Indication Messages Received for Cell

Counters
Counter ID
Counter Name
Counter Description
73424993
VS.BOOST.UU.BPLCapRp
rtInd
Number of UU BOOST BPL

Messages Received for Cell
Description
This counter provides the number of UU BOOST BPL capability indication messages received
in the best cell.
Issue 03 (2015-06-30)

1183
BSC6900 UMTS
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-497 BPL Message Interaction
Formula
None
Unit
None
Related Features
None
Number of Successful Responses to UU BOOST BPL Capability Indication

Messages Transmitted for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424994
VS.BOOST.UU.BPLCapRs
p.Succ
Responses to UU BOOST
BPL Capability Indication
Messages Transmitted for
Cell

1184
BSC6900 UMTS
Description
This counter provides the number of successful responses to UU BOOST BPL capability
indication messages transmitted in the best cell.
Measurement point
This measurement is triggered at point B as shown in the figure. When the RNC successfully
responds to a UU BOOST BPL capability indication message after PS RAB establishment, the
RNC measures this item in the best cell of the UE.
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

1185
BSC6900 UMTS
Number of UU BOOST BPL User Information Indication Messages Received for

Cell
Counters
Counter ID
Counter Name
Counter Description
73424995
VS.BOOST.UU.BPLInfoRprtInd

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.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1186
BSC6900 UMTS
Related Features
None
Number of Successful Responses to UU BOOST BPL User Information Indication

Messages Transmitted for Cell
Counters
Counter ID
Counter Name
Counter Description
73424996
VS.BOOST.UU.BPLInfoRs
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.
Issue 03 (2015-06-30)

1187
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
Number of UU BOOST BPL Release Messages Transmitted for Cell

Counters
Counter ID
Counter Name
Counter Description
73424997
VS.BOOST.UU.BPLRel

Release Messages
Description
This counter provides the number of UU BOOST BPL release messages transmitted in the best
cell.
Measurement point
This measurement is triggered at point E as shown in the figure. When the RNC transmits a UU
BOOST BPL release message after PS RAB establishment and branch connection timeout, the
RNC measures this item in the best cell of the UE.
Issue 03 (2015-06-30)

1188
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
Number of Successful UU BOOST Setups for Cell

Counters
Counter ID
Counter Name
Counter Description
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.
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.
Issue 03 (2015-06-30)

1189
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
Number of Normal UU BOOST Anchor Releases for Cell

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

1190
BSC6900 UMTS
Figure 1-503 Iu release
Formula
None
Unit
None
Related Features
None
Number of Normal UU BOOST Branch Releases for Cell

Counters
Counter ID
Counter Name
Counter Description
73425000
VS.BOOST.UU.Branch.Nor
mRel
Number of Normal UU
BOOST Branch Releases for
Cell
Description
This counter provides the number of normal UU BOOST branch UE releases in the best cell.
Issue 03 (2015-06-30)

1191
BSC6900 UMTS
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-504 IU
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

1192
BSC6900 UMTS
Average Number of UU BOOST Anchor UEs for Cell

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

Counters
Counter ID
Counter Name
Counter Description
73441556
VS.BOOST.UU.BranchUEs
.Mean
Average Number of UU
BOOST Branch UEs for Cell
Description
This counter provides the average number of UU BOOST branch UEs in the best cell.
Measurement point
In the best cell of the branch UEs, the RNC periodically samples the number of UU BOOST
branch UEs. The sample period is 5s. At the end of a measurement period, the RNC measures
Issue 03 (2015-06-30)

1193
BSC6900 UMTS
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 CBS Measurement <per Cell>(CBS.Cell)

Overview
The cell broadcast service function subset is to measure the following items on a cell basis.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73430561
VS.CBS.WriteReplace
Expected Number of
Messages with
WRITE-REPLACE
Information per Cell
BSC6900
V900R017C10
73430560
VS.CBS.WriteRepl
ace.CTCH.Tx
Number of Messages
with WRITEREPLACE
Information Sent on
the CTCH per Cell
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

1194
BSC6900 UMTS
Expected Number of Messages with WRITE-REPLACE Information per Cell

Counters
Counter ID
Counter Name
Counter Description
73430561
VS.CBS.WriteReplace
Expected Number of
Messages with WRITEREPLACE Information per
Cell
Description
This counter provides the expected number of messages with WRITE-REPLACE information
to be sent to UEs in a cell. Upon receiving a WRITE-REPLACE message from the cell broadcast
center (CBC), the RNC obtains the cell information contained in this message and sends this
message to UEs in the listed cells. This counter complies with 3GPP TS 25.419 (V11.1.0). For
details about this counter, see section 8.2 "Write-Replace" in this TS.
Measurement point
The measurement is triggered at point A in figure. After receiving a WRITE-REPLACE message
from the CBC, the RNC obtains the cell information contained in this message and sends this
message to UEs in the listed cells. This counter is measured in all these cells.
Figure 1-505 Successful transmission of a WRITE-REPLACE message
Issue 03 (2015-06-30)

1195
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CBS.WriteReplace
WRFD-011000
WRFD-011001
Simplified Cell Broadcast
WRFD-020127
Warning of Disaster
Number of Messages with WRITE-REPLACE Information Sent on the CTCH per

Cell
Counters
Counter ID
Counter Name
Counter Description
73430560
VS.CBS.WriteReplace.CTC
H.Tx
Number of Messages with

WRITE-REPLACE
Information Sent on the
CTCH per Cell
Description
This counter provides the number of BMC CBS messages with WRITE-REPLACE information
sent on the CTCH in a cell. This counter excludes retransmitted messages. This counter complies
with 3GPP TS 25.324 (V11.1.0). For details about this counter, see section 10.2 "BMC CBS
Message" in this TS.
Measurement point
The measurement is triggered at point A in figure 1. On receiving a WRITE-REPLACE message
from the CBC, the RNC sends this message to UEs in the cells indicated by this message. Note
that this counter excludes retransmitted messages.
Issue 03 (2015-06-30)

1196
BSC6900 UMTS
Figure 1-506 CBS message transmission procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CBS.WriteReplace.CTC
H.Tx
WRFD-011000
WRFD-011001
Simplified Cell Broadcast
WRFD-020127
Warning of Disaster
1.12.6 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423941
VS.IndepTRBNum
.FACH
Number of TBs That

Contain only TRB
Data on FACHs
BSC6900
V900R014

1197
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73423942
VS.SRBNum.FAC
H
Number of TBs That

Contain SRB Data on
FACHs
BSC6900
V900R014
73423943
VS.OneSRBTTINu
m.FACH
Number of TTIs
During Which One
SRB TB Is
Transmitted on
FACHs
BSC6900
V900R014
73423944
VS.TRBNum.RAC
H
Number of TRB TBs

Received on RACHs
BSC6900
V900R014
None
Number of TBs That Contain only TRB Data on FACHs

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)

1198
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IndepTRBNum.FACH
WRFD-021000
Transport Channel
Management
Number of TBs That Contain SRB Data on FACHs

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRBNum.FACH
WRFD-021000
Transport Channel
Management

1199
BSC6900 UMTS
Number of TTIs During Which One SRB TB Is Transmitted on FACHs

Counters
Counter ID
Counter Name
Counter Description
73423943
VS.OneSRBTTINum.FACH
Number of TTIs During

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

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423944
VS.TRBNum.RACH
Number of TRB TBs

Received on RACHs

1200
BSC6900 UMTS
Description
This counter measures the number of TRB TBs received on RACHs in a cell.
Measurement point
This counter is measured at MAC-c.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.TRBNum.RACH
WRFD-021000
Transport Channel
Management
1.12.7 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180378
VS.AttCellUpdt.R
LFail
Number of Cell
Updates Due to
Radio Link Failure
for Cell
Earlier than
BSC6900
V900R011

1201
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189767
VS.SuccCellUpdt.R
LFail
Number of
Successful Cell
Updates Due to
Radio Link Failure
for Cell
Earlier than
BSC6900
V900R011
67189768
VS.FailCellUpdt.R
LFail.NoReply
Number of Failed
Cell Updates Due to
No Response from
UE for Cell (Cell
Update Caused by
RL Failure)
Earlier than
BSC6900
V900R011
67180370
VS.CellUpdt.Confirm
Number of CELL
UPDATE
CONFIRM
Messages from
SRNC for Cell
Earlier than
BSC6900
V900R011
67192569
VS.AttCellUpdt
Number of Cell
Updates for Cell
Earlier than
BSC6900
V900R011
67192570
VS.AttCellUpdt.Er
rSRB
Number of Cell
Updates Due to SRB
RLC Unrecoverable
Error for Cell
Earlier than
BSC6900
V900R011
67192571
VS.AttCellUpdt.Er
rTRB
Number of Cell
Updates Due to TRB
RLC Unrecoverable
Error for Cell
Earlier than
BSC6900
V900R011
67192572
VS.SuccCellUpdt.E
rrTRB
Number of
Successful Cell
Updates Due to TRB
RLC Unrecoverable
Error for Cell
Earlier than
BSC6900
V900R011
67192573
VS.AttCellUpdt.M
bmsRecv
Number of Cell
Updates Due to
MBMS Reception
for Cell
Earlier than
BSC6900
V900R011
67192574
VS.SuccCellUpdt.
MbmsRecv
Number of
Successful Cell
Updates Due to
MBMS Reception
for Cell
Earlier than
BSC6900
V900R011

1202
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192575
VS.AttCellUpdt.M
bmsPtpRbReq
Number of Cell
Updates Due to
MBMS PtP RB
Request for Cell
Earlier than
BSC6900
V900R011
67192576
VS.SuccCellUpdt.
MbmsPtpRbReq
Number of
Successful Cell
Updates Due to
MBMS PtP RB
Request for Cell
Earlier than
BSC6900
V900R011
67180372
VS.AttCellUpdt.Pr
d
Number of
Periodical Cell
Updates for Cell
Earlier than
BSC6900
V900R011
67180373
VS.AttCellUpdt.Re
sel
Number of Cell
Updates Due to Cell
Reselection for Cell
Earlier than
BSC6900
V900R011
67180374
VS.AttCellUpdt.RS
A
Number of Cell
Updates Due to ReEntering Service
Area for Cell
Earlier than
BSC6900
V900R011
67180375
VS.AttCellUpdt.Pa
geRsp
Number of Cell
Updates Due to
Paging Response for
Cell
Earlier than
BSC6900
V900R011
67180376
VS.AttCellUpdt.U
LDataTrans
Number of Cell
Updates Due to
Uplink Data
Transmission for
Cell
Earlier than
BSC6900
V900R011
67180379
VS.SuccCellUpdt.P
rd
Number of
Successful
Periodical Cell
Updates for Cell
Earlier than
BSC6900
V900R011
67180380
VS.SuccCellUpdt.R
esel
Number of
Successful Cell
Updates Due to Cell
Earlier than
BSC6900
V900R011
67180381
VS.SuccCellUpdt.R
sa
Number of
Successful Cell
Updates Due to ReEntering Service
Area for Cell
Earlier than
BSC6900
V900R011

1203
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180382
VS.SuccCellUpdt.P
ageRsp
Number of
Successful Cell
Updates Due to
Paging Response for
Cell
Earlier than
BSC6900
V900R011
67180383
VS.SuccCellUpdt.U
LDataTrans
Number of
Successful Cell
Updates Due to
Uplink Data
Transmission for
Cell
Earlier than
BSC6900
V900R011
67180371
VS.SuccCellUpdt
Number of
Successful Cell
Updates for Cell
Earlier than
BSC6900
V900R011
67180386
VS.CellUpdt.RRC
Rel
Number of RRC
Connection Releases
Due to Cell Update
Failure for Cell
Earlier than
BSC6900
V900R011
73423781
VS.SuccCellUpdt.E
rrSRB
Number of
Successful Cell
Updates Due to SRB
RLC Unrecoverable
Error for Cell
BSC6900
V900R013
73424125
VS.FailCellUpdt.E
rrSRB.NoReply.FA
CH
Number of Cell
Update Failures due
to No Response from
UEs in the
CELL_FACH State
(SRB RLC ERROR)
for Cell
BSC6900
V900R014
73424126
VS.FailCellUpdt.E
rrTRB.NoReply.F
ACH
Number of Cell
Update Failures due
to No Response from
UEs in the
CELL_FACH State
(TRB RLC ERROR)
for Cell
BSC6900
V900R014
73424915
VS.AttCellUpdt.Ms
g
Number of Cell
Updates in a Cell
BSC6900
V900R014

1204
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424916
VS.AttCellUpdt.Ms
g.Conv
Number of Cell
Updates Triggered
by CS Service
Establishments in a
Cell
BSC6900
V900R014
73424917
VS.CU.CONV.FC.
Num.CPU.OverLo
ad
Number of Cell
Updates that Are
Under CPU UsageBased Flow Control
and Are Triggered by
CS Service
Establishments in a
Cell
BSC6900
V900R014
73424918
VS.CU.CONV.FC.
Num.RRCQueue
Number of Cell
Updates that Are
Under RRC
Queuing-Based
Flow Control and
Are Triggered by CS
Service
Establishments in a
Cell
BSC6900
V900R014
73424919
VS.CU.FC.Num.R
RCQueue
Number of Cell
Updates that Are
Under RRC
Queuing-Based
Flow Control in a
Cell
BSC6900
V900R014
73426812
VS.AttCellUpdt.Or
gStrCall.PCH
Number of Cell
Update Attempts for
Cell (Originating
Streaming Call)
BSC6900
V900R015C01
73426813
VS.AttCellUpdt.Or
gInterCall.PCH
Number of Cell
Update Attempts for
Cell (Originating
Interactive Call)
BSC6900
V900R015C01
73426814
VS.AttCellUpdt.Or
gBkgCall.PCH
Number of Cell
Update Attempts for
Cell (Originating
Background Call)
BSC6900
V900R015C01

1205
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426815
VS.AttCellUpdt.Or
gSubCall.PCH
Number of Cell
Update Attempts for
Cell (Originating
Subscribed traffic
Call)
BSC6900
V900R015C01
73426816
VS.AttCellUpdt.Or
gHhPrSig.PCH
Number of Cell
Update Attempts for
Cell (Originating
High Priority
Signalling)
BSC6900
V900R015C01
73426817
VS.AttCellUpdt.Or
gLwPrSig.PCH
Number of Cell
Update Attempts for
Cell (Originating
Low Priority
Signalling)
BSC6900
V900R015C01
73426818
VS.AttCellUpdt.T
mStrCall.PCH
Number of Cell
Update Attempts for
Cell (Terminating
Streaming Call)
BSC6900
V900R015C01
73426819
VS.AttCellUpdt.T
mInterCall.PCH
Number of Cell
Update Attempts for
Cell (Terminating
Interactive Call)
BSC6900
V900R015C01
73426820
VS.AttCellUpdt.T
mBkgCall.PCH
Number of Cell
Update Attempts for
Cell (Terminating
Background Call)
BSC6900
V900R015C01
73426821
VS.AttCellUpdt.T
mHhPrSig.PCH
Number of Cell
Update Attempts for
Cell (Terminating
High Priority
Signalling)
BSC6900
V900R015C01
73426822
VS.AttCellUpdt.T
mLwPrSig.PCH
Number of Cell
Update Attempts for
Cell (Terminating
Low Priority
Signalling)
BSC6900
V900R015C01
73426823
VS.AttCellUpdt.Un
known.PCH
Number of Cell
Update Attempts for
Cell (Terminating cause unknown)
BSC6900
V900R015C01

1206
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426824
VS.AttCellUpdt.Re
g.PCH
Number of Cell
Update Attempts for
Cell (Registration)
BSC6900
V900R015C01
73426825
VS.AttCellUpdt.De
tach.PCH
Number of Cell
Update Attempts for
Cell (Detach)
BSC6900
V900R015C01
73426826
VS.AttCellUpdt.Ot
her.PCH
Number of Cell
Update Attempts for
Cell (Other)
BSC6900
V900R015C01
73426827
VS.SuccCellUpdt.
OrgStrCall.PCH
Number of
Successful Cell
Updates for Cell
(Originating
Streaming Call)
BSC6900
V900R015C01
73426828
VS.SuccCellUpdt.
OrgInterCall.PCH
Number of
Successful Cell
Updates for Cell
(Originating
Interactive Call)
BSC6900
V900R015C01
73426829
VS.SuccCellUpdt.
OrgBkgCall.PCH
Number of
Successful Cell
Updates for Cell
(Originating
Background Call)
BSC6900
V900R015C01
73426830
VS.SuccCellUpdt.
OrgSubCall.PCH
Number of
Successful Cell
Updates for Cell
(Originating
Subscribed traffic
Call)
BSC6900
V900R015C01
73426831
VS.SuccCellUpdt.
OrgHhPrSig.PCH
Number of
Successful Cell
Updates for Cell
(Originating High
Priority Signalling)
BSC6900
V900R015C01
73426832
VS.SuccCellUpdt.
OrgLwPrSig.PCH
Number of
Successful Cell
Updates for Cell
(Originating Low
BSC6900
V900R015C01

1207
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426833
VS.SuccCellUpdt.T
mStrCall.PCH
Number of
Successful Cell
Updates for Cell
(Terminating
Streaming Call)
BSC6900
V900R015C01
73426834
VS.SuccCellUpdt.T
mInterCall.PCH
Number of
Successful Cell
Updates for Cell
(Terminating
Interactive Call)
BSC6900
V900R015C01
73426835
VS.SuccCellUpdt.T
mBkgCall.PCH
Number of
Successful Cell
Updates for Cell
(Terminating
Background Call)
BSC6900
V900R015C01
73426836
VS.SuccCellUpdt.T
mHhPrSig.PCH
Number of
Successful Cell
Updates for Cell
(Terminating High
BSC6900
V900R015C01
73426837
VS.SuccCellUpdt.T
mLwPrSig.PCH
Number of
Successful Cell
Updates for Cell
(Terminating Low
BSC6900
V900R015C01
73426838
VS.SuccCellUpdt.U
nknown.PCH
Number of
Successful Cell
Updates for Cell
(Terminating - cause
unknown)
BSC6900
V900R015C01
73426839
VS.SuccCellUpdt.R
eg.PCH
Number of
Successful Cell
Updates for Cell
(Registration)
BSC6900
V900R015C01
73426840
VS.SuccCellUpdt.D
etach.PCH
Number of
Successful Cell
Updates for Cell
(Detach)
BSC6900
V900R015C01
73426841
VS.SuccCellUpdt.
Other.PCH
Number of
Successful Cell
Updates for Cell
(Other)
BSC6900
V900R015C01

1208
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426842
VS.AttCellUpdt.P2
D
Number of Cell
Update Attempts
Accompanied by
P2D State
BSC6900
V900R015C01
73426843
VS.CellUpdt.Confi
rm.PageAndUlDat
a.PCH
Number of CELL
UPDATE
CONFIRM
Messages Sent by the
RNC for Cell (for the
CELL UPDATE
Messages with the
Cause Value "uplink
data transmission" or
"paging response")
BSC6900
V900R015C01
73426844
VS.AttCellUpdt.P2
D.OldRAB
Number of Cell
Update Attempts
Accompanied by
P2D State
Transitions Due to
Existing Data
Transmission
Requirements for
Cell
BSC6900
V900R015C01
73426845
VS.SuccCellUpdt.P
2D.OldRAB
Number of
Successful Cell
Updates
Accompanied by
P2D State
Transitions Due to
Existing Data
Transmission
Requirements for
Cell
BSC6900
V900R015C01
73426327
VS.AttCellUpdt.Or
gConvCall.PCH
Number of Cell
Update Attempts for
Cell (Originating
Conversational Call)
BSC6900
V900R015C00
73426328
VS.AttCellUpdt.T
mConvCall.PCH
Number of Cell
Update Attempts for
Cell (Terminating
BSC6900
V900R015C00

1209
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426329
VS.AttCellUpdt.E
mgCall.PCH
Number of Cell
Update Attempts for
Cell (Emergency
Call)
BSC6900
V900R015C00
73426330
VS.SuccCellUpdt.
OrgConvCall.PCH
Number of
Successful Cell
Updates for Cell
(Originating
BSC6900
V900R015C00
73426331
VS.SuccCellUpdt.T
mConvCall.PCH
Number of
Successful Cell
Updates for Cell
(Terminating
BSC6900
V900R015C00
73426332
VS.SuccCellUpdt.E
mgCall.PCH
Number of
Successful Cell
Updates for Cell
(Emergency Call)
BSC6900
V900R015C00
73426363
VS.P2F.Redir.Out
Number of Outgoing
P2F Redirections for
Cell
BSC6900
V900R015C00
73426364
VS.P2F.Redir.In.U
seNewCU
Number of Incoming
Cell (Cell Update)
BSC6900
V900R015C00
73426365
VS.P2F.Redir.Fail
Out.NonTargetFC
N
Number of P2F
Redirection Failures
Caused by UE Not
Accessing the Target
Frequency for Cell
BSC6900
V900R015C00
73426366
VS.P2F.Redir.Fail
Out.NoReply
Number of P2F
Redirection Failures
Caused by UE No
Response for Cell
BSC6900
V900R015C00
73427011
VS.P2F.Redir.In.Di
rectCmp
Number of Incoming
Cell (Direct
Complete)
BSC6900
V900R015C01
73427055
VS.P2F.Redir.Out.
RT.P2DFail
Number of Outgoing
Real-time Services
After P2D Failures
BSC6900
V900R015C01

1210
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73427056
VS.P2F.Redir.Out.
RT
Number of Outgoing
Real-time Services
for Cell
BSC6900
V900R015C01
73428882
VS.FailCellUpdt.P
2D.Cong
Number of Failed
State Transitions
from CELL_PCH/
URA_PCH to
CELL_DCH Due to
Resource
Congestion for Cell
BSC6900
V900R016C00
73428883
VS.FailCellUpdt.P
2D.CSConv.Cong
Number of Failed
State Transitions
from CELL_PCH/
URA_PCH to
CELL_DCH for
New CS Services
Due to Resource
Congestion for Cell
BSC6900
V900R016C00
73428884
VS.FailCellUpdt.P
2D.OldRAB.Cong
Number of Failed
State Transitions
from CELL_PCH/
URA_PCH to
CELL_DCH for
Existing Data
Transmission
Requirements Due to
Resource
Congestion for Cell
BSC6900
V900R016C00
Issue 03 (2015-06-30)

1211
BSC6900 UMTS
Counter
Sub Counter
VS.AttCellUpdt
VS.AttCellUpdt.OrgStrCall.PCH
VS.AttCellUpdt.OrgInterCall.PCH
VS.AttCellUpdt.OrgBkgCall.PCH
VS.AttCellUpdt.OrgSubCall.PCH
VS.AttCellUpdt.OrgHhPrSig.PCH
VS.AttCellUpdt.OrgLwPrSig.PCH
VS.AttCellUpdt.TmStrCall.PCH
VS.AttCellUpdt.TmInterCall.PCH
VS.AttCellUpdt.TmBkgCall.PCH
VS.AttCellUpdt.TmHhPrSig.PCH
VS.AttCellUpdt.TmLwPrSig.PCH
VS.AttCellUpdt.Unknown.PCH
VS.AttCellUpdt.Reg.PCH
VS.AttCellUpdt.Detach.PCH
VS.AttCellUpdt.Other.PCH
VS.AttCellUpdt.OrgConvCall.PCH
VS.AttCellUpdt.TmConvCall.PCH
VS.AttCellUpdt.EmgCall.PCH
VS.SuccCellUpdt
VS.SuccCellUpdt.OrgStrCall.PCH
VS.SuccCellUpdt.OrgInterCall.PCH
VS.SuccCellUpdt.OrgBkgCall.PCH
VS.SuccCellUpdt.OrgSubCall.PCH
VS.SuccCellUpdt.OrgHhPrSig.PCH
VS.SuccCellUpdt.OrgLwPrSig.PCH
VS.SuccCellUpdt.TmStrCall.PCH
VS.SuccCellUpdt.TmInterCall.PCH
VS.SuccCellUpdt.TmBkgCall.PCH
VS.SuccCellUpdt.TmHhPrSig.PCH
VS.SuccCellUpdt.TmLwPrSig.PCH
VS.SuccCellUpdt.Unknown.PCH
VS.SuccCellUpdt.Reg.PCH
VS.SuccCellUpdt.Detach.PCH
VS.SuccCellUpdt.Other.PCH
VS.SuccCellUpdt.OrgConvCall.PCH
VS.SuccCellUpdt.TmConvCall.PCH
VS.SuccCellUpdt.EmgCall.PCH
VS.P2F.Redir.Out.RT
Issue 03 (2015-06-30)
VS.P2F.Redir.Out.RT.P2DFail

1212
BSC6900 UMTS
Number of Unsuccessful Cell Updates due to RL Failure (No Response)

Counters
Counter ID
Counter Name
Counter Description
67189768
VS.FailCellUpdt.RLFail.No
Reply
Number of Failed Cell

Updates Due to No Response
from UE for Cell (Cell
Update Caused by RL
Failure)
Description
This counter provides the number of times that a cell update triggered by "radio link failure"
fails due to UE no response.This counter complies with section "8.3.1 Cell and URA update
Measurement point
The measurement is triggered at point A in Figure 1. After receiving a CELL UPDATE message
carrying a cause value of "radio link failure" from the UE, the RNC sends a CELL UPDATE
CONFIRM message to the UE and starts a timer to wait for a response message from the UE
(Figure 1 uses the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message as
an example.) If the RNC does not receive any response message from the UE before the timer
expires, this counter is measured for the cell where the UE sends the CELL UPDATE message.
Figure 1-507 Cell update procedure (failed operation due to timer expiry)
Issue 03 (2015-06-30)

1213
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.FailCellUpdt.RLFail.No
Reply
WRFD-010801
Intra RNC Cell Update
WRFD-010802
Number of Confirmation Messages from SRNC

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.3.1 Cell and URA update
Measurement point
The measurement is triggered at point B as shown in the figure, when the SRNC sends a CELL
UPDATE CONFIRM message to the UE. In this case, the RNC measures the item in the cell
that the UE has selected during the cell update procedure. Note that the measurement is not
triggered for a CELL UPDATE CONFIRM message that is retransmitted by the RNC.
Issue 03 (2015-06-30)

1214
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CellUpdt.Confirm
WRFD-010801
WRFD-010802
Number of Cell Update Attempts for Different Causes

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
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

1215
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192570
VS.AttCellUpdt.ErrSRB

to SRB RLC Unrecoverable
Error for Cell
67192571
VS.AttCellUpdt.ErrTRB

to TRB RLC Unrecoverable
Error for Cell
67192573
VS.AttCellUpdt.MbmsRecv

to MBMS Reception for Cell
67192575
VS.AttCellUpdt.MbmsPtpR
bReq

to MBMS PtP RB Request
for Cell
67180373
VS.AttCellUpdt.Resel

to Cell Reselection for Cell
67180374
VS.AttCellUpdt.RSA

to Re-Entering Service Area
for Cell
67180375
VS.AttCellUpdt.PageRsp

to Paging Response for Cell
67180376
VS.AttCellUpdt.ULDataTrans

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.The preceding counters comply with section "8.3.1 Cell and URA
update procedures" in 3GPP TS 25.331 (v10.13.0).
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 counters based on different cell update causes in the cell that
the UE chooses during the cell update. The table describes these counters. These counters are
not measured for a CELL UPDATE message retransmitted by the UE in the same cell.
Issue 03 (2015-06-30)

1216
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttCellUpdt.Prd
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010616
MBMS Introduction
Package
VS.AttCellUpdt.RLFail
VS.AttCellUpdt
VS.AttCellUpdt.ErrSRB
VS.AttCellUpdt.ErrTRB
VS.AttCellUpdt.MbmsRecv
Issue 03 (2015-06-30)

1217
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.AttCellUpdt.MbmsPtpR
bReq
WRFD-010801
WRFD-010802
WRFD-010616
MBMS Introduction
Package
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
VS.AttCellUpdt.Resel
VS.AttCellUpdt.RSA
VS.AttCellUpdt.PageRsp
VS.AttCellUpdt.ULDataTrans
Number of Successful Cell Updates for Different Causes

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180371
VS.SuccCellUpdt

Updates for Cell
67189767
VS.SuccCellUpdt.RLFail

Updates Due to Radio Link
Failure for Cell
67192572
VS.SuccCellUpdt.ErrTRB

Updates Due to TRB RLC
Unrecoverable Error for Cell
67192574
VS.SuccCellUpdt.MbmsRec
v

Updates Due to MBMS
Reception for Cell
67192576
VS.SuccCellUpdt.MbmsPtp
RbReq

Updates Due to MBMS PtP
RB Request for Cell
67180379
VS.SuccCellUpdt.Prd
Periodical Cell Updates for
Cell

1218
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67180380
VS.SuccCellUpdt.Resel

Updates Due to Cell
67180381
VS.SuccCellUpdt.Rsa

Updates Due to Re-Entering
Service Area for Cell
67180382
VS.SuccCellUpdt.PageRsp

Updates Due to Paging
Response for Cell
67180383
VS.SuccCellUpdt.ULDataTrans

Updates Due to Uplink Data
Transmission for Cell
73423781
VS.SuccCellUpdt.ErrSRB

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.The preceding counters comply with section "8.3.1 Cell and URA update
Measurement point
There are two types of cell update procedures: cell update requiring UE response and cell update
requiring no UE response.
In a cell update requiring no UE response, the RNC determines that the cell update is successful
after sending the CELL UPDATE CONFIRM message. In this procedure, the measurement is
triggered after the RNC sends a CELL UPDATE CONFIRM message to the UE based on the
cause value, as shown by point B in the following figure. The corresponding counter is measured
in the cell that is selected by the UE for cell update.
Issue 03 (2015-06-30)

1219
BSC6900 UMTS
Figure 1-510 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:
Figure 1-511 Cell update procedure with physical channel reconfiguration
Issue 03 (2015-06-30)

1220
BSC6900 UMTS
After the RNC receives a cell update message, if the RNC directly performs the RRC connection
release procedure rather than performs a cell update, the counter is measured at point B, as shown
in the following figure. For example, for cell updates due to SRB RLC unrecoverable errors,
when the SRB reestablishment algorithm is disabled, the counter is measured after the RNC
performs the RRC connection release procedure.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccCellUpdt
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010616
MBMS Introduction
Package
VS.SuccCellUpdt.RLFail
VS.SuccCellUpdt.ErrTRB
VS.SuccCellUpdt.MbmsRec
v
Issue 03 (2015-06-30)

1221
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.SuccCellUpdt.MbmsPtp
RbReq
WRFD-010801
WRFD-010802
WRFD-010616
MBMS Introduction
Package
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.ULDataTrans
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.ErrSRB
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.Prd
VS.SuccCellUpdt.Resel
VS.SuccCellUpdt.Rsa
VS.SuccCellUpdt.PageRsp
Number of RRC Connection Releases due to Cell Update Failure

Counters
Counter ID
Counter Name
Counter Description
67180386
VS.CellUpdt.RRCRel

Releases Due to Cell Update
Failure for Cell
Description
This counter provides the number of RRC connection releases due to cell update failures.This
counter complies with section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331
(v10.13.0).
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 the cell update.
Issue 03 (2015-06-30)

1222
BSC6900 UMTS
Figure 1-513 RRC connection release procedure triggered by cell update
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CellUpdt.RRCRel
WRFD-010801
WRFD-010802
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Cell Update Failures due to No Response from UEs in the CELL_FACH
State for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424125
VS.FailCellUpdt.ErrSRB.N
oReply.FACH

Failures due to No Response
from UEs in the
CELL_FACH State (SRB
RLC ERROR) for Cell

1223
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73424126
VS.FailCellUpdt.ErrTRB.N
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.The preceding
counters comply with section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered at point A in the Figure 1. 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 used as an example). If the RNC does not
receive any response message from the UE before the timer expires, these counters are increased
by one in the cell where the UE sends the CELL UPDATE message according to the value carried
in the information element(IE) "AM_RLC error indication(RB2, RB3 or RB4)" and IE
"AM_RLC error indication(RB>4)" in the CELL UPDATE message.
Figure 1-514 Cell update procedure (failed operation due to timer expiry)
Formula
None
Issue 03 (2015-06-30)

1224
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.FailCellUpdt.ErrSRB.N
oReply.FACH
WRFD-010801
WRFD-010802
VS.FailCellUpdt.ErrTRB.N
oReply.FACH
WRFD-010801
WRFD-010802
Counter ID
Counter Name
Counter Description
73424915
VS.AttCellUpdt.Msg
Number of Cell Updates in a

Cell
Number of Cell Updates in a Cell

Counters
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.This
(v10.13.0).
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, as shown by point A in
the following figure.
Figure 1-515 Basic cell update procedure from UE
Issue 03 (2015-06-30)

1225
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttCellUpdt.Msg
WRFD-040100
Flow Control
Number of Cell Updates Triggered by CS Service Establishments in a Cell

Counters
Counter ID
Counter Name
Counter Description
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
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. This counter complies with section "8.3.1 Cell and
URA update procedures" in 3GPP TS 25.331 (v10.13.0).
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, as shown by point A in the following figure.
Issue 03 (2015-06-30)

1226
BSC6900 UMTS
Figure 1-516 Basic cell update procedure from UE which established CS servcies
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttCellUpdt.Msg.Conv
WRFD-040100
Flow Control
Number of Cell Updates that Are Under CPU Usage-Based Flow Control and Are
Triggered by CS Service Establishments in a Cell
Counters
Counter ID
Counter Name
Counter Description
73424917
VS.CU.CONV.FC.Num.CP
U.OverLoad
Number of Cell Updates that

Are Under CPU UsageBased 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
Issue 03 (2015-06-30)

1227
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, as shown by point
A in the following figure.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.CU.CONV.FC.Num.CP
U.OverLoad
WRFD-040100
Flow Control

1228
BSC6900 UMTS
Number of Cell Updates that Are Under RRC Queuing-Based Flow Control and
Are Triggered by CS Service Establishments in a Cell
Counters
Counter ID
Counter Name
Counter Description
73424918
VS.CU.CONV.FC.Num.RR
CQueue

Are Under RRC QueuingBased 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 RRC Queue, the CELL UPDATE messsage will
be discarded When this cell receives a CELL UPDATE message from the UE, as shown by point
A in the following figure.
Issue 03 (2015-06-30)

1229
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CU.CONV.FC.Num.RR
CQueue
WRFD-040100
Flow Control
Number of Cell Updates that Are Under RRC Queuing-Based Flow Control in a
Cell
Counters
Counter ID
Counter Name
Counter Description
73424919
VS.CU.FC.Num.RRCQueue

Are Under RRC QueuingBased Flow Control in a Cell
Description
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.This counter
complies with section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331 (v10.13.0).
Measurement point
Flow Control Triggered by RRC Queue. 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, as shown by point A in the following figure.
Issue 03 (2015-06-30)

1230
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CU.FC.Num.RRCQueue
WRFD-040100
Flow Control
Number of Cell Update Attempts for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426812
VS.AttCellUpdt.OrgStrCall.
PCH

Attempts for Cell
(Originating Streaming Call)
73426813
VS.AttCellUpdt.OrgInterCal
l.PCH

Attempts for Cell
(Originating Interactive Call)
73426814
VS.AttCellUpdt.OrgBkgCal
l.PCH

Attempts for Cell
(Originating Background
Call)

1231
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426815
VS.AttCellUpdt.OrgSubCall
.PCH

Attempts for Cell
(Originating Subscribed
traffic Call)
73426816
VS.AttCellUpdt.OrgHhPrSi
g.PCH

Attempts for Cell
(Originating High Priority
Signalling)
73426817
VS.AttCellUpdt.OrgLwPrSi
g.PCH

Attempts for Cell
(Originating Low Priority
Signalling)
73426818
VS.AttCellUpdt.TmStrCall.
PCH

Attempts for Cell
(Terminating Streaming
Call)
73426819
VS.AttCellUpdt.TmInterCal
l.PCH

Attempts for Cell
(Terminating Interactive
Call)
73426820
VS.AttCellUpdt.TmBkgCall
.PCH

Attempts for Cell
(Terminating Background
Call)
73426821
VS.AttCellUpdt.TmHhPrSig
.PCH

Attempts for Cell
(Terminating High Priority
Signalling)
73426822
VS.AttCellUpdt.TmLwPrSi
g.PCH

Attempts for Cell
(Terminating Low Priority
Signalling)
73426823
VS.AttCellUpdt.Unknown.P
CH

Attempts for Cell
unknown)
73426824

Attempts for Cell
(Registration)
73426825
VS.AttCellUpdt.Detach.PC
H

Attempts for Cell (Detach)

1232
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426826

Attempts for Cell (Other)
73426327
VS.AttCellUpdt.OrgConvCa
ll.PCH

Attempts for Cell
(Originating Conversational
Call)
73426328
VS.AttCellUpdt.TmConvCa
ll.PCH

Attempts for Cell
(Terminating Conversational
Call)
73426329
VS.AttCellUpdt.EmgCall.P
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 initiate new services in a cell. These counters are measured based on the
specific causes of cell update attempts.The preceding counters comply with section "8.3.1 Cell
and URA update procedures" in 3GPP TS 25.331 (v10.13.0).
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 corresponding counter
based on the cause value. The retransmitted CELL UPDATE messages are not calculated into
these counters. The VS.AttCellUpdt.Other.PCH counter measures the number of cell update
attempts made by UEs in the CELL_PCH or URA_PCH state with other cause values in a cell.
Issue 03 (2015-06-30)

1233
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AttCellUpdt.OrgStrCall.
PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.OrgInterCal
l.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.OrgBkgCal
l.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.OrgSubCall
.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.OrgHhPrSi
g.PCH
WRFD-010801
WRFD-010802

1234
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AttCellUpdt.OrgLwPrSi
g.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.TmStrCall.
PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.TmInterCal
l.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.TmBkgCall
.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.TmHhPrSig
.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.TmLwPrSi
g.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.Unknown.P
CH
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
VS.AttCellUpdt.Detach.PC
H
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
VS.AttCellUpdt.OrgConvCa
ll.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.TmConvCa
ll.PCH
WRFD-010801
WRFD-010802
VS.AttCellUpdt.EmgCall.P
CH
WRFD-010801
WRFD-010802

1235
BSC6900 UMTS
Number of Successful Cell Updates for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426827
VS.SuccCellUpdt.OrgStrCal
l.PCH

Updates for Cell (Originating
Streaming Call)
73426828
VS.SuccCellUpdt.OrgInterC
all.PCH

Interactive Call)
73426829
VS.SuccCellUpdt.OrgBkgC
all.PCH

Background Call)
73426830
VS.SuccCellUpdt.OrgSubC
all.PCH

Subscribed traffic Call)
73426831
VS.SuccCellUpdt.OrgHhPr
Sig.PCH

High Priority Signalling)
73426832
VS.SuccCellUpdt.OrgLwPr
Sig.PCH

Low Priority Signalling)
73426833
VS.SuccCellUpdt.TmStrCal
l.PCH

Updates for Cell
Call)
73426834
VS.SuccCellUpdt.TmInterC
all.PCH

Updates for Cell
Call)
73426835
VS.SuccCellUpdt.TmBkgCa
ll.PCH

Updates for Cell
Call)
73426836
VS.SuccCellUpdt.TmHhPrS
ig.PCH

Updates for Cell
Signalling)
73426837
VS.SuccCellUpdt.TmLwPrS
ig.PCH

Updates for Cell
Signalling)

1236
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426838
VS.SuccCellUpdt.Unknown
.PCH

Updates for Cell
unknown)
73426839

Updates for Cell
(Registration)
73426840
VS.SuccCellUpdt.Detach.P
CH

Updates for Cell (Detach)
73426841
VS.SuccCellUpdt.Other.PC
H

Updates for Cell (Other)
73426330
VS.SuccCellUpdt.OrgConv
Call.PCH

73426331
VS.SuccCellUpdt.TmConv
Call.PCH

Updates for Cell
Call)
73426332
VS.SuccCellUpdt.EmgCall.
PCH

Updates for Cell (Emergency
Call)
Description
These counters measure the number of successful cell updates initiated by UEs in the
CELL_PCH or URA_PCH state to establish new services. These counters are measured in a cell
based on the specific causes of cell updates.The preceding counters comply with section "8.3.1
Cell and URA update procedures" in 3GPP TS 25.331 (v10.13.0).
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 to the UE. If the RNC receives a response from the UE, the RNC
considers the cell update procedure as successful. The measurement is triggered at point C, as
shown in the figure where the PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message 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 value in the CELL UPDATE message. On
receiving the CELL UPDATE CONFIRM message, the UE returns one of the following
messages based on the IE carried in the CELL UPDATE CONFIRM message: UTRAN
MOBILITY INFORMATION CONFIRM PHYSICAL CHANNEL RECONFIGURATION
COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO
BEARER RECONFIGURATION COMPLETE RADIO BEARER RELEASE COMPLETE
Issue 03 (2015-06-30)

1237
BSC6900 UMTS
The VS.SuccCellUpdt.Other counter measures the number of successful cell updates initiated
by UEs in the CELL_PCH or URA_PCH state with other cause values.
Figure 1-521 Cell update procedure with physical channel reconfiguration
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SuccCellUpdt.OrgStrCal
l.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.OrgInterC
all.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.OrgBkgC
all.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.OrgSubC
all.PCH
WRFD-010801
WRFD-010802

1238
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SuccCellUpdt.OrgHhPr
Sig.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.OrgLwPr
Sig.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.TmStrCal
l.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.TmInterC
all.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.TmBkgCa
ll.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.TmHhPrS
ig.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.TmLwPrS
ig.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.Unknown
.PCH
WRFD-010801
WRFD-010802
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.Detach.P
CH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.Other.PC
H
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.OrgConv
Call.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.TmConv
Call.PCH
WRFD-010801
WRFD-010802
VS.SuccCellUpdt.EmgCall.
PCH
WRFD-010801
WRFD-010802

1239
BSC6900 UMTS
Number of Cell Update Attempts Accompanied by P2D State Transitions for Cell
Counters
Counter ID
Counter Name
Counter Description
73426842
VS.AttCellUpdt.P2D

Attempts Accompanied by
P2D State Transitions for
Cell
Description
This counter measures the number of cell updates accompanied by state transitions from
CELL_PCH or URA_PCH to CELL_DCH in a cell.This counter complies with section "8.3.1
Measurement point
UPDATE message from a UE and the RNC instructs the UE to transition from the CELL_PCH
or URA_PCH state to the CELL_DCH state, this counter is measured in the cell that the UE
camps on. The retransmitted CELL UPDATE messages are not calculated into this counter. The
VS.DCCC.P2D.Succ counter measures the number of successful cell updates accompanied by
state transitions from CELL_PCH or URA_PCH to CELL_DCH.
Issue 03 (2015-06-30)

1240
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttCellUpdt.P2D
WRFD-010202

URA-PCH, CELL-FACH)
Number of CELL UPDATE CONFIRM Messages Sent by the RNC for Cell (for the
CELL UPDATE Messages with the Cause Value "uplink data transmission" or
"paging response")
Counters
Counter ID
Counter Name
Counter Description
73426843
VS.CellUpdt.Confirm.Page
AndUlData.PCH
Number of CELL UPDATE

CONFIRM Messages Sent
by the RNC for Cell (for the
with the Cause Value "uplink
data transmission" or "paging
response")
Description
This counter provides the number of CELL UPDATE CONFIRM messages sent by the RNC in
response to CELL UPDATE messages with the cause value "uplink data transmission" or
"paging response" in a cell. The CELL UPDATE messages are sent by UEs in the CELL_PCH
or URA_PCH state.This counter complies with section "8.3.1 Cell and URA update procedures"
in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point B, as shown in the figure. When receiving a CELL
a UE in the CELL_PCH or URA_PCH state, the RNC returns a CELL UPDATE CONFIRM
message to the UE. In this case, this counter is measured in the target cell. The retransmitted
CELL UPDATE CONFIRM messages are not calculated into this counter.
Issue 03 (2015-06-30)

1241
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.CellUpdt.Confirm.Page
AndUlData.PCH
WRFD-010801
WRFD-010802

1242
BSC6900 UMTS
Number of Cell Update Attempts Accompanied by P2D State Transitions Due to

Existing Data Transmission Requirements for Cell
Counters
Counter ID
Counter Name
Counter Description
73426844
VS.AttCellUpdt.P2D.OldRAB

Attempts Accompanied by
P2D State Transitions Due to
Existing Data Transmission
Requirements for Cell
Description
This counter provides the number of cell update attempts accompanied by state transitions from
CELL_PCH or URA_PCH to CELL_DCH due to existing data transmission requirements in a
cell.This counter complies with section "8.3.1 Cell and URA update procedures" in 3GPP TS
25.331 (v10.13.0).
Measurement point
a UE in the CELL_PCH or URA_PCH state and the CELL UPDATE message does not carry
the establish cause flag, this counter is increased by one. The retransmitted CELL UPDATE
messages are not calculated into this counter.
Figure 1-524 Cell update procedure with radio bearer reconfiguration
Issue 03 (2015-06-30)

1243
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttCellUpdt.P2D.OldRAB
WRFD-010202

URA-PCH, CELL-FACH)
Number of Successful Cell Updates Accompanied by P2D State Transitions Due

to Existing Data Transmission Requirements for Cell
Counters
Counter ID
Counter Name
Counter Description
73426845
VS.SuccCellUpdt.P2D.OldRAB

Updates Accompanied by
P2D State Transitions Due to
Existing Data Transmission
Description
This counter provides the number of successful cell updates accompanied by state transitions
from CELL_PCH or URA_PCH to CELL_DCH due to existing data transmission requirements
in a cell.This counter complies with section "8.3.1 Cell and URA update procedures" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC receives a CELL
a UE in the CELL_PCH or URA_PCH state and the CELL UPDATE message does not carry
the establish cause flag, the RNC considers the cell update procedure as successful if the RNC
receives a response from the UE. In this case, this counter is increased by one in the cell that the
UE camps on.
Issue 03 (2015-06-30)

1244
BSC6900 UMTS
Figure 1-525 Cell update procedure with radio bearer reconfiguration
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccCellUpdt.P2D.OldRAB
WRFD-010202

URA-PCH, CELL-FACH)
Number of Outgoing P2F Redirections for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426363
VS.P2F.Redir.Out
Number of Outgoing P2F

Redirections for Cell

1245
BSC6900 UMTS
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.This
(v10.13.0).
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-526 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.
Issue 03 (2015-06-30)

1246
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.P2F.Redir.Out
WRFD-150246
Service Steering and Load

Sharing in CELL_FACH
State

1247
BSC6900 UMTS
Number of Incoming P2F Redirections for Cell (Cell Update)

Counters
Counter ID
Counter Name
Counter Description
73426364
VS.P2F.Redir.In.UseNewCU
Number of Incoming P2F

Redirections for Cell (Cell
Update)
Description
This counter measures the number of incoming redirections triggered by state transitions from
CELL_PCH or URA_PCH to CELL_FACH in the target cell for the redirection.This counter
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.
Issue 03 (2015-06-30)

1248
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.P2F.Redir.In.UseNewCU
WRFD-150246

State
Number of P2F Redirection Failures Caused by UE Not Accessing the Target

Frequency for Cell
Counters
Counter ID
Counter Name
Counter Description
73426365
VS.P2F.Redir.FailOut.NonTargetFCN
Number of P2F Redirection

Failures Caused by UE Not
Accessing the Target
Frequency for Cell
Description
This counter measures the number of redirection failures caused by UE not accessing the target
frequency for the redirection. The redirection must be triggered by state transitions from
CELL_PCH or URA_PCH to CELL_FACH. This counter is measured in the source cell.This
(v10.13.0).
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.
Issue 03 (2015-06-30)

1249
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.P2F.Redir.FailOut.NonTargetFCN
WRFD-150246

State

1250
BSC6900 UMTS
Number of P2F Redirection Failures Caused by UE No Response for Cell

Counters
Counter ID
Counter Name
Counter Description
73426366
VS.P2F.Redir.FailOut.NoRe
ply
Number of P2F Redirection

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.This counter complies with section
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.
Issue 03 (2015-06-30)

1251
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.P2F.Redir.FailOut.NoRe
ply
WRFD-150246

State

1252
BSC6900 UMTS
Number of Incoming P2F Redirections for Cell (Direct Complete)

Counters
Counter ID
Counter Name
Counter Description
73427011
VS.P2F.Redir.In.DirectCmp
Number of Incoming P2F

Redirections for Cell (Direct
Complete)
Description
This counter measures the number of incoming redirections when the RNC receives any of the
following messages without receiving another CELL UPDATE message from a UE that is
performing the P2F state transition:
RADIO BEARER RECONFIGURATION COMPLETE.
P2F state transition refers to the transition from the CELL_PCH or URA_PCH state to the
CELL_FACH state. This counter complies with section "8.3.1 Cell and URA update procedures"
in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point B, as shown in figure 1. The RNC receives a CELL
a UE in the CELL_PCH or URA_PCH state and responds with a CELL UPDATE CONFIRM
message, instructing the UE to perform a P2F redirection. If the RNC receives a response
message, such as PHYSICAL CHANNEL RECONFIGURATION COMPLETE, in the target
cell for the redirection, this counter is increased by one in the target cell. On receiving the CELL
UPDATE CONFIRM message, the UE returns one of the following messages based on the
information element (IE) carried in the CELL UPDATE CONFIRM message:
RADIO BEARER RECONFIGURATION COMPLETE.
Issue 03 (2015-06-30)

1253
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.P2F.Redir.In.DirectCmp
WRFD-151202
FACH Pool
Number of Outgoing P2F Redirections for Real-time Services After P2D Failures
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73427055
VS.P2F.Redir.Out.RT.P2DF
ail

Redirections for Real-time
Services After P2D Failures

1254
BSC6900 UMTS
Description
This counter measures the number of P2F redirections for real-time services after UEs
performing real-time services experience P2D state transition failures. This counter is measured
in the cell where the P2F redirection is triggered.
P2D refers to the transition from the CELL_PCH or URA_PCH state to the CELL_DCH state.
P2F refers to the transition from the CELL_PCH or URA_PCH state to the CELL_FACH
state.This counter complies with section "8.3.1 Cell and URA update procedures" in 3GPP TS
25.331 (v10.13.0).
Measurement point
a UE in the CELL_PCH or URA_PCH state, the RNC attempts to transition the UE to the
CELL_DCH state. When the P2D state transition fails, the RNC performs a P2F redirection if
the RNC determines that the UE sends the CELL UPDATE message to perform real-time
services. This counter is measured in the cell where the UE sends the CELL UPDATE message
at the time the RNC sends a CELL UPDATE CONFIRM message. The retransmitted CELL
UPDATE CONFIRM messages are not calculated into this counter.
Real-time services include conversational services and push to talk (PTT) services. The RNC
considers a service as real-time service when any of the following conditions is met:
If the Establishment cause IE in the CELL UPDATE message is set to "Originating
Conversational Call", "Terminating Conversational Call", or "Emergency Call", the RNC
determines that the UE sends the CELL UPDATE message to initiate or respond to
conversational services.
If the UE has established a PTT service and the Cell update cause and Traffic volume indicator
IEs in the CELL UPDATE message are set to "uplink data transmission" and "True",
respectively, the RNC determines that the UE sends the CELL UPDATE message to initiate a
PTT call.
If the UE has established a PTT service, the PTT service has data to transmit in the downlink,
and the cell update cause IE in the CELL UPDATE message is set to "paging response", the
RNC determines that the UE sends the CELL UPDATE message to respond to a PTT call.
Issue 03 (2015-06-30)

1255
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.P2F.Redir.Out.RT.P2DF
ail
WRFD-150246

State

1256
BSC6900 UMTS
Number of Outgoing P2F Redirections for Real-time Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73427056
VS.P2F.Redir.Out.RT

Redirections for Real-time
Services for Cell
Description
This counter measures the number of outgoing P2F redirections for real-time services. It is
measured in the cell where the P2F redirection is triggered.
P2F refers to the transition from the CELL_PCH or URA_PCH state to the CELL_FACH state.
This counter complies with section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. The RNC receives a CELL
a UE in the CELL_PCH or URA_PCH state and determines that the UE sends the message to
perform real-time services. The RNC then performs a P2F redirection on the UE. This counter
is measured in the cell where the UE sends the CELL UPDATE message at the time the RNC
sends a CELL UPDATE CONFIRM message. The retransmitted CELL UPDATE CONFIRM
messages are not calculated into this counter.
This counter measures the P2F redirections after P2D state transition failures and the P2F
redirections for real-time services. The real-time services refer to AMR services. To determine
whether a real-time service is AMR service, the RNC needs to perform the following operations:
1. If the Establishment cause IE in the CELL UPDATE message is set to "Originating
Conversational Call" or "Terminating Conversational Call", the RNC determines that the UE
sends the CELL UPDATE message to initiate or respond to conversational services.
2. The RNC determines that the conversational service is AMR service, not PTT service. The
conversational service is considered as PTT service if either of the following conditions is met:
If,
The UE has established a PTT service,
The Cell update cause and Traffic volume indicator IEs in the CELL UPDATE message are set
to "uplink data transmission" and "TRUE", respectively,
The CELL UPDATE message does not include the CS Call Type IE, the RNC considers that
the UE sends the CELL UPDATE message to initiate a PTT call.
If,
The UE has established a PTT service,
Issue 03 (2015-06-30)

1257
BSC6900 UMTS
The PTT service has data to transmit in the downlink,

The cell update cause IE in the CELL UPDATE message is set to paging response, the RNC
determines that the UE sends the CELL UPDATE message to respond to a PTT call.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.P2F.Redir.Out.RT
WRFD-150246

State

1258
BSC6900 UMTS
Number of Failed State Transitions from CELL_PCH/URA_PCH to CELL_DCH

Due to Resource Congestion for Cell
Counters
Counter ID
Counter Name
Counter Description
73428882
VS.FailCellUpdt.P2D.Cong

Transitions from
CELL_PCH/URA_PCH to
CELL_DCH Due to
Description
CELL_DCH due to resource congestion in a cell. This counter helps evaluate the congestion of
resources that are used to perform admission during the state transitions.This counter complies
with section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A in the following figure. When a UE sends a CELL
UPDATE message to the RNC to trigger a state transition from CELL_PCH or URA_PCH to
CELL_DCH, the RNC performs resource-based admission. If the admission fails due to resource
congestion, this counter is measured in the serving cell.
Figure 1-535 Cell update failure caused by resource congestion
Formula
None
Issue 03 (2015-06-30)

1259
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.FailCellUpdt.P2D.Cong
WRFD-020101
Admission Control
WRFD-010202

URA-PCH, CELL-FACH)
Number of Failed State Transitions from CELL_PCH/URA_PCH to CELL_DCH for

New CS Services Due to Resource Congestion for Cell
Counters
Counter ID
Counter Name
Counter Description
73428883
VS.FailCellUpdt.P2D.CSCo
nv.Cong

Transitions from
CELL_PCH/URA_PCH to
CELL_DCH for New CS
Services Due to Resource
Congestion for Cell
Description
CELL_DCH triggered by CS service establishment in resource congestion scenarios in a cell.
This counter helps evaluate the congestion of resources that are used to perform admission during
the state transitions triggered by CS service establishment.This counter complies with section
Measurement point
UPDATE message from a UE, the RNC performs resource-based admission if the following
conditions are met: The UE sends the message to trigger a state transition from CELL_PCH or
URA_PCH to CELL_DCH; the value of the Establishment cause IE in the message is
"Originating Conversational Call", "Terminating Conversational Call", or "Emergency Call." If
the admission fails due to resource congestion, this counter is measured in the serving cell.
Issue 03 (2015-06-30)

1260
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.FailCellUpdt.P2D.CSCo
nv.Cong
WRFD-020101
Admission Control
WRFD-010202

URA-PCH, CELL-FACH)
Number of Failed State Transitions from CELL_PCH/URA_PCH to CELL_DCH for

Existing Data Transmission Requirements Due to Resource Congestion for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428884
VS.FailCellUpdt.P2D.OldR
AB.Cong

Transitions from
CELL_PCH/URA_PCH to
CELL_DCH for Existing
Data Transmission
Requirements Due to

1261
BSC6900 UMTS
Description
CELL_DCH triggered by existing data transmission requirements in resource congestion
scenarios in a cell. This counter helps evaluate the congestion of resources that are used to
perform admission during the state transitions triggered by existing data transmission
requirements.This counter complies with section "8.3.1 Cell and URA update procedures" in
3GPP TS 25.331 (v10.13.0).
Measurement point
UPDATE message from a UE, the RNC performs resource-based admission if the following
conditions are met: The UE sends the message to trigger a state transition from CELL_PCH or
URA_PCH to CELL_DCH; the message is triggered by uplink data transmission or paging
response and does not carries the Establishment cause IE. If the admission fails due to resource
congestion, this counter is measured in the serving cell.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1262
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.FailCellUpdt.P2D.OldR
AB.Cong
WRFD-020101
Admission Control
WRFD-010202

URA-PCH, CELL-FACH)
1.12.8 Measurement of Channel Reconfiguration to DCH <per

Cell>(Channel.Upswitch.Cell)
Overview
When UEs in the CELL_PCH, URA_PCH, or CELL_FACH state have large amounts of data
to transmit, the RNC switches them to the CELL_DCH state (DCH/HS-DSCH/E-DCH).
During the state transition:
(1) If the DRD policy is applied, a successful state transition is measured in the cell after the
state transition based on the UE' channels type after the channel reconfiguration. If the state
transition fails, the state transition attempt is measured in the first DRD target cell based on the
target channel type.
(2) If the UE reselects a UMTS cell under the RNC or another RNC, the RNC cancels the state
transition, and the measurement of channel reconfiguration to DCH is not performed. If the UE
initiates another state transition after the cell update procedure is complete, the state transition
is measured in the new cell.
(3) If the UE reselects an inter-RAT cell or if the UE or CN initiates a request to normally release
the connection, the state transition is canceled, and the measurement of channel reconfiguration
to DCH is not performed. The cause values indicating a normal release are "User Inactivity",
"Normal Release", "Successful Relocation", "Network Optimization", and "UE Generated
Signalling Connection Release."
Issue 03 (2015-06-30)

1263
BSC6900 UMTS
Figure 1-538 Channel Reconfiguration to DCH procedure
Issue 03 (2015-06-30)

1264
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.AttRecfg.F2D.DataTransTrig,
VS.AttRecfg.F2H.DataTransTrig,
VS.AttRecfg.F2E.DataTransTrig,
VS.AttRecfg.P2D.DataTransTrig,
VS.AttRecfg.P2H.DataTransTrig,
VS.AttRecfg.P2E.DataTransTrig,
VS.AttRecfg.Rep.F2D.DataTransTrig,
VS.AttRecfg.Rep.F2H.DataTransTrig,
VS.AttRecfg.Rep.F2E.DataTransTrig,
VS.AttRecfg.DCH0K.Upsizing,
VS.AttRecfg.DCH0K.HSDPA.Upsizing,
VS.AttRecfg.DCH0K.HSDPA.DC.Upsizing, VS.AttRecfg.DCH0K.HSDPA.
64QAM.Upsizing,
VS.AttRecfg.DCH0K.HSUPA.Upsizing
VS.SuccRecfg.F2D.DataTransTrig,
VS.SuccRecfg.F2H.DataTransTrig,
VS.SuccRecfg.F2E.DataTransTrig,
VS.SuccRecfg.P2D.DataTransTrig,
VS.SuccRecfg.P2H.DataTransTrig,
VS.SuccRecfg.P2E.DataTransTrig,
VS.SuccRecfg.DCH0K.Upsizing,
VS.SuccRecfg.DCH0K.HSDPA.Upsizing,
VS.SuccRecfg.DCH0K.HSDPA.DC.Upsizing, VS.SuccRecfg.DCH0K.HSDPA.
64QAM.Upsizing,
VS.SuccRecfg.DCH0K.HSUPA.Upsizing
VS.FailRecfg.F2D.DataTransTrig.Cong,
VS.FailRecfg.DCH0K.Cong,
VS.FailRecfg.DCH0K.ULCE.Cong,
VS.FailRecfg.DCH0K.DLCE.Cong,
VS.FailRecfg.DCH0K.Code.Cong,
VS.FailRecfg.DCH0K.ULpower.Cong,
VS.FailRecfg.DCH0K.DLpower.Cong,
VS.FailRecfg.DCH0K.DLIUBBand.Cong,
VS.FailRecfg.DCH0K.ULIUBBand.Cong,
VS.FailRecfg.DCH0K.HSUPAUser.Cong,
VS.FailRecfg.DCH0K.HSDPAUser.Cong
VS.FailRecfg.DCH0K.IubFail
VS.FailRecfg.DCH0K.IubAAL2Fail

1265
BSC6900 UMTS
Measurement points
Description
VS.FailRecfg.DCH0K.UuFail,
VS.FailRecfg.DCH0K.RBInvCfg,
VS.FailRecfg.DCH0K.RBCfgUnsupp,
VS.FailRecfg.DCH0K.PhyChFail,
VS.FailRecfg.DCH0K.UuNoReply,
VS.FailRecfg.DCH0K.SRBReset,
VS.FailRecfg.DCH0K.CellUpd
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429039
VS.AttRecfg.F2D.D
ataTransTrig
Number of F2D State

Transition Attempts
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429040
VS.AttRecfg.F2H.
DataTransTrig
Number of F2H State

Transition Attempts
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429041
VS.AttRecfg.F2E.D
ataTransTrig
Number of F2E State

Transition Attempts
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429042
VS.SuccRecfg.F2D.
DataTransTrig
Number of
Successful F2D State
Transitions
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00

1266
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429043
VS.SuccRecfg.F2H.
DataTransTrig
Number of
Successful F2H State
Transitions
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429044
VS.SuccRecfg.F2E.
DataTransTrig
Number of
Successful F2E State
Transitions
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429045
VS.AttRecfg.Rep.F
2D.DataTransTrig
Number of Repeated
F2D State Transition
Attempts Triggered
by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429046
VS.AttRecfg.Rep.F
2H.DataTransTrig
Number of Repeated
F2H State Transition
Attempts Triggered
by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429047
VS.AttRecfg.Rep.F
2E.DataTransTrig
Number of Repeated
F2E State Transition
Attempts Triggered
by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429048
VS.FailRecfg.F2D.
DataTransTrig.Co
ng
Number of Failed
F2D State
Transitions
Triggered by Data
Transmission
Requirements in
Congestion
Scenarios for Cell
BSC6900
V900R016C00

1267
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429049
VS.AttRecfg.P2D.D
ataTransTrig
Number of P2D State

Transition Attempts
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429050
VS.AttRecfg.P2H.
DataTransTrig
Number of P2H State

Transition Attempts
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429051
VS.AttRecfg.P2E.D
ataTransTrig
Number of P2E State

Transition Attempts
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429052
VS.SuccRecfg.P2D.
DataTransTrig
Number of
Transitions
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429053
VS.SuccRecfg.P2H.
DataTransTrig
Number of
Successful P2H State
Transitions
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429054
VS.SuccRecfg.P2E.
DataTransTrig
Number of
Successful P2E State
Transitions
Triggered by Data
Transmission
Requirements for
Cell
BSC6900
V900R016C00
73429055
VS.AttRecfg.DCH0
K.Upsizing
Number of Rate
Increase Attempts of
PS DCH 0K UEs for
Cell
BSC6900
V900R016C00

1268
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429056
VS.SuccRecfg.DC
H0K.Upsizing
Number of
Successful Rate
Increases of PS DCH
0K UEs for Cell
BSC6900
V900R016C00
73430564
VS.FailRecfg.DCH
0K.Cong
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
Congestion for Cell
BSC6900
V900R017C10
73430565
VS.FailRecfg.DCH
0K.ULCE.Cong
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
UL CE Congestion
for Cell
BSC6900
V900R017C10
73430566
VS.FailRecfg.DCH
0K.DLCE.Cong
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
DL CE Congestion
for Cell
BSC6900
V900R017C10
73430567
VS.FailRecfg.DCH
0K.Code.Cong
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
Code Congestion for
Cell
BSC6900
V900R017C00
73430568
VS.FailRecfg.DCH
0K.ULpower.Cong
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
UL Power
Congestion for Cell
BSC6900
V900R017C10

1269
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430569
VS.FailRecfg.DCH
0K.DLpower.Cong
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
DL Power
Congestion for Cell
BSC6900
V900R017C10
73430570
VS.FailRecfg.DCH
0K.DLIUBBand.C
ong
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
DL Iub Bandwidth
Congestion for Cell
BSC6900
V900R017C10
73430571
VS.FailRecfg.DCH
0K.ULIUBBand.C
ong
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
UL Iub Bandwidth
Congestion for Cell
BSC6900
V900R017C10
73430572
VS.FailRecfg.DCH
0K.HSUPAUser.Co
ng
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
Max. HSUPA User
Number for Cell
BSC6900
V900R017C10
73430573
VS.FailRecfg.DCH
0K.HSDPAUser.Co
ng
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
Max. HSDPA User
Number for Cell
BSC6900
V900R017C10
73430574
VS.FailRecfg.DCH
0K.UuFail
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
a Uu Configuration
Failure During RB
Reconfiguration for
Cell
BSC6900
V900R017C10

1270
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430575
VS.FailRecfg.DCH
0K.RBInvCfg
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
the Reception of an
Invalid
Configuration
Reason During RB
Reconfiguration for
Cell
BSC6900
V900R017C10
73430576
VS.FailRecfg.DCH
0K.RBCfgUnsupp
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
Unsupported
Configuration
During RB
Reconfiguration for
Cell
BSC6900
V900R017C10
73430577
VS.FailRecfg.DCH
0K.PhyChFail
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
a Physical Channel
Failure During RB
Reconfiguration for
Cell
BSC6900
V900R017C10
73430578
VS.FailRecfg.DCH
0K.UuNoReply
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
Uu No Response
During RB
Reconfiguration for
Cell
BSC6900
V900R017C10

1271
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430579
VS.FailRecfg.DCH
0K.SRBReset
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
an SRB Reset During
RB Reconfiguration
for Cell
BSC6900
V900R017C10
73430580
VS.FailRecfg.DCH
0K.CellUpd
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
the Initiation of a
Cell Update
Procedure During
RB Reconfiguration
for Cell
BSC6900
V900R017C10
73430581
VS.FailRecfg.DCH
0K.IubFail
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
an RL
Reconfiguration
Failure During RB
Reconfiguration for
Cell
BSC6900
V900R017C10
73430582
VS.FailRecfg.DCH
0K.IubAAL2Fail
Number of Times
Channel
Reconfigurations of
PS UEs Carried on
0K DCH Fail Due to
an Iub Transport
Bearer Setup Failure
During RB
Reconfiguration for
Cell
BSC6900
V900R017C10
73430583
VS.AttRecfg.DCH0
K.HSDPA.Upsizing
Number of DL
Channel
Reconfiguration
Attempts from 0K
DCH to HS-DSCH
for PS UEs for Cell
BSC6900
V900R017C10

1272
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430584
VS.AttRecfg.DCH0
K.HSDPA.DC.Upsizing
Number of DL
Channel
Reconfiguration
Attempts from 0K
DCH to DC HSDSCH for PS UEs
for Cell
BSC6900
V900R017C10
73430585
VS.AttRecfg.DCH0
K.HSDPA.
64QAM.Upsizing
Number of DL
Channel
Reconfiguration
Attempts from 0K
DCH to HS-DSCH
(64QAM) for PS
UEs for Cell
BSC6900
V900R017C10
73430586
VS.SuccRecfg.DC
H0K.HSDPA.Upsiz
ing
Number of Times DL
Channels of PS UEs
Are Successfully
Reconfigured from
0K DCH to HSDSCH for Cell
BSC6900
V900R017C10
73430587
VS.SuccRecfg.DC
H0K.HSDPA.DC.U
psizing
Number of Times DL
Channels of PS UEs
Are Successfully
Reconfigured from
0K DCH to DC HSDSCH for Cell
BSC6900
V900R017C10
73430588
VS.SuccRecfg.DC
H0K.HSDPA.
64QAM.Upsizing
Number of Times DL
Channels of PS UEs
Are Successfully
Reconfigured from
0K DCH to HSDSCH (64QAM) for
Cell
BSC6900
V900R017C10
73430589
VS.AttRecfg.DCH0
K.HSUPA.Upsizing
Number of UL
Channel
Reconfiguration
Attempts from 0K
DCH to E-DCH for
PS UEs for Cell
BSC6900
V900R017C10

1273
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430590
VS.SuccRecfg.DC
H0K.HSUPA.Upsiz
ing
Number of Times the

UL Channels for PS
UEs Is Successfully
Reconfigured from
0K DCH to E-DCH
for Cell
BSC6900
V900R017C10
Counter
Sub Counter
VS.FailRecfg.DCH0K.Cong
VS.FailRecfg.DCH0K.ULCE.Cong
VS.FailRecfg.DCH0K.DLCE.Cong
VS.FailRecfg.DCH0K.Code.Cong
VS.FailRecfg.DCH0K.ULpower.Cong
VS.FailRecfg.DCH0K.DLpower.Cong
VS.FailRecfg.DCH0K.DLIUBBand.Cong
VS.FailRecfg.DCH0K.ULIUBBand.Cong
VS.FailRecfg.DCH0K.HSUPAUser.Cong
VS.FailRecfg.DCH0K.HSDPAUser.Cong
VS.FailRecfg.DCH0K.UuFail
VS.FailRecfg.DCH0K.RBInvCfg
VS.FailRecfg.DCH0K.RBCfgUnsupp
VS.FailRecfg.DCH0K.PhyChFail
VS.FailRecfg.DCH0K.UuNoReply
Number of F2D State Transition Attempts Triggered by Data Transmission

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73429039
VS.AttRecfg.F2D.DataTransTrig
Number of F2D State

Transition Attempts
Triggered by Data
for Cell

1274
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73429040
VS.AttRecfg.F2H.DataTransTrig
Number of F2H State

Transition Attempts
Triggered by Data
for Cell
73429041
VS.AttRecfg.F2E.DataTransTrig
Number of F2E State

Transition Attempts
Triggered by Data
for Cell
Description
This counter provides the number of state transition attempts from CELL_FACH to CELL_DCH
(DCH/HS-DSCH/E-DCH) in a cell. For multi-carrier HSDPA or HSUPA users, this counter is
measured only in the primary cell. This counter includes neither the repeated state transition
attempts nor the state transition attempts that are canceled due to procedure concurrency. The
preceding counters comply with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered at point A in figure 1 when the RNC determines to switch the UE
from the CELL_FACH state to the CELL_DCH state due to data transmission requirements.
This counter is measured in the best cell based on the UE's channel type (DCH/HS-DSCH/EDCH) after the reconfiguration.
The RNC triggers this state transition in both of the following scenarios:
The amount of traffic to transmit in the uplink or downlink exceeds a certain threshold;
the type of PS service is identified (for example, web page browsing) and state transition is
triggered to improve service experience.
This counter excludes the repeated state transition attempts. The repeated state transition
attempts are reflected by the VS.AttRecfg.Rep.F2D.DataTransTrig,
VS.AttRecfg.Rep.F2H.DataTransTrig, and VS.AttRecfg.Rep.F2E.DataTransTrig counters.
This counter also excludes the state transition attempts that are canceled due to procedure
concurrency in the following scenarios:
Scenario 1: The RNC cancels the state transition if it receives a CELL UPDATE message with
the cause value cell reselection, re-entering service area, periodic cell update, or unrecoverable
RLC error from the UE during the state transition. The RNC waits until and cell update procedure
is complete and then initiates the state transition procedure.
Scenario 2: The RNC cancels the state transition if the UE reselects an inter-RAT cell or if the
CN or UE releases the RRC connection. When the UE reselects an inter-RAT cell, the CN sends
an SRNS CONTEXT REQUEST message to the RNC.
Issue 03 (2015-06-30)

1275
BSC6900 UMTS
Figure 1-539 Procedure of state transition from CELL_FACH to CELL_DCH
Formula
None
Unit
None
Issue 03 (2015-06-30)

1276
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRecfg.F2D.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
VS.AttRecfg.F2H.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061111

VS.AttRecfg.F2E.DataTransTrig
WRFD-021101
WRFD-01061208
Dynamic Channel
(DCCC)
HSUPA DCCC
Number of P2D State Transition Attempts Triggered by Data Transmission

Counters
Counter ID
Counter Name
Counter Description
73429049
VS.AttRecfg.P2D.DataTransTrig
Number of P2D State

Transition Attempts
Triggered by Data
for Cell
73429050
VS.AttRecfg.P2H.DataTransTrig
Number of P2H State

Transition Attempts
Triggered by Data
for Cell
73429051
VS.AttRecfg.P2E.DataTransTrig
Number of P2E State

Transition Attempts
Triggered by Data
for Cell
Description
This counter provides the number of state transition attempts from CELL_PCH and URA_PCH
to CELL_DCH (DCH/HS-DSCH/E-DCH) in a cell. For multi-carrier HSDPA or HSUPA users,
this counter is measured only in the primary cell. The preceding counters comply with section
Issue 03 (2015-06-30)

1277
BSC6900 UMTS
Measurement point
The measurement is triggered at point A in figure 3 when the RNC determines to switch the UE
from the CELL_PCH or URA_PCH state to the CELL_DCH state (DCH/HS-DSCH/E-DCH)
upon receiving a CELL UPDATE message from the UE with the cause value "uplink data
transmission" or "paging response" and without the "Establishment cause" IE. This counter is
measured in the best cell.
Note:
1. If the UE retransmits the CELL UPDATE message, only the state transition triggered by the
last CELL UPDATE message is measured.
2. This counter is not measured if the UE reselects an inter-RAT cell or if the CN releases the
UE's RRC connection. When the UE reselects an inter-RAT cell, the CN sends an SRNS
CONTEXT REQUEST message to the RNC.
3. If the state transition is triggered by the establishment of a new service (CS RAB or PS RAB)
and the cause value contained in the CELL UPDATE message is "uplink data transmission" or
"paging response", this counter is not measured even if the CELL UPDATE message does not
contain the "Establishment cause" IE.
Issue 03 (2015-06-30)

1278
BSC6900 UMTS
Figure 1-540 Procedure of state transition from CELL_PCH to CELL_DCH
Formula
None
Unit
None
Issue 03 (2015-06-30)

1279
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRecfg.P2D.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
VS.AttRecfg.P2H.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061111

VS.AttRecfg.P2E.DataTransTrig
WRFD-021101
WRFD-01061208
Dynamic Channel
(DCCC)
HSUPA DCCC
Number of Repeated F2D State Transition Attempts Triggered by Data

Transmission Requirements for Cell
Counters
Counter ID
Counter Name
Counter Description
73429045
VS.AttRecfg.Rep.F2D.DataTransTrig
Number of Repeated F2D

State Transition Attempts
Triggered by Data
for Cell
73429046
VS.AttRecfg.Rep.F2H.DataTransTrig
Number of Repeated F2H

Triggered by Data
for Cell
73429047
VS.AttRecfg.Rep.F2E.DataTransTrig
Number of Repeated F2E

Triggered by Data
for Cell
Description
This counter provides the number of repeated and failed attempts initiated by UEs in the
CELL_FACH state to switch to the CELL_DCH state (DCH/HS-DSCH/E-DCH) in a cell. The
RNC may repeatedly request UEs that stay in the CELL_FACH state due to congestion or
Issue 03 (2015-06-30)

1280
BSC6900 UMTS
procedure rollback to switch to the CELL_DCH state. The preceding counters comply with
section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A in figure 1. When the RNC determines to switch a UE
in the CELL_FACH state to the CELL_DCH state due to data transmission requirements, the
UE may remain in the CELL_FACH state due do an admission failure or channel reconfiguration
failure. If the RNC subsequently initiates a second request to switch the UE to the CELL_DCH
state and the UE remains in the CELL_FACH state due to an admission failure or channel
reconfiguration failure, this counter is measured in the best cell when the second state transition
request is initiated.
Figure 1-541 Procedure of repeat state transition from CELL_FACH to CELL_DCH
Issue 03 (2015-06-30)

1281
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRecfg.Rep.F2D.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
VS.AttRecfg.Rep.F2H.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061111

VS.AttRecfg.Rep.F2E.DataTransTrig
WRFD-021101
WRFD-01061208
Dynamic Channel
(DCCC)
HSUPA DCCC
Number of Rate Increase Attempts of PS DCH 0K UEs for Cell

Counters
Counter ID
Counter Name
Counter Description
73429055
VS.AttRecfg.DCH0K.Upsizing
Number of Rate Increase

Attempts of PS DCH 0K UEs
for Cell
Description
This counter measures the number of times that PS DCH 0 kbit/s UEs attempt to increase their
data rates through a DCCC procedure in the best cell.This counter complies with section "8.2.2
Measurement point
As shown by point A in the following figure, the measurement is triggered in the best cell when
the RNC determines to increase the UE data rate through a DCCC procedure if the UE's service
is carried on DCH 0 kbit/s. This counter does not include the number of rate increase reattempts
of PS DCH 0 kbit/s UEs.
Issue 03 (2015-06-30)

1282
BSC6900 UMTS
Figure 1-542 PS DCH 0 kbit/s UEs increase data rates through DCCC procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AttRecfg.DCH0K.Upsizing
WRFD-021101
Dynamic Channel
(DCCC)

1283
BSC6900 UMTS
Number of DL Channel Reconfiguration Attempts from 0K DCH to HS-DSCH for

PS UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73430583
VS.AttRecfg.DCH0K.HSD
PA.Upsizing
Number of DL Channel
Reconfiguration Attempts
from 0K DCH to HS-DSCH
for PS UEs for Cell
73430584
PA.DC.Upsizing
from 0K DCH to DC HSDSCH for PS UEs for Cell
73430585
PA.64QAM.Upsizing
(64QAM) for PS UEs for
Cell
Description
These counters provide the number of DL channel reconfiguration attempts from the 0 kbit/s
DCH to the HS-DSCH for PS UEs in a cell. The HS-DSCH can use different techniques such
as 64QAM and DC-HSDPA. For multi-carrier HSDPA users, this counter is measured only in
the primary cell.
Measurement point
The measurement is triggered at point A in figure 1. The RNC determines whether a UE carried
on the 0 kbit/s DCH requires rate increase through channel reconfiguration and whether the UE
needs to be carried on the DL HS-DSCH after channel reconfiguration. If yes, the preceding
counters are measured in the serving cell based on the technique used by the HS-DSCH.
Issue 03 (2015-06-30)

1284
BSC6900 UMTS
Figure 1-543 Rate increase procedure for a PS UE carried on the 0 kbit/s DCH
Formula
None
Unit
None
Issue 03 (2015-06-30)

1285
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
PA.Upsizing
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061008

PA.DC.Upsizing
WRFD-021101
WRFD-010696
Dynamic Channel
(DCCC)
DC-HSDPA
PA.64QAM.Upsizing
WRFD-021101
WRFD-010683
Dynamic Channel
(DCCC)
Downlink 64QAM
Number of UL Channel Reconfiguration Attempts from 0K DCH to E-DCH for PS

UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73430589
VS.AttRecfg.DCH0K.HSU
PA.Upsizing
Number of UL Channel
from 0K DCH to E-DCH for
PS UEs for Cell
Description
This counter provides the number of UL channel reconfiguration attempts from the 0 kbit/s DCH
to the E-DCH for PS UEs in a cell. For multi-carrier HSUPA UEs, this counter is measured only
in the primary cell.
Measurement point
The measurement is triggered at point A in figure 1. The RNC determines whether a UE carried
on the 0 kbit/s DCH requires rate increase through channel reconfiguration and whether the UE
needs to be carried on the UL E-DCH after channel reconfiguration. If yes, the preceding counter
is measured in the serving cell.
Issue 03 (2015-06-30)

1286
BSC6900 UMTS
Figure 1-544 Rate increase procedure for a PS UE carried on the 0 kbit/s DCH
Formula
None
Unit
None
Issue 03 (2015-06-30)

1287
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRecfg.DCH0K.HSU
PA.Upsizing
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061206

Number of Successful F2D State Transitions Triggered by Data Transmission

Counters
Counter ID
Counter Name
Counter Description
73429042
VS.SuccRecfg.F2D.DataTransTrig
Number of Successful F2D

State Transitions Triggered
by Data Transmission
73429043
VS.SuccRecfg.F2H.DataTransTrig
Number of Successful F2H

73429044
VS.SuccRecfg.F2E.DataTransTrig
Number of Successful F2E

Description
CELL_DCH (DCH/HS-DSCH/E-DCH) in a cell.The preceding counters comply with section
Measurement point
The measurement is triggered at point B in figure 1 when the RNC successfully receives a
RADIO BEARER RECONFIGURATION COMPLETE message from the UE after the RNC
determines to switch the UE from the CELL_FACH state to the CELL_DCH state due to data
transmission requirements. This counter is measured in the best cell based on the UE's channel
type (DCH/HS-DSCH/E-DCH) after the reconfiguration.
Issue 03 (2015-06-30)

1288
BSC6900 UMTS
Note: When F2D_PROCEDURE_OPTIMIZATION_SWITCH is set to on, the RNC determines
that a F2D state transition is complete and measures this counter in the following scenario: The
RNC does not receive a RADIO BEARER RECONFIGURATION COMPLETE message from
the UE, and all RLs are normal upon the expiration of the F2D procedure.
Formula
None
Issue 03 (2015-06-30)

1289
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccRecfg.F2D.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
VS.SuccRecfg.F2H.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061111

VS.SuccRecfg.F2E.DataTransTrig
WRFD-021101
WRFD-01061208
Dynamic Channel
(DCCC)
HSUPA DCCC
Number of Successful P2D State Transitions Triggered by Data Transmission

Counters
Counter ID
Counter Name
Counter Description
73429052
VS.SuccRecfg.P2D.DataTransTrig

73429053
VS.SuccRecfg.P2H.DataTransTrig
Number of Successful P2H

73429054
VS.SuccRecfg.P2E.DataTransTrig
Number of Successful P2E

Description
This counter provides the number of successful state transitions from CELL_PCH and
URA_PCH to CELL_DCH (DCH/HS-DSCH/E-DCH) in a cell. For multi-carrier HSDPA or
Issue 03 (2015-06-30)

1290
BSC6900 UMTS
HSUPA users, this counter is measured only in the primary cell. The preceding counters comply
with section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point B in figure 1 when the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message in the following scenario:
The RNC receives from the UE in the CELL_PCH or URA_PCH state a CELL UPDATE
message with the cause value "uplink data transmission" or "paging response" and without the
"Establishment cause" IE. And The RNC determines to switch the UE to the CELL_DCH state
(DCH/HS-DSCH/E-DCH). This counter is measured in the best cell.
Note:
If the state transition is triggered by the establishment of a new service (CS RAB or PS RAB)
and the cause value contained in the CELL UPDATE message is "uplink data transmission" or
"paging response", this counter is not measured even if the CELL UPDATE message does not
contain the "Establishment cause" IE.
Issue 03 (2015-06-30)

1291
BSC6900 UMTS
Figure 1-546 Procedure of state transition from CELL_PCH to CELL_DCH
Formula
None
Unit
None
Issue 03 (2015-06-30)

1292
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccRecfg.P2D.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
VS.SuccRecfg.P2H.DataTransTrig
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061111

VS.SuccRecfg.P2E.DataTransTrig
WRFD-021101
WRFD-01061208
Dynamic Channel
(DCCC)
HSUPA DCCC
Number of Successful Rate Increases of PS DCH 0K UEs for Cell

Counters
Counter ID
Counter Name
Counter Description
73429056
VS.SuccRecfg.DCH0K.Upsizing
Number of Successful Rate

Increases of PS DCH 0K UEs
for Cell
Description
This counter measures the number of times that PS DCH 0 kbit/s UEs successfully increase their
data rates through a DCCC procedure in the best cell.This counter complies with section "8.2.2
Measurement point
As shown by point B in the following figure, if the UE's service is carried on DCH 0 kbit/s, and
the RNC determines to increase the UE data rate through a DCCC procedure and sends an RB
reconfiguration message to the UE. The measurement is triggered in the best cell when the RNC
receives an RB reconfiguration complete message from the UE. This counter includes the
number of successful DCCC rate increases through link reestablishment.
Issue 03 (2015-06-30)

1293
BSC6900 UMTS
Figure 1-547 PS DCH 0 kbit/s UEs increase data rates through DCCC procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SuccRecfg.DCH0K.Upsizing
WRFD-021101
Dynamic Channel
(DCCC)

1294
BSC6900 UMTS
Number of Times DL Channels of PS UEs Are Successfully Reconfigured from 0K

DCH to HS-DSCH for Cell
Counters
Counter ID
Counter Name
Counter Description
73430586
VS.SuccRecfg.DCH0K.HS
DPA.Upsizing
Number of Times DL
Channels of PS UEs Are
Successfully Reconfigured
for Cell
73430587
DPA.DC.Upsizing
Number of Times DL
from 0K DCH to DC HSDSCH for Cell
73430588
DPA.64QAM.Upsizing
Number of Times DL
(64QAM) for Cell
Description
These counters provide the number of times DL channels of PS UEs are successfully
reconfigured from the 0 kbit/s DCH to the HS-DSCH in a cell. The HS-DSCH can use different
techniques, such as 64QAM and DC-HSDPA. For multi-carrier HSDPA UEs, this counter is
measured only in the primary cell.
Measurement point
The measurement is triggered at point B in figure 1. The RNC determines to increase the rate
of a PS UE carried on the 0 kbit/s DCH through dynamic channel configuration control (DCCC)
and sends an RB reconfiguration message to the UE. Upon receiving a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE, the RNC measures the preceding
counters based on the techniques used by the HS-DSCH if the UE is carried on the HS-DSCH
in the downlink.
Issue 03 (2015-06-30)

1295
BSC6900 UMTS
Figure 1-548 Successful channel reconfiguration for PS UEs carried on the 0 kbit/s DCH
Formula
None
Unit
None
Issue 03 (2015-06-30)

1296
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
DPA.Upsizing
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061008

DPA.DC.Upsizing
WRFD-021101
WRFD-010696
Dynamic Channel
(DCCC)
DC-HSDPA
DPA.64QAM.Upsizing
WRFD-021101
WRFD-010683
Dynamic Channel
(DCCC)
Downlink 64QAM
Number of Times the UL Channels for PS UEs Is Successfully Reconfigured from

0K DCH to E-DCH for Cell
Counters
Counter ID
Counter Name
Counter Description
73430590
UPA.Upsizing

Channels for PS UEs Is
from 0K DCH to E-DCH for
Cell
Description
This counter provides the number of times the UL channels of PS UEs are successfully
reconfigured from the 0 kbit/s DCH to the E-DCH in a cell. For multi-carrier HSUPA users, this
counter is measured only in the primary cell.
Measurement point
The measurement is triggered at point B in figure 1. The RNC determines to increase the rate
of a PS UE carried on the 0 kbit/s DCH through dynamic channel configuration control (DCCC)
and sends an RB reconfiguration message to the UE. Upon receiving a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE, the RNC measures this counter if
the UE is carried on the E-DCH in the uplink.
Issue 03 (2015-06-30)

1297
BSC6900 UMTS
Figure 1-549 Successful channel reconfiguration for PS UEs carried on the 0 kbit/s DCH
Formula
None
Unit
None
Issue 03 (2015-06-30)

1298
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
UPA.Upsizing
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061206

Number of Failed F2D State Transitions Triggered by Data Transmission

Requirements in Congestion Scenarios for Cell
Counters
Counter ID
Counter Name
Counter Description
73429048
VS.FailRecfg.F2D.DataTran
sTrig.Cong
Number of Failed F2D State

Transitions Triggered by
Data Transmission
Requirements in Congestion
Scenarios for Cell
Description
This counter provides the number of failed state transitions from CELL_FACH to CELL_DCH
caused by congestion in a cell. It excludes the repeated state transition failures. This counter
complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A in figure 1 when the state transition from CELL_FACH
to CELL_DCH triggered by data transmission requirements fails due to radio resource
congestion.
This counter excludes the repeated state transition failures caused by congestion.
Issue 03 (2015-06-30)

1299
BSC6900 UMTS
Formula
None
Unit
None
Issue 03 (2015-06-30)

1300
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.FailRecfg.F2D.DataTran
sTrig.Cong
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-01061111
WRFD-01061208

HSUPA DCCC
Number of Times Channel Reconfigurations of PS UEs Carried on 0K DCH Fail

Due to Congestion for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430564
Number of Times Channel

Reconfigurations of PS UEs
Carried on 0K DCH Fail Due
to Congestion for Cell
73430565
VS.FailRecfg.DCH0K.ULC
E.Cong

to UL CE Congestion for Cell
73430566
VS.FailRecfg.DCH0K.DLC
E.Cong

to DL CE Congestion for Cell
73430567
VS.FailRecfg.DCH0K.Code
.Cong

to Code Congestion for Cell
73430568
VS.FailRecfg.DCH0K.ULp
ower.Cong

to UL Power Congestion for
Cell
73430569
VS.FailRecfg.DCH0K.DLp
ower.Cong

to DL Power Congestion for
Cell

1301
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73430570
VS.FailRecfg.DCH0K.DLI
UBBand.Cong

to DL Iub Bandwidth
Congestion for Cell
73430571
VS.FailRecfg.DCH0K.ULI
UBBand.Cong

to UL Iub Bandwidth
Congestion for Cell
73430572
VS.FailRecfg.DCH0K.HSU
PAUser.Cong

to Max. HSUPA User
Number for Cell
73430573
VS.FailRecfg.DCH0K.HSD
PAUser.Cong

to Max. HSDPA User
Number for Cell
Description
These counters provide the number of times channel reconfigurations of PS UEs carried on the
0 kbit/s DCH fail due to different congestion reasons in the best cell. If congestion occurs in
both the uplink and downlink, only the counter for downlink congestion is measured. For
example, when a channel reconfiguration fails due to congestion in both the uplink and downlink
power resources, the RNC measures only the VS.FailRecfg.DCH0K.DLpower.Cong counter.
Measurement point
The measurement is triggered at point A in figure 1. For a data increase request initiated by a
PS UE whose BE service is carried on the DCH and whose data rate is 0 kbit/s, the RNC
determines whether the data increase request is triggered by a 4A event. If yes, the RNC performs
admission control on the UE. If the admission control fails, the RNC measures the preceding
counters in the best cell based on the resource type causing the admission failure.
Issue 03 (2015-06-30)

1302
BSC6900 UMTS
Figure 1-551 Failed channel reconfiguration of a PS UE carried on the 0 kbit/s DCH due to an
admission failure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.ULC
E.Cong
WRFD-021101
Dynamic Channel
(DCCC)

1303
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.FailRecfg.DCH0K.DLC
E.Cong
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.Code
.Cong
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.ULp
ower.Cong
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.DLp
ower.Cong
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.DLI
UBBand.Cong
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.ULI
UBBand.Cong
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.HSU
PAUser.Cong
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.HSD
PAUser.Cong
WRFD-021101
Dynamic Channel
(DCCC)

Due to an RL Reconfiguration Failure During RB Reconfiguration for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430581

to an RL Reconfiguration
Failure During RB

1304
BSC6900 UMTS
Description
This counter provides the number of times the channel reconfigurations of PS UEs carried on
the 0 kbit/s DCH fail due to an RL reconfiguration failure in the best cell. Possible causes of the
RL reconfiguration failure can be any of the following: 1.NodeB response timeout 2.Reception
of the RL reconfiguration failure message 3.RNC receiving a RADIO LINK FAIL
INDICATION message from the NodeB without a subsequent RADIO LINK RESTORE
INDICATION message
Measurement point
The measurement is triggered at point A in figure 1. After determining to perform channel
reconfiguration for a PS UE carried on the 0 kbit/s DCH, the RNC applies for related radio
resources and then initiates an RL establishment or reconfiguration procedure. If the RNC
receives a RADIO LINK RECONFIGURATION FAILURE message from the NodeB after
sending, for example, a RADIO LINK RECONFIGURATION PREPARE message to the
NodeB and if the channel reconfiguration fails, this counter is measured in the best cell. For
details about the cause values in the RADIO LINK RECONFIGURATION FAILURE message,
see section 9.2.1.6 in 3GPP TS 25.433. The RL establishment failures caused by CE congestion
are measured by congestion-related counters and therefore are not measured by this counter.
RL reconfiguration failure
Issue 03 (2015-06-30)

1305
BSC6900 UMTS

resources and then initiates an RL establishment or reconfiguration procedure. If the RNC, for
example, sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB but
does not receive a RADIO LINK RECONFIGURATION READY message from the NodeB
and if the channel reconfiguration fails, this counter is measured in the best cell.
Figure 1-553 Failed channel reconfiguration of a PS UE carried on the 0 kbit/s DCH due to
NodeB response timeout in RL reconfiguration

resources and then initiates an RL establishment or reconfiguration procedure. If the RNC
receives a RADIO LINK FAILURE INDICATION message from the NodeB after sending a
RADIO LINK RECONFIGURATION COMMIT message to the NodeB, the RNC starts a timer
to wait for a RADIO LINK RESTORE INDICATION message from the NodeB. If the RNC
does not receive this message until the time expires, the channel reconfiguration fails, and this
counter is measured in the best cell. In figure 3, the RADIO LINK RECONFIGURATION
COMMIT message is subsequent to a RADIO LINK RECONFIGURATION PREPARE
message, which is used as an example.
Issue 03 (2015-06-30)

1306
BSC6900 UMTS
RL synchronization failure
Formula
None
Unit
None
Issue 03 (2015-06-30)

1307
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-021101
Dynamic Channel
(DCCC)

Due to an Iub Transport Bearer Setup Failure During RB Reconfiguration for Cell
Counters
Counter ID
Counter Name
Counter Description
73430582
VS.FailRecfg.DCH0K.IubA
AL2Fail

to an Iub Transport Bearer
Setup Failure During RB
Description
This counter provides the number of times the channel reconfigurations of PS UEs carried on
the 0 kbit/s DCH fail due to a setup failure of the Iub transport bearer in the best cell.
Measurement point
The measurement is triggered at point A in figure 1. If the channel reconfiguration of a PS BE
carried on the 0 kbit/s DCH fails due to the setup failure of an AAL2 transport bearer over the
Iub interface, this counter is measured in the best cell.
Issue 03 (2015-06-30)

1308
BSC6900 UMTS
Figure 1-555 Failed channel reconfiguration of a PS BE carried on the 0 kbit/s DCH due to an
AAL2 transport bearer setup failure over the Iub interface
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.FailRecfg.DCH0K.IubA
AL2Fail
WRFD-021101
Dynamic Channel
(DCCC)

1309
BSC6900 UMTS

Due to a Uu Configuration Failure During RB Reconfiguration for Cell
Counters
Counter ID
Counter Name
Counter Description
73430574

to a Uu Configuration Failure
for Cell
73430575
VS.FailRecfg.DCH0K.RBIn
vCfg

to the Reception of an Invalid
Configuration Reason
for Cell
73430576
VS.FailRecfg.DCH0K.RBC
fgUnsupp

to Unsupported
Configuration During RB
73430577
VS.FailRecfg.DCH0K.PhyC
hFail

to a Physical Channel Failure
for Cell
73430578

to Uu No Response During
RB Reconfiguration for Cell
Description
These counters provide the number of times the channel reconfigurations of PS UEs carried on
the 0 kbit/s DCH fail due to Uu reconfiguration failures in the best cell. Uu reconfiguration
failures include no response from the UE and a failure response from the UE. For details about
the failure response from the UE, see section 10.3.3.14 in 3GPP TS 25.331.
Issue 03 (2015-06-30)

1310
BSC6900 UMTS
Measurement point
The measurement is triggered at point A in figure 1. After determining to increase the rate of a
PS UE carried on the 0 kbit/s DCH by channel reconfiguration, the RNC applies for related radio
resources and initiates a Uu reconfiguration procedure. If the RNC receives a RADIO BEARER
RECONFIGURATION FAILURE message from the UE, this counter is measured in the best
cell. For details about the cause values contained in the RADIO BEARER
RECONFIGURATION FAILURE message, see section "10.3.3.14 Failure cause and error
information" in 3GPP TS 25.331.
Figure 1-556 Failed channel reconfiguration of a PS BE carried on the 0 kbit/s DCH due to a
Uu reconfiguration failure
PS UE carried on the 0 kbit/s DCH by channel reconfiguration, the RNC applies for related radio
resources and initiates a Uu reconfiguration procedure. If the RNC does not receive a RADIO
BEARER RECONFIGURATION COMPLETE message from the UE within a specified period
of time, this counter is measured in the best cell.
Issue 03 (2015-06-30)

1311
BSC6900 UMTS
Figure 1-557 Failed channel reconfiguration of a PS BE carried on the 0 kbit/s DCH due to Uu
interface timeout
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.RBIn
vCfg
WRFD-021101
Dynamic Channel
(DCCC)

1312
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.FailRecfg.DCH0K.RBC
fgUnsupp
WRFD-021101
Dynamic Channel
(DCCC)
VS.FailRecfg.DCH0K.PhyC
hFail
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-021101
Dynamic Channel
(DCCC)

Due to an SRB Reset During RB Reconfiguration for Cell
Counters
Counter ID
Counter Name
Counter Description
73430579
VS.FailRecfg.DCH0K.SRB
Reset

to an SRB Reset During RB
Description
This counter provides the number of times channel reconfigurations of PS UEs carried on the 0
kbit/s DCH fail due to an SRB reset in the best cell. This counter is measured only when the UE
has newly established PS BE services on the DCH and the rate of the PS BE services is 0 kbit/
s.
Measurement point
PS UE carried on the 0 kbit/s DCH through channel reconfiguration, the RNC applies for related
radio resources and reconfigures a Uu link for the UE. If an SRB reset occurs after the RNC
sends a RADIO BEARER RECONFIGURATION PREPARE message to the UE and
consequently the channel reconfiguration fails, this counter is measured in the best cell.
Issue 03 (2015-06-30)

1313
BSC6900 UMTS
Figure 1-558 Failed channel reconfiguration of a PS BE carried on the 0 kbit/s DCH due to an
SRB reset failure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.FailRecfg.DCH0K.SRB
Reset
WRFD-021101
Dynamic Channel
(DCCC)

1314
BSC6900 UMTS

Due to the Initiation of a Cell Update Procedure During RB Reconfiguration for
Cell
Counters
Counter ID
Counter Name
Counter Description
73430580

to the Initiation of a Cell
Update Procedure During RB
Description
This counter provides the number of times channel reconfigurations of PS UEs carried on the 0
kbit/s DCH fail due to the initiation of a cell update procedure during RB reconfiguration in the
best cell.
Measurement point
The measurement is triggered at point A in figure 1. After deciding to increase the rate of a PS
UE carried on the 0 kbit/s DCH through channel reconfiguration, the RNC applies for related
radio resources and reconfigures a Uu link for the UE. If the UE initiates a cell update procedure
during RB reconfiguration, the channel reconfiguration fails. This counter is measured in the
best cell.
Issue 03 (2015-06-30)

1315
BSC6900 UMTS
Figure 1-559 Failed channel reconfiguration for a PS UE carried on the 0 kbit/s DCH due to the
initiation of a cell update procedure during RB reconfiguration
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-021101
Dynamic Channel
(DCCC)

1316
BSC6900 UMTS
1.12.9 Compressed Mode Measurement <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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194881
VS.CM.ULSF2.Act
.Att
Number of Uplink
SF-2 Compression
Mode Activation
Requests for Cell
Earlier than
BSC6900
V900R011
67194882
VS.CM.ULHLS.Ac
t.Att
Number of Uplink
HLS Compression
Mode Activation
Requests for Cell
Earlier than
BSC6900
V900R011
67194883
VS.CM.ULSF2.Act
.Fail
Number of Uplink
SF-2 Compression
Mode Activation
Failures for Cell
Earlier than
BSC6900
V900R011
67194884
VS.CM.ULHLS.Ac
t.Fail
Number of Uplink
HLS Compression
Mode Activation
Failures for Cell
Earlier than
BSC6900
V900R011
67194885
VS.CM.DLSF2.Act
.Att
Number of Downlink
SF-2 Compression
Mode Activation
Requests for Cell
Earlier than
BSC6900
V900R011
67194886
VS.CM.DLHLS.Ac
t.Att
Number of Downlink
HLS Compression
Mode Activation
Requests for Cell
Earlier than
BSC6900
V900R011
67194887
VS.CM.DLSF2.Act
.Fail
Number of Downlink
SF-2 Compression
Mode Activation
Failures for Cell
Earlier than
BSC6900
V900R011
67194888
VS.CM.DLHLS.Ac
t.Fail
Number of Downlink
HLS Compression
Mode Activation
Failures for Cell
Earlier than
BSC6900
V900R011

1317
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73444434
VS.CM.DLSF2.Alt
ScramCode.UE.Me
an
Average Number of
Ues with
Sf2AltScramCode in
a cell
BSC6900
V900R016C00
73428665
VS.CM.DLSF2.Alt
ScramCode.UE.Ma
x
Max Number Of Ues

with
Sf2AltScramCode In
a Cell
BSC6900
V900R016C00
73444435
VS.CM.DLSF2.UE.
Mean
Average Number Of
Ues with Sf2 In a Cell
BSC6900
V900R016C00
73428668
VS.CM.DLSF2.UE.
Max
Max Number Of Ues

with Sf2 In a Cell
BSC6900
V900R016C00
None
Number of Up Link SF-2 Compressed Mode Activation Attempts

Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)

1318
BSC6900 UMTS
Figure 1-560 Flow chart of Measurement of Compressed Mode
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.ULSF2.Act.Att
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Up Link HLS Compressed Mode Activation Attempts

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194882
VS.CM.ULHLS.Act.Att
Number of Uplink HLS

Compression Mode

1319
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.ULHLS.Act.Att
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1320
BSC6900 UMTS
Number of Up Link SF-2 Compressed Mode Activation Fails

Counters
Counter ID
Counter Name
Counter Description
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.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1321
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.ULSF2.Act.Fail
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Up Link HLS Compressed Mode Activation Fails

Counters
Counter ID
Counter Name
Counter Description
67194884
VS.CM.ULHLS.Act.Fail
Number of Uplink HLS

Compression Mode
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
Issue 03 (2015-06-30)

1322
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.ULHLS.Act.Fail
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Down Link SF-2 Compressed Mode Activation Attempts

Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)

1323
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.DLSF2.Act.Att
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Down Link HLS Compressed Mode Activation Attempts

Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)

1324
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.DLHLS.Act.Att
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Down Link SF-2 Compressed Mode Activation Fails

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194887
VS.CM.DLSF2.Act.Fail
Number of Downlink SF-2

Compression Mode

1325
BSC6900 UMTS
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
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.DLSF2.Act.Fail
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1326
BSC6900 UMTS
Number of Down Link HLS Compressed Mode Activation Fails

Counters
Counter ID
Counter Name
Counter Description
67194888
VS.CM.DLHLS.Act.Fail
Number of Downlink HLS

Compression Mode
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
Issue 03 (2015-06-30)

1327
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.DLHLS.Act.Fail
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number Of Ues with Sf2AltScramCode In a Cell

Counters
Counter ID
Counter Name
Counter Description
73444434
VS.CM.DLSF2.AltScramCo
de.UE.Mean
Average Number of Ues with

Sf2AltScramCode in a cell
73428665
de.UE.Max
Max Number Of Ues with

Sf2AltScramCode In a Cell
Description
This counter measures the average number and maximum number of users that use the alternative
scrambling code for the compressed mode method "SF/2" in the downlink in a cell.
Measurement point
The RNC takes samples of the number of users that use the alternative scrambling code for the
compressed mode method "SF/2" in the downlink every 5 seconds in a measurement period. At
the end of the measurement period, the RNC obtains the value of this counter by dividing the
accumulated number by the number of sampling times. At the end of the measurement period,
the RNC takes the maximum sample value as the value for this counter.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1328
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
de.UE.Mean
WRFD-020302

Handover Based on
Coverage
WRFD-020303

on Coverage
de.UE.Max
WRFD-020302
WRFD-020303

Handover Based on
Coverage
on Coverage
Number Of Ues with Sf2 In a Cell

Counters
Counter ID
Counter Name
Counter Description
73444435
VS.CM.DLSF2.UE.Mean
Average Number Of Ues

with Sf2 In a Cell
73428668
VS.CM.DLSF2.UE.Max
Max Number Of Ues with

Sf2 In a Cell
Description
This counter measures the average number and maximum number of users that use the
compressed mode method "SF/2" in the downlink in a cell.
Measurement point
The RNC takes samples of the number of UEs that use the compressed mode method "SF/2" in
the RNC obtains the value of this counter by dividing the accumulated number by the number
of sampling times. At the end of the measurement period, the RNC takes the maximum sample
value as the value for this counter.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1329
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CM.DLSF2.UE.Mean
WRFD-020302

Handover Based on
Coverage
WRFD-020303

on Coverage
VS.CM.DLSF2.UE.Max
WRFD-020302
WRFD-020303

Handover Based on
Coverage
on Coverage
1.12.10 CS Service Quality Measurement <per Cell>

(CSService.Cell)
Overview
This function subset provides measurements related to experience of UEs performing CS
services.
Measurements related to experience of UEs performing CS services can be classified into three
types: accessibility, service integrity, and retainability.
1.Measurements related to accessibility consist of the following:
1)Number of CS (including AMR-NB, AMR-WB, and VP) service setup attempts initiated by
the calling party and number of successful attempts
This function subset measures the number of CS service setup attempts and number of successful
CS service setups initiated by UEs that serve as the calling party or called party in the following
states: idle, CELL_DCH, CELL_FACH, CELL_PCH/URA_PCH, redirection-based CSFB, and
handover-based CSFB.
Number of CS service setup attempts and number of successful CS service setups initiated by
UEs that serve as the calling party: When detecting a CS service setup attempt initiated by UEs
in any of the preceding state, the RNC increases the number of CS service setup attempt by one.
If any of the following conditions is met, the RNC determines that the CS service setup is
successful:1.The RNC receives a Direct Transfer (Alerting) message from the CN. 2.After
sending a service request message to the CN, the RNC receives from the CN a Disconnect
message with any of the following cause values: Unassigned (unallocated) number; Operator
determined barring; Normal call clearing; User busy; No user responding; User alerting, no
answer; Call rejected; Number changed; Invalid number format (incomplete number); Normal,
unspecified; Service or option not available, unspecified; Service or option not implemented,
unspecified; or Recovery on timer expiry. For details about these cause values, see 3GPP TS
24.008. 3.After sending a service request message to the CN, the RNC receives from the CN a
connect message, not a Direct Transfer (Alerting) message. 4.After sending a service request
message to the CN, the RNC receives a Disconnect message from the UE before the Direct
Issue 03 (2015-06-30)

1330
BSC6900 UMTS
Transfer (Alerting) message. The UE sends a Disconnect message to the RNC when it hangs up
the call.
Note
(1) The measurement is not triggered for RRC CONNECTION REQUEST or CELL UPDATE
messages retransmitted by UEs.
(2) These counters do not measure RRC CONNECTION REQUEST messages that are rejected
due to service-steering-based redirection, distance-based (inter-RAT and inter-frequency)
redirection, weak-coverage-based redirection, or Macro & Micro joint inter-frequency
redirection. These counters do not measure RRC CONNECTION REQUEST messages that are
discarded due to flow control.
(3) The RNC measures the counter that provides the number of CS service setup attempts
initiated by UEs in idle mode if UEs in idle mode initiate an Iu connection setup procedure in
the PS domain after setting up their RRC connections.
(4) The RNC does not measure the counter that provides the number of CS service setup attempts
initiated by UEs in the CELL_PCH or URA_PCH state in either of the following scenario:
The UE in the CELL_PCH or URA_PCH state does not send an INITIAL DIRECT TRANSFER
(CM SERVICE REQUEST) or UPLINK DIRECT TRANSFER (CM SERVICE REQUEST)
message to the CS domain of the CN after the cell update procedure is complete.
The INITIAL DIRECT TRANSFER (CM Service Request) or UPLINK DIRECT TRANSFER
(CM Service Request) message contains a cause value other than "mobile originate call
establishment or packet mode connection establishment."
(5) One CS service setup attempt is calculated only into one counter.
2).Average access delay of the AMR-NB and AMR-WB calls and the level of the access delay
2.Measurements related to service integrity consist of the following:
1).Counters not included in the EVQI.CELL function subset
2).Number of the occurrences of garble voice and mute voice during AMR-NB and AMR-WB
calls in this function subset
3.Measurements related to retainability consist of the following:
1).Counters in the RAB.RelAbnormal.Cell function subset
2).Number of AMR-NB and AMR-WB RABs that are abnormally released by the CN
3).Number of times that the voice quality of AMR-NB and AMR-WB calls is considered as poor
before the calls are normally released
Note
(1) A UE is performing redirection-based CSFB if either of the following conditions is met:
(a) The RRC CONNECTION REQUEST message contains the CSFB Indication IE. This IE is
introduced in 3GPP Release 10.
(b) All of the following conditions are met:
The RRC CONNECTION REQUEST message contains V860 but does not contain the Preredirection info IE. The Pre-redirection info IE is introduced in 3GPP Release 10.
Issue 03 (2015-06-30)

1331
BSC6900 UMTS
In the RRC connection setup complete message, the value of the UE radio access capability >
UE multi-mode/multi-RAT capability > Support of E-UTRA FDD IE is
"DoesSupportEUTRAFDD." Alternatively, the value of the Support of E-UTRA TDD IE is
"DoesSupportEUTRATDD."
The RNC starts a timer upon receiving an RRC connection setup complete message. The length
of the timer is 10s. If the CS service is successfully set up before the timer expires, the RRC
Connection Request message contains the cause value "Originating Conversational Call" for the
calling party, and the message contains the cause value "Emergency Call" in the case of an
emergency call.
If neither of the preceding conditions is met, the CS service setup attempt is calculated into the
counter for UEs in idle mode.
(2) A UE is performing handover-based CSFB if either of the following conditions is met:
(a)The RELOCATION REQUET message contains the cause value "CS Fallback triggered."
(b) The RELOCATION REQUEST message contains the CSFB Information IE, and the value
of the IE is CSFB or CSFB High Priority. The preceding IE is an optional IE and is carried in
the network provided by Huawei. If the LTE devices are not from Huawei or the LTE network
does not provide this IE, this CS service setup attempt is calculated into the counter for UEs in
the CELL_FACH or CELL_DCH state.
(3) If a soft handover occurs during CS service setup, the CS service setup attempt is measured
in the best cell where the access succeeds or fails, and the successful CS service setup is measured
in the best cell where the access succeeds.
(4) During the CS RAB setup, if DRD is enabled, the best cell is the cell where the RAB is
successful set up. If the RAB fails to be set up, the best cell is the first target cell for DRD.
Issue 03 (2015-06-30)

1332
BSC6900 UMTS
Figure 1-568 CS service setup procedure for the calling party
Issue 03 (2015-06-30)

1333
BSC6900 UMTS
Measurement points
Description
A1
VS.OrigCSCall.AttEstab.Idle,
VS.OrigCSCall.AttEstab.CSFB.Redir
A2
VS.OrigCSCall.AttEstab.DCH,
VS.OrigCSCall.AttEstab.FACH,
VS.OrigCSCall.AttEstab.CSFB.PSHO
A3
VS.OrigCSCall.AttEstab.PCH
VS.OrigCSCall.SuccEstab.Idle,
VS.OrigCSCall.SuccEstab.CSFB.Redir,
VS.OrigCSCall.SuccEstab.DCH,
VS.OrigCSCall.SuccEstab.FACH,
VS.OrigCSCall.SuccEstab.PCH,
VS.OrigCSCall.SuccEstab.CSFB.PSHO
B1
B2
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427973
VS.SingleRAB.CS
VoicePPC.CSVoiceFrames
Number of Speech
Frames on Which the
CS Voice Precise
Power Control
Feature Takes Effect
for a Single AMR
Service for Cell
BSC6900
V900R016C00

1334
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427974
VS.MultiRAB.CSV
oicePPC.CSVoiceFrames
Number of Speech
Frames on Which the
CS Voice Precise
Power Control
Feature Takes Effect
for Combined
Services for Cell
BSC6900
V900R016C00
73427994
VS.SingleRAB.CS
VoiceTotalFrames
Number of Frames
Involved in a Single
AMR Service for
Cell
BSC6900
V900R016C00
73427995
VS.MultiRAB.CSV
oiceTotalFrames
Number of Frames
Involved in the AMR
Service of Combined
Services for Cell
BSC6900
V900R016C00
73428271
VS.RAB.Rel.AMR
NB.UL.LowQuality
Number of Normally
Released AMR-NB
RABs (Poor Uplink
Voice Quality)
BSC6900
V900R016C00
73428272
VS.RAB.Rel.AMR
NB.DL.LowQuality
Number of Normally
Released AMR-NB
RABs (Poor
Downlink Voice
Quality)
BSC6900
V900R016C00
73428273
VS.RAB.Rel.AMR
WB.UL.LowQualit
y
Number of Normally
Released AMR-WB
RABs (Poor Uplink
Voice Quality)
BSC6900
V900R016C00
73428274
VS.RAB.Rel.AMR
WB.DL.LowQualit
y
Number of Normally
Released AMR-WB
RABs (Poor
Downlink Voice
Quality)
BSC6900
V900R016C00
73428275
VS.AMRNB.ULSil
ent.OccurNum
Number of Times
That Silence Is
Detected in Uplink
for AMR-NB
Services for Cell
BSC6900
V900R016C00

1335
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428276
VS.AMRNB.DLSil
ent.OccurNum
Number of Times
That Silence Is
Detected in
Downlink for AMRNB Services for Cell
BSC6900
V900R016C00
73428277
VS.AMRWB.ULSil
ent.OccurNum
Number of Times
That Silence Is
Detected in Uplink
for AMR-WB
Services for Cell
BSC6900
V900R016C00
73428278
VS.AMRWB.DLSil
ent.OccurNum
Number of Times
That Silence Is
Detected in
Downlink for AMRWB Services for Cell
BSC6900
V900R016C00
73428351
VS.AMRNB.ULGa
rbledVoice.OccurNum
Number of Garbled
Voice Occurrences
on Uplink AMR-NB
Services for Cell
BSC6900
V900R016C00
73428352
VS.AMRNB.DLGa
rbledVoice.OccurNum
Number of Garbled
Voice Occurrences
on Downlink AMRNB Services for Cell
BSC6900
V900R016C00
73428353
VS.AMRWB.ULG
arbledVoice.OccurNum
Number of Garbled
Voice Occurrences
on Uplink AMR-WB
Services for Cell
BSC6900
V900R016C00
73428354
VS.AMRWB.DLG
arbledVoice.OccurNum
Number of Garbled
Voice Occurrences
on Downlink AMRWB Services for Cell
BSC6900
V900R016C00
73428355
VS.AMRNB.ULGa
rbledVoiceCorrect.
Num
Number of
Successful Garbled
Voice Corrections on
Uplink AMR-NB
Services for Cell
BSC6900
V900R016C00
73428356
VS.AMRWB.ULG
arbledVoiceCorrec
t.Num
Number of
Successful Garbled
Voice Corrections on
Uplink AMR-WB
Services for Cell
BSC6900
V900R016C00

1336
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428375
VS.OrigCSCall.Att
Estab.Idle
Number of CS
Service Setup
UEs in Idle Mode for
Cell
BSC6900
V900R016C00
73428376
VS.OrigCSCall.Att
Estab.CSFB.Redir
Number of CS
Service Setup
Redirection-based
CSFB UEs for Cell
BSC6900
V900R016C00
73428377
VS.OrigCSCall.Att
Estab.DCH
Number of CS
Service Setup
UEs in CELL_DCH
State for Cell
BSC6900
V900R016C00
73428378
VS.OrigCSCall.Att
Estab.FACH
Number of CS
Service Setup
UEs in
CELL_FACH State
for Cell
BSC6900
V900R016C00
73428379
VS.OrigCSCall.Att
Estab.PCH
Number of CS
Service Setup
UEs in CELL_PCH/
URA_PCH State for
Cell
BSC6900
V900R016C00
73428380
VS.OrigCSCall.Att
Estab.CSFB.PSHO
Number of CS
Service Setup
Handover-based
CSFB UEs for Cell
BSC6900
V900R016C00
73428381
VS.OrigCSCall.Suc
cEstab.Idle
Number of
Successful CS
Service Setups
Initiated by UEs in
Idle Mode for Cell
BSC6900
V900R016C00
73428382
VS.OrigCSCall.Suc
cEstab.CSFB.Redir
Number of
Successful CS
Service Setups
Initiated by
Redirection-based
CSFB UEs for Cell
BSC6900
V900R016C00

1337
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428383
VS.OrigCSCall.Suc
cEstab.DCH
Number of
Successful CS
Service Setups
Initiated by UEs in
the CELL_DCH
State for Cell
BSC6900
V900R016C00
73428384
VS.OrigCSCall.Suc
cEstab.FACH
Number of
Successful CS
Service Setups
Initiated by UEs in
the CELL_FACH
State for Cell
BSC6900
V900R016C00
73428385
VS.OrigCSCall.Suc
cEstab.PCH
Number of
Successful CS
Service Setups
Initiated by UEs in
the CELL_PCH/
URA_PCH State for
Cell
BSC6900
V900R016C00
73428386
VS.OrigCSCall.Suc
cEstab.CSFB.PSH
O
Number of
Successful CS
Service Setups
Initiated by
Handover-based
CSFB UEs for Cell
BSC6900
V900R016C00
73444350
VS.OrigCall.Estab
MeanTime.AMRN
B.Idle
Average Access
Delay of the AMRNB Calls Initiated by
UEs in Idle Mode for
Cell
BSC6900
V900R016C00
73444355
VS.OrigCall.Estab
MeanTime.AMRN
B.CSFB.Redir
Average Access
UEs in Redirectionbased CSFB for Cell
BSC6900
V900R016C00
73444356
VS.OrigCall.Estab
MeanTime.AMRN
B.DCH
Average Access
UEs in the
CELL_DCH State
for Cell
BSC6900
V900R016C00

1338
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444339
VS.OrigCall.Estab
MeanTime.AMRN
B.FACH
Average Access
UEs in the
CELL_FACH State
for Cell
BSC6900
V900R016C00
73444357
VS.OrigCall.Estab
MeanTime.AMRN
B.PCH
Average Access
UEs in the
CELL_PCH/
URA_PCH State for
Cell
BSC6900
V900R016C00
73444358
VS.OrigCall.Estab
MeanTime.AMRN
B.CSFB.PSHO
Average Access
UEs in Handoverbased CSFB for Cell
BSC6900
V900R016C00
73444351
VS.OrigCall.Estab
MeanTime.AMRN
B
Average Access
UEs for Cell
BSC6900
V900R016C00
73444352
VS.OrigCall.Estab
MeanTime.AMRW
B.Idle
Average Access
Delay of the AMRWB Calls Initiated
by UEs in Idle Mode
for Cell
BSC6900
V900R016C00
73444353
VS.OrigCall.Estab
MeanTime.AMRW
B.DCH
Average Access
by UEs in the
CELL_DCH State
for Cell
BSC6900
V900R016C00
73444354
VS.OrigCall.Estab
MeanTime.AMRW
B.FACH
Average Access
by UEs in the
CELL_FACH State
for Cell
BSC6900
V900R016C00

1339
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444346
VS.OrigCall.Estab
MeanTime.AMRW
B.PCH
Average Access
by UEs in the
CELL_PCH/
URA_PCH State for
Cell
BSC6900
V900R016C00
73444347
VS.OrigCall.Estab
MeanTime.AMRW
B.CSFB.Redir
Average Access
by UEs in
Redirection-based
CSFB for Cell
BSC6900
V900R016C00
73444348
VS.OrigCall.Estab
MeanTime.AMRW
B.CSFB.PSHO
Average Access
by UEs in Handoverbased CSFB for Cell
BSC6900
V900R016C00
73444349
VS.OrigCall.Estab
MeanTime.AMRW
B
Average Access
by UEs for Cell
BSC6900
V900R016C00
73428425
VS.OrigCall.Estab
Delay.Good.Num.A
MRNB
Number of Times
that the Access Delay
of AMR-NB Calls Is
GOOD for Cell
BSC6900
V900R016C00
73428426
VS.OrigCall.Estab
Delay.Medium.Nu
m.AMRNB
Number of Times
of AMR-NB Calls Is
MEDIUM for Cell
BSC6900
V900R016C00
73428427
VS.OrigCall.Estab
Delay.Bad.Num.A
MRNB
Number of Times
of AMR-NB Calls Is
BAD for Cell
BSC6900
V900R016C00
73428428
VS.OrigCall.Estab
Delay.Good.Num.A
MRWB
Number of Times
of AMR-WB Calls Is
GOOD for Cell
BSC6900
V900R016C00
73428429
VS.OrigCall.Estab
Delay.Medium.Nu
m.AMRWB
Number of Times
of AMR-WB Calls Is
MEDIUM for Cell
BSC6900
V900R016C00

1340
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428430
VS.OrigCall.Estab
Delay.Bad.Num.A
MRWB
Number of Times
of AMR-WB Calls Is
BAD for Cell
BSC6900
V900R016C00
73428431
VS.RAB.Rel.AMR
NB.CNAbnormal
Number of AMR-NB
RABs Abnormally
Released by the CN
for Cell
BSC6900
V900R016C00
73428432
VS.RAB.Rel.AMR
WB.CNAbnormal
Number of AMRWB RABs

Abnormally
Released by the CN
for Cell
BSC6900
V900R016C00
73430084
VS.RAB.AttEstab
CS.Parallel.Alerting
Number of Times the

Alerting Procedure Is
Initiated in Parallel
with the RAB Setup
Procedure for Cell
BSC6900
V900R017C10
73430085
VS.RAB.SuccEstab
CS.Parallel.Alerting
Number of Times the

Successfully
with the RAB Setup
Procedure for Cell
BSC6900
V900R017C10
73446291
VS.OrigCall.Estab
MeanTime.AMRN
B.UltraFastCSAccess
Average Access
Delay of the Calling
Party for AMR-NB
Services When the
Called Party Uses
Ultrafast CS Call
Setup for Cell
BSC6900
V900R017C10
73446292
VS.OrigCall.Estab
MeanTime.AMRW
B.UltraFastCSAccess
Average Access
Party for AMR-WB
Services When the
Called Party Uses
Ultrafast CS Call
Setup for Cell
BSC6900
V900R017C10
73446299
VS.TermCall.Estab
MeanTime.AMRN
B
Average Access
Delay of AMR-NB
Services Initiated by
the Called Party for
Cell
BSC6900
V900R017C10

1341
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73446306
VS.TermCall.Estab
MeanTime.AMRW
B
Average Access
Delay of AMR-WB
the Called Party for
Cell
BSC6900
V900R017C10
73446356
VS.OrigCall.Estab
MeanTime.AMRN
B.IntraVendor
Average Access
Party for AMR-NB
Services When the
Calling Party and
Called Party Are
Both Under Huawei
RNCs for Cell
BSC6900
V900R017C10
73446357
VS.OrigCall.Estab
MeanTime.AMRW
B.IntraVendor
Average Access
Party for AMR-WB
Services When the
Calling Party and
Called Party Are
Both Under Huawei
RNCs for Cell
BSC6900
V900R017C10
73446358
VS.UuSecMod.IuS
etup.MinDelay
Average Value of the

Smaller of the Delay
in the Uu Security
Mode and Iu Setup
Procedures for Cell
BSC6900
V900R017C10
73446359
VS.RAB.EstabCS.
MeanTime
Average Delay of CS
RAB Setups for Cell
BSC6900
V900R017C10
73430293
VS.SecMod.Paralle
l.Setup.Att
Number of Times the

Uu Security Mode
Procedure Is Parallel
with the Iu Setup
BSC6900
V900R017C10
73430294
VS.SecMod.Paralle
l.Setup.Succ
Number of Times the

Uu Security Mode
Procedure Is
Successfully
with the Iu Setup
Procedure for Cell
BSC6900
V900R017C00
None
Issue 03 (2015-06-30)

1342
BSC6900 UMTS
Number of CS Service Setup Attempts Initiated by UEs in Idle Mode and by

Redirection-based CSFB UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73428375
VS.OrigCSCall.AttEstab.Idl
e
Number of CS Service Setup

Attempts Initiated by UEs in
Idle Mode for Cell
73428376
VS.OrigCSCall.AttEstab.CS
FB.Redir

Redirection-based CSFB
UEs for Cell
Description
These counters provide the number of CS service setup attempts initiated by UEs in idle mode
and by UEs that are performing redirection-based CSFB in the best cell. CS services refer to the
AMR-WB, AMR-NB, and VP services.The preceding counters comply with section "10.2.39
RRC CONNECTION REQUEST" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A in figure 1. When receiving an RRC CONNECTION
REQUEST message with the cause value "Originating Conversational Call" or "Emergency
Call" from a UE, the RNC determines whether the UE is performing CSFB. If yes, the RNC
measures these counters in the best cell for the UE when the RNC successfully receives a
DIRECT TRANSFER (ALERTING) message from the CS domain of the CN or the access fails.
Note: 1.The CS service setup attempt initiated in the following scenario is also calculated into
the VS.OrigCSCall.AttEstab.Idle counter: The RRC CONNECTION REQUEST message sent
by a UE contains a cause value other than " Originating Conversational Call" or "Emergency
Call", but the INITIAL DIRECT TRANSFER (CM SERVICE REQUEST) or UPLINK
DIRECT TRANSFER (CM SERVICE REQUEST) message sent by the UE to the CN contains
the cause value "mobile originate call establishment or packet mode connection establishment"
or "Emergency call establishment".
Issue 03 (2015-06-30)

1343
BSC6900 UMTS
Figure 1-569 Successful CS service setup procedure for UEs in idle mode
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.OrigCSCall.AttEstab.Idl
e
WRFD-010501
WRFD-010613

Rate Wide Band)
FB.Redir
WRFD-010501
WRFD-010613

Rate Wide Band)

1344
BSC6900 UMTS
Number of CS Service Setup Attempts Initiated by UEs in CELL_DCH and

CELL_FACH States for Cell
Counters
Counter ID
Counter Name
Counter Description
73428377
VS.OrigCSCall.AttEstab.D
CH

CELL_DCH State for Cell
73428378
VS.OrigCSCall.AttEstab.FA
CH

CELL_FACH State for Cell
Description
These counters provide the number of CS service setup attempts initiated by UEs in the
CELL_DCH or CELL_FACH state in the best cell. CS services refer to the AMR-WB, AMRNB, and VP services.The preceding counters comply with section "10.5.3.3 CM service type"
in 3GPP TS 24.008 (v10.12.0).
Measurement point
The measurement is triggered at point A in figure 1. When receiving an INITIAL DIRECT
TRANSFER (CM SERVICE REQUEST) or UPLINK DIRECT TRANSFER (CM SERVICE
REQUEST) message from a UE in the CELL_DCH or CELL_FACH state and the cause value
contained in the message is "mobile originate call establishment or packet mode connection
establishment" or "Emergency call establishment", the RNC measures the corresponding
counter. This counter is measured in the best cell for the UE when the RNC successfully receives
a DIRECT TRANSFER (ALERTING) message from the CS domain of the CN or the access
fails.
Issue 03 (2015-06-30)

1345
BSC6900 UMTS
Figure 1-570 Successful CS service setup procedure for UEs in the CELL_DCH or
CELL_FACH state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.OrigCSCall.AttEstab.D
CH
WRFD-010501
WRFD-010613

Rate Wide Band)
VS.OrigCSCall.AttEstab.FA
CH
WRFD-010501
WRFD-010613

Rate Wide Band)

1346
BSC6900 UMTS
Number of CS Service Setup Attempts Initiated by Handover-based CSFB UEs for

Cell
Counters
Counter ID
Counter Name
Counter Description
73428380
FB.PSHO

Handover-based CSFB UEs
for Cell
Description
These counters provide the number of CS service setup attempts initiated by UEs that are
performing handover-based CSFB in the best cell. CS services refer to the AMR-WB, AMRNB, and VP services.This counter complies with section "9.1.10 RELOCATION REQUEST"
in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A in figure 1. The RNC measures this counter in the best
cell for the UE when the RNC successfully receives a DIRECT TRANSFER (ALERTING)
message from the CS domain of the CN or where the access fails if all of the following conditions
are met: 1. The RNC receives a RELOCATION REQUEST message from the CS domain of
the CN. 2. The UE is performing CSFB. 3. The UE returns to the CS domain of the CN an
INITIAL DIRECT TRANSFER (CM SERVICE REQUEST) or UPLINK DIRECT
TRANSFER (CM SERVICE REQUEST) message with the cause value "mobile originate call
establishment or packet mode connection establishment" or "Emergency Call".
Issue 03 (2015-06-30)

1347
BSC6900 UMTS
Figure 1-571 Successful CS service setup procedure for UEs that are performing handoverbased CSFB
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
FB.PSHO
WRFD-010501
WRFD-010613

Rate Wide Band)

1348
BSC6900 UMTS
Number of CS Service Setup Attempts Initiated by UEs in CELL_PCH/URA_PCH

State for Cell
Counters
Counter ID
Counter Name
Counter Description
73428379
VS.OrigCSCall.AttEstab.PC
H

CELL_PCH/URA_PCH
State for Cell
Description
This counter provides the number of CS service setup attempts initiated by UEs in CELL_PCH
and URA_PCH states in the best cell. CS services refer to the AMR-WB, AMR-NB, and VP
services.This counter complies with section "10.2.7 CELL UPDATE" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered at point A in figure 1. The RNC measures this counter when both
of the following conditions are met: The RNC receives a CELL UPDATE message from a UE
in the CELL_PCH or URA_PCH state. The cell update cause is "uplink data transmission", and
the value of the establishment cause IE is "Originating Conversational Call" or "Emergency
Call." This counter is measured in the best cell for the UE when the RNC successfully receives
a DIRECT TRANSFER (ALERTING) message from the CS domain of the CN or the access
fails.
Issue 03 (2015-06-30)

1349
BSC6900 UMTS
Figure 1-572 Successful CS service setup procedure for UEs in the CELL_PCH or URA_PCH
state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.OrigCSCall.AttEstab.PC
H
WRFD-010501
WRFD-010613

Rate Wide Band)

1350
BSC6900 UMTS
Number of Successful CS Service Setups Initiated by UEs in Idle Mode and by

Redirection-based CSFB UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73428381
VS.OrigCSCall.SuccEstab.I
dle
Service Setups Initiated by
UEs in Idle Mode for Cell
73428382
VS.OrigCSCall.SuccEstab.
CSFB.Redir
Redirection-based CSFB
UEs for Cell
Description
These counters provide the number of successful CS service setups initiated by UEs in idle mode
and by UEs that are performing redirection-based CSFB in the best cell. CS services refer to the
AMR-WB, AMR-NB, and VP services.
Measurement point
The measurement is triggered at point B in figure 1. The RNC measures this counter in the best
cell upon receiving a DIRECT TRANSFER (ALERTING) message from the CS domain of the
CN.
Issue 03 (2015-06-30)

1351
BSC6900 UMTS
Figure 1-573 Procedure for CS calling party in idle mode receiving an alerting message from
the CN
The measurement is triggered at point B in figure. When receiving from the CN a Disconnect
message with any of the following causes, the RNC determines that the CS service setup is
successful: Unassigned (unallocated) number (Value = 1) Operator determined barring (Value
= 8) Normal call clearing (Value = 16) User busy (Value = 17) No user responding (Value = 18)
User alerting, no answer (Value = 19) Call rejected (Value = 21) Number changed (Value = 22)
Invalid number format (incomplete number) (Value = 28) Normal, unspecified (Value = 31)
Service or option not available, unspecified (Value = 63) Service or option not implemented,
unspecified (Value = 79) Recovery on timer expiry (Value = 102) For details about these cause
values, see 3GPP TS 24.008.
Issue 03 (2015-06-30)

1352
BSC6900 UMTS
Figure 1-574 Procedure for CS calling party in idle mode receiving a disconnect message from
the CN
The measurement is triggered at point B in figure. After sending a service request message to
the CN, the RNC receives not a Direct Transfer (Alerting) message, but a connect message from
the CN. Under this circumstance, the RNC determines that the CS service setup is successful.
Issue 03 (2015-06-30)

1353
BSC6900 UMTS
Figure 1-575 Procedure for CS calling party in idle mode receiving a connect message from the
CN
the CN, the RNC receives a Disconnect message from the UE before the Direct Transfer
(Alerting) message. Under this circumstance, the RNC determines that the CS service setup is
successful.
Issue 03 (2015-06-30)

1354
BSC6900 UMTS
Figure 1-576 Procedure for CS calling party in idle mode receiving a disconnect message from
the called party
Formula
None
Unit
None
Issue 03 (2015-06-30)

1355
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.OrigCSCall.SuccEstab.I
dle
WRFD-010501
WRFD-010613

Rate Wide Band)
CSFB.Redir
WRFD-010501
WRFD-010613

Rate Wide Band)
Number of Successful CS Service Setups Initiated by UEs in CELL_DCH and

CELL_FACH States
Counters
Counter ID
Counter Name
Counter Description
73428383
DCH
for Cell
73428384
VS.OrigCSCall.SuccEstab.F
ACH
UEs in the CELL_FACH
State for Cell
Description
These counters provide the number of successful CS service setups initiated by UEs in the
CELL_DCH or CELL_FACH state in the best cell. CS services refer to the AMR-WB, AMRNB, and VP services.
Measurement point
The measurement is triggered at point B in figure 1. When receiving a DIRECT TRANSFER
(ALERTING) message from the CS domain of the CN, the RNC determines the state of the UE
that initiates the CS service. If the RNC determines that the UE is in the CELL_DCH or
CELL_FACH state, the RNC measures the corresponding counter in the best cell for the UE.
Issue 03 (2015-06-30)

1356
BSC6900 UMTS
Figure 1-577 Procedure for CS calling party in CELL_FACH or CELL_DCH state receiving
an alerting message from the CN
Issue 03 (2015-06-30)

1357
BSC6900 UMTS
Figure 1-578 Procedure for CS calling party in CELL_FACH or CELL_DCH state receiving a
disconnect message from the CN
Issue 03 (2015-06-30)

1358
BSC6900 UMTS
connect message from the CN
successful.
Issue 03 (2015-06-30)

1359
BSC6900 UMTS
disconnect message from the called party
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
DCH
WRFD-010501
WRFD-010613

Rate Wide Band)
VS.OrigCSCall.SuccEstab.F
ACH
WRFD-010501
WRFD-010613

Rate Wide Band)

1360
BSC6900 UMTS
Number of Successful CS Service Setups Initiated by UEs in the CELL_PCH/

Counters
Counter ID
Counter Name
Counter Description
73428385
VS.OrigCSCall.SuccEstab.P
CH
Description
This counter provides the number of successful CS service setups initiated by UEs in the
CELL_PCH and URA_PCH states in the best cell. CS services refer to the AMR-WB, AMRNB, and VP services.
Measurement point
(ALERTING) message from the CS domain of the CN, the RNC determines the state of the UE
that initiates the CS service. If the RNC determines that the UE is in the CELL_PCH or
URA_PCH state, the RNC measures this counter in the best cell for the UE.
Issue 03 (2015-06-30)

1361
BSC6900 UMTS
Figure 1-581 Procedure for CS calling party in CELL_PCH or URA_PCH state receiving an
alerting message from the CN
Issue 03 (2015-06-30)

1362
BSC6900 UMTS
Figure 1-582 Procedure for CS calling party in CELL_PCH or URA_PCH state receiving a
disconnect message from the CN
Issue 03 (2015-06-30)

1363
BSC6900 UMTS
connect message from the CN
successful.
Issue 03 (2015-06-30)

1364
BSC6900 UMTS
disconnect message from the called party
Formula
None
Unit
None
Issue 03 (2015-06-30)

1365
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.OrigCSCall.SuccEstab.P
CH
WRFD-010501
WRFD-010613

Rate Wide Band)
Number of Successful CS Service Setups Initiated by Handover-based CSFB UEs

for Cell
Counters
Counter ID
Counter Name
Counter Description
73428386
CSFB.PSHO
Handover-based CSFB UEs
for Cell
Description
This counter provides the number of successful CS service setups initiated by UEs that are
performing handover-based CSFB in the best cell. CS services refer to the AMR-WB, AMRNB, and VP services.
Measurement point
(ALERTING) message from the CS domain of the CN, the RNC determines whether the UE
that initiates the CS service is performing handover-based CSFB. If yes, the RNC measures this
counter in the best cell for the UE.
Issue 03 (2015-06-30)

1366
BSC6900 UMTS
Figure 1-585 Procedure for calling party in CSFB receiving an alerting message from the CN
Issue 03 (2015-06-30)

1367
BSC6900 UMTS
Figure 1-586 Procedure for calling party in CSFB receiving a disconnect message from the CN
Issue 03 (2015-06-30)

1368
BSC6900 UMTS
Figure 1-587 Procedure for calling party in CSFB receiving a connect message from the CN
successful.
Issue 03 (2015-06-30)

1369
BSC6900 UMTS
Figure 1-588 Procedure for calling party in CSFB receiving a disconnect message from the CN
Formula
None
Unit
None
Issue 03 (2015-06-30)

1370
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
CSFB.PSHO
WRFD-010501
WRFD-010613

Rate Wide Band)
Number of Speech Frames on Which the CS Voice Precise Power Control Feature
Takes Effect for a Single AMR Service for Cell
Counters
Counter ID
Counter Name
Counter Description
73427973
VS.SingleRAB.CSVoicePP
C.CSVoiceFrames
Number of Speech Frames on

Which the CS Voice Precise
Power Control Feature Takes
Effect for a Single AMR
Service for Cell
Description
This counter provides the number of speech frames on which the CS Voice Precise Power
Control feature takes effect for a single AMR service. This counter is updated in the best cell.
Measurement point
Within a measurement period, for a single AMR service, the MAC-d entity calculates the number
of speech frames on which the CS Voice Precise Power Control feature takes effect. The MACd entity does not calculate empty frames or SID frames. The counter is updated in the best cell.
Formula
None
Unit
frame
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SingleRAB.CSVoicePP
C.CSVoiceFrames
WRFD-160204
CS Voice Precise Power

Control

1371
BSC6900 UMTS
Number of Speech Frames on Which the CS Voice Precise Power Control Feature
Takes Effect for Combined Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73427974
VS.MultiRAB.CSVoicePPC
.CSVoiceFrames
Number of Speech Frames on

Which the CS Voice Precise
Power Control Feature Takes
Effect for Combined
Services for Cell
Description
This counter provides the number of speech frames on which the CS Voice Precise Power
Control feature takes effect for the AMR service in combined services. This counter is updated
in the best cell.
Note: During power control over combined services, the RNC considers the target SIR of the
CS service and the target SIR of the PS service. If the target SIR of the CS service is used at
last, this counter is updated. If the target SIR of the PS service is used at last, this counter is not
updated.
Measurement point
Within a measurement period, for the AMR service in combined services, the MAC-d entity
calculates the number of speech frames on which the CS Voice Precise Power Control feature
takes effect. The MAC-d entity does not calculate empty frames or SID frames. The counter is
updated in the best cell.
Formula
None
Unit
frame
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MultiRAB.CSVoicePPC
.CSVoiceFrames
WRFD-160204

Control

1372
BSC6900 UMTS
Number of Frames Involved in a Single AMR Service for Cell

Counters
Counter ID
Counter Name
Counter Description
73427994
VS.SingleRAB.CSVoiceTotalFrames
Number of Frames Involved

in a Single AMR Service for
Cell
Description
This counter provides the number of frames involved in a single AMR service. This counter is
updated in the best cell.
Note: This counter is updated only when the CS Voice Precise Power Control feature is activated.
Measurement point
Within a measurement period, for a single AMR service, the MAC-d entity calculates the number
of frames, including speech frames, empty frames, and SID frames. The counter is updated in
the best cell.
Formula
None
Unit
frame
Related Features
Counter Name
Feature ID
Feature Name
VS.SingleRAB.CSVoiceTotalFrames
WRFD-160204

Control
Number of Frames Involved in the AMR Service of Combined Services for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73427995
VS.MultiRAB.CSVoiceTotalFrames
Number of Frames Involved

in the AMR Service of
Combined Services for Cell

1373
BSC6900 UMTS
Description
This counter provides the number of frames involved in the AMR service of combined services.
This counter is updated in the best cell.
Note: This counter is updated only when the CS Voice Precise Power Control feature is activated.
Measurement point
Within a measurement period, for the AMR service in combined services, the MAC-d entity
calculates the number of frames, including speech frames, empty frames, and SID frames. The
counter is updated in the best cell.
Formula
None
Unit
frame
Related Features
Counter Name
Feature ID
Feature Name
VS.MultiRAB.CSVoiceTotalFrames
WRFD-160204

Control
Number of Normally Released AMR-NB RABs (Poor Uplink Voice Quality)

Counters
Counter ID
Counter Name
Counter Description
73428271
VS.RAB.Rel.AMRNB.UL.
LowQuality
Number of Normally
Released AMR-NB RABs
(Poor Uplink Voice Quality)
Description
This counter measures the number of normally released AMR-NB RABs whose uplink enhanced
VQIs (EVQIs) are lower than AMRNBLowQualRelEVQIThd for AMRLowQualRelEVQINum
consecutive times before the RAB release. The measurement is performed in the best cell that
the UE camps on.
Measurement point
The measurement is triggered in the best cell that the UE camps on when the uplink EVQIs of
AMR-NB RABs in the VS.RAB.NormRel.AMR counter are lower than
Issue 03 (2015-06-30)

1374
BSC6900 UMTS
AMRNBLowQualRelEVQIThd for AMRLowQualRelEVQINum consecutive times before the

RAB release. AMRNBLowQualRelEVQIThd and AMRLowQualRelEVQINum are set by the
SET UEVQIPARA command.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.AMRNB.UL.
LowQuality
WRFD-010501
Number of Normally Released AMR-NB RABs (Poor Downlink Voice Quality)

Counters
Counter ID
Counter Name
Counter Description
73428272
VS.RAB.Rel.AMRNB.DL.
LowQuality
Number of Normally
Released AMR-NB RABs
(Poor Downlink Voice
Quality)
Description
This counter measures the number of normally released AMR-NB RABs whose downlink
EVQIs are lower than AMRNBLowQualRelEVQIThd for AMRLowQualRelEVQINum
the UE camps on.
Measurement point
The measurement is triggered in the best cell that the UE camps on when the following conditions
are met:
The uplink EVQIs of AMR-NB RABs in the VS.RAB.NormRel.AMR counter are larger than
or equal to AMRNBLowQualRelEVQIThd for AMRLowQualRelEVQINum consecutive times
before the RAB release.
The downlink EVQIs of AMR-NB RABs in the VS.RAB.NormRel.AMR counter are lower than
AMRNBLowQualRelEVQIThd for AMRLowQualRelEVQINum consecutive times before the
RAB release.
Issue 03 (2015-06-30)

1375
BSC6900 UMTS
AMRNBLowQualRelEVQIThd and AMRLowQualRelEVQINum are set by the SET

UEVQIPARA command.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.AMRNB.DL.
LowQuality
WRFD-010501
Number of Normally Released AMR-WB RABs (Poor Uplink Voice Quality)

Counters
Counter ID
Counter Name
Counter Description
73428273
VS.RAB.Rel.AMRWB.UL.
LowQuality
Number of Normally
Released AMR-WB RABs
(Poor Uplink Voice Quality)
Description
This counter measures the number of normally released AMR-WB RABs whose uplink
enhanced VQIs (EVQIs) are lower than AMRWBLowQualRelEVQIThd for
AMRLowQualRelEVQINum consecutive times before the RAB release. The measurement is
performed in the best cell that the UE camps on.
Measurement point
The measurement is triggered in the best cell that the UE camps on when the uplink EVQIs of
AMR-WB RABs in the VS.RAB.NormRel.AMR counter are lower than
AMRWBLowQualRelEVQIThd for AMRLowQualRelEVQINum consecutive times before the
RAB release. AMRWBLowQualRelEVQIThd and AMRLowQualRelEVQINum are set by the
SET UEVQIPARA command.
Formula
None
Issue 03 (2015-06-30)

1376
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.AMRWB.UL.
LowQuality
WRFD-010501
WRFD-010613

Rate Wide Band)
Number of Normally Released AMR-WB RABs (Poor Downlink Voice Quality)

Counters
Counter ID
Counter Name
Counter Description
73428274
VS.RAB.Rel.AMRWB.DL.
LowQuality
Number of Normally
Released AMR-WB RABs
(Poor Downlink Voice
Quality)
Description
This counter measures the number of normally released AMR-WB RABs whose downlink
EVQIs are lower than AMRWBLowQualRelEVQIThd for AMRLowQualRelEVQINum
the UE camps on.
Measurement point
The measurement is triggered in the best cell that the UE camps on when the following conditions
are met:
The uplink EVQIs of AMR-WB RABs in the VS.RAB.NormRel.AMR counter are larger than
or equal to AMRWBLowQualRelEVQIThd for AMRLowQualRelEVQINum consecutive times
The downlink EVQIs of AMR-WB RABs in the VS.RAB.NormRel.AMR counter are lower
than AMRWBLowQualRelEVQIThd for AMRLowQualRelEVQINum consecutive times
AMRWBLowQualRelEVQIThd and AMRLowQualRelEVQINum are set by the SET
UEVQIPARA command.
Formula
None
Issue 03 (2015-06-30)

1377
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.AMRWB.DL.
LowQuality
WRFD-010501
WRFD-010613

Rate Wide Band)
Number of Times That Silence Is Detected for AMR Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73428275
VS.AMRNB.ULSilent.OccurNum

for AMR-NB Services for
Cell
73428276
VS.AMRNB.DLSilent.OccurNum

Downlink for AMR-NB
Services for Cell
73428277
VS.AMRWB.ULSilent.OccurNum

for AMR-WB Services for
Cell
73428278
VS.AMRWB.DLSilent.OccurNum

Downlink for AMR-WB
Services for Cell
Description
These counters measure the number of times that silence is detected in both the uplink and
downlink for AMR narrowband and wideband services. The measurement is performed in the
best cell that the UE camps on.
Measurement point
The RNC detects speech frames in both the uplink and downlink at the IuUP layer every two
seconds. It then checks whether frame loss or erroneous frame exists. If the ratio of lost frames
or erroneous frames exceeds the threshold (20% by default) for three consecutive measurement
Issue 03 (2015-06-30)

1378
BSC6900 UMTS
periods (a measurement period lasts two seconds), the RNC considers that silence is detected
during the AMR service and measures this counter based on service types and transmission
directions in the best cell that the UE camps on. This counter is not repetitively measured if the
ratio of lost frames or erroneous frames in the incoming measurement periods exceeds the
threshold after the silence detection. The measurement resumes only when this ratio in a
measurement period is lower than the threshold.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AMRNB.ULSilent.OccurNum
WRFD-010501
VS.AMRNB.DLSilent.OccurNum
WRFD-010501
VS.AMRWB.ULSilent.OccurNum
WRFD-010501
VS.AMRWB.DLSilent.OccurNum
WRFD-010501
Number of Garbled Voice Occurrences on Uplink AMR Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73428351
VS.AMRNB.ULGarbledVoi
ce.OccurNum
Number of Garbled Voice

Occurrences on Uplink
AMR-NB Services for Cell
73428353
VS.AMRWB.ULGarbledVo
ice.OccurNum

Occurrences on Uplink
AMR-WB Services for Cell
Description
These counters measure the number of garbled voice occurrences on the uplink AMR services
in a cell.
Issue 03 (2015-06-30)

1379
BSC6900 UMTS

Counter Name
Description
VS.AMRNB.ULGarbledVoice.OccurNum
This counter measures the number of garbled

voice occurrences on the uplink AMR-NB
services in a cell.
VS.AMRWB.ULGarbledVoice.OccurNum

voice occurrences on the uplink AMR-WB
services in a cell.
Measurement point
When receiving a message carrying encryption activation parameters from a UE performing
AMR services, the RNC starts garbled noise detection for uplink AMR services. The messages
can be any of the following:
1)RADIO BEARER SETUP COMPLETE
2)RADIO BEARER RECONFIGURATION COMPLETE
3)TRANSPORT CHANNEL RECONFIGURATION COMPLETE
4)PHYSICAL CHANNEL RECONFIGURATION COMPLETE
5)UTRAN MOBILITY INFORMATION CONFIRM
6)HANDOVER TO UTRAN COMPLETE
The measurement is triggered at point A in figure 1, which uses the RADIO BEARER SETUP
COMPLETE message as an example. When receiving a RADIO BEARER SETUP COMPLETE
message that carries encryption activation parameters START and COUNT-C activation time
from a UE, the RNC starts garbled noise detection for uplink AMR services. If garbled noise is
detected, this counter is measured in the best cell where the UE camps.
Figure 1-589 Uplink garbled noise detection
Issue 03 (2015-06-30)

1380
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ce.OccurNum
WRFD-160102
Garbled Noise Detection and

Correction of AMR Voice
ice.OccurNum
WRFD-160102

Number of Garbled Voice Occurrences on Downlink AMR Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73428352
VS.AMRNB.DLGarbledVoi
ce.OccurNum

Occurrences on Downlink
AMR-NB Services for Cell
73428354
VS.AMRWB.DLGarbledVo
ice.OccurNum

Occurrences on Downlink
AMR-WB Services for Cell
Description
These counters measure the number of garbled voice occurrences on the downlink AMR services
in a cell.
Issue 03 (2015-06-30)
Counter Name
Description
VS.AMRNB.DLGarbledVoice.OccurNum

voice occurrences on the downlink AMR-NB
services in a cell.

1381
BSC6900 UMTS
Counter Name
Description
VS.AMRWB.DLGarbledVoice.OccurNum

voice occurrences on the downlink AMRWB services in a cell.
Measurement point
When the function of garbled noise detection for downlink AMR services is enabled, the RNC
starts garbled noise detection for downlink AMR services upon the reception of any of the
following messages:
1)DIRECT TRANSFER(Connect) message from the CN for the calling party
2)DIRECT TRANSFER(Connect ACK) message from the CN for the called party
3)RELOCATION COMPLETE message from another RNC for UEs performing an incoming
relocation
4)RELOCATION COMPLETE message from another RNC for UEs performing an incoming
inter-RAT handover
The measurement is triggered at point A in figure 2, which uses the DIRECT TRANSFER
(Connect) message as an example. When receiving a DL DIRECT TRANSFER(Connect)
message from the CN, the RNC starts garbled noise detection for downlink AMR services. If
garbled noise is detected, this counter is measured in the best cell where the UE camps.
Figure 1-590 Downlink garbled noise detection
Formula
None
Issue 03 (2015-06-30)

1382
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AMRNB.DLGarbledVoi
ce.OccurNum
WRFD-160102

VS.AMRWB.DLGarbledVo
ice.OccurNum
WRFD-160102

Number of Successful Garbled Voice Corrections on Uplink AMR Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73428356
iceCorrect.Num
Garbled Voice Corrections
on Uplink AMR-WB
Services for Cell
73428355
ceCorrect.Num
Garbled Voice Corrections
on Uplink AMR-NB
Services for Cell
Description
These counters measure the number of successful garbled voice corrections on uplink AMR
services in a cell.
Issue 03 (2015-06-30)
Counter Name
Description
VS.AMRWB.ULGarbledVoiceCorrect.Num
This counter measures the number of

successful garbled voice corrections on
uplink AMR-WB services in a cell.
VS.AMRNB.ULGarbledVoiceCorrect.Num

successful garbled voice corrections on
uplink AMR-NB services in a cell.

1383
BSC6900 UMTS
Measurement point
When the function of garbled voice correction for uplink AMR services is enabled, the RNC
corrects the garbled voice in the uplink after detecting it. If no garbled voice is detected in the
uplink after the correction, this counter is measured in the best cell where the UE camps.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
iceCorrect.Num
WRFD-160102

ceCorrect.Num
WRFD-160102

Average Access Delay of the AMR-NB Calls Initiated by UEs in Idle Mode for Cell
Counters
Counter ID
Counter Name
Counter Description
73444350
VS.OrigCall.EstabMeanTim
e.AMRNB.Idle
Average Access Delay of the

AMR-NB Calls Initiated by
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428401
VS.OrigCall.EstabTime.AM
RNB.Idle.Cum
Accumulated Access Delay

of the AMR-NB Calls
Initiated by UEs in Idle Mode
for Cell

1384
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428402
RNB.Idle.Sample
Sampling Times of the

of the AMR-NB Calls
for Cell
Description
This counter provides the average access delay of the AMR-NB calls initiated by UEs in idle
mode in the best cell. This counter excludes the access delay of the AMR-NB calls initiated by
UEs that are performing redirection-based CSFB.
Measurement point
The RNC determines that the AMR-NB call is initiated by a UE in idle mode. When receiving
an RRC CONNECTION REQUEST message from the UE (shown by point A in figure 1), the
RNC records the receive time (T1). When receiving a DIRECT TRANSFER (ALERTING)
message from the CS domain of the CN, the RNC records the receive time (T2). The access
delay (delta T) equals T2 minus T1. At the end of the measurement period, the RNC obtains the
average access delay by dividing the accumulated access delay by the number of successful
AMR-NB calls initiated by UEs in idle mode.
Issue 03 (2015-06-30)

1385
BSC6900 UMTS
Formula
VS.OrigCall.EstabMeanTime.AMRNB.Idle = [VS.OrigCall.EstabTime.AMRNB.Idle.Cum]/
[VS.OrigCall.EstabTime.AMRNB.Idle.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRNB.Idle
WRFD-010501

1386
BSC6900 UMTS
Average Access Delay of the AMR-NB Calls Initiated by UEs in Redirection-based

CSFB for Cell
Counters
Counter ID
Counter Name
Counter Description
73444355
e.AMRNB.CSFB.Redir

UEs in Redirection-based
CSFB for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428403
RNB.CSFB.Redir.Cum

of the AMR-NB Calls
Initiated by UEs in
Redirection-based CSFB for
Cell
73428404
RNB.CSFB.Redir.Sample

of the AMR-NB Calls
Initiated by UEs in
Cell
Description
This counter provides the average access delay of the AMR-NB calls initiated by UEs in
redirection-based CSFB in the best cell.
Measurement point
The RNC determines that the AMR-NB call is initiated by a UE performing redirection-based
CSFB. When receiving an RRC CONNECTION REQUEST message from the UE (shown by
point A in figure 1), the RNC records the receive time (T1). When receiving a DIRECT
TRANSFER (ALERTING) message from the CS domain of the CN, the RNC records the receive
time (T2). The access delay (delta T) equals T2 minus T1. At the end of the measurement period,
the RNC obtains the average access delay by dividing the accumulated access delay by the
number of successful AMR-NB calls initiated by UEs performing redirection-based CSFB.
Issue 03 (2015-06-30)

1387
BSC6900 UMTS
Figure 1-592 Successful CS service setup initiated by UEs performing redirection-based CSFB
Formula
VS.OrigCall.EstabMeanTime.AMRNB.CSFB.Redir =
[VS.OrigCall.EstabTime.AMRNB.CSFB.Redir.Cum]/
[VS.OrigCall.EstabTime.AMRNB.CSFB.Redir.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRNB.CSFB.Redir
WRFD-010501

1388
BSC6900 UMTS
Average Access Delay of the AMR-NB Calls Initiated by UEs in the CELL_DCH
State for Cell
Counters
Counter ID
Counter Name
Counter Description
73444356
e.AMRNB.DCH

for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428405
RNB.DCH.Cum

of the AMR-NB Calls
Initiated by UEs in the
73428406
RNB.DCH.Sample

of the AMR-NB Calls
Description
This counter provides the average access delay of the AMR-NB calls initiated by UEs in the
CELL_DCH state in the best cell.
Measurement point
The RNC determines that the AMR-NB call is initiated by a UE in the CELL_DCH state. When
receiving an INITIAL DIRECT TRANSFER (CM SERVICE REQEUST) or UPLINK DIRECT
TRANSFER (CM SERVICE REQEUST) message from the UE (shown by point A in figure 1),
the RNC records the receive time (T1). When receiving a DIRECT TRANSFER (ALERTING)
AMR-NB calls initiated by UEs in the CELL_DCH state.
Issue 03 (2015-06-30)

1389
BSC6900 UMTS
Figure 1-593 Successful CS service setup procedure for UEs in the CELL_DCH state
Formula
VS.OrigCall.EstabMeanTime.AMRNB.DCH =
[VS.OrigCall.EstabTime.AMRNB.DCH.Cum]/
[VS.OrigCall.EstabTime.AMRNB.DCH.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRNB.DCH
WRFD-010501

1390
BSC6900 UMTS
Average Access Delay of the AMR-NB Calls Initiated by UEs in the CELL_FACH
State for Cell
Counters
Counter ID
Counter Name
Counter Description
73444339
e.AMRNB.FACH

State for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428407
RNB.FACH.Cum

of the AMR-NB Calls
73428408
RNB.FACH.Sample

of the AMR-NB Calls
Description
CELL_FACH state in the best cell.
Measurement point
The RNC determines that the AMR-NB call is initiated by a UE in the CELL_FACH state. When
AMR-NB calls initiated by UEs in the CELL_FACH state.
Issue 03 (2015-06-30)

1391
BSC6900 UMTS
Figure 1-594 Successful CS service setup procedure for UEs in the CELL_FACH state
Formula
VS.OrigCall.EstabMeanTime.AMRNB.FACH =
[VS.OrigCall.EstabTime.AMRNB.FACH.Cum]/
[VS.OrigCall.EstabTime.AMRNB.FACH.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRNB.FACH
WRFD-010501

1392
BSC6900 UMTS
Average Access Delay of the AMR-NB Calls Initiated by UEs in the CELL_PCH/
Counters
Counter ID
Counter Name
Counter Description
73444357
e.AMRNB.PCH

specific formulas.
Counter ID
Counter Name
Counter Description
73428409
RNB.PCH.Cum

of the AMR-NB Calls
CELL_PCH/URA_PCH
State for Cell
73428410
RNB.PCH.Sample

of the AMR-NB Calls
CELL_PCH/URA_PCH
State for Cell
Description
CELL_PCH and URA_PCH states in the best cell.
Measurement point
The RNC determines that the AMR-NB call is initiated by a UE in the CELL_PCH or URA_PCH
state. When receiving a CELL UPDATE message from the UE (shown by point A in figure 1),
AMR-NB calls initiated by UEs in the CELL_PCH and URA_PCH states.
Issue 03 (2015-06-30)

1393
BSC6900 UMTS
state
Formula
VS.OrigCall.EstabMeanTime.AMRNB.PCH = [VS.OrigCall.EstabTime.AMRNB.PCH.Cum]/
[VS.OrigCall.EstabTime.AMRNB.PCH.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRNB.PCH
WRFD-010501

1394
BSC6900 UMTS
Average Access Delay of the AMR-NB Calls Initiated by UEs in Handover-based

CSFB for Cell
Counters
Counter ID
Counter Name
Counter Description
73444358
e.AMRNB.CSFB.PSHO

UEs in Handover-based
CSFB for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428411
RNB.CSFB.PSHO.Cum

of the AMR-NB Calls
Initiated by UEs in
Handover-based CSFB for
Cell
73428412
RNB.CSFB.PSHO.Sample

of the AMR-NB Calls
Initiated by UEs in
Cell
Description
This counter provides the average access delay of the AMR-NB calls initiated by UEs that are
performing handover-based CSFB in the best cell.
Measurement point
The RNC determines that the AMR-NB call is initiated by a UE performing handover-based
CSFB. When receiving a RELOCATION REQUEST message from the CS domain of the CN
(shown by point A in figure 1), the RNC records the receive time (T1). When receiving a
DIRECT TRANSFER (ALERTING) message from the CS domain of the CN, the RNC records
the receive time (T2). The access delay (delta T) equals T2 minus T1. At the end of the
measurement period, the RNC obtains the average access delay by dividing the accumulated
access delay by the number of successful AMR-NB calls initiated by UEs performing handoverbased CSFB.
Issue 03 (2015-06-30)

1395
BSC6900 UMTS
Formula
VS.OrigCall.EstabMeanTime.AMRNB.CSFB.PSHO =
[VS.OrigCall.EstabTime.AMRNB.CSFB.PSHO.Cum]/
[VS.OrigCall.EstabTime.AMRNB.CSFB.PSHO.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRNB.CSFB.PSHO
WRFD-010501

1396
BSC6900 UMTS
Average Access Delay of the AMR-NB Calls Initiated by UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73444351
e.AMRNB

UEs for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428411
RNB.CSFB.PSHO.Cum

of the AMR-NB Calls
Initiated by UEs in
Cell
73428412
RNB.CSFB.PSHO.Sample

of the AMR-NB Calls
Initiated by UEs in
Cell
73428403
RNB.CSFB.Redir.Cum

of the AMR-NB Calls
Initiated by UEs in
Cell
73428404
RNB.CSFB.Redir.Sample

of the AMR-NB Calls
Initiated by UEs in
Cell
73428405
RNB.DCH.Cum

of the AMR-NB Calls
73428406
RNB.DCH.Sample

of the AMR-NB Calls

1397
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428407
RNB.FACH.Cum

of the AMR-NB Calls
73428408
RNB.FACH.Sample

of the AMR-NB Calls
73428401
RNB.Idle.Cum

of the AMR-NB Calls
for Cell
73428402
RNB.Idle.Sample

of the AMR-NB Calls
for Cell
73428409
RNB.PCH.Cum

of the AMR-NB Calls
CELL_PCH/URA_PCH
State for Cell
73428410
RNB.PCH.Sample

of the AMR-NB Calls
CELL_PCH/URA_PCH
State for Cell
Description
best cell.
Measurement point
The RNC measures the access delay of the AMR-NB calls initiated by UEs in idle mode, in
CELL_DCH/CELL_FACH/CELL_PCH/URA_PCH state, and by UEs that are performing
redirection- and handover-based CSFB. At the end of the measurement period, the RNC obtains
the average access delay by dividing the accumulated access delay by the number of successful
AMR-NB calls initiated by UEs in the cell.
Issue 03 (2015-06-30)

1398
BSC6900 UMTS
Formula
VS.OrigCall.EstabMeanTime.AMRNB = ([VS.OrigCall.EstabTime.AMRNB.Idle.Cum]+
[VS.OrigCall.EstabTime.AMRNB.DCH.Cum]+
[VS.OrigCall.EstabTime.AMRNB.FACH.Cum]+
[VS.OrigCall.EstabTime.AMRNB.PCH.Cum]+
[VS.OrigCall.EstabTime.AMRNB.CSFB.Redir.Cum]+
[VS.OrigCall.EstabTime.AMRNB.CSFB.PSHO.Cum])/
([VS.OrigCall.EstabTime.AMRNB.Idle.Sample]+
[VS.OrigCall.EstabTime.AMRNB.CSFB.Redir.Sample]+
[VS.OrigCall.EstabTime.AMRNB.DCH.Sample]+
[VS.OrigCall.EstabTime.AMRNB.FACH.Sample]+
[VS.OrigCall.EstabTime.AMRNB.PCH.Sample]+
[VS.OrigCall.EstabTime.AMRNB.CSFB.PSHO.Sample])
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
e.AMRNB
WRFD-010501
Average Access Delay of the AMR-WB Calls Initiated by UEs in Idle Mode for Cell
Counters
Counter ID
Counter Name
Counter Description
73444352
e.AMRWB.Idle

AMR-WB Calls Initiated by
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428413
RWB.Idle.Cum

of the AMR-WB Calls
for Cell

1399
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428414
RWB.Idle.Sample

of the AMR-WB Calls
for Cell
Description
This counter provides the average access delay of the AMR-WB calls initiated by UEs in idle
mode in the best cell. This counter excludes the access delay of the AMR-WB calls initiated by
UEs that are performing redirection-based CSFB.
Measurement point
The RNC determines that the AMR-WB call is initiated by a UE in idle mode. When receiving
an RRC CONNECTION REQUEST message from the UE (shown by point A in figure 1), the
RNC records the receive time (T1). When receiving a DIRECT TRANSFER (ALERTING)
AMR-WB calls initiated by UEs in idle mode.
Issue 03 (2015-06-30)

1400
BSC6900 UMTS
Formula
VS.OrigCall.EstabMeanTime.AMRWB.Idle = [VS.OrigCall.EstabTime.AMRWB.Idle.Cum]/
[VS.OrigCall.EstabTime.AMRWB.Idle.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRWB.Idle
WRFD-010501

1401
BSC6900 UMTS
Average Access Delay of the AMR-WB Calls Initiated by UEs in the CELL_DCH
State for Cell
Counters
Counter ID
Counter Name
Counter Description
73444353
e.AMRWB.DCH

for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428415
RWB.DCH.Cum

of the AMR-WB Calls
73428416
RWB.DCH.Sample

of the AMR-WB Calls
Description
This counter provides the average access delay of the AMR-WB calls initiated by UEs in the
CELL_DCH state in the best cell.
Measurement point
The RNC determines that the AMR-WB call is initiated by a UE in the CELL_DCH state. When
AMR-WB calls initiated by UEs in the CELL_DCH state.
Issue 03 (2015-06-30)

1402
BSC6900 UMTS
Figure 1-598 Successful CS service setup procedure for UEs in the CELL_DCH stat
Formula
VS.OrigCall.EstabMeanTime.AMRWB.DCH =
[VS.OrigCall.EstabTime.AMRWB.DCH.Cum]/
[VS.OrigCall.EstabTime.AMRWB.DCH.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRWB.DCH
WRFD-010501
WRFD-010613

Rate Wide Band)

1403
BSC6900 UMTS
Average Access Delay of the AMR-WB Calls Initiated by UEs in the CELL_FACH
State for Cell
Counters
Counter ID
Counter Name
Counter Description
73444354
e.AMRWB.FACH

State for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428417
RWB.FACH.Cum

of the AMR-WB Calls
73428418
RWB.FACH.Sample

of the AMR-WB Calls
Description
CELL_FACH state in the best cell.
Measurement point
The RNC determines that the AMR-WB call is initiated by a UE in the CELL_FACH state.
When receiving an INITIAL DIRECT TRANSFER (CM SERVICE REQEUST) or UPLINK
DIRECT TRANSFER (CM SERVICE REQEUST) message from the UE (shown by point A in
figure 1), the RNC records the receive time (T1). When receiving a DIRECT TRANSFER
(ALERTING) message from the CS domain of the CN, the RNC records the receive time (T2).
The access delay (delta T) equals T2 minus T1. At the end of the measurement period, the RNC
obtains the average access delay by dividing the accumulated access delay by the number of
successful AMR-WB calls initiated by UEs in the CELL_FACH state.
Issue 03 (2015-06-30)

1404
BSC6900 UMTS
Figure 1-599 Successful CS service setup procedure for UEs in the CELL_FACH state
Formula
VS.OrigCall.EstabMeanTime.AMRWB.FACH =
[VS.OrigCall.EstabTime.AMRWB.FACH.Cum]/
[VS.OrigCall.EstabTime.AMRWB.FACH.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRWB.FACH
WRFD-010501
WRFD-010613

Rate Wide Band)

1405
BSC6900 UMTS
Average Access Delay of the AMR-WB Calls Initiated by UEs in the CELL_PCH/
Counters
Counter ID
Counter Name
Counter Description
73444346
e.AMRWB.PCH

specific formulas.
Counter ID
Counter Name
Counter Description
73428419
RWB.PCH.Cum

of the AMR-WB Calls
CELL_PCH/URA_PCH
State for Cell
73428420
RWB.PCH.Sample

of the AMR-WB Calls
CELL_PCH/URA_PCH
State for Cell
Description
Measurement point
The RNC determines that the AMR-WB call is initiated by a UE in the CELL_PCH or
URA_PCH state. When receiving a CELL UPDATE message from the UE (shown by point A
in figure 1), the RNC records the receive time (T1). When receiving a DIRECT TRANSFER
(ALERTING) message from the CS domain of the CN, the RNC records the receive time (T2).
The access delay (delta T) equals T2 minus T1. At the end of the measurement period, the RNC
obtains the average access delay by dividing the accumulated access delay by the number of
successful AMR-WB calls initiated by UEs in the CELL_PCH and URA_PCH states.
Issue 03 (2015-06-30)

1406
BSC6900 UMTS
state
Formula
VS.OrigCall.EstabMeanTime.AMRWB.PCH =
[VS.OrigCall.EstabTime.AMRWB.PCH.Cum]/
[VS.OrigCall.EstabTime.AMRWB.PCH.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRWB.PCH
WRFD-010501
WRFD-010613

Rate Wide Band)

1407
BSC6900 UMTS
Average Access Delay of the AMR-WB Calls Initiated by UEs in Redirection-based

CSFB for Cell
Counters
Counter ID
Counter Name
Counter Description
73444347
e.AMRWB.CSFB.Redir

UEs in Redirection-based
CSFB for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428421
RWB.CSFB.Redir.Cum

of the AMR-WB Calls
Initiated by UEs in
Cell
73428422
RWB.CSFB.Redir.Sample

of the AMR-WB Calls
Initiated by UEs in
Cell
Description
This counter provides the average access delay of the AMR-WB calls initiated by UEs that are
performing redirection-based CSFB in the best cell.
Measurement point
The RNC determines that the AMR-WB call is initiated by a UE performing redirection-based
CSFB. When receiving an RRC CONNECTION REQUEST message from the UE (shown by
point A in figure 1), the RNC records the receive time (T1). When receiving a DIRECT
TRANSFER (ALERTING) message from the CS domain of the CN, the RNC records the receive
time (T2). The access delay (delta T) equals T2 minus T1. At the end of the measurement period,
the RNC obtains the average access delay by dividing the accumulated access delay by the
number of successful AMR-WB calls initiated by UEs performing redirection-based CSFB.
Issue 03 (2015-06-30)

1408
BSC6900 UMTS
Figure 1-601 Successful CS service setup initiated by UEs performing redirection-based CSFB
Formula
VS.OrigCall.EstabMeanTime.AMRWB.CSFB.Redir =
[VS.OrigCall.EstabTime.AMRWB.CSFB.Redir.Cum]/
[VS.OrigCall.EstabTime.AMRWB.CSFB.Redir.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRWB.CSFB.Redir
WRFD-010501
WRFD-010613

Rate Wide Band)

1409
BSC6900 UMTS
Average Access Delay of the AMR-WB Calls Initiated by UEs in Handover-based

CSFB for Cell
Counters
Counter ID
Counter Name
Counter Description
73444348
e.AMRWB.CSFB.PSHO

UEs in Handover-based
CSFB for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428423
RWB.CSFB.PSHO.Cum

of the AMR-WB Calls
Initiated by UEs in
Cell
73428424
RWB.CSFB.PSHO.Sample

of the AMR-WB Calls
Initiated by UEs in
Cell
Description
This counter provides the average access delay of the AMR-WB calls initiated by UEs that are
performing handover-based CSFB in the best cell.
Measurement point
The RNC determines that the AMR-WB call is initiated by a UE performing handover-based
CSFB. When receiving a RELOCATION REQUEST message from the CS domain of the CN
(shown by point A in figure 1), the RNC records the receive time (T1). When receiving a
DIRECT TRANSFER (ALERTING) message from the CS domain of the CN, the RNC records
the receive time (T2). The access delay (delta T) equals T2 minus T1. At the end of the
access delay by the number of successful AMR-WB calls initiated by UEs performing handoverbased CSFB.
Issue 03 (2015-06-30)

1410
BSC6900 UMTS
Formula
VS.OrigCall.EstabMeanTime.AMRWB.CSFB.PSHO =
[VS.OrigCall.EstabTime.AMRWB.CSFB.PSHO.Cum]/
[VS.OrigCall.EstabTime.AMRWB.CSFB.PSHO.Sample]
Unit
ms
Issue 03 (2015-06-30)

1411
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
e.AMRWB.CSFB.PSHO
WRFD-010501
WRFD-010613

Rate Wide Band)
Average Access Delay of the AMR-WB Calls Initiated by UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73444349
e.AMRWB

UEs for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428423
RWB.CSFB.PSHO.Cum

of the AMR-WB Calls
Initiated by UEs in
Cell
73428424
RWB.CSFB.PSHO.Sample

of the AMR-WB Calls
Initiated by UEs in
Cell
73428421
RWB.CSFB.Redir.Cum

of the AMR-WB Calls
Initiated by UEs in
Cell
73428422
RWB.CSFB.Redir.Sample

of the AMR-WB Calls
Initiated by UEs in
Cell

1412
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428415
RWB.DCH.Cum

of the AMR-WB Calls
73428416
RWB.DCH.Sample

of the AMR-WB Calls
73428417
RWB.FACH.Cum

of the AMR-WB Calls
73428418
RWB.FACH.Sample

of the AMR-WB Calls
73428413
RWB.Idle.Cum

of the AMR-WB Calls
for Cell
73428414
RWB.Idle.Sample

of the AMR-WB Calls
for Cell
73428419
RWB.PCH.Cum

of the AMR-WB Calls
CELL_PCH/URA_PCH
State for Cell
73428420
RWB.PCH.Sample

of the AMR-WB Calls
CELL_PCH/URA_PCH
State for Cell
Description
best cell.
Issue 03 (2015-06-30)

1413
BSC6900 UMTS
Measurement point
The RNC measures the access delay of the AMR-WB calls initiated by UEs in idle mode, in
redirection- and handover-based CSFB. At the end of the measurement period, the RNC obtains
the average access delay by dividing the accumulated access delay by the number of successful
AMR-WB calls initiated by UEs in the cell.
Formula
VS.OrigCall.EstabMeanTime.AMRWB = ([VS.OrigCall.EstabTime.AMRWB.Idle.Cum]+
[VS.OrigCall.EstabTime.AMRWB.DCH.Cum]+
[VS.OrigCall.EstabTime.AMRWB.FACH.Cum]+
[VS.OrigCall.EstabTime.AMRWB.PCH.Cum]+
[VS.OrigCall.EstabTime.AMRWB.CSFB.Redir.Cum]+
[VS.OrigCall.EstabTime.AMRWB.CSFB.PSHO.Cum])/
([VS.OrigCall.EstabTime.AMRWB.Idle.Sample]+
[VS.OrigCall.EstabTime.AMRWB.CSFB.Redir.Sample]+
[VS.OrigCall.EstabTime.AMRWB.DCH.Sample]+
[VS.OrigCall.EstabTime.AMRWB.FACH.Sample]+
[VS.OrigCall.EstabTime.AMRWB.PCH.Sample]+
[VS.OrigCall.EstabTime.AMRWB.CSFB.PSHO.Sample])
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
e.AMRWB
WRFD-010501
WRFD-010613

Rate Wide Band)
Number of Times that the Access Delay of AMR-NB Calls Is GOOD, MEDIUM,
and BAD for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428425
VS.OrigCall.EstabDelay.Go
od.Num.AMRNB
Number of Times that the

Access Delay of AMR-NB
Calls Is GOOD for Cell
73428426
VS.OrigCall.EstabDelay.Me
dium.Num.AMRNB

Calls Is MEDIUM for Cell

1414
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428427
VS.OrigCall.EstabDelay.Ba
d.Num.AMRNB

Calls Is BAD for Cell
Description
These counters provide the number of times that the access delay of the AMR-NB calls is GOOD,
MEDIUM, and BAD in the best cell, respectively.
Counter Name
Description
VS.OrigCall.EstabDelay.Good.Num.AMRN
B

that the access delay of AMR-NB calls is
smaller than or equal to AMRDelayGoodThd
in the best cell. The AMRDelayGoodThd
parameter is set in the SET
USERVPFMPARA command.
VS.OrigCall.EstabDelay.Medium.Num.AM
RNB

greater than AMRDelayGoodThd but smaller
than or equal to AMRDelayBadThd in the
best cell. Both the AMRDelayGoodThd and
AMRDelayBadThd parameters are set in the
SET USERVPFMPARA command.
VS.OrigCall.EstabDelay.Bad.Num.AMRN
B

greater than AMRDelayBadThd in the best
cell. The AMRDelayBadThd parameter is set
in the SET USERVPFMPARA command.
Measurement point
The RNC measures the access delay of the AMR-NB calls initiated by UEs in idle mode, in
redirection- and handover-based CSFB. The RNC then compares the access delay with the access
delay thresholds (AMRDelayGoodThd and AMRDelayBadThd) and measures the
corresponding counter in the best cell accordingly.
Formula
None
Issue 03 (2015-06-30)

1415
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
od.Num.AMRNB
WRFD-010501
dium.Num.AMRNB
WRFD-010501
d.Num.AMRNB
WRFD-010501
Number of Times that the Access Delay of AMR-WB Calls Is GOOD, MEDIUM,
and BAD for Cell
Counters
Counter ID
Counter Name
Counter Description
73428428
od.Num.AMRWB

Access Delay of AMR-WB
Calls Is GOOD for Cell
73428429
dium.Num.AMRWB

Calls Is MEDIUM for Cell
73428430
d.Num.AMRWB

Calls Is BAD for Cell
Description
These counters provide the number of times that the access delay of the AMR-WB calls is
GOOD, MEDIUM, and BAD in the best cell, respectively.
Issue 03 (2015-06-30)

1416
BSC6900 UMTS
Counter Name
Description
VS.OrigCall.EstabDelay.Good.Num.AMR
WB

that the access delay of AMR-WB calls is
smaller than or equal to AMRDelayGoodThd
in the best cell. The AMRDelayGoodThd
parameter is set in the SET
VS.OrigCall.EstabDelay.Medium.Num.AM
RWB

greater than AMRDelayGoodThd but smaller
than or equal to AMRDelayBadThd in the
best cell. Both the AMRDelayGoodThd and
AMRDelayBadThd parameters are set in the
SET USERVPFMPARA command.
VS.OrigCall.EstabDelay.Bad.Num.AMRW
B

greater than AMRDelayBadThd in the best
cell. The AMRDelayBadThd parameter is set
in the SET USERVPFMPARA command.
Measurement point
The RNC measures the access delay of the AMR-WB calls initiated by UEs in idle mode, in
redirection- and handover-based CSFB. The RNC then compares the access delay with the access
delay thresholds (AMRDelayGoodThd and AMRDelayBadThd) and measures the
corresponding counter in the best cell accordingly.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
od.Num.AMRWB
WRFD-010501
WRFD-010613

Rate Wide Band)

1417
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
dium.Num.AMRWB
WRFD-010501
WRFD-010613

Rate Wide Band)
d.Num.AMRWB
WRFD-010501
WRFD-010613

Rate Wide Band)
Number of AMR-NB RABs Abnormally Released by the CN for Cell

Counters
Counter ID
Counter Name
Counter Description
73428431
VS.RAB.Rel.AMRNB.CNA
bnormal
Number of AMR-NB RABs

Abnormally Released by the
CN for Cell
Description
This counter provides the number of AMR-NB RABs that are abnormally released by the CS
domain of the CN in the best cell.This counter complies with section "9.1.3 RAB ASSIGNMENT
REQUEST" and "9.2.1.4 Cause" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A in figure 1. When receiving from the CS domain of the
CN a RAB ASSIGNMENT REQUEST message with a cause value other than "Normal Release",
"Successful Relocation", "User Inactivity", "Network Optimization", or "UE Generated
Signalling Connection Release", this counter is increased by one if the RNC did not send a RAB
RELEASE REQUEST message to the CN.
Issue 03 (2015-06-30)

1418
BSC6900 UMTS
CN an IU RELEASE COMMAND message with a cause value other than "Normal Release",
Signalling Connection Release", this counter is increased by one if the RNC did not send an IU
RELEASE REQUEST or RAB RELEASE REQUEST message to the CN.
Issue 03 (2015-06-30)

1419
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.AMRNB.CNA
bnormal
WRFD-010501
Number of AMR-WB RABs Abnormally Released by the CN for Cell

Counters
Counter ID
Counter Name
Counter Description
73428432
VS.RAB.Rel.AMRWB.CN
Abnormal
Number of AMR-WB RABs

CN for Cell
Description
This counter provides the number of AMR-WB RABs that are abnormally released by the CS
domain of the CN in the best cell.This counter complies with section "9.1.3 RAB ASSIGNMENT
REQUEST" and "9.2.1.4 Cause" in 3GPP TS 25.413 (v10.10.0).
Measurement point
CN a RAB ASSIGNMENT REQUEST message with a cause value other than "Normal Release",
Signalling Connection Release", this counter is increased by one if the RNC did not send a RAB
RELEASE REQUEST message to the CN.
Issue 03 (2015-06-30)

1420
BSC6900 UMTS
CN an IU RELEASE COMMAND message with a cause value other than "Normal Release",
Signalling Connection Release", this counter is increased by one if the RNC did not send an IU
RELEASE REQUEST or RAB RELEASE REQUEST message to the CN.
Issue 03 (2015-06-30)

1421
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.AMRWB.CN
Abnormal
WRFD-010501
WRFD-010613

Rate Wide Band)
Number of Times the Alerting Procedure Is Initiated in Parallel with the RAB Setup
Procedure for Cell
Counters
Counter ID
Counter Name
Counter Description
73430084
VS.RAB.AttEstabCS.Parall
el.Alerting
Number of Times the

Initiated in Parallel with the
RAB Setup Procedure for
Cell
Description
This counter measures the number of times the alerting procedure is initiated in parallel with the
RAB setup procedure in a cell.
Measurement point
The measurement is triggered at point A in the figure. When the RNC initiates an alerting
procedure in parallel with the RAB setup procedure and sends a DIRECT TRANSFER(SETUP)
message to the UE, this counter is measured.
Issue 03 (2015-06-30)

1422
BSC6900 UMTS
Formula
None
Unit
None
Issue 03 (2015-06-30)

1423
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabCS.Parall
el.Alerting
WRFD-171202
Number of Times the Alerting Procedure Is Successfully Initiated in Parallel with

the RAB Setup Procedure for Cell
Counters
Counter ID
Counter Name
Counter Description
73430085
VS.RAB.SuccEstabCS.Paral
lel.Alerting
Number of Times the

Successfully Initiated in
Parallel with the RAB Setup
Procedure for Cell
Description
This counter measures the number of times the alerting procedure is successfully initiated in
parallel with the RAB setup procedure in a cell.
Measurement point
The measurement is triggered at point B in the figure. When the RNC initiates an alerting
procedure in parallel with the RAB setup procedure and sends a DIRECT TRANSFER(SETUP)
message to the UE, this counter is measured if the RNC receives an RADIO BEARER SETUP
COMPLETE message from the UE.
Issue 03 (2015-06-30)

1424
BSC6900 UMTS
Formula
None
Unit
None
Issue 03 (2015-06-30)

1425
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabCS.Paral
lel.Alerting
WRFD-171202
Average Access Delay of the Calling Party for AMR-NB Services When the Called
Party Uses Ultrafast CS Call Setup for Cell
Counters
Counter ID
Counter Name
Counter Description
73446291
e.AMRNB.UltraFastCSAccess

Calling Party for AMR-NB
Services When the Called
Party Uses Ultrafast CS Call
Setup for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73430087
e.AMRNB.UltraFastCSAcc
ess.sample

of the Calling Party for
AMR-NB Services When the
Called Party Uses Ultrafast
CS Call Setup for Cell
73430086
e.AMRNB.UltraFastCSAcc
ess.sum

Called Party Uses Ultrafast
CS Call Setup for Cell
Description
This counter measures the average access delay of the calling party that uses AMR-NB while
the called party uses the Ultrafast CS Call Setup feature in the best cell.
Measurement point
In scenarios where the calling party of an AMR-NB service is in Idle state or in redirectionbased CSFB and the called party uses the Ultrafast CS Call Setup feature, the RNC records point
Issue 03 (2015-06-30)

1426
BSC6900 UMTS
A in the figure as T1 and records point B as T2. The access delay of this AMR-NB service equals
T2 minus T1. At the end of the measurement period, the RNC obtains the average access delay
by dividing the accumulated access delay by the number of successful AMR-NB services
initiated by UEs in the cell. This counter is measured only when the function of parallel paging
processing is enabled.
Figure 1-609 Successful call setup procedure initiated by UE in idle mode or performing
redirection-based CSFB
In scenarios where the calling party of an AMR-NB service is in CELL_DCH or in CELL_FACH

state and the called party uses the Ultrafast CS Call Setup feature, the RNC records point A in
the figure as T1 and records point B as T2. The access delay of this AMR-NB service equals T2
minus T1. At the end of the measurement period, the RNC obtains the average access delay by
dividing the accumulated access delay by the number of successful AMR-NB services initiated
by UEs in the cell. This counter is measured only when the function of parallel paging processing
is enabled.
Issue 03 (2015-06-30)

1427
BSC6900 UMTS
Figure 1-610 Successful CS call setup procedure initiated by UE in CELL_FACH or

CELL_DCH state
In scenarios where the calling party of an AMR-NB service is in CELL_PCH and URA_PCH
states and the called party uses the Ultrafast CS Call Setup feature, the RNC records point A in
the figure as T1 and records point B as T2. The access delay of this AMR-NB service equals T2
minus T1. At the end of the measurement period, the RNC obtains the average access delay by
dividing the accumulated access delay by the number of successful AMR-NB services initiated
by UEs in the cell. This counter is measured only when the function of parallel paging processing
is enabled.
Issue 03 (2015-06-30)

1428
BSC6900 UMTS
Figure 1-611 Successful CS call setup procedure initiated by UE in CELL_PCH and URA_PCH
states
In scenarios where the calling party of an AMR-NB service is in handover-based CSFB and the
called party uses the Ultrafast CS Call Setup feature, the RNC records point A in the figure as
T1 and records point B as T2. The access delay of this AMR-NB service equals T2 minus T1.
At the end of the measurement period, the RNC obtains the average access delay by dividing
the accumulated access delay by the number of successful AMR-NB services initiated by UEs
in the cell. This counter is measured only when the function of parallel paging processing is
enabled.
Issue 03 (2015-06-30)

1429
BSC6900 UMTS
Figure 1-612 Successful CS call setup procedure initiated by UE performing handover-based

CSFB
Formula
VS.OrigCall.EstabMeanTime.AMRNB.UltraFastCSAccess =
[VS.OrigCall.EstabMeanTime.AMRNB.UltraFastCSAccess.sum]/
[VS.OrigCall.EstabMeanTime.AMRNB.UltraFastCSAccess.sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRNB.UltraFastCSAccess
WRFD-171202

1430
BSC6900 UMTS
Average Access Delay of the Calling Party for AMR-WB Services When the Called
Party Uses Ultrafast CS Call Setup for Cell
Counters
Counter ID
Counter Name
Counter Description
73446292
e.AMRWB.UltraFastCSAccess

Calling Party for AMR-WB
Services When the Called
Party Uses Ultrafast CS Call
Setup for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73430089
e.AMRWB.UltraFastCSAcc
ess.sample

AMR-WB Services When
the Called Party Uses
Ultrafast CS Call Setup for
Cell
73430088
e.AMRWB.UltraFastCSAcc
ess.sum

the Called Party Uses
Ultrafast CS Call Setup for
Cell
Description
This counter provides the average access delay of AMR-WB services initiated by the calling
party when the called party uses the Ultrafast CS Call Setup feature in the best cell.
Measurement point
In scenarios where the calling party of an AMR-WB service is in Idle state or in redirectionbased CSFB and the called party uses the Ultrafast CS Call Setup feature, the RNC records point
A in the figure as T1 and records point B as T2. The access delay of this AMR-WB service
equals T2 minus T1. At the end of the measurement period, the RNC obtains the average access
delay by dividing the accumulated access delay by the number of successful AMR-WB services
Issue 03 (2015-06-30)

1431
BSC6900 UMTS
In scenarios where the calling party of an AMR-WB service is in CELL_DCH or CELL_FACH

state and the called party uses the Ultrafast CS Call Setup feature, the RNC records point A in
the figure as T1 and records point B as T2. The access delay of this AMR-WB service equals
by dividing the accumulated access delay by the number of successful AMR-WB services
Issue 03 (2015-06-30)

1432
BSC6900 UMTS

CELL_DCH state
In scenarios where the calling party of an AMR-WB service is in CELL_PCH and URA_PCH
states and the called party uses the Ultrafast CS Call Setup feature, the RNC records point A in
the figure as T1 and records point B as T2. The access delay of this AMR-WB service equals
by dividing the accumulated access delay by the number of successful AMR-WB services
Issue 03 (2015-06-30)

1433
BSC6900 UMTS
states
In scenarios where the calling party of an AMR-WB service is in handover-based CSFB and the
called party uses the Ultrafast CS Call Setup feature, the RNC records point A in the figure as
T1 and records point B as T2. The access delay of this AMR-WB service equals T2 minus T1.
At the end of the measurement period, the RNC obtains the average access delay by dividing
the accumulated access delay by the number of successful AMR-WB services initiated by UEs
in the cell. This counter is measured only when the function of parallel paging processing is
enabled.
Issue 03 (2015-06-30)

1434
BSC6900 UMTS

CSFB
Formula
VS.OrigCall.EstabMeanTime.AMRWB.UltraFastCSAccess =
[VS.OrigCall.EstabMeanTime.AMRWB.UltraFastCSAccess.sum]/
[VS.OrigCall.EstabMeanTime.AMRWB.UltraFastCSAccess.sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRWB.UltraFastCSAccess
WRFD-171202

1435
BSC6900 UMTS
Average Access Delay of AMR-NB Services Initiated by the Called Party for Cell
Counters
Counter ID
Counter Name
Counter Description
73446299
VS.TermCall.EstabMeanTi
me.AMRNB
Average Access Delay of

AMR-NB Services Initiated
by the Called Party for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73430103
me.AMRNB.sample

of AMR-NB Services
Initiated by the Called Party
for Cell
73430102
me.AMRNB.sum

of AMR-NB Services
for Cell
Description
This counter measures the average access delay of AMR-NB services initiated by the called
party in the best cell.
Measurement point
The RNC determines that the AMR-NB service is initiated by a UE in the Idle state or in
redirection-based CSFB. The RNC records the point A in the figure as T1, and records point B
as T2. The access delay of this AMR-NB service equals T2 minus T1. At the end of the
access delay of AMR-NB services initiated by the called party by the number of times AMRNB services successfully initiated by the called party in the cell.
Issue 03 (2015-06-30)

1436
BSC6900 UMTS
Figure 1-617 Successful call setup procedure on the called party side when the calling party is
in idle mode or performing redirection-based CSFB
The RNC determines that the AMR-NB service is initiated by a UE in the CELL_DCH or
CELL_FACH state. The RNC records the point A in the figure as T1, and records point B as
T2. The access delay of this AMR-NB service equals T2 minus T1. At the end of the
access delay of AMR-NB services initiated by the called party by the number of times AMRNB services successfully initiated by the called party in the cell.
Issue 03 (2015-06-30)

1437
BSC6900 UMTS
Figure 1-618 Successful CS call setup procedure on the called party side when the calling party
is in CELL_FACH or CELL_DCH state
The RNC determines that the AMR-NB service is initiated by a UE in the CELL_PCH and
URA_PCH states. The RNC records the point A in the figure as T1, and records point B as T2.
The access delay of this AMR-NB service equals T2 minus T1. At the end of the measurement
period, the RNC obtains the average access delay by dividing the accumulated access delay of
AMR-NB services initiated by the called party by the number of times AMR-NB services
successfully initiated by the called party in the cell.
Issue 03 (2015-06-30)

1438
BSC6900 UMTS
is in CELL_PCH and URA_PCH states
The RNC determines that the AMR-NB service is initiated by a UE performing handover-based
CSFB. The RNC records the point A in the figure as T1, and records point B as T2. The access
delay of this AMR-NB service equals T2 minus T1. At the end of the measurement period, the
RNC obtains the average access delay by dividing the accumulated access delay of AMR-NB
services initiated by the called party by the number of times AMR-NB services successfully
initiated by the called party in the cell.
Issue 03 (2015-06-30)

1439
BSC6900 UMTS
is performing handover-based CSFB
Formula
VS.TermCall.EstabMeanTime.AMRNB = [VS.TermCall.EstabMeanTime.AMRNB.sum]/
[VS.TermCall.EstabMeanTime.AMRNB.sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
me.AMRNB
WRFD-171202

1440
BSC6900 UMTS
Average Access Delay of AMR-WB Services Initiated by the Called Party for Cell
Counters
Counter ID
Counter Name
Counter Description
73446306
me.AMRWB
Average Access Delay of

AMR-WB Services Initiated
by the Called Party for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73430117
me.AMRWB.sample

of AMR-WB Services
for Cell
73430116
me.AMRWB.sum

of AMR-WB Services
for Cell
Description
This counter measures the average access delay of AMR-WB services initiated by the called
party in the best cell.
Measurement point
In scenarios where an AMR-WB service is initiated by a UE in the Idle state or in the redirectionbased CSFB, the RNC records point A in the figure as T1 and records point B as T2. The access
delay of this AMR-WB service equals T2 minus T1. At the end of the measurement period, the
RNC obtains the average access delay by dividing the accumulated access delay of AMR-WB
services initiated by the called party by the number of times AMR-WB services successfully
initiated by the called party in the cell.
Issue 03 (2015-06-30)

1441
BSC6900 UMTS
Figure 1-621 Successful call setup procedure on the called party side when the calling party is
in idle mode or performing redirection-based CSFB
In scenarios where an AMR-WB service is initiated by a UE in the CELL_DCH or CELL_FACH

state, the RNC records point A in the figure as T1 and records point B as T2. The access delay
of this AMR-WB service equals T2 minus T1. At the end of the measurement period, the RNC
obtains the average access delay by dividing the accumulated access delay of AMR-WB services
initiated by the called party by the number of times AMR-WB services successfully initiated by
the called party in the cell.
Issue 03 (2015-06-30)

1442
BSC6900 UMTS
is in CELL_FACH or CELL_DCH state
In scenarios where an AMR-WB service is initiated by a UE in the CELL_PCH and URA_PCH

states, the RNC records point A in the figure as T1 and records point B as T2. The access delay
of this AMR-WB service equals T2 minus T1. At the end of the measurement period, the RNC
obtains the average access delay by dividing the accumulated access delay of AMR-WB services
Issue 03 (2015-06-30)

1443
BSC6900 UMTS
is in CELL_PCH and URA_PCH states
In scenarios where an AMR-WB service is initiated by a UE in the handover-based CSFB, the

RNC records point A in the figure as T1 and records point B as T2. The access delay of this
AMR-WB service equals T2 minus T1. At the end of the measurement period, the RNC obtains
the average access delay by dividing the accumulated access delay of AMR-WB services
Issue 03 (2015-06-30)

1444
BSC6900 UMTS
is performing handover-based CSFB
Formula
VS.TermCall.EstabMeanTime.AMRWB = [VS.TermCall.EstabMeanTime.AMRWB.sum]/
[VS.TermCall.EstabMeanTime.AMRWB.sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
me.AMRWB
WRFD-171202

1445
BSC6900 UMTS
Average Access Delay of the Calling Party for AMR-NB Services When the Calling
Party and Called Party Are Both Under Huawei RNCs for Cell
Counters
Counter ID
Counter Name
Counter Description
73446356
e.AMRNB.IntraVendor

Calling Party for AMR-NB
Services When the Calling
Party and Called Party Are
Both Under Huawei RNCs
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73430285
e.AMRNB.IntraVendor.sam
ple

Calling Party and Called
Party Are Both Under
Huawei RNCs for Cell
73430286
e.AMRNB.IntraVendor.sum

Calling Party and Called
Description
This counter provides the average access delay of the calling parties for AMR-NB services in
the best cell. This counter is measured only when the following conditions are met: (1) The
calling party and called party are both under Huawei RNCs. (2) The CallEstTimePfmSwitch is
set to ON and the TrFO function is enabled on the CN side.
Measurement point
The RNC determines that an AMR-NB service is initiated by a UE in idle mode or in redirectionbased CSFB and that the calling party and called party are both under Huawei RNCs. In the
figure, the RNC records the time at point A as T1, and records the time at point B as T2. The
access delay of this AMR-NB service equals T2 minus T1. At the end of a measurement period,
the RNC obtains the average access delay by dividing the accumulated access delay of AMRIssue 03 (2015-06-30)

1446
BSC6900 UMTS
NB services initiated by UEs by the number of times that AMR-NB services are successfully
initiated in the cell.
The RNC determines that an AMR-NB service is initiated by a UE in the CELL_DCH or

CELL_FACH state and that the calling party and called party are both under Huawei RNCs. In
the figure, the RNC records the time at point A as T1, and records the time at point B as T2. The
the RNC obtains the average access delay by dividing the accumulated access delay of AMRNB services initiated by UEs by the number of times that AMR-NB services are successfully
Issue 03 (2015-06-30)

1447
BSC6900 UMTS

CELL_DCH state
The RNC determines that an AMR-NB service is initiated by a UE in the CELL_PCH and
URA_PCH states and that the calling party and called party are both under Huawei RNCs. In
the RNC obtains the average access delay by dividing the accumulated access delay of AMRNB services initiated by UEs by the number of times that AMR-NB services are successfully
Issue 03 (2015-06-30)

1448
BSC6900 UMTS
states
The RNC determines that an AMR-NB service is initiated by a UE in the handover-based CSFB
and that the calling party and called party are both under Huawei RNCs. In the figure, the RNC
records the time at point A as T1, and records the time at point B as T2. The access delay of this
AMR-NB service equals T2 minus T1. At the end of a measurement period, the RNC obtains
the average access delay by dividing the accumulated access delay of AMR-NB services initiated
by UEs by the number of times that AMR-NB services are successfully initiated in the cell.
Issue 03 (2015-06-30)

1449
BSC6900 UMTS

CSFB
Formula
VS.OrigCall.EstabMeanTime.AMRNB.IntraVendor =
[VS.OrigCall.EstabMeanTime.AMRNB.IntraVendor.sum]/
[VS.OrigCall.EstabMeanTime.AMRNB.IntraVendor.sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRNB.IntraVendor
WRFD-171202

1450
BSC6900 UMTS
Average Access Delay of the Calling Party for AMR-WB Services When the Calling
Party and Called Party Are Both Under Huawei RNCs for Cell
Counters
Counter ID
Counter Name
Counter Description
73446357
e.AMRWB.IntraVendor

Calling Party for AMR-WB
Services When the Calling
Party and Called Party Are
Both Under Huawei RNCs
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73430287
e.AMRWB.IntraVendor.sa
mple

the Calling Party and Called
73430288
e.AMRWB.IntraVendor.su
m

the Calling Party and Called
Description
This counter provides the average access delay of the calling parties for AMR-WB services in
the best cell. This counter is measured only when the following conditions are met: (1) The
calling party and called party are both under Huawei RNCs. (2) The CallEstTimePfmSwitch is
set to ON and the TrFO function is enabled on the CN side.
Measurement point
The RNC determines that an AMR-WB service is initiated by a UE in idle mode or in redirectionbased CSFB and that the calling party and called party are both under Huawei RNCs. In the
figure, the RNC records the time at point A as T1, and records the time at point B as T2. The
access delay of this AMR-WB service equals T2 minus T1. At the end of a measurement period,
the RNC obtains the average access delay by dividing the accumulated access delay of AMRIssue 03 (2015-06-30)

1451
BSC6900 UMTS
WB services initiated by UEs by the number of times that AMR-WB services are successfully
The RNC determines that an AMR-WB service is initiated by a UE in the CELL_DCH or

CELL_FACH state and that the calling party and called party are both under Huawei RNCs. In
the RNC obtains the average access delay by dividing the accumulated access delay of AMRWB services initiated by UEs by the number of times that AMR-WB services are successfully
Issue 03 (2015-06-30)

1452
BSC6900 UMTS

CELL_DCH state
The RNC determines that an AMR-WB service is initiated by a UE in the CELL_PCH and
URA_PCH states and that the calling party and called party are both under Huawei RNCs. In
the RNC obtains the average access delay by dividing the accumulated access delay of AMRWB services initiated by UEs by the number of times that AMR-WB services are successfully
Issue 03 (2015-06-30)

1453
BSC6900 UMTS
states
The RNC determines that an AMR-WB service is initiated by a UE in the handover-based CSFB
and that the calling party and called party are both under Huawei RNCs. In the figure, the RNC
records the time at point A as T1, and records the time at point B as T2. The access delay of this
AMR-WB service equals T2 minus T1. At the end of a measurement period, the RNC obtains
the average access delay by dividing the accumulated access delay of AMR-WB services
initiated by UEs by the number of times that AMR-WB services are successfully initiated in the
cell.
Issue 03 (2015-06-30)

1454
BSC6900 UMTS

CSFB
Formula
VS.OrigCall.EstabMeanTime.AMRWB.IntraVendor =
[VS.OrigCall.EstabMeanTime.AMRWB.IntraVendor.sum]/
[VS.OrigCall.EstabMeanTime.AMRWB.IntraVendor.sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.AMRWB.IntraVendor
WRFD-171202

1455
BSC6900 UMTS
Average Value of the Smaller of the Delay in the Uu Security Mode and Iu Setup
Procedures for Cell
Counters
Counter ID
Counter Name
Counter Description
73446358
VS.UuSecMod.IuSetup.Min
Delay
Average Value of the Smaller

of the Delay in the Uu
Security Mode and Iu Setup
Procedures for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73430290
Delay.sample

Accumulated Value of the
Smaller in the Delay of the
Uu Security Mode and Iu
Setup Procedures for Cell
73430289
Delay.sum
Accumulated Value of the

Smaller of the Delay in the
Uu Security Mode and Iu
Setup Procedures for Cell
Description
This counter averages the smaller of the delay of the Uu security mode and Iu setup procedures
for all UEs in the best cell.
Measurement point
When the called party establishes an AMR service, the RNC sends a SECURITY MODE
COMMAND message to the UE and records the send time (T1) at point A in the figure. When
receiving a SECURITY MODE COMPLETE message from the UE, the RNC records the receive
time T2 at point B. Assume that delta T1 is the delay of this Uu security mode procedure. Delta
T1 equals T2 minus T1. The RNC subsequently sends a SECURITY MODE COMPLETE
message to the CN and records the send time T3 at point C. When receiving a DIRECT
TRANSFER (SETUP) message, the RNC records the receive time T4 at point D. Assume that
delta T2 is the delay of this Iu setup procedure. Delta T2 equals T4 minus T3. Assume that delta
T is the smaller of delta T1 and delta T2. At the end of a measurement period, the system obtains
the value of this counter by dividing the accumulated delta T for all UEs by the number of times
sampled.
Issue 03 (2015-06-30)

1456
BSC6900 UMTS
Figure 1-633 Uu security mode and Iu setup procedures
When the called party establishes an AMR service, the RNC sends a SECURITY MODE
COMMAND message to the UE and records the send time (T1) at point A in the figure. When
receiving a SECURITY MODE COMPLETE message from the UE, the RNC records the receive
time T2 at point B. Assume that delta T1 is the delay of this Uu security mode procedure. Delta
T1 equals T2 minus T1. The RNC subsequently sends a SECURITY MODE COMPLETE
message to the CN and records the send time T3 at point C. When receiving a DIRECT
TRANSFER (SETUP) message, the RNC records the receive time T4 at point D. Assume that
delta T2 is the delay of this Iu setup procedure. Delta T2 equals T4 minus T3. Assume that delta
T is the smaller of delta T1 and delta T2. At the end of a measurement period, the system obtains
the value of this counter by dividing the accumulated delta T for all UEs by the number of times
sampled.
Issue 03 (2015-06-30)

1457
BSC6900 UMTS
Figure 1-634 Parallel Uu security mode and Iu setup procedures
Formula
VS.UuSecMod.IuSetup.MinDelay = [VS.UuSecMod.IuSetup.MinDelay.sum]/
[VS.UuSecMod.IuSetup.MinDelay.sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Delay
WRFD-171202

1458
BSC6900 UMTS
Average Delay of CS RAB Setups for Cell

Counters
Counter ID
Counter Name
Counter Description
73446359
VS.RAB.EstabCS.MeanTime
Average Delay of CS RAB

Setups for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73430292
VS.RAB.EstabCS.MeanTim
e.sample
Sampling Times of
Accumulated Delay of CS
RAB Setups for Cell
73430291
VS.RAB.EstabCS.MeanTim
e.sum
Accumulated Delay of CS
RAB Setups for Cell
Description
This counter provides the average delay of CS RAB setup in the best cell.
Measurement point
When receiving a RAB ASSIGNMENT REQUEST message for a CS RAB, the RNC records
the receive time T1 at point A in figure 1. 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. (When the parallel handling of the alerting and
RAB setup procedures takes effect, the successful CS RAB setup procedure is shown in figure
2. Under these circumstances, the time T2 is recorded after the RNC receives a RADIO BEARER
SETUP COMPLETE message from the UE.) Assume that delta T is the delay of this RAB setup.
Delta T equals T2 minus T1. At the end of a measurement period, the delay of CS RAB setups
for all UEs is accumulated and the number of successful CS RAB setups is also accumulated.
The value of this counter equals the accumulated delay of CS RAB setups for all UEs divided
by the accumulated number of successful CS RAB setups.
Issue 03 (2015-06-30)

1459
BSC6900 UMTS
Figure 1-635 Successful CS RAB setup procedure
When receiving a RAB ASSIGNMENT REQUEST message for a CS RAB, the RNC records
the receive time T1 at point A in figure 1. 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. (When the parallel handling of the alerting and
RAB setup procedures takes effect, the successful CS RAB setup procedure is shown in figure
2. Under these circumstances, the time T2 is recorded after the RNC receives a RADIO BEARER
SETUP COMPLETE message from the UE.) Assume that delta T is the delay of this RAB setup.
Delta T equals T2 minus T1. At the end of a measurement period, the delay of CS RAB setups
for all UEs is accumulated and the number of successful CS RAB setups is also accumulated.
The value of this counter equals the accumulated delay of CS RAB setups for all UEs divided
by the accumulated number of successful CS RAB setups.
Issue 03 (2015-06-30)

1460
BSC6900 UMTS
Figure 1-636 Successful CS RAB setup procedure (in parallel with the alerting procedure)
Formula
VS.RAB.EstabCS.MeanTime = [VS.RAB.EstabCS.MeanTime.sum]/
[VS.RAB.EstabCS.MeanTime.sample]
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.EstabCS.MeanTime
WRFD-171202
Number of Times the Uu Security Mode Procedure Is Parallel with the Iu Setup
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430293
VS.SecMod.Parallel.Setup.
Att
Number of Times the Uu

Security Mode Procedure Is
Parallel with the Iu Setup

1461
BSC6900 UMTS
Description
This counter provides the number of times the Uu security mode procedure is initiated in parallel
with the Iu setup procedure in the best cell.
Measurement point
The measurement is triggered at point A in the figure. When the parallel handling of the Uu
security mode and Iu setup procedure is enabled, this counter is measured after the RNC sends
a SECURITY MODE COMPLETE message to the CN.
Formula
None
Issue 03 (2015-06-30)

1462
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SecMod.Parallel.Setup.
Att
WRFD-171202
Number of Times the Uu Security Mode Procedure Is Successfully Initiated in

Parallel with the Iu Setup Procedure for Cell
Counters
Counter ID
Counter Name
Counter Description
73430294
VS.SecMod.Parallel.Setup.S
ucc
Number of Times the Uu

Security Mode Procedure Is
Successfully Initiated in
Parallel with the Iu Setup
Procedure for Cell
Description
This counter provides the number of times the Uu security mode procedure is successfully
initiated in parallel with Iu setup procedure in the best cell.
Measurement point
The measurement is triggered at point B in the figure. When the parallel handling of the Uu
security mode and Iu setup procedures is enabled, this counter is measured after the RNC sends
a non-access stratum (NAS) message Downlink Direct Transfer (SETUP) to the UE.
Issue 03 (2015-06-30)

1463
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SecMod.Parallel.Setup.S
ucc
WRFD-171202

1464
BSC6900 UMTS
1.12.11 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193111
VS.RRC.AttConnE
stab.EFACH
Number of RRC
Establishment
Requests on EFACH
for Cell
Earlier than
BSC6900
V900R011
67193112
VS.RRC.SuccConn
Estab.EFACH
Number of
Successful RRC
Establishments on
EFACH for Cell
Earlier than
BSC6900
V900R011
67193119
VS.RAB.AttEstPS.
EFACH
Number of PS RAB
Establishment
Requests on EFACH
for Cell
Earlier than
BSC6900
V900R011
67193120
VS.RAB.SuccEstP
S.EFACH
Number of
Successful PS RAB
Establishments on
EFACH for Cell
Earlier than
BSC6900
V900R011
67193121
VS.RAB.Estab.PS.
CellFACH.MaxTi
me
Maximum Duration
of PS RAB
Establishment
Process on FACH for
Cell
Earlier than
BSC6900
V900R011
67204169
VS.RAB.Estab.PS.
CellFACH.MeanTime
Mean Duration of PS
RAB Establishment
Process on FACH for
Cell
Earlier than
BSC6900
V900R011
67193127
VS.RAB.AbnormR
el.PS.EFACH
Number of
Abnormal RAB
Releases on EFACH
for Cell
Earlier than
BSC6900
V900R011

1465
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193128
VS.RAB.NormRel.
PS.EFACH
Number of Normal
PS RAB Release on
EFACH for Cell
Earlier than
BSC6900
V900R011
67204778
VS.CRNCIubBytes
EFACH.Tx
Number of Bytes of
MAC PDUs Sent on
IUB EFACH FP for
Cell
Earlier than
BSC6900
V900R011
73410512
VS.EFACHUEs
Number of UEs
carried on EFACH
for Cell
Earlier than
BSC6900
V900R011
73421757
VS.RRC.ConnEsta
bTimeMax.CellFA
CH.EFACH
Maximum Duration
of RRC
Establishment
Process on EFACH
for Cell
BSC6900
V900R012
73439900
VS.RRC.ConnEsta
bTimeMean.CellF
ACH.EFACH
Mean Duration of
RRC Establishment
Process on EFACH
for Cell
BSC6900
V900R012
73441122
VS.EDRXUEs
Number of UEs
Carried on the
EFACH and Using
E-DRX
BSC6900
V900R013
73426149
VS.EFACH.F2D.At
t
Number of Attempts
at State Transitions
from Enhanced
CELL_FACH to
CELL_DCH (DCH)
for Cell
BSC6900
V900R015C00
73426150
VS.EFACH.D2F.At
t
Number of Attempts
from CELL_DCH
(DCH) to Enhanced
CELL_FACH for
Cell
BSC6900
V900R015C00
73426151
VS.EFACH.F2D.S
ucc
Number of
Successful State
Transitions from
Enhanced
CELL_FACH to
CELL_DCH (DCH)
for Cell
BSC6900
V900R015C00

1466
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426152
VS.EFACH.D2F.S
ucc
Number of
Successful State
Transitions from
CELL_DCH (DCH)
to Enhanced
CELL_FACH for
Cell
BSC6900
V900R015C00
73426153
VS.EFACH.H2F.S
ucc
Number of
Successful State
Transitions from
CELL_DCH (HSDSCH) to Enhanced
CELL_FACH for
Cell
BSC6900
V900R015C00
73426154
VS.EFACH.F2H.S
ucc
Number of
Successful State
Transitions from
Enhanced
CELL_FACH to
CELL_DCH (HSDSCH) for Cell
BSC6900
V900R015C00
73426155
VS.EFACH.F2H.A
tt
Number of Attempts
from Enhanced
CELL_FACH to
CELL_DCH (HSDSCH) for Cell
BSC6900
V900R015C00
73426156
VS.EFACH.H2F.A
tt
Number of Attempts
from CELL_DCH
(HS-DSCH) to
Enhanced
CELL_FACH for
Cell
BSC6900
V900R015C00
73426160
VS.EFACH.P2F.Su
cc
Number of
Successful State
Transitions from
CELL_PCH or
URA_PCH to
Enhanced
CELL_FACH for
Cell
BSC6900
V900R015C00

1467
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426159
VS.EFACH.P2F.At
t
Number of Attempts
from CELL_PCH or
URA_PCH to
Enhanced
CELL_FACH for
Cell
BSC6900
V900R015C00
73426158
VS.EFACH.F2P.Su
cc
Number of
Successful State
Transitions from
Enhanced
CELL_FACH to
CELL_PCH or
URA_PCH for Cell
BSC6900
V900R015C00
73426157
VS.EFACH.F2P.At
t
Number of Attempts
from Enhanced
CELL_FACH to
CELL_PCH or
URA_PCH for Cell
BSC6900
V900R015C00
73426171
VS.EFACHUEs.M
ax
Maximum Number
of UEs on E_FACH
for Cell
BSC6900
V900R015C00
Counter
Sub Counter
VS.EFACHUEs
VS.EDRXUEs
Number of RRC Connection Requests in a Cell (EFACH)

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193111
VS.RRC.AttConnEstab.EF
ACH
Number of RRC
Establishment Requests on
EFACH for Cell

1468
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.This counter does not include the RRC connection setup
requests in the Directed Signalling Connection Re-establishment (DSCR) procedure triggered
by the overlapping of the RRC connection setup procedure and cell update procedure.This
counter complies with section "8.1.3 RRC connection establishment" in 3GPP TS 25.331
(v10.13.0).
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.This counter does not include the RRC connection setup
by the overlapping of the RRC connection setup procedure and cell update procedure. The
measurement is triggered for only once if the RNC repeatedly receives the RRC CONNECTION
REQUEST message from the UE.
Figure 1-639 RRC connection setup success flow
Formula
None
Unit
None
Issue 03 (2015-06-30)

1469
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnEstab.EF
ACH
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Successful RRC Connection Setups in a Cell (EFACH)

Counters
Counter ID
Counter Name
Counter Description
67193112
VS.RRC.SuccConnEstab.EF
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.This counter complies with section "8.1.3 RRC connection
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.
Issue 03 (2015-06-30)

1470
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.SuccConnEstab.EF
ACH
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of PS RAB Setup Attempts on EFACH in a Cell

Counters
Counter ID
Counter Name
Counter Description
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.This counter
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.
Issue 03 (2015-06-30)

1471
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstPS.EFACH
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Successful PS RAB Setup on EFACH in a Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193120
VS.RAB.SuccEstPS.EFAC
H
RAB Establishments on
EFACH for Cell

1472
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.This counter complies with section "8.2.2 Reconfiguration
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
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstPS.EFAC
H
WRFD-010688
Downlink Enhanced
CELL_FACH

1473
BSC6900 UMTS
Signaling Delay of PS RAB Established on CCH in a Cell

Counters
Counter ID
Counter Name
Counter Description
67193121
VS.RAB.Estab.PS.CellFAC
H.MaxTime
RAB Establishment Process
on FACH for Cell
67204169
H.MeanTime

Establishment Process on
FACH for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
67193123
H.Cum
Accumulative Duration of PS
on FACH for Cell
67193124
H.Sample
Accumulative Duration of PS
on FACH for Cell
Description
These counters provide the signaling delay of PS RAB setup of the UE in CELL_FACH
status.The preceding counters comply with section "8.2.2 Reconfiguration procedures" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at points A and B, as shown in Figure: At point A, the RNC records
the time (T1) when it receives a RAB ASSIGNMENT REQUEST message and decides the PS
RAB is set up on the CCH. At point B, the RNC records the time (T2) when it sends a RAB
ASSIGNMENT RESPONSE message to the CN after receiving a RADIO BEARER SETUP
COMPLETE message. Suppose delta T represents the signaling delay of the RAB connection
setup. Then, delta T = T2 - T1 when the RRC connection is set up on the CCH.
Issue 03 (2015-06-30)

1474
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
Counter Name
Feature ID
Feature Name
H.MaxTime
WRFD-010688
Downlink Enhanced
CELL_FACH
H.MeanTime
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Abnormally Released PS RABs on the EFACH in a Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193127
VS.RAB.AbnormRel.PS.EF
ACH
Number of Abnormal RAB

Releases on EFACH for Cell

1475
BSC6900 UMTS
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.This counter complies with section "8.3.2 Successful
Measurement point
Release","UE Generated Signalling Connection 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.
COMMAND message(with the cause other than "User Inactivity","Normal Release","UE
Generated Signalling Connection Release", "Successful Relocation" or "Network
Issue 03 (2015-06-30)

1476
BSC6900 UMTS
Generated Signalling Connection Release", "Successful Relocation" or "Network
Issue 03 (2015-06-30)

1477
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.PS.EF
ACH
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Normal Released PS RABs on the EFACH in a Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193128
VS.RAB.NormRel.PS.EFA
CH
Number of Normal PS RAB

Release on EFACH for Cell

1478
BSC6900 UMTS
Description
This measurement item provides the number of normally released PS RABs on the EFACH in
the cell.This counter complies with section "8.3.2 Successful Operation" in 3GPP TS 25.413
(v10.10.0).
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.
Issue 03 (2015-06-30)

1479
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.PS.EFA
CH
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Downlink MAC PDU Bytes on the EFACH over the Iub Interface
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204778
VS.CRNCIubBytesEFACH.
Tx
Number of Bytes of MAC

PDUs Sent on IUB EFACH
FP for Cell

1480
BSC6900 UMTS
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 ,the MAC
headers and retransmitted 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 downlink MAC PDUs (including the signaling and service
data ,the MAC headers and retransmitted data,but not including the FP header) that are sent by
the CRNC on the EFACH over the Iub interface are accumulated in a cell.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.CRNCIubBytesEFACH.
Tx
WRFD-010688
Downlink Enhanced
CELL_FACH
Signaling Delay of RRC Established on EFACH in a Cell

Counters
Counter ID
Counter Name
Counter Description
73421757
ax.CellFACH.EFACH
Maximum Duration of RRC

EFACH for Cell
73439900
ean.CellFACH.EFACH
Mean Duration of RRC

EFACH for Cell
specific formulas.
Issue 03 (2015-06-30)

1481
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421758
CH.HSDSCH.Cum
Accumulative Duration of
RRC Establishment Process
on EFACH for Cell
73421759
CH.HSDSCH.Sample
Cumulative Duration of RRC
EFACH for Cell
Description
These counters provide the average and maximum durations of RRC signaling setups on the
EFACH in a cell.The preceding counters comply with section "8.1.3 RRC connection
Measurement point
As shown in the figure, when the RNC receives an RRC CONNECTION REQUEST message
at point A, it records the time T1. When the RNC receives an RRC CONNECTION SETUP
COMPLETE message at point C, it records the time T2. Assume that delta T is the duration of
RRC signaling setup on the EFACH in a cell, delta T = T2-T1. The RNC takes samples of the
durations of RRC signaling setups on the EFACH every 5 seconds. At the end of a measurement
period, the RNC obtains the average duration by dividing the accumulated number by the
sampling times. The maximum number in a measurement period is the maximum duration.
Issue 03 (2015-06-30)

1482
BSC6900 UMTS
Formula
VS.RRC.ConnEstabTimeMean.CellFACH.EFACH =
[VS.RRC.ConnEstabTime.CCH.HSDSCH.Cum]/
[VS.RRC.ConnEstabTime.CCH.HSDSCH.Sample]
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
ax.CellFACH.EFACH
WRFD-010688
Downlink Enhanced
CELL_FACH
ean.CellFACH.EFACH
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of UEs Carried on the EFACH or Those Carried on the EFACH and Using
E-DRX
Counters
Counter ID
Counter Name
Counter Description
73441122
VS.EDRXUEs
Number of UEs Carried on

the EFACH and Using EDRX
73410512
VS.EFACHUEs
Number of UEs carried on

EFACH for Cell
73426171
VS.EFACHUEs.Max

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
Issue 03 (2015-06-30)

1483
BSC6900 UMTS
sampling point is the maximum value obtained in a measurement period. The number of UEs
carried on the EFACH and using the E-DRX function in a cell is sampled every 5 seconds. At
the end of a measurement period, the average number of UEs that are carried on the EFACH
and use the E-DRX function is calculated by dividing the accumulated number of the UEs
measured at each sampling point by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EDRXUEs
WRFD-010702
Enhanced DRX
VS.EFACHUEs
WRFD-010688
Downlink Enhanced
CELL_FACH
VS.EFACHUEs.Max
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Attempts at State Transitions from Enhanced CELL_FACH to

CELL_DCH (DCH) for Cell
Counters
Counter ID
Counter Name
Counter Description
73426149
VS.EFACH.F2D.Att
Number of Attempts at State

Transitions from Enhanced
CELL_FACH to
73426150
VS.EFACH.D2F.Att

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 (EDCH) in a cell. Enhanced CELL_FACH refers to that a UE in the CELL_FACH state uses the
Issue 03 (2015-06-30)

1484
BSC6900 UMTS
HS-DSCH in the downlink.The preceding counters comply with section "8.2.2 Reconfiguration
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the UE a
RADIO BEARER RECONFIGURATION message during a state transition from CELL_DCH
(DCH) to enhanced CELL_FACH, this counter is measured in the best cell that the UE camps
on before the state transition. When the RNC sends the UE a RADIO BEARER
RECONFIGURATION message during a state transition from enhanced CELL_FACH to
CELL_DCH (DCH), this counter is measured in the cell that the UE currently camps on.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EFACH.F2D.Att
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-010688
Downlink Enhanced
CELL_FACH
Issue 03 (2015-06-30)

1485
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.EFACH.D2F.Att
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Successful State Transitions from Enhanced CELL_FACH to

Counters
Counter ID
Counter Name
Counter Description
73426151
VS.EFACH.F2D.Succ

CELL_FACH to
73426152
VS.EFACH.D2F.Succ

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
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.The preceding counters comply
with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

1486
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EFACH.F2D.Succ
WRFD-021101
Dynamic Channel
(DCCC)
WRFD-010688
Downlink Enhanced
CELL_FACH
VS.EFACH.D2F.Succ
WRFD-021101
WRFD-010688
Dynamic Channel
(DCCC)
Downlink Enhanced
CELL_FACH
Issue 03 (2015-06-30)

1487
BSC6900 UMTS

CELL_DCH (HS-DSCH) for Cell
Counters
Counter ID
Counter Name
Counter Description
73426154
VS.EFACH.F2H.Succ

CELL_FACH to
CELL_DCH (HS-DSCH) for
Cell
73426153
VS.EFACH.H2F.Succ

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.The preceding counters
comply with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

1488
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EFACH.F2H.Succ
WRFD-01061111
WRFD-010688
Downlink Enhanced
CELL_FACH
WRFD-01061111
WRFD-010688
Downlink Enhanced
CELL_FACH
VS.EFACH.H2F.Succ

CELL_DCH (HS-DSCH) for Cell
Counters
Counter ID
Counter Name
Counter Description
73426155
VS.EFACH.F2H.Att

CELL_FACH to
CELL_DCH (HS-DSCH) for
Cell
73426156
VS.EFACH.H2F.Att

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.The preceding counters
Issue 03 (2015-06-30)

1489
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EFACH.F2H.Att
WRFD-01061111
WRFD-010688
Downlink Enhanced
CELL_FACH
WRFD-01061111
WRFD-010688
Downlink Enhanced
CELL_FACH
VS.EFACH.H2F.Att
Issue 03 (2015-06-30)

1490
BSC6900 UMTS

Enhanced CELL_FACH for Cell
Counters
Counter ID
Counter Name
Counter Description
73426160
VS.EFACH.P2F.Succ

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.This counter
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, and RADIO BEARER
RECONFIGURATION COMPLETE.The measurement is triggered at point C, as shown in the
following figure.
Figure 1-654 cell update
Issue 03 (2015-06-30)

1491
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EFACH.P2F.Succ
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Attempts at State Transitions from CELL_PCH or URA_PCH to

Enhanced CELL_FACH for Cell
Counters
Counter ID
Counter Name
Counter Description
73426159
VS.EFACH.P2F.Att

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.This counter
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.
Issue 03 (2015-06-30)

1492
BSC6900 UMTS
Figure 1-655 cell update
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EFACH.P2F.Att
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-010688
Downlink Enhanced
CELL_FACH
Issue 03 (2015-06-30)

1493
BSC6900 UMTS

CELL_PCH or URA_PCH for Cell
Counters
Counter ID
Counter Name
Counter Description
73426158
VS.EFACH.F2P.Succ

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.This counter
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.
Formula
None
Issue 03 (2015-06-30)

1494
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EFACH.F2P.Succ
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-010688
Downlink Enhanced
CELL_FACH

CELL_PCH or URA_PCH for Cell
Counters
Counter ID
Counter Name
Counter Description
73426157
VS.EFACH.F2P.Att

CELL_FACH to
CELL_PCH or URA_PCH
for Cell
Description
This counter provides the number of UE attempts at state transitions from enhanced
CELL_FACH to CELL_PCH or URA_PCH in a cell. Enhanced CELL_FACH refers to the state
in which UEs stay in the CELL_FACH state but use HS-DSCHs in the downlink.This counter
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.
Issue 03 (2015-06-30)

1495
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EFACH.F2P.Att
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-010688
Downlink Enhanced
CELL_FACH
1.12.12 EPCH Measurement <per Cell>(EPCH.Cell)

Overview
UEs in the E-PCH state are those in the CELL_PCH or URA_PCH state and use the HS-DSCH
for downlink transmission.
The EPCH feature is introduced in 3GPP R7. It allows the PCCH to be mapped to the HS-DSCH
for UEs in the CELL_PCH or URA_PCH state and therefore enables transmission on the HSDSCH. It also allows the DCCH/DTCH to be mapped to the HS-DSCH for UEs in the
CELL_PCH state and therefore enables data transmission on the HS-DSCH. In this way,
downlink peak rate is increased and delay in signaling interaction is reduced.
Issue 03 (2015-06-30)

1496
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73441131
VS.EPCHUEs
Average Number of
UEs Carried on the
EPCH for Cell
BSC6900
V900R013
73441132
VS.EPCHUEs.DH
RNTI
Average Number of
UEs Carried on the
EPCH and Allocated
Dedicated H-RNTI
for Cell
BSC6900
V900R013
Counter
Sub Counter
VS.EPCHUEs
VS.EPCHUEs.DHRNTI
Average Number of UEs Carried on the EPCH or Those Carried on the EPCH and
Allocated Dedicated H-RNTI for Cell
Counters
Counter ID
Counter Name
Counter Description
73441131
VS.EPCHUEs
Average Number of UEs

Carried on the EPCH for Cell
73441132
VS.EPCHUEs.DHRNTI

Carried on the EPCH and
Allocated Dedicated HRNTI for Cell
Description
These counters provide the average number of UEs in the CELL_PCH state and carried on EPCH and the average number of those carried on the E-PCH and allocated dedicated HS-DSCH
Radio Network Temporary Identifier (H-RNTI) in a cell.
Measurement point
The number of UEs in the CELL_PCH state and carried on the E-PCH is sampled every 5
seconds. At the end of a measurement period, this counter is calculated by dividing the
Issue 03 (2015-06-30)

1497
BSC6900 UMTS
accumulated number of the UEs measured at each sampling point by the number of samples.
The number of UEs in the CELL_PCH state and carried on the E-PCH and allocated dedicated
H-RNTI are sampled every 5 seconds. At the end of a measurement period, this counter is
calculated by dividing the accumulated number of the UEs measured at each sampling point by
the number of samples.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EPCHUEs
WRFD-020134
Push to Talk
VS.EPCHUEs.DHRNTI
WRFD-020134
Push to Talk
1.12.13 ERACH Measurement <per Cell>(ERACH.Cell)

Overview
In ERACH mode, UEs in CELL_FACH state use the E-DCH as the uplink transport channel
and use the HS-DSCH as the downlink transport channel.
The ERACH feature is introduced in R8. The E-DCH carries message data, replacing the
traditional RACH for a higher uplink peak rate. In this way, delay of UEs in the IDLE mode or
in the CELL_FACH, CELL_PCH, or URA_PCH state on the user plane and control plane is
reduced and delay in transition from the CELL_FACH, CELL_PCH, or URA_PCH state to the
CELL_DCH state is reduced.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441118
VS.ERACHUEs
Number of UEs
Carried on ERACH
for Cell
BSC6900
V900R013
73423340
VS.RRC.AttConnE
stab.ERACH
Number of Requests
for Setting Up RRC
Connections on an
ERACH for Cell
BSC6900
V900R013

1498
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423341
VS.RRC.SuccConn
Estab.ERACH
Number of
Successful RRC
Connection Setups
on an ERACH for
Cell
BSC6900
V900R013
73423342
VS.RAB.AttEstabP
S.ERACH
Number of PS RAB
Setup Requests on an
ERACH for Cell
BSC6900
V900R013
73423343
VS.RAB.SuccEstab
PS.ERACH
Number of
Successful PS RAB
Setups on an
ERACH for Cell
BSC6900
V900R013
73423344
VS.RAB.NormRel.
PS.ERACH
Number of PS RABs
Normally Released
on an ERACH for
Cell
BSC6900
V900R013
73423345
VS.RAB.AbnormR
el.PS.ERACH
Number of PS RABs
Abnormally
Released on an
ERACH for Cell
BSC6900
V900R013
73423346
VS.RRC.ConnEsta
bTimeMax.ERAC
H
Maximum RRC
Connection Setup
Duration on an
ERACH for Cell
BSC6900
V900R013
73441135
VS.RRC.ConnEsta
bTimeMean.ERAC
H
Average RRC
Connection Setup
Duration on an
ERACH for Cell
BSC6900
V900R013
73441170
VS.CRNCIubBytes
ERACH.Rx
Number of Bytes
over Iub ERACH for
Cell
BSC6900
V900R013
73426161
VS.ERACH.E2F.S
ucc
Number of
Successful State
Transitions from
CELL_DCH (EDCH) to Enhanced
CELL_FACH (EDCH) for Cell
BSC6900
V900R015C00

1499
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426162
VS.ERACH.F2E.S
ucc
Number of
Successful State
Transitions from
Enhanced
CELL_FACH (EDCH) to
CELL_DCH (EDCH) for Cell
BSC6900
V900R015C00
73426163
VS.ERACH.E2F.A
tt
Number of Attempts
from CELL_DCH
(E-DCH) to
Enhanced
CELL_FACH (EDCH) for Cell
BSC6900
V900R015C00
73426164
VS.ERACH.F2E.A
tt
Number of Attempts
at State Transition
from Enhanced
CELL_FACH (EDCH) to
CELL_DCH (EDCH) for Cell
BSC6900
V900R015C00
73426172
VS.ERACHUEs.M
ax
Maximum Number
of UEs on E_RACH
for Cell
BSC6900
V900R015C00
None
Number of UEs Carried on ERACH for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441118
VS.ERACHUEs
Number of UEs Carried on

ERACH for Cell
73426172
VS.ERACHUEs.Max

on E_RACH for Cell

1500
BSC6900 UMTS
Description
These counters provide the average and maximum numbers of UEs that are carried on the
ERACH in a cell.
Measurement point
The RNC takes a sample from the number of UEs carried on the ERACH in a cell every 5s. At
the end of the measurement period, the RNC obtains the value of VS.ERACHUEs in the
measurement period by dividing the accumulated number of the UEs by the number of samples
and the RNC takes the maximum sampling number as the value of VS.ERACHUEs.Max.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ERACHUEs
WRFD-010701
Uplink Enhanced
CELL_FACH
VS.ERACHUEs.Max
WRFD-010701
Uplink Enhanced
CELL_FACH
Number of Requests for Setting Up RRC Connections on an ERACH for Cell

Counters
Counter ID
Counter Name
Counter Description
73423340
VS.RRC.AttConnEstab.ER
ACH
Number of Requests for

Setting Up RRC Connections
on an ERACH for Cell
Description
This counter provides the number of requests for setting up an RRC connection on the
ERACH.This counter does not include the RRC connection setup requests in the Directed
Signalling Connection Re-establishment (DSCR) procedure triggered by the overlapping of the
RRC connection setup procedure and cell update procedure. This counter complies with section
"8.1.3 RRC connection establishment" in 3GPP TS 25.331 (v12.1.0).
Issue 03 (2015-06-30)

1501
BSC6900 UMTS
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 does not include the RRC
procedure.This counter is measured only once if the RNC receives multiple RRC
CONNECTION REQUEST messages repeatedly from a UE.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnEstab.ER
ACH
WRFD-010701
Uplink Enhanced
CELL_FACH

1502
BSC6900 UMTS
Number of Successful RRC Connection Setups on an ERACH for Cell

Counters
Counter ID
Counter Name
Counter Description
73423341
VS.RRC.SuccConnEstab.E
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. This counter complies with section "8.1.3 RRC connection
Measurement point
The measurement is triggered at point C shown in the following figure. After receiving an RRC
CONNECTION SETUP COMPLETE message from an UE, the RNC measures this counter if
the RRC connection is set up on an ERACH.
Formula
None
Issue 03 (2015-06-30)

1503
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RACH
WRFD-010701
Uplink Enhanced
CELL_FACH
Number of PS RAB Setup Requests on an ERACH for Cell

Counters
Counter ID
Counter Name
Counter Description
73423342
VS.RAB.AttEstabPS.ERAC
H
Number of PS RAB Setup

Requests on an ERACH for
Cell
Description
This counter provides the number of requests for setting up a PS RAB on the ERACH in a cell.
This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v12.1.0).
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.
Issue 03 (2015-06-30)

1504
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabPS.ERAC
H
WRFD-010701
Uplink Enhanced
CELL_FACH
Number of Successful PS RAB Setups on an ERACH for Cell

Counters
Counter ID
Counter Name
Counter Description
73423343
VS.RAB.SuccEstabPS.ERA
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. This counter
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.
Issue 03 (2015-06-30)

1505
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabPS.ERA
CH
WRFD-010701
Uplink Enhanced
CELL_FACH
Number of PS RABs Normally Released on an ERACH for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423344
VS.RAB.NormRel.PS.ERA
CH
Number of PS RABs
Normally Released on an
ERACH for Cell

1506
BSC6900 UMTS
Description
This counter provides the number of times that a PS RAB is normally released on the ERACH
in a cell.This counter complies with section "8.3.2 Successful Operation" and "8.4.2 Successful
Measurement point
The measurement is triggered at point A in the figure. After receiving from the CN an IU
RELEASE COMMAND message, the RNC releases the corresponding RAB, and then sends
the CN an IU RELEASE COMPLETE message. If the release cause in the IU RELEASE
COMMAND message is "User Inactivity", "Normal Release", "Successful Relocation", or
"Network Optimization", or if the RNC has sent a release request with the cause of "User
Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release" before
the RNC receives the IU RELEASE COMMAND message and the RAB to be released is a PS
RAB carried on an ERACH, then the counter is measured in the cell that the UE camps on.
The measurement is triggered at point B in the following figure. After receiving an RAB
ASSIGNMENT REQUEST message with an RAB release request from the CN, the RNC
releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE message
to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is "User
Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization", or if the
RNC has sent a release request with the cause of "User Inactivity", "Network Optimization", or
"UE Generated Signalling Connection Release" before the RNC receives the IU RELEASE
COMMAND message and the RAB to be released is a PS RAB carried on an ERACH, then the
counter is measured in the cell that the UE camps on.
Issue 03 (2015-06-30)

1507
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.PS.ERA
CH
WRFD-010701
Uplink Enhanced
CELL_FACH
Number of PS RABs Abnormally Released on an ERACH for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423345
VS.RAB.AbnormRel.PS.ER
ACH
Number of PS RABs
Abnormally Released on an
ERACH for Cell

1508
BSC6900 UMTS
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 .This counter complies with section "8.3.2 Successful
Operation" and "8.4.2 Successful Operation" in 3GPP TS 25.413 (v10.10.0).
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", "UE Generated Signalling Connection
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
the CN an RAB RELEASE REQUEST message. If the RNC receives from the CN an IU
RELEASE COMMAND message which contains a cause value of the abnormal release (causes
except "User Inactivity," "Normal Release", "UE Generated Signalling Connection 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
Issue 03 (2015-06-30)

1509
BSC6900 UMTS
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", "UE Generated Signalling Connection Release", "Successful
Relocation", or "Network Optimization", for details, see 3GPP TS 25.413) and the RAB to be
released is a PS RAB carried on an ERACH, then this counter is measured in the cell that the
UE camps on.
Issue 03 (2015-06-30)

1510
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.PS.ER
ACH
WRFD-010701
Uplink Enhanced
CELL_FACH
RRC Connection Setup Duration on an ERACH for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423346
ax.ERACH
Maximum RRC Connection

Setup Duration on an
ERACH for Cell

1511
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73441135
ean.ERACH
Average RRC Connection

ERACH for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73423347
CH.ERACH.Cum
Accumulative Duration of
RRC Establishment Process
on ERACH for Cell
73423348
CH.ERACH.Sample
ERACH for Cell
Description
These counters provide the maximum and average durations taken by an RRC connection setup
on the ERACH in a cell.The preceding counters comply with section "8.1.3 RRC connection
Measurement point
at point A, the time is recorded as T1. When the RNC receives an RRC CONNECTION SETUP
COMPLETE message at point C, the time is recorded as T2. The RNC uses delta T = T2-T1 as
the RRC connection setup duration on the ERACH if the RRC connection is set up on the
ERACH. The RNC takes a sample from durations taken by an RRC connection setup on the
ERACH every 5s. At the end of the measurement period, the RNC obtains the value of
VS.RRC.ConnEstabTimeMean.ERACH for Cell by dividing the accumulated numbers by the
number of samples. In addition, the RNC takes the maximum sampling number as the value of
VS.RRC.ConnEstabTimeMax.ERACH.
Issue 03 (2015-06-30)

1512
BSC6900 UMTS
Formula
VS.RRC.ConnEstabTimeMean.ERACH = [VS.RRC.ConnEstabTime.CCH.ERACH.Cum]/
[VS.RRC.ConnEstabTime.CCH.ERACH.Sample]
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
ax.ERACH
WRFD-010701
Uplink Enhanced
CELL_FACH
ean.ERACH
WRFD-010701
Uplink Enhanced
CELL_FACH
Counter ID
Counter Name
Counter Description
73441170
VS.CRNCIubBytesERACH.
Rx
Number of Bytes over Iub

ERACH for Cell
Traffic over ERACH on Iub Interface

Counters
Issue 03 (2015-06-30)

1513
BSC6900 UMTS
Description
This counter provides the bytes of UL MAC PDUs (including the signaling data and the service
data, MAC headers and retransmitted 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, MAC headers and retransmitted data,not including the FP header) received by the CRNC
over the ERACH FP on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.CRNCIubBytesERACH.
Rx
WRFD-010701
Uplink Enhanced
CELL_FACH
Number of Successful State Transitions from CELL_DCH (E-DCH) to Enhanced

CELL_FACH (E-DCH) for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426161
VS.ERACH.E2F.Succ

Transitions from
CELL_DCH (E-DCH) to
Enhanced CELL_FACH (EDCH) for Cell
73426162
VS.ERACH.F2E.Succ

CELL_FACH (E-DCH) to
CELL_DCH (E-DCH) for
Cell

1514
BSC6900 UMTS
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.The
(v10.13.0).
Measurement point
When the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message
from a UE during a state transition from CELL_DCH (E-DCH) to enhanced CELL_FACH (EDCH), VS.ERACH.E2F.Succ is increased by one in the serving cell where the UE camps before
the state transition. If the state transition is from enhanced CELL_FACH (E-DCH) to
CELL_DCH (E-DCH), VS.ERACH.F2E.Succ is increased by one in the cell where the UE now
camps. The measurement is triggered at point B, as shown in the following figure.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ERACH.E2F.Succ
WRFD-01061208
HSUPA DCCC
WRFD-010701
Uplink Enhanced
CELL_FACH

1515
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.ERACH.F2E.Succ
WRFD-01061208
HSUPA DCCC
WRFD-010701
Uplink Enhanced
CELL_FACH
Number of Attempts at State Transitions from CELL_DCH (E-DCH) to Enhanced

CELL_FACH (E-DCH) for Cell
Counters
Counter ID
Counter Name
Counter Description
73426163
VS.ERACH.E2F.Att

Transitions from
CELL_DCH (E-DCH) to
Enhanced CELL_FACH (EDCH) for Cell
73426164
VS.ERACH.F2E.Att

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.The
(v10.13.0).
Measurement point
When the RNC sends a UE a RADIO BEARER RECONFIGURATION message during a state
transition from CELL_DCH (E-DCH) to enhanced CELL_FACH (E-DCH),
VS.ERACH.E2F.Att is increased by one in the serving cell where the UE camps before the state
transition. If the state transition is from enhanced CELL_FACH (E-DCH) to CELL_DCH (EDCH), VS.ERACH.F2E.Att is increased by one in the cell where the UE now camps. The
measurement is triggered at point A, as shown in the following figure.
Issue 03 (2015-06-30)

1516
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ERACH.E2F.Att
WRFD-01061208
HSUPA DCCC
WRFD-010701
Uplink Enhanced
CELL_FACH
WRFD-01061208
HSUPA DCCC
WRFD-010701
Uplink Enhanced
CELL_FACH
VS.ERACH.F2E.Att
1.12.14 Voice Quality EVQI Measurement <per Cell>(EVQI.CELL)

Overview
The Voice Quality EVQI Measurement <Cell> (EVQI.CELL) function subset contains counters
used to evaluate the voice quality of AMR-WB and AMR-NB services. The enhanced VQI
(EVQI) optimizes the evaluation of the voice quality of AMR-WB services, improves the
evaluation standards, and redefines the mean opinion score (MOS) thresholds for AMR-WB and
AMR-NB services, as compared with VQI.
Issue 03 (2015-06-30)

1517
BSC6900 UMTS
Figure 1-670 Comparison between VQI and EVQI
Figure 1-671 VQI (BLER = 0%) vs EVQI (BLER = 0%)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427874
VS.EVQI.AMRWB
.UL.TotalValue
Total Uplink EVQI

of AMR-WB
Services
BSC6900
V900R016C00

1518
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427875
VS.EVQI.AMRWB
.UL.Excellent.Num
Number of Times the

Uplink EVQI of
AMR-WB Services
Is EXCELLENT
BSC6900
V900R016C00
73427876
VS.EVQI.AMRWB
.UL.Good.Num
Number of Times the

Uplink EVQI of
AMR-WB Services
Is GOOD
BSC6900
V900R016C00
73427877
VS.EVQI.AMRWB
.UL.Accept.Num
Number of Times the

Uplink EVQI of
AMR-WB Services
Is ACCEPT
BSC6900
V900R016C00
73427878
VS.EVQI.AMRWB
.UL.Poor.Num
Number of Times the

Uplink EVQI of
AMR-WB Services
Is POOR
BSC6900
V900R016C00
73427879
VS.EVQI.AMRWB
.UL.Bad.Num
Number of Times the

Uplink EVQI of
AMR-WB Services
Is BAD
BSC6900
V900R016C00
73427880
VS.EVQI.AMRWB
.DL.TotalValue
Total Downlink
EVQI of AMR-WB
Services
BSC6900
V900R016C00
73427881
VS.EVQI.AMRWB
.DL.Excellent.Num
Number of Times the

Downlink EVQI of
AMR-WB Services
Is EXCELLENT
BSC6900
V900R016C00
73427882
VS.EVQI.AMRWB
.DL.Good.Num
Number of Times the

Downlink EVQI of
AMR-WB Services
Is GOOD
BSC6900
V900R016C00
73427883
VS.EVQI.AMRWB
.DL.Accept.Num
Number of Times the

Downlink EVQI of
AMR-WB Services
Is ACCEPT
BSC6900
V900R016C00
73427884
VS.EVQI.AMRWB
.DL.Poor.Num
Number of Times the

Downlink EVQI of
AMR-WB Services
Is POOR
BSC6900
V900R016C00

1519
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427885
VS.EVQI.AMRWB
.DL.Bad.Num
Number of Times the

Downlink EVQI of
AMR-WB Services
Is BAD
BSC6900
V900R016C00
73427886
VS.EVQI.AMRNB.
UL.TotalValue
Total Uplink EVQI

of AMR-NB
Services
BSC6900
V900R016C00
73427887
VS.EVQI.AMRNB.
UL.Excellent.Num
Number of Times the

Uplink EVQI of
AMR-NB Services Is
EXCELLENT
BSC6900
V900R016C00
73427888
VS.EVQI.AMRNB.
UL.Good.Num
Number of Times the

Uplink EVQI of
AMR-NB Services Is
GOOD
BSC6900
V900R016C00
73427889
VS.EVQI.AMRNB.
UL.Accept.Num
Number of Times the

Uplink EVQI of
AMR-NB Services Is
ACCEPT
BSC6900
V900R016C00
73427890
VS.EVQI.AMRNB.
UL.Poor.Num
Number of Times the

Uplink EVQI of
AMR-NB Services Is
POOR
BSC6900
V900R016C00
73427891
VS.EVQI.AMRNB.
UL.Bad.Num
Number of Times the

Uplink EVQI of
AMR-NB Services Is
BAD
BSC6900
V900R016C00
73427892
VS.EVQI.AMRNB.
DL.TotalValue
Total Downlink
EVQI of AMR-NB
Services
BSC6900
V900R016C00
73427893
VS.EVQI.AMRNB.
DL.Excellent.Num
Number of Times the

Downlink EVQI of
AMR-NB Services Is
EXCELLENT
BSC6900
V900R016C00
73427894
VS.EVQI.AMRNB.
DL.Good.Num
Number of Times the

Downlink EVQI of
AMR-NB Services Is
GOOD
BSC6900
V900R016C00

1520
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427895
VS.EVQI.AMRNB.
DL.Accept.Num
Number of Times the

Downlink EVQI of
AMR-NB Services Is
ACCEPT
BSC6900
V900R016C00
73427896
VS.EVQI.AMRNB.
DL.Poor.Num
Number of Times the

Downlink EVQI of
AMR-NB Services Is
POOR
BSC6900
V900R016C00
73427897
VS.EVQI.AMRNB.
DL.Bad.Num
Number of Times the

Downlink EVQI of
AMR-NB Services Is
BAD
BSC6900
V900R016C00
73429076
VS.SHO.EVQI.AM
RWB.UL.TotalValue
Total Uplink EVQI

of AMR-WB
Services During Soft
Handovers
BSC6900
V900R017C00
73429077
VS.SHO.EVQI.AM
RWB.UL.Excellent
.Num
Number of Times the

Uplink EVQI of
AMR-WB Services
During Soft
Handovers Is
EXCELLENT
BSC6900
V900R017C00
73429078
VS.SHO.EVQI.AM
RWB.UL.Good.Nu
m
Number of Times the

Uplink EVQI of
AMR-WB Services
During Soft
Handovers Is GOOD
BSC6900
V900R017C00
73429079
VS.SHO.EVQI.AM
RWB.UL.Accept.N
um
Number of Times the

Uplink EVQI of
AMR-WB Services
During Soft
Handovers Is
ACCEPT
BSC6900
V900R017C00
73429080
VS.SHO.EVQI.AM
RWB.UL.Poor.Nu
m
Number of Times the

Uplink EVQI of
AMR-WB Services
During Soft
Handovers Is POOR
BSC6900
V900R017C00

1521
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429081
VS.SHO.EVQI.AM
RWB.UL.Bad.Num
Number of Times the

Uplink EVQI of
AMR-WB Services
During Soft
Handovers Is BAD
BSC6900
V900R017C00
73429082
VS.SHO.EVQI.AM
RNB.UL.TotalValue
Total Uplink EVQI

of AMR-NB
Services During Soft
Handovers
BSC6900
V900R017C00
73429083
VS.SHO.EVQI.AM
RNB.UL.Excellent.
Num
Number of Times the

Uplink EVQI of
AMR-NB Services
During Soft
Handovers Is
EXCELLENT
BSC6900
V900R017C00
73429084
VS.SHO.EVQI.AM
RNB.UL.Good.Nu
m
Number of Times the

Uplink EVQI of
AMR-NB Services
During Soft
Handovers Is GOOD
BSC6900
V900R017C00
73429085
VS.SHO.EVQI.AM
RNB.UL.Accept.N
um
Number of Times the

Uplink EVQI of
AMR-NB Services
During Soft
Handovers Is
ACCEPT
BSC6900
V900R017C00
73429086
VS.SHO.EVQI.AM
RNB.UL.Poor.Num
Number of Times the

Uplink EVQI of
AMR-NB Services
During Soft
Handovers Is POOR
BSC6900
V900R017C00
73429087
VS.SHO.EVQI.AM
RNB.UL.Bad.Num
Number of Times the

Uplink EVQI of
AMR-NB Services
During Soft
Handovers Is BAD
BSC6900
V900R017C00
73429472
VS.EVQI.AMR.DL
.TotalValue.Platinum
Total Downlink
EVQI of AMR
Services for
Platinum Users
BSC6900
V900R017C00

1522
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429473
VS.EVQI.AMR.UL
.TotalValue.Platinum
Total Uplink EVQI

of AMR Services for
Platinum Users
BSC6900
V900R017C00
73429474
VS.EVQI.AMR.DL
.TotalNum.Platinum
Number of Times
Downlink EVQI of
AMR Services Is
Measured for
Platinum Users
BSC6900
V900R017C00
73429475
VS.EVQI.AMR.UL
.TotalNum.Platinum
Number of Times
Uplink EVQI of
AMR Services Is
Measured for
Platinum Users
BSC6900
V900R017C00
73446307
VS.EVQI.AMRNB.
UL.BLERRank0.A
verage
Average UL EVQI
Value of AMR-NB
Services That
Correspond to BLER
Level 0
BSC6900
V900R017C10
73446308
VS.EVQI.AMRNB.
UL.BLERRank1.A
verage
Average UL EVQI
Value of AMR-NB
Services That
Correspond to BLER
Level 1
BSC6900
V900R017C10
73446309
VS.EVQI.AMRNB.
UL.BLERRank2.A
verage
Average UL EVQI
Value of AMR-NB
Services That
Correspond to BLER
Level 2
BSC6900
V900R017C10
73446310
VS.EVQI.AMRNB.
UL.BLERRank3.A
verage
Average UL EVQI
Value of AMR-NB
Services That
Correspond to BLER
Level 3
BSC6900
V900R017C10
73446311
VS.EVQI.AMRNB.
UL.BLERRank4.A
verage
Average UL EVQI
Value of AMR-NB
Services That
Correspond to BLER
Level 4
BSC6900
V900R017C10

1523
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73446312
VS.EVQI.AMRWB
.UL.BLERRank0.A
verage
Average UL EVQI
Value of AMR-WB
Services That
Correspond to BLER
Level 0
BSC6900
V900R017C10
73446313
VS.EVQI.AMRWB
.UL.BLERRank1.A
verage
Average UL EVQI
Value of AMR-WB
Services That
Correspond to BLER
Level 1
BSC6900
V900R017C10
73446314
VS.EVQI.AMRWB
.UL.BLERRank2.A
verage
Average UL EVQI
Value of AMR-WB
Services That
Correspond to BLER
Level 2
BSC6900
V900R017C10
73446315
VS.EVQI.AMRWB
.UL.BLERRank3.A
verage
Average UL EVQI
Value of AMR-WB
Services That
Correspond to BLER
Level 3
BSC6900
V900R017C10
73446316
VS.EVQI.AMRWB
.UL.BLERRank4.A
verage
Average UL EVQI
Value of AMR-WB
Services That
Correspond to BLER
Level 4
BSC6900
V900R017C10
None
Total Uplink EVQI of AMR-WB Services

Counters
Counter ID
Counter Name
Counter Description
73427874
VS.EVQI.AMRWB.UL.TotalValue
Total Uplink EVQI of AMRWB Services
Description
This counter measures the total uplink EVQI of the AMR-WB services when the EVQI is used
to measure the voice quality. The measured EVQI ranges from 0 to 500. The actual EVQI equals
Issue 03 (2015-06-30)

1524
BSC6900 UMTS
the measured EVQI divided by 100 and ranges from 0 to 5. The EVQI indicates the voice quality
of AMR-WB services. The greater the value, the better the voice quality is.
The average uplink EVQI of the AMR-WB services of a cell can be calculated by using the
following formula:
EVQI(AVERAGE) = VS.EVQI.AMRWB.UL.TotalValue/
[(VS.EVQI.AMRWB.UL.Excellent.Num + VS.EVQI.AMRWB.UL.Good.Num +
VS.EVQI.AMRWB.UL.Accept.Num + VS.EVQI.AMRWB.UL.Poor.Num +
VS.EVQI.AMRWB.UL.Bad.Num) x 100]
Measurement point
After a UE initiates an AMR-WB service in a cell, the system measures the uplink EVQI of the
AMR-WB service every x seconds (x is set in the SET UEVQIPARA command) and reports
the measured value in the best cell. At the end of a measurement period, the system accumulates
the EVQI of all AMR-WB services.
Formula
None
Unit
None
Related Features
None
Number of Times the Uplink EVQI of AMR-WB Services Fall into A Level
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73427875
VS.EVQI.AMRWB.UL.Exc
ellent.Num

EVQI of AMR-WB Services
Is EXCELLENT
73427876
VS.EVQI.AMRWB.UL.Go
od.Num

Is GOOD
73427877
VS.EVQI.AMRWB.UL.Acc
ept.Num

Is ACCEPT
73427878
VS.EVQI.AMRWB.UL.Poo
r.Num

Is POOR

1525
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73427879
VS.EVQI.AMRWB.UL.Bad
.Num

Is BAD
Description
These counters measure the number of times the uplink EVQI of AMR-WB services is
considered to be EXCELLENT, GOOD, ACCEPT, POOR, or BAD when the EVQI is used to
measure the voice quality. The default mapping between the measured EVQI, actual EVQI, and
QoS quality levels is as follows:
[500, 400) = [5, 4) = Excellent
[400, 300) = [4, 3) = Good
[300, 200) = [3, 2) = Accept
[200, 100) = [2, 1) = Poor
[100, 0) = [1, 0) = Bad
The thresholds can be set by running the SET UEVQIPARA command.
Measurement point
After a UE initiates an AMR-WB service in a cell, the system measures the uplink EVQI of the
AMR-WB service every x seconds (x is set in the SET UEVQIPARA command) and reports
the measured value in the best cell. At the end of a measurement period, the system calculates
the number of times the EVQIs fall in the EXCELLENT, GOOD, ACCEPT, POOR, and BAD
levels, respectively.
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

1526
BSC6900 UMTS
Total Downlink EVQI of AMR-WB Services

Counters
Counter ID
Counter Name
Counter Description
73427880
VS.EVQI.AMRWB.DL.TotalValue
Total Downlink EVQI of

AMR-WB Services
Description
This counter measures the total downlink EVQI of the AMR-WB services when the EVQI is
used to measure the voice quality. The measured EVQI ranges from 0 to 500. The actual EVQI
equals the measured EVQI divided by 100 and ranges from 0 to 5. The EVQI indicates the voice
quality of AMR-WB services. The greater the value, the better the voice quality is.
The average downlink EVQI of the AMR-WB services of a cell can be calculated by using the
following formula:
EVQI(AVERAGE) = VS.EVQI.AMRWB.DL.TotalValue/
[(VS.EVQI.AMRWB.DL.Excellent.Num + VS.EVQI.AMRWB.DL.Good.Num +
VS.EVQI.AMRWB.DL.Accept.Num + VS.EVQI.AMRWB.DL.Poor.Num +
VS.EVQI.AMRWB.DL.Bad.Num) x 100]
Measurement point
After a UE initiates an AMR-WB service in a cell, the system measures the downlink EVQI of
the AMR-WB service every x seconds (x equals reporting period of the UE's measurement
reports) and reports the measured value in the best cell. At the end of a measurement period, the
system accumulates the EVQI of all AMR-WB services.
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

1527
BSC6900 UMTS
Number of Times the Downlink EVQI of AMR-WB Services Fall into A Level
Counters
Counter ID
Counter Name
Counter Description
73427881
VS.EVQI.AMRWB.DL.Exc
ellent.Num
Number of Times the

Downlink EVQI of AMRWB Services Is
EXCELLENT
73427882
VS.EVQI.AMRWB.DL.Go
od.Num
Number of Times the

Downlink EVQI of AMRWB Services Is GOOD
73427883
VS.EVQI.AMRWB.DL.Acc
ept.Num
Number of Times the

Downlink EVQI of AMRWB Services Is ACCEPT
73427884
VS.EVQI.AMRWB.DL.Poo
r.Num
Number of Times the

Downlink EVQI of AMRWB Services Is POOR
73427885
VS.EVQI.AMRWB.DL.Bad
.Num
Number of Times the

Downlink EVQI of AMRWB Services Is BAD
Description
These counters measure the number of times the downlink EVQI of AMR-WB services is
[500, 400) = [5, 4) = Excellent
[400, 300) = [4, 3) = Good
[300, 200) = [3, 2) = Accept
[200, 100) = [2, 1) = Poor
[100, 0) = [1, 0) = Bad
Measurement point
After a UE initiates an AMR-WB service in a cell, the system measures the downlink EVQI of
the AMR-WB service every x seconds (x equals reporting period of the UE's measurement
system calculates the number of times the EVQIs fall in the EXCELLENT, GOOD, ACCEPT,
POOR, and BAD levels, respectively.
Issue 03 (2015-06-30)

1528
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
Total Uplink EVQI of AMR-NB Services

Counters
Counter ID
Counter Name
Counter Description
73427886
VS.EVQI.AMRNB.UL.TotalValue
Total Uplink EVQI of AMRNB Services
Description
This counter measures the total uplink EVQI of the AMR-NB services when the EVQI is used
to measure the voice quality. The measured EVQI ranges from 0 to 500. The actual EVQI equals
the measured EVQI divided by 100 and ranges from 0 to 5. The EVQI indicates the voice quality
of AMR-NB services. The greater the value, the better the voice quality is.
The average uplink EVQI of the AMR-NB services of a cell can be calculated by using the
following formula:
EVQI(AVERAGE) = VS.EVQI.AMRNB.UL.TotalValue/
[(VS.EVQI.AMRNB.UL.Excellent.Num + VS.EVQI.AMRNB.UL.Good.Num +
VS.EVQI.AMRNB.UL.Accept.Num + VS.EVQI.AMRNB.UL.Poor.Num +
VS.EVQI.AMRNB.UL.Bad.Num) x 100]
Measurement point
After a UE initiates an AMR-NB service in a cell, the system measures the uplink EVQI of the
AMR-NB service every x seconds (x is set in the SET UEVQIPARA command) and reports the
measured value in the best cell. At the end of a measurement period, the system accumulates
the EVQI of all AMR-NB services.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1529
BSC6900 UMTS
Related Features
None
Number of Times the Uplink EVQI of AMR-NB Services Fall into A Level
Counters
Counter ID
Counter Name
Counter Description
73427887
VS.EVQI.AMRNB.UL.Exc
ellent.Num

EVQI of AMR-NB Services
Is EXCELLENT
73427888
VS.EVQI.AMRNB.UL.Goo
d.Num

Is GOOD
73427889
VS.EVQI.AMRNB.UL.Acc
ept.Num

Is ACCEPT
73427890
VS.EVQI.AMRNB.UL.Poor
.Num

Is POOR
73427891
VS.EVQI.AMRNB.UL.Bad.
Num

Is BAD
Description
These counters measure the number of times the uplink EVQI of AMR-NB services is considered
to be EXCELLENT, GOOD, ACCEPT, POOR, or BAD when the EVQI is used to measure the
voice quality. The default mapping between the measured EVQI, actual EVQI, and QoS quality
levels is as follows:
[500, 400) = [5, 4) = Excellent
[400, 300) = [4, 3) = Good
[300, 200) = [3, 2) = Accept
[200, 100) = [2, 1) = Poor
[100, 0) = [1, 0) = Bad
Measurement point
After a UE initiates an AMR-NB service in a cell, the system measures the uplink EVQI of the
AMR-NB service every x seconds (x is set in the SET UEVQIPARA command) and reports the
Issue 03 (2015-06-30)

1530
BSC6900 UMTS
measured value in the best cell. At the end of a measurement period, the system calculates the
number of times the EVQIs fall in the EXCELLENT, GOOD, ACCEPT, POOR, and BAD levels,
respectively.
Formula
None
Unit
None
Related Features
None
Total Downlink EVQI of AMR-NB Services

Counters
Counter ID
Counter Name
Counter Description
73427892
VS.EVQI.AMRNB.DL.TotalValue

AMR-NB Services
Description
This counter measures the total downlink EVQI of the AMR-NB services when the EVQI is
used to measure the voice quality. The measured EVQI ranges from 0 to 500. The actual EVQI
equals the measured EVQI divided by 100 and ranges from 0 to 5. The EVQI indicates the voice
quality of AMR-NB services. The greater the value, the better the voice quality is.
The average downlink EVQI of the AMR-NB services of a cell can be calculated by using the
following formula:
EVQI(AVERAGE) = VS.EVQI.AMRNB.DL.TotalValue/
[(VS.EVQI.AMRNB.DL.Excellent.Num + VS.EVQI.AMRNB.DL.Good.Num +
VS.EVQI.AMRNB.DL.Accept.Num + VS.EVQI.AMRNB.DL.Poor.Num +
VS.EVQI.AMRNB.DL.Bad.Num) x 100]
Measurement point
After a UE initiates an AMR-NB service in a cell, the system measures the downlink EVQI of
the AMR-NB service every x seconds (x equals reporting period of the UE's measurement
system accumulates the EVQI of all AMR-NB services.
Formula
None
Issue 03 (2015-06-30)

1531
BSC6900 UMTS
Unit
None
Related Features
None
Number of Times the Downlink EVQI of AMR-NB Services Fall into A Level
Counters
Counter ID
Counter Name
Counter Description
73427893
VS.EVQI.AMRNB.DL.Exc
ellent.Num
Number of Times the

Downlink EVQI of AMRNB Services Is
EXCELLENT
73427894
VS.EVQI.AMRNB.DL.Goo
d.Num
Number of Times the

Downlink EVQI of AMRNB Services Is GOOD
73427895
VS.EVQI.AMRNB.DL.Acc
ept.Num
Number of Times the

Downlink EVQI of AMRNB Services Is ACCEPT
73427896
VS.EVQI.AMRNB.DL.Poor
.Num
Number of Times the

Downlink EVQI of AMRNB Services Is POOR
73427897
VS.EVQI.AMRNB.DL.Bad.
Num
Number of Times the

Downlink EVQI of AMRNB Services Is BAD
Description
These counters measure the number of times the downlink EVQI of AMR-NB services is
[500, 400) = [5, 4) = Excellent
[400, 300) = [4, 3) = Good
[300, 200) = [3, 2) = Accept
[200, 100) = [2, 1) = Poor
[100, 0) = [1, 0) = Bad
Issue 03 (2015-06-30)

1532
BSC6900 UMTS
Measurement point
After a UE initiates an AMR-NB service in a cell, the system measures the downlink EVQI of
the AMR-NB service every x seconds (x equals reporting period of the UE's measurement
system calculates the number of times the EVQIs fall in the EXCELLENT, GOOD, ACCEPT,
POOR, and BAD levels, respectively.
Formula
None
Unit
None
Related Features
None
Total Uplink EVQI of AMR-WB Services During Soft Handovers

Counters
Counter ID
Counter Name
Counter Description
73429076
VS.SHO.EVQI.AMRWB.U
L.TotalValue
Total Uplink EVQI of AMRWB Services During Soft

Handovers
Description
This counter provides the total uplink EVQI of AMR-WB services in soft handover scenarios
when the EVQI is used to measure the voice quality. It is measured in the best cell. The measured
EVQI ranges from 0 to 500. The actual EVQI equals the measured EVQI divided by 100 and
ranges from 0 to 5. The EVQI indicates the voice quality of AMR-WB services. The larger the
value, the better the voice quality is.
The average uplink EVQI of AMR-WB services during soft handovers in a cell can be calculated
by using the following formula:
SHO EVQI(AVERAGE) = VS.SHO.EVQI.AMRWB.UL.TotalValue/
[(VS.SHO.EVQI.AMRWB.UL.Excellent.Num + VS.SHO.EVQI.AMRWB.UL.Good.Num +
VS.SHO.EVQI.AMRWB.UL.Accept.Num + VS.SHO.EVQI.AMRWB.UL.Poor.Num +
VS.SHO.EVQI.AMRWB.UL.Bad.Num) x 100]
Measurement point
When a UE initiates the AMR-WB service after being admitted to a cell, the system calculates
the uplink EVQI of this service every X seconds. X is specified by the EVQIUplinkPeriod
Issue 03 (2015-06-30)

1533
BSC6900 UMTS
parameter in the SET UEVQIPARA command. This counter measures the total uplink EVQI of
AMR-WB services during soft handovers. It is measured in the best cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.EVQI.AMRWB.U
L.TotalValue
WRFD-170201
Number of Times the Uplink EVQI of AMR-WB Services During Soft Handovers
Fall into A Level
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73429077
VS.SHO.EVQI.AMRWB.U
L.Excellent.Num

During Soft Handovers Is
EXCELLENT
73429078
VS.SHO.EVQI.AMRWB.U
L.Good.Num

GOOD
73429079
VS.SHO.EVQI.AMRWB.U
L.Accept.Num

ACCEPT
73429080
VS.SHO.EVQI.AMRWB.U
L.Poor.Num

POOR
73429081
VS.SHO.EVQI.AMRWB.U
L.Bad.Num

BAD

1534
BSC6900 UMTS
Description
These counters provide the number of times the uplink EVQI of AMR-WB services during soft
handovers is considered as EXCELLENT, GOOD, ACCEPT, POOR, and BAD in the best cell
when the EVQI is used to measure the voice quality. The default mapping between the measured
EVQI, actual EVQI, and QoS quality levels is as follows:
[500, 400) = [5, 4) = Excellent
[400, 300) = [4, 3) = Good
[300, 200) = [3, 2) = Accept
[200, 100) = [2, 1) = Poor
[100, 0) = [1, 0) = Bad
Measurement point
When a UE initiates the AMR-WB service after being admitted to a cell, the system calculates
parameter in the SET UEVQIPARA command. These counters measure the number of times
the uplink EVQI of AMR-WB services during soft handovers is considered as EXCELLENT,
GOOD, ACCEPT, POOR, and BAD. They are measured in the best cell.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.EVQI.AMRWB.U
L.Excellent.Num
WRFD-170201
VS.SHO.EVQI.AMRWB.U
L.Good.Num
WRFD-170201
VS.SHO.EVQI.AMRWB.U
L.Accept.Num
WRFD-170201
VS.SHO.EVQI.AMRWB.U
L.Poor.Num
WRFD-170201
VS.SHO.EVQI.AMRWB.U
L.Bad.Num
WRFD-170201

1535
BSC6900 UMTS
Total Uplink EVQI of AMR-NB Services During Soft Handovers

Counters
Counter ID
Counter Name
Counter Description
73429082
VS.SHO.EVQI.AMRNB.U
L.TotalValue
Total Uplink EVQI of AMRNB Services During Soft

Handovers
Description
This counter provides the total uplink EVQI of AMR-NB services in soft handover scenarios
when the EVQI is used to measure the voice quality. It is measured in the best cell. The measured
EVQI ranges from 0 to 500. The actual EVQI equals the measured EVQI divided by 100 and
ranges from 0 to 5. The EVQI indicates the voice quality of AMR-NB services. The larger the
value, the better the voice quality is.
The average uplink EVQI of AMR-NB services during soft handovers in a cell can be calculated
SHO EVQI(AVERAGE) = VS.SHO.EVQI.AMRNB.UL.TotalValue/
[(VS.SHO.EVQI.AMRNB.UL.Excellent.Num + VS.SHO.EVQI.AMRNB.UL.Good.Num +
VS.SHO.EVQI.AMRNB.UL.Accept.Num + VS.SHO.EVQI.AMRNB.UL.Poor.Num +
VS.SHO.EVQI.AMRNB.UL.Bad.Num) x 100]
Measurement point
When a UE initiates the AMR-NB service after being admitted to a cell, the system calculates
parameter in the SET UEVQIPARA command. This counter measures the total uplink EVQI of
AMR-NB services during soft handovers. It is measured in the best cell.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.EVQI.AMRNB.U
L.TotalValue
WRFD-170201

1536
BSC6900 UMTS
Number of Times the Uplink EVQI of AMR-NB Services During Soft Handovers
Fall into A Level
Counters
Counter ID
Counter Name
Counter Description
73429083
VS.SHO.EVQI.AMRNB.U
L.Excellent.Num

EXCELLENT
73429084
VS.SHO.EVQI.AMRNB.U
L.Good.Num

GOOD
73429085
VS.SHO.EVQI.AMRNB.U
L.Accept.Num

ACCEPT
73429086
VS.SHO.EVQI.AMRNB.U
L.Poor.Num

POOR
73429087
VS.SHO.EVQI.AMRNB.U
L.Bad.Num

BAD
Description
These counters provide the number of times the uplink EVQI of AMR-NB services during soft
handovers is considered as EXCELLENT, GOOD, ACCEPT, POOR, and BAD in the best cell
when the EVQI is used to measure the voice quality. The default mapping between the measured
EVQI, actual EVQI, and QoS quality levels is as follows:
[500, 400) = [5, 4) = Excellent
[400, 300) = [4, 3) = Good
[300, 200) = [3, 2) = Accept
[200, 100) = [2, 1) = Poor
[100, 0) = [1, 0) = Bad
Issue 03 (2015-06-30)

1537
BSC6900 UMTS
Measurement point
When a UE initiates the AMR-NB service after being admitted to a cell, the system calculates
parameter in the SET UEVQIPARA command. These counters measure the number of times
the uplink EVQI of AMR-NB services during soft handovers is considered as EXCELLENT,
GOOD, ACCEPT, POOR, and BAD. They are measured in the best cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.EVQI.AMRNB.U
L.Excellent.Num
WRFD-170201
VS.SHO.EVQI.AMRNB.U
L.Good.Num
WRFD-170201
VS.SHO.EVQI.AMRNB.U
L.Accept.Num
WRFD-170201
VS.SHO.EVQI.AMRNB.U
L.Poor.Num
WRFD-170201
VS.SHO.EVQI.AMRNB.U
L.Bad.Num
WRFD-170201
Total Downlink EVQI of AMR Services for Platinum Users

Counters
Counter ID
Counter Name
Counter Description
73429472
VS.EVQI.AMR.DL.TotalVa
lue.Platinum

AMR Services for Platinum
Users
Description
This counter measures the total downlink EVQI of the AMR services(including AMR-WB
services and AMR-NB services) for platinum users when the EVQI is used to measure the voice
Issue 03 (2015-06-30)

1538
BSC6900 UMTS
quality. The measured EVQI ranges from 0 to 500. The actual EVQI equals the measured EVQI
divided by 100 and ranges from 0 to 5. The EVQI indicates the voice quality of AMR-WB
services. The greater the value, the better the voice quality is.
The average downlink EVQI of the AMR services of a cell for platinum users can be calculated
Platinum EVQI(AVERAGE)=VS.EVQI.AMR.DL.TotalValue.Platinum/
(VS.EVQI.AMR.DL.TotalNum.Platinum*100)
Measurement point
After a platinum user initiates an AMR service (including AMR-WB service and AMR-NB
service) in a cell, the system measures the downlink EVQI of the AMR service every x seconds
(x equals reporting period of the UE's measurement reports) and reports the measured value in
the best cell. At the end of a measurement period, the system accumulates the EVQI of all AMR
services.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EVQI.AMR.DL.TotalVa
lue.Platinum
WRFD-150204
Total Uplink EVQI of AMR Services for Platinum Users

Counters
Counter ID
Counter Name
Counter Description
73429473
VS.EVQI.AMR.UL.TotalVa
lue.Platinum
Total Uplink EVQI of AMR

Services for Platinum Users
Description
This counter measures the total uplink EVQI of the AMR services(including AMR-WB services
and AMR-NB services) for platinum users when the EVQI is used to measure the voice quality.
The measured EVQI ranges from 0 to 500. The actual EVQI equals the measured EVQI divided
Issue 03 (2015-06-30)

1539
BSC6900 UMTS
by 100 and ranges from 0 to 5. The EVQI indicates the voice quality of AMR-WB services. The
greater the value, the better the voice quality is.
The average uplink EVQI of the AMR services of a cell for platinum users can be calculated by
using the following formula:
Platinum EVQI(AVERAGE)=VS.EVQI.AMR.UL.TotalValue.Platinum/
(VS.EVQI.AMR.UL.TotalNum.Platinum*100)
Measurement point
service) in a cell, the system measures the uplink EVQI of the AMR service every x seconds (x
is set in the SET UEVQIPARA command) and reports the measured value in the best cell. At
the end of a measurement period, the system accumulates the EVQI of all AMR services.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EVQI.AMR.UL.TotalVa
lue.Platinum
WRFD-150204
Number of Times Downlink EVQI of AMR Services Is Measured for Platinum

Users
Counters
Counter ID
Counter Name
Counter Description
73429474
VS.EVQI.AMR.DL.TotalN
um.Platinum
Number of Times Downlink

EVQI of AMR Services Is
Measured for Platinum Users
Description
These counters measure the number of times the downlink EVQI of AMR services (including
AMR-WB services and AMR-NB services)is measured for platinum users when the EVQI is
used to measure the voice quality.
Issue 03 (2015-06-30)

1540
BSC6900 UMTS
Measurement point
service) in a cell, the system measures the downlink EVQI of the AMR service every x seconds
(x equals reporting period of the UE's measurement reports) and reports the number of measured
times in the best cell. At the end of a measurement period, the system accumulates the number
of measured times of all AMR Services.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EVQI.AMR.DL.TotalN
um.Platinum
WRFD-150204
Number of Times Uplink EVQI of AMR Services Is Measured for Platinum Users
Counters
Counter ID
Counter Name
Counter Description
73429475
VS.EVQI.AMR.UL.TotalN
um.Platinum
Number of Times Uplink

EVQI of AMR Services Is
Measured for Platinum Users
Description
These counters measure the number of times the uplink EVQI of AMR services (including AMRWB services and AMR-NB services)is measured for platinum users when the EVQI is used to
measure the voice quality.
Measurement point
service) in a cell, the system measures the uplink EVQI of the AMR service every x seconds (x
is set in the SET UEVQIPARA command) and reports the number of measured times in the best
cell. At the end of a measurement period, the system accumulates the number of measured times
of all AMR Services.
Issue 03 (2015-06-30)

1541
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EVQI.AMR.UL.TotalN
um.Platinum
WRFD-150204
Average UL EVQI Values of AMR-NB Services That Correspond to Different BLER

Levels
Counters
Counter ID
Counter Name
Counter Description
73446307
VS.EVQI.AMRNB.UL.BLE
RRank0.Average
Average UL EVQI Value of

AMR-NB Services That
Correspond to BLER Level 0
73446308
RRank1.Average

73446309
RRank2.Average

73446310
RRank3.Average

73446311
RRank4.Average

Description
These counters provide the average EVQI values of uplink AMR-NB services that correspond
to BLER levels 0 to 4 in the best cell. The BLER level indicates the coverage performance of
AMR-NB services in the cell. The lower the BLER level, the lower the BLER is and the better
the coverage performance is. BLER levels are defined as follows:
BLER level 0 = [0%, 1%)
Issue 03 (2015-06-30)

1542
BSC6900 UMTS
BLER level 1 = [1%, 2%)

BLER level 2 = [2%, 5%)
BLER level 3 = [5%, 10%)
BLER level 4 = [10%, 100%]
Measurement point
When an AMR-NB service is initiated in a cell, the system calculates the ratio of speech frames
that fail the CRC to the total number of speech frames sent by the NodeB to the RNC in each
uplink EVQI evaluation period and determines the block error rate (BLER) level for this period.
The system then adds the EVQI value for this period to the total EVQI value for the
corresponding BLER level. If one-way audio or garbled voice is detected in an evaluation period,
the EVQI value for this EVQI evaluation period is not used in calculation. At the end of the
measurement period, the system calculates the average EVQI value of AMR-NB services that
correspond to each BLER level.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RRank0.Average
WRFD-171201

Coverage
WRFD-170201

RRank1.Average
WRFD-171201
WRFD-170201

Coverage
RRank2.Average
WRFD-171201
WRFD-170201

Coverage
RRank3.Average
WRFD-171201
WRFD-170201

Coverage
RRank4.Average
WRFD-171201
WRFD-170201

Coverage
Issue 03 (2015-06-30)

1543
BSC6900 UMTS
Average UL EVQI Values of AMR-WB Services That Correspond to Different

BLER Levels
Counters
Counter ID
Counter Name
Counter Description
73446312
VS.EVQI.AMRWB.UL.BL
ERRank0.Average

AMR-WB Services That
73446313
VS.EVQI.AMRWB.UL.BL
ERRank1.Average

73446314
VS.EVQI.AMRWB.UL.BL
ERRank2.Average

73446315
VS.EVQI.AMRWB.UL.BL
ERRank3.Average

73446316
VS.EVQI.AMRWB.UL.BL
ERRank4.Average

Description
These counters provide the average EVQI values of uplink AMR-WB services that correspond
to BLER levels 0 to 4 in the best cell. The BLER level indicates the coverage performance of
AMR-WB services in the cell. The lower the BLER level, the lower the BLER is and the better
the coverage performance is. BLER levels are defined as follows:
BLER level 0 = [0%, 1%)
BLER level 1 = [1%, 2%)
BLER level 2 = [2%, 5%)
BLER level 3 = [5%, 10%)
BLER level 4 = [10%, 100%]
Measurement point
When an AMR-WB service is initiated in a cell, the system calculates the ratio of speech frames
that fail the CRC to the total number of speech frames sent by the NodeB to the RNC in each
uplink EVQI evaluation period and determines the block error rate (BLER) level for this period.
The system then adds the EVQI value for this period to the total EVQI value for the
corresponding BLER level. If one-way audio or garbled voice is detected in an evaluation period,
the EVQI value for this EVQI evaluation period is not used in calculation. At the end of the
Issue 03 (2015-06-30)

1544
BSC6900 UMTS
measurement period, the system calculates the average EVQI value of AMR-WB services that
correspond to each BLER level.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.EVQI.AMRWB.UL.BL
ERRank0.Average
WRFD-171201

Coverage
WRFD-170201

VS.EVQI.AMRWB.UL.BL
ERRank1.Average
WRFD-171201
WRFD-170201

Coverage
VS.EVQI.AMRWB.UL.BL
ERRank2.Average
WRFD-171201
WRFD-170201

Coverage
VS.EVQI.AMRWB.UL.BL
ERRank3.Average
WRFD-171201
WRFD-170201

Coverage
VS.EVQI.AMRWB.UL.BL
ERRank4.Average
WRFD-171201
WRFD-170201

Coverage
1.12.15 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.
Issue 03 (2015-06-30)

1545
BSC6900 UMTS
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, counters that do not
differentiate services and that differentiate services are both measured. For example, if the RNC
triggers inter-RNC inter-frequency hard handovers for UEs processing combined services,
VS.HHO.SuccInterFreqOut.InterRNC, VS.HHO.SuccInterFreqOut.CS, and
VS.HHO.SuccInterFreqOut.PS are measured, respectively.
Issue 03 (2015-06-30)

1546
BSC6900 UMTS
Figure 1-672 Flow chart of hard handover and hard handover with relocation
Issue 03 (2015-06-30)

1547
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.HHO.EvalOut, VS.HHO.EvalIn,
VS.HHO.InterFreqOut.Eval.CM,
VS.HHO.InterFreqIn.Eval.CM,
VS.HHO.AttInterCellLB.SingleRL,
VS.HHO.AttInterCellLB.MultiRL
VS.HHO.AttIn,
VS.HHO.AttMultiBandOut.CS,
VS.HHO.AttMultiBandOut.PS,
VS.HHO.AttInterFreqOut,
VS.HHO.AttInterFreqIn,
VS.HHO.AttBlindHO,
VS.HHO.AttInterFreqIn.CS,
VS.HHO.AttInterFreqIn.PS,
VS.HHO.AttInterFreqOut.PS.UlBler,
VS.HHO.AttInterFreqOut.CS.TrigRscp,
VS.HHO.AttInterFreqOut.CS.TrigEcNo,
VS.HHO.AttInterFreqOut.PS.TrigRscp,
VS.HHO.AttInterFreqOut.PS.TrigEcNo,
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.Sig,
VS.HHO.AttInterFreqOut.PS.CoMacroMicro, VS.HHO.AttInterFreqOut.CS,
VS.HHO.AttInterFreqOut.PS,
VS.HHO.AttInterFreqOut.CSPS,
VS.HHO.AttInterFreqOut.CS.CLB,
VS.HHO.AttInterFreqOut.PS.CLB
VS.HHO.AttIntraFreqOut.IntraNodeB,
VS.HHO.AttInterFreqOut.IntraNodeB
VS.HHO.SuccIntraFreqOut.IntraNodeB,
VS.HHO.SuccInterFreqOut.IntraNodeB
VS.HHO.AttIntraFreqOut.InterNodeBIntraRNC, VS.HHO.AttInterFreqOut.InterNodeBIntraRNC

1548
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.HHO.SuccIntraFreqOut.InterNodeBIntraRNC, VS.HHO.SuccInterFreqOut.InterNodeBIntraRNC
VS.HHO.AttIntraFreqOut.InterRNC,
VS.HHO.AttInterFreqOut.InterRNC
VS.HHO.SuccIntraFreqOut.InterRNC,
VS.HHO.SuccInterFreqOut.InterRNC

1549
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.HHO.SuccIn,
VS.HHO.SuccMultiBandOut.CS,
VS.HHO.SuccMultiBandOut.PS,
VS.HHO.SuccInterCellLB.SingleRL,
VS.HHO.SuccInterCellLB.MultiRL,
VS.HHO.SuccInterFreqOut,
VS.HHO.SuccInterFreqIn,
VS.HHO.IntraFreqOut.Drop,
VS.HHO.SuccBlindHO,
VS.HHO.SuccInterFreqIn.CS,
VS.HHO.SuccInterFreqIn.PS,
VS.HHO.SuccInterFreqOut.CS,
VS.HHO.SuccInterFreqOut.PS,
VS.HHO.InterFreqOut.CS.Drop,
VS.HHO.InterFreqOut.PS.Drop,
VS.HHO.SuccInterFreqOut.PS.UlBler,
VS.HHO.SuccInterFreqOut.CS.Rscp,
VS.HHO.SuccInterFreqOut.CS.EcNo,
VS.HHO.SuccInterFreqOut.PS.Rscp,
VS.HHO.SuccInterFreqOut.PS.EcNo,
VS.HHO.SuccInterFreqOut.CS.UeTxPwr,
VS.HHO.SuccInterFreqOut.PS.UeTxPwr,
VS.HHO.SuccInterFreqOut.CS.Tcp,
VS.HHO.SuccInterFreqOut.PS.Tcp,
VS.HHO.SuccInterFreqOut.CS.TotalTxPwr,
VS.HHO.SuccInterFreqOut.PS.TotalTxPwr,
VS.HHO.SuccInterFreqOut.CS.TotalRxPwr,
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.CoMacroMicro, VS.HHO.SuccInterFreqOut.Sig,
VS.HHO.SuccInterFreqOut.CSPS,
VS.HHO.SuccInterFreqOut.CS.CLB,
VS.HHO.SuccInterFreqOut.PS.CLB

1550
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.HHO.FailIntraFreqOut.InterRNC.CfgU
nsupp,
VS.HHO.FailIntraFreqOut.InterRNC.PhyC
hFail,
VS.HHO.FailIntraFreqOut.InterRNC.ISR,
VS.HHO.FailIntraFreqOut.InterRNC.InvCf
g, VS.HHO.FailIntraFreqOut.InterRNC.CellUpdt,
VS.HHO.FailInterFreqOut.InterRNC.CfgU
nsupp,
VS.HHO.FailInterFreqOut.InterRNC.PhyC
hFail,
VS.HHO.FailInterFreqOut.InterRNC.ISR,
VS.HHO.FailInterFreqOut.InterRNC.InvCf
g, VS.HHO.FailInterFreqOut.InterRNC.CellUpdt
VS.HHO.FailIntraFreqOut.CfgUnsupp,
VS.HHO.FailIntraFreqOut.InvCfg,
VS.HHO.FailIntraFreqOut.PyhChFail,
VS.HHO.FailIntraFreqOut.ISR,
VS.HHO.FailIntraFreqOut.CellUpdt,
VS.HHO.FailIntraFreqOut.NoReply,
VS.HHO.FailInterFreqOut.CfgUnsupp,
VS.HHO.FailInterFreqOut.PyhChFail,
VS.HHO.FailInterFreqOut.ISR,
VS.HHO.FailInterFreqOut.CellUpdt,
VS.HHO.FailInterFreqOut.InvCfg,
VS.HHO.FailInterFreqOut.NoReply,
VS.HHO.FailIntraFreqOut.InterRNC.NoReply,
VS.HHO.FailInterFreqOut.InterRNC.NoReply
VS.HHO.FailIntraFreqOut.PrepFail,
VS.HHO.FailInterFreqOut.PrepFail,
VS.HHO.FailIntraFreqOut.RLSetupFail,
VS.HHO.FailInterFreqOut.RLSetupFail
VS.HHO.FailInterFreqOut.PrepFail
VS.HHO.AttIntraFreqRelocPrep,
VS.HHO.AttInterFreqRelocPrep
VS.HHO.SuccIntraFreqRelocPrep,
VS.HHO.SuccInterFreqRelocPrep
VS.HHO.AttIntraFreqRelocExec,
VS.HHO.AttInterFreqRelocExec

1551
BSC6900 UMTS
Measurement points
Description
VS.HHO.SuccIntraFreqRelocExec,
VS.HHO.SuccInterFreqRelocExec
VS.HHO.FailInterFreqOut.PrepFail,
VS.HHO.FailIntraFreqOut.RLSetupFail,
VS.HHO.FailInterFreqOut.RLSetupFail,
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180565
VS.HHO.AttIn
Number of Incoming
Hard Handover
Attempts for Cell
Earlier than
BSC6900
V900R011
67180566
VS.HHO.SuccIn
Number of
Successful Incoming
Hard Handovers in
the RNC for Cell
Earlier than
BSC6900
V900R011

1552
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193708
VS.HHO.AttIntraFreqRelocPrep
Number of
Relocation
Preparation
Attempts with
Outgoing IntraFrequency Hard
Handovers for Cell
Earlier than
BSC6900
V900R011
67192770
VS.HHO.SuccIntraFreqRelocPrep
Number of
Successful
Relocation
Preparations with
Handovers for Cell
Earlier than
BSC6900
V900R011
67192551
Number of
Relocation
Preparation
Attempts with
Outgoing InterFrequency Hard
Handovers for Cell
Earlier than
BSC6900
V900R011
67192552
Number of
Successful
Relocation
Preparations with
Handovers for Cell
Earlier than
BSC6900
V900R011
67192553
VS.HHO.FailIntra
FreqOut.NoReply
Number of Failed
Handovers Due to
No Response from
the UE for Cell
Earlier than
BSC6900
V900R011
67192554
VS.HHO.FailIntra
FreqOut.PrepFail
Number of Failed
Preparations for
Handovers for Cell
Earlier than
BSC6900
V900R011
67192555
VS.HHO.FailInter
FreqOut.PrepFail
Number of Failed
Preparations for
Handovers for Cell
Earlier than
BSC6900
V900R011

1553
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192556
VS.HHO.FailIntra
FreqOut.RLSetupFail
Number of Failed
Preparations for
Handovers Due to
Radio Link
Establishment
Failure for Cell
Earlier than
BSC6900
V900R011
67192557
VS.HHO.FailInter
FreqOut.RLSetupFail
Number of Failed
Preparations for
Handovers Due to
Radio Link
Establishment
Failure for Cell
Earlier than
BSC6900
V900R011
67192614
VS.HHO.FailIntra
FreqOut.InvCfg
Number of Failed
Handovers for Cell
(Invalid
Configuration)
Earlier than
BSC6900
V900R011
67192558
VS.HHO.FailIntra
FreqOut.CfgUnsupp
Number of Failed
Handovers for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67192559
VS.HHO.FailIntra
FreqOut.PyhChFail
Number of Failed
Handovers for Cell
(Physical Channel
Failure)
Earlier than
BSC6900
V900R011
67192560
VS.HHO.FailIntra
FreqOut.ISR
Number of Failed
Handovers for Cell
(Incompatible
Simultaneous
Reconfiguration)
Earlier than
BSC6900
V900R011

1554
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192561
VS.HHO.FailIntra
FreqOut.CellUpdt
Number of Failed
Handovers for Cell
(Cell Update
Occurred)
Earlier than
BSC6900
V900R011
67193565
VS.HHO.AttMulti
BandOut.CS
Number of CS
Outgoing Inter-Band
Hard Handover
Attempts for Cell
Earlier than
BSC6900
V900R011
67193566
VS.HHO.SuccMult
iBandOut.CS
Number of
Successful CS
Outgoing Inter-Band
Hard Handovers for
Cell
Earlier than
BSC6900
V900R011
67192567
VS.HHO.AttMulti
BandOut.PS
Number of PS
Outgoing Inter-Band
Hard Handover
Attempts for Cell
Earlier than
BSC6900
V900R011
67192568
VS.HHO.SuccMult
iBandOut.PS
Number of
Successful PS
Outgoing Inter-Band
Hard Handovers for
Cell
Earlier than
BSC6900
V900R011
67180585
VS.HHO.AttIntraF
reqOut.IntraNodeB
Number of Outgoing
Intra-Frequency
Hard Handover
Attempts in NodeB
for Cell
Earlier than
BSC6900
V900R011
67180586
VS.HHO.SuccIntra
FreqOut.IntraNodeB
Number of
Successful Outgoing
Intra-Frequency
Hard Handovers in
NodeB for Cell
Earlier than
BSC6900
V900R011
67180587
VS.HHO.AttIntraF
reqOut.InterNodeBIntraRNC
Number of Outgoing
Intra-Frequency
Hard Handover
Attempts Between
Different NodeBs of
RNC for Cell
Earlier than
BSC6900
V900R011

1555
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180588
VS.HHO.SuccIntra
FreqOut.InterNodeBIntraRNC
Number of
Successful Outgoing
Intra-Frequency
Hard Handovers
Between Different
NodeBs of RNC for
Cell
Earlier than
BSC6900
V900R011
67180589
VS.HHO.AttIntraF
reqOut.InterRNC
Number of Outgoing
Intra-Frequency
Hard Handover
Attempts Between
RNCs for Cell
Earlier than
BSC6900
V900R011
67180590
VS.HHO.SuccIntra
FreqOut.InterRNC
Number of
Successful Outgoing
Intra-Frequency
Hard Handovers
Between RNCs for
Cell
Earlier than
BSC6900
V900R011
67189701
VS.HHO.FailIntra
FreqOut.InterRNC
.CfgUnsupp
Number of Failed
Handovers Between
RNCs for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67189702
VS.HHO.FailIntra
FreqOut.InterRNC
.PhyChFail
Number of Failed
Handovers Between
RNCs for Cell
(Physical Channel
Failure)
Earlier than
BSC6900
V900R011
67189703
VS.HHO.FailIntra
FreqOut.InterRNC
.ISR
Number of Failed
Handovers Between
RNCs for Cell
(Incompatible
Simultaneous
Reconfiguration)
Earlier than
BSC6900
V900R011

1556
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189704
VS.HHO.FailIntra
FreqOut.InterRNC
.InvCfg
Number of Failed
Handovers Between
RNCs for Cell
(Invalid
Configuration)
Earlier than
BSC6900
V900R011
67189708
HHO.FailRelocPre
pOut.NoResAvail
Number of Failed
Relocation
Preparations with
Outgoing Hard
Handovers for Cell
(No Radio Resources
Available in Target
Cell)
Earlier than
BSC6900
V900R011
67189709
HHO.FailRelocPre
pOut.Texp
Number of Failed
Relocation
Preparations with
Outgoing Hard
Handovers for Cell
(TRELOCalloc
Expiry)
Earlier than
BSC6900
V900R011
67189710
HHO.FailRelocPre
pOut.TgtFail
Number of Failed
Relocation
Preparations with
Outgoing Hard
Handovers for Cell
(Relocation Failure
in Target CN/RNC or
Target System)
Earlier than
BSC6900
V900R011
67189711
HHO.FailRelocPre
pOut.RelocUnsupp
Number of Failed
Relocation
Preparations with
Outgoing Hard
Handovers for Cell
(Relocation Not
Supported in Target
RNC or Target
System)
Earlier than
BSC6900
V900R011

1557
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189712
HHO.FailRelocPre
pOut.TgtNotAllow
Number of Failed
Relocation
Preparations with
Outgoing Hard
Handovers for Cell
(Relocation Target
Not Allowed)
Earlier than
BSC6900
V900R011
67189713
HHO.FailRelocPre
pOut.OM
Number of Failed
Relocation
Preparations with
Outgoing Hard
Handovers for Cell
(O&M Intervention)
Earlier than
BSC6900
V900R011
67189714
HHO.FailRelocPre
pOut.ResUnavail
Number of Failed
Relocation
Preparations with
Outgoing Hard
Handovers for Cell
(No Resource
Available)
Earlier than
BSC6900
V900R011
67189715
HHO.FailRelocPre
pOut.Unspec
Number of Failed
Relocation
Preparations with
Outgoing Hard
Handovers for Cell
(Unspecified
Failure)
Earlier than
BSC6900
V900R011
67189716
VS.HHO.AttIntraFreqRelocExec
Number of
Relocation
Execution Attempts
with Outgoing IntraFrequency Hard
Handovers for Cell
Earlier than
BSC6900
V900R011
67189717
VS.HHO.SuccIntraFreqRelocExec
Number of
Successful
Relocation
Executions with
Handovers for Cell
Earlier than
BSC6900
V900R011
67189722
VS.HHO.EvalOut
Number of Decisions
for Outgoing Hard
Handovers for Cell
Earlier than
BSC6900
V900R011

1558
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189723
VS.HHO.EvalIn
Number of Decisions
for Incoming Hard
Handovers for Cell
Earlier than
BSC6900
V900R011
67180551
VS.HHO.InterFreq
Out.Eval.CM
Number of Decisions
for Outgoing InterFrequency Hard
Handovers in
Compressed Mode
for Cell
Earlier than
BSC6900
V900R011
67180570
VS.HHO.InterFreq
In.Eval.CM
Number of Decisions
for Incoming InterFrequency Hard
Handovers in
Compressed Mode
for Cell
Earlier than
BSC6900
V900R011
67180549
VS.HHO.AttInterC
ellLB.SingleRL
Number of Outgoing
Inter-Frequency
Hard Handover
Attempts Due to
Load Balancing for
Cell (Single RL)
Earlier than
BSC6900
V900R011
67180550
VS.HHO.SuccInter
CellLB.SingleRL
Number of
Successful Outgoing
Inter-Frequency
Hard Handovers Due
to Load Balancing
for Cell (Single RL)
Earlier than
BSC6900
V900R011
67193709
VS.HHO.AttInterC
ellLB.MultiRL
Number of Outgoing
Inter-Frequency
Hard Handover
Attempts Due to
Load Balancing for
Cell (Multiple RLs)
Earlier than
BSC6900
V900R011
67193710
VS.HHO.SuccInter
CellLB.MultiRL
Number of
Successful Outgoing
Inter-Frequency
Hard Handovers Due
to Load Balancing
for Cell (Multiple
RLs)
Earlier than
BSC6900
V900R011

1559
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67183900
VS.HHO.AttInterFreqOut
Number of Outgoing
Inter-Frequency
Hard Handover
Attempts for Cell
Earlier than
BSC6900
V900R011
67183901
VS.HHO.SuccInterFreqOut
Number of
Successful Outgoing
Inter-Frequency
Hard Handovers for
Cell
Earlier than
BSC6900
V900R011
67183902
VS.HHO.FailInter
FreqOut.CfgUnsupp
Number of Failed
Handovers for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67183903
VS.HHO.FailInter
FreqOut.PyhChFail
Number of Failed
Handovers for Cell
(Physical Channel
Failure)
Earlier than
BSC6900
V900R011
67183904
VS.HHO.FailInter
FreqOut.ISR
Number of Failed
Handovers for Cell
(Incompatible
Simultaneous
Reconfiguration)
Earlier than
BSC6900
V900R011
67183906
VS.HHO.FailInter
FreqOut.CellUpdt
Number of Failed
Handovers for Cell
(Cell Update
Occurred)
Earlier than
BSC6900
V900R011
67183907
VS.HHO.FailInter
FreqOut.InvCfg
Number of Failed
Handovers for Cell
(Invalid
Configuration)
Earlier than
BSC6900
V900R011

1560
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67183908
VS.HHO.FailInter
FreqOut.NoReply
Number of Failed
Handovers Due to
No Response from
the UE for Cell
Earlier than
BSC6900
V900R011
67183912
VS.HHO.AttInterFreqIn
Number of Incoming
Inter-Frequency
Hard Handover
Attempts for Cell
Earlier than
BSC6900
V900R011
67183913
VS.HHO.SuccInterFreqIn
Number of
Successful Incoming
Inter-Frequency
Hard Handovers for
Cell
Earlier than
BSC6900
V900R011
67183926
VS.HHO.IntraFreq
Out.Drop
Number of Call
Drops Due to Failed
Handovers for Cell
Earlier than
BSC6900
V900R011
67190877
VS.HHO.AttInterF
reqOut.IntraNodeB
Number of Outgoing
Inter-Frequency
Hard Handover
Attempts in NodeB
for Cell
Earlier than
BSC6900
V900R011
67190878
VS.HHO.SuccInter
FreqOut.IntraNodeB
Number of
Successful Outgoing
Inter-Frequency
Hard Handovers in
NodeB for Cell
Earlier than
BSC6900
V900R011
67190884
VS.HHO.AttInterF
reqOut.InterNodeBIntraRNC
Number of Outgoing
Inter-Frequency
Hard Handovers
Attempts Between
Different NodeBs of
RNC for Cell
Earlier than
BSC6900
V900R011
67190885
VS.HHO.SuccInter
FreqOut.InterNodeBIntraRNC
Number of
Successful Outgoing
Inter-Frequency
Hard Handovers
Between Different
NodeBs of RNC for
Cell
Earlier than
BSC6900
V900R011

1561
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190891
VS.HHO.AttInterF
reqOut.InterRNC
Number of Outgoing
Inter-Frequency
Hard Handovers
Attempts Between
RNCs for Cell
Earlier than
BSC6900
V900R011
67190892
VS.HHO.SuccInter
FreqOut.InterRNC
Number of
Successful Outgoing
Inter-Frequency
Hard Handovers
Between RNCs for
Cell
Earlier than
BSC6900
V900R011
67190898
Number of
Relocation
Execution Attempts
with Outgoing InterFrequency Hard
Handovers for Cell
Earlier than
BSC6900
V900R011
67190899
Number of
Successful
Relocation
Executions with
Handovers for Cell
Earlier than
BSC6900
V900R011
67191694
VS.HHO.AttBlindHO
Number of Outgoing
Emergency Blind
Handover Attempts
for Cell
Earlier than
BSC6900
V900R011
67191695
VS.HHO.SuccBlindHO
Number of
Successful Outgoing
Emergency Blind
Hard Handovers for
Cell
Earlier than
BSC6900
V900R011
67193397
VS.HHO.InterFreq
Out.CS.MeasTimeOut
Number of
Handovers Not
Performed Due to CS
Inter-Frequency
Measurement Expiry
for Cell
Earlier than
BSC6900
V900R011

1562
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193398
VS.HHO.InterFreq
Out.PS.MeasTimeOut
Number of
Handovers Not
Performed Due to PS
Inter-Frequency
Measurement Expiry
for Cell
Earlier than
BSC6900
V900R011
67193401
VS.HHO.AttInterF
reqOut.CS.TrigRsc
p
Number of CS InterFrequency Hard

Handover Attempts
Based on RSCP for
Cell
Earlier than
BSC6900
V900R011
67193402
VS.HHO.AttInterF
reqOut.CS.TrigEcNo

Handover Attempts
Based on EcNo for
Cell
Earlier than
BSC6900
V900R011
67193403
VS.HHO.AttInterF
reqOut.PS.TrigRsc
p
Number of PS InterFrequency Hard

Handover Attempts
Based on RSCP for
Cell
Earlier than
BSC6900
V900R011
67193404
VS.HHO.AttInterF
reqOut.PS.TrigEcNo

Handover Attempts
Based on EcNo for
Cell
Earlier than
BSC6900
V900R011
73403768
VS.HHO.AttInterF
reqIn.CS
Number of Requests
for CS Incoming
Inter-Frequency
Hard Handovers for
Cell
BSC6900
V900R012
73403769
VS.HHO.AttInterF
reqIn.PS
Number of Requests
for PS Incoming
Inter-Frequency
Hard Handovers for
Cell
BSC6900
V900R012
73403770
VS.HHO.AttInterF
reqOut.CS
Number of Requests
for CS Outgoing
Inter-Frequency
Hard Handovers for
Cell
BSC6900
V900R012

1563
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403771
VS.HHO.AttInterF
reqOut.PS
Number of Requests
for PS Outgoing
Inter-Frequency
Hard Handovers for
Cell
BSC6900
V900R012
73403772
VS.HHO.SuccInter
FreqIn.CS
Number of
Successful for CS
Incoming InterFrequency Hard
Handovers for Cell
BSC6900
V900R012
73403773
VS.HHO.SuccInter
FreqIn.PS
Number of
Successful for PS
Incoming InterFrequency Hard
Handovers for Cell
BSC6900
V900R012
73403774
VS.HHO.SuccInter
FreqOut.CS
Number of
Successful for CS
Handovers for Cell
BSC6900
V900R012
73403775
VS.HHO.SuccInter
FreqOut.PS
Number of
Successful for PS
Handovers for Cell
BSC6900
V900R012
73403776
VS.HHO.InterFreq
Out.CS.Drop
Number of CS Call
Drops due to
Unsuccessful
Handovers for cell
BSC6900
V900R012
73403777
VS.HHO.InterFreq
Out.PS.Drop
Number of PS Call
Drops due to
Unsuccessful
Handovers for cell
BSC6900
V900R012
73404081
VS.HHO.SuccInter
FreqOut.CS.Rscp
Number of
Successful CS InterFrequency Hard
Handovers Based on
RSCP for Cell
BSC6900
V900R012

1564
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73404082
VS.HHO.SuccInter
FreqOut.CS.EcNo
Number of
Handovers Based on
EcNo for Cell
BSC6900
V900R012
73404083
VS.HHO.SuccInter
FreqOut.PS.Rscp
Number of
Successful PS InterFrequency Hard
Handovers Based on
RSCP for Cell
BSC6900
V900R012
73404084
VS.HHO.SuccInter
FreqOut.PS.EcNo
Number of
Handovers Based on
EcNo for Cell
BSC6900
V900R012
73393851
VS.HHO.FailIntra
FreqOut.InterRNC
.CellUpdt
Number of Failed
Handovers Between
RNCs for Cell (Cell
update occurred)
BSC6900
V900R012
73393852
VS.HHO.FailIntra
FreqOut.InterRNC
.NoReply
Number of Failed
Handovers Between
the RNCs Due to No
Response from the
UE for Cell
BSC6900
V900R012
73393853
VS.HHO.FailInter
FreqOut.InterRNC
.CfgUnsupp
Number of Failed
Handovers Between
the RNCs for Cell
(Configuration
Unsupported)
BSC6900
V900R012
73393854
VS.HHO.FailInter
FreqOut.InterRNC
.PhyChFail
Number of Failed
Handovers Between
the RNCs for Cell
(Physical Channel
Failure)
BSC6900
V900R012

1565
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393855
VS.HHO.FailInter
FreqOut.InterRNC
.ISR
Number of Failed
Handovers Between
the RNCs for Cell
(Incompatible
Simultaneous
Reconfiguration)
BSC6900
V900R012
73393856
VS.HHO.FailInter
FreqOut.InterRNC
.InvCfg
Number of Failed
Handovers Between
the RNCs for Cell
(Invalid
Configuration)
BSC6900
V900R012
73393857
VS.HHO.FailInter
FreqOut.InterRNC
.CellUpdt
Number of Failed
Handovers Between
the RNCs for Cell
(Cell Update
Occurred)
BSC6900
V900R012
73393858
VS.HHO.FailInter
FreqOut.InterRNC
.NoReply
Number of Failed
Handovers Between
the RNCs Due to No
Response from the
UE for Cell
BSC6900
V900R012
73393934
VS.HHO.AttInterF
reqOut.PS.UlBler

Handover Attempts
Based on UL BLER
for Cell
BSC6900
V900R012
73393935
VS.HHO.AttInterF
reqOut.CS.UeTxP
wr

Handover Attempts
Based on UE
Transmit Power for
Cell
BSC6900
V900R012

1566
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393936
VS.HHO.AttInterF
reqOut.PS.UeTxP
wr

Handover Attempts
Based on UE
Transmit Power for
Cell
BSC6900
V900R012
73393937
VS.HHO.AttInterF
reqOut.CS.Tcp

Handover Attempts
Based on DL
Transmit Power for
Cell
BSC6900
V900R012
73393938
VS.HHO.AttInterF
reqOut.PS.Tcp

Handover Attempts
Based on DL
Transmit Power for
Cell
BSC6900
V900R012
73393939
VS.HHO.AttInterF
reqOut.CS.TotalTxPwr

Handover Attempts
Based on Cell Total
Transmit Power for
Cell
BSC6900
V900R012
73393940
VS.HHO.AttInterF
reqOut.PS.TotalTxPwr

Handover Attempts
Based on Cell Total
Transmit Power for
Cell
BSC6900
V900R012
73393941
VS.HHO.AttInterF
reqOut.CS.TotalRxPwr

Handover Attempts
Based on Cell Total
Receive Power for
Cell
BSC6900
V900R012
73393942
VS.HHO.AttInterF
reqOut.PS.TotalRxPwr

Handover Attempts
Based on Cell Total
Receive Power for
Cell
BSC6900
V900R012

1567
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393943
VS.HHO.AttInterF
reqOut.CS.Code

Handover Attempts
Based on Code
Resources for Cell
BSC6900
V900R012
73393944
VS.HHO.AttInterF
reqOut.PS.Code

Handover Attempts
Based on Code
Resources for Cell
BSC6900
V900R012
73393945
VS.HHO.SuccInter
FreqOut.PS.UlBler
Number of
Handovers Based on
UL BLER for Cell
BSC6900
V900R012
73393946
VS.HHO.SuccInter
FreqOut.CS.UeTx
Pwr
Number of
Handovers Based on
UE Transmit Power
for Cell
BSC6900
V900R012
73393947
VS.HHO.SuccInter
FreqOut.PS.UeTxP
wr
Number of
Handovers Based on
UE Transmit Power
for Cell
BSC6900
V900R012
73393948
VS.HHO.SuccInter
FreqOut.CS.Tcp
Number of
Handovers Based on
DL Transmit Power
for Cell
BSC6900
V900R012
73393949
VS.HHO.SuccInter
FreqOut.PS.Tcp
Number of
Handovers Based on
DL Transmit Power
for Cell
BSC6900
V900R012

1568
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393950
VS.HHO.SuccInter
FreqOut.CS.TotalTxPwr
Number of
Handovers Based on
Cell Total Transmit
Power for Cell
BSC6900
V900R012
73393951
VS.HHO.SuccInter
FreqOut.PS.TotalTxPwr
Number of
Handovers Based on
Cell Total Transmit
Power for Cell
BSC6900
V900R012
73393952
VS.HHO.SuccInter
FreqOut.CS.TotalRxPwr
Number of
Handovers Based on
Cell Total Receive
Power for Cell
BSC6900
V900R012
73393953
VS.HHO.SuccInter
FreqOut.PS.TotalRxPwr
Number of
Handovers Based on
Cell Total Receive
Power for Cell
BSC6900
V900R012
73393954
VS.HHO.SuccInter
FreqOut.CS.Code
Number of
Handovers Based on
Code Resources for
Cell
BSC6900
V900R012
73393955
VS.HHO.SuccInter
FreqOut.PS.Code
Number of
Handovers Based on
Code Resources for
Cell
BSC6900
V900R012
73424203
VS.HHO.AttInterF
reqOut.PS.UlCE

Handover Attempts
Based on UL CE for
Cell
BSC6900
V900R014

1569
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424204
VS.HHO.SuccInter
FreqOut.PS.UlCE
Number of
Handovers Based on
UL CE for Cell
BSC6900
V900R014
73424243
VS.HHO.AttInterF
reqOut.PS.DlCE

Handover Attempts
Based on DL CE for
Cell
BSC6900
V900R014
73424244
VS.HHO.SuccInter
FreqOut.PS.DlCE
Number of
Handovers Based on
DL CE for Cell
BSC6900
V900R014
73424245
VS.HHO.AttInterF
reqOut.CS.DlCE

Handover Attempts
Based on DL CE for
Cell
BSC6900
V900R014
73424246
VS.HHO.AttInterF
reqOut.CS.UlCE

Handover Attempts
Based on UL CE for
Cell
BSC6900
V900R014
73424247
VS.HHO.SuccInter
FreqOut.CS.UlCE
Number of
Handovers Based on
UL CE for Cell
BSC6900
V900R014
73424248
VS.HHO.SuccInter
FreqOut.CS.DlCE
Number of
Handovers Based on
DL CE for Cell
BSC6900
V900R014
73425014
VS.HHO.AttInterF
reqOut.Sig
Number of InterFrequency Hard

Handover Attempts
When only Signaling
Exists for Cell
BSC6900
V900R014

1570
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425015
VS.HHO.SuccInter
FreqOut.Sig
Number of
Successful InterFrequency Hard
Handover Attempts
When only Signaling
Exists for Cell
BSC6900
V900R014
73425831
VS.HHO.AttInterF
reqOut.PS.CoMacroMicro
Number of Outgoing
Macro & Micro Joint
Inter-frequency
Handover Attempts
in PS Domain for
Cell
BSC6900
V900R015C00
73425832
VS.HHO.SuccInter
FreqOut.PS.CoMacroMicro
Number of
Successful Outgoing
Macro & Micro Joint
Inter-frequency
Handovers in PS
Domain for Cell
BSC6900
V900R015C00
73428086
VS.HHO.AttInterF
reqOut.CSPS
Number of Outgoing
Inter-frequency Hard
Handover Attempts
for CS+PS
Combined Services
for Cell
BSC6900
V900R016C00
73428087
VS.HHO.SuccInter
FreqOut.CSPS
Number of
Successful Outgoing
Inter-frequency Hard
Handovers for CS
+PS Combined
Services for Cell
BSC6900
V900R016C00
73429116
VS.HHO.AttInterF
reqOut.FastMultR
LSetup.CS
Number of Fast
Multi-RL Setup
Attempts for
Outgoing Interfrequency CS HHOs
for Cell
BSC6900
V900R017C00
73429117
VS.HHO.AttInterF
reqOut.FastMultR
LSetup.PS
Number of Fast
Multi-RL Setup
Attempts for
Outgoing Interfrequency PS HHOs
for Cell
BSC6900
V900R017C00

1571
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429118
VS.HHO.SuccInter
FreqOut.FastMult
RLSetup.CS
Number of
Successful Fast
Multi-RL Setups for
for Cell
BSC6900
V900R017C00
73429119
VS.HHO.SuccInter
FreqOut.FastMult
RLSetup.PS
Number of
Successful Fast
Multi-RL Setups for
for Cell
BSC6900
V900R017C00
73429210
VS.HHO.InterFreq
Out.FastMultRLSe
tup.Prep.CS
Number of Times
that the RNC
Decides to Use Fast
Multi-RL Setup for
for Cell
BSC6900
V900R017C00
73429211
VS.HHO.InterFreq
Out.FastMultRLSe
tup.Prep.PS
Number of Times
that the RNC
Decides to Use Fast
Multi-RL Setup for
for Cell
BSC6900
V900R017C00
73430328
VS.HHO.AttInterF
reqOut.CS.CLB

Handover Attempts
Based on CLB for
Cell
BSC6900
V900R017C10
73430329
VS.HHO.AttInterF
reqOut.PS.CLB

Handover Attempts
Based on CLB for
Cell
BSC6900
V900R017C10
73430330
VS.HHO.SuccInter
FreqOut.CS.CLB
Number of
Handover Based on
CLB for Cell
BSC6900
V900R017C10

1572
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430331
VS.HHO.SuccInter
FreqOut.PS.CLB
Number of
Handover Based on
CLB for Cell
BSC6900
V900R017C10
Each Counter' s value equals to the sum of its subcounters' values
Counter
Sub Counter
VS.HHO.AttInterFreqOut.IntraNodeB
VS.HHO.AttInterFreqOut.InterNodeBIntraRNC
VS.HHO.AttInterFreqOut.InterRNC
VS.HHO.SuccInterFreqOut.IntraNodeB
VS.HHO.SuccInterFreqOut.InterNodeBIntraRNC
VS.HHO.SuccInterFreqOut.InterRNC
Number of Decisions for Outgoing Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67189722
VS.HHO.EvalOut
Number of Decisions for

Outgoing Hard Handovers
for Cell
67180551
VS.HHO.InterFreqOut.Eval.
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.The preceding counters comply with section "8.4.2
Measurement report" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

1573
BSC6900 UMTS

Counter Name
Description
VS.HHO.EvalOut
Number of decisions for outgoing intrafrequency and inter-frequency hard

handovers
VS.HHO.InterFreqOut.Eval.CM
Number of decisions for outgoing interfrequency 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.
Formula
None
Issue 03 (2015-06-30)

1574
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.EvalOut
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
VS.HHO.InterFreqOut.Eval.
CM
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Decisions for Incoming Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67189723
VS.HHO.EvalIn

Incoming Hard Handovers
for Cell
67180570
VS.HHO.InterFreqIn.Eval.C
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.The
preceding counters comply with section "8.4.2 Measurement report" in 3GPP TS 25.331
(v10.13.0).
Issue 03 (2015-06-30)

1575
BSC6900 UMTS
Counter Name
Description
VS.HHO.EvalIn
Number of decisions for incoming intrafrequency and inter-frequency hard

handovers
VS.HHO.InterFreqIn.Eval.CM
Number of decisions for incoming interfrequency 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.
Formula
None
Issue 03 (2015-06-30)

1576
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.EvalIn
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
VS.HHO.InterFreqIn.Eval.C
M
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Incoming Hard Handover Attempts

Counters
Counter ID
Counter Name
Counter Description
67180565
VS.HHO.AttIn
Number of Incoming Hard

Handover Attempts for Cell
67183912
Number of Incoming InterFrequency Hard Handover

Attempts for Cell
73403768
VS.HHO.AttInterFreqIn.CS
Number of Requests for CS

Hard Handovers for Cell
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.The preceding counters comply with section "8.3.5 Hard
handover" and "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

1577
BSC6900 UMTS

Counter Name
Description
VS.HHO.AttIn
Number of incoming intra-frequency and

inter-frequency hard handover attempts
(including CS and PS)
Number of incoming inter-frequency hard

handover attempts(including CS and PS)
Number of Requests for CS Incoming InterFrequency Hard Handovers
Number of Requests for PS Incoming InterFrequency Hard Handovers
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.
Issue 03 (2015-06-30)

1578
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.AttIn
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
WRFD-020302
WRFD-020304

Handover Based on
Coverage
WRFD-020302
WRFD-020304

Handover Based on
Coverage
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Outgoing Inter-Band Hard Handover Attempts for Different Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193565
VS.HHO.AttMultiBandOut.
CS
Inter-Band Hard Handover
Attempts for Cell

1579
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192567
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.The preceding counters comply with section "8.3.5 Hard handover" and "8.2.2
Measurement point
The measurement is triggered at point B as shown in the following figure, taking the PHYSICAL
CHANNEL RECONFIGURATION message as an example. The RNC performs hard handover
for 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
Issue 03 (2015-06-30)

1580
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CS
WRFD-020110
Multi Frequency Band

Networking Management
PS
WRFD-020110

Number of Outgoing Inter-Frequency Hard Handover Attempts

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67183900
Number of Outgoing InterFrequency Hard Handover

Attempts for Cell
67180549
VS.HHO.AttInterCellLB.Si
ngleRL

Attempts Due to Load
Balancing for Cell (Single
RL)
67193709
VS.HHO.AttInterCellLB.M
ultiRL

Attempts Due to Load
Balancing for Cell (Multiple
RLs)
73403770
VS.HHO.AttInterFreqOut.C
S
Number of Requests for CS

73403771
VS.HHO.AttInterFreqOut.P
S
Number of Requests for PS

73425014
VS.HHO.AttInterFreqOut.Si
g
Hard Handover Attempts
When only Signaling Exists
for Cell

1581
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428086
SPS
Number of Outgoing Interfrequency Hard Handover

Attempts for CS+PS
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.The
preceding counters comply with section "8.3.5 Hard handover" and "8.2.2 Reconfiguration
Counter Name
Description
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 interfrequency hard handovers
VS.HHO.AttInterFreqOut.PS
Number of requests for PS Outgoing interfrequency hard handovers
VS.HHO.AttInterFreqOut.Sig
Number of outgoing inter-frequency hard

handover attempts when the UE has only
signalling
Measurement point
CHANNEL RECONFIGURATION message as an example. After deciding to perform an
outgoing inter-frequency hard handover, the RNC sends a PHYSICAL CHANNEL
RECONFIGURATION message to the UE. In this case, the RNC measures the corresponding
counter according to service types and the number of RLs in the best cell where the UE camps
on before the inter-frequency hard handover.
Issue 03 (2015-06-30)

1582
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020302

Handover Based on
Coverage
WRFD-020304
WRFD-020106

Load Reshuffling
Issue 03 (2015-06-30)

1583
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HHO.AttInterCellLB.Si
ngleRL
WRFD-020103

Balance
VS.HHO.AttInterCellLB.M
ultiRL
WRFD-020103

Balance
S
WRFD-020302

Handover Based on
Coverage
WRFD-020304

S
WRFD-020302
WRFD-020304

Handover Based on
Coverage
VS.HHO.AttInterFreqOut.Si
g
WRFD-020302
WRFD-020304

Handover Based on
Coverage
SPS
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Outgoing Emergency Blind Handover Attempts

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.3.5 Hard handover" and "8.2.2 Reconfiguration
Issue 03 (2015-06-30)

1584
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HHO.AttBlindHO
WRFD-020302

Handover Based on
Coverage

1585
BSC6900 UMTS
Counters Related to the Number of Outgoing Inter-Frequency Hard Handover

Attempts
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393934
S.UlBler
Number of PS InterFrequency Hard Handover

Attempts Based on UL
BLER for Cell
67193401
S.TrigRscp
Number of CS InterFrequency Hard Handover

Attempts Based on RSCP for
Cell
67193402
S.TrigEcNo

Attempts Based on EcNo for
Cell
67193403
S.TrigRscp

Attempts Based on RSCP for
Cell
67193404
S.TrigEcNo

Attempts Based on EcNo for
Cell
73393935
S.UeTxPwr

Attempts Based on UE
Transmit Power for Cell
73393936
S.UeTxPwr

Attempts Based on UE
73393937
S.Tcp

Attempts Based on DL
73393938
S.Tcp

Attempts Based on DL

1586
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393939
S.TotalTxPwr

Attempts Based on Cell Total
73393940
S.TotalTxPwr

73393941
S.TotalRxPwr

Receive Power for Cell
73393942
S.TotalRxPwr

Receive Power for Cell
73393943
S.Code

Attempts Based on Code
Resources for Cell
73393944
S.Code

Attempts Based on Code
Resources for Cell
73424203
S.UlCE

Attempts Based on UL CE
for Cell
73424243
S.DlCE

Attempts Based on DL CE
for Cell
73424245
S.DlCE

Attempts Based on DL CE
for Cell
73424246
S.UlCE

Attempts Based on UL CE
for Cell

1587
BSC6900 UMTS
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.The preceding
counters comply with section "8.3.5 Hard handover" and "8.2.2 Reconfiguration procedures" in
3GPP TS 25.331 (v10.13.0).
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-679 Handover Indication
Formula
None
Unit
None
Issue 03 (2015-06-30)

1588
BSC6900 UMTS
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
S.TrigRscp
WRFD-020302

Handover Based on
Coverage
S.TrigEcNo
WRFD-020302

Handover Based on
Coverage
S.TrigRscp
WRFD-020302

Handover Based on
Coverage
S.TrigEcNo
WRFD-020302

Handover Based on
Coverage
S.Tcp
WRFD-020304

S.Tcp
WRFD-020304

S.TotalTxPwr
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.TotalTxPwr
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.TotalRxPwr
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.TotalRxPwr
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold

1589
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
S.Code
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.Code
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.UlCE
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.DlCE
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.DlCE
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.UlCE
WRFD-140217
Balancing Based on
Configurable Load
Threshold
Number of Outgoing Macro & Micro Joint Inter-frequency Handover Attempts in

PS Domain for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425831
S.CoMacroMicro
Number of Outgoing Macro

& Micro Joint Interfrequency Handover
Attempts in PS Domain for
Cell

1590
BSC6900 UMTS
Description
This counter measures the number of outgoing macro & micro joint inter-frequency handover
attempts in the PS domain in a cell.This counter complies with section "8.3.5 Hard handover"
and "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
Measurement point
In the figure 1, Both SHO and Non-SHO areas are macro & micro joint inter-frequency handover
area.
Figure 1-680 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-681 Successful physical channel reconfiguration procedure
Issue 03 (2015-06-30)

1591
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 interfrequency handover. This counter is increased by one in the serving cell where the UE camps
each time the RNC sends a TRANSPORT CHANNEL RECONFIGURATION message to the
UE.
Figure 1-682 Successful transport channel reconfiguration procedure
each time the RNC sends a RADIO BEARER RECONFIGURATION message to the UE.
Figure 1-683 Successful radio bearer reconfiguration procedure
Issue 03 (2015-06-30)

1592
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
S.CoMacroMicro
WRFD-150201

WRFD-15020102
Macro & Micro Joint Interfrequency Handover
Counters Related to the Number of Inter-Frequency Hard Handover Attempts

Based on CLB
Counters
Counter ID
Counter Name
Counter Description
73430328
S.CLB

Attempts Based on CLB for
Cell
73430329
S.CLB

Attempts Based on CLB for
Cell
Description
These counters provide the number of outgoing inter-frequency hard handover attempts for CS
services or PS services due to CLB causes in the best cell before the handover.
Measurement point
Taking the PHYSICAL CHANNEL RECONFIGURATION message as an example, the
measurement is triggered at point A as shown in figure 1. When the RNC sends the UE a
PHYSICAL CHANNEL RECONFIGURATION message, this counter is measured based on
the service type in the best cell that the UE camps on before the handover.
Issue 03 (2015-06-30)

1593
BSC6900 UMTS
Figure 1-684 Physical Channel Reconfiguration
Taking the TRANSPORT CHANNEL RECONFIGURATION message as an example, the

measurement is triggered at point A as shown in figure 2. When the RNC sends the UE a
TRANSPORT CHANNEL RECONFIGURATION message, this counter is measured based on
the service type in the best cell that the UE camps on before the handover.
Figure 1-685 Transmission Channel Reconfiguration
Issue 03 (2015-06-30)

1594
BSC6900 UMTS
Taking the RADIO BEARER RECONFIGURATION message as an example, the measurement

is triggered at point A as shown in figure 3. When the RNC sends the UE a RADIO BEARER
RECONFIGURATION message, this counter is measured based on the service type in the best
cell that the UE camps on before the handover.
Figure 1-686 RB Reconfiguration
Taking the RADIO BEARER SETUP message as an example, the measurement is triggered at
point A as shown in figure 4. When the RNC sends the UE a RADIO BEARER SETUP message,
this counter is measured based on the service type in the best cell that the UE camps on before
the handover.
Issue 03 (2015-06-30)

1595
BSC6900 UMTS
Figure 1-687 RB Setup
Taking the RADIO BEARER SETUP RELEASE message as an example, the measurement is
triggered at point A as shown in figure 5. When the RNC sends the UE a RADIO BEARER
SETUP RELEASE message, this counter is measured based on the service type in the best cell
that the UE camps on before the handover.
Figure 1-688 RB Release
Issue 03 (2015-06-30)

1596
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
S.CLB
WRFD-140217
Balancing Based on
Configurable Load
Threshold
S.CLB
WRFD-140217
Balancing Based on
Configurable Load
Threshold
Number of Outgoing Hard Handover Attempts in NodeB

Counters
Counter ID
Counter Name
Counter Description
67180585
VS.HHO.AttIntraFreqOut.In
traNodeB
Number of Outgoing IntraFrequency Hard Handover

Attempts in NodeB for Cell
67190877
VS.HHO.AttInterFreqOut.In
traNodeB

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.The preceding counters
Issue 03 (2015-06-30)

1597
BSC6900 UMTS
comply with section "8.3.5 Hard handover" and "8.2.2 Reconfiguration procedures" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency 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
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
Issue 03 (2015-06-30)

1598
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
traNodeB
WRFD-020301

Handover
traNodeB
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Successful Outgoing Hard Handovers in NodeB

Counters
Counter ID
Counter Name
Counter Description
67180586
VS.HHO.SuccIntraFreqOut.
IntraNodeB
Outgoing Intra-Frequency
Hard Handovers in NodeB
for Cell
67190878
VS.HHO.SuccInterFreqOut.
IntraNodeB
Hard Handovers in NodeB
for Cell
Description
These counters provide 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.The preceding counters
comply with section "8.3.5 Hard handover" and "8.2.2 Reconfiguration procedures" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency or inter-frequency hard handover if the criteria of the decision to perform hard
Issue 03 (2015-06-30)

1599
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
IntraNodeB
WRFD-020301

Handover

1600
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
IntraNodeB
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Outgoing Hard Handover Attempts Between Different NodeBs of RNC

Counters
Counter ID
Counter Name
Counter Description
67180587
terNodeBIntraRNC

Attempts Between Different
NodeBs of RNC for Cell
67190884
terNodeBIntraRNC
Number of Outgoing InterFrequency 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.The preceding counters comply with section "8.3.5 Hard handover"
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.
Issue 03 (2015-06-30)

1601
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
terNodeBIntraRNC
WRFD-020301

Handover
terNodeBIntraRNC
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1602
BSC6900 UMTS
Number of Successful Outgoing Hard Handovers Between Different NodeBs of

RNC
Counters
Counter ID
Counter Name
Counter Description
67180588
InterNodeBIntraRNC
Hard Handovers Between
Different NodeBs of RNC for
Cell
67190885
InterNodeBIntraRNC
Different NodeBs of RNC for
Cell
Description
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.The preceding counters comply with section "8.3.5 Hard handover"
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.
Issue 03 (2015-06-30)

1603
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
InterNodeBIntraRNC
WRFD-020301

Handover
InterNodeBIntraRNC
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1604
BSC6900 UMTS
Number of Outgoing Hard Handover Attempts Between RNCs

Counters
Counter ID
Counter Name
Counter Description
67180589
terRNC

Attempts Between RNCs for
Cell
67190891
terRNC
Number of Outgoing InterFrequency 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
through the Iur interface between the RNCs.The preceding counters comply with section "8.3.5
Hard handover" and "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

1605
BSC6900 UMTS
Figure 1-693 Hard handover procedure (between different RNCs)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
terRNC
WRFD-020301

Handover
terRNC
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1606
BSC6900 UMTS
Number of Successful Outgoing Hard Handovers Between RNCs

Counters
Counter ID
Counter Name
Counter Description
67180590
InterRNC
RNCs for Cell
67190892
InterRNC
RNCs for Cell
Description
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
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
through the Iur interface between the RNCs.The preceding counters comply with section "8.3.5
Measurement point
CHANNEL RECONFIGURATION message as an example. The RNC performs intrafrequency hard handover if the criteria of the decision to perform hard handover are fulfilled,
and then sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE. When
the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message
from the UE, the hard handover succeeds. If the best cell before the hard handover and the target
cell are controlled by the SRNC and the DRNC respectively, 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.
Issue 03 (2015-06-30)

1607
BSC6900 UMTS
Figure 1-694 Hard handover procedure (between different RNCs)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
InterRNC
WRFD-020301

Handover
InterRNC
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1608
BSC6900 UMTS
Number of Successful Incoming Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67180566
VS.HHO.SuccIn
Incoming Hard Handovers in
the RNC for Cell
67183913
73403772
VS.HHO.SuccInterFreqIn.C
S
Number of Successful for CS

73403773
VS.HHO.SuccInterFreqIn.P
S
Number of Successful for PS

Description
These counters provide the number of successful incoming hard handovers. The measurement
is performed in the target cell in the RNC.The preceding counters comply with section "8.3.5
Counter Name
Description
VS.HHO.SuccIn
Number of successful incoming intrafrequency and inter-frequency hard handover

(including CS and PS)
Number of successful incoming interfrequency hard handovers(including CS and

PS)
VS.HHO.SuccInterFreqIn.CS
Number of successful CS incoming interfrequency hard handovers
VS.HHO.SuccInterFreqIn.PS
Number of successful PS incoming interfrequency hard handovers
Measurement point
CHANNEL RECONFIGURATION message as an example. During the hard handover, if the
RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from
Issue 03 (2015-06-30)

1609
BSC6900 UMTS
the UE, the hard handover succeeds. In this case, the RNC measures the counter in the target
cell of incoming hard handover.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.SuccIn
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Issue 03 (2015-06-30)

1610
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-020302

Handover Based on
Coverage
WRFD-020304

VS.HHO.SuccInterFreqIn.C
S
WRFD-020302
WRFD-020304

Handover Based on
Coverage
VS.HHO.SuccInterFreqIn.P
S
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Successful Outgoing Inter-Band Hard Handovers for Different Services

Counters
Counter ID
Counter Name
Counter Description
67193566
VS.HHO.SuccMultiBandOu
t.CS
Outgoing Inter-Band Hard
Handovers for Cell
67192568
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.The preceding counters comply with section "8.3.5 Hard handover" and "8.2.2
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
Issue 03 (2015-06-30)

1611
BSC6900 UMTS
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
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
t.CS
WRFD-020110

t.PS
WRFD-020110


1612
BSC6900 UMTS
Number of Successful Outgoing Inter-Frequency Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67183901
67180550
VS.HHO.SuccInterCellLB.S
ingleRL
Hard Handovers Due to Load
Balancing for Cell (Single
RL)
67193710
VS.HHO.SuccInterCellLB.
MultiRL
Hard Handovers Due to Load
Balancing for Cell (Multiple
RLs)
73403774
CS
Number of Successful for CS

73403775
PS
Number of Successful for PS

73425015
Sig
Number of Successful InterFrequency Hard Handover

Attempts When only
Signaling Exists for Cell
73428087
CSPS
Outgoing Inter-frequency
Hard Handovers for CS+PS
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.The
Issue 03 (2015-06-30)

1613
BSC6900 UMTS
Counter Name
Description
Number of successful outgoing interfrequency hard handovers
VS.HHO.SuccInterCellLB.SingleRL
Number of successful outgoing interfrequency hard handovers due to the load

balancing in single RL
VS.HHO.SuccInterCellLB.MultiRL
Number of successful outgoing interfrequency hard handovers due to the load

balancing in Multiple RLs
VS.HHO.SuccInterFreqOut.CS
Number of successful for CS Outgoing interfrequency hard handovers
VS.HHO.SuccInterFreqOut.PS
Number of successful for PS Outgoing interfrequency hard handovers
VS.HHO.SuccInterFreqOut.Sig
Number of successful outgoing interfrequency hard handover when the UE has

only signalling
Measurement point
CHANNEL RECONFIGURATION message as an example. During the inter-frequency hard
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 RLs in the best cell where the UE
Issue 03 (2015-06-30)

1614
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020302

Handover Based on
Coverage
WRFD-020304
WRFD-020106

Load Reshuffling
Issue 03 (2015-06-30)

1615
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HHO.SuccInterCellLB.S
ingleRL
WRFD-020103

Balance
VS.HHO.SuccInterCellLB.
MultiRL
WRFD-020103

Balance
CS
WRFD-020302

Handover Based on
Coverage
WRFD-020304

PS
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Sig
WRFD-020302
WRFD-020304

Handover Based on
Coverage
CSPS
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Successful Outgoing Emergency Blind Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67191695
VS.HHO.SuccBlindHO
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.This counter complies with section "8.3.5 Hard handover" and "8.2.2 Reconfiguration
Issue 03 (2015-06-30)

1616
BSC6900 UMTS
Measurement point
CHANNEL RECONFIGURATION message as an example. During the emergency blind
COMPLETE message from the UE, the hard handover succeeds. In this case, the RNC measures
the counter in the best cell where the UE camps on before the hard handover.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HHO.SuccBlindHO
WRFD-020302

Handover Based on
Coverage

1617
BSC6900 UMTS
Number of Call Drops due to Unsuccessful Outgoing Hard Handovers for cell
Counters
Counter ID
Counter Name
Counter Description
73403776
VS.HHO.InterFreqOut.CS.
Drop
Number of CS Call Drops

due to Unsuccessful
Hard Handovers for cell
67183926
VS.HHO.IntraFreqOut.Drop
Number of Call Drops Due to

Failed Outgoing IntraFrequency Hard Handovers
for Cell
73403777
VS.HHO.InterFreqOut.PS.D
rop
Number of PS Call Drops due

to Unsuccessful Outgoing
Inter-Frequency Hard
Handovers for cell
Description
These measurement item take statistics of call drops due to unsuccessful intra-frequency and
inter-frequency hard handovers.The preceding counters comply with section "8.3.5 Hard
handover" and "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
Counter Name
Description
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.
Issue 03 (2015-06-30)

1618
BSC6900 UMTS
Figure 1-699 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 interfrequency or intra-frequency hard handover.
Issue 03 (2015-06-30)

1619
BSC6900 UMTS
Figure 1-700 Hard handover procedure (failed operation for timer expiry)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Drop
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)
WRFD-020301


Handover
1620
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HHO.InterFreqOut.PS.D
rop
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Counters Related to the Number of Successful Outgoing Inter-Frequency Hard

Handovers
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393945
PS.UlBler
Handovers Based on UL
BLER for Cell
73404081
CS.Rscp
Handovers Based on RSCP
for Cell
73404082
CS.EcNo
Handovers Based on EcNo
for Cell
73404083
PS.Rscp
Handovers Based on RSCP
for Cell
73404084
PS.EcNo
Handovers Based on EcNo
for Cell
73393946
CS.UeTxPwr
Handovers Based on UE
73393947
PS.UeTxPwr
Handovers Based on UE

1621
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393948
CS.Tcp
Handovers Based on DL
73393949
PS.Tcp
Handovers Based on DL
73393950
CS.TotalTxPwr
Handovers Based on Cell
Total Transmit Power for
Cell
73393951
PS.TotalTxPwr
Total Transmit Power for
Cell
73393952
CS.TotalRxPwr
Total Receive Power for Cell
73393953
PS.TotalRxPwr
Total Receive Power for Cell
73393954
CS.Code
Handovers Based on Code
Resources for Cell
73393955
PS.Code
Handovers Based on Code
Resources for Cell
73424204
PS.UlCE
Handovers Based on UL CE
for Cell
73424244
PS.DlCE
Handovers Based on DL CE
for Cell

1622
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73424247
CS.UlCE
Handovers Based on UL CE
for Cell
73424248
CS.DlCE
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.The
Measurement point
Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, the
measurement can be triggered at point B as shown in the figure. After determining interfrequency hard handovers, the RNC sends the PHYSICAL CHANNEL RECONFIGURATION
message to the UE. When receiving from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message, the RNC measures the counter measured in the
best cell that the UE camps on before the inter-frequency hard handover based on the handover
cause and the service type. Note: 1. If an inter-frequency hard handover is triggered due to high
BLER and the transmit power of the UE is also limited, the counter measuring the number of
successful inter-frequency hard handovers based on UL BLER and the counter measuring the
number of successful inter-frequency hard handovers based on transmit power are measured. 2.
Inter-frequency hard handovers include those that are involved in the LDR or CLB triggered by
the high power or large number of equivalent UEs. However, the RNC regards such handovers
as being triggered by high power.
Issue 03 (2015-06-30)

1623
BSC6900 UMTS
Figure 1-701 Handover Indication
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
CS.Rscp
WRFD-020302

Handover Based on
Coverage
CS.EcNo
WRFD-020302

Handover Based on
Coverage
PS.Rscp
WRFD-020302

Handover Based on
Coverage
PS.EcNo
WRFD-020302

Handover Based on
Coverage

1624
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
CS.Tcp
WRFD-020304

PS.Tcp
WRFD-020304

CS.TotalTxPwr
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
PS.TotalTxPwr
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
CS.TotalRxPwr
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
PS.TotalRxPwr
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
CS.Code
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
PS.Code
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold
PS.UlCE
WRFD-020106
Load Reshuffling
WRFD-140217
Balancing Based on
Configurable Load
Threshold

1625
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
PS.DlCE
WRFD-140217
Balancing Based on
Configurable Load
Threshold
CS.UlCE
WRFD-140217
Balancing Based on
Configurable Load
Threshold
CS.DlCE
WRFD-140217
Balancing Based on
Configurable Load
Threshold
Number of Successful Outgoing Macro & Micro Joint Inter-frequency Handovers

in PS Domain for Cell
Counters
Counter ID
Counter Name
Counter Description
73425832
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.This counter complies with section "8.3.5 Hard handover"
Measurement point
area.
Issue 03 (2015-06-30)

1626
BSC6900 UMTS
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.
Figure 1-703 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.
Issue 03 (2015-06-30)

1627
BSC6900 UMTS
Figure 1-704 Successful transport channel reconfiguration procedure
before the handover each time the RNC receives a RADIO BEARER RECONFIGURATION
COMPLETE in the target cell after sending a RADIO BEARER RECONFIGURATION
message to the UE.
Figure 1-705 Successful radio bearer reconfiguration procedure
Formula
None
Issue 03 (2015-06-30)

1628
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
PS.CoMacroMicro
WRFD-150201

WRFD-15020102
Macro & Micro Joint Interfrequency Handover
Counters Related to the Number of Successful Inter-Frequency Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
73430330
CS.CLB
Handover Based on CLB for
Cell
73430331
PS.CLB
Handover Based on CLB for
Cell
Description
These counters provide the number of successful outgoing inter-frequency hard handovers for
CS services or PS services due to CLB causes in the best cell before the handover.
Measurement point
Taking the PHYSICAL CHANNEL RECONFIGURATION message as an example, the
measurement is triggered at point B as shown in figure 1. After deciding to perform an interfrequency hard handover, the RNC sends a PHYSICAL CHANNEL RECONFIGURATION
message to the UE. After receiving from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message, the RNC measures this counter based on the
service type in the best cell that the UE camps on before the handover.
Issue 03 (2015-06-30)

1629
BSC6900 UMTS
Figure 1-706 Physical Channel Reconfiguration
Taking the TRANSPORT CHANNEL RECONFIGURATION message as an example, the

measurement is triggered at point B as shown in figure 2. After deciding to perform an interfrequency hard handover, the RNC sends a TRANSPORT CHANNEL RECONFIGURATION
message to the UE. After receiving from the UE a TRANSPORT CHANNEL
RECONFIGURATION COMPLETE message, the RNC measures this counter based on the
Issue 03 (2015-06-30)

1630
BSC6900 UMTS
Figure 1-707 Transmission Channel Reconfiguration
Taking the RADIO BEARER RECONFIGURATION message as an example, the measurement

is triggered at point B as shown in figure 3. After deciding to perform an inter-frequency hard
handover, the RNC sends a RADIO BEARER RECONFIGURATION message to the UE. After
receiving from the UE a RADIO BEARER RECONFIGURATION COMPLETE message, the
RNC measures this counter based on the service type in the best cell that the UE camps on before
the handover.
Issue 03 (2015-06-30)

1631
BSC6900 UMTS
Figure 1-708 RB Reconfiguration
Taking the RADIO BEARER SETUP message as an example, the measurement is triggered at
point B as shown in figure 4. After deciding to perform an inter-frequency hard handover, the
RNC sends a RADIO BEARER SETUP message to the UE. After receiving from the UE a
RADIO BEARER SETUP COMPLETE message, the RNC measures this counter based on the
Issue 03 (2015-06-30)

1632
BSC6900 UMTS
Figure 1-709 RB Setup
Taking the RADIO BEARER SETUP RELEASE message as an example, the measurement is
triggered at point B as shown in figure 5. After deciding to perform an inter-frequency hard
handover, the RNC sends a RADIO BEARER SETUP RELEASE message to the UE. After
receiving from the UE a RADIO BEARER SETUP RELEASE COMPLETE message, the RNC
measures this counter based on the service type in the best cell that the UE camps on before the
handover.
Issue 03 (2015-06-30)

1633
BSC6900 UMTS
Figure 1-710 RB Release
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
CS.CLB
WRFD-140217
Balancing Based on
Configurable Load
Threshold
PS.CLB
WRFD-140217
Balancing Based on
Configurable Load
Threshold

1634
BSC6900 UMTS
Number of Failed Outgoing Hard Handovers Between RNCs for Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189701
VS.HHO.FailIntraFreqOut.I
nterRNC.CfgUnsupp
Number of Failed Outgoing

Intra-Frequency Hard
Handovers Between RNCs
for Cell (Configuration
Unsupported)
67189702
nterRNC.PhyChFail

for Cell (Physical Channel
Failure)
67189703
nterRNC.ISR

for Cell (Incompatible
Simultaneous
Reconfiguration)
67189704
nterRNC.InvCfg

for Cell (Invalid
Configuration)
73393853
VS.HHO.FailInterFreqOut.I
nterRNC.CfgUnsupp

Handovers Between the
RNCs for Cell
(Configuration
Unsupported)
73393854
nterRNC.PhyChFail

RNCs for Cell (Physical
Channel Failure)
73393855
nterRNC.ISR

RNCs for Cell (Incompatible
Simultaneous
Reconfiguration)

1635
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73393856
nterRNC.InvCfg

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
in the best cell where the UE camps on before the hard handover.The preceding counters comply
with section "8.3.5 Hard handover" and "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurements are triggered at point A as shown in the following figure, taking the
PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intrafrequency 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 interfrequency 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.
Figure 1-711 Failed hard handover procedure
Formula
None
Issue 03 (2015-06-30)

1636
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
nterRNC.CfgUnsupp
WRFD-020301

Handover
nterRNC.PhyChFail
WRFD-020301

Handover
nterRNC.ISR
WRFD-020301

Handover
nterRNC.InvCfg
WRFD-020301

Handover
nterRNC.CfgUnsupp
WRFD-020302

Handover Based on
Coverage
WRFD-020304

nterRNC.PhyChFail
WRFD-020302
WRFD-020304

Handover Based on
Coverage
nterRNC.ISR
WRFD-020302
WRFD-020304

Handover Based on
Coverage
nterRNC.InvCfg
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Issue 03 (2015-06-30)

1637
BSC6900 UMTS
Number of Failed Outgoing Inter-RNC Hard Handovers for Cell (Concurrent

Procedures)
Counters
Counter ID
Counter Name
Counter Description
73393851
nterRNC.CellUpdt

for Cell (Cell update
occurred)
73393857
nterRNC.CellUpdt

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.The preceding counters comply with section "8.3.5 Hard handover" and "8.2.2
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.
Issue 03 (2015-06-30)

1638
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
nterRNC.CellUpdt
WRFD-020301

Handover
nterRNC.CellUpdt
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1639
BSC6900 UMTS
Number of Failed Outgoing Hard Handovers in RNC for Different Causes

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192558
VS.HHO.FailIntraFreqOut.
CfgUnsupp

Handovers for Cell
(Configuration
Unsupported)
67192614
nvCfg

Handovers for Cell (Invalid
Configuration)
67192559
VS.HHO.FailIntraFreqOut.P
yhChFail

Handovers for Cell (Physical
Channel Failure)
67192560
SR

Handovers for Cell
(Incompatible Simultaneous
Reconfiguration)
67183902
VS.HHO.FailInterFreqOut.
CfgUnsupp

Handovers for Cell
(Configuration
Unsupported)
67183903
VS.HHO.FailInterFreqOut.P
yhChFail

Channel Failure)
67183904
SR

Handovers for Cell
(Incompatible Simultaneous
Reconfiguration)
67183907
nvCfg

Handovers for Cell (Invalid
Configuration)

1640
BSC6900 UMTS
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.The preceding counters comply with
section "8.3.5 Hard handover" and "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurements are triggered at point A as shown in the following figure, taking the
PHYSICAL CHANNEL RECONFIGURATION message as an example. During the intrafrequency 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 interfrequencyhard handover according to the failure cause contained in the message.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
CfgUnsupp
WRFD-020301

Handover

1641
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
nvCfg
WRFD-020301

Handover
yhChFail
WRFD-020301

Handover
SR
WRFD-020301

Handover
CfgUnsupp
WRFD-020302

Handover Based on
Coverage
WRFD-020304

yhChFail
WRFD-020302
WRFD-020304

Handover Based on
Coverage
SR
WRFD-020302
WRFD-020304

Handover Based on
Coverage
nvCfg
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Failed Outgoing Intra-RNC Hard Handovers for Cell (Concurrent

Procedures)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192561
CellUpdt

Handovers for Cell (Cell
Update Occurred)

1642
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67183906
CellUpdt

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.The preceding counters comply with section "8.3.5 Hard handover" and "8.2.2
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.
Formula
None
Issue 03 (2015-06-30)

1643
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CellUpdt
WRFD-020301

Handover
CellUpdt
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Failed Outgoing Hard Handovers in RNC Due to No Response from

the UE
Counters
Counter ID
Counter Name
Counter Description
67192553
NoReply

Handovers Due to No
Response from the UE for
Cell
67183908
NoReply

Handovers Due to No
Response from the UE for
Cell
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.The preceding counters comply with section "8.3.5
Measurement point
CHANNEL RECONFIGURATION message as an example. During the intra-frequency and
inter-frequencyhard handover, the RNC sends a PHYSICAL CHANNEL
Issue 03 (2015-06-30)

1644
BSC6900 UMTS
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-715 Failed hard handover procedure (UE no response)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
NoReply
WRFD-020301

Handover
NoReply
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1645
BSC6900 UMTS
Number of Failed Outgoing Hard Handovers Between the RNCs Due to No

Response from the UE
Counters
Counter ID
Counter Name
Counter Description
73393852
nterRNC.NoReply

RNCs Due to No Response
from the UE for Cell
73393858
nterRNC.NoReply

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
in the best cell where the UE camps on before the hard handover.The preceding counters comply
with section "8.3.5 Hard handover" and "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v10.13.0).
Measurement point
CHANNEL RECONFIGURATION message as an example. During the intra-frequency and
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.
Issue 03 (2015-06-30)

1646
BSC6900 UMTS
Figure 1-716 Failed hard handover procedure (UE no response)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
nterRNC.NoReply
WRFD-020301

Handover
nterRNC.NoReply
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1647
BSC6900 UMTS
Number of Failed Preparations for Outgoing Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67192554
repFail
Number of Failed
Preparations for Outgoing
Handovers for Cell
67192555
repFail
Number of Failed
Handovers for Cell
Description
These counters provide the number of failed preparations for outgoing intra-frequency and interfrequency hard handovers. The measurement is performed in the best cell where the UE camps
on before the hard handover.The preceding counters comply with section "8.3.5 Hard handover"
Measurement point
The measurement is triggered at point A as shown in the figure, where the PHYSICAL
CHANNEL RECONFIGURATION message is used as an example. The RNC initiates a request
for an intra-frequency 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-717 Failed hard handover procedure (admission fails)
Issue 03 (2015-06-30)

1648
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-718 Failed hard handover procedure (failure in the RL establishment on the Iur
interface)
Formula
None
Unit
None
Issue 03 (2015-06-30)

1649
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
repFail
WRFD-020301

Handover
repFail
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Failed Preparations for Outgoing Hard Handovers Due to Radio Link
Establishment Failure
Counters
Counter ID
Counter Name
Counter Description
67192556
RLSetupFail
Number of Failed
Handovers Due to Radio
Link Establishment Failure
for Cell
67192557
RLSetupFail
Number of Failed
Handovers Due to Radio
Link Establishment Failure
for Cell
Description
These counters provide the number of failed preparations for outgoing intra-frequency and interfrequency 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.The preceding
3GPP TS 25.331 (v10.13.0).
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
Issue 03 (2015-06-30)

1650
BSC6900 UMTS
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-719 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.
Issue 03 (2015-06-30)

1651
BSC6900 UMTS
Figure 1-720 Failed hard handover procedure (failure in the RL establishment on the Iur
interface)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RLSetupFail
WRFD-020301

Handover
RLSetupFail
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

1652
BSC6900 UMTS
Number of Relocation Preparation Attempts with Outgoing Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67193708
Preparation Attempts with
67192551
Preparation Attempts with
Description
These counters provide the number of relocation preparation attempts with outgoing intrafrequency and inter-frequency hard handovers. The measurement is performed in the best cell
of the SRNC where the UE camps on.The preceding counters comply with section "8.6
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.
Issue 03 (2015-06-30)

1653
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-02060502
SRNS Relocation with Hard

Handover
WRFD-02060502

Handover
Number of Successful Relocation Preparations with Outgoing Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67192770
Relocation Preparations with
67192552
Relocation Preparations with
Description
These counters provide the number of successful relocation preparations with outgoing intrafrequency and inter-frequency hard handovers. The measurement is performed in the best cell
of the SRNC where the UE camps on.The preceding counters comply with section "8.6
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
Issue 03 (2015-06-30)

1654
BSC6900 UMTS
RELOCATION COMMAND message to the RNC. In this case, the RNC measures the counter
once only.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-02060502

Handover
WRFD-02060502

Handover

1655
BSC6900 UMTS
Number of Relocation Execution Attempts with Outgoing Hard Handovers

Counters
Counter ID
Counter Name
Counter Description
67189716
Execution Attempts with
67190898
Execution Attempts with
Description
These counters provide the number of relocation execution attempts with outgoing intrafrequency and inter-frequency hard handovers. The measurement is performed in the best cell
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.The preceding
3GPP TS 25.331 (v10.13.0).
Measurement point
CHANNEL RECONFIGURATION message as an example. During the relocation with intrafrequency 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.
Issue 03 (2015-06-30)

1656
BSC6900 UMTS
Figure 1-723 Reconfiguration procedure during SRNC relocation with hard handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-02060502

Handover
WRFD-02060502

Handover
Number of Successful Relocation Executions with Outgoing Hard Handovers

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189717
Relocation Executions with

1657
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67190899
Relocation Executions with
Description
These counters provide the number of successful relocation executions with outgoing intrafrequency and inter-frequency hard handovers. The measurement is performed in the best cell
controlled by the SRNC.The preceding counters comply with section "8.3.5 Hard handover" in
3GPP TS 25.331 (v10.13.0).
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.
Formula
None
Issue 03 (2015-06-30)

1658
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-02060502

Handover
WRFD-02060502

Handover
Counters Related to the Number of Failed Relocation Preparations with Outgoing

Hard Handovers for Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189708
HHO.FailRelocPrepOut.No
ResAvail

Preparations with Outgoing
Hard Handovers for Cell (No
Radio Resources Available
in Target Cell)
67189709
HHO.FailRelocPrepOut.Tex
p

(TRELOCalloc Expiry)
67189710
HHO.FailRelocPrepOut.Tgt
Fail

(Relocation Failure in Target
CN/RNC or Target System)
67189711
HHO.FailRelocPrepOut.RelocUnsupp

System)
67189712
NotAllow

Allowed)

1659
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67189713
HHO.FailRelocPrepOut.OM

(O&M Intervention)
67189714
HHO.FailRelocPrepOut.ResUnavail

Hard Handovers for Cell (No
Resource Available)
67189715

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.The preceding counters comply with section "8.6 Relocation Preparation" in
3GPP TS 25.413 (v10.10.0).
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-725 Failed SRNC relocation preparation procedure
Issue 03 (2015-06-30)

1660
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
HHO.FailRelocPrepOut.No
ResAvail
WRFD-02060502

Handover
HHO.FailRelocPrepOut.Tex
p
WRFD-02060502

Handover
Fail
WRFD-02060502

Handover
HHO.FailRelocPrepOut.RelocUnsupp
WRFD-02060502

Handover
NotAllow
WRFD-02060502

Handover
HHO.FailRelocPrepOut.OM
WRFD-02060502

Handover
HHO.FailRelocPrepOut.ResUnavail
WRFD-02060502

Handover
WRFD-02060502

Handover
Counters Related to the Number of Handovers Not Performed Due to InterFrequency Measurement Expiry
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193397
MeasTimeOut
Number of Handovers Not

Performed Due to CS InterFrequency Measurement
Expiry for Cell

1661
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67193398
VS.HHO.InterFreqOut.PS.
MeasTimeOut
Number of Handovers Not

Performed Due to PS InterFrequency 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 interfrequency measurement is initiated during the inter-frequency handover for CS and PS services.
The measurements are performed in the best cell where the UE camps on before the hard
handover.The preceding counters comply with section "8.3.5 Hard handover" and "8.2.2
Measurement point
After the inter-frequency measurement is initiated, if inter-frequency handover is not performed
before the timer for the inter-frequency measurement expires, the inter-frequency measurement
is stopped and the corresponding compressed mode (if enabled) is disabled for the UE. In this
case, the RNC measures the related counters in the best cell where the UE camps on before the
hard handover.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
MeasTimeOut
WRFD-020302

Handover Based on
Coverage
WRFD-020304

VS.HHO.InterFreqOut.PS.
MeasTimeOut
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Issue 03 (2015-06-30)

1662
BSC6900 UMTS
Number of Fast Multi-RL Setup Attempts for Outgoing Inter-frequency CS HHOs

for Cell
Counters
Counter ID
Counter Name
Counter Description
73429116
VS.HHO.AttInterFreqOut.F
astMultRLSetup.CS
Number of Fast Multi-RL

Setup Attempts for Outgoing
Inter-frequency CS HHOs
for Cell
Description
This counter provides the number of times a fast multi-RL setup attempt is initiated during an
outgoing inter-frequency CS hard handover (HHO). This counter is measured in the best cell
before the handover.
Measurement point
The measurement is triggered at point B shown in the following figure. After receiving an interfrequency measurement report, the RNC determines that a fast multi-RL setup needs to be
initiated for the outgoing inter-frequency CS HHO. During the fast multi-RL setup, the RNC
sends a message to the UE (The following figure uses the PHYSICAL CHANNEL
RECONFIGURATION message as an example). This counter is measured based on the service
type in the best cell before the outgoing inter-frequency CS HHO.
Issue 03 (2015-06-30)

1663
BSC6900 UMTS
Figure 1-726 Successful fast multi-RL setup for an outgoing inter-frequency CS HHO
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
astMultRLSetup.CS
WRFD-170102
Instant Diversity
Combination

1664
BSC6900 UMTS
Number of Fast Multi-RL Setup Attempts for Outgoing Inter-frequency PS HHOs

for Cell
Counters
Counter ID
Counter Name
Counter Description
73429117
astMultRLSetup.PS
Number of Fast Multi-RL

Setup Attempts for Outgoing
Inter-frequency PS HHOs for
Cell
Description
This counter provides the number of times a fast multi-RL setup attempt is initiated during an
outgoing inter-frequency PS hard handover (HHO). This counter is measured in the best cell
before the handover.
Measurement point
The measurement is triggered at point B shown in the following figure. After receiving an interfrequency measurement report, the RNC determines that a fast multi-RL setup needs to be
initiated for the outgoing inter-frequency PS HHO. During the fast multi-RL setup, the RNC
sends a message to the UE (The following figure uses the PHYSICAL CHANNEL
RECONFIGURATION message as an example). This counter is measured based on the service
type in the best cell before the outgoing inter-frequency PS HHO.
Issue 03 (2015-06-30)

1665
BSC6900 UMTS
Figure 1-727 Successful fast multi-RL setup for an outgoing inter-frequency PS HHO
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
astMultRLSetup.PS
WRFD-170102
Instant Diversity
Combination

1666
BSC6900 UMTS
Number of Successful Fast Multi-RL Setups for Outgoing Inter-frequency CS

HHOs for Cell
Counters
Counter ID
Counter Name
Counter Description
73429118
FastMultRLSetup.CS
Number of Successful Fast

Multi-RL Setups for
Outgoing Inter-frequency CS
HHOs for Cell
Description
This counter provides the number of successful fast multi-RL setups for outgoing inter-frequency
CS hard handovers (HHOs). This counter is measured in the best cell before the handover.
Measurement point
The measurement is triggered at point C shown in the following figure. After receiving an interfrequency measurement report, the RNC determines that a fast multi-RL setup needs to be
initiated for the outgoing inter-frequency CS HHO. During the fast multi-RL setup, the RNC
receives a message from the UE, indicating that the fast multi-RL setup is successful. The
following figure uses the PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message as an example. This counter is measured based on the service type in the best cell before
the outgoing inter-frequency CS HHO.
Issue 03 (2015-06-30)

1667
BSC6900 UMTS
Figure 1-728 Successful fast multi-RL setup for an outgoing inter-frequency CS HHO
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
FastMultRLSetup.CS
WRFD-170102
Instant Diversity
Combination

1668
BSC6900 UMTS
Number of Successful Fast Multi-RL Setups for Outgoing Inter-frequency PS

HHOs for Cell
Counters
Counter ID
Counter Name
Counter Description
73429119
FastMultRLSetup.PS
Number of Successful Fast

Multi-RL Setups for
Outgoing Inter-frequency PS
HHOs for Cell
Description
This counter provides the number of successful fast multi-RL setups for outgoing inter-frequency
PS hard handovers (HHOs). This counter is measured in the best cell before the handover.
Measurement point
The measurement is triggered at point C shown in the following figure. After receiving an interfrequency measurement report, the RNC determines that a fast multi-RL setup needs to be
initiated for the outgoing inter-frequency PS HHO. During the fast multi-RL setup, the RNC
receives a message from the UE, indicating that the fast multi-RL setup is successful. The
following figure uses the PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message as an example. This counter is measured based on the service type in the best cell before
the outgoing inter-frequency PS HHO.
Issue 03 (2015-06-30)

1669
BSC6900 UMTS
Figure 1-729 Successful fast multi-RL setup for an outgoing inter-frequency PS HHO
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
FastMultRLSetup.PS
WRFD-170102
Instant Diversity
Combination

1670
BSC6900 UMTS
Number of Times that the RNC Decides to Use Fast Multi-RL Setup for Outgoing
Inter-frequency CS HHOs for Cell
Counters
Counter ID
Counter Name
Counter Description
73429210
VS.HHO.InterFreqOut.Fast
MultRLSetup.Prep.CS

RNC Decides to Use Fast
Multi-RL Setup for Outgoing
Inter-frequency CS HHOs
for Cell
Description
This counter measures the number of times that the RNC decides to use the fast multi-RL setup
function for outgoing inter-frequency CS hard handovers. This counter is measured in the best
cell before the inter-frequency hard handover.
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving an interfrequency measurement report from the UE, the RNC determines whether to use the fast multiRL setup function for outing inter-frequency hard handovers. If so, this counter is incremented
by one based on the service type (CS or PS) in the best cell that the UE camps on before the
inter-frequency hard handover.
Issue 03 (2015-06-30)

1671
BSC6900 UMTS
Figure 1-730 The successful operation of the fast multi-RL setup function for inter-frequency
hard handovers
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
MultRLSetup.Prep.CS
WRFD-170102
Instant Diversity
Combination

1672
BSC6900 UMTS
Number of Times that the RNC Decides to Use Fast Multi-RL Setup for Outgoing
Inter-frequency PS HHOs for Cell
Counters
Counter ID
Counter Name
Counter Description
73429211
MultRLSetup.Prep.PS

RNC Decides to Use Fast
Multi-RL Setup for Outgoing
Inter-frequency PS HHOs for
Cell
Description
This counter measures the number of times that the RNC decides to use the fast multi-RL setup
function for outgoing inter-frequency PS hard handovers. This counter is measured in the best
cell before the inter-frequency hard handover.
Measurement point
The measurement is triggered at point A shown in the following figure. After receiving an interfrequency measurement report from the UE, the RNC determines whether to use the fast multiRL setup function for outing inter-frequency hard handovers. If so, this counter is incremented
by one based on the service type (CS or PS) in the best cell that the UE camps on before the
inter-frequency hard handover.
Issue 03 (2015-06-30)

1673
BSC6900 UMTS
Figure 1-731 The successful operation of the fast multi-RL setup function for inter-frequency
hard handovers
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
MultRLSetup.Prep.PS
WRFD-170102
Instant Diversity
Combination

1674
BSC6900 UMTS
1.12.16 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189830
VS.HSDPA.D2H.S
ucc
Number of
Successful Channel
Conversions from
DCH to HS-DSCH
for HSDPA Service
for Cell
Earlier than
BSC6900
V900R011
67189831
VS.HSDPA.F2H.Su
cc
Number of
Successful Channel
Conversions from
FACH to HS-DSCH
for HSDPA Service
for Cell
Earlier than
BSC6900
V900R011
67189832
VS.HSDPA.H2D.S
ucc
Number of
Successful Channel
Conversions from
HS-DSCH to DCH
for HSDPA Service
for Cell
Earlier than
BSC6900
V900R011
67189833
VS.HSDPA.H2F.Su
cc
Number of
Successful Channel
Conversions from
HS-DSCH to FACH
for HSDPA Service
for Cell
Earlier than
BSC6900
V900R011

1675
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189834
VS.HSDPA.MACD
.SuccSetup
Number of
Successful HSDPA
MAC-d Flow
Establishments for
Cell
Earlier than
BSC6900
V900R011
67202932
VS.HSDPA.UE.Me
an.Cell
Average Number of
HSDPA UEs in a
Cell
Earlier than
BSC6900
V900R011
67202941
VS.HSDPA.MACD
.Mean.Cell
Average Number of
MAC-d Flows in a
Cell
Earlier than
BSC6900
V900R011
67202894
VS.HSDPA.MeanChThroughput
Mean Downlink
Throughput of single
HSDPA MAC-d
Flows for Cell
Earlier than
BSC6900
V900R011
67189840
VS.HSDPA.MeanC
hThroughput.TotalBytes
Number of Total
Bytes Sent in
Downlink of HSDPA
MAC-d Flow for
Cell
Earlier than
BSC6900
V900R011
67204510
VS.HSDPA.MeanGoldenBeChThroughput
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE Service
for Golden
Subscriber for Cell
Earlier than
BSC6900
V900R011
67194867
VS.HSDPA.MeanG
oldenBeChThroug
hput.TotalBytes
Number of Total
Bytes Sent in
Downlink of HSDPA
MAC-d Flow of BE
Service for Golden
Subscriber for Cell
Earlier than
BSC6900
V900R011
67204511
VS.HSDPA.MeanSilverBeChThroughput
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE Service
for Silver Subscriber
for Cell
Earlier than
BSC6900
V900R011

1676
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194869
VS.HSDPA.MeanS
ilverBeChThrough
put.TotalBytes
Number of Total
Bytes Sent in
Downlink of HSDPA
MAC-d Flow of BE
Service for Silver
Subscriber for Cell
Earlier than
BSC6900
V900R011
67204512
VS.HSDPA.MeanCopperBeChThroughput
Mean Downlink
Throughput of
HSDPA MAC-d
Flow of BE Service
for Copper
Subscriber for Cell
Earlier than
BSC6900
V900R011
67194871
VS.HSDPA.MeanC
opperBeChThroug
hput.TotalBytes
Number of Total
Bytes Sent in
Downlink of HSDPA
MAC-d Flow of BE
Service for Copper
Subscriber for Cell
Earlier than
BSC6900
V900R011
67190690
VS.HSDPA.H2D.A
tt
Number of Channel
Conversion
Attempts from HSDSCH to DCH for
HSDPA Service for
Cell
Earlier than
BSC6900
V900R011
67190693
VS.HSDPA.D2H.A
tt
Number of Channel
Conversion
Attempts from DCH
to HS-DSCH for
HSDPA Service for
Cell
Earlier than
BSC6900
V900R011
67190696
VS.HSDPA.F2H.At
t
Number of Channel
Conversion
Attempts from
FACH to HS-DSCH
for HSDPA Service
for Cell
Earlier than
BSC6900
V900R011
67190697
VS.HSDPA.H2F.At
t
Number of Channel
Conversion
Attempts from HSDSCH to FACH for
HSDPA Service for
Cell
Earlier than
BSC6900
V900R011

1677
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190698
VS.HSDPA.SHO.S
ervCellChg.AttOut
Number of IntraRNC HSDPA

Serving Cell Change
Attempts for Cell
Earlier than
BSC6900
V900R011
67190699
VS.HSDPA.SHO.S
ervCellChg.SuccOut
Number of IntraRNC HSDPA

Serving Cell Change
Success in RNC for
Cell
Earlier than
BSC6900
V900R011
67195481
VS.HSDPA.SHO.S
ervCellChg.AttOutIur
Number of InterRNC HSDPA

Serving Cell Change
Attempts for Cell
Earlier than
BSC6900
V900R011
67195482
VS.HSDPA.SHO.S
ervCellChg.SuccOutIur
Number of InterRNC HSDPA

Serving Cell Change
Success for Cell
Earlier than
BSC6900
V900R011
67195483
VS.HSDPA.HHO.
H2H.AttOutIur
Number of InterRNC HSDPA Hard

Handover Attempts
Without Channel
Change for Cell
Earlier than
BSC6900
V900R011
67195484
VS.HSDPA.HHO.
H2H.SuccOutIur
Number of
Successful InterRNC HSDPA Hard
Handovers Without
Channel Change for
Cell
Earlier than
BSC6900
V900R011
67190700
VS.HSDPA.HHO.
H2H.AttOutIntraFreq
Number of IntraFrequency HSDPA

Hard Handover
Attempts Without
Channel Change for
Cell
Earlier than
BSC6900
V900R011
67190701
VS.HSDPA.HHO.
H2H.SuccOutIntraFreq
Number of
Successful IntraFrequency HSDPA
Hard Handovers
Without Channel
Change for Cell
Earlier than
BSC6900
V900R011

1678
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190702
VS.HSDPA.HHO.
H2H.AttOutInterFreq
Number of InterFrequency HSDPA

Hard Handover
Attempts Without
Channel Change for
Cell
Earlier than
BSC6900
V900R011
67190703
VS.HSDPA.HHO.
H2H.SuccOutInterFreq
Number of
Successful InterFrequency HSDPA
Hard Handovers
Without Channel
Change for Cell
Earlier than
BSC6900
V900R011
67191157
VS.HSDPA.HHO.
H2D.AttOutIntraFreq
Number of IntraFrequency H2D

Hard Handover
Attempts for Cell
Earlier than
BSC6900
V900R011
67191158
VS.HSDPA.HHO.
H2D.SuccOutIntraFreq
Number of
Successful IntraFrequency H2D
Hard Handovers for
Cell
Earlier than
BSC6900
V900R011
67191159
VS.HSDPA.HHO.
H2D.AttOutInterFreq
Number of InterFrequency H2D

Hard Handover
Attempts for Cell
Earlier than
BSC6900
V900R011
67191160
VS.HSDPA.HHO.
H2D.SuccOutInterFreq
Number of
Successful InterFrequency H2D
Hard Handovers for
Cell
Earlier than
BSC6900
V900R011
67190704
VS.HSDPA.RAB.A
ttEstab
Number of HSDPA
RAB Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67195507
VS.HSDPA.RAB.A
ttEstab.BE.Golden
Number of HSDPA
RAB Establishment
Attempts of BE
Service for Golden
Level User for Cell
Earlier than
BSC6900
V900R011

1679
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195508
VS.HSDPA.RAB.A
ttEstab.BE.Silver
Number of HSDPA
RAB Establishment
Attempts of BE
Service for Silver
Level User for Cell
Earlier than
BSC6900
V900R011
67195509
VS.HSDPA.RAB.A
ttEstab.BE.Copper
Number of HSDPA
RAB Establishment
Attempts of BE
Service for Copper
Level User for Cell
Earlier than
BSC6900
V900R011
67190705
VS.HSDPA.RAB.S
uccEstab
Number of
Successful HSDPA
RAB Establishments
for Cell
Earlier than
BSC6900
V900R011
67195510
VS.HSDPA.RAB.S
uccEstab.BE.Golden
Number of
Successful HSDPA
RAB Establishments
of BE Service for
Golden Level User
for Cell
Earlier than
BSC6900
V900R011
67195511
VS.HSDPA.RAB.S
uccEstab.BE.Silver
Number of
Successful HSDPA
RAB Establishments
of BE Service for
Silver Level User for
Cell
Earlier than
BSC6900
V900R011
67195512
VS.HSDPA.RAB.S
uccEstab.BE.Copper
Number of
Successful HSDPA
RAB Establishments
of BE Service for
Copper Level User
for Cell
Earlier than
BSC6900
V900R011
67191161
VS.HSDPA.RAB.N
ormRel.UsrInact
Number of HSDPA
RAB Releases Due
to User Inactivity for
Cell
Earlier than
BSC6900
V900R011
67191162
VS.HSDPA.RAB.A
bnormRel
Number of HSDPA
RABs Abnormal
Released for Cell
Earlier than
BSC6900
V900R011

1680
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191163
VS.HSDPA.RAB.A
bnormRel.RF
Number of HSDPA
RABs Abnormal
Released Due to RF
Cause for Cell
Earlier than
BSC6900
V900R011
67191164
VS.HSDPA.RAB.N
ormRel
Number of HSDPA
RABs Normal
Released for Cell
Earlier than
BSC6900
V900R011
73403763
VS.HSDPA.UE.Ma
x.Cell
Maximum Number
of HSDPA UEs in a
Cell
BSC6900
V900R012
73403764
VS.HSDPA.HHO.
H2D.AttOutIur
number of InterRNC H2D Hard

Handover Attempts
for Cell
BSC6900
V900R012
73403765
VS.HSDPA.HHO.
H2D.SuccOutIur
Number of
Successful InterRNC H2D Hard
Handovers for Cell
BSC6900
V900R012
73403817
VS.HSDPA.RAB.
64QAM.AttEstab
Number of HSDPA
64QAM RAB Setup
Requests for cell
BSC6900
V900R012
73403818
VS.HSDPA.RAB.
64QAM.SuccEstab
Number of HSDPA
64QAM RABs Setup
Successfully for cell
BSC6900
V900R012
73403819
VS.HSDPA.RAB.A
bnormRel.64QAM
Number of HSDPA
64QAM RABs
Abnormal Released
for cell
BSC6900
V900R012
73403820
VS.HSDPA.RAB.N
ormRel.64QAM
Number of HSDPA
64QAM RABs
Normal Released for
Cell
BSC6900
V900R012
73403821
VS.HSDPA.RAB.
MIMO.AttEstab
Number of HSDPA
MIMO RABs Setup
Request for Cell
BSC6900
V900R012
73403822
VS.HSDPA.RAB.
MIMO.SuccEstab
Number of HSDPA
MIMO RABs Setup
BSC6900
V900R012

1681
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403823
VS.HSDPA.RAB.N
ormRel.MIMO
Number of HSDPA
MIMO RABs
Normal Released for
cell
BSC6900
V900R012
73403824
VS.HSDPA.RAB.
MIMO64QAM.Att
Estab
Number of HSDPA
MIMO+64QAM
RABs Setup Request
for cell
BSC6900
V900R012
73403825
VS.HSDPA.RAB.
MIMO64QAM.Suc
cEstab
Number of HSDPA
MIMO+64QAM
RABs Setup
BSC6900
V900R012
73403826
VS.HSDPA.RAB.A
bnormRel.MIMO6
4QAM
Number of HSDPA
MIMO+64QAM
RABs Abnormal
Released for cell
BSC6900
V900R012
73403827
VS.HSDPA.RAB.N
ormRel.MIMO64Q
AM
Number of HSDPA
MIMO+64QAM
RABs Normal
Released for cell
BSC6900
V900R012
73403828
VS.HSDPA.RAB.D
C.AttEstab
Number of DCHSDPA RAB Setup

Requests in the
primary carrier of
DC-HSDPA counted
for cell
BSC6900
V900R012
73403829
VS.HSDPA.RAB.D
C.SuccEstab
Number of DCHSDPA RABs Setup

Successfully in the
primary carrier of
DC-HSDPA counted
for cell
BSC6900
V900R012
73403830
VS.HSDPA.RAB.A
bnormRel.DC
Number of DCHSDPA RABs

Abnormal Released
in the primary carrier
of DC counted for
Cell(including RF
Cause)
BSC6900
V900R012

1682
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403831
VS.HSDPA.RAB.N
ormRel.DC
Number of DCHSDPA RABs

Normal Released in
the primary carrier of
DC counted for Cell
BSC6900
V900R012
73403832
VS.HSDPA.RAB.A
bnormRel.MIMO
Number of HSDPA
MIMO RABs
Abnormal Released
for cell(Including RF
Cause)
BSC6900
V900R012
67204259
VS.HSDPA.UE.Me
an.CAT1.6
Average Number of
HSDPA UEs with
Category 1-6 in a
Cell
BSC6900
V900R012
67193578
VS.HSDPA.UE.Ma
x.CAT1.6
Maximum Number
of HSDPA UEs with
Category 1-6 in a
Cell
BSC6900
V900R012
67204260
VS.HSDPA.UE.Me
an.CAT7.10
Average Number of
HSDPA UEs with
Category 7-10 in a
Cell
BSC6900
V900R012
67193581
VS.HSDPA.UE.Ma
x.CAT7.10
Maximum Number
of HSDPA UEs with
Category 7-10 in a
Cell
BSC6900
V900R012
67204261
VS.HSDPA.UE.Me
an.CAT11.12
Average Number of
HSDPA UEs with
Category 11-12 in a
Cell
BSC6900
V900R012
67193584
VS.HSDPA.UE.Ma
x.CAT11.12
Maximum Number
of HSDPA UEs with
Category 11-12 in a
Cell
BSC6900
V900R012
67204262
VS.HSDPA.UE.Me
an.CAT13.14
Average Number of
HSDPA UEs with
Category 13-14 in a
Cell
BSC6900
V900R012
67193587
VS.HSDPA.UE.Ma
x.CAT13.14
Maximum Number
of HSDPA UEs with
Category 13-14 in a
Cell
BSC6900
V900R012

1683
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204263
VS.HSDPA.UE.Me
an.CAT15.16
Average Number of
HSDPA UEs with
Category 15-16 in a
Cell
BSC6900
V900R012
67193590
VS.HSDPA.UE.Ma
x.CAT15.16
Maximum Number
of HSDPA UEs with
Category 15-16 in a
Cell
BSC6900
V900R012
67204264
VS.HSDPA.UE.Me
an.CAT17.20
Average Number of
HSDPA UEs with
Category 17-20 in a
Cell
BSC6900
V900R012
67193593
VS.HSDPA.UE.Ma
x.CAT17.20
Maximum Number
of HSDPA UEs with
Category 17-20 in a
Cell
BSC6900
V900R012
67204265
VS.HSDPA.UE.Me
an.CAT21.24
Average Number of
HSDPA UEs with
Category 21-24 in a
Cell
BSC6900
V900R012
67193596
VS.HSDPA.UE.Ma
x.CAT21.24
Maximum Number
of HSDPA UEs with
Category 21-24 in a
Cell
BSC6900
V900R012
73393828
VS.HSDPA.MACD
.AttSetup
Number of HSDPA
MAC-d Flow
Establishment
Requests for Cell
BSC6900
V900R012
73393830
VS.HSDPA.RAB.F
ailEstab.DLPower.
Cong
Number of Failed
HSDPA Service
Establishments Due
to DL Power
Insufficiency for Cell
BSC6900
V900R012
73393831
VS.HSDPA.RAB.F
ailEstab.DLIUBBa
nd.Cong
Number of Failed
HSDPA Service
Establishments Due
to DL Iub Bandwidth
BSC6900
V900R012

1684
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73410484
VS.PS.Conv.Kbps.
HSDSCH
Average downlink
throughput of the
Traffic PS
Conversational
beared on HSDSCH
for cell
BSC6900
V900R012
73393912
VS.PS.Conv.Traffi
c.HSDSCH
Number of downlink
bytes of Transport
Blocks of Traffic PS
Conversational
beared on HSDSCH
for cell
BSC6900
V900R012
73410491
VS.HSDPA.
64QAM.UE.Mean.
Cell
Average Number of
64QAM UEs in a
Cell
BSC6900
V900R012
73410492
VS.HSDPA.MIMO
.UE.Mean.Cell
Average Number of
MIMO UEs in a Cell
BSC6900
V900R012
73410493
VS.HSDPA.MIMO
64QAM.UE.Mean.
Cell
Average Number of
MIMO+64QAM
UEs in a Cell
BSC6900
V900R012
73410508
VS.HSDPA.DC.PR
IM.UE.Mean.Cell
Average number of
DC-HSDPA UEs in
anchor carrier in a
Cell
BSC6900
V900R012
73410509
VS.HSDPA.DC.SE
C.UE.Mean.Cell
Average number of
DC-HSDPA UEs in
supplementary
carrier in a Cell
BSC6900
V900R012
73421686
VS.HSDPA.DRD.A
ttOut.Intelligence
Number of Outgoing
DRD Attempts for
HSDPA Users
Through Intelligent
User Recognition for
Cell
BSC6900
V900R012
73421687
VS.HSDPA.DRD.S
uccOut.Intelligence
Number of
Successful Outgoing
DRDs for HSDPA
Users Through
Intelligent User
Recognition for Cell
BSC6900
V900R012

1685
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421688
VS.HSDPA.DRD.A
ttIn.Intelligence
Number of Incoming
DRD Attempts for
HSDPA Users
Through Intelligent
User Recognition for
Cell
BSC6900
V900R012
73421689
VS.HSDPA.DRD.S
uccIn.Intelligence
Number of
Successful Incoming
DRDs for HSDPA
Users Through
Intelligent User
BSC6900
V900R012
73422167
VS.HSDPA.RAB.A
bnormRel.H2P
Number of RABs
Abnormally
Released for PS
HSDPA Services
during the State
Transition from
CELL_DCH to
CELL_PCH or
URA_PCH for Cell
BSC6900
V900R012
73423377
VS.HSDPA.UE.Ma
x.CAT25.28
Maximum Number
of HSDPA UEs with
Category 25-28 in a
Cell
BSC6900
V900R013
73441138
VS.HSDPA.UE.Me
an.CAT25.28
Average Number of
HSDPA UEs with
Category 25-28 in a
Cell
BSC6900
V900R013
73423378
VS.HSDPA.RAB.D
CMIMO.AttEstab
Number of DCHSDPA+MIMO
RAB Setup Requests
in the Primary
Carrier of DCHSDPA for Cell
BSC6900
V900R013
73423379
VS.HSDPA.RAB.D
CMIMO.SuccEsta
b
Number of
Successful DCHSDPA+MIMO
RAB Setups in the
Primary Carrier of
DC-HSDPA for cell
BSC6900
V900R013

1686
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423380
VS.HSDPA.RAB.D
CMIMO.NormRel
Number of Normal
DC-HSDPA+MIMO
RAB Releases in the
Primary Carrier of
DC-HSDPA for cell
BSC6900
V900R013
73423381
VS.HSDPA.RAB.D
CMIMO.AbnormR
el
Number of
Abnormal DCHSDPA+MIMO
RAB Releases in the
Primary Carrier of
DC-HSDPA for cell
BSC6900
V900R013
73441141
VS.HSDPA.MeanC
hThrouput.HighLoad
Mean Throughput on
HSDPA MAC-d
Flow for Cell
(Excluding the Data
of Low-Traffic
Users)
BSC6900
V900R013
73423462
VS.HSDPA.Traffic.
HighLoad
Number of Bytes
Sent on HSDPA
MAC-d Flow for
Cell (Excluding the
Bytes of Low-Traffic
Users)
BSC6900
V900R013
73441142
VS.HSDPA.UE.Me
an.Cell.Free
Average Number of
Free HSDPA Users
in a Cell
BSC6900
V900R013
73423469
VS.HSDPA.UE.Ma
x.Cell.Free
Maximum Number
of Free HSDPA
Users in a Cell
BSC6900
V900R013
73423900
VS.HSDPA.SHO.I
ubBasedServCellC
hg.AttOut
Number of Serving
Cell Change
Attempts Triggered
by Unbalanced Iub
Resources for Cell
BSC6900
V900R013
73423901
VS.HSDPA.SHO.I
ubBasedServCellC
hg.SuccOut
Number of
Successful Serving
Cell Changes
Triggered by
Unbalanced Iub
Resources for Cell
BSC6900
V900R013

1687
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425884
VS.HSDPA.
4C.PRIM.UE.Mea
n.Cell
Average Number of
4C-HSDPA UEs
Using This Cell as
the Primary Carrier
Cell
BSC6900
V900R015C00
73425887
VS.HSDPA.
3C.PRIM.UE.Mea
n.Cell
Average Number of
3C-HSDPA UEs
Using This Cell as
the Primary Carrier
Cell
BSC6900
V900R015C00
73425890
VS.HSDPA.MC.SE
C.UE.Mean.Cell
Average Number of
4C-HSDPA/DBHSDPA/DCHSDPA UEs Using
This Cell as the
Secondary Carrier
Cell
BSC6900
V900R015C00
73425893
VS.HSDPA.DB.PR
IM.UE.Mean.Cell
Average Number of
DB-HSDPA UEs
Using This Cell as
the Primary Carrier
Cell
BSC6900
V900R015C00
73425928
VS.HSDPA.RAB.A
bnormRel.DC2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of DCHSDPA UEs to
CELL/URA_PCH
BSC6900
V900R015C00
73425929
VS.HSDPA.RAB.A
bnormRel.
64QAM2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of
HSDPA+64QAM
UEs to CELL/
URA_PCH
BSC6900
V900R015C00
73425930
VS.HSDPA.RAB.A
bnormRel.MIMO2
P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of MIMO
UEs to CELL/
URA_PCH
BSC6900
V900R015C00

1688
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425931
VS.HSDPA.RAB.A
bnormRel.DCMIM
O2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of DCHSDPA+MIMO
UEs to CELL/
URA_PCH
BSC6900
V900R015C00
73425932
VS.HSDPA.RAB.A
bnormRel.MIMO6
4QAM2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of MIMO
+64QAM UEs to
CELL/URA_PCH
BSC6900
V900R015C00
73425933
VS.HSDPA.RAB.A
bnormRel.3C2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of 3CHSDPA UEs to
CELL/URA_PCH
BSC6900
V900R015C00
73425934
VS.HSDPA.RAB.A
bnormRel.
3CMIMO2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of 3CHSDPA+MIMO
UEs to CELL/
URA_PCH
BSC6900
V900R015C00
73425935
VS.HSDPA.RAB.A
bnormRel.4C2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of 4CHSDPA UEs to
CELL/URA_PCH
BSC6900
V900R015C00

1689
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425936
VS.HSDPA.RAB.A
bnormRel.
4CMIMO2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of 4CHSDPA+MIMO
UEs to CELL/
URA_PCH
BSC6900
V900R015C00
73425937
VS.HSDPA.RAB.A
bnormRel.DB2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of DBHSDPA UEs to
CELL/URA_PCH
BSC6900
V900R015C00
73425938
VS.HSDPA.RAB.A
bnormRel.DBMIM
O2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of DBHSDPA+MIMO
UEs to CELL/
URA_PCH
BSC6900
V900R015C00
73425939
VS.HSDPA.RAB.N
ormRel.DC.All
Number of Normal
RAB Releases of
DC-HSDPA UEs for
Cell (All Scenarios)
BSC6900
V900R015C00
73425940
VS.HSDPA.RAB.N
ormRel.
64QAM.All
Number of Normal
RAB Releases of
HSDPA+64QAM
UEs for Cell (All
Scenarios)
BSC6900
V900R015C00
73425941
VS.HSDPA.RAB.N
ormRel.MIMO.All
Number of Normal
RAB Releases of
HSDPA+MIMO
UEs for Cell (All
Scenarios)
BSC6900
V900R015C00
73425942
VS.HSDPA.RAB.N
ormRel.DCMIMO.
All
Number of Normal
RAB Releases of
DC-HSDPA+MIMO
UEs for Cell (All
Scenarios)
BSC6900
V900R015C00

1690
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425943
VS.HSDPA.RAB.N
ormRel.MIMO64Q
AM.All
Number of Normal
RAB Releases of
HSDPA MIMO
+64QAM UEs for
BSC6900
V900R015C00
73425944
VS.HSDPA.RAB.N
ormRel.3C.All
Number of Normal
RAB Releases of 3CHSDPA UEs for Cell
(All Scenarios)
BSC6900
V900R015C00
73425945
VS.HSDPA.RAB.N
ormRel.
3CMIMO.All
Number of Normal
RAB Releases of 3CHSDPA+MIMO
UEs for Cell (All
Scenarios)
BSC6900
V900R015C00
73425946
VS.HSDPA.RAB.N
ormRel.4C.All
Number of Normal
RAB Releases of 4CHSDPA UEs for Cell
(All Scenarios)
BSC6900
V900R015C00
73425947
VS.HSDPA.RAB.N
ormRel.
4CMIMO.All
Number of Normal
RAB Releases of 4CHSDPA+MIMO
UEs for Cell (All
Scenarios)
BSC6900
V900R015C00
73425948
VS.HSDPA.RAB.N
ormRel.DB.All
Number of Normal
RAB Releases of
DB-HSDPA UEs for
BSC6900
V900R015C00
73425949
VS.HSDPA.RAB.N
ormRel.DBMIMO.
All
Number of Normal
RAB Releases of
DB-HSDPA+MIMO
UEs for Cell (All
Scenarios)
BSC6900
V900R015C00
73426132
VS.HSDPA.UE.Me
an.CAT29
Average number of
Category 29 HSDPA
users in a cell
BSC6900
V900R015C00
73426133
VS.HSDPA.UE.Ma
x.CAT29
Maximum number of
Category 29 HSDPA
users in a cell
BSC6900
V900R015C00
73426136
VS.HSDPA.UE.Me
an.CAT30
Average number of
Category 30 HSDPA
users in a cell
BSC6900
V900R015C00

1691
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426137
VS.HSDPA.UE.Ma
x.CAT30
Maximum number of
Category 30 HSDPA
users in a cell
BSC6900
V900R015C00
73426140
VS.HSDPA.UE.Me
an.CAT31
Average number of
Category 31 HSDPA
users in a cell
BSC6900
V900R015C00
73426141
VS.HSDPA.UE.Ma
x.CAT31
Maximum number of
Category 31 HSDPA
users in a cell
BSC6900
V900R015C00
73426144
VS.HSDPA.UE.Me
an.CAT32
Average number of
Category 32 HSDPA
users in a cell
BSC6900
V900R015C00
73426145
VS.HSDPA.UE.Ma
x.CAT32
Maximum number of
Category 32 HSDPA
users in a cell
BSC6900
V900R015C00
73426170
VS.HSDPA.SRBoH
.UE.Mean.Cell
Average number of
users capable of the
SRB over HSDPA
feature in a cell
BSC6900
V900R015C00
73426094
VS.HSDPA.RAB.
3CMIMO.AttEstab
Number of RAB
Setup Attempts for
Cell When 3CHSDPA with MIMO
Applied
BSC6900
V900R015C00
73426095
VS.HSDPA.RAB.
3CMIMO.SuccEsta
b
Number of
Successful RAB
Setups for Cell When
3C-HSDPA with
MIMO Applied
BSC6900
V900R015C00
73426096
VS.HSDPA.RAB.A
bnormRel.
3CMIMO
Number of
Abnormally
Released RABs for
Applied (RF
Exceptions
Considered)
BSC6900
V900R015C00
73426097
VS.HSDPA.RAB.N
ormRel.3CMIMO
Number of Normally
Released RABs for
Applied
BSC6900
V900R015C00

1692
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426098
VS.HSDPA.RAB.
3C.AttEstab
Number of RAB
Setup Attempts for
Cell When 3CHSDPA Applied
BSC6900
V900R015C00
73426099
VS.HSDPA.RAB.
3C.SuccEstab
Number of
Successful RAB
3C-HSDPA Applied
BSC6900
V900R015C00
73426100
VS.HSDPA.RAB.A
bnormRel.3C
Number of
Abnormally
Released RABs for
Cell When 3CHSDPA Applied (RF
Exceptions
Considered)
BSC6900
V900R015C00
73426101
VS.HSDPA.RAB.N
ormRel.3C
Number of Normally
Released RABs for
BSC6900
V900R015C00
73426102
VS.HSDPA.RAB.
4CMIMO.AttEstab
Number of RAB
Setup Attempts for
Cell Where 4CHSDPA with MIMO
Applied
BSC6900
V900R015C00
73426103
VS.HSDPA.RAB.
4CMIMO.SuccEsta
b
Number of
Successful RAB
4C-HSDPA with
MIMO Applied
BSC6900
V900R015C00
73426104
VS.HSDPA.RAB.A
bnormRel.
4CMIMO
Number of
Abnormally
Released RABs for
Applied (RF
Exceptions
Considered)
BSC6900
V900R015C00
73426105
VS.HSDPA.RAB.N
ormRel.4CMIMO
Number of Normally
Released RABs for
Applied
BSC6900
V900R015C00

1693
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426106
VS.HSDPA.RAB.D
BMIMO.AttEstab
Number of RAB
Setup Attempts for
Cell When DBHSDPA with MIMO
Applied
BSC6900
V900R015C00
73426107
VS.HSDPA.RAB.D
BMIMO.SuccEstab
Number of
Successful RAB
DB-HSDPA with
MIMO Applied
BSC6900
V900R015C00
73426108
VS.HSDPA.RAB.A
bnormRel.DBMIM
O
Number of
Abnormal Released
RABs for Cell When
DB-HSDPA with
MIMO Applied (RF
Exceptions
Considered)
BSC6900
V900R015C00
73426109
VS.HSDPA.RAB.N
ormRel.DBMIMO
Number of Normally
Released RABs for
Cell When DBHSDPA with MIMO
Applied
BSC6900
V900R015C00
73426110
VS.HSDPA.RAB.
4C.AttEstab
Number of RAB
Setup Attempts for
BSC6900
V900R015C00
73426111
VS.HSDPA.RAB.
4C.SuccEstab
Number of
Successful RAB
4C-HSDPA Applied
BSC6900
V900R015C00
73426112
VS.HSDPA.RAB.A
bnormRel.4C
Number of
Abnormal Released
RABs for Cell When
4C-HSDPA Applied
(RF Exceptions
Considered)
BSC6900
V900R015C00
73426113
VS.HSDPA.RAB.N
ormRel.4C
Number of Normally
Released RABs for
BSC6900
V900R015C00

1694
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426114
VS.HSDPA.RAB.D
B.AttEstab
Number of RAB
Setup Attempts for
Cell When DBHSDPA Applied
BSC6900
V900R015C00
73426115
VS.HSDPA.RAB.D
B.SuccEstab
Number of
Successful RAB
DB-HSDPA Applied
BSC6900
V900R015C00
73426116
VS.HSDPA.RAB.A
bnormRel.DB
Number of
Abnormally
Released RABs for
Cell When DBHSDPA Applied (RF
Exceptions
Considered)
BSC6900
V900R015C00
73426117
VS.HSDPA.RAB.N
ormRel.DB
Number of Normally
Released RABs for
Cell When DBHSDPA Applied
BSC6900
V900R015C00
73426316
VS.HSDPA.RAB.A
bnormRel.SRBoH.
H2P
Number of
Abnormally
Released RABs
During State
Transition of SRB
over HSDPA Users
to CELL_PCH or
URA_PCH for Cell
BSC6900
V900R015C00
73426317
VS.HSDPA.RAB.A
bnormRel.SRBoH
Number of
Abnormally
Released RABs of
SRB over HSDPA
Users for Cell
BSC6900
V900R015C00
73426318
VS.HSDPA.RAB.N
ormRel.SRBoH.All
Number of Normally
Released RABs of
SRB over HSDPA
Users for Cell (All
Scenarios)
BSC6900
V900R015C00

1695
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426883
VS.HSDPA.RAB.A
bnormRel.H2F
Number of Times
RAB Is Abnormally
Released for HSDPA
UEs During State
Transitions from
CELL_DCH to
CELL_FACH
BSC6900
V900R015C00
73426884
VS.HSDPA.RAB.A
bnormRel.CellDC
H.CellUpdt
Number of Times PS
Service Is
Abnormally
Released for HSDPA
UEs in CELL_DCH
State Due to Cell
Update Failures
BSC6900
V900R015C00
73443312
VS.HSDPA.SumThroughput
Sum of the Sampled

RLC Throughput of
HSDPA Users in a
Cell
BSC6900
V900R015C00
73426999
VS.HSDPA.SamplesThroughput
Number of Times the

RLC Throughput Is
Not 0 for HSDPA
Users in a Cell
BSC6900
V900R015C00
73444431
VS.HSDPA.Golden
UE.Mean.Cell
Average Number of
Gold HSDPA Users
for Cell
BSC6900
V900R016C00
73444432
VS.HSDPA.SilverU
E.Mean.Cell
Average Number of
Silver HSDPA Users
for Cell
BSC6900
V900R016C00
73444433
VS.HSDPA.Copper
UE.Mean.Cell
Average Number of
Copper HSDPA
Users for Cell
BSC6900
V900R016C00
Issue 03 (2015-06-30)

1696
BSC6900 UMTS
Counter
Sub Counter
VS.HSDPA.UE.Mean.Cell
VS.HSDPA.UE.Mean.CAT1.6
VS.HSDPA.UE.Mean.CAT29
VS.HSDPA.MeanChThroughput.TotalBytes
VS.HSDPA.MeanGoldenBeChThroughput.
TotalBytes
VS.HSDPA.MeanSilverBeChThroughput.T
otalBytes
VS.HSDPA.MeanCopperBeChThroughput.
TotalBytes
VS.HSDPA.RAB.AttEstab
VS.HSDPA.RAB.AttEstab.BE.Golden
VS.HSDPA.RAB.AttEstab.BE.Silver
VS.HSDPA.RAB.AttEstab.BE.Copper
VS.HSDPA.RAB.SuccEstab.BE.Golden
VS.HSDPA.RAB.SuccEstab.BE.Silver
VS.HSDPA.RAB.SuccEstab.BE.Copper
Number of Successful Channel Reconfigurations

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189831
VS.HSDPA.F2H.Succ
FACH to HS-DSCH for
HSDPA Service for Cell
67189830
VS.HSDPA.D2H.Succ
DCH to HS-DSCH for

1697
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67189832
VS.HSDPA.H2D.Succ
HS-DSCH to DCH for
67189833
VS.HSDPA.H2F.Succ
HS-DSCH to FACH for
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
measured only in the cell with the primary carrier. The preceding counters comply with section
"8 RANAP Procedures" in 3GPP TS 25.413 (v9.5.1).
Counter Name
Description
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.
Issue 03 (2015-06-30)

1698
BSC6900 UMTS
Figure 1-732 Dynamic channel configuration procedure (RB reconfiguration)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.F2H.Succ
WRFD-01061111
VS.HSDPA.D2H.Succ
WRFD-01061111
VS.HSDPA.H2D.Succ
WRFD-01061111
VS.HSDPA.H2F.Succ
WRFD-01061111
Number of Successful HSDPA MAC-d Flow Establishments for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189834
VS.HSDPA.MACD.SuccSetup
HSDPA MAC-d Flow
Establishments for Cell

1699
BSC6900 UMTS
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.
This counter complies with section "8.2.17 Radio Link Setup","8.3.1 Radio Link
Addition","8.3.2 Synchronised Radio Link Reconfiguration Preparation" in 3GPP TS 25.433
(v10.10.0) .
Measurement point
During the RL reconfiguration, if the RADIO LINK RECONFIGURATION PREPARE
message contains an IE "HSDSCH FDD Information" or "HS-DSCH MAC-d Flows To Add",
it indicates that the RL is set up for HSDPA service. The measurement is triggered at point C
as shown in the following figure. When the RNC sends the NodeB a RADIO LINK
RECONFIGURATION COMMIT message, this counter is measured in the cell in which the
RL is set up.
Figure 1-733 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.
Issue 03 (2015-06-30)

1700
BSC6900 UMTS
Figure 1-734 Radio link setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.MACD.SuccSetup
WRFD-010610
HSDPA Introduction
Package
Counter ID
Counter Name
Counter Description
67202932
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.
64QAM.UE.Mean.Cell
Average Number of 64QAM

UEs in a Cell
73410493
VS.HSDPA.MIMO64QAM.
UE.Mean.Cell
Average Number of MIMO

+64QAM UEs in a Cell
Number of HSDPA UEs in a Cell

Counters
Issue 03 (2015-06-30)

1701
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73410508
VS.HSDPA.DC.PRIM.UE.
Mean.Cell
Average number of DCHSDPA UEs in anchor

carrier in a Cell
73410509
VS.HSDPA.DC.SEC.UE.M
ean.Cell
Average number of DCHSDPA UEs in

supplementary carrier in a
Cell
73441142
VS.HSDPA.UE.Mean.Cell.
Free
Average Number of Free

HSDPA Users in a Cell
73423469
VS.HSDPA.UE.Max.Cell.Fr
ee
Maximum Number of Free

73425884
VS.HSDPA.
4C.PRIM.UE.Mean.Cell
Average Number of 4CHSDPA UEs Using This Cell

as the Primary Carrier Cell
73425887
VS.HSDPA.
Average Number of 3CHSDPA UEs Using This Cell

73425890
VS.HSDPA.MC.SEC.UE.M
ean.Cell
Average Number of 4CHSDPA/DB-HSDPA/DCHSDPA UEs Using This Cell

as the Secondary Carrier Cell
73425893
VS.HSDPA.DB.PRIM.UE.
Mean.Cell
Average Number of DBHSDPA UEs Using This Cell

73426170
VS.HSDPA.SRBoH.UE.Me
an.Cell
Average number of users

capable of the SRB over
HSDPA feature in a cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393975
VS.HSDPA.
64QAM.UE.Mean.Cell.DENO

UEs in a Cell(Denominator)
73393974
VS.HSDPA.
64QAM.UE.Mean.Cell.NU
M

UEs in a Cell(Numerator)

1702
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73393979
VS.HSDPA.MIMO64QAM.
UE.Mean.Cell.DENO

(Denominator)
73393978
VS.HSDPA.MIMO64QAM.
UE.Mean.Cell.NUM

(Numerator)
73423471
Free.DENO
Free.DENO
73423470
Free.NUM
Free.NUM
Description
These counters provide the average number and maximum number of HSDPA UEs in a serving
cell when different technologies are used.
All these counters excluding VS.HSDPA.DC.SEC.UE.Mean.Cell and
VS.HSDPA.MC.SEC.UE.Mean.Cell are measured only in the primary cell for once for DCHSDPA, 3C-HSDPA, 4C-HSDPA, or DB-HSDPA users.
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]
Issue 03 (2015-06-30)

1703
BSC6900 UMTS
VS.HSDPA.MIMO64QAM.UE.Mean.Cell =
[VS.HSDPA.MIMO64QAM.UE.Mean.Cell.NUM]/
[VS.HSDPA.MIMO64QAM.UE.Mean.Cell.DENO]
VS.HSDPA.UE.Mean.Cell.Free = [VS.HSDPA.UE.Mean.Cell.Free.NUM]/
[VS.HSDPA.UE.Mean.Cell.Free.DENO]
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061016
16 HSDPA Users per Cell
WRFD-010622
WRFD-010623
WRFD-01061003
WRFD-020101
Admission Control
VS.HSDPA.
64QAM.UE.Mean.Cell
WRFD-010683
Downlink 64QAM
VS.HSDPA.MIMO64QAM.
UE.Mean.Cell
WRFD-010693
DL 64QAM+MIMO
VS.HSDPA.DC.PRIM.UE.
Mean.Cell
WRFD-010696
DC-HSDPA
VS.HSDPA.DC.SEC.UE.M
ean.Cell
WRFD-010696
DC-HSDPA
Free
WRFD-01061003
VS.HSDPA.UE.Max.Cell.Fr
ee
WRFD-01061003
VS.HSDPA.
WRFD-150207
4C-HSDPA
WRFD-150223
MC-HSDPA+MIMO
VS.HSDPA.
WRFD-150250
3C-HSDPA
WRFD-150223
MC-HSDPA+MIMO
VS.HSDPA.UE.Max.Cell
Issue 03 (2015-06-30)

1704
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HSDPA.MC.SEC.UE.M
ean.Cell
WRFD-150250
3C-HSDPA
WRFD-150207
4C-HSDPA
WRFD-150209
DB-HSDPA
WRFD-010696
DC-HSDPA
WRFD-150208
Flexible Dual Carrier

HSDPA
WRFD-010699
WRFD-150227
WRFD-150223
DC-HSDPA+MIMO
DB-HSDPA+MIMO
MC-HSDPA+MIMO
VS.HSDPA.DB.PRIM.UE.
Mean.Cell
WRFD-150209
DB-HSDPA
WRFD-150227
DB-HSDPA+MIMO
VS.HSDPA.SRBoH.UE.Me
an.Cell
WRFD-010652
SRB over HSDPA
Counter ID
Counter Name
Counter Description
67202941
VS.HSDPA.MACD.Mean.C
ell
Average Number of MAC-d

Flows in a Cell
Number of MAC-d Flows in a Cell

Counters
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
Issue 03 (2015-06-30)

1705
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.MACD.Mean.C
ell
WRFD-01061016
WRFD-010622
WRFD-010623
Mean Downlink Throughput of single HSDPA MAC-d Flows

Counters
Counter ID
Counter Name
Counter Description
67202894
Mean Downlink Throughput

of single HSDPA MAC-d
Flows for Cell
67204510

of HSDPA MAC-d Flow of
Subscriber for Cell
67204511

Subscriber for Cell
67204512

Subscriber for Cell
73410484
VS.PS.Conv.Kbps.HSDSC
H
Average downlink
throughput of the Traffic PS
Conversational beared on
HSDSCH for cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190567
VS.HSDPA.MeanChThroug
hput.Times
Duration of HSDPA MAC-D

Flow Sending Data for Cell

1706
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194872
VS.HSDPA.MeanCopperBe
ChThroughput.Times
Duration of Copper BE
HSDPA MAC-D Flow
Sending Data for Cell
67194868
VS.HSDPA.MeanGoldenBe
ChThroughput.Times
Duration of Golden BE
HSDPA MAC-D Flow
67194870
VS.HSDPA.MeanSilverBeC
hThroughput.Times
Duration of Silver BE
HSDPA MAC-D Flow
73393913
VS.PS.Conv.Times.HSDSC
H
Duration of PS
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
counter is measured only in the primary cell based on the total throughput on the primary and
secondary carriers.
Issue 03 (2015-06-30)
Counter Name
Description
VS.HSDPA.MeanChThroughput provides
the mean downlink throughput of all single
HSDPA MAC-d flows in a cell.
VS.HSDPA.MeanGoldenBeChThroughput,
VS.HSDPA.MeanSilverBeChThroughput,
and VS.HSDPA.MeanCopperBeChThroughput provide the mean downlink
throughput of HSDPA MAC-d flows of BE
services for golden subscribers, silver
subscribers, and copper subscribers in a cell,
respectively.
respectively.

1707
BSC6900 UMTS
Counter Name
Description
respectively.
VS.PS.Conv.Kbps.HSDSCH
VS.PS.Conv.Kbps.HSDSCH provides the

average downlink throughput of single MACd 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
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
Issue 03 (2015-06-30)

1708
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010610
HSDPA Introduction
Package
WRFD-01061008

WRFD-020806

on SPI Weight
WRFD-01061008
WRFD-020806

on SPI Weight
WRFD-01061008
WRFD-020806

on SPI Weight
VS.PS.Conv.Kbps.HSDSC
H
WRFD-010617
WRFD-010501
Number of Total Bytes Sent in Downlink of HSDPA MAC-d Flow

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189840
hput.TotalBytes
Number of Total Bytes Sent

in Downlink of HSDPA
MAC-d Flow for Cell
67194867
ChThroughput.TotalBytes

MAC-d Flow of BE Service
for Golden Subscriber for
Cell
67194869

for Silver Subscriber for Cell

1709
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194871

for Copper Subscriber for
Cell
73393912
VS.PS.Conv.Traffic.HSDSC
H
Number of downlink bytes of

Transport Blocks of Traffic
PS Conversational beared on
HSDSCH for cell
Description
These counters provide the number of bytes sent in the downlink for a single HSDPA MAC-d
flow according to user priorities or service types in a serving cell.
For multi-carrier HSDPA users, this counter is measured only in the primary cell based on the
total number of bytes sent on the primary and secondary carriers.
VS.HSDPA.MeanChThroughput provides total number of bytes sent in the downlink on all
HSDPA Mac-d flows.
VS.HSDPA.MeanGoldenBeChThroughput, VS.HSDPA.MeanSilverBeChThroughput, and
VS.HSDPA.MeanCopperBeChThroughput provide the number of bytes sent in the downlink
on the HSDPA MAC-d flows of BE services for golden subscribers, silver subscribers, and
copper subscribers in a cell, respectively.
VS.PS.Conv.Kbps.HSDSCH provides the number of bytes sent in the downlink on the MAC-d
flows of PS conversational services carried on HS-DSCH.
Measurement point
The RNC measures the number of total bytes (including all types of service data) sent in the
downlink at the RLC layer of the MAC-d flow in the serving cell. When data of BE services for
golden/silver/copper subscribers or data of PS conversational services carried on the HS-DSCH
is sent in the serving cell, the RNC measures the total number of bytes sent in the downlink at
the RLC layer of the MAC-d flow HSDPA serving cell. The total bytes do not include the RLC
header and the retransmitted data.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

1710
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
hput.TotalBytes
WRFD-010610
HSDPA Introduction
Package
WRFD-01061008

WRFD-020806

on SPI Weight
WRFD-01061008
WRFD-020806

on SPI Weight
WRFD-01061008
WRFD-020806

on SPI Weight
VS.PS.Conv.Traffic.HSDSC
H
WRFD-010617
WRFD-010501
Number of Handover Attempts Between Channels of Different Types

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
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

1711
BSC6900 UMTS
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. The preceding counters comply with section "8.2.2 Reconfiguration procedures" in
3GPP TS 25.331 (v10.13.0).
Counter Name
Description
VS.HSDPA.H2D.Att
VS.HSDPA.H2D.Att provides the number of

channel conversion attempts from the HSDSCH 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 HSDSCH to the FACH in a cell.
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.
Issue 03 (2015-06-30)

1712
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.H2D.Att
WRFD-01061111
VS.HSDPA.D2H.Att
WRFD-01061111
VS.HSDPA.F2H.Att
WRFD-01061111
VS.HSDPA.H2F.Att
WRFD-01061111
Number of HSDPA Serving Cell Change Attempts for Cell

Counters
Counter ID
Counter Name
Counter Description
67190698
VS.HSDPA.SHO.ServCellC
hg.AttOut
Number of Intra-RNC
HSDPA Serving Cell Change
Attempts for Cell
67195481
hg.AttOutIur
Number of Inter-RNC
Attempts for Cell
73423900
VS.HSDPA.SHO.IubBased
ServCellChg.AttOut
Number of Serving Cell

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. The preceding
counters comply with section "8.3.4 Active set update","8.2.2 Reconfiguration procedures" in
3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

1713
BSC6900 UMTS
Counter Name
Description
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
Out
VS.HSDPA.SHO.IubBasedServCellChg.Att
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.
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-736 HSDPA Serving cell change procedure (successful operation)
Issue 03 (2015-06-30)

1714
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
hg.AttOut
WRFD-01061006
HSDPA Mobility
Management
hg.AttOutIur
WRFD-01061006
HSDPA Mobility
Management
Number of Successful HSDPA Serving Cell Changes for Cell

Counters
Counter ID
Counter Name
Counter Description
67190699
hg.SuccOut
Number of Intra-RNC
Success in RNC for Cell
67195482
hg.SuccOutIur
Number of Inter-RNC
Success for Cell
73423901
VS.HSDPA.SHO.IubBased
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
with the primary carrier.The preceding counters comply with section "8.3.4 Active set
update","8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

1715
BSC6900 UMTS
Counter Name
Description
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
ccOut
VS.HSDPA.SHO.IubBasedServCellChg.Su
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,
(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.
Issue 03 (2015-06-30)

1716
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
hg.SuccOut
WRFD-01061006
HSDPA Mobility
Management
hg.SuccOutIur
WRFD-01061006
HSDPA Mobility
Management
Number of Inter-RNC HSDPA Hard Handover Attempts Without Channel Change

for Cell
Counters
Counter ID
Counter Name
Counter Description
67195483
VS.HSDPA.HHO.H2H.AttOutIur
Number of Inter-RNC
HSDPA Hard Handover
Attempts Without Channel
Change for Cell
67190700
VS.HSDPA.HHO.H2H.AttOutIntraFreq
HSDPA Hard Handover
Change for Cell
67190702
VS.HSDPA.HHO.H2H.AttOutInterFreq
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
only in the cell with the primary carrier.The preceding counters comply with section"8.3.4 Active
set update","8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

1717
BSC6900 UMTS
Counter Name
Description
VS.HSDPA.HHO.H2H.AttOutIur provides
the number of inter-RNC HSDPA hard
handover attempts without channel change in
the serving cell.
provides the number of intra-frequency
HSDPA hard handover attempts without
channel change in a cell.
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,
(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.
Issue 03 (2015-06-30)

1718
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061006
HSDPA Mobility
Management
Number of Successful Inter-RNC HSDPA Hard Handovers Without Channel

Change for Cell
Counters
Counter ID
Counter Name
Counter Description
67195484
VS.HSDPA.HHO.H2H.SuccOutIur
Number of Successful InterRNC HSDPA Hard

Handovers Without Channel
Change for Cell
67190701
VS.HSDPA.HHO.H2H.SuccOutIntraFreq
Number of Successful IntraFrequency 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
only in the cell with the primary carrier.The preceding complies with section "8.3.4 Active set
update","8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

1719
BSC6900 UMTS
Counter Name
Description
VS .HSDPA.HHO.H2H.SuccOutIur
provides the number of successful inter-RNC
channel change in the serving cell.
provides the number of successful intrafrequency 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,
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.
Issue 03 (2015-06-30)

1720
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061006
HSDPA Mobility
Management
Number of Successful Inter-Frequency HSDPA Hard Handovers Without Channel

Change for Cell
Counters
Counter ID
Counter Name
Counter Description
67190703
VS.HSDPA.HHO.H2H.SuccOutInterFreq
Number of Successful InterFrequency 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.
Issue 03 (2015-06-30)

1721
BSC6900 UMTS
Measurement point
The measurement is triggered at point B as shown in the figure, the procedure shown in the
figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an exampl, when
receiving from a UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message,the RNC measures this item in best the cell from which the UE is handed over if an
inter-frequency HSDPA hard handover without channel change is performed.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSDPA.HHO.H2H.SuccOutInterFreq
WRFD-01061006
HSDPA Mobility
Management

1722
BSC6900 UMTS
Number of HSDPA RAB Establishment Attempts for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190704
Number of HSDPA RAB

Cell
67195507
BE.Golden
Number of HSDPA RAB

Establishment Attempts of
BE Service for Golden Level
User for Cell
67195508
BE.Silver
Number of HSDPA RAB

BE Service for Silver Level
User for Cell
67195509
BE.Copper
Number of HSDPA RAB

BE Service for Copper Level
User for Cell
73403817
VS.HSDPA.RAB.
64QAM.AttEstab
Number of HSDPA 64QAM

RAB Setup Requests for cell
73403821
VS.HSDPA.RAB.MIMO.At
tEstab
Number of HSDPA MIMO

RABs Setup Request for Cell
73403824
VS.HSDPA.RAB.MIMO64
QAM.AttEstab

+64QAM RABs Setup
Request for cell
73403828
VS.HSDPA.RAB.DC.AttEstab
Number of DC-HSDPA
RAB Setup Requests in the
primary carrier of DCHSDPA counted for cell
73423378
VS.HSDPA.RAB.DCMIM
O.AttEstab
Number of DC-HSDPA
+MIMO RAB Setup
Requests in the Primary
Carrier of DC-HSDPA for
Cell
73426094
VS.HSDPA.RAB.
3CMIMO.AttEstab
Number of RAB Setup

Attempts for Cell When 3CHSDPA with MIMO Applied
73426098
VS.HSDPA.RAB.
3C.AttEstab
Number of RAB Setup

Attempts for Cell When 3CHSDPA Applied

1723
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426102
VS.HSDPA.RAB.
4CMIMO.AttEstab
Number of RAB Setup

Attempts for Cell Where 4CHSDPA with MIMO Applied
73426106
VS.HSDPA.RAB.DBMIM
O.AttEstab
Number of RAB Setup

Attempts for Cell When DBHSDPA with MIMO Applied
73426110
VS.HSDPA.RAB.
4C.AttEstab
Number of RAB Setup

Attempts for Cell When 4CHSDPA Applied
73426114
VS.HSDPA.RAB.DB.AttEstab
Number of RAB Setup

Attempts for Cell When DBHSDPA 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.The preceding counters complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the following figure. When the RNC
receives a RAB ASSIGNMENT REQUEST message from the CN for setting up HSDPA
services, the RNC measures the measurement items by the priority level or used technology in
the serving cell.
Issue 03 (2015-06-30)

1724
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-010630

HSDPA
Issue 03 (2015-06-30)
BE.Golden
WRFD-01061008

BE.Silver
WRFD-01061008

BE.Copper
WRFD-01061008


1725
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HSDPA.RAB.
64QAM.AttEstab
WRFD-010683
Downlink 64QAM
VS.HSDPA.RAB.MIMO.At
tEstab
WRFD-010684
2 x 2 MIMO
VS.HSDPA.RAB.MIMO64
QAM.AttEstab
WRFD-010693
DL 64QAM+MIMO
VS.HSDPA.RAB.DC.AttEstab
WRFD-010696
DC-HSDPA
VS.HSDPA.RAB.DCMIM
O.AttEstab
WRFD-010699
DC-HSDPA+MIMO
VS.HSDPA.RAB.
3CMIMO.AttEstab
WRFD-150223
MC-HSDPA+MIMO
VS.HSDPA.RAB.
3C.AttEstab
WRFD-150250
3C-HSDPA
VS.HSDPA.RAB.
4CMIMO.AttEstab
WRFD-150223
MC-HSDPA+MIMO
VS.HSDPA.RAB.DBMIM
O.AttEstab
WRFD-150227
DB-HSDPA+MIMO
VS.HSDPA.RAB.
4C.AttEstab
WRFD-150207
4C-HSDPA
VS.HSDPA.RAB.DB.AttEstab
WRFD-150209
DB-HSDPA
Number of Successful HSDPA RAB Establishments for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190705
HSDPA RAB
67195510
.BE.Golden
HSDPA RAB
Establishments of BE
Service for Golden Level
User for Cell

1726
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67195511
.BE.Silver
HSDPA RAB
Service for Silver Level User
for Cell
67195512
.BE.Copper
HSDPA RAB
Service for Copper Level
User for Cell
73403818
VS.HSDPA.RAB.
64QAM.SuccEstab

RABs Setup Successfully for
cell
73403822
VS.HSDPA.RAB.MIMO.Su
ccEstab

RABs Setup Successfully for
cell
73403825
VS.HSDPA.RAB.MIMO64
QAM.SuccEstab

+64QAM RABs Setup
73403829
VS.HSDPA.RAB.DC.SuccEstab
Number of DC-HSDPA
RABs Setup Successfully in
the primary carrier of DCHSDPA counted for cell
73423379
VS.HSDPA.RAB.DCMIM
O.SuccEstab
Number of Successful DCHSDPA+MIMO RAB

Setups in the Primary Carrier
of DC-HSDPA for cell
73426095
VS.HSDPA.RAB.
3CMIMO.SuccEstab

Setups for Cell When 3CHSDPA with MIMO Applied
73426099
VS.HSDPA.RAB.
3C.SuccEstab

Setups for Cell When 3CHSDPA Applied
73426103
VS.HSDPA.RAB.
4CMIMO.SuccEstab

Setups for Cell When 4CHSDPA with MIMO Applied
73426107
VS.HSDPA.RAB.DBMIM
O.SuccEstab

Setups for Cell When DBHSDPA with MIMO Applied

1727
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426111
VS.HSDPA.RAB.
4C.SuccEstab

Setups for Cell When 4CHSDPA Applied
73426115
VS.HSDPA.RAB.DB.SuccEstab

Setups for Cell When DBHSDPA 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.The preceding counters complies with section "8.2 RAB
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.
Issue 03 (2015-06-30)

1728
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-010630

HSDPA
Issue 03 (2015-06-30)
.BE.Golden
WRFD-01061008

.BE.Silver
WRFD-01061008

.BE.Copper
WRFD-01061008

VS.HSDPA.RAB.
64QAM.SuccEstab
WRFD-010683
Downlink 64QAM
VS.HSDPA.RAB.MIMO.Su
ccEstab
WRFD-010684
2 x 2 MIMO
VS.HSDPA.RAB.MIMO64
QAM.SuccEstab
WRFD-010693
DL 64QAM+MIMO
VS.HSDPA.RAB.DC.SuccEstab
WRFD-010696
DC-HSDPA
VS.HSDPA.RAB.DCMIM
O.SuccEstab
WRFD-010699
DC-HSDPA+MIMO
VS.HSDPA.RAB.
3CMIMO.SuccEstab
WRFD-150223
MC-HSDPA+MIMO
VS.HSDPA.RAB.
3C.SuccEstab
WRFD-150250
3C-HSDPA
VS.HSDPA.RAB.
4CMIMO.SuccEstab
WRFD-150223
MC-HSDPA+MIMO
VS.HSDPA.RAB.DBMIM
O.SuccEstab
WRFD-150227
DB-HSDPA+MIMO

1729
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HSDPA.RAB.
4C.SuccEstab
WRFD-150207
4C-HSDPA
VS.HSDPA.RAB.DB.SuccEstab
WRFD-150209
DB-HSDPA
Number of HSDPA RABs Abnormal Released for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67191162
VS.HSDPA.RAB.AbnormRel

Abnormal Released for Cell
67191163
VS.HSDPA.RAB.AbnormR
el.RF

Abnormal Released Due to
RF Cause for Cell
73403819
VS.HSDPA.RAB.AbnormRel.64QAM

RABs Abnormal Released
for cell
73403826
el.MIMO64QAM

+64QAM RABs Abnormal
Released for cell
73403830
el.DC
Number of DC-HSDPA
RABs Abnormal Released in
the primary carrier of DC
counted for Cell(including
RF Cause)
73403832
el.MIMO

for cell(Including RF Cause)
73423381
VS.HSDPA.RAB.DCMIM
O.AbnormRel
Number of Abnormal DCHSDPA+MIMO RAB

Releases in the Primary
cell
73426096
VS.HSDPA.RAB.AbnormRel.3CMIMO
Released RABs for Cell
When 3C-HSDPA with
MIMO Applied (RF
Exceptions Considered)

1730
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426100
VS.HSDPA.RAB.AbnormRel.3C
When 3C-HSDPA Applied
(RF Exceptions Considered)
73426104
When 4C-HSDPA with
MIMO Applied (RF
73426112
Number of Abnormal
73426116
el.DB
When DB-HSDPA Applied
73426317
el.SRBoH
Released RABs of SRB over
HSDPA Users for Cell
Description
These counters provide the number of times RABs are abnormally released when different
technologies such as 64QAM, MIMO, and DC are used due to different factors including the
RF failures in a serving cell.
For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier.
Note: Unless otherwise specified, SRB over HSDPA users are in the CELL_DCH state, and
their SRBs are carried on the HSDPA channel.The preceding counters complies with section
"8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.HSDPA.RAB.AbnormRel provides the

number of abnormal HSDPA RAB releases
in a cell.

1731
BSC6900 UMTS
Counter Name
Description
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.
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.
Issue 03 (2015-06-30)

1732
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","UE Generated
Signalling Connection Release", "Successful Relocation", and "Network Optimization". For
details, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

1733
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-010630

HSDPA
el.RF
WRFD-01061008
WRFD-010630

HSDPA
Issue 03 (2015-06-30)
VS.HSDPA.RAB.AbnormRel.64QAM
WRFD-010683
Downlink 64QAM
el.MIMO64QAM
WRFD-010693
DL 64QAM+MIMO

1734
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
el.DC
WRFD-010696
DC-HSDPA
el.MIMO
WRFD-010684
2 x 2 MIMO
VS.HSDPA.RAB.DCMIM
O.AbnormRel
WRFD-010699
DC-HSDPA+MIMO
WRFD-150223
MC-HSDPA+MIMO
WRFD-150250
3C-HSDPA
WRFD-150223
MC-HSDPA+MIMO
WRFD-150207
4C-HSDPA
el.DB
WRFD-150209
DB-HSDPA
el.SRBoH
WRFD-010652
SRB over HSDPA
Number of HSDPA RABs Normal Released for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67191164
VS.HSDPA.RAB.NormRel

Normal Released for Cell
67191161
VS.HSDPA.RAB.NormRel.
UsrInact
Number of HSDPA RAB

Releases Due to User
Inactivity for Cell
73403820
64QAM

RABs Normal Released for
Cell
73403823
MIMO

cell
73403827
MIMO64QAM

+64QAM RABs Normal
Released for cell

1735
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73403831
DC
Number of DC-HSDPA
RABs Normal Released in
the primary carrier of DC
counted for Cell
73423380
VS.HSDPA.RAB.DCMIM
O.NormRel
Number of Normal DCHSDPA+MIMO RAB

Releases in the Primary
cell
73426097
3CMIMO
Number of Normally
When 3C-HSDPA with
MIMO Applied
73426101
3C
Number of Normally
73426105
4CMIMO
Number of Normally
When 4C-HSDPA with
MIMO Applied
73426109
DBMIMO
Number of Normally
When DB-HSDPA with
MIMO Applied
73426113
4C
Number of Normally
73426117
DB
Number of Normally
When DB-HSDPA Applied
Description
technologies such as 64QAM, MIMO, and DC are used in a serving cell.
carrier.The preceding counters complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
Issue 03 (2015-06-30)

1736
BSC6900 UMTS
Counter Name
Description
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
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", "UE Generated Signalling
Connection Release", "Normal Release", "Successful Relocation", and "Network Optimization".
For details, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

1737
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-010630

HSDPA
UsrInact
WRFD-01061008
WRFD-010630

HSDPA
Issue 03 (2015-06-30)
64QAM
WRFD-010683
Downlink 64QAM
MIMO
WRFD-010684
2 x 2 MIMO

1738
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
MIMO64QAM
WRFD-010693
DL 64QAM+MIMO
DC
WRFD-010696
DC-HSDPA
VS.HSDPA.RAB.DCMIM
O.NormRel
WRFD-010699
DC-HSDPA+MIMO
3CMIMO
WRFD-150223
MC-HSDPA+MIMO
3C
WRFD-150250
3C-HSDPA
4CMIMO
WRFD-150223
MC-HSDPA+MIMO
DBMIMO
WRFD-150227
DB-HSDPA+MIMO
4C
WRFD-150207
4C-HSDPA
DB
WRFD-150209
DB-HSDPA
Number of Inter-RNC HSDPA Hard Handover Attempts for Cell(HSDPA to DCH)

Counters
Counter ID
Counter Name
Counter Description
73403764
VS.HSDPA.HHO.H2D.AttOutIur
number of Inter-RNC H2D

Hard Handover Attempts for
Cell
67191157
VS.HSDPA.HHO.H2D.AttOutIntraFreq
H2D Hard Handover
Attempts for Cell
67191159
VS.HSDPA.HHO.H2D.AttOutInterFreq
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
Issue 03 (2015-06-30)

1739
BSC6900 UMTS
measured only in the cell with the primary carrier.The preceding counters complies with section
Counter Name
Description
VS.HSDPA.HHO.H2D.AttOutIur provides
the number of inter-RNC hard handover from
HSDPA to DCH attempts in the serving cell.
provides the number of intra-frequency hard
handover from HSDPA to DCH attempts in a
cell.
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.
Issue 03 (2015-06-30)

1740
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061006
HSDPA Mobility
Management
Number of Successful inter-RNC HSDPA Hard Handovers for Cell(HSDPA to

DCH)
Counters
Counter ID
Counter Name
Counter Description
73403765
VS.HSDPA.HHO.H2D.SuccOutIur
Number of Successful InterRNC H2D Hard Handovers

for Cell
67191158
VS.HSDPA.HHO.H2D.SuccOutIntraFreq
Number of Successful IntraFrequency H2D Hard

Handovers for Cell
67191160
VS.HSDPA.HHO.H2D.SuccOutInterFreq
Number of Successful InterFrequency 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.
carrier.The preceding counters complies with section "8.2.2 Reconfiguration procedures" in
3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

1741
BSC6900 UMTS

Counter Name
Description
VS.HSDPA.HHO.H2D.SuccOutIur provides
the number of successful inter-RNC hard
handovers from HSDPA to DCH in a cell.
provides the number of successful intrafrequency hard handovers from HSDPA to
DCH in a cell.
provides the number of successful interfrequency 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:
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.
Issue 03 (2015-06-30)

1742
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061006
HSDPA Mobility
Management
WRFD-01061006
HSDPA Mobility
Management
Number of HSDPA UEs with Various Categories in a Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204259
VS.HSDPA.UE.Mean.CAT
1.6

UEs with Category 1-6 in a
Cell
67193578
VS.HSDPA.UE.Max.CAT1.
6
Maximum Number of
HSDPA UEs with Category
1-6 in a Cell
67204260
7.10

Cell
67193581
10
Maximum Number of
7-10 in a Cell
67204261
11.12

UEs with Category 11-12 in
a Cell
67193584
VS.HSDPA.UE.Max.CAT1
1.12
Maximum Number of
11-12 in a Cell

1743
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204262
13.14

a Cell
67193587
3.14
Maximum Number of
13-14 in a Cell
67204263
15.16

a Cell
67193590
5.16
Maximum Number of
15-16 in a Cell
67204264
17.20

a Cell
67193593
7.20
Maximum Number of
17-20 in a Cell
67204265
21.24

a Cell
67193596
1.24
Maximum Number of
21-24 in a Cell
73423377
5.28
Maximum Number of
25-28 in a Cell
73441138
25.28

a Cell
73426132
29
Average number of Category

29 HSDPA users in a cell
73426133
9
Maximum number of
Category 29 HSDPA users in
a cell
73426136
30

73426137
0
Maximum number of
a cell

1744
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426140
31

73426141
1
Maximum number of
a cell
73426144
32

73426145
2
Maximum number of
a cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193583
11.12.DENO

a Cell(Denominator)
67193582
11.12.NUM

a Cell(Numerator)
67193586
13.14.DENO

a Cell(Denominator)
67193585
13.14.NUM

a Cell(Numerator)
67193589
15.16.DENO

a Cell(Denominator)
67193588
15.16.NUM

a Cell(Numerator)
67193592
17.20.DENO

a Cell(Denominator)
67193591
17.20.NUM

a Cell(Numerator)

1745
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67193577
1.6.DENO
Average num of CAT1-6

HSDPA UEs (Denominator)
67193576
1.6.NUM

Cell(Numerator)
67193595
21.24.DENO

a Cell(Denominator)
67193594
21.24.NUM

a Cell(Numerator)
73423376
25.28.DENO

a Cell(Denominator)
73423375
25.28.NUM

a Cell(Numerator)
67193580
7.10.DENO

Cell(Denominator)
67193579
7.10.NUM

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.
Issue 03 (2015-06-30)

1746
BSC6900 UMTS
Formula
VS.HSDPA.UE.Mean.CAT1.6 = [VS.HSDPA.UE.Mean.CAT1.6.NUM]/
[VS.HSDPA.UE.Mean.CAT1.6.DENO]
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
1.6
WRFD-01061002
HSDPA UE Category 1 to 28
6
WRFD-01061002
7.10
WRFD-01061002
10
WRFD-01061002
11.12
WRFD-01061002
1.12
WRFD-01061002
13.14
WRFD-01061002

1747
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
3.14
WRFD-01061002
15.16
WRFD-01061002
5.16
WRFD-01061002
17.20
WRFD-01061002
7.20
WRFD-01061002
21.24
WRFD-01061002
1.24
WRFD-01061002
5.28
WRFD-010699
DC-HSDPA+MIMO
25.28
WRFD-010699
DC-HSDPA+MIMO
29
WRFD-150250
3C-HSDPA
9
WRFD-150250
3C-HSDPA
30
WRFD-150223
MC-HSDPA+MIMO
0
WRFD-150223
MC-HSDPA+MIMO
31
WRFD-150207
4C-HSDPA
1
WRFD-150207
4C-HSDPA
32
WRFD-150223
MC-HSDPA+MIMO
2
WRFD-150223
MC-HSDPA+MIMO

1748
BSC6900 UMTS
Number of HSDPA MAC-d Flow Establishment Requests for Cell

Counters
Counter ID
Counter Name
Counter Description
73393828
VS.HSDPA.MACD.AttSetup
Number of HSDPA MAC-d

Flow Establishment
Requests for Cell
Description
This counter provides the number of HSDPA MAC-d flow establishment requests in the cell.For
DC-HSDPA users, this counter is measured only in the cell with the primary carrier.This counter
complies with section "8.2.17 Radio Link Setup","8.3.1 Radio Link Addition","8.3.2
Synchronised Radio Link Reconfiguration Preparation" in 3GPP TS 25.433 (v10.10.0).
Measurement point
The measurement can be triggered at point A as shown in the figure. When the RNC sends the
NodeB a RADIO LINK SETUP REQUEST message, this counter is measured in the HSDPA
serving cell if the message contains the "HSDSCH FDD Information" IE.
The measurement can also be triggered at point A as shown in the figure. When the RNC sends
the NodeB a RADIO LINK RECONFIGURATION PREPARE message, this counter is
measured in the HSDPA serving cell if the message contains the "HSDSCH FDD Information"
or "HS-DSCH MAC-d Flows To Add" IE.
Issue 03 (2015-06-30)

1749
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.MACD.AttSetup
WRFD-010610
HSDPA Introduction
Package
Number of Failed HSDPA Service Establishments Due to Insufficiency of

Different Resources
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393830
VS.HSDPA.RAB.FailEstab.
DLPower.Cong
Number of Failed HSDPA

to DL Power Insufficiency
for Cell

1750
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73393831
DLIUBBand.Cong
Number of Failed HSDPA

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.The preceding counters
complies with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
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 HSDPA serving cell when
the RAB is for a HSDPA service and the resource request fails.
Figure 1-752 Failed RAB establishments due to resource insufficiency
Issue 03 (2015-06-30)

1751
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
DLPower.Cong
WRFD-01061003
DLIUBBand.Cong
WRFD-01061003
Counter ID
Counter Name
Counter Description
73410492
VS.HSDPA.MIMO.UE.Mea
n.Cell

UEs in a Cell
Number of MIMO UEs in a Cell

Counters
specific formulas.
Counter ID
Counter Name
Counter Description
73393977
n.Cell.DENO

UEs in a Cell(Denominator)
73393976
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
Issue 03 (2015-06-30)

1752
BSC6900 UMTS
data in the period by the number of samples, the average number of MIMO UEs in the
measurement period is obtained.
Formula
VS.HSDPA.MIMO.UE.Mean.Cell = [VS.HSDPA.MIMO.UE.Mean.Cell.NUM]/
[VS.HSDPA.MIMO.UE.Mean.Cell.DENO]
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
n.Cell
WRFD-010684
2 x 2 MIMO
Number of Outgoing DRD Attempts for HSDPA Users Through Intelligent User
Counters
Counter ID
Counter Name
Counter Description
73421686
VS.HSDPA.DRD.AttOut.Int
elligence
Number of Outgoing DRD

Attempts for HSDPA Users
Through Intelligent User
73421688
VS.HSDPA.DRD.AttIn.Intelligence
Number of Incoming DRD

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
users, this counter is measured only in the cell with the primary carrier. The preceding counters
Issue 03 (2015-06-30)

1753
BSC6900 UMTS
Counter Name
Description
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.
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
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-753 The DRD Process triggered by Intelligent User Recognition
Issue 03 (2015-06-30)

1754
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.DRD.AttOut.Int
elligence
WRFD-01061004
HSDPA Power Control
WRFD-01061004
HSDPA Power Control
Number of Successful Outgoing DRDs for HSDPA Users Through Intelligent User
Counters
Counter ID
Counter Name
Counter Description
73421687
VS.HSDPA.DRD.SuccOut.I
ntelligence
Outgoing DRDs for HSDPA
Users Through Intelligent
User Recognition for Cell
73421689
VS.HSDPA.DRD.SuccIn.Int
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
users, this counter is measured only in the cell with the primary carrier. The preceding counters
Issue 03 (2015-06-30)

1755
BSC6900 UMTS
Counter Name
Description
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
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-754 The DRD Process triggered by Intelligent User Recognition
Issue 03 (2015-06-30)

1756
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.DRD.SuccOut.I
ntelligence
WRFD-01061004
HSDPA Power Control
VS.HSDPA.DRD.SuccIn.Int
elligence
WRFD-01061004
HSDPA Power Control
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73422167
el.H2P
Number of RABs
HSDPA Services during the
State Transition from
CELL_DCH to CELL_PCH
or URA_PCH for Cell
73425928
el.DC2P

Releases for Cell During
State Transition of DCHSDPA UEs to CELL/
URA_PCH
73425929
VS.HSDPA.RAB.AbnormRel.64QAM2P

State Transition of HSDPA
+64QAM UEs to CELL/
URA_PCH
73425930
el.MIMO2P

State Transition of MIMO
UEs to CELL/URA_PCH

1757
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425931
el.DCMIMO2P

State Transition of DCHSDPA+MIMO UEs to
CELL/URA_PCH
73425932
el.MIMO64QAM2P

State Transition of MIMO
+64QAM UEs to CELL/
URA_PCH
73425933
VS.HSDPA.RAB.AbnormRel.3C2P

State Transition of 3CHSDPA UEs to CELL/
URA_PCH
73425934
VS.HSDPA.RAB.AbnormRel.3CMIMO2P

State Transition of 3CHSDPA+MIMO UEs to
CELL/URA_PCH
73425935

State Transition of 4CHSDPA UEs to CELL/
URA_PCH
73425936

State Transition of 4CHSDPA+MIMO UEs to
CELL/URA_PCH
73425937
el.DB2P

State Transition of DBHSDPA UEs to CELL/
URA_PCH
73425938
el.DBMIMO2P

State Transition of DBHSDPA+MIMO UEs to
CELL/URA_PCH

1758
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426316
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. The preceding
counters comply with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v9.5.1) and "8.2.2
Measurement point
As shown in point A of the following figure. When the UE fails to transit to CELL_PCH or
URA_PCH, the RNC sends the CN a RAB RELEASE REQUEST message. If the RNC receives
from the CN a RAB ASSIGNMENT REQUEST message which contains a cause value of
abnormal release, the counters related to abnormal release when different technologies are used
are measured.
Issue 03 (2015-06-30)

1759
BSC6900 UMTS
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.
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","UE
Generated Signalling Connection Release", "Successful Relocation", and "Network
Optimization". For details, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

1760
BSC6900 UMTS
Figure 1-757 IU release procedure triggered by the RNC
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.H2P
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-010610
HSDPA Introduction
Package
Issue 03 (2015-06-30)
el.DC2P
WRFD-010696
DC-HSDPA
VS.HSDPA.RAB.AbnormRel.64QAM2P
WRFD-010683
Downlink 64QAM
el.MIMO2P
WRFD-010684
2 x 2 MIMO

1761
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
el.DCMIMO2P
WRFD-010699
DC-HSDPA+MIMO
el.MIMO64QAM2P
WRFD-010693
DL 64QAM+MIMO
WRFD-150250
3C-HSDPA
WRFD-150223
MC-HSDPA+MIMO
WRFD-150207
4C-HSDPA
WRFD-150223
MC-HSDPA+MIMO
el.DB2P
WRFD-150209
DB-HSDPA
el.DBMIMO2P
WRFD-150227
DB-HSDPA+MIMO
el.SRBoH.H2P
WRFD-010652
SRB over HSDPA
Average Throughput on HSDPA MAC-d Flow for Cell (Excluding the Data of LowTraffic Users)
Counters
Counter ID
Counter Name
Counter Description
73441141
VS.HSDPA.MeanChThroup
ut.HighLoad
Mean Throughput on
HSDPA MAC-d Flow for
Cell (Excluding the Data of
Low-Traffic Users)
specific formulas.
Issue 03 (2015-06-30)

1762
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73423463
VS.HSDPA.Times.HighLoad
Duration of Data Sending on

HSDPA MAC-d flow for
Cell (Excluding the Duration
of Data Sending by LowTraffic Users)
Description
This counter provides the mean downlink throughput on HSDPA Single MAC-d flow in a cell.
It excludes the data sent by low-traffic users.For DC-HSDPA users, this counter is measured
only in the primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
The amount of data that is sent in downlink on HSDPA MAC-d flow at the RLC layer (excluding
the retransmitted RLC data and RLC headers) is measured every second in the serving cell.
The amount of data that is measured in one second is considered as valid only when the amount
of data received on the Iu interface within that second is greater than or equal to 80 KB and the
amount of data in the RLC buffer within that second is greater than or equal to 80 KB.
At the end of the measurement period, the mean throughput on HSDPA MAC-d flow is
calculated by dividing the total amount of data that is considered as valid by the total period of
valid time. Note that the total amount of data excludes the data sent by low-traffic users.
Formula
VS.HSDPA.MeanChThrouput.HighLoad = {8}*[VS.HSDPA.Traffic.HighLoad]/
[VS.HSDPA.Times.HighLoad]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.MeanChThroup
ut.HighLoad
WRFD-010610
HSDPA Introduction
Package
WRFD-01061008

Issue 03 (2015-06-30)

1763
BSC6900 UMTS
Number of Bytes Sent on HSDPA MAC-d Flow for Cell (Excluding the Bytes of
Low-Traffic Users)
Counters
Counter ID
Counter Name
Counter Description
73423462
VS.HSDPA.Traffic.HighLoad
Number of Bytes Sent on

HSDPA MAC-d Flow for
Cell (Excluding the Bytes of
Low-Traffic Users)
Description
This counter provides the number of bytes that are sent in downlink on HSDPA MAC-d flow
in a cell. It excludes the number of bytes that are sent by low-traffic users.For DC-HSDPA users,
this counter is measured only in the primary cell based on the total number of bytes sent on the
primary and secondary carriers.
Measurement point
The number of bytes that are sent in downlink on HSDPA MAC-d flow at the RLC layer
(excluding the retransmitted RLC data and RLC headers) is measured every second in the serving
cell.
The number of bytes that is measured in one second is calculated into the counter only when the
amount of data received on the Iu interface within that second is greater than or equal to 80 KB
and the amount of data in the RLC buffer within that second is greater than or equal to 80 KB.
At the end of the measurement period, the number of bytes that can be calculated into the counter
is accumulated. Note that the total number of bytes excludes the number of bytes sent by lowtraffic users at the RLC layer.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.Traffic.HighLoad
WRFD-010610
HSDPA Introduction
Package
WRFD-01061008

Issue 03 (2015-06-30)

1764
BSC6900 UMTS
Number of Normal RAB Releases of HSDPA UEs for Cell (All Scenarios)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425939
DC.All
Number of Normal RAB

Releases of DC-HSDPA UEs
for Cell (All Scenarios)
73425940
64QAM.All

Releases of HSDPA
+64QAM UEs for Cell (All
Scenarios)
73425941
MIMO.All

Releases of HSDPA+MIMO
UEs for Cell (All Scenarios)
73425942
DCMIMO.All

Releases of DC-HSDPA
+MIMO UEs for Cell (All
Scenarios)
73425943
MIMO64QAM.All

Releases of HSDPA MIMO
Scenarios)
73425944
3C.All

Releases of 3C-HSDPA UEs
73425945
3CMIMO.All

Releases of 3C-HSDPA
Scenarios)
73425946
4C.All

Releases of 4C-HSDPA UEs
73425947
4CMIMO.All

Releases of 4C-HSDPA
Scenarios)
73425948
DB.All

Releases of DB-HSDPA UEs

1765
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73425949
DBMIMO.All

Releases of DB-HSDPA
Scenarios)
73426318
SRBoH.All
Number of Normally
Released RABs of SRB over
HSDPA Users for Cell (All
Scenarios)
Description
These counters provide the number of normal RAB releases in a cell where HSDPA is applied.
For multi-carrier HSDPA UEs, these counters are measured only in the primary carrier cell.
Note: The normal RAB releases on HSDPA channels include the RAB releases over the Iu
interface and switchovers 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 (including intra- and inter-frequency
handovers).
Note: Unless otherwise specified, SRB over HSDPA users are in the CELL_DCH state, and
their SRBs are carried on the HSDPA channel.
The preceding counters comply with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v9.5.1).
Measurement point
As shown by point A in figure 1 (HSDPA UEs enter idle mode), after receiving an IU RELEASE
COMMAND message from the CN, the RNC releases the corresponding RAB and then sends
an IU RELEASE COMPLETE message to the CN. This counter is increased by one in the serving
cell where the UE camps when either of the following condition is met: The cause value in the
IU RELEASE COMMAND message is "User Inactivity", "Normal Release", "Successful
Relocation", or "Network Optimization." Alternatively, the RNC has initiated a release request
with the cause value "User Inactivity", "Network Optimization", or "UE Generated Signalling
Connection Release" before receiving the IU RELEASE COMMAND message.
Issue 03 (2015-06-30)

1766
BSC6900 UMTS
As shown by point B in figure 2 (HSDPA UEs enter idle mode), 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
Issue 03 (2015-06-30)

1767
BSC6900 UMTS
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.
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
Issue 03 (2015-06-30)

1768
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
DC.All
WRFD-010696
DC-HSDPA
64QAM.All
WRFD-010683
Downlink 64QAM
MIMO.All
WRFD-010684
2 x 2 MIMO
DCMIMO.All
WRFD-010699
DC-HSDPA+MIMO
MIMO64QAM.All
WRFD-010693
DL 64QAM+MIMO
3C.All
WRFD-150250
3C-HSDPA
3CMIMO.All
WRFD-150223
MC-HSDPA+MIMO
4C.All
WRFD-150207
4C-HSDPA
4CMIMO.All
WRFD-150223
MC-HSDPA+MIMO
DB.All
WRFD-150209
DB-HSDPA
DBMIMO.All
WRFD-150227
DB-HSDPA+MIMO
SRBoH.All
WRFD-010652
SRB over HSDPA
Number of Abnormal Released RABs for Cell When DB-HSDPA with MIMO
Applied (RF Exceptions Considered)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426108
el.DBMIMO
Number of Abnormal
When DB-HSDPA with
MIMO Applied (RF

1769
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. This counter complies with section "8.2 RAB Assignment" in 3GPP
TS 25.413 (v9.5.1).
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", "UE Generated Signalling Connection 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", "UE
Generated Signalling Connection 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.
Issue 03 (2015-06-30)

1770
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", "UE
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.
Issue 03 (2015-06-30)

1771
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
el.DBMIMO
WRFD-150227
DB-HSDPA+MIMO

1772
BSC6900 UMTS
Number of Times RAB Is Abnormally Released for HSDPA UEs During State
Transitions from CELL_DCH to CELL_FACH
Counters
Counter ID
Counter Name
Counter Description
73426883
el.H2F
Number of Times RAB Is

HSDPA UEs During State
Transitions from
CELL_DCH to
CELL_FACH
Description
This counter measures the number of times the RABs of HSDPA UEs are abnormally released
when HSDPA UEs are transitioning from the CELL_DCH state to the CELL_FACH state. This
counter is measured in the best cell. This counter complies with section "8 RANAP Procedures"
in 3GPP TS 25.413 (v9.5.1).
Measurement point
The measurement is triggered at point A, as shown in Figure 1. An exception, for example, SRB
reset occurs in the RB reconfiguration procedure (for the channel switchover from HS-DSCH
to FACH), and so the RNC sends a RAB RELEASE REQUEST message to the CN. The CN
responds with a RAB ASSIGNMENT REQUEST message. If the RAB ASSIGNMENT
REQUEST message carries a cause value other than "User Inactivity", "Normal Release", "UE
Optimization" and the PS service of the HSDPA UE is released, this counter is measured in the
best cell of the HSDPA UE. For details about the cause values indicating an abnormal release,
see 3GPP TS 25.413.
Issue 03 (2015-06-30)

1773
BSC6900 UMTS
to FACH), and so the RNC sends a RAB RELEASE REQUEST message to the CN. The CN
responds with an IU RELEASE COMMAND message. If the IU RELEASE COMMAND
message carries a cause value other than "User Inactivity", "Normal Release", "UE Generated
Signalling Connection Release", "Successful Relocation", or "Network Optimization" and the
PS service of the HSDPA UE is released, this counter is measured in the best cell of the HSDPA
UE. For details about the cause values indicating an abnormal release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

1774
BSC6900 UMTS
Figure 1-766 Iu connection release caused by RAB release
to FACH), and so the RNC sends an IU RELEASE REQUEST message to the CN. The CN
responds with an IU RELEASE COMMAND message. If the U RELEASE COMMAND
message carries a cause value other than "User Inactivity", "Normal Release", "UE Generated
Signalling Connection Release", "Successful Relocation", or "Network Optimization" and the
PS service of the HSDPA UE is released, this counter is measured in the best cell of the HSDPA
UE. For details about the cause values indicating an abnormal release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

1775
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.H2F
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010503
WRFD-010504

Issue 03 (2015-06-30)

1776
BSC6900 UMTS
Number of Times PS Service Is Abnormally Released for HSDPA UEs in

CELL_DCH State Due to Cell Update Failures
Counters
Counter ID
Counter Name
Counter Description
73426884
el.CellDCH.CellUpdt
Number of Times PS Service

Is Abnormally Released for
HSDPA UEs in CELL_DCH
State Due to Cell Update
Failures
Description
This counter measures the number of times the PS services of HSDPA UEs in CELL_DCH state
are abnormally released due to cell update failures. This counter is measured in the best cell.
This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v9.5.1).
Measurement point
The measurement is triggered at point A, as shown in Figure 1. The RNC receives a CELL
UPDATE message from an HSDPA UE in CELL_DCH state but the cell update procedure fails,
and so the RNC sends a RAB RELEASE REQUEST message to the CN. The CN responds with
a RAB ASSIGNMENT REQUEST message. If the RAB ASSIGNMENT REQUEST message
carries a cause value other than "User Inactivity", "Normal Release", "UE Generated Signalling
Connection Release", "Successful Relocation", or "Network Optimization" and the PS service
of the HSDPA UE is released, this counter is measured in the best cell of the HSDPA UE. For
details about the cause values indicating an abnormal release, see 3GPP TS 25.413.
A cell update procedure is considered as successful when the RNC receives a response message
from the UE after sending a CELL UPDATE CONFIRM message to the UE. The response
message from the UE can be any of the following based on the IE carried in the CELL UPDATE
CONFIRM message:
RADIO BEARER RELEASE COMPLETE
Figure 1 uses the PHYSICAL CHANNEL RECONFIGURATION COMPLETE message as an
example.
Issue 03 (2015-06-30)

1777
BSC6900 UMTS
and so the RNC sends a RAB RELEASE REQUEST message to the CN. The CN responds with
an IU RELEASE COMMAND message. If the IU RELEASE COMMAND message carries a
cause value other than "User Inactivity", "Normal Release", "UE Generated Signalling
example.
Issue 03 (2015-06-30)

1778
BSC6900 UMTS
and so the RNC sends an IU RELEASE REQUEST message to the CN. The CN responds with
an IU RELEASE COMMAND message. If the IU RELEASE COMMAND message carries a
cause value other than "User Inactivity", "Normal Release", "UE Generated Signalling
example.
Issue 03 (2015-06-30)

1779
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.CellDCH.CellUpdt
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010503
WRFD-010504

Issue 03 (2015-06-30)

1780
BSC6900 UMTS
Sum of the Sampled RLC Throughput of HSDPA Users in a Cell

Counters
Counter ID
Counter Name
Counter Description
73443312
Sum of the Sampled RLC

Throughput of HSDPA Users
in a Cell
Description
This counter measures the sum of the sampled RLC throughput of all HSDPA users in a serving
cell. This counter is in units of kbit/s. This counter is used with the
VS.HSDPA.SamplesThroughput counter to calculate the average throughput of HSDPA users.
The formula is as follows: Average throughput of HSDPA users = VS.HSDPA.SumThroughput/
Measurement point
The RNC takes samples of the RLC throughput of all HSDPA users every 100 ms in a
measurement period. The sum of the sampled user throughput that is not 0 in a measurement
period is used as the value of this counter. The RLC header and retransmitted data are excluded.
For multi-carrier users, this counter is measured only in the primary cell based on the total
throughput on the primary and secondary carriers.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010610
HSDPA Introduction
Package

1781
BSC6900 UMTS
Number of Times the RLC Throughput Is Not 0 for HSDPA Users in a Cell
Counters
Counter ID
Counter Name
Counter Description
73426999
Number of Times the RLC

Throughput Is Not 0 for
Description
This counter measures the total number of sampling times the RLC throughput is not 0 for
HSDPA users in a serving cell.
Measurement point
The RNC takes samples of the RLC throughput of HSDPA users every 100 ms in a measurement
period and records the number of times the RLC throughput is not 0. The sum of the sampling
times in a measurement period is used as the value of this counter.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010610
HSDPA Introduction
Package
Average Number of Gold, Silver, and Copper HSDPA Users for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444431
VS.HSDPA.GoldenUE.Mea
n.Cell
Average Number of Gold

73444432
VS.HSDPA.SilverUE.Mean.
Cell
Average Number of Silver


1782
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444433
VS.HSDPA.CopperUE.Mea
n.Cell
Average Number of Copper

Description
These counters measure the average number of gold, silver, and copper HSDPA users in the
serving cell. Each MC-HSDPA user is measured as one HSDPA user on the primary carrier. If
a UE is processing combined services, the priority of the highest-priority service is used as the
priority of the UE.
Measurement point
The RNC takes samples of the number of gold, silver, and copper HSDPA users every 5 seconds
in a measurement period. At the end of the measurement period, the RNC obtains the average
number of gold, silver, and copper HSDPA users by dividing the accumulated numbers by the
corresponding sampling times.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.GoldenUE.Mea
n.Cell
WRFD-01061016
WRFD-010622
WRFD-010623
WRFD-01061016
WRFD-010622
WRFD-010623
WRFD-01061016
WRFD-010622
WRFD-010623
VS.HSDPA.SilverUE.Mean.
Cell
VS.HSDPA.CopperUE.Mea
n.Cell
Issue 03 (2015-06-30)

1783
BSC6900 UMTS
1.12.17 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.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203850
VS.HSUPA.UE.Me
an.Cell
Average Number of
HSUPA UEs in a
Cell
Earlier than
BSC6900
V900R011
67192110
VS.HSUPA.MACD
.SuccSetup
Number of
Successful EDCH
MAC-d Flow
Establishments for
Cell
Earlier than
BSC6900
V900R011
67192114
VS.HSUPA.RAB.A
ttEstab
Number of HSUPA
RAB Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67192115
VS.HSUPA.RAB.S
uccEstab
Number of
Successful HSUPA
RAB Establishments
for Cell
Earlier than
BSC6900
V900R011
67192969
VS.HSUPA.RAB.A
ttEstab.BE.Golden
Number of HSUPA
RAB Establishment
Attempts of BE
Service for Golden
Level User for Cell
Earlier than
BSC6900
V900R011
67192970
VS.HSUPA.RAB.A
ttEstab.BE.Silver
Number of HSUPA
RAB Establishment
Attempts of BE
Service for Silver
Level User for Cell
Earlier than
BSC6900
V900R011
67192971
VS.HSUPA.RAB.A
ttEstab.BE.Copper
Number of HSUPA
RAB Establishment
Attempts of BE
Service for Copper
Level User for Cell
Earlier than
BSC6900
V900R011

1784
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192972
VS.HSUPA.RAB.S
uccEstab.BE.Golden
Number of
Successful HSUPA
RAB Establishments
of BE Service for
Golden Level User
for Cell
Earlier than
BSC6900
V900R011
67192973
VS.HSUPA.RAB.S
uccEstab.BE.Silver
Number of
Successful HSUPA
RAB Establishments
of BE Service for
Silver Level User for
Cell
Earlier than
BSC6900
V900R011
67192974
VS.HSUPA.RAB.S
uccEstab.BE.Copper
Number of
Successful HSUPA
RAB Establishments
of BE Service for
Copper Level User
for Cell
Earlier than
BSC6900
V900R011
67192364
VS.HSUPA.RAB.A
bnormRel
Number of HSUPA
RABs Abnormal
Releases for Cell
Earlier than
BSC6900
V900R011
67192365
VS.HSUPA.RAB.N
ormRel
Number of HSUPA
RABs Normal
Released for Cell
Earlier than
BSC6900
V900R011
67192366
VS.HSUPA.RAB.N
ormRel.UEGen
Number of HSUPA
RAB Releases Due
to UE Signal
Connection Release
for Cell
Earlier than
BSC6900
V900R011
67192367
VS.HSUPA.SHO.A
ttOut
Number of EDCH
RL Addition and
Deletion Attempts by
Soft Handover for
Cell
Earlier than
BSC6900
V900R011
67192368
VS.HSUPA.SHO.S
uccOut
Number of
Successful EDCH
RL Additions and
Deletions by Soft
Handover for Cell
Earlier than
BSC6900
V900R011

1785
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192369
VS.HSUPA.SHO.S
ervCellChg.SuccOut
Number of
Successful HSUPA
Serving Cell
Changes in Soft
Handover Status for
Cell
Earlier than
BSC6900
V900R011
67192370
VS.HSUPA.SHO.S
ervCellChg.AttOut
Number of HSUPA
Serving Cell Change
Attempts in Soft
Handover Status for
Cell
Earlier than
BSC6900
V900R011
67195485
VS.HSUPA.SHO.S
ervCellChg.AttOutIur
Number of interRNC HSUPA

Serving Cell Change
Attempts in Soft
Handover Status for
Cell
Earlier than
BSC6900
V900R011
67195486
VS.HSUPA.SHO.S
ervCellChg.SuccOutIur
Number of
Successful interRNC HSUPA
Serving Cell
Changes in Soft
Handover Status for
Cell
Earlier than
BSC6900
V900R011
67195487
VS.HSUPA.HHO.E
2E.SuccOutIur
Number of
Successful HSUPA
Serving Cell
Changes Due to
inter-RNC Hard
Handover without
Channel Change for
Cell
Earlier than
BSC6900
V900R011
67195488
VS.HSUPA.HHO.E
2E.AttOutIur
Number of HSUPA
Serving Cell Change
Attempts Due to
inter-RNC Hard
Handover without
Channel Change for
Cell
Earlier than
BSC6900
V900R011

1786
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192371
VS.HSUPA.HHO.E
2E.SuccOutIntraFreq
Number of
Successful HSUPA
Serving Cell
Changes Due to
Intra-Frequency
Hard Handover
without Channel
Change for Cell
Earlier than
BSC6900
V900R011
67192372
VS.HSUPA.HHO.E
2E.AttOutIntraFreq
Number of HSUPA
Serving Cell Change
Attempts Due to
Intra-Frequency
Hard Handover
without Channel
Change for Cell
Earlier than
BSC6900
V900R011
67192373
VS.HSUPA.HHO.E
2E.SuccOutInterFreq
Number of
Successful HSUPA
Serving Cell
Changes Due to
Inter-Frequency
Hard Handover
without Channel
Change for Cell
Earlier than
BSC6900
V900R011
67192374
VS.HSUPA.HHO.E
2E.AttOutInterFreq
Number of HSUPA
Serving Cell Change
Attempts Due to
Inter-Frequency
Hard Handover
without Channel
Change for Cell
Earlier than
BSC6900
V900R011
67192470
VS.HSUPA.E2D.Su
cc
Number of
Successful Channel
Conversions from
EDCH to DCH for
HSUPA Service for
Cell
Earlier than
BSC6900
V900R011
67192471
VS.HSUPA.E2D.At
t
Number of Channel
Conversion
Attempts from
EDCH to DCH for
HSUPA Service for
Cell
Earlier than
BSC6900
V900R011

1787
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192472
VS.HSUPA.HHO.E
2D.SuccOutIntraFreq
Number of
Successful HSUPA
Intra-Frequency
Hard Handovers for
Cell(EDCH to DCH)
Earlier than
BSC6900
V900R011
67192473
VS.HSUPA.HHO.E
2D.AttOutIntraFreq
Number of HSUPA
Intra-Frequency
Hard Handover
Attempts for Cell
(EDCH to DCH)
Earlier than
BSC6900
V900R011
67192474
VS.HSUPA.HHO.E
2D.SuccOutInterFreq
Number of
Successful HSUPA
Inter-Frequency
Hard Handovers for
Cell(EDCH to DCH)
Earlier than
BSC6900
V900R011
67192475
VS.HSUPA.HHO.E
2D.AttOutInterFreq
Number of HSUPA
Inter-Frequency
Hard Handover
Attempts for Cell
(EDCH to DCH)
Earlier than
BSC6900
V900R011
67192476
VS.HSUPA.D2E.Su
cc
Number of
Successful Channel
Conversions from
DCH to EDCH for
HSUPA Service for
Cell
Earlier than
BSC6900
V900R011
67192477
VS.HSUPA.D2E.At
t
Number of Channel
Conversion
Attempts from DCH
to EDCH for HSUPA
Service for Cell
Earlier than
BSC6900
V900R011
67192480
VS.HSUPA.E2F.At
t
Number of Channel
Conversion
Attempts from
EDCH to FACH for
HSUPA Service for
Cell
Earlier than
BSC6900
V900R011
67192481
VS.HSUPA.E2F.Su
cc
Number of
Successful Channel
Conversions from
EDCH to FACH for
HSUPA Service for
Cell
Earlier than
BSC6900
V900R011

1788
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192482
VS.HSUPA.F2E.At
t
Number of Channel
Conversion
Attempts from
FACH to EDCH for
HSUPA Service for
Cell
Earlier than
BSC6900
V900R011
67192483
VS.HSUPA.F2E.Su
cc
Number of
Successful Channel
Conversions from
FACH to EDCH for
HSUPA Service for
Cell
Earlier than
BSC6900
V900R011
67203932
VS.HSUPA.MeanChThroughput
Mean Uplink
Throughput of single
HSUPA MAC-d
Flow for Cell
Earlier than
BSC6900
V900R011
67192486
VS.HSUPA.MeanC
Number of Total
Bytes Received in
Uplink of HSUPA
MAC-d Flow for
Cell
Earlier than
BSC6900
V900R011
67204513
VS.HSUPA.Golden
BeMeanChThroug
hput
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE Service
for Golden
Subscriber for Cell
Earlier than
BSC6900
V900R011
67194873
VS.HSUPA.Golden
BeMeanChThroug
hput.TotalBytes
Number of Total
Bytes Received in
Uplink of HSUPA
MAC-d Flow of BE
Service for Golden
Subscriber for Cell
Earlier than
BSC6900
V900R011
67204514
VS.HSUPA.SilverBeMeanChThroug
hput
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE Service
for Silver Subscriber
for Cell
Earlier than
BSC6900
V900R011

1789
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194875
VS.HSUPA.SilverB
eMeanChThrough
put.TotalBytes
Number of Total
Bytes Received in
Uplink of HSUPA
MAC-d Flow of BE
Service for Silver
Subscriber for Cell
Earlier than
BSC6900
V900R011
67204515
VS.HSUPA.Copper
BeMeanChThroug
hput
Mean Uplink
Throughput of
HSUPA MAC-d
Flow of BE Service
for Copper
Subscriber for Cell
Earlier than
BSC6900
V900R011
67194889
VS.HSUPA.Copper
BeMeanChThroug
hput.TotalBytes
Number of Total
Bytes Received in
Uplink of HSUPA
MAC-d Flow of BE
Service for Copper
Subscriber for Cell
Earlier than
BSC6900
V900R011
73403761
VS.HSUPA.UE.Ma
x.Cell
Maximum Number
of HSUPA UEs in a
Cell
BSC6900
V900R012
73403766
VS.HSUPA.HHO.E
2D.AttOutIur
Number of interRNC HSUPA Hard

Handover Attempts
for Cell(EDCH to
DCH)
BSC6900
V900R012
73403767
VS.HSUPA.HHO.E
2D.SuccOutIur
Number of
Successful interRNC HSUPA Hard
Handovers for Cell
(EDCH to DCH)
BSC6900
V900R012
73403795
VS.HSUPA.RAB.
16QAM.SuccEstab
Number of
Successful HSUPA
16QAM RAB
Establishments for
cell
BSC6900
V900R012
73403796
VS.HSUPA.RAB.A
bnormRel.16QAM
Number of HSUPA
16QAM RABs
Abnormal Released
Including RF Cause
for cell
BSC6900
V900R012

1790
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403797
VS.HSUPA.RAB.N
ormRel.16QAM
Number of HSUPA
16QAM RABs
Normal Released for
cell
BSC6900
V900R012
73403794
VS.HSUPA.RAB.
16QAM.AttEstab
Number of HSUPA
16QAM RAB Setup
Attempts for cell
BSC6900
V900R012
73391136
VS.HSUPA.RAB.A
bnormRel.RF
Number of HSUPA
RABs Abnormal
Released due to RF
Failures for Cell
BSC6900
V900R012
67204266
VS.HSUPA.UE.Me
an.CAT1.4
Average Number of
HSUPA UEs with
Category 1-4 in a
Cell
BSC6900
V900R012
67204267
VS.HSUPA.UE.Me
an.CAT5
Average Number of
HSUPA UEs with
Category 5 in a Cell
BSC6900
V900R012
67204268
VS.HSUPA.UE.Me
an.CAT6
Average Number of
HSUPA UEs with
BSC6900
V900R012
67204269
VS.HSUPA.UE.Me
an.CAT7
Average Number of
HSUPA UEs with
BSC6900
V900R012
67193599
VS.HSUPA.UE.Ma
x.CAT1.4
Maximum Number
of HSUPA UEs with
Category1-4 in a Cell
BSC6900
V900R012
67193602
VS.HSUPA.UE.Ma
x.CAT5
Maximum Number
of HSUPA UEs with
BSC6900
V900R012
67193605
VS.HSUPA.UE.Ma
x.CAT6
Maximum Number
of HSUPA UEs with
BSC6900
V900R012
67193608
VS.HSUPA.UE.Ma
x.CAT7
Maximum Number
of HSUPA UEs with
BSC6900
V900R012
73393829
VS.HSUPA.MACD
.AttSetup
Number of EDCH
MAC-d Flow Setup
Requests for Cell
BSC6900
V900R012

1791
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393832
VS.HSUPA.RAB.F
ailEstab.ULPower.
Cong
Number of Failed
HSUPA Service
Establishments Due
to UL Power
BSC6900
V900R012
73393833
VS.HSUPA.RAB.F
ailEstab.ULIUBBa
nd.Cong
Number of Failed
HSUPA Service
Establishments Due
to UL Iub Bandwidth
BSC6900
V900R012
73393834
VS.HSUPA.RAB.F
ailEstab.ULCE.Co
ng
Number of Failed
HSUPA Service
Establishments Due
to UL CE
BSC6900
V900R012
73410485
VS.PS.Conv.Kbps.
EDCH
Average uplink
throughput of the
Traffic PS
Conversational
beared on E-DCH for
cell
BSC6900
V900R012
73393914
VS.PS.Conv.Traffi
c.EDCH
Number of uplink
bytes of Transport
Conversational
beared on E-DCH for
cell
BSC6900
V900R012
73393956
VS.HSUPA.RsnSm
all2Large.TTI2ms
Number of Times
that HSUPA 2ms
TTI Users Transfer
from Small
Retransmission to
Large
Retransmission for
Cell
BSC6900
V900R012
73393957
VS.HSUPA.RsnSm
all2Large.TTI10ms
Number of Times
that HSUPA 10ms
TTI Users Transfer
from Small
Retransmission to
Large
Retransmission for
Cell
BSC6900
V900R012

1792
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393958
VS.HSUPA.RsnLa
rge2Small.TTI2ms
Number of Times
that HSUPA 2ms
TTI Users Transfer
from Large
Retransmission to
Small
Retransmission for
Cell
BSC6900
V900R012
73393959
VS.HSUPA.RsnLa
rge2Small.TTI10m
s
Number of Times
that HSUPA 10ms
TTI Users Transfer
from Large
Retransmission to
Small
Retransmission for
Cell
BSC6900
V900R012
73393984
VS.HSUPA.TTI2to
10.Att
Number of TTI
Switch Attempts
During RB
Reconfiguration for
Cell(2ms to 10ms)
BSC6900
V900R012
73393985
VS.HSUPA.TTI2to
10.Succ
Number of
Successful TTI
Switches During RB
Reconfiguration for
Cell(2ms to 10ms)
BSC6900
V900R012
73393986
VS.HSUPA.TTI10t
o2.Att
Number of TTI
Switch Attempts
During RB
Reconfiguration for
Cell(10ms to 2ms)
BSC6900
V900R012
73393987
VS.HSUPA.TTI10t
o2.Succ
Number of
Successful TTI
Switches During RB
Reconfiguration for
Cell(10ms to 2ms)
BSC6900
V900R012
73410507
VS.HSUPA.
16QAM.UE.Mean.
Cell
Average Number of
HSUPA 16QAM
UEs in a Cell
BSC6900
V900R012
73441120
VS.HSUPA.Boostin
g.UE.Mean.Cell
Number of UEs
Supporting EDPCCH Boosting for
Cell
BSC6900
V900R013

1793
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441121
VS.HSUPA.Boostin
gCPC.UE.Mean.Ce
ll
Number of UEs
Supporting EDPCCH Boosting
and CPC for Cell
BSC6900
V900R013
73422168
VS.HSUPA.RAB.A
bnormRel.E2P
Number of RABs
Abnormally
Released for PS
HSUPA Services
during the State
Transition from
CELL_DCH to
CELL_PCH or
URA_PCH for Cell
BSC6900
V900R012
73423359
VS.HSUPA.RAB.B
oosting.AttEstab
Number of HSUPA
Boosting RAB Setup
Attempts for Cell
BSC6900
V900R013
73423360
VS.HSUPA.RAB.B
oosting.SuccEstab
Number of
Successful HSUPA
Boosting RAB
Setups for Cell
BSC6900
V900R013
73423361
VS.HSUPA.RAB.A
bnormRel.Boosting
Number of
Abnormally
Released HSUPA
Boosting RABs for
Cell
BSC6900
V900R013
73423362
VS.HSUPA.RAB.N
ormRel.Boosting
Number of Normally
Released HSUPA
Boosting RABs for
Cell
BSC6900
V900R013
73423567
VS.HSUPA.HARQ.
POReCfgAtt.TTI1
0ms
Number of HARQ
PO Reconfiguration
Attempts of HSUPA
Users with 10 ms TTI
for Cell
BSC6900
V900R013
73423568
VS.HSUPA.HARQ.
POReCfgSucc.TTI
10ms
Number of
Successful HARQ
PO Reconfigurations
of HSUPA Users
with 10 ms TTI for
Cell
BSC6900
V900R013

1794
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424115
VS.HSUPA.RAB.D
C.AttEstab
Number of DCHSUPA RAB Setup

Attempts for Cell
BSC6900
V900R014
73424116
VS.HSUPA.RAB.D
C.SuccEstab
Number of
Successful DCHSUPA RAB Setups
for Cell
BSC6900
V900R014
73424117
VS.HSUPA.RAB.D
C.NormRel
Number of DCHSUPA RABs

Normally Released
for Cell
BSC6900
V900R014
73424118
VS.HSUPA.RAB.D
C.AbnormRel
Number of DCHSUPA RABs

Abnormally
Released for Cell
BSC6900
V900R014
73441235
VS.HSUPA.UE.Me
an.CAT8
Average Number of
HSUPA UEs with
BSC6900
V900R014
73424186
VS.HSUPA.UE.Ma
x.CAT8
Maximum Number
of HSUPA UEs with
BSC6900
V900R014
73441236
VS.HSUPA.UE.Me
an.CAT9
Average Number of
HSUPA UEs with
BSC6900
V900R014
73424189
VS.HSUPA.UE.Ma
x.CAT9
Maximum Number
of HSUPA UEs with
BSC6900
V900R014
73424192
VS.HSUPA.DC.PR
IM.UE.Mean.Cell
Mean Number of
DC-HSUPA Users in
the Cell with the
Primary Carrier
BSC6900
V900R014
73441238
VS.HSUPA.DC.SE
C.UE.Mean.Cell
Mean Number of
DC-HSUPA Users in
the Cell with the
Secondary Carrier
BSC6900
V900R014
73441239
VS.HSUPA.UE.Me
an.TTI2ms
Average Number of
HSUPA 2 ms TTI
UEs in a Cell
BSC6900
V900R014

1795
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424199
VS.HSUPA.UE.Ma
x.TTI2ms
Maximum Number
of HSUPA 2 ms TTI
UEs in a Cell
BSC6900
V900R014
73441240
VS.HSUPA.UE.Me
an.TTI10ms
Average number of
HSUPA 10 ms TTI
UEs in a Cell
BSC6900
V900R014
73424202
VS.HSUPA.UE.Ma
x.TTI10ms
Maximum Number
of HSUPA 10 ms
TTI UEs in a Cell
BSC6900
V900R014
73424205
VS.HSUPA.RABEs
tabTTI10ms.AdmC
E.Succ
Number of
Successful RAB
Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to
Congestion of
Admitted CEs in a
Cell
BSC6900
V900R014
73424206
VS.HSUPA.RABEs
tabTTI10ms.ResR
TWP.Succ
Number of
Successful RAB
Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to
RTWP Congestion in
a Cell
BSC6900
V900R014
73424207
VS.HSUPA.RABEs
tabTTI10ms.ResUs
edCE.Succ
Number of
Successful RAB
Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to
Congestion of
Occupied CEs in a
Cell
BSC6900
V900R014
73424208
VS.HSUPA.RABEs
tabTTI10ms.ResIU
B.Succ
Number of
Successful RAB
Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to Iub
Resource
Congestion in a Cell
BSC6900
V900R014

1796
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424967
VS.HSUPA.RABEs
tabTTI10ms.Cover
.Succ
Number of
Successful RAB
Establishments
Initiated by HSUPA
2 ms UEs with a 10
ms TTI Due to
Limited Uplink
Coverage
BSC6900
V900R014
73425950
VS.HSUPA.RAB.A
bnormRel.
16QAM2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of
HSUPA+16QAM
UEs to CELL/
URA_PCH
BSC6900
V900R015C00
73425951
VS.HSUPA.RAB.A
bnormRel.DC2P
Number of
Abnormal RAB
Releases for Cell
During State
Transition of DCHSUPA UEs to
CELL/URA_PCH
BSC6900
V900R015C00
73425952
VS.HSUPA.RAB.N
ormRel.
16QAM.All
Number of Normal
RAB Releases of
HSUPA+16QAM
UEs for Cell (All
Scenarios)
BSC6900
V900R015C00
73425953
VS.HSUPA.RAB.N
ormRel.DC.All
Number of Normal
RAB Releases of
DC-HSUPA UEs for
BSC6900
V900R015C00
73443311
VS.HSUPA.SumThroughput
Sum of the Sampled

RLC Throughput of
HSUPA Users in a
Cell
BSC6900
V900R015C01
73426996
VS.HSUPA.SamplesThroughput
Number of Times the

RLC Throughput Is
Not 0 for HSUPA
Users in a Cell
BSC6900
V900R015C01

1797
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444295
VS.HSUPA.FlexPC
LowRate.UE.Mean
.TTI2ms
Average Number of
2 ms TTI UEs That
Use the Flexible
Power Control for
Uplink Low-Rate
Data Transmission
Feature When
Processing a Single
HSUPA BE Service
for Cell
BSC6900
V900R016C00
73444296
VS.HSUPA.FlexPC
LowRate.UE.Mean
.TTI10ms
Average Number of
10 ms TTI UEs That
Use the Flexible
Power Control for
Uplink Low-Rate
Data Transmission
Feature When
Processing a Single
HSUPA BE Service
for Cell
BSC6900
V900R016C00
73444297
VS.MultiRAB.Flex
PCLowRate.UE.M
ean.TTI2ms
Average Number of
2 ms TTI UEs That
Use the Flexible
Power Control for
Uplink Low-Rate
Data Transmission
Feature When
Processing
Combined Services
for Cell
BSC6900
V900R016C00
73444298
VS.MultiRAB.Flex
PCLowRate.UE.M
ean.TTI10ms
Average Number of
10 ms TTI UEs That
Use the Flexible
Power Control for
Uplink Low-Rate
Data Transmission
Feature When
Processing
Combined Services
for Cell
BSC6900
V900R016C00

1798
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444320
VS.HSUPA.Single
BE.Mean.TTI2ms.
ULActualPowerLoad.0
Average Number of
2ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
of the Cell Falls into
Range 0 for Cell
BSC6900
V900R016C00
73444321
VS.HSUPA.Single
BE.Mean.TTI2ms.
ULActualPowerLoad.1
Average Number of
2ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 1 for Cell
BSC6900
V900R016C00
73444322
VS.HSUPA.Single
BE.Mean.TTI2ms.
ULActualPowerLoad.2
Average Number of
2ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 2 for Cell
BSC6900
V900R016C00
73444323
VS.HSUPA.Single
BE.Mean.TTI2ms.
ULActualPowerLoad.3
Average Number of
2ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 3 for Cell
BSC6900
V900R016C00
73444324
VS.HSUPA.Single
BE.Mean.TTI2ms.
ULActualPowerLoad.4
Average Number of
2ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 4 for Cell
BSC6900
V900R016C00

1799
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444325
VS.HSUPA.Single
BE.Mean.TTI10ms
.ULActualPowerLoad.0
Average Number of
10ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 0 for Cell
BSC6900
V900R016C00
73444326
VS.HSUPA.Single
BE.Mean.TTI10ms
Average Number of
10ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 1 for Cell
BSC6900
V900R016C00
73444327
VS.HSUPA.Single
BE.Mean.TTI10ms
Average Number of
10ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 2 for Cell
BSC6900
V900R016C00
73444328
VS.HSUPA.Single
BE.Mean.TTI10ms
Average Number of
10ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 3 for Cell
BSC6900
V900R016C00
73444329
VS.HSUPA.Single
BE.Mean.TTI10ms
Average Number of
10ms TTI HSUPA
UEs Processing a
Single BE Service
When the Actual
Uplink Power Load
Range 4 for Cell
BSC6900
V900R016C00

1800
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428216
VS.HSUPA.HARQ.
POReCfgAtt.TTI2
ms
Number of HARQ
PO Reconfiguration
Attempts of HSUPA
Users with 2 ms TTI
for Cell
BSC6900
V900R016C00
73428217
VS.HSUPA.HARQ.
POReCfgSucc.TTI
2ms
Number of
Successful HARQ
PO Reconfigurations
of HSUPA Users
with 2 ms TTI for
Cell
BSC6900
V900R016C00
73444428
VS.HSUPA.Golden
UE.Mean.Cell
Average Number of
Gold HSUPA Users
for Cell
BSC6900
V900R016C00
73444429
VS.HSUPA.SilverU
E.Mean.Cell
Average Number of
Silver HSUPA Users
for Cell
BSC6900
V900R016C00
73444430
VS.HSUPA.Copper
UE.Mean.Cell
Average Number of
Copper HSUPA
Users for Cell
BSC6900
V900R016C00
73428930
VS.HSUPA.RAB.A
bnormRel.SRBoE.
AboveR8
Number of
Abnormal RAB
Releases for UEs
Complying with R8
and Later and Using
SRB over HSUPA
for Cell
BSC6900
V900R016C00
73428931
VS.HSUPA.RAB.N
ormRel.SRBoE.Ab
oveR8
Number of Normal
RAB Releases for
UEs Complying with
R8 and Later and
Using SRB over
HSUPA for Cell
BSC6900
V900R016C00
73430199
VS.HSUPA.HARQ.
ACK.TTI2ms
Number of Times the

HARQ Scheduling
Results of HSUPA
UEs Using the 2 ms
TTI Are ACK for
Cell
BSC6900
V900R017C10

1801
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430200
VS.HSUPA.HARQ.
NACK.TTI2ms
Number of Times the

HARQ Scheduling
Results of HSUPA
UEs Using the 2 ms
TTI Are NACK for
Cell
BSC6900
V900R017C10
73430201
VS.HSUPA.HARQ.
LOST.TTI2ms
Number of Times the

HARQ Scheduling
Results of HSUPA
UEs Using the 2 ms
TTI Are LOST for
Cell
BSC6900
V900R017C10
73430202
VS.HSUPA.HARQ.
ACK.TTI10ms
Number of Times the

HARQ Scheduling
Results of HSUPA
UEs Using the 10 ms
TTI Are ACK for
Cell
BSC6900
V900R017C10
73430203
VS.HSUPA.HARQ.
NACK.TTI10ms
Number of Times the

HARQ Scheduling
Results of HSUPA
UEs Using the 10 ms
TTI Are NACK for
Cell
BSC6900
V900R017C10
73430204
VS.HSUPA.HARQ.
LOST.TTI10ms
Number of Times the

HARQ Scheduling
Results of HSUPA
UEs Using the 10 ms
TTI Are LOST for
Cell
BSC6900
V900R017C10
73430279
VS.HSUPA.SHO.D
C.SEC.AttRLAdd
Number of Attempts
to Add RLs on the
Secondary Carrier
for DC-HSUPA UEs
During Soft and
Softer Handovers for
Cell
BSC6900
V900R017C10

1802
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430280
VS.HSUPA.SHO.D
C.SEC.SuccRLAdd
Number of Times
RLs on the
Secondary Carrier
Are Successfully
Added for DCHSUPA UEs During
Soft and Softer
Handovers for Cell
BSC6900
V900R017C10
73430281
VS.HSUPA.SHO.D
C.SEC.AttRLDel
Number of Attempts
to Remove RLs on
the Secondary
Carrier for DCHSUPA UEs During
Soft and Softer
Handovers for Cell
BSC6900
V900R017C10
73430282
VS.HSUPA.SHO.D
C.SEC.SuccRLDel
Number of Times
RLs on the
Secondary Carrier
Are Successfully
Removed for DCHSUPA UEs During
Soft and Softer
Handovers for Cell
BSC6900
V900R017C10
73446470
VS.HSUPA.UE.Me
an.BestCell
Average Number of
HSUPA UEs in the
Serving Cell
BSC6900
V900R017C10
Counter
Sub Counter
VS.HSUPA.RAB.AttEstab
VS.HSUPA.RAB.AttEstab.BE.Golden
VS.HSUPA.RAB.AttEstab.BE.Silver
VS.HSUPA.RAB.AttEstab.BE.Copper
VS.HSUPA.RAB.SuccEstab.BE.Golden
VS.HSUPA.RAB.SuccEstab.BE.Silver
VS.HSUPA.RAB.SuccEstab.BE.Copper
Issue 03 (2015-06-30)

1803
BSC6900 UMTS
Average Number of HSUPA UEs in a Cell

Counters
Counter ID
Counter Name
Counter Description
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.
For DC-HSUPA UEs, these counters are measured only on the primary carrier.
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of the number of
HSUPA UEs. At the end of the measurement period, by dividing the accumulated value of
sample data in the period by the number of samples, the average number of HSUPA UEs in the
measurement period is obtained; by selecting the maximum value of sample data in the period,
the maximum number of HSUPA UEs in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.UE.Mean.Cell
WRFD-01061211
20 HSUPA Users per Cell
WRFD-010634
WRFD-010639
WRFD-01061202
WRFD-020101
Admission Control
VS.HSUPA.UE.Max.Cell
Issue 03 (2015-06-30)

1804
BSC6900 UMTS
Number of Successful EDCH MAC-d Flow Establishments for Cell

Counters
Counter ID
Counter Name
Counter Description
67192110
VS.HSUPA.MACD.SuccSetup
Number of Successful EDCH

MAC-d Flow Establishments
for Cell
Description
This measurement item takes statistics of the number of successful EDCH MAC-d flow
establishments for UE by RNC in a cell.For DC-HSUPA users, this counter is measured only in
the cell with the primary carrier. This counter complies with section "8.2.17 Radio Link Setup",
"8.3.1 Radio Link Addition" and "8.3.2 Synchronised Radio Link" in 3GPP TS 25.433 (v9.2.0).
Measurement point
This measurement is triggered at point C as shown in Figure. When the RNC sends a RADIO
LINK RECONFIGURATION COMMIT message to the NodeB, the RNC measures this item
in the cell where the radio link exists if the HSUPA RABs are setup. During the reconfiguration
of the radio link, the HSUPA RABs are set up if the message RADIO LINK
RECONFIGURATION PREPARE contains the newly added EDCH MACD FLOW.
This measurement is triggered at point B as shown in Figure. When the RNC sends a RADIO
LINK SETUP REQUEST/RADIO LINK ADDITION REQUEST message to the NodeB, the
RNC measures this item in the cell where the radio link is successfully set up for the HSUPA
service if the RNC receives a RADIO LINK SETUP RESPONSE/RADIO LINK ADDITION
RESPONSE message from the NodeB.
Issue 03 (2015-06-30)

1805
BSC6900 UMTS
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-772 RL setup procedure (successful operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPA.MACD.SuccSetup
WRFD-010612
HSUPA Introduction
Package

1806
BSC6900 UMTS
Number of HSUPA RAB Establishment Attempts for Cell

Counters
Counter ID
Counter Name
Counter Description
67192114
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.
Issue 03 (2015-06-30)

1807
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-010632

HSUPA
Number of Successful HSUPA RAB Establishments for Cell

Counters
Counter ID
Counter Name
Counter Description
67192115
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.
Issue 03 (2015-06-30)

1808
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-010632

HSUPA
Issue 03 (2015-06-30)

1809
BSC6900 UMTS
Number of HSUPA RAB establish attempts of BE Service for different prior Level
Users (Cell)
Counters
Counter ID
Counter Name
Counter Description
67192969
BE.Golden
Number of HSUPA RAB

BE Service for Golden Level
User for Cell
67192970
BE.Silver
Number of HSUPA RAB

BE Service for Silver Level
User for Cell
67192971
BE.Copper
Number of HSUPA RAB

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 DCHSUPA users, these counters are measured only in the cell with the primary carrier. The
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.
Issue 03 (2015-06-30)

1810
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
BE.Golden
WRFD-01061206

BE.Silver
WRFD-01061206

BE.Copper
WRFD-01061206


1811
BSC6900 UMTS
Number of Successful HSUPA RAB Establishments of BE Service for different

prior Level Users (Cell)
Counters
Counter ID
Counter Name
Counter Description
67192972
.BE.Golden
HSUPA RAB
Service for Golden Level
User for Cell
67192973
.BE.Silver
HSUPA RAB
Service for Silver Level User
for Cell
67192974
.BE.Copper
HSUPA RAB
Service for Copper Level
User for Cell
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. The
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving a RADIO
BEARER SETUP COMPLETE message from a UE, the RNC sends a RAB ASSIGNMENT
RESPONSE message to the CN. If the assignment is for setting up the HSUPA service, the RNC
measures the items by the prior lever in the HSUPA serving cell.
Issue 03 (2015-06-30)

1812
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.BE.Golden
WRFD-01061206

.BE.Silver
WRFD-01061206

.BE.Copper
WRFD-01061206


1813
BSC6900 UMTS
Number of HSUPA RABs Abnormal Released for Cell

Counters
Counter ID
Counter Name
Counter Description
67192364
VS.HSUPA.RAB.AbnormRel

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. This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v9.5.1).
Measurement point
Optimization", reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA
serving cell if the released RAB is a HSUPA service.
Issue 03 (2015-06-30)

1814
BSC6900 UMTS

Generated Signalling Connection Release","Successful Relocation" or "Network Optimization",
reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA serving cell if the
released RAB is a HSUPA service.
Generated Signalling Connection Release","Successful Relocation" or "Network Optimization",
reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA serving cell if the
released RAB is a HSUPA service.
Issue 03 (2015-06-30)

1815
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.AbnormRel
WRFD-01061206

WRFD-010632

HSUPA
Issue 03 (2015-06-30)

1816
BSC6900 UMTS
Number of HSUPA RABs Normal Released for Cell

Counters
Counter ID
Counter Name
Counter Description
67192365
VS.HSUPA.RAB.NormRel

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. This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v9.5.1).
Measurement point
in the HSUPA serving cell if it is a HSUPA service.
Issue 03 (2015-06-30)

1817
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
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.NormRel
WRFD-01061206

WRFD-010632

HSUPA
Issue 03 (2015-06-30)

1818
BSC6900 UMTS
Number of HSUPA RAB Released due to UE Signaling Connection failure for Cell
Counters
Counter ID
Counter Name
Counter Description
67192366
VS.HSUPA.RAB.NormRel.
UEGen
Number of HSUPA RAB

Releases Due to UE Signal
Connection Release for Cell
Description
This measurement item takes statistics of the number of HSUPA RABs released by the RNC
due to UE Signal Connection Release.For DC-HSUPA users, this counter is measured only in
the cell with the primary carrier. This counter complies with section "8.2 RAB Assignment" in
3GPP TS 25.413 (v9.5.1).
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-782 UL SIG connection release procedure
Formula
None
Issue 03 (2015-06-30)

1819
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
UEGen
WRFD-01061206

WRFD-010632

HSUPA
Number of EDCH RL Addition and Deletion Attempts by Soft Handover for Cell
Counters
Counter ID
Counter Name
Counter Description
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
the primary carrier. This counter complies with section "8.3.4 Active set update" in 3GPP TS
25.331 (v9.2.1).
Measurement point
This measurement is triggered at point B as shown in the figure. When the RNC sends an
ACTIVE SET UPDATE message to the UE and there is EDCH RL to be deleted or added during
the soft handover, the RNC measures this item in the cell where the EDCH link is added or
deleted.
Issue 03 (2015-06-30)

1820
BSC6900 UMTS
Figure 1-783 Soft handover procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.SHO.AttOut
WRFD-01061204
HSUPA Mobility
Management
Number of Successful EDCH RL Additions and Deletions by Soft Handover for

Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192368
VS.HSUPA.SHO.SuccOut
Number of Successful EDCH

RL Additions and Deletions
by Soft Handover for Cell

1821
BSC6900 UMTS
Description
This counter provides the number of successful EDCH RL additions and deletions due to soft
handover in a cell. For DC-HSUPA users, this counter is measured only in the cell with the
primary carrier. This counter complies with section "8.3.4 Active set update" in 3GPP TS 25.331
(v9.2.1).
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 counter in the cell where the EDCH
link is added or deleted.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPA.SHO.SuccOut
WRFD-01061204
HSUPA Mobility
Management

1822
BSC6900 UMTS
Number of Successful HSUPA Serving Cell Changes in Soft Handover Status for
Cell
Counters
Counter ID
Counter Name
Counter Description
67192369
VS.HSUPA.SHO.ServCellC
hg.SuccOut
HSUPA Serving Cell
Changes in Soft Handover
Status for Cell
Description
This counter provides the number of successful HSUPA serving cell changes in soft handover
status in a cell. For DC-HSUPA users, this counter is measured only in the cell with the primary
carrier. This counter complies with section "8.3.4 Active set update" and "8.2.2 Reconfiguration
Measurement point
The procedure of changing a serving HSUPA cell can be triggered by any of the following
messages sent from a RNC to a UE: PHYSICAL CHANNEL RECONFIGURATION,
TRANSPORT CHANNEL RECONFIGURATION, and RADIO BEARER
RECONFIGURATION. Accordingly, the UE may send the UE may respond with any of the
following messages: PHYSICAL CHANNEL RECONFIGURATION COMPLETE,
PHYSICAL CHANNEL RECONFIGURATION FAILURE, TRANSPORT CHANNEL
RECONFIGURATION COMPLETE, TRANSPORT CHANNEL RECONFIGURATION
FAILURE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER
RECONFIGURATION FAILURE.This measurement is triggered at point B as shown in Figure
1, 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 counter in
the original HSUPA serving cell if the HSUPA serving cell is changed. The counter is used to
indicate the change of HSUPA serving cells in the soft handover status instead of the hard
handover status.
Issue 03 (2015-06-30)

1823
BSC6900 UMTS
Figure 1-785 Serving cell change procedure (successful operation)
This measurement is triggered at point C as shown in the following 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 the counter in the original HSUPA
serving cell.
Formula
None
Issue 03 (2015-06-30)

1824
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
hg.SuccOut
WRFD-01061204
HSUPA Mobility
Management
Number of HSUPA Serving Cell Change Attempts in Soft Handover Status for Cell
Counters
Counter ID
Counter Name
Counter Description
67192370
hg.AttOut
Number of HSUPA Serving

Cell Change Attempts in Soft
Handover Status for Cell
Description
This measurement item takes statistics of the number of HSUPA serving cell change attempts
in soft handover status for cell.For DC-HSUPA users, this counter is measured only in the cell
with the primary carrier. This counter complies with section "8.3.4 Active set update" and "8.2.2
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
to indicate the change of HSUPA serving cells in the soft handover status instead of the hard
handover status.
Issue 03 (2015-06-30)

1825
BSC6900 UMTS
This measurement triggered at point B as shown in Figure , when the RNC sends an ACTIVE
SET UPDATE message to the UE. If the HSUPA serving cell changes during the soft handover,
the RNC measures this item in the original HSUPA serving cell.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1826
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
hg.AttOut
WRFD-01061204
HSUPA Mobility
Management
Number of inter-RNC HSUPA Serving Cell Change Attempts in Soft Handover

Status for Cell
Counters
Counter ID
Counter Name
Counter Description
67195485
hg.AttOutIur
Number of inter-RNC
HSUPA Serving Cell Change
Attempts in Soft Handover
Status for Cell
Description
This measurement counter takes statistics of the number of inter-RNC HSUPA serving cell
change attempts in soft handover status for cell. It is measured in a serving cell.For DC-HSUPA
users, this counter is measured only in the cell with the primary carrier. This counter complies
with section "8.3.4 Active set update" and "8.2.2 Reconfiguration procedures" in 3GPP TS
25.331 (v9.2.1).
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.
Issue 03 (2015-06-30)

1827
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.
Formula
None
Issue 03 (2015-06-30)

1828
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
hg.AttOutIur
WRFD-01061204
HSUPA Mobility
Management
Number of Successful inter-RNC HSUPA Serving Cell Changes in Soft Handover

Status for Cell
Counters
Counter ID
Counter Name
Counter Description
67195486
hg.SuccOutIur
Number of Successful interRNC HSUPA Serving Cell

Changes in Soft Handover
Status for Cell
Description
This counter provides the number of successful HSUPA serving cell changes in soft handover
status in a cell. It is measured in a serving cell.For DC-HSUPA users, this counter is measured
only in the cell with the primary carrier. This counter complies with section "8.3.4 Active set
update" and "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v9.2.1).
Measurement point
The procedure of changing a serving HSUPA cell can be triggered by any of the following
messages sent from a RNC to a UE: PHYSICAL CHANNEL RECONFIGURATION,
TRANSPORT CHANNEL RECONFIGURATION, and RADIO BEARER
RECONFIGURATION. Accordingly, the UE may send the UE may respond with any of the
following messages: PHYSICAL CHANNEL RECONFIGURATION COMPLETE,
PHYSICAL CHANNEL RECONFIGURATION FAILURE, TRANSPORT CHANNEL
RECONFIGURATION COMPLETE, TRANSPORT CHANNEL RECONFIGURATION
FAILURE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER
RECONFIGURATION FAILURE. This measurement is triggered at point B as shown in Figure
1, 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 counter is used to
indicate the change of HSUPA serving cells in the soft handover status instead of the hard
handover status.
Issue 03 (2015-06-30)

1829
BSC6900 UMTS
This measurement is triggered at point C as shown in Figure 2 , 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 counter in the original HSUPA serving cell.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1830
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
hg.SuccOutIur
WRFD-01061204
HSUPA Mobility
Management
Number of Successful HSUPA Serving Cell Changes Due to inter-RNC Hard

Handover without Channel Change for Cell
Counters
Counter ID
Counter Name
Counter Description
67195487
VS.HSUPA.HHO.E2E.SuccOutIur
HSUPA Serving Cell
Changes Due to inter-RNC
Hard Handover without
Channel Change for Cell
Description
This measurement item provides the number of successful HSUPA serving cell changes due to
inter-RNC hard handover for cell. It is measured in the original serving cell.For DC-HSUPA
users, this counter is measured only in the cell with the primary carrier.The hard handover
procedure can be triggered with the following messages:[1]PHYSICAL CHANNEL
RECONFIGURATION,[2]TRANSPORT CHANNEL RECONFIGURATION,[3]RADIO
BEARER RECONFIGURATION,[4]RADIO BEARER SETUP,[5]RADIO BEARER
RELEASE message. Accordingly, UE may send [1]PHYSICAL CHANNEL
RECONFIGURATION COMPLETE,[2]PHYSICAL CHANNEL RECONFIGURATION
FAILURE,[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,[4]
TRANSPORT CHANNEL RECONFIGURATION FAILURE,[5]RADIO BEARER
RECONFIGURATION COMPLETE,[6]RADIO BEARER RECONFIGURATION
FAILURE message to RNC as a response. This counter complies with section "8.2.2
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.
Issue 03 (2015-06-30)

1831
BSC6900 UMTS
Figure 1-793 HSUPA Serving cell change procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2E.SuccOutIur
WRFD-01061204
HSUPA Mobility
Management
Number of HSUPA Serving Cell Change Attempts Due to inter-RNC Hard

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67195488
VS.HSUPA.HHO.E2E.AttOutIur

Cell Change Attempts Due to
inter-RNC Hard Handover
without Channel Change for
Cell

1832
BSC6900 UMTS
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. This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS
25.331 (v9.2.1).
Measurement point
This measurement is triggered at point A as shown in Figure. The procedure shown in the figure
takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When the RNC
sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE, the RNC measure
the item in the serving cell before hard handover on condition that this hard handover is
performed over the Iur interface from EDCH to EDCH.
Formula
None
Issue 03 (2015-06-30)

1833
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2E.AttOutIur
WRFD-01061204
HSUPA Mobility
Management
Number of Successful HSUPA Serving Cell Changes Due to Intra-Frequency Hard

Counters
Counter ID
Counter Name
Counter Description
67192371
VS.HSUPA.HHO.E2E.SuccOutIntraFreq
HSUPA Serving Cell
Changes Due to IntraFrequency Hard Handover
Cell
67192373
VS.HSUPA.HHO.E2E.SuccOutInterFreq
HSUPA Serving Cell
Changes Due to InterFrequency Hard Handover
Cell
Description
These counters provide the number of successful HSUPA serving cell changes due to E-DCHto-E-DCH intra-frequency and inter-frequency hard handover. For DC-HSUPA users, these
counters are measured only in the cell with the primary carrier. The preceding counters comply
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
Issue 03 (2015-06-30)

1834
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2E.SuccOutIntraFreq
WRFD-01061204
HSUPA Mobility
Management
VS.HSUPA.HHO.E2E.SuccOutInterFreq
WRFD-01061204
HSUPA Mobility
Management

1835
BSC6900 UMTS
Number of HSUPA Serving Cell Change Attempts Due to Intra-Frequency Hard

Counters
Counter ID
Counter Name
Counter Description
67192372
VS.HSUPA.HHO.E2E.AttOutIntraFreq

Handover without Channel
Change for Cell
Description
These counters provide the number of HSUPA serving cell change attempts due to E-DCH-toE-DCH intra-frequency and inter-frequency hard handover. For DC-HSUPA users, these
counters are measured only in the cell with the primary carrier. This counter complies with
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.
Issue 03 (2015-06-30)

1836
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2E.AttOutIntraFreq
WRFD-01061204
HSUPA Mobility
Management
Number of HSUPA Serving Cell Change Attempts Due to Inter-Frequency Hard

Counters
Counter ID
Counter Name
Counter Description
67192374
VS.HSUPA.HHO.E2E.AttOutInterFreq

Handover without Channel
Change for Cell
Description
due to inter-frequency hard handover without channel change for cell.For DC-HSUPA users,
this counter is measured only in the cell with the primary carrier. This counter complies with
Measurement point
This measurement is triggered at point A shown in the figure. When the RNC sends a PHYSICAL
CHANNEL RECONFIGRATION message or a TRANSPORT CHANNEL
RECONFIGRATION message or a RADIO BEARER RECONFIGRATION message or a
RADIO BEARER SETUP message or a RADIO BEARER RELEASE message to the UE, the
RNC measures the item in the HSUPA serving cell before the hard handover if an EDCH-toEDCH inter-frequency hard handover is performed.
Issue 03 (2015-06-30)

1837
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2E.AttOutInterFreq
WRFD-01061204
HSUPA Mobility
Management
Number of Successful HSUPA Intra-Frequency Hard Handovers for Cell(EDCH to

DCH)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192472
VS.HSUPA.HHO.E2D.SuccOutIntraFreq
HSUPA Intra-Frequency
(EDCH to DCH)

1838
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192474
VS.HSUPA.HHO.E2D.SuccOutInterFreq
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
only in the cell with the primary carrier. The preceding counters comply with section "8.2.2
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
Unit
None
Issue 03 (2015-06-30)

1839
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2D.SuccOutIntraFreq
WRFD-01061204
HSUPA Mobility
Management
VS.HSUPA.HHO.E2D.SuccOutInterFreq
WRFD-01061204
HSUPA Mobility
Management
Number of HSUPA Hard Handover Attempts for Cell(EDCH to DCH)

Counters
Counter ID
Counter Name
Counter Description
67192473
VS.HSUPA.HHO.E2D.AttOutIntraFreq
Number of HSUPA IntraFrequency Hard Handover

Attempts for Cell(EDCH to
DCH)
67192475
VS.HSUPA.HHO.E2D.AttOutInterFreq
Number of HSUPA InterFrequency 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
counters are measured only in the cell with the primary carrier. The preceding counters comply
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.
Issue 03 (2015-06-30)

1840
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2D.AttOutIntraFreq
WRFD-01061204
HSUPA Mobility
Management
VS.HSUPA.HHO.E2D.AttOutInterFreq
WRFD-01061204
HSUPA Mobility
Management
Number of Channel Conversion Attempts According to Different Channel Switch

Type for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192480
VS.HSUPA.E2F.Att
Number of Channel
EDCH to FACH for HSUPA
Service for Cell

1841
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
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. The preceding counters
Measurement point
This measurement is performed at point A shown in the figure. The RNC sends a RADIO
BEARER 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
Issue 03 (2015-06-30)

1842
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
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
Number of Successful Handovers Between Different Channel Types for Cell

Counters
Counter ID
Counter Name
Counter Description
67192481
VS.HSUPA.E2F.Succ
EDCH to FACH for HSUPA
Service for Cell
67192470
VS.HSUPA.E2D.Succ
EDCH to DCH for HSUPA
Service for Cell
67192476
VS.HSUPA.D2E.Succ
DCH to EDCH for HSUPA
Service for Cell
67192483
VS.HSUPA.F2E.Succ
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
the primary carrier. The preceding counters comply with section "8.2.2 Reconfiguration
Issue 03 (2015-06-30)

1843
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
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

1844
BSC6900 UMTS
Mean Uplink Throughput of single HSUPA MAC-d Flow

Counters
Counter ID
Counter Name
Counter Description
67203932
Mean Uplink Throughput of

single HSUPA MAC-d Flow
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
67192487
VS.HSUPA.MeanChThroug
hput.Times
Duration of HSUPA MAC-D

Flow Receiving Data for Cell
Description
This counter provides the mean uplink throughput of single HSUPA MAC-d flows in HSUPA
cells in active set.For DC-HSUPA users, this counter is measured only in the primary cell based
on the total throughput on the primary and secondary carriers.
Measurement point
When data is received in HSUPA active cells, the RNC measures the total data transfer time of
all the UEs and the total number of bits received in the cell. At the end of the measurement
period, the RNC divides the total number of bits by the total data transfer time to obtain the mean
uplink throughput of MAC-d flows at the RLC layer. Note that the total number of bits measured
excludes RLC headers and retransmitted data. In the case of a soft handover, the RNC measures
the number of bits received after combining in all cells of the active set.
Formula
VS.HSUPA.MeanChThroughput = {8}*[VS.HSUPA.MeanChThroughput.TotalBytes]/
[VS.HSUPA.MeanChThroughput.Times]
Unit
kbit/s
Issue 03 (2015-06-30)

1845
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010612
HSUPA Introduction
Package
Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow

Counters
Counter ID
Counter Name
Counter Description
67192486
hput.TotalBytes
Number of Total Bytes

Received in Uplink of
HSUPA MAC-d Flow for
Cell
Description
This counter provides the number of total bytes received in uplink of all the HSUPA MAC-d
flows in a cell.For DC-HSUPA users, this counter is measured only in the primary cell based
on the total number of bytes received on the primary and secondary carriers.
Measurement point
When data is received in HSUPA active cells, the RNC measures the number of total bytes
received in the uplink 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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
hput.TotalBytes
WRFD-010612
HSUPA Introduction
Package

1846
BSC6900 UMTS
Mean Uplink Throughput of HSUPA MAC-d Flow of BE Service for Golden

Subscriber
Counters
Counter ID
Counter Name
Counter Description
67204513
VS.HSUPA.GoldenBeMeanChThroughput

HSUPA MAC-d Flow of BE
Service for Golden
Subscriber for Cell
67204514
VS.HSUPA.SilverBeMeanChThroughput

Service for Silver Subscriber
for Cell
67204515
VS.HSUPA.CopperBeMeanChThroughput

Service for Copper
Subscriber for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
67194890
VS.HSUPA.CopperBeMean
ChThroughput.Times
Duration of Copper BE
HSUPA MAC-D Flow
Receiving Data for Cell
67194874
VS.HSUPA.GoldenBeMean
ChThroughput.Times
Duration of Golden BE
HSUPA MAC-D Flow
67194876
VS.HSUPA.SilverBeMeanC
hThroughput.Times
Duration of Silver BE
HSUPA MAC-D Flow
Description
These counters provide the average UL throughput of all the HSUPA MAC-d flows of differentpriority BE services in an HSUPA serving cell. For DC-HSUPA users, these counters are
measured only in the primary cell based on the total number of bytes received on the primary
and secondary carriers.
Measurement point
When BE services for golden, silver, and copper users are carried in an HSUPA serving cell,
the RNC measures the number of total bytes received in the uplink of the MAC-d flow of the
Issue 03 (2015-06-30)

1847
BSC6900 UMTS
BE service at the RLC layer and the time for data transmission for different users. At the end of
the measurement period, the average throughput of users of a priority, (for example, golden
users) is obtained by dividing the number of total bytes for the golden users by the total
transmission time for the golden users. RLC headers and retransmitted data are not considered.
Formula
VS.HSUPA.GoldenBeMeanChThroughput = {8}*
[VS.HSUPA.GoldenBeMeanChThroughput.TotalBytes]/
[VS.HSUPA.GoldenBeMeanChThroughput.Times]
VS.HSUPA.SilverBeMeanChThroughput = {8}*
[VS.HSUPA.SilverBeMeanChThroughput.TotalBytes]/
[VS.HSUPA.SilverBeMeanChThroughput.Times]
VS.HSUPA.CopperBeMeanChThroughput = {8}*
[VS.HSUPA.CopperBeMeanChThroughput.TotalBytes]/
[VS.HSUPA.CopperBeMeanChThroughput.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.GoldenBeMeanChThroughput
WRFD-01061008

WRFD-020806

on SPI Weight
VS.HSUPA.SilverBeMeanChThroughput
WRFD-01061008
WRFD-020806

on SPI Weight
VS.HSUPA.CopperBeMeanChThroughput
WRFD-01061008
WRFD-020806

on SPI Weight
Issue 03 (2015-06-30)

1848
BSC6900 UMTS
Number of Total Bytes Received in Uplink of HSUPA MAC-d Flow of BE Service

for Golden Subscriber
Counters
Counter ID
Counter Name
Counter Description
67194873

Service for Golden
Subscriber for Cell
67194875

Service for Silver Subscriber
for Cell
67194889

Service for Copper
Subscriber for Cell
Description
These counters provide the number of total bytes received in the uplink of all the HSUPA MACd flows of different-priority BE services in an HSUPA serving cell. For DC-HSUPA users, these
counters are measured only in the primary cell based on the total number of bytes received on
the primary and secondary carriers.
Measurement point
When BE services for golden, silver, and copper users are carried in an HSUPA serving cell,
the RNC separately measures the number of total bytes received in the uplink of the MAC-d
flow of different-priority BE service at the RLC layer. RLC headers and retransmitted data are
not considered.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

1849
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-020806

on SPI Weight
WRFD-01061008
WRFD-020806

on SPI Weight
WRFD-01061008
WRFD-020806

on SPI Weight
Number of inter-RNC HSUPA Hard Handover Attempts for Cell(EDCH to DCH)

Counters
Counter ID
Counter Name
Counter Description
73403766
VS.HSUPA.HHO.E2D.AttOutIur
Number of inter-RNC
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
a RADIO BEARER RECONFIGURATION message to a UE, the RNC measures this item in
Issue 03 (2015-06-30)

1850
BSC6900 UMTS
the serving cell before hard handover if an inter RNC hard handover from the EDCH to the DCH
is performed.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2D.AttOutIur
WRFD-01061204
HSUPA Mobility
Management
Number of Successful inter-RNC HSUPA Hard Handovers for Cell(EDCH to DCH)

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73403767
VS.HSUPA.HHO.E2D.SuccOutIur
Number of Successful interRNC HSUPA Hard

Handovers for Cell(EDCH to
DCH)

1851
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
Issue 03 (2015-06-30)

1852
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HHO.E2D.SuccOutIur
WRFD-01061204
HSUPA Mobility
Management
Number of Successful HSUPA 16QAM RAB Establishments for cell

Counters
Counter ID
Counter Name
Counter Description
73403795
VS.HSUPA.RAB.
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. This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v9.5.1).
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.
Issue 03 (2015-06-30)

1853
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.
16QAM.SuccEstab
WRFD-010694
UL 16QAM

1854
BSC6900 UMTS
Number of HSUPA 16QAM RABs Abnormal Released for cell

Counters
Counter ID
Counter Name
Counter Description
73403796
VS.HSUPA.RAB.AbnormRel.16QAM
Number of HSUPA 16QAM

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
the cell with the primary carrier. This counter complies with section "8.2 RAB Assignment" in
3GPP TS 25.413 (v9.5.1).
Measurement point
Optimization" , reference to 3GPP TS 25.413),the RNC measures the items in the HSUPA
serving cell if is a HSUPA service using 16QAM.
Issue 03 (2015-06-30)

1855
BSC6900 UMTS
Generated Signalling Connection Release","Successful Relocation" or "Network
Generated Signalling Connection Release","Successful Relocation" or "Network
Issue 03 (2015-06-30)

1856
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.AbnormRel.16QAM
WRFD-010694
UL 16QAM
Number of HSUPA 16QAM RABs Normal Released for cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73403797
16QAM

cell

1857
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. This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v9.5.1).
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.
Issue 03 (2015-06-30)

1858
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
16QAM
WRFD-010694
UL 16QAM
Number of HSUPA 16QAM RAB Setup Attempts for cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73403794
VS.HSUPA.RAB.
16QAM.AttEstab

RAB Setup Attempts for cell

1859
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
Issue 03 (2015-06-30)

1860
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.
16QAM.AttEstab
WRFD-010694
UL 16QAM
Number of HSUPA RABs Abnormal Released due to RF Failures for Cell

Counters
Counter ID
Counter Name
Counter Description
73391136
VS.HSUPA.RAB.AbnormR
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". This counter complies with section
"8.4 Iu Release Request" in 3GPP TS 25.413 (v9.5.1).
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","UE Generated Signalling Connection Release",
"Successful Relocation", or "Network Optimization", this counter is measured in the HSUPA
serving cell if HSUPA services are enabled. For details about the preceding cause values, see
3GPP TS 25.413.
Issue 03 (2015-06-30)

1861
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
3GPP TS 25.413.
Issue 03 (2015-06-30)

1862
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
3GPP TS 25.413.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.RF
WRFD-01061206

WRFD-010632

HSUPA
Issue 03 (2015-06-30)

1863
BSC6900 UMTS
Number of HSUPA UEs with Various Categories in a Cell

Counters
Counter ID
Counter Name
Counter Description
67204266
VS.HSUPA.UE.Mean.CAT
1.4

Cell
67204267
5

UEs with Category 5 in a Cell
67204268
6

67204269
7

67193599
VS.HSUPA.UE.Max.CAT1.
4
Maximum Number of
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
67193605
Maximum Number of
in a Cell
67193608
Maximum Number of
in a Cell
73441235
8

73424186
Maximum Number of
in a Cell
73441236
9

73424189
Maximum Number of
in a Cell
specific formulas.
Issue 03 (2015-06-30)

1864
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394367
1.4.DENO

Cell(Denominator)
73394366
1.4.NUM

Cell(Numerator)
73394369
5.DENO

(Denominator)
73394368
5.NUM

(Numerator)
73394371
6.DENO

(Denominator)
73394370
6.NUM

(Numerator)
73394373
7.DENO

(Denominator)
73394372
7.NUM

(Numerator)
73424188
8.DENO

(Denominator)
73424187
8.NUM

(Numerator)
73424191
9.DENO

(Denominator)
73424190
9.NUM

(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
Issue 03 (2015-06-30)

1865
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. According to 3GPP TS 25.331, the UE
capability indication IE is optional during the RRC connection setup procedure. If the UE does
not report its E-DCH category during this procedure, the RNC uses category 1 by default. In
this case, the value of this counter is greater than the actual value.
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
1.4
WRFD-01061201
HSUPA UE Category
Support
5
WRFD-01061201
HSUPA UE Category
Support
6
WRFD-01061201
HSUPA UE Category
Support
7
WRFD-01061201
HSUPA UE Category
Support

1866
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HSUPA.UE.Max.CAT1.
4
WRFD-01061201
HSUPA UE Category
Support
WRFD-01061201
HSUPA UE Category
Support
WRFD-01061201
HSUPA UE Category
Support
WRFD-01061201
HSUPA UE Category
Support
8
WRFD-01061201
HSUPA UE Category
Support
WRFD-01061201
HSUPA UE Category
Support
9
WRFD-01061201
HSUPA UE Category
Support
WRFD-01061201
HSUPA UE Category
Support
Number of EDCH MAC-d Flow Setup Requests for Cell

Counters
Counter ID
Counter Name
Counter Description
73393829
VS.HSUPA.MACD.AttSetup
Number of EDCH MAC-d

Flow Setup Requests for Cell
Description
This counter provides the number of EDCH MAC-d flow setup requests in the cell.For DCHSUPA users, this counter is measured only in the cell with the primary carrier.This counter
complies with section "8.2.17 Radio Link Setup","8.3.1 Radio Link Addition","8.3.2
Synchronised Radio Link Reconfiguration Preparation" in 3GPP TS 25.433 (v10.10.0).
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.
Issue 03 (2015-06-30)

1867
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 MACd Flows To Add" IE.
The measurement can also be triggered at point A as shown in the figure. When the RNC sends
the NodeB a RADIO LINK ADDITION REQUEST message, this counter is measured in the
HSUPA cell where the new E-DCH RL is to be added if the message indicates that an E-DCH
RL needs to be added.
Issue 03 (2015-06-30)

1868
BSC6900 UMTS
Figure 1-816 Radio link add procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.MACD.AttSetup
WRFD-010612
HSUPA Introduction
Package
Number of Failed HSUPA Service Establishments Due to Insufficiency of

Different Resources
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393832
VS.HSUPA.RAB.FailEstab.
ULPower.Cong
Number of Failed HSUPA

to UL Power Insufficiency
for Cell

1869
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73393833
ULIUBBand.Cong

to UL Iub Bandwidth
73393834
ULCE.Cong

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.The preceding counters complies
Measurement point
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-817 Failed RAB establishments due to resource insufficiency
Formula
None
Issue 03 (2015-06-30)

1870
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ULPower.Cong
WRFD-01061206

WRFD-010632

HSUPA
ULIUBBand.Cong
WRFD-01061206
WRFD-010632

HSUPA
ULCE.Cong
WRFD-01061206
WRFD-010632

HSUPA
Average uplink throughput of the Traffic PS Conversational beared on E-DCH for

cell
Counters
Counter ID
Counter Name
Counter Description
73410485
VS.PS.Conv.Kbps.EDCH
Average uplink throughput

of the Traffic PS
Conversational beared on EDCH for cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393915
VS.PS.Conv.Times.EDCH
Duration of PS
Conversational HSUPA
MAC-D Flow Receiving
Data for Cell

1871
BSC6900 UMTS
Description
This measurement item takes statistics of the average uplink throughput of the Traffic PS
Conversational beared on E-DCH in the cell.
Measurement point
The RNC measures all UL traffic volume (the RLC headers and retransmitted data are not
included) (unit: bit) and duration (unit: ms) of the PS conversational service beared on EDCH
in the cell of the RLC layer. At the end of the measurement period, the RNC calculates average
bit rate.
Formula
VS.PS.Conv.Kbps.EDCH = {8}*[VS.PS.Conv.Traffic.EDCH]/[VS.PS.Conv.Times.EDCH]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Conv.Kbps.EDCH
WRFD-010617
WRFD-010501
Number of uplink bytes of Transport Blocks of Traffic PS Conversational beared

on E-DCH for cell
Counters
Counter ID
Counter Name
Counter Description
73393914
VS.PS.Conv.Traffic.EDCH
Number of uplink bytes of

E-DCH for cell
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.
Issue 03 (2015-06-30)

1872
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Conv.Traffic.EDCH
WRFD-010617
WRFD-010501
Counters Related to the Number of Transfers Between Small Retransmission and

Large Retransmission for HSUPA 2ms TTI Users or HSUPA 10ms TTI Users
Counters
Counter ID
Counter Name
Counter Description
73393956
VS.HSUPA.RsnSmall2Larg
e.TTI2ms
Number of Times that

HSUPA 2ms TTI Users
Transfer from Small
Retransmission to Large
Retransmission for Cell
73393957
e.TTI10ms

HSUPA 10ms TTI Users
Transfer from Small
Retransmission to Large
73393958
VS.HSUPA.RsnLarge2Smal
l.TTI2ms

HSUPA 2ms TTI Users
Transfer from Large
Retransmission to Small
73393959
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
Issue 03 (2015-06-30)

1873
BSC6900 UMTS
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-818 Adaptive retransmission procedure
The measurement can also be triggered at point B as shown in the figure. In the OLPC_MODIFY
scenario, only small retransmission can be used. In this case, the corresponding counter is
measured based on the TTI of the user when the user in large retransmission mode receives an
OLPC_MODIFY message.
Figure 1-819 Retransmission of OLPC procedure
Issue 03 (2015-06-30)

1874
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
e.TTI2ms
WRFD-010641
HSUPA Adaptive
Transmission
e.TTI10ms
WRFD-010641
HSUPA Adaptive
Transmission
l.TTI2ms
WRFD-010641
HSUPA Adaptive
Transmission
l.TTI10ms
WRFD-010641
HSUPA Adaptive
Transmission
Number of TTI Switch Attempts During RB Reconfiguration for Cell

Counters
Counter ID
Counter Name
Counter Description
73393984
VS.HSUPA.TTI2to10.Att
Number of TTI Switch

Attempts During RB
(2ms to 10ms)
73393986
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 DCHSUPA users, this counter is measured only in the cell with the primary carrier.The preceding
counters complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v10.13.0).
Issue 03 (2015-06-30)

1875
BSC6900 UMTS
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
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010690

Based on Coverage
WRFD-01061404
HSUPA 2ms/10ms TTI

Handover
Issue 03 (2015-06-30)

1876
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010690

Based on Coverage
WRFD-01061404
HSUPA 2ms/10ms TTI

Handover
Number of Successful TTI Switches During RB Reconfiguration for Cell

Counters
Counter ID
Counter Name
Counter Description
73393985
VS.HSUPA.TTI2to10.Succ

Switches During RB
(2ms to 10ms)
73393987

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.The preceding counters complies with section "8.2.2 Reconfiguration procedures" in
3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

1877
BSC6900 UMTS
Figure 1-821 RB reconfig procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010690

Based on Coverage
WRFD-01061404
HSUPA 2ms/10ms TTI

Handover
WRFD-010690
WRFD-01061404

Based on Coverage
HSUPA 2ms/10ms TTI
Handover
Issue 03 (2015-06-30)

1878
BSC6900 UMTS
Number of HSUPA 16QAM UEs in a Cell

Counters
Counter ID
Counter Name
Counter Description
73410507
VS.HSUPA.
16QAM.UE.Mean.Cell

16QAM UEs in a Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73394088
VS.HSUPA.
16QAM.UE.Mean.Cell.DENO

16QAM UEs in a Cell
(Denominator)
73394087
VS.HSUPA.
16QAM.UE.Mean.Cell.NU
M

16QAM UEs in a Cell
(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)
Formula
VS.HSUPA.16QAM.UE.Mean.Cell = [VS.HSUPA.16QAM.UE.Mean.Cell.NUM]/
[VS.HSUPA.16QAM.UE.Mean.Cell.DENO]
Unit
None
Issue 03 (2015-06-30)

1879
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.
16QAM.UE.Mean.Cell
WRFD-010694
UL 16QAM
Number of HSUPA Boosting UEs in a Cell

Counters
Counter ID
Counter Name
Counter Description
73441120
VS.HSUPA.Boosting.UE.M
ean.Cell
Number of UEs Supporting

E-DPCCH Boosting for Cell
Description
This counter provides the average number of UEs in an active set of HSUPA E-DCH cells that
support E-DPCCH boosting.
Measurement point
UEs supporting E-DPCCH boosting in an HSUPA cell are sampled (sampling periodicity is 5
seconds) at a certain interval. At the end of a measurement period, this counter measured at each
sampling site is obtained by dividing the accumulated number of the UEs by the number of
samples.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPA.Boosting.UE.M
ean.Cell
WRFD-010697
E-DPCCH Boosting

1880
BSC6900 UMTS
Number of UEs Supporting E-DPCCH Boosting and CPC for Cell

Counters
Counter ID
Counter Name
Counter Description
73441121
VS.HSUPA.BoostingCPC.U
E.Mean.Cell
Number of UEs Supporting

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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPA.BoostingCPC.U
E.Mean.Cell
WRFD-010697
E-DPCCH Boosting

1881
BSC6900 UMTS
Number of RABs Abnormally Released for PS HSUPA Services during the State
Transition from CELL_DCH to CELL_PCH or URA_PCH for Cell
Counters
Counter ID
Counter Name
Counter Description
73422168
el.E2P
Number of RABs
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 DCHSUPA users, this counter is measured only in the cell with the primary carrier.This counter
complies with section "8 RANAP Procedures" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

1882
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",
Issue 03 (2015-06-30)

1883
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",
Issue 03 (2015-06-30)

1884
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.E2P
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-010612
HSUPA Introduction
Package
Issue 03 (2015-06-30)

1885
BSC6900 UMTS
Number of HSUPA Boosting RAB Setup Attempts for Cell

Counters
Counter ID
Counter Name
Counter Description
73423359
VS.HSUPA.RAB.Boosting.
AttEstab
Number of HSUPA Boosting

RAB Setup Attempts for Cell
Description
This counter provides the number of setup attempts for HSUPA RABs with the E-DPCCH
Boosting feature enabled in the serving cell.
Measurement point
the 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.
Issue 03 (2015-06-30)

1886
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
AttEstab
WRFD-010697
E-DPCCH Boosting
Number of Successful HSUPA Boosting RAB Setups for Cell

Counters
Counter ID
Counter Name
Counter Description
73423360
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.
Issue 03 (2015-06-30)

1887
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
SuccEstab
WRFD-010697
E-DPCCH Boosting

1888
BSC6900 UMTS
Number of Abnormally Released HSUPA Boosting RABs for Cell

Counters
Counter ID
Counter Name
Counter Description
73423361
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","UE
Optimization", for details, see 3GPP TS 25.413), then this counter is measured in the HSUPA
serving cell that the UE camps on if the RAB is intended for HSUPA services and the E-DPCCH
Boosting feature is enabled.
Issue 03 (2015-06-30)

1889
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","UE Generated
Signalling Connection Release", "Successful Relocation", or "Network Optimization", for
details, see 3GPP TS 25.413), then this counter is measured in the HSUPA serving cell that the
UE camps on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature
is enabled.
The measurement is also triggered at point A as shown in Figure 3. When a failure occurs, the
RNC sends the CN an IU RELEASE REQUEST message. After receiving from the CN an IU
RELEASE COMMAND message, the RNC responds with an IU RELEASE COMPLETE
message. If the IU RELEASE COMMAND message from the CN contains a cause value of
abnormal release (a cause value except "User Inactivity", "Normal Release","UE Generated
Signalling Connection Release", "Successful Relocation", or "Network Optimization", for
details, see 3GPP TS 25.413), then this counter is measured in the HSUPA serving cell that the
UE camps on if the RAB is intended for HSUPA services and the E-DPCCH Boosting feature
is enabled.
Issue 03 (2015-06-30)

1890
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.Boosting
WRFD-010697
E-DPCCH Boosting
Number of Normally Released HSUPA Boosting RABs for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423362
Boosting
Number of Normally
Released HSUPA Boosting
RABs for Cell

1891
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.
Issue 03 (2015-06-30)

1892
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Boosting
WRFD-010697
E-DPCCH Boosting
Number of DC-HSUPA RAB Setup Attempts for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424115
VS.HSUPA.RAB.DC.AttEstab
Number of DC-HSUPA
RAB Setup Attempts for Cell

1893
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.This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
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
Issue 03 (2015-06-30)

1894
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.DC.AttEstab
WRFD-140204
DC-HSUPA
Number of Successful DC-HSUPA RAB Setups for Cell

Counters
Counter ID
Counter Name
Counter Description
73424116
VS.HSUPA.RAB.DC.SuccEstab
Number of Successful DCHSUPA RAB Setups for Cell
Description
This counter provides the number of successful DC-HSUPA RAB setups in the serving cell
where the DC-HSUPA feature is enabled. This counter is measured only in the cell with the
primary carrier.This counter complies with section "8.2 RAB Assignment" in 3GPP TS 25.413
(v10.10.0).
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.
Issue 03 (2015-06-30)

1895
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.DC.SuccEstab
WRFD-140204
DC-HSUPA

1896
BSC6900 UMTS
Number of DC-HSUPA RABs Normally Released for Cell

Counters
Counter ID
Counter Name
Counter Description
73424117
VS.HSUPA.RAB.DC.Norm
Rel
Number of DC-HSUPA
Cell
Description
This counter provides the number of DC-HSUPA RABs normally released by the RNC in the
serving cell where the DC-HSUPA feature is enabled. This counter is measured only in the cell
with the primary carrier.This counter complies with section "8.2 RAB Assignment" in 3GPP TS
25.413 (v10.10.0).
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.
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
Issue 03 (2015-06-30)

1897
BSC6900 UMTS
to the CN. This counter is incremented by one in the cell with the primary carrier if the following
conditions are met:
The cause in the RAB ASSIGNMENT REQUEST message is User Inactivity, Normal Release,
Successful Relocation, or Network Optimization, or the RNC has sent a release request with the
cause of User Inactivity, Network Optimization, or UE Generated Signalling Connection
Release before the RNC receives the RAB ASSIGNMENT REQUEST message.
The RAB carries DC-HSUPA services and the DC-HSUPA feature is enabled in the serving
cell.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.DC.Norm
Rel
WRFD-140204
DC-HSUPA

1898
BSC6900 UMTS
Number of DC-HSUPA RABs Abnormally Released for Cell

Counters
Counter ID
Counter Name
Counter Description
73424118
VS.HSUPA.RAB.DC.AbnormRel
Number of DC-HSUPA
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
with the primary carrier.This counter complies with section "8.2 RAB Assignment" in 3GPP TS
25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

1899
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 DCHSUPA services, then this counter is incremented by one in the cell with the primary carrier.
For details about the causes indicating a normal RAB release, see 3GPP TS 25.413.
occurs, the RNC sends the CN an IU RELEASE REQUEST message. If the RNC receives from
the CN an IU RELEASE COMMAND message with a cause other than User Inactivity, Normal
Release, Successful Relocation, or Network Optimization and if the RAB carries DC-HSUPA
services, then this counter is incremented by one in the cell with the primary carrier. For details
about causes indicating a normal RAB release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

1900
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.DC.AbnormRel
WRFD-140204
DC-HSUPA
Mean Number of DC-HSUPA Users in the Cell with the Primary Carrier
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424192
VS.HSUPA.DC.PRIM.UE.
Mean.Cell
Mean Number of DCHSUPA Users in the Cell

with the Primary Carrier

1901
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73441238
VS.HSUPA.DC.SEC.UE.M
ean.Cell
Mean Number of DCHSUPA Users in the Cell

with the Secondary Carrier
specific formulas.
Counter ID
Counter Name
Counter Description
73424194
Mean.Cell.DENO

UEs in a primary Cell
(Denominator)
73424193
Mean.Cell.NUM

UEs in a primary Cell
(Numerator)
73424196
ean.Cell.DENO

UEs in supplementary carrier
Cell(Denominator)
73424195
ean.Cell.NUM

UEs in supplementary carrier
Cell(Numerator)
Description
These counters measures the mean number of DC-HSUPA users who use a cell as the primary
carrier and the cell is in the primary carrier active set and the mean number of DC-HSUPA users
who use a cell as the secondary carrier and the cell is in the secondary carrier active set,
respectively. If the RNC supports the DC-HSUPA independent active set function, but the DCHSUPA independent active set function is not enabled in a cell under the RNC, the cell can join
the primary or secondary carrier active set of a DC-HSUPA user when the following condition
is met: 2 ms TTI, F-DPCH, and uplink enhanced L2 are supported. In this case, these counters
measure the number of DC-HSUPA users who use a cell as the primary carrier and the cell is
in the primary carrier active set or the number of DC-HSUPA users who use a cell as the
secondary carrier and the cell is in the secondary carrier active.
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:
Issue 03 (2015-06-30)

1902
BSC6900 UMTS
Accumulated Number of DC-HSUPA Users in the Cell with the Secondary Carrier at the
sampling points in the measurement period (numerator)
Formula
VS.HSUPA.DC.PRIM.UE.Mean.Cell = [VS.HSUPA.DC.PRIM.UE.Mean.Cell.NUM]/
[VS.HSUPA.DC.PRIM.UE.Mean.Cell.DENO]
VS.HSUPA.DC.SEC.UE.Mean.Cell = [VS.HSUPA.DC.SEC.UE.Mean.Cell.NUM]/
[VS.HSUPA.DC.SEC.UE.Mean.Cell.DENO]
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Mean.Cell
WRFD-140204
DC-HSUPA
ean.Cell
WRFD-140204
DC-HSUPA
Number of HSUPA 2 ms TTI UEs in a Cell

Counters
Counter ID
Counter Name
Counter Description
73441239
VS.HSUPA.UE.Mean.TTI2
ms

2 ms TTI UEs in a Cell
73424199
VS.HSUPA.UE.Max.TTI2m
s
Maximum Number of
HSUPA 2 ms TTI UEs in a
Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424198
ms.DENO

(Denominator)

1903
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73424197
ms.NUM

(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.
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
Counter Name
Feature ID
Feature Name
ms
WRFD-010612
HSUPA Introduction
Package
WRFD-01061403
HSUPA 2ms TTI

VS.HSUPA.UE.Max.TTI2m
s
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
HSUPA 2ms TTI
Issue 03 (2015-06-30)

1904
BSC6900 UMTS
Number of HSUPA 10 ms TTI UEs in a Cell

Counters
Counter ID
Counter Name
Counter Description
73441240
0ms
Average number of HSUPA

73424202
VS.HSUPA.UE.Max.TTI10
ms
Maximum Number of
HSUPA 10 ms TTI UEs in a
Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73424201
0ms.DENO

(Denominator)
73424200
0ms.NUM

(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
Issue 03 (2015-06-30)

1905
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
0ms
WRFD-010612
HSUPA Introduction
Package
VS.HSUPA.UE.Max.TTI10
ms
WRFD-010612
HSUPA Introduction
Package
Number of Successful RAB Establishments Initiated by HSUPA 2 ms UEs with a

10 ms TTI in a Cell with Various Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424205
VS.HSUPA.RABEstabTTI1
0ms.AdmCE.Succ

Establishments Initiated by
HSUPA 2 ms UEs with a 10
ms TTI Due to Congestion of
Admitted CEs in a Cell
73424206
0ms.ResRTWP.Succ

ms TTI Due to RTWP
73424207
0ms.ResUsedCE.Succ

ms TTI Due to Congestion of
Occupied CEs in a Cell
73424208
0ms.ResIUB.Succ

ms TTI Due to Iub Resource
73424967
0ms.Cover.Succ

ms TTI Due to Limited
Uplink Coverage

1906
BSC6900 UMTS
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.These counters comply with section "8.2
Measurement point
At measurement point B shown in the following figure, the RNC receives an RAB
ASSGINMENT REQUEST message from the CN and an HSUPA 2 ms UE is configured with
a 10 ms TTI even though conditions on 2 ms TTI have been met. After an RB is set up and the
RNC sends an RAB ASSIGNMENT RESPONSE message to the CN, a specific counter in the
serving cell is increased by one and this specific counter is determined by the congestion cause.
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

1907
BSC6900 UMTS
Number of Abnormal RAB Releases for Cell During State Transition of HSUPA
UEs to CELL/URA_PCH
Counters
Counter ID
Counter Name
Counter Description
73425950
VS.HSUPA.RAB.AbnormRel.16QAM2P

State Transition of HSUPA
+16QAM UEs to CELL/
URA_PCH
73425951
el.DC2P

State Transition of DCHSUPA UEs to CELL/
URA_PCH
Description
These counters provide the number of abnormal RAB releases during the state transition of
HSUPA UEs to CELL_PCH or URA_PCH in the serving cell. For DC-HSUPA UEs, this counter
is measured only in the primary carrier cell.These counters comply with section "8.2 RAB
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","UE Generated Signalling Connection Release", "Successful Relocation", or "Network
Optimization", this counter is increased by one in the serving cell where the UE camps. For
details on cause values indicating RAB releases, see 3GPP TS 25.413.
Figure 1-840 The release process of RAB
Issue 03 (2015-06-30)

1908
BSC6900 UMTS
As shown by point A in figure 2, when an exception occurs, the RNC sends the CN a RAB
RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE
COMMAND message with the cause value being other than "User Inactivity", "Normal
Figure 1-841 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
Figure 1-842 The IU release process launched by RNC
Issue 03 (2015-06-30)

1909
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.RAB.AbnormRel.16QAM2P
WRFD-010694
UL 16QAM
el.DC2P
WRFD-140204
DC-HSUPA
Number of Normal RAB Releases of HSUPA UEs for Cell (All Scenarios)
Counters
Counter ID
Counter Name
Counter Description
73425952
16QAM.All

Releases of HSUPA
Scenarios)
73425953
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.These
counters comply with section "8.2 RAB Assignment" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

1910
BSC6900 UMTS
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.
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
receiving the RAB ASSIGNMENT REQUEST message.
Issue 03 (2015-06-30)

1911
BSC6900 UMTS
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.
Formula
None
Issue 03 (2015-06-30)

1912
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
16QAM.All
WRFD-010694
UL 16QAM
DC.All
WRFD-140204
DC-HSUPA
Sum of the Sampled RLC Throughput of HSUPA Users in a Cell

Counters
Counter ID
Counter Name
Counter Description
73443311
Sum of the Sampled RLC

Throughput of HSUPA Users
in a Cell
Description
This counter measures the sum of the sampled RLC throughput of all HSUPA users in a serving
cell. This counter is in units of kbit/s. This counter is used with the
VS.HSUPA.SamplesThroughput counter to calculate the average throughput of HSUPA users.
The formula is as follows: Average throughput of HSUPA users = VS.HSUPA.SumThroughput/
Measurement point
The RNC takes samples of the RLC throughput of all HSUPA users every 100 ms in a
measurement period. The sum of the sampled user throughput that is not 0 in a measurement
period is used as the value of this counter. The RLC header and retransmitted data are excluded.
For DC-HSUPA users, this counter is measured only in the primary cell based on the total
throughput on the primary and secondary carriers.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

1913
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010612
HSUPA Introduction
Package
Number of Times the RLC Throughput Is Not 0 for HSUPA Users in a Cell
Counters
Counter ID
Counter Name
Counter Description
73426996
Number of Times the RLC

Throughput Is Not 0 for
HSUPA Users in a Cell
Description
This counter measures the total number of sampling times the RLC throughput is not 0 for
HSUPA users in a serving cell.
Measurement point
The RNC takes samples of the RLC throughput of HSUPA users every 100 ms in a measurement
period and records the number of times the RLC throughput is not 0. The sum of the sampling
times in a measurement period is used as the value of this counter.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010612
HSUPA Introduction
Package

1914
BSC6900 UMTS
Average Number of UEs That Use the Flexible Power Control for Uplink Low-Rate
Data Transmission Feature for Cell
Counters
Counter ID
Counter Name
Counter Description
73444295
VS.HSUPA.FlexPCLowRat
e.UE.Mean.TTI2ms
Average Number of 2 ms TTI

UEs That Use the Flexible
Power Control for Uplink
Low-Rate Data
Transmission Feature When
Processing a Single HSUPA
BE Service for Cell
73444296
e.UE.Mean.TTI10ms
Average Number of 10 ms
TTI UEs That Use the
Flexible Power Control for
Uplink Low-Rate Data
Processing a Single HSUPA
BE Service for Cell
73444297
VS.MultiRAB.FlexPCLowR
ate.UE.Mean.TTI2ms
Average Number of 2 ms TTI

UEs That Use the Flexible
Power Control for Uplink
Low-Rate Data
Processing Combined
Services for Cell
73444298
ate.UE.Mean.TTI10ms
Average Number of 10 ms
TTI UEs That Use the
Uplink Low-Rate Data
Processing Combined
Services for Cell
Description
The preceding counters provide the average number of UEs that use the Flexible Power Control
for Uplink Low-Rate Data Transmission feature in a cell. These counters can reflect the feature
performance.
Issue 03 (2015-06-30)

1915
BSC6900 UMTS
Counter Name
Description
VS.HSUPA.FlexPCLowRate.UE.Mean.TTI
2ms
This counter provides the average number of

2 ms TTI UEs that use the Flexible Power
Control for Uplink Low-Rate Data
Transmission feature when processing a
single HSUPA BE service in a cell.
VS.HSUPA.FlexPCLowRate.UE.Mean.TTI
10ms

Transmission feature when processing a
single HSUPA BE service in a cell.
VS.MultiRAB.FlexPCLowRate.UE.Mean.T
TI2ms

Transmission feature when processing
combined services in a cell. Here, combined
services refer to the combined services that
contain a single AMR or PTT service and a
single HSUPA BE service.
VS.MultiRAB.FlexPCLowRate.UE.Mean.T
TI10ms

Transmission feature when processing
combined services in a cell. Here, combined
services refer to the combined services that
contain a single AMR or PTT service and a
single HSUPA BE service.
Measurement point
The RNC takes samples of the number of UEs that use the Flexible Power Control for Uplink
Low-Rate Data Transmission feature in a cell every 30 seconds in a measurement period. At the
end of the measurement period, the RNC obtains the value of this counter by dividing the
accumulated number by the number of sampling times. The RNC identifies such a UE when this
feature assigns appropriate values to outer loop power control parameters for an HSUPA BE
service of the UE.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1916
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
e.UE.Mean.TTI2ms
WRFD-160202

Uplink Low Data Rate
Transmission
e.UE.Mean.TTI10ms
WRFD-160202

Transmission
ate.UE.Mean.TTI2ms
WRFD-160202

Transmission
ate.UE.Mean.TTI10ms
WRFD-160202

Transmission
Average Number of 2ms TTI HSUPA UEs Processing a Single BE Service When the
Actual Uplink Power Load of the Cell Falls into a Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444320
VS.HSUPA.SingleBE.Mean
.TTI2ms.ULActualPowerLoad.0
Average Number of 2ms TTI

HSUPA UEs Processing a
Single BE Service When the
Actual Uplink Power Load of
the Cell Falls into Range 0 for
Cell
73444321

Cell
73444322

Cell

1917
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444323

Cell
73444324

Cell
Description
These counters provide the average number of 2 ms TTI HSUPA UEs processing a single BE
service when the actual uplink power load of a cell in an active set falls into a specific range.
These counters do not take DC-HSUPA UEs into account. The RNC calculates the actual uplink
power load of a cell based on the filtered RTWP, total uplink load, and required uplink load.
The actual uplink power load ranges are as follows: Range 0 [0, 40%) Range 1 [40%, 60%)
Range 2 [60%, 80%) Range 3 [80%, 95%) Range 4 [95%, 100%].
Measurement point
At an interval of 5 seconds, the RNC samples the number of 2 ms TTI HSUPA UEs processing
a single BE service when the actual uplink power load of the cell falls into a specific range. At
the end of a measurement period, the RNC divides the accumulated number by the number of
samples. Then, within the measurement period, the average number of such UEs when the actual
uplink power load of the cell falls into a specific range is obtained.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
Issue 03 (2015-06-30)

1918
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
Average Number of 10ms TTI HSUPA UEs Processing a Single BE Service When
the Actual Uplink Power Load of the Cell Falls into a Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444325
Average Number of 10ms

TTI HSUPA UEs Processing
a Single BE Service When
the Actual Uplink Power
Load of the Cell Falls into
Range 0 for Cell
73444326

Range 1 for Cell

1919
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444327

Range 2 for Cell
73444328

Range 3 for Cell
73444329

Range 4 for Cell
Description
These counters provide the average number of 10 ms TTI HSUPA UEs processing a single BE
service when the actual uplink power load of a cell in an active set falls into a specific range.
These counters do not take DC-HSUPA UEs into account. The RNC calculates the actual uplink
power load of a cell based on the filtered RTWP, total uplink load, and required uplink load.
The actual uplink power load ranges are as follows: Range 0 [0, 40%) Range 1 [40%, 60%)
Range 2 [60%, 80%) Range 3 [80%, 95%) Range 4 [95%, 100%].
Measurement point
At an interval of 5 seconds, the RNC samples the number of 10 ms TTI HSUPA UEs processing
a single BE service when the actual uplink power load of the cell falls into a specific range. At
the end of a measurement period, the RNC divides the accumulated number by the number of
samples. Then, within the measurement period, the average number of such UEs when the actual
uplink power load of the cell falls into a specific range is obtained.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1920
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020102
HSUPA 2ms TTI

Load Measurement
Number of HARQ PO Reconfiguration Attempts of HSUPA Users with Different

TTIs for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428216
VS.HSUPA.HARQ.POReCf
gAtt.TTI2ms
Number of HARQ PO
Reconfiguration Attempts of
HSUPA Users with 2 ms TTI
for Cell
73423567
gAtt.TTI10ms
Number of HARQ PO
Reconfiguration Attempts of
HSUPA Users with 10 ms
TTI for Cell

1921
BSC6900 UMTS
Description
These counters provide the number of HARQ PO reconfiguration attempts of HSUPA users
using 10 ms or 2 ms TTI in a cell. These counters are used to evaluate the performance of the
Adaptive Configuration of Traffic Channel Power offset for HSUPA feature in a network.These
counters comply with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331 (v10.10.0).
Measurement point
As shown at point A in the following figure, when the RNC sends a RADIO BEARER
RECONFIGURATION message during a HARQ PO reconfiguration procedure, the
measurement is triggered in the serving cell of HSUPA users based on the TTI.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1922
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
gAtt.TTI2ms
WRFD-010712
Adaptive Configuration of
Traffic Channel Power offset
for HSUPA
WRFD-160202

Transmission
gAtt.TTI10ms
WRFD-010712
WRFD-160202
for HSUPA
Transmission
Number of Successful HARQ PO Reconfigurations of HSUPA Users with

Different TTIs for Cell
Counters
Counter ID
Counter Name
Counter Description
73428217
gSucc.TTI2ms
HARQ PO Reconfigurations
of HSUPA Users with 2 ms
TTI for Cell
73423568
gSucc.TTI10ms
HARQ PO Reconfigurations
of HSUPA Users with 10 ms
TTI for Cell
Description
These counters provide the number of successful HARQ PO reconfigurations of HSUPA users
using 10 ms or 2 ms TTI in a cell. These counters are used to evaluate the performance of the
Adaptive Configuration of Traffic Channel Power offset for HSUPA feature in a network.
Measurement point
As shown at point B in the following figure, when the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message during a HARQ PO reconfiguration procedure,
the measurement is triggered in the serving cell of HSUPA users based on the TTI.
Issue 03 (2015-06-30)

1923
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
gSucc.TTI2ms
WRFD-010712
for HSUPA
WRFD-160202

Transmission
gSucc.TTI10ms
WRFD-010712
WRFD-160202
for HSUPA
Transmission
Issue 03 (2015-06-30)

1924
BSC6900 UMTS
Average Number of Gold, Silver, and Copper HSUPA Users for Cell
Counters
Counter ID
Counter Name
Counter Description
73444428
VS.HSUPA.GoldenUE.Mea
n.Cell
Average Number of Gold

HSUPA Users for Cell
73444429
VS.HSUPA.SilverUE.Mean.
Cell
Average Number of Silver

73444430
VS.HSUPA.CopperUE.Mea
n.Cell
Average Number of Copper

Description
These counters measure the average numbers of gold, silver, and copper HSUPA users in cells
in the active set. DC-HSUPA users are measured only on the primary carrier. If a UE is
processing combined services, the priority of the highest-priority service is used as the priority
of the UE.
Measurement point
The RNC takes samples of the number of gold, silver, and copper HSUPA users every 5 seconds
in a measurement period. At the end of the measurement period, the RNC obtains the average
number of gold, silver, and copper HSUPA users by dividing the accumulated numbers by the
corresponding sampling times.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.GoldenUE.Mea
n.Cell
WRFD-01061211
WRFD-010634
WRFD-010639
WRFD-01061211
WRFD-010634
WRFD-010639
VS.HSUPA.SilverUE.Mean.
Cell
Issue 03 (2015-06-30)

1925
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HSUPA.CopperUE.Mea
n.Cell
WRFD-01061211
WRFD-010634
WRFD-010639
Number of Abnormal RAB Releases for UEs Complying with R8 and Later and
Using SRB over HSUPA for Cell
Counters
Counter ID
Counter Name
Counter Description
73428930
el.SRBoE.AboveR8

Releases for UEs Complying
with R8 and Later and Using
SRB over HSUPA for Cell
Description
This counter provides the number of times the RAB of UEs complying with 3GPP Release 8
and later and using SRB over HSUPA is abnormally released in the serving cell (including RF
failures). For multi-carrier HSUPA users, this counter is measured only in the primary cell.
Unless otherwise stated, SRB over HSUPA users are those whose SRBs are carried on the
HSUPA and that are in the CELL_DCH state.This counter complies with section "8.2 RAB
Measurement point
The measurement is triggered at point A in figure 1. When a failure occurs, the RNC sends the
core network (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", "Network Optimization", or "UE Generated
Signalling Connection Release", this counter is measured in the serving cell if the RAB carries
HSUPA services and SRB over HSUPA is applied. For details about cause values indicating an
abnormal release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

1926
BSC6900 UMTS
CN a RAB RELEASE REQUEST message. If the RNC receives from the CN an IU RELEASE
COMMAND message with a cause value other than "User Inactivity", "Normal Release",
Release", this counter is measured in the serving cell if the RAB carries HSUPA services and
SRB over HSUPA is applied. For details about cause values indicating an abnormal release, see
3GPP TS 25.413.
Issue 03 (2015-06-30)

1927
BSC6900 UMTS
COMMAND message with a cause value other than "User Inactivity", "Normal Release",
Release", this counter is measured in the serving cell if the RAB carries HSUPA services and
SRB over HSUPA is applied. For details about cause values indicating an abnormal release, see
3GPP TS 25.413.
Issue 03 (2015-06-30)

1928
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
el.SRBoE.AboveR8
WRFD-020138
HSUPA Coverage
Enhancement at UE power
limitation

1929
BSC6900 UMTS
Number of Normal RAB Releases for UEs Complying with R8 and Later and Using
Counters
Counter ID
Counter Name
Counter Description
73428931
SRBoE.AboveR8

Releases for UEs Complying
with R8 and Later and Using
Description
This counter provides the number of times the RAB of UEs complying with 3GPP Release 8
and later and using SRB over HSUPA is normally released in the serving cell. For multi-carrier
HSUPA users, this counter is measured only in the primary cell. Unless otherwise stated, SRB
over HSUPA users are those whose SRBs are carried on the HSUPA and that are in the
CELL_DCH state.This counter complies with section "8.2 RAB Assignment" in 3GPP TS
25.413 (v10.10.0).
Measurement point
As shown by point A in figure 1, 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 when the following
conditions are met: The release cause 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 being "User
receiving the IU RELEASE COMMAND message. The RAB carries HSUPA services and SRB
over HSUPA is applied.
Issue 03 (2015-06-30)

1930
BSC6900 UMTS
As shown by point B in figure 2, after receiving an RAB ASSIGNMENT REQUEST message

with an RAB release request from the CN, the RNC releases the corresponding RAB and then
sends a RAB ASSIGNMENT RESPONSE message to the CN. This counter is increased by one
in the serving cell when the following conditions are met: The release cause 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 being "User Inactivity", "Network Optimization", or "UE Generated
Signalling Connection Release" before receiving the RAB ASSIGNMENT REQUEST message.
The RAB carries HSUPA services and SRB over HSUPA is applied.
Formula
None
Unit
None
Issue 03 (2015-06-30)

1931
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
SRBoE.AboveR8
WRFD-020138
HSUPA Coverage
Enhancement at UE power
limitation
HARQ Scheduling Results of HSUPA UEs Using the 2 ms or 10 ms TTI for Cell
Counters
Counter ID
Counter Name
Counter Description
73430199
VS.HSUPA.HARQ.ACK.T
TI2ms
Number of Times the HARQ

Scheduling Results of
HSUPA UEs Using the 2 ms
TTI Are ACK for Cell
73430200
VS.HSUPA.HARQ.NACK.
TTI2ms

TTI Are NACK for Cell
73430201
VS.HSUPA.HARQ.LOST.T
TI2ms

TTI Are LOST for Cell
73430202
VS.HSUPA.HARQ.ACK.T
TI10ms

TTI Are ACK for Cell
73430203
VS.HSUPA.HARQ.NACK.
TTI10ms

TTI Are NACK for Cell
73430204
TI10ms

TTI Are LOST for Cell
Description
These counter provide the HARQ scheduling results of HSUPA UEs using the 2 ms and 10 ms
TTIs in cells in the active set. The HARQ scheduling results of HSUPA UEs using the 2 ms and
10 ms TTIs can be ACK, NACK, and LOST.
Issue 03 (2015-06-30)

1932
BSC6900 UMTS
These counters comply with 3GPP TS 25.214 (v11.9.0). For details, see chapter 6B "E-DCH
related procedures" in this TS.
Measurement point
The RNC calculates the number of times the HARQ scheduling results are ACK, NACK, and
LOST, respectively for HSUPA UEs using the 2 ms and 10 ms TTIs in a measurement period.
At the end of the measurement period, these counters are independently measured in the cells
in the active set for the UE.
The RNC determines the HARQ scheduling results based on the scheduling results on the serving
and non-serving links. If the HARQ scheduling is successful on any link, the RNC determines
that the HARQ scheduling results are ACK. If the HARQ scheduling fails on all links, the RNC
determines that the HARQ scheduling results are NACK. If the HARQ scheduling fails on all
links or the data packet does not reach the RNC after the maximum number of retransmission
times have been reached, the RNC determines that the HARQ scheduling results are LOST.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.HARQ.ACK.T
TI2ms
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020503
HSUPA 2ms TTI

VS.HSUPA.HARQ.NACK.
TTI2ms
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020503
HSUPA 2ms TTI

TI2ms
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020503
HSUPA 2ms TTI

VS.HSUPA.HARQ.ACK.T
TI10ms
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020503
HSUPA 2ms TTI

Issue 03 (2015-06-30)

1933
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HSUPA.HARQ.NACK.
TTI10ms
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020503
HSUPA 2ms TTI

TI10ms
WRFD-010612
WRFD-01061403
HSUPA Introduction
Package
WRFD-020503
HSUPA 2ms TTI

Number of Attempts to Add RLs on the Secondary Carrier for DC-HSUPA UEs
During Soft and Softer Handovers for Cell
Counters
Counter ID
Counter Name
Counter Description
73430279
VS.HSUPA.SHO.DC.SEC.
AttRLAdd
Number of Attempts to Add

RLs on the Secondary Carrier
for DC-HSUPA UEs During
Soft and Softer Handovers
for Cell
Description
This counter provides the number of attempts to add a radio link (RL) on the secondary carrier
for a DC-HSUPA UE during a soft or softer handover in the cell to which the new RL belongs.
This counter is measured when the DC-HSUPA Independent Active Sets function is
enabled.This counter complies with 3GPP TS 25.331 (v9.17.0). For details, see section 10.2.1
"ACTIVE SET UPDATE" in this TS.
Measurement point
The measurement is triggered at point B in the following figure. During a soft or softer handover,
when the RNC sends an ACTIVE SET UPDATE message to the DC-HSUPA UE to add an RL
on the secondary carrier, this counter is measured in the cell to which the new RL belongs
Issue 03 (2015-06-30)

1934
BSC6900 UMTS
Figure 1-853 VS.HSUPA.SHO.DC.SEC.AttRLAdd
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
AttRLAdd
WRFD-140204
DC-HSUPA
Number of Times RLs on the Secondary Carrier Are Successfully Added for DCHSUPA UEs During Soft and Softer Handovers for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430280
SuccRLAdd
Number of Times RLs on the

Secondary Carrier Are
Successfully Added for DCHSUPA UEs During Soft and
Softer Handovers for Cell

1935
BSC6900 UMTS
Description
This counter provides the number of times that an RL on the secondary carrier is successfully
added for the DC-HSUPA UE during a soft or softer handover in the cell to which the new RL
belongs. This counter is measured when the DC-HSUPA Independent Active Sets function is
enabled.This counter complies with 3GPP TS 25.331 (v9.17.0). For details, see section 10.2.1
"ACTIVE SET UPDATE" in this TS.
Measurement point
The measurement is triggered at point C in the following figure. During a soft or softer handover,
when the RNC receives an ACTIVE SET UPDATE COMPLETE message from a DC-HSUPA
UE, the RNC considers the soft or softer handover as successful.If a new RL is added for the
DC-HSUPA UE on the secondary carrier, this counter is measured in the cell to which the new
RL belongs.
Figure 1-854 VS.HSUPA.SHO.DC.SEC.SuccRLAdd
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
SuccRLAdd
WRFD-140204
DC-HSUPA

1936
BSC6900 UMTS
Number of Attempts to Remove RLs on the Secondary Carrier for DC-HSUPA UEs
During Soft and Softer Handovers for Cell
Counters
Counter ID
Counter Name
Counter Description
73430281
AttRLDel
Remove RLs on the
Secondary Carrier for DCHSUPA UEs During Soft and
Softer Handovers for Cell
Description
This counter provides the number of attempts to remove an RL on the secondary carrier for a
DC-HSUPA UE. It is measured in the cell to which the RL to be removed belongs and is
measured only when the DC-HSUPA Independent Active Sets function is enabled.This counter
complies with 3GPP TS 25.331 (v9.17.0). For details, see section 10.2.1 "ACTIVE SET
UPDATE" in this TS.
Measurement point
The measurement is triggered at point B in the following figure. During a soft or softer handover,
when the RNC sends an ACTIVE SET UPDATE message to a DC-HSUPA UE to remove an
RL on the secondary carrier , this counter is measured in the cell to which the RL to be removed
belongs.
Figure 1-855 VS.HSUPA.SHO.DC.SEC.AttRLDel
Issue 03 (2015-06-30)

1937
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
AttRLDel
WRFD-140204
DC-HSUPA
Number of Times RLs on the Secondary Carrier Are Successfully Removed for DCHSUPA UEs During Soft and Softer Handovers for Cell
Counters
Counter ID
Counter Name
Counter Description
73430282
SuccRLDel
Number of Times RLs on the

Secondary Carrier Are
Successfully Removed for
DC-HSUPA UEs During
Soft and Softer Handovers
for Cell
Description
This counter provides the number of times an RL on the secondary carrier is successfully
removed for DC-HSUPA UEs during soft and softer handovers in a cell. It is measured in the
cell to which the RL to be removed belongs and is measured only when the DC-HSUPA
Independent Active Sets function is enabled.This counter complies with 3GPP TS 25.331
(v9.17.0). For details, see section 10.2.1 "ACTIVE SET UPDATE" in this TS.
Measurement point
The measurement is triggered at point C in the following figure. During a soft or softer handover,
when the RNC receives an ACTIVE SET UPDATE COMPLETE message from a DC-HSUPA
UE, the RNC considers the soft or softer handover as successful.If an RL is removed for the
DC-HSUPA UE on the secondary carrier during the soft or softer handover, this counter is
measured in the cell to which the RL belongs.
Issue 03 (2015-06-30)

1938
BSC6900 UMTS
Figure 1-856 VS.HSUPA.SHO.DC.SEC.SuccRLDel
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
SuccRLDel
WRFD-140204
DC-HSUPA
Average Number of HSUPA UEs in the Serving Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73446470
VS.HSUPA.UE.Mean.BestCell

UEs in the Serving Cell

1939
BSC6900 UMTS
Description
This counter provides the average number of HSUPA UEs in the serving cell. For DC-HSUPA
UEs, this counter is measured only in the primary carrier cell.
Measurement point
The system periodically takes samples (sampling period is 30 seconds) of the number of HSUPA
UEs. At the end of the measurement period, the average number of HSUPA UEs is obtained by
dividing the accumulated value of the sampling results in the period by the number of samplings.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.UE.Mean.BestCell
WRFD-01061211
WRFD-010634
WRFD-010639
1.12.18 Inter-RAT Handover Measurement <per Cell>

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

1940
BSC6900 UMTS
Figure 1-857 Flow chart of outgoing inter-RAT handover measurement procedure
Issue 03 (2015-06-30)

1941
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.IRATHO.AttRelocPrepOutCS.DR,
VS.IRATHO.AttRelocPrepOutCS.Load,
VS.IRATHO.AttRelocPrepOutCS.RF,
IRATHO.AttRelocPrepOutCS,
VS.IRATHO.AttRelocPrepOutCS.Service,
VS.IRATHO.AttRelocPrepOutCS.Sig,
VS.IRATHO.AttRelocPrepOutPS,
VS.IRATHO.AttOutCS.MBDR,
VS.SRVCC.U2GERAN.AttRelocPrepOutPS
VS.IRATHO.SuccRelocPrepOutCS.DR,
VS.IRATHO.SuccRelocPrepOutCS.Load,
VS.IRATHO.SuccRelocPrepOutCS.RF,
IRATHO.SuccRelocPrepOutCS,
VS.IRATHO.SuccRelocPrepOutCS.Service, VS.IRATHO.SuccRelocPrepOutCS.Sig,
VS.IRATHO.SuccRelocPrepOutPS,
VS.SRVCC.U2GERAN.SuccRelocPrepOutPS
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,
IRATHO.AttOutCS.Retry, VS.IRATHO.AttOutMultiRABCSPS,
VS.IRATHO.AttOutPS.TrigRscp,
VS.IRATHO.AttOutPS.TrigEcNo,
VS.IRATHO.AttOutPS.TrigULTxp,
VS.IRATHO.AttOutPS.TrigDLTxp

1942
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.IRATHO.SuccOutCS.DR,
VS.IRATHO.SuccOutCS.Load,
VS.IRATHO.SuccOutCS.RF,
IRATHO.SuccOutCS,
VS.IRATHO.SuccOutCS.Service,
VS.IRATHO.SuccOutCS.Sig,
VS.IRATHO.SuccRelocOutPS,
VS.IRATHO.SuccOutCS.MBDR,
VS.IRATHO.SuccOutCS.TrigRscp,
VS.IRATHO.SuccOutCS.TrigEcNo,
VS.IRATHO.SuccOutCS.TrigULTxp,
VS.IRATHO.SuccOutCS.TrigDLTxp,
VS.SRVCC.U2GERAN.SuccRelocOutPS,
VS.IRATHO.SuccOutMultiRABCSPS,
VS.IRATHO.SuccOutPS.TrigRscp,
VS.IRATHO.SuccOutPS.TrigEcNo,
VS.IRATHO.SuccOutPS.TrigULTxp,
VS.IRATHO.SuccOutPS.TrigDLTxp
IRATHO.FailRelocPrepOutCS.TAlExp,
IRATHO.FailRelocPrepOutCS.TgtFail,
IRATHO.FailRelocPrepOutCS.ReloNoSup,
IRATHO.FailRelocPrepOutCS.HigherTrafficLod,
IRATHO.FailRelocPrepOutCS.NoResAvail,
IRATHO.FailRelocPrepOutCS.UKnowRN
C,
VS.IRATHO.FailRelocPrepOutPS.TAlExp,
VS.IRATHO.FailRelocPrepOutPS.TgtFail,
VS.IRATHO.FailRelocPrepOutPS.ReloUnSupp,
VS.IRATHO.FailRelocPrepOutPS.TgtHighLoad,
VS.IRATHO.FailRelocPrepOutPS.NoResAvail,
VS.IRATHO.FailRelocPrepOutPS.UnKnowRNC,
VS.IRATHO.FailRelocPrepOutCS.Cancel,
VS.IRATHO.FailRelocPrepOutCS.ReqInfoNotAvail,
VS.IRATHO.FailRelocPrepOutCS.CNNoR
eply,
VS.IRATHO.FailRelocPrepOutCS.Abort

1943
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
IRATHO.FailOutCS.CfgUnsupp,
IRATHO.FailOutCS.PhyChFail,
VS.IRATHO.FailRelocOutPS.CfgUnSupp,
VS.IRATHO.FailRelocOutPS.PhyChFail,
VS.IRATHO.FailOutCS.SCRI,
VS.IRATHOCS.Cancel.ReEstab
VS.IRATHO.FailOutCS.NoReply,
VS.IRATHO.FailRelocOutPS.NoReply,
VS.IRATHO.FailOutCS.Abort,
VS.IRATHO.FailOutCS.InterRatRF,
VS.IRATHO.FailOutCS.CNUnspecFail
VS.IRATHO.AttNACC, VS.IRATHO.SuccNACC, VS.IRATHO.AttENACC,

VS.IRATHO.SuccENACC
VS.IRATHO.AttOutPSUTRAN.Load,
VS.IRATHO.AttOutPSUTRAN.RF,
IRATHO.AttOutPSUTRAN,
VS.IRATHO.AttOutPSUTRAN.Service,
VS.IRATHO.HSDPA.AttOutPSUTRAN,
VS.IRATHO.HSUPA.AttOutPSUTRAN,
VS.IRATHO.AttOutPSUTRAN.Sig,
IRATHO.AttOutPSUTRAN.Retry,
VS.IRATHO.SuccOutPSUTRAN.Load,
VS.IRATHO.SuccOutPSUTRAN.RF,
IRATHO.SuccOutPSUTRAN,
VS.IRATHO.SuccOutPSUTRAN.Service,
VS.IRATHO.HSDPA.SuccOutPSUTRAN,
VS.IRATHO.HSUPA.SuccOutPSUTRAN,
VS.IRATHO.SuccOutPSUTRAN.Sig,
VS.IRATHO.FailOutPSUTRAN.NoSRNSDataForwardCmd,
IRATHO.FailOutPSUTRAN.CfgUnsupp,
IRATHO.FailOutPSUTRAN.PhyChFail,
VS.IRATHO.FailOutPS.UEGen,
VS.IRATHOPS.Cancel.ReEstab,
VS.IRATHO.FailOutPS,
VS.IRATHO.FailOutPSUTRAN.SCRI

1944
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.IRATHO.FailOutPSUTRAN.NoReply,
VS.IRATHO.FailOutPS.Abort,
VS.IRATHO.FailOutPSUTRAN.InterRatRF,
VS.IRATHO.FailOutPSUTRAN.CNUnspecFail
VS.IRATHO.AttOutPSUE,
IRATHO.SuccOutPSUE,

1945
BSC6900 UMTS
Figure 1-858 Flow chart of incoming inter-RAT handover measurement procedure
Issue 03 (2015-06-30)

1946
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.SRVCC.L2U.AttRelocPrepInCS,
VS.SRVCC.L2U.AttRelocPrepInCS.Emerg,
VS.IRATHO.AttRelocPrepInCS,
VS.IRATHO.AttRelocPrepInPS,
VS.L2U.AttRelocPrepInPS,
VS.L2U.AttRelocPrepInPS.CS.CELL,
VS.SRVCC.L2U.AttRelocPrepInCSPS,
VS.SRVCC.L2U.AttRelocPrepInCSPS.Eme
rg
VS.IRATHO.SuccRelocPrepInCS,
VS.IRATHO.SuccRelocPrepInPS,
VS.SRVCC.L2U.SuccRelocPrepInCS,
VS.SRVCC.L2U.SuccRelocPrepInCS.Emer
g, VS.L2U.SuccRelocPrepInPS,
VS.L2U.SuccRelocPrepInPS.CS.CELL,
VS.SRVCC.L2U.SuccRelocPrepInCSPS,
VS.SRVCC.L2U.SuccRelocPrepInCSPS.E
merg
VS.IRATHO.AttInCS, VS.SRVCC.L2U.AttInCSPS
VS.IRATHO.SuccInCS, VS.IRATHO.SuccRelocInPS, VS.SRVCC.L2U.SuccRelocInCS,

VS.SRVCC.L2U.SuccRelocInCS.Emerg,
VS.L2U.SuccRelocInPS,
VS.L2U.SuccRelocInPS.CS.CELL,
VS.SRVCC.L2U.SuccInCSPS,
VS.SRVCC.L2U.SuccRelocInCSPS.Emerg

1947
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.IRATHO.FailRelocPrepInCS.TRNCSys
FailReloc,
VS.IRATHO.FailRelocPrepInCS.TRNCSys
RelocUnsupp,
VS.IRATHO.FailRelocPrepInCS.ResUnavail,
VS.IRATHO.FailRelocPrepInCS.TgtHighLoad,
VS.IRATHO.FailRelocPrepInPS.TgtFail,
VS.IRATHO.FailRelocPrepInPS.ReloUnSupp, VS.IRATHO.FailRelocPrepInPS.ResUnavail,
VS.IRATHO.FailRelocPrepInPS.TgtHighLoad,
VS.IRATHO.FailRelocPrepInCS.Abort,
VS.SRVCC.FailRelocPrepInCSPS.CSTimeOut,
VS.SRVCC.FailRelocPrepInCSPS.PSTimeOut,
VS.L2U.IRATHO.FailRelocPrepInCS.TgtF
ail,
VS.L2U.IRATHO.FailRelocPrepInCS.RelocUnSupp,
VS.L2U.IRATHO.FailRelocPrepInCS.ResUnavail,
VS.L2U.IRATHO.FailRelocPrepInCS.TgtH
ighLoad,
VS.L2U.IRATHO.FailRelocPrepInPS.TgtF
ail,
VS.L2U.IRATHO.FailRelocPrepInPS.ReloUnSupp,
VS.L2U.IRATHO.FailRelocPrepInPS.ResUnavail,
VS.L2U.IRATHO.FailRelocPrepInPS.TgtH
ighLoad,
VS.L2U.IRATHO.FailRelocPrepInCS.Abor
t,
VS.L2U.IRATHO.FailRelocPrepInPS.Abor
t
VS.IRATHO.FailInCS.NoReply,
VS.IRATHO.FailRelocInPS.NoReply,
VS.L2U.IRATHO.FailRelocInCS.NoReply,
VS.L2U.IRATHO.FailRelocInPS.NoReply
See counter "RRC.AttConnEstab.IRATCelRes" in function subset "RRC.Setup.Cell"
See counter "RRC.SuccConnEstab.IRATCelRes" in function subset "RRC.Setup.Cell"

1948
BSC6900 UMTS
Measurement points
Description
See counter "RRC.AttConnEstab.IRATCCO" in function subset "RRC.Setup.Cell"
See counter "RRC.SuccConnEstab.IRATCCO" in function subset "RRC.Setup.Cell"
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189729
VS.IRATHO.Succ
OutCS.DR
Number of
Successful CS
Outgoing Inter-RAT
Handovers Based on
Directed Retry for
Cell
Earlier than
BSC6900
V900R011
67189730
VS.IRATHO.AttRe
locPrepOutCS.DR
Number of
Preparation
Attempts for CS
Outgoing Inter-RAT
Handover Based on
Directed Retry for
Cell
Earlier than
BSC6900
V900R011
67189732
VS.IRATHO.Succ
RelocPrepOutCS.D
R
Number of
Successful
Preparations for CS
Outgoing Inter-RAT
Handover Based on
Directed Retry for
Cell
Earlier than
BSC6900
V900R011
67189739
VS.IRATHO.AttRe
locPrepOutCS.Loa
d
Number of
Preparation
Attempts for CS
Outgoing Inter-RAT
Handover Initiated
by UTRAN Based on
Load for Cell
Earlier than
BSC6900
V900R011
67189740
VS.IRATHO.Succ
RelocPrepOutCS.L
oad
Number of
Successful
Preparations for CS
Outgoing Inter-RAT
Handover Initiated
by UTRAN Based on
Load for Cell
Earlier than
BSC6900
V900R011

1949
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189741
VS.IRATHO.Succ
OutCS.Load
Number of
Successful CS
Outgoing Inter-RAT
Handovers Based on
Load for Cell
Earlier than
BSC6900
V900R011
67189742
VS.IRATHO.AttO
utPSUTRAN.Load
Number of PS
Outgoing Inter-RAT
Handover Attempts
Initiated by UTRAN
Based on Load for
Cell
Earlier than
BSC6900
V900R011
67189743
VS.IRATHO.Succ
OutPSUTRAN.Loa
d
Number of
Successful PS
Outgoing Inter-RAT
Handovers Initiated
by UTRAN Based on
Load for Cell
Earlier than
BSC6900
V900R011
67189744
VS.IRATHO.AttRe
locPrepOutCS.RF
Number of
Preparation
Attempts for CS
Outgoing Inter-RAT
Handover Based on
RF (Coverage, QoS,
or HCS) for Cell
Earlier than
BSC6900
V900R011
67189745
VS.IRATHO.Succ
RelocPrepOutCS.R
F
Number of
Successful
Preparations for CS
Outgoing Inter-RAT
Handover Based on
RF (Coverage, QoS,
or HCS) for Cell
Earlier than
BSC6900
V900R011
67189746
VS.IRATHO.Succ
OutCS.RF
Number of
Successful CS
Outgoing Inter-RAT
Handovers Based on
RF (Coverage, QoS,
or HCS) for Cell
Earlier than
BSC6900
V900R011
67189747
VS.IRATHO.AttO
utPSUTRAN.RF
Number of PS
Outgoing Inter-RAT
Handover Attempts
Initiated by the RNC
Based on RF
(Coverage, QoS, or
HCS) for Cell
Earlier than
BSC6900
V900R011

1950
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189748
VS.IRATHO.Succ
OutPSUTRAN.RF
Number of
Successful PS
Outgoing Inter-RAT
Handovers Initiated
by the RNC Based on
RF (Coverage, QoS,
or HCS) for Cell
Earlier than
BSC6900
V900R011
67189749
IRATHO.AttRelocPrepOutCS
Number of
Preparation
Attempts for CS
Outgoing Inter-RAT
Handover for Cell
Earlier than
BSC6900
V900R011
67189750
IRATHO.SuccRelocPrepOutCS
Number of
Successful
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
Earlier than
BSC6900
V900R011
67189751
IRATHO.FailReloc
PrepOutCS.TAlEx
p
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(TRELOCalloc
expiry)
Earlier than
BSC6900
V900R011
67189752
IRATHO.FailReloc
PrepOutCS.TgtFail
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(Relocation Failure
in Target CN/RNC or
Target System)
Earlier than
BSC6900
V900R011
67189753
IRATHO.FailReloc
PrepOutCS.ReloNoSup
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(Relocation not
supported in Target
RNC or Target
system)
Earlier than
BSC6900
V900R011
67189754
IRATHO.AttOutC
S
Number of CS
Outgoing Inter-RAT
Handover Attempts
Earlier than
BSC6900
V900R011

1951
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189755
IRATHO.SuccOut
CS
Number of
Successful CS
Outgoing Inter-RAT
Handovers for Cell
Earlier than
BSC6900
V900R011
67189756
IRATHO.FailOutC
S.CfgUnsupp
Number of Failed CS
Outgoing Inter-RAT
Handovers for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67189757
IRATHO.FailOutC
S.PhyChFail
Number of Failed CS
Outgoing Inter-RAT
Handovers for Cell
(Physical Channel
Failure)
Earlier than
BSC6900
V900R011
67189758
VS.IRATHO.AttRe
locPrepInCS
Number of
Preparations for CS
Incoming Inter-RAT
Handover for Cell
Earlier than
BSC6900
V900R011
67189759
VS.IRATHO.SuccInCS
Number of
Successful CS
Incoming Inter-RAT
Handovers for Cell
Earlier than
BSC6900
V900R011
67189760
VS.IRATHO.FailR
elocPrepInCS.TRN
CSysFailReloc
Number of Failed
Preparations for CS
Incoming Inter-RAT
Handover
target CN/RNC or
target system)
Earlier than
BSC6900
V900R011
67189761
VS.IRATHO.FailR
elocPrepInCS.TRN
CSysRelocUnsupp
Number of Failed
Preparations for CS
Incoming Inter-RAT
Handover
(Relocation not
supported in target
RNC or target
system)
Earlier than
BSC6900
V900R011
67189762
VS.IRATHO.FailR
elocPrepInCS.ResUnavail
Number of Failed
Preparations for CS
Incoming Inter-RAT
Handover (No
resource available)
Earlier than
BSC6900
V900R011

1952
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189763
IRATHO.SuccOutPSUE
Number of
Successful PS
Outgoing Inter-RAT
Handovers Initiated
by UE for Cell
Earlier than
BSC6900
V900R011
67190410
VS.IRATHO.FailI
nCS.NoReply
Number of Failed CS
Inter-RAT Incoming
Handovers Due to
No Response from
UE for Cell
Earlier than
BSC6900
V900R011
67190411
IRATHO.AttOutPSUTRAN
Number of PS
Outgoing Inter-RAT
Handover Attempts
Initiated by RNC for
Cell
Earlier than
BSC6900
V900R011
67190412
IRATHO.SuccOutPSUTRAN
Number of
Successful PS
Outgoing Inter-RAT
Handovers Initiated
by RNC for Cell
Earlier than
BSC6900
V900R011
67190476
IRATHO.FailOutP
SUTRAN.CfgUnsu
pp
Number of Failed PS
Outgoing Inter-RAT
Handovers Initiated
by RNC
(Configuration
unsupported)
Earlier than
BSC6900
V900R011
67190477
IRATHO.FailOutP
SUTRAN.PhyChFa
il
Number of Failed PS
Outgoing Inter-RAT
Handovers Initiated
by RNC (Physical
Channel Failure)
Earlier than
BSC6900
V900R011
67190413
VS.IRATHO.AttOutPSUE
Number of PS InterRAT Outgoing InterRAT Handover

Requests Initiated by
UE for Cell
Earlier than
BSC6900
V900R011
67190414
VS.IRATHO.SuccRelocPrepInCS
Number of
Successful
preparations for CS
Incoming Inter-RAT
Handovers for Cell
Earlier than
BSC6900
V900R011

1953
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190593
VS.IRATHO.AttRe
locPrepOutCS.Serv
ice
Number of
Preparation
Attempts for CS
Outgoing Inter-RAT
Handover Based on
Service Type for Cell
Earlier than
BSC6900
V900R011
67190856
VS.IRATHO.Succ
RelocPrepOutCS.S
ervice
Number of
Successful
Preparations for CS
Outgoing Inter-RAT
Handover Based on
Earlier than
BSC6900
V900R011
67190857
VS.IRATHO.Succ
OutCS.Service
Number of
Successful CS
Outgoing Inter-RAT
Handovers Based on
Earlier than
BSC6900
V900R011
67190858
VS.IRATHO.AttO
utPSUTRAN.Service
Number of PS
Outgoing Inter-RAT
Handover Attempts
Initiated by the RNC
Based on Service
Type for Cell
Earlier than
BSC6900
V900R011
67190859
VS.IRATHO.Succ
OutPSUTRAN.Ser
vice
Number of
Successful PS
Outgoing Inter-RAT
Handovers Initiated
by the RNC Based on
Earlier than
BSC6900
V900R011
67191155
VS.IRATHO.HSD
PA.AttOutPSUTR
AN
Number of PS InterRAT Outgoing

Handover Attempts
for HSDPA Services
for Cell
Earlier than
BSC6900
V900R011
67191156
VS.IRATHO.HSD
PA.SuccOutPSUTRAN
Number of
Successful PS
Outgoing Inter-RAT
Handovers for
HSDPA Services for
Cell
Earlier than
BSC6900
V900R011

1954
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192506
VS.IRATHO.HSU
PA.SuccOutPSUTRAN
Number of
Successful PS
Outgoing Inter-RAT
Handovers for
HSUPA Services for
Cell
Earlier than
BSC6900
V900R011
67192507
VS.IRATHO.HSU
PA.AttOutPSUTR
AN
Number of PS
Outgoing Inter-RAT
Handover Attempts
for HSUPA Services
for Cell
Earlier than
BSC6900
V900R011
67192186
IRATHO.FailReloc
PrepOutCS.HigherTrafficLod
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(Traffic Load In The
Target Cell Higher
Than In The Source
Cell)
Earlier than
BSC6900
V900R011
67192187
VS.IRATHO.FailR
elocPrepInCS.Tgt
HighLoad
Number of Failed
Preparations for CS
Incoming Inter-RAT
Handover (Traffic
Load In The Target
Cell Higher Than In
The Source Cell)
Earlier than
BSC6900
V900R011
67192654
VS.IRATHO.AttRe
locPrepOutCS.Sig
Number of
Preparations for CS
Outgoing Inter-RAT
Handover When only
Signaling Exists for
Cell
Earlier than
BSC6900
V900R011
67192655
VS.IRATHO.Succ
RelocPrepOutCS.S
ig
Number of
Successful
Preparations for CS
Outgoing Inter-RAT
Handover When only
Signaling Exists for
Cell
Earlier than
BSC6900
V900R011
67192656
VS.IRATHO.AttO
utCS.Sig
Number of CS
Outgoing Inter-RAT
Handover Attempts
When only Signaling
Exists for Cell
Earlier than
BSC6900
V900R011

1955
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192657
VS.IRATHO.Succ
OutCS.Sig
Number of
Successful CS
Outgoing Inter-RAT
Handovers When
only Signaling Exists
for Cell
Earlier than
BSC6900
V900R011
67192658
IRATHO.FailReloc
PrepOutCS.NoResAvail
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(No Resource
Available)
Earlier than
BSC6900
V900R011
67192659
IRATHO.FailReloc
PrepOutCS.UKno
wRNC
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(Unknown Target
RNC)
Earlier than
BSC6900
V900R011
67192660
VS.IRATHO.FailO
utCS.NoReply
Number of Times
that the Timer
Waiting for Iu
Release Command
Expires in CS
Outgoing Inter-RAT
Handover for Cell
Earlier than
BSC6900
V900R011
67192661
VS.IRATHO.FailO
utPSUTRAN.NoRe
ply
Number of Times
that the Timer
Waiting for Iu
Release Command
Expires in PS
Outgoing Inter-RAT
Handover Initiated
by RNC for Cell
Earlier than
BSC6900
V900R011
67192662
VS.IRATHO.AttRe
locPrepOutPS
Number of
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell
Earlier than
BSC6900
V900R011
67192663
VS.IRATHO.SuccRelocPrepOutPS
Number of
Successful
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell
Earlier than
BSC6900
V900R011

1956
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192664
VS.IRATHO.AttRe
locOutPS
Number of Enhanced
PS Outgoing InterRAT Handover
Attempts for Cell
Earlier than
BSC6900
V900R011
67192665
VS.IRATHO.SuccRelocOutPS
Number of
Successful Enhanced
PS Outgoing InterRAT Handovers for
Cell
Earlier than
BSC6900
V900R011
67192666
VS.IRATHO.FailR
elocPrepOutPS.TA
lExp
Number of Failed
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(TRELOCalloc
expiry)
Earlier than
BSC6900
V900R011
67192667
VS.IRATHO.FailR
elocPrepOutPS.Tgt
Fail
Number of Failed
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(Relocation Failure
in Target CN/RNC or
Target System)
Earlier than
BSC6900
V900R011
67192668
VS.IRATHO.FailR
elocPrepOutPS.ReloUnSupp
Number of Failed
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(Relocation not
supported in Target
RNC or Target
system)
Earlier than
BSC6900
V900R011
67192669
VS.IRATHO.FailR
elocPrepOutPS.Tgt
HighLoad
Number of Failed
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell
Target Cell Higher
Than In The Source
Cell)
Earlier than
BSC6900
V900R011

1957
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192670
VS.IRATHO.FailR
elocPrepOutPS.No
ResAvail
Number of Failed
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(No Resource
Available)
Earlier than
BSC6900
V900R011
67192671
VS.IRATHO.FailR
elocPrepOutPS.UnKnowRNC
Number of Failed
Preparations for
Enhanced PS
Outgoing Inter-RAT
Handover for Cell
(Unknown Target
RNC)
Earlier than
BSC6900
V900R011
67192672
VS.IRATHO.FailR
elocOutPS.CfgUnSupp
Number of Failed
Enhanced PS
Outgoing Inter-RAT
Handovers for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67192673
VS.IRATHO.FailR
elocOutPS.PhyChFail
Number of Failed
Enhanced PS
Outgoing Inter-RAT
Handovers for Cell
(Physical Channel
Failure)
Earlier than
BSC6900
V900R011
67192674
VS.IRATHO.FailR
elocOutPS.NoReply
Number of Times
that the Timer
Waiting for Iu
Release Command
Expires in Enhanced
PS Outgoing InterRAT Handover for
Cell
Earlier than
BSC6900
V900R011
67192675
VS.IRATHO.AttRe
locPrepInPS
Number of
Preparations for
Enhanced PS
Incoming Inter-RAT
Handover for Cell
Earlier than
BSC6900
V900R011

1958
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192676
VS.IRATHO.SuccRelocPrepInPS
Number of
Successful
Preparations for
Enhanced PS
Incoming Inter-RAT
Handover for Cell
Earlier than
BSC6900
V900R011
67192677
VS.IRATHO.SuccRelocInPS
Number of
Successful Enhanced
PS Incoming InterRAT Handovers for
Cell
Earlier than
BSC6900
V900R011
67192678
VS.IRATHO.FailR
elocPrepInPS.TgtF
ail
Number of Failed
Preparations for
Enhanced PS
Incoming Inter-RAT
Handover for cell
target CN/RNC or
target system)
Earlier than
BSC6900
V900R011
67192679
VS.IRATHO.FailR
elocPrepInPS.ReloUnSupp
Number of Failed
Preparations for
Enhanced PS
Incoming Inter-RAT
Handover for cell
(Relocation not
supported in target
RNC or target
system)
Earlier than
BSC6900
V900R011
67192680
VS.IRATHO.FailR
elocPrepInPS.ResUnavail
Number of Failed
Preparations for
Enhanced PS
Incoming Inter-RAT
Handover for cell
(No resource
available)
Earlier than
BSC6900
V900R011
67192681
VS.IRATHO.FailR
elocPrepInPS.TgtH
ighLoad
Number of Failed
Preparations for
Enhanced PS
Incoming Inter-RAT
Handover for cell
Target Cell Higher
Than In The Source
Cell)
Earlier than
BSC6900
V900R011

1959
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192682
VS.IRATHO.FailR
elocInPS.NoReply
Number of Failed
Enhanced PS
Incoming Inter-RAT
Handovers Due to
UE Response
Timeout for Cell
Earlier than
BSC6900
V900R011
67193399
VS.IRATHO.OutC
S.MeasTimeOut
Number of CS InterRAT Measurement

Expiry for Cell
Earlier than
BSC6900
V900R011
67193400
VS.IRATHO.OutP
S.MeasTimeOut
Number of PS InterRAT Measurement

Expiry for Cell
Earlier than
BSC6900
V900R011
67193405
VS.IRATHO.AttO
utCS.TrigRscp
Number of CS InterRAT Handover

Attempts Based on
RSCP for Cell
Earlier than
BSC6900
V900R011
67193406
VS.IRATHO.AttO
utCS.TrigEcNo

Attempts Based on
EcNo for Cell
Earlier than
BSC6900
V900R011
67193407
VS.IRATHO.AttO
utPS.TrigRscp
Number of PS InterRAT Handover

Attempts Based on
RSCP for Cell
Earlier than
BSC6900
V900R011
67193408
VS.IRATHO.AttO
utPS.TrigEcNo

Attempts Based on
EcNo for Cell
Earlier than
BSC6900
V900R011
67196299
VS.IRATHO.AttO
utCS.MBDR
Number of CS
Outgoing Inter-RAT
Handover Attempts
Based on
Measurement for
Cell
Earlier than
BSC6900
V900R011
67196300
VS.IRATHO.Succ
OutCS.MBDR
Number of
Successful CS
Outgoing Inter-RAT
Handovers Based on
Measurement for
Cell
Earlier than
BSC6900
V900R011

1960
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393922
VS.IRATHO.AttO
utCS.TrigULTxp

Attempts Based on
UL Transmit Power
of UE for Cell
BSC6900
V900R012
73393923
VS.IRATHO.AttO
utCS.TrigDLTxp

Attempts Based on
DL Code Power for
Cell
BSC6900
V900R012
73393924
VS.IRATHO.AttO
utPS.TrigULTxp

Attempts Based on
UL Transmit Power
of UE for Cell
BSC6900
V900R012
73393925
VS.IRATHO.AttO
utPS.TrigDLTxp

Attempts Based on
DL Code Power for
Cell
BSC6900
V900R012
73393926
VS.IRATHO.Succ
OutCS.TrigRscp
Number of
Successful CS InterRAT Handovers
Based on RSCP for
Cell
BSC6900
V900R012
73393927
VS.IRATHO.Succ
OutCS.TrigEcNo
Number of
Based on EcNo for
Cell
BSC6900
V900R012
73393928
VS.IRATHO.Succ
OutCS.TrigULTxp
Number of
Based on UL
Transmit Power of
UE for Cell
BSC6900
V900R012
73393929
VS.IRATHO.Succ
OutCS.TrigDLTxp
Number of
Based on DL Code
Power for Cell
BSC6900
V900R012

1961
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393930
VS.IRATHO.Succ
OutPS.TrigRscp
Number of
Successful PS InterRAT Handovers
Based on RSCP for
Cell
BSC6900
V900R012
73393931
VS.IRATHO.Succ
OutPS.TrigEcNo
Number of
Based on EcNo for
Cell
BSC6900
V900R012
73393932
VS.IRATHO.Succ
OutPS.TrigULTxp
Number of
Based on UL
Transmit Power of
UE for Cell
BSC6900
V900R012
73393933
VS.IRATHO.Succ
OutPS.TrigDLTxp
Number of
Based on DL Code
Power for Cell
BSC6900
V900R012
73394014
VS.IRATHO.AttInCS
Number of CS
Incoming Inter-RAT
Handover Attempts
for Cell
BSC6900
V900R012
73394015
VS.IRATHO.FailR
elocPrepOutCS.Ca
ncel
Number of Failed CS
Outgoing Inter-RAT
Handover
Preparations for Cell
(Relocation
Cancelled)
BSC6900
V900R012
73394016
VS.IRATHO.FailR
elocPrepOutCS.CN
NoReply
Number of Failed CS
Outgoing Inter-RAT
Handover
(Relocation
Command Wait
Timeout)
BSC6900
V900R012

1962
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394017
VS.IRATHO.FailR
elocPrepInCS.Abor
t
Number of CS
Incoming Inter-RAT
Handover
Preparation Failures
for Cell (Iu
RELEASE
COMMAND
Received)
BSC6900
V900R012
73394018
VS.IRATHO.FailO
utCS.Abort
Number of
Abnormally
Terminated CS
Outgoing Inter-RAT
Handovers for Cell
BSC6900
V900R012
73394019
VS.IRATHO.FailR
elocPrepOutCS.Ab
ort
Number of CS
Outgoing Inter-RAT
Handover
Preparation Failures
for Cell (Iu
RELEASE
COMMAND
Received)
BSC6900
V900R012
73394020
VS.IRATHO.FailR
elocPrepOutCS.ReqInfoNotAvail
Number of Failed CS
Outgoing Inter-RAT
Handover
(Requested
Information Not
Available)
BSC6900
V900R012
73394021
VS.IRATHO.FailOutPS
Number of Failed PS
Outgoing Inter-RAT
Handovers Initiated
by the RNC for Cell
BSC6900
V900R012
73394022
VS.IRATHO.FailO
utPS.Abort
Number of
Abnormally
Terminated PS
Outgoing Inter-RAT
Handovers for Cell
BSC6900
V900R012
73423107
VS.IRATHO.FailO
utPS.UEGen
Number of Failed
Outgoing UMTS-toGSM PS Handovers
due to UE
Reselection Back to a
UTRAN Cell
BSC6900
V900R013

1963
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423288
VS.SRVCC.U2GE
RAN.AttRelocPrepOutPS
Number of Outgoing
Inter-RAT PS
Handover
Preparation
Attempts Triggered
by SRVCC for VoIP
Services for Cell
BSC6900
V900R013
73423289
VS.SRVCC.U2GE
RAN.SuccRelocPrepOutPS
Number of
Successful Outgoing
Inter-RAT PS
Handover
Preparations
Triggered by
SRVCC for VoIP
Services for Cell
BSC6900
V900R013
73423290
VS.SRVCC.U2GE
RAN.SuccRelocOutPS
Number of
Successful Outgoing
Inter-RAT PS
Handovers Triggered
by SRVCC for VoIP
Services for Cell
BSC6900
V900R013
73425007
VS.IRATHO.FailO
utCS.SCRI
Number of Failed CS
Outgoing Inter-RAT
Handovers for Cell
(Signalling
Connection Release
Indication)
BSC6900
V900R014
73425008
VS.IRATHO.FailO
utPSUTRAN.SCRI
Number of Failed PS
Outgoing Inter-RAT
Handovers for Cell
(Signalling
Connection Release
Indication)
BSC6900
V900R014
73425009
VS.IRATHO.FailO
utPSUTRAN.NoSR
NSDataForwardC
md
Number of Failed PS
Outgoing Inter-RAT
Handovers for Cell
(No SRNS DATA
Forward cmd)
BSC6900
V900R014
73425010
VS.IRATHO.AttO
utPSUTRAN.Sig
Number of PS
Outgoing Inter-RAT
Handover Attempts
When only Signaling
Exists for Cell
BSC6900
V900R014

1964
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425011
VS.IRATHO.Succ
OutPSUTRAN.Sig
Number of
Successful PS
Outgoing Inter-RAT
Handovers When
only Signaling Exists
for Cell
BSC6900
V900R014
73425012
VS.IRATHO.FailO
utCS.InterRatRF
Number of Failed CS
Outgoing Inter-RAT
Handovers for Cell
BSC6900
V900R014
73425013
VS.IRATHO.FailO
utPSUTRAN.InterRatRF
Number of Failed PS
Outgoing Inter-RAT
Handovers for Cell
BSC6900
V900R014
73425926
VS.IRATHOCS.Ca
ncel.ReEstab
Number of RL
Reestablishment
Attempts After UEs
Failed to Receive the
CS Outgoing InterRAT Handover
Command for Cell
BSC6900
V900R015C00
73425927
VS.IRATHOPS.Ca
ncel.ReEstab
Number of RL
Reestablishment
Attempts After UEs
Failed to Receive the
PS Outgoing InterRAT Handover
Command for Cell
BSC6900
V900R015C00
73425954
VS.IRATHO.AttNACC
Number of Attempts
to Obtain GSM
System Information
during RIM-based
NACCs Triggered by
Inter-RAT PS
Handovers for Cell
BSC6900
V900R015C00

1965
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425955
VS.IRATHO.SuccNACC
Number of
Successful That
GSM System
Information Is
Obtained during
RIM-based NACCs
Triggered by InterRAT PS Handovers
for Cell
BSC6900
V900R015C00
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
BSC6900
V900R015C00
73425957
VS.IRATHO.Succ
ENACC
Number of
Successful Times
That GSM System
Information is
Obtained During Iurg-based ENACCs
Triggered by InterRAT PS Handovers
for Cell
BSC6900
V900R015C00
73426146
VS.L2U.AttRelocP
repInPS.CS.CELL
Number of Attempts
at Incoming PS LTEto-UMTS Handovers
Triggered by CSFB
for Cell
BSC6900
V900R015C00
73426147
VS.L2U.SuccReloc
InPS.CS.CELL
Number of
Successful Incoming
PS LTE-to-UMTS
Handovers Triggered
by CSFB for Cell
BSC6900
V900R015C00
73426148
VS.L2U.SuccReloc
PrepInPS.CS.CEL
L
Number of
Successful
Preparations for
Incoming PS LTEto-UMTS Handovers
Triggered by CSFB
for Cell
BSC6900
V900R015C00

1966
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425820
VS.SRVCC.L2U.At
tRelocPrepInCSPS
Number of
Preparation
Attempts for
Incoming LTE-toUMTS CS+PS
Handovers Triggered
by SRVCC for VoIP
Services for Cell
BSC6900
V900R015C00
73425821
VS.SRVCC.L2U.S
uccRelocPrepInCSPS
Number of
Successful
Preparations for
Incoming LTE-toUMTS CS+PS
Handovers Triggered
by SRVCC for VoIP
Services for Cell
BSC6900
V900R015C00
73425822
VS.SRVCC.L2U.At
tInCSPS
Number of Incoming
LTE-to-UMTS CS
+PS Handover
Attempts Triggered
by SRVCC for VoIP
Services for Cell
BSC6900
V900R015C00
73425823
VS.SRVCC.L2U.S
uccInCSPS
Number of
Successful Incoming
LTE-to-UMTS CS
+PS Handovers
Triggered by
SRVCC for VoIP
Services for Cell
BSC6900
V900R015C00
73426856
VS.IRATHO.FailO
utCS.CNUnspecFail
Number of Failed
Outgoing Inter-RAT
CS Handovers Due
to Abnormal
Connection Release
by CN for Cell
(Unspecified
Failure)
BSC6900
V900R015C01

1967
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426857
VS.IRATHO.FailO
utPSUTRAN.CNU
nspecFail
Number of Failed
Outgoing Inter-RAT
PS Handovers Due to
Abnormal
Connection Release
by CN for Cell
(Unspecified
Failure)
BSC6900
V900R015C01
73426858
VS.IRATHO.AttOutMultiRABCSP
S
Number of InterRAT Handover

CS+PS (One or
Multiple) Combined
Services for Cell
BSC6900
V900R015C01
73426859
VS.IRATHO.SuccOutMultiRABCS
PS
Number of
Successful InterRAT Handovers
Initiated by CS+PS
(One or Multiple)
Combined Services
for Cell
BSC6900
V900R015C01
73427898
VS.L2U.AttRelocPrepInPS
Number of
Preparation
Attempts for
Incoming PS Only
L2U Handovers in
Cell
BSC6900
V900R016C00
73427899
VS.L2U.SuccRelocPrepInPS
Number of
Successful
Preparations for
Incoming PS Only
L2U Handovers in
Cell
BSC6900
V900R016C00
73427900
VS.L2U.SuccRelocInPS
Number of
Successful Incoming
PS Only L2U
Handovers in Cell
BSC6900
V900R016C00

1968
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427977
VS.SRVCC.L2U.At
tRelocPrepInCS
Number of
Preparation
Attempts for CS
Only SRVCC
Handovers (a Single
Common Call or
Emergency Call) for
Cell
BSC6900
V900R016C00
73427978
VS.SRVCC.L2U.S
uccRelocPrepInCS
Number of
Successful
Preparation
Attempts for CS
Only SRVCC
Handovers (a Single
Common Call or
Emergency Call) for
Cell
BSC6900
V900R016C00
73427979
VS.SRVCC.L2U.S
uccRelocInCS
Number of
Successful CS Only
SRVCC Handover
Attempts (a Single
Common Call or
Emergency Call) for
Cell
BSC6900
V900R016C00
73427980
VS.SRVCC.L2U.At
tRelocPrepInCS.E
merg
Number of
Preparation
Attempts for CS
Only SRVCC
Handovers (a Single
Emergency Call) for
Cell
BSC6900
V900R016C00
73427981
VS.SRVCC.L2U.S
uccRelocPrepInCS.
Emerg
Number of
Successful
Preparation
Attempts for CS
Only SRVCC
Handovers (a Single
Emergency Call) for
Cell
BSC6900
V900R016C00

1969
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427982
VS.SRVCC.L2U.S
uccRelocInCS.Eme
rg
Number of
Successful CS Only
SRVCC Handover
Attempts (a Single
Emergency Call) for
Cell
BSC6900
V900R016C00
73427983
VS.SRVCC.FailRel
ocPrepInCSPS.CS
TimeOut
Number of Failed
Preparation
Attempts for CS+PS
SRVCC Handovers
Due to Timeout in
the LTE CS Domain
for Cell
BSC6900
V900R016C00
73427984
VS.SRVCC.FailRel
ocPrepInCSPS.PS
TimeOut
Number of Failed
Preparation
Attempts for CS+PS
SRVCC Handovers
Due to Timeout in
the LTE PS Domain
for Cell
BSC6900
V900R016C00
73427985
VS.SRVCC.L2U.At
tRelocPrepInCSPS.
Emerg
Number of
Preparation
Attempts for CS+PS
SRVCC Handovers
(Emergency Calls)
for Cell
BSC6900
V900R016C00
73427986
VS.SRVCC.L2U.S
uccRelocPrepInCS
PS.Emerg
Number of
Successful
Preparation
Attempts for CS+PS
SRVCC Handovers
(Emergency Calls)
for Cell
BSC6900
V900R016C00
73427987
VS.SRVCC.L2U.S
uccRelocInCSPS.E
merg
Number of
Successful CS+PS
SRVCC Handover
Attempts
(Emergency Calls)
for Cell
BSC6900
V900R016C00
73428084
IRATHO.AttOutC
S.Retry
Number of CS
Outgoing Inter-RAT
Handover
Reattempts for Cell
BSC6900
V900R016C00

1970
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428085
IRATHO.AttOutP
SUTRAN.Retry
Number of PS
Outgoing Inter-RAT
Handover
Reattempts for Cell
BSC6900
V900R016C00
73428677
VS.L2U.IRATHO.
FailRelocPrepInCS
.TgtFail
Number of Failed
Preparations for CS
Incoming L2U InterRAT Handover for
Cell (Relocation
failure in target CN/
RNC or target
system)
BSC6900
V900R016C00
73428678
VS.L2U.IRATHO.
FailRelocPrepInCS
.RelocUnSupp
Number of Failed
Preparations for CS
Cell (Relocation not
supported in target
RNC or target
system)
BSC6900
V900R016C00
73428679
VS.L2U.IRATHO.
FailRelocPrepInCS
.ResUnavail
Number of Failed
Preparations for CS
Cell (No resource
available)
BSC6900
V900R016C00
73428680
VS.L2U.IRATHO.
FailRelocPrepInCS
.TgtHighLoad
Number of Failed
Preparations for CS
Cell (Traffic Load In
The Target Cell
Higher Than In The
Source Cell)
BSC6900
V900R016C00
73428681
VS.L2U.IRATHO.
FailRelocPrepInPS
.TgtFail
Number of Failed
Preparations for PS
Cell (Relocation
failure in target CN/
RNC or target
system)
BSC6900
V900R016C00

1971
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428682
VS.L2U.IRATHO.
FailRelocPrepInPS
.ReloUnSupp
Number of Failed
Preparations for PS
Cell (Relocation not
supported in target
RNC or target
system)
BSC6900
V900R016C00
73428683
VS.L2U.IRATHO.
FailRelocPrepInPS
.ResUnavail
Number of Failed
Preparations for PS
Cell (No resource
available)
BSC6900
V900R016C00
73428684
VS.L2U.IRATHO.
FailRelocPrepInPS
.TgtHighLoad
Number of Failed
Preparations for PS
Cell (Traffic Load In
The Target Cell
Higher Than In The
Source Cell)
BSC6900
V900R016C00
73428685
VS.L2U.IRATHO.
FailRelocPrepInCS
.Abort
Number of Failed
Preparations for CS
Cell (IU RELEASE
COMMAND
message)
BSC6900
V900R016C00
73428686
VS.L2U.IRATHO.
FailRelocPrepInPS
.Abort
Number of Failed
Preparations for PS
Cell (IU RELEASE
COMMAND
message)
BSC6900
V900R016C00
73428687
VS.L2U.IRATHO.
FailRelocInCS.No
Reply
Number of Failed CS
Incoming L2U InterRAT Handovers Due
to UE Response
Timeout for Cell
BSC6900
V900R016C00

1972
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428688
VS.L2U.IRATHO.
FailRelocInPS.NoR
eply
Number of Failed PS
Incoming L2U InterRAT Handovers Due
to UE Response
Timeout for Cell
BSC6900
V900R016C00
73428827
VS.L2U.AttRelocP
repIn.UltraFlashCSFB
Number of Incoming
L2U CS+PS
Handover
Preparation
Attempts Triggered
by Ultra-Flash CSFB
for Cell
BSC6900
V900R016C00
73428828
VS.L2U.SuccReloc
PrepIn.UltraFlashCSFB
Number of
Successful Incoming
L2U CS+PS
Handover
Preparations
Triggered by UltraFlash CSFB for Cell
BSC6900
V900R016C00
73428829
VS.L2U.SuccReloc
In.UltraFlashCSFB
Number of
Successful Incoming
L2U CS+PS
Handovers Triggered
by Ultra-Flash CSFB
for Cell
BSC6900
V900R016C00
73430224
VS.L2U.IRATHO.
FailRelocPrepInCS
PS.ResUnavail
Number of Failed
Preparations for L2U
CS+PS Handovers
for Cell (No resource
available)
BSC6900
V900R017C10
73430225
VS.L2U.IRATHO.
FailRelocInCSPS.N
oReply
Number of Failed
L2U CS+PS
Handovers Due to
UE Response
Timeout for Cell
BSC6900
V900R017C10
73430230
VS.SRVCC.L2U.S
uccRelocPrepInCS.
PSTimeOut
Number of
Successful L2U CS
Handover
Preparations for CS
+PS Combined
Services Triggered
by SRVCC for Cell
(PS Timeout)
BSC6900
V900R017C10

1973
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430231
VS.SRVCC.L2U.S
uccRelocInCS.PSTi
meOut
Number of
Successful L2U CS
Handovers for CS
+PS Combined
Services Triggered
by SRVCC for Cell
(PS Timeout)
BSC6900
V900R017C10
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
VS.IRATHO.AttRelocPrepOutCS.DR
VS.IRATHO.AttRelocPrepOutCS.Load
VS.IRATHO.AttRelocPrepOutCS.RF
VS.IRATHO.AttRelocPrepOutCS.Service
VS.IRATHO.SuccRelocPrepOutCS.DR
VS.IRATHO.SuccRelocPrepOutCS.Load
VS.IRATHO.SuccRelocPrepOutCS.RF
VS.IRATHO.SuccRelocPrepOutCS.Service
VS.IRATHO.AttOutPSUTRAN.Load
VS.IRATHO.AttOutPSUTRAN.RF
VS.IRATHO.AttOutPSUTRAN.Service
VS.IRATHO.SuccOutPSUTRAN.Load
VS.IRATHO.SuccOutPSUTRAN.RF
VS.IRATHO.SuccOutPSUTRAN.Service
Issue 03 (2015-06-30)
VS.IRATHO.AttRelocPrepOutPS
VS.SRVCC.U2GERAN.SuccRelocPrepOutPS

1974
BSC6900 UMTS
Counter
Sub Counter
VS.SRVCC.U2GERAN.SuccRelocOutPS
Number of Preparations for CS or Enhanced PS Outgoing Inter-RAT Handover for

Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189730
OutCS.DR
Number of Preparation
Attempts for CS Outgoing
on Directed Retry for Cell
67189739
OutCS.Load
Inter-RAT Handover
Initiated by UTRAN Based
on Load for Cell
67189744
OutCS.RF
on RF (Coverage, QoS, or
HCS) for Cell
67189749
Inter-RAT Handover for Cell
67190593
OutCS.Service
on Service Type for Cell
67192654
OutCS.Sig
Number of Preparations for

CS Outgoing Inter-RAT
Handover When only
67192662

Enhanced PS Outgoing InterRAT Handover for Cell
67196299
VS.IRATHO.AttOutCS.MB
DR
Inter-RAT Handover
Attempts Based on
Measurement for Cell

1975
BSC6900 UMTS
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.
Counter Name
Description
VS.IRATHO.AttRelocPrepOutCS.DR
This counter complies with section "8.6

Relocation Preparation" in 3GPP TS 25.413
(v10.10.0).
VS.IRATHO.AttRelocPrepOutCS.Load

(v10.10.0).
VS.IRATHO.AttRelocPrepOutCS.RF

(v10.10.0).

(v10.10.0).
VS.IRATHO.AttRelocPrepOutCS.Service

(v10.10.0).
VS.IRATHO.AttRelocPrepOutCS.Sig

(v10.10.0).

(v10.10.0).
VS.IRATHO.AttOutCS.MBDR

Inter-RAT handover from UTRAN" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends the CN a
RELOCATION REQUIRED message during the CS or Enhanced PS outgoing inter-RAT
handover. In this case, the corresponding counters are measured in the best cell that the UE
camps on .
Issue 03 (2015-06-30)

1976
BSC6900 UMTS
Figure 1-859 Normal CS or Enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OutCS.DR
WRFD-02040002
Inter System Direct Retry
OutCS.Load
WRFD-020306

on Load
OutCS.RF
WRFD-020303

on Coverage
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

1977
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
OutCS.Service
WRFD-020305

on Service
OutCS.Sig
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
WRFD-02030802
PS Handover Between
UMTS and GPRS
VS.IRATHO.AttOutCS.MB
DR
WRFD-02040002
WRFD-020402
Measurement Based Direct

Retry
Number of Outgoing Inter-RAT PS Handover Preparation Attempts Triggered by

SRVCC for VoIP Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73423288
Number of Outgoing InterRAT PS Handover

Preparation Attempts
Triggered by SRVCC for
VoIP Services for Cell
Description
This counter provides the number of outgoing inter-RAT PS handover preparation attempts
triggered by Single Radio Voice Call Continuity (SRVCC) for VoIP services in the best cell that
the UE camps on. After SRVCC is enabled, a VoIP service carried on HSPA is processed as a
PS service at the UTRAN and as a CS service at the GERAN during the UTRAN-to-GERAN
handover to ensure the speech continuity.This counter complies with section "8.6 Relocation
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.
Issue 03 (2015-06-30)

1978
BSC6900 UMTS
Figure 1-860 VS.SRVCC.U2GERAN.AttRelocPrepOutPS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-02030802
PS Handover Between
UMTS and GPRS
Number of Successful Preparations for CS or Enhanced PS Outgoing Inter-RAT

Handover for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189732
pOutCS.DR
Preparations for CS
Outgoing Inter-RAT
Handover Based on Directed
Retry for Cell

1979
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67189740
pOutCS.Load
Preparations for CS
Outgoing Inter-RAT
Handover Initiated by
UTRAN Based on Load for
Cell
67189745
pOutCS.RF
Preparations for CS
Outgoing Inter-RAT
Handover Based on RF
(Coverage, QoS, or HCS) for
Cell
67189750
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
67190856
pOutCS.Service
Preparations for CS
Outgoing Inter-RAT
Handover Based on Service
Type for Cell
67192655
pOutCS.Sig
Preparations for CS
Outgoing Inter-RAT
Handover When only
67192663
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.The preceding counters complies with
section "8.6 Relocation Preparation" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

1980
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
pOutCS.DR
WRFD-02040002
pOutCS.Load
WRFD-020306

on Load
pOutCS.RF
WRFD-020303

on Coverage
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

1981
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
pOutCS.Service
WRFD-020305

on Service
pOutCS.Sig
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
WRFD-02030802
PS Handover Between
UMTS and GPRS
Number of Successful Outgoing Inter-RAT PS Handover Preparations Triggered

by SRVCC for VoIP Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73423289
VS.SRVCC.U2GERAN.Suc
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.This counter complies with section "8.6 Relocation
Measurement point
The measurement is triggered at point B shown in the figure. When the RNC receives from the
CN a RELOCATION COMMAND message during the SRVCC-triggered inter-RAT PS
handover for a VoIP service, this counter is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

1982
BSC6900 UMTS
Figure 1-862 VS.SRVCC.U2GERAN.SuccRelocPrepOutPS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
cRelocPrepOutPS
WRFD-02030802
PS Handover Between
UMTS and GPRS
Number of CS or Enhanced PS Outgoing Inter-RAT Handover Attempts for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189754
IRATHO.AttOutCS
Inter-RAT Handover
Attempts

1983
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192656
VS.IRATHO.AttOutCS.Sig
Inter-RAT Handover
Attempts When only
67192664
VS.IRATHO.AttRelocOutPS
Number of Enhanced PS
Outgoing Inter-RAT
67193405
VS.IRATHO.AttOutCS.Trig
Rscp
Number of CS Inter-RAT
Handover Attempts Based on
RSCP for Cell
67193406
VS.IRATHO.AttOutCS.TrigEcNo
EcNo for Cell
73393922
VS.IRATHO.AttOutCS.TrigULTxp
UL Transmit Power of UE
for Cell
73393923
DLTxp
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.The preceding counters complies with section "8.3.7 Inter-RAT
handover from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends the UE a
HANDOVER FROM UTRAN COMMAND message during the CS or Enhanced PS outgoing
inter-RAT handover. In this case, these counters are measured in the best cell that the UE camps
on.
Issue 03 (2015-06-30)

1984
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
IRATHO.AttOutCS
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
VS.IRATHO.AttOutCS.Sig
WRFD-020303
WRFD-020305
WRFD-020306

on Coverage
on Service
on Load
Issue 03 (2015-06-30)

1985
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttRelocOutPS
WRFD-02030802
PS Handover Between
UMTS and GPRS
Rscp
WRFD-020303

on Coverage
VS.IRATHO.AttOutCS.TrigEcNo
WRFD-020303

on Coverage
DLTxp
WRFD-020309

on DL QoS
Number of CS Outgoing Inter-RAT Handover Reattempts for Cell

Counters
Counter ID
Counter Name
Counter Description
73428084
IRATHO.AttOutCS.Retry
Inter-RAT Handover
Reattempts for Cell
Description
This counter measures the number of outgoing inter-RAT handover reattempts initiated on UEs
processing CS services in the best cell after an outgoing CS inter-RAT handover failure.This
(v10.13.0).
Measurement point
A UE processing CS services starts the compressed mode to perform inter-frequency
measurements. The RNC then initiates an outgoing inter-RAT handover procedure on the UE.
If the RNC receives a HANDOVER FROM UTRAN FAILURE message from the UE, the RNC
reattempts to initiate an outgoing inter-RAT handover procedure on the UE, as shown by points
B, C, and D in the following figure. This counter is measured in the best cell for the UE under
the SRNC when the RNC sends a HANDOVER FROM UTRAN COMMAND message to the
UE.
Issue 03 (2015-06-30)

1986
BSC6900 UMTS
Figure 1-864 CS inter-RAT handover reattempt procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

1987
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
IRATHO.AttOutCS.Retry
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Inter-RAT Handover Attempts Initiated by CS+PS (One or Multiple)

Counters
Counter ID
Counter Name
Counter Description
73426858
VS.IRATHO.AttOutMultiRABCSPS
Number of Inter-RAT
Handover Attempts Initiated
by CS+PS (One or Multiple)
Description
This counter measures the number of outgoing UMTS-to-GSM handover attempts initiated by
CS+PS combined services in the best cell. The CS+PS combined services can have either one
or multiple PS services.This counter complies with section "8.3.6 Inter-RAT handover to
UTRAN" in 3GPP TS 25.331 (v10.13.0).
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 an outgoing inter-RAT
handover initiated by CS+PS combined services, this counter is increased by one in the best cell
of the UE before the handover.
Issue 03 (2015-06-30)

1988
BSC6900 UMTS
Figure 1-865 Outgoing inter-RAT CS handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttOutMultiRABCSPS
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

1989
BSC6900 UMTS
Counters Related to the Number of PS Outgoing Inter-RAT Handover Attempts

Counters
Counter ID
Counter Name
Counter Description
67193407
VS.IRATHO.AttOutPS.Trig
Rscp
Number of PS Inter-RAT
RSCP for Cell
67193408
VS.IRATHO.AttOutPS.TrigEcNo
EcNo for Cell
73393924
VS.IRATHO.AttOutPS.TrigULTxp
UL Transmit Power of UE
for Cell
73393925
DLTxp
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.The preceding counters complies with section "8.3.11
Inter-RAT cell change order from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement can be triggered at point B as shown in the figure, when the RNC sends the
CELL CHANGE ORDER FROM UTRAN message during the PS outgoing inter-RAT
handover. In this case, the corresponding counter is measured in the best cell that the UE camps
on under the SRNC, based on the handover cause.
Issue 03 (2015-06-30)

1990
BSC6900 UMTS
Figure 1-866 Handover instruction
The measurement can also be triggered at point C as shown in the figure, when the RNC sends
the UE a HANDOVER FROM UTRAN COMMAND message during the enhanced PS outgoing
inter-RAT handover. In this case, the corresponding counter is measured in the best cell that the
UE camps on under the SRNC, based on the handover cause.
Issue 03 (2015-06-30)

1991
BSC6900 UMTS
Figure 1-867 Handover instruction
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Rscp
WRFD-020303

on Coverage
VS.IRATHO.AttOutPS.TrigEcNo
WRFD-020303

on Coverage
DLTxp
WRFD-020309

on DL QoS

1992
BSC6900 UMTS
Number of Successful CS or Enhanced PS Outgoing Inter-RAT Handovers for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189729
VS.IRATHO.SuccOutCS.D
R
Outgoing Inter-RAT
Handovers Based on
Directed Retry for Cell
67189741
VS.IRATHO.SuccOutCS.L
oad
Outgoing Inter-RAT
Handovers Based on Load
for Cell
67189746
F
Outgoing Inter-RAT
Handovers Based on RF
Cell
67189755
IRATHO.SuccOutCS
Outgoing Inter-RAT
Handovers for Cell
67190857
VS.IRATHO.SuccOutCS.Se
rvice
Outgoing Inter-RAT
Handovers Based on Service
Type for Cell
67192657
VS.IRATHO.SuccOutCS.Si
g
Outgoing Inter-RAT
Handovers When only
67192665
Enhanced PS Outgoing InterRAT Handovers for Cell
67196300
VS.IRATHO.SuccOutCS.M
BDR
Outgoing Inter-RAT
Handovers Based on
73393926
VS.IRATHO.SuccOutCS.Tr
igRscp
Inter-RAT Handovers Based
on RSCP for Cell
73393927
igEcNo
on EcNo for Cell

1993
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73393928
igULTxp
on UL Transmit Power of UE
for Cell
73393929
igDLTxp
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.
Issue 03 (2015-06-30)
Counter Name
Description
VS.IRATHO.SuccOutCS.DR

TS 25.331 (v10.13.0).
VS.IRATHO.SuccOutCS.Load

(v10.10.0).
VS.IRATHO.SuccOutCS.RF

TS 25.331 (v10.13.0).
IRATHO.SuccOutCS

TS 25.331 (v10.13.0).
VS.IRATHO.SuccOutCS.Service

TS 25.331 (v10.13.0).
VS.IRATHO.SuccOutCS.Sig

TS 25.331 (v10.13.0).

TS 25.331 (v10.13.0).
VS.IRATHO.SuccOutCS.MBDR

TS 25.331 (v10.13.0).

1994
BSC6900 UMTS
Counter Name
Description
VS.IRATHO.SuccOutCS.TrigRscp

TS 25.331 (v10.13.0).
VS.IRATHO.SuccOutCS.TrigEcNo

TS 25.331 (v10.13.0).
VS.IRATHO.SuccOutCS.TrigULTxp

TS 25.331 (v10.13.0).
VS.IRATHO.SuccOutCS.TrigDLTxp

TS 25.331 (v10.13.0).
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.
Figure 1-868 Normal CS or the Enhanced PS outgoing inter-RAT handover
Issue 03 (2015-06-30)

1995
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccOutCS.D
R
WRFD-02040002
VS.IRATHO.SuccOutCS.L
oad
WRFD-020306

on Load
F
WRFD-020303

on Coverage
IRATHO.SuccOutCS
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
VS.IRATHO.SuccOutCS.Se
rvice
WRFD-020305

on Service
VS.IRATHO.SuccOutCS.Si
g
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)
WRFD-02030802
PS Handover Between
UMTS and GPRS
VS.IRATHO.SuccOutCS.M
BDR
WRFD-02040002
WRFD-020402

Retry
igRscp
WRFD-020303

on Coverage
igEcNo
WRFD-020303

on Coverage

1996
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
igDLTxp
WRFD-020309

on DL QoS
Number of Successful Outgoing Inter-RAT PS Handovers Triggered by SRVCC

for VoIP Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73423290
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.This counter complies with section "8.5 Iu Release" in 3GPP TS
25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

1997
BSC6900 UMTS
Figure 1-869 VS.SRVCC.U2GERAN.SuccRelocOutPS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
cRelocOutPS
WRFD-02030802
PS Handover Between
UMTS and GPRS
Number of Successful Inter-RAT Handovers Initiated by CS+PS (One or Multiple)

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426859
VS.IRATHO.SuccOutMultiRABCSPS
Number of Successful InterRAT Handovers Initiated by

CS+PS (One or Multiple)

1998
BSC6900 UMTS
Description
This counter measures the number of successful outgoing UMTS-to-GSM handovers initiated
by CS+PS combined services in the best cell. The CS+PS combined services can have either
one or multiple PS services.This counter complies with section "8.3.6 Inter-RAT handover to
UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point D, as shown in the figure. During an outgoing inter-RAT
handover initiated by CS+PS combined services, when the RNC receives from the CS domain
an IU RELEASE COMMAND message with the cause value "Successful Relocation", "Normal
Release", or "Network Optimization" after sending a HANDOVER FROM UTRAN
COMMAND message, this counter is increased by one in the best cell of the UE before the
handover.
Figure 1-870 Outgoing inter-RAT CS handover
Formula
None
Unit
None
Issue 03 (2015-06-30)

1999
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccOutMultiRABCSPS
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Counters Related to the Number of Successful PS Outgoing Inter-RAT Handovers

Counters
Counter ID
Counter Name
Counter Description
73393930
VS.IRATHO.SuccOutPS.Tr
igRscp
on RSCP for Cell
73393931
igEcNo
on EcNo for Cell
73393932
igULTxp
on UL Transmit Power of UE
for Cell
73393933
igDLTxp
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.The preceding counters complies with section "8.3.11
Inter-RAT cell change order from UTRAN" in 3GPP TS 25.331 (v10.13.0).
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,
Issue 03 (2015-06-30)

2000
BSC6900 UMTS
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-871 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.
Issue 03 (2015-06-30)

2001
BSC6900 UMTS
Figure 1-872 Handover Indication 2
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
igRscp
WRFD-020303

on Coverage
igEcNo
WRFD-020303

on Coverage
igDLTxp
WRFD-020309

on DL QoS

2002
BSC6900 UMTS
Number of Failed Preparations for CS or Enhanced PS Outgoing Inter-RAT

Handover for Different Causes for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189751
IRATHO.FailRelocPrepOut
CS.TAlExp
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(TRELOCalloc expiry)
67189752
CS.TgtFail
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
67189753
CS.ReloNoSup
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell
(Relocation not supported in
system)
67192186
CS.HigherTrafficLod
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell (Traffic
Load In The Target Cell
Higher Than In The Source
Cell)
67192658
CS.NoResAvail
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell (No
Resource Available)
67192659
CS.UKnowRNC
Number of Failed
Preparations for CS
Outgoing Inter-RAT
Handover for Cell (Unknown
Target RNC)

2003
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192666
VS.IRATHO.FailRelocPrep
OutPS.TAlExp
Number of Failed
Handover for Cell
67192667
OutPS.TgtFail
Number of Failed
Handover for Cell
67192668
OutPS.ReloUnSupp
Number of Failed
Handover for Cell
system)
67192669
OutPS.TgtHighLoad
Number of Failed
Cell)
67192670
OutPS.NoResAvail
Number of Failed
Resource Available)
67192671
OutPS.UnKnowRNC
Number of Failed
Handover for Cell (Unknown
Target RNC)
73394015
OutCS.Cancel
Number of Failed CS
Outgoing Inter-RAT
Handover Preparations for
Cell (Relocation Cancelled)
73394020
OutCS.ReqInfoNotAvail
Number of Failed CS
Outgoing Inter-RAT
Cell (Requested Information
Not Available)

2004
BSC6900 UMTS
Description
These counters provide the number of failed preparations for CS or Enhanced PS outgoing interRAT handover in the best cell due to different causes.The preceding counters complies with
section "8.6 Relocation Preparation" in 3GPP TS 25.413 (v10.10.0).
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.
Figure 1-873 Failed relocation preparation for SRNC
Formula
None
Unit
None
Issue 03 (2015-06-30)

2005
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
CS.TAlExp
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
CS.TgtFail
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
CS.ReloNoSup
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
CS.HigherTrafficLod
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
CS.NoResAvail
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2006
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
CS.UKnowRNC
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
OutPS.TAlExp
WRFD-02030802
PS Handover Between
UMTS and GPRS
OutPS.TgtFail
WRFD-02030802
PS Handover Between
UMTS and GPRS
OutPS.ReloUnSupp
WRFD-02030802
PS Handover Between
UMTS and GPRS
OutPS.TgtHighLoad
WRFD-02030802
PS Handover Between
UMTS and GPRS
OutPS.NoResAvail
WRFD-02030802
PS Handover Between
UMTS and GPRS
OutPS.UnKnowRNC
WRFD-02030802
PS Handover Between
UMTS and GPRS
OutCS.Cancel
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
OutCS.ReqInfoNotAvail
WRFD-020303
WRFD-020305
WRFD-020306

on Coverage
on Service
on Load
Issue 03 (2015-06-30)

2007
BSC6900 UMTS
Number of Failed CS Outgoing Inter-RAT Handover Preparations (Relocation

Command Wait Timeout) for Cell
Counters
Counter ID
Counter Name
Counter Description
73394016
OutCS.CNNoReply
Number of Failed CS
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.This counter
complies with section "8.6 Relocation Preparation" in 3GPP TS 25.413 (v10.10.0).
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-874 SRNC relocation preparation failure due to expiry of relocation command
Issue 03 (2015-06-30)

2008
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OutCS.CNNoReply
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of CS Outgoing Inter-RAT Handover Preparation Failures (Iu RELEASE

COMMAND Received) for Cell
Counters
Counter ID
Counter Name
Counter Description
73394019
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.The preceding
counters complies with section "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives an IU
RELEASE COMMAND command after sending the CN a RELOCATION REQUIRED
message during the CS outgoing inter-RAT handover.
Issue 03 (2015-06-30)

2009
BSC6900 UMTS
Figure 1-875 RNC-initiated CS domain inter-RAT outgoing handover procedure (failed

operation due to termination)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OutCS.Abort
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2010
BSC6900 UMTS
Number of Failed CS or Enhanced PS Outgoing Inter-RAT Handovers for Different

Causes for Cell
Counters
Counter ID
Counter Name
Counter Description
67189756
IRATHO.FailOutCS.CfgUn
supp
Number of Failed CS
Outgoing Inter-RAT
Handovers for Cell
(Configuration
Unsupported)
67189757
IRATHO.FailOutCS.PhyCh
Fail
Number of Failed CS
Outgoing Inter-RAT
Channel Failure)
67192672
VS.IRATHO.FailRelocOutP
S.CfgUnSupp
Number of Failed Enhanced

Handovers for Cell
(Configuration
Unsupported)
67192673
S.PhyChFail

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.This counter complies with section "8.3.7 Inter-RAT
handover from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)
Counter Name
Description
IRATHO.FailOutCS.PhyChFail

TS 25.331 (v10.13.0).
VS.IRATHO.FailRelocOutPS.CfgUnSupp

(v10.10.0).
VS.IRATHO.FailRelocOutPS.PhyChFail

(v10.10.0).

2011
BSC6900 UMTS
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.
Figure 1-876 Failed CS or the Enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
IRATHO.FailOutCS.CfgUn
supp
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2012
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
IRATHO.FailOutCS.PhyCh
Fail
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
S.CfgUnSupp
WRFD-02030802
PS Handover Between
UMTS and GPRS
S.PhyChFail
WRFD-02030802
PS Handover Between
UMTS and GPRS
Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Signalling

Connection Release Indication)
Counters
Counter ID
Counter Name
Counter Description
73425007
VS.IRATHO.FailOutCS.SC
RI
Number of Failed CS
Outgoing Inter-RAT
Handovers for Cell
(Signalling Connection
Release Indication)
Description
This counter provides the number of the CS outgoing inter-RAT handover fails in the best cell
because the RNC receives SIGNALLING CONNECTION RELEASE INDICATION from the
UE.This counter complies with section "8.3.7 Inter-RAT handover from UTRAN" in 3GPP TS
25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure.During the CS outgoing interRAT handover, if the RNC receives a SIGNALLING CONNECTION RELEASE
INDICATION message after sending the HANDOVER FROM UTRAN COMMAND
message.In this case, this counter is increased by one in the best cell that the UE camps on before
the handover.
Issue 03 (2015-06-30)

2013
BSC6900 UMTS
Figure 1-877 Procedure for a failed outgoing inter-RAT handover in the CS domain
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutCS.SC
RI
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2014
BSC6900 UMTS
Number of RL Reestablishment Attempts After UEs Failed to Receive the CS

Outgoing Inter-RAT Handover Command for Cell
Counters
Counter ID
Counter Name
Counter Description
73425926
Number of RL
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.This counter complies with section "8.3.1 Cell
and URA update procedures" in 3GPP TS 25.331 (v10.13.0).
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-878 RL reestablishment during a CS or enhanced PS outgoing inter-RAT handover
Issue 03 (2015-06-30)

2015
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020303

on Coverage
WRFD-020306
WRFD-020305

on Load
on Service
Number of Times that the Timer Waiting for Iu Release Command Expires in CS
or Enhanced PS Outgoing Inter-RAT Handover for Cell
Counters
Counter ID
Counter Name
Counter Description
67192660
VS.IRATHO.FailOutCS.No
Reply

Timer Waiting for Iu Release
Command Expires in CS
Outgoing Inter-RAT
Handover for Cell
67192674
S.NoReply

Command Expires in
Enhanced PS Outgoing InterRAT Handover for Cell
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.The preceding
counters complies with section "8.5 Iu Release" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

2016
BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in the figure. During the CS or the Enhanced
PS outgoing inter-RAT handover, after sending the HANDOVER FROM UTRAN COMMAND
message, the RNC starts the timer waiting for the IU RELEASE COMMAND message from
the CN. If no message is received from the CN before the timer expires, these counters are
measured in the best cell that the UE camps on before the handover.
Figure 1-879 Timeout Waiting for Iu Release Command in CS or the Enhanced PS Outgoing
Inter-RAT Handover
Formula
None
Unit
None
Issue 03 (2015-06-30)

2017
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutCS.No
Reply
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
S.NoReply
WRFD-02030802
PS Handover Between
UMTS and GPRS
Number of Abnormally Terminated CS Outgoing Inter-RAT Handovers for Cell

Counters
Counter ID
Counter Name
Counter Description
73394018
VS.IRATHO.FailOutCS.Ab
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.This counter complies with section "8.3.7 Inter-RAT handover from
UTRAN" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

2018
BSC6900 UMTS
Figure 1-880 CS domain inter-RAT outgoing handover procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutCS.Ab
ort
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2019
BSC6900 UMTS
Number of Failed CS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio

Counters
Counter ID
Counter Name
Counter Description
73425012
VS.IRATHO.FailOutCS.InterRatRF
Number of Failed CS
Outgoing Inter-RAT
Handovers for Cell(Failure in
the Radio Interface
Procedure)
Description
This counter provides the number of IU RELEASE COMMAND messages that are received by
the RNC from the CN after the RNC sends HANDOVER FROM UTRAN COMMAND
messages to the UE and that contain the reason value "Failure in the Radio Interface Procedure."
This counter is measured in a CS inter-RAT handover and in the best cell before the
handover.This counter complies with section "8.3.7 Inter-RAT handover from UTRAN" in
3GPP TS 25.331 (v10.13.0).
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
Figure 1-881 Procedure for an outgoing inter-RAT handover in the CS domain
Issue 03 (2015-06-30)

2020
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutCS.InterRatRF
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Failed Outgoing Inter-RAT CS Handovers Due to Abnormal

Connection Release by CN for Cell (Unspecified Failure)
Counters
Counter ID
Counter Name
Counter Description
73426856
VS.IRATHO.FailOutCS.CN
UnspecFail

Inter-RAT CS Handovers
Due to Abnormal Connection
Release by CN for Cell
Description
This counter measures the number of outgoing inter-RAT CS handover failures caused by the
connection release triggered by the CN with the cause value "unspecified failure" in the best
cell.This counter complies with section "8.7 Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point D, as shown in the figure. During an outgoing inter-RAT
CS handover, if the RNC receives from the CN an IU RELEASE COMMAND message with
the cause value "unspecified failure" after sending a HANDOVER FROM UTRAN
Issue 03 (2015-06-30)

2021
BSC6900 UMTS
COMMAND message, this counter is increased by one in the best cell of the UE before the
handover.
Figure 1-882 CN release message with the cause value "unspecified failure" in the outgoing
inter-RAT CS handover procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutCS.CN
UnspecFail
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2022
BSC6900 UMTS
Number of Attempts to Obtain GSM System Information During RIM-based

NACCs Triggered by Inter-RAT PS Handovers
Counters
Counter ID
Counter Name
Counter Description
73425954
VS.IRATHO.AttNACC
Obtain GSM System
Information during RIMbased NACCs Triggered by
Inter-RAT PS Handovers for
Cell
Description
UMTS can exchange RIM information with GSM through the core network (CN) or
eCoordinator. The eCoordinator Supporting RIM Procedure switch controls whether the RIM
procedure is implemented through the CN or eCoordinator. When this switch is set to off, UMTS
exchanges RIM information with GSM through the CN. When this switch is set to on, UMTS
exchanges RIM information with GSM through the eCoordinator. 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. RIM is short for RAN information management and
NACC is short for network assisted cell change.This counter complies with section "8.34 Direct
Information Transfer" in 3GPP TS 25.413 (v10.10.0).
Measurement point
When the eCoordinator Supporting RIM Procedure switch is set to off, the measurement is
triggered at point A in figure 1. When the RNC sends a DIRECT INFORMATION TRANSFER
(RAN INFORMATION REQUEST) message to the CN during an NACC triggered by an interRAT PS handover, this counter is measured in the best cell under the SRNC.
Figure 1-883 RIM information flow over the Iu interface
Issue 03 (2015-06-30)

2023
BSC6900 UMTS
When the eCoordinator Supporting RIM Procedure switch is set to on, the measurement is
triggered at point A in figure 2. When the RNC sends an RNC DIRECT INFORMATION
TRANSFER (RAN INFORMATION REQUEST) message to the eCoordinator during an
NACC triggered by an inter-RAT PS handover, this counter is measured in the best cell under
the SRNC.
Figure 1-884 RIM information flow over the Sr interface
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttNACC
WRFD-02030801
NACC(Network Assisted
Cell Change)
MRFD-090211

Issue 03 (2015-06-30)

2024
BSC6900 UMTS
Number of Successful That GSM System Information Is Obtained During RIMbased NACCs Triggered by Inter-RAT PS Handovers
Counters
Counter ID
Counter Name
Counter Description
73425955
VS.IRATHO.SuccNACC
Number of Successful That

GSM System Information Is
Obtained during RIM-based
NACCs Triggered by InterRAT PS Handovers for Cell
Description
UMTS can exchange RIM information with GSM through the core network (CN) or
eCoordinator. The eCoordinator Supporting RIM Procedure switch controls whether the RIM
procedure is implemented through the CN or eCoordinator. When this switch is set to off, UMTS
exchanges RIM information with GSM through the CN. When this switch is set to on, UMTS
exchanges RIM information with GSM through the eCoordinator. This counter provides the
number of times that GSM system information is successfully obtained during RIM-based
NACCs triggered by inter-RAT PS handovers in the best cell. RIM is short for RAN information
management and NACC is short for network assisted cell change.This counter complies with
section "8.34 Direct Information Transfer" in 3GPP TS 25.413 (v10.10.0).
Measurement point
When the eCoordinator Supporting RIM Procedure switch is set to off, the measurement is
triggered at point B in figure 1. When the RNC receives a DIRECT INFORMATION
TRANSFER (RAN INFORMATION) message from the CN during an inter-RAT PS handover,
this counter is measured in the best cell under the SRNC.
Figure 1-885 RIM information flow over the Iu interface
Issue 03 (2015-06-30)

2025
BSC6900 UMTS
When the eCoordinator Supporting RIM Procedure switch is set to on, the measurement is
triggered at point B in figure 2. When the RNC receives an ECO DIRECT INFORMATION
TRANSFER (RAN INFORMATION) message from the eCoordinator during an NACC
triggered by an inter-RAT PS handover, this counter is measured in the best cell under the SRNC.
Figure 1-886 RIM information flow over the Sr interface
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccNACC
WRFD-02030801
NACC(Network Assisted
Cell Change)
MRFD-090211

Issue 03 (2015-06-30)

2026
BSC6900 UMTS
Number of Attempts to Obtain GSM System Information During Iur-g-based

ENACCs Triggered by Inter-RAT PS Handovers
Counters
Counter ID
Counter Name
Counter Description
73425956
VS.IRATHO.AttENACC
Obtain GSM System
Information During Iur-gbased ENACCs Triggered by
Inter-RAT PS Handovers for
Cell
Description
This counter provides the number of attempts to obtain GSM system information during Iur-gbased ENACCs triggered by Inter-RAT PS handovers in the best cell where the UE camps.
ENACC is short for evolved network assisted cell change.
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC sends the
BSC an INFORMATION EXCHANGE INITIATION REQUEST message which contains
NACC Related Data. This counter is measured in the best cell under the SRNC where the UE
is served.
Figure 1-887 Information exchange procedure between the RNC and BSC
Formula
None
Issue 03 (2015-06-30)

2027
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttENACC
WRFD-070005
NACC Procedure
Optimization Based on Iur-g
Number of Successful Times That GSM System Information Is Obtained During

Iur-g-based ENACCs Triggered by Inter-RAT PS Handovers
Counters
Counter ID
Counter Name
Counter Description
73425957
VS.IRATHO.SuccENACC

That GSM System
Information is Obtained
During Iur-g-based ENACCs
Triggered by Inter-RAT PS
Handovers for Cell
Description
This counter provides the number of successful times that GSM system information is obtained
during Iur-g-based ENACCs triggered by Inter-RAT PS handovers in the best cell where the
UE camps. ENACC is short for evolved network assisted cell change.
Measurement point
The measurement is triggered at point B shown in the following figure when the RNC receives
an INFORMATION EXCHANGE INITIATION REQUEST message which contains NACC
Related Data from the BSC. This counter is measured in the best cell under the SRNC where
the UE is served.
Issue 03 (2015-06-30)

2028
BSC6900 UMTS
Figure 1-888 Information exchange procedure between the RNC and BSC
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccENACC
WRFD-070005
NACC Procedure
Optimization Based on Iur-g
Number of PS Outgoing Inter-RAT Handover Attempts Initiated by RNC for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189742
AN.Load
Inter-RAT Handover
Cell

2029
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67189747
AN.RF
Inter-RAT Handover
Attempts Initiated by the
RNC Based on RF
Cell
67190411
Inter-RAT Handover
Attempts Initiated by RNC
for Cell
67190858
AN.Service
Inter-RAT Handover
Attempts Initiated by the
RNC Based on Service Type
for Cell
67191155
VS.IRATHO.HSDPA.AttOutPSUTRAN
Outgoing Handover
Attempts for HSDPA
Services for Cell
67192507
VS.IRATHO.HSUPA.AttOutPSUTRAN
Inter-RAT Handover
Attempts for HSUPA
Services for Cell
73425010
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.The preceding counters complies with section "8.3.11" in 3GPP TS 25.331
(v10.13.0).
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.
Issue 03 (2015-06-30)

2030
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
AN.Load
WRFD-020306

on Load
AN.RF
WRFD-020303

on Coverage
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
AN.Service
Issue 03 (2015-06-30)
WRFD-020305


on Service
2031
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.IRATHO.HSDPA.AttOutPSUTRAN
WRFD-01061006
HSDPA Mobility
Management
VS.IRATHO.HSUPA.AttOutPSUTRAN
WRFD-01061204
HSUPA Mobility
Management
AN.Sig
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of PS Outgoing Inter-RAT Handover Reattempts for Cell

Counters
Counter ID
Counter Name
Counter Description
73428085
.Retry
Inter-RAT Handover
Reattempts for Cell
Description
This counter measures the number of outgoing inter-RAT handover reattempts initiated on UEs
processing PS services in the best cell after an outgoing PS inter-RAT handover failure.This
counter complies with section "8.3.11 Inter-RAT cell change order from UTRAN" in 3GPP TS
25.331 (v10.13.0).
Measurement point
initiates an outgoing inter-RAT handover procedure on the UE. If the RNC receives a CELL
CHANGE ORDER FROM UTRAN FAILURE message from the UE, the RNC reattempts to
initiate an outgoing inter-RAT handover procedure on the UE, as shown by points C, D, and E
in the following figure. This counter is measured in the best cell for the UE under the SRNC
when the RNC sends a CELL CHANGE ORDER FROM UTRAN message to the UE.
Issue 03 (2015-06-30)

2032
BSC6900 UMTS
Figure 1-890 PS inter-RAT handover reattempt
Formula
None
Unit
None
Issue 03 (2015-06-30)

2033
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
.Retry
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Successful PS Outgoing Inter-RAT Handovers Initiated by RNC for

Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189743
RAN.Load
Outgoing Inter-RAT
Handovers Initiated by
Cell
67189748
RAN.RF
Outgoing Inter-RAT
Handovers Initiated by the
RNC Based on RF
Cell
67190412
Outgoing Inter-RAT
for Cell
67190859
RAN.Service
Outgoing Inter-RAT
RNC Based on Service Type
for Cell
67191156
VS.IRATHO.HSDPA.SuccOutPSUTRAN
Outgoing Inter-RAT
Handovers for HSDPA
Services for Cell

2034
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192506
VS.IRATHO.HSUPA.SuccOutPSUTRAN
Outgoing Inter-RAT
Handovers for HSUPA
Services for Cell
73425011
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.The preceding counters complies with section
"8.3.11" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

2035
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RAN.Load
WRFD-020306

on Load
RAN.RF
WRFD-020303

on Coverage
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
RAN.Service
WRFD-020305

on Service
VS.IRATHO.HSDPA.SuccOutPSUTRAN
WRFD-01061006
HSDPA Mobility
Management
VS.IRATHO.HSUPA.SuccOutPSUTRAN
WRFD-01061204
HSUPA Mobility
Management
RAN.Sig
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2036
BSC6900 UMTS
Number of Failed PS Outgoing Inter-RAT Handovers for Cell(No SRNS DATA

Forward cmd)
Counters
Counter ID
Counter Name
Counter Description
73425009
VS.IRATHO.FailOutPSUT
RAN.NoSRNSDataForwardCmd
Number of Failed PS
Outgoing Inter-RAT
Handovers for Cell(No
SRNS DATA Forward cmd)
Description
This counter provides the number of the PS outgoing inter-RAT handover fails in the best cell
because the timer waiting for the SRNS DATA FORWARD COMMAND message from CN
expires.This counter complies with section "8.12 SRNS Data Forwarding Initiation" in 3GPP
TS 25.413 (v10.10.0).
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-892 Procedure for a failed outgoing inter-RAT handover in the PS domain
Issue 03 (2015-06-30)

2037
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RAN.NoSRNSDataForwardCmd
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC for

Different Causes for Cell
Counters
Counter ID
Counter Name
Counter Description
67190476
IRATHO.FailOutPSUTRA
N.CfgUnsupp
Number of Failed PS
Outgoing Inter-RAT
(Configuration unsupported)
67190477
N.PhyChFail
Number of Failed PS
Outgoing Inter-RAT
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.The preceding counters complies with section "8.3.11 Inter-RAT cell
change order from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

2038
BSC6900 UMTS
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.
Figure 1-893 Failed PS outgoing inter-RAT handover initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
N.CfgUnsupp
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2039
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
N.PhyChFail
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
VS.IRATHO.FailOutPS
WRFD-020303
WRFD-020305
WRFD-020306

on Coverage
on Service
on Load
Number of Failed Outgoing UMTS-to-GSM PS Handovers due to UE Reselection

Back to a UTRAN Cell
Counters
Counter ID
Counter Name
Counter Description
73423107
VS.IRATHO.FailOutPS.UE
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 interRAT reselection parameters at the GSM and the handover parameters to check whether pingpong handovers exist.This counter complies with section "8.1.3 Signalling connection release
procedure" in 3GPP TS 25.331(v10.13.0).
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 is handed over back to a 3G cell soon after it is handed over to a 2G cell and sends an
Issue 03 (2015-06-30)

2040
BSC6900 UMTS
RRC connection setup request before the RNC receives an IU RELEASE COMMAND message
from the CN.
Figure 1-894 Inter-RAT handovers abnormal procedure caused by an RRC connection setup
request
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 RNC receives an IU RELEASE COMMAND message with the cause value of "UE
generated signalling connection release" from the CN.
Issue 03 (2015-06-30)

2041
BSC6900 UMTS
Figure 1-895 Inter-RAT handovers abnormal procedure caused by the IU REL procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutPS.UE
Gen
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2042
BSC6900 UMTS
Number of RL Reestablishment Attempts After UEs Failed to Receive the PS

Outgoing Inter-RAT Handover Command for Cell
Counters
Counter ID
Counter Name
Counter Description
73425927
VS.IRATHOPS.Cancel.ReEstab
Number of RL
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.This
(v10.13.0).
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.
Issue 03 (2015-06-30)

2043
BSC6900 UMTS
Figure 1-896 RL reestablishment during a PS outgoing inter-RAT handover
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.
Issue 03 (2015-06-30)

2044
BSC6900 UMTS
Figure 1-897 RL reestablishment during a CS or enhanced PS outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHOPS.Cancel.ReEstab
WRFD-020303

on Coverage
WRFD-020306
WRFD-020305

on Load
on Service
Issue 03 (2015-06-30)

2045
BSC6900 UMTS
Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Signalling

Connection Release Indication)
Counters
Counter ID
Counter Name
Counter Description
73425008
RAN.SCRI
Number of Failed PS
Outgoing Inter-RAT
Handovers for Cell
(Signalling Connection
Release Indication)
Description
This counter provides the number of the CS outgoing inter-RAT handover fails in the best cell
because the RNC receives SIGNALLING CONNECTION RELEASE INDICATION from the
UE.This counter complies with section "8.1.14 Signalling connection release indication
procedure" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure.During the PS outgoing interRAT handover, if the RNC receives a SIGNALLING CONNECTION RELEASE
INDICATION message after sending the CELL CHANGE ORDER FROM UTRAN message.In
this case, this counter is increased by one in the best cell that the UE camps on before the
handover.
Figure 1-898 Procedure for a failed outgoing inter-RAT handover in the PS domain
Issue 03 (2015-06-30)

2046
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RAN.SCRI
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Times that the Timer Waiting for Iu Release Command Expires in PS
Outgoing Inter-RAT Handover Initiated by RNC for Cell
Counters
Counter ID
Counter Name
Counter Description
67192661
RAN.NoReply

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.This
25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure. During the PS outgoing interRAT handover, if the RNC receives no CELL CHANGE ORDER FROM UTRAN FAILURE
message from the UE after sending the CELL CHANGE ORDER FROM UTRAN message and
Issue 03 (2015-06-30)

2047
BSC6900 UMTS
the timer waiting for the IU RELEASE COMMAND message from the CN expires, this counter
is measured in the best cell that the UE camps on before handover.
Figure 1-899 Timeout waiting for Iu Release Command in PS Outgoing Inter-RAT Handover
Initiated by RNC
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RAN.NoReply
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2048
BSC6900 UMTS
Number of Abnormally Terminated PS Outgoing Inter-RAT Handovers for Cell

Counters
Counter ID
Counter Name
Counter Description
73394022
VS.IRATHO.FailOutPS.Ab
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.This counter complies with section "8.5 Iu Release" in 3GPP TS
25.413 (v10.10.0).
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
Issue 03 (2015-06-30)

2049
BSC6900 UMTS
Figure 1-900 PS domain inter-RAT outgoing handover procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ort
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2050
BSC6900 UMTS
Number of Failed PS Outgoing Inter-RAT Handovers for Cell(Failure in the Radio

Counters
Counter ID
Counter Name
Counter Description
73425013
RAN.InterRatRF
Number of Failed PS
Outgoing Inter-RAT
Handovers for Cell(Failure in
the Radio Interface
Procedure)
Description
This counter provides the number of IU RELEASE COMMAND messages that are received by
the RNC from the CN after the RNC sends CELL CHANGE ORDER FROM UTRAN messages
to the UE and that contain the reason value "Failure in the Radio Interface Procedure." This
counter is measured in a PS inter-RAT handover and in the best cell before the handover.This
25.331 (v10.13.0).
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
Figure 1-901 Procedure for an outgoing inter-RAT handover in the PS domain
Issue 03 (2015-06-30)

2051
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RAN.InterRatRF
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Failed Outgoing Inter-RAT PS Handovers Due to Abnormal

Connection Release by CN for Cell (Unspecified Failure)
Counters
Counter ID
Counter Name
Counter Description
73426857
RAN.CNUnspecFail

Inter-RAT PS Handovers
Due to Abnormal Connection
Release by CN for Cell
Description
This counter measures the number of outgoing inter-RAT PS handover failures caused by the
connection release triggered by the CN with the cause value "unspecified failure" in the best
cell.This counter complies with section "8.7 Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point C, as shown in the figure. During an outgoing inter-RAT
PS handover, if the RNC receives from the CN an IU RELEASE COMMAND message with
the cause value "unspecified failure" after sending a CELL CHANGE ORDER FROM UTRAN
message, this counter is increased by one in the best cell of the UE before the handover.
Issue 03 (2015-06-30)

2052
BSC6900 UMTS
Figure 1-902 CN release message with the cause value "unspecified failure" in the outgoing
inter-RAT PS handover procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RAN.CNUnspecFail
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2053
BSC6900 UMTS
Number of PS Outgoing Inter-RAT Handover Requests Initiated by UE for Cell

Counters
Counter ID
Counter Name
Counter Description
67190413
Outgoing Inter-RAT
Handover Requests Initiated
by UE for Cell
Description
This counter provides the number of attempts of Cell Reselection in inter-RAT initiated by the
UE in the Cell. 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 inter-RAT network based on the cell
reselection criteria. After the UE reselects the inter-RAT network, it sets up PS services again.
During the PS service setup, the 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.This counter complies with section "8.3.9 Inter-RAT cell reselection from UTRAN
Inter-RAT cell reselection from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
the CN an SRNS CONTEXT REQUEST message that does not carry the RAT type or carries
a RAT type other than UTRAN during a PS inter-RAT outgoing handover, the counter is
measured in the best cell that the UE camps on before the handover.
Issue 03 (2015-06-30)

2054
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Successful PS Outgoing Inter-RAT Handovers Initiated by UE for Cell

Counters
Counter ID
Counter Name
Counter Description
67189763
IRATHO.SuccOutPSUE
Outgoing Inter-RAT
Handovers Initiated by UE
for Cell
Description
This counter provides the number of successful of Cell Reselection in inter-RAT initiated by
the UE in the Cell. 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 inter-RAT network based on the cell
reselection criteria. After the UE reselects the inter-RAT network, it sets up PS services again.
During the PS service setup, the 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.This counter complies with section in 3GPP TS 25.331 (v10.13.0)"8.3.9 Inter-RAT
cell change order to UTRAN"
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.
If the SRNS CONTEXT REQUEST message in the procedure does not carry the RAT type or
Issue 03 (2015-06-30)

2055
BSC6900 UMTS
carries a RAT type other than UTRAN, this counter is measured in the cell that the UE camps
on before handover.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
IRATHO.SuccOutPSUE
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2056
BSC6900 UMTS
Number of Preparation Attempts for CS Only SRVCC Handovers (a Single

Common Call or Emergency Call) for Cell
Counters
Counter ID
Counter Name
Counter Description
73427977
VS.SRVCC.L2U.AttRelocPrepInCS
Attempts for CS Only
SRVCC Handovers (a Single
Common Call or Emergency
Call) for Cell
73427980
VS.SRVCC.L2U.AttRelocP
repInCS.Emerg
Attempts for CS Only
SRVCC Handovers (a Single
Emergency Call) for Cell
Description
This counter provides the number of preparation attempts for CS only SRVCC handovers (a
single common call or emergency call). This counter is incremented in target cells specified in
RELOCATION REQUEST messages.This counter complies with section "8.7 Relocation
Measurement point
The measurement is triggered at point A shown in the following figure. During a CS only SRVCC
handover, upon receiving a RELOCATION REQUEST message from the CN, the RNC triggers
the incoming inter-RAT CS handover preparation procedure. Then, this counter is incremented
in the target cell specified by the TargetCellId IE in the RELOCATION REQUEST message.
Issue 03 (2015-06-30)

2057
BSC6900 UMTS
Figure 1-905 Successful incoming inter-RAT CS handover
Formula
None
Unit
None
Related Features
None
Number of Preparations for CS or Enhanced PS Incoming Inter-RAT Handover for

Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189758
VS.IRATHO.AttRelocPrepInCS

CS Incoming Inter-RAT
Handover for Cell
67192675
VS.IRATHO.AttRelocPrepInPS

Enhanced PS Incoming InterRAT Handover for Cell

2058
BSC6900 UMTS
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.The preceding
counters complies with section "8.7 Relocation Resource Allocation" in 3GPP TS 25.413
(v10.10.0).
Measurement point
the CN a RELOCATION REQUEST message during the CS or the Enhanced PS incoming interRAT handover. In this case, the preparation for CS or Enhanced PS incoming inter-RAT
handover is triggered and these counters are measured according to the value of TargetCellId in
the RELOCATION REQUEST message.
Figure 1-906 Normal CS or the Enhanced PS incoming inter-RAT handover
Formula
None
Unit
None
Issue 03 (2015-06-30)

2059
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttRelocPrepInCS
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
VS.IRATHO.AttRelocPrepInPS
WRFD-02030802
PS Handover Between
UMTS and GPRS
Number of Preparation Attempts for Incoming PS Only L2U Handovers in Cell

Counters
Counter ID
Counter Name
Counter Description
73427898
Attempts for Incoming PS
Only L2U Handovers in Cell
Description
This counter provides the number of preparation attempts for incoming LTE-to-UMTS (L2U)
handovers of only PS services (including single and multiple PS services) in a cell.This counter
complies with section "8.7 Relocation Resource Allocation" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A, as shown in the following figure. When the RNC
receives a RELOCATION REQUEST message from the CN and determines that the incoming
L2U handover is to be performed for only PS services, this counter is increased by one in the
cell that is specified by the TargetCellId IE in the message.
Issue 03 (2015-06-30)

2060
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-140102

LTE Emergency Calls

2061
BSC6900 UMTS
Number of Attempts at Incoming PS LTE-to-UMTS Handovers Triggered by CSFB

for Cell
Counters
Counter ID
Counter Name
Counter Description
73426146
CS.CELL
Number of Attempts at
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.This counter
Measurement point
When the RNC receives a RELOCATION REQUEST message from the CN, this counter is
increased by one in the cell that is specified by the TargetCellId IE in the message if the "Source
RNC To Target RNC Transparent Container" IE in the RELOCATION REQUEST message
carries a CSFB flag or the Cause IE in the message is set to "CS Fallback triggered." The
measurement is triggered at point A, as shown in the following figure.
Figure 1-908 CSFB signaling procedure initiated on the LTE side
Issue 03 (2015-06-30)

2062
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CS.CELL
WRFD-140102

LTE Emergency Calls
Number of Preparation Attempts for Incoming LTE-to-UMTS CS+PS Handovers

Triggered by SRVCC for VoIP Services
Counters
Counter ID
Counter Name
Counter Description
73425820
VS.SRVCC.L2U.AttRelocPrepInCSPS
Attempts for Incoming LTEto-UMTS CS+PS Handovers
73427985
repInCSPS.Emerg
Attempts for CS+PS SRVCC
Handovers (Emergency
Calls) for Cell
Description
This counter provides the number of preparation attempts for CS+PS SRVCC handovers
(common calls or emergency calls). This counter is incremented in target cells specified in
RELOCATION REQUEST messages. In a CS+PS SRVCC handover, the voice over Internet
Protocol (VoIP) service is handed over from the LTE network to the CS domain of the UMTS
network, and the PS service is handed over from the LTE network to the PS domain of the UMTS
network. On the UMTS RAN side, the procedure for the CS+PS SRVCC handover is identical
to that for an incoming inter-RAT CS+PS handover.The preceding counters complies with
section "8.7 Relocation Resource Allocation" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A shown in the following figure. During a CS+PS SRVCC
handover, upon receiving two RELOCATION REQUEST messages from the CN, the RNC
Issue 03 (2015-06-30)

2063
BSC6900 UMTS
determines whether the messages indicate an incoming CS+PS handover request from the LTE
network. If so, the RNC triggers the incoming inter-RAT CS+PS handover preparation
procedure. Then, this counter is incremented in the target cell specified by the TargetCellId IE
in the RELOCATION REQUEST messages.
Figure 1-909 Procedure of SRVCC inter-RAT handover
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRVCC.L2U.AttRelocPrepInCSPS
WRFD-150215
SRVCC from LTE to UMTS

with PS Handover

2064
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
repInCSPS.Emerg
WRFD-150215

with PS Handover
Number of Successful Preparations for CS or Enhanced PS Incoming Inter-RAT

Handover for Cell
Counters
Counter ID
Counter Name
Counter Description
67190414
preparations for CS
Incoming Inter-RAT
Handovers for Cell
67192676
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.The
preceding counters complies with section "8.7 Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends the CN a
RELOCATION REQUEST ACKNOWLEDGE message during the CS or the Enhanced PS
incoming inter-RAT handover. In this case, these counters are measured according to the value
of TargetCellId in the RELOCATION REQUEST message.
Issue 03 (2015-06-30)

2065
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)
WRFD-02030802

PS Handover Between
UMTS and GPRS
2066
BSC6900 UMTS
Number of Successful Preparation Attempts for CS Only SRVCC Handovers (a

Single Common Call or Emergency Call) for Cell
Counters
Counter ID
Counter Name
Counter Description
73427978
VS.SRVCC.L2U.SuccRelocPrepInCS
Preparation Attempts for CS
Only SRVCC Handovers (a
Single Common Call or
73427981
VS.SRVCC.L2U.SuccReloc
PrepInCS.Emerg
Only SRVCC Handovers (a
Single Emergency Call) for
Cell
Description
This counter provides the number of successful preparation attempts for CS only SRVCC
handovers (a single common call or emergency call). This counter is incremented in target cells
specified in RELOCATION REQUEST messages.This counter complies with section "8.7
Relocation Resource Allocation" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B shown in the following figure. During a CS only SRVCC
the incoming inter-RAT CS handover preparation procedure. If the RNC sends a RELOCATION
REQUEST ACKNOWLEDGE message to the CN, this counter is incremented in the target cell
specified by the TargetCellId IE in the RELOCATION REQUEST message.
Issue 03 (2015-06-30)

2067
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
Number of Successful Preparations for Incoming PS Only L2U Handovers in Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73427899
Preparations for Incoming PS
Only L2U Handovers in Cell

2068
BSC6900 UMTS
Description
This counter provides the number of successful preparations for incoming LTE-to-UMTS (L2U)
handovers of only PS services (including single and multiple PS services) in a cell.This counter
Measurement point
The measurement is triggered at point B, as shown in the following figure. After the RNC
receives a RELOCATION REQUEST message from the CN, if it determines that the incoming
L2U handover is to be performed for only PS services and responds with a RELOCATION
REQUEST ACKNOWLEDGE message, this counter is increased by one in the cell that is
specified by the TargetCellId IE in the RELOCATION REQUEST message.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-140102

LTE Emergency Calls

2069
BSC6900 UMTS
Number of Successful Preparations for Incoming PS LTE-to-UMTS Handovers

Triggered by CSFB for Cell
Counters
Counter ID
Counter Name
Counter Description
73426148
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.This counter complies with section "8.7 Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
Measurement point
When the RNC sends the CN a RELOCATION REQUEST ACKNOWLEDGE message, this
counter is increased by one in the cell that is specified by the TargetCellId IE in the corresponding
RELOCATION REQUEST message if the "Source RNC To Target RNC Transparent
Container" IE in the RELOCATION REQUEST message carries a CSFB flag or the Cause IE
in the message is set to "CS Fallback triggered." The measurement is triggered at point B, as
shown in the following figure.
Issue 03 (2015-06-30)

2070
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
S.CS.CELL
WRFD-140102

LTE Emergency Calls
Number of Successful Preparations for Incoming LTE-to-UMTS CS+PS Handovers

Triggered by SRVCC for VoIP Services
Counters
Counter ID
Counter Name
Counter Description
73425821
VS.SRVCC.L2U.SuccRelocPrepInCSPS
Preparations for Incoming
LTE-to-UMTS CS+PS
for Cell
73427986
PrepInCSPS.Emerg
+PS SRVCC Handovers
(Emergency Calls) for Cell
Description
This counter provides the number of successful preparation attempts for CS+PS SRVCC
handovers (common calls or emergency calls). This counter is incremented in target cells
specified in RELOCATION REQUEST messages. In a CS+PS SRVCC handover, the voice
over Internet Protocol (VoIP) service is handed over from the LTE network to the CS domain
of the UMTS network, and the PS service is handed over from the LTE network to the PS domain
of the UMTS network. On the UMTS RAN side, the procedure for the CS+PS SRVCC handover
is identical to that for an incoming inter-RAT CS+PS handover.The preceding counters complies
with section "8.7 Relocation Resource Allocation" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

2071
BSC6900 UMTS
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 for a CS+PS SRVCC
handover. Then, this counter is incremented in the target cell specified by the TargetCellId IE
in the RELOCATION REQUEST messages.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRVCC.L2U.SuccRelocPrepInCSPS
WRFD-150215

with PS Handover

2072
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
PrepInCSPS.Emerg
WRFD-150215

with PS Handover
Number of CS Incoming Inter-RAT Handover Attempts for Cell

Counters
Counter ID
Counter Name
Counter Description
73394014
VS.IRATHO.AttInCS
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.This counter complies with section "8.3.6 Inter-RAT
handover to UTRAN" in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

2073
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttInCS
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2074
BSC6900 UMTS
Number of Incoming LTE-to-UMTS CS+PS Handover Attempts Triggered by

Counters
Counter ID
Counter Name
Counter Description
73425822
VS.SRVCC.L2U.AttInCSPS
Number of Incoming LTEto-UMTS CS+PS Handover

Attempts Triggered by
for Cell
Description
This counter provides the number of CS+PS SRVCC handover attempts (common calls or
emergency calls). This counter is incremented in target cells specified in RELOCATION
REQUEST messages. In a CS+PS SRVCC handover, the voice over Internet Protocol (VoIP)
service is handed over from the LTE network to the CS domain of the UMTS network, and the
PS service is handed over from the LTE network to the PS domain of the UMTS network. On
the UMTS RAN side, the procedure for the CS+PS SRVCC handover is identical to that for an
incoming inter-RAT CS+PS handover.This counter complies with section "8.3.6 Inter-RAT
handover to UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point C shown in the following figure. During a CS+PS SRVCC
handover, the RNC sends two RELOCATION REQUEST ACKNOWLEDGE messages to the
CN and the handover preparation procedure is complete. After this, if the RNC receives a
HANDOVER TO UTRAN COMPLETE message from the UE, this counter is incremented in
the target cell specified by the TargetCellId IE in the RELOCATION REQUEST messages.
Issue 03 (2015-06-30)

2075
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRVCC.L2U.AttInCSPS
WRFD-150215

with PS Handover

2076
BSC6900 UMTS
Number of Successful CS or Enhanced PS Incoming Inter-RAT Handovers for Cell

Counters
Counter ID
Counter Name
Counter Description
67189759
VS.IRATHO.SuccInCS
Incoming Inter-RAT
Handovers for Cell
67192677
Enhanced PS Incoming InterRAT 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.
Counter Name
Description
VS.IRATHO.SuccInCS
This counter ccomplies with section "8.3.6

Inter-RAT handover to UTRAN" in 3GPP TS
25.331 (v10.13.0).

Relocation Complete" in 3GPP TS 25.413
(v10.10.0).
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.
Issue 03 (2015-06-30)

2077
BSC6900 UMTS
Figure 1-917 Normal CS or the Enhanced PS incoming inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccInCS
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)
WRFD-02030802

PS Handover Between
UMTS and GPRS
2078
BSC6900 UMTS
Number of Successful CS Only SRVCC Handover Attempts (a Single Common

Call or Emergency Call) for Cell
Counters
Counter ID
Counter Name
Counter Description
73427979
VS.SRVCC.L2U.SuccRelocInCS
Only SRVCC Handover
Attempts (a Single Common
Call or Emergency Call) for
Cell
73427982
InCS.Emerg
Only SRVCC Handover
Attempts (a Single
Description
This counter provides the number of successful CS only SRVCC handover attempts (a single
common call or emergency call). This counter is incremented in target cells specified in
RELOCATION REQUEST messages.This counter complies with section "8.9 Relocation
Complete" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point C shown in the following figure. During a CS only SRVCC
the incoming inter-RAT CS handover preparation procedure. If the RNC sends a RELOCATION
COMPLETE message to the CN, this counter is incremented in the target cell specified by the
TargetCellId IE in the RELOCATION REQUEST message.
Issue 03 (2015-06-30)

2079
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
Number of Successful Incoming PS Only L2U Handovers in Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73427900
Incoming PS Only L2U
Handovers in Cell

2080
BSC6900 UMTS
Description
This counter provides the number of successful incoming LTE-to-UMTS (L2U) handovers of
only PS services (including single and multiple PS services) in a cell.This counter complies with
section "8.7 Relocation Resource Allocation" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point D, as shown in the following figure. After the RNC
receives a RELOCATION REQUEST message from the CN, it responds with a RELOCATION
COMPLETE message if the incoming L2U handover is to be performed for only PS services.
This counter is increased by one in the cell that is specified by the TargetCellId IE in the
RELOCATION REQUEST message when the RNC sends the RELOCATION COMPLETE
message to the CN.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2081
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-140102

LTE Emergency Calls
Number of Successful Incoming PS LTE-to-UMTS Handovers Triggered by CSFB

for Cell
Counters
Counter ID
Counter Name
Counter Description
73426147
VS.L2U.SuccRelocInPS.CS.
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.This counter
complies with section "8.9 Relocation Complete" in 3GPP TS 25.413 (v10.10.0).
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.
Issue 03 (2015-06-30)

2082
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.L2U.SuccRelocInPS.CS.
CELL
WRFD-140102

LTE Emergency Calls

2083
BSC6900 UMTS
Number of Successful Incoming LTE-to-UMTS CS+PS Handovers Triggered by

Counters
Counter ID
Counter Name
Counter Description
73425823
VS.SRVCC.L2U.SuccInCSPS
Incoming LTE-to-UMTS CS
+PS Handovers Triggered by
for Cell
73427987
InCSPS.Emerg
+PS SRVCC Handover
Attempts (Emergency Calls)
for Cell
Description
This counter provides the number of successful CS+PS SRVCC handover attempts (common
calls or emergency calls). This counter is incremented in target cells specified in RELOCATION
REQUEST messages. In a CS+PS SRVCC handover, the voice over Internet Protocol (VoIP)
service is handed over from the LTE network to the CS domain of the UMTS network, and the
PS service is handed over from the LTE network to the PS domain of the UMTS network. On
the UMTS RAN side, the procedure for the CS+PS SRVCC handover is identical to that for an
incoming inter-RAT CS+PS handover.The preceding counters complies with section "8.3.6
Inter-RAT handover to UTRAN" in 3GPP TS 25.331 (v10.13.0).
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 for a CS+PS SRVCC handover. Then,
this counter is incremented in the target cell specified by the TargetCellId IE in the
RELOCATION REQUEST messages.
Issue 03 (2015-06-30)

2084
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRVCC.L2U.SuccInCSPS
WRFD-150215

with PS Handover
InCSPS.Emerg
WRFD-150215

with PS Handover

2085
BSC6900 UMTS
Number of Failed Preparations for CS or Enhanced PS Incoming Inter-RAT

Handover for Different Causes for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189760
InCS.TRNCSysFailReloc
Number of Failed
Preparations for CS
Incoming Inter-RAT
Handover (Relocation failure
in target CN/RNC or target
system)
67189761
InCS.TRNCSysRelocUnsupp
Number of Failed
Preparations for CS
Incoming Inter-RAT
Handover (Relocation not
supported in target RNC or
target system)
67189762
InCS.ResUnavail
Number of Failed
Preparations for CS
Incoming Inter-RAT
Handover (No resource
available)
67192187
InCS.TgtHighLoad
Number of Failed
Preparations for CS
Incoming Inter-RAT
Handover (Traffic Load In
The Target Cell Higher Than
In The Source Cell)
67192678
InPS.TgtFail
Number of Failed
Handover for cell
67192679
InPS.ReloUnSupp
Number of Failed
Handover for cell
target RNC or target system)

2086
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192680
InPS.ResUnavail
Number of Failed
Handover for cell (No
resource available)
67192681
InPS.TgtHighLoad
Number of Failed
Handover for cell (Traffic
Cell)
73428677
VS.L2U.IRATHO.FailReloc
PrepInCS.TgtFail
Number of Failed
Preparations for CS
Incoming L2U Inter-RAT
Handover for Cell
73428678
PrepInCS.RelocUnSupp
Number of Failed
Preparations for CS
Handover for Cell
target RNC or target system)
73428679
PrepInCS.ResUnavail
Number of Failed
Preparations for CS
resource available)
73428680
PrepInCS.TgtHighLoad
Number of Failed
Preparations for CS
Cell)
73428681
PrepInPS.TgtFail
Number of Failed
Preparations for PS Incoming
L2U Inter-RAT Handover
for Cell (Relocation failure in
target CN/RNC or target
system)

2087
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428682
PrepInPS.ReloUnSupp
Number of Failed
for Cell (Relocation not
supported in target RNC or
target system)
73428683
PrepInPS.ResUnavail
Number of Failed
for Cell (No resource
available)
73428684
PrepInPS.TgtHighLoad
Number of Failed
for Cell (Traffic Load In The
Target Cell Higher Than In
The Source Cell)
Description
These counters provide the number of failed preparations for CS or Enhanced PS incoming interRAT handover due to different causes according to the target cell ID in the relocation request.The
preceding counters complies with section "8.7 Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
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-922 Failed incoming inter-RAT handover
Issue 03 (2015-06-30)

2088
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
InCS.TRNCSysFailReloc
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
InCS.TRNCSysRelocUnsupp
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
InCS.ResUnavail
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
InCS.TgtHighLoad
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
InPS.TgtFail
Issue 03 (2015-06-30)
WRFD-02030802

PS Handover Between
UMTS and GPRS
2089
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
InPS.ReloUnSupp
WRFD-02030802
PS Handover Between
UMTS and GPRS
InPS.ResUnavail
WRFD-02030802
PS Handover Between
UMTS and GPRS
InPS.TgtHighLoad
WRFD-02030802
PS Handover Between
UMTS and GPRS
PrepInPS.TgtFail
WRFD-140102

LTE Emergency Calls
PrepInPS.ReloUnSupp
WRFD-140102

LTE Emergency Calls
PrepInPS.ResUnavail
WRFD-140102

LTE Emergency Calls
PrepInPS.TgtHighLoad
WRFD-140102

LTE Emergency Calls
Number of Incoming Inter-RAT Handover Preparation Failures (Iu RELEASE

COMMAND Received) for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73394017
InCS.Abort
Inter-RAT Handover
Preparation Failures for Cell
(Iu RELEASE COMMAND
Received)
73428685
PrepInCS.Abort
Number of Failed
Preparations for CS
Handover for Cell (IU
RELEASE COMMAND
message)
73428686
PrepInPS.Abort
Number of Failed
for Cell (IU RELEASE
COMMAND message)

2090
BSC6900 UMTS
Description
This counter provides the number of times that the CS or PS incoming inter-RAT handover
preparation fails because an IU RELEASE COMMAND message is received according to the
target cell ID in the relocation request.The preceding counters complies with section "8.5 Iu
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-923 inter-RAT incoming handover preparation
Formula
None
Unit
None
Issue 03 (2015-06-30)

2091
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
InCS.Abort
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
PrepInPS.Abort
WRFD-140102

LTE Emergency Calls
Number of Failed Preparation Attempts for CS+PS SRVCC Handovers Due to

Timeout in the LTE CS Domain for Cell
Counters
Counter ID
Counter Name
Counter Description
73427983
VS.SRVCC.FailRelocPrepI
nCSPS.CSTimeOut
Number of Failed
+PS SRVCC Handovers Due
to Timeout in the LTE CS
Domain for Cell
Description
During the incoming inter-RAT CS+PS handover preparation procedure for a CS+PS SRVCC
handover, the RNC receives a RELOCATION REQUEST message for the PS service from the
CN. However, the RNC does not receive a RELOCATION REQUEST message for the CS
service in time. As a result, the handover preparation fails. This counter provides the number of
such handover preparation failures in target cells specified in RELOCATION REQUEST
messages.This counter complies with section "8.7 Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A shown in the following figure. During the incoming
inter-RAT CS+PS handover preparation procedure for a CS+PS SRVCC handover, the RNC
starts a timer upon receiving a RELOCATION REQUEST message for the PS service. If the
RNC does not receive a RELOCATION REQUEST message for the CS service from the CN
before the timer expires, this counter is incremented in the target cell specified by the
TargetCellId IE in the RELOCATION REQUEST message for the PS service.
Issue 03 (2015-06-30)

2092
BSC6900 UMTS
Figure 1-924 Incoming inter-RAT CS+PS handover not going on well
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
nCSPS.CSTimeOut
WRFD-150215

with PS Handover

2093
BSC6900 UMTS
Number of Failed Preparation Attempts for CS+PS SRVCC Handovers Due to

Timeout in the LTE PS Domain for Cell
Counters
Counter ID
Counter Name
Counter Description
73427984
nCSPS.PSTimeOut
Number of Failed
+PS SRVCC Handovers Due
to Timeout in the LTE PS
Domain for Cell
Description
During the incoming inter-RAT CS+PS handover preparation procedure for a CS+PS SRVCC
handover, the RNC receives a RELOCATION REQUEST message for the CS service from the
CN. However, the RNC does not receive a RELOCATION REQUEST message for the PS
service in time. As a result, the handover preparation fails. This counter provides the number of
such handover preparation failures in target cells specified in RELOCATION REQUEST
messages.This counter complies with section "8.7 Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A shown in the following figure. During the incoming
inter-RAT CS+PS handover preparation procedure for a CS+PS SRVCC handover, the RNC
starts a timer upon receiving a RELOCATION REQUEST message for the CS service. If the
RNC does not receive a RELOCATION REQUEST message for the PS service from the CN
before the timer expires, this counter is incremented in the target cell specified by the
TargetCellId IE in the RELOCATION REQUEST message for the CS service.
Issue 03 (2015-06-30)

2094
BSC6900 UMTS
Figure 1-925 Incoming inter-RAT CS+PS handover not going on well
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
nCSPS.PSTimeOut
WRFD-150215

with PS Handover

2095
BSC6900 UMTS
Number of Failed CS or Enhanced PS Inter-RAT Incoming Handovers Due to No

Response from UE for Cell
Counters
Counter ID
Counter Name
Counter Description
67190410
VS.IRATHO.FailInCS.NoR
eply
Number of Failed CS InterRAT Incoming Handovers

Due to No Response from UE
for Cell
67192682
VS.IRATHO.FailRelocInPS
.NoReply

Handovers Due to UE
Response Timeout for Cell
73428687
InCS.NoReply
Number of Failed CS
Handovers Due to UE
73428688
InPS.NoReply
Number of Failed PS
Handovers Due to UE
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.This
(v10.13.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.IRATHO.FailRelocInPS.NoReply

Relocation Resource Allocation" in 3GPP TS
25.413 (v10.10.0).
VS.L2U.IRATHO.FailRelocInCS.NoReply

25.331 (v10.13.0).
VS.L2U.IRATHO.FailRelocInPS.NoReply

25.331 (v10.13.0).

2096
BSC6900 UMTS
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.
Figure 1-926 Failed CS Inter-RAT Incoming Handovers
Formula
None
Unit
None
Issue 03 (2015-06-30)

2097
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailInCS.NoR
eply
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
VS.IRATHO.FailRelocInPS
.NoReply
WRFD-02030802
PS Handover Between
UMTS and GPRS
InPS.NoReply
WRFD-140102

LTE Emergency Calls
Counters Related to the Number of Inter-RAT Measurement Expiry for Cell

Counters
Counter ID
Counter Name
Counter Description
67193399
VS.IRATHO.OutCS.MeasTimeOut
Measurement Expiry for Cell
67193400
VS.IRATHO.OutPS.MeasTimeOut
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.The preceding
counters complies with section "8.4.1 Measurement control" in 3GPP TS 25.331(v10.13.0).
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
Issue 03 (2015-06-30)

2098
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.OutCS.MeasTimeOut
WRFD-020303

on Coverage
WRFD-020309

on DL QoS
VS.IRATHO.OutPS.MeasTimeOut
WRFD-020303
WRFD-020309

on Coverage
on DL QoS
Number of Incoming L2U CS+PS Handover Preparation Attempts Triggered by

Ultra-Flash CSFB for Cell
Counters
Counter ID
Counter Name
Counter Description
73428827
VS.L2U.AttRelocPrepIn.UltraFlashCSFB
Number of Incoming L2U

CS+PS Handover
Triggered by Ultra-Flash
CSFB for Cell
Description
This counter measures the number of incoming L2U CS+PS handover preparation attempts
triggered by Ultra-Flash CSFB based on the target cell ID in the RELOCATION REQUEST
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A in the following figure. During an incoming L2U CS
+PS handover triggered by Ultra-Flash CSFB, when the RNC receives a RELOCATION
REQUEST message from the CN, this counter is measured based on the value of TargetCellId
in the message.
Issue 03 (2015-06-30)

2099
BSC6900 UMTS
Figure 1-927 Procedure of Ultra-Flash CSFB
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.L2U.AttRelocPrepIn.UltraFlashCSFB
WRFD-160271
Ultra-Flash CSFB

2100
BSC6900 UMTS
Number of Successful Incoming L2U CS+PS Handover Preparations Triggered by

Counters
Counter ID
Counter Name
Counter Description
73428828
VS.L2U.SuccRelocPrepIn.U
ltraFlashCSFB
Incoming L2U CS+PS
Triggered by Ultra-Flash
CSFB for Cell
Description
This counter measures the number of successful incoming L2U CS+PS handover preparations
triggered by Ultra-Flash CSFB based on the target cell ID in the RELOCATION REQUEST
25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B in the following figure. During an incoming L2U CS
+PS handover triggered by Ultra-Flash CSFB, when the RNC sends a RELOCATION
REQUEST ACKNOWLEDGE message to the CN, this counter is measured based on the value
of TargetCellId in the RELOCATION REQUEST message.
Issue 03 (2015-06-30)

2101
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.L2U.SuccRelocPrepIn.U
ltraFlashCSFB
WRFD-160271
Ultra-Flash CSFB

2102
BSC6900 UMTS
Number of Successful Incoming L2U CS+PS Handovers Triggered by Ultra-Flash

CSFB for Cell
Counters
Counter ID
Counter Name
Counter Description
73428829
VS.L2U.SuccRelocIn.UltraFlashCSFB
Incoming L2U CS+PS
Description
This counter measures the number of successful incoming L2U CS+PS handovers triggered by
Ultra-Flash CSFB based on the target cell ID in the RELOCATION REQUEST message.This
counter complies with section "8.9 Relocation Complete" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point C in the following figure. During an incoming L2U CS
+PS handover triggered by Ultra-Flash CSFB, when the RNC sends a RELOCATION
COMPLETE message to the CN, this counter is measured based on the value of TargetCellId
in the RELOCATION REQUEST message.
Issue 03 (2015-06-30)

2103
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.L2U.SuccRelocIn.UltraFlashCSFB
WRFD-160271
Ultra-Flash CSFB
Number of Failed Preparations for L2U CS+PS Handovers for Cell

Counters
Counter ID
Counter Name
Counter Description
73430224
PrepInCSPS.ResUnavail
Number of Failed
Preparations for L2U CS+PS
Handovers for Cell (No
resource available)
73430225
InCSPS.NoReply
Number of Failed L2U CS

+PS Handovers Due to UE
Description
This counter provides the number of failed preparations for incoming inter-RAT CS+enhanced
PS handovers based on the value of TargetCellId in the RELOCATION REQUEST message.
This counter complies with 3GPP TS 25.413 (V10.10.0). For details about this counter, see
section 8.7 "Relocation Resource Allocation" in this TS.
Measurement point
The measurement is triggered at point B in the following figure. During an incoming inter-RAT
CS+enhanced PS handover, when the TRNC sends a RELOCATION FAILURE message, this
counter is measured in based on the value of TargetCellId in the RELOCATION REQUEST
message.
Issue 03 (2015-06-30)

2104
BSC6900 UMTS
Figure 1-930 Incoming Inter-RAT CS+enhanced PS handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
PrepInCSPS.ResUnavail
WRFD-140102

LTE Emergency Calls
InCSPS.NoReply
WRFD-140102

LTE Emergency Calls
Number of Successful L2U CS Handover Preparations for CS+PS Combined

Services Triggered by SRVCC for Cell (PS Timeout)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430230
PrepInCS.PSTimeOut
Number of Successful L2U

CS Handover Preparations
for CS+PS Combined
Services Triggered by
SRVCC for Cell (PS
Timeout)

2105
BSC6900 UMTS
Description
This counter provides the number of successful preparations for CS only SRVCC handovers in
CS+PS SRVCC handover scenarios when the RNC does not receive a Relocation Request from
the PS domain of the CN.
This counter complies with 3GPP TS 23.216 (v11.1.0). For details about this counter, see section
6.2.2.2 "SRVCC from E-UTRAN to UTRAN with PS HO or GERAN with DTM HO support"
in this TS.
Measurement point
The measurement is triggered at point B in figure 1. During the preparation for the CS+PS
SRVCC handover, the RNC starts a timer after receiving a RELOCATION REQUEST message
from the CS domain of the CN. If the RNC does not receive a RELOCATION REQUEST from
the PS domain of the CN before this timer expires, the RNC triggers the preparation for the CS
only SRVCC handover. Subsequently, when the RNC sends a RELOCATION REQUEST
ACKNOWLDGE message to the CS domain of the CN, indicating that the handover preparation
is successful, this counter is measured based on the value of TargetCellId in the RELOCATION
REQUEST message.
Issue 03 (2015-06-30)

2106
BSC6900 UMTS
Figure 1-931 CS+PS SRVCC handover
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
PrepInCS.PSTimeOut
WRFD-150215

with PS Handover

2107
BSC6900 UMTS
Number of Successful L2U CS Handovers for CS+PS Combined Services Triggered

by SRVCC for Cell (PS Timeout)
Counters
Counter ID
Counter Name
Counter Description
73430231
InCS.PSTimeOut
Number of Successful L2U

CS Handovers for CS+PS
Combined Services
Cell (PS Timeout)
Description
This counter provides the number of successful CS only SRVCC handovers in CS+PS SRVCC
handover scenarios when the RNC does not receive a RELOCATION REQUEST message from
the PS domain of the CN within the specified period of time. This counter is measured based on
the value of TargetCellId in the RELOCATION REQUEST message.
This counter complies with 3GPP TS 23.216 (v11.1.0). For details about this counter, see section
6.2.2.2 "SRVCC from E-UTRAN to UTRAN with PS HO or GERAN with DTM HO support"
in this TS.
Measurement point
The measurement is triggered at point D in figure 1. During the preceding CS+PS SRVCC
handover, the RNC receives a RELOCATION REQUEST message from the CS domain but
does not receive a RELOCATION REQUEST message from the PS domain within the specified
period of time. Subsequently, if the RNC sends a RELOCATION COMPLETE message to the
MSC, indicating that the CS only SRVCC handover is successful, this counter is measured based
on the value of TargetCellId in the RELOCATION REQUEST message.
Issue 03 (2015-06-30)

2108
BSC6900 UMTS
Figure 1-932 CS+PS SRVCC handover
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
InCS.PSTimeOut
WRFD-150215

with PS Handover

2109
BSC6900 UMTS
1.12.19 Iu Singaling Connection Release Measurement<per 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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426353
VS.IU.Sig.Normal
Rel.CS
Number of Iu CS
Signaling
Connections
(Without RAB)
Normally Released
for Cell
BSC6900
V900R015C00
73426354
VS.IU.Sig.Normal
Rel.PS
Number of Iu PS
Signaling
Connections
(Without RAB)
Normally Released
for Cell
BSC6900
V900R015C00
73426355
VS.IU.Sig.Abnorm
alRel.CS
Number of Iu CS
Signaling
Connections
(Without RAB)
Abnormally
Released for Cell
BSC6900
V900R015C00
73426356
VS.IU.Sig.Abnorm
alRel.PS
Number of Iu PS
Signaling
Connections
(Without RAB)
Abnormally
Released for Cell
BSC6900
V900R015C00
73426357
VS.IU.Sig.Normal
Rel.CS.Service
Number of Iu CS
Signaling
Connections
(Without RAB)
Normally Released
for Cell (Service
Reasons)
BSC6900
V900R015C00

2110
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426358
VS.IU.Sig.Normal
Rel.PS.Service
Number of Iu PS
Signaling
Connections
(Without RAB)
Normally Released
for Cell (Service
Reasons)
BSC6900
V900R015C00
73426359
VS.IU.Sig.Abnorm
alRel.CS.Service
Number of Iu CS
Signaling
Connections
(Without RAB)
Abnormally
Released for Cell
(Service Reasons)
BSC6900
V900R015C00
73426360
VS.IU.Sig.Abnorm
alRel.PS.Service
Number of Iu PS
Signaling
Connections
(Without RAB)
Abnormally
Released for Cell
(Service Reasons)
BSC6900
V900R015C00
73426361
VS.IU.Sig.Abnorm
alRel.CS.Service.Se
cModeFail
Number of Iu CS
Signaling
Connections
(Without RAB)
Abnormally
Released Due to
Security Mode
Procedure Failures
for Cell (Service
Reasons)
BSC6900
V900R015C00
73426362
VS.IU.Sig.Abnorm
alRel.PS.Service.Se
cModeFail
Number of Iu PS
Signaling
Connections
(Without RAB)
Abnormally
Released Due to
Security Mode
Procedure Failures
for Cell (Service
Reasons)
BSC6900
V900R015C00

2111
BSC6900 UMTS
None
Number of Iu CS Signaling Connections (Without RAB) Normally Released for

Cell
Counters
Counter ID
Counter Name
Counter Description
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-933 Iu signaling connections normally released procedure
Issue 03 (2015-06-30)

2112
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.Sig.NormalRel.CS
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Iu PS Signaling Connections (Without RAB) Normally Released for

Cell
Counters
Counter ID
Counter Name
Counter Description
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.
Issue 03 (2015-06-30)

2113
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.Sig.NormalRel.PS
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2114
BSC6900 UMTS
Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for

Cell
Counters
Counter ID
Counter Name
Counter Description
73426355
VS.IU.Sig.AbnormalRel.CS
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-935 Iu signaling connections abnormally released procedure
Issue 03 (2015-06-30)

2115
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for

Cell
Counters
Counter ID
Counter Name
Counter Description
73426356
VS.IU.Sig.AbnormalRel.PS
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
Issue 03 (2015-06-30)

2116
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.Sig.AbnormalRel.PS
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2117
BSC6900 UMTS
Number of Iu CS Signaling Connections (Without RAB) Normally Released for

Cell (Service Reasons)
Counters
Counter ID
Counter Name
Counter Description
73426357
VS.IU.Sig.NormalRel.CS.S
ervice
(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 .
Issue 03 (2015-06-30)

2118
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IU.Sig.NormalRel.CS.S
ervice
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Iu PS Signaling Connections (Without RAB) Normally Released for

Counters
Counter ID
Counter Name
Counter Description
73426358
VS.IU.Sig.NormalRel.PS.Se
rvice
(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
Issue 03 (2015-06-30)

2119
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IU.Sig.NormalRel.PS.Se
rvice
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2120
BSC6900 UMTS
Number of Iu CS Signaling Connections (Without RAB) Abnormally Released for

Counters
Counter ID
Counter Name
Counter Description
73426359
.Service
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
Issue 03 (2015-06-30)

2121
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.Service
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Iu PS Signaling Connections (Without RAB) Abnormally Released for

Counters
Counter ID
Counter Name
Counter Description
73426360
VS.IU.Sig.AbnormalRel.PS.
Service
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
Issue 03 (2015-06-30)

2122
BSC6900 UMTS
of the released signaling connection. For details about the cause values indicating an abnormal
release, see 3GPP TS 25.413.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Service
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2123
BSC6900 UMTS
Number of Iu CS Signaling Connections (Without RAB) Abnormally Released Due

to Security Mode Procedure Failures for Cell (Service Reasons)
Counters
Counter ID
Counter Name
Counter Description
73426361
.Service.SecModeFail
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.
Issue 03 (2015-06-30)

2124
BSC6900 UMTS
Figure 1-941 Iu signaling connections abnormally released due to security mode procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.Service.SecModeFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2125
BSC6900 UMTS
Number of Iu PS Signaling Connections (Without RAB) Abnormally Released Due

to Security Mode Procedure Failures for Cell (Service Reasons)
Counters
Counter ID
Counter Name
Counter Description
73426362
Service.SecModeFail
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
Optimization" or "UE Generated Signalling Connection Release", and if the RRC connection is
set up due to originating interactive call, terminating interactive call, originating background
call, or terminating background call, this counter is increased by one in the best cell of the UE
based on the domain of the released signaling connection. For details about the cause values
indicating an abnormal release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

2126
BSC6900 UMTS
Figure 1-942 Iu signaling connections abnormally released due to security mode procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Service.SecModeFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.20 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, For multi-carrier HSDPA users, this counter is measured only in the cell
with the primary carrier.
When the DC-HSUPA Independent Active Sets function is enabled, the counters in this function
subset are separately measured on the primary and secondary carriers for DC-HSUPA UEs.
Issue 03 (2015-06-30)

2127
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180826
VS.IUB.CancelRLRecfg
Number of Iub
Interface RLs Whose
Synchronized
Reconfiguration Is
Cancelled for Cell
Earlier than
BSC6900
V900R011
67180827
VS.IUB.RLFailInd
Number of Iub
Interface RL Failures
for Cell
Earlier than
BSC6900
V900R011
67180831
VS.IUB.RLFailInd.
CfgUnsupp
Number of Iub
Interface Radio Link
Failures for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67180829
VS.IUB.RLFailInd.
HW
Number of Iub
Failures for Cell
(Device Fault)
Earlier than
BSC6900
V900R011
67189772
VS.IUB.RLFailInd.
SyncFail
Number of Iub
Synchronization
Failures for Cell
Earlier than
BSC6900
V900R011
67180830
VS.IUB.RLFailNoRestore
Number of Iub
Failures for Cell
(Synchronization
Failure)
Earlier than
BSC6900
V900R011
67180813
RLM.FailRLAddIu
b.CfgUnsup
Number of Iub
Addition Failures for
Cell (Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67180812
RLM.FailRLAddIu
b.Cong
Number of Iub
Cell (Congestion)
Earlier than
BSC6900
V900R011
67180811
VS.SHO.FailRLAd
dIub.HW
Number of Iub
Cell (Device Fault)
Earlier than
BSC6900
V900R011

2128
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180823
VS.IUB.FailRLRec
fg.CfgUnsupp
Number of Iub
Synchronous
Reconfiguration
Failures for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67180822
VS.IUB.FailRLRec
fg.Cong
Number of Iub
Synchronous
Reconfiguration
Failures for Cell
(Congestion)
Earlier than
BSC6900
V900R011
67180821
VS.IUB.FailRLRec
fg.HW
Number of Iub
Synchronous
Reconfiguration
Failures for Cell
(Device Fault)
Earlier than
BSC6900
V900R011
67180824
VS.IUB.FailRLRec
fg.NoReply
Number of Iub
Interface RLs
Unsuccessfully
Reconfigured Due to
No Response for Cell
Earlier than
BSC6900
V900R011
67180806
RLM.FailRLSetup
Iub.CfgUnsup
Number of Iub
Setup Failures for
Cell (Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67180805
RLM.FailRLSetup
Iub.Cong
Number of Iub
Setup Failures for
Cell (Congestion)
Earlier than
BSC6900
V900R011
67180804
VS.IUB.FailRLSet
up.HW
Number of Iub
Setup Failures for
Cell (Device Fault)
Earlier than
BSC6900
V900R011
67189775
VS.IUB.AttRLRecfg
Number of Iub
Interface RL
Reconfiguration
Attempts for Cell
Earlier than
BSC6900
V900R011

2129
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180808
VS.IUB.AttRLAdd
Number of Iub
Interface RL
Addition Requests
for Cell
Earlier than
BSC6900
V900R011
67180815
VS.IUB.AttRLDel
Number of Iub
Interface RL
Deletion Requests
for Cell
BSC6900
V900R012
67180801
VS.IUB.AttRLSetup
Number of Iub
Interface RL
Establishment
Requests for Cell
Earlier than
BSC6900
V900R011
67180832
VS.IUB.RLRestore
Number of Iub
Interface RL
Restorations for Cell
Earlier than
BSC6900
V900R011
67180809
VS.IUB.SuccRLAd
d
Number of Iub
Interface RLs
Successfully Added
for Cell
Earlier than
BSC6900
V900R011
67180816
VS.IUB.SuccRLDel
Number of Iub
Interface RLs
Successfully Deleted
for Cell
BSC6900
V900R012
67180819
VS.IUB.SuccRLRecfg
Number of Iub
Interface RLs
Successfully
Synchronization
Reconfigured for
Cell
Earlier than
BSC6900
V900R011
67180802
VS.IUB.SuccRLSetup
Number of Iub
Interface RLs
Successfully
Established for Cell
Earlier than
BSC6900
V900R011
67180838
VS.IUB.FailRLSet
up.NoReply
Number of Iub
Interface RLs
Unsuccessfully
Established Due to
Earlier than
BSC6900
V900R011

2130
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428357
VS.IUB.FailRLAd
dIub.NoReply
Number of Radio
Added over the Iub
Interface for Cell (No
Response from the
NodeB)
BSC6900
V900R016
None
Number of RLs with Synchronized Reconfiguration Cancelled on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67180826
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.This counter complies with section
"8.3.4 Synchronised Radio Link Reconfiguration Cancellation" in 3GPP TS 25.433 (v10.10.0).
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.
Issue 03 (2015-06-30)

2131
BSC6900 UMTS
Figure 1-943 RL reconfiguration cancel procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RL Failures on Iub Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180827
VS.IUB.RLFailInd
Number of Iub Interface RL

Failures for Cell

2132
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67180831
VS.IUB.RLFailInd.CfgUnsupp
Number of Iub Interface

Radio Link Failures for Cell
(Configuration
Unsupported)
67180829
VS.IUB.RLFailInd.HW

(Device Fault)
67189772
VS.IUB.RLFailInd.SyncFail

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.The preceding counters
comply with section "8.3.12 Radio Link Failure" in 3GPP TS 25.433 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
Number of RL failures on Iub interface due

to configuration unsupported (cause value:
Power level not supported, Measurement not
supported for the object, SIB Origination in
Node B not Supported, Requested Tx
Diversity Mode not supported, Number of DL
codes not supported, S-CPICH not supported,
Combining not supported, UL SF not
supported, DL SF not supported, Common
Transport Channel Type not supported,
Dedicated Transport Channel Type not
not supported, CM not supported, Tx
diversity no longer supported, or Number of
UL codes not supported)
VS.IUB.RLFailInd.HW

to hardware failure (cause value: Hardware
failure)

to synchronization failure (cause value:
Synchronization failure)

2133
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-944 RL failure procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IUB.RLFailInd
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.IUB.RLFailInd.HW
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2134
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Unsuccessfully Restored on Iub Interface due to No Response

Counters
Counter ID
Counter Name
Counter Description
67180830

(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.This counter complies with section "8.3.12 Radio Link Failure" in 3GPP TS 25.433
(v10.10.0).
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.
Issue 03 (2015-06-30)

2135
BSC6900 UMTS
Figure 1-945 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-946 RL restore time out procedure
Formula
None
Issue 03 (2015-06-30)

2136
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Unsuccessfully Added on Iub Interface for Different Causes

Counters
Counter ID
Counter Name
Counter Description
67180813
RLM.FailRLAddIub.CfgUn
sup

Radio Link Addition Failures
Unsupported)
67180812
RLM.FailRLAddIub.Cong

for Cell (Congestion)
67180811
VS.SHO.FailRLAddIub.H
W

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.The preceding counters comply with section "8.3.1.3 Unsuccessful
Issue 03 (2015-06-30)
Counter Name
Description
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)

2137
BSC6900 UMTS
Counter Name
Description

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

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-947 RL addition procedure (failed operation)
Formula
None
Issue 03 (2015-06-30)

2138
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RLM.FailRLAddIub.CfgUn
sup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.SHO.FailRLAddIub.H
W
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Unsuccessfully Synchronization Reconfigured on Iub Interface for

Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180823
VS.IUB.FailRLRecfg.CfgU
nsupp

Radio Link Synchronous
Reconfiguration Failures for
Cell (Configuration
Unsupported)
67180822
VS.IUB.FailRLRecfg.Cong

Cell (Congestion)
67180821
VS.IUB.FailRLRecfg.HW

Cell (Device Fault)

2139
BSC6900 UMTS
Description
The measurement counters provide the number of RLs unsuccessfully reconfigured on the Iub
interface in a cell for different causes.The preceding counters comply with section "8.3.1.3
Counter Name
Description
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)

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)

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.
Issue 03 (2015-06-30)

2140
BSC6900 UMTS
Figure 1-948 Synchronized RL reconfiguration procedure (failed operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IUB.FailRLRecfg.CfgU
nsupp
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2141
BSC6900 UMTS
Number of RLs Unsuccessfully Reconfigured on Iub Interface due to No Response

Counters
Counter ID
Counter Name
Counter Description
67180824
VS.IUB.FailRLRecfg.NoRe
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.The preceding counters comply with section
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-949 Sync RL reconfiguration procedure (NoReply)
Formula
None
Issue 03 (2015-06-30)

2142
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.FailRLRecfg.NoRe
ply
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Unsuccessfully Established on Iub Interface for Different Causes

Counters
Counter ID
Counter Name
Counter Description
67180806
RLM.FailRLSetupIub.CfgU
nsup

Radio Link Setup Failures for
Cell (Configuration
Unsupported)
67180805
RLM.FailRLSetupIub.Cong

Cell (Congestion)
67180804
VS.IUB.FailRLSetup.HW

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.The preceding counters comply with section
Issue 03 (2015-06-30)

2143
BSC6900 UMTS
Counter Name
Description
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)

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)

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.
Issue 03 (2015-06-30)

2144
BSC6900 UMTS
Figure 1-950 RL setup procedure (failed operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
RLM.FailRLSetupIub.CfgU
nsup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2145
BSC6900 UMTS
Number of RLs Requested to Reconfigure with Synchronization on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67189775
VS.IUB.AttRLRecfg

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.This counter complies with section "8.3.2.2
Successful Operation" in 3GPP TS 25.433 (v10.10.0).
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-951 Synchronized RL reconfiguration procedure (successful operation)
Formula
None
Issue 03 (2015-06-30)

2146
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.AttRLRecfg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Requested to Add on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67180808
VS.IUB.AttRLAdd

Addition Requests for Cell
Description
The measurement counters provide the number of RLs requested to add on the Iub interface in
a cell.This counter complies with section "8.3.1.2 Successful Operation" in 3GPP TS 25.433
(v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure. To add one or more RLs for a
NodeB communication context, the RNC shall initiate a RL addition procedure by sending a
RADIO LINK ADDITION REQUEST message to the NodeB. In this case, the RNC measures
the counter in the cell where the RLs are requested to add.
Issue 03 (2015-06-30)

2147
BSC6900 UMTS
Figure 1-952 RL addition procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.AttRLAdd
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Requested to Delete on Iub Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180815
VS.IUB.AttRLDel

Deletion Requests for Cell

2148
BSC6900 UMTS
Description
This measurement item provides the number of RLs requested to delete on the Iub interface in
a cell.This counter complies with section "8.3.6 Radio Link Deletion" in 3GPP TS 25.433
(v10.10.0).
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IUB.AttRLDel
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2149
BSC6900 UMTS
Number of RLs Requested to Establish on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67180801
VS.IUB.AttRLSetup

Cell
Description
This measurement counter takes statistics of the number of RLs requested to establish on the
Iub interface in a cell.This counter complies with section "8.2.17.2 Successful Operation" in
3GPP TS 25.433 (v10.10.0).
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-954 RL setup procedure (successful operation)
Formula
None
Issue 03 (2015-06-30)

2150
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.AttRLSetup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Restored on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67180832
VS.IUB.RLRestore

Restorations for Cell
Description
This measurement counter takes statistics of the number of RLs restored on the Iub interface in
a cell.This counter complies with section "8.3.13 Radio Link Restoration" in 3GPP TS 25.433
(v10.10.0).
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.
Figure 1-955 RL restoration procedure
Issue 03 (2015-06-30)

2151
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.RLRestore
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Successfully Added on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67180809
VS.IUB.SuccRLAdd

Successfully Added for Cell
Description
The measurement counters provide the number of RLs successfully added on the Iub interface
in a cell.This counter complies with section "8.3.1.2 Successful Operation" in 3GPP TS 25.433
(v10.10.0).
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.
Issue 03 (2015-06-30)

2152
BSC6900 UMTS
Figure 1-956 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.
Figure 1-957 RL addition procedure (failed operation)
Formula
None
Issue 03 (2015-06-30)

2153
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.SuccRLAdd
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Successfully Deleted on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67180816
VS.IUB.SuccRLDel

Successfully Deleted for Cell
Description
This measurement item provides the number of RLs successfully deleted on the Iub interface in
a cell.This counter complies with section "8.3.6 Radio Link Deletion" in 3GPP TS 25.433
(v10.10.0).
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.
Issue 03 (2015-06-30)

2154
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.SuccRLDel
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Successfully Reconfigured with Synchronization on Iub Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180819
VS.IUB.SuccRLRecfg

Successfully
Synchronization
Reconfigured for Cell

2155
BSC6900 UMTS
Description
This measurement counter takes statistics of the number of RLs successfully reconfigured on
the Iub interface in a cell.This counter complies with section "8.3.3 Synchronised Radio Link
Reconfiguration Commit" in 3GPP TS 25.433 (v10.10.0).
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC sends a RADIO
LINK RECONFIGURATION COMMIT message to the NodeB. In this case, the RNC measures
the counter in the cell where the RLs are successfully reconfigured.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2156
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.SuccRLRecfg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RLs Successfully Established on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67180802
VS.IUB.SuccRLSetup

Cell
Description
This measurement counter takes statistics of the number of RLs successfully established on Iub
interface in a cell.This counter complies with section "8.2.17.2 Successful Operation" in 3GPP
TS 25.433 (v10.10.0).
Measurement point
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.
Figure 1-960 Figure 7-33 RL setup procedure (successful operation)
Issue 03 (2015-06-30)

2157
BSC6900 UMTS
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-961 RL setup procedure (failed operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IUB.SuccRLSetup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2158
BSC6900 UMTS
Number of RLs Unsuccessfully Established on Iub Interface due to No Response

Counters
Counter ID
Counter Name
Counter Description
67180838
VS.IUB.FailRLSetup.NoReply

Unsuccessfully Established
Due to No Response for Cell
Description
This counter provides the number of RLs unsuccessfully established on the Iub interface due to
no response from the NodeB.This counter complies with section "8.2.17.4 Abnormal
Conditions" in 3GPP TS 25.433 (v10.10.0).
Measurement point
The RNC sends a RADIO LINK SETUP 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.
Figure 1-962 RL setup procedure (failed operation)(no reply)
Issue 03 (2015-06-30)

2159
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IUB.FailRLSetup.NoReply
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Radio Links That Fail to Be Added over the Iub Interface (No Response
from the NodeB)
Counters
Counter ID
Counter Name
Counter Description
73428357
VS.IUB.FailRLAddIub.NoR
eply

Fail to Be Added over the Iub
Interface for Cell (No
Response from the NodeB)
Description
This counter provides the number of radio links that fail to be added over the Iub interface in a
cell due to no response from the NodeB.This counter complies with section "8.3.1.4 Abnormal
conditions" in 3GPP TS 25.433 (v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. The RNC sends a
RADIO LINK ADDITION REQUEST message to the NodeB and then the RNC starts a timer.
If the RNC does not receive a response from the NodeB before the timer expires, this counter
is updated in the cell that requests to add radio links based on the number of radio links that fail
to be added.
Issue 03 (2015-06-30)

2160
BSC6900 UMTS
Figure 1-963 Radio link addition failure due to no response from the NodeB
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IUB.FailRLAddIub.NoR
eply
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2161
BSC6900 UMTS
1.12.21 LCS Service Measurement <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.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67190670
VS.LCS.OutCellCo
ver.AgpsAss
Number of
Positioning Results
Out of the Reference
Cell's Coverage in
Case of UE
ASSISTED AGPS
Method for Cell
Earlier than
BSC6900
V900R011
67190671
VS.LCS.OutCellCo
ver.AgpsBas
Number of
Positioning Results
Cell's Coverage in
Case of UE Based
AGPS Method for
Cell
Earlier than
BSC6900
V900R011
67190672
VS.LCS.OutCellCo
ver.Otdoa
Number of
Positioning Results
Cell's Coverage in
Case of OTDOA
Method for Cell
Earlier than
BSC6900
V900R011
67190673
VS.LCS.OutCellCo
ver.CellIdRtt
Number of
Positioning Results
Cell's Coverage in
Case of CELLID +
RTT Method for Cell
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

2162
BSC6900 UMTS
Number of Positioning Results Beyond Coverage of UE Reference Cell in UE

Assisted AGPS Method
Counters
Counter ID
Counter Name
Counter Description
67190670
VS.LCS.OutCellCover.AgpsAss
Number of Positioning
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.This counter complies
with section "10 Network-assisted GPS positioning method" in 3GPP TS 25.305 (v10.10.0).
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCS.OutCellCover.AgpsAss
WRFD-020803
A-GPS Based LCS

2163
BSC6900 UMTS
Number of Positioning Results Beyond Coverage of UE Reference Cell in UE-based

AGPS Method
Counters
Counter ID
Counter Name
Counter Description
67190671
VS.LCS.OutCellCover.Agp
sBas
UE Based AGPS Method for
Cell
Description
UE reference cell through the UE BASED AGPS method in a cell.This counter complies with
section "10 Network-assisted GPS positioning method" in 3GPP TS 25.305 (v10.10.0).
Measurement point
the coverage of UE reference cell and the current positioning method is UE BASED AGPS.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCS.OutCellCover.Agp
sBas
WRFD-020803
A-GPS Based LCS

2164
BSC6900 UMTS
Number of Positioning Results Beyond Coverage of UE Reference Cell in OTDOA

Method
Counters
Counter ID
Counter Name
Counter Description
67190672
VS.LCS.OutCellCover.Otdoa
OTDOA Method for Cell
Description
UE reference cell through the OTDOA method in a cell.This counter complies with section "9
OTDOA positioning method" in 3GPP TS 25.305 (v10.10.0).
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.LCS.OutCellCover.Otdoa
WRFD-020802
OTDOA Based LCS

2165
BSC6900 UMTS
Number of Positioning Results Beyond Coverage of UE Reference Cell in CELLID

+ RTT method
Counters
Counter ID
Counter Name
Counter Description
67190673
VS.LCS.OutCellCover.CellIdRtt
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.This counter complies with
section "8 Cell ID and Enhanced Cell ID based positioning methods" in 3GPP TS 25.305
(v10.10.0).
Measurement point
the coverage of UE reference cell and the current positioning method is CELLID + RTT.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LCS.OutCellCover.CellIdRtt
WRFD-020801

Based LCS
1.12.22 MBMS Measurement <per Cell>(MBMS.Cell)

Overview
This function subset is used to measure the number of setups and releases of the MBMS traffic.
Issue 03 (2015-06-30)

2166
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194980
VS.MBMS.InterCe
ll.PTPtoPTM.Att
Number of Handover
Requests from PTP
Cell to PTM Cell
Earlier than
BSC6900
V900R011
67194981
VS.MBMS.RB.PTP
.AttEstab
Number of MBMS
Service PTP Setup
Requests for Cell
Earlier than
BSC6900
V900R011
67194982
VS.MBMS.RB.PTP
.SuccEstab
Number of
Successful MBMS
Service PTP Setups
for Cell
Earlier than
BSC6900
V900R011
67194983
VS.MBMS.RB.PTP
.Loss.Abnorm
Number of
Abnormal MBMS
Service Releases in
PTP Mode for Cell
Earlier than
BSC6900
V900R011
67194984
VS.MBMS.RB.PTP
.Loss.Norm
Number of Normal
MBMS Service
Releases in PTP
Mode for Cell
Earlier than
BSC6900
V900R011
67192130
VS.MBMS.MTCH
SetupSucc.Cell
Number of
Successful MTCH
Setups for Cell
Earlier than
BSC6900
V900R011
67192131
VS.MBMS.MTCH
SetupFail.Cell
Number of MTCH
Setup Failures for
Cell
Earlier than
BSC6900
V900R011
67192615
VS.MBMS.PTMto
PTP.Succ
Number of
Successful
Transitions from
PTM to PTP for Cell
Earlier than
BSC6900
V900R011
67192616
VS.MBMS.PTPtoP
TM.Succ
Number of
Successful
Transitions from
PTP to PTM for Cell
Earlier than
BSC6900
V900R011
67192617
VS.MBMS.PTPtoP
TM.Att
Number of PTP to
PTM Transitions for
Cell
Earlier than
BSC6900
V900R011
67204014
VS.MBMS.PTM.R
B.Mean.Cell
Mean Number of
PTM RBs for Cell
Earlier than
BSC6900
V900R011

2167
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192620
VS.MBMS.PTM.R
B.Max.Cell
Maximum Number
of PTM RBs for Cell
Earlier than
BSC6900
V900R011
67192621
VS.MBMS.RB.PT
M.AttEstab
Number of PTM
Setup Requests for
Cell
Earlier than
BSC6900
V900R011
67192622
VS.MBMS.RB.PT
M.SuccEstab
Number of
Successful PTM
Setups for Cell
Earlier than
BSC6900
V900R011
67204225
VS.MBMS.PTP.UE
.Channel0.Mean.C
ell
Mean Number of
PTP Users of MBMS
Channel 0 for Cell
Earlier than
BSC6900
V900R011
67204226
VS.MBMS.PTM.U
E.Channel0.Mean.
Cell
Mean Number of
PTM Users of
MBMS Channel 0
for Cell
Earlier than
BSC6900
V900R011
67204227
VS.MBMS.PTP.UE
.Channel1.Mean.C
ell
Mean Number of
PTP Users of MBMS
Channel 1 for Cell
Earlier than
BSC6900
V900R011
67204228
VS.MBMS.PTM.U
E.Channel1.Mean.
Cell
Mean Number of
PTM Users of
MBMS Channel 1
for Cell
Earlier than
BSC6900
V900R011
67204229
VS.MBMS.PTP.UE
.Channel2.Mean.C
ell
Mean Number of
PTP Users of MBMS
Channel 2 for Cell
Earlier than
BSC6900
V900R011
67204230
VS.MBMS.PTM.U
E.Channel2.Mean.
Cell
Mean Number of
PTM Users of
MBMS Channel 2
for Cell
Earlier than
BSC6900
V900R011
67204231
VS.MBMS.PTP.UE
.Channel3.Mean.C
ell
Mean Number of
PTP Users of MBMS
Channel 3 for Cell
Earlier than
BSC6900
V900R011
67204232
VS.MBMS.PTM.U
E.Channel3.Mean.
Cell
Mean Number of
PTM Users of
MBMS Channel 3
for Cell
Earlier than
BSC6900
V900R011
67204233
VS.MBMS.PTP.UE
.Channel4.Mean.C
ell
Mean Number of
PTP Users of MBMS
Channel 4 for Cell
Earlier than
BSC6900
V900R011

2168
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204234
VS.MBMS.PTM.U
E.Channel4.Mean.
Cell
Mean Number of
PTM Users of
MBMS Channel 4
for Cell
Earlier than
BSC6900
V900R011
67204235
VS.MBMS.PTM.C
hannel0.Dur.Cell
Duration of MBMS
Channel 0 in PTM
Mode for Cell
Earlier than
BSC6900
V900R011
67204236
VS.MBMS.PTP.Ch
annel0.Dur.Cell
Duration of MBMS
Channel 0 in PTP
Mode for Cell
Earlier than
BSC6900
V900R011
67204237
VS.MBMS.PTM.C
hannel1.Dur.Cell
Duration of MBMS
Channel 1 in PTM
Mode for Cell
Earlier than
BSC6900
V900R011
67204238
VS.MBMS.PTP.Ch
annel1.Dur.Cell
Duration of MBMS
Channel 1 in PTP
Mode for Cell
Earlier than
BSC6900
V900R011
67204239
VS.MBMS.PTM.C
hannel2.Dur.Cell
Duration of MBMS
Channel 2 in PTM
Mode for Cell
Earlier than
BSC6900
V900R011
67204240
VS.MBMS.PTP.Ch
annel2.Dur.Cell
Duration of MBMS
Channel 2 in PTP
Mode for Cell
Earlier than
BSC6900
V900R011
67204241
VS.MBMS.PTM.C
hannel3.Dur.Cell
Duration of MBMS
Channel 3 in PTM
Mode for Cell
Earlier than
BSC6900
V900R011
67204242
VS.MBMS.PTP.Ch
annel3.Dur.Cell
Duration of MBMS
Channel 3 in PTP
Mode for Cell
Earlier than
BSC6900
V900R011
67204243
VS.MBMS.PTM.C
hannel4.Dur.Cell
Duration of MBMS
Channel 4 in PTM
Mode for Cell
Earlier than
BSC6900
V900R011
67204244
VS.MBMS.PTP.Ch
annel4.Dur.Cell
Duration of MBMS
Channel 4 in PTP
Mode for Cell
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

2169
BSC6900 UMTS
Number of Releases of PTP MBMS Services because the new best cell is on PTM
mode
Counters
Counter ID
Counter Name
Counter Description
67194980
VS.MBMS.InterCell.PTPto
PTM.Att
Number of Handover
Requests from PTP Cell to
PTM Cell
Description
This measurement item provides the number of releases of PTP MBMS Services because the
new best cell is on PTM mode.
Measurement point
After a PTP RB is set up and there are several cells in the active set for UE, the release of the
RB might be triggered if the best cell changes and the new best cell is on PTM mode. At that
time, the RNC measures the item.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.InterCell.PTPto
PTM.Att
WRFD-010660
MBMS Phase 2
Number of Requests for PTP MBMS Setup

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194981
VS.MBMS.RB.PTP.AttEstab

PTP Setup Requests for Cell

2170
BSC6900 UMTS
Description
This measurement item provides the number of requests for setup of Point-to-Point (PTP)
MBMS services in a cell.
Measurement point
After the UE initiates an MBMS setup request, the RNC measures the item when the RNC
initiates PTP RB setup based on the request of the UE. If the UE applies for more than one
service, the RNC measures the item once for each service.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.RB.PTP.AttEstab
WRFD-010660
MBMS Phase 2
Number of Successful PTP MBMS Setups

Counters
Counter ID
Counter Name
Counter Description
67194982
VS.MBMS.RB.PTP.SuccEstab
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.
Issue 03 (2015-06-30)

2171
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.RB.PTP.SuccEstab
WRFD-010660
MBMS Phase 2
Number of Abnormal Releases of PTP MBMS Services for Different Causes

Counters
Counter ID
Counter Name
Counter Description
67194983
VS.MBMS.RB.PTP.Loss.A
bnorm
Number of Abnormal
MBMS Service Releases in
PTP Mode for Cell
Description
This measurement item provides the number of abnormal releases of PTP MBMS services for
different causes in a cell.
Measurement point
If an unexpected event occurs, for example, for the RF reason on the air interface, the associated
PTP RB is released. At that time, the RNC measures the item. If more than one RB (one RB for
one service) is released at the same time, the RNC measures the item once for release of each
RB.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2172
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.RB.PTP.Loss.A
bnorm
WRFD-010660
MBMS Phase 2
Number of Normal Releases of PTP MBMS Services

Counters
Counter ID
Counter Name
Counter Description
67194984
VS.MBMS.RB.PTP.Loss.N
orm
Number of Normal MBMS

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

2173
BSC6900 UMTS
Number of Successful Setups of MBMS(PTM) Traffic Channel

Counters
Counter ID
Counter Name
Counter Description
67192130
VS.MBMS.MTCHSetupSuc
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.
Figure 1-964 MBMS traffic channel set up procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

2174
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.MTCHSetupSuc
c.Cell
WRFD-010616
MBMS Introduction
Package
Number of Unsuccessful Setups of MBMS(PTM) Traffic Channel

Counters
Counter ID
Counter Name
Counter Description
67192131
VS.MBMS.MTCHSetupFail
.Cell
Number of MTCH Setup

Failures for Cell
Description
This measurement item provides the number of unsuccessful setups of the MBMS(PTM) traffic
channel in a cell.
Measurement point
The RNC measures this item when a MBMS(PTM) traffic channel in the cell fails to be set up.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MBMS.MTCHSetupFail
.Cell
WRFD-010616
MBMS Introduction
Package

2175
BSC6900 UMTS
Number of successful PTM to PTP transition in a cell

Counters
Counter ID
Counter Name
Counter Description
67192615
VS.MBMS.PTMtoPTP.Succ
Transitions from PTM to
PTP for Cell
Description
This measurement item provides the number of successful transition from PTM MBMS service
to PTP MBMS service in a cell.
Measurement point
After a MBMS service is transited from PTM mode to PTP mode and a PTP MBMS RB is
successful set up, the RNC measures the item.
Figure 1-965 transmission of MBMS service from PTM to PTP
Formula
None
Unit
None
Issue 03 (2015-06-30)

2176
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.PTMtoPTP.Succ
WRFD-01066001
MBMS Enhanced Broadcast

Mode
Number of Successful Transitions from PTP MBMS Service to PTM MBMS Service
Counters
Counter ID
Counter Name
Counter Description
67192616
VS.MBMS.PTPtoPTM.Succ
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-966 Transmission of MBMS service from PTP to PTM
Formula
None
Issue 03 (2015-06-30)

2177
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.PTPtoPTM.Succ
WRFD-01066001

Mode
Number of Transitions from PTP MBMS Service to PTM MBMS Service

Counters
Counter ID
Counter Name
Counter Description
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MBMS.PTPtoPTM.Att
WRFD-01066001

Mode

2178
BSC6900 UMTS
Number of RBs in PTM MBMS Service

Counters
Counter ID
Counter Name
Counter Description
67204014
VS.MBMS.PTM.RB.Mean.
Cell
Mean Number of PTM RBs

for Cell
67192620
VS.MBMS.PTM.RB.Max.C
ell
Maximum Number of PTM

RBs for Cell
Description
These counters provide the mean number and maximum number of PTM MBMS RBs in a cell.
Measurement point
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MBMS.PTM.RB.Mean.
Cell
WRFD-01061601
MBMS Broadcast Mode
VS.MBMS.PTM.RB.Max.C
ell
WRFD-01061601
MBMS Broadcast Mode

2179
BSC6900 UMTS
Number of PTM setup request

Counters
Counter ID
Counter Name
Counter Description
67192621
VS.MBMS.RB.PTM.AttEstab
Number of PTM Setup

Requests for Cell
Description
This measurement item provides the number of setups of PTM MBMS service in a cell.
Measurement point
When the RNC initiates the setup of PTM MBMS service ,the RNC measures the item.
Figure 1-967 PTM MBMS service setup procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

2180
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.RB.PTM.AttEstab
WRFD-01061601
MBMS Broadcast Mode
Number of Successful Setups of PTM MBMS Service

Counters
Counter ID
Counter Name
Counter Description
67192622
VS.MBMS.RB.PTM.SuccEstab
Number of Successful PTM

Setups for Cell
Description
This measurement item provides the number of successful setups of PTM MBMS RB in a cell.
Measurement point
When the RB of PTM MBMS service is successful set up ,the RNC measures the item.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MBMS.RB.PTM.SuccEstab
WRFD-01061601
MBMS Broadcast Mode

2181
BSC6900 UMTS
Mean number of PTP users in a cell of MBMS Channel

Counters
Counter ID
Counter Name
Counter Description
67204225
VS.MBMS.PTP.UE.Channe
l0.Mean.Cell
Mean Number of PTP Users

of MBMS Channel 0 for Cell
67204227
l1.Mean.Cell

67204229
l2.Mean.Cell

67204231
l3.Mean.Cell

67204233
l4.Mean.Cell

Description
The previous measurement counter provides the mean number of UEs that subscribe to MBMS
channel in PTP mode in a cell.
Measurement point
If the MBMS channel is in PTP mode, the number of cell_MBMS UEs is reported when a
connected UE orders or releases the program in the cell. When the MBMS channel switches
from PTM to PTP, the number of UEs that currently order the program in the cell is reported.
When the MBMS channel switches from PTP to PTM, the number of UEs that order the program
in PTP mode is reported as 0.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
l0.Mean.Cell
WRFD-010665
MBMS Channel Audience

Rating Statistics
l1.Mean.Cell
WRFD-010665

Rating Statistics

2182
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
l2.Mean.Cell
WRFD-010665

Rating Statistics
l3.Mean.Cell
WRFD-010665

Rating Statistics
l4.Mean.Cell
WRFD-010665

Rating Statistics
Mean number of PTM users in a cell of MBMS Channel

Counters
Counter ID
Counter Name
Counter Description
67204226
VS.MBMS.PTM.UE.Chann
el0.Mean.Cell
Mean Number of PTM Users

67204228
el1.Mean.Cell

67204230
el2.Mean.Cell

67204232
el3.Mean.Cell

67204234
el4.Mean.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
Issue 03 (2015-06-30)

2183
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el0.Mean.Cell
WRFD-010665

Rating Statistics
el1.Mean.Cell
WRFD-010665

Rating Statistics
el2.Mean.Cell
WRFD-010665

Rating Statistics
el3.Mean.Cell
WRFD-010665

Rating Statistics
el4.Mean.Cell
WRFD-010665

Rating Statistics
A PTM Channel Duration in a cell MBMS service Channel

Counters
Counter ID
Counter Name
Counter Description
67204235
VS.MBMS.PTM.Channel0.
Dur.Cell
Duration of MBMS Channel

0 in PTM Mode for Cell
67204237
Dur.Cell

67204239
Dur.Cell

67204241
Dur.Cell

67204243
Dur.Cell

Description
The previous measurement counter provides the duration in which MBMS channel is in PTM
mode.
Issue 03 (2015-06-30)

2184
BSC6900 UMTS
Measurement point
When the MBMS channel is initially decided to be in PTM mode or switches from PTP to PTM,
the system records the time as T1. When the MBMS channel stops or switches to PTP, the system
records the time as T2. The difference between T1 and T2 indicates a duration in which the
MBMS channel is in PTM mode. Assume that T is the difference between T1 and T2. The sum
of all the Ts in the measurement period equals the total duration in which the MBMS channel
is in PTM mode in the measurement period.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
Dur.Cell
WRFD-010665

Rating Statistics
Dur.Cell
WRFD-010665

Rating Statistics
Dur.Cell
WRFD-010665

Rating Statistics
Dur.Cell
WRFD-010665

Rating Statistics
Dur.Cell
WRFD-010665

Rating Statistics
A PTP Channel Duration in a cell MBMS service Channel

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204236
VS.MBMS.PTP.Channel0.D
ur.Cell

0 in PTP Mode for Cell
67204238
ur.Cell

67204240
ur.Cell


2185
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67204242
ur.Cell

67204244
ur.Cell

Description
The previous measurement counter provides the duration in which MBMS channel is in PTP
mode.
Measurement point
When the MBMS channel is initially decided to be in PTP mode or switches from PTM to PTP,
the system records the time as T1. When the MBMS channel stops or switches to PTM, the
system records the time as T2. The difference between T1 and T2 indicates a duration in which
the MBMS channel is in PTP mode. Assume that T is the difference between T1 and T2. The
sum of all the Ts in the measurement period equals the total duration in which the MBMS channel
is in PTP mode in the measurement period.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ur.Cell
WRFD-010665

Rating Statistics
ur.Cell
WRFD-010665

Rating Statistics
ur.Cell
WRFD-010665

Rating Statistics
ur.Cell
WRFD-010665

Rating Statistics
ur.Cell
WRFD-010665

Rating Statistics

2186
BSC6900 UMTS
1.12.23 RRC MR 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.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180609
VS.RRC.MrRpt.1A
Number of Event 1A
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
67180610
VS.RRC.MrRpt.1B
Number of Event 1B
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
67180611
VS.RRC.MrRpt.1C
Number of Event 1C
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
67180612
VS.RRC.MrRpt.1D
Number of Event 1D
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
67180613
VS.RRC.MrRpt.2D
Number of Event 2D
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
67180614
VS.RRC.MrRpt.2F
Number of Event 2F
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
67180615
VS.RRC.MrRpt.4A
Number of Uplink
Event 4A
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
67180616
VS.RRC.MrRpt.4B
Number of Uplink
Event 4B
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
67192652
VS.Utran.MrRpt.
4A
Number of Downlink
Event 4A
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011

2187
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192653
VS.Utran.MrRpt.
4B
Number of Downlink
Event 4B
Measurement
Reports for Cell
Earlier than
BSC6900
V900R011
73440131
VS.RRC.MrRpt.S
HO.RSCP
Average RSCP for

Cell
BSC6900
V900R012
73440132
VS.RRC.MrRpt.S
HO.EcNo
Average Ec/No for

Cell
BSC6900
V900R012
73428022
VS.SHO.RSCP.0
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 0 for Cell
BSC6900
V900R016C00
73428023
VS.SHO.RSCP.1
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 1 for Cell
BSC6900
V900R016C00
73428024
VS.SHO.RSCP.2
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 2 for Cell
BSC6900
V900R016C00
73428025
VS.SHO.RSCP.3
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 3 for Cell
BSC6900
V900R016C00
73428026
VS.SHO.RSCP.4
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 4 for Cell
BSC6900
V900R016C00

2188
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428027
VS.SHO.RSCP.5
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 5 for Cell
BSC6900
V900R016C00
73428028
VS.SHO.RSCP.6
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 6 for Cell
BSC6900
V900R016C00
73428029
VS.SHO.RSCP.7
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 7 for Cell
BSC6900
V900R016C00
73428030
VS.SHO.RSCP.8
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 8 for Cell
BSC6900
V900R016C00
73428031
VS.SHO.RSCP.9
Number of Times the

Best Cell's RSCP
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 9 for Cell
BSC6900
V900R016C00
73428012
VS.RRC.Access.RS
CP.0
Number of Times the

RSCP Indicated in an
RRC
CONNECTION
REQUEST Message
Falls into Range 0 for
Cell
BSC6900
V900R016C00

2189
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428013
VS.RRC.Access.RS
CP.1
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428014
VS.RRC.Access.RS
CP.2
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428015
VS.RRC.Access.RS
CP.3
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428016
VS.RRC.Access.RS
CP.4
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428017
VS.RRC.Access.RS
CP.5
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428018
VS.RRC.Access.RS
CP.6
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00

2190
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428019
VS.RRC.Access.RS
CP.7
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428020
VS.RRC.Access.RS
CP.8
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428021
VS.RRC.Access.RS
CP.9
Number of Times the

RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428032
VS.Periodic.MrRpt
.RSCP.0
Number of Times the

Best Cell's RSCP
Indicated in a
Periodic IntraFrequency
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428033
VS.Periodic.MrRpt
.RSCP.1
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00

2191
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428034
VS.Periodic.MrRpt
.RSCP.2
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428035
VS.Periodic.MrRpt
.RSCP.3
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428036
VS.Periodic.MrRpt
.RSCP.4
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428037
VS.Periodic.MrRpt
.RSCP.5
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00

2192
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428038
VS.Periodic.MrRpt
.RSCP.6
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428039
VS.Periodic.MrRpt
.RSCP.7
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428040
VS.Periodic.MrRpt
.RSCP.8
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428041
VS.Periodic.MrRpt
.RSCP.9
Number of Times the

Best Cell's RSCP
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00

2193
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428042
VS.RRC.Access.Ec
No.0
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428043
VS.RRC.Access.Ec
No.1
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428044
VS.RRC.Access.Ec
No.2
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428045
VS.RRC.Access.Ec
No.3
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428046
VS.RRC.Access.Ec
No.4
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428047
VS.RRC.Access.Ec
No.5
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00

2194
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428048
VS.RRC.Access.Ec
No.6
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428049
VS.RRC.Access.Ec
No.7
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428050
VS.RRC.Access.Ec
No.8
Number of Times the

Ec/No Indicated in
an RRC
CONNECTION
REQUEST Message
Cell
BSC6900
V900R016C00
73428051
VS.Cell.Updt.EcNo.0
Number of Times the

Ec/No Indicated in a
CELL UPDATE
Message Falls into
Range 0 for Cell
BSC6900
V900R016C00
73428052
VS.Cell.Updt.EcNo.1
Number of Times the

CELL UPDATE
Message Falls into
Range 1 for Cell
BSC6900
V900R016C00
73428053
VS.Cell.Updt.EcNo.2
Number of Times the

CELL UPDATE
Message Falls into
Range 2 for Cell
BSC6900
V900R016C00
73428054
VS.Cell.Updt.EcNo.3
Number of Times the

CELL UPDATE
Message Falls into
Range 3 for Cell
BSC6900
V900R016C00

2195
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428055
VS.Cell.Updt.EcNo.4
Number of Times the

CELL UPDATE
Message Falls into
Range 4 for Cell
BSC6900
V900R016C00
73428056
VS.Cell.Updt.EcNo.5
Number of Times the

CELL UPDATE
Message Falls into
Range 5 for Cell
BSC6900
V900R016C00
73428057
VS.Cell.Updt.EcNo.6
Number of Times the

CELL UPDATE
Message Falls into
Range 6 for Cell
BSC6900
V900R016C00
73428058
VS.Cell.Updt.EcNo.7
Number of Times the

CELL UPDATE
Message Falls into
Range 7 for Cell
BSC6900
V900R016C00
73428059
VS.Cell.Updt.EcNo.8
Number of Times the

CELL UPDATE
Message Falls into
Range 8 for Cell
BSC6900
V900R016C00
73428060
VS.SHO.EcNo.0
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 0 for Cell
BSC6900
V900R016C00
73428061
VS.SHO.EcNo.1
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 1 for Cell
BSC6900
V900R016C00

2196
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428062
VS.SHO.EcNo.2
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 2 for Cell
BSC6900
V900R016C00
73428063
VS.SHO.EcNo.3
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 3 for Cell
BSC6900
V900R016C00
73428064
VS.SHO.EcNo.4
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 4 for Cell
BSC6900
V900R016C00
73428065
VS.SHO.EcNo.5
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 5 for Cell
BSC6900
V900R016C00
73428066
VS.SHO.EcNo.6
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 6 for Cell
BSC6900
V900R016C00
73428067
VS.SHO.EcNo.7
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 7 for Cell
BSC6900
V900R016C00

2197
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428068
VS.SHO.EcNo.8
Number of Times the

Best Cell's Ec/No
Indicated in a
MEASUREMENT
REPORT for Event
1A/1B/1C Falls into
Range 8 for Cell
BSC6900
V900R016C00
73428069
VS.Periodic.MrRpt
.EcNo.0
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 0
BSC6900
V900R016C00
73428070
VS.Periodic.MrRpt
.EcNo.1
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 1
BSC6900
V900R016C00
73428071
VS.Periodic.MrRpt
.EcNo.2
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 2
BSC6900
V900R016C00

2198
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428072
VS.Periodic.MrRpt
.EcNo.3
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 3
BSC6900
V900R016C00
73428073
VS.Periodic.MrRpt
.EcNo.4
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 4
BSC6900
V900R016C00
73428074
VS.Periodic.MrRpt
.EcNo.5
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 5
BSC6900
V900R016C00
73428075
VS.Periodic.MrRpt
.EcNo.6
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 6
BSC6900
V900R016C00

2199
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428076
VS.Periodic.MrRpt
.EcNo.7
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 7
BSC6900
V900R016C00
73428077
VS.Periodic.MrRpt
.EcNo.8
Number of Times the

Best Cell's Ec/No
Indicated in a
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 8
BSC6900
V900R016C00
73428078
VS.RRC.MrRpt.
1A.InterNodeB.All
Number of Times
Event 1A Is Reported
for Cell (InterNodeB Soft
Handover)
BSC6900
V900R016C00
73428079
VS.RRC.MrRpt.
1A.InterNodeB.RS
CP.0
Number of Times the

Best Cell's RSCP
Indicated in Event
1A Falls into Range 0
Handover)
BSC6900
V900R016C00
73428080
VS.RRC.MrRpt.
1A.InterNodeB.RS
CP.1
Number of Times the

Best Cell's RSCP
Indicated in Event
Handover)
BSC6900
V900R016C00

2200
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428081
VS.RRC.MrRpt.
1A.InterNodeB.RS
CP.2
Number of Times the

Best Cell's RSCP
Indicated in Event
Handover)
BSC6900
V900R016C00
73428082
VS.RRC.MrRpt.
1A.InterNodeB.RS
CP.3
Number of Times the

Best Cell's RSCP
Indicated in Event
Handover)
BSC6900
V900R016C00
73428083
VS.RRC.MrRpt.
1A.InterNodeB.RS
CP.4
Number of Times the

Best Cell's RSCP
Indicated in Event
Handover)
BSC6900
V900R016C00
73428095
VS.Periodic.MrRpt
.UETxPower.0
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428096
VS.Periodic.MrRpt
.UETxPower.1
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00

2201
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428097
VS.Periodic.MrRpt
.UETxPower.2
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428098
VS.Periodic.MrRpt
.UETxPower.3
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428099
VS.Periodic.MrRpt
.UETxPower.4
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428100
VS.Periodic.MrRpt
.UETxPower.5
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00

2202
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428101
VS.Periodic.MrRpt
.UETxPower.6
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428102
VS.Periodic.MrRpt
.UETxPower.7
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428103
VS.Periodic.MrRpt
.UETxPower.8
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00
73428104
VS.Periodic.MrRpt
.UETxPower.9
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Cell
BSC6900
V900R016C00

2203
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428105
VS.Periodic.MrRpt
.UETxPower.10
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 10
for Cell
BSC6900
V900R016C00
73428106
VS.Periodic.MrRpt
.UETxPower.11
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 11
for Cell
BSC6900
V900R016C00
73428107
VS.Periodic.MrRpt
.UETxPower.12
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 12
for Cell
BSC6900
V900R016C00
73428108
VS.Periodic.MrRpt
.UETxPower.13
Number of Times the

UE Tx Power
Indicated in a
Periodic
Measurement Report
Required by the
Measurement Report
Collecting Function
Falls into Range 13
for Cell
BSC6900
V900R016C00

2204
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428109
VS.RSCP.Mean.TP
0
Average RSCP for

UEs with a
Propagation Delay of
0 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428112
VS.RSCP.Mean.TP
1
Average RSCP for

UEs with a
1 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428115
VS.RSCP.Mean.TP
2
Average RSCP for

UEs with a
2 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428118
VS.RSCP.Mean.TP
3
Average RSCP for

UEs with a
3 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428121
VS.RSCP.Mean.TP
4
Average RSCP for

UEs with a
4 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428124
VS.RSCP.Mean.TP
5
Average RSCP for

UEs with a
5 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428127
VS.RSCP.Mean.TP
6.9
Average RSCP for

UEs with a
6 to 9 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00

2205
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428130
VS.RSCP.Mean.TP
10.15
Average RSCP for

UEs with a
10 to 15 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428133
VS.RSCP.Mean.TP
16.25
Average RSCP for

UEs with a
16 to 25 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428136
VS.RSCP.Mean.TP
26.35
Average RSCP for

UEs with a
26 to 35 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428139
VS.RSCP.Mean.TP
36.55
Average RSCP for

UEs with a
36 to 55 During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
73428142
VS.RSCP.Mean.TP
.More55
Average RSCP for

UEs with
Propagation Delay
Greater Than 55
During RRC
Connection Setups
for Cell
BSC6900
V900R016C00
None
Issue 03 (2015-06-30)

2206
BSC6900 UMTS
Number of Event 1A Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.4.2 Measurement
report" in 3GPP TS 25.331 (v10.10.0).
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
Formula
None
Unit
None
Issue 03 (2015-06-30)

2207
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.1A
WRFD-020202
WRFD-020203
Number of Event 1B Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
67180610
VS.RRC.MrRpt.1B
Number of Event 1B
Cell
Description
This measurement item provides the number of event 1B measurement reports about neighboring
report" in 3GPP TS 25.331 (v10.10.0).
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.
Issue 03 (2015-06-30)

2208
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.1B
WRFD-020202
WRFD-020203
Number of Event 1C Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
67180611
VS.RRC.MrRpt.1C
Number of Event 1C
Cell
Description
This measurement item provide the number of event 1C measurement reports about neighboring
report" in 3GPP TS 25.331 (v10.10.0).
Measurement point
MEASUREMENT REPORT message from the UE with the event type as 1C and the
Issue 03 (2015-06-30)

2209
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.1C
WRFD-020202
WRFD-020203
Number of Event 1D Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
67180612
VS.RRC.MrRpt.1D
Number of Event 1D
Cell
Description
This measurement item provides the number of event 1D measurement reports about neighboring
report" in 3GPP TS 25.331 (v10.10.0).
Measurement point
MEASUREMENT REPORT message from the UE with the event type as 1D and the
Issue 03 (2015-06-30)

2210
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.1D
WRFD-020202
WRFD-020203
Number of Event 2D Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.4.2 Measurement
report" in 3GPP TS 25.331 (v10.10.0).
Issue 03 (2015-06-30)

2211
BSC6900 UMTS
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
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.2D
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Issue 03 (2015-06-30)

2212
BSC6900 UMTS
Number of Event 2F Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
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
report" in 3GPP TS 25.331 (v10.10.0).
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
Unit
None
Issue 03 (2015-06-30)

2213
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.2F
WRFD-020302

Handover Based on
Coverage
WRFD-020304

Number of Uplink Event 4A Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
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
report" in 3GPP TS 25.331 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC receives from a
UE a Measurement Report message with the event type as 4A and the measurement object as
cells in the active set. In this case, the RNC measures the item in the best cell that the UE camps
on.
Issue 03 (2015-06-30)

2214
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.4A
WRFD-021101
Dynamic Channel
(DCCC)
Number of Uplink Event 4B Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
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
report" in 3GPP TS 25.331 (v10.10.0).
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.
Issue 03 (2015-06-30)

2215
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.4B
WRFD-021101
Dynamic Channel
(DCCC)
Number of Downlink Event 4A Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.4.2
Issue 03 (2015-06-30)

2216
BSC6900 UMTS
Measurement point
When the RNC receives a Measurement Report message from L2 to L3, if the event type of the
message is 4A and the measurement object is DL traffic of the UE, the RNC measures the item
in the best cell that the UE camps on.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Utran.MrRpt.4A
WRFD-021101
Dynamic Channel
(DCCC)
Number of Downlink Event 4B Measurement Reports

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.4.2
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
Issue 03 (2015-06-30)

2217
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Utran.MrRpt.4B
WRFD-021101
Dynamic Channel
(DCCC)
Counter ID
Counter Name
Counter Description
73440131
VS.RRC.MrRpt.SHO.RSCP
Average RSCP for Cell
Average RSCP for Cell

Counters
specific formulas.
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8.4.2 Measurement report" in 3GPP TS 25.331
(v10.10.0).
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.
Issue 03 (2015-06-30)

2218
BSC6900 UMTS
Figure 1-976 UE sends an event 1A, 1B, or 1C measurement report
Formula
VS.RRC.MrRpt.SHO.RSCP = [VS.RSCP.Cum.SHO]/[VS.MrRpt.Cum.SHO]
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.SHO.RSCP
WRFD-020201
WRFD-020202
Intra Node B Softer

Handover
WRFD-020203

Average Ec/No for Cell

Counters
Counter ID
Counter Name
Counter Description
73440132
VS.RRC.MrRpt.SHO.EcNo
Average Ec/No for Cell
specific formulas.
Issue 03 (2015-06-30)

2219
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
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. This counter complies with section "8.4.2
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC receives
from a UE a MEASUREMENT REPORT message with the event type being 1A, 1B, or 1C.
The RNC measures the total number of event 1A, 1B, or 1C measurement reports and the total
CPICH Ec/No of the cell with the best signal quality in the active set of the UEs. At the end of
each measurement period, this counter is calculated by dividing the total CPICH Ec/No by the
total number. Note that this counter is measured in the cell in the active set.
Figure 1-977 UE sends an event 1A, 1B, or 1C measurement report
Formula
VS.RRC.MrRpt.SHO.EcNo = [VS.EcNo.Cum.SHO]/[VS.EcNo.MrRpt.Cum.SHO]
Unit
dB
Issue 03 (2015-06-30)

2220
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.SHO.EcNo
WRFD-020201
WRFD-020202
Intra Node B Softer

Handover
WRFD-020203

Number of Times the Best Cell's RSCP Indicated in a MEASUREMENT REPORT

for Event 1A/1B/1C Falls into a Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428022
VS.SHO.RSCP.0
Number of Times the Best

Cell's RSCP Indicated in a
MEASUREMENT
REPORT for Event 1A/1B/
1C Falls into Range 0 for Cell
73428023
VS.SHO.RSCP.1

MEASUREMENT
73428024
VS.SHO.RSCP.2

MEASUREMENT
73428025
VS.SHO.RSCP.3

MEASUREMENT
73428026
VS.SHO.RSCP.4

MEASUREMENT

2221
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428027
VS.SHO.RSCP.5

MEASUREMENT
73428028
VS.SHO.RSCP.6

MEASUREMENT
73428029
VS.SHO.RSCP.7

MEASUREMENT
73428030
VS.SHO.RSCP.8

MEASUREMENT
73428031
VS.SHO.RSCP.9

MEASUREMENT
Description
Each of these counters provides the number of times the best cell's RSCP indicated in a
MEASUREMENT REPORT for event 1A/1B/1C falls into a specific range. These counters are
incremented in the best cell. According to 3GPP TS 25.133, a measured RSCP ranges from -115
dBm to -25 dBm. These counters, however, use the RSCP reported by UEs. The formula for
calculating a reported RSCP based on a measured RSCP is as follows: Reported RSCP =
Measured RSCP + 115.These counters comply with section "8.4.2 Measurement report" in 3GPP
TS 25.331 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.SHO.RSCP.0
This counter provides the number of times a

reported RSCP falls into range 0: [55, 90].
This range maps onto the measured RSCP
range [-60 dBm, -25 dBm] specified by 3GPP
TS 25.133.

2222
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Description
VS.SHO.RSCP.1

reported RSCP falls into range 1: [45, 55).
range [-70 dBm, -60 dBm) specified by 3GPP
TS 25.133.
VS.SHO.RSCP.2

TS 25.133.
VS.SHO.RSCP.3

TS 25.133.
VS.SHO.RSCP.4

TS 25.133.
VS.SHO.RSCP.5

TS 25.133.
VS.SHO.RSCP.6

range [-100 dBm, -95 dBm) specified by
3GPP TS 25.133.
VS.SHO.RSCP.7

3GPP TS 25.133.
VS.SHO.RSCP.8

reported RSCP falls into range 8: [5, 10). This
range maps onto the measured RSCP range
[-110 dBm, -105 dBm) specified by 3GPP TS
25.133.

2223
BSC6900 UMTS
Counter Name
Description
VS.SHO.RSCP.9

25.133.
Measurement point
MEASUREMENT REPORT message from the UE. If the message is for event 1A/1B/1C, a
specific counter is incremented by one.
Figure 1-978 Measurement points at which RSCP statistics are collected upon receipt of a
MEASUREMENT REPORT for event 1A/1B/1C
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.RSCP.0
WRFD-020202
VS.SHO.RSCP.1
WRFD-020202
VS.SHO.RSCP.2
WRFD-020202
VS.SHO.RSCP.3
WRFD-020202

2224
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.SHO.RSCP.4
WRFD-020202
VS.SHO.RSCP.5
WRFD-020202
VS.SHO.RSCP.6
WRFD-020202
VS.SHO.RSCP.7
WRFD-020202
VS.SHO.RSCP.8
WRFD-020202
VS.SHO.RSCP.9
WRFD-020202
Number of Times the RSCP Indicated in an RRC CONNECTION REQUEST

Message Falls into a Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428012
VS.RRC.Access.RSCP.0
Number of Times the RSCP

Indicated in an RRC
CONNECTION REQUEST
Message Falls into Range 0
for Cell
73428013

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428014

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428015

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428016

Indicated in an RRC
CONNECTION REQUEST
for Cell

2225
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428017

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428018

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428019

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428020

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428021

Indicated in an RRC
CONNECTION REQUEST
for Cell
Description
Each of these counters provides the number of times the RSCP indicated in an RRC
CONNECTION REQUEST message falls into a specific range. These counters are incremented
in the cell specified the message. According to 3GPP TS 25.133, a measured RSCP ranges from
-115 dBm to -25 dBm. These counters, however, use the RSCP reported by UEs. The formula
for calculating a reported RSCP based on a measured RSCP is as follows: Reported RSCP =
TS 25.331 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description

TS 25.133.

2226
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Description

TS 25.133.

TS 25.133.

TS 25.133.

TS 25.133.

TS 25.133.

3GPP TS 25.133.

3GPP TS 25.133.

25.133.

2227
BSC6900 UMTS
Counter Name
Description

25.133.
Measurement point
After a UE sends an RRC CONNECTION REQUEST message to the RNC:
1. If the "Measured results on RACH" IE in the RRC CONNECTION REQUEST message
includes a reported RSCP, a specific counter is incremented by one, as shown at point A.
2. If the "Measured results on RACH" IE in the RRC CONNECTION REQUEST message does
not include a reported RSCP, the RNC queries the RSCP included in a special intra-frequency
measurement report. This special report is the first intra-frequency measurement report that the
UE sends to the RNC within 5 seconds after sending the RRC CONNECTION REQUEST
message and that involves the cell specified in the RRC CONNECTION REQUEST message.
Then, a specific counter is incremented by one, as shown at point B. If the RNC does not receive
any intra-frequency measurement report within the 5 seconds, no counter is incremented.
Figure 1-979 Measurement points at which RSCP statistics are collected upon receipt of an
RRC CONNECTION REQUEST message
Formula
None
Unit
None
Issue 03 (2015-06-30)

2228
BSC6900 UMTS
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2229
BSC6900 UMTS
Number of Times the Best Cell's RSCP Indicated in a Periodic Intra-Frequency

Measurement Report Required by the Measurement Report Collecting Function
Falls into a Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428032
VS.Periodic.MrRpt.RSCP.0

Periodic Intra-Frequency
Measurement Report
Required by the
Measurement Report
Collecting Function Falls
into Range 0 for Cell
73428033

Measurement Report
Required by the
Measurement Report
73428034

Measurement Report
Required by the
Measurement Report
73428035

Measurement Report
Required by the
Measurement Report
73428036

Measurement Report
Required by the
Measurement Report

2230
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428037

Measurement Report
Required by the
Measurement Report
73428038

Measurement Report
Required by the
Measurement Report
73428039

Measurement Report
Required by the
Measurement Report
73428040

Measurement Report
Required by the
Measurement Report
73428041

Measurement Report
Required by the
Measurement Report
Description
Each of these counters provides the number of times the best cell's RSCP indicated in a periodic
intra-frequency measurement report required by the measurement report collecting function falls
Issue 03 (2015-06-30)

2231
BSC6900 UMTS
into a specific range when the MR_PRD_INTRA_FREQ_MEAS_SWITCH_1 under the

MrRprtCfgSwitch parameter in the SET UMRCTRL command is turned on. These counters are
dBm to -25 dBm. These counters, however, use the RSCP reported by UEs. The formula for
calculating a reported RSCP based on a measured RSCP is as follows: Reported RSCP =
TS 25.331 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description

TS 25.133.

TS 25.133.

TS 25.133.

TS 25.133.

TS 25.133.

TS 25.133.

3GPP TS 25.133.

2232
BSC6900 UMTS
Counter Name
Description

3GPP TS 25.133.

25.133.

25.133.
Measurement point
The measurement is triggered at point A as shown in the figure, when the
MR_PRD_INTRA_FREQ_MEAS_SWITCH_1 is turned on and the RNC receives a
periodically transmitted MEASUREMENT REPORT message that includes intra-frequency
measurement results. In this case, a specific counter is incremented by one.
Figure 1-980 Measurement points at which RSCP statistics are collected upon receipt of a
periodic intra-frequency measurement report
Formula
None
Unit
None
Issue 03 (2015-06-30)

2233
BSC6900 UMTS
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2234
BSC6900 UMTS
Number of Times the Ec/No Indicated in an RRC CONNECTION REQUEST

Message Falls into a Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428042
VS.RRC.Access.EcNo.0
Number of Times the Ec/No

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428043

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428044

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428045

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428046

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428047

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428048

Indicated in an RRC
CONNECTION REQUEST
for Cell

2235
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428049

Indicated in an RRC
CONNECTION REQUEST
for Cell
73428050

Indicated in an RRC
CONNECTION REQUEST
for Cell
Description
Each of these counters provides the number of times the Ec/No indicated in an RRC
CONNECTION REQUEST message falls into a specific range. These counters are incremented
in the cell specified in the message. According to 3GPP TS 25.133, a measured Ec/No ranges
from -24 dB to 0 dB. These counters, however, use the Ec/No reported by UEs. The relationship
between a reported Ec/No and a measured Ec/No is illustrated by the following formula:
Measured Ec/No = floor((Reported Ec/No - 49)/2).
Note:
"floor" in the preceding formula indicates the floor function in mathematics and computer
science.These counters comply with section "8.1.3 RRC connection establishment" in 3GPP TS
25.331 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description

reported Ec/No falls into range 0: [37, 49].
This range maps onto the measured Ec/No
range [-6 dB, 0 dB] specified by 3GPP TS
25.133.

reported Ec/No falls into range 1: [33, 37).
range [-8 dB, -6 dB) specified by 3GPP TS
25.133.

25.133.

2236
BSC6900 UMTS
Counter Name
Description

25.133.

25.133.

25.133.

25.133.

reported Ec/No falls into range 7: [3, 13). This
range maps onto the measured Ec/No range
[-23 dB, -18 dB) specified by 3GPP TS
25.133.

25.133.
Measurement point
When a UE sends an RRC CONNECTION REQUEST message to the RNC:
includes a reported Ec/No, a specific counter is incremented by one, as shown at point A.
not include a reported Ec/No, the RNC queries the Ec/No included in a special intra-frequency
message and that involves the cell specified in the RRC CONNECTION REQUEST message.
Then, a specific counter is incremented by one, as shown at point B. If the RNC does not receive
any intra-frequency measurement report within the 5 seconds, no counter is incremented.
Issue 03 (2015-06-30)

2237
BSC6900 UMTS
Figure 1-981 Measurement points at which Ec/No statistics are collected upon receipt of an
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2238
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Times the Ec/No Indicated in a CELL UPDATE Message Falls into a
Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428051
VS.Cell.Updt.EcNo.0

Indicated in a CELL
UPDATE Message Falls into
Range 0 for Cell
73428052
VS.Cell.Updt.EcNo.1

Indicated in a CELL
Range 1 for Cell
73428053
VS.Cell.Updt.EcNo.2

Indicated in a CELL
Range 2 for Cell

2239
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428054
VS.Cell.Updt.EcNo.3

Indicated in a CELL
Range 3 for Cell
73428055
VS.Cell.Updt.EcNo.4

Indicated in a CELL
Range 4 for Cell
73428056
VS.Cell.Updt.EcNo.5

Indicated in a CELL
Range 5 for Cell
73428057
VS.Cell.Updt.EcNo.6

Indicated in a CELL
Range 6 for Cell
73428058
VS.Cell.Updt.EcNo.7

Indicated in a CELL
Range 7 for Cell
73428059
VS.Cell.Updt.EcNo.8

Indicated in a CELL
Range 8 for Cell
Description
Each of these counters provides the number of times the Ec/No indicated in a CELL UPDATE
message falls into a specific range. These counters are incremented in the target cell specified
in the message. According to 3GPP TS 25.133, a measured Ec/No ranges from -24 dB to 0 dB.
These counters, however, use the Ec/No reported by UEs. The relationship between a reported
Ec/No and a measured Ec/No is illustrated by the following formula: Measured Ec/No = floor
((Reported Ec/No - 49)/2).
Note:
science.These counters comply with section "8.3.1 Cell and URA update procedures" in 3GPP
TS 25.331 (v10.10.0).
Issue 03 (2015-06-30)

2240
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Description
VS.Cell.Updt.EcNo.0

25.133.
VS.Cell.Updt.EcNo.1

25.133.
VS.Cell.Updt.EcNo.2

25.133.
VS.Cell.Updt.EcNo.3

25.133.
VS.Cell.Updt.EcNo.4

25.133.
VS.Cell.Updt.EcNo.5

25.133.
VS.Cell.Updt.EcNo.6

25.133.
VS.Cell.Updt.EcNo.7

25.133.

2241
BSC6900 UMTS
Counter Name
Description
VS.Cell.Updt.EcNo.8

25.133.
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. In this case, a specific counter is incremented by one.
Figure 1-982 Measurement points at which Ec/No statistics are collected upon receipt of a CELL
UPDATE message
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Cell.Updt.EcNo.0
WRFD-010801
VS.Cell.Updt.EcNo.1
WRFD-010801
VS.Cell.Updt.EcNo.2
WRFD-010801
VS.Cell.Updt.EcNo.3
WRFD-010801

2242
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.Cell.Updt.EcNo.4
WRFD-010801
VS.Cell.Updt.EcNo.5
WRFD-010801
VS.Cell.Updt.EcNo.6
WRFD-010801
VS.Cell.Updt.EcNo.7
WRFD-010801
VS.Cell.Updt.EcNo.8
WRFD-010801
Number of Times the Best Cell's Ec/No Indicated in a MEASUREMENT REPORT

for Event 1A/1B/1C Falls into a Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428060
VS.SHO.EcNo.0

Cell's Ec/No Indicated in a
MEASUREMENT
73428061
VS.SHO.EcNo.1

MEASUREMENT
73428062
VS.SHO.EcNo.2

MEASUREMENT
73428063
VS.SHO.EcNo.3

MEASUREMENT
73428064
VS.SHO.EcNo.4

MEASUREMENT

2243
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428065
VS.SHO.EcNo.5

MEASUREMENT
73428066
VS.SHO.EcNo.6

MEASUREMENT
73428067
VS.SHO.EcNo.7

MEASUREMENT
73428068
VS.SHO.EcNo.8

MEASUREMENT
Description
These counters provide the number of times the best cell's Ec/No indicated in a
MEASUREMENT REPORT for event 1A/1B/1C falls into a specific range. These counters are
incremented in the best cell. According to 3GPP TS 25.133, a measured Ec/No ranges from
-24.0 dB to 0 dB. These counters, however, use the Ec/No reported by UEs. The relationship
between a reported Ec/No and a measured Ec/No is illustrated by the following formula:
Measured Ec/No = floor((Reported Ec/No - 49)/2).
Note:
science.These counters comply with section "8.4.2 Measurement report" in 3GPP TS 25.331
(v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.SHO.EcNo.0

25.133.

2244
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Description
VS.SHO.EcNo.1

25.133.
VS.SHO.EcNo.2

25.133.
VS.SHO.EcNo.3

25.133.
VS.SHO.EcNo.4

25.133.
VS.SHO.EcNo.5

25.133.
VS.SHO.EcNo.6

25.133.
VS.SHO.EcNo.7

25.133.
VS.SHO.EcNo.8

25.133.

2245
BSC6900 UMTS
Measurement point
MEASUREMENT REPORT message from the UE. If the message is for event 1A/1B/1C, a
specific counter is incremented by one.
Figure 1-983 Measurement points at which Ec/No statistics are collected upon receipt of a
MEASUREMENT REPORT for event 1A/1B/1C
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.EcNo.0
WRFD-020202
VS.SHO.EcNo.1
WRFD-020202
VS.SHO.EcNo.2
WRFD-020202
VS.SHO.EcNo.3
WRFD-020202
VS.SHO.EcNo.4
WRFD-020202
VS.SHO.EcNo.5
WRFD-020202
VS.SHO.EcNo.6
WRFD-020202
VS.SHO.EcNo.7
WRFD-020202
VS.SHO.EcNo.8
WRFD-020202

2246
BSC6900 UMTS
Number of Times the Best Cell's Ec/No Indicated in a Periodic Intra-Frequency

Measurement Report Required by the Measurement Report Collecting Function
Falls into a Specific Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428069
VS.Periodic.MrRpt.EcNo.0

Measurement Report
Required by the
Measurement Report
into Range 0
73428070

Measurement Report
Required by the
Measurement Report
into Range 1
73428071

Measurement Report
Required by the
Measurement Report
into Range 2
73428072

Measurement Report
Required by the
Measurement Report
into Range 3
73428073

Measurement Report
Required by the
Measurement Report
into Range 4

2247
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428074

Measurement Report
Required by the
Measurement Report
into Range 5
73428075

Measurement Report
Required by the
Measurement Report
into Range 6
73428076

Measurement Report
Required by the
Measurement Report
into Range 7
73428077

Measurement Report
Required by the
Measurement Report
into Range 8
Description
These counters provide the number of times the best cell's Ec/No indicated in a periodic intrafrequency measurement report required by the measurement report collecting function falls into
a specific range when the MR_PRD_INTRA_FREQ_MEAS_SWITCH_1 under the
MrRprtCfgSwitch parameter in the SET UMRCTRL command is turned on. These counters are
dB to 0 dB. These counters, however, use the Ec/No reported by UEs. The relationship between
a reported Ec/No and a measured Ec/No is illustrated by the following formula: Measured Ec/
No = floor((Reported Ec/No - 49)/2).
Note:
Issue 03 (2015-06-30)

2248
BSC6900 UMTS
science.These counters comply with section "8.4.2 Measurement report" in 3GPP TS 25.331
(v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description

25.133.

25.133.

25.133.

25.133.

25.133.

25.133.

25.133.

2249
BSC6900 UMTS
Counter Name
Description

25.133.

25.133.
Measurement point
MR_PRD_INTRA_FREQ_MEAS_SWITCH_1 is turned on and the RNC receives a
periodically transmitted MEASUREMENT REPORT message that includes intra-frequency
measurement results. In this case, a specific counter is incremented by one.
Figure 1-984 Measurement points at which Ec/No statistics are collected upon receipt of a
periodic intra-frequency measurement report
Formula
None
Unit
None
Issue 03 (2015-06-30)

2250
BSC6900 UMTS
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2251
BSC6900 UMTS
Number of Times the Best Cell's RSCP Indicated in Event 1A Falls into Different
Ranges (Inter-NodeB Soft Handover)
Counters
Counter ID
Counter Name
Counter Description
73428078
VS.RRC.MrRpt.
1A.InterNodeB.All
Number of Times Event 1A

Is Reported for Cell (InterNodeB Soft Handover)
73428079
VS.RRC.MrRpt.
1A.InterNodeB.RSCP.0

Cell's RSCP Indicated in
Event 1A Falls into Range 0
for Cell (Inter-NodeB Soft
Handover)
73428080
VS.RRC.MrRpt.

Handover)
73428081
VS.RRC.MrRpt.

Handover)
73428082
VS.RRC.MrRpt.

Handover)
73428083
VS.RRC.MrRpt.

Handover)
Description
The preceding counters provide the number of times the best cell's RSCP indicated in event 1A
falls into different ranges. When event 1A is reported, the RNC checks whether the cell with the
largest RSCP indicated in the measurement report is under the same NodeB as the best cell.
If so, no counter is incremented.
If not, a specific counter is incremented.
If the best cell's RSCP is the largest one, the RNC checks whether the best cell is under the same
NodeB as the cell with the second largest RSCP.
Issue 03 (2015-06-30)

2252
BSC6900 UMTS
If so, no counter is incremented.

If not, a specific counter is incremented.
These counters comply with section "8.4.2 Measurement report" in 3GPP TS 25.331 (v10.10.0).
Counter Name
Description
VS.RRC.MrRpt.1A.InterNodeB.All
Number of Times The Best Cell's RSCP Is

Greater Than -116 dBm for Cell.
VS.RRC.MrRpt.1A.InterNodeB.RSCP.0
Number of Times The Best Cell's RSCP Is

Greater Than or Equal to -60 dBm for Cell.
Number of Times The Best Cell's RSCP

Ranges Between -70 dBm (Included) and -60
dBm.

dBm.

dBm.

Ranges Between -100 dBm (Included) and
-90 dBm.
Measurement point
MEASUREMENT REPORT message from the UE and event 1A is reported. If the cell with the
largest RSCP indicated in the message is under a different NodeB from the best cell, a specific
counter is incremented by one in the best cell based on the best cell's RSCP. If the best cell's
RSCP is the largest one and the best cell is under a different NodeB from the cell with the second
largest RSCP, a specific counter is incremented by one in the best cell based on the best cell's
RSCP.
Issue 03 (2015-06-30)

2253
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.MrRpt.
1A.InterNodeB.All
WRFD-020202
WRFD-020203
VS.RRC.MrRpt.
WRFD-020202
WRFD-020203
VS.RRC.MrRpt.
WRFD-020202
WRFD-020203
VS.RRC.MrRpt.
WRFD-020202
WRFD-020203
VS.RRC.MrRpt.
WRFD-020202
WRFD-020203
VS.RRC.MrRpt.
WRFD-020202
WRFD-020203
Number of Times the UE Tx Power Indicated in a Periodic Measurement Report

Required by the Measurement Report Collecting Function Falls into a Specific
Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428095
VS.Periodic.MrRpt.UETxPower.0
Number of Times the UE Tx

Power Indicated in a Periodic
Measurement Report
Required by the
Measurement Report

2254
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428096

Measurement Report
Required by the
Measurement Report
73428097

Measurement Report
Required by the
Measurement Report
73428098

Measurement Report
Required by the
Measurement Report
73428099

Measurement Report
Required by the
Measurement Report
73428100

Measurement Report
Required by the
Measurement Report
73428101

Measurement Report
Required by the
Measurement Report

2255
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428102

Measurement Report
Required by the
Measurement Report
73428103

Measurement Report
Required by the
Measurement Report
73428104

Measurement Report
Required by the
Measurement Report
73428105

Measurement Report
Required by the
Measurement Report
73428106

Measurement Report
Required by the
Measurement Report
73428107

Measurement Report
Required by the
Measurement Report

2256
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428108

Measurement Report
Required by the
Measurement Report
Description
Each of these counters provides the number of times the UE Tx power indicated in a periodic
intra-frequency measurement report falls into a specific range when the
MR_UE_TX_POWER_MEAS_SWITCH_8 under the MrRprtCfgSwitch parameter in the SET
UMRCTRL command is turned on. These counters are incremented in the best cell. According
to 3GPP TS 25.133, a measured UE Tx power ranges from -50 dBm to 33 dBm. These counters,
however, use the UE Tx power reported by UEs. The formula for calculating a reported UE Tx
power based on a measured UE Tx power is as follows: Reported UE Tx power = Measured UE
Tx power + 71.These counters comply with section "8.4.2 Measurement report" in 3GPP TS
25.331 (v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description

reported UE Tx power falls into range 0: [95,
104]. This range maps onto the measured UE
Tx power range [24 dBm, 33 dBm] specified
by 3GPP TS 25.133.

95). This range maps onto the measured UE
Tx power range [20 dBm, 24 dBm) specified
by 3GPP TS 25.133.

by 3GPP TS 25.133.

by 3GPP TS 25.133.

2257
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Description

by 3GPP TS 25.133.

Tx power range [6 dBm, 9 dBm) specified by
3GPP TS 25.133.

3GPP TS 25.133.

3GPP TS 25.133.

Tx power range [-3 dBm, 0 dBm) specified
by 3GPP TS 25.133.

Tx power range [-6 dBm, -3 dBm) specified
by 3GPP TS 25.133.

by 3GPP TS 25.133.

by 3GPP TS 25.133.

2258
BSC6900 UMTS
Counter Name
Description

Tx power range [-15 dBm, -12 dBm)
specified by 3GPP TS 25.133.

Tx power range [-50 dBm, -15 dBm)
specified by 3GPP TS 25.133.
Measurement point
MR_UE_TX_POWER_MEAS_SWITCH_8 is turned on and the RNC receives a periodically
transmitted MEASUREMENT REPORT message that includes the UE Tx power. In this case,
a specific counter is incremented by one in the best cell.
Figure 1-986 Measurement points at which UE Tx power statistics are collected upon receipt
of a periodic measurement report
Formula
None
Unit
None
Issue 03 (2015-06-30)

2259
BSC6900 UMTS
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2260
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Average RSCP for UEs with Different Propagation Delays During RRC Connection
Setups
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428109
VS.RSCP.Mean.TP0
Average RSCP for UEs with

a Propagation Delay of 0
During RRC Connection
Setups for Cell
73428112
VS.RSCP.Mean.TP1

Setups for Cell
73428115
VS.RSCP.Mean.TP2

Setups for Cell
73428118
VS.RSCP.Mean.TP3

Setups for Cell

2261
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428121
VS.RSCP.Mean.TP4

Setups for Cell
73428124
VS.RSCP.Mean.TP5

Setups for Cell
73428127
VS.RSCP.Mean.TP6.9

a Propagation Delay of 6 to 9
Setups for Cell
73428130
VS.RSCP.Mean.TP10.15

a Propagation Delay of 10 to
15 During RRC Connection
Setups for Cell
73428133

Setups for Cell
73428136

Setups for Cell
73428139

Setups for Cell
73428142
VS.RSCP.Mean.TP.More55

Propagation Delay Greater
Than 55 During RRC
Connection Setups for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428110
VS.RSCP.cum.TP0
Accumulated RSCP for UEs

with a Propagation Delay of
Setups for Cell

2262
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428113
VS.RSCP.cum.TP1

Setups for Cell
73428131
VS.RSCP.cum.TP10.15

10 to 15 During RRC
73428134
VS.RSCP.cum.TP16.25

16 to 25 During RRC
73428116
VS.RSCP.cum.TP2

Setups for Cell
73428137
VS.RSCP.cum.TP26.35

26 to 35 During RRC
73428119
VS.RSCP.cum.TP3

Setups for Cell
73428140
VS.RSCP.cum.TP36.55

36 to 55 During RRC
73428122
VS.RSCP.cum.TP4

Setups for Cell
73428125
VS.RSCP.cum.TP5

Setups for Cell
73428128
VS.RSCP.cum.TP6.9

6 to 9 During RRC

2263
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428143
VS.RSCP.cum.TP.More55

with Propagation Delay
Greater Than 55 During RRC
73428111
VS.RSCP.sample.TP0
Number of Times UEs Send

an RRC Connection Setup
Request with a Propagation
Delay of 0 for Cell
73428114
VS.RSCP.sample.TP1

Delay of 1 for Cell
73428132
VS.RSCP.sample.TP10.15

Delay of 10 to 15 for Cell
73428135

73428117
VS.RSCP.sample.TP2

Delay of 2 for Cell
73428138

73428120
VS.RSCP.sample.TP3

Delay of 3 for Cell
73428141

73428123
VS.RSCP.sample.TP4

Delay of 4 for Cell

2264
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428126
VS.RSCP.sample.TP5

Delay of 5 for Cell
73428129

73428144
VS.RSCP.sample.TP.More5
5

Delay Greater Than 55 for
Cell
Description
Each of these counters provides the average RSCP for UEs with different propagation delays
during RRC connection setups using the RSCP indicated in RRC CONNECTION REQUEST
messages. These counters are updated in the cell specified in these messages. According to 3GPP
TS 25.435, the propagation delay (or extended propagation delay) ranges from 0 to 1023, and
the unit of the propagation delay is 3 chips. According to 3GPP TS 25.133, a measured RSCP
ranges from -115 dBm to -25 dBm. These counters, however, use the RSCP reported by UEs.
The formula for calculating a reported RSCP based on a measured RSCP is as follows: Reported
RSCP = Measured RSCP + 115.These counters comply with section "8.1.3 RRC connection
Measurement point
When a UE sends an RRC CONNECTION REQUEST message to the RNC, the propagation
delay included in a RACH DATA FRAME message from the NodeB to the RNC is used.
As for reported RSCP:
includes a reported RSCP, a specific counter is updated, as shown at point A.
not include a reported RSCP, the RNC queries the RSCP included in a special intra-frequency
message and that involves the cell specified in the message. Then, a specific counter is updated,
as shown at point B. If the RNC does not receive any intra-frequency measurement report within
the 5 seconds, no counter is updated.
After obtaining a propagation delay and a reported RSCP, the RNC locates the corresponding
propagation delay range and saves the RSCP for the range. At the end of a measurement period,
the RNC sums all the reported RSCP values in the range and divides the sum by the number of
reported RSCP values. Then, the average RSCP for this range is obtained.
Issue 03 (2015-06-30)

2265
BSC6900 UMTS
3. When the Coverage Widening in Interfere Scenario feature is enabled, the measured TP value
does not include the value about the RACH on coordinating links. The reasons are as follows:
the Coverage Widening in Interfere Scenario feature enables coordinating links to report RACH
information. However, under these circumstances, the measured TP value indicates the total
delay of the downlink transmission distance in the target cell plus the uplink transmission
distance in the coordinating cell, and has not relation with the distance between the UE and the
target cell. Therefore, the measured TP value does not include that reported on coordinating
links.
Figure 1-987 Measurement points at which RSCP statistics are collected upon receipt of an
Formula
VS.RSCP.Mean.TP0 = [VS.RSCP.cum.TP0]/[VS.RSCP.sample.TP0]
VS.RSCP.Mean.TP6.9 = [VS.RSCP.cum.TP6.9]/[VS.RSCP.sample.TP6.9]
VS.RSCP.Mean.TP.More55 = [VS.RSCP.cum.TP.More55]/[VS.RSCP.sample.TP.More55]
Issue 03 (2015-06-30)

2266
BSC6900 UMTS
Unit
dBm
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RSCP.Mean.TP0
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RSCP.Mean.TP1
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RSCP.Mean.TP2
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RSCP.Mean.TP3
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RSCP.Mean.TP4
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RSCP.Mean.TP5
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RSCP.Mean.TP6.9
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2267
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RSCP.Mean.TP.More55
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.24 Paging Measurement <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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190472
VS.RRC.Paging1.L
oss.PCHCong.Cell
Number of Paging
Messages Discarded
Due to PCH
Congestion for Cell
Earlier than
BSC6900
V900R011
67190473
VS.UTRAN.AttPag
ing1
Number of Paging
Messages Sent by
RNC for Cell
Earlier than
BSC6900
V900R011
73422072
VS.RRC.Paging1.P
CHCong.CSPreem
ptAtt
Number of
Preemptions by CS
Paging due to PCH
Congestion per Cell
BSC6900
V900R012

2268
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73422073
VS.RRC.Paging1.P
CHCong.CSPreem
ptSucc
Number of
Successful
Preemptions by CS
Paging due to PCH
Congestion per Cell
BSC6900
V900R012
73424293
VS.Paging1.Att1.U
RA.RealTime.Cell
Number of Level-1
Paging Attempts for
UEs Processing
Real-Time Services
in the URA_PCH
State for Cell
BSC6900
V900R014
73424294
VS.Paging1.Succ1.
URA.RealTime.Cel
l
Number of
Successful Level-1
Paging Attempts for
UEs Processing
Real-Time Services
in the URA_PCH
State for Cell
BSC6900
V900R014
73424295
VS.Paging1.Att1.U
RA.NoneRealTime.
Cell
Number of Level-1
Paging Attempts for
UEs Processing NonReal-Time Services
in the URA_PCH
State for Cell
BSC6900
V900R014
73424296
VS.Paging1.Succ1.
URA.NoneRealTim
e.Cell
Number of
Successful Level-1
Paging Attempts for
in the URA_PCH
State for Cell
BSC6900
V900R014
73424297
VS.Paging1.TotalS
ucc.URA.RealTime
.Cell
Number of
Successful Layered
Paging Attempts for
UEs Processing
Real-Time Services
in the URA_PCH
State for Cell
BSC6900
V900R014

2269
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424298
VS.Paging1.TotalS
ucc.URA.NoneReal
Time.Cell
Number of
Successful Layered
Paging Attempts for
in the URA_PCH
State for Cell
BSC6900
V900R014
73394912
VS.UTRAN.Paging
1.Att.UraPCH
Number of PAGING
TYPE 1 Messages
Sent by the RNC to
UEs in the
URA_PCH State for
Cell
BSC6900
V900R014
73394913
VS.UTRAN.Paging
1.Att.Idle.CS
Number of CS
PAGING TYPE 1
RNC to UEs in the
Idle State for Cell
BSC6900
V900R014
73394914
VS.UTRAN.Paging
1.Att.Idle.PS
Number of PS
PAGING TYPE 1
RNC to UEs in the
Idle State for Cell
BSC6900
V900R014
73425838
VS.Paging1.Att1.Id
le.RealTime.Cell
Number of Level-1
Paging Attempts for
UEs Performing
Real-Time Services
in Idle Mode for Cell
BSC6900
V900R015C00
73425839
VS.Paging1.Succ1.I
dle.RealTime.Cell
Number of
Successful Level-1
Paging Attempts for
UEs Performing
Real-Time Services
in Idle Mode for Cell
BSC6900
V900R015C00
73425840
VS.Paging1.Att1.Id
le.NoneRealTime.C
ell
Number of Level-1
Paging Attempts for
UEs Performing
Non-Real-Time
Services in Idle
Mode for Cell
BSC6900
V900R015C00

2270
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425841
VS.Paging1.Succ1.I
dle.NoneRealTime.
Cell
Number of
Successful Level-1
Paging Attempts for
UEs Performing
Non-Real-Time
Services in Idle
Mode for Cell
BSC6900
V900R015C00
73426165
VS.RRC.Paging1.P
CHCong.SMSPree
mptAtt
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
BSC6900
V900R015C00
73426166
VS.RRC.Paging1.P
CHCong.SMSPree
mptSucc
Number of
Successful
Preemptions by SMS
Paging due to PCH
Congestion per Cell
BSC6900
V900R015C00
73426313
VS.UTRAN.Paging
1.Att.Etws
Number of ETWSrelated PAGING

TYPE 1 Messages
Sent in a Cell
BSC6900
V900R015C00
73430425
VS.RRC.Paging1.P
CHCong.CSPreem
ptAtt.Platinum
Number of CS
Paging Preemption
Platinum Users upon
PCH Congestion for
Cell
BSC6900
V900R017C10
73430426
VS.RRC.Paging1.P
CHCong.CSPreem
ptSucc.Platinum
Number of
Successful CS
Paging Preemption
Platinum Users upon
PCH Congestion for
Cell
BSC6900
V900R017C10
73430427
VS.RRC.Paging1.P
CHCong.PSPreem
ptAtt.Platinum
Number of PS
Paging Preemption
Platinum Users upon
PCH Congestion for
Cell
BSC6900
V900R017C10

2271
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430428
VS.RRC.Paging1.P
CHCong.PSPreem
ptSucc.Platinum
Number of
Successful PS
Paging Preemption
Platinum Users upon
PCH Congestion for
Cell
BSC6900
V900R017C10
None
Number of Paging Losses due to PCH Congestion

Counters
Counter ID
Counter Name
Counter Description
67190472
VS.RRC.Paging1.Loss.PCH
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.This counter complies with section "8.1.2 Paging" in 3GPP TS 25.331(v10.13.0).
Measurement point
The measurement is triggered when the RNC discards a paging message due to PCH congestion.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2272
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Paging1.Loss.PCH
Cong.Cell
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Counter ID
Counter Name
Counter Description
67190473
VS.UTRAN.AttPaging1

Sent by RNC for Cell
Number of Paging Type 1 Messages

Counters
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.This counter complies with section "8.1.2 Paging" in
3GPP TS 25.331(v10.13.0).
Measurement point
The measurement is triggered at point B as shown in the figure when the RNC sends a message
of PAGING TYPE 1. This counter also includes the number of PAGING TYPE 1 messages
retransmitted by the RNC.
Figure 1-988 Sending Procedure of PAGING TYPE 1
Issue 03 (2015-06-30)

2273
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.UTRAN.AttPaging1
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of Preemptions by CS Paging due to PCH Congestion per Cell

Counters
Counter ID
Counter Name
Counter Description
73422072
VS.RRC.Paging1.PCHCong
.CSPreemptAtt
Number of Preemptions by
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.This counter complies with section "8.1.2
Paging" in 3GPP TS 25.331(v10.13.0).
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.
Issue 03 (2015-06-30)

2274
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.CSPreemptAtt
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of Successful Preemptions by CS Paging due to PCH Congestion per Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73422073
.CSPreemptSucc
Preemptions by CS Paging
due to PCH Congestion per
Cell

2275
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.This counter complies with section
"8.1.2 Paging" in 3GPP TS 25.331(v10.13.0).
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.CSPreemptSucc
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)

2276
BSC6900 UMTS
Number of Level-1 Paging Attempts for UEs Processing Real-Time or Non-RealTime Services in the URA_PCH State
Counters
Counter ID
Counter Name
Counter Description
73424293
VS.Paging1.Att1.URA.Real
Time.Cell
Number of Level-1 Paging

Attempts for UEs Processing
Real-Time Services in the
73424295
VS.Paging1.Att1.URA.Non
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.The preceding counters complies with section "8.1.2 Paging" in 3GPP TS
25.331(v10.13.0).
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-991 Procedure of PAGING TYPE 1
Issue 03 (2015-06-30)

2277
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging1.Att1.URA.Real
Time.Cell
WRFD-140206
Layered Paging in
URA_PCH
VS.Paging1.Att1.URA.Non
eRealTime.Cell
WRFD-140206
Layered Paging in
URA_PCH
Number of Successful Level-1 Paging Attempts for UEs Processing Real-Time or

Non-Real-Time Services in the URA_PCH State
Counters
Counter ID
Counter Name
Counter Description
73424294
VS.Paging1.Succ1.URA.Re
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
neRealTime.Cell
UEs Processing Non-RealTime 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.The preceding counters complies with section "8.3.1 Cell and URA update procedures"
in 3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

2278
BSC6900 UMTS
Measurement point
The measurement is triggered at point B shown in the figure when both of the following
conditions are met: The RNC has sent PAGING TYPE 1 messages to the cells on which UEs in
the URA_PCH state camped recently and to their neighboring cells (level-1 paging) and starts
a paging response timer. Before the timer expires, the RNC receives CELL UPDATE messages
with the cause value of uplinkDataTransmission or a paging response from the UEs.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Paging1.Succ1.URA.Re
alTime.Cell
WRFD-140206
Layered Paging in
URA_PCH
VS.Paging1.Succ1.URA.No
neRealTime.Cell
WRFD-140206
Layered Paging in
URA_PCH

2279
BSC6900 UMTS
Number of Successful Layered Paging Attempts for UEs Processing Real-Time or

Non-Real-Time Services in the URA_PCH State
Counters
Counter ID
Counter Name
Counter Description
73424297
VS.Paging1.TotalSucc.URA
.RealTime.Cell
Layered Paging Attempts for
UEs Processing Real-Time
Services in the URA_PCH
State for Cell
73424298
.NoneRealTime.Cell
Layered Paging Attempts for
UEs Processing Non-RealTime 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.The preceding counters complies with section "8.3.1 Cell and URA update procedures"
in 3GPP TS 25.331 (v10.13.0).
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.
Issue 03 (2015-06-30)

2280
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.RealTime.Cell
WRFD-140206
Layered Paging in
URA_PCH
.NoneRealTime.Cell
WRFD-140206
Layered Paging in
URA_PCH
Number of PAGING TYPE 1 Messages Sent by the RNC to UEs in the URA_PCH
State
Counters
Counter ID
Counter Name
Counter Description
73394912
VS.UTRAN.Paging1.Att.Ur
aPCH
Number of PAGING TYPE 1

Messages Sent by the RNC to
UEs in the URA_PCH State
for Cell
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC to UEs in
the URA_PCH state in a cell.This counter complies with section "8.1.2 Paging" in 3GPP TS
25.331(v10.13.0).
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.
Issue 03 (2015-06-30)

2281
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.UTRAN.Paging1.Att.Ur
aPCH
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of CS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State
Counters
Counter ID
Counter Name
Counter Description
73394913
VS.UTRAN.Paging1.Att.Idl
e.CS
Number of CS PAGING
TYPE 1 Messages Sent by
the RNC to UEs in the Idle
State for Cell
Description
This counter measures the number of PAGING TYPE 1 messages sent by the RNC in the CS
domain to UEs in the idle state in a cell.This counter complies with section "8.1.2 Paging" in
3GPP TS 25.331(v10.13.0).
Issue 03 (2015-06-30)

2282
BSC6900 UMTS
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
Counter Name
Feature ID
Feature Name
e.CS
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of PS PAGING TYPE 1 Messages Sent by the RNC to UEs in the Idle State
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73394914
e.PS
Number of PS PAGING
TYPE 1 Messages Sent by
the RNC to UEs in the Idle
State for Cell

2283
BSC6900 UMTS
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.This counter complies with section "8.1.2 Paging" in
3GPP TS 25.331(v10.13.0).
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
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
e.PS
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)

2284
BSC6900 UMTS
Number of Level-1 Paging Attempts for UEs Performing Real-Time or Non-RealTime Services in Idle Mode for Cell
Counters
Counter ID
Counter Name
Counter Description
73425838
VS.Paging1.Att1.Idle.RealT
ime.Cell

Attempts for UEs Performing
Real-Time Services in Idle
Mode for Cell
73425840
VS.Paging1.Att1.Idle.None
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.This counter complies with
section "8.1.2 Paging" in 3GPP TS 25.331(v10.13.0).
Measurement point
The measurement is triggered at point A shown in the figure when the RNC sends PAGING
TYPE 1 messages to the last cell that a UE is camped on and to its neighboring cells. If the UE
is performing real-time services, the VS.Paging1.Att1.Idle.RealTime.Cell counter is measured
in the last camped-on cell. If the UE is performing non-real-time services, the
VS.Paging1.Att1.Idle.NoneRealTime.Cell counter is measured in the last camped-on cell.
Figure 1-997 How a UE in idle mode responds to the PAGING TYPE 1 message
Issue 03 (2015-06-30)

2285
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.Paging1.Att1.Idle.RealT
ime.Cell
WRFD-150205
Layered Paging in Idle Mode
VS.Paging1.Att1.Idle.None
RealTime.Cell
WRFD-150205
Number of Successful Level-1 Paging Attempts for UEs Performing Real-Time or

Non-Real-Time Services in Idle Mode for Cell
Counters
Counter ID
Counter Name
Counter Description
73425839
VS.Paging1.Succ1.Idle.Real
Time.Cell
UEs Performing Real-Time
Services in Idle Mode for
Cell
73425841
VS.Paging1.Succ1.Idle.Non
eRealTime.Cell
UEs Performing Non-RealTime 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.The preceding
counters complies with section "8.1.3 RRC connection establishment" in 3GPP TS 25.331
(v10.13.0).
Issue 03 (2015-06-30)

2286
BSC6900 UMTS
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-998 How a UE in idle mode responds to the PAGING TYPE 1 message
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Paging1.Succ1.Idle.Real
Time.Cell
WRFD-150205
VS.Paging1.Succ1.Idle.Non
eRealTime.Cell
WRFD-150205

2287
BSC6900 UMTS
Number of Times a UE Processing SMS services Attempts to Preempt Resources

to Be Allocated to Other UEs When the PCH Is Congested for Cell
Counters
Counter ID
Counter Name
Counter Description
73426165
.SMSPreemptAtt
Number of Times a UE
Processing SMS services
Attempts to Preempt
Resources to Be Allocated to
Other UEs When the PCH Is
Congested for Cell
Description
This counter provides the number of times that SMS paging preempts the resources of the other
paging due to PCH congestion in a cell.This counter complies with section "8.1.2 Paging" in
3GPP TS 25.331(v10.13.0).
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.
Formula
None
Issue 03 (2015-06-30)

2288
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.SMSPreemptAtt
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of Successful Preemptions by SMS Paging due to PCH Congestion per

Cell
Counters
Counter ID
Counter Name
Counter Description
73426166
.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.This counter complies with section "8.1.2
Paging" in 3GPP TS 25.331(v10.13.0).
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.
Issue 03 (2015-06-30)

2289
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.SMSPreemptSucc
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
Number of ETWS-related PAGING TYPE 1 Messages Sent in a Cell

Counters
Counter ID
Counter Name
Counter Description
73426313
VS.UTRAN.Paging1.Att.Et
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 ETWSrelated information.This counter complies with section "8.1.2 Paging" in 3GPP TS 25.331
(v10.13.0).
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.
Figure 1-1001 Message interactions for paging type 1
Issue 03 (2015-06-30)

2290
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.UTRAN.Paging1.Att.Et
ws
WRFD-150234

Number of CS Paging Preemption Attempts Initiated by Platinum Users upon PCH

Congestion for Cell
Counters
Counter ID
Counter Name
Counter Description
73430425
.CSPreemptAtt.Platinum
Number of CS Paging
Preemption Attempts
Initiated by Platinum Users
upon PCH Congestion for
Cell
Description
This counter provides the number of CS paging preemption attempts initiated by platinum users
in the case of PCH congestion in a cell. This counter complies with 3GPP TS 25.331 (V10.13.0).
For details about this counter, see section 8.1.2 "Paging" in this TS.
Measurement point
The measurement is triggered at point A in the following figure. When PCH congestion occurs
in a cell and the CS services of platinum users in this cell attempt to preempt the paging resources
to be allocated to other services, this counter is measured. Other services refer to conversational,
streaming, interactive, background, or SMS services.
Issue 03 (2015-06-30)

2291
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.CSPreemptAtt.Platinum
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-150204
Number of Successful CS Paging Preemption Attempts Initiated by Platinum Users

upon PCH Congestion for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430426
.CSPreemptSucc.Platinum
Paging Preemption Attempts
Cell

2292
BSC6900 UMTS
Description
This counter provides the number of times CS services of platinum users successfully preempt
the paging resources to be allocated to other services in the case of PCH congestion in a cell.
section 8.1.2 "Paging" in this TS.
Measurement point
The measurement is triggered at point B in the following figure. When PCH congestion occurs
in a cell, the CS services of platinum users in this cell successfully preempt the paging resources
to be allocated to other services, and the CS paging message for platinum users is successfully
sent, this counter is measured. Other services refer to conversational, streaming, interactive,
background, or SMS services.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.CSPreemptSucc.Platinum
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-150204
Issue 03 (2015-06-30)

2293
BSC6900 UMTS
Number of PS Paging Preemption Attempts Initiated by Platinum Users upon PCH

Congestion for Cell
Counters
Counter ID
Counter Name
Counter Description
73430427
.PSPreemptAtt.Platinum
Number of PS Paging
Preemption Attempts
Cell
Description
This counter provides the number of PS paging preemption attempts initiated by platinum users
in the case of PCH congestion in a cell. This counter complies with 3GPP TS 25.331 (V10.13.0).
For details about this counter, see section 8.1.2 "Paging" in this TS.
Measurement point
The measurement is triggered at point A in the following figure. When PCH congestion occurs
in a cell and the PS services of platinum users in this cell attempt to preempt the paging resources
to be allocated to other services, this counter is measured. Other services refer to streaming,
interactive, background, or SMS services.
Formula
None
Issue 03 (2015-06-30)

2294
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.PSPreemptAtt.Platinum
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-150204
Number of Successful PS Paging Preemption Attempts Initiated by Platinum Users

upon PCH Congestion for Cell
Counters
Counter ID
Counter Name
Counter Description
73430428
.PSPreemptSucc.Platinum
Paging Preemption Attempts
Cell
Description
This counter provides the number of times PS services of platinum users successfully preempt
the paging resources to be allocated to other services in the case of PCH congestion in a cell.
section 8.1.2 "Paging" in this TS.
Measurement point
The measurement is triggered at point B in the following figure. When PCH congestion occurs
in a cell, the PS services of platinum users in this cell successfully preempt the paging resources
to be allocated to other services, and the PS paging message for platinum users is successfully
sent, this counter is measured. Other services refer to streaming, interactive, background, or
SMS services.
Issue 03 (2015-06-30)

2295
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.PSPreemptSucc.Platinum
WRFD-010301
Paging UE in Idle,
CELL_PCH, URA_PCH
State (Type 1)
WRFD-150204
1.12.25 Parking Measurement<per Cell>(Parking.Cell)

Overview
The Parking.Cell function subset measures the number of times UEs enter the RB Parking state,
the number of times RB Parking UEs are normally released, the number of times RB Parking
UEs are abnormally released, and the average number of RB Parking UEs in the CELL_FACH
state in a cell.
When radio resources in a cell become congested, UEs processing a single PS BE service cannot
access the cell. In this case, the RB Parking feature transits these UEs to the CELL_FACH state
and includes the "Pending time after trigger" and "Tx interruption after trigger" IEs with large
values in MEASUREMENT CONTROL messages for events 4A and 4B to stop these UEs'
uplink and downlink data transmission for a short period of time.
Issue 03 (2015-06-30)

2296
BSC6900 UMTS
The RB Parking feature can address retaliatory PS RRC connection setup retries in case of
extreme congestion and improve the PS service admission efficiency.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73427975
VS.F2DAccessFail.
Parking
Number of Times
UEs Enter the RB
Parking State After
F2D State Transition
Failures Due to
Resource
BSC6900
V900R016C00
73427976
VS.RAB.SuccEstab
PS.Parking.0kbps
Number of Times
That RB Parking
UEs Successfully
Access Cells at the
Rate DCH 0/0 kbit/s
for Cell
BSC6900
V900R016C00
73427996
VS.RAB.NormRel
PS.Parking
Number of Normally
Released RABs for
UEs in the Parking
State for Cell
BSC6900
V900R016C00
73427997
VS.RAB.AbnormR
elPS.Parking
Number of
Abnormally
Released RABs for
UEs in the Parking
State for Cell
BSC6900
V900R016C00
73444330
VS.CellFACHUEs.
Parking.Mean
Average Number of
RB Parking UEs in
the CELL_FACH
State for Cell
BSC6900
V900R016C00
73444331
VS.CellEFACHUE
s.Parking.Mean
Average Number of
RB Parking UEs over
the E-FACH for Cell
BSC6900
V900R016C00
73428872
VS.PSPreempted.D
2F.Att.Parking
Number of Times PS
BE UEs Attempt to
Enter the RB Parking
State After D2F State
Transitions Caused
by Preemption
BSC6900
V900R016C00

2297
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428873
VS.PSPreempted.D
2F.Succ.Parking
Number of Times PS
BE UEs Successfully
Enter the RB Parking
State After D2F State
Transitions Caused
by Preemption
BSC6900
V900R016C00
73428874
VS.PS0kbps.D2F.A
tt.Parking
Number of D2F State

Transition Attempts
Initiated by 0 kbit/s
UEs in RB Parking
State
BSC6900
V900R016C00
73428875
VS.PS0kbps.D2F.S
ucc.Parking
Number of
Successful D2F State
Transitions Initiated
by 0 kbit/s UEs in RB
Parking State
BSC6900
V900R016C00
73428877
VS.RAC.FailParki
ng.FachDcchCong
Number of Failed
Requests for FACH
DCCH congestion
During RB Parking
Setup for Cell
BSC6900
V900R016C00
Counter
Sub Counter
VS.CellFACHUEs.Parking.Mean
VS.CellEFACHUEs.Parking.Mean
Number of Times UEs Enter the RB Parking State After F2D State Transition
Failures Due to Resource Insufficiency
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73427975
VS.F2DAccessFail.Parking
Number of Times UEs Enter

the RB Parking State After
F2D State Transition Failures
Due to Resource

2298
BSC6900 UMTS
Description
When the RB Parking feature is activated, a UE enters the RB Parking state after a CELL_FACHto-CELL_DCH (F2D) state transition failure due to resource insufficiency. This counter
provides the number of times UEs enter the RB Parking state after an F2D state transition failure
due to resource insufficiency in a cell. This counter helps evaluate the performance of the RB
Parking feature.This counter complies with section "8.4 Measurement procedures" in 3GPP TS
25.331 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when a UE experiences an F2D
state transition failure due to resource insufficiency. In this case, the UE enters the RB Parking
state and the RNC sends the UE a MEASUREMENT CONTROL message instructing the UE
to stop transmitting data. Then, this counter is incremented by one in the cell on which the UE
camps.
Figure 1-1006 Entering the RB Parking state after an F2D state transition failure due to resource
insufficiency
Formula
None
Unit
None
Issue 03 (2015-06-30)

2299
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.F2DAccessFail.Parking
WRFD-160206
RB Parking
Number of Times That RB Parking UEs Successfully Access Cells at the Rate DCH
0/0 kbit/s
Counters
Counter ID
Counter Name
Counter Description
73427976
VS.RAB.SuccEstabPS.Parking.0kbps
Number of Times That RB

Parking UEs Successfully
Access Cells at the Rate DCH
0/0 kbit/s for Cell
Description
After the RB Parking feature is enabled, the RNC switches a UE to the RB Parking state if the
UE that has only RRC connection fails to set up a PS BE RAB. That is, the RNC allows the UE
to access a cell at a rate of DCH 0/0 kbit/s and then switches the UE from the CELL_DCH state
to the CELL_FACH state. This counter measures the number of times that RB Parking UEs
successfully access a cell at a rate of DCH 0/0 kbit/s.This counter complies with section "8.2
Measurement point
BEARER SETUP COMPLETE message from a UE and the RNC sends a RAB ASSIGNMENT
RESPONSE message to the SGSN. In this case, this counter is incremented by one in the cell
on which the UE camps if the UE has entered the RB Parking state.
Issue 03 (2015-06-30)

2300
BSC6900 UMTS
Figure 1-1007 RB Parking UEs successfully accessing a cell at a rate of 0/0 kbit/s on the DCH
and successfully triggering D2F state transitions
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabPS.Parking.0kbps
WRFD-160206
RB Parking

2301
BSC6900 UMTS
Number of Normally Released RABs for UEs in the Parking State for Cell
Counters
Counter ID
Counter Name
Counter Description
73427996
VS.RAB.NormRelPS.Parking
Number of Normally
Released RABs for UEs in
the Parking State for Cell
Description
This counter measures the number of RABs that are normally released for UEs in the Parking
state in a cell. This counter is used to evaluate the impact of the Parking function on the PS call
drop rate.This counter complies with section "8 RANAP Procedures" in 3GPP TS 25.413
(v10.10.0).
Measurement point
As shown by point A in the following figure, after receiving an IU RELEASE COMMAND
message from the CN, the RNC releases the corresponding RAB and returns an IU RELEASE
COMPLETE message. This counter is measured in the best cell for the UE in the Parking state
when the following condition is met: The release cause in the IU RELEASE COMMAND
receiving the IU RELEASE COMMAND message.
Figure 1-1008 Iu connection release procedure for UEs in the Parking state
Issue 03 (2015-06-30)

2302
BSC6900 UMTS
As shown by point B in the following figure, after receiving a RAB ASSIGNMENT REQUEST
message with a RAB release request from the CN, the RNC releases the corresponding RAB
and returns a RAB ASSIGNMENT RESPONSE message. This counter is measured in the best
cell for the UE in the Parking state when the following condition is met: The release cause in
the RAB ASSIGNMENT REQUEST message is "User Inactivity", "Normal Release",
"Successful Relocation", or "Network Optimization." Alternatively, the RNC has initiated a
release request with the cause value "User Inactivity", "Network Optimization", or "UE
Generated Signalling Connection Release" before receiving the RAB ASSIGNMENT
REQUEST message.
Figure 1-1009 Successful RAB assignment release procedure for UEs in the Parking state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRelPS.Parking
WRFD-160206
RB Parking

2303
BSC6900 UMTS
Number of Abnormally Released RABs for UEs in the Parking State for Cell
Counters
Counter ID
Counter Name
Counter Description
73427997
VS.RAB.AbnormRelPS.Par
king
Released RABs for UEs in
the Parking State for Cell
Description
This counter measures the number of RABs that are abnormally released for UEs in the Parking
state in a cell. This counter is used to evaluate the impact of the Parking function on the PS call
drop rate.This counter complies with section "8 RANAP Procedures" in 3GPP TS 25.413
(v10.10.0).
Measurement point
The measurement is triggered at point A in the following figure. When an error occurs, the RNC
sends a RAB RELEASE REQUEST message to the CN. If the RNC receives from the CN a
RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity",
"Normal Release", "Successful Relocation", or "Network Optimization", this counter is
measured in the best cell for the UE in the Parking state. For details about cause values indicating
a normal release, see 3GPP TS 25.413.
Figure 1-1010 RAB release procedure for UEs in the Parking state
Issue 03 (2015-06-30)

2304
BSC6900 UMTS
sends a RAB RELEASE REQUEST message to the CN. If the RNC receives from the CN an
IU RELEASE COMMAND message with a cause value other than "User Inactivity", "Normal
Release", "Successful Relocation", or "Network Optimization", this counter is measured in the
best cell for the UE in the Parking state. For details about cause values indicating a normal
Figure 1-1011 Iu connection release procedure triggered by the RNC for UEs in the Parking
state
sends an IU RELEASE REQUEST message to the CN. If the RNC receives from the CN an IU
RELEASE COMMAND message with a cause value other than "User Inactivity", "Normal
Release", "Successful Relocation", or "Network Optimization", this counter is measured in the
best cell for the UE in the Parking state. For details about cause values indicating a normal
Issue 03 (2015-06-30)

2305
BSC6900 UMTS
Figure 1-1012 Iu connection release procedure triggered by the RNC for UEs in the Parking
state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRelPS.Par
king
WRFD-160206
RB Parking

2306
BSC6900 UMTS
Average Number of RB Parking UEs in the CELL_FACH State for Cell

Counters
Counter ID
Counter Name
Counter Description
73444330
VS.CellFACHUEs.Parking.
Mean
Average Number of RB
Parking UEs in the
73444331
VS.CellEFACHUEs.Parking
.Mean
Average Number of RB
Parking UEs over the EFACH for Cell
Description
This counter provides the average numbers of RB Parking UEs in the CELL_FACH state.
Counter Name
Description
VS.CellFACHUEs.Parking.Mean

RB Parking UEs in the CELL_FACH state to
evaluate the impact of the number of RB
Parking UEs on FACH specifications.
VS.CellEFACHUEs.Parking.Mean

RB Parking UEs over the E-FACH to
evaluate the impact of the number of RB
Parking UEs on E-FACH specifications.
Measurement point
At an interval of 5 seconds, the RNC samples the number of RB Parking UEs in the CELL_FACH
state. At the end of a measurement period, the RNC divides the accumulated number by the
number of samples. Then, the average number of such UEs within the measurement period is
obtained.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2307
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CellFACHUEs.Parking.
Mean
WRFD-160206
RB Parking
VS.CellEFACHUEs.Parking
.Mean
WRFD-160206
RB Parking
Number of Times PS BE UEs Attempt to Enter the RB Parking State After D2F State
Transitions Caused by Preemption
Counters
Counter ID
Counter Name
Counter Description
73428872
VS.PSPreempted.D2F.Att.P
arking
Number of Times PS BE UEs

Attempt to Enter the RB
Parking State After D2F
State Transitions Caused by
Preemption
Description
After the RB Parking feature is enabled, the RNC switches a PS BE UE to the RB Parking state
if the PS BE UE's resources are preempted by other services. That is, the RNC switches the PS
BE UE from the CELL_DCH state to the CELL_FACH state. This counter provides the number
of times PS BE UEs attempt to enter the RB Parking state after D2F state transitions caused by
preemption.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP
TS 25.331 (v10.10.0).
Measurement point
The measurement is triggered at point A in the following figure. When a PS BE UE's resources
are preempted by other services, the RNC switches the PS BE UE from the CELL_DCH state
to the CELL_FACH state if the requirements of RB Parking are met. The requirements of RB
Parking are as follows: (1)The UE processes only PS BE services. (2)The best cell for the UE
is under the SRNC. This counter is measured in the best cell for the UE when the RNC sends a
RADIO BEARER RECONFIGRATION message to the UE, instructing the UE to perform a
D2F state transition.
Issue 03 (2015-06-30)

2308
BSC6900 UMTS
Figure 1-1013 RB Parking procedure for UEs whose resources are preempted by other services
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PSPreempted.D2F.Att.P
arking
WRFD-160206
RB Parking

2309
BSC6900 UMTS
Number of Times PS BE UEs Successfully Enter the RB Parking State After D2F
State Transitions Caused by Preemption
Counters
Counter ID
Counter Name
Counter Description
73428873
VS.PSPreempted.D2F.Succ.
Parking
Number of Times PS BE UEs

Successfully Enter the RB
Parking State After D2F
State Transitions Caused by
Preemption
Description
After the RB Parking feature is enabled, the RNC switches a PS BE UE to the RB Parking state
if the PS BE UE's resources are preempted by other services. That is, the RNC switches the PS
BE UE from the CELL_DCH state to the CELL_FACH state. This counter provides the number
of times PS BE UEs successfully enter the RB Parking state after D2F state transitions caused
by preemption.This counter complies with section "8.2 Radio Bearer control procedures" in
3GPP TS 25.331 (v10.10.0).
Measurement point
The measurement is triggered at point B in the following figure. When a PS BE UE's resources
are preempted by other services, the RNC switches the PS BE UE from the CELL_DCH state
to the CELL_FACH state if the requirements of RB Parking are met. The requirements of RB
Parking are as follows: (1)The UE processes only PS BE services. (2)The best cell for the UE
is under the SRNC. This counter is measured when the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE, indicating that the D2F state
transition is complete. It is measured in the best cell for the UE before the D2F state transition.
Issue 03 (2015-06-30)

2310
BSC6900 UMTS
Figure 1-1014 RB Parking procedure for UEs whose resources are preempted by other services
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PSPreempted.D2F.Succ.
Parking
WRFD-160206
RB Parking

2311
BSC6900 UMTS
Number of D2F State Transition Attempts Initiated by 0 kbit/s UEs in RB Parking

State
Counters
Counter ID
Counter Name
Counter Description
73428874
VS.PS0kbps.D2F.Att.Parking
Number of D2F State

Transition Attempts Initiated
by 0 kbit/s UEs in RB Parking
State
Description
UE that has only an RRC connection fails to set up a PS BE RAB. That is, the RNC allows the
UE to access a cell at a rate of 0/0 kbit/s on the DCH and then switches the UE from the
CELL_DCH state to the CELL_FACH state. This counter provides the number of D2F state
transition attempts initiated UEs in the RB Parking state and with a 0 kbit/s rate.This counter
Measurement point
The measurement is triggered at point C in the following figure. When the RNC sends a RADIO
BEARER RECONFIGURATION message to the UE, instructing the UE to perform a D2F state
transition, this counter is measured in the best cell if the UE is in the RB Parking state.
Issue 03 (2015-06-30)

2312
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS0kbps.D2F.Att.Parking
WRFD-160206
RB Parking

2313
BSC6900 UMTS
Number of Successful D2F State Transitions Initiated by 0 kbit/s UEs in RB Parking

State
Counters
Counter ID
Counter Name
Counter Description
73428875
VS.PS0kbps.D2F.Succ.Park
ing
Number of Successful D2F

State Transitions Initiated by
0 kbit/s UEs in RB Parking
State
Description
UE that has only an RRC connection fails to set up a PS BE RAB. That is, the RNC allows the
UE to access a cell at a rate of 0/0 kbit/s on the DCH and then switches the UE from the
CELL_DCH state to the CELL_FACH state. This counter provides the number of successful
D2F state transitions initiated by UEs in the RB Parking state and with a 0 kbit/s rate.This counter
Measurement point
The measurement is triggered at point D in the following figure. When the RNC receives a
RADIO BEARER RECONFIGURATION COMPLETE message from the UE, indicating that
the D2F state transition is complete, this counter is measured in the best cell before the state
transition if the UE is in the RB Parking state.
Issue 03 (2015-06-30)

2314
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS0kbps.D2F.Succ.Park
ing
WRFD-160206
RB Parking

2315
BSC6900 UMTS
Number of Failed Requests for FACH DCCH congestion During RB Parking Setup
Counters
Counter ID
Counter Name
Counter Description
73428877
VS.RAC.FailParking.FachD
cchCong

for FACH DCCH congestion
During RB Parking Setup for
Cell
Description
After the RB Parking feature is enabled, the RNC switches a UE in idle mode to the RB Parking
state if the UE fails to set up a PS BE RAB and the admission fails. That is, the RNC allows the
UE to set up an RB at a rate of DCH 0/0 kbit/s and then switches the UE from the CELL_DCH
state to the CELL_FACH state. In addition, if the PS BE UE's radio resources are preempted by
other higher-priority UEs, the RNC switches the PS BE UE from the CELL_DCH state to the
CELL_FACH state. If the DCCH carried on the FACH is congested in the cell to which the PS
BE UE belongs in the preceding scenarios, the RNC undoes RB Parking for the UE and releases
the UE's RRC connection. This counter measures the number of times that the RNC undoes RB
Parking due to FACH DCCH congestion in a cell.This counter complies with section "8.2 Radio
Measurement point
The measurement is triggered at point A shown in the following figure. When a PS BE UE fails
to be admitted, the RNC attempts to set up an RB at a rate of DCH 0/0 kbit/s for the UE if the
conditions for RB Parking are met: The UE processes only PS BE services and the best cell of
the UE is under the SRNC. If the FACH DCCH of the cell is congested at this time, the RNC
undoes the RB setup for the UE and releases the UE's RRC connection In this case, this counter
is measured in the current cell.
Issue 03 (2015-06-30)

2316
BSC6900 UMTS
Figure 1-1017 RB Parking triggered by admission failures for a PS BE UE
The measurement is triggered at point B shown in the following figure. When a PS BE UE fails
to be admitted after an RB setup at a rate of DCH 0/0 kbit/s, the RNC attempts to switch the UE
from the CELL_DCH state to the CELL_FACH state if the conditions for RB Parking are met:
The UE processes only PS BE services and the best cell of the UE is under the SRNC. If the
FACH DCCH of the cell is congested at this time, the RNC undoes the CELL_DCH-toCELL_FACH state transition and releases the UE's RRC connection. In this case, this counter
is measured in the current cell.
Issue 03 (2015-06-30)

2317
BSC6900 UMTS
Figure 1-1018 RB Parking triggered by admission failures for a PS BE UE
The measurement is triggered at point A shown in the following figure. When the radio resources
of a PS BE UE are preempted by other higher-priority UEs, the RNC attempts to perform RB
Parking for the UE if the conditions for RB Parking are met: The UE processes only PS BE
services and the best cell of the UE is under the SRNC. If the FACH DCCH of the cell is
congested at this time, the RNC undoes RB Parking and releases the UE's RRC connection. In
this case, this counter is measured in the current cell.
Issue 03 (2015-06-30)

2318
BSC6900 UMTS
Figure 1-1019 RB Parking triggered by resource preemption on a PS BE UE
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAC.FailParking.FachD
cchCong
WRFD-160206
RB Parking
1.12.26 CNOperator Measurement <per Cell>(PLMN.CELL)

Overview
This function subset provides counters measured by operator in a cell.
Issue 03 (2015-06-30)

2319
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441192
VS.LC.ULCreditU
sed.Mean.PLMN0
Average Uplink
Credit Consumption
of Operator0 for Cell
BSC6900
V900R013
73441193
VS.LC.ULCreditU
sed.Mean.PLMN1
Average Uplink
Credit Consumption
BSC6900
V900R013
73441194
VS.LC.ULCreditU
sed.Mean.PLMN2
Average Uplink
Credit Consumption
BSC6900
V900R013
73441195
VS.LC.ULCreditU
sed.Mean.PLMN3
Average Uplink
Credit Consumption
BSC6900
V900R013
73423831
VS.LC.ULCreditU
sed.Min.PLMN0
Minimum Uplink
Credit Consumption
BSC6900
V900R013
73423832
VS.LC.ULCreditU
sed.Min.PLMN1
Minimum Uplink
Credit Consumption
BSC6900
V900R013
73423833
VS.LC.ULCreditU
sed.Min.PLMN2
Minimum Uplink
Credit Consumption
BSC6900
V900R013
73423834
VS.LC.ULCreditU
sed.Min.PLMN3
Minimum Uplink
Credit Consumption
BSC6900
V900R013
73423835
VS.LC.ULCreditU
sed.Max.PLMN0
Maximum Uplink
Credit Consumption
BSC6900
V900R013
73423836
VS.LC.ULCreditU
sed.Max.PLMN1
Maximum Uplink
Credit Consumption
BSC6900
V900R013
73423837
VS.LC.ULCreditU
sed.Max.PLMN2
Maximum Uplink
Credit Consumption
BSC6900
V900R013
73423838
VS.LC.ULCreditU
sed.Max.PLMN3
Maximum Uplink
Credit Consumption
BSC6900
V900R013

2320
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441196
VS.CSLoad.Erlang
.Equiv.PLMN0
Average Equivalent
Erlangs Consumed
by CS Services of
Operator0 for Cell
BSC6900
V900R013
73441197
VS.CSLoad.Erlang
.Equiv.PLMN1
Average Equivalent
Erlangs Consumed
by CS Services of
Operator1 for Cell
BSC6900
V900R013
73441198
VS.CSLoad.Erlang
.Equiv.PLMN2
Average Equivalent
Erlangs Consumed
by CS Services of
Operator2 for Cell
BSC6900
V900R013
73441199
VS.CSLoad.Erlang
.Equiv.PLMN3
Average Equivalent
Erlangs Consumed
by CS Services of
Operator3 for Cell
BSC6900
V900R013
73441200
VS.RAB.SFOccupy
.PLMN0
Average Number of
Spreading Codes
Occupied by
Operator0 for Cell
BSC6900
V900R013
73441201
VS.RAB.SFOccupy
.PLMN1
Average Number of
Spreading Codes
Occupied by
Operator1 for Cell
BSC6900
V900R013
73441202
VS.RAB.SFOccupy
.PLMN2
Average Number of
Spreading Codes
Occupied by
Operator2 for Cell
BSC6900
V900R013
73441203
VS.RAB.SFOccupy
.PLMN3
Average Number of
Spreading Codes
Occupied by
Operator3 for Cell
BSC6900
V900R013
73423839
VS.RAB.SFOccupy
.MAX.PLMN0
Maximum Number
of Spreading Codes
Occupied by
Operator0 for Cell
BSC6900
V900R013
73423840
VS.RAB.SFOccupy
.MAX.PLMN1
Maximum Number
of Spreading Codes
Occupied by
Operator1 for Cell
BSC6900
V900R013

2321
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423841
VS.RAB.SFOccupy
.MAX.PLMN2
Maximum Number
of Spreading Codes
Occupied by
Operator2 for Cell
BSC6900
V900R013
73423842
VS.RAB.SFOccupy
.MAX.PLMN3
Maximum Number
of Spreading Codes
Occupied by
Operator3 for Cell
BSC6900
V900R013
73424840
VS.RAB.SFOccupy
.MAX.SharedOper
ator0
Maximum Number
of Spreading Codes
Occupied by Shared
Operator0 for
MOCN Cell
BSC6900
V900R014
73441525
VS.RAB.SFOccupy
.SharedOperator0
Average Number of
Spreading Codes
Occupied by Shared
Operator0 for
MOCN Cell
BSC6900
V900R014
73424843
VS.RAB.SFOccupy
.MAX.SharedOper
ator1
Maximum Number
of Spreading Codes
Occupied by Shared
Operator1 for
MOCN Cell
BSC6900
V900R014
73441526
VS.RAB.SFOccupy
.SharedOperator1
Average Number of
Spreading Codes
Occupied by Shared
Operator1 for
MOCN Cell
BSC6900
V900R014
73424846
VS.RAB.SFOccupy
.MAX.SharedOper
ator2
Maximum Number
of Spreading Codes
Occupied by Shared
Operator2 for
MOCN Cell
BSC6900
V900R014
73441527
VS.RAB.SFOccupy
.SharedOperator2
Average Number of
Spreading Codes
Occupied by Shared
Operator2 for
MOCN Cell
BSC6900
V900R014

2322
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73424849
VS.RAB.SFOccupy
.MAX.SharedOper
ator3
Maximum Number
of Spreading Codes
Occupied by Shared
Operator3 for
MOCN Cell
BSC6900
V900R014
73441528
VS.RAB.SFOccupy
.SharedOperator3
Average Number of
Spreading Codes
Occupied by Shared
Operator3 for
MOCN Cell
BSC6900
V900R014
None
Credit Consumption of Operator0

Counters
Counter ID
Counter Name
Counter Description
73441192
.PLMN0

Consumption of Operator0
for Cell
73423831
VS.LC.ULCreditUsed.Min.
PLMN0
Minimum Uplink Credit

for Cell
73423835
VS.LC.ULCreditUsed.Max.
PLMN0

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.
Issue 03 (2015-06-30)

2323
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None

Counters
Counter ID
Counter Name
Counter Description
73441193
.PLMN1

for Cell
73423832
PLMN1

for Cell
73423836
PLMN1

for Cell
Description
Measurement point
Formula
None
Unit
None
Issue 03 (2015-06-30)

2324
BSC6900 UMTS
Related Features
None

Counters
Counter ID
Counter Name
Counter Description
73441194
.PLMN2

for Cell
73423833
PLMN2

for Cell
73423837
PLMN2

for Cell
Description
Measurement point
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

2325
BSC6900 UMTS

Counters
Counter ID
Counter Name
Counter Description
73441195
.PLMN3

for Cell
73423834
PLMN3

for Cell
73423838
PLMN3

for Cell
Description
Measurement point
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

2326
BSC6900 UMTS
Equivalent Erlangs Consumed by CS Services of Operator0

Counters
Counter ID
Counter Name
Counter Description
73441196
LMN0

Consumed by CS Services of
Operator0 for Cell
Description
This counter provides the average equivalent Erlangs consumed by all CS services of operator0
in a cell.
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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441197
LMN1

Operator1 for Cell

2327
BSC6900 UMTS
Description
in a cell.
Measurement point
Formula
None
Unit
Erl
Related Features
None

Counters
Counter ID
Counter Name
Counter Description
73441198
LMN2

Operator2 for Cell
Description
in a cell.
Measurement point
Issue 03 (2015-06-30)

2328
BSC6900 UMTS
Formula
None
Unit
Erl
Related Features
None

Counters
Counter ID
Counter Name
Counter Description
73441199
LMN3

Operator3 for Cell
Description
in a cell.
Measurement point
Formula
None
Unit
Erl
Issue 03 (2015-06-30)

2329
BSC6900 UMTS
Related Features
None
Number of Spreading Codes Occupied by Operator0

Counters
Counter ID
Counter Name
Counter Description
73441200
VS.RAB.SFOccupy.PLMN
0
Average Number of
Spreading Codes Occupied
by Operator0 for Cell
73423839
VS.RAB.SFOccupy.MAX.P
LMN0
Maximum Number of
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
Issue 03 (2015-06-30)

2330
BSC6900 UMTS

Counters
Counter ID
Counter Name
Counter Description
73441201
1
Average Number of
73423840
LMN1
Maximum Number of
Description
Measurement point
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

2331
BSC6900 UMTS

Counters
Counter ID
Counter Name
Counter Description
73441202
2
Average Number of
73423841
LMN2
Maximum Number of
Description
Measurement point
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

2332
BSC6900 UMTS

Counters
Counter ID
Counter Name
Counter Description
73441203
3
Average Number of
73423842
LMN3
Maximum Number of
Description
Measurement point
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

2333
BSC6900 UMTS
Number of Spreading Codes Occupied by Shared Operator for MOCN Cell

Counters
Counter ID
Counter Name
Counter Description
73424840
VS.RAB.SFOccupy.MAX.S
haredOperator0
Maximum Number of
by Shared Operator0 for
MOCN Cell
73441525
VS.RAB.SFOccupy.SharedOperator0
Average Number of
MOCN Cell
73424843
haredOperator1
Maximum Number of
MOCN Cell
73441526
Average Number of
MOCN Cell
73424846
haredOperator2
Maximum Number of
MOCN Cell
73441527
Average Number of
MOCN Cell
73424849
haredOperator3
Maximum Number of
MOCN Cell
73441528
Average Number of
MOCN Cell
Description
These counters provide the R99 code resource usage for operators in an MOCN cell.
Issue 03 (2015-06-30)

2334
BSC6900 UMTS
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
Counter Name
Feature ID
Feature Name
haredOperator0
WRFD-021311
MOCN Introduction
Package
WRFD-021311
MOCN Introduction
Package
haredOperator1
WRFD-021311
MOCN Introduction
Package
WRFD-021311
MOCN Introduction
Package
haredOperator2
WRFD-021311
MOCN Introduction
Package
WRFD-021311
MOCN Introduction
Package
haredOperator3
WRFD-021311
MOCN Introduction
Package
WRFD-021311
MOCN Introduction
Package
1.12.27 PS service quality Measurement <per Cell>(PSService.Cell)

Overview
This function subset provides measurements related to experience of UEs performing PS
services.
Issue 03 (2015-06-30)

2335
BSC6900 UMTS
Measurements related to experience of UEs performing PS services can be classified into two
types: accessibility and service integrity.
1.Measurements related to accessibility consist of the following:
Number of uplink and downlink data service setup attempts and delay
2.Measurements related to service integrity consist of the following:
a)Round trip time (RTT) of the first TCP packet
b)Throughput of large traffic data services
1).Number of uplink and downlink data service setup attempts and delay
This function subset provides the number of uplink and downlink data service setup attempts
and successful setups initiated by UEs in the idle state, in the CELL_PCH and URA_PCH states,
and by UEs that are processing combined services. This function subset also provides the delay
of uplink and downlink data services initiated by these UEs.
Uplink data services: The RNC records uplink data service setup attempts for UEs in the idle
state, in the CELL_PCH/URA_PCH state, and that are processing combined services. When the
RNC receives the first uplink data packet from UEs, the RNC determines that the uplink data
service is successfully initiated.
Downlink data services: The RNC records downlink data service setup attempts for UEs in the
idle state, in the CELL_PCH/URA_PCH state, and that are processing combined services. When
the RNC successfully sends the first downlink data packet to UEs, the RNC determines that the
downlink data service is successfully initiated.
Note:
For UEs in the idle state
a).The measurement is not triggered for RRC CONNECTION REQUEST messages
retransmitted by UEs in the idle state.
b).The measurement is not triggered for RRC CONNECTION REQUEST messages that are
rejected due to redirection, that are discarded due to flow control, and that are processed in DSCR
procedures.
c).If UEs in the idle state receive an RRC SETUP COMPLETE message but does not establish
an Iu connection in the PS domain, or if the UE sends an INITIAL DIRECT TRANSFER
(Service Request) or UL DIRECT TRANSFER (Service Request) message to the PS domain of
the CN but the value of the "service type" IE in the message is not data, the measurement is not
triggered.
d).If UEs in the idle state receive an RRC SETUP COMPLETE message but does not establish
an Iu connection in the PS domain, or if the UE sends an INITIAL DIRECT TRANSFER
(Service Request) or UL DIRECT TRANSFER (Service Request) message to the PS domain of
the CN but the value of the "service type" IE in the message is not paging response, the
measurement is not triggered.
For UEs in the CELL_PCH and URA_PCH states
a).If the CELL UPDATE message carries RRC CAUSE and the cause value is "Originating
Conversational Call", "Emergency Call", or "Terminating Conversational Call", the
Issue 03 (2015-06-30)

2336
BSC6900 UMTS
For UEs that are processing combined services

a).In the UL DIRECT TRANSFER (Service Request) message sent to the PS domain of the CN,
if the value of the "service type" IE is not data, the measurement for uplink data services is not
triggered.
b).In the UL DIRECT TRANSFER (Service Request) message sent to the PS domain of the CN,
if the value of the "service type" IE is not "paging response", the measurement for downlink
data services is not triggered.
2).RTT of the first TCP data packet
This function subset provides the RTT of the uplink and downlink TCP packets after UEs
successfully initiate the uplink and downlink data services.
RTT of uplink TCP packets: Interval between the time the RNC receives the first uplink TCP
data packet and the time the RNC receives the first downlink TCP ACK packet
RTT of downlink TCP packets: Interval between the time the RNC receives the first downlink
TCP data packet and the time the RNC receives the first uplink TCP ACK packet
Note
a).For uplink data services, if the first uplink data packet is not a TCP data packet, the
b).For uplink data services, if the downlink TCP ACK packet is not received before the RAB is
released, the measurement is not triggered.
c).For downlink data services, if the first downlink data packet is not a TCP data packet, the
d).For downlink data services, if the uplink TCP ACK packet is not received before the RAB is
released, the measurement is not triggered.
Issue 03 (2015-06-30)

2337
BSC6900 UMTS
Figure 1-1020 Procedure for calculating the access delay and loopback delay of data services
Issue 03 (2015-06-30)

2338
BSC6900 UMTS
Measurement points
Description
A1
VS.ULPSServ.AttEstab.Idle,
VS.DLPSServ.AttEstab.Idle
A2
VS.ULPSServ.AttEstab.PCH,
VS.DLPSServ.AttEstab.PCH
A3
VS.ULPSServ.AttEstab.MultiRAB,
VS.DLPSServ.AttEstab.MultiRAB
B1
VS.ULPSServ.EstabDelay.Good.Num.Idle,
VS.ULPSServ.EstabDelay.Medium.Num.Id
le,
VS.ULPSServ.EstabDelay.Bad.Num.Idle,
VS.ULPSServ.EstabDelay.Good.Num.PCH,
VS.ULPSServ.EstabDelay.Medium.Num.P
CH,
VS.ULPSServ.EstabDelay.Bad.Num.PCH,
VS.ULPSServ.EstabDelay.Good.Num.MultiRAB,
VS.ULPSServ.EstabDelay.Medium.Num.M
ultiRAB,
VS.ULPSServ.EstabDelay.Bad.Num.MultiRAB
B2
VS.PS.ULFirstPacket.RTT.Good.Num,
VS.PS.ULFirstPacket.RTT.Medium.Num,
VS.PS.ULFirstPacket.RTT.Bad.Num
C1
VS.DLPSServ.EstabDelay.Good.Num.Idle,
VS.DLPSServ.EstabDelay.Medium.Num.Id
le,
VS.DLPSServ.EstabDelay.Bad.Num.Idle,
VS.DLPSServ.EstabDelay.Good.Num.PCH,
VS.DLPSServ.EstabDelay.Medium.Num.P
CH,
VS.DLPSServ.EstabDelay.Bad.Num.PCH,
VS.DLPSServ.EstabDelay.Good.Num.MultiRAB,
VS.DLPSServ.EstabDelay.Medium.Num.M
ultiRAB,
VS.DLPSServ.EstabDelay.Bad.Num.MultiRAB
C2
VS.PS.DLFirstPacket.RTT.Good.Num,
VS.PS.DLFirstPacket.RTT.Medium.Num,
VS.PS.DLFirstPacket.RTT.Bad.Num
The dotted box on the right in figure 2 shows layers above the RAN, which are constituted by
all the possible nodes configured between the Iu interface and SP, including the CN, Internet,
and server.
Issue 03 (2015-06-30)

2339
BSC6900 UMTS
Figure 1-1021 Network topology
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428536
VS.Video.Total.DL
Traffic
Total DL Traffic of
Video Services for
Cell
BSC6900
V900R016C00
73428537
VS.Video.Total.DL
TransTime
Total DL
Transmission Time
of Video Services for
Cell
BSC6900
V900R016C00
73428538
VS.VoIP.Total.DL
Traffic
Total DL Traffic of
VoIP Services for
Cell
BSC6900
V900R016C00
73428539
VS.VoIP.Total.DL
TransTime
Total DL
Transmission Time
of VoIP Services for
Cell
BSC6900
V900R016C00
73428540
VS.Web.Total.DLT
raffic
Total DL Traffic of
Web Services for
Cell
BSC6900
V900R016C00
73428541
VS.Web.Total.DLT
ransTime
Total DL
Transmission Time
of Web Services for
Cell
BSC6900
V900R016C00
73428542
VS.P2P.Total.DLT
raffic
Total DL Traffic of
P2P Services for Cell
BSC6900
V900R016C00
73428543
VS.P2P.Total.DLT
ransTime
Total DL
Transmission Time
of P2P Services for
Cell
BSC6900
V900R016C00

2340
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428701
VS.ULPSServ.AttE
stab.Idle
Number of UL Data
Service Setup
UEs in the Idle State
for Cell
BSC6900
V900R016C00
73444440
VS.ULPSServ.Esta
bMeanTime.Idle
Average Access
Delay of UL Data
Services
Successfully
Initiated by UEs in
Idle State for Cell
BSC6900
V900R016C00
73428704
VS.ULPSServ.Esta
bDelay.Good.Num.
Idle
Number of Times the

Access Delay of UL
Data Services Falls
in the GOOD Level
for UEs in Idle State
for Cell
BSC6900
V900R016C00
73428705
VS.ULPSServ.Esta
bDelay.Medium.Nu
m.Idle
Number of Times the

Access Delay of UL
Data Services Falls
in the MEDIUM
Level for UEs in Idle
State for Cell
BSC6900
V900R016C00
73428706
VS.ULPSServ.Esta
bDelay.Bad.Num.I
dle
Number of Times the

Access Delay of UL
Data Services Falls
in the BAD Level for
UEs in Idle State for
Cell
BSC6900
V900R016C00
73428707
VS.DLPSServ.AttE
stab.Idle
Number of DL Data
Service Setup
UEs in the Idle State
for Cell
BSC6900
V900R016C00
73444441
VS.DLPSServ.Esta
bMeanTime.Idle
Average Access
Delay of DL Data
Services
Successfully
Initiated by UEs in
Idle State for Cell
BSC6900
V900R016C00

2341
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428710
VS.DLPSServ.Esta
bDelay.Good.Num.
Idle
Number of Times the

Access Delay of DL
Data Services Falls
in the GOOD Level
for UEs in Idle State
for Cell
BSC6900
V900R016C00
73428711
VS.DLPSServ.Esta
bDelay.Medium.Nu
m.Idle
Number of Times the

Access Delay of DL
Data Services Falls
in the MEDIUM
Level for UEs in Idle
State for Cell
BSC6900
V900R016C00
73428712
VS.DLPSServ.Esta
bDelay.Bad.Num.I
dle
Number of Times the

Access Delay of DL
Data Services Falls
UEs in Idle State for
Cell
BSC6900
V900R016C00
73428713
VS.ULPSServ.AttE
stab.PCH
Number of UL Data
Service Setup
UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00
73444442
VS.ULPSServ.Esta
bMeanTime.PCH
Average Access
Delay of UL Data
UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00
73428716
VS.ULPSServ.Esta
bDelay.Good.Num.
PCH
Number of Times the

Access Delay of UL
Data Services Falls
in the GOOD Level
for UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00

2342
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428717
VS.ULPSServ.Esta
bDelay.Medium.Nu
m.PCH
Number of Times the

Access Delay of UL
Data Services Falls
in the MEDIUM
Level for UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00
73428718
VS.ULPSServ.Esta
bDelay.Bad.Num.P
CH
Number of Times the

Access Delay of UL
Data Services Falls
UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00
73428719
VS.DLPSServ.AttE
stab.PCH
Number of DL Data
Service Setup
UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00
73444443
VS.DLPSServ.Esta
bMeanTime.PCH
Average Access
Delay of DL Data
UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00
73428722
VS.DLPSServ.Esta
bDelay.Good.Num.
PCH
Number of Times the

Access Delay of DL
Data Services Falls
in the GOOD Level
for UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00

2343
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428723
VS.DLPSServ.Esta
bDelay.Medium.Nu
m.PCH
Number of Times the

Access Delay of DL
Data Services Falls
in the MEDIUM
Level for UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00
73428724
VS.DLPSServ.Esta
bDelay.Bad.Num.P
CH
Number of Times the

Access Delay of DL
Data Services Falls
UEs in the
CELL_PCH and
URA_PCH States for
Cell
BSC6900
V900R016C00
73428725
VS.ULPSServ.AttE
stab.MultiRAB
Number of UL Data
Service Setup
UEs Processing
Combined Services
for Cell
BSC6900
V900R016C00
73444444
VS.ULPSServ.Esta
bMeanTime.MultiRAB
Average Access
Delay of UL Data
Service Successfully
Initiated by UEs
Processing
Combined Services
for Cell
BSC6900
V900R016C00
73428728
VS.ULPSServ.Esta
bDelay.Good.Num.
MultiRAB
Number of Times the

Access Delay of UL
Data Services Falls
in the GOOD Level
for UEs Processing
Combined Services
for Cell
BSC6900
V900R016C00
73428729
VS.ULPSServ.Esta
bDelay.Medium.Nu
m.MultiRAB
Number of Times the

Access Delay of UL
Data Services Falls
in the MEDIUM
Level for UEs
Processing
Combined Services
for Cell
BSC6900
V900R016C00

2344
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428730
VS.ULPSServ.Esta
bDelay.Bad.Num.
MultiRAB
Number of Times the

Access Delay of UL
Data Services Falls
UEs Processing
Combined Services
for Cell
BSC6900
V900R016C00
73428731
VS.DLPSServ.AttE
stab.MultiRAB
Number of DL Data
Service Setup
UEs Processing
Combined Services
for Cell
BSC6900
V900R016C00
73444445
VS.DLPSServ.Esta
bMeanTime.MultiRAB
Average Access
Delay of DL Data
Services
Successfully
Initiated by UEs
Processing
Combined Services
for Cell
BSC6900
V900R016C00
73428734
VS.DLPSServ.Esta
bDelay.Good.Num.
MultiRAB
Number of Times the

Access Delay of DL
Data Services Falls
in the GOOD Level
for UEs Processing
Combined Services
for Cell
BSC6900
V900R016C00
73428736
VS.DLPSServ.Esta
bDelay.Medium.Nu
m.MultiRAB
Number of Times the

Access Delay of DL
Data Services Falls
in the MEDIUM
Level for UEs
Processing
Combined Services
for Cell
BSC6900
V900R016C00
73428735
VS.DLPSServ.Esta
bDelay.Bad.Num.
MultiRAB
Number of Times the

Access Delay of DL
Data Services Falls
UEs Processing
Combined Services
for Cell
BSC6900
V900R016C00

2345
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428737
VS.PS.ULFirstPac
ket.RttDelay.Good.
Num
Number of Times the

RTT of the First UL
TCP Packet Falls in
the Good Level After
UEs Successfully
Initiate UL Data
Services
BSC6900
V900R016C00
73428738
VS.PS.ULFirstPac
ket.RttDelay.Medi
um.Num
Number of Times the

RTT of the First UL
TCP Packet Falls in
the Medium Level
After UEs
Successfully Initiate
UL Data Services
BSC6900
V900R016C00
73428739
VS.PS.ULFirstPac
ket.RttDelay.Bad.N
um
Number of Times the

RTT of the First UL
TCP Packet Falls in
the Bad Level After
UEs Successfully
Initiate UL Data
Services
BSC6900
V900R016C00
73444448
VS.PS.ULfirstPack
et.RttDelay.Mean
Average RTT of the

First UL TCP Packet
After UEs
UL Data Services
BSC6900
V900R016C00
73428743
VS.PS.DLFirstPac
ket.RttDelay.Good.
Num
Number of Times the

RTT of the First DL
TCP Packet Falls in
the Good Level After
UEs Successfully
Initiate DL Data
Services
BSC6900
V900R016C00
73428744
VS.PS.DLFirstPac
ket.RttDelay.Medi
um.Num
Number of Times the

RTT of the First DL
TCP Packet Falls in
the Medium Level
After UEs
DL Data Services
BSC6900
V900R016C00

2346
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428745
VS.PS.DLFirstPac
ket.RttDelay.Bad.N
um
Number of Times the

RTT of the First DL
TCP Packet Falls in
the Bad Level After
UEs Successfully
Initiate DL Data
Services
BSC6900
V900R016C00
73444451
VS.PS.DLfirstPack
et.RttDelay.Mean
Average RTT of the

First DL TCP Packet
After UEs
DL Data Services
BSC6900
V900R016C00
73428799
VS.PS.DLRequest.
OverThd.Throughput.0
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
0 for Cell
BSC6900
V900R016C00
73428800
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
1 for Cell
BSC6900
V900R016C00
73428801
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
2 for Cell
BSC6900
V900R016C00
73428802
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
3 for Cell
BSC6900
V900R016C00
73428803
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
4 for Cell
BSC6900
V900R016C00

2347
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428804
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
5 for Cell
BSC6900
V900R016C00
73428805
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
6 for Cell
BSC6900
V900R016C00
73428806
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
7 for Cell
BSC6900
V900R016C00
73428807
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
8 for Cell
BSC6900
V900R016C00
73428808
VS.PS.DLRequest.
Number of Times the

DL PS Requirement
Exceeds the
Threshold and DL PS
Throughput in Range
9 for Cell
BSC6900
V900R016C00
73445295
VS.PS.DLMeanTh
roughput.TCPTran
sfer.TotalBytes
DL Data Volume of
PS Services Using
TCP Transmission
for Cell
BSC6900
V900R017C00
73445297
VS.PS.DLMeanTh
roughput.TCPTran
sfer
Average DL
Throughput of PS
Services Using TCP
Transmission for
Cell
BSC6900
V900R017C00
73445298
VS.PS.DLMeanTh
roughput.TCPProx
y.TotalBytes
DL Data Volume of
PS Services Using
TCP Proxy for Cell
BSC6900
V900R017C00

2348
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73445300
VS.PS.DLMeanTh
roughput.TCPProx
y
Average DL
Throughput of PS
Services Using TCP
Proxy for Cell
BSC6900
V900R017C00
73445313
VS.PS.DL.TCPPro
xy.RttDelay.Mean
Average DL RTT of
UEs Using the TCP
Proxy for Cell
BSC6900
V900R017C00
73445316
VS.PS.UL.TCPPro
xy.RttDelay.Mean
Average UL RTT of
UEs Using the TCP
Proxy for Cell
BSC6900
V900R017C00
73428433
VS.PS.DLRequest.
OverThd
Number of Times the

DL PS Requirement
Exceeds the
Threshold for Cell
BSC6900
V900R016C00
73430467
VS.PS.DLRequest.
OverThd1
Number of Times the

DL PS Requirement
Exceeds the
Threshold1 for Cell
BSC6900
V900R017C10
73430468
VS.PS.DLRequest.
OverThd2
Number of Times the

DL PS Requirement
Exceeds the
Threshold2 for Cell
BSC6900
V900R017C10
73428434
VS.PS.DLThrough
put.OverThd
Number of Times the

Required DL PS
Throughput Exceeds
the Threshold for
Cell
BSC6900
V900R016C00
73430469
VS.PS.DLThrough
put.OverThd1
Number of Times the

Required DL PS
Throughput Exceeds
the Threshold1 for
Cell
BSC6900
V900R016C00
73430470
VS.PS.DLThrough
put.OverThd2
Number of Times the

Required DL PS
Throughput Exceeds
the Threshold2 for
Cell
BSC6900
V900R016C00
73444359
VS.PS.DLRequest.
OverThd.Traffic
Total Traffic When

the DL PS
Requirement
Exceeds the
Threshold for Cell
BSC6900
V900R016C00

2349
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73446377
VS.PS.DLRequest.
OverThd1.Traffic
Total Traffic When

the DL PS
Requirement
Exceeds the
Threshold1 for Cell
BSC6900
V900R016C00
73446378
VS.PS.DLRequest.
OverThd2.Traffic
Total Traffic When

the DL PS
Requirement
Exceeds the
Threshold2 for Cell
BSC6900
V900R016C00
None
Number of UL Data Service Setup Attempts Initiated by UEs in the Idle State for
Cell
Counters
Counter ID
Counter Name
Counter Description
73428701
VS.ULPSServ.AttEstab.Idle
Number of UL Data Service

Setup Attempts Initiated by
UEs in the Idle State for Cell
Description
This counter provides the number of uplink data service setup attempts initiated by UEs in idle
mode in the best cell.
Measurement point
REQUEST message from a UE, the RNC determines that the message is sent by a UE in idle
mode to initiate uplink data services if either of the following conditions is met: (1) The RRC
CONNECTION REQUEST message contains the cause value "Originating Interactive Call" or
"Originating Background Call." (2) The RRC CONNECTION REQUEST message does not
contain the cause value "Originating Interactive Call" or "Originating Background Call." The
RNC subsequently receives an INITIAL DIRECT TRANSFER message from the UE, the type
of the message is SERVICE REQUEST, and the values of the "CN-domain" and "service-type"
IEs in the message are PS and data, respectively. This counter is measured in the best cell for
the UE when the RNC successfully receives the first uplink data packet or when the access fails.
Issue 03 (2015-06-30)

2350
BSC6900 UMTS
Figure 1-1022 Uplink data service setup procedure for UEs in idle mode
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ULPSServ.AttEstab.Idle
WRFD-010504
WRFD-010503

2351
BSC6900 UMTS
Number of DL Data Service Setup Attempts Initiated by UEs in the Idle State for
Cell
Counters
Counter ID
Counter Name
Counter Description
73428707
Number of DL Data Service

UEs in the Idle State for Cell
Description
This counter provides the number of downlink data service setup attempts initiated by UEs in
idle mode in the best cell.
Measurement point
REQUEST message from a UE, the RNC determines that the message is sent by a UE in idle
mode to initiate downlink data services if either of the following conditions is met: (1) The RRC
CONNECTION REQUEST message contains the cause value "Terminating Interactive Call"
or "Terminating Background Call." (2) The RRC CONNECTION REQUEST message does not
contain the cause value "Terminating Interactive Call" or "Terminating Background Call." The
RNC subsequently receives an INITIAL DIRECT TRANSFER message from the UE, the type
of the message is SERVICE REQUEST, and the values of the "CN-domain" and "service-type"
IEs in the message are PS and paging response, respectively. This counter is measured in the
best cell for the UE when the RNC sends the first downlink data packet or when the access fails.
Issue 03 (2015-06-30)

2352
BSC6900 UMTS
Figure 1-1023 Downlink data service setup procedure for UEs in idle mode
Formula
None
Unit
None
Issue 03 (2015-06-30)

2353
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010504
WRFD-010503
Number of UL Data Service Setup Attempts Initiated by UEs in the CELL_PCH

and URA_PCH States for Cell
Counters
Counter ID
Counter Name
Counter Description
73428713
VS.ULPSServ.AttEstab.PC
H

UEs in the CELL_PCH and
URA_PCH States for Cell
Description
This counter measures the number of uplink data service setup attempts initiated by UEs in the
Measurement point
The measurement is triggered at point A in figure 1. When receiving a CELL UPDATE message
from a UE in the CELL_PCH or URA_PCH state, this counter is measured in the best cell for
the UE when the RNC successfully receives the first uplink data packet or when the access fails
if the following conditions are met: (1) The CELL UPDATE message contains the cause value
"uplink data transmission." (2) The service setup cause is neither "Originating Conversational
Call" nor "Originating Streaming Call."
Issue 03 (2015-06-30)

2354
BSC6900 UMTS
Figure 1-1024 Uplink data service setup procedure for UEs in the CELL_PCH or URA_PCH
state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ULPSServ.AttEstab.PC
H
WRFD-010504
WRFD-010503

2355
BSC6900 UMTS
Number of DL Data Service Setup Attempts Initiated by UEs in the CELL_PCH

and URA_PCH States for Cell
Counters
Counter ID
Counter Name
Counter Description
73428719
VS.DLPSServ.AttEstab.PC
H

Description
This counter measures the number of downlink data service setup attempts initiated by UEs in
the CELL_PCH and URA_PCH states in the best cell.
Measurement point
The measurement is triggered at point A in figure 1. After the core network (CN) sends downlink
data packets to the UE in the CELL_PCH or URA_PCH state, the RNC receives a CELL
UPDATE message from the UE. If the message contains the cause value "paging response" and
if the service setup cause is neither "Terminating Conversational Call" nor "Terminating
Streaming Call", this counter is measured in the best cell for the UE when the RNC successfully
sends the first downlink data packet or when the access fails.
Issue 03 (2015-06-30)

2356
BSC6900 UMTS
Figure 1-1025 Downlink data service setup procedure for UEs in the CELL_PCH or URA_PCH
state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DLPSServ.AttEstab.PC
H
WRFD-010504
WRFD-010503

2357
BSC6900 UMTS
Number of UL Data Service Setup Attempts Initiated by UEs Processing Combined

Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73428725
VS.ULPSServ.AttEstab.Mul
tiRAB

UEs Processing Combined
Services for Cell
Description
This counter measures the number of uplink data service setup attempts initiated by UEs that
are processing combined services in the best cell.
Measurement point
The measurement is triggered at point A in figure 1. When the RNC receives an INITIAL
DIRECT TRANSFER or UPLINK DIRECT TRANSFER message from a UE that already has
one or multiple RABs, this counter is measured in the best cell for the UE when the RNC
successfully receives the first uplink data packet or when the access fails if the following
conditions are met: The type of the message is service request; the values of the "CN-domain"
and "service-type" IEs in the message are PS and data, respectively.
Issue 03 (2015-06-30)

2358
BSC6900 UMTS
Figure 1-1026 Uplink data service setup procedure for UEs processing combined services
Formula
None
Issue 03 (2015-06-30)

2359
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ULPSServ.AttEstab.Mul
tiRAB
WRFD-010504
WRFD-010503
WRFD-010609
Multiple RAB Introduction

Package (PS RAB < 2)
WRFD-01061505
Services
Number of DL Data Service Setup Attempts Initiated by UEs Processing Combined

Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73428731
VS.DLPSServ.AttEstab.Mul
tiRAB

Services for Cell
Description
This counter measures the number of downlink data service setup attempts initiated by UEs that
Measurement point
The measurement is triggered at point A in figure 1. When the RNC receives an INITIAL
DIRECT TRANSFER or UPLINK DIRECT TRANSFER message from a UE that already has
one or multiple RABs, this counter is measured in the best cell for the UE when the RNC
successfully sends the first downlink data packet or when the access fails if the following
conditions are met: (1) The type of the message is service request. (2) The values of the "CNdomain" and "service-type" IEs in the message are PS and paging response, respectively.
Issue 03 (2015-06-30)

2360
BSC6900 UMTS
Figure 1-1027 Downlink data service setup procedure for UEs that are processing combined
services
Issue 03 (2015-06-30)

2361
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DLPSServ.AttEstab.Mul
tiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Number of Times the Access Delay of UL Data Services Falls in Different Levels
for UEs in Idle State for Cell
Counters
Counter ID
Counter Name
Counter Description
73428704
VS.ULPSServ.EstabDelay.
Good.Num.Idle
Number of Times the Access

Delay of UL Data Services
Falls in the GOOD Level for
UEs in Idle State for Cell
73428705
Medium.Num.Idle

Falls in the MEDIUM Level
73428706
Bad.Num.Idle

Falls in the BAD Level for
Description
These counters measure the number of times the access delay of uplink data services falls in
different levels for UEs in idle mode in the best cell.
Issue 03 (2015-06-30)

2362
BSC6900 UMTS

Counter Name
Description
VS.ULPSServ.EstabDelay.Good.Num.Idle

the access delay of uplink data services
initiated by UEs in idle mode is less than or
equal to PSULAccessDelayGoodThd in the
SET USERVPFMPARA command in the
best cell.
VS.ULPSServ.EstabDelay.Medium.Num.Id
le

initiated by UEs in idle mode is greater than
PSULAccessDelayGoodThd and meanwhile
less than or equal to PSULAccessDelayBadThd in the best cell. Both
PSULAccessDelayGoodThd and
PSULAccessDelayBadThd are set in the SET
VS.ULPSServ.EstabDelay.Bad.Num.Idle

PSULAccessDelayBadThd in the SET
USERVPFMPARA command in the best
cell.
Measurement point
When receiving an RRC CONNECTION REQUEST message, as shown by point A in figure
1, the RNC determines that the message is sent by a UE in idle mode to initiate uplink data
services and records the receive time (T1). When receiving the first uplink data packet, as shown
by point B in figure 1, the RNC also records the receive time (T2). The access delay equals T2
minus T1. These counters are measured in the best cell when the RNC receives the first uplink
data packet based on the delay level to which the access delay belongs.
Issue 03 (2015-06-30)

2363
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Good.Num.Idle
WRFD-010504
WRFD-010503

2364
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
Medium.Num.Idle
WRFD-010504
WRFD-010503
Bad.Num.Idle
WRFD-010504
WRFD-010503
for UEs in the CELL_PCH and URA_PCH States for Cell
Counters
Counter ID
Counter Name
Counter Description
73428716
Good.Num.PCH

73428717
Medium.Num.PCH

for UEs in the CELL_PCH
and URA_PCH States for
Cell
73428718
Bad.Num.PCH

Description
different levels for UEs in the CELL_PCH and URA_PCH states in the best cell.
Issue 03 (2015-06-30)

2365
BSC6900 UMTS
Counter Name
Description
VS.ULPSServ.EstabDelay.Good.Num.PCH

initiated by UEs in the CELL_PCH and
URA_PCH states is less than or equal to
PSULAccessDelayGoodThd in the SET
cell.
VS.ULPSServ.EstabDelay.Medium.Num.P
CH

URA_PCH states is greater than
PSULAccessDelayGoodThd and meanwhile
less than or equal to PSULAccessDelayBadThd in the best cell. Both
PSULAccessDelayGoodThd and
PSULAccessDelayBadThd are set in the SET
VS.ULPSServ.EstabDelay.Bad.Num.PCH

PSULAccessDelayBadThd in the SET
cell.
Measurement point
When receiving a CELL UPDATE message, as shown by point A in figure 1, the RNC
determines that the message is sent by a UE in the CELL_PCH or URA_PCH state to initiate
uplink data services and records the receive time (T1). When receiving the first uplink data
packet, as shown by point B in figure 1, the RNC also records the receive time (T2). The access
delay equals T2 minus T1. These counters are measured in the best cell when the RNC receives
the first uplink data packet based on the delay level to which the access delay belongs.
Issue 03 (2015-06-30)

2366
BSC6900 UMTS
state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Good.Num.PCH
WRFD-010504
WRFD-010503
Medium.Num.PCH
WRFD-010504
WRFD-010503
Bad.Num.PCH
WRFD-010504
WRFD-010503

2367
BSC6900 UMTS
for UEs Processing Combined Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73428728
Good.Num.MultiRAB

Services for Cell
73428729
Medium.Num.MultiRAB

for UEs Processing
73428730
Bad.Num.MultiRAB

Services for Cell
Description
different levels for UEs processing combined services in the best cell.
Issue 03 (2015-06-30)
Counter Name
Description
VS.ULPSServ.EstabDelay.Good.Num.MultiRAB

initiated by UEs that are processing combined
services is less than or equal to
PSULAccessDelayGoodThd in the SET
cell.
ultiRAB
ultiRAB

2368
BSC6900 UMTS
Measurement point
When receiving a service request, as shown by point A in figure 1, the RNC determines that the
request is sent by a UE that is processing combined services to initiate uplink data services and
records the receive time (T1). The RNC subsequently successfully receives the first uplink data
packet from the UE and records the receive time (T2). The access delay equals T2 minus T1.
These counters are measured in the best cell when the RNC receives the first uplink data packet
based on the delay level to which the access delay belongs.
Issue 03 (2015-06-30)

2369
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Good.Num.MultiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Medium.Num.MultiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Bad.Num.MultiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Number of Times the Access Delay of DL Data Services Falls in Different Levels
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428710
VS.DLPSServ.EstabDelay.
Good.Num.Idle

Delay of DL Data Services

2370
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428711
Medium.Num.Idle

73428712
Bad.Num.Idle

Description
These counters measure the number of times the access delay of downlink data services falls in
different levels for UEs in idle mode in the best cell.
Counter Name
Description
VS.DLPSServ.EstabDelay.Good.Num.Idle

the access delay of downlink data services
initiated by UEs in idle mode is less than or
equal to PSDLAccessDelayGoodThd in the
best cell.
VS.DLPSServ.EstabDelay.Medium.Num.Id
le

PSDLAccessDelayGoodThd and meanwhile
less than or equal to PSDLAccessDelayBadThd in the best cell. The
PSDLAccessDelayGoodThd is set in the SET
USERVPFMPARA command and
PSDLAccessDelayBadThd is set in the SET
VS.DLPSServ.EstabDelay.Bad.Num.Idle

PSDLAccessDelayBadThd in the SET
cell.
Measurement point
1, the RNC determines that the message is sent by a UE in idle mode to initiate downlink data
Issue 03 (2015-06-30)

2371
BSC6900 UMTS
services and records the receive time (T1). When sending the first downlink data packet, as
shown by point B in figure 1, the RNC records the send time (T2). The access delay equals T2
minus T1. These counters are measured in the best cell when the RNC sends the first downlink
data packet based on the delay level to which the access delay belongs.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2372
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
Good.Num.Idle
WRFD-010504
WRFD-010503
Medium.Num.Idle
WRFD-010504
WRFD-010503
Bad.Num.Idle
WRFD-010504
WRFD-010503
for UEs in the CELL_PCH and URA_PCH States for Cell
Counters
Counter ID
Counter Name
Counter Description
73428722
Good.Num.PCH

73428723
Medium.Num.PCH

for UEs in the CELL_PCH
Cell
73428724
Bad.Num.PCH

Description
different levels for UEs in the CELL_PCH and URA_PCH states in the best cell.
Issue 03 (2015-06-30)

2373
BSC6900 UMTS
Counter Name
Description
VS.DLPSServ.EstabDelay.Good.Num.PCH

URA_PCH states is less than or equal to
PSDLAccessDelayGoodThd in the SET
cell.
VS.DLPSServ.EstabDelay.Medium.Num.P
CH

PSDLAccessDelayGoodThd and meanwhile
less than or equal to PSDLAccessDelayBadThd in the best cell. Both
PSDLAccessDelayGoodThd and
PSDLAccessDelayBadThd are set in the SET
VS.DLPSServ.EstabDelay.Bad.Num.PCH

PSDLAccessDelayBadThd in the SET
cell.
Measurement point
downlink data services and records the receive time (T1). The RNC subsequently successfully
sends the first downlink data packet to the UE, as shown by point B in figure 1, and records the
send time (T2). The access delay equals T2 minus T1. These counters are measured in the best
cell when the RNC sends the first downlink data packet based on the delay level to which the
access delay belongs.
Issue 03 (2015-06-30)

2374
BSC6900 UMTS
state
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Good.Num.PCH
WRFD-010504
WRFD-010503
Medium.Num.PCH
WRFD-010504
WRFD-010503

2375
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
Bad.Num.PCH
WRFD-010504
WRFD-010503
for UEs Processing Combined Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73428734
Good.Num.MultiRAB

Services for Cell
73428736
Medium.Num.MultiRAB

for UEs Processing
73428735
Bad.Num.MultiRAB

Services for Cell
Description
different levels for UEs processing combined services in the best cell.
Issue 03 (2015-06-30)
Counter Name
Description
VS.DLPSServ.EstabDelay.Good.Num.MultiRAB

services is less than or equal to
PSDLAccessDelayGoodThd in the SET
cell.

2376
BSC6900 UMTS
Counter Name
Description
VS.DLPSServ.EstabDelay.Medium.Num.M
ultiRAB

services is greater than PSDLAccessDelayGoodThd and meanwhile less than or equal
to PSDLAccessDelayBadThd in the best cell.
Both PSDLAccessDelayGoodThd and
PSDLAccessDelayBadThd are set in the SET
VS.DLPSServ.EstabDelay.Bad.Num.MultiRAB

services is greater than PSDLAccessDelayBADThd in the SET USERVPFMPARA
command in the best cell.
Measurement point
request is sent by a UE that is processing combined services to initiate downlink data services
and records the receive time (T1). The RNC subsequently successfully sends the first downlink
data packet to the UE, as shown by point B in figure 1, and records the send time (T2). The
access delay equals T2 minus T1. These counters are measured in the best cell when the RNC
sends the first downlink data packet based on the delay level to which the access delay belongs.
Issue 03 (2015-06-30)

2377
BSC6900 UMTS
services
Issue 03 (2015-06-30)

2378
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Good.Num.MultiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Medium.Num.MultiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Bad.Num.MultiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Total DL Traffic for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428536
VS.Video.Total.DLTraffic
Total DL Traffic of Video

Services for Cell
73428538
VS.VoIP.Total.DLTraffic
Total DL Traffic of VoIP

Services for Cell

2379
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428540
VS.Web.Total.DLTraffic
Total DL Traffic of Web

Services for Cell
73428542
VS.P2P.Total.DLTraffic
Total DL Traffic of P2P

Services for Cell
Description
These counters provide the total downlink traffic of the video, VoIP, web, and P2P services at
the PDCP layer in the best cell. These counters exclude the PDCP headers.
Measurement point
The RNC obtains the values of these counters by accumulating the total downlink traffic of
video, VoIP, web, and P2P services at the PDCP layer in the best cell. The service type can be
identified by the service awareness function.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Video.Total.DLTraffic
WRFD-150252
Video Service Rate Adaption
VS.VoIP.Total.DLTraffic
WRFD-150253
VoIP Application
Management
VS.Web.Total.DLTraffic
WRFD-020132
VS.P2P.Total.DLTraffic
WRFD-020133


2380
BSC6900 UMTS
Total DL Transmission Time for Cell

Counters
Counter ID
Counter Name
Counter Description
73428537
VS.Video.Total.DLTransTime
Total DL Transmission Time

of Video Services for Cell
73428539
VS.VoIP.Total.DLTransTime

of VoIP Services for Cell
73428541
VS.Web.Total.DLTransTime

of Web Services for Cell
73428543
VS.P2P.Total.DLTransTime

of P2P Services for Cell
Description
These counters provide the total downlink transmission time of the video, VoIP, web, and P2P
services in the best cell.
Measurement point
The RNC checks the volume of the incoming video, VoIP, web, and P2P traffic at the PDCP
layer every second. If the RNC determines that the downlink traffic volumes of these services
are growing, the RNC increases the values of these counters by one in the best cell. The service
type can be identified by the service awareness function.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.Video.Total.DLTransTime
WRFD-150252
VS.VoIP.Total.DLTransTime
WRFD-150253
VoIP Application
Management
VS.Web.Total.DLTransTime
WRFD-020132

2381
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.P2P.Total.DLTransTime
WRFD-020133

Average Access Delay of UL Data Services Successfully Initiated by UEs in Idle

State for Cell
Counters
Counter ID
Counter Name
Counter Description
73444440
VS.ULPSServ.EstabMeanTi
me.Idle
Average Access Delay of UL

Data Services Successfully
Initiated by UEs in Idle State
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428702
VS.ULPSServ.EstabTime.Id
le.Cum

of UL Data Services
Successfully Initiated by UEs
in Idle State for Cell
73428703
VS.ULPSServ.EstabTime.Id
le.Sample
Accumulated Successful
Idle State to Establish UL
Data Services for Cell
Description
This counter measures the average access delay of uplink data services initiated by UEs in idle
mode in the best cell.
Measurement point
1, the RNC determines that the message is sent by a UE in idle mode to initiate uplink data
services and records the receive time (T1). The RNC subsequently receives the first uplink data
packet, as shown by point B, and records the receive time (T2). The access delay equals T2
minus T1. At the end of the measurement period, the RNC obtains the accumulated access delay
and the number of successful uplink data service setup times for UEs in idle mode. The RNC
Issue 03 (2015-06-30)

2382
BSC6900 UMTS
then calculates the average access delay by dividing the accumulated access delay by the number
of successful times.
Formula
VS.ULPSServ.EstabMeanTime.Idle = [VS.ULPSServ.EstabTime.Idle.Cum]/
[VS.ULPSServ.EstabTime.Idle.Sample]
Unit
ms
Issue 03 (2015-06-30)

2383
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
me.Idle
WRFD-010504
WRFD-010503
Average Access Delay of DL Data Services Successfully Initiated by UEs in Idle

State for Cell
Counters
Counter ID
Counter Name
Counter Description
73444441
VS.DLPSServ.EstabMeanTi
me.Idle
Average Access Delay of DL

Initiated by UEs in Idle State
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73428708
VS.DLPSServ.EstabTime.Id
le.Cum

of DL Data Services
in Idle State for Cell
73428709
VS.DLPSServ.EstabTime.Id
le.Sample
Idle State to Establish DL
Description
This counter measures the average access delay of downlink data services initiated by UEs in
idle mode in the best cell.
Measurement point
1, the RNC determines that the message is sent by a UE in idle mode to initiate downlink data
services and records the receive time (T1). The RNC subsequently sends the first downlink data
packet, as shown by point B, and records the send time (T2). The access delay equals T2 minus
T1. At the end of the measurement period, the RNC obtains the accumulated access delay and
Issue 03 (2015-06-30)

2384
BSC6900 UMTS
the number of successful downlink data service setup times for UEs in idle mode. The RNC then
calculates the average access delay by dividing the accumulated access delay by the number of
successful times.
Formula
VS.DLPSServ.EstabMeanTime.Idle = [VS.DLPSServ.EstabTime.Idle.Cum]/
[VS.DLPSServ.EstabTime.Idle.Sample]
Unit
ms
Issue 03 (2015-06-30)

2385
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
me.Idle
WRFD-010504
WRFD-010503
Average Access Delay of UL Data Services Initiated by UEs in the CELL_PCH and
Counters
Counter ID
Counter Name
Counter Description
73444442
me.PCH

Data Services Initiated by
specific formulas.
Counter ID
Counter Name
Counter Description
73428714
VS.ULPSServ.EstabTime.P
CH.Cum

of UL Data Services Initiated
by UEs in the CELL_PCH
Cell
73428715
VS.ULPSServ.EstabTime.P
CH.Sample
the CELL_PCH and
URA_PCH States to
Establish UL Data Services
for Cell
Description
This counter measures the average access delay of uplink data services initiated by UEs in the
Measurement point
Issue 03 (2015-06-30)

2386
BSC6900 UMTS
uplink data services and records the receive time (T1). The RNC subsequently receives the first
uplink data packet, as shown by point B, and records the receive time (T2). The access delay
equals T2 minus T1. At the end of the measurement period, the RNC obtains the accumulated
access delay and the number of successful uplink data service setup times for UEs in the
CELL_PCH and URA_PCH states. The RNC then calculates the average access delay by
dividing the accumulated access delay by the number of successful times.
state
Formula
VS.ULPSServ.EstabMeanTime.PCH = [VS.ULPSServ.EstabTime.PCH.Cum]/
[VS.ULPSServ.EstabTime.PCH.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
me.PCH
WRFD-010504
WRFD-010503

2387
BSC6900 UMTS
Average Access Delay of DL Data Services Initiated by UEs in the CELL_PCH and
Counters
Counter ID
Counter Name
Counter Description
73444443
me.PCH

Data Services Initiated by
specific formulas.
Counter ID
Counter Name
Counter Description
73428720
VS.DLPSServ.EstabTime.P
CH.Cum

of DL Data Services Initiated
by UEs in the CELL_PCH
Cell
73428721
VS.DLPSServ.EstabTime.P
CH.Sample
the CELL_PCH and
URA_PCH States to
Establish DL Data Services
for Cell
Description
This counter measures the average access delay of downlink data services initiated by UEs in
the CELL_PCH and URA_PCH states in the best cell.
Measurement point
downlink data services and records the receive time (T1). The RNC subsequently sends the first
downlink data packet, as shown by point B, and records the send time (T2). The access delay
equals T2 minus T1. At the end of the measurement period, the RNC obtains the accumulated
access delay and the number of successful downlink data service setup times for UEs in the
CELL_PCH and URA_PCH states. The RNC then calculates the average access delay by
dividing the accumulated access delay by the number of successful times.
Issue 03 (2015-06-30)

2388
BSC6900 UMTS
state
Formula
VS.DLPSServ.EstabMeanTime.PCH = [VS.DLPSServ.EstabTime.PCH.Cum]/
[VS.DLPSServ.EstabTime.PCH.Sample]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
me.PCH
WRFD-010504
WRFD-010503

2389
BSC6900 UMTS
Average Access Delay of UL Data Service Successfully Initiated by UEs Processing

Counters
Counter ID
Counter Name
Counter Description
73444444
me.MultiRAB

Data Service Successfully
Initiated by UEs Processing
specific formulas.
Counter ID
Counter Name
Counter Description
73428726
VS.ULPSServ.EstabTime.M
ultiRAB.Cum

of UL Data Service
Processing Combined
Services for Cell
73428727
VS.ULPSServ.EstabTime.M
ultiRAB.Sample
Attempts Initiated by UEs
Processing Combined
Services to Establish UL
Description
This counter measures the average access delay of uplink data services initiated by UEs that are
processing combined services in the best cell.
Measurement point
request is sent by a UE that is processing combined services to initiate uplink data services and
records the receive time (T1). The RNC subsequently receives the first uplink data packet, as
shown by point B, and records the receive time (T2). The access delay equals T2 minus T1. At
the end of the measurement period, the RNC obtains the accumulated access delay and the
number of successful uplink data service setup times for UEs that are processing combined
services. The RNC then calculates the average access delay by dividing the accumulated access
delay by the number of successful times.
Issue 03 (2015-06-30)

2390
BSC6900 UMTS
Formula
VS.ULPSServ.EstabMeanTime.MultiRAB = [VS.ULPSServ.EstabTime.MultiRAB.Cum]/
[VS.ULPSServ.EstabTime.MultiRAB.Sample]
Issue 03 (2015-06-30)

2391
BSC6900 UMTS
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
me.MultiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Average Access Delay of DL Data Services Successfully Initiated by UEs

Processing Combined Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73444445
me.MultiRAB

Initiated by UEs Processing
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428732
VS.DLPSServ.EstabTime.M
ultiRAB.Cum

of DL Data Services
Processing Combined
Services for Cell
73428733
VS.DLPSServ.EstabTime.M
ultiRAB.Sample
Processing Combined
Services to Establish DL

2392
BSC6900 UMTS
Description
This counter measures the average access delay of downlink data services initiated by UEs that
Measurement point
request is sent by a UE that is processing combined services to initiate downlink data services
and records the receive time (T1). The RNC subsequently sends the first downlink data packet,
as shown by point B, and records the send time (T2). The access delay equals T2 minus T1. At
the end of the measurement period, the RNC obtains the accumulated access delay and the
number of successful downlink data service setup times for UEs that are processing combined
services. The RNC then calculates the average access delay by dividing the accumulated access
delay by the number of successful times.
Issue 03 (2015-06-30)

2393
BSC6900 UMTS
services
Issue 03 (2015-06-30)

2394
BSC6900 UMTS
Formula
VS.DLPSServ.EstabMeanTime.MultiRAB = [VS.DLPSServ.EstabTime.MultiRAB.Cum]/
[VS.DLPSServ.EstabTime.MultiRAB.Sample]
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
me.MultiRAB
WRFD-010504
WRFD-010503
WRFD-010609

WRFD-01061505
Services
Number of Times the RTT of the First UL TCP Packet Falls in Different Levels
After UEs Successfully Initiate UL Data Services
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428737
VS.PS.ULFirstPacket.RttDe
lay.Good.Num
Number of Times the RTT of

the First UL TCP Packet
Falls in the Good Level After
UEs Successfully Initiate UL
Data Services
73428738
lay.Medium.Num

Falls in the Medium Level
After UEs Successfully
Initiate UL Data Services
73428739
lay.Bad.Num

Falls in the Bad Level After
Data Services

2395
BSC6900 UMTS
Description
These counters are measured in the best cell for UEs after UEs successfully initiate uplink data
services.
Counter Name
Description
VS.PS.ULFirstPacket.RttDelay.Good.Num

the round trip time (RTT) of the first TCP
packet is less than or equal to the value of
FirstULTCPRTTGoodThd in the SET
USERVPFMPARA command in the best cell
in the following scenario: The UE has
successfully initiated uplink data services.
VS.PS.ULFirstPacket.RttDelay.Medium.Nu
m

the RTT of the first TCP packet is greater than
the value of FirstULTCPRTTGoodThd and
meanwhile less than or equal to the value of
FirstULTCPRTTBadThd in the best cell in
the following scenario: The UE has
successfully initiated uplink data services.
Both FirstULTCPRTTGoodThd and
FirstULTCPRTTBadThd are set in the SET
VS.PS.ULFirstPacket.RttDelay.Bad.Num

the value of FirstULTCPRTTBadThd in the
best cell in the following scenario: The UE
has successfully initiated uplink data
services.
Measurement point
After the UE initiates uplink data services, the RNC receives the first uplink TCP packet, as
shown by point A in figure 1, and records the receive time (T1). The RNC subsequently receives
the first downlink TCP ACK packet, as shown by point B in figure 1, and records the receive
time (T2). Then the RTT of the first uplink TCP packet equals T2 minus T1. These counters are
measured based on the delay levels to which the RTT of the first uplink TCP packet belongs.
Note:
1. These counters do not apply to the scenario where the data service is not initiated by UEs in
idle mode.
2. When receiving an RRC CONNECTION REQUEST message from a UE, the RNC determines
that the message is sent by a UE in the idle state to initiate uplink data services if the following
condition is met, the RNC subsequently receives an INITIAL DIRECT TRANSFER message
Issue 03 (2015-06-30)

2396
BSC6900 UMTS
from the UE, the type of the message is SERVICE REQUEST, and the values of the "CNdomain" and "service-type" IEs in the message are PS and data, respectively.
Figure 1-1040 The RTT delay of the first uplink TCP packet
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
lay.Good.Num
WRFD-010504
WRFD-010503
lay.Medium.Num
WRFD-010504
WRFD-010503
lay.Bad.Num
WRFD-010504
WRFD-010503

2397
BSC6900 UMTS
Average RTT of the First UL TCP Packet After UEs Successfully Initiate UL Data
Services
Counters
Counter ID
Counter Name
Counter Description
73444448
VS.PS.ULfirstPacket.RttDel
ay.Mean
Average RTT of the First UL

TCP Packet After UEs
Successfully Initiate UL Data
Services
specific formulas.
Counter ID
Counter Name
Counter Description
73444447
ay.Cum
Accumulated RTT of the

First UL TCP Packet After
Data Services
73444446
ay.Sample
Accumulated Sampling
Times of the RTT of the First
UL TCP Packet After UEs
Successfully Initiate UL Data
Services
Description
The average RTT of the first uplink TCP packet is measured in the best cell for UEs after UEs
successfully initiate uplink data services.
Issue 03 (2015-06-30)
Counter Name
Description
VS.PS.ULfirstPacket.RttDelay.Mean
This counter measures the average RTT of the

first uplink TCP packet in the best cell after
the UE successfully initiates uplink data
services.
VS.PS.ULfirstPacket.RttDelay.Cum
This counter measures the accumulated RTT

of the first uplink TCP packet in the best cell
after the UE successfully initiates uplink data
services.

2398
BSC6900 UMTS
Counter Name
Description
VS.PS.ULfirstPacket.RttDelay.Sample

accumulated sampling times of the RTT of
the first uplink TCP packet in the best cell
after the UE successfully initiates uplink data
services.
Measurement point
After the UE initiates uplink data services, the RNC receives the first uplink TCP packet, as
shown by point A in figure 1, and records the receive time (T1). The RNC subsequently receives
the first downlink TCP ACK packet, as shown by point B in figure 1, and records the receive
time (T2). Then the RTT of the first uplink TCP packet equals T2 minus T1. At the end of the
measurement period, the system obtains the average RTT by dividing the accumulated RTT by
the number of sampling times.
Note:
1. These counters do not apply to the scenario where the data service is not initiated by Idle UE.
that the message is sent by a UE in the idle state to initiate uplink data services if the following
from the UE, the type of the message is SERVICE REQUEST, and the values of the "CNdomain" and "service-type" IEs in the message are PS and data, respectively.
Figure 1-1041 The RTT delay of the first uplink Tcp packet
Issue 03 (2015-06-30)

2399
BSC6900 UMTS
Formula
VS.PS.ULfirstPacket.RttDelay.Mean = [VS.PS.ULfirstPacket.RttDelay.Cum]/
[VS.PS.ULfirstPacket.RttDelay.Sample]
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
ay.Mean
WRFD-010504
WRFD-010503
Number of Times the RTT of the First DL TCP Packet Falls in Different Levels
After UEs Successfully Initiate DL Data Services
Counters
Counter ID
Counter Name
Counter Description
73428743
VS.PS.DLFirstPacket.RttDe
lay.Good.Num

the First DL TCP Packet
Falls in the Good Level After
UEs Successfully Initiate DL
Data Services
73428744
lay.Medium.Num

Falls in the Medium Level
After UEs Successfully
Initiate DL Data Services
73428745
lay.Bad.Num

Falls in the Bad Level After
Data Services
Description
These counters are measured in the best cell for UEs after UEs successfully initiate downlink
data services.
Issue 03 (2015-06-30)

2400
BSC6900 UMTS
Counter Name
Description
VS.PS.DLFirstPacket.RttDelay.Good.Num

the round trip time (RTT) of the first TCP
packet is less than or equal to the value of
FirstDLTCPRTTGoodThd in the SET
USERVPFMPARA command in the best cell
in the following scenario: The UE has
successfully initiated downlink data services.
VS.PS.DLFirstPacket.RttDelay.Medium.Nu
m

the value of FirstDLTCPRTTGoodThd and
meanwhile less than or equal to the value of
FirstDLTCPRTTBadThd in the best cell in
the following scenario: The UE has
successfully initiated downlink data services.
Both FirstDLTCPRTTGoodThd and FirstDLTCPRTTBadThd are set in the SET
VS.PS.DLFirstPacket.RttDelay.Bad.Num

the value of FirstDLTCPRTTBadThd in the
best cell in the following scenario: The UE
has successfully initiated downlink data
services.
Measurement point
After the UE initiates downlink data services, the RNC receives the first downlink TCP packet,
as shown by point A in figure 1, and records the receive time (T1). The RNC subsequently
receives the first uplink TCP ACK packet, as shown by point B in figure 1, and records the
receive time (T2). Then the RTT of the first downlink TCP packet equals T2 minus T1. These
counters are measured based on the delay levels to which the RTT of the first downlink TCP
packet belongs.
Note:
idle mode.
that the message is sent by a UE in the idle state to initiate downlink data services if the following
from the UE, the type of the message is SERVICE REQUEST, and the values of the "CNdomain" and "service-type" IEs in the message are PS and paging response, respectively.
Issue 03 (2015-06-30)

2401
BSC6900 UMTS
Figure 1-1042 The RTT delay of the first downlink TCP packet
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
lay.Good.Num
WRFD-010504
WRFD-010503
lay.Medium.Num
WRFD-010504
WRFD-010503
lay.Bad.Num
WRFD-010504
WRFD-010503

2402
BSC6900 UMTS
Average RTT of the First DL TCP Packet After UEs Successfully Initiate DL Data
Services
Counters
Counter ID
Counter Name
Counter Description
73444451
VS.PS.DLfirstPacket.RttDel
ay.Mean
Average RTT of the First DL

TCP Packet After UEs
Successfully Initiate DL Data
Services
specific formulas.
Counter ID
Counter Name
Counter Description
73444450
ay.Cum
Accumulated RTT of the

First DL TCP Packet After
Data Services
73444449
ay.Sample
Accumulated Sampling
Times of the RTT of the First
DL TCP Packet After UEs
Successfully Initiate DL Data
Services
Description
The average RTT of the first downlink TCP packet is measured in the best cell for UEs after
UEs successfully initiate downlink data services.
Issue 03 (2015-06-30)
Counter Name
Description
VS.PS.DLfirstPacket.RttDelay.Mean
This counter measures the average RTT of the

first downlink TCP packet in the best cell
after the UE successfully initiates downlink
data services.
VS.PS.DLfirstPacket.RttDelay.Cum
This counter measures the accumulated RTT

of the first downlink TCP packet in the best
cell after the UE successfully initiates
downlink data services.

2403
BSC6900 UMTS
Counter Name
Description
VS.PS.DLfirstPacket.RttDelay.Sample

accumulated sampling times of the RTT of
the first downlink TCP packet in the best cell
after the UE successfully initiates downlink
data services.
Measurement point
After the UE initiates downlink data services, the RNC receives the first downlink TCP packet,
as shown by point A in figure 1, and records the receive time (T1). The RNC subsequently
receives the first uplink TCP ACK packet, as shown by point B in figure 1, and records the
receive time (T2). Then the RTT of the first downlink TCP packet equals T2 minus T1. At the
end of the measurement period, the system obtains the average RTT by dividing the accumulated
RTT by the number of sampling times.
Note:
idle mode.
that the message is sent by a UE in the idle state to initiate downlink data services if the following
from the UE, the type of the message is SERVICE REQUEST, and the values of the "CNdomain" and "service-type" IEs in the message are PS and paging response, respectively.
Figure 1-1043 The RTT delay of the first downlink TCP packet
Issue 03 (2015-06-30)

2404
BSC6900 UMTS
Formula
VS.PS.DLfirstPacket.RttDelay.Mean = [VS.PS.DLfirstPacket.RttDelay.Cum]/
[VS.PS.DLfirstPacket.RttDelay.Sample]
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
ay.Mean
WRFD-010504
WRFD-010503
Number of Times the DL PS Requirement Exceeds the Threshold and DL PS

Throughput in Each Range for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428799
VS.PS.DLRequest.OverThd.
Throughput.0
Number of Times the DL PS

Requirement Exceeds the
Threshold and DL PS
Throughput in Range 0 for
Cell
73428800
Throughput.1

Threshold and DL PS
Cell
73428801
Throughput.2

Threshold and DL PS
Cell
73428802
Throughput.3

Threshold and DL PS
Cell

2405
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428803
Throughput.4

Threshold and DL PS
Cell
73428804
Throughput.5

Threshold and DL PS
Cell
73428805
Throughput.6

Threshold and DL PS
Cell
73428806
Throughput.7

Threshold and DL PS
Cell
73428807
Throughput.8

Threshold and DL PS
Cell
73428808
Throughput.9

Threshold and DL PS
Cell
Description
These counters measure the number of times the downlink PS throughput falls in a certain range
when the downlink PS service requirement exceeds the throughput threshold
(DLServiceThrouThd) in the best cell.
Issue 03 (2015-06-30)

2406
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Description
VS.PS.DLRequest.OverThd.Throughput.0

the downlink PS throughput falls in range 0
(0, 150] kbit/s when the downlink PS service
requirement exceeds the throughput
threshold (DLServiceThrouThd) in the best
cell.

(150, 250] kbit/s when the downlink PS
service requirement exceeds the throughput
cell.

cell.

cell.

cell.

cell.

cell.

2407
BSC6900 UMTS
Counter Name
Description

cell.

cell.

(greater than or equal to 4000) kbit/s when the
downlink PS service requirement exceeds the
throughput threshold (DLServiceThrouThd)
in the best cell.
Measurement point
The system takes samples of the RLC buffer (buffer 1) and PS traffic (traffic 1) of each downlink
PS service every second if the RLC instance for the PS service is configured to operate in
acknowledged mode (AM). The system then calculates the downlink requirement of the PS
service ((buffer 1 + traffic 1)/1s). If the downlink requirement of a PS service exceeds
DLServiceThrouThd, the system increases the value of the corresponding counter by one based
on the PS throughput. Note that buffer 1 and traffic 1 exclude the RLC header. In addition, traffic
1 excludes the retransmission traffic.Throughput threshold is specified by the command ADD
UCELLCOALGOENHPARA or MOD UCELLCOALGOENHPARA if the command is
configured. In other circumstances, throughput threshold is specified by the SET
UDPUCFGDATA command.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2408
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
Throughput.0
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
Throughput.1
Throughput.2
Throughput.3
Throughput.4
Throughput.5
Throughput.6
Throughput.7
Throughput.8
Throughput.9
Issue 03 (2015-06-30)

2409
BSC6900 UMTS
DL Data Volume of PS Services Using TCP Transmission for Cell

Counters
Counter ID
Counter Name
Counter Description
73445295
VS.PS.DLMeanThroughput.
TCPTransfer.TotalBytes
DL Data Volume of PS
Services Using TCP
Description
This counter provides the amount of downlink PS data that uses TCP transmission in the best
cell.
Measurement point
When a UE initiates a PS service and the PS services uses TCP transmission, the data volume
of the PS service is measured at the RLC layer in the downlink. The total data volume of the PS
service is obtained when the TCP data transmission is complete. In addition, the measured data
volume excludes RLC headers and retransmitted data.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
TCPTransfer.TotalBytes
WRFD-170202
TCP Proxy
Average DL Throughput of PS Services Using TCP Transmission for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73445297
TCPTransfer
Average DL Throughput of
PS Services Using TCP

2410
BSC6900 UMTS
specific formulas.
Counter ID
Counter Name
Counter Description
73445296
TCPTransfer.Times

of the PS Services Using TCP
Description
This counter provides the average downlink throughput of the PS services that use TCP
transmission in the best cell.
Measurement point
When a UE initiates a PS service and the PS service uses the TCP transmission, the total TCP
transmission time of the PS service and the number of bits transmitted at the RLC layer are
measured in the best cell. At the end of the measurement period, the value of this counter is
obtained by dividing the total number of bits by the total data transmission time.
Formula
VS.PS.DLMeanThroughput.TCPTransfer =
[VS.PS.DLMeanThroughput.TCPTransfer.TotalBytes]*{8}/
[VS.PS.DLMeanThroughput.TCPTransfer.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
TCPTransfer
WRFD-170202
TCP Proxy
DL Data Volume of PS Services Using TCP Proxy for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73445298
TCPProxy.TotalBytes
DL Data Volume of PS
Services Using TCP Proxy
for Cell

2411
BSC6900 UMTS
Description
This counter provides the downlink data volume of the PS services that use TCP proxy in the
best cell.
Measurement point
If a PS service uses TCP transmission after the three-way handshake is successful and the PS
service also uses TCP proxy, the data volume of the PS service is measured at the RLC layer.
The total data volume is obtained when the PS service stops using the TCP proxy. The measured
value of this counter excludes the RLC headers and retransmitted data.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
TCPProxy.TotalBytes
WRFD-170202
TCP Proxy
Average DL Throughput of PS Services Using TCP Proxy for Cell

Counters
Counter ID
Counter Name
Counter Description
73445300
TCPProxy
PS Services Using TCP
Proxy for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73445299
TCPProxy.Times

of PS Services Using TCP
Proxy for Cell

2412
BSC6900 UMTS
Description
Average DL Throughput of PS Services Using TCP Proxy for Cell.
Measurement point
This counter measures the average downlink throughput of the PS services that use TCP
transmission after the three-way handshake is successful and that use the TCP proxy. The total
TCP transmission time of such PS services and the number of bits transmitted at the RLC layer
are measured in the best cell. At the end of the measurement period, the value of this counter is
obtained by dividing the total number of bits by the total data transmission time.
Formula
VS.PS.DLMeanThroughput.TCPProxy =
[VS.PS.DLMeanThroughput.TCPProxy.TotalBytes]*{8}/
[VS.PS.DLMeanThroughput.TCPProxy.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
TCPProxy
WRFD-170202
TCP Proxy
Average DL RTT of UEs Using the TCP Proxy for Cell

Counters
Counter ID
Counter Name
Counter Description
73445313
VS.PS.DL.TCPProxy.RttDe
lay.Mean
Average DL RTT of UEs

Using the TCP Proxy for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73445312
lay.Sample
Number of Times DL RTT Is

Correctly Measured for UEs

2413
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73445311
lay.Sum
Accumulated DL RTT of
UEs Using the TCP Proxy for
Cell
Description
This counter provides the average downlink RTT of UEs using the TCP proxy in the best cell.
Measurement point
The RNC receives a downlink TCP data packet that is sent to a UE using the TCP proxy at point
A in figure 1 and records the receive time (T1). The RNC subsequently receives an uplink TCP
ACK packet from the UE as a response to the previous downlink TCP data packet at point B
and records the receive time (T2). The RTT of this downlink TCP data packet equals T2 minus
T1. At the end of the measurement period, the RNC obtains the value of this counter by dividing
the accumulated RTT by the number of times the downlink RTT is sampled.
Figure 1-1044 Downlink RTT of TCP Packets
Formula
VS.PS.DL.TCPProxy.RttDelay.Mean = [VS.PS.DL.TCPProxy.RttDelay.Sum]/
[VS.PS.DL.TCPProxy.RttDelay.Sample]
Issue 03 (2015-06-30)

2414
BSC6900 UMTS
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
lay.Mean
WRFD-170202
TCP Proxy
Average UL RTT of UEs Using the TCP Proxy for Cell

Counters
Counter ID
Counter Name
Counter Description
73445316
VS.PS.UL.TCPProxy.RttDe
lay.Mean
Average UL RTT of UEs

specific formulas.
Counter ID
Counter Name
Counter Description
73445315
lay.Sample
Number of Times UL RTT Is

Correctly Measured for UEs
73445314
lay.Sum
Accumulated UL RTT of
UEs Using the TCP Proxy for
Cell
Description
This counter provides the average uplink RTT of UEs using the TCP proxy in the best cell.
Measurement point
The RNC receives an uplink TCP data packet to a UE using the TCP proxy at point A in figure
1 and records the receive time (T1). The RNC subsequently receives a downlink TCP ACK
packet from the UE as a response to the previous downlink TCP data packet at point B and
records the receive time (T2). The RTT of this uplink TCP data packet equals T2 minus T1. At
the end of the measurement period, the RNC obtains the value of this counter by dividing the
accumulated RTT by the number of times the uplink RTT is sampled.
Issue 03 (2015-06-30)

2415
BSC6900 UMTS
Figure 1-1045 Uplink RTT of TCP Packets
Formula
VS.PS.UL.TCPProxy.RttDelay.Mean = [VS.PS.UL.TCPProxy.RttDelay.Sum]/
[VS.PS.UL.TCPProxy.RttDelay.Sample]
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
lay.Mean
WRFD-170202
TCP Proxy
Number of Times the DL PS Requirement Exceeds different Thresholds for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428433
VS.PS.DLRequest.OverThd

Threshold for Cell

2416
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73430467
1

Threshold1 for Cell
73430468
2

Threshold2 for Cell
Description
These counters measure the number of times the downlink PS service requirement exceeds the
throughput threshold in the best cell.
Counter Name
Description

the downlink PS service requirement exceeds
the throughput threshold (DLServiceThrouThd) in the best cell.
VS.PS.DLRequest.OverThd1

the throughput threshold (DLServiceThrouThd1) in the best cell.
VS.PS.DLRequest.OverThd2

Measurement point
service ((buffer 1 + traffic 1)/1s). If the downlink requirement of a PS service exceeds the
throughput threshold, the counter is incremented by one. Note that buffer 1 and traffic 1 exclude
the RLC header. In addition, traffic 1 excludes the retransmission traffic.Throughput threshold
is specified by the command ADD UCELLCOALGOENHPARA or MOD
UCELLCOALGOENHPARA if the command is configured. In other circumstances, throughput
threshold is specified by the SET UDPUCFGDATA command.
Formula
None
Issue 03 (2015-06-30)

2417
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
1
2
Number of Times the Required DL PS Throughput Exceeds different Thresholds

for Cell
Counters
Counter ID
Counter Name
Counter Description
73428434
VS.PS.DLThroughput.Over
Thd
Number of Times the

Required DL PS Throughput
Exceeds the Threshold for
Cell
73430469
Thd1
Number of Times the

Exceeds the Threshold1 for
Cell
73430470
Thd2
Number of Times the

Exceeds the Threshold2 for
Cell
Description
These counters measure the number of times the downlink PS throughput exceeds the throughput
threshold in the best cell.
Issue 03 (2015-06-30)

2418
BSC6900 UMTS
Counter Name
Description
VS.PS.DLThroughput.OverThd

the downlink PS throughput exceeds the
throughput threshold (DLServiceThrouThd)
in the best cell.
VS.PS.DLThroughput.OverThd1

throughput threshold (DLServiceThrouThd1) in the best cell.
VS.PS.DLThroughput.OverThd2

throughput threshold (DLServiceThrouThd2) in the best cell.
Measurement point
The system takes samples of the downlink throughput of each PS service (traffic 1/1s) every
second if the RLC instance for the PS service is configured to operate in acknowledged mode
(AM). If the downlink throughput of a PS service exceeds the throughput threshold, the counter
is incremented by one. Note that traffic 1 excludes the RLC header and the retransmission
traffic.Throughput threshold is specified by the command ADD UCELLCOALGOENHPARA
or MOD UCELLCOALGOENHPARA if the command is configured. In other circumstances,
throughput threshold is specified by the SET UDPUCFGDATA command.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Thd
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
Thd1
Issue 03 (2015-06-30)

2419
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
Thd2
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
Total Traffic When the DL PS Requirement Exceeds different Thresholds for Cell
Counters
Counter ID
Counter Name
Counter Description
73444359
Traffic
Total Traffic When the DL

PS Requirement Exceeds the
Threshold for Cell
73446377
1.Traffic

Threshold1 for Cell
73446378
2.Traffic

Threshold2 for Cell
Description
These counters measure the total traffic when the downlink PS service requirement exceeds the
throughput threshold in the best cell.
Issue 03 (2015-06-30)
Counter Name
Description
VS.PS.DLRequest.OverThd.Traffic
This counter measures the total traffic when

the throughput threshold (DLServiceThrouThd) in the best cell.
VS.PS.DLRequest.OverThd1.Traffic

VS.PS.DLRequest.OverThd2.Traffic


2420
BSC6900 UMTS
Measurement point
service ((buffer 1 + traffic 1)/1s). If the downlink requirement of a PS service exceeds the
throughput threshold, the system calculates the total traffic by accumulating the values of traffic
1. Note that buffer 1 and traffic 1 exclude the RLC header. In addition, traffic 1 excludes the
retransmission traffic.Throughput threshold is specified by the ADD
UCELLCOALGOENHPARA or MOD UCELLCOALGOENHPARA command if the
command is configured. In other circumstances, throughput threshold is specified by the SET
UDPUCFGDATA command.
Formula
None
Unit
kbit
Related Features
Counter Name
Feature ID
Feature Name
Traffic
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
WRFD-010504
WRFD-010503
WRFD-010502
Streaming QoS Class
1.Traffic
2.Traffic
1.12.28 PTT Measurement <per Cell>(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.
Issue 03 (2015-06-30)

2421
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423555
VS.PTT.PCH.Singl
eRAB.CallReq.Suc
c
Number of
Successful PTT Call
Initiation Attempts
or Responses of UEs
Using Only the PTT
Service in the
CELL_PCH or
URA_PCH State
During the State
Transition from
CELL_PCH/
URA_PCH to
CELL_DCH for Cell
BSC6900
V900R013
73423556
VS.PTT.FACH.Sin
gleRAB.CallReq.At
t
Number of PTT Call

Initiation or
Response Attempts
of UEs Using Only
the PTT Service in
the CELL_FACH
State for Cell
BSC6900
V900R013
73423557
VS.PTT.FACH.Sin
gleRAB.CallReq.S
ucc
Number of
Successful PTT Call
Initiation Attempts
or Responses of UEs
Using Only the PTT
Service in the
CELL_FACH State
for Cell
BSC6900
V900R013
73423558
VS.PTT.FACH.Mu
ltRAB.CallReq.Suc
c
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
V900R013
73423559
VS.PTT.NormalRe
l
Number of Complete
PTT Calls for Cell
BSC6900
V900R013
73423560
VS.PTT.RAB.Abno
rmRel.DCH
Number of RABs
Abnormally
Released During
PTT Calls for Cell
BSC6900
V900R013

2422
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423561
VS.PTT.SuccP2D.F
irst
Number of
Successful State
Transitions from
CELL_PCH/
URA_PCH to
CELL_DCH After
the RNC Sends a
CELL UPDATE
CONFIRM Message
for Cell
BSC6900
V900R013
73423562
VS.PTT.SuccP2D.S
econd
Number of
Successful State
Transitions from
CELL_PCH/
URA_PCH to
CELL_DCH After
the RNC Sends Two
CELL UPDATE
CONFIRM
Messages for Cell
BSC6900
V900R013
73423563
VS.PTT.SuccP2D.
Third
Number of
Successful State
Transitions from
CELL_PCH/
URA_PCH to
CELL_DCH After
the RNC Sends
Three CELL
UPDATE
CONFIRM
Messages for Cell
BSC6900
V900R013
73423564
VS.PTT.SuccPagin
g.First
Number of
Successful PTT
Paging Attempts
After the RNC Sends
a PAGING TYPE 1
Message for Cell
BSC6900
V900R013
73423565
VS.PTT.SuccPagin
g.Second
Number of
Successful PTT
Paging Attempts
After the RNC Sends
Two PAGING TYPE
1 Messages for Cell
BSC6900
V900R013

2423
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423566
VS.PTT.SuccPagin
g.Third
Number of
Successful PTT
Paging Attempts
After the RNC Sends
Three PAGING
TYPE 1 Messages
for Cell
BSC6900
V900R013
73423609
VS.PTT.FACH.Mu
ltRAB.CallReq.Att
Number of PTT Call

Initiation or
Responses Attempts
of UEs Using the
PTT and Other
Services in the
CELL_FACH State
for Cell
BSC6900
V900R013
73423610
VS.PTT.PCH.Singl
eRAB.CallReq.Fail
.Cong
Number of Failed
PTT Call Initiation
Attempts or
Responses of a UE in
the CELL_PCH or
URA_PCH State
Processing Only the
PTT Service During
P2D Due to
Congestion for Cell
BSC6900
V900R013
73423611
VS.PTT.FACH.Sin
gleRAB.CallReq.F
ail.Cong
Number of Failed
PTT Call Initiation
Attempts or
the CELL_FACH
State Processing
Only the PTT
Service Due to
Congestion for Cell
BSC6900
V900R013
73423612
VS.PTT.FACH.Mu
ltRAB.CallReq.Fail
.Cong
Number of Failed
PTT Call Initiation
Attempts or
the CELL_FACH
State Processing
Multiple Services
Due to Congestion
for Cell
BSC6900
V900R013

2424
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73423619
VS.PTT.PCH.Singl
eRAB.CallReq.Att
Number of PTT Call

Initiation or
Response Attempts
of UEs Using Only
the PTT Service in
the CELL_PCH
State for Cell
BSC6900
V900R013
73441168
VS.PTT.UL.Traffic
Uplink Traffic
Volume of the PTT
Service
BSC6900
V900R013
73441169
VS.PTT.DL.Traffic
Downlink Traffic
Volume of the PTT
Service
BSC6900
V900R013
73424828
VS.PTT.SHO.Serv
CellChg.SuccOut
Number of
Successful Serving
Cell Changes of PTT
Service in Soft
Handover Status for
Cell
BSC6900
V900R014
73424829
VS.PTT.SHO.Serv
CellChg.AttOut
Number of Serving
Cell Change
Attempts of PTT
Service in Soft
Handover Status for
Cell
BSC6900
V900R014
73424830
VS.PTT.HHO.SuccOut
Number of
Successful Hard
Handovers of PTT
Service for Cell
BSC6900
V900R014
73424831
VS.PTT.HHO.AttOut
Number of Hard
Handover Attempts
of PTT Service for
Cell
BSC6900
V900R014
None
Issue 03 (2015-06-30)

2425
BSC6900 UMTS
Number of Successful PTT Call Initiation Attempts or Responses During a P2D

Procedure for UEs Processing PTT Services
Counters
Counter ID
Counter Name
Counter Description
73423555
VS.PTT.PCH.SingleRAB.C
allReq.Succ
Number of Successful PTT

Call Initiation Attempts or
Responses of UEs Using
Only the PTT Service in the
CELL_PCH or URA_PCH
State During the State
Transition from
CELL_PCH/URA_PCH to
CELL_DCH for Cell
Description
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.This counter complies with section
"8.3.1 Cell and URA update procedures" in 3GPP TS 25.331(v10.13.0).
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.
Issue 03 (2015-06-30)

2426
BSC6900 UMTS
Figure 1-1046 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."
Issue 03 (2015-06-30)

2427
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
allReq.Succ
WRFD-020134
Push to Talk

2428
BSC6900 UMTS
Number of PTT Call Initiation or Response Attempts of UEs Using Only the PTT
Service in the CELL_FACH State for Cell
Counters
Counter ID
Counter Name
Counter Description
73423556
VS.PTT.FACH.SingleRAB.
CallReq.Att
Number of PTT Call

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.This
counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered at point A as shown in Figure 1, when a UE processing only the
PTT service in the CELL_FACH state transfers to CELL_DCH state triggered by an event 4A
measurement report.
Issue 03 (2015-06-30)

2429
BSC6900 UMTS
Figure 1-1048 PTT call normal procedure(F2D)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
CallReq.Att
WRFD-020134
Push to Talk

2430
BSC6900 UMTS
Number of Successful PTT Call Initiation Attempts or Responses of UEs Using

Only the PTT Service in the CELL_FACH State for Cell
Counters
Counter ID
Counter Name
Counter Description
73423557
CallReq.Succ

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.This counter
complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331(v10.13.0).
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.
Issue 03 (2015-06-30)

2431
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
CallReq.Succ
WRFD-020134
Push to Talk

2432
BSC6900 UMTS
Number of Successful PTT Call Initiation Attempts or Responses of UEs Using the
PTT and Other Services in the CELL_FACH State for Cell
Counters
Counter ID
Counter Name
Counter Description
73423558
VS.PTT.FACH.MultRAB.C
allReq.Succ

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.This counter
Measurement point
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.
Issue 03 (2015-06-30)

2433
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
allReq.Succ
WRFD-020134
Push to Talk

2434
BSC6900 UMTS
Number of Complete PTT Calls for Cell

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies
with section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331(v10.13.0).
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.
Issue 03 (2015-06-30)

2435
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.PTT.NormalRel
WRFD-020134
Push to Talk
Number of RABs Abnormally Released During PTT Calls for Cell

Counters
Counter ID
Counter Name
Counter Description
73423560
VS.PTT.RAB.AbnormRel.D
CH
Number of RABs
Abnormally Released
During PTT Calls for Cell
Description
This counter provides the number of times that RABs are abnormally released after a UE state
transition to CELL_DCH due to PTT data transmission, which indicates the number of PTT call
drops.
This counter is measured on a per cell basis. The counter is used with the VS.PTT.NormalRel
counter to access the PTT call drop rate.This counter complies with section "8.2.2
Reconfiguration procedures" in 3GPP TS 25.331(v10.13.0).
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.
Issue 03 (2015-06-30)

2436
BSC6900 UMTS
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.
Issue 03 (2015-06-30)

2437
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
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PTT.RAB.AbnormRel.D
CH
WRFD-020134
Push to Talk

2438
BSC6900 UMTS
Number of Successful State Transitions from CELL_PCH/URA_PCH to

CELL_DCH After the RNC Sends the CELL UPDATE CONFIRM Message for Cell
Counters
Counter ID
Counter Name
Counter Description
73423561
VS.PTT.SuccP2D.First

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

Transitions from
CELL_PCH/URA_PCH to
Sends Two CELL UPDATE
CONFIRM Messages for
Cell
73423563
VS.PTT.SuccP2D.Third

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
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.The preceding counters complies with section
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
Issue 03 (2015-06-30)

2439
BSC6900 UMTS
after the RNC sends the UE a first CELL UPDATE CONFIRM message, the counter is measured
Figure 1-1055 VS.PTT.SuccP2D.First
The VS.PTT.SuccP2D.Second counter is measured at point B as shown in Figure 2. During the

UE state transition from CELL_PCH or URA_PCH to CELL_DCH triggered by a PTT call, if
the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE
message after the RNC sends the UE a second CELL UPDATE CONFIRM message, the counter
is measured in the cell that the UE camps on.
Issue 03 (2015-06-30)

2440
BSC6900 UMTS
Figure 1-1056 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
Issue 03 (2015-06-30)

2441
BSC6900 UMTS
Figure 1-1057 VS.PTT.SuccP2D.Third
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
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

2442
BSC6900 UMTS
Number of Successful PTT Paging Attempts After the RNC Sends the PAGING
TYPE 1 Message for Cell
Counters
Counter ID
Counter Name
Counter Description
73423564
VS.PTT.SuccPaging.First

Paging Attempts After the
RNC Sends a PAGING
TYPE 1 Message for Cell
73423565
VS.PTT.SuccPaging.Second

RNC Sends Two PAGING
TYPE 1 Messages for Cell
73423566
VS.PTT.SuccPaging.Third

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.The preceding counters complies with section "8.1.2 Paging" in
3GPP TS 25.331(v10.13.0).
Measurement point
The measurement is triggered at point A as shown in Figure 1. When the RNC detects downlink
PTT data transmission, it sends the UE a first PAGING TYPE 1 message. When the RNC
receives a CELL UPDATE message that carries the "Cell update cause" IE with the value of
"paging response", the VS.PTT.SuccPaging.First counter is measured in the cell that the UE
camps on.
Issue 03 (2015-06-30)

2443
BSC6900 UMTS
Figure 1-1058 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.
Issue 03 (2015-06-30)

2444
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
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

2445
BSC6900 UMTS
Number of PTT Call Initiation or Response Attempts of UEs Using the PTT and
Other Services in the CELL_FACH State for Cell
Counters
Counter ID
Counter Name
Counter Description
73423609
allReq.Att
Number of PTT Call

Initiation or Responses
Attempts of UEs Using the
PTT and Other Services in
the CELL_FACH State for
Cell
Description
This counter provides the number of UE state transition attempts from the CELL_FACH to
CELL_DCH that is triggered by PTT data transmission of a UE processing PTT and other
services, which indicates the number of initiation or response attempts of a UE in the
CELL_FACH state. This counter is measured on a per cell basis. The counter is used with the
VS.PTT.FACH.MultRAB.CallReq.Succ counter to assess the success rate of PTT call initiations
or responses of a UE processing PTT and other services in the CELL_FACH state.This counter
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.
Issue 03 (2015-06-30)

2446
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
allReq.Att
WRFD-020134
Push to Talk

2447
BSC6900 UMTS
Number of Failed PTT Call Initiations or Responses Due to Resource Congestion

During a P2D Procedure for UEs Processing PTT Services
Counters
Counter ID
Counter Name
Counter Description
73423610
allReq.Fail.Cong
Number of Failed PTT Call

Initiation Attempts or
Responses of a UE in the
CELL_PCH or URA_PCH
State Processing Only the
PTT Service During P2D
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.This counter complies with section "8.3.1 Cell and URA update
procedures" in 3GPP TS 25.331(v10.13.0).
Measurement point
The measurement is triggered at point A as shown in Figure 1. If the UE transfers from the
CELL_PCH or URA_PCH state to the CELL_DCH state to initiate a PTT call, when the UE
access fails, the counter is measured in the cell that the UE camps on.
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.
Issue 03 (2015-06-30)

2448
BSC6900 UMTS
Figure 1-1062 VS.PTT.PCH.SingleRAB.CallReq.Fail.Cong
The measurement is triggered at point A as shown in Figure 2. If the UE transfers from the
CELL_PCH or URA_PCH state to the CELL_DCH state to respond a PTT call, when the UE
access fails, the counter is measured in the cell that the UE camps on.
Issue 03 (2015-06-30)

2449
BSC6900 UMTS
Figure 1-1063 VS.PTT.PCH.SingleRAB.CallReq.Fail.Cong
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
allReq.Fail.Cong
WRFD-020134
Push to Talk

2450
BSC6900 UMTS
Number of Failed PTT Call Initiation Attempts or Responses of a UE in the

CELL_FACH State Processing Only the PTT Service Due to Congestion for Cell
Counters
Counter ID
Counter Name
Counter Description
73423611
CallReq.Fail.Cong

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.
or capacity expansion.This counter complies with section "8.2.2 Reconfiguration procedures"
in 3GPP TS 25.331(v10.13.0).
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
CallReq.Fail.Cong
WRFD-020134
Push to Talk

2451
BSC6900 UMTS
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
Counters
Counter ID
Counter Name
Counter Description
73423612
allReq.Fail.Cong

CELL_FACH State
Processing Multiple Services
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.
or capacity expansion.This counter complies with section "8.2.2 Reconfiguration procedures"
in 3GPP TS 25.331(v10.13.0).
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
allReq.Fail.Cong
WRFD-020134
Push to Talk

2452
BSC6900 UMTS
Number of PTT Call Initiation Attempts or Responses During a P2D Procedure for
UEs Processing PTT Services
Counters
Counter ID
Counter Name
Counter Description
73423619
allReq.Att
Number of PTT Call

Initiation or Response
Attempts of UEs Using Only
the PTT Service in the
CELL_PCH State for Cell
Description
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.This counter complies with section
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.
Issue 03 (2015-06-30)

2453
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.
Issue 03 (2015-06-30)

2454
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
allReq.Att
WRFD-020134
Push to Talk

2455
BSC6900 UMTS
Uplink Traffic Volume of the PTT Service

Counters
Counter ID
Counter Name
Counter Description
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
Counter Name
Feature ID
Feature Name
VS.PTT.UL.Traffic
WRFD-020134
Push to Talk
Downlink Traffic Volume of the PTT Service

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441169
VS.PTT.DL.Traffic
Downlink Traffic Volume of

the PTT Service

2456
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
Counter Name
Feature ID
Feature Name
VS.PTT.DL.Traffic
WRFD-020134
Push to Talk
Number of Successful Serving Cell Changes of PTT Service in Soft Handover

Status
Counters
Counter ID
Counter Name
Counter Description
73424828
VS.PTT.SHO.ServCellChg.
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.This counter comply with section "8.3.4 Active set update" in 3GPP TS 25.331
(v10.13.0).
Issue 03 (2015-06-30)

2457
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-1066 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.
Issue 03 (2015-06-30)

2458
BSC6900 UMTS
Figure 1-1067 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 (intraor inter-RNC) change.
Figure 1-1068 Radio Bearer Reconfiguration Procedure
Issue 03 (2015-06-30)

2459
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-1069 Active Set Update Procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
SuccOut
WRFD-020134
Push to Talk

2460
BSC6900 UMTS
Number of Serving Cell Change Attempts of PTT Service in Soft Handover Status
Counters
Counter ID
Counter Name
Counter Description
73424829
AttOut
Number of Serving Cell

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 interRNC) change.
Figure 1-1070 Physical Channel Reconfiguration Procedure
services and is performing a soft handover. The RNC sends the UE a TRANSPORT CHANNEL
Issue 03 (2015-06-30)

2461
BSC6900 UMTS
services and is performing a soft handover. The RNC sends the UE a RADIO BEARER
Figure 1-1072 Radio Bearer Reconfiguration Procedure
Issue 03 (2015-06-30)

2462
BSC6900 UMTS
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-1073 Active Set Update Procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
AttOut
WRFD-020134
Push to Talk
Number of Successful Hard Handovers of PTT Service

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424830
VS.PTT.HHO.SuccOut
Number of Successful Hard

Handovers of PTT Service
for Cell

2463
BSC6900 UMTS
Description
This counter provides the number of successful hard handovers of a PTT UE, including intrafrequency, inter-frequency, intra-RNC, and inter-RNC hard handovers.
This counter is measured on a per cell basis. The counter is used with the VS.PTT.HHO.AttOut
counter to assess the success rate of hard handovers of a PTT UE.This counter comply with
section "8.3.5 Hard handover" in 3GPP TS 25.331 (v10.13.0).
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).
Figure 1-1074 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).
Issue 03 (2015-06-30)

2464
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 interRNC hard handovers).
Issue 03 (2015-06-30)

2465
BSC6900 UMTS
PTT services. The RNC receives from the UE a RADIO BEARER SETUP COMPLETE
message in responding to the RADIO BEARER SETUP message sent from the RNC. The RNC
sends the UE a RADIO BEARER SETUP message to initiate a hard handover (including intraand inter-frequency and intra- and inter-RNC hard handovers).
Figure 1-1077 Radio Bearer Setup procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PTT.HHO.SuccOut
WRFD-020134
Push to Talk

2466
BSC6900 UMTS
Number of Hard Handover Attempts of PTT Service

Counters
Counter ID
Counter Name
Counter Description
73424831
VS.PTT.HHO.AttOut
Number of Hard Handover

Attempts of PTT Service for
Cell
Description
This counter provides the number of hard handover attempts of a PTT UE, including intra- and
inter-frequency and intra- and inter-RNC hard handovers.
This counter is measured on a per cell basis. The counter is used with the VS.PTT.HHO.SuccOut
counter to assess the success rate of hard handovers of a PTT UE.This counter comply with
section "8.3.5 Hard handover" in 3GPP TS 25.331 (v10.13.0).
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).
Issue 03 (2015-06-30)

2467
BSC6900 UMTS
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).
PTT services. The RNC receives from the UE a RADIO BEARER RECONFIGURATION
message to initiate a hard handover (including intra- and inter-frequency and intra- and interRNC hard handovers).
Issue 03 (2015-06-30)

2468
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-1081 Radio Bearer Setup procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.PTT.HHO.AttOut
WRFD-020134
Push to Talk
1.12.29 QoS Measurement <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
Issue 03 (2015-06-30)

2469
BSC6900 UMTS
domains.3)Mean throughput count by user class and HSDPA download throughput.4)Mean

throughput count by user class and HSUPA upload throughput.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195972
VS.AMR.Estab.Ma
xTime
Maximum Delay
Between RRC
Connection
Establishment and
AMR RAB
Establishment
Completion for Cell
BSC6900
V900R012
67204785
VS.AMR.Estab.Me
anTime
Mean Delay
Between RRC
Connection
Establishment and
AMR RAB
Establishment
Completion for Cell
BSC6900
V900R012
67195973
VS.AMR.Estab.Mi
nTime
Minimum Delay
Between RRC
Connection
Establishment and
AMR RAB
Establishment
Completion for Cell
BSC6900
V900R012
67195976
VS.CS64.Estab.Ma
xTime
Maximum Delay
Between RRC
Connection
Establishment and
64kbit/s CS RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67204786
VS.CS64.Estab.Me
anTime
Mean Delay
Between RRC
Connection
Establishment and
64kbit/s CS RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011

2470
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195977
VS.CS64.Estab.Mi
nTime
Minimum Delay
Between RRC
Connection
Establishment and
64kbit/s CS RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67195980
VS.PSR99.Estab.M
axTime
Maximum Delay
Between RRC
Connection
Establishment and
PS R99 RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67204787
VS.PSR99.Estab.M
eanTime
Mean Delay
Between RRC
Connection
Establishment and
PS R99 RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67195981
VS.PSR99.Estab.M
inTime
Minimum Delay
Between RRC
Connection
Establishment and
PS R99 RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67195984
VS.HSDPA.Estab.
MaxTime
Maximum Delay
Between RRC
Connection
Establishment and
HSDPA RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67204788
VS.HSDPA.Estab.
MeanTime
Mean Delay
Between RRC
Connection
Establishment and
HSDPA RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011

2471
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195985
VS.HSDPA.Estab.
MinTime
Minimum Delay
Between RRC
Connection
Establishment and
HSDPA RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67195988
VS.HSUPA.Estab.
MaxTime
Maximum Delay
Between RRC
Connection
Establishment and
HSUPA RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67204789
VS.HSUPA.Estab.
MeanTime
Mean Delay
Between RRC
Connection
Establishment and
HSUPA RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67195989
VS.HSUPA.Estab.
MinTime
Minimum Delay
Between RRC
Connection
Establishment and
HSUPA RAB
Establishment
Completion for Cell
Earlier than
BSC6900
V900R011
67196050
VS.HSDPA.Golden
BeChThroughput.0
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between 0
Kbit/s and 32 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67196051
VS.HSDPA.Golden
BeChThroughput.1
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between 32
for Cell
Earlier than
BSC6900
V900R011

2472
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196052
VS.HSDPA.Golden
BeChThroughput.2
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between 64
for Cell
Earlier than
BSC6900
V900R011
67196053
VS.HSDPA.Golden
BeChThroughput.3
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196054
VS.HSDPA.Golden
BeChThroughput.4
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196055
VS.HSDPA.Golden
BeChThroughput.5
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196056
VS.HSDPA.Golden
BeChThroughput.6
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
1024 Kbit/s and 1536
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2473
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196057
VS.HSDPA.Golden
BeChThroughput.7
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196058
VS.HSDPA.Golden
BeChThroughput.8
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196059
VS.HSDPA.Golden
BeChThroughput.9
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196060
VS.HSDPA.Golden
BeChThroughput.
10
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196061
VS.HSDPA.Golden
BeChThroughput.
11
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2474
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196062
VS.HSDPA.Golden
BeChThroughput.
12
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Between
8192 Kbit/s and
12288 Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196063
VS.HSDPA.Golden
BeChThroughput.
13
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Golden BE
Services Greater
Than 12288 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67196064
VS.HSDPA.SilverBeChThroughput.0
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between 0
for Cell
Earlier than
BSC6900
V900R011
67196065
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between 32
for Cell
Earlier than
BSC6900
V900R011
67196066
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between 64
for Cell
Earlier than
BSC6900
V900R011

2475
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196067
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196068
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196069
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196070
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196071
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2476
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196072
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196073
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196074
VS.HSDPA.SilverBeChThroughput.
10
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196075
11
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196076
12
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Between
8192 Kbit/s and
Earlier than
BSC6900
V900R011

2477
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196077
13
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Silver BE
Services Greater
Than 12288 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67196078
VS.HSDPA.Copper
BeChThroughput.0
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between 0
for Cell
Earlier than
BSC6900
V900R011
67196079
VS.HSDPA.Copper
BeChThroughput.1
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between 32
for Cell
Earlier than
BSC6900
V900R011
67196080
VS.HSDPA.Copper
BeChThroughput.2
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between 64
for Cell
Earlier than
BSC6900
V900R011
67196081
VS.HSDPA.Copper
BeChThroughput.3
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2478
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196082
VS.HSDPA.Copper
BeChThroughput.4
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196083
VS.HSDPA.Copper
BeChThroughput.5
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196084
VS.HSDPA.Copper
BeChThroughput.6
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196085
VS.HSDPA.Copper
BeChThroughput.7
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196086
VS.HSDPA.Copper
BeChThroughput.8
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2479
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196087
VS.HSDPA.Copper
BeChThroughput.9
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196088
VS.HSDPA.Copper
BeChThroughput.
10
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196089
VS.HSDPA.Copper
BeChThroughput.
11
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196090
VS.HSDPA.Copper
BeChThroughput.
12
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Between
8192 Kbit/s and
Earlier than
BSC6900
V900R011
67196091
VS.HSDPA.Copper
BeChThroughput.
13
Number of Times
that Average DL
Throughput of
MAC-d Flow of
HSDPA Bronze BE
Services Greater
Than 12288 Kbit/s
for Cell
Earlier than
BSC6900
V900R011

2480
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196092
VS.HSUPA.Golden
BeChThroughput.0
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between 0
for Cell
Earlier than
BSC6900
V900R011
67196093
VS.HSUPA.Golden
BeChThroughput.1
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between 32
for Cell
Earlier than
BSC6900
V900R011
67196094
VS.HSUPA.Golden
BeChThroughput.2
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between 64
for Cell
Earlier than
BSC6900
V900R011
67196095
VS.HSUPA.Golden
BeChThroughput.3
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196096
VS.HSUPA.Golden
BeChThroughput.4
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2481
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196097
VS.HSUPA.Golden
BeChThroughput.5
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196098
VS.HSUPA.Golden
BeChThroughput.6
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196099
VS.HSUPA.Golden
BeChThroughput.7
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196100
VS.HSUPA.Golden
BeChThroughput.8
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196101
VS.HSUPA.Golden
BeChThroughput.9
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2482
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196102
VS.HSUPA.Golden
BeChThroughput.
10
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Golden BE
Services Greater
Than 4096 Kbit/s for
Cell
Earlier than
BSC6900
V900R011
67196103
VS.HSUPA.SilverBeChThroughput.0
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between 0
for Cell
Earlier than
BSC6900
V900R011
67196104
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between 32
for Cell
Earlier than
BSC6900
V900R011
67196105
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between 64
for Cell
Earlier than
BSC6900
V900R011
67196106
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2483
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196107
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196108
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196109
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196110
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196111
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2484
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196112
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196113
VS.HSUPA.SilverBeChThroughput.
10
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Silver BE
Services Greater
Cell
Earlier than
BSC6900
V900R011
67196114
VS.HSUPA.Copper
BeChThroughput.0
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between 0
for Cell
Earlier than
BSC6900
V900R011
67196115
VS.HSUPA.Copper
BeChThroughput.1
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between 32
for Cell
Earlier than
BSC6900
V900R011
67196116
VS.HSUPA.Copper
BeChThroughput.2
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between 64
for Cell
Earlier than
BSC6900
V900R011

2485
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196117
VS.HSUPA.Copper
BeChThroughput.3
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
256 Kbit/s and 512
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196118
VS.HSUPA.Copper
BeChThroughput.4
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
512 Kbit/s and 768
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196119
VS.HSUPA.Copper
BeChThroughput.5
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
768 Kbit/s and 1024
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196120
VS.HSUPA.Copper
BeChThroughput.6
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196121
VS.HSUPA.Copper
BeChThroughput.7
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2486
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196122
VS.HSUPA.Copper
BeChThroughput.8
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196123
VS.HSUPA.Copper
BeChThroughput.9
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Between
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67196124
VS.HSUPA.Copper
BeChThroughput.
10
Number of Times
that Average UL
Throughput of
MAC-d Flow of
HSUPA Bronze BE
Services Greater
Cell
Earlier than
BSC6900
V900R011
73423349
VS.ERACH.Estab.
MaxTime
Maximum Service
ERACH for Cell
BSC6900
V900R013
73441136
VS.ERACH.Estab.
MeanTime
Average Service
ERACH for Cell
BSC6900
V900R013
73423352
VS.ERACH.Estab.
MinTime
Minimum Service
ERACH for Cell
BSC6900
V900R013
73423353
VS.EFACH.Estab.
MaxTime
Maximum Service
EFACH for Cell
BSC6900
V900R013
73441137
VS.EFACH.Estab.
MeanTime
Average Service
EFACH for Cell
BSC6900
V900R013
73423356
VS.EFACH.Estab.
MinTime
Minimum Service
EFACH for Cell
BSC6900
V900R013

2487
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444317
VS.P2F.MeanTime
Average Delay of
CELL_PCH/
URA_PCH-toCELL_FACH State
BSC6900
V900R016C00
73444318
VS.P2D.MeanTime
Average Delay of
CELL_PCH/
BSC6900
V900R016C00
73444319
VS.F2D.MeanTime
Average Delay of
CELL_FACH-toCELL_DCH State
BSC6900
V900R016C00
73444380
VS.HSDPA.BeChT
hroughput.DevGrp
0
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp0
UEs for Cell
BSC6900
V900R016C00
73444381
VS.HSDPA.BeChT
hroughput.TotalBy
tes.DevGrp0
Number of Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp0
UEs for Cell
BSC6900
V900R016C00
73444383
VS.HSDPA.BeChT
hroughput.DevGrp
1
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp1
UEs for Cell
BSC6900
V900R016C00
73444384
VS.HSDPA.BeChT
hroughput.TotalBy
tes.DevGrp1
Number of Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp1
UEs for Cell
BSC6900
V900R016C00

2488
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444386
VS.HSDPA.BeChT
hroughput.DevGrp
2
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp2
UEs for Cell
BSC6900
V900R016C00
73444387
VS.HSDPA.BeChT
hroughput.TotalBy
tes.DevGrp2
Number of Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp2
UEs for Cell
BSC6900
V900R016C00
73444389
VS.HSDPA.BeChT
hroughput.DevGrp
3
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp3
UEs for Cell
BSC6900
V900R016C00
73444390
VS.HSDPA.BeChT
hroughput.TotalBy
tes.DevGrp3
Number of Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp3
UEs for Cell
BSC6900
V900R016C00
73444392
VS.HSDPA.BeChT
hroughput.DevGrp
4
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp4
UEs for Cell
BSC6900
V900R016C00
73444393
VS.HSDPA.BeChT
hroughput.TotalBy
tes.DevGrp4
Number of Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp4
UEs for Cell
BSC6900
V900R016C00
73444395
VS.HSDPA.BeChT
hroughput.DevGrp
5
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp5
UEs for Cell
BSC6900
V900R016C00

2489
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444396
VS.HSDPA.BeChT
hroughput.TotalBy
tes.DevGrp5
Number of Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp5
UEs for Cell
BSC6900
V900R016C00
73444398
VS.HSDPA.BeChT
hroughput.DevGrp
6
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp6
UEs for Cell
BSC6900
V900R016C00
73444399
VS.HSDPA.BeChT
hroughput.TotalBy
tes.DevGrp6
Number of Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp6
UEs for Cell
BSC6900
V900R016C00
73444401
VS.HSDPA.BeChT
hroughput.DevGrp
7
Average DL
Throughput of
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp7
UEs for Cell
BSC6900
V900R016C00
73444402
VS.HSDPA.BeChT
hroughput.TotalBy
tes.DevGrp7
Number of Bytes
Transmitted on
HSDPA MAC-d
Flows Carrying BE
Services of DevGrp7
UEs for Cell
BSC6900
V900R016C00
73444404
VS.HSUPA.BeChT
hroughput.DevGrp
0
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying BE
Services of DevGrp0
UEs for Cell
BSC6900
V900R016C00
73444405
VS.HSUPA.BeChT
hroughput.TotalBy
tes.DevGrp0
Number of Bytes
Received by HSUPA
MAC-d Flows
Carrying BE
Services of DevGrp0
UEs for Cell
BSC6900
V900R016C00

2490
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444407
VS.HSUPA.BeChT
hroughput.DevGrp
1
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying BE
Services of DevGrp1
UEs for Cell
BSC6900
V900R016C00
73444408
VS.HSUPA.BeChT
hroughput.TotalBy
tes.DevGrp1
Number of Bytes
Received by HSUPA
MAC-d Flows
Carrying BE
Services of DevGrp1
UEs for Cell
BSC6900
V900R016C00
73444410
VS.HSUPA.BeChT
hroughput.DevGrp
2
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying BE
Services of DevGrp2
UEs for Cell
BSC6900
V900R016C00
73444411
VS.HSUPA.BeChT
hroughput.TotalBy
tes.DevGrp2
Number of Bytes
Received by HSUPA
MAC-d Flows
Carrying BE
Services of DevGrp2
UEs for Cell
BSC6900
V900R016C00
73444413
VS.HSUPA.BeChT
hroughput.DevGrp
3
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying BE
Services of DevGrp3
UEs for Cell
BSC6900
V900R016C00
73444414
VS.HSUPA.BeChT
hroughput.TotalBy
tes.DevGrp3
Number of Bytes
Received by HSUPA
MAC-d Flows
Carrying BE
Services of DevGrp3
UEs for Cell
BSC6900
V900R016C00
73444416
VS.HSUPA.BeChT
hroughput.DevGrp
4
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying BE
Services of DevGrp4
UEs for Cell
BSC6900
V900R016C00

2491
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444417
VS.HSUPA.BeChT
hroughput.TotalBy
tes.DevGrp4
Number of Bytes
Received by HSUPA
MAC-d Flows
Carrying BE
Services of DevGrp4
UEs for Cell
BSC6900
V900R016C00
73444419
VS.HSUPA.BeChT
hroughput.DevGrp
5
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying BE
Services of DevGrp5
UEs for Cell
BSC6900
V900R016C00
73444420
VS.HSUPA.BeChT
hroughput.TotalBy
tes.DevGrp5
Number of Bytes
Received by HSUPA
MAC-d Flows
Carrying BE
Services of DevGrp5
UEs for Cell
BSC6900
V900R016C00
73444422
VS.HSUPA.BeChT
hroughput.DevGrp
6
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying BE
Services of DevGrp6
UEs for Cell
BSC6900
V900R016C00
73444423
VS.HSUPA.BeChT
hroughput.TotalBy
tes.DevGrp6
Number of Bytes
Received by HSUPA
MAC-d Flows
Carrying BE
Services of DevGrp6
UEs for Cell
BSC6900
V900R016C00
73444425
VS.HSUPA.BeChT
hroughput.DevGrp
7
Average UL
Throughput of
HSUPA MAC-d
Flows Carrying BE
Services of DevGrp7
UEs for Cell
BSC6900
V900R016C00
73444426
VS.HSUPA.BeChT
hroughput.TotalBy
tes.DevGrp7
Number of Bytes
Received by HSUPA
MAC-d Flows
Carrying BE
Services of DevGrp7
UEs for Cell
BSC6900
V900R016C00

2492
BSC6900 UMTS
None
Delay of Different Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
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

RRC Connection
Establishment and 64kbit/s
CS RAB Establishment
Completion for Cell
67204786
VS.CS64.Estab.MeanTime

and 64kbit/s CS RAB
for Cell
67195977
VS.CS64.Estab.MinTime

RRC Connection
Completion for Cell
67195980
VS.PSR99.Estab.MaxTime

RRC Connection
Establishment and PS R99
RAB Establishment
Completion for Cell

2493
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67204787
VS.PSR99.Estab.MeanTime

and PS R99 RAB
for Cell
67195981
VS.PSR99.Estab.MinTime

RRC Connection
RAB Establishment
Completion for Cell
67195984
VS.HSDPA.Estab.MaxTime

RRC Connection
Establishment and HSDPA
RAB Establishment
Completion for Cell
67204788
VS.HSDPA.Estab.MeanTime

and HSDPA RAB
for Cell
67195985
VS.HSDPA.Estab.MinTime

RRC Connection
RAB Establishment
Completion for Cell
67195988
VS.HSUPA.Estab.MaxTime

RRC Connection
Establishment and HSUPA
RAB Establishment
Completion for Cell
67204789
VS.HSUPA.Estab.MeanTime

and HSUPA RAB
for Cell
67195989
VS.HSUPA.Estab.MinTime

RRC Connection
RAB Establishment
Completion for Cell
specific formulas.
Issue 03 (2015-06-30)

2494
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67195974
VS.AMR.Estab.Cum
Cumulative Delay Between

RRC Connection
RAB Establishment
Completion for Cell
67195975
VS.AMR.Estab.Sample
Accumulative Delay
Between RRC Connection
RAB Establishment
Completion for Cell
67195978
VS.CS64.Estab.Cum

RRC Connection
Completion for Cell
67195979
VS.CS64.Estab.Sample
Accumulative Delay
Completion for Cell
67195986
VS.HSDPA.Estab.Cum

RRC Connection
RAB Establishment
Completion for Cell
67195987
VS.HSDPA.Estab.Sample
Accumulative Delay
RAB Establishment
Completion for Cell
67195990
VS.HSUPA.Estab.Cum

RRC Connection
RAB Establishment
Completion for Cell
67195991
VS.HSUPA.Estab.Sample
RRC Connection
RAB Establishment
Completion for Cell

2495
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67195982
VS.PSR99.Estab.Cum

RRC Connection
RAB Establishment
Completion for Cell
67195983
VS.PSR99.Estab.Sample
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. 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.The preceding counters comply with section "6.1.1 RRC Connection
Setup","6.1.2 CS Call Setup" in 3GPP TR 25.815 (v7.0.0).
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=T2T1. 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.
Issue 03 (2015-06-30)

2496
BSC6900 UMTS
Figure 1-1082 RAB establishment flow
The figure shows the RAB setup procedure that is in parallel with the alerting procedure. The
measurement is triggered at point A. When the RNC receives an RRC CONNECTION
REQUEST message from the UE, as shown by point A, the RNC records the receive time (T1).
When the RNC receives an RADIO BEARER SETUP COMPLETE message from the UE, the
RNC records the receive time (T2). The service setup delay equals T2 minus T1. The
VS.AMR.Estab.MeanTime, VS.AMR.Estab.MaxTime, and VS.AMR.Estab.MinTime are
measured in the best cell. This counter is measured only for the first RAB.
Issue 03 (2015-06-30)

2497
BSC6900 UMTS
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AMR.Estab.MeanTime
WRFD-010501
WRFD-171202

2498
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.AMR.Estab.MaxTime
WRFD-010501
WRFD-171202
WRFD-010501
WRFD-171202
VS.CS64.Estab.MaxTime
WRFD-010501
VS.CS64.Estab.MeanTime
WRFD-010501
VS.CS64.Estab.MinTime
WRFD-010501
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

VS.AMR.Estab.MinTime
WRFD-010630

HSDPA
VS.HSDPA.Estab.MeanTime
WRFD-01061008
WRFD-010630

HSDPA
VS.HSDPA.Estab.MinTime
WRFD-01061008
WRFD-010630

HSDPA
VS.HSUPA.Estab.MaxTime
WRFD-01061206
WRFD-010632

HSUPA
Issue 03 (2015-06-30)

2499
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.HSUPA.Estab.MeanTime
WRFD-01061206

WRFD-010632

HSUPA
VS.HSUPA.Estab.MinTime
WRFD-01061206
WRFD-010632

HSUPA
Counters Related to the Number of Times that DL Throughput of HSDPA Services

Within Each Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196050
VS.HSDPA.GoldenBeChThroughput.0

MAC-d Flow of HSDPA
Golden BE Services Between
0 Kbit/s and 32 Kbit/s for Cell
67196051

MAC-d Flow of HSDPA
32 Kbit/s and 64 Kbit/s for
Cell
67196052

MAC-d Flow of HSDPA
Cell
67196053

MAC-d Flow of HSDPA
Cell

2500
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196054

MAC-d Flow of HSDPA
Cell
67196055

MAC-d Flow of HSDPA
768 Kbit/s and 1024 Kbit/s
for Cell
67196056

MAC-d Flow of HSDPA
for Cell
67196057

MAC-d Flow of HSDPA
for Cell
67196058

MAC-d Flow of HSDPA
for Cell
67196059

MAC-d Flow of HSDPA
for Cell
67196060

MAC-d Flow of HSDPA
for Cell

2501
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196061

MAC-d Flow of HSDPA
for Cell
67196062

MAC-d Flow of HSDPA
8192 Kbit/s and 12288 Kbit/
s for Cell
67196063

MAC-d Flow of HSDPA
Golden BE Services Greater
Than 12288 Kbit/s for Cell
67196064

MAC-d Flow of HSDPA
Silver BE Services Between
67196065

MAC-d Flow of HSDPA
Cell
67196066

MAC-d Flow of HSDPA
Cell
67196067

MAC-d Flow of HSDPA
Cell

2502
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196068

MAC-d Flow of HSDPA
Cell
67196069

MAC-d Flow of HSDPA
for Cell
67196070

MAC-d Flow of HSDPA
for Cell
67196071

MAC-d Flow of HSDPA
for Cell
67196072

MAC-d Flow of HSDPA
for Cell
67196073

MAC-d Flow of HSDPA
for Cell
67196074

MAC-d Flow of HSDPA
for Cell

2503
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196075

MAC-d Flow of HSDPA
for Cell
67196076

MAC-d Flow of HSDPA
s for Cell
67196077

MAC-d Flow of HSDPA
Silver BE Services Greater
67196078
VS.HSDPA.CopperBeChThroughput.0

MAC-d Flow of HSDPA
Bronze BE Services Between
67196079

MAC-d Flow of HSDPA
Cell
67196080

MAC-d Flow of HSDPA
Cell
67196081

MAC-d Flow of HSDPA
Cell

2504
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196082

MAC-d Flow of HSDPA
Cell
67196083

MAC-d Flow of HSDPA
for Cell
67196084

MAC-d Flow of HSDPA
for Cell
67196085

MAC-d Flow of HSDPA
for Cell
67196086

MAC-d Flow of HSDPA
for Cell
67196087

MAC-d Flow of HSDPA
for Cell
67196088

MAC-d Flow of HSDPA
for Cell

2505
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67196089

MAC-d Flow of HSDPA
for Cell
67196090

MAC-d Flow of HSDPA
s for Cell
67196091

MAC-d Flow of HSDPA
Bronze BE Services Greater
Description
These counters provide the number of times that the average downlink throughput of the MACd flow carrying BE services at the RCL layer falls in the corresponding range based on the level
of the service in an HSDPA serving cell. For DC-HSDPA users, these counters are measured
only in the primary cell based on the total throughput on the primary and secondary carriers.
These counters are measured only when the SPI measure function is activated using the SET
UDPUCFGDATA command with CellCountersMeasOBJCtrlSwitch set to Qos or QosAndSpi.
Measurement point
In an HSDPA serving cell, the RNC takes samples of the average downlink throughput (the RLC
header and retransmitted data are not measured) of the MAC-d flow carrying BE services at the
RLC layer for gold, silver, and copper users every 20 seconds. When the throughput falls in a
predefined range, the corresponding counter is incremented by one. At the end of a measurement
period, the value of each counter is obtained.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2506
BSC6900 UMTS
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008


2507
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008


2508
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

Counters Related to the Number of Times that UL Throughput of HSUPA Services

Within Each Range
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196092
VS.HSUPA.GoldenBeChThroughput.0

Average UL Throughput of
MAC-d Flow of HSUPA
67196093

MAC-d Flow of HSUPA
Cell
67196094

MAC-d Flow of HSUPA
Cell

2509
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196095

MAC-d Flow of HSUPA
Cell
67196096

MAC-d Flow of HSUPA
Cell
67196097

MAC-d Flow of HSUPA
for Cell
67196098

MAC-d Flow of HSUPA
for Cell
67196099

MAC-d Flow of HSUPA
for Cell
67196100

MAC-d Flow of HSUPA
for Cell
67196101

MAC-d Flow of HSUPA
for Cell

2510
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196102

MAC-d Flow of HSUPA
Golden BE Services Greater
67196103

MAC-d Flow of HSUPA
67196104

MAC-d Flow of HSUPA
Cell
67196105

MAC-d Flow of HSUPA
Cell
67196106

MAC-d Flow of HSUPA
Cell
67196107

MAC-d Flow of HSUPA
Cell
67196108

MAC-d Flow of HSUPA
for Cell

2511
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196109

MAC-d Flow of HSUPA
for Cell
67196110

MAC-d Flow of HSUPA
for Cell
67196111

MAC-d Flow of HSUPA
for Cell
67196112

MAC-d Flow of HSUPA
for Cell
67196113

MAC-d Flow of HSUPA
Silver BE Services Greater
67196114
VS.HSUPA.CopperBeChThroughput.0

MAC-d Flow of HSUPA
67196115

MAC-d Flow of HSUPA
Cell

2512
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196116

MAC-d Flow of HSUPA
Cell
67196117

MAC-d Flow of HSUPA
Cell
67196118

MAC-d Flow of HSUPA
Cell
67196119

MAC-d Flow of HSUPA
for Cell
67196120

MAC-d Flow of HSUPA
for Cell
67196121

MAC-d Flow of HSUPA
for Cell
67196122

MAC-d Flow of HSUPA
for Cell

2513
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67196123

MAC-d Flow of HSUPA
for Cell
67196124

MAC-d Flow of HSUPA
Bronze BE Services Greater
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
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-01061206


2514
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206


2515
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

Service Setup Duration on an ERACH or EFACH for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423349
VS.ERACH.Estab.MaxTime
Maximum Service Setup

Duration on an ERACH for
Cell

2516
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73441136
VS.ERACH.Estab.MeanTime
Average Service Setup

Cell
73423352
VS.ERACH.Estab.MinTime
Minimum Service Setup

Cell
73441137
VS.EFACH.Estab.MeanTime
Average Service Setup

Duration on an EFACH for
Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73423354
VS.EFACH.Estab.Cum

RRC Connection
Establishment and EFACH
RAB Establishment
Completion for Cell
73423355
VS.EFACH.Estab.Sample
RRC Connection
Establishment and EFACH
RAB Establishment
Completion for Cell
73423350
VS.ERACH.Estab.Cum

RRC Connection
Establishment and ERACH
RAB Establishment
Completion for Cell
73423351
VS.ERACH.Estab.Sample
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.The preceding counters comply with section "6.1.1
RRC Connection Setup","6.1.2 CS Call Setup" in 3GPP TR 25.815 (v7.0.0).
Issue 03 (2015-06-30)

2517
BSC6900 UMTS
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.
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
Issue 03 (2015-06-30)

2518
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.ERACH.Estab.MaxTime
WRFD-010701
Uplink Enhanced
CELL_FACH
VS.ERACH.Estab.MeanTime
WRFD-010701
Uplink Enhanced
CELL_FACH
VS.ERACH.Estab.MinTime
WRFD-010701
Uplink Enhanced
CELL_FACH
VS.EFACH.Estab.MeanTime
WRFD-010688
Downlink Enhanced
CELL_FACH
Service Setup Duration on an EFACH for Cell

Counters
Counter ID
Counter Name
Counter Description
73423353
VS.EFACH.Estab.MaxTime
Maximum Service Setup

Cell
Description
This counter provides the duration from the RRC connection setup to the service setup on an
EFACH in the cell.
Measurement point
at point A, the time is recorded as T1. When the RNC sends the CN an RAB ASSIGNMENT
RESPONSE message at point B after receiving from the UE a RADIO BEARER SETUP
COMPLETE message, the time is recorded as T2. The RNC uses delta T=T2-T1 as the service
setup duration on an ERACH if the service is set up on an ERACH. In this case, the corresponding
counter is measured in the best cell that the UE camps on according to the service mode and
type.
Issue 03 (2015-06-30)

2519
BSC6900 UMTS
Formula
None
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.EFACH.Estab.MaxTime
WRFD-010688
Downlink Enhanced
CELL_FACH

2520
BSC6900 UMTS
Minimum Service Setup Duration on an EFACH for Cell

Counters
Counter ID
Counter Name
Counter Description
73423356
VS.EFACH.Estab.MinTime
Minimum Service Setup

Cell
Counter Name
Feature ID
Feature Name
VS.EFACH.Estab.MinTime
WRFD-010688
Downlink Enhanced
CELL_FACH
Description
None
Measurement point
None
Formula
None
Unit
ms
Related Features
Average Delay of CELL_PCH/URA_PCH-to-CELL_FACH/CELL_DCH State

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444317
VS.P2F.MeanTime
Average Delay of
CELL_PCH/URA_PCH-toCELL_FACH State

2521
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444318
VS.P2D.MeanTime
Average Delay of
CELL_PCH/URA_PCH-toCELL_DCH State
specific formulas.
Counter ID
Counter Name
Counter Description
73428092
VS.P2D.Num
Number of CELL_PCH/
URA_PCH-to-CELL_DCH
73428091
VS.P2D.TotalTime
Total Delay of CELL_PCH/

URA_PCH-to-CELL_DCH
73428090
VS.P2F.Num
Number of CELL_PCH/
73428089
VS.P2F.TotalTime
Total Delay of CELL_PCH/

Description
These counters measure the average delay of state transitions from CELL_PCH or URA_PCH
to CELL_FACH or CELL_DCH in a cell.The preceding counters complies with section "8.3.1
Cell and URA update procedures", "B.3 UTRA RRC Connected Mode States and Transitions"in
3GPP TS 25.331(v10.13.0).
Measurement point
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 (shown
by point A in the figure), the RNC records the receive time (T1). After returning a CELL
UPDATE CONFIRM message to the UE, the RNC receives a response indicating that the state
transition from CELL_PCH or URA_PCH to CELL_FACH or CELL_DCH is successful, for
example, a RADIO RECONFIGURATION COMPLETE message. The RNC records the
receive time (T2), as shown by point B in the figure. The transition delay (delta T) equals T2
minus T1. At the end of a measurement period, the RNC obtains the average delay of state
transitions from CELL_PCH or URA_PCH to CELL_FACH or CELL_DCH by dividing the
sum of transition delay by the number of successful state transitions. These counters are
Issue 03 (2015-06-30)

2522
BSC6900 UMTS
measured in the cell where the UE initiates the cell update procedure, if P2F redirection occurs,
the counter VS.P2F.MeanTime is measured in the cell where the UE finishes the cell update
procedure. 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:
Formula
VS.P2F.MeanTime = [VS.P2F.TotalTime]/[VS.P2F.Num]
VS.P2D.MeanTime = [VS.P2D.TotalTime]/[VS.P2D.Num]
Unit
ms
Issue 03 (2015-06-30)

2523
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.P2F.MeanTime
WRFD-010202

URA-PCH, CELL-FACH)
VS.P2D.MeanTime
WRFD-010202

URA-PCH, CELL-FACH)
Average Delay of CELL_FACH-to-CELL_DCH State Transitions for Cell

Counters
Counter ID
Counter Name
Counter Description
73444319
VS.F2D.MeanTime
Average Delay of
specific formulas.
Counter ID
Counter Name
Counter Description
73428094
VS.F2D.Num
Number of CELL_FACH-toCELL_DCH State

73428093
VS.F2D.TotalTime
Total Delay of
Description
This counter measures the average delay of state transitions from CELL_FACH to CELL_DCH
in a cell.
Measurement point
When sending a RADIO BEARER RECONFIGURATION message to a UE in the
CELL_FACH state (shown by point A in the figure), the RNC records the send time (T1). On
receiving a RADIO BEARER RECONFIGURATION COMPLETE message from the UE, the
Issue 03 (2015-06-30)

2524
BSC6900 UMTS
RNC considers the CELL_FACH-to-CELL_DCH state transition as successful and records the
receive time (shown by point B in the figure, recorded as T2). The transition delay (delta T)
equals T2 minus T1. At the end of a measurement period, the RNC obtains the average delay of
state transitions from CELL_FACH or CELL_DCH by dividing the sum of transition delay by
the number of successful state transitions. This counter is measured in the cell where the RNC
sends the RADIO BEARER RECONFIGURATION message.
Formula
VS.F2D.MeanTime = [VS.F2D.TotalTime]/[VS.F2D.Num]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.F2D.MeanTime
WRFD-010202

URA-PCH, CELL-FACH)

2525
BSC6900 UMTS
Average DL Throughput of HSDPA MAC-d Flows Carrying BE Services of

DevGrp0 to DevGrp7 UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73444380
VS.HSDPA.BeChThroughp
ut.DevGrp0
HSDPA MAC-d Flows
Carrying BE Services of
DevGrp0 UEs for Cell
73444383
ut.DevGrp1
HSDPA MAC-d Flows
73444386
ut.DevGrp2
HSDPA MAC-d Flows
73444389
ut.DevGrp3
HSDPA MAC-d Flows
73444392
ut.DevGrp4
HSDPA MAC-d Flows
73444395
ut.DevGrp5
HSDPA MAC-d Flows
73444398
ut.DevGrp6
HSDPA MAC-d Flows
73444401
ut.DevGrp7
HSDPA MAC-d Flows
specific formulas.
Issue 03 (2015-06-30)

2526
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444382
ut.Times.DevGrp0
DL Transmission Time of
HSDPA MAC-d Flows
73444385
ut.Times.DevGrp1
HSDPA MAC-d Flows
73444388
ut.Times.DevGrp2
HSDPA MAC-d Flows
73444391
ut.Times.DevGrp3
HSDPA MAC-d Flows
73444394
ut.Times.DevGrp4
HSDPA MAC-d Flows
73444397
ut.Times.DevGrp5
HSDPA MAC-d Flows
73444400
ut.Times.DevGrp6
HSDPA MAC-d Flows
73444403
ut.Times.DevGrp7
HSDPA MAC-d Flows
Description
These counters provide the average downlink throughput of HSDPA MAC-d flows carrying BE
services of UEs in different device groups in the HSDPA serving cell. For MC-HSDPA UEs,
these counters are measured only in the primary cell based on the total throughput on the primary
and secondary carriers. The eight device groups to be monitored can be set through the
MonDevGrp0ID, MonDevGrp1ID, MonDevGrp2ID, MonDevGrp3ID, MonDevGrp4ID,
MonDevGrp5ID, MonDevGrp6ID, and MonDevGrp7ID parameters in the SET
UMONDEVGRPID command. By default, device groups 0 to 7 are monitored.
Issue 03 (2015-06-30)

2527
BSC6900 UMTS
Measurement point
When UEs in an HSDPA serving cell are processing BE services, the system periodically (every
20s) takes samples of the total data transmission time of and the number of bits (excluding RLC
headers and retransmitted data) transmitted at the RLC layer by UEs in different device groups.
At the end of a sampling period, the system divides the total number of bits by the total data
transmission time and obtains the average downlink throughput of the MAC-d flows carrying
BE services of UEs in different device groups at the RLC layer.
Formula
VS.HSDPA.BeChThroughput.DevGrp0 = {8}*
[VS.HSDPA.BeChThroughput.TotalBytes.DevGrp0]/
[VS.HSDPA.BeChThroughput.Times.DevGrp0]
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ut.DevGrp0
WRFD-150255

on Terminal

2528
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
ut.DevGrp1
WRFD-150255

on Terminal
ut.DevGrp2
WRFD-150255

on Terminal
ut.DevGrp3
WRFD-150255

on Terminal
ut.DevGrp4
WRFD-150255

on Terminal
ut.DevGrp5
WRFD-150255

on Terminal
ut.DevGrp6
WRFD-150255

on Terminal
ut.DevGrp7
WRFD-150255

on Terminal
Number of Bytes Transmitted on HSDPA MAC-d Flows Carrying BE Services of

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444381
ut.TotalBytes.DevGrp0
Number of Bytes
Transmitted on HSDPA
MAC-d Flows Carrying BE
Services of DevGrp0 UEs for
Cell
73444384
Number of Bytes
Cell
73444387
Number of Bytes
Cell

2529
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444390
Number of Bytes
Cell
73444393
Number of Bytes
Cell
73444396
Number of Bytes
Cell
73444399
Number of Bytes
Cell
73444402
Number of Bytes
Cell
Description
These counters provide the number of bytes transmitted on HSDPA MAC-d flows carrying BE
services of UEs in different device groups in the HSDPA serving cell. For MC-HSDPA UEs,
these counters are measured only in the primary cell based on the total number of bytes
transmitted on the primary and secondary carriers. The eight device groups to be monitored can
be set through the MonDevGrp0ID, MonDevGrp1ID, MonDevGrp2ID, MonDevGrp3ID,
MonDevGrp4ID, MonDevGrp5ID, MonDevGrp6ID, and MonDevGrp7ID parameters in the
SET UMONDEVGRPID command. By default, device groups 0 to 7 are monitored.
Measurement point
When UEs in an HSDPA serving cell are processing BE services, the system periodically (every
20s) takes samples of the number of bytes of BE services transmitted on the RLC layer toby
UEs in different device groups at the RLC layer. The measured data excludes RLC headers and
retransmitted data.
Issue 03 (2015-06-30)

2530
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
Average UL Throughput of HSUPA MAC-d Flows Carrying BE Services of

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444404
VS.HSUPA.BeChThroughp
ut.DevGrp0
HSUPA MAC-d Flows

2531
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444407
ut.DevGrp1
HSUPA MAC-d Flows
73444410
ut.DevGrp2
HSUPA MAC-d Flows
73444413
ut.DevGrp3
HSUPA MAC-d Flows
73444416
ut.DevGrp4
HSUPA MAC-d Flows
73444419
ut.DevGrp5
HSUPA MAC-d Flows
73444422
ut.DevGrp6
HSUPA MAC-d Flows
73444425
ut.DevGrp7
HSUPA MAC-d Flows
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444406
ut.Times.DevGrp0
UL Transmission Time of
HSUPA MAC-d Flows
73444409
ut.Times.DevGrp1
HSUPA MAC-d Flows

2532
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444412
ut.Times.DevGrp2
HSUPA MAC-d Flows
73444415
ut.Times.DevGrp3
HSUPA MAC-d Flows
73444418
ut.Times.DevGrp4
HSUPA MAC-d Flows
73444421
ut.Times.DevGrp5
HSUPA MAC-d Flows
73444424
ut.Times.DevGrp6
HSUPA MAC-d Flows
73444427
ut.Times.DevGrp7
HSUPA MAC-d Flows
Description
These counters provide the average uplink throughput of HSUPA MAC-d flows carrying BE
services of UEs in different device groups in the HSUPA serving cell. For MC-HSUPA UEs,
these counters are measured only in the primary cell based on the total throughput on the primary
and secondary carriers. The eight device groups to be monitored can be set through the
MonDevGrp0ID, MonDevGrp1ID, MonDevGrp2ID, MonDevGrp3ID, MonDevGrp4ID,
MonDevGrp5ID, MonDevGrp6ID, and MonDevGrp7ID parameters in the SET
UMONDEVGRPID command. By default, device groups 0 to 7 are monitored.
Measurement point
When UEs in an HSUPA serving cell are processing BE services, the system periodically (every
20s) takes samples of the total data transmission time of and the number of bits received at the
RLC layer by UEs in different device groups. At the end of a sampling period, the system divides
the total number of bits (excluding the RLC headers and retransmitted data) by the total data
transmission time and obtains the average uplink throughput of the MAC-d flows carrying BE
services of UEs in different device groups at the RLC layer.
Issue 03 (2015-06-30)

2533
BSC6900 UMTS
Formula
VS.HSUPA.BeChThroughput.DevGrp0 = {8}*
[VS.HSUPA.BeChThroughput.TotalBytes.DevGrp0]/
[VS.HSUPA.BeChThroughput.Times.DevGrp0]
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ut.DevGrp0
WRFD-150255

on Terminal
ut.DevGrp1
WRFD-150255

on Terminal
ut.DevGrp2
WRFD-150255

on Terminal
ut.DevGrp3
WRFD-150255

on Terminal

2534
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
ut.DevGrp4
WRFD-150255

on Terminal
ut.DevGrp5
WRFD-150255

on Terminal
ut.DevGrp6
WRFD-150255

on Terminal
ut.DevGrp7
WRFD-150255

on Terminal
Number of Bytes Received by HSUPA MAC-d Flows Carrying BE Services of

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73444405
Number of Bytes Received

by HSUPA MAC-d Flows
73444408

73444411

73444414

73444417

73444420


2535
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444423

73444426

Description
These counters provide the number of bytes received by HSUPA MAC-d flows carrying BE
services of UEs in different device groups in the HSUPA serving cell. For MC-HSUPA UEs,
these counters are measured only in the primary cell based on the total number of bytes received
from the primary and secondary carriers. The eight device groups to be monitored can be set
through the MonDevGrp0ID, MonDevGrp1ID, MonDevGrp2ID, MonDevGrp3ID,
MonDevGrp4ID, MonDevGrp5ID, MonDevGrp6ID, and MonDevGrp7ID parameters in the
SET UMONDEVGRPID command. By default, device groups 0 to 7 are monitored.
Measurement point
When UEs in an HSUPA serving cell are processing BE services, the system periodically (every
20s) takes samples of the number of bytes of BE services received at the RLC layer from UEs
in different device groups. The measured data excludes RLC headers and retransmitted data.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal

2536
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
WRFD-150255

on Terminal
1.12.30 CS RAB Setup Measurement <per Cell>(RAB.EstabCS.Cell)

Overview
During the RAB setup process:
If the RAB is setup successfully, the RAB setup is measured in the best cell after the RAB setup.
If the RAB setup fails, the RAB setup is measured in the first DRD attempt cell if the DRD is
performed. The RAB assignment setup is measured in the current best cell if the DRD is not
performed.
The RAB setup procedure is illustrated in Figure 1.
After the parallel handling of the alerting and RAB setup procedures is introduced, the RNC
sends a RAB ASSIGNMENT RESPONSE message to the CN in an earlier time for RADIO
BEARER setup over the Uu interface.
If the RADIO BEARER setup over the Uu interface fails, the RNC sends a message to the CN
to release the connection over the Iu interface.
Issue 03 (2015-06-30)

2537
BSC6900 UMTS
1. In the existing RAB setup procedure, after receiving an RADIO BEARER SETUP
COMPLETE message from the UE, the RNC sends a RAB ASSIGNMENT RESPONSE
message. In the parallel RAB setup procedure, the RNC sends an RADIO BEARER SETUP
message to the UE to trigger the RADIO BEARER setup procedure, and in addition the RNC
sends a RAB ASSIGNMENT RESPONSE message to the CN at an earlier time.
2. In the existing RAB setup procedure, if the RADIO BEARER setup fails, the RNC sends an
IU RELEASE REQUEST or RAB ASSIGNMENT RESPONSE message to the CN, indicating
the RADIO BEARER setup failure. In the parallel RAB setup procedure, if the RADIO
BEARER setup fails, the RNC sends an IU RELEASE REQUEST message to the CN to release
the connection over the Iu interface.
After the parallel handling of the alerting and RAB setup procedures is introduced, the RAB
setup procedure is illustrated in Figure 2.
Issue 03 (2015-06-30)

2538
BSC6900 UMTS
Figure 1-1088 Flow chart of RAB setup
Issue 03 (2015-06-30)

2539
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.RAB.AttEstabCS.Conv,
VS.RAB.AttEstabCS.Str,
VS.RAB.AttEstabCS.AMR.12.2,
VS.RAB.AttEstCS.AMR.7.95,
VS.RAB.AttEstab.AMR,
VS.RAB.AttEstabCS.AMRWB,
VS.RAB.AttEstCS.Conv.64,
VS.RAB.AttEstabCS.AMRWB23.85,
VS.RAB.AttEstabCS.Platinum,
VS.RAB.AttEstabCS.Conv.Platinum,
VS.RAB.AttEstabCS.FastSetup,
VS.HSPA.RAB.AttEstab.CS.Conv,
VS.RAB.AttEstabCS.VPLimit,
VS.AttEstabCS.AfterP2F,
VS.AttEstabCS.AfterP2D,
VS.RAB.AttEstabCS.CSFB.Redir,
VS.RAB.AttEstabCS.CSFB.PSHO

2540
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.RAB.SuccEstabCS.Conv,
VS.RAB.SuccEstabCS.Str,
VS.RAB.SuccEstabCS.AMR.12.2,
VS.RAB.SuccEstCS.AMR.7.95,
VS.RAB.SuccEstabCS.AMR,
VS.RAB.SuccEstabCS.AMRWB,
VS.RAB.SuccEstCS.Conv.64,
VS.RAB.SuccEstabCS.AMRWB23.85,
VS.RAB.SuccEstabCS.Platinum,
VS.RAB.SuccEstabCS.Conv.Platinum,
VS.RAB.SuccEstabCS.FastSetup,
VS.RAB.SuccEstabCS.Queue,
VS.SuccEstabCS.AfterP2F,
VS.SuccEstabCS.AfterP2D,
VS.RAB.SuccEstabCS.CSFB.Redir,
VS.RAB.SuccEstabCS.CSFB.PSHO,
VS.HSPA.RAB.SuccEstab.CS.Conv
VS.RAB.AttEstabCS.Queue
D~H
See:RAB.EstFailCs.Cell

2541
BSC6900 UMTS
Issue 03 (2015-06-30)

2542
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.RAB.AttEstabCS.Conv,
VS.RAB.AttEstabCS.Str,
VS.RAB.AttEstabCS.AMR.12.2,
VS.RAB.AttEstab.AMR,
VS.RAB.AttEstabCS.AMRWB,
VS.RAB.AttEstCS.Conv.64,
VS.RAB.AttEstabCS.Platinum,
VS.RAB.AttEstabCS.Conv.Platinum,
VS.RAB.AttEstabCS.FastSetup,
VS.HSPA.RAB.AttEstab.CS.Conv,
VS.RAB.AttEstabCS.VPLimit,
VS.AttEstabCS.AfterP2F,
VS.AttEstabCS.AfterP2D,
VS.RAB.AttEstabCS.CSFB.Redir,
VS.RAB.AttEstabCS.CSFB.PSHO

2543
BSC6900 UMTS
Measurement points
Description
VS.RAB.SuccEstabCS.Conv,
VS.RAB.SuccEstabCS.AMR.12.2,
VS.RAB.SuccEstabCS.AMR,
VS.RAB.SuccEstabCS.AMRWB,
VS.RAB.SuccEstCS.Conv.64,
VS.RAB.SuccEstabCS.Platinum,
VS.RAB.SuccEstabCS.Conv.Platinum,
VS.RAB.SuccEstabCS.FastSetup,
VS.RAB.SuccEstabCS.Queue,
VS.SuccEstabCS.AfterP2F,
VS.SuccEstabCS.AfterP2D,
VS.RAB.SuccEstabCS.CSFB.Redir,
VS.RAB.SuccEstabCS.CSFB.PSHO,
VS.HSPA.RAB.SuccEstab.CS.Conv
D~H
See:RAB.EstFailCs.Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179825
VS.RAB.AttEstab
CS.Conv
Number of CS
Conversational RAB
Establishment
Requests for Cell
Earlier than
BSC6900
V900R011
67179826
VS.RAB.AttEstab
CS.Str
Number of CS
Streaming RAB
Establishment
Requests for Cell
Earlier than
BSC6900
V900R011

2544
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179827
VS.RAB.SuccEstab
CS.Conv
Number of
Successful CS
Conversational RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011
67179828
VS.RAB.SuccEstab
CS.Str
Number of
Successful CS
Streaming RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011
67190457
VS.RAB.AttEstab
CS.AMR.12.2
Number of CS
12.2kbit/s AMR
Service RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67190458
VS.RAB.AttEstCS.
AMR.7.95
Number of CS
7.95kbit/s AMR
Service RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67190460
VS.RAB.AttEstCS.
AMR.4.75
Number of CS
4.75kbit/s AMR
Service RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67190461
VS.RAB.SuccEstab
CS.AMR.12.2
Number of
Successful CS
12.2kbit/s AMR
Service RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011
67190462
VS.RAB.SuccEstC
S.AMR.7.95
Number of
Successful CS
7.95kbit/s AMR
Service RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011
67190464
VS.RAB.SuccEstC
S.AMR.4.75
Number of
Successful CS
4.75kbit/s AMR
Service RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011

2545
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179858
VS.RAB.AttEstab.
AMR
Number of CS AMR
Service RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67192120
VS.RAB.AttEstab
CS.AMRWB
Number of CS
Wideband AMR
Service RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67179859
VS.RAB.AttEstCS.
Conv.64
Number of CS
Conversational RAB
Establishment
Attempts for Cell
(Max DL Bit Rate is
64 kbit/s)
Earlier than
BSC6900
V900R011
67179860
VS.RAB.SuccEstab
CS.AMR
Number of
Successful CS AMR
RAB Establishments
for Cell
Earlier than
BSC6900
V900R011
67192121
VS.RAB.SuccEstab
CS.AMRWB
Number of
Successful CS
Wideband AMR
RAB Establishments
for Cell
Earlier than
BSC6900
V900R011
67179861
VS.RAB.SuccEstC
S.Conv.64
Number of
Successful CS RAB
Establishments for
Cell (Max DL Bit
Rate is 64 kbit/s)
Earlier than
BSC6900
V900R011
67196202
VS.HSPA.RAB.Att
Estab.CS.Conv
Number of CS over
HSPA RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67196203
VS.HSPA.RAB.Suc
cEstab.CS.Conv
Number of
Successful CS over
HSPA RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011

2546
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196232
VS.RAB.AttEstab
CS.VPLimit
Number of 64kbit/s
CS RAB Attempts
Initiated in Cell
Where 64kbit/s CS
Conversational
Service is Forbidden
for Cell
Earlier than
BSC6900
V900R011
67204853
VS.HSPA.UE.Mea
n.CS.Conv.Cell
Number of CS over
HSPA Users for Cell
Earlier than
BSC6900
V900R011
73393916
VS.RAB.AttEstab
CS.Queue
Number of Queuing
Attempts Due to
Insufficient
Resource in the CS
RAB Assignment
Establishment
Procedure for Cell
BSC6900
V900R012
73393918
VS.RAB.Estab.Que
ueTime.CS
Average Duration of
a CS Queuing in the
RAB Establishment
Procedure for Cell
BSC6900
V900R012
73393920
VS.RAB.SuccEstab
CS.Queue
Number of
Successful CS
Establishment After
Queuing for Cell
BSC6900
V900R012
73394277
VS.RAB.AttEstab
CS.AMRWB23.85
Number of CS
23.85kbit/s
AMRWB service
RAB establishment
Attempts for cell
BSC6900
V900R012
73394278
VS.RAB.AttEstab
CS.AMRWB23.05
Number of CS
23.05kbit/s
AMRWB service
RAB establishment
Attempts for cell
BSC6900
V900R012
73394279
VS.RAB.AttEstab
CS.AMRWB19.85
Number of CS
19.85kbit/s
AMRWB service
RAB establishment
Attempts for cell
BSC6900
V900R012

2547
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394280
VS.RAB.AttEstab
CS.AMRWB18.25
Number of CS
18.25kbit/s
AMRWB service
RAB establishment
Attempts for cell
BSC6900
V900R012
73394281
VS.RAB.AttEstab
CS.AMRWB15.85
Number of CS
15.85kbit/s
AMRWB service
RAB establishment
Attempts for cell
BSC6900
V900R012
73394282
VS.RAB.AttEstab
CS.AMRWB14.25
Number of CS
14.25kbit/s
AMRWB service
RAB establishment
Attempts for cell
BSC6900
V900R012
73394283
VS.RAB.AttEstab
CS.AMRWB12.65
Number of CS
12.65kbit/s
AMRWB service
RAB establishment
Attempts for cell
BSC6900
V900R012
73394284
VS.RAB.AttEstab
CS.AMRWB8.85
Number of CS
8.85kbit/s AMRWB
service RAB
establishment
Attempts for cell
BSC6900
V900R012
73394285
VS.RAB.AttEstab
CS.AMRWB6.60
Number of CS
6.60kbit/s AMRWB
service RAB
establishment
Attempts for cell
BSC6900
V900R012
73394286
VS.RAB.SuccEstab
CS.AMRWB23.85
Number of CS
23.85kbit/s
AMRWB service
RAB successfully
established for cell
BSC6900
V900R012
73394287
VS.RAB.SuccEstab
CS.AMRWB23.05
Number of CS
23.05kbit/s
AMRWB service
RAB successfully
BSC6900
V900R012

2548
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394288
VS.RAB.SuccEstab
CS.AMRWB19.85
Number of CS
19.85kbit/s
AMRWB service
RAB successfully
BSC6900
V900R012
73394289
VS.RAB.SuccEstab
CS.AMRWB18.25
Number of CS
18.25kbit/s
AMRWB service
RAB successfully
BSC6900
V900R012
73394290
VS.RAB.SuccEstab
CS.AMRWB15.85
Number of CS
15.85kbit/s
AMRWB service
RAB successfully
BSC6900
V900R012
73394291
VS.RAB.SuccEstab
CS.AMRWB14.25
Number of CS
14.25kbit/s
AMRWB service
RAB successfully
BSC6900
V900R012
73394292
VS.RAB.SuccEstab
CS.AMRWB12.65
Number of CS
12.65kbit/s
AMRWB service
RAB successfully
BSC6900
V900R012
73394293
VS.RAB.SuccEstab
CS.AMRWB8.85
Number of CS
8.85kbit/s AMRWB
service RAB
successfully
BSC6900
V900R012
73394294
VS.RAB.SuccEstab
CS.AMRWB6.60
Number of CS
6.60kbit/s AMRWB
service RAB
successfully
BSC6900
V900R012
73425918
VS.RAB.AttEstab
CS.Platinum
Number of CS RAB
Setup Requests for
Platinum UEs for
Cell
BSC6900
V900R015C00

2549
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425919
VS.RAB.SuccEstab
CS.Platinum
Number of
Successful CS RAB
Setups for Platinum
UEs for Cell
BSC6900
V900R015C00
73425920
VS.RAB.AttEstab
CS.Conv.Platinum
Number of CS RAB
Setup Requests for
Platinum UEs
Performing
Conversational
Services for Cell
BSC6900
V900R015C00
73425921
VS.RAB.SuccEstab
CS.Conv.Platinum
Number of
Successful CS RAB
Setups for Platinum
UEs Performing
Conversational
Services for Cell
BSC6900
V900R015C00
73426335
VS.AttEstabCS.Aft
erP2F
Number of CS
Service Setup
UEs During State
Transition from
CELL_PCH or
URA_PCH to
CELL_FACH for
Cell
BSC6900
V900R015C00
73426336
VS.AttEstabCS.Aft
erP2D
Number of CS
Service Setup
UEs During State
Transition from
CELL_PCH or
URA_PCH to
CELL_DCH for Cell
BSC6900
V900R015C00
73426337
VS.SuccEstabCS.A
fterP2F
Number of
Successful CS
Service Setups
Initiated by UEs
During State
Transition from
CELL_PCH or
URA_PCH to
CELL_FACH for
Cell
BSC6900
V900R015C00

2550
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426338
VS.SuccEstabCS.A
fterP2D
Number of
Successful CS
Service Setups
Initiated by UEs
During State
Transition from
CELL_PCH or
URA_PCH to
CELL_DCH for Cell
BSC6900
V900R015C00
73426417
VS.RAB.AttEstab
CS.CSFB.Redir
Number of CS RAB
Setup Requests
Initiated by
Redirection-based
CSFB for Cell
BSC6900
V900R015C01
73426418
VS.RAB.SuccEstab
CS.CSFB.Redir
Number of
Successful CS RAB
Setups Initiated by
Redirection-based
CSFB for Cell
BSC6900
V900R015C01
73426419
VS.RAB.AttEstab
CS.CSFB.PSHO
Number of CS RAB
Setup Requests
Initiated by PSHandover-based
CSFB for Cell
BSC6900
V900R015C01
73426420
VS.RAB.SuccEstab
CS.CSFB.PSHO
Number of
Successful CS RAB
Setups Initiated by
PS-Handover-based
CSFB for Cell
BSC6900
V900R015C01
73427962
VS.RAB.AttEstab
CS.FastSetup
Number of CS RAB
Setup Requests for
Cell (Fast Setup)
BSC6900
V900R016C00
73427963
VS.RAB.SuccEstab
CS.FastSetup
Number of
Successful CS RAB
Setups for Cell (Fast
Setup)
BSC6900
V900R016C00
Issue 03 (2015-06-30)

2551
BSC6900 UMTS
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
VS.RAB.AttEstabCS.Platinum
VS.RAB.AttEstabCS.Conv.Platinum
VS.RAB.SuccEstabCS.Platinum
VS.RAB.SuccEstabCS.Conv.Platinum

Counter
Sub Counter
VS.RAB.AttEstabCS.AMRWB
VS.RAB.AttEstabCS.AMRWB23.85
VS.RAB.SuccEstabCS.AMRWB
VS.RAB.SuccEstabCS.AMRWB23.85
Issue 03 (2015-06-30)

2552
BSC6900 UMTS
Number of CS RAB Setup Requests for Different Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179825
VS.RAB.AttEstabCS.Conv
Number of CS
Conversational RAB
Cell
67179826
VS.RAB.AttEstabCS.Str
RAB Establishment
Requests for Cell
67190457
VS.RAB.AttEstabCS.AMR.
12.2
Number of CS 12.2kbit/s
AMR Service RAB
Cell
67190458
VS.RAB.AttEstCS.AMR.
7.95
AMR Service RAB
Cell
67190460
4.75
AMR Service RAB
Cell
67179858
VS.RAB.AttEstab.AMR
Number of CS AMR Service

RAB Establishment
Attempts for Cell
67192120
VS.RAB.AttEstabCS.AMR
WB
Number of CS Wideband
AMR Service RAB
Cell
67179859
VS.RAB.AttEstCS.Conv.64
Number of CS
Conversational RAB
Cell (Max DL Bit Rate is 64
kbit/s)
73394277
WB23.85
AMRWB service RAB
establishment Attempts for
cell
73394278
WB23.05
AMRWB service RAB
cell

2553
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394279
WB19.85
AMRWB service RAB
cell
73394280
WB18.25
AMRWB service RAB
cell
73394281
WB15.85
AMRWB service RAB
cell
73394282
WB14.25
AMRWB service RAB
cell
73394283
WB12.65
AMRWB service RAB
cell
73394284
WB8.85
AMRWB service RAB
cell
73394285
WB6.60
AMRWB service RAB
cell
73425918
Number of CS RAB Setup

Requests for Platinum UEs
for Cell
73425920
Platinum

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. The counter VS.RAB.AttEstab.AMR only includes narrowband
AMR services. The preceding counters complies with section "8.2 Radio Bearer control
Issue 03 (2015-06-30)

2554
BSC6900 UMTS
Measurement point
ASSIGNMENT REQUEST message from the CN in the CS domain, it measures the
corresponding counter in the best cell according to the type of the service to be set up, user grade,
or maximum rate. The number of CS RAB setup requests for platinum UEs in the best cells is
provided by the VS.RAB.AttEstabCS.Platinum counter.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabCS.Conv
WRFD-010501
VS.RAB.AttEstabCS.Str
WRFD-010502
Streaming QoS Class

2555
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabCS.AMR.
12.2
WRFD-010501
7.95
WRFD-010501
4.75
WRFD-010501
VS.RAB.AttEstab.AMR
WRFD-010501
WB
WRFD-010613

Rate Wide Band)
VS.RAB.AttEstCS.Conv.64
WRFD-010501
WB23.85
WRFD-010613

Rate Wide Band)
WB23.05
WRFD-010613

Rate Wide Band)
WB19.85
WRFD-010613

Rate Wide Band)
WB18.25
WRFD-010613

Rate Wide Band)
WB15.85
WRFD-010613

Rate Wide Band)
WB14.25
WRFD-010613

Rate Wide Band)
WB12.65
WRFD-010613

Rate Wide Band)
WB8.85
WRFD-010613

Rate Wide Band)
WB6.60
WRFD-010613

Rate Wide Band)
WRFD-150204
Platinum
WRFD-150204

2556
BSC6900 UMTS
Number of CS RAB Setup Requests for Cell (Fast Setup)

Counters
Counter ID
Counter Name
Counter Description
73427962
VS.RAB.AttEstabCS.FastSetup

Requests for Cell (Fast
Setup)
Description
This counter measures the number of CS RAB setup requests that use the Fast Radio Bearer
Setup feature in the best cell. This counter applies only to UEs that are not processing any other
services.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.413(v10.10.0).
Measurement point
The measurement is triggered at point A. When the RNC receives a RAB ASSIGNMENT
REQUEST message from the CS CN and determines that the RAB needs to be set up by using
the Fast Radio Bearer Setup feature, this counter is measured in the best cell for the UE if the
UE is not processing any other services.
Issue 03 (2015-06-30)

2557
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabCS.FastSetup
WRFD-160106
Fast Radio Bearer Setup
Number of RAB Setup Attempts for CS HSPA Voice Services

Counters
Counter ID
Counter Name
Counter Description
67196202
VS.HSPA.RAB.AttEstab.C
S.Conv
Number of CS over HSPA

RAB Establishment
Attempts for Cell
Description
This counter provides the number of RAB setup attempts for CS HSPA voice services(including
wideband AMR services and narrowband AMR services) in the serving cell.This counter
complies with section "8.2 Radio Bearer control procedures" in 3GPP TS 25.413(v10.10.0).
Measurement point
ASSIGNMENT REQUEST message from the CN in the CS domain, it assigns a channel
according to the network configuration. In this case, the RNC measures this counter in the serving
cell where the UE camps on if the RAB is set up at an HSPA channel.
Issue 03 (2015-06-30)

2558
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSPA.RAB.AttEstab.C
S.Conv
WRFD-010619

+

2559
BSC6900 UMTS
Number of RAB Setup Attempts for VP Services when VP Call Is Limited

Counters
Counter ID
Counter Name
Counter Description
67196232
VS.RAB.AttEstabCS.VPLimit
Number of 64kbit/s CS RAB

Attempts Initiated in Cell
Where 64kbit/s CS
Conversational Service is
Forbidden for Cell
Description
This counter provides the number of RAB setup requests for VP services when the VP call is
limited in the best cell.This counter complies with section "8.2 Radio Bearer control procedures"
in 3GPP TS 25.413(v10.10.0).
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.
Figure 1-1093 RAB assignment procedure
Issue 03 (2015-06-30)

2560
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabCS.VPLimit
WRFD-020130
Videophone Service
Restriction
Number of CS Service Setup Attempts Initiated by UEs During State Transition

from CELL_PCH or URA_PCH to CELL_FACH for Cell
Counters
Counter ID
Counter Name
Counter Description
73426335
VS.AttEstabCS.AfterP2F

During State Transition from
CELL_FACH for Cell
73426336
VS.AttEstabCS.AfterP2D

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.The preceding counters complies with section "8.2 Radio Bearer
control procedures" in 3GPP TS 25.413(v10.10.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. A UE in the CELL_PCH or
URA_PCH state initiates CS services and transitions to another state. After the RNC receives a
RAB ASSIGNMENT REQUEST message from the CS domain of the CN, the RNC calculates
the number of CS service setup attempts in the best cell of the UE based on the UE state.
Issue 03 (2015-06-30)

2561
BSC6900 UMTS
Figure 1-1094 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.
Issue 03 (2015-06-30)

2562
BSC6900 UMTS
Figure 1-1095 RAB setup procedure initiated by CN RAB assignment requests for UEs in the
CELL_PCH or URA_PCH state
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttEstabCS.AfterP2F
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-010501
WRFD-010502
Streaming QoS Class
VS.AttEstabCS.AfterP2D
Issue 03 (2015-06-30)

2563
BSC6900 UMTS
Number of CS RAB Setup Requests Initiated by Redirection-based CSFB for Cell

Counters
Counter ID
Counter Name
Counter Description
73426417
VS.RAB.AttEstabCS.CSFB.
Redir

Requests Initiated by
Cell
Description
This counter provides the number of CS RAB setup requests that are initiated due to redirectionbased 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.This counter complies with section "8.2 Radio
Bearer control procedures" in 3GPP TS 25.413(v10.10.0).
Measurement point
The measurement is triggered at point D in the following figure. When the RNC receives a RAB
ASSIGNMENT REQUEST message from the CS domain of the CN and the CN sends this
message to initiate a conversational service for a UE during CSFB, this counter is measured in
the best cell for the UE. This counter applies only to the first RAB setup of the UE during CSFB.
The RNC determines that a UE is performing CSFB if either of the following conditions is met:
a)The RRC CONNECTION REQUEST message contains the CSFB Indication information
element (IE). This IE is introduced in 3GPP Release 9.
b)All of following conditions are met:
(1) The RRC CONNECTION REQUEST message contains V860 and meanwhile does not
contain the Pre-redirection info IE. This IE is introduced in 3GPP Release 8.
(2) In the RRC CONNECTION SETUP COMPLETE message, the value of the Support of EUTRA FDD IE is DoesSupportEUTRAFDD, or the value of the Support of E-UTRA TDD IE
is DoesSupportEUTRATDD. The Support of E-UTRA FDD or Support of E-UTRA TDD IE is
in the UE multi-mode/multi-RAT capability IE, which is in the UE radio access capability IE.
(3) When receiving the RRC CONNECTION SETUP COMPLETE message, the RNC starts a
timer, whose length is 10s. The UE initiates a CS service before the timer expires. That is, the
UE sends an INITIAL DIRECT TRANSFER or DIRECT TRANSFER message to the CN, and
the message type is CM Service Request that contains "Mobile originating call establishment or
packet mode connection establishment" or "Emergency call establishment" or the message type
is Paging Response.
Issue 03 (2015-06-30)

2564
BSC6900 UMTS
Figure 1-1096 RAB assignment setup procedure
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

2565
BSC6900 UMTS
Number of CS RAB Setup Requests Initiated by PS-Handover-based CSFB for Cell

Counters
Counter ID
Counter Name
Counter Description
73426419
VS.RAB.AttEstabCS.CSFB.
PSHO

Requests Initiated by PSHandover-based CSFB for
Cell
Description
This counter provides the number of CS RAB setup requests that are initiated due to PShandover-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 each CSFB procedure.This counter
Measurement point
The measurement is triggered at point E, as shown in the figure. When the RNC receives a RAB
ASSIGNMENT REQUEST message from the CS domain of the CN, 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 each CSFB procedure.
Issue 03 (2015-06-30)

2566
BSC6900 UMTS
Figure 1-1097 CS RAB setup procedure initiated by PS-handover-based CSFB
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

2567
BSC6900 UMTS
Number of Successful CS RAB Establishments in the Cell for Different Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179827
v
Conversational RAB
67179828
VS.RAB.SuccEstabCS.Str
Streaming RAB
67190461
VS.RAB.SuccEstabCS.AM
R.12.2
12.2kbit/s AMR Service
RAB Establishments for Cell
67190462
VS.RAB.SuccEstCS.AMR.
7.95
67190464
4.75
67179860
R
AMR RAB Establishments
for Cell
67192121
RWB
Wideband AMR RAB
67179861
VS.RAB.SuccEstCS.Conv.
64
(Max DL Bit Rate is 64 kbit/
s)
73394286
RWB23.85
AMRWB service RAB
successfully established for
cell
73394287
RWB23.05
AMRWB service RAB
cell
73394288
RWB19.85
AMRWB service RAB
cell

2568
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394289
RWB18.25
AMRWB service RAB
cell
73394290
RWB15.85
AMRWB service RAB
cell
73394291
RWB14.25
AMRWB service RAB
cell
73394292
RWB12.65
AMRWB service RAB
cell
73394293
RWB8.85
AMRWB service RAB
cell
73394294
RWB6.60
AMRWB service RAB
cell
73425919
RAB Setups for Platinum
UEs for Cell
73425921
v.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. The counter VS.RAB.SuccEstabCS.AMR only
includes narrowband AMR services. The preceding counters complies with section "8.2 Radio
Bearer control procedures" in 3GPP TS 25.413(v10.10.0).
Measurement point
Issue 03 (2015-06-30)

2569
BSC6900 UMTS
COMPLETE message from the UE, it measures the corresponding counter in the best cell where
the UE camps on according to the service type of the RAB, user grade, or maximum rate if the
RAB is for the CS service. The number of successful CS RAB setups for platinum UEs in the
best cells is provided by the VS.RAB.SuccEstabCS.Platinum counter.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
v
WRFD-010501
WRFD-171202
VS.RAB.SuccEstabCS.Str
WRFD-010502
Streaming QoS Class
R.12.2
WRFD-010501
WRFD-171202

2570
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
7.95
WRFD-010501
WRFD-171202
4.75
WRFD-010501
WRFD-171202
R
WRFD-010501
WRFD-171202
RWB
WRFD-010613

Rate Wide Band)
WRFD-171202

VS.RAB.SuccEstCS.Conv.
64
WRFD-010501
WRFD-171202
RWB23.85
WRFD-010613

Rate Wide Band)
WRFD-171202

RWB23.05
WRFD-010613
WRFD-171202

Rate Wide Band)
RWB19.85
WRFD-010613
WRFD-171202

Rate Wide Band)
RWB18.25
WRFD-010613
WRFD-171202

Rate Wide Band)
RWB15.85
WRFD-010613
WRFD-171202

Rate Wide Band)
RWB14.25
WRFD-010613
WRFD-171202

Rate Wide Band)
RWB12.65
WRFD-010613
WRFD-171202

Rate Wide Band)
RWB8.85
WRFD-010613
WRFD-171202

Rate Wide Band)
Issue 03 (2015-06-30)

2571
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
RWB6.60
WRFD-010613

Rate Wide Band)
WRFD-171202

WRFD-150204
WRFD-171202
v.Platinum
WRFD-150204
WRFD-171202
Number of Successful CS RAB Setups for Cell (Fast Setup)

Counters
Counter ID
Counter Name
Counter Description
73427963
VS.RAB.SuccEstabCS.FastSetup
RAB Setups for Cell (Fast
Setup)
Description
This counter measures the number of CS RABs that are successfully set up by using the Fast
Radio Bearer Setup feature in the best cell. This counter applies only to UEs that are not
processing any other services.This counter complies with section "8.2 Radio Bearer control
Measurement point
The measurement is triggered at point B. When the RNC returns a RAB ASSIGNMENT
RESPONSE message to the CN after receiving a RADIO BEARER SETUP COMPLETE
message from a UE and the RAB was set up by using the Fast Radio Bearer Setup feature, this
counter is measured in the best cell for the UE if the UE is not processing any other services.
Issue 03 (2015-06-30)

2572
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabCS.FastSetup
WRFD-160106
WRFD-171202
Number of Successful CS Establishment After Queuing

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393920
VS.RAB.SuccEstabCS.Que
ue
Establishment After Queuing
for Cell

2573
BSC6900 UMTS
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.This counter complies with section "8.2 Radio Bearer control
Measurement point
During the RAB establishment procedure, the RNC initiates queuing for the CS service if the
cell has insufficient resources for the service. After a period of time, the RNC tries to assign
resources to the service again. The measurement is triggered when the service is successfully
set up after it is queued,as shown of point C in Figure1. The counter is measured in the queued
cells.
Figure 1-1100 Queue procedure for admission failure during the RAB establishment
Formula
None
Unit
None
Issue 03 (2015-06-30)

2574
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabCS.Que
ue
WRFD-010505
WRFD-171202
Number of Successful CS Service Setups Initiated by UEs During State Transition

Counters
Counter ID
Counter Name
Counter Description
73426337
VS.SuccEstabCS.AfterP2F
UEs During State Transition
from CELL_PCH or
for Cell
73426338
VS.SuccEstabCS.AfterP2D
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
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.
Issue 03 (2015-06-30)

2575
BSC6900 UMTS

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
Issue 03 (2015-06-30)

2576
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccEstabCS.AfterP2F
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-171202
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-171202
VS.SuccEstabCS.AfterP2D
Issue 03 (2015-06-30)

2577
BSC6900 UMTS
Number of Successful CS RAB Setups Initiated by Redirection-based CSFB for

Cell
Counters
Counter ID
Counter Name
Counter Description
73426418
VS.RAB.SuccEstabCS.CSF
B.Redir
RAB Setups Initiated by
Cell
Description
This counter measures the number of successful CS RAB setups that are initiated due to
redirection-based CSFB to UMTS from LTE in the best cell. This counter includes those
successfully performed for combined services. This counter together with the
VS.RAB.AttEstabCS.CSFB.Redir counter evaluates the RAB setup success rate of CSFB
services on the UMTS network.This counter complies with section "8.2 Radio Bearer control
Measurement point
The measurement is triggered at point E shown in the following figure when both of the following
conditions are met:
The RNC receives a RADIO BEARER SETUP COMPLETE message from a UE and then sends
a RAB ASSIGNMENT RESPONSE message to the CN. The RAB is for a CS conversational
service, and the UE is performing CSFB. In this case, this counter is measured in the best cell
for the UE. This counter applies only to the first RAB setup of the UE during CSFB. The RNC
determines that a UE is performing CSFB if either of the following conditions is met:
timer, whose length is 10s. The UE succeeded a CS service before the timer expires. That is, the
is Paging Response.
Issue 03 (2015-06-30)

2578
BSC6900 UMTS
Figure 1-1103 RAB assignment setup procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
B.Redir
WRFD-171202

2579
BSC6900 UMTS
Number of Successful CS RAB Setups Initiated by PS-Handover-based CSFB for

Cell
Counters
Counter ID
Counter Name
Counter Description
73426420
B.PSHO
RAB Setups Initiated by PSHandover-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.This counter
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.
Issue 03 (2015-06-30)

2580
BSC6900 UMTS
Figure 1-1104 CS RAB setup procedure initiated by PS-handover-based CSFB
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
B.PSHO
WRFD-171202

2581
BSC6900 UMTS
Number of Successful RAB Setups for CS Conversational Services

Counters
Counter ID
Counter Name
Counter Description
67196203
VS.HSPA.RAB.SuccEstab.
CS.Conv
over HSPA RAB
Description
This counter provides the number of times that the RAB is set up successfully on the HSPA
channels for AMR service(narrowband and wideband AMR services)in the serving cell.This
(v10.10.0).
Measurement point
CN a RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP
COMPLETE message from the UE, it measures the counter in the serving cell where the UE
camps on if the RAB is for the CS conversational service and is carried on an HSPA channel.
Issue 03 (2015-06-30)

2582
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSPA.RAB.SuccEstab.
CS.Conv
WRFD-010619

+
WRFD-171202
Number of Queuing Attempts Due to Insufficient Resource in the CS RAB

Assignment Establishment Procedure
Counters
Counter ID
Counter Name
Counter Description
73393916
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.This counter complies with section "8.2 Radio Bearer
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 enters the queue,as
shown of point A in Figure1. The counter is measured in the queued cells.
Issue 03 (2015-06-30)

2583
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010505

2584
BSC6900 UMTS
Number of CS Over HSPA in a Cell

Counters
Counter ID
Counter Name
Counter Description
67204853
VS.HSPA.UE.Mean.CS.Co
nv.Cell

Users for Cell
Description
This counter provides the average number of CS over HSPA users in the serving cell.This counter
Measurement point
The system periodically samples (sampling periodicity is 5 seconds) the number of CS Over
HSPA users. At the end of a statistical period, the system divides the sampling number by the
sum at each sampling point to obtain the average number of CS Over HSPA users during the
period.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSPA.UE.Mean.CS.Co
nv.Cell
WRFD-010619

+
Average Duration of a CS Queuing in the RAB Establishment Procedure

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393918
VS.RAB.Estab.QueueTime.
CS
Average Duration of a CS
Queuing in the RAB
Establishment Procedure for
Cell

2585
BSC6900 UMTS
specific formulas.
Counter ID
Counter Name
Counter Description
73393966
CS.CUM
Duration of RAB queuing in

CS domain during the RAB
assignment in a cell
(Numerator)
73393967
CS.SAMPLE

CS domain during the RAB
(Denominator)
Description
This counter provides the queuing duration for the queued cells.The preceding counters complies
Measurement point
During the RAB establishment, the RNC initiates queuing for the CS service if the target cell
does not have sufficient resources. After a certain period of time, the RNC attempts to allocate
resources to the service again. If the service is allocated resources before the related timer expires,
this counter measures the queuing duration of this service in the cell where the corresponding
UE currently camps.
Formula
VS.RAB.Estab.QueueTime.CS = [VS.RAB.Estab.QueueTime.CS.CUM]/
[VS.RAB.Estab.QueueTime.CS.SAMPLE]
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
CS
WRFD-010505

2586
BSC6900 UMTS
1.12.31 PS RAB Setup Measurement <per Cell>(RAB.EstabPS.Cell)

Overview
If the RAB succeeds to setup, the RAB setup is measured in the best cell after the RAB setup.
If the RAB fails to setup, the RAB setup is measured in the first DRD attempt cell if the DRD
is performed. The RAB assignment setup is measured in the current best cell if the DRD is not
performed.
The RAB setup procedure is as follows.
Issue 03 (2015-06-30)

2587
BSC6900 UMTS
Issue 03 (2015-06-30)

2588
BSC6900 UMTS

Measurement points
Description
VS.RAB.AttEstabPS.Conv,
VS.RAB.AttEstabPS.Bkg,
VS.RAB.AttEstabPS.Int,
VS.RAB.AttEstabPS.Str,
VS.RAB.AttEstab.PSR99,
VS.RAB.AttEstabPS.PTT,
VS.RAB.AttEstabPS.Free,
VS.RAB.AttEstabPS.Platinum,
VS.RAB.AttEstabPS.FastSetup,
VS.RAB.AttEstabPS.Conv.Platinum,
VS.AttEstabPS.AfterP2F,
VS.AttEstabPS.AfterP2D
VS.RAB.SuccEstabPS.Conv,
VS.RAB.SuccEstabPS.Bkg,
VS.RAB.SuccEstabPS.Int,
VS.RAB.SuccEstabPS.Str,
VS.RAB.SuccEstab.PSR99,
VS.RAB.SuccEstabPS.PTT,
VS.RAB.SuccEstabPS.Free,
VS.RAB.SuccEstabPS.Platinum,
VS.RAB.SuccEstabPS.Conv.Platinum,
VS.RAB.SuccEstabPS.FastSetup,
VS.RAB.SuccEstabPS.0kbps,
VS.RAB.SuccEstabPS.Queue,
VS.SuccEstabPS.AfterP2F,
VS.SuccEstabPS.AfterP2D
VS.RAB.AttEstabPS.Queue
D~H
See:RAB.EstFailPs.Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179924
VS.RAB.AttEstabP
S.Bkg
Number of PS
Background RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011

2589
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179921
VS.RAB.AttEstabP
S.Conv
Number of PS
Conversational RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67179923
VS.RAB.AttEstabP
S.Int
Number of PS
Interactive RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67179922
VS.RAB.AttEstabP
S.Str
Number of PS
Streaming RAB
Establishment
Attempts for Cell
Earlier than
BSC6900
V900R011
67179928
VS.RAB.SuccEstab
PS.Bkg
Number of
Successful PS
Background RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011
67179925
VS.RAB.SuccEstab
PS.Conv
Number of
Successful PS
Conversational RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011
67179927
VS.RAB.SuccEstab
PS.Int
Number of
Successful PS
Interactive RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011
67179926
VS.RAB.SuccEstab
PS.Str
Number of
Successful PS
Streaming RAB
Establishments for
Cell
Earlier than
BSC6900
V900R011
67196301
VS.RAB.SuccEstabPS.0kbps
Number of PS RABs
Established
Successfully at 0
kbit/s in the Best Cell
Earlier than
BSC6900
V900R011
73403808
VS.RAB.SuccEstab
.PSR99
Number of PS R99
RAB successfully
BSC6900
V900R012
73403809
VS.RAB.AttEstab.
PSR99
Number of PS R99
RAB establishment
Attempts for cell
BSC6900
V900R012

2590
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393917
VS.RAB.AttEstabP
S.Queue
Number of Queuing
Attempts Due to
Insufficient
Resource in the PS
RAB Assignment
Establishment
Procedure for Cell
BSC6900
V900R012
73393919
VS.RAB.Estab.Que
ueTime.PS
Average Duration of
a PS Queuing in the
RAB Establishment
Procedure for Cell
BSC6900
V900R012
73393921
VS.RAB.SuccEstab
PS.Queue
Number of
Successful PS
Establishment After
Queuing for Cell
BSC6900
V900R012
73394075
VS.RAB.SuccEstab
PS.PTT
Number of
Successful PTT
Service
Establishments for
Cell
BSC6900
V900R012
73394076
VS.RAB.AttEstabP
S.PTT
Number of PTT
Service
Establishment
Attempts for Cell
BSC6900
V900R012
73423517
VS.RAB.AttEstabP
S.Free
Number of PS Free
RAB Setup Attempts
for Cell
BSC6900
V900R013
73423518
VS.RAB.SuccEstab
PS.Free
Number of
Successful PS Free
RAB Setups for Cell
BSC6900
V900R013
73425923
VS.RAB.SuccEstab
PS.Platinum
Number of
Successful PS RAB
Setups for Platinum
UEs for Cell
BSC6900
V900R015C00
73425924
VS.RAB.AttEstabP
S.Conv.Platinum
Number of PS RAB
Setup Requests for
Platinum UEs
Performing
Conversational
Services for Cell
BSC6900
V900R015C00

2591
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425925
VS.RAB.SuccEstab
PS.Conv.Platinum
Number of
Successful PS RAB
Setups for Platinum
UEs Performing
Conversational
Services for Cell
BSC6900
V900R015C00
73425922
VS.RAB.AttEstabP
S.Platinum
Number of PS RAB
Setup Requests for
Platinum UEs for
Cell
BSC6900
V900R015C00
73426339
VS.AttEstabPS.Aft
erP2F
Number of PS
Service Setup
UEs During State
Transition from
CELL_PCH or
URA_PCH to
CELL_FACH for
Cell
BSC6900
V900R015C00
73426340
VS.AttEstabPS.Aft
erP2D
Number of PS
Service Setup
UEs During State
Transition from
CELL_PCH or
URA_PCH to
CELL_DCH for Cell
BSC6900
V900R015C00
73426341
VS.SuccEstabPS.A
fterP2F
Number of
Successful PS
Service Setups
Initiated by UEs
During State
Transition from
CELL_PCH or
URA_PCH to
CELL_FACH for
Cell
BSC6900
V900R015C00

2592
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426342
VS.SuccEstabPS.A
fterP2D
Number of
Successful PS
Service Setups
Initiated by UEs
During State
Transition from
CELL_PCH or
URA_PCH to
CELL_DCH for Cell
BSC6900
V900R015C00
73427964
VS.RAB.AttEstabP
S.FastSetup
Number of PS RAB
Setup Requests for
Cell (Fast Setup)
BSC6900
V900R016C00
73427965
VS.RAB.SuccEstab
PS.FastSetup
Number of
Successful PS RAB
Setups for Cell (Fast
Setup)
BSC6900
V900R016C00
73430323
VS.RAB.FailEstab
PS.IUPSIntBrd.Ov
erload
Number of PS RAB
Setup Failures
Caused by Iu-PS
Interface Board
Overload for Cell
BSC6900
V900R017C10
73430780
VS.RAB.AttEstabP
S.PSLimit
Number of PS RAB
Setup Requests
Received in Cells
with Restricted PS
Service
BSC6900
V900R017C10
None
Number of PS RAB Setup Requests for Different Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179921
VS.RAB.AttEstabPS.Conv
Number of PS
Conversational RAB
Cell

2593
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67179924
VS.RAB.AttEstabPS.Bkg
RAB Establishment
Attempts for Cell
67179923
VS.RAB.AttEstabPS.Int
RAB Establishment
Attempts for Cell
67179922
VS.RAB.AttEstabPS.Str
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
73425922
VS.RAB.AttEstabPS.Platinum

for Cell
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.The preceding counters complies
with section "8.2 Radio Bearer control procedures" in 3GPP TS 25.413(v10.10.0).
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.
Issue 03 (2015-06-30)

2594
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabPS.Conv
WRFD-010501
VS.RAB.AttEstabPS.Bkg
WRFD-010504
VS.RAB.AttEstabPS.Int
WRFD-010503
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

2595
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabPS.Platinum
WRFD-150204
Number of PS RAB Setup Requests for Cell (Fast Setup)

Counters
Counter ID
Counter Name
Counter Description
73427964
VS.RAB.AttEstabPS.FastSetup

Requests for Cell (Fast
Setup)
Description
This counter measures the number of PS RAB setup requests that use the Fast Radio Bearer
Setup feature in the best cell. This counter applies only to UEs that are not processing any other
services.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.413(v10.10.0).
Measurement point
REQUEST message from the PS CN and determines that the RAB needs to be set up by using
UE is not processing any other services.
Issue 03 (2015-06-30)

2596
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabPS.FastSetup
WRFD-160106
Number of PS RAB Setup Requests for Platinum UEs Performing Conversational

Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73425924
Platinum

Performing Conversational
Services for Cell
Description
This counter measures the number of PS RAB setup requests for platinum UEs performing
conversational services in the best cells.This counter complies with section "8.2 Radio Bearer
Measurement point
The measurement is triggered at point A shown in the figure when the RNC receives from the
PS CN a RAB ASSIGNMENT REQUEST message specific to a platinum UE performing
conversational services. In this case, this counter is measured in the best cell that the UE camps
on.
Issue 03 (2015-06-30)

2597
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Platinum
WRFD-150204

2598
BSC6900 UMTS
Number of PS Service Setup Attempts Initiated by UEs During State Transition

Counters
Counter ID
Counter Name
Counter Description
73426339
VS.AttEstabPS.AfterP2F
Number of PS Service Setup

CELL_FACH for Cell
73426340
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.
Issue 03 (2015-06-30)

2599
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.
Issue 03 (2015-06-30)

2600
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttEstabPS.AfterP2F
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-010501
WRFD-010502
Streaming QoS Class
Issue 03 (2015-06-30)

2601
BSC6900 UMTS
Number of PS RABs Successfully Set Up in a Cell for Different Services

Counters
Counter ID
Counter Name
Counter Description
67179925
Conversational RAB
67179928
VS.RAB.SuccEstabPS.Bkg
Background RAB
67179927
VS.RAB.SuccEstabPS.Int
Interactive RAB
67179926
VS.RAB.SuccEstabPS.Str
Streaming RAB
73403808
VS.RAB.SuccEstab.PSR99

cell
73394075
VS.RAB.SuccEstabPS.PTT

Service Establishments for
Cell
73423518
VS.RAB.SuccEstabPS.Free
Free RAB Setups for Cell
73425923
VS.RAB.SuccEstabPS.Platinum
UEs for Cell
73425925
.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.The preceding counters
Measurement point
Issue 03 (2015-06-30)

2602
BSC6900 UMTS
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.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010501

2603
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabPS.Bkg
WRFD-010504
VS.RAB.SuccEstabPS.Int
WRFD-010503
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
VS.RAB.SuccEstabPS.Free
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.SuccEstabPS.Platinum
WRFD-150204
.Platinum
WRFD-150204
Number of Successful PS RAB Setups for Cell (Fast Setup)

Counters
Counter ID
Counter Name
Counter Description
73427965
VS.RAB.SuccEstabPS.FastSetup
RAB Setups for Cell (Fast
Setup)
Description
This counter measures the number of PS RABs that are successfully set up by using the Fast
Radio Bearer Setup feature in the best cell. This counter applies only to UEs that are not
processing any other services.This counter complies with section "8.2 Radio Bearer control
Measurement point
counter is measured in the best cell for the UE if the UE is not processing any other services.
Issue 03 (2015-06-30)

2604
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabPS.FastSetup
WRFD-160106
Number of PS RABs Set Up Successfully at 0 Kbit/s

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196301
VS.RAB.SuccEstabPS.
0kbps
Number of PS RABs
Established Successfully at 0
kbit/s in the Best Cell

2605
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 best cell during the procedures of RAB establishment, RAB
modification, cell update, incoming inter-RAT handover, relocation (UE involved) and hard
handover.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP
TS 25.413(v10.10.0).
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.
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.
Issue 03 (2015-06-30)

2606
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 best cell if the rate of the RAB is 0 Kbit/s.
Figure 1-1117 P2D procedure
The measurement is triggered at point A as shown in the following figure 4. During a relocation
(UE involved) procedure, when the RNC sends a RELOCATION COMPLETE message to CN,
it measures this counter in the best cell if the rate of the RAB is 0 Kbit/s.
Figure 1-1118 relocation (UE involved) procedure
The measurement is triggered at point A as shown in the following figure 5. During a hard
handover procedure, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from UE, it measures this counter in the best cell if the rate of the RAB
is 0 Kbit/s.
Issue 03 (2015-06-30)

2607
BSC6900 UMTS
Figure 1-1119 hard handover procedure
The measurement is triggered at point D as shown in the following figure 6. During a incoming
inter-RAT handover procedure, when the TRNC sends a RELOCATION COMPLETE message
to CN, it measures this counter in the best cell if the rate of the RAB is 0 Kbit/s.
Figure 1-1120 incoming inter-RAT handover procedure
Issue 03 (2015-06-30)

2608
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabPS.
0kbps
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Successful PS Establishment After Queuing

Counters
Counter ID
Counter Name
Counter Description
73393921
VS.RAB.SuccEstabPS.Queu
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.This counter complies with section "8.2 Radio Bearer control
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 is successfully
set up after it is queued,as shown of point C in Figure1. The counter is measured in the queued
cells.
Issue 03 (2015-06-30)

2609
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.SuccEstabPS.Queu
e
WRFD-010505

2610
BSC6900 UMTS
Number of Successful PS Service Setups Initiated by UEs During State Transition

Counters
Counter ID
Counter Name
Counter Description
73426341
VS.SuccEstabPS.AfterP2F
from CELL_PCH or
for Cell
73426342
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.The preceding counters complies with section
"8.2 Radio Bearer control procedures" in 3GPP TS 25.413(v10.10.0).
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
Issue 03 (2015-06-30)

2611
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
Issue 03 (2015-06-30)

2612
BSC6900 UMTS
Figure 1-1123 RAB setup procedure initiated by CN RAB assignment request for UEs in the
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SuccEstabPS.AfterP2F
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-010503
WRFD-010504

2613
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-010503
WRFD-010504
Number of Queuing Attempts Due to Insufficient Resource in the PS RAB

Assignment Establishment Procedure
Counters
Counter ID
Counter Name
Counter Description
73393917
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.This counter complies with section "8.2 Radio Bearer
Measurement point
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.
Issue 03 (2015-06-30)

2614
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010505

2615
BSC6900 UMTS
Average Duration of a PS Queuing in the RAB Establishment Procedure

Counters
Counter ID
Counter Name
Counter Description
73393919
PS
Average Duration of a PS
Queuing in the RAB
Establishment Procedure for
Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73393968
PS.CUM

PS domain during the RAB
(Numerator)
73393969
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.The preceding counters complies with section
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
Issue 03 (2015-06-30)

2616
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
PS
WRFD-010505
Number of PS RAB Setup Failures Caused by Iu-PS Interface Board Overload for
Cell
Counters
Counter ID
Counter Name
Counter Description
73430323
VS.RAB.FailEstabPS.IUPSI
ntBrd.Overload

Failures Caused by Iu-PS
Interface Board Overload for
Cell
Description
This counter provides the number of PS RAB setup failures caused by Iu-PS interface board
overload in the best cell. This counter complies with 3GPP TS 25.413 (V11.3.0). For details
about this counter, see section 8.2 "RAB Assignment" in this TS.
Measurement point
The measurement is triggered at point A in the following figure. When the RNC sends the CN
a RAB ASSIGNMENT RESPONSE message, indicating that a PS RAB fails to set up because
of Iu-PS interface board overload, this counter is measured in the best cell for the UE.
Figure 1-1125 RAB setup procedure (failed operation)
Issue 03 (2015-06-30)

2617
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabPS.IUPSI
ntBrd.Overload
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RAB Setup Requests Received in Cells with Restricted PS Service

Counters
Counter ID
Counter Name
Counter Description
73430780
VS.RAB.AttEstabPS.PSLimit

Requests Received in Cells
with Restricted PS Service
Description
This counter measures the number of PS RAB setup requests received in the best cell when the
PS service is restricted.
Measurement point
The measurement is triggered at point A in the following figure. When the RNC receives from
the PS domain of the CN a RAB ASSIGNMENT REQUEST message, this counter is measured
in the best cell if at least one cell in the active set for the UE has PS service restricted.
Issue 03 (2015-06-30)

2618
BSC6900 UMTS
Figure 1-1126 RAB assignment procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstabPS.PSLimit
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2619
BSC6900 UMTS
1.12.32 CS RAB Setup Failure Measurement <per Cell>

(RAB.EstFailCs.Cell)
Overview
performed.
The RAB setup procedure is illustrated in Figure 1.
After the parallel handling of the alerting and RAB setup procedures is introduced, the RNC
sends a RAB ASSIGNMENT RESPONSE message to the CN in an earlier time for RADIO
BEARER setup procedure over the Uu interface. The RADIO BEARER setup procedure over
the Uu interface remains unchanged. If the RADIO BEARER setup over the Uu interface fails,
the RNC sends a message to the CN to release the connection over the Iu interface.
1. In the existing RAB setup procedure, after receiving an RADIO BEARER SETUP
COMPLETE message from the UE, the RNC sends a RAB ASSIGNMENT RESPONSE
message. In the parallel RAB setup procedure, the RNC sends an RADIO BEARER SETUP
message to the UE to trigger the RADIO BEARER setup procedure, and in addition the RNC
sends a RAB ASSIGNMENT RESPONSE message to the CN at an earlier time.
2. In the existing RAB setup procedure, if the RADIO BEARER setup fails, the RNC sends an
IU RELEASE REQUEST or RAB ASSIGNMENT RESPONSE message to the CN, indicating
the RADIO BEARER setup failure. In the parallel RAB setup procedure, if the RADIO
BEARER setup fails, the RNC sends an IU RELEASE REQUEST message to the CN to release
the connection over the Iu interface.
After the parallel handling of the alerting and RAB setup procedures is introduced, the RAB
setup procedure is illustrated in Figure 2.
Issue 03 (2015-06-30)

2620
BSC6900 UMTS
Issue 03 (2015-06-30)

2621
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
A~B
See:RAB.EstabCS.Cell
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.DLIUCSBand.Cong,
VS.RAB.FailEstabCS.ULIUCSBand.Cong,
VS.RAB.FailEstabCS.Unsp
VS.RAB.FailEstabCS.TNL
VS.RAB.FailEstabCS.IubFail,
VS.RAB.FailEstabCS.NodeBULCE.Cong,
VS.RAB.FailEstabCS.NodeBDLCE.Cong
VS.RAB.FailEstabCS.IubAAL2Fail
VS.RAB.FailEstabCS.UuFail,
VS.RAB.FailEstabCS.UuFail.CSFB,
VS.RAB.FailEstabCS.RBIncCfg,
VS.RAB.FailEstabCS.RBCfgUnsup,
VS.RAB.FailEstabCS.UuNoReply,
VS.RAB.FailEstabCS.PhyChFail,
VS.RAB.FailEstabCS.SRBReset,
VS.RAB.FailEstabCS.CellUpd,
VS.RAB.FailEstabCS.SRBReset.CSFB,
VS.RAB.FailEstabCS.CellUpd.CSFB
VS.RAB.FailEstabCS.RNL

2622
BSC6900 UMTS
Issue 03 (2015-06-30)

2623
BSC6900 UMTS

Measurement points
Description
A~B
See:RAB.EstabCS.Cell
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.DLIUCSBand.Cong,
VS.RAB.FailEstabCS.ULIUCSBand.Cong,
VS.RAB.FailEstabCS.IubFail,
VS.RAB.FailEstabCS.NodeBULCE.Cong,
VS.RAB.FailEstabCS.UuFail,
VS.RAB.FailEstabCS.UuFail.CSFB,
VS.RAB.FailEstabCS.RBIncCfg,
VS.RAB.FailEstabCS.RBCfgUnsup,
VS.RAB.FailEstabCS.UuNoReply,
VS.RAB.FailEstabCS.PhyChFail,
VS.RAB.FailEstabCS.SRBReset,
VS.RAB.FailEstabCS.CellUpd,
VS.RAB.FailEstabCS.SRBReset.CSFB,
VS.RAB.FailEstabCS.CellUpd.CSFB
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189494
VS.RAB.FailEstab
CS.Cong
Number of Failed CS
RAB Establishments
Earlier than
BSC6900
V900R011

2624
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189495
VS.RAB.FailEstab
CS.RNL
Number of Failed CS
RAB Establishments
for Cell (Radio
Network Layer
Cause)
Earlier than
BSC6900
V900R011
67189496
VS.RAB.FailEstab
CS.TNL
Number of Failed CS
RAB Establishments
for Cell
(Transmission
Network Layer
Cause)
Earlier than
BSC6900
V900R011
67192610
VS.RAB.FailEstab
CS.DLIUBBand.C
ong
Number of Failed CS
RAB Establishments
for Cell (DL Iub
Bandwidth
Congestion)
Earlier than
BSC6900
V900R011
67192611
VS.RAB.FailEstab
CS.ULIUBBand.C
ong
Number of Failed CS
RAB Establishments
for Cell (UL Iub
Bandwidth
Congestion)
Earlier than
BSC6900
V900R011
67190406
VS.RAB.FailEstab
CS.ULCE.Cong
Number of Failed CS
RAB Establishments
for Cell (UL CE
Congestion)
Earlier than
BSC6900
V900R011
67190407
VS.RAB.FailEstab
CS.DLCE.Cong
Number of Failed CS
RAB Establishments
for Cell (DL CE
Congestion)
Earlier than
BSC6900
V900R011
67179864
VS.RAB.FailEstab
CS.Code.Cong
Number of Failed CS
RAB Establishments
for Cell (Code
Congestion)
Earlier than
BSC6900
V900R011
67193536
VS.RAB.FailEstab
CS.RBIncCfg
Number of Failed CS
RAB Establishments
for Cell(Invalid
configuration of UE
during the RB setup
procedure)
BSC6900
V900R012

2625
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193537
VS.RAB.FailEstab
CS.RBCfgUnsup
Number of Failed CS
RAB Establishments
for Cell
(Configuration
unsupported of UE
during the RB setup
procedure)
BSC6900
V900R012
67193539
VS.RAB.FailEstab
CS.UuNoReply
Number of Failed CS
RAB Establishments
for Cell(No reply of
UE during the RB
setup procedure)
BSC6900
V900R012
67193538
VS.RAB.FailEstab
CS.PhyChFail
Number of Failed CS
RAB Establishments
for Cell(Physical
channel failure of UE
during the RB setup
procedure)
BSC6900
V900R012
67193611
VS.RAB.FailEstab
CS.ULPower.Cong
Number of Failed CS
RAB Establishments
for Cell (UL Power
Congestion)
BSC6900
V900R012
67193612
VS.RAB.FailEstab
CS.DLPower.Cong
Number of Failed CS
RAB Establishments
for Cell (DL Power
Congestion)
BSC6900
V900R012
73393835
VS.RAB.FailEstab
CS.IubFail
Number of Failed CS
RAB Establishments
for cell (Radio Link
Configuration
Failure)
BSC6900
V900R012
73393836
VS.RAB.FailEstab
CS.UuFail
Number of Failed CS
RAB Establishments
for cell (Uu Interface
Configuration
Failure)
BSC6900
V900R012
67179830
VS.RAB.FailEstab
CS.Unsp
Number of Failed CS
RAB Establishments
for Cell
(Unsupported
Capabilities)
Earlier than
BSC6900
V900R011

2626
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424884
VS.RAB.FailEstab
CS.SRBReset
Number of Failed CS
RAB Establishments
for Cell (Signaling
RLC Reset)
BSC6900
V900R014
73424885
VS.RAB.FailEstab
CS.CellUpd
Number of Failed CS
RAB Establishments
for Cell (Concurrent
Procedures)
BSC6900
V900R014
73428176
VS.RAB.FailEstab
CS.NodeBULCE.C
ong
Number of Failed CS
RAB Setups due to
NodeB UL CE
Congestion for Cell
BSC6900
V900R016C00
73428177
VS.RAB.FailEstab
CS.NodeBDLCE.C
ong
Number of Failed CS
RAB Setups due to
NodeB DL CE
Congestion for Cell
BSC6900
V900R016C00
73428180
VS.RAB.FailEstab
CS.DLIUCSBand.
Cong
Number of CS RAB
Setup Failures
Caused by DL Iu-CS
Congestion for Cell
BSC6900
V900R016C00
73428181
VS.RAB.FailEstab
CS.ULIUCSBand.
Cong
Number of CS RAB
Setup Failures
Caused by UL Iu-CS
Congestion for Cell
BSC6900
V900R016C00
73428182
VS.RAB.FailEstab
CS.IubAAL2Fail
Number of CS RAB
Setup Failures
Caused by Iub
Transport Bearer
Establishment
Failures for Cell
BSC6900
V900R016C00
73428673
VS.RAB.FailEstab
CS.SRBReset.CSF
B
Number of Failed CS
RAB Establishments
for CSFB UEs for
Cell (Signaling RLC
Reset)
BSC6900
V900R016C00
73428674
VS.RAB.FailEstab
CS.CellUpd.CSFB
Number of Failed CS
RAB Establishments
for CSFB UEs for
Cell (Concurrent
Procedures)
BSC6900
V900R016C00

2627
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428675
VS.RAB.FailEstab
CS.UuFail.CSFB
Number of Failed CS
RAB Establishments
for CSFB UEs for
Cell (Uu Interface
Configuration
Failure)
BSC6900
V900R016C00
When the RAB_RELATED_COUNTER_OPT_SWITCH parameter in the SET
URRCTRLSWITCH command is set to 0, the inclusion relationship between counters is defined
below.
Counter
Sub Counter
VS.RAB.FailEstabCS.ULIUBBand.Cong
VS.RAB.FailEstabCS.DLIUBBand.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.ULIUCSBand.Cong
VS.RAB.FailEstabCS.DLIUCSBand.Cong
VS.RAB.FailEstabCS.UuFail
VS.RAB.FailEstabCS.SRBReset
VS.RAB.FailEstabCS.CellUpd
VS.RAB.FailEstabCS.Cong
Issue 03 (2015-06-30)

2628
BSC6900 UMTS
Counter
Sub Counter
VS.RAB.FailEstabCS.NodeBULCE.Cong
VS.RAB.FailEstabCS.RBIncCfg
VS.RAB.FailEstabCS.RBCfgUnsup
VS.RAB.FailEstabCS.PhyChFail
VS.RAB.FailEstabCS.UuNoReply

below.
Counter
Sub Counter
VS.RAB.FailEstabCS.SRBReset
VS.RAB.FailEstabCS.NodeBULCE.Cong
Issue 03 (2015-06-30)

2629
BSC6900 UMTS
Number of CS RABs Unsuccessfully Established due to Congestion

Counters
Counter ID
Counter Name
Counter Description
67189494
Number of Failed CS RAB

(Congestion)
67192610
VS.RAB.FailEstabCS.DLIU
BBand.Cong

Establishments for Cell (DL
Iub Bandwidth Congestion)
67192611
VS.RAB.FailEstabCS.ULIU
BBand.Cong

Establishments for Cell (UL
67190406
VS.RAB.FailEstabCS.ULC
E.Cong

CE Congestion)
67190407
VS.RAB.FailEstabCS.DLC
E.Cong

CE Congestion)
67179864
VS.RAB.FailEstabCS.Code.
Cong

(Code Congestion)
67193611
VS.RAB.FailEstabCS.ULPo
wer.Cong

Power Congestion)
67193612
VS.RAB.FailEstabCS.DLPo
wer.Cong

Power Congestion)
73428180
CSBand.Cong

Failures Caused by DL Iu-CS
Congestion for Cell
73428181
CSBand.Cong

Failures Caused by UL Iu-CS
Congestion for Cell
Description
These counters provide the number of CS RABs that fail to be set up due to downlink resource
congestion over the Iu-CS interface. These counters are measured in the best cell for a UE. If
congestion occurs both in the uplink and downlink, these counters are 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
Issue 03 (2015-06-30)

2630
BSC6900 UMTS
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.The preceding counters complies
Measurement point
The measurement is triggered at point B as shown in the following figure. After receiving from
the CN a RAB ASSIGNMENT REQUEST message, which requests the setup of a CS RAB, 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 one of the following: "No Radio Resources Available in
Target cell", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for
UL not Available", "Requested Maximum Bit Rate for DL not Available", or "Tqueuing Expiry".
In this case, the RNC measures this counter based on the specific cause in the best cell for the
UE.
The measurement scope of the preceding counters can be changed using the
RAB_RELATED_COUNTER_OPT_SWITCH parameter in the SET URRCTRLSWITCH
command. When this parameter is set to 1, these counters are not incremented when a RAB
ASSIGNMENT RESPONSE message includes the cause value of "No resource available".
Formula
None
Issue 03 (2015-06-30)

2631
BSC6900 UMTS
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
BBand.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
BBand.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabCS.ULC
E.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabCS.DLC
E.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabCS.Code.
Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabCS.ULPo
wer.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2632
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabCS.DLPo
wer.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
CSBand.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
CSBand.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Failed CS RABs due to Unsupported Capabilities (Cell)

Counters
Counter ID
Counter Name
Counter Description
67179830

(Unsupported Capabilities)
Description
This counter provides the number of failed CS RABs due to unsupported capabilities in the best
cell.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.413(v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. If a CS RAB fails to
be set up due to capability insufficiency, the RNC sends a RAB ASSIGNMENT RESPONSE
message to the CN, indicating the CS RAB setup failure. This counter is measured in the best
cell for a UE.
URRCTRLSWITCH command is set to 0, the common example of capability insufficiency is
license unavailability or radio resource insufficiency, the failure cause is "Requested Traffic
Class not Available", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit
Rate for DL not Available", "Requested Maximum Bit Rate for UL not Available", "Requested
Issue 03 (2015-06-30)

2633
BSC6900 UMTS
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".
When this parameter is set to 1, the common example of capability insufficiency is license
unavailability, the failure cause is "Requested Traffic Class not Available", "Requested
Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available",
"Requested Guaranteed Bit Rate for UL not Available", "Requested Transfer Delay not
Achievable".
Formula
None
Unit
None
Issue 03 (2015-06-30)

2634
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of CS RABs Unsuccessfully Established due to Transport Network Layer

Cause
Counters
Counter ID
Counter Name
Counter Description
67189496

(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.This counter complies
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.
Issue 03 (2015-06-30)

2635
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2636
BSC6900 UMTS
Number of Failed CS RAB Establishments Due to Radio Link Configuration

Failure
Counters
Counter ID
Counter Name
Counter Description
73393835
VS.RAB.FailEstabCS.IubFail

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.This counter complies
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-1132 Failed RAB establishments due to radio link configuration failure
Issue 03 (2015-06-30)

2637
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.
Issue 03 (2015-06-30)

2638
BSC6900 UMTS
Figure 1-1134 Timeout for a RADIO LINK RESTORE INDICATION message after receiving
a RADIO LINK FAIL INDICATION message
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabCS.IubFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2639
BSC6900 UMTS
Number of Failed CS RAB Setups due to NodeB CE Congestion for Cell

Counters
Counter ID
Counter Name
Counter Description
73428176
VS.RAB.FailEstabCS.Node
BULCE.Cong

Setups due to NodeB UL CE
Congestion for Cell
73428177
BDLCE.Cong

Setups due to NodeB DL CE
Congestion for Cell
Description
These counters measure the number of CS RAB establishment failures caused by NodeB uplink
or downlink CE congestion in a cell. These counters are measured in the best cell for UEs.The
preceding counters complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.413(v10.10.0).
Measurement point
The measurement is triggered at point B in figure 1. When the RNC receives a RAB
ASSIGNMENT REQUEST message from the CN, which requests the setup of a CS RAB, the
RNC applies for related radio resources and initiate an RL reconfiguration procedure (or RL
establishment procedure). If the RNC receives an RL reconfiguration failure message (or RL
establishment failure message) with a cause value indicating uplink or downlink CE congestion,
the RNC sends a RAB ASSIGNMENT RESPONSE message to the CN and the RAB setup fails.
The cause values indicating uplink CE congestion are
"UL_RADIO_RESOURCES_NOT_AVAILABLE" and "CELL_SYN_NOT_SUPP". The
cause values indicating downlink CE congestion are
"DL_RADIO_RESOURCES_NOT_AVAILABLE" and "CELL_SYN_ADJ_NOT_SUPP".
These counters are separately measured in the uplink and downlink of the best cell.
Issue 03 (2015-06-30)

2640
BSC6900 UMTS
Figure 1-1135 RAB setup failure procedure (due to NodeB CE resource congestion)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
BULCE.Cong
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2641
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
BDLCE.Cong
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of CS RAB Setup Failures Caused by Iub Transport Bearer Establishment

Failures for Cell
Counters
Counter ID
Counter Name
Counter Description
73428182
VS.RAB.FailEstabCS.IubA
AL2Fail

Failures Caused by Iub
Transport Bearer
Establishment Failures for
Cell
Description
This counter measures the number of CS RABs that fail to be set up due to Iub transport bearer
establishment failures. It is measured in the best cell for a UE.This counter complies with section
Measurement point
The measurement is triggered at point B as shown in the following figure. During the setup of
a CS RAB, if the AAL2 transport bearer fails to be set up over the Iub interface, the RNC sends
a RAB ASSIGNMENT RESPONSE message to the CN, indicating the CS RAB setup failure.
This counter is measured in the best cell for the UE.
Issue 03 (2015-06-30)

2642
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabCS.IubA
AL2Fail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2643
BSC6900 UMTS
Number of Failed CS RAB Establishments Due to Uu Interface Configuration

Failure
Counters
Counter ID
Counter Name
Counter Description
73393836

Establishments for cell (Uu
Interface Configuration
Failure)
73428675
VS.RAB.FailEstabCS.UuFa
il.CSFB

Establishments for CSFB
UEs for Cell (Uu Interface
Configuration Failure)
Description
This counter provides the number of times that a CS RAB establishment fails due to
configuration failure on the Uu interface (UE no response or UE returns a failure message).The
25.413(v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
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.
VS.RAB.FailEstabCS.UuFail.CSFB

Established due to CSFB UE configuration
failures (no response is received from the
CSFB UE or the CSFB 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.

2644
BSC6900 UMTS
Measurement point
it requests related radio resources and triggers a Uu interface configuration procedure. This
counter is measured in the best cell that the UE camps on when a RB configuration failure
message is received.
Figure 1-1137 Failed RAB establishment due to Uu interface configuration failure
it requests related radio resources and triggers a Uu interface configuration procedure. This
counter is measured in the best cell that the UE camps on when the UE response times out.
Issue 03 (2015-06-30)

2645
BSC6900 UMTS
Figure 1-1138 Failed RAB establishments due to UE response times out
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-171202

VS.RAB.FailEstabCS.UuFa
il.CSFB
WRFD-140224
WRFD-140102
WRFD-171202

RIM
LTE Emergency Calls
Issue 03 (2015-06-30)

2646
BSC6900 UMTS
Number of CS RABs Unsuccessfully Established due to Different Reasons of UE

During the RB Setup Procedure for Cell
Counters
Counter ID
Counter Name
Counter Description
67193536
VS.RAB.FailEstabCS.RBIn
cCfg

(Invalid configuration of UE
during the RB setup
procedure)
67193537
VS.RAB.FailEstabCS.RBCf
gUnsup

(Configuration unsupported
of UE during the RB setup
procedure)
67193539

Establishments for Cell(No
reply of UE during the RB
setup procedure)
67193538
VS.RAB.FailEstabCS.PhyC
hFail

(Physical channel failure of
UE during the RB setup
procedure)
Description
These measurement item provide the number of CS RABs unsuccessfully established due to
different reason of UE during the RB setup procedure in the best cell.The preceding counters
Issue 03 (2015-06-30)
Counter Name
Description

Established due to invalid configuration of
UE during the RB Setup Procedure

Established due to configuration unsupported
of UE During the RB Setup Procedure

Established due to no reply during the RB
Setup Procedure

2647
BSC6900 UMTS
Counter Name
Description

Established due to physical channel failure of
Measurement point
RAB ASSIGNMENT RESPONSE message indicating that the operation fails, the RNC
measures the VS.RAB.FailEstabCS.RBIncCfg, VS.RAB.FailEstabCS.RBCfgUnsupp, and
VS.RAB.FailEstabCS.PhyChFail counters in the best cell that the UE camps on based on the
failure causes contained in the RADIO BEARER SETUP FAILURE message.
measures the VS.RAB.FailEstabCS.UuNoReply counter 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.
Issue 03 (2015-06-30)

2648
BSC6900 UMTS
Figure 1-1140 RAB setup procedure (UE response timeouts)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabCS.RBIn
cCfg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-171202
Issue 03 (2015-06-30)

2649
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabCS.RBCf
gUnsup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-171202

WRFD-010510
WRFD-171202
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabCS.PhyC
hFail
WRFD-010510
WRFD-171202
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Failed CS RAB Establishments for Cell (Signaling RLC Reset)

Counters
Counter ID
Counter Name
Counter Description
73424884
VS.RAB.FailEstabCS.SRB
Reset

(Signaling RLC Reset)
73428673
Reset.CSFB

UEs for Cell (Signaling RLC
Reset)
Description
This counter provides the number of times that a CS RAB establishment fails due to signaling
RLC reset.The preceding counters complies with section "8.2 Radio Bearer control procedures"
in 3GPP TS 25.413(v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure, when a signaling RLC resets
during the RB setup procedure, the RNC sends the CN a RAB ASSIGNMENT RESPONSE
message, indicating that the RAB setup fails. In this case, this counter is measured in the best
cell where the UE camps.
Issue 03 (2015-06-30)

2650
BSC6900 UMTS
Figure 1-1141 RAB setup procedure(Signaling RLC Reset)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Reset
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-171202

Reset.CSFB
WRFD-140224
WRFD-140102
WRFD-171202

RIM
LTE Emergency Calls
Issue 03 (2015-06-30)

2651
BSC6900 UMTS
Number of Failed CS RAB Establishments for Cell (Concurrent Procedures)

Counters
Counter ID
Counter Name
Counter Description
73424885

(Concurrent Procedures)
73428674
VS.RAB.FailEstabCS.CellU
pd.CSFB

UEs for Cell (Concurrent
Procedures)
Description
This counter provides the number of times that a CS RAB establishment fails due to RB Setup
and Cell Update Overlap.The preceding counters complies with section "8.2 Radio Bearer
Measurement point
The measurement is triggered at point B shown in the following figure. When the RAB setup
fails due to the overlap of the 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 where the UE camps.
Figure 1-1142 RAB setup procedure(RB Setup and Cell Update Overlap)
Issue 03 (2015-06-30)

2652
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-171202

VS.RAB.FailEstabCS.CellU
pd.CSFB
WRFD-140224
WRFD-140102
WRFD-171202

RIM
LTE Emergency Calls
Number of Failed CS RABs due to Radio Network Layer Cause

Counters
Counter ID
Counter Name
Counter Description
67189495

Cause)
Description
This counter provies the number of failed CS RABs due to the radio network layer cause in the
best cell.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.413(v10.10.0).
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 counter in the best cell that the UE camps on.
Issue 03 (2015-06-30)

2653
BSC6900 UMTS
The measurement is triggered at point B as shown in the figure. the RNC receives the IU
RELEASE COMMAND message from the CN at point B during the RAB establishment process.
In this case, the RNC measures each counter in the best cell that the UE camps on.
Figure 1-1144 RAB ASSIGN IU REL procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

2654
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-171202
1.12.33 PS RAB Setup Failure Measurement <per Cell>

(RAB.EstFailPs.Cell)
Overview
performed.
The RAB setup procedure is as follows.
Issue 03 (2015-06-30)

2655
BSC6900 UMTS
Issue 03 (2015-06-30)

2656
BSC6900 UMTS

Measurement points
Description
A~B
See:RAB.EstabPS.Cell
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.DLIUPSBand.Cong,
VS.RAB.FailEstabPS.ULIUPSBand.Cong,
VS.RAB.FailEstabPS.ULCE.FinalCong,
VS.RAB.FailEstabPS.Unsp,
VS.RAB.FailEstabPS.DLPower.Cong.Free
VS.RAB.FailEstabPS.TNL
VS.RAB.FailEstabPS.IubFail,
VS.RAB.FailEstabPS.NodeBULCE.Cong,
VS.RAB.FailEstabPS.NodeBDLCE.Cong
VS.RAB.FailEstabPS.IubAAL2Fail
VS.RAB.FailEstabPS.UuFail,
VS.RAB.FailEstabPS.RBIncCfg,
VS.RAB.FailEstabPS.RBCfgUnsupp,
VS.RAB.FailEstabPS.UuNoReply,
VS.RAB.FailEstabPS.PhyChFail,
VS.RAB.FailEstabPS.SRBReset,
VS.RAB.FailEstabPS.CellUpd
VS.RAB.FailEstabPS.RNL
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192612
VS.RAB.FailEstab
PS.DLIUBBand.Co
ng
Number of Failed PS
RAB Establishments
for Cell (DL Iub
Bandwidth
Congestion)
Earlier than
BSC6900
V900R011

2657
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192613
VS.RAB.FailEstab
PS.ULIUBBand.Co
ng
Number of Failed PS
RAB Establishments
for Cell (UL Iub
Bandwidth
Congestion)
Earlier than
BSC6900
V900R011
67189556
VS.RAB.FailEstab
PS.RNL
Number of Failed PS
RAB Establishments
for Cell (Radio
Network Layer
Cause)
Earlier than
BSC6900
V900R011
67189557
VS.RAB.FailEstab
PS.TNL
Number of Failed PS
RAB Establishments
for Cell (Transport
Network Layer
Cause)
Earlier than
BSC6900
V900R011
67190408
VS.RAB.FailEstab
PS.ULCE.Cong
Number of Failed PS
RAB Establishments
for Cell (UL CE
Congestion)
BSC6900
V900R015C00
67190409
VS.RAB.FailEstab
PS.DLCE.Cong
Number of Failed PS
RAB Establishments
for Cell (DL CE
Congestion)
Earlier than
BSC6900
V900R011
67179967
VS.RAB.FailEstab
PS.Code.Cong
Number of Failed PS
RAB Establishments
for Cell (Code
Congestion)
Earlier than
BSC6900
V900R011
67193540
VS.RAB.FailEstab
PS.RBIncCfg
Number of Failed PS
RAB Establishments
for Cell (UU
interface invalid
configuration)
BSC6900
V900R012
67193541
VS.RAB.FailEstab
PS.RBCfgUnsupp
Number of Failed PS
RAB Establishments
for Cell
(Configuration
unsupported of UE
during the RB setup
procedure)
BSC6900
V900R012

2658
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193543
VS.RAB.FailEstab
PS.UuNoReply
Number of Failed PS
RAB Establishments
for Cell (No reply of
UE during the RB
setup procedure)
BSC6900
V900R012
67193542
VS.RAB.FailEstab
PS.PhyChFail
Number of Failed PS
RAB Establishments
for Cell (Physical
channel failure of UE
during the RB setup
procedure)
BSC6900
V900R012
67193613
VS.RAB.FailEstab
PS.ULPower.Cong
Number of Failed PS
RAB Establishments
for Cell (UL Power
Congestion)
BSC6900
V900R012
67193614
VS.RAB.FailEstab
PS.DLPower.Cong
Number of Failed PS
RAB Establishments
for Cell (DL Power
Congestion)
BSC6900
V900R012
73393837
VS.RAB.FailEstab
PS.IubFail
Number of Failed PS
RAB Establishments
Due to Radio Link
Configuration
Failure for Cell
BSC6900
V900R012
73393838
VS.RAB.FailEstab
PS.UuFail
Number of Failed PS
RAB Establishments
Due to Uu Interface
Configuration
Failure for Cell
BSC6900
V900R012
67179930
VS.RAB.FailEstab
PS.Unsp
Number of Failed PS
RAB Establishments
for Cell
(Unsupported
Capabilities)
Earlier than
BSC6900
V900R011
73394298
VS.RAB.FailEstab
PS.Cong
Number of Failed PS
RAB Establishments
BSC6900
V900R012
73423519
VS.RAB.FailEstab
PS.DLPower.Cong.
Free
Number of PS Free
RAB Setup Failures
due to DL Power
Resource
Congestion for Cell
BSC6900
V900R013

2659
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424886
VS.RAB.FailEstab
PS.SRBReset
Number of Failed PS
RAB Establishments
for Cell (Signaling
RLC Reset)
BSC6900
V900R014
73424887
VS.RAB.FailEstab
PS.CellUpd
Number of Failed PS
RAB Establishments
for Cell (Concurrent
Procedures)
BSC6900
V900R014
73424888
VS.RAB.FailEstab
PS.HSUPAUser.Co
ng
Number of Failed PS
RAB Establishments
for Cell (New RAB
Setup Failures When
the Maximum
Number of HSUPA
UEs Is Reached)
BSC6900
V900R014
73424889
VS.RAB.FailEstab
PS.HSDPAUser.Co
ng
Number of Failed PS
RAB Establishments
for Cell (New RAB
Setup Failures When
the Maximum
Number of HSDPA
UEs Is Reached)
BSC6900
V900R014
73428178
VS.RAB.FailEstab
PS.NodeBULCE.C
ong
Number of Failed PS
RAB Setups due to
NodeB UL CE
Congestion for Cell
BSC6900
V900R016C00
73428179
VS.RAB.FailEstab
PS.NodeBDLCE.C
ong
Number of Failed PS
RAB Setups due to
NodeB DL CE
Congestion for Cell
BSC6900
V900R016C00
73428183
VS.RAB.FailEstab
PS.DLIUPSBand.C
ong
Number of PS RAB
Setup Failures
Caused by DL Iu-PS
Congestion for Cell
BSC6900
V900R016C00
73428184
VS.RAB.FailEstab
PS.ULIUPSBand.C
ong
Number of PS RAB
Setup Failures
Caused by UL Iu-PS
Congestion for Cell
BSC6900
V900R016C00

2660
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428185
VS.RAB.FailEstab
PS.IubAAL2Fail
Number of PS RAB
Setup Failures
Caused by Iub
Transport Bearer
Establishment
Failures for Cell
BSC6900
V900R016C00
73428350
VS.RAB.FailEstab
PS.ULCE.FinalCong
Number of PS RAB
Setup Failures
Caused by
Admission Failures
in the Last Candidate
Cell Due to UL CE
Congestion
BSC6900
V900R016C00
below.
Counter
Sub Counter
VS.RAB.FailEstabPS.ULIUBBand.Cong
VS.RAB.FailEstabPS.DLIUBBand.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.UuFail
VS.RAB.FailEstabPS.SRBReset
VS.RAB.FailEstabPS.ULIUPSBand.Cong
VS.RAB.FailEstabPS.DLIUPSBand.Cong
VS.RAB.FailEstabPS.Unsp
Issue 03 (2015-06-30)
VS.RAB.FailEstabPS.Cong

2661
BSC6900 UMTS
Counter
Sub Counter
VS.RAB.FailEstabPS.NodeBULCE.Cong
VS.RAB.FailEstabPS.RBIncCfg
VS.RAB.FailEstabPS.RBCfgUnsupp
VS.RAB.FailEstabPS.PhyChFail
VS.RAB.FailEstabPS.UuNoReply

below.
Counter
Sub Counter
VS.RAB.FailEstabPS.IubAAL2Fail
VS.RAB.FailEstabPS.SRBReset
Issue 03 (2015-06-30)

2662
BSC6900 UMTS
Counter
Sub Counter
VS.RAB.FailEstabPS.NodeBULCE.Cong
VS.RAB.FailEstabPS.RBCfgUnsupp
VS.RAB.FailEstabPS.PhyChFail
Number of PS RABs Unsuccessfully Established due to Congestion

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73394298
Number of Failed PS RAB

(Congestion)
67192612
VS.RAB.FailEstabPS.DLIU
BBand.Cong

67192613
VS.RAB.FailEstabPS.ULIU
BBand.Cong

67190408
VS.RAB.FailEstabPS.ULC
E.Cong

CE Congestion)

2663
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67190409
VS.RAB.FailEstabPS.DLC
E.Cong

CE Congestion)
67179967
VS.RAB.FailEstabPS.Code.
Cong

(Code Congestion)
67193613
VS.RAB.FailEstabPS.ULPo
wer.Cong

Power Congestion)
67193614
VS.RAB.FailEstabPS.DLPo
wer.Cong

Power Congestion)
73424888
VS.RAB.FailEstabPS.HSUP
AUser.Cong

Establishments for Cell (New
RAB Setup Failures When
the Maximum Number of
HSUPA UEs Is Reached)
73424889
VS.RAB.FailEstabPS.HSDP
AUser.Cong

Establishments for Cell (New
RAB Setup Failures When
the Maximum Number of
HSDPA UEs Is Reached)
73428183
PSBand.Cong

Failures Caused by DL Iu-PS
Congestion for Cell
73428184
PSBand.Cong

Failures Caused by UL Iu-PS
Congestion for Cell
Description
These counters provide the number of PS RAB setup failures in the best cell for different resource
congestion causes. If the congestion occurs both in the uplink and downlink, the RNC measures
only the counters of the downlink. For example, if the power congestion occurs in the uplink
and downlink, the RNC measures only the VS.RAB.FailEstabPS.DLPower.Cong counter. The
25.413(v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving from the CN a
RAB ASSIGNMENT REQUEST message, requesting to setup a PS RAB, the RNC applies for
corresponding radio resources. If the application fails, the RAB setup fails, and the RNC sends
Issue 03 (2015-06-30)

2664
BSC6900 UMTS
the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the
failure cause is one of the following: "No Radio Resources Available in Target cell", "Requested
Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL not Available",
"Requested Maximum Bit Rate for DL not Available", or "Tqueuing Expiry". In this case, the
RNC measures this counter based on the specific cause in the best cell for the UE.
Note that the measurement scope of the preceding counters can be changed using the
RAB_RELATED_COUNTER_OPT_SWITCH parameter in the SET URRCTRLSWITCH
command. When this parameter is set to 1, these counters are not incremented by one when a
RAB ASSIGNMENT RESPONSE message includes a cause value of "No resource available".
Formula
None
Unit
None
Issue 03 (2015-06-30)

2665
BSC6900 UMTS
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
BBand.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
BBand.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
E.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabPS.DLC
E.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabPS.Code.
Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabPS.ULPo
wer.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
wer.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2666
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabPS.HSUP
AUser.Cong
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabPS.HSDP
AUser.Cong
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
PSBand.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
PSBand.Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RAB Setup Failures Caused by Admission Failures in the Last

Candidate Cell Due to UL CE Congestion
Counters
Counter ID
Counter Name
Counter Description
73428350
E.FinalCong

Failures Caused by
Admission Failures in the
Last Candidate Cell Due to
UL CE Congestion
Description
This counter measures the number of PS RAB setup failures caused by admission failures in the
last candidate cell due to uplink CE congestion. This counter is measured in the last candidate
cell. The following uses the inter-frequency DRD as an example to illustrate this counter. When
the requirements for the inter-frequency DRD are met, the UE attempts to access the current cell
or a candidate inter-frequency neighboring cell based on their priorities. If the admission in all
candidate cells fails (including the admission performed after the fallback from HSPA to R99),
the RAB setup fails. The admission failure in the last candidate cell is considered as the last
admission failure.This counter complies with section "8.2 Radio Bearer control procedures" in
3GPP TS 25.413(v10.10.0).
Issue 03 (2015-06-30)

2667
BSC6900 UMTS
Measurement point
The measurement is triggered at point B in figure 1. When receiving a RAB ASSIGNMENT
REQUEST message from the CN, requesting the establishment of a PS RAB, the RNC applies
for related radio resources. If the last admission fails because of uplink CE congestion, the RNC
sends a RAB ASSIGNMENT RESPONSE message to the CN, and the RAB setup procedure
fails. This counter is measured in the last candidate cell.
Figure 1-1147 PS RAB setup failure procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
E.FinalCong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-02040001

Issue 03 (2015-06-30)

2668
BSC6900 UMTS
Number of Failed PS RABs due to Unsupported Capabilities (Cell)

Counters
Counter ID
Counter Name
Counter Description
67179930

(Unsupported Capabilities)
Description
This counter provides the number of failed PS RABs due to insufficient abilities in the best
cell.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.413(v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the following figure. If a PS RAB fails to
be set up due to capability insufficiency, the RNC sends a RAB ASSIGNMENT RESPONSE
message to the CN, indicating the CS RAB setup failure. This counter is measured in the best
cell for a UE.
URRCTRLSWITCH command is set to 0, the common example of capability insufficiency is
license unavailability or radio resource insufficiency, the failure cause is "Requested Traffic
Class not Available","Requested Maximum Bit Rate not Available","Requested Maximum Bit
Rate for DL not Available","Requested Maximum Bit Rate for UL not Available","Requested
Guaranteed Bit Rate not Available","Requested Guaranteed Bit Rate for DL not
Available","Requested Guaranteed Bit Rate for UL not Available","No Radio Resources
Available in Target cell","Requested Transfer Delay not Achievable","No Resource
Available"or "TQUEUING Expiry".
When this parameter is set to 1, the common example of capability insufficiency is license
unavailability, the failure cause is "Requested Traffic Class not Available","Requested
Guaranteed Bit Rate not Available","Requested Guaranteed Bit Rate for DL not
Available","Requested Guaranteed Bit Rate for UL not Available","Requested Transfer Delay
not Achievable".
Issue 03 (2015-06-30)

2669
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2670
BSC6900 UMTS
Number of PS Free RAB Setup Failures due to DL Power Resource Congestion for
Cell
Counters
Counter ID
Counter Name
Counter Description
73423519
wer.Cong.Free
Number of PS Free RAB

Setup Failures due to DL
Power Resource Congestion
for Cell
Description
This counter provides the number of PS free RAB setup failures in the best cell due to DL power
resource congestion.This counter complies with section "8.2 Radio Bearer control procedures"
in 3GPP TS 25.413(v10.10.0).
Measurement point
This measurement is triggered at point B as shown in the following figure. When the RNC sends
to the CN a RAB ASSIGNMENT RESPONSE message indicating a RAB setup failure, it
measures this counter in the best cell on which the UE camps if the PS free RAB setup fails due
to DL power resource congestion.
Issue 03 (2015-06-30)

2671
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
wer.Cong.Free
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RABs Unsuccessfully Established due to Transport Network Layer

Cause
Counters
Counter ID
Counter Name
Counter Description
67189557

(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.This counter complies with section "8.2
Radio Bearer control procedures" in 3GPP TS 25.413(v10.10.0).
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,
Issue 03 (2015-06-30)

2672
BSC6900 UMTS
Figure 1-1150 PS RAB setup procedure (failed operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2673
BSC6900 UMTS
Number of Failed PS RAB Establishments Due to Radio Link Configuration

Failure
Counters
Counter ID
Counter Name
Counter Description
73393837
VS.RAB.FailEstabPS.IubFail

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.This counter complies
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.
Issue 03 (2015-06-30)

2674
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.
Issue 03 (2015-06-30)

2675
BSC6900 UMTS
Figure 1-1153 Timeout for a RADIO LINK RESTORE INDICATION message after receiving
a RADIO LINK FAIL INDICATION message
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabPS.IubFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2676
BSC6900 UMTS
Number of Failed PS RAB Setups due to NodeB CE Congestion for Cell

Counters
Counter ID
Counter Name
Counter Description
73428178
VS.RAB.FailEstabPS.Node
BULCE.Cong

Setups due to NodeB UL CE
Congestion for Cell
73428179
BDLCE.Cong

Setups due to NodeB DL CE
Congestion for Cell
Description
These counters measure the number of PS RAB establishment failures caused by NodeB uplink
or downlink CE congestion in a cell. These counters are measured in the best cell for UEs.The
25.413(v10.10.0).
Measurement point
The measurement is triggered at point B in figure 1. When the RNC receives a RAB
ASSIGNMENT REQUEST message from the CN, requesting the setup of a PS RAB, the RNC
applies for related radio resources and initiate an RL reconfiguration procedure (or RL
establishment procedure). If the RNC receives an RL reconfiguration failure message (or RL
establishment failure message) with a cause value indicating uplink or downlink CE congestion,
the RNC sends a RAB ASSIGNMENT RESPONSE message to the CN and the RAB setup fails.
The cause values indicating uplink CE congestion are
"UL_RADIO_RESOURCES_NOT_AVAILABLE" and "CELL_SYN_NOT_SUPP". The
cause values indicating downlink CE congestion are
These counters are separately measured in the uplink and downlink of the best cell.
Issue 03 (2015-06-30)

2677
BSC6900 UMTS
Figure 1-1154 RAB setup failure procedure (due to NodeB CE resource congestion)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
BULCE.Cong
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2678
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
BDLCE.Cong
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RAB Setup Failures Caused by Iub Transport Bearer Establishment

Failures for Cell
Counters
Counter ID
Counter Name
Counter Description
73428185
VS.RAB.FailEstabPS.IubA
AL2Fail

Failures Caused by Iub
Transport Bearer
Establishment Failures for
Cell
Description
This counter provides the number of PS RABs that fail to be set up due to Iub transport bearer
establishment failures. It is measured in the best cell for a UE.This counter complies with section
Measurement point
The measurement is triggered at point B as shown in the following figure. During the setup of
a PS RAB, if the AAL2 transport bearer fails to be set up over the Iub interface, the RNC sends
a RAB ASSIGNMENT RESPONSE message to the CN, indicating the PS RAB setup failure
and this counter is measured in the best cell for the UE.
Issue 03 (2015-06-30)

2679
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabPS.IubA
AL2Fail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2680
BSC6900 UMTS
Number of Failed PS RABs due to different reasons of UE During the RB Setup

Procedure for cell
Counters
Counter ID
Counter Name
Counter Description
67193540
VS.RAB.FailEstabPS.RBIn
cCfg

Establishments for Cell (UU
interface invalid
configuration)
67193541
VS.RAB.FailEstabPS.RBCf
gUnsupp

(Configuration unsupported
of UE during the RB setup
procedure)
67193543

Establishments for Cell (No
reply of UE during the RB
setup procedure)
67193542
VS.RAB.FailEstabPS.PhyC
hFail

(Physical channel failure of
UE during the RB setup
procedure)
73393838

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.The preceding counters complies with section "8.2 Radio Bearer control
Issue 03 (2015-06-30)
Counter Name
Description
Number of PS RABs Unsuccessfully

Established due to invalid configuration of

Established due to no reply during the RB
Setup Procedure

2681
BSC6900 UMTS
Counter Name
Description

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.
Issue 03 (2015-06-30)

2682
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-1157 RAB setup procedure (UE response timeouts)
Formula
None
Unit
None
Issue 03 (2015-06-30)

2683
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabPS.RBIn
cCfg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabPS.RBCf
gUnsupp
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.FailEstabPS.PhyC
hFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Failed PS RAB Establishments for Cell (Signaling RLC Reset)

Counters
Counter ID
Counter Name
Counter Description
73424886
VS.RAB.FailEstabPS.SRBR
eset

(Signaling RLC Reset)
Description
This counter provides the number of times that a PS RAB establishment fails due to signaling
RLC reset.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP
TS 25.413(v10.10.0).
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
Issue 03 (2015-06-30)

2684
BSC6900 UMTS
RESPONSE message indicating that the operation fails due to the reset of the RLC that carries
the RADIO BEARER SETUP message.
Figure 1-1158 RAB setup procedure(Signaling RLC Reset)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.FailEstabPS.SRBR
eset
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2685
BSC6900 UMTS
Number of Failed PS RAB Establishments for Cell (Concurrent Procedures)

Counters
Counter ID
Counter Name
Counter Description
73424887

(Concurrent Procedures)
Description
This counter provides the number of times that a PS RAB establishment fails due to RB Setup
and Cell Update Overlap.This counter complies with section "8.2 Radio Bearer control
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-1159 RAB setup procedure(RB Setup and Cell Update Overlap)
Formula
None
Issue 03 (2015-06-30)

2686
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RABs Unsuccessfully Established due to Radio Network Layer

Cause for Cell
Counters
Counter ID
Counter Name
Counter Description
67189556

Cause)
Description
These counter provide the number of PS RABs unsuccessfully established in the best cell due
to radio network layer cause.This counter complies with section "8.2 Radio Bearer control
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
case, the RNC measures each counter in the best cell that the UE camps on.
Issue 03 (2015-06-30)

2687
BSC6900 UMTS
Figure 1-1160 PS RAB setup procedure (failed operation)
The measurement is triggered at point B as shown in the figure. the RNC receives the IU
RELEASE COMMAND message from the CN at point B during the RAB establishment process.
In this case, the RNC measures each counter in the best cell that the UE camps on.
Figure 1-1161 RAB ASSIGN IU REL procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

2688
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.34 CS RAB Modification Measurement <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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179840
VS.RAB.FailModC
S.TNL
Number of Failed CS
RAB Modifications
Due to Iu Transport
Connection Setup
Failure for Cell
Earlier than
BSC6900
V900R011
67179835
VS.RAB.AttEstMo
dCS.Conv
Number of RAB
Modification
Requests for CS
Conversational
Services for Cell
Earlier than
BSC6900
V900R011
67179836
VS.RAB.AttEstMo
dCS.Str
Number of RAB
Modification
Requests for CS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011

2689
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67179837
VS.RAB.SuccMod
CS.Conv
Number of
Successful CS RAB
Modifications for
Conversational
Services for Cell
Earlier than
BSC6900
V900R011
67179838
VS.RAB.SuccMod
CS.Str
Number of
Successful CS RAB
Modifications for
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
73393839
VS.RAB.FailModC
S.RNL
Number of Failed CS
RAB Modifications
Due to Radio
Network Layer
Cause for Cell
BSC6900
V900R012
None
Number of Failed CS RAB Modifications Due to Transport Network Layer Cause

Counters
Counter ID
Counter Name
Counter Description
67179840
VS.RAB.FailModCS.TNL

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.This counter complies with
section "8.2 Radio Bearer control procedures" in 3GPP TS 25.413(v10.10.0).
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.
Issue 03 (2015-06-30)

2690
BSC6900 UMTS
Figure 1-1162 CS RAB modification procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.FailModCS.TNL
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counters Related to the Number of CS RAB Modification Requests

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179835
VS.RAB.AttEstModCS.Con
v
Number of RAB
for Cell

2691
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67179836
VS.RAB.AttEstModCS.Str
Number of RAB
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.The preceding counters complies with section "8.2 Radio Bearer
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-1163 CS RAB modification procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

2692
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstModCS.Con
v
WRFD-010501
VS.RAB.AttEstModCS.Str
WRFD-010502
Streaming QoS Class
Counters Related to the Number of Successful CS RAB Modifications

Counters
Counter ID
Counter Name
Counter Description
67179837
VS.RAB.SuccModCS.Conv
RAB Modifications for
Cell
67179838
VS.RAB.SuccModCS.Str
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.The preceding counters complies with section
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.
Issue 03 (2015-06-30)

2693
BSC6900 UMTS
Figure 1-1164 RAB modification procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccModCS.Conv
WRFD-010501
VS.RAB.SuccModCS.Str
WRFD-010502
Streaming QoS Class
Number of Failed CS RAB Modifications Due to Radio Network Layer Cause

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393839
VS.RAB.FailModCS.RNL

Modifications Due to Radio
Network Layer Cause for
Cell

2694
BSC6900 UMTS
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.This counter complies with section "8.2 Radio Bearer control procedures" in 3GPP TS
25.413(v10.10.0).
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-1165 RAB assignment failure procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

2695
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.FailModCS.RNL
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.35 PS RAB Modification Measurement <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.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179943
VS.RAB.FailModP
S.TNL
Number of Failed PS
RAB Modifications
Due to Iu Transport
Connection Failure
for Cell
Earlier than
BSC6900
V900R011
67179937
VS.RAB.AttEstMo
dPS.Bkg
Number of RAB
Modification
Requests for PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67179934
VS.RAB.AttEstMo
dPS.Conv
Number of RAB
Modification
Requests for PS
Conversational
Services for Cell
Earlier than
BSC6900
V900R011

2696
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67179936
VS.RAB.AttEstMo
dPS.Inter
Number of RAB
Modification
Requests for PS
for Cell
Earlier than
BSC6900
V900R011
67179935
VS.RAB.AttEstMo
dPS.Str
Number of RAB
Modification
Requests for PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67179941
VS.RAB.SuccMod
PS.Bkg
Number of
Successful RAB
Background
Services for Cell
Earlier than
BSC6900
V900R011
67179938
VS.RAB.SuccMod
PS.Conv
Number of
Successful RAB
Conversational
Services for Cell
Earlier than
BSC6900
V900R011
67179940
VS.RAB.SuccMod
PS.Inter
Number of
Successful RAB
for Cell
Earlier than
BSC6900
V900R011
67179939
VS.RAB.SuccMod
PS.Str
Number of
Successful RAB
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
73393840
VS.RAB.FailModP
S.RNL
Number of Failed PS
RAB Modifications
Due to Radio
Network Fault for
Cell
BSC6900
V900R012
None
Issue 03 (2015-06-30)

2697
BSC6900 UMTS
Number of Failed PS RAB Modifications Due to Iu Transport Connection Failure

Counters
Counter ID
Counter Name
Counter Description
67179943
VS.RAB.FailModPS.TNL

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.This counter complies with
section "8.2 Radio Bearer control procedures" in 3GPP TS 25.413(v10.10.0).
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends to the
SGSN a RAB ASSIGNMENT RESPONSE message with the failure cause of "Signalling
Transport Resource Failure" or "Iu Transport Connection Failed to Establish", indicating that
the RAB modification fails, this counter is measured in the best cell that the UE camps on.
Formula
None
Issue 03 (2015-06-30)

2698
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.FailModPS.TNL
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RAB Modification Requests

Counters
Counter ID
Counter Name
Counter Description
67179934
VS.RAB.AttEstModPS.Con
v
Number of RAB
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.The preceding counters complies with section "8.2 Radio Bearer
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.
Issue 03 (2015-06-30)

2699
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AttEstModPS.Con
v
WRFD-010501
VS.RAB.AttEstModPS.Bkg
WRFD-010504
VS.RAB.AttEstModPS.Inter
WRFD-010503
VS.RAB.AttEstModPS.Str
WRFD-010502
Streaming QoS Class

2700
BSC6900 UMTS
Number of Successful PS RAB Modifications

Counters
Counter ID
Counter Name
Counter Description
67179938
VS.RAB.SuccModPS.Conv

Cell
67179941
VS.RAB.SuccModPS.Bkg

67179940
VS.RAB.SuccModPS.Inter

67179939
VS.RAB.SuccModPS.Str

Description
These counters provide the number of times that the RAB is modified successfully for PS
services in the best cell based on the service type.The preceding counters complies with section
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.
Issue 03 (2015-06-30)

2701
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SuccModPS.Conv
WRFD-010501
VS.RAB.SuccModPS.Bkg
WRFD-010504
VS.RAB.SuccModPS.Inter
WRFD-010503
VS.RAB.SuccModPS.Str
WRFD-010502
Streaming QoS Class
Number of Failed PS RAB Modifications Due to Radio Network Fault

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393840
VS.RAB.FailModPS.RNL

Modifications Due to Radio
Network Fault for Cell

2702
BSC6900 UMTS
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.This
(v10.10.0).
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.
Figure 1-1169 RAB assignment failure procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

2703
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.FailModPS.RNL
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.36 Multi-RAB Service Measurement <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
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199698
VS.SingleRAB.SF4
Number of singleRAB UEs that

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 4 for Cell
Earlier than
BSC6900
V900R011
67199699
VS.SingleRAB.SF8

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 8 for Cell
Earlier than
BSC6900
V900R011
67199700
VS.SingleRAB.SF1
6

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 16 for Cell
Earlier than
BSC6900
V900R011
67199701
VS.SingleRAB.SF3
2

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 32 for Cell
Earlier than
BSC6900
V900R011

2704
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199702
VS.SingleRAB.SF6
4

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 64 for Cell
Earlier than
BSC6900
V900R011
67199703
VS.SingleRAB.SF1
28

Occupy the DL R99
Codes with
Spreading Factor
(SF) of 128 for Cell
Earlier than
BSC6900
V900R011
67199704
VS.SingleRAB.SF2
56

Occupy the DL R99
Codes with
Spreading Factor
Earlier than
BSC6900
V900R011
67202942
VS.MultRAB.SF4
Number of multiRAB UEs that

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 4 for Cell
Earlier than
BSC6900
V900R011
67199691
VS.MultRAB.SF8

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 8 for Cell
Earlier than
BSC6900
V900R011
67199692
VS.MultRAB.SF16

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 16 for Cell
Earlier than
BSC6900
V900R011
67199693
VS.MultRAB.SF32

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 32 for Cell
Earlier than
BSC6900
V900R011

2705
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199694
VS.MultRAB.SF64

Occupy the DL R99
Codes with the
Spreading Factor
(SF) of 64 for Cell
Earlier than
BSC6900
V900R011
67202943
VS.MultRAB.SF12
8

Occupy the DL R99
Codes with the
Spreading Factor
Earlier than
BSC6900
V900R011
67202944
VS.MultRAB.SF25
6

Occupy the DL R99
Codes with the
Spreading Factor
Earlier than
BSC6900
V900R011
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
Earlier than
BSC6900
V900R011
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
Earlier than
BSC6900
V900R011
73439942
VS.MultiRAB.Mea
nThroughput.HSD
PA
Mean Throughput of
a Single HSDPA
MAC-d Flow in the
Case of Multi-RAB
Services for Cell
BSC6900
V900R012
73439943
VS.MultiRAB.Mea
nThroughput.HSUPA
Mean Throughput of
a Single HSUPA
MAC-d Flow in the
Case of Multi-RAB
Services for Cell
BSC6900
V900R012

2706
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73439944
VS.MultiRAB.Mea
nThroughput.PSR9
9DL
Mean Downlink
Throughput of a
Single PS R99 RB in
the Case of MultiRAB Services for
Cell
BSC6900
V900R012
73439945
VS.MultiRAB.Mea
nThroughput.PSR9
9UL
Mean Uplink
Throughput of a
Single PS R99 RB in
Cell
BSC6900
V900R012
73421828
VS.MultiRAB.AttE
stab.CSPS
Number of CS+PS
Combined Service
Setup Requests for
Cell
BSC6900
V900R012
73421829
VS.MultiRAB.Succ
Estab.CSPS
Number of
Successful CS+PS
Combined Service
Setups for Cell
BSC6900
V900R012
73421830
VS.MultiRAB.AttE
stab.PSPS
Number of PS+PS
Combined Service
Setup Requests for
Cell
BSC6900
V900R012
73421831
VS.MultiRAB.Succ
Estab.PSPS
Number of
Successful PS+PS
Combined Service
Setups for Cell
BSC6900
V900R012
73421832
VS.MultiRAB.CSN
ormRel.CSPS
Number of Normal
CS Service Releases
of CS+PS Combined
Services for Cell
BSC6900
V900R012
73421834
VS.MultiRAB.PSN
ormRel.PSPS
Number of Normal
PS Service Releases
of PS+PS Combined
Services for Cell
BSC6900
V900R012
73421835
VS.MultiRAB.CSA
bnormRel.CSPS
Number of
Abnormal CS
Service Releases of
CS+PS Combined
Services for Cell
BSC6900
V900R012

2707
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421837
VS.MultiRAB.PSA
bnormRel.PSPS
Number of
Abnormal PS
Service Releases of
PS+PS Combined
Services for Cell
BSC6900
V900R012
73421838
VS.MultiRAB.CSA
bnormRel.PSAtt
Number of
Abnormal CS
Service Releases
During PS Service
Setup for Cell
BSC6900
V900R012
73421839
VS.MultiRAB.CSA
bnormRel.PSRel
Number of
Abnormal CS
Service Releases
During PS Service
Release for Cell
BSC6900
V900R012
73421840
VS.MultiRAB.PSN
ormRel.CSPS
Number of Normal
PS Service Releases
of CS+PS Combined
Services for Cell
BSC6900
V900R012
73421841
VS.MultiRAB.PSA
bnormRel.CSPS
Number of
Abnormal PS
Service Releases of
CS+PS Combined
Services for Cell
BSC6900
V900R012
73424024
VS.AttEstabCS.PSi
nDCH
Number of CS
Service Setup
Attempts of UEs
with an Ongoing PS
Service in the
CELL_DCH state for
Cell
BSC6900
V900R014
73424025
VS.SuccEstabCS.P
SinDCH
Number of
Successful CS
Service Setups of
UEs with an Ongoing
PS Service in the
CELL_DCH state for
Cell
BSC6900
V900R014

2708
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424026
VS.AttEstabCS.PSi
nFACH
Number of CS
Service Setup
Attempts of UEs
with an Ongoing PS
Service in the
CELL_FACH state
for Cell
BSC6900
V900R014
73424027
VS.SuccEstabCS.P
SinFACH
Number of
Successful CS
Service Setups of
UEs with an Ongoing
PS Service in the
CELL_FACH state
for Cell
BSC6900
V900R014
73424028
VS.AttPSP2D.CSC
onv
Number of State
Transition Attempts
from CELL_PCH or
URA_PCH to
CELL_DCH with the
Cause Value of CS
Service for Cell
BSC6900
V900R014
73424029
VS.SuccPSP2D.CS
Conv
Number of
Successful State
Transitions from
CELL_PCH or
URA_PCH to
CELL_DCH with the
Cause Value of CS
Service for Cell
BSC6900
V900R014
73425016
VS.MultiRAB.PSA
bnormRel.ResumeExp
Number of
Abnormal PS
Service Releases in
Cell during an interRAT handover( PS
Resume Timer
Expiry)
BSC6900
V900R014
73425977
VS.MultiRAB.CSP
SNormRel.CSPS
Number of Normally
Released CS and PS
Services in CS+PS
Combined Services
BSC6900
V900R015C00

2709
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73425978
VS.MultiRAB.CSP
SAbnormRel.CSPS
Number of
Abnormally
Released CS and PS
Services in CS+PS
Combined Services
BSC6900
V900R015C00
73426879
VS.MultiRAB.CSA
bnormRel.PSRBco
nfig.CellUpd
Number of Times CS
Service in CS+PS
Combined Services
Is Abnormally
Released Due to a
Cell Update Failure
During RB
Reconfiguration
BSC6900
V900R015C01
73426880
VS.MultiRAB.CSA
bnormRel.PSPhyR
ecfg.CellUpd
Number of Times CS
Service in CS+PS
Combined Services
Is Abnormally
Released Due to a
Cell Update Failure
During Physical
Channel
Reconfiguration
BSC6900
V900R015C01
73427966
VS.MultiRAB.AttE
stabCS.FastSetup
Number of CS RAB
Setup Requests for
PS+CS Combined
Services for Cell
(Fast Setup)
BSC6900
V900R016C00
73427967
VS.MultiRAB.Succ
EstabCS.FastSetup
Number of
Successful CS RAB
Setups for PS+CS
Combined Services
for Cell (Fast Setup)
BSC6900
V900R016C00
None
Issue 03 (2015-06-30)

2710
BSC6900 UMTS
Mean Number of Single-RAB UEs Occupy the Codes with Different Spreading
Factors
Counters
Counter ID
Counter Name
Counter Description
67199698
VS.SingleRAB.SF4
Number of single-RAB UEs

that Occupy the DL R99
Codes with Spreading Factor
(SF) of 4 for Cell
67199699
VS.SingleRAB.SF8

(SF) of 8 for Cell
67199700
VS.SingleRAB.SF16

(SF) of 16 for Cell
67199701
VS.SingleRAB.SF32

(SF) of 32 for Cell
67199702
VS.SingleRAB.SF64

(SF) of 64 for Cell
67199703
VS.SingleRAB.SF128

67199704
VS.SingleRAB.SF256

Description
These counters provide the average number of single-RAB UEs that use the spreading factor
(SF) of 4/8/16/32/64/128/256 in a cell.These counters comply with section "8.2.2
Measurement point
single-RAB UEs that use the SF of 4/8/16/32/64/128/256 in a cell. At the end of the measurement
Issue 03 (2015-06-30)

2711
BSC6900 UMTS
period, the RNC divides the accumulated number of single-RAB UEs by the number of samples
to get the average number of single-RAB UEs that use the SF of 4/8/16/32/64/128/256 in a cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SingleRAB.SF4
WRFD-020108
VS.SingleRAB.SF8
WRFD-020108
VS.SingleRAB.SF16
WRFD-020108
VS.SingleRAB.SF32
WRFD-020108
VS.SingleRAB.SF64
WRFD-020108
VS.SingleRAB.SF128
WRFD-020108
VS.SingleRAB.SF256
WRFD-020108
Mean Number of Multi-RAB UEs Occupy the Codes with Different Spreading
Factors
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202942
VS.MultRAB.SF4
Number of multi-RAB UEs

Codes with the Spreading
Factor (SF) of 4 for Cell
67199691
VS.MultRAB.SF8

67199692
VS.MultRAB.SF16


2712
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67199693
VS.MultRAB.SF32

67199694
VS.MultRAB.SF64

67202943
VS.MultRAB.SF128

67202944
VS.MultRAB.SF256

Description
These counters provide the average number of multi-RAB UEs that use the spreading factor
(SF) of 4/8/16/32/64/128/256 in a cell.These counters comply with section "8.2.2
Measurement point
multi-RAB UEs that use the SF of 4/8/16/32/64/128/256 in a cell. At the end of the measurement
period, the RNC divides the accumulated number of multi-RAB UEs by the number of samples
to get the average number of multi-RAB UEs that use the SF of 4/8/16/32/64/128/256 in a cell.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MultRAB.SF4
WRFD-020108
VS.MultRAB.SF8
WRFD-020108

2713
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.MultRAB.SF16
WRFD-020108
VS.MultRAB.SF32
WRFD-020108
VS.MultRAB.SF64
WRFD-020108
VS.MultRAB.SF128
WRFD-020108
VS.MultRAB.SF256
WRFD-020108
Max Count of SF which has been occupied

Counters
Counter ID
Counter Name
Counter Description
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 HSDSCH. Codes occupied by the HS-DSCH are allocated by the RNC using the automatic or
manual code allocation algorithm. The code number is normalized to SF = 256, that is, converted
to the code number when SF = 256. The way of the normalization to SF = 256 is to multiply the
number when SF = k by 256/k.When the NodeB dynamic code switch is turned on, the RNC
cannot count the extra SF codes beyond the range of reserved codes that are used by the NodeB.
Otherwise, the preceding counters are not reported as expected.These counters comply with
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..
Issue 03 (2015-06-30)

2714
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.SFOccupy.MAX
WRFD-020108
VS.RAB.SFOccupy
WRFD-020108
Mean Throughput of a Single HSDPA MAC-d Flow in the Case of Multi-RAB

Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73439942
VS.MultiRAB.MeanThroug
hput.HSDPA
Mean Throughput of a Single

HSDPA MAC-d Flow in the
Case of Multi-RAB Services
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73421821
hput.HSDPA.Times
hput.HSDPA.Times
73421820
hput.HSDPA.Traffic
hput.HSDPA.Traffic
Description
This counter provides the mean throughput of a single HSDPA MAC-d flow in the case of MultiRAB services in the HSDPA cell. For DC-HSDPA users, this counter is measured only in the
primary cell based on the total throughput on the primary and secondary carriers.
Issue 03 (2015-06-30)

2715
BSC6900 UMTS
Measurement point
When users initiate Multi-RAB services in an HSDPA cell and there is data transmission in the
HSDPA cell, the total period of time used for transmitting data and the total number of bits
transmitted in the HSDPA cell are calculated. At the end of the measurement period, the mean
throughput of a single MAC-d flow at the RLC layer in a cell is calculated by dividing the total
number of bits by the total period of time. Note that the total number of measured bits excludes
RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.HSDPA = {8}*
[VS.MultiRAB.MeanThroughput.HSDPA.Traffic]/
[VS.MultiRAB.MeanThroughput.HSDPA.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
hput.HSDPA
WRFD-010609

WRFD-01061505
Services
Mean Throughput of a Single HSUPA MAC-d Flow in the Case of Multi-RAB

Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73439943
hput.HSUPA
Mean Throughput of a Single

HSUPA MAC-d Flow in the
for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421823
hput.HSUPA.Times
hput.HSUPA.Times

2716
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421822
hput.HSUPA.Traffic
hput.HSUPA.Traffic
Description
This counter provides the mean throughput of a single HSUPA MAC-d flow in the case of MultiRAB services in the HSUPA cells of the active set.For DC-HSUPA users, this counter is
measured only in the primary cell based on the total throughput on the primary and secondary
carriers.
Measurement point
When users initiate Multi-RAB services in HSUPA cells of the active set and there is data
transmission in uplink in the HSUPA cells, the total period of time used for transmitting data
and the total number of bits transmitted in the HSUPA cells of the active set are calculated. At
the end of the measurement period, the mean uplink throughput of a single MAC-d flow at the
RLC layer in a cell is calculated by dividing the total number of bits by the total period of time.
Note that the total number of measured bits excludes RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.HSUPA = {8}*
[VS.MultiRAB.MeanThroughput.HSUPA.Traffic]/
[VS.MultiRAB.MeanThroughput.HSUPA.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
hput.HSUPA
WRFD-010609

WRFD-01061505
Services
Issue 03 (2015-06-30)

2717
BSC6900 UMTS
Mean Downlink Throughput of a Single PS R99 RB in the Case of Multi-RAB

Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73439944
hput.PSR99DL

of a Single PS R99 RB in the
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73421825
hput.PSR99DL.Times
hput.PSR99DL.Times
73421824
hput.PSR99DL.Traffic
hput.PSR99DL.Traffic
Description
This counter provides the mean downlink throughput of a single PS R99 RB in the case of MultiRAB services in cells of the active set.
Measurement point
When users initiate Multi-RAB services and there is PS R99 data transmission in downlink in
cells of the active set, the total period of time used for transmitting data and the total number of
bits transmitted in the cells of the active set are calculated. At the end of the measurement period,
the mean downlink throughput of a single PS R99 RB at the RLC layer in a cell is calculated by
dividing the total number of bits by the total period of time. Note that the total number of
measured bits excludes RLC headers and retransmitted data.
Formula
VS.MultiRAB.MeanThroughput.PSR99DL = {8}*
[VS.MultiRAB.MeanThroughput.PSR99DL.Traffic]/
[VS.MultiRAB.MeanThroughput.PSR99DL.Times]
Unit
kbit/s
Issue 03 (2015-06-30)

2718
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
hput.PSR99DL
WRFD-010609

WRFD-01061505
Services
Mean Uplink Throughput of a Single PS R99 RB in the Case of Multi-RAB Services

for Cell
Counters
Counter ID
Counter Name
Counter Description
73439945
hput.PSR99UL

a Single PS R99 RB in the
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73421827
hput.PSR99UL.Times
hput.PSR99UL.Times
73421826
hput.PSR99UL.Traffic
hput.PSR99UL.Traffic
Description
This counter provides the mean uplink throughput of a single PS R99 RB in the case of MultiRAB services in cells of the active set.
Measurement point
When users initiate Multi-RAB services and there is PS R99 data transmission in uplink in cells
of the active set, the total period of time used for transmitting data and the total number of bits
transmitted in cells of the active set are calculated. At the end of the measurement period, the
mean uplink throughput of a single PS R99 RB at the RLC layer in a cell is calculated by dividing
the total number of bits by the total period of time. Note that the total number of measured bits
excludes RLC headers and retransmitted data.
Issue 03 (2015-06-30)

2719
BSC6900 UMTS
Formula
VS.MultiRAB.MeanThroughput.PSR99UL = {8}*
[VS.MultiRAB.MeanThroughput.PSR99UL.Traffic]/
[VS.MultiRAB.MeanThroughput.PSR99UL.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
hput.PSR99UL
WRFD-010609

WRFD-01061505
Services
Number of CS+PS Combined Service Setup Requests for Cell

Counters
Counter ID
Counter Name
Counter Description
73421828
VS.MultiRAB.AttEstab.CS
PS
Number of CS+PS
Combined Service Setup
Requests for Cell
73421830
VS.MultiRAB.AttEstab.PSP
S
Number of PS+PS Combined

Service Setup Requests for
Cell
73424024
VS.AttEstabCS.PSinDCH

Attempts of UEs with an
Ongoing PS Service in the
CELL_DCH state for Cell
73424026
VS.AttEstabCS.PSinFACH

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.
Issue 03 (2015-06-30)

2720
BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in the following figure if one or more RABs
of a UE already exists in the cell. When receiving from the CN an RAB ASSIGNMENT
REQUEST message, the RNC checks the RAB type carried in the message and determines the
combined service type based on the existing RAB type of the UE. The counter is measured in
the best cell that the UE camps on if the combined service type is CS+PS. For the combined
service type of CS+PS, CS+2PS, or CS+3PS, the counter of CS+PS combined service is
measured. For the combined service type of 2PS, 3PS, or 4PS, the counter of PS+PS combined
service is measured. VS.MultiRAB.AttEstab.CSPS and VS.MultiRAB.AttEstab.PSPS are
measured in scenarios where service setup sequence is not considered.
VS.AttEstabCS.PSinDCH and VS.AttEstabCS.PSinFACH are measured in scenarios where PS
services are established before CS services.
Figure 1-1170 RAB setup for combined services
Issue 03 (2015-06-30)

2721
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MultiRAB.AttEstab.CS
PS
WRFD-010609

WRFD-01061505
Services
VS.MultiRAB.AttEstab.PSP
S
WRFD-010609
WRFD-01061505

Services
VS.AttEstabCS.PSinDCH
WRFD-010609
WRFD-01061505

Services
VS.AttEstabCS.PSinFACH
WRFD-010609
WRFD-01061505

Services
Number of Successful CS+PS Combined Service Setups for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421829
VS.MultiRAB.SuccEstab.C
SPS
+PS Combined Service
Setups for Cell
73421831
VS.MultiRAB.SuccEstab.P
SPS
+PS Combined Service
Setups for Cell

2722
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73424025
VS.SuccEstabCS.PSinDCH
Service Setups of UEs with
an Ongoing PS Service in the
CELL_DCH state for Cell
73424027
VS.SuccEstabCS.PSinFACH
Service Setups of UEs with
an Ongoing PS Service in the
CELL_FACH state for Cell
Description
This counter provides the number of successful RAB setup requests for combined services in
the best cell.
Measurement point
The measurement is triggered at point B as shown in the following figure if one or more RABs
of a UE already exists in the cell. When sending an RAB ASSIGNMENT RESPONSE message
to the CN after receiving an RADIO BEARER SETUP COMPLETE message from the UE, the
RNC checks the RAB type and determines the combined service type based on the existing RAB
type of the UE. The counter is measured in the best cell that the UE camps on if the combined
service type is CS+PS. For the combined service type of CS+PS, CS+2PS, or CS+3PS, the
counter of CS+PS combined service is measured. For the combined service type of 2PS, 3PS,
or 4PS, the counter of PS+PS combined service is measured. VS.MultiRAB.SuccEstab.CSPS
and VS.MultiRAB.SuccEstab.PSPS are measured in scenarios where service setup sequence is
not considered. VS.SuccEstabCS.PSinDCH and VS.SuccEstabCS.PSinFACH are measured in
scenarios where PS services are established before CS services.
Issue 03 (2015-06-30)

2723
BSC6900 UMTS
Figure 1-1171 RAB setup for combined services
The Figure show the combined service setup procedure of a CS called party after the parallel
handling of the alerting procedure is enabled. The measurement is triggered is triggered at point
B. When the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE,
the number of successful service setups is measured in the best cell. The
VS.SuccEstabCS.PSinDCH and VS.SuccEstabCS.PSinFACH counters apply to scenarios
where the UE establishes first a PS service and then a CS service.
Issue 03 (2015-06-30)

2724
BSC6900 UMTS
Figure 1-1172 Parallel handling of the alerting and RAB setup procedures in combined service
scenarios
The Figure show the combined service setup procedure of a CS called party after the parallel
handling of the alerting procedure is enabled. The measurement is triggered is triggered at point
B. When the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE,
the number of successful service setups is measured in the best cell. The
VS.SuccEstabCS.PSinDCH and VS.SuccEstabCS.PSinFACH counters apply to scenarios
where the UE establishes first a PS service and then a CS service.
Issue 03 (2015-06-30)

2725
BSC6900 UMTS
Figure 1-1173 Parallel handling of the alerting and RAB setup procedures in combined service
scenarios
Formula
None
Unit
None
Issue 03 (2015-06-30)

2726
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MultiRAB.SuccEstab.C
SPS
WRFD-010609

WRFD-01061505
WRFD-171202
Services
VS.MultiRAB.SuccEstab.P
SPS
WRFD-010609
WRFD-01061505

Services
VS.SuccEstabCS.PSinDCH
WRFD-010609
WRFD-01061505
WRFD-171202

Services
VS.SuccEstabCS.PSinFACH
WRFD-010609
WRFD-01061505
WRFD-171202

Services
Number of Normal Service Releases of Combined Services for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421832
VS.MultiRAB.CSNormRel.
CSPS
Number of Normal CS
Service Releases of CS+PS
73421834
VS.MultiRAB.PSNormRel.
PSPS
Number of Normal PS
Service Releases of PS+PS
73425977
VS.MultiRAB.CSPSNormR
el.CSPS
Number of Normally
Released CS and PS Services
in CS+PS Combined
Services

2727
BSC6900 UMTS
Description
This counter provides the number of normal combined service releases in the best cell.The
preceding counters complies with section "8 RANAP Procedures" in 3GPP TS 25.413(v10.10.0).
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-1174 RAB release procedure for combined services
The measurement is also triggered at point B as shown in the following figure. After receiving
an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the
RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE
message to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is User
Inactivity, Normal Release, Successful Relocation, or Network Optimization, or if the RNC has
sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated
Signalling Connection Release before the RNC receives the RAB ASSIGNMENT REQUEST
message, then the counter is measured in the best cell that the UE camps on according to the
combined service type and the released service type.
Issue 03 (2015-06-30)

2728
BSC6900 UMTS
Figure 1-1175 Successful RAB release procedure for combined services
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MultiRAB.CSNormRel.
CSPS
WRFD-010609

WRFD-01061505
Services
Issue 03 (2015-06-30)

2729
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
PSPS
WRFD-01061505
Services
VS.MultiRAB.CSPSNormR
el.CSPS
WRFD-010609

WRFD-01061505
Services
Number of Abnormal PS Service Releases of PS+PS Combined Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73421837
VS.MultiRAB.PSAbnormR
el.PSPS
Number of Abnormal PS
Service Releases of PS+PS
73421835
VS.MultiRAB.CSAbnormR
el.CSPS
Number of Abnormal CS
73425978
VS.MultiRAB.CSPSAbnor
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.The
Measurement point
As shown in point A of the figure, when a failure occurs, the RNC sends the CN an IU RELEASE
abnormal release (causes except "User Inactivity", "Normal Release", "UE Generated Signalling
Connection Release", "Successful Relocation", or "Network Optimization", for details, see
3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on according
to the types of the combined service and released service.
Issue 03 (2015-06-30)

2730
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
Relocation", or "Network Optimization", for details, see 3GPP TS 25.413), then the counter is
measured in the best cell that the UE camps on according to the types of the combined service
and released service.
Issue 03 (2015-06-30)

2731
BSC6900 UMTS
Figure 1-1177 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
Issue 03 (2015-06-30)

2732
BSC6900 UMTS
Figure 1-1178 Iu connection release procedure for combined services
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.PSPS
WRFD-010609

WRFD-01061505
Services
el.CSPS
WRFD-010609
WRFD-01061505

Services
VS.MultiRAB.CSPSAbnor
mRel.CSPS
WRFD-010609
WRFD-01061505

Services
Issue 03 (2015-06-30)

2733
BSC6900 UMTS
Number of Abnormal CS Service Releases During PS Service Setup for Cell

Counters
Counter ID
Counter Name
Counter Description
73421838
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.This counter complies with section "8 RANAP Procedures" in
3GPP TS 25.413(v10.10.0).
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", "UE Generated Signalling
3GPP TS 25.413), then the counter is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

2734
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", "UE Generated Signalling Connection
Release", "Successful Relocation", or "Network Optimization", for details, see 3GPP TS
25.413), then the counter is measured in the best cell that the UE camps on.
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
"Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the
Issue 03 (2015-06-30)

2735
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.PSAtt
WRFD-010609

WRFD-01061505
Services
Issue 03 (2015-06-30)

2736
BSC6900 UMTS
Number of Abnormal CS Service Releases During PS Service Release for Cell

Counters
Counter ID
Counter Name
Counter Description
73421839
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.This counter complies with section "8 RANAP
Procedures" in 3GPP TS 25.413(v10.10.0).
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
Issue 03 (2015-06-30)

2737
BSC6900 UMTS
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
"Network Optimization", for details, see 3GPP TS 25.413), then the counter is measured in the
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
Issue 03 (2015-06-30)

2738
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.PSRel
WRFD-010609

WRFD-01061505
Services
Issue 03 (2015-06-30)

2739
BSC6900 UMTS
Number of Normal PS Service Releases of CS+PS Combined Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73421840
CSPS
Number of Normal 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.This counter complies with section "8 RANAP Procedures"
in 3GPP TS 25.413(v10.10.0).
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.
Issue 03 (2015-06-30)

2740
BSC6900 UMTS
The measurement is also triggered at point B as shown in the following figure. After receiving
an RAB ASSIGNMENT REQUEST message with an RAB release request from the CN, the
RNC releases the corresponding RAB and then sends an RAB ASSIGNMENT RESPONSE
message to the CN. If the release cause in the RAB ASSIGNMENT REQUEST message is User
Inactivity, Normal Release, Successful Relocation, or Network Optimization, or if the RNC has
sent a release request with the cause of User Inactivity, Network Optimization, or UE Generated
Signalling Connection Release before the RNC receives the RAB ASSIGNMENT REQUEST
message, then the counter is measured in the best cell that the UE camps on according to the
combined service type and the released service type.
Figure 1-1186 Successful RAB release procedure for combined services
Formula
None
Unit
None
Issue 03 (2015-06-30)

2741
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
CSPS
WRFD-010609

WRFD-01061505
Services
Number of Abnormal PS Service Releases of CS+PS Combined Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73421841
el.CSPS
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.This counter complies with section "8 RANAP Procedures"
in 3GPP TS 25.413(v10.10.0).
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.
Issue 03 (2015-06-30)

2742
BSC6900 UMTS
COMMAND message which contains a cause value of abnormal release (causes except "User
Issue 03 (2015-06-30)

2743
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
Issue 03 (2015-06-30)

2744
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.CSPS
WRFD-010609

WRFD-01061505
Services
Issue 03 (2015-06-30)

2745
BSC6900 UMTS
Number of State Transition Attempts from CELL_PCH or URA_PCH to

CELL_DCH with the Cause Value of CS Service for Cell
Counters
Counter ID
Counter Name
Counter Description
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 provides 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.This counter complies with
section "8.3.1 Cell and URA update procedures" in 3GPP TS 25.331 (v10.13.0).
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
or Emergency Call in the Establishment cause information element (IE).
Issue 03 (2015-06-30)

2746
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttPSP2D.CSConv
WRFD-010609

WRFD-01061505
WRFD-010202
Services
URA-PCH, CELL-FACH)

CELL_DCH with the Cause Value of CS Service for Cell
Counters
Counter ID
Counter Name
Counter Description
73424029
VS.SuccPSP2D.CSConv

Transitions from
CELL_DCH with the Cause
Value of CS Service for Cell
Description
This counter provides 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 both 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,
Issue 03 (2015-06-30)

2747
BSC6900 UMTS
Terminating Conversational Call or Emergency Call in the Establishment cause information

element (IE).
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccPSP2D.CSConv
WRFD-010609

WRFD-01061505
WRFD-010202
Services
URA-PCH, CELL-FACH)
Issue 03 (2015-06-30)

2748
BSC6900 UMTS
Number of Abnormal PS Service Releases in the Case of Multi-RAB Services for

Cell during an inter-RAT handover( PS Resume Timer Expiry)
Counters
Counter ID
Counter Name
Counter Description
73425016
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.This counter complies with section "8 RANAP Procedures" in 3GPP TS 25.413
(v10.10.0).
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.
Issue 03 (2015-06-30)

2749
BSC6900 UMTS
Figure 1-1192 Procedure for an outgoing inter-RAT handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.ResumeExp
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

2750
BSC6900 UMTS
Number of Times CS Service in CS+PS Combined Services Is Abnormally

Released Due to a Cell Update Failure During RB Reconfiguration
Counters
Counter ID
Counter Name
Counter Description
73426879
el.PSRBconfig.CellUpd
Number of Times CS Service

in CS+PS Combined
Services Is Abnormally
Released Due to a Cell
Update Failure During RB
Reconfiguration
Description
This counter provides the number of CS RABs that are abnormally released due to a cell update
failure during the RB reconfiguration procedure in the best cell. This counter applies only to the
CS service in CS+PS combined services.This counter complies with section "8 RANAP
Measurement point
The measurement is triggered at point A, as shown in Figure 1. During an RB reconfiguration
procedure for CS+PS combined services, the cell update procedure fails, so the RNC sends a
RAB RELEASE REQUEST message to the CN. If the service to be released is a CS service in
CS+PS combined services and the CN responds with a RAB ASSIGNMENT REQUEST
message that carries a cause value other than "User Inactivity", "Normal Release", "UE
Optimization", this counter is measured in the best cell of the UE. For details about the cause
values indicating an abnormal release, see 3GPP TS 25.413.
CONFIRM message:
example.
Issue 03 (2015-06-30)

2751
BSC6900 UMTS
Figure 1-1193 Abnormal release of CS RABs of CS+PS combined services

procedure for CS+PS combined services, the cell update procedure fails, so the RNC sends a
CS+PS combined services and the CN responds with an IU RELEASE COMMAND message
that carries a cause value other than "User Inactivity", "Normal Release", "UE Generated
Signalling Connection Release", "Successful Relocation", or "Network Optimization", this
counter is measured in the best cell of the UE. For details about the cause values indicating an
example.
Issue 03 (2015-06-30)

2752
BSC6900 UMTS
Figure 1-1194 Iu connection release caused by the release of CS RABs of CS+PS combined
services

procedure for CS+PS combined services, the cell update procedure fails, so the RNC sends an
IU RELEASE REQUEST message to the CN. If the service to be released is a CS service in CS
+PS combined services and the CN responds with an IU RELEASE COMMAND message that
Connection Release", "Successful Relocation", or "Network Optimization", this counter is
measured in the best cell of the UE. For details about the cause values indicating an abnormal
example.
Issue 03 (2015-06-30)

2753
BSC6900 UMTS
Figure 1-1195 Abnormal release of the Iu connection for CS+PS combined services
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.PSRBconfig.CellUpd
WRFD-010609

WRFD-01061505
Services
Issue 03 (2015-06-30)

2754
BSC6900 UMTS
Number of Times CS Service in CS+PS Combined Services Is Abnormally

Released Due to a Cell Update Failure During Physical Channel Reconfiguration
Counters
Counter ID
Counter Name
Counter Description
73426880
el.PSPhyRecfg.CellUpd
Number of Times CS Service

in CS+PS Combined
Services Is Abnormally
Released Due to a Cell
Update Failure During
Physical Channel
Reconfiguration
Description
This counter provides the number of CS RABs that are abnormally released due to a cell update
failure during the physical channel reconfiguration procedure in the best cell. This counter
applies only to the CS service in CS+PS combined services.This counter complies with section
"8 RANAP Procedures" in 3GPP TS 25.413(v10.10.0).
Measurement point
The measurement is triggered at point A, as shown in Figure 1. During a physical channel
reconfiguration procedure (which is triggered by a serving cell change or CQI power offset
adjustment) for CS+PS combined services, the cell update procedure fails, so the RNC sends a
CS+PS combined services and the CN responds with a RAB ASSIGNMENT REQUEST
message that carries a cause value other than "User Inactivity", "Normal Release", "UE
Optimization", this counter is measured in the best cell of the UE. For details about the cause
values indicating an abnormal release, see 3GPP TS 25.413.
CONFIRM message:
example.
Issue 03 (2015-06-30)

2755
BSC6900 UMTS
Figure 1-1196 Abnormal release of CS RABs of CS+PS combined services

adjustment) for CS+PS combined services, the cell update procedure fails, so the RNC sends a
CS+PS combined services and the CN responds with an IU RELEASE COMMAND message
counter is measured in the best cell of the UE. For details about the cause values indicating an
example.
Issue 03 (2015-06-30)

2756
BSC6900 UMTS
Figure 1-1197 Iu connection release caused by the release of CS RABs of CS+PS combined
services

adjustment) for CS+PS combined services, the cell update procedure fails, so the RNC sends an
IU RELEASE REQUEST message to the CN. If the service to be released is a CS service in CS
+PS combined services and the CN responds with an IU RELEASE COMMAND message that
Connection Release", "Successful Relocation", or "Network Optimization", this counter is
measured in the best cell of the UE. For details about the cause values indicating an abnormal
example.
Issue 03 (2015-06-30)

2757
BSC6900 UMTS
Figure 1-1198 Abnormal release of the Iu connection for CS+PS combined services
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
el.PSPhyRecfg.CellUpd
WRFD-010609

WRFD-01061505
Services
Issue 03 (2015-06-30)

2758
BSC6900 UMTS
Number of CS RAB Setup Requests for PS+CS Combined Services for Cell (Fast
Setup)
Counters
Counter ID
Counter Name
Counter Description
73427966
VS.MultiRAB.AttEstabCS.
FastSetup

Requests for PS+CS
(Fast Setup)
Description
This counter provides the number of CS RAB setup requests that use the Fast Radio Bearer Setup
feature and are initiated by UEs processing PS services in the best cell.This counter complies
Measurement point
REQUEST message from the CS CN and determines that the RAB needs to be set up by using
UE is processing PS services.
Figure 1-1199 RAB setup procedure with PS RAB exist
Issue 03 (2015-06-30)

2759
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MultiRAB.AttEstabCS.
FastSetup
WRFD-160106
Number of Successful CS RAB Setups for PS+CS Combined Services for Cell (Fast
Setup)
Counters
Counter ID
Counter Name
Counter Description
73427967
VS.MultiRAB.SuccEstabCS
.FastSetup
RAB Setups for PS+CS
(Fast Setup)
Description
This counter provides the number of CS RABs that are successfully set up by using the Fast
Radio Bearer Setup feature for UEs processing PS services in the best cell.This counter complies
Measurement point
counter is measured in the best cell for the UE if the UE is processing PS services.
Issue 03 (2015-06-30)

2760
BSC6900 UMTS
Figure 1-1200 RAB setup procedure with PS RAB exist
The figure shows the combined service setup procedure of a CS called party after the parallel
handling of the alerting procedure is enabled. The measurement is triggered at point B. When
the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE, this counter
is measured in the best cell if the following conditions are met: The UE requests the establishment
of a CS service. The RB fast setup feature is used. The UE has already established a PS service.
Issue 03 (2015-06-30)

2761
BSC6900 UMTS
Figure 1-1201 Parallel handling of the alerting and RAB setup procedures when the UE has a
PS RAB
Formula
None
Unit
None
Issue 03 (2015-06-30)

2762
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MultiRAB.SuccEstabCS
.FastSetup
WRFD-160106
WRFD-171202
1.12.37 RAB Release Measurement <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.
Issue 03 (2015-06-30)

2763
BSC6900 UMTS
Figure 1-1202 Flow chart of call drop
Issue 03 (2015-06-30)

2764
BSC6900 UMTS
Figure 1-1203 Sub flow chart of call drop
Issue 03 (2015-06-30)

2765
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
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,
VS.RAB.AbnormRel.CS.CN,
VS.RAB.AbnormRel.CS.CSFB,
VS.RAB.AbnormRel.CS.CSFB.RF,
VS.RAB.AbnormRel.CS.IuTNL,
VS.RAB.AbnormRel.CS.IuupFail,
VS.RAB.AbnormRel.CS.Platinum

2766
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
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.NormRel.CS.CSFB,
VS.RAB.NormRel.CS.Platinum
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.CCHRelated, VS.RAB.NormRel.PS.NetOpt,
VS.RAB.NormRel.PS.0kbps.Timeout

2767
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
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.Silver,
VS.RAB.RelReqPS.BE.HSDPA.Cong.Copper,
VS.RAB.RelReqPS.BE.HSUPA.Cong.Gold
en,
VS.RAB.RelReqPS.BE.HSUPA.Cong.Silver,
VS.RAB.RelReqPS.BE.HSUPA.Cong.Copper, VS.RAB.AbnormRel.PS.CN,
VS.RAB.AbnormRel.PS.R99D2F,
VS.RAB.AbnormRel.PSR99.CellDCH.CellUpdt, VS.RAB.AbnormRel.PS.IuTNL

2768
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189568
VS.RAB.AbnormR
el.CS.RF.ULSync
Number of CS RABs
Abnormally
Released Due to RF
for Cell (Uplink
Synchronization
Fail)
Earlier than
BSC6900
V900R011
67192597
VS.RAB.AbnormR
el.CS.Str
Number of CS
Streaming RABs
Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67192598
VS.RAB.AbnormR
el.PS.Conv
Number of RABs
Abnormally
Released for PS
Conversational
Services for Cell
Earlier than
BSC6900
V900R011
67192599
VS.RAB.AbnormR
el.PS.Str
Number of RABs
Abnormally
Released for PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67192600
VS.RAB.NormRel.
CS.Str
Number of CS
Streaming RABs
Normally Released
for Cell
Earlier than
BSC6900
V900R011
67192601
VS.RAB.NormRel.
PS.Conv
Number of RABs
Normally Released
for PS
Conversational
Services for Cell
Earlier than
BSC6900
V900R011
67192602
VS.RAB.NormRel.
PS.Str
Number of RABs
Normally Released
for PS Streaming
Services for Cell
Earlier than
BSC6900
V900R011
67189572
VS.RAB.AbnormR
el.PS.RF.ULSync
Number of PS RABs
Abnormally
Released for Cell
(Uplink
Synchronization
Failure)
Earlier than
BSC6900
V900R011

2769
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190505
VS.RAB.AbnormR
el.CS.RF.UuNoReply
Number of CS RABs
Abnormally
Released Due to RF
for Cell (Failure in
the Radio Interface
Procedure)
Earlier than
BSC6900
V900R011
67190506
VS.RAB.AbnormR
el.PS.RF.UuNoReply
Number of PS RABs
Abnormally
Released Due to RF
for Cell (Failure in
the Radio Interface
Procedure)
Earlier than
BSC6900
V900R011
67179778
VS.RAB.AbnormR
el.CS
Number of CS RABs
Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67179777
VS.RAB.AbnormR
el.CS.RF
Number of CS RABs
Abnormally
Released Due to RF
for Cell
Earlier than
BSC6900
V900R011
67179779
VS.RAB.NormRel.
CS
Number of CS RABs
Normally Released
for Cell
Earlier than
BSC6900
V900R011
67179781
VS.RAB.AbnormR
el.PS
Number of PS RABs
Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67179782
VS.RAB.NormRel.
PS
Number of PS RABs
Normally Released
for Cell
Earlier than
BSC6900
V900R011
67179780
VS.RAB.AbnormR
el.PS.RF
Number of PS RABs
Abnormally
Released Due to RF
for Cell
Earlier than
BSC6900
V900R011
67180067
VS.RAB.AbnormR
el.CS.OM
Number of CS RAB
Release Requests for
Cell (O&M
Intervention)
Earlier than
BSC6900
V900R011
67180069
VS.RAB.AbnormR
el.CS.Preempt
Number of CS RAB
Cell (RAB
Preemption)
Earlier than
BSC6900
V900R011

2770
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180068
VS.RAB.AbnormR
el.CS.UTRANgen
Number of CS RAB
Abnormal Releases
Triggered by RNC
for Cell (UTRAN
Cause)
Earlier than
BSC6900
V900R011
67180074
VS.RAB.AbnormR
el.PS.OM
Number of PS RAB
Abnormal Released
Due to O&M
Intervention for Cell
Earlier than
BSC6900
V900R011
67180076
VS.RAB.AbnormR
el.PS.Preempt
Number of PS RAB
Abnormal Released
Due to RAB
Preemption for Cell
Earlier than
BSC6900
V900R011
67190467
VS.RAB.AbnormR
el.AMR.12.2
Number of CS
12.2kbit/s AMR
RABs Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67190468
VS.RAB.AbnormR
el.AMR.7.95
Number of CS
7.95kbit/s AMR
RABs Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67190469
VS.RAB.AbnormR
el.AMR.5.9
Number of CS
5.9kbit/s AMR
RABs Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67190470
VS.RAB.AbnormR
el.AMR.4.75
Number of CS
4.75kbit/s AMR
RABs Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67192201
VS.RAB.AbnormR
el.AMRWB.23.85
Number of CS
23.85kbit/s WB
AMR RABs
Abnormally
Released for Cell
BSC6900
V900R012
67192202
VS.RAB.AbnormR
el.AMRWB.23.05
Number of CS
23.05kbit/s WB
AMR RABs
Abnormally
Released for Cell
BSC6900
V900R012

2771
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192203
VS.RAB.AbnormR
el.AMRWB.19.85
Number of CS
19.85kbit/s WB
AMR RABs
Abnormally
Released for Cell
BSC6900
V900R012
67192204
VS.RAB.AbnormR
el.AMRWB.18.25
Number of CS
18.25kbit/s WB
AMR RABs
Abnormally
Released for Cell
BSC6900
V900R012
67192205
VS.RAB.AbnormR
el.AMRWB.15.85
Number of CS
15.85kbit/s WB
AMR RABs
Abnormally
Released for Cell
BSC6900
V900R012
67192206
VS.RAB.AbnormR
el.AMRWB.14.25
Number of CS
14.25kbit/s WB
AMR RABs
Abnormally
Released for Cell
BSC6900
V900R012
67192207
VS.RAB.AbnormR
el.AMRWB.12.65
Number of CS
12.65kbit/s WB
AMR RABs
Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67192208
VS.RAB.AbnormR
el.AMRWB.8.85
Number of CS
8.85kbit/s WB AMR
RABs Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67192209
VS.RAB.AbnormR
el.AMRWB.6.6
Number of CS
6.6kbit/s WB AMR
RABs Abnormally
Released for Cell
BSC6900
V900R012
67180077
VS.RAB.AbnormR
el.CS.RF.SRBReset
Number of CS RABs
Abnormally
Released for Cell
(Signaling RLC
Reset)
Earlier than
BSC6900
V900R011

2772
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180080
VS.RAB.AbnormR
el.CS.IuAAL2
Number of CS RABs
Abnormally
Released for Cell (Iu
Interface AAL2 Link
Failure)
Earlier than
BSC6900
V900R011
67180082
VS.RAB.AbnormR
el.AMR
Number of CS AMR
RABs Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67190518
VS.RAB.NormRel.
AMR
Number of CS AMR
RABs Normally
Released for Cell(not
including WBAMR)
Earlier than
BSC6900
V900R011
67180078
VS.RAB.AbnormR
el.PS.RF.SRBReset
Number of PS RABs
Abnormally
Released Due to
Signaling RLC Reset
for Cell
Earlier than
BSC6900
V900R011
67180079
VS.RAB.AbnormR
el.PS.RF.TRBReset
Number of PS RABs
Abnormally
Released for Cell
(Traffic RLC Reset)
Earlier than
BSC6900
V900R011
67180081
VS.RAB.AbnormR
el.PS.GTPULoss
Number of PS RABs
Abnormally
Released Due to
GTPU Failure for
Cell
Earlier than
BSC6900
V900R011
67190840
VS.RAB.AbnormR
el.PS.OLC
Number of PS
Domain RABs
Released Due to
Congestion for Cell
Earlier than
BSC6900
V900R011
67190841
VS.RAB.AbnormR
el.CS.OLC
Number of CS
Domain RABs
Released Due to
Congestion for Cell
Earlier than
BSC6900
V900R011
67192975
VS.RAB.RelReqPS
.BE.HSDPA.Cong.
Golden
Number of HSDPA
RABs Carrying
Golden Users BE
Traffic Released Due
to Congestion for
Cell
Earlier than
BSC6900
V900R011

2773
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192976
VS.RAB.RelReqPS
.BE.HSDPA.Cong.
Silver
Number of HSDPA
RABs Carrying
Silver Users BE
to Congestion for
Cell
Earlier than
BSC6900
V900R011
67192977
VS.RAB.RelReqPS
.BE.HSDPA.Cong.
Copper
Number of HSDPA
RABs Carrying
Copper Users BE
to Congestion for
Cell
Earlier than
BSC6900
V900R011
67192978
VS.RAB.RelReqPS
.BE.HSUPA.Cong.
Golden
Number of HSUPA
RABs Carrying
Golden Users BE
to Congestion for
Cell
Earlier than
BSC6900
V900R011
67192979
VS.RAB.RelReqPS
.BE.HSUPA.Cong.
Silver
Number of HSUPA
RABs Carrying
Silver Users BE
to Congestion for
Cell
Earlier than
BSC6900
V900R011
67192980
VS.RAB.RelReqPS
.BE.HSUPA.Cong.
Copper
Number of HSUPA
RABs Carrying
Copper Users BE
to Congestion for
Cell
Earlier than
BSC6900
V900R011
67191786
VS.RAB.NormRel.
CS64
Number of CS 64
kbit/s
Conversational
RABs Normally
Released for Cell
Earlier than
BSC6900
V900R011
67191791
VS.RAB.NormRel.
PS.CCH
Number of PS RABs
Mapped on CCH
Normally Released
for Cell
Earlier than
BSC6900
V900R011
67191818
VS.RAB.AbnormR
el.PS.CCH
Number of PS RABs
Mapped on CCH
Abnormally
Released for Cell
Earlier than
BSC6900
V900R011

2774
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191835
VS.RAB.NormRel.
PS.UEGen
Number of PS RABs
Normally Released
for Cell (UE
Signaling
Connection Release)
Earlier than
BSC6900
V900R011
67180083
VS.RAB.AbnormR
el.CS64
Number of CS
Conversational
64kbit/s RABs
Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67196204
VS.RAB.AbnormR
el.CS.HSPA.Conv
Number of CS over
HSPA RABs
Abnormally
Released for Cell
Earlier than
BSC6900
V900R011
67196205
VS.RAB.NormRel.
CS.HSPA.Conv
Number of CS over
HSPA RABs Normal
Released for Cell
Earlier than
BSC6900
V900R011
67196233
VS.RAB.NormRel.
VPLimit
Number of CS VP
RABs Released Due
to VP Forbiddance
for Cell
Earlier than
BSC6900
V900R011
67196302
VS.RAB.NormRel.
PS.0kbps.Timeout
Number of PS RABs
at 0 kbit/s Released
for Failure to Rate up
in the Best Cell
Earlier than
BSC6900
V900R011
73403833
VS.RAB.NormRel.
AMRWB.23.85
Number of CS
23.85kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012
73403834
VS.RAB.NormRel.
AMRWB.23.05
Number of CS
23.05kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012
73403835
VS.RAB.NormRel.
AMRWB.19.85
Number of CS
19.85kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012
73403836
VS.RAB.NormRel.
AMRWB.18.25
Number of CS
18.25kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012

2775
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403837
VS.RAB.NormRel.
AMRWB.15.85
Number of CS
15.85kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012
73403838
VS.RAB.NormRel.
AMRWB.14.25
Number of CS
14.25kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012
73403839
VS.RAB.NormRel.
AMRWB.12.65
Number of CS
12.65kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012
73403840
VS.RAB.NormRel.
AMRWB.8.85
Number of CS
8.85kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012
73403841
VS.RAB.NormRel.
AMRWB.6.60
Number of CS
6.60kbps AMRWB
RABs Normally
Released for cell
BSC6900
V900R012
73403842
VS.RAB.AbnormR
el.AMRWB
Number of CS
AMRWB RABs
Abnormally
Released for cell
BSC6900
V900R012
73403843
VS.RAB.NormRel.
AMRWB
Number of CS
AMRWB RABs
Normally Released
for cell
BSC6900
V900R012
73393843
VS.RAB.NormRel.
CS.UEGen
Number of CS RABs
Normally Released
for Cell (UE
Generated Signaling
Connection Release)
BSC6900
V900R012
73393845
VS.RAB.NormRel.
PS.BE
Number of RABs
Normally Released
for PS BE Services
for Cell
BSC6900
V900R012
73393846
VS.RAB.AbnormR
el.PS.BE
Number of RABs
Abnormally
Released for PS BE
Services for Cell
BSC6900
V900R012

2776
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394051
VS.RAB.AbnormR
el.AMR.RF
Number of CS AMR
RABs abnormal
release Due to RF
Failure for cell
BSC6900
V900R012
73394052
VS.RAB.AbnormR
el.CS64.RF
Number of CS
Conversational
64kbit/s RABs
abnormal released
due to RF failure for
cell
BSC6900
V900R012
73394073
VS.RAB.AbnormR
elPS.PTT
Number of RABs
Abnormally
Released for PTT
Services for Cell
BSC6900
V900R012
73394074
VS.RAB.NormRel
PS.PTT
Number of RABs
Normally Released
for PTT Services for
Cell
BSC6900
V900R012
73403805
VS.RAB.AbnormR
el.PSR99.RF
Number of PS R99
RABs abnormally
released Due to RF
Failure for cell
BSC6900
V900R012
73403806
VS.RAB.AbnormR
el.PSR99
Number of PS R99
RABs abnormally
released for cell
(Including RF
Failure)
BSC6900
V900R012
73403807
VS.RAB.NormRel.
PSR99
Number of PS R99
RAB successfully
released for cell
BSC6900
V900R012
73421882
VS.RAB.NormRel.
PS.PCH
Number of Normally
Released PS RABs
that Are in
CELL_PCH or
URA_PCH State for
Cell
BSC6900
V900R012
73421886
VS.RAB.AbnormR
el.PS.F2P
Number of call drops

During the F2P State
Transition for Cell
BSC6900
V900R012

2777
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421883
VS.RAB.AbnormR
el.PS.PCH
Number of
Abnormally
Released PS RABs
that Are in
CELL_PCH or
URA_PCH State for
Cell
BSC6900
V900R012
73422166
VS.RAB.AbnormR
el.PS.D2P
Number of RABs
Abnormally
Released for PS
Services during the
CELL_DCH to
CELL_PCH or
URA_PCH for Cell
BSC6900
V900R012
73422169
VS.RAB.AbnormR
el.PS.R99D2P
Number of RABs
Abnormally
Released for PS R99
Services during the
CELL_DCH to
CELL_PCH or
URA_PCH for Cell
BSC6900
V900R012
73423939
VS.RAB.AbnormR
el.CS.Security
Number of CS RABs
Abnormally
Released Due to
Security Mode
Procedure Failure for
Cell
BSC6900
V900R014
73423940
VS.RAB.AbnormR
el.PS.Security
Number of PS RABs
Abnormally
Released Due to
Security Mode
Procedure Failure for
Cell
BSC6900
V900R014
73425979
VS.RAB.NormRel.
CS.UEReEst
Number of Released
RABs Triggered by
the Second RRC
CONNECTION
REQUEST Message
from the Same UE in
the CS Domain for
Cell
BSC6900
V900R015C00

2778
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425980
VS.RAB.NormRel.
PS.UEReEst
Number of RAB
Releases Triggered
by the Second RRC
CONNECTION
REQUEST Message
from the Same UE in
the PS Domain for
Cell
BSC6900
V900R015C00
73425981
VS.RAB.NormRel.
PS.UEReEst.CCH
Related
Number of RAB
Releases Triggered
by the Second RRC
CONNECTION
REQUEST Message
from the Same UE in
the PS Domain in
Common Channelrelated Scenarios for
Cell
BSC6900
V900R015C00
73426205
VS.RAB.NormRel.
PS.NetOpt
Number of Released
PS RABs due to
Network
Optimization for Cell
BSC6900
V900R015C00
73426206
VS.RAB.AbnormR
el.PS.CN
Number of
Abnormally
Released PS RABs
Triggered by CN for
Cell
BSC6900
V900R015C00
73426207
VS.RAB.NormRel.
CS.NetOpt
Number of Released
CS RABs due to
Network
BSC6900
V900R015C00
73426209
VS.RAB.AbnormR
el.PS.UTRANgen
Number of
Abnormally
Released PS RABs
Triggered by RNC
for Cell
BSC6900
V900R015C00
73426208
VS.RAB.AbnormR
el.CS.CN
Number of
Abnormally
Released CS RABs
Triggered by CN for
Cell
BSC6900
V900R015C00

2779
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426881
VS.RAB.AbnormR
el.PS.R99D2F
Number of Times
RAB Is Abnormally
Released for R99
UEs During State
Transitions from
CELL_DCH to
CELL_FACH
BSC6900
V900R015C01
73426882
VS.RAB.AbnormR
el.PSR99.CellDCH.
CellUpdt
Number of Times PS
Services Are
Abnormally
Released for PS R99
UEs in CELL_DCH
State Due to Cell
Update Failures
BSC6900
V900R015C01
73428670
VS.RAB.AbnormR
el.CS.CSFB
Number of CS RABs
Abnormally
Released for CSFB
UEs for Cell
BSC6900
V900R016C00
73428671
VS.RAB.AbnormR
el.CS.CSFB.RF
Number of CS RABs
Abnormally
Released for CSFB
UEs Due to RF
Failures for Cell
BSC6900
V900R016C00
73428672
VS.RAB.NormRel.
CS.CSFB
Number of CS RABs
Normally Released
for CSFB UEs for
Cell
BSC6900
V900R016C00
73428903
VS.RAB.Rel.CS.C
NInit.AfterReEst
Number of Times
CN Initiates CS RAB
Releases After RL
Reestablishment and
Before Timer
Expires
BSC6900
V900R016C00
73428904
VS.RAB.Rel.CS.C
NInit.DuringReEst
Number of Times
CN Initiates CS RAB
Releases During RL
Reestablishment
BSC6900
V900R016C00
73429102
VS.RAB.AbnormR
el.PS.IuTNL
Number of
Abnormally
Released PS RABs
Triggered by the
RNC for Cell (TNL
Cause)
BSC6900
V900R017C00

2780
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429092
VS.RAB.AbnormR
el.CS.IuTNL
Number of
Abnormally
Released CS RABs
Triggered by the
RNC for Cell (TNL
Cause)
BSC6900
V900R017C00
73429099
VS.RAB.AbnormR
el.CS.IuupFail
Number of
Abnormally
Released CS RABs
Triggered by the
RNC for Cell (Iu UP
Failure Cause)
BSC6900
V900R017C00
73429470
VS.RAB.NormRel.
CS.Platinum
Number of CS RABs
Normally Released
for Platinum UEs for
Cell
BSC6900
V900R017C00
73429471
VS.RAB.AbnormR
el.CS.Platinum
Number of CS RABs
Abnormally
Released for
Platinum UEs for
Cell
BSC6900
V900R017C00
73430189
VS.RAB.AbnormR
el.PS.IRATResel.D
CHFACH
Number of PS RABs
Abnormally
Released for UEs in
the CELL_DCH and
CELL_FACH States
Due to Inter-RAT
Reselections for Cell
BSC6900
V900R017C10
73430190
VS.RAB.AbnormR
el.PS.IRATResel.P
CH
Number of PS RABs
Abnormally
Released for UEs in
the CELL_PCH and
URA_PCH States
Due to Inter-RAT
BSC6900
V900R017C10
73430220
VS.RAB.AbnormR
el.CS.Disconnect
Number of CS RABs
Abnormally
Released by the RNC
After the RNC
Receives the
DISCONNECT
Message for Cell
BSC6900
V900R017C10

2781
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430480
VS.RAB.AbnormR
el.CS.Str.PTPreem
pt
Number of
Abnormally
Released CS RABs
Carrying Streaming
Services for Cell
(Platinum User
Preemption)
BSC6900
V900R017C10
73430481
VS.RAB.AbnormR
el.CS.Conv.PTPree
mpt
Number of
Abnormally
Released CS RABs
Carrying
Conversational
Services for Cell
(Platinum User
Preemption)
BSC6900
V900R017C10
73430482
VS.RAB.AbnormR
el.PS.Bkg.PTPreem
pt
Number of
Abnormally
Released PS RABs
Carrying
Background
Services for Cell
(Platinum User
Preemption)
BSC6900
V900R017C10
73430483
VS.RAB.AbnormR
el.PS.Int.PTPreem
pt
Number of
Abnormally
Released PS RABs
Carrying Interactive
Services for Cell
(Platinum User
Preemption)
BSC6900
V900R017C10
73430484
VS.RAB.AbnormR
el.PS.Str.PTPreem
pt
Number of
Abnormally
Released PS RABs
Carrying Streaming
Services for Cell
(Platinum User
Preemption)
BSC6900
V900R017C10
73430485
VS.RAB.AbnormR
el.PS.Conv.PTPree
mpt
Number of
Abnormally
Released PS RABs
for Cell (Platinum
User Preemption)
BSC6900
V900R017C10

2782
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430559
VS.RAB.Rel.PS.F2
DNoRsp
Number of RRC
Connection Releases
Caused by No
Response to Three
Consecutive F2D
Requests for Cell
BSC6900
V900R017C10
73430562
VS.RAB.NormRel.
PS.UEReEst.PCH
Related
Number of RAB
Releases Triggered
by the Second RRC
CONNECTION
REQUEST Message
from the Same UE
That Is Processing
PS Services on the
PCH for Cell
BSC6900
V900R017C10
Counter
Sub Counter
VS.RAB.AbnormRel.CS
VS.RAB.AbnormRel.CS.OM
VS.RAB.AbnormRel.CS.Preempt
VS.RAB.AbnormRel.CS.UTRANgen
VS.RAB.AbnormRel.CS.OLC
VS.RAB.AbnormRel.CS.IuTNL
VS.RAB.AbnormRel.CS.IuupFail
VS.RAB.AbnormRel.PS
VS.RAB.AbnormRel.PS.OM
VS.RAB.AbnormRel.PS.Preempt
VS.RAB.AbnormRel.PS.GTPULoss
VS.RAB.AbnormRel.PS.OLC
VS.RAB.AbnormRel.PS.UTRANgen
VS.RAB.AbnormRel.PS.IuTNL
VS.RAB.AbnormRel.CS.RF.ULSync
VS.RAB.AbnormRel.CS.RF.UuNoReply
VS.RAB.AbnormRel.CS.RF.SRBReset
Issue 03 (2015-06-30)

2783
BSC6900 UMTS
Counter
Sub Counter
VS.RAB.AbnormRel.PS.RF.ULSync
VS.RAB.AbnormRel.PS.RF.UuNoReply
VS.RAB.AbnormRel.PS.RF.SRBReset
VS.RAB.AbnormRel.PS.RF.TRBReset
VS.RAB.AbnormRel.AMR.12.2
VS.RAB.NormRel.PSR99
VS.RAB.NormRel.PS.CCH
VS.RAB.NormRel.PS.UEReEst
VS.RAB.NormRel.PS.UEReEst.CCHRelated
VS.RAB.NormRel.CS
VS.RAB.AbnormRel.CS.CN
VS.RAB.NormRel.CS.UEGen
VS.RAB.NormRel.CS.UEReEst
VS.RAB.NormRel.CS.NetOpt
VS.RAB.NormRel.PS
VS.RAB.AbnormRel.PS.CN
VS.RAB.NormRel.PS.UEGen
VS.RAB.NormRel.PS.UEReEst
VS.RAB.NormRel.PS.NetOpt
VS.RAB.AbnormRel.CS.IuAAL2

Counter
Sub Counter
VS.RAB.AbnormRel.AMRWB
VS.RAB.AbnormRel.AMRWB.23.85
Issue 03 (2015-06-30)

2784
BSC6900 UMTS
Counter
Sub Counter
VS.RAB.NormRel.AMRWB
VS.RAB.NormRel.AMRWB.23.85
Number of CS RABs Abnormally Released for Different Services

Counters
Counter ID
Counter Name
Counter Description
67192597
for Cell
67179778
VS.RAB.AbnormRel.CS
Number of CS RABs
Cell
67180083
VS.RAB.AbnormRel.CS64
Number of CS
Conversational 64kbit/s
for Cell
67196204
PA.Conv

for Cell
73429471
VS.RAB.AbnormRel.CS.Pla
tinum
Number of CS RABs
Platinum UEs for Cell
Description
These measurement items take statistics of the number of CS RABs abnormally released
according to different types of service in the best cell.The preceding counters complies with
section "8 RANAP Procedures" in 3GPP TS 25.413(v10.10.0).
Issue 03 (2015-06-30)

2785
BSC6900 UMTS
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.
Issue 03 (2015-06-30)

2786
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.
Issue 03 (2015-06-30)

2787
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
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
PA.Conv
WRFD-010619

+

2788
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.CS.Pla
tinum
WRFD-150204
Number of CS RABs Abnormally Released Triggered by Different Causes

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179777
Number of CS RABs
RF for Cell
67189568
.ULSync
Number of CS RABs
RF for Cell (Uplink
Synchronization Fail)
67190505
.UuNoReply
Number of CS RABs
RF for Cell (Failure in the
Radio Interface Procedure)
67180067
VS.RAB.AbnormRel.CS.O
M

Requests for Cell (O&M
Intervention)
67180069
VS.RAB.AbnormRel.CS.Pr
eempt

Attempts for Cell (RAB
Preemption)
67180068
VS.RAB.AbnormRel.CS.U
TRANgen
Number of CS RAB
Abnormal Releases
Triggered by RNC for Cell
(UTRAN Cause)
67180077
.SRBReset
Number of CS RABs
Cell (Signaling RLC Reset)
67180080
VS.RAB.AbnormRel.CS.Iu
AAL2
Number of CS RABs
Cell (Iu Interface AAL2 Link
Failure)
67190841
LC
Number of CS Domain
RABs Released Due to
Congestion for Cell

2789
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394051
RF

abnormal release Due to RF
Failure for cell
73394052
RF
Number of CS
Conversational 64kbit/s
RABs abnormal released due
to RF failure for cell
73429092
TNL
Released CS RABs
Triggered by the RNC for
Cell (TNL Cause)
73429099
upFail
Released CS RABs
Triggered by the RNC for
Cell (Iu UP Failure Cause)
Description
These measurement items provide the number of CS RABs abnormally released triggered by
different causes in the best cell.The preceding counters complies with section "8 RANAP
Issue 03 (2015-06-30)
Counter Name
Description
Number of CS RABs Abnormally Released

Due to RF for Cell(The RF failure includes
Radio Connection With UE Lost and Failure
in the Radio Interface Procedure)
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

due to UU interface Fail(Fault over Iu: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)

2790
BSC6900 UMTS
Counter Name
Description
VS.RAB.AbnormRel.CS.UTRANgen

Due to causes on the UTRAN side for Cell
(Fault over Iu:Release due to UTRAN
Generated Reason)
VS.RAB.AbnormRel.CS.RF.SRBReset

due to signaling RLC reset(Fault over
Iu:Radio Connection With UE Lost)
VS.RAB.AbnormRel.CS.IuAAL2

Due to Iu Interface AAL2 Link Failure for
Cell(Fault over Iu:Signalling Transport
Resource Failure)
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)
This counter provides the number of

abnormally released CS RABs triggered by
the RNC due to TNL reasons over the Iu
interface
VS.RAB.AbnormRel.CS.IuupFail

abnormally released CS RABs triggered by
the RNC due to Iu UP failure reasons over the
Iu interface.
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.
Issue 03 (2015-06-30)

2791
BSC6900 UMTS
Issue 03 (2015-06-30)

2792
BSC6900 UMTS
Issue 03 (2015-06-30)

2793
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
.ULSync
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
.UuNoReply
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2794
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
M
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.CS.Pr
eempt
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010505

VS.RAB.AbnormRel.CS.U
TRANgen
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
.SRBReset
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
AAL2
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
LC
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-020107
Overload Control
Issue 03 (2015-06-30)
RF
WRFD-010501
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RF
WRFD-010501
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2795
BSC6900 UMTS
Number of wideband and narrowband AMR services RABs Abnormally Released

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180082

Cell
67190467
12.2
AMR RABs Abnormally
Released for Cell
67190468
7.95
AMR RABs Abnormally
Released for Cell
67190469
5.9
AMR RABs Abnormally
Released for Cell
67190470
4.75
AMR RABs Abnormally
Released for Cell
67192201
WB.23.85
WB AMR RABs
Cell
67192202
WB.23.05
WB AMR RABs
Cell
67192203
WB.19.85
WB AMR RABs
Cell
67192204
WB.18.25
WB AMR RABs
Cell
67192205
WB.15.85
WB AMR RABs
Cell

2796
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192206
WB.14.25
WB AMR RABs
Cell
67192207
WB.12.65
WB AMR RABs
Cell
67192208
WB.8.85
Number of CS 8.85kbit/s WB
AMR RABs Abnormally
Released for Cell
67192209
WB.6.6
Number of CS 6.6kbit/s WB
AMR RABs Abnormally
Released for Cell
73403842
WB
Number of CS AMRWB
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.The preceding counters complies with section "8 RANAP Procedures" in 3GPP
TS 25.413(v10.10.0).
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.
Issue 03 (2015-06-30)

2797
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.
Issue 03 (2015-06-30)

2798
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.
Issue 03 (2015-06-30)

2799
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010501
12.2
WRFD-010501
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
7.95
WRFD-010501
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2800
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
5.9
WRFD-010501
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
4.75
WRFD-010501
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB.23.85
WRFD-010613

Rate Wide Band)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB.23.05
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB.19.85
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB.18.25
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB.15.85
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

2801
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WB.14.25
WRFD-010613

Rate Wide Band)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB.12.65
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB.8.85
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB.6.6
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WB
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RABs Abnormally Released Due to Security Mode Procedure Failure

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423939
VS.RAB.AbnormRel.CS.Se
curity
Number of CS RABs
Failure for Cell

2802
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73423940
VS.RAB.AbnormRel.PS.Security
Number of PS RABs
Failure for Cell
Description
This counter measures the number of RABs abnormally released due to a security mode
procedure failure in the best cell.This counter complies with section "8 RANAP Procedures" in
3GPP TS 25.413(v10.10.0).
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-1213 Release procedure due to security mode failure
Formula
None
Issue 03 (2015-06-30)

2803
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.CS.Se
curity
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.PS.Security
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Abnormally Released RABs Triggered by CN for Cell

Counters
Counter ID
Counter Name
Counter Description
73426208
VS.RAB.AbnormRel.CS.C
N
Released CS RABs
Triggered by CN for Cell
73426206
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.The preceding counters complies with section "8
RANAP Procedures" in 3GPP TS 25.413(v10.10.0).
Measurement point
The measurement is triggered at point B shown in figure 1 when both of the following conditions
are met: The RNC receives a RAB ASSIGNMENT REQUEST message from the CS 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.
Issue 03 (2015-06-30)

2804
BSC6900 UMTS
The measurement is triggered at point A shown in figure 2 when both of the following conditions
are met: The RNC receives an IU RELEASE COMMAND message from the CS 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 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
Issue 03 (2015-06-30)

2805
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.CS.C
N
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of CS RABs Abnormally Released for CSFB UEs for Cell

Counters
Counter ID
Counter Name
Counter Description
73428670
VS.RAB.AbnormRel.CS.CS
FB
Number of CS RABs
CSFB UEs for Cell
73428671
FB.RF
Number of CS RABs
CSFB UEs Due to RF
Failures for Cell
Description
These counters provide the number of CS RABs that are abnormally released for CSFB UEs in
the best cell. They are used to locate problems of interoperation between UMTS and LTE.The
Issue 03 (2015-06-30)
Counter Name
Description
VS.RAB.AbnormRel.CS.CSFB
This counter measures the number of CS

RABs abnormally released for UEs that has
performed CSFB in the best cell. The cause
values indicating abnormal CS RAB releases
are those other than User Inactivity, Normal
Release, Successful Relocation, Network
Optimization, and UE Generated Signalling
Connection Release

2806
BSC6900 UMTS
Counter Name
Description
VS.RAB.AbnormRel.CS.CSFB.RF
This counter measures the number of CS

RABs released for UEs that has performed
CSFB in the best cell due to RF failures. The
cause values reflected on the Iu interface for
RF failures are "Radio Connection With UE
Lost" and "Failure in the Radio Interface
Procedure"
Measurement point
The measurement is triggered at point A shown in Figure 1. After the CS RAB is set up for a
UE that has performed a CSFB, an exception occurs and the RNC sends a RAB RELEASE
REQUEST message to the CN. If the CN returns a RAB ASSIGNMENT REQUEST message
but the cause value is not any of the following normal values: User Inactivity, Normal Release,
Successful Relocation, Network Optimization, and UE Generated Signalling Connection
Release, which are specified in 3GPP TS 25.413, the CS RAB will be abnormally released for
the CSFB UE. Then the RNC sends a RAB ASSIGNMENT REPONSE message to the CN and
measures the number of CS RABs abnormally released for CSFB UEs due to the corresponding
cause value in the best cell.
UE that has performed a CSFB, an exception occurs and the RNC sends a RAB RELEASE
REQUEST message to the CN. If the CN returns an IU RELEASE COMMAND message but
Issue 03 (2015-06-30)

2807
BSC6900 UMTS
the cause value is not any of the following normal values: User Inactivity, Normal Release,
the CSFB UE. Then the RNC sends an IU RELEASE REQUEST message to the CN and
UE that has performed a CSFB, an exception occurs and the RNC sends an IU RELEASE
REQUEST message to the CN. If the CN returns an IU RELEASE COMMAND message but
the cause value is not any of the following normal values: User Inactivity, Normal Release,
the CSFB UE. Then the RNC sends an IU RELEASE REQUEST message to the CN and
Issue 03 (2015-06-30)

2808
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
FB
WRFD-140224

RIM
WRFD-140102

LTE Emergency Calls
FB.RF
WRFD-140224
WRFD-140102

RIM
LTE Emergency Calls
Issue 03 (2015-06-30)

2809
BSC6900 UMTS
Number of CS RABs Normally Released for Cell

Counters
Counter ID
Counter Name
Counter Description
67179779
VS.RAB.NormRel.CS
Number of CS RABs
73428672
VS.RAB.NormRel.CS.CSF
B
Number of CS RABs
Normally Released for CSFB
UEs for Cell
73429470
Number of CS RABs
Normally Released for
Description
The measurement items provide the number of CS RABs normally released in the best cell.The
Measurement point
The measurement is triggered at point A as shown in Figure 1. When the RNC receives an IU
COMPLETE message to the CN. If the released RAB belongs to the CS domain and if the cause
value in the IU RELEASE COMMAND message is "User Inactivity", "Normal Release",
"Successful Relocation", or "Network Optimization", or the RNC initiated the release procedure
by sending an IU RELEASE REQUEST message or a RAB RELEASE REQUEST message
with the cause value of "User Inactivity", "Network Optimization", or "UE Generated Signalling
Connection Release", the RNC measures the corresponding counter in the best cell where the
UE camps.
Issue 03 (2015-06-30)

2810
BSC6900 UMTS
The measurement is triggered at point B as shown in Figure 2.When the RNC receives a RAB
If the released RAB belongs to the CS domain and if the cause value in the RAB ASSIGNMENT
REQUEST message is "User Inactivity", "Normal Release", "Successful Relocation", or
"Network Optimization", or the RNC initiated the release procedure by sending an IU RELEASE
REQUEST message or a RAB RELEASE REQUEST message with the cause value of "User
Inactivity", "Network Optimization", or "UE Generated Signalling Connection Release", the
RNC measures the corresponding counter in the best cell where the UE camps.
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.
Issue 03 (2015-06-30)

2811
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
Issue 03 (2015-06-30)

2812
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.CS
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.CS.CSF
B
WRFD-140224

RIM
WRFD-140102

LTE Emergency Calls
WRFD-150204
Number of CS RABs Normally Released for Different Services

Counters
Counter ID
Counter Name
Counter Description
67192600
VS.RAB.NormRel.CS.Str
Cell
67190518
VS.RAB.NormRel.AMR

(not including WB-AMR)
67191786
VS.RAB.NormRel.CS64
Number of CS 64 kbit/s
Conversational RABs
67196205
A.Conv

Cell
Description
The measurement items provide the number of RABs normally released according to different
CS service type in the best cell.The preceding counters complies with section "8 RANAP
Measurement point
Issue 03 (2015-06-30)

2813
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 if the released RAB belongs to CS
domain.
Signalling Connection Release",the RNC measures the items by the service type in the best cell
which the UE camps on if the released RAB belongs to CS domain.
Issue 03 (2015-06-30)

2814
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
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
VS.RAB.NormRel.CS64
WRFD-010501
A.Conv
WRFD-010619

+

2815
BSC6900 UMTS
Number of CS VP RABs Released Due to VP Forbiddance for Cell

Counters
Counter ID
Counter Name
Counter Description
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.This counter complies with section "8 RANAP Procedures" in 3GPP TS 25.413
(v10.10.0).
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.
Issue 03 (2015-06-30)

2816
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.VPLimit
WRFD-020130
Videophone Service
Restriction
Number of AMRWB RABs Normally Released for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73403833
VS.RAB.NormRel.AMRW
B.23.85
Number of CS 23.85kbps
AMRWB RABs Normally
Released for cell

2817
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73403834
VS.RAB.NormRel.AMRW
B.23.05
AMRWB RABs Normally
Released for cell
73403835
VS.RAB.NormRel.AMRW
B.19.85
AMRWB RABs Normally
Released for cell
73403836
VS.RAB.NormRel.AMRW
B.18.25
AMRWB RABs Normally
Released for cell
73403837
VS.RAB.NormRel.AMRW
B.15.85
AMRWB RABs Normally
Released for cell
73403838
VS.RAB.NormRel.AMRW
B.14.25
AMRWB RABs Normally
Released for cell
73403839
VS.RAB.NormRel.AMRW
B.12.65
AMRWB RABs Normally
Released for cell
73403840
VS.RAB.NormRel.AMRW
B.8.85
AMRWB RABs Normally
Released for cell
73403841
VS.RAB.NormRel.AMRW
B.6.60
AMRWB RABs Normally
Released for cell
73403843
VS.RAB.NormRel.AMRW
B
Number of CS AMRWB
cell
Description
The measurement item provides the number of CS AMRWB RABs of different rates normally
released in the best cell.The preceding counters complies with section "8 RANAP Procedures"
in 3GPP TS 25.413(v10.10.0).
Measurement point
Issue 03 (2015-06-30)

2818
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.
Issue 03 (2015-06-30)

2819
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.AMRW
B.23.85
WRFD-010613

Rate Wide Band)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.AMRW
B.23.05
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

2820
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.AMRW
B.19.85
WRFD-010613

Rate Wide Band)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.AMRW
B.18.25
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.AMRW
B.15.85
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.AMRW
B.14.25
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.AMRW
B.12.65
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.AMRW
B.8.85
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.AMRW
B.6.60
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

2821
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.AMRW
B
WRFD-010613

Rate Wide Band)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of CS RABs Normally Released Due to Uplink Signaling Connection

Release
Counters
Counter ID
Counter Name
Counter Description
73393843
Number of CS RABs
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.This counter complies with section
"8 RANAP Procedures" in 3GPP TS 25.413(v10.10.0).
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.
Issue 03 (2015-06-30)

2822
BSC6900 UMTS
Figure 1-1229 UL signalling connection release procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Released CS RABs due to Network Optimization for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426207
Number of Released CS
RABs due to Network

2823
BSC6900 UMTS
Description
This counter measures the number of released CS RABs due to network optimization.This
counter complies with section "8 RANAP Procedures" in 3GPP TS 25.413(v10.10.0).
Measurement point
The measurement is triggered at point A shown in figure 1 when the RNC sends a RAB
RELEASE REQUEST message to the CN and receives from the CN a RAB ASSIGNMENT
REQUEST message containing the cause value Network Optimization. If the RAB to be released
is for CS services, this counter is measured in the best cell that the UE camps on.
RELEASE REQUEST message to the CN and receives from the CN a IU RELEASE
COMMAND message containing the cause value Network Optimization. If the RAB to be
released is for CS services, this counter is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

2824
BSC6900 UMTS
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,
Issue 03 (2015-06-30)

2825
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RABs Normally Released for Cell

Counters
Counter ID
Counter Name
Counter Description
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.This
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 PS domain.
Issue 03 (2015-06-30)

2826
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 PS domain.
Issue 03 (2015-06-30)

2827
BSC6900 UMTS
The measurement is triggered at point B shown in figure 3 when both of the following conditions
are met: The RNC receives from the PS CN a RAB ASSIGNMENT REQUEST message in
which the cause value is not Normal Release, Successful Relocation, User Inactivity, 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
in the best cell that the UE camps on.
Issue 03 (2015-06-30)

2828
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 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
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.PS
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2829
BSC6900 UMTS
Number of PS RABs Normally Released According to Different Services and

Different Channel-beared Type
Counters
Counter ID
Counter Name
Counter Description
67192601

Released for PS
Cell
67192602
VS.RAB.NormRel.PS.Str

Released for PS Streaming
Services for Cell
67191791
Number of PS RABs Mapped

on CCH Normally Released
for Cell
73393845
VS.RAB.NormRel.PS.BE

Released for PS BE Services
for Cell
73394074
VS.RAB.NormRelPS.PTT

Released for PTT Services
for Cell
73403807

successfully released 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.The preceding
counters complies with section "8 RANAP Procedures" in 3GPP TS 25.413(v10.10.0).
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 PS domain.
Issue 03 (2015-06-30)

2830
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 PS domain.
Issue 03 (2015-06-30)

2831
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010501
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010502
Streaming QoS Class
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.PS.Str
Issue 03 (2015-06-30)

2832
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
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
and Release
WRFD-010504
WRFD-010503

VS.RAB.NormRelPS.PTT
WRFD-020134
Push to Talk
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Normally Released PS RABs that Are in CELL_PCH or URA_PCH State

for Cell
Counters
Counter ID
Counter Name
Counter Description
73421882
VS.RAB.NormRel.PS.PCH
Number of Normally
State for Cell
Description
This counter provides the number of normally released PS RABs that are in CELL_PCH or
URA_PCH state. The release of RABs in URA_PCH state is measured in the last cell that the
UE camps on before entering the URA_PCH state.This counter complies with section "8
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
Issue 03 (2015-06-30)

2833
BSC6900 UMTS
Release" before the RNC receives the IU RELEASE COMMAND message, then a counter is
measured in the cell that the UE camps on according to the channel type if the RAB is intended
for PS services.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.PS.PCH
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2834
BSC6900 UMTS
Number of PS RABs Normally Released due to UE Signaling Connection Release

Counters
Counter ID
Counter Name
Counter Description
67191835
Number of PS RABs
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.This counter complies with section "8
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.
Figure 1-1240 UL signalling connection release procedure
Formula
None
Issue 03 (2015-06-30)

2835
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RAB Releases Triggered by the Second RRC CONNECTION

REQUEST Message from the Same UE
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425980
VS.RAB.NormRel.PS.UER
eEst
Number of RAB Releases

Triggered by the Second
RRC CONNECTION
REQUEST Message from
the Same UE in the PS
Domain for Cell
73425979
VS.RAB.NormRel.CS.UER
eEst
Number of Released RABs

RRC CONNECTION
the Same UE in the CS
Domain for Cell
73425981
eEst.CCHRelated

RRC CONNECTION
the Same UE in the PS
Domain in Common
Channel-related Scenarios
for Cell
73430562
eEst.PCHRelated

RRC CONNECTION
the Same UE That Is
Processing PS Services on
the PCH for Cell

2836
BSC6900 UMTS
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.The
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
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.
If the RNC returns an IU RELEASE COMPLETE message to the CN, the UE is experiencing
a D2P or F2P or P2F or P2D 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.PCHRelated is measured in the best cell where the UE camps.
P2F refers to the process when a UE moves from the CELL_PCH state to the CELL_FACH
state. P2D refers to the process when a UE moves from the CELL_PCH state to the CELL_DCH
state.
Issue 03 (2015-06-30)

2837
BSC6900 UMTS
Figure 1-1241 Iu connection release procedure initiated by the RNC upon UEs' RRC connection
reestablishment
Formula
None
Unit
None
Issue 03 (2015-06-30)

2838
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
eEst
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.NormRel.CS.UER
eEst
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
eEst.CCHRelated
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
eEst.PCHRelated
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Released PS RABs due to Network Optimization for Cell

Counters
Counter ID
Counter Name
Counter Description
73426205
Number of Released PS
RABs due to Network
Description
This counter measures the number of released PS radio access bearers (RABs) due to network
optimization.This counter complies with section "8 RANAP Procedures" in 3GPP TS 25.413
(v10.10.0).
Measurement point
RELEASE REQUEST message to the CN and receives from the CN a RAB ASSIGNMENT
REQUEST message containing the cause value Network Optimization. If the RAB to be released
is for PS services, this counter is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

2839
BSC6900 UMTS
RELEASE REQUEST message to the CN and receives from the CN an IU RELEASE
COMMAND message containing the cause value Network Optimization. If the RAB to be
released is for PS services, this counter is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

2840
BSC6900 UMTS
The measurement is triggered at point A shown in figure 3 when the RNC sends an IU RELEASE
REQUEST message to the CN and receives from the CN an IU RELEASE COMMAND message
containing the cause value Network Optimization. If the RAB to be released is for PS services,
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2841
BSC6900 UMTS
Times of PS RAB of 0kbit/s released for failed to rate up

Counters
Counter ID
Counter Name
Counter Description
67196302
VS.RAB.NormRel.PS.
0kbps.Timeout
Number of PS RABs at 0
kbit/s Released for Failure to
Rate up in the Best Cell
Description
This measurement item provides the times of releasing RAB of 0kbit/s for failing to rate up
before timer expiry in the best cell.This counter complies with section "8 RANAP Procedures"
in 3GPP TS 25.413(v10.10.0).
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
the failure of 0 kbit/s PS RAB rating up before timer expiry, it measures the number of times of
releasing RAB of 0 kbit/s for failing to rate up before timer expiry in the best cell.
Issue 03 (2015-06-30)

2842
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.NormRel.PS.
0kbps.Timeout
WRFD-021101
Dynamic Channel
(DCCC)

2843
BSC6900 UMTS
Number of PS RABs Abnormally Released for Different Services Type and

Channel-beared Type
Counters
Counter ID
Counter Name
Counter Description
67192598
nv
Number of RABs
Cell
67192599
Number of RABs
67179781
VS.RAB.AbnormRel.PS
Number of PS RABs
Cell
67191818
H
Number of PS RABs Mapped

on CCH Abnormally
Released for Cell
73393846
Number of RABs
73394073
VS.RAB.AbnormRelPS.PT
T
Number of RABs
PTT Services for Cell
73403806
VS.RAB.AbnormRel.PSR9
9
Number of PS R99 RABs

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.The
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.
Issue 03 (2015-06-30)

2844
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
Issue 03 (2015-06-30)

2845
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
Issue 03 (2015-06-30)

2846
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
nv
WRFD-010501
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010502
Streaming QoS Class
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2847
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.PS
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
H
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010503
WRFD-010504

VS.RAB.AbnormRelPS.PT
T
WRFD-020134
Push to Talk
9
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of PS RABs Abnormally Released Due to Different Causes

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180081
VS.RAB.AbnormRel.PS.GT
PULoss
Number of PS RABs
GTPU Failure for Cell
67189572
.ULSync
Number of PS RABs
Cell (Uplink
Synchronization Failure)
67190506
.UuNoReply
Number of PS RABs
RF for Cell (Failure in the
67179780
Number of PS RABs
RF for Cell

2848
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67180074
VS.RAB.AbnormRel.PS.O
M
Number of PS RAB
O&M Intervention for Cell
67180076
VS.RAB.AbnormRel.PS.Pre
empt
Number of PS RAB
RAB Preemption for Cell
67180078
.SRBReset
Number of PS RABs
Signaling RLC Reset for Cell
67180079
.TRBReset
Number of PS RABs
Cell (Traffic RLC Reset)
67190840
VS.RAB.AbnormRel.PS.OL
C
Number of PS Domain RABs

Released Due to Congestion
for Cell
73403805
9.RF
Number of PS R99 RABs

abnormally released Due to
RF Failure for cell
73426209
VS.RAB.AbnormRel.PS.UT
RANgen
by RNC for Cell
73429102
VS.RAB.AbnormRel.PS.Iu
TNL
by the RNC for Cell (TNL
Cause)
Description
These counters provide the number of PS RABs abnormally released due to different causes in
the best cell.The preceding counters complies with section "8 RANAP Procedures" in 3GPP TS
25.413(v10.10.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.RAB.AbnormRel.PS.GTPULoss
Number of PS RABs Abnormally Released

Due to GTPU Failure for Cell(GTP
Resources Unavailable)
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)

2849
BSC6900 UMTS
Counter Name
Description
VS.RAB.AbnormRel.PS.RF.UuNoReply

to UU interface Fail(Fault over Iu:Failure in
the Radio Interface Procedure)

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

to signaling RLC reset(Fault over Iu:Radio
Connection With UE Lost)
VS.RAB.AbnormRel.PS.RF.TRBReset

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(Reduce Load in
Serving 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

Due to causes on the UTRAN side for Cell
(Fault over Iu:Release due to UTRAN
Generated Reason)
VS.RAB.AbnormRel.PS.IuTNL

abnormally released PS RABs triggered by
the RNC due to TNL reasons over the Iu
interface.
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 Relocation",
"Network Optimization" or "UE Generated Signalling Connection Release"(reference to 3GPP
Issue 03 (2015-06-30)

2850
BSC6900 UMTS
TS 25.413), the RNC measures these counters in the best cell where the UE camps on according
to different causes.
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 counters in the best cell where the UE camps on according to different causes.
Issue 03 (2015-06-30)

2851
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 counters in the best cell where the UE camps on according to different causes.
Issue 03 (2015-06-30)

2852
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.PS.GT
PULoss
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
.ULSync
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
.UuNoReply
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2853
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.PS.O
M
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.PS.Pre
empt
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010505
Issue 03 (2015-06-30)
.SRBReset
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
.TRBReset
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.PS.OL
C
WRFD-020107
Overload Control
9.RF
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RAB.AbnormRel.PS.UT
RANgen
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2854
BSC6900 UMTS
Number of Abnormally Released PS RABs that Are in CELL_PCH or URA_PCH

State for Cell
Counters
Counter ID
Counter Name
Counter Description
73421883
H
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.This counter complies with section "8
Measurement point
The measurement is triggered at point A as shown in the following figure. When a failure occurs,
the RNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the
CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND
message contains a cause value of abnormal release (causes except "User Inactivity", "Normal
Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling
Connection Release", for details, see 3GPP TS 25.413), then a counter is measured in the best
cell that the UE camps on according to the channel type if the RAB carries PS services.
Issue 03 (2015-06-30)

2855
BSC6900 UMTS
the RNC sends the CN an RAB RELEASE REQUEST message. After receiving the message,
the CN sends an RAB ASSIGNMENT REQUEST message to the RNC. If the RAB
ASSIGNMENT REQUEST message contains a cause value of abnormal release (causes except
"User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE
Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then a counter is
measured in the best cell that the UE camps on according to the channel type if the RAB carries
PS services.
the RNC sends the CN an RAB RELEASE REQUEST message. After receiving the message,
the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE
COMMAND message contains a cause value of abnormal release (causes except "User
Inactivity", "Normal Release", "Successful Relocation", "Network Optimization" or "UE
Generated Signalling Connection Release", for details, see 3GPP TS 25.413), then a counter is
measured in the best cell that the UE camps on according to the channel type if the RAB carries
PS services.
Issue 03 (2015-06-30)

2856
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
H
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2857
BSC6900 UMTS
Number of RABs Abnormally Released for PS Services during the Different State
Transition
Counters
Counter ID
Counter Name
Counter Description
73422166
VS.RAB.AbnormRel.PS.D2
P
Number of RABs
Services during the State
Transition from CELL_DCH
for Cell
73421886
VS.RAB.AbnormRel.PS.F2
P
Number of call drops During

the F2P State Transition for
Cell
73422169
VS.RAB.AbnormRel.PS.R9
9D2P
Number of RABs
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.The preceding counters complies with section "8
Issue 03 (2015-06-30)
Counter Name
Description
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

PS Services during the State Transition from
CELL_FACH to CELL_PCH or URA_PCH
VS.RAB.AbnormRel.PS.R99D2P

PS R99 Services during the State Transition
from CELL_DCH to CELL_PCH or
URA_PCH

2858
BSC6900 UMTS
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
value except "User Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization", or "UE Generated Signalling Connection Release", for details, see 3GPP TS
25.413), then this counter is measured in the best cell that the UE camps on according to different
State Transition if the RAB is for a PS service.
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.
Issue 03 (2015-06-30)

2859
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.
Issue 03 (2015-06-30)

2860
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.PS.D2
P
WRFD-010202

URA-PCH, CELL-FACH)
VS.RAB.AbnormRel.PS.F2
P
WRFD-010202

URA-PCH, CELL-FACH)
9D2P
WRFD-010202

URA-PCH, CELL-FACH)

2861
BSC6900 UMTS
Number of PS BE RABs Beared on HSPA Released due to Cell Congestion or

preemption
Counters
Counter ID
Counter Name
Counter Description
67192975
VS.RAB.RelReqPS.BE.HS
DPA.Cong.Golden

Carrying Golden Users BE
Traffic Released Due to
Congestion for Cell
67192976
DPA.Cong.Silver

Carrying Silver Users BE
Congestion for Cell
67192977
DPA.Cong.Copper

Carrying Copper Users BE
Congestion for Cell
67192978
UPA.Cong.Golden

Carrying Golden Users BE
Congestion for Cell
67192979
UPA.Cong.Silver

Carrying Silver Users BE
Congestion for Cell
67192980
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 DCHSDPA users, this counter is measured only in the cell with the primary carrier.The preceding
counters complies with section "8.2 Radio Bearer control procedures" in 3GPP TS 25.413
(v10.10.0).
Issue 03 (2015-06-30)

2862
BSC6900 UMTS
Counter Name
Description
VS.RAB.RelReqPS.BE.HSDPA.Cong.Silver
Number of released silver PS BE RABs

beared on HSDPA triggered by the RNC due
to CELL congestion
VS.RAB.RelReqPS.BE.HSDPA.Cong.Copper
Number of released copper users PS BE

RABs beared on HSDPA triggered by the
RNC due to CELL congestion
VS.RAB.RelReqPS.BE.HSUPA.Cong.Gold
en
Number of released golden users PS BE

RABs beared on HSUPA triggered by the
VS.RAB.RelReqPS.BE.HSUPA.Cong.Silver
Number of released silver users PS BE RABs

beared on HSUPA triggered by the RNC due
to CELL congestion
VS.RAB.RelReqPS.BE.HSUPA.Cong.Copper
Number of released copper users PS BE

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-1259 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.
Issue 03 (2015-06-30)

2863
BSC6900 UMTS
Figure 1-1260 IU connection release procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
DPA.Cong.Golden
WRFD-010610
HSDPA Introduction
Package
WRFD-020107
Overload Control
DPA.Cong.Silver
WRFD-010610
WRFD-020107
HSDPA Introduction
Package
Overload Control
DPA.Cong.Copper
WRFD-010610
WRFD-020107
HSDPA Introduction
Package
Overload Control
UPA.Cong.Golden
WRFD-010612
WRFD-020107
HSUPA Introduction
Package
Overload Control
Issue 03 (2015-06-30)

2864
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
UPA.Cong.Silver
WRFD-010612
HSUPA Introduction
Package
WRFD-020107
Overload Control
UPA.Cong.Copper
WRFD-010612
WRFD-020107
HSUPA Introduction
Package
Overload Control
Number of Times RAB Is Abnormally Released for R99 UEs During State
Transitions from CELL_DCH to CELL_FACH
Counters
Counter ID
Counter Name
Counter Description
73426881
9D2F
Number of Times RAB Is

R99 UEs During State
Transitions from
CELL_DCH to
CELL_FACH
Description
This counter measures the number of times the RABs of R99 UEs are abnormally released when
R99 UEs are transitioning from the CELL_DCH state to the CELL_FACH state. This counter
is measured in the best cell.This counter complies with section "8 RANAP Procedures" in 3GPP
TS 25.413(v10.10.0).
Measurement point
reset occurs in the RB reconfiguration procedure (for the state transition of a PS R99 UE from
CELL_DCH to CELL_FACH), so the RNC sends a RAB RELEASE REQUEST message to
the CN. If the service to be released for the R99 UE is a PS service and the CN responds with a
RAB ASSIGNMENT REQUEST message that carries a cause value other than "User Inactivity",
"Normal Release", "UE Generated Signalling Connection Release", "Successful Relocation", or
"Network Optimization", this counter is measured in the best cell of the R99 UE. For details
about the cause values indicating an abnormal release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

2865
BSC6900 UMTS
CELL_DCH to CELL_FACH), so the RNC sends a RAB RELEASE REQUEST message to
the CN. If the service to be released for the R99 UE is a PS service and the CN responds with
an IU RELEASE COMMAND message that carries a cause value other than "User Inactivity",
"Network Optimization", this counter is measured in the best cell of the UE. For details about
the cause values indicating an abnormal release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

2866
BSC6900 UMTS
CELL_DCH to CELL_FACH), so the RNC sends an IU RELEASE REQUEST message to the
CN. If the service to be released for the R99 UE is a PS service and the CN responds with an IU
RELEASE COMMAND message that carries a cause value other than "User Inactivity",
"Network Optimization", this counter is measured in the best cell of the R99 UE. For details
about the cause values indicating an abnormal release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

2867
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
9D2F
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010503
WRFD-010504

Issue 03 (2015-06-30)

2868
BSC6900 UMTS
Number of Times PS Services Are Abnormally Released for PS R99 UEs in

CELL_DCH State Due to Cell Update Failures
Counters
Counter ID
Counter Name
Counter Description
73426882
9.CellDCH.CellUpdt
Number of Times PS
Services Are Abnormally
Released for PS R99 UEs in
CELL_DCH State Due to
Cell Update Failures
Description
This counter provides the number of times the PS services of R99 UEs in CELL_DCH state are
abnormally released due to cell update failures. This counter is measured in the best cell.This
Measurement point
UPDATE message from an R99 UE in CELL_DCH state but the cell update procedure fails, so
the RNC sends a RAB RELEASE REQUEST message to the CN. The CN responds with a RAB
ASSIGNMENT REQUEST message. If the service to be released for the R99 UE is a PS service
and the CN responds with a RAB ASSIGNMENT REQUEST message that carries a cause value
other than "User Inactivity", "Normal Release", "UE Generated Signalling Connection Release",
"Successful Relocation", or "Network Optimization", this counter is measured in the best cell
of the R99 UE. For details about the cause values indicating an abnormal release, see 3GPP TS
25.413.
CONFIRM message:
example.
Issue 03 (2015-06-30)

2869
BSC6900 UMTS
the RNC sends a RAB RELEASE REQUEST message to the CN. If the service to be released
for the R99 UE is a PS service and the CN responds with an IU RELEASE COMMAND message
counter is measured in the best cell of the R99 UE. For details about the cause values indicating
example.
Issue 03 (2015-06-30)

2870
BSC6900 UMTS
the RNC sends an IU RELEASE REQUEST message to the CN. If the service to be released
for the R99 UE is a PS service and the CN responds with an IU RELEASE COMMAND message
counter is measured in the best cell of the R99 UE. For details about the cause values indicating
example.
Issue 03 (2015-06-30)

2871
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
9.CellDCH.CellUpdt
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010503
WRFD-010504

Issue 03 (2015-06-30)

2872
BSC6900 UMTS
Number of Times CN Initiates CS RAB Releases After RL Reestablishment and

Before Timer Expires
Counters
Counter ID
Counter Name
Counter Description
73428903
VS.RAB.Rel.CS.CNInit.AfterReEst
Number of Times CN
Initiates CS RAB Releases
After RL Reestablishment
and Before Timer Expires
Description
This counter provides the number of times the CN initiates CS RAB releases after radio link
(RL) reestablishment within the period of time specified by Message Statistics Timer After RL
Reestablishment. This timer is set in the SET USTATETIMER command. This counter is
measured in the best cell. When Message Statistics Timer After RL Reestablishment is set to 0,
this counter is not measured.This counter complies with section "8.2 Radio Bearer control
Measurement point
The measurement is triggered at point B in Figure 1. After the RL is reestablished for a UE
processing CS services, Message Statistics Timer After RL Reestablishment is started. If the
RNC receives an Iu Release Command message from the CN before the timer expires and the
RNC has not sent an Iu Release Request or RAB Release Request message to the CN, and the
RAB to be released belongs to CS domain, this counter is measured in the best cell for the UE.
Issue 03 (2015-06-30)

2873
BSC6900 UMTS
Figure 1-1267 Procedure of the CN initiating an Iu release command after RL reestablishment
The measurement is triggered at point B in Figure 2. After the RL is reestablished for a UE

processing CS services, Message Statistics Timer After RL Reestablishment is started. If the
RNC receives a RAB Assignment Request message from the CN before the timer expires and
the RNC has not sent a RAB Release Request message to the CN, and the RAB to be released
belongs to CS domain, this counter is measured in the best cell for the UE. On receiving a CELL
UPDATE CONFIRM message, the UE returns one of the following messages based on the IE
carried in the CELL UPDATE CONFIRM message:
The preceding figures use the PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message as an example.
Issue 03 (2015-06-30)

2874
BSC6900 UMTS
Figure 1-1268 Procedure of the CN initiating a RAB assignment request after RL

reestablishment
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.CS.CNInit.AfterReEst
WRFD-140103

2875
BSC6900 UMTS
Number of Times CN Initiates CS RAB Releases During RL Reestablishment

Counters
Counter ID
Counter Name
Counter Description
73428904
VS.RAB.Rel.CS.CNInit.Dur
ingReEst
Number of Times CN
Initiates CS RAB Releases
During RL Reestablishment
Description
This counter provides the number of times the CN initiates CS RAB releases during RL
reestablishment in the best cell.This counter complies with section "8.2 Radio Bearer control
Measurement point
The measurement is triggered at point A in figure 1. When a UE processing CS services
experiences an SRB reset, UL RL out-of-synchronization, or Air-interface process timeout, the
RNC sends a RADIO LINK ACTIVATION COMMAND message to the UE to reestablish the
UE's RL. If the RNC receives an Iu Release Command message from the CN prior to the
reconfiguration complete message from the UE and the RNC has not sent an Iu Release Request
or RAB Release Request message to the CN, and the released RAB belongs to CS domain, this
counter is measured in the best cell for the UE.
Figure 1-1269 Procedure of CN initiates Iu release command during RL reestablishment
Issue 03 (2015-06-30)

2876
BSC6900 UMTS
The measurement is triggered at point A in figure 2. If a UE processing CS services experiences

SRB reset, UL RL out-of-synchronization, or Air-interface timeout, the RNC sends a Radio Link
Activation Command message to the UE to reestablish the UE's RL. If the RNC receives a RAB
Assignment Request message from the CN prior to the reconfiguration complete message from
the UE and the RNC has not sent a RAB RELEASE REQUEST message to the CN, and the
released RAB belongs to CS domain, this counter is measured in the best cell for the UE. On
receiving a CELL UPDATE CONFIRM message, the UE returns one of the following messages
based on the IE carried in the CELL UPDATE CONFIRM message:
The preceding figures use the PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message as an example.
Figure 1-1270 Procedure of CN initiates RAB assignment request during RL reestablishment
Formula
None
Issue 03 (2015-06-30)

2877
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.CS.CNInit.Dur
ingReEst
WRFD-140103
Number of PS RABs Abnormally Released for UEs in the RRC Connected mode
Due to Inter-RAT Reselections for Cell
Counters
Counter ID
Counter Name
Counter Description
73430189
VS.RAB.AbnormRel.PS.IR
ATResel.DCHFACH
Number of PS RABs
UEs in the CELL_DCH and
CELL_FACH States Due to
Inter-RAT Reselections for
Cell
73430190
ATResel.PCH
Number of PS RABs
URA_PCH States Due to
Inter-RAT Reselections for
Cell
Description
These counters provide the number of PS RABs that are abnormally released for UEs in different
RRC connected modes during inter-RAT reselections in the best cell. This counter complies
with 3GPP TS 25.413 (V12.1.0). For details, see chapter 8 "RANAP Procedures" in this TS.
Note: The "RAT Type" is an optional IE in the SRNS Context Request message received from
the CN. If the "RAT Type" IE indicates another RAT, the number of inter-RAT cell reselections
is increased by one. If this IE is not included in the message, the RNC cannot determine whether
the cell reselection is inter-RAT or intra-RAT and increase each of them by one.
Issue 03 (2015-06-30)

2878
BSC6900 UMTS
Counter Name
Description
VS.RAB.AbnormRel.PS.IRATResel.DCHF
ACH
This counter provides the number of PS

RABs that are abnormally released for UEs
in the CELL_DCH and CELL_FACH states
during inter-RAT reselections in the best cell.
This counter excludes the PS RABs that are
abnormally released during inter-RAT
reselections in CELL_DCH-to-CELL_PCH/
URA_PCH and CELL_FACH-toCELL_PCH/URA_PCH scenarios.
VS.RAB.AbnormRel.PS.IRATResel.PCH
This counter provides the number of PS

RABs that are abnormally released for UEs
in the CELL_PCH and URA_PCH states
during inter-RAT reselections in the best cell.
This counter includes the PS RABs that are
abnormally released during inter-RAT
reselections in CELL_DCH-to-CELL_PCH/
URA_PCH and CELL_FACH-toCELL_PCH/URA_PCH scenarios.
Measurement point
The measurement is triggered at point A in the following figure. After a UE reselects an interRAT cell, the CN sends an SRNS Context Request message to the RNC but receives no response
from the RNC. The RNC subsequently sends a RAB RELEASE REQUEST message to the CN
due to an exception. If the CN responds with a RAB ASSIGNMENT REQUEST message with
a cause value other than "User Inactivity", "Normal Release", "UE Generated Signalling
Connection Release", "Successful Relocation", or "Network Optimization" and the RAB to be
released carries PS services, either of the preceding counters are measured in the best cell based
on the RRC connected mode of the UE before the inter-RAT reselection. For details about cause
values indicating an abnormal RAB release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

2879
BSC6900 UMTS
Figure 1-1271 RAB release for UEs in the RRC connected mode during inter-RAT reselections
from the RNC. The RNC subsequently sends a RAB RELEASE REQUEST message to the CN.
If the CN responds with an IU RELEASE COMMAND message with a cause value other than
"User Inactivity", "Normal Release", "UE Generated Signalling Connection Release",
"Successful Relocation", or "Network Optimization" and the RAB to be released carries PS
services, either of the preceding counters is measured in the best cell based on the RRC connected
mode of the UE before the inter-RAT reselection. For details about cause values indicating an
Issue 03 (2015-06-30)

2880
BSC6900 UMTS
Figure 1-1272 Iu release procedure triggered by RAB release for UEs in the RRC connected
mode during inter-RAT reselections
from the RNC. The RNC subsequently sends an IU RELEASE REQUEST message to the CN.
If the CN responds with an IU RELEASE COMMAND message with a cause value other than
"User Inactivity", "Normal Release", "UE Generated Signalling Connection Release",
"Successful Relocation", or "Network Optimization" and the RAB to be released carries PS
services, either of the preceding counters is measured in the best cell based on the RRC connected
mode of the UE before the inter-RAT reselection. For details about cause values indicating an
Issue 03 (2015-06-30)

2881
BSC6900 UMTS
Figure 1-1273 Iu release procedure initiated by the RNC for UEs in the RRC connected mode
during inter-RAT reselections
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ATResel.DCHFACH
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010503
WRFD-010504

ATResel.PCH
WRFD-010510
WRFD-010503
WRFD-010504
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

2882
BSC6900 UMTS
Number of CS RABs Abnormally Released by the RNC After the RNC Receives
the DISCONNECT Message for Cell
Counters
Counter ID
Counter Name
Counter Description
73430220
VS.RAB.AbnormRel.CS.Di
sconnect
Number of CS RABs
RNC After the RNC
Receives the DISCONNECT
Message for Cell
Description
This counter provides the number of CS RABs abnormally released after the RNC receives a
DISCONNECT direct transfer message in the best cell. This counter complies with 3GPP TS
25.413 (V11.1.0). For details about this counter, see sections 8.3 "RAB Release Request" and
8.4 "Iu Release Request" in this TS.
Measurement point
The measurement is triggered at point A in figure 1. After receiving a DISCONNECT direct
transfer message from the UE or MSC, the RNC sends a RAB RELEASE REQUEST message
to the CN. When the RNC receives from the CN a RAB ASSIGNMENT REQUEST message
with a cause value indicating abnormal release, this counter is measured in the best cell. The
cause values other than "User Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization", and "UE Generated Signalling Connection Release" indicate abnormal releases.
Issue 03 (2015-06-30)

2883
BSC6900 UMTS
Figure 1-1274 RNC abnormally releasing a UE's RAB after receiving a DISCONNECT
message

transfer message from the UE or MSC, the RNC sends a RAB RELEASE REQUEST message
to the CN. When the RNC receives from the CN an IU RELEASE COMMAND message with
a cause value indicating abnormal release, this counter is measured in the best cell. The cause
values other than "User Inactivity", "Normal Release", "Successful Relocation", "Network
Issue 03 (2015-06-30)

2884
BSC6900 UMTS
message

transfer message from the UE or MSC, the RNC sends an IU RELEASE REQUEST message
to the CN. When the RNC receives from the CN an IU RELEASE COMMAND message with
a cause value indicating abnormal release, this counter is measured in the best cell. The cause
values other than "User Inactivity", "Normal Release", "Successful Relocation", "Network
Issue 03 (2015-06-30)

2885
BSC6900 UMTS
message
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.CS.Di
sconnect
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2886
BSC6900 UMTS
Number of Abnormally Released CS RABs Carrying Streaming Services for Cell

(Platinum User Preemption)
Counters
Counter ID
Counter Name
Counter Description
73430480
.PTPreempt
Released CS RABs Carrying
Description
This counter provides the number of PS RABs that are abnormally released due to resource
preemption by platinum users. This counter is measured in the best cell based on the released
CS service type.
Measurement point
The measurement is triggered at point A figure 1. When the services of a platinum user preempt
the resources allocated to a CS user, the RNC sends the CN a RAB RELEASE REQUEST
message. If the RNC subsequently receives from the CN a RAB ASSIGNMENT REQUEST
message with a cause value indicating an abnormal release, this counter is measured in the best
cell based on the released CS service type. Except for the cause values "User Inactivity", "Normal
Release", "Successful Relocation", "Network Optimization", and "UE Generated Signalling
Connection Release", all other cause values indicate an abnormal release. For details about the
cause values indicating an abnormal release, see 3GPP TS 25.413.
Issue 03 (2015-06-30)

2887
BSC6900 UMTS
message. If the RNC subsequently receives from the CN an IU RELEASE COMMAND message
with a cause value indicating an abnormal release, this counter is measured in the best cell based
on the released PS service type. Except for the cause values "User Inactivity", "Normal Release",
"Successful Relocation", "Network Optimization", and "UE Generated Signalling Connection
Release", all other cause values indicate an abnormal release. For details about the cause values
indicating an abnormal release, see 3GPP TS
the resources allocated to a CS user, the RNC sends the CN an IU RELEASE REQUEST
on the released CS service type. Except for the cause values "User Inactivity", "Normal Release",
Issue 03 (2015-06-30)

2888
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.PTPreempt
WRFD-150204

2889
BSC6900 UMTS
Number of Abnormally Released CS RABs Carrying Conversational Services for

Cell (Platinum User Preemption)
Counters
Counter ID
Counter Name
Counter Description
73430481
VS.RAB.AbnormRel.CS.Co
nv.PTPreempt
Released CS RABs Carrying
Cell (Platinum User
Preemption)
Description
CS service type.
Measurement point
cell based on the released CS service type. Except for the cause values "User Inactivity", "Normal
Issue 03 (2015-06-30)

2890
BSC6900 UMTS
the resources allocated to a CS user, the RNC sends the CN an IU RELEASE REQUEST
on the released CS service type. Except for the cause values "User Inactivity", "Normal Release",
Issue 03 (2015-06-30)

2891
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.CS.Co
nv.PTPreempt
WRFD-150204

2892
BSC6900 UMTS
Number of Abnormally Released PS RABs Carrying Background Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73430482
VS.RAB.AbnormRel.PS.Bk
g.PTPreempt
Released PS RABs Carrying
Description
PS service type.
Measurement point
the resources allocated to a PS user, the RNC sends the CN a RAB RELEASE REQUEST
cell based on the released PS service type. Except for the cause values "User Inactivity", "Normal
Issue 03 (2015-06-30)

2893
BSC6900 UMTS
the resources allocated to a PS user, the RNC sends the CN an IU RELEASE REQUEST
Issue 03 (2015-06-30)

2894
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.PS.Bk
g.PTPreempt
WRFD-150204

2895
BSC6900 UMTS
Number of Abnormally Released PS RABs Carrying Interactive Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73430483
VS.RAB.AbnormRel.PS.Int.
PTPreempt
Description
PS service type.
Measurement point
Issue 03 (2015-06-30)

2896
BSC6900 UMTS
Issue 03 (2015-06-30)

2897
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RAB.AbnormRel.PS.Int.
PTPreempt
WRFD-150204

2898
BSC6900 UMTS
Number of Abnormally Released PS RABs Carrying Streaming Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73430484
.PTPreempt
Description
PS service type.
Measurement point
Issue 03 (2015-06-30)

2899
BSC6900 UMTS
Issue 03 (2015-06-30)

2900
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.PTPreempt
WRFD-150204
Number of Abnormally Released PS RABs for Cell (Platinum User Preemption)

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430485
nv.PTPreempt
Released PS RABs for Cell

2901
BSC6900 UMTS
Description
PS service type.
Measurement point
Issue 03 (2015-06-30)

2902
BSC6900 UMTS
Issue 03 (2015-06-30)

2903
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
nv.PTPreempt
WRFD-150204

2904
BSC6900 UMTS
Number of RRC Connection Releases Caused by No Response to Three

Consecutive F2D Requests for Cell
Counters
Counter ID
Counter Name
Counter Description
73430559
VS.RAB.Rel.PS.F2DNoRsp

Releases Caused by No
Response to Three
Consecutive F2D Requests
for Cell
Description
This counter provides the number of times RRC connections are released due to no response to
three consecutive F2D state transition requests initiated by the RNC in the best cell. F2D state
transitions refer to the transitions from the CELL_FACH state to the CELL_DCH state. The
cause value contained in the RRC Connection Release message is "User Inactive." This counter
complies with 3GPP TS 25.413 (V10.10.0). For details about this counter, see chapter 8
"RANAP Procedures" in this TS.
Measurement point
The measurement is triggered at point A in the following figure. The RNC sends three
consecutive RADIO BEARER RECONFIGURATION messages to the UE to trigger a F2D
state transition, but the UE responds to none of them. The RNC then releases the UE's PS
services. This counter is measured in the best cell for the UE.
Issue 03 (2015-06-30)

2905
BSC6900 UMTS
Figure 1-1295 Iu connection release procedure in case of no response to three consecutive F2D
state transition requests
The measurement is triggered at point A in the following figure. The RNC sends three
consecutive RADIO BEARER RECONFIGURATION messages to the UE to trigger a F2D
state transition, but the UE responds to none of them. The RNC then releases the UE's PS
services. This counter is measured in the best cell for the UE.
Issue 03 (2015-06-30)

2906
BSC6900 UMTS
Figure 1-1296 RAB release procedure in case of no response to three consecutive F2D state
transition requests
Formula
None
Unit
None
Issue 03 (2015-06-30)

2907
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RAB.Rel.PS.F2DNoRsp
WRFD-021101
Dynamic Channel
(DCCC)
1.12.38 RB Procedure Measurement <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. During the RB setup or reconfiguration: The RNC considers that the
RB setup or reconfiguration is successful if the RNC receives a RADIO BEARER SETUP
COMPLETE or RADIO BEARER RECONFIGURATION COMPLETE message from the UE.
If the RNC triggers a radio link re-establishment and receives an ACK message from the UE
indicating that the RB setup or reconfiguration is successful before receiving the RADIO
BEARER SETUP COMPLETE or RADIO BEARER RECONFIGURATION COMPLETE
message from the UE, the RNC considers that the new configurations on the UE takes effect,
and the RB setup or reconfiguration is successful. The consequent procedures are performed
based on the new configurations on the UE.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180113
VS.AttRBSetup
Number of RB Setup
Attempts for Cell
Earlier than
BSC6900
V900R011
67180114
VS.SuccRBSetup
Number of
Successful RB
Setups for Cell
Earlier than
BSC6900
V900R011
67180115
VS.FailRBSetup.Cf
gUnsup
Number of Failed RB
Setups for Cell
(configuration
unsupported)
Earlier than
BSC6900
V900R011
67180116
VS.FailRBSetup.P
hyChFail
Number of Failed RB
Setups for Cell
(physical channel
failure)
Earlier than
BSC6900
V900R011

2908
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180119
VS.FailRBSetup.C
ellUpd
Number of Failed RB
Setups for Cell (cell
update occurred)
Earlier than
BSC6900
V900R011
67180120
VS.FailRBSetup.In
cCfg
Number of Failed RB
Setups for Cell
(invalid
configuration)
Earlier than
BSC6900
V900R011
67180121
VS.FailRBSetup.N
oReply
Number of Failed RB
Setups for Cell (no
reply)
Earlier than
BSC6900
V900R011
67180122
VS.AttRBRecfg
Number of RB
Reconfiguration
Attempts for Cell
Earlier than
BSC6900
V900R011
67180123
VS.SuccRBRecfg
Number of
Successful RB
Reconfigurations for
Cell
Earlier than
BSC6900
V900R011
67180124
VS.FailRBRecfg.Cf
gUnsup
Number of Failed RB
Cell (configuration
unsupported)
Earlier than
BSC6900
V900R011
67180125
VS.FailRBRecfg.P
hyChFail
Number of Failed RB
Cell (physical
channel failure)
Earlier than
BSC6900
V900R011
67180128
VS.FailRBRecfg.C
ellUpd
Number of Failed RB
Cell (cell update
occurred)
Earlier than
BSC6900
V900R011
67180129
VS.FailRBRecfg.In
cCfg
Number of Failed RB
Cell (invalid
configuration)
Earlier than
BSC6900
V900R011
67180130
VS.FailRBRecfg.N
oReply
Number of Failed RB
Cell (no reply)
Earlier than
BSC6900
V900R011
67199619
VS.RB.AMR.DL.
10.2
Number of AMR
Users with DL rate of
10.2 Kbit/s for Cell
Earlier than
BSC6900
V900R011

2909
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199620
VS.RB.AMR.DL.
12.2
Number of AMR
Earlier than
BSC6900
V900R011
67199621
VS.RB.AMR.DL.
7.95
Number of AMR
Earlier than
BSC6900
V900R011
67199622
VS.RB.AMR.DL.
7.4
Number of AMR
7.4 Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199780
VS.RB.AMR.DL.
6.7
Number of AMR
6.7 Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199623
VS.RB.AMR.DL.
5.9
Number of AMR
5.9 Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199624
VS.RB.AMR.DL.
5.15
Number of AMR
Earlier than
BSC6900
V900R011
67199625
VS.RB.AMR.DL.
4.75
Number of AMR
Earlier than
BSC6900
V900R011
67199626
VS.RB.AMR.UL.
10.2
Number of AMR
Users with UL rate of
Earlier than
BSC6900
V900R011
67199627
VS.RB.AMR.UL.
12.2
Number of AMR
Earlier than
BSC6900
V900R011
67199628
VS.RB.AMR.UL.
7.95
Number of AMR
Earlier than
BSC6900
V900R011
67199629
VS.RB.AMR.UL.
7.4
Number of AMR
7.4 Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199781
VS.RB.AMR.UL.
6.7
Number of AMR
6.7 Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199630
VS.RB.AMR.UL.
5.9
Number of AMR
5.9 Kbit/s for Cell
Earlier than
BSC6900
V900R011

2910
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199631
VS.RB.AMR.UL.
5.15
Number of AMR
Earlier than
BSC6900
V900R011
67199632
VS.RB.AMR.UL.
4.75
Number of AMR
Earlier than
BSC6900
V900R011
67203430
VS.RB.PS.Conv.D
L.64
Average Number of
RBs for PS R99
Conversational
Services with DL
Cell
BSC6900
V900R012
67203434
VS.RB.PS.Conv.U
L.64
Average Number of
RBs for PS R99
Conversational
Services with UL
Cell
BSC6900
V900R012
67199594
VS.RB.PS.Bkg.DL.
128
Average Number of
RBs for PS R99
Background
Services with DL
Cell
Earlier than
BSC6900
V900R011
67199595
VS.RB.PS.Bkg.DL.
144
Average Number of
RBs for PS R99
Background
Services with DL
Cell
Earlier than
BSC6900
V900R011
67199591
VS.RB.PS.Bkg.DL.
16
Average Number of
RBs for PS R99
Background
Services with DL
Cell
Earlier than
BSC6900
V900R011
67199596
VS.RB.PS.Bkg.DL.
256
Average Number of
RBs for PS R99
Background
Services with DL
Cell
Earlier than
BSC6900
V900R011

2911
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199592
VS.RB.PS.Bkg.DL.
32
Average Number of
RBs for PS R99
Background
Services with DL
Cell
Earlier than
BSC6900
V900R011
67199597
VS.RB.PS.Bkg.DL.
384
Average Number of
RBs for PS R99
Background
Services with DL
Cell
Earlier than
BSC6900
V900R011
67199593
VS.RB.PS.Bkg.DL.
64
Average Number of
RBs for PS R99
Background
Services with DL
Cell
Earlier than
BSC6900
V900R011
67199590
VS.RB.PS.Bkg.DL.
8
Average Number of
RBs for PS R99
Background
Services with DL
Cell
Earlier than
BSC6900
V900R011
67199556
VS.RB.CS.Conv.D
L.64
Average Number of
RBs for CS
Conversational
Services with DL
Cell
Earlier than
BSC6900
V900R011
67203438
VS.RB.CS.Conv.U
L.64
Average Number of
RBs for CS
Conversational
Services with UL
Cell
Earlier than
BSC6900
V900R011
67199578
VS.RB.PS.Int.DL.
128
Average Number of
RBs for PS R99
with DL Rate of 128
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2912
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199579
VS.RB.PS.Int.DL.
144
Average Number of
RBs for PS R99
with DL Rate of 144
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199575
VS.RB.PS.Int.DL.
16
Average Number of
RBs for PS R99
with DL Rate of 16
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199580
VS.RB.PS.Int.DL.
256
Average Number of
RBs for PS R99
with DL Rate of 256
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199576
VS.RB.PS.Int.DL.
32
Average Number of
RBs for PS R99
with DL Rate of 32
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199581
VS.RB.PS.Int.DL.
384
Average Number of
RBs for PS R99
with DL Rate of 384
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199577
VS.RB.PS.Int.DL.
64
Average Number of
RBs for PS R99
with DL Rate of 64
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199574
VS.RB.PS.Int.DL.8
Average Number of
RBs for PS R99
with DL Rate of 8
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199560
VS.RB.CS.Str.DL.
57.6
Average Number of
RBs for CS
Streaming Services
with DL Rate of 57.6
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2913
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199569
VS.RB.PS.Str.DL.
128
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 128
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199570
VS.RB.PS.Str.DL.
144
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 144
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199567
VS.RB.PS.Str.DL.
32
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 32
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199568
VS.RB.PS.Str.DL.
64
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 64
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67203439
VS.RB.PS.Str.DL.8
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 8
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67203440
VS.RB.PS.Str.DL.
16
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 16
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199602
VS.RB.PS.Bkg.UL.
128
Average Number of
RBs for PS R99
Background
Services with UL
Cell
Earlier than
BSC6900
V900R011
67199603
VS.RB.PS.Bkg.UL.
144
Average Number of
RBs for PS R99
Background
Services with UL
Cell
Earlier than
BSC6900
V900R011

2914
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199599
VS.RB.PS.Bkg.UL.
16
Average Number of
RBs for PS R99
Background
Services with UL
Cell
Earlier than
BSC6900
V900R011
67199604
VS.RB.PS.Bkg.UL.
256
Average Number of
RBs for PS R99
Background
Services with UL
Cell
Earlier than
BSC6900
V900R011
67199600
VS.RB.PS.Bkg.UL.
32
Average Number of
RBs for PS R99
Background
Services with UL
Cell
Earlier than
BSC6900
V900R011
67199605
VS.RB.PS.Bkg.UL.
384
Average Number of
RBs for PS R99
Background
Services with UL
Cell
Earlier than
BSC6900
V900R011
67199601
VS.RB.PS.Bkg.UL.
64
Average Number of
RBs for PS R99
Background
Services with UL
Cell
Earlier than
BSC6900
V900R011
67199598
VS.RB.PS.Bkg.UL.
8
Average Number of
RBs for PS R99
Background
Services with UL
Cell
Earlier than
BSC6900
V900R011
67199586
VS.RB.PS.Int.UL.
128
Average Number of
RBs for PS R99
with UL Rate of 128
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2915
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199587
VS.RB.PS.Int.UL.
144
Average Number of
RBs for PS R99
with UL Rate of 144
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199583
VS.RB.PS.Int.UL.
16
Average Number of
RBs for PS R99
with UL Rate of 16
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199588
VS.RB.PS.Int.UL.
256
Average Number of
RBs for PS R99
with UL Rate of 256
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199584
VS.RB.PS.Int.UL.
32
Average Number of
RBs for PS R99
with UL Rate of 32
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199589
VS.RB.PS.Int.UL.
384
Average Number of
RBs for PS R99
with UL Rate of 384
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199585
VS.RB.PS.Int.UL.
64
Average Number of
RBs for PS R99
with UL Rate of 64
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199582
VS.RB.PS.Int.UL.8
Average Number of
RBs for PS R99
with UL Rate of 8
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67203442
VS.RB.CS.Str.UL.
57.6
Average Number of
RBs for CS
Streaming Services
with UL Rate of 57.6
Kbit/s for Cell
Earlier than
BSC6900
V900R011

2916
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199571
VS.RB.PS.Str.UL.
16
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 16
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199572
VS.RB.PS.Str.UL.
32
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 32
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67199573
VS.RB.PS.Str.UL.
64
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 64
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67203445
VS.RB.PS.Str.UL.8
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 8
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67203446
VS.RB.PS.Str.UL.
128
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 128
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67203447
VS.RB.PS.Str.UL.
144
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 144
Kbit/s for Cell
Earlier than
BSC6900
V900R011
67192389
VS.DRD.RBSetup.
AttOut
Number of RB Setup
Attempts for
Outgoing InterFrequency Directed
Retry for Cell
Earlier than
BSC6900
V900R011
67192390
VS.DRD.RBSetup.
SuccOut
Number of
Successful RB Setup
for Outgoing InterFrequency Directed
Retry for Cell
Earlier than
BSC6900
V900R011

2917
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192391
VS.DRD.RBSetup.
AttIn
Number of RB Setup
Attempts for
Incoming InterFrequency Directed
Retry for Cell
Earlier than
BSC6900
V900R011
67192392
VS.DRD.RBSetup.
SuccIn
Number of
Successful RB Setup
for Incoming InterFrequency Directed
Retry for Cell
Earlier than
BSC6900
V900R011
67192393
VS.DRD.RBRecfg.
AttOut
Number of RB
Reconfiguration
Attempts for
Retry for Cell
Earlier than
BSC6900
V900R011
67192394
VS.DRD.RBRecfg.
SuccOut
Number of
Successful RB
Reconfiguration for
Retry for Cell
Earlier than
BSC6900
V900R011
67192395
VS.DRD.RBRecfg.
AttIn
Number of RB
Reconfiguration
Attempts for
Retry for Cell
Earlier than
BSC6900
V900R011
67192396
VS.DRD.RBRecfg.
SuccIn
Number of
Successful RB
Reconfiguration for
Retry for Cell
Earlier than
BSC6900
V900R011
67192440
VS.DRD.RB.D2H.
AttOut
Number of Outgoing
DCH-to-HSDPA
Directed Retry
Attempts for Cell
Earlier than
BSC6900
V900R011
67192441
VS.DRD.RB.D2H.S
uccOut
Number of
Successful Outgoing
DCH-to-HSDPA
Directed Retry for
Cell
Earlier than
BSC6900
V900R011

2918
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192442
VS.DRD.RB.D2H.
AttIn
Number of Incoming
DCH-to-HSDPA
Directed Retry
Attempts for Cell
Earlier than
BSC6900
V900R011
67192443
VS.DRD.RB.D2H.S
uccIn
Number of
Successful Incoming
DCH-to-HSDPA
Directed Retry for
Cell
Earlier than
BSC6900
V900R011
67195503
VS.DRD.RB.D2E.
AttOut
Number of Outgoing
DCH-to-HSUPA
Directed Retry
Attempts for Cell
Earlier than
BSC6900
V900R011
67195504
VS.DRD.RB.D2E.S
uccOut
Number of
Successful DCH-toHSUPA Directed
Retry for Cell
Earlier than
BSC6900
V900R011
67195505
VS.DRD.RB.D2E.
AttIn
Number of Incoming
DCH-to-HSUPA
Directed Retry
Attempts for Cell
Earlier than
BSC6900
V900R011
67195506
VS.DRD.RB.D2E.S
uccIn
Number of
Successful Incoming
DCH-to-HSUPA
Directed Retry for
Cell
Earlier than
BSC6900
V900R011
67203803
VS.RB.AMRWB.D
L.23.85
Number of UEs that

use the CS AMR WB
speech service at the
DL bit rate of 23.85
kbit/s in the cell
BSC6900
V900R012
67203804
VS.RB.AMRWB.D
L.23.05
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203805
VS.RB.AMRWB.D
L.19.85
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012

2919
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203806
VS.RB.AMRWB.D
L.18.25
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203807
VS.RB.AMRWB.D
L.15.85
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203808
VS.RB.AMRWB.D
L.14.25
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203809
VS.RB.AMRWB.D
L.12.65
Number of UEs that

use the CS AMR WB
kbit/s in the cell
Earlier than
BSC6900
V900R011
67203810
VS.RB.AMRWB.D
L.8.85
Number of UEs that

use the CS AMR WB
DL bit rate of 8.85
kbit/s in the cell
Earlier than
BSC6900
V900R011
67203811
VS.RB.AMRWB.D
L.6.60
Number of UEs that

use the CS AMR WB
DL bit rate of 6.60
kbit/s in the cell
BSC6900
V900R012
67203812
VS.RB.AMRWB.U
L.23.85
Number of UEs that

use the CS AMR WB
UL bit rate of 23.85
kbit/s in the cell
BSC6900
V900R012
67203813
VS.RB.AMRWB.U
L.23.05
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012

2920
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203814
VS.RB.AMRWB.U
L.19.85
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203815
VS.RB.AMRWB.U
L.18.25
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203816
VS.RB.AMRWB.U
L.15.85
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203817
VS.RB.AMRWB.U
L.14.25
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203818
VS.RB.AMRWB.U
L.12.65
Number of UEs that

use the CS AMR WB
kbit/s in the cell
BSC6900
V900R012
67203819
VS.RB.AMRWB.U
L.8.85
Number of UEs that

use the CS AMR WB
UL bit rate of 8.85
kbit/s in the cell
Earlier than
BSC6900
V900R011
67203820
VS.RB.AMRWB.U
L.6.60
Number of UEs that

use the CS AMR WB
UL bit rate of 6.60
kbit/s in the cell
BSC6900
V900R012
67203441
VS.RB.PS.Str.DL.
256.384
Average Number of
RBs for PS R99
Streaming Services
with DL Rate of 256
for Cell
Earlier than
BSC6900
V900R011

2921
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203448
VS.RB.PS.Str.UL.
256.384
Average Number of
RBs for PS R99
Streaming Services
with UL Rate of 256
for Cell
Earlier than
BSC6900
V900R011
67204790
VS.RB.PS.Conv.D
L.38.8
Average Number of
RBs for PS R99
Conversational
Services with DL
Rate of 38.8 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67204794
VS.RB.PS.Conv.U
L.38.8
Average Number of
RBs for PS R99
Conversational
Services with UL
Rate of 38.8 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67204791
VS.RB.PS.Conv.D
L.39.2
Average Number of
RBs for PS R99
Conversational
Services with DL
Rate of 39.2 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67204795
VS.RB.PS.Conv.U
L.39.2
Average Number of
RBs for PS R99
Conversational
Services with UL
Rate of 39.2 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67204792
VS.RB.PS.Conv.D
L.40
Average Number of
RBs for PS R99
Conversational
Services with DL
Cell
Earlier than
BSC6900
V900R011
67204796
VS.RB.PS.Conv.U
L.40
Average Number of
RBs for PS R99
Conversational
Services with UL
Cell
Earlier than
BSC6900
V900R011

2922
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204793
VS.RB.PS.Conv.D
L.42.8
Average Number of
RBs for PS R99
Conversational
Services with DL
Rate of 42.8 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67204797
VS.RB.PS.Conv.U
L.42.8
Average Number of
RBs for PS R99
Conversational
Services with UL
Rate of 42.8 Kbit/s
for Cell
Earlier than
BSC6900
V900R011
67196294
VS.DRD.IFREQ.C
S.MBDR.RBSetup.
SuccOut
Number of
Successful CS Voice
Directed Retry Based
on Inter-Frequency
Measurement for
Cell
Earlier than
BSC6900
V900R011
67196293
VS.DRD.IFREQ.C
S.MBDR.RBSetup.
AttOut
Number of CS Voice
Directed Retry
Attempts Based on
Inter-Frequency
Measurement for
Cell
Earlier than
BSC6900
V900R011
67196295
VS.DRD.IFREQ.P
S.MBDR.R99.RBS
etup.AttOut
Number of PS R99
Directed Retry
Attempts Based on
Inter-Frequency
Measurement for
Cell
Earlier than
BSC6900
V900R011
67196296
VS.DRD.IFREQ.P
S.MBDR.R99.RBS
etup.SuccOut
Number of
Successful PS R99
Directed Retry Based
on Inter-Frequency
Measurement for
Cell
Earlier than
BSC6900
V900R011
67196297
VS.DRD.IFREQ.P
S.MBDR.HResCon
g.RBSetup.AttOut
Number of HSDPA
PS Directed Retry
Attempts Based on
Inter-Frequency
Measurement for
Cell
Earlier than
BSC6900
V900R011

2923
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196298
VS.DRD.IFREQ.P
S.MBDR.HResCon
g.RBSetup.SuccOut
Number of
Successful HSDPA
PS Directed Retry
Based on InterFrequency
Measurement for
Cell
Earlier than
BSC6900
V900R011
67196303
VS.RB.RateDown.
To.0kbps
Number of Times
that PS Rate
Downgrades to 0
Kbit/s in the Best
Cell
Earlier than
BSC6900
V900R011
73415857
VS.RB.PS.Conv.H
SDSCH
Number of PS
Conversation UEs on
HS-DSCH for Cell
BSC6900
V900R012
73415858
VS.RB.PS.Conv.E
DCH
Number of PS
Conversation UEs on
EDCH for Cell
BSC6900
V900R012
73394053
VS.DRD.PhyRecfg.
AttOut
Number of Outgoing
DRD Attempts
through Physical
Channel
Reconfiguration for
Cell
BSC6900
V900R012
73394054
VS.DRD.PhyRecfg.
SuccOut
Number of
Successful Outgoing
DRDs through
Physical Channel
Reconfiguration for
Cell
BSC6900
V900R012
73394055
VS.DRD.PhyRecfg.
AttIn
Number of Incoming
DRD Attempts
through Physical
Channel
Reconfiguration for
Cell
BSC6900
V900R012
73394056
VS.DRD.PhyRecfg.
SuccIn
Number of
Successful Incoming
DRDs through
Physical Channel
Reconfiguration for
Cell
BSC6900
V900R012

2924
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421487
VS.DRD.RBSetup.
AttEstab.RollBack
Number of RB Setup
Attempts After the
RB Setup DRD
Rollback
BSC6900
V900R012
73421488
VS.DRD.RBSetup.
SuccEstab.RollBack
Number of
successful RB Setups
After the RB Setup
DRD Rollback
BSC6900
V900R012
73421489
VS.DRD.RBRecfg.
AttEstab.RollBack
Number of RB
Reconfiguration
Attempts After the
RB Reconfiguration
DRD Rollback
BSC6900
V900R012
73421490
VS.DRD.RBRecfg.
SuccEstab.RollBack
Number of
Successful RB
Reconfigurations
After the RB
Reconfiguration
DRD Rollback
BSC6900
V900R012
73421491
VS.DRD.PhyRecfg.
AttEstab.RollBack
Number of Physical
Channel
Reconfiguration
Attempts After the
Physical Channel
Reconfiguration
DRD Rollback
BSC6900
V900R012
73421492
VS.DRD.PhyRecfg.
SuccEstab.RollBack
Number of
Successful Physical
Channel
Reconfigurations
After the Physical
Channel
Reconfiguration
DRD Rollback
BSC6900
V900R012
73421842
VS.DRD.RB.F2H.
AttOut
Number of Outgoing
FACH-to-HSDPA
Directed Retry
Attempts for Cell
BSC6900
V900R012
73421843
VS.DRD.RB.F2H.S
uccOut
Number of
Successful Outgoing
FACH-to-HSDPA
Directed Retries for
Cell
BSC6900
V900R012

2925
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421844
VS.DRD.RB.F2E.A
ttOut
Number of Outgoing
FACH-to-HSUPA
Directed Retry
Attempts for Cell
BSC6900
V900R012
73421845
VS.DRD.RB.F2E.S
uccOut
Number of
Successful Outgoing
FACH-to-HSUPA
Cell
BSC6900
V900R012
73421846
VS.DRD.RB.F2H.
AttIn
Number of Incoming
FACH-to-HSDPA
Directed Retry
Attempts for Cell
BSC6900
V900R012
73421847
VS.DRD.RB.F2H.S
uccIn
Number of
Successful Incoming
FACH-to-HSDPA
Cell
BSC6900
V900R012
73421848
VS.DRD.RB.F2E.A
ttIn
Number of Incoming
FACH-to-HSUPA
Directed Retry
Attempts for Cell
BSC6900
V900R012
73421849
VS.DRD.RB.F2E.S
uccIn
Number of
Successful Incoming
FACH-to-HSUPA
Cell
BSC6900
V900R012
73394177
VS.AttPhyRecfg.F2
P
Number of
CELL_FACH to
CELL_PCH
Transition Attempts
by Physical Channel
Reconfiguration for
Cell
BSC6900
V900R014
73394178
VS.SuccPhyRecfg.
F2P
Number of
Successful
CELL_FACH to
CELL_PCH
Transitions by
Physical Channel
Reconfiguration for
Cell
BSC6900
V900R014

2926
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425827
VS.UELocation.M
ultiBand.DRD.AttIn
Number of Incoming
Inter-Frequency
DRD Attempts
Triggered by
Multiband Direct
Retry Based on UE
Location for Cell
BSC6900
V900R015C00
73425835
VS.UELocation.M
ultiBand.DRD.SuccIn
Number of
Successful Incoming
Inter-Frequency
DRDs Triggered by
Multiband Direct
Retry Based on UE
Location for Cell
BSC6900
V900R015C00
73425836
VS.UELocation.M
ultiBand.DRD.AttOut
Number of Outgoing
Inter-Frequency
DRD Attempts
Triggered by
Multiband Direct
Retry Based on UE
Location for Cell
BSC6900
V900R015C00
73425837
VS.UELocation.M
ultiBand.DRD.SuccOut
Number of
Successful Outgoing
Inter-Frequency
DRDs Triggered by
Multiband Direct
Retry Based on UE
Location for Cell
BSC6900
V900R015C00
73426249
VS.MCDRD.Perio
dic.AttOut
Number of Periodic
Inter-Frequency
Outgoing Directed
Retry Attempts
based on
Measurement for
Cell
BSC6900
V900R015C00
73426250
VS.MCDRD.Perio
dic.SuccOut
Number of
Successful Periodic
Inter-Frequency
Outgoing Directed
Retries based on
Measurement for
Cell
BSC6900
V900R015C00

2927
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426251
VS.MCDRD.Perio
dic.AttIn
Number of Periodic
Inter-Frequency
Ingoing Directed
Retry Attempts
based on
Measurement for
Cell
BSC6900
V900R015C00
73426252
VS.MCDRD.Perio
dic.SuccIn
Number of
Successful Periodic
Inter-Frequency
Ingoing Directed
Retries based on
Measurement for
Cell
BSC6900
V900R015C00
73428927
VS.DRD.FailRBSet
up.RollBack
The number of times

the RNC makes a
rollback after the
DRD procedure fails
during RB setup
BSC6900
V900R016C00
73428928
VS.DRD.FailRBRe
cfg.RollBack
The number of times

the RNC makes a
rollback after the
DRD procedure fails
during RB
reconfiguration
BSC6900
V900R016C00
73428929
VS.DRD.FailPhyR
ecfg.RollBack
The number of times

the RNC makes a
rollback after the
DRD procedure fails
during physical
channel
reconfiguration
BSC6900
V900R016C00
73446471
VS.RB.PS.DLDCH
.BestCell
Number of RBs for

PS Services with
Downlink Carried on
the DCH for Cell
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

2928
BSC6900 UMTS
Number of RB Setup Attempts

Counters
Counter ID
Counter Name
Counter Description
67180113
VS.AttRBSetup
Number of RB Setup
Attempts for Cell
Description
This counter provides the number of times that the RNC sends to the UE a RADIO BEARER
SETUP message in the best cell.This counter complies with section "8.2.2 Reconfiguration
Measurement point
BEARER SETUP message to the UE. In this case, this counter is measured in the best cell that
the UE camps on.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2929
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRBSetup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counter ID
Counter Name
Counter Description
67180114
VS.SuccRBSetup
Number of Successful RB
Setups for Cell
Number of Successful RB Setups

Counters
Description
This counter provides the number of times that the RNC receives from the UE a RADIO
BEARER SETUP COMPLETE message in the best cell.This counter complies with section
"8.2.2 Reconfiguration procedures" in 3GPP TS 25.331(v10.13.0).
Measurement point
BEARER SETUP COMPLETE message from the UE. In this case, this counter is measured in
the best cell that the UE camps on.
Issue 03 (2015-06-30)

2930
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccRBSetup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counters Related to the Number of Failed RB Setups for Different Causes

Counters
Counter ID
Counter Name
Counter Description
67180115
VS.FailRBSetup.CfgUnsup
Number of Failed RB Setups

for Cell (configuration
unsupported)
67180116
VS.FailRBSetup.PhyChFail

for Cell (physical channel
failure)
67180119
VS.FailRBSetup.CellUpd

for Cell (cell update
occurred)
67180120
VS.FailRBSetup.IncCfg

for Cell (invalid
configuration)
67180121
VS.FailRBSetup.NoReply

for Cell (no reply)
Description
These counters provide the number of times that the RB setup fails in the best cell due to different
causes.The preceding counters complies with section "8.2.2 Reconfiguration procedures" in
3GPP TS 25.331(v10.13.0).
Issue 03 (2015-06-30)

2931
BSC6900 UMTS
Measurement point
BEARER SETUP FAILURE message from the UE. In this case, the corresponding counter is
measured in the best cell that the UE camps on based on the failure cause.
Figure 1-1299 RB setup procedure (failed operation)
The measurement is triggered at point A as shown in the following figure. When the RNC fails
to receive from the UE a RADIO BEARER SETUP COMPLETE message before the timer
expires, the VS.FailRBSetup.NoReply counter is measured in the best cell that the UE camps
on.
Figure 1-1300 RB setup procedure(no replay)
The measurement is triggered at point A as shown in the figure. The RNC receives a CELL
UPDATE message while waiting for a RADIO BEARER SETUP COMPLETE message, and
as a result the RB setup fails. Under this condition, this counter is increased by one in the best
Issue 03 (2015-06-30)

2932
BSC6900 UMTS
Figure 1-1301 RB setup procedure(cell update)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.FailRBSetup.CfgUnsup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.FailRBSetup.PhyChFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.FailRBSetup.CellUpd
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.FailRBSetup.IncCfg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2933
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.FailRBSetup.NoReply
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RB Reconfiguration Attempts

Counters
Counter ID
Counter Name
Counter Description
67180122
VS.AttRBRecfg
Number of RB
for Cell
Description
This counter provides the number of times that the RNC sends to the UE a RADIO BEARER
RECONFIGURATION message in the best cell.This counter complies with section "8.2.2
Measurement point
BEARER RECONFIGURATION message to the UE. In this case, this counter is measured in
the best cell that the UE camps on.
Issue 03 (2015-06-30)

2934
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttRBRecfg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Successful RB Reconfigurations

Counters
Counter ID
Counter Name
Counter Description
67180123
VS.SuccRBRecfg
Reconfigurations for Cell
Description
This counter provides the number of times that the RNC receives from the UE a RADIO
BEARER RECONFIGURATION COMPLETE message in the best cell.This counter complies
Measurement point
BEARER RECONFIGURATION COMPLETE message from the UE. In this case, this counter
is measured in the best cell that the UE camps on.
Issue 03 (2015-06-30)

2935
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SuccRBRecfg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2936
BSC6900 UMTS
Counters Related to the Number of Failed RB Reconfigurations for Different

Causes
Counters
Counter ID
Counter Name
Counter Description
67180124
VS.FailRBRecfg.CfgUnsup
Number of Failed RB
(configuration unsupported)
67180125
VS.FailRBRecfg.PhyChFail
Number of Failed RB
(physical channel failure)
67180128
VS.FailRBRecfg.CellUpd
Number of Failed RB
(cell update occurred)
67180129
VS.FailRBRecfg.IncCfg
Number of Failed RB
(invalid configuration)
67180130
VS.FailRBRecfg.NoReply
Number of Failed RB
Reconfigurations for Cell (no
reply)
Description
These counters provide the number of times that the RB reconfiguration fails in the best cell due
to different causes.The preceding counters complies with section "8.2.2 Reconfiguration
Measurement point
BEARER RECONFIGURATION FAILURE message from the UE. In this case, the
corresponding counter is measured in the best cell that the UE camps on based on the failure
cause.
Issue 03 (2015-06-30)

2937
BSC6900 UMTS
Figure 1-1304 RB reconfiguration procedure (failed operation)
The measurement is triggered at point A as shown in the following figure. When the RNC fails
to receive from the UE a RADIO BEARER RECONFIGURATION COMPLETE message
before the timer expires, the VS.FailRBRecfg.NoReply counter is measured in the best cell that
the UE camps on.
Figure 1-1305 RB reconfiguration procedure (failed operation)(no reply)
The measurement is triggered at point A as shown in the figure. The RNC receives a CELL
UPDATE message while waiting for a RADIO BEARER RECONFIGURATION COMPLETE
Issue 03 (2015-06-30)

2938
BSC6900 UMTS
message, and as a result the RB setup fails. Under this condition, this counter is increased by
one in the best cell that the UE camps on.
Figure 1-1306 RB reconfiguration procedure(cell update)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.FailRBRecfg.CfgUnsup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.FailRBRecfg.PhyChFail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.FailRBRecfg.CellUpd
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.FailRBRecfg.IncCfg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

2939
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.FailRBRecfg.NoReply
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of AMR Users with Different UL and DL Rates for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199625
VS.RB.AMR.DL.4.75
Number of AMR Users with

DL rate of 4.75 Kbit/s for
Cell
67199619
VS.RB.AMR.DL.10.2

Cell
67199620
VS.RB.AMR.DL.12.2

Cell
67199621
VS.RB.AMR.DL.7.95

Cell
67199622
VS.RB.AMR.DL.7.4

DL rate of 7.4 Kbit/s for Cell
67199780
VS.RB.AMR.DL.6.7

67199623
VS.RB.AMR.DL.5.9

67199624
VS.RB.AMR.DL.5.15

Cell
67199626
VS.RB.AMR.UL.10.2

UL rate of 10.2 Kbit/s for
Cell
67199627
VS.RB.AMR.UL.12.2

Cell

2940
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199628
VS.RB.AMR.UL.7.95

Cell
67199629
VS.RB.AMR.UL.7.4

UL rate of 7.4 Kbit/s for Cell
67199781
VS.RB.AMR.UL.6.7

67199630
VS.RB.AMR.UL.5.9

67199631
VS.RB.AMR.UL.5.15

Cell
67199632
VS.RB.AMR.UL.4.75

Cell
67203803
VS.RB.AMRWB.DL.23.85
Number of UEs that use the

CS AMR WB speech service
at the DL bit rate of 23.85
kbit/s in the cell
67203804

kbit/s in the cell
67203805

kbit/s in the cell
67203806

kbit/s in the cell
67203807

kbit/s in the cell
67203808

kbit/s in the cell

2941
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67203809

kbit/s in the cell
67203810
VS.RB.AMRWB.DL.8.85

at the DL bit rate of 8.85 kbit/
s in the cell
67203811
VS.RB.AMRWB.DL.6.60

at the DL bit rate of 6.60 kbit/
s in the cell
67203812
VS.RB.AMRWB.UL.23.85

at the UL bit rate of 23.85
kbit/s in the cell
67203813

kbit/s in the cell
67203814

kbit/s in the cell
67203815

kbit/s in the cell
67203816

kbit/s in the cell
67203817

kbit/s in the cell
67203818

kbit/s in the cell

2942
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67203819
VS.RB.AMRWB.UL.8.85

at the UL bit rate of 8.85 kbit/
s in the cell
67203820
VS.RB.AMRWB.UL.6.60

at the UL bit rate of 6.60 kbit/
s in the cell
Description
These counters provide the number of narrowband and wideband AMR users with different
uplink and downlink rates in the cells in the active set.These counters comply with section "8.2.2
Measurement point
The RNC takes samples of numbers of AMR users at different uplink and downlink bit rates for
various types of services every 30 seconds. At the end of the measurement period, the RNC
obtains the mean number of users for each type of service by dividing the accumulated number
of users for each type of service at each bit rate by the sampling times.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RB.AMR.DL.4.75
WRFD-010501
VS.RB.AMR.DL.10.2
WRFD-010501
VS.RB.AMR.DL.12.2
WRFD-010501
VS.RB.AMR.DL.7.95
WRFD-010501
VS.RB.AMR.DL.7.4
WRFD-010501
VS.RB.AMR.DL.6.7
WRFD-010501
VS.RB.AMR.DL.5.9
WRFD-010501
VS.RB.AMR.DL.5.15
WRFD-010501

2943
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RB.AMR.UL.10.2
WRFD-010501
VS.RB.AMR.UL.12.2
WRFD-010501
VS.RB.AMR.UL.7.95
WRFD-010501
VS.RB.AMR.UL.7.4
WRFD-010501
VS.RB.AMR.UL.6.7
WRFD-010501
VS.RB.AMR.UL.5.9
WRFD-010501
VS.RB.AMR.UL.5.15
WRFD-010501
VS.RB.AMR.UL.4.75
WRFD-010501
WRFD-010613

Rate Wide Band)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

2944
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010613

Rate Wide Band)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RB.AMRWB.DL.8.85
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RB.AMRWB.DL.6.60
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

2945
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010613

Rate Wide Band)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RB.AMRWB.UL.8.85
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RB.AMRWB.UL.6.60
WRFD-010613
WRFD-010510

Rate Wide Band)
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

2946
BSC6900 UMTS
Average Number of CS Conversational or Streaming Service RBs for Cell

Counters
Counter ID
Counter Name
Counter Description
67203438
VS.RB.CS.Conv.UL.64

Cell
67199556
VS.RB.CS.Conv.DL.64

Cell
67199560
VS.RB.CS.Str.DL.57.6

DL Rate of 57.6 Kbit/s for
Cell
67203442
VS.RB.CS.Str.UL.57.6

UL Rate of 57.6 Kbit/s for
Cell
Description
These counters provide the average numbers of RBs for various types of CS services at different
uplink and downlink bit rates in a cell of the active set.The preceding counters complies with
section "8.2.2 Reconfiguration procedures" in 3GPP TS 25.331(v10.13.0).
Measurement point
The takes samples of numbers of RBs at different bit rates for various types of CS services every
5 seconds. At the end of the measurement period, the RNC obtains the mean number of RBs for
each type of CS service by dividing the accumulated number of RBs for each type of CS service
at each bit rate by the sampling times.
Formula
None
Unit
None
Issue 03 (2015-06-30)

2947
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RB.CS.Conv.UL.64
WRFD-010501
VS.RB.CS.Conv.DL.64
WRFD-010501
VS.RB.CS.Str.DL.57.6
WRFD-010502
Streaming QoS Class
VS.RB.CS.Str.UL.57.6
WRFD-010502
Streaming QoS Class
Number of RBs for PS R99 Services with various Uplink and Downlink Rates for
Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199598
VS.RB.PS.Bkg.UL.8

Cell
67203430
VS.RB.PS.Conv.DL.64

Kbit/s for Cell
67203434
VS.RB.PS.Conv.UL.64

Kbit/s for Cell
67199594
VS.RB.PS.Bkg.DL.128

for Cell
67199595
VS.RB.PS.Bkg.DL.144

for Cell
67199591
VS.RB.PS.Bkg.DL.16

Cell

2948
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199596
VS.RB.PS.Bkg.DL.256

for Cell
67199592
VS.RB.PS.Bkg.DL.32

Cell
67199597
VS.RB.PS.Bkg.DL.384

for Cell
67199593
VS.RB.PS.Bkg.DL.64

Cell
67199590
VS.RB.PS.Bkg.DL.8

Cell
67199578
VS.RB.PS.Int.DL.128

for Cell
67199579
VS.RB.PS.Int.DL.144

for Cell
67199575
VS.RB.PS.Int.DL.16

Cell
67199580
VS.RB.PS.Int.DL.256

for Cell
67199576
VS.RB.PS.Int.DL.32

Cell

2949
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199581
VS.RB.PS.Int.DL.384

for Cell
67199577
VS.RB.PS.Int.DL.64

Cell
67199574
VS.RB.PS.Int.DL.8

Cell
67199569
VS.RB.PS.Str.DL.128

for Cell
67199570
VS.RB.PS.Str.DL.144

for Cell
67199567
VS.RB.PS.Str.DL.32

Cell
67199568
VS.RB.PS.Str.DL.64

Cell
67203439
VS.RB.PS.Str.DL.8

Cell
67203440
VS.RB.PS.Str.DL.16

Cell
67199602
VS.RB.PS.Bkg.UL.128

for Cell

2950
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199603
VS.RB.PS.Bkg.UL.144

for Cell
67199599
VS.RB.PS.Bkg.UL.16

Cell
67199604
VS.RB.PS.Bkg.UL.256

for Cell
67199600
VS.RB.PS.Bkg.UL.32

Cell
67199605
VS.RB.PS.Bkg.UL.384

for Cell
67199601
VS.RB.PS.Bkg.UL.64

Cell
67199586
VS.RB.PS.Int.UL.128

for Cell
67199587
VS.RB.PS.Int.UL.144

for Cell
67199583
VS.RB.PS.Int.UL.16

Cell
67199588
VS.RB.PS.Int.UL.256

for Cell

2951
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199584
VS.RB.PS.Int.UL.32

Cell
67199589
VS.RB.PS.Int.UL.384

for Cell
67199585
VS.RB.PS.Int.UL.64

Cell
67199582
VS.RB.PS.Int.UL.8

Cell
67199571
VS.RB.PS.Str.UL.16

Cell
67199572
VS.RB.PS.Str.UL.32

Cell
67199573
VS.RB.PS.Str.UL.64

Cell
67203445
VS.RB.PS.Str.UL.8

Cell
67203446
VS.RB.PS.Str.UL.128

for Cell
67203447
VS.RB.PS.Str.UL.144

for Cell

2952
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67203441
VS.RB.PS.Str.DL.256.384

with DL Rate of 256 Kbit/s or
384 Kbit/s for Cell
67203448
VS.RB.PS.Str.UL.256.384

with UL Rate of 256 Kbit/s or
384 Kbit/s for Cell
67204790
VS.RB.PS.Conv.DL.38.8

67204794
VS.RB.PS.Conv.UL.38.8

67204791

67204795

67204792
VS.RB.PS.Conv.DL.40

Kbit/s for Cell
67204796
VS.RB.PS.Conv.UL.40

Kbit/s for Cell
67204793

67204797


2953
BSC6900 UMTS
Description
These counters provide the average number of RBs for PS R99 services with different UL and
DL rates in the cells in the active set.The preceding counters complies with section "8.2.2
Measurement point
The RNC takes samples of numbers of RBs at different bit rates for various types of services
every 5 seconds. At the end of the measurement period, the RNC obtains the mean number of
RBs for each type of service by dividing the accumulated number of RBs for each type of service
at each bit rate by the sampling times.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RB.PS.Bkg.UL.8
WRFD-010504
VS.RB.PS.Conv.DL.64
WRFD-010501
VS.RB.PS.Conv.UL.64
WRFD-010501
VS.RB.PS.Bkg.DL.128
WRFD-010504
VS.RB.PS.Bkg.DL.144
WRFD-010504
VS.RB.PS.Bkg.DL.16
WRFD-010504
VS.RB.PS.Bkg.DL.256
WRFD-010504
VS.RB.PS.Bkg.DL.32
WRFD-010504
VS.RB.PS.Bkg.DL.384
WRFD-010504
VS.RB.PS.Bkg.DL.64
WRFD-010504
VS.RB.PS.Bkg.DL.8
WRFD-010504
VS.RB.PS.Int.DL.128
WRFD-010503
VS.RB.PS.Int.DL.144
WRFD-010503
VS.RB.PS.Int.DL.16
WRFD-010503
VS.RB.PS.Int.DL.256
WRFD-010503
VS.RB.PS.Int.DL.32
WRFD-010503

2954
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RB.PS.Int.DL.384
WRFD-010503
VS.RB.PS.Int.DL.64
WRFD-010503
VS.RB.PS.Int.DL.8
WRFD-010503
VS.RB.PS.Str.DL.128
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.DL.144
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.DL.32
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.DL.64
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.DL.8
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.DL.16
WRFD-010502
Streaming QoS Class
VS.RB.PS.Bkg.UL.128
WRFD-010504
VS.RB.PS.Bkg.UL.144
WRFD-010504
VS.RB.PS.Bkg.UL.16
WRFD-010504
VS.RB.PS.Bkg.UL.256
WRFD-010504
VS.RB.PS.Bkg.UL.32
WRFD-010504
VS.RB.PS.Bkg.UL.384
WRFD-010504
VS.RB.PS.Bkg.UL.64
WRFD-010504
VS.RB.PS.Int.UL.128
WRFD-010503
VS.RB.PS.Int.UL.144
WRFD-010503
VS.RB.PS.Int.UL.16
WRFD-010503
VS.RB.PS.Int.UL.256
WRFD-010503
VS.RB.PS.Int.UL.32
WRFD-010503
VS.RB.PS.Int.UL.384
WRFD-010503
VS.RB.PS.Int.UL.64
WRFD-010503
VS.RB.PS.Int.UL.8
WRFD-010503
VS.RB.PS.Str.UL.16
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.UL.32
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.UL.64
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.UL.8
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.UL.128
WRFD-010502
Streaming QoS Class

2955
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RB.PS.Str.UL.144
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.DL.256.384
WRFD-010502
Streaming QoS Class
VS.RB.PS.Str.UL.256.384
WRFD-010502
Streaming QoS Class
WRFD-010501
WRFD-010501
WRFD-010501
WRFD-010501
VS.RB.PS.Conv.DL.40
WRFD-010501
VS.RB.PS.Conv.UL.40
WRFD-010501
WRFD-010501
WRFD-010501
Number of RB Setup Attempts for Outgoing Inter-Frequency Directed Retry

Counters
Counter ID
Counter Name
Counter Description
67192389
VS.DRD.RBSetup.AttOut
Number of RB Setup
Attempts for Outgoing InterFrequency Directed Retry for
Cell
Description
This counter provides the number of RB setup attempts for the outgoing inter-frequency directed
retry in the best cell that the UE camps on.This counter complies with section "8.2.2
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends to the UE
a RADIO BEARER SETUP message, this counter is measured in the best cell that the UE camps
on if the message is for the inter-frequency directed retry.
Issue 03 (2015-06-30)

2956
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RBSetup.AttOut
WRFD-02040001
Number of Successful RB Setup for Outgoing Inter-Frequency Directed Retry

Counters
Counter ID
Counter Name
Counter Description
67192390
VS.DRD.RBSetup.SuccOut
Setup for Outgoing InterFrequency Directed Retry for
Cell
Description
This counter provides the number of times that the RB is set up successfully for the outgoing
inter-frequency directed retry in the best cell that the UE camps on.This counter complies with
Issue 03 (2015-06-30)

2957
BSC6900 UMTS
Measurement point
the UE a RADIO BEARER SETUP COMPLETE message, this counter is measured in the best
cell that the UE camps on if the message is for the inter-frequency directed retry.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RBSetup.SuccOut
WRFD-02040001
Number of RB Setup Attempts for Incoming Inter-Frequency Directed Retry

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192391
VS.DRD.RBSetup.AttIn
Number of RB Setup
Attempts for Incoming InterFrequency Directed Retry for
Cell

2958
BSC6900 UMTS
Description
This counter provides the number of RB setup attempts for the incoming inter-frequency directed
retry in the cell that the UE camps on.This counter complies with section "8.2.2 Reconfiguration
Measurement point
a RADIO BEARER SETUP message, this counter is measured in the target cell if the message
is for the inter-frequency directed retry.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.RBSetup.AttIn
WRFD-02040001

2959
BSC6900 UMTS
Number of Successful RB Setup for Incoming Inter-Frequency Directed Retry

Counters
Counter ID
Counter Name
Counter Description
67192392
VS.DRD.RBSetup.SuccIn
Setup for Incoming InterFrequency Directed Retry for
Cell
Description
This counter provides the number of times that the RB is set up successfully for the incoming
Measurement point
the UE a RADIO BEARER SETUP COMPLETE message, this counter is measured in the target
cell if the message is for the inter-frequency directed retry.
Formula
None
Issue 03 (2015-06-30)

2960
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RBSetup.SuccIn
WRFD-02040001
Number of RB Reconfiguration Attempts for Outgoing Inter-Frequency Directed

Retry
Counters
Counter ID
Counter Name
Counter Description
67192393
VS.DRD.RBRecfg.AttOut
Number of RB
for Outgoing InterFrequency Directed Retry for
Cell
Description
This counter provides the number of RB reconfiguration attempts for the outgoing interfrequency directed retry in the best cell that the UE camps on.This counter complies with section
Measurement point
a RADIO BEARER RECONFIGURATION message, this counter is measured in the best cell
that the UE camps on if the message is for the inter-frequency directed retry.
Issue 03 (2015-06-30)

2961
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.RBRecfg.AttOut
WRFD-02040001

2962
BSC6900 UMTS
Number of Successful RB Reconfiguration for Outgoing Inter-Frequency Directed

Retry
Counters
Counter ID
Counter Name
Counter Description
67192394
VS.DRD.RBRecfg.SuccOut
Reconfiguration for
Description
This counter provides the number of times that the RB reconfiguration succeeds for the outgoing
Measurement point
the UE a RADIO BEARER RECONFIGURATION COMPLETE message, this counter is
measured in the best cell that the UE camps on if the message is for the inter-frequency directed
retry.
Issue 03 (2015-06-30)

2963
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RBRecfg.SuccOut
WRFD-02040001
Number of RB Reconfiguration Attempts for Incoming Inter-Frequency Directed

Retry
Counters
Counter ID
Counter Name
Counter Description
67192395
VS.DRD.RBRecfg.AttIn
Number of RB
for Incoming InterFrequency Directed Retry for
Cell
Description
This counter provides the number of RB reconfiguration attempts for the incoming interfrequency directed retry in the cell that the UE camps on.This counter complies with section
Measurement point
a RADIO BEARER RECONFIGURATION message, this counter is measured in the target cell
if the message is for the inter-frequency directed retry.
Issue 03 (2015-06-30)

2964
BSC6900 UMTS
Figure 1-1313 RB reconfigureation procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.RBRecfg.AttIn
WRFD-02040001

2965
BSC6900 UMTS
Number of Successful RB Reconfiguration for Incoming Inter-Frequency Directed

Retry
Counters
Counter ID
Counter Name
Counter Description
67192396
VS.DRD.RBRecfg.SuccIn
Reconfiguration for
Description
This counter provides the number of times that the RB reconfiguration succeeds for the incoming
inter-frequency directed retry in the cell that the UE camps on.This counter complies with section
Measurement point
measured in the target cell if the message is for the inter-frequency directed retry.
Issue 03 (2015-06-30)

2966
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RBRecfg.SuccIn
WRFD-02040001
Number of Outgoing or Incoming DCH-to-HSDPA or DCH-to-HSUPA Directed

Retry Attempts
Counters
Counter ID
Counter Name
Counter Description
67192440
VS.DRD.RB.D2H.AttOut
Number of Outgoing DCHto-HSDPA Directed Retry

Attempts for Cell
67192442
VS.DRD.RB.D2H.AttIn
Number of Incoming DCHto-HSDPA Directed Retry

Attempts for Cell
67195503
VS.DRD.RB.D2E.AttOut
Number of Outgoing DCHto-HSUPA Directed Retry

Attempts for Cell
67195505
VS.DRD.RB.D2E.AttIn
Number of Incoming DCHto-HSUPA Directed Retry

Attempts for Cell
Description
These counters provide the number of outgoing or incoming DCH-to-HSDPA or DCH-toHSUPA directed retry attempts in the best cell that the UE camps on. The outgoing directed
retry attempts are measured in the best cell where the UE camps on, and the incoming directed
retry attempts are measured in the target cell of the directed retry. For a DC-HSDPA or DCHSUPA UE, these counters are measured only in the cell configured with the primary cell.The
preceding counters complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS
25.331(v10.13.0).
Issue 03 (2015-06-30)

2967
BSC6900 UMTS
Measurement point
a RADIO BEARER SETUP message, this counter is measured in the best cell where the UE
camps on if the message is for an outgoing DCH-to-HSDPA or DCH-to-HSUPA directed retry,
or measured in the target cell of the directed retry if the message is for an incoming DCH-toHSDPA or DCH-to-HSUPA directed retry.
RADIO BEARER RECONFIGURATION message, this counter is measured in the best cell
where the UE camps on if the message is for an outgoing DCH-to-HSDPA or DCH-to-HSUPA
directed retry, or measured in the target cell of the directed retry if the message is for an incoming
DCH-to-HSDPA or DCH-to-HSUPA directed retry.
Issue 03 (2015-06-30)

2968
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RB.D2H.AttOut
WRFD-01061112
HSDPA DRD
WRFD-02040001
WRFD-01061112
HSDPA DRD
WRFD-02040001
VS.DRD.RB.D2E.AttOut
WRFD-02040001
VS.DRD.RB.D2E.AttIn
WRFD-02040001
VS.DRD.RB.D2H.AttIn
Number of Successful Outgoing or Incoming DCH-to-HSDPA or DCH-to-HSUPA

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192441
VS.DRD.RB.D2H.SuccOut
Outgoing DCH-to-HSDPA
67192443
VS.DRD.RB.D2H.SuccIn
Incoming DCH-to-HSDPA
67195504
VS.DRD.RB.D2E.SuccOut
Number of Successful DCHto-HSUPA Directed Retry

for Cell
67195506
VS.DRD.RB.D2E.SuccIn
Incoming DCH-to-HSUPA

2969
BSC6900 UMTS
Description
These counters provide the number of successful outgoing or incoming DCH-to-HSDPA or
DCH-to-HSUPA directed retry attempts in the best cell that the UE camps on. The outgoing
directed retry attempts are measured in the best cells where the UE camps on, and the incoming
directed retry attempts are measured in the target cell of the directed retry. For a DC-HSDPA
or DC-HSUPA UE, this counter is measured only in the primary cell.The preceding counters
Measurement point
the UE a RADIO BEARER SETUP COMPLETE message, this counter is measured in the best
cell where the UE camps on if the message is for an outgoing RB DCH-to-HSDPA or RB DCHto-HSUPA directed retry, or measured in the target cell of the directed retry if the message is
for an incoming RB DCH-to-HSDPA or RB DCH-to-HSUPA directed retry.
measured in the best cell where the UE camps on if the message is for an outgoing RB DCHto-HSDPA or RB DCH-to-HSUPA directed retry, or measured in the target cell of the directed
retry if the message is for an incoming RB DCH-to-HSDPA or RB DCH-to-HSUPA directed
retry.
Issue 03 (2015-06-30)

2970
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RB.D2H.SuccOut
WRFD-01061112
HSDPA DRD
WRFD-02040001
WRFD-01061112
HSDPA DRD
WRFD-02040001
VS.DRD.RB.D2E.SuccOut
WRFD-02040001
VS.DRD.RB.D2E.SuccIn
WRFD-02040001
VS.DRD.RB.D2H.SuccIn
Issue 03 (2015-06-30)

2971
BSC6900 UMTS
Number of Successful Directed Retry Attempts Based on Inter-Frequency

Counters
Counter ID
Counter Name
Counter Description
67196294
VS.DRD.IFREQ.CS.MBDR
.RBSetup.SuccOut
Voice Directed Retry Based
on Inter-Frequency
67196296
VS.DRD.IFREQ.PS.MBDR
.R99.RBSetup.SuccOut
R99 Directed Retry Based on
Inter-Frequency
67196298
.HResCong.RBSetup.SuccOut
HSDPA PS Directed Retry
Based on Inter-Frequency
Description
These counters provide the number of successful directed retry attempts of different services
based on the inter-frequency measurement in the best cell. The number of successful directed
retry attempts for the HSDPA service based on the inter-frequency measurement is measured in
the serving cell of the HSDPA service.The preceding counters complies with section "8.2.2
Measurement point
the UE a RADIO BEARER SETUP COMPLETE message, the number of successful outgoing
directed retry attempts based on inter-frequency measurement is measured in the best cell where
the UE camps on. These counters are measured in the serving cell of the HSDPA service of the
UE if the message is for the PS directed retry based on inter-frequency measurement due to
HSDPA resource insufficiency.
Issue 03 (2015-06-30)

2972
BSC6900 UMTS
Figure 1-1319 RB SetUp Process
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.RBSetup.SuccOut
WRFD-020103

Balance
WRFD-020402

Retry
.R99.RBSetup.SuccOut
WRFD-020103
WRFD-020402

Balance
Retry
.HResCong.RBSetup.SuccOut
Issue 03 (2015-06-30)
WRFD-020103
WRFD-020402


Balance
Retry
2973
BSC6900 UMTS
Number of Directed Retry Attempts Based on Inter-Frequency Measurement for

Cell
Counters
Counter ID
Counter Name
Counter Description
67196293
.RBSetup.AttOut
Number of CS Voice
Directed Retry Attempts
67196295
.R99.RBSetup.AttOut
Number of PS R99 Directed

Retry Attempts Based on
Inter-Frequency
67196297
.HResCong.RBSetup.AttOut
Number of HSDPA PS
Description
These counters provide the number of directed retry attempts for different services based on the
inter-frequency measurement in the best cell.The preceding counters complies with section
Measurement point
RADIO BEARER SETUP message, the number of outgoing directed retry attempts based on
inter-frequency measurement is measured in the best cell where the UE camps on.
Figure 1-1320 RB SetUp Process
Issue 03 (2015-06-30)

2974
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.RBSetup.AttOut
WRFD-020103

Balance
WRFD-020402

Retry
.R99.RBSetup.AttOut
WRFD-020103
WRFD-020402

Balance
Retry
.HResCong.RBSetup.AttOut
WRFD-020103
WRFD-020402

Balance
Retry
Number of Times that PS Rate Downgrades to 0 Kbit/s

Counters
Counter ID
Counter Name
Counter Description
67196303
VS.RB.RateDown.To.0kbps
Number of Times that PS

Rate Downgrades to 0 Kbit/s
in the Best Cell
Description
This counter provides the number of times that the rate of PS R99 services downgrades to 0
Kbit/s.This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS
25.331(v10.13.0).
Measurement point
The measurement is triggered when the rate of PS R99 services downgrades to 0 Kbit/s.
Issue 03 (2015-06-30)

2975
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RB.RateDown.To.0kbps
WRFD-021101
Dynamic Channel
(DCCC)
Average Number of PS Conversation RBs on EDCH or HS-DSCH for Cell

Counters
Counter ID
Counter Name
Counter Description
73415857
VS.RB.PS.Conv.HSDSCH
Number of PS Conversation
UEs on HS-DSCH for Cell
73415858
VS.RB.PS.Conv.EDCH
Number of PS Conversation
UEs on EDCH for Cell
Description
These counters provide the average number of PS Conversation RBs on EDCH or HS-DSCH
in the cell. The downlink RBs on the HS-DSCH are measured in the serving cell, and the uplink
RBs on the EDCH are measured in the cells of the HSUPA active set. For a DC-HSDPA or DCHSUPA UE, these counters are measured only in the primary cell.The preceding counters
Measurement point
The RNC takes samples of PS conversation RB numbers carried on EDCH in the cells of the
HSUPA active set or PS conversation RB numbers carried on HS-DSCH in the serving cell of
HSDPA services every 5 seconds. At the end of a sampling period, the RNC obtains the average
number of PS conversation RBs carried on the EDCH or HS-DSCH by dividing the accumulated
number by the sampling times.
Formula
None
Issue 03 (2015-06-30)

2976
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RB.PS.Conv.HSDSCH
WRFD-010617
WRFD-010501
WRFD-010617
WRFD-010501
VS.RB.PS.Conv.EDCH
Number of Outgoing DRD Attempts through Physical Channel Reconfiguration

(Cell)
Counters
Counter ID
Counter Name
Counter Description
73394053
VS.DRD.PhyRecfg.AttOut
Number of Outgoing DRD

Attempts through Physical
Channel Reconfiguration for
Cell
Description
This counter provides the number of outgoing inter-frequency directed retry attempts through
physical channel reconfiguration in the best cell that the UE camps on before directed retry.This
(v10.13.0).
Measurement point
PHYSICAL CHANNEL RECONFIGURATION message for inter-frequency directed retry,
this counter is measured in the best cell that the UE camps on before directed retry.
Issue 03 (2015-06-30)

2977
BSC6900 UMTS
Figure 1-1321 Physical channel reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.PhyRecfg.AttOut
WRFD-020103

Balance
WRFD-02040001
Number of Successful Outgoing DRDs through Physical Channel Reconfiguration

(Cell)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73394054
VS.DRD.PhyRecfg.SuccOut
Outgoing DRDs through
Physical Channel

2978
BSC6900 UMTS
Description
This counter provides the number of successful outgoing inter-frequency directed retries through
physical channel reconfiguration in the best cell that the UE camps on before directed retry.This
(v10.13.0).
Measurement point
the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message for interfrequency directed retry, this counter is measured in the best cell that the UE camps on before
directed retry.
Figure 1-1322 Physical Channel Reconfiguration procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.PhyRecfg.SuccOut
WRFD-020103

Balance
WRFD-02040001
Issue 03 (2015-06-30)

2979
BSC6900 UMTS
Number of Incoming DRD Attempts through Physical Channel Reconfiguration

(Cell)
Counters
Counter ID
Counter Name
Counter Description
73394055
VS.DRD.PhyRecfg.AttIn
Number of Incoming DRD

Attempts through Physical
Cell
Description
This counter provides the number of incoming inter-frequency directed retry attempts through
physical channel reconfiguration in the cell.This counter complies with section "8.2.2
Measurement point
PHYSICAL CHANNEL RECONFIGURATION message for inter-frequency directed retry,
this counter is measured in the target cell of the directed retry.
Formula
None
Issue 03 (2015-06-30)

2980
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.PhyRecfg.AttIn
WRFD-020103

Balance
WRFD-02040001
Number of Successful Incoming DRDs through Physical Channel Reconfiguration

(Cell)
Counters
Counter ID
Counter Name
Counter Description
73394056
VS.DRD.PhyRecfg.SuccIn
Incoming DRDs through
Physical Channel
Description
This counter provides the number of successful incoming inter-frequency directed retries
through physical channel reconfiguration in the cell.This counter complies with section "8.2.2
Measurement point
the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message for interfrequency directed retry, this counter is measured in the target cell of the directed retry.
Issue 03 (2015-06-30)

2981
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.PhyRecfg.SuccIn
WRFD-020103

Balance
WRFD-02040001
Number of RB Setup Attempts After the RB Setup DRD Rollback

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421487
VS.DRD.RBSetup.AttEstab.
RollBack
Number of RB Setup
Attempts After the RB Setup
DRD Rollback

2982
BSC6900 UMTS
Description
This counter provides the number that the UE attempts to set up an RB in a target cell after the
UE fails to set up an RB through DRD and the RNC performs the rollback. This counter is
measured in the target cell.This counter complies with section "8.2.2 Reconfiguration
Measurement point
After the RNC receives an RADIO BEARER SETUP FAILURE message in an RB setup DRD
procedure, it sends an RADIO BEARER SETUP message to a target cell if it determines that a
rollback can be performed, as shown in point A of the figure. This counter is measured in the
target cell when the RNC sends the RADIO BEARER SETUP message.
Figure 1-1325 RB Setup DRD
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.RBSetup.AttEstab.
RollBack
WRFD-02040001

2983
BSC6900 UMTS
Number of successful RB Setups After the RB Setup DRD Rollback

Counters
Counter ID
Counter Name
Counter Description
73421488
VS.DRD.RBSetup.SuccEsta
b.RollBack
Number of successful RB
Setups After the RB Setup
DRD Rollback
Description
This counter provides the number that the UE sets up an RB successfully in a cell after the UE
fails to set up an RB through DRD and the RNC performs the rollback. This counter is measured
in the target cell.This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP
TS 25.331(v10.13.0).
Measurement point
After the RNC receives an RADIO BEARER SETUP FAILURE message in an RB setup DRD
procedure, it sends an RADIO BEARER SETUP message to a target cell if it determines that a
rollback can be performed, as shown in point A of the figure. This counter is measured in the
target cell when the RNC receives an RADIO BEARER SETUP COMPLETE message from
the UE.
Figure 1-1326 RB Setup DRD
Formula
None
Issue 03 (2015-06-30)

2984
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RBSetup.SuccEsta
b.RollBack
WRFD-02040001
Number of RB Reconfiguration Attempts After the RB Reconfiguration DRD

Rollback
Counters
Counter ID
Counter Name
Counter Description
73421489
VS.DRD.RBRecfg.AttEstab
.RollBack
Number of RB
After the RB
Reconfiguration DRD
Rollback
Description
This counter provides the number that the RNC attempts to reconfigure an RB in a cell after the
RB reconfigure through DRD fails and the RNC performs the rollback. This counter is measured
in the target cell.This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP
TS 25.331(v10.13.0).
Measurement point
After the RNC receives an RADIO BEARER RECONFIGURATION FAILURE message in an
RB reconfiguration DRD procedure, it sends an RADIO BEARER RECONFIGURATION
message to a target cell if it determines that a rollback can be performed, as shown in point A
of the figure. This counter is measured in the target cell when the RNC sends the RADIO
BEARER RECONFIGURATION message.
Issue 03 (2015-06-30)

2985
BSC6900 UMTS
Figure 1-1327 RB Reconfiguration DRD
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RBRecfg.AttEstab
.RollBack
WRFD-02040001
Number of Successful RB Reconfigurations After the RB Reconfiguration DRD

Rollback
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421490
VS.DRD.RBRecfg.SuccEsta
b.RollBack
Reconfigurations After the
RB Reconfiguration DRD
Rollback

2986
BSC6900 UMTS
Description
This counter provides the number that the RB reconfiguration succeeds in a cell after the RNC
fails to reconfigure an RB through DRD and performs the rollback. This counter is measured in
the target cell.
Measurement point
After the RNC receives an RADIO BEARER RECONFIGURATION FAILURE message in an
RB reconfiguration DRD procedure, it sends an RADIO BEARER RECONFIGURATION
message to a target cell if it determines that a rollback can be performed, as shown in point A
of the figure. This counter is measured in the target cell when the RNC receives an RADIO
BEARER RECONFIGURATION COMPLETE message from the UE.
Figure 1-1328 RB Reconfiguration DRD
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.RBRecfg.SuccEsta
b.RollBack
WRFD-02040001

2987
BSC6900 UMTS
Number of Physical Channel Reconfiguration Attempts After the Physical Channel

Reconfiguration DRD Rollback
Counters
Counter ID
Counter Name
Counter Description
73421491
VS.DRD.PhyRecfg.AttEsta
b.RollBack
Number of Physical Channel

After the Physical Channel
Reconfiguration DRD
Rollback
Description
This counter provides the number that the RNC attempts to perform physical channel
reconfiguration in a cell after the physical channel reconfiguration through DRD fails and the
RNC performs the rollback. This counter is measured in the target cell.This counter complies
Measurement point
After the RNC receives a PHYSICAL CHANNEL RECONFIGURATION FAILURE message
in a physical channel reconfiguration DRD procedure, it sends a PHYSICAL CHANNEL
RECONFIGURATION message to a target cell if it determines that a rollback can be performed,
as shown in point A of the figure. This counter is measured in the target cell when the RNC
sends the PHYSICAL CHANNEL RECONFIGURATION message.
Figure 1-1329 Physical Channel Reconfiguration DRD
Issue 03 (2015-06-30)

2988
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.PhyRecfg.AttEsta
b.RollBack
WRFD-02040001
Number of Successful Physical Channel Reconfigurations After the Physical

Channel Reconfiguration DRD Rollback
Counters
Counter ID
Counter Name
Counter Description
73421492
VS.DRD.PhyRecfg.SuccEst
ab.RollBack
Physical Channel
Reconfigurations After the
Physical Channel
Reconfiguration DRD
Rollback
Description
This counter provides the number that the physical channel reconfiguration succeeds in a cell
after the RNC fails to reconfigure physical channels through DRD and performs the rollback.
This counter is measured in the target cell.This counter complies with section "8.2.2
Measurement point
After the RNC receives a PHYSICAL CHANNEL RECONFIGURATION FAILURE message
in a physical channel reconfiguration DRD procedure, it sends a PHYSICAL CHANNEL
RECONFIGURATION message to a target cell if it determines that a rollback can be performed,
as shown in point A of the figure. This counter is measured in the target cell when the RNC
receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE.
Issue 03 (2015-06-30)

2989
BSC6900 UMTS
Figure 1-1330 Physical Channel Reconfiguration DRD
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.PhyRecfg.SuccEst
ab.RollBack
WRFD-02040001
Number of Outgoing or Incoming FACH-to-HSDPA or FACH-HSUPA Directed

Retry Attempts for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421842
VS.DRD.RB.F2H.AttOut
Number of Outgoing FACHto-HSDPA Directed Retry

Attempts for Cell

2990
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421844
VS.DRD.RB.F2E.AttOut
Number of Outgoing FACHto-HSUPA Directed Retry

Attempts for Cell
73421846
VS.DRD.RB.F2H.AttIn
Number of Incoming FACHto-HSDPA Directed Retry

Attempts for Cell
73421848
VS.DRD.RB.F2E.AttIn
Number of Incoming FACHto-HSUPA Directed Retry

Attempts for Cell
Description
These counters provide the number of outgoing or incoming FACH-to-HSDPA or FACHHSUPA directed retry attempts. The outgoing directed retry attempts are measured in the source
cell of the directed retry, and the incoming directed retry attempts are measured in the target cell
of the directed retry. For a DC-HSDPA or DC-HSUPA UE, these counters are measured only
in the primary cell.The preceding counters complies with section "8.2.2 Reconfiguration
Measurement point
RADIO BEARER SETUP message, these counters are measured in the source or target cell
where the UE camps on if the message is for the FACH-to-HSDPA or FACH-to-HSUPA directed
retry.
Figure 1-1331 RB setup procedure
RADIO BEARER RECONFIGURATION message, these counters are measured in the source
or target cell where the UE camps on if the message is for the FACH-to-HSDPA or FACH-toHSUPA directed retry.
Issue 03 (2015-06-30)

2991
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.DRD.RB.F2H.AttOut
WRFD-01061112
HSDPA DRD
WRFD-02040001
VS.DRD.RB.F2E.AttOut
WRFD-02040001
VS.DRD.RB.F2H.AttIn
WRFD-01061112
HSDPA DRD
WRFD-02040001
WRFD-02040001
VS.DRD.RB.F2E.AttIn
Issue 03 (2015-06-30)

2992
BSC6900 UMTS
Number of Successful Outgoing or Incoming FACH-to-HSDPA or FACH-HSUPA

Directed Retry Attempts for Cell
Counters
Counter ID
Counter Name
Counter Description
73421843
VS.DRD.RB.F2H.SuccOut
Outgoing FACH-to-HSDPA
Directed Retries for Cell
73421845
VS.DRD.RB.F2E.SuccOut
Outgoing FACH-to-HSUPA
73421847
VS.DRD.RB.F2H.SuccIn
Incoming FACH-to-HSDPA
73421849
VS.DRD.RB.F2E.SuccIn
Incoming FACH-to-HSUPA
Description
These counters provide the number of successful outgoing FACH-to-HSDPA or FACH-toHSUPA directed retries in the source cell. The outgoing directed retry attempts are measured in
the source cell of the directed retry, and the incoming directed retry attempts are measured in
the target cell of the directed retry. For a DC-HSDPA or DC-HSUPA UE, these counters are
measured only in the primary cell.The preceding counters complies with section "8.2.2
Measurement point
the UE a RADIO BEARER SETUP COMPLETE message, these counters are measured in the
source or target cell where the UE camps on if the message is for the FACH-to-HSDPA or
FACH-to-HSUPA directed retry.
Issue 03 (2015-06-30)

2993
BSC6900 UMTS
the UE a RADIO BEARER RECONFIGURATION COMPLETE message, these counters are
measured in the source or target cell where the UE camps on if the message is for the FACHto-HSDPA or FACH-to-HSUPA directed retry.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.RB.F2H.SuccOut
WRFD-01061112
HSDPA DRD
WRFD-02040001
VS.DRD.RB.F2E.SuccOut
WRFD-02040001
VS.DRD.RB.F2H.SuccIn
WRFD-01061112
HSDPA DRD
WRFD-02040001

2994
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.DRD.RB.F2E.SuccIn
WRFD-02040001
Number of CELL_FACH to CELL_PCH Transition Attempts by Physical Channel

Counters
Counter ID
Counter Name
Counter Description
73394177
VS.AttPhyRecfg.F2P
Number of CELL_FACH to
CELL_PCH Transition
Attempts by Physical
Cell
Description
This counter provides the number of state transition attempts from CELL_FACH to CELL_PCH
by physical channel reconfiguration in a cell.This counter complies with section "8.2.2
Measurement point
The measurement is triggered at point A, as shown in the following figure. When the RNC sends
a PHYSICAL CHANNEL RECONFIGURATION message to a UE, instructing the UE to
transfer from the CELL_FACH state to the CELL_PCH state, this counter is incremented by
one in the cell where the UE is camping.
Figure 1-1335 cd
Issue 03 (2015-06-30)

2995
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttPhyRecfg.F2P
WRFD-010202

URA-PCH, CELL-FACH)
Number of SuccessfulCELL_FACH to CELL_PCH Transitions by Physical Channel

Counters
Counter ID
Counter Name
Counter Description
73394178
VS.SuccPhyRecfg.F2P
CELL_FACH to
CELL_PCH Transitions by
Physical Channel
Description
CELL_PCH by physical channel reconfiguration in a cell.This counter complies with section
Measurement point
The measurement is triggered at point B, as shown in the following figure. When the RNC
receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from a UE,
indicating that the UE has transfered from the CELL_FACH state to the CELL_PCH state, this
counter is incremented by one in the cell where the UE is camping.
Issue 03 (2015-06-30)

2996
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccPhyRecfg.F2P
WRFD-010202

URA-PCH, CELL-FACH)
Number of Outgoing or Incoming Inter-Frequency DRD Attempts Triggered by

Multiband Directed Retry Based on UE Location for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425827
VS.UELocation.MultiBand.
DRD.AttIn
Number of Incoming InterFrequency DRD Attempts

Triggered by Multiband
Direct Retry Based on UE
Location for Cell

2997
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73425836
DRD.AttOut
Number of Outgoing InterFrequency DRD Attempts

Triggered by Multiband
Direct Retry Based on UE
Location for Cell
Description
These counters provide the number of outgoing or incoming inter-frequency directed retry
attempts triggered by the Multiband Directed Retry Based on UE Location feature. The outgoing
inter-frequency directed retry attempts are measured in the best cell where the UE camps on
before the directed retry, and the incoming inter-frequency directed retry attempts are measured
in the target cell of the directed retry.The preceding counters complies with section "8.2.2
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends a RADIO
BEARER SETUP message to the UE and a directed retry is triggered by the Multiband Directed
Retry based on UE location, the number of outgoing inter-frequency directed retry attempts
triggered by the Multiband Directed Retry based on UE location is measured in the best cell
where the UE camps on before the directed retry, and the number of incoming inter-frequency
directed retry attempts triggered by the Multiband Directed Retry based on UE location is
measured in the target cell of the directed retry.
The measurement is triggered at point A as shown in the figure. When the RNC sends a RADIO
BEARER RECONFIGURATION message to the UE and a directed retry is triggered by the
Multiband Directed Retry based on UE location, the number of outgoing inter-frequency directed
retry attempts triggered by the Multiband Directed Retry based on UE location is measured in
the best cell where the UE camps on before the directed retry, and the number of incoming interIssue 03 (2015-06-30)

2998
BSC6900 UMTS
frequency directed retry attempts triggered by the Multiband Directed Retry based on UE
location is measured in the target cell of the directed retry.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
DRD.AttIn
WRFD-150232
Multiband Direct Retry

Based on UE Location
DRD.AttOut
WRFD-150232


2999
BSC6900 UMTS
Number of Successful Incoming Inter-Frequency DRDs Triggered by Multiband

Directed Retry Based on UE Location for a Cell
Counters
Counter ID
Counter Name
Counter Description
73425835
DRD.SuccIn
DRDs Triggered by
Based on UE Location for
Cell
73425837
DRD.SuccOut
DRDs Triggered by
Based on UE Location for
Cell
Description
These counters provide the number of successful outgoing or incoming inter-frequency directed
retry attempts triggered by the multiband directed retry decision (DRD) Based on UE Location
feature. The outgoing inter-frequency directed retry attempts are measured in the best cell where
the UE camps on before the directed retry and the incoming inter-frequency directed retry
attempts are measured in the target cell of the directed retry.The preceding counters complies
Measurement point
The measurement is triggered at point B as shown in the figure. When the RNC sends a RADIO
BEARER SETUP COMPLETE message to the UE and the directed retry is triggered by
multiband directed retry decision (DRD) based on UE location, the number of successful
outgoing inter-frequency directed retry attempts triggered by the multiband directed retry
decision (DRD) based on UE location is measured in the best cell where the UE camps before
the directed retry, and the number of successful incoming inter-frequency directed retry attempts
triggered by multiband directed retry decision (DRD) based on UE location is measured in the
target cell of the directed retry.
Issue 03 (2015-06-30)

3000
BSC6900 UMTS
The measurement is triggered at point B as shown in the figure. When the RNC sends a RADIO
BEARER RECONFIGURATION COMPLETE message to the UE and the directed retry is
triggered by multiband directed retry decision (DRD) based on UE location, the number of
successful outgoing inter-frequency directed retry attempts triggered by multiband directed retry
decision (DRD) based on UE location is measured in the best cell where the UE camps on before
the directed retry, and the number of successful incoming inter-frequency directed retry attempts
triggered by multiband directed retry decision (DRD) based on UE location is measured in the
target cell of the directed retry.
Issue 03 (2015-06-30)

3001
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
DRD.SuccIn
WRFD-150232

DRD.SuccOut
WRFD-150232

Number of Periodic Inter-Frequency Ingoing Directed Retry Attempts based on

Counters
Counter ID
Counter Name
Counter Description
73426249
VS.MCDRD.Periodic.AttOut
Number of Periodic InterFrequency Outgoing

based on Measurement for
Cell
73426251
VS.MCDRD.Periodic.AttIn
Number of Periodic InterFrequency Ingoing Directed

Retry Attempts based on
Description
These counters provide the number of periodic inter-frequency outgoing or incoming directed
retry attempts based on measurement. The outgoing inter-frequency directed retry attempts are
measured in the best cell where the UE camps on before the directed retry, and the incoming
inter-frequency directed retry attempts are measured in the target cell of the directed retry.The
preceding counters complies with section "8.2.2 Reconfiguration procedures" in 3GPP TS
25.331(v10.13.0).
Measurement point
The measurement is triggered at point A as shown in Figure 1, when the RNC sends a RADIO
BEARER RECONFIGURATION message to the UE. In this case, this counter measures the
Issue 03 (2015-06-30)

3002
BSC6900 UMTS
total number of periodic inter-frequency outgoing or incoming directed retries in the best cell
where the UE camps on before the directed retry or the target cell of the directed retry when
measurement-based periodic inter-frequency directed retry is enabled.
The measurement is triggered at point A as shown in Figure 2, when the RNC sends a PHYSICAL
CHANNEL RECONFIGURATION message to the UE. In this case, this counter measures the
total number of periodic inter-frequency outgoing or incoming directed retries in the best cell
where the UE camps on before the directed retry or the target cell of the directed retry when
measurement-based periodic inter-frequency directed retry is enabled.
Issue 03 (2015-06-30)

3003
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MCDRD.Periodic.AttOut
WRFD-02040004
Traffic Steering and Load

Sharing During RAB Setup
WRFD-020160
Enhanced Multiband
Management
VS.MCDRD.Periodic.AttIn
WRFD-02040004
WRFD-020160

Enhanced Multiband
Management
Number of Successful Periodic Inter-Frequency Ingoing Directed Retry Attempts

based on Measurement for Cell
Counters
Counter ID
Counter Name
Counter Description
73426250
VS.MCDRD.Periodic.SuccOut
Periodic Inter-Frequency
Outgoing Directed Retries
Cell
73426252
VS.MCDRD.Periodic.SuccIn
Periodic Inter-Frequency
Ingoing Directed Retries
Cell
Description
These counters provide the number of successful periodic inter-frequency outgoing or incoming
directed retry attempts based on measurement. The outgoing inter-frequency directed retry
attempts are measured in the best cell where the UE camps on before the directed retry and the
Issue 03 (2015-06-30)

3004
BSC6900 UMTS
incoming inter-frequency directed retry attempts are measured in the target cell of the directed
retry.The preceding counters complies with section "8.2.2 Reconfiguration procedures" in 3GPP
TS 25.331(v10.13.0).
Measurement point
BEARER RECONFIGURATION COMPLETE message from the UE. In this case, this counter
measures the total number of successful periodic inter-frequency outgoing or incoming directed
retries in the best cell where the UE camps on before the directed retry or the target cell of the
directed retry when measurement-based periodic inter-frequency directed retry is enabled.
The measurement is triggered at point B as shown in Figure 2, when the RNC receives a
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE. In this
case, this counter measures the total number of successful periodic inter-frequency outgoing or
incoming directed retries in the best cell where the UE camps on before the directed retry or the
target cell of the directed retry when measurement-based periodic inter-frequency directed retry
is enabled.
Issue 03 (2015-06-30)

3005
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MCDRD.Periodic.SuccOut
WRFD-02040004

WRFD-020160
Enhanced Multiband
Management
VS.MCDRD.Periodic.SuccIn
WRFD-02040004
WRFD-020160

Enhanced Multiband
Management
Issue 03 (2015-06-30)

3006
BSC6900 UMTS
The number of times the RNC makes a rollback after the DRD procedure fails
during RB setup
Counters
Counter ID
Counter Name
Counter Description
73428927
VS.DRD.FailRBSetup.RollBack
The number of times the

RNC makes a rollback after
the DRD procedure fails
during RB setup
Description
This counter provides the number of times the RNC makes a rollback after the DRD procedure
fails during RB setup. This counter is measured in the best cell that the UE camps on before
directed retry.This counter complies with section "8.2.2 Reconfiguration procedures" in 3GPP
TS 25.331(v10.13.0).
Measurement point
The RNC sends a RADIO BEARER SETUP message to a UE and a directed retry decision
(DRD) procedure is triggered; the DRD procedure then fails. This counter is measured in the
best cell for the UE when the RNC determines to roll back the DRD procedure. The DRD
procedure failure is indicated by either of the following in this scenario: The RNC receives a
RADIO BEARER SETUP FAILURE message from the UE. The RB setup times out for the UE
that is transitioning from the CELL_FACH state to the CELL_DCH state to perform combined
services.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.FailRBSetup.RollBack
WRFD-020400
DRD Introduction Package

3007
BSC6900 UMTS
during RB reconfiguration
Counters
Counter ID
Counter Name
Counter Description
73428928
VS.DRD.FailRBRecfg.RollBack

during RB reconfiguration
Description
fails during RB reconfiguration. This counter is measured in the best cell that the UE camps on
before directed retry.This counter complies with section "8.2.2 Reconfiguration procedures" in
3GPP TS 25.331(v10.13.0).
Measurement point
The RNC sends a RADIO BEARER RECONFIGURATION message to a UE and a DRD
procedure is triggered; the DRD procedure then fails. This counter is measured in the best cell
for the UE when the RNC determines to roll back the DRD procedure. The DRD procedure
failure is indicated by either of the following in this scenario: The RNC receives a RADIO
BEARER RECONFIGURATION FAILURE message from the UE. The RB reconfiguration
times out for the UE that is transitioning from the CELL_FACH state to the CELL_DCH state.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.FailRBRecfg.RollBack
WRFD-020400

3008
BSC6900 UMTS
during physical channel reconfiguration
Counters
Counter ID
Counter Name
Counter Description
73428929
VS.DRD.FailPhyRecfg.Roll
Back

during physical channel
reconfiguration
Description
fails during physical channel reconfiguration. This counter is measured in the best cell that the
UE camps on before directed retry.This counter complies with section "8.2.2 Reconfiguration
Measurement point
The RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to a UE and a DRD
procedure is triggered; the DRD procedure then fails. This counter is measured in the best cell
for the UE when the RNC determines to roll back the DRD procedure. The DRD procedure
failure is indicated by the PHYSICAL CHANNEL RECONFIGURATION FAILURE message
received by the RNC or the Physical Channel reconfiguration times out for the UE in this
scenario.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DRD.FailPhyRecfg.Roll
Back
WRFD-020400

3009
BSC6900 UMTS
Number of RBs for PS Services with Downlink Carried on the DCH for Cell
Counters
Counter ID
Counter Name
Counter Description
73446471
VS.RB.PS.DLDCH.BestCell
Number of RBs for PS

Services with Downlink
Carried on the DCH for Cell
Description
This counter measures the average number of RBs for PS services with downlink carried on the
DCH in the best cell.
Measurement point
The system periodically takes samples (sampling period is 30 seconds) of the number of RBs
for PS services with downlink carried on the DCH. At the end of the measurement period, the
average number of RBs for PS services with downlink carried on the DCH is obtained by dividing
the accumulated value of the sampling results in the period by the number of samplings.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RB.PS.DLDCH.BestCell
WRFD-010501
WRFD-010502
Streaming QoS Class
WRFD-010503
WRFD-010504
1.12.39 Reserved Counter Measurement <per Cell>(RESERVE.Cell)

Overview
Reserved counter is used temporarily in patch versions and will be replaced with a new counter
in later versions. For the detailed information about used reserved counters, see the "Used
Reserved Counter List" of the corresponding version.
Issue 03 (2015-06-30)

3010
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423106
VS.Reserve.Counter5
Reserved counter 5
for cell
BSC6900
V900R013
73423305
VS.Reserve.Counter8
Reserved counter 8
for cell
BSC6900
V900R013
73423306
VS.Reserve.Counter9
Reserved counter 9
for cell
BSC6900
V900R013
73423301
VS.Reserve.Counter10
Reserved counter 10
for cell
BSC6900
V900R013
73423302
Reserved counter 11
for cell
BSC6900
V900R013
73423421
VS.Reserve.Counter1
Reserved counter 1
for cell
BSC6900
V900R013
73423422
VS.Reserve.Counter2
Reserved counter 2
for cell
BSC6900
V900R013
73423423
VS.Reserve.Counter3
Reserved counter 3
for cell
BSC6900
V900R013
73423424
VS.Reserve.Counter4
Reserved counter 4
for cell
BSC6900
V900R013
73423425
VS.Reserve.Counter6
Reserved counter 6
for cell
BSC6900
V900R013
73423426
VS.Reserve.Counter7
Reserved counter 7
for cell
BSC6900
V900R013
73423427
Reserved counter 12
for cell
BSC6900
V900R013
73423428
Reserved counter 13
for cell
BSC6900
V900R013
73423429
Reserved counter 14
for cell
BSC6900
V900R013
73423430
Reserved counter 15
for cell
BSC6900
V900R013
73423431
Reserved counter 16
for cell
BSC6900
V900R013
73423432
Reserved counter 17
for cell
BSC6900
V900R013

3011
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423433
Reserved counter 18
for cell
BSC6900
V900R013
73423434
Reserved counter 19
for cell
BSC6900
V900R013
73423435
Reserved counter 20
for cell
BSC6900
V900R013
73423436
Reserved counter 21
for cell
BSC6900
V900R013
73423437
Reserved counter 22
for cell
BSC6900
V900R013
73423438
Reserved counter 23
for cell
BSC6900
V900R013
73423439
Reserved counter 24
for cell
BSC6900
V900R013
73423440
Reserved counter 25
for cell
BSC6900
V900R013
73423441
Reserved counter 26
for cell
BSC6900
V900R013
73423442
Reserved counter 27
for cell
BSC6900
V900R013
73423443
Reserved counter 28
for cell
BSC6900
V900R013
73423444
Reserved counter 29
for cell
BSC6900
V900R013
73423445
Reserved counter 30
for cell
BSC6900
V900R013
73429009
Reserved counter 31
for cell
BSC6900
V900R016C00
73429010
Reserved counter 32
for cell
BSC6900
V900R016C00
73429011
Reserved counter 33
for cell
BSC6900
V900R016C00
73429012
Reserved counter 34
for cell
BSC6900
V900R016C00
73429013
Reserved counter 35
for cell
BSC6900
V900R016C00

3012
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429014
Reserved counter 36
for cell
BSC6900
V900R016C00
73429015
Reserved counter 37
for cell
BSC6900
V900R016C00
73429016
Reserved counter 38
for cell
BSC6900
V900R016C00
73429017
Reserved counter 39
for cell
BSC6900
V900R016C00
73429018
Reserved counter 40
for cell
BSC6900
V900R016C00
73429019
Reserved counter 41
for cell
BSC6900
V900R016C00
73429020
Reserved counter 42
for cell
BSC6900
V900R016C00
73429021
Reserved counter 43
for cell
BSC6900
V900R016C00
73429022
Reserved counter 44
for cell
BSC6900
V900R016C00
73429023
Reserved counter 45
for cell
BSC6900
V900R016C00
73429024
Reserved counter 46
for cell
BSC6900
V900R016C00
73429025
Reserved counter 47
for cell
BSC6900
V900R016C00
73429026
Reserved counter 48
for cell
BSC6900
V900R016C00
73429027
Reserved counter 49
for cell
BSC6900
V900R016C00
73429028
Reserved counter 50
for cell
BSC6900
V900R016C00
73429029
Reserved counter 51
for cell
BSC6900
V900R016C00
73429030
Reserved counter 52
for cell
BSC6900
V900R016C00
73429031
Reserved counter 53
for cell
BSC6900
V900R016C00

3013
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429032
Reserved counter 54
for cell
BSC6900
V900R016C00
73429033
Reserved counter 55
for cell
BSC6900
V900R016C00
73429034
Reserved counter 56
for cell
BSC6900
V900R016C00
73429035
Reserved counter 57
for cell
BSC6900
V900R016C00
73429036
Reserved counter 58
for cell
BSC6900
V900R016C00
73429037
Reserved counter 59
for cell
BSC6900
V900R016C00
73429038
Reserved counter 60
for cell
BSC6900
V900R016C00
73430886
Reserved counter 61
for cell
BSC6900
V900R017C10
73430887
Reserved counter 62
for cell
BSC6900
V900R017C10
73430888
Reserved counter 63
for cell
BSC6900
V900R017C10
73430889
Reserved counter 64
for cell
BSC6900
V900R017C10
73430890
Reserved counter 65
for cell
BSC6900
V900R017C10
73430891
Reserved counter 66
for cell
BSC6900
V900R017C10
73430892
Reserved counter 67
for cell
BSC6900
V900R017C10
73430893
Reserved counter 68
for cell
BSC6900
V900R017C10
73430894
Reserved counter 69
for cell
BSC6900
V900R017C10
73430895
Reserved counter 70
for cell
BSC6900
V900R017C10
73430896
Reserved counter 71
for cell
BSC6900
V900R017C10

3014
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430897
Reserved counter 72
for cell
BSC6900
V900R017C10
73430898
Reserved counter 73
for cell
BSC6900
V900R017C10
73430899
Reserved counter 74
for cell
BSC6900
V900R017C10
73430900
Reserved counter 75
for cell
BSC6900
V900R017C10
73430901
Reserved counter 76
for cell
BSC6900
V900R017C10
73430902
Reserved counter 77
for cell
BSC6900
V900R017C10
73430903
Reserved counter 78
for cell
BSC6900
V900R017C10
73430904
Reserved counter 79
for cell
BSC6900
V900R017C10
73430905
Reserved counter 80
for cell
BSC6900
V900R017C10
None
Reserved counters for cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423421
VS.Reserve.Counter1
Reserved counter 1 for cell
73423106
VS.Reserve.Counter5
73423305
VS.Reserve.Counter8
73423306
VS.Reserve.Counter9
73423301
73423302
73423422
VS.Reserve.Counter2

3015
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423423
VS.Reserve.Counter3
73423424
VS.Reserve.Counter4
73423425
VS.Reserve.Counter6
73423426
VS.Reserve.Counter7
73423427
73423428
73423429
73423430
73423431
73423432
73423433
73423434
73423435
73423436
73423437
73423438
73423439
73423440
73423441
73423442
73423443
73423444
73423445
73429009
73429010
73429011
73429012
73429013
73429014

3016
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73429015
73429016
73429017
73429018
73429019
73429020
73429021
73429022
73429023
73429024
73429025
73429026
73429027
73429028
73429029
73429030
73429031
73429032
73429033
73429034
73429035
73429036
73429037
73429038
73430886
73430887
73430888
73430889
73430890

3017
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73430891
73430892
73430893
73430894
73430895
73430896
73430897
73430898
73430899
73430900
73430901
73430902
73430903
73430904
73430905
Description
Reserved counters for cell.
Measurement point
Reserved counters for cell.
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

3018
BSC6900 UMTS
1.12.40 RLC Measurement <per Cell>(RLC.Cell)

Overview
Radio Link Control (RLC) measurement in a cell is to measure the number of RLC PDUs sent,
retransmitted and discarded in a cell. These RLC PDUs include traffic RLC PDUs and signaling
RLC PDUs.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204177
VS.RLC.AM.Rtx.T
rf.PDU.1
Number of Downlink
Service PDUs
Retransmitted on
AM RLC that Are
Smaller than 34% of
the Maximum RLC
PDU Size for Cell
Earlier than
BSC6900
V900R011
67204178
VS.RLC.AM.Rtx.T
rf.PDU.2
Number of Downlink
Service PDUs
Retransmitted on
AM RLC that Are
Between 34% and
66% of the
Maximum PDU Size
for Cell
Earlier than
BSC6900
V900R011
67204179
VS.RLC.AM.Rtx.T
rf.PDU.3
Number of Downlink
Service PDUs
Retransmitted on
AM RLC that Are
Greater than 66% of
the Maximum RLC
PDU Size for Cell
Earlier than
BSC6900
V900R011
67204860
VS.RLC.AM.Tx.Hs
dpaTrf.PDU
Number of HSDPA
Downlink Service
PDUs Sent on AM
RLC for Cell
Earlier than
BSC6900
V900R011
67204806
VS.RLC.AM.Tx.R
99Trf.PDU
Number of R99
Downlink Service
PDUs Sent on AM
RLC for Cell
Earlier than
BSC6900
V900R011
67204861
VS.AM.RLC.Tx.Hs
dpaSig.PDU
Number of HSDPA
Downlink Signaling
PDUs Sent on AM
RLC for Cell
Earlier than
BSC6900
V900R011

3019
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204807
VS.AM.RLC.Tx.R
99Sig.PDU
Number of R99
Downlink Signaling
PDUs Sent on AM
RLC for Cell
Earlier than
BSC6900
V900R011
67204808
VS.AM.RLC.Rtx.H
sdpaTrf.PDU
Number of HSDPA
Downlink Service
PDUs Retransmitted
on AM RLC for Cell
Earlier than
BSC6900
V900R011
67204809
VS.AM.RLC.Rtx.R
99Trf.PDU
Number of R99
Downlink Service
PDUs Retransmitted
on AM RLC for Cell
Earlier than
BSC6900
V900R011
67204862
VS.AM.RLC.Rtx.H
sdpaSig.PDU
Number of HSDPA
Downlink Signaling
PDUs Retransmitted
on AM RLC for Cell
Earlier than
BSC6900
V900R011
67204812
VS.AM.RLC.Rtx.R
99Sig.PDU
Number of R99
Downlink Signaling
PDUs Retransmitted
on AM RLC for Cell
Earlier than
BSC6900
V900R011
67204863
VS.RLC.AM.Disc.
HsdpaTrfPDU
Number of HSDPA
Downlink Service
PDUs Discarded on
AM RLC for Cell
Earlier than
BSC6900
V900R011
67204810
VS.RLC.AM.Disc.
R99TrfPDU
Number of R99
Downlink Service
PDUs Discarded on
AM RLC for Cell
Earlier than
BSC6900
V900R011
67204864
VS.RLC.AM.Disc.
HsdpaSig.PDU
Number of HSDPA
Downlink Signaling
PDUs Discarded on
AM RLC for Cell
Earlier than
BSC6900
V900R011
67204811
VS.RLC.AM.Disc.
R99Sig.PDU
Number of R99
Downlink Signaling
PDUs Discarded on
AM RLC for Cell
Earlier than
BSC6900
V900R011
73443314
VS.RLC.SDU.FAC
H.MeanDelay
Average Delay of
Packets Correctly
Sent on the FACH in
a Cell
BSC6900
V900R015C01

3020
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430205
VS.AM.RLC.TX.C
ontrolPDU.Bytes
Traffic of DL
Control PDUs
Transmitted by the
RLC in AM for Cell
BSC6900
V900R017C10
73430206
VS.AM.RLC.RX.C
ontrolPDU.Bytes
Traffic of UL
Control PDUs
Received by the RLC
in AM for Cell
BSC6900
V900R017C10
None
Number of Downlink Service PDUs Retransmitted on AM RLC (L2 Enhancement)

Counters
Counter ID
Counter Name
Counter Description
67204177
VS.RLC.AM.Rtx.Trf.PDU.1
Number of Downlink Service

PDUs Retransmitted on AM
RLC that Are Smaller than
34% of the Maximum RLC
PDU Size for Cell
67204178

RLC that Are Between 34%
and 66% of the Maximum
PDU Size for Cell
67204179

RLC that Are Greater than
66% of the Maximum RLC
PDU Size for Cell
Description
These counters provide the number of downlink PDUs that are retransmitted by the RLC in AM
mode in a HSDPA cell enabled with the enhanced L2 feature. The number of PDUs is provided
on a size basis. In addition, these counters exclude the number of downlink PDUs that are
automatically retransmitted by the RLC.
Issue 03 (2015-06-30)

3021
BSC6900 UMTS
Measurement point
When the AM RLC is configured with the DL L2 enhancement and a PDU is retransmitted, the
RNC measures the corresponding counter based on the comparison of the actual retransmitted
PDU size with the maximum PDU size.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010685
Downlink Enhanced L2
WRFD-010685
WRFD-010685
Number of Downlink Service PDUs Sent on AM RLC

Counters
Counter ID
Counter Name
Counter Description
67204860
VS.RLC.AM.Tx.HsdpaTrf.
PDU
Number of HSDPA
Downlink Service PDUs
Sent on AM RLC for Cell
67204806
VS.RLC.AM.Tx.R99Trf.PD
U

Service PDUs Sent on AM
RLC for Cell
Description
These counters provide the number of downlink service PDUs that are sent on the AM RLC for
different types of service. Retransmitted PDUs are not included.
Number of HSDPA Service PDUs Sent on AM RLC for Cell is measured for the HSDPA serving
cell, and the counter Number of R99 Service PDUs Sent on AM RLC for Cell is measured for
cells in the active set.
Measurement point
The measurement is triggered when a downlink service PDU is sent on the AM RLC.
Issue 03 (2015-06-30)

3022
BSC6900 UMTS
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.RLC.AM.Tx.HsdpaTrf.
PDU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RLC.AM.Tx.R99Trf.PD
U
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Downlink Signaling PDUs Sent on AM RLC

Counters
Counter ID
Counter Name
Counter Description
67204861
VS.AM.RLC.Tx.HsdpaSig.
PDU
Number of HSDPA
Downlink Signaling PDUs
Sent on AM RLC for Cell
67204807
VS.AM.RLC.Tx.R99Sig.PD
U

Signaling PDUs Sent on AM
RLC for Cell
Description
These counters provide the number of downlink signaling PDUs that are sent on the AM RLC.
Retransmitted PDUs are not included.
The counter Number of HSDPA Signaling PDUs Sent on AM RLC for Cell is measured for the
HSDPA serving cell, and the counter Number of R99 Signaling PDUs Sent on AM RLC for Cell
is measured for cells in the active set.
Measurement point
The measurement is triggered when a downlink signaling PDU is sent on the AM RLC.
Issue 03 (2015-06-30)

3023
BSC6900 UMTS
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.AM.RLC.Tx.HsdpaSig.
PDU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.AM.RLC.Tx.R99Sig.PD
U
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Downlink Service PDUs Retransmitted on AM RLC

Counters
Counter ID
Counter Name
Counter Description
67204808
VS.AM.RLC.Rtx.HsdpaTrf.
PDU
Number of HSDPA
Retransmitted on AM RLC
for Cell
67204809
VS.AM.RLC.Rtx.R99Trf.P
DU

Service PDUs Retransmitted
on AM RLC for Cell
Description
These counters provide the number of downlink service PDUs that are retransmitted on the AM
RLC. PDUs that are retransmitted by the RNC actively are not included.
The counter Number of DL HSDPA Service PDUs Retransmitted on AM RLC for Cell is
measured for the HSDPA serving cell, and the counter Number of DL R99 Service PDUs
Retransmitted on AM RLC for Cell is measured for cells in the active set.
Measurement point
The measurement is triggered when a downlink service PDU is retransmitted on the AM RLC.
Issue 03 (2015-06-30)

3024
BSC6900 UMTS
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.AM.RLC.Rtx.HsdpaTrf.
PDU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.AM.RLC.Rtx.R99Trf.P
DU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Downlink Signaling PDUs Retransmitted on AM RLC

Counters
Counter ID
Counter Name
Counter Description
67204862
VS.AM.RLC.Rtx.HsdpaSig.
PDU
Number of HSDPA
for Cell
67204812
VS.AM.RLC.Rtx.R99Sig.P
DU

Signaling PDUs
for Cell
Description
These counters provide the number of downlink signaling PDUs that are retransmitted on the
AM RLC. PDUs that are retransmitted by the RNC actively are not included.
The Number of DL HSDPA Signaling PDUs Retransmitted on AM RLC for Cell is measured
for the HSDPA serving cell, and the Number of DL R99 Signaling PDUs Retransmitted on AM
RLC for Cell is measured for cells in the active set.
Issue 03 (2015-06-30)

3025
BSC6900 UMTS
Measurement point
The measurement is triggered when a downlink signaling PDU is retransmitted on the AM RLC.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.AM.RLC.Rtx.HsdpaSig.
PDU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.AM.RLC.Rtx.R99Sig.P
DU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Downlink Service PDUs Discarded on AM RLC

Counters
Counter ID
Counter Name
Counter Description
67204863
VS.RLC.AM.Disc.HsdpaTrf
PDU
Number of HSDPA
Discarded on AM RLC for
Cell
67204810
VS.RLC.AM.Disc.R99TrfP
DU

Service PDUs Discarded on
AM RLC for Cell
Description
These counters provide the number of downlink service PDUs that are discarded on the AM
RLC.
The counter Number of DL HSDPA Service PDUs Discarded on AM RLC for Cell is measured
for the HSDPA serving cell, and the counter Number of DL R99 Service PDUs Discarded on
AM RLC for Cell is measured for cells in the active set.
Issue 03 (2015-06-30)

3026
BSC6900 UMTS
Measurement point
The measurement is triggered when a downlink service PDU is discarded on the AM RLC.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.RLC.AM.Disc.HsdpaTrf
PDU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RLC.AM.Disc.R99TrfP
DU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Downlink Signaling PDUs Discarded on AM RLC

Counters
Counter ID
Counter Name
Counter Description
67204864
VS.RLC.AM.Disc.HsdpaSig
.PDU
Number of HSDPA
Discarded on AM RLC for
Cell
67204811
VS.RLC.AM.Disc.R99Sig.P
DU

Signaling PDUs Discarded
on AM RLC for Cell
Description
These counters provide the number of downlink signaling PDUs that are discarded on the AM
RLC.
The Number of DL HSDPA Signaling PDUs Discarded on AM RLC for Cell is measured for
the HSDPA serving cell, and the Number of DL R99 Signaling PDUs Discarded on AM RLC
for Cell is measured for cells in the active set.
Issue 03 (2015-06-30)

3027
BSC6900 UMTS
Measurement point
The measurement is triggered when a downlink signaling PDU is discarded on the AM RLC.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.RLC.AM.Disc.HsdpaSig
.PDU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RLC.AM.Disc.R99Sig.P
DU
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Average Delay of Packets Correctly Sent on the FACH in a Cell

Counters
Counter ID
Counter Name
Counter Description
73443314
VS.RLC.SDU.FACH.MeanDelay
Average Delay of Packets

Correctly Sent on the FACH
in a Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73427002
VS.RLC.SDU.FACH.SduNum
Number of Packets Correctly

Sent on the FACH in a Cell
73443313
VS.RLC.SDU.FACH.TotalDelay
Total Delay of Packets

Correctly Sent on the FACH
in a Cell

3028
BSC6900 UMTS
Description
This counter measures the average delay of packets correctly sent on the FACH in a cell.
Measurement point
The time the SRNC receives packets (not including control plane data) from the CN is recorded
as T1, is shown at point A in the following figure. The time the SRNC receives the RLC SDU
acknowledgement (ACK) from the UE after sending the RLC service data unit (SDU) is recorded
as T2, is shown at point B in the following figure. When the SRNC receives the packets and the
RLC SDU ACK from the CN and the UE, respectively, the delay of packets sent on the FACH
(delta T) equals T2 minus T1 if the UE is carried on the FACH.
Figure 1-1345 Procedure for correctly sending packets on the FACH
Formula
VS.RLC.SDU.FACH.MeanDelay = [VS.RLC.SDU.FACH.TotalDelay]/
[VS.RLC.SDU.FACH.SduNum]
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RLC.SDU.FACH.MeanDelay
WRFD-151202
FACH Pool

3029
BSC6900 UMTS
Traffic of UL Control PDUs Received by and DL Control PDUs Transmitted by the

RLC in AM for Cell
Counters
Counter ID
Counter Name
Counter Description
73430205
VS.AM.RLC.TX.ControlPD
U.Bytes
Traffic of DL Control PDUs

Transmitted by the RLC in
AM for Cell
73430206
VS.AM.RLC.RX.ControlPD
U.Bytes
Traffic of UL Control PDUs

Received by the RLC in AM
for Cell
Description
These counters provide the traffic of control PDUs transmitted or received by the RLC in AM
in a cell. These counters comply with 3GPP TS 25.322 (v11.2.0). For details, see section 9.1.2
"Control PDUs" in this TS.
Measurement point
The system measures the traffic of downlink or uplink control PDUs when the RLC layer
transmits a downlink control PDU in AM or receives an uplink control PDU in AM in a
measurement period. For R99 and HSUPA UEs, these counters are measured in cells in the
active set. For HSDPA UEs, these counters are measured in the serving cell. For UEs carried on
common channels, these counters are measured in the bearing cells.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.AM.RLC.TX.ControlPD
U.Bytes
WRFD-010610
HSDPA Introduction
Package
WRFD-010612
HSUPA Introduction
Package
Issue 03 (2015-06-30)

3030
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.AM.RLC.RX.ControlPD
U.Bytes
WRFD-010610
HSDPA Introduction
Package
WRFD-010612
HSUPA Introduction
Package
1.12.41 RRC Connection Release Measurement <per Cell>

(RRC.Rel.Cell)
Overview
When the RNC releases a RRC connection, it sends a RRC CONNECTION RELEASE message
to the UE to release the resources occupied by the UE.
RRC connection release measurement provides the number of RRC connection release messages
with different causes in a specified cell.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189459
RRC.AttConnRelD
CCH.Cong
Number of RRC
Connection Releases
on DCCH due to
Congestion for Cell
Earlier than
BSC6900
V900R011
67189460
RRC.AttConnRelD
CCH.Preempt
Number of RRC
Connection Releases
on DCCH due to
Preemption for Cell
Earlier than
BSC6900
V900R011
67189461
RRC.AttConnRelD
CCH.ReEstRej
Number of RRC
Connection Releases
on DCCH due to Reestablishment Reject
for Cell
Earlier than
BSC6900
V900R011
67189462
RRC.AttConnRelD
CCH.DSCR
Number of RRC
Connection Releases
on DCCH due to
Directed Signaling
Cell
Earlier than
BSC6900
V900R011

3031
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189463
RRC.AttConnRelD
CCH.UsrInact
Number of RRC
Connection Releases
on DCCH due to
User Inactivity for
Cell
Earlier than
BSC6900
V900R011
67189464
RRC.AttConnRelD
CCH.Unspec
Number of RRC
Connection Releases
on DCCH due to
Unspecified Causes
for Cell
Earlier than
BSC6900
V900R011
67189465
RRC.AttConnRelC
CCH.Cong
Number of RRC
Connection Releases
on CCCH due to
Congestion for Cell
Earlier than
BSC6900
V900R011
67189466
RRC.AttConnRelC
CCH.Preempt
Number of RRC
Connection Releases
on CCCH due to
Preemption for Cell
Earlier than
BSC6900
V900R011
67189467
RRC.AttConnRelC
CCH.ReEstRej
Number of RRC
Connection Releases
on CCCH due to Reestablishment Reject
for Cell
Earlier than
BSC6900
V900R011
67189468
RRC.AttConnRelC
CCH.DSCR
Number of RRC
Connection Releases
on CCCH due to
Directed Signaling
Cell
Earlier than
BSC6900
V900R011
67189469
RRC.AttConnRelD
CCH.Norm
Number of RRC
Connection Releases
on DCCH due to
Normal Event for
Cell
Earlier than
BSC6900
V900R011
67189470
RRC.AttConnRelC
CCH.Norm
Number of RRC
Connection Releases
on CCCH due to
Normal Event for
Cell
Earlier than
BSC6900
V900R011

3032
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67189471
RRC.AttConnRelC
CCH.UsrInact
Number of RRC
Connection Releases
on CCCH due to
User Inactivity for
Cell
Earlier than
BSC6900
V900R011
67189472
RRC.AttConnRelC
CCH.Unspec
Number of RRC
Connection Releases
on CCCH due to
Unspecified Causes
for Cell
Earlier than
BSC6900
V900R011
67180387
VS.RRC.ConnRel.
CellUpd
Number of RRC
Connection Releases
due to Cell Update
Failure in the Case of
RL Failure for Cell
Earlier than
BSC6900
V900R011
73391137
VS.RRC.SigConnR
elInd.UEPSDataEnd
Number of RRCs
Release Due to
Receiving
SIGNALLING
CONNECTION
RELEASE
INDICATION
message with cause
of "UE Requested PS
Data session end" for
cell
BSC6900
V900R012
73429232
VS.RRCSig.Abnor
mRel.Preempted
Number of Times
RRC Connections
Are Abnormally
Released for UEs
with No TRBs Due to
Preemption for Cell
BSC6900
V900R017C00
73430563
VS.RRC.ConnRel.
DistLimit
Number of RRC
Connection Releases
Caused by Distancebased Access
Control for Cell
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

3033
BSC6900 UMTS
Counters Related to the Number of RRC Connection Releases on DCCH due to

Different Causes
Counters
Counter ID
Counter Name
Counter Description
67189469
RRC.AttConnRelDCCH.No
rm

Releases on DCCH due to
Normal Event for Cell
67189459
RRC.AttConnRelDCCH.Co
ng

Congestion for Cell
67189460
RRC.AttConnRelDCCH.Pre
empt

Preemption for Cell
67189461
RRC.AttConnRelDCCH.ReEstRej

Re-establishment Reject for
Cell
67189462
RRC.AttConnRelDCCH.DS
CR

Directed Signaling
Connection Reestablishment for Cell
67189463
RRC.AttConnRelDCCH.UsrInact

User Inactivity for Cell
67189464
RRC.AttConnRelDCCH.Un
spec

Unspecified Causes for Cell
Description
These counters provide the number of RRC CONNECTION RELEASE messages with different
causes on DCCH sent by the RNC to the UE in the best cell.The preceding counters comply
with section "8.1.4 RRC connection release" in 3GPP TS 25.331 (v10.13.0).
Measurement point
CONNECTION RELEASE message with a certain cause to the UE to release a RRC connection,
the corresponding counter is measured in the best cell that the UE camps on. For details on the
different causes, see section 10.3.3.32 in 3GPP TS 25.331.
Issue 03 (2015-06-30)

3034
BSC6900 UMTS
Figure 1-1346 RRC connection release procedure on the DCCH
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
RRC.AttConnRelDCCH.No
rm
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelDCCH.Co
ng
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelDCCH.Pre
empt
WRFD-010505
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3035
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
RRC.AttConnRelDCCH.ReEstRej
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelDCCH.DS
CR
WRFD-021400

WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelDCCH.UsrInact
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelDCCH.Un
spec
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counters Related to the Number of RRC Connection Releases on CCCH due to

Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189470
RRC.AttConnRelCCCH.No
rm

Releases on CCCH due to
Normal Event for Cell
67189465
RRC.AttConnRelCCCH.Co
ng

Congestion for Cell
67189466
RRC.AttConnRelCCCH.Pre
empt

Preemption for Cell
67189467
RRC.AttConnRelCCCH.ReEstRej

Re-establishment Reject for
Cell

3036
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67189468
RRC.AttConnRelCCCH.DS
CR

Directed Signaling
Connection Reestablishment for Cell
67189471
RRC.AttConnRelCCCH.UsrInact

User Inactivity for Cell
67189472
RRC.AttConnRelCCCH.Un
spec

Unspecified Causes for Cell
Description
These counters provide the number of RRC CONNECTION RELEASE messages with different
causes on CCCH sent by the RNC to the UE.The preceding counters comply with section "8.1.4
RRC connection release" in 3GPP TS 25.331 (v10.13.0).
Measurement point
CONNECTION RELEASE message with a certain cause to the UE to release a RRC connection,
the corresponding counter is measured in the cell that the UE camps on. For details on the
different causes, see section 10.3.3.32 in 3GPP TS 25.331.
Figure 1-1347 RRC connection release procedure on the CCCH
Issue 03 (2015-06-30)

3037
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RRC.AttConnRelCCCH.No
rm
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelCCCH.Co
ng
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelCCCH.Pre
empt
WRFD-010505
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelCCCH.ReEstRej
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelCCCH.DS
CR
WRFD-021400

WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)
RRC.AttConnRelCCCH.UsrInact
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnRelCCCH.Un
spec
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3038
BSC6900 UMTS
Number of RRC Connection Releases due to Cell Update Failure in the Case of RL
Failure
Counters
Counter ID
Counter Name
Counter Description
67180387
VS.RRC.ConnRel.CellUpd

Releases due to Cell Update
Failure in the Case of RL
Failure for Cell
Description
This counter provides the number of RRC connection releases due to cell update failure in the
case of radio link failure.This counter complies with section "8.1.4 RRC connection release" in
3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC fails in the cell
update due to radio link failure, it sends the UE a RRC CONNECTION RELEASE message. In
this case, this counter is measured in the target cell during cell update.
Figure 1-1348 RRC connection release caused by cell update failure
Issue 03 (2015-06-30)

3039
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.ConnRel.CellUpd
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010801
Number of RRCs Released due to PS Data session end

Counters
Counter ID
Counter Name
Counter Description
73391137
VS.RRC.SigConnRelInd.U
EPSDataEnd
Number of RRCs Release

Due to Receiving
SIGNALLING
CONNECTION RELEASE
INDICATION message with
cause of "UE Requested PS
Data session end" for cell
Description
The measurement item takes statistics of the number of RRCs Released due to Receiving
SIGNALLING CONNECTION RELEASE INDICATION message with cause of "UE
Requested PS Data session end" in the best cell which the UE camps on.This counter complies
with section "8.1.4 RRC connection release" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure.After the UE checks that no PS
data is transmitted, it sends to the RNC the SIGNALLING CONNECTION RELEASE
INDICATION message with the cause value "UE Requested PS Data session end". This counter
measures the numbers of RRCs Release on this situation.
Issue 03 (2015-06-30)

3040
BSC6900 UMTS
Figure 1-1349 UL SIG connection release procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.SigConnRelInd.U
EPSDataEnd
WRFD-020500

3041
BSC6900 UMTS
Number of Times RRC Connections Are Abnormally Released for UEs with No
TRBs Due to Preemption for Cell
Counters
Counter ID
Counter Name
Counter Description
73429232
VS.RRCSig.AbnormRel.Pre
empted
Number of Times RRC

Connections Are
UEs with No TRBs Due to
Preemption for Cell
Description
This counter provides the number of times RRC connections are abnormally released due to
preemption (indicated by the cause value "pre-emptive release" in the RRC CONNECTION
RELEASE message) in the best cell. For details about this cause value, see section 10.3.3.32 in
3GPP TS 25.331.
Measurement point
The measurement is triggered at point A in figure 1 when the RNC sends an RRC
CONNECTION RELEASE message with the cause value "pre-emptive release" to the UE. This
counter is measured in the best cell for the UE.
Issue 03 (2015-06-30)

3042
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRCSig.AbnormRel.Pre
empted
WRFD-010505
Number of RRC Connection Releases Caused by Distance-based Access Control

for Cell
Counters
Counter ID
Counter Name
Counter Description
73430563
VS.RRC.ConnRel.DistLimit

Releases Caused by
Distance-based Access
Control for Cell
Description
This counter provides the number of RRC connection releases caused by distance-based access
control in the best cell. This counter complies with 3GPP TS 25.331 (V9.3.0). For details about
this counter, see section 8.1.4 "RRC connection release" in this TS.
Measurement point
The measurement is triggered at point A figure 1. After receiving a service request from a UE
in RRC connected mode, the RNC determines that the distance-based access control function is
enabled and therefore sends an RRC CONNECTION RELEASE message to the UE. This
counter is measured in the best cell.
Issue 03 (2015-06-30)

3043
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.ConnRel.DistLimit
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.42 RRC Connection Setup Measurement <per Cell>

(RRC.Setup.Cell)
Overview
When an UE needs to access the network, setting up the RRC connection is the first step. From
the cell where the UE is located, the UE sends a RRC CONNECTION REQUEST message to
request network access.
Issue 03 (2015-06-30)

3044
BSC6900 UMTS
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 counter of RRC connection setup attempts and rejects does not include service-based
redirections, inter-RAT and inter-frequency distance-based redirections, weakcoverage-based
redirections, macro & micro joint inter-frequency redirections and the number of RRC
connection requests discarded during flow control.
In addition, the number of RRC connection setup attempts do not include the attempts in the
overlapping of the RRC connection setup procedure and cell update procedure.
During the resource admission and radio link setup process, if DRD is configured when resource
admission and radio link setup fail and the configured DRD succeeds, the measurement is
triggered in the target cell for the UE. If the configured DRD fails, the measurement is triggered
in the source cell for the UE.
Note that the measurement is not triggered for RRC CONNECTION REQUEST messages
retransmitted by the UE.
The following figure shows the measurement points of the counters.
Issue 03 (2015-06-30)

3045
BSC6900 UMTS
Issue 03 (2015-06-30)

3046
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.RRC.AttConnEstab.Msg.Conv

3047
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
RRC.AttConnEstab.OrgConvCall,
RRC.AttConnEstab.OrgStrCall,
RRC.AttConnEstab.OrgInterCall,
RRC.AttConnEstab.OrgBkgCall,
RRC.AttConnEstab.TmConvCall,
RRC.AttConnEstab.TmStrCall,
RRC.AttConnEstab.TmInterCall,
RRC.AttConnEstab.TmBkgCall,
RRC.AttConnEstab.OrgSubCall,
RRC.AttConnEstab.EmgCall,
RRC.AttConnEstab.IRATCelRes,
RRC.AttConnEstab.IRATCCO,
RRC.AttConnEstab.Reg,
RRC.AttConnEstab.Detach,
RRC.AttConnEstab.OrgHhPrSig,
RRC.AttConnEstab.OrgLwPrSig,
RRC.AttConnEstab.CallReEst,
RRC.AttConnEstab.TmHhPrSig,
RRC.AttConnEstab.TmLwPrSig,
RRC.AttConnEstab.Unknown,
VS.RRC.AttConnEstab.CellDCH,
VS.RRC.AttConnEstab.CellFACH,
VS.RRC.AttConnEstab.Sum,
RRC.AttConnEstab.MBMSRep,
RRC.AttConnEstab.MBMSPtp,
VS.RRC.AttConnEstab.EDCH,
VS.RRC.AttConnEstab.HSDSCH,
VS.RRC.AttConnEstab.Msg,
RRC.AttConnEstab.Rep.OrgConvCall,
RRC.AttConnEstab.Rep.OrgStrCall,
RRC.AttConnEstab.Rep.OrgInterCall,
RRC.AttConnEstab.Rep.OrgBkgCall,
RRC.AttConnEstab.Rep.TmConvCall,
RRC.AttConnEstab.Rep.TmStrCall,
RRC.AttConnEstab.Rep.TmInterCall,
RRC.AttConnEstab.Rep.TmBkgCall,
RRC.AttConnEstab.Rep.OrgSubCall,
RRC.AttConnEstab.Rep.EmgCall,
RRC.AttConnEstab.Rep.IRATCelRes,
RRC.AttConnEstab.Rep.IRATCCO,
RRC.AttConnEstab.Rep.Reg,
RRC.AttConnEstab.Rep.Detach,
RRC.AttConnEstab.Rep.OrgHhPrSig,
RRC.AttConnEstab.Rep.OrgLwPrSig,
RRC.AttConnEstab.Rep.CallReEst,
RRC.AttConnEstab.Rep.TmHhPrSig,
RRC.AttConnEstab.Rep.TmLwPrSig,
RRC.AttConnEstab.Rep.Unknown,
VS.RRC.AttConnEstab.PSDomain,
3048
BSC6900 UMTS
Measurement points
Description
VS.RRC.AttConnEstab.CSDomain,
VS.RRC.AttConnEstab.WithSI.CsDomain,
VS.RRC.AttConnEstab.WithSI.PsDomain,
RRC.AttConnEstab.Conv.Platinum,
RRC.AttConnEstab.Platinum,
VS.RRC.AttConnEstab.CellUpd.DSCR.CS,
VS.RRC.AttConnEstab.CellUpd.DSCR.PS,
VS.RRC.AttConnEstab.CellUpd.DSCR.Oth
er,
VS.RRC.AttConnEstab.CellUpd.DSCR.Ser
vice
Issue 03 (2015-06-30)
VS.EcNo.Mean.TP0, VS.EcNo.Cum.TP0,
VS.TP.UE.0, VS.EcNo.Mean.TP1,
VS.EcNo.Cum.TP1, VS.TP.UE.1,
VS.EcNo.Mean.TP6.9,
VS.EcNo.Cum.TP6.9, VS.TP.UE.6.9,
VS.EcNo.Mean.TP10.15,
VS.EcNo.Mean.TP.More55,
VS.EcNo.Cum.TP.More55,
VS.TP.UE.More55,
VS.EcNo.Cum.TP10.15, VS.TP.UE.10.15
VS.RRC.SetupConnEstab

3049
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
RRC.SuccConnEstab.sum,
VS.RRC.Estab.DRDOut.Succ,
VS.RRC.Estab.DRDIn,
VS.RRC.ConnEstabTimeMax.CellDCH,
RRC.SuccConnEstab.OrgConvCall,
RRC.SuccConnEstab.OrgStrCall,
RRC.SuccConnEstab.OrgInterCall,
RRC.SuccConnEstab.OrgBkgCall,
RRC.SuccConnEstab.OrgSubCall,
RRC.SuccConnEstab.TmConvCall,
RRC.SuccConnEstab.TmStrCall,
RRC.SuccConnEstab.TmItrCall,
RRC.SuccConnEstab.TmBkgCall,
RRC.SuccConnEstab.IRATCelRes,
RRC.SuccConnEstab.IRATCCO,
RRC.SuccConnEstab.Reg,
RRC.SuccConnEstab.OrgHhPrSig,
RRC.SuccConnEstab.OrgLwPrSig,
RRC.SuccConnEstab.CallReEst,
RRC.SuccConnEstab.TmHhPrSig,
RRC.SuccConnEstab.TmLwPrSig,
RRC.SuccConnEstab.Unkown,
RRC.SuccConnEstab.EmgCall,
RRC.SuccConnEstab.MBMSRep,
RRC.SuccConnEstab.MBMSPtp,
VS.RRC.SuccConnEstab.CellDCH,
VS.RRC.SuccConnEstab.CellFACH,
VS.RRC.SuccConnEstab.EDCH,
VS.RRC.SuccConnEstab.HSDSCH,
VS.RRC.SuccConnEstab.First,
VS.RRC.SuccConnEstab.Second,
VS.RRC.SuccConnEstab.Third,
VS.RRC.ConnEstabTimeMax.CellFACH,
VS.RRC.SuccConnEstab.WithSI.CsDomain,
VS.RRC.SuccConnEstab.WithSI.PsDomain, RRC.SuccConnEstab.Conv.Platinum,
RRC.SuccConnEstab.Platinum,
RRC.SuccConnEstab.Detach
VS.RRC.Estab.DRDOut.Att

3050
BSC6900 UMTS
Measurement points
Description
VS.RRC.FC.Num.MPU.OverLoad,
VS.RRC.FC.Num.CallShock,
VS.RRC.CONV.FC.Num.CPU.OverLoad,
VS.RRC.CONV.FC.Num.RRCQueue,
VS.RRC.CONV.FC.Num.MPU.OverLoad,
VS.RRC.CONV.FC.Num.CallShock,
VS.RRC.FC.Num.RanFC.Ph2,
VS.RRC.CONV.FC.Num.RanFC.Ph2,
VS.RRC.FC.Num.CAPS,
VS.RRC.CONV.FC.Num.CAPS, and other
counters, refer to RRC.SetupFail.Cell
L~M
VS.RRC.CONV.FC.Num.INT.OverLoad,
VS.RRC.FC.Num.INT.OverLoad,
VS.RRC.FC.Num.FACH.Cong,
VS.RRC.FC.Num.MPU.OverLoad,
VS.RRC.FC.Num.CallShock,
VS.RRC.CONV.FC.Num.CPU.OverLoad,
VS.RRC.CONV.FC.Num.RRCQueue,
VS.RRC.CONV.FC.Num.MPU.OverLoad,
VS.RRC.CONV.FC.Num.CallShock,
VS.RRC.FC.Num.CAPS,
VS.RRC.CONV.FC.Num.CAPS, and other
counters, refer to RRC.SetupFail.Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189400
VS.RRC.Estab.DR
DOut.Att
Number of RRC
Connection Setup
Attempts with DRD
out for Cell
Earlier than
BSC6900
V900R011
67189401
VS.RRC.Estab.DR
DOut.Succ
Number of
Successful RRC
Connection Setups
with DRD out for
Cell
Earlier than
BSC6900
V900R011

3051
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192607
VS.RRC.Estab.DR
DIn
Number of RRC
Connection Setup
Attempts with DRD
in for Cell
Earlier than
BSC6900
V900R011
67179302
VS.RRC.ConnEsta
bTimeMax.CellDC
H
Maximum Duration
of RRC Connection
Setup for Cell (UE
Target State on
CELL_DCH)
Earlier than
BSC6900
V900R011
67199510
VS.RRC.ConnEsta
bTimeMean.CellD
CH
Average Duration of
RRC Connection
Setup for Cell (UE
Target State on
CELL_DCH)
Earlier than
BSC6900
V900R011
67179329
RRC.AttConnEsta
b.OrgConvCall
Number of RRC
Connection Requests
for Cell (Originating
Earlier than
BSC6900
V900R011
67179330
RRC.AttConnEsta
b.OrgStrCall
Number of RRC
Connection Requests
Streaming Call)
Earlier than
BSC6900
V900R011
67179331
RRC.AttConnEsta
b.OrgInterCall
Number of RRC
Connection Requests
Interactive Call)
Earlier than
BSC6900
V900R011
67179332
RRC.AttConnEsta
b.OrgBkgCall
Number of RRC
Connection Requests
Background Call)
Earlier than
BSC6900
V900R011
67179334
RRC.AttConnEsta
b.TmConvCall
Number of RRC
Connection Requests
for Cell (Terminating
Earlier than
BSC6900
V900R011
67179335
RRC.AttConnEsta
b.TmStrCall
Number of RRC
Connection Requests
Streaming Call)
Earlier than
BSC6900
V900R011
67179336
RRC.AttConnEsta
b.TmInterCall
Number of RRC
Connection Requests
Interactive Call)
Earlier than
BSC6900
V900R011

3052
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179337
RRC.AttConnEsta
b.TmBkgCall
Number of RRC
Connection Requests
Background Call)
Earlier than
BSC6900
V900R011
67179457
RRC.SuccConnEst
ab.OrgConvCall
Number of
Successful RRC
Connection Setups
Earlier than
BSC6900
V900R011
67179458
RRC.SuccConnEst
ab.OrgStrCall
Number of
Successful RRC
Connection Setups
Streaming Call)
Earlier than
BSC6900
V900R011
67179459
RRC.SuccConnEst
ab.OrgInterCall
Number of
Successful RRC
Connection Setups
Interactive Call)
Earlier than
BSC6900
V900R011
67179460
RRC.SuccConnEst
ab.OrgBkgCall
Number of
Successful RRC
Connection Setups
Background Call)
Earlier than
BSC6900
V900R011
67179461
RRC.SuccConnEst
ab.OrgSubCall
Number of
Successful RRC
Connection Setups
Subscribed traffic
Call)
Earlier than
BSC6900
V900R011
67179462
RRC.SuccConnEst
ab.TmConvCall
Number of
Successful RRC
Connection Setups
Earlier than
BSC6900
V900R011
67179463
RRC.SuccConnEst
ab.TmStrCall
Number of
Successful RRC
Connection Setups
Streaming Call)
Earlier than
BSC6900
V900R011

3053
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179464
RRC.SuccConnEst
ab.TmItrCall
Number of
Successful RRC
Connection Setups
Interactive Call)
Earlier than
BSC6900
V900R011
67179465
RRC.SuccConnEst
ab.TmBkgCall
Number of
Successful RRC
Connection Setups
Background Call)
Earlier than
BSC6900
V900R011
67179298
VS.RRC.SetupCon
nEstab
Number of RRC
Connection Setup
Messages from RNC
to UE for Cell
Earlier than
BSC6900
V900R011
67179299
RRC.SuccConnEst
ab.sum
Number of
Successful RRC
Connection Setups
for Cell
Earlier than
BSC6900
V900R011
67179333
RRC.AttConnEsta
b.OrgSubCall
Number of RRC
Connection Requests
Subscribed Traffic
Call)
Earlier than
BSC6900
V900R011
67179338
RRC.AttConnEsta
b.EmgCall
Number of RRC
Connection Requests
for Cell (Emergency
Call)
Earlier than
BSC6900
V900R011
67179339
RRC.AttConnEsta
b.IRATCelRes
Number of RRC
Connection Requests
for Cell (Inter-RAT
Cell Re-Selection)
Earlier than
BSC6900
V900R011
67179340
RRC.AttConnEsta
b.IRATCCO
Number of RRC
Connection Requests
for Cell (Inter-RAT
Cell Change Order)
Earlier than
BSC6900
V900R011
67179341
RRC.AttConnEsta
b.Reg
Number of RRC
Connection Requests
for Cell
(Registration)
Earlier than
BSC6900
V900R011
67179342
RRC.AttConnEsta
b.Detach
Number of RRC
Connection Requests
for Cell (Detach)
Earlier than
BSC6900
V900R011

3054
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179343
RRC.AttConnEsta
b.OrgHhPrSig
Number of RRC
Connection Requests
High Priority
Signaling)
Earlier than
BSC6900
V900R011
67179344
RRC.AttConnEsta
b.OrgLwPrSig
Number of RRC
Connection Requests
Low Priority
Signaling)
Earlier than
BSC6900
V900R011
67179345
RRC.AttConnEsta
b.CallReEst
Number of RRC
Connection Requests
for Cell (Call ReEstablishment)
Earlier than
BSC6900
V900R011
67179346
RRC.AttConnEsta
b.TmHhPrSig
Number of RRC
Connection Requests
High Priority
Signaling)
Earlier than
BSC6900
V900R011
67179347
RRC.AttConnEsta
b.TmLwPrSig
Number of RRC
Connection Requests
Low Priority
Signaling)
Earlier than
BSC6900
V900R011
67179348
RRC.AttConnEsta
b.Unknown
Number of RRC
Connection Requests
for Cell
(Terminating-Cause
Unknown)
Earlier than
BSC6900
V900R011
67179467
RRC.SuccConnEst
ab.IRATCelRes
Number of
Successful RRC
Connection Setups
for Cell (Inter-RAT
Cell Re-Selection)
Earlier than
BSC6900
V900R011
67179468
RRC.SuccConnEst
ab.IRATCCO
Number of
Successful RRC
Connection Setups
for Cell (Inter-RAT
Cell Change Order)
Earlier than
BSC6900
V900R011

3055
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179469
RRC.SuccConnEst
ab.Reg
Number of
Successful RRC
Connection Setups
for Cell
(Registration)
Earlier than
BSC6900
V900R011
67179470
RRC.SuccConnEst
ab.Detach
Number of
Successful RRC
Connection Setups
for Cell (Detach)
Earlier than
BSC6900
V900R011
67179471
RRC.SuccConnEst
ab.OrgHhPrSig
Number of
Successful RRC
Connection Setups
High Priority
Signaling)
Earlier than
BSC6900
V900R011
67179472
RRC.SuccConnEst
ab.OrgLwPrSig
Number of
Successful RRC
Connection Setups
Low Priority
Signaling)
Earlier than
BSC6900
V900R011
67179473
RRC.SuccConnEst
ab.CallReEst
Number of
Successful RRC
Connection Setups
for Cell (Call ReEstablishment)
Earlier than
BSC6900
V900R011
67179474
RRC.SuccConnEst
ab.TmHhPrSig
Number of
Successful RRC
Connection Setups
High Priority
Signaling)
Earlier than
BSC6900
V900R011
67179475
RRC.SuccConnEst
ab.TmLwPrSig
Number of
Successful RRC
Connection Setups
Low Priority
Signaling)
Earlier than
BSC6900
V900R011

3056
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67179476
RRC.SuccConnEst
ab.Unkown
Number of
Successful RRC
Connection Setups
for Cell
(Terminating-Cause
Unknown)
Earlier than
BSC6900
V900R011
67179633
VS.RRC.AttConnE
stab.CellDCH
Number of RRC
Connection Requests
for Cell (UE Target
State of
CELL_DCH)
Earlier than
BSC6900
V900R011
67179634
VS.RRC.SuccConn
Estab.CellDCH
Number of
Successful RRC
Connection Setups
for Cell (UE Target
State of
CELL_DCH)
Earlier than
BSC6900
V900R011
67179649
VS.RRC.AttConnE
stab.CellFACH
Number of RRC
Connection Requests
for Cell (UE Target
State of
CELL_FACH)
Earlier than
BSC6900
V900R011
67179650
VS.RRC.SuccConn
Estab.CellFACH
Number of
Successful RRC
Connection Setups
for Cell (UE Target
State of
CELL_FACH)
Earlier than
BSC6900
V900R011
67179466
RRC.SuccConnEst
ab.EmgCall
Number of
Successful RRC
Connection Setups
for Cell (Emergency
Call)
Earlier than
BSC6900
V900R011
67190586
VS.RRC.AttConnE
stab.Sum
Number of Processed
RRC Connection
Requests for Cell
Earlier than
BSC6900
V900R011
67190587
VS.RRC.SuccConn
Estab.First
Number of
Successful RRC
Connection Setups
with One RRC
Connection Request
Message from UE for
Cell
Earlier than
BSC6900
V900R011

3057
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190588
VS.RRC.SuccConn
Estab.Second
Number of
Successful RRC
Connection Setups
with Two RRC
Connection Request
Messages from UE
for Cell
Earlier than
BSC6900
V900R011
67190589
VS.RRC.SuccConn
Estab.Third
Number of
Successful RRC
Connection Setups
with Three RRC
Connection Request
Messages from UE
for Cell
Earlier than
BSC6900
V900R011
67195590
VS.RRC.AutoDsac.
Num
Number of
Automatic DSACs
Triggered by
Congestion on Iu
Interface for Cell
Earlier than
BSC6900
V900R011
67195964
RRC.AttConnEsta
b.MBMSRep
Number of RRC
Connection Requests
for Cell (MBMS
Reception)
Earlier than
BSC6900
V900R011
67195965
RRC.AttConnEsta
b.MBMSPtp
Number of RRC
Connection Requests
for Cell (MBMS PTP
RB Request)
Earlier than
BSC6900
V900R011
67195966
RRC.SuccConnEst
ab.MBMSRep
Number of
Successful RRC
Connection Setups
for Cell (MBMS
Reception)
Earlier than
BSC6900
V900R011
67195967
RRC.SuccConnEst
ab.MBMSPtp
Number of
Successful RRC
Connection Setups
for Cell (MBMS PTP
RB Request)
Earlier than
BSC6900
V900R011
67196198
VS.RRC.AttConnE
stab.EDCH
Number of RRC
Connection
Attempts for UL
Carried on E_DCH
for Cell
Earlier than
BSC6900
V900R011

3058
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196199
VS.RRC.AttConnE
stab.HSDSCH
Number of RRC
Connection
Attempts for DL
Carried on
HS_DSCH for Cell
Earlier than
BSC6900
V900R011
67196200
VS.RRC.SuccConn
Estab.EDCH
Number of
Successful RRC
Connection Setups
on E_DCH)
Earlier than
BSC6900
V900R011
67196201
VS.RRC.SuccConn
Estab.HSDSCH
Number of
Successful RRC
Connection Setups
on HS_DSCH)
Earlier than
BSC6900
V900R011
73403798
VS.RRC.AttConnE
stab.Msg
Number of RRC
Connection Requests
sent by the UE for
cell
BSC6900
V900R012
73410489
VS.CellFACHUEs.
PTT
Number of PTT UEs

in Cell with RRC
Connection State of
CELL_FACH
BSC6900
V900R012
73410490
VS.CellDCHUEs.P
TT
Number of PTT UEs

in Cell with RRC
Connection State of
CELL_DCH
BSC6900
V900R012
73421887
VS.RRC.ConnEsta
bTimeMax.CellFACH
Maximum Duration
of RRC
Establishment
Process on FACH for
Cell
Earlier than
BSC6900
V900R011
73439969
VS.RRC.ConnEsta
bTimeMean.CellFACH
Mean Duration of
RRC Establishment
Process on FACH for
Cell
Earlier than
BSC6900
V900R011
73410505
VS.CellPCHUEs.P
TT
Number of PTT UEs

with RRC
Connection State of
CELL_PCH for Cell
BSC6900
V900R012

3059
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423388
RRC.AttConnEsta
b.Rep.OrgConvCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Originating
BSC6900
V900R013
73423389
RRC.AttConnEsta
b.Rep.OrgStrCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Originating
Streaming Call)
BSC6900
V900R013
73423390
RRC.AttConnEsta
b.Rep.OrgInterCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Originating
Interactive Call)
BSC6900
V900R013
73423391
RRC.AttConnEsta
b.Rep.OrgBkgCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Originating
Background Call)
BSC6900
V900R013
73423392
RRC.AttConnEsta
b.Rep.TmConvCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Terminating
BSC6900
V900R013
73423393
RRC.AttConnEsta
b.Rep.TmStrCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Terminating
Streaming Call)
BSC6900
V900R013
73423394
RRC.AttConnEsta
b.Rep.TmInterCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Terminating
Interactive Call)
BSC6900
V900R013

3060
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423395
RRC.AttConnEsta
b.Rep.TmBkgCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Terminating
Background Call)
BSC6900
V900R013
73423396
RRC.AttConnEsta
b.Rep.OrgSubCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Originating
Subscribed Traffic
Call)
BSC6900
V900R013
73423397
RRC.AttConnEsta
b.Rep.EmgCall
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Emergency Call)
BSC6900
V900R013
73423398
RRC.AttConnEsta
b.Rep.IRATCelRes
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Inter-RAT Cell Reselection)
BSC6900
V900R013
73423399
RRC.AttConnEsta
b.Rep.IRATCCO
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Inter-RAT Cell
Change Order)
BSC6900
V900R013
73423400
RRC.AttConnEsta
b.Rep.Reg
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Registration)
BSC6900
V900R013
73423401
RRC.AttConnEsta
b.Rep.Detach
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Detach)
BSC6900
V900R013

3061
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423402
RRC.AttConnEsta
b.Rep.OrgHhPrSig
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Originating High
BSC6900
V900R013
73423403
RRC.AttConnEsta
b.Rep.OrgLwPrSig
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Originating Low
BSC6900
V900R013
73423404
RRC.AttConnEsta
b.Rep.CallReEst
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Call Reestablishment)
BSC6900
V900R013
73423405
RRC.AttConnEsta
b.Rep.TmHhPrSig
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Terminating High
BSC6900
V900R013
73423406
RRC.AttConnEsta
b.Rep.TmLwPrSig
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Terminating Low
BSC6900
V900R013
73423407
RRC.AttConnEsta
b.Rep.Unknown
Number of
Retransmitted RRC
Connection Setup
Requests for Cell
(Terminating-Cause
Unknown)
BSC6900
V900R013
73441146
VS.EcNo.Mean.TP
0
Average Ec/N0
During RRC
Connection
Establishment
Requests with
0
BSC6900
V900R013

3062
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423486
VS.TP.UE.0
Number of RRC
Connection
Establishment
Requests with
0
BSC6900
V900R013
73441147
VS.EcNo.Mean.TP
1
Average Ec/N0
During RRC
Connection
Establishment
Requests with
1
BSC6900
V900R013
73423488
VS.TP.UE.1
Number of RRC
Connection
Establishment
Requests with
1
BSC6900
V900R013
73441148
VS.EcNo.Mean.TP
2
Average Ec/N0
During RRC
Connection
Establishment
Requests with
2
BSC6900
V900R013
73423490
VS.TP.UE.2
Number of RRC
Connection
Establishment
Requests with
2
BSC6900
V900R013
73441149
VS.EcNo.Mean.TP
3
Average Ec/N0
During RRC
Connection
Establishment
Requests with
3
BSC6900
V900R013

3063
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423492
VS.TP.UE.3
Number of RRC
Connection
Establishment
Requests with
3
BSC6900
V900R013
73441150
VS.EcNo.Mean.TP
4
Average Ec/N0
During RRC
Connection
Establishment
Requests with
4
BSC6900
V900R013
73423494
VS.TP.UE.4
Number of RRC
Connection
Establishment
Requests with
4
BSC6900
V900R013
73441151
VS.EcNo.Mean.TP
5
Average Ec/N0
During RRC
Connection
Establishment
Requests with
5
BSC6900
V900R013
73423496
VS.TP.UE.5
Number of RRC
Connection
Establishment
Requests with
5
BSC6900
V900R013
73441152
VS.EcNo.Mean.TP
6.9
Average Ec/N0
During RRC
Connection
Establishment
Requests with
6~9
BSC6900
V900R013

3064
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423498
VS.TP.UE.6.9
Number of RRC
Connection
Establishment
Requests with
6~9
BSC6900
V900R013
73441153
VS.EcNo.Mean.TP
10.15
Average Ec/N0
During RRC
Connection
Establishment
Requests with
10~15
BSC6900
V900R013
73441154
VS.EcNo.Mean.TP
16.25
Average Ec/N0
During RRC
Connection
Establishment
Requests with
16~25
BSC6900
V900R013
73423502
VS.TP.UE.16.25
Number of RRC
Connection
Establishment
Requests with
16~25
BSC6900
V900R013
73441155
VS.EcNo.Mean.TP
26.35
Average Ec/N0
During RRC
Connection
Establishment
Requests with
26~35
BSC6900
V900R013
73423504
VS.TP.UE.26.35
Number of RRC
Connection
Establishment
Requests with
26~35
BSC6900
V900R013

3065
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441156
VS.EcNo.Mean.TP
36.55
Average Ec/N0
During RRC
Connection
Establishment
Requests with
36~55
BSC6900
V900R013
73423506
VS.TP.UE.36.55
Number of RRC
Connection
Establishment
Requests with
36~55
BSC6900
V900R013
73441157
VS.EcNo.Mean.TP.
More55
Average Ec/N0
During RRC
Connection
Establishment
Requests with
Propagation Delay
Greater than 55
BSC6900
V900R013
73423508
VS.TP.UE.More55
Number of RRC
Connection
Establishment
Requests with
Propagation Delay
Greater than 55
BSC6900
V900R013
73423510
VS.TP.UE.10.15
Number of RRC
Connection
Establishment
Requests with
10~15
BSC6900
V900R013
73424223
VS.RRC.AttConnE
stab.Msg.Conv
Number of Received
RRC
CONNECTION
REQUESTS for CS
Services in a Cell
BSC6900
V900R014
73424224
VS.RRC.FC.Num.
CPU.OverLoad
Number of RRC
CONNECTION
REQUESTS Under
Flow Control
Triggered by High
CPU Usage for Cell
BSC6900
V900R014

3066
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424225
VS.RRC.FC.Num.
RRCQueue
Number of RRC
CONNECTION
REQUESTS Under
Flow Control
Triggered by RRC
Queue Overflow for
Cell
BSC6900
V900R014
73424226
VS.RRC.FC.Num.
MPU.OverLoad
Number of RRC
CONNECTION
REQUESTS Under
Flow Control
Triggered by MPU
Overload for Cell
BSC6900
V900R014
73424227
VS.RRC.FC.Num.
CallShock
Number of RRC
CONNECTION
REQUESTS Under
Flow Control
Triggered by Burst
Traffic for Cell
BSC6900
V900R014
73424228
VS.RRC.CONV.F
C.Num.CPU.OverLoad
Number of RRC
CONNECTION
REQUESTS for CS
Voice Services
Under Flow Control
Triggered by High
CPU Usage for Cell
BSC6900
V900R014
73424229
VS.RRC.CONV.F
C.Num.RRCQueue
Number of RRC
CONNECTION
REQUESTS for CS
Voice Services
Under Flow Control
Triggered by RRC
Queue Overflow for
Cell
BSC6900
V900R014
73424230
VS.RRC.CONV.F
C.Num.MPU.OverLoad
Number of RRC
CONNECTION
REQUESTS for CS
Voice Services
Under Flow Control
Triggered by MPU
Overload for Cell
BSC6900
V900R014

3067
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424231
VS.RRC.CONV.F
C.Num.CallShock
Number of RRC
CONNECTION
REQUESTS for CS
Voice Services
Under Flow Control
Triggered by Burst
Traffic for Cell
BSC6900
V900R014
73424232
VS.CU.FC.Num.C
PU.OverLoad
Number of Cell
Updates Under Flow
High CPU Usage for
Cell
BSC6900
V900R014
73424233
VS.RRC.FC.Num.
RanFC.Ph2
Number of RRC
CONNECTION
REQUESTS Under
E2E Flow Control
Phase 2 for Cell
BSC6900
V900R014
73424234
VS.RRC.CONV.F
C.Num.RanFC.Ph2
Number of RRC
CONNECTION
REQUESTS for CS
Voice Services
Under E2E Flow
Control Phase 2 for
Cell
BSC6900
V900R014
73424476
VS.RRC.AttConnE
stab.PSDomain
Number of RRC
Connection Setup
Requests for Cell (PS
Domain)
BSC6900
V900R014
73424477
VS.RRC.AttConnE
stab.CSDomain
Number of RRC
Connection Setup
Requests for Cell
(CS Domain)
BSC6900
V900R014
73424691
VS.RRC.CONV.F
C.Num.INT.OverLoad
Number of RRC
CONNECTION
REQUESTS for CS
Voice Services
Under Flow Control
Triggered by
Interface-Board CPU
Overload for Cell
BSC6900
V900R014

3068
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424692
VS.RRC.FC.Num.I
NT.OverLoad
Number of RRC
CONNECTION
REQUESTS Under
Flow Control
Triggered by
Interface-Board CPU
Overload for Cell
BSC6900
V900R014
73424693
VS.RRC.FC.Num.
FACH.Cong
Number of RRC
CONNECTION
REQUESTS Under
Flow Control
Triggered by FACH
Congestion for Cell
BSC6900
V900R014
73424694
VS.RRC.CONV.F
C.Num.RanFC.Ph1
Number of RRC
CONNECTION
REQUESTS for CS
Voice Services
Under E2E Flow
Control Phase 1 for
Cell
BSC6900
V900R014
73424695
VS.RRC.FC.Num.
RanFC.Ph1
Number of RRC
CONNECTION
REQUESTS Under
E2E Flow Control
Phase 1 for Cell
BSC6900
V900R014
73424968
VS.RRC.FC.Num.
CAPS
Number of RRC
CONNECTION
REQUESTS in a Cell
Under Cell Dynamic
CAPS Flow Control
BSC6900
V900R014
73424969
VS.RRC.CONV.F
C.Num.CAPS
Number of RRC
CONNECTION
REQUESTS for CS
Services in a Cell
Under Cell Dynamic
CAPS Flow Control
BSC6900
V900R014
73425017
VS.RRC.AttConnE
stab.WithSI.CsDomain
Number of RRC
Connection Setup
Requests that carried
System Information
Container Stored
Indication for CS
services
BSC6900
V900R014

3069
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425018
VS.RRC.SuccConn
Estab.WithSI.CsDo
main
Number of
Successful RRC
Connection Setups
for CS services (RRC
Connection Setup
System Information
Container Stored
Indication)
BSC6900
V900R014
73425019
VS.RRC.AttConnE
stab.WithSI.PsDomain
Number of RRC
Connection Setup
System Information
Container Stored
Indication for PS
services
BSC6900
V900R014
73425020
VS.RRC.SuccConn
Estab.WithSI.PsDo
main
Number of
Successful RRC
Connection Setups
for PS services (RRC
Connection Setup
System Information
Container Stored
Indication)
BSC6900
V900R014
73425914
RRC.AttConnEsta
b.Conv.Platinum
Number of RRC
Connection Setup
Requests for
Platinum UEs
Performing
Conversational
Services for Cell
BSC6900
V900R015C00
73425915
RRC.AttConnEsta
b.Platinum
Number of RRC
Connection Setup
Requests for
Platinum UEs
Performing Services
for Cell
BSC6900
V900R015C00

3070
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425916
RRC.SuccConnEst
ab.Conv.Platinum
Number of
Successful RRC
Connection Setups
for Platinum UEs
Performing
Conversational
Services for Cell
BSC6900
V900R015C00
73425917
RRC.SuccConnEst
ab.Platinum
Number of
Successful RRC
Connection Setups
for Platinum UEs for
Cell
BSC6900
V900R015C00
73426415
VS.RRC.AttConnE
stab.CSFB
Number of RRC
Connection Setup
Requests for CSFB
for Cell
BSC6900
V900R015C01
73426416
VS.RRC.SuccConn
Estab.CSFB
Number of
Successful RRC
Connection Setups
for CSFB for Cell
BSC6900
V900R015C01
73427913
VS.RRC.AttConnE
stab.CellUpd.DSC
R.CS
Number of CS RRC
Connection Setup
Requests in the
DSCR Procedure
Triggered by Process
Overlapping for Cell
BSC6900
V900R016C00
73427914
VS.RRC.AttConnE
stab.CellUpd.DSC
R.PS
Number of PS RRC
Connection Setup
Requests in the
DSCR Procedure
BSC6900
V900R016C00
73427915
VS.RRC.AttConnE
stab.CellUpd.DSC
R.Other
Number of RRC
Connection Setup
Requests in the
DSCR Procedure
(Others)
BSC6900
V900R016C00

3071
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73427916
VS.RRC.AttConnE
stab.CellUpd.DSC
R.Service
Number of RRC
Connection Setup
Requests in the
DSCR Procedure
(Service)
BSC6900
V900R016C00
Each Counter's value equals to the sum of its subcounters' values
Counter
Sub Counter
VS.RRC.AttConnEstab.Sum
RRC.AttConnEstab.OrgConvCall
RRC.AttConnEstab.OrgStrCall
RRC.AttConnEstab.OrgInterCall
RRC.AttConnEstab.OrgBkgCall
RRC.AttConnEstab.TmConvCall
RRC.AttConnEstab.TmStrCall
RRC.AttConnEstab.TmInterCall
RRC.AttConnEstab.TmBkgCall
RRC.AttConnEstab.OrgSubCall
RRC.AttConnEstab.EmgCall
RRC.AttConnEstab.IRATCelRes
RRC.AttConnEstab.IRATCCO
RRC.AttConnEstab.Reg
RRC.AttConnEstab.Detach
RRC.AttConnEstab.OrgHhPrSig
RRC.AttConnEstab.OrgLwPrSig
RRC.AttConnEstab.CallReEst
RRC.AttConnEstab.TmHhPrSig
RRC.AttConnEstab.TmLwPrSig
RRC.AttConnEstab.Unknown
RRC.AttConnEstab.MBMSRep
RRC.AttConnEstab.MBMSPtp
Issue 03 (2015-06-30)

3072
BSC6900 UMTS
Counter
Sub Counter
RRC.SuccConnEstab.sum
RRC.SuccConnEstab.OrgConvCall
RRC.SuccConnEstab.OrgStrCall
RRC.SuccConnEstab.OrgInterCall
RRC.SuccConnEstab.OrgBkgCall
RRC.SuccConnEstab.OrgSubCall
RRC.SuccConnEstab.TmConvCall
RRC.SuccConnEstab.TmStrCall
RRC.SuccConnEstab.TmItrCall
RRC.SuccConnEstab.TmBkgCall
RRC.SuccConnEstab.IRATCelRes
RRC.SuccConnEstab.IRATCCO
RRC.SuccConnEstab.Reg
RRC.SuccConnEstab.OrgHhPrSig
RRC.SuccConnEstab.OrgLwPrSig
RRC.SuccConnEstab.CallReEst
RRC.SuccConnEstab.TmHhPrSig
RRC.SuccConnEstab.TmLwPrSig
RRC.SuccConnEstab.Unkown
RRC.SuccConnEstab.EmgCall
RRC.SuccConnEstab.MBMSRep
RRC.SuccConnEstab.MBMSPtp
Each Counter's value is greater than the sum of its SubCounters' value
Issue 03 (2015-06-30)
Counter
Sub Counter
vice
VS.RRC.AttConnEstab.CellUpd.DSCR.CS
VS.RRC.AttConnEstab.CellUpd.DSCR.PS

3073
BSC6900 UMTS
Number of Received RRC CONNECTION REQUESTS for CS Services in a Cell

Counters
Counter ID
Counter Name
Counter Description
73424223
.Conv
Number of Received RRC

CONNECTION
in a Cell
Description
This counter provides the total number of received RRC CONNECTION REQUEST messages
for CS services in a cell, including repeatedly transmitted messages. If the establishment cause
in these requests is UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE or
current service is a CS service.This counter complies with section "8.1.3 RRC connection
Measurement point
After the RNC receives an RRC CONNECTION REQUEST message from a UE, this counter
is increased by one if the current service is a CS service. This counter calculates the repeatedly
transmitted RRC CONNECTION REQUEST message in the RRC connection setup procedure.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.Conv
WRFD-040100
Flow Control

3074
BSC6900 UMTS
Counters Related to the Number of RRC Connection Requests for Various Reasons
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179329

Requests for Cell
Call)
67179330

Requests for Cell
67179331

Requests for Cell
67179332
RRC.AttConnEstab.OrgBkg
Call

Requests for Cell
Call)
67179334
RRC.AttConnEstab.TmCon
vCall

Requests for Cell
Call)
67179335
RRC.AttConnEstab.TmStrC
all

Requests for Cell
Call)
67179336

Requests for Cell
Call)
67179337
RRC.AttConnEstab.TmBkg
Call

Requests for Cell
Call)
67179333

Requests for Cell
Traffic Call)
67179338

Requests for Cell
(Emergency Call)

3075
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179339

Requests for Cell (Inter-RAT
Cell Re-Selection)
67179340

Cell Change Order)
67179341

Requests for Cell
(Registration)
67179342

Requests for Cell (Detach)
67179343
RRC.AttConnEstab.OrgHhP
rSig

Requests for Cell
Signaling)
67179344
RRC.AttConnEstab.OrgLw
PrSig

Requests for Cell
Signaling)
67179345

Requests for Cell (Call ReEstablishment)
67179346
RRC.AttConnEstab.TmHhP
rSig

Requests for Cell
Signaling)
67179347
RRC.AttConnEstab.TmLwP
rSig

Requests for Cell
Signaling)
67179348

Requests for Cell
(Terminating-Cause
Unknown)
67195964
RRC.AttConnEstab.MBMS
Rep

Requests for Cell (MBMS
Reception)
67195965
Ptp

Requests for Cell (MBMS
PTP RB Request)

3076
BSC6900 UMTS
Description
These counters provide the number of RRC CONNECTION REQUEST messages sent from the
UE to the RNC that are actually processed by the RNC according to various reasons for RRC
connection requests. These counters exclude the number of rejected RRC connection requests
caused by service-based redirection, inter-RAT and inter-frequency distance-based redirection,
weakcoverage-based redirection, macro & micro joint inter-frequency redirection, UE
capability-based inter-frequency redirection or flow control discarding.These counters do not
procedure and cell update procedure.The preceding counters comply with section "8.1.3 RRC
Measurement point
CONNECTION REQUEST message from the UE. In this case, these counters are measured
separately according to the reasons for RRC connection requests in the cell where the UE is
located. These counters exclude the number of rejected RRC connection requests caused by
service-based redirections, inter-RAT and inter-frequency distance-based redirections,
weakcoverage-based redirections, and macro-and-micro-problematic-area-based interfrequency redirections, UE capability-based inter-frequency redirection, and the number of RRC
connection requests discarded during flow control. For more details on the reason types, see
3GPP TS 25.331. In the RRC connection setup procedure, The measurement is not triggered for
a RRC CONNECTION REQUEST message that is retransmitted by the UE.These counters do
not include the RRC connection setup requests in the Directed Signalling Connection Reestablishment (DSCR) procedure triggered by the overlapping of the RRC connection setup
procedure and cell update procedure.
Formula
None
Issue 03 (2015-06-30)

3077
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010501

WRFD-010510
WRFD-010502
3.4/6.8/13.6/27.2Kbps RRC
and Release
Streaming QoS Class
WRFD-010510
WRFD-010503
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.OrgBkg
Call
WRFD-010510
WRFD-010504
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.TmCon
vCall
WRFD-010510
WRFD-010501
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.TmStrC
all
WRFD-010510
WRFD-010502
3.4/6.8/13.6/27.2Kbps RRC
and Release
Streaming QoS Class
WRFD-010510
WRFD-010503
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

3078
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
RRC.AttConnEstab.TmBkg
Call
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010504
Issue 03 (2015-06-30)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-021104
Emergency Call
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.OrgHhP
rSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.OrgLw
PrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3079
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
RRC.AttConnEstab.TmHhP
rSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.TmLwP
rSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Rep
WRFD-01066001

Mode
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Ptp
WRFD-01066001
WRFD-010510

Mode
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counters Related to the Number of Processed RRC Connection Requests

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190586
Number of Processed RRC

Connection Requests for Cell
67179633
DCH

Requests for Cell (UE Target
State of CELL_DCH)
67179649
FACH

Requests for Cell (UE Target
State of CELL_FACH)

3080
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67196198
VS.RRC.AttConnEstab.ED
CH

Attempts for UL Carried on
E_DCH for Cell
67196199
VS.RRC.AttConnEstab.HS
DSCH

Attempts for DL Carried on
HS_DSCH for Cell
Description
These counters provide the number of times the RNC receives an RRC CONNECTION
REQUEST message from UEs in a cell. These counters exclude the number of rejected RRC
connection requests caused by service-based redirection, inter-RAT and inter-frequency
distance-based redirection, weakcoverage-based redirection, macro & micro joint interfrequency redirection, UE capability-based inter-frequency redirection and the number of RRC
connection requests discarded during flow control. These counters also exclude the RRC
connection requests in the Direct Signaling Connection Reestablishment (DSCR) triggered by
the overlapping of RRC connection setup and cell procedure procedures. The
VS.RRC.AttConnEstab.HSDSCH counter applies to UEs that use SRB over HSDPA and SRB
over EFACH. The VS.RRC.AttConnEstab.EDCH counter applies to UEs that use SRB over
HSUPA and SRB over ERACH.The preceding counters comply with section "8.1.3 RRC
Measurement point
CONNECTION REQUEST message from the UE. In this case, these counters are measured
separately in the cell where the UE is located. These counters exclude the number of rejected
RRC connection requests caused by service-based redirection, inter-RAT and inter-frequency
distance-based redirection, weakcoverage-based redirection, macro & micro joint interfrequency redirection, UE capability-based inter-frequency redirection or flow control
discarding. In addition,These counters do not include the RRC connection setup requests in the
overlapping of the RRC connection setup procedure and cell update procedure. Note that the
measurement is not triggered for a RRC CONNECTION REQUEST message that is
retransmitted by the UE in the RRC connection setup procedure..
Issue 03 (2015-06-30)

3081
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
DCH
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010202

URA-PCH, CELL-FACH)
Issue 03 (2015-06-30)

3082
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
FACH
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010202

URA-PCH, CELL-FACH)
VS.RRC.AttConnEstab.ED
CH
WRFD-010636
SRB over HSUPA
WRFD-010701
Uplink Enhanced
CELL_FACH
VS.RRC.AttConnEstab.HS
DSCH
WRFD-010652
SRB over HSDPA
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of RRC Connection Requests sent by the UE for cell

Counters
Counter ID
Counter Name
Counter Description
73403798

Requests sent by the UE for
cell
Description
The measurement item takes statistics of the total Number of RRC Connection Requests sent
by the UE including first and repetitive times.This counter complies with section "8.1.3 RRC
Measurement point
The measurement is triggered at point A in the figure. This measurement counter is incremented
by one when the RNC receives a RRC CONNECTION REQUEST message from an UE. To
increase the possibility of successful connection, an UE may send the RRC CONNECTION
REQUEST many times. The RNC counts the RRC connection requests repetitively sent by the
UE in the RRC connection setup procedure.
Issue 03 (2015-06-30)

3083
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3084
BSC6900 UMTS
Number of Retransmitted RRC Connection Setup Requests for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423388
RRC.AttConnEstab.Rep.Or
gConvCall
Number of Retransmitted
RRC Connection Setup
Requests for Cell
Call)
73423389
gStrCall
Requests for Cell
73423390
RRC.AttConnEstab.Rep.OrgInterCall
Requests for Cell
73423391
gBkgCall
Requests for Cell
Call)
73423392
RRC.AttConnEstab.Rep.Tm
ConvCall
Requests for Cell
Call)
73423393
StrCall
Requests for Cell
Call)
73423394
InterCall
Requests for Cell
Call)
73423395
BkgCall
Requests for Cell
Call)

3085
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423396
gSubCall
Requests for Cell
Traffic Call)
73423397
RRC.AttConnEstab.Rep.Em
gCall
Requests for Cell
(Emergency Call)
73423398
RRC.AttConnEstab.Rep.IR
ATCelRes
Cell Re-selection)
73423399
ATCCO
Cell Change Order)
73423400
RRC.AttConnEstab.Rep.Re
g
Requests for Cell
(Registration)
73423401
RRC.AttConnEstab.Rep.Detach
Requests for Cell (Detach)
73423402
gHhPrSig
Requests for Cell
Signalling)
73423403
gLwPrSig
Requests for Cell
Signalling)
73423404
RRC.AttConnEstab.Rep.Cal
lReEst
Requests for Cell (Call Reestablishment)
73423405
HhPrSig
Requests for Cell
Signalling)

3086
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73423406
LwPrSig
Requests for Cell
Signalling)
73423407
RRC.AttConnEstab.Rep.Un
known
Requests for Cell
(Terminating-Cause
Unknown)
Description
These counters provide the number of retransmitted RRC connection setup requests in the cell
after an RRC connection request is rejected due to resource insufficiency. These counters do not
procedure and cell update procedure. These counters indicate whether the resources are
congested. A high counter value indicates that a large number of users have accessed the cell or
the resources of the RNC or NodeB are insufficient, and the RRC connection setup fails. The
preceding counters comply with section "8.1.3 RRC connection establishment" in 3GPP TS
25.331 (v10.13.0).
Measurement point
The measurement is triggered at point B, C, D, and so on as shown in the figure. If an RRC
Connection Request message sent by the UE is rejected because of resource insufficiency, the
UE sends the RRC Connection Request message again. In this case, a counter is measured
according to the request cause as shown in point B. If the request is rejected again, the UE sends
another RRC Connection Request message, and a counter is measured again according to the
request cause as shown in point C. That is, each time an RRC Connection Request message is
retransmitted within (RRCWaitTime x N300 + 2) seconds after the last RRC Connection Request
message is sent by the UE, a counter is measured.These counters do not include the RRC
procedure.
Issue 03 (2015-06-30)

3087
BSC6900 UMTS
Figure 1-1356 RRC connection setup request resending and rejection
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
gConvCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3088
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
gStrCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.Rep.OrgInterCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
gBkgCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
ConvCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
StrCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
InterCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
BkgCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
gSubCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.Rep.Em
gCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
ATCelRes
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3089
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ATCCO
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.Rep.Re
g
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.Rep.Detach
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
gHhPrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
gLwPrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.Rep.Cal
lReEst
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
HhPrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
LwPrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.AttConnEstab.Rep.Un
known
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3090
BSC6900 UMTS
Number of RRC Connection Setup Requests for Cell (PS Domain)

Counters
Counter ID
Counter Name
Counter Description
73424476
VS.RRC.AttConnEstab.PSD
omain

Setup Requests for Cell (PS
Domain)
Description
This counter measures the number of radio resource control (RRC) connection setup requests
for PS services in a cell.This counter does not include the RRC connection setup requests in the
Measurement point
The measurement is triggered at point A shown in the figure when the RNC receives an RRC
CONNECTION REQUEST message containing the information element (IE) Domain Indicator
from a UE that is compliant with 3GPP Release 6 or later. This counter excludes the number of
rejected RRC connection requests caused by service-based redirection, inter-RAT and interfrequency distance-based redirection, weakcoverage-based redirection, macro & micro joint
inter-frequency redirection, UE capability-based inter-frequency redirection and the number of
RRC connection requests discarded during flow control and the number of RRC CONNECTION
REQUEST messages retransmitted by the UE in the RRC connection setup procedure.This
counter does not include the RRC connection setup requests in the Directed Signalling
Connection Re-establishment (DSCR) procedure triggered by the overlapping of the RRC
connection setup procedure and cell update procedure.
Issue 03 (2015-06-30)

3091
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnEstab.PSD
omain
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-140213

Control
Number of RRC Connection Setup Requests for Cell (CS Domain)

Counters
Counter ID
Counter Name
Counter Description
73424477
VS.RRC.AttConnEstab.CS
Domain

Setup Requests for Cell (CS
Domain)
Description
This counter measures the number of RRC connection setup requests for CS services in a
cell.This counter does not include the RRC connection setup requests in the Directed Signalling
connection setup procedure and cell update procedure.This counter complies with section "8.1.3
Measurement point
CONNECTION REQUEST message containing the IE Domain Indicator from a UE that is
compliant with 3GPP Release 6 or later. This counter excludes the number of rejected RRC
distance-based redirection, weakcoverage-based redirection, macro & micro joint interfrequency redirection and the number of RRC connection requests discarded during flow control
and the number of RRC CONNECTION REQUEST messages retransmitted by the UE in the
Issue 03 (2015-06-30)

3092
BSC6900 UMTS
RRC connection setup procedure. This counter does not include the RRC connection setup
by the overlapping of the RRC connection setup procedure and cell update procedure.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.AttConnEstab.CS
Domain
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-140213

Control
Issue 03 (2015-06-30)

3093
BSC6900 UMTS
Number of RRC Connection Setup Requests that carried System Information

Container Stored Indication for CS services
Counters
Counter ID
Counter Name
Counter Description
73425017
VS.RRC.AttConnEstab.Wit
hSI.CsDomain

Setup Requests that carried
System Information
Container Stored Indication
for CS services
Description
This counter provides the number of RRC CONNECTION REQUEST messages that are for PS
services, are received by the RNC from the UE, and carry the value TRUE for "System
Information Container Stored Indication".This counter does not include the RRC connection
setup requests in the Directed Signalling Connection Re-establishment (DSCR) procedure
triggered by the overlapping of the RRC connection setup procedure and cell update
TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure.When the RNC receives an RRC
CONNECTION REQUEST message from the UE, if the value of "System Information
Container Stored Indication" is TRUE and the domain indication is the CS domain, this counter
is increased by one in the cell where the UE is camping on.This counter does not include the
RRC connection setup requests in the Directed Signalling Connection Re-establishment (DSCR)
procedure.Note that this counter is not triggered for a RRC CONNECTION REQUEST message
that is retransmitted by the UE in the RRC connection setup procedure.
Figure 1-1359 Procedure for successful RRC setup
Issue 03 (2015-06-30)

3094
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
hSI.CsDomain
WRFD-140224

RIM
Number of RRC Connection Setup Requests that carried System Information

Container Stored Indication for PS services
Counters
Counter ID
Counter Name
Counter Description
73425019
hSI.PsDomain

System Information
Container Stored Indication
for PS services
Description
This counter provides the number of RRC CONNECTION REQUEST messages that are for PS
services, are received by the RNC from the UE, and carry the value TRUE for "System
Information Container Stored Indication".This counter does not include the RRC connection
TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure.When the RNC receives an RRC
Container Stored Indication" is TRUE and the domain indication is the PS domain, this counter
is increased by one in the cell where the UE is camping on.This counter does not include the
RRC connection setup requests in the Directed Signalling Connection Re-establishment (DSCR)
Issue 03 (2015-06-30)

3095
BSC6900 UMTS
procedure.Note that this counter is not triggered for a RRC CONNECTION REQUEST message
that is retransmitted by the UE in the RRC connection setup procedure.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
hSI.PsDomain
WRFD-140224

RIM

3096
BSC6900 UMTS
Number of RRC Connection Setup Requests for Platinum UEs Performing

Conversational Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73425914
RRC.AttConnEstab.Conv.Pl
atinum

Setup Requests for Platinum
UEs Performing
Cell
Description
This counter measures the number of RRC CONNECTION REQUEST messages (containing
the cause values "Originating Conversational Call" and "Terminating Conversational Call")
received by the RNC from platinum UEs.This counter does not include the RRC connection
TS 25.331 (v10.13.0).
Measurement point
CONNECTION REQUEST message from a UE and determines that the UE is a platinum user.
In this case, this counter is measured in the cell that the UE camps on. These counters exclude
joint inter-frequency redirection and the number of RRC connection requests discarded during
flow control. These counters do not include the RRC connection setup requests in the Directed
RRC connection setup procedure and cell update procedure.Note that the measurement is not
triggered for RRC CONNECTION REQUEST messages retransmitted by the UE in the RRC
connection setup procedure.
Issue 03 (2015-06-30)

3097
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RRC.AttConnEstab.Conv.Pl
atinum
WRFD-150204
Number of RRC Connection Setup Requests for Platinum UEs Performing Services
for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425915
RRC.AttConnEstab.Platinum

Setup Requests for Platinum
UEs Performing Services for
Cell

3098
BSC6900 UMTS
Description
This counter measures the number of RRC CONNECTION REQUEST messages received by
the RNC from platinum UEs (without differentiating between cause values).This counter does
not include the RRC connection setup requests in the Directed Signalling Connection Reestablishment (DSCR) procedure triggered by the overlapping of the RRC connection setup
procedure and cell update procedure.This counter complies with section "8.1.3 RRC connection
Measurement point
CONNECTION REQUEST message from a UE and determines that the UE is a platinum user.
In this case, this counter is measured in the cell that the UE camps on.This counter excludes the
number of rejected RRC connection requests caused by service-based redirection, inter-RAT
joint inter-frequency redirection, UE capability-based inter-frequency redirection and the
number of RRC connection requests discarded during flow control. This counter does not include
the RRC connection setup requests in the Directed Signalling Connection Re-establishment
(DSCR) procedure triggered by the overlapping of the RRC connection setup procedure and cell
update procedure.Note that the measurement is not triggered for RRC CONNECTION
REQUEST messages retransmitted by the UE in the RRC connection setup procedure.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3099
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
RRC.AttConnEstab.Platinum
WRFD-150204
Number of RRC Connection Setup Requests in the DSCR Procedure Triggered by

Process Overlapping for Cell
Counters
Counter ID
Counter Name
Counter Description
73427916
Upd.DSCR.Service

Setup Requests in the DSCR
Procedure Triggered by
(Service)
73427913
Upd.DSCR.CS
Number of CS RRC
Connection Setup Requests
in the DSCR Procedure
73427914
Upd.DSCR.PS
Number of PS RRC
in the DSCR Procedure
73427915
Upd.DSCR.Other

Setup Requests in the DSCR
Procedure Triggered by
(Others)
Description
These counters provide the number of RRC connection setup requests in the Direct Signaling
Connection Reestablishment (DSCR) procedure triggered by process overlapping in a cell.
Process overlapping refers to the overlapping of the RRC connection setup procedure and cell
update procedure. That is, the RNC receives a CELL UPDATE message from a UE after sending
an RRC CONNECTION SETUP message to the UE.This counter complies with section "8.1.3
Issue 03 (2015-06-30)

3100
BSC6900 UMTS
Counter Name
Description
vice
1.The value of this counter includes the

values of
and
VS.RRC.AttConnEstab.CellUpd.DSCR.PS.
2.The RRC CONNECTION REQEUST
message can carry any of the following cause
values:
Originating Conversational Call
Originating Streaming Call
Originating Interactive Call
Originating Background Call
Originating Subscribed traffic Call
Terminating Conversational Call
Terminating Streaming Call
Terminating Interactive Call
Terminating Background Call
Emergency Call
Terminating-Cause Unknown
Originating High Priority Signalling
Originating Low Priority Signalling
Call Re-establishment
Terminating High Priority Signalling
Terminating Low Priority Signalling
1.This counter applies to CS service.

values:
Originating Conversational Call
Terminating Conversational Call
Emergency Call
Issue 03 (2015-06-30)

3101
BSC6900 UMTS
Counter Name
Description
VS.RRC.AttConnEstab.CellUpd.DSCR.PS
1.This counter applies to PS service.

values:
Originating Interactive Call
Originating Background Call
Terminating Interactive Call
Terminating Background Call
Originating High Priority Signalling
Terminating High Priority Signalling
VS.RRC.AttConnEstab.CellUpd.DSCR.Oth
er
1.This counter applies to non-service-related

RRC connection.
values:
Inter-RAT cell re-selection
Inter-RAT cell change order
Registration
Detach
Measurement point
The RNC receives an RRC CONNECTION REQUEST message from a UE, determines the
service type based on the cause value included in the message, and returns an RRC
CONNECTION SETUP message to the UE. If the RNC receives a CELL UPDATE message
(cause value: RLC UNRECOVERABLE ERROR, RadioLink Failure, Cell Reselection, or Reentered Service Area) from the UE while waiting for the UE's response to the RRC
CONNECTION SETUP message, the RRC connection setup procedure overlaps with the cell
update procedure. Under this circumstance, the RNC sends an RRC CONNECTION RELEASE
message with the cause value "Directed Signalling Connection Re-establishment" to the UE.
Figure 1 shows the overlapping of the RRC connection setup procedure and cell update
procedure. The preceding counters are measured at point A in the cell where the UE reports the
RRC connection setup message based on the service type.
Issue 03 (2015-06-30)

3102
BSC6900 UMTS
Figure 1-1363 Overlapping of the RRC connection setup procedure and cell update procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Upd.DSCR.Service
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010801

Upd.DSCR.CS
WRFD-010510
WRFD-010801
3.4/6.8/13.6/27.2Kbps RRC
and Release
Upd.DSCR.PS
WRFD-010510
WRFD-010801
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

3103
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
Upd.DSCR.Other
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010801
The average Ec/N0 at each propagation delay range in a cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441146
VS.EcNo.Mean.TP0
Average Ec/N0 During RRC

Requests with Propagation
Delay of 0
73441147
VS.EcNo.Mean.TP1

Delay of 1
73441148
VS.EcNo.Mean.TP2

Delay of 2
73441149
VS.EcNo.Mean.TP3

Delay of 3
73441150
VS.EcNo.Mean.TP4

Delay of 4
73441151
VS.EcNo.Mean.TP5

Delay of 5
73441152
VS.EcNo.Mean.TP6.9

Delay of 6~9

3104
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73441153
VS.EcNo.Mean.TP10.15

Delay of 10~15
73441154

Delay of 16~25
73441155

Delay of 26~35
73441156

Delay of 36~55
73441157
VS.EcNo.Mean.TP.More55

Delay Greater than 55
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423485
VS.EcNo.Cum.TP0
TP0Cum
73423487
VS.EcNo.Cum.TP1
TP1Cum
73423509
VS.EcNo.Cum.TP10.15
TP10~15Cum
73423501
VS.EcNo.Cum.TP16.25
TP16~25Cum
73423489
VS.EcNo.Cum.TP2
TP2Cum
73423503
VS.EcNo.Cum.TP26.35
TP26~35Cum
73423491
VS.EcNo.Cum.TP3
TP3Cum
73423505
VS.EcNo.Cum.TP36.55
TP36~55Cum
73423493
VS.EcNo.Cum.TP4
TP4Cum
73423495
VS.EcNo.Cum.TP5
TP5Cum
73423497
VS.EcNo.Cum.TP6.9
TP6~9Cum

3105
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423507
VS.EcNo.Cum.TP.More55
TPMore55Cum
73427998
VS.EcNo.Sample.TP0

Establishment Requests
Where Propagation Delay is
0 and Ec/No Is Included for
Cell
73427999
VS.EcNo.Sample.TP1

Cell
73428005
VS.EcNo.Sample.TP10.15

Where Propagation Delay
Ranges from 10 to 15 and Ec/
No Is Included for Cell
73428006

73428000
VS.EcNo.Sample.TP2

Cell
73428007

73428001
VS.EcNo.Sample.TP3

Cell
73428008


3106
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73428002
VS.EcNo.Sample.TP4

Cell
73428003
VS.EcNo.Sample.TP5

Cell
73428004

Ranges from 6 to 9 and Ec/No
Is Included for Cell
73428009
VS.EcNo.Sample.TP.More5
5

Where Propagation Delay Is
Greater Than 55 and Ec/No Is
Included for Cell
Description
These counters provide the average Ec/N0 at each propagation delay range in a cell. The
propagation delay is carried in the RACH DATA FRAME message sent from the NodeB to the
RNC during an RRC connection establishment procedure. These counters are calculated based
on the Ec/N0 value reported by the UE. As specified in 3GPP TS25.133, the mapping between
the reported Ec/N0 value and the measured Ec/N0 value is: Measured Ec/N0 value = Round off
((Reported Ec/N0 value - 49)/2).The preceding counters comply with section "8.1.3 RRC
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an RRC
CONNECTION REQUEST message from a cell, the RNC accumulates Ec/N0 according to the
range of the propagation delay. At the end of each measurement period, the RNC divides the
accumulated Ec/N0 by the number of RRC connection requests in each propagation delay range
to obtain the average Ec/N0.
Issue 03 (2015-06-30)

3107
BSC6900 UMTS
Figure 1-1364 RRC connection establishment procedure
Formula
VS.EcNo.Mean.TP0 = [VS.EcNo.Cum.TP0]/[VS.EcNo.Sample.TP0]
VS.EcNo.Mean.TP6.9 = [VS.EcNo.Cum.TP6.9]/[VS.EcNo.Sample.TP6.9]
VS.EcNo.Mean.TP.More55 = [VS.EcNo.Cum.TP.More55]/[VS.EcNo.Sample.TP.More55]
Unit
dB
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.EcNo.Mean.TP0
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3108
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.EcNo.Mean.TP1
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.EcNo.Mean.TP2
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.EcNo.Mean.TP3
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.EcNo.Mean.TP4
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.EcNo.Mean.TP5
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.EcNo.Mean.TP6.9
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3109
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.EcNo.Mean.TP.More55
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Establishment Requests that propagation delay falls

into different value ranges in a cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73423486
VS.TP.UE.0

Establishment Requests with
Propagation Delay of 0
73423488
VS.TP.UE.1

73423490
VS.TP.UE.2

73423492
VS.TP.UE.3

73423494
VS.TP.UE.4

73423496
VS.TP.UE.5

73423498
VS.TP.UE.6.9

Propagation Delay of 6~9
73423502
VS.TP.UE.16.25

73423504
VS.TP.UE.26.35


3110
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73423506
VS.TP.UE.36.55

73423508
VS.TP.UE.More55

Propagation Delay Greater
than 55
73423510
VS.TP.UE.10.15

Description
These counters provide the number of times that propagation delay falls into different value
ranges in a cell. The propagation delay is carried in the RACH DATA FRAME message sent
from the NodeB to the RNC during an RRC connection establishment procedure. These counters
reflect the distribution of UEs in a cell.The preceding counters comply with section "8.1.3 RRC
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives a RACH
DATA FRAME message from a cell, the RNC increments the corresponding counter according
to the range of the propagation delay carried in the message. At the end of each measurement
period, the RNC calculates the total number of RRC connection establishments in each
propagation delay range.
Each propagation delay represents three chips(only the propagation delay of 0 represents two
chips). The propagation distance of one chip is 78 m.
When the propagation delay is 0, it indicates that the UE is 0-156 m away from the base station.
When the propagation delay is 1, it indicates that the UE is 156-390 m away from the base
station.
station.
......
station.
Issue 03 (2015-06-30)

3111
BSC6900 UMTS
Figure 1-1365 RRC connection establishment procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.TP.UE.0
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.1
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.2
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.3
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.4
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3112
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.TP.UE.5
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.6.9
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.16.25
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.26.35
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.36.55
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.More55
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.TP.UE.10.15
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Setup Messages Sent from RNC to UE

Counters
Counter ID
Counter Name
Counter Description
67179298

Setup Messages from RNC to
UE for Cell
Description
This counter measures the number of RRC CONNECTION SETUP messages from the RNC to
the UE in the cell after the RNC receives a RRC CONNECTION REQUEST message from the
Issue 03 (2015-06-30)

3113
BSC6900 UMTS
UE.This counter does not include the RRC connection setup requests in the Directed Signalling
connection setup procedure and cell update procedure.This counter complies with section "8.1.3
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC sends a RRC
CONNECTION SETUP message to the UE after receiving a RRC CONNECTION REQUEST
message from the UE. In this case, this counter is measured in the cell where the UE is
located.This counter does not include the RRC connection setup requests in the Directed
RRC connection setup procedure and cell update procedure. Note that the measurement is not
triggered for a RRC CONNECTION SETUP message that is retransmitted by the RNC to the
UE.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3114
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counters Related to the Number of Successful RRC Connection Setups

Counters
Counter ID
Counter Name
Counter Description
67179299

67179634
llDCH

(UE Target State of
CELL_DCH)
67179650
llFACH

(UE Target State of
CELL_FACH)
67196200
DCH

(UL Carried on E_DCH)
67196201
VS.RRC.SuccConnEstab.H
SDSCH

(DL Carried on HS_DSCH)
Description
These counters provide the number of times the RNC receives an RRC CONNECTION SETUP
COMPLETE message from UEs in a cell. The VS.RRC.SuccConnEstab.HSDSCH counter
applies to UEs that use SRB over HSDPA and SRB over EFACH. The
VS.RRC.SuccConnEstab.EDCH counter applies to UEs that use SRB over E-DCH and SRB
over ERACH.The preceding counters comply with section "8.1.3 RRC connection
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, these counters are measured in the
cell where the UE is located.
Issue 03 (2015-06-30)

3115
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
llDCH
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010202

URA-PCH, CELL-FACH)
Issue 03 (2015-06-30)

3116
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
llFACH
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010202

URA-PCH, CELL-FACH)
DCH
WRFD-010636
SRB over HSUPA
WRFD-010701
Uplink Enhanced
CELL_FACH
VS.RRC.SuccConnEstab.H
SDSCH
WRFD-010652
SRB over HSDPA
WRFD-010688
Downlink Enhanced
CELL_FACH
Number of Successful RRC Connection Setups with DRD Out

Counters
Counter ID
Counter Name
Counter Description
67189401
VS.RRC.Estab.DRDOut.Su
cc

Connection Setups with
DRD out for Cell
Description
This counter provides the number of successful RRC connection setups with RNC-initiated DRD
to a target cell during RRC connection setup. This counter is measured in the DRD source
cell.This counter complies with section "8.1.3 RRC connection establishment" in 3GPP TS
25.331 (v10.13.0).
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving a RRC
CONNECTION REQUEST message from the UE, the RNC initiates a DRD to the target cell
in the RRC connection setup procedure and receives a RRC CONNECTION SETUP
COMPLETE message from the UE. In this case, this counter is measured in the source cell.
Issue 03 (2015-06-30)

3117
BSC6900 UMTS
Figure 1-1368 Successful DRD in RRC Procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.Estab.DRDOut.Su
cc
WRFD-02040001
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3118
BSC6900 UMTS
Number of RRC Connection Setup Attempts with DRD in

Counters
Counter ID
Counter Name
Counter Description
67192607
VS.RRC.Estab.DRDIn

Setup Attempts with DRD in
for Cell
Description
This counter provides the number of RRC connection requests with RNC-initiated DRD to a
target cell during RRC connection setup. This counter is measured in the DRD target cell when
the RRC connection setup succeeds.This counter does not include the RRC connection setup
by the overlapping of the RRC connection setup procedure and cell update procedure.This
(v10.13.0).
Measurement point
The measurement is triggered at point B as shown in the figure. After receiving a RRC
CONNECTION REQUEST message from the UE, the RNC initiates the RRC connection setup
procedure with a DRD to the target cell and the RRC connection setup succeeds. In this case,
this counter is measured in the target cell.This counter does not include the RRC connection
triggered by the overlapping of the RRC connection setup procedure and cell update procedure.
Figure 1-1369 Successful DRD Procedure in RRC Procedure
Issue 03 (2015-06-30)

3119
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Estab.DRDIn
WRFD-02040001
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Counters Related to Duration of RRC Connection Setup on CELL_DCH

Counters
Counter ID
Counter Name
Counter Description
67179302
ax.CellDCH

Connection Setup for Cell
(UE Target State on
CELL_DCH)
67199510
ean.CellDCH
Average Duration of RRC

Connection Setup for Cell
(UE Target State on
CELL_DCH)
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179303
VS.RRC.ConnEstab.TimeC
um.CellDCH

Connection Setup in

3120
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67179304
VS.RRC.ConnEstab.TimeSa
mple.CellDCH

Setup in CELL_DCH State
for Cell
Description
These counters provide the duration of RRC connection setup in the cell when the target state
of the UE is CELL_DCH.The preceding counters comply with section "8.1.3 RRC connection
Measurement point
As shown in the figure, when the RNC receives a RRC CONNECTION REQUEST message,
namely at point A, the time is recorded as T1. When the RNC receives a RRC CONNECTION
SETUP COMPLETE message, namely at point C, the time is recorded as T2. As delta T=T2T1, delta T is the duration of the RRC connection setup.
Formula
VS.RRC.ConnEstabTimeMean.CellDCH = [VS.RRC.ConnEstab.TimeCum.CellDCH]/
[VS.RRC.ConnEstab.TimeSample.CellDCH]
Unit
ms
Issue 03 (2015-06-30)

3121
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
ax.CellDCH
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010202

URA-PCH, CELL-FACH)
ean.CellDCH
WRFD-010510
WRFD-010202
3.4/6.8/13.6/27.2Kbps RRC
and Release
URA-PCH, CELL-FACH)
Counters Related to the Number of Successful RRC Connection Setups for Various
Reasons
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179457

Call)
67179458
RRC.SuccConnEstab.OrgStr
Call

67179459

67179460
RRC.SuccConnEstab.OrgBk
gCall

Call)
67179461

traffic Call)

3122
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179462
RRC.SuccConnEstab.TmCo
nvCall

Call)
67179463
RRC.SuccConnEstab.TmStr
Call

Call)
67179464

Call)
67179465
RRC.SuccConnEstab.TmBk
gCall

Call)
67179467

(Inter-RAT Cell ReSelection)
67179468
RRC.SuccConnEstab.IRAT
CCO

(Inter-RAT Cell Change
Order)
67179469

(Registration)
67179470

(Detach)
67179471
RRC.SuccConnEstab.OrgH
hPrSig

Signaling)
67179472
RRC.SuccConnEstab.OrgL
wPrSig

Signaling)
67179473

(Call Re-Establishment)

3123
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67179474
RRC.SuccConnEstab.TmHh
PrSig

Signaling)
67179475
RRC.SuccConnEstab.TmLw
PrSig

Signaling)
67179476

(Terminating-Cause
Unknown)
67179466

(Emergency Call)
67195966
RRC.SuccConnEstab.MBM
SRep

(MBMS Reception)
67195967
SPtp

(MBMS PTP RB Request)
Description
from the UE to the RNC in the cell according to various reasons of RRC connection requests.The
preceding counters comply with section "8.1.3 RRC connection establishment" in 3GPP TS
25.331 (v10.13.0).
Measurement point
The measurement is triggered at point C as shown in the figure, when the RNC receives a RRC
CONNECTION SETUP COMPLETE message from the UE. In this case, these counters are
measured separately according to the reasons for RRC connection requests in the cell where the
UE is located. For details on the reason types, see section 10.3.3.11 in 3GPP TS 25.331.
Issue 03 (2015-06-30)

3124
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010501

RRC.SuccConnEstab.OrgStr
Call
WRFD-010510
WRFD-010502
3.4/6.8/13.6/27.2Kbps RRC
and Release
Streaming QoS Class
WRFD-010510
WRFD-010503
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

3125
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
RRC.SuccConnEstab.OrgBk
gCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010504

WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.SuccConnEstab.TmCo
nvCall
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010501

RRC.SuccConnEstab.TmStr
Call
WRFD-010510
WRFD-010502
3.4/6.8/13.6/27.2Kbps RRC
and Release
Streaming QoS Class
WRFD-010510
WRFD-010503
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.SuccConnEstab.TmBk
gCall
WRFD-010510
WRFD-010504
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.SuccConnEstab.IRAT
CCO
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3126
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.SuccConnEstab.OrgH
hPrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.SuccConnEstab.OrgL
wPrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.SuccConnEstab.TmHh
PrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
RRC.SuccConnEstab.TmLw
PrSig
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-021104
Emergency Call
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
SRep
WRFD-01066001

Mode
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

3127
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
SPtp
WRFD-01066001

Mode
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Successful RRC Connection Setups with Repeated RRC Connection

Request Messages from UE
Counters
Counter ID
Counter Name
Counter Description
67190587
VS.RRC.SuccConnEstab.Fir
st

Connection Setups with One
RRC Connection Request
Message from UE for Cell
67190588
VS.RRC.SuccConnEstab.Se
cond

Connection Setups with Two
RRC Connection Request
Messages from UE for Cell
67190589
VS.RRC.SuccConnEstab.Th
ird

Connection Setups with
Three RRC Connection
Request Messages from UE
for Cell
Description
sent from the UE to the RNC in the cell. These counters are measured separately according to
the number of RRC connection request messages.The preceding counters comply with section
Measurement point
receives from the UE an RRC CONNECTION SETUP COMPLETE message and the RRC
connection is established based on the first RRC CONNECTION REQUEST message sent by
the UE, the VS.RRC.SuccConnEstab.First counter is measured in the cell that the UE camps on.
Issue 03 (2015-06-30)

3128
BSC6900 UMTS
Figure 1-1372 Successful RRC connection setup during first request
The measurement is triggered at point D as shown in the following figure. When the RNC
connection is established based on the second RRC CONNECTION REQUEST message sent
by the UE, the VS.RRC.SuccConnEstab.Second counter is measured in the cell that the UE
camps on.
Issue 03 (2015-06-30)

3129
BSC6900 UMTS
Figure 1-1373 Successful RRC connection setup during second request
The measurement is triggered at point E as shown in the following figure. When the RNC
connection is established based on the third RRC CONNECTION REQUEST message sent by
the UE, the VS.RRC.SuccConnEstab.Third counter is measured in the cell that the UE camps
on.
Issue 03 (2015-06-30)

3130
BSC6900 UMTS
Figure 1-1374 Successful RRC connection setup during third request
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.SuccConnEstab.Fir
st
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3131
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RRC.SuccConnEstab.Se
cond
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.SuccConnEstab.Th
ird
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Duration of RRC Establishment Process on FACH for Cell

Counters
Counter ID
Counter Name
Counter Description
73421887
ax.CellFACH

FACH for Cell
73439969
ean.CellFACH
Mean Duration of RRC

FACH for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73421888
ellFACH.Cum

FACH for Cell
73421889
ellFACH.Sample
FACH for Cell
Description
These counters provide RRC signaling connection establishment in a cell after a UE transits to
CELL_FACH.The preceding counters comply with section "8.1.3 RRC connection
Issue 03 (2015-06-30)

3132
BSC6900 UMTS
Counter Name
Description
VS.RRC.ConnEstabTimeMax.CellFACH
Maximum delay of the RRC signaling on the

FACH in a cell
VS.RRC.ConnEstabTimeMean.CellFACH
Mean delay of the RRC signaling on the

FACH in a cell
Measurement point
As shown in the figure, when the RNC receives a RRC CONNECTION REQUEST message,
namely at point A, the time is recorded as T1. When the RNC receives a RRC CONNECTION
SETUP COMPLETE message, namely at point C, the time is recorded as T2. As delta T=T2T1, delta T is the duration of the RRC connection setup.
Formula
VS.RRC.ConnEstabTimeMean.CellFACH = [VS.RRC.ConnEstabTime.CellFACH.Cum]/
[VS.RRC.ConnEstabTime.CellFACH.Sample]
Unit
ms
Issue 03 (2015-06-30)

3133
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
ax.CellFACH
WRFD-010688
Downlink Enhanced
CELL_FACH
WRFD-010202

URA-PCH, CELL-FACH)
ean.CellFACH
WRFD-010688
WRFD-010202
Downlink Enhanced
CELL_FACH
URA-PCH, CELL-FACH)
Number of Successful RRC Connection Setups for CS services (RRC Connection

Setup Requests that carried System Information Container Stored Indication)
Counters
Counter ID
Counter Name
Counter Description
73425018
VS.RRC.SuccConnEstab.W
ithSI.CsDomain

Connection Setups for CS
services (RRC Connection
System Information
Container Stored Indication)
Description
This counter provides the number of RRC CONNECTION SETUP COMPLETE messages that
the RNC receives from the UE after the RNC receives RRC CONNECTION REQUEST
messages that are from the UE, for CS services, and carry the value TRUE for "System
Information Container Stored Indication". This counter is measured in the cell.This counter
Measurement point
The measurement is triggered at point C as shown in the figure.When the RNC receives an RRC
Container Stored Indication" is TRUE, the domain indication is the CS domain, and the UE
sends an RRC CONNECTION SETUP COMPLETE message to the RNC, this counter is
increased by one in the cell that the UE camps on.
Issue 03 (2015-06-30)

3134
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ithSI.CsDomain
WRFD-140224

RIM
Number of Successful RRC Connection Setups for PS services (RRC Connection

Setup Requests that carried System Information Container Stored Indication)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425020
ithSI.PsDomain

Connection Setups for PS
services (RRC Connection
System Information
Container Stored Indication)

3135
BSC6900 UMTS
Description
This counter provides the number of RRC CONNECTION SETUP COMPLETE messages that
the RNC receives from the UE after the RNC receives RRC CONNECTION REQUEST
messages that are from the UE, for PS services, and carry the value TRUE for "System
Information Container Stored Indication". This counter is measured in the cell.This counter
Measurement point
The measurement is triggered at point C as shown in the figure.When the RNC receives an RRC
Container Stored Indication" is TRUE, the domain indication is the PS domain, and the UE sends
an RRC CONNECTION SETUP COMPLETE message to the RNC, this counter is increased
by one in the cell that the UE camps on.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ithSI.PsDomain
WRFD-140224

RIM

3136
BSC6900 UMTS
Number of Successful RRC Connection Setups for Platinum UEs Performing

Conversational Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73425916
RRC.SuccConnEstab.Conv.
Platinum

Connection Setups for
Platinum UEs Performing
Cell
Description
This counter measures the number of RRC CONNECTION SETUP COMPLETE messages
received by the RNC from platinum UEs (without differentiating between cause values).This
(v10.13.0).
Measurement point
The measurement is triggered at point C shown in the figure when the RNC receives an RRC
CONNECTION SETUP COMPLETE message from a platinum UE. In this case, this counter
Formula
None
Issue 03 (2015-06-30)

3137
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RRC.SuccConnEstab.Conv.
Platinum
WRFD-150204
Number of Successful RRC Connection Setups for Platinum UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73425917
RRC.SuccConnEstab.Platinum

Connection Setups for
Description
This counter measures the number of RRC CONNECTION SETUP COMPLETE messages
received by the RNC from platinum UEs (with the cause values "Originating Conversational
Call" and "Terminating Conversational Call").This counter complies with section "8.1.3 RRC
Measurement point
The measurement is triggered at point C in the figure when the RNC receives an RRC
CONNECTION SETUP COMPLETE message from a platinum UE and the corresponding RRC
CONNECTION REQUEST message contains the cause value "Originating Conversational
Call" or "Terminating Conversational Call." In this case, this counter is measured in the cell that
the UE camps on.
Issue 03 (2015-06-30)

3138
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RRC.SuccConnEstab.Platinum
WRFD-150204
Number of RRC Connection Setup Attempts with DRD out

Counters
Counter ID
Counter Name
Counter Description
67189400

Setup Attempts with DRD
out for Cell
Description
This counter provides the number of RRC connection requests with RNC-initiated Directed
Retry Decision (DRD) to a target cell during RRC connection setup. This counter is measured
in the source cell.This counter does not include the RRC connection setup requests in the
Measurement point
The measurement is triggered at point A as shown in the figure, if the RNC initiates the RRC
connection setup procedure with a DRD to the target cell after receiving a RRC CONNECTION
REQUEST message from the UE. In this case, this counter is measured in the source cell.This
counter does not include the RRC connection setup requests in the Directed Signalling
connection setup procedure and cell update procedure.
Issue 03 (2015-06-30)

3139
BSC6900 UMTS
Figure 1-1380 Successful DRD Procedure in RRC Procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-02040001

3140
BSC6900 UMTS
Number of RRC CONNECTION REQUESTS for CS Voice Services Under Flow

Control for Cell
Counters
Counter ID
Counter Name
Counter Description
73424228
PU.OverLoad
Number of RRC
CONNECTION
REQUESTS for CS Voice
Services Under Flow Control
Triggered by High CPU
Usage for Cell
73424229
RCQueue
Number of RRC
CONNECTION
Triggered by RRC Queue
Overflow for Cell
73424230
PU.OverLoad
Number of RRC
CONNECTION
Triggered by MPU Overload
for Cell
73424231
allShock
Number of RRC
CONNECTION
Triggered by Burst Traffic
for Cell
73424234
anFC.Ph2
Number of RRC
CONNECTION
Services Under E2E Flow
Control Phase 2 for Cell
Description
These counters provide the number of RRC CONNECTION REQUEST messages for CS
services in a cell under flow control. If the establishment cause in these requests is
UU_ORIGINATING_CONVERSATIONAL_CALL_ESTAB_CAUSE or
current service is a CS service.The preceding counters comply with section "8.1.3 RRC
Issue 03 (2015-06-30)

3141
BSC6900 UMTS
Measurement point
After a CPUS subsystem under flow control receives an RRC CONNECTION REQUEST
message from a UE, the RNC determines whether to agree to this request by calling up the flow
control algorithm. If the RNC rejects the request and the number of rejected requests does not
exceed the related threshold within the current second, the RNC sends the UE an RRC
CONNECTION REJECT message. If the number of rejected requests exceeds the threshold
within the current second, the RNC discards the request. These counters calculate all rejected
and discarded requests in a cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
PU.OverLoad
WRFD-040100
Flow Control
RCQueue
WRFD-040100
Flow Control
PU.OverLoad
WRFD-040100
Flow Control
allShock
WRFD-040100
Flow Control
anFC.Ph2
WRFD-040100
Flow Control
Number of RRC CONNECTION REQUESTS in a Cell Under Cell Dynamic CAPS

Flow Control
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424968
VS.RRC.FC.Num.CAPS
Number of RRC
CONNECTION
REQUESTS in a Cell Under
Cell Dynamic CAPS Flow
Control

3142
BSC6900 UMTS
Description
This counter provides the number of RRC connection requests during the (call attempt per
second) CAPS flow control algorithm. This algorithm considers the ratio of RRC connection
setup failures, CPU usage of the SPU subsystem, and congestion status of the NCP link.This
(v10.13.0).
Measurement point
Upon receiving an RRC Connection Request message from a UE, the RNC determines whether
to set up the RRC connection based on the flow control algorithm if dynamic CAPS flow control
is being performed in the cell. If the RRC connection is not to be set up, the RNC checks whether
the number of rejected RRC connection requests during the latest second is less than or equal
to the preset maximum number of rejected RRC connection requests. If yes, the RNC responds
the UE with an RRC Connection Reject message. If no, the RNC directly discards the RRC
Connection Request message. This counter provides the number of rejected and discarded RRC
connection requests during the dynamic CAPS flow control algorithm in the cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Num.CAPS
WRFD-040100
Flow Control
Number of RRC CONNECTION REQUESTS for CS Services in a Cell Under Cell

Dynamic CAPS Flow Control
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424969
APS
Number of RRC
CONNECTION
in a Cell Under Cell Dynamic
CAPS Flow Control

3143
BSC6900 UMTS
Description
This counter provides the number of RRC connection requests for voice services during CAPS
flow control. This algorithm considers the ratio of RRC connection setup failures, CPU usage
of the SPU subsystem, and congestion status of the NCP link. If the cause of an RRC connection
request is "Originating Conversational Call" or "Terminating Conversational Call", the RNC
determines that the request is originated by a voice service.This counter complies with section
Measurement point
Upon receiving an RRC Connection Request message from a UE, the RNC determines whether
to set up the RRC connection based on the flow control algorithm if dynamic CAPS flow control
is being performed in the cell. If the RRC connection is not to be set up, the RNC checks whether
the number of rejected RRC connection requests during the latest second is less than or equal
to the preset maximum number of rejected RRC connection requests. If yes, the RNC responds
the UE with an RRC Connection Reject message. If no, the RNC directly discards the RRC
Connection Request message. This counter provides the number of rejected and discarded RRC
connection requests for voice services during dynamic CAPS flow control in the cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
APS
WRFD-040100
Flow Control
Number of Rejected RRC Connection Setup Requests for CS Voice Services During
Flow Control Caused by Interface-Board CPU Overload for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424691
NT.OverLoad
Number of RRC
CONNECTION
Triggered by Interface-Board
CPU Overload for Cell

3144
BSC6900 UMTS
Description
requests for CS Voice services during flow control caused by interface-board central processing
unit (CPU) overload in a cell. If the cause value contained in an RRC CONNECTION REQUEST
message is Originating Conversational Call or Terminating Conversational Call, the RRC
connection is set up for a CS Voice service.This counter complies with section "8.1.3 RRC
Measurement point
requests for CS Voice services during flow control caused by interface-board central processing
unit (CPU) overload in a cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
NT.OverLoad
WRFD-040100
Flow Control
Number of Rejected RRC Connection Setup Requests During Flow Control Caused
by Interface-Board CPU Overload for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424692
VS.RRC.FC.Num.INT.Over
Load
Number of RRC
CONNECTION
REQUESTS Under Flow
Interface-Board CPU
Overload for Cell

3145
BSC6900 UMTS
Description
requests during flow control caused by interface-board central processing unit (CPU) overload
in a cell.This counter complies with section "8.1.3 RRC connection establishment" in 3GPP TS
25.331 (v10.13.0).
Measurement point
requests during flow control caused by interface-board central processing unit (CPU) overload
in a cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Num.INT.Over
Load
WRFD-040100
Flow Control
Number of Rejected RRC Connection Setup Requests During Flow Control Caused
by FACH Congestion for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424693
VS.RRC.FC.Num.FACH.C
ong
Number of RRC
CONNECTION
REQUESTS Under Flow
Control Triggered by FACH
Congestion for Cell

3146
BSC6900 UMTS
Description
requests during flow control caused by FACH congestion in a cell.This counter complies with
Measurement point
The measurement is triggered when a CPUS receives an RRC CONNECTION REQUEST
message from a UE and the MAC-c discards the message due to severe FACH congestion. This
counter measures the number of rejected radio resource control (RRC) connection setup requests
during flow control caused by FACH CCCH congestion in a cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Num.FACH.C
ong
WRFD-040100
Flow Control
Number of Rejected RRC Connection Setup Requests for CS Voice Services During
E2E Flow Control Phase 1 for Cell
Counters
Counter ID
Counter Name
Counter Description
73424694
anFC.Ph1
Number of RRC
CONNECTION
Services Under E2E Flow
Control Phase 1 for Cell
Description
requests for CS Voice services during E2E flow control phase 1 in a cell. If the cause value
contained in an RRC CONNECTION SETUP REQUEST message is Originating
Conversational Call or Terminating Conversational Call, the RRC connection is set up for a CS
Issue 03 (2015-06-30)

3147
BSC6900 UMTS
Voice service.This counter complies with section "8.1.3 RRC connection establishment" in
3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered when a central processing unit subsystem (CPUS) receives an
RRC CONNECTION REQUEST message from a UE and a RADIO LINK SETUP FAILURE
message with the cause value of Control processing overload from the NodeB. This counter
measures the number of rejected radio resource control (RRC) connection setup requests for CS
Voice services during E2E flow control phase 1 in a cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
anFC.Ph1
WRFD-040100
Flow Control
Number of Rejected RRC Connection Setup Requests During E2E Flow Control
Phase 1 for Cell
Counters
Counter ID
Counter Name
Counter Description
73424695
VS.RRC.FC.Num.RanFC.P
h1
Number of RRC
CONNECTION
REQUESTS Under E2E
Flow Control Phase 1 for Cell
Description
requests during E2E flow control phase 1 in a cell.This counter complies with section "8.1.3
Measurement point
The measurement is triggered when a central processing unit subsystem (CPUS) receives an
RRC CONNECTION REQUEST message from a UE and a RADIO LINK SETUP FAILURE
Issue 03 (2015-06-30)

3148
BSC6900 UMTS
message with the cause value of NodeB CPU overload from the NodeB. This counter measures
the number of rejected radio resource control (RRC) connection setup requests during E2E flow
control phase 1 in a cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
h1
WRFD-040100
Flow Control
Number of Automatic DSACs Triggered by Congestion on Iu Interface

Counters
Counter ID
Counter Name
Counter Description
67195590
VS.RRC.AutoDsac.Num
Number of Automatic
DSACs Triggered by
Congestion on Iu Interface
for Cell
Description
When RANAP OVERLOAD occurs in the CN, the automatic DSAC is triggered in the scope
of the RNC. This counter provides the number of triggered automatic DSACs in the cell.This
(v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC receives an
RANAP OVERLOAD message from the CN, the automatic DSAC is triggered in the cell. The
number of triggered automatic DSACs is measured in the cell.
Issue 03 (2015-06-30)

3149
BSC6900 UMTS
Figure 1-1381 Automatic domain-based access control triggered by core network overload
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.AutoDsac.Num
WRFD-020114
Domain Specific Access

Control (DSAC)
Number of PTT UEs with RRC Connection State of CELL_FACH

Counters
Counter ID
Counter Name
Counter Description
73410489
VS.CellFACHUEs.PTT
Number of PTT UEs in Cell

with RRC Connection State
of CELL_FACH
Description
This counter provides the average number of PTT UEs with RRC Connection State of
CELL_FACH in the cell.This counter complies with section "8.1.3 RRC connection
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of number of PTT
UEs with RRC Connection State of CELL_FACH. At the end of the measurement period, by
Issue 03 (2015-06-30)

3150
BSC6900 UMTS
dividing the accumulated value of sample data in the period by the number of samples, the
average number of PTT UEs carried on the CELL_FACH in the measurement period is obtained.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CellFACHUEs.PTT
WRFD-020134
Push to Talk
Number of PTT UEs with RRC Connection State of CELL_DCH

Counters
Counter ID
Counter Name
Counter Description
73410490
VS.CellDCHUEs.PTT
Number of PTT UEs in Cell

with RRC Connection State
of CELL_DCH
Description
This counter provides the average number of PTT UEs with RRC Connection State of
CELL_DCH in the cell.This counter complies with section "8.1.3 RRC connection
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of number of PTT
UEs with RRC Connection State of CELL_DCH. At the end of the measurement period, by
dividing the accumulated value of sample data in the period by the number of samples, the
average number of PTT UEs carried on the CELL_DCH in the measurement period is obtained.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3151
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CellDCHUEs.PTT
WRFD-020134
Push to Talk
Number of PTT UEs in CELL_PCH State

Counters
Counter ID
Counter Name
Counter Description
73410505
VS.CellPCHUEs.PTT
Number of PTT UEs with

RRC Connection State of
CELL_PCH for Cell
Description
This counter provides the average number of PTT UEs with RRC connection state of
CELL_PCH in the Cell.This counter complies with section "8.1.3 RRC connection
Measurement point
The system periodically takes samples of the number of PTT UEs in the RRC connection state
of CELL_PCH every five seconds. At the end of the measurement period, the value of this
counter is obtained by dividing the accumulated value of UE number by the number of sampling
times.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CellPCHUEs.PTT
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-020134
Push to Talk
Issue 03 (2015-06-30)

3152
BSC6900 UMTS
Number of RRC CONNECTION REQUESTS Under Flow Control for Cell

Counters
Counter ID
Counter Name
Counter Description
73424224
VS.RRC.FC.Num.CPU.Ove
rLoad
Number of RRC
CONNECTION
REQUESTS Under Flow
Control Triggered by High
CPU Usage for Cell
73424225
ue
Number of RRC
CONNECTION
REQUESTS Under Flow
Control Triggered by RRC
Queue Overflow for Cell
73424226
VS.RRC.FC.Num.MPU.Ov
erLoad
Number of RRC
CONNECTION
REQUESTS Under Flow
Control Triggered by MPU
Overload for Cell
73424227
VS.RRC.FC.Num.CallShock
Number of RRC
CONNECTION
REQUESTS Under Flow
Control Triggered by Burst
Traffic for Cell
73424233
h2
Number of RRC
CONNECTION
REQUESTS Under E2E
Flow Control Phase 2 for Cell
Description
These counters provide the number of RRC CONNECTION REQUEST messages in a Cell
under flow control.The preceding counters comply with section "8.1.3 RRC connection
Measurement point
After a CPUS subsystem under flow control receives an RRC CONNECTION REQUEST
message from a UE, the RNC determines whether to agree to this request by calling up the flow
control algorithm. If the RNC rejects the request and the number of rejected requests does not
exceed the related threshold within the current second, the RNC sends the UE an RRC
CONNECTION REJECT message. If the number of rejected requests exceeds the threshold
within the current second, the RNC discards the request. These counters calculate all rejected
and discarded requests in a cell.
Issue 03 (2015-06-30)

3153
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Num.CPU.Ove
rLoad
WRFD-040100
Flow Control
ue
WRFD-040100
Flow Control
VS.RRC.FC.Num.MPU.Ov
erLoad
WRFD-040100
Flow Control
WRFD-040100
Flow Control
h2
WRFD-040100
Flow Control
Number of Cell Updates Under Flow Control Triggered by High CPU Usage for
Cell
Counters
Counter ID
Counter Name
Counter Description
73424232
VS.CU.FC.Num.CPU.OverLoad
Number of Cell Updates

Under Flow Control
Triggered by High CPU
Usage for Cell
Description
This counter provides the number of cell updates in a cell under flow control triggered by CPU
usage. The flow control is performed on UEs that are in the CELL_PCH or URA_PCH state and
require cell or URA updates.This counter complies with section "8.1.3 RRC connection
Measurement point
This counter is increased by one when either of the following conditions is met:
Issue 03 (2015-06-30)

3154
BSC6900 UMTS
(1)The RNC receives a cell update message from a UE in the CELL_PCH or URA_PCH state,
and the cell is under flow control triggered by CPU usage.
(2)The RNC receives a URA update message from a UE in the URA_PCH state, and the cell is
under flow control triggered by CPU usage.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.CU.FC.Num.CPU.OverLoad
WRFD-040100
Flow Control
Number of RRC Connection Setup Requests for CSFB for Cell

Counters
Counter ID
Counter Name
Counter Description
73426415
VS.RRC.AttConnEstab.CSF
B

Setup Requests for CSFB for
Cell
Description
This counter provides the number of RRC CONNECTION REQUEST messages sent by UEs
during circuit switched fallback (CSFB) in a cell. This counter together with the
VS.RRC.SuccConnEstab.CSFB counter is used to evaluate the RRC connection setup success
rate of UEs during CSFB on the UMTS network.This counter complies with section "8.1.3 RRC
Measurement point
The measurement is triggered at point A in the following figure. When the RNC receives an
RRC CONNECTION REQUEST message from a UE, the RNC determines that the UE is
performing CSFB. Under this circumstance, this counter is increased by one. At the end of the
measurement period, the value of this counter is obtained.
Issue 03 (2015-06-30)

3155
BSC6900 UMTS
is Paging Response.
Figure 1-1382 Successful RRC connection setup procedure
Formula
None
Unit
None
Related Features
None
Issue 03 (2015-06-30)

3156
BSC6900 UMTS
Number of Successful RRC Connection Setups for CSFB for Cell

Counters
Counter ID
Counter Name
Counter Description
73426416
SFB

Connection Setups for CSFB
for Cell
Description
This counter provides the number of successful RRC connection setups initiated by UEs during
CSFB in a cell. This counter together with the VS.RRC.AttConnEstab.CSFB counter is used to
evaluate the RRC connection setup success rate of UEs during CSFB on the UMTS network.This
(v10.13.0).
Measurement point
The measurement is triggered at point C in the following figure. When the RNC receives an
RRC CONNECTION REQUEST message from a UE, the RNC determines that the UE is
performing CSFB. Subsequently, if the RNC receives an RRC CONNECTION SETUP
COMPLETE message from the UE, the RRC connection setup is successful, and this counter is
increased by one. At the end of the measurement period, the value of this counter is obtained.
is Paging Response.
Issue 03 (2015-06-30)

3157
BSC6900 UMTS
Figure 1-1383 Successful RRC connection setup procedure
Formula
None
Unit
None
Related Features
None
1.12.43 RRC Connection Reject Measurement <per Cell>

(RRC.SetupFail.Cell)
Overview
This function subset measures the number of RRC connection setup rejections in a cell based
on different causes.The counter of RRC connection setup attempts and rejects does not include
service-based redirections, inter-RAT and inter-frequency distance-based redirections,
weakcoverage-based redirections, macro & micro joint inter-frequency redirections and the
number of RRC connection requests discarded during flow control.
Issue 03 (2015-06-30)

3158
BSC6900 UMTS
Issue 03 (2015-06-30)

3159
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
A~E
See:RRC.Setup.Cell,
VS.RRC.Rej.Redir.PingPongNum
VS.RRC.FailConnEstab.NoReply,
VS.RRC.FailConnEstab.NoReply.CSFB
VS.RRC.FC.Disc.Num,
VS.LowPriRRC.RanFC.Disc.Num,
VS.NormPriRRC.RanFC.Disc.Num,
VS.HighPriRRC.RanFC.Disc.Num
VS.RRC.Rej.Redir.Service,
VS.RRC.Rej.Redir.Dist,
VS.RRC.Rej.Redir.Dist.IntraRat,
VS.RRC.Rej.Redir.CoMacroMicro,
VS.RRC.Rej.Redir.WeakCoverage
VS.RRC.Rej.ULPower.Cong,
VS.RRC.Rej.DLPower.Cong,
VS.RRC.FailConnEstab.Cong,
VS.RRC.Rej.ULIUBBand.Cong,
VS.RRC.Rej.DLIUBBand.Cong,
VS.RRC.Rej.ULCE.Cong,
VS.RRC.Rej.DLCE.Cong,
VS.RRC.Rej.Code.Cong,
VS.RRC.Rej.NodeBULCE.Cong,
VS.RRC.Rej.NodeBDLCE.Cong
VS.RRC.Rej.RL.Fail, VS.RRC.Rej.NodeBResUnavail
VS.RRC.Rej.TNL.Fail
VS.RRC.Rej.Redir.InterRat,
VS.RRC.Rej.Redir.IntraRat,
VS.RRC.Rej.Redir.IntraRat.CSService,
VS.RRC.Rej.Redir.IntraRat.PSService,
VS.RRC.Rej.Redir.InterRat.CSService,
VS.RRC.Rej.Redir.InterRat.PSService
VS.RRC.Rej.Sum, and other counters, refer

to RRC.Setup.Cell

3160
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193609
VS.RRC.Rej.ULPo
wer.Cong
Number of RRC
Connection Rejects
for Cell (UL Power
Congestion)
BSC6900
V900R012
67193610
VS.RRC.Rej.DLPo
wer.Cong
Number of RRC
Connection Rejects
for Cell (DL Power
Congestion)
BSC6900
V900R012
67189473
VS.RRC.Rej.Redir.
IntraRat
Number of RRC
Connection Rejects
during redirection
between interfrequency cells for
cell
Earlier than
BSC6900
V900R011
67189474
VS.RRC.Rej.Redir.
InterRat
Number of RRC
Connection Rejects
during redirection
between inter-RAT
cells for cell
Earlier than
BSC6900
V900R011
67196031
VS.RRC.Rej.Redir.
Service
Number of RRC
Connection Rejects
Due to Service-based
RRC Redirection for
Cell
Earlier than
BSC6900
V900R011
67179521
VS.RRC.FailConn
Estab.Cong
Number of RRC
Connection Rejects
Due to Network
Congestion for Cell
Earlier than
BSC6900
V900R011
67192608
VS.RRC.Rej.ULIU
BBand.Cong
Number of RRC
Connection Rejects
for Cell (UL Iub
Bandwidth
Congestion)
Earlier than
BSC6900
V900R011
67192609
VS.RRC.Rej.DLIU
BBand.Cong
Number of RRC
Connection Rejects
for Cell (DL Iub
Bandwidth
Congestion)
Earlier than
BSC6900
V900R011

3161
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190401
VS.RRC.FailConn
Estab.NoReply
Number of RRC
Connection Rejects
Due to Timeout of
RRC CONNECT
SETUP
COMPLETE for Cell
Earlier than
BSC6900
V900R011
67190404
VS.RRC.Rej.ULC
E.Cong
Number of RRC
Connection Rejects
for Cell (UL CE
Resource
Congestion)
Earlier than
BSC6900
V900R011
67190405
VS.RRC.Rej.DLC
E.Cong
Number of RRC
Connection Rejects
for Cell (DL CE
Resource
Congestion)
Earlier than
BSC6900
V900R011
67179524
VS.RRC.Rej.Code.
Cong
Number of RRC
Connection Rejects
for Cell (Code
Resource
Congestion)
Earlier than
BSC6900
V900R011
67179525
VS.RRC.Rej.RL.F
ail
Number of RRC
Connection Rejects
Due to Radio Link
Setup Failure for Cell
Earlier than
BSC6900
V900R011
67179527
VS.RRC.Rej.TNL.
Fail
Number of RRC
Connection Rejects
for Cell
(Transmission Setup
Failure on Iub
Interface )
Earlier than
BSC6900
V900R011
67179300
VS.RRC.Rej.Sum
Number of RRC
Connection Rejects
for Cell
Earlier than
BSC6900
V900R011
73421493
VS.RRC.Rej.Redir.
Dist
Number of DistanceBased RRC

BSC6900
V900R012

3162
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423468
VS.RRC.FC.Disc.N
um
Number of
Discarded RRC
Connection Requests
Due to Various Flow
Control Functions
for Cell
BSC6900
V900R013
73393776
VS.LowPriRRC.Ra
nFC.Disc.Num
Number of LowPriority RRC

Connection Setup
Requests Discarded
During RAN
Integrated Flow
Control for Cell
BSC6900
V900R013
73393777
VS.NormPriRRC.
RanFC.Disc.Num
Number of MiddlePriority RRC

Connection Setup
Requests Discarded
During RAN
Integrated Flow
Control for Cell
BSC6900
V900R013
73393778
VS.HighPriRRC.R
anFC.Disc.Num
Number of HighPriority RRC

Connection Setup
Requests Discarded
During RAN
Integrated Flow
Control for Cell
BSC6900
V900R013
73424972
VS.RRC.Rej.Redir.
Dist.IntraRat
Number of DistanceBased RRC Interfrequency

BSC6900
V900R014
73425032
VS.RRC.Rej.NodeBResUnavail
Number of RRC
Connection Rejects
Due to NodeB
Resource
Unavailable
BSC6900
V900R014
73425833
VS.RRC.Rej.Redir.
CoMacroMicro
Number of Outgoing
Macro & Micro Joint
Inter-frequency
Redirections
BSC6900
V900R015C00

3163
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426860
VS.RRC.Rej.Redir.
PingPongNum
Number of RRC
Connection Requests
Initiated to Access
the Same Cell Within
20s After an RRC
Redirection
BSC6900
V900R015C01
73428174
VS.RRC.Rej.Node
BULCE.Cong
Number of RRC
Connection Request
Rejected due to
NodeB UL CE
Congestion for Cell
BSC6900
V900R016C00
73428175
VS.RRC.Rej.Node
BDLCE.Cong
Number of RRC
Connection Request
Rejected due to
NodeB DL CE
Congestion for Cell
BSC6900
V900R016C00
73428218
VS.RRC.Rej.Redir.
WeakCoverage
Number of Outgoing
Inter-RAT
Redirections based
on Weak Coverage
for Cell
BSC6900
V900R016C00
73428676
VS.RRC.FailConn
Estab.NoReply.CS
FB
Number of Failed CS
RAB Establishments
for CSFB UEs for
Cell (RRC
Connection Setup
Timeout)
BSC6900
V900R016C00
73429104
VS.RRC.Rej.Redir.
IntraRat.CSService
Number of
Admission Failure
based Interfrequency RRC
(CS Service)
BSC6900
V900R017C00
73429105
VS.RRC.Rej.Redir.
IntraRat.PSService
Number of
Admission Failure
based Interfrequency RRC
(PS Service)
BSC6900
V900R017C00

3164
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73429106
VS.RRC.Rej.Redir.
InterRat.CSService
Number of
Admission Failure
based Inter-RAT
RRC Redirections
for Cell (CS Service)
BSC6900
V900R017C00
73429107
VS.RRC.Rej.Redir.
InterRat.PSService
Number of
Admission Failure
based Inter-RAT
RRC Redirections
for Cell (PS Service)
BSC6900
V900R017C00
73430234
VS.RRC.Rej.Redir.
UECapab.IntraRat
Number of Outgoing
Inter-frequency
Redirections based
on Terminal
Capability for Cell
BSC6900
V900R017C10
73430680
VS.RRC.Rej.DistLimit
Number of RRC
Connection Rejects
Due to Distancebased Access
Control for Cell
BSC6900
V900R017C10
Counter
Sub Counter
VS.RRC.FailConnEstab.Cong
VS.RRC.Rej.ULPower.Cong
VS.RRC.Rej.DLPower.Cong
VS.RRC.Rej.ULIUBBand.Cong
VS.RRC.Rej.DLIUBBand.Cong
VS.RRC.Rej.ULCE.Cong
VS.RRC.Rej.DLCE.Cong
VS.RRC.Rej.Code.Cong
VS.RRC.Rej.Sum
VS.RRC.FailConnEstab.Cong
VS.RRC.Rej.RL.Fail
VS.RRC.Rej.TNL.Fail
Issue 03 (2015-06-30)
VS.RRC.Rej.NodeBULCE.Cong

3165
BSC6900 UMTS
Counter
Sub Counter
VS.RRC.Rej.NodeBDLCE.Cong
VS.RRC.Rej.Redir.InterRat
VS.RRC.Rej.Redir.InterRat.CSService
VS.RRC.Rej.Redir.IntraRat
VS.RRC.Rej.Redir.IntraRat.CSService
VS.RRC.Rej.Redir.IntraRat.PSService
Number of RRC Connection Requests Initiated to Access the Same Cell Within 20s
After an RRC Redirection
Counters
Counter ID
Counter Name
Counter Description
73426860

Requests Initiated to Access
the Same Cell Within 20s
After an RRC Redirection
Description
This counter measures the number of RRC connection requests initiated by UEs to access the
same cell within 20s after an RRC redirection.This counter complies with section "8.1.3 RRC
Measurement point
CONNECTION REQUEST message from a UE and determines that an RRC redirection is
required. The RNC sends an RRC CONNECTION REJECT message to the UE, rejecting the
UE's access to a cell. If the UE sends another RRC CONNECTION REQUEST message to the
RNC within 20s, requesting access to same cell, this counter is increased by one. At the end of
the measurement period, the RNC obtains the accumulated value of this counter.
Issue 03 (2015-06-30)

3166
BSC6900 UMTS
Figure 1-1385 Measurement point for ping-pong RRC redirections
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-020120

Sharing in RRC Connection
Setup
WRFD-02040005
WRFD-150201
WRFD-02040003
Inter-Frequency Redirection
Based on Distance
Inter System Redirect
Issue 03 (2015-06-30)

3167
BSC6900 UMTS
Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP

COMPLETE
Counters
Counter ID
Counter Name
Counter Description
67190401
VS.RRC.FailConnEstab.No
Reply

Rejects Due to Timeout of
RRC CONNECT SETUP
COMPLETE for Cell
73428676
Reply.CSFB

UEs for Cell (RRC
Connection Setup Timeout)
Description
This counter provides the number of RRC CONNECT SETUP COMPLETE messages that the
RNC fails to receive from the UE before the timer expires after the RNC sends a RRC CONNECT
SETUP message to the UE.The preceding counters comply with section "8.1.3 RRC connection
Measurement point
The measurement is triggered at point A as shown in the figure, if the RNC fails to receive a
RRC CONNECT SETUP COMPLETE message from the UE before the timer expires after the
RNC sends the RRC CONNECT SETUP message to the UE. In this case, this counter is
measured in the cell where the UE is located.
Issue 03 (2015-06-30)

3168
BSC6900 UMTS
Figure 1-1386 Timeout of RRC connection setup completion
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Reply
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Reply.CSFB
WRFD-140224

RIM
WRFD-140102

LTE Emergency Calls
Issue 03 (2015-06-30)

3169
BSC6900 UMTS
Number of Discarded RRC Connection Requests Due to Various Flow Control

Functions
Counters
Counter ID
Counter Name
Counter Description
73423468
VS.RRC.FC.Disc.Num

Various Flow Control
Functions for Cell
Description
This counter provides the number of RRC connection requests discarded by various flow control
functions such as CPU usage, MPU overload, RRC queuing, RAN integrated flow control, cell
dynamic CAPS flow control in a cell.This counter complies with section "8.1.3 RRC connection
Measurement point
The measurement is triggered when an RRC connection request is discarded in a cell. This
counter measures only the discarded requests but does not measure the rejection messages sent
due to flow control.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.FC.Disc.Num
WRFD-040100
Flow Control

3170
BSC6900 UMTS
Number of RRC Connection Requests of Different Priorities Discarded During

RAN Integrated Flow Control for Cell
Counters
Counter ID
Counter Name
Counter Description
73393776
VS.LowPriRRC.RanFC.Dis
c.Num
Requests Discarded During
RAN Integrated Flow
Control for Cell
73393777
VS.NormPriRRC.RanFC.Di
sc.Num
Number of Middle-Priority
RAN Integrated Flow
Control for Cell
73393778
VS.HighPriRRC.RanFC.Dis
c.Num
RAN Integrated Flow
Control for Cell
Description
These counters provide the number of RRC connection requests of different priorities discarded
in a cell in phase 2 of RAN integrated flow control. In this phase, the RNC performs RAN
integrated flow control based on NodeB-reported CPU load information.The preceding counters
comply with section "8.1.3 RRC connection establishment" in 3GPP TS 25.331 (v10.13.0).
Measurement point
After receiving an RRC CONNECTION REQUEST message from a UE, the RNC determines
whether to set up the RRC connection based on the flow control algorithm if RAN integrated
flow control is being performed in the cell.
If the RNC determines that the RRC connection will not be set up, the subsequent procedure is
as follows:
If the current number of RRC connection rejections does not exceed the configured RRC
REJECT message.
Otherwise, the RNC discards the RRC CONNECTION REQUEST message directly and
measures the number of discarded RRC connection requests.
Formula
None
Issue 03 (2015-06-30)

3171
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LowPriRRC.RanFC.Dis
c.Num
WRFD-040100
Flow Control
VS.NormPriRRC.RanFC.Di
sc.Num
WRFD-040100
Flow Control
VS.HighPriRRC.RanFC.Dis
c.Num
WRFD-040100
Flow Control
Number of RRC Connection Rejects Due to Service-based RRC Redirection

Counters
Counter ID
Counter Name
Counter Description
67196031
VS.RRC.Rej.Redir.Service

Rejects Due to Service-based
RRC Redirection for Cell
Description
This counter provides the number of RRC connection rejects due to service-based redirection
in the cell. VS.RRC.Rej.Redir.IntraRat and VS.RRC.Rej.Redir.InterRat are not measured when
the rejection is caused by service-based redirection.This counter complies with section "8.1.3
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC fails to set up
the RRC connection for the UE and sends to the UE a RRC CONNECTION REJECT message
with redirection information. In this case, this counter is measured in the cell where the UE is
located.
Issue 03 (2015-06-30)

3172
BSC6900 UMTS
Figure 1-1387 Service-based RRC redirection
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.Redir.Service
WRFD-020120

Sharing in RRC Connection
Setup
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Issue 03 (2015-06-30)

3173
BSC6900 UMTS
Number of Distance-Based RRC Redirections for Cell

Counters
Counter ID
Counter Name
Counter Description
73421493
VS.RRC.Rej.Redir.Dist
Number of Distance-Based
RRC Redirections for Cell
73424972
VS.RRC.Rej.Redir.Dist.IntraRat
Number of Distance-Based
RRC Inter-frequency
Description
These counters provide the number of RRC connection rejects due to distance-based redirection
in the cell. The VS.RRC.Rej.Redir.Dist counter provides the number of inter-RAT redirections
and inter-frequency redirections. The VS.RRC.Rej.Redir.Dist.IntraRat counter provides only
the number of inter-RAT redirections. VS.RRC.Rej.Redir.IntraRat and
VS.RRC.Rej.Redir.InterRat are not measured when the rejection is triggered by distance-based
redirection.The preceding counters comply with section "8.1.3 RRC connection establishment"
in 3GPP TS 25.331 (v10.13.0).
Measurement point
As shown by A in Figure 1, when the RNC determines that a distance-based inter-RAT or interfrequency redirection needs to be performed and the RNC sends the UE an RRC CONNECTION
REJECT message that carries redirection information,this counter is increased by one in the cell
where the UE is camping.
Figure 1-1388 Distance-Based RRC redirection
Issue 03 (2015-06-30)

3174
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.Redir.Dist
WRFD-02040003
WRFD-02040005
Based on Distance
WRFD-020401
Inter-RAT Redirection
Based on Distance
VS.RRC.Rej.Redir.Dist.IntraRat
WRFD-02040005
Based on Distance
Number of Outgoing Macro & Micro Joint Inter-frequency Redirections

Counters
Counter ID
Counter Name
Counter Description
73425833
VS.RRC.Rej.Redir.CoMacroMicro
Number of Outgoing Macro

& Micro Joint Interfrequency Redirections
Description
This counter provides the number of outgoing macro & micro joint inter-frequency
redirections.This counter complies with section "8.1.3 RRC connection establishment" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
area.
Issue 03 (2015-06-30)

3175
BSC6900 UMTS
macro & micro joint inter-frequency handover area and triggers a macro & micro joint interfrequency redirection. This counter is increased by one in the serving cell where the UE camps
each time the RNC sends an RRC CONNECTION REJECT message to the UE.
Figure 1-1390 Macro and micro joint inter-frequency RRC redirection
Formula
None
Unit
None
Issue 03 (2015-06-30)

3176
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.Redir.CoMacroMicro
WRFD-150201

WRFD-15020101
Macro & Micro Joint Interfrequency Redirection
Number of Outgoing Inter-RAT Redirections based on Weak Coverage for Cell

Counters
Counter ID
Counter Name
Counter Description
73428218
Number of Outgoing InterRAT Redirections based on

Weak Coverage for Cell
Description
This counter measures the number of times that the RNC sends an RRC CONNECTION
REJECT message to trigger a weak-coverage-based inter-RAT redirection in a cell. When this
counter is measured, VS.RRC.Rej.Redir.InterRat is not measured.This counter complies with
Measurement point
The measurement is triggered at point A in the figure. When a UE in weak coverage areas sends
an RRC CONNECTION REQUEST message to the RNC, the RNC returns an RRC
CONNECTION REJECT message to the UE if the conditions of weak-coverage-based interRAT redirection are met. The RRC CONNECTION REJECT message carries the redirection
information. This counter is measured in the cell where the UE camps.
Figure 1-1391 Weak-coverage-based redirection procedure
Issue 03 (2015-06-30)

3177
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-02040003
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Rejects Due to Congestion

Counters
Counter ID
Counter Name
Counter Description
67179521
VS.RRC.FailConnEstab.Co
ng

Rejects Due to Network
Congestion for Cell
Description
This counter provides the number of RRC CONNECTION REJECT messages sent by the RNC
to the UE due to network congestion after the RNC receives a RRC CONNECTION REQUEST
message from the UE.
This counter complies with section "8.1.3 RRC connection establishment" in 3GPP TS 25.331
(v10.13.0).
Remark: When the RRC connection is rejected by flow control, the following counters will be
added to this counter. When the RRC connection is discarded by flow control, the following
counters will not be added to this counter.
VS.RRC.FC.Num.CPU.OverLoad
VS.RRC.FC.Num.MPU.OverLoad
VS.RRC.FC.Num.RRCQueue
Issue 03 (2015-06-30)

3178
BSC6900 UMTS
VS.RRC.FC.Num.RanFC.Ph1
VS.RRC.FC.Num.RanFC.Ph2
VS.RRC.FC.Num.CAPS
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RRC
CONNECTION REJECT message to the UE with the reject cause of congestion.
Figure 1-1392 Procedure for RRC connection rejects
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.FailConnEstab.Co
ng
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3179
BSC6900 UMTS
Number of RRC Connection Rejects (Radio Resource Congestion)

Counters
Counter ID
Counter Name
Counter Description
67192608
VS.RRC.Rej.ULIUBBand.C
ong

Rejects for Cell (UL Iub
Bandwidth Congestion)
67193609
VS.RRC.Rej.ULPower.Con
g

Rejects for Cell (UL Power
Congestion)
67193610
VS.RRC.Rej.DLPower.Con
g

Rejects for Cell (DL Power
Congestion)
67192609
VS.RRC.Rej.DLIUBBand.C
ong

Rejects for Cell (DL Iub
Bandwidth Congestion)
67190404

Rejects for Cell (UL CE
Resource Congestion)
67190405

Rejects for Cell (DL CE
67179524

Rejects for Cell (Code
Description
These counters provide the numbers of RRC CONNECTION REJECT messages sent by the
RNC to the UE according to different congestion reasons in the cell.If congestion occurs on both
the uplink and downlink, only the related downlink counter is measured. For example, if an RRC
connection setup attempt is rejected due to the congestion on both the uplink and downlink, only
the counter VS.RRC.Rej.DLPower.Cong is measured. For example, if an RRC connection setup
attempts is rejected due to congestion in Iub uplink and downlink bandwidth (admission
bandwidth), the RNC measures only the VS.RRC.Rej.DLIUBBand.Cong counter.The preceding
counters comply with section "8.1.3 RRC connection establishment" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure. After receiving a RRC
CONNECTION REQUEST message from the UE, the RNC initiates admission procedures for
resources of code, power, CE, and Iub bandwidth. If the resource admission fails, the RNC sends
Issue 03 (2015-06-30)

3180
BSC6900 UMTS
a RRC CONNECTION REJECT message to the UE. In this case, the corresponding counter is
measured according to the reject reason in the cell where the UE is located.
Figure 1-1393 RRC resource admission failure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.ULIUBBand.C
ong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.Rej.ULPower.Con
g
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.Rej.DLPower.Con
g
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3181
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.DLIUBBand.C
ong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Requests Rejected due to NodeB CE Congestion for

Cell
Counters
Counter ID
Counter Name
Counter Description
73428174
VS.RRC.Rej.NodeBULCE.
Cong

Request Rejected due to
NodeB UL CE Congestion
for Cell
73428175
VS.RRC.Rej.NodeBDLCE.
Cong

Request Rejected due to
NodeB DL CE Congestion
for Cell
Description
This counter measures the number of RRC connection setup requests that are rejected due to
NodeB uplink or downlink CE congestion in a cell.The preceding counters comply with section
Issue 03 (2015-06-30)

3182
BSC6900 UMTS
Measurement point
The measurement is triggered at point B in figure 1. When the RNC receives an RRC
CONNECTION REQUEST message from a UE and triggers an RL establishment procedure, if
the RNC receives the NodeB a RADIO LINK SETUP FAILURE message with a cause value
indicating uplink or downlink CE congestion from the NodeB, it returns an RRC CONNECTION
REJECT message to the UE with the cause value "Congestion".The cause values indicating
uplink CE congestion are "UL_RADIO_RESOURCES_NOT_AVAILABLE" and
"CELL_SYN_NOT_SUPP". The cause values indicating downlink CE congestion are
These counters are separately measured in the uplink and downlink of the cell where the UE
camps.
Figure 1-1394 RRC connection request rejection procedure (due to NodeB CE congestion)
Formula
None
Unit
None
Issue 03 (2015-06-30)

3183
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.NodeBULCE.
Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.RRC.Rej.NodeBDLCE.
Cong
WRFD-020101
Admission Control
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Rejects Due to Radio Link Setup Failure

Counters
Counter ID
Counter Name
Counter Description
67179525
VS.RRC.Rej.RL.Fail

Rejects Due to Radio Link
Setup Failure for Cell
Description
to the UE due to RL setup failures on the Iub interface after the RNC receives an RRC
CONNECTION REQUEST message from the UE. Note that if the NodeB responds with a radio
link configuration failure message with the cause of CE resource insufficiency, this counter is
not measured. This counter is also not measured if phase 1 of E2E flow control is enabled and
the cause value contained in the RADIO LINK SETUP FAIL message responded by the NodeB
is "Control processing overload" or "NodeB Resources Unavailable". The mapped value of the
two causes in the RRC CONNECTION REJECT message is congestion.This counter complies
with section "8.1.3 RRC connection establishment" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement can be triggered at point B as shown in the figure. When the RNC receives a
RRC CONNECTION REQUEST message from the UE, the RNC starts a radio link setup
procedure. After receiving a RADIO LINK SETUP FAIL message from the NodeB, the RNC
sends a RRC CONNECTION REJECT message to the UE. In this case, this counter is measured
in the cell where the UE is located.
Issue 03 (2015-06-30)

3184
BSC6900 UMTS
Figure 1-1395 Radio link setup failure
The measurement can be also triggered at point B as shown in the figure. When the RNC receives
a RRC CONNECTION REQUEST message from the UE, the RNC starts a radio link setup
procedure. If the RNC fails to receive a RADIO LINK SETUP RESPONSE message from the
NodeB before the timer expires, the RNC sends a RRC CONNECTION REJECT to the UE. In
this case, this counter is measured in the cell where the UE is located.
Figure 1-1396 Radio link setup timeout
Issue 03 (2015-06-30)

3185
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.RL.Fail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Rejects Due to NodeB Resource Unavailable

Counters
Counter ID
Counter Name
Counter Description
73425032

Rejects Due to NodeB
Resource Unavailable
Description
to the UE due to RL setup failures on the Iub interface after the RNC receives an RRC
CONNECTION REQUEST message from the UE. Note that in this counter, the cause value for
RL setup failures is "NodeB Resources Unavailable" and the cause value for the RRC
CONNECTION REJECT message is congestion.This counter complies with section "8.1.3 RRC
Measurement point
The measurement is triggered at point B shown in the following figure. When the RNC receives
a RRC CONNECTION REQUEST message from the UE, the RNC starts a radio link setup
procedure. After receiving a RADIO LINK SETUP FAIL message with the cause of NodeB
Resources Unavailable from the NodeB, the RNC sends a RRC CONNECTION REJECT
message to the UE and the cause value contained in this message is congestion.In this case, this
counter is increased by one in the cell where the UE is located.
Issue 03 (2015-06-30)

3186
BSC6900 UMTS
Figure 1-1397 Radio link setup failure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3187
BSC6900 UMTS
Number of RRC Connection Rejects (Transmission Setup Failure on Iub Interface )

Counters
Counter ID
Counter Name
Counter Description
67179527
VS.RRC.Rej.TNL.Fail

Rejects for Cell
(Transmission Setup Failure
on Iub Interface )
Description
to the UE due to transmission setup failure on the Iub interface after the RNC receives a RRC
CONNECTION REQUEST message from the UE.This counter complies with section "8.1.3
Measurement point
The measurement is triggered at point B as shown in the figure. After the RNC and the NodeB
complete the radio link setup procedure, the RNC starts an ALCAP transmission setup procedure
on the Iub interface. If the ALCAP transmission setup fails, the RNC sends a RRC
CONNECTION REJECT message to the UE. In this case, this counter is measured in the cell
where the UE is located.
Figure 1-1398 Procedure for RRC connection rejects
Issue 03 (2015-06-30)

3188
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.TNL.Fail
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of RRC Connection Rejects during redirection between inter-RAT cells

Counters
Counter ID
Counter Name
Counter Description
67189474

Rejects during redirection
between inter-RAT cells for
cell
Description
These counters provide the number of RRC connection reject messages with inter-RAT
redirection information triggered by RRC admission failure in the cell. This counter only
measures the case of resource admission failure. The counter excludes the number of rejected
RRC connection requests caused by service-based redirection, inter-RAT and inter-frequency
distance-based redirection, weakcoverage-based redirection, or macro & micro joint interfrequency redirection.This counter complies with section "8.1.3 RRC connection establishment"
in 3GPP TS 25.331 (v10.13.0).
Measurement point
with redirection information. In this case, this counter is measured in the cell where the UE
camps on.
Issue 03 (2015-06-30)

3189
BSC6900 UMTS
Figure 1-1399 Procedure of RRC connection rejects
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-02040003
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3190
BSC6900 UMTS
Number of RRC Connection Rejects (RRC Redirection Triggered by Access

Failure)
Counters
Counter ID
Counter Name
Counter Description
67189473

Rejects during redirection
between inter-frequency
cells for cell
Description
These counters provide the number of RRC CONNECTION REJECT messages with interfrequency redirection information triggered by RRC admission failures in the cell. The counters
are measured only in the case of resource admission failure. The counters exclude the number
of rejected RRC connection requests caused by service-based redirection, inter-RAT and interfrequency distance-based redirection, weakcoverage-based redirection, or macro & micro joint
inter-frequency redirection, UE capability-based inter-frequency redirection.This counter
Measurement point
with redirection information. In this case, this counter is measured in the cell where the UE
camps on.
Issue 03 (2015-06-30)

3191
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Admission Failure based Inter-frequency or Inter-RAT RRC

Counters
Counter ID
Counter Name
Counter Description
73429104
VS.RRC.Rej.Redir.IntraRat.
CSService
Number of Admission
Failure based Interfrequency RRC Redirections
for Cell (CS Service)
73429105
VS.RRC.Rej.Redir.IntraRat.
PSService
Number of Admission
Failure based Interfrequency RRC Redirections
for Cell (PS Service)
73429106
VS.RRC.Rej.Redir.InterRat.
CSService
Number of Admission
Failure based Inter-RAT
(CS Service)
73429107
VS.RRC.Rej.Redir.InterRat.
PSService
Number of Admission
Failure based Inter-RAT
(PS Service)
Description
This counter provides the number of RRC CONNECTION REJECT messages with interfrequency or inter-RAT redirection information triggered by RRC admission failures in a cell.
Issue 03 (2015-06-30)

3192
BSC6900 UMTS
This counter is measured based on resource admission failures. The case of service-based
redirection is not measured.
Counter Name
Description
VS.RRC.Rej.Redir.IntraRat.CSService
This counter provides the number of RRC

CONNECTION REJECT messages with
inter-frequency redirection information
triggered by RRC admission failures in a cell.
This counter applies only to the RRC
connection requests whose cause is
"Originating Conversational Call",
"Terminating Conversational Call", or
"Emergency Call."
VS.RRC.Rej.Redir.IntraRat.PSService

inter-frequency redirection information
triggered by RRC admission failures in a cell.
This counter applies only to the RRC
connection requests whose cause is
"Originating Interactive Call", "Originating
Background Call","Terminating Interactive
Call", or "Terminating Background Call".
VS.RRC.Rej.Redir.InterRat.CSService

Inter-RAT redirection information triggered
by RRC admission failures in a cell. This
counter applies only to the RRC connection
requests whose cause is "Originating
Conversational Call", "Terminating
Conversational Call", or "Emergency Call."

Inter-RAT redirection information triggered
by RRC admission failures in a cell. This
counter applies only to the RRC connection
requests whose cause is "Originating
Interactive Call", "Originating Background
Call","Terminating Interactive Call", or
"Terminating Background Call".
Measurement point
The measurement is triggered at point A in the following figure. When receiving an RRC
CONNECTION REQUEST message from a UE, the RNC determines that the RRC admission
fails and sends the UE an RRC CONNECTION REJECT message, which carries the information
Issue 03 (2015-06-30)

3193
BSC6900 UMTS
about inter-frequency or inter-RAT RRC redirection. This counter is measured in the cell where
the UE is located based on the cause value included in the RRC CONNECT REQUEST message.
Formula
None
Unit
None
Related Features
None
Number of RRC Connection Rejects

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67179300
VS.RRC.Rej.Sum

Rejects for Cell

3194
BSC6900 UMTS
Description
This counter provides the number of RRC connection rejects in the cell. This counter excludes
and inter-frequency distance-based redirection, weakcoverage-based redirection, or macro &
micro joint inter-frequency redirection, UE capability-based inter-frequency redirection.This
(v10.13.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the RNC sends a RRC
CONNECTION REJECT message to reject the RRC connection after receiving a RRC
CONNECTION REQUEST message from the UE. In this case, this counter is measured
according to the cell where the UE is located. This counter excludes the number of rejected RRC
distance-based redirection, weakcoverage-based redirection, or macro & micro joint interfrequency redirection, UE capability-based inter-frequency redirection.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3195
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.Sum
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Number of Outgoing Inter-frequency Redirections based on Terminal Capability

for Cell
Counters
Counter ID
Counter Name
Counter Description
73430234
VS.RRC.Rej.Redir.UECapa
b.IntraRat
Number of Outgoing Interfrequency Redirections

based on Terminal Capability
for Cell
Description
REJECT message to trigger a terminal capability-based inter-frequency redirection in a cell.
When an RNC decides to perform a terminal capability-based RRC inter-frequency redirection,
the counter VS.RRC.Rej.Redir.IntraRat is not measured. For details about this counter, see
section 8.1.3 "RRC Connection Establishment" in 3GPP TS 25.331 v9.3.0.
Measurement point
As shown at point A in Figure 1, when an RNC decides to perform a terminal capability-based
RRC inter-frequency redirection, the RNC sends the UE an RRC CONNECTION REJECT
message, which contains redirection information. In this case, the counter is measured in the cell
where the UE camps. The terminal capability refers to the DC-HSDPA and 3C/4C-HSDPA
capability.
Issue 03 (2015-06-30)

3196
BSC6900 UMTS
Figure 1-1403 Terminal capability-based redirection procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.RRC.Rej.Redir.UECapa
b.IntraRat
WRFD-020110

WRFD-02040001
Number of RRC Connection Rejects Due to Distance-based Access Control for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430680

Rejects Due to Distancebased Access Control for
Cell

3197
BSC6900 UMTS
Description
REJECT message due to distance-based access control in a cell. For details about this counter,
see section 8.1.3 "RRC Connection Establishment" in 3GPP TS 25.331 V9.3.0.
Measurement point
As shown at point A in Figure 1, the RNC receives an RRC CONNECTION REQUEST message
from the UE. When the RNC decides to perform a distance-based access control, the RNC sends
the UE an RRC CONNECTION REJECT message, and this counter is measured in the cell
where the UE is located.
Figure 1-1404 Procedure for rejecting RRC connection requests due to distance-based access
control
Formula
None
Unit
None
Issue 03 (2015-06-30)

3198
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
1.12.44 RRC Status Measurement <per Cell>(RRC.State.Cell)

Overview
This function subset provides the average number of UEs in different RRC connection states in
the cell.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73410510
VS.CellDCHUEs
Number of UEs in
CELL_DCH State
for Cell
Earlier than
BSC6900
V900R011
73410511
VS.CellFACHUEs
Number of UEs in
CELL_FACH State
for Cell
Earlier than
BSC6900
V900R011
73410513
VS.CellPCHUEs
Number of UEs in
CELL_PCH State for
Cell
BSC6900
V900R012
73426285
VS.CellFACHUEs.
MAX
Maximum Count of
UE in CELL_FACH
BSC6900
V900R015C00
73443302
VS.CellDCH.RRC
UEs
Average Number of
Single-Signaling
UEs in the
CELL_DCH State
for Cell
BSC6900
V900R017C10
73443303
VS.CellDCHUEs.
MultiRAB
Average Number of
the UEs that Are in
the CELL_DCH
State and Are
Processing CS/PS
+PS Combined
Services for Cell
BSC6900
V900R015C01

3199
BSC6900 UMTS
Counter
Sub Counter
VS.CellDCHUEs
VS.CellDCHUEs.MultiRAB
Counters Related to the Number of UEs in Different RRC Connection States

Counters
Counter ID
Counter Name
Counter Description
73410510
VS.CellDCHUEs
Number of UEs in
73410511
VS.CellFACHUEs
Number of UEs in
73410513
VS.CellPCHUEs
Number of UEs in
CELL_PCH State for Cell
73426285
VS.CellFACHUEs.MAX
Maximum Count of UE in
CELL_FACH
Description
These counters provide the number of UEs in different RRC connection states.The preceding
counters comply with section "7.2.2 UTRA RRC Connected mode" in 3GPP TS 25.331
(v10.13.0).
Measurement point
The system periodically takes samples (sampling periodicity is 5 seconds) of UEs in different
RRC connection states. At the end of the measurement period, by dividing the accumulated value
of sample data in the period by the number of samples, the average and Maximum number of
UEs in each RRC connection state in the measurement period is obtained.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3200
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CellDCHUEs
WRFD-010202

URA-PCH, CELL-FACH)
VS.CellFACHUEs
WRFD-010202

URA-PCH, CELL-FACH)
VS.CellPCHUEs
WRFD-010202

URA-PCH, CELL-FACH)
VS.CellFACHUEs.MAX
WRFD-010202

URA-PCH, CELL-FACH)
Average Number of Single-Signaling UEs in the CELL_DCH State for Cell

Counters
Counter ID
Counter Name
Counter Description
73443302
VS.CellDCH.RRCUEs
Average Number of SingleSignaling UEs in the

Description
This counter provides the average number of single-signaling UEs in the CELL_DCH state
within a measurement period.
Measurement point
The system periodically takes samples (sampling period is five seconds) of the number of singlesignaling UEs in the CELL_DCH state. At the end of the measurement period, the average
number of single-signaling UEs in the CELL_DCH state is obtained by dividing the accumulated
value of the sampling results in the period by the number of samplings.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3201
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CellDCH.RRCUEs
WRFD-010202

URA-PCH, CELL-FACH)
Average Number of the UEs that Are in the CELL_DCH State and Are Processing
CS/PS+PS Combined Services for Cell
Counters
Counter ID
Counter Name
Counter Description
73443303
Average Number of the UEs

that Are in the CELL_DCH
State and Are Processing CS/
PS+PS Combined Services
for Cell
Description
This counter provides the average number of the UEs that are in the CELL_DCH state and are
processing CS/PS+PS combined services in a cell within a measurement period.This counter
complies with section "7.2.2 UTRA RRC Connected mode" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The RNC samples the number of the UEs that are in the CELL_DCH state and are processing
CS/PS+PS combined services in a cell every 5 seconds. At the end of a measurement period,
the RNC divides the accumulated value in the period by the number of samples to obtain the
average number of such UEs in the period.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3202
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010609

WRFD-010615
Multiple RAB Package (PS

RAB >=2)
1.12.45 UE Capability Measurement <per Cell>

(RRC.UECapab.Cell)
Overview
he RRC.UECapab.Cell counter provides the number of times that the RNC receives the RRC
CONNECTION SETUP COMPLETE message from the UE in a cell. This counter is measured
according to the UE capability information contained in the RRC CONNECTION SETUP
COMPLETE message.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425958
RRC.SuccConnEst
ab.HSDSCH.AllCA
T
Number of
Successful RRC
Connection Setups
for Cell (Including
All the HS-DSCH
Physical Layer
Categories)
BSC6900
V900R015C00
73425959
RRC.SuccConnEst
ab.HSDSCH.CAT7
.10
Number of
Successful RRC
Connection Setups
for Cell (including
the HS-DSCH
Physical Layer
Categories 7
Through 10)
BSC6900
V900R015C00
73425960
RRC.SuccConnEst
ab.HSDSCH.CAT1
3.14
Number of
Successful RRC
Connection Setups
for Cell (including
the HS-DSCH
Physical Layer
Categories 13 and
14)
BSC6900
V900R015C00

3203
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425961
RRC.SuccConnEst
ab.HSDSCH.CAT1
5.16
Number of
Successful RRC
Connection Setups
for Cell (Including
the HS-DSCH
Physical Layer
Categories 15 and
16)
BSC6900
V900R015C00
73425962
RRC.SuccConnEst
ab.HSDSCH.CAT1
7.20
Number of
Successful RRC
Connection Setups
for Cell (Including
the HS-DSCH
Physical Layer
Categories 17
Through 20)
BSC6900
V900R015C00
73425963
RRC.SuccConnEst
ab.HSDSCH.CAT2
1.24
Number of
Successful RRC
Connection Setups
for Cell (Including
the HS-DSCH
Physical Layer
Categories 21
Through 24)
BSC6900
V900R015C00
73425964
RRC.SuccConnEst
ab.HSDSCH.CAT2
5.28
Number of
Successful RRC
Connection Setups
for Cell (Including
the HS-DSCH
Physical Layer
Categories 25
Through 28)
BSC6900
V900R015C00
73425965
RRC.SuccConnEst
ab.HSDSCH.CAT2
9
Number of
Successful RRC
Connection Setups
for Cell (Including
the HS-DSCH
Physical Layer
Category 29)
BSC6900
V900R015C00

3204
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425966
RRC.SuccConnEst
ab.HSDSCH.CAT3
0
Number of
Successful RRC
Connection
Establishments for
Cell (Including the
HS-DSCH Physical
Layer Category 30)
BSC6900
V900R015C00
73425967
RRC.SuccConnEst
ab.HSDSCH.CAT3
1
Number of
Successful RRC
Connection Setups
for Cell (Including
the HS-DSCH
Physical Layer
Category 31)
BSC6900
V900R015C00
73425968
RRC.SuccConnEst
ab.HSDSCH.CAT3
2
Number of
Successful RRC
Connection Setups
for Cell (Including
the HS-DSCH
Physical Layer
Category 32)
BSC6900
V900R015C00
73425969
RRC.SuccConnEst
ab.EDCH.AllCAT
Number of
Successful RRC
Connection Setups
for Cell (Including
All the E-DCH
Physical Layer
Categories)
BSC6900
V900R015C00
73425970
RRC.SuccConnEst
ab.EDCH.CAT2
Number of
Successful RRC
Connection Setups
for Cell (Including
the E-DCH Physical
Layer Category 2)
BSC6900
V900R015C00
73425971
RRC.SuccConnEst
ab.EDCH.CAT4
Number of
Successful RRC
Connection Setups
for Cell (Including
the E-DCH Physical
Layer Category 4)
BSC6900
V900R015C00

3205
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73425972
RRC.SuccConnEst
ab.EDCH.CAT5
Number of
Successful RRC
Connection Setups
for Cell (Including
the E-DCH Physical
Layer Category 5)
BSC6900
V900R015C00
73425973
RRC.SuccConnEst
ab.EDCH.CAT6
Number of
Successful RRC
Connection Setups
for Cell (Including
the E-DCH Physical
Layer Category 6)
BSC6900
V900R015C00
73425974
RRC.SuccConnEst
ab.EDCH.CAT7
Number of
Successful RRC
Connection Setups
for Cell (Including
the E-DCH Physical
Layer Category 7)
BSC6900
V900R015C00
73425975
RRC.SuccConnEst
ab.EDCH.CAT8
Number of
Successful RRC
Connection Setups
for Cell (Including
the E-DCH Physical
Layer Category 8)
BSC6900
V900R015C00
73425976
RRC.SuccConnEst
ab.EDCH.CAT9
Number of
Successful RRC
Connection Setups
for Cell (Including
the E-DCH Physical
Layer Category 9)
BSC6900
V900R015C00
73427211
VS.AttCall.UECap
ab.AMRWB
Number of Calls
Initiated and
Received by UEs
Supporting AMRWB for Cell
BSC6900
V900R015C01
Issue 03 (2015-06-30)

3206
BSC6900 UMTS
Counter
Sub Counter
RRC.SuccConnEstab.HSDSCH.AllCAT
RRC.SuccConnEstab.HSDSCH.CAT7.10
RRC.SuccConnEstab.HSDSCH.CAT29
RRC.SuccConnEstab.EDCH.AllCAT
RRC.SuccConnEstab.EDCH.CAT2
Number of Successful RRC Connection Setups (Including All the HS-DSCH

Physical Layer Categories)
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425958
RRC.SuccConnEstab.HSDS
CH.AllCAT

(Including All the HS-DSCH
73425959
CH.CAT7.10

(including the HS-DSCH
Physical Layer Categories 7
Through 10)
73425960
CH.CAT13.14

(including the HS-DSCH
and 14)

3207
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73425961
CH.CAT15.16

(Including the HS-DSCH
and 16)
73425962
CH.CAT17.20

Through 20)
73425963
CH.CAT21.24

Through 24)
73425964
CH.CAT25.28

Through 28)
73425965
CH.CAT29

Physical Layer Category 29)
73425966
CH.CAT30

for Cell (Including the HSDSCH Physical Layer
Category 30)
73425967
CH.CAT31

73425968
CH.CAT32

Description
These counters provide the number of times that the RNC receives an RRC CONNECTION
SETUP COMPLETE message from a UE. These counters are measured based on the value of
the "HS-DSCH physical layer category" information element (IE) in the RRC CONNECTION
Issue 03 (2015-06-30)

3208
BSC6900 UMTS
SETUP COMPLETE message. 1) The RRC.SuccConnEstab.HSDSCH.AllCAT counter

provides the number of successful RRC connection setups with the "HS-DSCH physical layer
category" IE. 2) Other counters provide the number of successful RRC connection setups with
different values of the "HS-DSCH physical layer category" IE. These values are the maximum
values between basic IEs and extension IEs. The preceding counters comply with section "8.1.3
Measurement point
The measurement is triggered at point C as shown in the figure when the RNC receives an RRC
CONNECTION SETUP COMPLETE message from the UE. These counters are measured in
the cell where the UE camps based on the value of the "HS-DSCH physical layer category" IE
in the RRC CONNECTION SETUP COMPLETE message. The value is the maximum value
between the basic IE and extension IE. For details about HS-DSCH physical layer categories,
see Table 5.1a: FDD HS-DSCH physical layer categories in 3GPP TS 25.306.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3209
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
CH.AllCAT
WRFD-01061002
WRFD-010699
DC-HSDPA+MIMO
WRFD-150207
4C-HSDPA
WRFD-150223
MC-HSDPA+MIMO
CH.CAT7.10
WRFD-01061002
CH.CAT13.14
WRFD-01061002
CH.CAT15.16
WRFD-01061002
CH.CAT17.20
WRFD-01061002
CH.CAT21.24
WRFD-01061002
CH.CAT25.28
WRFD-010699
DC-HSDPA+MIMO
CH.CAT29
WRFD-150250
3C-HSDPA
CH.CAT30
WRFD-150223
MC-HSDPA+MIMO
CH.CAT31
WRFD-150207
4C-HSDPA
CH.CAT32
WRFD-150223
MC-HSDPA+MIMO
Number of Successful RRC Connection Setups for Cell (Including All the E-DCH
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425969
RRC.SuccConnEstab.EDCH
.AllCAT

(Including All the E-DCH

3210
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73425970
.CAT2

(Including the E-DCH
73425971
.CAT4

73425972
.CAT5

73425973
.CAT6

73425974
.CAT7

73425975
.CAT8

73425976
.CAT9

Description
These counters provide the number of times that the RNC receives an RRC CONNECTION
SETUP COMPLETE message from a UE. These counters are measured based on the value of
the "E-DCH physical layer category" information element (IE) in the RRC CONNECTION
SETUP COMPLETE message. 1) The RRC.SuccConnEstab.HSDSCH.AllCAT counter
provides the number of successful RRC connection setups with the "E-DCH physical layer
category" IE. 2) Other counters provide the number of successful RRC connection setups with
different values of the "E-DCH physical layer category" IE. These values are the maximum
values between basic IEs and extension IEs. The preceding counters comply with section "8.1.3
Measurement point
The measurement is triggered at point C as shown in the figure when the RNC receives an RRC
CONNECTION SETUP COMPLETE message from the UE. These counters are measured in
Issue 03 (2015-06-30)

3211
BSC6900 UMTS
the cell where the UE camps based on the value of the "E-DCH physical layer category" IE in
the RRC CONNECTION SETUP COMPLETE message. The value is the maximum value
between the basic IE and extension IE. For details about E-DCH physical layer categories, see
Table 5.1g: FDD E-DCH physical layer categories in 3GPP TS 25.306.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.AllCAT
WRFD-01061201
HSUPA UE Category
Support
.CAT2
WRFD-01061201
HSUPA UE Category
Support
.CAT4
WRFD-01061201
HSUPA UE Category
Support
.CAT5
WRFD-01061201
HSUPA UE Category
Support
.CAT6
WRFD-01061201
HSUPA UE Category
Support

3212
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
.CAT7
WRFD-01061201
HSUPA UE Category
Support
.CAT8
WRFD-01061201
HSUPA UE Category
Support
.CAT9
WRFD-01061201
HSUPA UE Category
Support
Number of Calls Initiated and Received by UEs Supporting AMR-WB for Cell
Counters
Counter ID
Counter Name
Counter Description
73427211
VS.AttCall.UECapab.AMR
WB
Number of Calls Initiated and

Received by UEs Supporting
AMR-WB for Cell
Description
This counter measures the number of calls initiated and received by UEs supporting AMR-WB
in the best cell. This counter indicates the penetration rate of UEs supporting AMR-WB.This
(v10.13.0).
Measurement point
The measurement is triggered at point A in figure 1. When receiving an UPLINK DIRECT
TRANSFER message from a UE, the RNC determines whether the message type is SETUP,
EMERGENCY SETUP, or CALL CONFIRMED. If yes, the RNC reads the value of the
supported-codecs IE in the message. If the IE carries UMTS_AMR-WB, this counter is measured
in the best cell for the UE. For details about the supported-codecs IE, see 3GPP TS 26.103 and
3GPP TS 24.008.
Figure 1-1407 Uplink Direct transfer process
Issue 03 (2015-06-30)

3213
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttCall.UECapab.AMR
WB
WRFD-010613

Rate Wide Band)
1.12.46 TX and RX Power Measurement <per Cell>(RTWPTCP.Cell)

Overview
The function subset provides the uplink interference and downlink power consumption of a cell,
which are used to assess the cell load. After a cell is set up, the NodeB periodically sends the
RNC RTWP-related COMMON MEASUREMENT REPORT messages and TCP-related
COMMON MEASUREMENT REPORT messages if transmit power and receive power are
required. After HSPA is introduced, the following HSPA-related measurements are added: nonHSPA power (Transmitted Carrier Power Of All Codes Not Used For HSTransmission in 3GPP
TS 25.433), HSDPA required power (HS-DSCH Required Power in 3GPP TS 25.433), and
power for HSUPA scheduling (Received Scheduled E-DCH Power Share in 3GPP TS 25.433).
The RNC obtains measurement values through COMMON MEASUREMENT REPORT
messages periodically send by the NodeB. You can run [CMD]SET ULDM[/CMD]to configure
measurement periods.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199680
VS.MaxRTWP
Maximum Power of
Totally Received
Bandwidth for Cell
Earlier than
BSC6900
V900R011
67199681
VS.MinRTWP
Minimum Power of
Totally Received
Bandwidth for Cell
Earlier than
BSC6900
V900R011
67199617
VS.MeanRTWP
Mean Power of
Totally Received
Bandwidth for Cell
Earlier than
BSC6900
V900R011

3214
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199682
VS.MaxTCP
Maximum
Transmitted Power
of Carrier for Cell
Earlier than
BSC6900
V900R011
67199683
VS.MinTCP
Minimum
Transmitted Power
of Carrier for Cell
Earlier than
BSC6900
V900R011
67199618
VS.MeanTCP
Mean Transmitted
Power of Carrier for
Cell
Earlier than
BSC6900
V900R011
67202900
VS.MaxTCP.NonH
S
Maximum NonHSDPA Transmitted

Carrier Power for
Cell
Earlier than
BSC6900
V900R011
67202901
VS.MinTCP.NonH
S
Minimum NonHSDPA Transmitted

Carrier Power for
Cell
Earlier than
BSC6900
V900R011
67202902
VS.MeanTCP.Non
HS
Mean Non-HSDPA
Transmitted Carrier
Power for Cell
Earlier than
BSC6900
V900R011
67202982
VS.HSDPA.MaxRe
quiredPwr
Maximum Power
Required by HSDSCH for Cell
Earlier than
BSC6900
V900R011
67202983
VS.HSDPA.MinRe
quiredPwr
Minimum Power
Earlier than
BSC6900
V900R011
67202984
VS.HSDPA.MeanR
equiredPwr
Mean Power
Earlier than
BSC6900
V900R011
73415859
VS.HSUPA.MeanRSEPS
Average Received
Scheduled E-DCH
Power Share for Cell
BSC6900
V900R012
73403758
VS.HSUPA.MaxRSEPS
Maximum Received
Scheduled E-DCH
BSC6900
V900R012
73403760
VS.HSUPA.MinRSEPS
Minimum Received
Scheduled E-DCH
BSC6900
V900R012

3215
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441143
VS.HSDPA.MaxRe
quiredPwr.Free
Maximum Power
Required for Free
HSDPA Users for
Cell
BSC6900
V900R013
73441144
VS.HSDPA.MeanR
equiredPwr.Free
Average Power
Required for Free
HSDPA Users for
Cell
BSC6900
V900R013
73425896
VS.HSDPA.MC.M
eanRequiredPwr
Power Required by
4C-HSDPA/DBHSDPA/DCHSDPA UEs for Cell
BSC6900
V900R015C00
73425901
VS.HSDPA.MC.M
axRequiredPwr
Maximum Power
Required by 4CHSDPA/DBHSDPA/DCHSDPA UEs for Cell
BSC6900
V900R015C00
73425903
VS.HSDPA.MC.Mi
nRequiredPwr
Minimum Power
Required by 4CHSDPA/DBHSDPA/DCHSDPA UEs for Cell
BSC6900
V900R015C00
73425905
VS.MeanTCP.HSD
PA.MC
Average DL
Transmit Power of
BSC6900
V900R015C00
73425910
VS.MaxTCP.HSDP
A.MC
Maximum DL
Transmit Power of
BSC6900
V900R015C00
73425912
VS.MinTCP.HSDP
A.MC
Minimum DL
Transmit Power of
BSC6900
V900R015C00
73426885
VS.RTWP.0
Number of Times the

RTWP of a Cell Is
Less than -108 dBm
BSC6900
V900R015C01

3216
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426886
VS.RTWP.1
Number of Times the

RTWP of a Cell Is
Between -108 dBm
(Included) and -107
dBm
BSC6900
V900R015C01
73426887
VS.RTWP.2
Number of Times the

RTWP of a Cell Is
Between -107 dBm
(Included) and -106
dBm
BSC6900
V900R015C01
73426888
VS.RTWP.3
Number of Times the

RTWP of a Cell Is
Between -106 dBm
(Included) and -105
dBm
BSC6900
V900R015C01
73426890
VS.RTWP.4
Number of Times the

RTWP of a Cell Is
Between -105 dBm
(Included) and -104
dBm
BSC6900
V900R015C01
73426891
VS.RTWP.5
Number of Times the

RTWP of a Cell Is
Between -104 dBm
(Included) and -103
dBm
BSC6900
V900R015C01
73426892
VS.RTWP.6
Number of Times the

RTWP of a Cell Is
Between -103 dBm
(Included) and -102
dBm
BSC6900
V900R015C01
73426893
VS.RTWP.7
Number of Times the

RTWP of a Cell Is
Between -102 dBm
(Included) and -101
dBm
BSC6900
V900R015C01
73426894
VS.RTWP.8
Number of Times the

RTWP of a Cell Is
Between -101 dBm
(Included) and -100
dBm
BSC6900
V900R015C01

3217
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426895
VS.RTWP.9
Number of Times the

RTWP of a Cell Is
Between -100 dBm
(Included) and -99
dBm
BSC6900
V900R015C01
73426896
VS.RTWP.10
Number of Times the

RTWP of a Cell Is
Between -99 dBm
(Included) and -98
dBm
BSC6900
V900R015C01
73426897
VS.RTWP.11
Number of Times the

RTWP of a Cell Is
Between -98 dBm
(Included) and -96
dBm
BSC6900
V900R015C01
73426898
VS.RTWP.12
Number of Times the

RTWP of a Cell Is
Between -96 dBm
(Included) and -94
dBm
BSC6900
V900R015C01
73426899
VS.RTWP.13
Number of Times the

RTWP of a Cell Is
Between -94 dBm
(Included) and -92
dBm
BSC6900
V900R015C01
73426900
VS.RTWP.14
Number of Times the

RTWP of a Cell Is
Between -92 dBm
(Included) and -89
dBm
BSC6900
V900R015C01
73426901
VS.RTWP.15
Number of Times the

RTWP of a Cell Is
Between -89 dBm
(Included) and -86
dBm
BSC6900
V900R015C01
73426902
VS.RTWP.16
Number of Times the

RTWP of a Cell Is
Between -86 dBm
(Included) and -83
dBm
BSC6900
V900R015C01

3218
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426903
VS.RTWP.17
Number of Times the

RTWP of a Cell Is
Between -83 dBm
(Included) and -80
dBm
BSC6900
V900R015C01
73426904
VS.RTWP.18
Number of Times the

RTWP of a Cell Is
Between -80 dBm
(Included) and -75
dBm
BSC6900
V900R015C01
73426905
VS.RTWP.19
Number of Times the

RTWP of a Cell Is
Between -75 dBm
(Included) and -70
dBm
BSC6900
V900R015C01
73426906
VS.RTWP.20
Number of Times the

RTWP of a Cell Is
Between -70 dBm
(Included) and -65
dBm
BSC6900
V900R015C01
73426907
VS.RTWP.21
Number of Times the

RTWP of a Cell Is
to -65 dBm
BSC6900
V900R015C01
73426908
VS.TCP.0
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 0%
(Included) and 5%
BSC6900
V900R015C01
73426909
VS.TCP.1
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 5%
(Included) and 10%
BSC6900
V900R015C01
73426910
VS.TCP.2
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 10%
(Included) and 15%
BSC6900
V900R015C01

3219
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426911
VS.TCP.3
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 15%
(Included) and 20%
BSC6900
V900R015C01
73426912
VS.TCP.4
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 20%
(Included) and 25%
BSC6900
V900R015C01
73426913
VS.TCP.5
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 25%
(Included) and 30%
BSC6900
V900R015C01
73426914
VS.TCP.6
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 30%
(Included) and 35%
BSC6900
V900R015C01
73426915
VS.TCP.7
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 35%
(Included) and 40%
BSC6900
V900R015C01
73426916
VS.TCP.8
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 40%
(Included) and 45%
BSC6900
V900R015C01
73426917
VS.TCP.9
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 45%
(Included) and 50%
BSC6900
V900R015C01
73426918
VS.TCP.10
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 50%
(Included) and 55%
BSC6900
V900R015C01

3220
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426919
VS.TCP.11
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 55%
(Included) and 60%
BSC6900
V900R015C01
73426920
VS.TCP.12
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 60%
(Included) and 65%
BSC6900
V900R015C01
73426921
VS.TCP.13
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 65%
(Included) and 70%
BSC6900
V900R015C01
73426922
VS.TCP.14
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 70%
(Included) and 75%
BSC6900
V900R015C01
73426923
VS.TCP.15
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 75%
(Included) and 80%
BSC6900
V900R015C01
73426924
VS.TCP.16
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 80%
(Included) and 85%
BSC6900
V900R015C01
73426925
VS.TCP.17
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 85%
(Included) and 90%
BSC6900
V900R015C01
73426926
VS.TCP.18
Number of Times the

Transmitted Carrier
Power of a Cell Is
Between 90%
(Included) and 95%
BSC6900
V900R015C01

3221
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426927
VS.TCP.19
Number of Times the

Transmitted Carrier
Power of a Cell Is
from 95% to 100%
BSC6900
V900R015C01
73426928
VS.TCP.NonHS.0
Number of Times the

Transmitted Carrier
Power of All Codes
not Used for Physical
HSDPA Channel
Transmission Is
Between 0%
(Included) and 5%
for Cell
BSC6900
V900R015C01
73426929
VS.TCP.NonHS.1
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 5%
(Included) and 10%
for Cell
BSC6900
V900R015C01
73426930
VS.TCP.NonHS.2
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 10%
(Included) and 15%
for Cell
BSC6900
V900R015C01
73426931
VS.TCP.NonHS.3
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 15%
(Included) and 20%
for Cell
BSC6900
V900R015C01

3222
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426932
VS.TCP.NonHS.4
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 20%
(Included) and 25%
for Cell
BSC6900
V900R015C01
73426933
VS.TCP.NonHS.5
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 25%
(Included) and 30%
for Cell
BSC6900
V900R015C01
73426934
VS.TCP.NonHS.6
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 30%
(Included) and 35%
for Cell
BSC6900
V900R015C01
73426935
VS.TCP.NonHS.7
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 35%
(Included) and 40%
for Cell
BSC6900
V900R015C01
73426936
VS.TCP.NonHS.8
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 40%
(Included) and 45%
for Cell
BSC6900
V900R015C01

3223
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426937
VS.TCP.NonHS.9
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 45%
(Included) and 50%
for Cell
BSC6900
V900R015C01
73426938
VS.TCP.NonHS.10
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 50%
(Included) and 55%
for Cell
BSC6900
V900R015C01
73426939
VS.TCP.NonHS.11
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 55%
(Included) and 60%
for Cell
BSC6900
V900R015C01
73426940
VS.TCP.NonHS.12
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 60%
(Included) and 65%
for Cell
BSC6900
V900R015C01
73426941
VS.TCP.NonHS.13
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 65%
(Included) and 70%
for Cell
BSC6900
V900R015C01

3224
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426942
VS.TCP.NonHS.14
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 70%
(Included) and 75%
for Cell
BSC6900
V900R015C01
73426943
VS.TCP.NonHS.15
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 75%
(Included) and 80%
for Cell
BSC6900
V900R015C01
73426944
VS.TCP.NonHS.16
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 80%
(Included) and 85%
for Cell
BSC6900
V900R015C01
73426945
VS.TCP.NonHS.17
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 85%
(Included) and 90%
for Cell
BSC6900
V900R015C01
73426946
VS.TCP.NonHS.18
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is
Between 90%
(Included) and 95%
for Cell
BSC6900
V900R015C01

3225
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426947
VS.TCP.NonHS.19
Number of Times the

Transmitted Carrier
Power of All Codes
HSDPA Channel
Transmission Is from
95% to 100% for Cell
BSC6900
V900R015C01
Counter
Sub Counter
VS.MaxTCP
VS.MaxTCP.NonHS
VS.MinTCP
VS.MinTCP.NonHS
VS.MeanTCP
VS.MeanTCP.NonHS
Received Total Wideband Power for cell

Counters
Counter ID
Counter Name
Counter Description
67199617
VS.MeanRTWP
Mean Power of Totally

Received Bandwidth for Cell
67199680
VS.MaxRTWP
Maximum Power of Totally

67199681
VS.MinRTWP
Minimum Power of Totally

specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180641
VS.RTWP.CUM
Accumulated Totally
Received Bandwidth Power
for Cell

3226
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67180642
VS.RTWP.SAMPLE
Number of the Totally

Received Bandwidth Power
for Cell
Description
These counters provide the received total wideband power (RTWP) measurement values of a
cell for assessing the uplink interference level and uplink loads in the cell.These counters comply
with section "9.2.1 Received total wideband power" in 3GPP TS 25.133 (v10.10.0).
Measurement point
1s. The RNC averages the reported measurement values every 5s to obtain the RTWP of the cell
in which the measurement is performed. At the end of the measurement period, the RNC divides
the accumulated numbers by the number of samples to obtain the value of VS.MeanRTWP in
the measurement period. The maximum and minimum sampled values are taken as the values
of VS.MaxRTWP and VS.MinRTWP.
Formula
VS.MeanRTWP = ([VS.RTWP.CUM]/[VS.RTWP.SAMPLE]-{1121})/{10}
Unit
dBm
Issue 03 (2015-06-30)

3227
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MeanRTWP
WRFD-020102
Load Measurement
VS.MaxRTWP
WRFD-020102
Load Measurement
VS.MinRTWP
WRFD-020102
Load Measurement
Transmitted Power of Carrier for Cell

Counters
Counter ID
Counter Name
Counter Description
67199618
VS.MeanTCP
Mean Transmitted Power of

Carrier for Cell
67199682
VS.MaxTCP
Maximum Transmitted
Power of Carrier for Cell
67199683
VS.MinTCP
Minimum Transmitted
Power of Carrier for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
67204826
VS.TCP.CUM.NoLog
Cumulated Transmitted
Power of Carrier of Cell
(Before Log Calculation)
67180648
VS.TCP.SAMPLE
Number of Received
Transmitted Power of Carrier
for Cell
Description
These counters provide the transmitted carrier power (TCP) measurement values of a cell for
assessing the downlink load state in the cell.These counters comply with section "9.2.16
Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH
or E-HICH transmission" in 3GPP TS 25.133 (v10.10.0).
Issue 03 (2015-06-30)

3228
BSC6900 UMTS
Measurement point
1s. The RNC averages the reported measurement values every 5s to obtain the TCP at a sampling
point. At the end of the measurement period, the RNC divides the accumulated numbers by the
number of samples to obtain the value of VS.MeanTCP in the measurement period. The
maximum and minimum sampled values are taken as the values of VS.MaxTCP and
VS.MinTCP.
Formula
VS.MeanTCP = {10}*(log10[VS.TCP.CUM.NoLog]-log10[VS.TCP.SAMPLE])
Unit
dBm
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MeanTCP
WRFD-020102
Load Measurement
VS.MaxTCP
WRFD-020102
Load Measurement
VS.MinTCP
WRFD-020102
Load Measurement

3229
BSC6900 UMTS
Transmitted Power of Non-HSDPA Carrier for Cell

Counters
Counter ID
Counter Name
Counter Description
67202902
VS.MeanTCP.NonHS
Mean Non-HSDPA
Transmitted Carrier Power
for Cell
67202900
VS.MaxTCP.NonHS
Maximum Non-HSDPA
for Cell
67202901
VS.MinTCP.NonHS
Minimum Non-HSDPA
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
67204827
VS.TCP.NonHS.CUM.NoLog
Non-HSDPA Transmitted
Carrier Power for Cell
67190621
VS.TCP.NonHS.SAMPLE
Number of Received
Measurement Reports of
Non-HSDPA Transmitted
Carrier Power for Cell
Description
These counters provide the downlink non-HSPA TCP measurement values of a cell for assessing
downlink non-HSPA power load state in the cell.
After HSPA is introduced, cell loads are classified into non-HSPA power loads and HSPA power
loads.
HSPA power is the power used to transmit data on the HS-PDSCH, HS-SCCH, E-AGCH, ERGCH, and E-HICH.
Non-HSPA power is the power used to transmit data on the common channels, DPDCH, and
DPCCH, including power consumed by loads on the DPCCH and DPDCH when HSDPA users
use SRB over DCH.These counters comply with section "9.2.16 Transmitted carrier power of
all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission"
in 3GPP TS 25.133 (v10.10.0).
Issue 03 (2015-06-30)

3230
BSC6900 UMTS
Measurement point
the NodeB a COMMON MEASUREMENT REPORT message about the non-HSDPA TCP of
a cell every 1s. The RNC averages the reported measurement values every 5s to obtain the nonHSDPA TCP at a sampling point. At the end of the measurement period, the RNC divides the
accumulated numbers by the number of samples to obtain the value of VS.MeanNonTCP in the
measurement period. The maximum and minimum sampled values are taken as the values of
VS.MaxNonTCP and VS.MinNonTCP.
Formula
VS.MeanTCP.NonHS = {10}*(log10[VS.TCP.NonHS.CUM.NoLog]-log10
[VS.TCP.NonHS.SAMPLE])
Unit
dBm
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MeanTCP.NonHS
WRFD-020102
Load Measurement
VS.MaxTCP.NonHS
WRFD-020102
Load Measurement
VS.MinTCP.NonHS
WRFD-020102
Load Measurement

3231
BSC6900 UMTS
Power Required by HS-DSCH for Cell

Counters
Counter ID
Counter Name
Counter Description
67202984
VS.HSDPA.MeanRequiredPwr
Mean Power Required by

HS-DSCH for Cell
67202982
VS.HSDPA.MaxRequiredPwr
Maximum Power Required

by HS-DSCH for Cell
67202983
VS.HSDPA.MinRequiredPwr
Minimum Power Required

by HS-DSCH for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
67204828
VS.HSDPA.RequiredPwr.C
UM.NoLog
Cumulated Power Required

by HS-DSCH for Cell
67191149
VS.HSDPA.RequiredPwr.S
AMPLE
Number of Received
Power Required by HSDSCH in dBm for Cell
Description
These counters provide the measurement values of power required to meet the guaranteed bit
rate (GBR) for SC-HSDPA users in an HSDPA cell. For details, see 3GPP TS 25.433. These
measurement values are used to assess downlink load state in the cell.These counters comply
with section "9.2.1.31 Ic HS-DSCH Required Power Value Information" in 3GPP TS 25.433
(v10.10.0).
Measurement point
the NodeB a COMMON MEASUREMENT REPORT message about the power required to
meet the GBR for SC-HSDPA users in an HSDPA cell every 1s. The RNC averages the reported
measurement values every 5s to obtain the value of the power at a sampling point. At the end
of the measurement period, the RNC divides the accumulated numbers by the number of samples
to obtain the value of VS.HSDPA.MeanRequiredPwr in the measurement period. The maximum
and minimum sampled values are taken as the values of VS.HSDPA.MaxRequiredPwr and
VS.HSDPA.MinRequiredPwr. Note: These counters can be measured only when data is
transmitted on the HS-DSCH.
Issue 03 (2015-06-30)

3232
BSC6900 UMTS
Formula
VS.HSDPA.MeanRequiredPwr = {10}*(log10[VS.HSDPA.RequiredPwr.CUM.NoLog]-log10
[VS.HSDPA.RequiredPwr.SAMPLE])
Unit
dBm
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.MeanRequiredPwr
WRFD-020102
Load Measurement
VS.HSDPA.MaxRequiredPwr
WRFD-020102
Load Measurement
VS.HSDPA.MinRequiredPwr
WRFD-020102
Load Measurement
Received Scheduled E-DCH Power Share in the Measurement Period for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73415859
VS.HSUPA.MeanRSEPS
Average Received Scheduled

E-DCH Power Share for Cell
73403758
VS.HSUPA.MaxRSEPS
Maximum Received
Scheduled E-DCH Power
Share for Cell

3233
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73403760
VS.HSUPA.MinRSEPS
Minimum Received
Scheduled E-DCH Power
Share for Cell
Description
Received scheduled E-DCH power share (RSEPS) is the ratio of E-DCH channel interference
to the total interference of the cell, which is measured on the NodeB. For details, see section
5.2.17 in 3GPP TS 25.215. Values of these counters are used to calculate uplink uncontrollable
loads and they serve as data input for the uplink admission algorithm and load reshuffling (LDR)
algorithm. These counters comply with section "9.2.18 Received scheduled E-DCH power share
(RSEPS)" in 3GPP TS 25.133 (v10.10.0).
Measurement point
the NodeB a COMMON MEASUREMENT REPORT message about the RSEPS value every
1s. Then, the RNC converts the received value to a value defined in 3GPP TS 25.133 by using
the following formula: pow(10.0, (2.0 + (RSEPS value reported by NodeB - 151)/100.0)) The
RNC averages the values complying with 3GPP TS 25.133 every 5s to obtain the RSEPS value
at a sampling point. At the end of the measurement period, the RNC divides the accumulated
numbers by the number of samples to obtain the value of VS.HSUPA.MeanRSEPS in the
VS.HSUPA.MaxRSEPS and VS.HSUPA.MinRSEPS.
Issue 03 (2015-06-30)

3234
BSC6900 UMTS
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.HSUPA.MeanRSEPS
WRFD-020102
Load Measurement
VS.HSUPA.MaxRSEPS
WRFD-020102
Load Measurement
VS.HSUPA.MinRSEPS
WRFD-020102
Load Measurement
Average Power Required for Free HSDPA Users for Cell

Counters
Counter ID
Counter Name
Counter Description
73441144
VS.HSDPA.MeanRequiredP
wr.Free
Average Power Required for

Free HSDPA Users for Cell
73441143
VS.HSDPA.MaxRequiredP
wr.Free

for Free HSDPA Users for
Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441145
VS.HSDPA.RequiredPwr.Fr
ee.CUM.NoLog
Cumulated Free Power

Required by HS-DSCH for
Cell (Before Log
Calculation)
73423475
VS.HSDPA.RequiredPwr.Fr
ee.SAMPLE
Number of Received
Free Power Required by HSDSCH in dBm for Cell

3235
BSC6900 UMTS
Description
These counters provide the maximum and mean measurement values of the transmit power of
the TRX that is required for free HSDPA users to meet the GBR in an HSDPA cell. For details,
see 3GPP TS 25.433. These measurement values are used to assess downlink loads of the free
HSDPA users in the HSDPA cell. "Free HSDPA user" is a customized function.These counters
comply with section "9.2.1.31 Ic HS-DSCH Required Power Value Information" in 3GPP TS
25.433 (v10.10.0).
Measurement point
the NodeB a COMMON MEASUREMENT REPORT message about the transmit power of the
TRX that is required for free HSDPA users to meet the GBR in an HSDPA cell every 1s. The
RNC averages the reported measurement values every 5s to obtain the value of the transmit
power at a sampling point. At the end of the measurement period, the RNC divides the
accumulated numbers by the number of samples to obtain the value of
VS.HSDPA.MeanRequiredPwr.Free in the measurement period. The maximum sampled value
is taken as the value of VS.HSDPA.MaxRequiredPwr.Free. Note: These counters can be
measured only when data is transmitted on the HS-DSCH.
Formula
VS.HSDPA.MeanRequiredPwr.Free = {10}*(log10
[VS.HSDPA.RequiredPwr.Free.CUM.NoLog]-log10
[VS.HSDPA.RequiredPwr.Free.SAMPLE])
Unit
dBm
Issue 03 (2015-06-30)

3236
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.MeanRequiredP
wr.Free
WRFD-020102
Load Measurement
VS.HSDPA.MaxRequiredP
wr.Free
WRFD-020102
Load Measurement
Power Required by 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell

Counters
Counter ID
Counter Name
Counter Description
73425896
VS.HSDPA.MC.MeanRequiredPwr
Power Required by 4CHSDPA/DB-HSDPA/DCHSDPA UEs for Cell
73425901
VS.HSDPA.MC.MaxRequiredPwr

by 4C-HSDPA/DB-HSDPA/
DC-HSDPA UEs for Cell
73425903
VS.HSDPA.MC.MinRequiredPwr
Minimum Power Required

by 4C-HSDPA/DB-HSDPA/
specific formulas.
Counter ID
Counter Name
Counter Description
73425900
VS.HSDPA.MC.RequiredP
wr.CUM.NoLog
Accumulated Power
Required by Multi-Carrier
HSDPA UEs for Cell (Before
Log Calculation)
73425899
VS.HSDPA.MC.RequiredP
wr.SAMPLE
Number of Power Reports

Required by Multi-Carrier
HSDPA UEs for Cell
Description
These counters provide the measurement values of the transmit power required by 4C-HSDPA,
3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs in an HSDPA cell. For details, see 3GPP TS
25.433. Multicarrier HSDPA implements load balancing among carriers. These counters comply
Issue 03 (2015-06-30)

3237
BSC6900 UMTS
with section "9.2.1.31 Ic HS-DSCH Required Power Value Information" in 3GPP TS 25.433
(v10.10.0).
Measurement point
the NodeB a COMMON MEASUREMENT REPORT message about the transmit power
required by 4C-HSDPA, 3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs in an HSDPA cell
every 1s. The RNC averages the reported measurement values every 5s to obtain the value of
the power at a sampling point. At the end of the measurement period, the RNC divides the
accumulated numbers by the number of samples to obtain the value of
VS.HSDPA.MC.MeanRequiredPwr in the measurement period. The maximum and minimum
sampled values are taken as the values of VS.HSDPA.MC.MaxRequiredPwr and
VS.HSDPA.MC.MinRequiredPwr. Note: These counters can be measured only when data is
transmitted on the HS-DSCH.
Formula
VS.HSDPA.MC.MeanRequiredPwr = {10}*(log10
[VS.HSDPA.MC.RequiredPwr.CUM.NoLog]-log10
[VS.HSDPA.MC.RequiredPwr.SAMPLE])
Unit
dBm
Issue 03 (2015-06-30)

3238
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.MC.MeanRequiredPwr
WRFD-150250
3C-HSDPA
WRFD-150207
4C-HSDPA
WRFD-150209
DB-HSDPA
WRFD-010696
DC-HSDPA
WRFD-150208

HSDPA
WRFD-010699
WRFD-150227
WRFD-150223
VS.HSDPA.MC.MaxRequiredPwr
DB-HSDPA+MIMO
MC-HSDPA+MIMO
WRFD-150250
3C-HSDPA
WRFD-150207
4C-HSDPA
WRFD-150209
DB-HSDPA
WRFD-010696
DC-HSDPA
WRFD-150208

HSDPA
WRFD-010699
WRFD-150227
WRFD-150223
VS.HSDPA.MC.MinRequiredPwr
DC-HSDPA+MIMO
DC-HSDPA+MIMO
DB-HSDPA+MIMO
MC-HSDPA+MIMO
WRFD-150250
3C-HSDPA
WRFD-150207
4C-HSDPA
WRFD-150209
DB-HSDPA
WRFD-010696
DC-HSDPA
WRFD-150208

HSDPA
WRFD-010699
WRFD-150227
WRFD-150223
DC-HSDPA+MIMO
DB-HSDPA+MIMO
MC-HSDPA+MIMO
DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73425905
VS.MeanTCP.HSDPA.MC
Average DL Transmit Power

of 4C-HSDPA/DB-HSDPA/

3239
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73425910
VS.MaxTCP.HSDPA.MC
Maximum DL Transmit
Power of 4C-HSDPA/DBHSDPA/DC-HSDPA UEs
for Cell
73425912
VS.MinTCP.HSDPA.MC
Minimum DL Transmit
Power of 4C-HSDPA/DBHSDPA/DC-HSDPA UEs
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
73425909
VS.TCP.HSDPA.MC.CUM.
NoLog
VS_TCP_HSDPA_MC_CU
M_NoLog
73425908
VS.TCP.HSDPA.MC.SAMPLE
VS_TCP_HSDPA_MC_SA
MPLE_smp1
Description
These counters provide the downlink transmitted carrier power (TCP) measurement values of
4C-HSDPA, 3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs in a cell. These counters also
include the TCP of 4C-HSDPA+MIMO UEs, 3C-HSDPA+MIMO UEs, DB-HSDPA+MIMO
UEs, and DC-HSDPA+MIMO UEs. They are used to assess the downlink load of the cell and
to evaluate the load balancing between cells after the multicarrier HSDPA is introduced.These
counters comply with section "9.2.4 Transmitted carrier power" in 3GPP TS 25.133 (v10.10.0).
Measurement point
the NodeB a COMMON MEASUREMENT REPORT message about the downlink TCP value
of 4C-HSDPA, 3C-HSDPA, DB-HSDPA, and DC-HSDPA UEs in a cell every 1s. The RNC
averages the reported measurement values every 5s to obtain the downlink TCP value at a
sampling point. At the end of the measurement period, the RNC divides the accumulated
numbers by the number of samples to obtain the value of VS.MeanTCP.HSDPA.MC in the
VS.MaxTCP.HSDPA.MC and VS.MinTCP.HSDPA.MC. Note: These counters can be
measured only when data is transmitted on the HS-DSCH.
Issue 03 (2015-06-30)

3240
BSC6900 UMTS
Formula
VS.MeanTCP.HSDPA.MC = {10}*(log10[VS.TCP.HSDPA.MC.CUM.NoLog]-log10
[VS.TCP.HSDPA.MC.SAMPLE])
Unit
dBm
Related Features
Counter Name
Feature ID
Feature Name
VS.MeanTCP.HSDPA.MC
WRFD-150250
3C-HSDPA
WRFD-150207
4C-HSDPA
WRFD-150209
DB-HSDPA
WRFD-010696
DC-HSDPA
WRFD-150208

HSDPA
WRFD-010699
WRFD-150227
WRFD-150223
VS.MaxTCP.HSDPA.MC
DB-HSDPA+MIMO
MC-HSDPA+MIMO
WRFD-150250
3C-HSDPA
WRFD-150207
4C-HSDPA
WRFD-150209
DB-HSDPA
WRFD-010696
DC-HSDPA
WRFD-150208

HSDPA
WRFD-010699
WRFD-150227
WRFD-150223
Issue 03 (2015-06-30)
DC-HSDPA+MIMO

DC-HSDPA+MIMO
DB-HSDPA+MIMO
MC-HSDPA+MIMO
3241
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.MinTCP.HSDPA.MC
WRFD-150250
3C-HSDPA
WRFD-150207
4C-HSDPA
WRFD-150209
DB-HSDPA
WRFD-010696
DC-HSDPA
WRFD-150208

HSDPA
WRFD-010699
WRFD-150227
WRFD-150223
DC-HSDPA+MIMO
DB-HSDPA+MIMO
MC-HSDPA+MIMO
Number of Times the RTWP of a Cell Is in a Certain Range

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426885
VS.RTWP.0
Number of Times the RTWP

of a Cell Is Less than -108
dBm
73426886
VS.RTWP.1

of a Cell Is Between -108
dBm (Included) and -107
dBm
73426887
VS.RTWP.2

dBm
73426888
VS.RTWP.3

dBm
73426890
VS.RTWP.4

dBm
73426891
VS.RTWP.5

dBm

3242
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426892
VS.RTWP.6

dBm
73426893
VS.RTWP.7

dBm
73426894
VS.RTWP.8

dBm
73426895
VS.RTWP.9

dBm (Included) and -99 dBm
73426896
VS.RTWP.10

of a Cell Is Between -99 dBm
(Included) and -98 dBm
73426897
VS.RTWP.11

73426898
VS.RTWP.12

73426899
VS.RTWP.13

73426900
VS.RTWP.14

73426901
VS.RTWP.15

73426902
VS.RTWP.16

73426903
VS.RTWP.17


3243
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426904
VS.RTWP.18

73426905
VS.RTWP.19

73426906
VS.RTWP.20

73426907
VS.RTWP.21

of a Cell Is Greater than or
Equal to -65 dBm
Description
These counters provide the number of times the RTWP of a cell is in a certain range. You can
divide the value of one counter by the sum of values of these counters to obtain the proportion
of a certain range to the total ranges in a measurement period.These counters comply with section
"9.2.1 Received total wideband power" in 3GPP TS 25.133 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the following figure, when the RNC receives
a COMMON MEASUREMENT REPORT message containing the RTWP of a cell. In this case,
a certain counter is incremented by one.
Formula
None
Issue 03 (2015-06-30)

3244
BSC6900 UMTS
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.RTWP.0
WRFD-020102
Load Measurement
VS.RTWP.1
WRFD-020102
Load Measurement
VS.RTWP.2
WRFD-020102
Load Measurement
VS.RTWP.3
WRFD-020102
Load Measurement
VS.RTWP.4
WRFD-020102
Load Measurement
VS.RTWP.5
WRFD-020102
Load Measurement
VS.RTWP.6
WRFD-020102
Load Measurement
VS.RTWP.7
WRFD-020102
Load Measurement
VS.RTWP.8
WRFD-020102
Load Measurement
VS.RTWP.9
WRFD-020102
Load Measurement
VS.RTWP.10
WRFD-020102
Load Measurement
VS.RTWP.11
WRFD-020102
Load Measurement
VS.RTWP.12
WRFD-020102
Load Measurement
VS.RTWP.13
WRFD-020102
Load Measurement
VS.RTWP.14
WRFD-020102
Load Measurement
VS.RTWP.15
WRFD-020102
Load Measurement
VS.RTWP.16
WRFD-020102
Load Measurement
VS.RTWP.17
WRFD-020102
Load Measurement
VS.RTWP.18
WRFD-020102
Load Measurement
VS.RTWP.19
WRFD-020102
Load Measurement
VS.RTWP.20
WRFD-020102
Load Measurement
VS.RTWP.21
WRFD-020102
Load Measurement

3245
BSC6900 UMTS
Number of Times the Transmitted Carrier Power of a Cell Is in a Certain Range

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426908
VS.TCP.0
Number of Times the

Transmitted Carrier Power of
a Cell Is Between 0%
(Included) and 5%
73426909
VS.TCP.1
Number of Times the

(Included) and 10%
73426910
VS.TCP.2
Number of Times the

(Included) and 15%
73426911
VS.TCP.3
Number of Times the

(Included) and 20%
73426912
VS.TCP.4
Number of Times the

(Included) and 25%
73426913
VS.TCP.5
Number of Times the

(Included) and 30%
73426914
VS.TCP.6
Number of Times the

(Included) and 35%
73426915
VS.TCP.7
Number of Times the

(Included) and 40%
73426916
VS.TCP.8
Number of Times the

(Included) and 45%

3246
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426917
VS.TCP.9
Number of Times the

(Included) and 50%
73426918
VS.TCP.10
Number of Times the

(Included) and 55%
73426919
VS.TCP.11
Number of Times the

(Included) and 60%
73426920
VS.TCP.12
Number of Times the

(Included) and 65%
73426921
VS.TCP.13
Number of Times the

(Included) and 70%
73426922
VS.TCP.14
Number of Times the

(Included) and 75%
73426923
VS.TCP.15
Number of Times the

(Included) and 80%
73426924
VS.TCP.16
Number of Times the

(Included) and 85%
73426925
VS.TCP.17
Number of Times the

(Included) and 90%
73426926
VS.TCP.18
Number of Times the

(Included) and 95%

3247
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426927
VS.TCP.19
Number of Times the

a Cell Is from 95% to 100%
Description
These counters provide the number of times the transmitted carrier power of a cell is in a certain
range. You can divide the value of one counter by the sum of values of these counters to obtain
the proportion of a certain range to the total ranges in a measurement period.These counters
comply with section "9.2.4 Transmitted carrier power" in 3GPP TS 25.133 (v10.10.0).
Measurement point
a COMMON MEASUREMENT REPORT message containing the transmitted carrier power of
a cell. In this case, a certain counter is incremented by one. 3GPP TS 25.302 specifies that the
transmitted carrier power is the ratio between the total transmitted power on one DL carrier from
one UTRAN access point, compared to the maximum power possible to use on that DL carrier
at this moment of time.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3248
BSC6900 UMTS
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.TCP.0
WRFD-020102
Load Measurement
VS.TCP.1
WRFD-020102
Load Measurement
VS.TCP.2
WRFD-020102
Load Measurement
VS.TCP.3
WRFD-020102
Load Measurement
VS.TCP.4
WRFD-020102
Load Measurement
VS.TCP.5
WRFD-020102
Load Measurement
VS.TCP.6
WRFD-020102
Load Measurement
VS.TCP.7
WRFD-020102
Load Measurement
VS.TCP.8
WRFD-020102
Load Measurement
VS.TCP.9
WRFD-020102
Load Measurement
VS.TCP.10
WRFD-020102
Load Measurement
VS.TCP.11
WRFD-020102
Load Measurement
VS.TCP.12
WRFD-020102
Load Measurement
VS.TCP.13
WRFD-020102
Load Measurement
VS.TCP.14
WRFD-020102
Load Measurement
VS.TCP.15
WRFD-020102
Load Measurement
VS.TCP.16
WRFD-020102
Load Measurement
VS.TCP.17
WRFD-020102
Load Measurement
VS.TCP.18
WRFD-020102
Load Measurement
VS.TCP.19
WRFD-020102
Load Measurement

3249
BSC6900 UMTS
Number of Times the Transmitted Carrier Power of All Codes not Used for Physical
HSDPA Channel Transmission Is in a Certain Range for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426928
VS.TCP.NonHS.0
Number of Times the

All Codes not Used for
Physical HSDPA Channel
Transmission Is Between 0%
(Included) and 5% for Cell
73426929
VS.TCP.NonHS.1
Number of Times the

Transmission Is Between 5%
(Included) and 10% for Cell
73426930
VS.TCP.NonHS.2
Number of Times the

Transmission Is Between
10% (Included) and 15% for
Cell
73426931
VS.TCP.NonHS.3
Number of Times the

Cell
73426932
VS.TCP.NonHS.4
Number of Times the

Cell
73426933
VS.TCP.NonHS.5
Number of Times the

Cell

3250
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426934
VS.TCP.NonHS.6
Number of Times the

Cell
73426935
VS.TCP.NonHS.7
Number of Times the

Cell
73426936
VS.TCP.NonHS.8
Number of Times the

Cell
73426937
VS.TCP.NonHS.9
Number of Times the

Cell
73426938
VS.TCP.NonHS.10
Number of Times the

Cell
73426939
VS.TCP.NonHS.11
Number of Times the

Cell

3251
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426940
VS.TCP.NonHS.12
Number of Times the

Cell
73426941
VS.TCP.NonHS.13
Number of Times the

Cell
73426942
VS.TCP.NonHS.14
Number of Times the

Cell
73426943
VS.TCP.NonHS.15
Number of Times the

Cell
73426944
VS.TCP.NonHS.16
Number of Times the

Cell
73426945
VS.TCP.NonHS.17
Number of Times the

Cell

3252
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73426946
VS.TCP.NonHS.18
Number of Times the

Cell
73426947
VS.TCP.NonHS.19
Number of Times the

Transmission Is from 95% to
100% for Cell
Description
These counters provide the number of times the transmitted carrier power of all codes not used
for physical HSDPA channel transmission in a cell is in a certain range. (Physical HSDPA
channels include the HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH, and E-HICH.) You can
divide the value of one counter by the sum of values of these counters to obtain the proportion
of a certain range to the total ranges in a measurement period.These counters comply with section
"9.2.16 Transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH,
E-RGCH or E-HICH transmission" in 3GPP TS 25.133 (v10.10.0).
Measurement point
a COMMON MEASUREMENT REPORT message containing the transmitted carrier power of
all codes not used for physical HSDPA channel transmission. In this case, a certain counter is
incremented by one.
3GPP TS 25.302 specifies that the transmitted carrier power of all codes not used for HSPDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission is the ratio between the total
transmitted power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or EHICH transmission on one DL carrier from one UTRAN access point, and the maximum
transmission power possible to use on that DL carrier at this moment of time.
Issue 03 (2015-06-30)

3253
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.TCP.NonHS.0
WRFD-020102
Load Measurement
VS.TCP.NonHS.1
WRFD-020102
Load Measurement
VS.TCP.NonHS.2
WRFD-020102
Load Measurement
VS.TCP.NonHS.3
WRFD-020102
Load Measurement
VS.TCP.NonHS.4
WRFD-020102
Load Measurement
VS.TCP.NonHS.5
WRFD-020102
Load Measurement
VS.TCP.NonHS.6
WRFD-020102
Load Measurement
VS.TCP.NonHS.7
WRFD-020102
Load Measurement
VS.TCP.NonHS.8
WRFD-020102
Load Measurement
VS.TCP.NonHS.9
WRFD-020102
Load Measurement
VS.TCP.NonHS.10
WRFD-020102
Load Measurement
VS.TCP.NonHS.11
WRFD-020102
Load Measurement
VS.TCP.NonHS.12
WRFD-020102
Load Measurement
VS.TCP.NonHS.13
WRFD-020102
Load Measurement
VS.TCP.NonHS.14
WRFD-020102
Load Measurement
VS.TCP.NonHS.15
WRFD-020102
Load Measurement
VS.TCP.NonHS.16
WRFD-020102
Load Measurement
VS.TCP.NonHS.17
WRFD-020102
Load Measurement
VS.TCP.NonHS.18
WRFD-020102
Load Measurement
VS.TCP.NonHS.19
WRFD-020102
Load Measurement

3254
BSC6900 UMTS
1.12.47 Soft Handover Measurement <per Cell>(SHO.Cell)

Overview
Soft handover is the procedure during which a radio link is added to or deleted from the active
set. When an UE moves or the radio link quality fluctuates, the RNC adds a radio link to the
active set if the RNC detects that the cell of the radio link is of good signal quality. If the quality
of a radio link in a cell in the active set becomes lower than the predefined threshold, the RNC
deletes this radio link from the active set.
A soft handover is considered as a softer handover if the two radio links of the UE connection
are established with cells belonging to the same NodeB.
The RNC determines whether to perform soft handover based on the intra-frequency
measurement of the UE. When the RNC receives a measurement report (MR) from the UE and
determines that a soft handover is required, it sends an ACTIVE SET UPDATE message to the
UE, and starts a timer to wait for the response from the UE. If the RNC receives an ACTIVE
SET UPDATE COMPLETE message from the UE before the timer expires, the soft handover
is considered successful. If the RNC receives an ACTIVE SET UPDATE FAILURE message
from the UE or does not receive any message from the UE before the timer expires, the soft
handover is considered as a failure.
For multi-carrier HSDPA users, this counter is measured only in the cell with the primary carrier.
When the DC-HSUPA Independent Active Sets function is enabled, the number of soft
handovers (including softer handovers) in this function subset are separately measured on the
primary and secondary carriers for DC-HSUPA UEs.
The following figure shows the soft handover procedure.
Issue 03 (2015-06-30)

3255
BSC6900 UMTS
Figure 1-1419 Flow chart of Soft handover
Issue 03 (2015-06-30)

3256
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.SHO.AttRLAdd.Prep
VS.SHO.AMR.Att, VS.SHO.PS.Att,
VS.SHO.AttRLAdd, VS.SHO.SigOnly.Att,
VS.SHO.CS64.Att
VS.SoHO.AttRLAdd
VS.SoHO.SuccRLAdd
VS.SHO.AMR.Succ, VS.SHO.PS.Succ,
VS.SHO.SuccRLAdd,
VS.SHO.SigOnly.Succ,
VS.SHO.CS64.Succ, VS.SHO.AS.1RL,
VS.SHO.AS.2RL, VS.SHO.AS.3RL,
VS.SHO.AS.6RL
VS.SoHO.FailRLAdd.CfgUnsupp,
VS.SoHO.FailRLAdd.NoReply,
VS.SoHO.FailRLAdd.ISR,
VS.SoHO.FailRLAdd.InvCfg
VS.SHO.FailRLAdd.CfgUnsupp,
VS.SHO.FailRLAdd.NoReply,
VS.SHO.FailRLAdd.ISR,
VS.SHO.FailRLAdd.InvCfg
VS.SHO.AMR.Att, VS.SHO.PS.Att,
VS.SHO.AttRLDel, VS.SHO.SigOnly.Att,
VS.SHO.CS64.Att
VS.SoHO.AttRLDel
VS.SoHO.SuccRLDel
VS.SHO.AMR.Succ, VS.SHO.PS.Succ,
VS.SHO.SuccRLDel,
VS.SHO.SigOnly.Succ,
VS.SHO.CS64.Succ, VS.SHO.AS.1RL,
VS.SHO.AS.4RL, VS.SHO.AS.5RL

3257
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180483
VS.SoHO.AttRLA
dd
Number of Radio
Link Addition
Attempts in Softer
Handover for Cell
Earlier than
BSC6900
V900R011
67180484
VS.SoHO.SuccRLAdd
Number of
Successful Radio
Link Additions in
Softer Handover for
Cell
Earlier than
BSC6900
V900R011
67180485
VS.SoHO.FailRLA
dd.CfgUnsupp
Number of Failed
Radio Link
Additions in Softer
Handover for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67180486
VS.SoHO.FailRLA
dd.ISR
Number of Failed
Radio Link
Additions in Softer
Handover for Cell
(Incompatible
Simultaneous
Reconfiguration)
Earlier than
BSC6900
V900R011
67180488
VS.SoHO.FailRLA
dd.InvCfg
Number of Failed
Radio Link
Additions in Softer
Handover for Cell
(Invalid
Configuration)
Earlier than
BSC6900
V900R011
67180489
VS.SoHO.FailRLA
dd.NoReply
Number of Failed
Radio Link
Additions in Softer
Handover due to UE
Earlier than
BSC6900
V900R011
67180490
VS.SoHO.AttRLDe
l
Number of Radio
Link Deletion
Attempts in Softer
Handover for Cell
Earlier than
BSC6900
V900R011

3258
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180491
VS.SoHO.SuccRLDel
Number of
Successful Radio
Link Deletions in
Softer Handover for
Cell
Earlier than
BSC6900
V900R011
67180498
VS.SHO.AttRLAd
d
Number of Radio
Link Addition
Attempts in Soft
Handover for Cell
Earlier than
BSC6900
V900R011
67180499
VS.SHO.SuccRLA
dd
Number of
Successful Radio
Link Additions in
Soft Handover for
Cell
Earlier than
BSC6900
V900R011
67180500
VS.SHO.FailRLAd
d.CfgUnsupp
Number of Failed
Radio Link
Additions in Soft
Handover for Cell
(Configuration
Unsupported)
Earlier than
BSC6900
V900R011
67180501
VS.SHO.FailRLAd
d.ISR
Number of Failed
Radio Link
Additions in Soft
Handover for Cell
(Incompatible
Simultaneous
Reconfiguration)
Earlier than
BSC6900
V900R011
67180503
VS.SHO.FailRLAd
d.InvCfg
Number of Failed
Radio Link
Additions in Soft
Handover for Cell
(Invalid
Configuration)
Earlier than
BSC6900
V900R011
67180504
VS.SHO.FailRLAd
d.NoReply
Number of Failed
Radio Link
Additions in Soft
Handover due to UE
Earlier than
BSC6900
V900R011
67180508
VS.SHO.AttRLDel
Number of Radio
Link Deletion
Attempts in Soft
Handover for Cell
Earlier than
BSC6900
V900R011

3259
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67180509
VS.SHO.SuccRLD
el
Number of
Successful Radio
Link Deletions in
Soft Handover for
Cell
Earlier than
BSC6900
V900R011
67192562
VS.SHO.SigOnly.A
tt
Number of Soft
Handover Attempts
with only Signaling
Connection for Cell
Earlier than
BSC6900
V900R011
67193563
VS.SHO.SigOnly.S
ucc
Number of
Successful Soft
Handovers with only
Signaling
Connection for Cell
Earlier than
BSC6900
V900R011
67193564
VS.SHO.AttRLAd
d.Prep
Number of Soft
Handover Decisions
for Radio Link
Addition for Cell
Earlier than
BSC6900
V900R011
67180519
VS.SHO.AMR.Att
Number of Soft
Handover Attempts
for Cell (AMR)
Earlier than
BSC6900
V900R011
67180520
VS.SHO.AMR.Suc
c
Number of
Successful Soft
Handovers in CS
Domain for Cell
(AMR Service)
Earlier than
BSC6900
V900R011
67180521
VS.SHO.CS64.Att
Number of Soft
Handover Attempts
in CS Domain for
Cell (64 kbit/s
Conversational
Service)
Earlier than
BSC6900
V900R011
67180522
VS.SHO.CS64.Succ
Number of
Successful Soft
Handovers in CS
Domain for Cell (64
kbit/s
Conversational
Service)
Earlier than
BSC6900
V900R011
67203936
VS.SHO.AS.1RL
Mean Number of
UEs with One Radio
Link for Cell
Earlier than
BSC6900
V900R011

3260
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67203937
VS.SHO.AS.2RL
Mean Number of
UEs with Two Radio
Links for Cell
Earlier than
BSC6900
V900R011
67203938
VS.SHO.AS.3RL
Mean Number of
UEs with Three
Radio Links for Cell
Earlier than
BSC6900
V900R011
67203939
VS.SHO.AS.4RL
Mean Number of
UEs with Four Radio
Links for Cell
Earlier than
BSC6900
V900R011
67203940
VS.SHO.AS.5RL
Mean Number of
UEs with Five Radio
Links for Cell
Earlier than
BSC6900
V900R011
67203941
VS.SHO.AS.6RL
Mean Number of
UEs with Six Radio
Links for Cell
Earlier than
BSC6900
V900R011
73393849
VS.SHO.PS.Att
Number of Soft
Handover Attempts
for PS Services for
Cell
BSC6900
V900R012
73393850
VS.SHO.PS.Succ
Number of
Successful Soft
Handovers for PS
Services for Cell
BSC6900
V900R012
73429089
VS.SHO.AttRLReplace
Number of RL
Replacement
Attempts During
Soft Handovers for
Cell
BSC6900
V900R017C00
73429090
VS.SHO.SuccRLR
eplace
Number of
Successful RL
Replacements
During Soft
Handovers for Cell
BSC6900
V900R017C00
Issue 03 (2015-06-30)
Counter
Sub Counter
VS.SHO.AttRLAdd
VS.SoHO.AttRLAdd

3261
BSC6900 UMTS
Counter
Sub Counter
VS.SHO.SuccRLAdd
VS.SoHO.SuccRLAdd
VS.SHO.FailRLAdd.CfgUnsupp
VS.SoHO.FailRLAdd.CfgUnsupp
VS.SHO.FailRLAdd.ISR
VS.SoHO.FailRLAdd.ISR
VS.SHO.FailRLAdd.NoReply
VS.SoHO.FailRLAdd.NoReply
VS.SHO.AttRLDel
VS.SoHO.AttRLDel
VS.SHO.SuccRLDel
VS.SoHO.SuccRLDel
Number of Soft Handover Decisions for Radio Link Addition Initiated by RNC
Counters
Counter ID
Counter Name
Counter Description
67193564
Number of Soft Handover

Decisions for Radio Link
Addition for Cell
Description
This counter provides the number of decisions determined by the RNC to trigger soft handovers
(including softer handovers) with radio link addition. It is measured in the cell where a radio
link is to be added.This counter complies with section "8.3.4 Active set update" in 3GPP TS
25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC determines to
add a radio link during the soft handover (including the softer handover) procedure, this counter
is measured in every cell where a radio link is to be added.
Issue 03 (2015-06-30)

3262
BSC6900 UMTS
Figure 1-1420 A successful soft handover (radio link addition)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover

3263
BSC6900 UMTS
Number of Soft Handover Attempts for Different Service

Counters
Counter ID
Counter Name
Counter Description
67180519
VS.SHO.AMR.Att

Attempts for Cell (AMR)
67192562
VS.SHO.SigOnly.Att

Attempts with only Signaling
Connection for Cell
67180521
VS.SHO.CS64.Att

Attempts in CS Domain for
Cell (64 kbit/s
Conversational Service)
73393849
VS.SHO.PS.Att

Attempts for PS Services for
Cell
Description
These counters provide the number of soft handover attempts for different service types in the
target cell.The preceding counters comply with section "8.3.4 Active set update" in 3GPP TS
25.331 (v10.13.0).
Counter Name
Description
VS.SHO.AMR.Att
Number of soft handover attempts for AMR

types,including narrowband and wideband
AMR services
VS.SHO.SigOnly.Att
Number of soft handover attempts with only

signaling connection
VS.SHO.CS64.Att
Number of soft handover attempts for CS

domain 64 kbit/s Conversational Service
VS.SHO.PS.Att
Number of soft handover attempts for PS

services
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends an
ACTIVE SET UPDATE message to the UE during the soft handover (including the softer
handover) procedure, the counter corresponding to the type of the service where the soft
handover occurs is measured in every cell where a radio link is added or deleted.
Issue 03 (2015-06-30)

3264
BSC6900 UMTS
Figure 1-1421 A successful soft handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AMR.Att
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020201
Intra Node B Softer

Handover
VS.SHO.SigOnly.Att
VS.SHO.CS64.Att
VS.SHO.PS.Att
WRFD-020202
Issue 03 (2015-06-30)

3265
BSC6900 UMTS
Number of Radio Link Addition Attempts in Soft Handover and Softer Handover
Counters
Counter ID
Counter Name
Counter Description
67180498
VS.SHO.AttRLAdd

Addition Attempts in Soft
Handover for Cell
67180483
VS.SoHO.AttRLAdd

Addition Attempts in Softer
Handover for Cell
Description
These counters provide the number of radio link addition attempts in the soft handover. It is
measured in the cell where a radio link is added.The preceding counters comply with section
"8.3.4 Active set update" in 3GPP TS 25.331 (v10.13.0).
Counter Name
Description
VS.SHO.AttRLAdd
Number of radio link addition attempts in the

soft handover (including the softer handover)
VS.SoHO.AttRLAdd
Number of radio link addition attempts in the

softer handover
Measurement point
ACTIVE SET UPDATE message to the UE during the soft handover procedure, this counter is
measured in every cell where a radio link is added.
Issue 03 (2015-06-30)

3266
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLAdd
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020201
Intra Node B Softer

Handover
VS.SoHO.AttRLAdd
Issue 03 (2015-06-30)

3267
BSC6900 UMTS
Counters Related to the Number of Successful Soft Handovers in Different Service

Types
Counters
Counter ID
Counter Name
Counter Description
67180520
VS.SHO.AMR.Succ

Handovers in CS Domain for
Cell (AMR Service)
67193563
VS.SHO.SigOnly.Succ

Handovers with only
Signaling Connection for
Cell
67180522
VS.SHO.CS64.Succ

Handovers in CS Domain for
Cell (64 kbit/s
Conversational Service)
73393850
VS.SHO.PS.Succ

Handovers for PS Services
for Cell
Description
These counters provide the number of successful soft handovers for different service types in
the target cell.The preceding counters comply with section "8.3.4 Active set update" in 3GPP
TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)
Counter Name
Description
VS.SHO.AMR.Succ
Number of successful soft handovers for

AMR services, includeing narrowband and
wideband AMR services
VS.SHO.SigOnly.Succ
Number of successful soft handovers with

only signaling connection
VS.SHO.CS64.Succ
Number of successful soft handovers for CS

voice services of 64 kbit/s
VS.SHO.PS.Succ
Number of the successful soft handovers for

PS services

3268
BSC6900 UMTS
Measurement point
(including the softer handover) procedure, the soft handover is considered successful. In this
case, the counter corresponding to the type of the service where the soft handover occurs is
measured in every cell where a radio link is added or deleted.
Figure 1-1423 A successful soft handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AMR.Succ
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
VS.SHO.SigOnly.Succ
Issue 03 (2015-06-30)

3269
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.SHO.CS64.Succ
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020201
Intra Node B Softer

Handover
VS.SHO.PS.Succ
WRFD-020202
Number of Successful Radio Link Additions in Soft Handover and Softer

Handover
Counters
Counter ID
Counter Name
Counter Description
67180499
VS.SHO.SuccRLAdd

Link Additions in Soft
Handover for Cell
67180484
VS.SoHO.SuccRLAdd

Link Additions in Softer
Handover for Cell
Description
These counters provide the number of successful radio link additions in the soft handover. It is
measured in the cell where a radio link is added.The preceding counters comply with section
Counter Name
Description
VS.SHO.SuccRLAdd
Number of successful radio link additions in

the soft handover (including the softer
handover)
VS.SoHO.SuccRLAdd
Number of successful radio link additions in

the softer handover
Measurement point
Issue 03 (2015-06-30)

3270
BSC6900 UMTS
procedure, the soft handover is considered successful. In this case, this counter is measured in
every cell where a radio link is added.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLAdd
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover

3271
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.SoHO.SuccRLAdd
WRFD-020201
Intra Node B Softer

Handover
Mean Number of UEs with One to Six Radio Link

Counters
Counter ID
Counter Name
Counter Description
67203936
VS.SHO.AS.1RL

One Radio Link for Cell
67203937
VS.SHO.AS.2RL

Two Radio Links for Cell
67203938
VS.SHO.AS.3RL

Three Radio Links for Cell
67203939
VS.SHO.AS.4RL

Four Radio Links for Cell
67203940
VS.SHO.AS.5RL

Five Radio Links for Cell
67203941
VS.SHO.AS.6RL

Six Radio Links for Cell
Description
These counters provide the mean number of UEs with one to six radio link in a cell of the active
set.The preceding counters comply with section "8.3.4 Active set update" in 3GPP TS 25.331
(v10.13.0).
Measurement point
In a measurement period, the RNC periodically takes samples (sampling periodicity is 30
seconds) of the number of UEs with one to six radio link in a cell of the active set. At the end
of the measurement period, the RNC divides the accumulated number by the number of sampling
times to obtain the mean number of UEs with only one to six radio link in a cell of the active set
in the measurement period.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3272
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AS.1RL
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
WRFD-020202
WRFD-020203
VS.SHO.AS.2RL
VS.SHO.AS.3RL
VS.SHO.AS.4RL
VS.SHO.AS.5RL
VS.SHO.AS.6RL
Number of Failed Radio Link Additions in Soft and Softer Handover due to
Different Causes
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67180500
VS.SHO.FailRLAdd.CfgUn
supp

Additions in Soft Handover
Unsupported)
67180485
VS.SoHO.FailRLAdd.CfgU
nsupp

Additions in Softer Handover
Unsupported)
67180486

Simultaneous
Reconfiguration)
67180488
VS.SoHO.FailRLAdd.InvCf
g

for Cell (Invalid
Configuration)

3273
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67180501

Simultaneous
Reconfiguration)
67180503

for Cell (Invalid
Configuration)
Description
These counters provide the number of failed radio link additions in the soft handover due to
different causes. They are measured in the cell where a radio link is added.The preceding counters
comply with section "8.3.4 Active set update" in 3GPP TS 25.331 (v10.13.0).
Counter Name
Description
VS.SHO.FailRLAdd.CfgUnsupp
Number of failed radio link additions in the

due to configuration unsupported
VS.SoHO.FailRLAdd.CfgUnsupp

softer handover due to configuration
unsupported

softer handover due to incompatible
simultaneous reconfiguration

softer handover due to invalid configuration

due to incompatible simultaneous
reconfiguration

due to invalid configuration
Measurement point
ACTIVE SET UPDATE FAILURE message from the UE during the soft handover procedure,
Issue 03 (2015-06-30)

3274
BSC6900 UMTS
this counter is measured on the basis of the different causes carried in the message in every cell
where a radio link is added.
Figure 1-1425 Soft handover procedure (failed operation)
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.FailRLAdd.CfgUn
supp
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
VS.SoHO.FailRLAdd.CfgU
nsupp
WRFD-020201
Intra Node B Softer

Handover
WRFD-020201
Intra Node B Softer

Handover
VS.SoHO.FailRLAdd.InvCf
g
WRFD-020201
Intra Node B Softer

Handover
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover

3275
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
Number of Failed Radio Link Additions in Soft and Softer Handover due to UE No
Response
Counters
Counter ID
Counter Name
Counter Description
67180504

due to UE No Response for
Cell
67180489
VS.SoHO.FailRLAdd.NoRe
ply

due to UE No Response for
Cell
Description
These counters provide the number of failed radio link additions in the case that there is no
response from the UE in the soft handover. It is measured in the cell where a radio link is
added.The preceding counters comply with section "8.3.4 Active set update" in 3GPP TS 25.331
(v10.13.0).
Counter Name
Description

case that there is no response from the UE in
the soft handover(including the softer
handover)
VS.SoHO.FailRLAdd.NoReply
Number of failed radio link additions because

there is no response from the UE in the softer
handover
Measurement point
The measurement is triggered at point A, as shown in the figure. During the soft handover, when
the RNC sends an ACTIVE SET UPDATE message to the UE, it starts a timer to wait for the
Issue 03 (2015-06-30)

3276
BSC6900 UMTS
response from the UE. If the RNC does not receive a response from the UE before the timer
expires, this counter is measured in every cell where a radio link is added.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
VS.SoHO.FailRLAdd.NoRe
ply
WRFD-020201
Intra Node B Softer

Handover

3277
BSC6900 UMTS
Number of Radio Link Deletion Attempts in Soft Handover and Softer Handover
Counters
Counter ID
Counter Name
Counter Description
67180508
VS.SHO.AttRLDel

Deletion Attempts in Soft
Handover for Cell
67180490
VS.SoHO.AttRLDel

Deletion Attempts in Softer
Handover for Cell
Description
These counters provide the number of radio link deletion attempts in the soft handover. It is
measured in the cell where a radio link is deleted.The preceding counters comply with section
Counter Name
Description
VS.SHO.AttRLDel
Number of radio link deletion attempts in the

VS.SoHO.AttRLDel
Number of radio link deletion attempts in the

softer handover
Measurement point
ACTIVE SET UPDATE message to the UE during the soft handover procedure, this counter is
measured in every cell where a radio link is deleted.
Issue 03 (2015-06-30)

3278
BSC6900 UMTS
Figure 1-1427 A successful soft handover (radio link deletion)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLDel
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020201
Intra Node B Softer

Handover
VS.SoHO.AttRLDel
Issue 03 (2015-06-30)

3279
BSC6900 UMTS
Number of Successful Radio Link Deletions in Soft Handover and Softer Handover
Counters
Counter ID
Counter Name
Counter Description
67180509
VS.SHO.SuccRLDel

Link Deletions in Soft
Handover for Cell
67180491
VS.SoHO.SuccRLDel

Link Deletions in Softer
Handover for Cell
Description
These counters provide the number of successful radio link deletions in the soft handover. It is
measured in the cell where a radio link is deleted.The preceding counters comply with section
Counter Name
Description
VS.SHO.SuccRLDel
Number of successful radio link deletions in

the soft handover (including the softer
handover)
VS.SoHO.SuccRLDel
Number of successful radio link deletions in

the softer handover
Measurement point
The measurement is triggered at point C in the figure. Each time the RNC receives an ACTIVE
SET UPDATE COMPLETE message from the UE during the soft handover procedure, the soft
handover is considered successful. In this case, this counter is measured in every cell where a
radio link is deleted.
Issue 03 (2015-06-30)

3280
BSC6900 UMTS
Figure 1-1428 A successful soft handover (radio link deletion)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLDel
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
WRFD-020201
Intra Node B Softer

Handover
VS.SoHO.SuccRLDel
Issue 03 (2015-06-30)

3281
BSC6900 UMTS
Number of RL Replacement Attempts During Soft Handovers for Cell

Counters
Counter ID
Counter Name
Counter Description
73429089
VS.SHO.AttRLReplace
Number of RL Replacement
Attempts During Soft
Handovers for Cell
Description
This counter provides the number of radio link (RL) replacement attempts during soft handovers.
It is measured in the cell to which the RL to be removed belongs.
Measurement point
The measurement is triggered at point B. When the RNC sends an ACTIVE SET UPDATE
message to the UE during a soft handover, if the number of cells in the active set reaches the
maximum, this counter is measured in the cell to which the RL to be removed belongs if an RL
is added and at the same time another RL is removed (referred to as RL replacement).
Figure 1-1429 VS.SHO.AttRLReplace
Issue 03 (2015-06-30)

3282
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttRLReplace
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
Number of Successful RL Replacements During Soft Handovers for Cell

Counters
Counter ID
Counter Name
Counter Description
73429090
VS.SHO.SuccRLReplace
Number of Successful RL
Replacements During Soft
Handovers for Cell
Description
This counter provides the number of successful RL replacements during soft handovers. It is
measured in the cell to which the RL to be removed belongs.
Measurement point
The measurement is triggered at point C. When the RNC receives an ACTIVE SET UPDATE
COMPLETE message from the UE during a soft handover, the RNC determines that the soft
handover is successful. If the number of cells in the active set reaches the maximum before a
soft handover, and an RL is added and at the same time another RL is removed (referred to as
RL replacement)during the soft handover, this counter is measured in the cell to which the RL
removed belongs.
Issue 03 (2015-06-30)

3283
BSC6900 UMTS
Figure 1-1430 VS.SHO.SuccRLReplace
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.SuccRLReplace
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover

3284
BSC6900 UMTS
1.12.48 Target SIR Measurement <per Cell>(SIR.Cell)

Overview
The Signal-to-Interference Ratio (SIR) target value used in the uplink out loop power control
on the DCH is adjusted dynamically based on the uplink Block Error Rate (BLER) or Bit Error
Rate (BER). The uplink outer loop power control adjusts the transmit power of the UE to lower
the interference on other UEs while ensuring the service quality of the UE.
Based on different service classes and traffic rates, this measurement indicates the ratio of the
duration when the target SIR reaches the maximum value to the total period when the uplink
outer loop power control is performed.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199814
VS.ULSirTarget.O
ut.AMR

SIR Target of AMR
Services Reaches
Maximum Value
Earlier than
BSC6900
V900R011
73394086
VS.ULSirTarget.O
ut.CS64

SIR Target of CS 64
Kbit/s
Conversational
Services Reaches
Maximum Value for
cell
BSC6900
V900R012
67199823
VS.ULSirTarget.O
ut.PS.BE.DCH.8

SIR Target of PS 8
Kbit/s BE Services
Reaches Maximum
Value
Earlier than
BSC6900
V900R011
67199824
VS.ULSirTarget.O
ut.PS.BE.DCH.16

SIR Target of PS 16
Kbit/s BE Services
Reaches Maximum
Value
Earlier than
BSC6900
V900R011
67199825
VS.ULSirTarget.O
ut.PS.BE.DCH.32

SIR Target of PS 32
Kbit/s BE Services
Reaches Maximum
Value
Earlier than
BSC6900
V900R011

3285
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67199826
VS.ULSirTarget.O
ut.PS.BE.DCH.64

SIR Target of PS 64
Kbit/s BE Services
Reaches Maximum
Value
Earlier than
BSC6900
V900R011
67199827
VS.ULSirTarget.O
ut.PS.BE.DCH.128

SIR Target of PS 128
Kbit/s BE Services
Reaches Maximum
Value
Earlier than
BSC6900
V900R011
67199828
VS.ULSirTarget.O
ut.PS.BE.DCH.144

Kbit/s BE Services
Reaches Maximum
Value
Earlier than
BSC6900
V900R011
67199829
VS.ULSirTarget.O
ut.PS.BE.DCH.256

Kbit/s BE Services
Reaches Maximum
Value
Earlier than
BSC6900
V900R011
67199830
VS.ULSirTarget.O
ut.PS.BE.DCH.384

Kbit/s BE Services
Reaches Maximum
Value
Earlier than
BSC6900
V900R011
None
SIR Target Measurement for Different Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199814
VS.ULSirTarget.Out.AMR
Rate of Duration that SIR

Target of AMR Services
Reaches Maximum Value

3286
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394086
VS.ULSirTarget.Out.CS64

Target of CS 64 Kbit/s
Reaches Maximum Value for
cell
67199823
VS.ULSirTarget.Out.PS.BE.
DCH.8

Target of PS 8 Kbit/s BE
Services Reaches Maximum
Value
67199824
DCH.16

Value
67199825
DCH.32

Value
67199826
DCH.64

Value
67199827
DCH.128

Value
67199828
DCH.144

Value
67199829
DCH.256

Value
67199830
DCH.384

Value
specific formulas.
Issue 03 (2015-06-30)

3287
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67184436
UlSirTarget.Out.AMR.Out
Duration of AMR Sir Target

Exceeding the Maximum
Value for Cell
67184489
UlSirTarget.Out.AMR.Total
Duration of Total Elapsed

Time of AMR for Cell
67184440
UlSirTarget.Out.CSRT.
64.Out
Duration of CS 64 kbit/s Sir

Target Exceeding the
Maximum Value for Cell
67184493
UlSirTarget.Out.CSRT.
64.Total

Time of CS 64 kbit/s for Cell
67184449
UlSirTarget.Out.PSNRT.
128.Out
Duration of PSNRT 128 kbit/

s Sir Target Exceeding the
67184502
128.Total

Time of PSNRT 128 kbit/s
for Cell
67184450
144.Out

67184503
144.Total

for Cell
67184446
16.Out
Duration of PSNRT 16 kbit/s

Sir Target Exceeding the
67184499
16.Total

Time of PSNRT 16 kbit/s for
Cell
67184451
256.Out

67184504
256.Total

for Cell
67184447
32.Out

67184500
32.Total

Cell

3288
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67184452
384.Out

67184505
384.Total

for Cell
67184448
64.Out

67184501
64.Total

Cell
67184445
8.Out

67184498
8.Total

Cell
Description
These counters provide the percentage of the duration when the signal-to-interference ratio (SIR)
target of uplink outer-loop power control reaches its upper limit to the total duration of the uplink
outer-loop power control for different services of all UEs in the best cell, such as the adaptive
multirate (AMR) service, CS 64 kbit/s conversational service, and PS BE service. The
VS.ULSirTarget.Out.AMR counter applies only to narrowband AMR service.
Measurement point
In a measurement period, the RNC periodically takes samples of the SIR target for different
services of all UEs in the best cell, such as the AMR service, CS 64 kbit/s conversational service,
and PS BE service in the best cell. When the SIR target of a UE reaches its upper limit, the
duration when the SIR target reaches its upper limit is accumulated. At the end of the
measurement period, this counter is calculated by dividing this duration by the total duration of
outer-loop power control.
Formula
VS.ULSirTarget.Out.AMR = {100}*[UlSirTarget.Out.AMR.Out]/
[UlSirTarget.Out.AMR.Total]
VS.ULSirTarget.Out.CS64 = {100}*[UlSirTarget.Out.CSRT.64.Out]/[UlSirTarget.Out.CSRT.
64.Total]
Issue 03 (2015-06-30)

3289
BSC6900 UMTS
VS.ULSirTarget.Out.PS.BE.DCH.8 = {100}*[UlSirTarget.Out.PSNRT.8.Out]/
[UlSirTarget.Out.PSNRT.8.Total]
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ULSirTarget.Out.AMR
WRFD-020503
VS.ULSirTarget.Out.CS64
WRFD-020503
DCH.8
WRFD-020503
DCH.16
WRFD-020503
DCH.32
WRFD-020503
DCH.64
WRFD-020503
DCH.128
WRFD-020503
DCH.144
WRFD-020503
DCH.256
WRFD-020503

3290
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
DCH.384
WRFD-020503
1.12.49 SPI Measurement <per Cell>(SPI.Cell)

Overview
This function subset is used to monitor and assess the performance of the feature of Differentiated
Service Based on SPI Weight. It provides the following information: (1) Number of times that
the downlink throughput of HSDPA services is within each range based on the service level. (2)
Number of times that the uplink throughput of HSUPA services is within each range based on
the service level. (3) Number of bytes sent in downlink on HSDPA MAC-d flows and the mean
downlink throughput of a single HSDPA MAC-d flow based on the service level. (4) Number
of bytes received in uplink on HSUPA MAC-d flows and the mean uplink throughput of a single
HSUPA MAC-d flow based on the service level.The measurement item is measured only when
the SPI measure function is activated using the SET UDPUCFGDATA command with
CellCountersMeasOBJCtrlSwitch set to Spi or QosAndSpi.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421554
VS.HSDPA.SPI8Be
ChThroughput.0
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 0 kbit/s and
32 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421555
VS.HSDPA.SPI8Be
ChThroughput.1
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 32 kbit/s
and 64 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012

3291
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421556
VS.HSDPA.SPI8Be
ChThroughput.2
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 64 kbit/s
and 256 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421557
VS.HSDPA.SPI8Be
ChThroughput.3
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 256 kbit/s
and 512 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421558
VS.HSDPA.SPI8Be
ChThroughput.4
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 512 kbit/s
and 768 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421559
VS.HSDPA.SPI8Be
ChThroughput.5
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 768 kbit/s
and 1024 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421560
VS.HSDPA.SPI8Be
ChThroughput.6
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 1024 kbit/s
Measurement Period
for Cell
BSC6900
V900R012

3292
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421561
VS.HSDPA.SPI8Be
ChThroughput.7
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 1536 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421562
VS.HSDPA.SPI8Be
ChThroughput.8
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 2048 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421563
VS.HSDPA.SPI8Be
ChThroughput.9
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 3072 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421564
VS.HSDPA.SPI8Be
ChThroughput.10
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 4096 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421565
VS.HSDPA.SPI8Be
ChThroughput.11
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 6144 kbit/s
Measurement Period
for Cell
BSC6900
V900R012

3293
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421566
VS.HSDPA.SPI8Be
ChThroughput.12
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
Between 8192 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421567
VS.HSDPA.SPI8Be
ChThroughput.13
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 8
larger than 12288
kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421568
VS.HSDPA.SPI5Be
ChThroughput.0
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
32 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421569
VS.HSDPA.SPI5Be
ChThroughput.1
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 32 kbit/s
and 64 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421570
VS.HSDPA.SPI5Be
ChThroughput.2
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 64 kbit/s
and 256 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012

3294
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421571
VS.HSDPA.SPI5Be
ChThroughput.3
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 256 kbit/s
and 512 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421572
VS.HSDPA.SPI5Be
ChThroughput.4
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 512 kbit/s
and 768 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421573
VS.HSDPA.SPI5Be
ChThroughput.5
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 768 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421574
VS.HSDPA.SPI5Be
ChThroughput.6
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 1024 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421575
VS.HSDPA.SPI5Be
ChThroughput.7
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 1536 kbit/s
Measurement Period
for Cell
BSC6900
V900R012

3295
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421576
VS.HSDPA.SPI5Be
ChThroughput.8
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 2048 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421577
VS.HSDPA.SPI5Be
ChThroughput.9
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 3072 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421578
VS.HSDPA.SPI5Be
ChThroughput.10
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 4096 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421579
VS.HSDPA.SPI5Be
ChThroughput.11
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 6144 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421580
VS.HSDPA.SPI5Be
ChThroughput.12
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
Between 8192 kbit/s
Measurement Period
for Cell
BSC6900
V900R012

3296
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421581
VS.HSDPA.SPI5Be
ChThroughput.13
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 5
larger than 12288
kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421582
VS.HSDPA.SPI2Be
ChThroughput.0
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
32 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421583
VS.HSDPA.SPI2Be
ChThroughput.1
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 32 kbit/s
and 64 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421584
VS.HSDPA.SPI2Be
ChThroughput.2
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 64 kbit/s
and 256 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421585
VS.HSDPA.SPI2Be
ChThroughput.3
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 256 kbit/s
and 512 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012

3297
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421586
VS.HSDPA.SPI2Be
ChThroughput.4
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 512 kbit/s
and 768 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421587
VS.HSDPA.SPI2Be
ChThroughput.5
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 768 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421588
VS.HSDPA.SPI2Be
ChThroughput.6
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 1024 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421589
VS.HSDPA.SPI2Be
ChThroughput.7
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 1536 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421590
VS.HSDPA.SPI2Be
ChThroughput.8
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 2048 kbit/s
Measurement Period
for Cell
BSC6900
V900R012

3298
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421591
VS.HSDPA.SPI2Be
ChThroughput.9
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 3072 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421592
VS.HSDPA.SPI2Be
ChThroughput.10
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 4096 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421593
VS.HSDPA.SPI2Be
ChThroughput.11
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 6144 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421594
VS.HSDPA.SPI2Be
ChThroughput.12
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
Between 8192 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421595
VS.HSDPA.SPI2Be
ChThroughput.13
Number of Times of
Mean Downlink
Throughput of
HSDPA BE Services
with SPI Set to 2
larger than 12288
kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012

3299
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421596
VS.HSUPA.SPI8Be
ChThroughput.0
Number of Times of
Mean Downlink
Throughput of
HSDPANumber of
Times of Mean
Uplink Throughput
of HSUPA BE
Services with SPI Set
to 8 Between 0 kbit/s
and 32 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421597
VS.HSUPA.SPI8Be
ChThroughput.1
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 32 kbit/s
and 64 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421598
VS.HSUPA.SPI8Be
ChThroughput.2
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 64 kbit/s
and 256 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421599
VS.HSUPA.SPI8Be
ChThroughput.3
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 256 kbit/s
and 512 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012

3300
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421600
VS.HSUPA.SPI8Be
ChThroughput.4
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 512 kbit/s
and 768 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421601
VS.HSUPA.SPI8Be
ChThroughput.5
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 768 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421602
VS.HSUPA.SPI8Be
ChThroughput.6
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 1024 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421603
VS.HSUPA.SPI8Be
ChThroughput.7
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 1536 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421604
VS.HSUPA.SPI8Be
ChThroughput.8
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 2048 kbit/s
Measurement Period
for Cell
BSC6900
V900R012

3301
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421605
VS.HSUPA.SPI8Be
ChThroughput.9
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
Between 3072 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421606
VS.HSUPA.SPI8Be
ChThroughput.10
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 8
larger than 4096 kbit/
s in a Measurement
Period for Cell
BSC6900
V900R012
73421607
VS.HSUPA.SPI5Be
ChThroughput.0
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
32 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421608
VS.HSUPA.SPI5Be
ChThroughput.1
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 32 kbit/s
and 64 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421609
VS.HSUPA.SPI5Be
ChThroughput.2
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 64 kbit/s
and 256 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012

3302
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421610
VS.HSUPA.SPI5Be
ChThroughput.3
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 256 kbit/s
and 512 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421611
VS.HSUPA.SPI5Be
ChThroughput.4
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 512 kbit/s
and 768 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421612
VS.HSUPA.SPI5Be
ChThroughput.5
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 768 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421613
VS.HSUPA.SPI5Be
ChThroughput.6
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 1024 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421614
VS.HSUPA.SPI5Be
ChThroughput.7
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 1536 kbit/s
Measurement Period
for Cell
BSC6900
V900R012

3303
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421615
VS.HSUPA.SPI5Be
ChThroughput.8
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 2048 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421616
VS.HSUPA.SPI5Be
ChThroughput.9
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
Between 3072 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421617
VS.HSUPA.SPI5Be
ChThroughput.10
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 5
s in a Measurement
Period for Cell
BSC6900
V900R012
73421618
VS.HSUPA.SPI2Be
ChThroughput.0
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
32 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421619
VS.HSUPA.SPI2Be
ChThroughput.1
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 32 kbit/s
and 64 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012

3304
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421620
VS.HSUPA.SPI2Be
ChThroughput.2
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 64 kbit/s
and 256 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421621
VS.HSUPA.SPI2Be
ChThroughput.3
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 256 kbit/s
and 512 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421622
VS.HSUPA.SPI2Be
ChThroughput.4
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 512 kbit/s
and 768 kbit/s in a
Measurement Period
for Cell
BSC6900
V900R012
73421623
VS.HSUPA.SPI2Be
ChThroughput.5
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 768 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421624
VS.HSUPA.SPI2Be
ChThroughput.6
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 1024 kbit/s
Measurement Period
for Cell
BSC6900
V900R012

3305
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421625
VS.HSUPA.SPI2Be
ChThroughput.7
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 1536 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421626
VS.HSUPA.SPI2Be
ChThroughput.8
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 2048 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421627
VS.HSUPA.SPI2Be
ChThroughput.9
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
Between 3072 kbit/s
Measurement Period
for Cell
BSC6900
V900R012
73421628
VS.HSUPA.SPI2Be
ChThroughput.10
Number of Times of
Mean Uplink
Throughput of
HSUPA BE Services
with SPI Set to 2
s in a Measurement
Period for Cell
BSC6900
V900R012
73421629
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI2
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
with SPI Set to 2 for
Cell
BSC6900
V900R012

3306
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421630
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI3
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421631
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI4
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421632
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI5
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421633
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI6
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421634
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI7
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421635
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI8
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421636
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI9
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012

3307
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421637
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI10
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73444436
VS.HSDPA.BeChT
hroughput.TotalBy
tes.SPI11
Number of Bytes
Sent in Downlink on
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R016C00
73421638
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI2
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421639
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI3
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421640
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI4
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421641
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI5
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421642
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI6
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012

3308
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73421643
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI7
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421644
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI8
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421645
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI9
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73421646
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI10
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73444438
VS.HSUPA.BeChT
hroughput.TotalBy
tes.SPI11
Number of Bytes
Received in Uplink
on HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R016C00
73439855
VS.HSDPA.BeChT
hroughput.SPI2
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439856
VS.HSDPA.BeChT
hroughput.SPI3
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012

3309
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73439857
VS.HSDPA.BeChT
hroughput.SPI4
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439858
VS.HSDPA.BeChT
hroughput.SPI5
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439859
VS.HSDPA.BeChT
hroughput.SPI6
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439860
VS.HSDPA.BeChT
hroughput.SPI7
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439861
VS.HSDPA.BeChT
hroughput.SPI8
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439862
VS.HSDPA.BeChT
hroughput.SPI9
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439863
VS.HSDPA.BeChT
hroughput.SPI10
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012

3310
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73444437
VS.HSDPA.BeChT
hroughput.SPI11
Mean Downlink
Throughput of
HSDPA MAC-d
flow of BE Services
Cell
BSC6900
V900R016C00
73439864
VS.HSUPA.BeChT
hroughput.SPI2
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439865
VS.HSUPA.BeChT
hroughput.SPI3
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439866
VS.HSUPA.BeChT
hroughput.SPI4
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439867
VS.HSUPA.BeChT
hroughput.SPI5
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439868
VS.HSUPA.BeChT
hroughput.SPI6
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439869
VS.HSUPA.BeChT
hroughput.SPI7
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012

3311
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73439870
VS.HSUPA.BeChT
hroughput.SPI8
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439871
VS.HSUPA.BeChT
hroughput.SPI9
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73439872
VS.HSUPA.BeChT
hroughput.SPI10
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R012
73444439
VS.HSUPA.BeChT
hroughput.SPI11
Mean Uplink
Throughput of
HSUPA MAC-d
flow of BE Services
Cell
BSC6900
V900R016C00
None
Number of Times of Downlink Throughput of BE Services with SPI Set to 8 with

a Certain Range in a Measurement Period for HSDPA Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421554
VS.HSDPA.SPI8BeChThroughput.0
Number of Times of Mean

Downlink Throughput of
HSDPA BE Services with
SPI Set to 8 Between 0 kbit/s
and 32 kbit/s in a
Measurement Period for Cell

3312
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421555

SPI Set to 8 Between 32 kbit/
s and 64 kbit/s in a
73421556

73421557

SPI Set to 8 Between 256
kbit/s and 512 kbit/s in a
73421558

73421559

73421560

73421561


3313
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421562

73421563

73421564

73421565

73421566

73421567

SPI Set to 8 larger than 12288
kbit/s in a Measurement
Period for Cell
Description
These counters provide the number of times that the average downlink throughput of MAC-d
flows carrying BE services whose SPIs are set to eight falls within each range in the HSDPA
serving cell. For DC-HSDPA users, this counter is measured only in the primary cell based on
the total throughput on the primary and secondary carriers.
Issue 03 (2015-06-30)

3314
BSC6900 UMTS
Measurement point
In the HSDPA serving cell, the RNC samples the average downlink throughput of MAC-d flows
carrying each BE service whose SPI is set to eight at the Radio Link Control (RLC) layer every
20s. The measured data excludes the RLC headers and retransmitted data. When the throughput
falls within a certain range, the corresponding counter is increased by one. At the end of the
measurement period, the number of times the throughput falls into each range is accumulated.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008


3315
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008


Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421568

and 32 kbit/s in a
73421569

73421570

73421571

73421572


3316
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421573

73421574

73421575

73421576

73421577

73421578

73421579


3317
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421580

73421581

Period for Cell
Description
flows carrying BE services whose SPIs are set to five falls within each range. For DC-HSDPA
users, this counter is measured only in the primary cell based on the total throughput on the
primary and secondary carriers.
Measurement point
carrying each BE service whose SPI is set to five at the Radio Link Control (RLC) layer every
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008


3318
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008


Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421582

and 32 kbit/s in a

3319
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421583

73421584

73421585

73421586

73421587

73421588

73421589


3320
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421590

73421591

73421592

73421593

73421594

73421595

Period for Cell
Description
flows carrying BE services whose SPIs are set to two falls within each range in the HSDPA
serving cell. For DC-HSDPA users, this counter is measured only in the primary cell based on
the total throughput on the primary and secondary carriers.
Issue 03 (2015-06-30)

3321
BSC6900 UMTS
Measurement point
carrying each BE service whose SPI is set to two at the Radio Link Control (RLC) layer every
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008

WRFD-01061008


3322
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-01061008

WRFD-01061008

Number of Times of Uplink Throughput of BE Services with SPI Set to 8 with a

Certain Range in a Measurement Period for HSUPA Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421596
VS.HSUPA.SPI8BeChThroughput.0

HSDPANumber of Times of
HSUPA BE Services with
and 32 kbit/s in a
73421597

Uplink Throughput of
73421598

73421599


3323
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421600

73421601

73421602

73421603

73421604

73421605

73421606

Period for Cell

3324
BSC6900 UMTS
Description
These counters provide the number of times that the average uplink throughput of MAC-d flows
carrying BE services whose SPIs are set to eight when the throughput falls within each range in
the HSUPA serving cell. For DC-HSUPA users, these counters are measured only in the primary
cell based on the total throughput on the primary and secondary carriers.
Measurement point
In the HSUPA serving cell, the RNC samples the average uplink throughput of MAC-d flows
carrying each BE service whose SPI is set to eight at the Radio Link Control (RLC) layer every
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206


3325
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-01061206


Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421607

and 32 kbit/s in a
73421608

73421609

73421610

73421611


3326
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421612

73421613

73421614

73421615

73421616

73421617

Period for Cell
Description
carrying BE services whose SPIs are set to five when the throughput falls within each range in
Issue 03 (2015-06-30)

3327
BSC6900 UMTS
Measurement point
carrying each BE service whose SPI is set to five at the Radio Link Control (RLC) layer every
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206


3328
BSC6900 UMTS

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421618

and 32 kbit/s in a
73421619

73421620

73421621

73421622

73421623


3329
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421624

73421625

73421626

73421627

73421628

Period for Cell
Description
carrying BE services whose SPIs are set to two when the throughput falls within each range in
Measurement point
carrying each BE service whose SPI is set to two at the Radio Link Control (RLC) layer every
Issue 03 (2015-06-30)

3330
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206

WRFD-01061206


3331
BSC6900 UMTS
Number of Bytes Sent on Downlink HSDPA Mac-d flow of BE Services with SPI
Setting to Different Values
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421629
ut.TotalBytes.SPI2
Number of Bytes Sent in

Downlink on HSDPA MACd flow of BE Services with
SPI Set to 2 for Cell
73421630
ut.TotalBytes.SPI3

73421631
ut.TotalBytes.SPI4

73421632
ut.TotalBytes.SPI5

73421633
ut.TotalBytes.SPI6

73421634
ut.TotalBytes.SPI7

73421635
ut.TotalBytes.SPI8

73421636
ut.TotalBytes.SPI9

73421637
ut.TotalBytes.SPI10


3332
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73444436
ut.TotalBytes.SPI11

Description
These counters provide the number of bytes that are sent on downlink HSDPA MAC-d flows
carrying BE services with different SPIs. For DC-HSDPA users, this counter is measured only
in the primary cell based on the total number of bytes sent on the primary and secondary carriers.
Measurement point
A counter is measured when the data of a BE service with the corresponding SPI is sent at the
RLC layer on the downlink. The measured data excludes the RLC headers and retransmitted
data.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ut.TotalBytes.SPI2
WRFD-01061008

ut.TotalBytes.SPI3
WRFD-01061008

ut.TotalBytes.SPI4
WRFD-01061008

ut.TotalBytes.SPI5
WRFD-01061008

ut.TotalBytes.SPI6
WRFD-01061008

ut.TotalBytes.SPI7
WRFD-01061008

ut.TotalBytes.SPI8
WRFD-01061008


3333
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
ut.TotalBytes.SPI9
WRFD-01061008

ut.TotalBytes.SPI10
WRFD-01061008

ut.TotalBytes.SPI11
WRFD-01061008

Number of Bytes Received on Uplink HSUPA Mac-d flow of BE Services with SPI
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421638
ut.TotalBytes.SPI2
Number of Bytes Received in

Uplink on HSUPA MAC-d
flow of BE Services with SPI
Set to 2 for Cell
73421639
ut.TotalBytes.SPI3

Set to 3 for Cell
73421640
ut.TotalBytes.SPI4

Set to 4 for Cell
73421641
ut.TotalBytes.SPI5

Set to 5 for Cell
73421642
ut.TotalBytes.SPI6

Set to 6 for Cell
73421643
ut.TotalBytes.SPI7

Set to 7 for Cell

3334
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421644
ut.TotalBytes.SPI8

Set to 8 for Cell
73421645
ut.TotalBytes.SPI9

Set to 9 for Cell
73421646
ut.TotalBytes.SPI10

Set to 10 for Cell
73444438
ut.TotalBytes.SPI11

Set to 11 for Cell
Description
These counters provide the number of bytes that are received on uplink HSUPA MAC-d flows
carrying BE services with different SPIs.For DC-HSUPA users, this counter is measured only
in the primary cell based on the total number of bytes received on the primary and secondary
carriers.
Measurement point
A counter is measured when the data of a BE service with the corresponding SPI is sent at the
RLC layer on the uplink. The measured data excludes the RLC headers and retransmitted data.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ut.TotalBytes.SPI2
WRFD-01061206


3335
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
ut.TotalBytes.SPI3
WRFD-01061206

ut.TotalBytes.SPI4
WRFD-01061206

ut.TotalBytes.SPI5
WRFD-01061206

ut.TotalBytes.SPI6
WRFD-01061206

ut.TotalBytes.SPI7
WRFD-01061206

ut.TotalBytes.SPI8
WRFD-01061206

ut.TotalBytes.SPI9
WRFD-01061206

ut.TotalBytes.SPI10
WRFD-01061206

ut.TotalBytes.SPI11
WRFD-01061206

Mean Downlink Throughput of HSDPA Mac-d flow of BE Services with SPI

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73439855
ut.SPI2

of HSDPA MAC-d flow of
BE Services with SPI Set to 2
for Cell
73439856
ut.SPI3

for Cell
73439857
ut.SPI4

for Cell

3336
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73439858
ut.SPI5

for Cell
73439859
ut.SPI6

for Cell
73439860
ut.SPI7

for Cell
73439861
ut.SPI8

for Cell
73439862
ut.SPI9

for Cell
73439863
ut.SPI10

BE Services with SPI Set to
10 for Cell
73444437
ut.SPI11

BE Services with SPI Set to
11 for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421655
ut.Times.SPI10
ut.Times.SPI10
73428697
ut.Times.SPI11
ut.Times.SPI11
73421647
ut.Times.SPI2
ut.Times.SPI2

3337
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73421648
ut.Times.SPI3
ut.Times.SPI3
73421649
ut.Times.SPI4
ut.Times.SPI4
73421650
ut.Times.SPI5
ut.Times.SPI5
73421651
ut.Times.SPI6
ut.Times.SPI6
73421652
ut.Times.SPI7
ut.Times.SPI7
73421653
ut.Times.SPI8
ut.Times.SPI8
73421654
ut.Times.SPI9
ut.Times.SPI9
Description
These counters provide the downlink average throughput of HSDPA Mac-d flows carrying BE
services with different SPIs. For DC-HSDPA users, this counter is measured only in the primary
Measurement point
The duration and number of bits of BE services sent at the RLC layer are accumulated on the
basis of different SPIs. At the end of the measurement period, the corresponding counters are
calculated by dividing the total number of bits by the total period of time. The measured data
excludes the RLC headers and retransmitted data.
Formula
VS.HSDPA.BeChThroughput.SPI2 = {8}*
[VS.HSDPA.BeChThroughput.TotalBytes.SPI2]/
[VS.HSDPA.BeChThroughput.Times.SPI2]
Issue 03 (2015-06-30)

3338
BSC6900 UMTS
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ut.SPI2
WRFD-01061008

ut.SPI3
WRFD-01061008

ut.SPI4
WRFD-01061008

ut.SPI5
WRFD-01061008

ut.SPI6
WRFD-01061008

ut.SPI7
WRFD-01061008

ut.SPI8
WRFD-01061008

ut.SPI9
WRFD-01061008


3339
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
ut.SPI10
WRFD-01061008

ut.SPI11
WRFD-01061008

Mean Downlink Throughput of HSUPA Mac-d flow of BE Services with SPI

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73439864
ut.SPI2

HSUPA MAC-d flow of BE
Services with SPI Set to 2 for
Cell
73439865
ut.SPI3

Cell
73439866
ut.SPI4

Cell
73439867
ut.SPI5

Cell
73439868
ut.SPI6

Cell
73439869
ut.SPI7

Cell
73439870
ut.SPI8

Cell

3340
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73439871
ut.SPI9

Cell
73439872
ut.SPI10

Services with SPI Set to 10
for Cell
73444439
ut.SPI11

Services with SPI Set to 11
for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73421664
ut.Times.SPI10
ut.Times.SPI10
73428700
ut.Times.SPI11
ut.Times.SPI11
73421656
ut.Times.SPI2
ut.Times.SPI2
73421657
ut.Times.SPI3
ut.Times.SPI3
73421658
ut.Times.SPI4
ut.Times.SPI4
73421659
ut.Times.SPI5
ut.Times.SPI5
73421660
ut.Times.SPI6
ut.Times.SPI6
73421661
ut.Times.SPI7
ut.Times.SPI7
73421662
ut.Times.SPI8
ut.Times.SPI8
73421663
ut.Times.SPI9
ut.Times.SPI9

3341
BSC6900 UMTS
Description
These counters provide the uplink average throughput of HSUPA MAC-d flows carrying BE
services with different SPIs. For DC-HSUPA users, these counters are measured only in the
primary cell based on the total throughput on the primary and secondary carriers.
Measurement point
The duration and number of bits of BE services received at the Radio Link Control (RLC) layer
are accumulated for different SPIs. At the end of the measurement period, these counters are
calculated by dividing the corresponding total number of bits by the total period of time. The
RLC headers and retransmitted data are excluded.
Formula
VS.HSUPA.BeChThroughput.SPI2 = {8}*
[VS.HSUPA.BeChThroughput.TotalBytes.SPI2]/
[VS.HSUPA.BeChThroughput.Times.SPI2]
Issue 03 (2015-06-30)

3342
BSC6900 UMTS
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
ut.SPI2
WRFD-01061206

ut.SPI3
WRFD-01061206

ut.SPI4
WRFD-01061206

ut.SPI5
WRFD-01061206

ut.SPI6
WRFD-01061206

ut.SPI7
WRFD-01061206

ut.SPI8
WRFD-01061206

ut.SPI9
WRFD-01061206

ut.SPI10
WRFD-01061206

ut.SPI11
WRFD-01061206

1.12.50 Traffic Volume and Data Rate Measurement <per Cell>

(THRUPUT.Cell)
Overview
The RNC traffic measurement is used to measure the traffic of the CS domain and PS domain
in the RNC. Here, the traffic of the CS domain is indicated by equivalent Erlang while the traffic
of the PS domain by kbit per second.
Issue 03 (2015-06-30)

3343
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202812
VS.CS.Conv.Kbps.
DL64
Average DL Rate of
64 Kbit/s CS
Conversational
Services for Cell
Earlier than
BSC6900
V900R011
67183986
VS.CS.Conv.DL.
64.Traffic
DL Traffic Volume
of 64 Kbit/s CS
Conversational
Services for Cel
Earlier than
BSC6900
V900R011
67202816
VS.CS.Str.Kbps.D
L57.6
Average DL Rate of
57.6 Kbit/s CS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67183990
VS.CS.Str.DL.
57.6.Traffic
DL Traffic Volume
of 57.6 Kbit/s CS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67202819
VS.PS.Bkg.Kbps.D
L8
Average DL Rate of
8 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67183993
VS.PS.Bkg.DL.
8.Traffic
DL Traffic Volume
of 8 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202820
VS.PS.Bkg.Kbps.D
L16
Average DL Rate of
16 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67183994
VS.PS.Bkg.DL.
16.Traffic
DL Traffic Volume
of 16 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202821
VS.PS.Bkg.Kbps.D
L32
Average DL Rate of
32 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67183995
VS.PS.Bkg.DL.
32.Traffic
DL Traffic Volume
of 32 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011

3344
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202822
VS.PS.Bkg.Kbps.D
L64
Average DL Rate of
64 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67183996
VS.PS.Bkg.DL.
64.Traffic
DL Traffic Volume
of 64 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202823
VS.PS.Bkg.Kbps.D
L128
Average DL Rate of
128 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67183997
VS.PS.Bkg.DL.
128.Traffic
DL Traffic Volume
of 128 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202824
VS.PS.Bkg.Kbps.D
L144
Average DL Rate of
144 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67183998
VS.PS.Bkg.DL.
144.Traffic
DL Traffic Volume
of 144 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202825
VS.PS.Bkg.Kbps.D
L256
Average DL Rate of
256 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67183999
VS.PS.Bkg.DL.
256.Traffic
DL Traffic Volume
of 256 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202826
VS.PS.Bkg.Kbps.D
L384
Average DL Rate of
384 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184000
VS.PS.Bkg.DL.
384.Traffic
DL Traffic Volume
of 384 Kbit/s PS
Background
Services for Cell
Earlier than
BSC6900
V900R011

3345
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202827
VS.PS.Int.Kbps.DL
8
Average DL Rate of
8 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67184001
VS.PS.Int.DL.
8.Traffic
DL Traffic Volume
of 8 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67202828
VS.PS.Int.Kbps.DL
16
Average DL Rate of
16 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67184002
VS.PS.Int.DL.
16.Traffic
DL Traffic Volume
of 16 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67202829
VS.PS.Int.Kbps.DL
32
Average DL Rate of
32 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67184003
VS.PS.Int.DL.
32.Traffic
DL Traffic Volume
of 32 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67202830
VS.PS.Int.Kbps.DL
64
Average DL Rate of
64 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67184004
VS.PS.Int.DL.
64.Traffic
DL Traffic Volume
of 64 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67202831
VS.PS.Int.Kbps.DL
128
Average DL Rate of
128 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67184005
VS.PS.Int.DL.
128.Traffic
DL Traffic Volume
of 128 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011

3346
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202832
VS.PS.Int.Kbps.DL
144
Average DL Rate of
144 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67184006
VS.PS.Int.DL.
144.Traffic
DL Traffic Volume
of 144 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67202833
VS.PS.Int.Kbps.DL
256
Average DL Rate of
256 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67184007
VS.PS.Int.DL.
256.Traffic
DL Traffic Volume
of 256 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67202834
VS.PS.Int.Kbps.DL
384
Average DL Rate of
384 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67184008
VS.PS.Int.DL.
384.Traffic
DL Traffic Volume
of 384 Kbit/s PS
for Cell
Earlier than
BSC6900
V900R011
67202835
VS.PS.Str.Kbps.D
L32
Average DL Rate of
32 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67184009
VS.PS.Str.DL.
32.Traffic
DL Traffic Volume
of 32 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67202836
VS.PS.Str.Kbps.D
L64
Average DL Rate of
64 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67184010
VS.PS.Str.DL.
64.Traffic
DL Traffic Volume
of 64 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011

3347
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202837
VS.PS.Str.Kbps.D
L128
Average DL Rate of
128 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67184011
VS.PS.Str.DL.
128.Traffic
DL Traffic Volume
of 128 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67202838
VS.PS.Str.Kbps.D
L144
Average DL Rate of
144 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67184012
VS.PS.Str.DL.
144.Traffic
DL Traffic Volume
of 144 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67202840
VS.PS.Bkg.Kbps.U
L8
Average UL Rate of
8 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184014
VS.PS.Bkg.UL.
8.Traffic
UL Traffic Volume
of 8 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202841
VS.PS.Bkg.Kbps.U
L16
Average UL Rate of
16 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184015
VS.PS.Bkg.UL.
16.Traffic
UL Traffic Volume
of 16 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202842
VS.PS.Bkg.Kbps.U
L32
Average UL Rate of
32 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184016
VS.PS.Bkg.UL.
32.Traffic
UL Traffic Volume
of 32 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011

3348
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202843
VS.PS.Bkg.Kbps.U
L64
Average UL Rate of
64 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184017
VS.PS.Bkg.UL.
64.Traffic
UL Traffic Volume
of 64 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202844
VS.PS.Bkg.Kbps.U
L128
Average UL Rate of
128 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184018
VS.PS.Bkg.UL.
128.Traffic
UL Traffic Volume
of 128 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202845
VS.PS.Bkg.Kbps.U
L144
Average UL Rate of
144 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184019
VS.PS.Bkg.UL.
144.Traffic
UL Traffic Volume
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202846
VS.PS.Bkg.Kbps.U
L256
Average UL Rate of
256 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184020
VS.PS.Bkg.UL.
256.Traffic
UL Traffic Volume
Background
Services for Cell
Earlier than
BSC6900
V900R011
67202847
VS.PS.Bkg.Kbps.U
L384
Average UL Rate of
384 Kbit/s PS R99
Background
Services for Cell
Earlier than
BSC6900
V900R011
67184021
VS.PS.Bkg.UL.
384.Traffic
UL Traffic Volume
Background
Services for Cell
Earlier than
BSC6900
V900R011

3349
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202848
VS.PS.Int.Kbps.UL
8
Average UL Rate of
8 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67184022
VS.PS.Int.UL.
8.Traffic
UL Traffic Volume
of 8 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67202849
VS.PS.Int.Kbps.UL
16
Average UL Rate of
16 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67184023
VS.PS.Int.UL.
16.Traffic
UL Traffic Volume
of 16 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67202850
VS.PS.Int.Kbps.UL
32
Average UL Rate of
32 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67184024
VS.PS.Int.UL.
32.Traffic
UL Traffic Volume
of 32 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67202851
VS.PS.Int.Kbps.UL
64
Average UL Rate of
64 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67184025
VS.PS.Int.UL.
64.Traffic
UL Traffic Volume
of 64 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67202852
VS.PS.Int.Kbps.UL
128
Average UL Rate of
128 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67184026
VS.PS.Int.UL.
128.Traffic
UL Traffic Volume
for Cell
Earlier than
BSC6900
V900R011

3350
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202853
VS.PS.Int.Kbps.UL
144
Average UL Rate of
144 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67184027
VS.PS.Int.UL.
144.Traffic
UL Traffic Volume
for Cell
Earlier than
BSC6900
V900R011
67202854
VS.PS.Int.Kbps.UL
256
Average UL Rate of
256 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67184028
VS.PS.Int.UL.
256.Traffic
UL Traffic Volume
for Cell
Earlier than
BSC6900
V900R011
67202855
VS.PS.Int.Kbps.UL
384
Average UL Rate of
384 Kbit/s PS R99
for Cell
Earlier than
BSC6900
V900R011
67184029
VS.PS.Int.UL.
384.Traffic
UL Traffic Volume
for Cell
Earlier than
BSC6900
V900R011
67202856
VS.PS.Str.Kbps.U
L16
Average UL Rate of
16 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67184030
VS.PS.Str.UL.
16.Traffic
UL Traffic Volume
of 16 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67202857
VS.PS.Str.Kbps.U
L32
Average UL Rate of
32 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67184031
VS.PS.Str.UL.
32.Traffic
UL Traffic Volume
of 32 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011

3351
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67202858
VS.PS.Str.Kbps.U
L64
Average UL Rate of
64 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67184032
VS.PS.Str.UL.
64.Traffic
UL Traffic Volume
of 64 Kbit/s PS
Streaming Services
for Cell
Earlier than
BSC6900
V900R011
67202859
VS.DcchSrbKbps.
Ul
Average UL Rate of
Signaling on DCCH
for Cell
Earlier than
BSC6900
V900R011
67189903
VS.DcchSRB.Ul.Tr
affic
UL Traffic Volume
of Signaling on
DCCH for Cell
Earlier than
BSC6900
V900R011
67202860
VS.DcchSrbKbps.
Dl
Average DL Rate of
Signaling on DCCH
for Cell
Earlier than
BSC6900
V900R011
67189905
VS.DcchSRB.Dl.Tr
affic
DL Traffic Volume
of Signaling on
DCCH for Cell
Earlier than
BSC6900
V900R011
67203449
VS.AMR.UL.Traffi
c.BestCell
UL Traffic Volume
of AMR Services for
Best Cell
Earlier than
BSC6900
V900R011
67203450
VS.AMR.DL.Traffi
c.BestCell
DL Traffic Volume
of AMR Services for
Best Cell
Earlier than
BSC6900
V900R011
67203451
VS.VP.UL.Traffic.
BestCell
UL Traffic Volume
of VP Services for
Best Cell
Earlier than
BSC6900
V900R011
67203452
VS.VP.DL.Traffic.
BestCell
DL Traffic Volume
of VP Services for
Best Cell
Earlier than
BSC6900
V900R011
67203453
VS.PS.BE.kbits.UL
.0.32.BestCell
UL Traffic Volume
of PS BE Services (0
Kbit/s < UL Bit Rate
<= 32 Kbit/s) for
Best Cell
Earlier than
BSC6900
V900R011

3352
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203454
VS.PS.BE.kbits.DL
.0.32.BestCell
DL Traffic Volume
of PS BE Services (0
Kbit/s < DL Bit Rate
<= 32 Kbit/s) for
Best Cell
Earlier than
BSC6900
V900R011
67203455
VS.PS.BE.kbits.UL
.32.64.BestCell
UL Traffic Volume
of PS BE Services
(32 Kbit/s < DL Bit
Rate <= 64 Kbit/s)
for Best Cell
Earlier than
BSC6900
V900R011
67203456
VS.PS.BE.kbits.DL
.32.64.BestCell
DL Traffic Volume
of PS BE Services
(32 Kbit/s < DL Bit
Rate <= 64 Kbit/s)
for Best Cell
Earlier than
BSC6900
V900R011
67203457
VS.PS.BE.kbits.UL
.64.144.BestCell
UL Traffic Volume
of PS BE Services
(64 Kbit/s < DL Bit
Rate <= 144 Kbit/s)
for Best Cell
Earlier than
BSC6900
V900R011
67203458
VS.PS.BE.kbits.DL
.64.144.BestCell
DL Traffic Volume
of PS BE Services
(64 Kbit/s < DL Bit
Rate <= 144 Kbit/s)
for Best Cell
Earlier than
BSC6900
V900R011
67203459
VS.PS.BE.kbits.UL
.144.384.BestCell
UL Traffic Volume
of PS BE Services
(144 Kbit/s < DL Bit
Rate <= 384 Kbit/s)
for Best Cell
Earlier than
BSC6900
V900R011
67203460
VS.PS.BE.kbits.DL
.144.384.BestCell
DL Traffic Volume
of PS BE Services
(144 Kbit/s < DL Bit
Rate <= 384 Kbit/s)
for Best Cell
Earlier than
BSC6900
V900R011
67192689
VS.AMR.Erlang.B
estCell
Equivalent Erlang
for AMR Services
for Best Cell
Earlier than
BSC6900
V900R011
67192690
VS.VP.Erlang.Best
Cell
Num Of Erlang of
VP service in the best
cell
Earlier than
BSC6900
V900R011

3353
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204482
VS.MBMS.PTM.M
eanThroughput
Average Throughput
of PTM MBMS
Services for Cell
Earlier than
BSC6900
V900R011
67204483
VS.MBMS.PTP.Me
anThroughput
Average Throughput
of PTP MBMS
Services for Cell
Earlier than
BSC6900
V900R011
67204248
VS.PS.Str.Kbps.D
L8
Average DL Rate of
8 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67193548
VS.PS.Str.DL.
8.Traffic
DL Traffic Volume
of 8 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67204249
VS.PS.Str.Kbps.D
L16
Average DL Rate of
16 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67193550
VS.PS.Str.DL.
16.Traffic
DL Traffic Volume
of 16 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67204250
VS.PS.Str.Kbps.D
L256
Average DL Rate of
256 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67193552
VS.PS.Str.DL.
256.Traffic
DL Traffic Volume
of 256 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67204251
VS.PS.Str.Kbps.D
L384
Average DL Rate of
384 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67193554
VS.PS.Str.DL.
384.Traffic
DL Traffic Volume
of 384 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012

3354
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204252
VS.PS.Str.Kbps.U
L8
Average UL Rate of
8 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67193556
VS.PS.Str.UL.
8.Traffic
UL Traffic Volume
of 8 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67204253
VS.PS.Str.Kbps.U
L128
Average UL Rate of
128 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
67193558
VS.PS.Str.UL.
128.Traffic
UL Traffic Volume
of 128 Kbit/s PS
Streaming Services
for Cell
BSC6900
V900R012
73410482
VS.PS.Conv.Kbps.
DL
Average downlink
throughput of the
Traffic PS
Conversational
beared on DCH for
cell
BSC6900
V900R012
73393908
VS.PS.Conv.DL.Tr
affic
Number of downlink
Bit Size of Transport
Conversational
beared on DCH for
cell
BSC6900
V900R012
73410483
VS.PS.Conv.Kbps.
UL
Average uplink
throughput of the
Traffic PS
Conversational
beared on DCH for
cell
BSC6900
V900R012
73393910
VS.PS.Conv.UL.Tr
affic
Number of uplink Bit

Size of Transport
Conversational
beared on DCH for
cell
BSC6900
V900R012

3355
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426120
VS.PS.BE.DCH.DL
.SumThroughput
Sum of Sampled
Downlink BE
Throughput of UEs
with PS Services
over DCHs
BSC6900
V900R015C00
73426121
VS.PS.BE.DCH.DL
.SamplesThroughput
Number of Times
Downlink BE
Throughput of UEs
with PS Services
over DCHs Is
Sampled
BSC6900
V900R015C00
73426122
VS.PS.BE.DCH.UL
.SumThroughput
Sum of Sampled
Uplink BE
Throughput of UEs
with PS Services
over DCHs
BSC6900
V900R015C00
73426123
VS.PS.BE.DCH.UL
.SamplesThroughput
Number of Times
Uplink BE
Throughput of UEs
with PS Services
over DCHs Is
Sampled
BSC6900
V900R015C00
73426291
VS.RAB.AMR.Erla
ng.cell
Number of Erlangs
for AMR Services
for Cell
BSC6900
V900R015C00
73444479
VS.RAB.AMRWB.
Erlang.cell
Number of Erlangs
for AMRWB
Services for Cell
BSC6900
V900R016C00
73444482
VS.AMR.Erlang.M
O
Erlang of MobileOriginated AMR

Service for Cell
BSC6900
V900R016C00
73444483
VS.AMR.Erlang.M
T
Erlang of MobileTerminated AMR

Service for Cell
BSC6900
V900R016C00
73444484
VS.AMR.Erlang.N
otDistinguish
Erlang of AMR
Services
(Unidentifiable
Mobile-Originated
or MobileTerminated) for Cell
BSC6900
V900R016C00

3356
BSC6900 UMTS
None
Average DL Rate of 64 Kbit/s CS Conversational Services

Counters
Counter ID
Counter Name
Counter Description
67202812
VS.CS.Conv.Kbps.DL64
Average DL Rate of 64 Kbit/

s CS Conversational Services
for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
67184036
VS.CS.Conv.DL.64.Times
Duration of Measuring
Throughput of CS Downlink
64 kbit/s Conversational
Service for Cell
Description
This counter provides the average downlink rate of 64 Kbit/s CS conversational services in the
cells in the active set. The measured data excludes the RLC headers and retransmitted data.
Measurement point
The DL traffic (unit: bit) and the service duration (unit: ms) of the 64 Kbit/s CS conversational
services in the cells in the active set are accumulated in the measurement period. At the end of
a measurement period, this counter is calculated using the following formula:
Formula
VS.CS.Conv.Kbps.DL64 = [VS.CS.Conv.DL.64.Traffic]/[VS.CS.Conv.DL.64.Times]
Unit
kbit/s
Issue 03 (2015-06-30)

3357
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CS.Conv.Kbps.DL64
WRFD-010501
DL Traffic Volume of 64 Kbit/s CS Conversational Services

Counters
Counter ID
Counter Name
Counter Description
67183986
VS.CS.Conv.DL.64.Traffic
DL Traffic Volume of 64
Kbit/s CS Conversational
Services for Cel
Description
This counter provides the downlink traffic volume of 64 Kbit/s CS conversational services in
the cells in the active set. The measured data excludes the RLC headers and retransmitted data.
Measurement point
The DL traffic volume of 64 Kbit/s CS conversational services over the RLC layer is accumulated
for the cells that are under the SRNC and are in the active set
Formula
None
Unit
bit
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.CS.Conv.DL.64.Traffic
WRFD-010501

3358
BSC6900 UMTS
Average DL Rate of 57.6 Kbit/s CS Streaming Services

Counters
Counter ID
Counter Name
Counter Description
67202816
VS.CS.Str.Kbps.DL57.6
Average DL Rate of 57.6

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

3359
BSC6900 UMTS
DL Traffic Volume of 57.6 Kbit/s CS Streaming Services

Counters
Counter ID
Counter Name
Counter Description
67183990
VS.CS.Str.DL.57.6.Traffic
DL Traffic Volume of 57.6

Kbit/s CS Streaming
Services for Cell
Description
This counter provides the downlink traffic volume of 57.6 Kbit/s CS streaming services in the
Measurement point
The DL traffic volume of 57.6 Kbit/s CS streaming services over the RLC layer is accumulated
for the cells that are under the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name
Feature ID
Feature Name
VS.CS.Str.DL.57.6.Traffic
WRFD-010502
Streaming QoS Class
Counters Related to the Average DL Rates of Different PS R99 Background Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202819
VS.PS.Bkg.Kbps.DL8
Average DL Rate of 8 Kbit/s

PS Background Services for
Cell
67202820
VS.PS.Bkg.Kbps.DL16

s PS Background Services for
Cell

3360
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67202821
VS.PS.Bkg.Kbps.DL32

Cell
67202822
VS.PS.Bkg.Kbps.DL64

Cell
67202823
VS.PS.Bkg.Kbps.DL128
Average DL Rate of 128

Kbit/s PS Background
Services for Cell
67202824

Services for Cell
67202825

Services for Cell
67202826

Services for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67184047
VS.PS.Bkg.DL.128.Times
128 kbit/s Background
Service for Cell
67184048
Service for Cell
67184044
16 kbit/s Background Service
for Cell
67184049
Service for Cell

3361
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67184045
for Cell
67184050
Service for Cell
67184046
for Cell
67184043
for Cell
Description
These counters provide the average downlink rates of different PS R99 background services in
the cells in the active set.
Measurement point
The DL traffic (not including the RLC header and the retransmitted data, unit: bit) and the actual
duration (unit: ms) with data transmission of each kind of PS R99 background services are
accumulated in the measurement period for the cells that are under the SRNC and are in the
active set. At the end of a measurement period, this counter is calculated using the following
formula:
Formula
VS.PS.Bkg.Kbps.DL8 = [VS.PS.Bkg.DL.8.Traffic]/[VS.PS.Bkg.DL.8.Times]
Issue 03 (2015-06-30)

3362
BSC6900 UMTS
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Bkg.Kbps.DL8
WRFD-010504
VS.PS.Bkg.Kbps.DL16
WRFD-010504
VS.PS.Bkg.Kbps.DL32
WRFD-010504
VS.PS.Bkg.Kbps.DL64
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
Counters Related to the DL Traffic Volumes of Different PS R99 Background

Services
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67183993
VS.PS.Bkg.DL.8.Traffic
DL Traffic Volume of 8 Kbit/

Cell
67183994
Services for Cell
67183995
Services for Cell
67183996
Services for Cell
67183997

Services for Cell

3363
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67183998

Services for Cell
67183999

Services for Cell
67184000

Services for Cell
Description
These counters provide the downlink traffic volumes of different PS R99 background services
in the cells in the active set.
Measurement point
The DL traffic volumes (not including the RLC header and the retransmitted data) of each kind
of PS R99 background services over the RLC layer are accumulated for the cells that are under
the SRNC and are in the active set.
Formula
None
Unit
bit
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504

3364
BSC6900 UMTS
Counters Related to the Average DL Rates of Different PS R99 Interactive Services

Counters
Counter ID
Counter Name
Counter Description
67202827
VS.PS.Int.Kbps.DL8

PS Interactive Services for
Cell
67202828
VS.PS.Int.Kbps.DL16

s PS Interactive Services for
Cell
67202829
VS.PS.Int.Kbps.DL32

Cell
67202830
VS.PS.Int.Kbps.DL64

Cell
67202831
VS.PS.Int.Kbps.DL128

Kbit/s PS Interactive
Services for Cell
67202832

Services for Cell
67202833

Services for Cell
67202834

Services for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67184055
VS.PS.Int.DL.128.Times
128 kbit/s Interactive Service
for Cell

3365
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67184056
for Cell
67184052
Duration of Measuring PS
Downlink 16 kbit/s
Interactive Service for Cell
67184057
for Cell
67184053
for Cell
67184058
for Cell
67184054
for Cell
67184051
for Cell
Description
These counters provide the average downlink rates of different PS R99 interactive services in
Measurement point
duration (unit: ms) with data transmission of each kind of PS R99 interactive services are
formula:
Formula
VS.PS.Int.Kbps.DL8 = [VS.PS.Int.DL.8.Traffic]/[VS.PS.Int.DL.8.Times]
Issue 03 (2015-06-30)

3366
BSC6900 UMTS
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Int.Kbps.DL8
WRFD-010503
VS.PS.Int.Kbps.DL16
WRFD-010503
VS.PS.Int.Kbps.DL32
WRFD-010503
VS.PS.Int.Kbps.DL64
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
Counters Related to the DL Traffic Volumes of Different PS R99 Interactive

Services
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67184001
VS.PS.Int.DL.8.Traffic

Cell
67184002
Services for Cell

3367
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67184003
Services for Cell
67184004
Services for Cell
67184005

Services for Cell
67184006

Services for Cell
67184007

Services for Cell
67184008

Services for Cell
Description
These counters provide the downlink traffic volumes of different PS R99 interactive services in
the cells in the active set. The measured data excludes the RLC headers and retransmitted data.
Measurement point
of PS R99 interactive services over the RLC layer are accumulated for the cells that are under
Formula
None
Unit
bit
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010503

3368
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
Counters Related to the Average DL Rates of Different PS R99 Streaming Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202835
VS.PS.Str.Kbps.DL32

s PS Streaming Services for
Cell
67202836
VS.PS.Str.Kbps.DL64

Cell
67202837
VS.PS.Str.Kbps.DL128

Kbit/s PS Streaming Services
for Cell
67202838

for Cell
67204248
VS.PS.Str.Kbps.DL8

Cell
67204249
VS.PS.Str.Kbps.DL16

Cell
67204250

for Cell
67204251

for Cell

3369
BSC6900 UMTS
specific formulas.
Counter ID
Counter Name
Counter Description
67184061
VS.PS.Str.DL.128.Times
128 kbit/s Streaming Service
for Cell
67184062
for Cell
67193551
Duration of Stat Throughput

of Traffic PS_STR_DL_16
for cell
67193553

for cell
67184059
for Cell
67193555

for cell
67184060
64 kbit/s Streaming for Cell
67193549

of Traffic PS_STR_DL_8 for
cell
Description
These counters provide the average downlink rates of different PS R99 streaming services in
Measurement point
duration (unit: ms) with data transmission of each kind of PS R99 streaming services are
formula:
Issue 03 (2015-06-30)

3370
BSC6900 UMTS
Formula
VS.PS.Str.Kbps.DL32 = [VS.PS.Str.DL.32.Traffic]/[VS.PS.Str.DL.32.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Str.Kbps.DL32
WRFD-010502
Streaming QoS Class
VS.PS.Str.Kbps.DL64
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
VS.PS.Str.Kbps.DL8
WRFD-010502
Streaming QoS Class
VS.PS.Str.Kbps.DL16
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
Counters Related to the DL Traffic Volumes of Different PS R99 Streaming

Services
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67184009
VS.PS.Str.DL.32.Traffic
for Cell

3371
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67184010
for Cell
67184011

for Cell
67184012

for Cell
67193548

Cell
67193550
for Cell
67193552

for Cell
67193554

for Cell
Description
These counters provide the downlink traffic volumes of different PS R99 streaming services in
Measurement point
of PS R99 streaming services over the RLC layer are accumulated for the cells that are under
Formula
None
Unit
bit
Issue 03 (2015-06-30)

3372
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
Counters Related to the Average UL Rates of Different PS R99 Background Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202840
VS.PS.Bkg.Kbps.UL8
Average UL Rate of 8 Kbit/s

for Cell
67202841
VS.PS.Bkg.Kbps.UL16
Average UL Rate of 16 Kbit/

s PS R99 Background
Services for Cell
67202842
VS.PS.Bkg.Kbps.UL32

s PS R99 Background
Services for Cell
67202843
VS.PS.Bkg.Kbps.UL64

s PS R99 Background
Services for Cell
67202844
VS.PS.Bkg.Kbps.UL128
Average UL Rate of 128

Kbit/s PS R99 Background
Services for Cell
67202845

Services for Cell
67202846

Services for Cell

3373
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67202847

Services for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67184068
VS.PS.Bkg.UL.128.Times
Throughput of PS Uplink 128
kbit/s Background Service
for Cell
67184069
for Cell
67184065
for Cell
67184070
for Cell
67184066
for Cell
67184071
for Cell
67184067
for Cell
67184064
for Cell

3374
BSC6900 UMTS
Description
These counters provide the average uplink rates of different PS R99 background services in the
Measurement point
The UL traffic (not including the RLC header and the retransmitted data, unit: bit) and the actual
duration (unit: ms) with data transmission of each kind of PS R99 background services are
formula:
Formula
VS.PS.Bkg.Kbps.UL8 = [VS.PS.Bkg.UL.8.Traffic]/[VS.PS.Bkg.UL.8.Times]
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS.Bkg.Kbps.UL8
WRFD-010504
VS.PS.Bkg.Kbps.UL16
WRFD-010504
VS.PS.Bkg.Kbps.UL32
WRFD-010504
VS.PS.Bkg.Kbps.UL64
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504

3375
BSC6900 UMTS
Counters Related to the UL Traffic Volumes of Different PS R99 Background

Services
Counters
Counter ID
Counter Name
Counter Description
67184014
VS.PS.Bkg.UL.8.Traffic
UL Traffic Volume of 8 Kbit/

s PS R99 Background
Services for Cell
67184015
UL Traffic Volume of 16
Services for Cell
67184016
Services for Cell
67184017
Services for Cell
67184018

Services for Cell
67184019

Services for Cell
67184020

Services for Cell
67184021

Services for Cell
Description
These counters provide the uplink traffic volumes of different PS R99 background services in
Measurement point
The UL traffic volumes (not including the RLC header and the retransmitted data) of each kind
of PS R99 background services over the RLC layer are accumulated for the cells that are under
Issue 03 (2015-06-30)

3376
BSC6900 UMTS
Formula
None
Unit
bit
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
WRFD-010504
Counters Related to the Average UL Rates of Different PS R99 Interactive Services

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67202848
VS.PS.Int.Kbps.UL8

for Cell
67202849
VS.PS.Int.Kbps.UL16

s PS R99 Interactive Services
for Cell
67202850
VS.PS.Int.Kbps.UL32

for Cell
67202851
VS.PS.Int.Kbps.UL64

for Cell
67202852
VS.PS.Int.Kbps.UL128

Kbit/s PS R99 Interactive
Services for Cell

3377
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67202853

Services for Cell
67202854

Services for Cell
67202855

Services for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67184076
VS.PS.Int.UL.128.Times
kbit/s Interactive Service for
Cell
67184077
Cell
67184073
Cell
67184078
Cell
67184074
Cell
67184079
Cell

3378
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67184075
Cell
67184072
Cell
Description
These counters provide the average uplink rates of different PS R99 interactive services in the
Measurement point
duration (unit: ms) with data transmission of each kind of PS R99 interactive services are
formula:
Formula
VS.PS.Int.Kbps.UL8 = [VS.PS.Int.UL.8.Traffic]/[VS.PS.Int.UL.8.Times]
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS.Int.Kbps.UL8
WRFD-010503

3379
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.PS.Int.Kbps.UL16
WRFD-010503
VS.PS.Int.Kbps.UL32
WRFD-010503
VS.PS.Int.Kbps.UL64
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
Counters Related to the UL Traffic Volumes of Different PS R99 Interactive

Services
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67184022
VS.PS.Int.UL.8.Traffic

for Cell
67184023
Services for Cell
67184024
Services for Cell
67184025
Services for Cell
67184026

Services for Cell
67184027

Services for Cell
67184028

Services for Cell

3380
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67184029

Services for Cell
Description
These counters provide the uplink traffic volumes of different PS R99 interactive services in the
Measurement point
of PS R99 interactive services over the RLC layer are accumulated for the cells that are under
Formula
None
Unit
bit
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503
WRFD-010503

3381
BSC6900 UMTS
Counters Related to the Average UL Rates of Different PS R99 Streaming Services

Counters
Counter ID
Counter Name
Counter Description
67202856
VS.PS.Str.Kbps.UL16

Cell
67202857
VS.PS.Str.Kbps.UL32

Cell
67202858
VS.PS.Str.Kbps.UL64

Cell
67204252
VS.PS.Str.Kbps.UL8

Cell
67204253
VS.PS.Str.Kbps.UL128

for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193559
VS.PS.Str.UL.128.Times

of Traffic PS_STR_UL_128
for cell
67184080
kbit/s Streaming Service for
Cell
67184081
Cell
67184082
Cell

3382
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67193557

of Traffic PS_STR_UL_8 for
cell
Description
These counters provide the average uplink rates of different PS R99 streaming services in the
Measurement point
duration (unit: ms) with data transmission of each kind of PS R99 streaming services are
formula:
Formula
VS.PS.Str.Kbps.UL16 = [VS.PS.Str.UL.16.Traffic]/[VS.PS.Str.UL.16.Times]
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS.Str.Kbps.UL16
WRFD-010502
Streaming QoS Class
VS.PS.Str.Kbps.UL32
WRFD-010502
Streaming QoS Class
VS.PS.Str.Kbps.UL64
WRFD-010502
Streaming QoS Class
VS.PS.Str.Kbps.UL8
WRFD-010502
Streaming QoS Class
VS.PS.Str.Kbps.UL128
WRFD-010502
Streaming QoS Class

3383
BSC6900 UMTS
Counters Related to the UL Traffic Volumes of Different PS R99 Streaming

Services
Counters
Counter ID
Counter Name
Counter Description
67184030
VS.PS.Str.UL.16.Traffic
for Cell
67184031
for Cell
67184032
for Cell
67193556

Cell
67193558

for Cell
Description
These counters provide the uplink traffic volumes of different PS R99 streaming services in the
Measurement point
of PS R99 streaming services over the RLC layer are accumulated for the cells that are under
Formula
None
Unit
bit
Issue 03 (2015-06-30)

3384
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
WRFD-010502
Streaming QoS Class
Average UL Rate of Signaling on DCCH

Counters
Counter ID
Counter Name
Counter Description
67202859
VS.DcchSrbKbps.Ul
Average UL Rate of
Signaling on DCCH for Cell
specific formulas.
Counter ID
Counter Name
Counter Description
67189904
VS.DcchSrbKbps.Ul.Times
Duration of Measuring UL
Description
This counter provides the average uplink rate of signaling on the DCCH in the cells in the active
set.
Measurement point
The UL traffic (not including the RLC header and the retransmitted data, unit: bit) and the
transmit duration (unit: ms) of the signaling over the DCCH are accumulated in the measurement
period for the cells that are under the SRNC and are in the active set. At the end of the
measurement period, the value of this counter is calculated.
Formula
VS.DcchSrbKbps.Ul = [VS.DcchSRB.Ul.Traffic]/[VS.DcchSrbKbps.Ul.Times]
Issue 03 (2015-06-30)

3385
BSC6900 UMTS
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.DcchSrbKbps.Ul
WRFD-020900
Logical Channel
Management
UL Traffic Volume of Signaling on DCCH

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

3386
BSC6900 UMTS
Average DL Rate of Signaling on DCCH

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

3387
BSC6900 UMTS
DL Traffic Volume of Signaling on DCCH

Counters
Counter ID
Counter Name
Counter Description
67189905
VS.DcchSRB.Dl.Traffic
DL Traffic Volume of
Description
This counter provides the downlink traffic volume of signaling on the DCCH in the cells in the
active set.
Measurement point
The DL traffic volume (not including the RLC header and the retransmitted data) of signaling
on the DCCH is accumulated in the measurement period for the cells that are under the SRNC
and are in the active set.
Formula
None
Unit
bit
Related Features
Counter Name
Feature ID
Feature Name
VS.DcchSRB.Dl.Traffic
WRFD-020900
Logical Channel
Management
UL Traffic Volume of AMR Services for Best Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67203449
VS.AMR.UL.Traffic.BestCell
UL Traffic Volume of AMR

Services for Best Cell

3388
BSC6900 UMTS
Description
This counter provides the uplink traffic volume of AMR services(narrowband AMR services)
in the best cell. The measured data excludes the RLC headers and retransmitted data.
Measurement point
The UL traffic volume of AMR services is accumulated in the measurement period for the best
cell under the SRNC.
Formula
None
Unit
kbit
Related Features
Counter Name
Feature ID
Feature Name
VS.AMR.UL.Traffic.BestCell
WRFD-010501
DL Traffic Volume of AMR Services for Best Cell

Counters
Counter ID
Counter Name
Counter Description
67203450
VS.AMR.DL.Traffic.BestCell
DL Traffic Volume of AMR

Description
This counter provides the downlink traffic volume of AMR services(narrowband AMR services)
in the best cell. The measured data excludes the RLC headers and retransmitted data.
Measurement point
The DL traffic volume of AMR services is accumulated in the measurement period for the best
Formula
None
Issue 03 (2015-06-30)

3389
BSC6900 UMTS
Unit
kbit
Related Features
Counter Name
Feature ID
Feature Name
VS.AMR.DL.Traffic.BestCell
WRFD-010501
UL Traffic Volume of VP Services for Best Cell

Counters
Counter ID
Counter Name
Counter Description
67203451
VS.VP.UL.Traffic.BestCell
UL Traffic Volume of VP
Description
This counter provides the uplink traffic volume of VP services in the best cell. The measured
data excludes the RLC headers and retransmitted data.
Measurement point
The UL traffic volume of VP services is accumulated in the measurement period for the best
Formula
None
Unit
kbit
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VP.UL.Traffic.BestCell
WRFD-010501

3390
BSC6900 UMTS
DL Traffic Volume of VP Services for Best Cell

Counters
Counter ID
Counter Name
Counter Description
67203452
VS.VP.DL.Traffic.BestCell
DL Traffic Volume of VP
Description
This counter provides the downlink traffic volume of VP services in the best cell. The measured
data excludes the RLC headers and retransmitted data.
Measurement point
The DL traffic volume of VP services is accumulated in the measurement period for the best
Formula
None
Unit
kbit
Related Features
Counter Name
Feature ID
Feature Name
VS.VP.DL.Traffic.BestCell
WRFD-010501
UL Traffic of BE Services with Different PS Data Rates for Best Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67203453
VS.PS.BE.kbits.UL.
0.32.BestCell
UL Traffic Volume of PS BE
Services (0 Kbit/s < UL Bit
Rate <= 32 Kbit/s) for Best
Cell

3391
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67203455
VS.PS.BE.kbits.UL.
32.64.BestCell
Services (32 Kbit/s < DL Bit
Cell
67203457
VS.PS.BE.kbits.UL.
64.144.BestCell
Cell
67203459
VS.PS.BE.kbits.UL.
144.384.BestCell
Cell
Description
These counters provides the uplink traffic of BE services with different PS data rates in the best
cell. The measured data excludes the RLC headers and retransmitted data.
Measurement point
The uplink traffic of BE services with different PS data rates over the DCH and RACH is
accumulated in the measurement period for the best cell under the SRNC.
Formula
None
Unit
kbit
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS.BE.kbits.UL.
0.32.BestCell
WRFD-010503
WRFD-010504
VS.PS.BE.kbits.UL.
32.64.BestCell
WRFD-010503
WRFD-010504
VS.PS.BE.kbits.UL.
64.144.BestCell
WRFD-010503
WRFD-010504

3392
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.PS.BE.kbits.UL.
144.384.BestCell
WRFD-010503
WRFD-010504
DL Traffic of BE Services with Different PS Data Rates for Best Cell

Counters
Counter ID
Counter Name
Counter Description
67203454
VS.PS.BE.kbits.DL.
0.32.BestCell
DL Traffic Volume of PS BE
Cell
67203456
VS.PS.BE.kbits.DL.
32.64.BestCell
Cell
67203458
VS.PS.BE.kbits.DL.
64.144.BestCell
Cell
67203460
VS.PS.BE.kbits.DL.
144.384.BestCell
Cell
Description
These counters provides the downlink traffic of BE services with different PS data rates in the
best cell. The measured data excludes the RLC headers and retransmitted data.
Measurement point
The downlink traffic of BE services with different PS data rates over the DCH and FACH is
accumulated in the measurement period for the best cell under the SRNC.
Formula
None
Unit
kbit
Issue 03 (2015-06-30)

3393
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.BE.kbits.DL.
0.32.BestCell
WRFD-010503
WRFD-010504
VS.PS.BE.kbits.DL.
32.64.BestCell
WRFD-010503
WRFD-010504
VS.PS.BE.kbits.DL.
64.144.BestCell
WRFD-010503
WRFD-010504
VS.PS.BE.kbits.DL.
144.384.BestCell
WRFD-010503
WRFD-010504
Mean Number of AMR service UEs in the best cell

Counters
Counter ID
Counter Name
Counter Description
67192689
VS.AMR.Erlang.BestCell
Equivalent Erlang for AMR

Description
This measurement item provides the mean number of UEs that use the AMR speech service
(narrowband and wideband AMR services) in the best cell.
Measurement point
The RNC takes samples every 30 seconds in a measurement period. At the end of the
measurement period, the RNC obtains the value of this counter by dividing the sum of sampling
values by the number of sampling times.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3394
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AMR.Erlang.BestCell
WRFD-010501
Mean Number of VP service UEs in the best cell

Counters
Counter ID
Counter Name
Counter Description
67192690
VS.VP.Erlang.BestCell
Num Of Erlang of VP service

in the best cell
Description
This counter provides the mean number of UEs for all VP services in the best cell.
Measurement point
The RNC takes samples every 30 seconds in a measurement period. At the end of the
measurement period, the RNC obtains the value of this counter by dividing the sum of sampling
values by the number of sampling times.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VP.Erlang.BestCell
WRFD-010502
Streaming QoS Class

3395
BSC6900 UMTS
Average Throughput of PTM MBMS Services

Counters
Counter ID
Counter Name
Counter Description
67204482
VS.MBMS.PTM.MeanThroughput
Average Throughput of PTM

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

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204483
VS.MBMS.PTP.MeanThroughput
Average Throughput of PTP

MBMS Services for Cell

3396
BSC6900 UMTS
Description
This counter provides the average downlink throughput of MBMS services with the transmission
mode of PTP in the cell. The measured data excludes the RLC headers and retransmitted data.
Measurement point
The RNC takes samples on the downlink throughput of MBMS services with the transmission
mode of PTP periodically. At the end of the measurement period, the value of this counter is
calculated.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.MBMS.PTP.MeanThroughput
WRFD-01061608
16/32/64/128Kbps Channel
Rate on MBMS
Average DL Bit Rate of PS Conversational Service

Counters
Counter ID
Counter Name
Counter Description
73410482
VS.PS.Conv.Kbps.DL
Average downlink
throughput of the Traffic PS
DCH for cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393909
VS.PS.Conv.DL.Times
Conversational Service for
Cell

3397
BSC6900 UMTS
Description
This measurement item takes statistics of the average downlink throughput of the traffic PS
conversational beared on DCH in the active cell. The measured data excludes the RLC headers
and retransmitted data.
Measurement point
The RNC measures all DL traffic volume (unit: bit) and duration (unit: ms) of the PS
conversational service in the SRNC cell of the RLC layer. At the end of a measurement period,
this counter is calculated using the following formula:
Formula
VS.PS.Conv.Kbps.DL = [VS.PS.Conv.DL.Traffic]/[VS.PS.Conv.DL.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Conv.Kbps.DL
WRFD-010501
DL Throughput of PS Conversational Service

Counters
Counter ID
Counter Name
Counter Description
73393908
VS.PS.Conv.DL.Traffic
Number of downlink Bit Size

of Transport Blocks of
Traffic PS Conversational
beared on DCH for cell
Description
This measurement item takes statistics of the number of downlink Bit Size of Transport Blocks
of traffic PS conversational beared on DCH in the active cell. The measured data excludes the
RLC headers and retransmitted data.
Measurement point
The RNC measures the total DL volume of PS conversational service by the SRNC cell in the
RLC layer.
Issue 03 (2015-06-30)

3398
BSC6900 UMTS
Formula
None
Unit
bit
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Conv.DL.Traffic
WRFD-010501
Average UL Bit Rate of PS Conversational Service

Counters
Counter ID
Counter Name
Counter Description
73410483
VS.PS.Conv.Kbps.UL
Average uplink throughput

of the Traffic PS
DCH for cell
specific formulas.
Counter ID
Counter Name
Counter Description
73393911
VS.PS.Conv.UL.Times
Throughput of PS uplink
Conversational Service for
Cell
Description
This measurement item takes statistics of the average uplink throughput of the traffic PS
conversational beared on DCH in the active cell. The measured data excludes the RLC headers
and retransmitted data.
Measurement point
The RNC measures all UL traffic volume (unit: bit) and duration (unit: ms) of the PS
conversational service in the SRNC cell of the RLC layer. At the end of a measurement period,
this counter is calculated using the following formula:
Issue 03 (2015-06-30)

3399
BSC6900 UMTS
Formula
VS.PS.Conv.Kbps.UL = [VS.PS.Conv.UL.Traffic]/[VS.PS.Conv.UL.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Conv.Kbps.UL
WRFD-010501
UL Throughput of PS Conversational Service

Counters
Counter ID
Counter Name
Counter Description
73393910
VS.PS.Conv.UL.Traffic
Number of uplink Bit Size of

DCH for cell
Description
This measurement item takes statistics of the number of uplink Bit Size of Transport Blocks of
traffic PS conversational beared on DCH in the active cell. The measured data excludes the RLC
headers and retransmitted data.
Measurement point
The RNC measures the total UL volume of PS conversational service by the SRNC cell in the
RLC layer.
Formula
None
Unit
bit
Issue 03 (2015-06-30)

3400
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.PS.Conv.UL.Traffic
WRFD-010501
Sum of Sampled Downlink BE Throughput of UEs with PS Services over DCHs

Counters
Counter ID
Counter Name
Counter Description
73426120
VS.PS.BE.DCH.DL.SumThroughput
Sum of Sampled Downlink

BE Throughput of UEs with
PS Services over DCHs
Description
This counter provides the sum of sampled downlink BE throughput of UEs whose PS services
are carried over DCHs in the best cell. The unit of the counter is Kbit/s.
Measurement point
The system samples the downlink BE throughput of all the R99 UEs that are processing PS
services at an interval of 500 ms. This counter then sums the sample values within each
measurement period for the best cell. Note that the RLC headers and retransmitted data are
excluded. For PS combined services, only one RAB is taken into account.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS.BE.DCH.DL.SumThroughput
WRFD-010503
WRFD-010504

3401
BSC6900 UMTS
Number of Times Downlink BE Throughput of UEs with PS Services over DCHs

Is Sampled
Counters
Counter ID
Counter Name
Counter Description
73426121
VS.PS.BE.DCH.DL.SamplesThroughput
Number of Times Downlink

BE Throughput of UEs with
PS Services over DCHs Is
Sampled
Description
This counter provides the number of times downlink BE throughput of UEs whose PS services
are carried over DCHs is sampled in the best cell.
Measurement point
The system samples the downlink BE throughput of all the R99 UEs that are processing PS
services at an interval of 500 ms. This counter then calculates the number of times the downlink
BE throughput of such R99 PS UEs whose downlink BE throughput is not 0 is sampled within
each measurement period for the best cell.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS.BE.DCH.DL.SamplesThroughput
WRFD-010503
WRFD-010504

3402
BSC6900 UMTS
Sum of Sampled Uplink BE Throughput of UEs with PS Services over DCHs

Counters
Counter ID
Counter Name
Counter Description
73426122
VS.PS.BE.DCH.UL.SumThroughput
Sum of Sampled Uplink BE

Throughput of UEs with PS
Services over DCHs
Description
This counter provides the sum of sampled uplink BE throughput of UEs whose PS services are
carried over DCHs in the best cell. The unit of the counter is Kbit/s.
Measurement point
The system samples the uplink BE throughput of all the R99 UEs that are processing PS services
at an interval of 500 ms. This counter then sums the sample values within each measurement
period for the best cell. Note that the RLC headers and retransmitted data are excluded. For PS
combined services, only one RAB is taken into account.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS.BE.DCH.UL.SumThroughput
WRFD-010503
WRFD-010504

3403
BSC6900 UMTS
Number of Times Uplink BE Throughput of UEs with PS Services over DCHs Is

Sampled
Counters
Counter ID
Counter Name
Counter Description
73426123
VS.PS.BE.DCH.UL.SamplesThroughput
Number of Times Uplink BE

Throughput of UEs with PS
Services over DCHs Is
Sampled
Description
This counter provides the number of times uplink BE throughput of UEs whose PS services are
carried over DCHs is sampled in the best cell.
Measurement point
The system samples the uplink BE throughput of all the R99 UEs that are processing PS services
at an interval of 500 ms. This counter then calculates the number of times uplink BE throughput
of such R99 PS UEs whose uplink BE throughput is not 0 is sampled within each measurement
period for the best cell.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PS.BE.DCH.UL.SamplesThroughput
WRFD-010503
WRFD-010504

3404
BSC6900 UMTS
Number of Erlangs for AMR Services for Cell

Counters
Counter ID
Counter Name
Counter Description
73426291
VS.RAB.AMR.Erlang.cell
Number of Erlangs for AMR

Services for Cell
73444479
VS.RAB.AMRWB.Erlang.c
ell
Number of Erlangs for

AMRWB Services for Cell
Description
These counters provide the number of Erlangs for AMR services and AMRWB services based
on the holding time in a cell.
Counter Name
Description
The number of Erlangs for narrowband and

wideband AMR services based on the holding
time in a cell
VS.RAB.AMRWB.Erlang.cell
The number of Erlangs for wideband AMR

services based on the holding time in a cell
Measurement point
This counter is measured based on the actual holding time that is the time for releasing a RAB
minus the time for establishing the RAB in a cell where the RAB is released. Within a
measurement period, the value of AMR Erlang for CS services (traffic volume of CS services)
is calculated using the following formula: SUM(All AMR RAB Holding Time in minute)/60
min. The value of AMRWB Erlang for CS services is calculated using the following formula:
SUM(All AMRWB RAB Holding Time in minute)/60 min. If there are multiple cells in the
active set when the RAB is released, this counter is measured in the best cell. The rate of each
CS RAB is different, and therefore the value of CS Erlang must be calculated based on 12.2
kbit/s AMR services. To be specific, the traffic volume of CS services at the rate of less than or
equal to 32 kbit/s is the actual value, and the traffic volume of CS services at the rate of greater
than 32 kbit/s is doubled.
Formula
None
Unit
Erl
Issue 03 (2015-06-30)

3405
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
MRFD-210403
License Management
VS.RAB.AMRWB.Erlang.c
ell
WRFD-010613

Rate Wide Band)
Erlang of Mobile-Originated AMR Service for Cell

Counters
Counter ID
Counter Name
Counter Description
73444482
VS.AMR.Erlang.MO
Erlang of Mobile-Originated
AMR Service for Cell
Description
This counter measures the number of Erlangs of mobile-originated AMR services (including
wideband and narrowband AMR services) based on the call duration in the best cell.
Measurement point
Assume that at time T1 a UE sets up a mobile-originated AMR RAB or changes its best cell to
cell A and at time T2 the UE changes its best cell to another cell or releases the AMR RAB.
Then, the mobile-originated call duration in the best cell A can be calculated by the formula
DeltaT = T2 - T1. The RNC aggregates all DeltaTs for calling UEs in the best cell A to obtain
the total call duration (recorded as All DeltaT). The number of Erlangs of mobile-originated
AMR RABs in the best cell A can be calculated using the following formula: SUM(All DeltaT
in minute)/60 minutes. The service initiated by a UE is a mobile-originated AMR service if the
Init Direct Transfer or UL Direct Transfer message sent by the UE to the CS CN contains the
CM Service Request information element (IE) with the cause value of "mobile originate call
establishment or packet mode connection establishment" or "Emergency call establishment".
Formula
None
Unit
Erl
Issue 03 (2015-06-30)

3406
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AMR.Erlang.MO
MRFD-210403
License Management
Erlang of Mobile-Terminated AMR Service for Cell

Counters
Counter ID
Counter Name
Counter Description
73444483
VS.AMR.Erlang.MT
Erlang of MobileTerminated AMR Service for

Cell
Description
This counter measures the number of Erlangs of mobile-terminated AMR services (including
Measurement point
Assume that at time T1 a UE sets up a mobile-terminated AMR RAB or changes its best cell to
cell A and at time T2 the UE changes its best cell to another cell or releases the AMR RAB.
Then, the mobile-terminated call duration in the best cell A can be calculated by the formula
DeltaT = T2 - T1. The RNC aggregates all DeltaTs for called UEs in the best cell A to obtain
the total call duration (recorded as All DeltaT). The number of Erlangs of mobile-terminated
AMR RABs in the best cell A can be calculated using the following formula: SUM(All DeltaT
in minute)/60 minutes. The service initiated by a UE is a mobile-terminated AMR service if the
Init Direct Transfer or UL Direct Transfer message sent by the UE to the CS CN contains the
Paging Response information element (IE).
Formula
None
Unit
Erl
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AMR.Erlang.MT
MRFD-210403
License Management

3407
BSC6900 UMTS
Erlang of AMR Services (Unidentifiable Mobile-Originated or MobileTerminated) for Cell

Counters
Counter ID
Counter Name
Counter Description
73444484
VS.AMR.Erlang.NotDistinguish
Erlang of AMR Services

(Unidentifiable MobileOriginated or MobileTerminated) for Cell
Description
This counter measures the number of Erlangs of unidentifiable AMR services (including
Unidentifiable AMR services are those transferred to the UMTS network through incoming
inter-RAT handovers or incoming relocations.
Measurement point
Assume that at time T1 a UE with an unidentifiable AMR RAB changes its best cell to cell A
and at time T2 the UE changes its best cell to another cell or releases the AMR RAB. Then, the
unidentifiable AMR call duration in the best cell A can be calculated by the formula DeltaT =
T2 - T1. The RNC aggregates all DeltaTs for all UEs with unidentifiable AMR RABs in the best
cell A to obtain the total call duration (recorded as All DeltaT). The number of Erlangs of
unidentifiable AMR RABs in the best cell A can be calculated using the following formula:
SUM(All DeltaT in minute)/60 minutes. The RNC cannot identify whether an AMR service is
a mobile-originated or mobile-terminated one if the service is transferred to the UMTS network
through an incoming inter-RAT handover or incoming relocation.
Formula
None
Unit
Erl
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AMR.Erlang.NotDistinguish
MRFD-210403
License Management

3408
BSC6900 UMTS
1.12.51 Traffic Measurement <per Cell>(TRFFIC.Cell)

Overview
This function subset involves the items related to the traffic on the common transport channels
(PCH, RACH, and FACH) and on the dedicated transport channels on the Iub Interface. The
function subset also involves the items about soft handover. The traffic on the dedicated transport
channels are measured on the basis of the service type.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189782
VS.BcchSrbKbps.
Dl
DL Signaling Rate
over BCCH for Cell
Earlier than
BSC6900
V900R011
67202807
VS.CcchSrbKbps.
Dl
DL Signaling Rate
over CCCH for Cell
Earlier than
BSC6900
V900R011
67202808
VS.CcchSrbKbps.
Ul
UL Signaling Rate
over CCCH for Cell
Earlier than
BSC6900
V900R011
67202422
VS.DRNCIubBytes
DCH.Rx
Number of UL
Service Bytes over
DRNC Iub DCH for
Cell
Earlier than
BSC6900
V900R011
67202423
VS.DRNCIubBytes
DCH.Tx
Number of DL
Service Bytes over
DRNC Iub DCH for
Cell
Earlier than
BSC6900
V900R011
67199640
VS.SRNCIubBytes
DCHSig.Rx
Number of UL
Signaling Bytes on
Iub Interface for Cell
Earlier than
BSC6900
V900R011
67199641
VS.SRNCIubBytes
DCHSig.Tx
Number of DL
Signaling Bytes on
Earlier than
BSC6900
V900R011
67199650
VS.SRNCIubBytes
PSR99Conv.Rx
Number of UL Bytes
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199651
VS.SRNCIubBytes
PSR99Str.Rx
Number of UL Bytes
of PS R99 Streaming
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011

3409
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199652
VS.SRNCIubBytes
PSR99Int.Rx
Number of UL Bytes
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199653
VS.SRNCIubBytes
PSR99Bkg.Rx
Number of UL Bytes
of PS R99
Background
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199654
VS.SRNCIubBytes
PSR99Conv.Tx
Number of DL Bytes
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199655
VS.SRNCIubBytes
PSR99Str.Tx
Number of DL Bytes
of PS R99 Streaming
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199656
VS.SRNCIubBytes
PSR99Int.Tx
Number of DL Bytes
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199657
VS.SRNCIubBytes
PSR99Bkg.Tx
Number of DL Bytes
of PS R99
Background
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199642
VS.SRNCIubBytes
CSConv.Rx
Number of UL Bytes
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199643
VS.SRNCIubBytes
CSStr.Rx
Number of UL Bytes
of CS Streaming
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199646
VS.SRNCIubBytes
CSConv.Tx
Number of DL Bytes
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011
67199647
VS.SRNCIubBytes
CSStr.Tx
Number of DL Bytes
of CS Streaming
Services over Iub
DCH for Cell
Earlier than
BSC6900
V900R011

3410
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67199639
VS.CRNCIubBytes
RACH.Rx
Number of Bytes
over Iub RACH for
Cell
Earlier than
BSC6900
V900R011
67199638
VS.CRNCIubBytes
FACH.Tx
Number of Bytes
over Iub FACH for
Cell
Earlier than
BSC6900
V900R011
67199637
VS.CRNCIubBytes
PCH.Tx
Number of Bytes
over Iub PCH for
Cell
Earlier than
BSC6900
V900R011
67199739
VS.CRNC.IUB.RA
CH.Bandwidth
RACH Bandwidth of
CRNC for Cell
Earlier than
BSC6900
V900R011
67199740
VS.CRNC.IUB.FA
CH.Bandwidth
FACH Bandwidth of
CRNC for Cell
Earlier than
BSC6900
V900R011
67199741
VS.CRNC.IUB.PC
H.Bandwidth
PCH Bandwidth of
CRNC for Cell
Earlier than
BSC6900
V900R011
67204155
VS.MBMS.IUB.BA
NDWIDTH
Bandwidth of
MBMS Services for
Cell
Earlier than
BSC6900
V900R011
67204753
VS.CRNCIubBytes
PSR99.CCH.Rx
Number of Bytes of
UL PS Services over
Iub RACH for Cell
Earlier than
BSC6900
V900R011
67204754
VS.CRNCIubBytes
PSR99.CCH.Tx
Number of Bytes of
DL PS Services over
Iub FACH for Cell
Earlier than
BSC6900
V900R011
73410499
VS.SRNCIubBytes
HSDPA.Tx
Number of DL Bytes
over Iub HSDSCH
for Cell
BSC6900
V900R012
73410500
VS.SRNCIubBytes
HSUPA.Rx
Number of UL Bytes
over Iub EDCH for
Cell
BSC6900
V900R012
73443290
VS.SRNCIubBytes
HSDSCHSig.Tx
Number of DL HSDSCH Signaling

Bytes on Iub
Interface for Cell
BSC6900
V900R015C01

3411
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73443291
VS.SRNCIubBytes
EDCHSig.Rx
Number of UL EDCH Signaling

Bytes on Iub
Interface for Cell
BSC6900
V900R015C01
73446462
VS.SRNCIubBytes
PSFACH.Tx
DL PS Traffic on the
FACH over the Iub
Interface for Cell
BSC6900
V900R017C10
73446463
VS.SRNCIubBytes
PSRACH.Rx
UL PS Traffic on the
RACH over the Iub
Interface for Cell
BSC6900
V900R017C10
73446464
VS.SRNCIubBytes
PSEFACH.Tx
DL PS Traffic on the
E-FACH over the Iub
Interface for Cell
BSC6900
V900R017C10
73446465
VS.SRNCIubBytes
PSERACH.Rx
UL PS Traffic on the
E-RACH over the
BSC6900
V900R017C10
None
DL Signaling Rate over BCCH on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67189782
VS.BcchSrbKbps.Dl
DL Signaling Rate over

BCCH for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190392
BCCH.SRB.KBPS.DL.Time
s
Duration of Measuring the

Bits of Transport Blocks on
DL BCCH for Cell
67190391
BCCH.SRB.KBPS.DL.Volume
Number of DL Bits on BCCH

for Cell

3412
BSC6900 UMTS
Description
This counter provides the average DL signaling rate of the CRNC over the BCCH on the Iub
interface within the cell.
Measurement point
When sending the DL signaling over the BCCH on the Iub interface, the CRNC measures the
data transmission period and the number of DL signaling bits (not including the FP header). At
the end of the measurement period, the value of this counter is obtained as follows: dividing the
total number of transmitted signaling bits by the transmission period.
Formula
VS.BcchSrbKbps.Dl = [BCCH.SRB.KBPS.DL.Volume]/[BCCH.SRB.KBPS.DL.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.BcchSrbKbps.Dl
WRFD-020900
Logical Channel
Management
DL Signaling Rate over CCCH on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67202807
VS.CcchSrbKbps.Dl
DL Signaling Rate over

CCCH for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189784
VS.CcchSrbKbps.Dl.Times

DL CCCH for Cell
67189783
VS.CcchSrbKbps.Dl.Volume
Number of DL Signaling Bits

on CCCH for Cell

3413
BSC6900 UMTS
Description
This counter provides the average DL signaling rate of the CRNC over the CCCH on the Iub
Measurement point
When sending the DL signaling over the CCCH on the Iub interface, the CRNC measures the
data transmission period and the number of DL signaling bits (not including the FP header). At
Formula
VS.CcchSrbKbps.Dl = [VS.CcchSrbKbps.Dl.Volume]/[VS.CcchSrbKbps.Dl.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.CcchSrbKbps.Dl
WRFD-020900
Logical Channel
Management
UL Signaling Rate over CCCH on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67202808
VS.CcchSrbKbps.Ul
UL Signaling Rate over

CCCH for Cell
specific formulas.
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67189786
VS.CcchSrbKbps.Ul.Times

UL CCCH for Cell
67189785
VS.CcchSrbKbps.Ul.Volume
Number of UL Signaling Bits

on CCCH for Cell

3414
BSC6900 UMTS
Description
This counter provides the average UL signaling rate of the CRNC over the CCCH on the Iub
Measurement point
When receiving the UL signaling over the CCCH on the Iub interface, the CRNC measures the
data transmission period and the number of UL signaling bits (not including the FP header). At
Formula
VS.CcchSrbKbps.Ul = [VS.CcchSrbKbps.Ul.Volume]/[VS.CcchSrbKbps.Ul.Times]
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.CcchSrbKbps.Ul
WRFD-020900
Logical Channel
Management
UL Service Traffic over DCH on Iub Interface for DRNC

Counters
Counter ID
Counter Name
Counter Description
67202422
VS.DRNCIubBytesDCH.Rx
Number of UL Service Bytes

over DRNC Iub DCH for
Cell
Description
This counter provides the bytes of UL MAC PDUs for the SRNC received by the DRNC over
the DCH FP that carries services on the Iub interface. The measurement involves the cells in the
active set.
Measurement point
The measurement is triggered when the DRNC receives UL data that is for the SRNC over the
DCH FP (not including the EDCH FP) that carries services on the Iub interface. The FP header
is not included.
Issue 03 (2015-06-30)

3415
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.DRNCIubBytesDCH.Rx
WRFD-021000
Transport Channel
Management
DL Service Traffic over DCH on Iub Interface for DRNC

Counters
Counter ID
Counter Name
Counter Description
67202423
VS.DRNCIubBytesDCH.Tx
Number of DL Service Bytes

over DRNC Iub DCH for
Cell
Description
This counter provides the bytes of DL MAC PDUs from the SRNC sent by the DRNC over the
DCH FP that carries services on the Iub interface. The measurement involves the cells in the
active set.
Measurement point
The measurement is triggered when the DRNC sends DL data that is from the SRNC over the
DCH FP (not including the HS-DSCH FP) that carries services on the Iub interface. The FP
header is not included.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

3416
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.DRNCIubBytesDCH.Tx
WRFD-021000
Transport Channel
Management
Counter ID
Counter Name
Counter Description
67199640
VS.SRNCIubBytesDCHSig.
Rx
Number of UL Signaling
Bytes on Iub Interface for
Cell
UL Signaling Traffic on Iub Interface

Counters
Description
This counter provides the bytes of UL MAC PDUs received by the SRNC over the DCH FP
(exclude EDCH FP and RACH FP) that carry signaling on the Iub interface. The measurement
involves the cells in the active set.
Measurement point
The measurement is triggered when the SRNC receives UL signaling over the DCH FP on the
Iub interface. The FP header is not included.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Rx
WRFD-021000
Transport Channel
Management

3417
BSC6900 UMTS
DL Signaling Traffic on Iub Interface

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

Counters
Issue 03 (2015-06-30)

3418
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67199651
VS.SRNCIubBytesPSR99St
r.Rx
R99 Streaming Services over
Iub DCH for Cell
67199652
VS.SRNCIubBytesPSR99In
t.Rx
R99 Interactive Services over
Iub DCH for Cell
67199653
VS.SRNCIubBytesPSR99B
kg.Rx
R99 Background Services
over Iub DCH for Cell
Description
These counters provide the number of uplink MAC PDU bytes received by the SRNC on the PS
R99 service bearer DCH FP over the Iub interface in a cell in the active set.
Measurement point
The measurement is triggered when the SRNC receives uplink data carried on the PS R99 service
bearer DCH FP over the Iub interface. The measured data excludes the FP header.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
onv.Rx
WRFD-010501
r.Rx
WRFD-010502
Streaming QoS Class
t.Rx
WRFD-010503
kg.Rx
WRFD-010504

3419
BSC6900 UMTS
DL PS R99 Traffic on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67199654
onv.Tx
Iub DCH for Cell
67199655
r.Tx
R99 Streaming Services over
Iub DCH for Cell
67199656
t.Tx
R99 Interactive Services over
Iub DCH for Cell
67199657
kg.Tx
R99 Background Services
over Iub DCH for Cell
Description
These counters provide the number of downlink MAC PDU bytes sent by the SRNC on the PS
R99 service bearer DCH FP over the Iub interface in a cell in the active set.
Measurement point
The measurement is triggered when the SRNC sends downlink data carried on the PS R99 service
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
onv.Tx
WRFD-010501
r.Tx
WRFD-010502
Streaming QoS Class

3420
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
t.Tx
WRFD-010503
kg.Tx
WRFD-010504
Counter ID
Counter Name
Counter Description
67199642
VS.SRNCIubBytesCSConv.
Rx
Iub DCH for Cell
67199643
VS.SRNCIubBytesCSStr.Rx
Streaming Services over Iub
DCH for Cell
UL CS Traffic on Iub Interface

Counters
Description
These counters provide the number of uplink MAC PDU bytes received by the SRNC on the
CS service bearer DCH FP over the Iub interface in a cell in the active set.
Measurement point
The measurement is triggered when the SRNC receives uplink data carried on the CS service
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Rx
WRFD-010501
VS.SRNCIubBytesCSStr.Rx
WRFD-010502
Streaming QoS Class

3421
BSC6900 UMTS
DL CS Traffic on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67199646
Tx
Iub DCH for Cell
67199647
VS.SRNCIubBytesCSStr.Tx
Streaming Services over Iub
DCH for Cell
Description
These counters provide the number of downlink MAC PDU bytes sent by the SRNC on the CS
service bearer DCH FP over the Iub interface in a cell in the active set.
Measurement point
The measurement is triggered when the SRNC sends downlink data carried on the CS service
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Tx
WRFD-010501
VS.SRNCIubBytesCSStr.Tx
WRFD-010502
Streaming QoS Class

3422
BSC6900 UMTS
Traffic over RACH on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67199639
VS.CRNCIubBytesRACH.R
x

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

FACH for Cell
Traffic over FACH on Iub Interface

Counters
Issue 03 (2015-06-30)

3423
BSC6900 UMTS
Description
This counter provides the bytes of DL MAC PDUs (including the signaling data and the service
data, not including the FP header) sent by the CRNC over the FACH FP on the Iub interface.
The measurement involves cells in the active set.
Measurement point
The measurement is triggered when the CRNC sends DL data over the FACH FP on the Iub
interface.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.CRNCIubBytesFACH.T
x
WRFD-021000
Transport Channel
Management
Counter ID
Counter Name
Counter Description
67199637
VS.CRNCIubBytesPCH.Tx

PCH for Cell
Traffic over PCH on Iub Interface

Counters
Description
This counter provides the number of bytes in PI fields of headers and payload of the PCH FP
packets transmitted over the Iub interface by the CRNC in a cell.
Measurement point
The measurement is triggered when the CRNC sends DL data over the PCH FP on the Iub
interface.
Formula
None
Issue 03 (2015-06-30)

3424
BSC6900 UMTS
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.CRNCIubBytesPCH.Tx
WRFD-021000
Transport Channel
Management
Counters Related to the Bandwidth of Common Channels on Iub Interface for

CRNC
Counters
Counter ID
Counter Name
Counter Description
67199739
VS.CRNC.IUB.RACH.Ban
dwidth
RACH Bandwidth of CRNC

for Cell
67199740
VS.CRNC.IUB.FACH.Band
width
FACH Bandwidth of CRNC

for Cell
67199741
VS.CRNC.IUB.PCH.Bandwidth
PCH Bandwidth of CRNC

for Cell
Description
These counters provide the bandwidth of common channels for the CRNC on the Iub interface
in the unit of bytes per second. The measurement involves cells in the active set.
Measurement point
The measurement is triggered when the CRNC sets up or removes a common channel on the
Iub interface.
Formula
None
Unit
byte/s
Issue 03 (2015-06-30)

3425
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.CRNC.IUB.RACH.Ban
dwidth
WRFD-021000
Transport Channel
Management
VS.CRNC.IUB.FACH.Band
width
WRFD-021000
Transport Channel
Management
VS.CRNC.IUB.PCH.Bandwidth
WRFD-021000
Transport Channel
Management
Bandwidth of Channel for MBMS Services

Counters
Counter ID
Counter Name
Counter Description
67204155
VS.MBMS.IUB.BANDWIDTH
Bandwidth of MBMS
Services for Cell
Description
This counter provides the bandwidth of the channel for MBMS services on the Iub interface in
the cell.
Measurement point
The measurement is triggered when an MBMS service is set up successfully in the cell.
Formula
None
Unit
byte/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MBMS.IUB.BANDWIDTH
WRFD-010616
MBMS Introduction
Package

3426
BSC6900 UMTS
PS Traffic over RACH on Iub Interface

Counters
Counter ID
Counter Name
Counter Description
67204753
VS.CRNCIubBytesPSR99.C
CH.Rx
Number of Bytes of UL PS
Services over Iub RACH for
Cell
Description
This counter provides the bytes of UL MAC PDUs (not including the FP header) received by
the CRNC over the RACH FP on the Iub interface. The measurement involves cells in the active
set.
Measurement point
The measurement is triggered when the CRNC receives UL data over the RACH FP that carries
PS services on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
CH.Rx
WRFD-021000
Transport Channel
Management
PS Traffic over FACH on Iub Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204754
CH.Tx
Number of Bytes of DL PS
Services over Iub FACH for
Cell

3427
BSC6900 UMTS
Description
This counter provides the bytes of DL MAC PDUs (not including the FP header) sent by the
CRNC over the FACH FP on the Iub interface. The measurement involves cells in the active
set.
Measurement point
The measurement is triggered when the CRNC sends DL data over the FACH FP that carries
PS services on the Iub interface.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
CH.Tx
WRFD-021000
Transport Channel
Management
Counter ID
Counter Name
Counter Description
73410499
VS.SRNCIubBytesHSDPA.
Tx
Number of DL Bytes over

Iub HSDSCH for Cell
DL HSDPA Traffic on Iub Interface

Counters
Description
This counter provides the bytes of DL MAC PDUs sent by the SRNC over the HS-DSCH FP
on the Iub interface(exclude DL signal data). The measurement involves HSDPA serving cells.
For DC-HSDPA users, this counter is measured only in the primary cell based on the total number
of bytes sent on the primary and secondary carriers.
Measurement point
The measurement is triggered when the SRNC sends DL data over the HS-DSCH FP on the Iub
Issue 03 (2015-06-30)

3428
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.SRNCIubBytesHSDPA.
Tx
WRFD-010610
HSDPA Introduction
Package
Counter ID
Counter Name
Counter Description
73410500
VS.SRNCIubBytesHSUPA.
Rx
Number of UL Bytes over

Iub EDCH for Cell
UL HSUPA Traffic on Iub Interface

Counters
Description
This counter provides the number of UL MAC PDU bytes (excluding UL signaling data)
received by the SRNC on the E-DCH FP over the Iub interface. This counter is measured in
HSUPA cells in the active set.For a DC-HSUPA UE, this counter is measured only on the primary
carrier if the DC-HSUPA UE only uses the primary carrier for data transmission. If a DC-HSUPA
UE uses both the primary and secondary carriers for data transmission, this counter measures
the total number of UL MAC PDU bytes received by the SRNC on the E-DCH FP over the Iub
interface on the primary carrier. If a DC-HSUPA only uses the secondary carrier for data
transmission, this counter is measured only on the secondary carrier.
Measurement point
The measurement is triggered when the SRNC receives UL data over the EDCH FP on the Iub
Formula
None
Unit
byte
Issue 03 (2015-06-30)

3429
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SRNCIubBytesHSUPA.
Rx
WRFD-010612
HSUPA Introduction
Package
Number of DL HS-DSCH Signaling Bytes on Iub Interface for Cell

Counters
Counter ID
Counter Name
Counter Description
73443290
VS.SRNCIubBytesHSDSC
HSig.Tx
Number of DL HS-DSCH
Signaling Bytes on Iub
Interface for Cell
Description
This counter provides the number of DL MAC PDU bytes sent by the SRNC on the HS-DSCH
FP carrying signaling over the Iub interface in an HSDPA serving cell. This counter does not
include the HS-DSCH FP carrying DL signaling when UEs are in the enhanced CELL_FACH
state.
Measurement point
The measurement is triggered when the SRNC sends DL signaling data on the HS-DSCH FP
carrying signaling over the Iub interface. The FP header is not included.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRNCIubBytesHSDSC
HSig.Tx
WRFD-010652
SRB over HSDPA

3430
BSC6900 UMTS
Number of UL E-DCH Signaling Bytes on Iub Interface for Cell

Counters
Counter ID
Counter Name
Counter Description
73443291
VS.SRNCIubBytesEDCHSi
g.Rx
Number of UL E-DCH
Signaling Bytes on Iub
Interface for Cell
Description
This counter provides the number of UL MAC PDU bytes received by the SRNC on the E-DCH
FP carrying signaling over the Iub interface. This counter is measured in HSUPA cells in the
active set. This counter does not include the E-DCH FP carrying UL signaling when UEs are in
the enhanced CELL_FACH state.
Measurement point
The measurement is triggered when the SRNC receives UL signaling data on the E-DCH FP
carrying signaling over the Iub interface. The FP header is not included.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.SRNCIubBytesEDCHSi
g.Rx
WRFD-010636
SRB over HSUPA
DL PS Traffic on the FACH over the Iub Interface for Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73446462
VS.SRNCIubBytesPSFACH
.Tx
DL PS Traffic on the FACH

over the Iub Interface for Cell

3431
BSC6900 UMTS
Description
This counter provides the number of DL MAC PDU bytes received by the SRNC on the PS
service bearer FACH FP over the Iub interface in a serving cell. This counter does not include
DL signaling data or FP headers.
Measurement point
The measurement is triggered when the SRNC sends downlink data carried on the PS service
bearer FACH FP over the Iub interface. This counter measures only the downlink data carried
on the PS service bearer FACH FP and does not measure the downlink data carried on the EFACH FP.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.SRNCIubBytesPSFACH
.Tx
WRFD-021000
Transport Channel
Management
UL PS Traffic on the RACH over the Iub Interface for Cell

Counters
Counter ID
Counter Name
Counter Description
73446463
VS.SRNCIubBytesPSRAC
H.Rx
UL PS Traffic on the RACH

over the Iub Interface for Cell
Description
This counter provides the number of UL MAC PDU bytes received by the SRNC on the PS
service bearer RACH FP over the Iub interface in a serving cell. This counter does not include
UL signaling data or FP headers.
Measurement point
The measurement is triggered when the SRNC receives uplink data carried on the PS service
bearer RACH FP over the Iub interface. This counter measures only the uplink data carried on
Issue 03 (2015-06-30)

3432
BSC6900 UMTS
the PS service bearer RACH FP and does not measure the uplink data carried on the E-RACH
FP.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.SRNCIubBytesPSRAC
H.Rx
WRFD-021000
Transport Channel
Management
DL PS Traffic on the E-FACH over the Iub Interface for Cell

Counters
Counter ID
Counter Name
Counter Description
73446464
VS.SRNCIubBytesPSEFAC
H.Tx
DL PS Traffic on the EFACH over the Iub Interface

for Cell
Description
This counter provides the number of DL MAC PDU bytes received by the SRNC on the PS
service bearer E-FACH FP over the Iub interface in a serving cell. This counter does not include
DL signaling data or FP headers.
Measurement point
The measurement is triggered when the SRNC sends downlink data carried on the PS service
bearer E-FACH FP over the Iub interface.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

3433
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SRNCIubBytesPSEFAC
H.Tx
WRFD-010688
Downlink Enhanced
CELL_FACH
UL PS Traffic on the E-RACH over the Iub Interface for Cell

Counters
Counter ID
Counter Name
Counter Description
73446465
VS.SRNCIubBytesPSERAC
H.Rx
UL PS Traffic on the ERACH over the Iub Interface

for Cell
Description
This counter provides the number of UL MAC PDU bytes received by the SRNC on the PS
service bearer E-RACH FP over the Iub interface in a serving cell. This counter does not include
UL signaling data or FP headers.
Measurement point
The measurement is triggered when the SRNC receives uplink data carried on the PS service
bearer E-RACH FP over the Iub interface.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SRNCIubBytesPSERAC
H.Rx
WRFD-010701
Uplink Enhanced
CELL_FACH

3434
BSC6900 UMTS
1.12.52 UL Interoperability Measurement <per Cell>

(U2LTE.HO.Cell)
Overview
According to handover methods, outgoing UMTS-to-LTE PS handovers can be classified into
PS inter-RAT handovers and redirection triggered by RRC connection release. Counters related
to the number of failed handovers during different phases of outgoing handovers are measured
based on different handover causes.
Issue 03 (2015-06-30)

3435
BSC6900 UMTS
Figure 1-1431 Flow chart of measurement related to U2L Handover
Issue 03 (2015-06-30)

3436
BSC6900 UMTS
Issue 03 (2015-06-30)
Measurement points
Description
VS.U2LTEHO.AttRelocPrepOutPS,
VS.U2LHO.AttRelocPrepOutPS.Coverage,
VS.U2LTEHO.AttRelocPrepOutPS.Service,
VS.U2LTEHO.AttRelocPrepOutPS.Load
VS.U2LTEHO.SuccRelocPrepOutPS,
VS.U2LHO.SuccRelocPrepOutPS.Coverage,
VS.U2LTEHO.SuccRelocPrepOutPS.Service,
VS.U2LTEHO.SuccRelocPrepOutPS.Load
VS.U2LTEHO.AttOutPS.Service,
VS.U2LHO.AttOutPS.Coverage,
VS.U2LTEHO.AttOutPS.Load,
VS.U2LTEHO.AttOutPS
VS.U2LTEHO.SuccOutPS.Service,
VS.U2LHO.SuccOutPS.Coverage,
VS.U2LTEHO.SuccOutPS.Load,
VS.U2LTEHO.SuccOutPS
VS.U2LTEHO.FailRelocPrepOutPS.NoResAvail,
VS.U2LTEHO.FailRelocPrepOutPS.TgtFail
, VS.U2LTEHO.FailRelocPrepOutPS.ReloUnSupp,
VS.U2LTEHO.FailRelocPrepOutPS.TgtHig
hLoad,
VS.U2LTEHO.FailRelocPrepOutPS.UnKnowRNC,
VS.U2LTEHO.FailRelocPrepOutPS.TAlEx
p
VS.U2LTEHO.FailOutPS.CfgUnSupp,
VS.U2LTEHO.FailOutPS.PhyChFail
VS.U2LTEHO.FailOutPS.NoReply,
VS.U2LTEHO.FailOutPS.Abort
VS.U2LTEHO.RRCRelease.Service,
VS.U2LTEHO.RRCRelease.Coverage,
VS.U2LTEHO.RRCRelease.Coverage.Eme
rgBlind, VS.U2LTEHO.RRCRelease.Load,
VS.U2LTEHO.RRCRelease.Load.Blind,
VS.U2LTEHO.RRCRelease.Sevice.Blind,
VS.U2LTEHO.RRCRelease.FastReturn.Bli
nd

3437
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423386
VS.U2LTEHO.Att
OutPS.Service
Number of ServiceBased UMTS-toLTE PS Handover

Attempts for Cell
BSC6900
V900R013
73423387
VS.U2LTEHO.Suc
cOutPS.Service
Number of
Successful ServiceBased UMTS-toLTE PS Handovers
for Cell
BSC6900
V900R013
73423408
VS.U2LTEHO.Fail
OutPS.NoReply
Number of Failed
UMTS-to-LTE PS
Handovers Due to Iu
Release Command
Timeout for Cell
BSC6900
V900R013
73423409
VS.U2LTEHO.Fail
OutPS.CfgUnSupp
Number of Failed
UMTS-to-LTE PS
Handovers for Cell
(Configuration
Unsupported)
BSC6900
V900R013
73423410
VS.U2LTEHO.Fail
OutPS.PhyChFail
Number of Failed
UMTS-to-LTE PS
Handovers for Cell
(Physical Channel
Failure)
BSC6900
V900R013
73423411
VS.U2LTEHO.Fail
OutPS.Abort
Number of
Abnormally
Terminated
Outgoing UMTS-toLTE PS Handovers
for Cell
BSC6900
V900R013
73423412
VS.U2LTEHO.AttRelocPrepOutPS
Number of Outgoing
UMTS-to-LTE PS
Handover
Preparation
Attempts for Cell
BSC6900
V900R013
73423413
VS.U2LTEHO.Suc
cRelocPrepOutPS
Number of
Successful
Preparations for
for Cell
BSC6900
V900R013

3438
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423414
VS.U2LTEHO.Fail
RelocPrepOutPS.N
oResAvail
Number of Failed
Preparations for
for Cell (No
Resource Available)
BSC6900
V900R013
73423415
VS.U2LTEHO.Fail
RelocPrepOutPS.T
gtFail
Number of Failed
Preparations for
for Cell (Relocation
Failure in Target CN/
RNC or Target
System)
BSC6900
V900R013
73423416
VS.U2LTEHO.Fail
RelocPrepOutPS.R
eloUnSupp
Number of Failed
Preparations for
for Cell (Relocation
not supported in
Target RNC or
Target system)
BSC6900
V900R013
73423417
VS.U2LTEHO.Fail
RelocPrepOutPS.T
gtHighLoad
Number of Failed
Preparations for
for Cell (Traffic
Load In The Target
Cell Higher Than In
The Source Cell)
BSC6900
V900R013
73423418
VS.U2LTEHO.Fail
RelocPrepOutPS.U
nKnowRNC
Number of Failed
Preparations for
for Cell (Unknown
Target RNC)
BSC6900
V900R013
73423419
VS.U2LTEHO.RR
CRelease.Service
Number of ServiceBased Redirection to

LTE Through RRC
Connection Release
for Cell
BSC6900
V900R013

3439
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73423420
VS.U2LTEHO.Fail
RelocPrepOutPS.T
AlExp
Number of Failed
Preparations for
for Cell
(TRELOCalloc
expiry)
BSC6900
V900R013
73425851
VS.U2LHO.AttOut
PS.Coverage
Number of
Measurement-based
UMTS-to-LTE PS
Handover Attempts
Triggered by Poor
Coverage for Cell
BSC6900
V900R015C00
73425852
VS.U2LHO.SuccO
utPS.Coverage
Number of
Successful
Measurement-based
UMTS-to-LTE PS
Handovers Triggered
by Poor Coverage for
Cell
BSC6900
V900R015C00
73425853
VS.U2LHO.AttRel
ocPrepOutPS.Coverage
Number of
Preparation
Attempts for
Outgoing Coveragetriggered UMTS-toLTE PS Handovers
for Cell
BSC6900
V900R015C00
73425854
VS.U2LHO.SuccRe
locPrepOutPS.Coverage
Number of
Successful
Preparations for
Outgoing Coveragetriggered UMTS-toLTE PS Handovers
for Cell
BSC6900
V900R015C00
73425855
VS.U2LTEHO.RR
CRelease.Coverage
Number of
Coverage-based
UMTS to LTE PS
BSC6900
V900R015C00
73425856
VS.U2LTEHO.RR
CRelease.Coverage
.EmergBlind
Number of
Coverage-based
UMTS to LTE PS
Emergency Blind
BSC6900
V900R015C00

3440
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73425857
VS.U2LTEHO.Att
OutPS.Load
Number of LDRtriggered UMTS-toLTE PS Handover

Attempts for Cell
BSC6900
V900R015C00
73425858
VS.U2LTEHO.Suc
cOutPS.Load
Number of
Successful LDRtriggered UMTS-toLTE PS Handovers
for Cell
BSC6900
V900R015C00
73425859
VS.U2LTEHO.RR
CRelease.Load
Number of Loadbased UMTS to LTE

PS Redirections for
Cell
BSC6900
V900R015C00
73425860
VS.U2LTEHO.RR
CRelease.Load.Bli
nd
Number of Loadbased UMTS to LTE

PS Blind
BSC6900
V900R015C00
73425819
VS.U2LTEHO.RR
CRelease.Sevice.Bli
nd
Number of Servicebased UMTS to LTE

PS Blind
BSC6900
V900R015C00
73428669
VS.U2LTEHO.RR
CRelease.FastRetu
rn.Blind
Number of UMTS to
LTE Blind
Redirections
Through Fast Return
for Cell
BSC6900
V900R016C00
73428689
VS.U2LTEHO.Att
RelocPrepOutPS.S
ervice
Number of
Preparation
Attempts for PS
Outgoing U2L
Service-Based
Handovers for Cell
BSC6900
V900R016C00
73428693
VS.U2LTEHO.Att
RelocPrepOutPS.L
oad
Number of
Preparation
Attempts for PS
Outgoing U2L LoadBased Handovers for
Cell
BSC6900
V900R016C00

3441
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428690
VS.U2LTEHO.Suc
cRelocPrepOutPS.
Service
Number of
Successful
Preparations for PS
Outgoing U2L
Service-Based
Handovers for Cell
BSC6900
V900R016C00
73428694
VS.U2LTEHO.Suc
cRelocPrepOutPS.
Load
Number of
Successful
Preparations for PS
Outgoing U2L LoadBased Handovers for
Cell
BSC6900
V900R016C00
73428691
VS.U2LTEHO.AttOutPS
Number of PS
Outgoing U2L
Handover Attempts
for Cell
BSC6900
V900R016C00
73428692
VS.U2LTEHO.Suc
cOutPS
Number of
Successful PS
Outgoing U2L
Handovers for Cell
BSC6900
V900R016C00
73428937
VS.U2LTEHO.Me
asCtrl.Num
Number of Times
That Measurement
Control Messages
Are Delivered for
LTE Measurement
for Cell
BSC6900
V900R016C00
73428938
VS.U2LTEHO.Me
asTimeOut.Num
Number of Times
That LTE
Measurement
Expires for Cell
BSC6900
V900R016C00
73430075
VS.U2L.OutOfUT
RAN.CellResel.PC
H
Number of Times
PCH UEs Leave
UTRAN Through
Cell Reselections for
Cell
BSC6900
V900R017C10
73430076
VS.U2L.OutOfUT
RAN.CellResel.FA
CH
Number of Times
FACH UEs Leave
UTRAN Through
Cell Reselections for
Cell
BSC6900
V900R017C10

3442
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430150
VS.U2LHO.FastRe
turn.AttRelocPrep
OutPS.SRVCCUE
Number of
Preparation
Attempts for U2L PS
Handovers Triggered
by Fast Return of
SRVCC UEs for Cell
BSC6900
V900R017C10
73430151
VS.U2LHO.FastRe
turn.SuccRelocPre
pOutPS.SRVCCU
E
Number of
Successful
Preparations for U2L
PS Handovers
Triggered by Fast
Return of SRVCC
UEs for Cell
BSC6900
V900R017C10
73430152
VS.U2LHO.FastRe
turn.AttOutPS.SR
VCCUE
Number of U2L PS
Handover Attempts
Triggered by Fast
Return of SRVCC
UEs for Cell
BSC6900
V900R017C10
73430153
VS.U2LHO.FastRe
turn.SuccOutPS.S
RVCCUE
Number of
Successful U2L PS
Handovers Triggered
by Fast Return of
SRVCC UEs for Cell
BSC6900
V900R017C10
73430154
VS.U2L.FastRetur
n.Redirect.SRVCC
UE
Number of U2L
Redirections
Triggered by Fast
Return of SRVCC
UEs for Cell
BSC6900
V900R017C10
73430173
VS.U2L.FastRetur
n.Redirect.CSFBU
E
Number of U2L
Redirections
Triggered by Fast
Return of CSFB UEs
for Cell
BSC6900
V900R017C10
73430174
VS.U2LHO.FastRe
turn.AttRelocPrep
OutPS.CSFBUE
Number of
Preparation
Attempts for U2L PS
Handovers Triggered
by Fast Return of
CSFB UEs for Cell
BSC6900
V900R017C10

3443
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430175
VS.U2LHO.FastRe
turn.SuccRelocPre
pOutPS.CSFBUE
Number of
Successful
PS Handovers
Triggered by Fast
Return of CSFB UEs
for Cell
BSC6900
V900R017C10
73430176
VS.U2LHO.FastRe
turn.AttOutPS.CS
FBUE
Number of U2L PS
Handover Attempts
Triggered by Fast
Return of CSFB UEs
for Cell
BSC6900
V900R017C10
73430177
VS.U2LHO.FastRe
turn.SuccOutPS.C
SFBUE
Number of
Successful U2L PS
Handovers Triggered
by Fast Return of
CSFB UEs for Cell
BSC6900
V900R017C10
Each counter's is greater than the sum of its subcounters' values
Counter
Sub Counter
VS.U2LHO.AttRelocPrepOutPS.Coverage
VS.U2LTEHO.AttRelocPrepOutPS.Service
VS.U2LTEHO.AttRelocPrepOutPS.Load
VS.U2LTEHO.SuccRelocPrepOutPS
VS.U2LHO.SuccRelocPrepOutPS.Coverage
VS.U2LTEHO.SuccRelocPrepOutPS.Service
VS.U2LTEHO.SuccRelocPrepOutPS.Load
Issue 03 (2015-06-30)
VS.U2LTEHO.RRCRelease.Coverage
rgBlind
VS.U2LTEHO.RRCRelease.Load
VS.U2LTEHO.RRCRelease.Load.Blind
VS.U2LTEHO.RRCRelease.Service
VS.U2LTEHO.RRCRelease.Sevice.Blind

3444
BSC6900 UMTS
Number of Outgoing UMTS-to-LTE PS Handover Preparation Attempts for Cell

Counters
Counter ID
Counter Name
Counter Description
73423412
Number of Outgoing UMTSto-LTE PS Handover

Preparation Attempts for Cell
73428689
VS.U2LTEHO.AttRelocPre
pOutPS.Service
Attempts for PS Outgoing
U2L Service-Based
Handovers for Cell
73428693
pOutPS.Load
Attempts for PS Outgoing
U2L Load-Based Handovers
for Cell
Description
These counters provide the number of attempts to prepare for an outgoing UMTS-to-LTE PS
handover in the best cell.The preceding counters comply with section "9.1.9 RELOCATION
REQUIRED" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A shown in the figure, when the RNC sends the CN a
RELOCATION REQUIRED message during the outgoing UMTS-to-LTE PS handover. In this
case, this counter is measured in the best cell that the UE camps on under the SRNC.
Figure 1-1432 Normal PS UMTS to LTE outgoing handover Procedure
Issue 03 (2015-06-30)

3445
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-140218
Service-Based PS Handover
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
Handover from UMTS to
LTE
Load Based PS Handover
from UMTS to LTE
pOutPS.Service
WRFD-140218
from UMTS to LTE
pOutPS.Load
WRFD-150217

from UMTS to LTE
Number of Preparation Attempts for Outgoing Coverage-triggered UMTS-to-LTE

PS Handovers
Counters
Counter ID
Counter Name
Counter Description
73425853
VS.U2LHO.AttRelocPrepO
utPS.Coverage
Attempts for Outgoing
Coverage-triggered UMTSto-LTE PS Handovers for
Cell
Description
This counter provides the number of preparation attempts for outgoing U2L PS handovers
triggered by poor coverage in the best cell where the UE camps. U2L refers to handovers from
the UMTS network to the LTE network.This counter complies with section "9.1.9
RELOCATION REQUIRED" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

3446
BSC6900 UMTS
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC sends a
RELOCATION REQUIRED message to the CN. This counter is measured in the best cell under
the SRNC where the UE is currently served.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.U2LHO.AttRelocPrepO
utPS.Coverage
WRFD-150220
Coverage Based PS
LTE

3447
BSC6900 UMTS
Number of Successful Preparations for Outgoing UMTS-to-LTE PS Handovers for

Cell
Counters
Counter ID
Counter Name
Counter Description
73423413
UMTS-to-LTE PS
Handovers for Cell
73428690
VS.U2LTEHO.SuccRelocPr
epOutPS.Service
Preparations for PS Outgoing
U2L Service-Based
Handovers for Cell
73428694
epOutPS.Load
Preparations for PS Outgoing
U2L Load-Based Handovers
for Cell
Description
These counters provide the number of times the preparation for an outgoing UMTS-to-LTE PS
handover succeeds in the best cell.The preceding counters comply with section "9.1.12
RELOCATION COMMAND" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B shown in the figure, when the RNC receives from the
CN a RELOCATION COMMAND message during the outgoing UMTS-to-LTE PS handover.
In this case, this counter is measured in the best cell that the UE camps on under the SRNC.
Issue 03 (2015-06-30)

3448
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)
epOutPS.Service
WRFD-140218
from UMTS to LTE
epOutPS.Load
WRFD-150217

from UMTS to LTE

3449
BSC6900 UMTS
Number of Successful Preparations for Outgoing Coverage-triggered UMTS-toLTE PS Handovers

Counters
Counter ID
Counter Name
Counter Description
73425854
VS.U2LHO.SuccRelocPrep
OutPS.Coverage
Coverage-triggered UMTSto-LTE PS Handovers for
Cell
Description
This counter provides the number of successful preparations for outgoing U2L PS handovers
triggered by poor coverage in the best cell where the UE camps. U2L refers to handovers from
the UMTS network to the LTE network.This counter complies with section "9.1.12
RELOCATION COMMAND" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point B shown in the following figure when the RNC receives
a RELOCATION COMMAND message from the CN. This counter is measured in the best cell
under the SRNC where the UE is currently served.
Issue 03 (2015-06-30)

3450
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.U2LHO.SuccRelocPrep
OutPS.Coverage
WRFD-150220
Coverage Based PS
LTE
Number of PS Outgoing U2L Handover Attempts for Cell

Counters
Counter ID
Counter Name
Counter Description
73428691
VS.U2LTEHO.AttOutPS
Number of PS Outgoing U2L

73423386
VS.U2LTEHO.AttOutPS.Se
rvice
Number of Service-Based
UMTS-to-LTE PS Handover
Attempts for Cell
73425851
VS.U2LHO.AttOutPS.Coverage
Number of Measurementbased UMTS-to-LTE PS

Handover Attempts
Triggered by Poor Coverage
for Cell
73425857
VS.U2LTEHO.AttOutPS.Lo
ad
Number of LDR-triggered
UMTS-to-LTE PS Handover
Attempts for Cell
Description
These counters provide the number of UMTS-to-LTE PS handover attempts in the best UMTS
cell based on different handover causes (services, coverage, or load).The preceding counters
comply with section "8.3.7 Inter-RAT handover from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point C shown in the figure, when the RNC sends the UE a
HANDOVER FROM UTRAN COMMAND message during the UMTS-to-LTE PS handover
Issue 03 (2015-06-30)

3451
BSC6900 UMTS
triggered based on various causes. In this case, this counter is measured in the best cell that the
UE camps on under the SRNC.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.U2LTEHO.AttOutPS
WRFD-140218
from UMTS to LTE
WRFD-150217
WRFD-150220

from UMTS to LTE
Coverage Based PS
LTE
Issue 03 (2015-06-30)
VS.U2LTEHO.AttOutPS.Se
rvice
WRFD-140218
from UMTS to LTE
VS.U2LHO.AttOutPS.Coverage
WRFD-150220
Coverage Based PS
LTE

3452
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.U2LTEHO.AttOutPS.Lo
ad
WRFD-150217

from UMTS to LTE
Number of Successful PS Outgoing U2L Handovers for Cell

Counters
Counter ID
Counter Name
Counter Description
73428692
Outgoing U2L Handovers for
Cell
73423387
VS.U2LTEHO.SuccOutPS.
Service
Service-Based UMTS-toLTE PS Handovers for Cell
73425852
VS.U2LHO.SuccOutPS.Cov
erage
Measurement-based UMTSto-LTE PS Handovers
Triggered by Poor Coverage
for Cell
73425858
Load
Number of Successful LDRtriggered UMTS-to-LTE PS

Handovers for Cell
Description
These counters provide the number of successful UMTS-to-LTE PS handover attempts in the
best UMTS cell based on different handover causes (services, coverage, or load).The preceding
counters comply with section "9.1.7 IU RELEASE COMMAND" in 3GPP TS 25.413
(v10.10.0).
Measurement point
The measurement is triggered at point D shown in the figure, when the RNC receives an IU
RELEASE COMMAND message with the cause value of "Successful Relocation," "Normal
Release," or "Network Optimization" after sending a HANDOVER FROM UTRAN
COMMAND message during the UMTS-to-LTE PS handover triggered by different causes. In
this case, this counter is measured in the best cell that the UE camps on under the SRNC.
Issue 03 (2015-06-30)

3453
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-140218
from UMTS to LTE
WRFD-150217
WRFD-150220

from UMTS to LTE
Coverage Based PS
LTE
Issue 03 (2015-06-30)
Service
WRFD-140218
from UMTS to LTE
VS.U2LHO.SuccOutPS.Cov
erage
WRFD-150220
Coverage Based PS
LTE
Load
WRFD-150217

from UMTS to LTE

3454
BSC6900 UMTS
Number of Failed Preparations for Outgoing UMTS-to-LTE PS Handovers Due to

Different Causes
Counters
Counter ID
Counter Name
Counter Description
73423414
VS.U2LTEHO.FailRelocPre
pOutPS.NoResAvail
Number of Failed
UMTS-to-LTE PS
Handovers for Cell (No
Resource Available)
73423415
pOutPS.TgtFail
Number of Failed
UMTS-to-LTE PS
Handovers for Cell
73423416
pOutPS.ReloUnSupp
Number of Failed
UMTS-to-LTE PS
Handovers for Cell
system)
73423417
pOutPS.TgtHighLoad
Number of Failed
UMTS-to-LTE PS
Handovers for Cell (Traffic
Cell)
73423418
pOutPS.UnKnowRNC
Number of Failed
UMTS-to-LTE PS
Handovers for Cell
(Unknown Target RNC)
73423420
pOutPS.TAlExp
Number of Failed
UMTS-to-LTE PS
Handovers for Cell
Description
These counters indicate the failure of preparations for a UMTS-to-LTE PS handover due to
different causes at the CN or LTE. For the detailed cause, see section 9.2.1.4 in 3GPP TS 25.413.
Issue 03 (2015-06-30)

3455
BSC6900 UMTS
If the value of this counter is high, check the detailed cause at the CN or LTE.The preceding
counters comply with section "9.1.15 RELOCATION PREPARATION FAILURE" in 3GPP
TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A shown in the figure, when the RNC receives from the
CN a RELOCATION PREPARATION FAILURE message after sending the CN a
RELOCATION REQUIRED message during the outgoing UMTS-to-LTE PS handover. In this
case, the corresponding counter is measured in the best cell that the UE camps on under the
SRNC based on the failure cause.
Figure 1-1438 PS UMTS to LTE outgoing handover Prepareation Procedure(failed operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
pOutPS.NoResAvail
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)

3456
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
pOutPS.TgtFail
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
pOutPS.ReloUnSupp
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
pOutPS.TgtHighLoad
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
pOutPS.UnKnowRNC
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
pOutPS.TAlExp
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)

3457
BSC6900 UMTS
Number of Failed UMTS-to-LTE PS Handovers Due to Different Causes for Cell

Counters
Counter ID
Counter Name
Counter Description
73423409
VS.U2LTEHO.FailOutPS.C
fgUnSupp
Number of Failed UMTS-toLTE PS Handovers for Cell

(Configuration
Unsupported)
73423410
VS.U2LTEHO.FailOutPS.P
hyChFail
Number of Failed UMTS-toLTE PS Handovers for Cell

Description
These counters provide the number of failed UMTS-to-LTE PS handovers in the best cell due
to different causes. These counters indicate that the UE fails to handle the HANDOVER FROM
UTRAN COMMAND message. A high value of this counter indicates that the UE does not
support the UMTS-to-LTE PS handover or the target LTE cell has poor LTE coverage.The
preceding counters comply with section "9.1.7 IU RELEASE COMMAND" in 3GPP TS 25.413
(v10.10.0).
Measurement point
The measurement is triggered at point A shown in the figure, when the RNC receives from the
UE a HANDOVER FROM UTRAN FAILURE message during the outgoing UMTS-to-LTE
PS handover. In this case, the corresponding counter is measured in the best cell that the UE
camps on under the SRNC based on the failure cause.
Figure 1-1439 PS UMTS to LTE outgoint handover Procedure(failed operation)
Issue 03 (2015-06-30)

3458
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.U2LTEHO.FailOutPS.C
fgUnSupp
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
VS.U2LTEHO.FailOutPS.P
hyChFail
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
Number of Failed UMTS-to-LTE PS Handovers Due to Iu Release Command

Timeout for Cell
Counters
Counter ID
Counter Name
Counter Description
73423408
VS.U2LTEHO.FailOutPS.N
oReply
Number of Failed UMTS-toLTE PS Handovers Due to Iu

Release Command Timeout
for Cell
Description
This counter provides the number of times that the UMTS-to-LTE PS handover fails in the best
cell because the timer waiting for the IU RELEASE COMMAND message expires. This counter
indicates that the UMTS-to-LTE PS handover fails. A higher value indicates a lower UMTS-toLTE PS handover success rate, and the failure cause should be checked at the LTE.This counter
complies with section "9.1.7 IU RELEASE COMMAND" in 3GPP TS 25.413 (v10.10.0).
Issue 03 (2015-06-30)

3459
BSC6900 UMTS
Measurement point
The measurement is triggered at point A shown in the figure. During the UMTS-to-LTE PS
handover, after sending the HANDOVER FROM UTRAN COMMAND message, the RNC
starts the timer waiting for the IU RELEASE COMMAND message from the CN. If no message
is received from the CN before the timer expires, this counter is measured in the best cell that
the UE camps on under the SRNC before the handover.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.U2LTEHO.FailOutPS.N
oReply
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)

3460
BSC6900 UMTS
Number of Abnormally Terminated Outgoing UMTS-to-LTE PS Handovers for

Cell
Counters
Counter ID
Counter Name
Counter Description
73423411
VS.U2LTEHO.FailOutPS.A
bort
Terminated Outgoing
UMTS-to-LTE PS
Handovers for Cell
Description
This counter provides the number of times that an outgoing UMTS-to-LTE PS handover is
terminated abnormally in the best cell. This counter indicates that the UMTS-to-LTE PS
handover is terminated abnormally due to some causes at the CN or LTE. If the value of this
counter is high, check the detailed cause at the CN or LTE.This counter complies with section
"9.1.7 IU RELEASE COMMAND" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point D shown in the figure, when the RNC receives an IU
RELEASE COMMAND message with a cause value other than "Successful Relocation",
"Normal Release" or "Network Optimization" after sending a HANDOVER FROM UTRAN
COMMAND message during the UMTS-to-LTE PS handover. In this case, this counter is
measured in the best cell that the UE camps on under the SRNC.
Figure 1-1441 PS UMTS to LTE outgoing handover Procedure
Issue 03 (2015-06-30)

3461
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.U2LTEHO.FailOutPS.A
bort
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Number of Redirection to LTE Through RRC Connection Release for Cell

Counters
Counter ID
Counter Name
Counter Description
73423419
VS.U2LTEHO.RRCRelease
.Service
Number of Service-Based
Redirection to LTE Through
RRC Connection Release for
Cell
73425855
.Coverage
Number of Coverage-based
UMTS to LTE PS
73425859
.Load
Number of Load-based
UMTS to LTE PS
Description
These counters provide the number of times that the RNC sends a RRC CONNECTION
RELEASE message to instruct the UE in the best cell to redirect to the LTE network due to
different causes (services, coverage, or load). These counters include the number of
measurement-based redirections and blind redirections.The preceding counters comply with
section "8.1.4.3 Reception of an RRC CONNECTION RELEASE message by the UE" in 3GPP
TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)

3462
BSC6900 UMTS
Counter Name
Description
VS.U2LTEHO.RRCRelease.Service
This counter provides the number of times

that the RNC sends the RRC CONNECTION
RELEASE message, instructing the UE in the
best cell to redirect to the LTE network due
to service requirements. This counter
includes the number of measurement-based
redirections and blind redirections.
VS.U2LTEHO.RRCRelease.Coverage

to poor coverage. This counter includes the
number of measurement-based redirections
and blind redirections (emergency blind
redirections triggered by event 1F).
VS.U2LTEHO.RRCRelease.Load

to heavy load. This counter includes the
number of measurement-based redirections
and blind redirections.
Measurement point
The measurement is triggered at point A shown in the figure.
When the RNC sends the UE an RRC Connection Release message, indicating the UE to redirect
to the LTE. In this case, the counter VS.U2LTEHO.RRCRelease.Service is measured in the best
When the RNC sends the UE an RRC CONNECTION RELEASE message due to poor coverage,
instructing the UE to blindly redirect to the LTE cell. The counter
VS.U2LTEHO.RRCRelease.Coverage is measured in the best cell under the SRNC where the
UE is currently served.
When the RNC sends an RRC CONNECTION RELEASE message to the UE, instructing the
UE to redirect to the LTE cell due to heavy load. The counter VS.U2LTEHO.RRCRelease.Load
is measured in the best cell under the SRNC where the UE is currently served.
Issue 03 (2015-06-30)

3463
BSC6900 UMTS
Figure 1-1442 UMTS Redirection to LTE Through RRC Connection Release Procedure
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.Service
WRFD-020129
Service-Based PS Service
Redirection from UMTS to
LTE
.Coverage
WRFD-150219
Coverage Based PS
LTE
.Load
WRFD-150216
Load Based PS Redirection

from UMTS to LTE

3464
BSC6900 UMTS
Number of UMTS to LTE Blind Redirections Through RRC Connection Release

for Cell
Counters
Counter ID
Counter Name
Counter Description
73425856
.Coverage.EmergBlind
Number of Coverage-based
UMTS to LTE PS
Emergency Blind
73425860
.Load.Blind
Number of Load-based
UMTS to LTE PS Blind
73425819
.Sevice.Blind
Number of Service-based
UMTS to LTE PS Blind
Description
These counters provide the number of RRC CONNECTION RELEASE messages sent by the
RNC to instruct the UE to blindly redirect to the LTE cell due to different causes (service,
coverage, or load) in the best UMTS cell where the UE camps on.The preceding counters comply
with section "8.1.4.3 Reception of an RRC CONNECTION RELEASE message by the UE" in
3GPP TS 25.331 (v10.13.0).
Issue 03 (2015-06-30)
Counter Name
Description
rgBlind

CONNECTION RELEASE messages sent
by the RNC to instruct the UE to blindly
redirect to the LTE cell due to event 1F in the
best cell where the UE camps. U2L refers to
handovers from the UMTS network to the
LTE network.
VS.U2LTEHO.RRCRelease.Load.Blind

CONNECTION RELEASE messages sent
by the RNC to instruct the UE to blindly
redirect to LTE cells due to load reshuffling
(LDR) in the best cell where the UE camps.
VS.U2LTEHO.RRCRelease.Sevice.Blind

Connection Release messages sent by the
RNC to instruct the UE to blindly redirect to
the LTE cell due to services in the best cell
where the UE camps.

3465
BSC6900 UMTS
Measurement point
The measurement is triggered at point A shown in Figure 1.
When the RNC sends the UE an RRC CONNECTION RELEASE message due to event 1F,
VS.U2LTEHO.RRCRelease.Coverage.EmergBlind is measured in the best cell under the SRNC
where the UE is currently served.
The UE does not support LTE measurement in connected mode. Therefore, when the load in the
best cell is heavy, the RNC sends an RRC CONNECTION RELEASE message to the UE,
VS.U2LTEHO.RRCRelease.Load.Blind is measured in the best cell under the SRNC where the
UE is currently served.
The UE does not support LTE measurement in connected mode. Therefore, the RNC sends an
RRC Release message to the UE, instructing the UE to blind redirect to the LTE cell due to
services. The counter VS.U2LTEHO.RRCRelease.Sevice.Blind is measured in the best cell
under the SRNC where the UE is currently served.
Figure 1-1443 UMTS Redirection to LTE Through RRC Connection Release Procedure
Formula
None
Unit
None
Issue 03 (2015-06-30)

3466
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
.Coverage.EmergBlind
WRFD-150219
Coverage Based PS
LTE
.Load.Blind
WRFD-150216

from UMTS to LTE
.Sevice.Blind
WRFD-020129
LTE
Number of UMTS to LTE Blind Redirections Through Fast Return for Cell
Counters
Counter ID
Counter Name
Counter Description
73428669
.FastReturn.Blind
Number of UMTS to LTE

Blind Redirections Through
Fast Return for Cell
Description
This counter provides the number of UMTS to LTE blind redirections triggered by fast return
after CS services are released for the UEs who have performed CS fallback (CSFB). It is used
for assessing the number of times that the feature has taken effect.This counter complies with
section "8.1.4.3 Reception of an RRC CONNECTION RELEASE message by the UE" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A shown in Figure 1. When the RNC sends an RRC
CONNECTION RELEASE message to a UE that has performed a CSFB, due to fast return
triggered by an IU RELEASE COMMAND message sent by the UE, instructing the UE to
blindly redirect to an LTE cell working at the frequency indicated in the message, this counter
is measured in the best cell under the SRNC where the UE is currently served.
Issue 03 (2015-06-30)

3467
BSC6900 UMTS
Figure 1-1444 UMTS to LTE blind redirection through fast return
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.FastReturn.Blind
WRFD-140226
Fast Return from UMTS to

LTE
Number of Times That Measurement Control Messages Are Delivered for LTE
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428937
VS.U2LTEHO.MeasCtrl.Nu
m

Measurement Control
Messages Are Delivered for
LTE Measurement for Cell

3468
BSC6900 UMTS
Description
None
Measurement point
The measurement is triggered at point A shown in the following figure when the RNC delivers
a measurement control message to the UE to measure the signal quality of the LTE network.
Figure 1-1445 Measurement Control
Formula
None
Unit
None
Issue 03 (2015-06-30)

3469
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.U2LTEHO.MeasCtrl.Nu
m
WRFD-020129
LTE
WRFD-150219
WRFD-150216
WRFD-140218
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
Number of Times That LTE Measurement Expires for Cell

Counters
Counter ID
Counter Name
Counter Description
73428938
VS.U2LTEHO.MeasTimeO
ut.Num
Number of Times That LTE

Measurement Expires for
Cell
Description
This counter measures the number of times that the UE does not send any valid measurement
reports of LTE cells within the specified time for LTE measurement.This counter complies with
section "8.3.7 Measurement control" in 3GPP TS 25.331 (v10.13.0).
Measurement point
This counter is measured in the best cell that the UE belongs to when the UE does not send any
valid measurement reports of LTE cells within the specified time for LTE measurement.
Formula
None
Issue 03 (2015-06-30)

3470
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.U2LTEHO.MeasTimeO
ut.Num
WRFD-020129
LTE
WRFD-150219
WRFD-150216
WRFD-140218
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
Number of Times PCH UEs Leave UTRAN Through Cell Reselections for Cell
Counters
Counter ID
Counter Name
Counter Description
73430075
VS.U2L.OutOfUTRAN.Cell
Resel.PCH
Number of Times PCH UEs

Leave UTRAN Through Cell
Description
This counter provides the number of times a UE in the CELL_PCH or URA_PCH state leaves
the UTRAN network by reselecting an inter-RAT cell. For details about this counter, see section
8.5 "Iu Release" in 3GPP TS 25.413 V11.0.0.
Measurement point
The measurement is triggered at point A in figure 1. When the RNC receives an IU RELEASE
COMMAND message with the "Out of UTRAN" IE from the CN, this counter is measured in
the camping cell for the UE in the CELL_PCH state, and is measured in the cell where the UE
establishes the RRC connection for the last time for the UE in the URA_PCH state.
Issue 03 (2015-06-30)

3471
BSC6900 UMTS
Figure 1-1446 Iu release procedure initiated by the CN
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Resel.PCH
WRFD-020126
Mobility Between UMTS

and LTE Phase 1
Number of Times FACH UEs Leave UTRAN Through Cell Reselections for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430076
Resel.FACH
Number of Times FACH

UEs Leave UTRAN Through
Cell Reselections for Cell

3472
BSC6900 UMTS
Description
This counter provides the number of times a UE in the CELL_FACH state leaves the UTRAN
network by reselecting an inter-RAT cell. For details about this counter, see section 8.5 "Iu
Release" in 3GPP TS 25.413 V11.0.0.
Measurement point
The measurement is triggered at point A in figure 1. When the RNC receives an IU RELEASE
COMMAND message with the "Out of UTRAN" IE from the CN, this counter is measured in
the serving cell if the UE is in the CELL_FACH state.
Figure 1-1447 Iu release procedure initiated by the CN
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Resel.FACH
WRFD-020126
Mobility Between UMTS

and LTE Phase 1

3473
BSC6900 UMTS
Number of Preparation Attempts for U2L PS Handovers Triggered by Fast Return

of SRVCC UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73430150
VS.U2LHO.FastReturn.Att
RelocPrepOutPS.SRVCCU
E
Attempts for U2L PS
Handovers Triggered by Fast
Return of SRVCC UEs for
Cell
Description
This counter provides the number of preparation attempts for U2L PS handovers triggered by
fast return of SRVCC UEs in the best cell. SRVCC UEs are those whose VoIP services are
handed over from the LTE network to the CS domain of the UMTS network. For details about
this counter, see section 8.6 "Relocation Preparation" in 3GPP TS 25.413 V11.1.0.
Measurement point
The measurement is triggered at point A in figure 1. During this handover process, when the
RNC sends a RELOCATION REQUIRED message to the CN, this counter is measured in the
best cell under the SRNC.
Issue 03 (2015-06-30)

3474
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RelocPrepOutPS.SRVCCU
E
WRFD-171223
Fast Return to LTE for

SRVCC User
Number of Successful Preparations for U2L PS Handovers Triggered by Fast

Return of SRVCC UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73430151
VS.U2LHO.FastReturn.Suc
cRelocPrepOutPS.SRVCCU
E
Preparations for U2L PS
Return of SRVCC UEs for
Cell
Description
This counter provides the number of successful preparations for U2L PS handovers triggered
by fast return of SRVCC UEs in the best cell. SRVCC UEs are those whose VoIP services are
handed over from the LTE network to the CS domain of the UMTS network. For details about
this counter, see section 8.6 "Relocation Preparation" in 3GPP TS 25.413 V11.1.0.
Measurement point
The measurement is triggered at point B in figure 1. During this handover process, when the
RNC receives a RELOCATION COMMAND message from the CN, this counter is measured
in the best cell under the SRNC.
Issue 03 (2015-06-30)

3475
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
cRelocPrepOutPS.SRVCCU
E
WRFD-171223

SRVCC User
Number of U2L PS Handover Attempts Triggered by Fast Return of SRVCC UEs

for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430152
OutPS.SRVCCUE
Number of U2L PS
Handover Attempts
Triggered by Fast Return of
SRVCC UEs for Cell

3476
BSC6900 UMTS
Description
This counter provides the number of U2L PS handover attempts triggered by fast return of
SRVCC UEs in the best cell. SRVCC UEs are those whose VoIP services are handed over from
the LTE network to the CS domain of the UMTS network. For details about this counter, see
section 8.3.7 "Inter-RAT handover from UTRAN" in 3GPP TS 25.331 V11.1.0.
Measurement point
The measurement is triggered at point C in figure 1. During this handover process, when the
RNC sends a HANDOVER FROM UTRAN COMMAND message to the UE, this counter is
measured in the best cell under the SRNC.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OutPS.SRVCCUE
WRFD-171223

SRVCC User

3477
BSC6900 UMTS
Number of Successful U2L PS Handovers Triggered by Fast Return of SRVCC UEs

for Cell
Counters
Counter ID
Counter Name
Counter Description
73430153
cOutPS.SRVCCUE
Number of Successful U2L

PS Handovers Triggered by
Fast Return of SRVCC UEs
for Cell
Description
This counter provides the number of successful U2L PS handovers triggered by fast return of
SRVCC UEs in the best cell. SRVCC UEs are those whose VoIP services are handed over from
the LTE network to the CS domain of the UMTS network. For details about this counter, see
section 8.8 "Relocation Detect" in 3GPP TS 25.413 V11.1.0.
Measurement point
The measurement is triggered at point D in figure 1. During this handover process, when the
RNC receives an IU RELEASE COMMAND message with the cause value "Successful
Relocation", "Normal Release", or "Network Optimization" from the CN after sending a
HANDOVER FROM UTRAN COMMAND message to the UE, this counter is measured in the
best cell under the SRNC.
Issue 03 (2015-06-30)

3478
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
cOutPS.SRVCCUE
WRFD-171223

SRVCC User
Number of U2L Redirections Triggered by Fast Return of SRVCC UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73430154
VS.U2L.FastReturn.Redirec
t.SRVCCUE
Number of U2L Redirections

SRVCC UEs for Cell
Description
This counter provides the number of U2L redirections triggered by fast return of SRVCC UEs
in the best cell. SRVCC UEs are those whose VoIP services are handed over from the LTE
network to the CS domain of the UMTS network. For details about this counter, see section 8.5.2
"Actions when entering idle mode from connected mode" in 3GPP TS 25.331 V11.1.0.
Measurement point
The measurement is triggered at point A in figure 1. When the RNC sends an RRC Connection
Release message with EARFCNs to the UE during a U2L redirection triggered by fast return of
an SRVCC UE, this counter is measured in the best cell under the SRNC.
Issue 03 (2015-06-30)

3479
BSC6900 UMTS
Figure 1-1452 UMTS to LTE redirection through fast return
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
t.SRVCCUE
WRFD-171223

SRVCC User
Number of U2L Redirections Triggered by Fast Return of CSFB UEs for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430173
t.CSFBUE
Number of U2L Redirections

CSFB UEs for Cell

3480
BSC6900 UMTS
Description
This counter provides the number of U2L redirections triggered by fast return of CSFB UEs in
the best UMTS cell. CSFB UEs are those that fall back from LTE to UMTS through the CSFB
feature.
This counter complies with 3GPP TS 25.331 (V11.1.0). For details, see section 8.5.2 "Actions
when entering idle mode from connected mode" in this TS.
Measurement point
The measurement is triggered at point A in the following figure. When the RNC receives an IU
RELEASE COMMAND message from the CS domain of the CN and determines to trigger a
fast return procedure on the corresponding CSFB UE, the RNC sends an RRC Connection
Release message with EARFCNs to the CSFB UE. Under these circumstances, this counter is
Figure 1-1453 U2L redirection triggered by fast return
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
t.CSFBUE
WRFD-140226

LTE

3481
BSC6900 UMTS
Number of Preparation Attempts for U2L PS Handovers Triggered by Fast Return

of CSFB UEs for Cell
Counters
Counter ID
Counter Name
Counter Description
73430174
RelocPrepOutPS.CSFBUE
Attempts for U2L PS
Return of CSFB UEs for Cell
Description
fast return of CSFB UEs in the best cell. CSFB UEs are those that fall back from LTE to UMTS
through the CSFB feature.
This counter complies with 3GPP TS 25.413 (V11.1.0). For details about this counter, see section
8.6 "Relocation Preparation" in this TS.
Measurement point
The measurement is triggered at point A in the following figure. When the RNC sends a
RELOCATION REQUIRED message to the CN during the preceding U2L PS handover
procedure, this counter is measured in the best cell under the SRNC.
Figure 1-1454 Successful U2L PS handover
Issue 03 (2015-06-30)

3482
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RelocPrepOutPS.CSFBUE
WRFD-140226

LTE
Number of Successful Preparations for U2L PS Handovers Triggered by Fast

Counters
Counter ID
Counter Name
Counter Description
73430175
cRelocPrepOutPS.CSFBUE
Description
by fast return of CSFB UEs in the best cell. CSFB UEs are those that fall back from LTE to
UMTS through the CSFB feature.
This counter complies with 3GPP TS 25.413 (V11.1.0). For details about this counter, see section
8.6 "Relocation Preparation" in this TS.
Measurement point
RELOCATION COMMAND message from the CN during the preceding U2L PS handover
procedure, this counter is measured in the best cell under the SRNC.
Issue 03 (2015-06-30)

3483
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
cRelocPrepOutPS.CSFBUE
WRFD-140226

LTE
Number of U2L PS Handover Attempts Triggered by Fast Return of CSFB UEs for
Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430176
OutPS.CSFBUE
Number of U2L PS
Handover Attempts
CSFB UEs for Cell

3484
BSC6900 UMTS
Description
This counter provides the number of U2L PS handover attempts triggered by fast return of CSFB
UEs in the best cell. CSFB UEs are those that fall back from LTE to UMTS through the CSFB
feature.
This counter complies with 3GPP TS 25.331 (V11.1.0). For details, see section 8.3.7 "Inter-RAT
handover from UTRAN" in this TS.
Measurement point
The measurement is triggered at point C. When the RNC sends a HANDOVER FROM UTRAN
COMMAND message to the UE during the preceding U2L PS handover, this counter is measured
in the best cell under the SRNC.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OutPS.CSFBUE
WRFD-140226

LTE

3485
BSC6900 UMTS
Number of Successful U2L PS Handovers Triggered by Fast Return of CSFB UEs

for Cell
Counters
Counter ID
Counter Name
Counter Description
73430177
cOutPS.CSFBUE

PS Handovers Triggered by
Fast Return of CSFB UEs for
Cell
Description
This counter provides the number of successful U2L PS handovers triggered by fast return of
CSFB UEs in the best cell. CSFB UEs are those that fall back from LTE to UMTS through the
CSFB feature.
This counter complies with 3GPP TS 25.413 (V11.1.0). For details, see section 8.8 "Relocation
Detect" in this TS.
Measurement point
The measurement is triggered at point D in the following figure. During the preceding U2L PS
handover, when the RNC receives an IU RELEASE COMMAND message with the cause value
"Successful Relocation", "Normal Release", or "Network Optimization" from the CN after
sending a HANDOVER FROM UTRAN COMMAND message to the UE, this counter is
Issue 03 (2015-06-30)

3486
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
cOutPS.CSFBUE
WRFD-140226

LTE
1.12.53 URA Update Measurement <per Cell>(URAUPDATE.Cell)

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

3487
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67180453
VS.SuccURAUpd.
Chg
Number of
Successful URA
Updates Due to
Change of URA for
Cell
Earlier than
BSC6900
V900R011
None
Number of URA Updates Attempts for Different Causes

Counters
Counter ID
Counter Name
Counter Description
67180452
VS.AttURAUpd.Prd
Number of URA Updates

Due to Periodic URA Update
for Cell
67180451
VS.AttURAUpd.Chg
Number of URA Updates

Due to Change of URA for
Cell
Description
These counters provide the number of URA UPDATE messages received by the RNC according
to different cause values. This counter complies with section "8.3.1 Cell and URA update
Issue 03 (2015-06-30)
Counter Name
Description
VS.AttURAUpd.Prd
Number of URA UPDATE messages with the

cause value of "periodic URA update"
received by the RNC
VS.AttURAUpd.Chg
Number of URA UPDATE messages with the

cause value of "change of URA" received by
the RNC

3488
BSC6900 UMTS
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC receives a URA
UPDATE message from an UE and the UE is not involved in the RRC connection release
procedure. In this case, the RNC measures the item based on different URA update causes in
the cell selected by the UE during the URA update procedure.
Figure 1-1458 URA update procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AttURAUpd.Prd
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-010901
WRFD-010902
Intra RNC URA Update

Inter RNC URA Update
VS.AttURAUpd.Chg
WRFD-010202
WRFD-010901
WRFD-010902

URA-PCH, CELL-FACH)
Issue 03 (2015-06-30)

3489
BSC6900 UMTS
Number of Successful URA Updates for Different Causes

Counters
Counter ID
Counter Name
Counter Description
67180454
VS.SuccURAUpd.Prd
Number of Successful URA

Updates Due to Periodic
URA Update for Cell
67180453
VS.SuccURAUpd.Chg
Number of Successful URA

Updates Due to Change of
URA for Cell
Description
The measurement items provide the number of URA UPDATE CONFIRM messages sent from
the RNC to the UE according to different cause values. This counter complies with section "8.3.1
Counter Name
Description
VS.SuccURAUpd.Prd
Number of URA UPDATE CONFIRM

messages sent from the RNC to the UE after
the RNC receives the URA UPDATE
message with the cause value of "periodic
URA update"
VS.SuccURAUpd.Chg
Number of URA UPDATE CONFIRM

messages sent from the RNC to the UE after
the RNC receives the URA UPDATE
message with the cause value of "change of
URA"
Measurement point
The measurement is triggered at point B as shown in the figure, when the RNC responds with
a URA UPDATE CONFIRM message after receiving the URA UPDATE message from the UE.
In this case, the RNC measures the item based on different URA update causes in the cell that
the UE camps on after the URA update.
Issue 03 (2015-06-30)

3490
BSC6900 UMTS
Figure 1-1459 URA update procedure (successful operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SuccURAUpd.Prd
WRFD-010901
WRFD-010902
WRFD-010202

URA-PCH, CELL-FACH)
WRFD-010901
WRFD-010902
WRFD-010202

URA-PCH, CELL-FACH)
VS.SuccURAUpd.Chg
Issue 03 (2015-06-30)

3491
BSC6900 UMTS
1.12.54 Video Service Quality Measurement <per Cell>

(VIDEO.CELL)
Overview
The measurement of video service quality indicates the user experience of UEs performing
HTTP-based video streaming services.
On receiving a packet from the UE as shown by point A in the following figure, the RNC
determines that the packet is the first packet related to a video service through the service
awareness function, and considers the receive time as the start time of the video service. When
the amount of downloaded video data reaches a certain threshold, as shown by point C, the initial
buffering is complete and video playback commences. On receiving the Ack packet for the last
HTTP data packet, as shown by point D, the RNC determines that the video data download is
complete. When the TCP connection for this video service is released, as shown by point E, the
RNC determines that the video service ends. The initial buffering delay lasts from points A to
C. Video playback starts at point C and ends at point E. When the network rate is lower than the
video bitrate, the receive buffer for the video service becomes empty on the UE side, and the
video service stalls. The UE enters the buffering state again. The measurement of video service
quality is performed in the best cell for the UE.
Issue 03 (2015-06-30)

3492
BSC6900 UMTS
Figure 1-1460 Video service procedure
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429214
VS.VideoShape.Bu
rst.Num
Total Number of
Times That Video
Shaping UEs Enter
the Burst State for
Cell
BSC6900
V900R017C00

3493
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429215
VS.VideoShape.Sle
ep.Num
Total Number of
Times That Video
Shaping UEs Enter
the Sleep State for
Cell
BSC6900
V900R017C00
73445292
VS.VideoShape.UE
.Burst.Mean.Cell
Average Number of
Video Shaping UEs
in the Burst State for
Cell
BSC6900
V900R017C00
73445293
VS.VideoShape.UE
.Sleep.Mean.Cell
Average Number of
Video Shaping UEs
in the Sleep State for
Cell
BSC6900
V900R017C00
73429226
VS.VideoShape.Bu
rst.Duration
Total Duration
During Which Video
Shaping UEs Stay in
the Burst State for
Cell
BSC6900
V900R017C00
73429227
VS.VideoShape.Sle
ep.Duration
Total Duration
During Which Video
Shaping UEs Stay in
the Sleep State for
Cell
BSC6900
V900R017C00
73429290
VS.VideoShape.D2
F.Att
Number of D2F State

Transition Attempts
Triggered upon
Video Service
Traffic Shaping for
Cell
BSC6900
V900R017C00
73429291
VS.VideoShape.D2
F.Succ
Number of
Successful D2F State
Transitions
Triggered upon
Video Service
Traffic Shaping for
Cell
BSC6900
V900R017C00
73429292
VS.VideoShape.F2
D.Att
Number of F2D State

Transition Attempts
Triggered upon
Video Service
Traffic Shaping for
Cell
BSC6900
V900R017C00

3494
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73429293
VS.VideoShape.F2
D.Succ
Number of
Successful F2D State
Transitions
Triggered upon
Video Service
Traffic Shaping for
Cell
BSC6900
V900R017C00
73429294
VS.VideoShape.D2
P.Att
Number of D2P State

Transition Attempts
Triggered upon
Video Service
Traffic Shaping for
Cell
BSC6900
V900R017C00
73429295
VS.VideoShape.D2
P.Succ
Number of
Successful D2P State
Transitions
Triggered upon
Video Service
Traffic Shaping for
Cell
BSC6900
V900R017C00
73429296
VS.VideoShape.P2
D.Att
Number of P2D State

Transition Attempts
Triggered upon
Video Service
Traffic Shaping for
Cell
BSC6900
V900R017C00
73429297
VS.VideoShape.P2
D.Succ
Number of
Transitions
Triggered upon
Video Service
Traffic Shaping for
Cell
BSC6900
V900R017C00
73445325
VS.Video.UE.Mean
.Cell
Average Number of
UEs Playing Online
Video Services for
cell
BSC6900
V900R017C00
73445326
VS.VideoShape.Bu
ffer.Time
Average Buffer
Delay of UEs During
Video Shaping and
Scheduling for Cell
BSC6900
V900R017C00

3495
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73445345
VS.VideoShape.Bu
rst.Data
Total Data Volume

Transmitted by
Video Shaping UEs
in the Burst State for
Cell
BSC6900
V900R017C00
None
Total Number of Times That Video Shaping UEs Enter the Burst State for Cell
Counters
Counter ID
Counter Name
Counter Description
73429214
VS.VideoShape.Burst.Num
Total Number of Times That

Video Shaping UEs Enter the
Burst State for Cell
Description
This counter measures the total number of times that video shaping UEs enter the burst state
during video shaping in a cell. The measurement is triggered only when the video shaping
function is enabled.
Measurement point
When video shaping UEs enter the burst state after a state transition from CELL_FACH to
CELL_DCH, or from CELL_PCH to CELL_DCH, the RNC measures the total number of times
that video shaping UEs enter the burst state in the best cell that the UEs camp on.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3496
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.Burst.Num
WRFD-170204
Radio Awared Video

Shaping
Total Number of Times That Video Shaping UEs Enter the Sleep State for Cell
Counters
Counter ID
Counter Name
Counter Description
73429215
VS.VideoShape.Sleep.Num
Total Number of Times That

Video Shaping UEs Enter the
Sleep State for Cell
Description
This counter measures the total number of times that video shaping UEs enter the sleep state
during video shaping in a cell. The measurement is triggered only when the video shaping
function is enabled.
Measurement point
When video shaping UEs enter the sleep state after a state transition from CELL_DCH to
CELL_FACH, or from CELL_DCH to CELL_PCH, the RNC obtains the total number of times
that video shaping UEs enter the sleep state in the cell that the UEs camp on.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VideoShape.Sleep.Num
WRFD-170204
Radio Awared Video

Shaping

3497
BSC6900 UMTS
Average Number of Video Shaping UEs in the Burst State for Cell
Counters
Counter ID
Counter Name
Counter Description
73445292
VS.VideoShape.UE.Burst.M
ean.Cell
Average Number of Video

Shaping UEs in the Burst
State for Cell
Description
This counter measures the average number of video shaping UEs in the burst state in a cell. The
measurement is triggered only when the video shaping function is enabled.
Measurement point
The RNC takes samples of the number of video shaping UEs in the burst state 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 number of video shaping UEs in the burst state by the
number of sampling times. This counter is measured in the best cell that video shaping UEs
camp on.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.UE.Burst.M
ean.Cell
WRFD-170204
Radio Awared Video

Shaping
Average Number of Video Shaping UEs in the Sleep State for Cell
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73445293
VS.VideoShape.UE.Sleep.
Mean.Cell
Average Number of Video

Shaping UEs in the Sleep
State for Cell

3498
BSC6900 UMTS
Description
This counter measures the average number of video shaping UEs in the sleep state in a cell. The
measurement is triggered only when the video shaping function is enabled.
Measurement point
The RNC takes samples of the average number of video shaping UEs in the sleep state 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 number of video shaping UEs in the sleep
state by the number of sampling times. This counter is measured in the cell that video shaping
UEs camp on.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.UE.Sleep.
Mean.Cell
WRFD-170204
Radio Awared Video

Shaping
Total Duration During Which Video Shaping UEs Stay in the Burst State for Cell
Counters
Counter ID
Counter Name
Counter Description
73429226
VS.VideoShape.Burst.Duration
Total Duration During

Which Video Shaping UEs
Stay in the Burst State for
Cell
Description
This counter measures the total duration during which video shaping UEs stay in the burst state
in a cell. The measurement is triggered only when the video shaping function is enabled.
Issue 03 (2015-06-30)

3499
BSC6900 UMTS
Measurement point
The RNC records the time when a video shaping UE enters the burst state after a state transition
from CELL_FACH to CELL_DCH, or from CELL_PCH to CELL_DCH as T1. The RNC
records the time when the UE exits the burst state after a state transition from CELL_DCH to
CELL_FACH, or from CELL_DCH to CELL_PCH as T2. Delta T = T2 - T1, where delta T is
the duration during which the video shaping UE stays in the burst state. At the end of the
measurement period, the RNC obtains the accumulated duration of all video shaping UEs in the
burst state. This counter is measured in the best cell that video shaping UEs camp on.
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.Burst.Duration
WRFD-170204
Radio Awared Video

Shaping
Total Duration During Which Video Shaping UEs Stay in the Sleep State for Cell
Counters
Counter ID
Counter Name
Counter Description
73429227
VS.VideoShape.Sleep.Duration
Total Duration During

Which Video Shaping UEs
Stay in the Sleep State for
Cell
Description
This counter measures the total duration during which video shaping UEs stay in the sleep state
Measurement point
The RNC records the time when a video shaping UE enters the sleep state after a state transition
from CELL_DCH to CELL_FACH, or from CELL_DCH to CELL_PCH as T1. The RNC
records the time when the UE exits the sleep state after a state transition from CELL_FACH to
CELL_DCH, or from CELL_PCH to CELL_DCH as T2. Delta T = T2 - T1, where delta T is
the duration during which the video shaping UE stays in the sleep state. At the end of the
Issue 03 (2015-06-30)

3500
BSC6900 UMTS
measurement period, the RNC obtains the accumulated duration of all video shaping UEs in the
sleep state. This counter is measured in the cell that video shaping UEs camp on.
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.Sleep.Duration
WRFD-170204
Radio Awared Video

Shaping
Number of D2F State Transition Attempts Triggered upon Video Service Traffic
Shaping for Cell
Counters
Counter ID
Counter Name
Counter Description
73429290
VS.VideoShape.D2F.Att
Number of D2F State

Transition Attempts
Triggered upon Video
Service Traffic Shaping for
Cell
Description
This counter provides the number of state transition attempts from CELL_DCH to CELL_FACH
triggered upon video service traffic shaping in a cell. This counter is measured only when the
Radio Awared Video Shaping feature is enabled in the cell.
Measurement point
The measurement is triggered at point A in the following figure. When the RNC sends a RADIO
BEARER RECONFIGURATION message to the UE, this counter is measured in the best cell
before the state transition if the state transition is triggered upon the completion of burst
transmission of video services.
Issue 03 (2015-06-30)

3501
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VideoShape.D2F.Att
WRFD-170204
Radio Awared Video

Shaping

3502
BSC6900 UMTS
Number of Successful D2F State Transitions Triggered upon Video Service Traffic
Shaping for Cell
Counters
Counter ID
Counter Name
Counter Description
73429291
VS.VideoShape.D2F.Succ
Number of Successful D2F

upon Video Service Traffic
Shaping for Cell
Description
CELL_FACH triggered upon video service traffic shaping in a cell. This counter is measured
only when the Radio Awared Video Shaping feature is enabled in the cell.
Measurement point
RADIO BEARER RECONFIGURATION COMPLETE message from the UE, this counter is
measured in the best cell before the state transition if the state transition is triggered upon the
completion of burst transmission of video services.
Issue 03 (2015-06-30)

3503
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.D2F.Succ
WRFD-170204
Radio Awared Video

Shaping
Number of F2D State Transition Attempts Triggered upon Video Service Traffic
Shaping for Cell
Counters
Counter ID
Counter Name
Counter Description
73429292
VS.VideoShape.F2D.Att
Number of F2D State

Transition Attempts
Cell
Description
This counter provides the number of state transition attempts from CELL_FACH to CELL_DCH
Measurement point
BEARER RECONFIGURATION message to the UE, this counter is measured in the cell that
serves the UE if the state transition is triggered by the start of burst transmission of video services.
Issue 03 (2015-06-30)

3504
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VideoShape.F2D.Att
WRFD-170204
Radio Awared Video

Shaping

3505
BSC6900 UMTS
Number of Successful F2D State Transitions Triggered upon Video Service Traffic
Shaping for Cell
Counters
Counter ID
Counter Name
Counter Description
73429293
VS.VideoShape.F2D.Succ
Number of Successful F2D

Shaping for Cell
Description
CELL_DCH triggered upon video service traffic shaping in a cell. This counter is measured only
when the Radio Awared Video Shaping feature is enabled in the cell.
Measurement point
measured in the cell that serves the UE if the state transition is triggered by the start of burst
Issue 03 (2015-06-30)

3506
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.F2D.Succ
WRFD-170204
Radio Awared Video

Shaping
Number of D2P State Transition Attempts Triggered upon Video Service Traffic
Shaping for Cell
Counters
Counter ID
Counter Name
Counter Description
73429294
VS.VideoShape.D2P.Att
Number of D2P State

Transition Attempts
Cell
Description
This counter provides the number of state transition attempts from CELL_DCH to CELL_PCH
Measurement point
BEARER RECONFIGURATION message to the UE, this counter is measured in the best cell
before the state transition if the state transition is triggered by the completion of burst
Issue 03 (2015-06-30)

3507
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VideoShape.D2P.Att
WRFD-170204
Radio Awared Video

Shaping

3508
BSC6900 UMTS
Number of Successful D2P State Transitions Triggered upon Video Service Traffic
Shaping for Cell
Counters
Counter ID
Counter Name
Counter Description
73429295
VS.VideoShape.D2P.Succ
Number of Successful D2P

Shaping for Cell
Description
CELL_PCH triggered upon video service traffic shaping in a cell. This counter is measured only
Measurement point
measured in the best cell before the state transition if the state transition is triggered by the
completion of burst transmission of video services.
Issue 03 (2015-06-30)

3509
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.D2P.Succ
WRFD-170204
Radio Awared Video

Shaping
Number of P2D State Transition Attempts Triggered upon Video Service Traffic
Shaping for Cell
Counters
Counter ID
Counter Name
Counter Description
73429296
VS.VideoShape.P2D.Att
Number of P2D State

Transition Attempts
Cell
Description
This counter provides the number of state transition attempts from CELL_PCH to CELL_DCH
Measurement point
The measurement is triggered at point B in the following figure. When a UE in the CELL_PCH
state switches to the CELL_DCH state, this counter is measured in the cell where the UE sends
the CELL UPDATE message if the state transition is triggered by the start of burst transmission
of video services.
Issue 03 (2015-06-30)

3510
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VideoShape.P2D.Att
WRFD-170204
Radio Awared Video

Shaping

3511
BSC6900 UMTS
Number of Successful P2D State Transitions Triggered upon Video Service Traffic
Shaping for Cell
Counters
Counter ID
Counter Name
Counter Description
73429297
VS.VideoShape.P2D.Succ

Shaping for Cell
Description
This counter provides the number of successful state transitions from CELL_PCH to
CELL_DCH triggered upon video service traffic shaping in a cell. This counter is measured only
Measurement point
The measurement is triggered at point C in the following figure. After a UE in the CELL_PCH
state successfully switches to the CELL_DCH state, this counter is measured in the cell where
the UE sends the CELL UPDATE message if the state transition is triggered by the start of burst
Issue 03 (2015-06-30)

3512
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.P2D.Succ
WRFD-170204
Radio Awared Video

Shaping
Average Number of UEs Playing Online Video Services for cell

Counters
Counter ID
Counter Name
Counter Description
73445325
VS.Video.UE.Mean.Cell

Playing Online Video
Services for cell
Description
This counter provides the average number of UEs playing online video services in a cell. This
counter is measured only when the Video Service Traffic Detection Switch is set to on.
Measurement point
The system takes samples of the number of UEs that are playing online video services every 5
seconds in a measurement period. At the end of the measurement period, the system obtains the
value of this counter by dividing the accumulated number by the number of times sampled. This
counter is measured in the best cell for the UE that is playing online video services.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3513
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.Video.UE.Mean.Cell
WRFD-170204
Radio Awared Video

Shaping
Average Buffer Delay of UEs During Video Shaping and Scheduling for Cell
Counters
Counter ID
Counter Name
Counter Description
73445326
VS.VideoShape.Buffer.Tim
e
Average Buffer Delay of UEs

During Video Shaping and
Scheduling for Cell
Description
This counter provides the estimated average buffer delay of UEs that are playing video services
upon video service traffic shaping. During video playing, the average buffer delay of UEs can
be estimated based on the video play start time, video download rate, and video bit rate. This
counter is measured only when the service awareness function is enabled and the Video Service
Traffic Detection Switch is set to on.
Measurement point
The system takes samples of the estimated buffer delay of UEs that are playing video services
upon video service traffic shaping every 5 seconds in a measurement period. At the end of the
number by the number of times sampled.
Formula
None
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VideoShape.Buffer.Tim
e
WRFD-170204
Radio Awared Video

Shaping

3514
BSC6900 UMTS
Total Data Volume Transmitted by Video Shaping UEs in the Burst State for Cell
Counters
Counter ID
Counter Name
Counter Description
73445345
VS.VideoShape.Burst.Data
Total Data Volume

Transmitted by Video
Shaping UEs in the Burst
State for Cell
Description
This counter measures the total data volume transmitted by video shaping UEs in the burst state
Measurement point
The RNC records the data volume transmitted by a video shaping UE in the burst state after the
UE exits the burst state. At the end of the measurement period, the RNC obtains the accumulated
data volume transmitted by all video shaping UEs in the burst state. This counter is measured
in the best cell that video shaping UEs camp on.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.VideoShape.Burst.Data
WRFD-170204
Radio Awared Video

Shaping
1.12.55 WLAN Measurement <per Cell>(WLAN.Cell)

Overview
WLAN Measurement per cell
Issue 03 (2015-06-30)

3515
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73426126
VS.WlanDistribute
.attempt
Number of Wi-Fi
Access Attempts for
Cell
BSC6900
V900R015C00
73426127
VS.WlanDistribute
.Fail
Number of Wi-Fi
Access Failures for
Cell
BSC6900
V900R015C00
None
Number of Wi-Fi Access Attempts for Cell

Counters
Counter ID
Counter Name
Counter Description
73426126
VS.WlanDistribute.attempt
Number of Wi-Fi Access

Attempts for Cell
Description
This counter provides the number of Wi-Fi access attempts in the best cell where the UE in
question camps.
Measurement point
As shown by point A in figure 1, the RNC sends an ApDetect_Response message to the UE,
and then this counter is increased by one in the best cell where the UE camps.
Issue 03 (2015-06-30)

3516
BSC6900 UMTS
Figure 1-1469 WIFI detect in cell
As shown by point A in figure 2, the RNC sends the UE a WiFi_Register_Response message

where "SSID List" is not set to NULL and "AccessFlag" is set to 1. Then, this counter is increased
by one in the best cell where the UE camps.
Figure 1-1470 WIFI regist in cell
Formula
None
Issue 03 (2015-06-30)

3517
BSC6900 UMTS
Unit
None
Related Features
None
Number of Wi-Fi Access Failures for Cell

Counters
Counter ID
Counter Name
Counter Description
73426127
VS.WlanDistribute.Fail
Number of Wi-Fi Access

Failures for Cell
Description
This counter provides the number of Wi-Fi access failures in the best cell where the UE in
question camps.
Measurement point
As shown by point B in the following figure, the RNC receives from the UE a Wi-Fi access
failure report, and then this counter is increased by one in the best cell where the UE camps.
This cell must be under the SRNC to which the UE belongs.
Figure 1-1471 WIFI access fail in cell
Issue 03 (2015-06-30)

3518
BSC6900 UMTS
Formula
None
Unit
None
Related Features
None
1.13 Measurement of UMTS Cell-to-GSM Cell Handover

Performance(UCELL_GCELL)
Overview
The measurement object type IRATHO.GCELL is used to measure the handovers between interRAT adjacent cells.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IRATHO.Gcell
UMTS Cell-to-GSM Cell Handover

Measurement
1.13.1 UMTS Cell-to-GSM Cell Handover Measurement

(IRATHO.Gcell)
Overview
This function subset is used to measure inter-RAT handovers between neighboring cells. For
details about inter-RAT handover procedure, refer to the following sections in "RNC
Performance Measurement (RNC)" :
"CS Domain Inter-RAT Handover Measurement";
"PS Domain Inter-RAT Handover Measurement".
The two cells involved in the inter-RAT handover are called source cell and target cell. They
belong to different communication systems. For the source cell, the RNC measures each of the
following items in the relationship of "source cell - target cell".
Suppose the UE camps on CELL1 before an inter-RAT handover. After inter-RAT handover,
the UE camps on CELL2. Then CELL1 is the source cell and CELL2 is the target cell. This
indicates one inter-RAT handover between CELL1 and CELL2.
The RNC takes statistics for source cells that belong to the WCDMA system.
Issue 03 (2015-06-30)

3519
BSC6900 UMTS
Note:
1. Using scenes of this kind of items are usually described as follows: evaluate neighboring cell
priority rationality, provide evidence for deleting redundant neighboring cell, which is generally
used for network optimization.
2. The measurement of this kind of item needs to be started through the U2000. The measurement
is not started by default.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67183495
VS.IRATHO.AttO
utCS.GCell
Number of CS InterRAT Outgoing

Handover Attempts
Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67183496
VS.IRATHO.Succ
OutCS.GCell
Number of
Successful CS InterRAT Outgoing
Handovers Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67189907
VS.IRATHO.FailO
utCS.UEFail.GCell
Number of Failed CS
Inter-RAT
HandoversBetween
Neighboring Cells
Due to UE Fault
Earlier than
BSC6900
V900R011
67183497
VS.IRATHO.AttO
utPSUTRAN.GCell
Number of PS InterRAT Outgoing

Handover Attempts
Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67183498
VS.IRATHO.Succ
OutPSUTRAN.GC
ell
Number of
Successful PS InterRAT Outgoing
Handovers Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67189908
VS.IRATHO.FaiO
utPSUTRAN.UEFa
il.GCell
Number of Failed PS
Inter-RAT
Handovers Between
Neighboring Cells
Due to UE Fault
Earlier than
BSC6900
V900R011

3520
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73394034
VS.IRATHO.AttRe
locPrepOutCS.GCe
ll
Number of CS
Outgoing Inter-RAT
Handover
Preparation
Attempts
BSC6900
V900R012
73394035
VS.IRATHO.AttRe
locPrepOutCS.DR.
GCell
Number of CS
Outgoing Inter-RAT
Handover
Preparation
Attempts (Directed
retry)
BSC6900
V900R012
73394036
VS.IRATHO.AttRe
locPrepOutCS.RF.
GCell
Number of Failed CS
Outgoing Inter-RAT
Handover
Preparations
(Relocation desirable
for radio reasons)
BSC6900
V900R012
73394037
VS.IRATHO.Succ
RelocPrepOutCS.G
Cell
Number of
Successful CS
Outgoing Inter-RAT
Handover
Preparations
BSC6900
V900R012
73394038
VS.IRATHO.FailR
elocPrepOutCS.TA
lExp.GCell
Number of Failed CS
Outgoing Inter-RAT
Handover
Preparations
(TRELOCalloc
expiry)
BSC6900
V900R012
73394039
VS.IRATHO.FailR
elocPrepOutCS.Tgt
Fail.GCell
Number of Failed CS
Outgoing Inter-RAT
Handover
Preparations
(Relocation Failure
in Target CN/RNC or
Target System)
BSC6900
V900R012
None
Issue 03 (2015-06-30)

3521
BSC6900 UMTS
Number of CS Inter-RAT Outgoing Handover Attempts Between Neighboring

Cells
Counters
Counter ID
Counter Name
Counter Description
67183495
VS.IRATHO.AttOutCS.GC
ell
Outgoing Handover
Attempts Between
Neighboring Cells
Description
This counter provides the number of attempts for CS outgoing inter-RAT handovers according
to the neighbor relationships.This counter complies with section "8.3.4 Inter-RAT handover
from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC sends a
HANDOVER FROM UTRAN COMMAND message to the UE in the CS domain inter-RAT
handover procedure, the RNC measures this item for each pair of source and target cells. Here,
the best cell that the UE camps on before the inter-RAT handover is the source cell, and the cell
that the UE wants to hand over to is the target cell.
Figure 1-1472 CS inter-RAT outgoing handover procedure
Issue 03 (2015-06-30)

3522
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttOutCS.GC
ell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Successful CS Inter-RAT Outgoing Handovers Between Neighboring

Cells
Counters
Counter ID
Counter Name
Counter Description
67183496
VS.IRATHO.SuccOutCS.G
Cell
Inter-RAT Outgoing
Handovers Between
Neighboring Cells
Description
This measurement item provides the number of successful CS inter-RAT outgoing handovers
between neighboring cells.This counter complies with section "8.3.4 Inter-RAT handover from
UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point D, as shown in the figure. After the RNC sends a
HANDOVER FROM UTRAN COMMAND message during the CS domain inter-RAT
handover, it receives from the CS domain an IU RELEASE COMMAND message with the cause
of "Successful Relocation", "Normal Release" or "Network Optimization". At this time, the RNC
measures this item for each pair of source and target cells. Here, the best cell that the UE camps
on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over
to is the target cell.
Issue 03 (2015-06-30)

3523
BSC6900 UMTS
Figure 1-1473 CS inter-RAT outgoing handover procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccOutCS.G
Cell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

3524
BSC6900 UMTS
Number of Failed CS Inter-RAT Outgoing Handovers Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67189907
VS.IRATHO.FailOutCS.UE
Fail.GCell
Number of Failed CS InterRAT HandoversBetween

Neighboring Cells Due to UE
Fault
Description
This measurement item provides the number of unsuccessful CS inter-RAT outgoing handovers
between neighboring cells.This counter complies with section "8.3.4 Inter-RAT handover from
UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
HANDOVER FROM UTRAN FAILURE message from an UE, the RNC measure this item for
each pair of source and target cells. Here, the best cell that the UE camps on before the interRAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell.
Figure 1-1474 CS inter-RAT outgoing handover procedure (failed operation)
Formula
None
Issue 03 (2015-06-30)

3525
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutCS.UE
Fail.GCell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of PS Inter-RAT Outgoing Handover Attempts Between Neighboring

Cells
Counters
Counter ID
Counter Name
Counter Description
67183497
AN.GCell
Outgoing Handover
Attempts Between
Neighboring Cells
Description
This counter provides the number of attempts for PS outgoing inter-RAT handovers initiated by
the RNC according to the neighbor relationships.This counter complies with section "8.3.4 InterRAT cell change order from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point B, as shown in the figure. When the RNC sends the UE
a CELL CHANGE ORDER FROM UTRAN message during the PS inter-RAT handover, it
measures this item for each pair of source and target cells. Here, the best cell that the UE camps
on before the inter-RAT handover is the source cell, and the cell that the UE wants to hand over
to is the target cell.
Issue 03 (2015-06-30)

3526
BSC6900 UMTS
Figure 1-1475 RNC-originated PS inter-RAT outgoing handover procedure (successful

operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
AN.GCell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Issue 03 (2015-06-30)

3527
BSC6900 UMTS
Number of Successful PS Inter-RAT Outgoing Handovers Between Neighboring

Cells
Counters
Counter ID
Counter Name
Counter Description
67183498
RAN.GCell
Inter-RAT Outgoing
Handovers Between
Neighboring Cells
Description
This measurement item provides the number of successful PS inter-RAT outgoing handovers
between neighboring cells.This counter complies with section "8.3.4 Inter-RAT cell change
order from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point C, as shown in the figure. After the RNC sends a CELL
CHANGE ORDER FROM UTRAN message during the PS inter-RAT handover procedure, it
receives from the CN an IU RELEASE COMMAND message with the cause of "Successful
Relocation", "Normal Release" or "Network Optimization". At this time, the RNC measures this
item for each pair of source and target cells. Here, the best cell that the UE camps on before the
inter-RAT handover is the source cell, and the cell that the UE wants to hand over to is the target
cell.
Figure 1-1476 RNC-originated PS inter-RAT outgoing handover procedure (successful
operation)
Issue 03 (2015-06-30)

3528
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
RAN.GCell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Failed PS Inter-RAT Outgoing Handovers Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67189908
VS.IRATHO.FaiOutPSUTR
AN.UEFail.GCell
Number of Failed PS InterRAT Handovers Between

Neighboring Cells Due to UE
Fault
Description
This measurement item provides the number of unsuccessful PS inter-RAT outgoing handovers
between neighboring cells.This counter complies with section "8.3.4 Inter-RAT cell change
order from UTRAN" in 3GPP TS 25.331 (v10.13.0).
Measurement point
The measurement is triggered at point A, as shown in the figure. When the RNC sends a CELL
CHANGE ORDER FROM UTRAN message to an UE, it receives a CELL CHANGE ORDER
FROM UTRAN FAILURE message from the UE. At this time, the RNC measures this item for
each pair of source and target cells. Here, the best cell that the UE camps on before the interRAT handover is the source cell, and the cell that the UE wants to hand over to is the target cell.
Issue 03 (2015-06-30)

3529
BSC6900 UMTS
Figure 1-1477 PS inter-RAT outgoing handover procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FaiOutPSUTR
AN.UEFail.GCell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of CS Outgoing Inter-RAT Handover Preparation Attempts Between

Neighboring Cells
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73394034
OutCS.GCell
Inter-RAT Handover

3530
BSC6900 UMTS
Description
This counter provides the number of CS outgoing inter-RAT handover preparation attempts in
the source cell and the target cell.This counter complies with section "8.6 Relocation
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the CN
a RELOCATION REQUIRED message during the CS outgoing inter-RAT handover, the RNC
measures these items for each pair of source and target cells according to different causes. Here,
Formula
None
Unit
None
Issue 03 (2015-06-30)

3531
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OutCS.GCell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of CS Outgoing Inter-RAT Handover Preparation Attempts According to

Different Causes Between Neighboring Cells
Counters
Counter ID
Counter Name
Counter Description
73394035
OutCS.DR.GCell
Inter-RAT Handover
(Directed retry)
73394036
OutCS.RF.GCell
Number of Failed CS
Outgoing Inter-RAT
(Relocation desirable for
radio reasons)
Description
These counters provide the number of CS outgoing inter-RAT handover preparation attempts
in the source cell and the target cell according to the cause values.The preceding counters comply
with section "8.6 Relocation Preparation" in 3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure. When the RNC sends the CN
a RELOCATION REQUIRED message during the CS outgoing inter-RAT handover, the RNC
measures these items for each pair of source and target cells according to different causes. Here,
Issue 03 (2015-06-30)

3532
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OutCS.DR.GCell
WRFD-02040002
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
OutCS.RF.GCell
Issue 03 (2015-06-30)
WRFD-020303


on Coverage
3533
BSC6900 UMTS
Number of Successful CS Outgoing Inter-RAT Handover Preparations Between

Neighboring Cells
Counters
Counter ID
Counter Name
Counter Description
73394037
pOutCS.GCell
Outgoing Inter-RAT
Description
This counter provides the number of Successful CS outgoing inter-RAT handover
preparations.This counter complies with section "8.6 Relocation Preparation" in 3GPP TS
25.413 (v10.10.0).
Measurement point
the CN a RELOCATION COMMAND message during the CS outgoing inter-RAT handover.
In this case, the RNC measures this item for each pair of source and target cells. Here, the best
cell that the UE camps on before the inter-RAT handover is the source cell, and the cell that the
UE wants to hand over to is the target cell.
Issue 03 (2015-06-30)

3534
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
pOutCS.GCell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
Number of Failed CS Outgoing Inter-RAT Handover Preparations According to

Different Causes Between Neighboring Cells
Counters
Counter ID
Counter Name
Counter Description
73394038
OutCS.TAlExp.GCell
Number of Failed CS
Outgoing Inter-RAT
73394039
OutCS.TgtFail.GCell
Number of Failed CS
Outgoing Inter-RAT
Description
This counter provides the number of failed CS outgoing inter-RAT handover preparations
according to different causes.The preceding counters comply with section "8.6 Relocation
Measurement point
the CN a RELOCATION PREPARATION FAILURE message after it sends the CN a
Issue 03 (2015-06-30)

3535
BSC6900 UMTS
RELOCATION REQUIRED message during the CS outgoing inter-RAT handover. In this case,
the RNC measures this item for each pair of source and target cells according to different causes.
Here, the best cell that the UE camps on before the inter-RAT handover is the source cell, and
the cell that the UE wants to hand over to is the target cell.
Figure 1-1481 SRNC relocation preparation procedure (failed operation)
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OutCS.TAlExp.GCell
WRFD-020303

on Coverage
WRFD-020305
WRFD-020306

on Service
on Load
OutCS.TgtFail.GCell
WRFD-020303
WRFD-020305
WRFD-020306

on Coverage
on Service
on Load
Issue 03 (2015-06-30)

3536
BSC6900 UMTS
1.14 Measurement of UMTS Cell-to-LTE Cell Handover

Performance(UCELL_LCELL)
Overview
The measurement object type IRATHO.LCELL is used to measure the handovers between interRAT adjacent cells.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IRATHO.Lcell
UMTS Cell-to-LTE Cell Handover

Measurement
1.14.1 UMTS Cell-to-LTE Cell Handover Measurement

(IRATHO.Lcell)
Overview
This function subset is used to measure inter-RAT handovers between neighboring cells. For
details about inter-RAT handover procedure, refer to the following sections in "RNC
Performance Measurement (RNC)" :
"CS Domain Inter-RAT Handover Measurement";
"PS Domain Inter-RAT Handover Measurement".
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430191
VS.IRATHO.AttRe
locPrepOutPS.LCE
LL
Number of Attempts
for U2L PS
Handovers per LTE
Cell
BSC6900
V900R017C10
73430207
VS.IRATHO.Succ
RelocPrepOutPS.L
CELL
Number of
Successful
PS Handovers per
LTE Cell
BSC6900
V900R017C10

3537
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73430208
VS.IRATHO.FailR
elocPrepOutPS.No
ResAvail.LCELL
Number of Failed
PS Handovers per
LTE Cell (No
Resource Available)
BSC6900
V900R017C10
73430209
VS.IRATHO.FailR
elocPrepOutPS.Tgt
Fail.LCELL
Number of Failed
PS Handovers per
LTE Cell
(Relocation Failure
in Target CN/RNC or
Target System)
BSC6900
V900R017C10
73430210
VS.IRATHO.FailR
elocPrepOutPS.Rel
oUnSupp.LCELL
Number of Failed
PS Handovers per
LTE Cell
(Relocation not
supported in Target
RNC or Target
system)
BSC6900
V900R017C10
73430211
VS.IRATHO.FailR
elocPrepOutPS.Tgt
HighLoad.LCELL
Number of Failed
PS Handovers per
LTE Cell (Traffic
Load In The Target
Cell Higher Than In
The Source Cell)
BSC6900
V900R017C10
73430212
VS.IRATHO.FailR
elocPrepOutPS.Un
KnowRNC.LCELL
Number of Failed
PS Handovers per
LTE Cell (Unknown
Target RNC)
BSC6900
V900R017C10
73430213
VS.IRATHO.FailR
elocPrepOutPS.TA
lExp.LCELL
Number of Failed
PS Handovers per
LTE Cell
(TRELOCalloc
expiry
BSC6900
V900R017C10
73430214
VS.IRATHO.AttO
utPS.LCELL
Number of U2L PS
Handover Attempts
per LTE Cell
BSC6900
V900R017C10

3538
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73430215
VS.IRATHO.Succ
OutPS.LCELL
Number of
Successful U2L PS
Handover per LTE
Cell
BSC6900
V900R017C10
73430216
VS.IRATHO.FailO
utPS.CfgUnSupp.L
CELL
Number of Failed
U2L PS Handovers
per LTE Cell
(Configuration
Unsupported)
BSC6900
V900R017C10
73430217
VS.IRATHO.FailO
utPS.PhyChFail.L
CELL
Number of Failed
U2L PS Handovers
per LTE Cell
(Physical Channel
Failure)
BSC6900
V900R017C10
73430218
VS.IRATHO.FailO
utPS.Abort.LCEL
L
Number of
Abnormally
Terminated U2L PS
Handovers per LTE
Cell
BSC6900
V900R017C10
73430219
VS.IRATHO.FailO
utPS.NoReply.LCE
LL
Number of Failed
U2L PS Handovers
due to Iu Release
Command Timeout
per LTE Cell
BSC6900
V900R017C10
None
Number of Attempts for U2L PS Handovers per LTE Cell

Counters
Counter ID
Counter Name
Counter Description
73430191
OutPS.LCELL
Number of Attempts for U2L

PS Handovers per LTE Cell
Description
different causes in the best cell.
Issue 03 (2015-06-30)

3539
BSC6900 UMTS
section 8.6 "Relocation Preparation" in this TS.
Measurement point
The measurement is triggered at point A in the following figure. During a U2L PS handover,
when the RNC sends a RELOCATION REQUIRED message to the CN, this counter is measured
in the best UMTS cell based on the target LTE cell.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OutPS.LCELL
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)

3540
BSC6900 UMTS
Number of Successful Preparations for U2L PS Handovers per LTE Cell

Counters
Counter ID
Counter Name
Counter Description
73430207
pOutPS.LCELL
Handovers per LTE Cell
Description
by different causes in the best cell.
section 8.6 "Relocation Preparation" in this TS.
Measurement point
The measurement is triggered at point B in the following figure. During a U2L PS handover,
when the RNC receives a RELOCATION COMMAND message from the CN, this counter is
measured in the best UMTS cell based on the target LTE cell.
Formula
None
Issue 03 (2015-06-30)

3541
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
pOutPS.LCELL
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Number of Failed Preparations for U2L PS Handovers per LTE Cell

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73430208
OutPS.NoResAvail.LCELL
Number of Failed
Handovers per LTE Cell (No
Resource Available)
73430209
OutPS.TgtFail.LCELL
Number of Failed
73430210
OutPS.ReloUnSupp.LCELL
Number of Failed
system)
73430211
OutPS.TgtHighLoad.LCEL
L
Number of Failed
(Traffic Load In The Target
Cell Higher Than In The
Source Cell)

3542
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73430212
OutPS.UnKnowRNC.LCEL
L
Number of Failed
(Unknown Target RNC)
73430213
OutPS.TAlExp.LCELL
Number of Failed
(TRELOCalloc expiry
Description
These counters provide the number of failed preparations for U2L PS handovers in the best cell
per the target LTE cell. The preparation failures are caused by the CN or the LTE side. For details
about the causes, see section 9.2.1.4 in 3GPP TS 25.413. If the values of these counters are large,
the causes of preparation failures need to be checked on the CN or LTE side.
section 8.7 "Relocation Resource Allocation" in this TS.
Measurement point
when the RNC receives a RELOCATION PREPARATION FAILURE message from the CN
after sending a RELOCATION REQUIRED message to the CN, this counter is measured in the
best cell under the SRNC per the target LTE cell.
Figure 1-1484 PS UMTS to LTE outgoing handover Prepareation Procedure(failed operation)
Formula
None
Issue 03 (2015-06-30)

3543
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OutPS.NoResAvail.LCELL
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
OutPS.TgtFail.LCELL
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
OutPS.ReloUnSupp.LCELL
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
OutPS.TgtHighLoad.LCEL
L
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
OutPS.UnKnowRNC.LCEL
L
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)

3544
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
OutPS.TAlExp.LCELL
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Number of U2L PS Handover Attempts per LTE Cell

Counters
Counter ID
Counter Name
Counter Description
73430214
VS.IRATHO.AttOutPS.LC
ELL
Number of U2L PS
Handover Attempts per LTE
Cell
Description
This counter provides the number of U2L PS handover attempts triggered by different causes
in the best UMTS cell.
This counter complies with 3GPP TS 25.331 (V10.10.0). For details, see section 8.3.7 "InterRAT handover from UTRAN" in this TS.
Measurement point
The measurement is triggered at point C in the following figure. During a U2L PS handover,
when the RNC sends a HANDOVER FROM UTRAN COMMAND message to the UE, this
counter is measured in the best UMTS cell per the target LTE cell.
Issue 03 (2015-06-30)

3545
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.AttOutPS.LC
ELL
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)

3546
BSC6900 UMTS
Number of Successful U2L PS Handover per LTE Cell

Counters
Counter ID
Counter Name
Counter Description
73430215
VS.IRATHO.SuccOutPS.L
CELL

PS Handover per LTE Cell
Description
This counter provides the number of successful U2L PS handovers triggered by different causes
in the best cell. This counter is measured per the target LTE cell.
Measurement point
The measurement is triggered at point D in the following figure. During a U2L PS handover,
when the RNC receives an IU RELEASE COMMAND message with the cause value
measured in the best UMTS cell per the target LTE cell.
Formula
None
Issue 03 (2015-06-30)

3547
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.SuccOutPS.L
CELL
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Number of Failed U2L PS Handovers per LTE Cell

Counters
Counter ID
Counter Name
Counter Description
73430216
VS.IRATHO.FailOutPS.Cfg
UnSupp.LCELL
Number of Failed U2L PS

(Configuration
Unsupported)
73430217
VS.IRATHO.FailOutPS.Phy
ChFail.LCELL

Description
These counters provide the number of U2L PS handover failures in the best UMTS cell per the
target LTE cell.These counters indicate the number of times UEs fail to process the HANDOVER
FROM UTRAN COMMAND message. If the values of these counters are large, UEs either do
not support U2L PS handovers or the signal strength of the target LTE cell is weak.
Measurement point
when the RNC receives a HANDOVER FROM UTRAN FAILURE message from the UE, this
counter is measured in the best UMTS cell per the target LTE cell.
Issue 03 (2015-06-30)

3548
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutPS.Cfg
UnSupp.LCELL
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
VS.IRATHO.FailOutPS.Phy
ChFail.LCELL
WRFD-140218
WRFD-150220
WRFD-150217
from UMTS to LTE
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)

3549
BSC6900 UMTS
Number of Abnormally Terminated U2L PS Handovers per LTE Cell

Counters
Counter ID
Counter Name
Counter Description
73430218
ort.LCELL
Terminated U2L PS
Description
This counter provides the number of U2L PS handover failures caused by abnormally terminated
handover procedures in the best UMTS cell per the target LTE cell. This counter indicates the
number of times the CN and LTE side abnormally terminate the U2L PS handover procedure.
If the value of this counter is large, the causes of the U2L PS handover failures need to be checked
on the CN or LTE side.
section 8.5 "Iu Release" in this TS.
Measurement point
The measurement is triggered at point D in the following figure. During a U2L PS handover,
when the RNC receives an IU RELEASE COMMAND message with a cause value other than
measured in the best UMTS cell per the target LTE cell.
Issue 03 (2015-06-30)

3550
BSC6900 UMTS
Figure 1-1488 PS domain inter-RAT outgoing handover procedure
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ort.LCELL
WRFD-140218
from UMTS to LTE
WRFD-150220
WRFD-150217
Coverage Based PS
LTE
from UMTS to LTE
Issue 03 (2015-06-30)

3551
BSC6900 UMTS
Number of Failed U2L PS Handovers due to Iu Release Command Timeout per LTE
Cell
Counters
Counter ID
Counter Name
Counter Description
73430219
VS.IRATHO.FailOutPS.No
Reply.LCELL

Handovers due to Iu Release
Command Timeout per LTE
Cell
Description
This counter provides the number of U2L PS handover failures caused by no IU RELEASE
COMMAND message in the best UMTS cell per the target LTE cell. If the value of this counter
is large, the causes of no IU RELEASE COMMAND message need to be check on the LTE
side.
section 8.5 "Iu Release" in this TS.
Measurement point
when the RNC does not receive an IU RELEASE COMMAND message from the CN within a
specified period of time after sending a HANDOVER FROM UTRAN COMMAND message
to the UE, this counter is measured in the best UMTS cell per the target LTE cell.
Figure 1-1489 Timeout Waiting for Iu Release Command in CS or the Enhanced PS Outgoing
Inter-RAT Handover
Issue 03 (2015-06-30)

3552
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IRATHO.FailOutPS.No
Reply.LCELL
WRFD-140218
from UMTS to LTE
WRFD-150220
Coverage Based PS
LTE
WRFD-150217

from UMTS to LTE
1.15 Measurement of UMTS Cell-to-UMTS Cell Handover

Performance(UCELL_NCELL)
Overview
The measurement object type of Neighboring Cell Measurement (CELL.NCELL) is used to
measure the handovers between neighboring cells.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
CELL.Ncell
UMTS Cell-to-UMTS Cell Handover

Measurement
1.15.1 UMTS Cell-to-UMTS Cell Handover Measurement

(CELL.Ncell)
Overview
This function subset measures handover procedures between neighboring cells. These
procedures include soft handover and hard handover procedures. For details about these
Issue 03 (2015-06-30)

3553
BSC6900 UMTS
procedures, see function subsets SHO.RNC and HHO.RNC in section "Measurement of RNC
Performance (RNC)".
The two cells involved in neighboring cell measurement are called source cell and target cell.
For the source cell, the RNC measures each of the following items in the relationship of "source
cell - target cell". If there are several target cells, the RNC measures the items in "source cell target cell n".
For example, the UE is in CELL1 before an inter-RAT handover, then moves to CELL2 and
CELL3 after soft handover. In this scenario, CELL1 is the source cell, CELL2 and CELL3 are
the target cells. You can measure the soft handovers as follows: one soft handover for "CELL1CELL2" and another for "CELL1-CELL3".
Neighboring cell measurement is used to measure only the items with the source cell under a
Source Radio Network Controller (SRNC) and the target cell under an SRNC or a Target Radio
Network Controller (TRNC).
Note:
1. Using scenes of this kind of items are usually described as follows: evaluate neighboring cell
priority rationality, provide evidence for deleting redundant neighboring cell, which is generally
used for network optimization.
2. The measurement of this kind of item needs to be started through the U2000. The measurement
is not started by default.
3. In BSC6900 versions, there is no restriction on the number of measurement objects.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67189909
VS.SHO.SuccASU.
NCell
Number of
Successful Soft
Handovers Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67189910
VS.SHO.AttASU.N
Cell
Number of Soft
Handover Attempts
Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67189911
VS.SHO.FailASU.
NoReply.NCell
Number of Failed
Soft Handovers
Between
Neighboring Cells
Due to Waiting
Active Set Update
Response Timeout
Earlier than
BSC6900
V900R011
67183489
VS.HHO.AttOut.N
Cell
Number of Hard
Handovers Attempts
Between
Neighboring Cells
Earlier than
BSC6900
V900R011

3554
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67183490
VS.HHO.SuccOut.
NCell
Number of
Successful Hard
Handovers Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67189912
VS.HHO.FailOut.N
oReply.NCell
Number of Failed
Hard Handover
Between
Neighboring Cells
Due to Timeout
Earlier than
BSC6900
V900R011
67183491
VS.SHO.AddRLAt
t.NCell
Number of RL
Addition Attempts in
Soft Handover
Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67183492
VS.SHO.AddRLSu
cc.NCell
Number of
Successful RL
Additions in Soft
Handover Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67183493
VS.SHO.DelRLAtt.
NCell
Number of RL
Deletion Attempts in
Soft Handover
Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67183494
VS.SHO.DelRLSuc
c.NCell
Number of
Successful RL
Deletions in Soft
Handover Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67190708
VS.HSDPA.HHO.
NoChR.Att.NCell
Number of
HSDSCH-toHSDSCH hard
Handover Requests
Without Channel
Change Between
Neighboring Cells
Earlier than
BSC6900
V900R011

3555
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190709
VS.HSDPA.HHO.
NoChR.Succ.NCell
Number of
Successful
HSDSCH-toHSDSCH hard
Handovers Without
Channel Change
Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67190710
VS.HSDPA.ServCe
llChg.Att.NCell
Number of HSDPA
Serving Cell Change
Attempts Between
Neighboring Cells
Earlier than
BSC6900
V900R011
67190711
VS.HSDPA.ServCe
llChg.Succ.NCell
Number of
Successful HSDPA
Serving Cell
Changes Between
Neighboring Cells
Earlier than
BSC6900
V900R011
73393988
VS.HHO.AttOutIn
traNodeB.CS.NCell
Number of CS
Outgoing IntraNodeB Inter-Cell
Hard Handover
Attempts
BSC6900
V900R012
73393989
VS.HHO.SuccOutI
ntraNodeB.CS.NCe
ll
Number of
Successful CS
Hard Handovers
BSC6900
V900R012
73393990
VS.HHO.FailOutIn
traNodeB.NoReply.
CS.NCell
Number of Failed CS
Hard Handovers (UE
No Response)
BSC6900
V900R012
73393991
VS.HHO.FailOutIn
traNodeB.PhyChF
ail.CS.NCell
Number of Failed CS
Hard Handovers
(Physical Channel
Failure)
BSC6900
V900R012
73393992
VS.HHO.AttOutIn
traNodeB.PS.NCell
Number of PS
Hard Handover
Attempts
BSC6900
V900R012

3556
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73393993
VS.HHO.SuccOutI
ntraNodeB.PS.NCe
ll
Number of
Successful PS
Hard Handovers
BSC6900
V900R012
73393994
VS.HHO.FailOutIn
traNodeB.NoReply.
PS.NCell
Number of Failed PS
Hard Handovers (UE
No Response)
BSC6900
V900R012
73393995
VS.HHO.FailOutIn
traNodeB.PhyChF
ail.PS.NCell
Number of Failed PS
Hard Handovers
(Physical Channel
Failure)
BSC6900
V900R012
73393996
VS.HHO.AttOutIn
terNodeBIntraRN
C.CS.NCell
Number of CS
Outgoing Intra-RNC
Inter-NodeB InterCell Hard Handover
Attempts
BSC6900
V900R012
73393997
VS.HHO.SuccOutI
nterNodeBIntraRN
C.CS.NCell
Number of
Successful CS
Outgoing Intra-RNC
Inter-NodeB InterCell Hard Handovers
BSC6900
V900R012
73393998
VS.HHO.FailOutIn
terNodeBIntraRN
C.NoReply.CS.NCe
ll
Number of Failed CS
Outgoing Intra-RNC
(UE No Response)
BSC6900
V900R012
73393999
VS.HHO.FailOutIn
terNodeBIntraRN
C.PhyChFail.CS.N
Cell
Number of Failed CS
Outgoing Intra-RNC
(Physical Channel
Failure)
BSC6900
V900R012
73394000
VS.HHO.AttOutIn
terNodeBIntraRN
C.PS.NCell
Number of PS
Outgoing Intra-RNC
Inter-NodeB InterCell Hard Handover
Attempts
BSC6900
V900R012

3557
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394001
VS.HHO.SuccOutI
nterNodeBIntraRN
C.PS.NCell
Number of
Successful PS
Outgoing Intra-RNC
BSC6900
V900R012
73394002
VS.HHO.FailOutIn
terNodeBIntraRN
C.NoReply.PS.NCe
ll
Number of Failed PS
Outgoing Intra-RNC
(UE No Response)
BSC6900
V900R012
73394003
VS.HHO.FailOutIn
terNodeBIntraRN
C.PhyChFail.PS.N
Cell
Number of Failed PS
Outgoing Intra-RNC
(Physical Channel
Failure)
BSC6900
V900R012
73394004
VS.HHO.AttOutIn
terRNCIur.CS.NC
ell
Number of CS
Outgoing Inter-RNC
Inter-Cell Hard
Handover Attempts
BSC6900
V900R012
73394005
VS.HHO.SuccOutI
nterRNCIur.CS.N
Cell
Number of
Successful CS
Outgoing Inter-RNC
Inter-Cell Hard
Handovers
BSC6900
V900R012
73394006
VS.HHO.FailOutIn
terRNCIur.CfgUns
up.CS.NCell
Number of Failed CS
Outgoing Inter-RNC
Inter-Cell Hard
Handovers
(Configuration
Unsupported)
BSC6900
V900R012
73394007
VS.HHO.FailOutIn
terRNCIur.PhyCh
Fail.CS.NCell
Number of Failed CS
Outgoing Inter-RNC
Inter-Cell Hard
Handovers (Physical
Channel Failure)
BSC6900
V900R012
73394008
VS.HHO.AttOutIn
terRNCIur.PS.NCe
ll
Number of PS
Outgoing Inter-RNC
Inter-Cell Hard
Handover Attempts
BSC6900
V900R012

3558
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394009
VS.HHO.SuccOutI
nterRNCIur.PS.N
Cell
Number of
Successful PS
Outgoing Inter-RNC
Inter-Cell Hard
Handovers
BSC6900
V900R012
73394010
VS.HHO.FailOutIn
terRNCIur.CfgUns
up.PS.NCell
Number of Failed PS
Outgoing Inter-RNC
Inter-Cell Hard
Handovers
(Configuration
Unsupported)
BSC6900
V900R012
73394011
VS.HHO.FailOutIn
terRNCIur.PhyCh
Fail.PS.NCell
Number of Failed PS
Outgoing Inter-RNC
Inter-Cell Hard
Handovers (Physical
Channel Failure)
BSC6900
V900R012
73394026
VS.HHO.AttOutIn
terRNCCN.CS.NC
ell
Number of Outgoing
UE-Involved SRNS
Relocation
Executions
Triggered by CS
HHO
BSC6900
V900R012
73394027
VS.HHO.SuccOutI
nterRNCCN.CS.N
Cell
Number of
Successful Outgoing
UE-Involved SRNS
Relocations
Triggered by CS
HHO
BSC6900
V900R012
73394028
VS.HHO.FailReloc
PrepOutInterRNC
CN.TExp.CS.NCell
Number of Failed
Outgoing UEInvolved SRNS
Relocation
Preparations
Triggered by CS
HHO
(TRELOCalloc
Expiry)
BSC6900
V900R012

3559
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73394029
VS.HHO.FailReloc
PrepOutInterRNC
CN.TgtF.CS.NCell
Number of Failed
Relocation
Preparations
Triggered by CS
HHO (Relocation
RNC or Target
System)
BSC6900
V900R012
73394030
VS.HHO.AttOutIn
terRNCCN.PS.NCe
ll
Number of Outgoing
UE-Involved SRNS
Relocation
Executions
Triggered by PS
HHO
BSC6900
V900R012
73394031
VS.HHO.SuccOutI
nterRNCCN.PS.N
Cell
Number of
Successful Outgoing
UE-Involved SRNS
Relocation
Executions
Triggered by PS
HHO
BSC6900
V900R012
73394032
VS.HHO.FailReloc
PrepOutInterRNC
CN.TExp.PS.NCell
Number of Failed
Relocation
Preparations
Triggered by PS
HHO
(TRELOCalloc
Expiry)
BSC6900
V900R012
73394033
VS.HHO.FailReloc
PrepOutInterRNC
CN.TgtF.PS.NCell
Number of Failed
Relocation
Preparations
Triggered by PS
HHO (Relocation
RNC or Target
System)
BSC6900
V900R012

3560
BSC6900 UMTS
None
Number of Successful Soft Handovers Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67189909
VS.SHO.SuccASU.NCell

Handovers Between
Neighboring Cells
Description
This counter provides the number of successful soft handovers between neighboring cells.This
Measurement point
The measurement is triggered at point C, as shown in the figure. When the RNC receives an
ACTIVE SET UPDATE COMPLETE message from the UE during a soft handover, the RNC
measures this counter for each pair of source and target cells. Here, the source cell refers to the
best cell that the UE camps on before the soft handover, and the target cell refers to the cells
whose RLs are added or the cell whose RL is released in this soft handover.
Formula
None
Issue 03 (2015-06-30)

3561
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.SuccASU.NCell
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
Number of Soft Handover Attempts Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67189910
VS.SHO.AttASU.NCell

Attempts Between
Neighboring Cells
Description
This measurement item provides the number of soft handover attempts between neighboring
cells.This counter complies with section "8.3.4 Active set update" in 3GPP TS 25.331 (v10.13.0).
Measurement point
ACTIVE SET UPDATE message to the UE during a soft handover, the RNC measures this item
for each pair of source and target cells. Here, the source cells refer to the best cell that the UE
camps on before the soft handover. The target cells refer to the cells whose RLs are added or
the cell whose RL is released in this soft handover.
Issue 03 (2015-06-30)

3562
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AttASU.NCell
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
Number of Failed Soft Handovers Between Neighboring Cells Due to No Response

from UE
Counters
Counter ID
Counter Name
Counter Description
67189911
VS.SHO.FailASU.NoReply.
NCell
Number of Failed Soft

Handovers Between
Neighboring Cells Due to
Waiting Active Set Update
Response Timeout
Description
This measurement item provides the number of unsuccessful soft handovers between
neighboring cells due to no response from the UE.This counter complies with section "8.3.4
Active set update" in 3GPP TS 25.331 (v10.13.0).
Measurement point
During a soft handover, after the RNC sends an ACTIVE SET UPDATE message to the UE, it
starts the timer to wait for the response from the UE. When the RNC receives no response until
the timer expires, it measures this item for each pair of source and target cells. Here, the source
cells refer to the best cell that the UE camps on before the soft handover. The target cells refer
to the cells whose RLs are added or the cell whose RL is released in this soft handover.
Issue 03 (2015-06-30)

3563
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.FailASU.NoReply.
NCell
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover

3564
BSC6900 UMTS
Number of Hard Handover Attempts Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67183489
VS.HHO.AttOut.NCell
Number of Hard Handovers

Attempts Between
Neighboring Cells
Description
This measurement item provides the number of hard handover attempts between neighboring
Measurement point
The measurement is triggered at point B, as shown in the figure. During the hard handover
procedure, for example, when the RNC sends a PHYSICAL CHANNEL
RECONFIGURATION message to the UE, the best cell that the UE camps on before the hard
handover is the source cell and the one that the UE camps on after the hard handover is the target
cell.
Figure 1-1493 Hard handover procedure (successful operation)
Formula
None
Issue 03 (2015-06-30)

3565
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.AttOut.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Successful Hard Handovers Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67183490
VS.HHO.SuccOut.NCell
Number of Successful Hard

Handovers Between
Neighboring Cells
Description
This measurement item provides the number of successful hard handovers between neighboring
Measurement point
The measurement is triggered at point C, as shown in the figure. During the hard handover
procedure, for example, when the RNC receives a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from the UE, the RNC shall measure this item
for each pair of source and target cells. Here, the best cell that the UE camps on before the hard
handover is source cell and the one that the UE camps on after the hard handover is the target
cell.
Issue 03 (2015-06-30)

3566
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.SuccOut.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Issue 03 (2015-06-30)

3567
BSC6900 UMTS
Number of Failed Hard Handovers Between Neighboring Cells Due to No

Response from UE
Counters
Counter ID
Counter Name
Counter Description
67189912
VS.HHO.FailOut.NoReply.
NCell
Number of Failed Hard

Handover Between
Neighboring Cells Due to
Timeout
Description
This measurement item provides the number of soft handover attempts between neighboring
Measurement point
During a hard handover, for example, when the RNC sends a PHYSICAL CHANNEL
RECONFIGURATION message to the UE, it starts the timer to wait for the response from the
UE. When the RNC receives no response until the timer expires, it measures this item for each
pair of source and target cells. Here, the source cells refer to the best cell that the UE camps on
before the hard handover. The target cells refer to the cells that the UE camps on after the hard
handover.
Figure 1-1495 Failed hard handover procedure (timer expiry)
Issue 03 (2015-06-30)

3568
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HHO.FailOut.NoReply.
NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of RL Addition Attempts in Soft Handover Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67183491
VS.SHO.AddRLAtt.NCell
Number of RL Addition
Between Neighboring Cells
Description
This measurement item provides the number of radio link addition attempts in the soft handover
between neighboring cells.This counter complies with section "8.3.4 Active set update" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
ACTIVE SET UPDATE message to the UE during the soft handover procedure, the RNC
measures this item for each pair of source and target cells if there are radio link additions in this
soft handover prodcedure. Here, the source cells refer to the best cell that the UE camps on before
the soft handover. The target cells refer to the cells whose RLs are added in this soft handover.
Issue 03 (2015-06-30)

3569
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.AddRLAtt.NCell
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
Number of Successful RL Additions in Soft Handover Between Neighboring Cells

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67183492
VS.SHO.AddRLSucc.NCell

3570
BSC6900 UMTS
Description
This counter provides the number of successful RL additions in the soft handover between
neighboring cells.This counter complies with section "8.3.4 Active set update" in 3GPP TS
25.331 (v10.13.0).
Measurement point
ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure,
the RNC measures this counter for each pair of source and target cells. Here, the source cell
refers to the best cell that the UE camps on before the soft handover, and the target cell refers
to the cells whose RLs are added in the soft handover.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SHO.AddRLSucc.NCell
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover

3571
BSC6900 UMTS
Number of RL Deletion Attempts in Soft Handover Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67183493
VS.SHO.DelRLAtt.NCell
Number of RL Deletion
Description
This measurement item provides the number of attempts to delete RLs in the soft handover
between neighboring cells.This counter complies with section "8.3.4 Active set update" in 3GPP
TS 25.331 (v10.13.0).
Measurement point
ACTIVE SET UPDATE message to the UE during the soft handover procedure, the RNC
measures this item for each pair of source and target cells. Here, source cells refer to the best
cell that the UE camps on before the soft handover. Target cells refer to the cells whose RLs
will be deleted in the soft handover.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3572
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.DelRLAtt.NCell
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
Number of Successful RL Deletions in Soft Handover Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67183494
VS.SHO.DelRLSucc.NCell
Deletions in Soft Handover
Description
This counter provides the number of radio link deletion attempts in the soft handover between
neighboring cells.This counter complies with section "8.3.4 Active set update" in 3GPP TS
25.331 (v10.13.0).
Measurement point
ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure,
the RNC measures this counter for each pair of source and target cells. Here, the source cell
refers to the best cell that the UE camps on before the soft handover, and the target cell refers
to the cells whose RLs will be deleted in the soft handover.
Issue 03 (2015-06-30)

3573
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SHO.DelRLSucc.NCell
WRFD-020202
WRFD-020201
Intra Node B Softer

Handover
Number of Hard Handover Attempts from HS-DSCH to HS-DSCH Between

Neighboring Cells
Counters
Counter ID
Counter Name
Counter Description
67190708
VS.HSDPA.HHO.NoChR.A
tt.NCell
Number of HSDSCH-toHSDSCH hard Handover

Requests Without Channel
Change Between
Neighboring Cells
Description
This measurement item provides the number of hard handover attempts from HS-DSCH to HSDSCH between neighboring cells.This counter complies with section "8.2.2 Reconfiguration
Measurement point
The measurement is triggered at point B, as shown in the figure. During a hard handover, for
example, when the RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to
an UE, the RNC measures this item for each pair of source and target cells. Here, source cell
refers to the best cell that the UE camps on before the hard handover. Target cells refer to the
cells that the UE camps on after the hard handover.
Issue 03 (2015-06-30)

3574
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSDPA.HHO.NoChR.A
tt.NCell
WRFD-01061006
HSDPA Mobility
Management

3575
BSC6900 UMTS
Number of Successful Hard Handovers from HS-DSCH to HS-DSCH Between

Neighboring Cells
Counters
Counter ID
Counter Name
Counter Description
67190709
VS.HSDPA.HHO.NoChR.S
ucc.NCell
HSDSCH-to-HSDSCH hard
Change Between
Neighboring Cells
Description
This measurement item provides the number of successful hard handovers from HS-DSCH to
HS-DSCH between neighboring cells.This counter complies with section "8.2.2 Reconfiguration
Measurement point
The measurement is triggered at point C, as shown in the figure. During a hard handover, for
example, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from an UE, the RNC measures this item for each pair of source and
target cells if the HSDPA service is in use before and after the hard handover. Here, source cell
refers to the best cell that the UE camps on before the hard handover. Target cells refer to the
Issue 03 (2015-06-30)

3576
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.HHO.NoChR.S
ucc.NCell
WRFD-01061006
HSDPA Mobility
Management
Number of HSDPA Serving Cell Change Attempts Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67190710
VS.HSDPA.ServCellChg.At
t.NCell
Number of HSDPA Serving

Cell Change Attempts
Description
This measurement item provides the number of HSDPA serving cell change attempts.This
Measurement point
This measurement item provides the number of HSDPA serving cell change attempts. This
procedure can be triggered with the following messages:
[1]PHYSICAL CHANNEL RECONFIGURATION,
[2]TRANSPORT CHANNEL RECONFIGURATION,
[3]RADIO BEARER RECONFIGURATION,
[4]ACTIVE SET UPDATE message.
Accordingly, UE may send
[1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE,
[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,
Issue 03 (2015-06-30)

3577
BSC6900 UMTS
[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,

[4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,
[5]RADIO BEARER RECONFIGURATION COMPLETE,
[6]RADIO BEARER RECONFIGURATION FAILURE,
[7]ACTIVE SET UPDATE COMPLETE,
[8]ACTIVE SET UPDATE FAILURE message to RNC as a response.
The measurement is triggered at point A, as shown in the figure. The procedure shown in the
figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When
the RNC sends the UE a PHYSICAL CHANNLE RECONFIGRATION message indicating that
the HSDPA serving cell changes, the RNC measures this item for each pair of source and target
cells.Here, source cell refers to the serving cell before change and target cell refers to the serving
cell after change.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.HSDPA.ServCellChg.At
t.NCell
WRFD-01061006
HSDPA Mobility
Management

3578
BSC6900 UMTS
Number of Successful HSDPA Serving Cell Changes Between Neighboring Cells

Counters
Counter ID
Counter Name
Counter Description
67190711
VS.HSDPA.ServCellChg.Su
cc.NCell
HSDPA Serving Cell
Changes Between
Neighboring Cells
Description
This measurement item provides the number of successful HSDPA serving cell changes.This
Measurement point
This measurement item provides the number of successful HSDPA serving cell changes. This
procedure can be triggered with the following messages:
[1]PHYSICAL CHANNEL RECONFIGURATION,
[2]TRANSPORT CHANNEL RECONFIGURATION,
[3]RADIO BEARER RECONFIGURATION,
[4]ACTIVE SET UPDATE message.
Accordingly, UE may send
[1]PHYSICAL CHANNEL RECONFIGURATION COMPLETE,
[2]PHYSICAL CHANNEL RECONFIGURATION FAILURE,
[3]TRANSPORT CHANNEL RECONFIGURATION COMPLETE,
[4]TRANSPORT CHANNEL RECONFIGURATION FAILURE,
[5]RADIO BEARER RECONFIGURATION COMPLETE,
[6]RADIO BEARER RECONFIGURATION FAILURE,
[7]ACTIVE SET UPDATE COMPLETE,
[8]ACTIVE SET UPDATE FAILURE message to RNC as a response.
The measurement is triggered at point B, as shown in the figure. The procedure shown in the
figure takes a PHYSICAL CHANNEL RECONFIGURATION message as an example. When
the RNC receives from the UE a PHYSICAL CHANNLE RECONFIGURATION COMPLETE
message indicating that the HSDPA serving cell changes, the RNC measures this item for each
pair of source and target cells. Here, source cell refers to the serving cell before change and
target cell refers to the serving cell after change.
Issue 03 (2015-06-30)

3579
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.HSDPA.ServCellChg.Su
cc.NCell
WRFD-01061006
HSDPA Mobility
Management
Number of CS Domain Outgoing Inter-Cell Hard Handover Attempts Between

Neighboring Cells
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393988
VS.HHO.AttOutIntraNodeB
.CS.NCell
Intra-NodeB Inter-Cell Hard
Handover Attempts
73393996
VS.HHO.AttOutInterNodeB
IntraRNC.CS.NCell
Intra-RNC Inter-NodeB
Inter-Cell Hard Handover
Attempts

3580
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394004
VS.HHO.AttOutInterRNCIu
r.CS.NCell
Inter-RNC Inter-Cell Hard
Handover Attempts
Description
These counters provide the number of CS domain outgoing inter-cell hard handover attempts
between neighboring cells.The preceding counters comply with section "8.2.2 Reconfiguration
Measurement point
The measurement is triggered at point B as shown in the figure, taking the physical channel
reconfiguration as an example. When the RNC determines to trigger a hard handover, it sends
to the UE a PHYSICAL CHANNEL RECONFIGURATION message. In this case, the RNC
measures this item for each pair of source and target cells if the HSDPA service is in use before
and after the hard handover. Here, source cell refers to the best cell that the UE camps on before
the hard handover. Target cells refer to the cells that the UE camps on after the hard handover.
Issue 03 (2015-06-30)

3581
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.CS.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
IntraRNC.CS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
r.CS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Number of Successful CS Domain Outgoing Hard Handovers Between

Neighboring Cells
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393989
VS.HHO.SuccOutIntraNode
B.CS.NCell
Outgoing Intra-NodeB InterCell Hard Handovers

3582
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73393997
VS.HHO.SuccOutInterNode
BIntraRNC.CS.NCell
Outgoing Intra-RNC InterNodeB Inter-Cell Hard
Handovers
73394005
VS.HHO.SuccOutInterRNC
Iur.CS.NCell
Outgoing Inter-RNC InterCell Hard Handovers
Description
These counters provide the number of CS domain successful Outgoing inter-cell hard handovers
Measurement point
Take physical channel reconfiguration as an example, the measurement is triggered at point C
as shown in the figure. When the RNC receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message, the RNC measures this item for each pair of
source and target cells. Here, the source cells refer to the best cell that the UE camps on before
the hard handover. The target cells refer to the cells that the UE camps on after the hard handover.
Issue 03 (2015-06-30)

3583
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
B.CS.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
BIntraRNC.CS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Iur.CS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Issue 03 (2015-06-30)

3584
BSC6900 UMTS
Number of Failed CS Domain Hard Handovers According to Different Causes

Counters
Counter ID
Counter Name
Counter Description
73393991
VS.HHO.FailOutIntraNode
B.PhyChFail.CS.NCell
Number of Failed CS
73393990
B.NoReply.CS.NCell
Number of Failed CS
Outgoing Intra-NodeB InterCell Hard Handovers (UE No
Response)
73393998
VS.HHO.FailOutInterNode
BIntraRNC.NoReply.CS.N
Cell
Number of Failed CS
Handovers (UE No
Response)
73393999
BIntraRNC.PhyChFail.CS.
NCell
Number of Failed CS
Handovers (Physical
Channel Failure)
73394006
VS.HHO.FailOutInterRNCI
ur.CfgUnsup.CS.NCell
Number of Failed CS
(Configuration
Unsupported)
73394007
ur.PhyChFail.CS.NCell
Number of Failed CS
Description
These counters provide the number of failed CS domain hard handovers between neighboring
cells according to different failure causes.The preceding counters comply with section "8.2.2
Measurement point
The measurement is triggered at point A as shown in the figure, taking PHYSICAL CHANNEL
RECONFIGURATION as an example. When the RNC receives from the UE a PHYSICAL
CHANNEL RECONFIGURATION FAILURE message, the RNC measures these items for
Issue 03 (2015-06-30)

3585
BSC6900 UMTS
each pair of source and target cells according to different failure causes. Here, the source cells
refer to the best cell that the UE camps on before the hard handover. The target cells refer to the
RECONFIGURATION as an example. When the RNC sends the UE a PHYSICAL CHANNEL
RECONFIGURATION message, it starts a timer to wait for the response message from the UE.
If no response is received from the UE before the timer expires, the hard handover is failed
because of "UE No Response". In this case, the RNC measures the items for each pair of source
and target cells according to different causes. Here, the source cells refer to the best cell that the
UE camps on before the hard handover. The target cells refer to the cells that the UE camps on
after the hard handover.
Issue 03 (2015-06-30)

3586
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
B.PhyChFail.CS.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
B.NoReply.CS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
BIntraRNC.NoReply.CS.N
Cell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
BIntraRNC.PhyChFail.CS.
NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Issue 03 (2015-06-30)

3587
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
ur.CfgUnsup.CS.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
ur.PhyChFail.CS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Number of PS Domain Outgoing Inter-Cell Hard Handover Attempts Between

Neighboring Cells
Counters
Counter ID
Counter Name
Counter Description
73393992
.PS.NCell
Intra-NodeB Inter-Cell Hard
Handover Attempts
73394000
IntraRNC.PS.NCell
Intra-RNC Inter-NodeB
Inter-Cell Hard Handover
Attempts
73394008
r.PS.NCell
Inter-RNC Inter-Cell Hard
Handover Attempts
Description
These counters provide the number of PS domain outgoing inter-cell hard handover attempts
Measurement point
The measurement is triggered at point B as shown in the figure, taking the physical channel
reconfiguration as an example. When the RNC determines to trigger a hard handover, it sends
Issue 03 (2015-06-30)

3588
BSC6900 UMTS
to the UE a PHYSICAL CHANNEL RECONFIGURATION message. In this case, the RNC

measures this item for each pair of source and target cells if the HSDPA service is in use before
and after the hard handover. Here, source cell refers to the best cell that the UE camps on before
the hard handover. Target cells refer to the cells that the UE camps on after the hard handover.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3589
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
.PS.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
IntraRNC.PS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
r.PS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Number of Successful PS Domain Outgoing Hard Handovers Between

Neighboring Cells
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393993
B.PS.NCell
73394001
BIntraRNC.PS.NCell
Handovers
73394009
Iur.PS.NCell

3590
BSC6900 UMTS
Description
These counters provide the number of PS domain successful Outgoing inter-cell hard handovers
Measurement point
Take physical channel reconfiguration as an example, the measurement is triggered at point C
as shown in the figure. When the RNC receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message, the RNC measures this item for each pair of
source and target cells. Here, the source cells refer to the best cell that the UE camps on before
the hard handover. The target cells refer to the cells that the UE camps on after the hard handover.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3591
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
B.PS.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
BIntraRNC.PS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Iur.PS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Number of Failed PS Domain Hard Handovers According to Different Causes

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393995
B.PhyChFail.PS.NCell
Number of Failed PS
73393994
B.NoReply.PS.NCell
Number of Failed PS
Outgoing Intra-NodeB InterCell Hard Handovers (UE No
Response)

3592
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394002
BIntraRNC.NoReply.PS.NC
ell
Number of Failed PS
Handovers (UE No
Response)
73394003
BIntraRNC.PhyChFail.PS.N
Cell
Number of Failed PS
Handovers (Physical
Channel Failure)
73394010
ur.CfgUnsup.PS.NCell
Number of Failed PS
(Configuration
Unsupported)
73394011
ur.PhyChFail.PS.NCell
Number of Failed PS
Description
These counters provide the number of failed PS domain hard handovers between neighboring
cells according to different failure causes.The preceding counters comply with section "8.2.2
Measurement point
RECONFIGURATION as an example. When the RNC receives from the UE a PHYSICAL
CHANNEL RECONFIGURATION FAILURE message, the RNC measures these items for
each pair of source and target cells according to different failure causes. Here, the source cells
refer to the best cell that the UE camps on before the hard handover. The target cells refer to the
Issue 03 (2015-06-30)

3593
BSC6900 UMTS
RECONFIGURATION as an example. When the RNC sends the UE a PHYSICAL CHANNEL
RECONFIGURATION message, it starts a timer to wait for the response message from the UE.
If no response is received from the UE before the timer expires, the hard handover is failed
because of "UE No Response". In this case, the RNC measures the items for each pair of source
and target cells according to different causes. Here, the source cells refer to the best cell that the
UE camps on before the hard handover. The target cells refer to the cells that the UE camps on
after the hard handover.
Formula
None
Issue 03 (2015-06-30)

3594
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
B.PhyChFail.PS.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
B.NoReply.PS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
BIntraRNC.NoReply.PS.NC
ell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
BIntraRNC.PhyChFail.PS.N
Cell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
ur.CfgUnsup.PS.NCell
WRFD-020301
WRFD-020302
WRFD-020304

Handover
Handover Based on
Coverage
Issue 03 (2015-06-30)

3595
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
ur.PhyChFail.PS.NCell
WRFD-020301

Handover
WRFD-020302
WRFD-020304

Handover Based on
Coverage
Number of Outgoing SRNS Relocation Executions with HHO Between

Neighboring Cells
Counters
Counter ID
Counter Name
Counter Description
73394026
VS.HHO.AttOutInterRNCC
N.CS.NCell
Number of Outgoing UEInvolved SRNS Relocation

Executions Triggered by CS
HHO
73394030
N.PS.NCell
Number of Outgoing UEInvolved SRNS Relocation

Executions Triggered by PS
HHO
Description
These counters provide the number of outgoing UE-involved SRNS relocation execution
attempts triggered by hard handover. Relocation execution is the process that the SRNC Sends
to the UE reconfiguration messages after the SRNC relocation prepration succeeds. The
reconfiguration involves the following messages: RADIO BEARER SETUP, RADIO BEARER
RECONFIGURATION, RADIO BEARER RELEASE, TRANSPORT CHANNEL
RECONFIGURATION, and PHYSICAL CHANNEL RECONFIGURATION. The originating
cell and the target cell of the hard handover should under different RNCs.The preceding counters
Measurement point
Take the RADIO BEARER RECONFIGURATION message as an example, the measurement
is triggered at point A as shown in the figure. When the SNRC sends the UE a RADIO BEARER
RECONFIGURATION message during the UE-involved SRNS relocation triggered by hard
handover, the counter is measured in both the best cells that the UE camps on before and after
the hard handover if the originating cell and the target cell are under different RNCs.
Issue 03 (2015-06-30)

3596
BSC6900 UMTS
Figure 1-1512 Reconfiguration procedure during SRNC relocation with hard handover
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
N.CS.NCell
WRFD-02060502

Handover
N.PS.NCell
WRFD-02060502

Handover
Number of Successful Outgoing SRNS Relocations with HHO Between

Neighboring Cells
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73394027
CN.CS.NCell
Outgoing UE-Involved
SRNS Relocations Triggered
by CS HHO

3597
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394031
CN.PS.NCell
Outgoing UE-Involved
SRNS Relocation
Executions Triggered by PS
HHO
Description
This counters provide the number of successful outgoing UE-involved SRNS relocations
triggered by the hard handover. The SRNC relocation succeeds when the CN sends an IU
Release", or "Network Optimization".The preceding counters comply with section "8.2.2
Measurement point
The measurement is triggered at point A as shown in the figure. When the SNRC receives an
IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal
Release", or "Network Optimization" during the UE-involved SRNS relocation triggered by
hard handover, the counter is measured in both the best cells that the UE camps on before and
after the hard handover if the originating cell and the target cell are under different RNCs.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3598
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
CN.CS.NCell
WRFD-02060502

Handover
CN.PS.NCell
WRFD-02060502

Handover
Number of Failed CS Domain Outgoing SRNS Relocation with HHO Preparations

According to Different Causes Between Neighboring Cells
Counters
Counter ID
Counter Name
Counter Description
73394028
VS.HHO.FailRelocPrepOutI
nterRNCCN.TExp.CS.NCel
l

UE-Involved SRNS
Relocation Preparations
Triggered by CS HHO
73394029
nterRNCCN.TgtF.CS.NCell

UE-Involved SRNS
Triggered by CS HHO
Description
These counters provide the number of CS domain failed outgoing UE-involved SRNS relocation
preparations triggered by hard handover according to different failure causes between
neighboring cells.The preceding counters comply with section "8.6 Relocation Preparation" in
3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC receives a
RELOCATION PREPARATION FAILURE message during the relocation triggered by a hard
handover. In this case, the corresponding counter is measured in both best cells that the UE
camps on before and after the hard handover according to different failure causes.
Issue 03 (2015-06-30)

3599
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
nterRNCCN.TExp.CS.NCel
l
WRFD-02060502

Handover
nterRNCCN.TgtF.CS.NCell
WRFD-02060502

Handover
Number of Failed PS Domain Outgoing SRNS Relocation with HHO Preparations

According to Different Causes Between Neighboring Cells
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73394032
nterRNCCN.TExp.PS.NCell

UE-Involved SRNS
Triggered by PS HHO

3600
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73394033
nterRNCCN.TgtF.PS.NCell

UE-Involved SRNS
Triggered by PS HHO
Description
These counters provide the number of PS domain failed outgoing UE-involved SRNS relocation
preparations triggered by hard handover according to different failure causes between
neighboring cells.The preceding counters comply with section "8.6 Relocation Preparation" in
3GPP TS 25.413 (v10.10.0).
Measurement point
The measurement is triggered at point A as shown in the figure, when the SRNC receives a
RELOCATION PREPARATION FAILURE message during the relocation triggered by a hard
handover. In this case, the corresponding counter is measured in both best cells that the UE
camps on before and after the hard handover according to different failure causes.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3601
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
nterRNCCN.TExp.PS.NCell
WRFD-02060502

Handover
nterRNCCN.TgtF.PS.NCell
WRFD-02060502

Handover
1.16 Measurement of UMTS DSP Performance(UDSP)

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

Overview
DSP is the core for the WCDMA RNC to handle the user plane protocol. During the system
operation, the DSP usage can be measured for the analysis of the system load and stability of
user plane handling so that the system runs in a reliable way.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73410488
VS.DSP.PSULTraf
fic
Number of UL PS
Traffic for DSP
BSC6900
V900R012
73410487
VS.DSP.PSDLTraf
fic
Number of DL PS
Traffic for DSP
BSC6900
V900R012
73393960
VS.DSP.UsagePeak
Peak DSP Usage in

Period
BSC6900
V900R012
73410486
VS.DSP.UsageAvg
Mean DSP Usage in

Period
BSC6900
V900R012

3602
BSC6900 UMTS
None
Uplink PS Traffic Handled by the DSP

Counters
Counter ID
Counter Name
Counter Description
73410488
VS.DSP.PSULTraffic
Number of UL PS Traffic for

DSP
Description
This measurement counter provides the uplink PS traffic handled by a DSP.
Measurement point
The measurement is triggered when the DSP handles the uplink PS data. This measurement
counter collects the information on the traffic at the RLC layer, excluding the RLC header. This
measurement counter includes RLC retransmitted traffic and soft handover, and does not include
softer handover.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DSP.PSULTraffic
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3603
BSC6900 UMTS
Downlink PS Traffic Handled by the DSP

Counters
Counter ID
Counter Name
Counter Description
73410487
VS.DSP.PSDLTraffic
Number of DL PS Traffic for

DSP
Description
This measurement counter provides the downlink PS traffic handled by a single DSP.
Measurement point
The measurement is triggered when the DSP handles the downlink PS data. This measurement
counter collects the information on the traffic at the RLC layer, excluding the RLC header. This
measurement counter includes RLC retransmitted traffic and soft handover, and does not include
softer handover.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.DSP.PSDLTraffic
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
Measurement of the DSP Usage in a Period

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73393960
VS.DSP.UsagePeak
Peak DSP Usage in Period
73410486
VS.DSP.UsageAvg
Mean DSP Usage in Period

3604
BSC6900 UMTS
specific formulas.
Counter ID
Counter Name
Counter Description
67196336
VS.DSP.DSPUsageAvgCount
Number of mean DSP Usage

Reports
67196335
VS.DSP.DSPUsageAvgValue
Mean Usage in 20 Seconds

for DSP
Description
These counters provide the maximum DSP CPU usage and average DSP CPU usage within a
measurement period.
Measurement point
The DSP CPU usage is sampled every five seconds. At the end of a measurement period, the
maximum of these sampling results is used as the value of VS.DSP.UsagePeak, and the value
of VS.DSP.UsageAvg is obtained by dividing the sum of these sampling results by the number
of samples.
Formula
VS.DSP.UsageAvg = [VS.DSP.DSPUsageAvgValue]/[VS.DSP.DSPUsageAvgCount]
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DSP.UsagePeak
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release
VS.DSP.UsageAvg
WRFD-010510
3.4/6.8/13.6/27.2Kbps RRC
and Release

3605
BSC6900 UMTS
1.17 Measurement of UMTS NIU DSP Performance

(UNIUDSP)
Overview
The UNIUDSP measurement object measures the load of the DSPs on an NIU board from the
following perspectives: total PS traffic, total number of PS data packets, total HTTP traffic, total
HTTPS traffic, total web page browsing traffic, total video traffic, total file download traffic,
total file upload traffic, and total number of packets related to the web page browsing, video,
file download, and file upload services.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
UNIUDSP
UMTS NIU DSP Performance Measurement
1.17.1 UMTS NIU DSP Performance Measurement(UNIUDSP)

Overview
NIU DSPs play an important role in identifying service types. Different types of services
processed by NIU DSPs can be measured to analyze system load. Based on the analysis results,
appropriate maintenance measures are taken to ensure reliable operation of the system.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73446438
VS.UNIUDSP.Traf
fic
Total PS Traffic
Processed by NIU
DSPs
BSC6900
V900R017C10
73446439
VS.UNIUDSP.Web
.Package.Num
Total Number of
Web Page Packets
Processed by NIU
DSPs
BSC6900
V900R017C10
73446440
VS.UNIUDSP.Pack
age.Num
Total Number of PS
Packets Processed by
NIU DSPs
BSC6900
V900R017C10
73446441
VS.UNIUDSP.HTT
P.Traffic
Total HTTP Traffic

Processed by NIU
DSPs
BSC6900
V900R017C10

3606
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73446442
VS.UNIUDSP.HTT
PS.Traffic
Total HTTPS Traffic

Processed by NIU
DSPs
BSC6900
V900R017C10
73446443
VS.UNIUDSP.Web
.Traffic
Total Web Page

Traffic Processed by
NIU DSPs
BSC6900
V900R017C10
73446444
VS.UNIUDSP.Vide
o.Traffic
Total Video Traffic

Processed by NIU
DSPs
BSC6900
V900R017C10
73446445
VS.UNIUDSP.Vide
o.Package.Num
Total Number of
Video Packets
Processed by NIU
DSPs
BSC6900
V900R017C10
73446446
VS.UNIUDSP.File
Download.Traffic
Total File Download

NIU DSPs
BSC6900
V900R017C10
73446447
VS.UNIUDSP.File
Download.Package.
Num
Total Number of File

Download Packets
Processed by NIU
DSPs
BSC6900
V900R017C10
73446448
VS.UNIUDSP.File
Upload.Traffic
Total File Upload

NIU DSPs
BSC6900
V900R017C10
73446449
VS.UNIUDSP.File
Upload.Package.N
um

Upload Packets
Processed by NIU
DSPs
BSC6900
V900R017C10
None
Total PS Traffic Processed by NIU DSPs

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73446438
VS.UNIUDSP.Traffic
Total PS Traffic Processed

by NIU DSPs

3607
BSC6900 UMTS
Description
This counter provides the total amount of uplink and downlink PS traffic processed by NIU
DSPs in a measurement period.
Measurement point
The system accumulates the total amount of uplink and downlink PS traffic processed by NIU
DSPs at the end of a measurement period. The counter value includes IP headers and
retransmitted TCP data.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.Traffic
WRFD-020132
WRFD-150252
WRFD-170202
TCP Proxy
WRFD-171210
Radio-Aware Video
Precedence
Total Number of Web Page Packets Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446439
VS.UNIUDSP.Web.Packag
e.Num
Total Number of Web Page

Packets Processed by NIU
DSPs
Description
This counter provides the total number of uplink and downlink web page packets processed by
NIU DSPs in a measurement period.
Issue 03 (2015-06-30)

3608
BSC6900 UMTS
Measurement point
The system accumulates the total number of uplink and downlink web page packets processed
by NIU DSPs at the end of a measurement period. The counter value includes retransmitted TCP
packets.
Each time when a UE establishes a TCP connection with a server, the serving NIU DSP checks
the service type after the server responds to an HTTP service request, as shown by point A in
figure 1. If the serving NIU DSP determines that the service type is web page browsing, this
counter is measured.
Figure 1-1516 Web service procedure
Formula
None
Issue 03 (2015-06-30)

3609
BSC6900 UMTS
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.Web.Packag
e.Num
WRFD-170202
TCP Proxy
Total Number of PS Packets Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446440
VS.UNIUDSP.Package.Nu
m
Total Number of PS Packets

Processed by NIU DSPs
Description
This counter provides the total number of uplink and downlink PS packets processed by NIU
Measurement point
The system accumulates the total number of uplink and downlink PS packets processed by NIU
DSPs at the end of a measurement period. The counter value includes retransmitted TCP packets.
Formula
None
Unit
packet
Issue 03 (2015-06-30)

3610
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.Package.Nu
m
WRFD-020132
WRFD-150252
WRFD-170202
TCP Proxy
WRFD-171210
Radio-Aware Video
Precedence
Different Traffic Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446441
VS.UNIUDSP.HTTP.Traffic
Total HTTP Traffic

73446442
VS.UNIUDSP.HTTPS.Traffic
Total HTTPS Traffic

Description
These counters provide the total amount of uplink and downlink HTTP and HTTPS traffic
processed by NIU DSPs in a measurement period.
Measurement point
The system accumulates the total amount of uplink and downlink HTTP and HTTPS traffic
processed by NIU DSPs at the end of a measurement period. The counter values include IP
headers and retransmitted TCP data.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

3611
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.HTTP.Traffic
WRFD-170202
TCP Proxy
WRFD-171210
Radio-Aware Video
Precedence
VS.UNIUDSP.HTTPS.Traffic
WRFD-170202
TCP Proxy
WRFD-171210
Radio-Aware Video
Precedence
Total Web Page Traffic Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446443
VS.UNIUDSP.Web.Traffic
Total Web Page Traffic

Description
This counter provides the total amount of uplink and downlink web page traffic processed by
Measurement point
The system accumulates the total amount of uplink and downlink web page traffic processed by
NIU DSPs at the end of a measurement period. The counter value includes IP headers and
figure 1. If the serving NIU DSP determines that the service type is web page browsing, this
counter is measured.
Issue 03 (2015-06-30)

3612
BSC6900 UMTS
Figure 1-1517 Web service procedure
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.Web.Traffic
WRFD-170202
TCP Proxy

3613
BSC6900 UMTS
Total Video Traffic Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446444
VS.UNIUDSP.Video.Traffic
Total Video Traffic

Description
This counter provides the total amount of uplink and downlink video traffic processed by NIU
Measurement point
The system accumulates the total amount of uplink and downlink video traffic processed by NIU
DSPs at the end of a measurement period. The counter value includes IP headers and
figure 1. If the serving NIU DSP determines that the service type is video, this counter is
measured.
Issue 03 (2015-06-30)

3614
BSC6900 UMTS
Formula
None
Unit
byte
Issue 03 (2015-06-30)

3615
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.Video.Traffic
WRFD-170202
TCP Proxy
WRFD-171210
Radio-Aware Video
Precedence
Total Number of Video Packets Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446445
VS.UNIUDSP.Video.Packa
ge.Num
Total Number of Video

DSPs
Description
This counter provides the total number of uplink and downlink video packets processed by NIU
Measurement point
The system accumulates the total number of uplink and downlink video packets processed by
NIU DSPs at the end of a measurement period. The counter value includes retransmitted TCP
packets.
figure 1. If the serving NIU DSP determines that the service type is video, this counter is
measured.
Issue 03 (2015-06-30)

3616
BSC6900 UMTS
Formula
None
Unit
packet
Issue 03 (2015-06-30)

3617
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.Video.Packa
ge.Num
WRFD-170202
TCP Proxy
WRFD-171210
Radio-Aware Video
Precedence
Total File Download Traffic Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446446
VS.UNIUDSP.FileDownloa
d.Traffic
Total File Download Traffic

Description
This counter provides the total amount of uplink and downlink file download traffic processed
by NIU DSPs in a measurement period.
Measurement point
The system accumulates the total amount of uplink and downlink file download traffic processed
by NIU DSPs at the end of a measurement period. The counter value includes IP headers and
the service type after the HTTP service request is complete, as shown by point A in figure 1. If
the serving NIU DSP determines that the service type is file download, this counter is measured.
Issue 03 (2015-06-30)

3618
BSC6900 UMTS
Figure 1-1520 File download procedure
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
d.Traffic
WRFD-170202
TCP Proxy

3619
BSC6900 UMTS
Total Number of File Download Packets Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446447
d.Package.Num

Download Packets Processed
by NIU DSPs
Description
This counter provides the total number of uplink and downlink file download packets processed
by NIU DSPs in a measurement period.
Measurement point
The system accumulates the total number of uplink and downlink file download packets
processed by NIU DSPs at the end of a measurement period. The counter value includes
retransmitted TCP packets.
the service type after the HTTP service request is complete, as shown by point A in figure 1. If
the serving NIU DSP determines that the service type is file download, this counter is measured.
Issue 03 (2015-06-30)

3620
BSC6900 UMTS
Figure 1-1521 File download procedure
Formula
None
Unit
packet
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
d.Package.Num
WRFD-170202
TCP Proxy

3621
BSC6900 UMTS
Total File Upload Traffic Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446448
VS.UNIUDSP.FileUpload.T
raffic
Total File Upload Traffic

Description
This counter provides the total amount of uplink and downlink file upload traffic processed by
Measurement point
The system accumulates the total amount of uplink and downlink file upload traffic processed
by NIU DSPs at the end of a measurement period. The counter value includes IP headers and
the service type after the HTTP POST request is comlete, as shown by point A in figure 1. If the
serving NIU DSP determines that the service type is file upload, this counter is measured.
Issue 03 (2015-06-30)

3622
BSC6900 UMTS
Figure 1-1522 File upload procedure
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.FileUpload.T
raffic
WRFD-170202
TCP Proxy

3623
BSC6900 UMTS
Total Number of File Upload Packets Processed by NIU DSPs

Counters
Counter ID
Counter Name
Counter Description
73446449
VS.UNIUDSP.FileUpload.P
ackage.Num
Total Number of File Upload

DSPs
Description
This counter provides the total number of uplink and downlink file upload packets processed by
Measurement point
The system accumulates the total number of uplink and downlink file upload packets processed
by NIU DSPs at the end of a measurement period. The counter value includes retransmitted TCP
packets.
the service type after the HTTP POST request is complete, as shown by point A in figure 1. If
the serving NIU DSP determines that the service type is file upload, this counter is measured.
Issue 03 (2015-06-30)

3624
BSC6900 UMTS
Figure 1-1523 File upload procedure
Formula
None
Unit
packet
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.UNIUDSP.FileUpload.P
ackage.Num
WRFD-170202
TCP Proxy

3625
BSC6900 UMTS
2 Transport Network Related Measurement
Transport Network Related Measurement
About This Chapter

The following table lists the relationship between measurement objects and boards. x indicates
the board from which the counters under the measurement object are collected.
Issue 03 (2015-06-30)
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
AA
L2P
AT
H
UM
TS
AA
L2P
AT
H_P
VC
LA
YE
R
UM
TS
AA
L2P
AT
H_
VC
LP
M
UM
TS
Boa
rd
PO
U
Boa
rd
EIU
Boa
rd
OI
U
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
XP
U
Boa
rd
AE
U
Boa
rd
UO
I
Boa
rd
AO
U

3626
BSC6900 UMTS
Issue 03 (2015-06-30)
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
Boa
rd
PO
U
Boa
rd
EIU
Boa
rd
OI
U
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
XP
U
ANI
_IP
GU
ANI
_Q
AA
L2
UM
TS
ANI
_Q
AA
L2_
IP
UM
TS
AT
ER_
RES
GS
M
AT
M_
LO
GIC
_PO
RT
UM
TS
BC
GS
M
BTS
CO
NN
EC
T
GS
M
BTS
EX
TO
PIP
PM
GS
M
BTS
IPP
M
GS
M
BTS
ML
PPP
GS
M
Boa
rd
AE
U
Boa
rd
UO
I
Boa
rd
AO
U

3627
BSC6900 UMTS
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
BTS
ML
PPP
GS
M
BTS
TU
NN
EL
GS
M
CH
AN
NE
LIZ
ED_
OP
TIC
AL_
PO
RT
GU
DP
CG
RO
UP
GS
M
ELE
CT
GU
E1T
1_E
S
GU
FE
GE
GU
Boa
rd
PO
U
Boa
rd
EIU
Boa
rd
OI
U
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
AE
U
x
x
Issue 03 (2015-06-30)
Boa
rd
AO
U
FIR
EW
AL
L
FR
AC
AT
ML
NK
Boa
rd
UO
I
Boa
rd
XP
U
UM
TS

3628
BSC6900 UMTS
Issue 03 (2015-06-30)
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
FR
ACI
MA
LN
K
UM
TS
GB
TSI
P
GS
M
HD
LC_
LIN
K
GS
M
IM
AG
RP
UM
TS
IM
AL
NK
UM
TS
INT
_TR
M
GU
IPO
AL
NK
UM
TS
IPO
AP
VC
_V
CLP
M
UM
TS
IPP
AT
H
GU
Boa
rd
PO
U
Boa
rd
EIU
Boa
rd
OI
U
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
XP
U
Boa
rd
AE
U
Boa
rd
UO
I
Boa
rd
AO
U

3629
BSC6900 UMTS
Issue 03 (2015-06-30)
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
Boa
rd
PO
U
Boa
rd
EIU
Boa
rd
OI
U
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
XP
U
IPP
AT
H_I
PL
AY
ER
GU
IPP
AT
H_P
M
GU
IPP
AT
H_
RTP
GU
IPP
OO
L_A
DJN
OD
E
GU
IPP
OO
L_P
M
UM
TS
IPP
OO
L_R
TP
GU
IPP
OO
L_S
IP
GU
IUR
PL
NK
UM
TS
Boa
rd
AE
U
Boa
rd
UO
I
Boa
rd
AO
U

3630
BSC6900 UMTS
Issue 03 (2015-06-30)
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
Boa
rd
PO
U
Boa
rd
EIU
Boa
rd
OI
U
LA
PD
LIN
K
GS
M
LO
CA
L_I
PA
DD
RES
S
GU
LO
GIC
_PO
RT
GU
LO
GIC
_PO
RT_
QU
EU
E
GU
M3
UA
_DE
GU
M3
UA
_LN
K
GU
M3
UA
_LN
K_S
ET
GU
ML
PPP
GU
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
XP
U
Boa
rd
AE
U
Boa
rd
UO
I
Boa
rd
AO
U

3631
BSC6900 UMTS
Issue 03 (2015-06-30)
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
Boa
rd
PO
U
Boa
rd
EIU
Boa
rd
OI
U
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
XP
U
ML
PPP
_Q
UE
UE
GU
MT
P2_
LN
K
GS
M
MT
P3_
DSP
GU
MT
P3_
LN
K
GU
MT
P3_
LN
K_S
ET
GU
NO
N_
CH
AN
NE
LIZ
ED_
OP
TIC
AL_
PO
RT
UM
TS
NS
VC
GS
M
NS
VL
GS
M
Boa
rd
AE
U
Boa
rd
UO
I
Boa
rd
AO
U
x
x

3632
BSC6900 UMTS
Issue 03 (2015-06-30)
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
Boa
rd
PO
U
Boa
rd
EIU
Boa
rd
OI
U
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
XP
U
OA
M_
FL
OW
UM
TS
PC
U
GS
M
PO
RT_
ABI
S
GS
M
PPP
GU
PPP
_Q
UE
UE
GU
PT
UF
E
GS
M
SA
AL_
LN
K
UM
TS
SA
AL
LN
K_P
VC
LA
YE
R
UM
TS
SA
AL
LN
K_
VC
LP
M
UM
TS
Boa
rd
AE
U
Boa
rd
UO
I
Boa
rd
AO
U

3633
BSC6900 UMTS
Issue 03 (2015-06-30)
Me
asu
rem
ent
obj
ect
Wh
ich
Mo
de
Boa
rd
PO
U
SC
CP
GU
SC
CP
DP
C
GS
M
SCT
PL
NK
GU
SCT
PL
NK
_IP
LA
YE
R
GU
SD
H
GU
TC_
RES
GS
M
TR
UN
K
GU
TS
AL
LO
C
GS
M
TW
AM
P
GU
UNI
LN
K
UM
TS
VC
AC
RO
SS
UM
TS
Boa
rd
EIU
Boa
rd
OI
U
Boa
rd
PE
U
Boa
rd
GO
U
Boa
rd
FG
2
Boa
rd
SC
U
Boa
rd
XP
U
Boa
rd
AE
U
Boa
rd
UO
I
Boa
rd
AO
U

3634
BSC6900 UMTS
2.1 Measurement of AAL2Path Performance(AAL2PATH)

2.2 Measurement of AAL2Path ATM Layer Performance(AAL2PATH_PVCLAYER)
2.3 Measurement of AAL2Path VCL PM Performance(AAL2PATH_VCLPM)
2.4 Measurement of IP Transport Adjacent Node Connection Performance(ANI_IP)
2.5 Measurement of QAAL2 Adjacent Node Performance(ANI_QAAL2)
2.6 Measurement of Dual-Stack Transport Adjacent Node Performance(ANI_QAAL2_IP)
2.7 Measurement of ATM Logical Port Performance(ATM_LOGIC_PORT)
2.8 Measurement of Channelized Optical Port Performance
(CHANNELIZED_OPTICAL_PORT)
2.9 Measurement of E1/T1 Port Bit Error Performance(E1T1_ES)
2.10 Measurement of E1/T1 Electrical Port Performance(ELECT)
2.11 Measurement of FE/GE Ethernet Port Performance(FEGE)
2.12 Measurement of Integrated Firewall Performance(FIREWALL)
2.13 Measurement of Fractional ATM Link Performance(FRACATMLNK)
2.14 Measurement of Fractioanl IMA Link Performance(FRACIMALNK)
2.15 Measurement of IMA Group Performance(IMAGRP)
2.16 Measurement of IMA Link Performance(IMALNK)
2.17 Measurement of Interface Board for Transport Resource Management Result Performance
(INT_TRM)
2.18 Measurement of IPoA Link Performance(IPOALNK)
2.19 Measurement of IPoAPVC VCL PM Performance(IPOAPVC_VCLPM)
2.20 Measurement of IP Path Performance(IPPATH)
2.21 Measurement of IPPath IP Layer Performance(IPPATH_IPLAYER)
2.22 Measurement of IPPath PM Performance(IPPATH_PM)
2.23 Measurement of IPPath RTP Performance(IPPATH_RTP)
2.24 Measurement of Transmission Resource Pool Adjacent Node Performance
(IPPOOL_ADJNODE)
2.25 Measurement of Transmission Resource Pool IPPM Performance(IPPOOL_PM)
2.26 Measurement of Transmission Resource Pool IP Address RTP Performance
(IPPOOL_RTP)
2.27 Measurement of Transmission Resource Pool Local IP Address Performance
(IPPOOL_SIP)
Issue 03 (2015-06-30)

3635
BSC6900 UMTS
2.28 Measurement of Iur-p Link Performance(IURPLNK)

2.29 Measurement of Local IP Address Performance(LOCAL_IPADDRESS)
2.30 Measurement of Logic Port Performance(LOGIC_PORT)
2.31 Measurement of Logic Port Queue Performance(LOGIC_PORT_QUEUE)
2.32 Measurement of M3UA Destination Entity Performance(M3UA_DE)
2.33 Measurement of M3UA Link Performance(M3UA_LNK)
2.34 Measurement of M3UA Link Set Performance(M3UA_LNK_SET)
2.35 Measurement of MP Group Performance(MLPPP)
2.36 Measurement of MP Queue Performance(MLPPP_QUEUE)
2.37 Measurement of MTP3 Destination Signaling Point Performance(MTP3_DSP)
2.38 Measurement of MTP3 Link Performance(MTP3_LNK)
2.39 Measurement of MTP3 Link Set Performance(MTP3_LNK_SET)
2.40 Measurement of Non-Channelized Optical Port Performance
(NON_CHANNELIZED_OPTICAL_PORT)
2.41 Measurement of NodeB OAM Flow Performance(OAM_FLOW)
2.42 Measurement of PPP Link Performance(PPP)
2.43 Measurement of PPP Link Queue Performance(PPP_QUEUE)
2.44 Measurement of SAAL Link Performance(SAAL_LNK)
2.45 Measurement of SAAL Link ATM Layer Performance(SAALLNK_PVCLAYER)
2.46 Measurement of SAAL VCL PM Performance(SAALLNK_VCLPM)
2.47 Measurement of SCCP OSP Performance(SCCP)
2.48 Measurement of SCTP Link Performance(SCTPLNK)
2.49 Measurement of SCTP Link IP Layer Performance(SCTPLNK_IPLAYER)
2.50 Measurement of SDH Performance(SDH)
2.51 Measurement of Trunk Group Performance(Trunk)
2.52 Measurement of TWAMP Performance(TWAMP)
2.53 Measurement of UNI Link Performance(UNILNK)
2.54 Measurement of VC Cross Connection Performance(VCACROSS)
Issue 03 (2015-06-30)

3636
BSC6900 UMTS
2.1 Measurement of AAL2Path Performance(AAL2PATH)

Overview
The AAL2 path is an important transmission resource. It carries the user plane data between the
BSC and other equipment. AAL2Path indicates transmission performance of an AAL2 path.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
AAL2PATH
AAL2 Path Measurement
2.1.1 AAL2 Path Measurement(AAL2PATH)

Overview
The AAL2 path measurement is used to measure the quality of transmission links directly affects
the system performance. It is used to helps analyze system transmission quality so as to maintain
system stability and reliability.
AAL2 paths carry mainly FP and IUUP packets. AAL2 paths are logical paths which are carried
by physical links, as shown in the following figure:
Figure 2-1 Physical bearer of the AAL2 path
Issue 03 (2015-06-30)

3637
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67204206
VS.AAL2PATH.Ac
t.Con
Number of Active
AAL2 Connections
to an Adjacent Node
Earlier than
BSC6900
V900R011
67195595
VS.AAL2PATH.F
wd.Cong
Number of Forward
Congestions on the
AAL2 Path
Earlier than
BSC6900
V900R011
67195596
VS.AAL2PATH.F
wd.Cong.Dur
Duration of Forward
Congestions on the
AAL2 Path
Earlier than
BSC6900
V900R011
67195597
VS.AAL2PATH.B
wd.Cong
Number of
Backward
Congestions on the
AAL2 Path
Earlier than
BSC6900
V900R011
67195598
VS.AAL2PATH.B
wd.Cong.Dur
Duration of
Backward
Congestions on the
AAL2 Path
Earlier than
BSC6900
V900R011
None
Number of Active AAL2 Connections to an Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67204206
VS.AAL2PATH.Act.Con
Number of Active AAL2

Connections to an Adjacent
Node
Description
This counter provides the number of active connections on an AAL2 path in a specified
measurement period. It indicates the connection status on a single AAL2 path. When the system
is configured with AAL2 paths and services access the system, active connections are required
Issue 03 (2015-06-30)

3638
BSC6900 UMTS
for the AAL2 path. An increase in the number of active connections indicates an increase in the
number of online users carried on the AAL2 path.
Measurement point
The system samples active connections on an AAL2 path every 15 seconds in a measurement
period. At the end of the measurement period, the system obtains the value of this counter by
dividing the accumulated number of active connections by the number of sampling times.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.Act.Con
WRFD-05030106
Call Admission Based on

Used AAL2 Path Bandwidth
Counters Related to the Number of Congestions on the AAL2 Path

Counters
Counter ID
Counter Name
Counter Description
67195595
VS.AAL2PATH.Fwd.Cong
Number of Forward
Congestions on the AAL2
Path
67195597
VS.AAL2PATH.Bwd.Cong
Number of Backward
Path
Description
When services using ATM transmission access the network, if the remaining bandwidth is less
than or equal to the congestion remaining threshold configured for an AAL2 path, traffic on the
AAL2 path is congested. Users can configure the congestion remaining threshold according to
the actual requirements. If the congestion remaining threshold is set to 0, congestion does not
occur. These counters provide the number of forward or backward bandwidth admission
congestions on an AAL2 path in a specified measurement period. The forward direction indicates
the TX direction, and the backward direction indicates the RX direction. These counters can be
Issue 03 (2015-06-30)

3639
BSC6900 UMTS
used together with the duration of AAL2 path congestion to observe the congestion. If traffic
on many AAL2 paths is congested for a long time, services are affected.
Measurement point
In a measurement period, the RNC checks the state of an AAL2 path each time a service is being
admitted to that path. This counter is incremented by one when the state of the AAL2 path
changes from non-congestion to forward or backward congestion, that is, the remaining
bandwidth available becomes smaller than the congestion threshold.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.Fwd.Cong
WRFD-05030106

VS.AAL2PATH.Bwd.Cong
WRFD-05030106

Counters Related to the Duration of Congestions on the AAL2 Path

Counters
Counter ID
Counter Name
Counter Description
67195596
VS.AAL2PATH.Fwd.Cong.
Dur
Duration of Forward
Path
67195598
VS.AAL2PATH.Bwd.Cong.
Dur
Duration of Backward
Path
Description
than or equal to the congestion remaining threshold configured for an AAL2 path, traffic on the
AAL2 path is congested. Users can configure the congestion remaining threshold according to
occur. These counters provide the duration of forward or backward congestions on an AAL2
Issue 03 (2015-06-30)

3640
BSC6900 UMTS
path in a measurement period. The forward direction indicates the TX direction, and the
backward direction indicates the RX direction. These counters can be used together with the
number of AAL2 path congestions to observe the congestion. If traffic on many AAL2 paths is
congested for a long time, services are affected.
Measurement point
In a measurement period, the RNC checks the state of an AAL2 path each time a service is being
admitted to that path. The measurement of a forward (backward) congestion duration starts when
a forward (backward) congestion is detected on an AAL2 path and stops when the forward
(backward) congestion is cleared. The accumulated duration of forward (backward) congestion
on the AAL2 path in the measurement period is taken as the value of this counter. Services will
be affected if many AAL2 paths are congested.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.Fwd.Cong.
Dur
WRFD-05030106

VS.AAL2PATH.Bwd.Cong.
Dur
WRFD-05030106

2.2 Measurement of AAL2Path ATM Layer Performance

(AAL2PATH_PVCLAYER)
Overview
AAL2 paths are ATM links used for resource management. It is used to configure the path that
carries user-plane data between the controller and other equipment. Measurement of AAL2Path
ATM Layer Performance indicates the transmission quality of the AAL2PATH link ATM Layer
on the AEUa, UOIa, AOUa, UOIc or AOUc board.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
AAL2PATH.PVCLAYER
AAL2Path ATM Layer Measurement

3641
BSC6900 UMTS
2.2.1 AAL2Path ATM Layer Measurement

(AAL2PATH.PVCLAYER)
Overview
The quality of transmission links directly affects the system performance. AAL2Path ATM
Layer Measurement helps analyze system transmission quality so as to maintain system stability
and reliability. This function subset takes effect after an AAL2Path link is added. Figure 1 shows
the location of the ATM Layer in the procotol.
Figure 2-2 ATM Reference Model
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194097
VS.AAL2PATH.P
VCLAYER.RXCO
RRECTCELLS
Number of Cells
Received on the
ATM Layer of the
AAL2 Path
Earlier than
BSC6900
V900R011

3642
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194098
VS.AAL2PATH.P
VCLAYER.RXBY
TES
Number of Bytes
Received on the
ATM Layer of the
AAL2 Path
Earlier than
BSC6900
V900R011
67194099
VS.AAL2PATH.P
VCLAYER.PEAK.
RXBYTES
Peak Number of
Bytes Received on
the ATM Layer of
the AAL2 Path
Earlier than
BSC6900
V900R011
67194100
VS.AAL2PATH.P
VCLAYER.TXCO
RRECTCELLS
Number of Cells
Transmitted on the
ATM Layer of the
AAL2 Path
Earlier than
BSC6900
V900R011
67194101
VS.AAL2PATH.P
VCLAYER.TXBY
TES
Number of Bytes
Transmitted on the
ATM Layer of the
AAL2 Path
Earlier than
BSC6900
V900R011
67194102
VS.AAL2PATH.P
VCLAYER.PEAK.
TXBYTES
Peak Number of
Bytes Transmitted on
the ATM Layer of
the AAL2 Path
Earlier than
BSC6900
V900R011
67194103
VS.AAL2PATH.P
VCLAYER.RXBY
TESOFAAL2CPSP
KTS
Number of Bytes of
AAL2 CPS
(Common Part
Sublayer) Packets
Received on the
ATM Layer of the
AAL2 Path
Earlier than
BSC6900
V900R011
67194104
VS.AAL2PATH.P
VCLAYER.TXBY
TESOFAAL2CPSP
KTS
Number of Bytes of
AAL2 CPS
(Common Part
Sublayer) Packets
Transmitted on the
ATM Layer of the
AAL2 Path
Earlier than
BSC6900
V900R011
67194105
VS.AAL2PATH.P
VCLAYER.DROP
FORHEADCELLS
Number of Cells
Discarded on the
ATM Layer of the
AAL2 Path Due to
Incorrect Header
Earlier than
BSC6900
V900R011

3643
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67194106
VS.AAL2PATH.P
VCLAYER.DROPFORRXOVERFL
OWCELLS
Number of Cells
Discarded on the
ATM Layer of the
AAL2 Path Due to
Overflow of Receive
Buffer
Earlier than
BSC6900
V900R011
67194107
VS.AAL2PATH.P
VCLAYER.DROPFORTXOVERFL
OWCELLS
Number of Cells
Discarded on the
ATM Layer of the
AAL2 Path Due to
Overflow of
Transmit Buffer
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of Cells Received, Transmitted or Dropped on an

AAL2PATH Link ATM Layer
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194097
VS.AAL2PATH.PVCLAYE
R.RXCORRECTCELLS
Number of Cells Received on

the ATM Layer of the AAL2
Path
67194100
VS.AAL2PATH.PVCLAYE
R.TXCORRECTCELLS
Number of Cells Transmitted

on the ATM Layer of the
AAL2 Path
67194105
VS.AAL2PATH.PVCLAYE
R.DROPFORHEADCELLS
Number of Cells Discarded

AAL2 Path Due to Incorrect
Header
67194106
VS.AAL2PATH.PVCLAYE
R.DROPFORRXOVERFLOWCELLS

AAL2 Path Due to Overflow
of Receive Buffer
67194107
VS.AAL2PATH.PVCLAYE
R.DROPFORTXOVERFLOWCELLS

AAL2 Path Due to Overflow
of Transmit Buffer

3644
BSC6900 UMTS
Description
These counters provide the number of cells received, transmitted or discarded on an AAL2PATH
link ATM Layer in the measurement period. They indicate the traffic volume of the AAL2PATH
link ATM Layer. The cells measured here are ATM cells. An ATM cell consists of 53 octets.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system obtains
the number of IEs received, transmitted or discarded on the link once every five seconds and
obtains the total number of one measurement period.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.PVCLAYE
R.RXCORRECTCELLS
WRFD-05030104
Dynamic AAL2 Connections

in Iub/IuCS/Iur Interface
VS.AAL2PATH.PVCLAYE
R.TXCORRECTCELLS
WRFD-05030104

VS.AAL2PATH.PVCLAYE
R.DROPFORHEADCELLS
WRFD-05030104

VS.AAL2PATH.PVCLAYE
R.DROPFORRXOVERFLOWCELLS
WRFD-05030104

VS.AAL2PATH.PVCLAYE
R.DROPFORTXOVERFLOWCELLS
WRFD-05030104


3645
BSC6900 UMTS
Counters Related to the Number of Bytes Received or Transmitted on an

AAL2PATH link ATM Layer
Counters
Counter ID
Counter Name
Counter Description
67194098
VS.AAL2PATH.PVCLAYE
R.RXBYTES

AAL2 Path
67194099
VS.AAL2PATH.PVCLAYE
R.PEAK.RXBYTES
Peak Number of Bytes

Received on the ATM Layer
of the AAL2 Path
67194101
VS.AAL2PATH.PVCLAYE
R.TXBYTES
Number of Bytes
Transmitted on the ATM
Layer of the AAL2 Path
67194102
VS.AAL2PATH.PVCLAYE
R.PEAK.TXBYTES
Peak Number of Bytes

67194103
VS.AAL2PATH.PVCLAYE
R.RXBYTESOFAAL2CPS
PKTS
Number of Bytes of AAL2

CPS(Common Part
Sublayer) Packets Received
AAL2 Path
67194104
VS.AAL2PATH.PVCLAYE
R.TXBYTESOFAAL2CPS
PKTS
Number of Bytes of AAL2

CPS(Common Part
Sublayer) Packets
Description
These counters provide the number of bytes received or transmitted on an AAL2PATH link
ATM Layer in the measurement period. They indicate the traffic volume of the AAL2PATH
link ATM Layer.
Measurement point
Samples are taken every five seconds in the a specific measurement period. The system obtains
the number of bytes received and transmitted on the link once every five seconds and obtains
the total number of one measurement period. The maximum numbers of bytes received and
transmitted is calculated based on the maximum numbers of bytes received and transmitted in
a sampling period within the measurement period.
Issue 03 (2015-06-30)

3646
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.PVCLAYE
R.RXBYTES
WRFD-05030104

VS.AAL2PATH.PVCLAYE
R.PEAK.RXBYTES
WRFD-05030104

VS.AAL2PATH.PVCLAYE
R.TXBYTES
WRFD-05030104

VS.AAL2PATH.PVCLAYE
R.PEAK.TXBYTES
WRFD-05030104

VS.AAL2PATH.PVCLAYE
R.RXBYTESOFAAL2CPS
PKTS
WRFD-05030104

VS.AAL2PATH.PVCLAYE
R.TXBYTESOFAAL2CPS
PKTS
WRFD-05030104

2.3 Measurement of AAL2Path VCL PM Performance

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

3647
BSC6900 UMTS
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
AAL2PATH.VCLPM
AAL2Path VCL PM Measurement
2.3.1 AAL2Path VCL PM Measurement(AAL2PATH.VCLPM)

Overview
After VCLPM is activated for AAL2 paths, the base station controller periodically sends forward
performance monitoring (FPM) cells and backward reporting (BR) cells to the peer end and
receives the response packet from the peer end. This measurement uses FPM and BR cells to
monitor the ATM transmission quality of a path. In the source direction, FPM cells are sent
periodically to indicate the number of transmitted cells and the number of error cells that failed
the Bit Interleaved Parity 16 (BIP16) check. In the sink direction, BR cells are transmitted as
response to the FPM cells. The BR cells calculate the number of received cells and the number
of error cells that fail the BIP16 check. In the source direction, BR cells are used to calculate
the number of discarded cells and the number of cells that are inserted by mistake. In the sink
direction, FPM cells are used to calculate the number of discarded cells and the number of cells
that are inserted by mistake. This function subset takes effect after VCLPM is activated for
AAL2 paths.
Figure 2-3 FPM and BR cells for VCL PM
Issue 03 (2015-06-30)

3648
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441401
VS.AAL2PATH.V
CLPM.RXCELL
Number of Received
VCL PM Cells on an
AAL2 Path
BSC6900
V900R014
73441402
VS.AAL2PATH.V
CLPM.TXCELL
Number of
Transmitted VCL
PM Cells on an
AAL2 Path
BSC6900
V900R014
73441403
VS.AAL2PATH.V
CLPM.PEAK.RXR
ATE
Maximum Receive
Rate of VCL PM on
an AAL2 Path
BSC6900
V900R014
73441404
VS.AAL2PATH.V
CLPM.PEAK.TXR
ATE
Maximum Transmit
Rate of VCL PM on
an AAL2 Path
BSC6900
V900R014
73441405
VS.AAL2PATH.V
CLPM.RX.MEAN.
LOSTCELLRATE
Average VCL PM
Cell Discard Rate in
the Receive
Direction of an
AAL2 Path
BSC6900
V900R014
73441406
VS.AAL2PATH.V
CLPM.RX.PEAK.
LOSTCELLRATE
Maximum VCL PM
the Receive
Direction of an
AAL2 Path
BSC6900
V900R014
73424531
VS.AAL2PATH.V
CLPM.TX.MEAN.
LOSTCELLRATE
Average VCL PM
the Transmit
Direction of an
AAL2 Path
BSC6900
V900R014
73441407
VS.AAL2PATH.V
CLPM.TX.PEAK.
LOSTCELLRATE
Maximum VCL PM
the Transmit
Direction of an
AAL2 Path
BSC6900
V900R014
73441408
VS.AAL2PATH.V
CLPM.RX.MEAN.
ERRINSERTCEL
LRATE
Average Rate of
Incorrectly Inserted
VCL PM Cells in the
Receive Direction of
an AAL2 Path
BSC6900
V900R014

3649
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73441409
VS.AAL2PATH.V
CLPM.RX.PEAK.
ERRINSERTCEL
LRATE
Maximum Rate of
VCL PM Cells in the
an AAL2 Path
BSC6900
V900R014
73441410
VS.AAL2PATH.V
CLPM.TX.MEAN.
ERRINSERTCEL
LRATE
Average Rate of
VCL PM Cells in the
Transmit Direction
of an AAL2 Path
BSC6900
V900R014
73441411
VS.AAL2PATH.V
CLPM.TX.PEAK.
ERRINSERTCEL
LRATE
Maximum Rate of
VCL PM Cells in the
Transmit Direction
of an AAL2 Path
BSC6900
V900R014
73424538
VS.AAL2PATH.V
CLPM.SOURCEBI
P16CRCERRCEL
L
Number of VCL PM
Error Cell Blocks
Failed the BIP16
Check in the Source
Direction of an
AAL2 Path
BSC6900
V900R014
73424539
VS.AAL2PATH.V
CLPM.SINKBIP16
CRCERRCELL
Number of VCL PM
Error Cell Blocks
Failed the BIP16
Check in the Sink
Direction of an
AAL2 Path
BSC6900
V900R014
None
Number of VCL PM Cells on an AAL2 Path

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441401
VS.AAL2PATH.VCLPM.R
XCELL
Number of Received VCL

PM Cells on an AAL2 Path
73441402
VS.AAL2PATH.VCLPM.T
XCELL
Number of Transmitted VCL

PM Cells on an AAL2 Path

3650
BSC6900 UMTS
Description
These counters provide the number of end-to-end received and transmitted cells at the ATM
layer over an AAL2 path and reflect the traffic over an AAL2 path at the ATM layer. Only ATM
cells are calculated.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The RNC measures the
number of cells transmitted at the ATM layers along an AAL2 path every 5 seconds and measures
the total number at the end of each measurement period.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.VCLPM.R
XCELL
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.T
XCELL
WRFD-05030110
F5
Maximum Data Rate of VCL PM on an AAL2 Path

Counters
Counter ID
Counter Name
Counter Description
73441403
VS.AAL2PATH.VCLPM.P
EAK.RXRATE
Maximum Receive Rate of

VCL PM on an AAL2 Path
73441404
VS.AAL2PATH.VCLPM.P
EAK.TXRATE
Maximum Transmit Rate of

VCL PM on an AAL2 Path
Description
These counters provide the end-to-end maximum receive and transmit rates on an AAL2 path,
indicating the maximum load in the receive and transmit directions on an AAL2 path.
Issue 03 (2015-06-30)

3651
BSC6900 UMTS
Measurement point
number of cells received and transmitted at the ATM layer along an AAL2 path every 5 seconds.
It compares and obtains the maximum number of received and transmitted cells per 5 seconds
within a measurement period and accordingly calculates the maximum receive and transmit
rates. The counters are in the unit of kbit/s, and are calculated with the following formula:
Maximum receive and transmit rates = Maximum number of received/transmitted cells x 53 x
8/5/1000.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.VCLPM.P
EAK.RXRATE
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.P
EAK.TXRATE
WRFD-05030110
F5
VCL PM Cell Discard Rate on an AAL2 Path

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441405
VS.AAL2PATH.VCLPM.R
X.MEAN.LOSTCELLRATE
Average VCL PM Cell

Discard Rate in the Receive
Direction of an AAL2 Path
73441406
VS.AAL2PATH.VCLPM.R
X.PEAK.LOSTCELLRATE
Maximum VCL PM Cell

73424531
VS.AAL2PATH.VCLPM.T
X.MEAN.LOSTCELLRATE
Average VCL PM Cell

Discard Rate in the Transmit
73441407
VS.AAL2PATH.VCLPM.T
X.PEAK.LOSTCELLRATE
Maximum VCL PM Cell


3652
BSC6900 UMTS
Description
These counters provide the end-to-end average and maximum rates of cells that are discarded
in the receive and transmit directions on an AAL2 path. They are used to monitor the error rate
of transmission cells on an AAL2 path.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. Every 5 seconds within
a measurement period, the RNC measures the number of cells that are discarded in the receive
and transmit directions at the ATM layers along an AAL2 path and compares to obtain the
maximum number. To obtain the maximum cell discard rates in the receive and transmit
directions, in each direction, the RNC divides the maximum number of cells that are discarded
within 5 seconds by the total number of cells measured in those directions during the same period.
To obtain the average cell discard rates in the receive and transmit directions, in each direction,
the RNC divides the number of cells discarded by the total number of cells measured in those
directions.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.VCLPM.R
X.MEAN.LOSTCELLRATE
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.R
X.PEAK.LOSTCELLRATE
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.T
X.MEAN.LOSTCELLRATE
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.T
X.PEAK.LOSTCELLRATE
WRFD-05030110
F5

3653
BSC6900 UMTS
Rate of Incorrectly Inserted VCL PM Cells on an AAL2 Path

Counters
Counter ID
Counter Name
Counter Description
73441408
VS.AAL2PATH.VCLPM.R
X.MEAN.ERRINSERTCELLRATE
Average Rate of Incorrectly

Inserted VCL PM Cells in the
Receive Direction of an
AAL2 Path
73441409
VS.AAL2PATH.VCLPM.R
X.PEAK.ERRINSERTCELLRATE
Maximum Rate of
Incorrectly Inserted VCL PM
Cells in the Receive
73441410
VS.AAL2PATH.VCLPM.T

Transmit Direction of an
AAL2 Path
73441411
VS.AAL2PATH.VCLPM.T
Maximum Rate of
Cells in the Transmit
Description
These counters provide the end-to-end average and maximum rates of cells that are incorrectly
inserted in the receive and transmit directions on an AAL2 path. They are used to monitor the
error rate of transmission cells on an AAL2 path.
Measurement point
a measurement period, the RNC measures the number of cells that are incorrectly inserted in the
receive and transmit directions at the ATM layers along an AAL2 path and compares to obtain
the maximum number. To obtain the maximum rates of incorrectly inserted cells in the receive
and transmit directions, in each direction, the RNC divides the maximum number of cells that
are incorrectly inserted within 5 seconds by the total number of cells measured in those directions
during the same period. To obtain the average rates of incorrectly inserted cells in the receive
and transmit directions, in each direction, the RNC divides the total number of incorrectly
inserted cells by the total number of measured cells in those directions during a measurement
period.
Formula
None
Issue 03 (2015-06-30)

3654
BSC6900 UMTS
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.VCLPM.R
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.R
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.T
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.T
WRFD-05030110
F5
Number of Error VCL PM Cell Blocks Failed BIP16 Check on an AAL2 Path
Counters
Counter ID
Counter Name
Counter Description
73424538
VS.AAL2PATH.VCLPM.S
OURCEBIP16CRCERRCELL
Number of VCL PM Error

Cell Blocks Failed the BIP16
Check in the Source
73424539
VS.AAL2PATH.VCLPM.SI
NKBIP16CRCERRCELL

Check in the Sink Direction
of an AAL2 Path
Description
These counters provide the number of error cell blocks that fail the BIP16 check in the receive
and transmit directions on an AAL2 path. They are used to monitor the error rate of transmission
cells on an AAL2 path.
Measurement point
number of error cell blocks that fail the BIP16 check in the source and link directions at the
Issue 03 (2015-06-30)

3655
BSC6900 UMTS
ATM layer along an AAL2 path every 5 seconds and calculates the total number at the end of
each measurement period. In each cell block measured for this counter, none of the cells is
discarded or incorrectly inserted.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2PATH.VCLPM.S
OURCEBIP16CRCERRCELL
WRFD-05030110
F5
VS.AAL2PATH.VCLPM.SI
NKBIP16CRCERRCELL
WRFD-05030110
F5
2.4 Measurement of IP Transport Adjacent Node

Connection Performance(ANI_IP)
Overview
An adjacent node is used to identify a logical node of network equipment adjacent to the BSC.
Measurement of IP Transport Adjacent Node Connection Performance indicates the
transmission performance of an IP transport adjacent node.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
ANIIPCONN
IP Transport Adjacent Node Connection

Measurement
ANIIPTRM
IP Transport Adjacent Node Resource

Operation Measurement

3656
BSC6900 UMTS
2.4.1 IP Transport Adjacent Node Connection Measurement

(ANIIPCONN)
Overview
IP Transport Adjacent Node Connection Measurement provides the measurement and statistics
on the attributes related to link establishments on an IP transport adjacent node during system
operation. This function subset helps analyze transmission quality and maintains system stability
and reliability. All counters of this function subset are not measured when the adjacent node
type is Iu-PS interface.
Figure 2-4 Physical bearer of the IP adjacent node
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194793
VS.ANI.IP.Conn.E
stab.Att
T6501:Number of
Connection Setup
Requests for IP
Transport from the
Transport Layer to
the Radio Network
Layer on the IP
Transport Adjacent
Node
Earlier than
BSC6900
V900R011

3657
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67194794
VS.ANI.IP.Conn.E
stab.Succ
T6502:Number of
Successful IP
Connection Setups
Initiated by the
Transport Layer on
IP Transport
Adjacent Node
Earlier than
BSC6900
V900R011
67194795
VS.ANI.IP.Conn.M
odify.Att
T6503:Number of IP
Connection
Modifications
Earlier than
BSC6900
V900R011
67194796
VS.ANI.IP.Conn.M
odify.Succ
T6504:Number of
Successful IP
Modifications
Initiated by the
Transport Layer on
IP Transport
Adjacent Node
Earlier than
BSC6900
V900R011
None
Number of IP Connection Setup Requests Received by IP Transport Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67194793
VS.ANI.IP.Conn.Estab.Att
T6501:Number of
for IP Transport from the
Transport Layer to the Radio
Network Layer on the IP
Transport Adjacent Node
Description
When services access the system, the radio layer sends a connection setup request to the transport
layer. This counter provides the number of IP link setup requests that the transport layer receives
from the radio layer in a specified measurement period.
Issue 03 (2015-06-30)

3658
BSC6900 UMTS
Measurement point
In a measurement period, this counter is incremented by one each time the transport layer
receives an IP link setup request message.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ANI.IP.Conn.Estab.Att
WRFD-050402
IP Transmission Introduction
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Number of Successful IP Connections for IP Transport Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67194794
VS.ANI.IP.Conn.Estab.Succ
T6502:Number of
Successful IP Connection
Setups Initiated by the
Transport Layer on IP
Description
When services access the system, the radio layer sends a connection setup request to the transport
layer. This counter provides the number of successful IP link setups initiated by the transport
layer in a specified measurement period.
Measurement point
receives an IP link setup request message and the link setup is successful.
Issue 03 (2015-06-30)

3659
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ANI.IP.Conn.Estab.Succ
WRFD-050402
on Iub Interface
Number of IP Connection Modifications

Counters
Counter ID
Counter Name
Counter Description
67194795
VS.ANI.IP.Conn.Modify.At
t
T6503:Number of IP
Connection Modifications
Description
When the service rate of the system needs to be adjusted, the radio layer sends a connection
modification request to the transport layer. This counter provides the number of IP connection
modification requests that the transport layer receives from the radio layer in a specified
measurement period.
Measurement point
receives an IP connection modification message.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3660
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.ANI.IP.Conn.Modify.At
t
WRFD-050402
on Iub Interface
Number of Successful IP Connection Modifications for IP Transport Adjacent

Node
Counters
Counter ID
Counter Name
Counter Description
67194796
VS.ANI.IP.Conn.Modify.Su
cc
T6504:Number of
Successful IP Modifications
Initiated by the Transport
Layer on IP Transport
Adjacent Node
Description
When the service rate of the system needs to be adjusted, the radio layer sends a connection
modification request to the transport layer. This counter provides the number of successful IP
transport bandwidth modifications performed by the transport layer in a specified measurement
period.
Measurement point
receives an IP connection modification message and the modification is successful.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ANI.IP.Conn.Modify.Su
cc
WRFD-050402
on Iub Interface

3661
BSC6900 UMTS
2.4.2 IP Transport Adjacent Node Resource Operation

Measurement(ANIIPTRM)
Overview
IP Transport Adjacent Node Resource Operation Measurement provides the measurement and
statistics on IP transmission links during the system operation. This function subset provides the
counters related to the number of failed transmission link applications and forward and backward
bandwidths. It helps analyze system transmission quality to maintain system stability ad
reliability.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194787
VS.ANI.IP.AttResAlloc
T6507:Number of
Requests for
Resource Allocation
on the IP Transport
Adjacent Node
BSC6900
V900R014
67194788
VS.ANI.IP.SuccResAlloc
T6508:Number of
Successful Resource
Allocations on the IP
Transport Adjacent
Node
BSC6900
V900R014
67204475
OS.ANI.IP.AllocedFwd
T6509:IP Path
Forward Bandwidth
Allocated to IP
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67204476
OS.ANI.IP.AllocedBwd
T6510:IP Path
Backward
Bandwidth
Allocated to IP
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67196162
VS.ANI.IP.FailResAllocForBwLimit
T6511:Number of
Failed Resource
Allocations Due to
Insufficient
Bandwidth on the IP
Transport Adjacent
Node
Earlier than
BSC6900
V900R011

3662
BSC6900 UMTS
None
Number of Requests for Resource Allocation on the IP Transport Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67194787
T6507:Number of Requests
for Resource Allocation on
the IP Transport Adjacent
Node
Description
When services access the system, the radio layer sends a transmission resource application
request to the transport layer. This counter provides the number of IP transmission resource
applications that the transport layer receives from the radio layer in a specified measurement
period.
Measurement point
receives an IP resource application message.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050402
on Iub Interface

3663
BSC6900 UMTS
Number of Successful Resource Allocations on the IP Transport Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67194788
T6508:Number of
Successful Resource
Allocations on the IP
Description
request to the transport layer. This counter provides the number of successful IP transmission
resource applications that the transport layer receives from the radio layer in a specified
measurement period.
Measurement point
receives an IP resource application message and the application is successful.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-050402
on Iub Interface
IP Path Forward Bandwidth Allocated to IP Transport Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204475
T6509:IP Path Forward

Bandwidth Allocated to IP

3664
BSC6900 UMTS
Description
When accessing the system, services need to apply for the bandwidth to perform bandwidth
admission. In non-transmission-pool networking, this counter provides the forward bandwidth,
that is, admitted bandwidth, allocated to an IP path on an adjacent node in a specified
measurement period. It is the average forward bandwidth sampled in a measurement period. In
transmission pool networking, this counter provides the forward bandwidth, that is, admitted
bandwidth, allocated to an adjacent node in a specified measurement period. It is the average
forward bandwidth sampled in a measurement period.
Measurement point
In non-transmission-pool networking, the system automatically samples the forward bandwidth
allocated to an IP path on an interface adjacent node every 15s in a measurement period. At the
end of the measurement period, the system divides the accumulated forward bandwidth by the
number of samples to obtain the average forward bandwidth allocated to the IP path on the
interface adjacent node. This counter becomes ineffective when the actual flow admission is
enabled. In transmission pool networking, the system automatically samples the forward
bandwidth allocated to an IP path on an interface adjacent node every 15s in a measurement
period. At the end of the measurement period, the system divides the accumulated forward
bandwidth by the number of samples to obtain the average forward bandwidth allocated to the
enabled. The interface type can be Iub, Iur, Iu-CS, or Iu-PS.
Formula
None
Unit
bit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050402
on Iub Interface

3665
BSC6900 UMTS
IP Path Backward Bandwidth Allocated to IP Transport Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67204476
T6510:IP Path Backward

Bandwidth Allocated to IP
Description
When accessing the system, services need to apply for the bandwidth to perform bandwidth
admission. In non-transmission-pool networking, this counter provides the backward bandwidth,
that is, admitted bandwidth, allocated to an adjacent node in a specified measurement period. It
is the average backward bandwidth sampled in a measurement period. In transmission pool
networking, this counter provides the backward bandwidth, that is, admitted bandwidth,
allocated to an adjacent node in a specified measurement period. It is the average backward
bandwidth sampled in a measurement period.
Measurement point
In non-transmission-pool networking, the system automatically samples the backward
bandwidth allocated to an interface adjacent node every 15s in a measurement period. At the
end of the measurement period, the system divides the accumulated backward bandwidth by the
number of samples to obtain the average backward bandwidth allocated to an IP path on the
enabled. In transmission pool networking, the system automatically samples the backward
bandwidth allocated to an interface adjacent node every 15s in a measurement period. At the
end of the measurement period, the system divides the accumulated backward bandwidth by the
number of samples to obtain the average backward bandwidth allocated to the interface adjacent
node. This counter becomes ineffective when the actual flow admission is enabled. The interface
type can be Iub, Iur, Iu-CS, or Iu-PS.
Formula
None
Unit
bit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050402
on Iub Interface

3666
BSC6900 UMTS
Number of Failed Resource Allocations Due to Insufficient Bandwidth on the IP

Counters
Counter ID
Counter Name
Counter Description
67196162
T6511:Number of Failed
Resource Allocations Due to
Insufficient Bandwidth on
the IP Transport Adjacent
Node
Description
request to the transport layer. If transmission resources are insufficient, the transport layer returns
a resource application failure message to the radio layer. This counter provides the number of
failed resource applications due to insufficient transmission bandwidth in a specified
measurement period.
Measurement point
In a measurement period, this counter is incremented by one each time the IP resource application
initiated by the radio network layer fails because of insufficient bandwidth.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050402
on Iub Interface

3667
BSC6900 UMTS
2.5 Measurement of QAAL2 Adjacent Node Performance

(ANI_QAAL2)
Overview
An adjacent node is used to identify a logical node of network equipment adjacent to the base
station controller. Measurement of QAAL2 Adjacent Node Performance is used to measure
QAAL2 adjacent nodes.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
QAAL2
QAAL2 Measurement
2.5.1 QAAL2 Measurement(QAAL2)

Overview
QAAL2 Measurement is used to measure AAL2 connections and releases on a QAAL2 adjacent
node. QAAL2 is the control plane protocol of AAL2 and is used to control the setup and release
of AAL2 connections. QAAL2 adjacent nodes of an RNC include NodeB, MSC, MGW, and
neighboring RNC (NRNC).
Figure 2-5 Physical bearer of the QAAL2 adjacent node
Issue 03 (2015-06-30)

3668
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190053
VS.AAL2.CAC.Att
Number of AAL2
Path Resource
Admissions
Earlier than
BSC6900
V900R011
67190054
VS.AAL2.CAC.Suc
c
Number of
Successful AAL2
Path Admissions
Earlier than
BSC6900
V900R011
67190055
VS.QAAL2.Est.RL
C.NoRoute.Rx
Number of RLC
Messages Received
by the QAAL2 Due
to No Route at the
Remote End
Earlier than
BSC6900
V900R011
67190056
VS.QAAL2.Est.RL
C.NoPath.Rx
Number of RLC
Messages Received
by QAAL2 Due to
No AAL2 Path
Configued at the
Remote End
Earlier than
BSC6900
V900R011
67190057
VS.QAAL2.Est.RL
C.NoCID.Rx
Number of RLC
Messages Received
by QAAL2 Due to
No CID Available at
the Remote End
Earlier than
BSC6900
V900R011
67190058
VS.QAAL2.Est.RL
C.Fail.Rx
Number of RLC
Messages Received
by QAAL2 Due to
Remote Network
Fault, Remote
Temporary Failure,
or Remote Normal
Releases
Earlier than
BSC6900
V900R011
67190059
VS.QAAL2.Est.RL
C.Cong.Rx
Number of RLC
Messages Received
by QAAL2 Due to
Switch Congestion at
the Remote End
Earlier than
BSC6900
V900R011

3669
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190060
VS.QAAL2.Est.RL
C.RecovOut.Rx
Number of RLC
Messages Received
by QAAL2 Due to
Timer Expiry at the
Remote End
Earlier than
BSC6900
V900R011
67190061
VS.QAAL2.Est.RL
C.NoRoute.Tx
Number of RLC
QAAL2 Due to No
Route at the Remote
End
Earlier than
BSC6900
V900R011
67190062
VS.QAAL2.Est.RL
C.NoPath.Tx
Number of RLC
QAAL2 Due to No
AAL2 Path
Configured
Earlier than
BSC6900
V900R011
67190063
VS.QAAL2.Est.RL
C.NoCID.Tx
Number of RLC
QAAL2 Due to No
CID Available
Earlier than
BSC6900
V900R011
67190064
VS.QAAL2.Est.RL
C.Fail.Tx
Number of RLC
QAAL2 Due to
Network Failure,
Unspecified Reason,
or Temporary Failure
Earlier than
BSC6900
V900R011
67190065
VS.QAAL2.Est.RL
C.Cong.Tx
Number of RLC
Messages Sent by
QAAL2 Due to
Switch Congestion
Earlier than
BSC6900
V900R011
67190066
VS.QAAL2.Est.RL
C.RecovOut.Tx
Number of RLC
Messages Sent by
QAAL2 Due to
Timer Expiry
Earlier than
BSC6900
V900R011
67183361
VS.QAAL2.ERQ.T
x
Number of AAL2
Connection
Establishment
Requests Sent by the
QAAL2
Earlier than
BSC6900
V900R011

3670
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67183362
VS.QAAL2.ERQ.R
x
Number of AAL2
Connection
Establishment
Requests Received
by the QAAL2
Earlier than
BSC6900
V900R011
67183363
VS.QAAL2.Est.RL
C.Rx
Number of AAL2
Connection Release
Confirmations
(RLCs) Received by
the QAAL2 After the
QAAL2 Sends the
ERQ Message
Earlier than
BSC6900
V900R011
67183364
VS.QAAL2.Est.EC
F.Rx
Number of ECF
Messages Received
by the QAAL2 After
the QAAL2 Sends
the ERQ Message
Earlier than
BSC6900
V900R011
67183365
VS.QAAL2.Est.EC
F.Tx
Number of ECF
QAAL2 After the
QAAL2 Receives the
ERQ Message
Earlier than
BSC6900
V900R011
67183366
VS.QAAL2.Est.RL
C.Tx
Number of RLC
QAAL2 After the
QAAL2 Receives the
ERQ Message
Earlier than
BSC6900
V900R011
67183367
VS.QAAL2.Rel.Tx
Number of AAL2
Connection Release
Requests (RELs)
Sent by the QAAL2
Earlier than
BSC6900
V900R011
67183368
VS.QAAL2.Rel.Rx
Number of AAL2
Connection Release
Requests (RELs)
Received by the
QAAL2
Earlier than
BSC6900
V900R011
67183369
VS.QAAL2.Rel.RL
C.Rx
Number of AAL2
Connection Release
Confirmations
(RLCs) Received by
the QAAL2 After the
QAAL2 Sends the
REL Message
Earlier than
BSC6900
V900R011

3671
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67183370
VS.QAAL2.Rel.RL
C.Tx
Number of RLC
QAAL2 After the
QAAL2 Receives the
REL Message
Earlier than
BSC6900
V900R011
67190067
VS.QAAL2.RxModRej
Number of AAL2
Connection
Modification
Rejections (MORs)
Received by the
QAAL2
Earlier than
BSC6900
V900R011
67190068
VS.QAAL2.TxModRej
Number of MOR
QAAL2 After the
QAAL2 Receives the
MOD Message
Earlier than
BSC6900
V900R011
67190553
VS.QAAL2.TxMod
Number of AAL2
Connection
Modification
Requests (MODs)
Sent by the QAAL2
Earlier than
BSC6900
V900R011
67190554
VS.QAAL2.RxMod
Number of AAL2
Connection
Modification
Requests (MODs)
Received by the
QAAL2
Earlier than
BSC6900
V900R011
67199677
VS.QAAL2.Act.Co
n
Number of Active
AAL2 Connections
to an QAAL2
Adjacent Node
Earlier than
BSC6900
V900R011
67190555
VS.QAAL2.Alloced
Fwd.AAL2BitRate
Mean Forward
Bandwidth of AAL2
Path Allocated to an
Adjacent Node
Earlier than
BSC6900
V900R011
67190558
VS.QAAL2.Alloced
Bwd.AAL2BitRate
Mean Backward
Bandwidth of AAL2
Path Allocated to an
Adjacent Node
Earlier than
BSC6900
V900R011

3672
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67190562
VS.QAAL2.Alloced
MaxFwd.AAL2Bit
Rate.Value
Maximum Value of
AAL2 Path Forward
Bandwidth
Allocated to an
Adjacent Node
Earlier than
BSC6900
V900R011
67190565
VS.QAAL2.Alloced
MaxBwd.AAL2Bit
Rate.Value
Maximum Value of
AAL2 Path
Backward
Bandwidth
Allocated to an
Adjacent Node
Earlier than
BSC6900
V900R011
67196149
VS.QAAL2.Est.RL
C.NoBitRate.Tx
Number of RLC
QAAL2 Due to No
Bandwidth
Available
Earlier than
BSC6900
V900R011
None
Number of Resource Allocation Requests by QAAL2

Counters
Counter ID
Counter Name
Counter Description
67190053
VS.AAL2.CAC.Att
Number of AAL2 Path

Resource Admissions
Description
When services using ATM transmission access the network, the radio layer sends a transmission
resource application request to the transport layer. This counter provides the number of
transmission resource applications received by the transport layer in ATM mode in a specified
measurement period.
Measurement point
In a measurement period, this counter is incremented by one each time the QAAL2 performs
path and CID resource admission and allocation after the QAAL2 receives an AAL2 connection
setup request from the upper layer. This counter is measured regardless of whether the path and
CID resource admission and allocation are successful.
Issue 03 (2015-06-30)

3673
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2.CAC.Att
WRFD-05030106

Number of Successful Resource Allocations by QAAL2

Counters
Counter ID
Counter Name
Counter Description
67190054
VS.AAL2.CAC.Succ
Number of Successful AAL2

Path Admissions
Description
When services using ATM transmission access the network, the radio layer sends a transmission
resource application request to the transport layer. This counter provides the number of
successful transmission resource applications received by the transport layer in ATM mode in
a specified measurement period.
Measurement point
In a measurement period, this counter is incremented by one each time the path and CID resource
admission and allocation performed by the QAAL2 are successful after the QAAL2 receives an
AAL2 connection setup request from the upper layer.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3674
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.AAL2.CAC.Succ
WRFD-05030106

Number of RLC messages received by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67190055
VS.QAAL2.Est.RLC.NoRo
ute.Rx
Number of RLC Messages

Received by the QAAL2 Due
to No Route at the Remote
End
67190056
VS.QAAL2.Est.RLC.NoPat
h.Rx

Received by QAAL2 Due to
No AAL2 Path Configued at
the Remote End
67190057
VS.QAAL2.Est.RLC.NoCI
D.Rx

No CID Available at the
Remote End
67190058
VS.QAAL2.Est.RLC.Fail.R
x

Remote Network Fault,
Remote Temporary Failure,
or Remote Normal Releases
67190059
VS.QAAL2.Est.RLC.Cong.
Rx

Switch Congestion at the
Remote End
67190060
VS.QAAL2.Est.RLC.Recov
Out.Rx

Timer Expiry at the Remote
End
Description
These counters provide the number of AAL2 RLC messages that the base station controller
receives from the adjacent node due to various reasons.
Issue 03 (2015-06-30)

3675
BSC6900 UMTS
Measurement point
In a measurement period, these counters are measured when the base station controller receives
the connection setup rejection from the adjacent node due to various reasons after sending the
AAL2 ERQ message to the adjacent node.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ute.Rx
WRFD-05030104

h.Rx
WRFD-05030104

D.Rx
WRFD-05030104

VS.QAAL2.Est.RLC.Fail.R
x
WRFD-05030104

Rx
WRFD-05030104

Out.Rx
WRFD-05030104

Number of RLC messages sent by the QAAL2

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190061
ute.Tx

Sent by the QAAL2 Due to
No Route at the Remote End
67190062
h.Tx

No AAL2 Path Configured

3676
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67190063
D.Tx

No CID Available
67190064
VS.QAAL2.Est.RLC.Fail.T
x

Network Failure,
Unspecified Reason, or
Temporary Failure
67190065
Tx

Sent by QAAL2 Due to
Switch Congestion
67190066
Out.Tx

Sent by QAAL2 Due to
Timer Expiry
67196149
VS.QAAL2.Est.RLC.NoBit
Rate.Tx

No Bandwidth Available
Description
These counters provide the number of AAL2 RLC messages that the QAAL2 sends to the
adjacent node due to various reasons.
Measurement point
In a measurement period, after the base station controller sends an AAL2 ERQ message to the
adjacent node and the adjacent node sends the REL message to the base station controller. These
counters are measured when the QAAL2 sends the RLC message to the adjacent node due to
various reasons.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
ute.Tx
WRFD-05030104


3677
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
h.Tx
WRFD-05030104

D.Tx
WRFD-05030104

VS.QAAL2.Est.RLC.Fail.T
x
WRFD-05030104

Tx
WRFD-05030104

Out.Tx
WRFD-05030104

VS.QAAL2.Est.RLC.NoBit
Rate.Tx
WRFD-05030106

Number of AAL2 Connection Establishment Requests Sent by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67183361
VS.QAAL2.ERQ.Tx
Number of AAL2
Requests Sent by the QAAL2
Description
When services using ATM transmission access the network, the base station controller sends
the ERQ message to the peer NE. This counter provides the number of ERQ messages that the
base station controller sends to the peer NE in a specified measurement period.
Measurement point
The measurement is triggered at point B shown in Figure 1. In a measurement period, this counter
is incremented by one each time the base station controller sends the AAL2 ERQ message to
the peer NE (NodeB shown in the figure).
Issue 03 (2015-06-30)

3678
BSC6900 UMTS
Figure 2-6 Successful AAL2 connection establishment procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.ERQ.Tx
WRFD-05030104

Number of AAL2 Connection Establishment Requests Received by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67183362
VS.QAAL2.ERQ.Rx
Number of AAL2
QAAL2
Description
When the local RNC works as the DRNC, the local RNC receives the ERQ message from the
peer NE. This counter provides the number of ERQ messages that the QAAL2 receives from
the peer NE. In normal situations, AAL2 connections are passively set up over only the Iur
interface. The base station controller actively initiates AAL2 connection setup over the Iub and
Iu interfaces.
Issue 03 (2015-06-30)

3679
BSC6900 UMTS
Measurement point
The measurement is triggered at point A shown in Figure 1. In a measurement period, this counter
is incremented by one each time the RNC receives the AAL2 ERQ message from the peer NE
(other RNC shown in the figure).
Figure 2-7 Successful AAL2 connection establishment procedure initiated by an adjacent node
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.ERQ.Rx
WRFD-05030104

Number of AAL2 Connection Establishment Request Rejections Received by the

QAAL2
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67183363
VS.QAAL2.Est.RLC.Rx
Number of AAL2
Connection Release
Confirmations (RLCs)
Received by the QAAL2
After the QAAL2 Sends the
ERQ Message

3680
BSC6900 UMTS
Description
the ERQ message to the peer NE. This counter provides the number of RLC messages that the
QAAL2 receives from the peer NE after sending the ERQ message to the peer NE.
Measurement point
is incremented by one each time the base station controller receives the RLC message from the
peer NE (NodeB shown in the figure) after sending the AAL2 ERQ message to the peer NE.
Figure 2-8 Failed AAL2 connection establishment procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.QAAL2.Est.RLC.Rx
WRFD-05030104


3681
BSC6900 UMTS
Number of AAL2 Connection Establishment Confirmations Received by the

QAAL2
Counters
Counter ID
Counter Name
Counter Description
67183364
VS.QAAL2.Est.ECF.Rx
Number of ECF Messages

ERQ Message
Description
the ERQ message to the peer NE. This counter provides the number of ECF messages that the
QAAL2 receives from the peer NE after sending the ERQ message to the peer NE.
Measurement point
is incremented by one each time the base station controller receives the ECF message from the
peer NE (NodeB shown in the figure) after sending the AAL2 ERQ message to the peer NE.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3682
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.Est.ECF.Rx
WRFD-05030104

Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67183365
VS.QAAL2.Est.ECF.Tx

Sent by the QAAL2 After the
QAAL2 Receives the ERQ
Message
Description
peer NE. This counter provides the number of ECF messages that the QAAL2 sends to the peer
NE after receiving the ERQ message from the peer NE.
Measurement point
is incremented by one each time the local RNC sends the ECF message to the peer NE (other
RNC shown in the figure) after receiving the AAL2 ERQ message from the peer NE.
Formula
None
Issue 03 (2015-06-30)

3683
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.Est.ECF.Tx
WRFD-05030104

Number of AAL2 Connection Establishment Rejections Sent by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67183366
VS.QAAL2.Est.RLC.Tx

QAAL2 Receives the ERQ
Message
Description
peer NE. This counter provides the number of RLC messages that the QAAL2 sends to the peer
NE after receiving the ERQ message from the peer NE.
Measurement point
is incremented by one each time the local RNC sends the RLC message to the peer NE (other
RNC shown in the figure) after receiving the AAL2 ERQ message from the peer NE.
Figure 2-11 Failed AAL2 connection establishment procedure initiated by an adjacent node
Issue 03 (2015-06-30)

3684
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.Est.RLC.Tx
WRFD-05030104

Number of AAL2 Connection Releases Initiated by QAAL2

Counters
Counter ID
Counter Name
Counter Description
67183367
VS.QAAL2.Rel.Tx
Number of AAL2
Connection Release
Requests (RELs) Sent by the
QAAL2
Description
When the network actively releases UEs using ATM transmission, the base station controller
sends the REL message to the peer NE. This counter provides the number of REL messages that
the QAAL2 sends to the peer NE.
Measurement point
is incremented by one each time the base station controller sends the AAL2 REL message to the
peer NE (NodeB shown in the figure).
Figure 2-12 AAL2 connection release procedure initiated by the RNC
Issue 03 (2015-06-30)

3685
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.Rel.Tx
WRFD-05030104

Number of AAL2 Connection Releases Received by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67183368
VS.QAAL2.Rel.Rx
Number of AAL2
Connection Release
Requests (RELs) Received
by the QAAL2
Description
This counter provides the number of REL messages that the base station controller receives from
the peer NE.
Measurement point
is incremented by one each time the base station controller receives the AAL2 REL message
from the peer NE (NodeB shown in the figure).
Figure 2-13 AAL2 connection release procedure initiated by an adjacent node
Issue 03 (2015-06-30)

3686
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.Rel.Rx
WRFD-05030104

Number of AAL2 Connection Confirmations Received by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67183369
VS.QAAL2.Rel.RLC.Rx
Number of AAL2
Connection Release
Confirmations (RLCs)
REL Message
Description
When the network actively releases UEs using ATM transmission, the base station controller
sends the REL message to the peer NE. This counter provides the number of RLC messages that
the base station controller receives from the peer NE after sending the REL message to the peer
NE.
Measurement point
peer NE (NodeB shown in the figure) after sending the AAL2 REL message to the peer NE.
Issue 03 (2015-06-30)

3687
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.Rel.RLC.Rx
WRFD-05030104

Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67183370
VS.QAAL2.Rel.RLC.Tx

QAAL2 Receives the REL
Message
Description
This counter provides the number of RLC messages that the base station controller sends to the
peer NE after receiving the REL message from the peer NE.
Issue 03 (2015-06-30)

3688
BSC6900 UMTS
Measurement point
is incremented by one each time the base station controller sends the RLC message to the peer
NE (NodeB shown in the figure) after receiving the AAL2 REL message from the peer NE.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.Rel.RLC.Tx
WRFD-05030104

Number of AAL2 Connection Modification Request Rejections Received by the

QAAL2
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190067
VS.QAAL2.RxModRej
Number of AAL2
Connection Modification
Rejections (MORs)

3689
BSC6900 UMTS
Description
When the rate of services using ATM transmission on the network needs to be adjusted, the base
station controller sends the MOD message to the peer NE. This counter provides the number of
MOR messages that the QAAL2 receives from the peer NE after sending the MOD message to
the peer NE.
Measurement point
is incremented by one each time the base station controller receives the MOR message from the
peer NE (NodeB shown in the figure) after sending the AAL2 MOD message to the peer NE.
Figure 2-16 Failed AAL2 connection modification procedure initiated by the RNC
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.QAAL2.RxModRej
WRFD-05030104


3690
BSC6900 UMTS
Number of AAL2 Connection Modification Rejections Sent by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67190068
VS.QAAL2.TxModRej
Number of MOR Messages

QAAL2 Receives the MOD
Message
Description
This counter provides the number of MOR messages that the QAAL2 sends to the peer NE after
receiving the MOD message from the peer NE.
Measurement point
is incremented by one each time the base station controller sends the MOR message to the peer
NE (other RNC shown in the figure) after receiving the AAL2 MOD message from the peer NE.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3691
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.TxModRej
WRFD-05030104

Number of AAL2 Connection Modification Requests Sent by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67190553
VS.QAAL2.TxMod
Number of AAL2
Requests (MODs) Sent by
the QAAL2
Description
When the rate of services using ATM transmission on the network needs to be adjusted, the base
station controller sends the MOD message to the peer NE. This counter provides the number of
MOD messages that the QAAL2 sends to the peer NE.
Measurement point
In a measurement period, this counter is incremented by one each time the base station controller
sends the MOD message to the peer NE.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.QAAL2.TxMod
WRFD-05030104


3692
BSC6900 UMTS
Number of AAL2 Connection Modification Requests Received by the QAAL2

Counters
Counter ID
Counter Name
Counter Description
67190554
VS.QAAL2.RxMod
Number of AAL2
Requests (MODs) Received
by the QAAL2
Description
This counter provides the number of MOD messages that the QAAL2 receives from the peer
NE.
Measurement point
receives the AAL2 MOD message from the peer NE.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.RxMod
WRFD-05030104

Average Number of Active AAL2 Connections to an QAAL2 Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67199677
VS.QAAL2.Act.Con

Connections to an QAAL2
Adjacent Node

3693
BSC6900 UMTS
Description
This counter provides the average number of active AAL2 connections to a QAAL2 adjacent
node in a specified measurement period and reflects the number of online UEs under a QAAL2
node. If the number of active AAL2 connections increases, the number of online UEs carried
on the adjacent node increases.
Measurement point
In a measurement period, the system samples the number of active AAL2 connections to an
adjacent node every 15s. At the end of the measurement period, the system automatically divides
the accumulated number of active AAL2 connections to an adjacent node by the sampling times
to obtain the value of this counter.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2.Act.Con
WRFD-05030104

AAL2 Path Bandwidth Allocated to an Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190555
VS.QAAL2.AllocedFwd.A
AL2BitRate
Mean Forward Bandwidth of

AAL2 Path Allocated to an
Adjacent Node
67190558
VS.QAAL2.AllocedBwd.A
AL2BitRate
Mean Backward Bandwidth

of AAL2 Path Allocated to an
Adjacent Node
67190562
VS.QAAL2.AllocedMaxFw
d.AAL2BitRate.Value
Maximum Value of AAL2

Path Forward Bandwidth
Allocated to an Adjacent
Node

3694
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67190565
VS.QAAL2.AllocedMaxBw
d.AAL2BitRate.Value
Maximum Value of AAL2

Path Backward Bandwidth
Allocated to an Adjacent
Node
Description
When services using ATM transmission access the network, bandwidth admission needs to be
performed on AAL2 paths. These counters provide the average or maximum forward/backward
bandwidth allocated to an AAL2 path on an interface adjacent node (Iub, Iur, or Iu) in a
measurement period.
Measurement point
In a measurement period, the system automatically samples the forward or backward bandwidth
allocated to an AAL2 path on the interface adjacent node (Iub, Iur, or Iu) every 15s. At the end
of the measurement period, the system divides the sum of the allocated forward or backward
bandwidth of the AAL2 path by the sampling times to obtain the average value or uses the
maximum sampled value as the maximum value.
Formula
None
Unit
bit
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.QAAL2.AllocedFwd.A
AL2BitRate
WRFD-05030106

VS.QAAL2.AllocedBwd.A
AL2BitRate
WRFD-05030106

VS.QAAL2.AllocedMaxFw
d.AAL2BitRate.Value
WRFD-05030106

VS.QAAL2.AllocedMaxBw
d.AAL2BitRate.Value
WRFD-05030106


3695
BSC6900 UMTS
2.6 Measurement of Dual-Stack Transport Adjacent Node

Performance(ANI_QAAL2_IP)
Overview
An adjacent node is used to identify a logical node of network equipment adjacent to the base
station controller. A dual-stack adjacent node is an ATM/IP dual-stack transmission link and
used to carry both of adjacent nodes using ATM and IP transmission modes. Measurement of
Dual-Stack Transport Adjacent Node Performance indicates transmission performance of a dualstack adjacent node.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IPPART
Dual-Stack Transport Adjacent Node IP Part

Measurement
QAAL2IP
Dual-Stack Transport Adjacent Node

Measurement
QAAL2PART

QAAL2 Part Measurement
2.6.1 Dual-Stack Transport Adjacent Node IP Part Measurement

(IPPART)
Overview
Dual-Stack Transport Adjacent Node IP Part Measurement is used to measure the attribute of
IP link establishment and resource allocation on a dual-stack adjacent node and analyze IP
transmission quality over the Iub interface in dual-stack configuration to ensure system stability
and reliability.
Issue 03 (2015-06-30)

3696
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194658
VS.IPPART.Node.
Conn.Estab.Att
Number of
Connection Setup
Requests for IP
Transport from the
Transport Layer to
the Radio Network
Layer on the DualStack Transport
Adjacent Node
Earlier than
BSC6900
V900R011
67194659
VS.IPPART.Node.
Conn.Estab.Succ
Number of
Successful IP
Connection Setups
Initiated by the
Transport Layer on
the Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67194660
VS.IPPART.Node.
Conn.Modify.Att
Number of IP
Connection
Modifications on the
Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67192414
VS.IPPART.Node.
Conn.Modify.Succ
Number of
Successful IP
Connection
Modifications
Initiated by the
Transport Layer on
the Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67192415
VS.IPPART.Node.
Conn.Rel
Number of IP
Connection Release
Requests Sent from
the Radio Network
Layer to the
Transport Layer on
the Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011

3697
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204200
VS.IPPART.Node.
Act.Con
Mean Number of
Active IP
Connections to a
Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67204201
VS.IPPART.AllocedFwd
Forward Bandwidth
of IP Path Allocated
to a Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67204202
VS.IPPART.AllocedBwd
Backward
Bandwidth of IP Path
Allocated to a DualStack Transport
Adjacent Node
Earlier than
BSC6900
V900R011
None
Number of IP Connection Setup Requests Received on Dual-Stack Transport

Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67194658
VS.IPPART.Node.Conn.Est
ab.Att
Number of Connection Setup

Requests for IP Transport
from the Transport Layer to
the Radio Network Layer on
the Dual-Stack Transport
Adjacent Node
Description
This counter takes effect only if ATM/IP dual-stack transmission links are configured on the
network. This counter provides the number of IP link setup requests that the transport layer
receives from the dual-stack adjacent node on the radio layer in a specified measurement period.
Issue 03 (2015-06-30)

3698
BSC6900 UMTS
Measurement point
receives an IP link setup request from the dual-stack adjacent node on the radio layer.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ab.Att
WRFD-050404
ATM/IP Dual Stack Node B
Number of Successful IP Connection Setups on the Dual-Stack Transport Adjacent

Node
Counters
Counter ID
Counter Name
Counter Description
67194659
ab.Succ
Number of Successful IP
Connection Setups Initiated
by the Transport Layer on the
Dual-Stack Transport
Adjacent Node
Description
network. This counter provides the number of successful IP connection setups on the dual-stack
adjacent node initiated by the transport layer in a specified measurement period.
Measurement point
successfully sets up an IP connection to the dual-stack adjacent node.
Formula
None
Issue 03 (2015-06-30)

3699
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
ab.Succ
WRFD-050404
Number of IP Connection Modifications on the Dual-Stack Transport Adjacent

Node
Counters
Counter ID
Counter Name
Counter Description
67194660
VS.IPPART.Node.Conn.Mo
dify.Att
Number of IP Connection
Modifications on the DualStack Transport Adjacent
Node
Description
network. When the service rate on the network needs to be adjusted, the radio layer sends a
connection modification request to the transport layer. This counter provides the number of IP
connection modification requests that the transport layer receives from the dual-stack adjacent
node on the radio layer in a specified measurement period.
Measurement point
receives an IP connection modification request from the dual-stack adjacent node on the radio
layer.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3700
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
dify.Att
WRFD-050404
Number of Successful IP Connection Modifications on the Dual-Stack Transport

Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67192414
dify.Succ
Number of Successful IP
Connection Modifications
Initiated by the Transport
Layer on the Dual-Stack
Description
network. When the service rate of the network needs to be adjusted, the radio layer sends a
connection modification request to the transport layer. This counter provides the number of
successful IP connection modifications on the dual-stack adjacent node initiated by the transport
Measurement point
successfully modifies an IP connection to a dual-stack adjacent node after receiving the IP
connection modification request.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3701
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
dify.Succ
WRFD-050404
Number of IP Connection Releases on the Dual-Stack Transport Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67192415
VS.IPPART.Node.Conn.Rel
Number of IP Connection
Release Requests Sent from
the Radio Network Layer to
the Transport Layer on the
Adjacent Node
Description
network. This counter provides the number of IP connection release requests that the transport
layer receives from the dual-stack adjacent node on the radio layer in a specified measurement
period.
Measurement point
receives an IP connection release request from the dual-stack adjacent node on the radio layer.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPPART.Node.Conn.Rel
WRFD-050404

3702
BSC6900 UMTS
Number of Active IP Connections on the Dual-Stack Transport Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67204200
VS.IPPART.Node.Act.Con
Mean Number of Active IP

Connections to a Dual-Stack
Description
network. This counter provides the number of active IP connections to a dual-stack adjacent
node in a specified measurement period. If the number of active IP connections increases, the
number of online UEs carried on the dual-stack adjacent node increases.
Measurement point
In a measurement period, the system automatically samples the number of active IP connections
to a dual-stack adjacent node every 15s. At the end of the measurement period, the system divides
the accumulated value by the sampling times to obtain the value of this counter.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPART.Node.Act.Con
WRFD-050404
IP Path Forward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204201
Forward Bandwidth of IP
Path Allocated to a DualStack Transport Adjacent
Node

3703
BSC6900 UMTS
Description
network. In non-transmission-pool networking, this counter provides the IP path forward
bandwidth (admitted bandwidth) allocated to a dual-stack adjacent node, that is, the average
forward bandwidth obtained from all sampling points in a measurement period. In transmission
pool networking, this counter provides the forward bandwidth (admitted bandwidth) allocated
to a dual-stack adjacent node in a specified measurement period, that is, the average forward
bandwidth obtained from all sampling points in a measurement period.
Measurement point
In non-transmission-pool networking, the system automatically samples the forward bandwidth
allocated to an IP path on the Iub adjacent node every 15s in a measurement period. At the end
of the measurement period, the system divides the accumulated forward bandwidth by the
sampling times to obtain the value of this counter. In transmission pool networking, the system
automatically samples the forward bandwidth allocated to an IP path on the Iub interface adjacent
node every 15s in a measurement period. At the end of the measurement period, the system
divides the accumulated forward bandwidth by the sampling times to obtain the value of this
counter.
Formula
None
Unit
bit/s
Related Features
Counter Name
Feature ID
Feature Name
WRFD-050404
IP Path Backward Bandwidth Allocated to a Dual-Stack Transport Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204202
Backward Bandwidth of IP
Path Allocated to a DualStack Transport Adjacent
Node

3704
BSC6900 UMTS
Description
network. In non-transmission-pool networking, this counter provides the IP path backward
bandwidth (admitted bandwidth) allocated to a dual-stack adjacent node, that is, the average
forward bandwidth obtained from all sampling points in a measurement period. In transmission
pool networking, this counter provides the backward bandwidth (admitted bandwidth) allocated
to a dual-stack adjacent node in a specified measurement period, that is, the average backward
bandwidth obtained from all sampling points in a measurement period.
Measurement point
In non-transmission-pool networking, the system automatically samples the backward
bandwidth allocated to the Iub adjacent node every 15s in a measurement period. At the end of
the measurement period, the system divides the accumulated backward bandwidth by the
sampling times to obtain the value of this counter. In transmission pool networking, the system
automatically samples the backward bandwidth allocated to the Iub adjacent node every 15s in
a measurement period. At the end of the measurement period, the system divides the accumulated
backward bandwidth by the sampling times to obtain the value of this counter.
Formula
None
Unit
bit/s
Related Features
Counter Name
Feature ID
Feature Name
WRFD-050404
2.6.2 Dual-Stack Transport Adjacent Node Measurement

(QAAL2IP)
Overview
Dual-Stack Transport Adjacent Node Measurement is used to measure the QAAL2 and IP
connections and resource allocations on a dual-stack adjacent node and analyze transmission
quality to ensure system stability and reliability.
Issue 03 (2015-06-30)

3705
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67192422
VS.QAAL2IP.AttResAlloc
Number of Resource
Requests Sent from
the Radio Network
Layer to the
Transport Layer on
Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67192423
VS.QAAL2IP.SuccResAlloc
Number of
Successful Resource
Allocations After the
Transport Layer
Receives the
Resource Requests
from the Radio
Network Layer on
Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67196160
VS.QAAL2IP.FailResAllocForBwLimit
Number of Failed
Resource
Allocations Due to
Insufficient
Bandwidth on the
Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

3706
BSC6900 UMTS
Number of Requests for Resource Allocations by Dual-Stack Transport Adjacent

Node
Counters
Counter ID
Counter Name
Counter Description
67192422
Number of Resource
Requests Sent from the Radio
Network Layer to the
Transport Layer on DualStack Transport Adjacent
Node
Description
network. This counter provides the number of resource application requests that the transport
layer receives from the radio layer in a specified measurement period.
Measurement point
receives a resource application request for a dual-stack adjacent node from the radio layer
(RNCAP and NBAP).
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050404

3707
BSC6900 UMTS
Number of Successful Resource Allocations to Dual-Stack Transport Adjacent

Node
Counters
Counter ID
Counter Name
Counter Description
67192423
Resource Allocations After
the Transport Layer Receives
the Resource Requests from
the Radio Network Layer on
Adjacent Node
Description
network. This counter provides the number of successful resource applications after the transport
layer receives the resource application requests from the radio layer in a specified measurement
period.
Measurement point
receives a resource application request for a dual-stack adjacent node from the radio layer
(RNCAP and NBAP) and the resource application is successful.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050404

3708
BSC6900 UMTS
Number of Failed Resource Allocations Due to Insufficient Bandwidth on the

Counters
Counter ID
Counter Name
Counter Description
67196160
Number of Failed Resource

Allocations Due to
Insufficient Bandwidth on
the Dual-Stack Transport
Adjacent Node
Description
network. When services access the network, the radio layer sends a transmission resource
application request to the transport layer. If transmission resources are insufficient, the transport
layer sends a resource application failure message to the radio layer. This counter provides the
number of failed resource applications due to insufficient bandwidth in a specified measurement
period.
Measurement point
In a measurement period, this counter is incremented by one each time the resource application
fails due to insufficient bandwidth after the radio layer sends a resource application request for
a dual-stack adjacent node to the transport layer.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050404

3709
BSC6900 UMTS
2.6.3 Dual-Stack Transport Adjacent Node QAAL2 Part

Measurement(QAAL2PART)
Overview
Dual-Stack Transport Adjacent Node QAAL2 Part Measurement is used to measure the QAAL2
and IP connections and resource allocations on a dual-stack adjacent node. It helps analyze
transmission quality of the system to ensure system stability and reliability.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192424
VS.QAAL2PART.
Est.RLC.NoRoute.
Rx
Number of AAL2
Connection Release
Confirmations
Received by QAAL2
on Dual-Stack
Adjacent Node Due
to No Route at the
Remote End
Earlier than
BSC6900
V900R011
67192425
VS.QAAL2PART.
Est.RLC.NoPath.R
x
Number of AAL2
Connection Release
Confirmations
Received by QAAL2
on Dual-Stack
Adjacent Node Due
to No Path path
Configured at the
Remote End
Earlier than
BSC6900
V900R011
67194611
VS.QAAL2PART.
Est.RLC.NoCID.R
x
Number of AAL2
Connection Release
Confirmations
Received by QAAL2
on Dual-Stack
Adjacent Node Due
to No CID Available
at the Remote End
Earlier than
BSC6900
V900R011

3710
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194612
VS.QAAL2PART.
Est.RLC.Fail.Rx
Number of AAL2
Connection Release
Confirmations
Received by QAAL2
on Dual-Stack
Adjacent Node Due
to Remote Network
Fault, Remote
Temporary Failure,
or Remote Normal
Releases
Earlier than
BSC6900
V900R011
67194661
VS.QAAL2PART.
Est.RLC.Cong.Rx
Number of AAL2
Connection Release
Confirmations
Received by QAAL2
on Dual-Stack
Adjacent Node Due
to Switch Congestion
at the Remote End
Earlier than
BSC6900
V900R011
67194662
VS.QAAL2PART.
Est.RLC.RecovOut
.Rx
Number of AAL2
Connection Release
Confirmations
Received by QAAL2
on Dual-Stack
Adjacent Node Due
to Timer Expiry at
the Remote End
Earlier than
BSC6900
V900R011
67194663
VS.QAAL2PART.
Est.RLC.NoRoute.
Tx
Number of AAL2
Connection Release
Confirmations Sent
by QAAL2 on DualStack Adjacent Node
Due to No Route
Earlier than
BSC6900
V900R011
67194664
VS.QAAL2PART.
Est.RLC.NoPath.T
x
Number of AAL2
Connection Release
Confirmations Sent
Due to No Path
Configured
Earlier than
BSC6900
V900R011

3711
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194665
VS.QAAL2PART.
Est.RLC.NoCID.T
x
Number of AAL2
Connection Release
Confirmations Sent
Due to No CID
Available
Earlier than
BSC6900
V900R011
67194666
VS.QAAL2PART.
Est.RLC.Fail.Tx
Number of AAL2
Connection Release
Confirmations Sent
Due to Network
Failure, Unspecified
Reason, or
Temporary Failure
Earlier than
BSC6900
V900R011
67194626
VS.QAAL2PART.
Est.RLC.Cong.Tx
Number of AAL2
Connection Release
Confirmations Sent
Due to Switch
Congestion
Earlier than
BSC6900
V900R011
67194627
VS.QAAL2PART.
Est.RLC.RecovOut
.Tx
Number of AAL2
Connection Release
Confirmations Sent
Due to Timer Expiry
Earlier than
BSC6900
V900R011
67194628
VS.QAAL2PART.
ERQ.Tx
Number of
Connection
Establishment
Request (ERQ)
Messages Sent by
QAAL2 on DualStack Adjacent Node
Earlier than
BSC6900
V900R011
67194629
VS.QAAL2PART.
ERQ.Rx
Number of
Connection
Establishment
Requests Received
by QAAL2 on the
Dual-Stack Adjacent
Node
Earlier than
BSC6900
V900R011

3712
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194630
VS.QAAL2PART.
Est.RLC.Rx
Number of RLC
Messages Received
After the QAAL2
Sends the
Connection ERQ
Messages
Earlier than
BSC6900
V900R011
67194631
VS.QAAL2PART.
Est.ECF.Rx
Number of ECF
Messages Received
After the QAAL2
Sends the
Connection ERQ
Messages
Earlier than
BSC6900
V900R011
67194620
VS.QAAL2PART.
Est.ECF.Tx
Number of
Connection ECF
Messages Sent by
After the QAAL2
Receives the
Connection ERQ
Message
Earlier than
BSC6900
V900R011
67194621
VS.QAAL2PART.
Est.RLC.Tx
Number of RLC
Messages Sent by
After the QAAL2
Receives the
Connection ERQ
Message
Earlier than
BSC6900
V900R011
67194622
VS.QAAL2PART.
Rel.Tx
Number of
Connection Release
(REL) Messages
Sent by QAAL2 on
Dual-Stack Adjacent
Node
Earlier than
BSC6900
V900R011
67194623
VS.QAAL2PART.
Rel.Rx
Number of
Connection REL
Messages Received
Earlier than
BSC6900
V900R011

3713
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194632
VS.QAAL2PART.
Rel.RLC.Rx
Number of RLC
Messages Received
After the QAAL2
Sends REL
Messages
Earlier than
BSC6900
V900R011
67194633
VS.QAAL2PART.
Rel.RLC.Tx
Number of RLC
Messages Sent by
QAAL2 on the DualStack Adjacent Node
After the QAAL2
Receives Connection
REL Messages
Earlier than
BSC6900
V900R011
67192446
VS.QAAL2PART.
RxModRej
Number of
Modification
Rejection (MOR)
Messages Received
After the QAAL2
Sends Connection
Modification
Request (MOD)
Messages
Earlier than
BSC6900
V900R011
67192447
VS.QAAL2PART.
TxModRej
Number of MOR
Messages Sent by
QAAL2 on the DualStack Adjacent Node
After the QAAL2
Receives Connection
MOD Messages
Earlier than
BSC6900
V900R011
67192448
VS.QAAL2PART.
TxMod
Number of MOD
Messages Sent by
Earlier than
BSC6900
V900R011
67192449
VS.QAAL2PART.
RxMod
Number of MOD
Messages Received
Earlier than
BSC6900
V900R011

3714
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204203
VS.QAAL2PART.
Act.Con
Number of Active
AAL2 Connections
to a Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67204204
VS.QAAL2PART.
AllocedFwd.AAL2
BitRate
Mean Forward
Bandwidth of AAL2
Path Allocated to a
Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67204205
VS.QAAL2PART.
AllocedBwd.AAL2
BitRate
Mean Backward
Bandwidth of AAL2
Path Allocated to a
Dual-Stack
Transport Adjacent
Node
Earlier than
BSC6900
V900R011
67196185
VS.QAAL2PART.
Est.RLC.NoBitRat
e.Tx
Number of AAL2
Connection Release
Confirmations Sent
Due to No
Bandwidth
Earlier than
BSC6900
V900R011
None
Number of RLC messages received by the QAAL2 on Dual-Stack Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192424
VS.QAAL2PART.Est.RLC.
NoRoute.Rx
Number of AAL2
Connection Release
Confirmations Received by
QAAL2 on Dual-Stack
Adjacent Node Due to No
Route at the Remote End

3715
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67192425
NoPath.Rx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Path path Configured at the
Remote End
67194611
NoCID.Rx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
CID Available at the Remote
End
67194612
Fail.Rx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Adjacent Node Due to
Remote Network Fault,
Remote Temporary Failure,
or Remote Normal Releases
67194661
Cong.Rx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Switch Congestion at the
Remote End
67194662
RecovOut.Rx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Adjacent Node Due to Timer
Expiry at the Remote End
Description
These counters take effect only if ATM/IP dual-stack transmission links are configured on the
network. These counters provide the number of AAL2 RLC messages that the QAAL2 receives
from an adjacent node in a specified measurement period.
Issue 03 (2015-06-30)

3716
BSC6900 UMTS
Measurement point
In a measurement period, these counters are measured when the base station controller receives
the RLC message from the adjacent node due to various reasons after sending an ERQ message
to the adjacent node.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
NoRoute.Rx
WRFD-050404
NoPath.Rx
WRFD-050404
NoCID.Rx
WRFD-050404
Fail.Rx
WRFD-05030104

Cong.Rx
WRFD-050404
RecovOut.Rx
WRFD-050404
Number of RLC messages sent by the QAAL2 on Dual-Stack Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194663
NoRoute.Tx
Number of AAL2
Connection Release
Confirmations Sent by
QAAL2 on Dual-Stack
Route

3717
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194664
NoPath.Tx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Path Configured
67194665
NoCID.Tx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
CID Available
67194666
Fail.Tx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Network Failure,
Unspecified Reason, or
Temporary Failure
67194626
Cong.Tx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Switch Congestion
67194627
RecovOut.Tx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Adjacent Node Due to Timer
Expiry
67196185
NoBitRate.Tx
Number of AAL2
Connection Release
QAAL2 on Dual-Stack
Bandwidth
Description
network. These counters provide the number of AAL2 RLC messages that the QAAL2 sends to
an adjacent node in a specified measurement period.
Issue 03 (2015-06-30)

3718
BSC6900 UMTS
Measurement point
In a measurement period, when the base station controller sends an ERQ message to the adjacent
node, the adjacent node sends the REL message to the base station controller. When the QAAL2
sends the RLC message to the adjacent node, these counters are measured.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
NoRoute.Tx
WRFD-050404
NoPath.Tx
WRFD-050404
NoCID.Tx
WRFD-050404
Fail.Tx
WRFD-050404
Cong.Tx
WRFD-050404
RecovOut.Tx
WRFD-050404
NoBitRate.Tx
WRFD-050404
Number of AAL2 Connection Establishment Requests Sent by the QAAL2 on DualStack Adjacent Node
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194628
VS.QAAL2PART.ERQ.Tx
Number of Connection
Establishment Request
(ERQ) Messages Sent by
QAAL2 on Dual-Stack
Adjacent Node

3719
BSC6900 UMTS
Description
network. When services using ATM transmission access the network, the base station controller
sends an ERQ message to the peer NE. This counter provides the number of AAL2 ERQ
messages that the base station controller sends to the peer NE in a specified measurement period.
Measurement point
is incremented by one each time the base station controller sends the ERQ message to the peer
NE (NodeB shown in the figure).
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.ERQ.Tx
WRFD-050404

3720
BSC6900 UMTS
Number of AAL2 Connection Establishment Requests Received by the QAAL2 on

the Dual-Stack Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67194629
VS.QAAL2PART.ERQ.Rx
Received by QAAL2 on the
Dual-Stack Adjacent Node
Description
receives an ERQ message from the peer NE. This counter provides the number of ERQ messages
that the QAAL2 receives from the peer NE. In normal situations, AAL2 connections are
passively set up over only the Iur interface. The base station controller actively initiates AAL2
connection setup over the Iub and Iu interfaces.
Measurement point
is incremented by one each time the base station controller receives the ERQ message from the
peer NE (other RNC shown in the figure).
Formula
None
Unit
None
Issue 03 (2015-06-30)

3721
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.ERQ.Rx
WRFD-050404
Number of AAL2 Connection Establishment Request Rejections Received by the

QAAL2 on the Dual-Stack Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67194630
Rx

Received by QAAL2 on
Connection ERQ Messages
Description
sends an ERQ message to the peer NE. This counter provides the number of RLC messages that
the QAAL2 receives from the peer NE after sending ERQ messages to the peer NE.
Measurement point
peer NE (NodeB shown in the figure) after sending the ERQ message to the peer NE.
Figure 2-20 Failed AAL2 connection establishment procedure initiated by the RNC
Issue 03 (2015-06-30)

3722
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Rx
WRFD-050404
Number of AAL2 Connection Establishment Confirmations Received by the

QAAL2 on Dual-Stack Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67194631
VS.QAAL2PART.Est.ECF.
Rx

Connection ERQ Messages
Description
sends an ERQ message to the peer NE. This counter provides the number of ECF messages that
the QAAL2 receives from the peer NE after sending ERQ messages to the peer NE.
Measurement point
is incremented by one each time the base station controller receives the ECF message from the
peer NE (NodeB shown in the figure) after sending the ERQ message to the peer NE.
Issue 03 (2015-06-30)

3723
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Rx
WRFD-050404
Number of AAL2 Connection Establishment Confirmations Sent by the QAAL2 on

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194620
Tx
Number of Connection ECF

Messages Sent by QAAL2 on
After the QAAL2 Receives
the Connection ERQ
Message

3724
BSC6900 UMTS
Description
receives an ERQ message from the peer NE. This counter provides the number of ECF messages
that the QAAL2 sends to the peer NE after receiving the ERQ message from the peer NE.
Measurement point
is incremented by one each time the base station controller sends the ECF message to the peer
NE (other RNC shown in the figure) after receiving the ERQ message from the peer NE.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Tx
WRFD-050404

3725
BSC6900 UMTS
Number of RLC Messages Sent by QAAL2 on Dual-Stack Adjacent Node after the
QAAL2 Receives the Connection ERQ Message
Counters
Counter ID
Counter Name
Counter Description
67194621
Tx

Sent by QAAL2 on DualStack Adjacent Node After
the QAAL2 Receives the
Connection ERQ Message
Description
receives an ERQ message from the peer NE. This counter provides the number of RLC messages
that the QAAL2 sends to the peer NE after receiving the ERQ message from the peer NE.
Measurement point
NE (other RNC shown in the figure) after receiving the ERQ message from the peer NE.
Figure 2-23 Failed AAL2 connection establishment procedure initiated by an adjacent node
Formula
None
Unit
None
Issue 03 (2015-06-30)

3726
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
Tx
WRFD-050404
Number of AAL2 Connection Releases Initiated by QAAL2 on Dual-Stack

Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67194622
VS.QAAL2PART.Rel.Tx
Release (REL) Messages
Sent by QAAL2 on DualStack Adjacent Node
Description
network. When the network actively releases UEs using ATM transmission, the base station
controller sends the REL message to the peer NE. This counter provides the number of REL
messages that the QAAL2 sends to the peer NE.
Measurement point
is incremented by one each time the base station controller sends the REL message to the peer
NE (NodeB shown in the figure).
Issue 03 (2015-06-30)

3727
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.Rel.Tx
WRFD-050404
Number of AAL2 Connection Releases Received by the QAAL2 on Dual-Stack

Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67194623
VS.QAAL2PART.Rel.Rx
Number of Connection REL

Messages Received by
QAAL2 on Dual-Stack
Adjacent Node
Description
controller sends the REL message to the peer NE. This counter provides the number of REL
messages received by the QAAL2 when the peer NE initiates a connection release.
Measurement point
is incremented by one each time the base station controller receives the REL message from the
peer NE (NodeB shown in the figure).
Issue 03 (2015-06-30)

3728
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.Rel.Rx
WRFD-050404
Number of AAL2 Connection Confirmations Received by the QAAL2 on DualStack Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67194632
VS.QAAL2PART.Rel.RLC.
Rx

After the QAAL2 Sends REL
Messages
Description
controller sends the RLC message to the peer NE. This counter provides the number of RLC
messages received by the QAAL2 when the peer NE initiates a connection release.
Measurement point
peer NE (NodeB shown in the figure) after sending the REL message to the peer NE.
Issue 03 (2015-06-30)

3729
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
Rx
WRFD-050404
Number of AAL2 Connection Releases Confirmation Initiated by the QAAL2 on

the Dual-Stack Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67194633
Tx

Sent by QAAL2 on the DualStack Adjacent Node After
the QAAL2 Receives
Connection REL Messages
Description
network. When the peer NE actively releases UEs using ATM transmission, the base station
Issue 03 (2015-06-30)

3730
BSC6900 UMTS
controller sends the REL message to the peer NE. This counter provides the number of RLC
messages that the QAAL2 sends to the peer NE after receiving REL messages from the peer
NE.
Measurement point
NE (NodeB shown in the figure) after receiving the REL message from the peer NE.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Tx
WRFD-050404

3731
BSC6900 UMTS
Number of AAL2 Connection Modification Request Rejections Received by the

QAAL2 on the Dual-Stack Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67192446
VS.QAAL2PART.RxModRej
Number of Modification
Rejection (MOR) Messages
After the QAAL2 Sends
Request (MOD) Messages
Description
network. When the rate of the service using ATM transmission on the network needs to be
adjusted, the base station controller sends the MOD message to the peer NE. This counter
provides the number of MOR messages that the QAAL2 receives from the peer NE after sending
MOD messages to the peer NE.
Measurement point
is incremented by one each time the base station controller receives the MOR message from the
peer NE (NodeB shown in the figure) after sending the MOD message to the peer NE.
Formula
None
Issue 03 (2015-06-30)

3732
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.RxModRej
WRFD-050404
Number of AAL2 Connection Modification Rejections Sent by the QAAL2 on

Counters
Counter ID
Counter Name
Counter Description
67192447
VS.QAAL2PART.TxModRej
Number of MOR Messages

Sent by QAAL2 on the DualStack Adjacent Node After
the QAAL2 Receives
Connection MOD Messages
Description
network. When adjusting the rate of the service using ATM transmission, the peer NE sends the
MOD message to the base station controller. This counter provides the number of MOR messages
that the QAAL2 sends to the peer NE after receiving MOD messages from the peer NE.
Measurement point
is incremented by one each time the base station controller sends the MOR message to the peer
NE (other RNC shown in the figure) after receiving the MOD message from the peer NE.
Issue 03 (2015-06-30)

3733
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.TxModRej
WRFD-050404
Number of AAL2 Connection Modification Requests Sent by the QAAL2 on DualStack Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67192448
VS.QAAL2PART.TxMod
Number of MOD Messages

Sent by QAAL2 on DualStack Adjacent Node
Description
network. When the rate of the service using ATM transmission on the network needs to be
adjusted, the base station controller sends the MOD message to the peer NE. This counter
provides the number of MOD messages that the QAAL2 sends to the peer NE.
Measurement point
sends the MOD message to the peer NE.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3734
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.TxMod
WRFD-050404
Number of AAL2 Connection Modification Requests Received by the QAAL2 on

Counters
Counter ID
Counter Name
Counter Description
67192449
VS.QAAL2PART.RxMod
Number of MOD Messages

Description
network. When adjusting the rate of the service using ATM transmission, the peer NE sends the
MOD message to the base station controller. This counter provides the number of MOD
messages that the QAAL2 receives from the peer NE.
Measurement point
receives the MOD message from the peer NE.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.RxMod
WRFD-050404

3735
BSC6900 UMTS
Average Number of QAAL2 Connections to Dual-Stack Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
67204203
VS.QAAL2PART.Act.Con

Connections to a Dual-Stack
Description
network. This counter provides the average number of active AAL2 connections to a dual-stack
adjacent node in a specified measurement period. It reflects the number of online UEs using
ATM transmission on a dual-stack adjacent node. If the number of active AAL2 connections
increases, the number of online UEs using ATM transmission on the adjacent node increases.
Measurement point
In a measurement period, the system samples the number of active AAL2 connections to an
adjacent node every 15s. At the end of the measurement period, the system divides the
accumulated value by the sampling times to obtain the value of this counter.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.Act.Con
WRFD-050404

3736
BSC6900 UMTS
Counters Related to Average QAAL2 Bandwidth Allocated to Iub Adjacent Node

on Dual-Stack Adjacent Node
Counters
Counter ID
Counter Name
Counter Description
67204204
VS.QAAL2PART.AllocedF
wd.AAL2BitRate
Mean Forward Bandwidth of

AAL2 Path Allocated to a
Adjacent Node
67204205
VS.QAAL2PART.AllocedB
wd.AAL2BitRate

of AAL2 Path Allocated to a
Adjacent Node
Description
network. When services using ATM transmission access the network, bandwidth admission
needs to be performed on AAL2 paths. These counters provide the average forward or backward
bandwidth of an AAL2 path allocated to a dual-stack adjacent node (Iub interface), that is, the
average forward or backward bandwidth obtained from all sampling points in a measurement
period.
Measurement point
of an AAL2 path allocated to a dual-stack adjacent node (Iub interface) every 15s. At the end
of the measurement period, the system divides the accumulated value by the sampling times to
obtain the values of these counters.
Formula
None
Unit
bit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.AllocedF
wd.AAL2BitRate
WRFD-050404

3737
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.QAAL2PART.AllocedB
wd.AAL2BitRate
WRFD-050404
2.7 Measurement of ATM Logical Port Performance

(ATM_LOGIC_PORT)
Overview
Logical port is a virtual port configured on a physical port. It provides the traffic shaping and
user-plane data flow control backpressure functions. Measurement of ATM Logical Port
Performance is used to measure performance of ATM logical ports on the AEU, AOU, and UOI
boards and indicates transmission quality of ATM logical ports.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
ATM.LOGIC.PORT
ATM Logical Port Measurement
2.7.1 ATM Logical Port Measurement(ATM.LOGIC.PORT)

Overview
ATM Logical Port Measurement is used to measure and collect statistics on performance of
ATM logical ports during system operation and helps analyze system transmission quality to
maintain system stability and reliability.
Issue 03 (2015-06-30)

3738
BSC6900 UMTS
Figure 2-30 Physical bearer of the ATM Logic Port
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204859
VS.ATMLGCPRT.
Alloced.Ave.Fwd
Mean Forward
Bandwidth Assigned
to the ATM Logical
Port
Earlier than
BSC6900
V900R011
67204858
VS.ATMLGCPRT.
Alloced.Ave.Bwd
Mean Backward
Bandwidth Assigned
to the ATM Logical
Port
Earlier than
BSC6900
V900R011
67196319
VS.ATMLGCPRT.
Alloced.Max.Fwd
Maximum Forward
Bandwidth Assigned
to the ATM Logical
Port
Earlier than
BSC6900
V900R011
67196320
VS.ATMLGCPRT.
Alloced.Max.Bwd
Maximum Backward
Bandwidth Assigned
to the ATM Logical
Port
Earlier than
BSC6900
V900R011

3739
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67196321
VS.ATMLGCPRT.
Fwd.Cong
Number of Forward
Congestions on the
ATM Logical Port
Earlier than
BSC6900
V900R011
67196322
VS.ATMLGCPRT.
Fwd.Cong.Dur
Duration of Forward
Congestions on the
ATM Logical Port
Earlier than
BSC6900
V900R011
67196323
VS.ATMLGCPRT.
Bwd.Cong
Number of
Backward
Congestions on the
ATM Logical Port
Earlier than
BSC6900
V900R011
67196324
VS.ATMLGCPRT.
Bwd.Cong.Dur
Duration of
Backward
Congestions on the
ATM Logical Port
Earlier than
BSC6900
V900R011
None
Counters Related to the Bandwidth Assigned to an ATM Logical Port

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204859
VS.ATMLGCPRT.Alloced.
Ave.Fwd
Mean Forward Bandwidth

Assigned to the ATM
Logical Port
67204858
Ave.Bwd

Assigned to the ATM
Logical Port
67196319
Max.Fwd
Maximum Forward
Bandwidth Assigned to the
ATM Logical Port
67196320
Max.Bwd
Maximum Backward
Bandwidth Assigned to the
ATM Logical Port

3740
BSC6900 UMTS
Description
When services using ATM transmission access the system, bandwidth admission needs to be
performed on ATM logical ports. These counter provide the mean or peak forward and backward
bandwidths allocated to an ATM logical port in a specified measurement period.
Measurement point
In a measurement period, the system samples the forward or backward bandwidth allocated to
an ATM logical port every 15s. At the end of the measurement period, the system divides the
accumulated backward bandwidth by the number of samples to obtain the average forward or
backward bandwidth allocated to an ATM logical port and uses the maximum sampled value as
the peak forward or backward bandwidth allocated to an ATM logical port.
Formula
None
Unit
bit/s
Related Features
Counter Name
Feature ID
Feature Name
Ave.Fwd
WRFD-05030104

Ave.Bwd
WRFD-05030104

Max.Fwd
WRFD-05030104

Max.Bwd
WRFD-05030104

Counters Related to the Number of Congestions on the ATM Logical Port

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196321
VS.ATMLGCPRT.Fwd.Con
g
Number of Forward
Congestions on the ATM
Logical Port

3741
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67196323
VS.ATMLGCPRT.Bwd.Co
ng
Number of Backward
Logical Port
Description
than or equal to the congestion remaining threshold configured for an ATM logical port, traffic
on the ATM logical port is congested. Users can configure the congestion remaining threshold
according to the actual requirements. If the congestion remaining threshold is set to 0, congestion
does not occur. These counters provide the number of forward or backward congestions on an
ATM logical port in a specified measurement period. Service access may be affected if traffic
on many ATM logical ports is congested for a long time. These counters can be used together
with the duration of ATM logical port congestion to observe the congestion.
Measurement point
In a measurement period, these counters are incremented by one each time the system detects
that the status of the ATM logical port changes from non-congestion to forward or backward
congestion.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
g
WRFD-05030104

VS.ATMLGCPRT.Bwd.Co
ng
WRFD-05030104


3742
BSC6900 UMTS
Counters Related to the Duration of Congestions on the ATM Logical Port

Counters
Counter ID
Counter Name
Counter Description
67196322
g.Dur
Duration of Forward
Logical Port
67196324
VS.ATMLGCPRT.Bwd.Co
ng.Dur
Logical Port
Description
than or equal to the congestion remaining threshold configured for an ATM logical port, traffic
on the ATM logical port is congested. Users can configure the congestion remaining threshold
according to the actual requirements. If the congestion remaining threshold is set to 0, congestion
does not occur. These counters provide the duration of forward or backward congestions on an
ATM logical port in a specified measurement period. Service access may be affected if traffic
on many ATM logical ports is congested for a long time. They can be used together with the
number of ATM logical port congestions to observe the congestion.
Measurement point
In a measurement period, the system starts measuring these counters when the forward or
backward congestion occurs on an ATM logical port, that is, the remaining bandwidth available
is less than the congestion threshold and stops measuring these counters when the forward or
backward congestion relieves. The system uses the accumulated values as the values of these
counters.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
g.Dur
WRFD-05030104

VS.ATMLGCPRT.Bwd.Co
ng.Dur
WRFD-05030104


3743
BSC6900 UMTS
2.8 Measurement of Channelized Optical Port Performance

(CHANNELIZED_OPTICAL_PORT)
Overview
Channelized optical interface boards use E1/T1 links to carry upper-layer configurations.
Measurement of Channelized Optical Port Performance indicates the transmission quality of the
optical ports on the AOUa, POUa, AOUc and POUc boards.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
CHANNELIZED.OPTICAL.PORT
Channelized Optical Port Measurement
2.8.1 Channelized Optical Port Measurement

(CHANNELIZED.OPTICAL.PORT)
Overview
Channelized optical ports are important resources of the Base Station Controller. Therefore, the
optical ports can be measured for the analysis of the transmission quality of the running Base
Station Controller so that the stable and reliable operation of the Base Station Controller can be
maintained. This function subset automatically takes effect after a channelized optical interface
board is added.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73404129
VS.CHANNELIZE
D.FAULTTIME
T7247:Duration of
Faults on the
Channelized Optical
Port
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

3744
BSC6900 UMTS
Duration of Faults on the Channelized Optical Port

Counters
Counter ID
Counter Name
Counter Description
73404129
VS.CHANNELIZED.FAUL
TTIME
T7247:Duration of Faults on
the Channelized Optical Port
Description
This counter provides the duration of faults in the optical port in the measurement period.
Measurement point
Samples are taken every second in the specified measurement period. If the system is in faulty
state at the current sampling point, one second is added to the fault duration of the port.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.CHANNELIZED.FAUL
TTIME
WRFD-050304
IMA for E1T1 or

Channelized STM-1/OC-3
on Iub Interface
2.9 Measurement of E1/T1 Port Bit Error Performance

(E1T1_ES)
Overview
Bit error performance is an important indicator to evaluate system performance and reflects
digital information loss during transmission. ITU G.826 defines the links where data is
transmitted through data blocks. It also defines the transmission bit error rate (BER) should be
monitored when the links are in normal state. Measurement of E1/T1 Port Bit Error Performance
is used to monitor the physical transmission quality by measuring the E1T1 errored second and
the BER.
Issue 03 (2015-06-30)

3745
BSC6900 UMTS
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
E1T1_ES
E1/T1 Port Bit Error Measurement
2.9.1 E1/T1 Port Bit Error Measurement(E1T1_ES)

Overview
E1/T1 is a major resource for the base station controller. It indicates E1T1 electrical ports or
channelized optical ports. E1/T1 Port Bit Error Measurement is used to measure the E1T1 errored
seconds and BER. In this way, the transmission quality can be monitored and the stable operation
of the system is ensured. ITU G.826 defines the following monitoring items(a1,a2,d1,d2,d3) and
HUAWEI defines the following monitoring(a3,d4,d5).Based on the items and their
measurement rules, the E1T1 errored seconds and BER can be obtained.
a1: an errored frame alignment signal.
a2: an EB as indicated by an EDC.
a3: E-Bit error, indicating that the CRC for the transmitted frames fails.
d1: loss of signal.
d2: alarm indication signal.
d3: loss of frame alignment.
d4: frame slip, indicating that frame slips occur in the receiving direction.
d5: remote alarm indication, indicating that the peer end cannot receive frames properly.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403242
VS.E1T1.ES.ES
T7001:E1/T1 Error
Seconds
BSC6900
V900R011
73403243
VS.E1T1.ES.SES
T7002:E1/T1
Severely Error
Seconds
BSC6900
V900R011
73403244
VS.E1T1.ES.UAS
T7003:E1/T1
Unavailable Seconds
BSC6900
V900R011

3746
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73403245
VS.E1T1.ES.BBE
T7004:Number of
E1/T1 Background
Error Blocks
BSC6900
V900R011
73415654
VS.E1T1.ES.ESR
T7005:E1/T1 Error
Second Rate
BSC6900
V900R011
73415655
VS.E1T1.ES.SESR
T7006:E1/T1
Severely Error
Second Rate
BSC6900
V900R011
73415656
VS.E1T1.ES.UASR
T7007:E1/T1
Unavailable Second
Rate
BSC6900
V900R011
73415657
VS.E1T1.ES.BBER
T7008:E1/T1
Background Block
Error Rate
BSC6900
V900R011
73403645
VS.E1T1.ES.TES
T7010:Number of
Seconds with Error
Codes Transmitted
over E1/T1
BSC6900
V900R011
73403646
VS.E1T1.ES.TSES
T7011:Number of
Seconds with
Severely Error Codes
Transmitted over E1/
T1
BSC6900
V900R011
73403647
VS.E1T1.ES.TBBE
T7012:Number of
Background Error
Blocks Transmitted
over E1/T1
BSC6900
V900R011
73415827
VS.E1T1.ES.TESR
T7013:Second Rate
with Error Codes
T1
BSC6900
V900R011
73415828
VS.E1T1.ES.TSES
R
T7014:Second Rate
with Severely Error
Codes Transmitted
over E1/T1
BSC6900
V900R011
73415829
VS.E1T1.ES.TBBE
R
T7015:Error Rate of
Background Block
T1
BSC6900
V900R011

3747
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426203
VS.E1T1.ES.NUV
T7077:E1/T1
Number of
Unavailability
BSC6900
V900R015C00
None
E1T1 Errored Second

Counters
Counter ID
Counter Name
Counter Description
73403242
VS.E1T1.ES.ES
T7001:E1/T1 Error Seconds
73403645
VS.E1T1.ES.TES
T7010:Number of Seconds
with Error Codes
Transmitted over E1/T1
Description
VS.E1T1.ES.ES: If any of the monitoring items a1, a2, d1, d2, d3 and d4 exists within one
second, it is considered as a received errored second (ES). For the meanings of the monitoring
items, see the definition of E1T1 Port Bit Error Measurement.
VS.E1T1.ES.TES: If any of the monitoring items a3 and d5 exists within one second, it is
considered as a transmitted errored second (TES).
Measurement point
VS.E1T1.ES.ES: Samples are taken every second in the specified measurement period. The
counter is added by one, if the current second is a received errored second (ES).
VS.E1T1.ES.TES: Samples are taken every second in the specified measurement period. The
counter is added by one, if the current second is a transmitted errored second (TES).
Formula
None
Unit
s
Issue 03 (2015-06-30)

3748
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.E1T1.ES.ES
WRFD-05030101
ATM over E1T1 on Iub

Interface
VS.E1T1.ES.TES
WRFD-05030101

Interface
Counter ID
Counter Name
Counter Description
73403243
VS.E1T1.ES.SES
T7002:E1/T1 Severely Error

Seconds
73403646
VS.E1T1.ES.TSES
T7011:Number of Seconds
with Severely Error Codes
E1T1 Severely Errored Second

Counters
Description
VS.E1T1.ES.SES: If any of the monitoring items d1, d2, d3, and d4 exists within one second or
x a1 items or a2 items (x indicates 100 in T1 transmission mode and 300 in E1 transmission
mode) exist within one second, it is considered as a received severely errored second (SES). For
the meanings of the monitoring items, see the definition of E1T1 Port Bit Error Measurement.
VS.E1T1.ES.TSES: If a monitoring item d5 exists within one second or x a3 items (x indicates
100 in T1 transmission mode and 300 in E1 transmission mode) exist within one second, it is
considered as a transmitted severely errored second (TSES).
Measurement point
VS.E1T1.ES.SES: Samples are taken every second in the specified measurement period. The
counter is added by one, if the current second is a received severely errored second (SES).
VS.E1T1.ES.TSES: Samples are taken every second in the specified measurement period. The
counter is added by one, if the current second is a transmitted severely errored second (TSES).
Formula
None
Unit
s
Issue 03 (2015-06-30)

3749
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.E1T1.ES.SES
WRFD-05030101

Interface
VS.E1T1.ES.TSES
WRFD-05030101

Interface
Counter ID
Counter Name
Counter Description
73403244
VS.E1T1.ES.UAS
T7003:E1/T1 Unavailable
Seconds
73426203
VS.E1T1.ES.NUV
T7077:E1/T1 Number of
Unavailability
E1T1 Unavailable Second

Counters
Description
The link is considered unavailable after 10 received severely errored seconds (SESs) or 10
transmitted severely errored seconds (TSESs) appear continuously. These 10 seconds are also
included in the unavailable time. The link is considered available when no SES appears within
10 seconds. These 10 seconds are also included in the available time. The unavailable seconds
(UASs) are from the time when the link is unavailable to the time when the link is available.An
unavailable second is not calculated as an errored second.The VS.E1T1.ES.NUV counter
measures the number of times the measurement of the VS.E1T1.ES.UAS counter is triggered
in a measurement period. This counter is increased by one each time an E1/T1 link becomes
faulty.
Measurement point
Samples are taken every second in the specified measurement period.
Formula
None
Unit
s
Issue 03 (2015-06-30)

3750
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.E1T1.ES.UAS
WRFD-05030101

Interface
VS.E1T1.ES.NUV
WRFD-05030101

Interface
Counter ID
Counter Name
Counter Description
73403245
VS.E1T1.ES.BBE
T7004:Number of E1/T1
Background Error Blocks
73403647
VS.E1T1.ES.TBBE
T7012:Number of
Background Error Blocks
E1T1 Background Error Block

Counters
Description
VS.E1T1.ES.BBE: This counter measures the number of received background error blocks that
contain a1 or a2 items but do not occur in any received severely errored second (SES). For the
meanings of the monitoring items, see the definition of E1T1 Port Bit Error Measurement.
VS.E1T1.ES.TBBE: This counter measures the number of transmitted background error blocks
that contain a3 items but do not occur in any transmitted severely errored second (TSES).
Measurement point
Formula
None
Unit
None
Issue 03 (2015-06-30)

3751
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.E1T1.ES.BBE
WRFD-05030101

Interface
VS.E1T1.ES.TBBE
WRFD-05030101

Interface
Counter ID
Counter Name
Counter Description
73415654
VS.E1T1.ES.ESR
T7005:E1/T1 Error Second

Rate
73415827
VS.E1T1.ES.TESR
T7013:Second Rate with

Error Codes Transmitted
over E1/T1
E1T1 Errored Second Rate

Counters
Description
VS.E1T1.ES.ESR: This counter measures the proportion of the received errored seconds (ESs)
in the specified measurement period.
VS.E1T1.ES.TESR: This counter measures the proportion of the transmitted errored seconds
(TESs) in the specified measurement period.
Measurement point
Formula
None
Unit
%
Issue 03 (2015-06-30)

3752
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.E1T1.ES.ESR
WRFD-05030101

Interface
VS.E1T1.ES.TESR
WRFD-05030101

Interface
Counter ID
Counter Name
Counter Description
73415655
VS.E1T1.ES.SESR
T7006:E1/T1 Severely Error

Second Rate
73415828
VS.E1T1.ES.TSESR
T7014:Second Rate with

Severely Error Codes
E1T1 Severely Errored Second Rate

Counters
Description
VS.E1T1.ES.SESR: This counter measures the proportion of the received severely errored
seconds (SESs) in the specified measurement period.
VS.E1T1.ES.TSESR: This counter measures the proportion of the transmitted severely errored
seconds (TSESs) in the specified measurement period.
Measurement point
Formula
None
Unit
%
Issue 03 (2015-06-30)

3753
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.E1T1.ES.SESR
WRFD-05030101

Interface
VS.E1T1.ES.TSESR
WRFD-05030101

Interface
Counter ID
Counter Name
Counter Description
73415656
VS.E1T1.ES.UASR
T7007:E1/T1 Unavailable
Second Rate
E1T1 Unavailable Second Rate

Counters
Description
This counter provides the proportion of the unavailable seconds in the specified measurement
period.
Measurement point
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.E1T1.ES.UASR
WRFD-05030101

Interface

3754
BSC6900 UMTS
E1T1 Background Block Error Rate

Counters
Counter ID
Counter Name
Counter Description
73415657
VS.E1T1.ES.BBER
T7008:E1/T1 Background
Block Error Rate
73415829
VS.E1T1.ES.TBBER
T7015:Error Rate of
Background Block
Description
VS.E1T1.ES.BBER: This counter measures the proportion of the Received Background Error
Blocks (BBEs) among all data blocks within the specified measurement period when the E1/T1
link is available.
VS.E1T1.ES.TBBER: This counter measures the proportion of the Transmitted Background
Error Blocks (TBBEs) among all data blocks within the specified measurement period when the
E1/T1 link is available.
Measurement point
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.E1T1.ES.BBER
WRFD-05030101

Interface
VS.E1T1.ES.TBBER
WRFD-05030101

Interface

3755
BSC6900 UMTS
2.10 Measurement of E1/T1 Electrical Port Performance

(ELECT)
Overview
E1/T1 is short for PCM30 and PCM24(Pulse Code Modulation) used in digital system. The
transmission rate of an E1 port is 2048 kbit/s and the transmission rate of a T1 port is 1544 kbit/
s. Measurement of E1/T1 Electrical Port Performance indicates the transmission quality of the
E1/T1 ELECT ports, that is, the electrical ports on the AEUa, PEU or PEUc board.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
ELECT
E1/T1 Electrical Port Measurement
2.10.1 E1/T1 Electrical Port Measurement(ELECT)

Overview
The E1/T1 Electronical Ports are important resources of the Base Station Controller system.
Each E1/T1 electronical port is a measurement object of the ELECT. Therefore, the E1/T1
Electronical ports can be measured for the analysis of the transmission quality of the running
Base Station Controller so that the stable and reliable operation of the Base Station Controller
can be maintained. This function subset measures the cell traffic sent and received over an E1/
T1 electrical port and various errors over the E1/T1 electrical port.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194334
VS.ELECT.CODEVIOLATE
T7016:Number of
Cells with Error
Codes in the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011
67204488
VS.ELECT.CODE
VIOLATE.Rate.M
ean
T7017:Rate of Cells
with Error Codes in
the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011

3756
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194335
VS.ELECT.FRAM
INGERROR
T7020:Number of
Cells with Error
Frame Delimitation
in the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011
67204489
VS.ELECT.FRAM
INGERROR.Rate.
Mean
T7021:Rate of Cells
with Frame
Delimitation Error in
the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011
67194336
VS.ELECT.CRCE
RROR
T7024:Number of
Cells with CRC Error
in the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011
67204490
VS.ELECT.CRCE
RROR.Rate.Mean
T7025:Rate of Cells
with CRC Error in
the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011
67194337
VS.ELECT.EBITE
RROR
T7028:Number of
Cells with Ebit Error
in the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011
67204491
VS.ELECT.EBITE
RROR.Rate.Mean
T7029:Rate of Cells
with Ebit Error in the
E1/T1 Electronical
Port
Earlier than
BSC6900
V900R011
67194338
VS.ELECT.SA6ER
ROR
T7032:Number of
Cells with Sa6 Error
in the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011
67194341
VS.ELECT.FAUL
TTIME
T7035:Duration of
Faults in the E1/T1
Electronical Port
Earlier than
BSC6900
V900R011
67194342
VS.ELECT.MULT
IFRAME
T7036:Number of
Multiframes on the
E1/T1 Electronical
Port
Earlier than
BSC6900
V900R011
67194343
VS.ELECT.RXFL
OWCAPACITY
T7037:Traffic
Received on the E1/
T1 Electronical Port
Earlier than
BSC6900
V900R011

3757
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67194344
VS.ELECT.TXFL
OWCAPACITY
T7038:Traffic
Transmitted on the
E1/T1 Electronical
Port
Earlier than
BSC6900
V900R011
67194347
VS.ELECT.FRAM
EALIGNCHANGE
D
T7039:Number of
Frame Alignment
Changes of the E1/
T1 Electronical Port
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of Cells with Error Codes in the E1/T1 electronical
port
Counters
Counter ID
Counter Name
Counter Description
67194334
T7016:Number of Cells with

Error Codes in the E1/T1
Electronical Port
67194335
VS.ELECT.FRAMINGERROR

Error Frame Delimitation in
the E1/T1 Electronical Port
67194336
VS.ELECT.CRCERROR

CRC Error in the E1/T1
Electronical Port
67194337
VS.ELECT.EBITERROR

Ebit Error in the E1/T1
Electronical Port
67194338
VS.ELECT.SA6ERROR

Sa6 Error in the E1/T1
Electronical Port
Description
These counters provide the number of cells with error codes in the E1/T1 electronical port in
Issue 03 (2015-06-30)

3758
BSC6900 UMTS
Measurement point
the number of cells with error codes on the E1/T1 electronical port once every five seconds and
obtains the total number of cells with error codes on the E1/T1 electronical port in one
measurement period.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-05030101

Interface
VS.ELECT.FRAMINGERROR
WRFD-05030101

Interface
VS.ELECT.CRCERROR
WRFD-05030101

Interface
VS.ELECT.EBITERROR
WRFD-05030101

Interface
VS.ELECT.SA6ERROR
WRFD-05030101

Interface
Counters Related to the Rate of Cells in the E1/T1 electronical port

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204488
VS.ELECT.CODEVIOLAT
E.Rate.Mean
T7017:Rate of Cells with

Error Codes in the E1/T1
Electronical Port
67204489
VS.ELECT.FRAMINGERR
OR.Rate.Mean

Frame Delimitation Error in
67204490
VS.ELECT.CRCERROR.R
ate.Mean

CRC Error in the E1/T1
Electronical Port

3759
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67204491
VS.ELECT.EBITERROR.R
ate.Mean

Ebit Error in the E1/T1
Electronical Port
Description
These counters provide the rate of cells with error codes in the E1/T1 electronical port in the
measurement period.
Measurement point
the error rate once every five seconds and calculates the mean value based on the collected
statistics within one measurement period.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ELECT.CODEVIOLAT
E.Rate.Mean
WRFD-05030101

Interface
VS.ELECT.FRAMINGERR
OR.Rate.Mean
WRFD-05030101

Interface
VS.ELECT.CRCERROR.R
ate.Mean
WRFD-05030101

Interface
VS.ELECT.EBITERROR.R
ate.Mean
WRFD-05030101

Interface

3760
BSC6900 UMTS
Duration of Faults in the E1/T1 electronical port

Counters
Counter ID
Counter Name
Counter Description
67194341
VS.ELECT.FAULTTIME
T7035:Duration of Faults in
Description
This counter provides the duration of faults in the E1/T1 electronical port in the measurement
period.
Measurement point
Samples are taken every five seconds in the specified measurement period. If the system is in
faulty state at the current sampling point, five seconds are added to the fault duration of the link.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.ELECT.FAULTTIME
WRFD-05030101

Interface
Number of Multiframes on the E1/T1 electronical port

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194342
VS.ELECT.MULTIFRAME
T7036:Number of
Multiframes on the E1/T1
Electronical Port

3761
BSC6900 UMTS
Description
This counter provides the number of loss of multiframe alignment (LMFA) times over the E1/
T1 electrical port.
Measurement point
the number of LMFA times on the E1/T1 electronical port once every five seconds and obtains
the total number of LMFA times in one measurement period.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.ELECT.MULTIFRAME
WRFD-05030101

Interface
Counters Related to the Traffic Received or Transmitted on the E1/T1 electronical

port
Counters
Counter ID
Counter Name
Counter Description
67194343
VS.ELECT.RXFLOWCAPACITY
T7037:Traffic Received on
67194344
VS.ELECT.TXFLOWCAPACITY
T7038:Traffic Transmitted
on the E1/T1 Electronical
Port
Description
This counter provides the traffic received and transmitted on the E1/T1 electronical port in the
measurement period.
Measurement point
Samples are taken every five seconds in the measurement period.
Issue 03 (2015-06-30)

3762
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.ELECT.RXFLOWCAPACITY
WRFD-05030101

Interface
VS.ELECT.TXFLOWCAPACITY
WRFD-05030101

Interface
Number of Frame Alignment Changes of the E1/T1 electronical port

Counters
Counter ID
Counter Name
Counter Description
67194347
VS.ELECT.FRAMEALIGNCHANGED
T7039:Number of Frame
Alignment Changes of the
E1/T1 Electronical Port
Description
This counter provides the number of frame alignment changes of the E1/T1 electronical port in
Measurement point
the number of frame alignment changes on the E1/T1 electronical port once every five seconds
and obtains the total number of frame alignment changes in one measurement period.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3763
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.ELECT.FRAMEALIGNCHANGED
WRFD-05030101

Interface
2.11 Measurement of FE/GE Ethernet Port Performance

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

Overview
FE/GE Ethernet ports are important resources of the Base Station Controller. Therefore, the
FEGE Ethernet ports can be measured for the analysis of the transmission quality of the running
Base Station Controller so that the stable and reliable operation of the Base Station Controller
can be maintained. This function subset automatically takes effect after an Ethernet interface
board is added.
FEGE Ethernet port belongs to the Link layer of the TCP/IP protocol suite, as figure 1 shows.
Figure 2-31 The four layers of the TCP/IP protocol suite
Issue 03 (2015-06-30)

3764
BSC6900 UMTS
In the configuration structure, FE/GE ports are physical ports, as shown in the figure 2. The data
traffic sent and received over an upper-layer link is the sum of traffic on FE/GE ports.
Figure 2-32 Physical bearer of the FEGE Ethernet Port
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204393
VS.FEGE.RXBYT
ES
T7101:Number of
Bytes Received on
the FEGE Ethernet
Port
Earlier than
BSC6900
V900R011
67204394
VS.FEGE.TXBYT
ES
T7104:Number of
the FEGE Ethernet
Port
Earlier than
BSC6900
V900R011
67204395
VS.FEGE.RXPAC
KETS
T7107:Number of
frames Received on
the FEGE Ethernet
Port
Earlier than
BSC6900
V900R011
67204396
VS.FEGE.TXPAC
KETS
T7110:Number of
frames Transmitted
on the FEGE
Ethernet Port
Earlier than
BSC6900
V900R011

3765
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194363
VS.FEGE.TXDRO
PPEDPKTS
T7113:Number of
frames Discarded in
Transmission on the
FEGE Ethernet Port
Earlier than
BSC6900
V900R011
67194364
VS.FEGE.RXERRORPKTS
T7114:Number of
FCS(Frame Check
Sequence) Error
frames Received on
the FEGE Ethernet
Port
Earlier than
BSC6900
V900R011
67194365
VS.FEGE.RXUNKNOWNPKTS
T7115:Frames
Number of Unknown
Protocol Received on
the FEGE Ethernet
Port
Earlier than
BSC6900
V900R011
67194368
VS.FEGE.FAULTTIME
T7118:Duration of
Faults in the FEGE
Ethernet Port
Earlier than
BSC6900
V900R011
67194369
VS.FEGE.RXMAX
SPEED
T7121:Highest
Receive Rate of the
FEGE Ethernet Port
Earlier than
BSC6900
V900R011
67194370
VS.FEGE.RXMINSPEED
T7122:Lowest
Receive Rate of the
FEGE Ethernet Port
Earlier than
BSC6900
V900R011
67194371
VS.FEGE.RXMEA
NSPEED
T7123:Mean
Receive Rate of the
FEGE Ethernet Port
Earlier than
BSC6900
V900R011
67194372
VS.FEGE.TXMAX
SPEED
T7126:Highest
Transmit Rate of the
FEGE Ethernet Port
Earlier than
BSC6900
V900R011
67194373
VS.FEGE.TXMINSPEED
T7127:Lowest
FEGE Ethernet Port
Earlier than
BSC6900
V900R011
67194374
VS.FEGE.TXMEA
NSPEED
T7128:Mean
FEGE Ethernet Port
Earlier than
BSC6900
V900R011
67204764
VS.FEGE.RXPAU
SEFRAMES
T7129:Number of
the PAUSE Control
Frames Received on
the FEGE Ethernet
Port
Earlier than
BSC6900
V900R011

3766
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204765
VS.FEGE.TXPAU
SEFRAMES
T7130:Number of
the PAUSE Control
Frames Transmitted
on the FEGE
Ethernet Port
Earlier than
BSC6900
V900R011
73441531
VS.FEGE.FIVE.M
INUTES.RXMAXSPEED
T7137:Highest
Receive Rate of the
FEGE Ethernet Port
(5-Minute)
BSC6900
V900R014
73441532
VS.FEGE.FIVE.M
INUTES.TXMAXSPEED
T7138:Highest
FEGE Ethernet Port
(5-Minute)
BSC6900
V900R014
73444333
VS.FEGE.Alloced.
Ave.Fwd
T7143:Mean
forward bandwidth
assigned to an FEGE
Ethernet Port
BSC6900
V900R016C00
73444334
VS.FEGE.Alloced.
Ave.Bwd
T7146:Mean
backward bandwidth
assigned to an FEGE
Ethernet Port
BSC6900
V900R016C00
73428372
VS.FEGE.Alloced.
Max.Fwd
T7149:Maximum
Forward bandwidth
assigned to an FEGE
Ethernet Port
BSC6900
V900R016C00
73428373
VS.FEGE.Alloced.
Max.Bwd
T7150:Maximum
Backward
bandwidth assigned
to an FEGE Ethernet
Port
BSC6900
V900R016C00
73428366
VS.FEGE.Fwd.Con
g
T7158:Number of
forward congestions
on an FEGE Ethernet
Port
BSC6900
V900R016C00
73444335
VS.FEGE.Fwd.Con
g.Dur
T7159:Duration of
forward congestion
on an FEGE Ethernet
Port
BSC6900
V900R016C00
73428367
VS.FEGE.Bwd.Co
ng
T7160:Number of
backward
congestions on an
FEGE Ethernet Port
BSC6900
V900R016C00

3767
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73444336
VS.FEGE.Bwd.Co
ng.Dur
T7161:Duration of
backward congestion
on an FEGE Ethernet
Port
BSC6900
V900R016C00
None
Counters Related to the Number of Bytes Received or Transmitted on the FEGE

Ethernet port
Counters
Counter ID
Counter Name
Counter Description
67204393
VS.FEGE.RXBYTES
T7101:Number of Bytes
Received on the FEGE
Ethernet Port
67204394
VS.FEGE.TXBYTES
Transmitted on the FEGE
Ethernet Port
Description
These counters provide the number of bytes received or transmitted at the Link layer for the FE/
GE port in a specified measurement period. They indicate the traffic volume at the Link layer
for the FE/GE port in the specified measurement period. The number of bytes measured includes
the number of bytes in the header of the MAC frame and the payload. The measured bytes include
the header, payload, and Frame Check Sequence (FCS)
Measurement point
the number of bytes received and transmitted on the port once every five seconds and obtains
the total number of bytes in one measurement period.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

3768
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.FEGE.RXBYTES
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.FEGE.TXBYTES
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Counters Related to the Number of frames Received, Transmitted or Discarded on

the FEGE Ethernet port
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204395
VS.FEGE.RXPACKETS
T7107:Number of frames
Ethernet Port
67204396
VS.FEGE.TXPACKETS
Ethernet Port
67194363
VS.FEGE.TXDROPPEDPKTS
Discarded in Transmission
on the FEGE Ethernet Port
67194364
VS.FEGE.RXERRORPKTS
T7114:Number of FCS
(Frame Check Sequence)
Error frames Received on the
FEGE Ethernet Port
67194365
T7115:Frames Number of
Unknown Protocol Received
on the FEGE Ethernet Port

3769
BSC6900 UMTS
Description
These counters provide the number of frames received, transmitted, or discarded on an FE/GE
Ethernet port in a measurement period. The frames measured by theses counters are MAC
frames.
When an error occurs in transmitting a frame (including overlong and overshort frames, packet
header length error, and packet length field error), the system discards this frame.
VS.FEGE.TXDROPPEDPKTS provides the number of frames discarded in the transmit
direction.
When the type of a received MAC frame is not IP, ARP, LAG (CFM detection), or 3ah/LACP,
the MAC frame is compliant with an unknown protocol. VS.FEGE.RXUNKNOWNPKTSFEGE
provides the number of received frames compliant with unknown protocols. This counter is valid
only for FG2c/GOUc/GOUe boards.
Measurement point
The system samples the bytes received, sent, and discarded on an FE/GE Ethernet port at an
interval of 5s in a measurement period. At the end of the measurement period, the system
accumulates the sampled values to obtain the values of the preceding counters.
Formula
None
Unit
frame
Related Features
Counter Name
Feature ID
Feature Name
VS.FEGE.RXPACKETS
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.FEGE.TXPACKETS
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3770
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.FEGE.TXDROPPEDPKTS
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.FEGE.RXERRORPKTS
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Duration of Faults in the FEGE Ethernet port

Counters
Counter ID
Counter Name
Counter Description
67194368
VS.FEGE.FAULTTIME
the FEGE Ethernet Port
Description
This counter provides the duration of faults in the FEGE Ethernet port in the measurement period.
Measurement point
Formula
None
Issue 03 (2015-06-30)

3771
BSC6900 UMTS
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.FEGE.FAULTTIME
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Counters related to the Receive Rate or Transmit Rate of the FEGE Ethernet port
Counters
Counter ID
Counter Name
Counter Description
67194369
VS.FEGE.RXMAXSPEED
T7121:Highest Receive Rate

of the FEGE Ethernet Port
67194370
VS.FEGE.RXMINSPEED
T7122:Lowest Receive Rate

67194371
VS.FEGE.RXMEANSPEED
T7123:Mean Receive Rate of

the FEGE Ethernet Port
67194372
VS.FEGE.TXMAXSPEED
T7126:Highest Transmit
Rate of the FEGE Ethernet
Port
67194373
VS.FEGE.TXMINSPEED
T7127:Lowest Transmit
Port
67194374
VS.FEGE.TXMEANSPEED
T7128:Mean Transmit Rate

Description
These counters provide the receive rate or transmit rate of the FEGE Ethernet port at the Link
layer in the measurement period. The rates measured here include the spending of the MAC
header and the MAC payload of the MAC data.
Issue 03 (2015-06-30)

3772
BSC6900 UMTS
Measurement point
The system samples the bytes sent and received on an FE/GE Ethernet port at the data link layer
at an interval of 5s. The measured MAC data includes MAC headers, payload, and CRC. At the
end of the measurement period, the system calculates the following information:
Maximum transmission rate and maximum reception rate, which are calculated by dividing the
maximum transmitted or received bytes in a measurement period by 5s.
Minimum transmission rate and minimum reception rate, which are calculated by dividing the
minimum transmitted or received bytes in a measurement period by 5s.
Average transmission rate and average reception rate, which are calculated by dividing the
accumulated bytes in a measurement period by the measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.FEGE.RXMAXSPEED
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.FEGE.RXMINSPEED
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.FEGE.RXMEANSPEED
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3773
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.FEGE.TXMAXSPEED
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.FEGE.TXMINSPEED
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.FEGE.TXMEANSPEED
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Counters Related to the Number of the PAUSE Control Frames on the FEGE
Ethernet port
Counters
Counter ID
Counter Name
Counter Description
67204764
VS.FEGE.RXPAUSEFRAMES
T7129:Number of the
PAUSE Control Frames
Ethernet Port
67204765
VS.FEGE.TXPAUSEFRAMES
T7130:Number of the
PAUSE Control Frames
Ethernet Port
Description
These counters provide the number of the PAUSE control frames received or transmitted on the
FEGE Ethernet port in the measurement period. The PAUSE control frame is a type of 64-byte
pause frame, which is defined in IEEE802.3X. When congestion occurs on the FE/GE Ethernet
port, the local end sends a PAUSE control frame to the peer end, notifying the peer end of the
congestion.
Issue 03 (2015-06-30)

3774
BSC6900 UMTS
Measurement point
the number of pause frames once every five seconds and obtains the total number of one
measurement period.
Formula
None
Unit
frame
Related Features
Counter Name
Feature ID
Feature Name
VS.FEGE.RXPAUSEFRAMES
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.FEGE.TXPAUSEFRAMES
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
5-Minute Measurement of the Highest Transmit and Receive Rates of the FEGE
Ethernet port
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441531
VS.FEGE.FIVE.MINUTES.
RXMAXSPEED

of the FEGE Ethernet Port(5Minute)
73441532
TXMAXSPEED
Port(5-Minute)

3775
BSC6900 UMTS
Description
These counters provide the receive rate or transmit rate of the FEGE Ethernet port at the Link
layer in the 5-Minute measurement period. The rates measured here include the spending of the
MAC header and the MAC payload of the MAC data.
Measurement point
1.Within a specified measurement period, the system measures the number of transmitted and
received bytes every 5 seconds and accumulates the number of bytes at the end of every 5-minute
sampling period to obtain the total number of bytes transmitted or received within the sampling
period.
2.The system calculates the transmit and receive rate within every 5-minute sampling period
with the following formula: Transmit and receive rate within a 5-minute sampling period = Total
number of bytes transmitted and received within a 5-minute sampling period/300
3.The system compares all of the collected transmit and receive rates to obtain the highest
transmit and receive rate within the specified measurement period, which is the value of the
corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
RXMAXSPEED
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
TXMAXSPEED
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3776
BSC6900 UMTS
Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to an

FEGE Ethernet Port
Counters
Counter ID
Counter Name
Counter Description
73444333
VS.FEGE.Alloced.Ave.Fwd
T7143:Mean forward
bandwidth assigned to an
FEGE Ethernet Port
73444334
VS.FEGE.Alloced.Ave.Bwd
T7146:Mean backward
FEGE Ethernet Port
73428372
VS.FEGE.Alloced.Max.Fwd
T7149:Maximum Forward
FEGE Ethernet Port
73428373
VS.FEGE.Alloced.Max.Bw
d
T7150:Maximum Backward
FEGE Ethernet Port
Description
When services access the network, bandwidth admission needs to be performed on FE/GE
Ethernet ports. These counters provide the average or maximum forward/backward bandwidth
allocated to an FE/GE Ethernet port in a specified measurement period.
Measurement point
allocated to an FE/GE Ethernet port every 15s. At the end of the measurement period, the system
divides the accumulated value by the sampling times to obtain the values of these counters.
Formula
None
Unit
bit/s
Issue 03 (2015-06-30)

3777
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.FEGE.Alloced.Ave.Fwd
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.FEGE.Alloced.Ave.Bwd
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.FEGE.Alloced.Max.Fwd
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.FEGE.Alloced.Max.Bw
d
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Measurement of the Number of Congestions on an FEGE Ethernet Port

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428366
VS.FEGE.Fwd.Cong
T7158:Number of forward
congestions on an FEGE
Ethernet Port
73428367
VS.FEGE.Bwd.Cong
T7160:Number of backward
congestions on an FEGE
Ethernet Port

3778
BSC6900 UMTS
Description
When services access the network, if the remaining bandwidth is less than or equal to the
congestion remaining threshold configured for an FE/GE Ethernet port, traffic on the FE/GE
Ethernet port is congested. Users can configure the congestion remaining threshold according
to the actual requirements. If the congestion remaining threshold is set to 0, congestion does not
occur. These counters provide the number of forward or backward congestions on an FE/GE
Ethernet port in a specified measurement period. If traffic on the FE/GE Ethernet port is
congested for a long time, service access may be affected. These counters can be used together
with the duration of congestion on the FE/GE Ethernet port to observe the congestion.
Measurement point
In a measurement period, these counters are incremented by one each time the state of an FE/
GE Ethernet port changes from non-congestion to forward or backward congestion, that is, the
remaining available bandwidth is less than the congestion remaining threshold.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.FEGE.Fwd.Cong
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.FEGE.Bwd.Cong
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3779
BSC6900 UMTS
Measurement of the Duration of Congestion on an FEGE Ethernet Port

Counters
Counter ID
Counter Name
Counter Description
73444335
VS.FEGE.Fwd.Cong.Dur
T7159:Duration of forward
congestion on an FEGE
Ethernet Port
73444336
VS.FEGE.Bwd.Cong.Dur
T7161:Duration of backward
congestion on an FEGE
Ethernet Port
Description
congestion remaining threshold configured for an FE/GE Ethernet port, traffic on the FE/GE
Ethernet port is congested. Users can configure the congestion remaining threshold according
to the actual requirements. If the congestion remaining threshold is set to 0, congestion does not
occur. These counters provide the duration of forward or backward congestions on an FE/GE
Ethernet port in a specified measurement period. If traffic on the FE/GE Ethernet port is
with the number of congestions on the FE/GE Ethernet port to observe the congestion.
Measurement point
In a measurement period, the measurement starts when forward or backward congestion occurs
on an FE/GE Ethernet port. The measurement stops when forward or backward congestion
relieves. At the end of the measurement period, the system uses the accumulated duration of
forward or backward congestions as the values of these counters.
Formula
None
Unit
s
Issue 03 (2015-06-30)

3780
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.FEGE.Fwd.Cong.Dur
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
VS.FEGE.Bwd.Cong.Dur
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
2.12 Measurement of Integrated Firewall Performance

(FIREWALL)
Overview
Measurement of Integrated Firewall Performance is used to measure the built-in firewall
performance of a base station controller and reflects the firewall status of the base station
controller.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
PACKETFILTER.FIREWALL
Packetfilter Measurement
2.12.1 Packetfilter Measurement(PACKETFILTER.FIREWALL)

Overview
The Packetfilter Measurement function subset is used to measure packet filtering performance
of a base station controller and reflect the packet filtering status of the base station controller.
Issue 03 (2015-06-30)

3781
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73446343
VS.FIREWALL.R
XACLDROPKETS
Number of
Discarded Packets
Due to Port-based
ACL Packet Filtering
BSC6900
V900R017C10
None
Number of Discarded Packets Due to Port-based ACL Packet Filtering

Counters
Counter ID
Counter Name
Counter Description
73446343
VS.FIREWALL.RXACLDROPKETS
Number of Discarded
Packets Due to Port-based
ACL Packet Filtering
Description
This counter provides the number of packets discarded on an FE/GE Ethernet port or a trunk
group due to port-based ACL packet filtering in a measurement period. FG2c/GOUc/GOUe
boards support ACL packet filtering.
Measurement point
In a measurement period, the system samples the number of packets discarded on an FE/GE
Ethernet port or a trunk group. At the end of the measurement period, the system uses the
accumulated value as the value of this counter.
Formula
None
Unit
packet
Related Features
None
Issue 03 (2015-06-30)

3782
BSC6900 UMTS
2.13 Measurement of Fractional ATM Link Performance

(FRACATMLNK)
Overview
The Fractional function is used for carrying wideband transmission signals in the narrowband
transmission system. In Fractional ATM mode, the data can be transmitted through one or more
idle E1/T1 timeslots of a E1/T1 frame. Measurement of Fractional ATM Link Performance
indicates the transmission quality of the Fractional ATM links on the AEUa or AOUc board.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
FRACATMLNK
Fractional ATM Link Measurement
2.13.1 Fractional ATM Link Measurement(FRACATMLNK)

Overview
The quality of transmission links directly affects the system performance. Fractional ATM link
measurement helps analyze system transmission quality so as to maintain system stability and
reliability. This function subset takes effect after a fractional link of ATM type is added.
Fractional ATM link belongs to the physical layer of the ATM reference model, as figure 1
shows.
Issue 03 (2015-06-30)

3783
BSC6900 UMTS
In the configuration structure, Fractional ATM links are between physical ports and logical
applications, as shown in the figure 2.
Figure 2-34 Physical bearer of the Fractional ATM
Issue 03 (2015-06-30)

3784
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67193989
VS.FRACATMLN
K.TXCELLS
Number of Cells
Transmitted on an
Fractional ATM
Link
Earlier than
BSC6900
V900R011
67193991
VS.FRACATMLN
K.RXCELLS
Number of Cells
Received on an
Fractional ATM
Link
Earlier than
BSC6900
V900R011
67193993
VS.FRACATMLN
K.RXHCSERRCE
LLS
Number of Error
Cells Received on an
Fractional ATM
Link
Earlier than
BSC6900
V900R011
67193994
VS.FRACATMLN
K.RXDROPPEDC
ELLS
Number of Cells
Discarded on an
Fractional ATM
Link
Earlier than
BSC6900
V900R011
67193995
VS.FRACATMLN
K.TXMAXSPEED
Maximum Transmit
Rate of an Fractional
ATM Link
Earlier than
BSC6900
V900R011
67193996
VS.FRACATMLN
K.TXMINSPEED
Minimum Transmit
ATM Link
Earlier than
BSC6900
V900R011
67193997
VS.FRACATMLN
K.TXMEANSPEE
D
Mean Transmit Rate

of an Fractional
ATM Link
Earlier than
BSC6900
V900R011
67193998
VS.FRACATMLN
K.RXMAXSPEED
Maximum Receive
ATM Link
Earlier than
BSC6900
V900R011
67193999
VS.FRACATMLN
K.RXMINSPEED
Minimum Receive
ATM Link
Earlier than
BSC6900
V900R011
67194000
VS.FRACATMLN
K.RXMEANSPEE
D
Mean Receive Rate

of an Fractional
ATM Link
Earlier than
BSC6900
V900R011
67204779
VS.FRACATMLN
K.Alloced.Ave.Fwd
Mean Occupied
Forward Bandwidth
of an FRA ATM
Link
Earlier than
BSC6900
V900R011

3785
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204780
VS.FRACATMLN
K.Alloced.Ave.Bwd
Mean Occupied
Backward
Bandwidth of an
FRA ATM Link
Earlier than
BSC6900
V900R011
67195938
VS.FRACATMLN
K.Alloced.Max.Fw
d
Maximum Occupied
Forward Bandwidth
of an FRA ATM
Link
Earlier than
BSC6900
V900R011
67195939
VS.FRACATMLN
K.Alloced.Max.Bw
d
Maximum Occupied
Backward
Bandwidth of an
FRA ATM Link
Earlier than
BSC6900
V900R011
67195940
VS.FRACATMLN
K.Fwd.Cong
Number of Forward
Congestions on an
FRA ATM Link
Earlier than
BSC6900
V900R011
67195941
VS.FRACATMLN
K.Fwd.Cong.Dur
Duration of Forward
Congestions on an
FRA ATM Link
Earlier than
BSC6900
V900R011
67195942
VS.FRACATMLN
K.Bwd.Cong
Number of
Backward
Congestions on an
FRA ATM Link
Earlier than
BSC6900
V900R011
67195943
VS.FRACATMLN
K.Bwd.Cong.Dur
Duration of
Backward
Congestions on an
FRA ATM Link
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of Cells Received, Transmitted or Discarded on

an Fractional ATM link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67193989
VS.FRACATMLNK.TXCE
LLS

on an Fractional ATM Link

3786
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67193991
VS.FRACATMLNK.RXCE
LLS

an Fractional ATM Link
67193993
VS.FRACATMLNK.RXHC
SERRCELLS
Number of Error Cells

Received on an Fractional
ATM Link
67193994
VS.FRACATMLNK.RXDR
OPPEDCELLS

on an Fractional ATM Link
Description
These counters provide the number of cells received, transmitted or discarded on an Fractional
ATM link in the specified measurement period.
Measurement point
the number of IEs transmitted, received or discarded on the link once every five seconds and
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.FRACATMLNK.TXCE
LLS
WRFD-050302
Fractional ATM Function on

Iub Interface
VS.FRACATMLNK.RXCE
LLS
WRFD-050302

Iub Interface
VS.FRACATMLNK.RXHC
SERRCELLS
WRFD-050302

Iub Interface
VS.FRACATMLNK.RXDR
OPPEDCELLS
WRFD-050302

Iub Interface

3787
BSC6900 UMTS
Counters Related to the Receive Rate or Transmit Rate of an Fractional ATM link
Counters
Counter ID
Counter Name
Counter Description
67193995
VS.FRACATMLNK.TXM
AXSPEED

67193996
VS.FRACATMLNK.TXMI
NSPEED
Minimum Transmit Rate of

67193997
VS.FRACATMLNK.TXME
ANSPEED
Mean Transmit Rate of an

Fractional ATM Link
67193998
VS.FRACATMLNK.RXM
AXSPEED

67193999
VS.FRACATMLNK.RXMI
NSPEED
Minimum Receive Rate of an

Fractional ATM Link
67194000
VS.FRACATMLNK.RXME
ANSPEED
Mean Receive Rate of an

Fractional ATM Link
Description
These counters provide the receive rate or transmit rate of an Fractional ATM link in the specified
measurement period from different perspectives.
Measurement point
the number of bytes received and transmitted on the link once every five seconds. With this, the
system obtains the maximum and the minimum number of bytes received or transmitted in five
seconds, and the total number of one measurement period. The maximum and minimum speed
is calculated with the maximum and minimum bytes in five seconds, and the average speed is
calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

3788
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.FRACATMLNK.TXM
AXSPEED
WRFD-050302

Iub Interface
VS.FRACATMLNK.TXMI
NSPEED
WRFD-050302

Iub Interface
VS.FRACATMLNK.TXME
ANSPEED
WRFD-050302

Iub Interface
VS.FRACATMLNK.RXM
AXSPEED
WRFD-050302

Iub Interface
VS.FRACATMLNK.RXMI
NSPEED
WRFD-050302

Iub Interface
VS.FRACATMLNK.RXME
ANSPEED
WRFD-050302

Iub Interface
Counters Related to the Occupied Forward Bandwidth or Backward Bandwidth of

an FRA ATM Link
Counters
Counter ID
Counter Name
Counter Description
67204779
VS.FRACATMLNK.Alloce
d.Ave.Fwd
Mean Occupied Forward

Bandwidth of an FRA ATM
Link
67204780
d.Ave.Bwd
Mean Occupied Backward

Bandwidth of an FRA ATM
Link
67195938
d.Max.Fwd
Maximum Occupied
Forward Bandwidth of an
FRA ATM Link
67195939
d.Max.Bwd
Maximum Occupied
Backward Bandwidth of an
FRA ATM Link
Description
The fractional function is used to carry wideband signals for the narrowband transmission
system. The fractional ATM mode allows the system to select one or multiple idle timeslots over
an E1/T1 link for transmission. When services access the network, bandwidth admission needs
to be performed on a fractional ATM link. These counters provide the average or maximum
Issue 03 (2015-06-30)

3789
BSC6900 UMTS
forward/backward bandwidth allocated to a fractional ATM link in a specified measurement

period.
Measurement point
allocated to a fractional ATM link every 15s. At the end of the measurement period, the system
divides the accumulated value by the sampling times to obtain the average forward or backward
bandwidth and uses the maximum sampled value as the maximum forward or backward
bandwidth.
Formula
None
Unit
bit/s
Related Features
Counter Name
Feature ID
Feature Name
d.Ave.Fwd
WRFD-050302

Iub Interface
d.Ave.Bwd
WRFD-050302

Iub Interface
d.Max.Fwd
WRFD-050302

Iub Interface
d.Max.Bwd
WRFD-050302

Iub Interface
Counters Related to the Number of Congestions on an FRA ATM Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67195940
VS.FRACATMLNK.Fwd.C
ong
Number of Forward
Congestions on an FRA
ATM Link
67195942
VS.FRACATMLNK.Bwd.C
ong
Number of Backward
ATM Link

3790
BSC6900 UMTS
Description
congestion remaining threshold configured for a fractional ATM link, traffic on the fractional
ATM link is congested. Users can configure the congestion remaining threshold according to
occur. These counters provide the number of forward or backward congestions on a fractional
ATM link in a specified measurement period. If traffic on multiple fractional ATM links is
with the duration of congestion on a fractional ATM link to observe the congestion.
Measurement point
In a measurement period, these counters are incremented by one each time the fractional ATM
link state changes from non-congestion to forward or backward congestion, that is, the remaining
available bandwidth is less than the congestion remaining threshold.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.FRACATMLNK.Fwd.C
ong
WRFD-050302

Iub Interface
VS.FRACATMLNK.Bwd.C
ong
WRFD-050302

Iub Interface
Counters Related to the Duration of Congestions on an FRA ATM Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67195941
VS.FRACATMLNK.Fwd.C
ong.Dur
Duration of Forward
ATM Link
67195943
VS.FRACATMLNK.Bwd.C
ong.Dur
ATM Link

3791
BSC6900 UMTS
Description
These counters provide the duration of congestion on an FRA ATM link in the measurement
period.
Counter Name
Description
VS.FRACATMLNK.Bwd.Cong.Dur
Duration of backward congestions on an FRA

ATM link
Measurement point
The measurement of a forward(backward) congestion duration starts when a forward(backward)
congestion is generated on an FRA ATM link and stops when the forward(backward) congestion
is cleared. In the measurement period, the accumulated forward(backward) congestion time on
the FRA ATM link is taken as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.FRACATMLNK.Fwd.C
ong.Dur
WRFD-050302

Iub Interface
VS.FRACATMLNK.Bwd.C
ong.Dur
WRFD-050302

Iub Interface
2.14 Measurement of Fractioanl IMA Link Performance

(FRACIMALNK)
Overview
The Fractional function is used for carrying wideband transmission signals in the narrowband
transmission system. In Fractional IMA mode, multiple fractional IMA links are logically
categorized into one group to increase the transmission bandwidth. Users can specify the number
of occupied timeslots when data is sent or received. Measurement of Fractioanl IMA Link
Performance indicates the transmission quality of the Fractional IMA links on the AEUa or
AOUc board.
Issue 03 (2015-06-30)

3792
BSC6900 UMTS
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
FRACIMALNK
Fractional IMA Link Measurement
2.14.1 Fractional IMA Link Measurement(FRACIMALNK)

Overview
The quality of transmission links directly affects the system performance. Fractional IMA Link
reliability. This function subset takes effect after a fractional link of IMA type is added.
In the configuration structure, Fractional IMA links are between physical ports and logical
applications, as shown in the figure 1.
Figure 2-35 Physical bearer of the Fractional IMA
Issue 03 (2015-06-30)

3793
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194002
VS.FRACIMALN
K.TXUSERCELLS
Number of User
Cells Transmitted on
an Fractional IMA
Link
Earlier than
BSC6900
V900R011
67194003
VS.FRACIMALN
K.TXSTUFFCELL
S
Number of Filling
an Fractional IMA
Link
Earlier than
BSC6900
V900R011
67194005
VS.FRACIMALN
K.RXUSERCELLS
Number of Cells
Received on an
Fractional IMA Link
Earlier than
BSC6900
V900R011
67194006
VS.FRACIMALN
K.RXSTUFFCELL
S
Number of Filling
Fractional IMA Link
Earlier than
BSC6900
V900R011
67194008
VS.FRACIMALN
K.RXDROPPEDC
ELLS
Number of Cells
Discarded on an
Fractional IMA Link
Earlier than
BSC6900
V900R011
67194009
VS.FRACIMALN
K.RXHCSERRCE
LLS
Number of Error
Fractional IMA Link
Earlier than
BSC6900
V900R011
67194010
VS.FRACIMALN
K.TXMAXSPEED
Maximum Transmit
IMA Link
Earlier than
BSC6900
V900R011
67194011
VS.FRACIMALN
K.TXMINSPEED
Minimum Transmit
IMA Link
Earlier than
BSC6900
V900R011
67194012
VS.FRACIMALN
K.TXMEANSPEE
D
Mean Transmit Rate

of an Fractional IMA
Link
Earlier than
BSC6900
V900R011
67194013
VS.FRACIMALN
K.RXMAXSPEED
Maximum Receive
IMA Link
Earlier than
BSC6900
V900R011
67194014
VS.FRACIMALN
K.RXMINSPEED
Minimum Receive
IMA Link
Earlier than
BSC6900
V900R011
67194015
VS.FRACIMALN
K.RXMEANSPEE
D
Mean Receive Rate

of an Fractional IMA
Link
Earlier than
BSC6900
V900R011

3794
BSC6900 UMTS
None
Counters Related to the Number of Cells Received, Transmitted or Discarded on

an Fractional IMA Link
Counters
Counter ID
Counter Name
Counter Description
67194002
VS.FRACIMALNK.TXUSERCELLS
Number of User Cells

Transmitted on an Fractional
IMA Link
67194003
VS.FRACIMALNK.TXST
UFFCELLS
Number of Filling Cells

Transmitted on an Fractional
IMA Link
67194005
VS.FRACIMALNK.RXUSERCELLS

67194006
VS.FRACIMALNK.RXST
UFFCELLS

IMA Link
67194008
VS.FRACIMALNK.RXDR
OPPEDCELLS

on an Fractional IMA Link
67194009
VS.FRACIMALNK.RXHC
SERRCELLS

IMA Link
Description
These counters provide the number of user cells received, transmitted or Discarded on an
Fractional IMA Link in the measurement period to indicate the traffic volume of the Fractional
IMA Link.
Issue 03 (2015-06-30)
Counter Name
Description
Number of user cells transmitted on an

Fractional IMA Link
VS.FRACIMALNK.TXSTUFFCELLS
Number of filling cells transmitted on an

Fractional IMA Link
Number of user cells received on an

Fractional IMA Link

3795
BSC6900 UMTS
Counter Name
Description
VS.FRACIMALNK.RXSTUFFCELLS
Number of filling cells received on an

Fractional IMA Link
VS.FRACIMALNK.RXDROPPEDCELLS
Number of received cells discarded on an

Fractional IMA Link due to errors in the link
VS.FRACIMALNK.RXHCSERRCELLS
Number of cells with error HCS (Header

Check Sequence) received on an Fractional
IMA Link
Measurement point
the number of IEs transmitted, received or discarded on the link once every five seconds and
obtains the total number of IEs in one measurement period.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050302

Iub Interface
VS.FRACIMALNK.TXST
UFFCELLS
WRFD-050302

Iub Interface
WRFD-050302

Iub Interface
VS.FRACIMALNK.RXST
UFFCELLS
WRFD-050302

Iub Interface
VS.FRACIMALNK.RXDR
OPPEDCELLS
WRFD-050302

Iub Interface
VS.FRACIMALNK.RXHC
SERRCELLS
WRFD-050302

Iub Interface

3796
BSC6900 UMTS
Counters Related to the Receive Rate or Transmit Rate of an Fractional IMA Link
Counters
Counter ID
Counter Name
Counter Description
67194010
VS.FRACIMALNK.TXMA
XSPEED

67194011
VS.FRACIMALNK.TXMI
NSPEED
Minimum Transmit Rate of

67194012
VS.FRACIMALNK.TXME
ANSPEED

Fractional IMA Link
67194013
VS.FRACIMALNK.RXMA
XSPEED

67194014
VS.FRACIMALNK.RXMI
NSPEED
Minimum Receive Rate of an

Fractional IMA Link
67194015
VS.FRACIMALNK.RXME
ANSPEED

Fractional IMA Link
Description
These counters provide the receive rate or transmit rate of an Fractional IMA Link in the
measurement period to indicate the load on an Fractional IMA Link.
Counter Name
Description
VS.FRACIMALNK.TXMAXSPEED
Maximum transmit rate of an Fractional IMA

Link
VS.FRACIMALNK.TXMINSPEED
Minimum transmit rate of an Fractional IMA

Link
VS.FRACIMALNK.TXMEANSPEED
Mean transmit rate of an Fractional IMA Link
VS.FRACIMALNK.RXMAXSPEED
Maximum receive rate of an Fractional IMA

Link
VS.FRACIMALNK.RXMINSPEED
Minimum receive rate of an Fractional IMA

Link
VS.FRACIMALNK.RXMEANSPEED
Mean receive rate of an Fractional IMA Link
Measurement point
Issue 03 (2015-06-30)

3797
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.FRACIMALNK.TXMA
XSPEED
WRFD-050302

Iub Interface
VS.FRACIMALNK.TXMI
NSPEED
WRFD-050302

Iub Interface
VS.FRACIMALNK.TXME
ANSPEED
WRFD-050302

Iub Interface
VS.FRACIMALNK.RXMA
XSPEED
WRFD-050302

Iub Interface
VS.FRACIMALNK.RXMI
NSPEED
WRFD-050302

Iub Interface
VS.FRACIMALNK.RXME
ANSPEED
WRFD-050302

Iub Interface
2.15 Measurement of IMA Group Performance(IMAGRP)

Overview
Inverse multiplexing over ATM (IMA) demultiplexes the assembled ATM cell flow into
multiple low-speed links and multiplexes the multiple low-speed links on the remote end to
restore the original assembled cell flow. It is a practical method for high-speed ATM cell flows.
Multiplexing multiple low-speed links significantly improves reliability of IMA groups on the
transport network. Measurement of IMA Group Performance indicates the transmission quality
of the IMA group on the AEUa, AOUa or AOUc board.
Issue 03 (2015-06-30)

3798
BSC6900 UMTS
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IMAGRP
IMA Group Measurement
2.15.1 IMA Group Measurement(IMAGRP)

Overview
The quality of transmission links directly affects the system performance. IMA group
reliability. This function subset takes effect after an IMA Group is added.
IMA group belongs to the physical layer of the ATM reference model, as figure 1 shows.
In the configuration structure, IMA groups are between physical ports and logical applications,
as shown in the figure 2.
Issue 03 (2015-06-30)

3799
BSC6900 UMTS
Figure 2-37 Physical bearer of the IMA Group
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194017
VS.IMAGROUP.R
XUSERCELLS
Number of User
IMA Group
Earlier than
BSC6900
V900R011
67194018
VS.IMAGROUP.R
XSTUFFCELLS
Number of Filling
IMA Group
Earlier than
BSC6900
V900R011
67204457
VS.IMAGROUP.P
EAK.RXRATE
Maximum Receive
Rate of an IMA
GROUP
Earlier than
BSC6900
V900R011
67194020
VS.IMAGROUP.R
XFILLERCELLS
Number of
decoupling Cells
(Idle Cells Received
when There Is No
Cell to Transmit)
Received on an IMA
Group
Earlier than
BSC6900
V900R011
67194021
VS.IMAGROUP.T
XUSERCELLS
Number of User
an IMA Group
Earlier than
BSC6900
V900R011

3800
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194022
VS.IMAGROUP.T
XSTUFFCELLS
Number of Filling
an IMA Group
Earlier than
BSC6900
V900R011
67204458
VS.IMAGROUP.P
EAK.TXRATE
Maximum Transmit
Rate of an IMA
Group
Earlier than
BSC6900
V900R011
67194024
VS.IMAGROUP.T
XFILLERCELLS
Number of
Decoupling Cells
when There Is No
Cell to Transmit)
Transmitted on an
IMA Group
Earlier than
BSC6900
V900R011
67194025
VS.IMAGROUP.T
XDISCARD
Number of Cells
Discarded in
Transmission on an
IMA Group
Earlier than
BSC6900
V900R011
67194026
VS.IMAGROUP.R
XDROP
Number of Cells
Discarded in
Reception on an IMA
Group
Earlier than
BSC6900
V900R011
67194027
VS.IMAGROUP.T
XERRORCELLS
Number of Error
an IMA Group
Earlier than
BSC6900
V900R011
67194028
VS.IMAGROUP.R
XERRORCELLS
Number of Error
IMA Group
Earlier than
BSC6900
V900R011
67202907
VS.IMA.Grp.Mean
Kbps.Rx
Mean Receive Rate

of an IMA Group
Earlier than
BSC6900
V900R011
67202908
VS.IMA.Grp.Mean
Kbps.Tx
Mean Transmit Rate

of an IMA Group
Earlier than
BSC6900
V900R011
67204192
VS.IMAGRP.Alloc
ed.Ave.Fwd
Mean Occupied
Forward Bandwidth
of an IMA Group
Earlier than
BSC6900
V900R011
67204193
VS.IMAGRP.Alloc
ed.Ave.Bwd
Mean Occupied
Backward
Bandwidth of an
IMA Group
Earlier than
BSC6900
V900R011

3801
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67193215
VS.IMAGRP.Alloc
ed.Max.Fwd
Maximum Occupied
Forward Bandwidth
of an IMA Group
Earlier than
BSC6900
V900R011
67193216
VS.IMAGRP.Alloc
ed.Max.Bwd
Maximum Occupied
Backward
Bandwidth of an
IMA Group
Earlier than
BSC6900
V900R011
67193217
VS.IMAGRP.Fwd.
Cong
Number of Forward
Congestions on an
IMA Group
Earlier than
BSC6900
V900R011
67193218
VS.IMAGRP.Fwd.
Cong.Dur
Duration of Forward
Congestions on an
IMA Group
Earlier than
BSC6900
V900R011
67193219
VS.IMAGRP.Bwd.
Cong
Number of
Backward
Congestions on an
IMA Group
Earlier than
BSC6900
V900R011
67193220
VS.IMAGRP.Bwd.
Cong.Dur
Duration of
Backward
Congestions on an
IMA Group
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of Cells Received or Transmitted on an IMA

Group
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194017
VS.IMAGROUP.RXUSERCELLS

Received on an IMA Group
67194018
VS.IMAGROUP.RXSTUFF
CELLS

67194020
VS.IMAGROUP.RXFILLERCELLS
Number of decoupling Cells

(Idle Cells Received when
There Is No Cell to Transmit)

3802
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194021
VS.IMAGROUP.TXUSERCELLS

Transmitted on an IMA
Group
67194022
VS.IMAGROUP.TXSTUFF
CELLS

Group
67194024
VS.IMAGROUP.TXFILLERCELLS
Number of Decoupling Cells

Group
67194025
VS.IMAGROUP.TXDISCARD

in Transmission on an IMA
Group
67194026
VS.IMAGROUP.RXDROP

in Reception on an IMA
Group
Description
These counters provide the number of cells received or transmitted on an IMA group in the
measurement period. They indicate the transmission condition of the IMA group.
Measurement point
the number of IEs transmitted on the link once every five seconds and obtains the total number
of one measurement period.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IMAGROUP.RXUSERCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface

3803
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.IMAGROUP.RXSTUFF
CELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMAGROUP.RXFILLERCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMAGROUP.TXUSERCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMAGROUP.TXSTUFF
CELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMAGROUP.TXFILLERCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMAGROUP.TXDISCARD
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMAGROUP.RXDROP
WRFD-050304
IMA for E1T1 or

on Iub Interface
Counters Related to the Receive Rate or Transmit Rate of an IMA Group

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204457
VS.IMAGROUP.PEAK.RX
RATE

an IMA GROUP
67204458
VS.IMAGROUP.PEAK.TX
RATE

an IMA Group
67202907
VS.IMA.Grp.MeanKbps.Rx

IMA Group
67202908
VS.IMA.Grp.MeanKbps.Tx

IMA Group

3804
BSC6900 UMTS
Description
These counters provide the receive rate or transmit rate of an IMA group in the measurement
period. They indicate the load on the IMA group.
Measurement point
system obtains the maximum number of bytes received or transmitted in five seconds, and the
total number of one measurement period. The maximum speed is calculated with the maximum
bytes in five seconds, and the average speed is calculated with the total bytes in one measurement
period.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IMAGROUP.PEAK.RX
RATE
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMAGROUP.PEAK.TX
RATE
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMA.Grp.MeanKbps.Rx
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMA.Grp.MeanKbps.Tx
WRFD-050304
IMA for E1T1 or

on Iub Interface

3805
BSC6900 UMTS
Counters Related to the Number of Error Cells Received or Transmitted on an IMA

Group
Counters
Counter ID
Counter Name
Counter Description
67194028
VS.IMAGROUP.RXERRORCELLS

67194027
VS.IMAGROUP.TXERRORCELLS

Group
Description
These counters provide the number of error cells received or transmitted on an IMA group in
Measurement point
the number of errored IEs transmitted and received on the link once every five seconds and
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IMAGROUP.RXERRORCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMAGROUP.TXERRORCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface

3806
BSC6900 UMTS
Counters related to the Occupied Forward Bandwidth or Occupied Backward

Bandwidth of an IMA Group
Counters
Counter ID
Counter Name
Counter Description
67204192
VS.IMAGRP.Alloced.Ave.F
wd
Mean Occupied Forward

67204193
VS.IMAGRP.Alloced.Ave.
Bwd
Mean Occupied Backward

67193215
VS.IMAGRP.Alloced.Max.
Fwd
Maximum Occupied
Forward Bandwidth of an
IMA Group
67193216
Bwd
Maximum Occupied
Backward Bandwidth of an
IMA Group
Description
IMA group is a logical concept, which logically considers multiple application links over an E1/
T1 port as a group. These links are IMA links. When services access the network, bandwidth
admission needs to be performed on IMA groups. These counters provide average or maximum
forward/backward bandwidth allocated to an IMA group in a specified measurement period.
Measurement point
allocated to an IMA group every 15s. At the end of the measurement period, the system divides
the accumulated value by the sampling times to obtain the average forward or backward
bandwidth and uses the maximum sampled value as the maximum forward or backward
bandwidth.
Formula
None
Unit
bit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IMAGRP.Alloced.Ave.F
wd
WRFD-05030106


3807
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.IMAGRP.Alloced.Ave.
Bwd
WRFD-05030106

Fwd
WRFD-05030106

Bwd
WRFD-05030106

Counters Related to the Number of Congestions on an IMA Group

Counters
Counter ID
Counter Name
Counter Description
67193217
VS.IMAGRP.Fwd.Cong
Number of Forward
Congestions on an IMA
Group
67193219
VS.IMAGRP.Bwd.Cong
Number of Backward
Group
Description
congestion remaining threshold configured for an IMA group, traffic on the IMA group is
congested. Users can configure the congestion remaining threshold according to the actual
requirements. If the congestion remaining threshold is set to 0, congestion does not occur. These
counters provide the number of forward or backward congestions on an IMA group in a specified
measurement period. If traffic on multiple IMA groups is congested for a long time, service
access may be affected. These counters can be used together with the duration of congestion on
an IMA group to observe the congestion.
Measurement point
In a measurement period, these counters are incremented by one each time the IMA group state
changes from non-congestion to forward or backward congestion, that is, the remaining available
bandwidth is less than the congestion remaining threshold.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3808
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IMAGRP.Fwd.Cong
WRFD-05030106

VS.IMAGRP.Bwd.Cong
WRFD-05030106

Counters Related to the Duration of Congestion on an IMA Group

Counters
Counter ID
Counter Name
Counter Description
67193218
VS.IMAGRP.Fwd.Cong.Du
r
Duration of Forward
Group
67193220
VS.IMAGRP.Bwd.Cong.Du
r
Group
Description
congestion remaining threshold configured for an IMA group, traffic on the IMA group is
counters provide the duration of forward or backward congestions on an IMA group in a specified
measurement period. If traffic on multiple IMA groups is congested for a long time, service
access may be affected. These counters can be used together with the number of congestions on
an IMA group to observe the congestion.
Counter Name
Description
VS.IMAGRP.Bwd.Cong.Dur
Duration of backward congestions on an IMA

group
Measurement point
on an IMA group. The measurement stops when forward or backward congestion relieves. At
the end of the measurement period, the system uses the accumulated duration of forward or
backward congestions as the values of these counters.
Issue 03 (2015-06-30)

3809
BSC6900 UMTS
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.IMAGRP.Fwd.Cong.Du
r
WRFD-05030106

VS.IMAGRP.Bwd.Cong.Du
r
WRFD-05030106

2.16 Measurement of IMA Link Performance(IMALNK)

Overview
An IMA link is a sub-link in an IMA group. One E1/T1 optical port can be configured with an
IMA link. All timeslots on an E1/T1 optical port are used when data is sent or received over this
link. Measurement of IMA Link Performance indicates the transmission quality of the IMA link
on the AEUa, AOUa or AOUc board.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IMALNK
IMA Link Measurement
2.16.1 IMA Link Measurement(IMALNK)

Overview
The quality of transmission links directly affects the system performance. IMA link
reliability. This function subset takes effect after an IMA Link is added.
IMA Link belongs to the physical layer of the ATM reference model, as figure 1 shows.
Issue 03 (2015-06-30)

3810
BSC6900 UMTS
In the configuration structure, IMA links are between physical ports and logical applications, as
shown in the figure 2.
Issue 03 (2015-06-30)

3811
BSC6900 UMTS
Figure 2-39 Physical bearer of the IMA Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194029
VS.IMALNK.RXU
SERCELLS
Number of User
IMA Link
Earlier than
BSC6900
V900R011
67194030
VS.IMALNK.RXU
STUFFCELLS
Number of Filling
IMA Link
Earlier than
BSC6900
V900R011
67203408
VS.IMALNK.PEA
K.RXRATE
Maximum Cell
Receive Rate of an
IMA Link
Earlier than
BSC6900
V900R011
67194032
VS.IMALNK.RXIDLECELLS
Number of idle Cells

Received on an IMA
Link
Earlier than
BSC6900
V900R011
67194033
VS.IMALNK.TXU
SERCELLS
Number of User
an IMA Link
Earlier than
BSC6900
V900R011
67194034
VS.IMALNK.TXU
STUFFCELLS
Number of Filling
an IMA Link
Earlier than
BSC6900
V900R011

3812
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67203409
VS.IMALNK.PEA
K.TXRATE
Maximum Cell
Transmit Rate of an
IMA Link
Earlier than
BSC6900
V900R011
67194036
VS.IMALNK.RXF
ILTERCELLS
Number of User
Cells Discarded on
an IMA Link Due to
Errors in the Link
Earlier than
BSC6900
V900R011
67194037
VS.IMALNK.RXA
NOMALY
Number of Cells with

Frame
synchronization
Error on an IMA
Link
Earlier than
BSC6900
V900R011
67194038
VS.IMALNK.RXI
CPVIOLATE

Error ICP(IMA
Control Protocol)
Received on an IMA
Link
Earlier than
BSC6900
V900R011
67194039
VS.IMALNK.RXI
CPCELLS

valid ICP(IMA
Control Protocol)
Received on an IMA
Link
Earlier than
BSC6900
V900R011
67194040
VS.IMALNK.RXH
CSERROR

HCS(Header Check
Sum) Error Received
on an IMA Link
Earlier than
BSC6900
V900R011
67194041
VS.IMALNK.RXF
ILLERCELLS
Number of
decoupling Cells
when There Is No
Cell to Transmit)
Received on an IMA
Link
Earlier than
BSC6900
V900R011
67194042
VS.IMALNK.FAU
LTEMIT
Number of Times
that a Fault Occurs in
an IMA Link
Earlier than
BSC6900
V900R011
67194043
VS.IMALNK.FAU
LTCLEAR
Number of Times
that a Fault is Cleared
in an IMA Link
Earlier than
BSC6900
V900R011
67194044
VS.IMALNK.FAU
LTTIME
Duration of Faults in
an IMA Link
Earlier than
BSC6900
V900R011

3813
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67202909
VS.IMA.Lnk.Mean
Kbps.Rx
Mean Receive Rate

of an IMA Link
Earlier than
BSC6900
V900R011
67202910
VS.IMA.Lnk.Mean
Kbps.Tx
Mean Transmit Rate

of an IMA Link
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of Packets Received or Transmitted on an IMA

Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194029
VS.IMALNK.RXUSERCELLS

Received on an IMA Link
67194030
VS.IMALNK.RXUSTUFFCELLS

67194032
Number of idle Cells

67194033
VS.IMALNK.TXUSERCELLS

Transmitted on an IMA Link
67194034
VS.IMALNK.TXUSTUFFCELLS

Transmitted on an IMA Link
67194036
VS.IMALNK.RXFILTERCELLS

Discarded on an IMA Link
Due to Errors in the Link
67194037
VS.IMALNK.RXANOMALY
Number of Cells with Frame

synchronization Error on an
IMA Link
67194038
VS.IMALNK.RXICPVIOLATE
Number of Cells with Error

ICP(IMA Control Protocol)

3814
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194039
VS.IMALNK.RXICPCELLS
Number of Cells with valid

ICP(IMA Control Protocol)
67194040
VS.IMALNK.RXHCSERROR
Number of Cells with HCS

(Header Check Sum) Error
67194041
VS.IMALNK.RXFILLERCELLS
Number of decoupling Cells

Description
These counters provide the number of cells received or transmitted on an IMA link in the
specified measurement period from different perspectives. They indicate the transmission
condition of the IMA link.
Measurement point
the number of IEs transmitted and received on the link once every five seconds and obtains the
total number of one measurement period.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IMALNK.RXUSERCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.RXUSTUFFCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
WRFD-050304
IMA for E1T1 or

on Iub Interface

3815
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.IMALNK.TXUSERCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.TXUSTUFFCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.RXFILTERCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.RXANOMALY
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.RXICPVIOLATE
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.RXICPCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.RXHCSERROR
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.RXFILLERCELLS
WRFD-050304
IMA for E1T1 or

on Iub Interface
Counters Related to the Receive Rate or Transmit Rate of an IMA Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67203408
VS.IMALNK.PEAK.RXRA
TE
Maximum Cell Receive Rate

of an IMA Link
67203409
VS.IMALNK.PEAK.TXRA
TE
Maximum Cell Transmit

Rate of an IMA Link
67202909
VS.IMA.Lnk.MeanKbps.Rx

IMA Link
67202910
VS.IMA.Lnk.MeanKbps.Tx

IMA Link

3816
BSC6900 UMTS
Description
These counters provide the receive rate or transmit rate of an IMA link in the specified
measurement period from different perspectives. They indicate the load on the IMA link.
Measurement point
period.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.IMALNK.PEAK.RXRA
TE
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMALNK.PEAK.TXRA
TE
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMA.Lnk.MeanKbps.Rx
WRFD-050304
IMA for E1T1 or

on Iub Interface
VS.IMA.Lnk.MeanKbps.Tx
WRFD-050304
IMA for E1T1 or

on Iub Interface
Number of Times That a Fault Occurs in an IMA Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194042
VS.IMALNK.FAULTEMIT
Number of Times that a Fault

Occurs in an IMA Link

3817
BSC6900 UMTS
Description
This counter provides the number of times that a fault occurs in an IMA Link in the specified
measurement period.
Measurement point
faulty state at the current sampling point but in normal state at the previous sampling point, the
number of faults is added by one.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IMALNK.FAULTEMIT
WRFD-050304
IMA for E1T1 or

on Iub Interface
Number of Times That a Fault Is Cleared in an IMA Link

Counters
Counter ID
Counter Name
Counter Description
67194043
VS.IMALNK.FAULTCLEAR
Number of Times that a Fault

is Cleared in an IMA Link
Description
This counter provides the number of times that a fault is cleared in an IMA link in the specified
measurement period.
Measurement point
normal state at the current sampling point but in faulty state at the previous sampling point, the
number of faults that are cleared is added by one.
Issue 03 (2015-06-30)

3818
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IMALNK.FAULTCLEAR
WRFD-050304
IMA for E1T1 or

on Iub Interface
Counter ID
Counter Name
Counter Description
67194044
VS.IMALNK.FAULTTIME
Duration of Faults in an IMA

Link
Duration of Faults in an IMA Link

Counters
Description
This counter provides the duration of faults that occur in an IMA link in the specified
measurement period.
Measurement point
state at the current sampling point, one second is added to the fault duration of the link.
Formula
None
Unit
s
Issue 03 (2015-06-30)

3819
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IMALNK.FAULTTIME
WRFD-050304
IMA for E1T1 or

on Iub Interface
2.17 Measurement of Interface Board for Transport

Resource Management Result Performance(INT_TRM)
Overview
The Measurement of Interface Board for Transport Resource Management Result Performance
measurement object indicates the transport resource usage of interface boards. The measurement
results can be used as a basis for capacity expansion or swapping.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
INT.TRM.ADMIT
Interface Board Admit Measurement
INT.TRM.FLOW
Interface Board Flow Resource Usage

Measurement
2.17.1 Interface Board Admit Measurement(INT.TRM.ADMIT)

Overview
The counters in this function subset indicate the usage of resources related to call admission over
the Iub/Iur/Iur-p/Iu interface, including the number of CS voice services, number of CS data
services, and transmission resource usage.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428460
VS.INT.TRM.AD
MIT.IUB.CS.VOIC
E.MAX
Maximum Online CS
Voice Traffic of
Interface Boards for
Iub Interface
BSC6900
V900R016C00

3820
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428461
VS.INT.TRM.AD
MIT.IUB.CS.VOIC
E.MEAN
Average Online CS
Voice Traffic of
Iub Interface
BSC6900
V900R016C00
73428464
VS.INT.TRM.AD
MIT.IUB.CS.DAT
A.MAX
Maximum Online CS
Data Traffic of
Iub Interface
BSC6900
V900R016C00
73444360
VS.INT.TRM.AD
MIT.IUB.CS.DAT
A.MEAN
Average Online CS
Data Traffic of
Iub Interface
BSC6900
V900R016C00
73428467
VS.INT.TRM.AD
MIT.IUCS.CS.VOI
CE.MAX
Maximum Online CS
Voice Traffic of
Iu-CS Interface
BSC6900
V900R016C00
73444361
VS.INT.TRM.AD
MIT.IUCS.CS.VOI
CE.MEAN
Average Online CS
Voice Traffic of
Iu-CS Interface
BSC6900
V900R016C00
73428470
VS.INT.TRM.AD
MIT.IUCS.CS.DA
TA.MAX
Maximum Online CS
Data Traffic of
Iu-CS Interface
BSC6900
V900R016C00
73444362
VS.INT.TRM.AD
MIT.IUCS.CS.DA
TA.MEAN
Average Online CS
Data Traffic of
Iu-CS Interface
BSC6900
V900R016C00
73428473
VS.INT.TRM.AD
MIT.IUR.CS.VOI
CE.MAX
Maximum Online CS
Voice Traffic of
Iur Interface
BSC6900
V900R016C00
73444363
VS.INT.TRM.AD
MIT.IUR.CS.VOI
CE.MEAN
Average Online CS
Voice Traffic of
Iur Interface
BSC6900
V900R016C00
73428476
VS.INT.TRM.AD
MIT.IUR.CS.DAT
A.MAX
Maximum Online CS
Data Traffic of
Iur Interface
BSC6900
V900R016C00

3821
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73444364
VS.INT.TRM.AD
MIT.IUR.CS.DAT
A.MEAN
Average Online CS
Data Traffic of
Iur Interface
BSC6900
V900R016C00
73428485
VS.INT.TRM.AD
MIT.IURP.CS.VOI
CE.MAX
Maximum Online CS
Voice Traffic of
Iur-p Interface
BSC6900
V900R016C00
73444367
VS.INT.TRM.AD
MIT.IURP.CS.VOI
CE.MEAN
Average Online CS
Voice Traffic of
Iur-p Interface
BSC6900
V900R016C00
73428488
VS.INT.TRM.AD
MIT.IURP.CS.DA
TA.MAX
Maximum Online CS
Data Traffic of
Iur-p Interface
BSC6900
V900R016C00
73444368
VS.INT.TRM.AD
MIT.IURP.CS.DA
TA.MEAN
Average Online CS
Data Traffic of
Iur-p Interface
BSC6900
V900R016C00
73428509
VS.INT.TRM.AD
MIT.RESUSAGE.
MAX
Maximum Transport
Resource Usage of
Interface Boards
BSC6900
V900R016C00
73444375
VS.INT.TRM.AD
MIT.RESUSAGE.
MEAN
Average Transport
Resource Usage of
Interface Boards
BSC6900
V900R016C00
None
Online CS Voice Traffic of Interface Boards for Iub Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428460
VS.INT.TRM.ADMIT.IUB.
CS.VOICE.MAX
Maximum Online CS Voice

Traffic of Interface Boards
for Iub Interface

3822
BSC6900 UMTS
Description
When services access the system, the transport layer needs to perform admission on the number
of subscribers on interface boards over different interfaces. These counters provide the maximum
online CS voice traffic and average online CS voice traffic of interface boards over the Iub
interface.
Measurement point
In a measurement period, the system automatically samples online CS voice traffic on an
interface board over the Iub interface every 15s. At the end of the measurement period, the
system obtains the average value by dividing the accumulated value by the number of sampling
times and uses the maximum sampled value as the maximum value.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CS.VOICE.MAX
WRFD-040100
Flow Control
Online CS Data Traffic of Interface Boards for Iub Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428464
CS.DATA.MAX
Maximum Online CS Data

for Iub Interface
73428461
CS.VOICE.MEAN
Average Online CS Voice

for Iub Interface
73444360
CS.DATA.MEAN
Average Online CS Data

for Iub Interface

3823
BSC6900 UMTS
Description
online CS data traffic and average online CS data traffic of interface boards over the Iub interface.
Measurement point
In a measurement period, the system automatically samples online CS data traffic on an interface
board over the Iub interface every 15s. At the end of the measurement period, the system obtains
the average value by dividing the accumulated value by the number of sampling times and uses
the maximum sampled value as the maximum value.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CS.DATA.MAX
WRFD-040100
Flow Control
CS.VOICE.MEAN
WRFD-040100
Flow Control
CS.DATA.MEAN
WRFD-040100
Flow Control
Online CS Voice Traffic of Interface Boards for Iu-CS Interface

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428467
VS.INT.TRM.ADMIT.IUC
S.CS.VOICE.MAX

for Iu-CS Interface
73444361
S.CS.VOICE.MEAN

for Iu-CS Interface

3824
BSC6900 UMTS
Description
online CS voice traffic and average online CS voice traffic of interface boards over the Iu-CS
interface.
Measurement point
interface board over the Iu-CS interface every 15s. At the end of the measurement period, the
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
S.CS.VOICE.MAX
WRFD-040100
Flow Control
S.CS.VOICE.MEAN
WRFD-040100
Flow Control
Online CS Data Traffic of Interface Boards for Iu-CS Interface

Counters
Counter ID
Counter Name
Counter Description
73428470
S.CS.DATA.MAX

for Iu-CS Interface
73444362
S.CS.DATA.MEAN

for Iu-CS Interface
Description
Issue 03 (2015-06-30)

3825
BSC6900 UMTS
online CS data traffic and average online CS data traffic of interface boards over the Iu-CS
interface.
Measurement point
board over the Iu-CS interface every 15s. At the end of the measurement period, the system
obtains the average value by dividing the accumulated value by the number of sampling times
and uses the maximum sampled value as the maximum value.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
S.CS.DATA.MAX
WRFD-040100
Flow Control
S.CS.DATA.MEAN
WRFD-040100
Flow Control
Online CS Voice Traffic of Interface Boards for Iur Interface

Counters
Counter ID
Counter Name
Counter Description
73428473
VS.INT.TRM.ADMIT.IUR.
CS.VOICE.MAX

for Iur Interface
73444363
CS.VOICE.MEAN

for Iur Interface
Description
online CS voice traffic and average online CS voice traffic of interface boards over the Iur
interface.
Issue 03 (2015-06-30)

3826
BSC6900 UMTS
Measurement point
interface board over the Iur interface every 15s. At the end of the measurement period, the system
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CS.VOICE.MAX
WRFD-040100
Flow Control
CS.VOICE.MEAN
WRFD-040100
Flow Control
Online CS Data Traffic of Interface Boards for Iur Interface

Counters
Counter ID
Counter Name
Counter Description
73428476
CS.DATA.MAX

for Iur Interface
73444364
CS.DATA.MEAN

for Iur Interface
Description
online CS data traffic and average online CS data traffic of interface boards over the Iur interface.
Measurement point
board over the Iur interface every 15s. At the end of the measurement period, the system obtains
Issue 03 (2015-06-30)

3827
BSC6900 UMTS
the average value by dividing the accumulated value by the number of sampling times and uses
the maximum sampled value as the maximum value.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
CS.DATA.MAX
WRFD-040100
Flow Control
CS.DATA.MEAN
WRFD-040100
Flow Control
Online CS Voice Traffic of Interface Boards for Iur-p Interface

Counters
Counter ID
Counter Name
Counter Description
73428485
VS.INT.TRM.ADMIT.IUR
P.CS.VOICE.MAX

for Iur-p Interface
73444367
P.CS.VOICE.MEAN

for Iur-p Interface
Description
online CS voice traffic and average online CS voice traffic of interface boards over the Iur-p
interface.
Measurement point
interface board over the Iur-p interface every 15s. At the end of the measurement period, the
Issue 03 (2015-06-30)

3828
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
P.CS.VOICE.MAX
WRFD-040100
Flow Control
P.CS.VOICE.MEAN
WRFD-040100
Flow Control
Online CS Data Traffic of Interface Boards for Iur-p Interface

Counters
Counter ID
Counter Name
Counter Description
73428488
P.CS.DATA.MAX

for Iur-p Interface
73444368
P.CS.DATA.MEAN

for Iur-p Interface
Description
online CS data traffic and average online CS data traffic of interface boards over the Iur-p
interface.
Measurement point
board over the Iur-p interface every 15s. At the end of the measurement period, the system
Formula
None
Issue 03 (2015-06-30)

3829
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
P.CS.DATA.MAX
WRFD-040100
Flow Control
P.CS.DATA.MEAN
WRFD-040100
Flow Control
Transport Resource Usage of Interface Boards

Counters
Counter ID
Counter Name
Counter Description
73428509
VS.INT.TRM.ADMIT.RES
USAGE.MAX
Maximum Transport
Resource Usage of Interface
Boards
73444375
USAGE.MEAN
Average Transport Resource

Usage of Interface Boards
Description
of subscribers and subscriber bandwidths on interface boards over different interfaces. These
counters provide the maximum transmission resource usage and average transmission resource
usage. The transmission usage is the total usage of transmission resources occupied by different
services (CS voice/CS data/PS) over different interfaces (Iub/Iur/Iurp/Iu).
Measurement point
In a measurement period, the system automatically samples the transmission resource usage on
an interface board every 15s. At the end of the measurement period, the system obtains the
average value by dividing the accumulated value by the number of sampling times and uses the
Formula
None
Unit
%
Issue 03 (2015-06-30)

3830
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
USAGE.MAX
WRFD-040100
Flow Control
USAGE.MEAN
WRFD-040100
Flow Control
2.17.2 Interface Board Flow Resource Usage Measurement

(INT.TRM.FLOW)
Overview
The counters in this function subset provide the usage of flow resources on interface boards over
different interfaces, such as the Iub, Iur, Iur-p, and Iu interfaces. Such flow resources include
the number of occupied CIDs, the number of occupied UDP ports, and the number of occupied
TEIDs.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73428512
VS.INT.TRM.FLO
W.UDP.MAX
Maximum Number
of Occupied UDP
Ports of Interface
Boards
BSC6900
V900R016C00
73444376
VS.INT.TRM.FLO
W.UDP.MEAN
Average Number of
Occupied UDP Ports
of Interface Boards
BSC6900
V900R016C00
73428515
VS.INT.TRM.FLO
W.CID.MAX
Maximum Number
of Occupied CIDs of
Interface Boards
BSC6900
V900R016C00
73444377
VS.INT.TRM.FLO
W.CID.MEAN
Average Number of
Occupied CIDs of
Interface Boards
BSC6900
V900R016C00
73428518
VS.INT.TRM.FLO
W.TEID.MAX
Maximum Number
of Occupied TEIDs
of Interface Boards
BSC6900
V900R016C00
73444378
VS.INT.TRM.FLO
W.TEID.MEAN
Average Number of
Occupied TEIDs of
Interface Boards
BSC6900
V900R016C00

3831
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73428817
VS.INT.TRM.FLO
W.UDP.RESUSAG
E.MAX
Maximum Usage of
UDP Ports of
Interface Boards
BSC6900
V900R016C00
73428821
VS.INT.TRM.FLO
W.CID.RESUSAG
E.MAX
Maximum Usage of
CID of Interface
Boards
BSC6900
V900R016C00
73444453
VS.INT.TRM.FLO
W.CID.RESUSAG
E.MEAN
Average Usage of
CID of Interface
Boards
BSC6900
V900R016C00
73428824
VS.INT.TRM.FLO
W.TEID.RESUSA
GE.MAX
Maximum Usage of
TEIDs of Interface
Boards
BSC6900
V900R016C00
73444454
VS.INT.TRM.FLO
W.TEID.RESUSA
GE.MEAN
Average Usage of
TEIDs of Interface
Boards
BSC6900
V900R016C00
73444455
VS.INT.TRM.FLO
W.UDP.RESUSAG
E.MEAN
Average Usage of
UDP Ports of
Interface Boards
BSC6900
V900R016C00
None
Number of Occupied UDP Ports of Interface Boards

Counters
Counter ID
Counter Name
Counter Description
73428512
VS.INT.TRM.FLOW.UDP.
MAX
Maximum Number of
Occupied UDP Ports of
Interface Boards
73444376
MEAN
Average Number of
Occupied UDP Ports of
Interface Boards
Description
These counters provide the maximum or average number of UDP ports on an IP interface board
in a specified measurement period. These counters reflect the usage of UDP ports on the IP
interface board. When services access the network, UDP ports must be allocated to the IP
Issue 03 (2015-06-30)

3832
BSC6900 UMTS
interface board for service processing. In normal situations, if the maximum number of UDP
ports on an interface board increases, the maximum traffic volume on the interface board
increases. If the average number of UDP ports on an interface board increases, the traffic volume
on the interface board increases. These counters are not measured for ATM interface boards.
Measurement point
In a measurement period, the system automatically samples the number of UDP ports on an
interface board every 15s. At the end of the measurement period, the system divides the
accumulated value by the sampling times to obtain the average number of UDP ports and uses
the maximum sampled value as the maximum number of UDP ports.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
MAX
WRFD-040100
Flow Control
MEAN
WRFD-040100
Flow Control
Number of Occupied CIDs of Interface Boards

Counters
Counter ID
Counter Name
Counter Description
73428515
VS.INT.TRM.FLOW.CID.
MAX
Maximum Number of
Occupied CIDs of Interface
Boards
73444377
MEAN
Average Number of
Occupied CIDs of Interface
Boards
Description
These counters provide the maximum or average number of CIDs on an ATM interface board
in a specified measurement period. These counters reflect the CID usage on the IP interface
board. When services access the network, CID resources must be allocated to the ATM interface
Issue 03 (2015-06-30)

3833
BSC6900 UMTS
board for service processing. In normal situations, if the maximum number of CIDs on an
interface board increases, the maximum traffic volume on the interface board increases. If the
average number of CIDs on an interface board increases, the traffic volume on the interface
board increases. These counters are not measured for IP interface boards.
Measurement point
In a measurement period, the system automatically samples the number of CIDs on an interface
board every 15s. At the end of the measurement period, the system divides the accumulated
value by the sampling times to obtain the average number of CIDs and uses the maximum
sampled value as the maximum number of CIDs.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
MAX
WRFD-040100
Flow Control
MEAN
WRFD-040100
Flow Control
Number of Occupied TEIDs of Interface Boards

Counters
Counter ID
Counter Name
Counter Description
73428518
VS.INT.TRM.FLOW.TEID.
MAX
Maximum Number of
Occupied TEIDs of Interface
Boards
73444378
MEAN
Average Number of
Occupied TEIDs of Interface
Boards
Description
These counters provide the maximum or average number of TEIDs on an interface board in a
specified measurement period. These counters reflect the TEID usage on the interface board.
When services access the network, TEID resources must be allocated to the interface board for
Issue 03 (2015-06-30)

3834
BSC6900 UMTS
service processing. In normal situations, if the maximum number of TEIDs on an interface board
increases, the maximum traffic volume on the interface board increases. If the average number
of TEIDs on an interface board increases, the traffic volume on the interface board increases.
Measurement point
In a measurement period, the system automatically samples the number of TEIDs on an interface
value by the sampling times to obtain the average number of TEIDs and uses the maximum
sampled value as the maximum number of TEIDs.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
MAX
WRFD-040100
Flow Control
MEAN
WRFD-040100
Flow Control
Usage of UDP Ports of Interface Boards

Counters
Counter ID
Counter Name
Counter Description
73428817
RESUSAGE.MAX
Maximum Usage of UDP

Ports of Interface Boards
73444455
RESUSAGE.MEAN
Average Usage of UDP Ports

of Interface Boards
Description
These counters provide the maximum or average usage of UDP ports on an IP interface board
in a specified measurement period. These counters reflect the usage of UDP ports on the IP
interface board. When services access the network, UDP ports must be allocated to the IP
interface board for service processing. In normal situations, if the maximum usage of UDP ports
on an interface board increases, the maximum traffic volume on the interface board increases.
Issue 03 (2015-06-30)

3835
BSC6900 UMTS
If the average usage of UDP ports on an interface board increases, the traffic volume on the
interface board increases. These counters are not measured for ATM interface boards.
Measurement point
In a measurement period, the system automatically samples the UDP port usage on an interface
value by the sampling times to obtain the average UDP port usage and uses the maximum
sampled value as the maximum UDP port usage.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
RESUSAGE.MAX
WRFD-040100
Flow Control
RESUSAGE.MEAN
WRFD-040100
Flow Control
Counter ID
Counter Name
Counter Description
73428821
RESUSAGE.MAX
Maximum Usage of CID of

Interface Boards
73444453
RESUSAGE.MEAN
Average Usage of CID of

Interface Boards
Usage of CID of Interface Boards

Counters
Description
These counters provide the maximum or average usage of CIDs on an ATM interface board in
a specified measurement period. These counters reflect the CID usage on the IP interface board.
When services access the network, CID resources must be allocated to the ATM interface board
for service processing. In normal situations, if the maximum usage of CIDs on an interface board
increases, the maximum traffic volume on the interface board increases. If the average usage of
CIDs on an interface board increases, the traffic volume on the interface board increases. These
counters are not measured for IP interface boards.
Issue 03 (2015-06-30)

3836
BSC6900 UMTS
Measurement point
In a measurement period, the system automatically samples the CID usage on an interface board
every 15s. At the end of the measurement period, the system divides the accumulated value by
the sampling times to obtain the average CID usage and uses the maximum sampled value as
the maximum CID usage.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
RESUSAGE.MAX
WRFD-040100
Flow Control
RESUSAGE.MEAN
WRFD-040100
Flow Control
Counter ID
Counter Name
Counter Description
73428824
RESUSAGE.MAX
Maximum Usage of TEIDs

of Interface Boards
73444454
RESUSAGE.MEAN
Average Usage of TEIDs of

Interface Boards
Usage of TEIDs of Interface Boards

Counters
Description
These counters provide the maximum or average usage of TEIDs on an interface board in a
specified measurement period. These counters reflect the TEID usage on the interface board.
When services access the network, TEID resources must be allocated to the interface board for
service processing. In normal situations, if the maximum usage of TEIDs on an interface board
increases, the maximum traffic volume on the interface board increases. If the average usage of
TEIDs on an interface board increases, the traffic volume on the interface board increases.
Measurement point
In a measurement period, the system automatically samples the TEID usage on an interface
Issue 03 (2015-06-30)

3837
BSC6900 UMTS
value by the sampling times to obtain the average TEID usage and uses the maximum sampled
value as the maximum TEID usage.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
RESUSAGE.MAX
WRFD-040100
Flow Control
RESUSAGE.MEAN
WRFD-040100
Flow Control
2.18 Measurement of IPoA Link Performance(IPOALNK)

Overview
IP over ATM (IPoA) is a technique used to transmit IP data packets over ATM links. It defines
the criterion that IP data communication is implemented using switched virtual circuits (SVCs)
between ATM UEs on the ATM network. Measurement of IPoA Link Performance indicates
the transmission quality of the IPoA links in the ATM layer on the AEUa, AOUa, UOIa, AOUc
or UOIc.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IPOALNK
IPoA Link Measurement
2.18.1 IPoA Link Measurement(IPOALNK)

Overview
Transmission links are important resources of the Base Station Controller system. The quality
of the transmission links directly affects the system performance. Therefore, you can take
statistics of the traffic in the ATM layer on the transmission links based on the IPoA link
measurement. This is to analyze the transmission quality of and maintain the stable and secure
operation of the system. This function subset takes effect after an IPoA link is added.
Figure 1 shows the location of the ATM Layer in the procotol.
Issue 03 (2015-06-30)

3838
BSC6900 UMTS
The configuration structure is as shown in the figure 2. If ATM configuration objects are used
for transmission on an IP network, these objects must be carried over IPoA links. According to
the TCP/IP protocol structure, IPoA links complete the mapping between IP addresses and
hardware addresses (ATM addresses), and encapsulate and send data packets. In addition, they
receive data packets and send them to the corresponding module.
Issue 03 (2015-06-30)

3839
BSC6900 UMTS
Figure 2-41 Physical bearer of the IPOA Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194073
VS.IPOALNK.RX
CORRECTCELLS
Number of Correct
Cells Received on
the IPoA Link
Earlier than
BSC6900
V900R011
67194074
VS.IPOALNK.RX
BYTES
Number of Bytes
Received on an IPoA
Link
Earlier than
BSC6900
V900R011
67204471
VS.IPOALNK.PE
AK.RXRATE
Maximum Receive
Rate of an IPoA Link
Earlier than
BSC6900
V900R011
67194076
VS.IPOALNK.TX
CORRECTCELLS
Number of Correct
an IPoA Link
Earlier than
BSC6900
V900R011
67194077
VS.IPOALNK.TX
BYTES
Number of Bytes
Transmitted on an
IPoA Link
Earlier than
BSC6900
V900R011

3840
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204472
VS.IPOALNK.PE
AK.TXRATE
Maximum Transmit
Rate of an IPoA Link
Earlier than
BSC6900
V900R011
67194079
VS.IPOALNK.DR
OPFORHEADCE
LLS
Number of Cells
Discarded on an
IPoA Link Due to
Packet Header Error
Earlier than
BSC6900
V900R011
67194080
VS.IPOALNK.DR
OPFORRXOVER
FLOWCELLS
Number of Cells
Discarded on an
IPoA Link Due to the
Overflow of the input
Buffer
Earlier than
BSC6900
V900R011
67194081
VS.IPOALNK.DR
OPFORTXOVERF
LOWCELLS
Number of Cells
Discarded on an
IPoA Link Due to the
Overflow of the
output Buffer
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of Cells Received or Transmitted Correctly on An

IPoA Link
Counters
Counter ID
Counter Name
Counter Description
67194073
VS.IPOALNK.RXCORRECTCELLS
Number of Correct Cells

Received on the IPoA Link
67194076
VS.IPOALNK.TXCORRECTCELLS
Number of Correct Cells

Transmitted on an IPoA Link
Description
These counters provide the number of cells received or transmitted correctly on an IPoA link at
the ATM layer in the specified measurement period. They indicate the traffic volume of the
IPoA link.
Issue 03 (2015-06-30)

3841
BSC6900 UMTS
Measurement point
the number of IEs successfully transmitted and received on the link once every five seconds and
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IPOALNK.RXCORRECTCELLS
WRFD-05030105
Permanent AAL5
Connections for Control
Plane Traffic
VS.IPOALNK.TXCORRECTCELLS
WRFD-05030105
Permanent AAL5
Plane Traffic
Counters Related to the Number of Bytes Received or Transmitted on an IPoA Link

Counters
Counter ID
Counter Name
Counter Description
67194074
VS.IPOALNK.RXBYTES

on an IPoA Link
67194077
VS.IPOALNK.TXBYTES
Number of Bytes
Transmitted on an IPoA Link
Description
These counters provide the number of bytes received or transmitted on an IPoA link at the ATM
layer in the specified measurement period. They indicate the traffic volume of the IPoA link.
Measurement point
the number of bytes transmitted and received on the link once every five seconds and obtains
the total number of one measurement period.
Issue 03 (2015-06-30)

3842
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IPOALNK.RXBYTES
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.IPOALNK.TXBYTES
WRFD-05030105
Permanent AAL5
Plane Traffic
Counters Related to the Maximum Receive Rate or the Maximum Transmit Rate of
an IPoA Link
Counters
Counter ID
Counter Name
Counter Description
67204471
VS.IPOALNK.PEAK.RXR
ATE

an IPoA Link
67204472
VS.IPOALNK.PEAK.TXR
ATE

an IPoA Link
Description
These counters provide the maximum receive rate or the maximum transmit rate of an IPoA link
at the ATM layer in the specified measurement period. They indicate the maximum load on the
IPoA link.
Measurement point
system obtains the maximum number of bytes received or transmitted in five seconds. The
maximum speed is calculated with the maximum bytes in five seconds.
Formula
None
Issue 03 (2015-06-30)

3843
BSC6900 UMTS
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.IPOALNK.PEAK.RXR
ATE
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.IPOALNK.PEAK.TXR
ATE
WRFD-05030105
Permanent AAL5
Plane Traffic
Counters Related to the Number of Cells Discarded on an IPoA Link

Counters
Counter ID
Counter Name
Counter Description
67194079
VS.IPOALNK.DROPFORHEADCELLS

on an IPoA Link Due to
Packet Header Error
67194080
VS.IPOALNK.DROPFORRXOVERFLOWCELLS

on an IPoA Link Due to the
Overflow of the input Buffer
67194081
VS.IPOALNK.DROPFORTXOVERFLOWCELLS

on an IPoA Link Due to the
Overflow of the output
Buffer
Description
These counters provide the number of cells discarded on an IPoA link at the ATM layer in the
specified measurement period from different perspectives. They indicate the transmission
quality of the cells on the IPoA link.
Measurement point
the number of IEs discarded on the link once every five seconds and obtains the total number
Issue 03 (2015-06-30)

3844
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IPOALNK.DROPFORHEADCELLS
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.IPOALNK.DROPFORRXOVERFLOWCELLS
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.IPOALNK.DROPFORTXOVERFLOWCELLS
WRFD-05030105
Permanent AAL5
Plane Traffic
2.19 Measurement of IPoAPVC VCL PM Performance

(IPOAPVC_VCLPM)
Overview
Measurement of IPoAPVC VCL PM Performance provides the statistics of PM on the ATM
layer of the IPoAPVC link for the AOUc and UOIc boards. The IPoAPVC PM function uses
forward performance monitoring (FPM) and backward reporting (BR) cells to monitor the
number of transmitted and received cells at both ends of the ATM layer on the IPoAPVC link.
Before viewing the IPoAPVC PM result, run the ACT VCLPM command to activate the PM
function on the IPoAPVC link.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
IPOAPVC.VCLPM
IPoAPVC VCL PM Measurement

3845
BSC6900 UMTS
2.19.1 IPoAPVC VCL PM Measurement(IPOAPVC.VCLPM)

Overview
This measurement uses FPM and BR cells to monitor the ATM transmission quality of a path.
In the source direction, FPM cells are sent periodically to indicate the number of transmitted
cells and the number of error cells that failed the Bit Interleaved Parity 16 (BIP16) check. In the
sink direction, BR cells are transmitted as response to the FPM cells. The BR cells calculate the
number of received cells and the number of error cells that fail the BIP16 check. In the source
direction, BR cells are used to calculate the number of discarded cells and the number of cells
that are inserted by mistake. In the sink direction, FPM cells are used to calculate the number
of discarded cells and the number of cells that are inserted by mistake.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441412
VS.IPOAPVC.VC
LPM.RXCELL
Number of Received
VCL PM Cells on an
IPOAPVC link
BSC6900
V900R014
73441413
VS.IPOAPVC.VC
LPM.TXCELL
Number of
Transmitted VCL
PM Cells on an
IPOAPVC link
BSC6900
V900R014
73441414
VS.IPOAPVC.VC
LPM.PEAK.RXRA
TE
Maximum Receive
Rate of VCL PM on
an IPOAPVC link
BSC6900
V900R014
73441415
VS.IPOAPVC.VC
LPM.PEAK.TXRA
TE
Maximum Transmit
Rate of VCL PM on
an IPOAPVC link
BSC6900
V900R014
73441416
VS.IPOAPVC.VC
LPM.RX.MEAN.L
OSTCELLRATE
Average VCL PM
the Receive
Direction of an
IPOAPVC link
BSC6900
V900R014
73441417
VS.IPOAPVC.VC
LPM.RX.PEAK.L
OSTCELLRATE
Maximum VCL PM
the Receive
Direction of an
IPOAPVC link
BSC6900
V900R014
73441418
VS.IPOAPVC.VC
LPM.TX.MEAN.L
OSTCELLRATE
Average VCL PM
the Transmit
Direction of an
IPOAPVC link
BSC6900
V900R014

3846
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73441419
VS.IPOAPVC.VC
LPM.TX.PEAK.L
OSTCELLRATE
Maximum VCL PM
the Transmit
Direction of an
IPOAPVC link
BSC6900
V900R014
73441420
VS.IPOAPVC.VC
LPM.RX.MEAN.E
RRINSERTCELL
RATE
Average Rate of
VCL PM Cells in the
an IPOAPVC link
BSC6900
V900R014
73441421
VS.IPOAPVC.VC
LPM.RX.PEAK.E
RRINSERTCELL
RATE
Maximum Rate of
VCL PM Cells in the
an IPOAPVC link
BSC6900
V900R014
73441422
VS.IPOAPVC.VC
LPM.TX.MEAN.E
RRINSERTCELL
RATE
Average Rate of
VCL PM Cells in the
Transmit Direction
of an IPOAPVC link
BSC6900
V900R014
73441423
VS.IPOAPVC.VC
LPM.TX.PEAK.E
RRINSERTCELL
RATE
Maximum Rate of
VCL PM Cells in the
Transmit Direction
of an IPOAPVC link
BSC6900
V900R014
73424558
VS.IPOAPVC.VC
LPM.SOURCEBIP
16CRCERRCELL
Number of VCL PM
Error Cell Blocks
Failed the BIP16
Check in the Source
Direction of an
IPOAPVC link
BSC6900
V900R014
73424559
VS.IPOAPVC.VC
LPM.SINKBIP16C
RCERRCELL
Number of VCL PM
Error Cell Blocks
Failed the BIP16
Check in the Sink
Direction of an
IPOAPVC link
BSC6900
V900R014
None
Issue 03 (2015-06-30)

3847
BSC6900 UMTS
Number of VCL PM Cells on an IPOAPVC link

Counters
Counter ID
Counter Name
Counter Description
73441412
VS.IPOAPVC.VCLPM.RX
CELL

PM Cells on an IPOAPVC
link
73441413
VS.IPOAPVC.VCLPM.TX
CELL

PM Cells on an IPOAPVC
link
Description
These counters provide the number of received and transmitted cells at the ATM layer along an
IPOAPVC link. Only ATM cells are calculated.
Measurement point
number of cells transmitted at the ATM layers along an IPOAPVC link every 5 seconds and
measures the total number at the end of each measurement period.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPOAPVC.VCLPM.RX
CELL
WRFD-05030110
F5
VS.IPOAPVC.VCLPM.TX
CELL
WRFD-05030110
F5

3848
BSC6900 UMTS
Maximum Data Rate of VCL PM on an IPOAPVC link

Counters
Counter ID
Counter Name
Counter Description
73441414
VS.IPOAPVC.VCLPM.PE
AK.RXRATE

VCL PM on an IPOAPVC
link
73441415
VS.IPOAPVC.VCLPM.PE
AK.TXRATE

VCL PM on an IPOAPVC
link
Description
These counters provide the maximum receive and transmit rates on an IPOAPVC link, indicating
the maximum load in the receive and transmit directions on an IPOAPVC link.
Measurement point
number of cells received and transmitted at the ATM layer along an IPOAPVC link every 5
seconds. It compares and obtains the maximum number of received and transmitted cells per 5
seconds within a measurement period and accordingly calculates the maximum receive and
transmit rates. The counters are in the unit of kbit/s, and are calculated with the following
formula: Maximum receive and transmit rates = Maximum number of received/transmitted cells
x 53 x 8/5/1000.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPOAPVC.VCLPM.PE
AK.RXRATE
WRFD-05030110
F5
VS.IPOAPVC.VCLPM.PE
AK.TXRATE
WRFD-05030110
F5

3849
BSC6900 UMTS
VCL PM Cell Discard Rate on an IPOAPVC link

Counters
Counter ID
Counter Name
Counter Description
73441416
VS.IPOAPVC.VCLPM.RX.
MEAN.LOSTCELLRATE
Average VCL PM Cell

Direction of an IPOAPVC
link
73441417
PEAK.LOSTCELLRATE
Maximum VCL PM Cell

link
73441418
VS.IPOAPVC.VCLPM.TX.
MEAN.LOSTCELLRATE
Average VCL PM Cell

link
73441419
PEAK.LOSTCELLRATE
Maximum VCL PM Cell

link
Description
These counters provide the average and maximum rates of cells that are discarded in the receive
and transmit directions on an IPOAPVC link. They are used to monitor the error rate of
transmission cells on an IPOAPVC link.
Measurement point
and transmit directions at the ATM layers along an IPOAPVC link and compares to obtain the
directions.
Formula
None
Unit
%
Issue 03 (2015-06-30)

3850
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
MEAN.LOSTCELLRATE
WRFD-05030110
F5
PEAK.LOSTCELLRATE
WRFD-05030110
F5
MEAN.LOSTCELLRATE
WRFD-05030110
F5
PEAK.LOSTCELLRATE
WRFD-05030110
F5
Rate of Incorrectly Inserted VCL PM Cells on an IPOAPVC link

Counters
Counter ID
Counter Name
Counter Description
73441420
MEAN.ERRINSERTCELLRATE

Receive Direction of an
IPOAPVC link
73441421
PEAK.ERRINSERTCELLRATE
Maximum Rate of
link
73441422

Transmit Direction of an
IPOAPVC link
73441423
Maximum Rate of
link
Description
These counters provide the average and maximum rates of cells that are incorrectly inserted in
the receive and transmit directions on an IPOAPVC link. They are used to monitor the error rate
of transmission cells on an IPOAPVC link.
Issue 03 (2015-06-30)

3851
BSC6900 UMTS
Measurement point
receive and transmit directions at the ATM layers along an IPOAPVC link and compares to
obtain the maximum number. To obtain the maximum rates of incorrectly inserted cells in the
receive and transmit directions, in each direction, the RNC divides the maximum number of
cells that are incorrectly inserted within 5 seconds by the total number of cells measured in those
directions during the same period. To obtain the average rates of incorrectly inserted cells in the
receive and transmit directions, in each direction, the RNC divides the total number of incorrectly
period.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-05030110
F5
WRFD-05030110
F5
WRFD-05030110
F5
WRFD-05030110
F5

3852
BSC6900 UMTS
Number of Error VCL PM Cell Blocks Failed BIP16 Check on an IPOAPVC link
Counters
Counter ID
Counter Name
Counter Description
73424558
VS.IPOAPVC.VCLPM.SO
URCEBIP16CRCERRCELL

Check in the Source
link
73424559
VS.IPOAPVC.VCLPM.SIN
KBIP16CRCERRCELL

of an IPOAPVC link
Description
and transmit directions on an IPOAPVC link. They are used to monitor the end-to-end error rate
of transmission cells on an IPOAPVC link.
Measurement point
ATM layer along an IPOAPVC link every 5 seconds and calculates the total number at the end
of each measurement period. In each cell block measured for this counter, none of the cells is
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPOAPVC.VCLPM.SO
URCEBIP16CRCERRCELL
WRFD-05030110
F5
VS.IPOAPVC.VCLPM.SIN
KBIP16CRCERRCELL
WRFD-05030110
F5

3853
BSC6900 UMTS
2.20 Measurement of IP Path Performance(IPPATH)

Overview
IP path is an important transmission resource. It carries the user plane data between the BSC6900
and other equipment. Measurement of IP Path Performance provides measurement on IP
transmission links.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IPPATH
IPPath Measurement
2.20.1 IPPath Measurement(IPPATH)

Overview
IP path is a logical channel used to carry user plane data on the base station controller and other
adjacent nodes. IP path quality affects service setup and user experience. IP Path Measurement
is used to monitor connections, congestion, ping delay, and packet loss on an IP path. Therefore,
it helps analyze IP path measurement and statistics and ensures system stability and reliability.
Figure 2-42 Physical bearer of the IP path
Issue 03 (2015-06-30)

3854
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204207
VS.IPPATH.Act.C
on
T6551:Number of
Active Connections
on an IP Path
Earlier than
BSC6900
V900R011
67204390
VS.IPPATH.PING.
MeanDELAY
T6552:Average IP
Path Ping Delay
Earlier than
BSC6900
V900R011
67194636
VS.IPPATH.PING.
MaxDELAY
T6553:Maximum IP
Path Ping Delay
Earlier than
BSC6900
V900R011
67204391
VS.IPPATH.PING.
MeanJITTER
T6554:Average IP
Path Ping Delay
variation
Earlier than
BSC6900
V900R011
67194639
VS.IPPATH.PING.
MaxJITTER
T6555:Maximum IP
Path Ping Delay
variation
Earlier than
BSC6900
V900R011
67204392
VS.IPPATH.PING.
MeanLOST
T6556:Average IP
Path Ping Packet
Loss Rate
Earlier than
BSC6900
V900R011
67194642
VS.IPPATH.PING.
MaxLOST
T6557:Maximum IP
Path Ping Packet
Loss Rate
Earlier than
BSC6900
V900R011
67195599
VS.IPPATH.Fwd.C
ong
T6558:Number of
Forward
Congestions on the
IP Path
Earlier than
BSC6900
V900R011
67195600
VS.IPPATH.Fwd.C
ong.Dur
T6559:Duration of
Forward Congestion
on the IP Path
Earlier than
BSC6900
V900R011
67195601
VS.IPPATH.Bwd.
Cong
T6560:Number of
Backward
Congestions on the
IP Path
Earlier than
BSC6900
V900R011
67195602
VS.IPPATH.Bwd.
Cong.Dur
T6561:Duration of
Backward
Congestion on the IP
PATH
Earlier than
BSC6900
V900R011

3855
BSC6900 UMTS
None
Number of Active Connections on an IP Path

Counters
Counter ID
Counter Name
Counter Description
67204207
VS.IPPATH.Act.Con
T6551:Number of Active
Connections on an IP Path
Description
This counter provides the number of active connections on an IP path in a specified measurement
period. It indicates the connection status on a single IP path. When the system is configured with
IP paths and IP services access the system, active connections are required for these IP paths.
In normal situations, an increase in the number of active connections indicates an increase in
the number of active connections on an IP path.
Measurement point
In a measurement period, the system automatically samples the number of active connections
on an IP path every 15 seconds. At the end of the measurement period, the system divides the
accumulated active connections by the number of samples to obtain the average number of active
connections.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.Act.Con
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3856
BSC6900 UMTS
Average IP Path Ping Delay

Counters
Counter ID
Counter Name
Counter Description
67204390
VS.IPPATH.PING.MeanDELAY
T6552:Average IP Path Ping

Delay
Description
When the IP path ping function is enabled, the base station controller periodically sends the IP
path ping request packet to the peer adjacent node and receives the acknowledgement packet
from the peer adjacent node. The sending frequency of ping packets is determined by the
PERIOD parameter of the IPPATH object. This counter provides the average two-way delay
between sending the ping request packet and receiving the acknowledgement packet. It is used
to monitor the delay changes on end-to-end IP paths between the base station controller and the
peer adjacent node. In normal situation, a large average delay indicates congestion on the
transmission path. The congestion can be relieved until packet loss occurs on the network. This
counter can also reflect the congestion on an IP path. It takes effect only when the IP path ping
function is enabled. When the ping packet loss rate of an IP path reaches 100%, this counter has
no reference value. The formula is as follow: Delay of ping request n = Receive time of packet
n - Send time of packet n (unit:ms)
Measurement point
In a measurement period, the system automatically samples the IP path ping delay every 5
minutes. At the end of the measurement period, the system divides the accumulated IP path ping
delay by the number of samples to obtain the average IP path ping delay.
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.PING.MeanDELAY
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3857
BSC6900 UMTS
Maximum IP Path Ping Delay

Counters
Counter ID
Counter Name
Counter Description
67194636
VS.IPPATH.PING.MaxDELAY
T6553:Maximum IP Path
Ping Delay
Description
PERIOD parameter of the IPPATH object. This counter provides the maximum two-way delay
between sending the ping request packet and receiving the acknowledgement packet in a
specified measurement period. It is used to monitor the maximum delay on end-to-end IP paths
between the base station controller and the peer adjacent node. It takes effect only when the IP
path ping function is enabled. When the ping packet loss rate of an IP path reaches 100%, this
counter has no reference value.
Measurement point
This counter takes effect only when an IP path is configured and the IP path ping function is
enabled. In a measurement period, the system automatically samples the IP path ping delay every
5 minutes uses the maximum ping delay as the value of this counter.
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.PING.MaxDELAY
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3858
BSC6900 UMTS
Average IP Path Ping Delay Variation

Counters
Counter ID
Counter Name
Counter Description
67204391
VS.IPPATH.PING.MeanJITTER

Delay variation
Description
PERIOD parameter of the IPPATH object. This counter provides the average two-way delay
variation between sending a ping packet and receiving an acknowledgement packet on an IP
path in a specified measurement period. It is used to monitor the delay changes on end-to-end
IP paths between the base station controller and the peer adjacent node. In normal situations, a
large average delay variation indicates poor transmission quality on the IP path. This counter
can also reflect the transmission quality stability on an IP path. It takes effect only when the IP
path ping function is enabled. When the ping packet loss rate of an IP path reaches 100%, this
counter has no reference value. The definition of the delay variation is as follows (from RFC1889
[Page 27]):
If Si is the RTP timestamp of packet i, and Ri is the time of arrival in RTP timestamp units for
packet i, then for two packets i and j, D may be expressed as follows:
D(i, j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si)
The arrival variation is calculated continuously as each data packet i is received from source
SSRC_n, using this difference D for that packet and the previous packet i-1 in order of arrival
(not necessarily in sequence), according to the following formula:
J = J + (|D(i-1,i)|-J)/16
Whenever a reception report is issued, the current value of J is sampled.
The variation calculation provided here allows protocol-independent monitors to make valid
explanations of reports coming from different implementations. This algorithm is the optimal
first-order estimation and the gain parameter 1/16 provides a good noise reduction ratio while
maintaining a reasonable rate of convergence.
Measurement point
This counter takes effect only when an IP path is configured and the IP path ping function is
enabled. In a measurement period, the system automatically samples the IP path ping delay
variation every 5 minutes and uses the average IP path ping delay variation as the value of this
counter.
Formula
None
Issue 03 (2015-06-30)

3859
BSC6900 UMTS
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.PING.MeanJITTER
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Maximum IP Path Ping Delay Variation

Counters
Counter ID
Counter Name
Counter Description
67194639
VS.IPPATH.PING.MaxJITTER
Ping Delay variation
Description
PERIOD parameter of the IPPATH object. This counter provides the maximum two-way delay
variation between sending a ping packet and receiving an acknowledgement packet on an IP
path in a specified measurement period. It is used to monitor the delay changes on end-to-end
IP paths between the base station controller and the peer adjacent node. In normal situations, a
large maximum delay variation indicates transmission instability on the IP path. It takes effect
only when the IP path ping function is enabled. When the ping packet loss rate of an IP path
reaches 100%, this counter has no reference value.
Measurement point
In a measurement period, the system samples the ping delay variation every 5 minutes and uses
the maximum ping delay variation as the value of this counter.
Formula
None
Issue 03 (2015-06-30)

3860
BSC6900 UMTS
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.PING.MaxJITTER
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Average IP Path Ping Packet Loss Rate

Counters
Counter ID
Counter Name
Counter Description
67204392
VS.IPPATH.PING.MeanLOST

Packet Loss Rate
Description
PERIOD parameter of the IPPATH object. This counter provides the average packet loss rate
of an IP path in a specified measurement period. It is used to monitor the transmission quality
and changes on end-to-end IP paths between the base station controller and the peer adjacent
node. In normal situations, a high average packet loss rate indicates poor transmission quality
on the IP path. This counter can also reflect the congestion on an IP path. It takes effect only
when the IP path ping function is enabled. When the packet loss rates of many IP paths reach
100%, services are affected.
Measurement point
In a measurement period, the system automatically samples the number of IP path ping request
packets and the number of unreceived acknowledgement packets every 5 minutes and obtains
the packet loss rate according to the ratio of the number of unreceived acknowledgement packets
to the number of IP path ping request packets. At the end of the measurement period, the system
uses the average packet loss rate of IP paths as the value of this counter. The display precision
of this counter is 1%, and therefore it is displayed as an integer.
Issue 03 (2015-06-30)

3861
BSC6900 UMTS
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.PING.MeanLOST
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Maximum IP Path Ping Packet Loss Rate

Counters
Counter ID
Counter Name
Counter Description
67194642
VS.IPPATH.PING.MaxLOST
Ping Packet Loss Rate
Description
PERIOD parameter of the IPPATH object. This counter provides the maximum packet loss rate
of an IP path in a specified measurement period. It is used to monitor the transmission quality
and changes on end-to-end IP paths between the base station controller and the peer adjacent
node. In normal situations, a high maximum packet loss rate indicates poor transmission quality
on the IP path. It takes effect only when the IP path ping function is enabled.
Measurement point
In a measurement period, the system automatically samples the number of sent ping packets and
the number of unreceived acknowledgement packets every 5 minutes and obtains the packet loss
rate according to the ratio of the number of unreceived acknowledgement packets to the number
of sent ping packets. At the end of the measurement period, the system uses the maximum packet
loss rate as the value of this counter. The display precision of this counter is 1%, and therefore
it is displayed as an integer.
Issue 03 (2015-06-30)

3862
BSC6900 UMTS
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.PING.MaxLOST
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Counters Related to the Number of Congestions on an IP Path

Counters
Counter ID
Counter Name
Counter Description
67195599
VS.IPPATH.Fwd.Cong
T6558:Number of Forward
Congestions on the IP Path
67195601
VS.IPPATH.Bwd.Cong
T6560:Number of Backward
Congestions on the IP Path
Description
When services using IP transmission access the network, if the remaining bandwidth is less than
or equal to the congestion remaining threshold configured for an IP path, traffic on the IP path
is congested. Users can configure the congestion remaining threshold according to the actual
counters provide the number of forward or backward bandwidth admission congestions on an
IP path in a specified measurement period. The forward direction indicates the TX direction,
and the backward direction indicates the RX direction. These counters can be used together with
the duration of IP path congestion to observe the congestion. If traffic on many IP paths is
congested for a long time, services are affected. These counters become ineffective when the
actual flow admission is enabled.
Issue 03 (2015-06-30)

3863
BSC6900 UMTS
Measurement point
In a measurement period, the RNC checks the state of an IP path each time a service is being
admitted to that path. The counter value is incremented by one each time the state of the IP path
changes from non-congestion to congestion.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.Fwd.Cong
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.IPPATH.Bwd.Cong
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Counters Related to the Duration of Congestion on an IP Path

Counters
Counter ID
Counter Name
Counter Description
67195600
VS.IPPATH.Fwd.Cong.Dur
T6559:Duration of Forward
Congestion on the IP Path
67195602
VS.IPPATH.Bwd.Cong.Dur
T6561:Duration of
Backward Congestion on the
IP PATH
Description
When services using IP transmission access the network, if the remaining bandwidth is less than
or equal to the congestion remaining threshold configured for an IP path, traffic on the IP path
Issue 03 (2015-06-30)

3864
BSC6900 UMTS
counters provide the duration of forward or backward congestions on an IP path in a measurement
period. The forward direction indicates the TX direction, and the backward direction indicates
the RX direction. These counters can be used together with the number of IP path congestions
to observe the congestion. If traffic on many IP paths is congested for a long time, services are
affected. These counters become ineffective when the actual flow admission is enabled.
Counter Name
Description
Duration of backward congestion on the IP

path
Measurement point
In a measurement period, the RNC checks the state of an IP path each time a service is being
admitted to that path. The measurement of a forward (backward) congestion duration starts when
a forward (backward) congestion is detected on an AAL2 path and stops when the forward
(backward) congestion is cleared. In the measurement period, the accumulated duration of
forward (backward) congestion on the IP path is taken as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.Fwd.Cong.Dur
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3865
BSC6900 UMTS
2.21 Measurement of IPPath IP Layer Performance

(IPPATH_IPLAYER)
Overview
IP path carries the user plane data between the controller and other NEs. It is an important
transmission resource. Measurement of IPPath IP Layer Performance indicates the transmission
quality of the IPPATH IP layer on the FG2a, GOUa, PEUa, PEUc, UOIa, POUa, FG2c, POUc,
GOUc and GOUe board.When the IPMUX switch is enabled, the interface board measures the
traffic on the IP path before performing IP packet multiplexing. Therefore, the counter values
for the IP path are not affected by IP packet multiplexing.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IPPATH.IPLAYER
IPPath IP Layer Measurement
2.21.1 IPPath IP Layer Measurement(IPPATH.IPLAYER)

Overview
The quality of transmission links directly affects the system performance. IPPath IP Layer
Measurement helps analyze system transmission quality so as to maintain system stability and
reliability. This function subset takes effect after IP paths are added. It measures the rate, packet
loss, and data volume sent or received over an IP path at the IP layer.
The figure1 shows the location of the IP Layer in the procotol.
Issue 03 (2015-06-30)

3866
BSC6900 UMTS
Figure 2-44 Physical bearer of the logical port for the IPPATH
The position of IP paths in the configuration structure is in figure2 and figure3:

Figure 2-45 Physical bearer of the IPPATH
Issue 03 (2015-06-30)

3867
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195395
VS.IPPATH.IPLA
YER.TXPACKET
S
T7401:Number of
Packets Transmitted
at the IP Layer of an
IP Path
Earlier than
BSC6900
V900R011
67195396
VS.IPPATH.IPLA
YER.TXBYTES
T7402:Number of
Bytes Transmitted at
the IP Layer of an IP
Path
Earlier than
BSC6900
V900R011
67195397
VS.IPPATH.IPLA
YER.TXDROPPA
CKETS
T7403:Number of
Packets Discarded in
Transmission at the
IP Layer of an IP Path
Earlier than
BSC6900
V900R011
67195398
VS.IPPATH.IPLA
YER.TXDROPBY
TES
T7404:Number of
Bytes Discarded in
Transmission at the
Earlier than
BSC6900
V900R011
67195399
VS.IPPATH.IPLA
YER.RXPACKET
S
T7405:Number of
Packets Received at
the IP Layer of an IP
Path
Earlier than
BSC6900
V900R011
67195400
VS.IPPATH.IPLA
YER.RXBYTES
T7406:Number of
Bytes Received at the
Earlier than
BSC6900
V900R011
67195401
VS.IPPATH.IPLA
YER.RXDROPPA
CKETS
T7407:Number of
Reception at the IP
Layer of an IP Path
Earlier than
BSC6900
V900R011
67195402
VS.IPPATH.IPLA
YER.RXDROPBY
TES
T7408:Number of
Bytes Discarded in
Reception at the IP
Layer of an IP Path
Earlier than
BSC6900
V900R011
67204698
VS.IPPATH.IPLA
YER.PEAK.TXRA
TE
T7410:Maximum
Transmit Rate of an
IP Path at the IP
Layer
Earlier than
BSC6900
V900R011
67204699
VS.IPPATH.IPLA
YER.MEAN.TX
T7411:Mean
Transmit Rate of an
IP Path at the IP
Layer
Earlier than
BSC6900
V900R011

3868
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204700
VS.IPPATH.IPLA
YER.PEAK.RXRA
TE
T7413:Maximum
Receive Rate of an IP
Path at the IP Layer
Earlier than
BSC6900
V900R011
67204701
VS.IPPATH.IPLA
YER.MEAN.RX
T7414:Mean
Earlier than
BSC6900
V900R011
73441529
VS.IPPATH.IPLA
YER.FIVE.MINU
TES.PEAK.TXRA
TE
T7419:Maximum
Transmit Rate of an
IP Path at the IP
Layer(5-Minute)
BSC6900
V900R014
73441530
VS.IPPATH.IPLA
YER.FIVE.MINU
TES.PEAK.RXRA
TE
T7420:Maximum
(5-Minute)
BSC6900
V900R014
None
Counters Related to the Number of Packets Received, Transmitted or Dropped at

the IP Layer of an IPPATH
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67195399
VS.IPPATH.IPLAYER.RX
PACKETS
T7405:Number of Packets
Received at the IP Layer of an
IP Path
67195395
VS.IPPATH.IPLAYER.TX
PACKETS
Transmitted at the IP Layer
of an IP Path
67195397
DROPPACKETS
Discarded in Transmission at
the IP Layer of an IP Path
67195401
DROPPACKETS
Discarded in Reception at the

3869
BSC6900 UMTS
Description
VS.IPPATH.IPLAYER.RXPACKETS and VS.IPPATH.IPLAYER.TXPACKETS provide the
number of User Plane packets received or transmitted at the IP layer of an IPPATH in the
measurement period. VS.IPPATH.IPLAYER.RXDROPPACKETS and
VS.IPPATH.IPLAYER.TXDROPPACKETS provide the number of packets discarded over IP
paths due to system internal faults. They indicate the traffic volume of the IPPATH at the IP
layer.
Measurement point
the number of packets transmitted, received or discarded on the link once in every five seconds
and obtains the total number of one measurement period.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
PACKETS
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
PACKETS
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
DROPPACKETS
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3870
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
DROPPACKETS
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Counters Related to the Number of Bytes Received, Transmitted or Discarded at

the IP Layer of an IPPATH
Counters
Counter ID
Counter Name
Counter Description
67195400
BYTES
Received at the IP Layer of an
IP Path
67195396
BYTES
of an IP Path
67195398
DROPBYTES
Discarded in Transmission at
the IP Layer of an IP Path
67195402
DROPBYTES
Discarded in Reception at the
Description
VS.IPPATH.IPLAYER.RXBYTES and VS.IPPATH.IPLAYER.TXBYTES provide the
number of User Plane bytes received or transmitted at the IP layer of an IPPATH.
VS.IPPATH.IPLAYER.RXDROPBYTES and VS.IPPATH.IPLAYER.TXDROPBYTES
provide the number of bytes discarded over IP paths due to system internal faults. They indicate
the traffic volume of the IPPATH at the IP layer. The number of bytes measured includes the
number of bytes in the header of the IP packet and the payload.
Measurement point
the number of bytes transmitted, received or discarded on the link once in every five seconds
Issue 03 (2015-06-30)

3871
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
BYTES
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
BYTES
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
DROPBYTES
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
DROPBYTES
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3872
BSC6900 UMTS
Counters Related to the Receive Rate or Transmit Rate of an IPPATH at the IP Layer
Counters
Counter ID
Counter Name
Counter Description
67204698
VS.IPPATH.IPLAYER.PE
AK.TXRATE
T7410:Maximum Transmit
Rate of an IP Path at the IP
Layer
67204699
VS.IPPATH.IPLAYER.ME
AN.TX

of an IP Path at the IP Layer
67204700
AK.RXRATE
T7413:Maximum Receive
Layer
67204701
AN.RX

an IP Path at the IP Layer
Description
These counters provide the receive rate or transmit rate of an IPPATH at the IP layer in the
measurement period. The rates measured here include the spending of the IP header and the
payload of the IP packet.
Measurement point
period.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

3873
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
AK.TXRATE
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
AN.TX
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
AK.RXRATE
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
AN.RX
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
5-Minute Measurement of the Highest Transmit and Receive Rates of an IPPATH

at the IP Layer
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441529
VS.IPPATH.IPLAYER.FIV
E.MINUTES.PEAK.TXRA
TE
Layer(5-Minute)
73441530
E.MINUTES.PEAK.RXRA
TE
Layer(5-Minute)

3874
BSC6900 UMTS
Description
These counters provide the receive rate or transmit rate of an IPPATH at the IP layer in the 5Minute measurement period. The rates measured here include the spending of the IP header and
the payload of the IP packet.
Measurement point
1.Within a specified measurement period, the system measures the number of transmitted and
received bytes every 5 seconds and accumulates the number of bytes at the end of every 5-minute
sampling period to obtain the total number of bytes transmitted or received within the sampling
period.
2.The system calculates the transmit and receive rate within every 5-minute sampling period
with the following formula: Transmit and receive rate within a 5-minute sampling period = Total
number of bytes transmitted and received within a 5-minute sampling period/300
3.The system compares all of the collected transmit and receive rates to obtain the highest
transmit and receive rate within the specified measurement period, which is the value of the
corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
E.MINUTES.PEAK.TXRA
TE
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
E.MINUTES.PEAK.RXRA
TE
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

3875
BSC6900 UMTS
2.22 Measurement of IPPath PM Performance

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

Overview
The IPPATH Performance Monitor (PM) uses Forward Monitoring (FM) and Backward
Reporting (BR) to check for packet loss over channels. For measurement on the BSC side, the
BSC periodically sends FM messages to indicate the number of outgoing packets, the number
of bytes, and sending time. The Base Station responds with BR messages after receiving the FM
message to report the number of received packets, the number of received bytes, the receiving
time of PM message, the sending time of BR response. The BSC calculates the packet loss rate,
transmission delay and jitter according to the BR response returned from the Base Station. The
numbers of packets and bytes listed in the FM and BR frames are the number of data packets
and the number of bytes included in the data packets, exclusive of the number of FM and BR
frames and the bytes included in the FM and BR frames. The following figure shows the
relationship between IPPM detection packets and service packets.
Figure 2-46 Relationship between IPPM detection packets and service packets
Issue 03 (2015-06-30)

3876
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192968
VS.IPPM.MaxRttDelay
T7663:Maximum
RTT Delay of IPPM
Earlier than
BSC6900
V900R011
67204117
VS.IPPM.Bits.Mea
nsTx
T7668:Average TX
Bit Rate of IPPM
Earlier than
BSC6900
V900R011
67204118
VS.IPPM.Pkts.Mea
nsTx
T7669:Average TX
Packet Rate of IPPM
Earlier than
BSC6900
V900R011
67204119
VS.IPPM.Peak.Bits
.RateTx
T7670:Peak TX Bit
Rate of IPPM
Earlier than
BSC6900
V900R011
67204120
VS.IPPM.Peak.Pkt
s.RateTx
T7671:Peak TX
Packet Rate of IPPM
Earlier than
BSC6900
V900R011
67204121
VS.IPPM.Peer.Bits
.MeansRx
T7672:Average RX
Bit Rate of IPPM
Earlier than
BSC6900
V900R011
67204122
VS.IPPM.Peer.Pkts
.MeansRx
T7673:Average RX
Packet Rate of Peer
End of IPPM
Earlier than
BSC6900
V900R011
67204123
VS.IPPM.Peer.Pea
k.Bits.RateRx
T7674:Peak RX Bit
Rate of Peer End of
IPPM
Earlier than
BSC6900
V900R011
67204124
VS.IPPM.Peer.Pea
k.Pkts.RateRx
T7675:Peak RX
Packet Rate of Peer
End of IPPM
Earlier than
BSC6900
V900R011
67204127
VS.IPPM.Forword.
DropMeans
T7676:Average
Forward Packet Loss
Rate of IPPM
Earlier than
BSC6900
V900R011
67204128
VS.IPPM.Forword.
Peak.DropRates
T7677:Peak Forward
Packet Loss Rate of
IPPM
Earlier than
BSC6900
V900R011
67204131
VS.IPPM.Forward.
JitterStandardDeviation
T7678:Forward
Jitter Standard
Deviation of IPPM
Earlier than
BSC6900
V900R011

3877
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204731
VS.IPPM.Back.JitterStandardDeviation
T7679:Backward
Jitter Standard
Deviation of IPPM
Earlier than
BSC6900
V900R011
67204132
VS.IPPM.Rtt.Mean
s
T7680:Average RTT
Delay of IPPM
Earlier than
BSC6900
V900R011
73441211
VS.IPPM.Forward.
Precise.Peak.DropRates
T7681:HighPrecision Peak
Forward Packet Loss
Rate of IPPM
BSC6900
V900R014
None
Bit Rate of IPPM

Counters
Counter ID
Counter Name
Counter Description
67204117
VS.IPPM.Bits.MeansTx
T7668:Average TX Bit Rate

of IPPM
67204119
VS.IPPM.Peak.Bits.RateTx
T7670:Peak TX Bit Rate of

IPPM
67204121
VS.IPPM.Peer.Bits.MeansR
x
T7672:Average RX Bit Rate

of IPPM
67204123
VS.IPPM.Peer.Peak.Bits.Ra
teRx
T7674:Peak RX Bit Rate of

Peer End of IPPM
Description
These counters provide the bit rate of the data packets (including IP header and payload, but
excluding FM and BR frames) on the IP path that is enabled with the Performance Monitor (PM)
function in a specified measurement period. These counters are measured at the transport layer.
Measurement point
Issue 03 (2015-06-30)

3878
BSC6900 UMTS
total number of packets in one measurement period. The maximum speed is calculated with the
maximum bytes in five seconds, and the average speed is calculated with the total bytes in one
measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPM.Bits.MeansTx
WRFD-050402
on Iub Interface
VS.IPPM.Peak.Bits.RateTx
WRFD-050402
on Iub Interface
VS.IPPM.Peer.Bits.MeansR
x
WRFD-050402
on Iub Interface
VS.IPPM.Peer.Peak.Bits.Ra
teRx
WRFD-050402
on Iub Interface
Counter ID
Counter Name
Counter Description
67204118
VS.IPPM.Pkts.MeansTx
T7669:Average TX Packet
Rate of IPPM
67204120
VS.IPPM.Peak.Pkts.RateTx
T7671:Peak TX Packet Rate

of IPPM
67204122
VS.IPPM.Peer.Pkts.MeansR
x
T7673:Average RX Packet
Rate of Peer End of IPPM
67204124
VS.IPPM.Peer.Peak.Pkts.Ra
teRx
T7675:Peak RX Packet Rate

of Peer End of IPPM
Packet TX and RX Rates of IPPM

Counters
Issue 03 (2015-06-30)

3879
BSC6900 UMTS
Description
These counters provide the packet rate of the data packets (excluding FM and BR frames) on
the IP path that is enabled with the Performance Monitor (PM) function in a specified
measurement period. These counters are measured at the transport layer.
Measurement point
the number of packets received and transmitted on the link once every five seconds. With this,
the system obtains the maximum number of packets received or transmitted in five seconds, and
the total number of packets in one measurement period. The maximum speed is calculated with
the maximum packets in five seconds, and the average speed is calculated with the total packets
in one measurement period.
Formula
None
Unit
packet/s
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPM.Pkts.MeansTx
WRFD-050402
on Iub Interface
VS.IPPM.Peak.Pkts.RateTx
WRFD-050402
on Iub Interface
VS.IPPM.Peer.Pkts.MeansR
x
WRFD-050402
on Iub Interface
VS.IPPM.Peer.Peak.Pkts.Ra
teRx
WRFD-050402
on Iub Interface
Counter ID
Counter Name
Counter Description
67204127
VS.IPPM.Forword.DropMeans
T7676:Average Forward
Packet Loss Rate of IPPM
67204128
VS.IPPM.Forword.Peak.Dro
pRates
T7677:Peak Forward Packet

Loss Rate of IPPM
Forward Packet Loss Rate of IPPM

Counters
Issue 03 (2015-06-30)

3880
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73441211
VS.IPPM.Forward.Precise.P
eak.DropRates
T7681:High-Precision Peak
Forward Packet Loss Rate of
IPPM
Description
This counter provides the Forward Packet Loss Rate of the IPPATH in the specified
measurement period.The packet loss rate is calculated as follows:(Number of Packets Sent Number of Packets Received by the Peer End)/Number of Packets Sent
Measurement point
the number of discarded packtes once every five seconds. With this, the system obtains the total
number of discarded packtes in one measurement period. The loss rate is calculated by dividing
the discarded packtes with total packtes.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPPM.Forword.DropMeans
WRFD-050402
on Iub Interface
VS.IPPM.Forword.Peak.Dro
pRates
WRFD-050402
on Iub Interface
VS.IPPM.Forward.Precise.P
eak.DropRates
WRFD-050402
on Iub Interface

3881
BSC6900 UMTS
Jitter Standard Deviation of IPPM

Counters
Counter ID
Counter Name
Counter Description
67204131
VS.IPPM.Forward.JitterStandardDeviation
T7678:Forward Jitter
Standard Deviation of IPPM
67204731
T7679:Backward Jitter
Standard Deviation of IPPM
Description
This counter provides the jitter standard deviation of IPPM data packets in a measurement period.
It indicates the stabilization of the transmission delay of the IP path. A large counter value
indicates that the transmission delay varies significantly.
Measurement point
The system obtains the delay jitter of every packet and calculates the standard deviation of the
IPPM data packet delay jitter based on the collected statistics within one measurement period.
The Jitter Standard Deviation is calculated as follows:
l
Jitter Standard Deviation = (((Jitter 1 - Mean Jitter)^2+(Jitter 2 - Mean Jitter)^2+......(Jitter

n - Mean Jitter)^2)/n)^0.5
Formula
None
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPPM.Forward.JitterStandardDeviation
WRFD-050402
on Iub Interface
WRFD-050402
on Iub Interface

3882
BSC6900 UMTS
RTT Delay of IPPM

Counters
Counter ID
Counter Name
Counter Description
67204132
VS.IPPM.Rtt.Means
T7680:Average RTT Delay

of IPPM
67192968
VS.IPPM.MaxRttDelay
T7663:Maximum RTT
Delay of IPPM
Description
This counter provides the IPPM RTT delay(Round-Trip Time) in the specified measurement
period to reflect the quality condition of IPPATH. The RTT here consists of the transmission
delay caused by an FM frame traveling from the BSC to the Base Station and a BR frame
traveling from the Base Station to the BSC.
Measurement point
As shown in the following figure, T1 indicates the time at which the BSC sends the FM packet,
T2 indicates the time at which the BTS receives the FM packet from the BSC, T3 indicates the
time at which the BTS sends the BR packet, and T4 indicates the time at which the BSC receives
the BR packet from the BTS. The RTT delay is calculated as follows:
RTT Delay = T4 - T1 - (T3 - T2)
Figure 2-47 RTT Delay
Formula
None
Unit
ms
Issue 03 (2015-06-30)

3883
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPM.Rtt.Means
WRFD-050402
on Iub Interface
VS.IPPM.MaxRttDelay
WRFD-050402
on Iub Interface
2.23 Measurement of IPPath RTP Performance

(IPPATH_RTP)
Overview
The measurement object type IPPATH_RTP has only one function subset, that is, IPPATH.RTP.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IPPATH.RTP
IPPath RTP Measurement
2.23.1 IPPath RTP Measurement(IPPATH.RTP)

Overview
The support of IP-based Iu/A interface is an important feature. In order to control the
transmission quality on the Iu/A interface, the performance of IP paths is measured on the basis
of Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol (RTCP)
packets. The transmission quality of the IP paths is related to the measurement items such as
Round Trip Time (RTT) of packets, delay jitter of packets, and packet loss rate, In order to
increase the ability of surveillance.The item is measured only when the RTCP function is
switched on.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67192702
VS.IPPATH.RTP.P
ktNum.Tx
Number of TX RTP
Packets at an IP Path
Earlier than
BSC6900
V900R011

3884
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204003
VS.IPPATH.RTP.
BytesNum.Tx
Number of Bytes of
TX RTP at an IP Path
Earlier than
BSC6900
V900R011
67204004
VS.IPPATH.RTP.
BytesLen.Rx
Number of Bytes of
RX RTP at an IP Path
Earlier than
BSC6900
V900R011
67204005
VS.IPPATH.RTP.
LossPktRatio.Rx
Rate of lost Packet at

Local End of IP Path
Earlier than
BSC6900
V900R011
67192707
VS.IPPATH.RTP.
LossPktNum.Rx
Number of lost RX
RTP Packets at an IP
Path
BSC6900
V900R016C00
67192708
VS.IPPATH.RTP.P
ktNum.Rx
Number of RX RTP
Earlier than
BSC6900
V900R011
67192709
VS.IPPATH.RTP.
AverageJitter
Delay Jitter at Local

End of IP Path
Earlier than
BSC6900
V900R011
67192710
VS.IPPATH.RTP.
AverageRtt
RTT at Local End of

IP Path
Earlier than
BSC6900
V900R011
67204006
VS.IPPATH.RTP.
BandWidth.Rx
RX RTP bandwidth
of IP Path
Earlier than
BSC6900
V900R011
67204007
VS.IPPATH.RTP.
BandWidth.Tx
TX RTP bandwidth
of IP Path
Earlier than
BSC6900
V900R011
67204008
VS.IPPATH.RTP.J
itterOverrun.TimeRatio

Delay Jitter Exceeds
Threshold of IP Path
Earlier than
BSC6900
V900R011
67204009
VS.IPPATH.RTP.
RttOverrun.TimeRatio

RTT Exceeds
Threshold of IP Path
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

3885
BSC6900 UMTS
Total Number of RTP Packets Transmitted over a Single IP Path

Counters
Counter ID
Counter Name
Counter Description
67192702
VS.IPPATH.RTP.PktNum.T
x
Number of TX RTP Packets

at an IP Path
Description
This measurement item takes statistics of the total number of RTP packets transmitted over a
single IP path during a specified measurement period. This item is used for checking the status
of packet transmission over a single IP path.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, this measurement
item is incremented by 1 each time the Iu UP/AoIP transmits an uplink data packet or an in-band
signaling packet during a specified measurement period.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.PktNum.T
x
WRFD-050409
on Iu Interface
Total Amount of RTP Data in KB Transmitted over a Single IP Path

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204003
VS.IPPATH.RTP.BytesNu
m.Tx
Number of Bytes of TX RTP

at an IP Path

3886
BSC6900 UMTS
Description
This measurement item takes statistics of the total amount of RTP data in kilobytes transmitted
over a single IP path during a specified measurement period.
Measurement point
item is incremented by the size of the RTP packet payload in kilobytes each time the Iu UP/
AoIP transmits an uplink user data packet or an in-band signaling packet during a specified
measurement period.
Formula
None
Unit
kB
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.BytesNu
m.Tx
WRFD-050409
on Iu Interface
Total Amount of RTP Data in KB Received over a Single IP Path

Counters
Counter ID
Counter Name
Counter Description
67204004
VS.IPPATH.RTP.BytesLen.
Rx
Number of Bytes of RX RTP

at an IP Path
Description
This measurement item takes statistics of the total amount of RTP data in kilobytes received
over a single IP path during a specified measurement period.
Measurement point
item is incremented by the size of the RTP packet payload in kilobytes each time the Iu UP/
AoIP receives a downlink data packet during a specified measurement period. This measurement
item is reset after each reporting.
Issue 03 (2015-06-30)

3887
BSC6900 UMTS
Formula
None
Unit
kB
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.BytesLen.
Rx
WRFD-050409
on Iu Interface
Loss Rate of RTP Packets Received over a Single IP Path

Counters
Counter ID
Counter Name
Counter Description
67204005
VS.IPPATH.RTP.LossPktR
atio.Rx
Rate of lost Packet at Local

End of IP Path
Description
This measurement item takes statistics of the loss rate of RTP packets received over a single IP
path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, each time the Iu UP/
AoIP transmits an RTCP packet during a specified measurement period, the number of packets
lost during the period increases by the number indicated in the RTCP packet. (Each RTCP packet
needs to contain the number of packets lost during the period.) Then, based on the number of
RTP packets received over the IP path, the RTP packet loss rate on the IP path can be calculated
according to the following formula:Packet loss rate = number of packets lost/(number of packets
lost + number of packets received)
Formula
None
Unit
%
Issue 03 (2015-06-30)

3888
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.LossPktR
atio.Rx
WRFD-050409
on Iu Interface
Loss Number of RTP Packets Received over a Single IP Path

Counters
Counter ID
Counter Name
Counter Description
67192707
VS.IPPATH.RTP.LossPktN
um.Rx
Number of lost RX RTP

Description
This counter provides the number of lost packets on an IP path in a measurement period and is
used to reflect the packet loss on an IP path.
Measurement point
When the Iu or A interface uses IP transmission and RTCP is supported, this counter is
incremented by one each time the Iu or A interface detects that a downlink RTP packet is lost.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.LossPktN
um.Rx
WRFD-050409
on Iu Interface

3889
BSC6900 UMTS
Total Number of RTP Packets Received over a Single IP Path

Counters
Counter ID
Counter Name
Counter Description
67192708
VS.IPPATH.RTP.PktNum.
Rx
Number of RX RTP Packets

at an IP Path
Description
This measurement item takes statistics of the total number of RTP packets received over a single
IP path during a specified measurement period. This item is used to check the status of packet
reception over a single IP path.
Measurement point
item is incremented by 1 each time the Iu UP/AoIP receives a downlink RTP data packet during
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.PktNum.
Rx
WRFD-050409
on Iu Interface
Mean Delay Jitter of RTP Packets Received over a Single IP Path

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192709
VS.IPPATH.RTP.AverageJitter
Delay Jitter at Local End of

IP Path

3890
BSC6900 UMTS
Description
This measurement item takes statistics of the average delay jitter of RTP packets received over
a single IP path.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, each time an RTP
packet is received in the downlink, the delay jitter of the packet is calculated on the basis of the
local time when the packet is received and the value of Ts in the packet. Then, the average delay
jitter can be calculated according to the following formula: Average delay jitter = Sum of delay
jitter /Total times
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.AverageJitter
WRFD-050409
on Iu Interface
Mean RTT of Packets Received over a Single IP Path

Counters
Counter ID
Counter Name
Counter Description
67192710
VS.IPPATH.RTP.AverageRtt
RTT at Local End of IP Path
Description
This measurement item takes statistics of the Round Trip Time (RTT) of packets received over
a single IP path.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, after an RTCP packet
is transmitted from the local end, RTT of the received RTCP packet can be calculated each time
an RTCP packet with Reception Report Block is received in the downlink. The RTT is calculated
on the basis of the time of transmitting that RTCP packet, the time of receiving this RTCP packet,
Issue 03 (2015-06-30)

3891
BSC6900 UMTS
and the DLSR field of the received RTCP packet. The formula is as follows: RTT = the time of
receiving this RTCP packet - the time of transmitting that RTCP packet - DLSR in the received
RTCP packet Then, the average RTT is calculated as follows: Average RTT =Sum of RTT/
Total times
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.AverageRtt
WRFD-050409
on Iu Interface
Local Received Bandwidth of a Single IP Path

Counters
Counter ID
Counter Name
Counter Description
67204006
VS.IPPATH.RTP.BandWidt
h.Rx
RX RTP bandwidth of IP
Path
Description
This measurement item takes statistics of the local received bandwidth of a single IP path during
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, the local received
bandwidth of a single IP path during a specified measurement period can be calculated according
to the following formula:Local received bandwidth = total amount of RTP data in KB received
over the IP path/length of the measurement period
Formula
None
Unit
kB/s
Issue 03 (2015-06-30)

3892
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
h.Rx
WRFD-050409
on Iu Interface
Local Transmitted Bandwidth of a Single IP Path

Counters
Counter ID
Counter Name
Counter Description
67204007
h.Tx
TX RTP bandwidth of IP
Path
Description
This measurement item takes statistics of the local transmitted bandwidth of a single IP path
during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, the local transmitted
bandwidth of a single IP path during a specified measurement period can be calculated according
to the following formula:Local transmitted bandwidth = total amount of RTP data in KB
transmitted over the IP path/length of the measurement period
Formula
None
Unit
kB/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
h.Tx
WRFD-050409
on Iu Interface

3893
BSC6900 UMTS
Ratio of Duration of RTP Delay Jitter Exceeding Threshold to Total Active

Duration
Counters
Counter ID
Counter Name
Counter Description
67204008
VS.IPPATH.RTP.JitterOver
run.TimeRatio
Rate of Duration that Delay

Jitter Exceeds Threshold of
IP Path
Description
This measurement item takes statistics of the ratio of the time during which the RTP delay jitter
exceeds the threshold to the total time during which an IP path is active. This measurement is
specific to the single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and Real-time Transport Control Protocol
(RTCP) is supported, during a specified measurement period, the ratio is calculated according
to the following formula: Ratio = duration of RTP delay jitter exceeding threshold/total active
duration. Total active duration indicates the sum of intervals between two consecutive Real-time
Transport Protocol (RTP) packets received at the local end over an IP path. Duration of RTP
delay jitter exceeding threshold indicates the length of time during which the delay jitter exceeds
the related threshold for RTP packets received at the local end over an IP path. The RTP delay
equals the elapsed time for a packet transmitted by the peer end to reach the local end.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.JitterOver
run.TimeRatio
WRFD-050409
on Iu Interface

3894
BSC6900 UMTS
Ratio of Duration of RTT Exceeding Threshold to Total Active Duration

Counters
Counter ID
Counter Name
Counter Description
67204009
VS.IPPATH.RTP.RttOverru
n.TimeRatio
Rate of Duration that RTT

Exceeds Threshold of IP Path
Description
This measurement item takes statistics of the ratio of the time during which the Round Trip Time
(RTT) exceeds the threshold to the total time during which an IP path is active. This measurement
is specific to the single IP path during a specified measurement period.
Measurement point
When IP transport is applied to the Iu/A interface and RTCP is supported, during a specified
measurement period, the ratio is calculated according to the following formula: Ratio = duration
of RTT exceeding threshold/total active duration. Total active duration indicates the sum of
intervals between two consecutive Real-time Transport Protocol (RTP) packets received at the
local end over an IP path. Duration of RTT exceeding threshold indicates the length of time
during which the RTT exceeds the related threshold over an IP path. The RTT indicates the
length of time it takes from the transit of one RTCP pakcet from the local end to the receiving
of the response from the peer end.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPATH.RTP.RttOverru
n.TimeRatio
WRFD-050409
on Iu Interface
2.24 Measurement of Transmission Resource Pool Adjacent

Node Performance(IPPOOL_ADJNODE)
Overview
Adjonde is used to configure an adjacent network device or an operator of an adjacent network
device of an controller. Measurement of Transmission Resource Pool Adjacent Node
Issue 03 (2015-06-30)

3895
BSC6900 UMTS
Performance indicates the transmission quality and IP layer transmission performance of each
adjacent node that communicates with the IP addresses in a transmission resource pool.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IPPOOL.ADJNODE.IPLAYER
Transmission Resource Pool Adjacent Node

User-Plane Traffic Measurement
IPPOOL.ADJNODE
Transmission Resource Pool Adjacent Node

IP Transmission Quality Measurement
2.24.1 Transmission Resource Pool Adjacent Node User-Plane

Traffic Measurement(IPPOOL.ADJNODE.IPLAYER)
Overview
Transmission Resource Pool Adjacent Node User-Plane Traffic Measurement indicates the userplane traffic of each adjacent node that communicates with the IP addresses in a transmission
resource pool. This measurement helps analyze the transmission quality of the system. These
counters provide the received and transmitted data of transmission resource pool adjacent node
traffic at the user-plane IP layer.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441279
VS.IPPOOL.ANI.I
PLAYER.TXPAC
KETS
T7909:Number of
Packets Transmitted
at the IP Layer on
Adjacent Node User
Plane
BSC6900
V900R014
73441248
VS.IPPOOL.ANI.I
PLAYER.TXBYT
ES
T7910:Number of
the IP Layer on
Adjacent Node User
Plane
BSC6900
V900R014
73441249
VS.IPPOOL.ANI.I
PLAYER.RXPAC
KETS
T7911:Number of
Packets Received at
the IP Layer on
Adjacent Node User
Plane
BSC6900
V900R014

3896
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73441250
VS.IPPOOL.ANI.I
PLAYER.RXBYT
ES
T7912:Number of
IP Layer on Adjacent
Node User Plane
BSC6900
V900R014
73441251
VS.IPPOOL.ANI.I
PLAYER.PEAK.T
XRATE
T7913:Maximum
Transmit Rate at the
Node User Plane per
Interface Board
BSC6900
V900R014
73441252
VS.IPPOOL.ANI.I
PLAYER.MEAN.T
X
T7914:Mean
Node User Plane
BSC6900
V900R014
73441253
VS.IPPOOL.ANI.I
PLAYER.PEAK.R
XRATE
T7915:Maximum
Receive Rate at the
Node User Plane per
Interface Board
BSC6900
V900R014
73441254
VS.IPPOOL.ANI.I
PLAYER.MEAN.R
X
T7916:Mean
Receive Rate at the
Node User Plane
BSC6900
V900R014
None
Counters Related to the Number of Packets Received or Transmitted at the IP Layer

on Adjacent Node User Plane
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441279
VS.IPPOOL.ANI.IPLAYER
.TXPACKETS
73441249
.RXPACKETS
Received at the IP Layer on
Adjacent Node User Plane

3897
BSC6900 UMTS
Description
These counters provide the number of received and transmitted IP packets on the user plane by
each adjacent node that communicates with the IP addresses of a transmission resource pool.
These counters indicate the traffic on the IP layer of an adjacent node in the transmission resource
pool.
Measurement point
Samples are taken every five seconds in the specified measurement period. The system measures
the number of IP packets received and transmitted on the user plane of the IP layer once every
five seconds and obtains the total number at the end of every measurement period.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
.TXPACKETS
WRFD-140207
Iu/Iur Transmission
Resource Pool of RNC
WRFD-140208
Iub Transmission Resource

Pool of RNC
.RXPACKETS
WRFD-140207
WRFD-140208
Iu/Iur Transmission
Pool of RNC
Counters Related to the Number of Bytes Received or Transmitted at the IP Layer

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441248
.TXBYTES
73441250
.RXBYTES

3898
BSC6900 UMTS
Description
These counters provide the number of received and transmitted IP bytes on the user plane by
each adjacent node that communicates with the IP addresses of a transmission resource pool.
The number of bytes measured includes the number of bytes in the header of the IP packet and
the payload.
Measurement point
the number of bytes received and transmitted on the user plane of the IP layer once every five
seconds and obtains the total number at the end of every measurement period.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
.TXBYTES
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
.RXBYTES
WRFD-140207
WRFD-140208
Iu/Iur Transmission
Pool of RNC
Counters Related to the Receive Rate or Transmit Rate at the IP Layer on Adjacent
Node User Plane
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441251
.PEAK.TXRATE
Rate at the IP Layer on
per Interface Board

3899
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73441252
.MEAN.TX

at the IP Layer on Adjacent
Node User Plane
73441253
.PEAK.RXRATE
Rate at the IP Layer on
per Interface Board
73441254
.MEAN.RX
T7916:Mean Receive Rate at

the IP Layer on Adjacent
Node User Plane
Description
These counters provide the receive rate or transmit rate on the user plane by each adjacent node
in the measurement period. The rates measured here include the spending of the IP header and
the payload of the IP packet. The Maximum Receive and Transmit Rate indicate the receive and
transmit rate of Adjacent Node on single Interface Board.
Measurement point
the number of bytes received and transmitted on the user plane of the IP layer once every five
seconds. With this, the system obtains the maximum number of bytes received or transmitted in
five seconds, and the total number of one measurement period. The maximum speed is calculated
with the maximum bytes in five seconds, and the average speed is calculated with the total bytes
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
.PEAK.TXRATE
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
Issue 03 (2015-06-30)

3900
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
.MEAN.TX
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
.PEAK.RXRATE
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
.MEAN.RX
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
2.24.2 Transmission Resource Pool Adjacent Node IP Transmission

Quality Measurement(IPPOOL.ADJNODE)
Overview
Transmission Resource Pool Adjacent Node IP Transmission Quality Measurement indicates
the transmission quality of each adjacent node that communicates with the IP addresses in a
transmission resource pool. This measurement helps analyze the transmission quality of the
system.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424310
VS.IPPOOL.ADJN
ODE.Fwd.Cong
T7917:Number of
Forward
Congestions of
Adjacent Node
BSC6900
V900R014
73441255
VS.IPPOOL.ADJN
ODE.Fwd.Cong.Du
r
T7918:Duration of
Forward Congestion
of Adjacent Node
BSC6900
V900R014
73424313
VS.IPPOOL.ADJN
ODE.Bwd.Cong
T7919:Number of
Backward
Congestions of
Adjacent Node
BSC6900
V900R014

3901
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73441256
VS.IPPOOL.ADJN
ODE.Bwd.Cong.Du
r
T7920:Duration of
Backward
Congestion of
Adjacent Node
BSC6900
V900R014
73441496
VS.IPPOOL.ADJN
ODE.PING.MeanD
ELAY
T7812:Average Ping
Delay of Adjacent
Node
BSC6900
V900R014
73424743
VS.IPPOOL.ADJN
ODE.PING.MaxD
ELAY
T7813:Maximum
Ping Delay of
Adjacent Node
BSC6900
V900R014
73441497
VS.IPPOOL.ADJN
ODE.PING.MeanJITTER
T7814:Average Ping
Delay Variation of
Adjacent Node
BSC6900
V900R014
73424745
VS.IPPOOL.ADJN
ODE.PING.MaxJI
TTER
T7815:Maximum
Ping Delay Variation
of Adjacent Node
BSC6900
V900R014
73441498
VS.IPPOOL.ADJN
ODE.PING.MeanLOST
T7816:Average Ping
Packet Loss Rate of
Adjacent Node
BSC6900
V900R014
73424747
VS.IPPOOL.ADJN
ODE.PING.MaxL
OST
T7817:Maximum
Ping Packet Loss
Rate of Adjacent
Node
BSC6900
V900R014
None
Counters Related to the Number of Congestions of Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73424310
VS.IPPOOL.ADJNODE.Fw
d.Cong
Congestions of Adjacent
Node
73424313
VS.IPPOOL.ADJNODE.Bw
d.Cong
Congestions of Adjacent
Node

3902
BSC6900 UMTS
Description
These counters take effect only when the interface board connected to the IP adjacent node uses
the transmission pool networking. When services using IP transmission access the network, if
the remaining bandwidth is less than or equal to the congestion remaining threshold configured
for an adjacent node, traffic on the adjacent node is congested. Users can configure the congestion
remaining threshold according to the actual requirements. If the congestion remaining threshold
is set to 0, congestion does not occur. These counters provide the number of forward and
backward bandwidth admission congestions on an IP adjacent node in a specified measurement
period. The forward direction indicates the TX direction, and the backward direction indicates
the RX direction. These counters can be used together with the duration of IP adjacent node
congestion to observe the congestion. If traffic on many IP adjacent nodes is congested for a
long time, services are affected. These counters become ineffective when the actual flow
admission is enabled.
Measurement point
In a measurement period, the RNC checks the state of an adjacent node in IP transmission mode
each time a service is being admitted to that node. This counter is incremented by one when the
state of the adjacent node changes from non-congestion to congestion.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
d.Cong
WRFD-140208

Pool of RNC
d.Cong
WRFD-140208

Pool of RNC
Counters Related to the Duration of Congestion of Adjacent Node

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441255
d.Cong.Dur
Congestion of Adjacent
Node

3903
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73441256
d.Cong.Dur
T7920:Duration of
Backward Congestion of
Adjacent Node
Description
These counters take effect only when the interface board connected to the IP adjacent node uses
the transmission pool networking. When services using IP transmission access the network, if
the remaining bandwidth is less than or equal to the congestion remaining threshold configured
for an adjacent node, traffic on the adjacent node is congested. Users can configure the congestion
remaining threshold according to the actual requirements. If the congestion remaining threshold
is set to 0, congestion does not occur. These counters provide the duration of an IP adjacent node
in the forward or backward congestion state when the adjacent node uses resource pool
networking. The forward direction indicates the TX direction, and the backward direction
indicates the RX direction. These counters can be used together with the number of IP adjacent
node congestions to observe the congestion. If traffic on many IP adjacent nodes is congested
for a long time, services are affected. These counters become ineffective when the actual flow
admission is enabled.
Measurement point
In a measurement period, the RNC checks the state of an adjacent node in IP transmission mode
each time a service is being admitted to the node. The measurement of a forward or backward
congestion duration starts when forward or backward congestion is detected on an adjacent node
in IP transmission mode and stops when forward or backward congestion is cleared. In the
measurement period, the accumulated duration of forward or backward congestion on the node
is taken as the value of this counter.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
d.Cong.Dur
WRFD-140208

Pool of RNC
d.Cong.Dur
WRFD-140208

Pool of RNC

3904
BSC6900 UMTS
Average Ping Delay of Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
73441496
VS.IPPOOL.ADJNODE.PI
NG.MeanDELAY
T7812:Average Ping Delay

of Adjacent Node
Description
After the adjacent node ping detection function is enabled, the base station controller periodically
sends the ping request packet to the peer NE and receives the acknowledgement packet from the
peer NE. This counter provides the average two-way delay between sending the ping request
packet and receiving the acknowledgement packet. It is used to monitor the delay changes on
end-to-end IP paths between the base station controller and the peer adjacent node. In normal
situation, a large average delay indicates congestion on the transmission paths. The congestion
can be relieved until packet loss occurs on the network. This counter can also reflect the
congestion on an IP path of the adjacent node. This counter takes effect only when the interface
board connected to the IP adjacent node uses the transmission pool networking and the adjacent
node ping detection is enabled. This counter provides the average ping delay of an adjacent node
in a specified measurement period. The formula for calculating the delay of a ping request is as
follow:
Delay of ping request n = Receive time of packet n - Send time of packet n (unit:ms)
Measurement point
In a measurement period, the system automatically samples the total delay of all ping packets
on an adjacent node every 90s. At the end of the specified measurement period, the system
divides the accumulated ping delay by the number of samples to obtain the value of this counter.
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
NG.MeanDELAY
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
Issue 03 (2015-06-30)

3905
BSC6900 UMTS
Maximum Ping Delay of Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
73424743
NG.MaxDELAY
T7813:Maximum Ping
Delay of Adjacent Node
Description
peer NE. This counter provides the maximum two-way delay variation between sending a ping
packet and receiving an acknowledgement packet on an IP path of an adjacent node in a
measurement period. It is used to monitor the delay changes on end-to-end IP paths between the
base station controller and the peer adjacent node. In normal situations, a large maximum delay
variation indicates poor transmission quality on the IP path of the adjacent node. This counter
takes effect only when the interface board connected to the IP adjacent node uses the transmission
pool networking and the adjacent node ping detection is enabled. This counter provides the
maximum ping delay of an adjacent node in a specified measurement period. It takes effect only
when the adjacent node ping function is enabled.
Measurement point
In a measurement period, the system automatically samples the maximum delay of all ping
packets on an adjacent node every 90s. At the end of the specified measurement period, the
system uses the maximum delay as the value of this counter.
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
NG.MaxDELAY
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
Issue 03 (2015-06-30)

3906
BSC6900 UMTS
Average Ping Delay Variation of Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
73441497
NG.MeanJITTER
T7814:Average Ping Delay

Variation of Adjacent Node
Description
peer NE. This counter provides the average two-way delay variation between sending a ping
pool networking and the adjacent node ping detection is enabled. The definition of the delay
variation is as follows (from RFC1889[Page 27]):
If Si is the RTP timestamp of packet i, and Ri is the time of arrival in RTP timestamp units for
packet i, then for two packets i and j, D may be expressed as follows:
D(i, j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si)
The arrival variation is calculated continuously as each data packet i is received from source
SSRC_n, using this difference D for that packet and the previous packet i-1 in order of arrival
(not necessarily in sequence), according to the following formula:
J = J + (|D(i-1,i)|-J)/16
Whenever a reception report is issued, the current value of J is sampled.
The variation calculation provided here allows protocol-independent monitors to make valid
explanations of reports coming from different implementations. This algorithm is the optimal
first-order estimation and the gain parameter 1/16 provides a good noise reduction ratio while
maintaining a reasonable rate of convergence.
Measurement point
In a measurement period, the system automatically samples the ping delay variation every 90s.
At the end of the specified measurement period, the system divides the accumulated ping delay
variation by the number of samples to obtain the value of this counter.
Formula
None
Issue 03 (2015-06-30)

3907
BSC6900 UMTS
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
NG.MeanJITTER
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
Maximum Ping Delay Variation of Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
73424745
NG.MaxJITTER
T7815:Maximum Ping
Delay Variation of Adjacent
Node
Description
peer NE. This counter provides the maximum two-way delay variation between sending a ping
pool networking and the adjacent node ping detection is enabled.
Measurement point
In a measurement period, the system automatically samples the maximum ping delay variation
of all ping packets on an adjacent node every 90s. At the end of the specified measurement
period, the system uses the maximum ping delay variation as the value of this counter.
Formula
None
Unit
ms
Issue 03 (2015-06-30)

3908
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
NG.MaxJITTER
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
Average Ping Packet Loss Rate of Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
73441498
NG.MeanLOST
T7816:Average Ping Packet

Loss Rate of Adjacent Node
Description
peer NE. This counter provides the average packet loss rate between sending a ping detection
packet and receiving an acknowledgement packet of an adjacent node in a specified measurement
period. It is used to monitor the delay changes on end-to-end IP paths between the base station
controller and the peer adjacent node. In normal situations, a large value of the average packet
loss rate indicates poor transmission quality. Services are affected when the average packet loss
rate of an adjacent node is high. This counter takes effect only when the interface board connected
to the IP adjacent node uses the transmission pool networking and the adjacent node ping
detection is enabled. This counter becomes ineffective when ping detection is enabled for a faulty
link.
Measurement point
In a measurement period, the system samples the number of sent ping packets and the number
of unreceived ping response packets and obtains the packet loss rate by calculating the ratio of
the number of unreceived ping response packets to the number of sent ping packets every 90s.
At the end of the measurement period, the system obtains the average packet loss rate by dividing
the accumulated value by the number of sampling times.
Formula
None
Unit
%
Issue 03 (2015-06-30)

3909
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
NG.MeanLOST
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
Maximum Ping Packet Loss Rate of Adjacent Node

Counters
Counter ID
Counter Name
Counter Description
73424747
NG.MaxLOST
T7817:Maximum Ping
Packet Loss Rate of Adjacent
Node
Description
peer NE. This counter provides the maximum packet loss rate between sending a ping detection
packet and receiving an acknowledgement packet of an adjacent node in a specified measurement
period. It is used to monitor the delay changes on end-to-end IP paths between the base station
controller and the peer adjacent node. In normal situations, a large value of the maximum packet
loss rate indicates poor transmission quality. This counter takes effect only when the interface
board connected to the IP adjacent node uses the transmission pool networking and the adjacent
node ping detection is enabled. This counter becomes ineffective when ping detection is enabled
for a faulty link.
Measurement point
In a measurement period, the system samples the number of sent ping packets and the number
of unreceived ping response packets and obtains the packet loss rate by calculating the ratio of
the number of unreceived ping response packets to the number of sent ping packets every 90s.
At the end of the measurement period, the system uses the maximum packet loss rate as the value
of this counter.
Formula
None
Unit
%
Issue 03 (2015-06-30)

3910
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
NG.MaxLOST
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
2.25 Measurement of Transmission Resource Pool IPPM

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

Measurement
2.25.1 Transmission Resource Pool IPPM Measurement

(IPPOOL.PM)
Overview
Transmission Resource Pool IPPM Measurement uses Forward Monitoring (FM) and Backward
Reporting (BR) to monitor transmission quality. The BSC support both forward measurement
and backward mesurement. The forward direction indicates the sending direction, and the
backward direction indicates the receiving direction. For forward measurement, the BSC
periodically sends FM messages to indicate the number of outgoing packets, the number of bytes,
and sending time. The Base Station responds with BR messages after receiving the FM message
to report the number of received packets, the number of received bytes, the receiving time of
PM message, the sending time of BR response. For backward measurement, the Base Station
periodically sends FM messages and the BSC responds with BR messages. The BSC calculates
the packet loss rate, transmission delay and jitter according to the FM and BR messages. The
numbers of packets and bytes listed in the FM and BR frames are the number of data packets
and the number of bytes included in the data packets, exclusive of the number of FM and BR
frames and the bytes included in the FM and BR frames. The following figure shows the
relationship between IPPM detection packets and service packets.
Issue 03 (2015-06-30)

3911
BSC6900 UMTS
Figure 2-48 Relationship between IPPM detection packets and service packets
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441257
VS.IPPOOL.IPPM.
ForwardBits.Mean
sTx
T7819:Average
Forward Transmit
Bit Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441258
VS.IPPOOL.IPPM.
ForwardPkts.Mean
sTx
T7820:Average
Forward Transmit
Packet Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441259
VS.IPPOOL.IPPM.
Peak.ForwardBits.
RateTx
T7821:Maximum
Forward Transmit
Bit Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441260
VS.IPPOOL.IPPM.
Peak.ForwardPkts.
RateTx
T7822:Maximum
Forward Transmit
Packet Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014

3912
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441261
VS.IPPOOL.IPPM.
Forward.DropMeans
T7823:Average
Forward Packet Loss
Rate of Transmission
Resource Pool IPPM
BSC6900
V900R014
73441522
VS.IPPOOL.IPPM.
Forward.Peak.Dro
pRates
T7824:Maximum
Forward Packet Loss
Rate of Transmission
Resource Pool IPPM
BSC6900
V900R014
73424341
VS.IPPOOL.IPPM.
Forward.JitterMax
T7825:Maximum
Forward Jitter of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441262
VS.IPPOOL.IPPM.
Forward.JitterStandardDeviation
T7826:Forward
Jitter Standard
Deviation of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441263
VS.IPPOOL.IPPM.
Rtt.Means
T7827:Average RTT
Delay of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73424342
VS.IPPOOL.IPPM.
MaxRttDelay
T7828:Maximum
RTT Delay of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441264
VS.IPPOOL.IPPM.
BackwardBits.Mea
nsTx
T7829:Average
Backward Transmit
Bit Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441265
VS.IPPOOL.IPPM.
BackwardPkts.Mea
nsTx
T7830:Average
Backward Transmit
Packet Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441266
VS.IPPOOL.IPPM.
Peak.BackwardBits
.RateTx
T7831:Maximum
Backward Transmit
Bit Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014

3913
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73441267
VS.IPPOOL.IPPM.
Peak.BackwardPkt
s.RateTx
T7832:Maximum
Backward Transmit
Packet Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441268
VS.IPPOOL.IPPM.
Backward.DropMeans
T7833:Average
Backward Packet
Loss Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014
73441523
VS.IPPOOL.IPPM.
Backward.Peak.Dr
opRates
T7834:Maximum
Backward Packet
Loss Rate of
Transmission
Resource Pool IPPM
BSC6900
V900R014
None
Bit Rate of Transmission Resource Pool IPPM

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441257
VS.IPPOOL.IPPM.Forward
Bits.MeansTx
Transmit Bit Rate of
Transmission Resource Pool
IPPM
73441259
VS.IPPOOL.IPPM.Peak.For
wardBits.RateTx
IPPM
73441264
VS.IPPOOL.IPPM.Backwar
dBits.MeansTx
T7829:Average Backward
IPPM
73441266
VS.IPPOOL.IPPM.Peak.Ba
ckwardBits.RateTx
IPPM

3914
BSC6900 UMTS
Description
These counters provide the bit rate of the data packets (including IP header and payload, but
excluding FM and BR frames) in a specified measurement period. These counters are measured
at the transport layer.
Measurement point
total number of packets in one measurement period. The maximum speed is calculated with the
measurement period.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
Bits.MeansTx
WRFD-140208

Pool of RNC
wardBits.RateTx
WRFD-140208

Pool of RNC
dBits.MeansTx
WRFD-140208

Pool of RNC
ckwardBits.RateTx
WRFD-140208

Pool of RNC
VS.IPPOOL.IPPM.ForwardPkts.MeansTx
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441258
Pkts.MeansTx
Transmit Packet Rate of
IPPM

3915
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73441260
wardPkts.RateTx
IPPM
73441265
dPkts.MeansTx
IPPM
73441267
ckwardPkts.RateTx
IPPM
Description
These counters provide the packet rate of the data packets (excluding FM and BR frames) in a
specified measurement period. These counters are measured at the transport layer.
Measurement point
the number of packets received and transmitted on the link once every five seconds. With this,
the system obtains the maximum number of packets received or transmitted in five seconds, and
the total number of packets in one measurement period. The maximum speed is calculated with
the maximum packets in five seconds, and the average speed is calculated with the total packets
Formula
None
Unit
packet/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Pkts.MeansTx
WRFD-140208

Pool of RNC
wardPkts.RateTx
WRFD-140208

Pool of RNC

3916
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
dPkts.MeansTx
WRFD-140208

Pool of RNC
ckwardPkts.RateTx
WRFD-140208

Pool of RNC
VS.IPPOOL.IPPM.Forward.DropMeans
Counters
Counter ID
Counter Name
Counter Description
73441261
VS.IPPOOL.IPPM.Forward.
DropMeans
Packet Loss Rate of
IPPM
73441522
Peak.DropRates
Packet Loss Rate of
IPPM
73441268
d.DropMeans
Packet Loss Rate of
IPPM
73441523
d.Peak.DropRates
Packet Loss Rate of
IPPM
Description
This counter provides the Forward Packet Loss Rate in the specified measurement period.
The forward packet loss rate is calculated as follows:
(Number of packets transmitted by BSC - Number of packets received by Base Station) / Number
of packets transmitted by BSC The backward packet loss rate is calculated as follows:
(Number of packets transmitted by Base Station - Number of packets received by BSC) / Number
of packets transmitted by Base Station
Measurement point
the number of discarded packtes once every five seconds. With this, the system obtains the total
Issue 03 (2015-06-30)

3917
BSC6900 UMTS
number of discarded packtes in one measurement period. The loss rate is calculated by dividing
the discarded packtes with total packtes. The display precision of this counter is 0.001%, so it
is displayed as floating point numbers. For instance, the loss rate is 1.235% when the number is
1.235 in the statistical.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
DropMeans
WRFD-140208

Pool of RNC
Peak.DropRates
WRFD-140208

Pool of RNC
d.DropMeans
WRFD-140208

Pool of RNC
d.Peak.DropRates
WRFD-140208

Pool of RNC
Forward Jitter of Transmission Resource Pool IPPM

Counters
Counter ID
Counter Name
Counter Description
73424341
JitterMax
Jitter of Transmission
Resource Pool IPPM
73441262
T7826:Forward Jitter
Standard Deviation of
IPPM
Description
This counter provides the jitter standard deviation of IPPM data packets in a measurement period.
It indicates the stabilization of the transmission delay of the Transmission Resource Pool. A
Issue 03 (2015-06-30)

3918
BSC6900 UMTS
large counter value indicates that the transmission delay varies significantly. The Jitter Standard
Deviation is calculated as follows:
Jitter Standard Deviation = (((Jitter 1 - Mean Jitter)^2+(Jitter 2 - Mean Jitter)^2+......(Jitter n Mean Jitter)^2)/n)^0.5
Measurement point
The system obtains the delay jitter of every packet and calculates the standard deviation of the
IPPM data packet delay jitter based on the collected statistics within one measurement period.
Formula
None
Unit
microsecond
Related Features
Counter Name
Feature ID
Feature Name
JitterMax
WRFD-140208

Pool of RNC
WRFD-140208

Pool of RNC
RTT Delay of Transmission Resource Pool IPPM

Counters
Counter ID
Counter Name
Counter Description
73441263
VS.IPPOOL.IPPM.Rtt.Mea
ns
T7827:Average RTT Delay

of Transmission Resource
Pool IPPM
73424342
VS.IPPOOL.IPPM.MaxRttDelay
T7828:Maximum RTT
Delay of Transmission
Resource Pool IPPM
Description
This counter provides the IPPM RTT delay in the specified measurement period. The RTT here
consists of the transmission delay caused by an FM frame traveling from the BSC to the Base
Station and a BR frame traveling from the Base Station to the BSC.
Issue 03 (2015-06-30)

3919
BSC6900 UMTS
Measurement point
As shown in the following figure, T1 indicates the time at which the BSC sends the FM packet,
T2 indicates the time at which the BTS receives the FM packet from the BSC, T3 indicates the
time at which the BTS sends the BR packet, and T4 indicates the time at which the BSC receives
the BR packet from the BTS. The delay measured here is the interval between T4 and T1. The
RTT delay is calculated as follows:
RTT Delay = T4 - T1 - (T3 - T2)
Figure 2-49 RTT Delay
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.IPPM.Rtt.Mea
ns
WRFD-140208

Pool of RNC
VS.IPPOOL.IPPM.MaxRttDelay
WRFD-140208

Pool of RNC
2.26 Measurement of Transmission Resource Pool IP

Address RTP Performance(IPPOOL_RTP)
Overview
This counter provides the RTP performance measurement in transmission resource pool
networking mode. The IPPATH_RTP measurement object provides the RTP performance
measurement in other networking modes. The measurement object type IPPOOL_RTP has only
one function subset, that is, IPPOOL.RTP.
Issue 03 (2015-06-30)

3920
BSC6900 UMTS
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IPPOOL.RTP
Transmission Resource Pool IP Address RTP

Measurement
2.26.1 Transmission Resource Pool IP Address RTP Measurement

(IPPOOL.RTP)
Overview
The support of IP-based IuCS/A interface is an important feature. In order to control the
transmission quality on the Iu/A interface, the performance of IP paths is measured on the basis
of Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol (RTCP)
packets. The transmission quality of the Source and Destination IP Addresses(IP Address Pair)
is related to the measurement items such as Round Trip Time (RTT) of packets, delay jitter of
packets, and packet loss rate, In order to increase the ability of surveillance.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73424358
VS.IPPOOL.RTP.
PktNum.Tx
P14101:Number of
RTP Packets Sent
Between an IP
Address Pair
BSC6900
V900R014
73441280
VS.IPPOOL.RTP.
BytesNum.Tx
P14102:Number of
Bytes in RTP Packets
Sent Between an IP
Address Pair
BSC6900
V900R014
73441281
VS.IPPOOL.RTP.
BytesLen.Rx
P14105:Number of
Bytes in RTP Packets
Received Between
an IP Address Pair
BSC6900
V900R014
73441282
VS.IPPOOL.RTP.
LossPktRatio.Rx
P14108:Downlink
Loss Rate of RTP
Packets Between an
IP Address Pair
BSC6900
V900R014
73424363
VS.IPPOOL.RTP.
PktNum.Rx
P141010:Number of
RTP Packets
Received Between
an IP Address Pair
BSC6900
V900R014

3921
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73441283
VS.IPPOOL.RTP.
AverageJitter
P141011:Mean
Delay Jitter for
Receiving RTP
Packets Between an
IP Address Pair
BSC6900
V900R014
73441284
VS.IPPOOL.RTP.
AverageRtt
P141012:Mean RTT
for RTP Packets
Received Between
an IP Address Pair
BSC6900
V900R014
73441285
VS.IPPOOL.RTP.
BandWidth.Rx
P141013:Receive
Bandwidth for RTP
Packets Received
Between an IP
Address Pair
BSC6900
V900R014
73441286
VS.IPPOOL.RTP.
BandWidth.Tx
P141014:Transmit
Bandwidth for RTP
Packets Sent
Between an IP
Address Pair
BSC6900
V900R014
73441287
VS.IPPOOL.RTP.J
itterOverrun.TimeRatio
P141016:Percentage
of Duration When
Delay Jitter of RTP
Packets Exceeds the
Threshold to Total
Activation Duration
BSC6900
V900R014
73441288
VS.IPPOOL.RTP.
RttOverrun.TimeRatio
P141018:Percentage
of Duration When
RTT of RTP Packets
Exceeds the
Threshold to Total
Activation Duration
BSC6900
V900R014
None
Issue 03 (2015-06-30)

3922
BSC6900 UMTS
Number of RTP Packets Sent Between an IP Address Pair

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

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441280
VS.IPPOOL.RTP.BytesNu
m.Tx
P14102:Number of Bytes in
RTP Packets Sent Between
an IP Address Pair

3923
BSC6900 UMTS
Description
This counter provides the number of bytes in uplink RTP packets sent over the Iu/A interface
between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is incremented by the bytes of the packet payload when an uplink RTP packet is
sent over the Iu/A interface between a certain pair of IP addresses in scenarios where Iu/A over
IP is applied and RTCP is supported.
Formula
None
Unit
kB
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.RTP.BytesNu
m.Tx
WRFD-140207
Iu/Iur Transmission
Number of Bytes in RTP Packets Received Between an IP Address Pair

Counters
Counter ID
Counter Name
Counter Description
73441281
VS.IPPOOL.RTP.BytesLen.
Rx
P14105:Number of Bytes in
RTP Packets Received
Between an IP Address Pair
Description
This counter provides the number of bytes in downlink RTP packets received over the Iu/A
interface between a certain pair of IP addresses in a measurement period.
Measurement point
This counter is incremented by the bytes of the packet payload when a downlink RTP packet is
received over the Iu/A interface between a certain pair of IP addresses in scenarios where Iu/A
over IP is applied and RTCP is supported.
Issue 03 (2015-06-30)

3924
BSC6900 UMTS
Formula
None
Unit
kB
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.RTP.BytesLen.
Rx
WRFD-140207
Iu/Iur Transmission
Downlink Loss Rate of RTP Packets Between an IP Address Pair

Counters
Counter ID
Counter Name
Counter Description
73441282
VS.IPPOOL.RTP.LossPktR
atio.Rx
P14108:Downlink Loss Rate

of RTP Packets Between an
IP Address Pair
Description
This counter provides the downlink loss rate of RTP packets over the Iu/A interface between a
certain pair of IP addresses in a measurement period.
Measurement point
This counter is calculated by using the following formula in scenarios where Iu/A over IP is
applied and RTCP is supported: Downlink loss rate of packets between an IP address pair =
Number of downlink packets lost between an IP address pair/(Number of downlink packets lost
between an IP address pair + Number of packets received between an IP address pair).
Formula
None
Unit
%
Issue 03 (2015-06-30)

3925
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.RTP.LossPktR
atio.Rx
WRFD-140207
Iu/Iur Transmission
Number of RTP Packets Received Between an IP Address Pair

Counters
Counter ID
Counter Name
Counter Description
73424363
VS.IPPOOL.RTP.PktNum.
Rx
P141010:Number of RTP
Packets Received Between
an IP Address Pair
Description
This counter provides the number of downlink packets received over the Iu/A interface between
a certain pair of IP addresses in a measurement period.
Measurement point
This counter is incremented by one when a downlink packet is received over the Iu/A interface
between a certain pair of IP addresses in scenarios where Iu/A over IP is applied and RTCP is
supported.
Formula
None
Unit
packet
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IPPOOL.RTP.PktNum.
Rx
WRFD-140207
Iu/Iur Transmission

3926
BSC6900 UMTS
Mean Delay Jitter for Receiving RTP Packets Between an IP Address Pair
Counters
Counter ID
Counter Name
Counter Description
73441283
VS.IPPOOL.RTP.AverageJitter
P141011:Mean Delay Jitter

for Receiving RTP Packets
Between an IP Address Pair
Description
This counter provides the mean delay jitter for receiving RTP packets over the Iu/A interface
Measurement point
applied and RTCP is supported: Mean delay jitter for receiving RTP packets = Total delay jitter
for receiving RTP packets/Number of RTP traffic statistic reporting times
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.RTP.AverageJitter
WRFD-140207
Iu/Iur Transmission
Mean RTT for RTP Packets Received Between an IP Address Pair

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441284
VS.IPPOOL.RTP.AverageRtt
P141012:Mean RTT for RTP

Packets Received Between
an IP Address Pair

3927
BSC6900 UMTS
Description
This counter provides the mean Round Trip Time (RTT) for packets received over the Iu/A
interface between a certain pair of IP addresses in a measurement period.
Measurement point
applied and RTCP is supported: Mean RTT = Sum of RTT/Number of RTP traffic statistic
reporting times
Formula
None
Unit
ms
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.RTP.AverageRtt
WRFD-140207
Iu/Iur Transmission
Receive Bandwidth for RTP Packets Received Between an IP Address Pair

Counters
Counter ID
Counter Name
Counter Description
73441285
VS.IPPOOL.RTP.BandWidt
h.Rx
P141013:Receive
Bandwidth for RTP Packets
Received Between an IP
Address Pair
Description
This counter provides the receive bandwidth for RTP packets received over the Iu/A interface
Measurement point
applied and RTCP is supported: Transmit bandwidth for RTP packets = Number of bytes of RTP
packets sent between an IP address pair/Duration of a measurement period
Issue 03 (2015-06-30)

3928
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
h.Rx
WRFD-140207
Iu/Iur Transmission
Transmit Bandwidth for RTP Packets Sent Between an IP Address Pair

Counters
Counter ID
Counter Name
Counter Description
73441286
h.Tx
P141014:Transmit
Bandwidth for RTP Packets
Sent Between an IP Address
Pair
Description
This counter provides the transmit bandwidth for RTP packets sent over the Iu/A interface
Measurement point
applied and RTCP is supported: Transmit bandwidth for RTP packets = Number of bytes of RTP
packets sent between an IP address pair/Duration of a measurement period
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

3929
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
h.Tx
WRFD-140207
Iu/Iur Transmission
Percentage of Duration When Delay Jitter of RTP Packets Exceeds the Threshold
to Total Activation Duration
Counters
Counter ID
Counter Name
Counter Description
73441287
VS.IPPOOL.RTP.JitterOver
run.TimeRatio
P141016:Percentage of
Duration When Delay Jitter
of RTP Packets Exceeds the
Threshold to Total
Activation Duration
Description
This counter provides the percentage of the duration when the delay jitter of RTP packets
received over the Iu/A interface between a certain pair of IP addresses exceeds the threshold to
the total activation duration in a measurement period.
Measurement point
applied and RTCP is supported: Percentage of duration when delay jitter for receiving RTP
packets exceeds threshold = Duration when delay jitter for receiving RTP packets exceeds
threshold/Total activation duration where, "Total activation duration" is the sum of activation
periods of all services processed between the IP address pair. "Duration when delay jitter for
receiving RTP packets exceeds threshold" is the total duration when the delay jitters for receiving
RTP packets between the IP address pair exceeds the threshold. The delay for receiving an RTP
packet refers to the duration from the time when the RTP packet is sent by the peer end to the
time when the RTP packet is received at the local end.
Formula
None
Unit
per mill
Issue 03 (2015-06-30)

3930
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.RTP.JitterOver
run.TimeRatio
WRFD-140207
Iu/Iur Transmission
Percentage of Duration When RTT of RTP Packets Exceeds the Threshold to Total
Activation Duration
Counters
Counter ID
Counter Name
Counter Description
73441288
VS.IPPOOL.RTP.RttOverru
n.TimeRatio
P141018:Percentage of
Duration When RTT of RTP
Packets Exceeds the
Threshold to Total
Activation Duration
Description
This counter provides the percentage of the duration when the RTT of RTP packets received
over the Iu/A interface between a certain pair of IP addresses exceeds the threshold to the total
activation duration in a measurement period.
Measurement point
applied and RTCP is supported: Percentage of duration when RTT of RTP packets exceeds
threshold = Duration when RTT of RTP packets exceeds threshold/Total activation duration
where, "Total activation duration" is the sum of activation periods of all services processed
between the IP address pair. "Duration when RTT of RTP packets exceeds threshold" is the total
duration when the RTT of RTP packets between the IP address pair exceeds the threshold. The
RTT of an RTP packet refers to the sum of the duration from the time when the RTP packet is
sent by the local end to the time when the RTP packet is received at the peer end and the duration
from the time when the RTP packet is sent by the peer end to the time when the RTP packet is
received at the local end.
Formula
None
Unit
per mill
Issue 03 (2015-06-30)

3931
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.RTP.RttOverru
n.TimeRatio
WRFD-140207
Iu/Iur Transmission
2.27 Measurement of Transmission Resource Pool Local IP

Address Performance(IPPOOL_SIP)
Overview
Measurement of Transmission Resource Pool Local IP Address Performance indicates the
transmission quality and IP layer transmission performance of each local IP address in the
transmission resource pool.The statistics based on SIP involves control plane and user plane
data, but does not involve the maintenance plane data.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IPPOOL.SIP.IPLAYER
Transmission Resource Pool Local IP

Address IP Layer Measurement
IPPOOL.SIP
Transmission Resource Pool Local IP

Address Transmission Quality Measurement
2.27.1 Transmission Resource Pool Local IP Address IP Layer

Measurement(IPPOOL.SIP.IPLAYER)
Overview
Transmission Resource Pool Local IP Address IP Layer Measurement indicates the IP layer
traffic of each Local IP address that communicates with the IP addresses in a transmission
resource pool. This measurement helps analyze the transmission quality of the system. These
counters provide the received and transmitted data of transmission resource pool local IP address
at the IP layer.
Issue 03 (2015-06-30)

3932
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73441269
VS.IPPOOL.SIP.IP
LAYER.TXPACK
ETS
T7900:Number of
Packets Transmitted
at the IP Layer on
Local IP Address
BSC6900
V900R014
73441270
VS.IPPOOL.SIP.IP
LAYER.TXBYTES
T7901:Number of
the IP Layer on Local
IP Address
BSC6900
V900R014
73441271
VS.IPPOOL.SIP.IP
LAYER.RXPACK
ETS
T7902:Number of
Packets Received at
the IP Layer on Local
IP Address
BSC6900
V900R014
73441272
VS.IPPOOL.SIP.IP
LAYER.RXBYTE
S
T7903:Number of
IP Layer on Local IP
Address
BSC6900
V900R014
73441273
VS.IPPOOL.SIP.IP
LAYER.PEAK.TX
RATE
T7904:Maximum
Address
BSC6900
V900R014
73441274
VS.IPPOOL.SIP.IP
LAYER.MEAN.T
X
T7905:Mean
Address
BSC6900
V900R014
73441276
VS.IPPOOL.SIP.IP
LAYER.PEAK.RX
RATE
T7906:Maximum
Receive Rate at the
Address
BSC6900
V900R014
73441277
VS.IPPOOL.SIP.IP
LAYER.MEAN.R
X
T7907:Mean
Receive Rate at the
Address
BSC6900
V900R014
None
Issue 03 (2015-06-30)

3933
BSC6900 UMTS
Counters Related to the Number of Packets Received or Transmitted at the IP Layer

on Local IP Address
Counters
Counter ID
Counter Name
Counter Description
73441269
VS.IPPOOL.SIP.IPLAYER.
TXPACKETS
on Local IP Address
73441271
RXPACKETS
Local IP Address
Description
These counters provide the number of received and transmitted IP packets on the Local IP
Address that communicates with the IP addresses of a transmission resource pool. These counters
indicate the traffic on the IP layer of a Local IP Address in the transmission resource pool.
Measurement point
the number of IP packets received and transmitted once every five seconds and obtains the total
number at the end of every measurement period.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
TXPACKETS
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
RXPACKETS
WRFD-140207
WRFD-140208
Iu/Iur Transmission
Pool of RNC
Issue 03 (2015-06-30)

3934
BSC6900 UMTS
Counters Related to the Number of Bytes Received or Transmitted at the IP Layer

on Local IP Address
Counters
Counter ID
Counter Name
Counter Description
73441270
TXBYTES
on Local IP Address
73441272
RXBYTES
Local IP Address
Description
These counters provide the number of received and transmitted IP bytes on the Local IP Address
that communicates with the IP addresses of a transmission resource pool. The number of bytes
measured includes the number of bytes in the header of the IP packet and the payload.
Measurement point
the number of bytes received and transmitted once every five seconds and obtains the total
number at the end of every measurement period.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
TXBYTES
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
RXBYTES
WRFD-140207
WRFD-140208
Iu/Iur Transmission
Pool of RNC
Issue 03 (2015-06-30)

3935
BSC6900 UMTS
Counters Related to the Receive Rate or Transmit Rate at the IP Layer on Local IP
Address
Counters
Counter ID
Counter Name
Counter Description
73441273
PEAK.TXRATE
Rate at the IP Layer on Local
IP Address
73441274
MEAN.TX

at the IP Layer on Local IP
Address
73441276
PEAK.RXRATE
Rate at the IP Layer on Local
IP Address
73441277
MEAN.RX
T7907:Mean Receive Rate at

the IP Layer on Local IP
Address
Description
These counters provide the receive rate or transmit rate on the Local IP Address in the
measurement period. The rates measured here include the spending of the IP header and the
payload of the IP packet.
Measurement point
the number of bytes received and transmitted once every five seconds. With this, the system
obtains the maximum number of bytes received or transmitted in five seconds, and the total
number of one measurement period. The maximum speed is calculated with the maximum bytes
in five seconds, and the average speed is calculated with the total bytes in one measurement
period.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

3936
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
PEAK.TXRATE
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
MEAN.TX
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
PEAK.RXRATE
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
MEAN.RX
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
2.27.2 Transmission Resource Pool Local IP Address Transmission

Quality Measurement(IPPOOL.SIP)
Overview
Transmission Resource Pool Local IP Address Transmission Quality Measurement indicates
transmission quality of each Local IP address in a transmission resource pool. This measurement
helps analyze transmission quality of the system and ensures the system stability and reliability.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73441500
VS.IPPOOL.SIP.PI
NG.MeanLOST
T7908:Average Ping
Packet Loss Rate of
Local IP Address
BSC6900
V900R014
None
Issue 03 (2015-06-30)

3937
BSC6900 UMTS
Average Ping Packet Loss Rate of Local IP Address

Counters
Counter ID
Counter Name
Counter Description
73441500
VS.IPPOOL.SIP.PING.Mea
nLOST
T7908:Average Ping Packet

Loss Rate of Local IP
Address
Description
When the ping detection function for adjacent nodes is enabled, the base station controller
periodically sends a ping request packet to the peer NE and receives a response packet from the
peer NE. This counter provides the average packet loss rate of a local IP address in a specified
measurement period. It is used to monitor transmission quality and stability on an end-to-end IP
path between a local IP address on the base station controller and an IP address on the peer NE.
In normal situations, if the average packet loss rate increases, transmission quality on the IP path
becomes poor. If the packet loss rate on a local IP address is high, services are affected. This
counter is not measured when ping detection is performed on faulty links. To query the status
of the ping detection between the local and peer IP addresses, run the DSP ADJNODEPING
command.
Measurement point
In a measurement period, the system samples the number of ping packets sent by the local IP
address and number of ping response packets that have not been received by the local IP address
every 90s. The system obtains the packet loss rate by calculating the ratio of the number of ping
response packets that have not been received by the local IP address to the number of ping packets
sent by the local IP address. At the end of the measurement period, the system divides the
accumulated packet loss rates by the sampling times to obtain the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.IPPOOL.SIP.PING.Mea
nLOST
WRFD-140207
Iu/Iur Transmission
WRFD-140208

Pool of RNC
Issue 03 (2015-06-30)

3938
BSC6900 UMTS
2.28 Measurement of Iur-p Link Performance(IURPLNK)

Overview
Iur-p links are used to connect different physical equipment in an RNC pool. Measurement of
Iur-p Link Performance provides measurement on Iur-p links.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
IURPLNK
Iur-p Link Measurement
2.28.1 Iur-p Link Measurement(IURPLNK)

Overview
Iur-p Link Measurement is used to measure packets sent and received and congestion over an
Iur-p link. It monitors reliability, that is, serviceability and delay on Iur-p links.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73426255
VS.IURPLNK.TX.
PKGNUM
Number of Packets
Sent on the IURP
Link
BSC6900
V900R015C00
73426256
VS.IURPLNK.RX.
PKGNUM
Number of Packets
Received on the
IURP Link
BSC6900
V900R015C00
73426257
VS.IURPLNK.TX.
MAXPKGNUM
Maximum Number
of Packets Sent on
the IURP Link
BSC6900
V900R015C00
73426258
VS.IURPLNK.RX.
MAXPKGNUM
Maximum Number
of Packets Received
on the IURP Link
BSC6900
V900R015C00
73426259
VS.IURPLNK.TX.
BYTES
Number of IP Bytes
Sent on the IURP
Link
BSC6900
V900R015C00
73426260
VS.IURPLNK.RX.
BYTES
Number of IP Bytes
Received on the
IURP Link
BSC6900
V900R015C00

3939
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73426261
VS.IURPLNK.TX.
MAXBYTES
Maximum Number
of IP Bytes Sent on
the IURP Link
BSC6900
V900R015C00
73426262
VS.IURPLNK.RX.
MAXBYTES
Maximum Number
of IP Bytes Received
on the IURP Link
BSC6900
V900R015C00
73426263
VS.IURPLNK.SER
VICE.INTERVAL
Service Duration of
the IURP Link
BSC6900
V900R015C00
73426264
VS.IURPLNK.CO
NGESTION
Number of
Congestions on the
IURP Link
BSC6900
V900R015C00
73426265
VS.IURPLNK.CO
NGESTION.INTE
RVAL
Congestion Duration
of the IURP Link
BSC6900
V900R015C00
73426267
VS.IURPLNK.OV
ERLOAD
Number of
Overloads on the
IURP Link
BSC6900
V900R015C00
73426268
VS.IURPLNK.OV
ERLOAD.INTERV
AL
Overload Duration of
the IURP Link
BSC6900
V900R015C00
73426271
VS.IURPLNK.RE
TX.PKGNUM
Number of Packets
Resent on the IURP
Link
BSC6900
V900R015C00
73446321
VS.IURPLNK.P2P.
RTT.MEANS
Average Iur-p Link

End-to-End
Loopback Delay
BSC6900
V900R017C10
73446322
VS.IURPLNK.P2P.
RTT.MAX
Maximum Iur-p Link

End-to-End
Loopback Delay
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

3940
BSC6900 UMTS
Number of Packets Sent on the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426255
VS.IURPLNK.TX.PKGNU
M
Number of Packets Sent on

the IURP Link
Description
This counter provides the number of data blocks that an Iur-p link sends to the bottom layer.
Measurement point
In a measurement period, the system automatically samples the number of data blocks (including
only user data) sent from an Iur-p link to the bottom layer every 5s. The data blocks contain only
user data. At the end of the measurement period, the system uses the accumulated value as the
value of this counter.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.TX.PKGNU
M
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Number of Packets Received on the IURP Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426256
VS.IURPLNK.RX.PKGNU
M
Number of Packets Received

on the IURP Link

3941
BSC6900 UMTS
Description
This counter provides the number of data blocks that an Iur-p link receives from the bottom
layer.
Measurement point
only user data) that an Iur-p link receives from the bottom layer every 5s. The data blocks contain
only user data. At the end of the measurement period, the system uses the accumulated value as
the value of this counter.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.RX.PKGNU
M
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Maximum Number of Packets Sent on the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426257
VS.IURPLNK.TX.MAXPK
GNUM
Maximum Number of
Packets Sent on the IURP
Link
Description
This counter provides the maximum number of data blocks that an Iur-p link sends to the bottom
layer.
Measurement point
only user data) sent from an Iur-p link to the bottom layer every 5s. The data blocks contain only
Issue 03 (2015-06-30)

3942
BSC6900 UMTS
user data. At the end of the measurement period, the system uses the maximum sampled value
as the value of this counter.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.TX.MAXPK
GNUM
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Maximum Number of Packets Received on the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426258
VS.IURPLNK.RX.MAXPK
GNUM
Maximum Number of
Packets Received on the
IURP Link
Description
This counter provides the maximum number of data blocks that an Iur-p link receives from the
bottom layer.
Measurement point
only user data) that an Iur-p link receives from the bottom layer every 5s. The data blocks contain
only user data. At the end of the measurement period, the system uses the maximum sampled
value as the value of this counter.
Formula
None
Unit
packet
Issue 03 (2015-06-30)

3943
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.RX.MAXPK
GNUM
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Number of IP Bytes Sent on the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426259
VS.IURPLNK.TX.BYTES
Number of IP Bytes Sent on

the IURP Link
Description
This counter provides the number of payload bytes of user data packets at the application layer
that an Iur-p link sends to the bottom layer.
Measurement point
In a measurement period, the system automatically samples the number of bytes (including only
user data) that an Iur-p link sends to the bottom layer every 5s. At the end of the measurement
period, the system uses the accumulated value as the value of this counter.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IURPLNK.TX.BYTES
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy

3944
BSC6900 UMTS
Number of IP Bytes Received on the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426260
VS.IURPLNK.RX.BYTES
Number of IP Bytes
Received on the IURP Link
Description
This counter provides the number of payload bytes of user data packets at the application layer
that an Iur-p link receives from the bottom layer.
Measurement point
user data) that an Iur-p link receives from the bottom layer every 5s. At the end of the
measurement period, the system uses the accumulated value as the value of this counter.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.RX.BYTES
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Maximum Number of IP Bytes Sent on the IURP Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426261
VS.IURPLNK.TX.MAXBYTES
Maximum Number of IP
Bytes Sent on the IURP Link

3945
BSC6900 UMTS
Description
This counter provides the maximum number of payload bytes of user data packets at the
application layer that an Iur-p link sends to the bottom layer.
Measurement point
user data) that an Iur-p link sends to the bottom layer every 5s. At the end of the measurement
period, the system uses the maximum sampled value as the value of this counter.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.TX.MAXBYTES
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Maximum Number of IP Bytes Received on the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426262
VS.IURPLNK.RX.MAXBYTES
Maximum Number of IP
Bytes Received on the IURP
Link
Description
This counter provides the maximum number of payload bytes of user data packets at the
application layer that an Iur-p link receives from the lower layer.
Measurement point
user data) that an Iur-p link receives from the bottom layer every 5s. At the end of the
measurement period, the system uses the maximum sampled value as the value of this counter.
Issue 03 (2015-06-30)

3946
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.RX.MAXBYTES
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Counter ID
Counter Name
Counter Description
73426263
VS.IURPLNK.SERVICE.I
NTERVAL
Service Duration of the IURP

Link
Service Duration of the IURP Link

Counters
Description
This counter provides the service duration of an Iur-p link.
Measurement point
In a measurement period, the system automatically samples the Iur-p link status every 5s and
uses the sampled instantaneous status as the link status within the measurement period. This
counter is measured when the link status is "Normal", "Congested", or "Overload."
Formula
None
Unit
s
Issue 03 (2015-06-30)

3947
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.SERVICE.I
NTERVAL
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Number of Congestions on the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426264
VS.IURPLNK.CONGESTION
Number of Congestions on
the IURP Link
Description
This counter provides the number of times that the status of an Iur-p link changes from "Normal"
to "Congested" in a measurement period.
Measurement point
In a measurement period, this counter is incremented by one each time the status of an Iur-p link
changes from "Normal" to "Congested."
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.IURPLNK.CONGESTION
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy

3948
BSC6900 UMTS
Congestion Duration of the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426265
VS.IURPLNK.CONGESTI
ON.INTERVAL
Congestion Duration of the

IURP Link
Description
This counter provides the total duration of congestion status of an Iur-p link in a measurement
period.
Measurement point
counter is measured when the link status is "Congested."
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.CONGESTI
ON.INTERVAL
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Number of Overloads on the IURP Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73426267
VS.IURPLNK.OVERLOAD
Number of Overloads on the

IURP Link

3949
BSC6900 UMTS
Description
This counter provides the number of times that the status of an Iur-p link changes from "Normal"
to "Overload" in a measurement period.
Measurement point
In a measurement period, this counter is incremented by one each time the status of an Iur-p link
changes to "Overload."
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.OVERLOAD
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Counter ID
Counter Name
Counter Description
73426268
VS.IURPLNK.OVERLOA
D.INTERVAL
Overload Duration of the

IURP Link
Overload Duration of the IURP Link

Counters
Description
This counter measures the total duration of overload occurrences of an Iur-p link in a
measurement period.
Measurement point
counter is measured when the link status is "Overload."
Issue 03 (2015-06-30)

3950
BSC6900 UMTS
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.OVERLOA
D.INTERVAL
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Number of Packets Resent on the IURP Link

Counters
Counter ID
Counter Name
Counter Description
73426271
VS.IURPLNK.RETX.PKG
NUM
Number of Packets Resent on

the IURP Link
Description
This counter provides the number of packets resent over an Iur-p link in a measurement period.
A large value of this counter indicates a high packet loss rate on an Iur-p link.
Measurement point
In a measurement period, this counter is incremented by one each time packets are resent over
an Iur-p link.
Formula
None
Unit
packet
Issue 03 (2015-06-30)

3951
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.IURPLNK.RETX.PKG
NUM
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Average Iur-p Link End-to-End Loopback Delay

Counters
Counter ID
Counter Name
Counter Description
73446321
VS.IURPLNK.P2P.RTT.M
EANS
Average Iur-p Link End-toEnd Loopback Delay
Description
This counter provides the average delay in transmitting or receiving messages over the Iur-p
interface in a measurement period and is used to evaluate the transmission delay of the Iur-p
interface.
Measurement point
In a measurement period, the local RNC sends the peer RNC an end-to-end loopback message
with the send time every 5s. Upon receiving the end-to-end loopback message, the peer RNC
refills an acknowledgement message with the send time in the loopback message and sends the
acknowledgement message to the local RNC. Upon receiving the end-to-end loopback
acknowledgment message, the local RNC subtracts the send time in the message from the current
time to obtain the message loopback delay. The local RNC divides the loopback delay by the
sampling times to obtain the value of this counter. End-to-end loopback messages and their
acknowledgement messages are sent over Iur-p links. Therefore, this counter is effective only
when Iur-p links are running properly.
Formula
None
Unit
ms
Issue 03 (2015-06-30)

3952
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
EANS
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
Maximum Iur-p Link End-to-End Loopback Delay

Counters
Counter ID
Counter Name
Counter Description
73446322
AX
Maximum Iur-p Link End-toEnd Loopback Delay
Description
This counter provides the maximum delay in transmitting or receiving messages over the Iur-p
interface in a measurement period and is used to evaluate the transmission delay of the Iur-p
interface.
Measurement point
In a measurement period, the local RNC sends the peer RNC an end-to-end loopback message
with the send time every 5s. Upon receiving the end-to-end loopback message, the peer RNC
refills an acknowledgement message with the send time in the loopback message and sends the
acknowledgement message to the local RNC. Upon receiving the end-to-end loopback
acknowledgment message, the local RNC subtracts the send time in the message from the current
time to obtain the message loopback delay. This local RNC uses the maximum loopback delay
as the value of this counter. End-to-end loopback messages and their acknowledgement
messages are sent over Iur-p links. Therefore, this counter is effective only when Iur-p links are
running properly.
Formula
None
Unit
ms
Issue 03 (2015-06-30)

3953
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
AX
WRFD-150211
WRFD-150212
RNC in Pool Node

Redundancy
2.29 Measurement of Local IP Address Performance

(LOCAL_IPADDRESS)
Overview
Measurement of Local IP Address Performance indicates the IP-layer transmission performance
of each Ethernet port IP address, trunk group IP address, or device IP address whose type is
logical IP address. This measurement measures data on the signaling plane, user plane, and
maintenance plane. This object type is effective only for FG2c, GOUc and GOUe boards.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
LOCAL.IPADDRESS.IPLAYER
Local IP Address IP Layer Measurement
2.29.1 Local IP Address IP Layer Measurement

(LOCAL.IPADDRESS.IPLAYER)
Overview
Local IP Address IP Layer Measurement provides measurement on the IP-layer traffic for a local
IP address in IP-based networking. This measurement helps analyze system transmission quality
to ensure the stable and reliable operation of the system. This function subset is effective only
for FG2c, GOUc and GOUe boards.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73445327
VS.LOCAL.IPAD
DRESS.IPLAYER.
TXPACKETS
Number of Packets
Transmitted at the IP
Layer Based on the
Local IP Address of
an Interface Board
BSC6900
V900R017C10

3954
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73445328
VS.LOCAL.IPAD
DRESS.IPLAYER.
RXPACKETS
Number of Packets
Received at the IP
Layer Based on the
Local IP Address of
an Interface Board
BSC6900
V900R017C10
73445329
VS.LOCAL.IPAD
DRESS.IPLAYER.
TXBYTES
Number of Bytes
Transmitted at the IP
Layer Based on the
Local IP Address of
an Interface Board
BSC6900
V900R017C10
73445330
VS.LOCAL.IPAD
DRESS.IPLAYER.
RXBYTES
Number of Bytes
Received at the IP
Layer Based on the
Local IP Address of
an Interface Board
BSC6900
V900R017C10
73445331
VS.LOCAL.IPAD
DRESS.IPLAYER.
PEAK.TXRATE
Maximum Transmit
Rate at the IP Layer
Based on the Local
IP Address of an
Interface Board
BSC6900
V900R017C10
73445332
VS.LOCAL.IPAD
DRESS.IPLAYER.
PEAK.RXRATE
Maximum Receive
Based on the Local
IP Address of an
Interface Board
BSC6900
V900R017C10
73445333
VS.LOCAL.IPAD
DRESS.IPLAYER.
MEAN.TX
Average Transmit
Based on the Local
IP Address of an
Interface Board
BSC6900
V900R017C10
73445334
VS.LOCAL.IPAD
DRESS.IPLAYER.
MEAN.RX
Average Receive
Based on the Local
IP Address of an
Interface Board
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

3955
BSC6900 UMTS
Counters Related to the Number of Packets Transmitted and Received at the IP

Layer Based on the Local IP Address of an Interface Board
Counters
Counter ID
Counter Name
Counter Description
73445327
VS.LOCAL.IPADDRESS.I
PLAYER.TXPACKETS
Number of Packets
Based on the Local IP
Address of an Interface
Board
73445328
PLAYER.RXPACKETS

at the IP Layer Based on the
Local IP Address of an
Interface Board
Description
These counters provide the number of packets transmitted or received at the IP layer based on
the local IP address of an interface board in IP-based networking. They are used to reflect the
traffic of a local IP address at the IP layer in IP-based networking. These counters measure the
number of IP packets.
Measurement point
The system samples the number of transmitted or received packets every 5s and accumulates
the sampled values in a measurement period as the values of the counters.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
PLAYER.TXPACKETS
WRFD-150244
Iu/Iur IP Transmission Based

on Dynamic Load Balancing
WRFD-150243
Iub IP Transmission Based

Issue 03 (2015-06-30)

3956
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
PLAYER.RXPACKETS
WRFD-150244

WRFD-150243

Counters Related to the Number of Bytes Transmitted and Received at the IP Layer
Based on the Local IP Address of an Interface Board
Counters
Counter ID
Counter Name
Counter Description
73445329
PLAYER.TXBYTES
Number of Bytes
Based on the Local IP
Address of an Interface
Board
73445330
PLAYER.RXBYTES
Number of Bytes Received at

the IP Layer Based on the
Interface Board
Description
These counters provide the number of bytes transmitted or received at the IP layer based on the
local IP address of an interface board in IP-based networking. They are used to reflect the traffic
of a local IP address at the IP layer in IP-based networking. These counters measure the bytes
of IP packet headers and payload.
Measurement point
The system samples the number of transmitted or received bytes every 5s and accumulates all
sampled bytes in a measurement period as the values of the counters.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

3957
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
PLAYER.TXBYTES
WRFD-150244

WRFD-150243

PLAYER.RXBYTES
WRFD-150244
WRFD-150243

Counters Related to Maximum Transmit or Receive Rate at the IP Layer Based on

the Local IP Address of an Interface Board
Counters
Counter ID
Counter Name
Counter Description
73445331
PLAYER.PEAK.TXRATE
Maximum Transmit Rate at

Interface Board
73445332
PLAYER.PEAK.RXRATE
Maximum Receive Rate at

Interface Board
Description
These counters provide the maximum transmit rate or maximum receive rate at the IP layer based
on the local IP address of an interface board in IP-based networking. They are used to reflect
the load of a local IP address at the IP layer in IP-based networking. These counters measure
the bytes of IP packet headers and payload.
Measurement point
The system samples the number of transmitted or received bytes every 5s and uses the maximum
value as the maximum number of transmitted or received bytes when a measurement period
ends. The maximum transmit rate and maximum receive rate are calculated using the following
formulas: Maximum transmit rate = (Maximum number of transmitted bytes x 8)/(1000 x 5)
Maximum receive rate = (Maximum number of received bytes x 8)/(1000 x 5)
Issue 03 (2015-06-30)

3958
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
PLAYER.PEAK.TXRATE
WRFD-150244

WRFD-150243

PLAYER.PEAK.RXRATE
WRFD-150244
WRFD-150243

Counters Related to Average Transmit or Receive Rate at the IP Layer Based on the
Local IP Address of an Interface Board
Counters
Counter ID
Counter Name
Counter Description
73445333
PLAYER.MEAN.TX
Average Transmit Rate at the

IP Layer Based on the Local
IP Address of an Interface
Board
73445334
PLAYER.MEAN.RX
Average Receive Rate at the

IP Layer Based on the Local
IP Address of an Interface
Board
Description
These counters provide the average transmit rate or average receive rate at the IP layer based on
the local IP address of an interface board in IP-based networking. They are used to reflect the
load of a local IP address at the IP layer in IP-based networking. These counters measure the
bytes of IP packet headers and payload.
Issue 03 (2015-06-30)

3959
BSC6900 UMTS
Measurement point
The system samples the number of transmitted or received bytes every 5s and uses the total
number of transmitted or received bytes when a measurement period ends. The average transmit
rate and average receive rate are calculated using the following formulas: Average transmit rate
= (Total number of transmitted bytes x 8)/(1000 x 5) Average receive rate = (Total number of
received bytes x 8)/(1000 x 5)
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
PLAYER.MEAN.TX
WRFD-150244

WRFD-150243

PLAYER.MEAN.RX
WRFD-150244
WRFD-150243

2.30 Measurement of Logic Port Performance

(LOGIC_PORT)
Overview
Logical port is a type of virtual port configured on physical ports. It provides traffic shaping and
user plane data flow control backpressure. The logical port shaping is mainly used for the traffic
management of each logical port. With this function, the efficiency of transmission statistical
multiplexing is improved and the bandwidth utilization of each operator is ensured during
network sharing. Logical ports can be configured according to the actual transmission
topological structure and bandwidth on transmission nodes. Logical ports implement traffic
shaping and backpressure to ensure that data flows on the transport network are not discarded
due to congestion. The logical ports are configured in IP networking. Measurement of Logic
Port Performance indicates the transmission quality of the logical port on the FG2a, GOUa,
UOIa, FG2c, GOUc, GOUe, PEUc and POUc board.
Issue 03 (2015-06-30)

3960
BSC6900 UMTS
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
LOGIC.PORT
Logical Port Measurement
2.30.1 Logical Port Measurement(LOGIC.PORT)

Overview
The logic ports measurement helps monitor the transmission quality of the running system and
analyze system transmission quality to maintain system stability and reliability. A logical port
performs shaping and reverse pressure on the frames at the data link layer, including MAC
frames, PPP frames, and MP frames. Thus, the logical port belongs to the data link layer. This
function subset takes effect after an IPLOGICPORT is added.
The figure 2 shows the position of the data link layer in the TCP/IP protocol suite.
The position of the Logic Port in the configuration structure is in the figure 2.
Issue 03 (2015-06-30)

3961
BSC6900 UMTS
Figure 2-51 Physical bearer of the Logic Port
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195360
VS.LGCPRT.TXP
ACKETS
T7501:Number of
frames Transmitted
over Logical Port
Earlier than
BSC6900
V900R011
67195361
VS.LGCPRT.TXB
YTES
T7502:Number of
Bytes Transmitted
over Logical Port
Earlier than
BSC6900
V900R011
67195362
VS.LGCPRT.TXD
ROPPACKETS
T7503:Number of
frames Discarded in
Transmission over
Logical Port
Earlier than
BSC6900
V900R011
67195363
VS.LGCPRT.TXD
ROPBYTES
T7504:Number of
Bytes Discarded in
Transmission over a
Logical Port
Earlier than
BSC6900
V900R011

3962
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67204684
VS.LGCPRT.PEA
K.TXRATE
T7506:Maximum
Transmit Rate of
Logical Port
Earlier than
BSC6900
V900R011
67204685
VS.LGCPRT.MEA
N.TXRATE
T7507:Average
Transmit Rate of
Logical Port
Earlier than
BSC6900
V900R011
67204783
VS.LGCPRT.Alloc
ed.Ave.Fwd
T7508:Mean
Forward Bandwidth
Allocated on Logical
Port
Earlier than
BSC6900
V900R011
67204784
VS.LGCPRT.Alloc
ed.Ave.Bwd
T7561:Mean
Backward
Bandwidth
Port
Earlier than
BSC6900
V900R011
67195958
VS.LGCPRT.Alloc
ed.Max.Fwd
T7564:Maximum
Forward Bandwidth
Port
Earlier than
BSC6900
V900R011
67195959
VS.LGCPRT.Alloc
ed.Max.Bwd
T7565:Maximum
Backward
Bandwidth
Port
Earlier than
BSC6900
V900R011
67195960
VS.LGCPRT.Fwd.
Cong
T7566:Number of
Forward
Congestions on
Logical Port
Earlier than
BSC6900
V900R011
67195961
VS.LGCPRT.Fwd.
Cong.Dur
T7567:Duration of
Forward
Congestions on
Logical Port
Earlier than
BSC6900
V900R011
67195962
VS.LGCPRT.Bwd.
Cong
T7568:Number of
Backward
Congestions on
Logical Port
Earlier than
BSC6900
V900R011
67195963
VS.LGCPRT.Bwd.
Cong.Dur
T7569:Duration of
Backward
Congestions on
Logical Port
Earlier than
BSC6900
V900R011

3963
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73441533
VS.LGCPRT.FIVE
.MINUTES.PEAK.
TXRATE
T7540:Maximum
Transmit Rate of
Logical Port(5Minute)
BSC6900
V900R014
None
Number of frames transmitted or discarded over a logical port

Counters
Counter ID
Counter Name
Counter Description
67195360
VS.LGCPRT.TXPACKETS
Transmitted over Logical
Port
67195362
VS.LGCPRT.TXDROPPACKETS
over Logical Port
Description
These counters provide the number of frames transmitted or discarded over a logical port in the
specified measurement period. The measured frames can be MAC frames, PPP frames, or MP
frames, depending on the bearer type of the logical port. The VS.LGCPRT.TXDROPPACKETS
counter is ineffective for FG2c, GOUc and GOUe boards.
Measurement point
Samples are taken every five seconds in the specified measurement period. The data frame will
be discarded if the congestion happens, when the logic port transmits data on the link. The system
obtains the number of frames transmitted or discarded on the link once every five seconds and
Formula
None
Unit
frame
Issue 03 (2015-06-30)

3964
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.TXPACKETS
WRFD-050402
on Iub Interface
VS.LGCPRT.TXDROPPACKETS
WRFD-050402
on Iub Interface
Number of bytes of data transmitted or discarded over a logical port

Counters
Counter ID
Counter Name
Counter Description
67195361
VS.LGCPRT.TXBYTES
Port
67195363
VS.LGCPRT.TXDROPBYTES
over a Logical Port
Description
These counters provide the number of bytes transmitted or discarded over a logical port in the
specified measurement period. They reflect the traffic load of the logical port at the data link
layer. The measured bytes can be the bytes of MAC frames, PPP frames, or MP frames,
depending on the bearer type of the logical port. The VS.LGCPRT.TXDROPBYTES counter is
ineffective for FG2c, GOUc, GOUe, PEUc and POUc boards.
Measurement point
the number of bytes transmitted or discarded on the link once every five seconds and obtains
Formula
None
Unit
byte
Issue 03 (2015-06-30)

3965
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.TXBYTES
WRFD-050402
on Iub Interface
VS.LGCPRT.TXDROPBYTES
WRFD-050402
on Iub Interface
Measurement of the Transmit Rate of the Logic Port

Counters
Counter ID
Counter Name
Counter Description
67204684
VS.LGCPRT.PEAK.TXRA
TE
Rate of Logical Port
67204685
VS.LGCPRT.MEAN.TXRA
TE
T7507:Average Transmit
Rate of Logical Port
Description
These measurement counters provide the transmission rate of the logic port in the specified
measurement period. The rates measured here include the spending of the header of the Link
layer frame(could be MAC, PPP or MP frame depending on the bearing type of the logic port)
and the payload.
Measurement point
the number of bytes received and transmitted on the logic port once every five seconds. With
this, the system obtains the maximum number of bytes received or transmitted in five seconds,
and the total number of one measurement period. The maximum speed is calculated with the
measurement period.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

3966
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.PEAK.TXRA
TE
WRFD-050402
on Iub Interface
VS.LGCPRT.MEAN.TXRA
TE
WRFD-050402
on Iub Interface
Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to the

Logic Port
Counters
Counter ID
Counter Name
Counter Description
67204783
VS.LGCPRT.Alloced.Ave.F
wd
T7508:Mean Forward
Bandwidth Allocated on
Logical Port
67204784
VS.LGCPRT.Alloced.Ave.
Bwd
T7561:Mean Backward
Logical Port
67195958
VS.LGCPRT.Alloced.Max.
Fwd
Logical Port
67195959
Bwd
Logical Port
Description
When services using IP transmission access the network, bandwidth admission needs to be
performed on logical ports. These counters provide the average or maximum forward/backward
bandwidth allocated to a logical port in a specified measurement period. The forward direction
indicates the TX direction and the backward direction indicates the RX direction. The average
forward/backward bandwidth allocated to a logical port can reflect the traffic volume in a
measurement period. The maximum forward/backward bandwidth allocated to a logical port can
reflect the maximum traffic volume in a measurement period. T7561 and T7565 counters do not
take effect when the actual flow admission is enabled.
Measurement point
allocated to a logical port every 15s. At the end of the measurement period, the system divides
Issue 03 (2015-06-30)

3967
BSC6900 UMTS
the accumulated value by the sampling times to obtain the average value and uses the maximum
sampled value as the maximum value.
Formula
None
Unit
bit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.Alloced.Ave.F
wd
WRFD-050402
on Iub Interface
VS.LGCPRT.Alloced.Ave.
Bwd
WRFD-050402
on Iub Interface
Fwd
WRFD-050402
on Iub Interface
Bwd
WRFD-050402
on Iub Interface
Measurement of the Number of Congestions on the Logic Port

Counters
Counter ID
Counter Name
Counter Description
67195960
VS.LGCPRT.Fwd.Cong
Congestions on Logical Port
67195962
VS.LGCPRT.Bwd.Cong
Description
congestion remaining threshold configured for a logical port, traffic on the logical port is
counters provide the number of forward or backward congestions on a logical port in a
measurement period. The forward direction indicates the TX direction and the backward
direction indicates the RX direction. These counters can be used together with the duration of
congestion on a logical port to observe the congestion. If traffic on many logical ports is
Issue 03 (2015-06-30)

3968
BSC6900 UMTS
congested for a long time, services are affected. The T7568: Number of Backward Congestions
on Logical Port counter becomes ineffective when the actual flow admission is enabled.
Measurement point
In a measurement period,the counter value is increased by one each time the state of the logic
port changes from non-congestion to congestion in the forward or backward direction(The
remaining available bandwidth is below the congestion remain threshold). This counter of
backward direction is invalid when the real flow access control switch is turned on.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.Fwd.Cong
WRFD-050402
on Iub Interface
VS.LGCPRT.Bwd.Cong
WRFD-050402
on Iub Interface
Measurement of Congestion Duration on the Logic Port

Counters
Counter ID
Counter Name
Counter Description
67195961
VS.LGCPRT.Fwd.Cong.Du
r
67195963
VS.LGCPRT.Bwd.Cong.Du
r
T7569:Duration of
Backward Congestions on
Logical Port
Description
congestion remaining threshold configured for a logical port, traffic on the logical port is
counters provide the duration of congestions on a logical port in a measurement period. The
forward direction indicates the TX direction and the backward direction indicates the RX
Issue 03 (2015-06-30)

3969
BSC6900 UMTS
direction. These counters can be used together with the number of congestions on a logical port
to observe the congestion. If traffic on many logical ports is congested for a long time, services
are affected. The T7569: Duration of Backward Congestions on Logical Port counter becomes
ineffective when the actual flow admission is enabled.
Measurement point
on a logical port. The measurement stops when the congestion relieves. At the end of the
measurement period, the system uses the accumulated duration of forward or backward
congestions as the values of these counters.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.Fwd.Cong.Du
r
WRFD-050402
on Iub Interface
VS.LGCPRT.Bwd.Cong.Du
r
WRFD-050402
on Iub Interface
5-Minute Measurement of the Highest Transmit Rates of of the Logic Port

Counters
Counter ID
Counter Name
Counter Description
73441533
VS.LGCPRT.FIVE.MINUT
ES.PEAK.TXRATE
Rate of Logical Port(5Minute)
Description
These measurement counters provide the transmission rate of the logic port in the 5-Minute
measurement period. The rates measured here include the spending of the header of the Link
layer frame(could be MAC, PPP or MP frame depending on the bearing type of the logic port)
and the payload.
Issue 03 (2015-06-30)

3970
BSC6900 UMTS
Measurement point
1.Within a specified measurement period, the system measures the number of transmitted bytes
every 5 seconds and accumulates the number of bytes at the end of every 5-minute sampling
period to obtain the total number of bytes transmitted within the sampling period.
2.The system calculates the transmit rate within every 5-minute sampling period with the
following formula: Transmit rate within a 5-minute sampling period = Total number of bytes
transmitted within a 5-minute sampling period/300
3.The system compares all of the collected transmit rates to obtain the highest transmit rate
within the specified measurement period, which is the value of the corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.FIVE.MINUT
ES.PEAK.TXRATE
WRFD-050402
on Iub Interface
2.31 Measurement of Logic Port Queue Performance

(LOGIC_PORT_QUEUE)
Overview
One Logical Port can be categorized into multiple scheduling queues according to packet
priorities. Measurement of Logic Port Queue Performance indicates the transmission quality of
the logical port queue on the FG2a, GOUa, UOIa, FG2c, GOUc, GOUe, PEUc and POUc board.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
LOGIC.PORT.QUEUE
Logical Port Queue Measurement

3971
BSC6900 UMTS
2.31.1 Logical Port Queue Measurement(LOGIC.PORT.QUEUE)

Overview
Logical ports are important resources of the Base Station Controller. Each logical port has eight
logical port queues. These queues are identified by different DSCP. A logical port can transmit
the services of different types. That is, the services of different types can be transmitted through
different queues according to certain rules, and the logical port schedules the data in different
queues according to Differentiated Service Code Point (DSCP). You can run the following
commands to query the correspondence between service types and DSCP:
1. You can run the LST TRMMAP command to query the correspondence between service types
and the Per-Hop Behavior (PHB).
2. You can run the LST PHBMAP command to query the correspondence between PHB and
DSCP.
Logical port queues belong to the data link layer. The following figure shows the position of the
data link layer in the TCP/IP protocol suite.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195365
VS.LGCPRT.QUE
UE.TXPACKETS
T7531:Number of
Packets Transmitted
over Logical Port
Queue
Earlier than
BSC6900
V900R011
67195366
VS.LGCPRT.QUE
UE.TXBYTES
T7532:Number of
Bytes Transmitted
over Logical Port
Queue
Earlier than
BSC6900
V900R011

3972
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67195367
VS.LGCPRT.QUE
UE.TXDROPPAC
KETS
T7533:Number of
Transmission over
Logical Port Queue
Earlier than
BSC6900
V900R011
67195368
VS.LGCPRT.QUE
UE.TXDROPBYT
ES
T7534:Number of
Bytes Discarded in
Transmission over
Logical Port Queue
Earlier than
BSC6900
V900R011
67204686
VS.LGCPRT.QUE
UE.PEAK.TXRAT
E
T7536:Maximum
Transmit Rate of
Logical Port Queue
Earlier than
BSC6900
V900R011
None
Measurement of the Transmitted and Discarded Packets over a logical port queue
Counters
Counter ID
Counter Name
Counter Description
67195365
VS.LGCPRT.QUEUE.TXP
ACKETS
Port Queue
67195367
VS.LGCPRT.QUEUE.TXD
ROPPACKETS
over Logical Port Queue
Description
These counters provide the number of frames transmitted or discarded in transmission over a
logical port queue in the specified measurement period. They indicate the transmit traffic volume
of the logical port queue. The frame measured could be MAC, PPP or MP frame depending on
the bearing type of the logic port. The VS.LGCPRT.QUEUE.TXDROPPACKETS counter is
ineffective for FG2c, GOUc and GOUe boards.
Measurement point
Samples are taken every five seconds in the specified measurement period. When the logical
port queue sends data to the circuit side, the data frames may be discarded due to the congestion
of the logical port queue. The system obtains the number of transmitted frames and discarded
frames once every five seconds. The number is accumulated in one measurement period. In this
Issue 03 (2015-06-30)

3973
BSC6900 UMTS
way, the system obtains the total number of transmitted frames and discarded frames in the
measurement period.
Formula
None
Unit
frame
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.QUEUE.TXP
ACKETS
WRFD-050402
on Iub Interface
VS.LGCPRT.QUEUE.TXD
ROPPACKETS
WRFD-050402
on Iub Interface
Measurement of the Transmitted and Discarded Bytes over a logical port queue
Counters
Counter ID
Counter Name
Counter Description
67195366
VS.LGCPRT.QUEUE.TXB
YTES
Port Queue
67195368
VS.LGCPRT.QUEUE.TXD
ROPBYTES
over Logical Port Queue
Description
These counters provide the number of bytes transmitted or discarded over a logical port queue
in the specified measurement period. The measured bytes can be the header and payload of MAC
frames, PPP frames, or MP frames, depending on the bearer type of the logical port. The
VS.LGCPRT.QUEUE.TXDROPBYTES counter is ineffective for FG2c, GOUc, GOUe, PEUc
and POUc boards.
Measurement point
Samples are taken every five seconds in the specified measurement period. The logical port
queue sends data to the circuit side. The system obtains the number of transmitted bytes and
discarded bytes once every five seconds. The number is accumulated in one measurement period.
Issue 03 (2015-06-30)

3974
BSC6900 UMTS
In this way, the system obtains the total number of transmitted bytes and discarded bytes in the
measurement period.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.QUEUE.TXB
YTES
WRFD-050402
on Iub Interface
VS.LGCPRT.QUEUE.TXD
ROPBYTES
WRFD-050402
on Iub Interface
Measurement of the Transmit Rate of logical port queue

Counters
Counter ID
Counter Name
Counter Description
67204686
VS.LGCPRT.QUEUE.PEA
K.TXRATE
Rate of Logical Port Queue
Description
These counters provide the transmit rate of a logical port queue in the specified measurement
period from different perspectives. The rates measured here include the spending of the header
of the Link layer frame(could be MAC, PPP or MP frame depending on the bearing type of the
logic port) and the payload.
Measurement point
Samples are taken every five seconds in the specified measurement period. The logical port
queue sends data to the circuit side. The system obtains the number of transmitted bytes once
every five seconds. The number is accumulated in one measurement period. The maximum
transmit rate can be obtained by dividing the maximum number of transmitted bytes in five
seconds by five. The mean transmit rate can be obtained by dividing the total number of
transmitted bytes in one measurement period by the number of sampling times.
Issue 03 (2015-06-30)

3975
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.LGCPRT.QUEUE.PEA
K.TXRATE
WRFD-050402
on Iub Interface
2.32 Measurement of M3UA Destination Entity

Performance(M3UA_DE)
Overview
The M3UA destination entity and local entity are logical entities mutually interconnected
through M3UA links. According to the M3UA link connection type, destination entities can be
categorized into adjacent and non-adjacent destination entities. M3UA destination entities can
be application server (AS), signaling gateway (SG), or signaling point (SP). Measurement of
M3UA Destination Entity Performance is used to measure M3UA destination entities.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
M3UA.DE
M3UA Destination Entity Measurement
2.32.1 M3UA Destination Entity Measurement(M3UA.DE)

Overview
M3UA Destination Entity Measurement provides the counters related to the number of times
the M3UA destination entity changes to the unavailable state and the duration of M3UA
destination entity in unavailable state.
For details about the M3UA function, see the protocol RFC4666.
Issue 03 (2015-06-30)

3976
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67194647
OS.M3UA.DE.Unavail
T6151:Number of
Times that M3UA
Destination Entity in
Unavailable State
Earlier than
BSC6900
V900R011
67194648
OS.M3UA.DE.Una
vail.Dur
T6152:Duration of
M3UA Destination
Entity in Unavailable
State
Earlier than
BSC6900
V900R011
None
Number of M3UA Destination Entity Changes to Unavailable State

Counters
Counter ID
Counter Name
Counter Description
67194647
OS.M3UA.DE.Unavail
T6151:Number of Times that

M3UA Destination Entity in
Unavailable State
Description
This counter provides the number of times that the status of M3UA destination entity changes
from available to unavailable.
Measurement point
In a measurement period, this counter is incremented by one each time the last route to a
destination entity fails and the destination signaling point becomes unavailable.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3977
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.M3UA.DE.Unavail
WRFD-050409
on Iu Interface
Duration of M3UA Destination Entity in Unavailable State

Counters
Counter ID
Counter Name
Counter Description
67194648
OS.M3UA.DE.Unavail.Dur
T6152:Duration of M3UA
Destination Entity in
Unavailable State
Description
This counter provides the duration during which the M3UA destination entity is unavailable.
Measurement point
In a measurement period, the system samples the status of an M3UA destination entity every
5s. This counter is incremented by five each time the destination entity status is unavailable.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.M3UA.DE.Unavail.Dur
WRFD-050409
on Iu Interface

3978
BSC6900 UMTS
2.33 Measurement of M3UA Link Performance

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

Overview
M3UA link measurement provides the counters related to signaling transmission on the M3UA
link between two M3UA entities.
For details about the M3UA function, see the protocol RFC4666.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194651
OS.M3UA.Lnk.Fail
T6161:Number of
M3UA Link Failures
Earlier than
BSC6900
V900R011
67194652
OS.M3UA.Lnk.Fail
.Dur
T6162:Duration of
M3UA Link Failure
Earlier than
BSC6900
V900R011
67194653
OS.M3UA.Lnk.Co
ng.Dur
T6163:Duration of
M3UA Link
Congestion
Earlier than
BSC6900
V900R011
67194654
OS.M3UA.Lnk.Tx.
Msg
T6164:Number of
Message Units Sent
on M3UA Link
Earlier than
BSC6900
V900R011

3979
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67194655
OS.M3UA.Lnk.Rx.
Msg
T6165:Number of
Messages Units
Received on M3UA
Link
Earlier than
BSC6900
V900R011
67194656
OS.M3UA.Lnk.AS
PM.Tx.Msg
T6166:Number of
ASPM Messages
Sent on M3UA Link
Earlier than
BSC6900
V900R011
67194657
OS.M3UA.Lnk.AS
PM.Rx.Msg
T6167:Number of
ASPM Messages
Received on M3UA
Link
Earlier than
BSC6900
V900R011
None
Number of M3UA Link Failures

Counters
Counter ID
Counter Name
Counter Description
67194651
OS.M3UA.Lnk.Fail
T6161:Number of M3UA
Link Failures
Description
This counter provides the number of times that the status of an M3UA link changes from
available to unavailable.
Measurement point
In a measurement period, the counter is incremented by one when the status of an M3UA link
changes from available to unavailable.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3980
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.M3UA.Lnk.Fail
WRFD-050409
on Iu Interface
Counter ID
Counter Name
Counter Description
67194652
OS.M3UA.Lnk.Fail.Dur
Link Failure
Duration of M3UA Link Failure

Counters
Description
This counter provides the duration during which the M3UA link is unavailable. If multiple
M3UA links are unavailable for a long time, services are affected.
Measurement point
In a measurement period, the system samples the status of an M3UA link every 5s. This counter
is measured each time the link status is "Unavailable." At the end of the measurement period,
the system uses the accumulated value as the value of this counter.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.M3UA.Lnk.Fail.Dur
WRFD-050409
on Iu Interface

3981
BSC6900 UMTS
Duration of M3UA Link Congestion

Counters
Counter ID
Counter Name
Counter Description
67194653
OS.M3UA.Lnk.Cong.Dur
Link Congestion
Description
This counter provides the duration of M3UA link congestion. Traffic on an M3UA link is
congested if the length of the idle section in the message sending queue is lower than the
congestion threshold. Packet loss may occur in a congested M3UA link, and services may be
affected if multiple M3UA links are congested for a long time .
Measurement point
In a measurement period, the system samples the status of an M3UA link every 5s. This counter
is measured each time the link status is "Congested." At the end of the measurement period, the
system uses the accumulated value as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
OS.M3UA.Lnk.Cong.Dur
WRFD-050409
on Iu Interface
Counters Related to the Number of Message Units Sent and Received on M3UA
Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194654
OS.M3UA.Lnk.Tx.Msg
T6164:Number of Message
Units Sent on M3UA Link

3982
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194655
OS.M3UA.Lnk.Rx.Msg
T6165:Number of Messages
Units Received on M3UA
Link
67194656
OS.M3UA.Lnk.ASPM.Tx.
Msg
T6166:Number of ASPM
Messages Sent on M3UA
Link
67194657
OS.M3UA.Lnk.ASPM.Rx.
Msg
T6167:Number of ASPM
Messages Received on
M3UA Link
Description
These counters provide the number of message signaling units (MSUs) sent and received over
an M3UA link.
Counter Name
Description
OS.M3UA.Lnk.Tx.Msg
This counter provides the number of message

signaling units (MSUs) sent on the M3UA
link.
OS.M3UA.Lnk.Rx.Msg
This counter provides the number of message

signaling units (MSUs) received on the
M3UA link.
OS.M3UA.Lnk.ASPM.Tx.Msg
This counter provides the number of ASPM

messages sent on the M3UA link.
OS.M3UA.Lnk.ASPM.Rx.Msg
This counter provides the number of ASPM

messages received on the M3UA link.
Measurement point
In a measurement period, the measurement is triggered when the M3UA link sends the upper
layer signaling message to the peer end or receives the message from the peer end.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3983
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.M3UA.Lnk.Tx.Msg
WRFD-050409
on Iu Interface
OS.M3UA.Lnk.Rx.Msg
WRFD-050409
on Iu Interface
OS.M3UA.Lnk.ASPM.Tx.
Msg
WRFD-050409
on Iu Interface
OS.M3UA.Lnk.ASPM.Rx.
Msg
WRFD-050409
on Iu Interface
2.34 Measurement of M3UA Link Set Performance

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

Overview
M3UA link set measurement provides the counters related to the configuration of the M3UA
link set between the local entity (OSP) and destination entity (DSP). It provides the functions
of signaling transport network layer for the Base Station Control. One link set only has up to 16
M3UA links, and one destination entity has only one M3UA signaling link set.
For details about the M3UA protocol, see the protocol RFC4666.
Issue 03 (2015-06-30)

3984
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67194649
OS.M3UA.Lnkset.
Unavail
T6156:Number of
M3UA Link Set
Failures
Earlier than
BSC6900
V900R011
67194650
OS.M3UA.Lnkset.
Unavail.Dur
T6157:Duration of
M3UA Link Set
Failure
Earlier than
BSC6900
V900R011
None
Number of M3UA Link Set Failures

Counters
Counter ID
Counter Name
Counter Description
67194649
OS.M3UA.Lnkset.Unavail
T6156:Number of M3UA
Link Set Failures
Description
This counter provides the number of times that the status of an M3UA link set changes from
available to unavailable.
Measurement point
In a measurement period, the counter is incremented by one each time the last available M3UA
link becomes unavailable.
Formula
None
Unit
None
Issue 03 (2015-06-30)

3985
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.M3UA.Lnkset.Unavail
WRFD-050409
on Iu Interface
Counter ID
Counter Name
Counter Description
67194650
OS.M3UA.Lnkset.Unavail.
Dur
Link Set Failure
Duration of M3UA Link Set Failure

Counters
Description
This counter provides the duration during which the M3UA link set is unavailable.
Measurement point
In a measurement period, the system samples the status of an M3UA link set every 5s. This
counter is incremented by five each time the link set status is unavailable.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
OS.M3UA.Lnkset.Unavail.
Dur
WRFD-050409
on Iu Interface
2.35 Measurement of MP Group Performance(MLPPP)

Overview
Multi-Link Point-to-Point Protocol (MLPPP) binds multiple PPP links to effectively improve
reliability and bandwidth of links on the transport network. Measurement of MP Performance
Issue 03 (2015-06-30)

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

Overview
Transmission links are important resources of the system. The transmission quality of the
transmission links directly affects the operation of any function of the system. Therefore, the
traffic on MP groups can be measured for the analysis of the transmission quality of the running
system so that the stable and reliable operation of the system can be maintained. This function
subset takes effect after an MP group is added.
MP group belongs to the Link layer of the TCP/IP protocol suite, as figure 1 shows.
In the configuration structure, MLPPP links are between physical ports and logical applications,
Issue 03 (2015-06-30)

3987
BSC6900 UMTS
Figure 2-54 Physical bearer of the MP Group
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194401
VS.MLPPP.TXPA
CKETS
T7300:Number of
frames Transmitted
on an MP Group
Earlier than
BSC6900
V900R011
67194402
VS.MLPPP.RXPA
CKETS
T7301:Number of
frames Received on
an MP Group
Earlier than
BSC6900
V900R011
67194403
VS.MLPPP.BYTESTXTOTAL
T7302:Number of
Bytes of Frames
(Including Frame
Header) Transmitted
on an MP Group
Earlier than
BSC6900
V900R011

3988
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194404
VS.MLPPP.BYTESRXTOTAL
T7303:Number of
Bytes of Frames
(Including Frame
Header) Received on
an MP Group
Earlier than
BSC6900
V900R011
67194405
VS.MLPPP.TXDR
OPPEDPKTS
T7304:Number of
Frames Discarded in
Transmission on an
MP Group
Earlier than
BSC6900
V900R011
67194406
VS.MLPPP.RXERRORPKTS
T7305:Number of
Error Frames
Received on an MP
Group
Earlier than
BSC6900
V900R011
67194409
VS.MLPPP.FAUL
TTIME
T7308:Duration of
Faults in an MP
Group
Earlier than
BSC6900
V900R011
67194410
VS.MLPPP.TXMA
XSPEED
T7311:Maximum
Transmit Rate of an
MP Group
Earlier than
BSC6900
V900R011
67194411
VS.MLPPP.TXMI
NSPEED
T7312:Minimum
Transmit Rate of an
MP Group
Earlier than
BSC6900
V900R011
67194412
VS.MLPPP.TXME
ANSPEED
T7313:Mean
Transmit Rate of an
MP Group
Earlier than
BSC6900
V900R011
67194413
VS.MLPPP.RXMA
XSPEED
T7316:Maximum
Receive Rate of an
MP Group
Earlier than
BSC6900
V900R011
67194414
VS.MLPPP.RXMI
NSPEED
T7317:Minimum
Receive Rate of an
MP Group
Earlier than
BSC6900
V900R011
67194415
VS.MLPPP.RXME
ANSPEED
T7318:Mean
Receive Rate of an
MP Group
Earlier than
BSC6900
V900R011
67204781
VS.MLPPP.Alloce
d.Ave.Fwd
T7320:Mean
forward bandwidth
assigned to an
MLPPP group
Earlier than
BSC6900
V900R011

3989
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204782
VS.MLPPP.Alloce
d.Ave.Bwd
T7323:Mean
backward bandwidth
assigned to an
MLPPP group
Earlier than
BSC6900
V900R011
67195948
VS.MLPPP.Alloce
d.Max.Fwd
T7326:Maximum
Forward bandwidth
assigned to an
MLPPP group
Earlier than
BSC6900
V900R011
67195949
VS.MLPPP.Alloce
d.Max.Bwd
T7327:Maximum
Backward
bandwidth assigned
to an MLPPP group
Earlier than
BSC6900
V900R011
67195950
VS.MLPPP.Fwd.C
ong
T7328:Number of
forward congestions
on an MLPPP group
Earlier than
BSC6900
V900R011
67195951
VS.MLPPP.Fwd.C
ong.Dur
T7329:Duration of
forward congestion
on an MLPPP group
Earlier than
BSC6900
V900R011
67195952
VS.MLPPP.Bwd.C
ong
T7330:Number of
backward
congestions on an
MLPPP group
Earlier than
BSC6900
V900R011
67195953
VS.MLPPP.Bwd.C
ong.Dur
T7391:Duration of
backward congestion
on an MLPPP group
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of frames Received, Transmitted or Discarded on

an MP Group
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194402
VS.MLPPP.RXPACKETS
Received on an MP Group
67194401
VS.MLPPP.TXPACKETS
Transmitted on an MP Group

3990
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194405
VS.MLPPP.TXDROPPEDPKTS
T7304:Number of Frames
on an MP Group
67194406
T7305:Number of Error
Frames Received on an MP
Group
Description
These counters provide the number of frames Received, Transmitted or Discarded on an MP
group in the specified measurement period from different perspectives. They indicate the traffic
volume of the MP group. The frames measured here are MP frames.
Measurement point
the number of frames transmitted, received or discarded on the MP group once every five seconds
Formula
None
Unit
frame
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MLPPP.RXPACKETS
WRFD-050402
on Iub Interface
VS.MLPPP.TXPACKETS
WRFD-050402
on Iub Interface
VS.MLPPP.TXDROPPEDPKTS
WRFD-050402
on Iub Interface
WRFD-050402
on Iub Interface

3991
BSC6900 UMTS
Counters Related to the Number of Bytes of Data Received or Transmitted on an

MP Group
Counters
Counter ID
Counter Name
Counter Description
67194404
T7303:Number of Bytes of
Frames (Including Frame
Header) Received on an MP
Group
67194403
Frames (Including Frame
Header) Transmitted on an
MP Group
Description
These counters provide the number of bytes received or transmitted on an MP group in the
specified measurement period. They indicate the traffic volume of the MP group. The number
of bytes measured includes the number of bytes in the header of the MP frame and the payload.
Measurement point
the number of bytes transmitted or received on the link once every five seconds and obtains the
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-050402
on Iub Interface
WRFD-050402
on Iub Interface

3992
BSC6900 UMTS
Duration of Faults in an MP Group

Counters
Counter ID
Counter Name
Counter Description
67194409
VS.MLPPP.FAULTTIME
an MP Group
Description
This counter provides the duration of faults occur in an MP group in the specified measurement
period.
Measurement point
Samples are taken every five seconds in the specified measurement period. If the MP group is
in faulty state at the current sampling point, five seconds are added to the fault duration of the
link.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.MLPPP.FAULTTIME
WRFD-050402
on Iub Interface
Counters Related to the Receive Rate or Transmit Rate of an MP Group

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194410
VS.MLPPP.TXMAXSPEED
Rate of an MP Group
67194411
VS.MLPPP.TXMINSPEED
T7312:Minimum Transmit
Rate of an MP Group

3993
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194412
VS.MLPPP.TXMEANSPEED

of an MP Group
67194413
VS.MLPPP.RXMAXSPEED
Rate of an MP Group
67194414
VS.MLPPP.RXMINSPEED
T7317:Minimum Receive
Rate of an MP Group
67194415
VS.MLPPP.RXMEANSPEED

an MP Group
Description
These counters provide the receive rate or transmit rate of an MP group in the specified
measurement period from different perspectives. The rates measured here include the header
and the payload of the MP frame.
Measurement point
seconds, and the total number of bytes in one measurement period. The maximum and minimum
speed is calculated with the maximum and minimum bytes in five seconds, and the average speed
is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.MLPPP.TXMAXSPEED
WRFD-050402
on Iub Interface
VS.MLPPP.TXMINSPEED
WRFD-050402
on Iub Interface
VS.MLPPP.TXMEANSPEED
WRFD-050402
on Iub Interface

3994
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.MLPPP.RXMAXSPEED
WRFD-050402
on Iub Interface
VS.MLPPP.RXMINSPEED
WRFD-050402
on Iub Interface
VS.MLPPP.RXMEANSPEED
WRFD-050402
on Iub Interface

MLPPP Group
Counters
Counter ID
Counter Name
Counter Description
67204781
VS.MLPPP.Alloced.Ave.Fw
d
T7320:Mean forward
MLPPP group
67204782
VS.MLPPP.Alloced.Ave.B
wd
T7323:Mean backward
MLPPP group
67195948
VS.MLPPP.Alloced.Max.F
wd
MLPPP group
67195949
VS.MLPPP.Alloced.Max.B
wd
MLPPP group
Description
MLPPP group is a logical concept, which means that multiple PPP links are bound to a group
logically. When services access the network, bandwidth admission needs to be performed on
the MLPPP group. These counters provide the average or maximum forward/backward
bandwidth allocated to an MLPPP group in a specified measurement period. The forward
direction indicates the TX direction and the backward direction indicates the RX direction. The
average forward or backward bandwidth allocated to an MLPPP group indicates the traffic
volume in a measurement period. The maximum forward or backward bandwidth allocated to
an MLPPP group indicates the maximum traffic volume in a measurement period.
Measurement point
allocated to an MLPPP group every 15s. At the end of the measurement period, the system
Issue 03 (2015-06-30)

3995
BSC6900 UMTS
divides the accumulated value by the sampling times to obtain the average value and uses the
Formula
None
Unit
bit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.MLPPP.Alloced.Ave.Fw
d
WRFD-050402
on Iub Interface
VS.MLPPP.Alloced.Ave.B
wd
WRFD-050402
on Iub Interface
VS.MLPPP.Alloced.Max.F
wd
WRFD-050402
on Iub Interface
VS.MLPPP.Alloced.Max.B
wd
WRFD-050402
on Iub Interface
Measurement of the Number of Congestions on an MLPPP Group

Counters
Counter ID
Counter Name
Counter Description
67195950
VS.MLPPP.Fwd.Cong
congestions on an MLPPP
group
67195952
VS.MLPPP.Bwd.Cong
congestions on an MLPPP
group
Description
congestion remaining threshold configured for an MLPPP group, traffic on the MLPPP group
counters provide the number of forward or backward congestions on an MLPPP group in a
Issue 03 (2015-06-30)

3996
BSC6900 UMTS
congestion on an MLPPP group to observe the congestion. If traffic on many MLPPP groups is
Measurement point
In a measurement period, this counter is incremented by one each time the MLPPP group status
changes from non-congestion to congestion, that is, the remaining available bandwidth is less
than the congestion remaining threshold.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.MLPPP.Fwd.Cong
WRFD-050402
on Iub Interface
VS.MLPPP.Bwd.Cong
WRFD-050402
on Iub Interface
Measurement of the Duration of Congestion on an MLPPP Group

Counters
Counter ID
Counter Name
Counter Description
67195951
VS.MLPPP.Fwd.Cong.Dur
congestion on an MLPPP
group
67195953
VS.MLPPP.Bwd.Cong.Dur
congestion on an MLPPP
group
Description
congestion remaining threshold configured for an MLPPP group, traffic on the MLPPP group
counters provide the duration of congestions on an MLPPP group in a measurement period. The
Issue 03 (2015-06-30)

3997
BSC6900 UMTS
direction. These counters can be used together with the number of congestions on an MLPPP
group to observe the congestion. If traffic on many MLPPP groups is congested for a long time,
services are affected.
Measurement point
on an MLPPP group. The measurement stops when the congestion relieves. At the end of the
measurement period, the system uses the accumulated duration of forward or backward
congestion as the values of these counters.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.MLPPP.Fwd.Cong.Dur
WRFD-050402
on Iub Interface
VS.MLPPP.Bwd.Cong.Dur
WRFD-050402
on Iub Interface
2.36 Measurement of MP Queue Performance

(MLPPP_QUEUE)
Overview
One MLPPP group can be categorized into multiple scheduling queues according to packet
priorities. Measurement of MP Queue Performance indicates the transmission quality of the MP
queue on the PEUa, PEUc, POUa or POUc board.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
MLPPP.QUEUE
MP Queue Measurement

3998
BSC6900 UMTS
2.36.1 MP Queue Measurement(MLPPP.QUEUE)

Overview
MP groups are important resources of the Base Station Controller. The transmission quality of
MP groups affects the availability of system functions. Packets carried on MP groups are mapped
onto four or eight queues based on their Differentiated Service Code Point (DSCP). The MHF
parameter determines the number of queues. A MP group can transmit the services of different
types. That is, the services of different types can be transmitted through different queues
according to certain rules, and the MP group schedules the data in different queues according
to priorities. You can run the following commands to query the correspondence between service
types and queues:
DSCP.
3. You can run the LST PHBMAP command to query the correspondence between DSCP and
queues.
MP group queues belong to the data link layer.
In the configuration structure, MLPPP links are between physical ports and logical applications,
Issue 03 (2015-06-30)

3999
BSC6900 UMTS
Figure 2-56 Physical bearer of the MP Queue
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195132
VS.MLPPP.QUEU
E.TXPACKETS
T7331:Number of
Packets Transmitted
on an MP Queue
Earlier than
BSC6900
V900R011
67195133
VS.MLPPP.QUEU
E.TXBYTES
T7332:Number of
an MP Queue
Earlier than
BSC6900
V900R011
67195134
VS.MLPPP.QUEU
E.TXDROPPACK
ETS
T7333:Number of
Transmission on an
MP Queue
Earlier than
BSC6900
V900R011
67195135
VS.MLPPP.QUEU
E.TXDROPBYTES
T7334:Number of
Bytes Discarded in
Transmission on an
MP Queue
Earlier than
BSC6900
V900R011

4000
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204558
VS.MLPPP.QUEU
E.PEAK.TXRATE
T7336:Maximum
Transmit Rate of an
MP Queue
Earlier than
BSC6900
V900R011
67204559
VS.MLPPP.QUEU
E.MEAN.TX
T7337:Mean
Transmit Rate of an
MP Queue
Earlier than
BSC6900
V900R011
None
Counters Related to the Transmitted and Discarded Packets on an MP Queue

Counters
Counter ID
Counter Name
Counter Description
67195132
VS.MLPPP.QUEUE.TXPA
CKETS
Transmitted on an MP Queue
67195134
VS.MLPPP.QUEUE.TXDR
OPPACKETS
on an MP Queue
Description
These counters provide the number of frames transmitted on an MP queue or the number of
transmitted frames discarded on an MP queue in the specified measurement period to indicate
the transmit traffic volume of the MP queue. The frames measured here are MP frames.
Measurement point
the number of frames transmitted or discarded on the link once every five seconds and obtains
Formula
None
Unit
frame
Issue 03 (2015-06-30)

4001
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MLPPP.QUEUE.TXPA
CKETS
WRFD-050402
on Iub Interface
VS.MLPPP.QUEUE.TXDR
OPPACKETS
WRFD-050402
on Iub Interface
Counters Related to the Number of Bytes Transmitted or Discarded on an MP

Queue
Counters
Counter ID
Counter Name
Counter Description
67195133
VS.MLPPP.QUEUE.TXBY
TES
Transmitted on an MP Queue
67195135
VS.MLPPP.QUEUE.TXDR
OPBYTES
on an MP Queue
Description
These counters provide the number of bytes transmitted on an MP queue or the number of
transmitted bytes discarded on an MP queue in the specified measurement period to indicate the
transmit traffic volume of the MP queue. The number of bytes measured includes the number
of bytes in the header of the MP frame and the payload.
Measurement point
Formula
None
Unit
byte
Issue 03 (2015-06-30)

4002
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MLPPP.QUEUE.TXBY
TES
WRFD-050402
on Iub Interface
VS.MLPPP.QUEUE.TXDR
OPBYTES
WRFD-050402
on Iub Interface
Measurement Counters Related to the Transmit Rate of an MP Queue

Counters
Counter ID
Counter Name
Counter Description
67204558
VS.MLPPP.QUEUE.PEAK.
TXRATE
Rate of an MP Queue
67204559
VS.MLPPP.QUEUE.MEAN
.TX

of an MP Queue
Description
These counters provide the transmit rate of an MP queue in the specified measurement period
from different perspectives.
Measurement point
the number of bytes transmitted on the link once every five seconds. With this, the system obtains
the maximum number of bytes transmitted in five seconds, and the total number of one
measurement period. The maximum speed is calculated with the maximum bytes in five seconds,
and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

4003
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.MLPPP.QUEUE.PEAK.
TXRATE
WRFD-050402
on Iub Interface
VS.MLPPP.QUEUE.MEAN
.TX
WRFD-050402
on Iub Interface
2.37 Measurement of MTP3 Destination Signaling Point

Performance(MTP3_DSP)
Overview
Measurement of MTP3 Destination Signaling Point Performance provides measurement on an
MTP3 signaling point.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
MTP3.DSP
MTP3 DSP Measurement
2.37.1 MTP3 DSP Measurement(MTP3.DSP)

Overview
MTP3 DSP Measurement provides the counters related to MTP3 destination signaling point.
MTP3 destination signaling point is a node in SS7 signaling network. The DSPs for a base station
include Serving GPRS Support Node (SGSN), Media Gateway (MGW), MSC server (Mobile
Switching Center Server), and neighboring base station controller.
For details about the M3UA function, see the protocol ITU-T Q.704.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196163
OS.MTP3.DSP.Unavail
T6101:Number of
MTP3 Destination
Signaling point
Failures
Earlier than
BSC6900
V900R011

4004
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67196164
OS.MTP3.DSP.Un
avail.Dur
T6102:Duration of
MTP3 Destination
Signaling point
Failure
Earlier than
BSC6900
V900R011
None
Number of MTP3 Destination Signaling Point Failures

Counters
Counter ID
Counter Name
Counter Description
67196163
OS.MTP3.DSP.Unavail
T6101:Number of MTP3
Destination Signaling point
Failures
Description
This counter provides the number of times that the status of an MTP3 destination signaling point
(DSP) changes from available to unavailable. If an MTP3 DSP is unavailable, no signaling can
be received by this DSP.
Measurement point
In a measurement period, the counter is incremented by one each time the last available MTP3
destination signaling point becomes unavailable because the last available route to the
destination signaling point is faulty.
Formula
None
Unit
None
Issue 03 (2015-06-30)

4005
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.DSP.Unavail
WRFD-010101
Compliance with 3GPP

Specifications
Duration of MTP3 Destination Signaling Point Failure

Counters
Counter ID
Counter Name
Counter Description
67196164
OS.MTP3.DSP.Unavail.Dur
T6102:Duration of MTP3
Destination Signaling point
Failure
Description
This counter provides the duration in which the MTP3 destination signaling point is unavailable.
Measurement point
In a measurement period, the system samples the status of an MTP3 destination signaling point
every 5s. This counter is incremented by five each time the MTP3 destination signaling point is
unavailable.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.MTP3.DSP.Unavail.Dur
WRFD-010101

Specifications

4006
BSC6900 UMTS
2.38 Measurement of MTP3 Link Performance(MTP3_LNK)

Overview
Measurement of MTP3 Link Performance provides measurement on MTP3 links.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
MTP3.LNK
MTP3 Link Measurement
2.38.1 MTP3 Link Measurement(MTP3.LNK)

Overview
MTP3 Link Measurement provides the counters related to MTP3 link. The MTP3 serves as the
signaling transport network layer for a base station controller. It is a signaling transport link
between two signaling points in direct connection. There are up to 16 MTP3 links between two
signaling points.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196165
OS.MTP3.Lnk.Ser
vice.Dur
T6111:Service
Duration of MTP3
Link
Earlier than
BSC6900
V900R011
67196166
OS.MTP3.Lnk.Fail
T6112:Number of
MTP3 Link Failures
Earlier than
BSC6900
V900R011
67196167
OS.MTP3.Lnk.Fail
.Dur
T6113:Out-ofService Duration of
MTP3 Link
Earlier than
BSC6900
V900R011
67196168
OS.MTP3.Lnk.Con
g.Dur
T6114:Duration of
MTP3 Link
Congestion
Earlier than
BSC6900
V900R011
67196169
OS.MTP3.Lnk.LocalInhibit
T6115:Number of
Local Inhibitions on
MTP3 Link
Earlier than
BSC6900
V900R011

4007
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196170
OS.MTP3.Lnk.Loc
alInh.Dur
T6116:Duration of
Local Inhibition on
MTP3 Link
Earlier than
BSC6900
V900R011
67196171
OS.MTP3.Lnk.Rm
tInhibit
T6117:Number of
Remote Inhibitions
on MTP3 Link
Earlier than
BSC6900
V900R011
67196172
OS.MTP3.Lnk.Rm
tInhibit.Dur
T6118:Duration of
Remote Inhibition on
MTP3 Link
Earlier than
BSC6900
V900R011
67196173
OS.MTP3.Lnk.Cho
T6119:Number of
MTP3 Link
Changeovers
Earlier than
BSC6900
V900R011
67196174
OS.MTP3.Lnk.Tx.
Msg
T6120:Number of
Signaling Units Sent
on MTP3 Link
Earlier than
BSC6900
V900R011
67196175
OS.MTP3.Lnk.Rx.
Msg
T6121:Number of
Signaling Units
Received on MTP3
Link
Earlier than
BSC6900
V900R011
67196176
OS.MTP3.Lnk.Con
G
T6122:Number of
MTP3 Link
Congestions
Earlier than
BSC6900
V900R011
67196177
OS.MTP3.Lnk.SIO
.SIF.Tx
T6123:Number of
Bytes of SIO and SIF
Sent on MTP3 Link
Earlier than
BSC6900
V900R011
67196178
OS.MTP3.Lnk.SIO
.SIF.Rx
T6124:Number of
Bytes of SIO and SIF
Received by MTP3
Link
Earlier than
BSC6900
V900R011
67184091
OS.MTP3.Lnk.Rpo
s
T6125:Number of
MTP3 Link Remote
Processor Failures
Earlier than
BSC6900
V900R011
67196179
OS.MTP3.Lnk.Disc
ard.Msg.Cong
T6126:Number of
Messages Discarded
on MTP3 Link Due
to Link Congestion
Earlier than
BSC6900
V900R011
67196180
OS.MTP3.Lnk.Rx.
TFP
T6127:Number of
Transfer-Prohibited
Signals Received on
MTP3 Link
Earlier than
BSC6900
V900R011

4008
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67196181
OS.MTP3.Lnk.Disc
ard.Msg.RouteFail
T6128:Number of
Messages Discarded
on MTP3 Link Due
to Route Fail
Earlier than
BSC6900
V900R011
67196182
OS.MTP3.Lnk.Rx.
TFC
T6129:Number of
Transfer-Controlled
Signals Received on
MTP3 Link
Earlier than
BSC6900
V900R011
73403527
OS.MTP3.Lnk.Rpo
.Dur
T6130:Duration of
MTP3 Link Remote
Processor Fault
Earlier than
BSC6900
V900R011
None
Service Duration of MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196165
OS.MTP3.Lnk.Service.Dur
T6111:Service Duration of
MTP3 Link
Description
This counter provides the service duration of an MTP3 link. If the duration of an MTP3 link in
the operating state is too short, the link fault persists or occurs repeatedly.
Measurement point
In a measurement period, the system samples the status of an MTP3 link every 5s. This counter
is measured each time the link status is "Available." At the end of the measurement period, the
Formula
None
Unit
s
Issue 03 (2015-06-30)

4009
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Service.Dur
WRFD-010101

Specifications
Counter ID
Counter Name
Counter Description
67196166
OS.MTP3.Lnk.Fail
Link Failures
Number of MTP3 Link Failures

Counters
Description
This counter provides the total number of MTP3 link failures for reasons such as MTP3 link
status transition from available state to unavailable state and link test failure.
Measurement point
In a measurement period, this counter is incremented by one each time the MTP3 link is in
service but its underlying link enters the out-of-service state, the MTP3 link is deactivated at the
local end, or the MTP3 link test fails.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Fail
WRFD-010101

Specifications

4010
BSC6900 UMTS
Duration of Out-of-Service MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196167
OS.MTP3.Lnk.Fail.Dur
T6113:Out-of-Service
Duration of MTP3 Link
Description
This counter provides the duration of an MTP3 link in the unavailable state.
Measurement point
In a measurement period, the system samples the status of an MTP3 link every 5s. This counter
is measured each time the link status is "Unavailable." At the end of the measurement period,
the system uses the accumulated value as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Fail.Dur
WRFD-010101

Specifications
Counter ID
Counter Name
Counter Description
67196168
OS.MTP3.Lnk.Cong.Dur
Link Congestion
Duration of MTP3 Link Congestion

Counters
Description
This counter provides the duration of MTP3 link congestion. The base station controller reports
that traffic on an MTP3 link is congested if the message sending queue usage of the MTP3 link
Issue 03 (2015-06-30)

4011
BSC6900 UMTS
exceeds the congestion threshold. If traffic on an MTP3 link is congested, packet loss may occur.
If traffic on multiple MTP3 links is congested, packet loss occurs for a long time, and service
may be affected.
Measurement point
In a measurement period, the system samples the congestion status of the MTP3 link every 5s.
This counter is measured each time the link status is "Congested." At the end of the measurement
period, the system uses the accumulated value as the value of this counter.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Cong.Dur
WRFD-010101

Specifications
Number of Local Inhibitions on MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196169
T6115:Number of Local
Inhibitions on MTP3 Link
Description
This counter provides the number of inhibitions on an MTP3 link at the local end. An inhibited
MTP3 link fails to transmit any signaling messages.
Measurement point
In a measurement period, the counter is incremented by one each time the local end successfully
inhibits the MTP3 link.
Formula
None
Issue 03 (2015-06-30)

4012
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010101

Specifications
Duration of Local Inhibition on MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196170
OS.MTP3.Lnk.LocalInh.Du
r
T6116:Duration of Local
Inhibition on MTP3 Link
Description
This counter provides the duration when an MTP3 link stays locally inhibited after being
inhibited at the local end. An inhibited MTP3 link fails to transmit any signaling messages.
Measurement point
In a measurement period, the system samples the local management status of an MTP3 link
every 5s. This counter is measured each time the local management status is "Prohibited." At
the end of the measurement period, the system uses the accumulated value as the value of this
counter.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.LocalInh.Du
r
WRFD-010101

Specifications

4013
BSC6900 UMTS
Number of Remote Inhibitions on MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196171
OS.MTP3.Lnk.RmtInhibit
T6117:Number of Remote
Inhibitions on MTP3 Link
Description
This counter provides the number of inhibitions on the MTP3 link at the remote signaling point.
An inhibited MTP3 link fails to transmit any signaling messages.
Measurement point
In a measurement period, this counter is incremented by one each time the MTP3 link receives
an INH message from the remote signaling point.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.RmtInhibit
WRFD-010101

Specifications
Duration of Remote Inhibition on MTP3 Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196172
OS.MTP3.Lnk.RmtInhibit.D
ur
T6118:Duration of Remote
Inhibition on MTP3 Link

4014
BSC6900 UMTS
Description
This counter provides the duration of an MTP3 link in inhibited state after it is successfully
inhibited by the remote signaling point. An inhibited MTP3 link fails to transmit any signaling
messages.
Measurement point
In a measurement period, the system samples the remote management status of the MTP3 link
every 5s. This counter is measured each time the remote management status is "Prohibited." At
the end of the measurement period, the system uses the accumulated value as the value of this
counter.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.RmtInhibit.D
ur
WRFD-010101

Specifications
Counter ID
Counter Name
Counter Description
67196173
OS.MTP3.Lnk.Cho
Link Changeovers
Number of MTP3 Link Changeovers

Counters
Description
This counter provides the number of service changeovers from one MTP3 link to another MTP3
link for some reason. After the changeover, the original MPT3 link becomes unavailable.
Measurement point
In a measurement period, this counter is incremented by one in any of the following conditions:
The MTP3 link status changes from "In Service" to "Out of Service". The MTP3 link is operated
or maintained by the local end. The MTP3 link is prohibited by the peer end.
Issue 03 (2015-06-30)

4015
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Cho
WRFD-010101

Specifications
Number of Message Signal Units Sent by MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196174
OS.MTP3.Lnk.Tx.Msg
T6120:Number of Signaling
Units Sent on MTP3 Link
Description
This counter provides the number of message signaling units (MSUs) sent by an MTP3 Link.
Signaling messages include signaling network management messages, signaling link test
messages, and upper-layer signaling messages.
Measurement point
In a measurement period, this counter is incremented by one each time the MTP3 link sends any
of the MSUs to the peer end.
Formula
None
Unit
None
Issue 03 (2015-06-30)

4016
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Tx.Msg
WRFD-010101

Specifications
Number of Message Signal Units Received by MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196175
OS.MTP3.Lnk.Rx.Msg
T6121:Number of Signaling
Units Received on MTP3
Link
Description
This counter provides the number of message signaling units (MSU) received by an MTP3 link.
Signaling messages include signaling network management messages, signaling link test
messages, and upper-layer signaling messages.
Measurement point
In a measurement period, this counter is incremented by one each time the MTP3 link receives
any of the MSUs from the peer end.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Rx.Msg
WRFD-010101

Specifications

4017
BSC6900 UMTS
Number of MTP3 Link Congestions

Counters
Counter ID
Counter Name
Counter Description
67196176
OS.MTP3.Lnk.ConG
Link Congestions
Description
This counter provides the number of MTP3 link congestions. The base station controller reports
that traffic on an MTP3 link is congested if the message sending queue usage of the MTP3 link
exceeds the congestion threshold. When traffic on an MTP3 link is congested, packet loss may
occur. If traffic on multiple MTP3 links is congested, packet loss occurs for a long time and
services may be affected.
Measurement point
In a measurement period, this counter is incremented by one each time the MTP3 link changes
from the non-congestion state to the congestion state.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.ConG
WRFD-010101

Specifications
Number of MSU Bytes Sent by MTP3 Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196177
OS.MTP3.Lnk.SIO.SIF.Tx
SIO and SIF Sent on MTP3
Link

4018
BSC6900 UMTS
Description
This counter provides the number of MSU bytes sent by an MTP3 link. The bytes include
signaling information field (SIF) and service information octet (SIO). The SIF includes upper
layer signaling content and routing label. The SIO includes network indicator and service
indicator.
Measurement point
In a measurement period, this counter is measured when the MTP3 link sends any of the
following messages to the peer end: signaling network management message, signaling link test
message, and upper-layer signaling message.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.SIO.SIF.Tx
WRFD-010101

Specifications
Number of MSU Bytes Received by MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196178
OS.MTP3.Lnk.SIO.SIF.Rx
SIO and SIF Received by
MTP3 Link
Description
This counter provides the number of MSU bytes received by an MTP3 link. The bytes include
signaling information field (SIF) and service information octet (SIO). SIF includes upper layer
signaling content and routing label. SIO includes network indicator and service indicator.
Issue 03 (2015-06-30)

4019
BSC6900 UMTS
Measurement point
In a measurement period, this counter is measured when the MTP3 link receives any of the
following messages from the peer end: signaling network management message, signaling link
test message, and upper-layer signaling message.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.SIO.SIF.Rx
WRFD-010101

Specifications
MTP3 Link Remote Processor Failures

Counters
Counter ID
Counter Name
Counter Description
67184091
OS.MTP3.Lnk.Rpos
Link Remote Processor
Failures
Description
This counter provides the number of times that an MTP3 link remote processor is faulty. When
an MTP3 link remote processor is faulty, the messages on the base station controller side cannot
be sent to the MTP3 and upper layer protocols on the peer end and the signaling transmitted on
this link fails to be processed at the remote end. If the remote processors of multiple MTP3 links
are faulty, services may be affected.
Measurement point
In a measurement period, this counter is incremented by one each time the MTP3 link remote
processor is faulty.
Formula
None
Issue 03 (2015-06-30)

4020
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Rpos
WRFD-010101

Specifications
Number of Messages Discarded on MTP3 Link Due to Link Congestion

Counters
Counter ID
Counter Name
Counter Description
67196179
OS.MTP3.Lnk.Discard.Msg
.Cong
Discarded on MTP3 Link
Due to Link Congestion
Description
This counter provides the number of messages discarded due to MTP3 link congestion. Packet
loss may occur when traffic on an MTP3 link is congested, that is, the message sending queue
usage of the MTP3 link exceeds the congestion threshold. If traffic on multiple links is congested,
packet loss occurs for a long time and services may be affected.
Measurement point
In a measurement period, this counter is incremented by one each time a message is discarded
on the MTP3 link due to link congestion.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
.Cong
WRFD-010101

Specifications

4021
BSC6900 UMTS
Number of Transfer-Prohibited Signals Received on MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196180
OS.MTP3.Lnk.Rx.TFP
T6127:Number of TransferProhibited Signals Received

on MTP3 Link
Description
This counter provides the number of transfer-prohibited signals received over an MTP3 link.If
a transfer-prohibited (TFP) signal is received over an MTP3 link, the MTP3 link becomes
unavailable.
Measurement point
In a measurement period, this counter is incremented by one when a TFP signal is received over
an MTP3 link.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Rx.TFP
WRFD-010101

Specifications
Number of Messages Discarded on MTP3 Link Due to Route Fail

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196181
.RouteFail
Discarded on MTP3 Link
Due to Route Fail

4022
BSC6900 UMTS
Description
This counter provides the number of messages discarded on an MTP3 link due to incorrect routes.
Signaling message loss occurs on an MTP3 link that has an incorrect route, and services may
be affected if multiple MTP3 links have incorrect routes.
Measurement point
In a measurement period, this counter is incremented by one each time a message is discarded
on an MTP3 link due to incorrect routes.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
.RouteFail
WRFD-010101

Specifications
Number of Transfer-Controlled Signals Received on MTP3 Link

Counters
Counter ID
Counter Name
Counter Description
67196182
OS.MTP3.Lnk.Rx.TFC
T6129:Number of TransferControlled Signals Received

on MTP3 Link
Description
This counter provides the number of transfer-controlled (TFC) signals received over an MTP3
link. If a TFC signal is received over an MTP3 link, the related signaling point may be in an
abnormal state such as under congestion.
Measurement point
In a measurement period, this counter is incremented by one each time TFC signal is received
over an MTP3 link.
Issue 03 (2015-06-30)

4023
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Rx.TFC
WRFD-010101

Specifications
Duration of MTP3 Link Remote Processor Fault

Counters
Counter ID
Counter Name
Counter Description
73403527
OS.MTP3.Lnk.Rpo.Dur
Link Remote Processor Fault
Description
This counter provides the duration of MTP3 link remote processor in fault state. If the remote
processor of an MTP3 link fails, the signaling transmitted on this link fails to be processed at
the remote end. The remote processor failure of multiple MTP3 links may affect the services.
Measurement point
In a measurement period, the system samples the remote processor status of an MTP3 link every
5s. This counter is measured each time the remote processor status is "Faulty." At the end of the
measurement period, the system uses the accumulated value as the value of this counter.
Formula
None
Unit
s
Issue 03 (2015-06-30)

4024
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnk.Rpo.Dur
WRFD-010101

Specifications
2.39 Measurement of MTP3 Link Set Performance

(MTP3_LNK_SET)
Overview
The measurement object of MTP3 Link Set Measurement (MTP3_LNK_SET) is used to measure
the MTP3 link set.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
MTP3.LNKSET
MTP3 Link Set Measurement
2.39.1 MTP3 Link Set Measurement(MTP3.LNKSET)

Overview
MTP3 link set measurement provides the counters related to MTP3(Message Transfer Part) link
set. The MTP3 serves as the signaling transport network layer for an Base Station Control. The
MTP3 link set refers to a set of MTP3 links between two signaling points in direct connection.
There is one MTP3 link set between two signalling points.Each MTP3 link set contains a
maximum of 16 MTP3 links.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67196183
OS.MTP3.Lnkset.
Unavail
T6106:Number of
MTP3 Link Set
Failures
Earlier than
BSC6900
V900R011
67196184
OS.MTP3.Lnkset.
Unavail.Dur
T6107:Duration of
MTP3 Link Set
Failure
Earlier than
BSC6900
V900R011

4025
BSC6900 UMTS
None
Number of MTP3 Link Set Failures

Counters
Counter ID
Counter Name
Counter Description
67196183
OS.MTP3.Lnkset.Unavail
Link Set Failures
Description
This counter provides the number of MTP3 link set failures. The MTP3 link set fails when it
changes from the available state to the unavailable state.
Measurement point
In a measurement period, this counter is incremented by one each time the last available MTP3
link in the MTP3 link set is faulty.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnkset.Unavail
WRFD-010101

Specifications
Duration of MTP3 Link Set in Unavailable State

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196184
OS.MTP3.Lnkset.Unavail.D
ur
Link Set Failure

4026
BSC6900 UMTS
Description
This counter provides the duration of an MTP3 link set in unavailable state.
Measurement point
In a measurement period, the system samples the status of an MTP3 link set every 5s. This
counter is incremented by five each time the link set is unavailable.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
OS.MTP3.Lnkset.Unavail.D
ur
WRFD-010101

Specifications
2.40 Measurement of Non-Channelized Optical Port

Performance(NON_CHANNELIZED_OPTICAL_PORT)
Overview
Non-channelized optical interface boards use optical ports to carry upper-layer logical
configurations, including configurations of ATM logical ports, SAAL links, AAL2 paths, IPoA
PVC links. Measurement of Non-channelized Optical Port Performance indicates the
transmission quality of the optical ports on the UOIa and UOIc boards.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
NON.CHANNELIZED.OPTICAL.PORT
Non-Channelized Optical Port Measurement
UOI.BOARD
Maximum UOI Data Rate Measurement

4027
BSC6900 UMTS
2.40.1 Non-Channelized Optical Port Measurement

(NON.CHANNELIZED.OPTICAL.PORT)
Overview
Optical ports are important resources of the Base Station Controller. Therefore, the optical ports
can be measured for the analysis of the transmission quality of the running Base Station
Controller so that the stable and reliable operation of the Base Station Controller can be
maintained. This function subset automatically takes effect after a non-channelized optical
interface board is added.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73416121
VS.NONCHANNE
LIZED.RXCELLS
T7214:Number of
Cells Received on
the Optical Port
BSC6900
V900R012
73416122
VS.NONCHANNE
LIZED.TXCELLS
T7217:Number of
the Optical Port
BSC6900
V900R012
73404139
VS.NONCHANNE
LIZED.FAULTTI
ME
T7222:Duration of
Faults on the Optical
Port
BSC6900
V900R012
73416123
VS.NONCHANNE
LIZED.TXMAXSP
EED
T7225:Highest
Transmit Rate over
the Optical Port
BSC6900
V900R012
73416124
VS.NONCHANNE
LIZED.TXMINSP
EED
T7226:Lowest
Transmit Rate over
the Optical Port
BSC6900
V900R012
73416125
VS.NONCHANNE
LIZED.TXMEANSPEED
T7227:Mean
Transmit Rate over
the Optical Port
BSC6900
V900R012
73416126
VS.NONCHANNE
LIZED.RXMAXSP
EED
T7230:Highest
Receive Rate over
the Optical Port
BSC6900
V900R012
73416127
VS.NONCHANNE
LIZED.RXMINSP
EED
T7231:Lowest
Receive Rate over
the Optical Port
BSC6900
V900R012
73416128
VS.NONCHANNE
LIZED.RXMEANSPEED
T7232:Mean
Receive Rate over
the Optical Port
BSC6900
V900R012

4028
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73444342
VS.NONCHANNE
LIZED.Alloced.Av
e.Fwd
T7212:Mean
forward bandwidth
assigned to an
Optical Port
Earlier than
BSC6900
V900R011
73444343
VS.NONCHANNE
LIZED.Alloced.Av
e.Bwd
T7201:Mean
backward bandwidth
assigned to an
Optical Port
BSC6900
V900R016C00
73428302
VS.NONCHANNE
LIZED.Alloced.Ma
x.Fwd
T7204:Maximum
Forward bandwidth
assigned to an
Optical Port
BSC6900
V900R016C00
73428303
VS.NONCHANNE
LIZED.Alloced.Ma
x.Bwd
T7205:Maximum
Backward
bandwidth assigned
to an Optical Port
BSC6900
V900R016C00
73428304
VS.NONCHANNE
LIZED.Fwd.Cong
T7290:Number of
forward congestions
on an Optical Port
Earlier than
BSC6900
V900R011
73444344
VS.NONCHANNE
LIZED.Fwd.Cong.
Dur
T7291:Duration of
forward congestion
on an Optical Port
Earlier than
BSC6900
V900R011
73428305
VS.NONCHANNE
LIZED.Bwd.Cong
T7292:Number of
backward
congestions on an
Optical Port
BSC6900
V900R016C00
73444345
VS.NONCHANNE
LIZED.Bwd.Cong.
Dur
T7293:Duration of
backward congestion
on an Optical Port
BSC6900
V900R016C00
None
Issue 03 (2015-06-30)

4029
BSC6900 UMTS
Counters Related to the Number of Cells Received or Transmitted on the optical

port
Counters
Counter ID
Counter Name
Counter Description
73416121
VS.NONCHANNELIZED.
RXCELLS
T7214:Number of Cells
Received on the Optical Port
73416122
VS.NONCHANNELIZED.
TXCELLS
T7217:Number of Cells
Transmitted on the Optical
Port
Description
These counters provide the number of cells received or transmitted on the optical port in the
measurement period.
Measurement point
the number of IEs transmitted on the port once every five seconds and obtains the total number
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.NONCHANNELIZED.
RXCELLS
WRFD-05030103
ATM over Non-channelized

STM-1/OC-3c on Iub/Iu/Iur
Interface
VS.NONCHANNELIZED.
TXCELLS
WRFD-05030103

Interface

4030
BSC6900 UMTS
Duration of Faults in the optical port

Counters
Counter ID
Counter Name
Counter Description
73404139
VS.NONCHANNELIZED.F
AULTTIME
the Optical Port
Description
This counter provides the duration of faults in the optical port in the measurement period.
Measurement point
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.NONCHANNELIZED.F
AULTTIME
WRFD-05030103

Interface
Counters Related to the Receive Rate or Transmit Rate over the optical port
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73416123
VS.NONCHANNELIZED.
TXMAXSPEED
Rate over the Optical Port
73416124
VS.NONCHANNELIZED.
TXMINSPEED
T7226:Lowest Transmit
Rate over the Optical Port
73416125
VS.NONCHANNELIZED.
TXMEANSPEED

over the Optical Port

4031
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
73416126
VS.NONCHANNELIZED.
RXMAXSPEED

73416127
VS.NONCHANNELIZED.
RXMINSPEED
T7231:Lowest Receive Rate

73416128
VS.NONCHANNELIZED.
RXMEANSPEED
T7232:Mean Receive Rate

Description
These counters provide the transmit rate over the optical port in the measurement period.
Measurement point
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.NONCHANNELIZED.
TXMAXSPEED
WRFD-05030103

Interface
VS.NONCHANNELIZED.
TXMINSPEED
WRFD-05030103

Interface
VS.NONCHANNELIZED.
TXMEANSPEED
WRFD-05030103

Interface
VS.NONCHANNELIZED.
RXMAXSPEED
WRFD-05030103

Interface

4032
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.NONCHANNELIZED.
RXMINSPEED
WRFD-05030103

Interface
VS.NONCHANNELIZED.
RXMEANSPEED
WRFD-05030103

Interface

Optical Port
Counters
Counter ID
Counter Name
Counter Description
73444342
VS.NONCHANNELIZED.
Alloced.Ave.Fwd
T7212:Mean forward
Optical Port
73444343
VS.NONCHANNELIZED.
Alloced.Ave.Bwd
T7201:Mean backward
Optical Port
73428302
VS.NONCHANNELIZED.
Alloced.Max.Fwd
Optical Port
73428303
VS.NONCHANNELIZED.
Alloced.Max.Bwd
Optical Port
Description
When services access the network, bandwidth admission needs to be performed on optical ports.
These counters provide the average or maximum forward/backward bandwidth allocated to an
optical port in a measurement period. The forward direction indicates the TX direction and the
backward direction indicates the RX direction. The average forward or backward bandwidth
allocated to an optical port can reflect the traffic volume in a measurement period. The maximum
forward or backward bandwidth allocated to an optical port can reflect the maximum traffic
volume in a measurement period.
Measurement point
In a measurement period, these counters automatically samples the forward or backward
bandwidth allocated to an optical port every 15s. At the end of the measurement period, the
system divides the accumulated value by the sampling times to obtain the average value and
uses the maximum sampled value as the maximum value.
Issue 03 (2015-06-30)

4033
BSC6900 UMTS
Formula
None
Unit
bit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.NONCHANNELIZED.
Alloced.Ave.Fwd
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.NONCHANNELIZED.
Alloced.Ave.Bwd
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.NONCHANNELIZED.
Alloced.Max.Fwd
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.NONCHANNELIZED.
Alloced.Max.Bwd
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

4034
BSC6900 UMTS
Measurement of the Number of Congestions on an Optical Port

Counters
Counter ID
Counter Name
Counter Description
73428304
VS.NONCHANNELIZED.F
wd.Cong
congestions on an Optical
Port
73428305
VS.NONCHANNELIZED.
Bwd.Cong
congestions on an Optical
Port
Description
congestion remaining threshold configured for an optical port, traffic on the optical port is
counters provide the number of forward or backward congestions on an optical port in a
congestion on an optical port to observe the congestion. If traffic on many optical ports is
Measurement point
In a measurement period, this counter is incremented by one each time forward or backward
congestion occurs on an optical port, that is, the remaining available bandwidth is less than the
congestion remaining threshold.
Formula
None
Unit
None
Issue 03 (2015-06-30)

4035
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.NONCHANNELIZED.F
wd.Cong
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.NONCHANNELIZED.
Bwd.Cong
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Measurement of the Duration of Congestion on an Optical Port

Counters
Counter ID
Counter Name
Counter Description
73444344
VS.NONCHANNELIZED.F
wd.Cong.Dur
congestion on an Optical Port
73444345
VS.NONCHANNELIZED.
Bwd.Cong.Dur
congestion on an Optical Port
Description
congestion remaining threshold configured for an optical port, traffic on the optical port is
counters provide the duration of congestions on an optical port in a measurement period. The
direction. These counters can be used together with the number of congestions on an optical port
to observe the congestion. If traffic on many optical ports is congested for a long time, services
are affected.
Measurement point
In a measurement, the measurement starts when forward or backward congestion occurs on an
optical port. The measurement stops when the congestion relieves. At the end of the measurement
period, the system uses the accumulated value as the values of these counters.
Issue 03 (2015-06-30)

4036
BSC6900 UMTS
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.NONCHANNELIZED.F
wd.Cong.Dur
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
VS.NONCHANNELIZED.
Bwd.Cong.Dur
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
2.40.2 Maximum UOI Data Rate Measurement(UOI.BOARD)

Overview
The measuerment indicates the flux of all the UOI board. This function subset automatically
takes effect after the UOI interface board is added.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73416129
VS.UOI.RXMAXSPEED
T7236:Maximum
Receive Rate of UOI
board
BSC6900
V900R012
73416130
VS.UOI.TXMAXSPEED
T7237:Maximum
Transmit Rate of
UOI board
BSC6900
V900R012

4037
BSC6900 UMTS
None
Maximum receiving and transmitting rate of UOI board

Counters
Counter ID
Counter Name
Counter Description
73416129
VS.UOI.RXMAXSPEED
Rate of UOI board
73416130
VS.UOI.TXMAXSPEED
Rate of UOI board
Description
These counters provide the maximum receive rate or transmit rate of an UOI board in the
measurement period.
Measurement point
the number of bytes received and transmitted on the board once every five seconds. The
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.UOI.RXMAXSPEED
WRFD-05030103

Interface
VS.UOI.TXMAXSPEED
WRFD-05030103

Interface

4038
BSC6900 UMTS
2.41 Measurement of NodeB OAM Flow Performance

(OAM_FLOW)
Overview
The EMS synchronizes the NodeB IP address from the controller to set up OM channels to the
NodeB. Measurement of NodeB OAM Flow Performance indicates the OAM traffic between
the RNC and the NodeB. Measurement of NodeB OAM Flow Performance reflects the
transmission quality at the IP layer of IP and hybrid IP NodeB OM flows, the part of IP NodeB
OM flows when the ATM/IP dual-stack transmission is used.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
OAM.FLOW
NodeB OAM Flow Measurement
2.41.1 NodeB OAM Flow Measurement(OAM.FLOW)

Overview
The operation and maintenance (OM) of the NodeB is performed through the OM channel
between the RNC and the NodeB. The OM flow measurement at the IP layer indicates the
transmission quality of the OM channel. This function subset takes effect after the NodeB IP is
added.
Figure 1 shows the location of the IP Layer in the procotol.
Issue 03 (2015-06-30)

4039
BSC6900 UMTS
Figure 2-58 Physical bearer of the logical port for the NodeB OAM
The position of the OAM flow in the configuration structure is in figure 2 and figure 3.
Figure 2-59 Physical bearer of the NodeB OAM
Issue 03 (2015-06-30)

4040
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195465
VS.OAM.FLOW.T
XPACKETS
Number of Packets
Transmitted on OM
Flow
Earlier than
BSC6900
V900R011
67195466
VS.OAM.FLOW.T
XBYTES
Number of Bytes
Transmitted on OM
Flow
Earlier than
BSC6900
V900R011
67195467
VS.OAM.FLOW.T
XDROPPACKETS
Number of Packets
Discarded in
Transmission on OM
Flow
Earlier than
BSC6900
V900R011
67195468
VS.OAM.FLOW.T
XDROPBYTES
Number of Bytes
Discarded in
Transmission on OM
Flow
Earlier than
BSC6900
V900R011
67195469
VS.OAM.FLOW.R
XPACKETS
Number of Packets
Received on OM
Flow
Earlier than
BSC6900
V900R011
67195470
VS.OAM.FLOW.R
XBYTES
Number of Bytes
Received on OM
Flow
Earlier than
BSC6900
V900R011
67195471
VS.OAM.FLOW.R
XDROPPACKETS
Number of Packets
Discarded in
Reception on OM
Flow
Earlier than
BSC6900
V900R011
67195472
VS.OAM.FLOW.R
XDROPBYTES
Number of Bytes
Discarded in
Reception on OM
Flow
Earlier than
BSC6900
V900R011
67195473
VS.OAM.FLOW.P
EAK.TXBYTES
Maximum Number
of Bytes Transmitted
on OM Flow
Earlier than
BSC6900
V900R011
67204726
VS.OAM.FLOW.P
EAK.TXRATE
Maximum Transmit
Rate on OM Flow
Earlier than
BSC6900
V900R011
67204727
VS.OAM.FLOW.
MEANS.TX
Average Transmit
Rate on OM Flow
Earlier than
BSC6900
V900R011

4041
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67195474
VS.OAM.FLOW.P
EAK.RXBYTES
Maximum Number
of Bytes Received on
OM Flow
Earlier than
BSC6900
V900R011
67204728
VS.OAM.FLOW.P
EAK.RXRATE
Maximum Receive
Rate on OM Flow
Earlier than
BSC6900
V900R011
67204729
VS.OAM.FLOW.
MEANS.RX
Average Receive
Rate on OM Flow
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of Packets Received or Transmitted in the OAM

FLOW
Counters
Counter ID
Counter Name
Counter Description
67195469
VS.OAM.FLOW.RXPACK
ETS

on OM Flow
67195465
VS.OAM.FLOW.TXPACKETS
Number of Packets
Transmitted on OM Flow
67195467
VS.OAM.FLOW.TXDROPPACKETS
Number of Packets
on OM Flow
67195471
VS.OAM.FLOW.RXDROP
PACKETS
Number of Packets
Discarded in Reception on
OM Flow
Description
These counters provide the number of packets received or transmitted in the OAM FLOW at the
IP layer in the specified measurement period.
Issue 03 (2015-06-30)

4042
BSC6900 UMTS
Measurement point
the number of packets transmitted, received or discarded on the link once every five seconds
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.OAM.FLOW.RXPACK
ETS
WRFD-050402
on Iub Interface
VS.OAM.FLOW.TXPACKETS
WRFD-050402
on Iub Interface
VS.OAM.FLOW.TXDROPPACKETS
WRFD-050402
on Iub Interface
VS.OAM.FLOW.RXDROP
PACKETS
WRFD-050402
on Iub Interface
Counters Related to the Number of Bytes Received or Transmitted in the OAM

FLOW
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67195470
VS.OAM.FLOW.RXBYTE
S

on OM Flow
67195466
VS.OAM.FLOW.TXBYTE
S
Number of Bytes
67195468
VS.OAM.FLOW.TXDROPBYTES
Number of Bytes Discarded

in Transmission on OM Flow
67195472
VS.OAM.FLOW.RXDROP
BYTES
Number of Bytes Discarded

in Reception on OM Flow
67195473
VS.OAM.FLOW.PEAK.TX
BYTES
Maximum Number of Bytes


4043
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67195474
VS.OAM.FLOW.PEAK.RX
BYTES
Maximum Number of Bytes

Received on OM Flow
Description
These counters provide the number of bytes received or transmitted in the OAM FLOW at the
IP layer in the specified measurement period. The number of bytes measured includes the number
of bytes in the header of the IP packet and the payload.
Measurement point
the number of bytes transmitted, received or discarded on the link once every five seconds. With
this, the system obtains the maximum number of bytes received or transmitted in five seconds,
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.OAM.FLOW.RXBYTE
S
WRFD-050402
on Iub Interface
VS.OAM.FLOW.TXBYTE
S
WRFD-050402
on Iub Interface
VS.OAM.FLOW.TXDROPBYTES
WRFD-050402
on Iub Interface
VS.OAM.FLOW.RXDROP
BYTES
WRFD-050402
on Iub Interface
VS.OAM.FLOW.PEAK.TX
BYTES
WRFD-050402
on Iub Interface
VS.OAM.FLOW.PEAK.RX
BYTES
WRFD-050402
on Iub Interface

4044
BSC6900 UMTS
Counters Related to the Receive Rate or Transmit Rate of the OAM FLOW
Counters
Counter ID
Counter Name
Counter Description
67204728
VS.OAM.FLOW.PEAK.RX
RATE
Maximum Receive Rate on

OM Flow
67204726
VS.OAM.FLOW.PEAK.TX
RATE
Maximum Transmit Rate on

OM Flow
67204727
VS.OAM.FLOW.MEANS.T
X
Average Transmit Rate on

OM Flow
67204729
VS.OAM.FLOW.MEANS.
RX
Average Receive Rate on

OM Flow
Description
These counters provide the receive rate or transmit rate of the OAM FLOW at the IP layer in
the specified measurement period. The rates measured here include the spending of the IP header
and the payload of the IP packet.
Measurement point
period.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.OAM.FLOW.PEAK.RX
RATE
WRFD-050402
on Iub Interface
VS.OAM.FLOW.PEAK.TX
RATE
WRFD-050402
on Iub Interface

4045
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.OAM.FLOW.MEANS.T
X
WRFD-050402
on Iub Interface
VS.OAM.FLOW.MEANS.
RX
WRFD-050402
on Iub Interface
2.42 Measurement of PPP Link Performance(PPP)

Overview
PPP is a link layer protocol used to transmit data packets between equivalent units. PPP links
provide full-duplex and transmit data packets in sequence. Measurement of PPP Link
Performance indicates the transmission quality of a PPP link on the PEUa, PEUc, POUa, POUc
or UOIa board.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
PPP
PPP Link Measurement
2.42.1 PPP Link Measurement(PPP)

Overview
The quality of transmission links directly affects the system performance. The PPP link
reliability. This function subset takes effect after a PPP link is added.
PPP link belongs to the Link layer of the TCP/IP protocol suite, as figure 1 shows.
Issue 03 (2015-06-30)

4046
BSC6900 UMTS
In the configuration structure, PPP links are between physical ports and logical applications, as
Figure 2-61 Physical bearer of the PPP Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194417
VS.PPP.TXPACK
ETS
T7345:Number of
Frames Transmitted
on a PPP Link
Earlier than
BSC6900
V900R011
67194418
VS.PPP.TXBYTES
T7346:Number of
a PPP Link.
Earlier than
BSC6900
V900R011
67194419
VS.PPP.TXDROPS
T7347:Number of
Frames Discarded in
Transmission on a
PPP Link
Earlier than
BSC6900
V900R011
67194420
VS.PPP.RXPACK
ETS
T7348:Number of
Frames Successfully
Received on a PPP
Link
Earlier than
BSC6900
V900R011

4047
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194421
VS.PPP.RXBYTES
T7349:Number of
Bytes Received on a
PPP Link
Earlier than
BSC6900
V900R011
67194422
VS.PPP.RXDROP
S
T7350:Number of
Frames Discarded in
Reception on a PPP
Link
Earlier than
BSC6900
V900R011
67194425
VS.PPP.FAULTTI
ME
T7353:Duration of
Faults on a PPP Link
Earlier than
BSC6900
V900R011
67194426
VS.PPP.TXMAXSPEED
T7356:Maximum
Transmit Rate of a
PPP Link
Earlier than
BSC6900
V900R011
67194427
VS.PPP.TXMINSPEED
T7357:Minimum
Transmit Rate of a
PPP Link
Earlier than
BSC6900
V900R011
67194428
VS.PPP.TXMEANSPEED
T7358:Average
Transmit Rate of a
PPP Link
Earlier than
BSC6900
V900R011
67194429
VS.PPP.RXMAXSPEED
T7361:Maximum
Receive Rate of a
PPP Link
Earlier than
BSC6900
V900R011
67194430
VS.PPP.RXMINSPEED
T7362:Minimum
Receive Rate of a
PPP Link
Earlier than
BSC6900
V900R011
67194431
VS.PPP.RXMEAN
SPEED
T7363:Average
Receive Rate of a
PPP Link
Earlier than
BSC6900
V900R011
67204198
VS.PPP.Alloced.Av
e.Fwd
T7365:Mean
forward bandwidth
assigned to a PPP
link
Earlier than
BSC6900
V900R011
67204199
VS.PPP.Alloced.Av
e.Bwd
T7368:Mean
backward
Bandwidth Assigned
to a PPP Link
Earlier than
BSC6900
V900R011
67193245
VS.PPP.Alloced.M
ax.Fwd
T7371:Maximum
forward bandwidth
assigned to a PPP
link
Earlier than
BSC6900
V900R011

4048
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67193246
VS.PPP.Alloced.M
ax.Bwd
T7372:Maximum
backward bandwidth
assigned to a PPP
link
Earlier than
BSC6900
V900R011
67193247
VS.PPP.Fwd.Cong
T7373:Number of
forward congestions
on a PPP link
Earlier than
BSC6900
V900R011
67193248
VS.PPP.Fwd.Cong.
Dur
T7374:Duration of
forward congestion
on a PPP link
Earlier than
BSC6900
V900R011
67193249
VS.PPP.Bwd.Cong
T7375:Number of
backward
congestions on a PPP
link
Earlier than
BSC6900
V900R011
67193250
VS.PPP.Bwd.Cong.
Dur
T7376:Duration of
backward congestion
on a PPP link
Earlier than
BSC6900
V900R011
None
Number of Frames Received, Transmitted or Discarded on a PPP Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194420
VS.PPP.RXPACKETS
Successfully Received on a
PPP Link
67194417
VS.PPP.TXPACKETS
Transmitted on a PPP Link
67194419
VS.PPP.TXDROPS
on a PPP Link
67194422
VS.PPP.RXDROPS
Discarded in Reception on a
PPP Link

4049
BSC6900 UMTS
Description
These counters provide the number of frames received or transmitted on a PPP link in the
specified measurement period. The frames measured here are PPP frames.
Measurement point
the number of frames transmitted, received or discarded on the link once every five seconds and
Formula
None
Unit
frame
Related Features
Counter Name
Feature ID
Feature Name
VS.PPP.RXPACKETS
WRFD-050402
on Iub Interface
VS.PPP.TXPACKETS
WRFD-050402
on Iub Interface
VS.PPP.TXDROPS
WRFD-050402
on Iub Interface
VS.PPP.RXDROPS
WRFD-050402
on Iub Interface
Number of Bytes Received or Transmitted on a PPP Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194421
VS.PPP.RXBYTES
Received on a PPP Link
67194418
VS.PPP.TXBYTES
Transmitted on a PPP Link.

4050
BSC6900 UMTS
Description
These counters provide the number of bytes received or transmitted on a PPP link in the specified
measurement period. The number of bytes measured includes the number of bytes in the header
of the PPP frame and the payload.
Measurement point
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.PPP.RXBYTES
WRFD-050402
on Iub Interface
VS.PPP.TXBYTES
WRFD-050402
on Iub Interface
Counter ID
Counter Name
Counter Description
67194425
VS.PPP.FAULTTIME
a PPP Link
Duration of Faults on a PPP Link

Counters
Description
This counter provides the duration of faults on a PPP link in the specified measurement period.
Measurement point
faulty state at the current sampling point, five seconds are added to the fault duration of the link.
Issue 03 (2015-06-30)

4051
BSC6900 UMTS
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.PPP.FAULTTIME
WRFD-050402
on Iub Interface
Counters Related to the Receive Rate or Transmit Rate of a PPP Link

Counters
Counter ID
Counter Name
Counter Description
67194426
VS.PPP.TXMAXSPEED
Rate of a PPP Link
67194427
VS.PPP.TXMINSPEED
Rate of a PPP Link
67194428
VS.PPP.TXMEANSPEED
Rate of a PPP Link
67194429
VS.PPP.RXMAXSPEED
Rate of a PPP Link
67194430
VS.PPP.RXMINSPEED
Rate of a PPP Link
67194431
VS.PPP.RXMEANSPEED
T7363:Average Receive
Rate of a PPP Link
Description
These counters provide the receive rate or transmit rate of a PPP link in the specified
measurement period. The rates measured here include the spending of the header and the payload
of the PPP frame.
Measurement point
Issue 03 (2015-06-30)

4052
BSC6900 UMTS
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PPP.TXMAXSPEED
WRFD-050402
on Iub Interface
VS.PPP.TXMINSPEED
WRFD-050402
on Iub Interface
VS.PPP.TXMEANSPEED
WRFD-050402
on Iub Interface
VS.PPP.RXMAXSPEED
WRFD-050402
on Iub Interface
VS.PPP.RXMINSPEED
WRFD-050402
on Iub Interface
VS.PPP.RXMEANSPEED
WRFD-050402
on Iub Interface
Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a

PPP Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67204198
VS.PPP.Alloced.Ave.Fwd
T7365:Mean forward
bandwidth assigned to a PPP
link
67204199
VS.PPP.Alloced.Ave.Bwd
T7368:Mean backward
Bandwidth Assigned to a
PPP Link

4053
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67193245
VS.PPP.Alloced.Max.Fwd
T7371:Maximum forward
link
67193246
VS.PPP.Alloced.Max.Bwd
T7372:Maximum backward
link
Description
When services access the network, bandwidth admission needs to be performed on a PPP link.
These counters provide the average or maximum forward/backward bandwidth allocated to a
PPP link in a measurement period. The forward direction indicates the TX direction and the
backward direction indicates the RX direction. The average forward or backward bandwidth
allocated to a PPP link can reflect the traffic volume in a measurement period. The maximum
forward or backward bandwidth allocated to a PPP link can reflect the maximum traffic volume
in a measurement period.
Measurement point
allocated to a PPP link every 15s. At the end of the measurement period, the system divides the
accumulated value by the sampling times to obtain the average value and uses the maximum
Formula
None
Unit
bit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PPP.Alloced.Ave.Fwd
WRFD-050402
on Iub Interface
VS.PPP.Alloced.Ave.Bwd
WRFD-050402
on Iub Interface
VS.PPP.Alloced.Max.Fwd
WRFD-050402
on Iub Interface
VS.PPP.Alloced.Max.Bwd
WRFD-050402
on Iub Interface

4054
BSC6900 UMTS
Measurement of the Number of Congestions on a PPP Link

Counters
Counter ID
Counter Name
Counter Description
67193247
VS.PPP.Fwd.Cong
congestions on a PPP link
67193249
VS.PPP.Bwd.Cong
congestions on a PPP link
Description
congestion remaining threshold configured for a PPP link, traffic on the PPP link is congested.
Users can configure the congestion remaining threshold according to the actual requirements.
If the congestion remaining threshold is set to 0, congestion does not occur. These counters
provide the number of forward or backward congestions on a PPP link in a measurement period.
The forward direction indicates the TX direction and the backward direction indicates the RX
direction. These counters can be used together with the duration of congestion on a PPP link to
observe the congestion. If traffic on many PPP links is congested for a long time, services are
affected.
Measurement point
In a measurement period, this counter is incremented by one each time congestion occurs on a
PPP link, that is, the remaining available bandwidth is less than the congestion remaining
threshold.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PPP.Fwd.Cong
WRFD-050402
on Iub Interface
VS.PPP.Bwd.Cong
WRFD-050402
on Iub Interface

4055
BSC6900 UMTS
Measurement of the Duration of Congestion on a PPP Link

Counters
Counter ID
Counter Name
Counter Description
67193248
VS.PPP.Fwd.Cong.Dur
congestion on a PPP link
67193250
VS.PPP.Bwd.Cong.Dur
congestion on a PPP link
Description
congestion remaining threshold configured for a PPP link, traffic on the PPP link is congested.
provide the duration of congestions on a PPP link in a measurement period. The forward direction
indicates the TX direction and the backward direction indicates the RX direction. These counters
can be used together with the number of congestions on a PPP link to observe the congestion.
If traffic on many PPP links is congested for a long time, services are affected.
Measurement point
on a PPP link. The measurement stops when the congestion relieves. At the end of the
measurement period, the system uses the accumulated value as the values of these counters.
Formula
None
Unit
s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.PPP.Fwd.Cong.Dur
WRFD-050402
on Iub Interface
VS.PPP.Bwd.Cong.Dur
WRFD-050402
on Iub Interface

4056
BSC6900 UMTS
2.43 Measurement of PPP Link Queue Performance

(PPP_QUEUE)
Overview
One PPP link can be categorized into multiple scheduling queues according to packet priorities.
Measurement of PPP Link Queue Performance indicates the transmission quality of a PPP link
queue on the PEUa, PEUc, UOIa or POUc board.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
PPP.QUEUE
PPP Link Queue Measurement
2.43.1 PPP Link Queue Measurement(PPP.QUEUE)

Overview
PPP links are important resources of the Base Station Controller. The transmission quality of
PPP links affects the availability of system functions. This function subset takes effect after a
PPP link is added. One PPP message enters one of six services data queues separately by
Differentiated Service Code Point (DSCP). That is, the services of different types can be
transmitted through different queues according to certain rules, and the PPP link schedules the
data in different queues according to priorities. You can run the following commands to query
the correspondence between service types and queues:
DSCP.
3. You can run the LST PHBMAP command to query the correspondence between DSCP and
queues.
PPP link queues belong to the data link layer.
Issue 03 (2015-06-30)

4057
BSC6900 UMTS
In the configuration structure, PPP links are between physical ports and logical applications, as
Figure 2-63 Physical bearer of the PPP Link Queue
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67195192
VS.PPP.QUEUE.T
XPACKETS
T7381:Number of
Packets Transmitted
in a PPP Link Queue
Earlier than
BSC6900
V900R011

4058
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67195193
VS.PPP.QUEUE.T
XBYTES
T7382:Number of
Bytes Transmitted in
a PPP Link Queue
Earlier than
BSC6900
V900R011
67195194
VS.PPP.QUEUE.T
XDROPPACKETS
T7383:Number of
Transmission on a
PPP Link Queue
Earlier than
BSC6900
V900R011
67195195
VS.PPP.QUEUE.T
XDROPBYTES
T7384:Number of
Bytes Discarded in
Transmission on a
PPP Link Queue
Earlier than
BSC6900
V900R011
67204582
VS.PPP.QUEUE.P
EAK.TXRATE
T7386:Maximum
Transmit Rate of a
PPP Link Queue
Earlier than
BSC6900
V900R011
67204583
VS.PPP.QUEUE.M
EAN.TX
T7387:Average
Transmit Rate of a
PPP Link Queue
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of Packets Transmitted in a PPP Link Queue or

Discarded in the Transmitting Direction of a PPP Link Queue
Counters
Counter ID
Counter Name
Counter Description
67195192
VS.PPP.QUEUE.TXPACKETS
Transmitted in a PPP Link
Queue
67195194
VS.PPP.QUEUE.TXDROPPACKETS
on a PPP Link Queue
Description
These counters provide the number of frames transmitted in a PPP link queue and the number
of frames discarded in the transmitting direction of the PPP link queue. The frames measured
here are PPP frames.
Issue 03 (2015-06-30)

4059
BSC6900 UMTS
Measurement point
the number of frames transmitted or discarded on the link once every five seconds and obtains
the total number of frames in one measurement period.
Formula
None
Unit
frame
Related Features
Counter Name
Feature ID
Feature Name
VS.PPP.QUEUE.TXPACKETS
WRFD-050402
on Iub Interface
VS.PPP.QUEUE.TXDROPPACKETS
WRFD-050402
on Iub Interface
Counters Related to the Number of Bytes Transmitted in a PPP Link Queue or

Discarded in the Transmitting Direction of a PPP Link Queue
Counters
Counter ID
Counter Name
Counter Description
67195193
VS.PPP.QUEUE.TXBYTE
S
Transmitted in a PPP Link
Queue
67195195
VS.PPP.QUEUE.TXDROPBYTES
on a PPP Link Queue
Description
These counters provide the number of bytes transmitted in a PPP link queue and the number of
bytes discarded in the transmitting direction of the PPP link queue.
Measurement point
the total number of bytes in one measurement period.
Issue 03 (2015-06-30)

4060
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.PPP.QUEUE.TXBYTE
S
WRFD-050402
on Iub Interface
VS.PPP.QUEUE.TXDROPBYTES
WRFD-050402
on Iub Interface
Counters Related to the Transmit Rate of a PPP Link Queue

Counters
Counter ID
Counter Name
Counter Description
67204582
VS.PPP.QUEUE.PEAK.TX
RATE
Rate of a PPP Link Queue
67204583
VS.PPP.QUEUE.MEAN.T
X
Rate of a PPP Link Queue
Description
These counters provide the transmit rate of a PPP link queue in the specified measurement period.
The rates measured here include the spending of the header and the payload of the PPP frame.
Measurement point
the number of bytes transmitted on the link once every five seconds. With this, the system obtains
the maximum number of bytes transmitted in five seconds, and the total number of one
measurement period. The maximum speed is calculated with the maximum bytes in five seconds,
and the average speed is calculated with the total bytes in one measurement period.
Formula
None
Issue 03 (2015-06-30)

4061
BSC6900 UMTS
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.PPP.QUEUE.PEAK.TX
RATE
WRFD-050402
on Iub Interface
VS.PPP.QUEUE.MEAN.T
X
WRFD-050402
on Iub Interface
2.44 Measurement of SAAL Link Performance(SAAL_LNK)

Overview
Measurement of SAAL Link Performance provides measurement on the SAAL links. The
counters for the measurement object can be used in ATM networking mode.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
SAAL.LNK
SAAL Link Measurement
2.44.1 SAAL Link Measurement(SAAL.LNK)

Overview
SAAL Link Measurement provides measurement on SAAL links. SAAL links provide pointto-point reliable signaling message transmission function for the base station controller.
Signaling messages from the base station controller to the NodeB, CN, or neighboring base
station controller are transmitted over SAAL links. SAAL links from the base station controller
to the NodeB are UNI links and SAAL links from the base station controller to the CN or
neighboring base station controller is NNI links.
Issue 03 (2015-06-30)

4062
BSC6900 UMTS
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67182593
VS.SAAL.LnkServ
Dur.Time
In-Service Duration
of SAAL Link
Earlier than
BSC6900
V900R011
67182594
VS.SAAL.FailLnk.
AllReasons
Number of SAAL
Link Failures (All
Causes)
Earlier than
BSC6900
V900R011
67182595
VS.SAAL.FailLnk.
NoRspTimExp
Number of SAAL
Failures (Timer
Expires)
Earlier than
BSC6900
V900R011
67182596
VS.SAAL.FailLnk.
ExcesErr.Rat
Number of SAAL
Failures (Over-High
BER)
Earlier than
BSC6900
V900R011
67182597
VS.SAAL.FailLnk.
ExcesNoCred
Number of SAAL
Link Failures
(Congestion)
Earlier than
BSC6900
V900R011
67182598
VS.SAAL.FailLnk.
AlignFail
Number of SAAL
Link Alignment
Failures
Earlier than
BSC6900
V900R011
67182599
VS.SAAL.LnkErr.
SDRetransTx
Number of SAAL
Link MAA-ERROR
Indications
(SDLOSS_TX)
Earlier than
BSC6900
V900R011
67182600
VS.SAAL.LnkErr.
PDUInval
Number of SAAL
Link MAA-ERROR
Indications (Invalid
PDU)
Earlier than
BSC6900
V900R011
67182601
VS.SAAL.LnkErr.
OthReasons
Number of SAAL
Link MAA-ERROR
Indications (Others)
Earlier than
BSC6900
V900R011
67182602
VS.SAAL.LnkErr.
RetransFail
Number of SAAL
Link MAA-ERROR
Indications Received
(Unsuccessful
Retransmission)
Earlier than
BSC6900
V900R011
67190615
VS.AAL5.SAALLn
k.BytesRx
Number of Bytes
Received by SAAL
Link
Earlier than
BSC6900
V900R011

4063
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67190616
VS.AAL5.SAALLn
k.BytesTx
Number of Bytes
Sent by SAAL Link
Earlier than
BSC6900
V900R011
67196153
VS.SAAL.LnkErr.
BufferLoss
Number of Packets
Discarded by SAAL
Link Due to Buffer
Congestion
Earlier than
BSC6900
V900R011
73421684
VS.SAAL.LnkErr.
SDRetransRx
Number of SAAL
Link MAA-ERROR
Indications
(SDLOSS_RX)
BSC6900
V900R012
None
In-Service Duration of SAAL Link

Counters
Counter ID
Counter Name
Counter Description
67182593
VS.SAAL.LnkServDur.Tim
e
In-Service Duration of
SAAL Link
Description
This counter provides the service duration of an SAAL link in a specified measurement period.
If the counter value is less than the specified measurement period, the link is faulty and services
are affected.
Measurement point
In a measurement period, the measurement starts when an SAAL link changes from the
unavailable state to the available state. The measurement stops when the SAAL link changes
from the available state to the unavailable state. At the end of the measurement period, the system
accumulates the service duration and restarts the measurement.
Formula
None
Issue 03 (2015-06-30)

4064
BSC6900 UMTS
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.LnkServDur.Tim
e
WRFD-05030105
Permanent AAL5
Plane Traffic
Counter ID
Counter Name
Counter Description
67182594
VS.SAAL.FailLnk.AllReasons
Number of SAAL Link

Failures (All Causes)
Number of SAAL Link Failures

Counters
Description
This counter provides the number of SAAL link failures. The failures include the SAAL
disconnection due to various causes and the location failure in the link setup process.
Measurement point
In a measurement period, the counter is incremented by one each time the SAAL link changes
from "In Service" state to "Out of Service" state or when the SAAL link location fails.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SAAL.FailLnk.AllReasons
WRFD-05030105
Permanent AAL5
Plane Traffic

4065
BSC6900 UMTS
Number of Link Failures Due to No Response of SAAL Link

Counters
Counter ID
Counter Name
Counter Description
67182595
VS.SAAL.FailLnk.NoRspTimExp
Number of SAAL Failures

(Timer Expires)
Description
This counter provides the number of SAAL link failures due to no peer end response.
Measurement point
As shown in Figure 1, the base station controller sends the POLL message to the peer end but
does not receive the state report (STAT) from the peer end. As a result, the local TimerNo_Response expires and this counter is incremented by one.
Figure 2-64 SAAL link procedure failure due to no response from the peer end (taking the Iu
interface as an example)
Formula
None
Issue 03 (2015-06-30)

4066
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.FailLnk.NoRspTimExp
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of SAAL Link Failures Due to Excessive Errors

Counters
Counter ID
Counter Name
Counter Description
67182596
VS.SAAL.FailLnk.ExcesErr
.Rat
Number of SAAL Failures

(Over-High BER)
Description
This counter provides the number of SAAL link failures due to a too high bit error rate (BER).
If the BER is too high, the number of packet retransmissions due to packet loss is too large. This
counter is measured only for NNI SAAL links.
Measurement point
In a measurement period, excessive packets are retransmitted over SAAL links due to packet
loss. This counter is incremented by one each time the SAAL management module releases an
SAAL link.
Formula
None
Unit
None
Issue 03 (2015-06-30)

4067
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.FailLnk.ExcesErr
.Rat
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of SAAL Link Failures Due to No Credit

Counters
Counter ID
Counter Name
Counter Description
67182597
VS.SAAL.FailLnk.ExcesNoCred
Number of SAAL Link

Failures (Congestion)
Description
This counter provides the number of SAAL link failures due to no credit for a long time. This
counter measures the NNI SAAL link only. The SAAL link flow control is implemented through
sliding window. The credit refers to the size of the sliding window, which indicates the data
transmit capacity of the local end.
Measurement point
In a measurement period, this counter is incremented by one each time Timer-No_Credit expires.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SAAL.FailLnk.ExcesNoCred
WRFD-05030105
Permanent AAL5
Plane Traffic

4068
BSC6900 UMTS
Number of SAAL Link Location Failures

Counters
Counter ID
Counter Name
Counter Description
67182598
VS.SAAL.FailLnk.AlignFail
Number of SAAL Link

Alignment Failures
Description
This counter provides the number of SAAL link location failures. This counter is measured only
for NNI SAAL links.
Measurement point
In a measurement period, this counter is incremented by one each time the location of the NNI
SAAL link fails during the link re-establishment process.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.FailLnk.AlignFail
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of Retransmissions of the downlink Lost Packet on the SAAL Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67182599
VS.SAAL.LnkErr.SDRetransTx
Number of SAAL Link

MAA-ERROR Indications
(SDLOSS_TX)

4069
BSC6900 UMTS
Description
This counter provides the number of retransmissions of the downlink packet loss on an SAAL
link. The SAAL link provides the reliable signaling transmission for the upper layer. When a
packet is lost on the SAAL link, the SAAL link retransmits the lost packet. This counter provides
the number of retransmissions of the lost packet on the SAAL link. Services may be affected if
many downlink packets are lost and retransmitted on multiple SAAL links.
Measurement point
In a measurement period, this counter is incremented by one each time the SAAL link receives
a USTAT or STAT message indicating the request for packet retransmission.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.LnkErr.SDRetransTx
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of Unexpected PDUs Received by SAAL Link

Counters
Counter ID
Counter Name
Counter Description
67182600
VS.SAAL.LnkErr.PDUInval
Number of SAAL Link

(Invalid PDU)
Description
This counter provides the number of unexpected protocol data units (PDUs) received over an
SAAL link, that is, the number of error PDUs with error codes A to M received by the SAAL
link. For details about the SAAL error codes, see TABLE A.1/Q.2110.
Issue 03 (2015-06-30)

4070
BSC6900 UMTS
Measurement point
the unexpected PDU.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.LnkErr.PDUInval
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of Errors of Other Types on SAAL Link

Counters
Counter ID
Counter Name
Counter Description
67182601
VS.SAAL.LnkErr.OthReasons
Number of SAAL Link

(Others)
Description
This counter provides the number of PDUs with error codes Q, R, S, or T received by an SAAL
link. For details about the SAAL error codes, see TABLE A.1/Q.2110.
Measurement point
the error PDU with error codes of Q, R, S, or T.
Formula
None
Unit
None
Issue 03 (2015-06-30)

4071
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.LnkErr.OthReasons
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of Retransmission Failures of Connection Control Message on SAAL Link

Counters
Counter ID
Counter Name
Counter Description
67182602
VS.SAAL.LnkErr.RetransFail
Number of SAAL Link

Received (Unsuccessful
Retransmission)
Description
This counter provides the number of retransmission failures of the connection control messages
(including BGN, END, RS, and ER) over an SAAL link. For example, if the peer end response
cannot be received after the BGN message is sent for certain repeated times during the SAAL
link establishment process, it indicates that the retransmission fails.
Measurement point
In a measurement period, after the SAAL link sends the connection control message (including
BGN, END, RS, and ER), if the peer end response message is not received, the TIMER_CC
expires and the connection control message is resent. This counter is incremented by one each
time the response message is not received after several transmissions (pre-specified number of
transmissions).
Formula
None
Unit
None
Issue 03 (2015-06-30)

4072
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.LnkErr.RetransFail
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of Bytes Received by SAAL Link

Counters
Counter ID
Counter Name
Counter Description
67190615
VS.AAL5.SAALLnk.Bytes
Rx

by SAAL Link
Description
This counter provides the number of bytes received by an SAAL link and reflects changes in
the receive traffic over the link.
Measurement point
In a measurement period, this counter is measured when an SAAL link receives data from AAL5.
Formula
None
Unit
byte
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Rx
WRFD-05030105
Permanent AAL5
Plane Traffic

4073
BSC6900 UMTS
Number of Bytes Sent by SAAL Link

Counters
Counter ID
Counter Name
Counter Description
67190616
Tx
Number of Bytes Sent by

SAAL Link
Description
This counter provides the number of bytes sent by an SAAL link and reflects changes in the
transmit traffic over the link.
Measurement point
In a measurement period, this counter is measured when an SAAL link sends data to AAL5.
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
Tx
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of Packets Discarded by SAAL Link Due to Buffer Congestion

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67196153
VS.SAAL.LnkErr.BufferLoss
Number of Packets
Discarded by SAAL Link
Due to Buffer Congestion

4074
BSC6900 UMTS
Description
This counter provides the number of packets discarded by an SAAL link due to a full send buffer.
Services are affected if packets are discarded on multiple SAAL links due to a full send buffer.
Measurement point
In a measurement period, this counter is measured when the send buffer is full and the SAAL
link sends data.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.LnkErr.BufferLoss
WRFD-05030105
Permanent AAL5
Plane Traffic
Number of Retransmissions of the uplink Lost Packet on the SAAL Link

Counters
Counter ID
Counter Name
Counter Description
73421684
VS.SAAL.LnkErr.SDRetransRx
Number of SAAL Link

(SDLOSS_RX)
Description
This counter provides the number of uplink packet retransmissions over an SAAL link due to
packet loss. The SAAL link provides the reliable signaling transmission for the upper layer.
When a packet is lost on the SAAL link, the SAAL link retransmits the lost packet. If a large
number of packets are retransmitted over multiple SAAL links, services may be affected.
Measurement point
In a measurement period, this counter is incremented by one each time the SAAL link sends the
USTAT or STAT message, indicating that certain packets need to be retransmitted.
Issue 03 (2015-06-30)

4075
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.LnkErr.SDRetransRx
WRFD-05030105
Permanent AAL5
Plane Traffic
2.45 Measurement of SAAL Link ATM Layer Performance

(SAALLNK_PVCLAYER)
Overview
SAAL means Signaling ATM Adaptation Layer link. SAAL carry signaling links and ensures
the reliability of transmission of Permanent Virtual Circuits (PVCs) between network elements
(NEs). Measurement of SAAL Link ATM Layer Performance indicates the transmission quality
of an SAAL PVC link on the AEUa, UOIa, AOUa, UOIc or AOUc board.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
SAALLNK.PVCLAYER
SAAL link ATM Layer Measurement
2.45.1 SAAL link ATM Layer Measurement

(SAALLNK.PVCLAYER)
Overview
The quality of transmission links directly affects the system performance. The SAAL link ATM
Layer measurement helps analyze system transmission quality so as to maintain system stability
and reliability. This function subset takes effect after a SAAL link is added.
Issue 03 (2015-06-30)

4076
BSC6900 UMTS
The position of SAAL links in the configuration structure is in figure 2.
Issue 03 (2015-06-30)

4077
BSC6900 UMTS
Figure 2-66 Physical bearer of the SAAL Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194771
VS.SAALLNK.PV
CLAYER.TXBYT
ES
Number of Bytes
Transmitted on an
SAAL Link ATM
Layer
Earlier than
BSC6900
V900R011
67204473
VS.SAALLNK.PV
CLAYER.PEAK.T
XRATE
Maximum Transmit
Rate of SAAL Link
ATM Layer
Earlier than
BSC6900
V900R011
67194773
VS.SAALLNK.PV
CLAYER.RXBYT
ES
Number of Bytes
Received on an
SAAL Link ATM
Layer
Earlier than
BSC6900
V900R011
67204474
VS.SAALLNK.PV
CLAYER.PEAK.R
XRATE
Maximum Receive
Rate of an SAAL
Link ATM Layer
Earlier than
BSC6900
V900R011

4078
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194775
VS.SAALLNK.PV
CLAYER.RXCOR
RECTPKTS
Number of Correct
Packets Received on
an SAAL Link ATM
Layer
Earlier than
BSC6900
V900R011
67194776
VS.SAALLNK.PV
CLAYER.TXCORRECTPKTS
Number of Correct
Packets Transmitted
on an SAAL Link
ATM Layer
Earlier than
BSC6900
V900R011
67194777
VS.SAALLNK.PV
CLAYER.DROPFORCNTERRCEL
LS
Number of Cells
Discarded on an
SAAL Link ATM
Layer Due to
Incorrect content
Earlier than
BSC6900
V900R011
67194778
VS.SAALLNK.PV
CLAYER.DROPF
ORLENERRCELL
S
Number of Cells
Discarded on an
SAAL Link ATM
Layer Due to
Incorrect Packet
length
Earlier than
BSC6900
V900R011
67194779
VS.SAALLNK.PV
CLAYER.RXBYT
ESOFAAL5CPSP
KTS
Number of Bytes in
Correct AAL2 CPS
Packets Received on
an SAAL Link ATM
Layer
Earlier than
BSC6900
V900R011
67194780
VS.SAALLNK.PV
CLAYER.TXBYT
ESOFAAL5CPSP
KTS
Number of Bytes in
Correct AAL2 CPS
Packets Transmitted
on an SAAL Link
ATM Layer
Earlier than
BSC6900
V900R011
67194781
VS.SAALLNK.PV
CLAYER.RXOVE
RFLOWDROPPE
DCELLS
Number of Cells
Discarded on an
SAAL Link ATM
Layer Due to the
Overflow of the
Receiving Buffer
Earlier than
BSC6900
V900R011
67194782
VS.SAALLNK.PV
CLAYER.TXOVE
RFLOWDROPPE
DCELLS
Number of Cells
Discarded on an
SAAL Link ATM
Layer Due to the
Overflow of the
Transmitting Buffer
Earlier than
BSC6900
V900R011

4079
BSC6900 UMTS
None
Counters Related to the Number of Bytes Received or Transmitted on an SAAL

link ATM Layer
Counters
Counter ID
Counter Name
Counter Description
67194773
VS.SAALLNK.PVCLAYE
R.RXBYTES

on an SAAL Link ATM
Layer
67194771
VS.SAALLNK.PVCLAYE
R.TXBYTES
Number of Bytes
Transmitted on an SAAL
Link ATM Layer
67194779
VS.SAALLNK.PVCLAYE
R.RXBYTESOFAAL5CPS
PKTS
Number of Bytes in Correct

AAL2 CPS Packets Received
on an SAAL Link ATM
Layer
67194780
VS.SAALLNK.PVCLAYE
R.TXBYTESOFAAL5CPS
PKTS
Number of Bytes in Correct

AAL2 CPS Packets
Link ATM Layer
Description
These counters provide the number of bytes received or transmitted on an SAAL link ATM
Layer in the specified measurement period.
Measurement point
total number of bytes in one measurement period.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

4080
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SAALLNK.PVCLAYE
R.RXBYTES
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.SAALLNK.PVCLAYE
R.TXBYTES
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.SAALLNK.PVCLAYE
R.RXBYTESOFAAL5CPS
PKTS
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.SAALLNK.PVCLAYE
R.TXBYTESOFAAL5CPS
PKTS
WRFD-05030105
Permanent AAL5
Plane Traffic
Counters Related to the Maximum Receive Rate or Maximum Transmit Rate of an

SAAL link ATM Layer
Counters
Counter ID
Counter Name
Counter Description
67204474
VS.SAALLNK.PVCLAYE
R.PEAK.RXRATE

an SAAL Link ATM Layer
67204473
VS.SAALLNK.PVCLAYE
R.PEAK.TXRATE

SAAL Link ATM Layer
Description
These counters provide the maximum receive rate or the maximum transmit rate of an SAAL
link ATM Layer in the specified measurement period.
Measurement point
system obtains the maximum number of bytes received or transmitted in five seconds. The
Formula
None
Issue 03 (2015-06-30)

4081
BSC6900 UMTS
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.SAALLNK.PVCLAYE
R.PEAK.RXRATE
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.SAALLNK.PVCLAYE
R.PEAK.TXRATE
WRFD-05030105
Permanent AAL5
Plane Traffic
Counters Related to the Number of Correct Packets Received or Transmitted on an

SAAL link ATM Layer
Counters
Counter ID
Counter Name
Counter Description
67194775
VS.SAALLNK.PVCLAYE
R.RXCORRECTPKTS
Number of Correct Packets

Received on an SAAL Link
ATM Layer
67194776
VS.SAALLNK.PVCLAYE
R.TXCORRECTPKTS
Number of Correct Packets

Link ATM Layer
Description
These counters provide the number of correct packets received or transmitted on an SAAL link
ATM Layer in the specified measurement period.
Measurement point
the number of packets transmitted or received on the link once every five seconds and obtains
Formula
None
Unit
packet
Issue 03 (2015-06-30)

4082
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SAALLNK.PVCLAYE
R.RXCORRECTPKTS
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.SAALLNK.PVCLAYE
R.TXCORRECTPKTS
WRFD-05030105
Permanent AAL5
Plane Traffic
Counters Related to the Number of Cells Discarded on an SAAL link ATM Layer
Counters
Counter ID
Counter Name
Counter Description
67194777
VS.SAALLNK.PVCLAYE
R.DROPFORCNTERRCELLS

on an SAAL Link ATM
Layer Due to Incorrect
content
67194778
VS.SAALLNK.PVCLAYE
R.DROPFORLENERRCELLS

on an SAAL Link ATM
Layer Due to Incorrect
Packet length
67194781
VS.SAALLNK.PVCLAYE
R.RXOVERFLOWDROPPEDCELLS

on an SAAL Link ATM
Layer Due to the Overflow of
the Receiving Buffer
67194782
VS.SAALLNK.PVCLAYE
R.TXOVERFLOWDROPPEDCELLS

on an SAAL Link ATM
Layer Due to the Overflow of
the Transmitting Buffer
Description
These counters provide the number of cells discarded on an SAAL link ATM Layer in the
specified measurement period.
Measurement point
the number of IEs discarded on the link once every five seconds and obtains the total number
Issue 03 (2015-06-30)

4083
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SAALLNK.PVCLAYE
R.DROPFORCNTERRCELLS
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.SAALLNK.PVCLAYE
R.DROPFORLENERRCELLS
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.SAALLNK.PVCLAYE
R.RXOVERFLOWDROPPEDCELLS
WRFD-05030105
Permanent AAL5
Plane Traffic
VS.SAALLNK.PVCLAYE
R.TXOVERFLOWDROPPEDCELLS
WRFD-05030105
Permanent AAL5
Plane Traffic
2.46 Measurement of SAAL VCL PM Performance

(SAALLNK_VCLPM)
Overview
Measurement of SAAL VCL PM Performance provides the statistics of PM on the ATM layer
of the SAAL link for the AOUc and UOIc boards. The SAAL PM function uses forward
performance monitoring (FPM) and backward reporting (BR) cells to monitor the number of
transmitted and received cells at both ends of the ATM layer on the SAAL link. Before viewing
the SAAL PM result, run the ACT VCLPM command to activate the PM function on the SAAL
link.
Issue 03 (2015-06-30)

4084
BSC6900 UMTS
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
SAALLNK.VCLPM
SAAL Link VCL PM Measurement
2.46.1 SAAL Link VCL PM Measurement(SAALLNK.VCLPM)

Overview
This measurement uses FPM and BR cells to monitor the ATM transmission quality of a SAAL
link. In the source direction, FPM cells are sent periodically to indicate the number of transmitted
cells and the number of error cells that failed the Bit Interleaved Parity 16 (BIP16) check. In the
sink direction, BR cells are transmitted as response to the FPM cells. The BR cells calculate the
number of received cells and the number of error cells that fail the BIP16 check. In the source
direction, BR cells are used to calculate the number of discarded cells and the number of cells
that are inserted by mistake. In the sink direction, FPM cells are used to calculate the number
of discarded cells and the number of cells that are inserted by mistake.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441389
VS.SAAL.VCLPM.
RXCELL
Number of Received
VCL PM Cells on a
SAAL link
BSC6900
V900R014
73441390
VS.SAAL.VCLPM.
TXCELL
Number of
Transmitted VCL
PM Cells on a SAAL
link
BSC6900
V900R014
73441391
VS.SAAL.VCLPM.
PEAK.RXRATE
Maximum Receive
Rate of VCL PM on
a SAAL link
BSC6900
V900R014
73441392
VS.SAAL.VCLPM.
PEAK.TXRATE
Maximum Transmit
Rate of VCL PM on
a SAAL link
BSC6900
V900R014
73441393
VS.SAAL.VCLPM.
RX.MEAN.LOSTCELLRATE
Average VCL PM
the Receive
Direction of a SAAL
link
BSC6900
V900R014

4085
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73441397
VS.SAAL.VCLPM.
RX.PEAK.LOSTCELLRATE
Maximum VCL PM
the Receive
Direction of a SAAL
link
BSC6900
V900R014
73441394
VS.SAAL.VCLPM.
TX.MEAN.LOSTCELLRATE
Average VCL PM
the Transmit
Direction of a SAAL
link
BSC6900
V900R014
73441398
VS.SAAL.VCLPM.
TX.PEAK.LOSTCELLRATE
Maximum VCL PM
the Transmit
Direction of a SAAL
link
BSC6900
V900R014
73441395
VS.SAAL.VCLPM.
RX.MEAN.ERRIN
SERTCELLRATE
Average Rate of
VCL PM Cells in the
a SAAL link
BSC6900
V900R014
73441399
VS.SAAL.VCLPM.
RX.PEAK.ERRINSERTCELLRATE
Maximum Rate of
VCL PM Cells in the
a SAAL link
BSC6900
V900R014
73441396
VS.SAAL.VCLPM.
TX.MEAN.ERRIN
SERTCELLRATE
Average Rate of
VCL PM Cells in the
Transmit Direction
of a SAAL link
BSC6900
V900R014
73441400
VS.SAAL.VCLPM.
TX.PEAK.ERRINSERTCELLRATE
Maximum Rate of
VCL PM Cells in the
Transmit Direction
of a SAAL link
BSC6900
V900R014
73424515
VS.SAAL.VCLPM.
SOURCEBIP16CR
CERRCELL
Number of VCL PM
Error Cell Blocks
Failed the BIP16
Check in the Source
Direction of a SAAL
link
BSC6900
V900R014

4086
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73424516
VS.SAAL.VCLPM.
SINKBIP16CRCE
RRCELL
Number of VCL PM
Error Cell Blocks
Failed the BIP16
Check in the Sink
Direction of a SAAL
link
BSC6900
V900R014
None
Number of VCL PM Cells on a SAAL link

Counters
Counter ID
Counter Name
Counter Description
73441389
VS.SAAL.VCLPM.RXCEL
L

PM Cells on a SAAL link
73441390
VS.SAAL.VCLPM.TXCEL
L

PM Cells on a SAAL link
Description
These counters provide the number of end-to-end received and transmitted cells at the ATM
layer over an SAAL link and reflect the traffic over an SAAL link at the ATM layer. Only ATM
cells are calculated.
Measurement point
number of cells transmitted at the ATM layers along a SAAL link every 5 seconds and measures
the total number at the end of each measurement period.
Formula
None
Unit
None
Issue 03 (2015-06-30)

4087
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.VCLPM.RXCEL
L
WRFD-05030110
F5
VS.SAAL.VCLPM.TXCEL
L
WRFD-05030110
F5
Maximum Data Rate of VCL PM on a SAAL link

Counters
Counter ID
Counter Name
Counter Description
73441391
VS.SAAL.VCLPM.PEAK.
RXRATE

VCL PM on a SAAL link
73441392
VS.SAAL.VCLPM.PEAK.T
XRATE

VCL PM on a SAAL link
Description
These counters provide the end-to-end maximum receive and transmit rates on a SAAL link,
indicating the maximum load in the receive and transmit directions on a SAAL link.
Measurement point
number of cells received and transmitted at the ATM layer along a SAAL link every 5 seconds.
It compares and obtains the maximum number of received and transmitted cells per 5 seconds
within a measurement period and accordingly calculates the maximum receive and transmit
rates. The counters are in the unit of kbit/s, and are calculated with the following formula:
Maximum receive and transmit rates = Maximum number of received/transmitted cells x 53 x
8/5/1000.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

4088
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.VCLPM.PEAK.
RXRATE
WRFD-05030110
F5
VS.SAAL.VCLPM.PEAK.T
XRATE
WRFD-05030110
F5
VCL PM Cell Discard Rate on a SAAL link

Counters
Counter ID
Counter Name
Counter Description
73441393
VS.SAAL.VCLPM.RX.ME
AN.LOSTCELLRATE
Average VCL PM Cell

Direction of a SAAL link
73441397
VS.SAAL.VCLPM.RX.PE
AK.LOSTCELLRATE
Maximum VCL PM Cell

73441394
VS.SAAL.VCLPM.TX.ME
AN.LOSTCELLRATE
Average VCL PM Cell

73441398
VS.SAAL.VCLPM.TX.PEA
K.LOSTCELLRATE
Maximum VCL PM Cell

Description
These counters provide the average and maximum rates of cells that are discarded in the receive
and transmit directions on a SAAL link. They are used to monitor the end-to-end error rate of
transmission cells on a SAAL link.
Measurement point
and transmit directions at the ATM layers along a SAAL link and compares to obtain the
directions.
Issue 03 (2015-06-30)

4089
BSC6900 UMTS
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.SAAL.VCLPM.RX.ME
AN.LOSTCELLRATE
WRFD-05030110
F5
VS.SAAL.VCLPM.RX.PE
AK.LOSTCELLRATE
WRFD-05030110
F5
VS.SAAL.VCLPM.TX.ME
AN.LOSTCELLRATE
WRFD-05030110
F5
K.LOSTCELLRATE
WRFD-05030110
F5
Rate of Incorrectly Inserted VCL PM Cells on a SAAL link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73441395
VS.SAAL.VCLPM.RX.ME
AN.ERRINSERTCELLRATE

Receive Direction of a SAAL
link
73441399
VS.SAAL.VCLPM.RX.PE
AK.ERRINSERTCELLRATE
Maximum Rate of
73441396
VS.SAAL.VCLPM.TX.ME

Transmit Direction of a
SAAL link
73441400
K.ERRINSERTCELLRATE
Maximum Rate of

4090
BSC6900 UMTS
Description
These counters provide the average and maximum rates of cells that are incorrectly inserted in
the receive and transmit directions on a SAAL link. They are used to monitor the end-to-end
error rate of transmission cells on a SAAL link.
Measurement point
receive and transmit directions at the ATM layers along a SAAL link and compares to obtain
the maximum number. To obtain the maximum rates of incorrectly inserted cells in the receive
and transmit directions, in each direction, the RNC divides the maximum number of cells that
are incorrectly inserted within 5 seconds by the total number of cells measured in those directions
during the same period. To obtain the average rates of incorrectly inserted cells in the receive
and transmit directions, in each direction, the RNC divides the total number of incorrectly
period.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SAAL.VCLPM.RX.ME
WRFD-05030110
F5
VS.SAAL.VCLPM.RX.PE
AK.ERRINSERTCELLRATE
WRFD-05030110
F5
VS.SAAL.VCLPM.TX.ME
WRFD-05030110
F5
K.ERRINSERTCELLRATE
WRFD-05030110
F5

4091
BSC6900 UMTS
Number of Error VCL PM Cell Blocks Failed BIP16 Check on a SAAL link
Counters
Counter ID
Counter Name
Counter Description
73424515
VS.SAAL.VCLPM.SOURC
EBIP16CRCERRCELL

Check in the Source
73424516
VS.SAAL.VCLPM.SINKBI
P16CRCERRCELL

of a SAAL link
Description
and transmit directions on an SAAL link. They are used to monitor the end-to-end error rate of
transmission cells on a SAAL link.
Measurement point
ATM layer along a SAAL link every 5 seconds and calculates the total number at the end of
each measurement period. In each cell block measured for this counter, none of the cells is
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SAAL.VCLPM.SOURC
EBIP16CRCERRCELL
WRFD-05030110
F5
VS.SAAL.VCLPM.SINKBI
P16CRCERRCELL
WRFD-05030110
F5

4092
BSC6900 UMTS
2.47 Measurement of SCCP OSP Performance(SCCP)

Overview
Measurement of SCCP OSP Performance provides measurement on originating signaling points
(OSPs) and monitors the SCCP connection success rate. It reflects network actions of the peer
equipment.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
SCCP
SCCP OSP Measurement
2.47.1 SCCP OSP Measurement(SCCP)

Overview
SCCP OSP Measurement provides the counters related to the SCCP originating signaling point
(OSP). The SCCP provides connection-oriented and connectionless signaling transmission
functions for base station controllers. Therefore, SCCP measurement provides the counters
related to the number of connection-oriented and connectionless messages received or sent by
the SCCP. It also provides the counters related to the errors and failures handled by the SCCP.
For details about the SCCP function, see the protocol ITU-T Q.704.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67178881
OS.SCCP.Fail.Rel.
Cmp
T6201:Number of
SCCP Connection
Release Expiry
Earlier than
BSC6900
V900R011
67178882
OS.SCCP.TiarTimeout
T6202:Number of
SCCP Connection
Releases Due to
SCCP Inactivity Test
Timeout
Earlier than
BSC6900
V900R011
67178883
OS.SCCP.ProvInitRel
T6203:Number of
NSP-Initiated SCCP
Connection Releases
Received by SCCP
Earlier than
BSC6900
V900R011

4093
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67178884
OS.SCCP.SegmenFail
T6204:Number of
SCCP XUDT
segmentation
Failures
Earlier than
BSC6900
V900R011
67178885
VS.SCCP.Rx.RLS
D.SubsFail
T6205:Number of
Connection Release
(RLSD) Messages
Received by SCCP
with the Cause of
Subsystem Faults
Earlier than
BSC6900
V900R011
67178886
VS.SCCP.Rx.RLS
D.MtpFail
T6206:Number of
RLSD Messages
Received by SCCP
with the Cause of
MTP Faults
Earlier than
BSC6900
V900R011
67178887
VS.SCCP.Rx.RLS
D.Cong
T6207:Number of
RLSD Messages
Received by SCCP
with the Cause of
Network Congestion
Earlier than
BSC6900
V900R011
67178888
VS.SCCP.Rx.RLS
D.Other
T6208:Number of
RLSD Messages
Received by the
SCCP for Other
Abnormal Causes
except for Subsystem
Faults, MTP Faults,
and Network
Congestion
Earlier than
BSC6900
V900R011
67195059
VS.SCCP.RX.RLS
D.NORMAL
T6209:Number of
RLSD Messages
Received by the
SCCP for Normal
Causes
Earlier than
BSC6900
V900R011
67178890
VS.SCCP.Rx.XUD
TS.ErrorMsg
T6211:Number of
XUDTS Messages
Received by SCCP
with the Cause of
Transmission Error
Earlier than
BSC6900
V900R011

4094
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67178891
VS.SCCP.Rx.UDT
S.FragFail
T6212:Number of
UDTS and XUDTS
Messages Received
by SCCP with the
Cause of
Segmentation
Failure
Earlier than
BSC6900
V900R011
67190756
VS.SCCP.Rx.ErrPDU
T6214:Number of
ERROR PDU
Messages Received
by SCCP
Earlier than
BSC6900
V900R011
67190757
VS.SCCP.Tx.ErrPDU
T6215:Number of
ERROR PDU
Messages Sent by
SCCP
Earlier than
BSC6900
V900R011
67178896
OS.SCCP.RouteFai
l.DSP.Unavai
T6219:Number of
SCCP Routing
Failures (Destination
Signaling Point
Inaccessible)
Earlier than
BSC6900
V900R011
67178897
OS.SCCP.RouteFai
l.SSNFail
T6220:Number of
SCCP Routing
Failures (Subsystem
Faults)
Earlier than
BSC6900
V900R011
67178898
OS.SCCP.RouteFai
l.SSNUnequip
T6221:Number of
SCCP Routing
Failures (Subsystem
Uninstalled)
Earlier than
BSC6900
V900R011
67178899
OS.SCCP.RouteFai
l.Unkown
T6227:Number of
SCCP Routing
Failures (Unknown
Causes)
Earlier than
BSC6900
V900R011
67178833
OS.SCCP.Tx.UDT
S.Msg
T6228:Number of
UDTS Messages
Sent by the SCCP
Earlier than
BSC6900
V900R011
67178834
OS.SCCP.Rx.UDT
S.Msg
T6229:Number of
UDTS Messages
Received by the
SCCP
Earlier than
BSC6900
V900R011

4095
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67178835
OS.SCCP.HandleTotalMsg
T6230:Number of
Messages Handled
by the SCCP from
the Local or Remote
End
Earlier than
BSC6900
V900R011
67178836
OS.SCCP.HandleLocalSSNMsg
T6231:Number of
SCCP to the Local
Subsystem
Earlier than
BSC6900
V900R011
67178837
OS.SCCP.Tx.Msg.
0.1
T6232:Number of
Connectionless
Messages Sent by
SCCP
Earlier than
BSC6900
V900R011
67178838
OS.SCCP.Rx.Msg.
0.1
T6233:Number of
Connectionless
Messages Received
by SCCP
Earlier than
BSC6900
V900R011
67178840
OS.SCCP.Rx.Msg.
2
T6234:Number of
Class 2 Messages
Received by SCCP
Earlier than
BSC6900
V900R011
67178839
OS.SCCP.Tx.Msg.
2
T6235:Number of
Class 2 Messages
Sent by SCCP
Earlier than
BSC6900
V900R011
73403248
OS.SCCP.CR.Tx
T6236:Number of
CR Messages Sent
by SCCP
Earlier than
BSC6900
V900R011
73403249
OS.SCCP.CR.Rx
T6237:Number of
CR Messages
Received by SCCP
Earlier than
BSC6900
V900R011
73403250
OS.SCCP.CREF.T
x
T6238:Number of
CREF Messages
Sent by SCCP
Earlier than
BSC6900
V900R011
73403251
OS.SCCP.CREF.R
x
T6239:Number of
CREF Messages
Received by SCCP
Earlier than
BSC6900
V900R011
73415658
OS.SCCP.REJ.Remote
T6240:Ratio of the
CREF Messages
from the Peer SCCP
Earlier than
BSC6900
V900R011

4096
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73415659
OS.SCCP.REJ.Local
T6241:Ratio of the
CREF Messages
from the Local SCCP
Earlier than
BSC6900
V900R011
73403252
OS.SCCP.CC.Tx
T6242:Number of
CC Messages Sent
by SCCP
Earlier than
BSC6900
V900R011
73403253
OS.SCCP.CC.Rx
T6243:Number of
CC Messages
Received by SCCP
Earlier than
BSC6900
V900R011
73403254
OS.SCCP.RLSD.T
x
T6244:Number of
RLSD Messages
Sent by SCCP
Earlier than
BSC6900
V900R011
73403255
OS.SCCP.RLC.Tx
T6245:Number of
RLC Messages Sent
by SCCP
Earlier than
BSC6900
V900R011
73403256
OS.SCCP.RLC.RX
T6246:Number of
RLC Messages
Received by SCCP
Earlier than
BSC6900
V900R011
None
Number of SCCP Connection Release Expiry

Counters
Counter ID
Counter Name
Counter Description
67178881
OS.SCCP.Fail.Rel.Cmp
T6201:Number of SCCP
Connection Release Expiry
Description
After the SCCP sends the RLSD message to instruct the SCCP node to release the connection,
if the SCCP does not receive the RLC message within the specified period, the release expires
and the local SCCP automatically releases the connection. This counter provides the number of
automatic connection releases due to expiration.
Issue 03 (2015-06-30)

4097
BSC6900 UMTS
Measurement point
In a measurement period, the SCCP starts the release protection timer after sending the RLSD
message and stops the timer after receiving the RLC message from the peer end. This counter
is incremented by one each time the timer expires due to no RLC message received within the
specified period.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.Fail.Rel.Cmp
WRFD-010101

Specifications
Number of SCCP Connection Releases Due to SCCP Inactivity Test

Counters
Counter ID
Counter Name
Counter Description
67178882
OS.SCCP.TiarTimeout
Connection Releases Due to
SCCP Inactivity Test
Timeout
Description
This counter provides the number of connection releases due to the SCCP inactivity test. The
SCCP inactivity receive timer (TIAR) and the SCCP inactivity send timer (TIAS) start after the
SCCP connection establishment. The TIAS restarts each time the SCCP sends a connectionoriented message. If no connection-oriented message is sent until the TIAS expires, the SCCP
sends the inactivity test message (IT). The TIAR restarts each time the SCCP receives a
connection-oriented message. If no connection-oriented message is received until the TIAR
expires, the SCCP releases the connection.
Measurement point
In a measurement period, this counter is incremented by one each time the TIAR expires and
the SCCP sends the connection release message.
Issue 03 (2015-06-30)

4098
BSC6900 UMTS
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.TiarTimeout
WRFD-010101

Specifications
Number of NSP-initiated SCCP Connection Releases Received by SCCP

Counters
Counter ID
Counter Name
Counter Description
67178883
OS.SCCP.ProvInitRel
T6203:Number of NSPInitiated SCCP Connection

Releases Received by SCCP
Description
When services are released, the network service provider (NSP) initiates a request for releasing
SCCP connections. This counter provides the number of SCCP connection releases initiated by
the NSP.
Measurement point
In a measurement period, this counter is incremented by one each time the SCCP receives or
sends a connection release message (RLSD) with the cause of "NSP."
Formula
None
Unit
None
Issue 03 (2015-06-30)

4099
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.ProvInitRel
WRFD-010101

Specifications
Number of SCCP XUDT Segmentation Failures

Counters
Counter ID
Counter Name
Counter Description
67178884
OS.SCCP.SegmenFail
XUDT segmentation
Failures
Description
This counter provides the number of SCCP XUDT segmentation failures. For details, see the
protocol ITU-T Q.712.
Measurement point
In a measurement period, this counter is incremented by one each time the size of the
connectionless message from the upper layer exceeds the maximum capability (3360 bytes) or
the SCCP fails to request a segmentation reference number.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.SCCP.SegmenFail
WRFD-010101

Specifications

4100
BSC6900 UMTS
Number of RLSD Messages Received by the SCCP

Counters
Counter ID
Counter Name
Counter Description
67178885
VS.SCCP.Rx.RLSD.SubsFail
T6205:Number of
Connection Release (RLSD)
Messages Received by SCCP
with the Cause of Subsystem
Faults
67178886
VS.SCCP.Rx.RLSD.MtpFai
l
T6206:Number of RLSD
with the Cause of MTP Faults
67178887
VS.SCCP.Rx.RLSD.Cong
with the Cause of Network
Congestion
67178888
VS.SCCP.Rx.RLSD.Other
SCCP for Other Abnormal
Causes except for Subsystem
Faults, MTP Faults, and
Network Congestion
67195059
VS.SCCP.RX.RLSD.NORMAL
SCCP for Normal Causes
Description
These counters provide the number of RLSD messages received by the SCCP with different
causes. Services may be affected if multiple connections are abnormally released.
Issue 03 (2015-06-30)
Counter Name
Description
This counter provides the number of RLSD

messages received by the SCCP with the
cause of subsystem faults.
VS.SCCP.Rx.RLSD.MtpFail

cause of message transfer part (MTP) faults.

4101
BSC6900 UMTS
Counter Name
Description

cause of network congestion.

messages received by the SCCP for other
abnormal causes except for subsystem faults,
MTP faults, and network congestion.

messages for normal causes.
Measurement point
In a measurement period, these counters are incremented by one each time the SCCP receives
the RLSD messages with different causes.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
WRFD-010101

Specifications
VS.SCCP.Rx.RLSD.MtpFai
l
WRFD-010101

Specifications
WRFD-010101

Specifications
WRFD-010101

Specifications
WRFD-010101

Specifications

4102
BSC6900 UMTS
Number of XUDTS Messages Received by the SCCP with the Cause of

Transmission Error
Counters
Counter ID
Counter Name
Counter Description
67178890
VS.SCCP.Rx.XUDTS.ErrorMsg
T6211:Number of XUDTS
with the Cause of
Transmission Error
Description
This counter provides the number of XUDTS messages received by the SCCP with the cause of
transmission error. For details, see the protocol ITU-T Q.712.
Measurement point
In a measurement period, this counter is incremented by one each time the SCCP receives the
XUDTS messages with the cause of transmission error.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.SCCP.Rx.XUDTS.ErrorMsg
WRFD-010101

Specifications

4103
BSC6900 UMTS
Number of UDTS Messages Received by the SCCP with the Cause of Segmentation
Failure
Counters
Counter ID
Counter Name
Counter Description
67178891
VS.SCCP.Rx.UDTS.FragFail
T6212:Number of UDTS and

XUDTS Messages Received
by SCCP with the Cause of
Segmentation Failure
Description
This counter provides the number of UDTS messages received by the SCCP with the cause of
segmentation failure. For details, see the protocol ITU-T Q.712.
Measurement point
UDTS messages with the cause of segementation failure.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SCCP.Rx.UDTS.FragFail
WRFD-010101

Specifications
Number of ERROR PDU Messages Received by the SCCP

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67190756
VS.SCCP.Rx.ErrPDU
T6214:Number of ERROR
PDU Messages Received by
SCCP

4104
BSC6900 UMTS
Description
This counter provides the number of PDU error messages received by the SCCP. For details,
see the protocol ITU-T Q.712.
Measurement point
PDU error messages.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SCCP.Rx.ErrPDU
WRFD-010101

Specifications
Number of ERROR PDU Messages Sent by the SCCP

Counters
Counter ID
Counter Name
Counter Description
67190757
VS.SCCP.Tx.ErrPDU
T6215:Number of ERROR
PDU Messages Sent by
SCCP
Description
This counter provides the number of PDU error messages sent by the SCCP. For details, see the
protocol ITU-T Q.712.
Measurement point
In a measurement period, this counter is incremented by one each time the SCCP sends the PDU
error messages.
Formula
None
Issue 03 (2015-06-30)

4105
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SCCP.Tx.ErrPDU
WRFD-010101

Specifications
Counter ID
Counter Name
Counter Description
67178896
OS.SCCP.RouteFail.DSP.U
navai
Routing Failures
(Destination Signaling Point
Inaccessible)
67178897
OS.SCCP.RouteFail.SSNFai
l
Routing Failures (Subsystem
Faults)
67178898
OS.SCCP.RouteFail.SSNUnequip
Routing Failures (Subsystem
Uninstalled)
67178899
OS.SCCP.RouteFail.Unkown
Routing Failures (Unknown
Causes)
Number of SCCP Routing Failures

Counters
Description
These counters provide the number of routing failures for different causes. The routing failure
leads to the data transmission failure between the SCCP and the DSP, and services may be
affected.
Issue 03 (2015-06-30)
Counter Name
Description
OS.SCCP.RouteFail.DSP.Unavai
This counter provides the number of SCCP

routing failures because the destination
signaling point is not accessible or does not
exit.

4106
BSC6900 UMTS
Counter Name
Description
OS.SCCP.RouteFail.SSNFail

routing failures due to subsystem faults.

routing failures because the subsystem is not
installed.
This counter provides the SCCP routing

failures for the causes except "destination
signaling point failure, subsystem failure, and
subsystem uninstalled.
Measurement point
In a measurement period, these counters are incremented by one each time the SCCP routing
failure occurs due to various reasons.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.SCCP.RouteFail.DSP.U
navai
WRFD-010101

Specifications
OS.SCCP.RouteFail.SSNFai
l
WRFD-010101

Specifications
WRFD-010101

Specifications
WRFD-010101

Specifications

4107
BSC6900 UMTS
Counters Related to Number of Messages Sent by the SCCP

Counters
Counter ID
Counter Name
Counter Description
67178833
OS.SCCP.Tx.UDTS.Msg
T6228:Number of UDTS
Messages Sent by the SCCP
67178837
OS.SCCP.Tx.Msg.0.1
T6232:Number of
Connectionless Messages
Sent by SCCP
67178839
OS.SCCP.Tx.Msg.2
T6235:Number of Class 2
Messages Sent by SCCP
Description
These counters provide the number of messages sent by the SCCP.
Counter Name
Description
OS.SCCP.Tx.UDTS.Msg
This counter provides the number of unit data

service (UDTS) messages sent by the SCCP.
OS.SCCP.Tx.Msg.0.1
This counter provides the number of classes

0 and 1 messages sent by the SCCP, that is,
the number of connectionless messages sent
by the SCCP. SCCP connectionless messages
include the UDT, XUDT, LUDT, UDTS,
XUDTS, and LUDTS messages.
OS.SCCP.Tx.Msg.2
This counter provides the number of class 2

messages sent by the SCCP, that is, the
number of connection-oriented messages sent
by the SCCP. SCCP connection-oriented
messages include the CR, CC, CREF, RLSD,
RLC, DT1, and IT messages.
Measurement point
In a measurement period, these counters are incremented by one each time the SCCP sends the
preceding messages.
Formula
None
Issue 03 (2015-06-30)

4108
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.Tx.UDTS.Msg
WRFD-010101

Specifications
OS.SCCP.Tx.Msg.0.1
WRFD-010101

Specifications
OS.SCCP.Tx.Msg.2
WRFD-010101

Specifications
Counters Related to Number of Messages Received by the SCCP

Counters
Counter ID
Counter Name
Counter Description
67178834
OS.SCCP.Rx.UDTS.Msg
T6229:Number of UDTS
SCCP
67178838
OS.SCCP.Rx.Msg.0.1
T6233:Number of
Connectionless Messages
Received by SCCP
67178840
OS.SCCP.Rx.Msg.2
T6234:Number of Class 2
Description
These counters provide the number of messages received by the SCCP.
Issue 03 (2015-06-30)
Counter Name
Description
OS.SCCP.Rx.UDTS.Msg
This counter provides the number of UDTS

messages received by the SCCP.

4109
BSC6900 UMTS
Counter Name
Description
OS.SCCP.Rx.Msg.0.1
This counter provides the number of classes

0 and 1 messages received by the SCCP, that
is, the number of connectionless messages
received by the SCCP. SCCP connectionless
messages include the UDT, XUDT, LUDT,
UDTS, XUDTS, and LUDTS messages.
OS.SCCP.Rx.Msg.2
This counter provides the number of class 2

messages received by the SCCP, that is, the
number of connection-oriented messages
received by the SCCP. SCCP connectionoriented messages include the CR, CC,
CREF, RLSD, RLC, DT1, and IT messages.
Measurement point
In a measurement period, these counters are incremented by one each time the SCCP receives
the preceding messages.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.SCCP.Rx.UDTS.Msg
WRFD-010101

Specifications
OS.SCCP.Rx.Msg.0.1
WRFD-010101

Specifications
OS.SCCP.Rx.Msg.2
WRFD-010101

Specifications

4110
BSC6900 UMTS
Number of Messages Handled by the SCCP

Counters
Counter ID
Counter Name
Counter Description
67178835
Handled by the SCCP from
the Local or Remote End
Description
This counter provides the total number of local-end or remote-end messages handled by the
SCCP.
Measurement point
In a measurement period, this counter is incremented by one each time the SCCP sends or
receives a messages.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010101

Specifications
Number of Messages Sent by the SCCP to the Local Subsystem

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67178836
Sent by the SCCP to the
Local Subsystem

4111
BSC6900 UMTS
Description
This counter provides the number of messages that the SCCP sends to the local subsystem.
Measurement point
In a measurement period, this counter is incremented by one each time the SCCP sends a message
to the local subsystem.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
WRFD-010101

Specifications
Number of CR Messages Sent and Received by the SCCP

Counters
Counter ID
Counter Name
Counter Description
73403248
OS.SCCP.CR.Tx
T6236:Number of CR
73403249
OS.SCCP.CR.Rx
T6237:Number of CR
Description
These counters provide the number of CR messages sent and received by the SCCP.
Issue 03 (2015-06-30)
Counter Name
Description
OS.SCCP.CR.Tx
This counter provides the number of CR

messages sent by the SCCP.

4112
BSC6900 UMTS
Counter Name
Description
OS.SCCP.CR.Rx
This counter provides the number of CR

Measurement point
In the measurement period, these counters are incremented by one when the SCCP sends or
receives a CR message.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.CR.Tx
WRFD-010101

Specifications
OS.SCCP.CR.Rx
WRFD-010101

Specifications
Number of CREF Messages Sent and Received by the SCCP

Counters
Counter ID
Counter Name
Counter Description
73403250
OS.SCCP.CREF.Tx
T6238:Number of CREF
73403251
OS.SCCP.CREF.Rx
T6239:Number of CREF
Description
These counters provide the number of CREF messages sent and received by the SCCP.Services
will be affected if many Connection Refused (CREF) messages are sent or received by the SCCP
module.
Issue 03 (2015-06-30)

4113
BSC6900 UMTS
Counter Name
Description
OS.SCCP.CREF.Tx
This counter provides the number of CREF

OS.SCCP.CREF.Rx
This counter provides the number of CREF

Measurement point
receives a CREF message.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.CREF.Tx
WRFD-010101

Specifications
OS.SCCP.CREF.Rx
WRFD-010101

Specifications
Ratio of the CREF Messages from the Peer SCCP

Counters
Counter ID
Counter Name
Counter Description
73415658
OS.SCCP.REJ.Remote
T6240:Ratio of the CREF

Messages from the Peer
SCCP
Description
This counter provide the ratio of the CREF messages from the peer SCCP to the local
SCCP.Services will be affected if the SCCP rejection rate is high.
Issue 03 (2015-06-30)

4114
BSC6900 UMTS
Measurement point
At the end of the measurement period, this counter is calculated using the formula.
Formula
OS.SCCP.REJ.Remote = [Number of Received CREF Messages] *100/ [Number of Sent CR
Messages]
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.REJ.Remote
WRFD-010101

Specifications
Ratio of the CREF Messages from the Local SCCP

Counters
Counter ID
Counter Name
Counter Description
73415659
OS.SCCP.REJ.Local
T6241:Ratio of the CREF

Messages from the Local
SCCP
Description
This counter provide the ratio of the CREF messages from the local SCCP to the peer
SCCP.Services will be affected if many connection setup requests are rejected.
Measurement point
At the end of the measurement period, this counter is calculated using the formula.
Formula
OS.SCCP.REJ.Local = [Number of Sent CREF Messages] *100/ [Number of Received CR
Messages]
Unit
%
Issue 03 (2015-06-30)

4115
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.REJ.Local
WRFD-010101

Specifications
Number of CC Messages Sent and Received by the SCCP

Counters
Counter ID
Counter Name
Counter Description
73403252
OS.SCCP.CC.Tx
T6242:Number of CC
73403253
OS.SCCP.CC.Rx
T6243:Number of CC
Description
These counters provide the number of CC messages sent and received by the SCCP module.
Counter Name
Description
OS.SCCP.CC.Tx
This counter provides the number of CC

OS.SCCP.CC.Rx
This counter provides the number of CC

Measurement point
In a measurement period, these counters are incremented by one each time the SCCP module
sends or receives a CC message.
Formula
None
Unit
None
Issue 03 (2015-06-30)

4116
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
OS.SCCP.CC.Tx
WRFD-010101

Specifications
OS.SCCP.CC.Rx
WRFD-010101

Specifications
Number of RLSD Messages Sent by the SCCP

Counters
Counter ID
Counter Name
Counter Description
73403254
OS.SCCP.RLSD.Tx
Description
This counter provides the number of RLSD messages sent by the SCCP module.
Measurement point
In a measurement period, this counter is incremented by one each time the SCCP module sends
an RLSD message.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.SCCP.RLSD.Tx
WRFD-010101

Specifications

4117
BSC6900 UMTS
Number of RLC Messages Sent and Received by the SCCP

Counters
Counter ID
Counter Name
Counter Description
73403255
OS.SCCP.RLC.Tx
T6245:Number of RLC
73403256
OS.SCCP.RLC.RX
T6246:Number of RLC
Description
These counters provide the number of RLC messages sent and received by the SCCP module.
Counter Name
Description
OS.SCCP.RLC.Tx
This counter provides the number of RLC

OS.SCCP.RLC.RX
This counter provides the number of RLC

Measurement point
receives a RLC message.
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
OS.SCCP.RLC.Tx
WRFD-010101

Specifications
OS.SCCP.RLC.RX
WRFD-010101

Specifications

4118
BSC6900 UMTS
2.48 Measurement of SCTP Link Performance(SCTPLNK)

Overview
Measurement of SCTP Link Performance provides measurement on SCTP links and monitors
the network status.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
SCTPIP
SCTP IP Measurement
SCTPLNK
SCTP Link Measurement
2.48.1 SCTP IP Measurement(SCTPIP)

Overview
Based on the IP protocol, the SCTP link provides reliable point-to-point transmission of
signaling messages for the base station controller. SCTP IP Measurement provides the counters
related to the traffic on an SCTP IP link.
For details about the SCTP protocol, see the protocol RFC4960.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67191610
VS.SCTP.RX.BYT
ES
T6001:Number of IP
Bytes Received on
the SCTP Link
Earlier than
BSC6900
V900R011
67191611
VS.SCTP.TX.BYT
ES
T6002:Number of IP
the SCTP Link
Earlier than
BSC6900
V900R011
67191612
VS.SCTP.RX.PKG
NUM
T6003:Number of IP
Packets Received on
the SCTP Link
Earlier than
BSC6900
V900R011
67191613
VS.SCTP.TX.PKG
NUM
T6004:Number of IP
Packets Transmitted
on the SCTP Link
Earlier than
BSC6900
V900R011

4119
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67191614
VS.SCTP.RX.MAX
BYTES
T6005:Maximum
Number of IP Bytes
Received on the
SCTP Link
Earlier than
BSC6900
V900R011
67191615
VS.SCTP.TX.MAX
BYTES
T6006:Maximum
Number of IP Bytes
Transmitted on the
SCTP Link
Earlier than
BSC6900
V900R011
67192144
VS.SCTP.RETX.P
KGNUM
T6007:Number of
Packets Resent on
the SCTP Link
Earlier than
BSC6900
V900R011
67191616
VS.SCTP.RX.MAX
PKGNUM
T6008:Maximum
Number of IP
Packets Received on
the SCTP Link
Earlier than
BSC6900
V900R011
67191617
VS.SCTP.TX.MAX
PKGNUM
T6009:Maximum
Number of IP
Packets Transmitted
on the SCTP Link
Earlier than
BSC6900
V900R011
67184352
VS.SCTP.RX.ERR
PKGNUM
T6010:Number of
Error Packets
Received on SCTP
Link
Earlier than
BSC6900
V900R011
73423484
VS.SCTP.REQ.RE
TX.NUM
T6016:Number of
Retransmit Request
Sent on the SCTP
Link
BSC6900
V900R013
None
Counters Related to Number of Bytes That the SCTP Link Receives from or
Transmits to the IP Layer
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67191610
VS.SCTP.RX.BYTES
T6001:Number of IP Bytes
Received on the SCTP Link

4120
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67191611
VS.SCTP.TX.BYTES
T6002:Number of IP Bytes
Transmitted on the SCTP
Link
67191614
VS.SCTP.RX.MAXBYTES
T6005:Maximum Number of
IP Bytes Received on the
SCTP Link
67191615
VS.SCTP.TX.MAXBYTES
IP Bytes Transmitted on the
SCTP Link
Description
These counters provide the number of payload bytes of data packets that the SCTP link receives
from or transmits to the IP layer in a specified measurement period.
Counter Name
Description
VS.SCTP.RX.BYTES
This counter provides the number of payload

bytes of data packets that the SCTP link
receives from the IP layer
VS.SCTP.TX.BYTES
This counter provides the number of payload

bytes of data packets that the SCTP link
transmits to the IP layer
VS.SCTP.RX.MAXBYTES
This counter provides the maximum number

of payload bytes of data packets that the
SCTP link receives from the IP layer
VS.SCTP.TX.MAXBYTES

of payload bytes of data packets that the
SCTP link transmits to the IP layer
Measurement point
In a measurement period, the system automatically sampled the number of payload bytes sent
or received over an SCTP link from the IP layer every 5s. At the end of the measurement period,
the system divides the accumulated value by the sampling times to obtain the total number and
Formula
None
Issue 03 (2015-06-30)

4121
BSC6900 UMTS
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.SCTP.RX.BYTES
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.SCTP.TX.BYTES
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.SCTP.RX.MAXBYTES
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.SCTP.TX.MAXBYTES
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Counters Related to the Number of IP Packets Received or Transmitted on the

SCTP Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67191612
VS.SCTP.RX.PKGNUM
T6003:Number of IP Packets
Received on the SCTP Link

4122
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67191613
VS.SCTP.TX.PKGNUM
T6004:Number of IP Packets
Transmitted on the SCTP
Link
67191616
VS.SCTP.RX.MAXPKGNUM
IP Packets Received on the
SCTP Link
67191617
VS.SCTP.TX.MAXPKGNUM
IP Packets Transmitted on
the SCTP Link
Description
These counters provide the number of all packets that the SCTP link receives from or transmits
to the IP layer in a specified measurement period.
Counter Name
Description
VS.SCTP.RX.PKGNUM
This counter provides the number of all

packets that the SCTP link receives from the
IP layer
VS.SCTP.TX.PKGNUM
This counter provides the number of all

packets that the SCTP link transmits to the IP
layer

of all packets that the SCTP link receives
from the IP layer

of all packets that the SCTP link transmits to
the IP layer
Measurement point
In a measurement period, the system automatically sampled the number of payload bytes sent
or received over an SCTP link from the IP layer every 5s. At the end of the measurement period,
the system divides the accumulated value by the sampling times to obtain the total number and
Formula
None
Issue 03 (2015-06-30)

4123
BSC6900 UMTS
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.SCTP.RX.PKGNUM
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.SCTP.TX.PKGNUM
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Number of Packets Resent on the SCTP Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67192144
VS.SCTP.RETX.PKGNUM
Resent on the SCTP Link

4124
BSC6900 UMTS
Description
This counter provides the number of packets resent over an SCTP link in a specified measurement
period and monitors whether delay or packet loss occurs on the network from the TX direction.
Measurement point
In a measurement period, this counter is incremented by one each time the packet is resent over
an SCTP link.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.SCTP.RETX.PKGNUM
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Number of Error Packets Received on SCTP Link

Counters
Counter ID
Counter Name
Counter Description
67184352
VS.SCTP.RX.ERRPKGNUM
T6010:Number of Error
Packets Received on SCTP
Link
Description
All the packets transferred on the SCTP links are assembled from data blocks. Error packets will
occur with respect to network performance or upper-layer application. This counter provides the
number of error packets received over an SCTP link.
Issue 03 (2015-06-30)

4125
BSC6900 UMTS
Measurement point
In a measurement period, this counter is incremented by one each time the error packets are
received over an SCTP link.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
VS.SCTP.RX.ERRPKGNUM
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Number of Retransmit Request Sent on the SCTP Link

Counters
Counter ID
Counter Name
Counter Description
73423484
VS.SCTP.REQ.RETX.NU
M
T6016:Number of
Retransmit Request Sent on
the SCTP Link
Description
This counter provides the number of retransmission requests sent over an SCTP link in a
specified measurement period and monitors whether delay or packet loss occurs on the network
from the RX direction.
Measurement point
In a measurement period, this counter is incremented by one each time one SACK packet
containing Gap Ack Blocks is sent over an SCTP link.
Formula
None
Issue 03 (2015-06-30)

4126
BSC6900 UMTS
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SCTP.REQ.RETX.NU
M
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
2.48.2 SCTP Link Measurement(SCTPLNK)

Overview
SCTP link measurement provides the counters related to the number of in-service duration and
congestion duration of the SCTP link. It also provides the counters related to the number of data
packets sent and received on the SCTP link.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67191618
VS.SCTP.SERVIC
E.INTERVAL
T6011:Service
Duration of the
SCTP Link
Earlier than
BSC6900
V900R011
67191619
VS.SCTP.CONGE
STION.INTERVA
L
T6012:Congestion
Duration of the
SCTP Link
Earlier than
BSC6900
V900R011
73403174
UPUSER.SEND.M
SG.NUM
T6014:Number of
Packets Sent on the
SCTP Link
Earlier than
BSC6900
V900R011
73403175
UPUSER.RECEIV
E.MSG.NUM
T6015:Number of
Packets Received on
SCTP Link
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

4127
BSC6900 UMTS
Service Duration of the SCTP Link

Counters
Counter ID
Counter Name
Counter Description
67191618
VS.SCTP.SERVICE.INTERVAL
T6011:Service Duration of
the SCTP Link
Description
This counter provides the service duration of an SCTP link. If multiple SCTP links are faulty
for a long time, services are affected.
Measurement point
In a measurement period, the system samples the status of an SCTP link every 5s. this counter
is measured each time the link status is "Available." At the end of the measurement period, the
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.SCTP.SERVICE.INTERVAL
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

4128
BSC6900 UMTS
Congestion Duration of the SCTP Link

Counters
Counter ID
Counter Name
Counter Description
67191619
VS.SCTP.CONGESTION.I
NTERVAL
T6012:Congestion Duration
of the SCTP Link
Description
This counter provides the congestion duration of an SCTP link. If traffic on multiple SCTP links
is congested for a long time, services are affected.
Measurement point
In a measurement period, the system samples the status of an SCTP link every 5s. this counter
is measured each time the link status is "Congested", that is, the message sending queue usage
of the SCTP link exceeds the congestion threshold. At the end of the measurement period, the
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.SCTP.CONGESTION.I
NTERVAL
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

4129
BSC6900 UMTS
Number of Packets Sent on the SCTP Link

Counters
Counter ID
Counter Name
Counter Description
73403174
UPUSER.SEND.MSG.NU
M
Sent on the SCTP Link
Description
This counter provides the number of data blocks that the SCTP link transmits to the bottom layer
in a specified measurement period.
Measurement point
In a measurement period, the sum of data blocks transmitted to the bottom layer on an SCTP
link is measured as the value of this counter. A data block contains only user data.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
UPUSER.SEND.MSG.NU
M
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
Number of Packets Received on SCTP Link

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73403175
UPUSER.RECEIVE.MSG.
NUM
Received on SCTP Link

4130
BSC6900 UMTS
Description
This counter provides the number of data blocks that an SCTP link receives from the bottom
Measurement point
In a measurement period, the sum of data blocks received from the bottom layer on an SCTP
link is measured as the value of this counter. A data block contains only user data.
Formula
None
Unit
packet
Related Features
Counter Name
Feature ID
Feature Name
UPUSER.RECEIVE.MSG.
NUM
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
2.49 Measurement of SCTP Link IP Layer Performance

(SCTPLNK_IPLAYER)
Overview
SCTP is a reliable transmission protocol. It uses multi-homing and multi-streaming to provide
reliable and sequential data transmission services and can protect data information boundary.
Measurement of SCTP Link IP Layer Performance indicates the transmission quality of the IP
layer of an SCTP link on the FG2a, GOUa, PEUa, PEUc, UOIa, POUa, FG2c, GOUc, GOUe
and POUc board.Measurement of SCTP Link IP Layer Performance is not triggered if the SCTP
link type is INNER_SRAP. Compared with Measurement of SCTP Link Performance,
Measurement of SCTP Link IP Layer Performance includes measurement on IP packet headers.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
SCTPLNK.IPLAYER
SCTP Link IP Layer Measurement

4131
BSC6900 UMTS
2.49.1 SCTP Link IP Layer Measurement(SCTPLNK.IPLAYER)

Overview
The quality of transmission links directly affects the system performance. SCTP Link IP Layer
reliability. This function subset takes effect after an SCTP link is added.
Figure 1 shows the location of the IP Layer in the procotol.
Figure 2-68 Physical bearer of the logical port for the SCTP Link
Issue 03 (2015-06-30)

4132
BSC6900 UMTS
The position of SCTP links in the configuration structure is figure 2 and figure 3.
Figure 2-69 Physical bearer of the SCTP Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194090
VS.SCTP.IPLAYE
R.TXMAXSPEED
T7261:Maximum
Transmit Rate of an
SCTP Link IP Layer
Earlier than
BSC6900
V900R011
67194091
VS.SCTP.IPLAYE
R.TXMINSPEED
T7262:Minimum
Transmit Rate of an
SCTP Link IP Layer
Earlier than
BSC6900
V900R011
67194092
VS.SCTP.IPLAYE
R.TXMEANSPEE
D
T7263:Average
Transmit Rate of an
SCTP Link IP Layer
Earlier than
BSC6900
V900R011
67194093
VS.SCTP.IPLAYE
R.RXMAXSPEED
T7266:Maximum
Receive Rate of an
SCTP Link IP Layer
Earlier than
BSC6900
V900R011
67194094
VS.SCTP.IPLAYE
R.RXMINSPEED
T7267:Minimum
Receive Rate of an
SCTP Link IP Layer
Earlier than
BSC6900
V900R011
67194095
VS.SCTP.IPLAYE
R.RXMEANSPEE
D
T7268:Average
Receive Rate of an
SCTP Link IP Layer
Earlier than
BSC6900
V900R011

4133
BSC6900 UMTS
None
Counters related to the Receive Rate or Transmit Rate of an SCTP link IP layer
Counters
Counter ID
Counter Name
Counter Description
67194090
VS.SCTP.IPLAYER.TXM
AXSPEED
Rate of an SCTP Link IP
Layer
67194091
VS.SCTP.IPLAYER.TXMI
NSPEED
Layer
67194092
VS.SCTP.IPLAYER.TXME
ANSPEED
Layer
67194093
VS.SCTP.IPLAYER.RXM
AXSPEED
Layer
67194094
VS.SCTP.IPLAYER.RXMI
NSPEED
Layer
67194095
VS.SCTP.IPLAYER.RXME
ANSPEED
Layer
Description
These counters provide the end-to-end receive rate or transmit rate of an SCTP link IP layer in
the specified measurement period. The rates measured here include the spending of the IP header
and the payload of the IP packet.
Measurement point
Samples are taken every 5 seconds in the specified measurement period. The system obtains the
number of bytes received and sent on the link once every 5 seconds. With this, the system obtains
the maximum and the minimum number of bytes received or sent in 5 seconds, and the total
number of bytes in one measurement period.
A Stream Control Transmission Protocol (SCTP) link can be configured for one or multiple
boards as follows:
l
Issue 03 (2015-06-30)
A standalone board
4134
BSC6900 UMTS
Two standalone boards
One or two pairs of active and standby boards
A pair of active and standby boards and a standalone board
If an SCTP link is configured for multiple boards, the system calculates the number of bytes
received from and sent to each of the boards every 5 seconds and compares to obtain the
maximum and minimum numbers of bytes received from and sent to each board every 5 seconds.
Then the system compares the maximum and minimum numbers obtained for all the boards to
obtain the maximum and minimum numbers of bytes received and sent on the SCTP link every
5 seconds. The maximum and minimum speed is calculated with the maximum and minimum
bytes in 5 seconds, and the average speed is calculated with the total bytes in one measurement
period.
Formula
None
Unit
kbit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.SCTP.IPLAYER.TXM
AXSPEED
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.SCTP.IPLAYER.TXMI
NSPEED
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.SCTP.IPLAYER.TXME
ANSPEED
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

4135
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.SCTP.IPLAYER.RXM
AXSPEED
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
VS.SCTP.IPLAYER.RXMI
NSPEED
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
VS.SCTP.IPLAYER.RXME
ANSPEED
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
2.50 Measurement of SDH Performance(SDH)

Overview
The Synchronous Digital Hierarchy (SDH) protocol defines digital transmission in terms of the
frame structure, multiplexing mode, transmission rate, and coding rate of the interface.
Measurement of SDH Performance indicates the transmission quality of optical port pairs
between the master and slave boards.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
SDH
SDH Measurement
2.50.1 SDH Measurement(SDH)

Overview
SDH ports are important resources of the Base Station Controller. By measuring the SDH ports,
you can analyze the transmission quality and maintain the stable and secure operation of the
Base Station Controller.
Issue 03 (2015-06-30)

4136
BSC6900 UMTS
Counters
Counter ID
Counter Name
Counter
Description
Original Release
67194469
VS.SDH.SWAP.RE
ASON.REQUEST.
COUNTS
T7041:Number of
SDH Port
Switchovers on
Conditional
Requests
Earlier than
BSC6900
V900R011
67194470
VS.SDH.SWAP.RE
ASON.KBYTE.CO
UNTS
T7042:Number of
SDH Port
Switchovers on K
byte Requests
Earlier than
BSC6900
V900R011
67194471
VS.SDH.SWAP.RE
ASON.EXTERNA
L.COUNTS
T7043:Number of
SDH Port
Switchovers on
external Requests
Earlier than
BSC6900
V900R011
67194472
VS.SDH.FAULT.C
HANNEL.PROTE
CT.COUNTS
T7044:Number of
SDH Protection
Channel Failures
Earlier than
BSC6900
V900R011
67194473
VS.SDH.FAULT.C
HANNEL.WORK.
COUNTS
T7045:Number of
SDH Working
Channel Failures
Earlier than
BSC6900
V900R011
None
Counters Related to the Number of SDH Port Switchovers

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194469
VS.SDH.SWAP.REASON.
REQUEST.COUNTS
T7041:Number of SDH Port

Switchovers on Conditional
Requests
67194470
VS.SDH.SWAP.REASON.
KBYTE.COUNTS

Switchovers on K byte
Requests
67194471
VS.SDH.SWAP.REASON.
EXTERNAL.COUNTS

Switchovers on external
Requests

4137
BSC6900 UMTS
Description
These counters provide the number of switchovers of an SDH port pair in the specified
measurement period. SDH port pair switchover complies to the protocol ITU-T
Recommendation G.841<TYPES AND CHARACTERISTICS OF SDH NETWORK
PROTECTION ARCHITECTURES>.
Measurement point
The measurement is triggered when SDH optical ports are switched over.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SDH.SWAP.REASON.
REQUEST.COUNTS
MRFD-210101
System Redundancy
VS.SDH.SWAP.REASON.
KBYTE.COUNTS
MRFD-210101
System Redundancy
VS.SDH.SWAP.REASON.
EXTERNAL.COUNTS
MRFD-210101
System Redundancy
Counter ID
Counter Name
Counter Description
67194472
VS.SDH.FAULT.CHANNE
L.PROTECT.COUNTS
T7044:Number of SDH
Protection Channel Failures
67194473
VS.SDH.FAULT.CHANNE
L.WORK.COUNTS
T7045:Number of SDH
Working Channel Failures
Number of SDH Channel Failures

Counters
Description
These counters provide the number of failures on an optical port pair in the specified
measurement period. Run MML command DSP MSP to query the slot No. of the protection
channel and the working channel.
Issue 03 (2015-06-30)

4138
BSC6900 UMTS
Measurement point
The measurement is triggered when a fault occurs in the protection or working channel.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.SDH.FAULT.CHANNE
L.PROTECT.COUNTS
MRFD-210101
System Redundancy
VS.SDH.FAULT.CHANNE
L.WORK.COUNTS
MRFD-210101
System Redundancy
2.51 Measurement of Trunk Group Performance(Trunk)

Overview
The trunk technique binds multiple physical ports together as a logical port and uses the total
bandwidth of multiple groups of ports to implement data transmission. The trunk technique
implements the mutual backup function for links in a trunk group. If a link becomes faulty,
services on other links are not affected. In addition, load balancing is implemented between these
links. Measurement of Trunk Group Performance provides the transmission quality of the Trunk
groups carried on boards FG2a, GOUa, FG2c, GOUc and GOUe.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
TRUNK
Trunk Group Measurement
2.51.1 Trunk Group Measurement(Trunk)

Overview
Trunk groups are important resources of the Base Station Controller. Therefore, the Trunk groups
can be measured for the analysis of the transmission quality of the running Base Station
Controller so that the stable and reliable operation of the Base Station Controller can be
maintained. This function subset takes effect after a Trunk is added.
Issue 03 (2015-06-30)

4139
BSC6900 UMTS
Trunk group belongs to the Link layer of the TCP/IP protocol suite, as figure 1 shows.
In the configuration structure, trunks are between physical ports and logical applications, as
Figure 2-71 Physical bearer of the TRUNK
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73439873
VS.TRUNK.RXBY
TES
T7840:Number of
Bytes Received on
the Trunk Group
BSC6900
V900R012

4140
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73439874
VS.TRUNK.RXBY
TESTOTALBAD
T7843:Bytes of Error
Frames Received on
the Trunk Group
BSC6900
V900R012
73439875
VS.TRUNK.TXBY
TES
T7851:Number of
the Trunk Group
BSC6900
V900R012
73439876
VS.TRUNK.TXBY
TESTOTALBAD
T7854:Bytes of Error
Frames Transmitted
on the Trunk Group
BSC6900
V900R012
73439881
VS.TRUNK.RXM
AXSPEED
T7863:Maximum
Receive Rate of the
Trunk Group
BSC6900
V900R012
73439882
VS.TRUNK.RXMI
NSPEED
T7864:Minimum
Receive Rate of the
Trunk Group
BSC6900
V900R012
73439883
VS.TRUNK.RXM
EANSPEED
T7865:Average
Receive Rate of the
Trunk Group
BSC6900
V900R012
73439884
VS.TRUNK.TXM
AXSPEED
T7868:Maximum
Transmitted Rate of
the Trunk Group
BSC6900
V900R012
73439885
VS.TRUNK.TXMI
NSPEED
T7869:Minimum
Transmitted Rate of
the Trunk Group
BSC6900
V900R012
73439886
VS.TRUNK.TXME
ANSPEED
T7870:Average
Transmitted Rate of
the Trunk Group
BSC6900
V900R012
73439887
VS.TRUNK.RX.E
RR.RATIO
T7871:BER of the
Data Received on the
Trunk Group
BSC6900
V900R012
73439888
VS.TRUNK.TX.ER
R.RATIO
T7872:BER of the
Data Transmitted on
the Trunk Group
BSC6900
V900R012
73439889
VS.TRUNK.RXUC
PKTS
T7876:Number of
Unicast Frames
Received on the
Trunk Group
BSC6900
V900R012

4141
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73439890
VS.TRUNK.RXM
CPKTS
T7878:Number of
Multicast Frames
Received on the
Trunk Group
BSC6900
V900R012
73439891
VS.TRUNK.RXBC
PKTS
T7880:Number of
Broadcast Frames
Received on the
Trunk Group
BSC6900
V900R012
73439892
VS.TRUNK.RXFC
SERRORS
T7882:Number of
CRC Error Frames
with Legal Length
Received on the
Trunk Group
BSC6900
V900R012
73439893
VS.TRUNK.RXTA
GGED
T7884:Number of
Frames with VLAN
Flags Received on
the Trunk Group
BSC6900
V900R012
73439894
VS.TRUNK.TXUC
PKTS
T7886:Number of
Unicast Frames
Transmitted on the
Trunk Group
BSC6900
V900R012
73439895
VS.TRUNK.TXM
CPKTS
T7888:Number of
Multicast Frames
Transmitted on the
Trunk Group
BSC6900
V900R012
73439896
VS.TRUNK.TXBC
PKTS
T7890:Number of
Broadcast Frames
Transmitted on the
Trunk Group
BSC6900
V900R012
73439897
VS.TRUNK.TXTA
GGED
T7892:Number of
Frames with VLAN
Flags Transmitted on
the Trunk Group
BSC6900
V900R012
73439898
VS.TRUNK.RXPK
TS
T7894:Number of
Frames Received on
the Trunk Group
BSC6900
V900R012
73439899
VS.TRUNK.TXPK
TS
T7896:Number of
Frames Transmitted
on the Trunk Group
BSC6900
V900R012

4142
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73444337
VS.TRUNK.Alloce
d.Ave.Fwd
T7897:Mean
forward bandwidth
assigned to an Trunk
Group
BSC6900
V900R016C00
73444338
VS.TRUNK.Alloce
d.Ave.Bwd
T7922:Mean
backward bandwidth
Group
BSC6900
V900R016C00
73428284
VS.TRUNK.Alloce
d.Max.Fwd
T7925:Maximum
Forward bandwidth
Group
BSC6900
V900R016C00
73428285
VS.TRUNK.Alloce
d.Max.Bwd
T7926:Maximum
Backward
bandwidth assigned
to an Trunk Group
BSC6900
V900R016C00
73428287
VS.TRUNK.Fwd.C
ong
T7927:Number of
forward congestions
on an Trunk Group
BSC6900
V900R016C00
73444340
VS.TRUNK.Fwd.C
ong.Dur
T7928:Duration of
forward congestion
on an Trunk Group
BSC6900
V900R016C00
73428289
VS.TRUNK.Bwd.C
ong
T7929:Number of
backward
congestions on an
Trunk Group
BSC6900
V900R016C00
73444341
VS.TRUNK.Bwd.C
ong.Dur
T7930:Duration of
backward congestion
on an Trunk Group
BSC6900
V900R016C00
None
Issue 03 (2015-06-30)

4143
BSC6900 UMTS
Number of Bytes That Are Transmitted and Received by Trunk Group

Counters
Counter ID
Counter Name
Counter Description
73439873
VS.TRUNK.RXBYTES
Received on the Trunk Group
73439874
VS.TRUNK.RXBYTESTOTALBAD
T7843:Bytes of Error Frames

73439875
VS.TRUNK.TXBYTES
Transmitted on the Trunk
Group
73439876
VS.TRUNK.TXBYTESTOTALBAD
T7854:Bytes of Error Frames

Group
Description
These counters provide the number of bytes received or transmitted at the data link layer for the
trunk group in a specified measurement period.
They indicate the traffic volume at the data link layer for the trunk group in the specified
measurement period. The number of bytes measured includes the MAC header and payload.
Normally, if the networking scenario remains unchanged, the traffic carried on the trunk group
is constant at the same period every day. Also, values of these counters are constant. If the number
of received and transmitted bytes decreases drastically and the number of bytes incorrectly
received and transmitted increases sharply, you can infer that a transmission fault occurs.
Related counters: Receive Rate and Transmit Rate of Trunk Group, BER of Data Transmitted
and Received by Trunk group
Measurement point
the number of bytes received and transmitted on the port once every five seconds, and calculates
the total number of bytes that are received, transmitted, or discarded in one measurement period.
Formula
None
Unit
byte
Issue 03 (2015-06-30)

4144
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.TRUNK.RXBYTES
MRFD-210103
Link aggregation
VS.TRUNK.RXBYTESTOTALBAD
MRFD-210103
Link aggregation
VS.TRUNK.TXBYTES
MRFD-210103
Link aggregation
VS.TRUNK.TXBYTESTOTALBAD
MRFD-210103
Link aggregation
Receive Rate and Transmit Rate of Trunk Group

Counters
Counter ID
Counter Name
Counter Description
73439883
VS.TRUNK.RXMEANSPEED
Rate of the Trunk Group
73439881
VS.TRUNK.RXMAXSPEED
73439882
VS.TRUNK.RXMINSPEED
73439884
VS.TRUNK.TXMAXSPEED
T7868:Maximum
Transmitted Rate of the
Trunk Group
73439885
VS.TRUNK.TXMINSPEED
T7869:Minimum
Transmitted Rate of the
Trunk Group
73439886
VS.TRUNK.TXMEANSPEED
T7870:Average Transmitted
Description
These counters provide the receive rate and transmit rate of the trunk group at the data link layer
in a specified measurement period.
They indicate the traffic volume at the data link layer for the trunk group in the specified
measurement period. The number of bytes measured includes the number of bytes in the header
of the MAC frame and the payload.
The values of these counters are displayed as integers with decimals rounded down. For example,
if the value of one of these counters is 9.9 kbit/s, the value is displayed as 9 kbit/s.
Issue 03 (2015-06-30)

4145
BSC6900 UMTS
Normally, if the networking scenario remains unchanged, the traffic carried on the trunk group
is constant at the same period every day. Also, values of these counters are constant. If both the
receive rate and transmit rate of the trunk group decrease greatly, you can infer that a transmission
fault occurs.
Related counters: Number of Bytes That Are Transmitted and Received by Trunk Group, BER
of Data Transmitted and Received by Trunk Group
Measurement point
the number of bytes that are transmitted by the trunk group and the number of bytes that are
received by the trunk group every five seconds. The maximum transmit rate can be obtained by
dividing the maximum number of transmitted bytes in five seconds by five. The minimum
transmit rate can be obtained by dividing the minimum number of transmitted bytes in five
seconds by five. The maximum receive rate and the minimum receive rate can also be calculated
in this method. The mean transmit rate can be calculated by dividing the total number of
transmitted bytes by the measurement period. The mean receive rate can also be calculated in
this method.
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.TRUNK.RXMEANSPEED
MRFD-210103
Link aggregation
VS.TRUNK.RXMAXSPEED
MRFD-210103
Link aggregation
VS.TRUNK.RXMINSPEED
MRFD-210103
Link aggregation
VS.TRUNK.TXMAXSPEED
MRFD-210103
Link aggregation
VS.TRUNK.TXMINSPEED
MRFD-210103
Link aggregation
VS.TRUNK.TXMEANSPEED
MRFD-210103
Link aggregation

4146
BSC6900 UMTS
BER of Data Transmitted and Received by Trunk Group

Counters
Counter ID
Counter Name
Counter Description
73439887
VS.TRUNK.RX.ERR.RATIO
T7871:BER of the Data

73439888
VS.TRUNK.TX.ERR.RATIO
T7872:BER of the Data

Group
Description
These counters provide the bit error rate (BER) the data that are transmitted and received by the
trunk group in a specified measurement period.
These counters indicate the BER of the trunk group.
If the BER of the data that is received and transmitted by the trunk group decrease greatly, you
can infer that a transmission fault occurs.
Related counters: Number of Bytes That Are Transmitted and Received by Trunk Group
Measurement point
the BER of the data that is received and transmitted on the port every five seconds. The mean
BER can be obtained by dividing the sum of sampled BERs by the number of sampling times.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.TRUNK.RX.ERR.RATIO
MRFD-210103
Link aggregation
VS.TRUNK.TX.ERR.RATIO
MRFD-210103
Link aggregation

4147
BSC6900 UMTS
Number of Frames That Are Transmitted, Received, or Discarded by the Trunk

Group
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73439898
VS.TRUNK.RXPKTS
73439889
VS.TRUNK.RXUCPKTS
T7876:Number of Unicast
Frames Received on the
Trunk Group
73439890
VS.TRUNK.RXMCPKTS
T7878:Number of Multicast
Trunk Group
73439891
VS.TRUNK.RXBCPKTS
T7880:Number of Broadcast
Trunk Group
73439892
VS.TRUNK.RXFCSERRORS
T7882:Number of CRC Error

Frames with Legal Length
73439893
VS.TRUNK.RXTAGGED
with VLAN Flags Received
on the Trunk Group
73439894
VS.TRUNK.TXUCPKTS
T7886:Number of Unicast
Frames Transmitted on the
Trunk Group
73439895
VS.TRUNK.TXMCPKTS
T7888:Number of Multicast
Trunk Group
73439896
VS.TRUNK.TXBCPKTS
T7890:Number of Broadcast
Trunk Group
73439897
VS.TRUNK.TXTAGGED
with VLAN Flags
Group
73439899
VS.TRUNK.TXPKTS
Group

4148
BSC6900 UMTS
Description
These counters provide the number of frames that are transmitted, received, or discarded by the
trunk group in the measurement period. They indicate the traffic volume on the trunk group. The
frames measured here are MAC frames
Measurement point
the number of frames that are received, transmitted, and discarded on the port every five seconds,
calculates the total number of frames that are received, transmitted, or discarded in one
measurement period.
Formula
None
Unit
frame
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.TRUNK.RXPKTS
MRFD-210103
Link aggregation
VS.TRUNK.RXUCPKTS
MRFD-210103
Link aggregation
VS.TRUNK.RXMCPKTS
MRFD-210103
Link aggregation
VS.TRUNK.RXBCPKTS
MRFD-210103
Link aggregation
VS.TRUNK.RXFCSERRORS
MRFD-210103
Link aggregation
VS.TRUNK.RXTAGGED
MRFD-210103
Link aggregation
VS.TRUNK.TXUCPKTS
MRFD-210103
Link aggregation
VS.TRUNK.TXMCPKTS
MRFD-210103
Link aggregation
VS.TRUNK.TXBCPKTS
MRFD-210103
Link aggregation
VS.TRUNK.TXTAGGED
MRFD-210103
Link aggregation
VS.TRUNK.TXPKTS
MRFD-210103
Link aggregation

4149
BSC6900 UMTS

Trunk Group
Counters
Counter ID
Counter Name
Counter Description
73444337
VS.TRUNK.Alloced.Ave.F
wd
T7897:Mean forward
Trunk Group
73444338
VS.TRUNK.Alloced.Ave.B
wd
T7922:Mean backward
Trunk Group
73428284
VS.TRUNK.Alloced.Max.F
wd
Trunk Group
73428285
VS.TRUNK.Alloced.Max.B
wd
Trunk Group
Description
When services access the network, bandwidth admission needs to be performed on trunk groups.
These counters provide the forward bandwidth or backward bandwidth allocated to a trunk
group. The forward direction indicates the TX direction and the backward direction indicates
the RX direction. The average forward or backward bandwidth allocated to a trunk group
indicates the traffic volume in a measurement period. The maximum forward or backward
bandwidth allocated to a trunk group indicates the maximum traffic volume in a measurement
period.
Measurement point
allocated to a trunk group every 15s. At the end of the measurement period, the system divides
the accumulated value by the sampling times to obtain the average value and uses the maximum
Formula
None
Unit
bit/s
Issue 03 (2015-06-30)

4150
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.TRUNK.Alloced.Ave.F
wd
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.TRUNK.Alloced.Ave.B
wd
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.TRUNK.Alloced.Max.F
wd
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
VS.TRUNK.Alloced.Max.B
wd
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Measurement of the Number of Congestions on an Trunk Group

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73428287
VS.TRUNK.Fwd.Cong
congestions on an Trunk
Group
73428289
VS.TRUNK.Bwd.Cong
congestions on an Trunk
Group

4151
BSC6900 UMTS
Description
congestion remaining threshold configured for a trunk group, traffic on the trunk group is
counters provide the number of forward or backward congestions on a trunk group in a
congestion on a trunk group to observe the congestion. If traffic on many trunk groups is
Measurement point
In a measurement period, these counters are incremented by one each time the state of a trunk
group changes from non-congestion to forward or backward congestion.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.TRUNK.Fwd.Cong
WRFD-050402
on Iub Interface
WRFD-050409
WRFD-050410
on Iu Interface
on Iur Interface
VS.TRUNK.Bwd.Cong
WRFD-050402
WRFD-050409
WRFD-050410
on Iub Interface
on Iu Interface
on Iur Interface
Issue 03 (2015-06-30)

4152
BSC6900 UMTS
Measurement of the Duration of Congestion on an Trunk Group

Counters
Counter ID
Counter Name
Counter Description
73444340
VS.TRUNK.Fwd.Cong.Dur
congestion on an Trunk
Group
73444341
VS.TRUNK.Bwd.Cong.Dur
congestion on an Trunk
Group
Description
congestion remaining threshold configured for a trunk group, traffic on the trunk group is
counters provide the duration of congestions on a trunk group in a measurement period. The
direction. These counters can be used together with the number of congestions on a trunk group
to observe the congestion. If traffic on many trunk groups is congested for a long time, services
are affected.
Measurement point
on a trunk group. The measurement stops when the congestion relieves. At the end of the
measurement period, the system uses the accumulated duration as the values of these counters.
Formula
None
Unit
s
Issue 03 (2015-06-30)

4153
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.TRUNK.Fwd.Cong.Dur
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
VS.TRUNK.Bwd.Cong.Dur
WRFD-050402
on Iub Interface
WRFD-050409
on Iu Interface
WRFD-050410
on Iur Interface
2.52 Measurement of TWAMP Performance(TWAMP)

Overview
TWAMP(Two-Way Active Measurement Protocol) defines a flexible method to measure IP
performance between two TWAMP devices on a network. TWAMP uses UDP data packets to
measure the two-way delay on the network. Before measurement, TWAMP uses the TCP
protocol to control measured sessions to negotiate the UDP port No. between hosts and to check
whether the measured data is encrypted during transmission. It can effectively and completely
measure IP performance of transmission through coordination between deployed network
devices. TWAMP is used to perform IP performance monitoring (PM) between a controller and
a device supporting TWAMP on a radio network. The application scenarios of the measurement
object are as follows:
1.Acceptance of quality of service (QoS) on the radio network during a site deployment.
2.Location of transmission performance problems and monitoring of performance quality on the
transmission network during daily operation and maintenance.
FunctionSubSets
Issue 03 (2015-06-30)
FunctionSubSet
FunctionSubSet Name
TransportLink.TWAMP
TWAMP Transport Link Measurement

4154
BSC6900 UMTS
2.52.1 TWAMP Transport Link Measurement

(TransportLink.TWAMP)
Overview
The counters for the TWAMP Measurement function subset are used to monitor transmission
QoS, including round trip time (RTT), one-way packet loss rate, and one-way jitter.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
73443304
VS.TWAMP.Forw
ard.DropRates.Ma
x
Peak Forward Packet

Loss Rates for
TWAMP
Measurement
BSC6900
V900R015C00
73443305
VS.TWAMP.Back
ward.DropRates.M
ean
Average Backward
Packet Loss Rates for
TWAMP
Measurement
BSC6900
V900R015C00
73443306
VS.TWAMP.Back
ward.DropRates.M
ax
Peak Backward
TWAMP
Measurement
BSC6900
V900R015C00
73426982
VS.TWAMP.RttDe
lay.Min
Minimum RTT for

TWAMP
Measurement
BSC6900
V900R015C00
73426983
VS.TWAMP.RttDe
lay.Max
Maximum RTT for

TWAMP
Measurement
BSC6900
V900R015C00
73443307
VS.TWAMP.RttDe
lay.Mean
Average RTT for

TWAMP
Measurement
BSC6900
V900R015C00
73426985
VS.TWAMP.Forw
ard.Jitter.Min
Minimum Forward
Delay Jitters for
TWAMP
Measurement
BSC6900
V900R015C00
73426986
VS.TWAMP.Forw
ard.Jitter.Max
Maximum Forward
Delay Jitters for
TWAMP
Measurement
BSC6900
V900R015C00

4155
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
73443308
VS.TWAMP.Forw
ard.Jitter.Mean
Average Forward
Delay Jitters for
TWAMP
Measurement
BSC6900
V900R015C00
73426989
VS.TWAMP.Back
ward.Jitter.Min
Minimum Backward
Delay Jitters for
TWAMP
Measurement
BSC6900
V900R015C00
73426990
VS.TWAMP.Back
ward.Jitter.Max
Maximum Backward
Delay Jitters for
TWAMP
Measurement
BSC6900
V900R015C00
73443309
VS.TWAMP.Back
ward.Jitter.Mean
Average Backward
Delay Jitters for
TWAMP
Measurement
BSC6900
V900R015C00
73443310
VS.TWAMP.Forw
ard.DropRates.Me
an
Average Forward
TWAMP
Measurement
BSC6900
V900R015C00
None
RTT for TWAMP Measurement

Counters
Counter ID
Counter Name
Counter Description
73426982
VS.TWAMP.RttDelay.Min
Minimum RTT for TWAMP

Measurement
73426983
VS.TWAMP.RttDelay.Max
Maximum RTT for TWAMP

Measurement
73443307
VS.TWAMP.RttDelay.Mea
n
Average RTT for TWAMP

Measurement
Description
These counters provide the minimum, maximum, and average RTT for a TWAMP measurement.
Issue 03 (2015-06-30)

4156
BSC6900 UMTS
Measurement point
Figure 1 shows the principles for the TWAMP to calculate the RTT.
T1 indicates the time when the sender sends a packet.
T2 indicates the time when the reflector receives a packet.
T3 indicates the time when the reflector sends a response packet.
T4 indicates the time when the sender receives a response packet.
RTT = (T2 - T1) + (T4 - T3) = (T4 - T1) - (T3 - T2)
The controller samples the RTT every 5s and uses the minimum value as the value of the
VS.TWAMP.RttDelay.Min counter, the maximum value as the value of the
VS.TWAMP.RttDelay.Max counter, and the average value as the value of the
VS.TWAMP.RttDelay.Mean counter.
Figure 2-72 RTT Time Delay
Formula
None
Unit
ms
Issue 03 (2015-06-30)

4157
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.TWAMP.RttDelay.Min
WRFD-151211
RNC IP Active Performance

Measurement
VS.TWAMP.RttDelay.Max
WRFD-151211

Measurement
VS.TWAMP.RttDelay.Mea
n
WRFD-151211

Measurement
Forward and Backward Delay Jitters for TWAMP Measurement

Counters
Counter ID
Counter Name
Counter Description
73426985
VS.TWAMP.Forward.Jitter.
Min
Minimum Forward Delay

Jitters for TWAMP
Measurement
73426986
Max
Maximum Forward Delay

Jitters for TWAMP
Measurement
73443308
Mean
Average Forward Delay

Jitters for TWAMP
Measurement
73426989
VS.TWAMP.Backward.Jitte
r.Min
Minimum Backward Delay

Jitters for TWAMP
Measurement
73426990
r.Max
Maximum Backward Delay

Jitters for TWAMP
Measurement
73443309
r.Mean
Average Backward Delay

Jitters for TWAMP
Measurement
Description
These counters provide the minimum, maximum, and average forward delay jitters, and the
minimum, maximum, and average backward delay jitters for a TWAMP measurement.
Measurement point
Figure 1 shows the principles for the TWAMP to calculate the delay jitter.
Issue 03 (2015-06-30)

4158
BSC6900 UMTS
T1_1 indicates the time when the sender sends packet 1.

T1_2 indicates the time when the reflector receives packet 1.
T1_3 indicates the time when the reflector sends response packet 1.
T1_4 indicates the time when the sender receives response packet 1.
T2_1 indicates the time when the sender sends packet 2.
T2_2 indicates the time when the reflector receives packet 2.
T2_3 indicates the time when the reflector sends response packet 2.
T2_4 indicates the time when the sender receives response packet 2.
The forward delay is calculated using the following formula:
T1_2 - T1_1 = delta T_1
The backward delay is calculated using the following formula:
T1_4 - T1_3 = delta D_1
For response packet 2:
The forward delay is calculated using the following formula:
T2_2 - T2_1 = delta T_2
The backward delay is calculated using the following formula:
T2_4 - T2_3 = delta D_2
Then:
The forward jitter is calculated using the following formula:
J1 = delta T_2 - delta T_1 = (T2_2 - T2_1) - (T1_2 - T1_1)
The backward jitter is calculated using the following formula:
Q1 = delta D_2 - delta D_1 = (T2_4 - T2_3) - (T1_4 - T1_3)
The controller samples the forward and backward delay jitters every 5s and uses the minimum
values as the values of the VS.TWAMP.Forward.Jitter.Min and
VS.TWAMP.Backward.Jitter.Min counters, the maximum values as the values of the
VS.TWAMP.Forward.Jitter.Max and VS.TWAMP.Backward.Jitter.Max counters, and the
average values as the values of the VS.TWAMP.Forward.Jitter.Mean and
VS.TWAMP.Backward.Jitter.Mean counters.
Issue 03 (2015-06-30)

4159
BSC6900 UMTS
Figure 2-73 Delay Jitter
Formula
None
Unit
ms
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Min
WRFD-151211

Measurement
Max
WRFD-151211

Measurement

4160
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
Mean
WRFD-151211

Measurement
r.Min
WRFD-151211

Measurement
r.Max
WRFD-151211

Measurement
r.Mean
WRFD-151211

Measurement
Forward and Backward Packet Loss Rates for TWAMP Measurement

Counters
Counter ID
Counter Name
Counter Description
73443310
VS.TWAMP.Forward.Drop
Rates.Mean
Average Forward Packet

Loss Rates for TWAMP
Measurement
73443304
Rates.Max
Peak Forward Packet Loss

Rates for TWAMP
Measurement
73443305
VS.TWAMP.Backward.Dro
pRates.Mean
Average Backward Packet

Loss Rates for TWAMP
Measurement
73443306
pRates.Max
Peak Backward Packet Loss

Rates for TWAMP
Measurement
Description
These counters provide the average forward packet loss rate, peak forward packet loss rate,
average backward packet loss rate, and peak backward packet loss rate for a TWAMP
measurement.
Measurement point
The controller samples the number of packets sent by the sender and reflector and the number
of packets received by the sender from the TWAMP in a measurement period of 30s.
Number of forward lost packets = Number of packets sent by the sender - Number of packets
sent by the reflector.
Issue 03 (2015-06-30)

4161
BSC6900 UMTS
Number of backward lost packets = Number of packets sent by the reflector - Number of packets
received by the sender.
VS.TWAMP.Forward.DropRates.Mean: The controller obtains the number of packets sent by
the sender and number of forward lost packets every 30s, and accumulates the values to obtain
the total number of forward lost packets, and calculates the average forward packet loss rate in
a measurement period by dividing the total number of forward lost packets by the total number
of packets sent by the sender.
VS.TWAMP.Forward.DropRates.Max: The controller calculates the packet loss rate every 30s
by dividing the total number of forward lost packets by the number of packets sent by the sender
and uses the maximum value as the value of this counter.
VS.TWAMP.Backward.DropRates.Mean: The controller obtains the number of packets sent by
the reflector and number of backward lost packets every 30s, and accumulates the values to
obtain the total number of backward lost packets, and calculates the average backward packet
loss rate in a measurement period by dividing the total number of backward lost packets by the
total number of packets sent by the reflector.
VS.TWAMP.Backward.DropRates.Max: The controller calculates the packet loss rate every 30s
by dividing the total number of backward lost packets by the number of packets sent by the
reflector and uses the maximum value as the value of this counter.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
Rates.Mean
WRFD-151211

Measurement
Rates.Max
WRFD-151211

Measurement
pRates.Mean
WRFD-151211

Measurement
pRates.Max
WRFD-151211

Measurement

4162
BSC6900 UMTS
2.53 Measurement of UNI Link Performance(UNILNK)

Overview
UNILNK means User-Network Interface Link. The UNILNK performance measurement
indicates the transmission quality of a UNI link on the AEUa, AOUa or AOUc board.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
UNILNK
UNI Link Measurement
2.53.1 UNI Link Measurement(UNILNK)

Overview
The quality of transmission links directly affects the system performance. UNI Link
reliability. This function subset takes effect after a UNI link is added. It measures data
transmission and reception, allocated bandwidth, and congestion on a UNI link.
UNI Link belongs to the physical layer of the ATM reference model, as figure 1 shows.
Issue 03 (2015-06-30)

4163
BSC6900 UMTS
In the configuration structure, UNI links are between physical ports and logical applications, as
Figure 2-75 Physical bearer of the UNI Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67190491
VS.UNILNK.TXC
ELLS
Number of Cells
Transmitted on a
UNI Link
Earlier than
BSC6900
V900R011
67202977
VS.UNILNK.PEA
K.TXRATE
Maximum Rate of
Transmitting Cells
on a UNI Link
Earlier than
BSC6900
V900R011
67190490
VS.UNILNK.RXC
ELLS
Number of Cells
Received on a UNI
Link
Earlier than
BSC6900
V900R011
67202976
VS.UNILNK.PEA
K.RXRATE
Maximum Rate of
Receiving Cells on a
UNI Link
Earlier than
BSC6900
V900R011
67194049
VS.UNILNK.RXH
CSERRCELLS
Number of Error
Cells Received on a
UNI Link
Earlier than
BSC6900
V900R011
67194050
VS.UNILNK.RXD
ROPS
Number of Cells
Discarded on a UNI
Link
Earlier than
BSC6900
V900R011

4164
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67202915
VS.UNI.Lnk.Mean
Kbps.Rx
Average Rate of
Receiving Cells a
UNI Link
Earlier than
BSC6900
V900R011
67202916
VS.UNI.Lnk.Mean
Kbps.Tx
Average Rate of
Transmitting Cells
on a UNI Link
Earlier than
BSC6900
V900R011
67204196
VS.UNILNK.Alloc
ed.Ave.Fwd
Mean Forward
Bandwidth
Allocated for UNI
Link
Earlier than
BSC6900
V900R011
67204197
VS.UNILNK.Alloc
ed.Ave.Bwd
Mean Backward
Bandwidth
Allocated for UNI
Link
Earlier than
BSC6900
V900R011
67193235
VS.UNILNK.Alloc
ed.Max.Fwd
Maximum Forward
Bandwidth
Allocated for UNI
Link
Earlier than
BSC6900
V900R011
67193236
VS.UNILNK.Alloc
ed.Max.Bwd
Maximum Backward
Bandwidth
Allocated for UNI
Link
Earlier than
BSC6900
V900R011
67193237
VS.UNILNK.Fwd.
Cong
Number of UNI Link

Forward
Congestions
Earlier than
BSC6900
V900R011
67193238
VS.UNILNK.Fwd.
Cong.Dur
Duration of UNI
Link Forward
Congestions
Earlier than
BSC6900
V900R011
67193239
VS.UNILNK.Bwd.
Cong
Number of UNI Link

Backward
Congestions
Earlier than
BSC6900
V900R011
67193240
VS.UNILNK.Bwd.
Cong.Dur
Duration of UNI
Link Backward
Congestions
Earlier than
BSC6900
V900R011
None
Issue 03 (2015-06-30)

4165
BSC6900 UMTS
Counters Related to the Number of Cells Received or Transmitted on a UNI Link

Counters
Counter ID
Counter Name
Counter Description
67190490
VS.UNILNK.RXCELLS

a UNI Link
67190491
VS.UNILNK.TXCELLS

on a UNI Link
67194049
VS.UNILNK.RXHCSERRCELLS

Received on a UNI Link
67194050
VS.UNILNK.RXDROPS

on a UNI Link
Description
These counters provide the number of cells received or transmitted on a UNI link in the specified
measurement period.
Measurement point
the number of cells transmitted, received or discarded on the link once every five seconds and
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.UNILNK.RXCELLS
WRFD-05030101

Interface
VS.UNILNK.TXCELLS
WRFD-05030101

Interface
VS.UNILNK.RXHCSERRCELLS
WRFD-05030101

Interface

4166
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.UNILNK.RXDROPS
WRFD-05030101

Interface
Counters Related to the Receive Rate or Transmit Rate of a UNI Link

Counters
Counter ID
Counter Name
Counter Description
67202976
VS.UNILNK.PEAK.RXRA
TE
Maximum Rate of Receiving

Cells on a UNI Link
67202977
VS.UNILNK.PEAK.TXRA
TE
Maximum Rate of
Transmitting Cells on a UNI
Link
67202915
VS.UNI.Lnk.MeanKbps.Rx
Average Rate of Receiving

Cells a UNI Link
67202916
VS.UNI.Lnk.MeanKbps.Tx
Average Rate of
Transmitting Cells on a UNI
Link
Description
These counters provide the receive rate or transmit rate of a UNI link in the specified
measurement period.
Measurement point
the number of bytes transmitted, received or discarded on the link once every five seconds and
obtains the total number of bytes in one measurement period.
Formula
None
Unit
kbit/s
Issue 03 (2015-06-30)

4167
BSC6900 UMTS
Related Features
Counter Name
Feature ID
Feature Name
VS.UNILNK.PEAK.RXRA
TE
WRFD-05030101

Interface
VS.UNILNK.PEAK.TXRA
TE
WRFD-05030101

Interface
VS.UNI.Lnk.MeanKbps.Rx
WRFD-05030101

Interface
VS.UNI.Lnk.MeanKbps.Tx
WRFD-05030101

Interface
Measurement of the Forward Bandwidth or Backward Bandwidth Assigned to a

UNI Link
Counters
Counter ID
Counter Name
Counter Description
67204196
VS.UNILNK.Alloced.Ave.F
wd
Mean Forward Bandwidth

Allocated for UNI Link
67204197
VS.UNILNK.Alloced.Ave.
Bwd

Allocated for UNI Link
67193235
VS.UNILNK.Alloced.Max.
Fwd
Maximum Forward
Bandwidth Allocated for
UNI Link
67193236
Bwd
Maximum Backward
Bandwidth Allocated for
UNI Link
Description
When services access the network, bandwidth admission needs to be performed on UNI links.
These counters provide the maximum or average forward/backward bandwidth allocated to a
UNI link in a specified measurement period. The forward direction indicates the TX direction
and the backward direction indicates the RX direction. The average forward or backward
bandwidth indicates the traffic volume in a measurement period. The maximum forward or
backward bandwidth indicates the maximum traffic volume in a measurement period.
Measurement point
allocated to a UNI link every 15s. At the end of the measurement period, the system divides the
Issue 03 (2015-06-30)

4168
BSC6900 UMTS
accumulated value by the sampling times to obtain the average value and uses the maximum
Formula
None
Unit
bit/s
Related Features
Counter Name
Feature ID
Feature Name
VS.UNILNK.Alloced.Ave.F
wd
WRFD-05030106

VS.UNILNK.Alloced.Ave.
Bwd
WRFD-05030106

Fwd
WRFD-05030106

Bwd
WRFD-05030106

Measurement of the Number of Congestions on a UNI Link

Counters
Counter ID
Counter Name
Counter Description
67193237
VS.UNILNK.Fwd.Cong
Number of UNI Link

Forward Congestions
67193239
VS.UNILNK.Bwd.Cong
Number of UNI Link

Backward Congestions
Description
congestion remaining threshold configured for a UNI link, traffic on the UNI link is congested.
provide the number of forward or backward congestions on a UNI link in a measurement period.
The forward direction indicates the TX direction and the backward direction indicates the RX
direction. These counters can be used together with the duration of congestion on a UNI link to
Issue 03 (2015-06-30)

4169
BSC6900 UMTS
observe the congestion. If traffic on many UNI links is congested for a long time, services are
affected.
Measurement point
In a measurement period, this counter is incremented by one each time a UNI link changes from
the non-congestion state to the congestion state.
Formula
None
Unit
None
Related Features
Counter Name
Feature ID
Feature Name
VS.UNILNK.Fwd.Cong
WRFD-05030106

VS.UNILNK.Bwd.Cong
WRFD-05030106

Measurement of the Duration of Congestion on an UNI Link

Counters
Counter ID
Counter Name
Counter Description
67193238
VS.UNILNK.Fwd.Cong.Du
r
Duration of UNI Link

Forward Congestions
67193240
VS.UNILNK.Bwd.Cong.Du
r
Duration of UNI Link

Backward Congestions
Description
congestion remaining threshold configured for a UNI link, traffic on the UNI link is congested.
provide the duration of congestions on a UNI link in a measurement period. The forward
direction indicates the TX direction and the backward direction indicates the RX direction. These
counters can be used together with the number of congestions on a UNI link to observe the
congestion. If traffic on many UNI links is congested for a long time, services are affected.
Issue 03 (2015-06-30)

4170
BSC6900 UMTS
Measurement point
on a UNI link. The measurement stops when the congestion relieves. At the end of the
measurement period, the system uses the accumulated duration as the values of these counters.
Formula
None
Unit
s
Related Features
Counter Name
Feature ID
Feature Name
VS.UNILNK.Fwd.Cong.Du
r
WRFD-05030106

VS.UNILNK.Bwd.Cong.Du
r
WRFD-05030106

2.54 Measurement of VC Cross Connection Performance

(VCACROSS)
Overview
The VPL/VCL Cross-Connects specifies the VPL or VCL cross-connection and is used to
configure VCL or VPL cross-connections within a board or between two boards. Measurement
of VC Cross Connection Performance indicates the transmission quality in the ATM layer of a
VC cross connection on the AEUa , AOUa, or UOIa board.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
VCACROSS
VC Cross Connection Measurement
2.54.1 VC Cross Connection Measurement(VCACROSS)

Overview
The VC Cross Connection Measurement collect statistics on the traffic volume of the VC
connection in both the receiving and transmitting directions to indicate the QoS in ATM layer
of the connection. This function subset takes effect after the VPCLCX is added.
Issue 03 (2015-06-30)

4171
BSC6900 UMTS

The position of the VC corss in the configuration structure is in figure 2.
Issue 03 (2015-06-30)

4172
BSC6900 UMTS
Figure 2-77 Physical bearer of the VCL Cross
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194494
VS.VCCROSS.RX
BYTES
Number of Bytes
Received on a VC
Cross Connection
Earlier than
BSC6900
V900R011
67194495
VS.VCCROSS.TX
BYTES
Number of Bytes
Transmitted on a VC
Cross Connection
Earlier than
BSC6900
V900R011
67194496
VS.VCCROSS.RX
CELLS
Number of Cells
Received on a VC
Cross Connection
Earlier than
BSC6900
V900R011
67194497
VS.VCCROSS.TX
CELLS
Number of Cells
Transmitted on a VC
Cross Connection
Earlier than
BSC6900
V900R011
67194498
VS.VCCROSS.RX
HCSERRCELLS

HCS(Header Check
Sum) Errors
Received on a VC
Cross Connection
Earlier than
BSC6900
V900R011

4173
BSC6900 UMTS
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194499
VS.VCCROSS.RX
DROPCELLS
Number of Cells
Discarded in the
Receiving Direction
of a VC Cross
Connection Due to
the Congestion of the
ATM Layer
Earlier than
BSC6900
V900R011
67194500
VS.VCCROSS.RX
OVERFLOWDRO
PCELLS
Number of Cells
Discarded on a VC
Cross Connection
Due to the Overflow
of the Receiving
Buffer
Earlier than
BSC6900
V900R011
67194501
VS.VCCROSS.RX
RECTIFIABLEHE
CERRCELLS

rectifiable HEC
Errors Received on a
VC Cross
Connection
Earlier than
BSC6900
V900R011
67194502
VS.VCCROSS.RX
UNRECTIFIABLE
HECERRCELLS

Unrectifiable HEC
Errors Received on a
VC Cross
Connection
Earlier than
BSC6900
V900R011
67194503
VS.VCCROSS.TX
OVERFLOWDRO
PCELLS
Number of Cells
Discarded Because
of Sending Buffer
Overflow on a VC
Cross Connection
Earlier than
BSC6900
V900R011
67194504
VS.VCCROSS.TX
DROPCELLS
Number of Cells
Abnormally
Discarded on a VC
Cross Connection
Earlier than
BSC6900
V900R011
67194505
VS.VCCROSS.TX
OVERFLOWCEL
LS
Number of Overflow
Cells on a VC Cross
Connection
Earlier than
BSC6900
V900R011
67194506
VS.VCCROSS.TX
MAXSPEED
Maximum Transmit
Rate of a VC Cross
Connection
Earlier than
BSC6900
V900R011
67194507
VS.VCCROSS.TX
MINSPEED
Minimum Transmit
Rate of a VC Cross
Connection
Earlier than
BSC6900
V900R011

4174
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67194508
VS.VCCROSS.TX
MEANSPEED
Average Transmit
Rate of a VC Cross
Connection
Earlier than
BSC6900
V900R011
67194509
VS.VCCROSS.RX
MAXSPEED
Maximum Receive
Rate of a VC Cross
Connection
Earlier than
BSC6900
V900R011
67194510
VS.VCCROSS.RX
MINSPEED
Minimum Receive
Rate of a VC Cross
Connection
Earlier than
BSC6900
V900R011
67194511
VS.VCCROSS.RX
MEANSPEED
Average Receive
Rate of a VC Cross
Connection
Earlier than
BSC6900
V900R011
None
Measurement of the Number of Bytes Received or Transmitted on a VCCROSS

Link
Counters
Counter ID
Counter Name
Counter Description
67194494
VS.VCCROSS.RXBYTES

on a VC Cross Connection
67194495
VS.VCCROSS.TXBYTES
Number of Bytes
Transmitted on a VC Cross
Connection
Description
These counters provide the number of bytes received or transmitted on a VC cross connection
at the ATM layer in the specified measurement period.
Measurement point
Issue 03 (2015-06-30)

4175
BSC6900 UMTS
Formula
None
Unit
byte
Related Features
Counter Name
Feature ID
Feature Name
VS.VCCROSS.RXBYTES
WRFD-05030101

Interface
VS.VCCROSS.TXBYTES
WRFD-05030101

Interface
Measurement of the Number of Cells Received or Transmitted on a VCCROSS

Link
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
67194496
VS.VCCROSS.RXCELLS

a VC Cross Connection
67194497
VS.VCCROSS.TXCELLS

67194498
VS.VCCROSS.RXHCSER
RCELLS
Number of Cells with HCS

(Header Check Sum) Errors
Received on a VC Cross
Connection
67194499
VS.VCCROSS.RXDROPCELLS

in the Receiving Direction of
a VC Cross Connection Due
to the Congestion of the
ATM Layer
67194500
VS.VCCROSS.RXOVERFLOWDROPCELLS

Due to the Overflow of the
Receiving Buffer
67194501
VS.VCCROSS.RXRECTIFIABLEHECERRCELLS

rectifiable HEC Errors
Connection

4176
BSC6900 UMTS
Counter ID
Counter Name
Counter Description
67194502
VS.VCCROSS.RXUNRECTIFIABLEHECERRCELLS

Unrectifiable HEC Errors
Connection
67194503
VS.VCCROSS.TXOVERFLOWDROPCELLS

Because of Sending Buffer
Overflow on a VC Cross
Connection
67194504
VS.VCCROSS.TXDROPCELLS
Number of Cells Abnormally

Discarded on a VC Cross
Connection
67194505
VS.VCCROSS.TXOVERFLOWCELLS
Number of Overflow Cells

Description
These counters provide the number of cells received or transmitted on a VC cross connection at
the ATM layer in the specified measurement period, HEC Errors means Header Error Control
check failure.
Measurement point
the number of cells transmitted, received or discarded on the link once every five seconds and
Formula
None
Unit
None
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VCCROSS.RXCELLS
WRFD-05030101

Interface
VS.VCCROSS.TXCELLS
WRFD-05030101

Interface
VS.VCCROSS.RXHCSER
RCELLS
WRFD-05030101

Interface

4177
BSC6900 UMTS
Counter Name
Feature ID
Feature Name
VS.VCCROSS.RXDROPCELLS
WRFD-05030101

Interface
VS.VCCROSS.RXOVERFLOWDROPCELLS
WRFD-05030101

Interface
VS.VCCROSS.RXRECTIFIABLEHECERRCELLS
WRFD-05030101

Interface
VS.VCCROSS.RXUNRECTIFIABLEHECERRCELLS
WRFD-05030101

Interface
VS.VCCROSS.TXOVERFLOWDROPCELLS
WRFD-05030101

Interface
VS.VCCROSS.TXDROPCELLS
WRFD-05030101

Interface
VS.VCCROSS.TXOVERFLOWCELLS
WRFD-05030101

Interface
Counters Related to the Receive Rate or Transmit Rate of a VC Cross Connection

Counters
Counter ID
Counter Name
Counter Description
67194506
VS.VCCROSS.TXMAXSPEED
Maximum Transmit Rate of a

VC Cross Connection
67194507
VS.VCCROSS.TXMINSPEED
Minimum Transmit Rate of a

VC Cross Connection
67194508
VS.VCCROSS.TXMEANSPEED
Average Transmit Rate of a

VC Cross Connection
67194509
VS.VCCROSS.RXMAXSPEED
Maximum Receive Rate of a

VC Cross Connection
67194510
VS.VCCROSS.RXMINSPEED
Minimum Receive Rate of a

VC Cross Connection
67194511
VS.VCCROSS.RXMEANSPEED
Average Receive Rate of a

VC Cross Connection
Description
These counters provide the receive rate or transmit rate of a VC cross connection at the ATM
layer in the specified measurement period.
Issue 03 (2015-06-30)

4178
BSC6900 UMTS
Measurement point
Formula
None
Unit
kbit/s
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.VCCROSS.TXMAXSPEED
WRFD-05030101

Interface
VS.VCCROSS.TXMINSPEED
WRFD-05030101

Interface
VS.VCCROSS.TXMEANSPEED
WRFD-05030101

Interface
VS.VCCROSS.RXMAXSPEED
WRFD-05030101

Interface
VS.VCCROSS.RXMINSPEED
WRFD-05030101

Interface
VS.VCCROSS.RXMEANSPEED
WRFD-05030101

Interface

4179
BSC6900 UMTS
3 Hardware Platform Related Measurement
Hardware Platform Related Measurement
About This Chapter

The following measurements are Hardware Platform Related Measurement.
3.1 Measurement of ASU Subsystem Performance(ASU)
3.2 Measurement of DEU Subsystem Performance(DEU)
3.3 Measurement of DEU DSP Performance(DEUDSP)
3.4 Measurement of DPU Subsystem Performance(DPU)
3.5 Measurement of Inter-Subrack Traffic Performance(FRAME_FLUX)
3.6 Measurement of GCU Subsystem Performance(GCU)
3.7 Measurement of Interface Board Subsystem Performance(INT)
3.8 Measurement of NIU DSP Performance(NDSP)
3.9 Measurement of NIU Subsystem Performance(NIU)
3.10 Measurement of RNC Node Performance(RNCNODE)
3.11 Measurement of SCU Subsystem Performance(SCU)
3.12 Measurement of XPU Subsystem Performance(XPU)
Issue 03 (2015-06-30)

4180
BSC6900 UMTS
3.1 Measurement of ASU Subsystem Performance(ASU)

Overview
ASU performance measurement indicates the operating status, such as the CPU usage, of a single
ASU in a subrack.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
ASU
ASU Subsystem Measurement
3.1.1 ASU Subsystem Measurement(ASU)

Overview
ASU measurement indicates the operating state, such as the CPU usage, of a single ASU system.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73429458
VS.ASU.CPULOA
D.MAX
HR9120:Maximum
CPU Usage of the
ASU
BSC6900
V900R017C10
73445350
VS.ASU.CPULOA
D.MEAN
AR9120:Average
CPU Usage of the
ASU
BSC6900
V900R017C10
73445352
VS.ASU.CPULOA
D.OVER
TR9120a:Rate of the
Period in Which the
CPU Usage of the
ASU Exceeds the
Alarm Threshold
BSC6900
V900R017C10
73445351
VS.ASU.CPULOA
D.LESS
TR9120b:Rate of the
Period in Which the
CPU Usage of the
ASU is Lower than
the Alarm Threshold
BSC6900
V900R017C10
None
Issue 03 (2015-06-30)

4181
BSC6900 UMTS
Maximum CPU Usage of the ASU

Counters
Counter ID
Counter Name
Counter Description
73429458
VS.ASU.CPULOAD.MAX
HR9120:Maximum CPU
Usage of the ASU
Description
None
Measurement point
The CPU usage of the ASU is sampled every second in the measurement period. Then, the
maximum usage is taken as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.ASU.CPULOAD.MAX
WRFD-040100
Flow Control
Counter ID
Counter Name
Counter Description
73445350
VS.ASU.CPULOAD.MEA
N
AR9120:Average CPU
Usage of the ASU
Average CPU Usage of the ASU

Counters
Description
None
Issue 03 (2015-06-30)

4182
BSC6900 UMTS
Measurement point
The CPU usage of the ASU subsystem is sampled and accumulated every second in the
measurement period. Then, the average CPU usage of the ASU subsystem is the accumulated
value divided by the number of sampling times.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.ASU.CPULOAD.MEA
N
WRFD-040100
Flow Control
Rate of the Period in Which the CPU Usage of the ASU Exceeds the Alarm
Threshold
Counters
Counter ID
Counter Name
Counter Description
73445352
VS.ASU.CPULOAD.OVER
TR9120a:Rate of the Period

in Which the CPU Usage of
the ASU Exceeds the Alarm
Threshold
Description
None
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the ASU exceeds
the alarm threshold is divided by the number of sampling times for a rate. The sampling period
is 1s.
Formula
None
Issue 03 (2015-06-30)

4183
BSC6900 UMTS
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.ASU.CPULOAD.OVER
WRFD-040100
Flow Control
Rate of the Period in Which the CPU Usage of the ASU is Lower than the Alarm
Threshold
Counters
Counter ID
Counter Name
Counter Description
73445351
VS.ASU.CPULOAD.LESS
TR9120b:Rate of the Period

the ASU is Lower than the
Alarm Threshold
Description
None
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the ASU is lower
than the alarm threshold is divided by the number of sampling times for a rate. The sampling
period is 1s.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.ASU.CPULOAD.LESS
WRFD-040100
Flow Control

4184
BSC6900 UMTS
3.2 Measurement of DEU Subsystem Performance(DEU)

Overview
DEU performance measurement indicates the operating status, such as the CPU usage, of a single
DEU in a subrack.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
DEU
DEU Subsystem Measurement
3.2.1 DEU Subsystem Measurement(DEU)

Overview
DEU measurement indicates the operating state, such as the CPU usage, of a single DEU system.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73429070
VS.DEU.CPULOA
D.MAX
HR9110:Maximum
CPU Usage of the
DEU
BSC6900
V900R017C00
73445289
VS.DEU.CPULOA
D.MEAN
AR9110:Average
CPU Usage of the
DEU
BSC6900
V900R017C00
73445346
VS.DEU.CPULOA
D.OVER
TR9110a:Rate of the
Period in Which the
CPU Usage of the
DEU Exceeds the
Alarm Threshold
BSC6900
V900R017C00
73445347
VS.DEU.CPULOA
D.LESS
TR9110b:Rate of the
Period in Which the
CPU Usage of the
DEU Is Lower Than
the Alarm Threshold
BSC6900
V900R017C00
None
Issue 03 (2015-06-30)

4185
BSC6900 UMTS
Maximum CPU Usage of the DEU

Counters
Counter ID
Counter Name
Counter Description
73429070
VS.DEU.CPULOAD.MAX
HR9110:Maximum CPU
Usage of the DEU
Description
This counter provides the maximum CPU usage of the DEU in a measurement period. It indicates
the load and operating performance of the CPU on the DEU in the measurement period.
Measurement point
The CPU usage of the DEU is sampled every second in the measurement period. Then, the
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.DEU.CPULOAD.MAX
WRFD-040100
Flow Control
Counter ID
Counter Name
Counter Description
73445289
VS.DEU.CPULOAD.MEA
N
AR9110:Average CPU
Usage of the DEU
Average CPU Usage of the DEU

Counters
Description
This counter provides the average CPU usage of the DEU in a measurement period.
Issue 03 (2015-06-30)

4186
BSC6900 UMTS
Measurement point
The CPU usage of the DEU is sampled and accumulated every second in the measurement period.
Then, the average CPU usage of the DEU is the accumulated value divided by the number of
sampling times.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.DEU.CPULOAD.MEA
N
WRFD-040100
Flow Control
Rate of the Period in Which the CPU Usage of the DEU Exceeds the Alarm
Threshold
Counters
Counter ID
Counter Name
Counter Description
73445346
VS.DEU.CPULOAD.OVER
TR9110a:Rate of the Period

the DEU Exceeds the Alarm
Threshold
Description
This counter provides the rate of the period in which the CPU usage of the DEU exceeds the
alarm threshold to the entire measurement period. It indicates the load and operating performance
of the CPU on the DEU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the DEU exceeds
the alarm threshold (can be queried by running the LST CPUTHD command) is divided by the
number of sampling times for a rate. The sampling period is 1s.
Formula
None
Issue 03 (2015-06-30)

4187
BSC6900 UMTS
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.DEU.CPULOAD.OVER
WRFD-040100
Flow Control
Rate of the Period in Which the CPU Usage of the DEU Is Lower Than the Alarm
Threshold
Counters
Counter ID
Counter Name
Counter Description
73445347
VS.DEU.CPULOAD.LESS
TR9110b:Rate of the Period

the DEU Is Lower Than the
Alarm Threshold
Description
This counter provides the rate of the sampling times in which the CPU usage of the DEU is lower
than the alarm threshold to the sampling times in the entire measurement period. It indicates the
load and operating performance of the CPU on the DEU in the measurement period.
Measurement point
In the measurement period, the number of times that the sampled CPU usage of the DEU is lower
than the alarm threshold (can be queried by running the LST CPUTHD command) is divided by
the number of sampling times for a rate. The sampling period is 1s.
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DEU.CPULOAD.LESS
WRFD-040100
Flow Control

4188
BSC6900 UMTS
3.3 Measurement of DEU DSP Performance(DEUDSP)

Overview
This measurement object measures the running status of the DSPs on all DEU boards, including
the usage of each DSP.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
DEUDSP
DEU DSP Measurement
3.3.1 DEU DSP Measurement(DEUDSP)

Overview
This function subset mainly measures the load of the AMR speech services that use the seamless
crystal voice function, including the DEU DSP usage.
Counters
Counter ID
Counter Name
Counter
Description
Original Release
73429073
VS.DEU.DSP.UsagePeak
Maximum DEU DSP

Usage
BSC6900
V900R017C00
73445290
VS.DEU.DSP.UsageAvg
Average DEU DSP

Usage
BSC6900
V900R017C00
None
Maximum DEU DSP Usage

Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter Description
73429073
Maximum DEU DSP Usage

4189
BSC6900 UMTS
Description
This counter provides the maximum DSP usage of a DEU in a measurement period. It reflects
the load and operating performance of the DSPs on the DEU in the measurement period.
Measurement point
The DSP usage of the DEU is sampled every five seconds in a measurement period. At the end
of the measurement period, the maximum DSP usage is used as the value of this counter.
Formula
None
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
WRFD-040100
Flow Control
Counter ID
Counter Name
Counter Description
73445290
VS.DEU.DSP.UsageAvg
Average DEU DSP Usage
Average DEU DSP Usage

Counters
Description
This counter provides the average DSP usage of a DEU in a measurement period. It reflects the
load and operating performance of the DSPs on the DEU in the measurement period.
Measurement point
The DSP usage of the DEU is sampled every five seconds in a measurement period. At the end
of the measurement period, the system obtains the value of this counter by dividing the
accumulated value of all samples in the period by the number of times sampled.
Formula
None
Issue 03 (2015-06-30)

4190
BSC6900 UMTS
Unit
%
Related Features
Counter Name
Feature ID
Feature Name
VS.DEU.DSP.UsageAvg
WRFD-040100
Flow Control
3.4 Measurement of DPU Subsystem Performance(DPU)

Overview
DPU performance measurement indicates the operating status, such as the CPU usage, of a single
DPU in a subrack.
FunctionSubSets
FunctionSubSet
FunctionSubSet Name
DPU
DPU Subsystem Measurement
3.4.1 DPU Subsystem Measurement(DPU)

Overview
DPU measurement indicates the operating state, such as the CPU usage, of a single DPU system.
Counters
Issue 03 (2015-06-30)
Counter ID
Counter Name
Counter
Description
Original Release
67194743
VS.DPU.CPULOA
D.MAX
HR9760:Maximum
CPU Usage of the
DPU
Earlier than
BSC6900
V900R011
67204463
VS.DPU.CPULOA
D.MEAN
AR9760:Average
CPU Usage of the
DPU
Earlier than
BSC6900
V900R011
67204464
VS.DPU.CPULOA
D.OVER
TR9760a:Rate of the
Period in Which the
CPU Usage of the
DPU Exceeds the
Alarm Threshold
Earlier than
BSC6900
V900R011

4191
BSC6900 UMTS
Counter ID
Counter Name
Counter
Description
Original Release
67204465
VS.DPU.CPULOA
D.LESS
TR9760b:Rate of the
Period in Which the
CPU Usage of the
DPU is Lower than
the Alarm Threshold
Earlier than
BSC6900
V900R011
None
Maximum CPU Usage of the DPU

Counters
Counter ID
Counter Name
Counter Description
67194743
VS.DPU.CPULOAD.MAX
HR9760:Maximum CPU
Usage of the DPU
Description
This counter provides the maximum CPU usage of the DPU in a measurement period. It indicates
the load and operating performance of the CPU on the DPU in the measurement period.
Measurement point
The CPU usage of the DPU is sampled every second in the measurement period. Then, the
Formula
None
Unit
%
Related Features
Issue 03 (2015-06-30)
Counter Name
Feature ID
Feature Name
VS.DPU.CPULOAD.MAX
WRFD-040100
Flow Control

4192
BSC6900 UMTS
3 Hardware Platform R

BSC6900 UMTS Performance Counter Reference (V900R017C10 - 02) (PDF) - en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC6900 UMTS Performance Counter Reference (V900R017C10 - 02) (PDF) - en

Uploaded by

Copyright:

Available Formats

BSC6900 UMTS

Performance Counter Reference

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

Figure 1 Document structure

Table 1 explains the terms shown in Figure 1.

Classification of Object Type

On the top level, object types are classified

Object types are located at the second level of

Function Subsets are located at the third level

Counters are located at the fourth level of the

Counter Item Description

Definition and function of a object type.

Huawei Proprietary and Confidential

Function subsets contained in a object type.

Name of the function set.

Definition of a function subset and the flowchart for measuring related

Counters contained in a function subset.

A string of digits that uniquely

Name of a counter. It is composed of

A phrase that provides a simple

Detailed description about a counter.

Condition for triggering counter measurement.

Relationship among counters.

About This Document

One function set contains one or more function subsets.

Related intermediate counters are

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1.8.2 RRC Measurement per Load Sharing Node(RRC.NODESHARE)........................................................................441

Huawei Proprietary and Confidential

1.12.5 CBS Measurement <per Cell>(CBS.Cell)...........................................................................................................1194

Huawei Proprietary and Confidential

1.12.46 TX and RX Power Measurement <per Cell>(RTWPTCP.Cell)........................................................................3214

2 Transport Network Related Measurement.........................................................................3626

Huawei Proprietary and Confidential

2.9.1 E1/T1 Port Bit Error Measurement(E1T1_ES).....................................................................................................3746

Huawei Proprietary and Confidential

2.28 Measurement of Iur-p Link Performance(IURPLNK)...........................................................................................3939

Huawei Proprietary and Confidential

2.48 Measurement of SCTP Link Performance(SCTPLNK).........................................................................................4119

3 Hardware Platform Related Measurement.........................................................................4180

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1 UMTS Radio Network Related Measurement

UMTS Radio Network Related

About This Chapter

Huawei Proprietary and Confidential

1 UMTS Radio Network Related Measurement

1.1 Measurement of CNOperator Performance

Algorithm Measurement per PLMN

RAB Setup Measurement per PLMN

RAB Release Measurement per PLMN

Traffic Measurement per PLMN

1.1.1 Algorithm Measurement per PLMN(ALGO.PLMN.RNC)