8.31 Trace Information

29.2743GPP3GPP Evolved Packet System (EPS)Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)Release 18Stage 3TS

Trace Information is coded as depicted in Figure 8.31-1. See 3GPP TS 32.422 [18] for details on trace related information.

		Bits
	Octets	8	7	6	5	4	3	2	1
	1	Type = 96(decimal)
	2 to 3	Length = n
	4	Spare				Instance
	5	MCC digit 2				MCC digit 1
	6	MNC digit 3				MCC digit 3
	7	MNC digit 2				MNC digit 1
	8 to10	Trace ID
	11 to 19	Triggering Events
	20 to 21	List of NE Types
	22	Session Trace Depth
	23 to 34	List of Interfaces
	35 to (n+4)	IP Address of Trace Collection Entity

Figure 8.31-1: Trace Information

Octets 5 to 10 represent the Trace Reference parameter as defined in clause 5.6 of 3GPP TS 32.422 [18].

Triggering Events shall be encoded as the first 9 octets in clause 5.1 of 3GPP TS 32.422 [18].

List of NE Types, Session Trace Depth and IP Address of Trace Collection Entity are specified in 3GPP TS 32.422 [18].

List of Interfaces shall be encoded as the first 12 octets in clause 5.5 of 3GPP TS 32.422 [18].

See 3GPP TS 24.008 [5], clause 10.5.1.4, Mobile Identity, for the coding of MCC and MNC, whose values are obtained from the serving PLMN that the EM/NM is managing. If MNC is 2 digits long, bits 5 to 8 of octet 6 are coded as "1111".

NOTE: During a 5GS to EPS mobility, the MME derives the information to be sent in the Trace Information IE over S11 from the Extended Trace Information IE received from the AMF, if an SGW trace is activated; the PGW(+SMF) derives relevant trace information from the Trace Data that it received earlier (at the SMF), if a PGW trace is to be activated.