4.30 gNB-CU-CP Trace Record Content
32.4233GPPRelease 16Subscriber and equipment traceTelecommunication managementTrace data definition and managementTS
The following table shows the trace record content for gNB-CU-CP network element
The trace record is the same for management based activation and for signalling based activation.
gNB-CU-CP shall support at least one of the following trace depth levels – Maximum, Medium or Minimum.
Table 4.30.1 : gNB-CU-CP Trace Record Content
Interface (specific messages) |
Format |
Level of details |
Description |
||
Min |
Med |
Max |
|||
Uu |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
ID of traced gNB-CU-CP node |
||
O |
O |
X |
IE extracted from RRC messages between the traced gNB-CU-CP node and the UE as per 3GPP TS 38.331 [21] |
||
Encoded* |
X |
X |
M |
Raw Uu Messages: RRC messages between the traced gNB-CU-CP node and the UE. The encoded content of the message is provided |
|
NG-C |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
ID of traced gNB-CU-CP node |
||
O |
O |
X |
IE extracted from NGAP messages between the traced gNB-CU-CP node and Core Network as per 3GPP TS 38.413 [23] |
||
Encoded* |
X |
X |
M |
Raw NG-C Messages NGAP: messages between the traced gNB-CU-CP node and Core Network The encoded content of the message is provided |
|
Xn-C |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
ID of traced gNB-CU-CP node |
||
O |
O |
X |
IE extracted from XnAP messages between the traced gNB-CU-CP node and the neighbouring gNB-CU-CP/ng-eNB node as per 3GPP TS 38.423 [24] |
||
Encoded* |
X |
X |
M |
Raw Xn-C Messages: XnAP messages between the traced gNB-CU-CP node and the neighbouring gNB-CU-CP/ng-eNB node. The encoded content of the message is provided |
|
X2-C |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
ID of traced gNB-CU-CP node |
||
O |
O |
X |
IE extracted from EN-DC X2AP messages between the traced gNB-CU-CP node and the connected NSA eNB node as per 3GPP TS 36.423 [17] |
||
Encoded* |
X |
X |
M |
Raw EN-DC X2-C Messages: EN-DC X2AP messages between the traced gNB-CU-CP node and the connected NSA eNB node. The encoded content of the message is provided |
|
F1-C |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
ID of traced gNB-CU-CP |
||
O |
O |
X |
IE extracted from F1AP messages between the traced gNB-CU-CP and the gNB-DU as per 3GPP TS 38.473 [26] |
||
Encoded* |
X |
X |
M |
Raw F1-C Messages: F1AP messages between the traced gNB-CU-CP and the gNB-DU. The encoded content of the message is provided |
|
E1 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
ID of traced gNB-CU-CP |
||
O |
O |
X |
IE extracted from E1AP messages between the traced gNB-CU-CP and the gNB-CU-UP as per 3GPP TS 38.473 [26] |
||
Encoded* |
X |
X |
M |
Raw E1 Messages: E1AP messages between the traced gNB-CU-CP and the gNB-CU-UP. The encoded content of the message is provided |
Encoded* – the messages are left encoded in the format it was received.