Umts Access Counters List Umt Sys DD 75.v2.13

UMTS Access counters list
Document number: Document issue: Document status: Date: UMT/SYS/DD/0075 02.13 / EN Standard 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 confidential and 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.
Nortel Networks confidential
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 2/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
Issue 02.01 / EN, Provisional Document update after: agreement on V2 RNC AN counter list as stated in internal document UMT/RNC/GES/0032 V .1.01 dated 02/Jul/2001 issue of internal document RNC Performance Management Spooling of Interface Node and Access Node counters and traces to the OMC in V2 version AA02 dated 04/Sep/2001 issue of Functional Note NodeB UTRAN counters Functional Note RFF 13479 UMT/BTS/DD/0345 dated 05/Jul/2001
28/Sept/2001
Issue 02.02 / EN, Provisional Document update after: follow-up meetings for clarification of the three above mentioned internal documents
12/Oct/2001
Issue 02.03 / EN, Provisional Document update after: review meeting held on Friday the 12th of October new releases of internal iRNC and iBTS documents on which is based the current document
18/Oct/2001
Issue 02.04 / EN, Draft Document update after: last comments Status reset to draft in order to be consistent with KIOSK procedure
22/Oct/2001
Issue 02.05 / EN, Draft Introduction of RNC and iBTS load management counters.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 3/136

Split of Radio bearer release success / unsuccess counters per controlled cell / per neighboring RNC. Screenings on failure causes for some counters related to radio-link management by RNSAP. 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 radiolink release Minor corrections and clarifications
19/Apr/2002
Alignment of counter names on counter names provided on the ADI export interface of the Performance Server. Each counter value provided by a screened counter is identified by its own counter name. A global numbering plane is used for UTRAN Access counters whichever is the related 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 All RRC radio-link management counters (c.f. 6) All RB related counters in chapter 9 RAB and RB management
Semantic modifications on the following counters:
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, then only the version in which the current counter specification had been introduced is provided. V 1.2.b V2 D2 V2 D4
The only considered versions are the software versions with a customer visibility i.e: -
Revision bars show modifications between V 02.06 and V 02.08 of the document
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 4/136
UMTS Access counters list 23/Aug/2002

Issue 02.09 / EN, Draft 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 new services. 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
Issue 02.10 / EN, Draft
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.0 causes. 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 on counters #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 the average value directly and sends it in the cumulative part of the counter and also set the number of events to 1.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 5/136
CONTENTS
1. INTRODUCTION..........................................................................................................................12 1.1. 1.2. 1.3. 2. OBJECT ..................................................................................................................................12 SCOPE OF THIS DOCUMENT .....................................................................................................12 AUDIENCE FOR THIS DOCUMENT ..............................................................................................12
RELATED DOCUMENTS ............................................................................................................12 2.1. 2.2. APPLICABLE DOCUMENTS ........................................................................................................12 REFERENCE DOCUMENTS ........................................................................................................13
3.
DOCUMENT ORGANISATION ...................................................................................................14 3.1. 3.2. FAMILIES OF COUNTERS ..........................................................................................................14 WORKING ASSUMPTIONS .........................................................................................................14 Wording .........................................................................................................................14 Specified counters are user available counters on the OMC GUI ................................14 Counters are specified according a Counter Definition Template ................................17
3.2.1 3.2.2 3.2.3 4.
NBAP RADIO-LINK MANAGEMENT..........................................................................................20 4.1. 4.2. 4.3. 4.4. 4.5. 4.6. 4.7. 4.8. 4.9. 4.10. 4.11. NUMBER OF SUCCESSFUL NBAP RADIO-LINK SETUPS ...............................................................20 NUMBER OF FAILED NBAP RADIO-LINK SETUPS ........................................................................21 NUMBER OF SUCCESSFUL NBAP RADIO-LINK ADDITIONS ...........................................................22 NUMBER OF FAILED NBAP RADIO-LINK ADDITIONS ....................................................................23 NUMBER OF SUCCESSFUL NBAP RADIO-LINK DELETIONS ..........................................................24 NUMBER OF FAILED NBAP RADIO-LINK DELETIONS ...................................................................25 NUMBER OF SUCCESSFUL NBAP RADIO-LINK RECONFIGURATION PREPARATIONS.......................25 NUMBER OF FAILED NBAP RADIO-LINK RECONFIGURATION PREPARATIONS ................................26 NUMBER OF NBAP RADIO-LINK RECONFIGURATION CANCELS ....................................................27 NUMBER OF NBAP RADIO-LINK RECONFIGURATION COMMITS ....................................................28
NUMBER OF NBAP RADIO-LINKS ..............................................................................................29
4.11.1 Average number of NBAP radio-links ...........................................................................29 4.11.2 Minimum number of NBAP radio-links ..........................................................................30 4.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. 5.2. 5.3. 5.4. 5.5. NUMBER OF INTER-RAT HANDOVER FROM UTRAN COMMANDS PER CELL .................................32 NUMBER OF INTER-RAT HANDOVER FROM UTRAN COMMANDS PER RNC.................................33 NUMBER OF INTER-RAT HANDOVER FROM UTRAN FAILURES PER CELL ....................................33 NUMBER OF FAILED INTER-RAT HANDOVER FROM UTRAN PER RNC........................................34 NUMBER OF RRC CELL CHANGE ORDER FROM UTRAN
PER CELL ...................................35
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 6/136

5.6. 5.7. 5.8. 5.9. 5.10. 6. NUMBER OF RRC CELL CHANGE ORDER FROM UTRAN NUMBER OF RRC CELL CHANGE ORDER FROM UTRAN
PER RNC ..................................36
NUMBER OF CELL CHANGE ORDER FROM UTRAN FAILURE PER CELL ...............................36
FAILURE PER RNC .....................37
NUMBER OF 3G TO 2G HANDOVER REQUESTS PER CELL ..........................................................38 NUMBER OF 3G TO 2G HANDOVER REQUESTS PER RNC .........................................................39
RRC RADIO-LINK MANAGEMENT ............................................................................................40 6.1. 6.2. 6.3. 6.4. NUMBER OF SUCCESSFUL RRC ACTIVE SET UPDATES PER CELL .........................................40 NUMBER OF SUCCESSFUL RRC ACTIVE SET UPDATES PER RNC ........................................41 NUMBER OF FAILED RRC ACTIVE SET UPDATES PER CELL ..................................................41 NUMBER OF FAILED RRC ACTIVE SET UPDATES PER RNC..................................................42
7.
RRC CONNECTION ....................................................................................................................44 7.1. 7.2. 7.3. 7.4. 7.5. NUMBER OF RRC CONNECTION REQUESTS ..............................................................................44 NUMBER OF SUCCESSFUL RRC CONNECTION ESTABLISHMENTS ................................................44 NUMBER OF RRC CONNECTION ESTABLISHMENT FAILURES .......................................................45 NUMBER OF RRC CONNECTION RELEASES PER CELL.............................................................46 NUMBER OF RRC CONNECTION RELEASES PER RNC..............................................................47
8.
IU INTERFACE ............................................................................................................................49 8.1. 8.2. 8.3. 8.4. 8.5. 8.6. NUMBER OF SUCCESSFUL SCCP CONNECTIONS AT IU INTERFACE .............................................49 NUMBER OF FAILED SCCP CONNECTIONS AT IU INTERFACE ......................................................49 NUMBER OF RELEASE REQUESTS ON IU CS .......................................................................50 NUMBER OF RELEASE REQUESTS ON IU PS .......................................................................51 NUMBER OF RELEASE COMMANDS ON IU CS......................................................................51 NUMBER OF RELEASE COMMANDS ON IU PS......................................................................52
9.
RAB AND RB MANAGEMENT ...................................................................................................54 9.1. 9.2. 9.3. 9.4. 9.5. 9.6. 9.7. 9.8. 9.9. 9.10. 9.11. 9.12. NUMBER OF SUCCESSFUL RAB ESTABLISHMENTS ....................................................................54 NUMBER OF FAILED RAB ESTABLISHMENTS ..............................................................................55 NUMBER OF SUCCESSFUL RAB RELEASES ...............................................................................56 NUMBER OF FAILED RAB RELEASES ........................................................................................57 NUMBER OF SUCCESSFUL RADIO-BEARER ESTABLISHMENTS PER CELL...................................57 NUMBER OF SUCCESSFUL RADIO-BEARER ESTABLISHMENTS PER RNC ....................................59 NUMBER OF REFUSED RADIO-BEARER ESTABLISHMENTS PER CELL ...........................................60 NUMBER OF REFUSED RADIO-BEARER ESTABLISHMENTS PER RNC...........................................60 NUMBER OF FAILED RADIO-BEARER ESTABLISHMENTS PER CELL ...............................................61 NUMBER OF FAILED RADIO-BEARER ESTABLISHMENTS PER RNC ..............................................62 NUMBER OF SUCCESSFUL RADIO-BEARER RELEASES PER CELL .................................................63 NUMBER OF SUCCESSFUL RADIO-BEARER RELEASES PER RNC ................................................64
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 7/136

9.13. 9.14. 9.15. 9.16. 9.17. 9.18. 10. NUMBER OF FAILED RADIO-BEARER RELEASES PER CELL ..........................................................65 NUMBER OF FAILED RADIO-BEARER RELEASES PER RNC..........................................................66 NUMBER OF SUCCESSFUL RADIO-BEARER RECONFIGURATIONS PER CELL ..................................67 NUMBER OF SUCCESSFUL RADIO-BEARER RECONFIGURATIONS PER RNC .................................68 NUMBER OF FAILED RADIO-BEARER RECONFIGURATIONS PER CELL ...........................................69 NUMBER OF FAILED RADIO-BEARER RECONFIGURATIONS PER RNC...........................................70
RNSAP RADIO-LINK MANAGEMENT .......................................................................................72 10.1. 10.2. 10.3. 10.4. 10.5. 10.6. 10.7. 10.8. 10.9. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK SETUPS ............................................................72 NUMBER OF FAILED RNSAP RADIO-LINK SETUPS .....................................................................73 NUMBER OF SUCCESSFUL RNSAP RADIO-LINK ADDITIONS ........................................................74 NUMBER OF FAILED RNSAP RADIO-LINK ADDITIONS .................................................................75 NUMBER OF SUCCESSFUL RNSAP RADIO-LINK DELETIONS .......................................................76 NUMBER OF SUCCESSFUL RNSAP RADIO-LINK RECONFIGURATION PREPARATIONS ....................77 NUMBER OF FAILED RNSAP RADIO-LINK RECONFIGURATION PREPARATIONS .............................78 NUMBER OF RNSAP RADIO-LINK RECONFIGURATION CANCELS .................................................78 NUMBER OF RNSAP RADIO-LINK RECONFIGURATION COMMITS .................................................79
11.
PAGING .......................................................................................................................................81 11.1. NUMBER OF RECEIVED PAGING REQUESTS ...............................................................................81
12.
POWER MANAGEMENT ............................................................................................................82 12.1. AVERAGE CELL POWER USED FOR SPEECH CALLS .....................................................................82 12.1.1 Average cell power used for speech calls.....................................................................82 12.1.2 Minimum cell power used for speech calls ...................................................................82 12.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.......................................................................83 12.2.2 Minimum cell power used for DATA calls ....................................................................83 12.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...............................................................................85 12.3.3 Maximum cell power used for signalling .......................................................................85 12.4. UPLINK RSSI ..........................................................................................................................86 12.4.1 12.4.2 12.4.3 Averaged uplink RSSI ...................................................................................................86 Minimum uplink RSSI....................................................................................................86 Maximum uplink RSSI...................................................................................................86
13.
QUALITY OF SERVICE...............................................................................................................88 13.1. 13.2. 13.3. 13.4. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 1 PER CELL ........................................................88 NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 1 PER RNC .......................................................89 NUMBER OF UNSUCCESSFUL DOWNSIZINGS STEP 1 PER CELL ................................................90 NUMBER OF UNSUCCESSFUL DOWNSIZINGS STEP 1 PER RNC..................................................91
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 8/136

13.5. 13.6. 13.7. 13.8. 13.9. 13.10. 13.11. 13.12. 13.13. 13.14. 14. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 2 PER CELL ........................................................92 NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 2 PER RNC .......................................................93 NUMBER OF SUCCESSFUL UPSIZINGS PER CELL ........................................................................93 NUMBER OF SUCCESSFUL UPSIZINGS PER RNC........................................................................94 NUMBER OF UNSUCCESSFUL UPSIZINGS PER CELL.................................................................95 NUMBER OF UNSUCCESSFUL UPSIZINGS PER RNC ..............................................................96 NUMBER OF SUCCESSFUL IRM SCHEDULING DOWNGRADINGS PER CELL.................................97 NUMBER OF FAILED IRM SCHEDULING DOWNGRADINGS PER CELL ..........................................98 NUMBER OF SUCCESSFUL IRM SCHEDULING DOWNGRADINGS PER RNC ................................99 NUMBER OF FAILED IRM SCHEDULING DOWNGRADINGS PER RNC ...................................... 100
USER PLANE TRAFFIC........................................................................................................... 102 14.1. 14.2. 14.3. 14.4. 14.5. 14.6. 14.7. 14.8. 14.9. 14.10. 14.11. 14.12. TOTAL COUNT OF UPLINK RLC PAYLOAD ON COMMON CHANNELS ........................................... 102 TOTAL COUNT OF DOWNLINK RLC PAYLOAD ON COMMON CHANNELS ...................................... 102 NUMBER OF UPLINK RLC PDUS ON COMMON CHANNELS ....................................................... 103 NUMBER OF DOWNLINK RLC PDUS ON COMMON CHANNELS .................................................. 103 NUMBER OF UPLINK RLC SDUS ON COMMON CHANNELS ....................................................... 104 NUMBER OF DOWNLINK RLC SDUS ON COMMON CHANNELS .................................................. 104 NUMBER OF DISCARDED RLC SDUS ON COMMON CHANNELS ................................................ 105 NUMBER OF RLC DUMMY PADDINGS ON COMMON CHANNELS ................................................. 105 NUMBER OF UPLINK MAC PDUS ON COMMON CHANNELS ...................................................... 106 NUMBER OF DOWNLINK MAC PDUS ON COMMON CHANNELS ............................................. 106 TOTAL COUNT OF UPLINK MAC PAYLOAD ON COMMON CHANNELS ....................................... 107 TOTAL COUNT OF DOWNLINK MAC PAYLOAD ON COMMON CHANNELS.................................. 107
15.
IUR INTERFACE....................................................................................................................... 108 15.1. 15.2. NUMBER OF SUCCESSFUL SCCP CONNECTIONS AT IUR INTERFACE ........................................ 108 NUMBER OF FAILED SCCP CONNECTIONS AT IUR INTERFACE ................................................. 108
16.
RNC LOAD MANAGEMENT .................................................................................................... 109 16.1.

LOAD OF TMU PROCESSORS ................................................................................................
109
16.1.1 16.1.2 16.1.3 17.
Average load of TMU processors .............................................................................. 109 Minimum load of TMU processors ............................................................................. 109 Maximum load of TMU processors ............................................................................ 110
NODE B PCM ........................................................................................................................... 112 17.1. 17.2. 17.3. 17.4. 17.5. LOSS OF INCOMING SIGNAL ................................................................................................... 112 ALARM INDICATION SIGNAL ................................................................................................... 112 LOSS OF FRAME ALIGNMENT ................................................................................................. 112 FRAME ERROR ..................................................................................................................... 113 CRC................................................................................................................................... 113
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 9/136

17.6. 17.7. 17.8. 17.9. 17.10. 17.11. 17.12. 17.13. 17.14. 18. REMOTE ALARM INDICATION ................................................................................................. 114 FRAME ALIGNMENT SIGNAL .................................................................................................. 114 E-BITS ................................................................................................................................. 114 BIPOLAR VIOLATION ............................................................................................................. 115 SLIP EVENT ...................................................................................................................... 115 ERRORED SECONDS ......................................................................................................... 116 SEVERELY ERRORED SECONDS ........................................................................................ 116 BACKGROUND BLOCK ERRORS ......................................................................................... 116 UNAVAILABLE SECONDS ................................................................................................... 117
NODE B ATM............................................................................................................................ 118 18.1. 18.2. 18.3. 18.4. 18.5. 18.6. 18.7. 18.8. 18.9. 18.10. 18.11. 18.12. 18.13. 18.14. 18.15. 18.16. NUMBER OF RECEIVED CELLS (AAL2) ................................................................................... 118 NUMBER OF LOST CPS PACKETS (AAL2).............................................................................. 118 NUMBER OF STF PARITY ERRORS (AAL2)............................................................................. 118 NUMBER OF SEQUENCE NUMBER ERRORS (AAL2) ................................................................ 119 NUMBER OF CPS HEADER CHECKSUM ERROR (AAL2)........................................................ 119 NUMBER OF CPS LENGTH ERRORS (AAL2)........................................................................... 120 NUMBER OF LENGTH MISMATCHES (AAL2) ........................................................................... 120 NUMBER OF INVALID CID (AAL2).......................................................................................... 120 NUMBER OF CELLS WITH OFFSET FIELD > 47 (AAL2)............................................................. 121 NUMBER OF RECEIVED CELLS (AAL5) ............................................................................... 121 NUMBER OF ABORT ERRORS (AAL5)................................................................................. 121 NUMBER OF LENGTH ERRORS (AAL5) ............................................................................... 122 NUMBER OF CRC FRAME ERRORS (AAL5) ........................................................................ 122 NUMBER OF INVALID SIZE ERRORS (AAL5)......................................................................... 123 NUMBER OF SENT CELLS (AAL2)....................................................................................... 123 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............................................... 124 19.1.2 Minimum wide-band received power on Main antenna ............................................. 124 19.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......................................... 125 19.2.2 Minimum wide-band received power on Diversity antenna ....................................... 126 19.2.3 Maximum wide-band received power on diversity antenna ....................................... 126 19.3. TRANSMITTED CARRIER POWER ............................................................................................ 127 19.3.1 Average transmitted carrier power............................................................................. 127 19.3.2 Minimum transmitted carrier power............................................................................ 127 19.3.3 Maximum transmitted carrier power........................................................................... 128 19.4. MULTI-CARRIER POWER AMPLIFIER POWER............................................................................ 128 19.4.1 Average MCPA power................................................................................................ 128
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 10/136

19.4.2 19.4.3 20. Minimum MCPA power .............................................................................................. 129 Maximum MCPA power ............................................................................................. 129
IBTS LOAD MANAGEMENT.................................................................................................... 130 20.1. CEM CAPACITY USED........................................................................................................... 130 20.1.1 Average CEM capacity used...................................................................................... 130 20.1.2 Minimum CEM capacity used..................................................................................... 130 20.1.3 Maximum CEM capacity used.................................................................................... 131 20.2. CEM RESOURCE ALLOCATION FAILURE ................................................................................. 131
21.
ABBREVIATIONS AND DEFINITIONS.................................................................................... 133 21.1. 21.2. ABBREVIATIONS ................................................................................................................... 133

DEFINITIONS ........................................................................................................................
133
21.2.1 21.2.2 22. 23. 24.
Access stratum configuration ..................................................................................... 133 Reference cell ............................................................................................................ 133
ANNEXE 1: DOWNLINK ACCESS STRATUM CONFIGURATIONS ..................................... 134 ANNEXE 2: RRC CONNECTION ESTABLISHMENT CAUSES ............................................. 135 ANNEXE 3: RRC CONNECTION RELEASE CAUSES........................................................... 136
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 11/136
1.
1.1.
INTRODUCTION
OBJECT
This document provides the list of UMTS Access counters as available on the user interface.
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.
2.1.
RELATED DOCUMENTS
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 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication Management; Performance Management (PM); Performance Measurements - GSM (Release 4) [A3] 3GPP TS 32.403 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects;
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 12/136

Telecommunication Management; Performance Management (PM); 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 equipment and maintenance features of transmission
Loss of Signal (LOS), Alarm Indication Signal (AIS) and Remote Defect Indication (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 availability targets Error performance parameters and objectives for international, constant bit rate digital paths at or above the primary rate
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 13/136
3.
3.1.
DOCUMENT ORGANISATION
FAMILIES OF COUNTERS
The counters specified in the document are grouped into families of counters. A family of counter is attached to a given UMTS feature (e.g. Hard hand-over where are put together counters allowing to report hard hand-over performances) or to a Performance Management purpose (e.g. Traffic where are put together counters related 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 for identifying 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 in minutes or hours, e.g. 30 mn, while a measurement is elaborated on periods expressed in milliseconds, e.g. 500 ms. 3GPP Performance Management specifications preferably considers measurements. When the context refers to 3GPP specifications measurement is used, while counter is used is more NORTEL specific part, but both wordings are equivalent.
3.2.2 SPECIFIED COUNTERS ARE USER AVAILABLE COUNTERS ON THE OMC GUI
Specified counters are user available counters, periodically reportable on the OMC GUI and directly derived from the raw Network elements counters. Remark: In this document are not specified the metrics provided by the optional postprocessing 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 1 each time a call establishment occurs.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 14/136
Value counter A value counter is elaborated according the mechanism defined by the 3GPP TS 32.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 is incremented by a value attached to the event itself. An example is the counter Occupation of a subscriber line which is incremented by the duration of the call, each time a call is released. The NORTEL value counter provides not only the cumulated value which corresponds 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 each granularity 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 TS 32.104 (document [A1]), to implement a SI type measurement. It is elaborated using sampling events periodically generated. The load counter is incremented by a value sampled on the sampling event occurence . An example is the counter Number of calls established on a subscriber end switch which is incremented by the number of established calls measured on each sampling event. 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 provide values on the GUI, for the three following counters, at the end of each granularity period: the mean number of established calls during the granularity period by dividing the cumulated value by the number of sampling events; this provides 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.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 15/136
NETWORK ELEMENT COUNTER CUMULATIVE counter VALUE counter Number of events Cumulated value (1) Number of events (1)
COUNTERS OMC GUI
PRESENTED
ON
THE
Number of events
CC type counter
Cumulated value
DER type counter

Number of events Mean value = Cumulated value / Number of events Minimum value (attached to an event) Maximum value (attached to an event) Minimum value Maximum value Cumulated value Mean value = Cumulated value / Number of events
LOAD counter
Cumulated value (1) Number of samplings (1)
SI type counter
Minimum value (obtained by a sampling) Maximum value (obtained by a sampling) Minimum value Maximum value
(1) There is no mean value field in the NE-OMC interface. However The NE may report directly the mean value over the observation period in the cumulated value field. In this case, the Number of Events/Number of Sampling field is set to 1 and the Cumulated value and the Mean value in XML results file (on the interface-N) are the same and Number of Events is 1. Remark NORTEL UTRAN do not implement, in a general way, GAUGE type measurements. To provide the current value of a measurement by incrementing it by one when a positive event occurs and by decrementing it by one when a negative event occurs, may lead to some shifts if an event is missed. For instance, a GAUGE type Number of calls established on a subscriber end switch may be implemented by incrementing it each time a subscriber call is established and decremented each time a subscriber call is released. The problem is there is a permanent shift, making the counter value to be false, during successive granularity periods if an event is lost.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 16/136
3.2.3 COUNTERS ARE SPECIFIED ACCORDING A COUNTER DEFINITION TEMPLATE

The counters are specified according the Measurement definition template defined in the 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 the present 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 during the period of measurement; DER (Discrete Event Registration), when data related to a particular event are captured every nth event 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 be updated; This will be defined by identifying protocol related trigger events for starting and stopping measurement processes, or updating the current measurement result value. Where it is not possible to give a precise condition, then the conditional circumstances leading to the update are 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, which is 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. trunk1 means object class is trunk and instance #1 is being measured. The object class and instance 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 TS 32.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 measurement job.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 17/136

g) Switching Technology This section contains the Switching domain(s) this measurement is applicable to i.e. Circuit Switched and/or Packet Switched.
Two counter specification items are added to the seven items a), b), c), d), e), f), g) considered by the 3GPP. They are: h) 3GPP compliance This section states on the compliance of the NORTEL measurement with the 3GPP specification. If the NORTEL implementation is fully compliant with the 3GPP specification, then the statement is 3GPP specified counter. If the counter is not considered by the 3GPP, then the statement is NORTEL specified counter. If the NORTEL implementation is not fully compliant with the 3GPP specification, the section explains 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 NORTEL
UMTS V3 implementation.
Nevertheless, the currently NORTEL provided counters are matched against this TS in order to show how much they are in-line with the current 3GPP SA5 work, even if this work is not completed 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 had been modified in a subsequent version, then only the version in which the current counter specification had been introduced is provided. 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 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 protocol messages. 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 be screened 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 paragraph specifying the various sub-counter with their # with their meaning.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 18/136

For consistency purpose, the wording Screening = NO is mentioned for counters providing only 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 drop counter which is breakdown into sub-counters, each one providing the number of call drops for a given call drop reason. In the current document version , the list of sub-counters attached to each screened counter is provided for information and may be subject for further modifications.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 19/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 NBAP message sent by Node B to the Controlling RNC in response to a RADIO LINK SETUP REQUEST message. The measurement considers each Radio Link mentioned as set-up in the RADIO LINK SETUP RESPONSE 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 ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.RadioLinkSetupSuccess.DL stratum conf 0 VS.RadioLinkSetupSuccess.DL stratum conf 1 VS.RadioLinkSetupSuccess.DL stratum conf 2 VS.RadioLinkSetupSuccess.DL stratum conf 3 VS.RadioLinkSetupSuccess.DL stratum conf 4 VS.RadioLinkSetupSuccess.DL stratum conf 5 VS.RadioLinkSetupSuccess.DL stratum conf 6 VS.RadioLinkSetupSuccess.DL stratum conf 7 VS.RadioLinkSetupSuccess.DL stratum conf 8 VS.RadioLinkSetupSuccess.DL stratum conf 9 VS.RadioLinkSetupSuccess.DL stratum conf 10
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
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 20/136

I. Message flow
CRNC
RADIO LINK SETUP REQUEST
Node B
RADIO LINK SETUP RESPONSE
Radio Link Setup procedure: Successful Operation
4.2.
A. B. C.
NUMBER OF FAILED NBAP RADIO-LINK SETUPS

This measurement provides the number of radio links failed in setup on a NBAP point of view, screened by detecting event. CC This measurement is based on two different events: 1) Receipt of a NBAP RADIO LINK SETUP FAILURE message sent by Node B to the Controlling RNC in response to a RADIO LINK SETUP REQUEST message. The measurement considers each Radio Link referred as failed in the NBAP RADIO LINK SETUP FAILURE message. 2) Time-out expired without reception of a RADIO LINK SETUP RESPONSE message or RADIO LINK SETUP FAILURE message. The measurement considers each Radio Link required to set-up in the NBAP RADIO LINK SETUP REQUEST message.
D.
Two integer values: one for each above event. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> RADIO LINK SETUP FAILURE reception Time-out
E. VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure VS.RadioLinkSetupUnsuccess.Timeout F. FDDCell G. Valid for circuit switched and packet switched traffic H. NORTEL specified counter NORTEL # 0002 Current counter specification introduced in V 2.0c I. Message flow
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 21/136
CRNC
RADIO LINK SETUP REQUEST
Node B
RADIO LINK SETUP FAILURE
Radio Link Setup procedure: Unsuccessful Operation
4.3.
A. B. C.
NUMBER OF SUCCESSFUL NBAP RADIO-LINK ADDITIONS

This measurement provides the number of radio-links successfully added on a NBAP point of view, screened by Downlink Access Stratum configuration. CC Receipt of a RADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION FAILURE NBAP message sent by Node B to the Controlling RNC in response to a RADIO LINK SETUP REQUEST message. The measurement considers each Radio Link mentioned as added in the RADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION 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.RadioLinkAdditionSuccess.DL stratum conf 0 VS.RadioLinkAdditionSuccess.DL stratum conf 1 VS.RadioLinkAdditionSuccess.DL stratum conf 2 VS.RadioLinkAdditionSuccess.DL stratum conf 3 VS.RadioLinkAdditionSuccess.DL stratum conf 4 VS.RadioLinkAdditionSuccess.DL stratum conf 5 VS.RadioLinkAdditionSuccess.DL stratum conf 6 VS.RadioLinkAdditionSuccess.DL stratum conf 7 VS.RadioLinkAdditionSuccess.DL stratum conf 8 VS.RadioLinkAdditionSuccess.DL stratum conf 9 VS.RadioLinkAdditionSuccess.DL stratum conf 10
F.
FDDCell
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 22/136

G. H. Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0003 Current counter specification introduced in V 2.0c I. Message flow
CRNC
RADIO LINK ADDITION REQUEST
Node B
RADIO LINK ADDITION RESPONSE
Radio Link Addition procedure: Successful Operation
4.4.
A. B. C.
NUMBER OF FAILED NBAP RADIO-LINK ADDITIONS

This measurement provides the number of radio links failed in addition on a NBAP point de view. CC This measurement is based on two different events: 1) Receipt of a NBAP RADIO LINK ADDITION FAILURE message sent by Node B to the Controlling RNC in response to a RADIO LINK ADDITION REQUEST message. The measurement considers each Radio Link referred as failed in the NBAP RADIO LINK ADDITION FAILURE message. 2) Time-out expired without reception of a RADIO LINK ADDITION RESPONSE message 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 ----> Sub-counter # 1 ----> RADIO LINK ADDITION FAILURE reception Time-out
E.
VS.RadioLinkAdditionUnsuccess.RadioLinkAdditionFailure VS.RadioLinkAdditionUnsuccess.Timeout
F. G.
FDDCell Valid for circuit switched and packet switched traffic

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

H. NORTEL specified counter NORTEL # 0004 Current counter specification introduced in V 2.0c I. Message flow
CRNC
Node B
RADIO LINK ADDITION FAILURE
Radio Link Addition procedure: Unsuccessful Operation
4.5.
A. B. C.
NUMBER OF SUCCESSFUL NBAP RADIO-LINK DELETIONS

This measurement provides the number of radio-links successfully deleted on a NBAP point of view. CC Receipt of a NBAP RADIO LINK DELETION RESPONSE message sent by Node B to the Serving RNC in response to a RADIO LINK DELETION REQUEST. The measurement considers each Radio Link referred in the NBAP RADIO LINK DELETION RESPONSE message
D.
A single integer value. Screening = NO
E. F. G. H.
VS.RadioLinkDeletionSuccess FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0005 Current counter specification introduced in V 2.0c
I.
Message flow
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 24/136

CRNC
RADIO LINK DELETION REQUEST
Node B
RADIO LINK DELETION RESPONSE
Radio Link Deletion procedure: Successful Operation
4.6.
A. B. C. D.
NUMBER OF FAILED NBAP RADIO-LINK DELETIONS

This measurement provides the number of radio links failed in deletion on a NBAP point de view. CC Time-out expired without reception of a RADIO LINK DELETION RESPONSE A single integer value. Screening = NO
E. F. G. H.
VS.RadioLinkDeletionUnsuccess FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0006 Current counter specification introduced in V 2.0c
I.
Message flow
4.7.
NUMBER OF SUCCESSFUL NBAP RADIO-LINK RECONFIGURATION 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 LINK RECONFIGURATION READY 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
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 25/136

E. VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 0 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 1 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 2 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 3 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 4 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 5 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 6 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 7 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 8 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 9 VS.RadioLinkReconfigPrepareSuccess.DL stratum conf 10 F. FDDCell G. Valid for circuit switched and packet switched traffic H. NORTEL specified counter 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.
A. B. C.
NUMBER OF FAILED NBAP RADIO-LINK RECONFIGURATION PREPARATIONS

This measurement provides the number of radio links failed in reconfiguration preparation. CC This measurement is based on four different events: 1) Receipt of a NBAP RADIO LINK RECONFIGURATION FAILURE message sent by Node B to the Controlling RNC in response to a RADIO LINK RECONFIGURATION PREPARE message.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 26/136

2) 3) 4) D. No reception of RADIO LINK RECONFIGURATION READY message before a timeout RRM refusal (e.g. no power allocation, no code allocation) I-Node refusal (e.g. no CID allocation)
Four integer values: one for each above event Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Sub-counter # 3 ----> RADIO LINK RECONFIGURATION FAILURE reception Time-out RRM refusal I-Node refusal
E.
VS.RadioLinkReconfigPrepareUnsuccess.RadioLinkReconfigurationFailure VS.RadioLinkReconfigPrepareUnsuccess.TimeoutNbap VS.RadioLinkReconfigPrepareUnsuccess.RrmRefusal VS.RadioLinkReconfigPrepareUnsuccess.INodeRefusal
F. G. H.
FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0008 Counter introduced in V 2.0c
I.
Message flow
CRNC Node B
RADIO LINK RECONFIGURATION FAILURE
Synchronised Radio Link Reconfiguration Preparation procedure, Unsuccessful Operation
4.9.
A. B. C. D.
NUMBER OF NBAP RADIO-LINK RECONFIGURATION CANCELS

This measurement provides the number of NBAP RADIO LINK RECONFIGURATION CANCEL messages. CC Emission of a NBAP RADIO LINK RECONFIGURATION CANCEL message by the RNC to a Node B. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1).
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 27/136

Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.RadioLinkReconfigCancelSuccess.DL stratum conf 0 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 1 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 2 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 3 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 4 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 5 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 6 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 7 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 8 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 9 VS.RadioLinkReconfigCancelSuccess.DL stratum conf 10
F. G. H.
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 RECONFIGURATION COMMITS

A. B. C. D. This measurement provides the number of NBAP RADIO LINK RECONFIGURATION COMMIT messages. CC Emission of a NBAP RADIO LINK RECONFIGURATION COMMIT message by the RNC to a Node B A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening:
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 28/136

Sub-counter # i ----> F. Downlink Access Stratum configuration # i for i = 0 to 10
VS.RadioLinkReconfigCommitSuccess.DL stratum conf 0 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 1 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 2 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 3 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 4 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 5 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 6 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 7 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 8 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 9 VS.RadioLinkReconfigCommitSuccess.DL stratum conf 10
F. G. H.
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. B. This measurement provides the average number of NBAP radio-links established in a cell during a granularity period. DER NORTEL VAL type counter 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 averaged value is assessed at the end of the granularity period.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 29/136

D. A single integer value. Screening = NO E. F. G. H. VS.RadioLinkEstablishedPerCellVal.Avg FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0012 Counter introduced in V 2.0c
4.11.2 MINIMUM NUMBER OF NBAP RADIO-LINKS

A. B. This measurement provides the minimum number of NBAP radio-links established in a cell during a granularity period. DER NORTEL VAL type counter 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 minimum value is assessed at each modification of the current counter. D. A single integer value. Screening = NO E. F. G. H. VS.RadioLinkEstablishedPerCellVal.Min FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0012 Counter introduced in V 2.0c
4.11.3 MAXIMUM NUMBER OF NBAP RADIO-LINKS

A. B. This measurement provides the maximum number of NBAP radio-links established in a cell during a granularity period. DER NORTEL VAL type counter 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.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 30/136

D. A single integer value. Screening = NO E. F. G. H. VS.RadioLinkEstablishedPerCellVal.Max FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0012 Counter introduced in V 2.0c
4.12. NUMBER OF DROPPED CALLS ON LAST RADIO-LINK RELEASE

A. B. C. This measurement provides the number of dropped calls on last radio-link release, for each cell controlled by the RNC. CC 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 fail simultaneously and make the call to be dropped. D. A single integer value. Screening = NO E. F. G. H. VS.RadioLinkDroppedLastRadioLink FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0013 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 31/136
5.
5.1.
A.
HARD HAND-OVERS
NUMBER OF INTER-RAT HANDOVER FROM UTRAN COMMANDS PER CELL
This measurement provides the number of RRC HANDOVER FROM UTRAN COMMAND messages emitted by a RNC, for each cell controlled by the RNC and acting as a reference cell i.e. an involved UE in the procedure is served by a RNC which is the controlling RNC of its reference cell.
B. C. D.
CC Emission of a RRC HANDOVER FROM UTRAN COMMAND by a RRC to a UE having its reference controlled by the considered RNC A single integer value per reason. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Rescue CS Service CS
E.
VS.RrcHoFromUtranCommand.RescueCS VS.RrcHoFromUtranCommand.ServiceCS
F.
FDDCell Related to the reference cell
G. H.
Valid for circuit switched traffic NORTEL specified counter NORTEL # 0101 Counter introduced in V 2.0c
I.
Message flow
UE UTRAN
HANDOVER FROM UTRAN COMMAND
Inter-RAT handover from UTRAN, successful case
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 32/136
5.2.
A.
NUMBER OF INTER-RAT HANDOVER FROM UTRAN COMMANDS PER RNC

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 its reference cell.
B. C. D.
CC Emission of a RRC HANDOVER FROM UTRAN COMMAND by a RRC to a UE having its reference cell controlled by another RNC A single integer value per reason. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Rescue CS Service CS
E.
VS.RrcHoFromUtranCommandNeighbRnc.RescueCS VS.RrcHoFromUtranCommandNeighbRnc.ServiceCS
F. G. H.
Neighboring RNC Valid for circuit switched traffic NORTEL specified counter NORTEL # 0102 Counter introduced in V 2.0c
I.
Message flow See 5.1
5.3.
A.
NUMBER OF INTER-RAT HANDOVER FROM UTRAN FAILURES PER CELL

This measurement provides the number of RRC HANDOVER FROM UTRAN FAILURE messages, for each cell controlled by the RNC and acting as a reference cell i.e. an involved UE in the procedure is served by a RNC which is the controlling RNC of its reference cell.
B. C. D.
CC Reception of a RRC HANDOVER FROM UTRAN FAILURE message by a RRC from a UE having its reference controlled by the considered RNC A single integer value per reason. Screening: Sub-counter # 0 ----> Rescue CS
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 33/136

Sub-counter # 1 ----> E. Service CS
VS.RrcHoFromUtranFailure.RescueCS VS.RrcHoFromUtranFailure.ServiceCS
F.
G. H.
Valid for circuit switched traffic NORTEL specified counter NORTEL # 0103 Counter introduced in V 2.0c
I.
Message flow
UE UTRAN
HANDOVER FROM UTRAN COMMAND
HANDOVER FROM UTRAN FAILURE
Inter-RAT handover from UTRAN, failure case
5.4.
A.
NUMBER OF FAILED INTER-RAT HANDOVER FROM UTRAN PER RNC

This measurement provides the number of RRC HANDOVER FROM UTRAN COMMAND messages received 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 its reference cell.
B. C. D.
CC Reception of a RRC HANDOVER FROM UTRAN FAILURE message by a RRC from a UE having its reference cell controlled by another RNC A single integer value per reason. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Rescue CS Service CS
E.
VS.RrcHoFromUtranFailureNeighbRnc.RescueCS VS.RrcHoFromUtranFailureNeighbRnc.ServiceCS
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 34/136

F. G. H. Neighboring RNC Valid for circuit switched traffic NORTEL specified counter NORTEL # 0104 Counter introduced in V 2.0c I. Message flow See 5.3
5.5.
A.
NUMBER OF RRC CELL CHANGE ORDER FROM UTRAN PER CELL

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 i.e. an involved UE in the procedure is served by a RNC which is the controlling RNC of its reference cell.
B. C.
CC Emission of a RRC CELL CHANGE ORDER FROM UTRAN message from the RNC to the UE. The event is only considered when the UE has a reference cell under the control of the RNC in charge of the measurement.
D.
E. F.
IRATHO.AttOutPSUTRAN FDDCell Related to the reference cell
G. H.
Valid for packet switched traffic 3GPP specified counter (3GPP specification is applied for the cells which are controlled by the SRNC) NORTEL # 0105 Counter introduced in V 2.0c
I.
Message flow
UE UTRAN
CELL CHANGE ORDER FROM UTRAN
InterRAT cell change order from UTRAN

UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 35/136
5.6.
A.
NUMBER OF RRC CELL CHANGE ORDER FROM UTRAN PER RNC

This measurement provides the number of RRC CELL CHANGE ORDER FROM UTRAN messages sent 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 its reference cell.
B. C.
CC 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..
D.
E. F. G. H.
VS.RrcCellChangeOrderNeighbRnc.RescuePs Neighboring RNC Valid for packet switched traffic NORTEL specified counter NORTEL # 0106 Counter introduced in V 2.0c
I.
5.7.
A.
NUMBER OF CELL CHANGE ORDER FROM UTRAN FAILURE PER CELL

This measurement provides the number of RRC CELL CHANGE ORDER FROM UTRAN FAILURE messages received by a RNC, for each cell controlled by the RNC and acting as a reference cell i.e. an involved UE in the procedure is served by a RNC which is the controlling RNC of its reference cell.
B. C.
CC Reception of a RRC CELL CHANGE ORDER FROM UTRAN FAILURE message sent by an UE to the Serving RNC in response to a RRC CELL CHANGE ORDER FROM UTRAN message. The event is only considered when the UE has a reference cell under the control of the RNC in charge of the measurement.
D.

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

E. F. IRATHO.FailOutPSUTRAN FDDCell Related to the reference cell G. H. Valid for packet switched traffic 3GPP specified counter (3GPP specification is applied for the cells which are controlled by the SRNC) NORTEL # 0107 Counter introduced in V 2.0c 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 UTRAN FAILURE PER RNC
This measurement provides the number of RRC CELL CHANGE ORDER FROM UTRAN FAILURE messages received 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 its reference cell.
A.
B.
CC
C.
Reception of a RRC CELL CHANGE ORDER FROM UTRAN FAILURE message sent by UE to the Serving RNC in response to a RRC CELL CHANGE ORDER FROM UTRAN message. The event is only considered when the UE has a reference cell under the control of the RNC in charge of the measurement.
D.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 37/136

E. F. G. H. VS.RrcCellChangeOrderFailureNeighbRnc.RescuePs Neighboring RNC Valid for packet switched traffic NORTEL specified counter NORTEL # 0108 Counter introduced in V 2.0c I. Message flow See 5.7
5.9.
A.
NUMBER OF 3G TO 2G HANDOVER REQUESTS PER CELL

This measurement provides the number of RRM decisions for a 3G TO 2G handover performed by a RNC, screened by reference cell from which the UEs have left the 3G Network, when these cells are controlled by the considered RNC. This measurement considers both CS and PS handovers.
B. C.
CC 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 RNC in charge of the measurement.
D.
One single integer value per HO reason. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Rescue CS Rescue PS Service CS
E.
VS.3gto2gHoDetectionFromFddcell.RescueCs VS.3gto2gHoDetectionFromFddcell.RescuePs VS.3gto2gHoDetectionFromFddcell.ServiceCS
F.
G. H.
Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0109 Counter introduced in V 2.0c
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 38/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 handover performed by a RNC, screened by neighboring RNC grouping reference cells from which the UEs have left the 3G Network. This measurement considers both CS and PS handovers. B. C. CC 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 RNC which is not the RNC in charge of the measurement. D. One single integer value per HO reason. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> E. Rescue CS Rescue PS Service CS
VS.3gto2gHoDetectionFromFddcellNeighbRnc.RescueCs VS.3gto2gHoDetectionFromFddcellNeighbRnc.RescuePs VS.3gto2gHoDetectionFromFddcellNeighbRnc.ServiceCS
F. G. H.
Neighboring RNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0110 Counter introduced in V 2.0c
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 39/136
6.
6.1.
A.
RRC RADIO-LINK MANAGEMENT

NUMBER OF SUCCESSFUL RRC ACTIVE SET UPDATES PER CELL
This measurement provides the number of successful RRC ACTIVE SET UPDATE procedures managed by a RNC. This counter is updated on the cells that are added to or removed from the active set. CC Receipt of a RRC ACTIVE SET UPDATE COMPLETE message sent by UE to the Serving RNC in response to an ACTIVE SET UPDATE message.
B. C.
D. E.
One integer value for addition to active set, one integer value for removal from active set. SHO.SuccRLAddUESide SHO.SuccRLDelUESide
F.
FDDCell
G. H.
Valid for circuit switched and packet switched traffic 3GPP counter NORTEL # 0401 Current counter specification introduced in V 2.0c
I.
Message flow
UE ACTIVE SET UPDATE
UTRAN
ACTIVE SET UPDATE COMPLETE
Active Set Update procedure, successful case
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 40/136
6.2.
A.
NUMBER OF SUCCESSFUL RRC ACTIVE SET UPDATES PER RNC

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 RNC which are added / removed from active set.
B. C. D.
CC Receipt of a RRC ACTIVE SET UPDATE COMPLETE message sent by UE to the Serving RNC in response to an ACTIVE SET UPDATE message. One integer value for addition to active set, one integer value for removal from active set.
E.
VS.RrcActiveSetUpdateSuccessNeighbRnc.radiolinkAdditionOnCell VS.RrcActiveSetUpdateSuccessNeighbRnc.radiolinkActiveRemovalOnCell
F. G. H.
NeighboringRNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0406 Counter introduced in V 2.0c
I.
6.3.
A.
NUMBER OF FAILED RRC ACTIVE SET UPDATES PER CELL

This measurement provides the number of failed RRC ACTIVE SET UPDATE procedures managed 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 cell belongs to the active set of the involved UE. CC This measurement is based on two different events:. 1) Receipt of a RRC ACTIVE SET UPDATE FAILURE message sent by UE to the Serving RNC in response to a RRC ACTIVE SET UPDATE message. 2) Time-out expired without reception of a ACTIVE SET UPDATE COMPLETE message or a ACTIVE SET UPDATE FAILURE message. The events are only considered for cells belonging to the active set which are under the control of the RNC in charge of the measurement.
B. C.
D.
A single integer value for each cause.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 41/136

Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> E. RRC ACTIVE SET UPDATE FAILURE reception Time-out
SHO.FailRLAddUESid.RrcActiveSetUpdateFailure SHO.FailRLAddUESid.Timeout FDDCell Valid for circuit switched and packet switched traffic 3GPP counter NORTEL # 0402 Current counter specification introduced in V 2.0c
F. G. H.
I.
Message flow
UE ACTIVE SET UPDATE
UTRAN
ACTIVE SET UPDATE FAILURE
Active Set Update procedure, failure case
6.4.
A.
NUMBER OF FAILED RRC ACTIVE SET UPDATES PER RNC

This measurement provides the number of failed RRC ACTIVE SET UPDATE procedures managed 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 the procedure failure. CC
B. C.
This measurement is based on two different events: 1) Receipt of a RRC ACTIVE SET UPDATE FAILURE message sent by UE to the Serving RNC in response to a RRC ACTIVE SET UPDATE message. 2) Time-out expired without reception of a ACTIVE SET UPDATE COMPLETE message or a ACTIVE SET UPDATE FAILURE message. The events are considered for cells belonging to the active set which are outside the control of the RNC in charge of the measurement.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 42/136

D. A single integer value for each cause. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> E. RRC ACTIVE SET UPDATE FAILURE reception Time-out
VS.RrcActiveSetUpdateUnsuccessNeighbRnc.RrcActiveSetUpdateFailure VS.RrcActiveSetUpdateUnsuccessNeighbRnc.Timeout NeighboringRNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0407 Counter introduced in V 2.0c
F. G. H.
I.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 43/136
7.
7.1.
A. B. C. D.
RRC CONNECTION
NUMBER OF RRC CONNECTION REQUESTS
This measurement provides the number of RRC connection requests screened by establishment cause. CC Reception by the RNC of a RRC CONNECTION REQUEST message. 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.<0..20>
F. G. H.
FDDCell. Valid for circuit switched and packet switched traffic traffic. 3GPP specified counter NORTEL # 0409 Counter introduced in V 2.0e
I.
Message flow
UE RRC CONNECTION REQUEST RRC CONNECTION SETUP UTRAN
RRC CONNECTION SETUP COMPLETE
RRC Connection Establishment, network accepts RRC connection
7.2.
A.
NUMBER OF SUCCESSFUL RRC CONNECTION ESTABLISHMENTS

This measurement provides the number of successful RRC connection establishments screened by establishment cause.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 44/136

B. C. CC Reception by the RNC of a RRC CONNECTION SETUP COMPLETE message following a RRC connection establishment attempt. A RRC connection establishment attempt is considered on the reception by the RNC of a RRC CONNECTION REQUEST message. D. An integer value for each establishment cause Screening: Sub-counter # i ----> E. RRC.SuccConnEstab.<0..20> Establishment cause # i as in TS 25.331 (c.f. Annexe 2)
F. G. H.
FDDCell. Valid for circuit switched and packet switched traffic traffic. 3GPP specified counter NORTEL # 0403 Counter introduced in V 1.2.b ; screening criteria later modified
I.
7.3.
A. B. C.
NUMBER OF RRC CONNECTION ESTABLISHMENT FAILURES

This measurement provides the number of RRC connection establishment failures screened by establishment failure cause. CC The measurement counts the number of RRC connection establishment attempts which have not evolved into a RRC connection establishment. A RRC connection establishment attempt is considered on the reception by the RNC of a RRC CONNECTION REQUEST message. A RRC connection establishment is considered on the reception by the RNC of a RRC CONNECTION SETUP COMPLETE message following a RRC connection attempt.
D.
An integer value for each connection establishment failure cause. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Sub-counter # 3 ----> Sub-counter # 4 ----> Time-out Unavailable downlink code resources Unavailable downlink power resources Unspecified RSSI
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 45/136

E. RRC.FailConnEstab.<0..4>
F. G. H.
FDDCell Valid for circuit switched and packet switched traffic. 3GPP specified counter NORTEL provides a wider screening as the one requested by 3GPP (which is reduced to Congestion + Time-out + Unspecified). NORTEL # 0404 Counter introduced in V 1.2.b ; screening criteria later modified
I.
Message flow
UE RRC CONNECTION REQUEST RRC CONNECTION REJECT UTRAN
RRC Connection Establishment, network rejects RRC connection
7.4.
A.
NUMBER OF RRC CONNECTION RELEASES PER CELL

This measurement provides the number of RRC connection releases managed by a RNC, screened by release cause, for each cell controlled by the RNC. During such a procedure, the measurement attached to a given cell is incremented if the cell is the reference cell of the involved UE.
B. C.
CC Emission by the RNC of a RRC CONNECTION RELEASE message. The event is only considered when the UE has a reference cell under the control of the RNC in charge of the measurement.
D.
An integer value for each connection release cause Screening: Sub-counter # i ----> Connection release cause # i as in TS 25.331 (c.f. Annexe 3)
E.
VS.RrcConnectionRelease.NormalEvent VS.RrcConnectionRelease.Unspecified+SccpReleaseCause VS.RrcConnectionRelease.Pre-emptiveRelease

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

VS.RrcConnectionRelease.Congestion VS.RrcConnectionRelease.Re-establishmentReject VS.RrcConnectionRelease.UserInactivity VS.RrcConnectionRelease.DirectedSignallingConnectionRe-establishement F. G. H. FDDCell. Valid for circuit switched and packet switched traffic. 3GPP specified counter (specification applied to the only cells that are controlled by the SRNC) NORTEL # 0405 Counter introduced in V 1.2.b ; screening criteria later modified I. Message flow
UE RRC CONNECTION RELEASE UTRAN
RRC CONNECTION RELEASE COMPLETE
RRC Connection Release procedure on the DCCH
7.5.
NUMBER OF RRC CONNECTION RELEASES PER RNC
A. This measurement provides the number of RRC connection releases managed by a RNC, screened by release cause, for each neighboring RNC. During such a procedure, the measurement attached to a given neighboring RNC is incremented if the neighboring RNC controls the reference cell of the involved UE. B. C. CC Emission by the RNC of a RRC CONNECTION RELEASE message. The event is only considered when the UE has a reference cell outside the control of the RNC in charge of the measurement. D. An integer value for each connection release cause Screening: Sub-counter # i ----> Connection release cause # i as in TS 25.331 (c.f. Annexe 3).
E.
VS.RrcConnectionReleaseNeighbRnc.NormalEvent
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 47/136

VS.RrcConnectionReleaseNeighbRnc.Unspecified+SccpReleaseCause VS.RrcConnectionReleaseNeighbRnc.Pre-emptiveRelease VS.RrcConnectionReleaseNeighbRnc.Congestion VS.RrcConnectionReleaseNeighbRnc.Re-establishmentReject VS.RrcConnectionReleaseNeighbRnc.UserInactivity VS.RrcConnectionReleaseNeighbRnc.DirectedSignallingConnectionRe-establishement F. G. H. NeighboringRNC Valid for circuit switched and packet switched traffic. 3GPP specified counter NORTEL # 0408 Counter introduced in V 2.0c I. Message flow See 7.4
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 48/136
8.
8.1.
A. B. C. D.
IU INTERFACE
NUMBER OF SUCCESSFUL SCCP CONNECTIONS AT IU INTERFACE
This measurement provides the number of successful SCCP connections at Iu interface, screened by CN domain CC Successful SCCP connection establishment An integer value for each CN domain Screening: Sub-counter # 0 Sub-counter # 1 ----> ----> Connection on Iu-CS Connection on Iu-PS
E.
VS.IuSccpCnxSuccess.WithCoreNetworkCs VS.IuSccpCnxSuccess.WithCoreNetworkPs
F. G. H.
RNC Valid for circuit switched and packet switched traffic. NORTEL specified counter NORTEL # 0501 Counter introduced in V 2.0c
8.2.
A. B. C. D.
NUMBER OF FAILED SCCP CONNECTIONS AT IU INTERFACE

This measurement provides the number of failed SCCP connections at Iu interface, screened by CN domain and by peer entity having refused the connection CC Unsuccessful SCCP connection establishment An integer value for each couple (CN domain * Refusing Iu peer entity) Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 ----> ----> ----> Connection on Iu-CS refused by the CN Connection on Iu-CS refused by the RNC Connection on Iu-PS refused by the CN
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 49/136

Sub-counter # 3 ----> Connection on Iu-PS refused by the RNC
Note : Sub-counters #1 and #3 are not incremented in V2 because the RNC does not manages relocation. E. VS.IuSccpCnxUnsuccess.Iu-csConnectionReqByRnc VS.IuSccpCnxUnsuccess.Iu-csConnectionReqByCs VS.IuSccpCnxUnsuccess.Iu-psConnectionReqByRnc VS.IuSccpCnxUnsuccess.Iu-psConnectionReqByPs F. G. H. RNC Valid for circuit switched and packet switched traffic. NORTEL specified counter NORTEL # 0502 Counter introduced in V 2.0c
8.3.
A. B. C. D.
NUMBER OF RELEASE REQUESTS ON IU CS

This measurement provides the number of RANAP IU RELEASE REQUEST messages sent by the RNC on Iu CS CC Emission of a RANAP IU RELEASE REQUEST message by the RNC on Iu CS A single integer value. Screening = NO
E. F.
VS.IuReleaseRequestCs FDDCell Related to the reference cell
G. H.
Valid for circuit switched traffic. NORTEL specified counter NORTEL # 0503 Counter introduced in V 2.0c
I.
Message flow
RNC
CN IU RELEASE REQUEST
Iu Release Request procedure. Successful operation.

UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 50/136
8.4.
A. B. C. D.
NUMBER OF RELEASE REQUESTS ON IU PS

This measurement provides the number of RANAP IU RELEASE REQUEST messages sent by the RNC on Iu PS CC Emission of a RANAP IU RELEASE REQUEST message by the RNC on Iu PS A single integer value. Screening = NO
E. F.
VS.IuReleaseRequestPs FDDCell Related to the reference cell
G. H.
Valid for packet switched traffic. NORTEL specified counter NORTEL # 0504 Counter introduced in V 2.0c
I.
8.5.
A. B. C. D.
NUMBER OF RELEASE COMMANDS ON IU CS

This measurement provides the number of RANAP IU RELEASE COMMAND messages received by the RNC on Iu CS CC Reception of a RANAP IU RELEASE COMMAND message by the RNC on Iu CS An integer value for each cause of IU RELEASE COMMAND on Iu CS Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 ----> ----> ----> Normal end of communication Successful 3G/2G relocation Previous request from iRNC (Iu_release_request already sent) Sub-counter # 3 ----> Other cause
E.
VS.IuReleaseCommandCs.Normal VS.IuReleaseCommandCs.CompletionSuccessful3g2gRelocation VS.IuReleaseCommandCs.PreviousRequestFromIrnc VS.IuReleaseCommandCs.Other

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

F. FDDCell Related to the reference cell G. H. Valid for circuit switched traffic. NORTEL specified counter NORTEL # 0505 Counter introduced in V 2.0c I. Message flow
RNC
CN
IU RELEASE COMMAND IU RELEASE COMPLETE

Iu Release procedure. Successful operation.
8.6.
A. B. C. D.
NUMBER OF RELEASE COMMANDS ON IU PS

This measurement provides the number of RANAP IU RELEASE COMMAND messages received by the RNC on Iu PS CC Reception of a RANAP IU RELEASE COMMAND message by the RNC on Iu PS An integer value for each cause of IU RELEASE COMMAND on Iu PS Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 ----> ----> ----> Normal end of communication Successful 3G/2G relocation Previous request from iRNC (Iu_release_request already sent) Sub-counter # 3 ----> Other cause
E.
VS.IuReleaseCommandPs.Normal IRATHO.SuccOutPSUTRAN VS.IuReleaseCommandPs.PreviousRequestFromIrnc VS.IuReleaseCommandPs.Other
F.
G.
Valid for packet switched traffic.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 52/136

H. NORTEL specified counter NORTEL # 0506 Counter introduced in V 2.0c I. Message flow See 8.5
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 53/136
9.
9.1.
A. B. C.
RAB AND RB MANAGEMENT

NUMBER OF SUCCESSFUL RAB ESTABLISHMENTS
This measurement provides the number of successful Radio Access Bearer establishments, screened by traffic class. CC Emission by the RNC of RAB ASSIGNMENT RESPONSE message(s) following the reception of a RANAP RAB ASSIGNMENT REQUEST message. The RAB ASSIGNMENT RESPONSE(s) may report RABs successfully established or modified and RABs released. The measurement considers (and only considers) each successfully established RAB.
D.
A single integer value for each Traffic Class. Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 Sub-counter # 3 ----> ----> ----> ----> Traffic Class 0, i.e. Traffic Class 1, i.e. Traffic Class 2, i.e. Traffic Class 3, i.e. Conversational Streaming Interactive Background
E.
VS.RabAssignmentSetupSuccess.Conversational VS.RabAssignmentSetupSuccess.Streaming VS.RabAssignmentSetupSuccess.Interactive VS.RabAssignmentSetupSuccess.Background
F. G. H.
RNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL provides the 3GPP required screening per traffic class but for a global counter taking into account CS and PS domains while 3GPP considers two different counters, one dedicated to CS domain and the other one to PS domain. NORTEL # 0604 Counter introduced in V 2.0c
I.
Message flow
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 54/136
RNC RAB ASSIGNMENT REQUEST RAB ASSIGNMENT RESPONSE

. . .
CN
* it can be several responses
RAB Assignment procedure. Successful operation.
9.2.
A. B. C.
NUMBER OF FAILED RAB ESTABLISHMENTS

This measurement provides the number of unsuccessful Radio Access Bearer establishments, screened by traffic class. CC Emission by the RNC of the RANAP RAB ASSIGNMENT RESPONSE message(s) following the reception of a RANAP RAB ASSIGNMENT REQUEST message. The RAB ASSIGNMENT RESPONSE(s) may report RABs successfully established or modified and RABs released. The measurement considers (and only considers) each RAB requested for establishment in the RAB ASSIGNMENT REQUEST which is not reported as established in the RAB ASSIGNMENT RESPONSE(s).
D.
A single integer value for each Traffic Class. Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 Sub-counter # 3 ----> ----> ----> ----> Traffic Class 0, i.e. Traffic Class 1, i.e. Traffic Class 2, i.e. Traffic Class 3, i.e. Conversational Streaming Interactive Background
E.
VS.RabAssignmentSetupUnsuccess.Conversational VS.RabAssignmentSetupUnsuccess.Streaming VS.RabAssignmentSetupUnsuccess.Interactive VS.RabAssignmentSetupUnsuccess.Background
F. G. H.
RNC Valid for circuit switched and packet switched traffic NORTEL specified counter
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 55/136

NORTEL # 0605 Counter introduced in V 2.0c I. Message flow See 9.1
9.3.
A. B. C.
NUMBER OF SUCCESSFUL RAB RELEASES

This measurement provides the number of successful Radio Access Bearer releases, screened by traffic class. CC Emission by the RNC of RAB ASSIGNMENT RESPONSE message(s) following the reception of a RANAP RAB ASSIGNMENT REQUEST message. The RAB ASSIGNMENT RESPONSE(s) may report RABs successfully established or modified and RABs released. The measurement considers (and only considers) each successfully released RAB as requested in the RANAP RAB ASSIGNMENT REQUEST message.
D.
A single integer value for each Traffic Class. Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 Sub-counter # 3 ----> ----> ----> ----> Traffic Class 0 i.e. Traffic Class 1 i.e. Traffic Class 2 i.e. Traffic Class 3 i.e. Conversational Streaming Interactive Background
E.
VS.RabAssignmentReleaseSuccess.Conversational VS.RabAssignmentReleaseSuccess.Streaming VS.RabAssignmentReleaseSuccess.Interactive VS.RabAssignmentReleaseSuccess.Background
F. G. H.
RNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0606 Counter introduced in V 2.0c
I.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 56/136
9.4.
A. B. C.
NUMBER OF FAILED RAB RELEASES

This measurement provides the number of failed Radio Access Bearer releases, screened by traffic class. CC Emission by the RNC of RAB ASSIGNMENT RESPONSE message(s) following the reception of a RANAP RAB ASSIGNMENT REQUEST message. The RAB ASSIGNMENT RESPONSE(s) may report RABs successfully established or modified and RABs released. The measurement considers (and only considers) each RAB requested to be released in the RANAP RAB ASSIGNMENT REQUEST message which is not mentioned as released in the subsequent RAB ASSIGNMENT RESPONSE(s).
D.
A single integer value for each Traffic Class. Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 Sub-counter # 3 ----> ----> ----> ----> Traffic Class 0 i.e. Traffic Class 1 i.e. Traffic Class 2 i.e. Traffic Class 3 i.e. Conversational Streaming Interactive Background
E.
VS.RabAssignmentReleaseUnsuccess.Conversational VS.RabAssignmentReleaseUnsuccess.Streaming VS.RabAssignmentReleaseUnsuccess.Interactive VS.RabAssignmentReleaseUnsuccess.Background
F. G. H.
RNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0607 Counter introduced in V 2.0c
I.
9.5.
A.
NUMBER OF SUCCESSFUL RADIO-BEARER ESTABLISHMENTS PER CELL

This measurement provides the number of successful radio bearer establishments, for each cell controlled by the RNC. During such a procedure, the measurement attached to a given cell is incremented if the cell belongs to the active set of the involved UE
B.
CC
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 57/136

C. Reception by the RNC of a RRC RADIO BEARER SETUP COMPLETE message following the emission of a RRC RADIO BEARER SETUP message. The event is only considered when the UE has one or several cells in its active set which are under the control of its SRNC. D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.RadioBearerSetupSuccess.DL stratum conf 0 VS.RadioBearerSetupSuccess.DL stratum conf 1 VS.RadioBearerSetupSuccess.DL stratum conf 2 VS.RadioBearerSetupSuccess.DL stratum conf 3 VS.RadioBearerSetupSuccess.DL stratum conf 4 VS.RadioBearerSetupSuccess.DL stratum conf 5 VS.RadioBearerSetupSuccess.DL stratum conf 6 VS.RadioBearerSetupSuccess.DL stratum conf 7 VS.RadioBearerSetupSuccess.DL stratum conf 8 VS.RadioBearerSetupSuccess.DL stratum conf 9 VS.RadioBearerSetupSuccess.DL stratum conf 10
F. G. H.
FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0601 Current counter specification introduced in V 2.0c
I.
Message flow
UE RADIO BEARER SETUP
UTRAN
RADIO BEARER SETUP COMPLETE
Radio Bearer Establishment, normal case
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 58/136
9.6.
A.
NUMBER OF SUCCESSFUL RADIO-BEARER ESTABLISHMENTS PER RNC

This measurement provides the number of successful radio bearer establishments, 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 in the active set which are controlled by this neighboring RNC.
B. C.
CC Reception by the RNC of a RRC RADIO BEARER SETUP COMPLETE message following the emission of a RRC RADIO BEARER SETUP message. The event is only considered when the UE has one or several cells in its active set which are outside the control of its SRNC.
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.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 0 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 1 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 2 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 3 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 4 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 5 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 6 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 7 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 8 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 9 VS.RadioBearerSetupSuccessNeighbRnc.DL stratum conf 10
F. G. H.
Neighboring RNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0610 Counter introduced in V 2.0c
I.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 59/136
9.7.
A.
NUMBER OF REFUSED RADIO-BEARER ESTABLISHMENTS PER CELL

This measurement provides the number of RB establishment refusals before any sending of RRC RADIO BEARER SETUP, screened by establishment refusal cause, for each cell controlled by the RNC. During such a procedure, the measurement attached to a given cell is incremented if the cell belongs to the active set of the involved UE.
B. C.
CC The measurement counts the number of RB establishment attempts which have not evolved into the sending of a RADIO BEARER SETUP message. A RB establishment attempt is considered when the RNC takes into account a need to establish a RB. If the RNC considers the need can not be satisfied, it refuses the RB establishment and does not send any RADIO BEARER SETUP message. The measurement is only incremented when the UE has one or several cells in its active set which are under the control of its SRNC.
D.
An integer value for each refusal cause. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Sub-counter # 3 ----> Invalid RB parameter value Unavailable downlink code resources Unavailable downlink power resources Unspecified
E.
VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeRessources VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerRessources VS.RadioBearerEstablishmentUnsuccess.Unspecified
F. G. H.
FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0603 Current counter specification introduced in V 2.0c
9.8.
A.
NUMBER OF REFUSED RADIO-BEARER ESTABLISHMENTS PER RNC

This measurement provides the number of RB establishment refusals before any sending of RRC RADIO BEARER SETUP, screened by establishment refusal cause, for each neighboring RNC.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 60/136

During such a procedure, the measurement attached to a given neighboring RNC is incremented as many times as there are cells in the active set which are controlled by this neighboring RNC. B. C. CC RB establishment attempt which has not evolved into the sending of a RADIO BEARER SETUP message. A RB establishment attempt is considered when the RNC takes into account a need to establish a RB. If the RNC considers the need can not be satisfied, it refuses the RB establishment and does not send any RADIO BEARER SETUP message. The measurement is only incremented when the UE has one or several cells in its active set which are outside the control of its SRNC. . D. An integer value for each refusal cause. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> E. Invalid RB parameter value Unavailable radio resource Unspecified
VS.RadioBearerEstablishmentUnsuccessNeighbRnc.InvalidRabParametersValue VS.RadioBearerEstablishmentUnsuccessNeighbRnc.ProblemRadioResource VS.RadioBearerEstablishmentUnsuccessNeighbRnc.Unspecified
F. G. H.
NeighboringRNC. Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0612 Counter introduced in V 2.0c
9.9.
A.
NUMBER OF FAILED RADIO-BEARER ESTABLISHMENTS PER CELL

This measurement provides the number of RB establishment failures, screened by establishment failure cause, for each cell controlled by the RNC. During such a procedure, the measurement attached to a given cell is incremented if the cell belongs to the active set of the involved UE.
B. C.
CC The measurement counts the number of RB establishment attempts which have evolved into the emission by the RNC of a RRC RADIO BEARER SETUP message
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 61/136

for which any subsequent RADIO BEARER SETUP COMPLETE message has been received.
The measurement is only incremented when the UE has one or several cells in its active set which are under the control of its SRNC. D. An integer value for each establishment failure cause. Screening: Sub-counter # 0 ----> Time-out expired without reception of a RADIO BEARER SETUP COMPLETE message or a RADIO BEARER SETUP FAILURE message. Reception of a RRC RADIO BEARER SETUP FAILURE message
Sub-counter # 1 ----> E.
VS.RadioBearerSetupUnsuccess.Timeout VS.RadioBearerSetupUnsuccess.RadioBearerSetupFailure
F. G. H.
FDD Cell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0602 Current counter specification introduced in V 2.0c
I.
Message flow
UE RADIO BEARER SETUP UTRAN
RADIO BEARER SETUP FAILURE
Radio Bearer Establishment, failure case
9.10. NUMBER OF FAILED RADIO-BEARER ESTABLISHMENTS PER RNC

A. This measurement provides the number of RB establishment failures, screened by establishment failure cause, 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 in the active set which are controlled by this neighboring RNC. B. CC
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 62/136

C. RB establishment attempt which has evolved into the emission by the RNC of a RRC RADIO BEARER SETUP message for which any subsequent RADIO BEARER SETUP COMPLETE message has been received
The measurement is only incremented when the UE has one or several cells in its active set which are outside the control of its SRNC. . D. An integer value for each establishment failure cause. Screening: Sub-counter # 0 ----> Time-out expired without reception of a RADIO BEARER SETUP COMPLETE message or a RADIO BEARER SETUP FAILURE message. Reception of a RRC RADIO BEARER SETUP FAILURE message
VS.RadioBearerSetupUnsuccessNeighbRnc.Timeout VS.RadioBearerSetupUnsuccessNeighbRnc.RadioBearerSetupFailure
F. G. H.
NeighboringRNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0611 Counter introduced in V 2.0c
I.
9.11. NUMBER OF SUCCESSFUL RADIO-BEARER RELEASES PER CELL

A. This measurement provides the number of successful radio bearer releases for each cell controlled by the RNC. During such a procedure, the measurement attached to a given cell is incremented if the cell belongs to the active set of the involved UE. B. C. CC Reception by the RNC of a RRC RADIO BEARER RELEASE COMPLETE message following the emission of a RRC RADIO BEARER RELEASE message. The measurement is only incremented when the UE has one or several cells in its active set which are under the control of its SRNC. D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening:
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 63/136

Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.RadioBearerReleaseSuccess.DL stratum conf 0 VS.RadioBearerReleaseSuccess.DL stratum conf 1 VS.RadioBearerReleaseSuccess.DL stratum conf 2 VS.RadioBearerReleaseSuccess.DL stratum conf 3 VS.RadioBearerReleaseSuccess.DL stratum conf 4 VS.RadioBearerReleaseSuccess.DL stratum conf 5 VS.RadioBearerReleaseSuccess.DL stratum conf 6 VS.RadioBearerReleaseSuccess.DL stratum conf 7 VS.RadioBearerReleaseSuccess.DL stratum conf 8 VS.RadioBearerReleaseSuccess.DL stratum conf 9 VS.RadioBearerReleaseSuccess.DL stratum conf 10
F. G. H.
I.
Message flow
UE RADIO BEARER RELEASE UTRAN
RADIO BEARER RELEASE COMPLETE
Radio Bearer Release, normal case
9.12. NUMBER OF SUCCESSFUL RADIO-BEARER RELEASES PER RNC

A. This measurement provides the number of successful radio bearer releases 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 in the active set which are controlled by this neighboring RNC. B. CC
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 64/136

C. Reception by the RNC of a RRC RADIO BEARER RELEASE COMPLETE message following the emission of a RRC RADIO BEARER RELEASE message. The event is only considered when the UE has one or several cells in its active set which are outside the control of its SRNC. . D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.RadioBearerReleaseSuccess.DL stratum conf 0 VS.RadioBearerReleaseSuccess.DL stratum conf 1 VS.RadioBearerReleaseSuccess.DL stratum conf 2 VS.RadioBearerReleaseSuccess.DL stratum conf 3 VS.RadioBearerReleaseSuccess.DL stratum conf 4 VS.RadioBearerReleaseSuccess.DL stratum conf 5 VS.RadioBearerReleaseSuccess.DL stratum conf 6 VS.RadioBearerReleaseSuccess.DL stratum conf 7 VS.RadioBearerReleaseSuccess.DL stratum conf 8 VS.RadioBearerReleaseSuccess.DL stratum conf 9 VS.RadioBearerReleaseSuccess.DL stratum conf 10
F. G. H.
NeighboringRNC. Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0613 Counter introduced in V 2.0e
I.
9.13. NUMBER OF FAILED RADIO-BEARER RELEASES PER CELL

A. This measurement provides the number of RB release failures screened by release failure cause, for each cell controlled by the RNC. During such a procedure, the measurement attached to a given cell is incremented if the cell belongs to the active set of the involved UE. B. C. CC The measurement counts the number of emissions by the RNC of a RRC RADIO BEARER RELEASE message for which any subsequent RADIO BEARER RELEASE COMPLETE message has been received.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 65/136

The measurement is only incremented when the UE has one or several cells in its active set which are under the control of its SRNC. D. An integer value for each release failure cause. Screening: Sub-counter # 0 ----> Time-out expired without reception of a RADIO BEARER RELEASE COMPLETE message or a RADIO BEARER RELEASE FAILURE message. Reception of a RRC RADIO BEARER RELEASE FAILURE message
VS.RadioBearerReleaseUnsuccess.Timeout VS.RadioBearerReleaseUnsuccess.RadioBearerReleaseFailure
F. G. H.
FDD Cell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0609 Counter introduced in V 2.0c
I.
Message flow
UE RADIO BEARER RELEASE
UTRAN
RADIO BEARER RELEASE FAILURE
Radio Bearer Release, failure case
9.14. NUMBER OF FAILED RADIO-BEARER RELEASES PER RNC

A. This measurement provides the number of RB release failures screened by release failure cause, 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 in the active set which are controlled by this neighboring RNC. B. C. CC Emission by the RNC of a RRC RADIO BEARER RELEASE message for which any subsequent RADIO BEARER RELEASE COMPLETE message has been received. The event is only considered when the UE has one or several cells in its active set which are outside the control of its SRNC. .
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 66/136

D. An integer value for each release failure cause. Screening: Sub-counter # 0 ----> Time-out expired without reception of a RADIO BEARER RELEASE COMPLETE message or a RADIO BEARER RELEASE FAILURE message. Reception of a RRC RADIO BEARER RELEASE FAILURE message
VS.RadioBearerReleaseUnsuccessNeighbRnc.Timeout VS.RadioBearerReleaseUnsuccessNeighbRnc.RadioBearerReleaseFailure
F. G. H.
NeighboringRNC. Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0614 Counter introduced in V 2.0e
I.
9.15. NUMBER OF SUCCESSFUL RADIO-BEARER RECONFIGURATIONS PER CELL

A. This measurement provides the number of successful radio bearer reconfigurations for each cell controlled by the RNC. During such a procedure, the measurement attached to a given cell is incremented if the cell belongs to the active set of the involved UE. B. C. CC Reception by the RNC of a RRC RADIO BEARER RECONFIGURATION COMPLETE message following the emission of a RRC RADIO BEARER RECONFIGURATION message. The measurement is only incremented when the UE has one or several cells in its active set which are under the control of its SRNC. D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.RadioBearerReconfigSuccess.DL stratum conf 0 VS.RadioBearerReconfigSuccess.DL stratum conf 1 VS.RadioBearerReconfigSuccess.DL stratum conf 2 VS.RadioBearerReconfigSuccess.DL stratum conf 3 VS.RadioBearerReconfigSuccess.DL stratum conf 4
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 67/136

VS.RadioBearerReconfigSuccess.DL stratum conf 5 VS.RadioBearerReconfigSuccess.DL stratum conf 6 VS.RadioBearerReconfigSuccess.DL stratum conf 7 VS.RadioBearerReconfigSuccess.DL stratum conf 8 VS.RadioBearerReconfigSuccess.DL stratum conf 9 VS.RadioBearerReconfigSuccess.DL stratum conf 10 F. G. H. FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0615 Counter introduced in V 2.0e I. Message flow
UE
UTRAN
RADIO BEARER RECONFIGURATION
RADIO BEARER RECONFIGURATION COMPLETE
Radio bearer reconfiguration, normal flow
9.16. NUMBER OF SUCCESSFUL RADIO-BEARER RECONFIGURATIONS PER RNC

A. This measurement provides the number of successful radio bearer reconfigurations 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 in the active set which are controlled by this neighboring RNC. B. C. CC Failure or time-out after RB set-up, addition or reconfiguration which entails the last Radiobearer of a call releasing. The measurement is only incremented when the UE has a reference cell outside the control of the RNC in charge of the measurement. D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening:
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 68/136

Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 0 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 1 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 2 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 3 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 4 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 5 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 6 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 7 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 8 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 9 VS.RadioBearerReconfigSuccessNeighbRnc.DL stratum conf 10
F. G. H.
NeighboringRNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0617 Counter introduced in V 2.0e
I.
9.17. NUMBER OF FAILED RADIO-BEARER RECONFIGURATIONS PER CELL

A. This measurement provides the number of RB reconfiguration failures screened by release failure cause, for each cell controlled by the RNC. During such a procedure, the measurement attached to a given cell is incremented if the cell belongs to the active set of the involved UE. B. C. CC Emission by the RNC of a RRC RADIO BEARER RECONFIGURATION message for which any subsequent RADIO BEARER RECONFIGURATION COMPLETE message has been received. The measurement is only incremented when the UE has one or several cells in its active set which are under the control of its SRNC. D. An integer value for each reconfiguration failure cause.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 69/136

Screening: Sub-counter # 0 ----> Time-out expired without reception of a RADIO BEARER RECONFIGURATION COMPLETE message or a RADIO BEARER RECONFIGURATION FAILURE message. Reception of a RRC RADIO BEARER RECONFIGURATION FAILURE message
VS.RadioBearerReconfigUnsuccess.Timeout VS.RadioBearerReconfigUnsuccess.RadioBearerReconfigurationFailure
F. G. H.
FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0616 Counter introduced in V 2.0e
I.
Message flow
UE
UTRAN
RADIO BEARER RECONFIGURATION
RADIO BEARER RECONFIGURATION FAILURE
Radio bearer reconfiguration, failure case
9.18. NUMBER OF FAILED RADIO-BEARER RECONFIGURATIONS PER RNC

A. This measurement provides the number of RB reconfiguration failures screened by release failure cause, 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 in the active set which are controlled by this neighboring RNC. B. C. CC Emission by the RNC of a RRC RADIO BEARER RECONFIGURATION message for which any subsequent RADIO BEARER RECONFIGURATION COMPLETE message has been received. The measurement is only incremented when the UE has a reference cell outside the control of the RNC in charge of the measurement.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 70/136

D. An integer value for each reconfiguration failure cause. Screening: Sub-counter # 0 ----> Time-out expired without reception of a RADIO BEARER RECONFIGURATION COMPLETE message or a RADIO BEARER RECONFIGURATION FAILURE message. Reception of a RRC RADIO BEARER RECONFIGURATION FAILURE message
VS.RadioBearerReconfigUnsuccessNeighbRnc.Timeout VS.RadioBearerReconfigUnsuccessNeighbRnc.RadioBearerReconfigurationFailure
F. G. H.
I.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 71/136
10. RNSAP RADIO-LINK MANAGEMENT

10.1. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK SETUPS
A. This measurement provides the number of radio-links successfully setup on a RNSAP point of view, screened by Downlink Access Stratum configuration. B. CC C. Emission of a RADIO LINK SETUP RESPONSE or RADIO LINK SETUP FAILURE RNSAP message sent by the Drift RNC to the Serving RNC in response to a RADIO LINK SETUP REQUEST message. The measurement considers each Radio Link mentioned as set-up in the RADIO LINK SETUP RESPONSE or RADIO LINK SETUP FAILURE RNSAP message. D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 0 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 1 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 2 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 3 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 4 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 5 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 6 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 7 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 8 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 9 VS.IurDrncRadioLinkSetupSuccess.DL stratum conf 10
F. FDDCell G. Valid for circuit switched and packet switched traffic H. NORTEL specified counter NORTEL # 1301 Counter introduced in V 2.0c I. Message flow
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 72/136
SRNC
RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE
DRNC
Radio Link Setup procedure: Successful Operation
10.2. NUMBER OF FAILED RNSAP RADIO-LINK SETUPS

A. B. C This measurement provides the number of radio links failed in setup on a RNSAP point of view, screened by set-up failure cause. CC This measurement is based on two different events: 1) Emission of a RNSAP RADIO LINK SETUP FAILURE message by the Drift RNC to the Serving RNC in response to a RADIO LINK SETUP REQUEST message. The measurement considers each Radio Link referred as failed in the RNSAP RADIO LINK SETUP FAILURE message. 2) Time-out expired without emission of a RADIO LINK SETUP RESPONSE message or RADIO LINK SETUP FAILURE message. The measurement considers each Radio Link required to set-up in the RNSAP RADIO LINK SETUP REQUEST message. D. An integer value for each set-up failure cause Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Sub-counter # 3 ----> E. Unspecified No radio resource (RNC internal cause) NBAP refusal (NBAP failure cause) Requested configuration not supported (RNSAP failure cause)
VS.IurDrncRadioLinkSetupUnsuccess.Unspecified VS.IurDrncRadioLinkSetupUnsuccess.NoRadioResource VS.IurDrncRadioLinkSetupUnsuccess.NbapRefusal VS.IurDrncRadioLinkSetupUnsuccess.ReqConfigUnsupported
F. FDDCell G. Valid for circuit switched and packet switched traffic H. NORTEL specified counter NORTEL # 1302 Counter introduced in V 2.0c I. Message flow
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 73/136
SRNC
RADIO LINK SETUP REQUEST RADIO LINK SETUP FAILURE
DRNC
Radio Link Setup procedure: Unsuccessful Operation
10.3. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK ADDITIONS

A. B. C. This measurement provides the number of radio-links successfully added on a RNSAP point of view, screened by Downlink Access Stratum configuration. CC Emission of a RADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION FAILURE RNSAP message by the Drift RNC to the Serving RNC in response to a RADIO LINK SETUP REQUEST message. The measurement considers each Radio Link mentioned as added in the RADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION FAILURE RNSAP message. D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 0 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 1 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 2 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 3 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 4 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 5 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 6 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 7 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 8 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 9 VS.IurDrncRadioLinkAdditionSuccess.DL stratum conf 10
F. G. H.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 74/136

I. Message flow
SRNC
DRNC
RADIO LINK ADDITION RESPONSE
Radio Link Addition procedure: Successful Operation
10.4. NUMBER OF FAILED RNSAP RADIO-LINK ADDITIONS

A. B. C. This measurement provides the number of radio links failed in addition on a RNSAP point de view, screened by addition failure cause. CC This measurement is based on two different events: 1) Emission of a RNSAP RADIO LINK ADDITION FAILURE message by the Drift RNC to the Serving RNC in response to a RADIO LINK ADDITION REQUEST message. The measurement considers each Radio Link referred as failed in the RNSAP RADIO LINK ADDITION FAILURE message. 2) Time-out expired without emission of a RADIO LINK ADDITION RESPONSE message or a RADIO LINK ADDITION FAILURE message. The measurement considers each Radio Link required to addition in the RNSAP RADIO LINK ADDITION REQUEST message. D. An integer value for each addition failure cause Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Sub-counter # 3 ----> E. Unspecified No radio resource (RNC internal cause) NBAP refusal (NBAP failure cause) Requested configuration not supported (RNSAP failure cause)
VS.IurDrncRadioLinkAdditionUnsuccess.Unspecified VS.IurDrncRadioLinkAdditionUnsuccess.NoRadioResource VS.IurDrncRadioLinkAdditionUnsuccess.NbapRefusal VS.IurDrncRadioLinkAdditionUnsuccess.ReqConfigUnsupported
F. G. H.
FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 75/136

NORTEL # 1304 Counter introduced in V 2.0c I. Message flow
SRNC
DRNC
RADIO LINK ADDITION FAILURE
Radio Link Addition procedure: Unsuccessful Operation
10.5. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK DELETIONS

A. B. C. This measurement provides the number of radio-links successfully deleted on a RNSAP point of view. CC Emission of a RNSAP RADIO LINK DELETION RESPONSE message by the Drift RNC to the Serving RNC in response to a RADIO LINK DELETION REQUEST. The measurement considers each Radio Link referred in the RNSAP RADIO LINK DELETION RESPONSE message D. A single integer value. Screening = NO E. F. G. H. VS.IurDrncRadioLinkDeletionSuccess FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1306 Counter introduced in V 2.0c I. Message flow
SRNC
RADIO LINK DELETION REQUEST
DRNC
RADIO LINK DELETION RESPONSE
Radio Link Deletion procedure: Successful Operation
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 76/136
10.6. NUMBER OF SUCCESSFUL RNSAP RADIO-LINK RECONFIGURATION PREPARATIONS

A. B. C. This measurement provides the number of radio-links successfully prepared for reconfiguration , screened by Downlink Access Stratum configuration. CC Emission of RNSAP RADIO LINK RECONFIGURATION READY message. The measurement considers each Radio Link referred in the RNSAP RADIO LINK RECONFIGURATION READY message. D. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 0 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 1 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 2 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 3 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 4 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 5 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 6 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 7 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 8 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 9 VS.IurDrncRadioLinkReconfigPrepareSuccess.DL stratum conf 10
F. G. H.
I.
Message flow
SRNC
RADIO LINK RECONFIGURATION READY
DRNC
Synchronised Radio Link Reconfiguration Preparation procedure, Successful Operation
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 77/136
10.7. NUMBER OF FAILED RNSAP RADIO-LINK RECONFIGURATION PREPARATIONS

A. B. C. This measurement provides the number of radio links failed in reconfiguration preparation on a RNSAP point of view, screened by cause of reconfiguration preparation failure. CC Emission of a RNSAP RADIO LINK RECONFIGURATION FAILURE message by the Drift RNC to the Serving RNC in response to a RADIO LINK RECONFIGURATION PREPARE message or no reception of RADIO LINK RECONFIGURATION READY message before a time-out An integer value for each cause of reconfiguration preparation failure. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Sub-counter # 3 ----> E. Unspecified No radio resource (RNC internal cause) NBAP refusal (NBAP failure cause) Requested configuration not supported (RNSAP failure cause)
E.
VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.Unspecified VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.NoRadioResource VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.NbapRefusal VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.ReqConfigUnsupported
F. G. H.
I.
Message flow
SRNC
DRNC
RADIO LINK RECONFIGURATION PREPARE RADIO LINK RECONFIGURATION FAILURE
Synchronised Radio Link Reconfiguration Preparation procedure, Unsuccessful Operation
10.8. NUMBER OF RNSAP RADIO-LINK RECONFIGURATION CANCELS

A. This measurement provides the number of RNSAP RADIO LINK RECONFIGURATION CANCEL messages.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 78/136

B. C. D. CC Reception of a RNSAP RADIO LINK RECONFIGURATION CANCEL message by the drift RNC from the serving RNC. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 0 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 1 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 2 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 3 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 4 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 5 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 6 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 7 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 8 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 9 VS.IurDrncRadioLinkReconfigCancelSuccess.DL stratum conf 10
F. G. H.
I.
Message flow
SRNC
RADIO LINK RECONFIGURATION CANCEL
DRNC
Synchronised Radio Link Reconfiguration Cancellation procedure, Successful Operation
10.9. NUMBER OF RNSAP RADIO-LINK RECONFIGURATION COMMITS

A. B. This measurement provides the number of RNSAP RADIO LINK RECONFIGURATION COMMIT messages. CC
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 79/136

C. D. Reception of a RNSAP RADIO LINK RECONFIGURATION COMMIT message by the Drift RNC from the Serving RNC. A single integer value for each DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 0 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 1 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 2 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 3 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 4 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 5 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 6 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 7 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 8 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 9 VS.IurDrncRadioLinkReconfigCommitSuccess.DL stratum conf 10
F. G. H.
I.
Message flow
SRNC
RADIO LINK RECONFIGURATION COMMIT
DRNC
Synchronised Radio Link Reconfiguration Commit procedure, Successful Operation
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 80/136
11. PAGING
11.1. NUMBER OF RECEIVED PAGING REQUESTS
A. B. C. D. This measurement provides the number of received paging requests screened by Core Network domain CC Reception by the RNC of a RANAP PAGING message from the Core Network. An integer value for each Core Network domain. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> E. Circuit Switched Packet Switched
VS.ReceivedPagingRequest.WithCoreNetworkCs VS.ReceivedPagingRequest.WithCoreNetworkPs
F. G. H.
RNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 0801 Counter introduced in V 1.2.b
I.
Message flow
RNC PAGING
CN
Paging procedure. Successful operation.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 81/136
12. POWER MANAGEMENT

12.1. AVERAGE CELL POWER USED FOR SPEECH CALLS 12.1.1 AVERAGE CELL POWER USED FOR SPEECH CALLS
A. B. This measurement provides the average cell power used for speech calls. DER NORTEL VAL type counter C. D. E. F. G. H. The average cell power used for speech calls is updated on each addition/deletion of a radiolink supporting a speech call. A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForSpeech.Avg FDDCell N/A NORTEL specified counter NORTEL # 0301 Counter introduced in V 1.2.b
12.1.2 MINIMUM CELL POWER USED FOR SPEECH CALLS

A. B. This measurement provides the minimum cell power used for speech calls. DER NORTEL VAL type counter C. D. E. F. G. H. The minimum cell power used for speech calls is reconsidered on each addition/deletion of a radio-link supporting a speech call. A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForSpeech.Min FDDCell N/A NORTEL specified counter NORTEL # 0301 Counter introduced in V 1.2.b
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 82/136
12.1.3 MAXIMUM CELL POWER USED FOR SPEECH CALLS

A. B. This measurement provides the maximum cell power used for speech calls. DER NORTEL VAL type counter C. D. E. F. G. H. The maximum cell power used for speech calls is reconsidered on each addition/deletion of a radio-link supporting a speech call. A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForSpeech.Max FDDCell N/A NORTEL specified counter NORTEL # 0301 Counter introduced in V 1.2.b
12.2.
CELL POWER USED FOR DATA CALLS
12.2.1 AVERAGE CELL POWER USED FOR DATA CALLS

A. B. This measurement provides the average cell power used for data calls. DER NORTEL VAL type counter C. D. E. F. G. H. The average cell power used for data calls is updated on each addition/deletion of a radio-link supporting a data call. A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForData.Avg FDDCell N/A NORTEL specified counter NORTEL # 0302 Counter introduced in V 1.2.b
12.2.2 MINIMUM CELL POWER USED FOR DATA CALLS

A. This measurement provides the minimum cell power used for data calls.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 83/136

B. DER NORTEL VAL type counter C. D. E. F. G. H. The minimum cell power used for data calls is reconsidered on each addition/deletion of a radio-link supporting a data call. A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForData.Min FDDCell N/A NORTEL specified counter NORTEL # 0302 Counter introduced in V 1.2.b
12.2.3 MAXIMUM CELL POWER USED FOR DATA CALLS

A. B. This measurement provides the maximum cell power used for data calls. DER NORTEL VAL type counter C. D. E. F. G. H. The maximum cell power used for data calls is reconsidered on each addition/deletion of a radio-link supporting a data call. A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForData.Max FDDCell N/A NORTEL specified counter NORTEL # 0302 Counter introduced in V 1.2.b
12.3. AVERAGED POWER USED FOR SIGNALLING
12.3.1 AVERAGED POWER USED FOR SIGNALLING

A. B. This measurement provides the Averaged cell power used for signalling. DER NORTEL VAL type counter C. The average cell power used for signalling is updated on each addition/deletion of a radio-link
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 84/136

D. E. F. G. H. A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForSignalling.Avg FDDCell N/A NORTEL specified counter NORTEL # 0304 Counter introduced in V 2.0c
12.3.2 MINIMUM POWER USED FOR SIGNALLING

A. B. This measurement provides the minimum cell power used for signalling. DER NORTEL VAL type counter C. D. E. F. G. H. The minimum cell power used for signalling is reconsidered on each addition/deletion of a radio-link A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForSignalling.Min FDDCell N/A NORTEL specified counter NORTEL # 0304 Counter introduced in V 2.0c
12.3.3 MAXIMUM CELL POWER USED FOR SIGNALLING

A. B. This measurement provides the maximum cell power used for signalling. DER NORTEL VAL type counter C. D. E. F. G. H. The maximum cell power used for signalling is updated on each addition/deletion of a radiolink A single integer value expressed in units of 0.1 mW VS.AveragePowerUsedForSignalling.Max FDDCell N/A NORTEL specified counter NORTEL # 0304
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 85/136

Counter introduced in V 2.0c
12.4. UPLINK RSSI 12.4.1 AVERAGED UPLINK RSSI

A. B. This measurement provides the Averaged uplink RSSI per cell. DER NORTEL VAL type counter C. D. E. F. G. H. The Averaged uplink RSSI is updated on each reception on a NBAP common measurement A single integer value expressed in 10-11.2 mW VS.UplinkRssi.Avg FDDCell N/A NORTEL specified counter NORTEL # 0303 Counter introduced in V 2.0c
12.4.2 MINIMUM UPLINK RSSI

A. B. This measurement provides the minimum uplink RSSI per cell. DER NORTEL VAL type counter C. D. E. F. G. H. The minimum uplink RSSI is updated on each reception on a NBAP common measurement A single integer value expressed in 10-11.2 mW VS.UplinkRssi.Min FDDCell N/A NORTEL specified counter NORTEL # 0303 Counter introduced in V 2.0c
12.4.3 MAXIMUM UPLINK RSSI

A. B. This measurement provides the maximum uplink RSSI per cell. DER NORTEL VAL type counter
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 86/136

C. D. E. F. G. H. The maximum uplink RSSI is updated on each reception on a NBAP common measurement A single integer value expressed in 10-11.2 mW VS.UplinkRssi.Max FDDCell N/A NORTEL specified counter NORTEL # 0303 Counter introduced in V 2.0c
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 87/136
13. QUALITY OF SERVICE

13.1. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 1 PER CELL
A. This measurement provides the number of downsizing step 1 successes, screened by Downlink Access Stratum Configuration, for each cell controlled by the RNC. The measurement attached to a given cell is incremented if the cell is the reference cell of the involved UE. B. C. CC Successful implementation of an Always On algorithm decision to downgrade the UE capabilities to the Always On radio-configuration. It is stated on reception of a RRC RB RECONFIGURATION COMPLETE message consistent with the required downgraded capabilities. The measurement is only incremented when the UE has a reference cell under the control of the RNC in charge of the measurement. D. A single integer value for each source DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.DownsizingStep1Success.DL stratum conf 0 VS.DownsizingStep1Success.DL stratum conf 1 VS.DownsizingStep1Success.DL stratum conf 2 VS.DownsizingStep1Success.DL stratum conf 3 VS.DownsizingStep1Success.DL stratum conf 4 VS.DownsizingStep1Success.DL stratum conf 5 VS.DownsizingStep1Success.DL stratum conf 6 VS.DownsizingStep1Success.DL stratum conf 7 VS.DownsizingStep1Success.DL stratum conf 8 VS.DownsizingStep1Success.DL stratum conf 9 VS.DownsizingStep1Success.DL stratum conf 10
F.
FDDCell Related to the reference cell Valid for circuit switched and packet switched traffic NORTEL specified counter
G. H.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 88/136

NORTEL # 1101 Counter introduced in V 2.0e
13.2. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 1 PER RNC

A. This measurement provides the number of downsizing step 1 successes, screened by Downlink Access Stratum Configuration, for each neighboring RNC. The measurement attached to a neighboring RNC is incremented if the neighboring RNC controls the reference cell of the involved UE. B. C. CC Successful implementation of an Always On algorithm decision to downgrade the UE capabilities to the Always On radio-configuration. It is stated on reception of a RRC RB RECONFIGURATION COMPLETE message consistent with the required downgraded capabilities. The measurement is only incremented when the UE has a reference cell outside the control of the RNC in charge of the measurement. D. A single integer value for each source DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 0 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 1 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 2 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 3 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 4 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 5 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 6 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 7 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 8 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 9 VS.DownsizingStep1SuccessNeighbRnc.DL stratum conf 10
F. G. H.
Neighboring RNC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1102 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 89/136
13.3. NUMBER OF UNSUCCESSFUL DOWNSIZINGS STEP 1 PER CELL

A. This measurement provides the number of unsuccessful downsizing step 1, screened by Downlink Access Stratum Configuration, for each cell controlled by the RNC. The measurement attached to a given cell is incremented if the cell is the reference cell of the involved UE. B. C. CC Unsuccessful implementation of an Always On algorithm decision to downgrade the UE capabilities to the Always On radio-configuration e.g. reception of a RRC RB RECONFIGURATION FAILURE message. The measurement is only incremented when the UE has a reference cell under the control of the RNC in charge of the measurement. D. A single integer value for each source DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.DownsizingStep1Unsuccess.DL stratum conf 0 VS.DownsizingStep1Unsuccess.DL stratum conf 1 VS.DownsizingStep1Unsuccess.DL stratum conf 2 VS.DownsizingStep1Unsuccess.DL stratum conf 3 VS.DownsizingStep1Unsuccess.DL stratum conf 4 VS.DownsizingStep1Unsuccess.DL stratum conf 5 VS.DownsizingStep1Unsuccess.DL stratum conf 6 VS.DownsizingStep1Unsuccess.DL stratum conf 7 VS.DownsizingStep1Unsuccess.DL stratum conf 8 VS.DownsizingStep1Unsuccess.DL stratum conf 9 VS.DownsizingStep1Unsuccess.DL stratum conf 10
F.
FDDCell Related to the reference cell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1103 Counter introduced in V 2.0e
G. H.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 90/136
13.4. NUMBER OF UNSUCCESSFUL DOWNSIZINGS STEP 1 PER RNC

A. This measurement provides the number of unsuccessful downsizing step 1, screened by Downlink Access Stratum Configuration, for each neighboring RNC. The measurement attached to a neighboring RNC is incremented if the neighboring RNC controls the reference cell of the involved UE. B. C. CC Unsuccessful implementation of an Always On algorithm decision to downgrade the UE capabilities to the Always On radio-configuration e.g. reception of a RRC RB RECONFIGURATION FAILURE message. The measurement is only incremented when the UE has a reference cell outside the control of the RNC in charge of the measurement. D. A single integer value for each source DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 0 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 1 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 2 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 3 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 4 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 5 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 6 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 7 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 8 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 9 VS.DownsizingStep1UnsuccessNeighbRnc.DL stratum conf 10
F. G. H.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 91/136
13.5. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 2 PER CELL

A. This measurement provides the number of downsizing step 2 successes, screened by Downlink Access Stratum Configuration, for each cell controlled by the RNC. The measurement attached to a given cell is incremented if the cell is the reference cell of the involved UE. B. C. CC Successful implementation of an Always On algorithm decision to release an UE call due to the UE inactivity. It is stated on reception of a RRC RRC RELEASE COMPLETE message for User inactivity reason. The measurement is only incremented when the UE has a reference cell under the control of the RNC in charge of the measurement. D. A single integer value for each source DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.DownsizingStep2Success.DL stratum conf 0 VS.DownsizingStep2Success.DL stratum conf 1 VS.DownsizingStep2Success.DL stratum conf 2 VS.DownsizingStep2Success.DL stratum conf 3 VS.DownsizingStep2Success.DL stratum conf 4 VS.DownsizingStep2Success.DL stratum conf 5 VS.DownsizingStep2Success.DL stratum conf 6 VS.DownsizingStep2Success.DL stratum conf 7 VS.DownsizingStep2Success.DL stratum conf 8 VS.DownsizingStep2Success.DL stratum conf 9 VS.DownsizingStep2Success.DL stratum conf 10
F.
G. H.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 92/136
13.6. NUMBER OF SUCCESSFUL DOWNSIZINGS STEP 2 PER RNC

A. This measurement provides the number of downsizing step 2 successes, screened by Downlink Access Stratum Configuration, for each neighboring RNC. The measurement attached to a neighboring RNC is incremented if the neighboring RNC controls the reference cell of the involved UE. B. C. CC Successful implementation of an Always On algorithm decision to release an UE call due to the UE inactivity. It is stated on reception of a RRC RRC RELEASE COMPLETE message for User inactivity reason. The measurement is only incremented when the UE has a reference cell outside the control of the RNC in charge of the measurement. D. A single integer value for each source DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 0 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 1 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 2 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 3 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 4 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 5 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 6 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 7 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 8 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 9 VS.DownsizingStep2SuccessNeighbRnc.DL stratum conf 10
F. G. H.
13.7. NUMBER OF SUCCESSFUL UPSIZINGS PER CELL

A. This measurement provides the number of successful upsizings, screened by Downlink Access Stratum Configuration, for each cell controlled by the RNC.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 93/136

The measurement attached to a given cell is incremented if the cell is the reference cell of the involved UE. B. C. CC Successful implementation of an Always On algorithm decision to restore the full UE capabilities It is stated on reception of a RRC RB RECONFIGURATION COMPLETE message consistent with the required upgraded capabilities. The measurement is only incremented when the UE has a reference cell under the control of the RNC in charge of the measurement. D. A single integer value for each target DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.UpsizingSuccess.DL stratum conf 0 VS.UpsizingSuccess.DL stratum conf 1 VS.UpsizingSuccess.DL stratum conf 2 VS.UpsizingSuccess.DL stratum conf 3 VS.UpsizingSuccess.DL stratum conf 4 VS.UpsizingSuccess.DL stratum conf 5 VS.UpsizingSuccess.DL stratum conf 6 VS.UpsizingSuccess.DL stratum conf 7 VS.UpsizingSuccess.DL stratum conf 8 VS.UpsizingSuccess.DL stratum conf 9 VS.UpsizingSuccess.DL stratum conf 10
F.
G. H.
13.8. NUMBER OF SUCCESSFUL UPSIZINGS PER RNC

A. This measurement provides the number of successful upsizings, screened by Downlink Access Stratum Configuration, for each neighboring RNC. The measurement attached to a neighboring RNC is incremented if the neighboring RNC controls the reference cell of the involved UE.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 94/136

B. C. CC Successful implementation of an Always On algorithm decision to restore the full UE capabilities It is stated on reception of a RRC RB RECONFIGURATION COMPLETE message consistent with the required upgraded capabilities. The measurement is only incremented when the UE has a reference cell outside the control of the RNC in charge of the measurement. D. A single integer value for each target DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.UpsizingSuccessNeighbRnc.DL stratum conf 0 VS.UpsizingSuccessNeighbRnc.DL stratum conf 1 VS.UpsizingSuccessNeighbRnc.DL stratum conf 2 VS.UpsizingSuccessNeighbRnc.DL stratum conf 3 VS.UpsizingSuccessNeighbRnc.DL stratum conf 4 VS.UpsizingSuccessNeighbRnc.DL stratum conf 5 VS.UpsizingSuccessNeighbRnc.DL stratum conf 6 VS.UpsizingSuccessNeighbRnc.DL stratum conf 7 VS.UpsizingSuccessNeighbRnc.DL stratum conf 8 VS.UpsizingSuccessNeighbRnc.DL stratum conf 9 VS.UpsizingSuccessNeighbRnc.DL stratum conf 10
F. G. H.
13.9. NUMBER OF UNSUCCESSFUL UPSIZINGS PER CELL

A. This measurement provides the number of unsuccessful upsizings, screened by Downlink Access Stratum Configuration, for each cell controlled by the RNC. The measurement attached to a given cell is incremented if the cell is the reference cell of the involved UE. B. C. CC Unsuccessful implementation of an Always On algorithm decision to restore the full UE capabilities. e.g. reception of a RRC RB RECONFIGURATION FAILURE message.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 95/136

The measurement is only incremented when the UE has a reference cell under the control of the RNC in charge of the measurement. D. A single integer value for each target DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.UpsizingUnsuccess.DL stratum conf 0 VS.UpsizingUnsuccess.DL stratum conf 1 VS.UpsizingUnsuccess.DL stratum conf 2 VS.UpsizingUnsuccess.DL stratum conf 3 VS.UpsizingUnsuccess.DL stratum conf 4 VS.UpsizingUnsuccess.DL stratum conf 5 VS.UpsizingUnsuccess.DL stratum conf 6 VS.UpsizingUnsuccess.DL stratum conf 7 VS.UpsizingUnsuccess.DL stratum conf 8 VS.UpsizingUnsuccess.DL stratum conf 9 VS.UpsizingUnsuccess.DL stratum conf 10
F.
G. H.
13.10. NUMBER OF UNSUCCESSFUL UPSIZINGS PER RNC

A. This measurement provides the number of unsuccessful upsizings, screened by Downlink Access Stratum Configuration, for each neighboring RNC. The measurement attached to a neighboring RNC is incremented if the neighboring RNC controls the reference cell of the involved UE. B. C. CC Unsuccessful implementation of an Always On algorithm decision to restore the full UE capabilities e.g. reception of a RRC RB RECONFIGURATION FAILURE message. The measurement is only incremented when the UE has a reference cell outside the control of the RNC in charge of the measurement. D. A single integer value for each target DL Access Stratum configuration (c.f. Annexe 1).
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 96/136

Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 0 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 1 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 2 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 3 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 4 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 5 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 6 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 7 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 8 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 9 VS.UpsizingUnsuccessNeighbRnc.DL stratum conf 10
F. G. H.
13.11. NUMBER OF SUCCESSFUL IRM SCHEDULING DOWNGRADINGS PER CELL

A. This measurement provides the number of successful RB throughput downgradings performed by the iRM scheduling feature (FRS # 22522), screened by Downlink Access Stratum Configuration, for the current reference cell of the UE. Considered DLASConfigurations are the DLASConfigurations after throughput downgrading B. C. D. CC Successful establishment of the downgraded throughput. A single integer value for each target DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IRMSchedulingDowngradedSuccess.DL stratum conf 0 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 1 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 2 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 3
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 97/136

VS.IRMSchedulingDowngradedSuccess.DL stratum conf 4 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 5 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 6 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 7 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 8 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 9 VS.IRMSchedulingDowngradedSuccess.DL stratum conf 10 F. FDDCell Related to the reference cell Valid for packet switched traffic NORTEL specified counter NORTEL # 1120 Counter introduced in V2.1
G. H.
13.12. NUMBER OF FAILED IRM SCHEDULING DOWNGRADINGS PER CELL

A. This measurement provides the number of failed RB throughput downgradings encountered by the iRM scheduling feature (FRS # 22522), screened by Downlink Access Stratum Configuration, for the current reference cell of the UE. Considered DLASConfigurations are the DLASConfigurations after throughput downgrading B. C. D. CC Failed establishment of the downgraded throughput. A single integer value for each target DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IRMSchedulingDowngradedFailure.DL stratum conf 0 VS.IRMSchedulingDowngradedFailure.DL stratum conf 1 VS.IRMSchedulingDowngradedFailure.DL stratum conf 2 VS.IRMSchedulingDowngradedFailure.DL stratum conf 3 VS.IRMSchedulingDowngradedFailure.DL stratum conf 4 VS.IRMSchedulingDowngradedFailure.DL stratum conf 5 VS.IRMSchedulingDowngradedFailure.DL stratum conf 6 VS.IRMSchedulingDowngradedFailure.DL stratum conf 7 VS.IRMSchedulingDowngradedFailure.DL stratum conf 8
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 98/136

VS.IRMSchedulingDowngradedFailure.DL stratum conf 9 VS.IRMSchedulingDowngradedFailure.DL stratum conf 10 F. FDDCell Related to the reference cell Valid for packet switched traffic NORTEL specified counter NORTEL # 1121 Counter introduced in V2.1
G. H.
13.13. NUMBER OF SUCCESSFUL IRM SCHEDULING DOWNGRADINGS PER RNC

A. This measurement provides the number of successful RB throughput downgradings performed by the iRM scheduling feature (FRS # 22522), screened by Downlink Access Stratum Configuration, for each neighboring RNC. The measurement attached to a given neighboring RNC is incremented each time a success on a RB throughput downgrading is detected on a UE which current reference cell is controlled by the neighboring RNC. Considered DLASConfigurations are the DLASConfigurations after throughput downgrading B. C. D. CC Successful establishment of the downgraded throughput. A single integer value for each target DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 0 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 1 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 2 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 3 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 4 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 5 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 6 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 7 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 8 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 9 VS.IRMSchedulingDowngradedSuccessNeighbRnc.DL stratum conf 10
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 99/136

F. G. H. NeighboringRNC Valid for packet switched traffic NORTEL specified counter NORTEL # 1122 Counter introduced in V2.1
13.14. NUMBER OF FAILED IRM SCHEDULING DOWNGRADINGS PER RNC

A. This measurement provides the number of failed RB throughput downgradings encountered by the iRM scheduling feature (FRS # 22522), screened by Downlink Access Stratum Configuration, for each neighboring RNC. The measurement attached to a given neighboring RNC is incremented each time a failure on a RB throughput downgrading is detected on a UE which current reference cell is controlled by the neighboring RNC. Considered DLASConfigurations are the DLASConfigurations after throughput downgrading B. C. D. CC Failed establishment of the downgraded throughput. A single integer value for each target DL Access Stratum configuration (c.f. Annexe 1). Screening: Sub-counter # i ----> E. Downlink Access Stratum configuration # i for i = 0 to 10
VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 0 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 1 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 2 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 3 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 4 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 5 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 6 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 7 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 8 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 9 VS.IRMSchedulingDowngradedFailureNeighbRnc.DL stratum conf 10
F. G. H.
NeighboringRNC Valid for packet switched traffic NORTEL specified counter

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

NORTEL # 1123 Counter introduced in V2.1
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 101/136
14. USER PLANE TRAFFIC

14.1. TOTAL COUNT OF UPLINK RLC PAYLOAD ON COMMON CHANNELS
A. B. C. This measurement provides the total count of uplink RLC payload on common channels expressed in kilo-octets. CC Reception by the RNC of a RLC PDU on an uplink common channel. On the PDU reception, the counter is increased with the value of the received PDU payload D. E. F. G. H. An integer value. VS.CommonUplinkDataRlc FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1201 Counter introduced in V 1.2.b
14.2. TOTAL COUNT OF DOWNLINK RLC PAYLOAD ON COMMON CHANNELS

A. B. C. This measurement provides the total count of downlink RLC payload on common channels expressed in kilo-octets. CC Emission by the RNC of a RLC PDU on an downlink common channel. On the PDU emission, the counter is increased with the value of the emitted PDU payload D. E. F. G. H. An integer value. VS.CommonDownlinkDataRlc FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1202 Counter introduced in V 1.2.b
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 102/136
14.3. NUMBER OF UPLINK RLC PDUS ON COMMON CHANNELS

A. This measurement provides the total count of uplink RLC PDUs on common channels. Remark: Only Transparent Mode is concerned since the RACH is the only UL common channel. B. C. D. E. F. G. H. CC The counter is increased on reception by the RNC of a RLC PDU on an uplink common channel. An integer value. VS.CommonUplinkPduRlc FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1203 Counter introduced in V 1.2.b
14.4. NUMBER OF DOWNLINK RLC PDUS ON COMMON CHANNELS

A. B. C. D. This measurement provides the total count of downlink RLC PDUs on common channels, screened per mode. CC The counter is increased on emission by the RNC of a RLC PDU on an downlink common channel. An integer value for each mode. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> E. Acknowledged Mode Unacknowledged Mode Transparent Mode (AM) (UM) (TM)
VS.CommonDownlinkPduRlc.AcknowledgeMode VS.CommonDownlinkPduRlc.UnacknowledgeMode VS.CommonDownlinkPduRlc.TransparentMode
F. G. H.
FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 103/136

NORTEL # 1204 Counter introduced in V 1.2.b
14.5. NUMBER OF UPLINK RLC SDUS ON COMMON CHANNELS

A. This measurement provides the total count of uplink RLC SDUs on common channels. Remark: Only Transparent Mode is concerned since the RACH is the only UL common channel. B. C. D. E. F. G. H. CC The counter is increased on reception by the RNC of a RLC SDU on an uplink common channel. An integer value. VS.CommonUplinkSduRlc FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1205 Counter introduced in V 2.0c
14.6. NUMBER OF DOWNLINK RLC SDUS ON COMMON CHANNELS

A. B. C. D. This measurement provides the total count of downlink RLC SDUs on common channels, screened per mode. CC The counter is increased on emission by the RNC of a RLC SDU on an downlink common channel. An integer value for each mode. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> E. Acknowledged Mode Unacknowledged Mode Transparent Mode (AM) (UM) (TM.
VS.CommonDownlinkSduRlc.AcknowledgeMode VS.CommonDownlinkSduRlc.UnacknowledgeMode VS.CommonDownlinkSduRlc.TransparentMode
F. G.
FDDCell Valid for circuit switched and packet switched traffic

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

H. NORTEL specified counter NORTEL # 1206 Counter introduced in V 2.0c
14.7. NUMBER OF DISCARDED RLC SDUS ON COMMON CHANNELS

A. B. C. D. This measurement provides the total count of discarded RLC SDUs on common channels, screened per mode. CC The counter is increased on each discard of RLC SDU on a common channel. An integer value for each mode. Screening: Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> E. Acknowledged Mode Unacknowledged Mode Transparent Mode (AM) (UM) (TM)
VS.CommonDiscardSduRlc.AcknowledgeMode VS.CommonDiscardSduRlc.UnacknowledgeMode VS.CommonDiscardSduRlc.TransparentMode
F. G. H.
14.8. NUMBER OF RLC DUMMY PADDINGS ON COMMON CHANNELS

A. B. C. D. E. F. G. H. This measurement provides the total count of RLC dummy paddings generated on common channels. CC The counter is increased on each generation of RLC dummy padding on a common channel. An integer value. VS.CommonPaddingRlc FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 105/136

NORTEL # 1208 Counter introduced in V 2.0c
14.9. NUMBER OF UPLINK MAC PDUS ON COMMON CHANNELS

A. B. C. D. E. F. G. H. This measurement provides the total count of uplink MAC PDUs on common channels. CC The counter is increased on reception by the RNC of a MAC PDU on an uplink common channel. An integer value. VS.CommonUplinkPduMac FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1209 Counter introduced in V 2.0c
14.10. NUMBER OF DOWNLINK MAC PDUS ON COMMON CHANNELS

A. B. C. D. E. F. G. H. This measurement provides the total count of downlink MAC PDUs on common channels, screened per mode. CC The counter is increased on emission by the RNC of a MAC PDU on an downlink common channel. An integer value VS.CommonDownlinkPduMac FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1210 Counter introduced in V 2.0c
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 106/136
14.11. TOTAL COUNT OF UPLINK MAC PAYLOAD ON COMMON CHANNELS

A. B. C. This measurement provides the total count of uplink MAC payload on common channels expressed in kilo-octets. CC Reception by the RNC of a MAC PDU on an uplink common channel. On the PDU reception, the counter is increased with the value of the received PDU payload D. E. F. G. H. An integer value. VS.CommonUplinkDataMac FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1211 Counter introduced in V 2.0c
14.12. TOTAL COUNT OF DOWNLINK MAC PAYLOAD ON COMMON CHANNELS

A. B. C. This measurement provides the total count of downlink MAC payload on common channels expressed in kilo-octets. CC Emission by the RNC of a MAC PDU on an downlink common channel. On the PDU emission, the counter is increased with the value of the emitted PDU payload D. E. F. G. H. An integer value. VS.CommonDownlinkDataMac FDDCell Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 1212 Counter introduced in V 2.0c
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 107/136
15. IUR INTERFACE

15.1. NUMBER OF SUCCESSFUL SCCP CONNECTIONS AT IUR INTERFACE
A. B. C. D. This measurement provides the number of successful SCCP connections at Iur interface for each neighboring RNC of a considered RNC. CC Successful SCCP connection establishment An integer value for each behavior of the considered RNC Screening: Sub-counter # 0 Sub-counter # 1 E. ----> ----> The considered RNC acts as a SRNC The considered RNC acts as a DRNC
VS.IurSccpCnxSuccess.EstablishedAsServingRnc VS.IurSccpCnxSuccess.EstablishedAsDriftRnc
F. G. H.
Neighboring RNC Valid for circuit switched and packet switched traffic. NORTEL specified counter NORTEL # 1311 Counter introduced in V 2.0c
15.2. NUMBER OF FAILED SCCP CONNECTIONS AT IUR INTERFACE

A. B. C. D. This measurement provides the number of failed SCCP connections at Iur interface, for each neighboring RNC of a given RNC CC Unsuccessful SCCP connection establishment An integer value for each Iur peer entity having requested a SCCP connection Screening: Sub-counter # 0 Sub-counter # 1 E. ----> ----> Refusal of local RNC request (by the SCCP protocol layer or by the neighboring RNC) Refusal of distant RNC request (by the local RNC)
VS.IurSccpCnxUnsuccess.RequestByLocalRncOnIur VS.IurSccpCnxUnsuccess.RequestByNeighRncOnIur
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 108/136

F. G. H. Neighboring RNC Valid for circuit switched and packet switched traffic. NORTEL specified counter NORTEL # 1312 Counter introduced in V 2.0c
16. RNC LOAD MANAGEMENT

16.1. LOAD OF TMU PROCESSORS 16.1.1 AVERAGE LOAD OF TMU PROCESSORS
A. B. This measurement provides the average processor load of TMU processors. SI NORTEL LOAD type counter C. A sampling event is generated according a sampling period. Sampled load of TMU processors values are cumulated. The averaged value is calculated at the end of the granularity period. It is expressed as a percentage (the value 100 expresses a 100% load). D. A integer value for each TMU board Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 E. VS.E3PrLoadCnTmu.Sbc.Avg VS.E3PrLoadCnTmu.Tm.Avg VS.E3PrLoadCnTmu.Pmc.Avg F. G. H. TMU N/A NORTEL specified counter NORTEL # 3001 Counter introduced in V 2.0e ----> ----> ----> SBC board TM board PMC board
16.1.2 MINIMUM LOAD OF TMU PROCESSORS

A. This measurement provides the minimum processor load of TMU processors.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 109/136

B. SI NORTEL LOAD type counter C. The minimum processor load of TMU processors is re-assessed at each sampling period during the granularity period. It is expressed as a percentage (the value 100 expresses a 100% load). D. A integer value for each TMU board Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 E. VS.E3PrLoadCnTmu.Sbc.Min VS.E3PrLoadCnTmu.Tm.Min VS.E3PrLoadCnTmu.Pmc.Min F. G. H. TMU N/A NORTEL specified counter NORTEL # 3001 Counter introduced in V 2.0e ----> ----> ----> SBC board TM board PMC board
16.1.3 MAXIMUM LOAD OF TMU PROCESSORS

A. B. This measurement provides the maximum processor load of TMU processors. SI NORTEL LOAD type counter C. The maximum processor load of TMU processors is re-assessed at each sampling period during the granularity period. It is expressed as a percentage (the value 100 expresses a 100% load). D. A integer value for each TMU board Screening: Sub-counter # 0 Sub-counter # 1 Sub-counter # 2 E. VS.E3PrLoadCnTmu.Sbc.Max VS.E3PrLoadCnTmu.Tm.Max VS.E3PrLoadCnTmu.Pmc.Max
----> ----> ---->
SBC board TM board PMC board
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 110/136

F. G. H. TMU N/A NORTEL specified counter NORTEL # 3001 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 111/136
17. NODE B PCM

17.1. LOSS OF INCOMING SIGNAL
A. B. C. D. E. F. G. H. This measurement provides the number of faulty seconds due to LOS alarm. CC Loss of the incoming signal . An integer value VS.PcmLos PCM Valid for circuit switched and packet switched traffic ITU-T G775 compliant NORTEL # 10001 Counter introduced in V 2.0e
17.2. ALARM INDICATION SIGNAL

A. B. C. D. E. F. G. H. This measurement provides the number of faulty seconds due to AIS alarm. CC Alarm Indication Signal sent by the remote equipment indicating that a transmission fault is located either at the remote equipment or upstream of the transmitting equipment. An integer value VS.PcmAis PCM Valid for circuit switched and packet switched traffic ITU-T G775 compliant NORTEL # 10002 Counter introduced in V 2.0e
17.3. LOSS OF FRAME ALIGNMENT

A. B. C. D. This measurement provides the number of faulty seconds due to LFA alarm. CC Loss of Frame Alignment due to patterns received with error. An integer value
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 112/136

E. F. G. H. VS.PcmLfa PCM Valid for circuit switched and packet switched traffic ITU-T G706 compliant NORTEL # 10003 Counter introduced in V 2.0e
17.4. FRAME ERROR

A. B. C. D. E. F. G. H. This measurement provides the number of faulty seconds due to FE alarm (this counter is meaningless in case of T1 link). CC Excessive bit error ratio detected by monitoring the frame alignment signal An integer value VS.PcmFe PCM Valid for circuit switched and packet switched traffic ITU-T G732 compliant NORTEL # 10004 Counter introduced in V 2.0e
17.5. CRC
A. B. C. D. E. F. G. H. This measurement provides the number of faulty seconds due to CRC alarm (this counter is meaningless in case of T1 link). CC CRC error detection An integer value VS.PcmCrc PCM Valid for circuit switched and packet switched traffic ITU-T G706 compliant NORTEL # 10005 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 113/136
17.6. REMOTE ALARM INDICATION

A. B. C. D. E. F. G. H. This measurement provides the number of faulty seconds due to RAI alarm. CC Remote alarm indication received by the local equipment and indicating that the remote equipment does not receive coherent data from the local equipment. An integer value VS.PcmRai PCM Valid for circuit switched and packet switched traffic ITU-T G775 compliant NORTEL # 10006 Counter introduced in V 2.0e
17.7.
A. B. C.
FRAME ALIGNMENT SIGNAL

This measurement provides the number of Frame Alignment Signal received in error. CC Frame Alignment Signal received in error. The counter is disabled during the receive loss of synchronization conditions
D. E. F. G. H.
An integer value VS.PcmFas PCM Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10007 Counter introduced in V 2.0e
17.8. E-BITS
A. B. C. This measurement provides the number of received E-bits set to zero (this counter is meaningless in case of T1 link). CC Reception of an E-bit set to zero (meaning that remote equipment received the corresponding sub-multi frame with an errored CRC4 code). The counter is disabled during the receive loss of framing or multi-framing synchronization. D. An integer value
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 114/136

E. F. G. H. VS.PcmEbits PCM Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10008 Counter introduced in V 2.0e
17.9.
A. B. C.
BIPOLAR VIOLATION
This measurement provides the number of consecutive bipolar violation of the same polarity detected on the receiving line per second. CC Consecutive bipolar violation of the same polarity detected on the receiving line The counter shall increment even if framing alignment is not succeeded.
D. E. F. G. H.
An integer value VS.PcmBpv PCM Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10009 Counter introduced in V 2.0e
17.10. SLIP EVENT

A. B. C. D. E. F. G. H. This measurement provides the number of seconds during which at least one slip event occurred. CC Slip event, i.e. the repetition or the deletion of a frame on receive or transmit side. An integer value VS.PcmSlip PCM Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10010 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 115/136
17.11. ERRORED SECONDS

A. B. C. D. E. F. G. H. This measurement provides the number of Errored Seconds during the last supervision period. CC Input event of the Errored seconds algorithm (c.f. ITU-T G826 Recommendation). An integer value VS.PcmEs PCM Valid for circuit switched and packet switched traffic ITU-T G826 compliant NORTEL # 10011 Counter introduced in V 2.0e
17.12. SEVERELY ERRORED SECONDS

A. B. C. D. E. F. G. H. This measurement provides the number of Severely Errored Seconds during the last supervision period. CC Input event of the Severely Errored Seconds algorithm (c.f. ITU-T G826 Recommendation). An integer value VS.PcmSes PCM Valid for circuit switched and packet switched traffic ITU-T G826 compliant NORTEL # 10012 Counter introduced in V 2.0e
17.13. BACKGROUND BLOCK ERRORS

A. B. C. D. E. F. This measurement provides the number of Background Block Errors during the last supervision period. CC Background Block Error (c.f. ITU-T G826 Recommendation). An integer value VS.PcmBbe PCM
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 116/136

G. H. Valid for circuit switched and packet switched traffic ITU-T G826 compliant NORTEL # 10013 Counter introduced in V 2.0e
17.14. UNAVAILABLE SECONDS

A. B. C. This measurement provides the number of Severely UnAvailable Seconds during the last supervision period. CC Input event of the Severely UnAvailable Seconds algorithm (c.f. ITU-T G826 Recommendation). An UAS is a second being part of a unavailable time period. D. E. F. G. H. An integer value VS.PcmUas PCM Valid for circuit switched and packet switched traffic ITU-T G826 compliant NORTEL # 10014 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 117/136
18. NODE B ATM

18.1. NUMBER OF RECEIVED CELLS (AAL2)
A. B. C. D. E. F. G. H. This measurement provides the number of received cells per user plane ATM PVC. CC The counter is increased on a cell reception. An integer value VS.AAL2NbReceivedCell VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10101 Counter introduced in V 2.0e
18.2. NUMBER OF LOST CPS PACKETS (AAL2)

A. B. C. D. E. F. G. H. This measurement provides the number of lost CPS packets per user plane ATM PVC. CC The counter is increased on detection of a CPS packet loss. An integer value VS.AAL2NbLostCPS VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10102 Counter introduced in V 2.0e
18.3. NUMBER OF STF PARITY ERRORS (AAL2)

A. B. This measurement provides the number of received CPS PDUs with parity error per user plane ATM PVC. CC
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 118/136

C. D. E. F. G. H. The counter is increased on detection of a parity error on a CPS PDU. An integer value VS.AAL2NbSTFParityErr VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10103 Counter introduced in V 2.0e
18.4. NUMBER OF SEQUENCE NUMBER ERRORS (AAL2)

A. B. C. D. E. F. G. H. This measurement provides the number of received CPS PDUs with a sequence number error per user plane ATM PVC. CC The counter is increased on detection of an error sequence on a CPS PDU. An integer value VS.AAL2NbSequenceNumberErr VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10104 Counter introduced in V 2.0e
18.5. NUMBER OF CPS HEADER CHECKSUM ERROR (AAL2)

A. B. C. D. E. F. G. H. This measurement provides the number of received CPS packets with a Header checksum error per user plane ATM PVC. CC The counter is increased on detection of a Header checksum error. An integer value VS.AAL2NbCPSHecErr VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10105 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 119/136
18.6. NUMBER OF CPS LENGTH ERRORS (AAL2)

A. B. C. D. E. F. G. H. This measurement provides the number of received CPS packets with a wrong length per user plane ATM PVC. CC The counter is increased on detection of a length different from LI field content in CPS packet. An integer value VS.AAL2NbCPSLengthErr VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10106 Counter introduced in V 2.0e
18.7. NUMBER OF LENGTH MISMATCHES (AAL2)

A. B. C. D. E. F. G. H. This measurement provides the number of received CPS packets with a length mismatch per user plane ATM PVC. CC The counter is increased on detection of a LI field content in CPS packet different from OSF field content in CPS PDU . An integer value VS.AAL2NbCpsLengthMismatch VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10107 Counter introduced in V 2.0e
18.8. NUMBER OF INVALID CID (AAL2)

A. B. C. D. E. This measurement provides the number of received CPS packets with a forbidden CID per user plane ATM PVC. CC The counter is increased on detection of a CID inside the range 0-7 . An integer value VS.AAL2NbCpsInvalidCIDErr
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 120/136

F. G. H. VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10108 Counter introduced in V 2.0e
18.9. NUMBER OF CELLS WITH OFFSET FIELD > 47 (AAL2)

A. B. C. D. E. F. G. H. This measurement provides the number of received CPS PDUs with an OSF field value > 47 per user plane ATM PVC. CC The counter is increased on detection of a OSF field value > 47 An integer value VS.AAL2NbOSFBiggerThan47 VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10109 Counter introduced in V 2.0e
18.10. NUMBER OF RECEIVED CELLS (AAL5)

A. B. C. D. E. F. G. H. This measurement provides the number of received cells per control plane ATM PVC. CC The counter is increased on a cell reception. An integer value VS.AAL5NbReceivedCell VCC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10110 Counter introduced in V 2.0e
18.11. NUMBER OF ABORT ERRORS (AAL5)

A. B. This measurement provides the number of cells dropped on peer demand per control plane ATM PVC. CC
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 121/136

C. D. E. F. G. H. The counter is increased on peer demand to drop a cell. An integer value VS.AAL5NbAbortErr VCC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10111 Counter introduced in V 2.0e
18.12. NUMBER OF LENGTH ERRORS (AAL5)

A. B. C. D. E. F. G. H. This measurement provides the number of AAL5 frames with a wrong size per control plane ATM PVC. CC The counter is increased on detection of a wrong size of a frame. An integer value VS.AAL5NbLengthErr VCC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10112 Counter introduced in V 2.0e
18.13. NUMBER OF CRC FRAME ERRORS (AAL5)

A. B. C. D. E. F. G. H. This measurement provides the number of received AAL5 frames with a wrong CRC per control plane ATM PVC. CC The counter is increased on detection of a CRC different the trailer value . An integer value VS.AAL5NbCrcFrameErr VCC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10113 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 122/136
18.14. NUMBER OF INVALID SIZE ERRORS (AAL5)

A. B. C. D. E. F. G. H. This measurement provides the number of AAL5 frames with an invalid size per control plane ATM PVC. CC The counter is increased on detection of a frame size larger than the maximum frame size. An integer value VS.AAL5NbInvalidSize VCC Valid for circuit switched and packet switched traffic NORTEL specified counter NORTEL # 10114 Counter introduced in V 2.0e
18.15. NUMBER OF SENT CELLS (AAL2)

A. B. C. D. E. F. G. H. This measurement provides the number of sent cells per user plane ATM PVC. CC The counter is increased on a cell emission. An integer value VS.AAL2NbSentCell VCC Valid for circuit switched traffic NORTEL specified counter NORTEL # 10115 Counter introduced in V 2.0e
18.16. NUMBER OF SENT CELLS (AAL5)

A. B. C. D. E. F. G. This measurement provides the number of sent cells per control plane ATM PVC. CC The counter is increased on a cell emission. An integer value VS.AAL5NbSentCell VCC Valid for circuit switched and packet switched traffic
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 123/136

H. NORTEL specified counter NORTEL # 10116 Counter introduced in V 2.0e
19. NODE B RADIO

19.1. WIDE-BAND RECEIVED POWER ON MAIN ANTENNA 19.1.1 AVERAGE WIDE-BAND RECEIVED POWER ON MAIN ANTENNA
A. This measurement provides the average wide-band received power on the main antenna for each cell (i.e. per sector and per frequency). The averaged value over the observation period is calculated directly by the BTS at the end of the observation period (and the number of samples is set to 1). SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 100 ms A single integer value, expressed in mW, with a 10-12 mW resolution VS.RadioWBandRxMainPwr.Avg BTSCell N/A NORTEL specified counter NORTEL # 10201 Counter introduced in V 2.0e
B.
19.1.2 MINIMUM WIDE-BAND RECEIVED POWER ON MAIN ANTENNA

A. B. This measurement provides the minimum wide-band received power on the main antenna for each cell (i.e. per sector and per frequency) on a 100 ms period during the collection period SI NORTEL LOAD type counter C. D. A sampling event generated every 100 ms A single integer value, expressed in mW, with a 10-12 mW resolution
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 124/136

E. F. G. H. VS.RadioWBandRxMainPwr.Min BTSCell N/A NORTEL specified counter NORTEL # 10201 Counter introduced in V 2.0e
19.1.3 MAXIMUM WIDE-BAND RECEIVED POWER ON MAIN ANTENNA

A. B. This measurement provides the maximum wide-band received power on the main antenna for each cell (i.e. per sector and per frequency) on a 100 ms period during the collection period . SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 100 ms A single integer value, expressed in mW, with a 10-12 mW resolution VS.RadioWBandRxMainPwr.Max BTSCell N/A NORTEL specified counter NORTEL # 10201 Counter introduced in V 2.0e
19.2. WIDE-BAND RECEIVED POWER ON DIVERSITY ANTENNA 19.2.1 AVERAGE WIDE-BAND RECEIVED POWER ON DIVERSITY ANTENNA
A. This measurement provides the average wide-band received power on the diversity antenna for each cell (i.e. per sector and per frequency). The averaged value over the observation period is calculated directly by the BTS at the end of the observation period (and the number of samples is set to 1). SI NORTEL LOAD type counter C. D. E. A sampling event generated every 100 ms A single integer value, expressed in mW, with a 10-12 mW resolution VS.RadioWBandRxDivPwr.Avg
B.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 125/136

F. G. H. BTSCell N/A NORTEL specified counter NORTEL # 10202 Counter introduced in V 2.0e
19.2.2 MINIMUM WIDE-BAND RECEIVED POWER ON DIVERSITY ANTENNA

A. This measurement provides the minimum wide-band received power on the diversity antenna for each cell (i.e. per sector and per frequency) on a 100 ms period during the collection period SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 100 ms A single integer value, expressed in mW, with a 10-12 mW resolution VS.RadioWBandRxDivPwr.Min BTSCell N/A NORTEL specified counter NORTEL # 10202 Counter introduced in V 2.0e
B.
19.2.3 MAXIMUM WIDE-BAND RECEIVED POWER ON DIVERSITY ANTENNA

A. This measurement provides the maximum wide-band received power on the diversity antenna for each cell (i.e. per sector and per frequency) on a 100 ms period during the collection period SI NORTEL LOAD type counter C. D. E. F. G. A sampling event generated every 100 ms A single integer value, expressed in mW, with a 10-12 mW resolution VS.RadioWBandRxDivPwr.Max BTSCell N/A
B.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 126/136

19.3. TRANSMITTED CARRIER POWER 19.3.1 AVERAGE TRANSMITTED CARRIER POWER

A. This measurement provides the average value of the total transmitted power for each cell (i.e. per sector and per frequency). The averaged value over the observation period is calculated directly by the BTS at the end of the observation period (and the number of samples is set to 1). SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 100 ms A single integer value, expressed as in mW VS.RadioTxCarrierPwr.Avg BTSCell N/A NORTEL specified counter NORTEL # 10203 Counter introduced in V 2.0e
B.
19.3.2 MINIMUM TRANSMITTED CARRIER POWER

A. This measurement provides the minimum value of the total transmitted power for each cell (i.e. per sector and per frequency). This minimum value is re-assessed at each 100 ms period during the collection period . SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 100 ms A single integer value, expressed in mW VS.RadioTxCarrierPwr.Min BTSCell N/A NORTEL specified counter NORTEL # 10203 Counter introduced in V 2.0e
B.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 127/136
19.3.3 MAXIMUM TRANSMITTED CARRIER POWER

A. This measurement provides the maximum value of the total transmitted power for each cell (i.e. per sector and per frequency). This maximum value is re-assessed at each 100 ms period during the collection period . SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 100 ms A single integer value, expressed in mW VS.RadioTxCarrierPwr.Max BTSCell N/A NORTEL specified counter NORTEL # 10203 Counter introduced in V 2.0e
B.
19.4. MULTI-CARRIER POWER AMPLIFIER POWER 19.4.1 AVERAGE MCPA POWER

A. This measurement provides the average value of the total transmitted power by the Power Amplifier. The averaged value over the observation period is calculated directly by the BTS at the end of the observation period (and the number of samples is set to 1). SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 1 second A single integer value, expressed in mW VS.RadioTxCarrierPwr.Avg PA N/A NORTEL specified counter NORTEL # 10204 Counter introduced in V 2.0e
B.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 128/136
19.4.2 MINIMUM MCPA POWER

A. This measurement provides the minimum value of the total transmitted power by the Power Amplifier. This minimum value is re-assessed at each 100 ms period during the collection period . SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 1 second A single integer value, expressed in mW VS.RadioTxCarrierPwr.Min PA N/A NORTEL specified counter NORTEL # 10204 Counter introduced in V 2.0e
B.
19.4.3 MAXIMUM MCPA POWER

A. This measurement provides the maximum value of the total transmitted power by the Power Amplifier. This maximum value is re-assessed at each 100 ms period during the collection period . SI NORTEL LOAD type counter C. D. E. F. G. H. A sampling event generated every 1 second A single integer value, expressed in mW VS.RadioTxCarrierPwr.Max PA N/A NORTEL specified counter NORTEL # 10204 Counter introduced in V 2.0e
B.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 129/136
20. IBTS LOAD MANAGEMENT

20.1. CEM CAPACITY USED 20.1.1 AVERAGE CEM CAPACITY USED
A. This measurement provides the average CEM capacity used. The averaged value over the observation period is calculated directly by the BTS at the end of the observation period (and the number of samples is set to 1). SI NORTEL LOAD type counter C. A sampling event is generated according a 5-sec sampling period. Sampled CEM capacity used values are cumulated. The averaged value is calculated at the end of the granularity period. It is expressed as a percentage (the value 100 expresses a 100% load). D. A single integer value Screening =NO E. F. G. H. VS.CEMUsed.Avg BTSEquipment N/A NORTEL specified counter NORTEL # 10301 Counter introduced in V 2.0e
B.
20.1.2 MINIMUM CEM CAPACITY USED

A. B. This measurement provides the minimum CEM capacity used. SI NORTEL LOAD type counter C. The minimum CEM capacity used is re-assessed at each 5-sec sampling period during the granularity period. It is expressed as a percentage (the value 100 expresses a 100% load). D. A single integer value Screening =NO E. F. G. VS.CEMUsed.Min BTSEquipment N/A
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 130/136

20.1.3 MAXIMUM CEM CAPACITY USED

A. B. This measurement provides the Maximum CEM capacity. SI NORTEL LOAD type counter C. D. The maximum CEM capacity used is re-assessed at each 5-sec sampling period during the granularity period. A single integer value Screening =NO E. F. G. H. VS.CEMUsed.Max BTSEquipment N/A NORTEL specified counter NORTEL # 10301 Counter introduced in V 2.0e
20.2. CEM RESOURCE ALLOCATION FAILURE

A. B. C. D. This measurement provides the percentage of times allocation of CEM resources failed due to unavailability of CEM resource. CC Resource failure on CEM resource allocation request. A single integer value expressed as a percentage Screening =NO E. F. G. H. VS.CEMAllocFail BTSEquipment N/A NORTEL specified counter NORTEL # 10302 Counter introduced in V 2.0e
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 131/136
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 132/136
21. ABBREVIATIONS AND DEFINITIONS

21.1. ABBREVIATIONS
CBR: CLP: N/A: RAB: RB: RRM: RSSI: VS: Constant Bit Rate Cell Loss Priority Not Applicable Radio Access Bearer Radio Bearer Radio Resource Management Received Signal Strength Indicator Vendor Specific
21.2. DEFINITIONS 21.2.1 ACCESS STRATUM CONFIGURATION

Pointer to a pre-defined set of Radio Bearers providing a given Radio Access Bearer Service. For instance: the 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 The list of DL access stratum configurations is provided in Annexe 1.
21.2.2 REFERENCE CELL

Cell ranking first in a UE active set considering a radio criteria , i.e. 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.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 133/136
22. ANNEXE 1: DOWNLINK ACCESS STRATUM CONFIGURATIONS

Downlink Access Stratum configuration #
0 1 2 3 4 5 6 7 8 9 10
RB configuration
1 CS RB DTCH 64 Kbps + 3 SRB DCCH 3,4 Kbps. 3 CS RB DTCH 12,2 Kbps + 3 SRB DCCH 3,4 Kbps. 1 PS RB DTCH 64 Kbps + 3 SRB DCCH 3,4 Kbps. 3 Stand-alone SRB DCCH 3,4 Kbps. 34.108 configuration with only 3 SRBs 1 PS RB DTCH 8 Kbps + 3 SRB DCCH 3,4 Kbps. 34.108 configuration with only 3 SRBs 3 CS RB DTCH 12,2 Kbps (DTX) + 3 SRB DCCH 3,4 Kbps. 1 PS RB DTCH 128 Kbps + 3 SRB DCCH 3,4 Kbps 1 PS RB DTCH 384 Kbps + 3 SRB DCCH 3,4 Kbps 1 PS RB DTCH 14,4 Kbps + 3 SRB DCCH 3,4 Kbps (*) 1 CS RB DTCH 12,2 Kbps (No DTX) + 1 PS RB DTCH 64 Kbps + 3 SRB DCCH 3,4 Kbps 1 CS RB DTCH 12,2 Kbps (DTX) + 1 PS RB DTCH 64 Kbps + 3 SRB DCCH 3,4 Kbps
(*) : The DL Access Stratum Configuration #8 (PS14.4/14.4) is not available in UMTS02/UMTS02.1. So results for index #8 in counters screened by DLAsConf are not meaningful and are not incremented.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 134/136
23. ANNEXE 2: RRC CONNECTION ESTABLISHMENT CAUSES

RRC connection establishment causes used in the V2 implementation are:
Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Sub-counter # 3 ----> Sub-counter # 4 ----> Sub-counter # 5 ----> Sub-counter # 6 ----> Sub-counter # 7 ----> Sub-counter # 8 ----> Sub-counter # 9 ---->
Originating Conversational call Originating Streaming call Originating Interactive call Originating Background call Subscribed Traffic call Terminating Conversational call Terminating Streaming call Terminating Interactive call Terminating Background call Emergency call
Sub-counter # 10 ----> Intersystem cell re-selection Sub-counter # 11 ----> Intersystem cell change order Sub-counter # 12 ----> Registration Sub-counter # 13 ----> Detach Sub-counter # 14 ----> Originating High priority signalling Sub-counter # 15 ----> Originating Low priority signalling Sub-counter # 16 ----> Call re-establishment Sub-counter # 17 ----> Terminating High priority signalling Sub-counter # 18 ----> Terminating Low priority signalling Sub-counter # 19 ----> Terminating : Cause unknown Sub-counter # 20 ----> Spare1 (not used : provisioned for future use)
Nota : sub-counters #17-19 have been added and #14-15 have been modified in V2 due to modifications in 3GPP TS 25.331 3.7.0. Sub-counter #20 is not an RRC cause and is not used in V2 but has been provisionned for future used.
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 135/136
24. ANNEXE 3: RRC CONNECTION RELEASE CAUSES

RRC connection release causes used in the V2 implementation are:
Sub-counter # 0 ----> Sub-counter # 1 ----> Sub-counter # 2 ----> Sub-counter # 3 ----> Sub-counter # 4 ----> Sub-counter # 5 ----> Sub-counter # 6 ----> Normal release Unspecified release + SCCP release Preemptive release Congestion Re-establishment reject User inactivity Directed signalling connection re-establishment
Nota : sub-counters #5 and #6 have been swapped between V1 and V2.
END OF DOCUMENT
UMT/SYS/DD/0075
02.13 / EN
Standard
27/Jun/2003
Page 136/136

Umts Access Counters List Umt Sys DD 75.v2.13

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Umts Access Counters List Umt Sys DD 75.v2.13

Uploaded by

Copyright:

Available Formats

UMTS Access counters list