4 CHF-CDR Format
Caution:
Deploying charging for 5G with HTTP Gateway (5G CHF) requires a cloud native deployment of ECE and BRM components. The HTTP Gateway can be used only on an ECE cloud native system.
The following table describes the conformance status for the fields in the 3GPP Charging Function Call Detail Record (CHF-CDR), taken from the 3GPP TS 32.298 version 16.5.0 specification. You can configure Oracle Communications Elastic Charging Engine (ECE) to generate CHF-CDRs. See "Generating CDRs" in ECE Implementing Charging.
Table 4-1 CHF-CDR Format
Field | Status |
---|---|
Record Type | Supported |
Recording Network Function ID | Not supported |
Charging Session Identifier | Supported |
Subscriber Identifier | Supported |
NF Consumer Information | Supported |
NF Functionality | Supported |
NF Name | Supported |
NF Address | Supported |
NF PLMN ID | Supported |
Triggers | Supported |
SMF Triggers | Supported |
List of Multiple Unit Usage | Supported |
Rating Group | Supported |
Used Unit Container | Supported |
Service Identifier | Supported |
Quota management Indicator | Supported |
Local Sequence Number | Supported |
Time | Supported |
Uplink Volume | Supported |
Downlink Volume | Supported |
Total Volume | Supported |
Service Specific Units | Supported |
Event Time Stamp | Supported |
Rating Indicator | Supported |
Triggers | Supported |
SMF Triggers | Supported |
Trigger Time Stamp | Supported |
PDU Container Information | Supported |
UPF ID | Supported |
Record Opening Time | Supported |
Duration | Supported |
Record Sequence Number | Supported |
Cause for Record Closing | Supported |
Local Record Sequence Number | Supported |
Record Extensions | Not supported |
Service Specification Information | Supported |
PDU Session Charging Information | Supported |
Roaming QBC Information | Supported |
SMS Charging Information | Supported |
Registration Charging Information | Not supported |
N2 connection charging Information | Not supported |
Location reporting charging Information | Not supported |