4.33 ng-eNB Trace Record Content

32.4233GPPRelease 16Subscriber and equipment traceTelecommunication managementTrace data definition and managementTS

The following table shows the trace record content for ng-eNB network element

The trace record is the same for management based activation and for signalling based activation.

ng-eNB shall support at least one of the following trace depth levels – Maximum, Medium or Minimum.

Table 4.33.1 : ng-eNB 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 ng-eNB node

O

O

X

IE extracted from RRC messages between the traced ng-eNB node and the UE as per 3GPP TS 36.331 [28]

Encoded*

X

X

M

Raw Uu Messages: RRC messages between the traced ng-eNB 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 ng-eNB node
AMF ID of the connected AMF

O

O

X

IE extracted from NGAP messages between the traced ng-eNB node and Core Network as per 3GPP TS 38.413 [23]

Encoded*

X

X

M

Raw NG-C Messages NGAP: messages between the traced ng-eNB 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 ng-eNB node
ID of neighbouring NG-RAN node (i.e. ng-eNB or gNB)

O

O

X

IE extracted from XnAP messages between the traced ng-eNB and the neighbouring NG-RAN node as per 3GPP TS 38.423 [24]

Encoded*

X

X

M

Raw Xn-C Messages: XnAP messages between the traced ng-eNB node and the neighbouring NG-RAN node. The encoded content of the message is provided

Encoded* – the messages are left encoded in the format it was received.