W-Cdma: Counters Reference Guide For Micronodeb

NN-20500-028
Wireless Service Provider Solutions
W-CDMA
Alcatel-Lucent 9300 W-CDMA Product Family
Counters Reference Guide for MicroNodeB
NN-20500-028 09.07 Standard April 2009
W-CDMA
Document number: NN-20500-028
Document issue: 09.07
Document status: Standard
Product release: OAM06.0
Date: April 2009
Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
Copyright © 2003-2009 Alcatel-Lucent, All Rights Reserved

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write
protected"; it may be altered only by authorized persons. While copies may be printed, it is not
recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies
taken must be regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of
Alcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all
information contained herein confidential, shall disclose the information only to its employees with a need
to know, and shall protect the information from disclosure and dissemination to third parties. Except as
expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information
contained herein. If you have received this document in error, please notify the sender and destroy it
immediately.
Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks
of Alcatel-Lucent, Alcatel and Lucent Technologies.
All other trademarks are the property of their owners.

Publication history 3
PUBLICATION HISTORY
SYSTEM RELEASE OAM06.0
April 2009
Issue 09.07/EN Standard
Update for DR5.
September 2008
Issue 09.06/EN Preliminary
Update after internal review.
July 2008
June 2008
Issue 09.04/EN Draft
Update for Pre-DR4
May 2008
Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Table of contents 4
1 About this publication................................................................................................................................................... 9

2 Road map to UTRAN documentation......................................................................................................................... 12
3 What's new....................................................................................................................................................................13
4 Access Network observation counters...................................................................................................................... 14
4.1 How Access Network observation counters are defined......................................................................................... 15
4.2 How Access Network observation counters are described......................................................................................21
5 Micro Node B counter families....................................................................................................................................24
5.1 Radio Statistics........................................................................................................................................................ 25
6 Micro Node B counter families..................................................................................................................................160
NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

List of figures 5
Figure 1 - BTS containment tree........................................................................................................... ............. ......... 15

List of tables 6
Table 1 - Table of aggregation rules..................................................................................................... ............. ......... 20

Table 2 - VS.RTWP - #30010............................................................................................................................. ......... 28
Table 3 - VS.RTWP_RxA - #30020.................................................................................................................... ......... 29
Table 4 - VS.RTWP_RxB - #30030.................................................................................................................... ......... 30
Table 5 - VS.TCP - #30040................................................................................................................... ............. ......... 30
Table 6 - VS.TCP_dBm - #30050....................................................................................................................... ......... 31
Table 7 - VS.TCP_Exceed90 - #30060................................................................................................. ............. ......... 32
Table 8 - VS.NmbPrachPreamblDetect - #30510................................................................................. ............. ......... 33
Table 9 - VS.NmbPrachPreamblAck - #30520................................................................................................... ......... 34
Table 10 - VS.PrachCRCerror - #30530............................................................................................... ............. ......... 35
Table 11 - VS.PRACHload - #30540.................................................................................................................. ......... 36
Table 12 - VS.SCCPCHload - #30550.................................................................................................. ............. ......... 37
Table 13 - VS.NmbDedicatedRL - #31010......................................................................................................... ......... 38
Table 14 - VS.SIRsf4 - #31020............................................................................................................. ............. ......... 39
Table 15 - VS.SIRsf8 - #31030............................................................................................................. ............. ......... 40
Table 16 - VS.SIRsf16 - #31040........................................................................................................... ............. ......... 40
Table 17 - VS.SIRsf32 - #31050........................................................................................................... ............. ......... 41
Table 18 - VS.SIRsf64 - #31060........................................................................................................... ............. ......... 42
Table 19 - VS.SIRsf128 - #31070......................................................................................................... ............. ......... 43
Table 20 - VS.SIRsf256 - #31080......................................................................................................... ............. ......... 43
Table 21 - VS.ULCeConsumedDPCH - #31090................................................................................... ............. ......... 44
Table 22 - VS.ULCeFreeForDPCH - #31100........................................................................................ ............. ......... 45
Table 23 - VS.DLCeConsumedDPCH - #31110................................................................................... ............. ......... 46
Table 24 - VS.DLCeFreeForDPCH - #31120........................................................................................ ............. ......... 46
Table 25 - VS.CpLoad - #31510......................................................................................................................... ......... 47
Table 26 - VS.BasebandLoad - #31520................................................................................................ ............. ......... 48
Table 27 - VS.BasebandCapAllocation - #31530............................................................................................... ......... 49
Table 28 - VS.BaseBandCapAllocationReject - #31540....................................................................... ............. ......... 50
Table 29 - VS.AAL2_LostCPS - #32010............................................................................................... ............. ......... 51
Table 30 - VS.AAL2_STFParityErrors - #32020................................................................................................. ......... 52
Table 31 - VS.AAL2_SeqNmbErrors - #32030................................................................................................... ......... 53
Table 32 - VS.AAL2_CPSHeaderChecksumErrors - #32040............................................................... ............. ......... 54
Table 33 - VS.AAL2_CPSLenErrors - #32050...................................................................................... ............. ......... 55
Table 34 - VS.AAL2_CPSLenMismatch - #32060.............................................................................................. ......... 56
Table 35 - VS.AAL2_NmbLostCPS - #32070..................................................................................................... ......... 58
Table 36 - VS.AAL2BandwidthAllocation - #32080............................................................................... ............. ......... 59
Table 37 - VS.AAL2BandwidthUsageRatio - #32090......................................................................................... ......... 59
Table 38 - VS.NmbFPmessages - #32100......................................................................................................... ......... 60
Table 39 - VS.FPCrcErrors - #32110.................................................................................................... ............. ......... 61
Table 40 - VS.AAL5_TransmittedCells - #32510.................................................................................. ............. ......... 62
Table 41 - VS.AAL5_ReceivedCells - #32520...................................................................................... ............. ......... 65

List of tables 7
Table 42 - VS.AAL5_AbortErrors - #32530........................................................................................... ............. ......... 67

Table 43 - VS.AAL5_LengthErrors - #32540...................................................................................................... ......... 69
Table 44 - VS.AAL5_CrcFrameErrors - #32550................................................................................................. ......... 72
Table 45 - VS.AAL5_InvalidSize - #32560............................................................................................ ............. ......... 74
Table 46 - VS.TCP_ExceptHSDPA - #33010..................................................................................................... ......... 76
Table 47 - VS.TCP_HSPDSCH - #33020............................................................................................. ............. ......... 77
Table 48 - VS.TCP_HS_SCCH - #33030........................................................................................................... ......... 78
Table 49 - VS.HSDPA_PDSCH_codes - #33040............................................................................................... ......... 79
Table 50 - VS.HSDPA_SCCHcodes - #33050...................................................................................... ............. ......... 79
Table 51 - VS.HSDPA_16QAMusage - #33060................................................................................................. ......... 80
Table 52 - VS.HSDPA_MAC-D_PDU_ack_bits - #33070..................................................................... ............. ......... 81
Table 53 - VS.HSDPA_PduRxBits - #33080......................................................................................... ............. ......... 82
Table 54 - VS.HSDPA_MacTxBits - #33090......................................................................................... ............. ......... 83
Table 55 - VS.HSDPA_TxDataBits - #33100........................................................................................ ............. ......... 84
Table 56 - VS.HSDPA_Ack - #33110................................................................................................................. ......... 85
Table 57 - VS.HSDPA_Nack - #33120............................................................................................................... ......... 86
Table 58 - VS.HSDPA_dtx - #33130..................................................................................................... ............. ......... 87
Table 59 - VS.HSDPA_DiscardTimeout - #33140.............................................................................................. ......... 88
Table 60 - VS.HSDPA_DiscardedDueToMaxRetransmit - #33150.................................................................... ......... 90
Table 61 - VS.HSDPA_DiscardedDueToT1Timer - #33160................................................................. ............. ......... 91
Table 62 - VS.HSDPA_DiscardDueToMacHSWindow - #33170.......................................................... ............. ......... 92
Table 63 - VS.HSDPA_TB_Retransmit0 - #33180............................................................................................. ......... 93
Table 67 - VS.HSDPA_TB_Retransmit_gt3 - #33220........................................................................................ ......... 97
Table 68 - VS.HSDPA_DataBuffered - #33230.................................................................................................. ......... 98
Table 69 - VS.HSDPA_TTIused - #33240.......................................................................................................... ......... 99
Table 70 - VS.CellULload - #33500.................................................................................................................... ....... 100
Table 71 - VS.FailedAdmissionsDueToULload - #33510................................................................................... ....... 101
Table 72 - VS.AdmissionRequestsULcac - #33520.............................................................................. ............. ....... 102
Table 73 - VS.HsdpaCQIdecodingFailed - #33530............................................................................... ............. ....... 103
Table 74 - VS.HsdpaReceivedCQI0 - #33540...................................................................................... ............. ....... 104

List of tables 8
Table 84 - VS.HsdpaReceivedCQI10 - #33640.................................................................................... ............. ....... 115

Table 100 - VS.HsdpaReceivedCQI26 - #33800.................................................................................. ............. ....... 133
Table 105 - VS.HsdpaUEsPerCell - #33850......................................................................................... ............. ....... 138
Table 106 - VS.eDCHcommonChannelsTxPower - #33860................................................................. ............. ....... 139
Table 107 - VS.eDCHmWcommonChannelsTxPower - #33870........................................................................ ....... 140
Table 108 - VS.eDCHdataBitsSentToRNC - #33880............................................................................ ............. ....... 141
Table 109 - VS.eDCHtranspBlockNoRetransmit - #33890................................................................................. ....... 142
Table 110 - VS.eDCHtranspBlockRetransmit1 - #33900...................................................................... ............. ....... 143
Table 119 - VS.eDCHtranspBlockRetransmit10 - #33990.................................................................... ............. ....... 153
Table 120 - VS.eDCHtranspBlockRetransmit11 - #34000.................................................................... ............. ....... 154
Table 121 - VS.eDCHtranspBlockRetransmit12orMore - #34010...................................................................... ....... 155
Table 122 - VS.eDCHtranspBlockDiscardedRetransm - #34020....................................................................... ....... 156
Table 123 - VS.eDCHdataBitsReceived - #34030................................................................................ ............. ....... 157
Table 124 - VS.eDCHactiveUsers - #34040....................................................................................................... ....... 158
Table 125 - VS.eDCHriseOverThermal - #34050............................................................................................... ....... 158

9
1 About this publication

This publication provides a list of UMTS Access Network observation counters collected by the
APM/ADI applications of the Performance server.
This section consists of the following topics:
• "Applicability"
• "Audience"
• "Prerequisites"
• "Related publications"
• "How this publication is organized"
• "Vocabulary conventions"
Applicability
This publication applies to OAM06.0 System Release.
Audience
This publication is intended for network controllers responsible for the Performance Management of
the UMTS Access Network.
Prerequisites
It is recommended that readers become familiar with the following Technical Publications :
• Alcatel-Lucent 9353 Management System - System Overview (NN-20500-031) provides a
functional overview of the Operation, Administration and Maintenance (OAM) subsystem of the
Access Network.
Related publications
• Alcatel-Lucent 9300 W-CDMA Product Family - Performance Management (NN-20500-033)
How this publication is organized

This publication consists of the following modules:
• "Road map to Utran" presents the documents in the UTRAN documentation suite.
• "What is new in Access Network Observation Counters" presents the changes and, or the
new features introduced for the UA V6.0 release.
• "Access Network observation counters" is split into the following sections:
— "How Access Network observation counters are defined" provides information about the
counter definition template, counter types on the OAM GUI, and counter hierarchy.
— "How Access Network observation counters are described" describes the Access

10
Network observation counters.

• "BTS counter families" lists BTS counter families and presents their counters. Each counter is
described separately in a table, and these tables are arranged in alphanumerical order.
• "BTS counter index" presents the index of each Access Network observation counter.
Vocabulary conventions
For a list of UMTS terms used in this document, see the Alcatel-Lucent 9300 W-CDMA Product
Family - Terminology ( NN-20500-002).
The specific acronyms used in this publication are the following:
A. Release Available Release

CC Cumulative Counter
CFN Connection Frame Number
CUM CUMulative
DER Discrete Event Registration counter
DTD Document Type Definition
mW milliWatt
NEI NEIghbouring
SI Status Inspection
VAL VALue counter
The specific terms used in this publication are the following:
Access Stratum Config- Pointer to a pre-defined set of Radio Bearers providing a given Ra-
uration dio Access Bearer service.
For example:
• the Downlink (DL) access stratum configuration which number is
1 is dedicated to voice support; it comprises the following Radio
Bearers : 3 x 12.2 Kbps CS RBs on DTCH and 3 x 3.4 Kbps
SRB on DCCH.
• the DL access stratum configuration which number is 2 is dedic-
ated to packet support at 64 Kbps; it comprises the following Ra-
dio Bearers : 1 x 64 Kbps PS RB on DTCH and 3 x 3.4 Kbps
SRB for DCCH.
Refer to the following configurations:
— Downlink Access Stratum Configuration (DASC)
— Downlink Radio Bearer Set Configuration (DRBS)
— Uplink Access Stratum Configuration (UASC)
— Uplink Radio Bearer Set Configuration (URBS)

11
Connection Frame Num- CFN is the frame counter used for the L2/transport channel syn-
ber (CFN) chronisation between UE and UTRAN. A CFN value is associated to
each Transport Block Set (TBS) and it is passed together with it
through the MAC-L1 SAP. CFN provides a common frame reference
(at L2) to be used that is for synchronized transport channel recon-
figuration.
Measurement Term used in 3GPP TS 32.104 specifications. It has the same
meaning as the word 'counter' and is used in this publication to dis-
tinguish a counter from a '(radio) measurement'.
Reference cell Cell ranking first in a UE active set considering a radio criteria , that
means the cell supposed to provide on average the best radio qual-
ity for the reception of the next frames.
The reference cell is the primary cell considered in RRM.

12
2 Road map to UTRAN documentation

For collection roadmaps information, see Alcatel-Lucent 9300 W-CDMA Product Family - Document
Collection Overview and Update Summary (NN-20500-050).

13
3 What's new
For information about What's new section, see : Alcatel-Lucent 9300 W-CDMA Product Family -
UA06.0 / OAM06.0 Operational Impacts: CM, FM and PM Delta NN-20500-052

14
4 Access Network observation counters

This section includes the following topics:
• "How Access Network observation counters are defined"
• "How Access Network observation counters are described"

15
4.1 How Access Network observation counters are defined

A standard observation counter is a device used in Performance Management to calculate the
number of occurrences of an event. For further definitions for observation counters, refer to 3GPP TS
32.104 specifications.
This section describes the following topics:
• "Counter families"
• "Object hierarchy"
• "Wording assumption"
• "Counter definition template"
• "Counter types on the OAM GUI"
• "Counter hierarchy"
• "Aggregation rules"
Counter families
The counters specified in this publication are grouped into families of counters. A family of counters
is attached to a given UMTS feature. For example the "Radio Link Management Family" groups
together counters involved with Radio Link Management (i.e.: Setup, Addition, Deletion,
Reconfiguration..).
Object hierarchy
Counters are reported on objects (that is located) according to their hierarchy.
The following figure show the hierarchy of objects.
Figure 1 BTS containment tree

16
For more information about UTRAN objects and their relationships, refer to the Alcatel-Lucent 9353
Management System - System Overview (NN-20500-031) publication.
Wording assumption
Both wordings counter and measurement are equally used in this document to identify the same
concept. Usually, Alcatel-Lucent uses the term counter to distinguish a counter from a (radio)
measurement
A counter is periodically elaborated on periods expressed in minutes or hours, for example 15
minutes, while a measurement is elaborated on periods expressed in milliseconds, for example : 500
ms.
3GPP Performance Management specifications preferably use measurement. When the context
refers to 3GPP specifications, measurement is used, while counter is used in Alcatel-Lucent
specific part, but both wordings are equivalent.
Counter definition template

The following template used to describe the counters is extracted from 3GPP TS 32.104
specifications.
Measurement name (section header)
This is a descriptive name of the measurement type.
A-Description
This section contains an explanation of the measurement operation.
B-Collection
This section contains the form of the obtained measurement data:
• CC (Cumulative Counter) is incremented by 1 each time the counted event occurs.
• GAUGE (dynamic variable), data being measured can vary during the period of measurement.
• DER (Discrete Event Registration), data related to a particular event is captured every nth event,
where n can be 1 or larger.
• SI (Status Inspection), data related to the mean value is captured every nth sampling, where n
can be 1 or larger.
C-Condition (Event)
This section contains the condition that causes the measurement result data to be updated.
The condition is defined by identifying protocol related triggering events that either start or stop the
measurement processes or by updating the current measurement result value. When a precise

17
condition cannot be provided, the conditional circumstances behind the update are stated.
D-Result
This section contains a description of expected result value(s) (for example, a single integer value). If
more than one value is provided, the measurement is screened according to criteria, for example, a
number of call releases may be screened according to the cause of the call releases.
The number of call releases related to a given cause can be considered a subcounter. In that case,
the measurement result specification item includes a 'screening paragraph' that specifies the various
subcounters and their meanings.
E-Type
This section contains a short form of the measurement name specified in the header, which is used
to identify the measurement type in the result files.
F-Object Instance
This section contains the object class and its instance. The "measObjInstId" field identifies the
measured object class and its instance; for example, trunk1 means that object class trunk instance
#1 is being measured. The object class and instance values used for this purpose will be in
accordance with 3GPP TS 32.106. This means the NE or resource object model (defined in the Basic
CM IRP Information Model - 3GPP TS 32.106-5) and naming conventions (defined in the Naming
Convention for Managed Objects - 3GPP TS 32.106-8). This parameter, if applicable, will be
provided in the measurement job.
G-Switching
This section contains the Switching domain(s). Its measurement is applicable to Circuit Switched
and, or Packet Switched domains.
Note: Two counter specification items have been added to the seven preceding 3GPP items by
Alcatel-Lucent.
H-3GPP Compliance
This section states the compliance of the Alcatel-Lucent measurement with 3GPP specifications:
• the statement is "3GPP specified counter" if the Alcatel-Lucent implementation is fully compliant
with the 3GPP specification.
• the statement is "Alcatel-Lucent specified counter" if the counter is not considered by the 3GPP
specification.
I-Range
This section contains the range of the counter.

18
J-Unit
This section contains the unit of the counter.
K-Available Release
This section states the Alcatel-Lucent UMTS system release(s) in which the counter had been
introduced.
L-Aggregation Rule
This section contains one of these three values :RLoad, RVal and Rtotal. Each value defines the
aggregation rule type. The counter type defines the aggregation rule value.
M-Notes
This section contains notes and FRS numbers associated with the counters.
Counter types on the OAM GUI :

The three types of user-accessible observation counters available on the OAM GUI are as follows:
• CUMULATIVE (or TOTAL)
• VALUE
• LOAD
CUMULATIVE counters
CUMULATIVE counters provide raw counts. A CUMULATIVE counter is a CUM (CC) type counter,
as identified in 3GPP TS 32.104 specifications. It is incremented by 1 each time the counted event
occurs, and it provides the cumulative value. One NE cumulative counter provides one counter at the
OAM GUI level.
VALUE counters
VALUE counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order to
implement a DER (VAL) type measurement. This mechanism provides average values from raw
counts obtained by internal events (the time interval between two events is random and is not
accessible to users). The counter is incremented by a value attached to the event itself.
Alcatel-Lucent provides the following:
• the cumulated value (.Cum in XML files)
• the number of events (.NbEvt in XML files)
• the averaged value (.Avg in XML files)
• the maximum added value (.Max in XML files)

19
• the minimum added value (.Min in XML files)

Note: The averaged value is equal to cumulated value over number of events
LOAD counters
LOAD counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order to
implement an SI type measurement. This mechanism provides average values from raw counts
obtained by internal sampling (the time interval between two events is constant and is not accessible
to users). The counter is incremented by a sampled value on the sampling event occurrence.
Alcatel-Lucent provides the following:
• the cumulated value (.Cum in XML files)
• the number of samplings (.NbEvt in XML files)
• the averaged value (.Avg in XML files)
• the maximum sampled value (.Max in XML files)
• the minimum sampled value (.Min in XML files)
Note: The averaged value is equal to cumulated value/number of samplings.
Note: Alcatel-Lucent does not generally implement GAUGE type measurements because
providing the current value of a measurement by incrementing it by 1 when a positive event occurs
and by decrementing it by 1 when a negative event occurs, can lead to some shifts if an event is
missed.
Note: The reported value counter is collected by a non real time task at the end of each
observation period. The collection period (usually one hour) for the Performance Management file
does not imply that all .NbEvt of LOAD counters are exactly equal to the number of counter
periods included in one collection (12 for counters with 5mn granularity). Due to the low priority of
the Performance Management task, it is possible when the PM file is built that some samples can
miss. They will be included in the next file. This can lead to one file with NbEvt equal to 11 (for a
5mn counter), followed later by one with 13 (possibly with some 12 between). The averages
values calculated by computing .Cum/.NbEvt are still meaningful, as the samples added in .Cum
are coherent with the .NbEvt value.
Counter hierarchy
An observation counter stored in XML files can contain one or several levels.
A dot (.) separates two successive levels.
The following example shows the counter hierarchy with five levels.
Example:
radioLink.establishment.failure.cause<Name>.Avg
Counters with one level do not end with a dot.
Example:
droppedLastRadioLink

20
Aggregation rules
When aggregating counters from different periods of observation (temporal aggregation) you must
follow the following rules.
Let X1,X2,...,Xn the measurements from periods 1,2,...,n and X the resulting value over the total
period.
The following table presents a rule for each counter.
Table 1 Table of aggregation rules
Rule Results Apply to
Rtotal X.cum = X1.cum + X2.cum + ... + Xn.cum CUM (CC) counters
Rload/Rval X.cum = X1.cum + ... + Xn.cum Some LOAD and VAL
X.nbevt = X1.nbevt + ... + Xn.nbevt counters
X.avg = (X1.cum + ... + Xn.cum) / (X1.nbevt + ...

+ Xn.nbevt)
X.min = min (X1.min,...,Xn.min)
X.max = max (X1.max,...,Xn.max)
Rload* Same as Rload but resulting X.cum has no phys- Some LOAD counters
ical meaning due to the nature of the measure-
ment (like percents) and is not interpreted but is
necessary for intermediate computations.
Ravg X = Xi / n MSS counters
where Xi (i = 1 to n) represent average values
Radd X = ΣXi MSS counters
where Xi (i = 1 to n) represent cumulative values
Rmin X = min (Xi) MSS counters
where Xi (i = 1 to n) represent minimum values
Rmax X = max (Xi) MSS counters
where Xi (i = 1 to n) represent maximum values

21
4.2 How Access Network observation counters are described

An observation counter is a measurement used to report data for network Performance
Management.
Observation counters are stored in XML record files.

Each record file contains the counters produced by a single NE collection.
Access Network observation counters handled by the ADI application for the UMTS V6.0 system
release are as follows:
• C-Node application counters
• I-Node platform counters
• Node B counters
These counters have been divided into the three following sets of families:
• "RNC counters families"
• "NodeB counter families"
• "MSS counter families"
Each counter family is attached to a given UMTS feature (for example, Handover counters, where
hard handover performances are reported) or to a Performance Management purpose for example,
User Plane Traffic counters, where counters related to traffic observation are grouped together).
Access observation file structure

Some observation counters are processed in order to provide temporal and spatial aggregations. The
following observation counter records are available:
• single period
• hourly aggregated
• daily aggregated
Each observation file produces single, hourly and daily observation counter records. At the dedicated
NE level, a predetermined subset of these data are aggregated.
The file name convention for an observation is as follows:
<type><startdate>.<starttime>-<endtime>_<NE>[-<RC>].
Where:
type is set to A which indicates one of the following aggregated observations:

• the observation file contains data originated from a single NE for a unique time period.
• the observation file contains data originated from a single NE for an hourly aggregated file.

22
• the observation file contains data originated from a single NE for a daily aggregated file.
startdate is the beginning date of the granularity period; its format must be <YYYYMMDD>.
starttime is the beginning time of the granularity period; its format must be <hhmm+#GMT>.
endtime is the end time of the granularity period; its format must be <hhmm+#GMT>.
NE is the Network Element type ID that means a unique numerical identifier as 3GPP using
<node Type>-<NE userlabel> pattern (for example, "ANode-rnc1" or "RNCCN-rnc10" or "INode-
rnc12").
List of possible NE types:
• RNCCN
• INode
• ANode
• NodeB
• POC
Or the BTS name using the NE userLabel as a NE ID (for example "NodeB-A10km215").
RC is an optional running count. In case of PPT aggressive mode collection,the value is 2+.
Note : If the RC is absent, the "-" separator is absent as well.
Refer to the following table for an interpretation of the codes:
Code Description
YYYY The 4-digit year
MM The month of the year (01, 02,..., 12) for file creation time at RNC level
DD The day of the month (01, 02,..., 31) for file creation time at RNC level
hh The 2-digit hour (00, 01,..., 23). In the case of daily aggregation files, hh is al-
ways 00.
mm The 2-digit minute of the hour. Possible values are by increments of five
minutes: 00, 05, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55. In the case of
hourly or daily aggregation files, mm is always 00.
#GMT Difference between local time and Greenwich Meridian Time (+/-hhmm). At
10:15:02 in Paris, the 13 April 2005 in Paris, the #GMT is +0100 = the
hhmm#GMT is 1015+0100.At 18:12:11 in New York, the 13 April 2005, the
#GMT is #0500 = the hhmm#GMT is 1812-0500.
Node B observation file

The XML format is compliant with 3 GPP dtd file: 32.401-02.dtd. The counters measured by the Node
B are stored in the RAM of the Node B. This file is periodically uploaded by the Performance
Server.(XDR file format is used on the Node B)

23
The directory of the RNC Node B observation file on PerfServer is as follows:

/opt/nortel/data/utran/observation/stats/<YYYYMMDD>/<BTSEquipment-BTSUserLabel>
Example:
/opt/nortel/data/utran/observation/stats/20020828/BTSEq-BTSM1_30_000
For more information about Node B record files, see the Alcatel-Lucent 9300 W-CDMA Product
Family - Performance Management (NN-20500-033) publication.

24
5 Micro Node B counter families

• Radio Statistics

25
5.1 Radio Statistics
Alcatel-Lucent Counter name

counter number
#30010 VS.RTWP
#30020 VS.RTWP_RxA
#30030 VS.RTWP_RxB
#30040 VS.TCP
#30050 VS.TCP_dBm
#30060 VS.TCP_Exceed90
#30510 VS.NmbPrachPreamblDetect
#30520 VS.NmbPrachPreamblAck
#30530 VS.PrachCRCerror
#30540 VS.PRACHload
#30550 VS.SCCPCHload
#31010 VS.NmbDedicatedRL
#31020 VS.SIRsf4
#31030 VS.SIRsf8
#31040 VS.SIRsf16
#31050 VS.SIRsf32
#31060 VS.SIRsf64
#31070 VS.SIRsf128
#31080 VS.SIRsf256
#31090 VS.ULCeConsumedDPCH
#31100 VS.ULCeFreeForDPCH
#31110 VS.DLCeConsumedDPCH
#31120 VS.DLCeFreeForDPCH
#31510 VS.CpLoad
#31520 VS.BasebandLoad
#31530 VS.BasebandCapAllocation
#31540 VS.BaseBandCapAllocationReject
#32010 VS.AAL2_LostCPS
#32020 VS.AAL2_STFParityErrors
#32030 VS.AAL2_SeqNmbErrors
#32040 VS.AAL2_CPSHeaderChecksumErrors
#32050 VS.AAL2_CPSLenErrors

26

counter number
#32060 VS.AAL2_CPSLenMismatch
#32070 VS.AAL2_NmbLostCPS
#32080 VS.AAL2BandwidthAllocation
#32090 VS.AAL2BandwidthUsageRatio
#32100 VS.NmbFPmessages
#32110 VS.FPCrcErrors
#32510 VS.AAL5_TransmittedCells
#32520 VS.AAL5_ReceivedCells
#32530 VS.AAL5_AbortErrors
#32540 VS.AAL5_LengthErrors
#32550 VS.AAL5_CrcFrameErrors
#32560 VS.AAL5_InvalidSize
#33010 VS.TCP_ExceptHSDPA
#33020 VS.TCP_HSPDSCH
#33030 VS.TCP_HS_SCCH
#33040 VS.HSDPA_PDSCH_codes
#33050 VS.HSDPA_SCCHcodes
#33060 VS.HSDPA_16QAMusage
#33070 VS.HSDPA_MAC-D_PDU_ack_bits
#33080 VS.HSDPA_PduRxBits
#33090 VS.HSDPA_MacTxBits
#33100 VS.HSDPA_TxDataBits
#33110 VS.HSDPA_Ack
#33120 VS.HSDPA_Nack
#33130 VS.HSDPA_dtx
#33140 VS.HSDPA_DiscardTimeout
#33150 VS.HSDPA_DiscardedDueToMaxRetransmit
#33160 VS.HSDPA_DiscardedDueToT1Timer
#33170 VS.HSDPA_DiscardDueToMacHSWindow
#33180 VS.HSDPA_TB_Retransmit0
#33220 VS.HSDPA_TB_Retransmit_gt3
#33230 VS.HSDPA_DataBuffered

27

counter number
#33240 VS.HSDPA_TTIused
#33500 VS.CellULload
#33510 VS.FailedAdmissionsDueToULload
#33520 VS.AdmissionRequestsULcac
#33530 VS.HsdpaCQIdecodingFailed
#33540 VS.HsdpaReceivedCQI0

28

counter number
#33850 VS.HsdpaUEsPerCell
#33860 VS.eDCHcommonChannelsTxPower
#33870 VS.eDCHmWcommonChannelsTxPower
#33880 VS.eDCHdataBitsSentToRNC
#33890 VS.eDCHtranspBlockNoRetransmit
#33900 VS.eDCHtranspBlockRetransmit1
#34010 VS.eDCHtranspBlockRetransmit12orMore
#34020 VS.eDCHtranspBlockDiscardedRetransm
#34030 VS.eDCHdataBitsReceived
#34040 VS.eDCHactiveUsers
#34050 VS.eDCHriseOverThermal
Table 2 VS.RTWP - #30010

A-Description
The received wide band power, including noise generated in the receiver, within the bandwidth
defined by the receiver pulse shaping filter. The reference point for the measurement shall be
the Rx antenna connector. In case of receiver diversity the reported value shall be linear aver-
age of the power in the diversity branches. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type

29
VS.RTWP
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-112.0..-50.0
J-Unit
dbM
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 3 VS.RTWP_RxA - #30020

A-Description
the Rx antenna connector. This value is for receiver antenna branch A. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.RTWP_RxA
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-112.0..-50.0

30
J-Unit
dBm
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 4 VS.RTWP_RxB - #30030

A-Description
the Rx antenna connector. This value is for receiver antenna branch B. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.RTWP_RxB
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-112.0..-50.0
J-Unit
dBm
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 5 VS.TCP - #30040

31
A-Description
Total Transmitted carrier power for one DL carier from one cell and sector. Reported as per-
centage of maximum configured transmission power (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.TCP
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..100.0
J-Unit
%
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 6 VS.TCP_dBm - #30050

A-Description
Transmitted carrier power in dBm total transmitted power on one DL carrier from one UTRAN
access point. The reference point for the transmitted carrier power measurement shall be the
Tx antenna connector (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.

32
E-Type
VS.TCP_dBm
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..100.0
J-Unit
dBm
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 7 VS.TCP_Exceed90 - #30060

A-Description
Number of periods for which the total transmitted carrier power exceeded 90% of the maximum
cell power configured (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
• Sub-Counter #0: NA
E-Type
VS.TCP_Exceed90.CC

33
VS.TCP_Exceed90.AVG
VS.TCP_Exceed90.SDEV
VS.TCP_Exceed90.MIN
VS.TCP_Exceed90.MAX
VS.TCP_Exceed90.TSAMPL
VS.TCP_Exceed90.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 8 VS.NmbPrachPreamblDetect - #30510

A-Description
The detected PRACH access preambles measurement is defined as the total number of detec-
ted access preambles per access frame per PRACH (including all sub-channels and signa-
tures). The value includes detected preambles both positively (ACK) and negatively acknow-
ledged (NAK) on AICH (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

34
E-Type
VS.NmbPrachPreamblDetect.CC
VS.NmbPrachPreamblDetect.AVG
VS.NmbPrachPreamblDetect.SDEV
VS.NmbPrachPreamblDetect.MIN
VS.NmbPrachPreamblDetect.MAX
VS.NmbPrachPreamblDetect.TSAMPL
VS.NmbPrachPreamblDetect.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 9 VS.NmbPrachPreamblAck - #30520

A-Description
The Acknowledged PRACH preambles measurement is defined as the total number of ac-
knowledged PRACH preambles per access frame per PRACH. This is equivalent to the num-
ber of positive acquisition indicators transmitted per access frame per AICH (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

35
E-Type
VS.NmbPrachPreamblAck.CC
VS.NmbPrachPreamblAck.AVG
VS.NmbPrachPreamblAck.SDEV
VS.NmbPrachPreamblAck.MIN
VS.NmbPrachPreamblAck.MAX
VS.NmbPrachPreamblAck.TSAMPL
VS.NmbPrachPreamblAck.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 10 VS.PrachCRCerror - #30530

A-Description
For each acknowledged PRACH preamble the Node B shall attempt to detect the PRACH
message part. If the CRC of the detected transport block is incorrect then this counter shall be
increased. Enables calculation of BLER for PRACH (Cumulative)
B-Collection

36
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.PrachCRCerror.CC
VS.PrachCRCerror.AVG
VS.PrachCRCerror.SDEV
VS.PrachCRCerror.MIN
VS.PrachCRCerror.MAX
VS.PrachCRCerror.TSAMPL
VS.PrachCRCerror.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 11 VS.PRACHload - #30540

37
A-Description
Ratio between: 1) Total number of received and processed frames with PRACH message
parts. 2) Maximum number of PRACH message part frame that the Node B could possibly pro-
cess during the same period with the configuration of the PRACH given by the RNC for the
cell. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.PRACHload
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..100.0
J-Unit
%load
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 12 VS.SCCPCHload - #30550

A-Description
Ratio between: 1) Total number of used data bits on the SCCPCH physical channels, i.e. ex-
cluding bits in DTX 2) Total number of data bits that the Node B could possibly process during
the same period with the configuration of all the SCCPCH given by the RNC for the cell.
(Average)
B-Collection
LOAD
C-Condition (Event)
-

38
D-Result
One measurement.
E-Type
VS.SCCPCHload
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..100.0
J-Unit
%load
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 13 VS.NmbDedicatedRL - #31010

A-Description
Number of simultaneous active dedicated radio links (DPCH) currently setup on this cell carrier
(common channels not counted) (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.NmbDedicatedRL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N

39
I-Range
0.0..128.0
J-Unit
links
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 14 VS.SIRsf4 - #31020

A-Description
Signal to Interference Ratio defined as: (RSCP/ISCP) x SF, see also [3GPP TS25.215] section
5.2.2. Reported value is averaged over all radio link sets using SF4 during the sample period,
where: RSCP = Received Signal Code Power, unbiased measurement of the received power
on one code. ISCP = Interference Signal Code Power, the interference on the received signal.
SF=The spreading factor used on the DPCCH. Measurement of SIR performed on the DPCCH
of all Radio Link Sets. In compressed mode the SIR is not measured in the transmission gap.
The reference point for the SIR measurements are Rx antenna connector. If Rx diversity is
used in the BTS for the cell, then SIR for a radio link is the linear summation of the SIR from
each Rx antenna for that radio link. eDCH channels are not included. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.SIRsf4
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-11.0..20.0
J-Unit
dB
K-Available Release

40
05_01_00
L-Aggregation Rule
Ravg
M-Notes

A-Description
see Uplink SIR SF4 (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.SIRsf8
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-11.0..20.0
J-Unit
dB
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes

A-Description
B-Collection
LOAD

41
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.SIRsf16
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-11.0..20.0
J-Unit
dB
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes

A-Description
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.SIRsf32
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance

42
N
I-Range
-11.0..20.0
J-Unit
dB
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes

A-Description
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.SIRsf64
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-11.0..20.0
J-Unit
dB
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes

43

A-Description
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.SIRsf128
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-11.0..20.0
J-Unit
dB
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes

A-Description
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type

44
VS.SIRsf256
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
-11.0..20.0
J-Unit
dB
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes
Table 21 VS.ULCeConsumedDPCH - #31090

A-Description
The BTS has a dedicated pool of channel elements (CE) available for all uplink processing.
This pool is shared both for common and dedicated channels. The number reported in this
counter corresponds to number of CE at the time of sampling consumed for processing of up-
link dedicated channels DPCH. CEs consumed for processing of eDCH or common channels
are not included. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.ULCeConsumedDPCH
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range

45
0.0..256.0
J-Unit
CE
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes
Table 22 VS.ULCeFreeForDPCH - #31100

A-Description
The BTS has a dedicated pool of channel elements (CE) available for uplink processing. This
pool is shared both for common and dedicated channels. The number reported in this counter
corresponds to number of CE at the time of sampling free to use for processing of additional
uplink dedicated channels DPCH. CEs consumed for common channels or eDCH are not in-
cluded. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.ULCeFreeForDPCH
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..256.0
J-Unit
CE
K-Available Release
05_01_00
L-Aggregation Rule
Ravg

46
M-Notes
Table 23 VS.DLCeConsumedDPCH - #31110

A-Description
The BTS has a dedicated pool of channel elements (CE) available for downlink processing.
counter corresponds to number of CE at the time of sampling consumed for processing of
downlink dedicated channels DPCH. CEs consumed for common channels or eDCH are not in-
cluded. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.DLCeConsumedDPCH
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..256.0
J-Unit
CE
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes
Table 24 VS.DLCeFreeForDPCH - #31120

A-Description
The BTS has a dedicated pool of channel elements (CE) available for downlink processing.
counter corresponds to number of CE at the time of sampling free to use for processing of ad-
ditional downlink dedicated channels DPCH.CEs consumed for common channels or eDCH

47
are not included. (Average)

B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.DLCeFreeForDPCH
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..256.0
J-Unit
CE
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes
Table 25 VS.CpLoad - #31510

A-Description
Processor load on the main control processing system of the Node B unit. Value is presented
as % of maximum load allowed for a guaranteed safe operation of the node (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.CpLoad

48
F-Object Instance
SectorEquipment
G-Switching
H-3GPP Compliance
N
I-Range
0.0..200.0
J-Unit
%load
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 26 VS.BasebandLoad - #31520

A-Description
Processing load on base band processing system of the Node B unit. Value is presented as %
of maximum load allowed for a guaranteed safe operation of the node (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.BasebandLoad
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..200.0
J-Unit
%load

49
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 27 VS.BasebandCapAllocation - #31530

A-Description
Number of requests for reservation of additional base band capacity. This number includes all
requests from RNC which results increased usage of base band processing resource e.g. all
radio link set up requests and radio link reconfiguration requests resulting in additional load on
the base band processing system. The number includes both approved and rejected capacity
allocation requests (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.BasebandCapAllocation.CC
VS.BasebandCapAllocation.AVG
VS.BasebandCapAllocation.SDEV
VS.BasebandCapAllocation.MIN
VS.BasebandCapAllocation.MAX
VS.BasebandCapAllocation.TSAMPL
VS.BasebandCapAllocation.NSAMPL
F-Object Instance
BTSCell
G-Switching

50
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 28 VS.BaseBandCapAllocationReject - #31540

A-Description
Number of rejected requests for reservation of additional base band capacity. This number in-
cludes all requests from RNC which have been rejected due to not enough processing re-
sources available. The rejected requests includes e.g. radio link setup requests and radio link
reconfiguration requests implying higher load on the base band processing system
(Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.BaseBandCapAllocationReject.CC
VS.BaseBandCapAllocationReject.AVG
VS.BaseBandCapAllocationReject.SDEV
VS.BaseBandCapAllocationReject.MIN
VS.BaseBandCapAllocationReject.MAX

51
VS.BaseBandCapAllocationReject.TSAMPL
VS.BaseBandCapAllocationReject.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 29 VS.AAL2_LostCPS - #32010

A-Description
Number of lost CPS packets per user plane AAL2 PVC (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.AAL2_LostCPS.CC
VS.AAL2_LostCPS.AVG

52
VS.AAL2_LostCPS.SDEV
VS.AAL2_LostCPS.MIN
VS.AAL2_LostCPS.MAX
VS.AAL2_LostCPS.TSAMPL
VS.AAL2_LostCPS.NSAMPL
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 30 VS.AAL2_STFParityErrors - #32020

A-Description
Number of CPS PDUs received with parity error (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

53
E-Type
VS.AAL2_STFParityErrors.CC
VS.AAL2_STFParityErrors.AVG
VS.AAL2_STFParityErrors.SDEV
VS.AAL2_STFParityErrors.MIN
VS.AAL2_STFParityErrors.MAX
VS.AAL2_STFParityErrors.TSAMPL
VS.AAL2_STFParityErrors.NSAMPL
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 31 VS.AAL2_SeqNmbErrors - #32030

A-Description
Number of received CPS PDUs with sequence number error (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

54
E-Type
VS.AAL2_SeqNmbErrors.CC
VS.AAL2_SeqNmbErrors.AVG
VS.AAL2_SeqNmbErrors.SDEV
VS.AAL2_SeqNmbErrors.MIN
VS.AAL2_SeqNmbErrors.MAX
VS.AAL2_SeqNmbErrors.TSAMPL
VS.AAL2_SeqNmbErrors.NSAMPL
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 32 VS.AAL2_CPSHeaderChecksumErrors - #32040

A-Description
Number of CPS PDUs received with header checksum error (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

55
E-Type
VS.AAL2_CPSHeaderChecksumErrors.CC
VS.AAL2_CPSHeaderChecksumErrors.AVG
VS.AAL2_CPSHeaderChecksumErrors.SDEV
VS.AAL2_CPSHeaderChecksumErrors.MIN
VS.AAL2_CPSHeaderChecksumErrors.MAX
VS.AAL2_CPSHeaderChecksumErrors.TSAMPL
VS.AAL2_CPSHeaderChecksumErrors.NSAMPL
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 33 VS.AAL2_CPSLenErrors - #32050

A-Description
Number of CPS PDUs with length errors (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)

56
-
D-Result
E-Type
VS.AAL2_CPSLenErrors.CC
VS.AAL2_CPSLenErrors.AVG
VS.AAL2_CPSLenErrors.SDEV
VS.AAL2_CPSLenErrors.MIN
VS.AAL2_CPSLenErrors.MAX
VS.AAL2_CPSLenErrors.TSAMPL
VS.AAL2_CPSLenErrors.NSAMPL
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 34 VS.AAL2_CPSLenMismatch - #32060

A-Description
Number of CPS PDUs with incorrect CPS length (Cumulative)

57
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.AAL2_CPSLenMismatch.CC
VS.AAL2_CPSLenMismatch.AVG
VS.AAL2_CPSLenMismatch.SDEV
VS.AAL2_CPSLenMismatch.MIN
VS.AAL2_CPSLenMismatch.MAX
VS.AAL2_CPSLenMismatch.TSAMPL
VS.AAL2_CPSLenMismatch.NSAMPL
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes

58
Table 35 VS.AAL2_NmbLostCPS - #32070

A-Description
Number of cells received with offset field >47 (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.AAL2_NmbLostCPS.CC
VS.AAL2_NmbLostCPS.AVG
VS.AAL2_NmbLostCPS.SDEV
VS.AAL2_NmbLostCPS.MIN
VS.AAL2_NmbLostCPS.MAX
VS.AAL2_NmbLostCPS.TSAMPL
VS.AAL2_NmbLostCPS.NSAMPL
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule

59
Radd
M-Notes
Table 36 VS.AAL2BandwidthAllocation - #32080

A-Description
Bandwidth allocated by RNC on each user data port. 1) If RNC informs Node B about band-
width allocation at creation/modification of a tansport bearer, then the Node B will use this
value to reserve bandwidth on the user data port. 2) If RNC does not inform Node B about
bandwidth allocation for transport bearer, then Node B estimates bandwidth allocation using in-
formation received from RNC in NBAP. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.AAL2BandwidthAllocation
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..35000.0
J-Unit
kbit/s
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 37 VS.AAL2BandwidthUsageRatio - #32090

A-Description
Amount of configured bandwidth allocated by RNC for each user data port. 1) If RNC informs
Node B about bandwidth allocation at creation / modification of a transport bearer, then Node B
will use this value to reserve bandwidth on the user data port. 2) If RNC does not inform Node

60
B about bandwidth allocation for transport bearer, then Node B estimates bandwidth allocation
using information received from RNC in NBAP. 3) The percent load is calculated as the ratio
between currently allocated bandwidth and the configured max peak cell rate for the AAL2
PVC (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.AAL2BandwidthUsageRatio
F-Object Instance
UserDataPort
G-Switching
H-3GPP Compliance
N
I-Range
0.0..200.0
J-Unit
%
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 38 VS.NmbFPmessages - #32100

A-Description
Number of received frame protocol messages from RNC. Both control and userplane mes-
sages received on FP from RNC are counted. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

61
E-Type
VS.NmbFPmessages.CC
VS.NmbFPmessages.AVG
VS.NmbFPmessages.SDEV
VS.NmbFPmessages.MIN
VS.NmbFPmessages.MAX
VS.NmbFPmessages.TSAMPL
VS.NmbFPmessages.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 39 VS.FPCrcErrors - #32110

A-Description
Number of CRC errors detected on frame protocol messages from RNC. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)

62
-
D-Result
E-Type
VS.FPCrcErrors.CC
VS.FPCrcErrors.AVG
VS.FPCrcErrors.SDEV
VS.FPCrcErrors.MIN
VS.FPCrcErrors.MAX
VS.FPCrcErrors.TSAMPL
VS.FPCrcErrors.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 40 VS.AAL5_TransmittedCells - #32510

A-Description
Number of transmitted cells on AAL5 (Cumulative)

63
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

64
VS.AAL5_TransmittedCells.CC
VS.AAL5_TransmittedCells.AVG
VS.AAL5_TransmittedCells.SDEV
VS.AAL5_TransmittedCells.MIN
VS.AAL5_TransmittedCells.MAX
VS.AAL5_TransmittedCells.TSAMPL
VS.AAL5_TransmittedCells.NSAMPL
F-Object Instance
ItfB
G-Switching
H-3GPP Compliance
N
I-Range

65
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 41 VS.AAL5_ReceivedCells - #32520

A-Description
Number of received cells on AAL5 (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

66
E-Type
VS.AAL5_ReceivedCells.CC
VS.AAL5_ReceivedCells.AVG
VS.AAL5_ReceivedCells.SDEV
VS.AAL5_ReceivedCells.MIN
VS.AAL5_ReceivedCells.MAX
VS.AAL5_ReceivedCells.TSAMPL
VS.AAL5_ReceivedCells.NSAMPL

67
F-Object Instance
ItfB
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 42 VS.AAL5_AbortErrors - #32530

A-Description
Number of abort errors on AAL5 (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

68
E-Type
VS.AAL5_AbortErrors.CC
VS.AAL5_AbortErrors.AVG
VS.AAL5_AbortErrors.SDEV
VS.AAL5_AbortErrors.MIN
VS.AAL5_AbortErrors.MAX
VS.AAL5_AbortErrors.TSAMPL
VS.AAL5_AbortErrors.NSAMPL

69
F-Object Instance
ItfB
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 43 VS.AAL5_LengthErrors - #32540

A-Description
Number of length errors on AAL5 (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)

70
-
D-Result
E-Type
VS.AAL5_LengthErrors.CC
VS.AAL5_LengthErrors.AVG
VS.AAL5_LengthErrors.SDEV

71
VS.AAL5_LengthErrors.MIN
VS.AAL5_LengthErrors.MAX
VS.AAL5_LengthErrors.TSAMPL
VS.AAL5_LengthErrors.NSAMPL
F-Object Instance
ItfB
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release

72
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 44 VS.AAL5_CrcFrameErrors - #32550

A-Description
Number of frames with incorrect CRC received on an AAL5 PVC (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

73
E-Type
VS.AAL5_CrcFrameErrors.CC
VS.AAL5_CrcFrameErrors.AVG
VS.AAL5_CrcFrameErrors.SDEV
VS.AAL5_CrcFrameErrors.MIN
VS.AAL5_CrcFrameErrors.MAX
VS.AAL5_CrcFrameErrors.TSAMPL
VS.AAL5_CrcFrameErrors.NSAMPL

74
F-Object Instance
ItfB
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 45 VS.AAL5_InvalidSize - #32560

A-Description
Number of received AAL5 frames with an invalid size (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

75
E-Type
VS.AAL5_InvalidSize.CC
VS.AAL5_InvalidSize.AVG
VS.AAL5_InvalidSize.SDEV
VS.AAL5_InvalidSize.MIN
VS.AAL5_InvalidSize.MAX
VS.AAL5_InvalidSize.TSAMPL
VS.AAL5_InvalidSize.NSAMPL

76
F-Object Instance
ItfB
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 46 VS.TCP_ExceptHSDPA - #33010

A-Description
Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission.
This shall be reported as percentage of maximum configured transmission power for the cell
(Average)
B-Collection
LOAD
C-Condition (Event)
-

77
D-Result
One measurement.
E-Type
VS.TCP_ExceptHSDPA
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..100.0
J-Unit
%
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 47 VS.TCP_HSPDSCH - #33020

A-Description
Total transmitted power on all allocated HS-PDSCH codes per TTI. This shall be reported as
percentage of maximum configured transmission power for the cell (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.TCP_HSPDSCH
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N

78
I-Range
0.0..100.0
J-Unit
%
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 48 VS.TCP_HS_SCCH - #33030

A-Description
Total transmitted power for all HS-SSCH codes per TTI. This shall be reported as percentage
of maximum configured transmission power for the cell (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.TCP_HS_SCCH
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..100.0
J-Unit
%
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes

79
Table 49 VS.HSDPA_PDSCH_codes - #33040

A-Description
Number of HS-PDSCH codes actually used per TTI (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.HSDPA_PDSCH_codes
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..15.0
J-Unit
codes/TTI
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 50 VS.HSDPA_SCCHcodes - #33050

A-Description
Number of HS-SCCH codes used per TTI. It then indicates the number of scheduled UEs in
the TTI (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.

80
E-Type
VS.HSDPA_SCCHcodes
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..4.0
J-Unit
codes/TTI
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 51 VS.HSDPA_16QAMusage - #33060

A-Description
Number of scheduled mobiles using 16QAM per TTI (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.HSDPA_16QAMusage
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..15.0
J-Unit

81
UE/TTI
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 52 VS.HSDPA_MAC-D_PDU_ack_bits - #33070

A-Description
Total number of successfully transmitted MAC-d PDU bits per TTI (an ACK has been received
for the corresponding transport block) (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.HSDPA_MAC-D_PDU_ack_bits.CC
VS.HSDPA_MAC-D_PDU_ack_bits.AVG
VS.HSDPA_MAC-D_PDU_ack_bits.SDEV
VS.HSDPA_MAC-D_PDU_ack_bits.MIN
VS.HSDPA_MAC-D_PDU_ack_bits.MAX
VS.HSDPA_MAC-D_PDU_ack_bits.TSAMPL
VS.HSDPA_MAC-D_PDU_ack_bits.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance

82
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 53 VS.HSDPA_PduRxBits - #33080

A-Description
Total number of data bits received by the NodeB. It corresponds to the bits of all the MAC-d
PDUs received in every FP data frame (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.HSDPA_PduRxBits.CC
VS.HSDPA_PduRxBits.AVG
VS.HSDPA_PduRxBits.SDEV
VS.HSDPA_PduRxBits.MIN
VS.HSDPA_PduRxBits.MAX
VS.HSDPA_PduRxBits.TSAMPL
VS.HSDPA_PduRxBits.NSAMPL
F-Object Instance

83
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 54 VS.HSDPA_MacTxBits - #33090

A-Description
Total number of data bits (transport block size) first transmitted by the MAC hs per TTI. The re-
transmissions are then not taken into account, meaning that a block retransmitted several
times is only taken into account once at the first transmission (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.HSDPA_MacTxBits.CC
VS.HSDPA_MacTxBits.AVG
VS.HSDPA_MacTxBits.SDEV
VS.HSDPA_MacTxBits.MIN

84
VS.HSDPA_MacTxBits.MAX
VS.HSDPA_MacTxBits.TSAMPL
VS.HSDPA_MacTxBits.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 55 VS.HSDPA_TxDataBits - #33100

A-Description
Total number of data bits (transport block size) scheduled per TTI, taking into account the re-
transmissions. Any time a block is retransmitted, its bits are added (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

85
VS.HSDPA_TxDataBits.CC
VS.HSDPA_TxDataBits.AVG
VS.HSDPA_TxDataBits.SDEV
VS.HSDPA_TxDataBits.MIN
VS.HSDPA_TxDataBits.MAX
VS.HSDPA_TxDataBits.TSAMPL
VS.HSDPA_TxDataBits.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 56 VS.HSDPA_Ack - #33110

A-Description
Number of acknowledged transport blocks (ACK received for a transmitted transport block)
(Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

86
E-Type
VS.HSDPA_Ack.CC
VS.HSDPA_Ack.AVG
VS.HSDPA_Ack.SDEV
VS.HSDPA_Ack.MIN
VS.HSDPA_Ack.MAX
VS.HSDPA_Ack.TSAMPL
VS.HSDPA_Ack.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 57 VS.HSDPA_Nack - #33120

A-Description
Number of negatively acknowledged transport blocks (NACK received for a transmitted trans-
port block) (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

87
E-Type
VS.HSDPA_Nack.CC
VS.HSDPA_Nack.AVG
VS.HSDPA_Nack.SDEV
VS.HSDPA_Nack.MIN
VS.HSDPA_Nack.MAX
VS.HSDPA_Nack.TSAMPL
VS.HSDPA_Nack.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 58 VS.HSDPA_dtx - #33130

A-Description
Number of DTX detected (neither ACK nor NACK received for a transmitted transport block)
(Cumulative)
B-Collection
CUMULATE
C-Condition (Event)

88
-
D-Result
E-Type
VS.HSDPA_dtx.CC
VS.HSDPA_dtx.AVG
VS.HSDPA_dtx.SDEV
VS.HSDPA_dtx.MIN
VS.HSDPA_dtx.MAX
VS.HSDPA_dtx.TSAMPL
VS.HSDPA_dtx.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 59 VS.HSDPA_DiscardTimeout - #33140

A-Description
Number of MAC-d PDUs that have been discarded due to discard timer expiration
(Cumulative)

89
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.HSDPA_DiscardTimeout.CC
VS.HSDPA_DiscardTimeout.AVG
VS.HSDPA_DiscardTimeout.SDEV
VS.HSDPA_DiscardTimeout.MIN
VS.HSDPA_DiscardTimeout.MAX
VS.HSDPA_DiscardTimeout.TSAMPL
VS.HSDPA_DiscardTimeout.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes

90
Table 60 VS.HSDPA_DiscardedDueToMaxRetransmit - #33150

A-Description
Number of transport blocks that have been discarded because the maximum number of re-
transmissions was reached. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.HSDPA_DiscardedDueToMaxRetransmit.CC
VS.HSDPA_DiscardedDueToMaxRetransmit.AVG
VS.HSDPA_DiscardedDueToMaxRetransmit.SDEV
VS.HSDPA_DiscardedDueToMaxRetransmit.MIN
VS.HSDPA_DiscardedDueToMaxRetransmit.MAX
VS.HSDPA_DiscardedDueToMaxRetransmit.TSAMPL
VS.HSDPA_DiscardedDueToMaxRetransmit.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00

91
L-Aggregation Rule
Radd
M-Notes
Table 61 VS.HSDPA_DiscardedDueToT1Timer - #33160

A-Description
Number of transport blocks that have been discarded because T1 timer expired. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.HSDPA_DiscardedDueToT1Timer.CC
VS.HSDPA_DiscardedDueToT1Timer.AVG
VS.HSDPA_DiscardedDueToT1Timer.SDEV
VS.HSDPA_DiscardedDueToT1Timer.MIN
VS.HSDPA_DiscardedDueToT1Timer.MAX
VS.HSDPA_DiscardedDueToT1Timer.TSAMPL
VS.HSDPA_DiscardedDueToT1Timer.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit

92
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 62 VS.HSDPA_DiscardDueToMacHSWindow - #33170

A-Description
Number of transport blocks that have been discarded because MAC-hs window size exceeded.
(Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.HSDPA_DiscardDueToMacHSWindow.CC
VS.HSDPA_DiscardDueToMacHSWindow.AVG
VS.HSDPA_DiscardDueToMacHSWindow.SDEV
VS.HSDPA_DiscardDueToMacHSWindow.MIN
VS.HSDPA_DiscardDueToMacHSWindow.MAX
VS.HSDPA_DiscardDueToMacHSWindow.TSAMPL
VS.HSDPA_DiscardDueToMacHSWindow.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N

93
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 63 VS.HSDPA_TB_Retransmit0 - #33180

A-Description
Total number of transport blocks acknowledged by Ue after 0 retransmissions. 1) Number of
retransmissions = 0 means the block has been correctly received after the first transmission. 2)
The blocks discarded due to the maximum (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.HSDPA_TB_Retransmit0.CC
VS.HSDPA_TB_Retransmit0.AVG
VS.HSDPA_TB_Retransmit0.SDEV
VS.HSDPA_TB_Retransmit0.MIN
VS.HSDPA_TB_Retransmit0.MAX
VS.HSDPA_TB_Retransmit0.TSAMPL
VS.HSDPA_TB_Retransmit0.NSAMPL
F-Object Instance

94
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes

A-Description
Defined as 1) Total number of transport blocks acknowledged by Ue after one retransmission.
2) The blocks discarded due to the maximum number of retransmissions reached are not taken
into account. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

95
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes

A-Description
Defined as 1) Total number of transport blocks acknowledged by Ue after 2 retransmissions. 2)
The blocks discarded due to the maximum number of retransmissions reached are not taken
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

96
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes

A-Description
Defined as 1) Total number of transport blocks acknowledged by Ue after 3 retransmissions. 2)
The blocks discarded due to the maximum number of retransmissions reached are not taken
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

97
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 67 VS.HSDPA_TB_Retransmit_gt3 - #33220

A-Description
Defined as 1) Total number of transport blocks acknowledged by Ue after more than 3 retrans-
missions. 2) The blocks discarded due to the maximum number of retransmissions reached
are not taken into account. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

98
E-Type
VS.HSDPA_TB_Retransmit_gt3.CC
VS.HSDPA_TB_Retransmit_gt3.AVG
VS.HSDPA_TB_Retransmit_gt3.SDEV
VS.HSDPA_TB_Retransmit_gt3.MIN
VS.HSDPA_TB_Retransmit_gt3.MAX
VS.HSDPA_TB_Retransmit_gt3.TSAMPL
VS.HSDPA_TB_Retransmit_gt3.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 68 VS.HSDPA_DataBuffered - #33230

A-Description
Total number of data kbit (MAC-d PDU bits) buffered in NodeB. Each 100ms, the counter is
updated by the averaged value during this period. Min and max values are nevertheless up-
dated on a TTI basis (Average)
B-Collection

99
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.HSDPA_DataBuffered
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..10000.0
J-Unit
kbit
K-Available Release
04_02_00
L-Aggregation Rule
Ravg
M-Notes
Table 69 VS.HSDPA_TTIused - #33240

A-Description
Number of TTIs (2ms) containing at least one scheduled UE. It allows new statistics to be de-
rived for some previous counters (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

100
E-Type
VS.HSDPA_TTIused.CC
VS.HSDPA_TTIused.AVG
VS.HSDPA_TTIused.SDEV
VS.HSDPA_TTIused.MIN
VS.HSDPA_TTIused.MAX
VS.HSDPA_TTIused.TSAMPL
VS.HSDPA_TTIused.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
04_02_00
L-Aggregation Rule
Radd
M-Notes
Table 70 VS.CellULload - #33500

A-Description
The cell uplink load on air interface (Uu) is estimated from measured RTWP and the Referen-
ceRTWP value received from RNC. Total RTWP is used, including eDCH traffic. Calculation:
ULload = 1 # 10exp{-(RTWPmeas-RTWPref/10} where RTWP measured in dBm. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.

101
E-Type
VS.CellULload
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..100.0
J-Unit
%
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes
Table 71 VS.FailedAdmissionsDueToULload - #33510

A-Description
For each connection request from RNC the BTS checks current uplink air-interface load. New
connections are rejected by the BTS if the uplink load exceeds a threshold. This counter shows
number of connection requests from RNC rejected by BTS due to excessive load in the cell up-
link air-interface. The counter includes connection requests both related to DCH and eDCH.
Rejected connections due to other reasons, e.g. downlink transmission power, transmission in-
terface, channel element capacity etc, are not included in this value. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

102
E-Type
VS.FailedAdmissionsDueToULload.CC
VS.FailedAdmissionsDueToULload.AVG
VS.FailedAdmissionsDueToULload.SDEV
VS.FailedAdmissionsDueToULload.MIN
VS.FailedAdmissionsDueToULload.MAX
VS.FailedAdmissionsDueToULload.TSAMPL
VS.FailedAdmissionsDueToULload.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 72 VS.AdmissionRequestsULcac - #33520

A-Description
Number of connection requests from RNC resulting in BTS checking for load in the cell uplink
air-interface. Counter includes connection requests both for DCH and eDCH. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

103
E-Type
VS.AdmissionRequestsULcac.CC
VS.AdmissionRequestsULcac.AVG
VS.AdmissionRequestsULcac.SDEV
VS.AdmissionRequestsULcac.MIN
VS.AdmissionRequestsULcac.MAX
VS.AdmissionRequestsULcac.TSAMPL
VS.AdmissionRequestsULcac.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 73 VS.HsdpaCQIdecodingFailed - #33530

A-Description
Counting number of occassions where BTS failed to decode CQI report from a UE.
(Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

104
E-Type
VS.HsdpaCQIdecodingFailed.CC
VS.HsdpaCQIdecodingFailed.AVG
VS.HsdpaCQIdecodingFailed.SDEV
VS.HsdpaCQIdecodingFailed.MIN
VS.HsdpaCQIdecodingFailed.MAX
VS.HsdpaCQIdecodingFailed.TSAMPL
VS.HsdpaCQIdecodingFailed.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 74 VS.HsdpaReceivedCQI0 - #33540

A-Description
Counting number of occassions where CQI value identical to 0 has been reported from a UE
using HSDPA. Counter does not include occassions where CQI decoding failed. (Cumulative)
B-Collection
CUMULATE

105
C-Condition (Event)
-
D-Result
E-Type
VS.HsdpaReceivedCQI0.CC
VS.HsdpaReceivedCQI0.AVG
VS.HsdpaReceivedCQI0.SDEV
VS.HsdpaReceivedCQI0.MIN
VS.HsdpaReceivedCQI0.MAX
VS.HsdpaReceivedCQI0.TSAMPL
VS.HsdpaReceivedCQI0.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description

106
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

107

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00

108
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7

109
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance

110
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance

111
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

112
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

113
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

114
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

115
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-

116
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection

117
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

118
A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd

119
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release

120
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range

121
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching

122
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

123
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

124
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

125
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

126
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

127
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)

128
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description

129
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

130

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00

131
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7

132
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance

133
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance

134
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

135
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

136
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

137
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

138
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 105 VS.HsdpaUEsPerCell - #33850

A-Description
Number of UE with HSDPA connections in the cell. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result

139
One measurement.
E-Type
VS.HsdpaUEsPerCell
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..64.0
J-Unit
UE
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes
Table 106 VS.eDCHcommonChannelsTxPower - #33860

A-Description
Total transmitted carrier power used for eDCH downlink system channels (E-AGCH, E-RGCH
and E-HICH). Reported as ratio [%] between - transmitted carrier power per TTI for the down-
link eDCH system channels: - and the maximum transmission power possible on that downlink
carrier during the same time interval. Maximum transmission power is the mean power [W] on
the RF carrier when the BTS transmits at the configured maximum transmission power of the
cell. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.eDCHcommonChannelsTxPower
F-Object Instance
BTSCell
G-Switching

140
H-3GPP Compliance
N
I-Range
0.0..100.0
J-Unit
%
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes
Table 107 VS.eDCHmWcommonChannelsTxPower - #33870

A-Description
Total transmitted carrier power in mW used for eDCH downlink system channels (E-AGCH, E-
RGCH and E-HICH) (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.eDCHmWcommonChannelsTxPower
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..2000.0
J-Unit
mW
K-Available Release
05_01_00
L-Aggregation Rule

141
Ravg
M-Notes
Table 108 VS.eDCHdataBitsSentToRNC - #33880

A-Description
Number of data bits sent RNC for eDCH data channels. Calculation includes all bits in the
MAC-d PDUs sent to RNC. MAC-es overhead is not included. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.eDCHdataBitsSentToRNC.CC
VS.eDCHdataBitsSentToRNC.AVG
VS.eDCHdataBitsSentToRNC.SDEV
VS.eDCHdataBitsSentToRNC.MIN
VS.eDCHdataBitsSentToRNC.MAX
VS.eDCHdataBitsSentToRNC.TSAMPL
VS.eDCHdataBitsSentToRNC.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit

142
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 109 VS.eDCHtranspBlockNoRetransmit - #33890

A-Description
Number of eDCH transport blocks acknowledged immediately without any retransmissions.
(Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.eDCHtranspBlockNoRetransmit.CC
VS.eDCHtranspBlockNoRetransmit.AVG
VS.eDCHtranspBlockNoRetransmit.SDEV
VS.eDCHtranspBlockNoRetransmit.MIN
VS.eDCHtranspBlockNoRetransmit.MAX
VS.eDCHtranspBlockNoRetransmit.TSAMPL
VS.eDCHtranspBlockNoRetransmit.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N

143
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 110 VS.eDCHtranspBlockRetransmit1 - #33900

A-Description
Number of eDCH transport blocks acknowledged after 1 retransmissions. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.eDCHtranspBlockRetransmit1.CC
VS.eDCHtranspBlockRetransmit1.AVG
VS.eDCHtranspBlockRetransmit1.SDEV
VS.eDCHtranspBlockRetransmit1.MIN
VS.eDCHtranspBlockRetransmit1.MAX
VS.eDCHtranspBlockRetransmit1.TSAMPL
VS.eDCHtranspBlockRetransmit1.NSAMPL
F-Object Instance
BTSCell
G-Switching

144
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance

145
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

146
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type

147
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

148
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

149
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result

150
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)

151
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

A-Description

152
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes

153

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule

154
Radd
M-Notes

A-Description
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit

155
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 121 VS.eDCHtranspBlockRetransmit12orMore - #34010

A-Description
Number of eDCH transport blocks acknowledged after 12 or more retransmissions.
(Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.eDCHtranspBlockRetransmit12orMore.CC
VS.eDCHtranspBlockRetransmit12orMore.AVG
VS.eDCHtranspBlockRetransmit12orMore.SDEV
VS.eDCHtranspBlockRetransmit12orMore.MIN
VS.eDCHtranspBlockRetransmit12orMore.MAX
VS.eDCHtranspBlockRetransmit12orMore.TSAMPL
VS.eDCHtranspBlockRetransmit12orMore.NSAMPL
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N

156
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 122 VS.eDCHtranspBlockDiscardedRetransm - #34020

A-Description
Number of eDCH transport block discarded due to that the limit for maximum number of re-
transmissions reached. (Cumulative)
B-Collection
CUMULATE
C-Condition (Event)
-
D-Result
E-Type
VS.eDCHtranspBlockDiscardedRetransm.CC
VS.eDCHtranspBlockDiscardedRetransm.AVG
VS.eDCHtranspBlockDiscardedRetransm.SDEV
VS.eDCHtranspBlockDiscardedRetransm.MIN
VS.eDCHtranspBlockDiscardedRetransm.MAX
VS.eDCHtranspBlockDiscardedRetransm.TSAMPL
VS.eDCHtranspBlockDiscardedRetransm.NSAMPL
F-Object Instance
BTSCell

157
G-Switching
H-3GPP Compliance
N
I-Range
0.0..214748364.7
J-Unit
K-Available Release
05_01_00
L-Aggregation Rule
Radd
M-Notes
Table 123 VS.eDCHdataBitsReceived - #34030

A-Description
Number of bits (before channel decoding) received at each eDCH TTI for all active connec-
tions. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.eDCHdataBitsReceived
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..32767.0
J-Unit
kbit
K-Available Release
05_01_00
L-Aggregation Rule

158
Ravg
M-Notes
Table 124 VS.eDCHactiveUsers - #34040

A-Description
Number of eDCH users which in a TTI have been given a grant and are currently transmitting
an eDPDCH. (Average)
B-Collection
LOAD
C-Condition (Event)
-
D-Result
One measurement.
E-Type
VS.eDCHactiveUsers
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.0..32.0
J-Unit
UE
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes
Table 125 VS.eDCHriseOverThermal - #34050

A-Description
The uplink power rise over thermal (RoT). (Average)
B-Collection
LOAD
C-Condition (Event)

159
-
D-Result
One measurement.
E-Type
VS.eDCHriseOverThermal
F-Object Instance
BTSCell
G-Switching
H-3GPP Compliance
N
I-Range
0.00..100.00
J-Unit
dB
K-Available Release
05_01_00
L-Aggregation Rule
Ravg
M-Notes

160
6 Micro Node B counter families

• #30010 VS.RTWP
• #30020 VS.RTWP_RxA
• #30030 VS.RTWP_RxB
• #30040 VS.TCP
• #30050 VS.TCP_dBm
• #30060 VS.TCP_Exceed90
• #30510 VS.NmbPrachPreamblDetect
• #30520 VS.NmbPrachPreamblAck
• #30530 VS.PrachCRCerror
• #30540 VS.PRACHload
• #30550 VS.SCCPCHload
• #31010 VS.NmbDedicatedRL
• #31020 VS.SIRsf4
• #31030 VS.SIRsf8
• #31040 VS.SIRsf16
• #31050 VS.SIRsf32
• #31060 VS.SIRsf64
• #31070 VS.SIRsf128
• #31080 VS.SIRsf256
• #31090 VS.ULCeConsumedDPCH
• #31100 VS.ULCeFreeForDPCH
• #31110 VS.DLCeConsumedDPCH
• #31120 VS.DLCeFreeForDPCH
• #31510 VS.CpLoad
• #31520 VS.BasebandLoad
• #31530 VS.BasebandCapAllocation
• #31540 VS.BaseBandCapAllocationReject
• #32010 VS.AAL2_LostCPS
• #32020 VS.AAL2_STFParityErrors
• #32030 VS.AAL2_SeqNmbErrors
• #32040 VS.AAL2_CPSHeaderChecksumErrors
• #32050 VS.AAL2_CPSLenErrors

161
• #32060 VS.AAL2_CPSLenMismatch
• #32070 VS.AAL2_NmbLostCPS
• #32080 VS.AAL2BandwidthAllocation
• #32090 VS.AAL2BandwidthUsageRatio
• #32100 VS.NmbFPmessages
• #32110 VS.FPCrcErrors
• #32510 VS.AAL5_TransmittedCells
• #32520 VS.AAL5_ReceivedCells
• #32530 VS.AAL5_AbortErrors
• #32540 VS.AAL5_LengthErrors
• #32550 VS.AAL5_CrcFrameErrors
• #32560 VS.AAL5_InvalidSize
• #33010 VS.TCP_ExceptHSDPA
• #33020 VS.TCP_HSPDSCH
• #33030 VS.TCP_HS_SCCH
• #33040 VS.HSDPA_PDSCH_codes
• #33050 VS.HSDPA_SCCHcodes
• #33060 VS.HSDPA_16QAMusage
• #33070 VS.HSDPA_MAC-D_PDU_ack_bits
• #33080 VS.HSDPA_PduRxBits
• #33090 VS.HSDPA_MacTxBits
• #33100 VS.HSDPA_TxDataBits
• #33110 VS.HSDPA_Ack
• #33120 VS.HSDPA_Nack
• #33130 VS.HSDPA_dtx
• #33140 VS.HSDPA_DiscardTimeout
• #33150 VS.HSDPA_DiscardedDueToMaxRetransmit
• #33160 VS.HSDPA_DiscardedDueToT1Timer
• #33170 VS.HSDPA_DiscardDueToMacHSWindow
• #33180 VS.HSDPA_TB_Retransmit0
• #33220 VS.HSDPA_TB_Retransmit_gt3

162
• #33230 VS.HSDPA_DataBuffered
• #33240 VS.HSDPA_TTIused
• #33500 VS.CellULload
• #33510 VS.FailedAdmissionsDueToULload
• #33520 VS.AdmissionRequestsULcac
• #33530 VS.HsdpaCQIdecodingFailed
• #33540 VS.HsdpaReceivedCQI0

163
• #33850 VS.HsdpaUEsPerCell
• #33860 VS.eDCHcommonChannelsTxPower
• #33870 VS.eDCHmWcommonChannelsTxPower
• #33880 VS.eDCHdataBitsSentToRNC
• #33890 VS.eDCHtranspBlockNoRetransmit
• #33900 VS.eDCHtranspBlockRetransmit1
• #34010 VS.eDCHtranspBlockRetransmit12orMore
• #34020 VS.eDCHtranspBlockDiscardedRetransm
• #34030 VS.eDCHdataBitsReceived
• #34040 VS.eDCHactiveUsers
• #34050 VS.eDCHriseOverThermal

164

W-CDMA
Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
Copyright © 2003-2009 Alcatel-Lucent, All Rights Reserved
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be altered
only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access
to the current issue. Any hardcopies taken must be regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as
expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the
information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third
parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained
herein. If you have received this document in error, please notify the sender and destroy it immediately.
Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks of Alcatel-Lucent, Alcatel
and Lucent Technologies.
All other trademarks are the property of their owners.
Document number: NN-20500-028

Document issue: 09.07
Document status: Standard
Product Release: OAM06.0
Date: April 2009

W-Cdma: Counters Reference Guide For Micronodeb

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

W-Cdma: Counters Reference Guide For Micronodeb

Uploaded by

Copyright:

Available Formats

NN-20500-028

Wireless Service Provider Solutions

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

Copyright © 2003-2009 Alcatel-Lucent, All Rights Reserved

All other trademarks are the property of their owners.

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

1 About this publication................................................................................................................................................... 9

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

Figure 1 - BTS containment tree........................................................................................................... ............. ......... 15

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Table 1 - Table of aggregation rules..................................................................................................... ............. ......... 20

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

Table 42 - VS.AAL5_AbortErrors - #32530........................................................................................... ............. ......... 67

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Table 84 - VS.HsdpaReceivedCQI10 - #33640.................................................................................... ............. ....... 115

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

1 About this publication

How this publication is organized

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Network observation counters.

A. Release Available Release

The specific terms used in this publication are the following:

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

2 Road map to UTRAN documentation

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

4 Access Network observation counters

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

4.1 How Access Network observation counters are defined

Figure 1 BTS containment tree

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Counter definition template

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Counter types on the OAM GUI :

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

• the minimum added value (.Min in XML files)

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

X.avg = (X1.cum + ... + Xn.cum) / (X1.nbevt + ...

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

4.2 How Access Network observation counters are described

Observation counters are stored in XML record files.

Access observation file structure

type is set to A which indicates one of the following aggregated observations:

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Refer to the following table for an interpretation of the codes:

Node B observation file

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

The directory of the RNC Node B observation file on PerfServer is as follows:

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

5 Micro Node B counter families

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

5.1 Radio Statistics

Alcatel-Lucent Counter name

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Alcatel-Lucent Counter name

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent

Alcatel-Lucent Counter name

Copyright © 2003-2009 Alcatel-Lucent Counters Reference Guide for MicroNodeB

Alcatel-Lucent Counter name

Table 2 VS.RTWP - #30010

NN-20500-028 09.07 Standard April 2009 Copyright © 2003-2009 Alcatel-Lucent