The Event Logging feature captures procedure-level information per subscriber. Upon completing a procedure, either successfully or unsuccessfully, the SMF generates event data records capturing the details of procedures and events.

The EDR generation per procedure is configurable. For configuration details, see the Configure EDR Files for Generation section in this guide.

The following table lists the supported procedures and the corresponding IDs.

Note	The procedure IDs remain the same for both roaming and non-roaming procedures.

Further, the SMF captures event-level information per procedure. The following table provides details on the subscriber events and the respective event IDs.

The events captured per procedure are configurable. For configuration details, see the Configure EDR Files for Generation section in this guide.

The following tables list the detailed event record for the PDU Session Create, Modify, and Delete procedures.

For details on the listed attributes, see the table in the EDR Transaction File section.

The following tables list the detailed event record for the SMF DEDICATED BEARER and SMF IDLE-MODE procedures.

NOTES:

• subscribed-sess-ambr-uplink and subscribed-sess-ambr-downlink: These fields are captured in the metadata event for some of the procedures. The values for these fields are printed as saved in pducontext. Bitrates in the metadata event are without any unit such as bps, kbps, or mbps. The default bitrate is read as bits per second (bps).

• Status: In event METADATA (id = 1000), this field indicates the status of the procedure. For other events, it indicates the type of received response message or intended outgoing response type. The status can be one of the following:

  • Success

  • Failed

  • PartialFailure

  • NoRspValidation: This status is used in case the request is sent in ASYNC (fire and forget) mode and the response is neither expected nor processed in SMF.

• Status-code: This field indicates HTTP status-code of the response message. This field should be empty for outgoing response messages as smf-service is unaware of the actual status-code filled by rest-ep. In such cases, the status field indicates the response type that SMF intended to send, such as success or failure response.

• Userplane-status is of type number. The number can be one of the following:

  • UpStateNone = 0

  • UpStateEstablishing = 1 // UPF Session is being established or setup

  • UpStateActivating = 2 // UPF Session is being modified to Activate Access Tunnel

  • UpStateActivated = 3 // UPF Session Active for Access & Core Tunnel

  • UpStateDeactivating = 4 // UPF Session is being modified to Deactivate Access Tunnel

  • UpStateDeactivated = 5 // UPF Session Deactivated for Access, valid Core Tunnel Only

  • UpStateModifying = 6 // UPF Session is being modified for QoS or flow parameters

  • UpStateDeleting = 7 // UPF Session is being Released

  • UpStateDeleted = 8 // UPF Session is Released

• PduSessionType is of type number. The number can be one of the following:

  • UnknownSessionType or Invalid = 0

  • Ipv4PduSession = 1

  • Ipv6PduSession = 2

  • Ipv4V6PduSession = 3

  • Unstrutured = 4

  • Ethernet = 5

  • FutureUsePduSessionType = 7

• SSC mode is of type number. The number can be one of the following:

  • UnknownSscMode = 0

  • SscMode1 = 1

  • SscMode2 = 2

  • SscMode3 = 3

  • DupSscMode1 = 4

  • DupSscMode2 = 5

  • DupSscMode3 = 6

  • FutureUseSscMode = 7

• Eps Iwk (Type: Number)

  • EpsInterworkingIndication_DummyEnum = 0

  • EpsInterworkingIndication_NONE = 1

  • EpsInterworkingIndication_WITH_N26 = 2

  • EpsInterworkingIndication_WITHOUT_N26 = 3

• Roaming status (Type: Number)

  • ROAMING_STATUS_NONE = 0

  • ROAMING_STATUS_HOMER =1 //HOMER

  • ROAMING_STATUS_VISITOR_LBO =2 //LBO

  • ROAMING_STATUS_VISITOR_HR = 3 //IN-HR

  • ROAMING_STATUS_ROMER = 4 //OUT-HR

• PreemptionCapability (type: Number)

  5G:

  • 0: "PreemptionCapability_DummyEnum"

  • 1: "NOT_PREEMPT"

  • 2: "MAY_PREEMPT"

  4G and Wi-Fi:

  • 0: Disabled

  • 1: Enabled

• PreemptionVulnerability (type: Number)

  5G:

  • 0: "PreemptionVulnerability_DummyEnum"

  • 1: "NOT_PREEMPTABLE"

  • 2: "PREEMPTABLE"

  4G and Wi-Fi:

  • 0: Disabled

  • 1: Enabled

• Disconnect-Reason (type: String)

  Disconnect-Reason contains a self-explanatory string. If it holds a number, then the string interpretation is as follows:

  • PduRelReason_Error = 1

  • PduRelReason_SessIdleTimeout = 2

  • PduRelReason_SessCpIdleTimeout = 3

  • PduRelReason_SessAbsoluteTimeout = 4

• RequestType (type: Number)

  • RequestType_DummyEnum = 0

  • INITIAL_REQUEST = 1

  • EXISTING_PDU_SESSION = 2

  • INITIAL_EMERGENCY_REQUEST = 3

  • EXISTING_EMERGENCY_PDU_SESSION = 4

• RequestIndication (type: Number)

  • RequestIndication_DummyEnum = 0

  • UE_REQ_PDU_SES_MOD = 1

  • UE_REQ_PDU_SES_REL = 2

  • PDU_SES_MOB = 3

  • NW_REQ_PDU_SES_AUTH = 4

  • NW_REQ_PDU_SES_MOD = 5

  • NW_REQ_PDU_SES_REL = 6

  • EBI_ASSIGNMENT_REQ = 7

• AccessType (type: Number)

  • AccessType_DummyEnum = 0

  • AccessType_3GPP_ACCESS = 1

  • AccessType_NON_3GPP_ACCESS AccessType = 2

Procedure EDR Example:

1,2021/03/18 13:43:40.892,1448,imsi-123456789012345,1287,N11SmContextCreateReq,
.
.
.
3,1313,V1,Success,201,1,,3,1316,V1,Success,200,1,,3,1319,V1,Success,201,1,,3,1287,V1,
imsi-123456789012345,imei-123456786666660,123456789012345,9999988888,msisdn-9999988888,
Success,,1,0,,,193|,,,,,,,NR,3,3329,V1,imsi-123456789012345,imei-123456786666660,msisdn-9999988888,
Success,201,1,3|1;2;7|3000 mbps|4000 mbps|1000 mbps|2000 mbps,20 kbps|20 kbps,,3,3332,V1,Success,
204,1,,3,3585,V1,Success,201,1,,3,524,V1,Success,,1,Request_Accepted,3,1299,V1,Success,200,194|,
77|,,,,1,1,intershat,2|1|0|2|128|1|filters:0;3;1;;|3|1|0|2|192|1|filters:0;3;1;;|1|1|1|1|255|1|
filters:0;3;1;;,5||0 kbps|0 kbps|0 kbps|0 kbps|3||6000 mbps|8000 mbps|2000 mbps|4000 mbps,20 kbps|
20 kbps,N1_N2_TRANSFER_INITIATED,209.165.200.235|,2|Abf123||,0

In the preceding example, the initial entries represent the transaction EDRs and last part provided here represents the procedure-level EDRs.