Utran Kpi Description

sUTRAN Performance MeasurementSystem Key Performance Indicators

A50016-G5000-D528-1-7618 ND-57827-701(E)-01

Siemens AG: NEC Corporation:

A50016-G5000-D528-1-7618 ND-57827-701(E)-01

1

Key Performance Indicators

Performance Measurement System

Trademarks: All designations used in this document can be trademarks, the use of which by third parties for their own purposes could violate the rights of their owners.

Copyright (C) Siemens AG / NEC Corporation 2003Issued by: Siemens AG, Information and Communications Group, Hofmannstrae 51, 81359 Mnchen, Germany and NEC Corporation, 7-1, Shiba 5-chome, Minato-ku, Tokyo, Japan Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.

2


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



Reason for UpdateSummary: First issue. Details: Chapter/Section All Reason for Update First issue

Issue historyIssue Number/ Version 1 08/2003 First issue Date of Issue Reason for Update


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

3



This document consists of a total of 70 pages. All pages are issue 1.

Contents1 1.1 1.2 1.3 2 2.1 2.1.1 2.1.2 2.1.2.1 2.1.2.2 2.1.3 2.1.3.1 2.1.3.2 2.1.4 2.1.4.1 2.2 2.2.1 2.2.1.1 2.2.2 2.2.2.1 2.2.2.2 2.3 2.3.1 2.4 2.4.1 2.4.1.1 2.4.1.2 2.4.2 2.4.2.1 2.4.2.2 3 3.1 3.1.1 3.2 3.2.1 3.2.1.1 3.2.1.2 3.2.2 3.2.2.1 3.3 3.3.1 3.3.2 4 Introduction ..................................................................................................... 8 Purpose .......................................................................................................... 8 Definition of terms........................................................................................... 8 General Principles .......................................................................................... 9 Call/Connection Analysis .............................................................................. 12 Call Establishments ...................................................................................... 12 Call setup success rate ................................................................................ 12 RRC Connection Establishments ................................................................. 14 RRC connection establishment success rate............................................... 14 RRC connection establishment failure rate .................................................. 15 RAB Establishments ..................................................................................... 15 RAB establishment success rate.................................................................. 16 RAB establishment failure rate ..................................................................... 17 Paging........................................................................................................... 18 Paging Failure Rate ...................................................................................... 18 Connection Release Analysis....................................................................... 19 CN originated release analysis..................................................................... 19 Connection Release rate .............................................................................. 19 UTRAN originated release analysis.............................................................. 20 Connection Drop Analysis ............................................................................ 20 RRC Drop Analysis....................................................................................... 22 RRC State Transitions .................................................................................. 23 State transition failure rate............................................................................ 23 Channel Reconfiguration Analysis................................................................ 25 Transport Channel Reconfiguration.............................................................. 25 Transport Channel Reconfiguration success rate ........................................ 25 Transport Channel Reconfiguration failure rate ........................................... 26 Physical Channel Reconfiguration................................................................ 27 Physical Channel Reconfiguration success rate .......................................... 27 Physical Channel Reconfiguration failure rate ............................................. 27 Connection Mobility ...................................................................................... 28 UTRAN updates............................................................................................ 28 Update rate ................................................................................................... 28 Relocation Preparation ................................................................................. 29 Outgoing Relocations ................................................................................... 29 Relocation success rate outgoing................................................................. 29 Relocation failure rate outgoing.................................................................... 29 Incoming Relocations ................................................................................... 30 Relocation success rate incoming ................................................................ 30 Soft Handover............................................................................................... 31 Branch addition success rate ....................................................................... 31 Branch addition failure rate........................................................................... 33 Siemens AG: A50016-G5000-D528-1-7618 NEC Corporation: ND-57827-701(E)-01



3.4 3.4.1 3.4.2 3.4.3 3.5 3.5.1 3.5.1.1 3.5.2 3.5.2.1 3.5.2.2 3.5.2.3 4 4.1 4.2 4.3 4.4 4.5 5 5.1 5.1.1 5.1.2 5.2 5.2.1 5.3 5.3.1 5.3.2 5.3.3 5.4 5.4.1 5.5 5.5.1 6 6.1 6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.2 6.2.1 6.2.2 6.2.3 6.3 6.3.1 6.3.1.1 Siemens AG: NEC Corporation:

Hard Handover ............................................................................................. 37 Outgoing Hard Handover success rate ........................................................ 37 Outgoing Hard Handover failure rate ........................................................... 38 Outgoing Hard Handover drop rate .............................................................. 39 Inter-System (Inter-RAT) Handover ............................................................. 40 Relocation Preparation (ACM)...................................................................... 40 Relocation Preparation failure rate ............................................................... 40 Outgoing circuit switched Inter-System Handover ....................................... 41 Outgoing CS Inter System Handover success rate...................................... 41 Outgoing CS Inter System Handover failure rate ......................................... 42 Outgoing CS Inter System Handover drop rate............................................ 44 Quality Indicators .......................................................................................... 46 Principle ........................................................................................................ 46 Call establishment quality indicator .............................................................. 46 Branch Addition quality indicator .................................................................. 46 Hard handover quality indicator.................................................................... 47 Inter-System handover quality indicator ....................................................... 47 QuaNTIty Indicators...................................................................................... 48 RRC State Transitions.................................................................................. 48 Number of successful state transitions......................................................... 48 Number of state transitions to Idle mode...................................................... 49 Soft Handover............................................................................................... 49 Soft Handover rate ....................................................................................... 49 Relocations ................................................................................................... 50 Number of outgoing relocations ................................................................... 50 Number of incoming relocations ................................................................... 50 Outgoing Relocation per Call rate ................................................................ 50 Hard Handover ............................................................................................. 51 Outgoing Hard Handover per call rate.......................................................... 51 Inter System Handover................................................................................. 52 Outgoing CS Inter System Handover per call rate ....................................... 52 UtiliZation...................................................................................................... 53 RNC Load Report ......................................................................................... 53 RNC Processor Load.................................................................................... 53 DHT usage.................................................................................................... 53 DHT allocation success rate......................................................................... 53 PRLC usage ................................................................................................. 53 PRLC allocation success rate ...................................................................... 54 Node B Load Report..................................................................................... 54 Node B usage rate........................................................................................ 54 Base Band usage rate .................................................................................. 54 Rest of call capacity...................................................................................... 54 Cell Load Report........................................................................................... 55 Cell Utilisation ............................................................................................... 55 Code usage rate ........................................................................................... 55

A50016-G5000-D528-1-7618 ND-57827-701(E)-01

5



6.3.2 6.3.2.1 6.3.2.2 6.4 6.4.1 6.4.2 7 7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.1.5 7.2 7.2.1 7.2.2 8 8.1 8.2 8.3 9 10

Cell load related Radio Measurements ........................................................ 56 Transmitted Carrier power ............................................................................ 56 Received Total Wide Band Power................................................................ 56 Radio interface.............................................................................................. 57 Common Channel Load Reports .................................................................. 57 Code allocation success rate........................................................................ 57 Transport Network Layer .............................................................................. 58 ATM-Layer on RNC side .............................................................................. 58 STM-1 Transmission usage rate .................................................................. 58 STM-1 Receive usage rate........................................................................... 58 STM-1 Transmit/Receive rate....................................................................... 59 E1 Transmit/Receive rate ............................................................................. 59 Cell Loss Ratio.............................................................................................. 59 ATM-Layer on Node B side .......................................................................... 60 Cell Loss Ratio.............................................................................................. 60 ATM Transmit/Receive rate.......................................................................... 60 Appendix....................................................................................................... 61 List of Measurements in RNC....................................................................... 61 List of Measurements in Node B .................................................................. 64 List of KPIs.................................................................................................... 65 Reference documents .................................................................................. 69 Abbreviations ................................................................................................ 70

6


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



IllustrationsFig. 2.1 Release Request message and command flow ........................................... 20 Fig. 12.1 Success rates of QoS classes...................................................................... 10


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

7



1 Introduction1.1 PurposeThis document is intended to define UTRAN Key Performance Indicators, which give information about quality, performance, load, capacity, .. in a uniform way to the operator. These indicators may be used for the following purposes: Definition of formulas, which are used for realization of predefined reports in the PM+ application of the O&M Toolset (i.e. SPOTS),

1.2

Definition of termsEach KPI will be described by the following fields:

Long name This field contains the name of the described KPI.

Short name This field contains an acronym for the described KPI

Description This field contains a short explanation of the KPI.

Formula This field contains the formula for calculation of the KPI.

Counters This field contains the counters used for calculation of the KPI. Counters are described by the shortname of the measurement and, in brackets, the index of the used counter. The indices are listed with the following meaning: - measType[i] Counter with index #i is used - measType[i,j,k] Counters with indices #i, #j, #k are summarized - measType[i-j] Counters in the index range #i to #j are summarized - measType[all] All counters of the measurement are summarized - measType[i][j] Counter related to index #i with sub-counters index #j are used. E.g. index[j] related to CS defined with index #i Note: An Index is represented by x,y,z, where x represents the protocol type, y represents the cause categorization and z represents the cause value (see [2]. If specific indices are listed, only the cause values are listed. 8 Siemens AG: NEC Corporation: A50016-G5000-D528-1-7618 ND-57827-701(E)-01



Elementary object This field contains the measured object class the KPI is applicable to. For UMR2.0, this field will only contain the objects RNC, cell, adjacent cell relation, adjacent GERAN cell relation.

Unit/Range This field contains unit and/or range related to the KPI, e.g. percent.

Remark This field contains additional information.

1.3

General Principles(n-1) out of n approach Measurements can be split in 3 sub-measurements number of attempts, number of successes and number of failures where any of the three measurements can be calculated from the two others. # of Success + # of Failures = # of Attempts SuccessRate + FailureRate = 100% SuccessRate + FailureRate + DropRate = 100% For procedure related KPI analysis it will be defined the Success Rate and the Failure Rate if possible. In case of Hard handover or Inter-System handover a drop rate is added which indicates a failed handover procedure with the consequence that the connection is lost. According the formulas depicted above, one of the rates could be calculated if the other value(s) are known. However, since the measurement recording within the network entities may be out of balance due to failed counting or in case attempts and successful/failed cases are counted within different granularity periods, the adding of the indicated rates may not be exactly 100% in all cases. It will be therefore indicated all rate cases within the document to be able to make a double check of the counters.

Cause relations For determination of per-cause values the following rules shall apply:

SuccessRate[ InitCause] =

# ofSucc[ InitCause] # ofAttempts[ InitCause] # ofFailures[ FailureCause] # ofAttempts[ AllCauses ]

FailureRate[ FailureCause] =


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

9



In case of the Success Rate per init cause, the number of success is related to the number of attempts, where in both terms the init cause shall apply. In case of the Failure Rate per dedicated failure cause, the number of failures is related to the number of attempts, where the dedicated failure cause is related to all causes of the attempts. The difference of these calculation rules is based on the target group that evaluates the KPI. The success rates of a procedure refers mainly to Network Planning / Network Optimization groups where the success rate related to the dedicated initialization cause is focused. Thus, e.g. the success rate of the RAB establishment for each QoS class may be depicted in a diagram as follows:

94% 92% 90% 88% 86% 84% 82% Convers. Streaming Interactive Background Success Rate

Fig. 1.1

Success rates of QoS classes

The dedicated FailureRates of a procedure is mainly used for Troubleshooting. Within this KPI document the definition the ratios of the individual failure causes are depicted related to all attempts. All failure rates per cause added up result in the total failure rate. Of course the indication of the failure rate per initial cause would be advantageous, but this is not possible. In case a failure occur the context of the initialization cause would have to be created which results in a lot of effort and a higher number of measurement counters since for each initialization cause the failure cause has to be stored separately.

Granularity Period Within this document it is assumed that the KPI is applicable for the same granularity period as defined for the measurements that are utilized within the formulas. Thus, no recommendation is given related to the GP of the KPI. However, the measurements used within one formula may have been activated within separate scanners where different GPs may have been activated. In such a case the O&M Toolset shall consider the different GPs and aggregate the measurements with the lower GPs until the same GP for all measurements apply.

10


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



Call versus Connection Within this document KPIs will be defined analyzing calls and analyzing connections. In our approach calls will be analyzed if a RAB establishment/release is involved. Thus, a call is not related only to a voice connection but also to PS connections. If in the concerned measurements it cannot be distinguished if a RAB is involved or not, e.g. within the iuRelReq counter, then the behavior of connections will be analyzed. I.e. the connection may be related to a call or to signaling only due to SMS transmission or due to Location updates.


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

11



2 Call/Connection Analysis2.1 Call EstablishmentsGeneral assumption: In reference to 3GPP TS 25.931, a call setup will be described by the concatenation of the phases 1. RRC connection establishment (cf. 3GPP TR25.931, chapter 7.3) -> covered by measurements rrcEstabAtt, rrcEstabSucc, rrcEstabFail 2. NAS signaling connection establishment (cf. 3GPP TR25.931, chapter 7.2) -> pure pass-through of Initial Direct Transfer message; success rate=100% assumed 3. RAB establishment (cf. 3GPP TR25.931, chapter 7.6) -> covered by measurements rabEstabAtt, rabEstabSucc, rabEstabFail Remark, that these phases refer to the UE in IDLE mode, but it is possible to have several RAB establishments in the same RRC connection.

2.1.1

Call setup success rateRemark, that for the indicated success rate only UTRAN failures are taken into account. In case the Core Network rejects the establishment request from the UE due to internal checks, UTRAN is not able to know the failed NAS procedure. Remark, in UMR2.0 following RAB establishment causes are not supported: 1-0 2-0 3-0 0-1 1-1 CS streaming CS interactive CS background PS conversational PS streaming

Long name

Short name

Description Formula

a) Call setup success rate (Access probability) b) User setup success rate (Access probability) c) User setup success rate (multi RAB assignment) a) CSSR(AccessProbability) b) USSR(AccessProbability) c) USSR(multiRAB) This KPI describes the ratio of successful call establishments related to attempts of procedures involved considering success rate of RRC - and RAB Establishment. rrcEstabSucc[0 9] rabEstabSucc[all ] * *100% a) CSSR( Access Pr obability ) = rrcEstabAtt[0 9] rabEstabAtt[all ]

12


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



USSR( Access Pr obability ) =b)

rrcEstabAtt[all ] rrcEstabFail[0] * rrcEstabAtt[all ] rabEstabSucc[all ] *100% rabEstabAtt[all ]

Counters

rrcEstabAtt[0 - 9] USSR(multiRAB ) = * (USSR( Access Pr obability )) + rabEstabAtt[all] c) rrcEstabAtt[0 - 9] rabEstabSucc[all] 1 * * 100% rabEstabAtt [all] rabEstabAtt[all] rrcEstabAtt[all] rrcEstabSucc[all] rabEstabSucc[all] rabEstabAtt[all]RAB establishment causes: 0-0 CS conversational 1-0 CS streaming 2-0 CS interactive 3-0 CS background 0-1 PS conversational 1-1 PS streaming 2-1 PS interactive 3-1 PS background RRC establishment causes: 3,0,0 Originating conversational call 3,0,1 Originating streaming call 3,0,2 Originating interactive call 3,0,3 Originating background call 3,0,4 Originating subscribed traffic call 3,0,5 Terminating conversational call 3,0,6 Terminating streaming call 3,0,7 Terminating interactive call 3,0,8 Terminating background call 3,0,9 Emergency call 3,0,10 Inter-RAT cell re-selection 3,0,11 Inter-RAT cell change order 3,0,12 Registration 3,0,13 Detach 3,0,14 Originating High Priority Signalling 3,0,15 Originating Low Priority Signalling 3,0,16 Call re-establishment 3,0,17 Terminating High Priority Signalling 3,0,18 Terminating Low Priority Signalling 3,0,19 Terminating cause unknown Other other causes RRC establishment failure causes: 3,0,0 Congestion 3,0,1 Unspecified NoReply No reply other Other failure cause Cell Percent A50016-G5000-D528-1-7618 ND-57827-701(E)-01

Object Unit/Range Siemens AG: NEC Corporation:

13



Remark

The main difference between call setup and user setup success rate is that with the USSR only the failures due to congestion are supposed to impact the access probability in the user perspective.

2.1.2

RRC Connection Establishments

2.1.2.1Long name

RRC connection establishment success rateRRC connection establishment success rate a) RRC connection establishment success rate (MO call) b) RRC connection establishment success rate (MT call) c) RRC connection establishment success rate (Establishment cause) a) RrcEstabSR b) RrcEstabSR(MO) c) RrcEstabSR(MT) d) RrcEstabSR(EstabCause) This KPI describes the ratio of successful RRC connection establishments related to the total number of RRC connection establishment attempts. rrcEstabSucc[all ] *100% a) RrcEstabSR = rrcEstabAtt[all ] b)

Short name

Description Formula

RrcEstabSR( MO) =

rrcEstabSucc[0 4,9] *100% rrcEstabAtt[0 4,9] rrcEstabSucc[5 8] *100% rrcEstabAtt[5 8] rrcEstabSucc[i ] *100% rrcEstabAtt[i ]

c)

RrcEstabSR( MT ) =

d) Counters

RrcEstabSR( EstabCause) =

rrcEstabSucc[all] rrcEstabAtt[all]RRC establishment causes: 3,0,0 Originating conversational call 3,0,1 Originating streaming call 3,0,2 Originating interactive call 3,0,3 Originating background call 3,0,4 Originating subscribed traffic call 3,0,5 Terminating conversational call 3,0,6 Terminating streaming call 3,0,7 Terminating interactive call 3,0,8 Terminating background call 3,0,9 Emergency call 3,0,10 Inter-RAT cell re-selection 3,0,11 Inter-RAT cell change order 3,0,12 Registration 3,0,13 Detach 3,0,14 Originating High Priority Signaling

14


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



Object Unit/Range Remark

3,0,15 3,0,16 3,0,17 3,0,18 3,0,19 Other Cell Percent

Originating Low Priority Signaling Call re-establishment Terminating High Priority Signaling Terminating Low Priority Signaling Terminating cause unknown other causes

2.1.2.2Long name Short name Description Formula

RRC connection establishment failure ratea) RRC connection establishment failure rate b) RRC connection establishment failure rate (Failure cause) a) RrcEstabFR b) RrcEstabFR(Failure) This KPI describes the ratio of unsuccessful RRC connection establishments related to all RRC connection establishment attempts. rrcEstabFail[all ] *100% a) RrcEstabFR = rrcEstabAtt[all ] b)

RrcEstabFR( Failure) =

rrcEstabFail[i ] *100% rrcEstabAtt[all ]

Counters

rrcEstabAtt[all] rrcEstabFail[all] RRC establishment failure causes: 3,0,0 Congestion 3,0,1 Unspecified NoReply No reply other Other failure cause Cell Percent


2.1.3

RAB EstablishmentsRemark, in UMR2.0 following RAB establishment causes are not supported: 1-0 2-0 3-0 0-1 1-1 CS streaming CS interactive CS background PS conversational PS streaming


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

15



2.1.3.1Long name

RAB establishment success ratea) RAB establishment success rate b) RAB establishment success rate (CS) c) RAB establishment success rate (PS) d) RAB establishment success rate (QoS class) a) RabEstabSR b) RabEstabSR(CS) c) RabEstabSR(PS) d) RabEstabSR(QoS) This KPI describes the ratio of successful RAB establishments related to the total number of RAB establishment attempts. rabEstabSucc[all ] *100% a) RabEstabSR = rabEstabAtt[all ]

Short name

Description Formula

b)

RabEstabSR(CS ) = RabEstabSR( PS ) =

rabEstabSucc[0 3][0] *100% rabEstabAtt[0 3][0] rabEstabSucc[0 3][1] *100% rabEstabAtt[0 3][1] rabEstabSucc[i ] *100% rabEstabAtt[i ]

c)

d) Counters

RabEstabSR(QoS ) =

rabEstabSucc[all] rabEstabAtt[all] RAB establishment causes: 0-0 CS, conversational 1-0 CS, streaming 2-0 CS, interactive 3-0 CS, background 0-1 PS, conversational 1-1 PS, streaming 2-1 PS, interactive 3-1 PS, background Cell Percent


16


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



2.1.3.2Long name

RAB establishment failure ratea) RAB establishment failure rate b) RAB establishment failure rate (CS) c) RAB establishment failure rate (PS) d) RAB establishment failure rate (Failure cause) a) RabEstabFR b) RabEstabFR(CS) c) RabEstabFR(PS) d) RabEstabFR(Failure) This KPI describes the ratio of unsuccessful RAB establishments related to the total number of all RAB establishment attempts rabEstabFail[all ] *100% a) RabEstabFR = rabEstabAtt[all ] b)

Short name

Description Formula

RabEstabFR (CS ) =

rabEstabFail[0][all ] * 100% rabEstabAtt[0 3][0] rabEstabFail[1][all ] * 100% rabEstabAtt[0 3][1] rabEstabFail[i ] *100% rabEstabAtt[all ]

c)

RabEstabFR ( PS ) =

d) Counters

RabEstabFR ( Failure) =

rabEstabAtt[all] rabEstabFail[all] RAB failure rates: 0-2,4,6 CS, Relocation triggered 0-2,4,8 CS, Unabled to establish during relocation 0-2.4.12 CS, Requested ciphering and/or integrity protection algorithms not supported 0-2,4,14 CS, Failure in the radio interface procedure 0-2,4,18 CS, Requested traffic class not available 0-2,4,19 CS, Invalid RAB parameters value 0-2,4,23 CS, Invalid RAB parameters combination 0-2,4,24 CS, Condition violation for SDU parameters 0-2,4,30 CS, Invalid RAB ID 0-2,4,32 CS, Interaction with other procedure 0-2,4,39 CS, Request superseded 0-2,4,66 CS, Iu transport connection failed to establish 0-2,4,97 CS, Transfer syntax error 0-2,4,98 CS, Semantic error 0-2,4,99 CS, Message not compatible with receiver state 0-2,4,100 CS, Abstract syntax error (reject) 0-2,4,101 CS, Abstract syntax error (ignore and notify) 0-2,4,102 CS, Abstract syntax error (falsely constructed message) 0-2,4,114 CS, No ressource available 0-2,4,115 CS, Unspecified failure 0-other CS, Other failure cause 1-2,4,6 PS, Relocation triggered 1-2,4,8 PS, Unabled to establish during relocation 1-2.4.12 PS, Requested ciphering and/or integrity protection algorithms not supported


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

17



1-2,4,14 1-2,4,18 1-2,4,19 1-2,4,23 1-2,4,24 1-2,4,30 1-2,4,32 1-2,4,39 1-2,4,66 1-2,4,97 1-2,4,98 1-2,4,99 1-2,4,100 1-2,4,101 1-2,4,102 1-2,4,114 1-2,4,115 1-other

PS, Failure in the radio interface procedure PS, Requested traffic class not available PS, Invalid RAB parameters value PS, Invalid RAB parameters combination PS, Condition violation for SDU parameters PS, Invalid RAB ID PS, Interaction with other procedure PS, Request superseded PS, Iu transport connection failed to establish PS, Transfer syntax error PS, Semantic error PS, Message not compatible with receiver state PS, Abstract syntax error (reject) PS, Abstract syntax error (ignore and notify) PS, Abstract syntax error (falsely constructed message) PS, No resource available PS, Unspecified failure PS, Other failure cause

RAB establishment causes: 0-0 CS, conversational 1-0 CS, streaming 2-0 CS, interactive 3-0 CS, background 0-1 PS, conversational 1-1 PS, streaming 2-1 PS, interactive 3-1 PS, background Object Unit/Range Remark Cell Percent

2.1.4 2.1.4.1Long name Short name Description

Paging Paging Failure Ratea) Paging Failure Rate in Cell_PCH state b) Paging Failure Rate in URA_PCH state a) PagingFailureCell_PCH b) PagingFailureURA_PCH This KPI describes the ratio of Paging failures, i.e. no response to Paging-type 1 received or receipt of RRC STATUS message in response to Paging-Type 1 indicating protocol error, related to the total number of Pagings in CELL_PCH/URA_PCH state. a)

Formula

PagingFailureCell _ PCH = PagingFailureURA _ PCH =

pagingCellFail[all ] *100% paging1CellUtran[all ] pagingUraFail[all ] *100% paging1UraUtran[all ]A50016-G5000-D528-1-7618 ND-57827-701(E)-01

b) Counters 18

pagingCellFail[all] Siemens AG: NEC Corporation:



paging1CellUtran[all]

Paging failure causes: 3,3,0 ASN.1 violation or encoding error 3,3,1 Message type non-existent or not implemented 3,3,2 Message not compatible with receiver state 3,3,3 Information element value not comprehended 3,3,4 Conditional information element error 3,3,5 Message extension not comprehended NoReply No reply Other Other causes Paging causes in Cell_PCH/URA_PCH state: 3,0,6 Terminating cause unknown Other Other causesObject Unit/Range Remark Cell Percent

2.22.2.1

Connection Release AnalysisCN originated release analysisConnection release analysis CN originated investigates the release causes on connection releases from CN. By these KPIs the normal connection releases and un-normal connection releases i.e. connection release due to failure from CN side or UTRAN side shall be distinguished.

2.2.1.1Long name

Connection Release ratea) Normal Connection release rate b) Unnormal connection release rate c) Connection release rate (Release cause) a) NormalCRR b) UnNormalCRR c) CRR(ReleaseCause) This KPI describes the ratio of normal CN initiated connection releases related to the total number of CN initiated connection releases. iu Re lCmd [10,11,16,31,83] *100% a) NormalCRR = iu Re lCmd [all ] b)

Short name

Description Formula

UnNormalCRR =

iu Re lCmd [15,28,40,45,115, other ] *100% iu Re lCmd [all ] iu Re lCmd [i ] *100% iu Re lCmd [all ]

c) Counters Siemens AG: NEC Corporation:

CRR(Re leaseCause) =

iuRelCmd[all] A50016-G5000-D528-1-7618 ND-57827-701(E)-01

19




Iu release causes: 2,4,10 Relocation Cancelled (Normal) 2,4,11 Successful Relocation (Normal) 2,4,15 Release due to UTRAN Generated Reason (Failure, Initiated by Iu Rel Req) 2,4,16 User inactivity (Normal) 2,4,28 Iu UP failure (Failure) 2,4,31 No Remaining RAB (Normal) 2,4,40 Release due to UE generated signaling connection release (Failure, Initiated by Iu Rel Req) 2,4,45 Directed retry (Failure, Initiated by Iu Rel Req) 2,6,83 Normal Release (Normal) 2,8,115 Unspecified Failure (Failure) Other other cause (Unknown) Cell Percent

2.2.2

UTRAN originated release analysisConnection release analysis UTRAN originated refers only to un-normal releases UTRAN originated i.e. existing connections have been lost at UTRAN side. KPIs in this subsection analyze the connection drop rates by means of release indication toward the CN and the RRC connection drop rate.

2.2.2.1

Connection Drop AnalysisThe un-normal release of a connection UTRAN originated is indicated either by the RAB RELEASE REQUEST message or the IU RELEASE REQUEST message transmitted from the RNC to the CN. The RAB RELEASE REQUEST message will be used when the failure occurs in the RAB management as e.g. firmware failure PRLC, DHT,... In any case the UE is still reachable via a RRC connection. The IU RELEASE REQUEST message is used in case the UE is lost at the air interface. The CN will response either with the RANAP message RAB ASSIGNMENT REQUEST indicating the RAB to be released if another parallel transaction is still ongoing or with the IU RELEASE COMMAND message.iuRelCmd iuRelReq

RNC

iuRelReq

MSC

Fig. 2.1 20

Release Request message and command flow Siemens AG: NEC Corporation: A50016-G5000-D528-1-7618 ND-57827-701(E)-01



For evaluation of the connection drop rates following aspects have to be considered impacting the KPI result:

If the dropped connection was related to a call or to a signaling connection, which was established for registration or signaling, cannot be distinguished. I.e. service related call drops, which are intentionally preferred to measure, cannot be distinguished from RRC connections dropped by UTRAN. In case the transmitted RAB RELEASE REQUEST message from the RNC to the CN will be acknowledged by the RAB ASSIGNMENT REQUEST message from the CN because a parallel transaction is still running, the rabRel counter in UMR2.0 will count the same event twice. In case that the established connection is in Softer/Soft handover when the connection loss occur and the RNC transmits the RAB RELEASE REQUEST message the rabRel counter will be incremented in all cells of existing radio links. Thus, including the rabRel counter in the drop rate calculation means that the drop rate is calculated depending the existing radio links and not per RAB establishments.

As a consequence of the falsification by the rabRel counter, the rabRel counter is not considered for the drop analysis toward the CN. Thus, the calculated drop rate is not quite correct but the drops caused from internal RNC failures should be much less compared to the loss of the UE.

2.2.2.1.1

Connection drop ratea) Connection drop rate b) Connection drop rate (CS) c) Connection drop rate (PS) d) Connection drop rate (Drop cause) a) ConDR b) ConDR(CS) c) ConDR(PS) d) ConDR(DropCause) This KPI describes the ratio between the number of abnormal call releases and the number of released calls. iu Re l Re q[0][14,15,28,37,40,46,113, other ] + a)

Long name

Short name

Description Formula

ConDR =

iu Re l Re q[1][14,15,28,37,40,46,113, other ] iu Re lCmd [all ]

*100%

b)

ConDR(CS ) =

iu Re l Re q[0][14,15,28,37,40,46,113, other ] *100% iu Re lCmd [0][all ] iu Re l Re q[1][14,15,28,37,40,46,113, other ] *100% iu Re lCmd [1][all ] iu Re l Re q[i ] *100% iu Re lCmd [all ]

c)

ConDR( PS ) =

d) Counters

ConDR( DropCause) =

iuRelReq[i] iuRelCmd[all] A50016-G5000-D528-1-7618 ND-57827-701(E)-01


21




Iu release request causes: 0-2,4,14 CS, Failure in the Radio IF Procedure 0-2,4,15 CS, Release due to UTRAN generated reason 0-2,4,16 CS, User inactivity 0-2,4,28 CS, Iu UP failure 0-2,4,37 CS, Repeated Integrity checking fail 0-2,4,40 CS, Release due to UE generated signaling connection release 0-2,4,45 CS, Directed retry 0-2,4,46 CS, Radio connection with UE lost 0-2,8,113 CS, O&M intervention 0-Other CS, Other cause 1-2,4,14 PS, Failure in the Radio IF Procedure 1-2,4,15 PS, Release due to UTRAN generated reason 1-2,4,16 PS, User inactivity 1-2,4,28 PS, Iu UP failure 1-2,4,37 PS, Repeated Integrity checking fail 1-2,4,40 PS, Release due to UE generated signaling connection release 1-2,4,45 PS, Directed retry 1-2,4,46 PS, Radio connection with UE lost 1-2,8,113 PS, O&M intervention 1-Other PS, Other cause Cell Percent

2.2.2.2

RRC Drop AnalysisRRC drop describes the loss of a RRC connection with exceptional cause.

22


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



2.2.2.2.1

RRC drop ratea) RRC drop rate b) RRC drop rate (Drop cause) a) RRCDR b) RRCDR(DropCause) This KPI describes the ratio between the number of abnormal RRC connection releases and the number of successful established RRC connections. rrc Re lDcch[1 4, other ] + rrc Re lCcch[1 4, other ] *100% a) RRCDR = rrcEstabSucc[all ] b)

Long name Short name Description Formula

RRCDR ( DropCause) =

rrc Re lDcch[i ] + rrc Re lCcch[i ] * 100% rrcEstabSucc[all ]

Counters

rrcEstabSucc[all] rrcRelDcch[i] rrcRelCcch[i] RRC release causes: 3,0,0 Normal event 3,0,1 Unspecified 3,0,2 Pre-emptive release 3,0,3 Congestion 3,0,4 Re-establishment reject 3,0,5 Directed signaling connection re-establishment 3,0,6 User inactivity other Other release cause Cell Percent


2.3

RRC State Transitions

2.3.1Long name a) b) c) d) e) f) g) h) a) b) c) d) e)

State transition failure rateCell_DCH state transition failure rate (Target state) Cell_FACH state transition failure rate (Target state) Cell_PCH state transition failure rate (Target state) URA_PCH state transition failure rate (Target state) Cell_DCH state transition failure rate (Target state, Failure cause) Cell_FACH state transition failure rate (Target state, Failure cause) Cell_PCH state transition failure rate (Target state, Failure cause) URA_PCH state transition failure rate (Target state, Failure cause) Cell_DCHSTFR(Target) Cell_FACHSTFR(Target) Cell_PCHSTFR(Target) URA_PCHSTFR(Target) Cell_DCHSTFR(Target,Failure) A50016-G5000-D528-1-7618 ND-57827-701(E)-01

Short name


23



Descriptio n Formula

f) Cell_FACHSTFR(Target,Failure) g) Cell_PCHSTFR(Target, Failure) h) URA_PCHSTFR(Target,Failure) This KPI describes the ratio of unsuccessful State transitions from the originating state to the individual target state per failure cause related to the number of State transition attempts. transFromCellDchFail[1][all ] *100% a) Cell _ DCHSTFR (1) = transFromCellDchAtt[1] b)

Cell _ FACHSTFR(0,2,3) =

transFromCellFachFail[0,2,3][all ] *100% transFromCellFachAtt[0,2,3]

c)

Cell _ PCHSTFR(1) =

transFromCellPchFail[1][all ] * 100% transFromCellPchAtt[1]transFromUraPchFail[1][all ] * 100% transFromUraPchAtt[1] transFromCellDchFail[1][i ] * 100% transFromCellDchAtt[1] transFromCellFachFail[0,2,3][i ] * 100% transFromCellFachAtt[0,2,3]

d)

URA _ PCHSTFR (1) =

e)

Cell _ DCHSTFR (1, Failure) =

f)

Cell _ FACHSTFR (0,2,3, Failure) =

g)

Cell _ PCHSTFR (1, Failure) =

transFromCellPchFail[1][i ] * 100% transFromCellPchAtt[1] transFromUraPchFail[1][i ] * 100% transFromUraPchAtt[1]

h) Counters

URA _ PCHSTFR (1, Failure) =

transFromCell****Att[Target] transFromCell****Fail[Target][all]

State transition failure causes: 3,2,0 Configuration unsupported 3,2,1 Physical channel failure 3,2,2 Incompatible simultaneous reconfiguration 3,2,3 Protocol error 3,2,4 Compressed mode runtime error 3,2,5 Cell update occurred 3,2,6 Invalid configuration 3,2,7 Configuration incompatible NoReply No reply Other Other causes Target states: 0 1 2 3Object

CELL_DCH CELL_FACH CELL_PCH URA_PCH

Cell RNC for transitions from URA_PCH state Siemens AG: NEC Corporation: A50016-G5000-D528-1-7618 ND-57827-701(E)-01

24



Unit/Rang e Remark

Percent

2.42.4.1

Channel Reconfiguration AnalysisTransport Channel Reconfiguration


Transport Channel Reconfiguration success rateTransport Channel reconfiguration success rate TChReconfSR This KPI describes the ratio of successful transport channel reconfigurations related to total number of transport channel reconfiguration attempts.

TCh Re confSR =traChReconfSucc traChReconfAttCell Percent

traCh Re confSucc * 100% traCh Re confAtt

Counters



A50016-G5000-D528-1-7618 ND-57827-701(E)-01

25




Transport Channel Reconfiguration failure ratea) Transport Channel reconfiguration failure rate b) Transport Channel reconfiguration failure rate (Failure cause) a) TChReconfFR b) TChReconfFR(Fail) This KPI describes the ratio of unsuccessful transport channel reconfigurations related to total number of transport channel reconfiguration attempts. traCh Re confFail[all ] *100% a) TCh Re confFR = traCh Re confAtt b)

TCh Re confFR( Fail ) =

traCh Re confFail[i ] * 100% traCh Re confAtt

Counters

traChReconfFail[all] traChReconfAtt Transport channel reconfiguration failure causes: 3,2,0 Configuration unsupported 3,2,1 Physical channel failure 3,2,2 Incompatible simultaneous reconfiguration 3,2,3 Protocol error 3,2,4 Compressed mode runtime error 3,2,5 Cell update occurred 3,2,6 Invalid configuration 3,2,7 Configuration incompatible NoReply No reply Other Other causes


Cell Percent

26


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



2.4.2

Physical Channel Reconfiguration

2.4.2.1Long name Short name Description Formula Counters

Physical Channel Reconfiguration success ratePhysical Channel reconfiguration success rate PhyChReconfSR This KPI describes the ratio of successful physical channel reconfigurations related to total number of physical channel reconfiguration attempts.

PhyCh Re confSR =phyChReconfSucc phyChReconfAttCell Percent

phyCh Re confSucc *100% phyCh Re confAtt



Physical Channel Reconfiguration failure ratea) Physical Channel reconfiguration failure rate b) Physical Channel reconfiguration failure rate (Failure cause) a) PhyChReconfFR b) PhyChReconfFR(Fail) This KPI describes the ratio of unsuccessful physical channel reconfigurations related to total number of physical channel reconfiguration attempts. phyCh Re confFail[all ] *100% a) PhyCh Re confFR = phyCh Re confAtt b)

PhyCh Re confFR( Fail ) =

phyCh Re confFail[i ] * 100% phyCh Re confAtt

Counters

phyChReconfFail[all] phyChReconfAtt Physical channel reconfiguration failure causes: 3,2,0 Configuration unsupported 3,2,1 Physical channel failure 3,2,2 Incompatible simultaneous reconfiguration 3,2,3 Protocol error 3,2,4 Compressed mode runtime error 3,2,5 Cell update occurred 3,2,6 Invalid configuration 3,2,7 Configuration incompatible NoReply No reply Other Other causes

Object Unit/Range Remark Siemens AG: NEC Corporation:

Cell Percent

A50016-G5000-D528-1-7618 ND-57827-701(E)-01

27



3 Connection Mobility3.13.1.1Long name Short name Description Formula

UTRAN updatesUpdate ratea) Cell update rate (Update cause) b) URA update rate (Update cause) a) CellUpdateRate(UpdateCause) b) URAUpdateRate(UpdateCause) This KPI describes the ratio of cell/ura updates per update cause related to the total number of cell/ura updates. cellUpdate[i ] *100% a) CellUpdateRate(UpdateCause) = cellUpdate[all ] b)

UraUpdateRate(UpdateCause) =

uraUpdate[i] *100% uraUpdate[all ]

Counters

cellUpdate[all] uraUpdate[all] Cell update causes: 3,0,0 Cell reselection 3,0,1 Periodical cell update 3,0,2 Uplink data transmission 3,0,3 Paging response 3,0,4 Re-entered service area 3,0,5 Radio link failure 3,0,6 RLC unrecoverable error Other Other cause URA update causes: 3,0,0 Change of URA 3,0,1 Periodic URA update 3,0,2 Re-entered service area Other Other cause Cell Percent


28


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



3.23.2.1

Relocation PreparationOutgoing Relocations


Relocation success rate outgoinga) Relocation success rate outgoing b) Relocation success rate outgoing(Relocation cause) a) RelocOutSR b) RelocOutSR(RelocationCause) This KPI describes the ratio of successful outgoing relocations related to the total number of outgoing relocation attempts. relocOutSucc[all ] a) Re locOutSR = * 100% relocOutAtt[all ] b)

Re locOutSR(Re locationCause) =

relocOutSucc[i ] * 100% relocOutAtt[i ]

Counters

relocOutSucc[all] relocOutAtt[all] Relocation causes: 2,4,41 Resource optimisation relocation 2,4,43 Relocation desirable for radio reasons 2,4,45 Directed Retry other other causes RNC Percent


3.2.1.2Long name

Relocation failure rate outgoinga) Relocation failure rate outgoing b) Relocation failure rate outgoing (Relocation failure cause) a) RelocOutFR b) RelocOutFR(RelocationFailureCause) This KPI describes the ratio of unsuccessful outgoing relocations related to the total number of outgoing relocation attempts. relocOutFail[all ] a) Re locOutFR = * 100% relocOutAtt[all ] b)

Short nameDescription Formula

Re locOutFR(Re locationFailureCause) =

relocOutFail[i ] * 100% relocOutAtt[all ]

Counters

relocOutFail[all] relocOutAtt[all]


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

29



Relocation failure causes: 2,4,7 TRELOCalloc expiry 2,4,9 Unknown target RNC 2,4,10 relocation cancelled 2,4,29 relocation failure in Target CN or target system 2,4,44 relocation not supported in target system Other other failure cause during relocation preparation Object Unit/Range Remark RNC Percent

3.2.2

Incoming Relocations


Relocation success rate incominga) Relocation success rate incoming b) Relocation success rate incoming (Relocation cause) a) RelocIncSR b) RelocIncSR(RelocationCause) This KPI describes the ratio of successful incoming relocations related to the total number of incoming relocation attempts. relocIncSucc[all ] a) Re locIncSR = * 100% relocIncAtt[all ] b)

Re locIncSR(Re locationCause) =

relocIncSucc[i ] * 100% relocIncAtt[i ]

Counters

relocIncSucc[all] relocIncAtt[all] Relocation causes: 2,4,41 Resource optimisation relocation 2,4,43 Relocation desirable for radio reasons 2,4,45 Directed Retry other other causes RNC Percent


30


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



3.3

Soft Handover

3.3.1

Branch addition success ratea) Per cell related measurements:

Long name

Short name

Description Formula

a) Branch addition success rate b) Branch addition success rate (Intra Node B) c) Branch addition success rate (Intra RNC) d) Branch addition success rate (InterRNC) e) Branch addition success rate (Addition cause) f) Intra Node B branch addition success rate (Addition cause) g) Intra RNC branch addition success rate (Addition cause) h) Inter RNC branch addition success rate (Addition cause) a) BranchAddSR b) BranchAddSR(IntraNodeB) c) BranchAddSR(IntraRNC) d) BranchAddSR(InterRNC) e) BranchAddSR(Addition cause) f) IntraNBBranchAddSR(AdditionCause) g) IntraRNCBranchAddSR(AdditionCause) h) InterRNCBranchAddSR(AdditionCause) This KPI describes the ratio of successful branch additions related to the total number of branch addition attempts. shoAddIntraNodeBSucc[all ] +

a)

shoAddIntraRncSucc[all ] + shoAddInterRncSucc[all ] * 100% BranchAddSR = shoAddIntraNodeBAtt[all ] + shoAddIntraRncAtt[all ] + shoAddInterRncAtt[all ]

b)

BranchAddSR( IntraNodeB) =

shoAddIntraNodeBSucc[all ] * 100% shoAddIntraNodeBAtt[all ]

c)

BranchAddSR( IntraRNC ) =

shoAddIntraRncSucc[all ] * 100% shoAddIntraRncAtt[all ] shoAddInterRncSucc[all ] * 100% shoAddInterRncAtt[all ] shoAddIntraNodeBSucc[i ] + shoAddIntraRncSucc[i ] +

d)

BranchAddSR( InterRNC ) =

e)

BranchAddSR( AdditionCause) =

shoAddInterRncSucc[i ] * 100% shoAddIntraNodeBAtt[i ] + shoAddIntraRncAtt[i ] + shoAddInterRncAtt[i ]


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

31



f)

IntraNBBranchAddSR( AdditionCause) =

shoAddIntraNodeBSucc[i ] *100% shoAddIntraNodeBAtt[i ] shoAddIntraRncSucc[i ] *100% shoAddIntraRncAtt[i ] shoAddInterRncSucc[i ] *100% shoAddInterRncAtt[i ]

g)

IntraRNCBranchAddSR( AdditionCause) =

h)

InterRNCBranchAddSR( AdditionCause) =

Counters

shoAddIntraNodeBSucc[all] shoAddIntraRncSucc[all] shoAddInterRncSucc[all] shoAddIntraNodeBAtt[all] shoAddIntraRncAtt[all] shoAddInterRncAtt[all] SHO addition cause: 1,0,1 CPICH comparison (1A) 1,0,2 CPICH comparison (1A) 1,0,4 CPICH comparison (1C) Other other causes


Cell Percent Remark, the measured object is the cell, which has been added to the active link (set).

b) Per adjacent cell related measurements: Long name Short name Description Formula a) a) Branch addition success rate (Cell related) b) Branch addition success rate (ACR) a) BranchAddSRACR(Cell) b) BranchAddSRACR(ACR) This KPI describes the ratio of successful branch additions related to the total number of branch addition attempts per adjacent cell measurement.

shoMoveOutSucc BranchAddSRACR(Cell ) = * 100% shoMoveOutAttACR ACR

b) Counters

BranchAddSRACR( ACR) =

shoMoveOutSucc * 100% shoMoveOutAtt

shoMoveOutSucc shoMoveOutAtt a) Cell b) Adjacent cell Percent a) This calculation provides the cell related branch addition success rate. I.e. the success rate belongs to the added cell from all cell relations. b) This calculation provides the adjacent cell related branch addition success rate. Calculation of the success rate per individual cell relation. Siemens AG: NEC Corporation: A50016-G5000-D528-1-7618 ND-57827-701(E)-01


32



Remark, the measured object in both cases is the cell, which has been added to the active link set.

3.3.2

Branch addition failure ratea) Per cell related measurements:

Long name

Short name

Description Formula

a) Branch addition failure rate b) Branch addition failure rate (Intra Node B) c) Branch addition failure rate (Intra RNC) d) Branch addition failure rate (Inter RNC) e) Branch addition failure rate (Failure cause) f) Intra Node B branch addition failure rate (Failure cause) g) Intra RNC branch addition failure rate (Failure cause) h) Inter RNC branch addition failure rate (Failure cause) a) BranchAddFR b) BranchAddFR(IntraNodeB) c) BranchAddFR(IntraRNC) d) BranchAddFR(InterRNC) e) BranchAddFR(FailureCause) f) IntraNBBranchAddFR(FailureCause) g) IntraRNCBranchAddFR(FailureCause) h) InterRNCBranchAddFR(FailureCause) These KPIs describes the ratio of unsuccessful branch additions related to the total number of branch addition attempts. shoAddIntraNodeBFail[all ] +

a)

shoAddIntraRncFail[all ] + shoAddInterRncFail[all ] * 100% BranchAddFR = shoAddIntraNodeBAtt[all ] + shoAddIntraRncAtt[all ] + shoAddInterRncAtt[all ]BranchAddFR( IntraNodeB ) = shoAddIntraNodeBFail[all ] * 100% shoAddIntraNodeBAtt[all ]

b)

c)

BranchAddFR( IntraRNC ) =

shoAddIntraRncFail[all ] * 100% shoAddIntraRncAtt[all ] shoAddInterRncFail[all ] * 100% shoAddInterRncAtt[all ]

d)

BranchAddFR( InterRNC ) =


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

33



e)

shoAddIntraNodeBFail[i ] + shoAddIntraRncFail[i ] + shoAddInterRncFail[i ] * 100% BranchAddFR( FailureCause) = shoAddIntraNodeBAtt[all ] + shoAddIntraRncAtt[all ] + shoAddInterRncAtt[all ] IntraNBBranchAddFR ( FailureCause) = shoAddIntraNodeBFail[i ] * 100% shoAddIntraNodeBAtt[all ]

f)

g)

IntraRNCBranchAddFR( FailureCause) =

shoAddIntraRncFail[i ] *100% shoAddIntraRncAtt[all ]

h)

InterRNCBranchAddFR( FailureCause) =

shoAddInterRncFail[i ] * 100% shoAddInterRncAtt[all ]

Counters

shoAddIntraNodeBFail[all] shoAddIntraRncFail[all] shoAddInterRncFail[all] shoAddIntraNodeBAtt[all] shoAddIntraRncAtt[all] shoAddInterRncAtt[all]

SHO failure causes. 6,4,0 Unknown C-Id 6,4,1 Cell not available 6,4,2 Power Level not supported 6,4,3 DL Radio Resources not available 6,4,4 UL Radio Resources not available 6,4,5 RL already activated/allocated 6,4,6 Node B Resources unavailable 6,4,7 Combining resources not available 6,4,8 Requested Configuration not supported 6,4,9 Unspecified (Radio Network Layer Cause) 6,4,10 Measurement temporarily not available 6,4,11 Invalid CM Settings 6,4,12 Reconfiguration CFN not elapsed 6,4,13 Number of DL codes not supported 6,4,14 Combining not supported 6,4,15 UL SF not supported 6,4,16 DL SF not supported 6,4,17 Dedicated transport channel type not supported 6,4,18 CM not supported 6,4,19 UL Scrambling Code Already in use 6,4,20 Transaction not supported by Destination Node B 6,4,21 Number of UL codes not supported 6,5,0 Transport resources unavailable 6,5,1 Unspecified (Transport Layer Cause)34 Siemens AG: NEC Corporation: A50016-G5000-D528-1-7618 ND-57827-701(E)-01




6,7,0 Transfer Syntax Error 6,7,1 Abstract Syntax Error (Reject) 6,7,2 Abstract Syntax Error (Ignore and Notify) 6,7,3 Message not compatible with Receiver State 6,7,4 Semantic Error 6,7,5 Unspecified (Protocol Cause) 6,7,6 Abstract Syntax Error (Falsely Constructed Message) 6,8,0 Control processing overload 6,8,1 HW failure 6,8,2 O&M Intervention 6,8,3 Not enough User Plane Processing Resources 6,8,4 Unspecified (Miscellaneous Cause) 3,2,0 Configuration unsupported 3,2,1 Physical channel failure 3,2,2 Incompatible simultaneous reconfiguration 3,2,3 Protocol error 3,2,4 Compressed mode runtime error 3,2,5 Cell reselection 3,2,6 Invalid configuration 3,2,7 Configuration incomplete 3,2,8 Unsupported measurement NoReply No reply Other other causes Cell Percent Remark, the measured object is the cell, which has been added to the active link set.

b) Per adjacent cell related measurements: Long name a) Branch addition failure rate (Cell related) b) Branch addition failure rate (ACR) c) Branch addition failure rate (Cell,Failure cause) d) Branch addition failure rate (ACR,Failure cause) a) BranchAddFRACR(Cell) b) BranchAddFRACR(ACR) c) BranchAddFRACR(Cell,FailureCause) d) BranchAddFRACR(ACR,FailureCause) This KPI describes the ratio of unsuccessful branch additions per adjacent cell related to the total number of branch addition attempts. a)

Short name

Description Formula

shoMoveOutFail[all ] BranchAddFRACR (Cell ) = * 100% shoMoveOutAttACR ACR

b)

BranchAddFRACR( ACR) =

shoMoveOutFail[all ] * 100% shoMoveOutAtt

c)

shoMoveOutFail[i] BranchAddFRACR(Cell , FailureCause) = *100% shoMoveOutAttACR ACR


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

35



d) Counters

BranchAddFRACR( ACR, FailureCause) =

shoMoveOutFail[i ] * 100% shoMoveOutAtt

shoMoveOutFail[all] shoMoveOutAtt Failure causes same as for measurements per cell. a) c) Cell b) d) Adjacent cell Percent a) c) These calculations provide the cell related branch addition failure rate. I.e. the failure rate belongs to the added cell from all cell relations. b) d) These calculations provide the adjacent cell related branch addition failure rate. Calculation of the failure rate per individual cell relation. Remark, the measured object is the cell, which has been added to the active link set.


36


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



3.4

Hard HandoverWithin UMR2.0, only intra Node B inter-frequency Hard Handovers are considered.

3.4.1Long name Short name Description Formula

Outgoing Hard Handover success ratea) Outgoing Hard Handover success rate (Intra Node B) b) Intra Node B outgoing Hard Handover success rate (Handover cause) a) HHOSR(IntraNB) b) IntraNBHHOSR(HandoverCause) This KPI provides the ratio between successful outgoing circuit switched hard handover related to the attempted outgoing circuit switched hard handover. hhoAllOutSucc[1][all ] a) HHOSR( IntraNB ) = * 100% hhoAllOutAtt[1][all ]

b)

IntraNBHHOSR ( HandoverCause) =

hhoAllOutSucc[1][i ] hhoAllOutAtt[1][i ]

* 100%

Counters

hhoAllOutSucc[type][all] hhoAllOutAtt[type][all]

HHO cause: 1,0,0 Load control 2,4,43 Relocation desirable for radio reasons Other other causeHHO type: 1 Cell Percent

Intra Node B



A50016-G5000-D528-1-7618 ND-57827-701(E)-01

37



3.4.2Long name Short name Description

Outgoing Hard Handover failure ratea) Outgoing Hard Handover failure rate (Intra Node B) b) Intra Node B outgoing Hard Handover failure rate (Failure cause) a) HHOFR(IntraNB) b) IntraNBHHOFR(FailureCause) This KPI provides the ratio between unsuccessful outgoing circuit switched hard handover related to the attempted outgoing circuit switched hard handover. Handover failure describes unsuccessful handovers with the reconnection to the originating cell. hhoAllOutFail[1][0 8, other ] *100% a) HHOFR( IntraNB ) = hhoAllOutAtt[1][all ] b)

Formula

IntraNBHHOFR( FailureCause) =

hhoAllOutFail[1][i ] *100% hhoAllOutAtt[1][all ]

Counters

hhoAllOutFail[type][all] hhoAllOutAtt[type][all]

HHO failure causes: 3,2,0 Configuration unsupported 3,2,1 physical channel failure 3,2,2 incompatible simultaneous reconf. 3,2,3 protocol error 3,2,4 compressed mode runtime error 3,2,5 cell reselection 3,2,6 invalid configuration 3,2,7 configuration incomplete 3,2,8 unsupported measurement NoReply no reply Other other failure causeHHO type: 1 Cell Percent

Intra Node B


38


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



3.4.3Long name Short name Description

Outgoing Hard Handover drop rateOutgoing Hard Handover drop rate (Intra Node B) HHODR(IntraNB) This KPI provides the hard handover drop rate. Handover drop describes unsuccessful handovers without reconnection to originating cell, i.e. with loss of call. hhoAllOutFail[1][ No Re ply ] HHODR( IntraNB) = *100% hhoAllOutAtt[1][all ] hhoAllOutFail[type][all] hhoAllOutAtt[type][all]

Formula

Counters

HHO failure causes: 3,2,0 Configuration unsupported 3,2,1 physical channel failure 3,2,2 incompatible simultaneous reconf. 3,2,3 protocol error 3,2,4 compressed mode runtime error 3,2,5 cell reselection 3,2,6 invalid configuration 3,2,7 configuration incomplete 3,2,8 unsupported measurement NoReply no reply Other other failure causeHHO type: 1 Intra Node B Cell Percent



A50016-G5000-D528-1-7618 ND-57827-701(E)-01

39



3.53.5.1

Inter-System (Inter-RAT) HandoverRelocation Preparation (ACM)

3.5.1.1

Relocation Preparation failure rate

Long name a) Relocation Preparation failure rate b) Relocation Preparation failure rate (Relocation Failure cause) Short a) RelocPrepFRpACM name b) RelocPrepFRpACM(RelocationFailure) Description This KPI provides the Relocation Preparation failure rate per adjacent inter RAT cell. Formula int erRatHoOut Re locFail[all ] *100% a) Re loc Pr epFRpACM = int erRatHoOut Re locAtt[all ] b)

Re loc Pr epFRpACM (RelocationFailure) =

int erRatHoOut Re locFail[i ] *100% int erRatHoOut Re locAtt[all ]

Counters

interRatHoOutRelocFail[all] interRatHoOutRelocAtt[all] Inter-system relocation failure cause: 2,4,7 TRELOCalloc expiry 2,4,9 Unknown target RNC 2,4,10 relocation cancelled 2,4,29 relocation failure in Target CN or target system 2,4,44 relocation not supported in target system Other other failure cause during relocation preparation

Object Adjacent GSM Cell Unit/Range Percent Remark These calculations provide the adjacent inter system cell related relocation preparation failure rate. I.e. calculation of the failure rate per individual UTRAN to inter system cell relation.

40


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



3.5.2

Outgoing circuit switched Inter-System Handover

3.5.2.1

Outgoing CS Inter System Handover success ratea) Per adjacent inter system cell:


a) Outgoing CS Inter System Handover success rate b) Outgoing CS Inter System Handover success rate (Handover cause) a) ISHOOutCSSRpACM b) ISHOOutCSSRpACM(HandoverCause) This KPI provides the outgoing circuit switched inter RAT handover success rate per adjacent inter Rat cell. int erRatHoOutSucc[all ] *100% a) ISHOOutCSSRpACM = int erRatHoOutAtt[all ] b)

ISHOOutCSSRpACM ( HandoverCause) =

int erRatHoOutSucc[i ] *100% int erRatHoOutAtt[i ]

Counters

interRatHoOutSucc[all] interRatHoOutAtt[all] Inter-System HHO cause: 2,4,43 Relocation desirable for radio reasons other other cause Adjacent GSM Cell Percent These calculations provide the adjacent cell related inter system handover success rate. I.e. calculation of the success rate per individual UTRAN to inter system cell relation.


b) Per cell: Long name Short name Description Formula a) Outgoing CS Inter System Handover success rate b) Outgoing CS Inter System Handover success rate (Handover cause) a) ISHOOutCSSRpCell b) ISHOOutCSSRpCell(HandoverCause) This KPI provides the outgoing circuit switched inter RAT handover success rate. hhoAllOutSucc[5][all ] *100% a) ISHOOutCSSRpCell = hhoAllOutAtt[5][all ] b) Counters

ISHOOutCSSRpCell ( HandoverCause) =

hhoAllOutSucc[5][i ] *100% hhoAllOutAtt[5][i ]

hhoAllOutSucc[type][all] hhoAllOutAtt[type][all] Inter-System HHO cause: 2,4,43 Relocation desirable for radio reasons Other Other cause


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

41




HHO type: 5 Cell Percent

Inter System

3.5.2.2

Outgoing CS Inter System Handover failure ratea) Per adjacent GSM cell:

Long name a) Outgoing CS Inter System Handover failure rate b) Outgoing CS Inter System Handover failure rate (Handover Failure cause) Short a) ISHOOutCSFRpACM name b) ISHOOutCSFRpACM(HandoverFailureCause) Description This KPI provides the outgoing circuit switched inter RAT handover failure rate per adjacent inter Rat cell. Handover failure describes unsuccessful handovers with re-connection to originating cell Formula int erRatHoOutFail[0,1,2,3, other ] *100% a) ISHOOutCSFRpACM = int erRatHoOutAtt[all ] b)

ISHOOutCSFRpACM ( HandoverFailureCause) =

int erRatHoOutFail[i ] *100% int erRatHoOutAtt[all ]

Counters

interRatHoOutFail[all] interRatHoOutAtt[all] Inter-System HHO failure cause: 3,1,0 Configuration unsupported 3,1,1 Physical channel failure 3,1,2 Protocol error 3,1,3 Inter-RAT protocol error NoReply No reply other Other causes

Object Adjacent GSM Cell Unit/Range Percent Remark These calculations provide the adjacent cell related inter system handover failure rate. I.e. calculation of the failure rate per individual UTRAN to inter system cell relation.

42


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



b) Per cell: Long name Short name Description a) Outgoing CS Inter System Handover failure rate b) Outgoing CS Inter System Handover failure rate (Handover Failure cause) a) ISHOOutCSFRpCell b) ISHOOutCSFRpCell(HandoverFailureCause) This KPI provides the outgoing circuit switched inter RAT handover failure rate. Handover failure describes unsuccessful handovers with re-connection to originating cell hhoAllOutFail[5][0,1,2,3, other ] *100% a) ISHOOutCSFRpCell = hhoAllOutAtt[5][all ] b)

Formula

ISHOOutCSFRpCell ( HandoverFailureCause) =

hhoAllOutFail[5][i ] *100% hhoAllOutAtt[5][all ]

Counters

hhoAllOutFail[type][i] hhoAllOutAtt[type][all] Inter-System HHO failure cause: 3,1,0 Configuration unsupported 3,1,1 Physical channel failure 3,1,2 Protocol error 3,1,3 Inter-RAT protocol error NoReply No reply other Other causes HHO type: 5 Cell Percent

Inter System



A50016-G5000-D528-1-7618 ND-57827-701(E)-01

43



3.5.2.3

Outgoing CS Inter System Handover drop ratea) Per adjacent GSM cell:

Long name Short name Description

Formula

Outgoing CS Inter System Handover drop rate ISHOOutCSDRpACM This KPI provides the outgoing circuit switched inter RAT handover drop rate per adjacent inter Rat cell. Handover drop describes unsuccessful handovers without re-connection to originating cell, i.e. with loss of call. int erRatHoOutFail[ No Re ply ] ISHOOutCSDRpACM = * 100% int erRatHoOutAtt[all ] interRatHoOutFail[i] interRatHoOutAtt[all] Inter-System HHO failure cause: 3,1,0 Configuration unsupported 3,1,1 Physical channel failure 3,1,2 Protocol error 3,1,3 Inter-RAT protocol error NoReply No reply other Other causes Adjacent GSM Cell Percent This calculation provides the adjacent cell related inter system handover drop rate. I.e. calculation of the drop rate per individual UTRAN to inter system cell relation.

Counters


b) Per cell: Long name Short name Description Outgoing CS Inter System Handover drop rate ISHOOutCSDRpCell This KPI provides the outgoing circuit switched inter RAT handover drop rate. Handover drop describes unsuccessful handovers without re-connection to originating cell, i.e. with loss of call. hhoAllOutFail[5][ No Re ply ] ISHOOutCSDRpCell = *100% hhoAllOutAtt[5][all ] hhoAllOutFail[type][i] hhoAllOutAtt[type][all] Inter-System HHO failure cause: 3,1,0 Configuration unsupported 3,1,1 Physical channel failure 3,1,2 Protocol error 3,1,3 Inter-RAT protocol error NoReply No reply other Other causes HHO type: 5 Inter System 44 Siemens AG: NEC Corporation: A50016-G5000-D528-1-7618 ND-57827-701(E)-01

Formula

Counters




Cell Percent


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

45



4 Quality Indicators4.1 PrincipleHigh-level quality indicators are used for the detection of trends in quality and quantity of the UTRAN. The scope for these indicators may vary, depending on the observed region. In all quality indications depicted below the procedure related success rate is defined according the generic indicator below:

A B Indicator = Ci , NE NE i NE i i , NE NE i

i , NE

* 100%

4.2Long name Short name Description Formula

Call establishment quality indicatorCall establishment quality indicator CSQI This KPI gives an overall quality indicator for call establishments. rrcEstabSucc[0 9] rabEstabSucc[all ] CSQI = Cell * Cell *100% rrcEstabAtt[0 9] rabEstabAtt[all ] Cell Cell CSSR(AccessProbability) (see 2.1.1) UTRAN / RNC / NodeB 0% (worst) ..100% (best) Elementary object is depending on the scope of the summarizations

Counters Object Unit/Range Remark


Branch Addition quality indicatorBranch addition quality indicator BranchAddQI This KPI gives an overall quality indicator for soft handover. (shoAddIntraNodeBSucc[all ] + Cell shoAddIntraRncSucc[all ] +

Counters Object 46

shoAddInterRncSucc[all ]) *100% (shoAddIntraNodeBAtt[all ] + Cell shoAddIntraRncAtt[all ] + shoAddInterRncAtt[all ]) BranchAddSR (see 3.3.1) UTRAN / RNC / NodeB BranchAddQI =Siemens AG: NEC Corporation: A50016-G5000-D528-1-7618 ND-57827-701(E)-01



Unit/Range Remark

0% (worst) ..100% (best) Elementary object is depending on the scope of the summarizations


Hard handover quality indicatorHard handover quality indicator HHOQI(IntraNB) This KPI gives an overall quality indicator for hard handover. hhoAllOutSucc[1][all ] *100% HHOQI ( IntraNB ) = Cell hhoAllOutAtt[1][all ] Cell HHOSR (see 3.4.1) UTRAN / RNC / NodeB 0% (worst) ..100% (best) Elementary object is depending on the scope of the summarizations. Only Intra Node B handover supported within UMR2.0.



Inter-System handover quality indicatorInter-System handover quality indicator ISHOQI This KPI gives an overall quality indicator for inter-System handover. hhoAllOutSucc[5][all ] ISHOQI = Cell *100% hhoAllOutAtt[5][all ] Cell ISHOOutCSSRpCell (see 3.5.2.1) UTRAN / RNC / NodeB 0% (worst) ..100% (best) Elementary object is depending on the scope of the summarizations



A50016-G5000-D528-1-7618 ND-57827-701(E)-01

47



5 QuaNTIty Indicators5.15.1.1Long name

RRC State TransitionsNumber of successful state transitionsa) Number of successful state transitions from Cell_DCH state (Target state) b) Number of successful state transitions from Cell_FACH state (Target state) c) Number of successful state transitions from Cell_PCH state (Target state) d) Number of successful state transitions from URA_PCH state (Target state) a) STSuccfromCell_DCH(Target) b) STSuccfromCell_FACH(Target) c) STSuccfromCell_PCH[Target] d) STSuccfromURA_PCH[Target] This indicator will give you the number of successful state transitions from origin state to target state. STSuccfromCell _ DCH (1) = transFromCellDchAtt[1] a) transFromCellDchFail[1][all ] b)

Short name

Description Formula

STSuccfromCell _ FACH [0,2,3] = transFromCellFachAtt[0,2,3] transFromCellFachFail[0,2,3][all ] STSuccfromCell _ PCH [1] = transFromCellPchAtt[1] transFromCellPchFail[1][all ]

c)

Counters

STSuccfromURA _ PCH [1] = transFromUraPchAtt[1] transFromUraPchFail[1][all ] transFrom****Att[Target] transFrom****Fail[Target][all]d)

Target states: 0 1 2 3

CELL_DCH CELL_FACH CELL_PCH URA_PCH

State transition failure causes: See 2.3.1Object Unit/Range Remark Cell RNC - for transitions from URA_PCH state None

48


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



5.1.2

Number of state transitions to Idle modeThis KPI corresponds to the RRC release. See measurement type description in appendix: rrcRelDcch[all] and rrcRelCcch[all]

5.25.2.1Long name Short name Description Formula Counters

Soft HandoverSoft Handover rateSoft handover rate SHORate(RLN) This indicator will give you the percentage rate of UEs with 1, 2 or 3 radio links per active link set size. uesPerActiveLinkSetSize[ RLN ] SHORate( RLN ) = *100% uesPerActiveLinkSetSize[all ] uesPerActiveLinkSetSize[RLN]


Radio Link Numbers: 0 Active Link set size =1 1 Active Link set size = 2 2 Active Link set size = 3 Cell Percent Since in UMR2.0 the periodicity is 5 minutes the actual value of the number of active links per link set size are considered this calculation gives only a rough indication of the soft handover rate.


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

49



5.35.3.1

RelocationsNumber of outgoing relocationsSee measurement type description in appendix: relocOutAtt[all]

5.3.2

Number of incoming relocationsSee measurement type description in appendix: relocIncAtt[all]


Outgoing Relocation per Call rateOutgoing Relocation per call rate RelocperCallRate This KPI describes the ratio of successful outgoing relocations related to the number of established calls. relocOutSucc[all ] Re locperCallRate = *100% rabEstabSucc[all ] Cell relocOutSucc[all] rabEstabSucc[all] Relocation causes: 2,4,41 Resource optimisation relocation 2,4,43 Relocation desirable for radio reasons 2,4,45 Directed Retry other other causes RNC Percent In a normal sequence first the RAB will be established and later on the outgoing relocation may occur. Thus, it may occur that the RAB Establishment may be measured within an earlier GP than the outgoing relocation procedure is measured. This applies especially in case of PS calls. The mean number of outgoing relocations per call should therefore be considered in a greater period, e.g. per day.

Counters


50


A50016-G5000-D528-1-7618 ND-57827-701(E)-01




Hard HandoverOutgoing Hard Handover per call rateOutgoing Hard Handover per call rate HHOperCallRate(NodeB) This indicator gives the ratio between Intra-Node B hard handovers related to the number of Call Setups.

hhoAllOutSucc[1][all ] HHOperCallRate( NodeB) = rabEstabSucc[all ]Cell Cell

Counters

hhoAllOutSucc[type][all] rabEstabSucc[all]

HHO cause: 1,0,0 Load control 2,4,43 Relocation desirable for radio reasons Other other causeHHO type: 1 Intra Node B RNC None In a normal sequence first the RAB will be established and later on the outgoing hard handover may occur. Thus, it may occur that the RAB establishment may be measured within an earlier GP than the outgoing hard handover procedure is measured. This applies especially in case of PS calls. The mean number of outgoing hard handover per call should therefore be considered in a greater period, e.g. per day. In addition it should be considered that by a previous Soft Handover the originating cell of the hard handover may not be the cell where the RAB establishment has been performed and measured. Therefore the Outgoing Hard Handover per call rate should is related to the RNC instead to a cell.



A50016-G5000-D528-1-7618 ND-57827-701(E)-01

51



5.55.5.1

Inter System HandoverOutgoing CS Inter System Handover per call rateIn a normal sequence first the RAB will be established and later on the inter system hard handover may occur. Thus, it may occur that the RAB establishment may be measured within an earlier GP than the outgoing inter system handover procedure is measured. This applies especially in case of PS calls. The mean number of outgoing hard handover per call should therefore be considered in a greater period, e.g. per day. In addition it should be considered that by a previous Soft Handover the originating cell of the hard handover may not be the cell where the RAB establishment has been performed and measured. Therefore the Outgoing Inter System Handover per call rate may be related better to the RNC instead to a cell.


Outgoing CS Inter System Handover per call rate ISHOperCallRate This indicator gives the ratio between inter system handovers related to the number of Call Setups.

hhoAllOutSucc[5][all ] ISHOperCallRate = rabEstabSucc[all ]Cell Cell

Counters

hhoAllOutSucc[type][all] rabEstabSucc[all]

HHO cause: 2,4,43 Relocation desirable for radio reasons Other other causeHHO type: 5 RNC None

Inter System


52


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



6 UtiliZation6.16.1.1

RNC Load ReportRNC Processor LoadSee measurement type description in appendix: rncUsageRatio

6.1.2

DHT usageSee measurement type description in appendix: dhtUsage


DHT allocation success rateDHT allocation success rate DHTAllocSR This indicator provides the DHT allocation success ratio. dhtAllocSucc DHTAllocSR = *100% dhtAllocAtt dhtAllocSucc dhtAllocAtt RNC Percent

Counters


6.1.4

PRLC usageSee measurement type description in appendix: prlcUsage


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

53




PRLC allocation success ratePRLC allocation success rate PRLCAllocSR This indicator provides the PRLC allocation success ratio. prlcAllocSucc PRLCAllocSR = *100% prlcAllocAtt prlcAllocSucc prlcAllocAtt RNC Percent

Counters


6.26.2.1

Node B Load ReportNode B usage rateSee measurement type description in appendix: cpUsageRatio for Node B PF1 and ccProcessorLoad for Node B PF2.

6.2.2

Base Band usage rateSee measurement type description in appendix: bbUsageRatio

6.2.3

Rest of call capacitySee measurement type description in appendix: restOfCallCapacity

54


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



6.36.3.1 6.3.1.1Long name Short name Description Formula

Cell Load ReportCell Utilisation Code usage rateCode usage rate CodeUsageRate This indicator gives the ratio between the sum of used codes per SF related to the total number of usable SF. uuCodesUsed [7] *1 + uuCodesUsed [6] * 2 +

uuCodesUsed [5] * 4 + uuCodesUsed [4] * 8 + uuCodesUsed [3] *16 + uuCodesUsed [2] * 32 + uuCodesUsed [1] * 64 + uuCodesUsed [0] *128 CodeUsageRate = *100% 512Counters uuCodesUsed [all]


Spreading factor parameters: 0 SF4 1 SF8 2 SF16 3 SF32 4 SF64 5 SF128 6 SF256 7 SF512 Cell Percent The indicated code usage rate applies only for DL. Remark also, that SF4 is not supported in UMR2.0. Since in UMR2.0 the periodicity is 5 minutes the actual value of the number of used codes per SF are considered this calculation gives only a rough indication of the code usage rate.


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

55



6.3.2 6.3.2.1Long name Short name Description Formula Counters

Cell load related Radio Measurements Transmitted Carrier powerCell load per Transmitted Carrier power TxCarrierPwr(MMM) This indicator provides the cell load related to the transmitted carrier power. TxCarrierPwr ( MMM ) = uuTransmCarrierPwr[ MMM ] uuTransmCarrierPwr[MMM] MMM: 0 Mean value 1 Minimum value 2 Maximum value Cell Percent The measured value already provides a percentage value.



Received Total Wide Band PowerCell load per Received Total Wide Band Power RxTotalWBPwr(MMM) This indicator provides the cell load related to the received total wide band power. uu Re cTotalWbPwr[ MMM ] RxTotalWBPwr ( MMM ) = *100% 621 uuRecTotalWbPwr[MMM] MMM: 0 Mean value 1 Minimum value 2 Maximum value Cell Percent

Counters


56


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



6.46.4.1

Radio interfaceCommon Channel Load ReportsFor load reports of common channels see measurement type description in appendix:

pchUsageRate pchDiscardRate fachUsageRate fachDiscardRate prachUsageRate sccpchUsageRatio numberOfReceivedPreambles


Code allocation success ratea) Code allocation success rate b) Code allocation success rate(SF) a) CodeAllocSR b) CodeAllocSR(SF) This indicator provides the code allocation success ratio per spreading factor. uuCode Re qSucc[all ] *100% a) CodeAllocSR = uuCode Re qAtt[all ] b)

CodeAllocSR( SF ) =

uuCode Re qSucc[ SF ] *100% uuCode Re qAtt[all ]

Counters

uuCodeReqAtt[all] uuCodeReqSucc[all]


Spreading factor parameters: 0 SF4 1 SF8 2 SF16 3 SF32 4 SF64 5 SF128 6 SF256 7 SF512 Cell Percent The indicated code usage rate applies only for DL. Remark also, that SF4 is not supported in UMR2.0.


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

57



7 Transport Network Layer7.17.1.1Long name Short name Description Formula

ATM-Layer on RNC sideSTM-1 Transmission usage rateSTM-1 transmission usage rate STM1TxUsageRate This indicator provides the ratio between transmitted cells related to maximum number of cell transmissions. lineOutgoingCells lineOutgoingCells STM 1TxUsageRate = = *100% 155Mbit / s max Outgoingcells / line * GP 53 * 8 lineOutgoingCells

Counters


STML Percent


STM-1 Receive usage rateSTM-1 receive usage rate STM1RxUsageRate This indicator provides the ratio between received cells related to maximum number of received cells. lineInco min gCells lineInco min gCells STM 1RxUsageRate = = *100% 155Mbit / s max Inco min gcells / line * GP 53 * 8 lineIncomingCells

Counters


STML Percent

58


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



7.1.3Long name Short name Description Formula Counters

STM-1 Transmit/Receive rateSTM-1 transmit/receive rate STMTxRxRate This indicator provides the asymetry ratio between transmitted and received cells. lineOutgoingCells STMTxRxRate = lineInco min gCells lineOutgoingCells lineIncomingCells STML None



E1 Transmit/Receive rateE1 transmit/receive rate E1TxRxRate This indicator provides the asymmetry ratio between transmitted and received cells. lineOutgoingCells E1TxRxRate = lineInco min gCells lineOutgoingCells lineIncomingCells EL None


7.1.5

Cell Loss RatioSee measurement type description in appendix: cellLossRatio


A50016-G5000-D528-1-7618 ND-57827-701(E)-01

59



7.27.2.1

ATM-Layer on Node B sideCell Loss RatioSee measurement type description in appendix: cellLossRatio


ATM Transmit/Receive rateATM transmit/receive rate ATMTxRxRate This indicator provides the asymmetry ratio between transmitted and received cells. totalNumberOfTransmitCell ATMTxRxRate = totalNumberOf Re ceivingCell totalNumberOfTransmitCell totalNumberOfReceivingCell VP None


60


A50016-G5000-D528-1-7618 ND-57827-701(E)-01



8 Appendix8.1 List of Measurements in RNCMeasurement MeasObjI nstId Class RNC CELL CELL RNC CELL RNC CELL CELL CELL CELL CELL RNC CELL CELL CELL CELL CELL CELL CELL CELL CELL

MeasType description

"paging1Cn." "paging2Cn." "paging1CellUtran." "paging1UraUtran." "pagingCellFail." "pagingUraFail." "rrcEstabAtt." "rrcEstabSucc." "rrcEstabFail." "rrcRelDcch." "rrcRelCcch." "sigConnEstabReq." "sigConnRelReq" "sigConnRelNotif" "rabEstabAtt.." "rabEstabSucc.." "rabEstabFail.-" "rabRel. -" "traChReconfAtt" "traChReconfSucc" "traChReconfFail."

Number of CN originated pagings typ

Utran Kpi Description

Documents

Transcript of Utran Kpi Description