RTWP Rssi

NN-20500-028
Wireless Service Provider Solutions
W-CDMA
Alcatel-Lucent 9300 W-CDMA Product Family
Counters Reference Guide for MSS

NN-20500-028 10.03 Preliminary July 2009
W-CDMA

Document number:
Document issue:
Document status:
Product release:
Date:
NN-20500-028
10.03
Preliminary
OAM07.0
July 2009
Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
Copyright 2003-2009 Alcatel-Lucent, All Rights Reserved

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

April 2009
Issue 09.07/EN Standard
Update for DR5.
September 2008
Update after internal review.
July 2008
June 2008
Update for Pre-DR4
May 2008
Copyright 2003-2009 Alcatel-Lucent
Publication history
February 2008
Update for V6.0 April-08 portfolio content.
Minor Corrections
January 2008
Update/Creation for V6.0 April-08 portfolio content.

November 2007
Update for DR5.
September 2007
Update for OAM05.2 after internal review.
August 2007
Update for OAM05.2
SYSTEM RELEASE UMTS 5.1

July 2007
Update for UA 5.0 Channel Readiness.
March 2007
November 2006
Publication history

Update for OAM 5.1.0 / UA 5.0 [UMTS 5.1]
The Publication History information for the outdated releases

has been deleted.
Document creation date: March 2003
Table of contents
1 About this publication................................................................................................................................................... 9

2 Roadmap to Performance Management documentation..........................................................................................12
3 What's new....................................................................................................................................................................15
4 Access Network observation counters...................................................................................................................... 16
4.1 How Access Network observation counters are defined......................................................................................... 17
4.2 How Access Network observation counters are described......................................................................................24
5 MSS counters families................................................................................................................................................. 27
5.1 ACCOUNT ATM Vcc............................................................................................................................................... 28
5.2 ACCOUNT ATM Vpc............................................................................................................................................... 38
6 MSS counters index..................................................................................................................................................... 46
List of figures
Figure 1 - Roadmap to Performance Management documentation...................................................... ............. ......... 13

Figure 2 - MSS containment tree.......................................................................................................... ............. ......... 18
List of tables
Table 1 - Table of aggregation rules..................................................................................................... ............. ......... 22

Table 2 - VS.AcVccIngressCellCountClp0 - #30001............................................................................. ............. ......... 28
Table 3 - VS.AcVccIngressCellCountClp01 - #30002........................................................................... ............. ......... 29
Table 4 - VS.AcVccEgressCellCountClp0 - #30003........................................................................................... ......... 30
Table 5 - VS.AcVccEgressCellCountClp01 - #30004......................................................................................... ......... 31
Table 6 - VS.AcVccIngressDiscardedClp0 - #30005.......................................................................................... ......... 32
Table 7 - VS.AcVccIngressDiscardedClp01 - #30006........................................................................................ ......... 33
Table 8 - VS.AcVccEgressDiscardedClp0 - #30007............................................................................. ............. ......... 35
Table 9 - VS.AcVccEgressDiscardedClp01 - #30008........................................................................... ............. ......... 36
Table 10 - VS.AcVpcIngressCellCountClp0 - #30101........................................................................................ ......... 38
Table 11 - VS.AcVpcIngressCellCountClp01 - #30102...................................................................................... ......... 39
Table 12 - VS.AcVpcEgressCellCountClp0 - #30103........................................................................... ............. ......... 39
Table 13 - VS.AcVpcEgressCellCountClp01 - #30104......................................................................... ............. ......... 40
Table 14 - VS.AcVpcIngressDiscardedClp0 - #30105.......................................................................... ............. ......... 41
Table 15 - VS.AcVpcIngressDiscardedClp01 - #30106........................................................................ ............. ......... 42
Table 16 - VS.AcVpcEgressDiscardedClp0 - #30107........................................................................... ............. ......... 43
Table 17 - VS.AcVpcEgressDiscardedClp01 - #30108......................................................................... ............. ......... 44
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 OAM07.0 System Release.
Audience
This publication is intended for network controllers responsible for the Performance Management of
the UMTS Access Network.
Prerequisites
It is recommended that readers become familiar with the following Technical Publications :
Alcatel-Lucent 9300 W-CDMA Product Family - Performance Management (NN-20500-033)
Alcatel-Lucent 9353 Management System - Access Network Management Overview

(NN-20500-031) provides a functional overview of the Operation, Administration and
Maintenance (OAM) subsystem of the Access Network.
How this publication is organized

This publication consists of the following modules:
"Road map to Utran" presents the documents in the UTRAN documentation suite.
"What is new in Access Network Observation Counters" presents the changes and, or the
new features introduced for the UMTS 7.0 release.
"Access Network observation counters" is split into the following sections:

"How Access Network observation counters are defined" provides information about the
counter definition template, counter types on the OAM GUI, and counter hierarchy.
"How Access Network observation counters are described" describes the Access
Network observation counters.
"MSS Platform counter families" lists MSS platform counter families and presents their
10
counters. Each counter is described separately in a table, and these tables are arranged in
alphanumerical order.
Index presents the index of each Access Network observation counter.
Vocabulary conventions
For a list of UMTS terms used in this document, see the Alcatel-Lucent 9300 W-CDMA Product
Family - Terminology ( NN-20500-002).
The specific acronyms used in this publication are the following:
A. Release
Available Release
CC
Cumulative Counter
CFN
Connection Frame Number
CUM
CUMulative
DER
Discrete Event Registration counter
DTD
Document Type Definition
mW
milliWatt
NEI
NEIghboring
SI
Status Inspection
VAL
VALue counter
The specific terms used in this publication are the following:

Access Stratum Config- Pointer to a pre-defined set of Radio Bearers providing a given Rauration
dio Access Bearer service.
For example:
the Downlink (DL) access stratum configuration which number is

1 is dedicated to voice support; it comprises the following Radio
Bearers : 3 x 12.2 Kbps CS RBs on DTCH and 3 x 3.4 Kbps
SRB on DCCH.
the DL access stratum configuration which number is 2 is dedicated to packet support at 64 Kbps; it comprises the following Radio Bearers : 1 x 64 Kbps PS RB on DTCH and 3 x 3.4 Kbps
SRB for DCCH.
Refer to the following configurations:
Downlink Access Stratum Configuration (DASC)
Downlink Radio Bearer Set Configuration (DRBS)
Uplink Access Stratum Configuration (UASC)
Uplink Radio Bearer Set Configuration (URBS)
Connection Frame Num- CFN is the frame counter used for the L2/transport channel synber (CFN)
chronisation between UE and UTRAN. A CFN value is associated to
11
each Transport Block Set (TBS) and it is passed together with it

through the MAC-L1 SAP. CFN provides a common frame reference
(at L2) to be used that is for synchronized transport channel reconfiguration.
Measurement
Term used in 3GPP TS 32.104 specifications. It has the same

meaning as the word 'counter' and is used in this publication to distinguish a counter from a '(radio) measurement'.
Reference cell
Cell ranking first in a UE active set considering a radio criteria , that

means the cell supposed to provide on average the best radio quality for the reception of the next frames.
The reference cell is the primary cell considered in RRM.
12
Roadmap to Performance Management documentation

The figure next page shows where the current document stands within the W-CDMA Customer
Documentation.
Note:
For a global view of the W-CDMA Customer Documentation, see Roadmap chapter in:
Alcatel-Lucent 9300 W-CDMA Product Family - Document Collection Overview

(NN-20500-050)
Alcatel-Lucent 9300 W-CDMA Product Family - Access Network Management Overview

(NN-20500-031)
13
Figure 1 Roadmap to Performance Management documentation
14
15
What's new
For information about What's new section, see : Alcatel-Lucent 9300 W-CDMA Product Family UA07.0 / OAM07.0 Operational Impacts: CM, FM and PM Delta NN-20500-052
16
Access Network observation counters

This section includes the following topics:
"How Access Network observation counters are defined"
"How Access Network observation counters are described"
17
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.
18
Figure 2 MSS containment tree
Note: Objects that report counters are in bold underlined.

For more information about UTRAN objects and their relationships, refer to the Alcatel-Lucent 9353
Management System - Access Network Management Overview (NN-20500-031) publication.
Wording assumption
Both wordings counter and measurement are equally used in this document to identify the same
concept. Usually, Alcatel-Lucent uses the term counter to distinguish a counter from a (radio)
measurement
3GPP Performance Management specifications preferably use measurement. When the context
refers to 3GPP specifications, measurement is used, while counter is used in Alcatel-Lucent
specific part, but both wordings are equivalent.
Counter definition template

The following template used to describe the counters is extracted from 3GPP TS 32.104
specifications.
19
Measurement name (section header)

This is a descriptive name of the measurement type.
A-Description
This section contains an explanation of the measurement operation.
B-Collection
This section contains the form of the obtained measurement data:
CC (Cumulative Counter) is incremented by 1 each time the counted event occurs.
GAUGE (dynamic variable), data being measured can vary during the period of measurement.
DER (Discrete Event Registration), data related to a particular event is captured every nth event,
where n can be 1 or larger.
SI (Status Inspection), data related to the mean value is captured every nth sampling, where n
can be 1 or larger.
C-Condition (Event)
This section contains the condition that causes the measurement result data to be updated.
The condition is defined by identifying protocol related triggering events that either start or stop the
measurement processes or by updating the current measurement result value. When a precise
condition cannot be provided, the conditional circumstances behind the update are stated.
D-Result
This section contains a description of expected result value(s) (for example, a single integer value). If
more than one value is provided, the measurement is screened according to criteria, for example, a
number of call releases may be screened according to the cause of the call releases.
The number of call releases related to a given cause can be considered a subcounter. In that case,
the measurement result specification item includes a 'screening paragraph' that specifies the various
subcounters and their meanings.
E-Type
This section contains a short form of the measurement name specified in the header, which is used
to identify the measurement type in the result files.
F-Object Instance
This section contains the object class and its instance. The "measObjInstId" field identifies the
measured object class and its instance; for example, trunk1 means that object class trunk instance
#1 is being measured. The object class and instance values used for this purpose will be in
20
accordance with 3GPP TS 32.106. This means the NE or resource object model (defined in the Basic
CM IRP Information Model - 3GPP TS 32.106-5) and naming conventions (defined in the Naming
Convention for Managed Objects - 3GPP TS 32.106-8). This parameter, if applicable, will be
provided in the measurement job.
G-RANLocation
This section contains the Switching domain(s). Its measurement is applicable to Circuit Switched
and, or Packet Switched domains.
Note: Two counter specification items have been added to the seven preceding 3GPP items by
Alcatel-Lucent.
H-Range
This section contains the range of the counter.
I-Unit
This section contains the unit of the counter.
J-Available Release
This section states the Alcatel-Lucent UMTS system release(s) in which the counter had been
introduced.
K-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.
L-Notes
This section contains notes and FRS numbers associated with the counters.
Counter types on the OAM GUI

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

Note: This value is sampled once per hour and is indicated in the XML observation file.
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 to
implement an SI type measurement. This mechanism provides average values from raw counts
obtained by internal sampling (the time interval between two events is constant and is not accessible
to users). The counter is incremented by a sampled value on the sampling event occurrence.
Alcatel-Lucent provides the following:
the cumulated value (.Cum in XML files)
the number of samplings (.NbEvt in XML files)
the averaged value (.Avg in XML files)
the maximum sampled value (.Max in XML files)
the minimum sampled value (.Min in XML files)

Note: The averaged value is equal to cumulated value/number of samplings.
Note: Alcatel-Lucent does not generally implement GAUGE type measurements because
providing the current value of a measurement by incrementing it by 1 when a positive event occurs
and by decrementing it by 1 when a negative event occurs, can lead to some shifts if an event is
missed.
Note: The reported value counter is collected by a non real time task at the end of each
observation period. The collection period (usually one hour) for the Performance Management file
does not imply that all .NbEvt of LOAD counters are exactly equal to the number of counter
periods included in one collection (12 for counters with 5mn granularity). Due to the low priority of
the Performance Management task, it is possible when the PM file is built that some samples can
miss. They will be included in the next file. This can lead to one file with NbEvt equal to 11 (for a
22
5mn counter), followed later by one with 13 (possibly with some 12 between). The averages
values calculated by computing .Cum/.NbEvt are still meaningful, as the samples added in .Cum
are coherent with the .NbEvt value.
Counter hierarchy
An observation counter stored in XML files can contain one or several levels.
A dot (.) separates two successive levels.
The following example shows the counter hierarchy with five levels.
Example:
radioLink.establishment.failure.cause<Name>.Avg
Counters with one level do not end with a dot.
Example:
droppedLastRadioLink
Aggregation rules
When aggregating counters from different periods of observation (temporal aggregation) you must
follow the following rules.
Let X1,X2,...,Xn the measurements from periods 1,2,...,n and X the resulting value over the total
period.
The following table presents a rule for each counter.
Table 1 Table of aggregation rules
Rule
Results
Apply to
Rtotal
X.cum = X1.cum + X2.cum + ... + Xn.cum
CUM (CC) counters
Rload/Rval
X.cum = X1.cum + ... + Xn.cum
Some LOAD and VAL

counters
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)
Rload*
Same as Rload but resulting X.cum has no physical meaning due to the nature of the measurement (like percents) and is not interpreted but is
necessary for intermediate computations.
Some LOAD counters
Ravg
X = Xi / n
MSS counters
where Xi (i = 1 to n) represent average values

Radd
X = Xi
MSS counters
23
Rule
Results
Apply to
where Xi (i = 1 to n) represent cumulative values

Rmin
X = min (Xi)
MSS counters
where Xi (i = 1 to n) represent minimum values

Rmax
X = max (Xi)
MSS counters
where Xi (i = 1 to n) represent maximum values
24
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 UA7.0 system release
are as follows:
C-Node application counters
I-Node platform counters
Node B counters
These counters have been divided into the three following sets of families:
"RNC counter families"
"NodeB counter families"
"MSS counter families"
Each counter family is attached to a given UMTS feature (for example, Handover counters, where
hard handover performances are reported) or to a Performance Management purpose for example,
User Plane Traffic counters, where counters related to traffic observation are grouped together).
Access observation file structure

Some observation counters are processed in order to provide temporal and spatial aggregations. The
following observation counter records are available:
single period
hourly aggregated
daily aggregated
Each observation file produces single, hourly and daily observation counter records. At the dedicated
NE level, a predetermined subset of these data are aggregated.
The file name convention for an observation is as follows:
<type><startdate>.<starttime>-<endtime>_<NE>[-<RC>].
Where:
type is set to A which indicates one of the following aggregated observations:
the observation file contains data originated from a single NE for a unique time period.
the observation file contains data originated from a single NE for an hourly aggregated file.
25
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 "INodernc12").
List of possible NE types:
RNCCN
INode
ANode
NodeB
POC
Or the BTS name using the NE userLabel as a NE ID (for example "NodeB-A10km215").
RC is an optional running count. In case of PPT aggressive mode collection,the value is 2+.
Note : If the RC is absent, the "-" separator is absent as well.
Refer to the following table for an interpretation of the codes:
Code
Description
YYYY
The 4-digit year
MM
The month of the year (01, 02,..., 12) for file creation time at RNC level
DD
The day of the month (01, 02,..., 31) for file creation time at RNC level
hh
The 2-digit hour (00, 01,..., 23). In the case of daily aggregation files, hh is always 00.
mm
The 2-digit minute of the hour. Possible values are by increments of five
minutes: 00, 05, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55. In the case of
hourly or daily aggregation files, mm is always 00.
#GMT
Difference between local time and Greenwich Meridian Time (+/-hhmm). At

10:15:02 in Paris, the 13 April 2005 in Paris, the #GMT is +0100 = the
hhmm#GMT is 1015+0100.At 18:12:11 in New York, the 13 April 2005, the
#GMT is #0500 = the hhmm#GMT is 1812-0500.
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 for accounting is 60
and for stats are 15, 30 and 60.
26
The directory of the RNC I-Node observation XML file for statistic counters on PerfServer is as
follows:
For Stats:
/opt/nortel/data/utran/observation/stats/<YYYYMMDD>/INode-<RNC><PPUserLabel>
For Accounting:
/opt/nortel/data/utran/observation/account/<YYYYMMDD>/INode-<RNC><PPUserLabel>
For more information about MSS record files, see the Alcatel-Lucent 9300 W-CDMA Product Family Performance Management (NN-20500-033) publication.
27
MSS counters families
ACCOUNT ATM Vcc
ACCOUNT ATM Vpc
28
5.1
ACCOUNT ATM Vcc

Alcatel-Lucent
counter number
Counter name
#30001
VS.AcVccIngressCellCountClp0
#30002
#30003
VS.AcVccEgressCellCountClp0
#30004
#30005
VS.AcVccIngressDiscardedClp0
#30006
#30007
VS.AcVccEgressDiscardedClp0
#30008
Table 2 VS.AcVccIngressCellCountClp0 - #30001

A-Description
This Attribute contains the number of high priority cells (with CLP=0) received from the link during the accounting interval.
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
Sub-Counter #1: NA
Sub-Counter #2: NA
Sub-Counter #3: NA
Sub-Counter #4: NA
Sub-Counter #5: NA
E-Type
VS.AcVccIngressCellCountClp0 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vcc)
VS.AcVccIngressCellCountClp0 (RNC/RNCEquipment/INode/EM/Ss7/SaalNni)
VS.AcVccIngressCellCountClp0 (RNC/RNCEquipment/INode/EM/Aal2If/Path)
VS.AcVccIngressCellCountClp0 (RNC/RNCEquipment/INode/EM/Aal2If/Alcap)
VS.AcVccIngressCellCountClp0 (RNC/RNCEquipment/INode/EM/Iub/Sig)
29
([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmMpe/Ac)
F-Object Instance
Vcc
G-RAN Location
[RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vcc
H-Range
0..2^63-1
I-Unit
ATM cells
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 3 VS.AcVccIngressCellCountClp01 - #30002
A-Description
This Attribute indicates the total number of cells (with CLP=0 or CLP=1) received from the link
during the accounting interval.
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
Sub-Counter #1: NA
Sub-Counter #2: NA
Sub-Counter #3: NA
Sub-Counter #4: NA
Sub-Counter #5: NA
E-Type
([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vcc)
VS.AcVccIngressCellCountClp01 (RNC/RNCEquipment/INode/EM/Ss7/SaalNni)
30
VS.AcVccIngressCellCountClp01 (RNC/RNCEquipment/INode/EM/Aal2If/Path)
VS.AcVccIngressCellCountClp01 (RNC/RNCEquipment/INode/EM/Aal2If/Alcap)
VS.AcVccIngressCellCountClp01 (RNC/RNCEquipment/INode/EM/Iub/Sig)
F-Object Instance
Vcc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 4 VS.AcVccEgressCellCountClp0 - #30003
A-Description
This Attribute contains the number of high priority cells (with CLP=0) transmitted on the link
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
Sub-Counter #1: NA
Sub-Counter #2: NA
Sub-Counter #3: NA
Sub-Counter #4: NA
Sub-Counter #5: NA
31
E-Type
VS.AcVccEgressCellCountClp0 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vcc)
VS.AcVccEgressCellCountClp0 (RNC/RNCEquipment/INode/EM/Ss7/SaalNni)
VS.AcVccEgressCellCountClp0 (RNC/RNCEquipment/INode/EM/Aal2If/Path)
VS.AcVccEgressCellCountClp0 (RNC/RNCEquipment/INode/EM/Aal2If/Alcap)
VS.AcVccEgressCellCountClp0 (RNC/RNCEquipment/INode/EM/Iub/Sig)
F-Object Instance
Vcc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 5 VS.AcVccEgressCellCountClp01 - #30004
A-Description
This Attribute indicates the total number of cells (with CLP=0 or CLP=1) transmitted on the link
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
Sub-Counter #1: NA
Sub-Counter #2: NA
32
Sub-Counter #3: NA
Sub-Counter #4: NA
Sub-Counter #5: NA
E-Type
VS.AcVccEgressCellCountClp01 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vcc)
VS.AcVccEgressCellCountClp01 (RNC/RNCEquipment/INode/EM/Ss7/SaalNni)
VS.AcVccEgressCellCountClp01 (RNC/RNCEquipment/INode/EM/Aal2If/Path)
VS.AcVccEgressCellCountClp01 (RNC/RNCEquipment/INode/EM/Aal2If/Alcap)
VS.AcVccEgressCellCountClp01 (RNC/RNCEquipment/INode/EM/Iub/Sig)
F-Object Instance
Vcc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 6 VS.AcVccIngressDiscardedClp0 - #30005
A-Description
This Attribute indicates the number of high priority cells or frames (with CLP=0) received from
the link and discarded (not transmitted to the switch) during the accounting interval. - For consistency with other operational measurements for various applications, the count is expressed
either as number of cells or as number of frames. - For applications: Loop, CES, Wireless,
PVG, and ABS, the count is expressed in cells. - For applications: FrAtm, PORS, ATMMPE,
and control channels for SVCs, the count is expressed in frames. - For applications: Test,
SVCs, SVPs, and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 is
used, the count is expressed in frames.
B-Collection
33
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
Sub-Counter #1: NA
Sub-Counter #2: NA
Sub-Counter #3: NA
Sub-Counter #4: NA
Sub-Counter #5: NA
E-Type
VS.AcVccIngressDiscardedClp0 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vcc)
VS.AcVccIngressDiscardedClp0 (RNC/RNCEquipment/INode/EM/Ss7/SaalNni)
VS.AcVccIngressDiscardedClp0 (RNC/RNCEquipment/INode/EM/Aal2If/Path)
VS.AcVccIngressDiscardedClp0 (RNC/RNCEquipment/INode/EM/Aal2If/Alcap)
VS.AcVccIngressDiscardedClp0 (RNC/RNCEquipment/INode/EM/Iub/Sig)
F-Object Instance
Vcc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells or frames
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 7 VS.AcVccIngressDiscardedClp01 - #30006
A-Description
34
This Attribute indicates the total number of cells or frames (with CLP=0 or CLP=1) received
from the link and discarded (not transmitted to the switch) during the accounting interval. For
consistency with other operational measurements for various applications, the count is expressed either as number of cells or as number of frames. For applications: Loop, CES, Wireless, PVG, and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATMMPE, and control channels for SVCs, the count is expressed in frames. For applications: Test,
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
Sub-Counter #1: NA
Sub-Counter #2: NA
Sub-Counter #3: NA
Sub-Counter #4: NA
Sub-Counter #5: NA
E-Type
VS.AcVccIngressDiscardedClp01 (RNC/RNCEquipment/INode/EM/Ss7/SaalNni)
VS.AcVccIngressDiscardedClp01 (RNC/RNCEquipment/INode/EM/Aal2If/Path)
VS.AcVccIngressDiscardedClp01 (RNC/RNCEquipment/INode/EM/Aal2If/Alcap)
VS.AcVccIngressDiscardedClp01 (RNC/RNCEquipment/INode/EM/Iub/Sig)
F-Object Instance
Vcc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells or frames
J-Available Release
35
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 8 VS.AcVccEgressDiscardedClp0 - #30007
A-Description
the switch and discarded (not transmitted on the link) during the accounting interval. For consistency with other operational measurements for various applications, the count is expressed
either as number of cells or as number of frames. For applications: Loop, CES, Wireless, PVG,
and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATMMPE, and control channels for SVCs, the count is expressed in frames. For applications: Test, SVCs, SVPs,
and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 is used, the count
is expressed in frames.
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
Sub-Counter #1: NA
Sub-Counter #2: NA
Sub-Counter #3: NA
Sub-Counter #4: NA
Sub-Counter #5: NA
E-Type
VS.AcVccEgressDiscardedClp0 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vcc)
VS.AcVccEgressDiscardedClp0 (RNC/RNCEquipment/INode/EM/Ss7/SaalNni)
VS.AcVccEgressDiscardedClp0 (RNC/RNCEquipment/INode/EM/Aal2If/Path)
VS.AcVccEgressDiscardedClp0 (RNC/RNCEquipment/INode/EM/Aal2If/Alcap)
VS.AcVccEgressDiscardedClp0 (RNC/RNCEquipment/INode/EM/Iub/Sig)
F-Object Instance
Vcc
36
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells or frames
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 9 VS.AcVccEgressDiscardedClp01 - #30008
A-Description
from the switch and discarded (not transmitted on the link) during the accounting interval. For
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
Sub-Counter #1: NA
Sub-Counter #2: NA
Sub-Counter #3: NA
Sub-Counter #4: NA
Sub-Counter #5: NA
E-Type
37
VS.AcVccEgressDiscardedClp01 (RNC/RNCEquipment/INode/EM/Ss7/SaalNni)
VS.AcVccEgressDiscardedClp01 (RNC/RNCEquipment/INode/EM/Aal2If/Path)
VS.AcVccEgressDiscardedClp01 (RNC/RNCEquipment/INode/EM/Aal2If/Alcap)
VS.AcVccEgressDiscardedClp01 (RNC/RNCEquipment/INode/EM/Iub/Sig)
F-Object Instance
Vcc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells or frames
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
38
5.2
ACCOUNT ATM Vpc

Alcatel-Lucent
counter number
Counter name
#30101
VS.AcVpcIngressCellCountClp0
#30102
#30103
VS.AcVpcEgressCellCountClp0
#30104
#30105
VS.AcVpcIngressDiscardedClp0
#30106
#30107
VS.AcVpcEgressDiscardedClp0
#30108
Table 10 VS.AcVpcIngressCellCountClp0 - #30101

A-Description
This Attribute contains the number of high priority cells (with CLP=0) received from the link during the accounting interval.
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
E-Type
VS.AcVpcIngressCellCountClp0 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vpc)
F-Object Instance
Vpc
G-RAN Location
[RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vpc
H-Range
0..2^63-1
I-Unit
ATM cells
J-Available Release
05_01_00
39
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 11 VS.AcVpcIngressCellCountClp01 - #30102
A-Description
This Attribute indicates the total number of cells (with CLP=0 or CLP=1) received from the link
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
E-Type
([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vpc)
F-Object Instance
Vpc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 12 VS.AcVpcEgressCellCountClp0 - #30103
A-Description
This Attribute contains the number of high priority cells (with CLP=0) transmitted on the link
40

B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
E-Type
VS.AcVpcEgressCellCountClp0 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vpc)
F-Object Instance
Vpc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 13 VS.AcVpcEgressCellCountClp01 - #30104
A-Description
This Attribute indicates the total number of cells (with CLP=0 or CLP=1) transmitted on the link
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
E-Type
41
F-Object Instance
Vpc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 14 VS.AcVpcIngressDiscardedClp0 - #30105
A-Description
the link and discarded (not transmitted to the switch) during the accounting interval. - For consistency with other operational measurements for various applications, the count is expressed
either as number of cells or as number of frames. - For applications: Loop, CES, Wireless,
PVG, and ABS, the count is expressed in cells. - For applications: FrAtm, PORS, ATMMPE,
and control channels for SVCs, the count is expressed in frames. - For applications: Test,
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
E-Type
VS.AcVpcIngressDiscardedClp0 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vpc)
F-Object Instance
Vpc
42
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells or frames
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 15 VS.AcVpcIngressDiscardedClp01 - #30106
A-Description
from the link and discarded (not transmitted to the switch) during the accounting interval. For
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
E-Type
F-Object Instance
Vpc
G-RAN Location
H-Range
0..2^63-1
43
I-Unit
ATM cells or frames
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
Table 16 VS.AcVpcEgressDiscardedClp0 - #30107
A-Description
the switch and discarded (not transmitted on the link) during the accounting interval. For consistency with other operational measurements for various applications, the count is expressed
either as number of cells or as number of frames. For applications: Loop, CES, Wireless, PVG,
and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATMMPE, and control channels for SVCs, the count is expressed in frames. For applications: Test, SVCs, SVPs,
and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 is used, the count
is expressed in frames.
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
E-Type
VS.AcVpcEgressDiscardedClp0 ([RNC/RNCEquipment/INode|POCEquipment]/EM/AtmIf/Vpc)
F-Object Instance
Vpc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells or frames
J-Available Release
05_01_00
K-Aggregation Rule
44
Radd
L-Notes
FRS: 30069
Table 17 VS.AcVpcEgressDiscardedClp01 - #30108
A-Description
from the switch and discarded (not transmitted on the link) during the accounting interval. For
B-Collection
CUMULATE
C-Condition (Event)
D-Result
Sub-Counter #0: NA
E-Type
F-Object Instance
Vpc
G-RAN Location
H-Range
0..2^63-1
I-Unit
ATM cells or frames
J-Available Release
05_01_00
K-Aggregation Rule
Radd
L-Notes
FRS: 30069
45
46
MSS counters index
#30001 VS.AcVccIngressCellCountClp0
#30002 VS.AcVccIngressCellCountClp01
#30003 VS.AcVccEgressCellCountClp0
#30004 VS.AcVccEgressCellCountClp01
#30005 VS.AcVccIngressDiscardedClp0
#30006 VS.AcVccIngressDiscardedClp01
#30007 VS.AcVccEgressDiscardedClp0
#30008 VS.AcVccEgressDiscardedClp01
#30101 VS.AcVpcIngressCellCountClp0
#30102 VS.AcVpcIngressCellCountClp01
#30103 VS.AcVpcEgressCellCountClp0
#30104 VS.AcVpcEgressCellCountClp01
#30105 VS.AcVpcIngressDiscardedClp0
#30106 VS.AcVpcIngressDiscardedClp01
#30107 VS.AcVpcEgressDiscardedClp0
#30108 VS.AcVpcEgressDiscardedClp01
47

W-CDMA
Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction
Copyright 2003-2009 Alcatel-Lucent, All Rights Reserved

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

RTWP Rssi

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

RTWP Rssi

Diunggah oleh

Hak Cipta:

Format Tersedia

NN-20500-028

Wireless Service Provider Solutions

Counters Reference Guide for MSS

Wireless Service Provider Solutions

Counters Reference Guide for MSS

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

Copyright 2003-2009 Alcatel-Lucent, All Rights Reserved

SYSTEM RELEASE OAM06.0

Copyright 2003-2009 Alcatel-Lucent

Counters Reference Guide for MSS

Update after internal review.

SYSTEM RELEASE OAM05.2

SYSTEM RELEASE UMTS 5.1

NN-20500-028 10.03 Preliminary July 2009

Copyright 2003-2009 Alcatel-Lucent

Issue 07.01/EN Draft

The Publication History information for the outdated releases

Copyright 2003-2009 Alcatel-Lucent

Counters Reference Guide for MSS

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

NN-20500-028 10.03 Preliminary July 2009

Copyright 2003-2009 Alcatel-Lucent

Figure 1 - Roadmap to Performance Management documentation...................................................... ............. ......... 13

Copyright 2003-2009 Alcatel-Lucent

Counters Reference Guide for MSS

Table 1 - Table of aggregation rules..................................................................................................... ............. ......... 22

NN-20500-028 10.03 Preliminary July 2009

Copyright 2003-2009 Alcatel-Lucent

About this publication

"How this publication is organized"

Alcatel-Lucent 9300 W-CDMA Product Family - Performance Management (NN-20500-033)

Alcatel-Lucent 9353 Management System - Access Network Management Overview

How this publication is organized

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

Copyright 2003-2009 Alcatel-Lucent

Counters Reference Guide for MSS

Index presents the index of each Access Network observation counter.

Connection Frame Number

Discrete Event Registration counter

Document Type Definition

The specific terms used in this publication are the following:

the Downlink (DL) access stratum configuration which number is

NN-20500-028 10.03 Preliminary July 2009

Copyright 2003-2009 Alcatel-Lucent

each Transport Block Set (TBS) and it is passed together with it

Term used in 3GPP TS 32.104 specifications. It has the same

Cell ranking first in a UE active set considering a radio criteria , that

Copyright 2003-2009 Alcatel-Lucent

Counters Reference Guide for MSS

Roadmap to Performance Management documentation

Alcatel-Lucent 9300 W-CDMA Product Family - Document Collection Overview

Alcatel-Lucent 9300 W-CDMA Product Family - Access Network Management Overview

NN-20500-028 10.03 Preliminary July 2009

Copyright 2003-2009 Alcatel-Lucent

Figure 1 Roadmap to Performance Management documentation

Copyright 2003-2009 Alcatel-Lucent

Counters Reference Guide for MSS

NN-20500-028 10.03 Preliminary July 2009

Copyright 2003-2009 Alcatel-Lucent

Copyright 2003-2009 Alcatel-Lucent

Counters Reference Guide for MSS

Access Network observation counters