ETSI TS 132 422 V15.3.0 (2020-03)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Subscriber and equipment trace;
Trace control and configuration management
(3GPP TS 32.422 version 15.3.0 Release 15)

3GPP TS 32.422 version 15.3.0 Release 15 1 ETSI TS 132 422 V15.3.0 (2020-03)

Reference
RTS/TSGS-0532422vf30
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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 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.422 version 15.3.0 Release 15 2 ETSI TS 132 422 V15.3.0 (2020-03)
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.422 version 15.3.0 Release 15 3 ETSI TS 132 422 V15.3.0 (2020-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 8
Introduction . 8
1 Scope . 9
2 References . 9
3 Definitions and abbreviations . 11
3.1 Definitions . 11
3.2 Abbreviations . 11
4 Trace/UE measurements activation and deactivation . 12
4.1 Trace Session activation / deactivation for Trace and MDT . 12
4.1.1 Management activation . 12
4.1.1.1 General . 12
4.1.1.2 UTRAN activation mechanisms . 13
4.1.1.2a UTRAN activation mechanisms for area based MDT data collections without IMSI/IMEI(SV)
selection . 14
4.1.1.3 PS Domain activation mechanisms . 17
4.1.1.4 CS Domain activation mechanisms . 18
4.1.1.5 IP Multimedia Subsystem activation mechanisms . 18
4.1.1.6 E-UTRAN activation mechanisms . 18
4.1.1.6a E-UTRAN activation mechanisms for area based MDT data collections without IMSI/IMEI(SV)
selection . 19
4.1.1.6b E-UTRAN activation mechanisms for area based Logged MBSFN MDT data collections without
IMSI/IMEI(SV) selection . 23
4.1.1.7 EPC Domain activation mechanisms . 26
4.1.1.8 5GC Domain activation mechanisms . 26
4.1.1.9 NG-RAN activation mechanisms . 27
4.1.2 Signalling activation . 27
4.1.2.1 General . 27
4.1.2.2 Intra PLMN signalling activation . 28
4.1.2.3 Inter PLMN Signalling Activation . 29
4.1.2.4 UTRAN activation mechanisms . 31
4.1.2.5 PS Domain activation mechanisms . 31
4.1.2.6 CS Domain activation mechanisms . 35
4.1.2.7 Void. 36
4.1.2.8 Tracing roaming subscribers . 36
4.1.2.9 Service Level Tracing for IMS activation mechanisms . 36
4.1.2.9.1 General . 36
4.1.2.9.2 Trace session activation for non-registered UE . 38
4.1.2.9.3 Trace session activation for a registered UE . 42
4.1.2.9.4 Trace session activation at the UE . 43
4.1.2.10 EPC activation mechanism . 44
4.1.2.10.1 UE attached to EPC via E-UTRAN . 44
4.1.2.10.2 UE attached to EPC via non-3GPP accesses with DSMIPv6 on S2c or PMIP on S2a/S2b . 47
4.1.2.10.3 UE attached to EPC via non-3GPP accesses with GTP on S2b interface . 48
4.1.2.10.4 Inter-RAT handover from E-UTRAN to UTRAN . 50
4.1.2.11 E-UTRAN activation mechanisms . 52
4.1.2.12 EPC and E-UTRAN Activation mechanism for MDT . 53
4.1.2.12.1 General . 53
4.1.2.12.2 Activation of MDT task before UE attaches to the network. 54
4.1.2.12.3 Activation of MDT task after UE attachment . 56
4.1.2.12.4 Handling of various scenarios during MDT activation . 57
ETSI
3GPP TS 32.422 version 15.3.0 Release 15 4 ETSI TS 132 422 V15.3.0 (2020-03)
4.1.2.12.5 Activation of Logged MBSFN MDT task before UE attaches to the network . 58
4.1.2.12.6 Activation of Logged MBSFN MDT task after UE attachment . 60
4.1.2.13 PS domain activation mechanism for MDT . 61
4.1.2.13.1 General . 61
4.1.2.13.2 Activation of MDT task before UE attaches to the network. 61
4.1.2.13.2a Activation of MDT task after UE attaches to the network . 63
4.1.2.13.3 Handling of various scenarios during MDT activation . 65
4.1.2.14 CS domain activation mechanism for MDT . 66
4.1.2.14.0 Activation of MDT task before UE attaches to the network. 66
4.1.2.14.1 MDT Error Handling . 69
4.1.2.15 5GC activation mechanism . 69
4.1.2.15.1 UE attached to 5GC via NG-RAN. 69
4.1.2.15.2 Inter-RAT handover between E-UTRAN and NG-RAN . 79
4.1.2.15.3 Non-3GPP access scenarios . 82
4.1.2.16 NG-RAN activation mechanisms . 87
4.1.3 Management deactivation . 89
4.1.3.1 UTRAN deactivation mechanisms . 89
4.1.3.2 PS Domain deactivation mechanisms . 89
4.1.3.3 CS Domain deactivation mechanisms . 89
4.1.3.4 IP Multimedia Subsystem deactivation mechanisms . 89
4.1.3.5 E-UTRAN deactivation mechanisms . 90
4.1.3.6 EPC Domain deactivation mechanisms . 91
4.1.3.7 E-UTRAN deactivation mechanisms for MDT . 91
4.1.3.8 Deactivation mechanisms at UE for MDT . 91
4.1.3.9 5GC Domain deactivation mechanisms . 91
4.1.3.10 NG-RAN deactivation mechanisms . 91
4.1.4 Signalling deactivation . 92
4.1.4.1 General . 92
4.1.4.2 UTRAN deactivation mechanisms . 92
4.1.4.3 PS Domain deactivation mechanisms . 95
4.1.4.4 CS Domain deactivation mechanisms . 95
4.1.4.5 Void. 95
4.1.4.6 Service Level Trace in IMS deactivation mechanisms . 95
4.1.4.6.1 General . 95
4.1.4.6.2 Trace session deactivation at an IMS NE . 96
4.1.4.6.2.1 Trace session deactivation propagated by EM . 96
4.1.4.6.2.2 Trace session deactivation following a Triggering event . 96
4.1.4.6.2.3 Trace session deactivation initiated directly by an EM . 96
4.1.4.6.3 Trace session deactivation at the UE . 96
4.1.4.7 EPC deactivation mechanisms . 97
4.1.4.8 E-UTRAN deactivation mechanisms . 100
4.1.4.9 EPC deactivation mechanisms for MDT . 100
4.1.4.10 Deactivation mechanisms at UE for MDT . 100
4.1.4.11 5GC deactivation mechanisms . 100
4.1.4.12 NG-RAN deactivation mechanisms . 102
4.1.5 MDT Trace selection conditions . 103
4.2 Trace Recording Session Start / Stop triggering for Trace and MDT . 104
4.2.1 General . 104
4.2.2 Starting a trace recording session - management based . 104
4.2.2.1 UTRAN starting mechanisms . 104
4.2.2.2 PS Domain starting mechanisms . 104
4.2.2.3 CS Domain starting mechanisms . 104
4.2.2.4 IP Multimedia Subsystem starting mechanisms . 105
4.2.2.5 E-UTRAN starting mechanism . 105
4.2.2.6 EPC Domain starting mechanisms . 107
4.2.2.7 E-UTRAN starting mechanisms for MDT . 107
4.2.2.8 Starting mechanisms at UE for MDT . 107
4.2.2.9 5GC Domain starting mechanisms . 107
4.2.2.10 NG-RAN starting mechanism . 108
4.2.3 Starting a trace recording session - signalling based . 110
4.2.3.1 UTRAN starting mechanisms . 110
4.2.3.2 PS Domain starting mechanisms . 113
ETSI
3GPP TS 32.422 version 15.3.0 Release 15 5 ETSI TS 132 422 V15.3.0 (2020-03)
4.2.3.3 CS Domain starting mechanisms . 114
4.2.3.4 Void. 116
4.2.3.5 Service level tracing for IMS starting mechanism . 116
4.2.3.5.1 General . 116
4.2.3.5.2 Starting mechanism at the UE . 118
4.2.3.5.3 Starting mechanism at the IMS NE . 119
4.2.3.5.4 Charging concepts for Service Level Tracing for IMS . 119
4.2.3.6 E-UTRAN starting mechanism . 119
4.2.3.7 EPC starting mechanisms . 120
4.2.3.8 EPC starting mechanisms for MDT . 121
4.2.3.9 E-UTRAN starting mechanisms for MDT . 121
4.2.3.10 Starting mechanisms at UE for MDT . 121
4.2.3.11 5GC starting mechanisms . 121
4.2.3.12 NG-RAN starting mechanism . 122
4.2.4 Stopping a trace recording session - management based . 123
4.2.4.1 UTRAN stopping mechanisms . 123
4.2.4.2 PS Domain stopping mechanisms . 123
4.2.4.3 CS Domain stopping mechanisms . 125
4.2.4.4 IP Multimedia Subsystem stopping mechanisms . 125
4.2.4.5 E-UTRAN stopping mechanisms . 125
4.2.4.6 EPC Domain stopping mechanisms . 126
4.2.4.7 E-UTRAN stopping mechanisms for MDT . 126
4.2.4.8 Stopping mechanisms at UE for MDT . 126
4.2.4.9 5GC Domain stopping mechanisms . 126
4.2.4.10 NG-RAN stopping mechanisms . 126
4.2.5 Stopping a trace recording session - signalling based . 127
4.2.5.1 UTRAN stopping mechanisms . 127
4.2.5.2 PS Domain stopping mechanisms . 127
4.2.5.3 CS Domain stopping mechanisms . 129
4.2.5.4 Void. 131
4.2.5.5 Service level tracing for IMS stopping mechanism . 131
4.2.5.5.1 General . 131
4.2.5.5.2 Stopping mechanism at the UE . 132
4.2.5.5.3 Stopping mechanism at the IMS NE . 132
4.2.5.6 Service level tracing Trace session deletion and trace retrieval . 132
4.2.5.7 E-UTRAN stopping mechanisms . 132
4.2.5.8 EPC Domain stopping mechanisms . 132
4.2.5.9 EPC stopping mechanisms for MDT . 133
4.2.5.10 E-UTRAN stopping mechanisms for MDT . 133
4.2.5.11 Stopping mechanisms at UE for MDT . 133
4.2.5.12 5GC Domain stopping mechanisms . 133
4.2.5.13 NG-RAN stopping mechanisms . 134
4.2.6 Void . 134
4.2.7 Void . 134
4.2.8 Void . 134
4.2.8.1 Void. 134
4.2.8.2 Void. 134
4.2.9 Void . 134
4.3 RLF reporting . 134
4.3.1 Trace session activation for RLF reporting . 134
4.3.2 Trace session deactivation for RLF reporting . 137
4.4 Handling of MDT Trace sessions at handover for Immediate MDT . 137
4.5 Handling of MDT Trace sessions at handover for Logged MDT and Logged MBSFN MDT . 139
4.6 User consent handling in MDT . 139
4.6.1 Signalling based MDT . 139
4.6.2 Area based MDT . 140
4.7 Anonymization of MDT data for area based MDT . 142
4.8 RCEF reporting . 142
4.8.1 Trace session activation for RCEF reporting . 142
4.8.2 Trace session deactivation for RCEF reporting . 144
5 Trace/UE measurement control and configuration parameters . 145
ETSI
3GPP TS 32.422 version 15.3.0 Release 15 6 ETSI TS 132 422 V15.3.0 (2020-03)
5.1 Triggering events (M) . 145
5.2 Service Level Tracing Start Triggering event (M) . 153
5.3 Trace Depth (M) . 153
5.4 List of NE types (M) . 154
5.5 List of interfaces (O) . 155
5.6 Trace Reference (M) . 158
5.7 Trace Recording Session Reference (M) . 158
5.8 Void . 158
5.9 IP Address of Trace Collection Entity (CM,CO) . 158
5.9a Job type (CM) . 159
5.9b PLMN Target (CM). 159
5.10 MDT specific configuration parameters (CM) . 159
5.10.1 Void . 159
5.10.2 Area Scope . 159
5.10.3 List of measurements . 160
5.10.4 Reporting Trigger . 161
5.10.5 Report Interval . 161
5.10.6 Report Amount . 162
5.10.7 Event Threshold for RSRP . 163
5.10.7a Event Threshold for RSRQ . 163
5.10.8 Logging Interval . 163
5.10.9 Logging Duration . 164
5.10.10 Void . 164
5.10.11 Trace Collection Entity Id . 164
5.10.12 Anonymization of MDT data . 164
5.10.13 Event Threshold for Event 1F . 164
5.10.14 Event threshold for Event 1I . 165
5.10.15 Measurement quantity. 165
5.10.16 void . 165
5.10.17 void . 165
5.10.18 void . 165
5.10.19 Positioning Method . 165
5.10.20 Collection period for RRM measurements LTE . 166
5.10.21 Collection period for RRM measurements UMTS . 166
5.10.22 Measurement period UMTS . 167
5.10.23 Measurement period LTE . 167
5.10.24 MDT PLMN List . 168
5.10.25 MBSFN Area List . 168
6 MDT Reporting . 169
6.1 MDT reporting in case of Immediate MDT: . 169
6.2 MDT reporting in case of Logged MDT . 170
6.3 MDT reporting in case of Logged MBSFN MDT . 171
7 Trace reporting . 172
7.1 Single operator case. 172
7.2 Shared network case for Participating Operator . 173
8 RLF Reporting . 174
9 RCEF Reporting . 174
Annex A (normative): Trace failure notification file format. 175
A.1 Global structure . 175
A.2 XML elements fileHeader and fileFooter. 175
A.2.1 XML elements fileHeader . 175
A.2.2 XML element fileFooter. 175
A.3 Trace failure notification specific XML elements . 175
A.4 Trace IRP XML File Name Conventions . 175
A.5 Trace failure notification file XML schema . 176
ETSI
3GPP TS 32.422 version 15.3.0 Release 15 7 ETSI TS 132 422 V15.3.0 (2020-03)
Annex B (informative): Examples for alternative ways to route the Trace file to the TCE . 177
B.1 Routing the Trace file directly to the TCE . 177
B.2 Routing the Trace file via the management system . 177
Annex C (informative): Change history . 178
History . 184

ETSI
3GPP TS 32.422 version 15.3.0 Release 15 8 ETSI TS 132 422 V15.3.0 (2020-03)
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:
TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements";
TS 32.422: "Subscriber and equipment trace: Trace control and configuration management";
TS 32.423: "Subscriber and equipment trace: Trace data definition and management";
Additionally, there is a GSM only Subscriber and Equipment Trace specification: 3GPP TS 52.008 [5].
Subscriber and Equipment Trace provide very detailed information at call level on one or more specific mobile(s). This
data is an additional source of information to Performance Measurements and allows going further in monitoring and
optimisation operations.
Contrary to Performance Measurements, which are a permanent source of information, Trace is activated on user
demand for a limited period of time for specific analysis purposes.
Trace plays a major role in activities such as determination of the root cause of a malfunctioning mobile, advanced
troubleshooting, optimisation of resource usage and quality, RF coverage control and capacity improvement, dropped
call analysis, Core Network, UTRAN, EPC, 5GC, E-UTRAN and NG-RAN procedure validation.
The capability to log data on any interface at call level for a specific user (e.g. IMSI or SUPI) or mobile type (e.g. IMEI
or IMEISV), or service initiated from a UE allows getting information which cannot be deduced from Performance
Measurements such as perception of end-user QoS during his call (e.g. requested QoS vs. provided QoS), correlation
between protocol messages and RF measurements, or interoperability with specific mobile vendors.
Moreover, Performance Measurements provide values aggregated on an observation period, Subscriber and Equipment
Trace give instantaneous values for a specific event (e.g., call, location update, etc.).
If Performance Measurements are mandatory for daily operations, future network planning and primary trouble
shooting, Subscriber and Equipment Trace is the easy way to go deeper into investigation and network optimisation.
In order to produce this data, Subscriber and Equipment Trace are carried out 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.422 version 15.3.0 Release 15 9 ETSI TS 132 422 V15.3.0 (2020-03)
1 Scope
The present document describes the mechanisms used for the control and configuration of the Trace, Minimization of
Drive Test (MDT) and Radio Link Failure (RLF) reporting functionality at the management system (at the Element
Manager (EM) and or Network Manager (NMs) in UMTS and EPS), Network Elements (NEs) and User Equipment
(UEs). For Trace functionality, it covers the triggering events for starting/stoppi
...