NN-20500-028P2 (NodeB Counters) 08.03 Standard November 2007

NN-20500-028

Wireless Service Provider Solutions

W-CDMAUMTS Access Network Counters Reference-Volume 2: BTS CountersNN-20500-028 08.03 Standard November 2007

Wireless Service Provider Solutions

W-CDMAUMTS Access Network Counters Reference- Volume 2:BTS Counters

Document number: NN-20500-028Document issue: 08.03Document status: StandardSystem release: OAM05.2Date: November 2007

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

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "writeprotected"; it may be altered only by authorized persons. While copies may be printed, it is notrecommended. Viewing of the master electronically ensures access to the current issue. Any hardcopiestaken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property ofAlcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep allinformation contained herein confidential, shall disclose the information only to its employees with a needto know, and shall protect the information from disclosure and dissemination to third parties. Except asexpressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the informationcontained herein. If you have received this document in error, please notify the sender and destroy itimmediately.

PUBLICATION HISTORYSYSTEM RELEASE OAM05.2

November 2007

Issue 08.03/EN Standard

Update for DR5.

September 2007

Issue 08.02/EN Preliminary

Update for OAM05.2 after internal review.

Resolution of the following CR :

• Q01741771

August 2007

Issue 08.01/EN Draft

Update for OAM05.2

SYSTEM RELEASE UMTS 5.1

July 2007


Update for UA 5.0 Channel Readiness.

Resolution of the following CR(s):

Q01641207

March 2007


Update after internal review.

November 2006


Update for OAM 5.1.0 / UA 5.0 [UMTS 5.1]

SYSTEM RELEASE UMTS V5.0

Alcatel-Lucent Confidential Publication history i

Copyright © 2003-2007 Alcatel-Lucent UMTS Access Network Counters Reference- Volume 2: BTSCounters

November 2006


Update for OAM 5.0.0.6 / UA 4.2.6 [UMTS V5.0 Post-ChR Load]

October 2006

Issue 06.07 N/A

October 2006


Update for OAM 5.0.0.5 / UA 4.2.5 [UMTS V5.0 Post-ChR Load]

July 2006


Update for Post-Channel Readiness

Resolution of the following CR :

• Q01408175

June 2006


Update for Post-Channel Readiness

April 2006


Update for Channel Readiness

November 2005


Update for RANV4.2 after internal review

October 2005


Update for RAN V4.2


October 2005

Alcatel-Lucent Confidential Publication history ii

NN-20500-028 08.03 Standard November 2007 Copyright © 2003-2007 Alcatel-Lucent


Update for RAN V4.1

August 2005


Update for RAN V4.1

Resolution of the following CRs :

• Q01173557

• Q01173549

• Q01173564

• Q01173750

June 2005


Update for RAN V4.1

Change of the NTP structure: review of the content and split into 3 volumes

March 2005


Update for Customer Readness after internal review

Resolution of the following CRs:

• Q00862233

• Q01033167

• Q01033176

• Q01034927

• Q01039681

February 2005


Update for RAN V4.1


February 2005


Alcatel-Lucent Confidential Publication history iii


Update for Channel Readness

November 2004



October 2004

Issue 04.04/EN Pre-standard

Update for Pre-Channel Readness

Resolution of the CR Q00982652

June 2004



May 2004


Update for RAN V4.0


March 2004



February 2004


Update for RAN V3.2


February 2004

Issue 03.04a/EN Standard


November 2003

Alcatel-Lucent Confidential Publication history iv




May 2003



April 2003


Update for RAN V3.1

March 2003


Update for RAN V3.1

Alcatel-Lucent Confidential Publication history v


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

2 Road map to UTRAN documentation........................................................................................................................... 4

3 What's new......................................................................................................................................................................5

4 Access Network observation counters........................................................................................................................6

4.1 How Access Network observation counters are defined........................................................................................... 7

4.2 How Access Network observation counters are described......................................................................................15

5 BTS counter families....................................................................................................................................................18

5.1 PCM statistics..........................................................................................................................................................19

5.2 ATM statistics.......................................................................................................................................................... 35

5.3 Radio counters.........................................................................................................................................................58

5.4 Radio statistics.........................................................................................................................................................67

5.5 CallP counters......................................................................................................................................................... 70

5.6 EEC......................................................................................................................................................................... 79

5.7 IMA statistics............................................................................................................................................................83

5.8 IP statistics...............................................................................................................................................................97

5.9 HSDPA statistics....................................................................................................................................................107

5.10 HSUPA statistics..................................................................................................................................................130

6 BTS Counters Index...................................................................................................................................................139

Alcatel-Lucent Confidential Table of contents vi


Figure 1 - BTS containment tree........................................................................................................... ............. ........... 8

Alcatel-Lucent Confidential List of figures vii


Table 1 - Table of aggregation rules..................................................................................................... ............. ......... 14

Table 2 - VS.PcmLos - #10001............................................................................................................. ............. ......... 19

Table 3 - VS.PcmAis - #10002.............................................................................................................. ............. ......... 20

Table 4 - VS.PcmLfa - #10003.............................................................................................................. ............. ......... 21

Table 5 - VS.PcmFe - #10004............................................................................................................................ ......... 22

Table 6 - VS.PcmCrc - #10005............................................................................................................. ............. ......... 23

Table 7 - VS.PcmRai - #10006........................................................................................................................... ......... 24

Table 8 - VS.PcmFas - #10007............................................................................................................. ............. ......... 25

Table 9 - VS.PcmEbits - #10008........................................................................................................... ............. ......... 26

Table 10 - VS.PcmBpvp - #10009...................................................................................................................... ......... 26

Table 11 - VS.PcmSlip - #10010........................................................................................................... ............. ......... 27

Table 12 - VS.PcmEs - #10011.......................................................................................................................... ......... 28

Table 13 - VS.PcmSes - #10012........................................................................................................................ ......... 29

Table 14 - VS.PcmBbe - #10013........................................................................................................................ ......... 30

Table 15 - VS.PcmUas - #10014........................................................................................................................ ......... 31

Table 16 - VS.PCMATMnbReceivedCell - #10015............................................................................... ............. ......... 32

Table 17 - VS.PCMATMnbSentCell - #10016....................................................................................... ............. ......... 33

Table 18 - VS.PCMthroughputCapacity - #10017................................................................................. ............. ......... 33

Table 19 - VS.AAL2NbLostCPS - #10102.......................................................................................................... ......... 36

Table 20 - VS.AAL2NbSTFParityErr - #10103...................................................................................... ............. ......... 36

Table 21 - VS.AAL2NbSequenceNumberErr - #10104......................................................................... ............. ......... 37

Table 22 - VS.AAL2NbCPSHecErr - #10105........................................................................................ ............. ......... 38

Table 23 - VS.AAL2NbCPSLengthErr - #10106................................................................................................. ......... 39

Table 24 - VS.AAL2NbCpsLengthMismatch - #10107.......................................................................... ............. ......... 40

Table 25 - VS.AAL2NbOSFBiggerThan47 - #10109............................................................................. ............. ......... 41

Table 26 - VS.AAL5NbAbortErr - #10111............................................................................................. ............. ......... 41

Table 27 - VS.AAL5NbLengthErr - #10112........................................................................................... ............. ......... 42

Table 28 - VS.AAL5NbCrcFrameErr - #10113...................................................................................... ............. ......... 43

Table 29 - VS.AAL5NbInvalidSize - #10114......................................................................................... ............. ......... 44

Table 30 - VS.AAL2NbReceivedCell - #10117................................................................................................... ......... 45

Table 31 - VS.AAL5NbReceivedCell - #10118................................................................................................... ......... 46

Table 32 - VS.AAL2NbSentCell - #10119............................................................................................. ............. ......... 47

Table 33 - VS.AAL5NbSentCell - #10120............................................................................................. ............. ......... 48

Table 34 - VS.CESSnLostCells - #10142........................................................................................................... ......... 48

Table 35 - VS.CESSnMisinsertCells - #10143...................................................................................... ............. ......... 49

Table 36 - VS.CESSnSeqce - #10144.................................................................................................. ............. ......... 50

Table 37 - VS.CESSpErrors - #10145................................................................................................................ ......... 51

Table 38 - VS.CESRxGov - #10146................................................................................................................... ......... 52

Table 39 - VS.CESTxGun - #10147...................................................................................................... ............. ......... 53

Table 40 - VS.CESReSync - #10148.................................................................................................... ............. ......... 54

Table 41 - VS.CESReceivedCells - #10149.......................................................................................... ............. ......... 55

Alcatel-Lucent Confidential List of tables viii


Table 42 - VS.CESSentCells - #10150................................................................................................. ............. ......... 56

Table 43 - VS.RadioWBandRxMainPwr - #10201.............................................................................................. ......... 58

Table 44 - VS.RadioWBandRxDivPwr - #10202................................................................................... ............. ......... 59

Table 45 - VS.PAPwr - #10204............................................................................................................. ............. ......... 60

Table 46 - VS.PAPwr - #10204............................................................................................................. ............. ......... 61

Table 47 - VS.PAPwr - #10204............................................................................................................. ............. ......... 62

Table 48 - VS.PAPwr - #10204............................................................................................................. ............. ......... 63

Table 49 - VS.RadioTxCarrierPwr - #10205....................................................................................................... ......... 64

Table 50 - VS.SIRperSF - #10206........................................................................................................ ............. ......... 65

Table 51 - VS.CellULload - #10211.................................................................................................................... ......... 67

Table 52 - VS.FailedAdmissionDueToULload - #10213..................................................................................... ......... 68

Table 53 - VS.CEMUsedDCH - #10301................................................................................................ ............. ......... 70

Table 54 - VS.RachNack - #10303..................................................................................................................... ......... 71

Table 55 - VS.RachNackSquare - #10304............................................................................................ ............. ......... 72

Table 56 - VS.RachAck - #10305....................................................................................................................... ......... 73

Table 57 - VS.RachAckSquare - #10306.............................................................................................. ............. ......... 74

Table 58 - VS.NodeBCidDchCollisionDetected - #10307..................................................................... ............. ......... 74

Table 59 - VS.NodeBCidCtchCollisionDetected - #10308.................................................................... ............. ......... 75

Table 60 - VS.CEMAlloc - #10309........................................................................................................ ............. ......... 76

Table 61 - VS.LocalCellGroupLoad - #10310....................................................................................... ............. ......... 77

Table 62 - VS.cpuLoad - #10403.......................................................................................................... ............. ......... 79

Table 63 - VS.cpuLoad - #10403.......................................................................................................... ............. ......... 80

Table 64 - VS.cpuLoad - #10403.......................................................................................................... ............. ......... 81

Table 65 - VS.cpuLoad - #10403.......................................................................................................... ............. ......... 81

Table 66 - VS.imaGroupUnavailSecs - #10601.................................................................................... ............. ......... 83

Table 67 - VS.imaGroupNeNumFailures - #10602............................................................................... ............. ......... 84

Table 68 - VS.imaLinkImaViolations - #10603...................................................................................... ............. ......... 85

Table 69 - VS.imaLinkNeSevErroredSecs - #10604............................................................................. ............. ......... 86

Table 70 - VS.imaLinkFeSevErroredSecs - #10605............................................................................. ............. ......... 87

Table 71 - VS.imaLinkNeUnavailSecs - #10606................................................................................... ............. ......... 87

Table 72 - VS.imaLinkFeUnavailSecs - #10607................................................................................................. ......... 88

Table 73 - VS.imaLinkNeTxUnusableSecs - #10608............................................................................ ............. ......... 89

Table 74 - VS.imaLinkNeRxUnusableSecs - #10609......................................................................................... ......... 90

Table 75 - VS.imaLinkFeTxUnusableSecs - #10610............................................................................ ............. ......... 91

Table 76 - VS.imaLinkFeRxUnusableSecs - #10611............................................................................ ............. ......... 92

Table 77 - VS.imaLinkNeTxNumFailures - #10612............................................................................... ............. ......... 92

Table 78 - VS.imaLinkNeRxNumFailures - #10613.............................................................................. ............. ......... 93

Table 79 - VS.imaGroupNbReceivedCell - #10614............................................................................................ ......... 94

Table 80 - VS.imaGroupNbSentCell - #10615...................................................................................... ............. ......... 95

Table 81 - VS.ifInOctets - #10701......................................................................................................... ............. ......... 97

Table 82 - VS.ifInUcastPkts - #10702................................................................................................... ............. ......... 98

Table 83 - VS.ifInNUcastPkts - #10703.............................................................................................................. ......... 99

Alcatel-Lucent Confidential List of tables ix


Table 84 - VS.ifInDiscards - #10704..................................................................................................... ............. ....... 100

Table 85 - VS.ifInErrors - #10705....................................................................................................................... ....... 100

Table 86 - VS.ifInUnknownProtos - #10706.......................................................................................... ............. ....... 101

Table 87 - VS.ifOutOctets - #10707...................................................................................................... ............. ....... 102

Table 88 - VS.ifOutUcastPkts - #10708................................................................................................ ............. ....... 103

Table 89 - VS.ifOutNUcastPkts - #10709.............................................................................................. ............. ....... 104

Table 90 - VS.ifOutDiscards - #10710................................................................................................................ ....... 105

Table 91 - VS.ifOutErrors - #10711.................................................................................................................... ....... 106

Table 92 - VS.HsdpaHSPDSCHTxPwr - #10801.................................................................................. ............. ....... 107

Table 93 - VS.HsdpaHSPDSCHCodesPerTTI - #10802....................................................................... ............. ....... 108

Table 94 - VS.HsdpaHSSCCHTxPwr - #10803.................................................................................... ............. ....... 109

Table 95 - VS.HsdpaHSSCCHCodesPerTTI - #10804......................................................................... ............. ....... 110

Table 96 - VS.Hsdpa16QAMUsage - #10805....................................................................................... ............. ....... 111

Table 97 - VS.HsdpaMACdPDUAckBits - #10806................................................................................ ............. ....... 112

Table 98 - VS.HsdpaRxDataBitsMAChs - #10807................................................................................ ............. ....... 113

Table 99 - VS.HsdpaTxDataBitsMAChs - #10808................................................................................ ............. ....... 114

Table 100 - VS.HsdpaTxDataBitsSchedTotal - #10809........................................................................ ............. ....... 115

Table 101 - VS.HsdpaNbrACKRcv - #10810........................................................................................ ............. ....... 116

Table 102 - VS.HsdpaNbrNACKRcv - #10811...................................................................................... ............. ....... 117

Table 103 - VS.HsdpaNbrDTX - #10812............................................................................................... ............. ....... 118

Table 104 - VS.HsdpaDiscMACdPDUsTimerExpiry - #10813.............................................................. ............. ....... 118

Table 105 - VS.HsdpaDiscTransportBlocksOnMaxRetrans - #10814................................................................ ....... 119

Table 106 - VS.HsdpaMeanNbrRetrans - #10815................................................................................ ............. ....... 120

Table 107 - VS.HsdpaDataBufferedNodeB - #10816......................................................................................... ....... 121

Table 108 - VS.HsdpaPAOverload - #10817........................................................................................ ............. ....... 122

Table 109 - VS.HsdpaTTIsUsed - #10818............................................................................................ ............. ....... 123

Table 110 - VS.HsdpaReceivedCQI - #10819...................................................................................... ............. ....... 124

Table 111 - VS.HsdpaUEsPerHBBU - #10820..................................................................................... ............. ....... 127

Table 112 - VS.HsdpaUEsPerLCG - #10821........................................................................................ ............. ....... 128

Table 113 - VS.eDCHcommonChannelsTxPower - #10901................................................................. ............. ....... 130

Table 114 - VS.eDCHdataBitSentToRNC - #10902.............................................................................. ............. ....... 131

Table 115 - VS.eDCHretransBlocks - #10903.................................................................................................... ....... 132

Table 116 - VS.eDCHdataBitRec - #10904........................................................................................... ............. ....... 133

Table 117 - VS.eDCHactiveUsers - #10905....................................................................................................... ....... 134

Table 118 - VS.eDCHriseOverThermal - #10906............................................................................................... ....... 135

Table 119 - VS.eDCHstatus - #10907................................................................................................................ ....... 136

Table 120 - VS.eDCHSFupsizingDuringCompressedMode - #10908................................................................ ....... 137

Table 121 - VS.eDCHUEsPerLCG - #10921...................................................................................................... ....... 137

Alcatel-Lucent Confidential List of tables x


1 About this publication

This publication provides a list of UMTS Access Network observation counters collected by theAPM/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 OAM05.2 System Release.

Audience

This publication is intended for network controllers responsible for the Performance Management ofthe UMTS Access Network.

Prerequisites

It is recommended that readers become familiar with the following Technical Publications :

• UMTS Access Network Overview (NN-20500-031) provides a functional overview of theOperation, Administration and Maintenance (OAM) subsystem of the Access Network.

Related publications• UMTS Access Network 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 thenew features introduced for the UMTS V5.1 release.

• "Access Network observation counters" is split into the following sections:

— "How Access Network observation counters are defined" provides information about thecounter definition template, counter types on the OAM GUI, and counter hierarchy.

Alcatel-Lucent Confidential 1


— "How Access Network observation counters are described" describes the AccessNetwork observation counters.

• "BTS counter families" lists BTS counter families and presents their counters. Each counter isdescribed 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 UMTS Access 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-uration

Pointer to a pre-defined set of Radio Bearers providing a given Ra-dio Access Bearer service.

For example:

• the Downlink (DL) access stratum configuration which number is1 is dedicated to voice support; it comprises the following RadioBearers : 3 x 12.2 Kbps CS RBs on DTCH and 3 x 3.4 KbpsSRB 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 KbpsSRB 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)



Connection Frame Num-ber (CFN)

CFN is the frame counter used for the L2/transport channel syn-chronisation between UE and UTRAN. A CFN value is associated toeach Transport Block Set (TBS) and it is passed together with itthrough 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 samemeaning 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 , thatmeans 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.



2 Road map to UTRAN documentation

For collection roadmaps information, see UMTS Access Document Collection - Overview and updatesummary (NN-20500-050).



3 What's new

For information about What's new section, see : UTRAN Release Operational Impacts(NN-20500-44), Annex C New/Deleted/Modified Counters.



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"



4.1 How Access Network observation counters are defined

A standard observation counter is a device used in Performance Management to calculate thenumber of occurrences of an event. For further definitions for observation counters, refer to 3GPP TS32.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 countersis attached to a given UMTS feature. For example the "Radio Link Management Family" groupstogether 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



For more information about UTRAN objects and their relationships, refer to the UMTS AccessNetwork Overview (NN-20500-031) publication.

Wording assumption

Both wordings counter and measurement are equally used in this document to identify the sameconcept. 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 15minutes, while a measurement is elaborated on periods expressed in milliseconds, for example : 500ms.

3GPP Performance Management specifications preferably use measurement. When the contextrefers to 3GPP specifications, measurement is used, while counter is used in Alcatel-Lucentspecific part, but both wordings are equivalent.

Counter definition template

The following template used to describe the counters is extracted from 3GPP TS 32.104specifications.

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 ncan 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 themeasurement processes or by updating the current measurement result value. When a precise



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). Ifmore than one value is provided, the measurement is screened according to criteria, for example, anumber 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 varioussubcounters and their meanings.

E-Type

This section contains a short form of the measurement name specified in the header, which is usedto identify the measurement type in the result files.

F-Object Instance

This section contains the object class and its instance. The "measObjInstId" field identifies themeasured 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 inaccordance with 3GPP TS 32.106. This means the NE or resource object model (defined in the BasicCM IRP Information Model - 3GPP TS 32.106-5) and naming conventions (defined in the NamingConvention for Managed Objects - 3GPP TS 32.106-8). This parameter, if applicable, will beprovided in the measurement job.

G-Switching

This section contains the Switching domain(s). Its measurement is applicable to Circuit Switchedand, or Packet Switched domains.

Note: Two counter specification items have been added to the seven preceding 3GPP items byAlcatel-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 compliantwith the 3GPP specification.

• the statement is "Alcatel-Lucent specified counter" if the counter is not considered by the 3GPPspecification.

I-Range

This section contains the range of the counter.



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

L-Aggregation Rule

This section contains one of these three values :RLoad, RVal and Rtotal. Each value defines theaggregation rule type. The counter type defines the aggregation rule value.

M-Notes

This section contains notes and FRS numbers associated with the counters.

Three types of counters :

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 eventoccurs, and it provides the cumulative value. One NE cumulative counter provides one counter at theOAM GUI level.

VALUE counters

VALUE counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order toimplement a DER (VAL) type measurement. This mechanism provides average values from rawcounts obtained by internal events (the time interval between two events is random and is notaccessible 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)



• 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 toimplement an SI type measurement. This mechanism provides average values from raw countsobtained by internal sampling (the time interval between two events is constant and is not accessibleto 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 becauseproviding the current value of a measurement by incrementing it by 1 when a positive event occursand by decrementing it by 1 when a negative event occurs, can lead to some shifts if an event ismissed.

Note: The reported value counter is collected by a non real time task at the end of eachobservation period. The collection period (usually one hour) for the Performance Management filedoes not imply that all .NbEvt of LOAD counters are exactly equal to the number of counterperiods included in one collection (12 for counters with 5mn granularity). Due to the low priority ofthe Performance Management task, it is possible when the PM file is built that some samples canmiss. They will be included in the next file. This can lead to one file with NbEvt equal to 11 (for a5mn counter), followed later by one with 13 (possibly with some 12 between). The averagesvalues calculated by computing .Cum/.NbEvt are still meaningful, as the samples added in .Cumare 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



Aggregation rules

When aggregating counters from different periods of observation (temporal aggregation) you mustfollow the following rules.

Let X1,X2,...,Xn the measurements from periods 1,2,...,n and X the resulting value over the totalperiod.

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

X.nbevt = X1.nbevt + ... + Xn.nbevt

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

X.min = min (X1.min,...,Xn.min)

X.max = max (X1.max,...,Xn.max)

Some LOAD and VALcounters

Rload* Same as Rload but resulting X.cum has no phys-ical meaning due to the nature of the measure-ment (like percents) and is not interpreted but isnecessary for intermediate computations.

Some LOAD counters

Ravg X = Xi / n

where Xi (i = 1 to n) represent average values

Passport counters

Radd X = ΣXi

where Xi (i = 1 to n) represent cumulative values

Passport counters

Rmin X = min (Xi)

where Xi (i = 1 to n) represent minimum values

Passport counters

Rmax X = max (Xi)

where Xi (i = 1 to n) represent maximum values

Passport counters



4.2 How Access Network observation counters are described

An observation counter is a measurement used to report data for network PerformanceManagement.

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 V5.1 systemrelease 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"

• "BTS counter families"

• "Passport counter families"

Each counter family is attached to a given UMTS feature (for example, Handover counters, wherehard 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. Thefollowing observation counter records are available:

• single period

• hourly aggregated

• daily aggregated

Each observation file produces single, hourly and daily observation counter records. At the dedicatedNE 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.

• 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

• POCOr 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 fiveminutes: 00, 05, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55. In the case ofhourly or daily aggregation files, mm is always 00.

#GMT Difference between local time and Greenwich Meridian Time (+/-hhmm). At10:15:02 in Paris, the 13 April 2005 in Paris, the #GMT is +0100 = thehhmm#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 NodeB 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)

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 UMTS Access Network PerformanceManagement (NN-20500-033) publication.



5 BTS counter families

• PCM statistics

• ATM statistics

• Radio counters

• Radio statistics

• CallP counters

• EEC

• IMA statistics

• IP statistics

• HSDPA statistics

• HSUPA statistics



5.1 PCM statistics

The PCM alarms statistics consist in statistics information about the PCM faulty seconds. Asdescribed in "UMT/BSS/DD/0210 Requirements Specification for PCM Interface", each second hasthe characteristic of being faulty or not faulty. A faulty second is one in which at least one PCM alarmwas detected for that second. Even if the PCM alarm duration is less than that second, the secondshall be declared as faulty. A faulty second is always associated with the highest ranking alarm thathas occurred during that second. So, for each PCM alarm, a counter shall be defined which willincrement every faulty seconds associated with that alarm.

Alcatel-Lucentcounter number

Counter name

#10001 VS.PcmLos

#10002 VS.PcmAis

#10003 VS.PcmLfa

#10004 VS.PcmFe

#10005 VS.PcmCrc

#10006 VS.PcmRai

#10007 VS.PcmFas

#10008 VS.PcmEbits

#10009 VS.PcmBpvp

#10010 VS.PcmSlip

#10011 VS.PcmEs

#10012 VS.PcmSes

#10013 VS.PcmBbe

#10014 VS.PcmUas

#10015 VS.PCMATMnbReceivedCell

#10016 VS.PCMATMnbSentCell

#10017 VS.PCMthroughputCapacity

Table 2 VS.PcmLos - #10001

A-Description

Number of faulty seconds due to Loss Of incoming Signal alarm (LOS alarm)

B-Collection

CUM

CUM



C-Condition (Event)

A LOS defect is detected when the incoming signal has no transition (i.e. when the level of thesignal is less than or equal to a signal level of 35 dB below nominal), for N consecutive pulseintervals, with N comprised between 10 and 255 (E1), or between 100 and 250 (T1)

D-Result

one measurement

E-Type

VS.PcmLos

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ITU-T G775 compliant-#10001

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 3 VS.PcmAis - #10002

A-Description

Number of faulty seconds due to Alarm Indication Signal (AIS alarm)

B-Collection

CUM

CUM

C-Condition (Event)

An AIS defect is detected when the incoming signal : (E1) has two or less ZEROs in each oftwo consecutive double frame periods (512 bits). (T1) signal with ONEs density of at least99.9% present for a time equal to or greater than T, where T is in the range 3 ms to 75 ms.



D-Result

one measurement

E-Type

VS.PcmAis

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 4 VS.PcmLfa - #10003

A-Description

Number of faulty seconds due to Loss of Frame Alignment (LFA) alarm

B-Collection

CUM

CUM

C-Condition (Event)

An LFA defect is detected when : (E1) three consecutive incorrect frame alignment signalshave been received, or bit 2 in time slot 0 in frames not containing the frame alignment signalhas been received with an error on three consecutive occasions. (T1) the frame alignment sig-nal should be monitored to determine if frame alignment has been lost. Loss of frame align-ment should be detected within 12ms. Loss of frame alignment must be confirmed over severalframes to avoid the unnecessary initiation of the frame alignment recovery procedure due totransmission bit errors.

D-Result



one measurement

E-Type

VS.PcmLfa

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 5 VS.PcmFe - #10004

A-Description

Number of faulty seconds due to framing Event (FE) alarm (excessive bit error ratio detectedby monitoring the frame alignment signal)

B-Collection

CUM

CUM

C-Condition (Event)

Number of faulty seconds due to Framing Event alarm (excessive bit error ratio detected bymonitoring the frame alignment signal) : 22 FAS /sec; Note : this counter is meanlingless incase of T1 lines, but observation files prepared for OMC-B will still contain it valued to zero.

D-Result

one measurement

E-Type

VS.PcmFe

F-Object Instance



PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 6 VS.PcmCrc - #10005

A-Description

Number of faulty seconds due to CRC (Cyclic Redundancy Check) alarm (loss of multi-framealignment)

B-Collection

CUM

CUM

C-Condition (Event)

CRC alarm (loss of multi-frame alignment): 915 CRC4 errors / sec ;Note : this counter is mean-lingless in case of T1 lines, but observation files prepared for OMC-B will still contain it valuedto zero.

D-Result

one measurement

E-Type

VS.PcmCrc

F-Object Instance

PCMLink

G-Switching

NA



H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 7 VS.PcmRai - #10006

A-Description

Number of faulty seconds due to RAI (Remote Alarm Indication) alarm indicating that the re-mote equipment does not receive coherent data from the local equipment

B-Collection

CUM

CUM

C-Condition (Event)

Remote alarm indication received by the local equipment

D-Result

one measurement

E-Type

VS.PcmRai

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit



second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 8 VS.PcmFas - #10007

A-Description

number of Frame Alignment Signal received in error

B-Collection

CUM

CUM

C-Condition (Event)

each time a Frame Alignment Signal is received in error. The counter is disabled during the re-ceive loss of synchronization conditions.

D-Result

one measurement

E-Type

VS.PcmFas

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ALCATEL-LUCENT specified counter-#10007

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal



Table 9 VS.PcmEbits - #10008

A-Description

Number of received E-bits set to 0 indicating that the remote equipment received the corres-ponding sub-multi-frame with an errored CRC4 code

B-Collection

CUM

CUM

C-Condition (Event)

each time an E-bit set to zero is received. The counter is disabled during loss of framing ormulti-framing synchronization. Note : this counter is meanlingless in case of T1 lines, but ob-servation files prepared for OMC-B will still contain it valued to zero.

D-Result

one measurement

E-Type

VS.PcmEbits

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 10 VS.PcmBpvp - #10009

A-Description

Number of consecutive BiPolar Violations of the same polarity detected on the received line



per second. Counter shall increment even if framing alignment is not succeeded (it saturates at65535 errors)

B-Collection

CUM

CUM

C-Condition (Event)

each time consecutive bipolar violations of the same polarity detected on the received line isdetected.

D-Result

one measurement

E-Type

VS.PcmBpvp

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 11 VS.PcmSlip - #10010

A-Description

Number of seconds during which at least one slip event occurred. A slip event is defined as therepetition or deletion of a frame on receive or transmit side.

B-Collection

CUM

CUM



C-Condition (Event)

each first slip event in a second

D-Result

one measurement

E-Type

VS.PcmSlip

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 12 VS.PcmEs - #10011

A-Description

Number of Errored second(s) during the available time periods of the last supervision period.(default value of supervision period in ITU-T G826 is 5 minutes)

B-Collection

CUM

CUM

C-Condition (Event)

A second with at least one FAS or one Errored Block) or one (LOS or AIS or LFA) event

D-Result

one measurement

E-Type



VS.PcmEs

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 13 VS.PcmSes - #10012

A-Description

Number of Severely Errored Seconds during the available time periods of the last supervisionperiod. (default value of supervision period in ITU-T G826 is 5 minutes)

B-Collection

CUM

CUM

C-Condition (Event)

A second with at least 300 E1 (100 T1) FAS or 30 % Errored Block or one (LOS or AIS or LFA)event

D-Result

one measurement

E-Type

VS.PcmSes

F-Object Instance

PCMLink

G-Switching



NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 14 VS.PcmBbe - #10013

A-Description

number of Background Block Errors during the available time periods of the last supervisionperiod. (default value of supervision period in ITU-T G826 is 5 minutes).

B-Collection

CUM

CUM

C-Condition (Event)

Triggering event: FAS or Errored Block event occuring at a time not included in an SES

D-Result

one measurement

E-Type

VS.PcmBbe

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1



J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 15 VS.PcmUas - #10014

A-Description

number of Severely UnAvailable Seconds during the last supervision period.

B-Collection

CUM

CUM

C-Condition (Event)

FBT consecutive SES (FBT is in range 2 .. 60 and default value is 14

D-Result

one measurement

E-Type

VS.PcmUas

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

second

K-Available Release

V1.0

L-Aggregation Rule



Rtotal

Table 16 VS.PCMATMnbReceivedCell - #10015

A-Description

the number of cells received for the PCM link. The sampling is made at a frequency of onesecond.

B-Collection

LOAD

LOAD

C-Condition (Event)

D-Result

one measurement

E-Type

VS.PCMATMnbReceivedCell

F-Object Instance

PCMATM

G-Switching

NA

H-3GPP Compliance

N-#10015

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

not to be reported for PCMs included in an IMA group (replaced by #10614 in this case)

FRS :

• 30069 UA5.0 counters



Table 17 VS.PCMATMnbSentCell - #10016

A-Description

the number of cells sent on the PCM link. The sampling is made at a frequency of one second.

B-Collection

LOAD

LOAD

C-Condition (Event)

D-Result

one measurement

E-Type

VS.PCMATMnbSentCell

F-Object Instance

PCMATM

G-Switching

NA

H-3GPP Compliance

N-#10016

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

not to be reported for PCMs included in an IMA group (replaced by #10615 in this case)

FRS :


Table 18 VS.PCMthroughputCapacity - #10017

A-Description



give the useful throughput of all PCMs. The sampling is made at a frequency of one second.

B-Collection

LOAD

LOAD

C-Condition (Event)

D-Result

A set of subcounters screened on: configurated and operational throughputs

• Sub-Counter #0 : Configured throughput

• Sub-Counter #1 : Operational throughput

E-Type

• VS.PCMthroughputCapacity.Config

• VS.PCMthroughputCapacity.Oper

F-Object Instance

BTSEquipment

G-Switching

NA

H-3GPP Compliance

N-#10017

I-Range

0-2^31-1

J-Unit

Kbit/s

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

FRS :




5.2 ATM statistics

Note : Those counters will also be reported for the VCC used by OAM. This VCC is not included inthe configuration file provided by OMC-B. Instead it is implicitly created by iBTS, and its counters willbe reported to OMC-B with a pre-defined instance number set to 0xFF FF FF FF. OMC-B will have torecognize this value as being a special case i.e. checking that the instance value is in OMC-Bdatabase, is not performed. VCC's are separated in three different locations, ATMVCCAAL1 (forCES), ATMVCCAAL2 and ATMVCCAAL5. The counters associated to CES (Circuit Emulation) arenot available in this Release.


Counter name

#10102 VS.AAL2NbLostCPS

#10103 VS.AAL2NbSTFParityErr

#10104 VS.AAL2NbSequenceNumberErr

#10105 VS.AAL2NbCPSHecErr

#10106 VS.AAL2NbCPSLengthErr

#10107 VS.AAL2NbCpsLengthMismatch

#10109 VS.AAL2NbOSFBiggerThan47

#10111 VS.AAL5NbAbortErr

#10112 VS.AAL5NbLengthErr

#10113 VS.AAL5NbCrcFrameErr

#10114 VS.AAL5NbInvalidSize

#10117 VS.AAL2NbReceivedCell

#10118 VS.AAL5NbReceivedCell

#10119 VS.AAL2NbSentCell

#10120 VS.AAL5NbSentCell

#10142 VS.CESSnLostCells

#10143 VS.CESSnMisinsertCells

#10144 VS.CESSnSeqce

#10145 VS.CESSpErrors

#10146 VS.CESRxGov

#10147 VS.CESTxGun

#10148 VS.CESReSync

#10149 VS.CESReceivedCells

#10150 VS.CESSentCells



Table 19 VS.AAL2NbLostCPS - #10102

A-Description

the number of lost CPS packets for one user plane ATM PVC

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.AAL2NbLostCPS

F-Object Instance

ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance

N-#10102

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 20 VS.AAL2NbSTFParityErr - #10103

A-Description

the number of received CPS PDU with parity error for one user plane ATM PVC

B-Collection

CUM

CUM



C-Condition (Event)

D-Result

one measurement

E-Type

VS.AAL2NbSTFParityErr

F-Object Instance

ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance

N-#10103

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 21 VS.AAL2NbSequenceNumberErr - #10104

A-Description

the number of received CPS PDU with a sequence number error for one user plane ATM PVC

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.AAL2NbSequenceNumberErr

F-Object Instance



ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance

N-#10104

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 22 VS.AAL2NbCPSHecErr - #10105

A-Description

the number of received CPS packets with a Header checksum error for one user plane ATMPVC.

B-Collection

CUM

CUM

C-Condition (Event)

The counter is increased on detection of a Header checksum error.

D-Result

one measurement

E-Type

VS.AAL2NbCPSHecErr

F-Object Instance

ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance




I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 23 VS.AAL2NbCPSLengthErr - #10106

A-Description

the number of received CPS packets with a wrong length for one user plane ATM PVC.

B-Collection

CUM

CUM

C-Condition (Event)

The counter is increased on detection of a length different from LI field content in CPS packet.

D-Result

one measurement

E-Type

VS.AAL2NbCPSLengthErr

F-Object Instance

ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release



V1.0

L-Aggregation Rule

Rtotal

Table 24 VS.AAL2NbCpsLengthMismatch - #10107

A-Description

the number of received CPS packets with a length mismatch for one user plane ATM PVC. (LIfield in CPS packet mismatch with OSF field in CPS PDU)

B-Collection

CUM

CUM

C-Condition (Event)

The counter is increased on detection of a LI field content in CPS packet different from OSFfield content in CPS PDU .

D-Result

one measurement

E-Type

VS.AAL2NbCpsLengthMismatch

F-Object Instance

ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal



Table 25 VS.AAL2NbOSFBiggerThan47 - #10109

A-Description

the number of received CPS PDUs with an OSF field value > 47 for one user plane ATM PVC.

B-Collection

CUM

CUM

C-Condition (Event)

The counter is increased on detection of a OSF field value > 47

D-Result

one measurement

E-Type

VS.AAL2NbOSFBiggerThan47

F-Object Instance

ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 26 VS.AAL5NbAbortErr - #10111

A-Description

the number of cells dropped on peer demand for one control plane ATM PVC.

B-Collection

CUM

CUM



C-Condition (Event)

The counter is increased on peer demand to drop a cell.

D-Result

one measurement

E-Type

VS.AAL5NbAbortErr

F-Object Instance

ATMVCCAAL5

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 27 VS.AAL5NbLengthErr - #10112

A-Description

the number of AAL5 frames with a wrong size for one control plane ATM PVC (the size is dif-ferent from the trailer value)

B-Collection

CUM

CUM

C-Condition (Event)

The counter is increased on detection of a wrong size of a frame.

D-Result

one measurement

E-Type



VS.AAL5NbLengthErr

F-Object Instance

ATMVCCAAL5

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 28 VS.AAL5NbCrcFrameErr - #10113

A-Description

the number of received AAL5 frames with a wrong CRC for one control plane ATM PVC (theCRC is different from the trailer value)

B-Collection

CUM

CUM

C-Condition (Event)

The counter is increased on detection of a CRC different the trailer value .

D-Result

one measurement

E-Type

VS.AAL5NbCrcFrameErr

F-Object Instance

ATMVCCAAL5

G-Switching

NA



H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 29 VS.AAL5NbInvalidSize - #10114

A-Description

the number of AAL5 frames with an invalid size for one control plane ATM PVC.

B-Collection

CUM

CUM

C-Condition (Event)

The counter is increased on detection of a frame size larger than the maximum frame size.

D-Result

one measurement

E-Type

VS.AAL5NbInvalidSize

F-Object Instance

ATMVCCAAL5

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit



EVENT

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 30 VS.AAL2NbReceivedCell - #10117

A-Description

the number of cells received for one user plane ATM PVC. The sampling is made at a fre-quency of one second.

B-Collection

LOAD

LOAD

C-Condition (Event)

D-Result

one measurement

E-Type

VS.AAL2NbReceivedCell

F-Object Instance

ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance

N-#10117

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes



evolution of #10101 (was CUM)

FRS :


Table 31 VS.AAL5NbReceivedCell - #10118

A-Description

the number of correctly received cells per control plane ATM PVC.

B-Collection

LOAD

LOAD

C-Condition (Event)

The counter is increased on a cell reception (except if the cell is in error).

D-Result

one measurement

E-Type

VS.AAL5NbReceivedCell

F-Object Instance

ATMVCCAAL5

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes


FRS :




Table 32 VS.AAL2NbSentCell - #10119

A-Description

the number of sent cells for one user plane ATM PVC.

B-Collection

LOAD

LOAD

C-Condition (Event)

The counter is increased on a cell emission.

D-Result

one measurement

E-Type

VS.AAL2NbSentCell

F-Object Instance

ATMVCCAAL2

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes


FRS :




Table 33 VS.AAL5NbSentCell - #10120

A-Description

the number of sent cells for one control plane ATM PVC.

B-Collection

LOAD

LOAD

C-Condition (Event)

The counter is increased on a cell emission.

D-Result

one measurement

E-Type

VS.AAL5NbSentCell

F-Object Instance

ATMVCCAAL5

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes


FRS :


Table 34 VS.CESSnLostCells - #10142



A-Description

Number of AAL1 lost cells. Not supported in this release.

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.CESSnLostCells

F-Object Instance

ATMVCCAAL1

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :

• 25069 CES introduction

Table 35 VS.CESSnMisinsertCells - #10143

A-Description

Number of AAL1 misinserted cells. Not supported in this release.

B-Collection

CUM



CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.CESSnMisinsertCells

F-Object Instance

ATMVCCAAL1

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 36 VS.CESSnSeqce - #10144

A-Description

Number of Sequence Count Errors (SCE). Not supported in this release.

B-Collection

CUM

CUM

C-Condition (Event)

D-Result



one measurement

E-Type

VS.CESSnSeqce

F-Object Instance

ATMVCCAAL1

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 37 VS.CESSpErrors - #10145

A-Description

Number of structure pointer errors (Sp). Not supported in this release.

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.CESSpErrors

F-Object Instance



ATMVCCAAL1

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 38 VS.CESRxGov - #10146

A-Description

Number of Rx slip counter (overrun). Not supported in this release.

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.CESRxGov

F-Object Instance

ATMVCCAAL1

G-Switching

NA



H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 39 VS.CESTxGun - #10147

A-Description

Number of Tx slip (underrun). Not supported in this release.

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.CESTxGun

F-Object Instance

ATMVCCAAL1

G-Switching

NA

H-3GPP Compliance


I-Range



0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 40 VS.CESReSync - #10148

A-Description

Number of AAL1 resynchronized. Not supported in this release.

B-Collection

CUM

CUM

C-Condition (Event)

It can be (1) pointer reframes (2) slip event (3) 2 consecutive cells with errors (4) 2 consecutivepointers with errors

D-Result

one measurement

E-Type

VS.CESReSync

F-Object Instance

ATMVCCAAL1

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit



EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 41 VS.CESReceivedCells - #10149

A-Description

Number of valid cells received from ATM network. Not supported in this release.

B-Collection

LOAD

LOAD

C-Condition (Event)

D-Result

one measurement

E-Type

VS.CESReceivedCells

F-Object Instance

ATMVCCAAL1

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0



L-Aggregation Rule

Rload

M-Notes


FRS :


Table 42 VS.CESSentCells - #10150

A-Description

Number of valid cells sent to ATM network. Not supported in this release.

B-Collection

LOAD

LOAD

C-Condition (Event)

D-Result

one measurement

E-Type

VS.CESSentCells

F-Object Instance

ATMVCCAAL1

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes




FRS :




5.3 Radio counters

Radio counters production Radio counters are physically located in TRM modules. A TRM cansupport multiple cells/sectors/frequencies. A sector may have different Cell-ID depending on thefrequency plane. CCM do not need to identify TRM for the PM counters, all radio counters exceptMCPA power counter should be identified with cell id (BTSCell object / instance id) which is uniqueper frequency per sector. For example, in STSR2 configurations, 2 TRM will manage 6 cells. TRM 1will manage all 6 Tx cells (cell id 1-6, frequency f1 and frequency f2 on Alpha, Beta, Gamma sectors)and 3 Rx cells (cell id 1-3, frequency f1 on Alpha, Beta, Gamma sector) and TRM 2 will manage 3 Rxcells (cell id 4-6, frequency f2 on Alpha, Beta, Gamma sectors). Upon receiving a PM Request, TRM1 will send Tx power counters for cell id 1-6, and Rx pwr counters for cell id 1-3. TRM 2 will send Rxpower counters for cell id 4-6. CCM just need to pack all the Tx and Rx power counters for cell id 1together in the loadCounterList for BTSCell 1 ObservedObject. Same for the other cell Ids. Inaddition, the min, max, average calculation period is the associated PM collecting period. For radiocounters, PM requests can occur every 15 minutes (or 60 minutes) so calculation period will be 15minutes (respectively 60 minutes). Counters are reset at each PM request. Mapping The power isreported in dBm with a 0.1dB resolution: Power (dB) = (int32 Value) / 10


Counter name

#10201 VS.RadioWBandRxMainPwr

#10202 VS.RadioWBandRxDivPwr

#10204 VS.PAPwr

#10204 VS.PAPwr

#10204 VS.PAPwr

#10204 VS.PAPwr

#10205 VS.RadioTxCarrierPwr

#10206 VS.SIRperSF

Table 43 VS.RadioWBandRxMainPwr - #10201

A-Description

average wide-band received power on the main antenna - at the Rx main channelizer- for eachcell (per sector and per frequency). The averaged value over the observation period is calcu-lated directly by the BTS at the end of the observation period (and the number of samples isset to 1). The minimum and maximum powers during the observation period are also provided.

B-Collection

LOAD

LOAD



C-Condition (Event)

A sampling event generated every 100 ms

D-Result

one measurement

E-Type

VS.RadioWBandRxMainPwr

F-Object Instance

BTSCell

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

10-12 mW

K-Available Release

V1.0

L-Aggregation Rule

Rload

M-Notes

the .Cum value is limited to 0x7FFFFFFF

Table 44 VS.RadioWBandRxDivPwr - #10202

A-Description

average wide-band received power on the diversity antenna - at the Rx diversity channelizer -for each cell (per sector and per frequency) on the observation period. The averaged valueover the observation period is calculated directly by the BTS at the end of the observation peri-od (and the number of samples is set to 1). The minimum and maximum powers during the ob-servation period are also provided.

B-Collection

LOAD

LOAD

C-Condition (Event)




D-Result

one measurement

E-Type

VS.RadioWBandRxDivPwr

F-Object Instance

BTSCell

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

10-12 mW

K-Available Release

V1.0

L-Aggregation Rule

Rload

M-Notes

the .Cum value is limited to 0x7FFFFFFF

Table 45 VS.PAPwr - #10204

A-Description

min/max/linear average of the MCPA power detected

B-Collection

LOAD

LOAD

C-Condition (Event)

a sampling event generated every 1 second (mean power during 1 s).

D-Result

one measurement

E-Type



VS.PAPwr

F-Object Instance

PassiveComponent/PA

G-Switching

NA

H-3GPP Compliance

N-#10204

I-Range

0-2^31-1

J-Unit

mW

K-Available Release

V1.0

L-Aggregation Rule

Rload

M-Notes

(old name : MCPAPwr)


A-Description

min/max/linear average of the PALLET power detected

B-Collection

LOAD

LOAD

C-Condition (Event)


D-Result

one measurement

E-Type

VS.PAPwr

F-Object Instance

PassiveComponent/PA/PALLET

G-Switching



NA

H-3GPP Compliance

N-#10204

I-Range

0-2^31-1

J-Unit

mW

K-Available Release

V4.1

L-Aggregation Rule

Rload

M-Notes


FRS :

• 25877 TRIPA introduction


A-Description

min/max/linear average of the PA (included in the DDM-RK) power detected

B-Collection

LOAD

LOAD

C-Condition (Event)


D-Result

one measurement

E-Type

VS.PAPwr

F-Object Instance

PassiveComponent/DDM/PA

G-Switching

NA

H-3GPP Compliance



N-#10204

I-Range

0-2^31-1

J-Unit

mW

K-Available Release

V4.3K

L-Aggregation Rule

Rload

M-Notes


FRS :

• 30800 Subway iBTS


A-Description

min/max/linear average of the PA (included in the RRH) power detected

B-Collection

LOAD

LOAD

C-Condition (Event)


D-Result

one measurement

E-Type

VS.PAPwr

F-Object Instance

Board/RRH

G-Switching

NA

H-3GPP Compliance

N-#10204

I-Range



0-2^31-1

J-Unit

mW

K-Available Release

V4.2

L-Aggregation Rule

Rload

M-Notes


FRS :

• 29926 RRH introduction

Table 49 VS.RadioTxCarrierPwr - #10205

A-Description

average value of the total transmitted power - at the Tx channelizer - for each cell (i.e. per sec-tor and per frequency). The cumulated value at the end of the observation period and the num-ber of samples are provided. The minimum and maximum powers during the reporting periodare also provided.

B-Collection

LOAD

LOAD

C-Condition (Event)


D-Result

A set of subcounters screened on: distribution according thresholds

• Sub-Counter #0 : Operational Max Power

• Sub-Counter #1 : Power used

E-Type

• VS.RadioTxCarrierPwr.Oper

• VS.RadioTxCarrierPwr.Used

F-Object Instance

BTSCell

G-Switching

NA



H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

mW

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

replace #10203 : screening added (screening 1 is equal to #10203)

FRS :


Table 50 VS.SIRperSF - #10206

A-Description

signal to interference ratio for all communications with one SF (UpLink)

B-Collection

VAL

VAL

C-Condition (Event)

sampling events generated every 200 ms, one per communication

D-Result

A set of subcounters screened on: distribution according SF

• Sub-Counter #0 : For SF4







E-Type



• VS.SIRperSF.SF4

• VS.SIRperSF.SF8

• VS.SIRperSF.SF16





F-Object Instance

BTSEquipment

G-Switching

NA

H-3GPP Compliance

N-#10206

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rval

M-Notes

FRS :




5.4 Radio statistics


Counter name

#10211 VS.CellULload

#10213 VS.FailedAdmissionDueToULload

Table 51 VS.CellULload - #10211

A-Description

The mean UL Load value

B-Collection

LOAD

LOAD

C-Condition (Event)

At each Load estimation: fixed period depending on RNC filtering parameter.

D-Result

one measurement

E-Type

VS.CellULload

F-Object Instance

BTSCell

G-Switching

NA

H-3GPP Compliance

N-#10211

I-Range

0-1000

J-Unit

0.1%

K-Available Release

V5.0

L-Aggregation Rule



Rload

M-Notes

this counter is not significant if the RTWP measures are not activated (default value: 0).

FRS :

• 27745 UL load management

Table 52 VS.FailedAdmissionDueToULload - #10213

A-Description

Total number of failed UL admission due to excessive load in the cell. TheVS.FailedAdmissionDueToUlLoad.min and VS.FailedAdmissionDueToULload.Max are notused. The initial values are respectively 2147483648 and 0.

B-Collection

VAL

VAL

C-Condition (Event)

At each UL admission proposed by RNC

D-Result

one measurement

E-Type

VS.FailedAdmissionDueToULload

F-Object Instance

BTSCell

G-Switching

NA

H-3GPP Compliance

N-#10213

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule



Rval

M-Notes

this counter is not significant if the RTWP measures are not activated (default value: 0).

FRS :

• 27745 UL load management



5.5 CallP counters


Counter name

#10301 VS.CEMUsedDCH

#10303 VS.RachNack

#10304 VS.RachNackSquare

#10305 VS.RachAck

#10306 VS.RachAckSquare

#10307 VS.NodeBCidDchCollisionDetected

#10308 VS.NodeBCidCtchCollisionDetected

#10309 VS.CEMAlloc

#10310 VS.LocalCellGroupLoad

Table 53 VS.CEMUsedDCH - #10301

A-Description

min/max/avg of the ratio between the CEM capacity used and the total CEM capacity that wasavailable at the BTS startup, restricted to DCH.

B-Collection

LOAD

LOAD

C-Condition (Event)

a sampling event generated by the CCM CallP every 5 seconds that gets the current percent-age of CEM used (restricted to DCH : HSxPA are excluded)

D-Result

one measurement

E-Type

VS.CEMUsedDCH

F-Object Instance

BTSEquipment

G-Switching

NA

H-3GPP Compliance



N-#10301

I-Range

0-100

J-Unit

percentage

K-Available Release

V1.0

L-Aggregation Rule

Rload

M-Notes

name changed from "CEMUsed" (in UA5.0)

Table 54 VS.RachNack - #10303

A-Description

The number of refused Random accesses (RACH NACK) sent in a BTSCell, measured foreach TTI : - the number of refused Random accesses during the reporting period is given bythe cumulating part (.Cum). - the maximum number of refused random accesses recorded in aTTI window is given by the maximum part (.Max) - the minimum number of refused random ac-cesses recorded in a TTI window is given by the minimum part (.Min) - the average number ofrefused random accesses per TTI window is given by the average part (.Avg) - the number ofTTI windows during the reporting period is given by the number of events part (.NbEvt) Hencethe ratio mNack = (cumulated value / N) yields the mean number of RACH Nack per TTI. forthe BTSCell

B-Collection

LOAD

LOAD

C-Condition (Event)

The measurement is based on the sampling (at each TTI) of the number of RACH NACK dur-ing the TTI (10 ms for RACH).

D-Result

one measurement

E-Type

VS.RachNack

F-Object Instance

BTSCell

G-Switching



NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 55 VS.RachNackSquare - #10304

A-Description

the sum of squares of the number of refused random accesses in a cell during a reporting peri-od. It allows to compute the standard deviation of RACH Nack per TTI with the formula(SQNack / N) - meanNACK2

B-Collection

CUM

CUM

C-Condition (Event)

End of a TTI window.

D-Result

one measurement

E-Type

VS.RachNackSquare

F-Object Instance

BTSCell

G-Switching

NA

H-3GPP Compliance


I-Range



0-2^31-1

J-Unit

EVENT

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 56 VS.RachAck - #10305

A-Description

the number of accepted Random accesses (RACH ACK) sent in a cell during a reporting peri-od.

B-Collection

CUM

CUM

C-Condition (Event)


D-Result

one measurement

E-Type

VS.RachAck

F-Object Instance

BTSCell

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V3.1



L-Aggregation Rule

Rtotal

Table 57 VS.RachAckSquare - #10306

A-Description

the sum of squares of the number of accepted random accesses in a cell during a reportingperiod. It allows to compute the standard deviation of RACH Ack per TTI with the formula(SQAck / N) - meanACK2

B-Collection

CUM

CUM

C-Condition (Event)


D-Result

one measurement

E-Type

VS.RachAckSquare

F-Object Instance

BTSCell

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT per TTI

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 58 VS.NodeBCidDchCollisionDetected - #10307



A-Description

Number of time that a CID included in channel establishment request is already used by Dedic-ated Channel according to the Node B

B-Collection

CUM

CUM

C-Condition (Event)

reception of channel establishment request (either NBAP RL Setup Req or Common TransportChannel Setup Req) with a CID already used by Dedicated Channel.

D-Result

one measurement

E-Type

VS.NodeBCidDchCollisionDetected

F-Object Instance

BTSEquipment

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 59 VS.NodeBCidCtchCollisionDetected - #10308

A-Description

Number of CID collision with an already established Common channel detected in the NodeB

B-Collection

CUM

CUM



C-Condition (Event)

Detection of a CID collision with an already established CTCH

D-Result

one measurement

E-Type

VS.NodeBCidCtchCollisionDetected

F-Object Instance

BTSEquipment

G-Switching

NA

H-3GPP Compliance

N-#10308

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 60 VS.CEMAlloc - #10309

A-Description

number of times allocation of CEM resources succeeded, and failed (due to no CEM resourceavailable).

B-Collection

CUM

CUM

C-Condition (Event)

when the CCM Load Balancing Get_Resource is called

D-Result

A set of subcounters screened on: success/fail of the allocation

• Sub-Counter #0 : Allocation success



• Sub-Counter #1 : Allocation fail

E-Type

• VS.CEMAlloc.success

• VS.CEMAlloc.fail

F-Object Instance

LocalCellGroup

G-Switching

NA

H-3GPP Compliance

N-#10309

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

M-Notes

replace #10302 : screening added

FRS :


Table 61 VS.LocalCellGroupLoad - #10310

A-Description

number of CE (channel elements) used for a local cell group (restricted to DCH).

B-Collection

LOAD

LOAD

C-Condition (Event)

a sampling event generated by the CCM CallP every 5 seconds

D-Result



A set of subcounters screened on: free and used capacity, UL and DL

• Sub-Counter #0 : Free UL capacity

• Sub-Counter #1 : Used UL capacity

• Sub-Counter #2 : Free DL capacity

• Sub-Counter #3 : Used DL capacity

E-Type

• VS.LocalCellGroupLoad.FreeUL

• VS.LocalCellGroupLoad.UsedUL

• VS.LocalCellGroupLoad.FreeDL

• VS.LocalCellGroupLoad.UsedDL

F-Object Instance

LocalCellGroup

G-Switching

NA

H-3GPP Compliance

N-#10310

I-Range

0-2^31-1

J-Unit

number of CE

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

FRS :




5.6 EEC

The instance of EEC logs refer to the slot number of the cards that are collected from.


Counter name

#10403 VS.cpuLoad

#10403 VS.cpuLoad

#10403 VS.cpuLoad

#10403 VS.cpuLoad

Table 62 VS.cpuLoad - #10403

A-Description

% CPU load

B-Collection

LOAD

LOAD

C-Condition (Event)

each 5 minutes the mean load is reported. The .Min and .Max values are updated each 2seconds.

D-Result

one measurement

E-Type

VS.cpuLoad

F-Object Instance

Board/CCM

G-Switching

NA

H-3GPP Compliance

N-#10403

I-Range

0-100

J-Unit



percentage

K-Available Release

V1.0

L-Aggregation Rule

Rload


A-Description

% CPU load

B-Collection

LOAD

LOAD

C-Condition (Event)


D-Result

one measurement

E-Type

VS.cpuLoad

F-Object Instance

Board/CEM

G-Switching

NA

H-3GPP Compliance

N-#10403

I-Range

0-100

J-Unit

percentage

K-Available Release

V1.0

L-Aggregation Rule

Rload




A-Description

% CPU load

B-Collection

LOAD

LOAD

C-Condition (Event)


D-Result

one measurement

E-Type

VS.cpuLoad

F-Object Instance

Board/TRM

G-Switching

NA

H-3GPP Compliance

N-#10403

I-Range

0-100

J-Unit

percentage

K-Available Release

V1.0

L-Aggregation Rule

Rload


A-Description

% CPU load

B-Collection



LOAD

LOAD

C-Condition (Event)


D-Result

one measurement

E-Type

VS.cpuLoad

F-Object Instance

Board/RRH

G-Switching

NA

H-3GPP Compliance

N-#10403

I-Range

0-100

J-Unit

percentage

K-Available Release

V4.2

L-Aggregation Rule

Rload

M-Notes

FRS :

• 29926 RRH introduction



5.7 IMA statistics


Counter name

#10601 VS.imaGroupUnavailSecs

#10602 VS.imaGroupNeNumFailures

#10603 VS.imaLinkImaViolations

#10604 VS.imaLinkNeSevErroredSecs

#10605 VS.imaLinkFeSevErroredSecs

#10606 VS.imaLinkNeUnavailSecs

#10607 VS.imaLinkFeUnavailSecs

#10608 VS.imaLinkNeTxUnusableSecs

#10609 VS.imaLinkNeRxUnusableSecs

#10610 VS.imaLinkFeTxUnusableSecs

#10611 VS.imaLinkFeRxUnusableSecs

#10612 VS.imaLinkNeTxNumFailures

#10613 VS.imaLinkNeRxNumFailures

#10614 VS.imaGroupNbReceivedCell

#10615 VS.imaGroupNbSentCell

Table 66 VS.imaGroupUnavailSecs - #10601

A-Description

Count of one second invervals where the IMA Group Traffic State Machine is down

B-Collection

CUM

CUM

C-Condition (Event)

IMA Group State Machine is down

D-Result

one measurement

E-Type

VS.imaGroupUnavailSecs

F-Object Instance

IMAgroup



G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : GR-UAS-IMA-#10601

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 67 VS.imaGroupNeNumFailures - #10602

A-Description

The number of times a near-end group failure (Config-Aborted, Insufficient-links) has been re-ported since power-up or reboot.

B-Collection

CUM

CUM

C-Condition (Event)

IMA near-end group failure (Config-Aborted, Insufficient-links)

D-Result

one measurement

E-Type

VS.imaGroupNeNumFailures

F-Object Instance

IMAgroup

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : GR-FC-#10602

I-Range



0-2^31-1

J-Unit

EVENT

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 68 VS.imaLinkImaViolations - #10603

A-Description

ICP violations : count of errored, invalid or missing ICP cells, except during SES-IMA (SeverelyErrored Seconds) or UAS-IMA (Unavailable Seconds) conditions (this counter will not excludefaulty ICP cells during SES-IMA and UAS-IMA conditions).

B-Collection

CUM

CUM

C-Condition (Event)

Reception of an errored, invalid or missing ICP cell

D-Result

one measurement

E-Type

VS.imaLinkImaViolations

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : IV-IMA-#10603

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release



V3.0

L-Aggregation Rule

Rtotal

Table 69 VS.imaLinkNeSevErroredSecs - #10604

A-Description

Count of one second intervals containing >= 30% of the ICP cells counted as IV-IMAs, or oneor more link defects (e.g., LOS, OOF/LOF, AIS, or LCD), LIF (Loss of IMA Frame) defects, orLODS (Link Out Of Delay Synchronization)

B-Collection

CUM

CUM

C-Condition (Event)

Incremented each time the last second window is considered in severed error

D-Result

one measurement

E-Type

VS.imaLinkNeSevErroredSecs

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : SES-IMA-#10604

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule

Rtotal



Table 70 VS.imaLinkFeSevErroredSecs - #10605

A-Description

Count of one second intervals containing one or more RDI-IMA (Remote Defect Indicator) de-fects, except during UAS-IMA-FE (Far End Unavailable Seconds) condition

B-Collection

CUM

CUM

C-Condition (Event)

Incremented each time there is at least one RDI-IMA during the last second window

D-Result

one measurement

E-Type

VS.imaLinkFeSevErroredSecs

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : SES-IMA-FE-#10605

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 71 VS.imaLinkNeUnavailSecs - #10606

A-Description

Count of unavailable seconds at near-end: unavailability begins at the onset of 10 contiguousSES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA

B-Collection



CUM

CUM

C-Condition (Event)

Begin with 10 contiguous SES-IMA. Stop with 10 contiguous seconds with no SES-IMA.

D-Result

one measurement

E-Type

VS.imaLinkNeUnavailSecs

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : UAS-IMA-#10606

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 72 VS.imaLinkFeUnavailSecs - #10607

A-Description

Count of unavailable seconds at far-end: unavailability begins at the onset of 10 contiguousSES-IMA-FE and ends at the onset of 10 contiguous seconds with no SES-IMA-FE.

B-Collection

CUM

CUM

C-Condition (Event)

Begin with 10 contiguous SES-IMA-FEtop with 10 contiguous seconds with no SES-IMA-FE

D-Result



one measurement

E-Type

VS.imaLinkFeUnavailSecs

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : UAS-IMA-FE-#10607

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 73 VS.imaLinkNeTxUnusableSecs - #10608

A-Description

Tx Unusable seconds at the near-end Tx LSM (Link State Machine)

B-Collection

CUM

CUM

C-Condition (Event)

Incremented each time the near-end Tx LSM can not transmit during the last one-second win-dow

D-Result

one measurement

E-Type

VS.imaLinkNeTxUnusableSecs

F-Object Instance

PCMLink



G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : Tx-UUS-IMA-#10608

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 74 VS.imaLinkNeRxUnusableSecs - #10609

A-Description

Rx Unusable seconds at the near-end Rx LSM (Link State Machine)

B-Collection

CUM

CUM

C-Condition (Event)

Incremented each time the near-end Rx LSM can not receive during the last one-second win-dow

D-Result

one measurement

E-Type

VS.imaLinkNeRxUnusableSecs

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : Rx-UUS-IMA-#10609

I-Range



0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 75 VS.imaLinkFeTxUnusableSecs - #10610

A-Description

Tx Unusable seconds at the far-end Tx LSM (Link State Machine)

B-Collection

CUM

CUM

C-Condition (Event)

Incremented each time the far-end Tx LSM can not transmit during the last one-second window

D-Result

one measurement

E-Type

VS.imaLinkFeTxUnusableSecs

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : Tx-UUS-IMA-FE-#10610

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule



Rtotal

Table 76 VS.imaLinkFeRxUnusableSecs - #10611

A-Description

Rx Unusable seconds at the far-end Rx LSM (Link State Machine)

B-Collection

CUM

CUM

C-Condition (Event)

Incremented each time the far-end Rx LSM can not receive during the last one-second window

D-Result

one measurement

E-Type

VS.imaLinkFeRxUnusableSecs

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : Rx-UUS-IMA-FE-#10611

I-Range

0-2^31-1

J-Unit

second

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 77 VS.imaLinkNeTxNumFailures - #10612

A-Description

The number of times a near-end transmit failure alarm condition has been entered on this link.(i.e. some form of implementation specific transmit fault). This counter will not take into accountthe fault Tx-Mis-Connected (i.e. Tx link is not connected to the same Far End IMA unit as the



other Tx link in the group).

B-Collection

CUM

CUM

C-Condition (Event)

A near-end transmit failure alarm

D-Result

one measurement

E-Type

VS.imaLinkNeTxNumFailures

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : Tx-FC-#10612

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 78 VS.imaLinkNeRxNumFailures - #10613

A-Description

The number of times a near-end receive failure alarm condition has been entered on this link(i.e., LIF, LODS, RFI-IMA, Mis-Connected or some form of implementation specific receivefault). This counter will not take into account the fault Rx-Mis-Connected (i.e. Rx link is not con-nected to the same Far End IMA unit as the other Rx link in the group).

B-Collection

CUM

CUM



C-Condition (Event)

A near-end receive failure alarm

D-Result

one measurement

E-Type

VS.imaLinkNeRxNumFailures

F-Object Instance

PCMLink

G-Switching

NA

H-3GPP Compliance

ATM Forum - IMA Specification v 1.1 (af-phy-0086.001) : Rx-FC-#10613

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 79 VS.imaGroupNbReceivedCell - #10614

A-Description

the number of ATM cells received for the IMA group. The sampling is made at a frequency ofone second.

B-Collection

LOAD

LOAD

C-Condition (Event)

D-Result

one measurement

E-Type

VS.imaGroupNbReceivedCell



F-Object Instance

IMAgroup

G-Switching

NA

H-3GPP Compliance

N-#10614

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

FRS :


Table 80 VS.imaGroupNbSentCell - #10615

A-Description

the number of ATM cells sent for the IMA group. The sampling is made at a frequency of onesecond.

B-Collection

LOAD

LOAD

C-Condition (Event)

D-Result

one measurement

E-Type

VS.imaGroupNbSentCell

F-Object Instance

IMAgroup

G-Switching



NA

H-3GPP Compliance

N-#10615

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

FRS :




5.8 IP statistics

The list of counters is established according to the MIB for Management of TCP/IP networks definedby IETF: "IETF RFC 1213 MIB for Network Management of TCP/IP based internets". It is restricted tothe Interfaces Group of this specification (for a justification, please refer to section 4.3.2 of"UMT/BTS/DD/0484 FN 13490 Site LAN").


Counter name

#10701 VS.ifInOctets

#10702 VS.ifInUcastPkts

#10703 VS.ifInNUcastPkts

#10704 VS.ifInDiscards

#10705 VS.ifInErrors

#10706 VS.ifInUnknownProtos

#10707 VS.ifOutOctets

#10708 VS.ifOutUcastPkts

#10709 VS.ifOutNUcastPkts

#10710 VS.ifOutDiscards

#10711 VS.ifOutErrors

Table 81 VS.ifInOctets - #10701

A-Description

The total number of octets received on the interface, including framing characters

B-Collection

CUM

CUM

C-Condition (Event)

Reception of an IP packet on the IP Interface

D-Result

one measurement

E-Type

VS.ifInOctets

F-Object Instance

IPinterface



G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifInOctets-#10701

I-Range

0-2^31-1

J-Unit

byte

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 82 VS.ifInUcastPkts - #10702

A-Description

The number of subnetwork-unicast packets delivered to a higher-layer protocol

B-Collection

CUM

CUM

C-Condition (Event)

Reception of a subnetwork-unicast packet

D-Result

one measurement

E-Type

VS.ifInUcastPkts

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifInUcastPkts-#10702

I-Range



0-2^31-1

J-Unit

packet

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 83 VS.ifInNUcastPkts - #10703

A-Description

The number of non-unicast (broadcast and multicast) packets delivered to a higher-layer pro-tocol

B-Collection

CUM

CUM

C-Condition (Event)

Reception of a non-unicast packet

D-Result

one measurement

E-Type

VS.ifInNUcastPkts

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifInNUcastPkts-#10703

I-Range

0-2^31-1

J-Unit

packet

K-Available Release

V3.0



L-Aggregation Rule

Rtotal

Table 84 VS.ifInDiscards - #10704

A-Description

The number of inbound packets which were chosen to be discarded even though no errors hadbeen detected to prevent their being deliverable to a higher-layer protocol. One possible reas-on for discarding such a packet could be to free up buffer space.

B-Collection

CUM

CUM

C-Condition (Event)

Discard of a received IP packet

D-Result

one measurement

E-Type

VS.ifInDiscards

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifInDiscards-#10704

I-Range

0-2^31-1

J-Unit

packet

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 85 VS.ifInErrors - #10705



A-Description

The number of inbound packets that contained errors preventing them from being deliverableto a higher-layer protocol.

B-Collection

CUM

CUM

C-Condition (Event)

Reception of an erroneous IP packet

D-Result

one measurement

E-Type

VS.ifInErrors

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifInErrors-#10705

I-Range

0-2^31-1

J-Unit

packet

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 86 VS.ifInUnknownProtos - #10706

A-Description

The number of packets received via the interface which were discarded because of an un-known or unsupported protocol

B-Collection

CUM

CUM



C-Condition (Event)

Reception of an unknown or unsupported IP packet

D-Result

one measurement

E-Type

VS.ifInUnknownProtos

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifInUnknownProtos-#10706

I-Range

0-2^31-1

J-Unit

packet

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 87 VS.ifOutOctets - #10707

A-Description

The total number of octets transmitted out of the interface, including framing characters

B-Collection

CUM

CUM

C-Condition (Event)

Emission of an IP packet on the interface

D-Result

one measurement

E-Type

VS.ifOutOctets



F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifOutOctets-#10707

I-Range

0-2^31-1

J-Unit

byte

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 88 VS.ifOutUcastPkts - #10708

A-Description

The total number of packets that higher-level protocols requested be transmitted to a unicastaddress, including those that were discarded or not sent

B-Collection

CUM

CUM

C-Condition (Event)

Submission of a unicast IP packet by higher layer

D-Result

one measurement

E-Type

VS.ifOutUcastPkts

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance



IETF : RFC 1213 : ifOutUcastPkts-#10708

I-Range

0-2^31-1

J-Unit

packet

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 89 VS.ifOutNUcastPkts - #10709

A-Description

The total number of packets that higher-level protocols requested be transmitted to a non- uni-cast (broadcast or multicast) address, including those that were discarded or not sent

B-Collection

CUM

CUM

C-Condition (Event)

Submission of a non-unicast packet by higher layer

D-Result

one measurement

E-Type

VS.ifOutNUcastPkts

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifOutNUcastPkts-#10709

I-Range

0-2^31-1

J-Unit

packet



K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 90 VS.ifOutDiscards - #10710

A-Description

The number of outbound packets which were chosen to be discarded even though no errorshad been detected to prevent their being transmitted. One possible reason for discarding sucha packet could be to free up buffer space.

B-Collection

CUM

CUM

C-Condition (Event)

Discard of an IP packet submitted by higher layer

D-Result

one measurement

E-Type

VS.ifOutDiscards

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifOutDiscards-#10710

I-Range

0-2^31-1

J-Unit

packet

K-Available Release

V3.0

L-Aggregation Rule

Rtotal



Table 91 VS.ifOutErrors - #10711

A-Description

The number of outbound packets that could not be transmitted because of errors

B-Collection

CUM

CUM

C-Condition (Event)

Emission of an IP packet that contains error

D-Result

one measurement

E-Type

VS.ifOutErrors

F-Object Instance

IPinterface

G-Switching

NA

H-3GPP Compliance

IETF : RFC 1213 : ifOutErrors-#10711

I-Range

0-2^31-1

J-Unit

packet

K-Available Release

V3.0

L-Aggregation Rule

Rtotal



5.9 HSDPA statistics

These are 500 TTI per second (2 ms). Kbit means 1024 bits, and the values are rounded to thenearest value. So the following calculation is made , if X is the value in bits: (X+512)/1024


Counter name

#10801 VS.HsdpaHSPDSCHTxPwr

#10802 VS.HsdpaHSPDSCHCodesPerTTI

#10803 VS.HsdpaHSSCCHTxPwr

#10804 VS.HsdpaHSSCCHCodesPerTTI

#10805 VS.Hsdpa16QAMUsage

#10806 VS.HsdpaMACdPDUAckBits

#10807 VS.HsdpaRxDataBitsMAChs

#10808 VS.HsdpaTxDataBitsMAChs

#10809 VS.HsdpaTxDataBitsSchedTotal

#10810 VS.HsdpaNbrACKRcv

#10811 VS.HsdpaNbrNACKRcv

#10812 VS.HsdpaNbrDTX

#10813 VS.HsdpaDiscMACdPDUsTimerExpiry

#10814 VS.HsdpaDiscTransportBlocksOnMaxRetrans

#10815 VS.HsdpaMeanNbrRetrans

#10816 VS.HsdpaDataBufferedNodeB

#10817 VS.HsdpaPAOverload

#10818 VS.HsdpaTTIsUsed

#10819 VS.HsdpaReceivedCQI

#10820 VS.HsdpaUEsPerHBBU

#10821 VS.HsdpaUEsPerLCG

Table 92 VS.HsdpaHSPDSCHTxPwr - #10801

A-Description

Total transmitted power on all allocated HS-PDSCH codes per TTI.

B-Collection

LOAD

LOAD

C-Condition (Event)



Each TTI

D-Result

one measurement

E-Type

VS.HsdpaHSPDSCHTxPwr

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

100 mW

K-Available Release

V4.2

L-Aggregation Rule

Rload

M-Notes

FRS :

• 27932 HSDPA introduction

Table 93 VS.HsdpaHSPDSCHCodesPerTTI - #10802

A-Description

Number of HS-PDSCH codes used per TTI.

B-Collection

LOAD

LOAD

C-Condition (Event)

Each TTI (note that there are 500 TTI of 2ms each per second)

D-Result



one measurement

E-Type

VS.HsdpaHSPDSCHCodesPerTTI

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rload

M-Notes

FRS :


Table 94 VS.HsdpaHSSCCHTxPwr - #10803

A-Description

Total power on all transmitted HS-SCCH codes per TTI.

B-Collection

LOAD

LOAD

C-Condition (Event)

Each TTI

D-Result

one measurement

E-Type

VS.HsdpaHSSCCHTxPwr



F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

100 mW

K-Available Release

V4.2

L-Aggregation Rule

Rload

M-Notes

FRS :


Table 95 VS.HsdpaHSSCCHCodesPerTTI - #10804

A-Description

Number of HS-SCCH codes used per TTI. It then indicates the number of scheduled UEs inthe TTI.

B-Collection

LOAD

LOAD

C-Condition (Event)

Each TTI

D-Result

one measurement

E-Type

VS.HsdpaHSSCCHCodesPerTTI

F-Object Instance

BTSCellHSDPA



G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rload

M-Notes

FRS :


Table 96 VS.Hsdpa16QAMUsage - #10805

A-Description

Number of scheduled mobiles using 16QAM.

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.Hsdpa16QAMUsage

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance




I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 97 VS.HsdpaMACdPDUAckBits - #10806

A-Description

Total number of successfully transmitted MAC-d PDU bits (an ACK has been received for thecorresponding transport block).

B-Collection

LOAD

LOAD

C-Condition (Event)

Each TTI

D-Result

one measurement

E-Type

VS.HsdpaMACdPDUAckBits

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range



0-2^31-1

J-Unit

Kbit

K-Available Release

V4.2

L-Aggregation Rule

Rload

M-Notes

FRS :


Table 98 VS.HsdpaRxDataBitsMAChs - #10807

A-Description

Total number of data bits received by the NodeB. It corresponds to the bits of all the MAC-dPDUs received in every FP data frame.

B-Collection

VAL

VAL

C-Condition (Event)

FP data frame received without error

D-Result

one measurement

E-Type

VS.HsdpaRxDataBitsMAChs

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit



Kbit

K-Available Release

V4.2

L-Aggregation Rule

Rval

M-Notes

FRS :


Table 99 VS.HsdpaTxDataBitsMAChs - #10808

A-Description

Total number of data bits (transport block size) first transmitted by the MAC-hs. The retrans-missions are then not taken into account, meaning that a block retransmitted several times isonly taken into account once at the first transmission.

B-Collection

VAL

VAL

C-Condition (Event)

Each first transmitted block (retransmissions are excluded)

D-Result

one measurement

E-Type

VS.HsdpaTxDataBitsMAChs

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

Kbit



K-Available Release

V4.2

L-Aggregation Rule

Rval

M-Notes

FRS :


Table 100 VS.HsdpaTxDataBitsSchedTotal - #10809

A-Description

Total number of data bits (transport block size) scheduled any TTI, taking into account the re-transmissions. Any time a block is retransmitted, its bits are added.

B-Collection

VAL

VAL

C-Condition (Event)

Each transmitted block

D-Result

one measurement

E-Type

VS.HsdpaTxDataBitsSchedTotal

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

Kbit

K-Available Release

V4.2



L-Aggregation Rule

Rval

M-Notes

FRS :


Table 101 VS.HsdpaNbrACKRcv - #10810

A-Description

Number of acknowledged transport blocks ('ACK' received for a transmitted transport block).Remark: ACK + NACK + DTX = Total number of transmitted transport blocks.

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.HsdpaNbrACKRcv

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes



FRS :


Table 102 VS.HsdpaNbrNACKRcv - #10811

A-Description

Number of negatively acknowledged transport blocks ('NACK' received for a transmitted trans-port block).

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.HsdpaNbrNACKRcv

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :




Table 103 VS.HsdpaNbrDTX - #10812

A-Description

Number of DTX detected (neither 'ACK' nor 'NACK' received for a transmitted transport block).

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.HsdpaNbrDTX

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 104 VS.HsdpaDiscMACdPDUsTimerExpiry - #10813

A-Description

Number of MAC-d PDUs that have been discarded due to 'discard timer' expiration.



B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.HsdpaDiscMACdPDUsTimerExpiry

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 105 VS.HsdpaDiscTransportBlocksOnMaxRetrans - #10814

A-Description

Number of transport blocks that have been discarded because the maximum number of re-transmissions was reached.

B-Collection

CUM

CUM



C-Condition (Event)

D-Result

one measurement

E-Type

VS.HsdpaDiscTransportBlocksOnMaxRetrans

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 106 VS.HsdpaMeanNbrRetrans - #10815

A-Description

Number of necessary retransmissions for acknowledged Transport blocks (0 means the blockhas been correctly received after the first transmission). The blocks discarded due to the max-imum number of retransmissions reached are not taken into account.

B-Collection

VAL

VAL

C-Condition (Event)

Block send correctly (ACK received)



D-Result

one measurement

E-Type

VS.HsdpaMeanNbrRetrans

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rval

M-Notes

FRS :


Table 107 VS.HsdpaDataBufferedNodeB - #10816

A-Description

Total number of data Kbits (MAC-d PDU bits) buffered in NodeB. Each 100ms, the counter isupdated by the averaged value during this period. Min and max values are nevertheless up-dated on a TTI basis.

B-Collection

LOAD

LOAD

C-Condition (Event)

Each 100ms

D-Result



one measurement

E-Type

VS.HsdpaDataBufferedNodeB

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

Kbit

K-Available Release

V4.2

L-Aggregation Rule

Rload

M-Notes

FRS :


Table 108 VS.HsdpaPAOverload - #10817

A-Description

Number of periods for which the total transmitted power (measurement received from PMM)exceeded 90% of the maximum cell power configured.

B-Collection

CUM

CUM

C-Condition (Event)

Reception of ATM cell indicating PMM measurement

D-Result

one measurement

E-Type



VS.HsdpaPAOverload

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 109 VS.HsdpaTTIsUsed - #10818

A-Description

Number of TTIs containing at least one scheduled UE. It allows new statistics to be derived forsome previous counters.

B-Collection

CUM

CUM

C-Condition (Event)

D-Result

one measurement

E-Type

VS.HsdpaTTIsUsed

F-Object Instance

BTSCellHSDPA



G-Switching

NA

H-3GPP Compliance


I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 110 VS.HsdpaReceivedCQI - #10819

A-Description

level of quality reception for HSDPA

B-Collection

CUM

CUM

C-Condition (Event)

when a CQI is received

D-Result

A set of subcounters screened on: distribution according CQI

• Sub-Counter #0 : For level 0

































• Sub-Counter #31 : CQI not detected

E-Type

• VS.HsdpaReceivedCQI.level0

































• VS.HsdpaReceivedCQI.notDecoded

F-Object Instance

BTSCellHSDPA

G-Switching

NA

H-3GPP Compliance

N-#10819

I-Range

0-2^31-1

J-Unit



EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

M-Notes

FRS :


Table 111 VS.HsdpaUEsPerHBBU - #10820

A-Description

Number of UEs configured in the H-BBU

B-Collection

LOAD

LOAD

C-Condition (Event)

Each 5s (Min and Max updated for any setup/delete/mobility of UE)

D-Result

one measurement

E-Type

VS.HsdpaUEsPerHBBU

F-Object Instance

HSDPAresource

G-Switching

NA

H-3GPP Compliance

N-#10820

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release



V5.0

L-Aggregation Rule

Rload

M-Notes

the configured cells on this H-BBU are the one using the hsdpaResourceId (defined in the Cellconfiguration)

FRS :

• 29801 48-user HSDPA

Table 112 VS.HsdpaUEsPerLCG - #10821

A-Description

Number of HSDPA UEs configured in the LocalCellGroup

B-Collection

LOAD

LOAD

C-Condition (Event)


D-Result

one measurement

E-Type

VS.HsdpaUEsPerLCG

F-Object Instance

LocalCellGroup

G-Switching

NA

H-3GPP Compliance

N-#10821

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.1



L-Aggregation Rule

Rload

M-Notes

FRS :

• 18555 UTRAN sharing



5.10 HSUPA statistics


Counter name

#10901 VS.eDCHcommonChannelsTxPower

#10902 VS.eDCHdataBitSentToRNC

#10903 VS.eDCHretransBlocks

#10904 VS.eDCHdataBitRec

#10905 VS.eDCHactiveUsers

#10906 VS.eDCHriseOverThermal

#10907 VS.eDCHstatus

#10908 VS.eDCHSFupsizingDuringCompressedMode

#10921 VS.eDCHUEsPerLCG

Table 113 VS.eDCHcommonChannelsTxPower - #10901

A-Description

Total transmitted power on all allocated e-AGCH and e-HICH/e-RGCH channels per 2ms peri-od.

B-Collection

LOAD

LOAD

C-Condition (Event)

Each 2ms (3 slots)

D-Result

one measurement

E-Type

VS.eDCHcommonChannelsTxPower

F-Object Instance

BTSCellHSUPA

G-Switching

NA

H-3GPP Compliance

N-#10901



I-Range

0-2^31-1

J-Unit

100 mW

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

FRS :

• 29840 HSUPA introduction

Table 114 VS.eDCHdataBitSentToRNC - #10902

A-Description

Total number of data bits sent to RNC. It corresponds to the bits of all the MAC-d PDUs sent inevery FP data frame.

B-Collection

VAL

VAL

C-Condition (Event)

FP data frame sent to RNC

D-Result

one measurement

E-Type

VS.eDCHdataBitSentToRNC

F-Object Instance

BTSCellHSUPA

G-Switching

NA

H-3GPP Compliance

N-#10902

I-Range

0-2^31-1



J-Unit

Kbit

K-Available Release

V5.0

L-Aggregation Rule

Rval

M-Notes

FRS :


Table 115 VS.eDCHretransBlocks - #10903

A-Description

Total number of necessary retransmissions for acknowledged Transport blocks (0 means theblock has been correctly received after the first transmission). The blocks discarded due to themaximum number of retransmissions reached are not taken into account.

B-Collection

VAL

VAL

C-Condition (Event)

Block received correctly (ACK received)

D-Result

one measurement

E-Type

VS.eDCHretransBlocks

F-Object Instance

BTSCellHSUPA

G-Switching

NA

H-3GPP Compliance

N-#10903

I-Range

0-2^31-1

J-Unit



EVENT

K-Available Release

V5.0

L-Aggregation Rule

Rval

M-Notes

FRS :


Table 116 VS.eDCHdataBitRec - #10904

A-Description

The number of bits (before channel decoding) received at each e-DCH TTI for all active con-nections.

B-Collection

VAL

VAL

C-Condition (Event)

Each 2 ms (3 slots)

D-Result

one measurement

E-Type

VS.eDCHdataBitRec

F-Object Instance

BTSCellHSUPA

G-Switching

NA

H-3GPP Compliance

N-#10904

I-Range

0-2^31-1

J-Unit

Kbit

K-Available Release



V5.0

L-Aggregation Rule

Rval

M-Notes

FRS :


Table 117 VS.eDCHactiveUsers - #10905

A-Description

The number of active users for a cell is collected every 2ms (it correspond to users that havebeen received a grant and currently transmitting an eDPDCH part).

B-Collection

LOAD

LOAD

C-Condition (Event)

Each 2 ms (3 slots)

D-Result

one measurement

E-Type

VS.eDCHactiveUsers

F-Object Instance

BTSCellHSUPA

G-Switching

NA

H-3GPP Compliance

N-#10905

I-Range

0-2^31-1

J-Unit

nb of user

K-Available Release

V5.0

L-Aggregation Rule



Rload

M-Notes

FRS :


Table 118 VS.eDCHriseOverThermal - #10906

A-Description

The RoT (rise over thermal) evaluated every 100ms

B-Collection

LOAD

LOAD

C-Condition (Event)

Fixed observation period of 100ms

D-Result

one measurement

E-Type

VS.eDCHriseOverThermal

F-Object Instance

BTSCellHSUPA

G-Switching

NA

H-3GPP Compliance

N-#10906

I-Range

0-2000

J-Unit

1/100 dB

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes



FRS :


Table 119 VS.eDCHstatus - #10907

A-Description

The LOAD EXCESS status of the HSUPA cell

B-Collection

LOAD

LOAD

C-Condition (Event)

Fixed observation period of 100ms

D-Result

one measurement

E-Type

VS.eDCHstatus

F-Object Instance

BTSCellHSUPA

G-Switching

NA

H-3GPP Compliance

N-#10907

I-Range

0 (NORMAL) / 1 (HEAVY)

J-Unit

no unit

K-Available Release

V5.0

L-Aggregation Rule

Rload

M-Notes

FRS :




Table 120 VS.eDCHSFupsizingDuringCompressedMode - #10908

A-Description

Each time the SF/2 case for a first transmission during a compressed frame is observed thiscounter must be incremented

B-Collection

CUM

CUM

C-Condition (Event)

Each TTI (10ms) of each UL eDCH connections

D-Result

one measurement

E-Type

VS.eDCHSFupsizingDuringCompressedMode

F-Object Instance

BTSCellHSUPA

G-Switching

NA

H-3GPP Compliance

N-#10908

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.1

L-Aggregation Rule

Rtotal

M-Notes

FRS :

• 33480 CM in Mac-e Scheduler

Table 121 VS.eDCHUEsPerLCG - #10921

A-Description



Number of HSUPA UEs configured in the LocalCellGroup

B-Collection

LOAD

LOAD

C-Condition (Event)


D-Result

one measurement

E-Type

VS.eDCHUEsPerLCG

F-Object Instance

LocalCellGroup

G-Switching

NA

H-3GPP Compliance

N-#10921

I-Range

0-2^31-1

J-Unit

EVENT

K-Available Release

V5.1

L-Aggregation Rule

Rload

M-Notes

FRS :

• 18555 UTRAN sharing



6 BTS Counters Index

• #10001 VS.PcmLos

• #10002 VS.PcmAis

• #10003 VS.PcmLfa

• #10004 VS.PcmFe

• #10005 VS.PcmCrc

• #10006 VS.PcmRai

• #10007 VS.PcmFas

• #10008 VS.PcmEbits

• #10009 VS.PcmBpvp

• #10010 VS.PcmSlip

• #10011 VS.PcmEs

• #10012 VS.PcmSes

• #10013 VS.PcmBbe

• #10014 VS.PcmUas

• #10015 VS.PCMATMnbReceivedCell

• #10016 VS.PCMATMnbSentCell

• #10017 VS.PCMthroughputCapacity

• #10102 VS.AAL2NbLostCPS

• #10103 VS.AAL2NbSTFParityErr

• #10104 VS.AAL2NbSequenceNumberErr

• #10105 VS.AAL2NbCPSHecErr

• #10106 VS.AAL2NbCPSLengthErr

• #10107 VS.AAL2NbCpsLengthMismatch

• #10109 VS.AAL2NbOSFBiggerThan47

• #10111 VS.AAL5NbAbortErr

• #10112 VS.AAL5NbLengthErr

• #10113 VS.AAL5NbCrcFrameErr

• #10114 VS.AAL5NbInvalidSize

• #10117 VS.AAL2NbReceivedCell

• #10118 VS.AAL5NbReceivedCell

• #10119 VS.AAL2NbSentCell



• #10120 VS.AAL5NbSentCell

• #10142 VS.CESSnLostCells

• #10143 VS.CESSnMisinsertCells

• #10144 VS.CESSnSeqce

• #10145 VS.CESSpErrors

• #10146 VS.CESRxGov

• #10147 VS.CESTxGun

• #10148 VS.CESReSync

• #10149 VS.CESReceivedCells

• #10150 VS.CESSentCells

• #10201 VS.RadioWBandRxMainPwr

• #10202 VS.RadioWBandRxDivPwr

• #10204 VS.PAPwr

• #10204 VS.PAPwr

• #10204 VS.PAPwr

• #10204 VS.PAPwr

• #10205 VS.RadioTxCarrierPwr

• #10206 VS.SIRperSF

• #10211 VS.CellULload

• #10213 VS.FailedAdmissionDueToULload

• #10301 VS.CEMUsedDCH

• #10303 VS.RachNack

• #10304 VS.RachNackSquare

• #10305 VS.RachAck

• #10306 VS.RachAckSquare

• #10307 VS.NodeBCidDchCollisionDetected

• #10308 VS.NodeBCidCtchCollisionDetected

• #10309 VS.CEMAlloc

• #10310 VS.LocalCellGroupLoad

• #10403 VS.cpuLoad




• #10601 VS.imaGroupUnavailSecs



• #10602 VS.imaGroupNeNumFailures

• #10603 VS.imaLinkImaViolations

• #10604 VS.imaLinkNeSevErroredSecs

• #10605 VS.imaLinkFeSevErroredSecs

• #10606 VS.imaLinkNeUnavailSecs

• #10607 VS.imaLinkFeUnavailSecs

• #10608 VS.imaLinkNeTxUnusableSecs

• #10609 VS.imaLinkNeRxUnusableSecs

• #10610 VS.imaLinkFeTxUnusableSecs

• #10611 VS.imaLinkFeRxUnusableSecs

• #10612 VS.imaLinkNeTxNumFailures

• #10613 VS.imaLinkNeRxNumFailures

• #10614 VS.imaGroupNbReceivedCell

• #10615 VS.imaGroupNbSentCell

• #10701 VS.ifInOctets

• #10702 VS.ifInUcastPkts

• #10703 VS.ifInNUcastPkts

• #10704 VS.ifInDiscards

• #10705 VS.ifInErrors

• #10706 VS.ifInUnknownProtos

• #10707 VS.ifOutOctets

• #10708 VS.ifOutUcastPkts

• #10709 VS.ifOutNUcastPkts

• #10710 VS.ifOutDiscards

• #10711 VS.ifOutErrors

• #10801 VS.HsdpaHSPDSCHTxPwr

• #10802 VS.HsdpaHSPDSCHCodesPerTTI

• #10803 VS.HsdpaHSSCCHTxPwr

• #10804 VS.HsdpaHSSCCHCodesPerTTI

• #10805 VS.Hsdpa16QAMUsage

• #10806 VS.HsdpaMACdPDUAckBits

• #10807 VS.HsdpaRxDataBitsMAChs

• #10808 VS.HsdpaTxDataBitsMAChs

• #10809 VS.HsdpaTxDataBitsSchedTotal



• #10810 VS.HsdpaNbrACKRcv

• #10811 VS.HsdpaNbrNACKRcv

• #10812 VS.HsdpaNbrDTX

• #10813 VS.HsdpaDiscMACdPDUsTimerExpiry

• #10814 VS.HsdpaDiscTransportBlocksOnMaxRetrans

• #10815 VS.HsdpaMeanNbrRetrans

• #10816 VS.HsdpaDataBufferedNodeB

• #10817 VS.HsdpaPAOverload

• #10818 VS.HsdpaTTIsUsed

• #10819 VS.HsdpaReceivedCQI

• #10820 VS.HsdpaUEsPerHBBU

• #10821 VS.HsdpaUEsPerLCG

• #10901 VS.eDCHcommonChannelsTxPower

• #10902 VS.eDCHdataBitSentToRNC

• #10903 VS.eDCHretransBlocks

• #10904 VS.eDCHdataBitRec

• #10905 VS.eDCHactiveUsers

• #10906 VS.eDCHriseOverThermal

• #10907 VS.eDCHstatus

• #10908 VS.eDCHSFupsizingDuringCompressedMode

• #10921 VS.eDCHUEsPerLCG



Wireless Service Provider SolutionsW-CDMAUMTS Access Network Counters Reference- Volume 2: BTS Counters

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

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be alteredonly by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures accessto 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 asexpressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose theinformation only to its employees with a need to know, and shall protect the information from disclosure and dissemination to thirdparties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information containedherein. If you have received this document in error, please notify the sender and destroy it immediately.

Document number: NN-20500-028Document issue: 08.03Document status: StandardSystem Release: OAM05.2Date: November 2007

NN-20500-028P2 (NodeB Counters) 08.03 Standard November 2007

Documents

Transcript of NN-20500-028P2 (NodeB Counters) 08.03 Standard November 2007