Feature Description

Event Data Records (EDRs) collect information that you can use to charge subscribers for specific events that they consume. The EDRs catch whatever bytes get transmitted over the flow.

When a flow ends, the SMF generates EDRs with detail information of the terminated flow. The SMF supports logging of EDRs for both 4G and 5G subscriber sessions.

The SMF uses the event reports to generate EDR files comprised of logged information in comma-separated value (CSV) format. The SMF sends one CSV record per line. The CSV records are stored in a file and are optionally compressed before sending to an external server.

These CSV files can be downloaded and used offline to—

  • Debug or understand the application behaviour.

  • Diagnose the call flow for the specific subscribers.

The SMF supports EDR file generation for transaction and transaction-collision level details for subscriber sessions. By default, the EDR generation is disabled.

EDR Format

In addition to the existing Transaction EDR fields, the application appends procedure-id and event-id along with their field values. Application registers the procedure-id, event-id, and field-id along with their corresponding names. This mapping is used to format the CSV event entry. Each event entry consists of comma-separated procedure-id, event-id, and field-value. These registered mappings can also be used in CLI commands to disable EDRs at procedure, event, or field level. You can enable or disable the EDRs dynamically during runtime. The existing EDR records remain the same and the runtime changes get reflected only in the newly generated EDR records.

Transaction EDR Format

Transaction-EDR-Fields, list of Event-Entries []

Event Entries

Procedure-id1, Event-id1, list of field-id1-values[]

The following is a sample transaction entry along with a list of events in the CSV format.

Transaction-id-value, Start-Time, Elapsed-Time, ……, 
Procedure-id1, event-id1, field-id1-value, field-id2-value……, 
Procedure-id1, event-id2, field-id1-value, field-id2-value……, 
        Procedure-id1, event-id1, field-id1-value, field-id2-value……
Note

There might be different set of fields for a combination of procedure-id and event-id. You can enable or disable the EDRs dynamically during runtime by using a CLI command. For configuration details, see the Configure EDR Files for Generation section in this guide.

The CSV file is generated in each SMF service pod where the subscriber sessions and events are processed. The location of the EDR files inside pod is as follows:

/tmp/edr/smf-service/<pod-instance>/transactions.csv

/tmp/edr/smf-service/<pod-instance>/transaction_collisions.csv

Example:

/tmp/edr/smf-service/1/transactions.csv

/tmp/edr/smf-service/1/transaction_collisions.csv