3GPP TS 32.425: Performance Measurements (E-UTRAN)

3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;

Telecommunication management;
Performance Management
(PM);
V10.4.0 (2011-03)
Performance measurements
Technical Specification
Evolved Universal Terrestrial Radio Access Network
(E-UTRAN)
(Release 10)
3GPP TS 32.425
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this
Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 10
3GPP TS 32.425 V10.4.0 (2011-03)
Keywords
E-UTRAN, management, performance
3GPP
Postal address
3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.
UMTS is a Trade Mark of ETSI registered for the benefit of its members
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP
Organizational Partners
GSM and the GSM logo are registered and owned by the GSM Association
3GPP
Release 10
3GPP TS 32.425 V10.4.0 (2011-03)
Contents
Foreword..........................................................................................................................................................
1
Scope......................................................................................................................................................
References..............................................................................................................................................
Measurement family and abbreviations................................................................................................
3.1
3.2
4
4.0
4.1
4.1.1
4.1.1.1
4.1.1.2
4.1.1.3
4.1.1.4
4.1.2
4.1.2.1
4.1.2.2
4.1.2.3
4.1.3
4.1.3.1
4.1.3.2
4.1.4
4.1.4.1
4.1.4.2
4.1.5
4.1.5.1
4.1.5.2
4.2
4.2.1
4.2.1.1
4.2.1.2
4.2.1.3
4.2.1.4
4.2.1.5
4.2.1.6
4.2.1.7
4.2.1.8
4.2.2
4.2.2.1
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6
4.2.3
4.2.3.1
4.2.3.2
4.2.3.3
4.2.4
4.2.4.1
4.2.4.2
4.2.5
4.2.5.1
4.2.5.2
4.3
4.3.1
Measurement family..........................................................................................................................................
Abbreviations.....................................................................................................................................................
Measurements related to eNodeB, Donor eNodeB and Relay Node.....................................................

Applicability of measurements to eNB and DeNB............................................................................................
RRC connection related measurements.............................................................................................................
RRC connection establishment....................................................................................................................
Attempted RRC connection establishments...........................................................................................
Successful RRC connection establishments...........................................................................................
Failed RRC connection establishments..................................................................................................
Failed RRC connection establishment per failure cause........................................................................
RRC connection re-establishment................................................................................................................
Attempted RRC connection re-establishments.......................................................................................
Successful RRC connection re-establishments......................................................................................
Failed RRC connection re-establishments.............................................................................................
RRC connection number..............................................................................................................................
Mean number of RRC Connections.......................................................................................................
Maximum number of RRC Connections................................................................................................
RRC connection setup time..........................................................................................................................
Mean RRC connection setup time..........................................................................................................
Maximum RRC connection setup time..................................................................................................
UE CONTEXT Release...............................................................................................................................
Number of UE CONTEXT Release Request initiated by eNodeB/RN.................................................
Successful UE CONTEXT Release.......................................................................................................
E-RAB related measurements...........................................................................................................................
E-RAB setup................................................................................................................................................
Number of initial E-RABs attempted to setup.......................................................................................
Number of initial E-RABs successfully established..............................................................................
Number of initial E-RABs failed to setup..............................................................................................
Number of additional E-RABs attempted to setup.................................................................................
Number of additional E-RABs successfully established........................................................................
Number of additional E-RABs failed to setup.......................................................................................
Mean E-RAB Setup time........................................................................................................................
Maximum E-RAB Setup time................................................................................................................
E-RAB release..............................................................................................................................................
Number of E-RABs requested to release initiated by eNodeB/RN per QCI.........................................
Number of E-RABs attempted to release...............................................................................................
Number of E-RAB successfully released...............................................................................................
Number of E-RAB failed to release.......................................................................................................
Number of released active E-RABs.......................................................................................................
E-RAB modification....................................................................................................................................
Number of E-RABs attempted to modify the QoS parameter...............................................................
Number of E-RABs successfully modified the QoS parameter.............................................................
Number of E-RABs failed to modify the QoS parameter......................................................................
E-RAB activity.............................................................................................................................................
In-session activity time for UE...............................................................................................................
In-session activity time for E-RABs......................................................................................................
E-RAB number............................................................................................................................................
Average Number of simultaneous E-RABs............................................................................................
Maximum Number of simultaneous E-RABs........................................................................................
Handover related measurements........................................................................................................................
Intra-RAT Handovers...................................................................................................................................
3GPP
Release 10
4.3.1.1
4.3.1.1.1
4.3.1.1.2
4.3.1.1.3
4.3.1.1.4
4.3.1.1.5
4.3.1.2
4.3.1.2.1
4.3.1.2.2
4.3.1.2.3
4.3.1.3
4.3.1.3.1
4.3.1.3.2
4.3.1.3.3
4.3.1.4
4.3.1.4.1
4.3.1.4.2
4.3.1.4.3
4.3.1.4.4
4.3.1.4.5
4.3.1.4.6
4.3.1.5
4.3.1.5.1
4.3.1.5.2
4.3.1.5.3
4.3.1.5.4
4.3.1.6
4.3.1.6.1
4.3.1.6.2
4.3.1.6.3
4.3.1.7
4.3.1.7.1
4.3.1.7.2
4.3.2
4.3.2.1
4.3.2.1.1
4.3.2.1.2
4.4
4.4.1
4.4.1.1
4.4.1.2
4.4.1.3
4.4.1.4
4.4.1.5
4.4.1.6
4.4.2
4.4.2.1
4.4.2.2
4.4.3
4.4.3.1
4.4.3.2
4.4.4
4.4.4.1
4.4.4.2
4.4.5
4.4.5.1
4.4.6
4.4.6.1
3GPP TS 32.425 V10.4.0 (2011-03)
Intra-eNB/RN Handover related measurements....................................................................................

Attempted outgoing intra-eNB/RN handovers per handover cause.................................................
Successful outgoing intra-eNB/RN handovers per handover cause.................................................
Attempted outgoing intra-DeNB handover preparations from DeNB cell to RN per handover
cause.................................................................................................................................................
Attempted outgoing intra-DeNB handover executions from DeNB cell to RN per handover
cause.................................................................................................................................................
Successful outgoing intra-DeNB handover executions from DeNB cell to RN per handover
cause.................................................................................................................................................
Inter-eNB Handover related measurements...........................................................................................
Attempted outgoing inter-eNB handover preparations.....................................................................
Attempted outgoing inter-eNB handover executions per handover cause.......................................
Successful outgoing inter-eNB handover executions per handover cause.......................................
Handover measurements on neighbour cell basis..................................................................................
Attempted outgoing handovers per handover cause.........................................................................
Successful outgoing handovers per handover cause.........................................................................
Number of handover failures related with MRO..............................................................................
Intra- / Inter-frequency Handover related measurements.......................................................................
Attempted outgoing intra-frequency handovers...............................................................................
Successful outgoing intra-frequency handovers...............................................................................
Attempted outgoing inter-frequency handovers gap-assisted measurement.................................
Successful outgoing inter-frequency handovers gap-assisted measurement.................................
Attempted outgoing inter-frequency handovers non gap-assisted measurement..........................
Successful outgoing inter-frequency handovers non gap-assisted measurement..........................
Handover related measurements for DRX / non-DRX..........................................................................
Attempted outgoing handovers with DRX.......................................................................................
Successful outgoing handovers with DRX.......................................................................................
Attempted outgoing handovers non-DRX........................................................................................
Successful outgoing handovers non-DRX........................................................................................
Handover to cells outside the RN related measurements.......................................................................
Attempted preparations of outgoing handovers to the cells outside the RN....................................
Attempted executions of outgoing handover to the cells outside the RN per handover cause.........
Successful executions of outgoing handover to the cells outside the RN per handover cause........
Handover triggering measurements.......................................................................................................
Average quality of the serving cell when HO is triggered................................................................
Average quality of the neighboring cell when HO is triggered........................................................
Inter-RAT Handovers...................................................................................................................................
Measurements related to inter-RAT Handovers target cell of 3GPP and non-3GPP network
technology..............................................................................................................................................
Attempted outgoing inter-RAT handovers per handover cause........................................................
Successful outgoing inter-RAT handovers per handover cause........................................................
Cell level radio bearer QoS related measurements............................................................................................
Cell PDCP SDU bit-rate...............................................................................................................................
Average DL cell PDCP SDU bit-rate.....................................................................................................
Average UL cell PDCP SDU bit-rate.....................................................................................................
Maximum DL cell PDCP SDU bit-rate..................................................................................................
Maximum UL cell PDCP SDU bit-rate..................................................................................................
Average DL cell control plane PDCP SDU bit-rate...............................................................................
Average UL cell control plane PDCP SDU bit-rate...............................................................................
Active UEs...................................................................................................................................................
Average number of active UEs on the DL.............................................................................................
Average number of active UEs on the UL.............................................................................................
Packet Delay and Drop Rate........................................................................................................................
Average DL PDCP SDU delay...............................................................................................................
DL PDCP SDU drop rate........................................................................................................................
Packet loss rate.............................................................................................................................................
DL PDCP SDU air interface loss rate....................................................................................................
UL PDCP SDU loss rate.........................................................................................................................
IP Latency measurements............................................................................................................................
IP Latency in DL, E-RAB level.............................................................................................................
IP Throughput measurements.......................................................................................................................
IP Throughput in DL..............................................................................................................................
3GPP
Release 10
4.4.6.2
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.5.1
4.5.5.2
4.5.5.3
4.5.5.4
4.5.5.5
4.5.5.6
4.5.6
4.5.7
4.5.7.1
4.5.7.2
4.5.7.3
4.5.7.4
4.5.8
4.5.8.1
4.5.8.2
4.5.9
4.5.9.1
4.5.9.2
4.6
4.6.1
4.6.1.1
4.6.1.2
4.7
4.7.1
4.7.1.1
4.7.1.2
4.8
4.8.1
4.8.1.1
4.8.1.2
4.9
4.9.1
4.10
4.10.1
4.10.1.1
4.10.1.2
4.10.2
5
5.1
5.1.1
5.1.1.1
5.1.1.2
3GPP TS 32.425 V10.4.0 (2011-03)
IP Throughput in UL..............................................................................................................................
Radio resource utilization related measurements..............................................................................................
DL PRB Usage for traffic.............................................................................................................................
UL PRB Usage for traffic.............................................................................................................................
DL Total PRB Usage....................................................................................................................................
UL Total PRB Usage....................................................................................................................................
RACH Usage...............................................................................................................................................
Mean number of RACH preambles received.........................................................................................
Distribution of RACH preambles sent...................................................................................................
Distribution of RACH access delay.......................................................................................................
Percentage of contentious RACH attempts............................................................................................
Number of UE RACH reports received.................................................................................................
Percentage of time when all dedicated RACH preambles are used.......................................................
Cell Unavailable Time.................................................................................................................................
TB related measurements.............................................................................................................................
Total Number of DL TBs..................................................................................................................
Error Number of DL TBs..................................................................................................................
Total Number of UL TBs..................................................................................................................
Error Number of UL TBs..................................................................................................................
Power utilization measurements..................................................................................................................
Maximum carrier transmit power...........................................................................................................
Mean carrier transmit power..................................................................................................................
PRB Full Utilisation.....................................................................................................................................
DL PRB full utilisation...........................................................................................................................
UL PRB full utilisation...........................................................................................................................
UE-associated logical S1-connection related measurements............................................................................
UE-associated logical S1-connection establishment....................................................................................
Attempted UE-associated logical S1-connection establishment from eNB to MME............................
Succesful UE-associated logical S1-connection establishment from eNB to MME..............................
Paging related measurements............................................................................................................................
Paging Performance.....................................................................................................................................
Number of paging records discarded at the eNodeB/RN.......................................................................
Number of paging records received by the eNodeB/RN........................................................................
Measurements related to equipment resources..................................................................................................
eNodeB/RN processor usage.......................................................................................................................
Mean processor usage............................................................................................................................
Peak processor usage..............................................................................................................................
Common LAs of overlapping RATs coverage.................................................................................................
Number of incoming IRAT mobility events per LA....................................................................................
RF Measurements..............................................................................................................................................
CQI Distribution..........................................................................................................................................
Wideband CQI distribution....................................................................................................................
Average sub-band CQI...........................................................................................................................
Timing Advance Distribution.......................................................................................................................
Measurements related to Relay Node...................................................................................................

DeNB Reconfiguration related measurements..................................................................................................
RN Reconfiguration.....................................................................................................................................
Number of RNReconfiguration attempts...............................................................................................
Number of RNReconfiguration Completed...........................................................................................
3GPP
Release 10
Annex A (informative):
3GPP TS 32.425 V10.4.0 (2011-03)
Use cases for performance measurements defintion.................................
A.1
Monitor of call(/session) setup performance.........................................................................................
A.2
Monitor of E-RAB release....................................................................................................................
A.3
Monitor of E-RAB level QoS modification..........................................................................................
A.4
Overview handover related Use Cases..................................................................................................
A.5
Monitor of cell level QoS and radio resource utilisation......................................................................
A.6
Monitor of the number of connected users...........................................................................................
A.7
Monitoring of interference situation.....................................................................................................
A.8
Monitor of ARQ and HARQ performance............................................................................................
A.9
Monitoring of RF performance.............................................................................................................
A.10 Monitor of paging performance............................................................................................................

A.11 Use case of eNodeB processor usage....................................................................................................
A.12 Monitor of simultaneous E-RABs........................................................................................................
A.13 Monitoring of Mobility Robustness Optimization (MRO)....................................................................
A.14 Monitor of BLER performance.............................................................................................................
A.15 Monitoring of common LAs of overlapping target RATs coverage.....................................................
A.16 Monitoring of Energy Saving...............................................................................................................
A.17 Monitoring of RNReconfiguration.......................................................................................................
Annex B (informative):
Change history.............................................................................................
3GPP
Release 10
3GPP TS 32.425 V10.4.0 (2011-03)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification
Group Services and System Aspects; Telecommunication management; as identified below:
32.401
Performance Management (PM); Concept and requirements
52.402
Performance Management (PM); Performance measurements GSM
32.404
Performance Management (PM); Performance measurements - Definitions and template
32.405
Performance Management (PM); Performance measurements Universal Terrestrial Radio Access

Network (UTRAN)
32.406
Performance Management (PM); Performance measurements Core Network (CN) Packet Switched
(PS) domain
32.407
Performance Management (PM); Performance measurements Core Network (CN) Circuit

Switched (CS) domain
32.408
Performance Management (PM); Performance measurements Teleservice
32.409
Performance Management (PM); Performance measurements IP Multimedia Subsystem (IMS)
32.425
Performance Management (PM); Evolved Performance measurements Universal Terrestrial

Radio Access Network (E-UTRAN)
32.426
Performance Management (PM); Evolved Packet Core (EPC)
The present document is part of a set of specifications, which describe the requirements and information model
necessary for the standardised Operation, Administration and Maintenance (OA&M) of a multi-vendor E-UTRAN and
EPC system.
During the lifetime of an E-UTRAN, its logical and physical configuration will undergo changes of varying degrees and
frequencies in order to optimise the utilisation of the network resources. These changes will be executed through
network configuration management activities and/or network engineering, see TS 32.600 [3].
3GPP
Release 10
3GPP TS 32.425 V10.4.0 (2011-03)
Many of the activities involved in the daily operation and future network planning of an E-UTRAN require data on
which to base decisions. This data refers to the load carried by the network and the grade of service offered. In order to
produce this data performance measurements are executed in the NEs, which comprise the network. The data can then
be transferred to an external system, e.g. an Operations System (OS) in TMN terminology, for further evaluation. The
purpose of the present document is to describe the mechanisms involved in the collection of the data and the definition
of the data itself.
Annex B of TS 32.404 helps in the definition of new performance measurements that can be submitted to 3GPP for
potential adoption and inclusion in the present document. Annex B of TS 32.404 discusses a top-down performance
measurement definition methodology that focuses on how the end-user of performance measurements can use the
measurements.
3GPP
Release 10
3GPP TS 32.425 V10.4.0 (2011-03)
Scope
The present document describes the measurements for E-UTRAN.

TS 32.401 [5] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of an E-UTRAN.
Only measurement types that are specific to E-UTRAN are defined within the present documents. Vendor specific
measurement types used in E-UTRAN are not covered. Instead, these could be applied according to manufacturer's
documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g.
ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence
of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a
multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
-
Header 1: Network Element (e.g. measurements related to eNodeB);
Header 2: Measurement function (e.g. RRC connection setup related measurements);
Header 3: Measurements.
References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1]
3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[2]
3GPP TS 32.102: "Telecommunication management; Architecture".
[3]
3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept

and high-level requirements".
[4]
Void.
[5]
3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept

and requirements".
[6]
3GPP TS 32.404: "Performance Management (PM); Performance measurements - Definitions and

template".
[7]
3GPP TS 32.762: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network
Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
[8]
3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC) protocol specification".
3GPP
Release 10
10
3GPP TS 32.425 V10.4.0 (2011-03)
[9]
3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1

Application Protocol (S1AP)".
[10]
3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2

application protocol (X2AP)".
[11]
3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2

Measurements".
[12]
3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA); and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[13]
3GPP TS 32.450: "Telecommunication management; Key Performance Indicators (KPI) for EUTRAN: Definitions".
[14]
3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
procedures in idle mode".
[15]
3GPP TS 32.522: "Technical Specification Group Services and SystemAspects;

Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource
Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[16]
3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control
(MAC) protocol specification".
[17]
3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[18]
3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification".
Measurement family and abbreviations
3.1
Measurement family
The measurement names defined in the present document are all beginning with a prefix containing the measurement
family name (e.g. RRC.AttConnEstab.Cause). This family name identifies all measurements which relate to a given
functionality and it may be used for measurement administration (see TS 32.401 [5]).
The list of families currently used in the present document is as follows:
-
3.2
DRB (measurements related to Data Radio Bearer)

RRC (measurements related to Radio Resource Control)
RRU (measurements related to Radio Resource Utilization)
ERAB (measurements related to E-RAB)
HO (measurements related to Handover)
S1SIG (measurements related to S1 Signalling)
SRB (measurements related to Signalling Radio Bearer)
PAG (measurements related to Paging)
EQPT(measurements related to Equipment)
UECNTX(measurements related to UE CONTEXT)
TB(measurements related to Transport Block)
Abbreviations
For the purposes of the present document, the following abbreviations apply:
3G
3GPP
BLER
CRC
EQPT
E-UTRAN
E-RAB
3rd Generation
3G Partnership Project
Block Error Rate
Cyclic Redundancy ChecksumEPS Evolved Packet System
Equipment
Evolved UTRAN
E-UTRAN Radio Access Bearer
3GPP
Release 10
HO
QoS
TB
UTRAN
11
3GPP TS 32.425 V10.4.0 (2011-03)
Handover
Quality of Service
Transport Block
Universal Terrestrial Radio Access Network
You can find below a list of abbreviations used within the measurement types for field E of the measurement template
(see 3GPP TS 32.404 [6]).
Alloc
Att
Conn
Ded
DL
ENB
Err
Estab
Fail
Freq
Inc
Out
Pkt
Prep
Late
Mod
Nbr
Rel
Res
Succ
Tot
UL
Allocation
Attempt(s,ed)
Connection
Dedicated
Downlink
eNodeB
Error
Establish (ed,ment)
Fail(ed, ure)
Frequency
Incoming
Outgoing
Packet(s)
Prepare(/Preparation)
Latency
Modify(/Modification)
Number
Release(s,d)
Resource
Success(es,ful)
Total
Uplink
Measurements related to eNodeB, Donor eNodeB

and Relay Node
4.0
Applicability of measurements to eNB and DeNB
Without particular constraint, the following measurements defined for eNB apply to both eNB and DeNB. In such
measurements definitions the triggering signalling messages transmitted to or received from the UE apply to both cases:
a) direct transferred between UE and eNB and
b) relayed by the RN between UE and DeNB.
If the specific constraint is present, which one of the eNB or DeNB the subject measurement applies to,
is following the constraint.
4.1
RRC connection related measurements
4.1.1
RRC connection establishment
The three measurement types defined in the subclauses 4.1.1.1, 4.1.1.2 and 4.1.1.3 are subject to the "2 out of 3
approach".
4.1.1.1
Attempted RRC connection establishments
a) This measurement provides the number of RRC connection establishment attempts for each establishment cause.
b) CC
3GPP
Release 10
12
3GPP TS 32.425 V10.4.0 (2011-03)
c) Receipt of an RRCConnectionRequest message by the eNodeB/RN from the UE. Each RRCConnectionRequest
message received is added to the relevant per establishment cause measurement. The possible causes are
included in TS 36.331 [8]. The sum of all supported per cause measurements shall equal the total number of
RRCConnectionRequest. In case only a subset of per cause measurements is supported, a sum subcounter will be
provided first.
d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a
possible sum value identified by the .sum suffix.
e) The measurement name has the form RRC.ConnEstabAtt.Cause
where Cause identifies the establishment cause.
f) EUtranCellFDD
EUtranCellTDD
g) Valid for packet switched traffic
h) EPS
4.1.1.2
Successful RRC connection establishments
a) This measurement provides the number of successful RRC establishments for each establishment cause.
b) CC
c) Receipt by the eNodeB/RN of an RRCConnectionSetupComplete message following a RRC connection
establishment request. Each RRCConnectionSetupComplete message received is added to the relevant per
establishment cause measurement. The possible causes are included in TS 36.331 [8]. The sum of all supported
per cause measurements shall equal the total number of successful RRC Connection Establishments. In case only
a subset of per cause measurements is supported, a sum subcounter will be provided first.
e) The measurement name has the form RRC.ConnEstabSucc.Cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.1.1.3
Failed RRC connection establishments
a) This measurement provides the number of RRC establishment failures for each establishment cause.
b) CC
c) Transmission of an RRCConnectionReject message by the eNodeB/RN to the UE or an expected
RRCConnectionSetupComplete message not received by the eNodeB/RN. Each failed RRC connection
establishment is added to the relevant per establishment cause measurement. The possible causes are included in
TS 36.331 [8].
The sum of all supported per cause measurements shall equal the total number of RRC connection establishment
failures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
e) The measurement name has the form RRC.ConnEstabFail.Cause
f) EUtranCellFDD
EUtranCellTDD
3GPP
Release 10
13
3GPP TS 32.425 V10.4.0 (2011-03)

h) EPS
4.1.1.4
Failed RRC connection establishment per failure cause
a) This measurement provides the number of failed RRC establishment per failure cause. This measurement is to
support LBO target setting and evaluation, see [15]
b) CC
c) Transmission of an RRCConnectionReject message by the eNodeB to the UE.
Each transmitted RRCConnectionReject message caused by congestion is added to the measurement cause
Congestion, when eNB receives an RRCConnectionRequest message and the RRC connection is not
established because the eNB is going to Energy Saving mode is added to the measurement cause EnergySaving
and each transmitted RRCConnectionReject message caused by the other reasons is added to measurement cause
Unspecified.
d) Each measurement is an integer value.
e) RRC.ConnEstabFaileNBCause.Congestion
RRC.ConnEstabFaileNBCause.Unspecified
RRC.ConnEstabFaileNBCause.EnergySaving
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) The measurement is use to count Failed RRC connection establishment related to load for LBO target setting
and evaluation, see [15].
4.1.2
RRC connection re-establishment
The three measurement types defined in the subclause 4.1.2.n are subject to the "2 out of 3 approach".
4.1.2.1
Attempted RRC connection re-establishments
a) This measurement provides the number of RRC connection re-establishment attempts for each re-establishment
cause.
b) CC.
c) Receipt of an RRCConnectionReestablishmentRequest message by the eNodeB/RN from the UE. Each
RRCConnectionReestablishmentRequest received is added to the relevant per reestablishment cause
measurement. The possible causes are included in TS 36.331 [8]. The sum of all supported per cause
measurements shall equal the total number of RRC connection re-stablishment attempts. In case only a subset of
per cause measurements is supported, a sum subcounter will be provided first.
e) The measurement name has the form RRC.ConnReEstabAtt.Cause
where Cause identifies the reestablishment cause.
f) EUtranCellFDD
EUtranCellTDD
g) Valid for packet switching.
h) EPS
3GPP
Release 10
4.1.2.2
14
3GPP TS 32.425 V10.4.0 (2011-03)
Successful RRC connection re-establishments
a) This measurement provides the number of successful RRC connection re-establishments for each reestablishment cause.
b) CC.
c) Receipt by the eNodeB/RN of an RRCConnectionReestablishmentComplete message following a RRC
connection reestablishment request. Each RRCConnectionReestablishmentComplete message received is added
to the relevant per reestablishment cause measurement. The possible causes are included in TS 36.331 [8]. The
sum of all supported per cause measurements shall equal the total number of successful RRC connection reestablishments. In case only a subset of per cause measurements is supported, a sum subcounter will be provided
first.
e) The measurement name has the form RRC.ConnReEstabSucc.Cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.1.2.3
Failed RRC connection re-establishments
a) This measurement provides the number of RRC re-establishment failures for each re-establishment cause.
b) CC.
c) Transmission of an RRCConnectionReestablishmentReject message by the eNodeB/RN to the UE or an
expected RRCConnectionReestablishmentComplete message not received by the eNodeB/RN.
Each failed RRC connection re-establishment is added to the relevant per re-establishment.cause measurement.
The possible causes are included in TS 36.331 [8].
The sum of all supported per cause measurements shall equal the total number of RRC connection reestablishment failures. In case only a subset of per cause measurements is supported, a sum subcounter will be
provided first.
e) The measurement name has the form RRC.ConnReEstabFail.Cause
where Cause identifies the re-establishment.cause.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.1.3
4.1.3.1
RRC connection number

Mean number of RRC Connections
a) This measurement provides the mean number of RRC Connections during each granularity period.
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval, the number of RRC connections for each EUTRAN Cell and then taking the arithmetic mean
d) A single integer value.
3GPP
Release 10
15
3GPP TS 32.425 V10.4.0 (2011-03)
e) RRC.ConnMean
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.1.3.2
Maximum number of RRC Connections
a) This measurement provides the maximum number of RRC Connections during each granularity period.
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval, the number of RRC connections for each EUTRAN cell and then taking the maximum.
e) RRC.ConnMax
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.1.4
RRC connection setup time
4.1.4.1
Mean RRC connection setup time
a) This measurement provides the mean time per establishment cause it takes to establish an RRC connection.
b) DER (n=1).
c) This measurement is obtained by accumulating the time intervals for every successful RRC connection
establishment between the receipt of a RRCConnectionRequest and the corresponding
RRCConnectionSetupComplete message by the eNodeB/RN over the granularity period. The end value of this
time will then be divided by the number of successful RRC connections observed in the granularity period to
give the arithmetic mean. The accumulator shall be reinitialised at the beginning of each granularity period. The
measurement is split into subcounters per establishment cause, and the possible causes are included in
TS 36.331 [8].
d) Each measurement is an integer value (in milliseconds).
e) The measurement name has the form RRC.ConnEstabTimeMean.Cause
where Cause identifies the establishment cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.1.4.2
Maximum RRC connection setup time
a) This measurement provides the maximum time per establishment cause it takes to establish an RRC connection.
b) GAUGE.
3GPP
Release 10
16
3GPP TS 32.425 V10.4.0 (2011-03)
c) This measurement is obtained by monitoring the time intervals for each successful RRC connection
establishment between the receipt of a RRCConnectionRequest and the corresponding
RRCConnectionSetupComplete message by the eNodeB/RN over the granularity period. The high tide mark of
this time will be stored in a gauge, the gauge shall be reinitialised at the beginning of each granularity period.
The measurement is split into subcounters per establishment cause, and the possible causes are included in
TS 36.331 [8].
e) The measurement name has the form RRC.ConnEstabTimeMax.Cause
where Cause identifies the establishment cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.1.5
4.1.5.1
UE CONTEXT Release
Number of UE CONTEXT Release Request initiated by eNodeB/RN
a) This measurement provides the number of UE CONTEXT Release initiated by eNB/RN for each release cause.
b) CC.
c) Transmission of an UE CONTEXT RELEASE REQUEST message initiated by eNodeB/RN. Each release
request is to be added to the relevant cause measurement. The possible causes are defined in 36.413 [9]. The sum
of all supported per causes measurements shall equal the total number of UE CONTEXT Release initiated by
eNodeB/RN. In case only a subset of per cause measurements is supported, a sum subcounter will be provided
first.
e) The measurement name has the form UECNTX.RelReq.Cause
where Cause identifies the release cause.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) By differenciate the causes, this measurement is used to count The number of abnormal RRC connection
release related to load, which can be used for LBO target calculation..
4.1.5.2
Successful UE CONTEXT Release
a) This measurement provides the number of successful UE Context Release.

b) CC.
c) Sending of UE CONTEXT RELEASE COMPLETE from eNB/RN to MME/DeNB
e) UEContext.RelSuccNbr.
3GPP
Release 10
17
3GPP TS 32.425 V10.4.0 (2011-03)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement can be used to count the total number of RRC connection release, which can be used for
LBO target calculation.
4.2
E-RAB related measurements
4.2.1
E-RAB setup
4.2.1.1
Number of initial E-RABs attempted to setup
a) This measurement provides the number of initial E-RABs attempted to setup. The measurement is split into
subcounters per E-RAB QoS level (QCI).
b) CC
c) On receipt by the eNodeB/RN of an INITIAL CONTEXT SETUP REQUEST message, each requested E-RAB
in the message is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [9].
The sum of all supported per QCI measurements shall equal the total number of E-RABs attempted to setup. In
case only a subset of per QCI measurements is supported, a sum subcounter will be provided first.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
e) The measurement name has the form ERAB.EstabInitAttNbr.QCI
where QCI identifies the E-RAB level quality of service class.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.1.2
Number of initial E-RABs successfully established
a) This measurement provides the number of initial E-RABs successfully established. The measurement is split into
b) CC
c) On transmission by the eNodeB/RN of an INITIAL CONTEXT SETUP RESPONSE message, each E-RAB
successfully established is added to the relevant measurement per QCI, the possible QCIs are included in
TS 36.413 [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs
successfully setup. In case only a subset of per QCI measurements is supported, a sum subcounter will be
provided first.
e) The measurement name has the form ERAB.EstabInitSuccNbr.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
3GPP
Release 10
4.2.1.3
18
3GPP TS 32.425 V10.4.0 (2011-03)
Number of initial E-RABs failed to setup
a) This measurement provides the number of initial E-RABs failed to setup. The measurement is split into
subcounters per failure cause.
b) CC
c) On transmission by the eNodeB/RN of an INITIAL CONTEXT SETUP RESPONSE, or INITIAL CONTEXT
SETUP FAILURE message, each E-RAB failed to establish is added to the relevant measurement per cause, the
possible causes are included in TS 36.413 [9]. The sum of all supported per cause measurements shall equal the
total number of E-RABs failed to setup. In case only a subset of per cause measurements is supported, a sum
subcounter will be provided first.
e) The measurement name has the form ERAB.EstabInitFailNbr.Cause
where Cause identifies the cause resulting in the initial E-RAB setup failure.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.1.4
Number of additional E-RABs attempted to setup
a) This measurement provides the number of additional E-RABs attempted to setup. The measurement is split into
b) CC
c) On receipt by the eNodeB/RN of an E-RAB SETUP REQUEST message, each requested E-RAB in the message
is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [9]. The sum of all
supported per QCI measurements shall equal the total number of additional E-RABs attempted to setup. In case
only a subset of per QCI measurements is supported, a sum subcounter will be provided first.
e) The measurement name has the form ERAB. EstabAddAttNbr.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Accessibility KPI E-RAB Accessibility defined in [13].
4.2.1.5
Number of additional E-RABs successfully established
a) This measurement provides the number of additional E-RABs successfully established. The measurement is split
into subcounters per E-RAB QoS level (QCI).
b) CC
c) On transmission by the eNodeB/RN of an E-RAB SETUP RESPONSE message, each E-RAB successfully
established is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [9]. The
sum of all supported per QCI measurements shall equal the total number of additional E-RABs successfully
setup. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first.
3GPP
Release 10
19
3GPP TS 32.425 V10.4.0 (2011-03)
e) The measurement name has the form ERAB.EstabAddSuccNbr.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Accessibility KPI E-RAB Accessibility defined [13].
4.2.1.6
Number of additional E-RABs failed to setup
a) This measurement provides the number of additional E-RABs failed to setup. The measurement is split into
subcounters per failure cause.
b) CC
c) On transmission by the eNodeB/RN of an E-RAB SETUP RESPONSE message, each E-RAB failed to establish
is added to the relevant measurement per cause, the possible causes are included in TS 36.413 [9]. The sum of all
supported per cause measurements shall equal the total number of additional E-RABs failed to setup. In case
only a subset of per cause measurements is supported, a sum subcounter will be provided first.
e) The measurement name has the form ERAB. EstabAddFailNbr.Cause
where Cause identifies the cause resulting in the additional E-RAB setup failure.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.1.7
a)
Mean E-RAB Setup time
This measurement provides the mean time per QCI it takes to establish an E-RAB.
b) DER (n=1)
c)
This measurement is obtained by accumulating the time intervals for every successfully established E-RAB
between the receipt of an E-RAB SETUP REQUEST or INITIAL CONTEXT SETUP REQUEST message and
the transmission of the corresponding E-RAB SETUP RESPONSE or INITIAL CONTEXT SETUP
RESPONSE message by the eNodeB over the granularity period. The end value of this time will then be
divided by the number of successfully established E-RABs in the granularity period to give the arithmetic mean.
The accumulator shall be reinitialised at the beginning of each granularity period. The measurement is split into
subcounters per QCI, and the possible QCIs are included in TS 36.413 [9].

e)
The measurement name has the form ERAB.EstabTimeMean.QCI

f)
EUtranCellFDD
EUtranCellTDD

h) EPS
3GPP
Release 10
20
4.2.1.8
a)
3GPP TS 32.425 V10.4.0 (2011-03)
Maximum E-RAB Setup time
This measurement provides the maximum time per QCI it takes to establish an E-RAB.
b) GAUGE
c)
This measurement is obtained by monitoring the time intervals for every successfully established E-RAB
between the receipt of an E-RAB SETUP REQUEST or INITIAL CONTEXT SETUP REQUEST message and
the transmission of the corresponding E-RAB SETUP RESPONSE or INITIAL CONTEXT SETUP
RESPONSE message by the eNodeB over the granularity period. The high tide mark of this time will be stored
in a gauge, the gauge shall be reinitialised at the beginning of each granularity period..
The measurement is split into subcounters per QCI, and the possible QCIs are included in TS 36.413 [9].

e)
The measurement name has the form ERAB.EstabTimeMax.QCI

f)
EUtranCellFDD
EUtranCellTDD

h) EPS
4.2.2
4.2.2.1
E-RAB release
Number of E-RABs requested to release initiated by eNodeB/RN per QCI
a) This measurement provides the number of E-RABs requested to release initiated by eNodeB/RN. The
measurement is split into subcounters per E-RAB QoS level (QCI).
b) CC
c) On transmission by the eNodeB/RN of an E-RAB RELEASE INDICATION, or an UE CONTEXT RELEASE
REQUEST, or a RESET message to MME or DeNB( in case of RN), each corresponding E-RAB requested to
release is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [9]. The sum
of all supported per QCI measurements shall equal the total number of E-RABs requested to release initiated by
eNodeB/RN. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided
first.
e) The measurement name has the form ERAB.RelEnbNbr.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.2.2
Number of E-RABs requested to release initiated by eNodeB/RN per cause
a) This measurement provides the number of E-RABs requested to release initiated by eNodeB/RN. The
measurement is split into subcounters per cause.
b) CC
c) On transmission by the eNodeB/RN of an E-RAB RELEASE INDICATION, or an UE CONTEXT RELEASE
REQUEST, or a RESET message to MME or DeNB( in case of RN), each corresponding E-RAB requested to
release is added to the relevant measurement per cause. Possible causes are included in TS 36.413 [9].
d) Each measurement is an integer value. The number of measurements is equal to the number of supported causes.
3GPP
Release 10
21
3GPP TS 32.425 V10.4.0 (2011-03)
e) The measurement names have the form ERAB.RelEnbNbr.cause

where cause identifies the reason for the E-RABs release request initiated by eNodeB/RN.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.2.3
Number of E-RABs attempted to release
a) This measurement provides the number of E-RABs attempted to release. The measurement is split into
b) CC
c) On receipt by the eNodeB/RN of an E-RAB RELEASE COMMAND or UE CONTEXT RELEASE
COMMAND or UE CONTEXT RELEASE, or RESET message from MME/DeNB, or transmission by the
eNodeB/RN of a RESET message to MME/DeNB, each corresponding E-RAB to release is added to the relevant
measurement per QCI, the possible QCIs are included in TS 36.413 [9]. The sum of all supported per QCI
measurements shall equal the total number of E-RABs attempted to release. In case only a subset of per QCI
measurements is supported, a sum subcounter will be provided first.
e) The measurement name has the form ERAB.RelAttNbr.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.2.4
Number of E-RAB successfully released
a) This measurement provides the number of E-RABs successfully released. The measurement is split into
b) CC
c) On transmission by the eNodeB/RN of an E-RAB RELEASE RESPONSE or UE CONTEXT RELEASE
COMPLETE, or the E-RAB released successfully by source eNB/RN after receiving UE CONTEXT RELEASE,
or a RESET ACKNOWLEDGE message to MME/DeNB, or receipt of a RESET ACKNOWLEDGE message
from MME/DeNB, each corresponding E-RAB successfully released is added to the relevant measurenment per
QCI, the possible QCIs are included in TS 36.413 [9]. The sum of all supported per QCI measurements shall
equal the total number of E-RABs fully released. In case only a subset of per QCI measurements is supported, a
sum subcounter will be provided first.
e) The measurement name has the form ERAB.RelSuccNbr.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
3GPP
Release 10
4.2.2.5
22
3GPP TS 32.425 V10.4.0 (2011-03)
Number of E-RAB failed to release
a) This measurement provides the number of E-RAB failed to release. The measurement is split into subcounters
per failure cause.
b) CC
c) On transmission by the eNodeB/RN of an E-RAB RELEASE RESPONSE message, each E-RAB failed to
release is added to the relevant measurement per cause, the possible causes are included in TS 36.413 [9]. The
sum of all supported per cause measurements shall equal the total number of E-RABs failed to release. In case
e) The measurement name has the form ERAB.RelFailNbr.Cause
where Cause identifies the cause resulting in the E-RAB release failure.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.2.6
Number of released active E-RABs
a) This measurement provides the number of released E-RAB that were active at the time of release (i.e.when there
was user data in the queue in any of the directions). The measurement is split into subcounters per E-RAB QoS
level (QCI).
b) CC
c) On transmission by the eNodeB/RN of an E-RAB RELEASE RESPONSE or UE CONTEXT RELEASE
COMPLETE message with the exception of those succeeding the message UE CONTEXT RELEASE
COMMAND with Cause indicating that the release was performed due to a successful Mobility activity, or a
RESET ACKNOWLEDGE to MME/DeNB, or receipt of a RESET ACKNOWLEDGE message from
MME/DeNB, if any of the UL or DL are considered active (according to the definition used for "Number of
active UEs in TS 36.314 when there is still data in the DL or UL buffer, each corresponding E-RAB to release is
added to the relevant measurement per QCI. The possible QCIs are described in TS 36.413 [9]. The sum of all
supported per QCI measurements shall equal the total number of E-RAB attempted to release with data in the DL
or UL buffer. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided
first.
e) The measurement name has the form ERAB.RelActNbr.QCI
where QCI identifies the SAE Bearer level quality of service class.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Retainability KPI E-UTRAN EPS Bearer Retainability defined in [13]
4.2.3
4.2.3.1
E-RAB modification
Number of E-RABs attempted to modify the QoS parameter
a) This measurement provides the number of E-RABs attempted to modify the QoS parameter. The measurement is
split into subcounters per E-RAB QoS level (QCI).
3GPP
Release 10
23
3GPP TS 32.425 V10.4.0 (2011-03)
b) CC
c) On receipt by the eNodeB/RN of an E-RAB MODIFY REQUEST message, each E-RAB attempted to modify
the QoS parameter is added to the relevant measurement per QCI, the possible QCIs are included in
attempted to modify the QoS parameter. In case only a subset of per QCI measurements is supported, a sum
e) The measurement name has the form ERAB.ModQoSAttNbr.QCI
where QCI identifies the target E-RAB level quality of service class.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.3.2
Number of E-RABs successfully modified the QoS parameter
a) This measurement provides the number of E-RABs successfully modified the QoS parameter. The measurement
is split into subcounters per E-RAB QoS level (QCI).
b) CC
c) On transmission by the eNodeB/RN of an E-RAB MODIFY RESPONSE message, each E-RAB successfully
modified the QoS parameter is added to the relevant measurement per QCI, the possible QCIs are included in
successfully modified the QoS parameter. In case only a subset of per QCI measurements is supported, a sum
e) The measurement name has the form ERAB.ModQoSSuccNbr.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.3.3
Number of E-RABs failed to modify the QoS parameter
a) This measurement provides the number of E-RABs failed to be modified the QoS parameter. The measurement
is split into subcounters per failure cause.
b) CC
c) On transmission by the eNodeB/RN of an E-RAB MODIFY RESPONSE message, each E-RAB failed to modify
the QoS parameter is added to the relevant measurement per cause, the possible causes are included in
TS 36.413 [9]. The sum of all supported per cause measurements shall equal the total number of E-RABs failed
to modify the QoS parameter. In case only a subset of per cause measurements is supported, a sum subcounter
will be provided first.
3GPP
Release 10
24
3GPP TS 32.425 V10.4.0 (2011-03)
e) The measurement name has the form ERAB.ModQoSFailNbr.Cause

where Cause identifies the cause resulting in the E-RAB Modify failure.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.4
4.2.4.1
E-RAB activity
In-session activity time for UE
a) This measurement provides the aggregated active session time for UEs in a cell.
b) CC
c) Number of session seconds aggregated for UEs in a cell. A UE is said to be in session if any E-RAB data on a
Data Radio Bearer (UL or DL) has been transferred during the last 100 ms.
e) ERAB.SessionTimeUE
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Retainability KPI E-RAB Retainability defined in [13].
4.2.4.2
In-session activity time for E-RABs
a) This measurement provides the aggregated active session time for E-RABs in a cell. The measurement is split
into subcounters per E-RAB QoS level (QCI).
b) CC
c) Number of session seconds aggregated for E-RABs with a certain QCI. The E-RABs for a UE is said to be in
session if any E-RAB data on any Data Radio Bearer (UL or DL) has been transferred during the last 100 ms
for that QCI. The possible QCIs are described in TS 36.413 [9]. The sum of all supported per QCI measurements
shall equal the total session seconds. In case only a subset of per QCI measurements is supported, a sum
e) The measurement name has the form ERAB.SessionTimeQCI.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Retainability KPI E-RAB Retainability defined in [13].
3GPP
Release 10
4.2.5
4.2.5.1
25
3GPP TS 32.425 V10.4.0 (2011-03)
E-RAB number
Average Number of simultaneous E-RABs.
a) This measurement provides the average number of simultaneous E-RABs. The measurement is split into
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval, the number of simultaneous E-RABs and
then taking the arithmetic mean. The measurement is split into subcounters per QCI, and the possible QCIs are
included in TS 36.413 [9]. In case only a subset of per QCI measurements is supported, a sum subcounter will be
provided first.
e) The measurement name has the form ERAB.UsageNbrMean.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.2.5.2
Maximum Number of simultaneous E-RABs.
a) This measurement provides the maximum number of simultaneous E-RABs. The measurement is split into
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval, the number of simultaneous E-RABs and
then taking the maximum. The measurement is split into subcounters per QCI, and the possible QCIs are
included in TS 36.413 [9]. In case only a subset of per QCI measurements is supported, a sum subcounter will be
provided first.
e) The measurement name has the form ERAB.UsageNbrMax.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3
Handover related measurements
4.3.1
Intra-RAT Handovers
4.3.1.1
4.3.1.1.1
Intra-eNB/RN Handover related measurements

Attempted outgoing intra-eNB/RN handovers per handover cause
a) This measurement provides the number of attempted outgoing intra-eNB/RN handovers per handover cause.
b) CC.
3GPP
Release 10
26
3GPP TS 32.425 V10.4.0 (2011-03)
c) Transmission of the RRCConnectionReconfiguration message by the eNB/RN to the UE triggering the intraeNB/RN handover (see TS 36.331 [8]). Each RRCConnectionReconfiguration message transimtted is added to
the relevant per handover cause measurement, the possible causes are included in TS 36.413 [9].
The sum of all supported per cause measurements shall equal the total number of outgoing intra-eNB/RN
handover events. In case only a subset of per cause measurements is supported, a sum subcounter will be
provided first.
d) Each measurement is an integer value. The number of measurements is equal to the number of causes supported
plus a possible sum value identified by the .sum suffix.
e) HO.IntraEnbOutAtt.Cause
where Cause identifies the cause for handover.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.1.2
Successful outgoing intra-eNB/RN handovers per handover cause
a) This measurement provides the number of successful outgoing intra-eNB/RN handovers per handover cause.
b) CC.
c) Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source)
eNB/RN, indicating a successful outgoing intra-eNB/RN handover (see TS 36.331 [8]). Each
RRCConnectionReconfigurationComplete message transimtted is added to the relevant per handover cause
measurement, the possible causes are included in TS 36.413 [9].
The sum of all supported per cause measurements shall equal the total number of outgoing intra-eNB/RN
handover events. In case only a subset of per cause measurements is supported, a sum subcounter will be
provided first.
plus a possible sum value identified by the .sum suffix
e) HO.IntraEnbOutSucc.Cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.1.3
Attempted outgoing intra-DeNB handover preparations from DeNB cell to RN per

handover cause
a) This measurement provides the number of attempted outgoing intra-DeNB handover preparations from DeNB
cell to RN per handover cause; this measurement is only applicable to DeNB.
b) CC.
c) Transmission of the X2AP message HANDOVER REQUEST from the DeNB to RN (see TS 36.423[10]),
indicating the attempt of an outgoing intra-DeNB handover preparation from DeNB cell to RN, the forwarded
X2AP message HANDOVER REQUEST for the handover from another RN, eNB or DeNB to the RN is
exclusive, the measurement is only incemented by one for one handover in case the X2AP message
HANDOVER REQUEST are sent to multiple RNs. Each attempted outgoing intra-DeNB handover preparation
from DeNB cell to RN is added to the relevant per handover cause measurement, the possible causes are
included in TS 36.413 [9]. The sum of all supported per cause measurements shall equal the total number of
attempted outgoing intra-DeNB handover preparations from DeNB cell to RN. In case only a subset of per cause
3GPP
Release 10
27
3GPP TS 32.425 V10.4.0 (2011-03)

e) HO.IntraDenbOutPrepToRnAtt.Cause
where Cause identifies the cause for handover
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.1.4
Attempted outgoing intra-DeNB handover executions from DeNB cell to RN per

handover cause
a) This measurement provides the number of attempted outgoing intra-eNB handovers from DeNB cell to RN per
handover cause; this measurement is only applicable to DeNB.
b) CC.
c) Transmission of the RRC ConnectionReconfiguration message to UE triggering the handover from the DeNB to
the RN, indicatingthe attempt of an outgoing intra-eNB handover from DeNB cell to RN (see TS 36.331 [8]).
Each RRCConnectionReconfiguration message transimtted is added to the relevant per handover cause
measurement, the possible causes are included in TS 36.413 [9]. The sum of all supported per cause
measurements shall equal the total number of attempted outgoing intra-eNB handovers from DeNB cell to RN.
In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
e) HO.IntraDenbOutToRnAtt.Cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.1.5
Successful outgoing intra-DeNB handover executions from DeNB cell to RN per

handover cause
a) This measurement provides the number of successful outgoing intra-DeNB handovers from DeNB cell to RN per
handover cause; this measurement is only applicable to DeNB.
b) CC.
c) Receipt by the source DeNB of X2AP message UE CONTEXT RELEASE from the RN following a successful
handover (see TS 36.423[10]), the forwarded X2AP message UE CONTEXT RELEASE for the handover from
another RN, eNB or DeNB to the RN is exclusive. Each outgoing intra-DeNB handover from DeNB cell to RN
is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413 [9].
The sum of all supported per cause measurements shall equal the total number of succesful outgoing intra-eNB
handovers from DeNB cell to RN. In case only a subset of per cause measurements is supported, a sum
e) HO.IntraDenbOutToRnSucc.Cause
f) EUtranCellFDD
EUtranCellTDD
3GPP
Release 10
28
3GPP TS 32.425 V10.4.0 (2011-03)
h) EPS
4.3.1.2
4.3.1.2.1
Inter-eNB Handover related measurements

Attempted outgoing inter-eNB handover preparations
a) This measurement provides the number of attempted outgoing inter-eNB handover preparations, the forwarded
handovers for RN in DeNB are exclusive.
b) CC.
c) Transmission of the X2AP message HANDOVER REQUEST from the source eNB to the target eNB (see TS
36.423[10]), indicating the attempt of an outgoing inter-eNB handover preparation or on transmission of S1AP
message HANDOVER REQUIRED to the MME (see TS 36.413 [9]), the forwarded X2AP message
HANDOVER REQUEST and S1AP message HANDOVER REQUIRED for RN in DeNB are exclusive.
e) HO.InterEnbOutPrepAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.2.2
Attempted outgoing inter-eNB handover executions per handover cause
a) This measurement provides the number of attempted outgoing inter-eNB handovers per handover cause.
b) CC.
c) Transmission of the RRC ConnectionReconfiguration message to UE triggering the handover from the source
eNB to the target eNB, indicatingthe attempt of an outgoing inter-eNB handover (see TS 36.331 [8]).
The sum of all supported per cause measurements shall equal the total number of outgoing inter-eNB handover
event Each RRCConnectionReconfiguration message transimtted is added to the relevant per handover cause
measurement, the possible causes are included in TS 36.413 [9]. In case only a subset of per cause measurements
is supported, a sum subcounter will be provided first.
e) HO.InterEnbOutAtt.Cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.2.3
Successful outgoing inter-eNB handover executions per handover cause
a) This measurement provides the number of successful outgoing inter-eNB handovers per handover cause, the
forwarded handovers for RN in DeNB are exclusive.
b) CC.
c) Receipt at the source eNB of UE CONTEXT RELEASE [10] over the X2 from the target eNB following a
successful handover, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND [9]
at the source eNB following a successful handover, the forwarded X2AP UE CONTEXT RELEASE message
and S1AP UE CONTEXT RELEASE COMMAND message for RN in DeNB are exclusive. Each X2AP UE
CONTEXT RELEASE message or S1AP UE CONTEXT RELEASE COMMAND message received and
counted is added to the relevant per handover cause measurement, the possible causes are included in
3GPP
Release 10
29
3GPP TS 32.425 V10.4.0 (2011-03)
TS 36.413 [9].
The sum of all supported per cause measurements shall equal the total number of outgoing inter-eNB handover
events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
e) HO.InterEnbOutSucc.Cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.3
4.3.1.3.1
Handover measurements on neighbour cell basis

Attempted outgoing handovers per handover cause
a) This measurement provides the number of attempted outgoing handovers per handover cause and LTE target cell
specific.
b) CC.
c) Transmission of the RRCConnection reconfiguration message to UE triggering the intra-RAT handover (see TS
36.331 [8]). Each RRCConnectionReconfiguration message transimtted is added to the relevant per handover
cause measurement, the possible causes are included in TS 36.413 [9].
The sum of all supported per cause measurements shall equal the total number of outgoing handover events. In
case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
e) HO.OutAttTarget.Cause
f) EUtranRelation
h) EPS
4.3.1.3.2
Successful outgoing handovers per handover cause
a) This measurement provides the number of successful outgoing handovers per handover cause and LTE target cell
specific.
b) CC.
eNB, indicating a successful outgoing intra-eNB handover (see TS 36.331 [8]), or receipt at the source eNB of
UE CONTEXT RELEASE [10] over the X2 from the target eNB following a successful inter-eNB handover, or
if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source eNB
following a successful inter-eNB handover. Each RRCConnectionReconfigurationComplete, X2AP UE
CONTEXT RELEASE message or S1AP UE CONTEXT RELEASE COMMAND message received is added to
the relevant per handover cause measurement, the possible causes are included in TS 36.413 [9]. The sum of all
supported per cause measurements shall equal the total number of outgoing intra-RAT handover events. In case
e) HO.OutSuccTarget.Cause
3GPP
Release 10
30
3GPP TS 32.425 V10.4.0 (2011-03)
f) EUtranRelation
h) EPS
4.3.1.3.3
Number of handover failures related with MRO
a) This measurement provides the number of outgoing handover related events that fail related with MRO.
Handover related events include normal successful handovers and all failure events by which a UE in RRC
connected state changes its serving cell without following a normal handover. Different MRO failure cases are
found in [12]. The measurement includes separate counters for the number of handover failures classified as too
early, too late and to wrong cell.
b) CC
c) The measurement is obtained by accumulating the number of failure events related to handover which are
identified by the eNB according to the definitions in TS 36.300 [12].
e) The measurements are named
HO.IntraFreqOutFail.TooEarly
HO.IntraFreqOutFail.TooLate
HO.IntraFreqOutFail.ToWrongCell
f) EUtranRelation
h) EPS
4.3.1.4
4.3.1.4.1
Intra- / Inter-frequency Handover related measurements

Attempted outgoing intra-frequency handovers
a) This measurement provides the number of attempted outgoing intra-frequency handovers.

b) CC.
c) Transmission of the RRCConnectionReconfiguration message by the eNB/RN to UE triggering the handover,
indicating the attempt of an outgoing intra-frequency handover (see TS 36.331 [8]).
e) HO.IntraFreqOutAtt.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.4.2
Successful outgoing intra-frequency handovers
a) This measurement provides the number of successful outgoing intra-frequency handovers.

b) CC.
eNB/RN, indicating a successful outgoing intra-eNB/RN intra-frequency handover (see TS 36.331 [8]), orreceipt
at the source eNB/RN of UE CONTEXT RELEASE [10] over the X2 from the target eNB or DeNB following a
3GPP
Release 10
31
3GPP TS 32.425 V10.4.0 (2011-03)
successful inter-eNB intra-frequency handover, or if handover is performed via S1, receipt of UE CONTEXT
RELEASE COMMAND[9] at the source eNB following a successful inter-eNB intra-frequency handover.
e) HO.IntraFreqOutSucc
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.4.3
Attempted outgoing inter-frequency handovers gap-assisted measurement
a) This measurement provides the number of attempted outgoing inter-frequency handovers, when measurement
gaps are used [12].
b) CC.
indicating the attempt of an outgoing inter-frequency handover when measurement gaps are used (see TS
36.331 [8]).
e) HO.InterFreqMeasGapOutAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.4.4
Successful outgoing inter-frequency handovers gap-assisted measurement
a) This measurement provides the number of successful outgoing inter-frequency handovers, when measurement
gaps are used [12].
b) CC.
eNB/RN, indicating a successful outgoing intra-eNB/RN inter-frequency handover when measurement gaps are
used (see TS 36.331 [8]), or receipt at the source eNB/RN of UE CONTEXT RELEASE [10] over the X2 from
the target eNB or DeNB following a successful inter-frequency handover when measurement gaps are used, or if
handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source eNB
following a successful inter-frequency handover when measurement gaps are used.
e) HO.InterFreqMeasGapOutSucc
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.4.5
Attempted outgoing inter-frequency handovers non gap-assisted measurement
a) This measurement provides the number of attempted outgoing inter-frequency handovers, when measurement
gaps are not used [12].
b) CC.
3GPP
Release 10
32
3GPP TS 32.425 V10.4.0 (2011-03)

indicating the attempt of an outgoing inter-frequency handover when measurement gaps are not used (see TS
36.331 [8]).
e) HO.InterFreqNoMeasGapOutAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.4.6
Successful outgoing inter-frequency handovers non gap-assisted measurement
a) This measurement provides the number of successful outgoing inter-frequency handovers, when measurement
gaps are not used [12].
b) CC.
eNB/RN, indicating a successful outgoing intra-eNB/RN inter-frequency handover when measurement gaps are
not used (see TS 36.331 [8]), or receipt at the source eNB/RN of UE CONTEXT RELEASE [10] over the X2
from the target eNB or from DeNB following a successful inter-frequency handover when measurement gaps are
not used, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source
eNB following a successful inter-frequency handover when measurement gaps are not used.
e) HO.InterFreqNoMeasGapOutSucc
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.5
4.3.1.5.1
Handover related measurements for DRX / non-DRX

Attempted outgoing handovers with DRX
a) This measurement provides the number of attempted outgoing handovers, when DRX is used (for DRX see
[12]).
b) CC.
c) Transmission of the RRCConnectionReconfiguration message to UE triggering the handover, indicating the
attempt of an outgoing handover when DRX is used (see TS 36.331 [8]).
e) HO.DrxOutAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.5.2
Successful outgoing handovers with DRX
a) This measurement provides the number of successful outgoing handovers, when DRX is used (for DRX see
[12]).
3GPP
Release 10
33
3GPP TS 32.425 V10.4.0 (2011-03)
b) CC.
eNB, indicating a successful outgoing intra-eNB handover when DRX is used (see TS 36.331 [8]), or receipt at
the source eNB of UE CONTEXT RELEASE [10] over the X2 from the target eNB following a successful
handover when DRX is used, or if handover is performed via S1, receipt of UE CONTEXT RELEASE
COMMAND[9] at the source eNB following a successful handover when DRX is used.
e) HO.DrxOutSucc
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.5.3
Attempted outgoing handovers non-DRX
a) This measurement provides the number of attempted outgoing handovers, when DRX is not used (for DRX see
[12]).
b) CC.
c) Transmission of the RRCConnectionReconfiguration message to UE triggering the handover, indicating the
attempt of an outgoing handover when DRX is not used (see TS 36.331 [8]).
e) HO.NoDrxOutAtt.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.5.4
Successful outgoing handovers non-DRX
a) This measurement provides the number of successful outgoing handovers, when DRX is not used (for DRX see
[12]).
b) CC.
eNB, indicating a successful outgoing intra-eNB handover when DRX is not used (see TS 36.331 [8]) when
DRX is not used, or receipt at the source eNB of UE CONTEXT RELEASE [10] over the X2 from the target
eNB following a successful handover when DRX is not used, or if handover is performed via S1, receipt of UE
CONTEXT RELEASE COMMAND[9] at the source eNB following a successful handoverwhen DRX is not
used.
e) HO.NoDrxOutSucc
f) EUtranCellFDD
EUtranCellTDD
h) EPS
3GPP
Release 10
4.3.1.6
4.3.1.6.1
34
3GPP TS 32.425 V10.4.0 (2011-03)
Handover to cells outside the RN related measurements

Attempted preparations of outgoing handovers to the cells outside the RN
a) This measurement provides the number of attempted preparations of outgoing handovers to the cells outside the
RN.
b) CC.
c) Transmission of the X2AP message HANDOVER REQUEST by the RN to the DeNB (see TS 36.423[10]),
indicating the attempt of an outgoing handover preparation to the cells outside the RN.
e) HO.OutRNOutPrepAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.6.2
Attempted executions of outgoing handover to the cells outside the RN per

handover cause
a) This measurement provides the number of attempted executions of outgoing handovers to the cells outside the
RN per handover cause.
b) CC.
c) Transmission of the RRC ConnectionReconfiguration message by the RN to UE triggering the handover from the
RN to the cell outside the RN, indicatingthe attempt of an outgoing handover to the cell outside the RN(see TS
36.331 [8]).
The sum of all supported per cause measurements shall equal the total number of attempted executions of
outgoing handovers to the cell outside the RN. Each RRCConnectionReconfiguration message transimtted is
added to the relevant per handover cause measurement, the possible causes are included in TS 36.413 [9]. In case
e) HO.OutRNOutAtt.Cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.6.3
Successful executions of outgoing handover to the cells outside the RN per

handover cause
a) This measurement provides the number of successful executions of outgoing handovers to the cells outside the
RN per handover cause.
b) CC.
c) Receipt at the RN of UE CONTEXT RELEASE [10] over the X2 from the DeNB following a successful
handover. Each X2AP UE CONTEXT RELEASE message received is added to the relevant per handover cause
The sum of all supported per cause measurements shall equal the total number of executions of outgoing
handovers to the cells outside the RN. In case only a subset of per cause measurements is supported, a sum
3GPP
Release 10
35
3GPP TS 32.425 V10.4.0 (2011-03)
e) HO.InterRNOutSucc.Cause
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.3.1.7
Handover triggering measurements
4.3.1.7.1
Average quality of the serving cell when HO is triggered
a) This measurement provides the average quality of the serving cell reported in the UE measurement reports that
triggered HO. The average is computed over all measurement reports that triggered HO received during the
measurement granularity period. Separate measurement is produced for each measurement quantity {RSRP,
RSRQ}.
b) DER (n=1)
c) For each UtranRelation, this measurement is obtained by accumulating the value (linear value converted from
dbm unit) of the quality of the serving (source) cell (RSRP and RSRQ) in the UE measurement report causing
HO on the UtranRelation, and dividing the accumulated value by the number of HO occurrence on the
UtranRelation at the end of granularity period, and converting the value back to dbm unit from linear value.
Separate measurement is provided for RSRP and for RSRQ.
d) Each measurement is asingle integer value in dBm (RSRP) or dB (RSRQ)
e) HO.SrcCellQual.RSRP
HO.SrcCellQual.RSRQ
f) EUtranRelation
h) EPS
4.3.1.7.2
Average quality of the neighboring cell when HO is triggered
a) This measurement provides the average quality of the neigbor cell that triggered HO (target HO cell) reported in
the UE measurement reports. The average is computed over all measurement reports that triggered HO during
the measurement granularity period. Separate measurement is produced for each measurement quantity {RSRP,
RSRQ}.
b) DER (n=1)
c) For each UtranRelation, this measurement is obtained by accumulating the value (linear value converted from
dbm unit) of the quality of neighbor (target) cell (RSRP, RSRQ) in the UE measurement report causing HO to
the subject neighbor (target) cell on the UtranRelation, and dividing the accumulated value by the number of HO
occurrence on the UtranRelation at the end of granularity period, and converting the value back to dbm unit from
linear value. Separate measurement is provided for RSRP and for RSRQ.
d) Each measurement is a single integer value in dBm (RSRP) or dB (RSRQ)
e) HO.TrgtCellQual.RSRP
HO.TrgtCellQual.RSRQ
f) EUtranRelation
h) EPS
3GPP
Release 10
4.3.2
4.3.2.1
4.3.2.1.1
36
3GPP TS 32.425 V10.4.0 (2011-03)
Inter-RAT Handovers
Measurements related to inter-RAT Handovers target cell of 3GPP and
non-3GPP network technology
Attempted outgoing inter-RAT handovers per handover cause
a) This measurement provides the number of attempted outgoing inter-RAT handovers per cause and target cell
specific.
b) CC.
c) Transmission of the MobilityFromEUTRACommand message or the HandoverFromEUTRAPreparationRequest
message from the serving eNB/RN to the UE indicating the attempt of an outgoing handover from EUTRAN to
UTRAN or to GERAN or to CDMA2000 (see TS 36.331 [8]). Each MobilityFromEUTRACommand message or
HandoverFromEUTRAPreparationRequest message transmitted is added to the relevant per handover cause
The sum of all supported per cause measurements shall equal the total number of outgoing inter-RAT handover
All IRAT handovers to the neighbouring cells in non-eUTRAN networks are measured.
e) HO.IartOutAtt.Cause
f) EUtranCellFDD
EUtranCellTDD
GSMRelation
UTRANRelation
CDMA2000Relation
h) EPS
4.3.2.1.2
Successful outgoing inter-RAT handovers per handover cause
a) This measurement provides the number of successful outgoing inter-RAT handovers per cause target cell
specific.
b) CC.
c) Receipt of a S1AP message UE CONTEXT RELEASE COMMAND sent from the MME/DeNB to the source
eNB, indicating a successful IRAT handover (see TS 36.413 [9]). Each UE CONTEXT RELEASE COMMAND
message received is added to the relevant per handover cause measurement, the possible causes are included in
TS 36.413 [9].
The sum of all supported per cause measurements shall equal the total number of outgoing inter-RAT handover
All IRAT handovers to the neighbouring cells in non-eUTRAN are measured.
e) HO.IartOutSucc.Cause
where Cause indicating the cause for handover.
f) EUtranCellFDD
EUtranCellTDD
GSMRelation
UTRANRelation
CDMA2000Relation
3GPP
Release 10
37
3GPP TS 32.425 V10.4.0 (2011-03)
h) EPS
4.4
Cell level radio bearer QoS related measurements
4.4.1
Cell PDCP SDU bit-rate
4.4.1.1
Average DL cell PDCP SDU bit-rate
a) This measurement provides the average cell bit-rate of PDCP SDUs on the downlink. This represents the ingress
rate of user plane traffic to the eNodeB/RN (via X2 or S1). The measurement is split into subcounters per ERAB QoS level (QCI).
b) CC
c) This measurement is obtained by accumulating the number of bits entering the eNodeB/RN, and then dividing
the sum by the measurement period . The measurement is performed at the PDCP SDU level. PDCP SDUs that
are forwarded over the X2/S1 to another eNodeB during handover shall be deducted from the bit count if this
results in a negative bit count the bit count shall be set to zero. Separate counters are maintained for each QCI.
The sum of all supported per QCI measurements shall equal the total DL cell PDCP SDU bit-rate. In case only a
subset of per QCI measurements is supported, a sum subcounter will be provided first.
d) Each measurement is an integer value representing the bit-rate measured in kb/s. The number of measurements is
equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
e) The measurement name has the form DRB.PdcpSduBitrateDl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.1.2
Average UL cell PDCP SDU bit-rate
a) This measurement provides the average cell bit-rate of PDCP SDUs on the uplink. This represents successful
transmissions of user plane traffic; control signalling and retransmissions are excluded from this measure. The
measurement is split into subcounters per E-RAB QoS level (QCI).
b) CC
c) This measurement is obtained by accumulating the number of bits leaving the eNodeB/RN on the X2 or S1
interface, and then dividing the sum by the measurement period. The measurement is performed at the PDCP
SDU level. PDCP SDUs that were not received over the air interface in the cell (but were forwarded from
another eNodeB during handover) are excluded from the count. Separate counters are maintained for each QCI.
The sum of all supported per QCI measurements shall equal the total UL cell PDCP SDU bit-rate. In case only a
subset of per QCI measurements is supported, a sum subcounter will be provided first.
d) Each measurement is an integer value representing the bit-rate measured in kb/s. The number of measurements is
equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
e) The measurement name has the form DRB. PdcpSduBitrateUl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
3GPP
Release 10
4.4.1.3
38
3GPP TS 32.425 V10.4.0 (2011-03)
Maximum DL cell PDCP SDU bit-rate
a) This measurement provides the maximum cell bit-rate of PDCP SDUs on the downlink. This represents the
maximum ingress rate of user plane traffic to the eNodeB/RN (via X2 or S1). This is a sum counter measured
across all QCIs.
b) SI
c) This measurement is obtained by sampling at pre-defined intervals the DL cell PDCP SDU bit-rate summed
across all QCIs (see clause 4.4.1.1), and then taking the arithmetic maximum of these samples.
d) A single integer value representing the maximum bit-rate measured in kb/s.
e) DRB.PdcpSduBitrateDlMax
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.1.4
Maximum UL cell PDCP SDU bit-rate
a) This measurement provides the maximum cell bit-rate of PDCP SDUs measured on the uplink. This represents
successful transmissions of user plane traffic; control signalling and retransmissions are excluded from this
measure. This is a sum counter measured across all QCIs.
b) SI
c) The measurement is obtained by sampling at pre-defined intervals the UL cell PDCP SDU bit-rate summed
across all QCIs (see clause 4.4.1.2), and then taking the arithmetic maximum of these samples.
d) A single integer value representing the maximum bit-rate measured in kb/s.
e) DRB.PdcpSduBitrateUlMax
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.1.5
Average DL cell control plane PDCP SDU bit-rate
i) This measurement provides the average cell bit-rate of control plane PDCP SDUs on the downlink.
j) CC.
k) This measurement is obtained by accumulating the number of received control plane PDCP SDU bits by the
eNodeB/RN, including the control plane PDCP SDU bits received from S1 and RRC SAP, and then dividing the
sum by the measurement period.
l) An single integer value in kb/s.
m) SRB.PdcpSduBitrateDl
n) EUtranCellFDD
EUtranCellTDD
o) Valid for packet switching.
p) EPS
3GPP
Release 10
4.4.1.6
39
3GPP TS 32.425 V10.4.0 (2011-03)
Average UL cell control plane PDCP SDU bit-rate
a) This measurement provides the average cell bit-rate of control plane PDCP SDUs on the uplink.
This represents successful transmissions of control plane traffic;
b) CC.
c) This measurement is obtained by accumulating the number of transmitted uplink control plane PDCP SDU bits
by the eNodeB/RN, and then dividing the sum by the measurement period.
d) An single integer value in kb/s.
e) SRB.PdcpSduBitrateUl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.2
4.4.2.1
Active UEs
Average number of active UEs on the DL
a) This measurement provides the average number of UEs that have DTCH data queued on the downlink. The
measurement is split into subcounters per E-RAB QoS level (QCI). In case of DeNB the measurement shows the
number of active UEs connected directly to the DeNB.
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11]. Separate counters are
maintained for each QCI.
e) The measurement name has the form
DRB.UEActiveDl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.2.2
Average number of active UEs on the UL
a) This measurement provides the average number of UEs that have DTCH data queued on the uplink. The
measurement is split into subcounters per E-RAB QoS level (QCI). In case of DeNB the measurement shows the
number of active UEs connected directly to the DeNB.
b) SI
maintained for each QCI.
DRB.UEActiveUl.QCI
3GPP
Release 10
40
3GPP TS 32.425 V10.4.0 (2011-03)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.3
4.4.3.1
Packet Delay and Drop Rate

Average DL PDCP SDU delay
a) This measurement provides the average (arithmetic mean) PDCP SDU delay on the downlink. The measurement
is split into subcounters per E-RAB QoS level (QCI). In case of DeNB the measurement provides separate
counter for the Un link and Uu link.
b) DER (n=1)
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11].
d) Each measurement is an integer value representing the mean delay in ms. The number of measurements is equal
to the number of QCIs plus a possible sum value identified by the .sum suffix.
DRB.PdcpSduDelayDl.QCI
DRB.PdcpSduDelayDlUn.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.3.2
DL PDCP SDU drop rate
a) This measurement provides the fraction of IP packets (PDCP SDUs) which are dropped on the downlink. Only
user-plane traffic (DTCH) is considered. A dropped packet is one whose context is removed from the
eNodeB/RN without any part of it having been transmitted on the air interface. Packets discarded during
handover are excluded from the count. The measurement is split into subcounters per E-RAB QoS level (QCI).
b) SI
maintained for each QCI. In case only a subset of per QCI measurements is supported, a drop rate subcounter
calculated across all QCIs will be provided first.
d) Each measurement is an integer value representing the drop rate multiplied by 1E6. The number of
measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
e) The measurement name has the form DRB.PdcpSduDropRateDl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
3GPP
Release 10
4.4.4
4.4.4.1
41
3GPP TS 32.425 V10.4.0 (2011-03)
Packet loss rate

DL PDCP SDU air interface loss rate
a) This measurement provides the fraction of IP packets (PDCP SDUs) which are lost (not successfully transmitted)
on the downlink air interface. Only user-plane traffic (DTCH) is considered. A lost packet is one whose context
is removed from the eNodeB/RN after an attempt has been made to transmit part or all of the packet on the air
interface but the whole packet has not been successfully transmitted. The measurement is split into subcounters
per E-RAB QoS level (QCI). In case of DeNB the measurement provides the packet loss rate for Uu link only.
b) SI
maintained for each QCI. In case only a subset of per QCI measurements is supported, a loss rate subcounter
d) Each measurement is an integer value representing the air interface loss rate multiplied by 1E6. The number of
measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
DRB. PdcpSduAirLossRateDl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.4.2
UL PDCP SDU loss rate
a) This measurement provides the fraction of IP packets (PDCP SDUs) which are lost (not successfully received)
on the uplink. Only user-plane traffic (DTCH) and only PDCP SDUs that have entered PDCP (and given a
PDCP sequence number) are considered. The measurement is split into subcounters per E-RAB QoS level
(QCI). In case of DeNB the measurement provides the packet loss rate for Uu link only (i.e. Un link is
excluded). The measurement is also applicable to RN.
b) SI
maintained for each QCI. In case only a subset of per QCI measurements is supported, a loss rate subcounter
d) Each measurement is an integer value representing the loss rate multiplied by 1E6. The number of measurements
is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
e) The measurement name has the form DRB.PdcpSduLossRateUl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.4.5
4.4.5.1
IP Latency measurements
IP Latency in DL, E-RAB level
a) This measurement provides IP Latency in DL on E-RAB level.

b) CC
3GPP
Release 10
42
3GPP TS 32.425 V10.4.0 (2011-03)
c) This measurement is obtained by the following formula for E-RABs
LatTime
LatSample
LatTime is obtained by accumulating the time T for E-RABs
T t first
part of data volume transmitte d
t data received
ms
The sample of T is made for the new arrived IP data block (PDCP SDU) when there is no other prior data to be
transmitted to the same UE in the eNodeB/RN .
LatSample is obtained by accumulating the number of Latency samples taken on the E-RAB level
The measurement is split into subcounters per E-RAB QoS level (QCI).
d) Each measurement is an integer value representing the time in ms. The number of measurements is equal to the
number of QCIs.
e) The measurement name has the form DRB.IpLateDl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Integrity KPI E-UTRAN IP Latency defined in [13]
4.4.6
4.4.6.1
IP Throughput measurements
IP Throughput in DL
a) This measurement provides IP throughput in downlink. In case of DeNB the measurement provides the
throughput of Uu link only. The measurement is also applicable to RN.
b) DER(N=1)
c) This measurement is obtained according to the definition Scheduled IP Throughput in 3GPP TS 36.314 [11].
Separate counters are maintained for each QCI.
d) Each measurement is a real value representing the throughput in kbits/s. The number of measurements is equal to
the number of QCIs.
DRB.IPThpDl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Integrity KPI E-UTRAN IP Throughput defined in [13].
4.4.6.2
IP Throughput in UL
a) This measurement provides IP throughput in uplink. In case of DeNB the measurement provides the throughput
of Uu link only (i.e. Un link throughput is excluded). The measurement is also applicable to RN
b) DER(N=1)
3GPP
Release 10
43
3GPP TS 32.425 V10.4.0 (2011-03)
c) This measurement is obtained according to the definition Scheduled IP Throughput in 3GPP TS 36.314 [11].
Separate counters are maintained for each QCI.
d) Each measurement is a real value representing the volume in kbits. The number of measurements is equal to the
number of QCIs.
DRB.IPThpUl.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Integrity KPI E-UTRAN IP Throughput defined in [13].
4.5
Radio resource utilization related measurements
4.5.1
DL PRB Usage for traffic
a) This measurement provides the usage (in percentage) of physical resource blocks (PRBs) on the downlink for
DTCH traffic. The measurement is split into subcounters per E-RAB QoS level (QCI). The measurement
provides separate counters for Un and non-Un subframes in case of DeNB.
b) SI
maintained for each QCI. The sum of all supported per QCI measurements shall equal the total PRB usage for
DTCH. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first.
d) Each measurement is an integer value from 0 to 100. The number of measurements is equal to the number of
QCIs plus a possible sum value identified by the .sum suffix.
RRU.PrbDl.QCI
RRU.PrbDlUn.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.2
UL PRB Usage for traffic
a) This measurement provides the usage (in percentage) of physical resource blocks (PRBs) on the uplink for
DTCH traffic. The measurement is split into subcounters per E-RAB QoS level (QCI). The measurement
provides separate counters for Un and non-Un subframes in case of DeNB.
b) SI
maintained for each QCI. The sum of all supported per QCI measurements shall equal the total PRB usage for
DTCH. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first.
d) Each measurement is an integer value from 0 to 100. The number of measurements is equal to the number of
QCIs plus a possible sum value identified by the .sum suffix.
RRU.PrbUl.QCI
3GPP
Release 10
44
3GPP TS 32.425 V10.4.0 (2011-03)
RRU.PrbUlUn.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.3
DL Total PRB Usage
a) This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the downlink
for any purpose. The measurement provides separate counters for Un and non-Un subframes in case of DeNB.
b) SI
d) A single integer value from 0 to 100.
e) RRU.PrbTotDl
RRU.PrbTotDlUn
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.4
UL Total PRB Usage
a) This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the uplink for
any purpose. The measurement provides separate counters for Un and non-Un subframes in case of DeNB.
b) SI
e) RRU.PrbTotUl
RRU.PrbTotUlUn
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.5
4.5.5.1
RACH Usage
Mean number of RACH preambles received
a) This measurement provides the mean number of RACH preambles received in a cell in one second. Separate
counts are provided for dedicated preambles, randomly chosen preambles in group A (aka low range) and
randomly chosen preambles in group B (aka high range).
b) Gauge
c) This measurement is obtained according to the definition in 36.314 [11].
3GPP
Release 10
45
3GPP TS 32.425 V10.4.0 (2011-03)
e) RRU.RachPreambleDedMean
RRU.RachPreambleAMean
RRU.RachPreambleBMean
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.5.2
Distribution of RACH preambles sent
a) This measurement provides the distribution of number of RACH preambles sent by the UE as reported by the
UEs inside the UEInformationResponse message
b) CC
c) This measurement is obtained by incrementing the measurement bin corresponding to the value of IE
numberOfPreamblesSent-r9 ([8] clause 6.2.2) reported by UE inside UEInformationResponse message. The
measurement is incremented each time a UEInformationResponse message containing rach-Report-r9 IE is
received.
e) RRU.RachPreambleDist.BinX
where BinX represents the bin.
Note: Number of bins and the range for each bin is left to implementation.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.5.3
Distribution of RACH access delay
a) This measurement provides the distribution of number of the time before UEs in a cell achieve a successful
attach. The RACH access delay is the time from when a UE sends its first Random Access Preamble until the UE
receives the Random Access Response.
b) CC
c) This measurement is obtained by incrementing the measurement bin corresponding to the access delay
experienced by the UE. The access delay is calculated based upon the value of IE numberOfPreamblesSent and
IE contentionDetected reported by UE inside UEInformationResponse message ([8] clause 6.2.2). The
measurement is incremented each time a UEInformationResponse message containing rach-Report-r9 IE is
received.
e) RRU.RachAccessDelayDist.BinX
where BinX represents the bin.
Note: Number of bins and the range for each bin is left to implementation.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
3GPP
Release 10
4.5.5.4
46
3GPP TS 32.425 V10.4.0 (2011-03)
Percentage of contentious RACH attempts
a) This measurement provides the percentage of UEInformationResponse messages received within the
measurement granularity interval with contentionDetected IE set to TRUE.
b) SI
c) When UEInformationResponse message ([8] clause 6.2.1) continaing rachReport-r9 IE is received the
measurement is updated.
d) Percentage
e) RRU.RachContentionReported
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.5.5
Number of UE RACH reports received
a) This measurement provides the number of UEInformationResponse messages received within the measurement
granularity interval continaing rachReport-r9 IE.
b) CC
c) When UEInformationResponse message ([8] clause 6.2.1) continaing rachReport-r9 IE is received the
measurement is incremented by one.
d) Single integer value
e) RRU.RachReportCount
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.5.6
Percentage of time when all dedicated RACH preambles are used
a) This measurement provides the percentage of time when all dedicated RACH preambles are assigned to UEs.
b) SI
c) During each measurement granularity interval the percentage of time during which all dedicated RACH
preambles were assigned to UEs is computed.
d) Percentage
e) RRU.RachDedicatedPreamblesAssigned
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.6
Cell Unavailable Time
a) This measurement provides the length of time the cell has been unavailable for each cause.
b) DER (n=1)
3GPP
Release 10
47
3GPP TS 32.425 V10.4.0 (2011-03)
c) This measurement is obtained by accumulating the time periods when the cell is unavailable per cause. The
possible cause could be manual intervention, fault and energy saving. The sum of all supported per cause
measurements shall equal the total time periods of cell unavailability. In case only a subset of per cause
d) Each measurement is an integer value (in seconds). The number of measurements is equal to the number of
supported causes plus a possible sum value identified by the .sum suffix.
e) The measurement name has the form RRU.CellUnavailableTime.cause.
Where cause identifies the cause resuling in cell unavailable.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support KPI E-UTRAN Cell Availability defined in [13].
4.5.7
TB related measurements
4.5.7.1
Total Number of DL TBs
a) This measurement provides the total number of TBs transmitted on the downlink in a cell. HARQ
retransmissions are excluded from this measurement.
b) CC
c) On transmission by the eNodeB/RNof TB to UE during the period of measurement. (see 36.321 [16])
e) TB.TotNbrDl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.7.2
Error Number of DL TBs
a) This measurement provides the number of faulty TBs transmitted on the downlink in a cell. HARQ
retransmissions are excluded from this measurement.
b) CC
c) On receipt by the eNodeB/RN of a NACK from UE which indicates a faulty receiption of TB by UE during the
period of measurement. (see 36.321 [16])
e) TB.ErrNbrDl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.7.3
Total Number of UL TBs
a) This measurement provides the total number of TBs on the uplink in a cell. HARQ retransmissions are excluded
from this measurement.
3GPP
Release 10
48
3GPP TS 32.425 V10.4.0 (2011-03)
b) CC
c) On receipt by the eNodeB/RN of TB from UE during the period of measurement. (see 36.321 [16])
e) TB.TotNbrUl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.7.4
Error Number of UL TBs
a) This measurement provides the number of faulty TBs on the uplink in a cell. HARQ retransmissions are
excluded from this measurement.
b) CC
c) On receipt by the eNodeB/RN of a TB on which CRC fails from UE during the period of measurement. (see
36.321 [16])
e) TB.ErrNbrUl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.8
Power utilization measurements
4.5.8.1
Maximum carrier transmit power
a) This measurement provides the maximum carrier transmit power in the measurement granularity interval.
b) SI
c) This measurement is obtained by retaining the maximum value of the total carrier power transmitted in the cell
within the measurement granularity period. The power includes all radio power transmitted, included common
channels, traffic channels, control channels. The value is expressed in dBm.
d) Float in dBm.
e) CARR.MaxTxPwr
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.8.2
Mean carrier transmit power
a) This measurement provides the mean carrier transmit power in the measurement granularity interval.
b) SI
3GPP
Release 10
49
3GPP TS 32.425 V10.4.0 (2011-03)
c) This measurement is obtained by computing the mean value of the total carrier power transmitted in the cell
within the measurement granularity period. The power includes all radio power transmitted, included common
channels, traffic channels, control channels. The value is expressed in dBm.
d) Float in dBm.
e) CARR.AvgTxPwr
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.9
4.5.9.1
PRB Full Utilisation

DL PRB full utilisation
a) This measurement provides the percentage of time during which all available PRBs for traffic on the downlink
have been assigned.
b) SI
c) This measurement represents the percentage of time during the measurement granularity interval during which
all available PRBs for downlink traffic have been assigned to UEs.
e) RRU.PrbCongestionDl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.5.9.2
UL PRB full utilisation
a) This measurement provides the percentage of time during which all available PRBs for traffic on the uplink have
been assigned.
b) SI
c) This measurement represents the percentage of time during the measurement granularity interval during which
all available PRBs for uplink traffic have been assigned to UEs.
e) RRU.PrbCongestionUl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
3GPP
Release 10
50
3GPP TS 32.425 V10.4.0 (2011-03)
4.6
UE-associated logical S1-connection related measurements
4.6.1
UE-associated logical S1-connection establishment
4.6.1.1
Attempted UE-associated logical S1-connection establishment from eNB to

MME
a) This measurement provides the number of attempted UE-associated logical S1-connection establishments from
eNB to MME.
b) CC
c) Transmission of an INITIAL UE MESSAGE by the eNodeB to the MME (See 36.413 [9]).
e) S1SIG.ConnEstabAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Accessibility KPI E-RAB Accessibility defined in [13].
4.6.1.2
Succesful UE-associated logical S1-connection establishment from eNB to

MME
a) This measurement provides the number of successful UE-associated logical S1-connection establishments from
eNB to MME.
b) CC
c) On receipt by the eNB of first message from MME which succeeds INITIAL UE MESSAGE message on an UEassociated logical S1-connection (See 36.413 [9]).
e) S1SIG.ConnEstabSucc
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Accessibility KPI E-RAB Accessibility defined in [13]
4.7
Paging related measurements
4.7.1
Paging Performance
4.7.1.1
Number of paging records discarded at the eNodeB/RN
a) This measurement provides the number of paging records that are discarded at the eNB/RN for paging occasions
in each cell.
b) CC
c) Reception of a S1AP PAGING message from MME/DeNB, see TS 36.413[9], with UE identity which satisfies
the following formulae from TS 36.304 [14].
3GPP
Release 10
51
3GPP TS 32.425 V10.4.0 (2011-03)
X = (T div N)*(UE_ID mod N)

Y = floor(UE_ID/N) mod Ns
AND the maximum number of paging records that can be queued for each paging occasion has been reached.
e) PAG. DiscardedNbr
f) EUtranCellFDD
EUtranCellTDD
g) Valid for packet switched traffic.
h) EPS
4.7.1.2
Number of paging records received by the eNodeB/RN
a) This measurement provides the number of paging records that are received by the eNB/RN for paging occasions
in each cell.
b) CC
c) Reception of a S1AP PAGING message from MME/DeNB, see TS 36.413[9].
e) PAG.ReceivedNbr
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.8
Measurements related to equipment resources
4.8.1
eNodeB/RN processor usage
4.8.1.1
Mean processor usage
a) This measurement provides the mean usage of each key processor during the granularity period. Each equipment
may have more than one key processor, how to indentify key processor is vendor specific.
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval the usage of the processor and then taking
the arithmetic mean for each key processor.
d) Each measurement is an integer value (Unit: %).
e) EQPT.MeanProcessorUsage.ProcessorID
where ProcessorID identifies the key processor of this equipment, the format of ProcessorID is vendor specific.
f) ManagedElement.
h) EPS.
4.8.1.2
Peak processor usage
a) This measurement provides the peak usage of each key processor during the granularity period. Each equipment
may have more than one key processor, how to indentify key processor is vendor specific.
3GPP
Release 10
52
3GPP TS 32.425 V10.4.0 (2011-03)
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval the usage of the processor and then taking
the maximum for each key processor.
d) Each measurement is an integer value (Unit: %).
e) EQPT.PeakProcessorUsage.ProcessorID
where ProcessorID identifies the key processor of this equipment, the format of ProcessorID is vendor specific.
f) ManagedElement.
h) EPS.
4.9
Common LAs of overlapping RATs coverage
4.9.1
Number of incoming IRAT mobility events per LA
a) This measurement provides the number of incoming IRAT mobility events per E-UTRAN cell. This
measurement is split into subcounters per LA.
b) CC.
c) On receipt by the eNB from UE of an RRCConnectionSetupComplete message in which the most significant bit
of the mmegi in RegisteredMME IE is 0 (see TS 36.331 [8]). Each RRCConnectionSetupComplete
message received is added to the relevant per LAI measurement. This definition is only applicable to the
EUTRAN cells of which the adjacent (including overlaid) RAT is set the most significant bit of the <LAC> with
zero.
e) RRC.IratIncMobility.LAI
where LAI identifies the LAI of the RATs coverage the UE comes from.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.10
RF Measurements
4.10.1
CQI Distribution
4.10.1.1
Wideband CQI distribution
a) This measurement provides the distribution of the Wideband CQI (Channel Quality Indicator) reported by UEs
in the cell.
b) CC.
c) This measurement is obtained by incrementing the appropriate measurement bin when a wideband CQI value is
reported by a UE in the cell. When spatial multiplexing is used, CQI for both code words should be considered.
e) CARR.WBCQIDist.BinX
where X represents the CQI value (0 to 15).
f) EUtranCellFDD
EUtranCellTDD
3GPP
Release 10
53
3GPP TS 32.425 V10.4.0 (2011-03)

h) EPS
4.10.1.2
Average sub-band CQI
a) This measurement provides the average value of the sub-band CQI (Channel Quality Indicator) reported by UEs
in the cell.
A subband is a set of k contiguous PRBs where k is a function of system bandwidth. Note the last subband in set
S may have fewer than k contiguous PRBs depending on
. The number of subbands for system bandwidth
given by
is defined by
. The subbands shall be indexed in the order of increasing frequency
and non-increasing sizes starting at the lowest frequency.
b) CC
c) This measurement is obtained by computing the average value of the sub-band CQI reported by UEs in the cell
within the measurement granularity period. One value is produced for each sub-band. The number of sub-bands
depends on the bandwidth used, as specified in [18]. When spatial multiplexing is used, CQI for both code words
should be considered.
d) Float value.
e) CARR.AvgSubCQI.SubbandX
where SubbandX represents the sub-band index, as specified in [18].
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.10.2
Timing Advance Distribution
a) This measurement provides the distribution of the Timing Advance (TA) values transmitted by the eNB to UEs in
the cell.
b) CC.
c) This measurement is obtained by incrementing the appropriate measurement bin when a Timing Advance
Command is sent to a UE in the cell. For Timing Advance Commend see [16] clause 6.1.3.5.
e) CARR. TADist.BinX
where X represents the TA value (0 to 63).
f) EUtranCellFDD
EUtranCellTDD
h) EPS
3GPP
Release 10
54
3GPP TS 32.425 V10.4.0 (2011-03)
Measurements related to Relay Node
5.1
DeNB Reconfiguration related measurements
5.1.1
RN Reconfiguration
5.1.1.1
Number of RNReconfiguration attempts
a) This measurement provides the number of RNReconfiguration attempts sent by DeNB.

b) CC
c) On transmission by the DeNB of a RNReconfiguration message to RN. Each RNReconfiguration message
received is added to the relevant measurement. The message is included in 3GPP TS 36.331 [8].
e) The measurement name has the form RRC.RNReconAttNbr.
f) DeNBCapability
h) EPS
5.1.1.2
Number of RNReconfiguration Completed
a) This measurement provides the number of RNReconfiguration completed received by DeNB

b) CC
c) On receipt by the DeNB of a RNReconfigurationComplete message from RN. Each
RNReconfigurationComplete message received is added to the relevant measurement. The message is included
in 3GPP TS 36.331 [8].
e) The measurement name has the form RRC.RNReconCmptNbr
f) DeNBCapability
h) EPS
3GPP
Release 10
55
3GPP TS 32.425 V10.4.0 (2011-03)
Annex A (informative):
Use cases for performance measurements defintion
This annex provides the concrete use cases for the E-UTRAN performance measurements defined in clause 4.
Without particular constraint, the following use cases defined for eNB apply to both eNB and DeNB. If the specific
constraint is present, which one of the eNB or DeNB the subject use case applies to, is following the constraint.
A.1
Monitor of call(/session) setup performance
Call(/session) setup is one of most important step to start delivering services by the networks to users.
The success or failure of a call(/session) setup directly impacts the quality level for delivering the service by the
networks, and also the feeling of the end user. So the success or failure of call(/session) setup needs be monitored, this
can be achieved by the calculation of call setup success rate which gives a direct view to evaluate the call setup
performance, and the analysis of the specific reason causing the failure to find out the problem and ascertain the
solutions.
In addition, the time duration of the call(/session) setup need to be monitored as it impacts the end user experience, and
by comparison with operators benchmark requirements, the optimization may be required according the performance.
And due to different priority and tolerance for different service type with different OoS level in the networks, the
monitor needs to be opened on each service type and OoS level.
To complete the call(/session) setup procedure, E-UTRAN is mainly responsible for the establishment of radio and S1
signaling connection and service bearer by the RRC connection establishment (See 3GPP TS 36.331[8]), RRC
connection reestablishment after RRC connection dropped due to some reasons like radio link failure or handover
failure etc (See 3GPP TS 36.331[8]) E-RAB setup (See 3GPP TS 36.413[9]) and Initial UE Context Setup (See 3GPP
TS 36.413[9]) procedure.
To support the monitor of success or failure of the call(/session) setup, the performance measurements related to RRC
connection establishment (See 3GPP TS 36.331[8]), RRC connection reestablishment (See 3GPP TS 36.331[8])
procedure, and the performance measurements related to E-RAB setup (See 3GPP TS 36.413[9]) and Initial UE Context
Setup (See 3GPP TS 36.413[9]) procedure for each QoS level are required To support the monitor of time duration of
setup call(/session) setup, the performance measurements related to RRC connection setup time and E-RAB setup time
are required.
A.2
Monitor of E-RAB release
E-RAB is the key and limited resource for E-UTRAN to deliver services. The release of the E-RAB needs to be
monitored as:
- an abnormal release of the E-RAB will cause the call(/session) drop, which directly impacts the QoS delivered by the
networks, and the satisfaction degree of the end user;
- a successfully released E-RAB can be used to setup other requested calls(/sessions). The E-RAB failed to be released
will still occupy the limited resource and hence it can not be used to admit other requested calls(/sessions).
The specific reason causing the abnormal and failed release of the E-RAB is required in order to find out the problem
and ascertain the solutions. And due to different priority and tolerance for different service type with different OoS level
in the networks, the monitor needs to be opened on each service type with OoS level.
The E-RAB can be released by E-RAB Release (See 3GPP TS 36.413[9]) and UE Context Release (See 3GPP TS
36.413[9] and 3GPP TS 36.423[10]) procedure, either initiated by eNodeB or MME.
So performance measurements related to E-RAB Release (See 3GPP TS 36.413[9]) and UE Context Release (See 3GPP
TS 36.413[9]) procedure for each service type with QoS level are necessary to support the monitor of E-RAB release.
3GPP
Release 10
A.3
56
3GPP TS 32.425 V10.4.0 (2011-03)
Monitor of E-RAB level QoS modification
When an E-RAB has been established, the QoS it experiences in the E-UTRAN is dependent upon the E-RAB level
QoS parameters established for the bearer, together with settings of other bearers established in the same cell. If the QoS
experienced by a bearer does not meet the expected performance, or the resource need be reassigned for other bearers,
the E-RAB level QoS may be adjusted (typically with a knock-on effect onto other bearers).
So the modification of E-RAB level QoS parameters needs to be monitored, and due to different priority and tolerance
for different service type with different OoS level in the networks, the monitor needs to be opened on each target service
type with OoS level.
The E-RAB level QoS can be modified by E-RAB Modify procedure (see 3GPP TS 36.413[9]), in which the MME
entity instructs the eNodeB to change one or more QoS parameters on an E-RAB using the E-RAB MODIFY
REQUEST message. The eNodeB typically makes the adjustments as instructed (and adjusts the RRM applied to the
bearer appropriately) but in some circumstances the bearer modification can fail. The eNodeB returns an E-RAB
MODIFY RESPONSE message that tells the MME whether the modification was successful or not for an
unsuccessful modification a cause value is included. It is important for OAM to measure the failure rate of the bearer
modifications, this information can be used, for example, to make adjustments to OAM CM settings.
A.4
Overview handover related Use Cases
Use Case
PM KPI / elementary object
Continuous Network Supervision: Supervision of overall

handover performance. It is essential in network operations to
follow the success rate of various handover. Low handover
success rate will impact user experience, therefore it is
important to define measurements to follow handover success
rate.
- outgoing Intra RAT HO Success Rate (cell) *1

- outgoing Inter RAT HO Success Rate (cell) *1
- outgoing Inter System HO Success Rate (cell) *1 *3
- outgoing Intra Frequency HO Success Rate (cell) *1
- outgoing Inter Frequency HO Success Rate (cell) *1
- outgoing Intra eNB/RN HO Success Rate (cell) *2 *2.1
- outgoing Inter eNB HO Success Rate (cell) *2 *2.2
- outgoing HO to the cells outside the RN
*1: It is expected that the HO success rate may vary depending
on the respective scenarios : intra-RAT, inter-RAT, inter System,
intra frequency, inter frequency
*2: it is expected that the HO success rate may vary depending

on the used external interfaces
*2.1: For the intra-DeNB handover, the handover from a DeNB cell to
an RN under the same DeNB shall be counted separately as the
handover goes through Un interface to RN.
*2.2: For the handover from the DeNB to another eNB/DeNB, the
forwarded handovers for RN in the source DeNB shall not be counted
as these handovers are controlled by RN so cannot directly reflect
DeNB handover performance.
*3: inter system : LTE- non 3GPP HO
3GPP
Release 10
57
Continuous Network Supervision: Supervision of the signal

strength when handovers are triggered. This information is
useful for evaluating the customer experience (e.g.
throughput) at the cell edge and during handover as well for
network planning purposes (e,g, signal strength at the cell
edge).
Troubleshooting: detect a "bad" configuration/neighbor in a
particular direction by analyzing abnormal measurement
report causing HO.
3GPP TS 32.425 V10.4.0 (2011-03)
Signal strength of the serving and neighbouring cell reported by the

UE in handover triggering measurement reports in EUtranRelation..
Troubleshooting: Detection of bad handover relation. The first

use case provides the overall performance of handover
success rate on E-UTRAN cell level, but it is essential to get a
knowledge between which cell pairs the handover success
rate is low. Therefore it is important to know the success rate
on neighbor cell relation basis.
- HO Success Rate (neighbourcell)
Troubleshooting: Reason for started handover
- outgoing HO Success Rate per HO reason (

neighbor cell) *4
To go for further analysis of handover failures, it is essential to

know what causes the handovers. For this we need to know
the success rate of handovers per HO reason.
*4 different results expected e.g. emergency or normal HO
Troubleshooting: Reason for failed handover. To go for further

detailed analysis for handover failure it is important to know
what the reason for handover failure was, or whether the
handover was assisted by measurement gaps or was with
DRX.
It is also important to know if measurement gaps and DRX are
helping in handover procedure or not. (i.e. what is the
handover failure rate if measurement gaps are switched on.
Measurement gaps and DRX can cause more load and
battery consumption to the UE, therefore if these are not
causing any changes in handover failure rate, operators may
not use them)
Network Planning: Traffic flow analysis

or
- outgoing HO Failure Distribution Rate (cell+neighbourcell)

- HO Path Switching Failure Distribution Rate (cell or Interface)
- HO Failure Rate DRX / Non DRX (cell) *5
- Inter frequency HO Failure Rate Meas gap assisted / not assisted
(cell) *5
*5: measurement only on cell basis and not per neighbourcell

due to amount of counters as mentioned above.
- outgoing Intra RAT HO Success Rate (neighbour cell)

- outgoing Inter RAT HO Success Rate (cell)
- outgoing Inter System HO Success Rate (cell)
Network Planning: Handover traffic optimization
A.5
Monitor of cell level QoS and radio resource

utilisation
In an E-UTRAN cell the quality of service achieved is directly influenced by a number of factors, including:
Loading of users on the cell
Traffic loading and characteristics
UE locations and mobility
RRM policies
3GPP
Release 10
58
Scheduling
congestion control
admission control
layer 2 protocol configuration
Mapping of traffic to QCI
Setting of QoS parameters other than the QCI.
3GPP TS 32.425 V10.4.0 (2011-03)
It is very important to be able to monitor the QoS to determine whether the combined effect of these policies,
algorithms and external factors is satisfactory. Unsatisfactory QoS may be rectified by adjusting policies and RRM
settings, for instance.
Cell bit-rate
A fundamental measure of QoS is the throughput (data rate) of the cell. The total cell throughput measured across all
radio bearers gives an indication of the loading and activity in the cell. Adding a per QCI counter allows the loading on
the different QCIs to be measured. For example, if QCI 1 is used exclusively for VoIP then the loading of
conversational speech can be directly determined. Finally, the maximum throughput can indicate to the operator
whether there is enough capacity in the network; for example, is the backhaul sufficient. Separate counters should be
configured on the downlink and uplink. Complexity may be reduced by performing the counters at layer 3, giving the
ingress bit-rate to the eNB on the downlink and the egress bit-rate from the eNB on the uplink.
Cell throughput includes both User Plane data and Control Plane data. To support the User Plane data, necessary
Control Plane data also need to be transmitted. This Control Plane data although required, will not be perceived (felt) by
the User. The total cell throughput helps to evaluate the usage of bandwidth and radio resource.
Operators ideally want to see the Control Plane data as small as possible when compared to the User Plane data without
compromising on the service.
Hence it is important to monitor the total cell throughput as well as how much is occupied by Control Plane Data.
Number of actives UEs

It is also of interest to determine how many users are enjoying the throughput numbers determined for each QCI.
Therefore, we may count the number of users that are active for each QCI here active users have data queued pending
transmission. A simple division of the throughput (data rate) of a QCI by the number of active users on the QCI
indicates the throughput per user on the QCI. For example, taking QCI 1 this metric could indicate the typical codec
rate being employed in the cell. Alternatively, for QCI 9 supporting low priority TCP-based traffic it can indicate the
typical bandwidth pipe size for a user when he has data to send / receive.
In case of DeNB the users can be connected to the eNB directly via Uu interface or connected via RN. Without having
separate measurement for active UEs on Uu and users connected to RN would not provide information on the
throughput per user at DeNB as on Un interface there can be many users connected via RN. Therefore it is beneficial to
provide separatly the number of active users on Uu interfaces and have the same measurement also in RN. Also it is
required to have separate measurements for throughput on Uu interface in DeNB and also in the RN.
DL packet delay
Latency is of prime concern for some services, particularly conversational services like speech and instant messaging.
A counter is added to measure the mean delay for IP packets incurred within the eNodeB. Separate counters are
provided per QCI which are particularly useful when the QCI is used by very few services and the packet sizes vary
little. It is only practical to measure packet delays on the downlink.
In case of DeNB the packet delay includes both the internal processing delay at DeNB and UE/RN as well as the packet
transferring delay on the radio link. As RN UEs packets need to be transferred via Un and Uu while packets for UEs
directly connected to DeNB need to pass through only Un interface, packet delay optimization mechanism may be
different for RN UEs and DeNB UEs. Therefore it is beneficial to have separate measurements on packet delay for Uu
and Un interface.
3GPP
Release 10
59
3GPP TS 32.425 V10.4.0 (2011-03)
DL packet drop rate

When a cell is heavily loaded congestion can take place. When congestion is not severe. the impact is typically the
incurrence of additional delay for non-GBR radio bearers. However, when congestion is severe the eNodeB may be
forced to discard packets. It is important for the operator to have visibility of packet discard so that corrective action
can be instigated (for example, by adjusting admission control settings in the network). It is only practical to measure
packet discards on the downlink. Packet discards on handover should not be included in the count.
PRB Usage
The resource utilisation, measured in terms of physical resource blocks (PRBs), is a useful measure of whether a cell is
lightly loaded or not. Loading is a key input to network capacity planning and load balancing. Furthermore, when
resource utilisation per QCI is reported the distribution of resources between different services can be estimated.
For Type 1 relay, the Un subframe configuration is necessary for RN operation. The RN can only be scheduled by the
DeNB within subframes configured for RN backhaul communication (i.e, Un subframes), while, in principle, the UEs
connected directly to DeNB can be scheduled in any subframe. Therefore, in certain scenarios, it may be possible that
the PRB usage in the Un subframes and in the non-Un subframes is quite different. For example, in case there are many
RNs in the network and only few UEs connected directly to the DeNB, it may happen that the PRB usage in the Un
subframes is quite high while the PRB usage in non-Un subframes is low.Therefore it is seen useful to have separate
measurements on PRB usage for Un subframe and non-Un subframes.
Resource Full Utilisation

Resource congestion is a critical situation in the network that needs to be monitored closely in order to be assessed and
addressed immediately (e.g. by expanding related resources). Measurements reflecting the time during which the
resources are fully used are needed to properly assess the congestion. Congestion affects PRB so appropriate congestion
measurements are needed.
Transport Resource Usage

Transport resource utilisation provides information on the overall traffic of an eNodeB with the rest of the network,
together with information on the traffic of the individual cells it gives the ability to localise bottlenecks. On the other
hand it is a key input for planning of timely expansion of transport (backhaul) resources in the network provides .
Measurements enabling to track the transport resource utilisation are therefore useful.
Hardware Resource Usage

Hardware resource utilisation provides information on the overall load of an eNodeB, together with the information on
the individual loads it gives the ability to localise bottlenecks. On the other hand it is a key input for planning of timely
expansion of hardware resources in the network. Measurements enabling to track the hardware resource utilisation are
therefore useful.
Downlink Air interface packet loss rate

The downlink air interface packet loss can be directly compared with the PELR value of a QCI to see if the packet loss
(over the air interface) aspect of quality of service is being met within the cell (see [12] for more details on PELR). On
the downlink this measurement can be added to the congestion losses (see DL packet drop rate) to determine the total
packet loss rate at the eNodeB. Consequently, the downlink useful bit-rate can be estimated by scaling the
measurement of the downlink PDCP ingress bit-rate by (1 DL packet drop rate) (1 air interface packet loss rate).
Uplink packet loss rate

The uplink air interface packet loss rate (per QCI) can be compared directly with the PELR defined for that QCI. An
estimate of the uplink air interface packet loss may be provided by the Uplink PDCP SDU loss rate. This uplink
measurement is based on PDCP sequence numbers and cannot precisely measure the air interface losses. Any packets
discarded by the UE within the protocol stack (i.e. at layer 2) are also counted since they will have been given a PDCP
sequence number. Discards at layer 3 are not counted.
RACH Usage
The RACH plays a vital role in the following procedures:
-
Initial access from RRC_IDLE;
3GPP
Release 10
60
3GPP TS 32.425 V10.4.0 (2011-03)
Initial access after radio link failure;
Handover requiring random access procedure;
DL data arrival during RRC_CONNECTED requiring random access procedure;
UL data arrival during RRC_CONNECTED requiring random access procedure;
Furthermore, the random access procedure takes two distinct forms:

-
Contention based using a randomly selected preamble (applicable to all five events);
Non-contention based using a dedicated preamble (applicable to only handover and DL data arrival).
In the use-case of RACH configuration optimization, received Random Access Preambles and a contention indicator are
signalled across an OAM interface.
Monitoring of the preamble usage in a cell allows the operator to determine if the resources allocated to the RACH by
the eNodeB are appropriate for the number of random access attempts. If the resources are underutilised then the
operator may reconfigure the eNodeB (via CM) to allocate less resource to RACH thereby freeing up resource for other
uplink transmissions. Alternatively, if the resources are heavily utilised then this is indicative of RACH congestion
leading to increased latency for the procedures listed above. To this effect, measurements directly reflecting RACH
congestion experienced by the eNodeB and by the UEs are useful.
The eNodeB can partition the RACH resource between dedicated preambles, randomly selected preambles in group A
and randomly selected preambles in group B. This partitioning can be evaluated when usage measurements are made
on each set separately.
To further monitor and analyze the latency of the procedures listed above created at the RACH level, the measurement
of the number of RACH preambles sent per RACH attempt is useful.
RACH optimisation function optimises RACH related configurations to achieve minimizing of access delays and
random access collision probability for all the UEs. eNB may request the UEs to report the number of attempts to access
the network (numberOfPreamblesSent in TS 36.331 [8]). Based on the attempting number of random access of all the
UEs, the eNB can know the distribution of RACH preambles sent by UEs and calculate the access probability (AP) of a
cell accurately. The eNB may also request the UEs to report contention detected while attempting to access the network
(contentionDetected in TS 36.331 [8]). Based on the estimated time per random access and the estimated contention
level in the network, the eNB can estimate the access delay probability (ADP) of a cell.
A.6
Monitor of the number of connected users
The number of the connected users in each cell is valuable information for operators to know how many uses are
connecting to E-UTRAN per cell basis. This kind of information can help operator to tune the admission control
parameters for the cell and to do load balancing between cells to ensure that the target percentage or number the of users
admitted achieve the target QoS.
A.7
Monitoring of interference situation
In the LTE radio technology interference has to be coordinated on the basis uplink and downlink i.e. in a coordinated
usage of the UL resources (Physical Resource Blocks, PRBs) and DL Transmitted Power, which lead to improve SIR
and corresponding throughput. These are achieved by means of mechanisms employing channel quality indicators in
support of scheduling/radio resource allocation functions.
These RRM functions in the eNB require the setting of frequency / power restrictions and preferences for the resource
usage in the different cells. Setting and updating these parameters is the task of a network optimisation (done by
operator or automatically by SON).
Use cases for the related interference measurements are e.g. optimisation of ICIC related RRM functionality, the
detection of long distance interferer and the interference due to spurious emissions of neighbour cells. The later case is
assumed only in high load scenarios or unsufficent ICIC functionality due to the the fact that ICIC functionality would
minimise interference autonomously if sufficient bandwidth is available.
3GPP
Release 10
61
3GPP TS 32.425 V10.4.0 (2011-03)
The necessary measurements to identify and anylse the interference situation as input for optimisation tasks has to be
defined.
A.8
Monitor of ARQ and HARQ performance
Reliable Packet Delivery is one of the important Performance factor for a better User experience. HARQ
retransmissions at the MAC layer ensure reliable packet delivery
In addition, RLC can be configured to operate in acknowledged mode for those applications that need very low packet
drops and can tolerate a slightly higher delay from RLC retransmissions.
If a MAC PDU is not delivered, HARQ takes care of retransmitting (upto a maximum configurable number). If all the
retransmissions fail at MAC layer, and if RLC is configured to operate in acknowledged mode, RLCs ARQ mechanism
will take care of any residual packet errors.
It is important to
a) maintain the block error rate or packet error rate within tolerable limits
b) ensure that HARQ retransmissions take care of most packet errors, instead of relying on RLC layer retransmissions
(which would increase the delay).
So, it is important to monitor the performance of these schemes.
ARQ Performance if viewed at QCI level can help in monitoring the distribution for each of the services.
HARQ Performance if viewed at MCS (Modulation Coded Scheme) can help in monitoring the MCS Performance also.
A.9
Monitoring of RF performance
RF Performance reflects the cell loading levels and abnormal conditions.

In the Downlink, Power Resources are managed by the EUTRAN Cell(RAN).
More Power Resources may help in increasing the Capacity of the System. Hence, there the power resources could be
effectively used to optimize the Capacity of the System.
Hence there is a need to keep monitoring the Power Resource Utilization in % and also in absolute terms.
Monitoring of the quality of RF signal in the cell is useful for the purpose of NW planning and overall service quality
assessment. Measurements of Channel Quality Indicator (CQI) reported by UEs is a useful metric reflecting RF signal
quality and service quality.
Timing advance measurements reflect the distance of the UE from the cell antenna. This information reflects the
optimality of the cell antenna location with respect to the cell traffic and is useful in the NW planning process.
Monitoring interference, both uplink and downlink, is an important aspect of monitoring RF performance. For this
purpose, monitoring of UL interference power is useful.
Interference signals in a number of different ways, including frequency, frequency band, direction of interfering signals,
etc. can also be classified by System internal interference and External interference. By efficient frequency planning and
careful
Selection of base station locations, the impact of interference signal can be effectively controlled within an acceptable
scope.uplink interference disturbs the base station receiver. Once the base station receiver is compromised, it leads to
receiving code errors for the whole base station and the sites entire service area is degraded including its network and
service. Of course, customer satisfaction is negatively impacted. So it is very useful to monitor uplink interference of
communication system to do network optimization.
A.10
Monitor of paging performance
In EUTRAN, Paging is under the control of the MME. When the MME wants to page a UE it has to page it in all cells
that belong to the TA(s) to which the UE is registered.
3GPP
Release 10
62
3GPP TS 32.425 V10.4.0 (2011-03)
The paging load per cell is an important measure for the operator as it allows the operator to properly dimension the
resources for paging in the E-UTRAN Cell .
At an E-UTRAN Cell it makes sense to measure the number of discarded paging messages if this is due to some
problem in the eNodeB, such as paging occasion overflow. In that scenario the periodicity of paging occasions can be
reconfigured in order to ensure that all paging messages are transmitted by the eNodeB in the first available paging
occasion, thereby avoiding paging delays and extended call setup delay.
Operators need to know when such an event occurs, in order to identify if the problem is at the E-UTRAN cell level or
not.
In addition to discarded paging records measurement, it is important to know total paging records received so that
discarded paging records ratio can be derived.
Total number of paging records received is important in the sense that, it may be fine if the discarded paging records are
high if discarded paging records ratio is small. On the other hand, it may be problematic if discarded paging records are
low, if discarded paging records ratio turn out to be high.
A.11
Use case of eNodeB processor usage
When network is very busy, for example on important holiday or emergency events happened, the traffic of one eNodeB
is very heavy. So eNodeB processor usage measurements are very important to indicate eNodeB processor load
capability. If eNodeB processor usage is too high, operator must take action to avoid network paralysis.
A.12
Monitor of simultaneous E-RABs
E-RAB is one of the EUTRAN Cell resources which are limited in number.
Hence along with the E-RAB Setup Success Rate, there is a need to keep monitoring the simultaneous E-RABs and
having them at QCI level can help in learning the service distribution in time periods.
Average / Maximum simultaneous E-RABs, can help to know the average / maximum utilization of the resources in
time periods, thereby helping to do necessary resource capacity engineering.
A.13
Monitoring of Mobility Robustness Optimization

(MRO)
The following measurement is defined specifically to monitor the performance of intra-frequency handover
optimisation:
Number of handover failures for MRO.
The measurement examines handover related events in which the serving cell of a RRC connected UE is changed.
Handover related events are either normal successful handovers, or they are failures. Different failure modes are
possible and the measurement provides counts for the occurrences of the failure modes related with MRO, too early,
too late and to wrong cell. The detailed definitions of these modes are captured in [12]. The counters provide
visibility of the mix of failure problems that the handover optimistion function is tackling.
In addition to event-based (i.e. reactive) optimization of handover performance, a pro-active optimization is possible by
monitoring the dynamics of handover triggering from UE measurement reports.
A.14
Monitor of BLER performance
The TB Error Rate in UL/DL can directly reflect the BLER, and has an influence on MCS selection and user
throughput. It can be helpful to estimate the performance of radio resource management like radio resource schedulein
transport layer and be helpful in trouble shooting. Furthermore, they should be taken into account to optimize the
system performance. To obtain TB Error Rate by calculating, the number of total and error TBs transmitted in a cell
should be monitored.
3GPP
Release 10
A.15
63
3GPP TS 32.425 V10.4.0 (2011-03)
Monitoring of common LAs of overlapping target

RATs coverage
For CS fallback in EPS, as defined in section 5.1A of 3GPP TS 23.272 [17], the fallback procedure is likely to be faster
if the network can allocate a Location Area to the UE that is the LA of the overlapping target RAT's coverage. For this
situation, the MME should avoid allocating TAI lists that span multiple Location Areas of the target RAT, this can be
achieved by:
-
configuring the E-UTRAN cell's TAI to align the LA boundary of the target RAT;
the MME being configured to know which TAIs are within which LA; and
the MME using the TAI of the current E-UTRAN cell to derive the LAI.
Also as specified in section 4.3.4 of 3GPP TS 23.272 [17], to facilitate the alignment of TA boundaries with LA
boundaries, the E-UTRAN can gather statistics (from the inbound inter-RAT mobility events of all UEs) of the most
common LAs indicated in the RRC signalling.
From such measurements per E-UTRAN cell basis, operators 1) can know the common LA(s) of the overlapping target
RATs coverage for each TA, which is useful to configure the TAI list within which LA boundary to MME, operators
can also 2) detect the case that TA spans multiple LAs if different most common LA(s) is/are reported from the EUTRAN cells in the same TA, operators may take actions to rectify it if needed.
A.16
Monitoring of Energy Saving
Beside monitoring of the energy consumption it is also important to differentiate if the cell unavailability or the failure
of the RRC connection establishment happens because of Energy Saving as Energy Saving Management feature is by
the Operator on purpose. Therefore such failures should be distinguishable from other network failures, therefore should
be counted separately. With the separate cell unavailability counter due to Energy Saving makes it possible to deduct the
cell downtime due to Energy Savings from the total cell outage.
A.17
Monitoring of RNReconfiguration
The purpose of RNReconfiguration related procedure is to configure/reconfigure the RN subframe configuration and/or
to update the system information relevant for the RN in RRC_CONNECTED.
The system information and subframe configuration is very important for RN, but the RN does not need to apply the
system information acquisition and change monitoring procedures, if configured with an RN subframe configuration.
Upon change of any system information relevant to an RN, E-UTRAN provides the system information blocks
containing the relevant system information to RNs with an RN subframe configuration via dedicated signalling using
the RNReconfiguration message. This dedicated signalling replaces any stored system information acquired through the
system information acquisition procedure.
Because the RN is semi-duplex, to avoid the transmission conflict between access link (between UE and RN) and
backhaul link (between RN and DeNB), the subframe of RN is semi-statically assigned (see TR 36.814) and the
configuration information is included in the RNReconfiguration message.
During the RN operation, failures of backhaul link will cause unsuccessful RN reconfiguration. In that case, RN will not
get any response from DeNB. The defined performance counter will help to compute how many respose messages are
missing. Depending on this result, operators could easily make network planning to consider fix or optimize the
backhaul link quality.
3GPP
Release 10
64
3GPP TS 32.425 V10.4.0 (2011-03)
Annex B (informative):
Change history
Change history
Date
TSG #
Mar 2009 SP-43
Jun 2009 SP-44
Jun 2009 SP-44
Sep 2009 SP-45
Sep 2009
Sep 2009
Mar 2010
Mar 2010
SP-45
SP-45
SP-47
SP-47
Mar 2010 SP-47

Mar 2010
Mar 2010
Jun 2010
Jun 2010
Jun 2010
Jun 2010
SP-47
SP-47
SP-48
SP-48
SP-48
SP-48
Jun 2010
Sep 2010
Sep 2010
Sep 2010
Sep 2010
SP-48
SP-49
SP-49
SP-49
SP-49
Dec 2010 SP-50

Mar 2011 SP-51
Mar 2011 SP-51
Mar 2011
Mar 2011
Mar 2011
Mar 2011
Mar 2011
Mar 2011
SP-51
SP-51
SP-51
SP-51
SP-51
SP-51
Mar 2011
Mar 2011
Mar 2011
SP-51
SP-51
SP-51
Mar 2011
SP-51
Mar 2011
Mar 2011
Mar 2011
Mar 2011
Mar 2011
Mar 2011
Mar 2011
SP-51
SP-51
SP-51
SP-51
SP-51
SP-51
SP-51
Mar 2011
SP-51
Mar 2011
Mar 2011
Mar 2011
Mar 2011
SP-51
SP-51
SP-51
SP-51
TSG Doc. CR Rev Subject/Comment

SP-090143 --Presentation to SA for information and approval
SP-090408 002 -Add missing E-UTRAN measurement for paging discards at the
eNodeB - Align with 36.304 and 32.426
SP-090290 001 -Addition of eNodeB processor usage related measurements
SP-090542 004 -Correction on the IP latency and additional SAE Bearers setup
measurements
SP-090542 006 -Alignment of PRB usage related measurements with 36.314
SP-090627 007 -Add SAE Bearer number related measurements
SP-100035 010 -Add RRC connection release as a PM counter
SP-100035 011 -Introduction of handover failure PM counters for handover
optimisation
SP-100035 012 -Add a PM counter of RRC connection establishments per failure
cause
SP-100036 008 -Incorrect section numbering
SP-100036 009 -Add TB related measurements
SP-100264 013 -Editorial changes to clause References
SP-100259 022 -Correct L3 messages in measurement definitions
SP-100412 018 -Add IP Throughput measurements
SP-100262
-Missing Measurement related to common LAs to support faster CS
015
fallback in EPS
SP-100262 019 -Add the missing reference of causes in HO measurements
SP-100488 023 -Correction of intra-RAT HO measurements
SP-100489 024 -Modification of E-RAB release related measurements
SP-100489 025 -Addition of measurements for pagings received
SP-100493
-Modifying RRC establishment failure and Cellunavailability
026
measurements due to Energy Saving
SP-100878 030 1
Correcting L3 messages and cleanup
SP-110095 031 1
Apply the RRC connection setup related measurements to RN
Apply the RRC connection reestablishment related measurements to
SP-110095 032 2
RN
SP-110095 033 1
Apply the E-RAB setup related measurements to RN
SP-110095 034 2
Apply the abnormal E-RAB release related measurements to RN
SP-110095 035 1
Addition of HO related measurements to RN
SP-110095 036 1
Apply the eNB measurements to DeNB as well
SP-110095 044 1
Adding measurements on power utilization
Change counter for RACH usage from 'Cumulative Counter' to
SP-110093 048 'Gauge'
SP-110095 053 1
Add measurements for maximum PRB usage
SP-110095 054 1
Add measurements for radio coverage
Add measurements for radio coverage, handover triggering, RACH
SP-110095 055 9
performance
Add RRC connection setup and UE context release related
SP-110095 058 1
measurements of RN
SP-110095 059 1
Add E-RAB release and modification related measurements of RN
SP-110095 060 Add inter-RAT HO related measurements of RN
SP-110095 061 Add cell level radio bearer QoS related measurements of RN
SP-110095 062 Add Radio resource utilization related measurements of RN
SP-110095 063 Add paging related measurements of RN
SP-110095 064 Add equipment resources related measurements of RN
Adding separate counters for Un link and Uu link L2 measurements
SP-110095 065 2
in DeNB.
Add RNReconfiguration related measurements to DeNB - Align with
SP-110095 066 2
RAN2 TS 36.331
SP-110098 067 1
Introduction of PM counters on distribution of RACH preambles sent
SP-110095 068 1
Add HO to RN in intro-eNB HO measurements
SP-110095 069 1
Exclude HOs from RN in inter-eNB HO measurements
SP-110094 071 2
Correct CSFB measurements to exclude inapplicable scenarios
3GPP
Cat Old
-1.0.0
F
8.0.0
New
8.0.0
8.1.0
B
A
8.1.0
9.0.0
9.0.0
9.1.0
A
B
F
F
9.0.0
9.0.0
9.1.0
9.1.0
9.1.0
9.1.0
9.2.0
9.2.0
9.1.0
9.2.0
D
B
D
A
A
A
9.2.0
9.2.0
10.0.0
10.0.0
10.0.0
10.0.0
10.0.0
10.0.0
10.1.0
10.1.0
10.1.0
10.1.0
A
A
C
B
10.0.0
10.1.0
10.1.0
10.1.0
10.1.0
10.1.0
10.2.0
10.2.0
10.2.0
10.2.0
10.2.0
10.3.0
10.3.0
10.3.0
10.4.0
10.4.0
10.3.0
10.3.0
10.3.0
10.3.0
10.3.0
10.3.0
10.4.0
10.4.0
10.4.0
10.4.0
10.4.0
10.4.0
10.3.0
10.3.0
10.3.0
10.4.0
10.4.0
10.4.0
10.3.0
10.4.0
10.3.0
10.3.0
10.3.0
10.3.0
10.3.0
10.3.0
10.3.0
10.4.0
10.4.0
10.4.0
10.4.0
10.4.0
10.4.0
10.4.0
10.3.0
10.4.0
10.3.0
10.3.0
10.3.0
10.3.0
10.4.0
10.4.0
10.4.0
10.4.0
C
A
B
B
B
B
B
C
B
A
B
B
B
B
B
B
B
B
B
B
B
B
B
B
C
A

3GPP TS 32.425: Performance Measurements (E-UTRAN)

Uploaded by

Copyright:

Available Formats

3GPP TS 32.425: Performance Measurements (E-UTRAN)

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

3GPP TS 32.425: Performance Measurements (E-UTRAN)

Uploaded by

Copyright:

Available Formats

3rd Generation Partnership Project;

Technical Specification Group Services and System Aspects;

3GPP TS 32.425 V10.4.0 (2011-03)

3GPP TS 32.425 V10.4.0 (2011-03)

Measurement family and abbreviations................................................................................................

Measurements related to eNodeB, Donor eNodeB and Relay Node.....................................................

3GPP TS 32.425 V10.4.0 (2011-03)

Intra-eNB/RN Handover related measurements....................................................................................

3GPP TS 32.425 V10.4.0 (2011-03)

Measurements related to Relay Node...................................................................................................

3GPP TS 32.425 V10.4.0 (2011-03)

Use cases for performance measurements defintion.................................

Monitor of call(/session) setup performance.........................................................................................

Monitor of E-RAB release....................................................................................................................

Monitor of E-RAB level QoS modification..........................................................................................

Overview handover related Use Cases..................................................................................................

Monitor of cell level QoS and radio resource utilisation......................................................................

Monitor of the number of connected users...........................................................................................

Monitoring of interference situation.....................................................................................................

Monitor of ARQ and HARQ performance............................................................................................

A.10 Monitor of paging performance............................................................................................................

3GPP TS 32.425 V10.4.0 (2011-03)

Performance Management (PM); Concept and requirements

Performance Management (PM); Performance measurements GSM

Performance Management (PM); Performance measurements - Definitions and template

Performance Management (PM); Performance measurements Universal Terrestrial Radio Access

Performance Management (PM); Performance measurements Core Network (CN) Circuit

Performance Management (PM); Performance measurements Teleservice

Performance Management (PM); Performance measurements IP Multimedia Subsystem (IMS)

Performance Management (PM); Evolved Performance measurements Universal Terrestrial

Performance Management (PM); Evolved Packet Core (EPC)

3GPP TS 32.425 V10.4.0 (2011-03)

3GPP TS 32.425 V10.4.0 (2011-03)

The present document describes the measurements for E-UTRAN.

Header 1: Network Element (e.g. measurements related to eNodeB);

Header 2: Measurement function (e.g. RRC connection setup related measurements);

3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".

3GPP TS 32.102: "Telecommunication management; Architecture".

3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept

3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept

3GPP TS 32.404: "Performance Management (PM); Performance measurements - Definitions and

3GPP TS 32.425 V10.4.0 (2011-03)

3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1

3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2

3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2

3GPP TS 32.522: "Technical Specification Group Services and SystemAspects;

Measurement family and abbreviations

DRB (measurements related to Data Radio Bearer)

3GPP TS 32.425 V10.4.0 (2011-03)

Measurements related to eNodeB, Donor eNodeB

Applicability of measurements to eNB and DeNB

RRC connection related measurements

RRC connection establishment

Attempted RRC connection establishments

3GPP TS 32.425 V10.4.0 (2011-03)

Successful RRC connection establishments

Failed RRC connection establishments

3GPP TS 32.425 V10.4.0 (2011-03)

g) Valid for packet switched traffic