ETSI TS 132 423 V16.15.0 (2025-07)

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

RTS/TSGS-0532423vgf0

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 29-Jul-2025

Standards Content (Sample)

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

3GPP TS 32.423 version 16.15.0 Release 16 1 ETSI TS 132 423 V16.15.0 (2025-07)

Reference
RTS/TSGS-0532423vgf0
Keywords
5G,GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
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 on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2025.
All rights reserved.
ETSI
3GPP TS 32.423 version 16.15.0 Release 16 2 ETSI TS 132 423 V16.15.0 (2025-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo 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.
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 at 3GPP to ETSI numbering cross-referencing.
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.423 version 16.15.0 Release 16 3 ETSI TS 132 423 V16.15.0 (2025-07)
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 . 9
3.3 Abbreviations . 9
4 Trace record contents . 10
4.1 General . 10
4.2 MSC Server Trace Record Content . 11
4.3 MGW Trace Record Content. 18
4.4 SGSN Trace Record Content. 19
4.5 GGSN Trace Record Content . 28
4.6 UTRAN Trace Record Content . 32
4.7 Void . 40
4.8 Void . 40
4.9 HSS Trace Record Content . 41
4.10 BM-SC Trace Record Content . 46
4.11 PGW Trace Record Content . 47
4.12 MME Trace Record Content . 52
4.13 E-UTRAN Trace Record Content . 61
4.14 SGW Trace Record Content . 67
4.15 EIR Trace Record Content . 72
4.16 LTE MDT Trace Record Content . 73
4.16.1 Trace Record for Immediate MDT measurements . 73
4.16.2 Trace Record for UE location information . 76
4.17 UMTS MDT Trace Record Content . 76
4.17.1 Trace Record for Immediate MDT measurements . 76
4.17.2 Trace Record for UE location information . 78
4.18 AMF Trace Record Content . 78
4.19 SMF Trace Record Content . 80
4.20 PCF Trace Record Content . 81
4.21 AUSF Trace Record Content. 81
4.22 NEF Trace Record Content . 82
4.23 NRF Trace Record Content . 82
4.24 NSSF Trace Record Content . 82
4.25 UDM Trace Record Content . 83
4.26 UPF Trace Record Content . 84
4.27 SMSF Trace Record Content. 85
4.28 AF Trace Record Content . 85
4.29 Void . 86
4.30 gNB-CU-CP Trace Record Content . 86
4.31 gNB-CU-UP Trace Record Content . 87
4.32 gNB-DU Trace Record Content . 87
4.33 ng-eNB Trace Record Content . 87
4.34 NR MDT Trace Record Content . 89
4.34.1 Trace Record for Immediate MDT measurements . 89
4.34.2 Trace Record for UE location information . 91
ETSI
3GPP TS 32.423 version 16.15.0 Release 16 4 ETSI TS 132 423 V16.15.0 (2025-07)
5 Trace streaming format . 91
5.1 Introduction . 91
5.2 Streaming Trace Record . 92
5.2.1 Introduction. 92
5.2.2 Streaming Trace Record Header . 92
5.2.3 Streaming Trace Record Payload . 93
5.2.4 Streaming Trace administrative messages . 94
5.2.4.1 Introduction . 94
5.2.4.2 Trace Session Start administrative message . 94
5.2.4.3 Trace Session Stop administrative message . 94
5.2.4.3a Trace Recording Session Start administrative message . 94
5.2.4.3b Trace Recording Session Stop administrative message . 94
5.2.4.4 Trace Stream Heartbeat administrative message . 94
5.2.4.5 Trace Recording Session Not Started administrative message . 95
5.2.4.6 Trace Recording Session Dropped Events administrative message . 95
5.2.4.7 Trace Session Not Started administrative message . 95
5.2.5 Void . 95
5.3 Void . 95
Annex A (normative): Trace Report File Format. 96
A.0 Introduction . 96
A.1 Parameter description and mapping table. 97
A.2 XML file format definition . 100
A.2.1 XML trace/MDT file diagram . 100
A.2.2 Trace data file XML schema . 101
Annex B (normative): Trace Report File Conventions and Transfer Procedure . 104
B.0 Introduction . 104
B.1 File naming convention . 104
B.2 File transfer . 105
Annex C (informative): Trace Functional Architecture: Reporting . 106
C.1 Figure of Trace Reporting . 106
Annex D (informative): Examples of trace files . 108
D.1 Examples of trace XML file . 108
D.1.1 Example of XML trace file with the maximum level of details . 108
D.1.2 Example of XML trace file with the minimum level of details . 109
D.1.3 Example of XML trace file for IMSI information from the MME . 109
D.1.4 Example of MDT XML file . 110
Annex E (informative): Void . 111
Annex F (Informative): Void . 112
Annex G (normative): Trace Record Protocol Buffer (GPB) . 113
G.1 Transport Protocol Payload Format . 113
G.2 Trace Record Protocol Buffer (GPB) definitions . 113
Annex H (informative): Examples of Protocol Buffer (GPB) encoded Streaming Trace
administrative messages . 115
Annex I (informative): Change history . 116
History . 119

ETSI
3GPP TS 32.423 version 16.15.0 Release 16 5 ETSI TS 132 423 V16.15.0 (2025-07)
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 [2]: "Subscriber and equipment trace; Trace concepts and requirements";
TS 32.422 [3]: "Subscriber and equipment trace; Trace control and configuration management ";
TS 32.423: "Subscriber and equipment trace; Trace data definition and management";
Subscriber and EquipmentTrace 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 by 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 EquipmentTrace is the easy way to go deeper into investigation and network optimisation.
In order to produce this data, Subscriber and Equipmenttrace 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.423 version 16.15.0 Release 16 6 ETSI TS 132 423 V16.15.0 (2025-07)
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
3GPP TS 32.423 version 16.15.0 Release 16 7 ETSI TS 132 423 V16.15.0 (2025-07)
[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
3GPP TS 32.423 version 16.15.0 Release 16 8 ETSI TS 132 423 V16.15.0 (2025-07)
[34] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management".
[35] 3GPP TS 38.314: "NR; layer 2 measurements ".
[36] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[37] 3GPP TS 38.213: "NR; Physical layer procedures for control".
[38] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer;
Measurements".
[39] 3GPP TS 32.425: "Telecommunication management; Performance Management (PM); Performance
measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN)".
[40] IETF RFC 6455: "The WebSocket Procotol".
[41] IETF RFC 7692: "Compression Extensions for WebSocket".
[42] 3GPP TS 38.215: "NR; Physical layer measurements".
[43] 3GPP TS 28.532: "Management and orchestration; Generic management services".
[44] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User
Equipment (UE) positioning in NG-RAN".
[45] Void
[46] Void
[47] Void
[48] 3GPP TS 33.401: "System Architecture Evolution (SAE); Security architecture".
[49] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
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.
ETSI
3GPP TS 32.423 version 16.15.0 Release 16 9 ETSI TS 132 423 V16.15.0 (2025-07)
3.2 Symbols
For the purposes of the present document, the following symbols apply:
: Element named xxx
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
3GPP TS 32.423 version 16.15.0 Release 16 10 ETSI TS 132 423 V16.15.0 (2025-07)
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.
Receiving entities may be outside an operator’s secure domain. For any IEs or parts of IEs containing security keys as specified in subclause 6.2 of 3GPP TS 33.401 [48] and
subclause 6.2.2.1 of TS 33.501 [49] (e.g. K ) the value 0 shall be written in the trace file.
eNB
ETSI
3GPP TS 32.423 version 16.15.0 Release 16 11 ETSI TS 132 423 V16.15.0 (2025-07)
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
3GPP TS 32.423 version 16.15.0 Release 16 12 ETSI TS 132 423 V16.15.0 (2025-07)
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 party BCD number SETUP M M TS 24.008
Redirecting party BCD number SETUP M M TS 24.008
AUTHENTICATION FAILURE
CM SERVICE REJECT
Reject cause ABORT M M TS 24.008
LOCATION UPDATING REJECT
MM STATUS
CM RE-ESTABLISHMENT REQUEST
LOCATION UPDATING ACCEPT
Location area identification M M TS 24.008
LOCATION UPDATING REQUEST
TMSI REALLOCATION COMMAND
Iu, A MM CM RE-ESTABLISHMENT REQUEST
CM SERVICE REQUEST
IDENTITY REQUEST
IDENTITY RESPONSE
Mobile identity M M TS 24.008
IMSI DETACH INDICATION
LOCATION UPDATING ACCEPT
LOCATION UPDATING REQUEST
TMSI REALLOCATION COMMAND
CM service type CM SERVICE REQUEST M M TS 24.008
Location updating type LOCATION UPDATING REQUEST M M TS 24.008
FACILITY
Iu, A SS Facility REGISTER M M TS 24.008
RELEASE COMPLETE
ETSI
3GPP TS 32.423 version 16.15.0 Release 16 13 ETSI TS 132 423 V16.15.0 (2025-07)
Cause RELEASE COMPLETE M M TS 24.008
TP-Originating-Address SMS-DELIVER M M TS 23.040
SMS-DELIVER
TP-Service-Centre- Time-Stamp SMS-SUBMIT-REPORT M M TS 23.040
SMS-STATUS-REPORT
Iu, A SMS SMS-DELIVER-REPORT
TP-Failure-Cause M M TS 23.040
SMS-SUBMIT-REPORT
SMS-SUBMIT
TP-Destination-Address M M TS 23.040
SMS-COMMAND
TP-Recipient-Address SMS-STATUS-REPORT M M TS 23.040
ASSIGNMENT REQUEST
Channel Type M M TS 48.008
HANDOVER REQUEST
Circuit ASSIGNMENT REQUEST M M TS 48.008
ASSIGNMENT COMPLETE
HANDOVER REQUEST
Cell Identifier (Serving) HANDOVER COMMAND M M TS 48.008
HANDOVER PERFORMED
PERFORM LOCATION REQUEST
ASSIGNMENT COMPLETE
Chosen Channel HANDOVER REQUEST ACKNOWLEDGE M M TS 48.008
HANDOVER PERFORMED
ASSIGNMENT COMPLETE
HANDOVER REQUEST
Speech version (chosen) HANDOVER REQUIRED M M TS 48.008
HANDOVER REQUEST ACKNOWLEDGE
HANDOVER PERFORMED
ASSIGNMENT FAILURE
HANDOVER REQUEST
HANDOVER REQUIRED
A BSSMAP
HANDOVER FAILURE
Cause M M TS 48.008
CLEAR REQUEST
CLEAR COMMAND
HANDOVER PERFORMED
HANDOVER REQUIRED REJECT
ASSIGNMENT FAILURE
RR Cause HANDOVER COMPLETE M M TS 48.008
HANDOVER FAILURE
Cell Identifier (target) HANDOVER REQUEST M M TS 48.008
HANDOVER REQUEST
Current Channel type 1 M M TS 48.008
HANDOVER REQUIRED
Cell Identifier List HANDOVER REQUIRED
M M TS 48.008
(Preferred) PAGING
PAGING
IMSI M M TS 48.008
COMMON ID
Location Type PERFORM LOCATION REQUEST M M TS 48.008
Location Estimate PERFORM LOCATION RESPONSE M M TS 48.008
PERFORM LOCATION RESPONSE
LCS Cause M M TS 48.008
PERFORM LOCATION ABORT
ETSI
3GPP TS 32.423 version 16.15.0 Release 16 14 ETSI TS 132 423 V16.15.0 (2025-07)
MAP_REGISTER_SS
MAP_ERASE_SS
MAP_ACTIVATE_SS
MAP_DEACTIVATE_SS
SS-Code M M TS 29.002
MAP_INTERROGATE_SS
MAP_REGISTER_PASSWORD
MAP_REGISTER_CC_ENTRY
MAP_ERASE_CC_ENTRY
Forwarded-to number with subaddress MAP_REGISTER_SS M M TS 29.002
B MAP MAP_REGISTER_SS
MAP_ERASE_SS
Basic service MAP_ACTIVATE_SS M M TS 29.002
MAP_DEACTIVATE_SS
MAP_INTERROGATE_SS
SM RP DA MAP-SEND-INFO-FOR-MT-SMS M M TS 29.002
Service Centre Address MAP-SEND-INFO-FOR-MO-SMS M M TS 29.002
Alert Reason MAP-READY-FOR-SM M M TS 29.002
TS 29.002
Abort reason Abort M M
TS 23.018
Complete Call
Process Access Request ack
Process Call Waiting TS 29.002
MSISDN M M
Send Info For Incoming Call ack TS 23.018
MAP-SEND-INFO-FOR-MT-SMS
MAP-SEND-INFO-FOR-MO-SMS
Complete Call
Page MS ack
Process Access Request TS 29.002
IMEI(SV) M M
Process Access Request ack TS 23.018
Provide IMEI ack
Search For MS ack
Complete Call TS 29.002
PLMN bearer capability M M
Process Call Waiting TS 23.018
Complete Call TS 29.002
ISDN bearer capability M M
Process Call Waiting TS 23.018
C MAP
Page MS
Process Access Request
Process Access Request ack
TS 29.002
IMSI Provide IMSI ack M M
TS 23.018
Search For MS
Send Info For Incoming Call ack
MAP-SEND-INFO-FOR-MT-SMS
Page MS
Page MS ack TS 29.002
Location area ID / Current location area ID M M
Process Access Request TS 23.018
Search For MS ack
Page MS TS 29.002
Page type M M
Search For MS TS 23.018
Page MS ack
TS 29.002
Serving cell ID Process Access Request M M
TS 23.018
Search For MS ack
ETSI
3GPP TS 32.423 version 16.15.0 Release 16 15 ETSI TS 132 423 V16.15.0 (2025-07)
Page MS ack
TS 29.002
Service area ID Process Access Request M M
TS 23.018
Search For MS ack
TS 29.002
CM service type Process Access Request M M
TS 23.018
TS 29.002
MSRN Send Info For Incoming Call M M
TS 23.018
Send Info For Incoming Call TS 29.002
Bearer service M M
Send Info For Outgoing Call TS 23.018
Send Info For Incoming Call TS 29.002
Teleservice M M
Send Info For Outgoing Call TS 23.018
TS 29.002
Dialled number Send Info For Incoming Call M M
TS 23.018
TS 29.002
Number of forwarding Send Info For Incoming Call M M
TS 23.018
TS 29.002
Forwarded-to number Send Info For Incoming Call ack M M
TS 23.018
TS 29.002
Forwarding reason Send Info For Incoming Call ack M M
TS 23.018
TS 29.002
Called number Send Info For Outgoing Call M M
TS 23.018
TS 29.002
MSISDN Send Routeing Info M M
TS 23.018
User error Every message where it appears M M TS 29.002
Provider error Every message where it appears M M TS 29.002
MAP-SEND-ROUTING-INFO-FOR-SM
Service Centre Address MAP-REPORT-SM-DELIVERY-STATUS M M TS 29.002
MAP-ALERT-SERVICE-CENTRE
SM Delivery Outcome MAP-REPORT-SM-DELIVERY-STATUS M M TS 29.002
MAP-ALERT-SERVICE-CENTRE
MSIsdn-Alert M M TS 29.002
MAP-INFORM-SERVICE-CEN
TS 29.002
Number of forwarding Send Routeing Info M M
TS 23.018
TS 29.002
ISDN BC Send Routeing Info M M
TS 23.018
TS 29.002
IMSI Send Routeing Info ack M M
TS 23.018
TS 29.002
Roaming number Send Routeing Info ack M M
TS 23.018
TS 29.002
Forwarded-to number Send Routeing Info ack M M
TS 23.018
Send Routeing Info ack TS 29.002
Forwarding reason M M
TS 23.018
Send Routeing Info ack TS 29.002
MSISDN M M
MAP_SEND_ROUTING_INFO_FOR_SM TS 23.018
User error Every message where it appears M M TS 29.002
Provider error
Every message where it appears M M TS 29.002

HLR number MAP_RESTORE_DATA M M TS 29.002
D MAP
MS Not Reachable Flag MAP_RESTORE_DATA M M TS 29.002
ETSI
3GPP TS 32.423 version 16.15.0 Release 16 16 ETSI TS 132 423 V16.15.0 (2025-07)
MAP_REGISTER_SS
MAP_ERASE_SS
MAP_ACTIVATE_SS
MAP_DEACTIVATE_SS
SS-Code M M TS 29.002
MAP_INTERROGATE_SS
MAP_REGISTER_PASSWORD
MAP_REGISTER_CC_ENTRY
MAP_ERASE_CC_ENTRY
Forwarded-to number with subaddress MAP_REGISTER_SS M M TS 29.002
MAP_REGISTER_SS
MAP_ERASE_SS
Basic service MAP_ACTIVATE_SS M M TS 29.002
MAP_DEACTIVATE_SS
MAP_INTERROGATE_SS
Alert Reason MAP-READY-FOR-SM M M TS 29.002
MSC Address MAP_UPDATE_LOCATION M M TS 29.002
Provide Roaming Number
Provide Subscriber Info
MAP_UPDATE_LOCATION
MAP_CANCEL_LOCATION TS 29.002
IMSI M M
MAP_PURGE_MS TS 23.018
MAP-INSERT-SUBSCRIBER-DATA
MAP-DELETE-SUBSCRIBER-DATA
MAP_RESTORE_DATA
Provide Roaming Number TS 29.002
MSISDN M M
MAP-INSERT-SUBSCRIBER-DATA TS 23.018
TS 29.002
PLMN bearer capability Provide Roaming Number M M
TS 23.018
TS 29.002
ISDN BC Provide Roaming Number M M
TS 23.018
TS 29.002
Roaming number Provide Roaming Number ack M M
TS 23.018
TS 29.002
Service area ID Provide Subscriber Info ack M M
TS 23.018
TS 29.002
Cell ID Provide Subscriber Info ack M M
TS 23.018
TS 29.002
IMEI(SV) Provide Subscriber Info ack M M
TS 23.018
User error Every message where it appears M M TS 29.002
Provider error Every message where it appears M M TS 29.002
TS 29.002
IMEI(SV) MAP_CHECK_IMEI M M
TS 23.018
TS 29.002
F MAP Equipment status MAP_CHECK_IMEI M M
TS 23.018
User error Every message where it appears M M TS 29.002
Provider error Every message where it appears M M TS 29.002
MAP_PREPARE_HANDOVER
Targ
...