ETSI TS 132 426 V9.6.0 (2019-10)

LTE; Telecommunication management; Performance Management (PM); Performance measurements Evolved Packet Core (EPC) network (3GPP TS 32.426 version 9.6.0 Release 9)

RTS/TSGS-0532426v960

General Information

• Status: Published
• Publication Date: 06-Oct-2019
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Completion
• Completion Date: 07-Oct-2019

Standards Content (Sample)

TECHNICAL SPECIFICATION
LTE;
Telecommunication management;
Performance Management (PM);
Performance measurements Evolved Packet Core (EPC)
network
(3GPP TS 32.426 version 9.6.0 Release 9)

3GPP TS 32.426 version 9.6.0 Release 9 1 ETSI TS 132 426 V9.6.0 (2019-10)

Reference
RTS/TSGS-0532426v960
Keywords
LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
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 2019.
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.426 version 9.6.0 Release 9 2 ETSI TS 132 426 V9.6.0 (2019-10)
Intellectual Property Rights
Essential patents
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.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 3 ETSI TS 132 426 V9.6.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
1 Scope . 9
2 References . 9
3 Measurement family and abbreviations. 10
3.1 Measurement family . 10
3.2 Abbreviations . 10
4 Measurements related to the MME . 10
4.1 Mobility Management . 10
4.1.1 EPS attach procedures . 10
4.1.1.1 Attempted EPS attach procedures . 11
4.1.1.2 Successful EPS attach procedures . 11
4.1.1.3 Failed EPS attach procedures . 11
4.1.2 UE-initiated EPS Detach procedure . 12
4.1.2.1 Attempted EPS detach procedures by UE . 12
4.1.2.2 Successful EPS detach procedures by UE . 12
4.1.3 MME-initiated EPS Detach procedure . 12
4.1.3.1 Attempted EPS detach procedures by MME . 12
4.1.3.2 Successful EPS detach procedures by MME . 13
4.1.4 HSS-initiated EPS Detach procedure . 13
4.1.4.1 Attempted EPS detach procedures by HSS . 13
4.1.4.2 Successful EPS detach procedures by HSS . 13
4.1.5 Tracking area update procedure with Serving GW change . 14
4.1.5.1 Attempted tracking area update procedure with Serving GW change . 14
4.1.5.2 Successful tracking area update procedure with Serving GW change . 14
4.1.5.3 Failed tracking area update procedure with Serving GW change . 14
4.1.6 Tracking area update procedure without Serving GW change. 15
4.1.6.1 Attempted tracking area update procedure without Serving GW change . 15
4.1.6.2 Successful tracking area update procedure without Serving GW change . 15
4.1.6.3 Failed tracking area update procedure without Serving GW change . 16
4.1.9 EPS paging procedures . 16
4.1.9.1 Attempted EPS paging procedures . 16
4.1.9.2 Successful EPS paging procedures . 17
4.1.9.3 Failed EPS paging procedures. 17
4.1.10 MME control of overload related measurements for EPC . 17
4.1.10.1 Attempted Overload Start procedure . 17
4.1.10.2 Attempted Overload Stop procedure . 18
4.1.11 EMM-Registered subscribers. 18
4.1.11.1 Mean number of EMM-Registered subscribers . 18
4.1.11.2 Maximum number of EMM-Registered subscribers . 18
4.1.12 Handover related measurements . 19
4.1.12.1 Inter RAT handover . 19
4.1.12.1.1 Incoming inter RAT handover . 19
4.1.12.1.1.1 Attempted incoming inter RAT handover. 19
4.1.12.1.1.2 Successful incoming inter RAT handover . 19
4.1.12.1.2 Outgoing inter RAT handover . 19
4.1.12.1.2.1 Attempted outgoing inter RAT handover . 19
4.1.12.1.2.2 Successful outgoing inter RAT handover . 20
4.1.13 Routeing area update with MME interaction . 20
4.1.13.1 Attempted routeing area update with MME interaction . 20
4.1.13.2 Successful routeing area update with MME interaction and without S-GW change . 21
4.1.13.3 Failed routeing area update with MME interaction and without S-GW change . 21
4.1.13.4 Successful routeing area update with MME interaction and with S-GW change . 21
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 4 ETSI TS 132 426 V9.6.0 (2019-10)
4.1.13.5 Failed routeing area update with MME interaction and with S-GW change. 22
4.2 Session Management . 22
4.2.1 Number of dedicated EPS bearers in active mode (Mean) . 22
4.2.2 Number of dedicated EPS bearers in active mode (Maximum) . 22
4.2.3 Dedicated bearer set-up time by MME (Mean) . 23
4.2.4 MME initiated dedicated bearer activation . 23
4.2.4.1 Attempted dedicated bearer activation procedures by MME . 23
4.2.4.2 Successful dedicated bearer activation procedures by MME . 23
4.2.4.3 Failed dedicated bearer activation procedures by MME . 24
4.2.5 MME initiated dedicated bearer deactivation . 24
4.2.5.1 Attempted dedicated bearer deactivation procedures by MME . 24
4.2.5.2 Successful dedicated bearer deactivation procedures by MME . 24
4.2.6. MME initiated EPS bearer modification . 25
4.2.6.1 Attempted EPS bearer modification procedures by MME . 25
4.2.6.2 Successful EPS bearer modification procedures by MME . 25
4.2.6.3 Failed EPS bearer modification procedures by MME . 25
4.2.7 Total EPS Service Request . 26
4.2.7.1 Total Attempted EPS Service Request procedures. . 26
4.2.7.2 Total Successful EPS Service Request procedures. . 26
4.2.7.3 Total failed EPS Service Request procedures. . 26
4.3 Subscriber management for MME . 27
4.3.1 Attempted insert subscriber data requests received from a HSS . 27
4.3.2 Attempted delete subscriber data requests received from a HSS . 27
4.4 S1-MME data volume related measurements . 27
4.4.1 Number of incoming IP data packets on the S1-MME interface from eNodeB to MME . 27
4.4.2 Number of outgoing IP data packets on the S1-MME interface from MME to eNodeB . 28
4.4.3 Number of octets of incoming IP data packets on the S1-MME interface from eNodeB to MME . 28
4.4.4 Number of octets of outgoing IP data packets on the S1-MME interface from MME to eNodeB . 28
4.5 Equipment resource . 29
4.5.1 MME Processor usage . 29
4.5.1.1 Mean Processor Usage . 29
4.5.1.2 Peak processor usage. 29
5 Measurements related to the PDN-GW for a GTP based S5/S8 . 30
5.1 Session Management . 30
5.1.1 PDN-GW initiated Dedicated Bearer Creation . 30
5.1.1.1 Attempted number of PDN-GW initiated Dedicated Bearer Creation . 30
5.1.1.2 Successful number of PDN-GW initiated Dedicated Bearer Creation . 30
5.1.1.3 Failed number of PDN-GW initiated Dedicated Bearer Creation . 30
5.1.2 PDN-GW initiated Dedicated Bearer Deletion . 31
5.1.2.1 Attempted number of PDN-GW initiated Dedicated Bearer Deletion . 31
5.1.2.2 Successful number of PDN-GW initiated Dedicated Bearer Deletion . 31
5.1.2.3 Failed number of PDN-GW initiated Dedicated Bearer Deletion . 31
5.1.3 PDN-GW initiated Dedicated Bearer Modification with QoS update procedure . 32
5.1.3.1 Attempted number of PDN-GW initiated Dedicated Bearer Modification with QoS update . 32
5.1.3.2 Successful PDN-GW initiated Dedicated Bearer Modification with QoS update . 32
5.1.3.3 Failed PDN-GW initiated Dedicated Bearer Modification with QoS update . 33
5.1.4 PDN-GW initiated Dedicated Bearer Modification without QoS update procedure . 33
5.1.4.1 Attempted number of PDN-GW initiated Dedicated Bearer Modification without QoS update . 33
5.1.4.2 Successful number of PDN-GW initiated Dedicated Bearer Modification without QoS update . 33
5.1.4.3 Failed number of PDN-GW initiated Dedicated Bearer Modification without QoS update . 34
5.1.5 Active EPS Bearers related measurements for EPC . 34
5.1.5.1 Mean Number of Active EPS Bearers . 34
5.1.5.2 Max Number of Active EPS Bearers . 34
5.1.6 UE requested bearer resource modification related measurements for EPC . 35
5.1.6.1 Attempted UE requested bearer resource modification procedure . 35
5.1.6.2 Successful UE requested bearer resource modification procedure . 35
5.1.6.3 Failed UE requested bearer resource modification procedure . 35
5.1.7 PDN Connections related measurements for EPC . 36
5.1.7.1 Mean Number of PDN Connections, per APN . 36
5.1.7.2 Max Number of PDN Connections, per APN . 36
5.2 SGi related measurements . 37
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 5 ETSI TS 132 426 V9.6.0 (2019-10)
5.2.1 SGi incoming link usage . 37
5.2.2 SGi outgoing link usage . 37
6 Measurements related to the S-GW . 38
6.1 GTP related measurements . 38
6.1.1 GTP S5/S8 . 38
6.1.1.1 Number of outgoing GTP data packets on the S5/S8 interface, from S-GW to PDN-GW . 38
6.1.1.2 Number of incoming GTP data packets on the S5/S8 interface, from PDN-GW to S-GW . 38
6.1.1.3 Number of octets of outgoing GTP data packets on the S5/S8 interface, from S-GW to PDN-GW . 38
6.1.1.4 Number of octets of incoming GTP data packets on the S5/S8 interface, from PDN-GW to S-
GW . 39
6.1.1.5 Number of outgoing GTP signalling packets on the S5/S8 interface, from S-GW to PDN-GW . 39
6.1.1.6 Number of incoming GTP signalling packets on the S5/S8 interface, from PDN-GW to S-GW . 39
6.1.1.7 Number of octets of outgoing GTP signalling packets on the S5/S8 interface, from S-GW to
PDN-GW . 40
6.1.1.8 Number of octets of incoming GTP signalling packets on the S5/S8 interface, from PDN-GW to
S-GW . 40
7 Measurements related to the SGW . 41
7.1 S1-U data volume related measurements . 41
7.1.1 Number of outgoing GTP data packets on the S1-U interface, from S-GW to eNodeB . 41
7.1.1.2 Number of incoming GTP data packets on the S1-U interface, from eNodeB to S-GW . 41
7.1.1.3 Number of octets of outgoing GTP data packets on the S1-U interface, from S-GW to eNodeB . 41
7.1.1.4 Number of octets of incoming GTP data packets on the S1-U interface, from eNodeB to S-GW . 42
Annex A (informative): Use case for measurements . 43
A.1 Use case for mobility management related measurements . 43
A.2 Use case for detach related measurements . 43
A.3 Use case for tracking and routeing area update related measurements . 43
A.4 Use case for session related measurements . 44
A.5 Use case for EPS paging procedures . 44
A.6 Use case of PDN-GW initiated Dedicated Bearer Management related measurements for EPC . 44
A.7 Use case of PDN-GW initiated Dedicated Bearer Management related measurements for EPC . 44
A.8 Use case of PDN-GW initiated Dedicated Bearer Management related measurements for EPC . 45
A.9 Use case of PDN-GW initiated Dedicated Bearer Management related measurements for EPC . 45
A.10 Use case of GTP S5/S8 data volume related measurements . 45
A.11 Use case of S1-U data volume related measurements . 45
A.12 Use case of SGi related measurements for EPC . 45
A.13 Use case of subscriber management for MME related measurements . 46
A.14 Use case of S1-MME data volume related measurements . 46
A.15 Use case of Active EPS Bearers related measurements for EPC . 46
A.16 Use case of MME control of overload related measurements for EPC . 46
A.17 Use case of UE requested bearer resource modification related measurements for EPC . 47
A.18 Use case for registered subscribers related measurements for EPC . 47
A.19 Use case of PDN Connections related measurements for EPC . 47
A.20 Use case of MME processor usage . 47
A.21 Use case for EPS Service Request related Measurements . 47
Annex B (informative): Change history . 49
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 6 ETSI TS 132 426 V9.6.0 (2019-10)
History . 50

ETSI
3GPP TS 32.426 version 9.6.0 Release 9 7 ETSI TS 132 426 V9.6.0 (2019-10)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification
Group Services and System Aspects; Telecommunication management; as identified below:
32.401 Performance Management (PM); Concept and requirements
52.402 Performance Management (PM); Performance measurements - GSM
32.404 Performance Management (PM); Performance measurements - Definitions and template
32.405 Performance Management (PM); Performance measurements Universal Terrestrial Radio Access
Network (UTRAN)
32.406 Performance Management (PM); Performance measurements Core Network (CN) Packet Switched
(PS) domain
32.407 Performance Management (PM); Performance measurements Core Network (CN) Circuit
Switched (CS) domain
32.408 Performance Management (PM); Performance measurements Teleservice
32.409 Performance Management (PM); Performance measurements IP Multimedia Subsystem (IMS)
32.425 Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio
Access Network (E-UTRAN)
32.426 Performance Management (PM); Performance measurements Evolved Packet Core network
(EPC)
The present document is part of a set of specifications, which describe the requirements and information model
necessary for the standardised Operation, Administration and Maintenance (OA&M) of a multi-vendor LTE SAE-
system.
During the lifetime of a LTE SAE network, 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 [2].
Many of the activities involved in the daily operation and future network planning of a LTE SAE network 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.
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 8 ETSI TS 132 426 V9.6.0 (2019-10)
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.426 version 9.6.0 Release 9 9 ETSI TS 132 426 V9.6.0 (2019-10)
1 Scope
The present document describes the measurements for EPC and combined EPC/UMTS/GSM.
TS 32.401 [1] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of an EPC network and
combined EPC/UMTS/GSM network. Only measurement types that are specific to EPC or combined EPC/UMTS/GSM
networks are defined within the present documents.
Vendor specific measurement types used in EPC and combined EPC/UMTS/GSM networks are not covered. Instead,
these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as IP) as described by "external" standards bodies (e.g. IETF)
shall only be referenced within this specification, wherever there is a need identified for the existence of such a
reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a
multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. MME related measurements);
- Header 2: Measurement function;
- 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 specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept
and requirements".
[2] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept
and high-level requirements".
[3] 3GPP TS 24.301: " Technical Specification Group Core Network and Terminals; Non-Access-
Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[4] 3GPP TS 29.274: "Evolved General Packet Radio Service (GPRS); Tunnelling Protocol for
Control plane (GTPv2-C); Stage 3".
[5] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access (Release 8)".
[6] 3GPP TS 29.274: " Tunnelling Protocol for Control plane (GTPv2-C)".
[7] 3GPP TS 29.281: "GPRS Tunnelling Protocol User Plane (GTPv1-U)".
[8] 3GPP TS 36.414: "Evolved Universal Terrestrial Access Network (E-UTRAN); S1 data transport".
[9] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node
(SGSN) related interfaces based on Diameter protocol".
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 10 ETSI TS 132 426 V9.6.0 (2019-10)
[10] 3GPP TS 23.203: "Policy and charging control architecture".
[11] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1
Application Protocol (S1AP)".
[12] 3GPP TS 36.412: "Evolved Universal Terrestrial Access Network (E-UTRAN); S1 signaling
transport".
[13] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[14] IETF RFC 5136: "Defining Network Capacity".
3 Measurement family and abbreviations
3.1 Measurement family
The measurement names defined in the present document are all beginning with a prefix containing the measurement
family name. This family name identifies all measurements which relate to a given functionality and it may be used for
measurement administration (see TS 32.401 [1]).
The list of families currently used in the present document is as follows:
- EQPT (measurements related to Equipment)
- MM (measurements related to Mobility Management)
- GTP (measurements related to GTP Management)
- IP (measurements related to IP Management)
- IRATHO (measurements related to Inter-Radio Access Technology Handover)
- SM (measurements related to Session Management)
- SUB (measurements related to Subscriber Management)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
EQPT Equipment
EPC Evolved Packet Core
GTP GPRS Tunnelling Protocol
MME Mobility Management Entity
UMTS Universal Mobile Telecommunications System
UTRAN Universal Terrestrial Radio Access Network
Subscr Subscriber
Tau Tracking area update
Rau Routeing area update
4 Measurements related to the MME
4.1 Mobility Management
4.1.1 EPS attach procedures
The three measurement types defined in this clause are subject to the "2 out of 3 approach".
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 11 ETSI TS 132 426 V9.6.0 (2019-10)
4.1.1.1 Attempted EPS attach procedures
a) This measurement provides the number of attempted EPS attach procedures initiated within this MME area.
b) CC.
c) Receipt of "ATTACH REQUEST" message with "Attach type" information element indicating "EPS attach"
from the MS (TS 24.301 [3]).
Editor notes: Attach type message needs to be changed according to TS24.301.
d) A single integer value per measurement type defined in e).
e) MM.EpsAttachAtt.E
Note: E indicates EPS.
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code).
g) Valid for packet switching.
h) EPS.
4.1.1.2 Successful EPS attach procedures
a) This measurement provides the number of successfully performed EPS attach procedures within this MME area.
b) CC.
c) Transmission of a "ATTACH ACCEPT" message to the MS, in response to a "ATTACH REQUEST" message
with the "Attach type" information element indicating "EPS attach". If the "ATTACH ACCEPT" message is
caused by a retransmission, this will not cause the counter to be increased. (TS 24.301 [3]).

Editor notes: Attach type message needs to be changed according to TS24.301.
d) A single integer value per measurement type defined in e).
e) MM.EpsAttachSucc.E
Note: E indicates EPS.
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code).
g) Valid for packet switching.
h) EPS.
4.1.1.3 Failed EPS attach procedures
a) This measurement provides the number of failed EPS attach procedures. The measurement is split into
subcounters per the reject cause.
b) CC
c) Transmission by the MME of the ATTACH REJECT message to the MS, in response to a "ATTACH
REQUEST" message with the "Attach type" information element indicating "EPS attach", the relevant
measurement is incremented according to the reject cause. Possible reject causes are defined within TS 24.301
[3].
The sum of all supported per cause measurements shall be equal to the total number of failed EPS attach
procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided
first.
Editor notes: Attach type message needs to be changed according to TS24.301.
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 12 ETSI TS 132 426 V9.6.0 (2019-10)
d) Each measurement (as defined in e) 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) MM.EpsAttachFail.Cause.E
where Cause identifies the reject cause, E indicates EPS.
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code).
g) Valid for packet switching
h) EPS.
4.1.2 UE-initiated EPS Detach procedure
4.1.2.1 Attempted EPS detach procedures by UE
a) This measurement provides the number of attempted EPS detach procedures initiated by UE within this MME
area.
b) CC.
c) Receipt of "DETACH REQUEST" message with "detach type" information element indicating "EPS detach"
from the UE (TS 24.301 [3]).
Editor notes: Attach type message needs to be changed according to TS24.301.
d) A single integer value.
e) MM.EpsDetachUeAtt
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code)
g) Valid for packet switching.
h) EPS.
4.1.2.2 Successful EPS detach procedures by UE
a) This measurement provides the number of successful EPS detach procedures initiated by UE within this MME
area.
b) CC
c) Transmission of "DETACH ACCEPT" message from the MME (TS 24.301 [3]).
d) A single integer value.
e) MM.EpsDetachUeSucc
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code)
g) Valid for packet switching.
h) EPS
4.1.3 MME-initiated EPS Detach procedure
4.1.3.1 Attempted EPS detach procedures by MME
a) This measurement provides the number of attempted EPS detach procedures initiated by MME.
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 13 ETSI TS 132 426 V9.6.0 (2019-10)
b) CC
c) Transmission of "DETACH REQUEST" message by UE from the MME, not including repeat (TS 24.301 [3]).
d) A single integer value.
e) MM.EpsDetachMMEAtt
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code)
g) Valid for packet switching.
h) EPS
4.1.3.2 Successful EPS detach procedures by MME
a) This measurement provides the number of successful EPS detach procedures initiated by MME.
b) CC
c) Receipt of "DETACH ACCEPT" message by MME from the UE (TS 24.301 [3]).
d) A single integer value.
e) MM.EpsDetachMMESucc
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code)
g) Valid for packet switching.
h) EPS
4.1.4 HSS-initiated EPS Detach procedure
4.1.4.1 Attempted EPS detach procedures by HSS
a) This measurement provides the number of attempted EPS detach procedures initiated by HSS.
b) CC
c) Receipt of "CANCEL LOCATION" message by MME from HSS with "cancel type" information element
indicating “delete user”, not including repeat (TS 24.301 [3]).
d) A single integer value.
e) MM.EpsDetachHssAtt
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code)
g) Valid for packet switching.
h) EPS
4.1.4.2 Successful EPS detach procedures by HSS
a) This measurement provides the number of successful EPS detach procedures initiated by HSS.
b) CC
c) Transmission of "CANCEL LOCATION ACK" message by HSS from the MME (TS 24.301 [3]).
d) A single integer value.
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 14 ETSI TS 132 426 V9.6.0 (2019-10)
e) MM.EpsDetachHssSucc
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code)
g) Valid for packet switching.
h) EPS
4.1.5 Tracking area update procedure with Serving GW change
The three measurement types defined in this clause are subject to the "2 out of 3 approach".
4.1.5.1 Attempted tracking area update procedure with Serving GW change
a) This measurement provides the number of attempted tracking area update procedures with Serving GW change
initiated within this MME area.
b) CC.
c) Receipt of "TRACKING AREA UPDATE REQUEST" message from a MS with "Last visited registered TAI"
information element indicating to the MME that it wishes to be served by a new Serving GW (different to the old
Serving GW (TS 24.301 [3])).
d) A single integer value per measurement type defined in e).
e) MM.TauInterSgwAtt
a) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code).
b) Valid for packet switching.
c) EPS.
4.1.5.2 Successful tracking area update procedure with Serving GW change
a) This measurement provides the number of successfully performed tracking area update procedures with Serving
GW change within this MME area.
b) CC.
c) Transmission of a "TRACKING AREA UPDATE ACCEPT" message to the MS, in response to a "TRACKING
AREA UPDATE REQUEST" message in which the "Last visited registered TAI" information element indicated
to the MME that it wishes to be served by a new Serving GW (different to the old Serving GW). If the
"TRACKING AREA UPDATE ACCEPT" message is caused by a retransmission, this will not cause the counter
to be increased. (TS 24.301 [3]).
d) A single integer value per measurement type defined in e).
e) MM.TauInterSgwSucc
f) TA, specified by a concatenation of the MCC (Mobile Country Code), MNC (Mobile Network Code), TAC
(Tracking Area Code).
g) Valid for packet switching.
h) EPS.
4.1.5.3 Failed tracking area update procedure with Serving GW change
a) This measurement provides the number of failed tracking area update procedure with Serving GW change. The
measurement is split into subcounters per the reject cause.
ETSI
3GPP TS 32.426 version 9.6.0 Release 9 15 ETSI TS 132 426 V9.6.0 (2019-10)
b) CC
c) Transmission of a “TRACKING AREA UPDATE REJECT” message to the MS, in response to a " TRACKING
AREA UPDATE REQUEST" message with in which the "Last visited registered TAI" information element
indicated to the MME that it
...