Trace Data Definition and Management
Trace Data Definition and Management
0 (2013-10)
Technical Specification
Reference
RTS/TSGS-0532423vb60
Keywords
GSM,LTE,UMTS
ETSI
Important notice
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
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
[Link]
If you find errors in the present document, please send your comment to one of the following services:
[Link]
Copyright Notification
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 2 ETSI TS 132 423 V11.6.0 (2013-10)
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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
[Link]
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 3 ETSI TS 132 423 V11.6.0 (2013-10)
Contents
Intellectual Property Rights ................................................................................................................................2
Foreword.............................................................................................................................................................2
Foreword.............................................................................................................................................................5
Introduction ........................................................................................................................................................5
1 Scope ........................................................................................................................................................6
2 References ................................................................................................................................................6
3 Definitions, symbols and abbreviations ...................................................................................................7
3.1 Definitions .......................................................................................................................................................... 7
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 ........................................................................................................................... 26
4.6 UTRAN Trace Record Content ........................................................................................................................ 29
4.7 S-CSCF Trace Record Content ........................................................................................................................ 36
4.8 P-CSCF Trace Record Content ........................................................................................................................ 36
4.9 HSS Trace Record Content .............................................................................................................................. 37
4.10 BM-SC Trace Record Content ......................................................................................................................... 41
4.11 PGW Trace Record Content ............................................................................................................................. 42
4.12 MME Trace Record Content ............................................................................................................................ 46
4.13 E-UTRAN Trace Record Content .................................................................................................................... 54
4.14 SGW Trace Record Content ............................................................................................................................. 59
4.15 EIR Trace Record Content ............................................................................................................................... 63
4.16 LTE MDT Trace Record Content..................................................................................................................... 64
4.16.1 Trace Record for Immediate MDT measurements...................................................................................... 64
4.16.2 Trace Record for UE location information ................................................................................................. 65
4.17 UMTS MDT Trace Record Content ................................................................................................................. 65
4.17.1 Trace Record for Immediate MDT measurements...................................................................................... 65
4.17.2 Trace Record for UE location information ................................................................................................. 66
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 4 ETSI TS 132 423 V11.6.0 (2013-10)
D.1.2 Example of XML trace file with the minimum level of details ........................................................................ 80
D.1.3 Example of XML trace file for IMSI information from the MME ............................................................. 80
D.1.4 Example of MDT XML file ...................................................................................................................81
Annex E (informative): Void .................................................................................................................82
Annex F (informative): Change history ...............................................................................................83
History ..............................................................................................................................................................84
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 5 ETSI TS 132 423 V11.6.0 (2013-10)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification
Group Services and System Aspects; Telecommunication management, as identified below:
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 UTRAN end to end 3G procedure validation.
The capability to log data on any interface at call level for a specific user (e.g. IMSI) 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 3G 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
3GPP TS 32.423 version 11.6.0 Release 11 6 ETSI TS 132 423 V11.6.0 (2013-10)
1 Scope
The present document describes Trace data definition and management. It covers the trace records content, their format
and transfer across UMTS networks or EPS 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.
• 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 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 ".
[5] W3C Recommendation "Extensible Markup Language (XML) 1.0" (Second Edition, 6 October
2000) [Link]
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 7 ETSI TS 132 423 V11.6.0 (2013-10)
[10] International Standard ISO 8601: 1988 (E) "Representations of dates and times" (1988-06-15)
[Link]
[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".
[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)".
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 32.421 [2] and 3GPP TS 32.422
[3] 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 11.6.0 Release 11 8 ETSI TS 132 423 V11.6.0 (2013-10)
3.2 Symbols
For the purposes of the present document, the following symbols apply:
xxx
: Element named xxx
The maximum number of occurrence is unbounded
1..∞
: Global element
: Required element
: Optional element
••• : Sequence
: : Choice
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [4] and 3GPP TS 32.101 [1]
apply.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 9 ETSI TS 132 423 V11.6.0 (2013-10)
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, or E-UTRAN 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 Protocol name IE name Message name(s)
Min Med
Notes
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.
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
3GPP TS 32.423 version 11.6.0 Release 11 10 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 11 ETSI TS 132 423 V11.6.0 (2013-10)
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
Facility REGISTER M M TS 24.008
Iu, A SS
RELEASE COMPLETE
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
A BSSMAP
HANDOVER REQUEST ACKNOWLEDGE
HANDOVER PERFORMED
ASSIGNMENT FAILURE
HANDOVER REQUEST
HANDOVER REQUIRED
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
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 12 ETSI TS 132 423 V11.6.0 (2013-10)
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
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
C MAP 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
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
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 13 ETSI TS 132 423 V11.6.0 (2013-10)
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
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
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 14 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 15 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 16 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 17 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 18 ETSI TS 132 423 V11.6.0 (2013-10)
The trace record is the same for management based activation and for signalling based activation.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 19 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 20 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 21 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 22 ETSI TS 132 423 V11.6.0 (2013-10)
BSSAP+-GPRS-DETACH-INDICATION
BSSAP+-IMSI-DETACH-INDICATION
Cell global identity/ New CGI BSSAP+-LOCATION-UPDATE-REQUEST M M TS 29.018
BSSAP+-MS-ACTIVITY-INDICATION
BSSAP+-TMSI-REALLOCATION-COMPLETE
BSSAP+-GPRS-DETACH-INDICATION
BSSAP+-IMSI-DETACH-INDICATION
Service area identification /New SAI BSSAP+-LOCATION-UPDATE-REQUEST M M TS 29.018
BSSAP+-MS-ACTIVITY-INDICATION
BSSAP+-TMSI-REALLOCATION-COMPLETE
Detach type BSSAP+-IMSI-DETACH-INDICATION M M TS 29.018
Reject cause BSSAP+-LOCATION-UPDATE-REJECT M M TS 29.018
Update type BSSAP+-LOCATION-UPDATE-REQUEST M M TS 29.018
BSSAP+-LOCATION-UPDATE-ACCEPT
LAI/Old LAI BSSAP+-LOCATION-UPDATE-REQUEST M M TS 29.018
BSSAP+-PAGING-REQUEST
IMEISV BSSAP+-LOCATION-UPDATE-REQUEST M M TS 29.018
Erroneous message BSSAP+-MOBILE-STATUS M M TS 29.018
MAP_CANCEL_LOCATION
MAP_PURGE_MS
MAP_UPDATE_GPRS_LOCATION
IMSI MAP_NOTE_MM_EVENT M M TS 29.002
MAP-INSERT-SUBSCRIBER-DATA
MAP-DELETE-SUBSCRIBER-DATA
Gr MAP-READY-FOR-SM
Cancellation Type MAP_CANCEL_LOCATION M M TS 29.002
User error Every message where it appears M M TS 29.002
Provider error Every message where it appears M M TS 29.002
Location Information for GPRS MAP_NOTE_MM_EVENT M M TS 29.002
MAP MSISDN MAP-INSERT-SUBSCRIBER-DATA M M TS 29.002
Alert Reason MAP-READY-FOR-SM M M TS 29.002
MAP-MO-FORWARD-SHORT-MESSAGE
SM RP OA M M TS 29.002
MAP-MT-FORWARD-SHORT-MESSAGE
MAP-MO-FORWARD-SHORT-MESSAGE
Gd SM RP DA M M TS 29.002
MAP-MT-FORWARD-SHORT-MESSAGE
IMSI MAP-MO-FORWARD-SHORT-MESSAGE M M TS 29.002
More Messages To Send MAP-MT-FORWARD-SHORT-MESSAGE M M TS 29.002
IMEI(SV) MAP_CHECK_IMEI M M TS 29.002
Equipment status MAP_CHECK_IMEI M M TS 29.002
Gf
User error Every message where it appears M M TS 29.002
Provider error Every message where it appears M M TS 29.002
RAB ASSIGNMENT REQUEST
RAB ASSIGNMENT RESPONSE
RAB RELEASE REQUEST
Iu RANAP RAB ID IU RELEASE COMPLETE M M TS 25.413
RELOCATION REQUEST
RELOCATION REQUEST ACKNOWLEDGE
RELOCATION COMMAND
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 23 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 24 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 25 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 26 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 27 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 28 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 29 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 30 ETSI TS 132 423 V11.6.0 (2013-10)
Definitions:
• rncID of traced RNC: The id of the RNC traced, e.g. the RNC which handles the connection of the traced MS, during the Trace Recording Session.
• rncID of neighbouring RNC: The ids of all Neighbouring RNC involved in the Iur procedures during the Trace Recording Session.
• cId: The cIds of all cells involved in the Iub and Iur procedures during the Trace Recording Session. The cId is provided with each NBAP and
RNSAP messages
for which the cId is relevant.
• rabId: Specific recorded IE that contains the RAB identifier.
• rlId: Specific recorded IE that contains the Radio Link identifier
• rbId: Specific recorded IE that contains the Radio Bearer identifier
• Message name: Name of the protocol message
• Record extensions: A set of manufacturer specific extensions to the record
• Decoded: Some IEs shall be decoded (cf. detailed list in table 4.6.2. depending on trace depth)
• ASN.1: Messages in encoded format
Table 4.6.2 : trace record description for minimum and medium trace depth
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 31 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 32 ETSI TS 132 423 V11.6.0 (2013-10)
RRC/MEASUREMENT REPORT
Cell parameters Id O O TS 25.331
for measurement = inter frequency
RRC/MEASUREMENT REPORT
Timeslot list X O TS 25.331
for measurement = inter frequency
RRC/MEASUREMENT REPORT
BCCH ARFCN X M TS 25.331
for measurement = inter RAT
RRC/MEASUREMENT REPORT
GSM Carrier RSSI X M TS 25.331
for measurement = inter RAT
RRC/MEASUREMENT REPORT
RLC buffer Payload X M TS 25.331
for measurement = traffic volume
RRC/MEASUREMENT REPORT
Average RLC buffer payload X M TS 25.331
for measurement = traffic volume
RRC/MEASUREMENT REPORT
Variance of RLC buffer payload X M TS 25.331
for measurement = traffic volume
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 33 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 34 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 35 ETSI TS 132 423 V11.6.0 (2013-10)
Constraints:
The following optional IE names shall be supported for corresponding modes as described below:
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 36 ETSI TS 132 423 V11.6.0 (2013-10)
• PCCPCH RSCP
• Cell parameters Id
• UARFCN (Nt)
• Timeslot list
• UL Timeslot information
• DL Timeslot information
• UL Time Slot ISCP Info
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 37 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 38 ETSI TS 132 423 V11.6.0 (2013-10)
TS 29.002
Number of forwarding 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
TS 29.002
Forwarding reason Send Routeing Info ack M M
TS 23.018
Additional Number MAP-SEND-ROUTING-INFO-FOR-SM M M TS 29.002
SGSN address MAP_UPDATE_GPRS_LOCATION M M TS 29.002
MAP_CANCEL_LOCATION
MAP_PURGE_MS
IMSI MAP_UPDATE_GPRS_LOCATION M M TS 29.002
MAP-INSERT-SUBSCRIBER-DATA
Gr MAP MAP-READY-FOR-SM
MAP_UPDATE_GPRS_LOCATION
SGSN number M M TS 29.002
MAP_PURGE_MS
Alert Reason MAP-READY-FOR-SM M M TS 29.002
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_GPRS
IMSI MAP_FAILURE_REPORT M M TS 29.002
MAP_NOTE_MS_PRESENT_FOR_GPRS
MAP_SEND_ROUTING_INFO_FOR_GPRS
SGSN address M M TS 29.002
MAP_NOTE_MS_PRESENT_FOR_GPRS
Gc MAP MAP_SEND_ROUTING_INFO_FOR_GPRS
GGSN address MAP_FAILURE_REPORT M M TS 29.002
MAP_NOTE_MS_PRESENT_FOR_GPRS
Mobile Not Reachable Reason MAP_SEND_ROUTING_INFO_FOR_GPRS M M TS 29.002
User error Every message where it appears M M TS 29.002
Provider error Every message where it appears M M TS 29.002
USER-AUTHORIZATION-REQUEST M M TS 29.228
Public User Identity MULTIMEDIA-AUTH-REQUEST
LOCATION INFO REQUEST
USER-AUTHORIZATION-REQUEST M M TS 29.228
MULTIMEDIA-AUTH-REQUEST
Private User Identity
REGISTRATION-TERMINATION-REQUEST
Cx Diameter PUSH-PROFILE-REQUEST
Visited Network Identifier USER-AUTHORIZATION-REQUEST M M TS 29.228
SERVER-ASSIGNMENT-REQUEST M M TS 29.228
S-CSCF Name
MULTIMEDIA-AUTH-REQUEST
Server Assignment Type SERVER-ASSIGNMENT-REQUEST M M TS 29.228
M M TS 29.228
User Data Already Available SERVER-ASSIGNMENT-REQUEST
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 39 ETSI TS 132 423 V11.6.0 (2013-10)
M M TS 29.228
Reason for de-registration REGISTRATION-TERMINATION-REQUEST
REGISTRATION-TERMINATION-REQUEST M M TS 29.228
Routing Information
PUSH-PROFILE-REQUEST
M M TS 29.228
Number Authentication Items MULTIMEDIA-AUTH-REQUEST
M M TS 29.228
Authentication Data MULTIMEDIA-AUTH-REQUEST
M M TS 29.228
Authentication Scheme MULTIMEDIA-AUTH-REQUEST
M M TS 29.228
Registration result SERVER-ASSIGNMENT-ANSWER
USER-AUTHORIZATION-ANSWER M M TS 29.228
REGISTRATION-TERMINATION-ANSWER
Result LOCATION INFO ANSWER
PUSH-PROFILE-ANSWER
MULTIMEDIA-AUTH-ANSWER
USER-DATA-REQUEST M M TS 29.328
PROFILE-UPDATE-REQUEST
User Identity
SUBSCRIBE-NOTIFICATIONS-REQUEST
PUSH-NOTIFICATION-REQUEST
USER-DATA-REQUEST M M TS 29.328
Requested data PROFILE-UPDATE-REQUEST
SUBSCRIBE-NOTIFICATIONS-REQUEST
USER-DATA-REQUEST M M TS 29.328
Application Server Identity PROFILE-UPDATE-REQUEST
Sh Diameter
SUBSCRIBE-NOTIFICATIONS-REQUEST
PROFILE-UPDATE-REQUEST M M TS 29.328
Data
PUSH-NOTIFICATION-REQUEST
M M TS 29.328
Subscription request type SUBSCRIBE-NOTIFICATIONS-REQUEST
USER-DATA-ANSWER M M TS 29.328
PROFILE-UPDATE-ANSWER
Result
SUBSCRIBE-NOTIFICATIONS-ANSWER
PUSH-NOTIFICATION-ANSWER
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 40 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 41 ETSI TS 132 423 V11.6.0 (2013-10)
The record content is same for management based activation and for signalling based activation.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 42 ETSI TS 132 423 V11.6.0 (2013-10)
The trace record is the same for management based activation and for signalling based activation.
PGW shall support at least one of the following trace depth levels – Maximum, Medium or Minimum.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 43 ETSI TS 132 423 V11.6.0 (2013-10)
Table 4.11.2 : PGW trace record description for minimum and medium trace depth
Trace
Prot.
Interface name IE name Message name(s) depth Notes
name
Min Med
S2a/S2b PMIP
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 44 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 45 ETSI TS 132 423 V11.6.0 (2013-10)
TS
3GPP AAA Server Name AAA M M
29.273
S2c DSMIP
TS
Bearer-Identifier CCR M M
29.212
TS
Bearer-Operation CCR M M
29.212
TS
IP-CAN-Type CCR M M
29.212
TS
RAT-Type CCR M M
29.212
CCR
TS
QoS-Information CCA M M
29.212
RAR
TS
QoS-Negotiation CCR M M
29.212
TS
Gx Diameter QoS-Upgrade CCR M M
29.212
CCR
TS
Default-EPS-Bearer-QoS CCA M M
29.212
RAR
CCR
CCA TS
Supported-Features M M
RAR 29.212
RAA
CCR
CCA TS
Event-Trigger M M
RAR 29.212
TS
Result Code RAA M M
29.212
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 46 ETSI TS 132 423 V11.6.0 (2013-10)
CCR
CCA TS
Origin-Realm M M
RAR 29.212
RAA
CCR TS
Destination-Realm M M
RAR 29.212
SGi
The trace record is the same for management based activation and for signalling based activation.
MME shall support at least one of the following trace depth levels – Maximum, Medium or Minimum.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 47 ETSI TS 132 423 V11.6.0 (2013-10)
M M O Message name
O O O Record extensions
HSS ID of the connected HSS
Decoded M M X
S6a MME ID of the traced MME
Dedicated IE extracted from S6a messages between the traced HSS and the MME. A subset of IEs as given in the
M M X
table [Link] provided
Encoded * X X M Raw S6a messages between the traced HSS and the MME. The encoded content of the message is provided
M M O Message name
O O O Record extensions
MME ID of the connected MME
Decoded M M X
S10 MME ID of the traced MME
Dedicated IE extracted from S10 messages between the traced MME and another MME. A subset of IEs as given in
M M X
the table [Link] provided
Encoded * X X M Raw S10 messages between the traced MME and another MME. The encoded content of the message is provided
Encoded* - the messages are left encoded in the format it was received.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 48 ETSI TS 132 423 V11.6.0 (2013-10)
Table 4.12.2 : MME trace record description for minimum and medium trace depth
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 49 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 50 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 51 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 52 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 53 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 54 ETSI TS 132 423 V11.6.0 (2013-10)
NOTE: For the security keys in IEs or part of IEs that are containing security keys used by the eNB (e.g. KeNB), the value 0 shall be written in the trace file.
Definitions:
Global eNBID of traced eNB: The id of the eNB traced, e.g. the eNB which handles the connection of the traced MS, during the Trace Recording Session. The id
corresponds to the 'Global eNB ID', as defined in [16] and [17].
Global eNBID of neighbouring eNB: The ids of all Neighbouring eNB involved in the X2 procedures during the Trace Recording Session. The id corresponds to the
'Global eNB ID', as defined in [16] and [17].
cell Id: The cell Ids of the cells involved in the X2 procedures during the Trace Recording Session. The cell Ids is provided with each X2AP messages for which
the cId is relevant.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 55 ETSI TS 132 423 V11.6.0 (2013-10)
Decoded: Some IEs shall be decoded (cf. detailed list in table 4.6.2. depending on trace depth)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 56 ETSI TS 132 423 V11.6.0 (2013-10)
Table 4.13.2 : trace record description for minimum and medium trace depth
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 57 ETSI TS 132 423 V11.6.0 (2013-10)
HANDOVER REQUIRED
Handover Type HANDOVER COMMAND M M TS 36.413
HANDOVER REQUEST
HANDOVER NOTIFY
PATH SWITCH REQUEST
E-UTRAN CGI CM CM TS 36.413
INITIAL UE MESSAGE
UPLINK NAS TRANSPORT
HANDOVER NOTIFY
TAI PATH SWITCH REQUEST M M TS 36.413
UPLINK NAS TRANSPORT
Target ID HANDOVER REQUIRED M M TS 36.413
CDMA2000 HO Status DOWNLINK S1 CDMA2000 TUNNELING M M TS 36.413
DOWNLINK S1 CDMA2000 TUNNELING
CDMA2000 RAT Type M M TS 36.413
UPLINK S1 CDMA2000 TUNNELING
CDMA2000 Sector ID UPLINK S1 CDMA2000 TUNNELING M M TS 36.413
CDMA2000 HO Required Indication UPLINK S1 CDMA2000 TUNNELING M M TS 36.413
E-RAB id All messages where it is present M M TS 36.423
E-RAB Level QoS HANDOVER REQUEST M M TS 36.423
HANDOVER REQUEST
Cause HANDOVER PREPARATION FAILURE M M TS 36.423
HANDOVER CANCEL
X2 X2AP
Target Cell ID HANDOVER REQUEST M M TS 36.423
GUMMEI HANDOVER REQUEST M M TS 36.423
UE History Information HANDOVER REQUEST M M TS 36.423
UE RLF Report Container RLF INDICATION X M TS 36.423
Constraints:
The condition for capturing the following Information Element is that Cell Traffic Trace is used:
• E-UTRAN CGI from S1 interface from the following messages: Initial UE message, Handover Notify
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 58 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 59 ETSI TS 132 423 V11.6.0 (2013-10)
The trace record is the same for management based activation and for signalling based activation.
SGW shall support at least one of the following trace depth levels – Maximum, Medium or Minimum.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 60 ETSI TS 132 423 V11.6.0 (2013-10)
Table 4.14.2 : SGW trace record description for minimum and medium trace depth
Trace
Prot.
Interface name IE name Message name(s) depth Notes
name
Min Med
Create Session Request
Suspend Notification
TS
IMSI Suspend Acknowledge M M
29.274
Resume Notification
Resume Acknowledge
Create Session Request TS
MSISDN M M
Modify Bearer Response 29.274
Create Session Request TS
RAT type M M
Modify Bearer Request 29.274
Create Session Request TS
Serving Network M M
Modify Bearer Request 29.274
TS
Access Point Name (APN) Create Session Request M M
29.274
TS
PDN Type Create Session Request M M
29.274
Create Session Request
Create Bearer Request
Create Bearer Response
Delete Bearer Request
Delete Bearer Response
Modify Bearer Command
Modify Bearer Failure Indication
Update Bearer Request TS
Bearer Contexts M M
Update Bearer Response 29.274
Delete Bearer Command
Delete Bearer Failure Indication
Create Indirect Data Forwarding
Tunnel Request
Create Indirect Data Forwarding
S11 GTPv2C Tunnel Response
Update Bearer Complete
Create Session Response
Create Bearer Response
Bearer Resource Failure Indication
Modify Bearer Response
Delete Session Response
Downlink Data Notification
Acknowledgement
TS
Cause Downlink Data Notification Failure M M
29.274
Indication
Modify Bearer Failure Indication
Update Bearer Response
Delete Bearer Failure Indication
Create Indirect Data Forwarding
Tunnel Response
Update Bearer Complete
TS
Bearer Contexts created Create Session Response M M
29.274
TS
APN Restriction Create Session Response M M
29.274
Create Bearer Request
Bearer Resource Command
Linked Bearer Identity TS
Delete Session Request M M
29.274
(LBI)
Delete Bearer Request
Delete Bearer Response
Traffic Aggregate TS
Bearer Resource Command M M
29.274
Description (TAD)
TS
Linked EPS Bearer ID Bearer Resource Command M M
29.274
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 61 ETSI TS 132 423 V11.6.0 (2013-10)
Bearer Contexts to be M M
TS
Modify Bearer Request 29.274
removed
Bearer Contexts TS
Modify Bearer Response M M
29.274
modified
Bearer Contexts marked Modify Bearer Response TS
M M
for removal Update User Plane Response 29.274
Bearer Contexts to be M M
TS
Update User Plane Request 29.274
updated
Bearer Contexts to be TS
Update User Plane Request M M
29.274
removed
TS
Bearer Contexts updated Update User Plane Response M M
29.274
Bearer Contexts to be TS
Modify Bearer Request M M
29.274
modified
Traffic Aggregate TS
Bearer Resource Command M M
29.274
Description (TAD)
Bearer Resource Command
Linked Bearer Identity TS
Create Bearer Request M M
29.274
(LBI)
Delete Bearer Response
Bearer Resource Failure Indication
TS
Linked EPS Bearer ID Delete Session Request M M
29.274
Delete Bearer Request
Bearer Resource Failure Indication
Create Session Response
Create Bearer Response
Modify Bearer Response
Delete Session Response
Delete Bearer Response
Downlink Data Notification TS
Cause M M
29.274
Acknowledgement
Downlink Data Notification Failure
Indication
Update Bearer Response
Create Indirect Data Forwarding
Tunnel Response
Update Bearer Complete
Bearer Contexts to be TS
Modify Bearer Request M M
29.274
modified
Bearer Contexts to be TS
Modify Bearer Request M M
29.274
removed
S4 GTPv2C Create Session Request TS
IMSI M M
Update Bearer Request 29.274
Create Session Request TS
MSISDN M M
Modify Bearer Response 29.274
TS
Serving Network Create Session Request M M
29.274
TS
Access Point Name (APN) Create Session Request M M
29.274
TS
PDN Type Create Session Request M M
29.274
Create Session Request
Create Bearer Request
Create Bearer Response
Delete Bearer Request
Delete Bearer Response
Update Bearer Request TS
Bearer Contexts M M
Update Bearer Response 29.274
Create Indirect Data Forwarding
Tunnel Request
Create Indirect Data Forwarding
Tunnel Response
Update Bearer Complete
Create Session Request TS
RAT Type M M
29.274
Modify Bearer Request
TS
Bearer Contexts created Create Session Response M M
29.274
Bearer Contexts marked TS
Create Session Response M M
29.274
for removal
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 62 ETSI TS 132 423 V11.6.0 (2013-10)
Bearer Contexts M M
TS
Modify Bearer Response 29.274
modified
Bearer Contexts marked TS
Modify Bearer Response M M
29.274
for removal
Create Session Request TS
IMSI M M
Update Bearer Request 29.274
Create Session Request M M
TS
MSISDN
Modify Bearer Response 29.274
Create Session Request TS
Serving Network M M
Modify Bearer Request 29.274
TS
Access Point Name (APN) Create Session Request M M
29.274
TS
PDN Type Create Session Request M M
29.274
Create Session Request
Create Bearer Request
Create Bearer Response
Delete Bearer Request
Delete Bearer Response
TS
Bearer Contexts Modify Bearer Command M M
29.274
Modify Bearer Failure Indication
Update Bearer Request
Update Bearer Response
Delete Bearer Command
Delete Bearer Failure Indication
Create Session Response
Create Bearer Response
Bearer Resource Failure Indication
Modify Bearer Response
TS
Cause Delete Session Response M M
29.274
Delete Bearer Response
S5/S8 GTPv2C
Modify Bearer Failure Indication
Update Bearer Response
Delete Bearer Failure Indication
TS
Bearer Contexts created Create Session Response M M
29.274
Bearer Contexts marked TS
Create Session Response M M
for removal 29.274
TS
APN Restriction Create Session Response M M
29.274
Create Bearer Request
Linked Bearer Identity TS
Bearer Resource Command M M
29.274
(LBI)
Delete Bearer Response
Traffic Aggregate M M
TS
Bearer Resource Command 29.274
Description (TAD)
Linked EPS Bearer ID Bearer Resource Failure Indication
TS
Delete Session Request M M
29.274
Delete Bearer Request
Create Session Request TS
RAT Type M M
29.274
Modify Bearer Request
Bearer Contexts to be TS
Modify Bearer Request M M
29.274
modified
Bearer Contexts to be TS
Modify Bearer Request M M
29.274
removed
Bearer Contexts TS
M M
modified 29.274
Bearer Contexts marked TS
M M
for removal 29.274
TS
IP-CAN-Type CCR M M
29.212
TS
RAT-Type CCR M M
29.212
CCR
TS
Gxc Diameter QoS-Information CCA M M
29.212
RAR
TS
QoS-Negotiation CCR M M
29.212
CCR TS
QoS-Rule-Report M M
29.212
RAA
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 63 ETSI TS 132 423 V11.6.0 (2013-10)
CCR
Default-EPS-Bearer- TS
CCA M M
29.212
QoS
RAR
CCR
CCA TS
Supported-Features M M
29.212
RAR
RAA
CCR
CCA TS
Event-Trigger M M
29.212
RAR
TS
Result Code RAA M M
29.212
CCR
CCA TS
Origin-Realm M M
RAR 29.212
RAA
RAR TS
QoS-Rule-Remove M M
29.212
CAA
RAR TS
QoS-Rule-Install M M
29.212
CAA
CCR TS
Destination-Realm M M
29.212
RAR
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 64 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 65 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 66 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 67 ETSI TS 132 423 V11.6.0 (2013-10)
Annex A (normative):
Trace Report File Format
This annex describes the format of trace or MDT result files. Those files are to be transferred from the network (NEs or
EM) to the NM.
The following conditions have been considered for the definition of this file format:
- The trace data volume and trace duration is not predictable. Depending on the data retrieval and storage
mechanisms, several consecutive trace result files could be generated for a single traced call. The file naming
convention shall allow rebuilding the temporal file sequences.
- Since the files are transferred via a machine-machine interface, the files should be machine-readable using
standard tools.
- The file format should be independent from the data transfer protocol used to carry the file from one system to
another.
- The file format should be generic across UMTS and EPS systems.
- The file format should be flexible enough to support further trace data types and decoded IEs, as well as vendor
specific trace data.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 68 ETSI TS 132 423 V11.6.0 (2013-10)
- MNC is in BCD format, 1 to 3 digits in length, with no filler digit for MNCs less than 3 digits
(element specification "MNC")
traceRecSession Attribute specification that provides a unique trace recording session identifier as described in
traceRecSessionRef 3GPP TS 32.421 [2] and 3GPP TS 32.422 [3]. Trace Recording Session Reference is represented in
hexadecimal format. No filler digits for hex numbers of less than four digits. All hex letters (A thru F) are
capitalized.
traceRecSession stime Optional attribute specification that provides the start time of the call.
ue This element gives the ue identifier provided in trace activation messages. It includes:
- the ue identifier type (attribute specification "idType")
- the ue identifier value (attribute specification "idValue")
This element shall not be present in the Trace record of E-UTRAN.
ue idType Attribute specification that provides the ue identifier type (IMSI, IMEI (SV), TAC, or Public User
Identity). For management based MDT, IMSI or IMEI(SV) can not be selected as ue idType.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 69 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 70 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 71 ETSI TS 132 423 V11.6.0 (2013-10)
NOTE: In case a trace only recording session, the elements/attributes (such as "meas") which are specific to MDT
but not used for trace should be excluded from the file; In case a MDT only recording session, the
elements/attributes (such as "msg") which are specific to trace but not used for MDT should be excluded
from the file: In case of a combined trace and MDT recording session, all the elements/attributes are
included in the file.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 72 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 73 ETSI TS 132 423 V11.6.0 (2013-10)
<extension base="string">
<attribute name="type" type="NCName"
use="optional"/>
</extension>
</simpleContent>
</complexType>
</element>
<element name="rawMsg" minOccurs="0">
<complexType>
<simpleContent>
<extension base="hexBinary">
<attribute name="protocol" type="string"
use="required"/>
<attribute name="version" type="string"
use="required"/>
<attribute name="NumOfTargets" type="integer"
use="optional"/>
</extension>
</simpleContent>
</complexType>
</element>
<choice minOccurs="0" maxOccurs="unbounded">
<element ref="td:ie"/>
<element ref="td:ieGroup"/>
</choice>
</sequence>
<attribute name="function" type="string" use="required"/>
<attribute name="name" type="string" use="required"/>
<attribute name="changeTime" type="float" use="required"/>
<attribute name="vendorSpecific" type="boolean" use="required"/>
</complexType>
</element>
<!-- Element specific to MDT data file -->
<element name="meas" minOccurs="0" maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension base="string">
<attribute name="name" type="string" use="required"/>
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 74 ETSI TS 132 423 V11.6.0 (2013-10)
</schema>
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 75 ETSI TS 132 423 V11.6.0 (2013-10)
Annex B (normative):
Trace Report File Conventions and Transfer Procedure
This annex describes naming conventions of files containing trace results and the procedure to transfer these files from
the network to the NM.
<Type><Startdate>.<Starttime>-<SenderType>.<SenderName>.[<TraceReference>].[<TraceRecordingSessionRef>]
1) The Type field indicates if the file contains trace data for single or multiple calls, where:
2) The Startdate field indicates the date of the first record in the trace file. The Startdate field is of the form
YYYYMMDD, where:
3) The Starttime field indicates the time of the first record in the trace file. The Starttime field is of the form
HHMMshhmm, where:
- HH is the two digit hour of the day (local time), based on 24 hour clock (00 - 23);
- MM is the two digit minute of the hour (local time),
- s is the sign of the local time differential from UTC (+ or -), in case the time differential to UTC is 0 then the
sign may be arbitrarily set to "+" or "-";
- hh is the two digit number of hours of the local time differential from UTC (00-23);
- mm is the two digit number of minutes of the local time differential from UTC (00-59).
4) SenderType field is the type of NE defined by IOC attribute managedElementType in 3GPP TS 32.622 [12] that
recorded and sent the trace file; SenderName field is the identifier of the NE that recorded and sent the trace file.
5) TraceRecordingSessionReference field is set only if the type field is A, and is represented in hexa-decimal
format. TraceRecordingSessionReference is a 4 digit hexadecimal number and will not include filler digits for
values less than 4 digits in length. All hexadecimal letters (A thru F) are capitalized.
6) TraceReference field is set if the type field is A. For type B the Trace Reference is optional and will be used
when one trace file is created per trace session with multiple trace recording session. Trace Reference is
represented in hexadecimal format. Trace Reference as defined in 3GPP TS 32.422 [3] is composed of PLMN ID
(MCC, MNC) and Trace ID. The PLMN identity consists of 3 digits for MCC followed by either - a filler digit
plus 2 digits from MNC (in case of 2 digit MNC) or 3 digits from MNC (in case of a 3 digit MNC). MCC and
MNC are in BCD format.
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 76 ETSI TS 132 423 V11.6.0 (2013-10)
See bullet 6 above for details regarding the representation of the Trace [Link] examples describing file
naming convention:
meaning: file produced by MME< MME5> on September 28, 2009, first trace record at 23:15 local with a time
differential of +2 hours against UTC. The file contains trace data for the Trace Session with the Trace reference
13F232000056 (where MCC is 312, MNC is 23, and Trace ID is 000056, all in hexadecimal format) and for the
Trace Recording Session with the reference 125.
meaning: file produced by RNC<RNC02> on January 15, 2003, first trace record at 17:00 local with a time
differential of -3 hours against UTC. The file contains trace data for several Trace Recording Sessions.
meaning: file produced by RNC<RNC02> on January 15, 2003, first trace record at 17:00 local with a time
differential of -3 hours against UTC. The file contains trace 4358070034D7 (where MCC is 348, MNC is 570,
and Trace ID is 0034D7) data for Trace reference and several Trace Recording Sessions.
Meaning: file produced by MME<MME02> on January 15, 2003, first trace record at 17:00 local with a time
differential of -3 hours against UTC. The file contains IMSI/IMEI (SV) or IMEI-TAC information for one or
more UEs traced at eNB with Trace Reference26F452550021 (where MCC is 624, MNC is 25, and Trace ID is
550021).
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 77 ETSI TS 132 423 V11.6.0 (2013-10)
Annex C (informative):
Trace Functional Architecture: Reporting
OSS/NM/TCE
HSS
EMx EMy
MSC Server
MGW
SGSN
S-CSCF P-CSCF GGSN
RNC
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 78 ETSI TS 132 423 V11.6.0 (2013-10)
OSS/NM/TCE EM
HSS
EM
MSC Server
EM
MGW
EM
EM EM
SGSN
S-CSCF P-CSCF EM
EM
GGSN
RNC
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 79 ETSI TS 132 423 V11.6.0 (2013-10)
Annex D (informative):
Examples of trace files
D.1.1 Example of XML trace file with the maximum level of details
<?xml version="1.0" encoding="UTF-8"?>
<traceCollecFile xmlns="[Link]
xmlns:xsi="[Link]
xsi:schemaLocation="[Link]
[Link]
<fileHeader fileFormatVersion="32.423 V6.0" vendorName="Company NN">
<fileSender elementDn="DC=[Link],SubNetwork=1, ManagedElement=RNC-1"
elementType="RNC"/>
<traceCollec beginTime="2001-09-11T[Link]-05:00"/>
</fileHeader>
<traceRecSession dnPrefix="DC=[Link],SubNetwork=1" traceRecSessionRef="1" stime="2001-
09-11T[Link]-05:00">
<ue idType="IMSI" idValue="32795"/>
<msg function="Iub" name="Radio LinkSetup Request" changeTime="0.005"
vendorSpecific="false">
<target type="Cell">SubNetwork=1,ManagedElement=Cell-1</target>
<rawMsg protocol="Nbap" version="001">A9FD64E12C</rawMsg>
</msg>
<traceSessionRef>
<MCC>460</MCC>
<MNC>10</MNC>
<TRACE_ID>000122</TRACE_ID>
</traceSessionRef>
</traceRecSession>
</traceCollecFile>
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 80 ETSI TS 132 423 V11.6.0 (2013-10)
D.1.2 Example of XML trace file with the minimum level of details
<?xml version="1.0" encoding="UTF-8"?>
<traceCollecFile xmlns="[Link]
xmlns:xsi="[Link]
xsi:schemaLocation="[Link]
[Link]
<fileHeader fileFormatVersion="32.423 V6.0" vendorName="Company NN">
<fileSender elementDn="DC=[Link],SubNetwork=1, ManagedElement=RNC-1"
elementType="RNC"/>
<traceCollec beginTime="2001-09-11T[Link]-05:00"/>
</fileHeader>
<traceRecSession dnPrefix="DC=[Link],SubNetwork=1" traceRecSessionRef="1" stime="2001-
09-11T[Link]-05:00">
<ue idType="IMSI" idValue="32795"/>
<msg function="Iub" name="Radio Link Setup Request" changeTime="0.005"
vendorSpecific="false">
<target type="Cell">SubNetwork=1,ManagedElement=Cell-1</target>
<ie name="UL Scrambling Code">54</ie>
<ie name="UL SIR Target">17.3</ie>
<ie name="Min UL Channelisation Code Length">8</ie>
<ie name="Poncture Limit">2</ie>
<ieGroup name="RadioLink" value="1">
<ie name="DL Scrambling Code">1</ie>
<ie name="DL Channelisation Code Number">15</ie>
<ie name="Maximum DL Power">9.3</ie>
<ie name="Minimum DL Power">-10.1</ie>
</ieGroup>
</msg>
<msg function="IuPs" name="RAB Assignment Response" changeTime="0.010"
vendorSpecific="false">
<ieGroup name="RAB" value="1">
<ieGroup name="RAB Failed To Setup Or Modify">
<ie name="cause">2</ie>
</ieGroup>
</ieGroup>
</msg>
<traceSessionRef>
<MCC>460</MCC>
<MNC>10</MNC>
<TRACE_ID>000130</TRACE_ID>
</traceSessionRef>
</traceRecSession>
</traceCollecFile>
D.1.3 Example of XML trace file for IMSI information from the MME
<?xml version="1.0" encoding="UTF-8"?>
<traceCollecFile xmlns=[Link]
xmlns:xsi="[Link]
xsi:schemaLocation="[Link]
[Link]
<fileHeader fileFormatVersion="32.423 V8.0" vendorName="Company NN">
<fileSender elementDn="DC=[Link],SubNetwork=1, ManagedElement=MME"
elementType="MME"/>
<traceCollec beginTime="2001-09-11T[Link]-05:00"/>
</fileHeader>
<traceRecSession dnPrefix="DC=[Link],SubNetwork=1" traceRecSessionRef="1" stime="2001-09-
11T[Link]-05:00">
<ue idType="IMSI" idValue="32795"/>
<traceSessionRef>
<MCC>460</MCC>
<MNC>10</MNC>
<TRACE_ID>000130</TRACE_ID>
</traceSessionRef>
</traceRecSession>
<traceRecSession dnPrefix="DC=[Link],SubNetwork=1" traceRecSessionRef="2" stime="2001-09-
11T[Link]-05:00">
<ue idType="IMSI" idValue="12345"/>
<traceSessionRef>
<MCC>460</MCC>
<MNC>10</MNC>
<TRACE_ID>000150</TRACE_ID>
</traceSessionRef>
</traceRecSession>
</traceCollecFile>
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 81 ETSI TS 132 423 V11.6.0 (2013-10)
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 82 ETSI TS 132 423 V11.6.0 (2013-10)
Annex E (informative):
Void
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 83 ETSI TS 132 423 V11.6.0 (2013-10)
Annex F (informative):
Change history
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Cat Old New
Sep 2005 SA_29 SP-050623 0004 1 Clarify Trace Messages for FDD and TDD modes B 6.2.0 7.0.0
Dec 2005 SA_30 SP-050690 0007 -- Differentiate Trace Contents for FDD and TDD B 7.0.0 7.1.0
Dec 2005 SA_30 SP-050709 0008 -- Remove SFN-SFN observed time difference - Align with 25.331 A 7.0.0 7.1.0
Dec 2005 SA_30 SP-050709 0009 -- Correction to name space URI A 7.0.0 7.1.0
Jun 2006 SA_32 SP-060258 0011 -- Correction for compilation errors of schema and addition of the missing link A 7.1.0 7.2.0
Sep 2006 SA_33 SP-060533 0013 -- Correct UTRA Carrier RSSI for trace contents- Align with RAN2's 25.331 A 7.2.0 7.3.0
Sep 2006 SA_33 SP-060533 0015 -- Correct CFN-SFN observed time difference for trace IE - Align with RAN2's A 7.2.0 7.3.0
25.331
Sep 2006 SA_33 SP-060552 0016 -- Add Trace IEs to differentiate UARFCN for FDD and TDD - Align with RAN2's C 7.2.0 7.3.0
25.331
Sep 2006 SA_33 SP-060552 0018 -- Correction in XML schema and examples F 7.2.0 7.3.0
Dec 2006 SA_34 SP-060728 0019 -- Correct the errors in figure and examples F 7.3.0 7.4.0
Mar 2009 SA_43 SP-090207 0020 -- Constraint of the presence for the "ue" element F 7.4.0 8.0.0
Mar 2009 SA_43 SP-090207 0021 -- Adding PGW trace record content B 7.4.0 8.0.0
Mar 2009 SA_43 SP-090207 0022 -- Alignment with 32.421 and 32.422. Introduction medium and minimum trace B 7.4.0 8.0.0
dept IEs for the GTP and S1AP protcols in MME
Mar 2009 SA_43 SP-090207 0023 -- Alignment with 32.421 and 32.422. Introduction of E-UTRAN B 7.4.0 8.0.0
Jun 2009 SA_44 SP-090289 0024 -- Alignment with 32.421 and 32.422 - Introduction medium and minimum trace F 8.0.0 8.1.0
depth IEs in MME.
Jun 2009 SA_44 SP-090289 0025 -- Add missing SGW Trace Record content F 8.0.0 8.1.0
Jun 2009 SA_44 SP-090289 0026 -- Add missing PGW Trace Record content for Gx and S6b interfaces F 8.0.0 8.1.0
Jun 2009 SA_44 SP-090289 0027 -- Alignment with 32.421 and 32.422 - Introduction medium and minimum trace F 8.0.0 8.1.0
dept IEs for NAS in MME.
Sep 2009 SA_45 SP-090534 0028 -- Correction in TS 32.423 Trace Depth requirements for MME, SGW and PGW F 8.1.0 8.2.0
Sep 2009 SA_45 SP-090534 0030 -- Unable to uniquely identify file name when one file per UE trace F 8.1.0 8.2.0
Sep 2009 SA_45 SP-090534 Added a file format and example for sending the IMSI/IMEI (SV) information
0031 -- from the MME F 8.1.0 8.2.0
Sep 2009 SA-45 SP-090542 0029 -- Correction on XML file format for Trace failure notification F 8.2.0 9.0.0
Dec 2009 SA-46 SP-090719 0032 -- Clarify Trace Reference and Trace Recording Session Reference format F 9.0.0 9.1.0
Jan 2010 -- -- -- -- Removal of track changes -- 9.1.0 9.1.1
Mar 2010 SA-47 SP-100034 0034 -- Align with 32.421 and 33.401 A 9.1.1 9.2.0
Sep 2010 SA-49 SP-100487 0039 -- Correcting references A 9.2.0 9.3.0
Sep 2010 SA-49 SP-100489 0036 -- Add Diameter in HSS Trace Record Content B 9.2.0 9.3.0
Sep 2010 SA-49 SP-100488 0035 -- Correct call trace file format to allow multiple targets F 9.3.0 10.0.0
Dec 2010 SA-50 SP-100833 Add trace Record Content in MME trace and SGSN trace - Align with 32.421
0040 1 and 32.422 C 10.0.0 10.1.0
Dec 2010 SA-50 SP-100858 Correcting the Trace Reference definition - Align with RAN3 TS 36.423,
0042 -- 36.413 A 10.0.0 10.1.0
Dec 2010 SA-50 SP-100833 0043 -- Adding the S6a trace interface for HSS B 10.0.0 10.1.0
Dec 2010 SA-50 SP-100833 0044 -- Correcting the Identification of IMS Subscriber Tracing - Align with 32.421 F 10.0.0 10.1.0
Dec 2010 SA-50 SP-100831 Add missing interfaces S3, S4 and S6d trace record contents of SGSN - Align
0047 -- with 32.422 A 10.0.0 10.1.0
Mar 2011 SA-51 SP-110095 0049 - Addition of trace Record Content of EIR Trace B 10.1.0 10.2.0
May 2011 SA-52 SP-110292 0050 1 Applying trace data file to MDT data format B 10.2.0 10.3.0
Dec 2011 SA-54 SP-110715 Correcting the description of meas vendorSpecific attribute in the XML trace
0054 -- file F 10.3.0 10.4.0
Dec 2011 SA-54 SP-110716 0047 Clarification of eNB ID in E-UTRAN Trace Record B 10.4.0 11.0.0
Dec 2011 SA-54 SP-110716 0053 -- Rel11 CR to 32423 Update the trace record content for Uu and X2 interfaces C 10.4.0 11.0.0
March SA55 SP-120053
2012 0058 1 Correct IMSI retrieval file to include MDT anonymization info A 11.0.0 11.1.0
March SA-55 SP-120044
2012 0061 1 Modify E-UTRAN Trace Record Content A 11.0.0 11.1.0
Sep-2012 SA-57 SP-120627 0064 1 Reference list correction to align with the corrected TS 29.212 title F 11.1.0 11.2.0
SP-120783 Correction of inconsistent specification of data type for Trace Recording
0065 1 Session Reference Length (TRSR) F
Dic-2012 SA-58 SP-120796 0066 1 Specifying trace record content for immediate MDT measurements B 11.2.0 11.3.0
SP-120796 0067 - Add RCEF in Uu interface trace C
SP-120795 0068 1 Correction on the scope and reference related to MDT F
Mar-2013 SA-59 SP-130057 0069 - RCEF reporting in UMTS F 11.3.0 11.4.0
June- SP-130265 0072 1 Correct trace file name format A
SA-60 11.4.0 11.5.0
2013 SP-130304 0073 2 Correct the XML shcema for MDT data F
Sep-2013 SA-61 SP-130432 0075 2 Correction on some inconsistent definitons for trace data file parameters A 11.5.0 11.6.0
ETSI
3GPP TS 32.423 version 11.6.0 Release 11 84 ETSI TS 132 423 V11.6.0 (2013-10)
History
Document history
V11.2.0 September 2012 Publication
ETSI