8.4 Trace Procedures

38.4633GPPE1 Application Protocol (E1AP)NG-RANRelease 16TS

8.4.1 Trace Start

8.4.1.1 General

The purpose of the Trace Start procedure is to allow the gNB-CU-CP to request the gNB-CU-UP to initiate a trace session for a UE. The procedure uses UE-associated signalling.

8.4.1.2 Successful Operation

Figure 8.4.1.2-1: Trace start procedure: Successful Operation.

Upon reception of the TRACE START message, the gNB-CU-UP shall initiate the requested trace session for the requested UE, as described in TS 32.422 [24]. In particular, the gNB-CU-UP shall, if supported:

– if the MDT Activation IE is set to "Immediate MDT Only", initiate the requested MDT session as described in TS 32.422 [24] and the gNB-CU-UP shall ignore Interfaces To Trace IE, and Trace Depth IE.

8.4.1.3 Abnormal Conditions

Void.

8.4.2 Deactivate Trace

8.4.2.1 General

The purpose of the Deactivate Trace procedure is to allow the gNB-CU-CP to request the gNB-CU-UP to stop the trace session for the indicated trace reference. The procedure uses UE-associated signalling.

8.4.2.2 Successful Operation

Figure 8.4.2.2-1: Deactivate trace procedure: Successful Operation.

Upon reception of the DEACTIVATE TRACE message, the gNB-CU-UP shall stop the trace session for the indicated trace reference contained in the Trace ID IE, as described in TS 32.422 [24].

8.4.2.3 Abnormal Conditions

Void.

8.4.3 Cell Traffic Trace

8.4.3.1 General

The purpose of the Cell Traffic Trace procedure is to send the allocated Trace Recording Session Reference and the Trace Reference to the gNB-CU-CP. The procedure uses UE-associated signalling.

8.4.3.2 Successful Operation

Figure 8.4.3.2-1: Cell Traffic Trace procedure. Successful operation.

The procedure is initiated with a CELL TRAFFIC TRACE message sent from the gNB-CU-UP to the gNB-CU-CP.

If the Privacy Indicator IE is included in the message, the gNB-CU-CP shall store the information so that it can be transferred towards the AMF.

8.4.3.3 Abnormal Conditions

Void.