5.2.3 CDR generation
32.2553GPP5G data connectivity domain chargingCharging managementRelease 17Stage 2Telecommunication managementTS
5.2.3.1 Introduction
The CHF CDRs for PDU session charging and roaming QBC are generated by the CHF to collect charging information that they subsequently transfer to the Charging Gateway Function (CGF).
The following clauses describe in detail the conditions for opening, adding information to, and closing the CHF CDR.
5.2.3.2 Triggers for CHF CDR
5.2.3.2.1 General
A PDU session charging CHF CDR is used to collect charging information related to the PDU session data information for a UE in Flow Based Charging. Multiple service data flow containers per PDU session can be added in the CHF CDR by the CHF, upon receiving a Charging Data Request including new counts as defined in subclause 5.2.1.1.
A CHF CDR shall be opened when the CHF receives Charging Data Request[Initial].
As an alternative to the default CHF behaviour, the "Individual Partial record" mechanism can be used based on Operator’s policy configured in the CHF. In this case a new CDR shall be opened for each Charging Data Request[Initial, Update, Termination], charging information shall be added and the CDR shall then be closed. The Sequence Number will be incremented for each Charging Data Request[Initial, Update, Termination] received by the CHF.
5.2.3.2.2 Triggers for CHF CDR charging information addition
When the CHF receives Charging Data Request[Update], with the change conditions identified in Table 5.2.3.2.2.1 the charging information shall be added in the PDU session charging CHF CDR, and the CDR shall remain open, as the default supported mechanism.
Table 5.2.3.2.2.1: Triggers for CHF CDR charging information addition
|
Trigger Conditions |
Applicable for converged charging |
Applicable for offline only charging |
|
Change of Charging conditions |
||
|
QoS change |
Yes |
Yes |
|
User Location change |
Yes |
Yes |
|
Serving Node change |
Yes |
Yes |
|
Change of UE presence in Presence Reporting Area(s) |
Yes |
Yes |
|
Change of 3GPP PS Data off Status |
Yes |
Yes |
|
Handover cancel |
Yes |
Yes |
|
Handover start |
Yes |
Yes |
|
Limit per Rating Group |
||
|
Expiry of data time limit per RG |
Yes |
Yes |
|
Expiry of data volume limit per RG |
Yes |
Yes |
|
Expiry of data event limit per RG |
Yes |
Yes |
|
Quota management triggers |
||
|
Time threshold reached |
Yes |
No |
|
Volume threshold reached |
Yes |
No |
|
Unit threshold reached |
Yes |
No |
|
Time quota exhausted |
Yes |
No |
|
Volume quota exhausted |
Yes |
No |
|
Unit quota exhausted |
Yes |
No |
|
Expiry of quota validity time |
Yes |
No |
|
Re-authorization request by CHF |
Yes |
No |
In case the "Individual Partial record" mechanism is enabled, the Table 5.2.3.2.2.1 is not applicable. The charging information consists of a set of containers, which are added as "List of Multiple Unit Usage" parameter of the CHF CDR. Each container identifies the configured counts (volume separated for uplink and downlink, elapsed time or number of events) per rating group or combination of the rating group and service id, associated with the changed charging conditions.
5.2.3.2.3 Triggers for CHF CDR partial record closure
When the CHF receives Charging Data Request [Update], with the change conditions identified in Table 5.2.3.2.3.1, the charging information shall be added in the PDU session charging CHF CDR, before the CDR is closed and a subsequent CHF CDR shall be opened with an incremented Sequence Number, as the default supported mechanism.
.
Table 5.2.3.2.3.1: Triggers for CHF CDR partial record closure
|
Trigger Conditions |
|
Change of Charging conditions |
|
UE time zone change |
|
PLMN change |
|
RAT type change |
|
Session-AMBR change |
|
Removal of UPF |
|
Insertion_of_ISMF |
|
Change_of_ISMF |
|
Removal_of_ISMF |
|
Handover complete |
|
Management intervention |
|
Addition of access |
|
Removal of access |
|
Limit per PDU session |
|
Expiry of data time limit per PDU session |
|
Expiry of data volume limit per PDU session |
|
Expiry of data event limit per PDU session |
|
Expiry of limit of number of charging condition changes |
In case the "Individual Partial record" mechanism is enabled, the Table 5.2.3.2.3.1 is not applicable.
5.2.3.2.4 Triggers for CHF CDR closure
When the CHF receives Charging Data Request[Termination], the charging information shall be added in the PDU session charging CHF CDR and the CDR shall be closed.
5.2.3.3 Triggers for CHF CDR for roaming QBC
5.2.3.3.1 General
A Roaming QBC CHF CDR is used to collect charging information related to Roaming QBC in V-SMF, and the PDU session charging CHF CDR is used to collect charging information related to Roaming QBC in H-SMF. QoS flow containers per PDU session can be added in the CHF CDRs by the CHF, upon receiving a Charging Data Request.
The charging information received from the CHF consists of a set of containers, which are added as "List Multiple QFI container" parameter of the CHF CDRs. Each container identifies the configured counts (volume separated for uplink and downlink, elapsed time) per QoS Flow, associated with the changed charging conditions.
A roaming CHF CDR shall be opened when the CHF receives Charging Data Request[Initial] indicating "in-bound roamer".
5.2.3.3.2 Triggers for CHF CDR charging information addition for roaming QBC
When the CHF receives Charging Data Request[Update], with the change conditions identified in Table 5.2.3.3.2.1 the charging information shall be added in the CHFCDR, and the CDR shall remain open, as the default supported mechanism.
Table 5.2.3.3.2.1: Triggers for CHF CDR charging information addition for roaming QBC
|
Trigger Conditions |
|
Change of Charging conditions |
|
QoS change |
|
User Location change |
|
Serving Node change |
|
Change of UE presence in Presence Reporting Area(s) |
|
Change of 3GPP PS Data off Status |
|
Limit per QoS Flow |
|
Expiry of data time limit per QoS Flow |
|
Expiry of data volume limit per QoS Flow |
|
Others |
|
End of QoS Flow |
In case the "Individual partial record" mechanism is enabled, this sub-clause is not applicable.
5.2.3.3.3 Triggers for CHF CDR partial record closure for roaming QBC
When the CHF receives Charging Data Request [Update] with the change conditions identified in Table 5.2.3.3.3.1, the charging information shall be added in the CHF CDR, before the CDR is closed and a subsequent CHF CDR shall be opened with an incremented Sequence Number, as the default supported mechanism.
Table 5.2.3.3.3.1: Triggers for CHF CDR partial record closure for roaming QBC
|
Trigger Conditions |
|
Change of Charging conditions |
|
UE time zone change |
|
PLMN change |
|
RAT type change |
|
Session-AMBR change |
|
Removal of UPF |
|
Management intervention |
|
Limit per PDU session |
|
Expiry of data time limit per PDU session |
|
Expiry of data volume limit per PDU session |
|
Expiry of data event limit per PDU session |
|
Expiry of limit of number of charging condition changes |
In case the "Individual partial record" mechanism is enabled, the Table 5.2.3.3.3.1 is not relevant: instead, the charging information shall be added in the CHF CDR, before the CDR is closed and a subsequent CHF CDR shall be opened with an incremented Sequence Number for each Charging Data Request [Update] received by the CHF.
5.2.3.3.4 Triggers for roaming QBC CHF CDR closure
When the CHF receives Charging Data Request[Termination], the charging information shall be added in the roaming QBC CHF CDR and the CDR shall be closed.