Professional Documents
Culture Documents
V100R013C00
NodeBFunction Performance
Counter Reference
Issue 03
Date 2017-12-28
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
This section describes performance counters for 3900 and 5900 series base stations.
Document Structure
Figure 1 shows the document structure.
Table 1 Terms
Term Explanation
Object type One object type contains one or more function subsets.
Counter A table that lists parent counters and their child counters in
Relationship 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.
NOTE
If the value of the parent counter exceeds the sum of the values of
the child counters, the value difference is the items that are not
counted.
Item Description
Original Release The version for which the counter was first available.
Contents
1.1.3.11 Average Number of 2 ms TTI HSUPA Users at Different Rates in a Cell......................................................... 253
1.1.3.12 Average Number of 10 ms TTI HSUPA Users at Different Rates in a Cell....................................................... 257
1.1.3.13 Average Number of Valid Time-Division Scheduling Users in a Cell............................................................... 261
1.1.3.14 Number of TTIs with HSUPA Users in a Cell....................................................................................................262
1.1.3.15 Number of TTIs in Which at Least One HSUPA User Transmits Data in a Cell...............................................263
1.1.3.16 Number of TTIs in Which at Least One HSUPA User Transmits the TRB Data in a Cell................................ 265
1.1.3.17 Number of HSUPA Users with Data Transmission under Different Uplink Uu Loads in a Cell.......................266
1.1.3.18 Number of TTIs in Which HSUPA Users Have Data to Transmit under Different Uplink Uu Loads in a Cell
.......................................................................................................................................................................................... 269
1.1.3.19 HSUPA HARQ Distribution in a Cell................................................................................................................ 274
1.1.3.20 HSUPA MAC-e/MAC-i PDU Statistics in a Cell...............................................................................................276
1.1.3.21 Cell Throughput of HSUPA Users Under Different Uplink Uu Loads.............................................................. 278
1.1.3.22 Average/Maximum IC Efficiency in a Cell........................................................................................................ 284
1.1.3.23 Ratio of Unhappy HSUPA Users with SG Limit due to Resource Insufficiency in a Cell................................ 286
1.1.3.24 Proportion of the Time When FDE is Used in a Cell......................................................................................... 288
1.1.3.25 Proportion of the Time When 16QAM is Used in a Cell................................................................................... 290
1.1.3.26 Proportion of the Time When Boosting is Used in a Cell.................................................................................. 291
1.1.3.27 Possibility of the Active Anti-Interference Scheduling Algorithm in a Cell......................................................292
1.1.3.28 Time-Division Scheduling Algorithm Validity Probability in a Cell................................................................. 293
1.1.3.29 Number of Transitions from Using All HARQ Processes to Using A Single HARQ Process In the Cell........ 294
1.1.3.30 Number of Transitions from Using A Single HARQ Process to Using All HARQ Processes In the Cell........ 296
1.1.3.31 Ratio of SIs That Are Reported by HSUPA Users and Meet Power Limit Conditions in a Cell....................... 297
1.1.3.32 Number of Times UPH Values Reported by HSUPA 2 ms TTI Users Are Within Each Interval......................298
1.1.3.33 Number of TTIs in which HSUPA UEs that perform uplink full buffer services with have data to transmit under
Different CQIs in a cell.....................................................................................................................................................301
1.1.3.34 Number of TTIs in which MAC-e/MAC-i data is received from HSUPA UEs with insufficient transmit power
in a cell..............................................................................................................................................................................304
1.1.3.35 HSUPA Mac-d TRB data volume in the cell......................................................................................................305
1.1.3.36 Number of TTIs in which HSUPA Mac-e/Mac-i TRBs are received in a cell................................................... 306
1.1.3.37 Average number of HSUPA users with Turbo IC enabled in a cell....................................................................308
1.1.3.38 Traffic of Mac-e/Mac-i PDUs received from 2 ms TTI HSUPA users in a cell.................................................309
1.1.3.39 Traffic of Mac-e/Mac-i PDUs received from 10 ms TTI HSUPA users in a cell...............................................310
1.1.3.40 Average number of 10 ms TTI HSUPA UEs in the CCH OLPC state in a cell..................................................311
1.1.3.41 Average number of 2 ms TTI HSUPA UEs in the CCH OLPC state in a cell................................................... 313
1.1.3.42 Average SIRtarget decrease of 10 ms TTI HSUPA UEs in the CCH OLPC state in a cell................................314
1.1.3.43 Average SIRtarget decrease of 2 ms TTI HSUPA UEs in the CCH OLPC state in a cell..................................315
1.1.3.44 Average Number of HSUPA 2 ms TTI UEs in the Virtual Power Scaling State in a Cell................................. 317
1.1.3.45 Average Number of HSUPA 10 ms TTI Users Enabled with Turbo IC in a Cell.............................................. 318
1.1.3.46 Average number of inter-NodeB UL CoMP users in a cell................................................................................319
1.1.3.47 Average Number of Coordinating Links for Enhanced Inter-NodeB UL CoMP in a Cell................................ 320
1.1.3.48 Time Ratio of Existent DC-HSUPA Users with Deactivated Supplementary Carriers in a Cell....................... 321
1.1.3.49 Traffic of MAC-e/MAC-i PDUs received from HSUPA UEs that perform uplink full buffer services under
Different CQIs in a cell.....................................................................................................................................................323
1.1.3.50 Traffic of MAC-e/MAC-i PDUs received from HSUPA UEs with insufficient transmit power in a cell..........327
1.1.3.51 Average number of virtual CPC users in a cell...................................................................................................328
1.1.3.52 Average SIRtarget decrease of virtual CPC users in a cell.................................................................................329
1.1.3.53 Average Number of HSUPA 2 ms TTI Users Enabled with Precise Channel Estimation in a Cell...................331
1.1.4 CPC Measurement (CPC.LOCELL)....................................................................................................................... 332
1.1.4.1 Number of UL_DTX Users in a Cell....................................................................................................................334
1.1.4.2 Number of DL_DRX Users in a Cell................................................................................................................... 336
1.1.4.3 Number of Users in HS-SCCH-Less Mode in a Cell........................................................................................... 339
1.1.4.4 Activated CPC Enhancement-capable Users FDPCH DTX Act Ratio for Using the Cell as Serving Cell in Cells
.......................................................................................................................................................................................... 341
1.1.5 ERACH Measurement (ERACH.LOCELL)........................................................................................................... 342
1.1.5.1 Number of used common E-DCHs in a cell......................................................................................................... 343
1.1.5.2 Throughput of E-RACH users at the Mac-i layer in a cell................................................................................... 345
1.1.5.3 Number of TTIs in which E-RACH users have data to transmit in a cell............................................................ 346
1.1.6 PRACH Measurement (PRACH.LOCELL)............................................................................................................347
1.1.6.1 Number of positive acknowledgments on AICH in the preamble detection results of the primary cell that are
reported by coordinating cells.......................................................................................................................................... 348
1.1.6.2 Number of negative acknowledgments on AICH in the preamble detection results of the primary cell that are
reported by coordinating cells.......................................................................................................................................... 349
1.1.6.3 Number of TBs obtained by the primary cell from the coordinating cells with correct CRCs over the RACH.. 351
1.1.6.4 Total number of TBs obtained by the primary cell from the coordinating cells...................................................352
1.1.7 SCCPCH Measurement (SCCPCH.LOCELL)........................................................................................................353
1.1.7.1 Statistics on Received and Discarded FACH FP Frames in a Cell.......................................................................355
1.1.7.2 Statistics on Received and Discarded PCH FP Frames in a Cell......................................................................... 357
1.1.8 DCH Measurement (DCH.LOCELL)......................................................................................................................359
1.1.8.1 Statistics on Received and Discarded Downlink DCH FP Frames in a Cell........................................................360
1.1.8.2 Number of Received or Sent Multiplexed DCH FP Data Frames for AMR Services in a Cell...........................363
1.1.9 Cell Algorithm Measurement (ALGO.LOCELL)................................................................................................... 364
1.1.9.1 Average Ratio of the Number of Valid Antennas to the Number of Configured Antennas................................. 369
1.1.9.2 Average/Maximum Efficiency of Stage 1 Interference Cancellation (IC) in a Cell.............................................371
1.1.9.3 Number of Normalized Downlink Codes Used in a Cell..................................................................................... 372
1.1.9.4 Average Number of Users Enabled with DPCH Power Control Based on Radio Quality in a Cell.................... 374
1.1.9.5 Average Number of Users Enabled with F-DPCH Power Control Based on Radio Quality in a Cell.................375
1.1.9.6 User Number of PLVA in the local cell................................................................................................................ 376
1.1.9.7 Average Number of IRC Users in a Cell.............................................................................................................. 377
1.1.9.8 Average Number of Channels for CCPIC Phase 3 in a Cell.................................................................................378
1.1.9.9 Ratio of Strong Colored Interference in a Cell.....................................................................................................379
1.1.9.10 Average Number of CoMP Users in a Host Cell Enabled with Coverage Expansion Under Interference........ 381
1.1.9.11 Average Number of Users Enabled with 4-Way Receive Diversity by Inter-Band Assistance in a Cell........... 382
1.1.9.12 Effective Duration of the Narrowband Interference Suppression Feature for Cell............................................ 383
1.1.9.13 Average number of users with DPCH TPC Power Adjustment enabled in a cell.............................................. 384
1.1.9.14 Average Interference Decrease Degree for an AIR-enabled Cell.......................................................................385
1.1.9.15 Average Number of Users Enabled with Advanced Demodulation in a Cell.....................................................386
1.1.9.16 Average Number of Users Enabled with Moving Speed-based Adaptive Demodulation..................................388
1.1.9.17 Average Number of users for CCPIC Phase 4 in a Cell..................................................................................... 389
1.1.9.18 Ratio of AIR Activation for a Cell..................................................................................................................... 390
1.1.9.19 Average Number of Frequencies Enabled with Comb Filtering in a Cell.......................................................... 391
1.1.9.20 Average Bandwidth of Notched Frequencies by Baseband NBIS in a Cell....................................................... 392
1.1.9.21 Average Number of Frequencies Enabled with Comb Filtering out of the 3.8 MHz Frequency Band in a Cell
.......................................................................................................................................................................................... 394
1.1.10 Cell Reserved Counter Measurement (CELLRESERVE.LOCELL).....................................................................395
1.1.10.1 Reserved 1 in the cell..........................................................................................................................................398
1.1.10.2 Reserved 2 in the cell..........................................................................................................................................399
1.1.10.3 Reserved 3 in the cell..........................................................................................................................................400
1.1.10.4 Reserved 4 in the cell..........................................................................................................................................401
1.1.10.5 Reserved 5 in the cell..........................................................................................................................................402
1.1.10.6 Reserved 6 in the cell..........................................................................................................................................403
1.1.10.7 Reserved 7 in the cell..........................................................................................................................................404
1.1.10.8 Reserved 8 in the cell..........................................................................................................................................405
1.1.10.9 Reserved 9 in the cell..........................................................................................................................................406
1.1.10.10 Reserved 10 in the cell......................................................................................................................................407
1.1.10.11 Reserved 11 in the cell......................................................................................................................................408
1.1.10.12 Reserved 12 in the cell......................................................................................................................................409
1.1.10.13 Reserved 13 in the cell......................................................................................................................................410
1.1.10.14 Reserved 14 in the cell......................................................................................................................................411
1.1.11 Cell Power Measurement (POWER.LOCELL)..................................................................................................... 411
1.1.11.1 Average Ratio of DPCH and F-DPCH Transmit Power over Different SF Code Channels to the Maximum
Downlink Transmit Power in a Cell................................................................................................................................. 416
1.1.11.2 Uplink power loads of different services in a cell.............................................................................................. 418
1.1.11.3 Average Ratio of Downlink DCH Transmit Power Occupied by Operator 0 in an MOCN Network................421
1.1.12 EFACH Measurement (EFACH.LOCELL)...........................................................................................................423
1.1.12.1 E-FACH HARQ Distributing in a Cell...............................................................................................................425
1.1.12.2 Number of TTIs in Which E-FACH Users Have Data to Transmit in a Cell..................................................... 427
1.1.12.3 E-FACH User Throughput at the MAC-ehs Layer in a Cell.............................................................................. 428
1.1.12.4 Average HS-SCCH transmit power of all E-FACH users in a cell.....................................................................429
1.1.12.5 Average HS-PDSCH transmit power of all E-FACH users in a cell.................................................................. 431
1.1.13 HSDPA Measurement 2 (HSDPA2.LOCELL)...................................................................................................... 432
1.1.13.1 Number of Times Different Quantities of HS-PDSCH Codes Are Used in a Cell............................................ 467
1.1.13.2 Average Number of HSDPA Users in a Cell...................................................................................................... 472
1.1.13.3 Number of MAC-d PDUs received over Iub interfaces in a cell........................................................................473
1.1.13.4 Traffic of MAC-ehs PDUs Correctly Transmitted by 64QAM Users in a Cell................................................. 474
1.1.13.5 Throughput Distribution of Single HSDPA User in a Full Buffer..................................................................... 476
1.1.13.6 Traffic of Delay Sensitive BE Services Transmitted by HSDPA Users in a Cell...............................................481
1.1.13.7 Number of Times HSDPA Users Running Delay Sensitive BE Services Are Scheduled in a Cell................... 483
1.1.13.8 Number of Times HSDPA Users Are not Scheduled in a Cell...........................................................................485
1.1.13.9 Number of Times the Next HSDPA User Cannot be Scheduled Due to Resource Insufficiency in a Cell........487
1.2.3.2 Number of radio link setup rejections because of license congestion in terms of the signaling processing
capability.......................................................................................................................................................................... 637
1.2.3.3 Number of Received Radio Links per Second..................................................................................................... 639
1.2.3.4 Maximum number of wireless connection processing times per second............................................................. 641
1.2.3.5 Total number of times radio link setup requests are rejected because of control plane congestion (CPU overload)
within a measurement period............................................................................................................................................643
1.2.3.6 Maximum number of received uplink coordinating links per second.................................................................. 644
1.2.4 NodeB Reserved Counter Measurement (NODEBRESERVE.NODEB)................................................................645
1.2.4.1 Reserved 1 for the NodeB.................................................................................................................................... 647
1.2.4.2 Reserved 2 for the NodeB.................................................................................................................................... 648
1.2.4.3 Reserved 3 for the NodeB.................................................................................................................................... 649
1.2.4.4 Reserved 4 for the NodeB.................................................................................................................................... 650
1.2.4.5 Reserved 5 for the NodeB.................................................................................................................................... 651
1.2.5 Iub Transmission Performance Measurement per NodeB (TRAFFIC.TRPIP.NODEB).........................................651
1.2.5.1 Number of IP Packets at the IP Layer over the Iub Interface...............................................................................653
1.2.5.2 Number of Bytes in the IP Packets at the IP Layer over the Iub Interface...........................................................655
1.2.5.3 Rate at the IP Layer over the Iub Interface...........................................................................................................657
1.3 Measurement of CNOperator Performance (OPERATOR)........................................................................................659
1.3.1 Traffic Measurement per CNOperator (TRAFFIC.OPERATOR)........................................................................... 659
1.3.1.1 Number of Uplink CEs Consumed by an Operator.............................................................................................. 667
1.3.1.2 Number of Downlink CEs Consumed by an Operator......................................................................................... 669
1.3.1.3 Number of DL CEs Configured for an Operator.................................................................................................. 671
1.3.1.4 Number of UL CEs Configured for an Operator.................................................................................................. 672
1.3.1.5 Number of UL CEs Configured for a Shared Group............................................................................................673
1.3.1.6 Number of DL CEs Configured for a Shared Group............................................................................................674
1.3.1.7 Number of Uplink CEs Consumed in a Shared group..........................................................................................675
1.3.1.8 Number of Downlink CEs consumed in a Shared group......................................................................................677
1.3.1.9 Number of Uplink CEs Consumed by HSUPA Services of an Operator............................................................. 679
1.3.1.10 Number of Shared Uplink CEs Consumed by HSUPA Services of a Shared Group......................................... 682
1.3.1.11 Average number of uplink CEs consumed by each operator in an MOCN network..........................................684
1.3.1.12 Average number of downlink CEs consumed by each operator in an MOCN network.....................................686
1.3.1.13 Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links.................................. 687
1.3.1.14 Number of UL CEs Configured for an Operator in a Shared Group Consumed by UL Coordinating Links.... 689
1.3.1.15 Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links Carrying HSUPA
Services.............................................................................................................................................................................692
1.3.1.16 Number of UL CEs in a Shared Group Consumed by UL Coordinating Links Carrying HSUPA Services..... 694
1.3.2 Operator Reserved Counter Measurement (OPERESERVE.OPERATOR)............................................................ 697
1.3.2.1 Reserved 1 for the operator.................................................................................................................................. 698
1.3.2.2 Reserved 2 for the operator.................................................................................................................................. 699
1.3.2.3 Reserved 3 for the operator.................................................................................................................................. 700
1.3.2.4 Reserved 4 for the operator.................................................................................................................................. 701
1.3.2.5 Reserved 5 for the operator.................................................................................................................................. 702
1.4 Measurement of LoCell_SectorEQM Performance (LOCELL_SECTOREQM)...................................................... 702
Index................................................................................................................................................745
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
Root Counter Level-1 Counter
VS.AckTotal VS.AckFirst
VS.AckRetrans.1
VS.AckRetrans.2
VS.AckRetrans.3
VS.AckRetrans.4
VS.AckRetrans.5
VS.AckRetrans.6
VS.AckRetrans.7
VS.AckRetrans.8
VS.AckRetrans.9
VS.AckRetrans.10
VS.MIMODUALSTREAM1.ACK
VS.MIMODUALSTREAM2.ACK
VS.NackTotal VS.MIMODUALSTREAM1.NACK
VS.MIMODUALSTREAM2.NACK
VS.DtxTotal VS.MIMODUALSTREAM1.DTX
VS.MIMODUALSTREAM2.DTX
VS.HSDPA.All.ScheduledNum VS.HSDPA.16QAMCfg.ActedNum
VS.HSDPA.QPSKCfg.ActedNum
VS.HSDPA.64QAMCfg.ActedNum
VS.HSDPA.DataTtiNum.TRB VS.HSDPA.InactiveDataTtiNum.TRB
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the number of HARQ-related messages sent by HSDPA users
received in a cell. The Acknowledgment (ACK), Negative Acknowledgment (NACK), and
Discontinuous Transmission (DTX) statistics are used to analyze the overall HSDPA running
status.
The following table describes the meanings of each counter.
Measurement Points
The NodeB measures the preceding counters when demodulating the HARQ-ACK
information carried on the HS-DPCCH from the HSDPA UE. VS.NackTotal and VS.DtxTotal
indicate the number of NACK and DTX messages received at the NodeB, respectively, in
event of failed data transmission at the physical layer. For the ACK messages, the NodeB
takes statistics about the messages according to the number of data transmissions. The number
of transmissions is an integer from 1 to MaxRetransNum+1. For multi-carrier users, these
counters are measured in the anchor carrier and the supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the HARQ distribution for MIMO users on the primary and
secondary streams in a cell. The statistics about the ACK, NACK, and DTX message sent
from MIMO users are used to analyze the overall running status of MIMO users.
Measurement Points
The NodeB measures the preceding counters when demodulating the HARQ-ACK
information carried on the HS-DPCCH from the MIMO UE.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the overall distribution of channel quality indicators (CQIs)
received in a cell from HSDPA users. For each CQI value, the NodeB counts the number of
CQIs received in a cell during a measurement period. The values of VS.CQI.0 to VS.CQI.30
correspond to the values of CQI0 to CQI30 reported by an HSDPA UE.
The preceding counters comply with section "6A.2 Channel quality indicator (CQI)
definition" in 3GPP TS 25.214 (v10.10.0).
Measurement Points
The NodeB takes statistics about the preceding counters when demodulating the CQI
information of the HSDPA UE carried on the HS-DPCCH. For multi-carrier users, these
counters are measured in the anchor carrier and the supplementary carrier separately.For inter-
NodeB DB-HSDPA users, only CQIs with data transmission are counted in the supplementary
carrier.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the CQI values ranging from 0 to 30 and [31,39] used by the NodeB
to transmit TBS to HSDPA users within a measurement period, indicating the overall
distribution of the used CQIs. These counters measure the channel quality indicator (CQI)
used for HSDPA scheduling, not the CQI reported by a UE. VS.UsedCQI31to39 is specific to
16QAM or 64QAM users.
Measurement Points
The NodeB takes statistics about the preceding counters for HSDPA users when MAC-hs/
MAC-ehs scheduling is complete. The preceding counters do not measure the CQIs sent by
the MIMO users.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the distribution of dual CQIs reported by MIMO users in a
cell, evaluating the channel conditions for MIMO users.
The preceding counters comply with section "6A.2 Channel quality indicator (CQI)
definition" in 3GPP TS 25.214 (v10.10.0).
Measurement Points
The NodeB takes statistics about the preceding counters when demodulating the CQI
information of the UE carried on the HS-DPCCH. VS.MIMODualCQI1.0 to
VS.MIMODualCQI1.14 indicate the distribution of CQI1 in TypeA CQI reports from MIMO
users; VS.MIMODualCQI2.0 to VS.MIMODualCQI2.14 indicate the distribution of CQI2 in
TypeA CQI reports from MIMO users.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.1.6 Average CQI Reported by All HSDPA UEs That Have Data to Transmit.
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the average value of CQIs reported by all HSDPA users with
data transmission in a cell. The value has been amplified by 1000 times. For example, the
value 29100 stands for the CQI value 29.1.
This counter complies with section "6A.2 Channel quality indicator (CQI) definition" in
3GPP TS 25.214 (v10.10.0).
Measurement Points
Within a measurement period, the accumulated CQI values reported by UEs that have data to
transmit in the cell per TTI is recorded as A, and the total number of HSDPA users that have
data to transmit in the cell per TTI is recorded as B. The formula for calculating this counter
is: VS.DataCQI.MEAN = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The NodeB takes statistics about the preceding counters for HSDPA users when MAC-hs/
MAC-ehs scheduling is complete. For MIMO users, if two transport blocks are used, the
VS.HSDPA.All.ScheduledNum counter is incremented by 2; if a single transport block is
used, the VS.HSDPA.All.ScheduledNum counter is incremented by 1. For MIMO users, if
two transport blocks are used, the VS.HSDPA.16QAMCfg.ActedNum and
VS.HSDPA.QPSKCfg.ActedNum counters are measured on each transport block separately.
For multi-carrier users, the preceding counters are measured in the anchor carrier and the
supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The NodeB takes statistics about the preceding counters when MAC-hs/MAC-ehs scheduling
is complete. For MIMO+64QAM users, if two transport blocks are used, the VS.HSDPA.
64QAMCfg.ScheduledNum counter is incremented by 2; if a single transport block is used,
the VS.HSDPA.64QAMCfg.ScheduledNum counter is incremented by 1. For MIMO users, if
two transport blocks are used, the VS.HSDPA.64QAMCfg.ActedNum counter is measured on
each transport block separately. For DC-HSDPA users, the preceding counters are measured
in the anchor carrier and the supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the usage of two transport blocks for MIMO-enabled users in
a cell.
Measurement Points
The NodeB takes statistics about the preceding counters when MAC-hs/MAC-ehs scheduling
is complete.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the usage of 64QAM for 64QAM+MIMO users in a cell.
Measurement Points
The NodeB takes statistics about the preceding counters when MAC-hs/MAC-ehs scheduling
is complete. If two transport blocks are used, the
VS.HSDPA.MIMO64QAMCfg.ScheduledNum counter is incremented by 2; if a single
transport block is used, the VS.HSDPA.MIMO64QAMCfg.ScheduledNum counter is
incremented by 1.When 64QAM+MIMO users are scheduled based on 64QAM, the
VS.HSDPA.MIMO64QAMCfg.ActedNum counter is used. If a single transport block is used,
the VS.HSDPA.MIMO64QAMCfg.ActedNum counter is incremented by 1; if two transport
blocks are used, the VS.HSDPA.MIMO64QAMCfg.ActedNum counter is incremented by 2.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The NodeB takes statistics about the preceding counters for DC-HSDPA or DB-HSDPA users
when MAC-hs/MAC-ehs scheduling is complete. When a user is scheduled by the anchor
carrier, the VS.HSDPA.DCCfg.AnchorCarrierActedNum counter is incremented by 1
regardless of whether the user is scheduled by the supplementary carrier. If a user is scheduled
by the supplementary carrier, the VS.HSDPA.DCCfg.SupCarrierActedNum counter is
incremented by 1 regardless of whether the user is scheduled by the anchor carrier. If MC
Inter-Board Joint Scheduling Switch is turned off and a user is scheduled by the anchor and
supplementary carriers at the same time, the VS.HSDPA.DCCfg.DualCarrierActedNum
counter is only incremented by 1. If MC Inter-Board Joint Scheduling Switch is turned on, the
VS.HSDPA.DCCfg.DualCarrierActedNum counter is not incremented.The
VS.HSDPA.DCCfg.DualCarrierActedNum counter does not count inter-NodeB DB-HSDPA
users.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter provides the ratio of the time when at least one HSDPA UE camps on a
cell to the total time of the measurement period.
Measurement Points
During a measurement period, if at least one HSDPA UE camps on a cell in one Transmission
Time Interval (TTI), the NodeB counts the number of all such TTIs in the measurement
period. Assume that this number is A and the total number of TTIs in the measurement period
is B. Then, VS.UserTtiRatio.Mean = A/B. A DC-HSDPA user is regarded as an HSDPA user
in each anchor carrier and supplementary carrier. For DC-HSDPA users, the counter is
measured in the anchor carrier and the supplementary carrier separately.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.13 Time Ratio for HSDPA User with Data to be Transmitted in the Queue
Buffer in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter measures the ratio of the time when at least one HSDPA user in a cell
has data to transmit in the queue buffer to the total time within a measurement period.
Measurement Points
During a measurement period, if at least one HSDPA user in a cell has data to transmit in the
queue buffer in a TTI, the NodeB counts the number of all such TTIs. Assume that the
number is A, and the total number of TTIs within the measurement period is B. Then,
VS.DataTtiRatio.Mean = A/B. For DC-HSDPA users, the counter is measured in the anchor
carrier and the supplementary carrier separately. In the SRB over HSDPA scenario, when the
SRB over HSDPA measurement optimization is enabled, this counter does not measure the
number of TTIs in which HSDPA UEs have only SRB data to transmit in queue buffers. The
counter is measured at point C in the following figure:
Figure 1-1
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.14 Time Ratio for HSDPA Users Having Data in the Queue Buffer but
Having No Conventional Data Transmission
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the average ratio of the time period when at least one HSDPA user in a
cell has data to transmit in the queue buffer but there is no conventional HSDPA data
transmission at the physical layer. Conventional data transmission does not include the
following scenario: The ACK/NACK fields of the uplink HS-DPCCH corresponding to the
current TTI fall into the transmission gap in compressed mode.
Measurement Points
During a measurement period, if at least one HSDPA user in a cell has data to transmit in the
queue buffer but there is no conventional HSDPA data transmission at the physical layer
within a TTI, the NodeB counts the number of such TTIs in the measurement period. Assume
that the number is A, and the total number of TTIs in the measurement period is B. Then,
VS.HSDPA.InactiveDataTtiRatio.Mean = A/B. For DC-HSDPA users, the counter is
measured in the anchor carrier and the supplementary carrier separately. In the SRB over
HSDPA scenario, when the SRB over HSDPA measurement optimization is enabled, this
counter does not measure the number of TTIs in which HSDPA UEs have only SRB data to
transmit in queue buffers but no data to transmit at the physical layer. The following figure
shows the flowchart where the counter is measured at points D, E and F:
Figure 1-2
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.15 Average Time Ratio for HSDPA User Queues in the Scheduling
Candidate Set but Having No Data Transmission
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the average time ratio for HSDPA user queues in the
scheduling candidate set but having no data transmission.
Measurement Points
During a measurement period, if an HSDPA user queue enters the scheduling candidate set
but does not transmit data at the physical layer in one Transmission Time Interval (TTI), the
NodeB counts the number of all such TTIs. Assume that this number is A and the total
number of TTIs in the measurement period is B. Then,
VS.HSDPA.ScheInactiveDataTtiRatio.Mean = A/B.For DC-HSDPA users, the counter is
measured in the anchor carrier and the supplementary carrier separately.In the SRB over
HSDPA scenario, when the SRB over HSDPA measurement optimization is enabled, this
counter does not measure the number of TTIs in which HSDPA UEs that have only SRB data
to transmit are added to the scheduling candidate set but no data is transmitted at the physical
layer. The counter is measured at point E in the following figure:
Figure 1-3
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the number of TTIs in which the TRB data is to be
transmitted in at least one HSDPA user queue in a cell.
Measurement Points
The NodeB calculates the number of TTIs in which at least one HSDPA user in a cell has the
TRB data to transmit in the queue buffer within a measurement period. For DC-HSDPA users,
the counter is measured in the anchor carrier and the supplementary carrier separately.The
counter is measured at point A in the following figure:
Figure 1-4
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.1.17 Number of TTIs for HSDPA Users in a Cell Having TRB Data to
Transmit in the Queue Buffer but Having No Conventional Data Transmission
at the Physical Layer
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the number of TTIs for at least one HSDPA user in a cell having the
TRB data to transmit in the queue buffer but having no conventional data transmission at the
physical layer. Conventional data transmission does not include the following scenario: The
ACK/NACK fields of the uplink HS-DPCCH corresponding to the current TTI fall into the
transmission gap in compressed mode.
Measurement Points
The NodeB calculates the total number of TTIs in which at least one HSDPA user in a cell has
the TRB data to transmit in the queue buffer but there is no conventional TRB data
transmission at the physical layer within a TTI. For DC-HSDPA users, the counter is
measured in the anchor carrier and the supplementary carrier separately. The following figure
shows the flowchart where the counter is measured at points A and B:
Figure 1-5
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.1.18 Total number of user-level TTIs within which there is data to transmit in
HSDPA user queue buffers
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs within which there is data to transmit in HSDPA
user queue buffers. This counter needs to be measured repeatedly if more than one HSDPA
user queue buffer has data to transmit within a TTI.
Measurement Points
The number of TTIs within which there is data to transmit in all HSDPA user queue buffers is
accumulated within a measurement period. This counter will be measured repeatedly if more
than one HSDPA user queue buffer has data to transmit within a TTI. This counter is
measured in the serving cell. For DC-HSDPA, DB-HSDPA, 4C-HSDPA, or 3C-HSDPA users,
this counter is measured in the anchor carrier and supplementary carrier separately. In the
SRB over HSDPA scenario, when the SRB over HSDPA measurement optimization is
enabled, this counter does not measure the number of TTIs in which HSDPA UEs have only
SRB data to transmit in queue buffers.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.1.19 Total number of user-level TTIs within which there is data to transmit in
MC-HSDPA/MC-HSDPA+MIMO user queue buffers
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of TTIs within which there is data to transmit in all DC-HSDPA or DC-HSDPA
+MIMO user queues is accumulated to VS.DCHSDPA.DataTtiNum.User within a
measurement period, with the local cell served by the anchor carrier. This counter will be
measured repeatedly if more than one DC-HSDPA or DC-HSDPA+MIMO user queue buffer
has data to transmit within a TTI.
The number of TTIs within which there is data to transmit in all DB-HSDPA or DB-HSDPA
+MIMO user queues is accumulated to VS.DBHSDPA.DataTtiNum.User within a
measurement period, with the local cell served by the anchor carrier. This counter will be
measured repeatedly if more than one DB-HSDPA or DB-HSDPA+MIMO user queue buffer
has data to transmit within a TTI.
The number of TTIs within which there is data to transmit in all 3C-HSDPA or 3C-HSDPA
+MIMO user queues is accumulated to VS.3CHSDPA.DataTtiNum.User within a
measurement period, with the local cell served by the anchor carrier. This counter will be
measured repeatedly if more than one 3C-HSDPA or 3C-HSDPA+MIMO user queue buffer
has data to transmit within a TTI.
The number of TTIs within which there is data to transmit in all 4C-HSDPA or 4C-HSDPA
+MIMO user queues is accumulated to VS.4CHSDPA.DataTtiNum.User within a
measurement period, with the local cell served by the anchor carrier. This counter will be
measured repeatedly if more than one 4C-HSDPA or 4C-HSDPA+MIMO user queue buffer
has data to transmit within a TTI.
These counters are measured only in the anchor carrier, not in the supplementary carrier.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the ratio of time when different HS-SCCH codes are used for
a cell.
Measurement Points
Take the VS.HSDPA.2ScchCodeRatio counter as an example. During a measurement period,
the NodeB calculates the number of TTIs in which only two HS-SCCH codes are used for the
cell. Assume that the number is A, and the number of TTIs in which one or more HS-SCCH
codes are used in the measurement period is B. Then, VS.HSDPA.2ScchCodeRatio = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and maximum number of available HS-PDSCH
codes in a cell during a measurement period.
Measurement Points
During a measurement period, the NodeB counts the number of available HS-PDSCH codes
in all TTIs in the cell. Assume that this value is A and the number of TTIs in the measurement
period is B. Then, VS.PdschCodeAvail.Mean = A/B. The NodeB samples
VS.PdschCodeAvail.Mean every 5s and takes the maximum value within the measurement
period as VS.PdschCodeAvail.Max.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average, maximum, and minimum number of used HS-
PDSCH codes in a cell during a measurement period.
Measurement Points
During a measurement period, the NodeB counts the number of used HS-PDSCH codes in all
TTIs in the cell. Assume that this value is A and the number of TTIs in the measurement
period is B. Then, VS.PdschCodeUsed.Mean = A/B. The NodeB samples
VS.PdschCodeUsed.Mean every 5s and takes the maximum value within the measurement
period as VS.PdschCodeUsed.Max and the minimum value within the measurement period as
VS.PdschCodeUsed.Min.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters provide the average, maximum, and minimum usage of the HS-SCCH
code resources during a measurement period. These counters are used to analyze the
allocation appropriateness of the HS-SCCH code resources. If the code usage is high, the code
resources are insufficient for the current traffic. Therefore, more code resources are required.
Measurement Points
Assume that the number of HS-SCCH codes used in all TTIs is A and the number of available
HS-SCCH codes in all TTIs is B. Then, VS.ScchCodeUtil.Mean = A/B. The NodeB samples
VS.ScchCodeUtil.Mean every 5s and then takes the maximum value within the measurement
period as VS.ScchCodeUtil.Max and the minimum value within the measurement period as
VS.ScchCodeUtil.Min.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.24 Usage of HS-SCCH Code Resources When at Least One HSDPA User
Camps on the Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the average usage of HS-SCCH code resources when at least
one HSDPA user camps on the cell during a measurement period.
Measurement Points
Assume that the total number of used HS-SCCH codes in all TTIs when at least one HSDPA
user camps on the cell within a measurement period is A, and the total number of available
HS-SCCH codes in all TTIs when at least one HSDPA user camps on the cell is B. Then,
VS.ScchCodeUtil.Mean.User = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.25 Usage of HS-SCCH Code Resources When at Least One HSDPA User
Has Data to Transmit in the Queue Buffer
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the average usage of HS-SCCH code resources when at least one
HSDPA user has data to transmit in the queue buffer within a measurement period.
Measurement Points
Assume that the total number of used HS-SCCH codes in all TTIs when at least one HSDPA
user has data to transmit in the queue buffer within the measurement period is A, and the total
number of available HS-SCCH codes in all TTIs when at least one HSDPA user has data to
transmit in the queue buffer is B. Then, VS.ScchCodeUtil.Mean.Data = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters provide the average, maximum, and minimum usage of HS-PDSCH
code resources in a cell during a measurement period respectively. These counters are used to
analyze the allocation appropriateness of the HS-PDSCH code resources. If the code usage is
high, the code resources are insufficient for the current traffic. Therefore, more code resources
are required.
Measurement Points
Assume that the number of HS-PDSCH codes used in all TTIs is A and the number of
available HS-PDSCH codes in all TTIs is B. Then, VS.PdschCodeUtil.Mean = A/B. The
NodeB calculates VS.PdschCodeUtil.Mean every 5s and then takes the maximum value
within the measurement period as VS.PdschCodeUtil.Max and the minimum value within the
measurement period as VS.PdschCodeUtil.Min.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.27 Usage of HS-PDSCH Code Resources When at Least One HSDPA User
Camps on the cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the average usage of HS-PDSCH code resources when at
least one HSDPA user camps on the cell within a measurement period.
Measurement Points
Assume that the total number of used HS-PDSCH codes in all TTIs when at least one HSDPA
user camps on the cell within the measurement period is A, and the total number of available
HS-PDSCH codes in all TTIs when at least one HSDPA user camps on the cell is B. Then,
VS.PdschCodeUtil.Mean.User = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.28 Usage of HS-PDSCH Code Resources When at Least One HSDPA User
Has Data to Transmit in the Queue Buffer
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the average usage of HS-PDSCH code resources when at
least one HSDPA user has data to transmit in the queue buffer within a measurement period.
Measurement Points
Assume that the total number of used HS-PDSCH codes in all TTIs when at least one HSDPA
user has data to transmit in the queue buffer within the measurement period is A, and the total
number of available HS-PDSCH codes in all TTIs when at least one HSDPA user has data to
transmit in the queue buffer is B. Then, VS.PdschCodeUtil.Mean.Data = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average, maximum, and minimum ratios of the transmit
power of all the HS-SCCHs in a cell during a measurement period respectively. Each value is
expressed as the ratio of the respective transmit power to the maximum cell transmit power.
Measurement Points
During the measurement period, the NodeB calculates the total ratio of the transmit power of
all the HS-SCCHs to the maximum cell transmit power in all TTIs in the cell. Assume that
this value is A and the number of TTIs in the measurement period is B. Then,
VS.ScchPwrRatio.Mean = A/B. The NodeB calculates VS.ScchPwrRatio.Mean every 5s and
then takes the maximum value within the measurement period as VS.ScchPwrRatio.Max and
the minimum value within the measurement period as VS.ScchPwrRatio.Min.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average, maximum, and minimum ratios of the transmit
power over all the HS-PDSCHs in a cell during a measurement period respectively. Each
value is expressed as the ratio of the respective transmit power to the maximum cell transmit
power.
Measurement Points
During the measurement period, the NodeB calculates the total ratio of the transmit power
over all the HS-PDSCHs to the maximum cell transmit power in all TTIs in the cell. Assume
that this value is A and the number of TTIs in the measurement period is B. Then,
VS.PdschPwrRatio.Mean = A/B. The NodeB calculates VS.PdschPwrRatio.Mean every 5s
and then takes the maximum value within the measurement period as VS.PdschPwrRatio.Max
and the minimum value within the measurement period as VS.PdschPwrRatio.Min.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and maximum power usage of HSDPA free users
within a measurement period. The values are expressed as the ratios of the HSDPA power to
the maximum cell transmit power.
Measurement Points
Within the measurement period, the NodeB calculates the total ratio of the power for all
HSDPA free users to the maximum cell transmit power in all TTIs. Assume that this value is
A and the number of TTIs in the measurement period is B. Then,
VS.HSDPAPwrRatio.Mean.FreeUser = A/B. The NodeB calculates
VS.HSDPAPwrRatio.Mean.FreeUser every 5s and then takes the maximum value within the
measurement period as VS.HSDPAPwrRatio.Max.FreeUser.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average, maximum, and minimum available HSDPA
power within a measurement period. The values are expressed as the ratios of the available
HSDPA power to the maximum cell transmit power.
Measurement Points
Within the measurement period, the NodeB calculates the total ratio of the available HSDPA
power to the maximum cell transmit power in all TTIs. Assume that this value is A and the
number of TTIs in the measurement period is B. Then, VS.AvaiHSDPAPwrRatio.Mean =
A/B. The NodeB calculates VS.AvaiHSDPAPwrRatio.Mean every 5s and then takes the
maximum value within the measurement period as VS.AvaiHSDPAPwrRatio.Max and the
minimum value within the measurement period as VS.AvaiHSDPAPwrRatio.Min.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average HSDPA power ratios for operators within a
measurement period. The values are expressed as the ratios of the HSDPA power to the
maximum cell transmit power.
Measurement Points
Take VS.HSDPAPwrRatio.PLMN0 as an example. Within the measurement period, the
NodeB calculates the total ratio of the transmit power over the HS-SCCHs and HS-PDSCHs
to the maximum cell transmit power in all TTIs. Assume that this value is A and the number
of TTIs in the measurement period is B. Then, VS.HSDPAPwrRatio.PLMN0 = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average HSDPA power ratios for operators in an MOCN
network during a measurement period. The values are expressed as the ratios of the HSDPA
power to the maximum cell transmit power.
Measurement Points
Take VS.HSDPAPwrRatio.SharedOperator0 as an example. Within the measurement period,
the NodeB calculates the total ratio of the transmit power over the HS-SCCHs and HS-
PDSCHs to the maximum cell transmit power in all TTIs. Assume that this value is A and the
number of TTIs in the measurement period is B. Then, VS.HSDPAPwrRatio.SharedOperator0
= A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.35 Average permillage of transmit power for HSDPA users in each resource
group to the maximum cell transmit power
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measures the average permillage of transmit power for HSDPA users in each
resource group to the maximum cell transmit power.
Measurement Points
The permillage of transmit power for HS-SCCH and HS-PDSCH users in resource group to
the maximum cell transmit power is sampled within each transmission time interval (TTI). At
the end of the measurement period, the accumulated permillage is A, and the number of TTIs
is B. The formula for calculating this counter is: VS.HSDPAPwrRatio.Mean.ResG=A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters indicate the average, maximum, and minimum throughput of MAC-d PDUs in
a cell.
Measurement Points
Within a measurement period, the traffic volume of MAC-d PDUs with ACKs sent by all
users in a TTI is sampled every five seconds. At the end of the measurement period, the
accumulated traffic volume is A and the measurement period is B. The average of these
sampling results is defined as the value of VS.DataOutput.Mean (that is, A divided by B), the
maximum of these sampling results is defined as the value of VS.DataOutput.Max, and the
minimum of these sampling results is defined as the value of VS.DataOutput.Min. For a
multicarrier user, the corresponding counter is measured in the anchor and supplementary
carriers separately.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
1.1.1.37 HSDPA Cell Throughput of MAC-d PDUs When the Cell Serves HSDPA
Users
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The counter indicates the average throughput of MAC-d PDUs in a cell when the cell serves
HSDPA users.
Measurement Points
Within a measurement period, the traffic volume of MAC-d PDUs with ACKs sent by all
users in a TTI is sampled. At the end of the measurement period, the accumulated traffic
volume is A and the total duration within which the cell serves HSDPA users is B. A divided
by B is used as the value of the VS.DataOutput.User counter. For a multicarrier user, the
corresponding counter is measured in the anchor and supplementary carriers separately.
Formula
1000*[VS.DataOutput.Mean]/[VS.UserTtiRatio.Mean]
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
1.1.1.38 HSDPA Cell Throughput of MAC-d PDUs When at Least One HSDPA
User Has Data to Transmit in the Queue Buffer
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The counter indicates the average throughput of MAC-d PDUs in a cell when at least one
HSDPA user has data to transmit in the queue buffer.
Measurement Points
Within a measurement period, the traffic volume of MAC-d PDUs with ACKs sent by all
users in a TTI and the duration within which at least one HSDPA user has data to transmit in
the queue buffer . At the end of the measurement period, the accumulated traffic volume is A
and the total duration is B. A divided by B is used as the value of the
VS.DataOutput.UserData counter. For a multicarrier user, the corresponding counter is
measured in the anchor and supplementary carriers separately.
Formula
1000*[VS.DataOutput.Mean]/[VS.DataTtiRatio.Mean]
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters indicate the average, maximum, and minimum throughput of MAC-d PDUs of
HSDPA free users in a cell.
Measurement Points
Within a measurement period, the traffic volume of MAC-d PDUs with ACKs sent by all
HSDPA free users in a cell is sampled every five seconds. At the end of the measurement
period, the accumulated traffic volume is A and the measurement period is B. The average of
these sampling results is defined as the value of VS.DataOutput.Mean.FreeUser (that is, A
divided by B), the maximum of these sampling results is defined as the value of
VS.DataOutput.Max.FreeUser, and the minimum of these sampling results is defined as the
value of VS.DataOutput.Min.FreeUser. For a multicarrier user, the corresponding counter is
measured in the anchor and supplementary carriers separately.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
During a measurement period, the preceding counter indicates the total HS-DSCH TRB traffic
volume for which the ACK messages are sent by HSDPA users to the NodeB within a TTI in
a cell, including MAC-hs/MAC-ehs headers.
Measurement Points
The NodeB takes statistics on the preceding counter when demodulating the HARQ-ACK
information of the HSDPA UE carried on the HS-DPCCH. For multi-carrier users, this
counter is measured in the anchor carrier and the supplementary carrier separately.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total traffic volume of the MAC-hs/MAC-ehs PDUs with ACKs
received from all HSDPA users in a cell.
Measurement Points
The traffic volume of MAC-hs/MAC-ehs PDUs with ACKs received from all HSDPA users is
accumulated within a measurement period. This counter is measured in the serving cell. For
DC-HSDPA, DB-HSDPA, 4C-HSDPA, or 3C-HSDPA users, this counter is measured in the
anchor carrier and supplementary carrier separately. In the SRB over HSDPA scenario, when
the SRB over HSDPA measurement optimization is enabled, this counter does not measure
the traffic volume of MAC-hs/MAC-ehs PDUs with ACKs received from HSDPA users to the
SRB-only data.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The traffic volume of MAC-ehs PDUs received from DC-HSDPA/DC-HSDPA+MIMO users
with ACKs is sampled in the anchor carrier and supplementary carrier separately within each
TTI. At the end of a measurement period, the accumulated value is used as the value of the
counter VS.DataOutput.DCHSDPA.Traffic.
TTI. At the end of a measurement period, the accumulated value is used as the value of the
counter VS.DataOutput.DBHSDPA.Traffic.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average, maximum, and minimum ratios of the volume of
HSDPA user data discarded due to timer expiry to the total volume of HSDPA user data
received at the cell during a measurement period.
Measurement Points
During the measurement period, the NodeB calculates the volume of the HSDPA user data
that is discarded due to timer expiry in the cell. Assume that this value is A. The NodeB also
calculates the total volume of the HSDPA user data received at the cell during the
measurement period. Assume that this value is B. Then, VS.DataDiscardRatio.Mean = A/B.
The NodeB calculates VS.DataDiscardRatio.Mean every 5s and then takes the maximum
value within the measurement period as VS.DataDiscardRatio.Max and the minimum value
within the measurement period as VS.DataDiscardRatio.Min.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.1.44 Ratio of the Actual Transmit Power over the SCPICH to the SCPICH
Power Configured on the RNC
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the ratio of the actual transmit power over the SCPICH to the
SCPICH power configured on the RNC. If HSDPA users and MIMO users exist in the current
cell, the NodeB dynamically adjusts the transmit power over the SCPICH to make the cell
performance optimal.
Measurement Points
The NodeB samples the ratio of the actual transmit power over the S-CPICH to the S-CPICH
power configured on the RNC every 5s within a measurement period. The sum of the
sampling values at the end of a measurement period is recorded as A, and the number of
sampling periods in a measurement period is recorded as B. divided by the number of
samplings at the end of a measurement period. Then, VS.SCPICH.AvgPowerRate = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the power-enabled duration of the SCPICH in a cell. When
an MIMO user accesses the cell, the SCPICH power is enabled.
Measurement Points
Within a measurement period, the NodeB checks whether the SCPICH power is enabled
during each MAC-hs/MAC-ehs scheduling period. If the SCPICH power is enabled, the
counter value is accumulated.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the ratio of the traffic-based deactivation time of the
secondary-carrier cell to the activation time of the primary-carrier cell for DC-HSDPA,DC-
HSDPA+MIMO,DB-HSDPA and DB-HSDPA+MIMO users within a measurement period.
Measurement Points
Within the measurement period, the NodeB calculates the total time during which the
secondary-carrier cell for the DC-HSDPA,DB-HSDPA,DB-HSDPA+MIMO and DC-HSDPA
+MIMO users is deactivated because of decrease in throughput. Assume that this value is
A.The NodeB calculates the total time during which the DC-HSDPA,DB-HSDPA,DB-
HSDPA+MIMO and DC-HSDPA+MIMO users are active (the active time for a user starting
from the establishment of a PS service and ending at the release of cell connection). Assume
that this value is B. Then, VS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the ratio of the duration of the maximum DPCH transmit power
decrease to the online duration of all HSDPA users after the maximum DPCH power
restriction algorithm is activated.
Note: This algorithm is applicable only to HSDPA users that perform non-voice services and
carry only 3.4 kbit/s signaling radio bearers (SRBs) over the DPCH.
Measurement Points
At the end of a measurement period, for all HSDPA users supported by this algorithm, the
accumulated duration of the maximum DPCH transmit power decrease is A, and the
accumulated user online duration is B. The formula for calculating this counter is:
VS.HSDPA.DpchMaxPwrRestr.ActRatio = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Overview
The function subset measures the consumption of baseband resources on the NodeB side
according to the usage of CEs in each cell.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average and maximum number of UL CEs in a dedicated group
consumed in a cell. This counter is only used for operators with RAN sharing.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU, Coverage Expansion Under Interference,
Uplink Active Set Extension (Coordinating Link Extension Supported by Seamless Crystal
Voice, by SRB over DCH Uplink Coverage Expansion, or by CCPIC Phase 2), 4-Way
Receive Diversity by Inter-Band Assistance, and Enhanced Inter-NodeB Uplink CoMP (Joint
Reception) are introduced, the number of consumed uplink CEs in the cell includes the
number of uplink CEs consumed by R99 users and HSUPA users and the number of CEs
consumed by coordinating links. After the Uplink Enhanced CELL_FACH feature is
introduced, the uplink consumed CEs in the cell include those consumed by E-RACH users.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side. A coordinating link is established when Uplink CoMP (Joint Reception), HetNet
Uplink CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU,
Coverage Expansion Under Interference, Uplink Active Set Extension (Coordinating Link
Extension Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage
Expansion, or by CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or
Enhanced Inter-NodeB Uplink CoMP (Joint Reception) is enabled.
Measurement Points
The number of dedicated uplink CEs is sampled every five seconds. At the end of a
measurement period, the number of dedicated uplink CEs is obtained by dividing the
accumulated value in the period by the number of samples. The maximum of these sampling
results is defined as the maximum number of dedicated uplink CEs consumed in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of dedicated downlink CEs is sampled every five seconds. At the end of a
measurement period, the number of dedicated downlink CEs is obtained by dividing the
accumulated value in the period by the number of samples. The maximum of these sampling
results is defined as the maximum number of dedicated downlink CEs consumed in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average and maximum number of UL CEs in a shared group
consumed in a cell.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU, Coverage Expansion Under Interference,
Uplink Active Set Extension (Coordinating Link Extension Supported by Seamless Crystal
Voice, by SRB over DCH Uplink Coverage Expansion, or by CCPIC Phase 2), 4-Way
Receive Diversity by Inter-Band Assistance, and Enhanced Inter-NodeB Uplink CoMP (Joint
Reception) are introduced, the number of consumed uplink CEs in the cell includes the
number of uplink CEs consumed by R99 users and HSUPA users and the number of CEs
consumed by coordinating links. After the Uplink Enhanced CELL_FACH feature is
introduced, the uplink consumed CEs in the cell include those consumed by E-RACH users.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side. A coordinating link is established when Uplink CoMP (Joint Reception), HetNet
Uplink CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU,
Coverage Expansion Under Interference, Uplink Active Set Extension (Coordinating Link
Extension Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage
Expansion, or by CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or
Enhanced Inter-NodeB Uplink CoMP (Joint Reception) is enabled.
Measurement Points
The number of shared uplink CEs is sampled every five seconds. At the end of a measurement
period, the number of shared uplink CEs is obtained by dividing the accumulated value in the
period by the number of samples. The maximum of these sampling results is defined as the
maximum number of shared uplink CEs consumed in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of shared downlink CEs is sampled every five seconds. At the end of a
measurement period, the number of shared downlink CEs is obtained by dividing the
accumulated value in the period by the number of samples. The maximum of these sampling
results is defined as the maximum number of shared downlink CEs consumed in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average and maximum number of UL CEs in a shared group
consumed by all coordinating links in a cell.
Remarks:
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, Coverage
Expansion Under Interference, Uplink Active Set Extension (Coordinating Link Extension
Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage Expansion, or by
CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or Enhanced Inter-
NodeB Uplink CoMP (Joint Reception) is enabled.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side.
Measurement Points
The number of UL CEs in a shared group consumed by all coordinating links in a cell is
sampled every 5 seconds. At the end of a measurement period, the average number of UL CEs
in a shared group consumed by all coordinating links in a cell is obtained by dividing the
accumulated value within the measurement period by the number of samples. The maximum
value within the measurement period is the maximum number of UL CEs in a shared group
consumed by all coordinating links in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average and maximum number of UL CEs in a dedicated group
consumed by all coordinating links in a cell.
Remarks:
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, Coverage
Expansion Under Interference, Uplink Active Set Extension (Coordinating Link Extension
Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage Expansion, or by
CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or Enhanced Inter-
NodeB Uplink CoMP (Joint Reception) is enabled.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side.
Measurement Points
The number of dedicated UL CEs in a dedicated group consumed by all coordinating links is
sampled every 5 seconds. At the end of a measurement period, the average number of UL CEs
in a dedicated group consumed by all coordinating links is obtained by dividing the
accumulated value within the measurement period by the number of samples. The maximum
value within the measurement period is the maximum number of UL CEs in a dedicated
group consumed by all coordinating links.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
Root Counter Level-1 Counter
VS.HSUPA.TTI2msUserNumber.0 VS.HSUPA.LowRateTTI2msUserNumber
VS.HSUPA.Thruput.ROTAll VS.HSUPA.Thruput.ROTMor3
VS.HSUPA.Thruput.ROTAll VS.HSUPA.Thruput.ROTMor6
VS.HSUPA.Thruput.ROTAll VS.HSUPA.Thruput.ROTMor7
VS.HSUPA.Thruput.ROTAll VS.HSUPA.Thruput.ROTMor9
VS.HSUPA.Thruput.ROTAll VS.HSUPA.Thruput.ROTMor10
VS.HSUPA.Thruput.ROTAll VS.HSUPA.Thruput.ROTMor13
VS.HSUPA.Thruput.ROTAll VS.HSUPA.Thruput.ROTMor20
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the distribution of cell load (that is, the ratio of the actual
RTWP in a cell to the reference RTWP) on the air interface during a measurement period.
Measurement Points
The uplink Uu interface load is sampled every 2 ms within a measurement period. The
corresponding counter is incremented by 1 each time the uplink Uu interface load is within
the correponding load range.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the number of times the uplink overload occurs in a cell over
the air interface. Uplink cell overload over the air interface affects the HSUPA services.
Measurement Points
The Uu interface load factor is sampled every 2 ms within a measurement period. This
counter indicates the total number of times that the Uu interface load factor of the cell exceeds
the target value of the maximum uplink load factor in a measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the ratio of E-AGCH code collisions in a cell.
Measurement Points
At the end of a measurement period, the calculated number of users that fail to send AGs due
to occupied E-AGCH codes is recorded A, and the calculated number of users that
successfully send AGs is recorded B. The ratio of E-AGCH code collisions is A/(A+B). This
counter is sampled every five seconds. VS.HSUPA.AGCHCodeCollision.Mean measures the
average of these sampling results within a measurement period.
VS.HSUPA.AGCHCodeCollision.Max measures the maximum of these sampling results
within a measurement period. Note that these counters involve only the users with the local
cell as the serving cell, and the users that fail to send AGs within the previous measurement
period and then reattempt to send AGs with the next measurement period are also included.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the statistics on the E-AGCH utilization in a cell.
Measurement Points
Within a measurement period, the NodeB counts the total number of used E-AGCHs in all
scheduling periods. Assume that this value is A. The NodeB counts the total number of
configured E-AGCHs in all scheduling periods of the measurement period. Assume that this
value is B. Then, VS.HSUPA.AGCHCodeUtil.Mean = A/B. The NodeB samples the value of
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and maximum number of HSUPA users with data
transmission in each TTI during a measurement period in a cell.
Measurement Points
During the measurement period, the NodeB counts the total number of HSUPA users with
data transmission in all TTIs. This counter is counted once for HSUPA users with 2 ms TTI
and five times for HSUPA users with 10 ms TTI. Assume that this value is A and the number
of TTIs in the measurement period is B. Then, VS.HSUPA.DataUserNum.Mean = A/B. The
NodeB samples the value of VS.HSUPA.DataUserNum.Mean in each sampling period (5s)
and takes the maximum sampled value within the measurement period as
VS.HSUPA.DataUserNum.Max. For DC-HSUPA users, the preceding counter is measured in
the anchor carrier and the supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and maximum number of scheduled HSUPA
users in each TTI during a measurement period in a cell. When an HSUPA user is scheduled,
the NodeB sends the RG UP, RG DOWN, or AG grant to the HSUPA user.
Measurement Points
During the measurement period, the NodeB counts the total number of scheduled HSUPA
users in all TTIs. Assume that this value is A and the number of TTIs in the measurement
period is B. Then, VS.HSUPA.ScheduleUserNum.Mean = A/B. The NodeB samples the value
of VS.HSUPA.ScheduleUserNum.Mean in each sampling period (5s) and takes the maximum
sampled value within the measurement period as VS.HSUPA.ScheduleUserNum.Max. For
DC-HSUPA users, the preceding counter is measured in the anchor carrier and the
supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the ratio of the number of HSUPA users with limited UE
Power Headroom (UPH) to the total number of HSUPA users in a cell. The power is limited
when the rate requested by the UE to send buffered data is higher than the maximum
permissible transmit rate indicated in the UPH field. For more information about UPH, see
section "9.2.5.3.2 Scheduling Information" in 3GPP TS 25.321 (v10.10.0).
Measurement Points
During the measurement period, the NodeB counts the total number of power-limited HSUPA
users in all TTIs. Assume that this value is A and the total number of HSUPA users in all TTIs
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the ratio of the number of HSUPA users whose requested rate
fails to be reached because of limited load over the air interface to the total number of HSUPA
users in a cell during a measurement period.
Measurement Points
During a measurement period, the NodeB counts the total number of HSUPA users whose
requested rate fails to be reached because of limited load over the air interface in all TTIs.
Assume that this value is A and the total number of HSUPA users in all TTIs in the
measurement period is B. Then, VS.HSUPA.LeftPwrLmtUserRatio = A/B. If the load of an
HSUPA user is limited several times during the measurement period, the NodeB counts the
user repeatedly. For DC-HSUPA users, the preceding counter is measured in the anchor
carrier and the supplementary carrier separately.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the number of unhappy HSUPA users in a cell.
Measurement Points
This counter is measured when the NodeB finds that the happy bit value carried by an HSUPA
user is unhappy in MAC-e scheduling. For more information about the happy bit, see section
"9.2.5.3.1 Happy Bit" in 3GPP TS 25.321 (v10.10.0). This counter is counted once for
HSUPA 2 ms TTI users and five times for HSUPA 10 ms TTI users. For DC-HSUPA users,
the preceding counter is measured in the anchor carrier and the supplementary carrier
separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the ratio of the number of unhappy HSUPA users to the total
number of HSUPA users in a cell during a measurement period. For more information about
unhappy, see section "9.2.5.3.1 Happy Bit" in 3GPP TS 25.321 (v10.10.0).
Measurement Points
During a measurement period, the NodeB counts the total number of unhappy HSUPA users
in all TTIs. Assume that this value is A and the total number of HSUPA users in all TTIs in
the measurement period is B. Then, VS.HSUPA.UnHappyUserNumRatio = A/B. If an
HSUPA user reports the unhappy state several times during the measurement period, the
NodeB counts the user repeatedly.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the average number of 2 ms TTI HSUPA users at different rates in a
cell within a measurement period.
Measurement Points
The number of 2 ms TTI HSUPA users at different MAC-e/i rates is sampled every 100 ms.
At the end of a measurement period, the accumulated value is A, and the number of samples
is B. The formula for calculating this counter is: VS.HSUPA.TTI2msUserNumber = A/B. For
DC-HSUPA users or users in handover scenarios, these counters are measured in each cell.
Rate at the HSUPA MAC-e/i layer = Traffic of MAC-e/i TRBs correctly received from
HSUPA users within a measurement period/Online duration for HSUPA users within the
measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the average number of 10 ms TTI HSUPA users at different rate
intervals in a cell within a measurement period, reflecting the distribution of HSUPA users at
these rate intervals.
Here,
Interval 0 ranges from 0 kbit/s (included) to 50 kbit/s.
Interval 1 ranges from 50 kbit/s (included) to 100 kbit/s.
Interval 2 ranges from 100 kbit/s (included) to 150 kbit/s.
Interval 3 ranges from 150 kbit/s (included) to 200 kbit/s.
Interval 4 ranges from 200 kbit/s (included) to 400 kbit/s.
Interval 5 ranges from 400 kbit/s (included) to 700 kbit/s.
Interval 6 ranges from 700 kbit/s (included) to 1500 kbit/s.
Interval 7 ranges from 1500 kbit/s (included) to 2000 kbit/s.
Measurement Points
The number of 10 ms TTI HSUPA users at different MAC-e/i rates is sampled every 100 ms.
At the end of a measurement period, the accumulated value is A, and the number of samples
is B. The formula for calculating this counter is: VS.HSUPA.TTI10msUserNumber = A/B.
For DC-HSUPA users or users in handover scenarios, these counters are measured in each
cell. Rate at the HSUPA MAC-e/i layer = Traffic of MAC-e/i TRBs correctly received from
HSUPA users within a measurement period/Online duration for HSUPA users within the
measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of valid time-division scheduling users in a
cell.When the time-division scheduling takes effect, the number of time-division scheduling
users in the cell is not 0.
Measurement Points
The number of valid HSUPA time-division scheduling users is sampled every 5s within a
measurement period. The sum of sampling results at the end of a measurement period is
recorded as A. The number of sampling times in a measurement period is recorded as B.
VS.HSUPA.TDMUserNum.Mean=A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the number of TTIs when at least one HSUPA user exists in a
cell during a measurement period.
Measurement Points
This counter is measured when at least one HSUPA user exists in a TTI each time MAC-e
scheduling is performed. For DC-HSUPA users, the preceding counter is measured in the
anchor carrier and the supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.3.15 Number of TTIs in Which at Least One HSUPA User Transmits Data in a
Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the number of TTIs in which at least one HSUPA user
transmits data in a cell.
Measurement Points
This counter indicates the number of TTIs in which at least an HSUPA user transmits data in
MAC-e scheduling. There is data transmission within a TTI if at least an HSUPA user
transmits data in the TTI. This counter is counted once for HSUPA 2 ms TTI users and five
times for HSUPA 10 ms TTI users. A DC-HSUPA user is regarded as an HSUPA user in each
anchor carrier and supplementary carrier. For DC-HSUPA users, the counter is measured in
the anchor carrier and the supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.3.16 Number of TTIs in Which at Least One HSUPA User Transmits the TRB
Data in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the number of TTIs in which at least one HSUPA user
transmits the TRB data in a cell.
Measurement Points
This counter indicates the number of TTIs in which at least an HSUPA user transmits the TRB
data in MAC-e scheduling in an HSUPA serving cell. There is data transmission within a TTI
if at least an HSUPA user transmits the TRB data in the TTI in an HSUPA serving cell. This
counter is counted once for HSUPA 2 ms TTI users and five times for HSUPA 10 ms TTI
users. A DC-HSUPA user is regarded as an HSUPA user in each anchor carrier and
supplementary carrier. For DC-HSUPA users, the counter is measured in the anchor carrier
and the supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The counters measure the number of HSUPA users with data transmission under different
uplink Uu loads in a cell. The average number of HSUPA users with data transmission under
different uplink Uu loads in a cell is calculated by dividing this counter by
VS.HSUPA.DataTtiNum.ROTMorX.
Measurement Points
Map Uu loads, which are sampled every 100 ms, to corresponding counters within a
measurement period. Accumulate the number of 2 ms TTI HSUPA users every 100 ms, the
result of which is represented by N. Then, calculate the number of accumulated values of N
using the corresponding cell load counter within a measurement period. At the end of a
measurement period, the calculation result is the number of HSUPA users with data
transmission under different uplink Uu loads. For multi-carrier HSUPA users or users in
handover scenarios, these counters are measured in the cells with the anchor carrier and the
supplementary carriers separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.3.18 Number of TTIs in Which HSUPA Users Have Data to Transmit under
Different Uplink Uu Loads in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the number of TTIs in which HSUPA users have data to transmit
under different uplink Uu loads in a cell. Uu interface load indicates the ratio of the current
RTWP to the reference RTWP in a cell.
Measurement Points
At the end of a measurement period, the number of TTIs in which HSUPA users have data to
transmit under different uplink Uu loads is measured in a cell. If at least one user transmits
data, there is data transmission within the TTI. For 2 ms TTI HSUPA users, this scenario is
measured once. For 10 ms TTI HSUPA users, this scenario is measured five times. For DC-
HSUPA users or users in handover scenarios, these counters are measured in each cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the HSUPA HARQ distribution in a cell.
Measurement Points
During a measurement period, the NodeB uses VS.HSUPA.ACKTotal to count the total
number of HI messages containing ACK on the E-HICH for HSUPA users,
VS.HSUPA.NACKTotal to count the total number of HI messages containing NACK on the
E-HICH for HSUPA users, and VS.HSUPA.DTXTotal to count the total number of HSUPA
users without data transmission in all TTIs. A DC-HSUPA user is regarded as an HSUPA user
in each anchor carrier and supplementary carrier. For DC-HSUPA users, the counter is
measured in the anchor carrier and the supplementary carrier separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of MAC-e/MAC-i PDUs successfully received in the serving cell from HSUPA
UEs is sampled within a measurement period. At the end of the measurement period, the sum
of these sampling results is defined as the value of VS.HSUPA.PDUNum. The number of
such PDUs received from E-RACH UEs is not counted into this counter. The number of
retransmitted MAC-e/MAC-i PDUs received in the serving cell from HSUPA UEs is sampled
within a measurement period. At the end of the measurement period, the sum of these
sampling results is defined as the value of VS.HSUPA.RetransPDUNum. The number of such
PDUs retransmitted by E-RACH UEs is not counted into this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the cell throughput of HSUPA users under different uplink Uu loads.
Uu interface load indicates the ratio of the current RTWP to the reference RTWP in a cell.
Measurement Points
At the end of a measurement period, the traffic of MAC-e/MAC-i TRBs successfully received
from all HSUPA users under different uplink Uu loads is measured in a cell. For DC-HSUPA
users or users in handover scenarios, these counters are measured according to the actual
traffic in a cell.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the ratio of RTWP difference to RTWP before IC in a
measurement period. RTWP difference means RTWP before IC minus RTWP after IC. These
counters represent the total IC efficiency in a cell. The total IC includes stage 1 IC (control
channel IC) and stage 2 IC (HSUPA IC).When the RRU3801C is used for a cell, the statistics
value is 0xffff, which is invalid.
Measurement Points
Within the measurement period, the NodeB samples the IC efficiency in each sampling period
(5s) and adds up the sampled values. Assume that the sum is A and the number of samples
within the measurement period is B. Then, VS.HSUPA.Ic.MeanEff = A/B. The NodeB takes
the maximum sampled value within the measurement period as VS.HSUPA.Ic.MaxEff.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the ratio of Unhappy HSUPA users with scheduling grant
(SG) limit due to resource insufficiency to all Unhappy HSUPA users. SG limit means that the
SG value is decreased or remains unchanged. For details about SG, see 3GPP TS 25.321.
Measurement Points
Within a measurement period, the number of Unhappy HSUPA users with SG limit due to
resource insufficiency and the number of all Unhappy HSUPA users are sampled every 2 ms.
At the end of the measurement period, the calculated value of Unhappy HSUPA users with
SG limit due to Iub resource insufficiency within each sampling period is recorded as A. The
calculated value of Unhappy HSUPA users with SG limit due to air interface load
insufficiency within each sampling period is recorded as B. The calculated value of Unhappy
HSUPA users with SG limit due to CE insufficiency within each sampling period is recorded
as C. The calculated value of Unhappy HSUPA users within each sampling period is recorded
as D.
Note that the number of Unhappy HSUPA users with SG limit due to resource insufficiency is
E-DCH serving RLS specific only.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the ratio of samples with HSUPA users using FDE to the total
samples with HSUPA users in a cell during a measurement period. This counter is used to
evaluate the performance of the HSUPA FDE feature.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU and Coverage Expansion Under Interferenceare
are introduced, the number of samples with HSUPA users using FDE includes the number of
samples with HSUPA users in the local cell using FDE and the number of samples with
coordinating links for UL CoMP (joint reception) users in other cells using FDE in the local
cell.
Coordinating link: Link specifically established by the NodeB for UL CoMP (joint reception)
users. The link is transparent to the RNC and UEs.
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, or
Coverage Expansion Under Interference is enabled.
Measurement Points
During a measurement period, the NodeB counts the number of TTIs in which at least one
HSUPA user uses FDE. Assume that this value is A. The NodeB counts the number of TTIs in
which at least one HSUPA user camps on the cell during the measurement period. Assume
that this value is B. Then, VS.HSUPA.FDE.UtilizeTimePermillage = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the ratio of samples with HSUPA users using 16QAM to the
total samples with HSUPA users in a cell during a measurement period. This counter is used
to evaluate the performance of the UL 16QAM feature.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU and Coverage Expansion Under Interferenceare
are introduced, the number of samples with HSUPA users using 16QAM includes the number
of samples with HSUPA users in the local cell using 16QAM and the number of samples with
coordinating links for UL CoMP (joint reception) users in other cells using 16QAM in the
local cell.
Coordinating link: Link specifically established by the NodeB for UL CoMP (joint reception)
users. The link is transparent to the RNC and UEs.
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, or
Coverage Expansion Under Interference is enabled.
Measurement Points
During a measurement period, the NodeB counts the number of TTIs in which at least one
HSUPA user uses 16QAM. Assume that this value is A. The NodeB counts the number of
TTIs in which at least one HSUPA user camps on the cell during the measurement period.
Assume that this value is B. Then, VS.HSUPA.16QAM.UtilizeTimePermillage = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the Boosting usage in a cell during a measurement period.
This counter is used to evaluate the performance of the E-DPCCH Boosting feature.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU and Coverage Expansion Under Interferenceare
are introduced, the number of samples with HSUPA users using Boosting includes the number
of samples with HSUPA users in the local cell using Boosting and the number of samples with
coordinating links for UL CoMP (joint reception) users in other cells using Boosting in the
local cell.
Coordinating link: Link specifically established by the NodeB for UL CoMP (joint reception)
users. The link is transparent to the RNC and UEs.
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, or
Coverage Expansion Under Interference is enabled.
Measurement Points
During a measurement period, the NodeB counts the number of TTIs in which at least one
HSUPA user uses Boosting. Assume that this value is A. The NodeB counts the number of
TTIs in which at least one HSUPA user camps on the cell during the measurement period.
Assume that this value is B. Then, VS.HSUPA.Boosting.UtilizeTimeRatio = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the possibility of the active anti-interference scheduling
algorithm in a cell during a measurement period.
Measurement Points
During a measurement period, the NodeB counts the number of TTIs in which the anti-
interference scheduling algorithm is active. Assume that this value is A. The NodeB counts
the number of TTIs in which the switch for anti-interference scheduling is turned on during
the measurement period. Assume that this value is B. Then,
VS.HSUPA.AntiInterfSch.ActRatio = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the time-division scheduling algorithm validity probability in a cell.
This counter is used to evaluate the performance of the HSUPA Time Division Scheduling
feature. When the time-division scheduling takes effect, the number of time-division
scheduling users in the cell is not 0.
Measurement Points
The number of periods for valid HSUPA time-division scheduling is sampled every five
seconds. At the end of a measurement period, for example, 15 minutes, the sum of these
sampling results is reported. The time-division scheduling algorithm validity probability is
equal to the result of the sum of the sampling results divided by the sampling times.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
For more information about HARQ, see section "9.2.5.1 HARQ information" in 3GPP TS
25.321 (v10.10.0).
Measurement Points
The following table describes the Measurement Points of each counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.3.30 Number of Transitions from Using A Single HARQ Process to Using All
HARQ Processes In the Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of transitions from using a single HARQ process to using
all HARQ processes in the cell. For more information about HARQ, see section "9.2.5.1
HARQ information" in 3GPP TS 25.321 (v10.10.0).
Measurement Points
This counter measures the number of transitions from using a single HARQ process to using
all HARQ processes within a measurement period in the serving cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.3.31 Ratio of SIs That Are Reported by HSUPA Users and Meet Power Limit
Conditions in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the ratio of SIs that are reported by HSUPA users and meet power limit
conditions to all reported SIs in a cell. The power is considered insufficient if the maximum
allowed transmit rate, which can be measured by using the UE Power Headroom (UPH), is
less than the rate requested by transmit buffer included in the scheduling information. For
details about SI and UPH, see section 9.2.5.3.2 "Scheduling Information" in 3GPP TS 25.321
(v10.10.0).
Measurement Points
During a measurement period, the amount of scheduling information (SI) that is reported by
HSUPA users and meets the power limit conditions in a cell is recorded as A. The total
number of SIs reported by all HSUPA users in the cell is recorded as B. Then,
VS.HSUPA.UPHLmtRatio.SI = A/B. For a DC-HSUPA user, the corresponding counter is
measured in the anchor and supplementary carriers separately.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.3.32 Number of Times UPH Values Reported by HSUPA 2 ms TTI Users Are
Within Each Interval
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the number of times UPH values are within different intervals
according to the scheduling information (SI) reported by HSUPA 2ms TTI users, reflecting
the distribution of uplink coverage for users in the cell.
The UE Power Headroom (UPH) indicates the ratio of the maximum UE transmission power
to the corresponding DPCCH code power. For more information, see section "9.2.5.3.2
Scheduling Information" in 3GPP TS 25.321 (v10.10.0).
Here,
Interval 0 ranges from 0 db (included) to 7 db.
Interval 1 ranges from 7 db (included) to 10 db.
Interval 2 ranges from 10 db (included) to 13 db.
Interval 3 ranges from 13 db (included) to 31 db (included).
Measurement Points
Each time the NodeB receives scheduling information (SI) from an HSUPA 2 ms TTI user
within a measurement period, the number of times the UPH value contained in the SI is
within the corresponding interval is measured in the serving cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.3.33 Number of TTIs in which HSUPA UEs that perform uplink full buffer
services with have data to transmit under Different CQIs in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs in which uplink TRBs are received over the HSPA
service link from UEs that perform uplink full buffer services within the corresponding CQI
range in a cell.
Uplink full buffer services: If the total E-DCH buffer status (TEBS) index is greater than or
equal to 18 in a period, the services in the period are full buffer services. For details about the
TEBS index, see section 9.2.5.3.2 "Scheduling Information" in 3GPP TS 25.321 (V11.6.0).
Measurement Points
During a measurement period, the NodeB sums up the number of TTIs in which the Mac-e/
Mac-i TRBs are received over the HSPA service link from UEs that perform uplink full buffer
services with different CQI ranges in a cell, including the number of TTIs in which TRBs are
retransmitted. If Mac-e/Mac-i TRBs are received from multiple UEs within a TTI, this
counter is repeatedly measured.
For 2 ms TTI HSUPA UEs, this counter is measured once. For 10 ms TTI HSUPA UEs, this
counter is measured five times.
This counter is measured for HSPA UEs supporting both HSDPA and HSUPA. For UEs
supporting both multi-carrier HSDPA and SC-HSUPA, this counter is measured only on the
primary carrier. For DC-HSUPA UEs, this counter is measured separately on the primary and
secondary carriers. The CQI range is determined based on the single-stream CQI for MIMO
UEs. For details about single-stream CQIs, see section "6A.2.2 CQI definition when the UE is
configured in MIMO mode" in 3GPP TS 25.214 (V11.6.0).
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs in which MAC-e/MAC-i data is received over the
HSUPA service link from UEs with insufficient transmit power in a cell.
Measurement Points
During a measurement period, the NodeB sums up the number of TTIs in which Mac-e/Mac-i
data is received from HSUPA UEs with insufficient transmit power in the serving cell,
The UE transmit power is considered insufficient if the maximum allowed transmit rate,
which can be measured by using the UE power headroom (UPH), is smaller than the rate
requested by the transmit buffer included in the scheduling information. For details about the
UPH, see section 9.2.5.3.2 "Scheduling Information" in 3GPP TS 25.321 (v10.10.0).
For 2 ms TTI HSUPA UEs, this counter is measured once. For 10 ms TTI HSUPA UEs, this
counter is measured five times. For DC-HSUPA UEs, this counter is measured separately on
the primary and secondary carriers.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the Mac-d TRB data volume sent by HSUPA users in the serving cell.
Measurement Points
The traffic volume of Mac-d TRB PDUs successfully received from HSUPA users in the
serving cell is accumulated within a measurement period. A DC-HSUPA user is regarded as
one HSUPA user in the primary carrier and one HSUPA user in the secondary carrier, and this
counter is measured in the two carriers separately.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of TTIs in which Mac-e/Mac-i TRBs are received from HSUPA 2 ms TTI users
in the serving cell is accumulated within a measurement period, including the number of TTIs
in which TRBs are retransmitted. If Mac-e/Mac-i TRBs are received from multiple users in a
TTI, the VS.HSUPA.2msPDU.TTI.Num counter is repeatedly measured.
The number of TTIs in which Mac-e/Mac-i TRBs are received from HSUPA 10 ms TTI users
in the serving cell is accumulated within a measurement period, including the number of TTIs
in which TRBs are retransmitted. If Mac-e/Mac-i TRBs are received from multiple users in a
TTI, the VS.HSUPA.10msPDU.TTI.Num counter is repeatedly measured.
For a DC-HSUPA user, the corresponding counter is measured in the primary and secondary
carriers separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of HSUPA users enabled with Turbo IC in an
HSUPA cell. This counter is used to evaluate the Turbo IC feature.
Measurement Points
During a measurement period, the NodeB calculates the total number of HSUPA users
enabled with Turbo IC(including 2 ms TTI HSUPA and 10 ms TTI HSUPA) in all sampling
periods with each lasting for 10 ms and records the accumulated number in the measurement
period as A. At the same time, the NodeB counts the number of sampling periods in the
measurement period and records the number as B. Then, VS.HSUPA.TurboIC.Number = A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total traffic of Mac-e/Mac-i PDUs correctly received from all 2 ms
TTI HSUPA users.
Measurement Points
The traffic of Mac-e/Mac-i PDUs correctly received from 2 ms TTI HSUPA users is sampled
in each TTI within a measurement period. At the end of the measurement period, the sum of
these sampling results is used as the value of this counter. This counter is measured in the
serving cell. If SRB over EDCH is enabled, this counter is not incremented when a UE
transmits only SRB data. For DC-HSUPA users, this counter is measured in primary carrier
and secondary carrier separately.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total traffic of Mac-e/Mac-i PDUs correctly received from all 10
ms TTI HSUPA users.
Measurement Points
The traffic of Mac-e/Mac-i PDUs correctly received from 10 ms TTI HSUPA users is sampled
in each TTI within a measurement period. At the end of the measurement period, the sum of
these sampling results is used as the value of this counter. This counter is measured in the
serving cell. If SRB over EDCH is enabled, this counter is not incremented when a UE
transmits only SRB data. For DC-HSUPA users, this counter is measured in primary carrier
and secondary carrier separately.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
1.1.3.40 Average number of 10 ms TTI HSUPA UEs in the CCH OLPC state in a
cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of 10 ms TTI HSUPA UEs in the CCH OLPC state is sampled in a cell every 100
ms. At the end of the measurement period, dividing the accumulated value in the period by
samples is defined as the value of this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.3.41 Average number of 2 ms TTI HSUPA UEs in the CCH OLPC state in a
cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of 2 ms TTI HSUPA UEs in the CCH OLPC state is sampled in a cell every 100
ms. At the end of the measurement period, dividing the accumulated value in the period by
samples is defined as the value of this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.3.42 Average SIRtarget decrease of 10 ms TTI HSUPA UEs in the CCH OLPC
state in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
SIRtarget decrease of 10 ms TTI HSUPA UEs in the CCH OLPC state is sampled in a cell
every 100 ms. The SIRtarget decrease is equal to SIRtarget in the DCH OLPC state minus
SIRtarget in the CCH OLPC state, in the unit of dB. SIRtarget decrease within this sampling
period is obtained by dividing the accumulated decrease from all such UEs by the total
number of UEs. At the end of the measurement period, dividing the accumulated value in the
measurement period by samples is defined as the value of this counter.
Formula
None
Unit
dB
Related Features
Counter Name Feature ID Feature Name
1.1.3.43 Average SIRtarget decrease of 2 ms TTI HSUPA UEs in the CCH OLPC
state in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
SIRtarget decrease of 2 ms TTI HSUPA UEs in the CCH OLPC state is sampled in a cell
every 100 ms. The SIRtarget decrease is equal to SIRtarget in the DCH OLPC state minus
SIRtarget in the CCH OLPC state, in the unit of dB. SIRtarget decrease within this sampling
period is obtained by dividing the accumulated decrease from all such UEs by the total
number of UEs. At the end of the measurement period, dividing the accumulated value in the
measurement period by samples is defined as the value of this counter.
Formula
None
Unit
dB
Related Features
Counter Name Feature ID Feature Name
1.1.3.44 Average Number of HSUPA 2 ms TTI UEs in the Virtual Power Scaling
State in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the average number of 2 ms TTI HSUPA UEs in the virtual power
scaling state in a cell. This counter is used to evaluate the performance of the Coverage
Improvement for HSUPA 2 ms TTI UEs feature.
Measurement Points
The total number of 2 ms TTI HSUPA UEs in the virtual power scaling state is measured
every 2 ms in a cell within a measurement period. Assume that the measured number is A,
and the total number of samples within a measurement period is B. Then, VS.HSUPA.
2msTTI.VPSUserNum.Mean = A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of HSUPA 10 ms TTI users enabled with Turbo IC
in an HSUPA cell to evaluate the Turbo IC enhancement feature.
Measurement Points
During a measurement period, the NodeB calculates the total number of HSUPA 10 ms TTI
users enabled with Turbo IC in all sampling periods with each lasting for 10 ms and records
the accumulated number in the measurement period as A. At the same time, the NodeB counts
the number of sampling periods in the measurement period and records the number as B.
Then, VS.HSUPA.TurboIC.Number.TTI10ms = A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average number of HSUPA users selected for UL CoMP in a cell
enabled with Inter-NodeB Uplink CoMP (Joint Reception).
The following table describes the meanings of each counter.
Measurement Points
The NodeB calculates the total number of HSUPA users selected for UL CoMP in a cell
enabled with Inter-NodeB Uplink CoMP (Joint Reception) every 5 s within a measurement
period. Assume that the measured number is A, and the total number of samples within the
measurement period is B. Then, VS.HSUPA.InterNodeBUlCoMP.UserNum = A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The counter measures the average number of HSUPA coordinating links selected for UL
CoMP in a cell enabled with Enhanced Inter-NodeB Uplink CoMP (Joint Reception).
Measurement Points
The NodeB calculates the total number of HSUPA coordinating links selected for UL CoMP
in a cell enabled with Enhanced Inter-NodeB Uplink CoMP (Joint Reception) every 5 seconds
within a measurement period. Assume that the measured number is A, and the total number of
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
Within a measurement period, the NodeB accumulates the time period during which the
supplementary carrier of each DC-HSUPA user is deactivated due to RTWP insufficiency.
Assume that this number is A. The NodeB accumulates the time period during which the
supplementary carrier of each DC-HSUPA user is deactivated due to uplink transmit power
insufficiency. Assume that this number is B. The NodeB calculates the total time during
which the DC-HSUPA users are active (the active time for a user starting from the
establishment of an RRC connection and ending at the release of RRC connection) in the
serving cell. Assume that the calculated value is C.
VS.HSUPA.DCCfg.SupCarrierDeact.RTWP.TimeRatio = A/C.
VS.HSUPA.DCCfg.SupCarrierDeact.ULPwr.TimeRatio = B/C.
The preceding counters are measured in the serving cell of the supplementary carriers of DC-
HSUPA users.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.3.49 Traffic of MAC-e/MAC-i PDUs received from HSUPA UEs that perform
uplink full buffer services under Different CQIs in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the traffic of MAC-e/MAC-i PDUs received over the HSPA service
link from UEs that perform uplink full buffer services within the corresponding CQI range in
a cell.
Uplink full buffer services: If the total E-DCH buffer status (TEBS) index is greater than or
equal to 18 in a period, the services in the period are full buffer services. For details about the
TEBS index, see section 9.2.5.3.2 "Scheduling Information" in 3GPP TS 25.321 (V11.6.0).
Measurement Points
During a measurement period, the NodeB sums up the traffic of MAC-e/MAC-i TRB PDUs
correctly received over the HSPA service link from UEs that perform uplink full buffer
services with different CQI ranges in a cell.
This counter is measured for HSPA UEs supporting both HSDPA and HSUPA. For UEs
supporting both multi-carrier HSDPA and SC-HSUPA, this counter is measured only on the
primary carrier. For DC-HSUPA UEs, this counter is measured separately on the primary and
secondary carriers. The CQI range is determined based on the single-stream CQI for MIMO
UEs. For details about single-stream CQIs, see section "6A.2.2 CQI definition when the UE is
configured in MIMO mode" in 3GPP TS 25.214 (V11.6.0).
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the traffic of MAC-e/MAC-i PDUs correctly received over the HSUPA
service link from UEs with insufficient transmit power in a cell.
Measurement Points
During a measurement period, the NodeB sums up the traffic of MAC-e/MAC-i PDUs
correctly received over the HSUPA service link from UEs with insufficient transmit power in
a cell.
The UE transmit power is considered insufficient if the maximum allowed transmit rate,
which can be measured by using the UE power headroom (UPH), is smaller than the rate
requested by the transmit buffer included in the scheduling information. For details about the
UPH, see section 9.2.5.3.2 "Scheduling Information" in 3GPP TS 25.321 (v10.10.0).
For DC-HSUPA UEs, this counter is measured separately on the primary and secondary
carriers.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the average number of HSUPA users enabled with virtual CPC in a
cell. If the counter value is not 0, the Virtual CPC feature has taken effect.
Measurement Points
The total number of HSUPA users enabled with virtual CPC is measured every 100 ms in all
cells in the serving E-DCH link set within a measurement period. Assume that the measured
number is A, and the total number of samples is B in the measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the average decrease in the target SIR of HSUPA users enabled with
virtual CPC in a cell. This counter is used to evaluate the gains yielded by the virtual CPC
feature.
Measurement Points
The total SIRtarget decrease of HSUPA users enabled with virtual CPC is measured every 100
ms in all cells in the serving E-DCH link set within a measurement period. Assume that the
measured value is A, and the total number HSUPA users enabled with virtual CPC is B in the
measurement period.
Then, VS.HSUPA.VirtualCPC.SIRTargetDec.Mean = A/B. The SIRtarget is calculated in the
unit of dB.
When the Uplink Control Channel OLPC feature is enabled,
SIRtarget decrease of users in the CCH OLPC state = CCH SIRtarget - Virtual CPC SIRtarget
SIRtarget decrease of users in the DCH OLPC state = DCH SIRtarget - Virtual CPC SIRtarget
When the Uplink Control Channel OLPC feature is disabled,
SIRtarget decrease = DCH SIRtarget - Virtual CPC SIRtarget.
Formula
None
Unit
dB
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of HSUPA 2 ms TTI users enabled with precise
channel estimation in a cell. This counter is used to evaluate the performance of precise
channel estimation for HSUPA 2 ms TTI users.
The following table describes the meanings of each counter.
Measurement Points
The number of HSUPA 2 ms TTI users enabled with precise channel estimation is sampled
every TTI in a cell within a measurement period. At the end of the measurement period, the
accumulated user number is recorded as A, and the total number of TTIs (when this feature is
enabled) within the measurement period is B. The value of
VS.HSUPA.PreciseChEstUserNum.TTI2ms.Mean equals A divided by B. For DC-HSUPA
users or users in handover scenarios, this counter is measured in each cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The function subset consists of CPC-related counters for a cell to indicate the CPC cell status
and performance.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters comply with section "6C.2 Discontinuous uplink DPCCH
transmission operation" in 3GPP TS 25.214 (v10.10.0).
For more information about CPC, see section "9.2.2.64 Continuous Packet Connectivity
DTX-DRX Capability" in 3GPP TS 25.433 (v10.10.0).
For more information about UL_DTX, see section "6C.2 Discontinuous uplink DPCCH
transmission operation" in 3GPP TS 25.214 (v10.10.0).
The following table describes the meanings of each counter.
Measurement Points
During a measurement period, the NodeB counts the number of users configured in UL_DTX
mode within each sampling period (5s). Assume that the sum of these numbers within the
measurement period is A and the total number of sampling periods within the measurement
period is B. Then, VS.CPC.DTXCfg.UserNum = A/B.
During a measurement period, the NodeB counts the number of users that are configured in
UL_DTX mode and also employ discontinuous transmission in the uplink within each
sampling period (5s). Assume that the sum of these numbers within the measurement period
is C and the total number of sampling periods within the measurement period is D. Then,
VS.CPC.DTXAct.UserNum = C/D.
The VS.CPC.DTXCfg.UserNum counter is measured at point E and the
VS.CPC.DTXAct.UserNum counter is measured at point F in the following figure:
Figure 1-6
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters comply with section "6C.3 Discontinuous downlink reception" in
3GPP TS 25.214 (v10.10.0).
For more information about CPC, see section "9.2.2.64 Continuous Packet Connectivity
DTX-DRX Capability" in 3GPP TS 25.433 (v10.10.0).
For more information about DL_DRX, see section "6C.3 Discontinuous downlink reception"
in 3GPP TS 25.214 (v10.10.0).
Measurement Points
During a measurement period, the NodeB counts the number of users configured in DL_DRX
mode within each sampling period (5s). Assume that the sum of these numbers within the
measurement period is A and the total number of sampling periods within the measurement
period is B. Then, VS.CPC.DRXCfg.UserNum = A/B.
During a measurement period, the NodeB counts the number of users that are configured in
DL_DRX mode and also employ discontinuous reception in the downlink within each
sampling period (5s). Assume that the sum of these numbers within the measurement period
is C and the total number of sampling periods within the measurement period is D. Then,
VS.CPC.DRXAct.UserNum = C/D.
The VS.CPC.DRXCfg.UserNum counter is measured at point E and the
VS.CPC.DRXAct.UserNum counter is measured at point F in the following figure:
Figure 1-7
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters comply with section "6A.1.1 UE procedure for receiving HS-DSCH
and HS-SCCH in the CELL_DCH state" in 3GPP TS 25.214 (v10.10.0).
For more information about CPC, see section "9.2.2.64 Continuous Packet Connectivity
DTX-DRX Capability" in 3GPP TS 25.433 (v10.10.0).
For more information about LesOp, see section "6A.1.1 UE procedure for receiving HS-
DSCH and HS-SCCH in the CELL_DCH state" in 3GPP TS 25.214 (v10.10.0).
Measurement Points
The NodeB takes statistics about the preceding counters when MAC-hs/MAC-ehs scheduling
is complete.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.4.4 Activated CPC Enhancement-capable Users FDPCH DTX Act Ratio for
Using the Cell as Serving Cell in Cells
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the sum number of activated CPC enhancement-capable Users FDPCH
DTX Act Ratio for Using the Cell as Serving Cell in Cells,it can be using for CPC
Enhance(F-DPCH DTX) Active situation.
The following table describes the meanings of each counter.
Measurement Points
Within a measurement period, the time length for all activated CPC enhancement-capable
users in the serving cell is sampled every 5s, and the time length for all activated CPC
enhancement-capable users who adopt F-DPCH DTX in the serving cell is also sampled every
5s. At the end of a measurement period, the former sample value is accumulated and recorded
as A and the latter is recorded as B. Then, VS.CPC.FDPCHDTX.ActRatio = B/A. If there are
no CPC enhancement-capable users within a measurement period, the value of
VS.CPC.FDPCHDTX.ActRatio will be Null.
After CPC enhancement has been enabled, the number of activated CPC enhancement-
capable users is measured in the serving cell. For a DC-HSUPA user, this counter is measured
in the primary and secondary carriers separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of used common E-DCHs in a cell.
For more information about Common E-DCH, see section "3.1 Definitions" in 3GPP TS
25.319 (v11.7.0).
Measurement Points
The number of used common E-DCHs in a cell is sampled every five seconds. At the end of a
measurement period, the average number of used common E-DCHs is obtained by dividing
the accumulated value in the period by the number of samples. The maximum of these
sampling results is defined as the maximum number of used common E-DCHs in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the throughput of E-RACH users at the Mac-i layer within a
measurement period in a cell.
Measurement Points
This counter measures the total throughput of all E-RACH users at the Mac-i layer within a
measurement period.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
1.1.5.3 Number of TTIs in which E-RACH users have data to transmit in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs in which E-RACH users have data to transmit
within a measurement period in a cell.
Measurement Points
This counter measures the total number of TTIs in which E-RACH users have data to transmit
within a measurement period in a cell. If multiple E-RACH users have data to transmit within
a measurement period, this counter is incremented accordingly. For 2 ms TTI HSUPA users,
this counter is measured once. For 10 ms TTI HSUPA users, this counter is measured five
times.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of positive acknowledgments (with +1 acquisition
indicators (AIs)) in the preamble detection results of the primary cell that are reported by
coordinating cells when Coverage Expansion Under Interference is enabled.
This counter is used to evaluate the RACH RX performance of coordinating cells when the
Coverage Expansion Under Interference feature is enabled.
The following table describes the meanings of each counter.
Measurement Points
The number of positive acknowledgments (with +1 acquisition indicators (AIs)) in the
preamble detection results of the primary cell that are reported by coordinating cells within a
measurement period when Coverage Expansion Under Interference is enabled.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of negative acknowledgments (with =1 acquisition
indicators (AIs)) in the preamble detection results of the primary cell that are reported by
coordinating cells when Coverage Expansion Under Interference is enabled.
This counter is used to evaluate the RACH RX performance of coordinating cells when the
Coverage Expansion Under Interference feature is enabled.
Measurement Points
The number of negative acknowledgments (with -1 acquisition indicators (AIs)) in the
preamble detection results of the primary cell that are reported by coordinating cells within a
measurement period when Coverage Expansion Under Interference is enabled.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.6.3 Number of TBs obtained by the primary cell from the coordinating cells
with correct CRCs over the RACH
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TBs obtained by the primary cell from the coordinating
cells with correct CRCs over the RACH when Coverage Expansion Under Interference is
enabled.
This counter is used to evaluate the RACH RX performance of coordinating cells when the
Coverage Expansion Under Interference feature is enabled.
Measurement Points
The number of TBs obtained by the primary cell from the coordinating cells with correct
CRCs over the RACH within a measurement period when Coverage Expansion Under
Interference is enabled.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.6.4 Total number of TBs obtained by the primary cell from the coordinating
cells
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TBs obtained by the primary cell from the coordinating
cells with correct and incorrect CRCs over the RACH when Coverage Expansion Under
Interference is enabled.
This counter is used to evaluate the RACH RX performance of coordinating cells when the
Coverage Expansion Under Interference feature is enabled.
The following table describes the meanings of each counter.
Measurement Points
The number of TBs obtained by the primary cell from the coordinating cells with correct and
incorrect CRCs over the RACH within a measurement period when Coverage Expansion
Under Interference is enabled.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
VS.FPNum.Received.FACH is measured at point A. VS.FPNum.Discarded.FACH is
measured at point B. See the following figure:
Figure 1-8
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
VS.FPNum.Received.PCH is measured at point A. VS.FPNum.Discarded.PCH is measured at
point B. See the following figure:
Figure 1-9
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
VS.FPNum.Discarded.DCH and VS.FPNum.Late.DCH are measured at point B.
VS.FPNum.Received.DCH is measured at point A. See the following figure:
Figure 1-10
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.8.2 Number of Received or Sent Multiplexed DCH FP Data Frames for AMR
Services in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the accumulated number of sent (or received) UL (or DL) multiplexed
DCH FP data frames for AMR services within a measurement period in a cell where the AMR
Transmission Bandwidth Compress feature is effective. If the AMR Transmission Bandwidth
Compress feature is ineffective, the value of this counter is 0. The AMR Transmission
Bandwidth Compress feature applies only to AMR-NB services.
Measurement Points
When the AMR Transmission Bandwidth Compress feature is effective and AMR services are
carried over the DCH, this counter is measured if multiplexed DCH FP data frames are
received or sent in a cell. During multiplexing, multiple DCH FP data frames are multiplexed
into one FP data frame.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average ratio of the number of valid antennas to the number of
configured antennas.
This counter will be measured regardless of whether Anti-imbalance in the Interference of the
Different Antenna is enabled. In one of the following scenarios, the counter is not measured
and is directly reported as 1000:
Multiple RRUs share one cell, for example, in 0.5/0.5 configuration mode, distributed sector
configuration mode (digital combination and split), and cell with independent demodulation
of signals from multiple RRUs in one cell mode.
20 W RRU3801Cs are configured.
Cells are created on the WBBPa board.
Measurement Points
This counter is sampled every five seconds and measures the ratio of the number of valid
antennas to the number of configured antennas. The accumulated value is A, and the number
of samples is B. The formula for calculating the counter is as follows:
VS.ValidAntRatio.Mean=A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the ratio of the RTWP difference to the RTWP before interference
cancellation (IC) within a measurement period, reflecting stage 1 IC efficiency. The RTWP
difference indicates the difference between the RTWP before IC and the RTWP after stage 1
IC.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the
accumulated IC efficiency is A, and the accumulated number of samples is B. The formula for
calculating this counter is: VS.FirstStageIcEff.Mean = A/B. VS.FirstStageIcEff.Max
measures the maximum IC efficiency.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters indicate the average and maximum number of normalized downlink codes
used in a cell. The used codes are normalized using SF256. SF is short for spreading factor.
Used codes include the code resources used for the common channel, R99 channel, and HS-
DSCH. For example, if a code in SFk is normalized using SF256, the calculation formula is
256/k.
Measurement Points
Within a measurement period, the number of used codes is sampled in a cell every one
second. Then, the used codes are normalized using SF256. At the end of the measurement
period, the number of normalized codes used in a cell is accumulated. The accumulated value
divided by the number of samples is defined as the value of the VS.DlCode.Used.Mean
counter, and the maximum of these sampling results is defined as the value of the
VS.DlCode.Used.Max counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.9.4 Average Number of Users Enabled with DPCH Power Control Based on
Radio Quality in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of users enabled with the DPCH Power Control
Based on Radio Quality feature in a cell. This counter is used to evaluate whether the DPCH
Power Control Based on Radio Quality feature has taken effect.
Measurement Points
During a measurement period, the NodeB samples the number of users enabled with DPCH
Power Control Based on Radio Quality every 10 ms and records the accumulated value in the
measurement period as A, and counts the number of samples in the measurement period and
records the number as B. Then, VS.RadioQualityDPCHPC.UserNum = A/B.
For HSDPA users, the counter value is calculated in the serving cell. For MF-HSDPA users,
the counter value is calculated in the serving cell and assisting serving cell separately.
In a sampling period, a user is enabled with DPCH Power Control Based on Radio Quality if
the NodeB adjusts the transmit power of the associated DPCH for the user based on the
reported CQIs.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.9.5 Average Number of Users Enabled with F-DPCH Power Control Based on
Radio Quality in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of users enabled with the F-DPCH Power Control
Based on Radio Quality feature in a cell. This counter is used to evaluate whether the F-
DPCH Power Control Based on Radio Quality feature has taken effect.
Measurement Points
During a measurement period, the NodeB samples the number of users, on whom the F-
DPCH Power Control Based on Radio Quality feature takes effect and adjusts the transmit
power of the associated F-DPCH based on the reported CQIs, every 10 ms, and records the
accumulated value in the measurement period as A. The NodeB counts the number of samples
in the measurement period and records the number as B. Then,
VS.RadioQualityFDPCHPC.UserNum = A/B.
For HSDPA users, the counter value is calculated in the serving cell. For MF-HSDPA users,
the counter value is calculated in the serving cell and assisting serving cell separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of users enabled with AMR voice quality improvement
based on PLVA in a cell.
Measurement Points
This counter is sampled every five seconds. Assume that the total number of users enabled
with AMR voice quality improvement based on PLVA in a cell is A, and the number of
samples is B. VS.PLVA.User = A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of users using IRC in a cell.
The following table describes the meanings of each counter.
Measurement Points
During a measurement period, the NodeB samples the number of IRC users every 10 ms and
records the accumulated value in the measurement period as A, and counts the number of
samples in the measurement period and records the number as B. Then, VS.IRC.UserNum =
A/B.
IRC is used only in TTIs when users have data to transmit. If a user uses both DPDCH and E-
DPDCH for data transmission, the user is counted twice in the accumulated value A.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of HS-DPCCHs for CCPIC Phase 3 and E-
DPCCHs for CCPIC Phase 3 in a cell.
Measurement Points
With a measurement period, the number of HS-DPCCHs for CCPIC Phase 3 and E-DPCCHs
for CCPIC Phase 3 is sampled every five seconds in a cell. At the end of the measurement
period, the accumulated value of HS-DPCCHs for CCPIC Phase 3 is recorded as A, the
accumulated value of E-DPCCHs for CCPIC Phase 3 is recorded as A2, and the number of
samples is recorded as B. The sum of A1 and A2 divided by B is used as the value of the
VS.CCPICPhase3.CodNum.Mean counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of strong colored interferences is sampled every 5s. At the end of a measurement
period, the sum of these sampling results is recorded as A, and the number of samples is
recorded as B. Ratio of strong colored interference in a cell = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
1.1.9.10 Average Number of CoMP Users in a Host Cell Enabled with Coverage
Expansion Under Interference
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of CoMP users in a host cell enabled with
Coverage Expansion Under Interference. This counter indicates whether the Coverage
Expansion Under Interference feature has taken effect.
Measurement Points
This counter is sampled every 5 seconds. Assume that the measured number is A, and the
total number of samples within the measurement period is B. Then,
VS.UlCovExpansion.UserNum.HostCell = A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of users enabled with the 4-Way Receive Diversity
by Inter-Band Assistance feature in a cell. This counter is used to evaluate whether the 4-Way
Receive Diversity by Inter-Band Assistance feature has taken effect.
Measurement Points
Within a measurement period, the number of users enabled with 4-Way Receive Diversity by
Inter-Band Assistance is sampled every 5 seconds. At the end of a measurement period, the
accumulated number of these users is A, and the total number of samples is B. Then,
VS.Assistance4Rx.UserNum is A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the effective duration of the Narrowband Interference Suppression
feature in a cell.
Measurement Points
The NodeB checks the effective status of the Narrowband Interference Suppression feature
every 5s within a measurement period. If the feature is effective, this counter is incremented
by 5s. At the end of a measurement period, the effective duration of the Narrowband
Interference Suppression feature is calculated by accumulating the sampled values in the cell.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
1.1.9.13 Average number of users with DPCH TPC Power Adjustment enabled in
a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of users with DPCH TPC Power Adjustment
enabled in a cell.
Measurement Points
Within a measurement period, the number of users with DPCH TPC Power Adjustment
enabled is sampled every 100 ms. At the end of a measurement period, the accumulated
number of these users is A, and the number of samples is B. Then,
VS.DPCHTPCPwrAdj.UserNum is A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The interference decrease degree for an AIR-enabled cell is sampled every 100 ms. At the end
of a measurement period, the sum of these sampling results is recorded as A, and the number
Formula
None
Unit
dB
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average mumber of users enabled with Advanced Demodulation in
a cell. This counter is used to check whether the Voice Coverage Improvement by Advanced
Demodulation feature has taken effect.
The following table describes the meanings of each counter.
Measurement Points
The number of users enabled with the Voice Coverage Improvement by Advanced
Demodulation feature is sampled every 20 ms. At the end of a measurement period, the sum
of these sampling results is recorded as A, and the number of samples is recorded as B. Then,
VS.AdvancedDemodulation.User.Mean = A/B.
Note: If both functions involved in the Voice Coverage Improvement by Advanced
Demodulation feature are effective for a user, this counter is incremented by 2 on the user. For
users involved in soft handovers and softer handovers, this counter is separately measured in
each cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the average number of users enabled with Moving Speed-based
Adaptive Demodulation. This counter is used to evaluate the performance of the Moving
Speed-based Adaptive Demodulation feature and the feature gains.
Measurement Points
During a measurement period, the number of users using the Moving Speed-based Adaptive
Demodulation feature is sampled within each sampling period (10 ms). The sum of the
sampled users within the measurement period is recorded as A. The number of samples within
the measurement period is recorded as B.
VS.SpeedBasedDemod.UserNum = A/B
Note: DC-HSUPA users, soft handover users, and softer handover users are counted on cell-
specific links separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of users for CCPIC Phase 4 in a cell.
Measurement Points
With a measurement period, the number of users for CCPIC Phase 4 is sampled every five
seconds in a cell. At the end of the measurement period, the accumulated value of users for
CCPIC Phase 4 is recorded as A, and the number of samples is recorded as B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The number of times the AIR algorithm takes effect for a cell is sampled every 2 ms. At the
end of a measurement period, the total samples of AIR algorithm takes effect is recorded as
A, and the total number of times the AIR feature enabled is recorded as B. Ratio of AIR
algorithm takes effect for a cell = A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average number of GSM frequencies enabled with comb filtering in
a UMTS cell working on 3.8 MHz in the downlink.
Measurement Points
The number of GSM frequencies enabled with comb filtering in a UMTS cell working on 3.8
MHz in the downlink is measured every 30 ms. The total number is recorded as A. The
NodeB counts the number of sampling periods in the measurement period and records the
number as B. Then, VS.CombFilter.FreqNum.Mean = A/B.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average bandwidth of notched frequencies by baseband NBIS in a
cell.
The following table describes the meanings of each counter.
Measurement Points
When Uplink Adaptive Band-Pass Filter of WRFD-200201 GU@5 MHz Phase 2 takes effect,
the NodeB detects the frequencies with strong narrowband interference on RX antennas and
notches these frequencies to reduce uplink interference.During a measurement period, the
NodeB samples the bandwidth of notched frequencies by baseband NBIS and records the
accumulated value as A, and records the number of notching periods as B. Then,
VS.BasebandNBIS.Bandwidth.Mean = A/B.
Formula
None
Unit
kHz
Related Features
Counter Name Feature ID Feature Name
1.1.9.21 Average Number of Frequencies Enabled with Comb Filtering out of the
3.8 MHz Frequency Band in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average number of GSM frequencies enabled with comb filtering
between 3.8 MHz and 5 MHz in the downlink of a cell.
Measurement Points
Every 1/30 ms, the NodeB samples the number of GSM frequencies enabled with comb
filtering between 3.8 MHz and 5 MHz in the downlink of the cell and records the accumulated
value as A.The number of samples in a measurement period is recorded as B.
VS.CombFilterExtend.FreqNum.Mean = A/B
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter1 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter2 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
VS.CellReserve.Counter3 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter4 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter5 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter6 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter7 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter8 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter9 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter10 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter11 None.
Measurement Points
None
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter12 None.
Measurement Points
None
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.CellReserve.Counter13 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
VS.CellReserve.Counter14 None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Overview
The function subset consists of counters related to uplink load and downlink power.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
1.1.11.1 Average Ratio of DPCH and F-DPCH Transmit Power over Different SF
Code Channels to the Maximum Downlink Transmit Power in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the average ratio of DPCH and F-DPCH transmit power over
different SF code channels to the maximum downlink transmit power in a cell.
Measurement Points
The average permillage of DPCH and F-DPCH transmit power over different SF downlink
code channels to the maximum downlink transmit power in a cell is sampled every 200 ms.
At the end of a measurement period, the accumulated permillage is A, and the number of
samples is B. The formula for calculating this counter is A/B. If the cell is configured on the
WBBPa board, the value of this counter is 0.
Formula
None
Unit
per mill
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counter measures the uplink power loads of different services over control channels or
data channels within a measurement period in a cell.
The following table describes the meanings of each counter.
Measurement Points
This counter is sampled every 100 ms and measures the uplink power loads of different
services over control channels or data channels within a measurement period. The
accumulated value is A, and the number of samples is B. At the end of the measurement
period, the uplink power loads of different services over control channels or data channels are
calculated by dividing A by B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average ratio of downlink DCH transmit power for all users served
by each operator to the maximum cell transmit power in an MOCN network. DCH power
consumption indicates the power consumed for DPDCHs and DPCCHs and the power
consumed for F-DPCHs for HSDPA users in CELL_DCH state with SRB over HSDPA
enabled.
Measurement Points
Using VS.DCHPwrRatio.SharedOperator0 as an example, the ratio of downlink DCH
transmit power for all users served by the operator to the maximum cell transmit power is
sampled every 100 ms within a measurement period. At the end of the measurement period,
the accumulated value of the transmit power ratio is recorded as A, and the number of
samples is recorded as B. A divided by is used as the value of the
VS.DLDCHPwrRatio.SharedOperator0 counter.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Overview
The function subset consists of EFACH-related counters for a cell.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the number of TTIs in which the NodeB does not receive ACKs or
NACKs and receives ACKs and NACKs from E-FACH users over the HS-DPCCH in a cell.
The following table describes the meanings of each counter.
Measurement Points
The number of TTIs in which the NodeB does not receive ACKs or NACKs or receives
ACKs or NACKs from E-FACH users over the HS-DPCCH is sampled every 2 ms. At the
end of a measurement period, the sum of these sampling results is used as the value of the
corresponding counter. The corresponding counter will be measured repeatedly if the NodeB
does not receive ACKs or NACKs or receives ACKs or NACKs from more than one E-FACH
user within a TTI.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.12.2 Number of TTIs in Which E-FACH Users Have Data to Transmit in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs in which E-FACH users have data to transmit in a
cell.This counter needs to be measured repeatedly if more than one E-FACH user have data to
transmit within a TTI.
Measurement Points
The number of TTIs in which E-FACH users have data to transmit is sampled every 2 ms. At
the end of a measurement period, the sum of these sampling results is used as the value of this
counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the E-FACH user throughput at the MAC-ehs layer in a cell.
Measurement Points
The scheduling traffic volume of E-FACH users in a cell are accumulated within a
measurement period. The scheduling traffic volume includes the ACK scheduling traffic
volume when E-FACH users have HS-DPCCH feedbacks and the traffic volume of initial
transmission when E-FACH users have no HS-DPCCH feedbacks.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measures the average and maximum HS-SCCH transmit power of all E-FACH
users in a cell.
Measurement Points
The permillage of HS-SCCH transmit power for all E-FACH users to the maximum cell
transmit power is sampled every 2 ms within a TTI. At the end of a measurement period, the
accumulated permillage is A, and the number of TTIs is B. The formula for calculating
VS.EFACH.ScchPwrRatio.Mean is: VS.EFACH.ScchPwrRatio.Mean = A/B. This counter is
sampled every five seconds. At the end of a measurement period, the maximum sampling
results is used as the value of VS.EFACH.ScchPwrRatio.Max.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measures the average and maximum HS-PDSCH transmit power of all E-
FACH users in a cell.
Measurement Points
The permillage of HS-PDSCH transmit power for all E-FACH users to the maximum cell
transmit power is sampled every 2 ms within a TTI. At the end of a measurement period, the
accumulated permillage is A, and the number of TTIs is B. The formula for calculating
VS.EFACH.PdschPwrRatio.Mean is: VS.EFACH.PdschPwrRatio.Mean = A/B. This counter
is sampled every five seconds. At the end of a measurement period, the maximum sampling
results is used as the value of VS.EFACH.PdschPwrRatio.Max.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Overview
The function subset indicates the running status and performance of the HSDPA cell on a
NodeB. Unless otherwise stated, HSDPA users are those in the CELL_DCH state.Unless
otherwise stated, DB-HSDPA users are traditional DB-HSDPA users and inter-NodeB DB-
HSDPA users.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
Root Counter Level-1 Counter
VS.HSDPA.64QAMCfg.Traffic VS.HSDPA.64QAMCfg.Acted.Traffic
VS.HSDPA.DelaySensitive.DataOutput VS.HSDPA.DelaySensitive.DataOutput.Urg
ency
VS.HSDPA.ScheduleNum.DelaySensitive VS.HSDPA.ScheduleNum.DelaySensitive.B
lind
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of times different quantities of HS-PDSCH codes are used
in a cell, which explains the usage of HS-PDSCH codes.
Measurement Points
This counter counts the accumulated TTIs within which a specific number of HS-PDSCH
codes are used. Assume that the number of accumulated TTIs is A and the number of used
HS-PDSCH codes is x. Then, VS.HSDPA.PdschCodeUsed.x = A.
For example, VS.HSDPA.PdschCodeUsed.5 counts the accumulated TTIs within which five
HS-PDSCH codes are used.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of HSDPA users in a cell.
Measurement Points
Within a measurement period, the total number of HSDPA users in each TTI is recorded as A,
and the number of TTIs within the measurement period is recorded as B. The formula for
calculating the counter is: VS.AttRLSETUP.MEAN=A/B. A multicarrier user is regarded as
one HSDPA user in the anchor carrier and one HSDPA user in the supplementary carrier, and
this counter is measured in the two carriers separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
Number of HSDPA MAC-d PDUs (including those from E-FACH users and E-PCH users)
received over the Iub interface in a cell.
Measurement Points
This counter measures the number of HSDPA MAC-d PDUs (including those from E-FACH
users and E-PCH users) received over the Iub interface in a cell within a measurement period.
If there are multi-carrier users in the cell, PDUs of the anchor and supplementary carriers are
counted to the anchor carrier.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The traffic of MAC-ehs PDUs correctly transmitted by a 64QAM user in 64QAM mode and
received with ACKs is sampled in a cell. At the end of a measurement period, the sum of
these sampling results is defined as the value of the VS.HSDPA.64QAMCfg.Acted.Traffic
counter.
The traffic of MAC-ehs PDUs correctly transmitted by a 64QAM user and received with
ACKs is sampled in a cell. At the end of a measurement period, the sum of these sampling
results is defined as the value of the VS.HSDPA.64QAMCfg.Traffic counter.
For a multicarrier user, the corresponding counter is measured in the anchor and
supplementary carriers separately.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the number of samples for HSDPA users in a full buffer at different
throughput intervals, reflecting the distribution of the single HSDPA user throughput at these
throughput intervals.
After scheduling, HSDPA users have data to transmit in the full buffer.
Here,
Measurement Points
The downlink traffic of an HSDPA user is sampled every one second. Within a sampling
period, the accumulated value is recorded as A, and the duration in which HSDPA users have
data to transmit is recorded as B. In this counter, however, the traffic of HSDPA users having
no data to transmit in the full buffer after scheduling is not counted into A and the duration in
which HSDPA users having no data to transmit is not counted into B. At the end of the
sampling period, A divided by B is throughput of the HSDPA user, and the throughput is
counted into the corresponding throughput interval.For MC-HSDPA users, the counter is
measured in the corresponding scheduled cell.
Notes: The downlink traffic of an HSDPA user includes MAC-hs/MAC-ehs headers.
Figure 1-11
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
Delay sensitive BE services are PS interactive and PS background services that are delay
sensitive, for example, Skype.
Measurement Points
The traffic of MAC-hs/MAC-ehs sensitive delay BE services preferentially transmitted by an
HSDPA user and received with ACKs is sampled in a cell. At the end of a measurement
period, the sum of these sampling results is defined as the value of the
VS.HSDPA.DelaySensitive.DataOutput.Urgency counter.
For an MC-HSDPA user, the corresponding counter is measured in the anchor and
supplementary carriers separately.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
Delay sensitive BE services are PS interactive and PS background services that are delay
sensitive, for example, Skype.
Measurement Points
These counters are measured after MAC-hs/MAC-ehs scheduling completes. For an MIMO
user, if dual streams are used, these counters are measured twice; if a single stream is used,
these counters are measured once. For an MC user, these counters are measured in the anchor
and supplementary carriers separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The VS.HSDPA.NotSchedule.CQI0 counter is incremented by 1 in the HSDPA cell each time
an HSDPA user having data to transmit in the full buffer is not scheduled within a TTI
because CQI is 0.
The corresponding counter is measured multiple times if more than one user meets the
sampling requirement within a TTI. For a multicarrier user, the corresponding counter is
measured in the anchor and supplementary carriers separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.13.9 Number of Times the Next HSDPA User Cannot be Scheduled Due to
Resource Insufficiency in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
The VS.HSDPA.RemainResLimit.ScchCode counter is incremented by 1 in the HSDPA cell
each time an HSDPA user (including E-FACH users and E-PCH users) in the candidate set is
not scheduled within a TTI due to HS-SCCH insufficiency.
The VS.HSDPA.RemainResLimit.PdschCode counter is incremented by 1 in the HSDPA cell
each time an HSDPA user (including E-FACH users and E-PCH users) in the candidate set is
not scheduled within a TTI due to HS-PDSCH insufficiency.
The VS.HSDPA.RemainResLimit.HSDPAPwr counter is incremented by 1 in the HSDPA cell
each time an HSDPA user (including E-FACH users and E-PCH users) in the candidate set is
not scheduled within a TTI due to HS-PDSCH or HS-SCCH power insufficiency.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counter indicates the ratio of the traffic-based deactivation time of the
supplementary carrier to the activation time for 3C-HSDPA and 4C-HSDPA users whose
primary-carrier cell is the cell where the counter is measured. This counter is used to evaluate
the effect and benefits of the function of downlink traffic-based deactivation of the
supplementary carrier for 3C-HSDPA and 4C-HSDPA users.
Measurement Points
Within the measurement period, the NodeB calculates the total time during which the
supplementary carrier is deactivated because of decrease in throughput for each 3C-HSDPA
user and 4C-HSDPA user whose primary-carrier cell is the cell where the counter is
measured. Assume that the calculated value is A. The NodeB calculates the total time during
which each 3C-HSDPA user and 4C-HSDPA user is active (the active time for a user starting
from the establishment of a PS service and ending at the release of cell connection) in the
primary-carrier cell. Assume that the calculated value is B. Then,
VS.HSDPA.MCCfg.SupCarrierDeact.Traffic.TimeRatio = A/B.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total traffic volume of the MAC-hs/MAC-ehs PDUs successfully
received at all HSDPA users (including multicarrier users) whose anchor-carrier cell is the cell
where this counter is measured. When an HSDPA user successfully receives a MAC-hs/
MAC-ehs PDU, the HSDPA user responds with an ACK.
Measurement Points
The traffic volume of MAC-hs/MAC-ehs PDUs successfully received at all HSDPA users is
accumulated within a measurement period. This counter is measured for HSDPA users whose
anchor-carrier cell is the cell where this counter is measured. For DC-HSDPA, DB-HSDPA,
3C-HSDPA, and 4C-HSDPA users, the traffic volume of MAC-hs/MAC-ehs PDUs with
ACKs over all carriers are counted as being transmitted over the anchor carrier. In the SRB
over HSDPA scenario, when the SRB over HSDPA measurement optimization is enabled, this
counter does not measure the traffic volume of MAC-hs/MAC-ehs PDUs with ACKs received
from HSDPA users after the SRB-only data is scheduled. This counter complies with section
"6A HS-DSCH-related procedures" in 3GPP TS 25.214 (v8.3.0).
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs during which there is data to transmit in the queue
buffers for HSDPA users whose anchor-carrier cell is the cell where this counter is measured.
This counter does not repeatedly count the number of TTIs when multicarrier users have
concurrent buffered data in multiple cells. This counter repeatedly counts the number of TTIs
if more than one HSDPA user queue buffer has data to transmit within a TTI.
Measurement Points
The number of TTIs during which there is data to transmit in the HSDPA user queue buffers
is accumulated within a measurement period. This counter is measured for HSDPA users
whose anchor-carrier cell is the cell where this counter is measured. This counter repeatedly
counts the number of TTIs if more than one HSDPA user queue buffer has data to transmit
within a TTI. For DC-HSDPA, DB-HSDPA, 3C-HSDPA, and 4C-HSDPA users, this counter
is incremented by 1 in the anchor-carrier cell when such a user has data to transmit in the
queue buffer over any carrier. In the SRB over HSDPA scenario, when the SRB over HSDPA
measurement optimization is enabled, this counter does not measure the number of TTIs in
which HSDPA UEs have only SRB data to transmit in queue buffers.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total traffic volume of the MAC-hs/MAC-ehs PDUs transmitted to
all HSDPA users in a cell, including the successfully transmitted and retransmitted traffic
volume.
Measurement Points
The traffic volume of MAC-hs/MAC-ehs PDUs transmitted to all HSDPA users is
accumulated within a measurement period. The traffic volume includes the successfully
transmitted and retransmitted traffic volume. This counter is measured for HSDPA users
whose anchor-carrier cell is the cell where this counter is measured. For DC-HSDPA, DB-
HSDPA, 3C-HSDPA, and 4C-HSDPA users, this counter is measured over the anchor carrier
and supplementary carrier separately. This counter complies with section "6A HS-DSCH-
related procedures" in 3GPP TS 25.214 (v8.3.0).
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the distribution of CQIs reported by non-MIMO 64QAM
users in a cell.
The definition of CQI ranges is as follows:
CQI range 0: [0, 15]
CQI range 1: [16, 20]
CQI range 2: [21, 25]
CQI range 3: [26, 30].
Measurement Points
The NodeB takes statistics about the preceding counters after demodulating CQI information
of the 64QAM users carried on the HS-DPCCH. The total number of samples in each CQI
range is generated at the end of a measurement period. This counter is measured for 64QAM
users whose anchor-carrier cell is the cell where this counter is measured. For DC-HSDPA,
DB-HSDPA, 3C-HSDPA, and 4C-HSDPA users, this counter is measured over the anchor
carrier and supplementary carrier separately. This counter complies with section "6A.2
Channel quality indicator (CQI) definition" in 3GPP TS 25.214 (v8.3.0).
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.13.15 Number of TTIs within which the HSDPA cell uses shared power
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs within which an HSDPA user queue (including E-
FACH users and E-PCH users) uses the shared power.
Measurement Points
In a measurement period, this counter is incremented by 1 if one or more HSDPA user queues
(including E-FACH users and E-PCH users) use the shared power within the current TTI in a
cell. An HSDPA user queue has used the shared power when both of the following conditions
are met:
1. The HSDPA cell obtains the shared power from other cells within a TTI.
2. The HSDPA user queue uses the shared power from other cells after all HSDPA available
power in the cell is used up.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the total traffic volume of MAC-hs/MAC-ehs PDUs with ACKs
received from all HSDPA users performing soft handovers in a cell.
Measurement Points
The traffic volume of MAC-hs/MAC-ehs PDUs with ACKs received from all HSDPA users
performing soft handovers is accumulated within a measurement period. This counter is
measured in the serving cell. For DC-HSDPA, DB-HSDPA, 4C-HSDPA, or 3C-HSDPA users
whose anchor carrier has multiple RLSs, this counter is measured in the anchor carrier and
supplementary carrier separately.This counter is measured only when the RNC-level switches
specified by PC_ASYMMETRY_MEAS_SWITCH, PC_FP_MULTI_RLS_IND_SWITCH,
and PC_FP_MULTI_RLS_IND_SEND_TIME_OPT_SWITCH are all turned on.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
1.1.13.17 Total number of user-level TTIs within which there is data to transmit
in queue buffers of HSDPA users performing soft handovers
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs within which there is data to transmit in all queue
buffers of HSDPA users performing soft handovers. This counter needs to be measured
repeatedly if more than one such queue buffer has data to transmit within a TTI.
Measurement Points
The number of TTIs within which there is data to transmit in all queue buffers of HSDPA
users performing soft handovers is accumulated within a measurement period. This counter
will be measured repeatedly if more than one such queue buffer has data to transmit within a
TTI. This counter is measured in the serving cell. For DC-HSDPA, DB-HSDPA, 4C-HSDPA,
or 3C-HSDPA users whose anchor carrier has multiple RLSs, this counter is measured in the
anchor carrier and supplementary carrier separately.This counter is measured only when the
RNC-level switches specified by PC_ASYMMETRY_MEAS_SWITCH,
PC_FP_MULTI_RLS_IND_SWITCH, and
PC_FP_MULTI_RLS_IND_SEND_TIME_OPT_SWITCH are all turned on.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
During a measurement period, the NodeB calculates the total number of HSDPA video users
and prioritized HSDPA video users every 1s in a cell and records the accumulated number as
A and B, respectively. At the same time, the NodeB counts the number of sampling periods in
the measurement period and records the number as C. Then,
VS.HSDPA.VideoUserNum.Mean = A/C, VS.HSDPA.PrioritizedVideoUserNum.Mean =
B/C. Prioritized HSDPA video users are users whose CQI values are higher than the
configured video CQI threshold. For details, see Radio-Aware Video Precedence Feature
Parameter Description.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters indicate the TTI distribution for HSDPA users with throughput minus the
small data volume in a full buffer at different throughput intervals.
Users in a full buffer are HSDPA users who have data to transmit in the buffer before
scheduling but are not scheduled or still have data to transmit in the buffer after scheduling.
Measurement Points
The downlink data volume of an HSDPA user in a cell is sampled every one second and the
accumulated value within a sampling period is recorded as A. The duration in which HSDPA
data is transmitted within a sampling period is recorded as B. The downlink data volume in
TTIs for HSDPA users having no data to transmit in the full buffer after scheduling is not
counted into A. The TTIs in which HSDPA users having no data to transmit in the full buffer
after scheduling are not counted into B. If A is greater than or equal to the value of
HDSPAFullbufDataThd in the SET ULOCELLMACHSPARA command, A divided by B is
downlink throughput of the HSDPA user at the end of the sampling period. B of the HSDPA
user is accumulated to this counter in the corresponding throughput interval. For multicarrier
users, the counter is measured only over the primary carrier. That is, B is counted over the
primary carrier when HSDPA data is transmitted on any carrier for a multicarrier user.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters indicate the data volume distribution for HSDPA users with throughput minus
the small data volume in a full buffer at different throughput intervals.
Users in a full buffer are HSDPA users who have data to transmit in the buffer before
scheduling but are not scheduled or still have data to transmit in the buffer after scheduling.
Interval 0 ranges from 0 kbit/s to 512 kbit/s.
Interval 1 ranges from 512 kbit/s (included) to 1 Mbit/s.
Interval 2 ranges from 1 Mbit/s (included) to 2 Mbit/s.
Interval 3 ranges from 2 Mbit/s (included) to 3 Mbit/s.
Interval 4 ranges from 3 Mbit/s (included) to 4 Mbit/s.
Interval 5 ranges from 4 Mbit/s (included) to 5 Mbit/s.
Interval 6 ranges from 5 Mbit/s (included) to 7 Mbit/s.
Interval 7 ranges from 7 Mbit/s (included) to 10 Mbit/s.
Measurement Points
The downlink data volume of an HSDPA user in a cell is sampled every one second and the
accumulated value within a sampling period is recorded as A. The duration in which HSDPA
data is transmitted within a sampling period is recorded as B. The downlink data volume in
TTIs for HSDPA users having no data to transmit in the full buffer after scheduling is not
counted into A. The TTIs in which HSDPA users having no data to transmit in the full buffer
after scheduling are not counted into B. If A is greater than or equal to the value of
HDSPAFullbufDataThd in the SET ULOCELLMACHSPARA command, A divided by B is
downlink throughput of the HSDPA user at the end of the sampling period. A of the HSDPA
user is accumulated to this counter in the corresponding throughput interval. For multicarrier
users, the counter is measured only over the primary carrier. That is, A is counted over the
primary carrier when HSDPA data is transmitted on any carrier for a multicarrier user.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
1.1.13.21 Total TTIs in a Full Buffer for Single HSDPA Users with Throughput
Minus Small Data Volume Exceeding the Target Threshold
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters indicate the number of TTIs for HSDPA users with throughput minus the
small data volume in a full buffer.
Users in a full buffer are HSDPA users who have data to transmit in the buffer before
scheduling but are not scheduled or still have data to transmit in the buffer after scheduling.
Measurement Points
The downlink data volume of an HSDPA user in a cell is sampled every one second and the
accumulated value within a sampling period is recorded as A. The duration in which HSDPA
data is transmitted within a sampling period is recorded as B. The downlink data volume in
TTIs for HSDPA users having no data to transmit in the full buffer after scheduling is not
counted into A. The TTIs in which HSDPA users having no data to transmit in the full buffer
after scheduling are not counted into B. If A is greater than or equal to the value of
HDSPAFullbufDataThd in the SET ULOCELLMACHSPARA command, A divided by B is
downlink throughput of the HSDPA user at the end of the sampling period. If the calculated
downlink throughput is greater than or equal to HDSPAFullbufThrouThd in the SET
ULOCELLMACHSPARA command, B is accumulated to this counter for the HSDPA user.
For multicarrier users, the counter is measured only over the primary carrier. That is, B is
counted over the primary carrier when HSDPA data is transmitted on any carrier for a
multicarrier user.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.13.22 Total Data Volume in a Full Buffer for Single HSDPA Users with
Throughput Minus Small Data Volume Exceeding the Target Threshold
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter indicates the data volume for HSDPA users with throughput minus the small data
volume in a full buffer.
Users in a full buffer are HSDPA users who have data to transmit in the buffer before
scheduling but are not scheduled or still have data to transmit in the buffer after scheduling.
Measurement Points
The downlink data volume of an HSDPA user in a cell is sampled every one second and the
accumulated value within a sampling period is recorded as A. The duration in which HSDPA
data is transmitted within a sampling period is recorded as B. The downlink data volume in
TTIs for HSDPA users having no data to transmit in the full buffer after scheduling is not
counted into A. The TTIs in which HSDPA users having no data to transmit in the full buffer
after scheduling are not counted into B. If A is greater than or equal to the value of
HDSPAFullbufDataThd in the SET ULOCELLMACHSPARA command, A divided by B is
downlink throughput of the HSDPA user at the end of the sampling period. If the calculated
downlink throughput is greater than or equal to HDSPAFullbufThrouThd in the SET
ULOCELLMACHSPARA command, A is accumulated to this counter for the HSDPA user.
For multicarrier users, the counter is measured only over the primary carrier. That is, A is
counted over the primary carrier when HSDPA data is transmitted on any carrier for a
multicarrier user.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
Within a measurement period, the traffic volume of MAC-ehs PDUs with ACKs sent by all
inter-NodeB DB-HSDPA users in the anchor and supplementary carriers in a TTI is sampled.
At the end of the measurement period, the accumulated traffic volume is defined as the value
of the VS.DataOutput.NBDBHSDPA.Traffic counter.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
Within a measurement period, the number of TTIs in which an inter-NodeB DB-HSDPA user
queue has data to transmit in a cell is sampled. If more than one inter-NodeB DB-HSDPA
user queue has data to transmit in a TTI, the number of TTIs is counted repeatedly. At the end
of the measurement period, the accumulated number of TTIs is defined as the value of the
VS.NBDBHSDPA.DataTtiNum.User counter. This counter is measured for inter-NodeB DB-
HSDPA users whose anchor-carrier cell is the cell where this counter is measured.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
Within a measurement period, the traffic volume of MAC-ehs PDUs successfully transmitted
to all inter-NodeB DB-HSDPA users in the supplementary carrier is accumulated to this
counter in the anchor-carrier cell.
Formula
None
Unit
kbit
Related Features
Counter Name Feature ID Feature Name
1.1.13.26 Number of TTIs in Which HSDPA Cell Throughput Is Lower Than the
Target Threshold Due to Insufficient Scheduling Resources
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the number of TTIs in which HSDPA cell throughput is lower than
the target threshold due to insufficient scheduling resources in an HSDPA cell. The target
threshold for HSDPA cell throughput is specified by the HSDPACELLTHPTHD parameter.
Measurement Points
In an HSDPA cell, cell throughput is measured in each scheduling period. If cell throughput is
lower than the target threshold due to insufficient CQIs, the value of
VS.HSDPA.CellThroughput.UnderThd.CQILimit.TTINum is incremented by 1.
In an HSDPA cell, cell throughput is measured in each scheduling period. If cell throughput is
lower than the target threshold due to insufficient HSDPA power resources, the value of
VS.HSDPA.CellThroughput.UnderThd.PowerLimit.TTINum is incremented by 1.
In an HSDPA cell, cell throughput is measured in each scheduling period. If cell throughput is
lower than the target threshold due to insufficient HS-PDSCH codes, the value of
VS.HSDPA.CellThroughput.UnderThd.CodeLimit.TTINum is incremented by 1.
In an HSDPA cell, cell throughput is measured in each scheduling period. If cell throughput is
lower than the target threshold due to insufficient data sources, the value of
VS.HSDPA.CellThroughput.UnderThd.BufferLimit.TTINum is incremented by 1.
A multicarrier user is regarded as an HSDPA user in the anchor carrier and an HSDPA user in
the supplementary carrier, and this counter is incremented in the carriers separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the number of TTIs with buffered data to be transmitted in at least
one HSDPA user queue for an operator in a cell of an MOCN network.These counters are
added to accommodate the MOCN Cell Resource Demarcation feature.
Measurement Points
The TTIs, in which at least one HSDPA user queue has buffered data to transmit for one
operator in a cell, are sampled within a measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.13.28 Number of TTIs in which UEs in the scheduling candidate set are not
scheduled in an MOCN network
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure, for each operator, the number of TTIs in which HSDPA UEs are
added to the scheduling candidate set but the operator does not transmit data at the physical
layer because the operator's priority is lowered. These counters are added to accommodate the
MOCN Cell Resource Demarcation feature.
Measurement Points
In a TTI, HSDPA users served by an operator are added to the scheduling candidate set but
the operator does not transmit data at the physical layer because the scheduling priority of the
operator is lowered due to the MOCN scheduling sequencing algorithm. Such TTIs are
sampled within a measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of times an HSDPA user is scheduled with its scheduling
weight increased due to a small data buffer in a cell having two or more HSDPA user queues.
This counter is used to measure whether the buffer-based scheduling algorithm takes effect.
Measurement Points
The NodeB takes statistics about the counter for HSDPA users when MAC-hs/MAC-ehs
scheduling is complete. For MIMO users, if two transport blocks are used, the
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.13.30 Number of TTIs in Which Idle Codes are Available for HSDPA
Scheduling in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the number of TTIs in which inconsecutive idle codes are available for
HSDPA scheduling in a cell.
Measurement Points
In a measurement period, the NodeB counts the inconsecutive idle codes that can be used for
HSDPA scheduling in the code tree when the Dynamic Code Allocation Based on NodeB
feature takes effect. This counter is incremented by 1 each time an inconsecutive idle code is
found. The inconsecutive idle codes are counted every 2 ms within a measurement period and
the accumulated number is taken as the counter value at the end of the measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the volume of MAC-ehs PDUs that are correctly transmitted using
inconsecutive idle codes in a cell.
Measurement Points
In a measurement period, the NodeB counts the total MAC-hs/MAC-ehs PDUs received with
ACKs that are transmitted using inconsecutive idle codes for HSDPA scheduling. The MAC-
hs/MAC-ehs PDUs are counted every 2 ms and the accumulated number is taken as the
counter value at the end of the measurement period.
For an MC-HSDPA user, this counter is separately measured in the cells where the user is
scheduled.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the number of TTIs during which combined signal reception is
performed on the HS-DPCCH. This counter is used to evaluate whether the Inter-NodeB HS-
DPCCH CoMP (Joint Reception) feature takes effect.
Measurement Points
In the anchor cell enabled with the Inter-NodeB HS-DPCCH CoMP (Joint Reception) feature,
this counter is incremented by 1 within a measurement period if either of the following
criteria applies:
The ACK is unreliable in a TTI and user data becomes correctly received after the signals
from coordinating links are combined for reception.
The CQI is unreliable in a TTI and becomes reliable for data transmission after the signals
from coordinating links are combined for reception.
For multicarrier users, this counter is measured in the anchor carrier and the supplementary
carriers separately.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters provide the total traffic volume of the MAC-hs/MAC-ehs PDUs with
ACKs from all HSDPA users in different CQI ranges in a cell.
Measurement Points
Within a measurement period, the total traffic volume of the MAC-hs/MAC-ehs PDUs with
ACKs from all HSDPA users in different CQI ranges is incremented in a cell.
For multicarrier HSDPA users, these counters are measured in the anchor carrier and the
supplementary carriers separately.
For MIMO users, CQI ranges are specified based on single-stream CQIs. For details about
single-stream CQIs, see section "6A.2.2 CQI definition when the UE is configured in MIMO
mode" in 3GPP TS 25.214 (V11.6.0).
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
1.1.13.34 Number of User-level TTIs During Which HSDPA Users in Each CQI
Range Have Data to Transmit in Queue Buffers for Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters provide the number of TTIs during which HSDPA users in different
CQI ranges have data to transmit in the queue buffers in a cell. If multiple HSDPA users have
data to transmit in the queue buffer in a TTI, the TTI will be counted repeatedly.
Measurement Points
Within a measurement period, the total number of TTIs during which HSDPA users in
different CQI ranges have data to transmit in the queue buffers is incremented in a cell.
If multiple HSDPA users have data to transmit in the queue buffer in a TTI, the TTI will be
counted repeatedly.
For multicarrier HSDPA users, these counters are measured in the anchor carrier and the
supplementary carriers separately.
For MIMO users, CQI ranges are specified based on single-stream CQIs. For details about
single-stream CQIs, see section "6A.2.2 CQI definition when the UE is configured in MIMO
mode" in 3GPP TS 25.214 (V11.6.0).
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.13.35 Traffic correctly received by HSDPA users enabled with the best
retransmission scheduling algorithm in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total traffic volume of MAC-hs/MAC-ehs PDUs with ACKs
received from all HSDPA users enabled with the best retransmission scheduling algorithm in
a cell.
Measurement Points
This counter measures the total traffic volume of MAC-hs/MAC-ehs PDUs with ACKs
received from all HSDPA users enabled with the best retransmission scheduling algorithm
within a measurement period. This counter is measured in the serving cell. For multi-carrier
users, this counter is measured separately on the primary and secondary carriers.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
1.1.13.36 Number of ACKs received from all HSDPA users enabled with the best
retransmission scheduling algorithm in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the HARQ distribution of HSDPA users enabled with the best
retransmission scheduling algorithm in a cell.
Measurement Points
In a measurement period, for HSDPA users enabled with the best retransmission scheduling
algorithm, this counter is measured when the NodeB decodes the HARQ information carried
on the HS-DPCCH channel. The VS.Ack.RetraSch, VS.Nack.RetraSch, and VS.Dtx.RetraSch
counters are sampled when the HARQ information contains ACK, NACK, and DTX,
respectively. This counter is measured in the serving cell. For multi-carrier users, this counter
is measured separately on the primary and secondary carriers.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total traffic volume of the MAC-hs/MAC-ehs PDUs with ACKs for
SRB-only data received from all HSDPA users in a cell.
SRB-only: The scheduled MAC-hs/MAC-ehs PDU contains only SRB data and no TRB data.
Measurement Points
The traffic volume of the MAC-hs/MAC-ehs PDUs with ACKs for SRB-only data received
from all HSDPA users is accumulated within a measurement period. This counter is measured
in the serving cell. For multi-carrier users, this counter is measured separately on the primary
and secondary carriers.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
1.1.13.38 Number of user-level TTIs during which HSDPA UEs have SRB-only
data to transmit in queue buffers in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs within which there is only SRB data to transmit in
HSDPA user queue buffers. This counter needs to be measured repeatedly if more than one
HSDPA user queue buffer has only SRB data to transmit within a TTI.
SRB-only: The scheduled MAC-hs/MAC-ehs PDU contains only SRB data and no TRB data.
Measurement Points
This counter measures the number of TTIs in which there is only SRB-only data to transmit
by HSDPA users in the queue buffers within a measurement period. This counter needs to be
measured repeatedly if more than one HSDPA user has only SRB-only data to transmit in the
queue buffer within a TTI. This counter is measured in the serving cell. For multi-carrier
users, this counter is measured separately on the primary and secondary carriers.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.13.39 Number of times when the SRB-only data of the HSDPA UEs is
scheduled in a cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs within which only SRB data are scheduled for
HSDPA users in a cell. This counter needs to be measured repeatedly if more than one
HSDPA user has only SRB data to schedule within a TTI.
SRB-only: The scheduled MAC-hs/MAC-ehs PDU contains only SRB data and no TRB data.
Measurement Points
This counter is measured after the MAC-hs/MAC-ehs scheduling is complete. This counter
measures the number of TTIs within which only SRB data are scheduled for HSDPA users in
a cell. This counter needs to be measured repeatedly if more than one HSDPA user has only
SRB data to schedule within a TTI. This counter is measured in the serving cell. For multi-
carrier users, this counter is measured separately on the primary and secondary carriers.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TTIs with phase adjustment in operation periods of
Intelligent 2T VAM or MIMO Prime to evaluate the feature performance.
Measurement Points
Within a measurement period, the NodeB calculates the number of TTIs in which the number
of phase adjustments is not 0 in a cell enabled with Intelligent 2T VAM or MIMO Prime.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.1.13.41 Number of TTIs in Which Combined TFRC Takes Effect for HSDPA
UEs for Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the number of TTIs in which combined TFRC takes effect for HSDPA
users.
Measurement Points
In a measurement period, the NodeB performs TFRC in each TTI. After resource allocation is
complete for a UE in a cell, if there are still available code resources but unavailable power
resources and the next UE has data to transmit in the cell, the NodeB attempts to reconfigure
resources using combined TFRC.If the resource reconfiguration is successful in the current
TTI, this counter is incremented by 1.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average percentage of the HSDPA power used by a certain user
group in the total available HSDPA power in a cell.
Measurement Points
The NodeB samples the percentage of the TX power of all users in user group N on the HS-
SCCH and HS-PDSCH in the total available HSDPA power every 5s within a measurement
period. The sum of the sampling values at the end of a measurement period is recorded as
A.The number of sampling times in a measurement period is recorded as B. Then,
VS.HSDPAPwrRatio.UEGroupN = A/B.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
1.1.13.43 Average Percentage of the Duration in Which the HSDPA Power Usage
of User Group N Exceeds the Configured Threshold to in the Total Measurement
Duration in a Cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average percentage of the duration in which the HSDPA TX power
usage of a certain user group exceeds the configured threshold in the total measurement
duration in a cell.
Measurement Points
The NodeB samples the percentage of the TX power of all users in user group N on the HS-
SCCH and HS-PDSCH in the total available HSDPA power every 5s within a measurement
period. The sum of the sampling values at the end of a measurement period is recorded as A.
The total sampling duration in a measurement period is recorded as B.Then,
VS.HSDPATimeRatio.PwrOver.UEGroupN = A/B.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average percentage of the duration in which the HSDPA TX power
usage of a certain user group exceeds the configured threshold in the total measurement
duration in a cell.
Measurement Points
The NodeB samples the percentage of the TX power of all users in user group N on the HS-
SCCH and HS-PDSCH every 5s within a measurement period. The percentage that exceeds
the threshold configured for this user group is summed up and recorded as A.The number of
times when the percentage exceeds the configured threshold within a measurement period is
recorded as B.VS.HSDPAPwrRatio.PwrOver.UEGroupN=A/B. Then,
VS.HSDPAPwrRatio.PwrOver.UEGroupN = A/B.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and maximum of RL Setup Request per second
during a measurement period.
The preceding counters comply with section "8.2.17 Radio Link Setup" in 3GPP TS 25.433
(v10.10.0).
Measurement Points
Within a measurement period, the number of RL SETUP REQUEST messages per second is
recorded as A, and the number of seconds within the measurement period is recorded as B.
VS.AttRLSETUP.MEAN=A/B. VS.AttRLSETUP.MEAN is sampled every five seconds. At
the end of the measurement period, the maximum of these sampling results is used as the
value of VS.AttRLSETUP.MAX.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and maximum of RL Add Request per second
during a measurement period.
The preceding counters comply with section "8.3.1 Radio Link Addition" in 3GPP TS 25.433
(v10.10.0).
Measurement Points
Within a measurement period, the number of RL ADD REQUEST messages per second is
recorded as A, and the number of seconds within the measurement period is recorded as B.
VS.AttRLADD.MEAN=A/B. VS.AttRLADD.MEAN is sampled every five seconds. At the
end of the measurement period, the maximum of these sampling results is used as the value of
VS.AttRLADD.MAX.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and maximum of RL Reconfiguration
Preparation Request per second during a measurement period.
The preceding counters comply with section "8.3.2 Synchronised Radio Link Reconfiguration
Preparation" in 3GPP TS 25.433 (v10.10.0).
Measurement Points
Within a measurement period, the number of RL RECONFIGUATION PREPARE messages
per second is recorded as A, and the number of seconds within the measurement period is
recorded as B. VS.AttRLRecfg.MEAN=A/B. VS.AttRLRecfg.MEAN is sampled every five
seconds. At the end of the measurement period, the maximum of these sampling results is
used as the value of VS.AttRLRecfg.MAX.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and maximum of Dedicated Measurement
Reporting per second during a measurement period.
The preceding counters comply with section "8.3.9 Dedicated Measurement Reporting" in
3GPP TS 25.433 (v10.10.0).
Measurement Points
Within a measurement period, the number of DEDICATED MEASUREMENT REPORT
messages per second is recorded as A, and the number of seconds within the measurement
period is recorded as B. VS.DedicMeaRpt.MEAN=A/B. VS.DedicMeaRpt.MEAN is sampled
every five seconds. At the end of the measurement period, the maximum of these sampling
results is used as the value of VS.DedicMeaRpt.MAX.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
For each of the preceding counters, the NodeB takes statistics about the available UL
(outgoing from the NodeB) bandwidth of an ATM physical port during a measurement period.
If the physical port carries an IMA group, the value of the counter is the total UL bandwidth
of the available IMA links in the IMA group. If the physical port is an STM-1 port or carries a
UNI or fractional ATM link, the value of the counter is the available UL bandwidth of the
physical port. The NodeB can take statistics on these counters for a maximum of four ATM
physical ports. One counter is specific for one physical port, and one physical port
corresponds to one counter. That is, the counters and the physical ports have a one-to-one
relation between each other. These counters are identical in application, since they are all used
for traffic measurement at the physical layer.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
For each of the preceding counters, the NodeB takes statistics about the available DL
(incoming to the NodeB) bandwidth of an ATM physical port during a measurement period. If
the physical port carries an IMA group, the value of the counter is the total DL bandwidth of
the available IMA links in the IMA group. If the physical port is an STM-1 port or carries a
UNI or fractional ATM link, the value of the counter is the available DL bandwidth of the
physical port. The NodeB can take statistics on these counters for a maximum of four ATM
physical ports. One counter is specific for one physical port, and one physical port
corresponds to one counter. That is, the counters and the physical ports have a one-to-one
relation between each other. These counters are identical in application, since they are all used
for traffic measurement at the physical layer.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The following table describes the meanings of each counter.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB reports traffic statistics of logical ports that carry PATH. The NodeB takes the
traffic statistics on these counters for a maximum of two logical ports and it preferentially
reports the statistics for IP transmission. If no more than two logical ports exists, the NodeB
reports only the traffic statistics of logical ports that carry PATH. One logical port is
associated with one resource group. The default resource group number is 1. LgcPort1
measures traffic of the resource group created firstly, and LgcPort2 measures traffic of the
resource group created secondly. The traffic of the resource group includes the traffic of all
paths to which the resource group belongs. For an IP&ATM network: If the IP resource group
is created prior to the ATM resource group, lgcPort1 will report the traffic of the IP resource
group, and lgcPort2 will report the traffic of the ATM resource group. If the ATM resource
group is created prior to the IP resource group, lgcPort1 will report the traffic of the ATM
resource group, and lgcPort2 will report the traffic of the IP resource group. Usually,
LgcPort1 reports the traffic of the IP resource group and LgcPort2 reports the traffic of the
ATM resource group. However, the mapping is not fixed, and it is determined by the sequence
of creating the resource groups.
The following table describes the meanings of each counter.
Disuse Statement:
In the current version, either this counter VS.IUB.FlowCtrol.UL.AdjBW.LgcPort1.Max or the
VS.RscGroup.FlowCtrol.UL.AdjBW.Max counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.UL.AdjBW.Max counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.AdjBW.LgcPort1.Min or the
VS.RscGroup.FlowCtrol.UL.AdjBW.Min counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.UL.AdjBW.Min counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.AdjBW.LgcPort1.Avg or the
VS.RscGroup.FlowCtrol.UL.AdjBW.Avg counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.UL.AdjBW.Avg counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.AdjBW.LgcPort2.Max or the
VS.RscGroup.FlowCtrol.UL.AdjBW.Max counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version, only the VS.RscGroup.FlowCtrol.UL.AdjBW.Max counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.AdjBW.LgcPort2.Min or the
VS.RscGroup.FlowCtrol.UL.AdjBW.Min counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version, only the VS.RscGroup.FlowCtrol.UL.AdjBW.Min counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.AdjBW.LgcPort2.Avg or the
VS.RscGroup.FlowCtrol.UL.AdjBW.Avg counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.UL.AdjBW.Avg counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.This counter
only include the payload of IP packets.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB reports the traffic statistics of logic ports that carry PATH. The NodeB can take
the traffic statistics on these counters for a maximum of two logic ports and it preferentially
reports the statistics for IP transmission. If only one logic port is configured, the traffic
statistics of only one logic port is reported.
The following table describes the meanings of each counter.
Disuse Statement:
In the current version, either this counter VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Max or the
VS.RscGroup.FlowCtrol.DL.AdjBW.Max counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.DL.AdjBW.Max counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Min or the
VS.RscGroup.FlowCtrol.DL.AdjBW.Min counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.DL.AdjBW.Min counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.This counter
only include the payload of IP packets. If the IP path is carried on loopback interface, the
value of this counter is the total available DL bandwidth on the current loopback interface.
(The default DL bandwidth on the loopback interface is 1 Gbit/s.)
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB calculates the number of attempts to increase the available UL bandwidth of the
NodeB IUB logic port per five seconds. All collection values in a statistics period are
accumulated. The NodeB reports the traffic statistics of logic ports that carry PATH. The
NodeB can take the traffic statistics on these counters for a maximum of two logic ports and it
preferentially reports the statistics for IP transmission. If only one logic port is configured, the
traffic statistics of only one logic port is reported.
Disuse Statement:
In the current version, either this counter VS.IUB.FlowCtrol.UL.UpBW.Num.LgcPort1 or the
VS.RscGroup.FlowCtrol.UL.UpBW.Num counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.UL.UpBW.Num counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.UpBW.Num.LgcPort2 or the
VS.RscGroup.FlowCtrol.UL.UpBW.Num counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version, only the VS.RscGroup.FlowCtrol.UL.UpBW.Num counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.2.1.12 IUB logic port DL HSDPA available bandwidth increase times after jitter
congestion released
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB
calculates the number of attempts to increase the available DL MAC-HS layer bandwidth
after the congestion caused by jitter is released. When other algorithms are used, the NodeB
reports 0 as the statistics value. All collected values in a statistics period are accumulated. The
NodeB reports the traffic statistics of logic ports that carry PATH. The NodeB can take the
traffic statistics on these counters for a maximum of two logic ports and it preferentially
reports the statistics for IP transmission. If only one logic port is configured, the traffic
statistics of only one logic port is reported.
Disuse Statement:
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.2.1.13 IUB logic port DL HSDPA available bandwidth increase times after
packet loss congestion released
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB
calculates the number of attempts to increase the available DL MAC-HS layer bandwidth
after the congestion caused by packet loss is released. When other algorithms are used, the
NodeB reports 0 as the statistics value. All collected values in a statistics period are
accumulated. The NodeB reports the traffic statistics of logic ports that carry PATH. The
NodeB can take the traffic statistics on these counters for a maximum of two logic ports and it
preferentially reports the statistics for IP transmission. If only one logic port is configured, the
traffic statistics of only one logic port is reported.
Disuse Statement:
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.2.1.14 IUB logic port available UL bandwidth decrease times for jitter
congestion
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB calculates the number of attempts to decrease the available UL physical layer
bandwidth of the NodeB IUB logic port due to jitter per five seconds. All collected values in a
statistics period are accumulated. The NodeB reports the traffic statistics of logic ports that
carry PATH. The NodeB can take the traffic statistics on these counters for a maximum of two
logic ports and it preferentially reports the statistics for IP transmission. If only one logic port
is configured, the traffic statistics of only one logic port is reported.
Disuse Statement:
In the current version, either this counter
VS.IUB.FlowCtrol.UL.DelayCong.DownBWNum.LgcPort1 or the
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.2.1.15 IUB logic port DL HSDPA available bandwidth decrease times for jitter
congestion
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB
calculates the number of attempts to decrease the available DL MAC-HS layer bandwidth of
the NodeB IUB logic port due to jitter. When other algorithms are used, the NodeB reports 0
as the statistics value. All collected values in a statistics period are accumulated. The NodeB
reports the traffic statistics of logic ports that carry PATH. The NodeB can take the traffic
statistics on these counters for a maximum of two logic ports and it preferentially reports the
statistics for IP transmission. If only one logic port is configured, the traffic statistics of only
one logic port is reported.
Disuse Statement:
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.2.1.16 IUB logic port available UL bandwidth decrease times for packet loss
congestion
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB calculates the number of attempts to decrease the available UL physical layer
bandwidth of the NodeB IUB logic port due to packet loss per five seconds. All collected
values in a statistics period are accumulated. The NodeB reports the traffic statistics of logic
ports that carry PATH. The NodeB can take the traffic statistics on these counters for a
maximum of two logic ports and it preferentially reports the statistics for IP transmission. If
only one logic port is configured, the traffic statistics of only one logic port is reported.
Disuse Statement:
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.2.1.17 IUB logic port DL HSDPA available bandwidth decrease times for packet
loss congestion
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB
calculates the number of attempts to decrease the available DL MAC-HS layer bandwidth of
the NodeB IUB logic port due to packet loss. When other algorithms are used, the NodeB
reports 0 as the statistics value. All collected values in a statistics period are accumulated. The
NodeB reports the traffic statistics of logic ports that carry PATH. The NodeB can take the
traffic statistics on these counters for a maximum of two logic ports and it preferentially
reports the statistics for IP transmission. If only one logic port is configured, the traffic
statistics of only one logic port is reported.
Disuse Statement:
In the current version, either this counter
VS.IUB.FlowCtrol.DL.DropCong.DownBWNum.LgcPort1 or the
VS.RscGroup.FlowCtrol.DL.DropCong.DownBWNum counter is used, or they can both be
used. The reported value of this counter is normal but this counter is not recommended for
use. In a later version , only the VS.RscGroup.FlowCtrol.DL.DropCong.DownBWNum
counter is used.
In the current version, either this counter
VS.IUB.FlowCtrol.DL.DropCong.DownBWNum.LgcPort2 or the
VS.RscGroup.FlowCtrol.DL.DropCong.DownBWNum counter is used, or they can both be
used. The reported value of this counter is normal but this counter is not recommended for
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB calculates the number of frames that are successfully sent through the NodeB IUB
logic port per five seconds. All calculation values in a statistics period are accumulated. The
NodeB reports the traffic statistics of logic ports that carry PATH. The NodeB can take the
traffic statistics on these counters for a maximum of two logic ports and it preferentially
reports the statistics for IP transmission. If only one logic port is configured, the traffic
statistics of only one logic port is reported.
Disuse Statement:
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB
calculates the number of frames that are successfully received through the NodeB IUB logic
port. When other algorithms are used, the NodeB reports 0 as the statistics value. All collected
values in a statistics period are accumulated. The NodeB reports the traffic statistics of logic
ports that carry PATH. The NodeB can take the traffic statistics on these counters for a
maximum of two logic ports and it preferentially reports the statistics for IP transmission. If
only one logic port is configured, the traffic statistics of only one logic port is reported.
Disuse Statement:
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB calculates the number of UL frames that are discarded by the NodeB IUB logic
port per five seconds. All calculation values in a statistics period are accumulated. The NodeB
reports the traffic statistics of logic ports that carry PATH. The NodeB can take the traffic
statistics on these counters for a maximum of two logic ports and it preferentially reports the
statistics for IP transmission. If only one logic port is configured, the traffic statistics of only
one logic port is reported.
Disuse Statement:
reported value of this counter is normal but this counter is not recommended for use. In a later
version, only the VS.RscGroup.FlowCtrol.UL.DropNum counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB
calculates the number of DL frames that are lost on the NodeB IUB logic port. These DL
HSDPA frames are discarded by the RNC interface board, intermediate transmission links, or
the NodeB. When other algorithms are used, the NodeB reports 0 as the statistics value. All
collected values in a statistics period are accumulated. The NodeB reports the traffic statistics
of logic ports that carry PATH. The NodeB can take the traffic statistics on these counters for
a maximum of two logic ports and it preferentially reports the statistics for IP transmission. If
only one logic port is configured, the traffic statistics of only one logic port is reported.
Disuse Statement:
In the current version , either this counter VS.IUB.FlowCtrol.DL.DropNum.LgcPort1 or the
VS.RscGroup.FlowCtrol.DL.DropNum counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version, only the VS.RscGroup.FlowCtrol.DL.DropNum counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.DL.DropNum.LgcPort2 or the
VS.RscGroup.FlowCtrol.DL.DropNum counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.DL.DropNum counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB reports the traffic statistics of logic ports that carry PATH. The NodeB can take
the traffic statistics on these counters for a maximum of two logic ports and it preferentially
reports the statistics for IP transmission. If only one logic port is configured, the traffic
statistics of only one logic port is reported.
The following table describes the meanings of each counter.
Disuse Statement:
In the current version, either this counter VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Max or
the VS.RscGroup.FlowCtrol.UL.DelayVara.Max counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.UL.DelayVara.Max counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Min or
the VS.RscGroup.FlowCtrol.DL.DropNum counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.DL.DropNum counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Avg or
the VS.RscGroup.FlowCtrol.UL.DelayVara.Avg counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.UL.DelayVara.Avg counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2.Max or
the VS.RscGroup.FlowCtrol.UL.DelayVara.Max counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version, only the VS.RscGroup.FlowCtrol.UL.DelayVara.Max counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2.Min or
the VS.RscGroup.FlowCtrol.UL.DelayVara.Min counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.UL.DelayVara.Min counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2.Avg or
the VS.RscGroup.FlowCtrol.UL.DelayVara.Avg counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.UL.DelayVara.Avg counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB reports the traffic statistics of logic ports that carry PATH. The NodeB can take
the traffic statistics on these counters for a maximum of two logic ports and it preferentially
reports the statistics for IP transmission. If only one logic port is configured, the traffic
statistics of only one logic port is reported.
The following table describes the meanings of each counter.
Disuse Statement:
In the current version, either this counter VS.IUB.FlowCtrol.DL.DelayVara.LgcPort1.Max or
the VS.RscGroup.FlowCtrol.DL.DelayVara.Max counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.DL.DelayVara.Max counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.DL.DelayVara.LgcPort1.Min or
the VS.RscGroup.FlowCtrol.DL.DelayVara.Min counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.DL.DelayVara.Min counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.DL.DelayVara.LgcPort1.Avg or
the VS.RscGroup.FlowCtrol.DL.DelayVara.Avg counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.DL.DelayVara.Avg counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.DL.DelayVara.LgcPort2.Max or
the VS.RscGroup.FlowCtrol.DL.DelayVara.Max counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.DL.DelayVara.Max counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.DL.DelayVara.LgcPort2.Min or
the VS.RscGroup.FlowCtrol.DL.DelayVara.Min counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version, only the VS.RscGroup.FlowCtrol.DL.DelayVara.Min counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.DL.DelayVara.LgcPort2.Avg or
the VS.RscGroup.FlowCtrol.DL.DelayVara.Avg counter is used, or they can both be used.
The reported value of this counter is normal but this counter is not recommended for use. In a
later version , only the VS.RscGroup.FlowCtrol.DL.DelayVara.Avg counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The NodeB determines whether the following requirement is met:
VS.IUB.FlowCtrol.UL.AdjBW.LgcPort.Avg*0.8 less than Actual physical layer flow of the
UL logic port. If the preceding requirement is met, the UL congestion duration is increased by
one second. If the preceding requirement is not met, the UL congestion duration does not
change. The NodeB collects the UL congestion duration per five seconds. All collected values
in a statistics period are accumulated. The NodeB reports the traffic statistics of logic ports
that carry PATH. The NodeB can take the traffic statistics on these counters for a maximum of
two logic ports and it preferentially reports the statistics for IP transmission. If only one logic
port is configured, the traffic statistics of only one logic port is reported.Under certain
circumstances, the value of this counter may have an error of one measurement period (5
seconds).
Disuse Statement:
In the current version, either this counter VS.IUB.FlowCtrol.UL.CongTime.LgcPort1 or the
VS.RscGroup.FlowCtrol.UL.CongTime counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.UL.CongTime counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.UL.CongTime.LgcPort2 or the
VS.RscGroup.FlowCtrol.UL.CongTime counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.UL.CongTime counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
When the DYNAMIC_BW_SHAPING algorithm is enabled in complete sharing mode of
configured bandwidth, the NodeB determines whether the following requirement is met:
VS.IUB.FlowCtrol.DL.AdjBW.LgcPort.Avg*0.8 less than HSDPA flow of the DL logic port.
If the preceding requirement is met, the DL congestion duration is increased by one second. If
the preceding requirement is not met, the DL congestion duration does not change. The
NodeB calculates the DL congestion duration per five seconds. When other algorithms are
used, the NodeB reports 0 as the calculation value. All collected values in a statistics period
are accumulated. The NodeB reports the traffic statistics of logic ports that carry PATH. The
NodeB can take the traffic statistics on these counters for a maximum of two logic ports and it
preferentially reports the statistics for IP transmission. If only one logic port is configured, the
traffic statistics of only one logic port is reported.Under certain circumstances, the value of
this counter may have an error of one measurement period (5 seconds).
Disuse Statement:
In the current version, either this counter VS.IUB.FlowCtrol.DL.CongTime.LgcPort1 or the
VS.RscGroup.FlowCtrol.DL.CongTime counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.DL.CongTime counter is used.
In the current version, either this counter VS.IUB.FlowCtrol.DL.CongTime.LgcPort2 or the
VS.RscGroup.FlowCtrol.DL.CongTime counter is used, or they can both be used. The
reported value of this counter is normal but this counter is not recommended for use. In a later
version , only the VS.RscGroup.FlowCtrol.DL.CongTime counter is used.
Measurement Points
For the preceding counters, the NodeB takes statistics in each scheduling period.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of available downlink CEs for hardware in the NodeB
within a measurement period.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the
maximum of these sampling results is defined as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of available uplink CEs for hardware in the NodeB within
a measurement period.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the
maximum of these sampling results is defined as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the HSDPA user load sharing duration when the HSDPA Scheduler
Pool feature takes effect.
Measurement Points
This counter measures the HSDPA user load sharing every 5s within a measurement period. If
HSDPA users are offloaded form one HSDPA scheduler (board) to another one, this counter is
incremented by 5s. In a measurement period, the sampling duration is accumulated.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the HSUPA user load sharing duration when the HSUPA Scheduler
Pool feature takes effect.
Measurement Points
This counter measures the HSUPA user load sharing every 5s within a measurement period. If
HSUPA users are offloaded form one HSUPA scheduler (board) to another one, this counter is
incremented by 5s. In a measurement period, the sampling duration is accumulated.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the average and maximum ratio of using CNBAP capabilities of the
NodeB.
Measurement Points
CNBAP capabilities supported by NodeB hardware are sampled every five seconds. Within a
measurement period, the average number of received radio links per second divided by
CNBAP capabilities supported by NodeB hardware is the ratio of using CNBAP capabilities
of the NodeB. At the end of the measurement period, the average of these sampling results is
defined as the value of the VS.BTS.CnbapCap.UseRate counter, the maximum of these
sampling results is defined as the value of the VS.BTS.CnbapCap.MaxUseRate counter.
Formula
None
Unit
%
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total number of radio link setup rejections because the number of
processed radio links exceeds the licensed capacity within a measurement period. The total
number of processed radio links corresponds to the CNBAP times for the three types of
signaling messages that are indicative of processed radio link setup requests in the NodeB,
radio link addition requests in the NodeB, and radio link reconfiguration preparations in the
NodeB.
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 Points
The measurement is triggered when the request for radio link setup is rejected because the
CNBAP times of processed radio link setup requests in the NodeB, radio link addition
requests in the NodeB, and radio link reconfiguration preparations in the NodeB is beyond the
licensed capacity.
As shown in point A in the following figure, this counter is incremented by 1 each time the
request for radio link setup is rejected because the number of processed radio links is beyond
the licensed capacity after the NodeB receives a RADIO LINK SETUP REQUEST message
from the RNC.
Figure 1-12
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters meansure the number of CNBAP times the NodeB receives radio link setup
requests over the Iub interface, radio link addition requests over the Iub interface, and radio
link recofniguration preparations over the Iub interface.
The preceding counters comply 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 Points
Within a measurement period, this counter is incremented each time the NodeB receives a
radio link setup request over the Iub interface, a radio link addition request over the Iub
interface, or a radio link reconfiguration preparation over the Iub interface.
As shown in point A in Figure 1, the counter is incremented each time the NodeB receives a
RADIO LINK SETUP REQUEST message from the RNC.
As shown in point A in Figure 2, the counter is incremented each time the NodeB receives a
RADIO LINK ADDITION REQUEST message from the RNC.
As shown in point A in Figure 3, the counter is incremented each time the NodeB receives a
RADIO LINK RECONFIGURATION PREPARE message from the RNC.
At the end of a measurement period, the average number of received radio links is obtained by
dividing the accumulated value in the period by the number of samples. The maximum of
these sampling results is defined as the maximum number of received radio links per second.
Figure 1-13
Figure 1-14
Figure 1-15
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of CNBAP times the NodeB successfully processes radio
link setup requests, radio link addition requests, and radio link reconfiguration preparations.
The number of rejections due to control plane congestion is not counted into the counter.
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 Points
Within a measurement period, this counter is incremented each time the NodeB receives a
radio link setup request over the Iub interface, a radio link addition request over the Iub
interface, or a radio link reconfiguration preparation over the Iub interface and no radio link
setup request is rejected due to congestion on the control plane.
As shown in point A in Figure 1, this counter is incremented each time the NodeB does not
reject the RADIO LINK SETUP REQUEST message even though the control plane is
congested.
As shown in point A in Figure 2, this counter is incremented each time the NodeB does not
reject the RADIO LINK ADDITION REQUEST message even though the control plane is
congested.
As shown in point A in Figure 3, this counter is incremented each time the NodeB does not
reject the RADIO LINK RECONFIGURATION PREPARE message even though the control
plane is congested.
This counter is sampled every five seconds. The average number of processed radio links per
second is obtained within each measurement period, and then the maximum of these sampling
results is defined as the value of the counter.
Figure 1-16
Figure 1-17
Figure 1-18
Formula
None
Unit
None
Related Features
None
1.2.3.5 Total number of times radio link setup requests are rejected because of
control plane congestion (CPU overload) within a measurement period
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total number of radio link setup rejections in the NodeB due to
congestion on the control plane, that is, CPU overload.
This counter complies with section "8.2.17 Radio Link Setup" in 3GPP TS 25.433 (v10.10.0).
Measurement Points
As shown in point A in the following figure, this counter is incremented by 1 each time the
NodeB receives a radio link setup rejection due to congestion on the control plane.
Figure 1-19
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the sum of received coordinating link setup requests over the Iub
interface, coordinating link addition requests over the Iub interface, and doubled coordinating
link reconfiguration preparations over the Iub interface. The number of request rejections due
to congestion on the NodeB control plane is not counted into this counter.
Measurement Points
Within a measurement period, this counter is measured every 5 seconds each time the NodeB
receives a coordinating link setup request from the RNC over the Iub interface, a coordinating
link addition request over the Iub interface, or a coordinating link reconfiguration preparation
over the Iub interface, and the request is not rejected due to congestion on the control plane.
At the end of the measurement period, the average number of received coordinating links is
obtained by dividing the sum of these sampling results in the period by the number of
samples.The maximum of these sampling results is defined as the maximum number of
received coordinating links.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.NodeBReserve.Counter1.NodeB None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.NodeBReserve.Counter2.NodeB None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.NodeBReserve.Counter3.NodeB None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.NodeBReserve.Counter4.NodeB None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
VS.NodeBReserve.Counter5.NodeB None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Overview
The function subset measures the transmission bandwidth and rate on the NodeB user plane
and control plane.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the number of user-plane and control-plane IP packets transmitted
and received at the IP layer over the Iub interface with a measurement period, respectively.
For user-plane IP packets transmitted, only these packets before multiplexing, fragmentation,
or IPsec encryption are counted. For control-plane IP packets transmitted, only these packets
before fragmentation or IPsec encryption are counted. For user-plane IP packets received,
only these packets after demultiplexing, reassembly, or IPsec decryption are counted. For
control-plane IP packets received, only these packets after reassembly or IPsec decryption are
counted.
If the WMPT functions as the main control board, the preceding statistics do not take effect.
Measurement Points
The number of IP packets transmitted at the IP layer over the Iub interface and the number of
IP packets received at the IP layer over the Iub interface are sampled every ten seconds within
a measurement period. At the end of the measurement period, the sum of these sampling
results is used as the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.2.5.2 Number of Bytes in the IP Packets at the IP Layer over the Iub Interface
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the number of bytes in the user-plane and control-plane IP packets
transmitted and received at the IP layer over the Iub interface with a measurement period,
respectively. For the bytes of user-plane IP packets transmitted, only the bytes of these
packets before multiplexing, fragmentation, or IPsec encryption are counted. For bytes of
control-plane IP packets transmitted, only the bytes of these packets before fragmentation or
IPsec encryption are counted. For bytes of user-plane IP packets received, only the bytes of
these packets after demultiplexing, reassembly, or IPsec decryption are counted. For bytes of
control-plane IP packets received, only these packets after reassembly or IPsec decryption are
counted.
If the WMPT functions as the main control board, the preceding statistics do not take effect.
Measurement Points
The number of bytes in the IP packets transmitted at the IP layer over the Iub interface and the
number of bytes in the IP packets received at the IP layer over the Iub interface are sampled
every ten seconds within a measurement period. At the end of the measurement period, the
sum of these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
These counters measure the user-plane and control-plane transmit rate at the IP layer over the
Iub interface and user-plane and control-plane receive rate at the IP layer over the Iub
interface every ten seconds within a measurement period. At the end of the measurement
period, the maximum and average of these sampling results are used as the values of the
corresponding counters. For the user-plane transmit rate, only the transmit rate before
multiplexing, fragmentation, or IPsec encryption is counted. For the control-plane transmit
rate, only the transmit rate before fragmentation or IPsec encryption is counted. For the user-
plane receive rate, only the receive rate after demultiplexing, reassembly, or IPsec decryption
is counted. For the control-plane receive rate, only the receive rate after reassembly or IPsec
decryption is counted.
If the WMPT functions as the main control board, the preceding statistics do not take effect.
Measurement Points
The transmit rate at the IP layer over the Iub interface and receive rate at the IP layer over the
Iub interface are sampled every ten seconds within a measurement period. At the end of the
measurement period, the maximum and average of these sampling results are used as the
values of the corresponding counters.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average, maximum and minimum number of uplink CEs in
dedicated and shared groups consumed by an operator. This counter is only used for operators
with RAN sharing.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU, Coverage Expansion Under Interference,
Uplink Active Set Extension (Coordinating Link Extension Supported by Seamless Crystal
Voice, by SRB over DCH Uplink Coverage Expansion, or by CCPIC Phase 2), 4-Way
Receive Diversity by Inter-Band Assistance, and Enhanced Inter-NodeB Uplink CoMP (Joint
Reception) are introduced, the number of consumed uplink CEs in license groups includes the
number of uplink CEs consumed by R99 users and HSUPA users and the number of CEs
consumed by coordinating links in the local license group. After the Uplink Enhanced
CELL_FACH feature is introduced, the uplink consumed CEs in license groups include those
consumed by E-RACH users.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side. A coordinating link is established when Uplink CoMP (Joint Reception), HetNet
Uplink CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU,
Coverage Expansion Under Interference, Uplink Active Set Extension (Coordinating Link
Extension Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage
Expansion, or by CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or
Enhanced Inter-NodeB Uplink CoMP (Joint Reception) is enabled. After the Uplink
Enhanced CELL_FACH feature is enabled, the uplink consumed CEs include those consumed
by E-RACH users.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the average
number of dedicated and shared uplink CEs consumed by an operator is obtained by dividing
the accumulated value in the period by the number of samples. The maximum of these
sampling results is defined as the maximum number of dedicated and shared uplink CEs
consumed by an operator, and the minimum of these sampling results is defined as the
minimum number of dedicated and shared uplink CEs consumed by an operator.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of dedicated and shared downlink CEs consumed by an
operator. This counter is only used for operators with RAN sharing.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the average
number of dedicated and shared downlink CEs consumed by an operator is obtained by
dividing the accumulated value in the period by the number of samples. The maximum of
these sampling results is defined as the maximum number of dedicated and shared downlink
CEs consumed by an operator, and the minimum of these sampling results is defined as the
minimum number of dedicated and shared uplink CEs consumed by an operator.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of dedicated downlink CEs configured for an operator.
This counter is only used for operators with RAN sharing.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the number
of dedicated downlink CEs configured for an operator is obtained by dividing the
accumulated value in the period by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of dedicated uplink CEs configured for an operator. This
counter is only used for operators with RAN sharing.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the number
of dedicated uplink CEs configured for an operator is obtained by dividing the accumulated
value in the period by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of uplink CEs configured for a shared group within a
measurement period. This counter is only used for operators with RAN sharing.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the number
of uplink CEs configured for a shared group is obtained by dividing the accumulated value in
the period by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of downlink CEs configured for a shared group within a
measurement period. This counter is only used for operators with RAN sharing.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the number
of downlink CEs configured for a shared group is obtained by dividing the accumulated value
in the period by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average, maximum and minimum number of uplink CEs in a shared
group. This counter is only used for operators with RAN sharing.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU, Coverage Expansion Under Interference,
Uplink Active Set Extension (Coordinating Link Extension Supported by Seamless Crystal
Voice, by SRB over DCH Uplink Coverage Expansion, or by CCPIC Phase 2), 4-Way
Receive Diversity by Inter-Band Assistance, and Enhanced Inter-NodeB Uplink CoMP (Joint
Reception) are introduced, the number of consumed uplink CEs in license groups includes the
number of uplink CEs consumed by R99 users and HSUPA users and the number of CEs
consumed by coordinating links in the local license group. After the Uplink Enhanced
CELL_FACH feature is introduced, the uplink consumed CEs in license groups include those
consumed by E-RACH users.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side. A coordinating link is established when Uplink CoMP (Joint Reception), HetNet
Uplink CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU,
Coverage Expansion Under Interference, Uplink Active Set Extension (Coordinating Link
Extension Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage
Expansion, or by CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or
Enhanced Inter-NodeB Uplink CoMP (Joint Reception) is enabled. After the Uplink
Enhanced CELL_FACH feature is enabled, the uplink consumed CEs include those consumed
by E-RACH users.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the average
number of uplink CEs consumed in a shared group is obtained by dividing the accumulated
value in the period by the number of samples. The maximum of these sampling results is
defined as the maximum number of uplink CEs consumed in a shared group, and the
minimum of these sampling results is defined as the minimum number of uplink CEs
consumed in a shared group.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of shared downlink CEs consumed in a shared group. This
counter is only used for operators with RAN sharing.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the average
number of downlink CEs consumed in a shared group is obtained by dividing the accumulated
value in the period by the number of samples. The maximum of these sampling results is
defined as the maximum number of downlink CEs consumed in a shared group, and the
minimum of these sampling results is defined as the minimum number of downlink CEs
consumed in a shared group.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average, maximum and minimum number of uplink CEs in
dedicated and shared groups consumed by HSUPA services of an operator. This counter is
only used for operators with RAN sharing.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU, Coverage Expansion Under Interference,
Uplink Active Set Extension (Coordinating Link Extension Supported by Seamless Crystal
Voice, by SRB over DCH Uplink Coverage Expansion, or by CCPIC Phase 2), 4-Way
Receive Diversity by Inter-Band Assistance, and Enhanced Inter-NodeB Uplink CoMP (Joint
Reception) are introduced, the number of consumed uplink CEs in license groups includes the
number of uplink CEs consumed by HSUPA users and the number of CEs consumed by
coordinating links for HSUPA users in the local license group. After the Uplink Enhanced
CELL_FACH feature is introduced, the uplink consumed CEs in license groups include those
consumed by E-RACH users.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side. A coordinating link is established when Uplink CoMP (Joint Reception), HetNet
Uplink CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU,
Coverage Expansion Under Interference, Uplink Active Set Extension (Coordinating Link
Extension Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage
Expansion, or by CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or
Enhanced Inter-NodeB Uplink CoMP (Joint Reception) is enabled.
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the average
number of dedicated and shared uplink CEs consumed by HSUPA services of an operator is
obtained by dividing the accumulated value in the period by the number of samples. The
maximum of these sampling results is defined as the maximum number of dedicated and
shared uplink CEs consumed by HSUPA services of an operator, and the minimum of these
sampling results is defined as the minimum number of dedicated and shared uplink CEs
consumed by HSUPA services of an operator.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average, maximum and minimum number of uplink CEs consumed
by HSUPA services of a shared group. This counter is only used for operators with RAN
sharing.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU, Coverage Expansion Under Interference,
Uplink Active Set Extension (Coordinating Link Extension Supported by Seamless Crystal
Voice, by SRB over DCH Uplink Coverage Expansion, or by CCPIC Phase 2), 4-Way
Receive Diversity by Inter-Band Assistance, and Enhanced Inter-NodeB Uplink CoMP (Joint
Reception) are introduced, the number of consumed uplink CEs in license groups includes the
number of uplink CEs consumed by HSUPA users and the number of CEs consumed by
coordinating links for HSUPA users in the local license group. After the Uplink Enhanced
CELL_FACH feature is introduced, the uplink consumed CEs in license groups include those
consumed by E-RACH users.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side. A coordinating link is established when Uplink CoMP (Joint Reception), HetNet
Measurement Points
This counter is sampled every five seconds. At the end of a measurement period, the average
number of dedicated uplink CEs consumed by an operator is obtained by dividing the
accumulated value in the period by the number of samples. The maximum of these sampling
results is defined as the maximum number of dedicated uplink CEs consumed by an operator,
and the minimum of these sampling results is defined as the minimum number of dedicated
uplink CEs consumed by HSUPA services of an operator.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average number of uplink CEs consumed by each operator in an
MOCN network. The traffic statistics ID ranges from -1 to 3. The range 0 to 3 corresponds to
the primary/secondary operator indexes configured on the RNC. Value -1 does not take effect.
Remarks:
After Uplink CoMP (Joint Reception), HetNet Uplink CoMP(Joint Reception), UL CoMP
(Joint Reception) based on Coordinated BBU, Coverage Expansion Under Interference,
Uplink Active Set Extension (Coordinating Link Extension Supported by Seamless Crystal
Voice, by SRB over DCH Uplink Coverage Expansion, or by CCPIC Phase 2), 4-Way
Receive Diversity by Inter-Band Assistance, and Enhanced Inter-NodeB Uplink CoMP (Joint
Reception) are introduced, the number of consumed uplink CEs in license groups includes the
number of uplink CEs consumed by R99 users and HSUPA users and the number of CEs
consumed by coordinating links in the local license group. After the Uplink Enhanced
CELL_FACH feature is introduced, the uplink consumed CEs in license groups include those
consumed by E-RACH users.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side. A coordinating link is established when Uplink CoMP (Joint Reception), HetNet
Uplink CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU,
Coverage Expansion Under Interference, Uplink Active Set Extension (Coordinating Link
Extension Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage
Expansion, or by CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or
Enhanced Inter-NodeB Uplink CoMP (Joint Reception) is enabled.
Measurement Points
This counter is sampled every five seconds and measures the average number of uplink CEs
consumed by each operator in an MOCN network. At the end of a measurement period (for
example 15 minutes), the average number is obtained by diving the accumulated value in the
period by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average number of downlink CEs consumed by each operator in an
MOCN network. The traffic statistics ID ranges from -1 to 3. The range 0 to 3 corresponds to
the primary/secondary operator indexes configured on the RNC. Value -1 does not take effect.
Measurement Points
This counter is sampled every five seconds and measures the average number of downlink
CEs consumed by each operator in an MOCN network. At the end of a measurement period
(for example 15 minutes), the average number is obtained by diving the accumulated value in
the period by the number of samples.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average and maximum number of UL CEs in shared and dedicated
groups configured for an operator consumed by all coordinating links.
Remarks:
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, Coverage
Expansion Under Interference, Uplink Active Set Extension (Coordinating Link Extension
Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage Expansion, or by
CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or Enhanced Inter-
NodeB Uplink CoMP (Joint Reception) is enabled.
Coordinating link: Link specifically established by the NodeB for UL CoMP (joint reception)
users.
Measurement Points
The number of UL CEs in shared and dedicated groups configured for an operator consumed
by all coordinating links is sampled every 5 seconds. At the end of a measurement period, the
average number of UL CEs in shared and dedicated groups configured for an operator
consumed by all coordinating links is obtained by dividing the accumulated value within the
measurement by the number of samples. The maximum value within the measurement period
is the maximum number of UL CEs in shared and dedicated groups configured for an operator
consumed by all coordinating links.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average and maximum number of UL CEs configured for an
operator in a shared group consumed by all coordinating links.
Remarks:
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, Coverage
Expansion Under Interference, Uplink Active Set Extension (Coordinating Link Extension
Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage Expansion, or by
CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or Enhanced Inter-
NodeB Uplink CoMP (Joint Reception) is enabled.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side.
Measurement Points
The number of UL CEs configured for an operator in a shared group consumed by all
coordinating links is sampled every 5 seconds. At the end of a measurement period, the
average number of UL CEs configured for an operator in a shared group consumed by all
coordinating links is obtained by dividing the accumulated value within the measurement by
the number of samples. The maximum value within the measurement period is the maximum
number of UL CEs configured for an operator in a shared group consumed by all coordinating
links.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average and maximum number of UL CEs in shared and dedicated
groups configured for an operator consumed by all coordinating links carrying HSUPA
services.
Remarks:
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, Coverage
Expansion Under Interference, Uplink Active Set Extension (Coordinating Link Extension
Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage Expansion, or by
CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or Enhanced Inter-
NodeB Uplink CoMP (Joint Reception) is enabled.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side.
Measurement Points
The number of UL CEs in shared and dedicated groups configured for an operator consumed
by all coordinating links carrying HSUPA services is sampled every 5 seconds. At the end of
a measurement period, the average number of UL CEs in shared and dedicated groups
configured for an operator consumed by all coordinating links carrying HSUPA services is
obtained by dividing the accumulated value within the measurement by the number of
samples. The maximum value within the measurement period is the maximum number of UL
CEs in shared and dedicated groups configured for an operator consumed by all coordinating
links carrying HSUPA services.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter provides the average and maximum number of UL CEs in a shared group
consumed by all coordinating links carrying HSUPA services.
Remarks:
A coordinating link is established when Uplink CoMP (Joint Reception), HetNet Uplink
CoMP(Joint Reception), UL CoMP (Joint Reception) based on Coordinated BBU, Coverage
Expansion Under Interference, Uplink Active Set Extension (Coordinating Link Extension
Supported by Seamless Crystal Voice, by SRB over DCH Uplink Coverage Expansion, or by
CCPIC Phase 2), 4-Way Receive Diversity by Inter-Band Assistance, or Enhanced Inter-
NodeB Uplink CoMP (Joint Reception) is enabled.
Coordinating link: Link specifically established for UL CoMP (joint reception) users on the
RAN side.
Measurement Points
The number of UL CEs in a shared group consumed by all coordinating links carrying
HSUPA services is sampled every 5 seconds. At the end of a measurement period, the average
number of UL CEs in a shared group consumed by all coordinating links carrying HSUPA
services is obtained by dividing the accumulated value within the measurement by the number
of samples. The maximum value within the measurement period is the maximum number of
UL CEs in a shared group consumed by all coordinating links carrying HSUPA services.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The function subset indicates measurements reserved for operators. Reserved counter is used
temporarily in patch versions and will be replaced with a new counter in later versions. For
the detailed information about used reserved counters, see the "Used Reserved Counter List"
of the corresponding version.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.OpeReserve.Counter1.OP None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
VS.OpeReserve.Counter2.OP None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.OpeReserve.Counter3.OP None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.OpeReserve.Counter4.OP None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
None.
The following table describes the meanings of each counter.
VS.OpeReserve.Counter5.OP None.
Measurement Points
None.
Formula
None
Unit
None
Related Features
None
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of normal cell-sectoreqm RL releases within a
measurement period when the Independent Demodulation of Signals from Multiple RRUs in
One Cell feature has been enabled or a 0.5/0.5 cell has been deployed.
This counter complies with section "8.3 NBAP Dedicated Procedures" in 3GPP TS 25.433
(v10.10.0).
Measurement Points
As shown in point A of the following figure, the measurement is triggered in the sector in
which a UE releases an RL when the NodeB receives a RADIO LINK DELETION
REQUEST message from the RNC and the RL is normally released. The measurement is
triggered in each sector if the UE is served by multiple sectors while releasing the RL.
Figure 1-20
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of abnormal cell-sectoreqm RL releases within a
measurement period when the Independent Demodulation of Signals from Multiple RRUs in
One Cell feature has been enabled or a 0.5/0.5 cell has been deployed.
This counter complies with section "8.3 NBAP Dedicated Procedures" in 3GPP TS 25.433
(v10.10.0).
Measurement Points
As shown in point A of the following figure, the measurement is triggered in the sector in
which a UE releases an RL when the NodeB receives a RADIO LINK DELETION
REQUEST message from the RNC but the RL is abnormally released. The measurement is
triggered in each sector if the UE is served by multiple sectors while releasing the RL.
Figure 1-21
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of cell-sectoreqm positive AI acknowledgements for
RACH users within a measurement period. If the Independent Demodulation of Signals from
Multiple RRUs in One Cell feature has not been enabled or a 0.5/0.5 cell has not been
deployed, the measurement is triggered on a basis of cell, not a basis of sectoreqm.
Measurement Points
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has been
enabled or a 0.5/0.5 cell has been deployed, this counter is sampled in each sector. At the end
of a measurement period, the number of preamble acquisition indicators (AIs) sent to RACH
users with positive acknowledgements transmitted over the downlink AICH is measured in a
sector.
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has not
been enabled or a 0.5/0.5 cell has not been deployed, this counter is sampled on a basis of
cell, not a basis of sector. At the end of a measurement period, the number of preamble
acquisition indicators (AIs) sent to RACH users with positive acknowledgements transmitted
over the downlink AICH is measured in a cell.
If the Coverage Expansion Under Interference feature has been enabled, the number of
preamble acquisition indicators (AIs) sent to RACH users with positive acknowledgements
transmitted over the downlink AICH is measured within a measurement period. Users served
by both the host cell (primary cell) and neighboring cell (coordinating cell) are counted.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of cell-sectoreqm negative AI acknowledgements for
RACH users within a measurement period. If the Independent Demodulation of Signals from
Multiple RRUs in One Cell feature has not been enabled or a 0.5/0.5 cell has not been
deployed, the measurement is triggered on a basis of cell, not a basis of sectoreqm.
Measurement Points
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has been
enabled or a 0.5/0.5 cell has been deployed, this counter is sampled in each sector. At the end
of a measurement period, the number of preamble acquisition indicators (AIs) sent to RACH
users with negative acknowledgements transmitted over the downlink AICH is measured in a
sector.
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has not
been enabled or a 0.5/0.5 cell has not been deployed, this counter is sampled on a basis of
cell, not a basis of sector. At the end of a measurement period, the number of preamble
acquisition indicators (AIs) sent to RACH users with negative acknowledgements transmitted
over the downlink AICH is measured in a cell.
If the Coverage Expansion Under Interference feature has been enabled, the number of
preamble acquisition indicators (AIs) sent to RACH users with negative acknowledgements
transmitted over the downlink AICH is measured within a measurement period. Users served
by both the host cell (primary cell) and neighboring cell (coordinating cell) are counted.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.4.2.3 Number of TBs successfully received over the cell-sectoreqm RACH with
correct CRCs
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TBs successfully received over the cell-sectoreqm
RACH with correct CRCs within a measurement period. If the Independent Demodulation of
Signals from Multiple RRUs in One Cell feature has not been enabled or a 0.5/0.5 cell has not
been deployed, the measurement is triggered on a basis of cell, not a basis of sectoreqm.
Measurement Points
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has been
enabled or a 0.5/0.5 cell has been deployed, this counter is sampled in each sector. At the end
of a measurement period, the number of TBs successfully received over the uplink RACH
with correct CRCs is measured in a sector.
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has not
been enabled or a 0.5/0.5 cell has not been deployed, this counter is sampled on a basis of
cell, not a basis of sector. At the end of a measurement period, the number of TBs
successfully received over the uplink RACH with correct CRCs is measured in a cell.
If the Coverage Expansion Under Interference feature has been enabled, the number of TBs
successfully received over the uplink RACH with correct CRCs is measured within a
measurement period. Users served by both the host cell (primary cell) and neighboring cell
(coordinating cell) are counted.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TBs received over the cell-sectoreqm RACH with
correct and incorrect CRCs within a measurement period. If the Independent Demodulation of
Signals from Multiple RRUs in One Cell feature has not been enabled or a 0.5/0.5 cell has not
been deployed, the measurement is triggered on a basis of cell, not a basis of sectoreqm.
Measurement Points
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has been
enabled or a 0.5/0.5 cell has been deployed, this counter is sampled in each sector. At the end
of a measurement period, the number of TBs received over the uplink RACH with correct and
incorrect CRCs is measured in a sector.
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has not
been enabled or a 0.5/0.5 cell has not been deployed, this counter is sampled on a basis of
cell, not a basis of sector. At the end of a measurement period, the number of TBs received
over the uplink RACH with correct and incorrect CRCs is measured in a cell.
If the Coverage Expansion Under Interference feature has been enabled, the number of TBs
received over the uplink RACH with correct and incorrect CRCs is measured within a
measurement period. Users served by both the host cell (primary cell) and neighboring cell
(coordinating cell) are counted.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The function subset consists of ERACH-related counters for the LoCell_SectorEQM and does
not apply to LampSite base stations.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of cell-sectoreqm positive AI acknowledgements for E-
RACH users within a measurement period. If the Independent Demodulation of Signals from
Multiple RRUs in One Cell feature has not been enabled or a 0.5/0.5 cell has not been
deployed, the measurement is triggered on a basis of cell, not a basis of sectoreqm.
Measurement Points
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has been
enabled or a 0.5/0.5 cell has been deployed, the number of positive acknowledgements (with
+1 acquisition indicators (AIs)) and the number of positive acknowledgements (with +1
extended acquisition indicators (EAIs)) transmitted to E-RACH users over the AICH are
sampled per sector within a measurement period. At the end of the measurement period, the
sum of these sampling results is used as the value of this counter.
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has not
been enabled or a 0.5/0.5 cell has not been deployed, the number of positive
acknowledgements (with +1 acquisition indicators (AIs)) and the number of positive
acknowledgements (with +1 extended acquisition indicators (EAIs)) transmitted to E-RACH
users over the AICH are sampled per cell within a measurement period. At the end of the
measurement period, the sum of these sampling results is used as the value of this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of cell-sectoreqm negative AI acknowledgements for E-
RACH users within a measurement period. If the Independent Demodulation of Signals from
Multiple RRUs in One Cell feature has not been enabled or a 0.5/0.5 cell has not been
deployed, the measurement is triggered on a basis of cell, not a basis of sectoreqm.
Measurement Points
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has been
enabled or a 0.5/0.5 cell has been deployed, the number of negative acknowledgements
transmitted to E-RACH users over the AICH is sampled per sector within a measurement
period. At the end of the measurement period, the sum of these sampling results is used as the
value of this counter.
If the Independent Demodulation of Signals from Multiple RRUs in One Cell feature has not
been enabled or a 0.5/0.5 cell has not been deployed, the number of negative
acknowledgements transmitted to E-RACH users over the AICH is sampled per cell within a
measurement period. At the end of the measurement period, the sum of these sampling results
is used as the value of this counter.
When extended acquisition indicators (EAIs) are not configured, the number of negative
acknowledgements (with -1 AIs) transmitted to E-RACH users is sampled. When EAIs are
configured, the number of negative acknowledgements (with -1 AIs and -1 EAIs) transmitted
to E-RACH users is sampled.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the average and minimum antenna RTWP of each receive
antenna during a measurement period.
Measurement Points
Within a measurement period, the NodeB accumulates the antenna RTWP per second.
Assume that the sum is A. The NodeB counts the seconds in the measurement period. Assume
that this value is B. Then, Average antenna RTWP = A/B. The system calculates the average
antenna RTWP every 5 seconds and then takes the minimum value within the measurement
period as the minimum antenna RTWP.
For the LampSite base stations, the preceding counters are measured only when the sector-
equipment-level RTWP subscription function is enabled by running the STR
LOCELLRTWPREPORT command.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
The preceding counters indicate the ratio of time when the Narrowband Interference
Suppression feature takes effect to the time when interference is detected on each RX antenna
within a measurement period.
Measurement Points
Within a measurement period, the NodeB counts the number of times the Narrowband
Interference Suppression feature successfully suppresses narrowband interference. Assume
that this number is A. The NodeB counts the number of times the Narrowband Interference
Suppression feature detects interference. Assume that this number is B. Then, Time Ratio of
Effective Narrowband Interference Suppression = A/B. This counter is available only when
the Narrowband Interference Suppression feature is enabled and RRUs support this feature.
Formula
None
Unit
per mill
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The function subset measures the number of CoMP users in a coordinating cell, which
indicates the CoMP performance on the NodeB.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
1.5.1.1 Number of CoMP Users in a CoMP Cell Pair Enabled with Coverage
Expansion Under Interference
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average and maximum number of CoMP users in a CoMP cell pair.
This counter indicates whether the Coverage Expansion Under Interference feature has taken
effect.
Remarks:
For details, see Coverage Expansion Under Interference Feature Parameter Description.
Disuse Statement:
Measurement Points
The number of CoMP users in a CoMP cell pair is sampled every 5 seconds. At the end of a
measurement period, the average number of CoMP users in a CoMP cell pair equals the
accumulated value within the measurement period divided by the number of samples. The
maximum value within the measurement period is the maximum number of CoMP users in a
CoMP cell pair.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average and maximum number of CoMP users in a UL CoMP cell
pair. The measurement results confirm whether the CoMP feature takes effect.
Remarks:
UL CoMP (joint reception) user: Users using Uplink CoMP (Joint Reception) or HetNet
Uplink CoMP(Joint Reception) to receive signals on the NodeB side.
Coordinating link: Link specifically established by the NodeB for UL CoMP (joint reception)
users. The link is transparent to the RNC and UEs.
User in a CoMP cell pair: specifies a user that uses a CoMP cell occupying coordinating links
as the secondary cell and a CoMP cell occupying other links set up by RNC as the primary
cell.
Measurement Points
The number of CoMP users in a UL CoMP cell pair is sampled every 5 seconds. At the end of
the measurement period, the average number of CoMP users in a UL CoMP cell pair is
obtained by dividing the accumulated value within the measurement period by the number of
samples. The maximum value within the measurement period is the maximum number of
CoMP users in a UL CoMP cell pair.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of normal RL releases in a sector equipment group in a
local cell if Independent Demodulation of Signals from Multiple Small Cell RRUs in One
Cell has been enabled.
Measurement Points
As shown in point A of the following figure, the measurement is triggered in the sector
equipment group in a local cell where a UE releases an RL when the NodeB receives a
RADIO LINK DELETION REQUEST message from the RNC and the RL is normally
released. The measurement is triggered in each sector equipment group if the UE is served by
multiple sector equipment groups while releasing the RL. The measurement is not triggered in
the non-mixed-multi-RRU cell, so the corresponding values are not counted into this counter.
Figure 1-22
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of abnormal RL releases in a sector equipment group in a
local cell if Independent Demodulation of Signals from Multiple Small Cell RRUs in One
Cell has been enabled.
Measurement Points
As shown in point A of the following figure, the measurement is triggered in the sector
equipment group in a local cell where a UE releases an RL when the NodeB receives a
RADIO LINK DELETION REQUEST message from the RNC and the RL is abnormally
released. The measurement is triggered in each sector equipment group if the UE is served by
multiple sector equipment groups while releasing the RL. The measurement is not triggered in
the non-mixed-multi-RRU cell, so the corresponding values are not counted into this counter.
Figure 1-23
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
1.6.2.1 Number of positive acknowledgments for RACH users over the AICH in a
sector equipment group in a local cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of positive acknowledgments transmitted to RACH users
over the AICH in a sector equipment group in a local cell if Independent Demodulation of
Signals from Multiple Small Cell RRUs in One Cell has been enabled.
Measurement Points
If Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell has been
enabled, the number of positive acknowledgments (with +1 acquisition indicators (AIs))
transmitted to RACH users over the AICH is sampled per sector equipment group in a local
cell within a measurement period. At the end of the measurement period, the sum of these
sampling results is used as the value of this counter. The measurement is not triggered in the
non-mixed-multi-RRU cell, so the corresponding values are not counted into this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.6.2.2 Number of negative acknowledgments for RACH users over the AICH in
a sector equipment group in a local cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of negative acknowledgments transmitted to RACH users
over the AICH in a sector equipment group in a local cell if Independent Demodulation of
Signals from Multiple Small Cell RRUs in One Cell has been enabled.
Measurement Points
If Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell has been
enabled, the number of negative acknowledgments (with -1 acquisition indicators (AIs))
transmitted to RACH users over the AICH is sampled per sector equipment group in a local
cell within a measurement period. At the end of the measurement period, the sum of these
sampling results is used as the value of this counter. The measurement is not triggered in the
non-mixed-multi-RRU cell, so the corresponding values are not counted into this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.6.2.3 Number of TBs successfully received with correct CRCs over the RACH in
a sector equipment group in a local cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of TBs successfully received with correct CRCs over the
RACH in a sector equipment group in a local cell if Independent Demodulation of Signals
from Multiple Small Cell RRUs in One Cell has been enabled.
Measurement Points
If Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell has been
enabled, the number of TBs successfully received with correct CRCs over the RACH is
sampled per sector equipment group in a local cell within a measurement period. At the end of
the measurement period, the sum of these sampling results is used as the value of this counter.
The measurement is not triggered in the non-mixed-multi-RRU cell, so the corresponding
values are not counted into this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.6.2.4 Total number of TBs received over the RACH in a sector equipment group
in a local cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the total number of TBs received over the RACH in a sector equipment
group in a local cell if Independent Demodulation of Signals from Multiple Small Cell RRUs
in One Cell has been enabled.
Measurement Points
If Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell has been
enabled, the total number of TBs received over the RACH is sampled per sector equipment
group in a local cell within a measurement period. At the end of the measurement period, the
sum of these sampling results is used as the value of this counter. The measurement is not
triggered in the non-mixed-multi-RRU cell, so the corresponding values are not counted into
this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
1.6.3.1 Number of positive acknowledgments for E-RACH users over the AICH
in a sector equipment group in a local cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of positive acknowledgments transmitted to E-RACH
users over the AICH in a sector equipment group in a local cell if Independent Demodulation
of Signals from Multiple Small Cell RRUs in One Cell has been enabled.
Measurement Points
If Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell has been
enabled, the number of positive acknowledgments (with +1 acquisition indicators (AIs)) and
the number of positive acknowledgments (with +1 extended acquisition indicators (EAIs))
transmitted to E-RACH users over the AICH are sampled per sector equipment group in a
local cell within a measurement period. At the end of the measurement period, the sum of
these sampling results is used as the value of this counter. The measurement is not triggered in
the non-mixed-multi-RRU cell, so the corresponding values are not counted into this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.6.3.2 Number of negative acknowledgments for E-RACH users over the AICH
in a sector equipment group in a local cell
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the number of negative acknowledgments transmitted to E-RACH
users over the AICH in a sector equipment group in a local cell if Independent Demodulation
of Signals from Multiple Small Cell RRUs in One Cell has been enabled.
Measurement Points
If Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell has been
enabled, the number of negative acknowledgments transmitted to E-RACH users over the
AICH is sampled per sector equipment group in a local cell within a measurement period. At
the end of the measurement period, the sum of these sampling results is used as the value of
this counter. When extended acquisition indicators (EAIs) are not configured, the number of
negative acknowledgments (with -1 AIs) transmitted to E-RACH users is sampled. When
EAIs are configured, the number of negative acknowledgments (with -1 AIs and -1 EAIs)
transmitted to E-RACH users is sampled. The measurement is not triggered in the non-mixed-
multi-RRU cell, so the corresponding values are not counted into this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
Counter Relationship
None
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
Description
This counter measures the average RTWP in a sector equipment group in a local cell if
Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell has been
enabled.
Measurement Points
If Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell has been
enabled, the RTWP in a sector equipment group in a local cell is sampled per second within a
measurement period. At the end of the measurement period, the sum of these sampling results
is recorded A, and the number of samples is recorded B. The value of A/B is defined as the
value of this counter.
The measurement is not triggered in the non-mixed-multi-RRU cell, so the corresponding
values are not counted into this counter.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
Index
V VS.DataDiscardRatio.Mean, 160
VS.DataOutput.AllHSDPA.Traffic, 490
VS.Ack.RetraSch, 536 VS.DataOutput.DCHSDPA.Traffic, 157
VS.AckTotal, 46 VS.DataOutput.InterNBDBHSDPA.AllSec.Traffic,
VS.AdvancedDemodulation.User.Mean, 386 517
VS.AIR.ActRatio, 390 VS.DataOutput.InterNBDBHSDPA.Traffic, 515
VS.AIR.InterferenceDec.Mean, 385 VS.DataOutput.Mean, 150
VS.AllHSDPA.DataTtiNum.User, 492 VS.DataOutput.Mean.FreeUser, 153
VS.Assistance4Rx.UserNum, 382 VS.DataOutput.User, 151
VS.ATMDlMaxUsed.1, 590 VS.DataOutput.UserData, 152
VS.ATMDlTotal.1, 587 VS.DataTtiRatio.Mean, 107
VS.ATMUlMaxUsed.1, 584 VS.DCHSDPA.DataTtiNum.User, 120
VS.ATMUlTotal.1, 582 VS.DedicMeaRpt.MEAN, 581
VS.AttRLADD.MEAN, 579 VS.DLCE.Mean.Dedicated, 171
VS.AttRLRecfg.MEAN, 580 VS.DLCE.Mean.Shared, 175
VS.AttRLSETUP.MEAN, 577 VS.DlCode.Used.Mean, 372
VS.AvaiHSDPAPwrRatio.Mean, 142 VS.DLDCHPwrRatio.SharedOperator0, 421
VS.BasebandNBIS.Bandwidth.Mean, 392 VS.DlPwrRatio.SF256, 416
VS.BTS.CnbapCap.UseRate, 636 VS.DPCCH.R99.POWER, 418
VS.CCPICPhase3.CodeNum.Mean, 378 VS.DPCHTPCPwrAdj.UserNum, 384
VS.CCPICPhase4.UserNum.Mean, 389 VS.EFACH.AckTtiNum, 425
VS.CellReserve.Counter1, 398 VS.EFACH.DataTtiNum, 427
VS.CellReserve.Counter10, 407 VS.EFACH.PdschPwrRatio.Mean, 431
VS.CellReserve.Counter11, 408 VS.EFACH.ScchPwrRatio.Mean, 429
VS.CellReserve.Counter12, 409 VS.EFACH.Thruput, 428
VS.CellReserve.Counter13, 410 VS.ERACH.DataTtiNum, 346
VS.CellReserve.Counter14, 411 VS.ERACH.NegativeNum.AICH.Locell.SectorEqm,
VS.CellReserve.Counter2, 399 714
VS.CellReserve.Counter3, 400 VS.ERACH.NegativeNum.AICH.Locell.SectorEqmGr
VS.CellReserve.Counter4, 401 p, 741
VS.CellReserve.Counter5, 402 VS.ERACH.OccupiedNum.Mean, 343
VS.CellReserve.Counter6, 403 VS.ERACH.PositiveNum.AICH.Locell.SectorEqm,
VS.CellReserve.Counter7, 404 713
VS.CellReserve.Counter8, 405 VS.ERACH.PositiveNum.AICH.Locell.SectorEqmGr
VS.CellReserve.Counter9, 406 p, 740
VS.CombFilter.FreqNum.Mean, 391 VS.ERACH.Thruput, 345
VS.CombFilterExtend.FreqNum.Mean, 394 VS.FirstStageIcEff.Mean, 371
VS.CoordinatingRL.Handle.Max, 644 VS.FPNum.Discarded.DCH, 360
VS.CPC.DRXCfg.UserNum, 336 VS.FPNum.MUX.AMR.Rx, 363
VS.CPC.DTXCfg.UserNum, 334 VS.FPNum.Received.FACH, 355
VS.CPC.FDPCHDTX.ActRatio, 341 VS.FPNum.Received.PCH, 357
VS.CPC.LesOpCfg.SceduledNum, 339 VS.HSDPA.16QAMCfg.ActedNum, 96
VS.CQI.0, 56 VS.HSDPA.2ScchCodeRatio, 123
VS.DataCQI.MEAN, 95 VS.HSDPA.64QAMCfg.Acted.Traffic, 474
VS.UlCovExpansion.UserNum.HostCell, 381
VS.UsedCQI0, 72
VS.UserTtiRatio.Mean, 106
VS.UUlCoMPGroup.UserNum, 727
VS.ValidAntRatio.Mean, 369