umts access counters list umt sys dd 75.v2.13

7/27/2019 Umts Access Counters List Umt Sys Dd 75.v2.13

1/136

UMTS Access counters list

Document number: UMT/SYS/DD/0075Document issue: 02.13 / ENDocument status: StandardDate: 27/Jun/2003

External document

Copyright 2000 Nortel Networks, All Rights Reserved

Printed in France

NORTEL NETWORKS CONFIDENTIAL:

The information contained in this document is the property of Nortel Networks. Except as specifically authorized in

writing by Nortel Networks, the holder of this document shall keep the information contained herein confidentialand shall protect same in whole or in part from disclosure and dissemination to third parties and use same for

evaluation, operation and maintenance purposes only.

The content of this document is provided for information purposes only and is subject to modification. It does not

constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information

contained herein, including but not limited to the suitability and performances of the product or its intended

application.

The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate

logo, the NORTEL Globemark, UNIFIED NETWORKS. The information in this document is subject to change

without notice. Nortel Networks assumes no responsibility for errors that might appear in this document.

All other brand and product names are trademarks or registered trademarks of their respective holders.


2/136


Nortel Networks confidential

UMT/SYS/DD/0075 02.13 / EN Standard 27/Jun/2003 Page 2/136


3/136




PUBLICATION HISTORY

19/Mar/2001

Issue 01.01 / EN, Provisional

Document creation

01/Jun/2001

Issue 01.02 / EN, Approved

Document update after the final agreement on the V1 counter list

17/Sept/2001


Document update after:

- agreement on V2 RNC AN counter list as stated in internal documentUMT/RNC/GES/0032 V .1.01 dated 02/Jul/2001

- issue of internal document RNC Performance Management Spooling ofInterface Node and Access Node counters and traces to the OMC in V2version AA02 dated 04/Sep/2001

- issue of Functional Note NodeB UTRAN counters Functional Note RFF13479 UMT/BTS/DD/0345 dated 05/Jul/2001

28/Sept/2001



- follow-up meetings for clarification of the three above mentioned internaldocuments

12/Oct/2001



- review meeting held on Friday the 12th

of October

- new releases of internal iRNC and iBTS documents on which is based thecurrent document

18/Oct/2001

Issue 02.04 / EN, Draft


- last comments

Status reset to draft in order to be consistent with KIOSK procedure

22/Oct/2001

Issue 02.05 / EN, DraftIntroduction of RNC and iBTS load management counters.


4/136




Split of Radio bearer release success / unsuccess counters per controlled cell / perneighboring RNC.

Screenings on failure causes for some counters related to radio-link management byRNSAP.

Correction on some name errors of HO counters (Detection modified into Request).

Correction of the understanding of the counter Number of dropped calls on last radio-link release

Minor corrections and clarifications

19/Apr/2002

Alignment of counter names on counter names provided on the ADI export interface ofthe Performance Server. Each counter value provided by a screened counter isidentified by its own counter name.

A global numbering plane is used for UTRAN Access counters whichever is therelated Network Element (RNC or iBTS).

Editorial corrections related to the following counters:

- Number of 3G to 2G handovers requests (per cell / per RNC)

- Number of release commands (on Iu CS / on Iu PS

Semantic modifications on the following counters:

- All RRC radio-link management counters (c.f. 6)

- All RB related counters in chapter 9 RAB and RB management

Introduction of RB reconfiguration counters for AlwaysOn feature observation.

Removal of counters Call drop on last RB release (per cell / per RNC)Introduction of iBTS ATM counters Number of sent cells (AAL2 / AAL5).

Introduction of iBTS Radio counter MCPA power (average / min /max).

28/Jun/2002

Clarification on the scope of the document (1.2)

Corrections related to iBTS counters ( 17. and 17): NORTEL # , localisation,..

Screened counter names provided ( 9.)

12/Jul/2002

For each counter is provided in specification field H. :

- The software version in which the counter had been introduced

- If the counter definition had been modified in a subsequent version, thenonly the version in which the current counter specification had beenintroduced is provided.

The only considered versions are the software versions with a customer visibility i.e:

- V 1.2.b

- V2 D2

- V2 D4

Revision bars show modifications between V 02.06 and V 02.08 of the document


5/136




23/Aug/2002


References to V2 drop # replaced by references to V2 software delivery # :

The only considered versions are the last software deliveries of a new software drop,a software drop providing a consistent set of new features and the related newservices.

Considered versions are therefore:

- V 1.2.b

- V 2.0c

- V 2.0e

- V 2.1

Introduction of the counters related to the feature Simplified IRM (feature churned

back from V3 to V2.1).

11/Sept/2002


09/Apr/2003

Issue 02.11 / EN, Preliminary

Counters renamed to follow 3GPP-like naming in results files. Modifications of Annexe

1 (number of DLAsConf) and Annexes 2 and 3 to follow 3GPP TS 25.331 3.7.0causes. Corrections of several errors on units.

17/Apr/2003

Issue 02.12 / EN, Standard

Publish as standard after review. Corrections on the number of DL As Conf oncounters #615, #617 and #1303. Clarifications on counters #401 and #405.

27/Jun/2003

Issue 02.13 / EN, Standard

Clarification of BTS LOAD counters after CR Q00671611. The BTS computes theaverage value directly and sends it in the cumulative part of the counter and also setthe number of events to 1.


6/136




CONTENTS

1. INTRODUCTION..........................................................................................................................121.1. OBJECT..................................................................................................................................12

1.2. SCOPE OF THIS DOCUMENT .....................................................................................................12

1.3. AUDIENCE FOR THIS DOCUMENT ..............................................................................................12

2. RELATED DOCUMENTS............................................................................................................12

2.1. APPLICABLE DOCUMENTS ........................................................................................................12

2.2. REFERENCE DOCUMENTS ........................................................................................................13

3. DOCUMENT ORGANISATION ...................................................................................................143.1. FAMILIES OF COUNTERS ..........................................................................................................14

3.2. WORKING ASSUMPTIONS .........................................................................................................14

3.2.1 Wording.........................................................................................................................143.2.2 Specified counters are user available counters on the OMC GUI ................................143.2.3 Counters are specified according a Counter Definition Template ................................17

4. NBAP RADIO-LINK MANAGEMENT..........................................................................................20

4.1. NUMBER OF SUCCESSFUL NBAP RADIO-LINK SETUPS ...............................................................20

4.2. NUMBER OF FAILED NBAP RADIO-LINK SETUPS ........................................................................21

4.3. NUMBER OF SUCCESSFUL NBAP RADIO-LINK ADDITIONS...........................................................224.4. NUMBER OF FAILED NBAP RADIO-LINK ADDITIONS ....................................................................23

4.5. NUMBER OF SUCCESSFUL NBAP RADIO-LINK DELETIONS ..........................................................24

4.6. NUMBER OF FAILED NBAP RADIO-LINK DELETIONS ...................................................................25

4.7. NUMBER OF SUCCESSFUL NBAP RADIO-LINK RECONFIGURATION PREPARATIONS.......................25

4.8. NUMBER OF FAILED NBAP RADIO-LINK RECONFIGURATION PREPARATIONS ................................26

4.9. NUMBER OF NBAP RADIO-LINK RECONFIGURATION CANCELS ....................................................27

4.10. NUMBER OF NBAP RADIO-LINK RECONFIGURATION COMMITS ....................................................28

4.11. NUMBER OF NBAP RADIO-LINKS ..............................................................................................29

4.11.1 Average number of NBAP radio-links ...........................................................................294.11.2 Minimum number of NBAP radio-links..........................................................................304.11.3 Maximum number of NBAP radio-links.........................................................................30

4.12. NUMBER OF DROPPED CALLS ON LAST RADIO-LINK RELEASE......................................................31

5. HARD HAND-OVERS..................................................................................................................32

5.1. NUMBER OF INTER-RAT HANDOVER FROM UTRAN COMMANDS PER CELL .................................32

5.2. NUMBER OF INTER-RAT HANDOVER FROM UTRAN COMMANDS PER RNC.................................33

5.3. NUMBER OF INTER-RAT HANDOVER FROM UTRAN FAILURES PER CELL ....................................33

5.4.

NUMBER OF FAILED INTER-RAT HANDOVER FROM UTRAN PER RNC........................................34

5.5. NUMBER OF RRCCELLCHANGEORDERFROMUTRAN PER CELL...................................35


7/136




5.6. NUMBER OF RRCCELLCHANGEORDERFROMUTRAN PER RNC ..................................36

5.7. NUMBER OF CELLCHANGEORDERFROMUTRAN FAILURE PER CELL ...............................36

5.8. NUMBER OF RRCCELLCHANGEORDERFROMUTRAN FAILURE PER RNC .....................37

5.9. NUMBER OF

3GTO

2G

HANDOVER REQUESTS PER CELL..........................................................38

5.10. NUMBER OF 3GTO2G HANDOVER REQUESTS PER RNC .........................................................39

6. RRC RADIO-LINK MANAGEMENT............................................................................................40

6.1. NUMBER OF SUCCESSFUL RRCACTIVESETUPDATES PER CELL .........................................40

6.2. NUMBER OF SUCCESSFUL RRCACTIVESETUPDATES PER RNC ........................................41

6.3. NUMBER OF FAILED RRCACTIVESETUPDATES PER CELL ..................................................41

6.4. NUMBER OF FAILED RRCACTIVESETUPDATES PER RNC..................................................42

7. RRC CONNECTION ....................................................................................................................44

7.1. NUMBER OF RRC CONNECTION REQUESTS ..............................................................................44

7.2. NUMBER OF SUCCESSFUL RRC CONNECTION ESTABLISHMENTS................................................44

7.3. NUMBER OF RRC CONNECTION ESTABLISHMENT FAILURES .......................................................45

7.4. NUMBER OF RRC CONNECTION RELEASES PERCELL.............................................................46

7.5. NUMBER OF RRC CONNECTION RELEASES PERRNC..............................................................47

8. IU INTERFACE............................................................................................................................49

8.1. NUMBER OF SUCCESSFUL SCCP CONNECTIONS AT IU INTERFACE.............................................49

8.2. NUMBER OF FAILED SCCP CONNECTIONS AT IU INTERFACE ......................................................498.3. NUMBER OF RELEASEREQUESTS ON IU CS .......................................................................50

8.4. NUMBER OF RELEASEREQUESTS ON IU PS .......................................................................51

8.5. NUMBER OF RELEASECOMMANDS ON IU CS......................................................................51

8.6. NUMBER OF RELEASECOMMANDS ON IU PS......................................................................52

9. RAB AND RB MANAGEMENT ...................................................................................................54

9.1. NUMBER OF SUCCESSFUL RAB ESTABLISHMENTS ....................................................................54

9.2. NUMBER OF FAILED RAB ESTABLISHMENTS..............................................................................55

9.3. NUMBER OF SUCCESSFUL RAB RELEASES ...............................................................................569.4. NUMBER OF FAILED RAB RELEASES ........................................................................................57

9.5. NUMBER OF SUCCESSFUL RADIO-BEARER ESTABLISHMENTS PERCELL...................................57

9.6. NUMBER OF SUCCESSFUL RADIO-BEARER ESTABLISHMENTS PERRNC....................................59

9.7. NUMBER OF REFUSED RADIO-BEARER ESTABLISHMENTS PER CELL ...........................................60

9.8. NUMBER OF REFUSED RADIO-BEARER ESTABLISHMENTS PER RNC...........................................60

9.9. NUMBER OF FAILED RADIO-BEARER ESTABLISHMENTS PER CELL ...............................................61

9.10. NUMBER OF FAILED RADIO-BEARER ESTABLISHMENTS PER RNC ..............................................62

9.11. NUMBER OF SUCCESSFUL RADIO-BEARER RELEASES PER CELL .................................................63

9.12. NUMBER OF SUCCESSFUL RADIO-BEARER RELEASES PER RNC ................................................64


8/136




9.13. NUMBER OF FAILED RADIO-BEARER RELEASES PER CELL ..........................................................65

9.14. NUMBER OF FAILED RADIO-BEARER RELEASES PER RNC..........................................................66

9.15. NUMBER OF SUCCESSFUL RADIO-BEARER RECONFIGURATIONS PER CELL ..................................67

9.16. NUMBER OF SUCCESSFUL

RADIO

-BEARER RECONFIGURATIONS PER

RNC .................................689.17. NUMBER OF FAILED RADIO-BEARER RECONFIGURATIONS PER CELL ...........................................69

9.18. NUMBER OF FAILED RADIO-BEARER RECONFIGURATIONS PER RNC...........................................70

10. RNSAP RADIO-LINK MANAGEMENT .......................................................................................72

10.1. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK SETUPS ............................................................72

10.2. NUMBER OF FAILED RNSAP RADIO-LINK SETUPS .....................................................................73

10.3. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK ADDITIONS ........................................................74

10.4. NUMBER OF FAILED RNSAP RADIO-LINK ADDITIONS .................................................................75

10.5. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK DELETIONS .......................................................7610.6. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK RECONFIGURATION PREPARATIONS ....................77

10.7. NUMBER OF FAILED RNSAP RADIO-LINK RECONFIGURATION PREPARATIONS .............................78

10.8. NUMBER OF RNSAP RADIO-LINK RECONFIGURATION CANCELS .................................................78

10.9. NUMBER OF RNSAP RADIO-LINK RECONFIGURATION COMMITS .................................................79

11. PAGING .......................................................................................................................................81

11.1. NUMBER OF RECEIVED PAGING REQUESTS ...............................................................................81

12. POWER MANAGEMENT ............................................................................................................8212.1. AVERAGE CELL POWER USED FOR SPEECH CALLS .....................................................................82

12.1.1 Average cell power used for speech calls.....................................................................8212.1.2 Minimum cell power used for speech calls ...................................................................8212.1.3 Maximum cell power used for speech calls .................................................................83

12.2. CELL POWER USED FOR DATA CALLS ......................................................................................83

12.2.1 Average cell power used for DATA calls.......................................................................8312.2.2 Minimum cell power used for DATA calls ....................................................................8312.2.3 Maximum cell power used for DATA calls ....................................................................84

12.3. AVERAGED POWER USED FOR SIGNALLING ...............................................................................84

12.3.1 Averaged power used for signalling..............................................................................84

12.3.2 Minimum power used for signalling...............................................................................8512.3.3 Maximum cell power used for signalling .......................................................................85

12.4. UPLINK RSSI ..........................................................................................................................86

12.4.1 Averaged uplink RSSI...................................................................................................8612.4.2 Minimum uplink RSSI....................................................................................................8612.4.3 Maximum uplink RSSI...................................................................................................86

13. QUALITY OF SERVICE...............................................................................................................88

13.1. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 1 PER CELL ........................................................88

13.2. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 1 PER RNC .......................................................89

13.3. NUMBER OF UNSUCCESSFUL DOWNSIZINGS STEP 1PERCELL ................................................90

13.4. NUMBER OF UNSUCCESSFUL DOWNSIZINGS STEP 1PERRNC..................................................91


9/136




13.5. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 2 PER CELL ........................................................92

13.6. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 2 PER RNC .......................................................93

13.7. NUMBER OF SUCCESSFUL UPSIZINGS PER CELL ........................................................................93

13.8. NUMBER OF SUCCESSFUL UPSIZINGS PER

RNC........................................................................9413.9. NUMBER OF UNSUCCESSFUL UPSIZINGS PERCELL.................................................................95

13.10. NUMBER OF UNSUCCESSFUL UPSIZINGS PERRNC ..............................................................96

13.11. NUMBER OF SUCCESSFUL IRM SCHEDULING DOWNGRADINGS PER CELL.................................97

13.12. NUMBER OF FAILED IRM SCHEDULING DOWNGRADINGS PER CELL ..........................................98

13.13. NUMBER OF SUCCESSFUL IRM SCHEDULING DOWNGRADINGS PER RNC................................99

13.14. NUMBER OF FAILED IRM SCHEDULING DOWNGRADINGS PER RNC ...................................... 100

14. USER PLANE TRAFFIC........................................................................................................... 102

14.1. TOTAL COUNT OF UPLINK RLC PAYLOAD ON COMMON CHANNELS ........................................... 10214.2. TOTAL COUNT OF DOWNLINK RLC PAYLOAD ON COMMON CHANNELS ...................................... 102

14.3. NUMBER OF UPLINK RLCPDUS ON COMMON CHANNELS ....................................................... 103

14.4. NUMBER OF DOWNLINK RLCPDUS ON COMMON CHANNELS .................................................. 103

14.5. NUMBER OF UPLINK RLCSDUS ON COMMON CHANNELS ....................................................... 104

14.6. NUMBER OF DOWNLINK RLCSDUS ON COMMON CHANNELS .................................................. 104

14.7. NUMBER OF DISCARDED RLCSDUS ON COMMON CHANNELS ................................................ 105

14.8. NUMBER OF RLC DUMMY PADDINGS ON COMMON CHANNELS ................................................. 105

14.9. NUMBER OF UPLINK MACPDUS ON COMMON CHANNELS ...................................................... 106

14.10. NUMBER OF DOWNLINK MACPDUS ON COMMON CHANNELS ............................................. 106

14.11. TOTAL COUNT OF UPLINK MAC PAYLOAD ON COMMON CHANNELS....................................... 107

14.12. TOTAL COUNT OF DOWNLINK MAC PAYLOAD ON COMMON CHANNELS.................................. 107

15. IUR INTERFACE....................................................................................................................... 108

15.1. NUMBER OF SUCCESSFUL SCCP CONNECTIONS AT IUR INTERFACE........................................ 108

15.2. NUMBER OF FAILED SCCP CONNECTIONS AT IUR INTERFACE ................................................. 108

16. RNC LOAD MANAGEMENT.................................................................................................... 109

16.1. LOAD OF TMU PROCESSORS ................................................................................................ 109

16.1.1 Average load of TMU processors .............................................................................. 10916.1.2 Minimum load of TMU processors ............................................................................. 10916.1.3 Maximum load of TMU processors ............................................................................ 110

17. NODE B PCM ........................................................................................................................... 112

17.1. LOSS OF INCOMING SIGNAL................................................................................................... 112

17.2. ALARM INDICATION SIGNAL ................................................................................................... 112

17.3. LOSS OF FRAME ALIGNMENT ................................................................................................. 112

17.4. FRAME ERROR ..................................................................................................................... 113

17.5. CRC................................................................................................................................... 113


10/136




17.6. REMOTEALARM INDICATION................................................................................................. 114

17.7. FRAMEALIGNMENT SIGNAL .................................................................................................. 114

17.8. E-BITS................................................................................................................................. 114

17.9. BIPOLAR

VIOLATION

............................................................................................................. 11517.10. SLIP EVENT ...................................................................................................................... 115

17.11. ERRORED SECONDS ......................................................................................................... 116

17.12. SEVERELY ERRORED SECONDS ........................................................................................ 116

17.13. BACKGROUND BLOCK ERRORS ......................................................................................... 116

17.14. UNAVAILABLE SECONDS ................................................................................................... 117

18. NODE B ATM............................................................................................................................ 118

18.1. NUMBER OF RECEIVED CELLS (AAL2) ................................................................................... 118

18.2. NUMBER OF LOST CPS PACKETS (AAL2).............................................................................. 11818.3. NUMBER OF STF PARITY ERRORS (AAL2)............................................................................. 118

18.4. NUMBER OF SEQUENCE NUMBER ERRORS (AAL2)................................................................ 119

18.5. NUMBER OF CPSHEADER CHECKSUMERROR (AAL2)........................................................ 119

18.6. NUMBER OF CPS LENGTH ERRORS (AAL2)........................................................................... 120

18.7. NUMBER OF LENGTH MISMATCHES (AAL2) ........................................................................... 120

18.8. NUMBER OF INVALID CID(AAL2).......................................................................................... 120

18.9. NUMBER OF CELLS WITH OFFSET FIELD >47(AAL2)............................................................. 121

18.10. NUMBER OF RECEIVED CELLS (AAL5) ............................................................................... 121

18.11. NUMBER OFABORT ERRORS (AAL5)................................................................................. 121

18.12. NUMBER OF LENGTH ERRORS (AAL5)............................................................................... 122

18.13. NUMBER OF CRC FRAME ERRORS (AAL5) ........................................................................ 122

18.14. NUMBER OF INVALID SIZE ERRORS (AAL5)......................................................................... 123

18.15. NUMBER OF SENT CELLS (AAL2)....................................................................................... 123

18.16. NUMBER OF SENT CELLS (AAL5)....................................................................................... 123

19. NODE B RADIO........................................................................................................................ 124

19.1. WIDE-BAND RECEIVED POWER ON MAIN ANTENNA .................................................................. 124

19.1.1 Average wide-band received power on Main antenna............................................... 12419.1.2 Minimum wide-band received power on Main antenna ............................................. 12419.1.3 Maximum wide-band received power on main antenna ............................................ 125

19.2. WIDE-BAND RECEIVED POWER ON DIVERSITY ANTENNA .......................................................... 125

19.2.1 Average wide-band received power on Diversity antenna......................................... 12519.2.2 Minimum wide-band received power on Diversity antenna ....................................... 12619.2.3 Maximum wide-band received power on diversity antenna....................................... 126

19.3. TRANSMITTED CARRIER POWER ............................................................................................ 127

19.3.1 Average transmitted carrier power............................................................................. 12719.3.2 Minimum transmitted carrier power............................................................................ 12719.3.3 Maximum transmitted carrier power........................................................................... 128

19.4. MULTI-CARRIER POWER AMPLIFIER POWER............................................................................ 12819.4.1 Average MCPA power................................................................................................ 128


11/136




19.4.2 Minimum MCPA power .............................................................................................. 12919.4.3 Maximum MCPA power ............................................................................................. 129

20. IBTS LOAD MANAGEMENT.................................................................................................... 130

20.1. CEMCAPACITY USED

........................................................................................................... 13020.1.1 Average CEM capacity used...................................................................................... 13020.1.2 Minimum CEM capacity used..................................................................................... 13020.1.3 Maximum CEM capacity used.................................................................................... 131

20.2. CEM RESOURCE ALLOCATION FAILURE ................................................................................. 131

21. ABBREVIATIONS AND DEFINITIONS.................................................................................... 133

21.1. ABBREVIATIONS ................................................................................................................... 133

21.2. DEFINITIONS ........................................................................................................................ 133

21.2.1 Access stratum configuration..................................................................................... 13321.2.2 Reference cell ............................................................................................................ 133

22. ANNEXE 1: DOWNLINK ACCESS STRATUM CONFIGURATIONS ..................................... 134

23. ANNEXE 2: RRC CONNECTION ESTABLISHMENT CAUSES ............................................. 135

24. ANNEXE 3: RRC CONNECTION RELEASE CAUSES........................................................... 136


12/136




1. INTRODUCTION

1.1. OBJECT

This document provides the list of UMTS Access counters as available on the userinterface.

1.2. SCOPE OF THIS DOCUMENT

The document applies to the complete version UMTS UA02 Access software.

Related FRS is FRS 013479 UTRAN Counters (UMTS02).

1.3. AUDIENCE FOR THIS DOCUMENT

Customers NORTEL Customer Support, PLM, R&D teams

2. RELATED DOCUMENTS

2.1. APPLICABLE DOCUMENTS

[A1] 3GPP TS 32.401

3rd Generation Partnership Project;

Technical Specification Group Services and System Aspects;

Telecommunication Management;

Performance Management (PM);

Concept and Requirements

(Release 4)

[A2] 3GPP TS 32.402





Performance Measurements - GSM

(Release 4)

[A3] 3GPP TS 32.403




13/136






Performance Measurements UMTS and combined UMTS/GSM

(Release 4)

2.2. REFERENCE DOCUMENTS

[R2] ITU-T G.775

Series G: Transmission Systems and Media, Digital Systems and Networks

Digital transmission systems - Terminal equipments;

Operations, administration and maintenance features of transmissionequipment

Loss of Signal (LOS), Alarm Indication Signal (AIS) and Remote DefectIndication (RDI) defect detection and clearance criteria for PDH signals

[R3] ITU-T G.826

Series G: Transmission Systems and Media, Digital Systems and Networks

Digital transmission systems Digital networks Quality and availabilitytargets

Error performance parameters and objectives for international, constant bitrate digital paths at or above the primary rate


14/136




3. DOCUMENT ORGANISATION

3.1. FAMILIES OF COUNTERS

The counters specified in the document are grouped into families of counters. A familyof counter is attached to a given UMTS feature (e.g. Hard hand-over where are puttogether counters allowing to report hard hand-over performances) or to aPerformance Management purpose (e.g. Traffic where are put together countersrelated to Traffic observation).

Each family is described in a separate chapter.

3.2. WORKING ASSUMPTIONS

3.2.1 WORDING

The wording counter and measurement are equally used in this document foridentifying the same concept.

Usually, NORTEL prefers to use the term counter to distinguish a counter from a(radio) measurement. A counter is periodically elaborated on periods expressed inminutes or hours, e.g. 30 mn, while a measurement is elaborated on periodsexpressed in milliseconds, e.g. 500 ms.

3GPP Performance Management specifications preferably considers measurements.When the context refers to 3GPP specifications measurement is used, whilecounter is used is more NORTEL specific part, but both wordings are equivalent.

3.2.2 SPECIFIED COUNTERS ARE USER AVAILABLE COUNTERSON THE OMC GUI

Specified counters are user available counters, periodically reportable on the OMCGUI and directly derived from the raw Network elements counters.

Remark:

In this document are not specified the metrics provided by the optional post-

processing application PMO.The here specified counters are not exactly those provided by the Network Elements.Network elements as RNC-CN and iBTS provide counters of different types called:

- cumulative counters

- value counters

- load counters.

Cumulative counter

A cumulative counter is a CC type counter as identified in the 3GPP TS 32.104(document [A1]). It is incremented by 1, each time the counted event occurs.

One NE cumulative counter provides one counter at the OMC GUI level.

An example is the counter Number of established calls which is incremented by 1each time a call establishment occurs.


15/136




Value counter

A value counter is elaborated according the mechanism defined by the 3GPP TS32.104 (document [A1]), to implement a DER type measurement. It is elaborated

using all pertinent events, i.e. one event every one event. The value counter isincremented by a value attached to the event itself.

An example is the counter Occupation of a subscriber line which is incremented bythe duration of the call, each time a call is released.

The NORTEL value counter provides not only the cumulated value whichcorresponds to the 3GPP DER type measurement. It provides additionally:

- the number of events

- the minimum value added

- the maximum value added.

In the upper example, the considered Network Element value counter allows to

provide values on the GUI, for the three following counters, at the end of eachgranularity period:

- the total occupation time of the subscriber line during the period

- the mean duration of a call in the period

which is obtained by dividing the cumulated value by the number of events

- the number of call releases in the period

- the duration of the shortest call in the period

- the duration of the longest call in the period

Load counter

A load counter is elaborated according the mechanism defined by the 3GPP TS32.104 (document [A1]), to implement a SI type measurement. It is elaborated usingsampling events periodically generated. The load counter is incremented by a valuesampled on the sampling event occurence .

An example is the counter Number of calls established on a subscriber end switchwhich is incremented by the number of established calls measured on each samplingevent.

The NORTEL load counter provides:

- the cumulated value

- the number of sampling events

- the minimum sampled value

- the maximum sampled value.

In the upper example, the considered Network Element load counter allows to providevalues on the GUI, for the three following counters, at the end of each granularityperiod:

- the mean number of established calls during the granularity period bydividing the cumulated value by the number of sampling events; thisprovides the 3GPP SI type measurement

- the minimum number of established calls during the granularity period

- the maximum number of established calls during the granularity period.


16/136




NETWORK ELEMENT COUNTER COUNTERS PRESENTED ON THEOMC GUI

CUMULATIVEcounter

Number of events Number of events

CC type counter

Cumulated value (1) Cumulated value

DER type counter

Number of events (1) Number of events

Mean value =Cumulated value / Number of events

Minimum value(attached to an event)

Minimum value

VALUEcounter

Maximum value(attached to an event)

Maximum value

Cumulated value (1) Cumulated value

Number of samplings (1)

Mean value =Cumulated value / Number of events

SI type counter

Minimum value(obtained by a sampling)

Minimum value

LOADcounter

Maximum value(obtained by a sampling) Maximum value

(1) There is no mean value field in the NE-OMC interface. However The NE mayreport directly the mean value over the observation period in the cumulatedvalue field. In this case, the Number of Events/Number of Sampling field isset to 1 and the Cumulated value and the Mean value in XML results file (onthe interface-N) are the same and Number of Events is 1.

Remark

NORTEL UTRAN do not implement, in a general way, GAUGE typemeasurements. To provide the current value of a measurement by

incrementing it by one when a positive event occurs and by decrementing itby one when a negative event occurs, may lead to some shifts if an event ismissed.

For instance, a GAUGE type Number of calls established on a subscriberend switch may be implemented by incrementing it each time a subscribercall is established and decremented each time a subscriber call is released.

The problem is there is a permanent shift, making the counter value to befalse, during successive granularity periods if an event is lost.


17/136




3.2.3 COUNTERS ARE SPECIFIED ACCORDING A COUNTERDEFINITION TEMPLATE

The counters are specified according the Measurement definition template defined inthe 3GPP specification [A1].

Below is the related extract of document [A1] (written in italics) :

Following is the template used to describe the measurements.

C.x.y. Measurement Name (section header)

This is a descriptive name of the measurement type that is specified as clause C.x.y of thepresent document.

a) Description

This section contains an explanation of the measurement operation;

b) Collection Method

This section contains the form in which this measurement data is obtained:

- CC (Cumulative Counter);

- GAUGE (dynamic variable), used when data being measured can vary up or down duringthe period of measurement;

- DER (Discrete Event Registration), when data related to a particular event are capturedevery n

thevent is registered, where n can be 1 or larger;

- SI (Status Inspection).

c) Condition

This section contains the condition, which causes the measurement result data to beupdated;This will be defined by identifying protocol related trigger events for starting and stoppingmeasurement processes, or updating the current measurement result value. Where it is notpossible to give a precise condition, then the conditional circumstances leading to the updateare stated.

d) Measurement Result(measured value(s), Units)

This section contains a description of expected result value(s) (e.g. a single integer value).

e) Measurement Type

This section contains a short form of the measurement name specified in the header, whichis used to identify the measurement type in the result files;

f) Measurement Object Instance

The measObjInstId field identifies the measured object class and its instance, e.g. trunk1means object class is trunk and instance #1 is being measured. The object class andinstance values used for this purpose shall be in accordance with 3GPP TS 32.106 [3], i.e.the NE/resource object model (defined in the Basic CM IRP Information Model - 3GPP TS32.106-5) and naming conventions (defined in the Name Convention for Managed Objects -

3GPP TS 32.106-8). This parameter, if applicable, shall be provided in the measurementjob.


18/136




g) Switching Technology

This section contains the Switching domain(s) this measurement is applicable to i.e. CircuitSwitched and/or Packet Switched.

Two counter specification items are added to the seven items a), b), c), d), e), f), g) consideredby the 3GPP. They are:

h) 3GPP compliance

This section states on the compliance of the NORTEL measurement with the 3GPPspecification.

If the NORTEL implementation is fully compliant with the 3GPP specification, then thestatement is 3GPP specified counter.

If the counter is not considered by the 3GPP, then the statement is NORTEL specifiedcounter.

If the NORTEL implementation is not fully compliant with the 3GPP specification, the sectionexplains how the counter is not fully compliant and the reason why.

Remark:

Currently the only 3GPP specification providing a list of recommended UMTS counters e is TS

32.403 (referred as document [A3]), but it is a Release 4 document to apply to NORTELUMTS V3 implementation.

Nevertheless, the currently NORTEL provided counters are matched against this TS in order toshow how much they are in-line with the current 3GPP SA5 work, even if this work is notcompleted yet..

The NORTEL internal number of the counter is provided.

The software version in which the counter had been introduced is provided. If the counter definition hadbeen modified in a subsequent version, then only the version in which the current counter specificationhad been introduced is provided.

The only considered versions are the last software deliveries of a new software drop, a software dropproviding a consistent set of new features and the related new services.

Considered versions are therefore:

- UA01.2b (V 1.2b)

- UA02.0c (V 2.0c)

- UA02.0e (V 2.0e)

- UA02.1 (V 2.1)

i) comments

This optional section provides additional information when necessary.

It may for instance, contain message flows when counters are attached to protocolmessages.

Remark 1:

If more than one value is provided in the counter specification item d) measurement result,then the measurement is screened according a criteria, e.g. a number of call releases may bescreened according the call release causes.

The number of call releases related to a given cause may be considered as a sub-counter.

In such a case, the measurement result specification item includes a screening paragraphspecifying the various sub-counter with their # with their meaning.


19/136




For consistency purpose, the wording Screening = NO is mentioned for counters providingonly one value.

Remark 2:

The measurement result item in the counter definition template may provides a screening of

some counters, i.e. the counter is breakdown into sub-counters. An example is a call dropcounter which is breakdown into sub-counters, each one providing the number of call drops fora given call drop reason.

In the current document version , the list of sub-counters attached to each screened counter isprovided for information and may be subject for further modifications.


20/136




4. NBAP RADIO-LINK MANAGEMENT

4.1. NUMBER OF SUCCESSFUL NBAP RADIO-LINK SETUPS

A. This measurement provides the number of radio-links successfully setup on a NBAP point of view,screened by Downlink Access Stratum configuration.

B. CC

C. Receipt of a RADIO LINK SETUP RESPONSE or RADIO LINK SETUP FAILURE NBAPmessage sent by Node B to the Controlling RNC in response to a RADIO LINK SETUP REQUESTmessage.

The measurement considers each Radio Link mentioned as set-up in the RADIO LINK SETUPRESPONSE or RADIO LINK SETUP FAILURE NBAP message.

D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1).

Screening:

Sub-counter # i ----> Downlink Access Stratum configuration # i for i = 0 to 10

E. VS.RadioLinkSetupSuccess.DL stratum conf 0

VS.RadioLinkSetupSuccess.DL stratum conf 1










F. FDDCell

G. Valid for circuit switched and packet switched traffic

H. NORTEL specified counter

NORTEL # 0001

Current counter specification introduced in V 2.0c


21/136




I. Message flow

CRNC Node B

RADIO LINK SETUP REQUEST

RADIO LINK SETUP RESPONSE

Radio Link Setup procedure: Successful Operation

4.2. NUMBER OF FAILED NBAP RADIO-LINK SETUPS

A. This measurement provides the number of radio links failed in setup on a NBAP point of view,screened by detecting event.

B. CC

C. This measurement is based on two different events:

1) Receipt of a NBAP RADIO LINK SETUP FAILURE message sent by Node B to theControlling RNC in response to a RADIO LINK SETUP REQUEST message.

The measurement considers each Radio Link referred as failed in the NBAP RADIOLINK SETUP FAILURE message.

2) Time-out expired without reception of a RADIO LINK SETUP RESPONSE messageor RADIO LINK SETUP FAILURE message.

The measurement considers each Radio Link required to set-up in the NBAP RADIOLINK SETUP REQUEST message.

D. Two integer values: one for each above event.

Screening:

Sub-counter # 0 ----> RADIO LINK SETUP FAILURE reception

Sub-counter # 1 ----> Time-out

E. VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure

VS.RadioLinkSetupUnsuccess.Timeout

F. FDDCell



NORTEL # 0002


I. Message flow


22/136




CRNC Node B

RADIO LINK SETUP REQUEST

RADIO LINK SETUP FAILURE

Radio Link Setup procedure: Unsuccessful Operation

4.3. NUMBER OF SUCCESSFUL NBAP RADIO-LINK ADDITIONS

A. This measurement provides the number of radio-links successfully added on a NBAP point ofview, screened by Downlink Access Stratum configuration.

B. CC

C. Receipt of a RADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION FAILURENBAP message sent by Node B to the Controlling RNC in response to a RADIO LINK SETUPREQUEST message.

The measurement considers each Radio Link mentioned as added in the RADIO LINKADDITION RESPONSE or RADIO LINK ADDITION FAILURE NBAP message.


Screening:


E. VS.RadioLinkAdditionSuccess.DL stratum conf 0

VS.RadioLinkAdditionSuccess.DL stratum conf 1










F. FDDCell


23/136






NORTEL # 0003


I. Message flow

CRNC Node B

RADIO LINK ADDITION REQUEST

RADIO LINK ADDITION RESPONSE

Radio Link Addition procedure: Successful Operation

4.4. NUMBER OF FAILED NBAP RADIO-LINK ADDITIONS

A. This measurement provides the number of radio links failed in addition on a NBAP point deview.

B. CC


1) Receipt of a NBAP RADIO LINK ADDITION FAILURE message sent by Node B tothe Controlling RNC in response to a RADIO LINK ADDITION REQUESTmessage.

The measurement considers each Radio Link referred as failed in the NBAPRADIO LINK ADDITION FAILURE message.

2) Time-out expired without reception of a RADIO LINK ADDITION RESPONSEmessage or a RADIO LINK ADDITION FAILURE message.

The measurement considers each Radio Link required to addition in the NBAP

RADIO LINK ADDITION REQUEST message.

D. Two integer values: one for each above event.

Screening:

Sub-counter # 0 ----> RADIO LINK ADDITION FAILURE reception


E. VS.RadioLinkAdditionUnsuccess.RadioLinkAdditionFailure

VS.RadioLinkAdditionUnsuccess.Timeout

F. FDDCell



24/136





NORTEL # 0004


I. Message flow

CRNC Node B

RADIO LINK ADDITION REQUEST

RADIO LINK ADDITION FAILURE

Radio Link Addition procedure: Unsuccessful Operation

4.5. NUMBER OF SUCCESSFUL NBAP RADIO-LINK DELETIONS

A. This measurement provides the number of radio-links successfully deleted on a NBAP point ofview.

B. CC

C. Receipt of a NBAP RADIO LINK DELETION RESPONSE message sent by Node B to theServing RNC in response to a RADIO LINK DELETION REQUEST.

The measurement considers each Radio Link referred in the NBAP RADIO LINK DELETIONRESPONSE message

D. A single integer value.

Screening = NO

E. VS.RadioLinkDeletionSuccess

F. FDDCell



NORTEL # 0005


I. Message flow


25/136




CRNC Node B

RADIO LINK DELETION REQUEST

RADIO LINK DELETION RESPONSE

Radio Link Deletion procedure: Successful Operation

4.6. NUMBER OF FAILED NBAP RADIO-LINK DELETIONS

A. This measurement provides the number of radio links failed in deletion on a NBAP point deview.

B. CC

C. Time-out expired without reception of a RADIO LINK DELETION RESPONSE


Screening = NO

E. VS.RadioLinkDeletionUnsuccess

F. FDDCell



NORTEL # 0006


I. Message flow

4.7. NUMBER OF SUCCESSFUL NBAP RADIO-LINKRECONFIGURATION PREPARATIONS

A. This measurement provides the number of radio-links successfully prepared for reconfiguration,screened by Downlink Access Stratum configuration.

B. CC

C. Reception of a valid NBAP RADIO LINK RECONFIGURATION READY message.

The measurement considers each Radio Link referred in the NBAP RADIO LINKRECONFIGURATION READY message.


Screening:



26/136




E. VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 0

VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 1










F. FDDCell



NORTEL # 0007

Counter introduced in V 2.0c

I. Message flow

CRNC Node B

RADIO LINK RECONFIGURATION PREPARE

RADIO LINK RECONFIGURATION READY

Synchronised Radio Link Reconfiguration Preparation procedure, Successful Operation

4.8. NUMBER OF FAILED NBAP RADIO-LINK RECONFIGURATIONPREPARATIONS

A. This measurement provides the number of radio links failed in reconfiguration preparation.

B. CC

C. This measurement is based on four different events:

1) Receipt of a NBAP RADIO LINK RECONFIGURATION FAILURE message sent byNode B to the Controlling RNC in response to a RADIO LINK RECONFIGURATIONPREPARE message.


27/136




2) No reception of RADIO LINK RECONFIGURATION READY message before a time-out

3) RRM refusal (e.g. no power allocation, no code allocation)

4) I-Node refusal (e.g. no CID allocation)D. Four integer values: one for each above event

Screening:

Sub-counter # 0 ----> RADIO LINK RECONFIGURATION FAILURE reception


Sub-counter # 2 ----> RRM refusal

Sub-counter # 3 ----> I-Node refusal

E. VS.RadioLinkReconfigPrepareUnsuccess.RadioLinkReconfigurationFailure

VS.RadioLinkReconfigPrepareUnsuccess.TimeoutNbap

VS.RadioLinkReconfigPrepareUnsuccess.RrmRefusal

VS.RadioLinkReconfigPrepareUnsuccess.INodeRefusal

F. FDDCell



NORTEL # 0008


I. Message flow

CRNC Node B

RADIO LINK RECONFIGURATION PREPARE

RADIO LINK RECONFIGURATION FAILURE

Synchronised Radio Link Reconfiguration Preparation procedure, Unsuccessful Operation

4.9. NUMBER OF NBAP RADIO-LINK RECONFIGURATIONCANCELS

A. This measurement provides the number of NBAP RADIO LINK RECONFIGURATIONCANCEL messages.

B. CC

C. Emission of a NBAP RADIO LINK RECONFIGURATION CANCEL message by the RNC to a

Node B.



28/136




Screening:


E. VS.RadioLinkReconfigCancelSuccess.DL stratum conf 0

VS.RadioLinkReconfigCancelSuccess.DL stratum conf 1










F. FDDCell



NORTEL # 0009


I. Message flow

CRNC Node B

RADIO LINK RECONFIGURATION CANCEL

Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation

4.10. NUMBER OF NBAP RADIO-LINK RECONFIGURATIONCOMMITS

A. This measurement provides the number of NBAP RADIO LINK RECONFIGURATIONCOMMIT messages.

B. CC

C. Emission of a NBAP RADIO LINK RECONFIGURATION COMMIT message by the RNC to aNode B


Screening:


29/136





F. VS.RadioLinkReconfigCommitSuccess.DL stratum conf 0

VS.RadioLinkReconfigCommitSuccess.DL stratum conf 1










F. FDDCell



NORTEL # 0010


I. Message flow

CRNC Node B

RADIO LINK RECONFIGURATION COMMIT

Synchronised Radio Link Reconfiguration Commit procedure, Successful Operation

4.11. NUMBER OF NBAP RADIO-LINKS

4.11.1 AVERAGE NUMBER OF NBAP RADIO-LINKS

A. This measurement provides the average number of NBAP radio-links established in a cellduring a granularity period.

B. DER

NORTEL VAL type counter

C. A current counter is incremented by 1 on each radio-link addition on the NBAP. The counter isdecremented by 1 on each radio-link deletion on the NBAP.

The averaged value is assessed at the end of the granularity period.


30/136





Screening = NO

E. VS.RadioLinkEstablishedPerCellVal.Avg

F. FDDCell



NORTEL # 0012


4.11.2 MINIMUM NUMBER OF NBAP RADIO-LINKS

A. This measurement provides the minimum number of NBAP radio-links established in a cellduring a granularity period.

B. DER


C. A current counter is incremented by 1 on each radio-link addition on the NBAP. The counter isdecremented by 1 on each radio-link deletion on the NBAP.

The minimum value is assessed at each modification of the current counter.


Screening = NO

E. VS.RadioLinkEstablishedPerCellVal.Min

F. FDDCell



NORTEL # 0012


4.11.3 MAXIMUM NUMBER OF NBAP RADIO-LINKS

A. This measurement provides the maximum number of NBAP radio-links established in a cellduring a granularity period.

B. DER


C. A current counter is incremented by 1 on each radio-link addition on the NBAP. The counter is

decremented by 1 on each radio-link deletion on the NBAP.

The maximum value is assessed at each modification of the current counter.


31/136





Screening = NO

E. VS.RadioLinkEstablishedPerCellVal.Max

F. FDDCell



NORTEL # 0012


4.12. NUMBER OF DROPPED CALLS ON LAST RADIO-LINK

RELEASE

A. This measurement provides the number of dropped calls on last radio-link release, for eachcell controlled by the RNC.

B. CC

C. Radio-link release which force the communication to be lost.

The measurement may be incremented for more than one cell if more than one radio-link failsimultaneously and make the call to be dropped.


Screening = NO

E. VS.RadioLinkDroppedLastRadioLink

F. FDDCell



NORTEL # 0013

Counter introduced in V 2.0e


32/136




5. HARD HAND-OVERS

5.1. NUMBER OF INTER-RAT HANDOVER FROM UTRANCOMMANDS PER CELL

A. This measurement provides the number of RRC HANDOVER FROM UTRAN COMMANDmessages emitted by a RNC, for each cell controlled by the RNC and acting as a referencecell

i.e. an involved UE in the procedure is served by a RNC which is the controlling RNC of itsreference cell.

B. CC

C. Emission of a RRC HANDOVER FROM UTRAN COMMAND by a RRC to a UE having itsreference controlled by the considered RNC

D. A single integer value per reason.

Screening:

Sub-counter # 0 ----> Rescue CS

Sub-counter # 1 ----> Service CS

E. VS.RrcHoFromUtranCommand.RescueCS

VS.RrcHoFromUtranCommand.ServiceCS

F. FDDCell

Related to the reference cell

G. Valid for circuit switched traffic


NORTEL # 0101


I. Message flow

UE UTRAN

HANDOVER FROM UTRAN COMMAND

Inter-RAT handover from UTRAN, successful case


33/136




5.2. NUMBER OF INTER-RAT HANDOVER FROM UTRANCOMMANDS PER RNC

A. This measurement provides the number of RRC HANDOVER FROM UTRAN COMMAND

messages emitted by a RNC, for each neighboring RNC.

Neighboring RNCs act as Drift RNCs controlling the reference cell of procedure involved UEs.

i.e. an involved UE in the procedure is served by a RNC which is not the controlling RNC of itsreference cell.

B. CC

C. Emission of a RRC HANDOVER FROM UTRAN COMMAND by a RRC to a UE having itsreference cell controlled by another RNC


Screening:



E. VS.RrcHoFromUtranCommandNeighbRnc.RescueCS

VS.RrcHoFromUtranCommandNeighbRnc.ServiceCS

F. Neighboring RNC



NORTEL # 0102


I. Message flow

See 5.1

5.3. NUMBER OF INTER-RAT HANDOVER FROM UTRANFAILURES PER CELL

A. This measurement provides the number of RRC HANDOVER FROM UTRAN FAILUREmessages, for each cell controlled by the RNC and acting as a reference cell


B. CC

C. Reception of a RRC HANDOVER FROM UTRAN FAILURE message by a RRC from a UEhaving its reference controlled by the considered RNC


Screening:



34/136





E. VS.RrcHoFromUtranFailure.RescueCS

VS.RrcHoFromUtranFailure.ServiceCS

F. FDDCell




NORTEL # 0103


I. Message flow

UE UTRAN

HANDOVER FROM UTRAN COMMAND

HANDOVER FROM UTRAN FAILURE

Inter-RAT handover from UTRAN, failure case

5.4. NUMBER OF FAILED INTER-RAT HANDOVER FROM UTRANPER RNC

A. This measurement provides the number of RRC HANDOVER FROM UTRAN COMMANDmessages received by a RNC, for each neighboring RNC.

Neighboring RNCs act as Drift RNCs controlling the reference cell of procedure involved UEs


B. CC

C. Reception of a RRC HANDOVER FROM UTRAN FAILURE message by a RRC from a UEhaving its reference cell controlled by another RNC


Screening:



E. VS.RrcHoFromUtranFailureNeighbRnc.RescueCS

VS.RrcHoFromUtranFailureNeighbRnc.ServiceCS


35/136




F. Neighboring RNC



NORTEL # 0104


I. Message flow

See 5.3

5.5. NUMBER OF RRC CELL CHANGE ORDER FROM UTRANPER CELL

A. This measurement provides the number of RRC CELL CHANGE ORDER FROM UTRAN

messages sent by a RNC, for each cell controlled by the RNC and acting as a reference cell


B. CC

C. Emission of a RRC CELL CHANGE ORDER FROM UTRAN message from the RNC to theUE.

The event is only considered when the UE has a reference cell under the control of the RNC incharge of the measurement.


Screening = NO

E. IRATHO.AttOutPSUTRAN

F. FDDCell


G. Valid for packet switched traffic

H. 3GPP specified counter

(3GPP specification is applied for the cells which are controlled by the SRNC)

NORTEL # 0105


I. Message flow

UE UTRAN

CELL CHANGE ORDER FROM UTRAN

InterRAT cell change order from UTRAN


36/136




5.6. NUMBER OF RRC CELL CHANGE ORDER FROM UTRANPER RNC

A. This measurement provides the number of RRC CELL CHANGE ORDER FROM UTRANmessages sent by a RNC, for each neighboring RNC. Neighboring RNCs act as Drift RNCscontrolling the reference cell of procedure involved UEs.


B. CC

C. Emission of a RRC CELL CHANGE ORDER FROM UTRAN message by the RNC to the UE.

The event is only considered when the UE has a reference cell outside the control of the RNC

in charge of the measurement..


Screening = NO

E. VS.RrcCellChangeOrderNeighbRnc.RescuePs

F. Neighboring RNC



NORTEL # 0106


I. Message flow

See 5.5

5.7. NUMBER OF CELL CHANGE ORDER FROM UTRAN FAILUREPER CELL

A. This measurement provides the number of RRC CELL CHANGE ORDER FROM UTRANFAILURE messages received by a RNC, for each cell controlled by the RNC and acting as a

reference cell


B. CC

C. Reception of a RRC CELL CHANGE ORDER FROM UTRAN FAILURE message sent by anUE to the Serving RNC in response to a RRC CELL CHANGE ORDER FROM UTRANmessage.

The event is only considered when the UE has a reference cell under the control of the RNCin charge of the measurement.


Screening = NO


37/136




E. IRATHO.FailOutPSUTRAN

F. FDDCell




(3GPP specification is applied for the cells which are controlled by the SRNC)

NORTEL # 0107


I. Message flow

UE UTRAN

CELL CHANGE ORDER FROM UTRAN

CELL CHANGE ORDER FROM UTRAN FAILURE

Inter-RAT cell change order from UTRAN, failure case

5.8. NUMBER OF RRC CELL CHANGE ORDER FROM UTRANFAILURE PER RNC

A. This measurement provides the number of RRC CELL CHANGE ORDER FROM UTRANFAILURE messages received by a RNC, for each neighboring RNC.

Neighboring RNCs act as Drift RNCs controlling the reference cell of procedure involved UEsi.e. an involved UE in the procedure is served by a RNC which is not the controlling RNC of itsreference cell.

B. CC

C. Reception of a RRC CELL CHANGE ORDER FROM UTRAN FAILURE message sent by UEto the Serving RNC in response to a RRC CELL CHANGE ORDER FROM UTRAN message.



Screening = NO


38/136




E. VS.RrcCellChangeOrderFailureNeighbRnc.RescuePs

F. Neighboring RNC



NORTEL # 0108


I. Message flow

See 5.7

5.9. NUMBER OF 3G TO 2G HANDOVER REQUESTS PER CELL

A. This measurement provides the number of RRM decisions for a 3G TO 2G handoverperformed by a RNC, screened by reference cell from which the UEs have left the 3GNetwork, when these cells are controlled by the considered RNC.

This measurement considers both CS and PS handovers.

B. CC

C. RRM decision for a UE handover from 3G to 2G network.


D. One single integer value per HO reason.

Screening:


Sub-counter # 1 ----> Rescue PS


E. VS.3gto2gHoDetectionFromFddcell.RescueCs

VS.3gto2gHoDetectionFromFddcell.RescuePs

VS.3gto2gHoDetectionFromFddcell.ServiceCS

F. FDDCell




NORTEL # 0109



39/136




5.10. NUMBER OF 3G TO 2G HANDOVER REQUESTS PER RNC

A. This measurement provides the number of RRM decisions for a 3G TO 2G handoverperformed by a RNC, screened by neighboring RNC grouping reference cells from which theUEs have left the 3G Network.

This measurement considers both CS and PS handovers.

B. CC

C. RRM decision for a UE handover from 3G to 2G network.

The event is only considered when the UE has a reference cell under the control of the RNCwhich is not the RNC in charge of the measurement.

D. One single integer value per HO reason.

Screening:


Sub-counter # 1 ----> Rescue PS


E. VS.3gto2gHoDetectionFromFddcellNeighbRnc.RescueCs

VS.3gto2gHoDetectionFromFddcellNeighbRnc.RescuePs

VS.3gto2gHoDetectionFromFddcellNeighbRnc.ServiceCS

F. Neighboring RNC



NORTEL # 0110



40/136




6. RRC RADIO-LINK MANAGEMENT

6.1. NUMBER OF SUCCESSFUL RRC ACTIVE SET UPDATES PERCELL

A. This measurement provides the number of successful RRC ACTIVE SET UPDATEprocedures managed by a RNC. This counter is updated on the cells that are added to orremoved from the active set.

B. CC

C. Receipt of a RRC ACTIVE SET UPDATE COMPLETE message sent by UE to the ServingRNC in response to an ACTIVE SET UPDATE message.

D. One integer value for addition to active set, one integer value for removal from active set.

E. SHO.SuccRLAddUESide

SHO.SuccRLDelUESide

F. FDDCell


H. 3GPP counter

NORTEL # 0401


I. Message flow

UE UTRAN

ACTIVE SET UPDATE

ACTIVE SET UPDATE COMPLETE

Active Set Update procedure, successful case


41/136




6.2. NUMBER OF SUCCESSFUL RRC ACTIVE SET UPDATES PERRNC

A. This measurement provides the number of successful RRC ACTIVE SET UPDATE

procedures managed by a RNC, for each neighboring RNC.

The counter is incremented as many times as there are cells in a given neighboring RNCwhich are added / removed from active set.

B. CC

C. Receipt of a RRC ACTIVE SET UPDATE COMPLETE message sent by UE to the ServingRNC in response to an ACTIVE SET UPDATE message.

D. One integer value for addition to active set, one integer value for removal from active set.

E. VS.RrcActiveSetUpdateSuccessNeighbRnc.radiolinkAdditionOnCell

VS.RrcActiveSetUpdateSuccessNeighbRnc.radiolinkActiveRemovalOnCell

F. NeighboringRNC



NORTEL # 0406


I. Message flow

See 6.1

6.3. NUMBER OF FAILED RRC ACTIVE SET UPDATES PER CELL

A. This measurement provides the number of failed RRC ACTIVE SET UPDATE proceduresmanaged by a RNC, for each cell controlled by the RNC.

During such a procedure, the measurement attached to a given cell is incremented if the cellbelongs to the active set of the involved UE.

B. CC

C. This measurement is based on two different events:.

1) Receipt of a RRC ACTIVE SET UPDATE FAILURE message sent by UE to theServing RNC in response to a RRC ACTIVE SET UPDATE message.

2) Time-out expired without reception of a ACTIVE SET UPDATE COMPLETE messageor a ACTIVE SET UPDATE FAILURE message.

The events are only considered for cells belonging to the active set which are under thecontrol of the RNC in charge of the measurement.

D. A single integer value for each cause.


42/136




Screening:

Sub-counter # 0 ----> RRC ACTIVE SET UPDATE FAILURE reception


E. SHO.FailRLAddUESid.RrcActiveSetUpdateFailure

SHO.FailRLAddUESid.Timeout

F. FDDCell


H. 3GPP counter

NORTEL # 0402


I. Message flow

UE UTRAN

ACTIVE SET UPDATE

ACTIVE SET UPDATE FAILURE

Active Set Update procedure, failure case

6.4. NUMBER OF FAILED RRC ACTIVE SET UPDATES PER RNC

A. This measurement provides the number of failed RRC ACTIVE SET UPDATE proceduresmanaged by a RNC, for each neighboring RNC.

During such a procedure, the measurement attached to a given neighboring RNC is

incremented as many times as there are cells it controls which are concerned by theprocedure failure.

B. CC


1) Receipt of a RRC ACTIVE SET UPDATE FAILURE message sent by UE to the Serving RNCin response to a RRC ACTIVE SET UPDATE message.

2) Time-out expired without reception of a ACTIVE SET UPDATE COMPLETE message or aACTIVE SET UPDATE FAILURE message.

The events are considered for cells belonging to the active set which are outside the control ofthe RNC in charge of the measurement.


43/136




D. A single integer value for each cause.

Screening:

Sub-counter # 0 ----> RRC ACTIVE SET UPDATE FAILURE reception


E. VS.RrcActiveSetUpdateUnsuccessNeighbRnc.RrcActiveSetUpdateFailure

VS.RrcActiveSetUpdateUnsuccessNeighbRnc.Timeout

F. NeighboringRNC



NORTEL # 0407


I. Message flow

See 6.3


44/136




7. RRC CONNECTION

7.1. NUMBER OF RRC CONNECTION REQUESTS

A. This measurement provides the number of RRC connection requests screened byestablishment cause.

B. CC

C. Reception by the RNC of a RRC CONNECTION REQUEST message.

D. An integer value for each establishment cause

Screening:

Sub-counter # i ----> Establishment cause # i as in TS 25.331 (c.f. Annexe 2)

E. RRC.AttConnEstab.

F. FDDCell.

G. Valid for circuit switched and packet switched traffic traffic.


NORTEL # 0409

Counter introduced in V 2.0e

I. Message flow

UE UTRAN

RRC CONNECTION REQUEST

RRC CONNECTION SETUP

RRC CONNECTION SETUP COMPLETE

RRC Connection Establishment, network accepts RRC connection

7.2. NUMBER OF SUCCESSFUL RRC CONNECTIONESTABLISHMENTS

A. This measurement provides the number of successful RRC connection establishmentsscreened by establishment cause.


45/136




B. CC

C. Reception by the RNC of a RRC CONNECTION SETUP COMPLETE message following aRRC connection establishment attempt.

A RRC connection establishment attempt is considered on the reception by the RNC of a RRCCONNECTION REQUEST message.

D. An integer value for each establishment cause

Screening:

Sub-counter # i ----> Establishment cause # i as in TS 25.331 (c.f. Annexe 2)

E. RRC.SuccConnEstab.

F. FDDCell.

G. Valid for circuit switched and packet switched traffic traffic.


NORTEL # 0403

Counter introduced in V 1.2.b ; screening criteria later modified

I. Message flow

See 7.1

7.3. NUMBER OF RRC CONNECTION ESTABLISHMENTFAILURES

A. This measurement provides the number of RRC connection establishment failures screenedby establishment failure cause.

B. CC

C. The measurement counts the number of RRC connection establishment attempts which havenot evolved into a RRC connection establishment.

A RRC connection establishment attempt is considered on the reception by the RNC of a RRCCONNECTION REQUEST message.

A RRC connection establishment is considered on the reception by the RNC of a RRCCONNECTION SETUP COMPLETE message following a RRC connection attempt.

D. An integer value for each connection establishment failure cause.

Screening:


Sub-counter # 1 ----> Unavailable downlink code resources

Sub-counter # 2 ----> Unavailable downlink power resources

Sub-counter # 3 ----> Unspecified

Sub-counter # 4 ----> RSSI


46/136




E. RRC.FailConnEstab.

F. FDDCell

G. Valid for circuit switched and packet switched traffic.


NORTEL provides a wider screening as the one requested by 3GPP (which is reduced toCongestion + Time-out + Unspecified).

NORTEL # 0404

Counter introduced in V 1.2.b ; screening criteria later modified

I. Message flow

UE UTRAN

RRC CONN

umts access counters list umt sys dd 75.v2.13

Documents