ETSI TS 132 423 V15.2.0 (2020-03)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Subscriber and equipment trace; Trace data definition and management (3GPP TS 32.423 version 15.2.0 Release 15)

RTS/TSGS-0532423vf20

General Information

• Status: Published
• Publication Date: 30-Mar-2020
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Completion
• Completion Date: 31-Mar-2020

Standards Content (Sample)

ETSI TS 132 423 V15.2.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 data definition and management
(3GPP TS 32.423 version 15.2.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 1 ETSI TS 132 423 V15.2.0 (2020-03)



Reference
RTS/TSGS-0532423vf20
Keywords
GSM,LTE,UMTS
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 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

---------------------- Page: 2 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 2 ETSI TS 132 423 V15.2.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

---------------------- Page: 3 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 3 ETSI TS 132 423 V15.2.0 (2020-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Trace record contents . 9
4.1 General . 9
4.2 MSC Server Trace Record Content . 10
4.3 MGW Trace Record Content. 17
4.4 SGSN Trace Record Content. 18
4.5 GGSN Trace Record Content . 27
4.6 UTRAN Trace Record Content . 31
4.7 S-CSCF Trace Record Content . 38
4.8 P-CSCF Trace Record Content . 38
4.9 HSS Trace Record Content . 39
4.10 BM-SC Trace Record Content . 43
4.11 PGW Trace Record Content . 44
4.12 MME Trace Record Content . 49
4.13 E-UTRAN Trace Record Content . 58
4.14 SGW Trace Record Content . 64
4.15 EIR Trace Record Content . 69
4.16 LTE MDT Trace Record Content . 70
4.16.1 Trace Record for Immediate MDT measurements . 70
4.16.2 Trace Record for UE location information . 73
4.17 UMTS MDT Trace Record Content . 73
4.17.1 Trace Record for Immediate MDT measurements . 73
4.17.2 Trace Record for UE location information . 75
4.18 AMF Trace Record Content . 75
4.19 SMF Trace Record Content . 77
4.20 PCF Trace Record Content . 77
4.21 AUSF Trace Record Content. 78
4.22 NEF Trace Record Content . 78
4.23 NRF Trace Record Content . 79
4.24 NSSF Trace Record Content . 79
4.25 UDM Trace Record Content . 80
4.26 UPF Trace Record Content . 81
4.27 SMSF Trace Record Content. 81
4.28 AF Trace Record Content . 81
4.29 Void . 82
4.30 gNB-CU-CP Trace Record Content . 82
4.31 gNB-CU-UP Trace Record Content . 83
4.32 gNB-DU Trace Record Content . 83
4.33 ng-eNB Trace Record Content . 84
Annex A (normative): Trace Report File Format . 85
A.0 Introduction . 85
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 4 ETSI TS 132 423 V15.2.0 (2020-03)
A.1 Parameter description and mapping table. 86
A.2 XML file format definition . 89
A.2.1 XML trace/MDT file diagram . 89
A.2.2 Trace data file XML schema . 90
Annex B (normative): Trace Report File Conventions and Transfer Procedure . 93
B.0 Introduction . 93
B.1 File naming convention . 93
B.2 File transfer . 94
Annex C (informative): Trace Functional Architecture: Reporting . 95
C.1 Figure of Trace Reporting . 95
Annex D (informative): Examples of trace files . 97
D.1 Examples of trace XML file . 97
D.1.1 Example of XML trace file with the maximum level of details . 97
D.1.2 Example of XML trace file with the minimum level of details . 98
D.1.3 Example of XML trace file for IMSI information from the MME . 98
D.1.4 Example of MDT XML file . 99
Annex E (informative): Void . 100
Annex F (informative): Change history . 101
History . 104

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 5 ETSI TS 132 423 V15.2.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";
Subscriber and MS 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 purpose
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 and TRAN end to end  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) 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 MS Trace is the easy way to go deeper into investigation and network optimisation.
In order to produce this data, Subscriber and MS 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

---------------------- Page: 6 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 6 ETSI TS 132 423 V15.2.0 (2020-03)
1 Scope
The present document describes Trace data definition and management. It covers the trace records content, their format
and transfer across UMTS networks, EPS networks or 5GS networks. GSM Trace is outside of the scope of this
specification.
The present document also describes the data definition for Minimization of Drive Tests (MDT) across UMTS networks
or EPS networks.
The objectives of the present document are:
- To provide the descriptions for a standard set of Trace and MDT data;
- To define the common format of trace and MDT records; and
- To define a method for the reporting of Trace and MDT results across the management interfaces.
Clause 4 details the various Trace records content, Annex A provides Trace and MDT report file format, Annex B
provides the trace report file conventions and transfer procedure, Annex C provides the trace reporting functional
architecture and Annex D provides some trace and MDT files examples. Trace and MDT concepts and requirements are
covered in TS 32.421 [2] while Trace control and configuration management are described in 3GPP TS 32.422 [3].
The definition of Trace and MDT data is intended to result in comparability of Trace and MDT data produced in a
multi-vendor wireless UMTS and/or EPS network.
The following is beyond the scope of the present document, and therefore the present document does not describe:
- Any notification mechanisms or IRPs for trace. Only file transfer mechanism is specified for trace data transfer;
- Any data compression mechanisms for trace data transfer;
- Any Trace capability limitations (e.g. maximum number of simultaneous traced mobiles for a given NE).
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, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[2] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace: Trace
concepts and requirements."
[3] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace: Trace
control and configuration management ".
[4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[5] W3C Recommendation "Extensible Markup Language (XML) 1.0" (Second Edition, 6 October
2000) http://www.w3.org/TR/2000/REC-xml-20001006
[6] W3C Recommendation "Namespaces in XML" (14 January 1999)
http://www.w3.org/TR/1999/REC-xml-names-19990114
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 7 ETSI TS 132 423 V15.2.0 (2020-03)
[7] W3C Recommendation "XML Schema Part 0: Primer" (2 May 2001)
http://www.w3.org/TR/2001/REC-xmlschema-0-20010502
[8] W3C Recommendation "XML Schema Part 1: Structures" (2 May 2001)
http://www.w3.org/TR/2001/REC-xmlschema-1-20010502
[9] W3C Recommendation "XML Schema Part 2: Datatypes" (2 May 2001)
http://www.w3.org/TR/2001/REC-xmlschema-2-20010502
[10] International Standard ISO 8601: 1988 (E) "Representations of dates and times" (1988-06-15)
http://www.iso.ch/markete/8601.pdf
[11] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[12] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[13] 3GPP TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service
(GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[14] 3GPP TS 29.212: "Policy and Charging Control (PCC);Reference points".
[15] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
[16] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1
Application Protocol (S1AP)".
[17] 3GPP TS 36.423 "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2
Application Protocol (X2AP)".
[18] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[19] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2"
[20] 3GPP TS 38.300: "NR and NG-RAN Overall Description; Stage 2".
[21] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[22] 3GPP TS 38.401: "NG-RAN; Architecture Description".
[23] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[24] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
[25] 3GPP TS 38.463: "NG-RAN; E1 Application Protocol (E1AP)".
[26] 3GPP TS 38.473: "NG-RAN; F1 Application Protocol (F1AP)".
[27] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[28] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control
(RRC); Protocol specification".
[29] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".
[30] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification".
[31] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 -
Measurements".
[32] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial
Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT);
Overall description; Stage 2".
[33] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures".
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 8 ETSI TS 132 423 V15.2.0 (2020-03)
[34] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 32.421 [2], 3GPP TS 32.422 [3] ,
TS 23.501 [18], TS 38.300 [20], TS 38.401 [22], TS 37.320 [32] and the following apply.
Minimum Level of detail: Allows for retrieval of a decoded subset of the IEs contained in the signalling interface
messages.
Medium Level of detail: Allows for retrieval of the decoded subset of the IEs contained in the signalling interface
messages in the Minimum Level plus a selected set of decoded radio measurement IEs.
Maximum Level of detail: Allows for retrieval of signalling interface messages within the Trace Scope in encoded
format.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
xxx : Element named xxx
 The maximum number of occurrence is 1
xxx
: Element named xxx
 The maximum number of occurrence is unbounded
1.∞
: Global element
The XML element has a value part
: Required element
: Optional element
•••
: Sequence
: Choice
:

3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [4], TS 32.101 [1], TS 23.501 [18], TS
38.300 [20] and TS 38.401 [22] and TS 37.320 [32] apply.
NSA Non Stand Alone

ETSI

---------------------- Page: 9 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 9 ETSI TS 132 423 V15.2.0 (2020-03)
4 Trace record contents
4.1 General
The trace reference, trace type and operation system identification are all provided on trace activation.
Each record may contain an MSC Server, MGW, SGSN, GGSN, S-CSCF, P-CSCF, UTRAN, HSS, MME, Serving GW, E-UTRAN, AUSF, AMF, NEF, NRF, NSSF, PCF,
SMF, SMSF, UDM, UPF, AF and , ng-eNB, gNB-CU-CP, gNB-CU-UP and gNB-DU event record. A key is included in the table indicating whether or not the field is
mandatory.
The following table shows the template for trace record description for minimum and medium trace depth:

Trace depth
Interface name IE name Message name(s) Notes
Protocol name
Min Med


Interface name: Contains the name of the interface, where the IE is available.
Protocol name: Contains the protocol name on the interface, where the IE is available.
IE name: The name of the Information Element, which should be decoded.
Message name(s): The name of the message(s), where the IE is included.
Trace depth: Shows in which trace depth the IE should be recorded. It also classifies whether the IE is mandatory in the trace record or not (M, O or X: meaning described in
the previous table)

M Mandatory This field must be in the trace record if it is available, i.e. if the message appears during the trace recording session and the IE is present in
the message.
O Optional This field is optional and its support is a matter for agreement between equipment manufacturer and network operator.
X Not applicable This field is not required in this instance.
CM Conditional Mandatory This field must be in the trace record if it is available and the condition is met.

NOTE: Any kind of comments related to the IE can be made here. Also this is the placeholder for referencing the relevant 3GPP specifications, which define the IE.
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 10 ETSI TS 132 423 V15.2.0 (2020-03)
4.2 MSC Server Trace Record Content
The following table shows the trace record content for MSC Server.
The trace record is the same for management based activation and for signalling based activation.
For MSC Server, the Minimum level of detail shall be supported.
ETSI

---------------------- Page: 11 ----------------------
3GPP TS 32.423 version 15.2.0 Release 15 11 ETSI TS 132 423 V15.2.0 (2020-03)
Prot. Trace depth
Interface name IE name Message name(s) Notes
name
Min Med
ALERTING
CALL PROCEEDING
CONNECT
DISCONNECT TS 24.008
Facility M M
FACILITY TS 24.080
RELEASE
RELEASE COMPLETE
SETUP
CALL CONFIRMED
CALL PROCEEDING
EMERGENCY SETUP
Bearer capability MODIFY M M TS 24.008
MODIFY COMPLETE
MODIFY REJECT
SETUP
Iu, A CC
CALL CONFIRMED
CONGESTION CONTROL
DISCONNECT
HOLD REJECT
MODIFY REJECT
Cause M M TS 24.008
RELEASE
RELEASE COMPLETE
RETRIEVE REJECT
START DTMF REJECT
STATUS
Connected number CONNECT M M TS 24.008
Calling party BCD number SETUP M M TS 24.008
Called
...