counters - volume 3 - passport counters nn-20500-028_p3_07 03_standard_july_2007

8/13/2019 Counters - Volume 3 - Passport Counters NN-20500-028_P3_07 03_Standard_July_2007

1/121

NN-20500-028

Wireless Service Provider Solutions

UMTSPerformance Management

UMTS Access Network PerformanceManagement Observation Counters - Volume3: Passport CountersNN-20500-028 07.03 Standard July 2007


2/121

Wireless Service Provider Solutions

UMTS

Performance ManagementUMTS Access Network Performance ManagementObservation Counters - Volume 3: Passport Counters

Document number: NN-20500-028Document issue: 07.03Document status: StandardProduct release: UMTS 5.1Date: July 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 as

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


3/121

PUBLICATION HISTORYSYSTEM RELEASE UMTS 5.1

July 2007

Issue 07.03/EN Standard

Update for UA 5.0 Channel Readiness.

March 2007

Issue 07.02/EN Preliminary

Update after internal review.

November 2006

Issue 07.01/EN Draft

Update for OAM 5.1.0 / UA 5.0 [UMTS 5.1]

SYSTEM RELEASE UMTS V5.0

November 2006


Update for OAM V5.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 V5.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

Alcatel-Lucent Confidential Publication history i

Copyright 2003-2007 Alcatel-Lucent UMTS Access Network Performance Management ObservationCounters - Volume 3: Passport Counters


4/121


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


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

Alcatel-Lucent Confidential Publication history ii

NN-20500-028 07.03 Standard July 2007 Copyright 2003-2007 Alcatel-Lucent


5/121


Update for Customer Readness after internal review

Resolution of the following CRs:

Q00862233

Q01033167

Q01033176

Q01034927

Q01039681

February 2005Issue 05.01/EN Draft

Update for RAN V4.1


February 2005


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

Alcatel-Lucent Confidential Publication history iii



6/121


March 2004



February 2004


Update for RAN V3.2


February 2004

Issue 03.04a/EN Standard


November 2003



May 2003



April 2003


Update for RAN V3.1

March 2003


Update for RAN V3.1

Alcatel-Lucent Confidential Publication history iv



7/121

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

5 RNC PASSPORT Platform counter families...............................................................................................................16

5.1 ATM port..................................................................................................................................................................17

5.2 Logical Processor Use.............................................................................................................................................62

5.3 Adjunct Processor Stats.......................................................................................................................................... 77

5.4 ACCOUNT ATM Vcc............................................................................................................................................... 91

5.5 ACCOUNT ATM Vpc............................................................................................................................................... 99

6 Passport Counters Index...........................................................................................................................................107

Alcatel-Lucent Confidential Table of contents v



8/121

Figure 1 - Passport containment tree.................................................................................................... ............. ........... 8

Alcatel-Lucent Confidential List of figures vi



9/121

Table 1 - Table of aggregation rules..................................................................................................... ............. ......... 12

Table 2 - VS.ProvRate - #20001........................................................................................................... ............. ......... 18

Table 3 - VS.ActualRate - #20002...................................................................................................................... ......... 19

Table 4 - VS.TxUtilization - #20003.................................................................................................................... ......... 20

Table 5 - VS.RxUtilization - #20004...................................................................................................... ............. ......... 21

Table 6 - VS.TxMaxCellRate - #20005............................................................................................................... ......... 22

Table 7 - VS.TxMinCellRate - #20006................................................................................................................ ......... 23

Table 8 - VS.TxAvgCellRate - #20007.................................................................................................. ............. ......... 24

Table 9 - VS.RxMaxCellRate - #20008................................................................................................. ............. ......... 24

Table 10 - VS.RxMinCellRate - #20009................................................................................................ ............. ......... 25

Table 11 - VS.RxAvgCellRate - #20010............................................................................................................. ......... 26Table 12 - VS.TxMaxCellRateClp - #20011.......................................................................................... ............. ......... 27

Table 13 - VS.TxMinCellRateClp - #20012........................................................................................... ............. ......... 28

Table 14 - VS.TxAvgCellRateClp - #20013........................................................................................................ ......... 29

Table 15 - VS.RxMaxCellRateClp - #20014....................................................................................................... ......... 29

Table 16 - VS.RxMinCellRateClp - #20015........................................................................................................ ......... 30

Table 17 - VS.RxAvgCellRateClp - #20016.......................................................................................... ............. ......... 31

Table 18 - VS.TxCellDiscards - #20017................................................................................................ ............. ......... 32

Table 19 - VS.RxCellDiscards - #20018............................................................................................................. ......... 33

Table 20 - VS.TxFrameDiscards - #20019......................................................................................................... ......... 34

Table 21 - VS.RxFrameDiscards - #20020........................................................................................... ............. ......... 34

Table 22 - VS.TxCellDiscardsClp - #20021........................................................................................................ ......... 35

Table 23 - VS.RxCellDiscardsClp - #20022.......................................................................................... ............. ......... 36

Table 24 - VS.TxFrameDiscardsClp - #20023...................................................................................... ............. ......... 37

Table 25 - VS.RxFrameDiscardsClp - #20024...................................................................................... ............. ......... 38

Table 26 - VS.TxMaxCellRate - #20025............................................................................................................. ......... 39

Table 27 - VS.TxMinCellRate - #20026.............................................................................................................. ......... 40

Table 28 - VS.TxAvgCellRate - #20027................................................................................................ ............. ......... 41

Table 29 - VS.RxMaxCellRate - #20028............................................................................................... ............. ......... 42

Table 30 - VS.RxMinCellRate - #20029................................................................................................ ............. ......... 43

Table 31 - VS.RxAvgCellRate - #20030............................................................................................................. ......... 44

Table 32 - VS.TxMaxCellRateClp - #20031.......................................................................................... ............. ......... 45Table 33 - VS.TxMinCellRateClp - #20032........................................................................................... ............. ......... 47

Table 34 - VS.TxAvgCellRateClp - #20033........................................................................................................ ......... 48

Table 35 - VS.RxMaxCellRateClp - #20034....................................................................................................... ......... 49

Table 36 - VS.RxMinCellRateClp - #20035........................................................................................................ ......... 50

Table 37 - VS.RxAvgCellRateClp - #20036.......................................................................................... ............. ......... 51

Table 38 - VS.TxCellDiscards - #20037................................................................................................ ............. ......... 52

Table 39 - VS.RxCellDiscards - #20038............................................................................................................. ......... 53

Table 40 - VS.TxFrameDiscards - #20039......................................................................................................... ......... 54

Table 41 - VS.RxFrameDiscards - #20040........................................................................................... ............. ......... 56

Alcatel-Lucent Confidential List of tables vii



10/121

Table 42 - VS.TxCellDiscardsClp - #20041........................................................................................................ ......... 57

Table 43 - VS.RxCellDiscardsClp - #20042.......................................................................................... ............. ......... 58

Table 44 - VS.TxFrameDiscardsClp - #20043...................................................................................... ............. ......... 59

Table 45 - VS.RxFrameDiscardsClp - #20044...................................................................................... ............. ......... 60

Table 46 - VS.CpuUtilAvg - #20103...................................................................................................... ............. ......... 62

Table 47 - VS.CpuUtilAvgMin - #20104................................................................................................ ............. ......... 63

Table 48 - VS.CpuUtilAvgMax - #20105............................................................................................... ............. ......... 64

Table 49 - VS.MemoryCapacity - #20106............................................................................................. ............. ......... 65

Table 50 - VS.MemoryUsageAvg - #20107........................................................................................................ ......... 66

Table 51 - VS.MemoryUsageAvgMin - #20108.................................................................................................. ......... 67

Table 52 - VS.MemoryUsageAvgMax - #20109................................................................................................. ......... 68

Table 53 - VS.SharedMsgBlockCapacity - #20110............................................................................... ............. ......... 69

Table 54 - VS.SharedMsgBlockUsageAvg - #20111............................................................................ ............. ......... 70

Table 55 - VS.SharedMsgBlockUsageAvgMin - #20112.................................................................................... ......... 70

Table 56 - VS.SharedMsgBlockUsageAvgMax - #20113................................................................................... ......... 71

Table 57 - VS.LocalMsgBlockCapacity - #20114.................................................................................. ............. ......... 72

Table 58 - VS.LocalMsgBlockUsageAvg - #20115............................................................................... ............. ......... 73

Table 59 - VS.LocalMsgBlockUsageMin - #20116............................................................................................. ......... 74

Table 60 - VS.LocalMsgBlockUsageMax - #20117............................................................................................ ......... 75

Table 61 - VS.ApCpuUtilizationHistogram - #20201............................................................................. ............. ......... 77

Table 62 - VS.ApCpuUtilizationAvg - #20202....................................................................................... ............. ......... 79

Table 63 - VS.ApMemoryCapacity - #20203...................................................................................................... ......... 79

Table 64 - VS.ApMemoryUtilization - #20204....................................................................................... ............. ......... 80

Table 65 - VS.ApMemoryUsageAvgMin - #20205................................................................................ ............. ......... 81

Table 66 - VS.ApMemoryUsageAvgMax - #20206............................................................................... ............. ......... 82

Table 67 - VS.ApSharedMsgBlockCapacity - #20207........................................................................................ ......... 83

Table 68 - VS.ApSharedMsgBlockUsageAvg - #20208........................................................................ ............. ......... 84

Table 69 - VS.ApSharedMsgBlockUsageAvgMin - #20209.................................................................. ............. ......... 84

Table 70 - VS.ApSharedMsgBlockUsageAvgMax - #20210................................................................. ............. ......... 85

Table 71 - VS.ApLocalMsgBlockCapacity - #20211........................................................................................... ......... 86

Table 72 - VS.ApLocalMsgBlockUsageAvg - #20212........................................................................... ............. ......... 87

Table 73 - VS.ApLocalMsgBlockUsageAvgMin - #20213..................................................................... ............. ......... 88

Table 74 - VS.ApLocalMsgBlockUsageAvgMax - #20214.................................................................... ............. ......... 89

Table 75 - VS.AcVccIngressCellCountClp0 - #30001........................................................................... ............. ......... 91

Table 76 - VS.AcVccIngressCellCountClp01 - #30002......................................................................... ............. ......... 92

Table 77 - VS.AcVccEgressCellCountClp0 - #30003......................................................................................... ......... 93

Table 78 - VS.AcVccEgressCellCountClp01 - #30004....................................................................................... ......... 93

Table 79 - VS.AcVccIngressDiscardedClp0 - #30005........................................................................................ ......... 94

Table 80 - VS.AcVccIngressDiscardedClp01 - #30006...................................................................................... ......... 95

Table 81 - VS.AcVccEgressDiscardedClp0 - #30007........................................................................... ............. ......... 96

Table 82 - VS.AcVccEgressDiscardedClp01 - #30008......................................................................... ............. ......... 97

Table 83 - VS.AcVpcIngressCellCountClp0 - #30101........................................................................................ ......... 99

Alcatel-Lucent Confidential List of tables viii



11/121

Table 84 - VS.AcVpcIngressCellCountClp01 - #30102...................................................................................... ....... 100

Table 85 - VS.AcVpcEgressCellCountClp0 - #30103........................................................................... ............. ....... 101

Table 86 - VS.AcVpcEgressCellCountClp01 - #30104......................................................................... ............. ....... 101

Table 87 - VS.AcVpcIngressDiscardedClp0 - #30105.......................................................................... ............. ....... 102

Table 88 - VS.AcVpcIngressDiscardedClp01 - #30106........................................................................ ............. ....... 103

Table 89 - VS.AcVpcEgressDiscardedClp0 - #30107........................................................................... ............. ....... 104

Table 90 - VS.AcVpcEgressDiscardedClp01 - #30108......................................................................... ............. ....... 105

Alcatel-Lucent Confidential List of tables ix



12/121

1 About this publication

This publication provides a list of UMTS Access Network observation counters collected by the

APM/ADI applications of the Performance server.

This section consists of the following topics:

"Applicability"

"Audience"

"Prerequisites"

"Related publications"

"How this publication is organized"

"Vocabulary conventions"

Applicability

This publication applies to RAN 5.0 of the UMTS 5.1 System Release.

Audience

This publication is intended for network controllers responsible for the Performance Management of

the UMTS Access Network.

Prerequisites

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

UMTS Access Network Performance Management (NN-20500-034)

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

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

"How Access Network observation counters are defined"provides information about the

Alcatel-Lucent Confidential 1



13/121

counter definition template, counter types on the OAM GUI, and counter hierarchy. "How Access Network observation counters are described"describes the Access

Network observation counters.

"Passport Platform counter families" lists Passport platform counter families and presentstheir counters. Each counter is described separately in a table, and these tables are arranged inalphanumerical order.

Indexpresents 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 NEIghboringSI 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)




14/121

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.




15/121

2 Road map to UTRAN documentation

For collection roadmaps information, see UMTS Access Document Collection - Overview and update

summary (NN-20500-050).




16/121

3 What's new

For information about What's new section, see :UTRAN 5.0 / W-NMS 5.1 Release Operational

ImpactsNN-20500-052, Vol3, Annex C




17/121

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"




18/121

4.1 How Access Network observation counters are defined

A standard observation counter is a device used in Performance Management to calculate the

number of occurrences of an event. For further definitions for observation counters, refer to 3GPP TS

32.104 specifications.

This section describes the following topics:

"Counter families"

"Object hierarchy"

"Wording assumption"

"Counter definition template"

"Counter types on the OAM GUI"

"Counter hierarchy"

"Aggregation rules"

Counter families

The counters specified in this publication are grouped into families of counters. A family of counters

is attached to a given UMTS feature. For example the "Radio Link Management Family" groups

together counters involved with Radio Link Management (i.e.: Setup, Addition, Deletion,

Reconfiguration..).

Object hierarchy

Counters are reported on objects (that is location) according to their hierarchy.

The following figure show the hierarchy of objects.




19/121

Figure 1 Passport containment tree

Note: Objects that report counters are in bold underlined.

For more information about UTRAN objects and their relationships, refer to theUMTS Access

Network Overview(NN-20500-031) publication.

Wording assumption

Both wordingscounterand measurementare equally used in this document to identify the same

concept. Usually, Alcatel-Lucent uses the term counterto distinguish a counter from a (radio)

measurement

3GPP Performance Management specifications preferably use measurement. When the context

refers to 3GPP specifications,measurementis used, whilecounter is used in Alcatel-Lucent

specific part, but both wordings are equivalent.

Counter definition template

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

specifications.

Measurement name (section header)

This is a descriptive name of the measurement type.

A-Description




20/121

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 the

measurement 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). If

more than one value is provided, the measurement is screened according to criteria, for example, a

number of call releases may be screened according to the cause of the call releases.

The number of call releases related to a given cause can be considered a subcounter. In that case,

the measurement result specification item includes a 'screening paragraph' that specifies the various

subcounters and their meanings.

E-Type

This section contains a short form of the measurement name specified in the header, which is used

to identify the measurement type in the result files.

F-Object InstanceThis section contains the object class and its instance. The "measObjInstId" field identifies the

measured object class and its instance; for example, trunk1 means that object class trunk instance

#1 is being measured. The object class and instance values used for this purpose will be in

accordance with 3GPP TS 32.106. This means the NE or resource object model (defined in the Basic

CM IRP Information Model - 3GPP TS 32.106-5) and naming conventions (defined in the Naming

Convention for Managed Objects - 3GPP TS 32.106-8). This parameter, if applicable, will be

provided in the measurement job.




21/121

G-Switching

This section contains the Switching domain(s). Its measurement is applicable to Circuit Switched

and, or Packet Switched domains.

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

aggregation rule type. The counter type defines the aggregation rule value.

Counter types on the OAM GUI

The three types of user-accessible observation counters available on the OAM GUI are as follows:

CUMULATIVE (or TOTAL)

VALUE

LOAD

CUMULATIVE counters

CUMULATIVE counters provide raw counts. A CUMULATIVE counter is a CUM (CC) type counter,

as identified in 3GPP TS 32.104 specifications. It is incremented by 1 each time the counted event

occurs, and it provides the cumulated value. One NE cumulative counter provides one counter at the

OAM GUI level.




22/121

VALUE counters

VALUE counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order to

implement a DER (VAL) type measurement. This mechanism provides average values from raw

counts obtained by internal events (the time interval between two events is random and is not

accessible to users). The counter is incremented by a value attached to the event itself.

Alcatel-Lucent provides the following:

the cumulated value (.Cumin XML files)

the number of events (.NbEvtin XML files)

Note: This value is sampled once per hour and is indicated in the XML observation file.

the averaged value (.Avgin XML files) the maximum added value (.Maxin XML files)

the minimum added value (.Minin XML files)

Note: The averaged value is equal to cumulated value over number of events

LOAD counters

LOAD counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order to

implement an SI type measurement. This mechanism provides average values from raw counts

obtained by internal sampling (the time interval between two events is constant and is not accessible

to users). The counter is incremented by a sampled value on the sampling event occurrence.

Alcatel-Lucent provides the following:

the cumulated value (.Cumin XML files)

the number of samplings (.NbEvtin XML files)

the averaged value (.Avgin XML files)

the maximum sampled value (.Maxin XML files)

the minimum sampled value (.Minin 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 occurs

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




23/121

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

follow the following rules.

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

period.

The following table presents a rule for each counter.

Table 1 Table of aggregation rules

Rule Results Apply to

Rtotal X.cum = X1.cum + X2.cum + ... + Xn.cum CUM (CC) counters

Rload/Rval X.cum = X1.cum + ... + Xn.cum

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




24/121

Rule Results Apply to

Rmax X = max (Xi)

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

Passport counters




25/121

4.2 How Access Network observation counters are described

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

Management.

Observation counters are stored in XML record files.

Each record file contains the counters produced by a single NE collection.

Access Network observation counters handled by the ADI application for the UMTS 5.1 system

release are as follows:

C-Node application counters

I-Node platform counters

Node B counters

These counters have been divided into the three following sets of families:

"RNC counter families"

"BTS counter families"

"Passport counter families"

Each counter family is attached to a given UMTS feature (for example, Handover counters, where

hard handover performances are reported) or to a Performance Management purpose for example,

User Plane Traffic counters, where counters related to traffic observation are grouped together).

Access observation file structure

Some observation counters are processed in order to provide temporal and spatial aggregations. The

following observation counter records are available:

single period

hourly aggregated

daily aggregated

Each observation file produces single, hourly and daily observation counter records. At the dedicated

NE level, a predetermined subset of these data are aggregated.

The file name convention for an observation is as follows:

.-_.xml .

Where:

typeis set toA which indicates one of the following aggregated observations:

the observation file contains data originated from a single NE for a unique time period.




26/121

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 .

starttime is the beginning time of the granularity period; its format must be .

endtime is the end time of the granularity period; its format must be .

NEis the Network Element type ID that means a unique numerical identifier as 3GPP using

- _[CN|AN|IN] pattern (for example, RNC-RNC535_CN). Or the BTS

name using the NE userLabel as a NE ID (for example BTSEq-A10km215).

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

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

RNC observation XML file

The XML format is compliant with 3 GPP dtd file: 32.401-02.dtd. The granularity period defines, in

minutes, the periodicity of the generation of the counter; the values supported are 15, 30 and 60.

The directory of the RNC I-Node observation XML file on PerfServer is as follows:

/opt/nortel/data/access/observation//_IN

For more information about RNC XML record files, refer to the UMTS Access Network Performance

Management(NN-20500-033) publication.




27/121

5 RNC PASSPORT Platform counter families

ATM port

Logical Processor Use

Adjunct Processor Stats

ACCOUNT ATM Vcc

ACCOUNT ATM Vpc




28/121

5.1 ATM port

These counters apply to both I-node and A-node Lp (Logical Processor) and AtmPort locations. All of

them are vendor-specific, and none of them are used to compute 3GPP counters. In UMTS 04.1,

with UTRAN version UA04.1, Passport release is PCR6.1. Therefore the ultimate reference for

description of counters provided by NTPs Passport are to be found in the adequate NTP, see

references [R4], [R6], [R7], and [R8]. The counters of the family ATM port come from Passport,

component ATMInterface (ATMIf). GROUP ATMIf Statistics (Stats). The Passport Attribute e.g.

ATTRIBUTE AtmIf txCellDiscardClp maps directly to the name of the counter VS.TxCellDiscardsClp.

RNC provides only a subset of the ATM statistics available on Passport. Note that some counters are

not available on some configurations (see Chapter 3 Monitoring ATM interfaces in Passport

Monitoring and Troubleshooting Guide). On 16-port OC3/STM1 FP statistics per port (AtmIf)

txCellDiscardCLP0+1, tx CellDiscardCLP1, rxCellDiscardCLP0+1, rxCellDiscardCLP1 are NOT

available. , and On 4-port OC12/STM4 channelized FP statistics per port on an unchannelized basis

(ATmIf) txCellCLP1, txCellDiscardCLP1, rxCellCLP1, rxCellDiscardCLP1 are NOT available. Ref:

NTP 241-5701-060 Volume 2 (Passport Components)

Alcatel-Lucentcounter number

Counter name

#20001 VS.ProvRate

#20002 VS.ActualRate

#20003 VS.TxUtilization

#20004 VS.RxUtilization

#20005 VS.TxMaxCellRate

#20006 VS.TxMinCellRate

#20007 VS.TxAvgCellRate

#20008 VS.RxMaxCellRate

#20009 VS.RxMinCellRate

#20010 VS.RxAvgCellRate

#20011 VS.TxMaxCellRateClp#20012 VS.TxMinCellRateClp

#20013 VS.TxAvgCellRateClp

#20014 VS.RxMaxCellRateClp

#20015 VS.RxMinCellRateClp

#20016 VS.RxAvgCellRateClp

#20017 VS.TxCellDiscards

#20018 VS.RxCellDiscards




29/121

Alcatel-Lucentcounter number Counter name

#20019 VS.TxFrameDiscards

#20020 VS.RxFrameDiscards

#20021 VS.TxCellDiscardsClp

#20022 VS.RxCellDiscardsClp

#20023 VS.TxFrameDiscardsClp

#20024 VS.RxFrameDiscardsClp

#20025 VS.TxMaxCellRate

#20026 VS.TxMinCellRate

#20027 VS.TxAvgCellRate#20028 VS.RxMaxCellRate

#20029 VS.RxMinCellRate

#20030 VS.RxAvgCellRate

#20031 VS.TxMaxCellRateClp

#20032 VS.TxMinCellRateClp

#20033 VS.TxAvgCellRateClp

#20034 VS.RxMaxCellRateClp

#20035 VS.RxMinCellRateClp

#20036 VS.RxAvgCellRateClp

#20037 VS.TxCellDiscards

#20038 VS.RxCellDiscards

#20039 VS.TxFrameDiscards

#20040 VS.RxFrameDiscards

#20041 VS.TxCellDiscardsClp

#20042 VS.RxCellDiscardsClp

#20043 VS.TxFrameDiscardsClp

#20044 VS.RxFrameDiscardsClp

Table 2 VS.ProvRate - #20001

A-Description

AtmIf s provisioned link rate in cells per second

B-Collection

CUM

CUMulative

C-Condition (Event)

-




30/121

D-Result

one measurement

E-Type

VS.ProvRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20001

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 3 VS.ActualRate - #20002

A-Description

AtmIf 's actual bandwidth in cells per second. Equals provRate when no errors occur.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ActualRate

F-Object Instance

AtmPort




31/121

G-Switching

NA

H-3GPP Compliance

N-N-#20002

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 4 VS.TxUtilization - #20003

A-Description

This attribute indicates the average transmit traffic rate over the most recent collection intervalexpressed as a percentage of the ATM link bandwidth. On AtmIfs linked to MPLS POS inter-faces, the ATM link is the LSP. Many LSPs could share the same POS link. If the POS link is

underutilized it is possible for an LSP to carry more traffic than it has been assigned. This oc-curs as bandwidth on an LSP is allocated based on determining whether the requested band-width exceeds the available bandwidth on an LSP, not on whether the actual bandwidth ex-ceeds the available bandwidth. When the actual bandwidth is higher than the requested band-with it is possible that this extra traffic will be carried over the LSP. Since this is possible, thevalue of this attribute may exceed 100%. If the utilization exceeds 65535% then 65535 is dis-played. If the Lsp has a bandwidth of 0, then 0 is displayed for the utilization.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxUtilization

F-Object Instance

AtmPort




32/121

G-Switching

NA

H-3GPP Compliance

N-N-#20003

I-Range

0..100

J-Unit

percent

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 5 VS.RxUtilization - #20004

A-Description

This attribute indicates the average receive traffic rate over the most recent collection intervalexpressed as a percentage of the ATM link bandwidth. On AtmIfs linked to MPLS POS inter-faces, the ATM link is the LSP. Many LSPs could share the same POS link. If the POS link is

underutilized it is possible for an LSP to carry more traffic than it has been assigned. This oc-curs as bandwidth on an LSP is allocated based on determining whether the requested band-width exceeds the available bandwidth on an LSP, not on whether the actual bandwidth ex-ceeds the available bandwidth. When the actual bandwidth is higher than the requested band-with it is possible that this extra traffic will be carried over the LSP. Since this is possible, thevalue of this attribute may exceed 100%. If the utilization exceeds 65535% then 65535 is dis-played. If the Lsp has a bandwidth of 0, then 0 is displayed for the utilization.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxUtilization

F-Object Instance

AtmPort




33/121

G-Switching

NA

H-3GPP Compliance

N-N-#20004

I-Range

0..100

J-Unit

percent

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 6 VS.TxMaxCellRate - #20005

A-Description

This attribute indicates the transmitted cell rate (CLP=0+1) during the busiest minute of the col-lection interval.

B-CollectionCUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxMaxCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20005

I-Range




34/121

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 7 VS.TxMinCellRate - #20006

A-Description

This attribute indicates the transmitted cell rate (CLP=0+1) during the least busy minute of thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxMinCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20006

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0




35/121

L-Aggregation Rule

Rmin

Table 8 VS.TxAvgCellRate - #20007

A-Description

This attribute indicates the average transmitted cell rate (CLP=0+1) during the collection inter-val.

B-Collection

CUM

CUMulativeC-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxAvgCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20007

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 9 VS.RxMaxCellRate - #20008

A-Description




36/121

This attribute indicates the received cell rate (CLP=0+1) during the busiest minute of the collec-

tion interval.B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-TypeVS.RxMaxCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20008

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 10 VS.RxMinCellRate - #20009

A-Description

This attribute indicates the received cell rate (CLP=0+1) during the least busy minute of thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)




37/121

-

D-Result

one measurement

E-Type

VS.RxMinCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20009

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 11 VS.RxAvgCellRate - #20010

A-Description

This attribute indicates the average received cell rate (CLP=0+1) during the collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxAvgCellRate

F-Object Instance




38/121

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20010

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 12 VS.TxMaxCellRateClp - #20011

A-Description

This attribute indicates the transmitted cell rate (CLP=1) during the busiest minute of the col-

lection interval.B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxMaxCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20011




39/121

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 13 VS.TxMinCellRateClp - #20012

A-Description

This attribute indicates the transmitted cell rate (CLP=1) during the least busy minute of thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-D-Result

one measurement

E-Type

VS.TxMinCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20012

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release




40/121

V2v0

L-Aggregation Rule

Rmin

Table 14 VS.TxAvgCellRateClp - #20013

A-Description

This attribute indicates the average transmitted cell rate (CLP=1) during the collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxAvgCellRateClp

F-Object Instance

AtmPortG-Switching

NA

H-3GPP Compliance

N-N-#20013

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 15 VS.RxMaxCellRateClp - #20014

A-Description




41/121

This attribute indicates the received cell rate (CLP=1) during the busiest minute of the collec-

tion interval.B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-TypeVS.RxMaxCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20014

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 16 VS.RxMinCellRateClp - #20015

A-Description

This attribute indicates the received cell rate (CLP=1) during the least busy minute of the col-lection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)




42/121

-

D-Result

one measurement

E-Type

VS.RxMinCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20015

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 17 VS.RxAvgCellRateClp - #20016

A-Description

This attribute indicates the average received cell rate (CLP=1) during the collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxAvgCellRateClp

F-Object Instance




43/121

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20016

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 18 VS.TxCellDiscards - #20017

A-Description

This attribute counts the cells (CLP=0+1) which are discarded before being transmitted during

the collection interval.B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxCellDiscards

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20017




44/121

I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 19 VS.RxCellDiscards - #20018

A-Description

This attribute counts the cells (CLP=0+1) which are discarded after being received during thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-D-Result

one measurement

E-Type

VS.RxCellDiscards

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20018

I-Range

0..2^64-1

J-Unit

cell

K-Available Release




45/121

V2v0

L-Aggregation Rule

Radd

Table 20 VS.TxFrameDiscards - #20019

A-Description

This attribute counts the frames (CLP=0+1) which are discarded before being transmitted dur-ing the collection interval.

B-Collection

CUMCUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxFrameDiscards

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20019

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 21 VS.RxFrameDiscards - #20020




46/121

A-Description

This attribute counts the frames (CLP=0+1) which are discarded after being received duringthe collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxFrameDiscards

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20020

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 22 VS.TxCellDiscardsClp - #20021

A-Description

This attribute counts the cells (CLP=1) which are discarded before being transmitted during thecollection interval.

B-Collection

CUM

CUMulative




47/121

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxCellDiscardsClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20021

I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 23 VS.RxCellDiscardsClp - #20022

A-Description

This attribute counts the cells (CLP=1) which are discarded after being received during the col-lection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type




48/121

VS.RxCellDiscardsClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20022

I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 24 VS.TxFrameDiscardsClp - #20023

A-DescriptionThis attribute counts the frames (CLP=1) which are discarded before being transmitted duringthe collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxFrameDiscardsClp

F-Object Instance

AtmPort

G-Switching

NA




49/121

H-3GPP Compliance

N-N-#20023

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 25 VS.RxFrameDiscardsClp - #20024

A-Description

This attribute counts the frames (CLP=1) which are discarded after being received during thecollection interval.

B-Collection

CUM

CUMulativeC-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxFrameDiscardsClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20024

I-Range

0..2^64-1

J-Unit




50/121

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 26 VS.TxMaxCellRate - #20025

A-Description

This attribute indicates the transmitted cell rate (CLP=0+1) during the busiest minute of the col-

lection interval by ATM service category.B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

A set of subcounters screened on: ATM Service Category

Sub-Counter #0 : Cbr

Sub-Counter #1 : Rtvbr

Sub-Counter #2 : Nrtvbr

Sub-Counter #3 : Abr

Sub-Counter #4 : Ubr

E-Type

VS.TxMaxCellRate.VS.TxMaxCellRate.Cbr

VS.TxMaxCellRate.VS.TxMaxCellRate.Rtvbr

VS.TxMaxCellRate.VS.TxMaxCellRate.Nrtvbr

VS.TxMaxCellRate.VS.TxMaxCellRate.Abr

VS.TxMaxCellRate.VS.TxMaxCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance




51/121

N-N-#20025

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 27 VS.TxMinCellRate - #20026

A-Description

This attribute indicates the transmitted cell rate (CLP=0+1) during the least busy minute of thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

VS.TxMinCellRate.VS.TxMinCellRate.Cbr

VS.TxMinCellRate.VS.TxMinCellRate.Rtvbr

VS.TxMinCellRate.VS.TxMinCellRate.Nrtvbr

VS.TxMinCellRate.VS.TxMinCellRate.Abr

VS.TxMinCellRate.VS.TxMinCellRate.Ubr

F-Object Instance




52/121

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20026

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 28 VS.TxAvgCellRate - #20027

A-Description

This attribute indicates the average transmitted cell rate (CLP=0+1) during the collection inter-

val by ATM service category.B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

VS.TxAvgCellRate.VS.TxAvgCellRate.Cbr

VS.TxAvgCellRate.VS.TxAvgCellRate.Rtvbr




53/121

VS.TxAvgCellRate.VS.TxAvgCellRate.Nrtvbr VS.TxAvgCellRate.VS.TxAvgCellRate.Abr

VS.TxAvgCellRate.VS.TxAvgCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20027

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 29 VS.RxMaxCellRate - #20028

A-Description

This attribute indicates the received cell rate (CLP=0+1) during the busiest minute of the collec-tion interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result









54/121

Sub-Counter #4 : UbrE-Type

VS.RxMaxCellRate.VS.RxMaxCellRate.Cbr

VS.RxMaxCellRate.VS.RxMaxCellRate.Rtvbr

VS.RxMaxCellRate.VS.RxMaxCellRate.Nrtvbr

VS.RxMaxCellRate.VS.RxMaxCellRate.Abr

VS.RxMaxCellRate.VS.RxMaxCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20028

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 30 VS.RxMinCellRate - #20029

A-Description

This attribute indicates the received cell rate (CLP=0+1) during the least busy minute of thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result





55/121

Sub-Counter #0 : Cbr Sub-Counter #1 : Rtvbr




E-Type

VS.RxMinCellRate.VS.RxMinCellRate.Cbr

VS.RxMinCellRate.VS.RxMinCellRate.Rtvbr

VS.RxMinCellRate.VS.RxMinCellRate.Nrtvbr

VS.RxMinCellRate.VS.RxMinCellRate.Abr

VS.RxMinCellRate.VS.RxMinCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20029

I-Range0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 31 VS.RxAvgCellRate - #20030

A-Description

This attribute indicates the average received cell rate (CLP=0+1) during the collection intervalby ATM service category.

B-Collection

CUM

CUMulative




56/121

C-Condition (Event)

-

D-Result







E-Type

VS.RxAvgCellRate.VS.RxAvgCellRate.Cbr

VS.RxAvgCellRate.VS.RxAvgCellRate.Rtvbr

VS.RxAvgCellRate.VS.RxAvgCellRate.Nrtvbr

VS.RxAvgCellRate.VS.RxAvgCellRate.Abr

VS.RxAvgCellRate.VS.RxAvgCellRate.Ubr

F-Object Instance

AtmPort

G-SwitchingNA

H-3GPP Compliance

N-N-#20030

I-Range

0..2^32-1

J-Unit

cell/s

K-Available ReleaseV2v0

L-Aggregation Rule

Ravg

Table 32 VS.TxMaxCellRateClp - #20031

A-Description

This attribute indicates the transmitted cell rate (CLP=1) during the busiest minute of the col-




57/121

lection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

VS.TxMaxCellRateClp.VS.TxMaxCellRateClp.Cbr

VS.TxMaxCellRateClp.VS.TxMaxCellRateClp.Rtvbr

VS.TxMaxCellRateClp.VS.TxMaxCellRateClp.Nrtvbr

VS.TxMaxCellRateClp.VS.TxMaxCellRateClp.Abr

VS.TxMaxCellRateClp.VS.TxMaxCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20031

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax




58/121

Table 33 VS.TxMinCellRateClp - #20032

A-Description

This attribute indicates the transmitted cell rate (CLP=1) during the least busy minute of thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-D-Result







E-Type

VS.TxMinCellRateClp.VS.TxMinCellRateClp.Cbr

VS.TxMinCellRateClp.VS.TxMinCellRateClp.Rtvbr

VS.TxMinCellRateClp.VS.TxMinCellRateClp.Nrtvbr

VS.TxMinCellRateClp.VS.TxMinCellRateClp.Abr

VS.TxMinCellRateClp.VS.TxMinCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NAH-3GPP Compliance

N-N-#20032

I-Range

0..2^32-1

J-Unit

cell/s




59/121

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 34 VS.TxAvgCellRateClp - #20033

A-Description

This attribute indicates the average transmitted cell rate (CLP=1) during the collection intervalby ATM service category.

B-CollectionCUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

VS.TxAvgCellRateClp.VS.TxAvgCellRateClp.Cbr

VS.TxAvgCellRateClp.VS.TxAvgCellRateClp.Rtvbr

VS.TxAvgCellRateClp.VS.TxAvgCellRateClp.Nrtvbr

VS.TxAvgCellRateClp.VS.TxAvgCellRateClp.Abr

VS.TxAvgCellRateClp.VS.TxAvgCellRateClp.UbrF-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20033




60/121

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 35 VS.RxMaxCellRateClp - #20034

A-Description

This attribute indicates the received cell rate (CLP=1) during the busiest minute of the collec-tion interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-D-Result







E-Type

VS.RxMaxCellRateClp.VS.RxMaxCellRateClp.Cbr

VS.RxMaxCellRateClp.VS.RxMaxCellRateClp.Rtvbr

VS.RxMaxCellRateClp.VS.RxMaxCellRateClp.Nrtvbr

VS.RxMaxCellRateClp.VS.RxMaxCellRateClp.Abr

VS.RxMaxCellRateClp.VS.RxMaxCellRateClp.Ubr

F-Object Instance

AtmPort




61/121

G-Switching

NA

H-3GPP Compliance

N-N-#20034

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 36 VS.RxMinCellRateClp - #20035

A-Description

This attribute indicates the received cell rate (CLP=1) during the least busy minute of the col-lection interval by ATM service category.

B-CollectionCUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

VS.RxMinCellRateClp.VS.RxMinCellRateClp.Cbr

VS.RxMinCellRateClp.VS.RxMinCellRateClp.Rtvbr

VS.RxMinCellRateClp.VS.RxMinCellRateClp.Nrtvbr




62/121

VS.RxMinCellRateClp.VS.RxMinCellRateClp.Abr VS.RxMinCellRateClp.VS.RxMinCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20035

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 37 VS.RxAvgCellRateClp - #20036

A-Description

This attribute indicates the average received cell rate (CLP=1) during the collection interval byATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result










63/121

E-Type

VS.RxAvgCellRateClp.VS.RxAvgCellRateClp.Cbr

VS.RxAvgCellRateClp.VS.RxAvgCellRateClp.Rtvbr

VS.RxAvgCellRateClp.VS.RxAvgCellRateClp.Nrtvbr

VS.RxAvgCellRateClp.VS.RxAvgCellRateClp.Abr

VS.RxAvgCellRateClp.VS.RxAvgCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20036

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 38 VS.TxCellDiscards - #20037

A-Description

This attribute counts the cells (CLP=0+1) which are discarded before being transmitted duringthe collection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result






64/121

Sub-Counter #1 : Rtvbr Sub-Counter #2 : Nrtvbr



E-Type

VS.TxCellDiscards.VS.TxCellDiscards.Cbr

VS.TxCellDiscards.VS.TxCellDiscards.Rtvbr

VS.TxCellDiscards.VS.TxCellDiscards.Nrtvbr

VS.TxCellDiscards.VS.TxCellDiscards.Abr

VS.TxCellDiscards.VS.TxCellDiscards.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-N-#20037

I-Range

0..2^32-1J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 39 VS.RxCellDiscards - #20038

A-Description

This attribute counts the cells (CLP=0+1) which are discarded after being received during thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)




65/121

-

D-Result







E-Type

VS.RxCellDiscards.VS.RxCellDiscards.Cbr

VS.RxCellDiscards.VS.RxCellDiscards.Rtvbr

VS.RxCellDiscards.VS.RxCellDiscards.Nrtvbr

VS.RxCellDiscards.VS.RxCellDiscards.Abr

VS.RxCellDiscards.VS.RxCellDiscards.Ubr

F-Object Instance

AtmPort

G-Switching

NAH-3GPP Compliance

N-N-#20038

I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0L-Aggregation Rule

R

counters - volume 3 - passport counters nn-20500-028_p3_07 03_standard_july_2007

Documents