Ts - 132425v160500p (RAN)
Ts - 132425v160500p (RAN)
Ts - 132425v160500p (RAN)
0 (2020-11)
TECHNICAL SPECIFICATION
LTE;
Telecommunication management;
Performance Management (PM);
Performance measurements Evolved Universal Terrestrial
Radio Access Network (E-UTRAN)
(3GPP TS 32.425 version 16.5.0 Release 16)
3GPP TS 32.425 version 16.5.0 Release 16 1 ETSI TS 132 425 V16.5.0 (2020-11)
Reference
RTS/TSGS-0532425vg50
Keywords
LTE
ETSI
Important notice
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 2 ETSI TS 132 425 V16.5.0 (2020-11)
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 3 ETSI TS 132 425 V16.5.0 (2020-11)
Contents
Intellectual Property Rights ................................................................................................................................2
Legal Notice .......................................................................................................................................................2
Modal verbs terminology....................................................................................................................................2
Foreword.............................................................................................................................................................9
1 Scope ......................................................................................................................................................11
2 References ..............................................................................................................................................11
3 Measurement family and abbreviations..................................................................................................12
3.1 Measurement family ......................................................................................................................................... 12
3.2 Abbreviations ................................................................................................................................................... 13
4 Measurements related to eNodeB, Donor eNodeB and relay node ........................................................14
4.0 Applicability of measurements ......................................................................................................................... 14
4.1 RRC connection related measurements ............................................................................................................ 15
4.1.1 RRC connection establishment ................................................................................................................... 15
4.1.1.0 General .................................................................................................................................................. 15
4.1.1.1 Attempted RRC connection establishments .......................................................................................... 15
4.1.1.2 Successful RRC connection establishments .......................................................................................... 15
4.1.1.3 Failed RRC connection establishments ................................................................................................. 16
4.1.1.4 Failed RRC connection establishment per failure cause ....................................................................... 16
4.1.2 RRC connection re-establishment............................................................................................................... 16
4.1.2.0 General .................................................................................................................................................. 16
4.1.2.1 Attempted RRC connection re-establishments ...................................................................................... 17
4.1.2.2 Successful RRC connection re-establishments ..................................................................................... 17
4.1.2.3 Failed RRC connection re-establishments ............................................................................................ 17
4.1.3 RRC connection number ............................................................................................................................. 18
4.1.3.1 Mean number of RRC Connections ...................................................................................................... 18
4.1.3.2 Maximum number of RRC Connections ............................................................................................... 18
4.1.3.3 RRC connection usage per UE multi-RAT capability .......................................................................... 19
4.1.4 RRC connection setup time ........................................................................................................................ 19
4.1.4.1 Mean RRC connection setup time ......................................................................................................... 19
4.1.4.2 Maximum RRC connection setup time ................................................................................................. 19
4.1.5 UE CONTEXT Release .............................................................................................................................. 20
4.1.5.1 Number of UE CONTEXT Release Request initiated by eNodeB/RN ................................................. 20
4.1.5.2 Successful UE CONTEXT Release ...................................................................................................... 20
4.1.6 Inactivity timer............................................................................................................................................ 21
4.1.6.1 Number of successful RRC connection setups in relation to the time between successful RRC
connection setup and last RRC connection release ............................................................................... 21
4.2 E-RAB related measurements .......................................................................................................................... 21
4.2.0 General........................................................................................................................................................ 21
4.2.1 E-RAB setup ............................................................................................................................................... 21
4.2.1.1 Number of initial E-RABs attempted to setup ...................................................................................... 21
4.2.1.2 Number of initial E-RABs successfully established ............................................................................. 22
4.2.1.3 Number of initial E-RABs failed to setup ............................................................................................. 22
4.2.1.4 Number of additional E-RABs attempted to setup ................................................................................ 23
4.2.1.5 Number of additional E-RABs successfully established ....................................................................... 23
4.2.1.6 Number of additional E-RABs failed to setup ...................................................................................... 24
4.2.1.7 Mean E-RAB Setup time ...................................................................................................................... 24
4.2.1.8 Maximum E-RAB Setup time ............................................................................................................... 24
4.2.1.9 Number of E-RABs attempted to establish for incoming HOs ............................................................. 25
4.2.1.10 Number of E-RABs successfully established for incoming HOs .......................................................... 25
4.2.2 E-RAB release ............................................................................................................................................ 26
4.2.2.1 Number of E-RABs requested to release initiated by eNodeB/RN per QCI ......................................... 26
4.2.2.3 Number of E-RABs attempted to release .............................................................................................. 27
4.2.2.4 Number of E-RAB successfully released .............................................................................................. 27
4.2.2.5 Number of E-RAB failed to release ...................................................................................................... 28
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 4 ETSI TS 132 425 V16.5.0 (2020-11)
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 5 ETSI TS 132 425 V16.5.0 (2020-11)
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 6 ETSI TS 132 425 V16.5.0 (2020-11)
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 7 ETSI TS 132 425 V16.5.0 (2020-11)
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 8 ETSI TS 132 425 V16.5.0 (2020-11)
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 9 ETSI TS 132 425 V16.5.0 (2020-11)
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:
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.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.425 Performance Management (PM); Evolved Performance measurements Universal Terrestrial Radio
Access Network (E-UTRAN)
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].
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 10 ETSI TS 132 425 V16.5.0 (2020-11)
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 11 ETSI TS 132 425 V16.5.0 (2020-11)
1 Scope
The present document describes the measurements for E-UTRAN.
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.
- Header 3: Measurements.
2 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 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".
[4] Void.
[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".
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 12 ETSI TS 132 425 V16.5.0 (2020-11)
[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 E-
UTRAN: Definitions".
[14] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
procedures in idle mode".
[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".
[19] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management".
[20] ES 203 228 V1.0.0: "Environmental Engineering (EE); Assessment of mobile network energy
efficiency".
[21] ES 203 228 V1.0.0: "Environmental Engineering (EE); Assessment of mobile network energy
efficiency".
[23] ETSI ES 202 336-12 V1.1.1: "Environmental Engineering (EE); Monitoring and control interface
for infrastructure equipment (power, cooling and building environment systems used in
telecommunication networks); Part 12: ICT equipment power, energy and environmental
parameters monitoring information model".
[24] 3GPP TS 36.465: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and
Wireless LAN (WLAN); Xw interface user plane protocol".
[25] 3GPP TS 36.361: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-WLAN Radio
Level Integration Using IPsec Tunnel (LWIP) encapsulation; Protocol specification".
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 13 ETSI TS 132 425 V16.5.0 (2020-11)
- LWI (measurements related to LTE and WLAN integration, including LWA and LWIP).
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
NOTE: Below there's a list of abbreviations used within the measurement types for field E of the measurement
template (see 3GPP TS 32.404 [6]).
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 14 ETSI TS 132 425 V16.5.0 (2020-11)
Alloc Allocation
AOA Angle of Arrival
Att Attempt(s,ed)
Conn Connection
Ded Dedicated
DL Downlink
EE Energy Efficiency
ENB eNodeB
Err Error
Estab Establish (ed,ment)
Fail Fail(ed, ure)
Freq Frequency
Inc Incoming
Out Outgoing
Pkt Packet(s)
Prep Prepare(/Preparation)
Late Latency
Mod Modify(/Modification)
Nbr Number
Rel Release(s,d)
Res Resource
RSRP Reference Signal Received Power
RSRQ Reference Signal Received Quality
Succ Success(es,ful)
Tot Total
UL Uplink
DC Intra-E-UTRA Dual Connectivity
EN-DC E-UTRA-NR Dual Connectivity
MCG Master Cell Group
MN Master Node
MR-DC Multi-RAT Dual Connectivity
NE-DC NR-E-UTRA Dual Connectivity
NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity
SCG Secondary Cell Group
SN Secondary Node
If the specific constraint is present, which one of above scenarios the subject measurement applies to,
is following the constraint.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 15 ETSI TS 132 425 V16.5.0 (2020-11)
4.1.1.0 General
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".
b) CC
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area
determination in [21].
2) CC
4) 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.
6) EUtranCellFDD
EUtranCellTDD
8) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 16 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area
determination in [21].
b) CC
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.0 General
The three measurement types defined in the subclause 4.1.2.n are subject to the "2 out of 3 approach".
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 17 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC.
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC.
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 18 ETSI TS 132 425 V16.5.0 (2020-11)
The sum of all supported per cause measurements shall equal the total number of RRC connection re-
establishment failures. 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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval, the number of RRC connections for each E-
UTRAN Cell and then taking the arithmetic mean
e) RRC.ConnMean
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval, the number of RRC connections for each E-
UTRAN cell and then taking the maximum.
e) RRC.ConnMax
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 19 ETSI TS 132 425 V16.5.0 (2020-11)
b) DER (n=1)
c) This measurement is obtained by accumulating successful RRC connections per UE multi-RAT capability after
the receipt of a RRC CONNECTION SETUP COMPLETE message by the eNodeB/RN. The possible UE multi-
RAT capabilities are included in TS 36.331 [8]. One or more subcounters are stepped based on received UE
multi-RAT capabilities.
e) RRC.ConnUsage.geranCs
RRC.ConnUsage.geranPs
RRC.ConnUsage.cdma20001xRTT
RRC.ConnUsage.utra
RRC.ConnUsage.eutra
RRC.ConnUsage.eutra-nr
RRC.ConnUsage.nr
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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].
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 20 ETSI TS 132 425 V16.5.0 (2020-11)
b) GAUGE.
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].
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC.
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.
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..
b) CC.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 21 ETSI TS 132 425 V16.5.0 (2020-11)
e) UEContext.RelSuccNbr.
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.1.6.1 Number of successful RRC connection setups in relation to the time between
successful RRC connection setup and last RRC connection release
a) This measurement provides the histogram as function of the number of successful RRC Connection setups and
the time between the successful RRC Connection setup attempt and last RRC Connection release for the UE with
the same S-TMSI and long inactivity timer configured.
It is not counted to the histogram in case last RRC Connection release of the UE with the same S-TMSI is caused
by call drops or handover.
b) CC.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 22 ETSI TS 132 425 V16.5.0 (2020-11)
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
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area
determination in [21].
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.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 23 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area
determination in [21].
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.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS.
i) This measurement is to support the Accessibility KPI “E-RAB Accessibility” defined in [13].
Another usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area
determination in [21].
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.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Accessibility KPI “E-RAB Accessibility” defined [13].
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 24 ETSI TS 132 425 V16.5.0 (2020-11)
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.
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS.
i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area
determination in [21].
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].
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 25 ETSI TS 132 425 V16.5.0 (2020-11)
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].
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
c) On receipt by the eNB of a X2AP HANDOVER REQUEST or S1AP HANDOVER REQUEST message; or on
transmission by the eNB of the RRCConnectionReconfiguration message to the UE triggering the intra-eNB
handover (see TS 36.331 [8]), all E-RABs of this UE (but not only the E-RABs in the message) are counted for
this measurement to the target E-UTRAN cell. Each E-RAB attempted to establish 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
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 26 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
d) Each measurement is an integer value. The number of measurements is equal to the number of supported causes.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 27 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area
determination in [21].
b) CC
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 28 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area
determination in [21].
b) CC
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 29 ETSI TS 132 425 V16.5.0 (2020-11)
E-RABs with bursty flow are considered active when there is still data in the DL or UL buffer. E-RABs with
continuous flow are always seen as active E-RABs in the context of this measurement.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-RABs attempted to release when the E-RAB is active according to the definition of bursty
flow/continuous flow. In case only a subset of per QCI measurements is supported, a sum subcounter will be
provided first.
How to define for a particular QCI if the E-RAB is of type bursty flow or continuous flow is outside the scope of
this document.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Retainability KPI “E-RAB Retainability” defined in [13].
b) CC
c) Each sample is measured from the point in time the QCI1 E-RAB has been successfully established via initial
Context setup or additional E-RAB setup procedure or incoming handover till the point in time the E-RAB is
released via eNB or EPC initiated release procedure or successful outgoing handover according to 3GPP TS
36.413 due to normal release cause. Triggering is done for the bin the given sample falls in.
e) The measurement name has the form QCI1ERAB.NormCallDurationBinX where X denotes the X-th bin from
total number of N configured bins. X-th bin stands for the normal call duration which is within the range from tx-
1 to tx.
f) Cell
h) EPS
i) Each histogram function is represented by the configured number of bins with configured bin width by operator.
b) CC
c) Each sample is measured from the point in time the QCI1 E-RAB has been successfully established via initial
Context setup or additional E-RAB setup procedure or incoming handover till the point in time the E-RAB is
released via eNB or EPC initiated release procedure according to 3GPP TS 36.413 due to abnormal release
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 30 ETSI TS 132 425 V16.5.0 (2020-11)
cause. The time period with ongoing RLF or user inactivity timer are excluded from measurement the sample
duration. Triggering is done for the bin the given sample falls in.
e) The measurement name has the form QCI1ERAB.AbnormCallDurationBinX where X denotes the X-th bin from
total number of N configured bins. X-th bin stands for the normal call duration which is within the range from tx-
1 to tx.
f) Cell
h) EPS
i) Each histogram function is represented by the configured number of bins with configured bin width by operator.
h) EPS
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
TS 36.413 [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs
attempted to modify the QoS parameter. 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
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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
TS 36.413 [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs
successfully modified the QoS parameter. 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
possible sum value identified by the .sum suffix.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 31 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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.
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
e) ERAB.SessionTimeUE
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 32 ETSI TS 132 425 V16.5.0 (2020-11)
i) This measurement is to support the Retainability KPI “E-RAB Retainability” defined in [13].
b) CC
c) Number of s“in ession ”seconds aggregated for E-RABs with a certain QCI. , where “in session” has the
following definitions:
- E-RABs with bursty flow is said to be “in session” for a UE if any E-RAB data on any Data Radio Bearer (UL
or DL) has been transferred during the last 100 ms for that QCI
- E-RABs with continuous flow are always seen as being “in session” in the context of this measurement, and the
session time is increased from the first data transmission on the E-RAB until 100 ms after the last data
transmission on the E-RAB.
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 subcounter will be
provided first.
How to decide for a particular QCI if the E-RAB is of type continuous flow is outside the scope of this
document.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
g) EUtranCellFDD
EUtranCellTDD
i) EPS
j) This measurement is to support the Retainability KPI “E-RAB Retainability” defined in [13].
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.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 33 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC.
c) Transmission of the RRCConnectionReconfiguration message by the eNB/RN to the UE triggering the intra-
eNB/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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 34 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS
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.
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.IntraEnbOutSucc.Cause
where Cause identifies the cause for handover.
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
measurements is supported, a sum subcounter will be provided first.
e) HO.IntraDenbOutPrepToRnAtt.Cause
where Cause identifies the cause for handover
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 35 ETSI TS 132 425 V16.5.0 (2020-11)
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.
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.IntraDenbOutToRnAtt.Cause
where Cause identifies the cause for handover
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
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.IntraDenbOutToRnSucc.Cause
where Cause identifies the cause for handover.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 36 ETSI TS 132 425 V16.5.0 (2020-11)
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
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.
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.InterEnbOutAtt.Cause
where Cause identifies the cause for handover
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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
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.
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 37 ETSI TS 132 425 V16.5.0 (2020-11)
e) HO.InterEnbOutSucc.Cause
where Cause identifies the cause for handover.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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] . In case of CA, this attempted handover is
only added to the neighbour cell relation from the source EUTRAN cell, through which the
RRCConnectionReconfiguration message is sent to the UE, to the target EUTRAN cell appointed in the
“MobilityControlInfo” IE of the RRCConnectionReconfiguration message.
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.
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.OutAttTarget.Cause
where Cause identifies the cause for handover
f) EUtranRelation
h) EPS
b) CC.
c) Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source)
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] . In case of CA,
this succesful handover is only added to same the neighbour cell relation that the corresponding attempted
handover is counted at (i.e., the same neighbour cell relation that the measurement defined in subcluse 4.3.1.3.1
is counted at). The sum of all supported per cause measurements shall equal the total number of outgoing intra-
RAT 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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 38 ETSI TS 132 425 V16.5.0 (2020-11)
e) HO.OutSuccTarget.Cause
where Cause identifies the cause for handover.
f) EUtranRelation
h) EPS
b) CC
c) The measurements of too early handovers, too late handovers and to wrong cell handovers are obtained
respectively 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].
Besides being added to the measurement of total too late handovers, each too late handover (identified by the
eNB according to the definitions in TS 36.300 [12]) is also added to the relevant subcounter indicating the
threshold of the serving cell itself configured in the measurement report triggering events (see 36.331 [18]) was
not crossed or the threshold of the neighbour cell configured in the measurement report triggering events was not
crossed if more than one threshold triggering a measurement report is configured to the UEs for the involved
neighbour relation and the following UE measurement results are available for both cells involved in the too late
handover
- rsrpResult of “measResultLastServCell” and
- rsrpResult of the subject neighbour cell in “measResultNeighCells”
in
a) the “RLF report” IE in the received RRC message “UEInformationResponse” (see 36.331 [18]), in case both
cells involved in the too late handover belong to the same eNB,
or
b) the “UE RLF Report Container” IE in the received X2 message “RLF Indication”, in case the cells involved in
the too late handover belong to different eNBs.
The uncrossed threshold (of the serving itself and the neighbour) is identified by comparing the UE measurement
results above with the configured thresholds (adding the corresponding hysteresis, see 36.331 [18]) of the
measurement report triggering events,
- if the threshold of the serving cell itself was not crossed, the observed too late handover is then added to the
subcounter (HO.OutFail.TooLateOwnNotCrossed) indicating the threshold of the serving cell was not crossed
- if the threshold of the neighbor cell itself was not crossed, the observed too late handover is then added to the
subcounter (HO.OutFail.TooLateNeighborNotCrossed) indicating the threshold of the neighbour cell was not
crossed
- if the thresholds of both the serving cell itself and the neighbour cell were not crossed, then this too late
handover is added to both subcounters (HO.OutFail.TooLateOwnNotCrossed and
HO.OutFail.TooLateNeighborNotCrossed) indicating the threshold of serving cell itself was not crossed and the
threshold of the neighbour cell was not crossed
- if no threshold was not crossed, then this handover is only added to the measurement of total too late
handovers but not to the subcounter indicating the threshold of the serving cell itself was not crossed or the
threshold of the neighbour cell was not crossed.
If only one threshold triggring the measurement report is configured to the UEs for the involved neighbour
relation or the UE measurements above are not available, the observed too late handover is only added to the
measurement of total too late handovers but not to the subcounter indicating the threshold of the serving cell
itself was not crossed or the threshold of the neighbour cell was not crossed.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 39 ETSI TS 132 425 V16.5.0 (2020-11)
HO.OutFail.TooEarly
HO.OutFail.TooLate
Which indicates the total number of too late handovers identified by the eNB according to the definitions in
TS 36.300 [12].
HO.OutFail.TooLateOwnNotCrossed
Which indicates the number of too late handovers for which the threshold of the serving cell itself was not
crossed.
HO.OutFail.TooLateNeighborNotCrossed
Which indicates the number of too late handovers for which the threshold of the neighbor cell was not
crossed.
HO.OutFail.ToWrongCell
Which indicates the number of “handover to wrong cell” cases on the NR (NR A B in Annex A.13)
towards the target cell (see 36.300 [12]). It is up to the eNodeB to decide whether or not the HO parameters
of this NR are problematic in the “handover to wrong cell” case.
HO.OutFail.HwcReestablish
Which indicates the number of “handover to wrong cell” cases on the NR (NR A C in Annex A.13)
towards the cell with which the UE attempts to re-establish the radio link connection (see 36.300 [12]). It is
up to the eNodeB to decide whether or not the HO parameters of this NR are problematic in the “handover to
wrong cell” case.
f) EUtranRelation
h) EPS
b) CC.
e) HO.IntraFreqOutAtt.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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 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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 40 ETSI TS 132 425 V16.5.0 (2020-11)
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
b) CC.
e) HO.InterFreqMeasGapOutAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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 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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 41 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC.
e) HO.InterFreqNoMeasGapOutAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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 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
b) CC.
e) HO.DrxOutAtt
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 42 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC.
c) Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source)
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
b) CC.
e) HO.NoDrxOutAtt.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC.
c) Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source)
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 43 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS
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
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.OutRNOutAtt.Cause
where Cause identifies the cause for handover
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 44 ETSI TS 132 425 V16.5.0 (2020-11)
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
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 executions of outgoing
handovers to the cells outside the RN. 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.InterRNOutSucc.Cause
where Cause identifies the cause for handover.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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.
e) HO.SrcCellQual.RSRP
HO.SrcCellQual.RSRQ
f) EUtranRelation
h) EPS
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 45 ETSI TS 132 425 V16.5.0 (2020-11)
e) HO.TrgtCellQual.RSRP
HO.TrgtCellQual.RSRQ
f) EUtranRelation
h) EPS
b) CC.
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.IartOutAtt.Cause
where Cause identifies the cause for handover
f) EUtranCellFDD
EUtranCellTDD
GSMRelation
UTRANRelation
CDMA2000Relation
h) EPS
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
events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
All IRAT handovers to the neighbouring cells in non-eUTRAN are measured.
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 46 ETSI TS 132 425 V16.5.0 (2020-11)
e) HO.IartOutSucc.Cause
where Cause indicating the cause for handover.
f) EUtranCellFDD
EUtranCellTDD
GSMRelation
UTRANRelation
CDMA2000Relation
h) EPS
b) CC
c) The measurement is obtained by accumulating the number of outgoing unnecessary handovers to anther RAT
from E-UTRAN according to the definitions in TS 36.300 [12] and TS 36.413[9].
e) HO.IratOutUnnecessaryFromEutran
f) GSMRelation
UTRANRelation
CDMA2000Relation
h) EPS
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 kbit/s. The number of measurements
is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 47 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) One usage of this measurement is to support the KPI "E-UTRAN data Energy Efficiency" defined in [13].
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 kbit/s. The number of measurements
is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) One usage of this measurement is to support the KPI "E-UTRAN data Energy Efficiency" defined in [13].
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.
e) DRB.PdcpSduBitrateDlMax
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 48 ETSI TS 132 425 V16.5.0 (2020-11)
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.
e) DRB.PdcpSduBitrateUlMax
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC.
c) 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.
e) SRB.PdcpSduBitrateDl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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.
e) SRB.PdcpSduBitrateUl
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 49 ETSI TS 132 425 V16.5.0 (2020-11)
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11]. Separate counters are
maintained for each QCI.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11]. Separate counters are
maintained for each QCI.
d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a
possible sum value identified by the .sum suffix.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 50 ETSI TS 132 425 V16.5.0 (2020-11)
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314[11]. Separate counters are
maintained for each QCI.
d) Each measurement is an integer value. The number of measurements is eaqul to the number of QCIs plus a
possible sum value identified by the .sum suffix.
DRB.UEActive.QCI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI
d) An integer value.
DRB.UEActive
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) DER (n=1)
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 51 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11]. Separate counters are
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11]. Separate counters are
maintained for each QCI. In case only a subset of per QCI measurements is supported, a loss rate subcounter
calculated across all QCIs will be provided first.
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 52 ETSI TS 132 425 V16.5.0 (2020-11)
DRB. PdcpSduAirLossRateDlRN.QCI, which indicates the DL PDCP SDU air interface loss rate between the
E-UTRAN and RN.
where QCI identifies the target E-RAB level quality of service class.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11]. Separate counters are
maintained for each QCI. In case only a subset of per QCI measurements is supported, a loss rate subcounter
calculated across all QCIs will be provided first.
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.QCII, which indicates the UL PDCP SDU loss
rate between the eNodeB (or RN) and UE
DRB.PdcpSduLossRateUlRN.QCI, which indicates the UL PDCP SDU loss rate between the E-UTRAN and RN.
where QCI identifies the target E-RAB level quality of service class.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
LatTime
LatSample
LatTime is obtained by accumulating the time T for E-RABs
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).
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 53 ETSI TS 132 425 V16.5.0 (2020-11)
d) Each measurement is an integer value representing the time in ms. The number of measurements is equal to the
number of QCIs.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Integrity KPI “E-UTRAN IP Latency” defined in [13]
4.4.6.1 IP Throughput in DL
a) This measurement provides IP throughput in downlink. For an eNodeB serving one or more RNs, packets
transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or
RN) and UEs are counted. The measurement is also applicable to RN.
b) DER(N=1)
c) This measurement is obtained according to the following formula based on the “ThpVolDl” and “ThpTimeDl”
defined for the “Scheduled IP Throughput in DL” in 3GPP TS 36.314 [11] for each QCI.
ThpVolDl
If ThpTimeDl > 0, UEs
x1000 [kbits / s ]
UEs ThpTimeDl
UEs
If
UEs
ThpTimeDl = 0, 0 [kbits / s ]
d) Each measurement is a real value representing the throughput in kbit/s. The number of measurements is equal to
the number of QCIs.
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. For an eNodeB serving one or more RNs, packets
transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or
RN) and UEs are counted. The measurement is also applicable to RN
b) DER(N=1)
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 54 ETSI TS 132 425 V16.5.0 (2020-11)
c) This measurement is obtained according to the following formula based on the “ThpVolUl” and “ThpTimeUl”
defined for the “Scheduled IP Throughput inUL” in 3GPP TS 36.314 [11] for each QCI.
ThpVolUl
If ThpTimeUl > 0, UEs
x1000 [kbits / s ]
UEs ThpTimeUl
UEs
If
UEs
ThpTimeUl = 0, 0 [kbits / s ]
d) Each measurement is a real value representing the volume in kbit. The number of measurements is equal to the
number of QCIs.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Integrity KPI “E-UTRAN IP Throughput” defined in [13].
b) DER(n=1)
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11] clause 4.1.6 as sum of
ThpVolDl. Separate counters are maintained for each QCI.
d) Each measurement is a real value representing volume of a data burst in kbit. The number of measurements is
equal to the number of QCIs.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support the Integrity KPI "E-UTRAN IP Throughput" defined in [13].
b) DER(n=1).
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11] clause 4.1.6 as sum of
ThpVolUl. Separate counters are maintained for each QCI.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 55 ETSI TS 132 425 V16.5.0 (2020-11)
d) Each measurement is a real value representing volume of a data burst in kbit. The number of measurements is
equal to the number of QCIs.
f) EUtranCellFDD
EUtranCellTDD
h) EPS.
i) This measurement is to support the Integrity KPI "E-UTRAN IP Throughput" defined in [13].
b) DER(n=1).
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11] clause 4.1.6 as sum of
ThpTimeDl. Separate counters are maintained for each QCI.
d) Each measurement is a real value representing active transmission time of a data burst in ms. The number of
measurements is equal to the number of QCIs.
f) EUtranCellFDD
EUtranCellTDD
h) EPS.
i) This measurement is to support the Integrity KPI "E-UTRAN IP Throughput" defined in [13].
b) DER(n=1)
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11] clause 4.1.6 as sum of
ThpTimeUl. Separate counters are maintained for each QCI.
d) Each measurement is a real value representing active transmission time of a data burst in ms. The number of
measurements is equal to the number of QCIs.
f) EUtranCellFDD
EUtranCellTDD
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 56 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS.
i) This measurement is to support the Integrity KPI "E-UTRAN IP Throughput" defined in [13].
b) CC
c) Each measurement sample is obtained according to the definition in TS 36.314 [11] clause 4.1.11.1. Depending
on the value of the sample, the proper bin of the counter is increased. The number of samples during one
measurement period is provided by the operator.
d) A set of integers, each representing the (integer) number of samples with a DL UE IP throughput in the range
represented by that bin.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
c) Each measurement sample is obtained according to the definition in TS 36.314 [11] clause 4.1.11.2. Depending
on the value of the sample, the proper bin of the counter is increased. The number of samples during one
measurement period is provided by the operator.
d) A set of integers, each representing the (integer) number of samples with a UL UE IP throughput in the range
represented by that bin.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 57 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC
c) This measurement is obtained by counting the number of bits entering the eNodeB/RN. The measurement is
performed at the PDCP SDU level. The measurement is performed per configured PLMN ID per configured DL
QoS profile criteria. (See 3GPP TS 36.314, clause 4.1.9).
d) Each measurement is an integer value representing the number of bits measured in Mbits. The number of
measurements is equal to the number of PLMNs multiplied by the number of QoS profiles.
[Total no. of measurement instances] x [no. of filter values for all measurements] (DL and UL) ≤ 200.
Example: A measurement with filter PLMN=2, QCImax=4, QCImin=2, ARPmax=10, ARPmin=1 and GBR=3
results in the measurement name: DRB.PdcpSduVolumeDl_Plmn2Qci2-4Arp1-10Gbr3.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) Can be used by MOP (see TS 32.130 [22]) for cross-operator accounting in shared networks.
b) CC
c) This measurement is obtained by counting the number of bits entering the eNodeB/RN. The measurement is
performed at the PDCP SDU level. The measurement is performed per configured PLMN ID per configured UL
QoS profile criteria. (See 3GPP TS 36.314, clause 4.1.9).
d) Each measurement is an integer value representing the number of bits measured in Mbits. The number of
measurements is equal to the number of PLMNs multiplied by the number of QoS profiles.
[Total no. of measurement instances] x [no. of filter values for all measurements] (DL and UL) ≤ 200.
Example: A measurement with filter PLMN=2, QCImax=4, QCImin=2, ARPmax=10, ARPmin=1 and GBR=3
results in the measurement name: DRB.PdcpSduVolumeUl_Plmn2Qci2-4Arp1-10Gbr3.
f) EUtranCellFDD
EUtranCellTDD
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 58 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS
i) Can be used by MOP (see TS 32.130 [22]) for cross-operator accounting in shared networks.
b) CC
c) This measurement is obtained by summing up the pre-defined sampling intervals during which the requested IP
throughput cannot be achieved in the cell and reporting accumulated value at the end of measurement period.
The IP throughput defined in TS 36.314 is used to evaluate time period during which the QoS is not satisfied by
comparing the IP throughput with the guaranteed bit rate of the GBR services. The measurement period and
number of samples during one measurement period are provided by the operator.
f) EUtranCellFDD
EUtranCellTDD
h) EPS.
i)
In case the duration interval provided with this measurement is followed with the on restricting the UEs for
network access to the cell policy executed via ACB as mentioned in A.5 then this measurement provides
“Time period in Active ACB triggered via requested QoS cannot be achieved”.
The measurement can be executed with grouping of couple of QCIs to a common monitoring to distinguish
between voice and data services.
The IP throughput measurements is used as a reference on how to evaluate the quality of provided
services to end user in observed cell. They shall be obtained directly in the eNB as internal
measurements during each sampling period.
4.4.8.2 Time Period the Requested latency of GBR services Cannot be Achieved in
the Cell
a) This measurement provides time period the requested latency cannot be achieved in the cell. The measurement is
split into sub-counters per QoS class level (QCI). Concerning operator specific QCIs their definition is vendor
specific.
b) CC
c) This measurement is obtained by summing up the pre-defined sampling intervals during which the requested
latency cannot be achieved in the cell and reporting accumulated value at the end of measurement period. The
latency defined in TS 36.314 is used to evaluate time period during which the QoS is not satisfied by comparing
the latency with the packet delay budget of the GBR services. The measurement period and number of samples
during one measurement period are provided by the operator.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 59 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS.
i)
In case the duration interval provided with this measurement is followed with the on restricting the UEs for
network access to the cell policy executed via ACB as mentioned in A.5 then this measurement provides
“Time period in Active ACB triggered via requested QoS cannot be achieved”.
The measurement can be executed with grouping of couple of QCIs to a common monitoring to distinguish
between voice and data services.
The latency measurements is used as a reference on how to evaluate the quality of provided services to
end user in observed cell. They shall be obtained directly in the eNB as internal measurements
during each sampling period.
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11]. Separate counters are
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 60 ETSI TS 132 425 V16.5.0 (2020-11)
(including transmissions to/from RNs and UEs directly connected to the eNodeB) and for RN traffic. The
measurement is also applicable to RNs.
b) SI
c) This measurement is obtained according to the definition in 3GPP TS 36.314 [11]. Separate counters are
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) SI
f) EUtranCellFDD
EUtranCellTDD
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 61 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS
b) Gauge
e) RRU.RachPreambleDedMean
RRU.RachPreambleAMean
RRU.RachPreambleBMean
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 62 ETSI TS 132 425 V16.5.0 (2020-11)
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
f) EUtranCellFDD
EUtranCellTDD
h) EPS
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
b) CC
c) When UEInformationResponse message ([8] clause 6.2.1) continaing rachReport-r9 IE is received the
measurement is incremented by one.
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 63 ETSI TS 132 425 V16.5.0 (2020-11)
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
b) DER (n=1)
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
measurements is supported, a sum subcounter will be provided first.
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) This measurement is to support KPI “E-UTRAN Cell Availability” defined in [13].
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 64 ETSI TS 132 425 V16.5.0 (2020-11)
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
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
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 65 ETSI TS 132 425 V16.5.0 (2020-11)
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
b) SI
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
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 66 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS
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
b) CC
c) Each measurement sample is obtained according to the definition in TS 36.314[11] clause 4.1.10.1. Depending
on the value of the sample, the proper bin of the counter is increased. The number of samples during one
measurement period is provided by the operator.
d) A set of integers. Each representing the (integer) number of samples with a DL total PRB percentage usage in
the range represented by that bin.
e) RRU.PrbTotDlDist.BinX, which indicates the distribution of DL PRB Usage for all traffic.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) The distribution information is a key input to network capacity planning and load balancing.
b) CC
c) Each measurememt sample is obtained according to the definition in TS 36.314 [11] clause 4.1.10.1. Depending
on the value of the sample, the proper bin of the counter is increased. The number of samples during one
measurement period is provided by the operator.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 67 ETSI TS 132 425 V16.5.0 (2020-11)
d) A set of integers, each representing the (integer) number of samples with a UL PRB percentage usage in the
range represented by that bin.
e) RRU.PrbTotUlDist.BinX, which indicates the distribution of UL PRB Usage for all traffic.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
i) The distribution information is a key input to network capacity planning and load balancing.
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].
b) CC
c) On receipt by the eNB of first message from MME which succeeds INITIAL UE MESSAGE message on an UE-
associated logical S1-connection (See 36.413 [9]).
e) S1SIG.ConnEstabSucc
f) EUtranCellFDD
EUtranCellTDD
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 68 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS
i) This measurement is to support the Accessibility KPI “E-RAB Accessibility” defined in [13]
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].
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
h) EPS
b) CC
e) PAG.ReceivedNbr
f) EUtranCellFDD
EUtranCellTDD
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 69 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS
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.
e) EQPT.MeanProcessorUsage.ProcessorID
where ProcessorID identifies the key processor of this equipment, the format of ProcessorID is vendor specific.
f) ManagedElement.
h) EPS.
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.
e) EQPT.PeakProcessorUsage.ProcessorID
where ProcessorID identifies the key processor of this equipment, the format of ProcessorID is vendor specific.
f) ManagedElement.
h) EPS.
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 70 ETSI TS 132 425 V16.5.0 (2020-11)
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 RAT’s coverage the UE comes from.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
4.10 RF Measurements
4.10.1 CQI Distribution
4.10.1.0 General
In CA, in case the CQI of SCell is reported to PCell via PUCCH, the CQI is counted to the reported SCell (but not to
the PCell).
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
h) EPS
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 71 ETSI TS 132 425 V16.5.0 (2020-11)
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
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
b) CC
c) On allocation of PUCCH resources in the Pcell for Scell scheduling in Carrier Aggregation.
e) DRB.PucchAllocNbrAtt.PUCCHFormat
where PUCCHFormat identifies the PUCCH format, which is either “format3” or “format1bwcs”.
f) EUtranCellFDD
EUtranCellTDD
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 72 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS
b) CC
e) DRB.PucchAllocNbrSucc.PUCCHFormat
where PUCCHFormat identifies the PUCCH format, which is either “format3” or “format1bwcs”.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
c) On the failure of a Scell scheduling due to lack of PUCCH resources in the PCell for Carrier Aggregation.
e) DRB.PucchAllocNbrFail.PUCCHFormat
where PUCCHFormat identifies the PUCCH format, which is either “format3” or “format1bwcs”.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 73 ETSI TS 132 425 V16.5.0 (2020-11)
4.12.1 Power
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – clauses 4.4.3.1,
4.4.3.4, Annex A.
h) EPS.
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – clauses 4.4.3.1,
4.4.3.4, Annex A.
h) EPS.
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – clauses 4.4.3.1,
4.4.3.4, Annex A.
h) EPS.
4.12.2 Energy
a) This measurement provides the energy consumed.
b) SI.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 74 ETSI TS 132 425 V16.5.0 (2020-11)
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – clauses 4.4.3.2,
4.4.3.4, Annex A.
h) EPS.
i) One usage of this measurement is to support the KPI "E-UTRAN data Energy Efficiency" defined in [13].
4.12.3 Temperature
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – clause 4.4.3.4,
Annex A.
h) EPS.
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – clause 4.4.3.4,
Annex A.
h) EPS.
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – clause 4.4.3.4,
Annex A.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 75 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS.
4.12.4 Voltage
a) This measurement provides the voltage.
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – Clauses 4.4.3.3,
4.4.3.4, Annex B.
h) EPS.
4.12.5 Current
a) This measurement provides the current.
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – Clauses 4.4.3.3,
4.4.3.4, Annex B.
h) EPS.
4.12.6 Humidity
a) This measurement provides the percentage of humidity.
b) SI.
c) This measurement is obtained according to the method defined in ETSI ES 202 336-12 [23] – clause 4.4.3.3,
Annex B.
h) EPS.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 76 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC.
c) On receipt of DL DATA DELIVERY STATUS frame by the eNB from WT indicating the downlink LWA
PDUs have been successfully transmitted over the Xw interface (see TS 36.465 [24]), the measurement is
incremented by 1 for each octet of the successfully transmitted downlink LWA PDUs.
e) LWI.LwaPduXwDlOctet
h) EPS.
b) SI.
c) This measurement is obtained by sampling at a pre-defined interval, the number of UEs associated with WLAN
on the Xw interface by the eNB and then taking the arithmetic mean.
d) A real value.
e) LWI.UeAssocWlanLwa.
h) EPS.
b) CC.
c) On receipt of DL DATA DELIVERY STATUS frame by the eNB from WT indicating the downlink LWA
PDUs have been successfully transmitted over the Xw interface (see TS 36.465 [24]) for a UE, the measurement
is incremented by 1 in case the UE has not been counted yet for this measurement in the collection period.
d) A real value.
e) LWI.UeWithDlLwaPDU.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 77 ETSI TS 132 425 V16.5.0 (2020-11)
h) EPS.
4.13.2.1 Number of attempted WLAN additions to the LWA WLAN mobility set
a) This measurement provides the number of attempted WLAN additions to the LWA WLAN mobility set.
b) CC
d) An integer value
e) LWI.LwaWlanAddAtt
f) WLANMobilitySet
h) EPS
4.13.2.2 Number of successful WLAN additions to the LWA WLAN mobility set
a) This measurement provides the number of successful WLAN additions to the LWA WLAN mobility set.
b) CC
d) An integer value
e) LWI.LwaWlanAddSucc
f) WLANMobilitySet
h) EPS
4.13.2.3 Number of attempted WLAN releases from the LWA WLAN mobility set
a) This measurement provides the number of attempted WLAN releases from the LWA WLAN mobility set.
b) CC
d) An integer value
e) LWI.LwaWlanRelAtt
f) WLANMobilitySet
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 78 ETSI TS 132 425 V16.5.0 (2020-11)
4.13.2.4 Number of successful WLAN releases from the LWA WLAN mobility set
a) This measurement provides the number of successful WLAN releases from the LWA WLAN mobility set.
b) CC
d) An integer value
e) LWI.LwaWlanRelSucc
f) WLANMobilitySet
h) EPS
b) CC
d) An integer value
e) LWI.LwaDrbAddAtt
f) WLANMobilitySet
h) EPS
b) CC
d) An integer value
e) LWI.LwaDrbAddSucc
f) WLANMobilitySet
h) EPS
b) CC
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 79 ETSI TS 132 425 V16.5.0 (2020-11)
d) An integer value
e) LWI.LteToLwaDrbReconfAtt
f) WLANMobilitySet
h) EPS
b) CC
d) An integer value
e) LWI.LteToLwaDrbReconfSucc
f) WLANMobilitySet
h) EPS
b) CC
d) An integer value
e) LWI.LwaDrbReconfAtt
f) WLANMobilitySet
h) EPS
b) CC
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 80 ETSI TS 132 425 V16.5.0 (2020-11)
d) An integer value
e) LWI.LwaDrbReconfSucc
f) WLANMobilitySet
h) EPS
b) CC
c) Transmission of the DL LWIPEP PDUs (see 3GPP TS 36.361 [25]) by the eNB.
e) LWI.LwipepPduDlOctet
f) ENBFunction
h) EPS
b) CC
c) Receipt of the UL LWIPEP PDUs (see 3GPP TS 36.361 [x]) by the eNB.
e) LWI.LwipepPduUlOctet
f) ENBFunction
h) EPS
b) CC
c) Transmission of DL LWIPEP PDU by the eNB for a UE which has not been counted for this measurement in the
collection period.
d) An integer value.
e) LWI.UeWithDlLwipepPDU
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 81 ETSI TS 132 425 V16.5.0 (2020-11)
f) ENBFunction
h) EPS
b) CC
c) Receipt of UL LWIPEP PDU by the eNB for a UE which has not been counted for this measurement in the
collection period.
d) An integer value.
e) LWI.UeWithUlLwipepPDU
f) ENBFunction
h) EPS
4.14.2.1 Number of attempted WLAN additions to the LWIP WLAN mobility set
a) This measurement provides the number of attempted WLAN additions to the LWIP WLAN mobility set.
b) CC
d) An integer value
e) LWI.LwipWlanAddAtt
f) WLANMobilitySet
h) EPS
4.14.2.2 Number of successful WLAN additions to the LWIP WLAN mobility set
a) This measurement provides the number of successful WLAN additions to the LWIP WLAN mobility set.
b) CC
d) An integer value
e) LWI.LwipWlanAddSucc
f) WLANMobilitySet
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 82 ETSI TS 132 425 V16.5.0 (2020-11)
4.14.2.3 Number of attempted WLAN releases from the LWIP WLAN mobility set
a) This measurement provides the number of attempted WLAN releases from the LWIP WLAN mobility set.
b) CC
d) An integer value
e) LWI.LwipWlanRelAtt
f) WLANMobilitySet
h) EPS
4.14.2.4 Number of successful WLAN releases from the LWIP WLAN mobility set
a) This measurement provides the number of successful WLAN releases from the LWIP WLAN mobility set.
b) CC
d) An integer value
e) LWI.LwipWlanRelSucc
f) WLANMobilitySet
h) EPS
b) CC
d) An integer value
e) LWI.LwipDrbAddAtt
f) WLANMobilitySet
h) EPS
b) CC
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 83 ETSI TS 132 425 V16.5.0 (2020-11)
d) An integer value
e) LWI.LwipDrbAddSucc
f) WLANMobilitySet
h) EPS
b) CC
d) An integer value
e) LWI.LteToLwipDrbReconfAtt
f) WLANMobilitySet
h) EPS
b) CC
d) An integer value
e) LWI.LteToLwipDrbReconfSucc
f) WLANMobilitySet
h) EPS
b) CC
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 84 ETSI TS 132 425 V16.5.0 (2020-11)
d) An integer value
e) LWI.LwipDrbReconfAtt
f) WLANMobilitySet
h) EPS
b) CC
d) An integer value
e) LWI.LwipDrbReconfSucc
f) WLANMobilitySet
h) EPS
b) CC
c) On receipt of WLANConnectionStatusReport message (see TS 36.331 [18]) by the eNB. Each received message
increments the relevant subcounter per WLAN status by 1.
e) LWI.WlanConnectionReport.succAsso
LWI.WlanConnectionReport.failRL
LWI.WlanConnectionReport.failUnavail
LWI.WlanConnectionReport.failTimeout
LWI.WlanConnectionReport.suspended
LWI.WlanConnectionReport.resumed
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 85 ETSI TS 132 425 V16.5.0 (2020-11)
f) WLANMobilitySet
h) EPS
b) CC
c) On transmission by the MN of an SgNB Addition Request message to SN, the request not include SN terminated
bearers. SGNB Addition Trigger Indication (TS 36.423[10]) excludes SN change, inter-eNB HO, intra-eNB HO.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 86 ETSI TS 132 425 V16.5.0 (2020-11)
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 Additions failed to setup at Secondary Node Additions
without SN terminated bearers case. In case only a subset of per cause measurements is supported, a sum
subcounter will be provided first. SGNB Addition Trigger Indication (TS 36.423[10]) excludes SN change, inter-
eNB HO, intra-eNB HO.
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
c) On transmission by the MN of an SgNB Addition Request message to SN,the request include SN terminated
bearers. SGNB Addition Trigger Indication (TS 36.423[10]) excludes SN change, inter-eNB HO, intra-eNB HO.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 87 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC
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.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
c) On receipt of an E-RAB modification confirmation message by the MN from MME (after MN sends SgNB
reconfiguration complete message) when path switch is needed. SGNB Addition Trigger Indication (TS
36.423[10]) excludes SN change, inter-eNB HO, intra-eNB HO.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 88 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
c) On transmission by the MN of an SgNB Addition Request message to SN,the request include SN terminated
bearers. Each requested E-RAB in the message (IE E-RABs To Be Added List TS 36.423 [10]) is added to the
relevant measurement per bearer type. The sum of all supported per bearer type measurements shall equal the
total number of E-RABs atttempted to setup. In case only a subset of per bearer measurements is supported, a
sum subcounter will be provided first. SGNB Addition Trigger Indication (TS 36.423[10]) excludes SN change,
inter-eNB HO, intra-eNB HO.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
c) On transmission by the MN of an SGNB ADDITION REQUEST ACKNOWLEDGE message (TS 36.423 [10])
to SN when Secondary Node Additions with SN terminated bearers. Each successful ERAB added to the
relevant measurement per bearer type. The sum of all supported per bearer type measurements shall equal the
total number of E-RABs successfully setup. In case only a subset of per bearer type measurements is supported,
a sum subcounter will be provided first. SGNB Addition Trigger Indication (TS 36.423[10]) excludes SN
change, inter-eNB HO, intra-eNB HO.
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 89 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
f) EUtranCellFDD
EUtranCellTDD
h) EPS
b) CC
c) On receipt of an E-RAB modification confirmation message by the MN from MME (after MN sends SgNB
reconfiguration complete message) when path switch is needed. SGNB Addition Trigger Indication (TS
36.423[10]) excludes SN change, inter-eNB HO, intra-eNB HO.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 90 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellFDD
EUtranCellTDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 91 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC
f) DeNBCapability
h) EPS
b) CC
f) DeNBCapability
h) EPS
b) CC
c) Receipt by the eNodeB from the UE of MeasurementReport message indicating a periodical UE measurement
report where IE MeasResults field includes rsrpResult. The event triggered MeasurementReport messages are
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 92 ETSI TS 132 425 V16.5.0 (2020-11)
excluded.This measurement shall be increased for each reported value RSRP_LEV (See in 3GPP TS 36.331
[18]). For every one or two or 17 or 20 RSRP_LEV(s) a separate measurement is defined. (See in 3GPP TS
36.133 [19])
f) EUtranCellTDD
EUtranCellFDD
h) EPS
b) CC
c) Receipt by the eNodeB from the UE of MeasurementReport message indicating a periodical UE measurement
report where IE MeasResults field includes rsrqResult. The event triggered MeasurementReport messages are
excluded. This measurement shall be increased for each reported value RSRQ_LEV (See in 3GPP TS 36.331
[18]). For every one or two RSRQ_LEV(s) a separate measurement is defined. (See in 3GPP TS 36.133 [19])
f) EUtranCellTDD
EUtranCellFDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 93 ETSI TS 132 425 V16.5.0 (2020-11)
b) CC
c) Receipt by the eNodeB from the UE of Power Headroom Report message indicating a periodical UE
measurement POWER_HEADROOM report. This measurement shall be increased for each reported value
POWER_HEADROOM (See in 3GPP TS 36.321 [16]). For every one POWER_HEADROOM (s) a separate
measurement is defined. (See in 3GPP TS 36.133 [19]).
f) EUtranCellTDD
EUtranCellFDD
h) EPS
b) CC
c) Receipt by the eNodeB from the UE of MeasurementReport message indicating a periodical UE measurement
report where IE MeasResults field includes ue-RxTxTimeDiffResult. The event triggered MeasurementReport
messages are excluded. This measurement shall be increased for each reported value RX-
TX_TIME_DIFFERENCE (See in 3GPP TS 36.331 [18]). For every 5 or 20 or 100 or 524 RX-
TX_TIME_DIFFERENCEs a separate measurement is defined. (See in 3GPP TS 36.133 [19])
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 94 ETSI TS 132 425 V16.5.0 (2020-11)
f) EUtranCellTDD
EUtranCellFDD
h) EPS
b) CC
f) EUtranCellTDD, EUtranCellFDD
h) EPS
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 95 ETSI TS 132 425 V16.5.0 (2020-11)
Annex A (informative):
Use cases for performance measurements defintion
A.0 Introduction
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 eNodeB apply to following scenarios
If the specific constraint is present, which one of the above scenarios the subject use case applies to, is following the
constraint.
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 operator’s 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.
- 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;
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 96 ETSI TS 132 425 V16.5.0 (2020-11)
- 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).
However, the abnormal release of the E-RAB has potential scenario where, regardless of receiving the UE Context
Release Command with the cause related to abnormal release, the end user does not perceive it as abnormal. This
scenario is explicitly related to VoLTE calls, for other services it is not possible to determine the reason behind
the cause code. It is typical to encounter such scenario, a so called "double UE Context", when Radio Link
Failure occurs during an ongoing VoLTE call and RRC Connection Re-establishment attempt fails on target or
other cell. If then the UE does a new RRC Connection the QCI1 bearer is set-up during Initial Context Setup in
the target or other cell. However, when MME receives that service request with the Initial UE message through
the target or other cell, it realize that it already has the same UE Context but from the source cell (it has not been
released yet). In such case, MME sends UE Context Release Command to the source cell. As the QCI1 E-RAB
has been successfully setup in the target or other cell, the QCI1 E-RAB release in the source cell may not be
perceived as a drop (abnormal release) by the end user, as the service has been sustained with some interruption
time, and cannot be considered as a drop in the QCI1 E-RAB flow Drop Ratio.
From a retainability measurement aspect, E-RABs do not need to be released because they are inactive, they can be kept
to give fast access when new data arrives.
To define (from an E-RAB release measurement point of view) if an E-RAB is considered active or not, the E-RABs
can be divided into two groups:
a) Continuous flow, E-RABs that are always considered active, i.e. independent of if there is ongoing traffic or not
at the moment. Examples: VoIP sessions, Real-time sessions, Live streaming sessions.
b) Bursty flow, E-RABs that are only considered active when there is data in UL/DL buffer.
Example: Web sessions.
How to decide for a particular QCI if the E-RAB is of type bursty flow or continuous flow is outside the scope of this
document.
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 procedure (See 3GPP TS 36.413[9]) , UE Context Release procedure
(See 3GPP TS 36.413[9] and 3GPP TS 36.423[10]) procedure, Reset procedure(See 3GPP TS 36.413[9]) either
initiated by eNodeB or MM, Path Switch procedure (See 3GPP TS 36.413[9]) and Intra-eNB HO procedure (See 3GPP
TS 36.331[8])E.
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.
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 97 ETSI TS 132 425 V16.5.0 (2020-11)
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.
Continuous Network Supervision: Supervision of overall - outgoing Intra RAT HO Success Rate (cell) *1
handover performance. It is essential in network operations - outgoing Inter RAT HO Success Rate (cell) *1
to follow the success rate of various handover. Low - outgoing Inter System HO Success Rate (cell) *1 *3
handover success rate will impact user experience, therefore - outgoing Intra Frequency HO Success Rate (cell) *1
it is important to define measurements to follow handover - outgoing Inter Frequency HO Success Rate (cell) *1
success rate. - 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
*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 happens between E-UTRAN and 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.
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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 98 ETSI TS 132 425 V16.5.0 (2020-11)
Troubleshooting: Reason for failed handover. To go for - outgoing HO Failure Distribution Rate (cell+neighbourcell)
further detailed analysis for handover failure it is important to - HO Path Switching Failure Distribution Rate (cell or Interface)
know what the reason for handover failure was, or whether - HO Failure Rate DRX / Non DRX (cell) *5
the handover was assisted by measurement gaps or was - Inter frequency HO Failure Rate Meas gap assisted / not assisted
with DRX. (cell) *5
Network Planning: Traffic flow analysis - outgoing Intra RAT HO Success Rate (neighbour cell)
or - outgoing Inter RAT HO Success Rate (cell)
- outgoing Inter System HO Success Rate (cell)
Network Planning: Handover traffic optimization
- RRM policies
- Scheduling
- congestion control
- admission control
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.In case the rectification is not leading to desired QoS some other policies (ACB, rejected RRC
connection setup) based on restricting the UEs for network access to the cell may be applied
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 99 ETSI TS 132 425 V16.5.0 (2020-11)
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.
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 the eNodeB serving one or more RN, the packet delay includes both the internal processing delay at eNB)
and UE/RN as well as the packet transferring delay on the radio link. As RN UE’s packets need to be transferred via
between E-UTRAN snfRN while packets for UEs directly connected to eNB need to pass through only Uu interface,
packet delay optimization mechanism may be different for RN UEs and eNB UEs. Therefore it is beneficial to have
measurements on packet delay separately for packets transmitted between the eNodeB and UEs and for packets
transmitted between the E-UTRAN and RNs.
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.
The PRB usage distribution could provide operators the load distribution information of the network during the
collecting time period.According to the PRB usage distribution information, the scenarios where a cell may experience
high load in certain short times (e.g. in a second) and recover to normal very quickly can be recognized.The PRB usage
distribution is a useful measure for operator to be aware of whether a cell has ever experienced high load or not in the
monitoring duration. This distribution information could also help in the root cause analysis in case when the
application problems are caused by load bursts. The distribution information could show the median usage and the peak
usage. The median usage is within the range of the bin that got the highest number of samples and the peak usage is
within the range of the “highest” bin that got >0 samples. The distribution information is a key input to network
capacity planning and load balancing.
For a RN that requires subframe configuration, the RN can only be scheduled by the eNodeB within subframes
configured for RN, while macro UE can be scheduled in any subframe. Therefore, in certain scenario it may be
possible that the PRB usage is different for the subframe configured for the RN and for any other subframe. For
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 100 ETSI TS 132 425 V16.5.0 (2020-11)
example, in case there are many RNs in the network and only a few UEs connected directly to the eNodeB, it may
happen that the PRB usage in the subframe configured for RN is quite high, while the subframes used for UEs is low.
Therefore, it is beneficial to measure the PRB usage separately for RN and the total PRB usage. The total PRB usage
includes the PRB usage for RN traffic and UE traffic, while the RN PRB usage includes only PRB usage for RN traffic.
In case or RN deployment the communicstion between the E-UTRAN and RN is going through the air interface. It is
possible that the radio conditions are bad, which can lead also to high packet loss rate, which can contribute also
whether the packet loss aspect of the quality of service is met or not. Therefore it is beneficial to have separate packet
loss rate measurement for RN traffic and for the traffic connected directly to the eNodeB.
In case or RN deployment the communicstion between the E-UTRAN and RN is going through the air interface. It is
possible that the radio conditions are bad, which can lead also to high packet loss rate, which can contribute also
whether the packet loss aspect of the quality of service is met or not. Therefore it is beneficial to have separate packet
loss rate measurement for RN traffic and for the traffic connected directly to the eNodeB.
RACH Usage
The RACH plays a vital role in the following procedures:
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 101 ETSI TS 132 425 V16.5.0 (2020-11)
- 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.
An overload situation in the cell can be related also to other conditions leading to insufficient QoS. That means UE is
allowed for network access but later one due to some other reason either the session is dropped, or there is big PDCP
SDU delay or low IP scheduled throughput, etc. leading to degradation of quality of provided services. Let’s consider a
UE which is having an GBR service ongoing. The radio conditions in the cell are bad and thus despite there is no RLF
detected for the UE because the QoS characteristics for the UE like throughput and delay cannot be achieved the UE is
either abnormally released or quality of provided services has significantly degraded. Another example could be for the
UE having an nonGBR service ongoing and RLF has been detected which leads to abnormal UE release or significant
degradation of quality of provided services as well. In both cases despite the cell serving the UEs did its best from the
point of view the most robust MCSs and thus maximum possible resources used, maximum UE transmit power and
using other possible techniques (like HO, redirection….) it was not possible to keep the UEs active in the cell with
guaranteed QoS simply because the cell did not have the needed capacity (features) to do so.
For the operator it is therefore very important to have measurements to monitor duration the requested quality of service
cannot be achieved.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 102 ETSI TS 132 425 V16.5.0 (2020-11)
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.
The necessary measurements to identify and anylse the interference situation as input for optimisation tasks has to be
defined.
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, RLC’s 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).
HARQ Performance if viewed at MCS (Modulation Coded Scheme) can help in monitoring the MCS Performance also.
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
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 103 ETSI TS 132 425 V16.5.0 (2020-11)
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 site’s 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.
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.
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.
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”,
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 104 ETSI TS 132 425 V16.5.0 (2020-11)
“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 “handover to wrong cell” case, an RLF occurs shortly after a successful handover from a source cell (cell A in Figure
A.13-1) to a target cell (cell B in Figure A.13-1) or a HOF occurs during the handover procedure; the UE attempts to re-
establish the radio link connection in a cell (Cell C in Figure A.13-1) other than the source cell and the target cell. (See
36.300 [12]).
For the “handover to wrong cell” case (A B C) above-mentioned, the handover parameters on Neighbour Relation
A B, Neighbour Relation A C or both may be problematic and need to be corrected. So the performance
measurements for both Neighbour Relation A B and Neighbour Relation A C are needed for problem detection.
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.
- 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.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 105 ETSI TS 132 425 V16.5.0 (2020-11)
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
RAT’s 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 E-
UTRAN cells in the same TA, operators may take actions to rectify it if needed.
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.
The unsuccessful setup of E-RABs with different QCIs could lead to different user experience, thus the E-RAB setup
for incoming HOs needs to be monitored per QCI.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 106 ETSI TS 132 425 V16.5.0 (2020-11)
According to optimization experience and the transmission bandwidth requirement reduced, several granularity of this
measurement is proposed. For -120 dBm ≤ RSRP < -115dBm, the granularity is 5dB, for -115 dBm ≤ RSRP < -
80dBm, the granularity is 1dB, and for -80 dBm ≤ RSRP < -60dBm, the granularity is 2dB.
In order to reduce the transmission bandwidth requirement, according to network optimization experience, 1dB
granularity of measurement is enough.
According to network optimization experience, the granularity of measurement 1dB is enough to do trouble shooting of
coverage hole and evaluation of power control.
For TDD mode, propagation distance of 1Ts is nearly 9.77m. According to optimization experience, several granularity
of this measurement is proposed. Minimize granularity of 10Ts is enough to analyze distance distribution for near base
station, namely UE Rx–Tx time difference is less than 200Ts. For UE Rx–Tx time difference is larger than 200Ts and
less than 1000Ts, the corresponding propagation distance is from 1953m to 9766m, the granularity of 40Ts is enough to
do trouble shooting of extending coverage. For UE Rx–Tx time difference is larger than 1000Ts and less than 2000Ts.
the granularity is 200Ts. And for UE Rx–Tx time difference is larger than 2000Ts and less than 4096Ts, the granularity
is 1048Ts.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 107 ETSI TS 132 425 V16.5.0 (2020-11)
- Over-dimensioned PUCCH causes high overhead and results in reduced UL throughput is (in general UL is not
used efficiently);
- Under-dimensioned PUCCH will result in reduced DL throughput (if no PUCCH format 1bCS or format 3
ACK/NACK resource is available, PDSCH cannot be allocated by the PDCCH for the SCell(s) and the UE
cannot be allocated resources on its SCell(s)).
Thus, the SCell scheduling success/blocking rate on PUCCH needs to be monitored for evaluation of control channel
usage in CA. When needed OAM can also provide the guidance or take action to the eNB to optimize the PUCCH
dimension for CA.
In the past operators had only option to set the inactivity timer commonly for all kind of services. This may lead to the
situation that for the services from the first group UE had to spend ineffectively longer time in RRC Connected state
which had negative impact on UE’s battery live. On the other hand for the services from the second group the inactivity
timer setting can be insufficient which then may lead to significant increase of the UE movements from RRC Idle to
RRC Connected state.
Operators shall therefore accurately tune the inactivity timers to avoid some bottlenecks in the RRC Connection setup
on one side and prolongation of the UE’s battery life on the second side. Especially regarding the services where long
inactivity timer applies operator needs to have an option to estimate how intended prolongation of the long inactivity
timer is going to decrease the number of RRC Connection Setups on one side and prolong the UEs’ state in RRC
Connected state on second side, using the "Number of successful RRC connection setups in relation to the time between
successful RRC connection setup and last RRC connection release".
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 108 ETSI TS 132 425 V16.5.0 (2020-11)
during the monitoring period is satisfactory. the user experience may not be always satisfactory because the UE IP
throughput may significantly vary during the monitoring period. It would be useful for operators to know the
distribution information on the UE IP throughput. This distribution information could also help in the root cause
analysis in case when the application problems are caused by load bursts. The UE IP throughput distribution
information could show the mean throughput and the peak throughput. The median throughput is within the range of the
bin that got the highest number of samples and the peak throughput is within the range of the “highest” bin that got >0
samples. With the information of UE IP throughput distribution, operator may consider to optimize the network if
needed.
As the active UEs reflect UEs have data to transmit or receive , the ratio of the number of active UEs to the number of
the RRC connected UEs can be established, which can be used to monitor the the cell. In addition, compared with the
number of RRC connected users, the number of active UEs is a more effective measurement to reflect the control plane
capacity of wireless network.
The Xw-U interface is used to deliver LWA PDUs (user data) between eNB and WT for a UE. The user data
For LWA, the S1-U terminates in the eNB and, if Xw-U user data bearers are associated with E-RABs for which the
LWA bearer option is configured, the user plane data is transferred from eNB to WT using the Xw-U interface.
The E-UTRAN capacity needs to be determined with the user data transmitted over Xw interface into account, including
the volume of the user data transmitted or received over Xw interface for non-collocated LWA, the number of UEs
associated with WLAN and the number of UEs actually with user data transferred over Xw interface.
The performance of these RRC procedures needs to be monitored for LWA (both collocated LWA and non-collocated
LWA).
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 109 ETSI TS 132 425 V16.5.0 (2020-11)
A single IPSec tunnel is used per UE for all the data bearers that are configured to send and/ or receive data over
WLAN. Each data bearer may be configured so that traffic for that bearer can be routed over the IPsec tunnel in only
downlink, only uplink, or both uplink and downlink over WLAN.
The operator needs to know the performance regarding user data transmission via WLAN for LWIP.
When the connection with WLAN is failed, the UE configured with bearer(s) on WLAN becomes unable to establish or
continue LTE and WLAN integration operation.
So it is necessary to monitor the WLAN connection status reports to evaluate the performance of the LTE and WLAN
integration.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 110 ETSI TS 132 425 V16.5.0 (2020-11)
RRC connection usage per UE multi-RAT capability related measurement is helpful for operators to identify how
efficient they utilize their deployed radio access technology layers and perform corrective actions when needed.
- 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).
From a retainability measurement aspect, E-RABs do not need to be released because they are inactive, they can be kept
to give fast access when new data arrives.
To define (from an E-RAB release measurement point of view) if an E-RAB is considered active or not, the E-RABs
can be divided into two groups:
a) Continuous flow, E-RABs that are always considered active, i.e. independent of if there is ongoing traffic or not
at the moment. Examples: VoIP sessions, Real-time sessions, Live streaming sessions.
b) Bursty flow, E-RABs that are only considered active when there is data in UL/DL buffer.
Example: Web sessions.
How to decide for a particular QCI if the E-RAB is of type bursty flow or continuous flow is outside the scope of this
document.
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 procedure (See 3GPP TS 36.413[9]) , UE Context Release procedure
(See 3GPP TS 36.413[9] and 3GPP TS 36.423[10]) procedure, Reset procedure(See 3GPP TS 36.413[9]) either
initiated by eNodeB or MM, Path Switch procedure (See 3GPP TS 36.413[9]) and Intra-eNB HO procedure (See 3GPP
TS 36.331[8])E.
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.
From quality point of view the E-RAB or UE Context drop ratio of the same values in two different cells may be
perceived differently by the end user especially for VoIP services, depending on the duration of the dropped call in
comparison to intended call duration when call would not be dropped. For example, having the E-RAB drop ratio of
90% in two cells may be perceived differently by the end user, where in the first cell there was a dropped call which
lasted for 99% of intended call duration and in the other cell it lasted only 40%. In the first case, the end user with high
probability may not follow up with an additional call request, while in the second it may be the opposite as the main
goal of the conversation has not been achieved yet.
Therefore, as an extended monitoring especially for VoIP sessions observation of the "Distribution of Normally
Released Call (QCI1 E-RAB) Duration" and "Distribution of Abnormally Released Call (QCI1 E-RAB) Duration" is
recommended.
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 111 ETSI TS 132 425 V16.5.0 (2020-11)
Annex B (informative):
Change history
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 112 ETSI TS 132 425 V16.5.0 (2020-11)
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Cat Old New
Mar 2009 SP-43 SP-090143 -- -- Presentation to SA for information and -- 1.0.0 8.0.0
approval
Jun 2009 SP-44 SP-090408 002 -- Add missing E-UTRAN measurement for F 8.0.0 8.1.0
paging discards at the eNodeB - Align with
36.304 and 32.426
Jun 2009 SP-44 SP-090290 001 -- Addition of eNodeB processor usage B 8.1.0 9.0.0
related measurements
Sep 2009 SP-45 SP-090542 004 -- Correction on the IP latency and additional A 9.0.0 9.1.0
SAE Bearers setup measurements
Sep 2009 SP-45 SP-090542 006 -- Alignment of PRB usage related A 9.0.0 9.1.0
measurements with 36.314
Sep 2009 SP-45 SP-090627 007 -- Add SAE Bearer number related B 9.0.0 9.1.0
measurements
Mar 2010 SP-47 SP-100035 010 -- Add RRC connection release as a PM F 9.1.0 9.2.0
counter
Mar 2010 SP-47 SP-100035 011 -- Introduction of handover failure PM F 9.1.0 9.2.0
counters for handover optimisation
Mar 2010 SP-47 SP-100035 012 -- Add a PM counter of RRC connection F 9.1.0 9.2.0
establishments per failure cause
Mar 2010 SP-47 SP-100036 008 -- Incorrect section numbering D 9.2.0 10.0.0
Mar 2010 SP-47 SP-100036 009 -- Add TB related measurements B 9.2.0 10.0.0
Jun 2010 SP-48 SP-100264 013 -- Editorial changes to clause References D 10.0.0 10.1.0
Jun 2010 SP-48 SP-100259 -- Correct L3 messages in measurement A 10.0.0 10.1.0
022 definitions
Jun 2010 SP-48 SP-100412 018 -- Add IP Throughput measurements A 10.0.0 10.1.0
Jun 2010 SP-48 SP-100262 -- Missing Measurement related to common A 10.0.0 10.1.0
015 LAs to support faster CS fallback in EPS
Jun 2010 SP-48 SP-100262 -- Add the missing reference of causes in A 10.0.0 10.1.0
019 HO measurements
Sep 2010 SP-49 SP-100488 -- Correction of intra-RAT HO 10.1.0 10.2.0
023 measurements A
Sep 2010 SP-49 SP-100489 -- Modification of E-RAB release related 10.1.0 10.2.0
024 measurements C
Sep 2010 SP-49 SP-100489 -- Addition of measurements for pagings 10.1.0 10.2.0
025 received B
Sep 2010 SP-49 SP-100493 -- Modifying RRC establishment failure and 10.1.0 10.2.0
Cellunavailability measurements due to
026 Energy Saving C
Dec 2010 SP-50 SP-100878 030 1 Correcting L3 messages and cleanup A 10.2.0 10.3.0
Mar 2011 SP-51 Apply the RRC connection setup related 10.3.0 10.4.0
SP-110095 031 1 measurements to RN B
Mar 2011 SP-51 Apply the RRC connection 10.3.0 10.4.0
reestablishment related measurements to
SP-110095 032 2 RN B
Mar 2011 SP-51 Apply the E-RAB setup related 10.3.0 10.4.0
SP-110095 033 1 measurements to RN B
Mar 2011 SP-51 Apply the abnormal E-RAB release related 10.3.0 10.4.0
SP-110095 034 2 measurements to RN B
Mar 2011 SP-51 Addition of HO related measurements to 10.3.0 10.4.0
SP-110095 035 1 RN B
Mar 2011 SP-51 Apply the eNB measurements to DeNB as 10.3.0 10.4.0
SP-110095 036 1 well C
Mar 2011 SP-51 SP-110095 044 1 Adding measurements on power utilization B 10.3.0 10.4.0
Mar 2011 SP-51 Change counter for RACH usage from 10.3.0 10.4.0
SP-110093 048 - 'Cumulative Counter' to 'Gauge' A
Mar 2011 SP-51 Add measurements for maximum PRB 10.3.0 10.4.0
SP-110095 053 1 usage B
Mar 2011 SP-51 SP-110095 054 1 Add measurements for radio coverage B 10.3.0 10.4.0
Mar 2011 SP-51 Add measurements for radio coverage, 10.3.0 10.4.0
SP-110095 055 9 handover triggering, RACH performance B
Mar 2011 SP-51 Add RRC connection setup and UE 10.3.0 10.4.0
context release related measurements of
SP-110095 058 1 RN B
Mar 2011 SP-51 Add E-RAB release and modification 10.3.0 10.4.0
SP-110095 059 1 related measurements of RN B
Mar 2011 SP-51 Add inter-RAT HO related measurements 10.3.0 10.4.0
SP-110095 060 - of RN B
Mar 2011 SP-51 Add cell level radio bearer QoS related 10.3.0 10.4.0
SP-110095 061 - measurements of RN B
Mar 2011 SP-51 Add Radio resource utilization related 10.3.0 10.4.0
SP-110095 062 - measurements of RN B
Mar 2011 SP-51 SP-110095 063 - Add paging related measurements of RN B 10.3.0 10.4.0
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 113 ETSI TS 132 425 V16.5.0 (2020-11)
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 114 ETSI TS 132 425 V16.5.0 (2020-11)
Change history
Date Meeting TDoc CR Rev Cat Subject/Comment New version
2016-12 SA#74 SP-160856 0163 1 B Add measurements for cross-operator 14.1.0
accounting based on data volume and QoS”
2018-03 SA#79 SP-180060 0168 - B Introduction of power, energy and environment 15.0.0
related measurements and related use case
description.
2018-06 SA#80 SP-180429 0169 2 B Add use case and definition for distribution of 15.1.0
scheduled IP Throughput
2018-06 SA#80 SP-180429 0170 2 B Add Use Case and definition for distribution of 15.1.0
Total PRB Usage for UL/DL
2018-06 SA#81 SP-180831 0172 2 B Add use case and definitions for average 16.0.0
number of active UEs and average number of
active UEs per QCI
2018-12 SA#82 SP-181049 0173 3 B Add measurements related to user data 16.1.0
transmission on Xw interface for non-
collocated LWA
2018-12 SA#82 SP-181049 0175 1 B Add measurements related to RRC 16.1.0
procedures for LWA
2018-12 SA#82 SP-181039 0177 1 A Update measurements supporting energy 16.1.0
efficiency KPI
2019-03 SA#83 SP-190124 0178 1 B Add measurements related to user data 16.2.0
transmission via WLAN for LWIP
2019-03 SA#83 SP-190124 0179 1 B Add measurements related to RRC 16.2.0
procedures for LWIP
2019-03 SA#83 SP-190124 0183 - B Add measurements related to WLAN 16.2.0
connection status report
2019-06 SA#84 SP-190371 0184 1 B Add measurements related to Secondary 16.3.0
Node Addition for E-UTRA-NR Dual
Connectivity
2019-06 SA#84 SP-190371 0188 1 B Add measurement on RRC connection 16.3.0
usage per UE multi RAT capability
2019-06 SA#84 SP-190386 0190 1 A Correction on kbits abbreviation 16.3.0
2019-09 SA#85 SP-190747 0197 1 B Add measurement related to QoS of cell 16.4.0
2019-09 SA#85 SP-190747 0198 1 B Add measurements related to extended 16.4.0
monitoring of the retainability for the QCI1
services
2019-12 SA#86 SP-191149 0199 2 B Add new Use case related to QCI1 E-RAB 16.5.0
establishment via Initial Context Setup into
A2
ETSI
3GPP TS 32.425 version 16.5.0 Release 16 115 ETSI TS 132 425 V16.5.0 (2020-11)
History
Document history
V16.5.0 November 2020 Publication
ETSI