4.22 NEF Trace Record Content
32.4233GPPRelease 16Subscriber and equipment traceTelecommunication managementTrace data definition and managementTS
The following table shows the trace record content for NEF.
The trace record is the same for management based activation and for signalling based activation.
NEF shall support at least one of the following trace depth levels – Maximum, Medium or Minimum.
Table 4.22.1 : NEF Trace Record Content
Interface (specific messages) |
Format |
Level of details |
Description |
||
Min |
Med |
Max |
|||
N29 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
SMF ID of the connected SMF |
||
O |
O |
X |
IE extracted from N29 messages between the traced NEF and the SMF. |
||
Encoded* |
X |
X |
M |
Raw Messages: N29 messages between the traced NEF and the SMF. The encoded content of the message is provided. |
|
N30 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
PCF ID of the connected PCF |
||
O |
O |
X |
IE extracted from N30 messages between the traced NEF and PCF. |
||
Encoded* |
X |
X |
M |
Raw N30 Messages: messages between the traced NEF and PCF. The encoded content of the message is provided |
|
N33 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
AF ID of the connected AF |
||
O |
O |
X |
IE extracted from N33 messages between the traced NEF and AF. |
||
Encoded* |
X |
X |
M |
Raw N33 Messages: messages between the traced NEF and AF. The encoded content of the message is provided |
Encoded* – the messages are left encoded in the format it was received.