4.1 General

32.4233GPPRelease 16Subscriber and equipment traceTelecommunication managementTrace data definition and managementTS

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:

Interface name	Protocol name	IE name	Message name(s)	Trace depth		Notes
				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.