Content for TS 37.483 Word version: 17.3.0
8.4 Trace Procedures
8.4.1 Trace Start
8.4.2 Deactivate Trace
8.4.3 Cell Traffic Trace
8.5 IAB Procedures
8.5.1 IAB UP TNL Address Update
8.5.2 IAB PSK Notification
...
...
8.4 Trace Procedures p. 55
8.4.1 Trace Start p. 55
8.4.1.1 General p. 55
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 p. 55
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. 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 and the gNB-CU-UP shall ignore Interfaces To Trace IE, and Trace Depth IE.
8.4.1.3 Abnormal Conditions p. 55
Void.
8.4.2 Deactivate Trace p. 56
8.4.2.1 General p. 56
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 p. 56
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.
8.4.2.3 Abnormal Conditions p. 56
Void.
8.4.3 Cell Traffic Trace p. 56
8.4.3.1 General p. 56
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 p. 56
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 p. 57
Void.
8.5 IAB Procedures p. 57
8.5.1 IAB UP TNL Address Update p. 57
8.5.1.1 General p. 57
The purpose of the IAB UP TNL Address Update procedure is to allow the gNB-CU-CP to request the gNB-CU-UP to update the TNL Address(es) for all the DL F1-U GTP-U tunnels related to this (these) TNL address(es), and to allow the gNB-CU-UP to inform the gNB-CU-CP about the updated TNL Address(es) for all the UL F1-U GTP-U tunnels. The procedure uses non-UE associated signalling.
8.5.1.2 Successful Operation p. 57
The gNB-CU-CP initiates the procedure by sending the IAB UP TNL ADDRESS UPDATE message to the gNB-CU-UP. If the gNB-CU-UP succeeds to update the TNL Address(es), it replies to the gNB-CU-CP with the IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE message.
Upon reception of the IAB UP TNL ADDRESS UPDATE message, if the DL UP TNL Address to Update List IE is included therein, the gNB-CU-UP shall replace the old TNL Address(es) by the new TNL Address(es) for all the maintained DL F1-U GTP tunnels corresponding to the old TNL Address(es).
If the UL UP TNL Address to Update List IE is contained in the IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE message, the gNB-CU-CP shall consider the new TNL address(es) as replacement for the corresponding old TNL address(es).
8.5.1.3 Unsuccessful Operation p. 58
If the gNB-CU-UP receives an IAB UP TNL ADDRESS UPDATE message, but cannot perform the update accordingly, it shall consider the update procedure as failed and respond with an IAB UP TNL ADDRESS UPDATE FAILURE message and appropriate cause value.
If the IAB UP TNL ADDRESS UPDATE FAILURE message includes the Time To Wait IE, the gNB-CU-CP shall wait at least for the indicated amount of time before reinitiating the IAB UP TNL Address Update procedure towards the same gNB-CU-UP.
8.5.1.4 Abnormal Conditions p. 58
Not Applicable.
8.5.2 IAB PSK Notification p. 58
8.5.2.1 General p. 58
The purpose of the IAB PSK Notification procedure is to allow the gNB-CU-CP to send the security key info to the gNB-CU-UP, which will be used for the IKEv2 Pre-shared Secret Key (PSK) authentication to protect the F1-U interface of the IAB-node(s) as specified in TS 33.501. The procedure uses non-UE associated signalling.
8.5.2.2 Successful Operation p. 58
The gNB-CU-CP initiates the procedure by sending the IAB PSK NOTIFICATION message to the gNB-CU-UP.
The gNB-CU-UP uses the IAB-Donor-CU-UP PSK Info IE included in the IAB PSK NOTIFICATION message as specified in TS 33.501.
8.5.2.3 Abnormal Conditions p. 59
Not applicable.
