3900 Series Base Station NodeBFunction Performance Counter Reference (V100R009C00_11)(PDF)-En

3900 Series Base Station V100R009C00

NodeBFunction Performance Counter Reference Issue

11

Date

2015–05–30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

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

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 11 (2015–05–30)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

3900 Series Base Station NodeBFunction Performance Counter Reference

About This Document

About This Document This section describes performance counters for 3900 series base stations.

Document Structure Figure 1 shows the document structure. Figure 1 Document structure

Table 1 explains the terms shown in Figure 1. Table 1 Terms Term

Explanation

Object type

One object type contains one or more function subsets.

Function Subset

One function subset contains one or more counters but belongs to only one object type.

Counter

Counters are the basic elements of performance measurement. One counter can belong to only one function subset.

Counter Item Description Table 2 lists the description of each counter item.

Issue 11 (2015–05–30)


ii


About This Document

Table 2 Description of each counter item Item

Description

Object type

Overview

Definition and function of a object type.

Function SubSets

Function subsets contained in a object type.

Functio n Set

FunctionSet Name

Name of the function set.

Functio n Subset

Overview

Definition of a function subset and the flowchart for measuring related counters.

Counters

Counters contained in a function subset.

Counter Relationship

A table that lists parent counters and their child counters in a table. Note that the child counters listed in the table cover only typical scenarios. That is, some scenarios are not covered by any counter. Therefore, the value of a parent counter is larger than or equal to the sum of the values of its child counters. Some counters may not be involved in any counter relationship.

Counter ID

A string of digits that uniquely identifies a counter.

Counter Name

Name of a counter. It is composed of a string of uppercase letters, lowercase letters, and dots.

Counter Description

A phrase that provides a simple description about a counter.

Description

Detailed description about a counter.

Measurement Point

Condition for triggering counter measurement.

Formula

Relationship among counters.

Unit

Unit of a counter.

Related Features

Features related to a counter are listed in feature ID and feature name. A counter is used to estimate related features. Related features are listed as follows in different scenarios:

Counter

One function set contains one or more function subsets.

l If a counter has no related features, no features are listed. l A counter has related features, – If this counter applies only to GSM, UMTS, LTE, or SingleRAN, the features are related to such RAT. – If this counter applies to multiple RATs in GSM, UMTS, LTE, and SingleRAN, the features are a set of features related to all associated RATs. Only the feature IDs and feature names of the features for related RATs are listed.

Issue 11 (2015–05–30)


iii


Item

Issue 11 (2015–05–30)

About This Document

Description Original Release

The version for which the counter was first available.

Network Element

NE Type of a product displayed on the U2000. The value can be BTS3900, BTS3900 WCDMA, or BTS3900 LTE. BTS3900 indicates a co-MPT base station; BTS3900 WCDMA indicates a UMTS base station; BTS3900 LTE indicates an LTE base station. These NE types are applicable to the following base station models: DBS3900, BTS3900, BTS3900A, BTS3900L, BTS3900AL, and BTS3900C.

Applicable Mode

The corresponding mode of the counters.


iv


Contents

Contents About This Document.....................................................................................................................ii 1 NodeBFunction Performance Counter Measurement............................................................1 1.1 Measurement of Local Cell Performance (LOCELL)....................................................................................................2 1.1.1 HSDPA Measurement (HSDPA.LOCELL)................................................................................................................2 1.1.2 Cell Traffic Measurement (TRAFFIC.LOCELL)...................................................................................................145 1.1.3 HSUPA Measurement (HSUPA.LOCELL)............................................................................................................156 1.1.4 CPC Measurement (CPC.LOCELL).......................................................................................................................232 1.1.5 ERACH Measurement (ERACH.LOCELL)...........................................................................................................238 1.1.6 SCCPCH Measurement (SCCPCH.LOCELL)........................................................................................................242 1.1.7 DCH Measurement (DCH.LOCELL)......................................................................................................................247 1.1.8 Cell Algorithm Measurement (ALGO.LOCELL)...................................................................................................250 1.1.9 Cell Reserved Counter Measurement (CELLRESERVE.LOCELL)......................................................................259 1.1.10 Cell Power Measurement (POWER.LOCELL).....................................................................................................272 1.1.11 EFACH Measurement (EFACH.LOCELL)..........................................................................................................281 1.1.12 HSDPA Measurement 2 (HSDPA2.LOCELL).....................................................................................................288 1.2 Measurement of NodeB Performance (NodeB).........................................................................................................333 1.2.1 Iub Measurement per NodeB (IUB.NODEB).........................................................................................................333 1.2.2 NodeB Hardware Baseband Resource Measurement (TRAFFIC.NODEB)...........................................................411 1.2.3 NodeB NBAP Procedure Measurement (NBAP.NODEB).....................................................................................413 1.2.4 NodeB Reserved Counter Measurement (NODEBRESERVE.NODEB)...............................................................422 1.2.5 Iub Transmission Performance Measurement per NodeB (TRAFFIC.TRPIP.NODEB)........................................427 1.3 Measurement of CNOperator Performance (OPERATOR).......................................................................................434 1.3.1 Traffic Measurement per CNOperator (TRAFFIC.OPERATOR)..........................................................................434 1.3.2 Operator Reserved Counter Measurement (OPERESERVE.OPERATOR)...........................................................462 1.4 Measurement of LoCell_SectorEQM Performance (LOCELL_SECTOREQM)......................................................467 1.4.1 Iub Measurement per LoCell_SectorEQM (IUB.LOCELL.SECTOREQM)..........................................................468 1.4.2 PRACH Measurement per LoCell_SectorEQM (PRACH.LOCELL.SECTOREQM)...........................................471 1.4.3 ERACH Measurement per LoCell_SectorEQM (ERACH.LOCELL.SECTOREQM)...........................................476 1.4.4 RTWP Measurement per LoCell_SectorEQM (RTWP.LOCELL.SECTOREQM)................................................479 1.5 Measurement of UMTS ULCoMP Group Performance (UULCOMPGROUP)........................................................483 1.5.1 ULCoMP Group Algorithm Measurement (ALGO.UULCOMPGROUP).............................................................483

Issue 11 (2015–05–30)


v


1

1 NodeBFunction Performance Counter Measurement

NodeBFunction Performance Counter Measurement

About This Chapter This section describes NodeBFunction performance counters. 1.1 Measurement of Local Cell Performance (LOCELL) 1.2 Measurement of NodeB Performance (NodeB) 1.3 Measurement of CNOperator Performance (OPERATOR) 1.4 Measurement of LoCell_SectorEQM Performance (LOCELL_SECTOREQM) 1.5 Measurement of UMTS ULCoMP Group Performance (UULCOMPGROUP)

Issue 11 (2015–05–30)


1



1.1 Measurement of Local Cell Performance (LOCELL) Overview The object type consists of function subnets in the local cell to indicate the local cell status and performance on a NodeB.

FunctionSubSets FunctionSubSet

FunctionSubSet Name

HSDPA.LOCELL

HSDPA Measurement

TRAFFIC.LOCELL

Cell Traffic Measurement

HSUPA.LOCELL

HSUPA Measurement

CPC.LOCELL

CPC Measurement

ERACH.LOCELL

ERACH Measurement

SCCPCH.LOCELL

SCCPCH Measurement

DCH.LOCELL

DCH Measurement

ALGO.LOCELL

Cell Algorithm Measurement

CELLRESERVE.LOCELL

Cell Reserved Counter Measurement

POWER.LOCELL

Cell Power Measurement

EFACH.LOCELL

EFACH Measurement

HSDPA2.LOCELL

HSDPA Measurement 2

1.1.1 HSDPA Measurement (HSDPA.LOCELL) Overview The function subset consists of HSDPA-related counters for a cell to indicate the HSDPA cell status and performance. Unless otherwise stated, HSDPA users are those in the CELL_DCH state.

Issue 11 (2015–05–30)


2



Counters Counter ID

Counter Name

Counter Description

Original Release

50331654

VS.AckTotal

Total number of ACKs received

BTS3900: V100R008C00 BTS3900 WCDMA: version earlier than V200R011C00

50331655

VS.NackTotal

Total number of NACKs received


50331656

VS.DtxTotal

Total number of TTIs when the NodeB can not translate the acknowledgement information from the UE


50331657

VS.AckFirst

Number of ACKs received after 1st transmission


50331658

VS.AckRetrans.1

Number of ACKs received after 1st retransmission


50331659

VS.AckRetrans.2

Number of ACKs received after 2nd retransmission


50331660

VS.AckRetrans.3

Number of ACKs received after 3rd retransmission


50331661

VS.AckRetrans.4

Number of ACKs received after 4th retransmission


Issue 11 (2015–05–30)


3



Counter ID

Counter Name

Counter Description

Original Release

50331662

VS.AckRetrans.5



50331663

VS.AckRetrans.6



50331664

VS.AckRetrans.7



50331665

VS.AckRetrans.8



50331666

VS.AckRetrans.9



50331667

VS.AckRetrans.10



50331668

VS.AckRemain

Number of times the NodeB does not receive the ACK from the UE after the last retransmission


50331816

VS.MIMODUALS TREAM1.DTX

Number Of MIMO Anchor Stream DTX

BTS3900: V100R008C00 BTS3900 WCDMA: V200R013C00

Issue 11 (2015–05–30)


4



Counter ID

Counter Name

Counter Description

Original Release

50331817

VS.MIMODUALS TREAM2.DTX

Number Of MIMO SupStream DTX


50331818

VS.MIMODUALS TREAM1.ACK

Number Of MIMO Anchor Stream ACK


50331819

VS.MIMODUALS TREAM2.ACK

Number Of MIMO SupStream ACK


50331820

VS.MIMODUALS TREAM1.NACK

Number Of MIMO Anchor Stream NACK


50331821

VS.MIMODUALS TREAM2.NACK

Number Of MIMO SupStream NACK


50331669

VS.CQI.0

Number of reports with CQI0


50331670

VS.CQI.1



50331671

VS.CQI.2



50331672

VS.CQI.3



Issue 11 (2015–05–30)


5



Counter ID

Counter Name

Counter Description

Original Release

50331673

VS.CQI.4



50331674

VS.CQI.5



50331675

VS.CQI.6



50331676

VS.CQI.7



50331677

VS.CQI.8



50331678

VS.CQI.9



50331679

VS.CQI.10



50331680

VS.CQI.11



Issue 11 (2015–05–30)


6



Counter ID

Counter Name

Counter Description

Original Release

50331681

VS.CQI.12



50331682

VS.CQI.13



50331683

VS.CQI.14



50331684

VS.CQI.15



50331685

VS.CQI.16



50331686

VS.CQI.17



50331687

VS.CQI.18



50331688

VS.CQI.19



Issue 11 (2015–05–30)


7



Counter ID

Counter Name

Counter Description

Original Release

50331689

VS.CQI.20



50331690

VS.CQI.21



50331691

VS.CQI.22



50331692

VS.CQI.23



50331693

VS.CQI.24



50331694

VS.CQI.25



50331695

VS.CQI.26



50331696

VS.CQI.27



Issue 11 (2015–05–30)


8



Counter ID

Counter Name

Counter Description

Original Release

50331697

VS.CQI.28



50331698

VS.CQI.29



50331699

VS.CQI.30



50331725

VS.CQI.31

Number of Cqi31

BTS3900 WCDMA: V200R012C00

50331726

VS.CQI.32

Number of Cqi32


50331727

VS.CQI.33

Number of Cqi33


50331728

VS.CQI.34

Number of Cqi34


50331729

VS.CQI.35

Number of Cqi35


50331754

VS.UsedCQI0

Number of times the NodeB transmits data with CQI=0


50331755

VS.UsedCQI1



50331756

VS.UsedCQI2



Issue 11 (2015–05–30)


9



Counter ID

Counter Name

Counter Description

Original Release

50331757

VS.UsedCQI3



50331758

VS.UsedCQI4



50331759

VS.UsedCQI5



50331760

VS.UsedCQI6



50331761

VS.UsedCQI7



50331762

VS.UsedCQI8



50331763

VS.UsedCQI9



50331764

VS.UsedCQI10



50331765

VS.UsedCQI11



50331766

VS.UsedCQI12



Issue 11 (2015–05–30)


10



Counter ID

Counter Name

Counter Description

Original Release

50331767

VS.UsedCQI13



50331768

VS.UsedCQI14



50331769

VS.UsedCQI15



50331770

VS.UsedCQI16



50331771

VS.UsedCQI17



50331772

VS.UsedCQI18



50331773

VS.UsedCQI19



50331774

VS.UsedCQI20



50331775

VS.UsedCQI21



50331776

VS.UsedCQI22



Issue 11 (2015–05–30)


11



Counter ID

Counter Name

Counter Description

Original Release

50331777

VS.UsedCQI23



50331778

VS.UsedCQI24



50331779

VS.UsedCQI25



50331780

VS.UsedCQI26



50331781

VS.UsedCQI27



50331782

VS.UsedCQI28



50331783

VS.UsedCQI29



50331784

VS.UsedCQI30



50331785

VS.UsedCQI31to39

Number of times the NodeB transmits data with CQI=[31, 39]


50331786

VS.MIMODualCQ I1.0

Number Of MIMO TYPEA CQI Report With CQI1 0


Issue 11 (2015–05–30)


12



Counter ID

Counter Name

Counter Description

Original Release

50331787

VS.MIMODualCQ I1.1



50331788

VS.MIMODualCQ I1.2



50331789

VS.MIMODualCQ I1.3



50331790

VS.MIMODualCQ I1.4



50331791

VS.MIMODualCQ I1.5



50331792

VS.MIMODualCQ I1.6



50331793

VS.MIMODualCQ I1.7



50331794

VS.MIMODualCQ I1.8



50331795

VS.MIMODualCQ I1.9



50331796

VS.MIMODualCQ I1.10



Issue 11 (2015–05–30)


13



Counter ID

Counter Name

Counter Description

Original Release

50331797

VS.MIMODualCQ I1.11



50331798

VS.MIMODualCQ I1.12



50331799

VS.MIMODualCQ I1.13



50331800

VS.MIMODualCQ I1.14



50331801

VS.MIMODualCQ I2.0



50331802

VS.MIMODualCQ I2.1



50331803

VS.MIMODualCQ I2.2



50331804

VS.MIMODualCQ I2.3



50331805

VS.MIMODualCQ I2.4



50331806

VS.MIMODualCQ I2.5



Issue 11 (2015–05–30)


14



Counter ID

Counter Name

Counter Description

Original Release

50331807

VS.MIMODualCQ I2.6



50331808

VS.MIMODualCQ I2.7



50331809

VS.MIMODualCQ I2.8



50331810

VS.MIMODualCQ I2.9



50331811

VS.MIMODualCQ I2.10



50331812

VS.MIMODualCQ I2.11



50331813

VS.MIMODualCQ I2.12



50331814

VS.MIMODualCQ I2.13



50331815

VS.MIMODualCQ I2.14



50331822

VS.APCPhase0CQ I.MEAN

Average CQI Of Phase 0 Based On APC Algorithm


Issue 11 (2015–05–30)


15



Counter ID

Counter Name

Counter Description

Original Release

50331823

VS.APCCQI.MEA N

Average CQI Of All Phase Based On APC Algorithm


50341722

VS.DataCQI.MEA N

Average CQI Reported by All UEs That Have Data to Transmit


50331722

VS.HSDPA. 16QAMCfg.ActedNum

Total number of times all the users in a cell use 16QAM mode


50331723

VS.HSDPA.QPSK Cfg.ActedNum

Total number of times users use the QPSK mode


50331724

VS.HSDPA.All.Sch eduledNum

Total number of times all the users are scheduled in a cell


50331709


Total number of times all the users in a cell use the 64QAM mode


50331710

VS.HSDPA. 64QAMCfg.Schedu ledNum

Total number of times all the users in 64QAM mode are scheduled in a cell


50331711

VS.MIMOCfg.ActedNum

Total number of times all the MIMOenabled users use two transport blocks in a cell


50331712

VS.MIMOCfg.Sche duledNum

Total number of times all the MIMOenabled users are scheduled in a cell


Issue 11 (2015–05–30)


16



Counter ID

Counter Name

Counter Description

Original Release

50331717

VS.HSDPA.MIMO 64QAMCfg.ActedNum

Number of times that all the users configured in 64QAM+MIMO mode in a cell employ 64QAM during the measurement period


50331718

VS.HSDPA.MIMO 64QAMCfg.Schedu ledNum

Number of times that all the users configured in 64QAM+MIMO mode in a cell are scheduled during the measurement period


50331719

VS.HSDPA.DCCfg. AnchorCarrierActedNum

Number of times that all the users configured in DC mode in a cell are scheduled by AnchorCarrier during the measurement period


50331720

VS.HSDPA.DCCfg. SupCarrierActedNum

Total number of times DC-HSDPAenabled users are scheduled by the supplementary carrier


50331721

VS.HSDPA.DCCfg. DualCarrierActedNum

Total number of times DC-HSDPAenabled users are scheduled by the anchor and supplementary carriers at the same time


50341658

VS.UserTtiRatio.M ean

Ratio of the time when at least one HSDPA UE camps on the cell


Issue 11 (2015–05–30)


17



Counter ID

Counter Name

Counter Description

Original Release

50341659

VS.DataTtiRatio.M ean

Ratio of the time when at least one HSDPA user has data to transmit in the queue buffer


50341693

VS.HSDPA.Inactiv eDataTtiRatio.Mea n

Number of TTIs in which at least one HSDPA user in a cell has TRB data to transmit in the queue buffer but there is no conventional TRB data transmission at the physical layer


50341739

VS.HSDPA.ScheIn activeDataTtiRatio. Mean

Average ratio of the time when some HSDPA users are queued in the scheduling candidate set but do not transmit data


50331839

VS.HSDPA.DataTt iNum.TRB

Number of TTIs in which TRB data is to be transmitted in the HSDPA user queue in a cell


50331840

VS.HSDPA.Inactiv eDataTtiNum.TRB

Number of TTIs in which at least one HSDPA user in a cell has TRB data to transmit in the queue buffer but there is no conventional TRB data transmission at the physical layer .


50331745

VS.HSDPA.DataTt iNum.User

Total number of user-level TTIs within which there is data to transmit in HSDPA user queue buffers


Issue 11 (2015–05–30)


18



Counter ID

Counter Name

Counter Description

Original Release

50332215

VS.DCHSDPA.Dat aTtiNum.User

Total number of user-level TTIs within which there is data to transmit in DC-HSDPA/DCHSDPA+MIMO user queue buffers


50332173

VS.DBHSDPA.Dat aTtiNum.User

Total number of user-level TTIs within which there is data to transmit in DB-HSDPA/DBHSDPA+MIMO user queue buffers


50332217

VS. 3CHSDPA.DataTti Num.User

Total number of user-level TTIs within which there is data to transmit in 3C-HSDPA/3CHSDPA+MIMO user queue buffers


50332174

VS. 4CHSDPA.DataTti Num.User

Total number of user-level TTIs within which there is data to transmit in 4C-HSDPA/4CHSDPA+MIMO user queue buffers


50341694

VS.HSDPA. 2ScchCodeRatio

The time ratio of only using two HS-SCCH codes for cell


50341695


The time ratio of only using three HSSCCH codes for cell


50341696


The time ratio of only using four HS-SCCH codes for cell


Issue 11 (2015–05–30)


19



Counter ID

Counter Name

Counter Description

Original Release

50341690

VS.PdschCodeAvai l.Mean

Average number of available HSPDSCH codes in a cell


50341691

VS.PdschCodeAvai l.Max

Maximum number of available HSPDSCH codes in a cell


50341688

VS.PdschCodeUsed .Mean

Average number of used HS-PDSCH codes in a cell


50341689

VS.PdschCodeUsed .Max

Maximum number of used HS-PDSCH codes in a cell


50341692

VS.PdschCodeUsed .Min

Minimum number of used HS-PDSCH codes in a cell


50341648

VS.ScchCodeUtil. Mean

Average usage of HS-SCCH code resources in a cell


50341649

VS.ScchCodeUtil. Max

Maximum usage of HS-SCCH code resources in a cell


50341650

VS.ScchCodeUtil. Min

Minimum usage of HS-SCCH code resources in a cell


50341654

VS.ScchCodeUtil. Mean.User

Average usage of HS-SCCH code resources when HSDPA users camp on the cell


Issue 11 (2015–05–30)


20



Counter ID

Counter Name

Counter Description

Original Release

50341655

VS.ScchCodeUtil. Mean.Data

Average usage of HS-SCCH code resources when at least one HSDPA user has data to transmit in the queue buffer


50341651

VS.PdschCodeUtil. Mean

Average usage of HS-PDSCH code resources in a cell


50341652

VS.PdschCodeUtil. Max

Maximum usage of HS-PDSCH code resources in a cell


50341653

VS.PdschCodeUtil. Min

Minimum usage of HS-PDSCH code resources in a cell


50341656

VS.PdschCodeUtil. Mean.User

Average usage of HS-PDSCH code resources when HSDPA users camp on the cell


50341657

VS.PdschCodeUtil. Mean.Data

Average usage of HS-PDSCH code resources when at least one HSDPA user has data to transmit in the queue buffer


50341675

VS.ScchPwrRatio. Mean

Average transmit power over the HSSCCH in a cell


Issue 11 (2015–05–30)


21



Counter ID

Counter Name

Counter Description

Original Release

50341676

VS.ScchPwrRatio. Max

Maximum transmit power over the HSSCCH in a cell


50341677

VS.ScchPwrRatio. Min

Minimum transmit power over the HSSCCH in a cell


50341681

VS.ScchPwrRatio. User

Average transmit power over the HSSCCH when HSDPA users camp on the cell


50341683

VS.ScchPwrRatio. UserData

Average transmit power over the HSSCCH when at least one HSDPA user has data to transmit in the queue buffer


50341678

VS.PdschPwrRatio .Mean

Average transmit power over the HSPDSCH in a cell


50341679

VS.PdschPwrRatio .Max

Maximum transmit power over the HSPDSCH in a cell


50341680

VS.PdschPwrRatio .Min

Minimum transmit power over the HSPDSCH in a cell


50341682

VS.PdschPwrRatio .User

Average transmit power over the HSPDSCH when HSDPA users camp on the cell


Issue 11 (2015–05–30)


22



Counter ID

Counter Name

Counter Description

Original Release

50341684

VS.PdschPwrRatio .Data

Average transmit power over the HSPDSCH when at least one HSDPA user has data to transmit in the queue buffer


50341697

VS.HSDPAPwrRat io.Mean.FreeUser

Average usage of free users Hsdpa Power


50341698

VS.HSDPAPwrRat io.Max.FreeUser

Maximum usage of free users Hsdpa Power


50341703

VS.AvaiHSDPAPw rRatio.Mean

Mean ratio of availble HSDPA Power Ratio


50341704

VS.AvaiHSDPAPw rRatio.Max

Maximum ratio of availble HSDPA Power Ratio


50341705

VS.AvaiHSDPAPw rRatio.Min

Minimum ratio of availble HSDPA Power Ratio


50341706

VS.HSDPAPwrRat io.PLMN0

Mean Ratio of PLMN0 used HSDPA Power


50341707




50341708




50341709




Issue 11 (2015–05–30)


23



Counter ID

Counter Name

Counter Description

Original Release

50341710

VS.HSDPAPwrRat io.SharedOperator0

Average HSDPA power ratio for operator 0 in a cell of an MOCN network


50341711




50341712




50341713




50341714

VS.HSDPAPwrRat io.Mean.ResG0

Average permillage of transmit power for HSDPA users in resource group 0 to the maximum cell transmit power


50341715




50341716




50341717




Issue 11 (2015–05–30)


24



Counter ID

Counter Name

Counter Description

Original Release

50341660

VS.RabNum.Mean

Average number of HSDPA RABs in a cell


50341661

VS.RabNum.Max

Maximum number of HSDPA RABs in a cell


50341662

VS.RabNum.Min

Minimum number of HSDPA RABs in a cell


50341666

VS.RabNumAve.U ser

Average number of HSDPA RABs when HSDPA users camp on the cell


50341663

VS.DataRabNum. Mean

Average number of HSDPA RABs have data to transmit in the queue buffer in a cell


50341664

VS.DataRabNum. Max

Maximum number of HSDPA RABs have data to transmit in the queue buffer in a cell


50341665

VS.DataRabNum. Min

Minimum number of HSDPA RABs have data to transmit in the queue buffer in a cell


50341667

VS.RabNumAve.U serData

Average number of HSDPA RABs have data to transmit in the queue buffer when at least one HSDPA user has data to transmit in the queue buffer in a cell


Issue 11 (2015–05–30)


25



Counter ID

Counter Name

Counter Description

Original Release

50341668

VS.DataOutput.Me an

Average throughput of MAC-d PDUs in a cell


50341669

VS.DataOutput.Ma x

Maximum throughput of MACd PDUs in a cell


50341670

VS.DataOutput.Mi n

Minimum throughput of MACd PDUs in a cell


50341671

VS.DataOutput.Us er

Average cell throughput when HSDPA users camp on the cell


50341672

VS.DataOutput.Us erData

Average cell throughput when at least one HSDPA user has data to transmit in the queue buffer


50341673

VS.DataOutput.Ra b

Average throughput of each RAB when HSDPA users camp on the cell


50341674

VS.DataOutput.Ra bData

Average throughput of each RAB when at least one HSDPA user has data to transmit in the queue buffer


50341699

VS.DataOutput.Me an.FreeUser

Average throughput of MAC-d PDUs of HSDPA free users


Issue 11 (2015–05–30)


26



Counter ID

Counter Name

Counter Description

Original Release

50341700

VS.DataOutput.Ma x.FreeUser

Maximum throughput of MACd PDUs of HSDPA free users


50341701

VS.DataOutput.Mi n.FreeUser

Minimum throughput of MACd PDUs of HSDPA free users


50331838

VS.HSDPA.DataO utput.TRB

HSDSCH TRB traffic volume in a cell


50331746

VS.HSDPA.DataO utput.Traffic

Traffic volume of the MAC-hs/MAC-ehs PDUs successfully received in a cell


50332170

VS.DataOutput.DC HSDPA.Traffic

MAC-ehs traffic volume of DCHSDPA/DCHSDPA+MIMO users


50332168

VS.DataOutput.DB HSDPA.Traffic

MAC-ehs traffic volume of DBHSDPA/DBHSDPA+MIMO users


50332216

VS.DataOutput. 3CHSDPA.Traffic

MAC-ehs traffic volume of 3CHSDPA/3C-HSDPA +MIMO users


50332169


MAC-ehs traffic volume of 4CHSDPA/4C-HSDPA +MIMO users


50341685

VS.DataDiscardRa tio.Mean

Average ratio of discarded HSDPA data due to timer expiry


Issue 11 (2015–05–30)


27



Counter ID

Counter Name

Counter Description

Original Release

50341686

VS.DataDiscardRa tio.Max

Maximum ratio of discarded HSDPA data due to timer expiry


50341687

VS.DataDiscardRa tio.Min

Minimum ratio of discarded HSDPA data due to timer expiry


50331713

VS.SCPICH.AvgPo werRate

Ratio of the actual transmit power of the SCPICH to the power of the SCPICH configured by the RNC


50331714

VS.SCPICH.PwrO n.Duration

Power-enabled duration of the SCPICH in a cell


50341702

VS.HSDPA.DCCfg. SupCarrierDeact.T imeRatio

The Ratio Of Dc Deact


50341740

VS.HSDPA.DpchM axPwrRestr.ActRatio

Maximum DPCH power restriction algorithm validity probability


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

Issue 11 (2015–05–30)


28


Root Counter


Level-1 Counter VS.AckRetrans.6 VS.AckRetrans.7 VS.AckRetrans.8 VS.AckRetrans.9 VS.AckRetrans.10

VS.HSDPA.DataTtiNum.TRB

VS.HSDPA.InactiveDataTtiNum.TRB

VS.RabNum.Mean

VS.DataRabNum.Mean

VS.RabNum.Max

VS.DataRabNum.Max

VS.RabNum.Min

VS.DataRabNum.Min

Number of HARQ-Related Messages from HSDPA Users Received in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331654

VS.AckTotal

Total number of ACKs received

BTS3900, BTS3900 WCDMA

U

50331655

VS.NackTotal

Total number of NACKs received


U

50331656

VS.DtxTotal

Total number of TTIs when the NodeB can not translate the acknowledgeme nt information from the UE


U

50331657

VS.AckFirst

Number of ACKs received after 1st transmission


U

50331658

VS.AckRetrans. 1

Number of ACKs received after 1st retransmission


U

Issue 11 (2015–05–30)


29



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331659

VS.AckRetrans. 2

Number of ACKs received after 2nd retransmission


U

50331660

VS.AckRetrans. 3

Number of ACKs received after 3rd retransmission


U

50331661

VS.AckRetrans. 4



U

50331662

VS.AckRetrans. 5



U

50331663

VS.AckRetrans. 6



U

50331664

VS.AckRetrans. 7



U

50331665

VS.AckRetrans. 8



U

50331666

VS.AckRetrans. 9



U

50331667

VS.AckRetrans. 10



U

Issue 11 (2015–05–30)


30



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331668

VS.AckRemain

Number of times the NodeB does not receive the ACK from the UE after the last retransmission


U

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: Counter Name

Description

VS.AckTotal

Number of ACK messages received during the measurement period.

VS.NackTotal

Number of NACK messages received during the measurement period.

VS.DtxTotal

This counter measures the total number of TTIs when the NodeB can not translate the acknowledgement information from the UE after transmitting data to the UE within a measurement period.

VS.AckFirst

Number of ACK messages received after the first data transmission.

VS.AckRetrans.1

VS.AckRetrans.Num refers to the number of ACK messages received after the first data retransmission.

VS.AckRetrans.2

VS.AckRetrans.Num refers to the number of ACK messages received after the second data retransmission.

VS.AckRetrans.3

VS.AckRetrans.Num refers to the number of ACK messages received after the third data retransmission.

VS.AckRetrans.4

VS.AckRetrans.Num refers to the number of ACK messages received after the 4th data retransmission.

Issue 11 (2015–05–30)


31



Counter Name

Description

VS.AckRetrans.5


VS.AckRetrans.6


VS.AckRetrans.7


VS.AckRetrans.8


VS.AckRetrans.9


VS.AckRetrans.10


VS.AckRemain

Number of data blocks whose maximum number of retransmissions is reached but no ACK message is received. The maximum number of retransmissions depends on the data configuration.

Measurement Points The NodeB measures the preceding counters when demodulating the HARQ-ACK information carried on the HS-DPCCH from the HSDPA UE.The NACK or DTX messages are received after the data at the physical layer fails to be transmitted. 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

Issue 11 (2015–05–30)


32



Related Features Counter Name

Feature ID

VS.AckTotal

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-01061009 LTE: None

VS.NackTotal

HSDPA H-ARQ & Scheduling (MAX C/I, RR and PF)

Multi-mode: None GSM: None UMTS: WRFD-01061009 LTE: None

VS.DtxTotal



VS.AckFirst



VS.AckRetrans.1



VS.AckRetrans.2



Issue 11 (2015–05–30)



33



Counter Name

Feature ID

VS.AckRetrans.3

Multi-mode: None

Feature Name


VS.AckRetrans.4



VS.AckRetrans.5



VS.AckRetrans.6



VS.AckRetrans.7



VS.AckRetrans.8



Issue 11 (2015–05–30)



34



Counter Name

Feature ID

VS.AckRetrans.9

Multi-mode: None

Feature Name


VS.AckRetrans.10



VS.AckRemain




HARQ Distribution for MIMO Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331816

VS.MIMODUA LSTREAM1.D TX

Number Of MIMO Anchor Stream DTX


U

50331817

VS.MIMODUA LSTREAM2.D TX

Number Of MIMO SupStream DTX


U

50331818

VS.MIMODUA LSTREAM1.A CK

Number Of MIMO Anchor Stream ACK


U

50331819

VS.MIMODUA LSTREAM2.A CK

Number Of MIMO SupStream ACK


U

Issue 11 (2015–05–30)


35



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331820

VS.MIMODUA LSTREAM1.N ACK

Number Of MIMO Anchor Stream NACK


U

50331821

VS.MIMODUA LSTREAM2.N ACK

Number Of MIMO SupStream NACK


U

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


Feature ID

VS.MIMODUALSTREAM 1.DTX

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-010684

2*2 MIMO

LTE: None VS.MIMODUALSTREAM 2.DTX

Multi-mode: None GSM: None UMTS: WRFD-010684

2*2 MIMO

LTE: None

Issue 11 (2015–05–30)


36



Counter Name

Feature ID

VS.MIMODUALSTREAM 1.ACK

Multi-mode: None

Feature Name


2*2 MIMO

LTE: None VS.MIMODUALSTREAM 2.ACK


2*2 MIMO

LTE: None VS.MIMODUALSTREAM 1.NACK


2*2 MIMO

LTE: None VS.MIMODUALSTREAM 2.NACK


2*2 MIMO

LTE: None

Number of CQIs from HSDPA Users Received in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331669

VS.CQI.0



U

50331670

VS.CQI.1



U

50331671

VS.CQI.2



U

50331672

VS.CQI.3



U

Issue 11 (2015–05–30)


37



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331673

VS.CQI.4



U

50331674

VS.CQI.5



U

50331675

VS.CQI.6



U

50331676

VS.CQI.7



U

50331677

VS.CQI.8



U

50331678

VS.CQI.9



U

50331679

VS.CQI.10



U

50331680

VS.CQI.11



U

50331681

VS.CQI.12



U

50331682

VS.CQI.13



U

50331683

VS.CQI.14



U

50331684

VS.CQI.15



U

50331685

VS.CQI.16



U

Issue 11 (2015–05–30)


38



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331686

VS.CQI.17



U

50331687

VS.CQI.18



U

50331688

VS.CQI.19



U

50331689

VS.CQI.20



U

50331690

VS.CQI.21



U

50331691

VS.CQI.22



U

50331692

VS.CQI.23



U

50331693

VS.CQI.24



U

50331694

VS.CQI.25



U

50331695

VS.CQI.26



U

50331696

VS.CQI.27



U

50331697

VS.CQI.28



U

50331698

VS.CQI.29



U

Issue 11 (2015–05–30)


39



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331699

VS.CQI.30



U

50331725

VS.CQI.31

Number of Cqi31

BTS3900 WCDMA

U

50331726

VS.CQI.32

Number of Cqi32

BTS3900 WCDMA

U

50331727

VS.CQI.33

Number of Cqi33

BTS3900 WCDMA

U

50331728

VS.CQI.34

Number of Cqi34

BTS3900 WCDMA

U

50331729

VS.CQI.35

Number of Cqi35

BTS3900 WCDMA

U

Description The preceding counters indicate the overall distribution of the channel quality for HSDPA users. For each Channel Quality Indicators (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. Disuse Statement: The counter 50331725 VS.CQI.31 will be deleted in later version. In current version, the value of this counter is 0. This counter is not recommended. The counter 50331726 VS.CQI.32 will be deleted in later version. In current version, the value of this counter is 0. This counter is not recommended. The counter 50331727 VS.CQI.33 will be deleted in later version. In current version, the value of this counter is 0. This counter is not recommended. The counter 50331728 VS.CQI.34 will be deleted in later version. In current version, the value of this counter is 0. This counter is not recommended. The counter 50331729 VS.CQI.35 will be deleted in later version. In current version, the value of this counter is 0. This counter is not recommended.

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.

Issue 11 (2015–05–30)


40



Formula None

Unit None


Feature ID

VS.CQI.0

Multi-mode: None

Feature Name


HSDPA Power Control

LTE: None VS.CQI.1


HSDPA Power Control

LTE: None VS.CQI.2


HSDPA Power Control

LTE: None VS.CQI.3


HSDPA Power Control

LTE: None VS.CQI.4


HSDPA Power Control

LTE: None VS.CQI.5


HSDPA Power Control

LTE: None VS.CQI.6


HSDPA Power Control

LTE: None

Issue 11 (2015–05–30)


41



Counter Name

Feature ID

VS.CQI.7

Multi-mode: None

Feature Name


HSDPA Power Control

LTE: None VS.CQI.8


HSDPA Power Control

LTE: None VS.CQI.9


HSDPA Power Control

LTE: None VS.CQI.10


HSDPA Power Control

LTE: None VS.CQI.11


HSDPA Power Control

LTE: None VS.CQI.12


HSDPA Power Control

LTE: None VS.CQI.13


HSDPA Power Control

LTE: None VS.CQI.14


HSDPA Power Control

LTE: None

Issue 11 (2015–05–30)


42



Counter Name

Feature ID

VS.CQI.15

Multi-mode: None

Feature Name


HSDPA Power Control

LTE: None VS.CQI.16


HSDPA Power Control

LTE: None VS.CQI.17


HSDPA Power Control

LTE: None VS.CQI.18


HSDPA Power Control

LTE: None VS.CQI.19


HSDPA Power Control

LTE: None VS.CQI.20


HSDPA Power Control

LTE: None VS.CQI.21


HSDPA Power Control

LTE: None VS.CQI.22


HSDPA Power Control

LTE: None

Issue 11 (2015–05–30)


43



Counter Name

Feature ID

VS.CQI.23

Multi-mode: None

Feature Name


HSDPA Power Control

LTE: None VS.CQI.24


HSDPA Power Control

LTE: None VS.CQI.25


HSDPA Power Control

LTE: None VS.CQI.26


HSDPA Power Control

LTE: None VS.CQI.27


HSDPA Power Control

LTE: None VS.CQI.28


HSDPA Power Control

LTE: None VS.CQI.29


HSDPA Power Control

LTE: None VS.CQI.30


HSDPA Power Control

LTE: None

Issue 11 (2015–05–30)


44



Counter Name

Feature ID

VS.CQI.31

Multi-mode: None

Feature Name


HSDPA Power Control

LTE: None VS.CQI.32


HSDPA Power Control

LTE: None VS.CQI.33


HSDPA Power Control

LTE: None VS.CQI.34


HSDPA Power Control

LTE: None VS.CQI.35


HSDPA Power Control

LTE: None

Number of CQIs Used for HSDPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331754

VS.UsedCQI0



U

50331755

VS.UsedCQI1



U

Issue 11 (2015–05–30)


45



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331756

VS.UsedCQI2



U

50331757

VS.UsedCQI3



U

50331758

VS.UsedCQI4



U

50331759

VS.UsedCQI5



U

50331760

VS.UsedCQI6



U

50331761

VS.UsedCQI7



U

50331762

VS.UsedCQI8



U

50331763

VS.UsedCQI9



U

50331764

VS.UsedCQI10



U

50331765

VS.UsedCQI11



U

Issue 11 (2015–05–30)


46



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331766

VS.UsedCQI12



U

50331767

VS.UsedCQI13



U

50331768

VS.UsedCQI14



U

50331769

VS.UsedCQI15



U

50331770

VS.UsedCQI16



U

50331771

VS.UsedCQI17



U

50331772

VS.UsedCQI18



U

50331773

VS.UsedCQI19



U

50331774

VS.UsedCQI20



U

50331775

VS.UsedCQI21



U

Issue 11 (2015–05–30)


47



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331776

VS.UsedCQI22



U

50331777

VS.UsedCQI23



U

50331778

VS.UsedCQI24



U

50331779

VS.UsedCQI25



U

50331780

VS.UsedCQI26



U

50331781

VS.UsedCQI27



U

50331782

VS.UsedCQI28



U

50331783

VS.UsedCQI29



U

50331784

VS.UsedCQI30



U

50331785

VS.UsedCQI31 to39

Number of times the NodeB transmits data with CQI=[31, 39]


U

Issue 11 (2015–05–30)


48



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/MACehs scheduling is complete. The preceding counters do not measure the CQIs sent by the MIMO users.

Formula None

Unit None


Feature ID

VS.UsedCQI0

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-010610 WRFD-01061018 WRFD-01061019 LTE: None

VS.UsedCQI1

HSDPA Introduction Package Time and HS-PDSCH Codes Multiplex HSDPA Dynamic Power Allocation

Multi-mode: None GSM: None UMTS: WRFD-010610 WRFD-01061018 WRFD-01061019 LTE: None

Issue 11 (2015–05–30)



49



Counter Name

Feature ID

VS.UsedCQI2

Multi-mode: None

Feature Name


VS.UsedCQI3



VS.UsedCQI4



VS.UsedCQI5



Issue 11 (2015–05–30)



50



Counter Name

Feature ID

VS.UsedCQI6

Multi-mode: None

Feature Name


VS.UsedCQI7



VS.UsedCQI8



VS.UsedCQI9



Issue 11 (2015–05–30)



51



Counter Name

Feature ID

VS.UsedCQI10

Multi-mode: None

Feature Name


VS.UsedCQI11



VS.UsedCQI12



VS.UsedCQI13



Issue 11 (2015–05–30)



52



Counter Name

Feature ID

VS.UsedCQI14

Multi-mode: None

Feature Name


VS.UsedCQI15



VS.UsedCQI16



VS.UsedCQI17



Issue 11 (2015–05–30)



53



Counter Name

Feature ID

VS.UsedCQI18

Multi-mode: None

Feature Name


VS.UsedCQI19



VS.UsedCQI20



VS.UsedCQI21



Issue 11 (2015–05–30)



54



Counter Name

Feature ID

VS.UsedCQI22

Multi-mode: None

Feature Name


VS.UsedCQI23



VS.UsedCQI24



VS.UsedCQI25



Issue 11 (2015–05–30)



55



Counter Name

Feature ID

VS.UsedCQI26

Multi-mode: None

Feature Name


VS.UsedCQI27



VS.UsedCQI28



VS.UsedCQI29



Issue 11 (2015–05–30)



56



Counter Name

Feature ID

VS.UsedCQI30

Multi-mode: None

Feature Name


VS.UsedCQI31to39




MIMO Dual CQI Distribution In a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331786

VS.MIMODual CQI1.0



U

50331787

VS.MIMODual CQI1.1



U

50331788

VS.MIMODual CQI1.2



U

Issue 11 (2015–05–30)


57



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331789

VS.MIMODual CQI1.3



U

50331790

VS.MIMODual CQI1.4



U

50331791

VS.MIMODual CQI1.5



U

50331792

VS.MIMODual CQI1.6



U

50331793

VS.MIMODual CQI1.7



U

50331794

VS.MIMODual CQI1.8



U

50331795

VS.MIMODual CQI1.9



U

50331796

VS.MIMODual CQI1.10



U

50331797

VS.MIMODual CQI1.11



U

50331798

VS.MIMODual CQI1.12



U

Issue 11 (2015–05–30)


58



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331799

VS.MIMODual CQI1.13



U

50331800

VS.MIMODual CQI1.14



U

50331801

VS.MIMODual CQI2.0



U

50331802

VS.MIMODual CQI2.1



U

50331803

VS.MIMODual CQI2.2



U

50331804

VS.MIMODual CQI2.3



U

50331805

VS.MIMODual CQI2.4



U

50331806

VS.MIMODual CQI2.5



U

50331807

VS.MIMODual CQI2.6



U

50331808

VS.MIMODual CQI2.7



U

Issue 11 (2015–05–30)


59



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331809

VS.MIMODual CQI2.8



U

50331810

VS.MIMODual CQI2.9



U

50331811

VS.MIMODual CQI2.10



U

50331812

VS.MIMODual CQI2.11



U

50331813

VS.MIMODual CQI2.12



U

50331814

VS.MIMODual CQI2.13



U

50331815

VS.MIMODual CQI2.14



U

Description The preceding counters indicate the distribution of dual CQIs reported by MIMO users in a cell, evaluating the channel conditions for MIMO users.

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.

Issue 11 (2015–05–30)


60



Formula None

Unit None


Feature ID

VS.MIMODualCQI1.0

Multi-mode: None

Feature Name


2*2 MIMO

LTE: None VS.MIMODualCQI1.1


2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO

LTE: None

Issue 11 (2015–05–30)


61



Counter Name

Feature ID

VS.MIMODualCQI1.7

Multi-mode: None

Feature Name


2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO

LTE: None

Issue 11 (2015–05–30)


62



Counter Name

Feature ID

VS.MIMODualCQI2.0

Multi-mode: None

Feature Name


2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO

LTE: None

Issue 11 (2015–05–30)


63



Counter Name

Feature ID

VS.MIMODualCQI2.8

Multi-mode: None

Feature Name


2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO



2*2 MIMO

LTE: None

Average CQI Of Phase 0 Based On APC Algorithm in a Cell

Issue 11 (2015–05–30)


64



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331822

VS.APCPhase0 CQI.MEAN

Average CQI Of Phase 0 Based On APC Algorithm

BTS3900 WCDMA

U

Description The preceding counter indicates the average value of reported CQIs corresponding to phase 0 in all phase shift periods when the automatic phase control (APC) algorithm is used in a cell, evaluating the channel quality of users with data transmission in the cell when the VAM algorithm does not take effect. The value has been amplified by 1000 times. For example, the value 29100 stands for the CQI value 29.1. Disuse Statement: The counter 50331822 VS.APCPhase0CQI.MEAN will be deleted and replaced by 50341722 VS.DataCQI.MEAN in later versions. In current version, both the counters take effect but VS.APCPhase0CQI.MEAN is not recommended.

Measurement Points Within the measurement period, the NodeB counts the sum of reported CQI values corresponding to Phase 0 in a cell when the automatic phase control (APC) algorithm takes effect. Assume that this value is A. The NodeB counts the total number of reported CQI samples corresponding to Phase 0 within the measurement period. Assume that this value is B. Then, VS.APCPhase0CQI.MEAN = A/B.

Formula None

Unit None

Issue 11 (2015–05–30)


65




Feature ID

VS.APCPhase0CQI.MEAN

Multi-mode: None

Feature Name


Performance Improvement of MIMO and HSDPA Cocarrier

WRFD-030011 LTE: None

MIMO Prime

Average CQI Of All Phase Based On APC Algorithm in cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331823

VS.APCCQI.M EAN

Average CQI Of All Phase Based On APC Algorithm

BTS3900 WCDMA

U

Description The preceding counter indicates the average value of CQIs reported by all 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. Disuse Statement: The counter 50331823 VS.APCCQI.MEAN will be deleted and replaced by 50341722 VS.DataCQI.MEAN in later versions. In current version, both the counters take effect but VS.APCCQI.MEAN is not recommended.

Measurement Points Within the measurement period, the NodeB counts the sum of CQI values reported by all users that have data to transmit in a cell. Assume that this value is A. The NodeB counts the total number of reported CQI samples within the measurement period. Assume that this value is B. Then, VS.APCCQI.MEAN = A/B.

Formula None Issue 11 (2015–05–30)


66



Unit None


Feature ID

VS.APCCQI.MEAN

Multi-mode: None

Feature Name




MIMO Prime

Average CQI Reported by All HSDPA UEs That Have Data to Transmit. Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341722

VS.DataCQI.M EAN

Average CQI Reported by All UEs That Have Data to Transmit


U

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.

Measurement Points The accumulated CQI values reported by HSDPA UEs that have data to transmit is A, and the number of CQI samples reported by HSDPA UEs that have data to transmit is B. The formula for calculating this counter is: VS.DataCQI.MEAN = A/B.



67



Unit per mill


Feature ID

VS.DataCQI.MEAN

Multi-mode: None

Feature Name


MIMO Prime

WRFD-010700


LTE: None

Statistics on Modulation Schemes for HSDPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331722

VS.HSDPA. 16QAMCfg.Act edNum

Total number of times all the users in a cell use 16QAM mode


U

50331723

VS.HSDPA.QP SKCfg.ActedN um

Total number of times users use the QPSK mode


U

50331724

VS.HSDPA.All .ScheduledNum

Total number of times all the users are scheduled in a cell


U

Description The following table describes the meanings of each counter:

Issue 11 (2015–05–30)


68



Counter Name

Description

VS.HSDPA.16QAMCfg.ActedNum

This counter measures the total number of times all the HSDPA users in a cell use 16QAM within a measurement period.

VS.HSDPA.QPSKCfg.ActedNum

This counter measures the total number of times all the HSDPA users in a cell use QPSK within a measurement period.

VS.HSDPA.All.ScheduledNum

This counter measures the total number of times all the HSDPA users in a cell are scheduled within a measurement period.

Measurement Points The NodeB takes statistics about the preceding counters for HSDPA users when MAC-hs/MACehs 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


Feature ID


Multi-mode: None GSM: None UMTS: WRFD-010610 WRFD-010629 LTE: None

Issue 11 (2015–05–30)

Feature Name


HSDPA Introduction Package DL 16QAM Modulation

69



Counter Name

Feature ID

VS.HSDPA.QPSKCfg.ActedNum

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-010610 WRFD-01061017

QPSK Modulation

LTE: None VS.HSDPA.All.ScheduledNum

HSDPA Introduction Package


HSDPA H-ARQ & Scheduling (MAX C/I, RR and PF) HSDPA Introduction Package

Statistics on 64QAM Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331709

VS.HSDPA. 64QAMCfg.Act edNum

Total number of times all the users in a cell use the 64QAM mode


U

50331710

VS.HSDPA. 64QAMCfg.Sc heduledNum

Total number of times all the users in 64QAM mode are scheduled in a cell


U


Issue 11 (2015–05–30)


70



Counter Name

Description

VS.HSDPA.64QAMCfg.ActedNum

This counter measures the total number of times that 64QAM users transmitting datas with 64QAM modulation method are scheduled in a cell within a measurement period.

VS.HSDPA.64QAMCfg.ScheduledNum

This counter measures the total number of times that 64QAM users transmitting datas with QPSK, 16QAM, or 64QAM modulation method are scheduled in a cell within a measurement period.

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


Feature ID


Multi-mode: None

Feature Name


Downlink 64QAM Downlink Enhanced L2

LTE: None VS.HSDPA. 64QAMCfg.ScheduledNum

Multi-mode: None GSM: None UMTS: WRFD-010683 WRFD-010685

Downlink 64QAM Downlink Enhanced L2

LTE: None

Issue 11 (2015–05–30)


71



Statistics on 2x2 MIMO Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331711

VS.MIMOCfg. ActedNum

Total number of times all the MIMO-enabled users use two transport blocks in a cell


U

50331712

VS.MIMOCfg. ScheduledNum

Total number of times all the MIMO-enabled users are scheduled in a cell


U

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


Feature ID

VS.MIMOCfg.ActedNum

Multi-mode: None

Feature Name


2*2 MIMO Downlink Enhanced L2

LTE: None Issue 11 (2015–05–30)


72



Counter Name

Feature ID

VS.MIMOCfg.ScheduledNum

Multi-mode: None

Feature Name


2*2 MIMO

WRFD-010685

Downlink Enhanced L2

LTE: None

Statistics on 64QAM+MIMO Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331717

VS.HSDPA.MI MO64QAMCfg .ActedNum

Number of times that all the users configured in 64QAM +MIMO mode in a cell employ 64QAM during the measurement period


U

50331718

VS.HSDPA.MI MO64QAMCfg .ScheduledNum

Number of times that all the users configured in 64QAM +MIMO mode in a cell are scheduled during the measurement period


U

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 Issue 11 (2015–05–30)


73



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. For users with two transport blocks, the VS.HSDPA.MIMO64QAMCfg.ActedNum counter is measured on each transport block separately.

Formula None

Unit None


Feature ID

VS.HSDPA.MIMO64QAM Cfg.ActedNum


VS.HSDPA.MIMO64QAM Cfg.ScheduledNum

Feature Name

DL 64QAM+MIMO HSPA+Downlink 42Mbps per User HSDPA Introduction Package


HSDPA Introduction Package HSPA+Downlink 42Mbps per User DL 64QAM+MIMO

Statistics on DC Users in a Cell

Issue 11 (2015–05–30)


74



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331719

VS.HSDPA.DC Cfg.AnchorCarrierActedNum

Number of times that all the users configured in DC mode in a cell are scheduled by AnchorCarrier during the measurement period


U

50331720

VS.HSDPA.DC Cfg.SupCarrierActedNum

Total number of times DCHSDPAenabled users are scheduled by the supplementary carrier


U

50331721

VS.HSDPA.DC Cfg.DualCarrier ActedNum

Total number of times DCHSDPAenabled users are scheduled by the anchor and supplementary carriers at the same time


U

Description The following table describes the meanings of each counter: Counter Name

Description

VS.HSDPA.DCCfg.AnchorCarrierActedNum

This counter measures the number of times the users whose anchor carrier is the carrier of a DC-HSDPA cell are scheduled by the anchor carrier during a measurement period.

Issue 11 (2015–05–30)


75



Counter Name

Description

VS.HSDPA.DCCfg.SupCarrierActedNum

This counter measures the number of times the users whose supplementary carrier is the carrier of a DC-HSDPA cell are scheduled by the supplementary carrier during a measurement period.

VS.HSDPA.DCCfg.DualCarrierActedNum

This counter measures the number of times the users whose anchor carrier is the carrier of a DC-HSDPA cell are scheduled by the anchor and supplementary carriers at the same time during a measurement period.

Measurement Points The NodeB takes statistics about the preceding counters 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 anchor and supplementary carriers at the same time, the VS.HSDPA.DCCfg.AnchorCarrierActedNum counter is only incremented by 1. 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 a user is scheduled by the anchor and supplementary carriers at the same time, the VS.HSDPA.DCCfg.SupCarrierActedNum counter is only incremented by 1.

Formula None

Unit None


Feature ID

VS.HSDPA.DCCfg.AnchorCarrierActedNum


Issue 11 (2015–05–30)

Feature Name


HSDPA Introduction Package HSPA+Downlink 42Mbps per User DC-HSDPA

76



Counter Name

Feature ID

VS.HSDPA.DCCfg.SupCarrierActedNum

Multi-mode: None

Feature Name



WRFD-010689

HSPA+Downlink 42Mbps per User


VS.HSDPA.DCCfg.DualCarrierActedNum

DC-HSDPA



WRFD-010689

HSPA+Downlink 42Mbps per User


DC-HSDPA

Time Ratio for HSDPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341658

VS.UserTtiRati o.Mean

Ratio of the time when at least one HSDPA UE camps on the cell


U

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 Issue 11 (2015–05–30)


77



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


Feature ID

VS.UserTtiRatio.Mean

Multi-mode: None

Feature Name



LTE: None

Time Ratio for HSDPA User with Data to be Transmitted in the Queue Buffer in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341659

VS.DataTtiRati o.Mean

Ratio of the time when at least one HSDPA user has data to transmit in the queue buffer


U

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, Issue 11 (2015–05–30)


78



VS.DataTtiRatio.Mean = A/B. For DC-HSDPA users, the counter is measured in the anchor carrier and the supplementary carrier separately.The counter is measured at point C in the following figure: Figure 1-1

Formula None

Unit per mill

Issue 11 (2015–05–30)


79




Feature ID

VS.DataTtiRatio.Mean

Multi-mode: None

Feature Name



LTE: None

Time Ratio for HSDPA Users Having Data in the Queue Buffer but Having No Data Transmission in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341693

VS.HSDPA.Ina ctiveDataTtiRat io.Mean

Number of TTIs in which at least one HSDPA user in a cell has TRB data to transmit in the queue buffer but there is no conventional TRB data transmission at the physical layer


U

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 Issue 11 (2015–05–30)


80



in the anchor carrier and the supplementary carrier separately. The following figure shows the flowchart where the counter is measured at points D, E and F: Figure 1-2

Issue 11 (2015–05–30)


81



Formula None

Unit per mill


Feature ID

VS.HSDPA.InactiveDataTti Ratio.Mean

Multi-mode: None

Feature Name



LTE: None

Average Time Ratio for HSDPA User Queues in the Scheduling Candidate Set but Having No Data Transmission Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341739

VS.HSDPA.Sc heInactiveData TtiRatio.Mean

Average ratio of the time when some HSDPA users are queued in the scheduling candidate set but do not transmit data


U

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 Issue 11 (2015–05–30)


82



DC-HSDPA users, the counter is measured in the anchor carrier and the supplementary carrier separately.The counter is measured at point E in the following figure: Figure 1-3

Formula None

Unit per mill

Issue 11 (2015–05–30)


83




Feature ID

VS.HSDPA.ScheInactiveDa taTtiRatio.Mean

Multi-mode: None

Feature Name



LTE: None

Number of TTIs in Which TRB Data Is to be Transmitted in the HSDPA User Queue in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331839

VS.HSDPA.Dat aTtiNum.TRB

Number of TTIs in which TRB data is to be transmitted in the HSDPA user queue in a cell


U

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:

Issue 11 (2015–05–30)


84



Figure 1-4

Formula None

Unit None


Feature ID

VS.HSDPA.DataTtiNum.T RB

Multi-mode: None

Feature Name


HSDPA Enhanced Package

LTE: None

Issue 11 (2015–05–30)


85



Number of TTIs for HSDPA Users in a Cell Having TRB Data to Transmit in the Queue Buffer but Having No Data Transmission at the Physical Layer Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331840

VS.HSDPA.Ina ctiveDataTtiNu m.TRB

Number of TTIs in which at least one HSDPA user in a cell has TRB data to transmit in the queue buffer but there is no conventional TRB data transmission at the physical layer .


U

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:

Issue 11 (2015–05–30)


86



Figure 1-5

Formula None

Unit None

Issue 11 (2015–05–30)


87




Feature ID

VS.HSDPA.InactiveDataTti Num.TRB

Multi-mode: None

Feature Name



LTE: None

Total number of user-level TTIs within which there is data to transmit in HSDPA user queue buffers Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331745

VS.HSDPA.Dat aTtiNum.User

Total number of user-level TTIs within which there is data to transmit in HSDPA user queue buffers


U

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.

Formula None

Unit None Issue 11 (2015–05–30)


88




Feature ID

VS.HSDPA.DataTtiNum.Us er

Multi-mode: None

Feature Name



LTE: None

Total number of user-level TTIs within which there is data to transmit in MCHSDPA/MC-HSDPA+MIMO user queue buffers Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332215

VS.DCHSDPA. DataTtiNum.Us er

Total number of user-level TTIs within which there is data to transmit in DCHSDPA/DCHSDPA +MIMO user queue buffers


U

50332173

VS.DBHSDPA. DataTtiNum.Us er

Total number of user-level TTIs within which there is data to transmit in DBHSDPA/DBHSDPA +MIMO user queue buffers


U

50332217

VS. 3CHSDPA.Dat aTtiNum.User

Total number of user-level TTIs within which there is data to transmit in 3CHSDPA/3CHSDPA +MIMO user queue buffers


U

Issue 11 (2015–05–30)


89



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332174

VS. 4CHSDPA.Dat aTtiNum.User

Total number of user-level TTIs within which there is data to transmit in 4CHSDPA/4CHSDPA +MIMO user queue buffers


U


Description

VS.DCHSDPA.DataTtiNum.User

This counter measures the number of TTIs within which there is data to transmit in DCHSDPA or DC-HSDPA+MIMO user queue buffers. This counter needs to be measured repeatedly if more than one DC-HSDPA or DC-HSDPA+MIMO user queue buffer has data to transmit within a TTI.

VS.DBHSDPA.DataTtiNum.User

This counter measures the number of TTIs within which there is data to transmit in DBHSDPA or DB-HSDPA+MIMO user queue buffers. This counter needs to be measured repeatedly if more than one DB-HSDPA or DB-HSDPA+MIMO user queue buffer has data to transmit within a TTI.

VS.3CHSDPA.DataTtiNum.User

This counter measures the number of TTIs within which there is data to transmit in 3CHSDPA or 3C-HSDPA+MIMO user queue buffers. This counter needs to be measured repeatedly if more than one 3C-HSDPA or 3C-HSDPA+MIMO user queue buffer has data to transmit within a TTI.

VS.4CHSDPA.DataTtiNum.User

This counter measures the number of TTIs within which there is data to transmit in 4CHSDPA or 4C-HSDPA+MIMO user queue buffers. This counter needs to be measured repeatedly if more than one 4C-HSDPA or 4C-HSDPA+MIMO user queue buffer has data to transmit within a TTI.

Issue 11 (2015–05–30)


90



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. This counter is measured only in the anchor carrier, not in the supplementary carrier.

Formula None

Unit None


Feature ID

VS.DCHSDPA.DataTtiNum .User

Multi-mode: None

Feature Name


DC-HSDPA

LTE: None VS.DBHSDPA.DataTtiNum .User


DB-HSDPA

LTE: None

Issue 11 (2015–05–30)


91



Counter Name

Feature ID

VS. 3CHSDPA.DataTtiNum.Use r

Multi-mode: None

Feature Name


3C-HSDPA

WRFD-150223

MC-HSDPA+MIMO

LTE: None VS. 4CHSDPA.DataTtiNum.Use r


4C-HSDPA

WRFD-150223

MC-HSDPA+MIMO

LTE: None

Time Ratio Used for HS-SCCH Channel Codes in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341694

VS.HSDPA. 2ScchCodeRati o

The time ratio of only using two HS-SCCH codes for cell


U

50341695


The time ratio of only using three HS-SCCH codes for cell


U

50341696


The time ratio of only using four HS-SCCH codes for cell


U

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 Issue 11 (2015–05–30)


92



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


Feature ID


Multi-mode: None

Feature Name



LTE: None VS.HSDPA. 3ScchCodeRatio



LTE: None VS.HSDPA. 4ScchCodeRatio



LTE: None

Available HS-PDSCH Codes in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341690

VS.PdschCode Avail.Mean

Average number of available HSPDSCH codes in a cell


U

Issue 11 (2015–05–30)


93



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341691

VS.PdschCode Avail.Max

Maximum number of available HSPDSCH codes in a cell


U

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


Feature ID

VS.PdschCodeAvail.Mean

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-010610 LTE: None VS.PdschCodeAvail.Max



Issue 11 (2015–05–30)



94



Used HS-PDSCH Codes in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341688

VS.PdschCode Used.Mean

Average number of used HS-PDSCH codes in a cell


U

50341689

VS.PdschCode Used.Max

Maximum number of used HS-PDSCH codes in a cell


U

50341692

VS.PdschCode Used.Min

Minimum number of used HS-PDSCH codes in a cell


U

Description The preceding counters indicate the average, maximum, and minimum number of used HSPDSCH 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

Issue 11 (2015–05–30)


95




Feature ID

VS.PdschCodeUsed.Mean

Multi-mode: None

Feature Name



LTE: None VS.PdschCodeUsed.Max



LTE: None VS.PdschCodeUsed.Min



LTE: None

Usage of HS-SCCH Code Resources in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341648

VS.ScchCodeU til.Mean

Average usage of HS-SCCH code resources in a cell


U

50341649

VS.ScchCodeU til.Max

Maximum usage of HSSCCH code resources in a cell


U

50341650

VS.ScchCodeU til.Min

Minimum usage of HS-SCCH code resources in a cell


U

Issue 11 (2015–05–30)


96



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. If the code usage is low, the code resources are excessive. Therefore, some of the code resources can be allocated to R99 services.

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


Feature ID

VS.ScchCodeUtil.Mean

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-01061001 WRFD-01061018 WRFD-01061005 WRFD-010631 LTE: None

15 Codes per Cell Time and HS-PDSCH Codes Multiplex HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation Dynamic Code Allocation Based on NodeB

Issue 11 (2015–05–30)


97



Counter Name

Feature ID

VS.ScchCodeUtil.Max

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-01061001 WRFD-01061018 WRFD-01061005

15 Codes per Cell Time and HS-PDSCH Codes Multiplex HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation


Dynamic Code Allocation Based on NodeB

VS.ScchCodeUtil.Min

Multi-mode: None GSM: None UMTS: WRFD-01061001 WRFD-01061018 WRFD-01061005




Usage of HS-SCCH Code Resources When at Least One HSDPA User Camps on the Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341654

VS.ScchCodeU til.Mean.User

Average usage of HS-SCCH code resources when HSDPA users camp on the cell


U

Issue 11 (2015–05–30)


98



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 HSSCCH 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


Feature ID

VS.ScchCodeUtil.Mean.Use r

Multi-mode: None

Feature Name


HSDPA Static Code Allocation and RNCControlled Dynamic Code Allocation Dynamic Code Allocation Based on NodeB 15 Codes per Cell Time and HS-PDSCH Codes Multiplex

Usage of HS-SCCH Code Resources When at Least One HSDPA User Has Data to Transmit in the Queue Buffer

Issue 11 (2015–05–30)


99



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341655

VS.ScchCodeU til.Mean.Data

Average usage of HS-SCCH code resources when at least one HSDPA user has data to transmit in the queue buffer


U

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

Issue 11 (2015–05–30)


100




Feature ID

VS.ScchCodeUtil.Mean.Data

Multi-mode: None

Feature Name



Usage of HS-PDSCH Code Resources in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341651

VS.PdschCode Util.Mean

Average usage of HS-PDSCH code resources in a cell


U

50341652

VS.PdschCode Util.Max

Maximum usage of HSPDSCH code resources in a cell


U

50341653

VS.PdschCode Util.Min

Minimum usage of HS-PDSCH code resources in a cell


U

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 Issue 11 (2015–05–30)


101



are required. If the code usage is low, the code resources are excessive. Therefore, some of the code resources can be allocated to R99 services.

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


Feature ID

VS.PdschCodeUtil.Mean

Multi-mode: None

Feature Name



VS.PdschCodeUtil.Max

Multi-mode: None GSM: None UMTS: WRFD-01061005 WRFD-010631 WRFD-01061001 WRFD-01061018 LTE: None


Issue 11 (2015–05–30)


102



Counter Name

Feature ID

VS.PdschCodeUtil.Min

Multi-mode: None

Feature Name



Usage of HS-PDSCH Code Resources When at Least One HSDPA User Camps on the cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341656

VS.PdschCode Util.Mean.User

Average usage of HS-PDSCH code resources when HSDPA users camp on the cell


U

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.



103



Unit per mill


Feature ID

VS.PdschCodeUtil.Mean.Us er

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-01061001 WRFD-01061018 WRFD-01061005




Usage of HS-PDSCH Code Resources When at Least One HSDPA User Has Data to Transmit in the Queue Buffer Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341657

VS.PdschCode Util.Mean.Data

Average usage of HS-PDSCH code resources when at least one HSDPA user has data to transmit in the queue buffer


U

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 Issue 11 (2015–05–30)


104



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


Feature ID

VS.PdschCodeUtil.Mean.Da ta

Multi-mode: None

Feature Name



Transmit Power over the HS-SCCH in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341675

VS.ScchPwrRat io.Mean

Average transmit power over the HSSCCH in a cell


U

50341676

VS.ScchPwrRat io.Max

Maximum transmit power over the HSSCCH in a cell


U

Issue 11 (2015–05–30)


105



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341677

VS.ScchPwrRat io.Min

Minimum transmit power over the HSSCCH in a cell


U

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


Feature ID

VS.ScchPwrRatio.Mean

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-01061004 WRFD-01061019 LTE: None

Issue 11 (2015–05–30)


HSDPA Power Control HSDPA Dynamic Power Allocation

106



Counter Name

Feature ID

VS.ScchPwrRatio.Max

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-01061004 WRFD-01061019 LTE: None VS.ScchPwrRatio.Min




Transmit Power over the HS-SCCH When at Least One HSDPA User Camps on the Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341681

VS.ScchPwrRat io.User

Average transmit power over the HSSCCH when HSDPA users camp on the cell


U

Description The preceding counter indicates the average transmit power over the HS-SCCH when at least one HSDPA user camps on the cell. The value is expressed as the ratio of the transmit power to the maximum cell transmit power. Disuse Statement: The counter 50341681 VS.ScchPwrRatio.User will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points During the measurement period, the NodeB calculates the total ratio of the transmit power over the HS-SCCHs to the maximum cell transmit power in all TTIs when at least one HSDPA user Issue 11 (2015–05–30)


107



camps on the cell. Assume that this value is A and the number of TTIs when at least one HSDPA user camps on the cell is B. Then, VS.ScchPwrRatio.User = A/B.

Formula 1000*[VS.ScchPwrRatio.Mean]/[VS.UserTtiRatio.Mean]

Unit per mill


Feature ID

VS.ScchPwrRatio.User

Multi-mode: None

Feature Name



Transmit Power over the HS-SCCH When at Least One HSDPA User Has Data to Transmit in the Queue Buffer Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341683

VS.ScchPwrRat io.UserData

Average transmit power over the HSSCCH when at least one HSDPA user has data to transmit in the queue buffer


U

Description The preceding counter indicates the average transmit power over the HS-SCCH when at least one HSDPA user has data to transmit in the queue buffer within a measurement period. The value is expressed as the ratio of the transmit power to the maximum cell transmit power. Disuse Statement: Issue 11 (2015–05–30)


108



The counter 50341683 VS.ScchPwrRatio.UserData will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Within the measurement period, the NodeB calculates the total ratio of the transmit power over the HS-SCCHs in all TTIs when at least one HSDPA user has data to transmit in the queue buffer. Assume that this value is A and the number of TTIs when at least one HSDPA user has data to transmit in the queue buffer is B. Then, VS.ScchPwrRatio.UserData = A/B.

Formula 1000*[VS.ScchPwrRatio.Mean]/[VS.DataTtiRatio.Mean]

Unit per mill


Feature ID

VS.ScchPwrRatio.UserData

Multi-mode: None

Feature Name



Transmit Power over the HS-PDSCH in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341678

VS.PdschPwrR atio.Mean

Average transmit power over the HSPDSCH in a cell


U

50341679

VS.PdschPwrR atio.Max

Maximum transmit power over the HSPDSCH in a cell


U

Issue 11 (2015–05–30)


109



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341680

VS.PdschPwrR atio.Min

Minimum transmit power over the HSPDSCH in a cell


U

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


Feature ID

VS.PdschPwrRatio.Mean

Multi-mode: None

Feature Name


Issue 11 (2015–05–30)



110



Counter Name

Feature ID

VS.PdschPwrRatio.Max

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-01061004 WRFD-01061019 LTE: None VS.PdschPwrRatio.Min




Transmit Power over the HS-PDSCH When at Least One HSDPA User Camps on the Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341682

VS.PdschPwrR atio.User

Average transmit power over the HSPDSCH when HSDPA users camp on the cell


U

Description The preceding counter indicates the average transmit power over the HS-PDSCH when at least one HSDPA user camps on the cell within a measurement period. The value is expressed as the ratio of the transmit power to the maximum cell transmit power. Disuse Statement: The counter 50341682 VS.PdschPwrRatio.User will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Within the measurement period, the NodeB calculates the total ratio of the transmit power over the HS-PDSCHs to the maximum cell transmit power in all TTIs when at least one HSDPA user Issue 11 (2015–05–30)


111



camps on the cell. Assume that this value is A and the number of TTIs when at least one HSDPA user camps on the cell is B. Then, VS.PdschPwrRatio.User = A/B.

Formula 1000*[VS.PdschPwrRatio.Mean]/[VS.UserTtiRatio.Mean]

Unit per mill


Feature ID

VS.PdschPwrRatio.User

Multi-mode: None

Feature Name



Transmit Power over the HS-PDSCH When at Least One HSDPA User Has Data to Transmit in the Queue Buffer Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341684

VS.PdschPwrR atio.Data

Average transmit power over the HSPDSCH when at least one HSDPA user has data to transmit in the queue buffer


U

Description The preceding counter indicates the average transmit power over the HS-PDSCH when at least one HSDPA user has data to transmit in the queue buffer within a measurement period. The value is expressed as the ratio of the transmit power to the maximum cell transmit power. Disuse Statement: Issue 11 (2015–05–30)


112



The counter 50341684 VS.PdschPwrRatio.Data will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Within the measurement period, the NodeB calculates the total ratio of the transmit power over the HS-PDSCHs to the maximum cell transmit power in all TTIs when at least one HSDPA user has data to transmit in the queue buffer. Assume that this value is A and the number of TTIs when at least one HSDPA user has data to transmit in the queue buffer is B. Then, VS.PdschPwrRatio.Data = A/B.

Formula 1000*[VS.PdschPwrRatio.Mean]/[VS.DataTtiRatio.Mean]

Unit per mill


Feature ID

VS.PdschPwrRatio.Data

Multi-mode: None

Feature Name



Power Usage of HSDPA Free Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341697

VS.HSDPAPwr Ratio.Mean.Fre eUser

Average usage of free users Hsdpa Power


U

50341698

VS.HSDPAPwr Ratio.Max.Free User

Maximum usage of free users Hsdpa Power


U

Issue 11 (2015–05–30)


113



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


Feature ID

VS.HSDPAPwrRatio.Mean. FreeUser


VS.HSDPAPwrRatio.Max.F reeUser

Feature Name




Available HSDPA Power in a Cell

Issue 11 (2015–05–30)


114



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341703

VS.AvaiHSDP APwrRatio.Mea n

Mean ratio of availble HSDPA Power Ratio


U

50341704

VS.AvaiHSDP APwrRatio.Ma x

Maximum ratio of availble HSDPA Power Ratio


U

50341705

VS.AvaiHSDP APwrRatio.Min

Minimum ratio of availble HSDPA Power Ratio


U

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

Issue 11 (2015–05–30)


115




Feature ID

VS.AvaiHSDPAPwrRatio. Mean

Multi-mode: None

Feature Name



LTE: None VS.AvaiHSDPAPwrRatio. Max



LTE: None VS.AvaiHSDPAPwrRatio. Min



LTE: None

Average HSDPA Power Ratio for Each Operator in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341706

VS.HSDPAPwr Ratio.PLMN0



U

50341707




U

50341708




U

50341709




U

Issue 11 (2015–05–30)


116



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


Feature ID

VS.HSDPAPwrRatio.PLM N0



GSM: None LTE: None

GSM: None LTE: None



Issue 11 (2015–05–30)


Multi-mode: None UMTS: WRFD-010610





Feature Name



117



Average HSDPA Power for Each Operator in a Cell in an MOCN Network Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341710

VS.HSDPAPwr Ratio.SharedOp erator0



U

50341711




U

50341712




U

50341713




U

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.



118



Unit per mill


Feature ID

VS.HSDPAPwrRatio.SharedOperator0



GSM: None LTE: None

MOCN Introduction Package






Feature Name




Average permillage of transmit power for HSDPA users in each resource group to the maximum cell transmit power

Issue 11 (2015–05–30)


119



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341714

VS.HSDPAPwr Ratio.Mean.Res G0



U

50341715




U

50341716




U

50341717




U

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 Issue 11 (2015–05–30)


120



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


Feature ID

VS.HSDPAPwrRatio.Mean. ResG0



GSM: None LTE: None

Differentiated Service Based on Resource Reservation






Feature Name




Number of HSDPA RABs in a Cell

Issue 11 (2015–05–30)


121



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341660

VS.RabNum.M ean

Average number of HSDPA RABs in a cell


U

50341661

VS.RabNum.M ax

Maximum number of HSDPA RABs in a cell


U

50341662

VS.RabNum.M in

Minimum number of HSDPA RABs in a cell


U

Description The preceding counters indicate the average, maximum, and minimum number of HSDPA radio access bearers (RABs) in a cell within each TTI during a measurement period. Disuse Statement: The counter 50341660 VS.RabNum.Mean will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended. The counter 50341661 VS.RabNum.Max will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended. The counter 50341662 VS.RabNum.Min will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points The NodeB calculates the total number of RABs for all HSDPA users in all TTIs during a measurement period. Assume that this number is A and the number of TTIs within the measurement period is B. Then, VS.RabNum.Mean = A/B. The NodeB calculates VS.RabNum.Mean every 5s and then takes the maximum value within the measurement period as VS.RabNum.Max and the minimum value within the measurement period as VS.RabNum.Min. The RAB for a DC-HSDPA user is regarded as the RAB for an HSDPA user in each anchor carrier and supplementary carrier. For the RABs of DC-HSDPA users, the counter is measured in the anchor carrier and the supplementary carrier separately.



122



Unit None


Feature ID

VS.RabNum.Mean

Multi-mode: None

Feature Name



LTE: None VS.RabNum.Max



LTE: None VS.RabNum.Min



LTE: None

Number of HSDPA RABs When at Least One HSDPA User Camps on the Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341666

VS.RabNumAv e.User

Average number of HSDPA RABs when HSDPA users camp on the cell


U

Description The preceding counter indicates the average number of HSDPA RABs when at least one HSDPA user camps on the cell in each TTI during a measurement period. Disuse Statement: Issue 11 (2015–05–30)


123



The counter 50341666 VS.RabNumAve.User will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Assume that the total number of HSDPA RABs in all TTIs within the measurement period is A, and the number of TTIs when at least one HSDPA user camps on the cell is B. Then, VS.RabNumAve.User = A/B. The RAB for a DC-HSDPA user is regarded as the RAB for an HSDPA user in each anchor carrier and supplementary carrier. For the RABs of DC-HSDPA users, the counter is measured in the anchor carrier and the supplementary carrier separately.

Formula 1000*[VS.RabNum.Mean]/[VS.UserTtiRatio.Mean]

Unit None


Feature ID

VS.RabNumAve.User

Multi-mode: None

Feature Name



LTE: None

Number of RABs with HSDPA Data to Be Transmitted in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341663

VS.DataRabNu m.Mean

Average number of HSDPA RABs have data to transmit in the queue buffer in a cell


U

Issue 11 (2015–05–30)


124



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341664

VS.DataRabNu m.Max

Maximum number of HSDPA RABs have data to transmit in the queue buffer in a cell


U

50341665

VS.DataRabNu m.Min

Minimum number of HSDPA RABs have data to transmit in the queue buffer in a cell


U

Description The preceding counters indicate the average, maximum, and minimum number of RABs with HSDPA data to be transmitted in the queue buffer of a cell within each TTI during a measurement period. Disuse Statement: The counter 50341663 VS.DataRabNum.Mean will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended. The counter 50341664 VS.DataRabNum.Max will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended. The counter 50341665 VS.DataRabNum.Min will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Within the measurement period, the NodeB calculates the total number of RABs with HSDPA data to be transmitted in the queue buffer in all TTIs. Assume that this value is A and the number of TTIs within the measurement period is B. Then, VS.DataRabNum.Mean = A/B. The NodeB calculates VS.DataRabNum.Mean every 5s and then takes the maximum value within the measurement period as VS.DataRabNum.Max and the minimum value within the measurement period as VS.DataRabNum.Min. The RAB for a DC-HSDPA user is regarded as the RAB for an HSDPA user in each anchor carrier and supplementary carrier. For the RABs of DC-HSDPA users, the counter is measured in the anchor carrier and the supplementary carrier separately.



125



Unit None


Feature ID

VS.DataRabNum.Mean

Multi-mode: None

Feature Name



LTE: None VS.DataRabNum.Max



LTE: None VS.DataRabNum.Min



LTE: None

Number of RABs with HSDPA Data to Be Transmitted in the Queue Buffer When at Least One HSDPA User Has Data to Transmit in the Queue Buffer in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341667

VS.RabNumAv e.UserData

Average number of HSDPA RABs have data to transmit in the queue buffer when at least one HSDPA user has data to transmit in the queue buffer in a cell


U

Issue 11 (2015–05–30)


126



Description The preceding counter indicates the average number of RABs with HSDPA data to be transmitted in the queue buffer when at least one HSDPA user has data to transmit in the queue buffer in a cell. Disuse Statement: The counter 50341667 VS.RabNumAve.UserData will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Within the measurement period, the NodeB calculates the total number of RABs with HSDPA data to be transmitted in the queue buffer in all TTIs. Assume that this value is A and the number of TTIs when at least one HSDPA user has data to transmit in the queue buffer is B. Then, VS.RabNumAve.UserData = A/B. The RAB for a DC-HSDPA user is regarded as the RAB for an HSDPA user in each anchor carrier and supplementary carrier. For the RABs of DC-HSDPA users, the counter is measured in the anchor carrier and the supplementary carrier separately.

Formula 1000*[VS.DataRabNum.Mean]/[VS.DataTtiRatio.Mean]

Unit None


Feature ID

VS.RabNumAve.UserData

Multi-mode: None

Feature Name



LTE: None

HSDPA Throughput of MAC-d PDUs in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341668

VS.DataOutput. Mean

Average throughput of MAC-d PDUs in a cell


U

Issue 11 (2015–05–30)


127



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341669

VS.DataOutput. Max

Maximum throughput of MAC-d PDUs in a cell


U

50341670

VS.DataOutput. Min

Minimum throughput of MAC-d PDUs in a cell


U

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 total length of 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


Feature ID

VS.DataOutput.Mean

Multi-mode: None

Feature Name



LTE: None

Issue 11 (2015–05–30)


128



Counter Name

Feature ID

VS.DataOutput.Max

Multi-mode: None

Feature Name



LTE: None VS.DataOutput.Min



LTE: None

HSDPA Cell Throughput of MAC-d PDUs When the Cell Serves HSDPA Users Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341671

VS.DataOutput. User

Average cell throughput when HSDPA users camp on the cell


U

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 Issue 11 (2015–05–30)


129




Feature ID

VS.DataOutput.User

Multi-mode: None

Feature Name



LTE: None

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 Name

Counter Description

Network Element

Applicable Mode

50341672

VS.DataOutput. UserData

Average cell throughput when at least one HSDPA user has data to transmit in the queue buffer


U

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]



130




Feature ID

VS.DataOutput.UserData

Multi-mode: None

Feature Name



LTE: None

Throughput of MAC-d PDUs for Each RAB in a Cell When the Cell Serves HSDPA Users Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341673

VS.DataOutput. Rab

Average throughput of each RAB when HSDPA users camp on the cell


U

Description The counter indicates the average throughput of MAC-d PDUs for each RAB in a cell when the cell serves HSDPA users. Disuse Statement: The counter 50341673 VS.DataOutput.Rab will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Within a measurement period, the average throughput of MAC-d PDUs in a cell when the cell serves HSDPA users is A, and the average number of HSDPA RABs when the cell serves HSDPA users is B. A divided by B is used as the value of the VS.DataOutput.Rab counter. For a multicarrier user, the corresponding counter is measured in the anchor and supplementary carriers separately.

Formula [VS.DataOutput.User]/[VS.RabNumAve.User]



131




Feature ID

VS.DataOutput.Rab

Multi-mode: None

Feature Name



LTE: None

Throughput of MAC-d PDUs for Each RAB in a Cell When at Least One HSDPA User Has Data to Transmit in the Queue Buffer Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341674

VS.DataOutput. RabData

Average throughput of each RAB when at least one HSDPA user has data to transmit in the queue buffer


U

Description The counter indicates the average throughput of MAC-d PDUs for each RAB in a cell when at least one HSDPA user has data to transmit in the queue buffer. Disuse Statement: The counter 50341674 VS.DataOutput.RabData will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Within a measurement period, the average throughput of MAC-d PDUs in a cell when at least one HSDPA user has data to transmit in the queue buffer is A, and the average number of HSDPA RABs when at least one HSDPA user has data to transmit in the queue buffer is B. A divided by B is used as the value of the VS.DataOutput.RabData counter. For a multicarrier user, the corresponding counter is measured in the anchor and supplementary carriers separately.

Formula [VS.DataOutput.UserData]/[VS.RabNumAve.UserData] Issue 11 (2015–05–30)


132



Unit bit/s


Feature ID

VS.DataOutput.RabData

Multi-mode: None

Feature Name



LTE: None

Throughput of MAC-d PDUs of HSDPA Free Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341699

VS.DataOutput. Mean.FreeUser

Average throughput of MAC-d PDUs of HSDPA free users


U

50341700

VS.DataOutput. Max.FreeUser

Maximum throughput of MAC-d PDUs of HSDPA free users


U

50341701

VS.DataOutput. Min.FreeUser

Minimum throughput of MAC-d PDUs of HSDPA free users


U

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 Issue 11 (2015–05–30)


133



accumulated traffic volume is A and the total length of 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


Feature ID

VS.DataOutput.Mean.FreeUser


VS.DataOutput.Max.FreeUser



VS.DataOutput.Min.FreeUser

Feature Name




HS-DSCH TRB Traffic Volume of HSDPA Users in a Cell

Issue 11 (2015–05–30)


134



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331838

VS.HSDPA.Dat aOutput.TRB

HSDSCH TRB traffic volume in a cell


U

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


Feature ID

VS.HSDPA.DataOutput.TR B

Multi-mode: None

Feature Name



LTE: None

Traffic volume of the MAC-hs/MAC-ehs PDUs successfully received in a cell

Issue 11 (2015–05–30)


135



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331746

VS.HSDPA.Dat aOutput.Traffic

Traffic volume of the MAC-hs/ MAC-ehs PDUs successfully received in a cell


U

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 DCHSDPA, DB-HSDPA, 4C-HSDPA, or 3C-HSDPA users, this counter is measured in the anchor carrier and supplementary carrier separately.

Formula None

Unit bit


Feature ID

VS.HSDPA.DataOutput.Tra ffic

Multi-mode: None

Feature Name



LTE: None

MAC-ehs traffic volume of MC-HSDPA/MC-HSDPA+MIMO users

Issue 11 (2015–05–30)


136



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332170

VS.DataOutput. DCHSDPA.Tra ffic

MAC-ehs traffic volume of DC-HSDPA/ DC-HSDPA +MIMO users


U

50332168

VS.DataOutput. DBHSDPA.Tra ffic

MAC-ehs traffic volume of DB-HSDPA/ DB-HSDPA +MIMO users


U

50332216

VS.DataOutput. 3CHSDPA.Traf fic

MAC-ehs traffic volume of 3C-HSDPA/ 3C-HSDPA +MIMO users


U

50332169

VS.DataOutput. 4CHSDPA.Traf fic

MAC-ehs traffic volume of 4C-HSDPA/ 4C-HSDPA +MIMO users


U


Description

VS.DataOutput.DCHSDPA.Traffic

This counter measures the MAC-ehs traffic volume of DC-HSDPA/DC-HSDPA+MIMO users.

VS.DataOutput.DBHSDPA.Traffic

This counter measures the MAC-ehs traffic volume of DB-HSDPA/DB-HSDPA+MIMO users.

VS.DataOutput.3CHSDPA.Traffic

This counter measures the MAC-ehs traffic volume of 3C-HSDPA/3C-HSDPA+MIMO users.

VS.DataOutput.4CHSDPA.Traffic

This counter measures the MAC-ehs traffic volume of 4C-HSDPA/4C-HSDPA+MIMO users.

Issue 11 (2015–05–30)


137



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. The traffic volume of MAC-ehs PDUs received from DB-HSDPA/DB-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.DBHSDPA.Traffic. The traffic volume of MAC-ehs PDUs received from 3C-HSDPA/3C-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.3CHSDPA.Traffic. The traffic volume of MAC-ehs PDUs received from 4C-HSDPA/4C-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.4CHSDPA.Traffic.

Formula None

Unit kbit


Feature ID

VS.DataOutput.DCHSDPA. Traffic


VS.DataOutput.DBHSDPA. Traffic

Feature Name

Flexible Dual Carrier HSDPA DC-HSDPA+MIMO


DB-HSDPA

LTE: None

Issue 11 (2015–05–30)


138



Counter Name

Feature ID


Multi-mode: None

Feature Name


3C-HSDPA

WRFD-150223

MC-HSDPA+MIMO

LTE: None VS.DataOutput. 4CHSDPA.Traffic


4C-HSDPA

WRFD-150223

MC-HSDPA+MIMO

LTE: None

Ratio of HSDPA User Data Discarded upon Timeout in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341685

VS.DataDiscard Ratio.Mean

Average ratio of discarded HSDPA data due to timer expiry


U

50341686

VS.DataDiscard Ratio.Max

Maximum ratio of discarded HSDPA data due to timer expiry


U

50341687

VS.DataDiscard Ratio.Min

Minimum ratio of discarded HSDPA data due to timer expiry


U

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.

Issue 11 (2015–05–30)


139



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


Feature ID

VS.DataDiscardRatio.Mean

Multi-mode: None

Feature Name


VS.DataDiscardRatio.Max



VS.DataDiscardRatio.Min



Issue 11 (2015–05–30)



140



Ratio of the Actual Transmit Power over the SCPICH to the SCPICH Power Configured on the RNC Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331713

VS.SCPICH.Av gPowerRate

Ratio of the actual transmit power of the SCPICH to the power of the SCPICH configured by the RNC


U

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 SCPICH to the SCPICH power configured on the RNC every 5s. The value of this counter is the sum of these sampling results divided by the number of samplings at the end of a measurement period.

Formula None

Unit per mill

Issue 11 (2015–05–30)


141




Feature ID

VS.SCPICH.AvgPowerRate

Multi-mode: None

Feature Name


2*2 MIMO

LTE: None

Power-enabled Duration of the SCPICH in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331714

VS.SCPICH.P wrOn.Duration

Power-enabled duration of the SCPICH in a cell


U

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

Issue 11 (2015–05–30)


142




Feature ID

VS.SCPICH.PwrOn.Duration

Multi-mode: None

Feature Name


2*2 MIMO

LTE: None

Time Ratio of Existent Deactivated DC Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341702

VS.HSDPA.DC Cfg.SupCarrier Deact.TimeRati o

The Ratio Of Dc Deact


U

Description The preceding counter indicates the ratio of the traffic-based deactivation time of the secondarycarrier 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 secondarycarrier 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

Issue 11 (2015–05–30)


143




Feature ID

VS.HSDPA.DCCfg.SupCarr ierDeact.TimeRatio

Multi-mode: None

Feature Name


DB-HSDPA

WRFD-010713

Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier


DC-HSDPA+MIMO

Maximum DPCH power restriction algorithm validity probability Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341740

VS.HSDPA.Dp chMaxPwrRestr .ActRatio

Maximum DPCH power restriction algorithm validity probability


U

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.



144



Unit per mill


Feature ID

Feature Name

VS.HSDPA.DpchMaxPwrR estr.ActRatio


DPCH Maximum Power Restriction

1.1.2 Cell Traffic Measurement (TRAFFIC.LOCELL) 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 Description

Original Release

50332548

VS.ULCE.Mean.De dicated

Average Dedicated Uplink CE


50332549

VS.DLCE.Mean.De dicated

Average Dedicated Downlink CE


50332550

VS.ULCE.Mean.Sh ared

Average Shared Uplink CE


50332554

VS.DLCE.Mean.Sh ared

Average Shared Downlink CE


Issue 11 (2015–05–30)


145



Counter ID

Counter Name

Counter Description

Original Release

50342548

VS.ULCE.Max.De dicated

Maximum Dedicated Uplink CE


50342549

VS.DLCE.Max.De dicated

Maximum Dedicated Downlink CE


50342550

VS.ULCE.Max.Sha red

Maximum Shared Uplink CE


50342554

VS.DLCE.Max.Sha red

Maximum Shared Downlink CE


50342612

VS.ULCoMP.ULC E.Mean.Shared

Average Number of UL CEs in a Shared Group Consumed by UL Coordinating Links in a Cell


50342613

VS.ULCoMP.ULC E.Max.Shared

Maximum Number of UL CEs in a Shared Group Consumed by UL Coordinating Links in a Cell


50342615

VS.ULCoMP.ULC E.Mean.Dedicated

Average Number of UL CEs in a Dedicated Group Consumed by UL Coordinating Links in a Cell


50342616

VS.ULCoMP.ULC E.Max.Dedicated

Maximum Number of UL CEs in a Dedicated Group Consumed by UL Coordinating Links in a Cell


Issue 11 (2015–05–30)


146



Counter Relationship None

Number of Dedicated Uplink CEs Consumed in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332548

VS.ULCE.Mea n.Dedicated

Average Dedicated Uplink CE


U

50342548

VS.ULCE.Max. Dedicated

Maximum Dedicated Uplink CE


U

Description After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) are introduced, the number of consumed uplink CEs in license groups includes the number of uplink CEs consumed by DCH users and HSUPA users and the number of CEs consumed by coordinating links for UL CoMP (joint reception) users in the local license group. 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. The following table describes the meanings of each counter: Counter Name

Description

VS.ULCE.Mean.Dedicated

This counter measures the average number of dedicated uplink CEs consumed in a cell within a measurement period. This counter is only used for operators with RAN sharing.

VS.ULCE.Max.Dedicated

This counter measures the maximum number of dedicated uplink CEs consumed in a cell within a measurement period. This counter is only used for operators with RAN sharing.

Issue 11 (2015–05–30)


147



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


Feature ID

VS.ULCE.Mean.Dedicated

Multi-mode: None

Feature Name


RAN Sharing Introduction Package

LTE: None VS.ULCE.Max.Dedicated



LTE: None

Number of Dedicated Downlink CEs Consumed in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332549

VS.DLCE.Mea n.Dedicated

Average Dedicated Downlink CE


U

50342549

VS.DLCE.Max. Dedicated

Maximum Dedicated Downlink CE


U

Issue 11 (2015–05–30)


148




Description

VS.DLCE.Mean.Dedicated

This counter measures the average number of dedicated downlink CEs consumed in a cell within a measurement period. This counter is only used for operators with RAN sharing.

VS.DLCE.Max.Dedicated

This counter measures the maximum number of dedicated downlink CEs consumed in a cell within a measurement period. This counter is only used for operators with RAN sharing.

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


Feature ID

VS.DLCE.Mean.Dedicated

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-021304 LTE: None VS.DLCE.Max.Dedicated



Issue 11 (2015–05–30)



149



Number of Shared Uplink CEs Consumed in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332550

VS.ULCE.Mea n.Shared

Average Shared Uplink CE


U

50342550

VS.ULCE.Max. Shared

Maximum Shared Uplink CE


U

Description After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) are introduced, the number of consumed uplink CEs in license groups includes the number of uplink CEs consumed by DCH users and HSUPA users and the number of CEs consumed by coordinating links for UL CoMP (joint reception) users in the local license group. 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. The following table describes the meanings of each counter: Counter Name

Description

VS.ULCE.Mean.Shared

This counter measures the average number of shared uplink CEs consumed in a cell within a measurement period.

VS.ULCE.Max.Shared

This counter measures the maximum number of shared uplink CEs consumed in a cell within a measurement period.

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.



150



Unit None


Feature ID

Feature Name

VS.ULCE.Mean.Shared



LTE: None VS.ULCE.Max.Shared



LTE: None

Number of Downlink Shared CEs Consumed in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332554

VS.DLCE.Mea n.Shared

Average Shared Downlink CE


U

50342554

VS.DLCE.Max. Shared

Maximum Shared Downlink CE


U


Description

VS.DLCE.Mean.Shared

This counter measures the average number of shared downlink CEs consumed in a cell within a measurement period.

Issue 11 (2015–05–30)


151



Counter Name

Description

VS.DLCE.Max.Shared

This counter measures the maximum number of shared downlink CEs consumed in a cell within a measurement period.

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


Feature ID

VS.DLCE.Mean.Shared

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-021304 LTE: None VS.DLCE.Max.Shared




Number of UL CEs in a Shared Group Consumed by UL Coordinating Links in a Cell

Issue 11 (2015–05–30)


152



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342612

VS.ULCoMP.U LCE.Mean.Shar ed

Average Number of UL CEs in a Shared Group Consumed by UL Coordinating Links in a Cell


U

50342613

VS.ULCoMP.U LCE.Max.Share d

Maximum Number of UL CEs in a Shared Group Consumed by UL Coordinating Links in a Cell


U

Description This counter measures the average and maximum number of UL CEs in a shared group consumed by UL coordinating links in a cell. The measurement results show how the CEs are additionally consumed after the UL CoMP feature has been enabled. The consumption can be assessed using the ratio of UL CEs in a shared group consumed by UL coordinating links in a cell to those of other links. 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.

Measurement Points The number of UL CEs in a shared group consumed by UL 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 UL 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 UL coordinating links in a cell.



153



Unit None


Feature ID

VS.ULCoMP.ULCE.Mean. Shared


VS.ULCoMP.ULCE.Max.S hared

Feature Name

Uplink CoMP (Joint Reception) HetNet Uplink CoMP (Joint Reception) Uplink CoMP (Joint Reception) Based on Coordinated BBU



Number of UL CEs in a Dedicated Group Consumed by UL Coordinating Links in a Cell

Issue 11 (2015–05–30)


154



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342615

VS.ULCoMP.U LCE.Mean.Ded icated

Average Number of UL CEs in a Dedicated Group Consumed by UL Coordinating Links in a Cell


U

50342616

VS.ULCoMP.U LCE.Max.Dedi cated

Maximum Number of UL CEs in a Dedicated Group Consumed by UL Coordinating Links in a Cell


U

Description This counter measures the average and maximum number of UL CEs in a dedicated group consumed by UL coordinating links in a cell. The measurement results show how the CEs are additionally consumed after the UL CoMP feature has been enabled. The consumption can be assessed using the ratio of UL CEs in a dedicated group consumed by UL coordinating links in a cell to those of other links. Remarks: After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) are introduced, the number of consumed uplink CEs in license groups includes the number of uplink CEs consumed by DCH users and HSUPA users and the number of CEs consumed by coordinating links for UL CoMP (joint reception) users in the local license group. 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.

Measurement Points The number of dedicated UL CEs in a dedicated group consumed by UL 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 UL coordinating links is obtained by dividing the accumulated value within the measurement period by the number of samples. The maximum value within the Issue 11 (2015–05–30)


155



measurement period is the maximum number of UL CEs in a dedicated group consumed by UL coordinating links.

Formula None

Unit None


Feature ID

VS.ULCoMP.ULCE.Mean. Dedicated


VS.ULCoMP.ULCE.Max.D edicated

Feature Name




1.1.3 HSUPA Measurement (HSUPA.LOCELL) Overview The function subset consists of HSUPA-related counters to indicate the HSUPA cell status and performance. Unless otherwise stated, HSUPA users are those in the CELL_DCH state.

Issue 11 (2015–05–30)


156



Counters Counter ID

Counter Name

Counter Description

Original Release

50331850

VS.HSUPA.LoadOutput.0

Number of Cell Ul Load Between 0db to 0.5db


50331851


Number of Cell Ul Load Between 0.5db to 1db


50331852


Number of Cell Ul Load Between 1.0db to 1.5db


50331853




50331854




50331855




50331856




50331857




Issue 11 (2015–05–30)


157



Counter ID

Counter Name

Counter Description

Original Release

50331858


Number of Cell Ul Load Between 4db to 5db


50331859




50331860




50331861




50331862




50331863




50331864




50331865




Issue 11 (2015–05–30)


158



Counter ID

Counter Name

Counter Description

Original Release

50331866




50331867




50331868




50331869




50331870




50331871




50331872




50331873




Issue 11 (2015–05–30)


159



Counter ID

Counter Name

Counter Description

Original Release

50331874




50331875


Number of Cell Ul Load above 30db


50331876

VS.HSUPA.OverLoadNum

Number of times the uplink is overloaded in a cell


50341864

VS.HSUPA.AGCH CodeCollision.Mea n

Average ratio of EAGCH code collisions in a cell


50331904

VS.HSUPA.AGCH CodeCollision.Max

Maximum ratio of EAGCH code collisions in a cell


50341865

VS.HSUPA.AGCH CodeUtil.Mean

average number of AGCH usage ratio


50331903

VS.HSUPA.AGCH CodeUtil.Max

Max value of AGCH usage ratio


50341850

VS.HSUPA.DataUs erNum.Mean

Average number of HSUPA users that transmit data in a cell


50341851

VS.HSUPA.DataUs erNum.Max

Maximum number of HSUPA users that transmit data in a cell


Issue 11 (2015–05–30)


160



Counter ID

Counter Name

Counter Description

Original Release

50341852

VS.HSUPA.Schedu leUserNum.Mean

Average number of scheduled HSUPA users in a cell


50341853

VS.HSUPA.Schedu leUserNum.Max

Maximum number of scheduled HSUPA users in a cell


50341854

VS.HSUPA.MaxP wrLmtUserRatio

Ratio of the number of HSUPA users with limited UPH to the total number of HSUPA users in a cell


50341855

VS.HSUPA.LeftPwrLmtUserRatio

Ratio of the number of HSUPA users with limited uplink load to the total number of HSUPA users in a cell


50331877

VS.HSUPA.UnHap pyUserNum

Number of Unhappy HSUPA users in a cell


50341849

VS.HSUPA.UnHap pyUserNumRatio

Ratio of the number of Unhappy HSUPA users to the total number of HSUPA users in a cell


50341892

VS.HSUPA.LowRa teTTI2msUserNum ber

Average number of 2 ms TTI HSUPA users at a rate lower than or equal to 23.25 kbit/s in a cell


50341870

VS.HSUPA.TTI2m sUserNumber.0

Average number of 2 ms TTI HSUPA users at a rate of below 150 kbit/s in a cell


Issue 11 (2015–05–30)


161



Counter ID

Counter Name

Counter Description

Original Release

50341871


Average number of 2 ms TTI HSUPA users at a rate in the range of [150 kbit/s, 700 kbit/s) in a cell


50341872




50341873




50341874




50341875




50341884

VS.HSUPA.TTI10 msUserNumber.0

Average number of 10 ms TTI HSUPA users at a rate of interval 0 in a cell


50341885




50341886




50341887




Issue 11 (2015–05–30)


162



Counter ID

Counter Name

Counter Description

Original Release

50341888




50341889




50341890




50341891




50341868

VS.HSUPA.TDMU serNum.Mean

Average number of valid time-division scheduling users in a cell


50331878

VS.HSUPA.UserTtiNum

Number of TTIs in which at least one HSUPA user exists in a cell


50331879

VS.HSUPA.DataTtiNum

Number of TTIs in which HSUPA users transmit data in a cell


50331908

VS.HSUPA.DataTt iNum.TRB

Number of TTIs in which HSUPA users transmit TRB data in a cell


50331961

VS.HSUPA.DataUs erSumNum.ROTM or3

Number of HSUPA users with data transmission under the 3 dB or above uplink Uu load in a cell


Issue 11 (2015–05–30)


163



Counter ID

Counter Name

Counter Description

Original Release

50331962




50331963




50331964




50331965




50331966




50331967




50331925

VS.HSUPA.DataTt iNum.ROTMor3

Number of TTIs in which HSUPA users have data to transmit under the 3 dB or above uplink Uu load in a cell


Issue 11 (2015–05–30)


164



Counter ID

Counter Name

Counter Description

Original Release

50331926




50331927




50331928




50331929




50331930




50331931




50331885

VS.HSUPA.ACKT otal

Number of transmitted ACKs


Issue 11 (2015–05–30)


165



Counter ID

Counter Name

Counter Description

Original Release

50331886

VS.HSUPA.NACK Total

Number of transmitted NACKs


50331887

VS.HSUPA.DTXT otal

Number of transmitted DTXs


50331888

VS.HSUPA.PDUN um

Number of successfully received MAC-e/MAC-i PDUs from the UE in a cell


50331889

VS.HSUPA.RetransPDUNum

Number of MAC-e/ MAC-i PDUs to be retransmitted by the UE in a cell


50332551

VS.HSUPA.Thrup ut

Total traffic volume of HSUPA users in a cell


50341876

VS.HSUPA.Thrup ut.ROTMor3

Cell throughput of HSUPA users under the 3 dB or above uplink Uu load


50341877




50341878




50341879




50341880




Issue 11 (2015–05–30)


166



Counter ID

Counter Name

Counter Description

Original Release

50341881




50341882




50341883

VS.HSUPA.Thrup ut.ROTAll

Cell throughput of HSUPA users under all uplink Uu loads


50342552

VS.HSUPA.MeanB itRate

Average throughput of HSUPA users in a cell


50342553

VS.HSUPA.MeanB itRate.WithData

Average throughput of HSUPA users in a cell when data is transmitted


50331892

VS.HSUPA.Ic.Mea nEff

Average Efficiency of Interference Cancellation (IC) in a Cell


50341858

VS.HSUPA.Ic.Max Eff

Maximum Efficiency of Interference Cancellation (IC) in a Cell


50331907

VS.CellFirstStageI cEff.Mean

Average Efficiency of Stage 1 Interference Cancellation (IC) in a Cell


50341867

VS.CellFirstStageI cEff.Max

Maximum Efficiency of Stage 1 Interference Cancellation (IC) in a Cell


Issue 11 (2015–05–30)


167



Counter ID

Counter Name

Counter Description

Original Release

50341893

VS.HSUPA.SGLmt .UnHappyUserRati o.Iub

Ratio of Unhappy users with SG limit due to Iub resource insufficiency in a cell


50341894

VS.HSUPA.SGLmt .UnHappyUserRati o.RTWP

Ratio of Unhappy users with SG limit due to air interface load insufficiency in a cell


50341895

VS.HSUPA.SGLmt .UnHappyUserRati o.CE

Ratio of Unhappy users with SG limit due to CE insufficiency in a cell


50341856

VS.HSUPA.FDE.U tilizeTimePermillage

Proportion of the time when HSUPA users use the FDE mode in a cell


50341857

VS.HSUPA. 16QAM.UtilizeTimePermillage

Proportion of the time when HSUPA users uses the 16QAM mode in a cell


50341859

VS.HSUPA.Boostin g.UtilizeTimeRatio

Ratio of the utilize time of boosting in a cell


50341866

VS.HSUPA.AntiInt erfSch.ActRatio

The antiintereference scheduling algrithm active ratio


50341869

VS.HSUPA.TDMS ch.ActRatio

Time-division scheduling algorithm validity probability in a cell


50331957

VS.HSUPA.AlltoSi ngleHARQNum.R TWPCong

Number of transitions from using all HARQ processes to using a single HARQ process due to limited RTWP in the cell


Issue 11 (2015–05–30)


168



Counter ID

Counter Name

Counter Description

Original Release

50331958

VS.HSUPA.AlltoSi ngleHARQNum.C ECong

Number of transitions from using all HARQ processes to using a single HARQ process due to limited CEs in the cell


50331959

VS.HSUPA.SingletoAllHARQNum

Number of Transitions from Using A Single HARQ Process to Using All HARQ Processes In the Cell


50332378

VS.HSUPA.Traffic. TRB

HSUPA Mac-d TRB data volume in the cell


50332379

VS.HSUPA. 2msPDU.TTI.Num

Number of TTIs in which HSUPA 2 ms Mac-e/Mac-i TRBs are received in a cell


50332380

VS.HSUPA. 10msPDU.TTI.Nu m



50332385

VS.HSUPA.TurboI C.Number

Average number of users with Turbo IC enabled in a cell


50332386

VS.HSUPA. 2msTTI.Traffic

Traffic of Mac-e/ Mac-i PDUs received from 2 ms TTI HSUPA users in a cell


50332387


Traffic of Mac-e/ Mac-i PDUs received from 10 ms TTI HSUPA users in a cell


Issue 11 (2015–05–30)


169




Level-1 Counter

VS.HSUPA.Thruput.ROTAll

VS.HSUPA.Thruput.ROTMor3













Cell Load on the Air Interface Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331850

VS.HSUPA.Lo adOutput.0

Number of Cell Ul Load Between 0db to 0.5db


U

50331851




U

50331852




U

50331853




U

50331854




U

Issue 11 (2015–05–30)


170



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331855




U

50331856




U

50331857




U

50331858




U

50331859




U

50331860




U

50331861




U

50331862




U

50331863




U

50331864




U

Issue 11 (2015–05–30)


171



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331865




U

50331866




U

50331867




U

50331868




U

50331869




U

50331870




U

50331871




U

50331872




U

50331873




U

50331874




U

Issue 11 (2015–05–30)


172



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331875


Number of Cell Ul Load above 30db


U

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 NodeB takes statistics on the preceding counters based on the calculated cell air-interface load when obtaining the actual RTWP in the cell.

Formula None

Unit None


Feature ID


Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-010612 LTE: None VS.HSUPA.LoadOutput.1

HSUPA Introduction Package





Issue 11 (2015–05–30)



173



Counter Name

Feature ID


Multi-mode: None

Feature Name



















Issue 11 (2015–05–30)



174



Counter Name

Feature ID


Multi-mode: None

Feature Name



















Issue 11 (2015–05–30)



175



Counter Name

Feature ID


Multi-mode: None

Feature Name



















Issue 11 (2015–05–30)



176



Counter Name

Feature ID


Multi-mode: None

Feature Name



LTE: None VS.HSUPA.LoadOutput.25



LTE: None

Number of Uplink Overloads in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331876

VS.HSUPA.Ov erLoadNum

Number of times the uplink is overloaded in a cell


U

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 Within a measurement period, the NodeB counts the total number of times the cell RTWP exceeds the target RTWP in all TTIs.

Formula None

Unit None

Issue 11 (2015–05–30)


177




Feature ID

VS.HSUPA.OverLoadNum

Multi-mode: None

Feature Name



LTE: None

E-AGCH Code Collision Ratio in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341864

VS.HSUPA.AG CHCodeCollisi on.Mean

Average ratio of E-AGCH code collisions in a cell


U

50331904

VS.HSUPA.AG CHCodeCollisi on.Max

Maximum ratio of E-AGCH code collisions in a cell


U

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.



178



Unit per mill


Feature ID

VS.HSUPA.AGCHCodeCol lision.Mean

Multi-mode: None

Feature Name


VS.HSUPA.AGCHCodeCol lision.Max

Enhanced Fast UL Scheduling



Statistics on AGCH Utilization in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341865

VS.HSUPA.AG CHCodeUtil.M ean

average number of AGCH usage ratio


U

50331903

VS.HSUPA.AG CHCodeUtil.M ax

Max value of AGCH usage ratio


U

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 VS.HSUPA.AGCHCodeUtil.Mean in each sampling period (5s) and takes the maximum sampled value within the measurement period as VS.HSUPA.AGCHCodeUtil.Max. Issue 11 (2015–05–30)


179



Formula None

Unit per mill


Feature ID

VS.HSUPA.AGCHCodeUtil .Mean

Multi-mode: None

Feature Name


VS.HSUPA.AGCHCodeUtil .Max




Number of HSUPA Users with Data Transmission in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341850

VS.HSUPA.Dat aUserNum.Mea n

Average number of HSUPA users that transmit data in a cell


U

50341851

VS.HSUPA.Dat aUserNum.Max

Maximum number of HSUPA users that transmit data in a cell


U

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. Issue 11 (2015–05–30)


180



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


Feature ID

VS.HSUPA.DataUserNum. Mean

Multi-mode: None

Feature Name



LTE: None VS.HSUPA.DataUserNum. Max



LTE: None

Number of Scheduled HSUPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341852

VS.HSUPA.Sc heduleUserNu m.Mean

Average number of scheduled HSUPA users in a cell


U

Issue 11 (2015–05–30)


181



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341853

VS.HSUPA.Sc heduleUserNu m.Max

Maximum number of scheduled HSUPA users in a cell


U

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 DCHSUPA users, the preceding counter is measured in the anchor carrier and the supplementary carrier separately.

Formula None

Unit None


Feature ID

VS.HSUPA.ScheduleUserN um.Mean


Issue 11 (2015–05–30)

Feature Name


HSUPA Introduction Package Enhanced Fast UL Scheduling

182



Counter Name

Feature ID

VS.HSUPA.ScheduleUserN um.Max

Multi-mode: None

Feature Name


HSUPA Introduction Package Enhanced Fast UL Scheduling

LTE: None

Proportion of Power-Limited HSUPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341854

VS.HSUPA.Ma xPwrLmtUserR atio

Ratio of the number of HSUPA users with limited UPH to the total number of HSUPA users in a cell


U

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.

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 in the measurement period is B. Then, VS.HSUPA.MaxPwrLmtUserRatio = A/B. If the power 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.



183



Unit per mill


Feature ID

VS.HSUPA.MaxPwrLmtUserRatio

Multi-mode: None

Feature Name


HSUPA Power Control HSUPA E-AGCH Power Control (Based on CQI or HS-SCCH)

Proportion of Load-Limited HSUPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341855

VS.HSUPA.Lef tPwrLmtUserR atio

Ratio of the number of HSUPA users with limited uplink load to the total number of HSUPA users in a cell


U

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 DCHSUPA users, the preceding counter is measured in the anchor carrier and the supplementary carrier separately. Issue 11 (2015–05–30)


184



Formula None

Unit per mill


Feature ID

VS.HSUPA.LeftPwrLmtUserRatio

Multi-mode: None

Feature Name


HSUPA Admission Control Enhanced Fast UL Scheduling

Number of Unhappy HSUPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331877

VS.HSUPA.Un HappyUserNu m

Number of Unhappy HSUPA users in a cell


U

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



185



Unit None


Feature ID

VS.HSUPA.UnHappyUserNum

Multi-mode: None

Feature Name


96 HSUPA Users per Cell

WRFD-01061211


WRFD-010634


WRFD-010612


LTE: None

Ratio of Unhappy HSUPA Users to Total HSUPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341849

VS.HSUPA.Un HappyUserNu mRatio

Ratio of the number of Unhappy HSUPA users to the total number of HSUPA users in a cell


U

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.

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. Issue 11 (2015–05–30)


186



Formula None

Unit per mill


Feature ID

VS.HSUPA.UnHappyUserNumRatio

Multi-mode: None

Feature Name



WRFD-01061211


WRFD-010634


WRFD-010612


LTE: None

Average Number of 2 ms TTI HSUPA Users at Different Rates in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341892

VS.HSUPA.Lo wRateTTI2msU serNumber

Average number of 2 ms TTI HSUPA users at a rate lower than or equal to 23.25 kbit/s in a cell


U

50341870

VS.HSUPA.TT I2msUserNumb er.0

Average number of 2 ms TTI HSUPA users at a rate of below 150 kbit/s in a cell


U

Issue 11 (2015–05–30)


187



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341871


Average number of 2 ms TTI HSUPA users at a rate in the range of [150 kbit/s,700 kbit/s) in a cell


U

50341872


Average number of 2 ms TTI HSUPA users at a rate in the range of [700 kbit/s,1500 kbit/s) in a cell


U

50341873




U

50341874




U

50341875




U

Description These counters measure the average number of 2 ms TTI HSUPA users at different rates in a cell within a measurement period.

Issue 11 (2015–05–30)


188



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 DCHSUPA 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


Feature ID

VS.HSUPA.LowRateTTI2m sUserNumber


VS.HSUPA.TTI2msUserNumber.0

Feature Name

CE Efficiency Improvement for HSUPA TTI 2ms


Turbo IC

LTE: None VS.HSUPA.TTI2msUserNumber.1


Turbo IC



Turbo IC



Turbo IC

LTE: None

Issue 11 (2015–05–30)


189



Counter Name

Feature ID


Multi-mode: None

Feature Name


Turbo IC



Turbo IC

LTE: None

Average Number of 10 ms TTI HSUPA Users at Different Rates in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341884

VS.HSUPA.TT I10msUserNum ber.0



U

50341885




U

50341886




U

50341887




U

Issue 11 (2015–05–30)


190



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341888




U

50341889




U

50341890




U

50341891




U

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. Issue 11 (2015–05–30)


191



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 DCHSUPA 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


Feature ID




GSM: None LTE: None

GSM: None LTE: None



Issue 11 (2015–05–30)







Feature Name



192



Counter Name

Feature ID


Multi-mode: None

Feature Name












LTE: None

Average Number of Valid Time-Division Scheduling Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341868

VS.HSUPA.TD MUserNum.Me an

Average number of valid time-division scheduling users in a cell


U

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. Issue 11 (2015–05–30)


193



Measurement Points The number of valid HSUPA time-division scheduling users 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 average number of valid time-division scheduling users is equal to the result of the sum of the sampling results divided by the sampling times.

Formula None

Unit None


Feature ID

VS.HSUPA.TDMUserNum. Mean

Multi-mode: None

Feature Name


HSUPA Time Division Scheduling

LTE: None

Number of TTIs with HSUPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331878

VS.HSUPA.Us erTtiNum

Number of TTIs in which at least one HSUPA user exists in a cell


U

Description The preceding counter indicates the number of TTIs when at least one HSUPA user exists in a cell during a measurement period.

Issue 11 (2015–05–30)


194



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


Feature ID

VS.HSUPA.UserTtiNum

Multi-mode: None

Feature Name



LTE: None

Number of TTIs in Which at Least One HSUPA User Transmits Data in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331879

VS.HSUPA.Dat aTtiNum

Number of TTIs in which HSUPA users transmit data in a cell


U

Description The preceding counter indicates the number of TTIs in which at least one HSUPA user transmits data in a cell.

Measurement Points During a measurement period, 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 users with 2 ms TTI and five times for HSUPA users with 10 ms TTI. A DC-HSUPA user is regarded as an HSUPA user in Issue 11 (2015–05–30)


195



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


Feature ID

VS.HSUPA.DataTtiNum

Multi-mode: None

Feature Name



LTE: None

Number of TTIs in Which at Least One HSUPA User Transmits the TRB Data in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331908

VS.HSUPA.Dat aTtiNum.TRB

Number of TTIs in which HSUPA users transmit TRB data in a cell


U

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 During a measurement period, 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 users with 2 ms TTI and five times for HSUPA users with 10 ms TTI. A DC-HSUPA user is regarded as an HSUPA user in each anchor carrier and supplementary carrier. For DCIssue 11 (2015–05–30)


196



HSUPA users, the counter is measured in the anchor carrier and the supplementary carrier separately.

Formula None

Unit None


Feature ID

VS.HSUPA.DataTtiNum.T RB

Multi-mode: None

Feature Name



LTE: None

Number of HSUPA Users with Data Transmission under Different Uplink Uu Loads in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331961

VS.HSUPA.Dat aUserSumNum. ROTMor3



U

50331962




U

Issue 11 (2015–05–30)


197



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331963




U

50331964




U

50331965




U

50331966




U

50331967




U

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.

Issue 11 (2015–05–30)


198



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


Feature ID

VS.HSUPA.DataUserSumN um.ROTMor3



GSM: None LTE: None

GSM: None LTE: None



Issue 11 (2015–05–30)







Feature Name



199



Counter Name

Feature ID


Multi-mode: None

Feature Name



LTE: None VS.HSUPA.DataUserSumN um.ROTMor13



LTE: None VS.HSUPA.DataUserSumN um.ROTMor20



LTE: None

Number of TTIs in Which HSUPA Users Have Data to Transmit under Different Uplink Uu Loads in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331925

VS.HSUPA.Dat aTtiNum.ROT Mor3



U

50331926




U

Issue 11 (2015–05–30)


200



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331927




U

50331928




U

50331929




U

50331930




U

50331931




U

Issue 11 (2015–05–30)


201



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


Feature ID

VS.HSUPA.DataTtiNum.R OTMor3



GSM: None LTE: None



Issue 11 (2015–05–30)




Feature Name



202



Counter Name

Feature ID


Multi-mode: None

Feature Name



LTE: None VS.HSUPA.DataTtiNum.R OTMor10









LTE: None

HSUPA HARQ Distribution in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331885

VS.HSUPA.AC KTotal

Number of transmitted ACKs


U

50331886

VS.HSUPA.NA CKTotal

Number of transmitted NACKs


U

50331887

VS.HSUPA.DT XTotal

Number of transmitted DTXs


U

Issue 11 (2015–05–30)


203



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


Feature ID

VS.HSUPA.ACKTotal

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-010612 LTE: None VS.HSUPA.NACKTotal



VS.HSUPA.DTXTotal




HSUPA MAC-e/MAC-i PDU Statistics in a Cell Issue 11 (2015–05–30)


204



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331888

VS.HSUPA.PD UNum

Number of successfully received MACe/MAC-i PDUs from the UE in a cell


U

50331889


Number of MAC-e/MAC-i PDUs to be retransmitted by the UE in a cell


U


Description

VS.HSUPA.PDUNum

This counter measures the number of MACe/MAC-i PDUs successfully received in the serving cell from HSUPA UEs.


This counter measures the number of retransmitted MAC-e/MAC-i PDUs received in the serving cell from HSUPA UEs.

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

Issue 11 (2015–05–30)


205



Unit None


Feature ID

VS.HSUPA.PDUNum

Multi-mode: None

Feature Name



LTE: None VS.HSUPA.RetransPDUNum



LTE: None

HSUPA MAC Thruput in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332551

VS.HSUPA.Thr uput

Total traffic volume of HSUPA users in a cell


U

Description This counter measures the total traffic volume of the MAC-d PDUs successfully received from all HSUPA users in a cell within a measurement period. Disuse Statement: The counter 50332551 VS.HSUPA.Thruput will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points The traffic volume of the MAC-d PDUs successfully received from all HSUPA users in a cell is sampled every 100 ms, and the accumulated value is reported. In softer handover scenarios, the throughput is averaged among cells. Issue 11 (2015–05–30)


206



Formula None

Unit kbit


Feature ID

VS.HSUPA.Thruput

Multi-mode: None

Feature Name



LTE: None

Cell Throughput of HSUPA Users Under Different Uplink Uu Loads Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341876

VS.HSUPA.Thr uput.ROTMor3



U

50341877




U

50341878




U

50341879




U

Issue 11 (2015–05–30)


207



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341880

VS.HSUPA.Thr uput.ROTMor1 0



U

50341881




U

50341882




U

50341883

VS.HSUPA.Thr uput.ROTAll

Cell throughput of HSUPA users under all uplink Uu loads


U

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

Issue 11 (2015–05–30)


208




Feature ID




GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None



Issue 11 (2015–05–30)
















Feature Name



209



Counter Name

Feature ID


Multi-mode: None

Feature Name



LTE: None

HSUPA MAC Average Throughput in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342552

VS.HSUPA.Me anBitRate

Average throughput of HSUPA users in a cell


U

Description This counter measures the average throughput of MAC-d data flows successfully received from all HSUPA users in a cell within a measurement period. Disuse Statement: The counter 50342552 VS.HSUPA.MeanBitRate will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Assume that the volume of MAC-d data flows successfully received from all HSUPA users in a cell within a measurement period is A and the length of the measurement period is B. The formula for calculating this counter is: VS.HSUPA.MeanBitRate = A/B. In softer handover scenarios, the throughput is averaged among cells. In soft handover scenarios, the throughput is measured on the basis of the actual traffic volume received in each cell.

Formula None

Unit kbit/s Issue 11 (2015–05–30)


210




Feature ID

VS.HSUPA.MeanBitRate

Multi-mode: None

Feature Name



LTE: None

HSUPA MAC Throughput in a Cell During Data Transmission Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342553

VS.HSUPA.Me anBitRate.With Data

Average throughput of HSUPA users in a cell when data is transmitted


U

Description This counter measures the average throughput of MAC-d data flows successfully received from HSUPA users that transmit data in a cell within a measurement period. Disuse Statement: The counter 50342553 VS.HSUPA.MeanBitRate.WithData will be deleted in later version. In current version, the value of this counter take effect. This counter is not recommended.

Measurement Points Assume that the volume of MAC-d data flows successfully received from all HSUPA users that transmit data in a cell within a measurement period is A and the length of the time when data is transmitted is B. The formula for calculating this counter is: VS.HSUPA.MeanBitRate.WithData = A/B. In this formula, B is the number of samples when data is transmitted multiplies the sampling period, for example, 100 ms. If the traffic volume of received MAC-d PDUs is 0 within a sampling period, the sampling period is not considered. In softer handover scenarios, the throughput is averaged among cells. In soft handover scenarios, the throughput is measured on the basis of the actual traffic volume received in each cell.



211



Unit kbit/s


Feature ID

VS.HSUPA.MeanBitRate. WithData

Multi-mode: None

Feature Name



LTE: None

Average/Maximum IC Efficiency in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331892

VS.HSUPA.Ic. MeanEff

Average Efficiency of Interference Cancellation (IC) in a Cell


U

50341858

VS.HSUPA.Ic. MaxEff

Maximum Efficiency of Interference Cancellation (IC) in a Cell


U

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 MTRU or 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. Issue 11 (2015–05–30)


212



Formula None

Unit %


Feature ID

VS.HSUPA.Ic.MeanEff

Multi-mode: None

Feature Name


HSUPA UL Interference Cancellation Control Channel Parallel Interference Cancellation (CCPIC) Control Channel Parallel Interference Cancellation (Phase 2) Turbo IC

VS.HSUPA.Ic.MaxEff

Multi-mode: None GSM: None UMTS: WRFD-010691 WRFD-010210 WRFD-140202 WRFD-150206 LTE: None

HSUPA UL Interference Cancellation Control Channel Parallel Interference Cancellation (CCPIC) Control Channel Parallel Interference Cancellation (Phase 2) Turbo IC

Average/Maximum IC Efficiency of Stage 1 in a Cell

Issue 11 (2015–05–30)


213



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331907

VS.CellFirstSta geIcEff.Mean

Average Efficiency of Stage 1 Interference Cancellation (IC) in a Cell

BTS3900 WCDMA

U

50341867

VS.CellFirstSta geIcEff.Max

Maximum Efficiency of Stage 1 Interference Cancellation (IC) in a Cell

BTS3900 WCDMA

U

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. If Control Channel Parallel Interference Cancellation (Phase 2) takes effect, stage 1 IC is specific to the DPCCH. If Control Channel Parallel Interference Cancellation (Phase 3) takes effect, stage 1 IC is specific to the DPCCH, HS-DPCCH, or E-DPCCH. When the MTRU or RRU3801c is used, an invalid value 0xffff is displayed. Disuse Statement: The counter 50331907 VS.CellFirstStageIcEff.Mean will be deleted and replaced by 50332061 VS.FirstStageIcEff.Mean in later versions. In current version, both the counters take effect but VS.CellFirstStageIcEff.Mean is not recommended. The counter 50341867 VS.CellFirstStageIcEff.Max will be deleted and replaced by 50342048 VS.FirstStageIcEff.Max in later versions. In current version, both the counters take effect but VS.CellFirstStageIcEff.Max is not recommended.

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.CellFirstStageIcEff.Mean = A/B. The NodeB takes the maximum sampled value within the measurement period as VS.CellFirstStageIcEff.Max.



214



Unit %


Feature ID

VS.CellFirstStageIcEff.Mea n

Multi-mode: None

Feature Name


Control Channel Parallel Interference Cancellation (Phase 2)


VS.CellFirstStageIcEff.Max






Ratio of Unhappy HSUPA Users with SG Limit due to Resource Insufficiency in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341893

VS.HSUPA.SG Lmt.UnHappyU serRatio.Iub

Ratio of Unhappy users with SG limit due to Iub resource insufficiency in a cell


U

Issue 11 (2015–05–30)


215



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341894

VS.HSUPA.SG Lmt.UnHappyU serRatio.RTWP

Ratio of Unhappy users with SG limit due to air interface load insufficiency in a cell


U

50341895

VS.HSUPA.SG Lmt.UnHappyU serRatio.CE

Ratio of Unhappy users with SG limit due to CE insufficiency in a cell


U

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. A divided by D is used as the value of the VS.HSUPA.SGLmt.UnHappyUserRatio.Iub counter. B divided by D is used as the value of the VS.HSUPA.SGLmt.UnHappyUserRatio.RTWP counter. C divided by D is used as the value of the VS.HSUPA.SGLmt.UnHappyUserRatio.CE counter. 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 Issue 11 (2015–05–30)


216




Feature ID

VS.HSUPA.SGLmt.UnHap pyUserRatio.Iub

Multi-mode: None

Feature Name



LTE: None VS.HSUPA.SGLmt.UnHap pyUserRatio.RTWP



LTE: None VS.HSUPA.SGLmt.UnHap pyUserRatio.CE



LTE: None

Proportion of the Time When FDE is Used in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341856

VS.HSUPA.FD E.UtilizeTimePermillage

Proportion of the time when HSUPA users use the FDE mode in a cell


U

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. Remarks: After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) 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. Issue 11 (2015–05–30)


217



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.

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


Feature ID

VS.HSUPA.FDE.UtilizeTimePermillage

Multi-mode: None

Feature Name


HSUPA FDE

LTE: None

Proportion of the Time When 16QAM is Used in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341857

VS.HSUPA. 16QAM.Utilize TimePermillage

Proportion of the time when HSUPA users uses the 16QAM mode in a cell


U

Issue 11 (2015–05–30)


218



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. Remarks: After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) 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. 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.

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


Feature ID

VS.HSUPA. 16QAM.UtilizeTimePermillage

Multi-mode: None

Feature Name


UL 16QAM

LTE: None

Proportion of the Time When Boosting is Used in a Cell

Issue 11 (2015–05–30)


219



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341859

VS.HSUPA.Bo osting.UtilizeTimeRatio

Ratio of the utilize time of boosting in a cell


U

Description The preceding counter indicates the Boosting usage in a cell during a measurement period. Remarks: After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) 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. 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.

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

Issue 11 (2015–05–30)


220




Feature ID

VS.HSUPA.Boosting.UtilizeTimeRatio

Multi-mode: None

Feature Name


E-DPCCH Boosting

LTE: None

Possibility of the Active Anti-Interference Scheduling Algorithm in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341866

VS.HSUPA.An tiInterfSch.ActRatio

The antiintereference scheduling algrithm active ratio


U

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 antiinterference 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

Issue 11 (2015–05–30)


221




Feature ID

VS.HSUPA.AntiInterfSch.A ctRatio

Multi-mode: None

Feature Name


Anti-Interference Scheduling for HSUPA

LTE: None

Time-Division Scheduling Algorithm Validity Probability in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341869

VS.HSUPA.TD MSch.ActRatio

Time-division scheduling algorithm validity probability in a cell


U

Description This counter measures the time-division scheduling algorithm validity probability 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 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

Issue 11 (2015–05–30)


222




Feature ID

VS.HSUPA.TDMSch.ActRatio

Multi-mode: None

Feature Name


HSUPA Time Division Scheduling

LTE: None

Number of Transitions from Using All HARQ Processes to Using A Single HARQ Process In the Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331957

VS.HSUPA.All toSingleHARQ Num.RTWPCo ng

Number of transitions from using all HARQ processes to using a single HARQ process due to limited RTWP in the cell


U

50331958

VS.HSUPA.All toSingleHARQ Num.CECong

Number of transitions from using all HARQ processes to using a single HARQ process due to limited CEs in the cell


U


Issue 11 (2015–05–30)


223



Counter Name

Description

VS.HSUPA.AlltoSingleHARQNum.RTWP Cong

This counter measures the number of transitions from using all HARQ processes to using a single HARQ process due to limited RTWP in the cell.

VS.HSUPA.AlltoSingleHARQNum.CECong

This counter measures the number of transitions from using all HARQ processes to using a single HARQ process due to limited CEs in the cell.

Measurement Points The following table describes the Measurement Points of each counter. Counter Name

Measurement Points

VS.HSUPA.AlltoSingleHARQNum.RTWP Cong

This counter measures the number of transitions from using all HARQ processes to using a single HARQ process within a measurement period due to limited RTWP in the service cell.

VS.HSUPA.AlltoSingleHARQNum.CECong

This counter measures the number of transitions from using all HARQ processes to using a single HARQ process within a measurement period due to limited CEs in the serving cell.

Formula None

Unit None


Feature ID

VS.HSUPA.AlltoSingleHA RQNum.RTWPCong

Multi-mode: None

Feature Name


Turbo IC Phase 2

LTE: None Issue 11 (2015–05–30)


224



Counter Name

Feature ID

VS.HSUPA.AlltoSingleHA RQNum.CECong

Multi-mode: None

Feature Name



LTE: None

Number of Transitions from Using A Single HARQ Process to Using All HARQ Processes In the Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331959

VS.HSUPA.Sin gletoAllHARQ Num

Number of Transitions from Using A Single HARQ Process to Using All HARQ Processes In the Cell


U

Description This counter measures the number of transitions from using a single HARQ process to using all HARQ processes in the cell.

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

Issue 11 (2015–05–30)


225




Feature ID

VS.HSUPA.SingletoAllHARQNum

Multi-mode: None

Feature Name


Turbo IC Phase 2

WRFD-160205


LTE: None

HSUPA Mac-d TRB data volume in the cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332378

VS.HSUPA.Tra ffic.TRB

HSUPA Mac-d TRB data volume in the cell


U

Description This counter measures the traffic volume of HSUPA TRB PDUs in a cell. 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.

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. For a DC-HSUPA user, the corresponding counter is measured in the primary and secondary carriers separately.

Formula None

Unit kbit

Issue 11 (2015–05–30)


226




Feature ID

Feature Name

VS.HSUPA.Traffic.TRB



LTE: None

Number of TTIs in which HSUPA Mac-e/Mac-i TRBs are received in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332379

VS.HSUPA. 2msPDU.TTI.N um



U

50332380

VS.HSUPA. 10msPDU.TTI. Num



U


Description

VS.HSUPA.2msPDU.TTI.Num

This counter measures the number of TTIs in which Mac-e/Mac-i TRBs are received from HSUPA 2 ms TTI users in the serving cell 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.

Issue 11 (2015–05–30)


227



Counter Name

Description

VS.HSUPA.10msPDU.TTI.Num

This counter measures the number of TTIs in which Mac-e/Mac-i TRBs are received from HSUPA 10 ms TTI users in the serving cell 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. This counter does not involve the number of HSUPA 10 ms Mac-e/Mac-i TRB PDUs received by the WBBPa.

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


Feature ID



Issue 11 (2015–05–30)

Feature Name



228



Counter Name

Feature ID


Multi-mode: None

Feature Name



LTE: None

Average number of users with Turbo IC enabled in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332385

VS.HSUPA.Tur boIC.Number

Average number of users with Turbo IC enabled in a cell


U

Description This counter measures the average number of users with Turbo IC enabled within a measurement period in the HSUPA cell.

Measurement Points This counter is sampled every 10 ms and measures the number of users with Turbo IC enabled within a measurement period. The accumulated value is A, and the number of samples is B. The formula for calculating this counter is: VS.HSUPA.TurboIC.Number=A/B.

Formula None

Unit None

Issue 11 (2015–05–30)


229




Feature ID

VS.HSUPA.TurboIC.Number

Multi-mode: None

Feature Name


Turbo IC

LTE: None

Traffic of Mac-e/Mac-i PDUs received from 2 ms TTI HSUPA users in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332386


Traffic of Mace/Mac-i PDUs received from 2 ms TTI HSUPA users in a cell


U

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

Issue 11 (2015–05–30)


230




Feature ID

VS.HSUPA.2msTTI.Traffic

Multi-mode: None

Feature Name


HSUPA Phase 2

LTE: None

Traffic of Mac-e/Mac-i PDUs received from 10 ms TTI HSUPA users in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332387

VS.HSUPA. 10msTTI.Traffi c

Traffic of Mace/Mac-i PDUs received from 10 ms TTI HSUPA users in a cell


U

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

Issue 11 (2015–05–30)


231




Feature ID

Feature Name




1.1.4 CPC Measurement (CPC.LOCELL) 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 Description

Original Release

50331748

VS.CPC.DTXCfg. UserNum

Number of UL_DTX users in a cell


50331749

VS.CPC.DTXAct.U serNum

User Numbers with the status of UL_DTX and actived Configuration


50331750

VS.CPC.DRXCfg. UserNum

Number of DL_DRX users in a cell


50331751

VS.CPC.DRXAct. UserNum

User Numbers with the status of UL_DRX and actived Configuration


50331752

VS.CPC.LesOpCfg .SceduledNum

Number of users in Less mode in a cell


Issue 11 (2015–05–30)


232



Counter ID

Counter Name

Counter Description

Original Release

50331753

VS.CPC.LesOpCfg .LesModeNum

Schedule Numbers to the user configured Less opration Mode and actually used less transferred



Number of UL_DTX Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331748

VS.CPC.DTXC fg.UserNum

Number of UL_DTX users in a cell


U

50331749

VS.CPC.DTXA ct.UserNum

User Numbers with the status of UL_DTX and actived Configuration


U


Description

VS.CPC.DTXCfg.UserNum

Number of UL_DTX users in a cell.

VS.CPC.DTXAct.UserNum

Number of active users in the status of UL_DTX.

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. Issue 11 (2015–05–30)


233



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



234




Feature ID

Feature Name

VS.CPC.DTXCfg.UserNum


CPC-DTX/DRX

LTE: None VS.CPC.DTXAct.UserNum


CPC-DTX/DRX

LTE: None

Number of DL_DRX Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331750

VS.CPC.DRXC fg.UserNum

Number of DL_DRX users in a cell


U

50331751

VS.CPC.DRXA ct.UserNum

User Numbers with the status of UL_DRX and actived Configuration


U


Description

VS.CPC.DRXCfg.UserNum

Number of DL_DRX users in a cell.

VS.CPC.DRXAct.UserNum

Number of active users in the status of DL_DRX.

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 Issue 11 (2015–05–30)


235



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

Issue 11 (2015–05–30)


236



Unit None


Feature ID

Feature Name

VS.CPC.DRXCfg.UserNum


CPC-DTX/DRX

LTE: None VS.CPC.DRXAct.UserNum


CPC-DTX/DRX

LTE: None

Number of Users in HS-SCCH-Less Mode in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331752

VS.CPC.LesOp Cfg.SceduledN um

Number of users in Less mode in a cell


U

50331753

VS.CPC.LesOp Cfg.LesModeN um

Schedule Numbers to the user configured Less opration Mode and actually used less transferred


U


Description

VS.CPC.LesOpCfg.SceduledNum

Total number of times all the users in HSSCCH-less mode in a cell are scheduled during a measurement period.

Issue 11 (2015–05–30)


237



Counter Name

Description

VS.CPC.LesOpCfg.LesModeNum

Total number of times all the users in HSSCCH-less mode in a cell are scheduled and perform the HS-SCCH-less operation during a measurement period.

Measurement Points The NodeB takes statistics about the preceding counters when MAC-hs/MAC-ehs scheduling is complete.

Formula None

Unit None


Feature ID

VS.CPC.LesOpCfg.SceduledNum


VS.CPC.LesOpCfg.LesModeNum

Feature Name

CPC-HS-SCCH less operation


CPC-HS-SCCH less operation

1.1.5 ERACH Measurement (ERACH.LOCELL) Overview The function subset consists of ERACH-related counters.

Issue 11 (2015–05–30)


238



Counters Counter ID

Counter Name

Counter Description

Original Release

50332250

VS.ERACH.Occup iedNum.Mean

Mean used Common E-DCH number in one cell


50332251

VS.ERACH.Occup iedNum.Max

Max used Common E-DCH number in one cell


50332410

VS.ERACH.Thrup ut

Throughput of ERACH users at the Mac-i layer in a cell


50332411

VS.ERACH.DataTtiNum

Number of TTIs in which E-RACH users have data to transmit in a cell



Number of used common E-DCHs in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332250

VS.ERACH.Oc cupiedNum.Me an

Mean used Common EDCH number in one cell


U

50332251

VS.ERACH.Oc cupiedNum.Ma x

Max used Common EDCH number in one cell


U

Description This counter measures the number of used common E-DCHs in a cell. Issue 11 (2015–05–30)


239



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


Feature ID

VS.ERACH.OccupiedNum. Mean

Multi-mode: None

Feature Name


Uplink Enhanced CELL_FACH

LTE: None VS.ERACH.OccupiedNum. Max



LTE: None

Throughput of E-RACH users at the Mac-i layer in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332410

VS.ERACH.Th ruput

Throughput of E-RACH users at the Mac-i layer in a cell


U

Issue 11 (2015–05–30)


240



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


Feature ID

VS.ERACH.Thruput

Multi-mode: None

Feature Name



LTE: None

Number of TTIs in which E-RACH users have data to transmit in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332411

VS.ERACH.Da taTtiNum

Number of TTIs in which ERACH users have data to transmit in a cell


U

Description This counter measures the number of TTIs in which E-RACH users have data to transmit within a measurement period in a cell. Issue 11 (2015–05–30)


241



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


Feature ID

Feature Name

VS.ERACH.DataTtiNum



1.1.6 SCCPCH Measurement (SCCPCH.LOCELL) Overview The function subset consists of SCCPCH-related counters for a cell.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332048

VS.FPNum.Receive d.FACH

Number of FACH FP frames correctly received in a cell


50332049

VS.FPNum.Discar ded.FACH

Number of FACH FP frames discarded in a cell


Issue 11 (2015–05–30)


242



Counter ID

Counter Name

Counter Description

Original Release

50332050

VS.FPNum.Receive d.PCH

Number of PCH FP frames correctly received in a cell


50332051

VS.FPNum.Discar ded.PCH

Number of PCH FP frames discarded in a cell



Statistics on Received and Discarded FACH FP Frames in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332048

VS.FPNum.Rec eived.FACH

Number of FACH FP frames correctly received in a cell


U

50332049

VS.FPNum.Dis carded.FACH

Number of FACH FP frames discarded in a cell


U


Description

VS.FPNum.Received.FACH

Number of FACH FP frames correctly received on the SCCPCH in a cell.

Issue 11 (2015–05–30)


243



Counter Name

Description

VS.FPNum.Discarded.FACH

Number of discarded FACH FP frames on the SCCPCH in a cell. These frames are discarded because of CRC errors, invalid parameters, too-early frame arrival, or toolate frame arrival.

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



244




Feature ID

Feature Name

VS.FPNum.Received.FACH


Physical Channel Management

LTE: None VS.FPNum.Discarded.FAC H



LTE: None

Statistics on Received and Discarded PCH FP Frames in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332050

VS.FPNum.Rec eived.PCH

Number of PCH FP frames correctly received in a cell


U

50332051

VS.FPNum.Dis carded.PCH

Number of PCH FP frames discarded in a cell


U


Description

VS.FPNum.Received.PCH

Number of PCH FP frames correctly received on the SCCPCH in a cell.

Issue 11 (2015–05–30)


245



Counter Name

Description

VS.FPNum.Discarded.PCH

Number of discarded PCH FP frames on the SCCPCH in a cell. These frames are discarded because of CRC errors, invalid parameters, too-early frame arrival, or toolate frame arrival.

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



246




Feature ID

Feature Name

VS.FPNum.Received.PCH


VS.FPNum.Discarded.PCH




1.1.7 DCH Measurement (DCH.LOCELL) Overview The function subset consists of DCH-related counters for a cell.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332052

VS.FPNum.Discar ded.DCH

Number of downlink DCH FP frames discarded in a cell


50332053

VS.FPNum.Late.D CH

Number of downlink DCH FP frames late received in a cell


50332054

VS.FPNum.Receive d.DCH

Number of downlink DCH FP frames correctly received in a cell



Issue 11 (2015–05–30)


247



Statistics on Received and Discarded Downlink DCH FP Frames in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332052

VS.FPNum.Dis carded.DCH

Number of downlink DCH FP frames discarded in a cell


U

50332053

VS.FPNum.Lat e.DCH

Number of downlink DCH FP frames late received in a cell


U

50332054

VS.FPNum.Rec eived.DCH

Number of downlink DCH FP frames correctly received in a cell


U


Description

VS.FPNum.Discarded.DCH

Number of discarded downlink DCH FP frames in a cell. These frames are discarded because of CRC errors, invalid parameters, too-early frame arrival, or too-late frame arrival.

VS.FPNum.Late.DCH

Number of downlink DCH FP frames received later than expected (after ToAWE but before LTOA) in a cell.

VS.FPNum.Received.DCH

Number of downlink DCH FP frames correctly received in a cell.

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:

Issue 11 (2015–05–30)


248



Figure 1-10

Formula None

Unit None


Feature ID

VS.FPNum.Discarded.DCH

Multi-mode: None

Feature Name


Issue 11 (2015–05–30)


Transport Channel Management

249



Counter Name

Feature ID

Feature Name

VS.FPNum.Late.DCH


VS.FPNum.Received.DCH




1.1.8 Cell Algorithm Measurement (ALGO.LOCELL) Overview The function subset consists of algorithm-related counters.

Counters Counter ID

Counter Name

Counter Description

Original Release

50331917

VS.ValidAntRatio. Mean

Average ratio of the number of valid antennas to the number of configured antennas


50332061

VS.FirstStageIcEff. Mean

Average value of stage 1 interference cancellation efficiency


50342048

VS.FirstStageIcEff. Max

Maximum value of stage 1 interference cancellation efficiency


50342049

VS.DlCode.Used.M ean

Average number of normalized downlink codes used in a cell


Issue 11 (2015–05–30)


250



Counter ID

Counter Name

Counter Description

Original Release

50332064

VS.DlCode.Used.M ax

Maximum number of normalized downlink codes used in a cell


50332258

VS.PLVA.User

Numbers of plva user in one cell


50332388

VS.IRC.UserNum

Average number of users using IRC in a cell


50332389

VS.CCPICPhase3. CodeNum.Mean

Average number of channels for CCPIC Phase 3 by users in a cell



Average Ratio of the Number of Valid Antennas to the Number of Configured Antennas Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331917

VS.ValidAntRa tio.Mean

Average ratio of the number of valid antennas to the number of configured antennas


U

Description This counter measures the average ratio of the number of valid antennas to the number of configured antennas.

Issue 11 (2015–05–30)


251



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


Feature ID

Feature Name

VS.ValidAntRatio.Mean

Multi-mode: MRFD-210604

2-Way Antenna Receive Diversity


4-Antenna Receive Diversity

LTE: None

Average/Maximum Efficiency of Stage 1 Interference Cancellation (IC) in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332061

VS.FirstStageIc Eff.Mean

Average value of stage 1 interference cancellation efficiency


U

Issue 11 (2015–05–30)


252



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342048

VS.FirstStageIc Eff.Max

Maximum value of stage 1 interference cancellation efficiency


U

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. If Control Channel Parallel Interference Cancellation (Phase 2) takes effect, stage 1 IC is specific to the DPCCH. If Control Channel Parallel Interference Cancellation (Phase 3) takes effect, stage 1 IC is specific to the DPCCH, HS-DPCCH, or E-DPCCH. When the MTRU or RRU3801c is used, an invalid value 0xffff is displayed.

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 %

Issue 11 (2015–05–30)


253




Feature ID

VS.FirstStageIcEff.Mean

Multi-mode: None

Feature Name




VS.FirstStageIcEff.Max






Number of Normalized Downlink Codes Used in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342049

VS.DlCode.Use d.Mean

Average number of normalized downlink codes used in a cell


U

50332064

VS.DlCode.Use d.Max

Maximum number of normalized downlink codes used in a cell


U

Issue 11 (2015–05–30)


254



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 HSDSCH. For example, if a code in SFk is normalized using SF256, the calculation formula is 256/ k. However, the codes used for service simulation in the NodeB in some scenarios are not included, such as downlink load simulation or intermodulation interference.

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


Feature ID

VS.DlCode.Used.Mean

Multi-mode: None

Feature Name


Code Resource Management

LTE: None VS.DlCode.Used.Max


Code Resource Management

LTE: None

User Number of PLVA in the local cell

Issue 11 (2015–05–30)


255



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332258

VS.PLVA.User

Numbers of plva user in one cell


U

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.UserNum = A/B.

Formula None

Unit None


Feature ID

VS.PLVA.User

Multi-mode: None

Feature Name


AMR Voice Quality Improvement Based on PLVA

Average Number of IRC Users in a Cell

Issue 11 (2015–05–30)


256



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332388

VS.IRC.UserN um

Average number of users using IRC in a cell


U

Description This counter measures the average number of users using IRC in a cell.

Measurement Points Within a measurement period, the number of users using IRC is sampled every 10ms. At the end of the measurement period, the accumulated value of users using IRC is recorded as A, and the number of samples is recorded as B. A divided by B is used as the value of the VS.IRC.UserNum counter.

Formula None

Unit None


Feature ID

VS.IRC.UserNum

Multi-mode: None

Feature Name


Interference Rejection Combining (IRC)

Average Number of Channels for CCPIC Phase 3 in a Cell

Issue 11 (2015–05–30)


257



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332389

VS.CCPICPhas e3.CodeNum.M ean

Average number of channels for CCPIC Phase 3 by users in a cell


U

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


Feature ID

VS.CCPICPhase3.CodeNu m.Mean


Issue 11 (2015–05–30)

Feature Name



258



1.1.9 Cell Reserved Counter Measurement (CELLRESERVE.LOCELL) Overview The function subset indicates measurements reserved for local cells. 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 Description

Original Release

50331740

VS.CellReserve.Co unter1

Reserved 1 in the cell


50331741




50331742




50331743




50331744




50331909




50331910




Issue 11 (2015–05–30)


259



Counter ID

Counter Name

Counter Description

Original Release

50331911




50331912




50331913




50332381




50332382




50332576




50332577






Issue 11 (2015–05–30)


260



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331740

VS.CellReserve .Counter1



U

Description None. The following table describes the meanings of each counter: Counter Name

Description

VS.CellReserve.Counter1

None.

Measurement Points None.

Formula None

Unit None

Related Features None

Reserved 2 in the cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331741




U

Issue 11 (2015–05–30)


261




Description


None.


Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50331742




U


Description


None.

Issue 11 (2015–05–30)


262




Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50331743




U


Description


None.


Formula None



263





Counter Name

Counter Description

Network Element

Applicable Mode

50331744




U


Description


None.


Formula None

Unit None



Issue 11 (2015–05–30)


264



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331909




U


Description


None.


Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50331910




U

Issue 11 (2015–05–30)


265




Description


None.


Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50331911




U


Description


None.

Issue 11 (2015–05–30)


266




Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50331912




U


Description


None.


Formula None



267





Counter Name

Counter Description

Network Element

Applicable Mode

50331913




U


Description


None.


Formula None

Unit None



Issue 11 (2015–05–30)


268



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332381




U


Description


None.

Measurement Points None

Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332382




U

Issue 11 (2015–05–30)


269




Description


None.

Measurement Points None

Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332576




U


Description


None.

Issue 11 (2015–05–30)


270




Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332577




U


Description


None.


Formula None



271




1.1.10 Cell Power Measurement (POWER.LOCELL) Overview The function subset consists of counters related to uplink load and downlink power.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332055

VS.DlPwrRatio.SF 256

Average ratio of SF 256 downlink code channel transmit power to the maximum downlink transmit power in a cell


50332056

VS.DlPwrRatio.SF 128



50332057

VS.DlPwrRatio.SF 64



50332058

VS.DlPwrRatio.SF 32



Issue 11 (2015–05–30)


272



Counter ID

Counter Name

Counter Description

Original Release

50332059

VS.DlPwrRatio.SF 16



50332060

VS.DlPwrRatio.SF 8



50332278

VS.DPCCH.R99.P OWER

DPCCH uplink power load of R99 services in a cell


50332279

VS.DPDCH.R99. POWER

DPDCH uplink power load of R99 services in a cell


50332280

VS.HSDPCCH.PO WER

HSDPCCH uplink power load of HSDPA services in a cell


50332281

VS.DPCCH. 10ms.POWER

DPCCH uplink power load of 10 ms TTI HSUPA services in a cell


50332282

VS.DPCCH. 2ms.POWER



50332283

VS.EDPCCH. 10ms.POWER

EDPCCH uplink power load of 10 ms TTI HSUPA services in a cell


50332284




Issue 11 (2015–05–30)


273



Counter ID

Counter Name

Counter Description

Original Release

50332285

VS.EDPDCH. 10ms.POWER

EDPDCH uplink power load of 10 ms TTI HSUPA services in a cell


50332286




50361648

VS.DLDCHPwrRa tio.SharedOperator0

Average ratio of downlink DCH transmit power occupied by operator 0 in an MOCN network


50361649




50361650




50361651





Average Ratio of DPCH and F-DPCH Transmit Power over Different SF Code Channels to the Maximum Downlink Transmit Power in a Cell

Issue 11 (2015–05–30)


274



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332055

VS.DlPwrRatio .SF256



U

50332056

VS.DlPwrRatio .SF128



U

50332057

VS.DlPwrRatio .SF64



U

50332058

VS.DlPwrRatio .SF32



U

50332059

VS.DlPwrRatio .SF16



U

Issue 11 (2015–05–30)


275



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332060

VS.DlPwrRatio .SF8



U

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


Uplink power loads of different services in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332278

VS.DPCCH.R9 9.POWER

DPCCH uplink power load of R99 services in a cell


U

Issue 11 (2015–05–30)


276



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332279

VS.DPDCH.R9 9. POWER

DPDCH uplink power load of R99 services in a cell


U

50332280

VS.HSDPCCH. POWER

HSDPCCH uplink power load of HSDPA services in a cell


U

50332281

VS.DPCCH. 10ms.POWER



U

50332282

VS.DPCCH. 2ms.POWER



U

50332283




U

50332284




U

50332285




U

50332286




U

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: Issue 11 (2015–05–30)


277



Counter Name

Description

VS.DPCCH.R99.POWER

This counter measures the ratio of DPCCH uplink power of R99 users to the total uplink power.

VS.DPDCH.R99. POWER

This counter measures the ratio of DPDCH uplink power of R99 users to the total uplink power.

VS.HSDPCCH.POWER

This counter measures the ratio of HSDPCCH uplink power of HSDPA users to the total uplink power, including only the CQI load, not ACK/NACK load.

VS.DPCCH.10ms.POWER

This counter measures the ratio of DPCCH uplink power of 10 ms TTI HSUPA users to the total uplink power.

VS.DPCCH.2ms.POWER

This counter measures the ratio of DPCCH uplink power of 2 ms TTI HSUPA users to the total uplink power.

VS.EDPCCH.10ms.POWER

This counter measures the ratio of EDPCCH uplink power of 10 ms TTI HSUPA users to the total uplink power.

VS.EDPCCH.2ms.POWER

This counter measures the ratio of EDPCCH uplink power of 2 ms TTI HSUPA users to the total uplink power.

VS.EDPDCH.10ms.POWER

This counter measures the ratio of EDPDCH uplink power of 10 ms TTI HSUPA users to the total uplink power.

VS.EDPDCH.2ms.POWER

This counter measures the ratio of EDPDCH uplink power of 2 ms TTI HSUPA users to the total uplink power.

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

Issue 11 (2015–05–30)


278



Unit per mill


Average Ratio of Downlink DCH Transmit Power Occupied by Operator 0 in an MOCN Network Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50361648

VS.DLDCHPw rRatio.SharedO perator0



U

50361649




U

50361650




U

50361651




U

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. Issue 11 (2015–05–30)


279



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


Feature ID

VS.DLDCHPwrRatio.Share dOperator0



GSM: None LTE: None

GSM: None LTE: None

MOCN Cell Resource Demarcation


Issue 11 (2015–05–30)







Feature Name



280



1.1.11 EFACH Measurement (EFACH.LOCELL) Overview The function subset consists of EFACH-related counters for a cell.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332163

VS.EFACH.AckTti Num

Number of TTIs in Which the NodeB Receives ACKs from E-FACH Users in a Cell


50332164

VS.EFACH.NackT tiNum

Number of TTIs in Which the NodeB Receives NACKs from E-FACH Users in a Cell


50332165

VS.EFACH.DtxTti Num

Number of TTIs in Which the NodeB Does Not Receive ACKs or NACKs from E-FACH Users in a Cell


50332162

VS.EFACH.DataTtiNum

Number of TTIs in Which E-FACH Users Have Data to Transmit in a Cell


50332161

VS.EFACH.Thrup ut

E-FACH User Throughput at the MAC-ehs Layer in a Cell


50341718

VS.EFACH.ScchP wrRatio.Mean

Average HS-SCCH transmit power of all E-FACH users in a cell


50341719

VS.EFACH.ScchP wrRatio.Max

Maximum HSSCCH transmit power of all E-FACH users in a cell


Issue 11 (2015–05–30)


281



Counter ID

Counter Name

Counter Description

Original Release

50341720

VS.EFACH.Pdsch PwrRatio.Mean

Average HS-PDSCH transmit power of all E-FACH users in a cell


50341721

VS.EFACH.Pdsch PwrRatio.Max

Maximum HSPDSCH transmit power of all E-FACH users in a cell



E-FACH HARQ Distributing in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332163

VS.EFACH.Ac kTtiNum

Number of TTIs in Which the NodeB Receives ACKs from E-FACH Users in a Cell


U

50332164

VS.EFACH.Na ckTtiNum

Number of TTIs in Which the NodeB Receives NACKs from EFACH Users in a Cell


U

50332165

VS.EFACH.Dt xTtiNum

Number of TTIs in Which the NodeB Does Not Receive ACKs or NACKs from EFACH Users in a Cell


U

Issue 11 (2015–05–30)


282



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: Counter Name

Description

VS.EFACH.AckTtiNum

This counter measures the number of TTIs in which the NodeB receives ACKs from EFACH users over the HS-DPCCH in a cell.

VS.EFACH.NackTtiNum

This counter measures the number of TTIs in which the NodeB receives NACKs from EFACH users over the HS-DPCCH in a cell.

VS.EFACH.DtxTtiNum

This counter measures the number of TTIs in which the NodeB does not receive ACKs or NACKs from these E-FACH users over the HS-DPCCH in a cell.

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


Feature ID

VS.EFACH.AckTtiNum

Multi-mode: None

Feature Name


Issue 11 (2015–05–30)



283



Counter Name

Feature ID

VS.EFACH.NackTtiNum

Multi-mode: None

Feature Name



LTE: None VS.EFACH.DtxTtiNum



LTE: None

Number of TTIs in Which E-FACH Users Have Data to Transmit in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332162

VS.EFACH.Dat aTtiNum

Number of TTIs in Which EFACH Users Have Data to Transmit in a Cell


U

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

Issue 11 (2015–05–30)


284



Unit None


Feature ID

VS.EFACH.DataTtiNum

Multi-mode: None

Feature Name



LTE: None

E-FACH User Throughput at the MAC-ehs Layer in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332161

VS.EFACH.Thr uput

E-FACH User Throughput at the MAC-ehs Layer in a Cell


U

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 EFACH users have HS-DPCCH feedbacks and the traffic volume of initial transmission when EFACH users have no HS-DPCCH feedbacks.

Formula None

Unit bit Issue 11 (2015–05–30)


285




Feature ID

VS.EFACH.Thruput

Multi-mode: None

Feature Name



LTE: None

Average HS-SCCH transmit power of all E-FACH users in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341718

VS.EFACH.Scc hPwrRatio.Mea n

Average HSSCCH transmit power of all EFACH users in a cell


U

50341719

VS.EFACH.Scc hPwrRatio.Max

Maximum HSSCCH transmit power of all EFACH users in a cell


U

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.



286



Unit per mill


Feature ID

VS.EFACH.ScchPwrRatio. Mean

Multi-mode: None

Feature Name



LTE: None VS.EFACH.ScchPwrRatio. Max



LTE: None

Average HS-PDSCH transmit power of all E-FACH users in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341720

VS.EFACH.Pds chPwrRatio.Me an

Average HSPDSCH transmit power of all E-FACH users in a cell


U

50341721

VS.EFACH.Pds chPwrRatio.Ma x

Maximum HSPDSCH transmit power of all E-FACH users in a cell


U

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 Issue 11 (2015–05–30)


287



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


Feature ID

Feature Name

VS.EFACH.PdschPwrRatio. Mean


VS.EFACH.PdschPwrRatio. Max




1.1.12 HSDPA Measurement 2 (HSDPA2.LOCELL) 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.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332175

VS.HSDPA.Pdsch CodeUsed.0

Number of times 0 HS-PDSCH codes are used in a cell


Issue 11 (2015–05–30)


288



Counter ID

Counter Name

Counter Description

Original Release

50332176


Number of times 1 HS-PDSCH code is used in a cell


50332177




50332178




50332179




50332180




50332181




50332182




50332183




50332184




50332185




Issue 11 (2015–05–30)


289



Counter ID

Counter Name

Counter Description

Original Release

50332186




50332187




50332188




50332189




50332190




50341723

VS.HSDPA.UserN um.Mean

Average Number of HSDPA Users in a Cell


50331747

VS.HSDPA.Data.Iu bMacdPdu

Number of MAC-d PDUs received over Iub interfaces in a cell


50332219

VS.HSDPA. 64QAMCfg.Acted. Traffic

Traffic of Mac-ehs PDUs correctly transmitted by 64QAM users in 64QAM mode in a cell


50332193

VS.HSDPA. 64QAMCfg.Traffic

Traffic of Mac-ehs PDUs correctly transmitted by all 64QAM users in a cell


Issue 11 (2015–05–30)


290



Counter ID

Counter Name

Counter Description

Original Release

50332204

VS.HSDPA.FullBu ffer.Throughput.Su mNum.0

Number of samples in which the full buffer throughput of a single HSDPA user is within the range of interval 0


50332205




50332206




50332207




50332208




50332209




50332210




Issue 11 (2015–05–30)


291



Counter ID

Counter Name

Counter Description

Original Release

50332211




50332212




50332213




50332214




50332200

VS.HSDPA.DelayS ensitive.DataOutpu t.Urgency

Traffic of delay sensitive BE services preferentially transmitted by HSDPA users in a cell


50332199

VS.HSDPA.DelayS ensitive.DataOutput

Traffic of delay sensitive BE services transmitted by all HSDPA users in a cell


50332198

VS.HSDPA.Schedu leNum.DelaySensiti ve.Blind

Number of times HSDPA users running delay sensitive BE services are blind scheduled in a cell


Issue 11 (2015–05–30)


292



Counter ID

Counter Name

Counter Description

Original Release

50332197

VS.HSDPA.Schedu leNum.DelaySensitive

Number of times HSDPA users running delay sensitive BE services are scheduled in a cell


50332194

VS.HSDPA.NotSch edule.CQI0

Number of times HSDPA users are not scheduled in a cell due to CQI of 0


50332195

VS.HSDPA.NotSch edule.InvalidCQI

Number of times HSDPA users are not scheduled in a cell due to invalid CQI


50332196

VS.HSDPA.NotSch edule.CMGAP

Number of times HSDPA users within the GAP period in compressed mode are not scheduled in a cell


50332201

VS.HSDPA.Remai nResLimit.ScchCo de

Number of times the next HSDPA user cannot be scheduled due to HS-SCCH insufficiency in a cell


50332202

VS.HSDPA.Remai nResLimit.PdschC ode

Number of times the next HSDPA user cannot be scheduled due to HS-PDSCH insufficiency in a cell


50332203

VS.HSDPA.Remai nResLimit.HSDPA Pwr

Number of times the next HSDPA user cannot be scheduled due to HSDPA power insufficiency in a cell


50332648

VS.HSDPA.FullBu ffer.ThdLimit.Thro ughput.TTINum.0

Total TTIs in Interval 0 for Single HSDPA Users with Throughput Minus Small Data Volume in a Full Buffer


Issue 11 (2015–05–30)


293



Counter ID

Counter Name

Counter Description

Original Release

50332649




50332650




50332651




50332652




50332653




50332654




50332655




Issue 11 (2015–05–30)


294



Counter ID

Counter Name

Counter Description

Original Release

50332656




50332657




50332658




50341748

VS.HSDPA.FullBu ffer.ThdLimit.Thro ughput.Traffic.0

Total data volume in Interval 0 for single HSDPA users with throughput minus the small data volume in a full buffer


50341749




50341750




50341751




Issue 11 (2015–05–30)


295



Counter ID

Counter Name

Counter Description

Original Release

50341752




50341753




50341754




50341755




50341756




50341757




50341758




Issue 11 (2015–05–30)


296



Counter ID

Counter Name

Counter Description

Original Release

50332670

VS.HSDPA.FullBu ffer.ThdLimit.Thro ughputSatisfied.TT INum

Total TTIs in a Full Buffer for Single HSDPA Users with Throughput Minus Small Data Volume Exceeding the Target Threshold


50341759

VS.HSDPA.FullBu ffer.ThdLimit.Thro ughputSatisfied.Tr affic

Total Data Volume in a Full Buffer for Single HSDPA Users with Throughput Minus Small Data Volume Exceeding the Target Threshold


50332192

VS.HSDPAPwrSha re.TtiNum

Number of TTIs within which the HSDPA cell uses shared power



Level-1 Counter

VS.HSDPA.64QAMCfg.Traffic

VS.HSDPA.64QAMCfg.Acted.Traffic

VS.HSDPA.DelaySensitive.DataOutput

VS.HSDPA.DelaySensitive.DataOutput.Urgency

VS.HSDPA.ScheduleNum.DelaySensitive

VS.HSDPA.ScheduleNum.DelaySensitive. Blind

Number of Times Different Quantities of HS-PDSCH Codes Are Used in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332175

VS.HSDPA.Pds chCodeUsed.0

Number of times 0 HSPDSCH codes are used in a cell


U

Issue 11 (2015–05–30)


297



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332176


Number of times 1 HSPDSCH code is used in a cell


U

50332177




U

50332178




U

50332179




U

50332180




U

50332181




U

50332182




U

50332183




U

50332184




U

50332185




U

Issue 11 (2015–05–30)


298



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332186




U

50332187




U

50332188




U

50332189




U

50332190




U

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

Issue 11 (2015–05–30)


299




Feature ID

VS.HSDPA.PdschCodeUsed.0



GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None



Issue 11 (2015–05–30)
















Feature Name



300



Counter Name

Feature ID




GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None



Issue 11 (2015–05–30)
















Feature Name



301



Counter Name

Feature ID


Multi-mode: None

Feature Name



LTE: None VS.HSDPA.PdschCodeUsed.15



LTE: None

Average Number of HSDPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341723

VS.HSDPA.Us erNum.Mean

Average Number of HSDPA Users in a Cell


U

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



302




Feature ID

VS.HSDPA.UserNum.Mean

Multi-mode: None

Feature Name



LTE: None

Number of MAC-d PDUs received over Iub interfaces in a cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50331747

VS.HSDPA.Dat a.IubMacdPdu

Number of MAC-d PDUs received over Iub interfaces in a cell


U

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

Issue 11 (2015–05–30)


303




Feature ID

Feature Name

VS.HSDPA.Data.IubMacdPdu



LTE: None

Traffic of Mac-ehs PDUs Correctly Transmitted by 64QAM Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332219

VS.HSDPA. 64QAMCfg.Act ed.Traffic

Traffic of Macehs PDUs correctly transmitted by 64QAM users in 64QAM mode in a cell


U

50332193

VS.HSDPA. 64QAMCfg.Tra ffic

Traffic of Macehs PDUs correctly transmitted by all 64QAM users in a cell


U


Description

VS.HSDPA.64QAMCfg.Acted.Traffic

This counter measures the traffic of Mac-ehs PDUs correctly transmitted by 64QAM users in 64QAM mode in a cell.

VS.HSDPA.64QAMCfg.Traffic

This counter measures the traffic of Mac-ehs PDUs correctly transmitted by all 64QAM users in a cell.

Issue 11 (2015–05–30)


304



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


Feature ID

VS.HSDPA. 64QAMCfg.Acted.Traffic

Multi-mode: None

Feature Name


Downlink 64QAM DL 64QAM+MIMO

LTE: None VS.HSDPA. 64QAMCfg.Traffic

Multi-mode: None GSM: None UMTS: WRFD-010683 WRFD-010693

Downlink 64QAM DL 64QAM+MIMO

LTE: None

Throughput Distribution of Single HSDPA User in a Full Buffer

Issue 11 (2015–05–30)


305



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332204

VS.HSDPA.Ful lBuffer.Throug hput.SumNum. 0



U

50332205




U

50332206




U

50332207




U

Issue 11 (2015–05–30)


306



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332208




U

50332209




U

50332210




U

50332211




U

50332212




U

Issue 11 (2015–05–30)


307



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332213




U

50332214




U

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, 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. Interval 8 ranges from 10 Mbit/s (included) to 15 Mbit/s. Interval 9 ranges from 15 Mbit/s (included) to 21 Mbit/s. Interval 10 indicates a value greater than or equal to 21 Mbit/s. Issue 11 (2015–05–30)


308



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. Figure 1-11

Formula None

Unit None

Issue 11 (2015–05–30)


309




Feature ID

VS.HSDPA.FullBuffer.Thro ughput.SumNum.0



GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None



Issue 11 (2015–05–30)
















Feature Name



310



Counter Name

Feature ID


Multi-mode: None

Feature Name



LTE: None VS.HSDPA.FullBuffer.Thro ughput.SumNum.8









LTE: None

Traffic of Delay Sensitive BE Services Transmitted by HSDPA Users in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332200

VS.HSDPA.Del aySensitive.Dat aOutput.Urgenc y

Traffic of delay sensitive BE services preferentially transmitted by HSDPA users in a cell


U

Issue 11 (2015–05–30)


311



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332199

VS.HSDPA.Del aySensitive.DataOutput

Traffic of delay sensitive BE services transmitted by all HSDPA users in a cell


U


Description

VS.HSDPA.DelaySensitive.DataOutput.Urgency

This counter measures the traffic of MAC-hs/ MAC-ehs sensitive delay BE services preferentially transmitted by HSDPA users and received with ACKs in a cell. If the waiting delay in the queue buffer for delay sensitive BE services approaches the maximum buffer delay, the BE services are preferentially transmitted at the MAC-hs/ Mac-ehs layer. Delay sensitive BE services are PS interactive and PS background services that are delay sensitive, for example, Skype.

VS.HSDPA.DelaySensitive.DataOutput

This counter measures the total traffic of MAC-hs/MAC-ehs sensitive delay BE services transmitted by all HSDPA users and received with ACKs in a cell. 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 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 counter. 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. Issue 11 (2015–05–30)


312



For an MC-HSDPA user, the corresponding counter is measured in the anchor and supplementary carriers separately.

Formula None

Unit bit


Feature ID

VS.HSDPA.DelaySensitive. DataOutput.Urgency

Multi-mode: None

Feature Name


VoIP Application Management

LTE: None VS.HSDPA.DelaySensitive. DataOutput



LTE: None

Number of Times HSDPA Users Running Delay Sensitive BE Services Are Scheduled in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332198

VS.HSDPA.Sc heduleNum.Del aySensitive.Bli nd

Number of times HSDPA users running delay sensitive BE services are blind scheduled in a cell


U

Issue 11 (2015–05–30)


313



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332197

VS.HSDPA.Sc heduleNum.Del aySensitive

Number of times HSDPA users running delay sensitive BE services are scheduled in a cell


U


Description

VS.HSDPA.ScheduleNum.DelaySensitive. Blind

This counter measures the number of times HSDPA users running delay sensitive BE services are blind scheduled in a cell. Delay sensitive BE services are PS interactive and PS background services that are delay sensitive, for example, Skype.

VS.HSDPA.ScheduleNum.DelaySensitive

This counter measures the number of times HSDPA users running delay sensitive BE services are scheduled in a cell. 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

Issue 11 (2015–05–30)


314




Feature ID

VS.HSDPA.ScheduleNum. DelaySensitive.Blind

Multi-mode: None

Feature Name



LTE: None VS.HSDPA.ScheduleNum. DelaySensitive



LTE: None

Number of Times HSDPA Users Are not Scheduled in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332194

VS.HSDPA.No tSchedule.CQI0

Number of times HSDPA users are not scheduled in a cell due to CQI of 0


U

50332195

VS.HSDPA.No tSchedule.InvalidCQI

Number of times HSDPA users are not scheduled in a cell due to invalid CQI


U

50332196

VS.HSDPA.No tSchedule.CMG AP

Number of times HSDPA users within the GAP period in compressed mode are not scheduled in a cell


U

Issue 11 (2015–05–30)


315




Description

VS.HSDPA.NotSchedule.CQI0

This counter measures the number of times HSDPA users having data to transmit in the full buffer are not scheduled in a cell because CQI is 0. CQI of 0 indicates that the CQI reported by a UE is 0 or uplink synchronization fails and therefore the CQI reported by a UE is not obtained when radio links are established.

VS.HSDPA.NotSchedule.InvalidCQI

This counter measures the number of times HSDPA users having data to transmit in the full buffer are not scheduled in a cell because uplink coverage is poor and a valid CQI cannot be obtained.

VS.HSDPA.NotSchedule.CMGAP

This counter measures the number of times HSDPA users having data to transmit in the full buffer are not scheduled in a cell because the users are within the GAP period in compressed mode.

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 VS.HSDPA.NotSchedule.InvalidCQI 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 uplink coverage is poor and a valid CQI cannot be obtained. The VS.HSDPA.NotSchedule.CMState 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 the user is within the GAP period in compressed mode. 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



316




Feature ID

VS.HSDPA.NotSchedule.C QI0

Multi-mode: None

Feature Name



LTE: None VS.HSDPA.NotSchedule.In validCQI



LTE: None VS.HSDPA.NotSchedule.C MGAP



LTE: None

Number of Times the Next HSDPA User Cannot be Scheduled Due to Resource Insufficiency in a Cell Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332201

VS.HSDPA.Re mainResLimit.S cchCode

Number of times the next HSDPA user cannot be scheduled due to HS-SCCH insufficiency in a cell


U

50332202

VS.HSDPA.Re mainResLimit.P dschCode

Number of times the next HSDPA user cannot be scheduled due to HS-PDSCH insufficiency in a cell


U

Issue 11 (2015–05–30)


317



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332203

VS.HSDPA.Re mainResLimit. HSDPAPwr

Number of times the next HSDPA user cannot be scheduled due to HSDPA power insufficiency in a cell


U


Description

VS.HSDPA.RemainResLimit.ScchCode

This counter measures the number of times the next HSDPA user (including E-FACH users and E-PCH users) in the candidate set cannot be scheduled due to HS-SCCH insufficiency in an HSDPA cell.

VS.HSDPA.RemainResLimit.PdschCode

This counter measures the number of times the next HSDPA user (including E-FACH users and E-PCH users) in the candidate set cannot be scheduled due to HS-PDSCH insufficiency in an HSDPA cell.

VS.HSDPA.RemainResLimit.HSDPAPwr

This counter measures the number of times the next HSDPA user (including E-FACH users and E-PCH users) in the candidate set cannot be scheduled due to HSDPA power insufficiency in an HSDPA cell.

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. Issue 11 (2015–05–30)


318



Formula None

Unit None


Feature ID

VS.HSDPA.RemainResLim it.ScchCode

Multi-mode: None

Feature Name



LTE: None VS.HSDPA.RemainResLim it.PdschCode



LTE: None VS.HSDPA.RemainResLim it.HSDPAPwr



LTE: None

Throughput Distribution of Single HSDPA User in a Full Buffer(by TTIs) Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332648

VS.HSDPA.Ful lBuffer.ThdLim it.Throughput.T TINum.0



U

Issue 11 (2015–05–30)


319



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332649




U

50332650




U

50332651




U

50332652




U

50332653




U

Issue 11 (2015–05–30)


320



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332654




U

50332655




U

50332656




U

50332657




U

50332658




U

Issue 11 (2015–05–30)


321



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. 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. Interval 8 ranges from 10 Mbit/s (included) to 15 Mbit/s. Interval 9 ranges from 15 Mbit/s (included) to 21 Mbit/s. Interval 10 indicates a value greater than or equal to 21 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 ULOCELLRSVDPARA9 in the SET ULOCELLRSVDPARA 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

Issue 11 (2015–05–30)


322




Feature ID

VS.HSDPA.FullBuffer.Thd Limit.Throughput.TTINum. 0










Issue 11 (2015–05–30)


Multi-mode: None

LTE: None VS.HSDPA.FullBuffer.Thd Limit.Throughput.TTINum. 6


Multi-mode: None



Multi-mode: None



Multi-mode: None



Multi-mode: None


Feature Name



323



Counter Name

Feature ID


Multi-mode: None

Feature Name












LTE: None

Throughput Distribution of Single HSDPA User in a Full Buffer(by Data Volume) Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341748

VS.HSDPA.Ful lBuffer.ThdLim it.Throughput.T raffic.0



U

Issue 11 (2015–05–30)


324



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341749




U

50341750




U

50341751




U

50341752




U

50341753




U

Issue 11 (2015–05–30)


325



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341754




U

50341755




U

50341756




U

50341757




U

50341758




U

Issue 11 (2015–05–30)


326



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. Interval 8 ranges from 10 Mbit/s (included) to 15 Mbit/s. Interval 9 ranges from 15 Mbit/s (included) to 21 Mbit/s. Interval 10 indicates a value greater than or equal to 21 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 ULOCELLRSVDPARA9 in the SET ULOCELLRSVDPARA 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 Issue 11 (2015–05–30)


327




Feature ID

VS.HSDPA.FullBuffer.Thd Limit.Throughput.Traffic.0



GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None



Issue 11 (2015–05–30)
















Feature Name



328



Counter Name

Feature ID


Multi-mode: None

Feature Name



LTE: None VS.HSDPA.FullBuffer.Thd Limit.Throughput.Traffic.8









LTE: None

Total TTIs in a Full Buffer for Single HSDPA Users with Throughput Minus Small Data Volume Exceeding the Target Threshold Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332670

VS.HSDPA.Ful lBuffer.ThdLim it.ThroughputSa tisfied.TTINum

Total TTIs in a Full Buffer for Single HSDPA Users with Throughput Minus Small Data Volume Exceeding the Target Threshold


U

Issue 11 (2015–05–30)


329



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 ULOCELLRSVDPARA9 in the SET ULOCELLRSVDPARA 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 ULOCELLRSVDPARA10 in the SET ULOCELLRSVDPARA 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


Feature ID

VS.HSDPA.FullBuffer.Thd Limit.ThroughputSatisfied.T TINum

Multi-mode: None

Feature Name




Issue 11 (2015–05–30)


330



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50341759

VS.HSDPA.Ful lBuffer.ThdLim it.ThroughputSa tisfied.Traffic



U

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 ULOCELLRSVDPARA9 in the SET ULOCELLRSVDPARA 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 ULOCELLRSVDPARA10 in the SET ULOCELLRSVDPARA 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

Issue 11 (2015–05–30)


331




Feature ID

VS.HSDPA.FullBuffer.Thd Limit.ThroughputSatisfied.T raffic

Multi-mode: None

Feature Name



LTE: None

Number of TTIs within which the HSDPA cell uses shared power Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332192

VS.HSDPAPwr Share.TtiNum

Number of TTIs within which the HSDPA cell uses shared power


U

Description This counter measures the number of TTIs within which an HSDPA user queue (including EFACH 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



332




Feature ID

Feature Name

VS.HSDPAPwrShare.TtiNum


HSDPA Inter-Cell Power Sharing

1.2 Measurement of NodeB Performance (NodeB) Overview The object type consists of NodeB-related function subnets to indicate the NodeB status and performance.


FunctionSubSet Name

IUB.NODEB

Iub Measurement per NodeB

TRAFFIC.NODEB

NodeB Hardware Baseband Resource Measurement

NBAP.NODEB

NodeB NBAP Procedure Measurement

NODEBRESERVE.NODEB

NodeB Reserved Counter Measurement

TRAFFIC.TRPIP.NODEB

Iub Transmission Performance Measurement per NodeB

1.2.1 Iub Measurement per NodeB (IUB.NODEB) Overview The function subset measures the traffic and performance on the physical ports of the NodeB that serve the Iub interface.

Issue 11 (2015–05–30)


333



Counters Counter ID

Counter Name

Counter Description

Original Release

50332578

VS.AttRLSETUP. MEAN

The average number of RL Setup Request per second


50332579

VS.AttRLADD.ME AN

The average number of RL Add Request per second


50332580

VS.AttRLRecfg.M EAN

The average number of RL Reconfiguration Preparation Request per second


50332581

VS.DedicMeaRpt. MEAN

The average number of Dedicated Measurement Reporting per second


50332673

VS.ATMUlTotal.1

ATM physical port_1 uplink total bandwidth


50332674

VS.ATMUlMaxUse d.1

ATM physical port_1 uplink maximum used bandwidth


50332675

VS.ATMUlAvgUse d.1

ATM physical port_1 uplink average used bandwidth


50332676

VS.ATMDlTotal.1

ATM physical port_1 downlink total bandwidth


Issue 11 (2015–05–30)


334



Counter ID

Counter Name

Counter Description

Original Release

50332677

VS.ATMDlMaxUse d.1

ATM physical port_1 downlink maximum used bandwidth


50332678

VS.ATMDlAvgUse d.1

ATM physical port_1 downlink average used bandwidth


50332679

VS.IPUlTotal.1

IP physical port_1 uplink total bandwidth

BTS3900 WCDMA: version earlier than V200R011C00

50332680

VS.IPUlMaxUsed.1

IP physical port_1 uplink maximum used bandwidth


50332681

VS.IPUlAvgUsed.1

IP physical port_1 uplink average used bandwidth


50332682

VS.IPDlTotal.1

IP physical port_1 downlink total bandwidth


50332683

VS.IPDlMaxUsed.1

IP physical port_1 downlink maximum used bandwidth


50332684

VS.IPDlAvgUsed.1

IP physical port_1 downlink average used bandwidth


50332685

VS.ATMUlTotal.2



50332686

VS.ATMUlMaxUse d.2



Issue 11 (2015–05–30)


335



Counter ID

Counter Name

Counter Description

Original Release

50332687

VS.ATMUlAvgUse d.2



50332688

VS.ATMDlTotal.2



50332689

VS.ATMDlMaxUse d.2



50332690

VS.ATMDlAvgUse d.2



50332691

VS.IPUlTotal.2



50332692

VS.IPUlMaxUsed.2



50332693

VS.IPUlAvgUsed.2



50332694

VS.IPDlTotal.2



50332695

VS.IPDlMaxUsed.2



50332696

VS.IPDlAvgUsed.2



Issue 11 (2015–05–30)


336



Counter ID

Counter Name

Counter Description

Original Release

50332697

VS.ATMUlTotal.3



50332698

VS.ATMUlMaxUse d.3



50332699

VS.ATMUlAvgUse d.3



50332700

VS.ATMDlTotal.3



50332701

VS.ATMDlMaxUse d.3



50332702

VS.ATMDlAvgUse d.3



50332703

VS.IPUlTotal.3



50332704

VS.IPUlMaxUsed.3



50332705

VS.IPUlAvgUsed.3



50332706

VS.IPDlTotal.3



Issue 11 (2015–05–30)


337



Counter ID

Counter Name

Counter Description

Original Release

50332707

VS.IPDlMaxUsed.3



50332708

VS.IPDlAvgUsed.3



50332709

VS.ATMUlTotal.4

ATM physical port uplink total bandwidth


50332710

VS.ATMUlMaxUse d.4



50332711

VS.ATMUlAvgUse d.4



50332712

VS.ATMDlTotal.4



50332713

VS.ATMDlMaxUse d.4



50332714

VS.ATMDlAvgUse d.4



50332715

VS.IPUlTotal.4



50332716

VS.IPUlMaxUsed.4



Issue 11 (2015–05–30)


338



Counter ID

Counter Name

Counter Description

Original Release

50332717

VS.IPUlAvgUsed.4



50332718

VS.IPDlTotal.4



50332719

VS.IPDlMaxUsed.4



50332720

VS.IPDlAvgUsed.4



50332721

VS.IUB.FlowCtrol. UL.AdjBW.LgcPor t1.Max

IUB logic port_1 maximum UL available bandwidth


50332722

VS.IUB.FlowCtrol. UL.AdjBW.LgcPor t1.Min

IUB logic port_1 minimum UL available bandwidth


50332723

VS.IUB.FlowCtrol. UL.AdjBW.LgcPor t1.Avg

IUB logic port_1 average UL available bandwidth


50332724

VS.IUB.FlowCtrol. DL.AdjBW.LgcPor t1.Max

IUB logic port_1 maximum DL HSDPA available bandwidth


50332725

VS.IUB.FlowCtrol. DL.AdjBW.LgcPor t1.Min

IUB logic port_1 minimum DL HSDPA available bandwidth


50332726

VS.IUB.FlowCtrol. DL.AdjBW.LgcPor t1.Avg

IUB logic port_1 average DL HSDPA available bandwidth


50332727

VS.IUB.FlowCtrol. UL.UpBW.Num.Lg cPort1

IUB logic port_1 available UL bandwidth increase times


Issue 11 (2015–05–30)


339



Counter ID

Counter Name

Counter Description

Original Release

50332728

VS.IUB.FlowCtrol. DL.Delay.UpBW.N um.LgcPort1

IUB logic port_1 DL HSDPA available bandwidth increase times after jitter congestion released


50332729

VS.IUB.FlowCtrol. DL.Drop.UpBW.N um.LgcPort1

IUB logic port_1 DL HSDPA available bandwidth increase times after packet loss congestion released


50332730

VS.IUB.FlowCtrol. UL.DelayCong.Do wnBWNum.LgcPo rt1

IUB logic port_1 available UL bandwidth decrease times for jitter congestion


50332731

VS.IUB.FlowCtrol. DL.DelayCong.Do wnBWNum.LgcPo rt1

IUB logic port_1 DL HSDPA available bandwidth decrease times for jitter congestion


50332732

VS.IUB.FlowCtrol. UL.DropCong.Dow nBWNum.LgcPort 1

IUB logic port_1 available UL bandwidth decrease times for packet loss congestion


50332733

VS.IUB.FlowCtrol. DL.DropCong.Dow nBWNum.LgcPort 1

IUB logic port_1 DL HSDPA available bandwidth decrease times for packet loss congestion


50332734

VS.IUB.FlowCtrol. UL.SendNum.LgcP ort1

IUB logic port_1 Number of UL frames IUB logic port sent successfully


50332735

VS.IUB.FlowCtrol. DL.ReceiveNum.L gcPort1

IUB logic port_1 Number of DL HSDPA frames IUB logic port received


50332736

VS.IUB.FlowCtrol. UL.DropNum.Lgc Port1

IUB logic port_1 Number of lost UL frames


Issue 11 (2015–05–30)


340



Counter ID

Counter Name

Counter Description

Original Release

50332737

VS.IUB.FlowCtrol. DL.DropNum.Lgc Port1

IUB logic port_1 Number of lost DL HSDPA frames


50332738

VS.IUB.FlowCtrol. UL.DelayVara.Lgc Port1.Max

IUB logic port_1 maximum UL delay jitter


50332739

VS.IUB.FlowCtrol. UL.DelayVara.Lgc Port1.Min

IUB logic port_1 minimum UL delay jitter


50332740

VS.IUB.FlowCtrol. UL.DelayVara.Lgc Port1.Avg

IUB logic port_1 average UL delay jitter


50332741

VS.IUB.FlowCtrol. DL.DelayVara.Lgc Port1.Max

IUB logic port_1 maximum DL HSDPA delay jitter


50332742

VS.IUB.FlowCtrol. DL.DelayVara.Lgc Port1.Min

IUB logic port_1 minimum DL HSDPA delay jitter


50332743

VS.IUB.FlowCtrol. DL.DelayVara.Lgc Port1.Avg

IUB logic port_1 average DL HSDPA delay jitter


50332744

VS.IUB.FlowCtrol. UL.CongTime.Lgc Port1

IUB logic port_1 UL congestion duration


50332745

VS.IUB.FlowCtrol. DL.CongTime.Lgc Port1

IUB logic port_1 DL HSDPA congestion duration


50332746

VS.IUB.FlowCtrol. UL.AdjBW.LgcPor t2.Max



50332747

VS.IUB.FlowCtrol. UL.AdjBW.LgcPor t2.Min



50332748

VS.IUB.FlowCtrol. UL.AdjBW.LgcPor t2.Avg



50332749

VS.IUB.FlowCtrol. DL.AdjBW.LgcPor t2.Max



Issue 11 (2015–05–30)


341



Counter ID

Counter Name

Counter Description

Original Release

50332750

VS.IUB.FlowCtrol. DL.AdjBW.LgcPor t2.Min



50332751

VS.IUB.FlowCtrol. DL.AdjBW.LgcPor t2.Avg



50332752

VS.IUB.FlowCtrol. UL.UpBW.Num.Lg cPort2



50332753

VS.IUB.FlowCtrol. DL.Delay.UpBW.N um.LgcPort2



50332754

VS.IUB.FlowCtrol. DL.Drop.UpBW.N um.LgcPort2



50332755

VS.IUB.FlowCtrol. UL.DelayCong.Do wnBWNum.LgcPo rt2



50332756

VS.IUB.FlowCtrol. DL.DelayCong.Do wnBWNum.LgcPo rt2



50332757

VS.IUB.FlowCtrol. UL.DropCong.Dow nBWNum.LgcPort 2



50332758

VS.IUB.FlowCtrol. DL.DropCong.Dow nBWNum.LgcPort 2



Issue 11 (2015–05–30)


342



Counter ID

Counter Name

Counter Description

Original Release

50332759

VS.IUB.FlowCtrol. UL.SendNum.LgcP ort2



50332760

VS.IUB.FlowCtrol. DL.ReceiveNum.L gcPort2



50332761

VS.IUB.FlowCtrol. UL.DropNum.Lgc Port2



50332762

VS.IUB.FlowCtrol. DL.DropNum.Lgc Port2



50332763

VS.IUB.FlowCtrol. UL.DelayVara.Lgc Port2.Max



50332764

VS.IUB.FlowCtrol. UL.DelayVara.Lgc Port2.Min



50332765

VS.IUB.FlowCtrol. UL.DelayVara.Lgc Port2.Avg



50332766

VS.IUB.FlowCtrol. DL.DelayVara.Lgc Port2.Max



50332767

VS.IUB.FlowCtrol. DL.DelayVara.Lgc Port2.Min



50332768

VS.IUB.FlowCtrol. DL.DelayVara.Lgc Port2.Avg



50332769

VS.IUB.FlowCtrol. UL.CongTime.Lgc Port2



50332770

VS.IUB.FlowCtrol. DL.CongTime.Lgc Port2



Issue 11 (2015–05–30)


343



Counter ID

Counter Name

Counter Description

Original Release

50342578

VS.AttRLSETUP. MAX

The max number of RL Setup Request per second


50342579

VS.AttRLADD.MA X

The max number of RL Add Request per second


50342580

VS.AttRLRecfg.M AX

The max number of RL Reconfiguration Preparation Requeset per second


50342581

VS.DedicMeaRpt. MAX

The max number of Dedicated Measurement Reporting per second



Number of RL Setup Request per second Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332578

VS.AttRLSET UP.MEAN

The average number of RL Setup Request per second


U

50342578

VS.AttRLSET UP.MAX

The max number of RL Setup Request per second


U

Description The preceding counters indicate the average and maximum of RL Setup Request per second during a measurement period. Issue 11 (2015–05–30)


344



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


Number of RL Add Request per second Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332579

VS.AttRLADD. MEAN

The average number of RL Add Request per second


U

50342579

VS.AttRLADD. MAX

The max number of RL Add Request per second


U

Description The preceding counters indicate the average and maximum of RL Add Request per second during a measurement period.

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. Issue 11 (2015–05–30)


345



Formula None

Unit None


Number of RL Reconfiguration Preparation Request per second Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332580

VS.AttRLRecfg .MEAN

The average number of RL Reconfiguration Preparation Request per second


U

50342580

VS.AttRLRecfg .MAX

The max number of RL Reconfiguration Preparation Requeset per second


U

Description The preceding counters indicate the average and maximum of RL Reconfiguration Preparation Request per second during a measurement period.

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.



346



Unit None


Number of Dedicated Measurement Reporting per second Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332581

VS.DedicMeaR pt.MEAN

The average number of Dedicated Measurement Reporting per second


U

50342581

VS.DedicMeaR pt.MAX

The max number of Dedicated Measurement Reporting per second


U

Description The preceding counters indicate the average and maximum of Dedicated Measurement Reporting per second during a measurement period.

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



347




Available UL Bandwidth on ATM Physical Ports Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332673

VS.ATMUlTot al.1



U

50332685

VS.ATMUlTot al.2



U

50332697

VS.ATMUlTot al.3



U

50332709

VS.ATMUlTot al.4

ATM physical port uplink total bandwidth


U

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



348




Feature ID

VS.ATMUlTotal.1

Multi-mode: None

Feature Name


VS.ATMUlTotal.2

ATM over E1T1 on Iub Interface ATM over Channelized STM-1/OC-3 on Iub Interface


VS.ATMUlTotal.3



VS.ATMUlTotal.4




Used UL Bandwidth on ATM Physical Ports

Issue 11 (2015–05–30)


349



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332674

VS.ATMUlMa xUsed.1



U

50332675

VS.ATMUlAvg Used.1



U

50332686

VS.ATMUlMa xUsed.2



U

50332687

VS.ATMUlAvg Used.2



U

50332698

VS.ATMUlMa xUsed.3



U

50332699

VS.ATMUlAvg Used.3



U

50332710

VS.ATMUlMa xUsed.4



U

50332711

VS.ATMUlAvg Used.4



U


Issue 11 (2015–05–30)


350



Counter Name

Description

VS.ATMUlMaxUsed.1

For each of these counters, the NodeB takes statistics about the maximum used UL bandwidth on an ATM physical port during a measurement period. The NodeB measures the used UL bandwidth on the physical port every five seconds within a measurement period and then obtains the maximum value. 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-toone relation between each other. These counters are identical in application, since they are all used for traffic measurement at the physical layer.

VS.ATMUlAvgUsed.1

For each of these counters, the NodeB takes statistics about the average used UL bandwidth on an ATM physical port during a measurement period. The NodeB measures the used UL bandwidth on the physical port every five seconds within a measurement period and then calculates the average value. 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-toone relation between each other. These counters are identical in application, since they are all used for traffic measurement at the physical layer.


Formula None



351




Feature ID

VS.ATMUlMaxUsed.1

Multi-mode: None

Feature Name


VS.ATMUlAvgUsed.1



VS.ATMUlMaxUsed.2



VS.ATMUlAvgUsed.2



Issue 11 (2015–05–30)



352



Counter Name

Feature ID

VS.ATMUlMaxUsed.3

Multi-mode: None

Feature Name


VS.ATMUlAvgUsed.3



VS.ATMUlMaxUsed.4



VS.ATMUlAvgUsed.4




Available DL Bandwidth on ATM Physical Ports

Issue 11 (2015–05–30)


353



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332676

VS.ATMDlTot al.1



U

50332688

VS.ATMDlTot al.2



U

50332700

VS.ATMDlTot al.3



U

50332712

VS.ATMDlTot al.4



U

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.


Formula None



354




Feature ID

VS.ATMDlTotal.1

Multi-mode: None

Feature Name


VS.ATMDlTotal.2



VS.ATMDlTotal.3



VS.ATMDlTotal.4




Used DL Bandwidth on ATM Physical Ports

Issue 11 (2015–05–30)


355



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332677

VS.ATMDlMa xUsed.1



U

50332678

VS.ATMDlAvg Used.1



U

50332689

VS.ATMDlMa xUsed.2



U

50332690

VS.ATMDlAvg Used.2



U

50332701

VS.ATMDlMa xUsed.3



U

50332702

VS.ATMDlAvg Used.3



U

50332713

VS.ATMDlMa xUsed.4



U

50332714

VS.ATMDlAvg Used.4



U

Issue 11 (2015–05–30)


356




Description

VS.ATMDlMaxUsed.1

For each of these counters, the NodeB takes statistics about the maximum used DL bandwidth on an ATM physical port during a measurement period. The NodeB measures the used DL bandwidth on the physical port every five seconds within a measurement period and then obtains the maximum value. 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-toone relation between each other. These counters are identical in application, since they are all used for traffic measurement at the physical layer.

VS.ATMDlAvgUsed.1

For each of these counters, the NodeB takes statistics about the average used DL bandwidth on an ATM physical port during a measurement period. The NodeB measures the used DL bandwidth on the physical port every five seconds within a measurement period and then calculates the average value. 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-toone relation between each other. These counters are identical in application, since they are all used for traffic measurement at the physical layer.




357



Unit kbit/s


Feature ID

VS.ATMDlMaxUsed.1

Multi-mode: None

Feature Name


VS.ATMDlAvgUsed.1



VS.ATMDlMaxUsed.2



VS.ATMDlAvgUsed.2



Issue 11 (2015–05–30)



358



Counter Name

Feature ID

VS.ATMDlMaxUsed.3

Multi-mode: None

Feature Name


VS.ATMDlAvgUsed.3



VS.ATMDlMaxUsed.4



VS.ATMDlAvgUsed.4




Available UL Bandwidth on IP Physical Ports

Issue 11 (2015–05–30)


359



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332679

VS.IPUlTotal.1


BTS3900 WCDMA

U

50332691

VS.IPUlTotal.2


BTS3900 WCDMA

U

50332703

VS.IPUlTotal.3


BTS3900 WCDMA

U

50332715

VS.IPUlTotal.4


BTS3900 WCDMA

U

Description For each of the preceding counters, the NodeB takes statistics about the available UL (outgoing from the NodeB) bandwidth of an IP physical port during a measurement period. If the physical port carries on MLPPP group or a PPP link, the value of the counter is the total UL bandwidth of the available MLPPP links in the MLPPP group or the available bandwidth of the PPP link respectively. If the physical port is a ETHTRUNK port or an Ethernet port, the value of the counter depends on the negotiation for the port.If the physical port carries on TUNNEL, the value of the counter is the total available UL bandwidth on current TUNNEL. If rate limitation is set on the port, the value of the counter is the smaller value between the defined upper limit of the rate and the measured available bandwidth. The NodeB can take statistics on these counters for a maximum of four IP 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 oneto-one relation between each other. These counters are identical in application, since they are all used for traffic measurement at the physical layer. Disuse Statement: Counter 50332679 VS.IPUlTotal.1 will be replaced by counter 1542460296 VS.FEGE.TxTotalBW/1542460302 VS.TRUNK.TxTotalBW/1542460300 VS.MP.TxTotalBW/1542460298 VS.PPP.TxTotalBW in later versions. In the current version, counters 50332679 VS.IPUlTotal.1 and 1542460296 VS.FEGE.TxTotalBW/1542460302 VS.TRUNK.TxTotalBW/1542460300 VS.MP.TxTotalBW/1542460298 VS.PPP.TxTotalBW are both valid, and the value of counter 50332679 VS.IPUlTotal.1 is properly reported. Counter 50332679 VS.IPUlTotal.1 will be deleted in later versions. Using counter 50332679 VS.IPUlTotal.1 is not recommended. Counter 50332691 VS.IPUlTotal.2 will be replaced by counter 1542460296 VS.FEGE.TxTotalBW/1542460302 VS.TRUNK.TxTotalBW/1542460300 VS.MP.TxTotalBW/1542460298 VS.PPP.TxTotalBW in later versions. In the current version, counters 50332691 VS.IPUlTotal.2 and 1542460296 VS.FEGE.TxTotalBW/1542460302 Issue 11 (2015–05–30)


360



VS.TRUNK.TxTotalBW/1542460300 VS.MP.TxTotalBW/1542460298 VS.PPP.TxTotalBW are both valid, and the value of counter 50332691 VS.IPUlTotal.2 is properly reported. Counter 50332691 VS.IPUlTotal.2 will be deleted in later versions. Using counter 50332691 VS.IPUlTotal.2 is not recommended. Counter 50332703 VS.IPUlTotal.3 will be replaced by counter 1542460296 VS.FEGE.TxTotalBW/1542460302 VS.TRUNK.TxTotalBW/1542460300 VS.MP.TxTotalBW/1542460298 VS.PPP.TxTotalBW in later versions. In the current version, counters 50332703 VS.IPUlTotal.3 and 1542460296 VS.FEGE.TxTotalBW/1542460302 VS.TRUNK.TxTotalBW/1542460300 VS.MP.TxTotalBW/1542460298 VS.PPP.TxTotalBW are both valid, and the value of counter 50332703 VS.IPUlTotal.3 is properly reported. Counter 50332703 VS.IPUlTotal.3 will be deleted in later versions. Using counter 50332703 VS.IPUlTotal.3 is not recommended. Counter 50332715 VS.IPUlTotal.4 will be replaced by counter 1542460296 VS.FEGE.TxTotalBW/1542460302 VS.TRUNK.TxTotalBW/1542460300 VS.MP.TxTotalBW/1542460298 VS.PPP.TxTotalBW in later versions. In the current version, counters 50332715 VS.IPUlTotal.4 and 1542460296 VS.FEGE.TxTotalBW/1542460302 VS.TRUNK.TxTotalBW/1542460300 VS.MP.TxTotalBW/1542460298 VS.PPP.TxTotalBW are both valid, and the value of counter 50332715 VS.IPUlTotal.4 is properly reported. Counter 50332715 VS.IPUlTotal.4 will be deleted in later versions. Using counter 50332715 VS.IPUlTotal.4 is not recommended.


Formula None

Unit kbit/s


Feature ID

VS.IPUlTotal.1

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-050402 LTE: None VS.IPUlTotal.2

IP Transmission Introduction on Iub Interface


Issue 11 (2015–05–30)



361



Counter Name

Feature ID

VS.IPUlTotal.3

Multi-mode: None

Feature Name



LTE: None VS.IPUlTotal.4



LTE: None

Used UL Bandwidth on IP Physical Ports Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332680

VS.IPUlMaxUs ed.1


BTS3900 WCDMA

U

50332681

VS.IPUlAvgUs ed.1


BTS3900 WCDMA

U

50332692

VS.IPUlMaxUs ed.2


BTS3900 WCDMA

U

50332693

VS.IPUlAvgUs ed.2


BTS3900 WCDMA

U

50332704

VS.IPUlMaxUs ed.3


BTS3900 WCDMA

U

Issue 11 (2015–05–30)


362



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332705

VS.IPUlAvgUs ed.3


BTS3900 WCDMA

U

50332716

VS.IPUlMaxUs ed.4


BTS3900 WCDMA

U

50332717

VS.IPUlAvgUs ed.4


BTS3900 WCDMA

U


Description

VS.IPUlMaxUsed.1

For each of these counters, the NodeB takes statistics about the maximum used UL bandwidth on an IP physical port during a measurement period. The NodeB measures the used UL bandwidth on the physical port every five seconds within a measurement period and then obtains the maximum value. The NodeB can take statistics on these counters for a maximum of four IP 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.

Issue 11 (2015–05–30)


363



Counter Name

Description

VS.IPUlAvgUsed.1

For each of these counters, the NodeB takes statistics about the average used UL bandwidth on an IP physical port during a measurement period. The NodeB measures the used UL bandwidth on the physical port every five seconds within a measurement period and then calculates the average value. The NodeB can take statistics on these counters for a maximum of four IP 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.

Disuse Statement: Counter 50332680 VS.IPUlMaxUsed.1 will be replaced by counter 1542455302 VS.FEGE.TxMaxSpeed/1542460306 VS.TRUNK.TxMaxSpeed/1542455358 VS.MP.TxMaxSpeed/1542455343 VS.PPP.TxMaxSpeed in later versions. In the current version, counters 50332680 VS.IPUlMaxUsed.1 and 1542455302 VS.FEGE.TxMaxSpeed/ 1542460306 VS.TRUNK.TxMaxSpeed/1542455358 VS.MP.TxMaxSpeed/1542455343 VS.PPP.TxMaxSpeed are both valid, and the value of counter 50332680 VS.IPUlMaxUsed.1 is properly reported. Counter 50332680 VS.IPUlMaxUsed.1 will be deleted in later versions. Using counter 50332680 VS.IPUlMaxUsed.1 is not recommended. Counter 50332681 VS.IPUlAvgUsed.1 will be replaced by counter 1542455304 VS.FEGE.TxMeanSpeed/1542460307 VS.TRUNK.TxMeanSpeed/1542455360 VS.MP.TxMeanSpeed/1542455345 VS.PPP.TxMeanSpeed in later versions. In the current version, counters 50332681 VS.IPUlAvgUsed.1 and 1542455304 VS.FEGE.TxMeanSpeed/ 1542460307 VS.TRUNK.TxMeanSpeed/1542455360 VS.MP.TxMeanSpeed/1542455345 VS.PPP.TxMeanSpeed are both valid, and the value of counter 50332681 VS.IPUlAvgUsed.1 is properly reported. Counter 50332681 VS.IPUlAvgUsed.1 will be deleted in later versions. Using counter 50332681 VS.IPUlAvgUsed.1 is not recommended. Counter 50332692 VS.IPUlMaxUsed.2 will be replaced by counter 1542455302 VS.FEGE.TxMaxSpeed/1542460306 VS.TRUNK.TxMaxSpeed/1542455358 VS.MP.TxMaxSpeed/1542455343 VS.PPP.TxMaxSpeed in later versions. In the current version, counters 50332692 VS.IPUlMaxUsed.2 and 1542455302 VS.FEGE.TxMaxSpeed/ 1542460306 VS.TRUNK.TxMaxSpeed/1542455358 VS.MP.TxMaxSpeed/1542455343 VS.PPP.TxMaxSpeed are both valid, and the value of counter 50332692 VS.IPUlMaxUsed.2 is properly reported. Counter 50332692 VS.IPUlMaxUsed.2 will be deleted in later versions. Using counter 50332692 VS.IPUlMaxUsed.2 is not recommended. Counter 50332693 VS.IPUlAvgUsed.2 will be replaced by counter 1542455304 VS.FEGE.TxMeanSpeed/1542460307 VS.TRUNK.TxMeanSpeed/1542455360 VS.MP.TxMeanSpeed/1542455345 VS.PPP.TxMeanSpeed in later versions. In the current Issue 11 (2015–05–30)


364



version, counters 50332693 VS.IPUlAvgUsed.2 and 1542455304 VS.FEGE.TxMeanSpeed/ 1542460307 VS.TRUNK.TxMeanSpeed/1542455360 VS.MP.TxMeanSpeed/1542455345 VS.PPP.TxMeanSpeed are both valid, and the value of counter 50332693 VS.IPUlAvgUsed.2 is properly reported. Counter 50332693 VS.IPUlAvgUsed.2 will be deleted in later versions. Using counter 50332693 VS.IPUlAvgUsed.2 is not recommended. Counter 50332704 VS.IPUlMaxUsed.3 will be replaced by counter 1542455302 VS.FEGE.TxMaxSpeed/1542460306 VS.TRUNK.TxMaxSpeed/1542455358 VS.MP.TxMaxSpeed/1542455343 VS.PPP.TxMaxSpeed in later versions. In the current version, counters 50332704 VS.IPUlMaxUsed.3 and 1542455302 VS.FEGE.TxMaxSpeed/ 1542460306 VS.TRUNK.TxMaxSpeed/1542455358 VS.MP.TxMaxSpeed/1542455343 VS.PPP.TxMaxSpeed are both valid, and the value of counter 50332704 VS.IPUlMaxUsed.3 is properly reported. Counter 50332704 VS.IPUlMaxUsed.3 will be deleted in later versions. Using counter 50332704 VS.IPUlMaxUsed.3 is not recommended. Counter 50332705 VS.IPUlAvgUsed.3 will be replaced by counter 1542455304 VS.FEGE.TxMeanSpeed/1542460307 VS.TRUNK.TxMeanSpeed/1542455360 VS.MP.TxMeanSpeed/1542455345 VS.PPP.TxMeanSpeed in later versions. In the current version, counters 50332705 VS.IPUlAvgUsed.3 and 1542455304 VS.FEGE.TxMeanSpeed/ 1542460307 VS.TRUNK.TxMeanSpeed/1542455360 VS.MP.TxMeanSpeed/1542455345 VS.PPP.TxMeanSpeed are both valid, and the value of counter 50332705 VS.IPUlAvgUsed.3 is properly reported. Counter 50332705 VS.IPUlAvgUsed.3 will be deleted in later versions. Using counter 50332705 VS.IPUlAvgUsed.3 is not recommended. Counter 50332716 VS.IPUlMaxUsed.4 will be replaced by counter 1542455302 VS.FEGE.TxMaxSpeed/1542460306 VS.TRUNK.TxMaxSpeed/1542455358 VS.MP.TxMaxSpeed/1542455343 VS.PPP.TxMaxSpeed in later versions. In the current version, counters 50332716 VS.IPUlMaxUsed.4 and 1542455302 VS.FEGE.TxMaxSpeed/ 1542460306 VS.TRUNK.TxMaxSpeed/1542455358 VS.MP.TxMaxSpeed/1542455343 VS.PPP.TxMaxSpeed are both valid, and the value of counter 50332716 VS.IPUlMaxUsed.4 is properly reported. Counter 50332716 VS.IPUlMaxUsed.4 will be deleted in later versions. Using counter 50332716 VS.IPUlMaxUsed.4 is not recommended. Counter 50332717 VS.IPUlAvgUsed.4 will be replaced by counter 1542455304 VS.FEGE.TxMeanSpeed/1542460307 VS.TRUNK.TxMeanSpeed/1542455360 VS.MP.TxMeanSpeed/1542455345 VS.PPP.TxMeanSpeed in later versions. In the current version, counters 50332717 VS.IPUlAvgUsed.4 and 1542455304 VS.FEGE.TxMeanSpeed/ 1542460307 VS.TRUNK.TxMeanSpeed/1542455360 VS.MP.TxMeanSpeed/1542455345 VS.PPP.TxMeanSpeed are both valid, and the value of counter 50332717 VS.IPUlAvgUsed.4 is properly reported. Counter 50332717 VS.IPUlAvgUsed.4 will be deleted in later versions. Using counter 50332717 VS.IPUlAvgUsed.4 is not recommended.


Formula None



365




Feature ID

VS.IPUlMaxUsed.1

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-050402 LTE: None VS.IPUlAvgUsed.1



VS.IPUlMaxUsed.2



VS.IPUlAvgUsed.2



VS.IPUlMaxUsed.3



VS.IPUlAvgUsed.3



VS.IPUlMaxUsed.4



Issue 11 (2015–05–30)



366



Counter Name

Feature ID

VS.IPUlAvgUsed.4

Multi-mode: None

Feature Name



LTE: None

Available DL Bandwidth on IP Physical Ports Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332682

VS.IPDlTotal.1


BTS3900 WCDMA

U

50332694

VS.IPDlTotal.2


BTS3900 WCDMA

U

50332706

VS.IPDlTotal.3


BTS3900 WCDMA

U

50332718

VS.IPDlTotal.4


BTS3900 WCDMA

U

Description For each of the preceding counters, the NodeB takes statistics about the available DL (incoming to the NodeB) bandwidth of an IP physical port during a measurement period. If the physical port carries on MLPPP group or a PPP link, the value of the counter is the total DL bandwidth of the available MLPPP links in the MLPPP group or the available bandwidth of the PPP link respectively. If the physical port is a ETHTRUNK port or an Ethernet port, the value of the counter depends on the negotiation for the port.If the physical port carries on TUNNEL, the value of the counter is the total available DL bandwidth on current TUNNEL. The NodeB can take statistics on these counters for a maximum of four IP 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. Issue 11 (2015–05–30)


367



Disuse Statement: Counter 50332682 VS.IPDlTotal.1 will be replaced by counter 1542460297 VS.FEGE.RxTotalBW/1542460303 VS.TRUNK.RxTotalBW/1542460301 VS.MP.RxTotalBW/1542460299 VS.PPP.RxTotalBW in later versions. In the current version, counters 50332682 VS.IPDlTotal.1 and 1542460297 VS.FEGE.RxTotalBW/1542460303 VS.TRUNK.RxTotalBW/1542460301 VS.MP.RxTotalBW/1542460299 VS.PPP.RxTotalBW are both valid, and the value of counter 50332682 VS.IPDlTotal.1 is properly reported. Counter 50332682 VS.IPDlTotal.1 will be deleted in later versions. Using counter 50332682 VS.IPDlTotal.1 is not recommended. Counter 50332694 VS.IPDlTotal.2 will be replaced by counter 1542460297 VS.FEGE.RxTotalBW/1542460303 VS.TRUNK.RxTotalBW/1542460301 VS.MP.RxTotalBW/1542460299 VS.PPP.RxTotalBW in later versions. In the current version, counters 50332694 VS.IPDlTotal.2 and 1542460297 VS.FEGE.RxTotalBW/1542460303 VS.TRUNK.RxTotalBW/1542460301 VS.MP.RxTotalBW/1542460299 VS.PPP.RxTotalBW are both valid, and the value of counter 50332694 VS.IPDlTotal.2 is properly reported. Counter 50332694 VS.IPDlTotal.2 will be deleted in later versions. Using counter 50332694 VS.IPDlTotal.2 is not recommended. Counter 50332706 VS.IPDlTotal.3 will be replaced by counter 1542460297 VS.FEGE.RxTotalBW/1542460303 VS.TRUNK.RxTotalBW/1542460301 VS.MP.RxTotalBW/1542460299 VS.PPP.RxTotalBW in later versions. In the current version, counters 50332706 VS.IPDlTotal.3 and 1542460297 VS.FEGE.RxTotalBW/1542460303 VS.TRUNK.RxTotalBW/1542460301 VS.MP.RxTotalBW/1542460299 VS.PPP.RxTotalBW are both valid, and the value of counter 50332706 VS.IPDlTotal.3 is properly reported. Counter 50332706 VS.IPDlTotal.3 will be deleted in later versions. Using counter 50332706 VS.IPDlTotal.3 is not recommended. Counter 50332718 VS.IPDlTotal.4 will be replaced by counter 1542460297 VS.FEGE.RxTotalBW/1542460303 VS.TRUNK.RxTotalBW/1542460301 VS.MP.RxTotalBW/1542460299 VS.PPP.RxTotalBW in later versions. In the current version, counters 50332718 VS.IPDlTotal.4 and 1542460297 VS.FEGE.RxTotalBW/1542460303 VS.TRUNK.RxTotalBW/1542460301 VS.MP.RxTotalBW/1542460299 VS.PPP.RxTotalBW are both valid, and the value of counter 50332718 VS.IPDlTotal.4 is properly reported. Counter 50332718 VS.IPDlTotal.4 will be deleted in later versions. Using counter 50332718 VS.IPDlTotal.4 is not recommended.


Formula None

Unit kbit/s

Issue 11 (2015–05–30)


368




Feature ID

VS.IPDlTotal.1

Multi-mode: None

Feature Name



LTE: None VS.IPDlTotal.2









LTE: None

Used DL Bandwidth on IP Physical Ports Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332683

VS.IPDlMaxUs ed.1


BTS3900 WCDMA

U

50332684

VS.IPDlAvgUs ed.1


BTS3900 WCDMA

U

Issue 11 (2015–05–30)


369



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332695

VS.IPDlMaxUs ed.2


BTS3900 WCDMA

U

50332696

VS.IPDlAvgUs ed.2


BTS3900 WCDMA

U

50332707

VS.IPDlMaxUs ed.3


BTS3900 WCDMA

U

50332708

VS.IPDlAvgUs ed.3


BTS3900 WCDMA

U

50332719

VS.IPDlMaxUs ed.4


BTS3900 WCDMA

U

50332720

VS.IPDlAvgUs ed.4


BTS3900 WCDMA

U


Issue 11 (2015–05–30)


370



Counter Name

Description

VS.IPDlMaxUsed.1

For each of these counters, the NodeB takes statistics about the maximum used DL bandwidth on an IP physical port during a measurement period. The NodeB measures the used DL bandwidth on the physical port every five seconds within a measurement period and then obtains the maximum value. The NodeB can take statistics on these counters for a maximum of four IP 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.

VS.IPDlAvgUsed.1

For each of these counters, the NodeB takes statistics about the average used DL bandwidth on an IP physical port during a measurement period. The NodeB measures the used DL bandwidth on the physical port every five seconds within a measurement period and then calculates the average value. The NodeB can take statistics on these counters for a maximum of four IP 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.

Disuse Statement: Counter 50332683 VS.IPDlMaxUsed.1 will be replaced by counter 1542455305 VS.FEGE.RxMaxSpeed/1542460304 VS.TRUNK.RxMaxSpeed/1542455361 VS.MP.RxMaxSpeed/1542455346 VS.PPP.RxMaxSpeed in later versions. In the current version, counters 50332683 VS.IPDlMaxUsed.1 and 1542455305 VS.FEGE.RxMaxSpeed/ 1542460304 VS.TRUNK.RxMaxSpeed/1542455361 VS.MP.RxMaxSpeed/1542455346 VS.PPP.RxMaxSpeed are both valid, and the value of counter 50332683 VS.IPDlMaxUsed.1 is properly reported. Counter 50332683 VS.IPDlMaxUsed.1 will be deleted in later versions. Using counter 50332683 VS.IPDlMaxUsed.1 is not recommended. Counter 50332684 VS.IPDlAvgUsed.1 will be replaced by counter 1542455307 VS.FEGE.RxMeanSpeed/1542460305 VS.TRUNK.RxMeanSpeed/1542455363 VS.MP.RxMeanSpeed/1542455348 VS.PPP.RxMeanSpeed in later versions. In the current version, counters 50332684 VS.IPDlAvgUsed.1 and 1542455307 VS.FEGE.RxMeanSpeed/ Issue 11 (2015–05–30)


371



1542460305 VS.TRUNK.RxMeanSpeed/1542455363 VS.MP.RxMeanSpeed/1542455348 VS.PPP.RxMeanSpeed are both valid, and the value of counter 50332684 VS.IPDlAvgUsed.1 is properly reported. Counter 50332684 VS.IPDlAvgUsed.1 will be deleted in later versions. Using counter 50332684 VS.IPDlAvgUsed.1 is not recommended. Counter 50332695 VS.IPDlMaxUsed.2 will be replaced by counter 1542455305 VS.FEGE.RxMaxSpeed/1542460304 VS.TRUNK.RxMaxSpeed/1542455361 VS.MP.RxMaxSpeed/1542455346 VS.PPP.RxMaxSpeed in later versions. In the current version, counters 50332695 VS.IPDlMaxUsed.2 and 1542455305 VS.FEGE.RxMaxSpeed/ 1542460304 VS.TRUNK.RxMaxSpeed/1542455361 VS.MP.RxMaxSpeed/1542455346 VS.PPP.RxMaxSpeed are both valid, and the value of counter 50332695 VS.IPDlMaxUsed.2 is properly reported. Counter 50332695 VS.IPDlMaxUsed.2 will be deleted in later versions. Using counter 50332695 VS.IPDlMaxUsed.2 is not recommended. Counter 50332696 VS.IPDlAvgUsed.2 will be replaced by counter 1542455307 VS.FEGE.RxMeanSpeed/1542460305 VS.TRUNK.RxMeanSpeed/1542455363 VS.MP.RxMeanSpeed/1542455348 VS.PPP.RxMeanSpeed in later versions. In the current version, counters 50332696 VS.IPDlAvgUsed.2 and 1542455307 VS.FEGE.RxMeanSpeed/ 1542460305 VS.TRUNK.RxMeanSpeed/1542455363 VS.MP.RxMeanSpeed/1542455348 VS.PPP.RxMeanSpeed are both valid, and the value of counter 50332696 VS.IPDlAvgUsed.2 is properly reported. Counter 50332696 VS.IPDlAvgUsed.2 will be deleted in later versions. Using counter 50332696 VS.IPDlAvgUsed.2 is not recommended. Counter 50332707 VS.IPDlMaxUsed.3 will be replaced by counter 1542455305 VS.FEGE.RxMaxSpeed/1542460304 VS.TRUNK.RxMaxSpeed/1542455361 VS.MP.RxMaxSpeed/1542455346 VS.PPP.RxMaxSpeed in later versions. In the current version, counters 50332707 VS.IPDlMaxUsed.3 and 1542455305 VS.FEGE.RxMaxSpeed/ 1542460304 VS.TRUNK.RxMaxSpeed/1542455361 VS.MP.RxMaxSpeed/1542455346 VS.PPP.RxMaxSpeed are both valid, and the value of counter 50332707 VS.IPDlMaxUsed.3 is properly reported. Counter 50332707 VS.IPDlMaxUsed.3 will be deleted in later versions. Using counter 50332707 VS.IPDlMaxUsed.3 is not recommended. Counter 50332708 VS.IPDlAvgUsed.3 will be replaced by counter 1542455307 VS.FEGE.RxMeanSpeed/1542460305 VS.TRUNK.RxMeanSpeed/1542455363 VS.MP.RxMeanSpeed/1542455348 VS.PPP.RxMeanSpeed in later versions. In the current version, counters 50332708 VS.IPDlAvgUsed.3 and 1542455307 VS.FEGE.RxMeanSpeed/ 1542460305 VS.TRUNK.RxMeanSpeed/1542455363 VS.MP.RxMeanSpeed/1542455348 VS.PPP.RxMeanSpeed are both valid, and the value of counter 50332708 VS.IPDlAvgUsed.3 is properly reported. Counter 50332708 VS.IPDlAvgUsed.3 will be deleted in later versions. Using counter 50332708 VS.IPDlAvgUsed.3 is not recommended. Counter 50332719 VS.IPDlMaxUsed.4 will be replaced by counter 1542455305 VS.FEGE.RxMaxSpeed/1542460304 VS.TRUNK.RxMaxSpeed/1542455361 VS.MP.RxMaxSpeed/1542455346 VS.PPP.RxMaxSpeed in later versions. In the current version, counters 50332719 VS.IPDlMaxUsed.4 and 1542455305 VS.FEGE.RxMaxSpeed/ 1542460304 VS.TRUNK.RxMaxSpeed/1542455361 VS.MP.RxMaxSpeed/1542455346 VS.PPP.RxMaxSpeed are both valid, and the value of counter 50332719 VS.IPDlMaxUsed.4 is properly reported. Counter 50332719 VS.IPDlMaxUsed.4 will be deleted in later versions. Using counter 50332719 VS.IPDlMaxUsed.4 is not recommended. Counter 50332720 VS.IPDlAvgUsed.4 will be replaced by counter 1542455307 VS.FEGE.RxMeanSpeed/1542460305 VS.TRUNK.RxMeanSpeed/1542455363 VS.MP.RxMeanSpeed/1542455348 VS.PPP.RxMeanSpeed in later versions. In the current version, counters 50332720 VS.IPDlAvgUsed.4 and 1542455307 VS.FEGE.RxMeanSpeed/ Issue 11 (2015–05–30)


372



1542460305 VS.TRUNK.RxMeanSpeed/1542455363 VS.MP.RxMeanSpeed/1542455348 VS.PPP.RxMeanSpeed are both valid, and the value of counter 50332720 VS.IPDlAvgUsed.4 is properly reported. Counter 50332720 VS.IPDlAvgUsed.4 will be deleted in later versions. Using counter 50332720 VS.IPDlAvgUsed.4 is not recommended.


Formula None

Unit kbit/s


Feature ID

VS.IPDlMaxUsed.1

Multi-mode: None

Feature Name

GSM: None UMTS: WRFD-050402 LTE: None VS.IPDlAvgUsed.1



VS.IPDlMaxUsed.2



VS.IPDlAvgUsed.2



Issue 11 (2015–05–30)



373



Counter Name

Feature ID

VS.IPDlMaxUsed.3

Multi-mode: None

Feature Name



LTE: None VS.IPDlAvgUsed.3



LTE: None VS.IPDlMaxUsed.4



LTE: None VS.IPDlAvgUsed.4



LTE: None

IUB logic port available UL bandwidth Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332721

VS.IUB.FlowCt rol.UL.AdjBW. LgcPort1.Max


BTS3900 WCDMA

U

50332722

VS.IUB.FlowCt rol.UL.AdjBW. LgcPort1.Min


BTS3900 WCDMA

U

Issue 11 (2015–05–30)


374



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332723

VS.IUB.FlowCt rol.UL.AdjBW. LgcPort1.Avg


BTS3900 WCDMA

U

50332746

VS.IUB.FlowCt rol.UL.AdjBW. LgcPort2.Max


BTS3900 WCDMA

U

50332747

VS.IUB.FlowCt rol.UL.AdjBW. LgcPort2.Min


BTS3900 WCDMA

U

50332748

VS.IUB.FlowCt rol.UL.AdjBW. LgcPort2.Avg


BTS3900 WCDMA

U

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:

Issue 11 (2015–05–30)


375



Counter Name

Description

VS.IUB.FlowCtrol.UL.AdjBW.LgcPort1.M ax

The NodeB adjusts the UL port bandwidth according to the congestion indicator sent by the RNC, The NodeB calculates the UL available bandwidth of the physical layer per five seconds, VS.IUB.FlowCtrol.UL.AdjBW.LgcPort.Ma x is the maximum value of available bandwidth of the UL physical layer.

VS.IUB.FlowCtrol.UL.AdjBW.LgcPort1.M in

The NodeB adjusts the UL port bandwidth according to the congestion indicator sent by the RNC, The NodeB calculates the UL available bandwidth of the physical layer per five seconds, VS.IUB.FlowCtrol.UL.AdjBW.LgcPort.Mi n is the minimum value of the available bandwidth of the UL physical layer.

VS.IUB.FlowCtrol.UL.AdjBW.LgcPort1.A vg

The NodeB adjusts the UL port bandwidth according to the congestion indicator sent by the RNC, The NodeB calculates the UL available bandwidth of the physical layer per five seconds, The collected values of available bandwidth in a statistics period are accumulated and recorded as A, and the number of calculation times in a statistics period is recorded as B. Then, VS.IUB.FlowCtrol.UL.AdjBW.LgcPort.Av g = A/B.

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 Issue 11 (2015–05–30)


376



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


Feature ID

VS.IUB.FlowCtrol.UL.Adj BW.LgcPort1.Max


VS.IUB.FlowCtrol.UL.Adj BW.LgcPort1.Min

GSM: None LTE: None

HSUPA Iub Flow Control in Case of Iub Congestion


Issue 11 (2015–05–30)



VS.IUB.FlowCtrol.UL.Adj BW.LgcPort1.Avg

Feature Name



377



Counter Name

Feature ID

VS.IUB.FlowCtrol.UL.Adj BW.LgcPort2.Max

Multi-mode: None

Feature Name



LTE: None VS.IUB.FlowCtrol.UL.Adj BW.LgcPort2.Min



LTE: None VS.IUB.FlowCtrol.UL.Adj BW.LgcPort2.Avg



LTE: None

IUB logic port available DL HSDPA bandwidth Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332724

VS.IUB.FlowCt rol.DL.AdjBW. LgcPort1.Max


BTS3900 WCDMA

U

50332725

VS.IUB.FlowCt rol.DL.AdjBW. LgcPort1.Min


BTS3900 WCDMA

U

50332726

VS.IUB.FlowCt rol.DL.AdjBW. LgcPort1.Avg


BTS3900 WCDMA

U

Issue 11 (2015–05–30)


378



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332749

VS.IUB.FlowCt rol.DL.AdjBW. LgcPort2.Max


BTS3900 WCDMA

U

50332750

VS.IUB.FlowCt rol.DL.AdjBW. LgcPort2.Min


BTS3900 WCDMA

U

50332751

VS.IUB.FlowCt rol.DL.AdjBW. LgcPort2.Avg


BTS3900 WCDMA

U

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:

Issue 11 (2015–05–30)


379



Counter Name

Description

VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.M ax

When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB adjusts the available bandwidth of HSDPA according to the result of internal congestion statistics, and it calculates the available bandwidth of HSDPA per five seconds. When the STATIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB calculates the available bandwidth of HSDPA according to the following formula: Available bandwidth of HSDPA = Total physical bandwidth * Coefficient. (The coefficient is 0.8 in ATM mode and 0.9 in IP mode.) The NodeB calculates the available bandwidth of HSDPA per five seconds. When other algorithms are used, the base station reports 0 as the statistics value. VS.IUB.FlowCtrol.DL.AdjBW.LgcPort.Ma x is the collected maximum value of the available DL MAC-HS layer bandwidth. The DL statistics is valid only in the complete sharing mode of configured bandwidth. The complete sharing mode of configured bandwidth is enabled when the following requirement is met: Bandwidth configured for each type of PATH (for example RT and NRT) > Total physical bandwidth x 90%.

Issue 11 (2015–05–30)


380



Counter Name

Description

VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.M in

When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB adjusts the available bandwidth of HSDPA according to the result of internal congestion statistics, and it calculates the available bandwidth of HSDPA per five seconds. When the STATIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB calculates the available bandwidth of HSDPA according to the following formula: Available bandwidth of HSDPA = Total physical bandwidth * Coefficient. (The coefficient is 0.8 in ATM mode and 0.9 in IP mode.) The NodeB calculates the available bandwidth of HSDPA per five seconds. When other algorithms are used, the base station reports 0 as the statistics value. VS.IUB.FlowCtrol.DL.AdjBW.LgcPort.Mi n is the collected minimum value of the available DL MAC-HS layer bandwidth. The DL statistics is valid only in the complete sharing mode of configured bandwidth. The complete sharing mode of configured bandwidth is enabled when the following requirement is met: Bandwidth configured for each type of PATH (for example RT and NRT) > Total physical bandwidth x 90%.

Issue 11 (2015–05–30)


381



Counter Name

Description

VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.A vg

When the DYNAMIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB adjusts the available bandwidth of HSDPA according to the result of internal congestion statistics, and it calculates the available bandwidth of HSDPA per five seconds. When the STATIC_BW_SHAPING algorithm of the NodeB is enabled, the NodeB calculates the available bandwidth of HSDPA according to the following formula: Available bandwidth of HSDPA = Total physical bandwidth * Coefficient. (The coefficient is 0.8 in ATM mode and 0.9 in IP mode.) The NodeB calculates the available bandwidth of HSDPA per five seconds. When other algorithms are used, the base station reports 0 as the statistics value. The collected values of available bandwidth of the DL MAC-HS layer in a statistics period are accumulated and recorded as A, and the number of calculation times is recorded as B. Then, VS.IUB.FlowCtrol.DL.AdjBW.LgcPort.Av g = A/B. The DL statistics is valid only in the complete sharing mode of configured bandwidth. The complete sharing mode of configured bandwidth is enabled when the following requirement is met: Bandwidth configured for each type of PATH (for example RT and NRT) > Total physical bandwidth x 90%.

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. In the current version, either this counter VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Avg or the VS.RscGroup.FlowCtrol.DL.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.DL.AdjBW.Avg counter is used. Issue 11 (2015–05–30)


382



In the current version, either this counter VS.IUB.FlowCtrol.DL.AdjBW.LgcPort2.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.LgcPort2.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. In the current version, either this counter VS.IUB.FlowCtrol.DL.AdjBW.LgcPort2.Avg or the VS.RscGroup.FlowCtrol.DL.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.DL.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. 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


Feature ID

VS.IUB.FlowCtrol.DL.Adj BW.LgcPort1.Max

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Adj BW.LgcPort1.Min


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Adj BW.LgcPort1.Avg


HSDPA Flow Control

LTE: None

Issue 11 (2015–05–30)


383



Counter Name

Feature ID

VS.IUB.FlowCtrol.DL.Adj BW.LgcPort2.Max

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Adj BW.LgcPort2.Min


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Adj BW.LgcPort2.Avg


HSDPA Flow Control

LTE: None

IUB logic port available UL bandwidth increase times Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332727

VS.IUB.FlowCt rol.UL.UpBW. Num.LgcPort1


BTS3900 WCDMA

U

50332752

VS.IUB.FlowCt rol.UL.UpBW. Num.LgcPort2


BTS3900 WCDMA

U

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 Issue 11 (2015–05–30)


384



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.


Formula None

Unit None


Feature ID

VS.IUB.FlowCtrol.UL.UpB W.Num.LgcPort1


VS.IUB.FlowCtrol.UL.UpB W.Num.LgcPort2

Feature Name




IUB logic port DL HSDPA available bandwidth increase times after jitter congestion released

Issue 11 (2015–05–30)


385



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332728

VS.IUB.FlowCt rol.DL.Delay.U pBW.Num.Lgc Port1


BTS3900 WCDMA

U

50332753

VS.IUB.FlowCt rol.DL.Delay.U pBW.Num.Lgc Port2


BTS3900 WCDMA

U

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: In the current version, either this counter VS.IUB.FlowCtrol.DL.Delay.UpBW.Num.LgcPort1 or the VS.RscGroup.FlowCtrol.DL.Delay.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.DL.Delay.UpBW.Num counter is used. In the current version, either this counter VS.IUB.FlowCtrol.DL.Delay.UpBW.Num.LgcPort2 or the VS.RscGroup.FlowCtrol.DL.Delay.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.DL.Delay.UpBW.Num counter is used.

Measurement Points For the preceding counters, the NodeB takes statistics in each scheduling period. Issue 11 (2015–05–30)


386



Formula None

Unit None


Feature ID

VS.IUB.FlowCtrol.DL.Dela y.UpBW.Num.LgcPort1

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Dela y.UpBW.Num.LgcPort2


HSDPA Flow Control

LTE: None

IUB logic port DL HSDPA available bandwidth increase times after packet loss congestion released Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332729

VS.IUB.FlowCt rol.DL.Drop.Up BW.Num.LgcP ort1


BTS3900 WCDMA

U

Issue 11 (2015–05–30)


387



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332754

VS.IUB.FlowCt rol.DL.Drop.Up BW.Num.LgcP ort2


BTS3900 WCDMA

U

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: In the current version, either this counter VS.IUB.FlowCtrol.DL.Drop.UpBW.Num.LgcPort1 or the VS.RscGroup.FlowCtrol.DL.Drop.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.DL.Drop.UpBW.Num counter is used. In the current version, either this counter VS.IUB.FlowCtrol.DL.Drop.UpBW.Num.LgcPort2 or the VS.RscGroup.FlowCtrol.DL.Drop.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.DL.Drop.UpBW.Num counter is used.


Formula None

Unit None

Issue 11 (2015–05–30)


388




Feature ID

VS.IUB.FlowCtrol.DL.Drop .UpBW.Num.LgcPort1

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Drop .UpBW.Num.LgcPort2


HSDPA Flow Control

LTE: None

IUB logic port available UL bandwidth decrease times for jitter congestion Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332730

VS.IUB.FlowCt rol.UL.DelayCo ng.DownBWNu m.LgcPort1


BTS3900 WCDMA

U

50332755

VS.IUB.FlowCt rol.UL.DelayCo ng.DownBWNu m.LgcPort2


BTS3900 WCDMA

U

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 Issue 11 (2015–05–30)


389



VS.RscGroup.FlowCtrol.UL.DelayCong.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.UL.DelayCong.DownBWNum counter is used. In the current version, either this counter VS.IUB.FlowCtrol.UL.DelayCong.DownBWNum.LgcPort2 or the VS.RscGroup.FlowCtrol.UL.DelayCong.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.UL.DelayCong.DownBWNum counter is used.


Formula None

Unit None


Feature ID

VS.IUB.FlowCtrol.UL.Dela yCong.DownBWNum.LgcP ort1


VS.IUB.FlowCtrol.UL.Dela yCong.DownBWNum.LgcP ort2

Feature Name




IUB logic port DL HSDPA available bandwidth decrease times for jitter congestion

Issue 11 (2015–05–30)


390



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332731

VS.IUB.FlowCt rol.DL.DelayCo ng.DownBWNu m.LgcPort1


BTS3900 WCDMA

U

50332756

VS.IUB.FlowCt rol.DL.DelayCo ng.DownBWNu m.LgcPort2


BTS3900 WCDMA

U

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: In the current version, either this counter VS.IUB.FlowCtrol.DL.DelayCong.DownBWNum.LgcPort1 or the VS.RscGroup.FlowCtrol.DL.DelayCong.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.DelayCong.DownBWNum counter is used. In the current version, either this counter VS.IUB.FlowCtrol.DL.DelayCong.DownBWNum.LgcPort2 or the VS.RscGroup.FlowCtrol.DL.DelayCong.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.DelayCong.DownBWNum counter is used.

Issue 11 (2015–05–30)


391




Formula None

Unit None


Feature ID

VS.IUB.FlowCtrol.DL.Dela yCong.DownBWNum.LgcP ort1

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Dela yCong.DownBWNum.LgcP ort2


HSDPA Flow Control

LTE: None

IUB logic port available UL bandwidth decrease times for packet loss congestion Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332732

VS.IUB.FlowCt rol.UL.DropCo ng.DownBWNu m.LgcPort1


BTS3900 WCDMA

U

50332757

VS.IUB.FlowCt rol.UL.DropCo ng.DownBWNu m.LgcPort2


BTS3900 WCDMA

U

Issue 11 (2015–05–30)


392



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: In the current version, either this counter VS.IUB.FlowCtrol.UL.DropCong.DownBWNum.LgcPort1 or the VS.RscGroup.FlowCtrol.UL.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.UL.DropCong.DownBWNum counter is used. In the current version, either this counter VS.IUB.FlowCtrol.UL.DropCong.DownBWNum.LgcPort2 or the VS.RscGroup.FlowCtrol.UL.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.UL.DropCong.DownBWNum counter is used.


Formula None

Unit None


Feature ID

VS.IUB.FlowCtrol.UL.Drop Cong.DownBWNum.LgcPo rt1


Issue 11 (2015–05–30)

Feature Name



393



Counter Name

Feature ID

VS.IUB.FlowCtrol.UL.Drop Cong.DownBWNum.LgcPo rt2

Multi-mode: None

Feature Name



LTE: None

IUB logic port DL HSDPA available bandwidth decrease times for packet loss congestion Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332733

VS.IUB.FlowCt rol.DL.DropCo ng.DownBWNu m.LgcPort1


BTS3900 WCDMA

U

50332758

VS.IUB.FlowCt rol.DL.DropCo ng.DownBWNu m.LgcPort2


BTS3900 WCDMA

U

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: Issue 11 (2015–05–30)


394



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 use. In a later version , only the VS.RscGroup.FlowCtrol.DL.DropCong.DownBWNum counter is used.


Formula None

Unit None


Feature ID

VS.IUB.FlowCtrol.DL.Drop Cong.DownBWNum.LgcPo rt1

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Drop Cong.DownBWNum.LgcPo rt2


HSDPA Flow Control

LTE: None

Number of UL frames IUB logic port sent successfully

Issue 11 (2015–05–30)


395



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332734

VS.IUB.FlowCt rol.UL.SendNu m.LgcPort1


BTS3900 WCDMA

U

50332759

VS.IUB.FlowCt rol.UL.SendNu m.LgcPort2


BTS3900 WCDMA

U

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: In the current version , either this counter VS.IUB.FlowCtrol.UL.SendNum.LgcPort1 or the VS.RscGroup.FlowCtrol.UL.SendNum 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.SendNum counter is used. In the current version, either this counter VS.IUB.FlowCtrol.UL.SendNum.LgcPort2 or the VS.RscGroup.FlowCtrol.UL.SendNum 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.SendNum counter is used.


Formula None



396




Feature ID

VS.IUB.FlowCtrol.UL.Send Num.LgcPort1

Multi-mode: None

Feature Name



LTE: None VS.IUB.FlowCtrol.UL.Send Num.LgcPort2



LTE: None

Number of DL HSDPA frames IUB logic port received Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332735

VS.IUB.FlowCt rol.DL.Receive Num.LgcPort1


BTS3900 WCDMA

U

50332760

VS.IUB.FlowCt rol.DL.Receive Num.LgcPort2


BTS3900 WCDMA

U

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. Issue 11 (2015–05–30)


397



Disuse Statement: In the current version , either this counter VS.IUB.FlowCtrol.DL.ReceiveNum.LgcPort1 or the VS.RscGroup.FlowCtrol.DL.ReceiveNum 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.ReceiveNum counter is used. In the current version, either this counter VS.IUB.FlowCtrol.DL.ReceiveNum.LgcPort2 or the VS.RscGroup.FlowCtrol.DL.ReceiveNum 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.ReceiveNum counter is used.


Formula None

Unit None


Feature ID

VS.IUB.FlowCtrol.DL.Rece iveNum.LgcPort1

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Rece iveNum.LgcPort2


HSDPA Flow Control

LTE: None

Number of lost UL frames

Issue 11 (2015–05–30)


398



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332736

VS.IUB.FlowCt rol.UL.DropNu m.LgcPort1


BTS3900 WCDMA

U

50332761

VS.IUB.FlowCt rol.UL.DropNu m.LgcPort2


BTS3900 WCDMA

U

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: In the current version , either this counter VS.IUB.FlowCtrol.UL.DropNum.LgcPort1 or the VS.RscGroup.FlowCtrol.UL.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.UL.DropNum counter is used. In the current version, either this counter VS.IUB.FlowCtrol.UL.DropNum.LgcPort2 or the VS.RscGroup.FlowCtrol.UL.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.UL.DropNum counter is used.


Formula None

Unit None

Issue 11 (2015–05–30)


399




Feature ID

VS.IUB.FlowCtrol.UL.Drop Num.LgcPort1

Multi-mode: None

Feature Name



LTE: None VS.IUB.FlowCtrol.UL.Drop Num.LgcPort2



LTE: None

Number of lost DL HSDPA frames Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332737

VS.IUB.FlowCt rol.DL.DropNu m.LgcPort1


BTS3900 WCDMA

U

50332762

VS.IUB.FlowCt rol.DL.DropNu m.LgcPort2


BTS3900 WCDMA

U

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 Issue 11 (2015–05–30)


400



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.


Formula None

Unit None


Feature ID

VS.IUB.FlowCtrol.DL.Drop Num.LgcPort1

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Drop Num.LgcPort2


HSDPA Flow Control

LTE: None

IUB logic port UL delay jitter Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332738

VS.IUB.FlowCt rol.UL.DelayVa ra.LgcPort1.Ma x


BTS3900 WCDMA

U

Issue 11 (2015–05–30)


401



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332739

VS.IUB.FlowCt rol.UL.DelayVa ra.LgcPort1.Mi n


BTS3900 WCDMA

U

50332740

VS.IUB.FlowCt rol.UL.DelayVa ra.LgcPort1.Av g


BTS3900 WCDMA

U

50332763

VS.IUB.FlowCt rol.UL.DelayVa ra.LgcPort2.Ma x


BTS3900 WCDMA

U

50332764

VS.IUB.FlowCt rol.UL.DelayVa ra.LgcPort2.Mi n


BTS3900 WCDMA

U

50332765

VS.IUB.FlowCt rol.UL.DelayVa ra.LgcPort2.Av g


BTS3900 WCDMA

U

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: Counter Name

Description

VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1 .Max

The NodeB calculates the UL jitter per five seconds. VS.IUB.FlowCtrol.UL.DelayVara.LgcPort. Max is the collected maximum value of UL jitter.

VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1 .Min

The NodeB calculates the UL jitter per five seconds. VS.IUB.FlowCtrol.UL.DelayVara.LgcPort. Min is the collected minimum value of UL jitter.

Issue 11 (2015–05–30)


402



Counter Name

Description

VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1 .Avg

The NodeB calculates the UL jitter per five seconds. All collected values of UL jitter in a statistics period are accumulated and recorded as A, and the number of calculation times is recorded as B. Then, VS.IUB.FlowCtrol.UL.DelayVara.LgcPort. Avg = A/B.

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.


Formula None

Issue 11 (2015–05–30)


403



Unit ms


Feature ID

VS.IUB.FlowCtrol.UL.Dela yVara.LgcPort1.Max


VS.IUB.FlowCtrol.UL.Dela yVara.LgcPort1.Min

GSM: None LTE: None

GSM: None LTE: None

GSM: None LTE: None



VS.IUB.FlowCtrol.UL.Dela yVara.LgcPort2.Avg



VS.IUB.FlowCtrol.UL.Dela yVara.LgcPort2.Min



VS.IUB.FlowCtrol.UL.Dela yVara.LgcPort2.Max



VS.IUB.FlowCtrol.UL.Dela yVara.LgcPort1.Avg

Feature Name




IUB logic port DL HSDPA delay jitter Issue 11 (2015–05–30)


404



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332741

VS.IUB.FlowCt rol.DL.DelayVa ra.LgcPort1.Ma x


BTS3900 WCDMA

U

50332742

VS.IUB.FlowCt rol.DL.DelayVa ra.LgcPort1.Mi n


BTS3900 WCDMA

U

50332743

VS.IUB.FlowCt rol.DL.DelayVa ra.LgcPort1.Av g


BTS3900 WCDMA

U

50332766

VS.IUB.FlowCt rol.DL.DelayVa ra.LgcPort2.Ma x


BTS3900 WCDMA

U

50332767

VS.IUB.FlowCt rol.DL.DelayVa ra.LgcPort2.Mi n


BTS3900 WCDMA

U

50332768

VS.IUB.FlowCt rol.DL.DelayVa ra.LgcPort2.Av g


BTS3900 WCDMA

U

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:

Issue 11 (2015–05–30)


405



Counter Name

Description

VS.IUB.FlowCtrol.DL.DelayVara.LgcPort1 .Max

When the DYNAMIC_BW_SHAPING algorithm is enabled, the NodeB calculates the DL jitter per five seconds. When other algorithms are used, the NodeB reports 0 as the statistics value. VS.IUB.FlowCtrol.DL.DelayVara.LgcPort. Max is the collected maximum value of DL jitter.

VS.IUB.FlowCtrol.DL.DelayVara.LgcPort1 .Min

When the DYNAMIC_BW_SHAPING algorithm is enabled, the NodeB calculates the DL jitter per five seconds. When other algorithms are used, the NodeB reports 0 as the statistics value. VS.IUB.FlowCtrol.DL.DelayVara.LgcPort. Min is the collected minimum value of DL jitter.

VS.IUB.FlowCtrol.DL.DelayVara.LgcPort1 .Avg

When the DYNAMIC_BW_SHAPING algorithm is enabled, the NodeB calculates the DL jitter per five seconds. When other algorithms are used, the NodeB reports 0 as the statistics value. All collected values of DL jitter in a statistics are accumulated and recorded as A, and the number of calculation times is recorded as B. Then, VS.IUB.FlowCtrol.DL.DelayVara.LgcPort. Avg = A/B.

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. Issue 11 (2015–05–30)


406



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.


Formula None

Unit ms


Feature ID

VS.IUB.FlowCtrol.DL.Dela yVara.LgcPort1.Max

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Dela yVara.LgcPort1.Min


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Dela yVara.LgcPort1.Avg


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Dela yVara.LgcPort2.Max


HSDPA Flow Control

LTE: None

Issue 11 (2015–05–30)


407



Counter Name

Feature ID

VS.IUB.FlowCtrol.DL.Dela yVara.LgcPort2.Min

Multi-mode: None

Feature Name


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Dela yVara.LgcPort2.Avg


HSDPA Flow Control

LTE: None

IUB logic port UL congestion duration Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332744

VS.IUB.FlowCt rol.UL.CongTi me.LgcPort1


BTS3900 WCDMA

U

50332769

VS.IUB.FlowCt rol.UL.CongTi me.LgcPort2


BTS3900 WCDMA

U

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 Issue 11 (2015–05–30)


408



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.


Formula None

Unit s


Feature ID

VS.IUB.FlowCtrol.UL.Con gTime.LgcPort1


VS.IUB.FlowCtrol.UL.Con gTime.LgcPort2

Feature Name




IUB logic port DL HSDPA congestion duration

Issue 11 (2015–05–30)


409



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332745

VS.IUB.FlowCt rol.DL.CongTi me.LgcPort1


BTS3900 WCDMA

U

50332770

VS.IUB.FlowCt rol.DL.CongTi me.LgcPort2


BTS3900 WCDMA

U

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.




410



Unit s


Feature ID

Feature Name

VS.IUB.FlowCtrol.DL.Con gTime.LgcPort1


HSDPA Flow Control

LTE: None VS.IUB.FlowCtrol.DL.Con gTime.LgcPort2


HSDPA Flow Control

LTE: None

1.2.2 NodeB Hardware Baseband Resource Measurement (TRAFFIC.NODEB) Overview The function subset indicates the availability of the hardware resources at the NodeB side.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332565

VS.HW.DLCredit Available

Number of Available Downlink Hardware CEs


50332566

VS.HW.ULCredit Available

Number of Available Uplink Hardware CEs



Number of Available Downlink Hardware CEs Issue 11 (2015–05–30)


411



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332565

VS.HW.DLCre ditAvailable

Number of Available Downlink Hardware CEs


U

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


Feature ID

VS.HW.DLCreditAvailable

Multi-mode: None

Feature Name


Admission Control

LTE: None


Issue 11 (2015–05–30)


412



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332566

VS.HW.ULCre ditAvailable



U

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


Feature ID

VS.HW.ULCreditAvailable

Multi-mode: None

Feature Name


Admission Control

LTE: None

1.2.3 NodeB NBAP Procedure Measurement (NBAP.NODEB) Overview The function subset refers to the measurement of the load and status during the NodeB NBAP procedure.

Issue 11 (2015–05–30)


413



Counters Counter ID

Counter Name

Counter Description

Original Release

50332572

VS.BTS.CnbapCap .UseRate

Average CNBAP ratio of the NodeB


50332585

VS.RlSetup.Reject. License.Cong

Number of radio link setup rejections because of license congestion in terms of the signaling processing capability


50332587

VS.RadioLink.Rec v.Max

Maximum number of received radio links per second


50332588

VS.RadioLink.Han dle.Max

Maximum number of wireless connection processing times per second


50332589

VS.RlSetup.Reject. CP.Cong

Number of radio link setup rejections because of control plane congestion


50332590

VS.RadioLink.Rec v.Mean

Average number of received radio links per second




Issue 11 (2015–05–30)


414



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332572

VS.BTS.Cnbap Cap.UseRate



U

Description This counter measures the average 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 counter.

Formula None

Unit %



Issue 11 (2015–05–30)


415



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332585

VS.RlSetup.Rej ect.License.Con g



U

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.

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

Issue 11 (2015–05–30)


416



Formula None

Unit None


Feature ID

VS.RlSetup.Reject.License. Cong

Multi-mode: None

Feature Name


Admission Control

LTE: None

Number of Received Radio Links per Second Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332587

VS.RadioLink. Recv.Max

Maximum number of received radio links per second


U

50332590

VS.RadioLink. Recv.Mean

Average number of received radio links per second


U

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.

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. Issue 11 (2015–05–30)


417



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

Issue 11 (2015–05–30)


418



Figure 1-15

Formula None

Unit None


Maximum number of wireless connection processing times per second Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332588

VS.RadioLink. Handle.Max

Maximum number of wireless connection processing times per second


U

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. Issue 11 (2015–05–30)


419



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

Issue 11 (2015–05–30)


420



Figure 1-18

Formula None

Unit None


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 Name

Counter Description

Network Element

Applicable Mode

50332589

VS.RlSetup.Rej ect.CP.Cong

Number of radio link setup rejections because of control plane congestion


U

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. Issue 11 (2015–05–30)


421



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


1.2.4 NodeB Reserved Counter Measurement (NODEBRESERVE.NODEB) Overview The function subset indicates measurements reserved for NodeBs. Reserved counter is used temporarily in patch versions and will be replaced with a new counter in later versions. For the detailed information about used reserved counters, see the "Used Reserved Counter List" of the corresponding version.

Issue 11 (2015–05–30)


422



Counters Counter ID

Counter Name

Counter Description

Original Release

50332567

VS.NodeBReserve. Counter1.NodeB

Reserved 1 for the NodeB


50332568




50332569




50332570




50332571





Reserved 1 for the NodeB Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332567

VS.NodeBRese rve.Counter1.N odeB



U

Description None. The following table describes the meanings of each counter: Issue 11 (2015–05–30)


423



Counter Name

Description

VS.NodeBReserve.Counter1.NodeB

None.


Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332568




U


Description


None.

Measurement Points None. Issue 11 (2015–05–30)


424



Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332569




U


Description


None.


Formula None

Unit None

Related Features None Issue 11 (2015–05–30)


425




Counter Name

Counter Description

Network Element

Applicable Mode

50332570




U


Description


None.


Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332571




U

Issue 11 (2015–05–30)


426




Description


None.


Formula None

Unit None


1.2.5 Iub Transmission Performance Measurement per NodeB (TRAFFIC.TRPIP.NODEB) Overview The function subset measures the transmission bandwidth and rate on the NodeB user plane and control plane.

Counters Counter ID

Counter Name

Counter Description

Original Release

50342640

VS.IubIP.TxPackets

Number of userplane and controlplane IP packets transmitted at the IP layer over the Iub interface


Issue 11 (2015–05–30)


427



Counter ID

Counter Name

Counter Description

Original Release

50342641

VS.IubIP.RxPackets

Number of userplane and controlplane IP packets received at the IP layer over the Iub interface


50342642

VS.IubIP.TxBytes

Number of bytes in the user-plane and control-plane IP packets transmitted at the IP layer over the Iub interface


50342643

VS.IubIP.RxBytes

Number of bytes in the user-plane and control-plane IP packets received at the IP layer over the Iub interface


50342644

VS.IubIP.TxMaxSpeed

Maximum userplane and controlplane transmit rate at the IP layer over the Iub interface


50342645

VS.IubIP.TxMeanSpeed

Average user-plane and control-plane transmit rate at the IP layer over the Iub interface


50342646

VS.IubIP.RxMaxSpeed

Maximum userplane and controlplane receive rate at the IP layer over the Iub interface


50342647

VS.IubIP.RxMeanSpeed

Average user-plane and control-plane receive rate at the IP layer over the Iub interface


Counter Relationship None Issue 11 (2015–05–30)


428



Number of IP Packets at the IP Layer over the Iub Interface Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342640

VS.IubIP.TxPa ckets

Number of userplane and control-plane IP packets transmitted at the IP layer over the Iub interface


U

50342641

VS.IubIP.RxPa ckets

Number of userplane and control-plane IP packets received at the IP layer over the Iub interface


U

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 userplane 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 Issue 11 (2015–05–30)


429




Feature ID

VS.IubIP.TxPackets

Multi-mode: None

Feature Name



WRFD-050411

Fractional IP Function on Iub Interface

LTE: None

VS.IubIP.RxPackets



WRFD-050411

Fractional IP Function on Iub Interface

LTE: None

Number of Bytes in the IP Packets at the IP Layer over the Iub Interface Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342642

VS.IubIP.TxBy tes

Number of bytes in the user-plane and controlplane IP packets transmitted at the IP layer over the Iub interface


U

50342643

VS.IubIP.RxBy tes

Number of bytes in the user-plane and controlplane IP packets received at the IP layer over the Iub interface


U

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, Issue 11 (2015–05–30)


430



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


Feature ID

VS.IubIP.TxBytes

Multi-mode: None

Feature Name


VS.IubIP.RxBytes

IP Transmission Introduction on Iub Interface Fractional IP Function on Iub Interface



Rate at the IP Layer over the Iub Interface Issue 11 (2015–05–30)


431



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342644

VS.IubIP.TxMa xSpeed

Maximum userplane and control-plane transmit rate at the IP layer over the Iub interface


U

50342645

VS.IubIP.TxMe anSpeed

Average userplane and control-plane transmit rate at the IP layer over the Iub interface


U

50342646

VS.IubIP.RxMa xSpeed

Maximum userplane and control-plane receive rate at the IP layer over the Iub interface


U

50342647

VS.IubIP.RxMe anSpeed

Average userplane and control-plane receive rate at the IP layer over the Iub interface


U

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 Issue 11 (2015–05–30)


432



measurement period, the maximum and average of these sampling results are used as the values of the corresponding counters.

Formula None

Unit bit/s


Feature ID

VS.IubIP.TxMaxSpeed

Multi-mode: None

Feature Name


VS.IubIP.TxMeanSpeed



VS.IubIP.RxMaxSpeed



VS.IubIP.RxMeanSpeed



Issue 11 (2015–05–30)



433



1.3 Measurement of CNOperator Performance (OPERATOR) Overview The object type consists of operator-related function subnets to indicate the bandwidth consumption on a NodeB.


FunctionSubSet Name

TRAFFIC.OPERATOR

Traffic Measurement per CNOperator

OPERESERVE.OPERATOR

Operator Reserved Counter Measurement

1.3.1 Traffic Measurement per CNOperator (TRAFFIC.OPERATOR) Overview The function subset measures the consumption of baseband resources on the NodeB side according to the usage of CEs of each license group.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332555

VS.LC.ULMean.Li censeGroup

Average number of uplink CEs consumed by an operator


50332556

VS.LC.DLMean.Li censeGroup

Average number of downlink CEs consumed by an operator


50332557

VS.LC.DLCreditA vailable.LicenseGr oup.Dedicated

Number of dedicated DL CEs configured for an operator


Issue 11 (2015–05–30)


434



Counter ID

Counter Name

Counter Description

Original Release

50332558

VS.LC.ULCreditA vailable.LicenseGr oup.Dedicated

Number of dedicated UL CEs configured for an operator


50332559

VS.LC.ULCreditA vailable.Shared

Number of UL CEs configured for a shared group


50332560

VS.LC.DLCreditA vailable.Shared

Number of DL CEs configured for a shared group


50332561

VS.LC.ULMean.Li censeGroup.Shared

Average number of UL CEs consumed in a shared group


50332562

VS.LC.DLMean.Li censeGroup.Shared

Average number of DL CEs consumed in a shared group


50332563

VS.HSUPA.LC.UL Mean.LicenseGroup

Average number of uplink CEs consumed by HSUPA services of an operator


50332564

VS.HSUPA.LC.UL Mean.LicenseGrou p.Shared

Average number of shared uplink CEs consumed by HSUPA services of a shared group


50332593

VS.LC.ULCreditU sed.Mean.SharedOperator

Average number of uplink CEs consumed by each operator in an MOCN network


Issue 11 (2015–05–30)


435



Counter ID

Counter Name

Counter Description

Original Release

50332594

VS.LC.DLCreditU sed.Mean.SharedOperator

Average number of downlink CEs consumed by each operator in an MOCN network


50342555

VS.LC.ULMax.LicenseGroup

Maximum number of uplink CEs consumed by an operator


50342556

VS.LC.DLMax.LicenseGroup

Maximum number of downlink CEs consumed by an operator


50342561

VS.LC.ULMax.Lic enseGroup.Shared

Maximum number of UL CEs consumed in a shared group


50342562

VS.LC.DLMax.Lic enseGroup.Shared

Maximum number of DL CEs consumed in a shared group


50342563

VS.HSUPA.LC.UL Max.LicenseGroup

Maximum number of uplink CEs consumed by HSUPA services of an operator


50342564

VS.HSUPA.LC.UL Max.LicenseGroup .Shared

Maximum number of shared uplink CEs consumed by HSUPA services of a shared group


50342567

VS.LC.DLMin.Lice nseGroup.Shared

Minimum Number of DL CEs consumed in a shared group


Issue 11 (2015–05–30)


436



Counter ID

Counter Name

Counter Description

Original Release

50342568

VS.LC.ULMin.Lice nseGroup.Shared

Minimum Number of UL CEs consumed in a shared group


50342569

VS.HSUPA.LC.UL Min.LicenseGroup. Shared

Minimum Number of Shared uplink CEs Consumed by HSUPA Services of a shared group


50342570

VS.LC.DLMin.LicenseGroup

Minimum number of downlink CEs consumed by an operator


50342571

VS.LC.ULMin.LicenseGroup

Minimum number of uplink CEs consumed by an operator


50342572

VS.HSUPA.LC.UL Min.LicenseGroup

Minimum number of uplink CEs consumed by HSUPA services of an operator


50342618

VS.ULCoMP.LC.U LMean.LicenseGroup

Average Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links


50342619

VS.ULCoMP.LC.U LMax.LicenseGroup

Maximum Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links


50342621

VS.ULCoMP.LC.U LMean.LicenseGro up.Shared

Average Number of UL CEs Configured for an Operator in a Shared Group Consumed by UL Coordinating Links


Issue 11 (2015–05–30)


437



Counter ID

Counter Name

Counter Description

Original Release

50342622

VS.ULCoMP.LC.U LMax.LicenseGrou p.Shared

Maximum Number of UL CEs Configured for an Operator in a Shared Group Consumed by UL Coordinating Links


50342624

VS.ULCoMP.HSU PA.LC.ULMean.Li censeGroup

Average Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links Carrying HSUPA Services


50342625

VS.ULCoMP.HSU PA.LC.ULMax.LicenseGroup

Maximum Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links Carrying HSUPA Services


50342627

VS.ULCoMP.HSU PA.LC.ULMean.Li censeGroup.Shared

Average Number of UL CEs in a Shared Group Consumed by UL Coordinating Links Carrying HSUPA Services


50342628

VS.ULCoMP.HSU PA.LC.ULMax.Lic enseGroup.Shared

Maximum Number of UL CEs in a Shared Group Consumed by UL Coordinating Links Carrying HSUPA Services



Number of Uplink CEs Consumed by an Operator

Issue 11 (2015–05–30)


438



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332555

VS.LC.ULMea n.LicenseGroup

Average number of uplink CEs consumed by an operator


U

50342555

VS.LC.ULMax. LicenseGroup

Maximum number of uplink CEs consumed by an operator


U

50342571

VS.LC.ULMin. LicenseGroup

Minimum number of uplink CEs consumed by an operator


U

Description This counter measures the number of dedicated and shared uplink CEs consumed by an operator. This counter is only used for operators with RAN sharing. Remarks: After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) are introduced, the number of consumed uplink CEs in license groups includes the number of uplink CEs consumed by DCH users and HSUPA users and the number of CEs consumed by coordinating links for UL CoMP (joint reception) users in the local license group. 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.

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.



439



Unit None


Feature ID

VS.LC.ULMean.LicenseGroup

Multi-mode: None

Feature Name


Admission Control

LTE: None VS.LC.ULMax.LicenseGroup


Admission Control

LTE: None VS.LC.ULMin.LicenseGroup


Admission Control

LTE: None

Number of Downlink CEs Consumed by an Operator Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332556

VS.LC.DLMea n.LicenseGroup

Average number of downlink CEs consumed by an operator


U

50342556

VS.LC.DLMax. LicenseGroup

Maximum number of downlink CEs consumed by an operator


U

50342570

VS.LC.DLMin. LicenseGroup

Minimum number of downlink CEs consumed by an operator


U

Issue 11 (2015–05–30)


440



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


Feature ID

VS.LC.DLMean.LicenseGroup

Multi-mode: None

Feature Name


Admission Control

LTE: None VS.LC.DLMax.LicenseGroup


Admission Control

LTE: None VS.LC.DLMin.LicenseGroup


Admission Control

LTE: None

Number of DL CEs Configured for an Operator

Issue 11 (2015–05–30)


441



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332557

VS.LC.DLCred itAvailable.Lice nseGroup.Dedic ated

Number of dedicated DL CEs configured for an operator


U

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


Feature ID

VS.LC.DLCreditAvailable. LicenseGroup.Dedicated

Multi-mode: None

Feature Name


Admission Control

LTE: None

Number of UL CEs Configured for an Operator

Issue 11 (2015–05–30)


442



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332558

VS.LC.ULCred itAvailable.Lice nseGroup.Dedic ated

Number of dedicated UL CEs configured for an operator


U

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


Feature ID

VS.LC.ULCreditAvailable. LicenseGroup.Dedicated

Multi-mode: None

Feature Name


Admission Control

LTE: None

Number of UL CEs Configured for a Shared Group

Issue 11 (2015–05–30)


443



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332559

VS.LC.ULCred itAvailable.Shar ed

Number of UL CEs configured for a shared group


U

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


Feature ID

VS.LC.ULCreditAvailable. Shared

Multi-mode: None

Feature Name


Admission Control

LTE: None

Number of DL CEs Configured for a Shared Group

Issue 11 (2015–05–30)


444



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332560

VS.LC.DLCred itAvailable.Shar ed

Number of DL CEs configured for a shared group


U

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


Feature ID

VS.LC.DLCreditAvailable. Shared

Multi-mode: None

Feature Name


Admission Control

LTE: None

Number of Uplink CEs Consumed in a Shared group

Issue 11 (2015–05–30)


445



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332561

VS.LC.ULMea n.LicenseGroup .Shared

Average number of UL CEs consumed in a shared group


U

50342561

VS.LC.ULMax. LicenseGroup.S hared

Maximum number of UL CEs consumed in a shared group


U

50342568

VS.LC.ULMin. LicenseGroup.S hared

Minimum Number of UL CEs consumed in a shared group


U

Description This counter measures the number of uplink CEs consumed in a shared group. This counter is only used for operators with RAN sharing. Remarks: After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) are introduced, the number of consumed uplink CEs in license groups includes the number of uplink CEs consumed by DCH users and HSUPA users and the number of CEs consumed by coordinating links for UL CoMP (joint reception) users in the local license group. 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.

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.



446



Unit None


Feature ID

VS.LC.ULMean.LicenseGr oup.Shared

Multi-mode: None

Feature Name


Admission Control

LTE: None VS.LC.ULMax.LicenseGro up.Shared


Admission Control

LTE: None VS.LC.ULMin.LicenseGrou p.Shared


Admission Control

LTE: None

Number of Downlink CEs consumed in a Shared group Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332562

VS.LC.DLMea n.LicenseGroup .Shared

Average number of DL CEs consumed in a shared group


U

50342562

VS.LC.DLMax. LicenseGroup.S hared

Maximum number of DL CEs consumed in a shared group


U

50342567

VS.LC.DLMin. LicenseGroup.S hared

Minimum Number of DL CEs consumed in a shared group


U

Issue 11 (2015–05–30)


447



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


Feature ID

VS.LC.DLMean.LicenseGr oup.Shared

Multi-mode: None

Feature Name


Admission Control

LTE: None VS.LC.DLMax.LicenseGro up.Shared


Admission Control

LTE: None VS.LC.DLMin.LicenseGrou p.Shared


Admission Control

LTE: None

Number of Uplink CEs Consumed by HSUPA Services of an Operator

Issue 11 (2015–05–30)


448



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332563

VS.HSUPA.LC .ULMean.Licen seGroup

Average number of uplink CEs consumed by HSUPA services of an operator


U

50342563

VS.HSUPA.LC .ULMax.LicenseGroup

Maximum number of uplink CEs consumed by HSUPA services of an operator


U

50342572

VS.HSUPA.LC .ULMin.LicenseGroup

Minimum number of uplink CEs consumed by HSUPA services of an operator


U

Description This counter measures the number of dedicated and shared uplink CEs consumed by HSUPA services of an operator. This counter is only used for operators with RAN sharing. Remarks: After Uplink CoMP (Joint Reception) and HetNet Uplink CoMP(Joint Reception) are introduced, the number of consumed uplink CEs in license groups includes the number of uplink CEs consumed by DCH users and HSUPA users and the number of CEs consumed by coordinating links for UL CoMP (joint reception) users in the local license group. 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.

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 Issue 11 (2015–05–30)


449



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


Feature ID

VS.HSUPA.LC.ULMean.Li censeGroup

Multi-mode: None

Feature Name


Admission Control

LTE: None VS.HSUPA.LC.ULMax.LicenseGroup


Admission Control

LTE: None VS.HSUPA.LC.ULMin.LicenseGroup


Admission Control

LTE: None

Number of Shared Uplink CEs Consumed by HSUPA Services of a Shared Group Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332564

VS.HSUPA.LC .ULMean.Licen seGroup.Shared

Average number of shared uplink CEs consumed by HSUPA services of a shared group


U

Issue 11 (2015–05–30)


450



Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342564

VS.HSUPA.LC .ULMax.Licens eGroup.Shared

Maximum number of shared uplink CEs consumed by HSUPA services of a shared group


U

50342569

VS.HSUPA.LC .ULMin.Licens eGroup.Shared

Minimum Number of Shared uplink CEs Consumed by HSUPA Services of a shared group


U

Description This counter measures the number of shared 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) and HetNet Uplink CoMP(Joint Reception) are introduced, the number of consumed uplink CEs in license groups includes the number of uplink CEs consumed by DCH users and HSUPA users and the number of CEs consumed by coordinating links for UL CoMP (joint reception) users in the local license group. 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.

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

Issue 11 (2015–05–30)


451



Unit None


Feature ID

VS.HSUPA.LC.ULMean.Li censeGroup.Shared

Multi-mode: None

Feature Name


Admission Control

LTE: None VS.HSUPA.LC.ULMax.Lic enseGroup.Shared


Admission Control

LTE: None VS.HSUPA.LC.ULMin.Lic enseGroup.Shared


Admission Control

LTE: None

Average number of uplink CEs consumed by each operator in an MOCN network Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332593

VS.LC.ULCred itUsed.Mean.Sh aredOperator

Average number of uplink CEs consumed by each operator in an MOCN network


U

Description This counter measures 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) and HetNet Uplink CoMP(Joint Reception) are introduced, the number of consumed uplink CEs in license groups includes the number of uplink Issue 11 (2015–05–30)


452



CEs consumed by DCH users and HSUPA users and the number of CEs consumed by coordinating links for UL CoMP (joint reception) users in the local license group. 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.

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


Feature ID

VS.LC.ULCreditUsed.Mean .SharedOperator

Multi-mode: None

Feature Name




Issue 11 (2015–05–30)


453



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332594

VS.LC.DLCred itUsed.Mean.Sh aredOperator



U

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


Feature ID

VS.LC.DLCreditUsed.Mean .SharedOperator

Multi-mode: None

Feature Name



Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links Issue 11 (2015–05–30)


454



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342618

VS.ULCoMP.L C.ULMean.Lic enseGroup

Average Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links


U

50342619

VS.ULCoMP.L C.ULMax.Lice nseGroup

Maximum Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links


U

Description This counter measures the average and maximum number of UL CEs in shared and dedicated groups configured for an operator consumed by UL coordinating links. The measurement results show how the CEs are additionally consumed after the UL CoMP feature has been enabled. The consumption can be assessed using the ratio of UL CEs configured for an operator consumed by UL coordinating links to those of other links. This counter is only used for operators with RAN sharing. 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.

Measurement Points The number of UL CEs in shared and dedicated groups configured for an operator consumed by UL 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 UL 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 UL coordinating links.

Issue 11 (2015–05–30)


455



Formula None

Unit None


Feature ID

VS.ULCoMP.LC.ULMean. LicenseGroup


VS.ULCoMP.LC.ULMax.Li censeGroup

Feature Name




Number of UL CEs Configured for an Operator in a Shared Group Consumed by UL Coordinating Links

Issue 11 (2015–05–30)


456



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342621

VS.ULCoMP.L C.ULMean.Lic enseGroup.Shar ed

Average Number of UL CEs Configured for an Operator in a Shared Group Consumed by UL Coordinating Links


U

50342622

VS.ULCoMP.L C.ULMax.Lice nseGroup.Share d

Maximum Number of UL CEs Configured for an Operator in a Shared Group Consumed by UL Coordinating Links


U

Description This counter measures the average and maximum number of UL CEs configured for an operator in a shared group consumed by UL coordinating links. The measurement results show how the CEs are additionally consumed after the UL CoMP feature has been enabled. The consumption can be assessed using the ratio of UL CEs configured for an operator in a shared group consumed by UL coordinating links to those of other links. This counter is only used for operators with RAN sharing. 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.

Measurement Points The number of UL CEs configured for an operator in a shared group consumed by UL 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 UL 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 UL coordinating links. Issue 11 (2015–05–30)


457



Formula None

Unit None


Feature ID

VS.ULCoMP.LC.ULMean. LicenseGroup.Shared


VS.ULCoMP.LC.ULMax.Li censeGroup.Shared

Feature Name




Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links Carrying HSUPA Services

Issue 11 (2015–05–30)


458



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342624

VS.ULCoMP.H SUPA.LC.UL Mean.LicenseGroup

Average Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links Carrying HSUPA Services


U

50342625

VS.ULCoMP.H SUPA.LC.UL Max.LicenseGr oup

Maximum Number of UL CEs Configured for an Operator Consumed by UL Coordinating Links Carrying HSUPA Services


U

Description This counter measures the average and maximum number of UL CEs in shared and dedicated groups configured for an operator consumed by UL coordinating links carrying HSUPA services. The measurement results show how the CEs are additionally consumed after the UL CoMP feature has been enabled. The consumption can be assessed using the ratio of UL CEs configured for an operator consumed by UL coordinating links carrying HSUPA services to those of other links. This counter is only used for operators with RAN sharing. 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.

Measurement Points The number of UL CEs in shared and dedicated groups configured for an operator consumed by UL 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 UL 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 Issue 11 (2015–05–30)


459



and dedicated groups configured for an operator consumed by UL coordinating links carrying HSUPA services.

Formula None

Unit None


Feature ID

VS.ULCoMP.HSUPA.LC.U LMean.LicenseGroup


VS.ULCoMP.HSUPA.LC.U LMax.LicenseGroup

Feature Name




Number of UL CEs in a Shared Group Consumed by UL Coordinating Links Carrying HSUPA Services

Issue 11 (2015–05–30)


460



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342627

VS.ULCoMP.H SUPA.LC.UL Mean.LicenseG roup.Shared

Average Number of UL CEs in a Shared Group Consumed by UL Coordinating Links Carrying HSUPA Services


U

50342628

VS.ULCoMP.H SUPA.LC.UL Max.LicenseGr oup.Shared

Maximum Number of UL CEs in a Shared Group Consumed by UL Coordinating Links Carrying HSUPA Services


U

Description This counter measures the average and maximum number of UL CEs in a shared group consumed by UL coordinating links carrying HSUPA services. The measurement results show how the CEs are additionally consumed after the UL CoMP feature has been enabled. The consumption can be assessed using the ratio of UL CEs in a shared group consumed by UL coordinating links carrying HSUPA services to those of other links. This counter is only used for operators with RAN sharing. 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.

Measurement Points The number of UL CEs in a shared group consumed by UL 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 UL 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 UL coordinating links carrying HSUPA services. Issue 11 (2015–05–30)


461



Formula None

Unit None


Feature ID

VS.ULCoMP.HSUPA.LC.U LMean.LicenseGroup.Share d


VS.ULCoMP.HSUPA.LC.U LMax.LicenseGroup.Shared

Feature Name




1.3.2 Operator Reserved Counter Measurement (OPERESERVE.OPERATOR) 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.

Issue 11 (2015–05–30)


462



Counters Counter ID

Counter Name

Counter Description

Original Release

50332591

VS.OpeReserve.Co unter1.OP

Reserved 1 for the operator


50332592




50332595




50332596




50332597





Reserved 1 for the operator Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332591

VS.OpeReserve .Counter1.OP



U

Description None. The following table describes the meanings of each counter: Issue 11 (2015–05–30)


463



Counter Name

Description

VS.OpeReserve.Counter1.OP

None.


Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332592




U


Description


None.

Measurement Points None. Issue 11 (2015–05–30)


464



Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332595




U


Description


None.


Formula None

Unit None

Related Features None Issue 11 (2015–05–30)


465




Counter Name

Counter Description

Network Element

Applicable Mode

50332596




U


Description


None.


Formula None

Unit None



Counter Name

Counter Description

Network Element

Applicable Mode

50332597




U

Issue 11 (2015–05–30)


466




Description


None.


Formula None

Unit None


1.4 Measurement of LoCell_SectorEQM Performance (LOCELL_SECTOREQM) Overview The object type consists of function subsets in a local cell under the sector equipment to indicate the local cell performance.


FunctionSubSet Name

IUB.LOCELL.SECTOREQM

Iub Measurement per LoCell_SectorEQM

PRACH.LOCELL.SECTOREQM

PRACH Measurement per LoCell_SectorEQM

ERACH.LOCELL.SECTOREQM

ERACH Measurement per LoCell_SectorEQM

Issue 11 (2015–05–30)


467



FunctionSubSet

FunctionSubSet Name

RTWP.LOCELL.SECTOREQM

RTWP Measurement per LoCell_SectorEQM

1.4.1 Iub Measurement per LoCell_SectorEQM (IUB.LOCELL.SECTOREQM) Overview The function subset consists of counters related to radio link deletion over an Iub interface.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332348

VS.RL.NormRel.L ocell.SectorEqm

Number of normal cell-sectoreqm RL releases


50332349

VS.RL.AbnormRel .Locell.SectorEqm

Number of abnormal cell-sectoreqm RL releases



Number of normal cell-sectoreqm RL releases Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332348

VS.RL.NormRe l.Locell.SectorEqm

Number of normal cellsectoreqm RL releases


U

Issue 11 (2015–05–30)


468



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.

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


Feature ID

VS.RL.NormRel.Locell.Sect orEqm


Issue 11 (2015–05–30)

Feature Name


Independent Demodulation of Signals from Multiple RRUs in One Cell

469



Number of abnormal cell-sectoreqm RL releases Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332349

VS.RL.Abnorm Rel.Locell.SectorEqm

Number of abnormal cellsectoreqm RL releases


U

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.

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



470




Feature ID

Feature Name

VS.RL.AbnormRel.Locell.S ectorEqm



1.4.2 PRACH Measurement per LoCell_SectorEQM (PRACH.LOCELL.SECTOREQM) Overview The function subset consists of PRACH-related counters for the LoCell_SectorEQM.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332350

VS.PositiveNum.AI CH.Locell.SectorEqm

Number of cellsectoreqm positive AI acknowledgments for RACH users


50332351

VS.NegativeNum.A ICH.Locell.SectorEqm

Number of cellsectoreqm negative AI acknowledgments for RACH users


50332352

VS.TBNum.Succ.R ACH.Locell.SectorEqm

Number of TBs successfully received over the cellsectoreqm RACH with correct CRCs


50332353

VS.TBNum.Total. RACH.Locell.SectorEqm

Total number of TBs received over the cell-sectoreqm RACH


Issue 11 (2015–05–30)


471




Number of cell-sectoreqm positive AI acknowledgments for RACH users Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332350

VS.PositiveNu m.AICH.Locell. SectorEqm

Number of cellsectoreqm positive AI acknowledgme nts for RACH users


U

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.

Formula None

Unit None

Issue 11 (2015–05–30)


472




Feature ID

VS.PositiveNum.AICH.Loc ell.SectorEqm

Multi-mode: None

Feature Name



LTE: None

Number of cell-sectoreqm negative AI acknowledgments for RACH users Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332351

VS.NegativeNu m.AICH.Locell. SectorEqm

Number of cellsectoreqm negative AI acknowledgme nts for RACH users


U

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.

Issue 11 (2015–05–30)


473



Formula None

Unit None


Feature ID

VS.NegativeNum.AICH.Lo cell.SectorEqm

Multi-mode: None

Feature Name



LTE: None

Number of TBs successfully received over the cell-sectoreqm RACH with correct CRCs Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332352

VS.TBNum.Su cc.RACH.Locel l.SectorEqm

Number of TBs successfully received over the cellsectoreqm RACH with correct CRCs


U

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 Issue 11 (2015–05–30)


474



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.

Formula None

Unit None


Feature ID

VS.TBNum.Succ.RACH.Lo cell.SectorEqm

Multi-mode: None

Feature Name



LTE: None

Total number of TBs received over the cell-sectoreqm RACH Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332353

VS.TBNum.Tot al.RACH.Locel l.SectorEqm

Total number of TBs received over the cellsectoreqm RACH


U

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. Issue 11 (2015–05–30)


475



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.

Formula None

Unit None


Feature ID

Feature Name

VS.TBNum.Total.RACH.Lo cell.SectorEqm



1.4.3 ERACH Measurement per LoCell_SectorEQM (ERACH.LOCELL.SECTOREQM) Overview The function subset consists of ERACH-related counters for the LoCell_SectorEQM.

Counters Counter ID

Counter Name

Counter Description

Original Release

50332354

VS.ERACH.Positiv eNum.AICH.Locell .SectorEqm

Number of cellsectoreqm positive AI acknowledgments for E-RACH users


Issue 11 (2015–05–30)


476



Counter ID

Counter Name

Counter Description

Original Release

50332355

VS.ERACH.Negati veNum.AICH.Loce ll.SectorEqm

Number of cellsectoreqm negative AI acknowledgments for E-RACH users



Number of cell-sectoreqm positive AI acknowledgments for E-RACH users Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332354

VS.ERACH.Po sitiveNum.AIC H.Locell.Sector Eqm

Number of cellsectoreqm positive AI acknowledgme nts for E-RACH users


U

Description This counter measures the number of cell-sectoreqm positive AI acknowledgements for ERACH 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 Issue 11 (2015–05–30)


477



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


Feature ID

VS.ERACH.PositiveNum.A ICH.Locell.SectorEqm

Multi-mode: None

Feature Name



LTE: None

Number of cell-sectoreqm negative AI acknowledgments for E-RACH users Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50332355

VS.ERACH.Ne gativeNum.AIC H.Locell.Sector Eqm

Number of cellsectoreqm negative AI acknowledgme nts for E-RACH users


U

Description This counter measures the number of cell-sectoreqm negative AI acknowledgements for ERACH 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. Issue 11 (2015–05–30)


478



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 featurehas 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


Feature ID

Feature Name

VS.ERACH.NegativeNum. AICH.Locell.SectorEqm



1.4.4 RTWP Measurement per LoCell_SectorEQM (RTWP.LOCELL.SECTOREQM) Overview The function subset measures the RTWP over antenna ports.

Counters Counter ID

Counter Name

Counter Description

Original Release

50342590

VS.MeanRTWP.Lo cell.SectorEqm.Ant 0

Average RTWP of Antenna 0


Issue 11 (2015–05–30)


479



Counter ID

Counter Name

Counter Description

Original Release

50342591




50342592




50342593




50342594

VS.MinRTWP.Loc ell.SectorEqm.Ant0

Minimum RTWP of Antenna 0


50342595




50342596




50342597





Average number of Ant RTWP

Issue 11 (2015–05–30)


480



Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342590

VS.MeanRTW P.Locell.Sector Eqm.Ant0



U

50342591




U

50342592




U

50342593




U

50342594

VS.MinRTWP. Locell.SectorEq m.Ant0



U

50342595




U

50342596




U

50342597




U

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.



481



Unit dBm


Feature ID

Feature Name

VS.MeanRTWP.Locell.Sect orEqm.Ant0





LTE: None






LTE: None






LTE: None





VS.MinRTWP.Locell.Secto rEqm.Ant0

LTE: None






LTE: None





Issue 11 (2015–05–30)



482



Counter Name

Feature ID

Feature Name






LTE: None






LTE: None

1.5 Measurement of UMTS ULCoMP Group Performance (UULCOMPGROUP) Overview The object type consists of UMTS ULCoMP Group-related function subnets to indicate the UMTS ULCoMP group status and performance.


FunctionSubSet Name

ALGO.UULCOMPGROUP

ULCoMP Group Algorithm Measurement

1.5.1 ULCoMP Group Algorithm Measurement (ALGO.UULCOMPGROUP) Overview The function subset measures the number of CoMP users in a coordinating cell, which indicates the CoMP performance on the NodeB.

Issue 11 (2015–05–30)


483



Counters Counter ID

Counter Name

Counter Description

Original Release

50342610

VS.UUlCoMPGrou p.UserNum

Average Number of CoMP Users in a UL CoMP Cell Pair


50342611

VS.UUlCoMPGrou p.MaxUserNum

Maximum Number of CoMP Users in a UL CoMP Cell Pair



Number of CoMP Users in a UL CoMP Cell Pair Counters Counter ID

Counter Name

Counter Description

Network Element

Applicable Mode

50342610

VS.UUlCoMP Group.UserNu m

Average Number of CoMP Users in a UL CoMP Cell Pair


U

50342611

VS.UUlCoMP Group.MaxUser Num

Maximum Number of CoMP Users in a UL CoMP Cell Pair


U

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. Issue 11 (2015–05–30)


484



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


Feature ID

VS.UUlCoMPGroup.UserNum


VS.UUlCoMPGroup.MaxUserNum



Issue 11 (2015–05–30)

Feature Name



485

3900 Series Base Station NodeBFunction Performance Counter Reference (V100R009C00_11)(PDF)-En

Recommend Documents