4.18 AMF Trace Record Content
32.4233GPPRelease 16Subscriber and equipment traceTelecommunication managementTrace data definition and managementTS
The following table shows the trace record content for AMF.
The trace record is the same for management based activation and for signalling based activation.
AMF shall support at least one of the following trace depth levels – Maximum, Medium or Minimum.
Table 4.18.1 : AMF Trace Record Content
Interface (specific messages) |
Format |
Level of details |
Description |
||
Min |
Med |
Max |
|||
N1 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
ID of the connected gNB-CU-CP node/ng-eNB |
||
O |
O |
X |
IE extracted from N1 messages between the traced AMF and the gNB-CU-CP/ng-eNB node. |
||
ASN.1 |
X |
X |
M |
Raw Messages: N1 messages between the traced AMF and the gNB-CU-CP/ng-eNB node. The encoded content of the message is provided. |
|
N1 NAS PDU IE |
Encoded* |
X |
X |
M |
Hexdata dump of the decrypted NAS message formatted according to 3GPP TS 24.501 [x10], sections 8 and 9, recorded as a separate message entry in the call trace file |
N8 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
UDM ID of the connected UDM |
||
O |
O |
X |
IE extracted from N8 messages between the traced AMF and the UDM. |
||
Encoded* |
X |
X |
M |
Raw N8 messages between the traced AMF and the UDM. The encoded content of the message is provided |
|
N11 |
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 N11 messages between the traced AMF and the SMF. |
||
Encoded* |
X |
X |
M |
Raw N11 messages between the traced AMF and the SMF. The encoded content of the message is provided |
|
N12 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
AUSF ID of the connected AUSF |
||
O |
O |
X |
IE extracted from N12 messages between the traced AMF and AUSF. |
||
Encoded* |
X |
X |
M |
Raw N12 messages between the traced AMF and AUSF. The encoded content of the message is provided |
|
N14 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
AMF ID of the connected AMF |
||
O |
O |
X |
IE extracted from N14 messages between the traced AMF and another AMF. |
||
Encoded* |
X |
X |
M |
Raw N14 messages between the traced AMF and another AMF. The encoded content of the message is provided |
|
N15 |
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 N15 messages between the traced AMF and PCF. |
||
Encoded* |
X |
X |
M |
Raw N15 messages between the traced AMF and PCF. The encoded content of the message is provided |
|
N20 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
SMSF ID of the connected SMSF |
||
O |
O |
X |
IE extracted from N20 messages between the traced AMF and SMSF. |
||
Encoded* |
X |
X |
M |
Raw N20 messages between the traced AMF and SMSF. The encoded content of the message is provided |
|
N22 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
NSSF ID of the connected NSSF |
||
O |
O |
X |
IE extracted from N22 messages between the traced AMF and NSSF. |
||
Encoded* |
X |
X |
M |
Raw N22 messages between the traced AMF and NSSF. The encoded content of the message is provided |
|
N26 |
Decoded |
M |
M |
O |
Message name |
O |
O |
O |
Record extensions |
||
M |
M |
X |
MME ID of the connected MME |
||
O |
O |
X |
IE extracted from N26 messages between the traced AMF and MME. |
||
Encoded* |
X |
X |
M |
Raw N26 messages between the traced AMF and MME. The encoded content of the message is provided |
Encoded* – the messages are left encoded in the format it was received.