Section: 8.31 Trace Information
Content: Trace Information is coded as depicted in Figure 8.31-1. See 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ]  [18] for details on trace related information. 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[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ]  [18]. Triggering Events shall be encoded as the first 9 octets in clause 5.1 of 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ]  [18]. List of NE Types, Session Trace Depth and IP Address of Trace Collection Entity are specified in 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ]  [18]. List of Interfaces shall be encoded as the first 12 octets in clause 5.5 of 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ]  [18]. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ]  [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.