5.2.4 Charging scenarios for edge enabling services
32.2573GPPCharging managementEdge computing domain chargingRelease 17Telecommunication managementTS
5.2.4.1 Basic principles
5.2.4.1.1 General
Converged charging for edge enabling services, when activated may be performed by the EES interacting with CHF using Nchf specified in 3GPP TS 32.290 [6] and 3GPP TS 32.291 [7]. In order to provide the data required for the management activities outlined in 3GPP TS 32.240 [1] (Credit-Control, accounting, billing, statistics, etc.), the EES shall be able to perform converged charging for each of the following:
– Edge enabling services directly provided by ECSP to ASP (see 3GPP TS 23.558 [9]):
– EAS registration;
– EAS discovery;
– Support to Service Continuity;
– Application Client information exposure;
– Edge enabling services exposed by ECSP to ASP (see 3GPP TS 23.558 [9]):
– Obtaining UE location;
– ACR management events subscription;
– Session with QoS.
The EES shall be able to perform converged charging by interacting with CHF, for charging data related to the evens mentioned above. The Charging Data Request and Charging Data Response are exchanged between the EES and the CHF, based on either IEC or PEC scenarios as specified in 3GPP TS 32.290 [6].
The contents and purpose of each charging event that triggers interaction with CHF, as well as the chargeable events that trigger them, are described in the following clauses.
A detailed formal description of the converged charging parameters defined in the present document is to be found in 3GPP TS 32.291 [7].
A detailed formal description of the CDR parameters defined in the present document is to be found in 3GPP TS 32.298 [3].
NOTE: How to avoid double triggering or support correlation of charging events from both NEF and EES is not addressed in the present document.
5.2.4.1.2 Applicable triggers in the EES
When a charging event is issued towards the CHF by the EES, it includes details of charging information, such as EAS identifier (e.g. EAS ID, see 3GPP TS 23.558 [9]).
Each trigger condition (i.e. chargeable event) defined for edge enabling services charging, is specified with the associated behaviour when they are met.
The immediate report is applied to the chargeable events for edge enabling services charging, i.e. the chargeable events for which, when occurring, the current counts are closed and sent together with the charging data generated by the EES towards the CHF in a Charging Data Request. New counts are started by the EES.
Table 5.2.4.1.2-1 summarizes the set of default trigger conditions and their category which shall be supported by the EES when charging is active for the edge enabling services charging.
Table 5.2.4.1.2-1: Default Trigger conditions in EES
|
Trigger Conditions |
Trigger level |
Default category |
CHF allowed to change category |
CHF allowed to enable and disable |
Message when "immediate reporting" category |
|---|---|---|---|---|---|
|
Charging for edge enabling services directly provided by EES |
|||||
|
EAS registration request |
– |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
EAS registration response |
– |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
EAS discovery request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
EAS discovery response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
ACR request |
– |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
ACR response |
– |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
ACR status update request |
– |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
ACR status update response |
– |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
AC information subscribe request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
AC information subscribe response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
AC information subscription update request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
AC information subscription update response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
AC information notification |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
Charging for edge enabling services exposed by EES |
|||||
|
UE location request |
– |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
UE location response |
– |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
UE location subscribe request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
UE location subscribe response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
UE location subscription update request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
UE location subscription update response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
UE location notification |
– |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
ACR management event subscribe request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
ACR management event subscribe response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
ACR management event subscription update request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
ACR management event subscription update response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
Session with QoS create request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
Session with QoS create response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
Session with QoS update request |
Immediate |
Not Applicable |
Yes |
IEC: Charging Data Request [Event] |
|
|
Session with QoS update response |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
|
Session with QoS event notification |
Immediate |
Not Applicable |
Yes |
PEC: Charging Data Request [Event] |
|
5.2.4.2 Message flows
5.2.4.2.1 General
The flows in the present document specify the interactions between the EES and CHF for edge enabling services converged charging, based on the procedures and flows specified in 3GPP TS 23.558 [9].
This interaction is based on Charging Data Request /Response specified in 3GPP TS 32.290 [6], exchanged between the EES embedding the CTF and the CHF, in compliance with the converged charging architecture defined in clause 4.2.3.
5.2.4.2.2 EAS registration charging
5.2.4.2.2.1 General
The clauses below describe the EAS registration charging message flows.
For EAS registration charging, the following scenarios specified in 3GPP TS 32.290 [6] are supported:
– IEC;
– PEC.
5.2.4.2.2.2 EAS registration charging – IEC
Figure 5.2.4.2.2.2-1 describes an EAS registration charging message flow in IEC charging.
Figure 5.2.4.2.2.2-1: Charging for EAS registration – IEC
1) The EAS determines that registration to the EES is needed (e.g. the EAS is instantiated and started up).
2) The EAS sends an EAS registration request to the EES. The request shall include the EAS profile and may include proposed expiration time for the registration.
3) The EES performs an authorization check to verify whether the EAS has the authorization to register on the EES. If authorized:
3ch-a) Charging Data Request [Event]: The EES generates charging data related to the EAS Registration request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
3ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
3ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
4) The EES sends EAS response (see 3GPP TS 23.558 [9]) to the EAS.
5.2.4.2.2.3 EAS registration charging – PEC
Figure 5.2.4.2.2.3-1 describes an EAS registration charging message flow in PEC charging.
Figure 5.2.4.2.2.3-1: Charging for EAS registration – PEC
1) The EAS determines that registration to the EES is needed (e.g. the EAS is instantiated and started up).
2) The EAS sends an EAS registration request to the EES. The request shall include the EAS profile and may include proposed expiration time for the registration.
3) The EES performs an authorization check to verify whether the EAS has the authorization to register on the EES, if authorized.
4) Upon successful authorization, the EES stores the EAS Profile for later use (e.g. for serving EAS discovery requests received from EECs, etc.) and replies to the EAS with an EAS registration response:
4ch-a) Charging Data Request [Event]: The EES generates charging data related to the EAS Registration and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
4ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
4ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.3 EAS discovery charging
5.2.4.2.3.1 General
The clauses below describe the EAS discovery charging message flows.
For EAS discovery charging, the following scenarios specified in 3GPP TS 32.290 [6] are supported:
– IEC;
– PEC.
5.2.4.2.3.2 EAS discovery charging – IEC
Figure 5.2.4.2.3.2-1 describes an EAS discovery charging message flow in IEC charging.
Figure 5.2.4.2.3.2-1: Charging for EAS discovery – IEC
1) The EEC sends the EES discovery request to the EES.
2) Upon receiving the request from the EEC, the EES checks if the EEC is authorized to discover the requested EAS(s). If authorized:
2ch-a) Charging Data Request [Event]: The EES generates charging data related to the EAS discovery request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
2ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
2ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
3) The EES sends EAS discovery response to the EEC.
5.2.4.2.3.3 EAS discovery charging – PEC
Figure 5.2.4.2.3.3-1 describes an EAS discovery charging message flow in PEC charging.
Figure 5.2.4.2.3.3-1: Charging for EAS discovery – PEC
1) The EEC sends the EAS discovery request to the EES.
2) Upon receiving the request from the EEC, the EES checks if the EEC is authorized to discover the requested EAS(s).
3) The EES sends EAS discovery response to the EEC:
3ch-a) Charging Data Request [Event]: The EES generates charging data related to the EAS discovery and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
3ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
3ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.4 Support to Service Continuity charging
5.2.4.2.4.1 General
The clauses below describe the Support to Service Continuity charging message flows.
For Support to Service Continuity charging, the following scenarios specified in 3GPP TS 32.290 [6] are supported:
– IEC;
– PEC.
5.2.4.2.4.2 ACR charging – IEC
Figure 5.2.4.2.4.2-1 describes an ACR charging message flow in IEC charging.
Figure 5.2.4.2.4.2-1: Charging for ACR – IEC
1) The EEC or S-EAS sends the ACR request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to the ACR request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES checks the authorization and processes the request.
3) The EES sends ACR response to the EEC or S-EAS.
5.2.4.2.4.3 ACR charging – PEC
Figure 5.2.4.2.4.3-1 describes an ACR charging message flow in PEC charging.
Figure 5.2.4.2.4.3-1: Charging for ACR – PEC
1) The EEC or S-EAS sends the ACR request to the EES.
2) The EES checks the authorization and processes the request.
3) The EES sends ACR response to the EEC or S-EAS.
1ch-a) Charging Data Request [Event]: The EES generates charging data related to the ACR and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.4.4 ACR status update charging – IEC
Figure 5.2.4.2.4.4-1 describes an ACR status update charging message flow in IEC charging.
Figure 5.2.4.2.4.4-1: Charging for ACR status update – IEC
1) The EAS sends the ACR status update request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to the ACR status update request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES processes the request.
3) The EES sends ACR status update response to the EAS.
5.2.4.2.4.5 ACR status update charging – PEC
Figure 5.2.4.2.4.5-1 describes an ACR status update charging message flow in PEC charging.
Figure 5.2.4.2.4.5-1: Charging for ACR status update – PEC
1) The EAS sends the ACR status update request to the EES.
2) The EES processes the request.
3) The EES sends ACR response to the EAS:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to the ACR status update and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.5 Application Client information exposure charging
5.2.4.2.5.1 General
The clauses below describe the Application Client information exposure charging message flows.
For Application Client information exposure charging, the following scenarios specified in 3GPP TS 32.290 [6] are supported:
– IEC;
– PEC.
5.2.4.2.5.2 Application Client information subscription charging – IEC
Figure 5.2.4.2.5.2-1 describes an Application Client information subscription charging message flow in IEC charging.
Figure 5.2.4.2.5.2-1: Charging for AC information subscription – IEC
1) The EAS sends the AC information subscription request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to AC information subscription request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES processes the request.
3) The EES sends the AC information subscription response to EAS.
5.2.4.2.5.3 Application Client information subscription charging – PEC
Figure 5.2.4.2.5.3-1 describes an Application Client information subscription charging message flow in PEC charging.
Figure 5.2.4.2.5.3-1: Charging for AC information subscription – PEC
1) The EAS sends the AC information subscription request to the EES.
2) The EES processes the request.
3) The EES sends the AC information subscription response to EAS:
3ch-a) Charging Data Request [Event]: The EES generates charging data related to AC information subscription and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
3ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
3ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.5.4 Application Client information subscription update charging – IEC
Figure 5.2.4.2.5.4-1 describes an Application Client information subscription update charging message flow in IEC charging.
Figure 5.2.4.2.5.4-1: Charging for AC information subscription update – IEC
1) The EAS sends the AC information subscription update request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to AC information subscription update request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES processes the request.
3) The EES sends the AC information subscription update response to EAS.
5.2.4.2.5.5 Application Client information subscription update charging – PEC
Figure 5.2.4.2.5.5-1 describes an Application Client information subscription update charging message flow in PEC charging.
Figure 5.2.4.2.5.5-1: Charging for AC information subscription update – PEC
1) The EAS sends the AC information subscription update request to the EES.
2) The EES processes the request.
3) The EES sends the AC information subscription update response to EAS:
3ch-a) Charging Data Request [Event]: The EES generates charging data related to AC information subscription update and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
3ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
3ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.5.6 Application Client information notification charging – PEC
Figure 5.2.4.2.5.6-1 describes an Application Client information notification charging message flow in PEC charging.
Figure 5.2.4.2.5.6-1: Charging for AC information notification – PEC
1) The EEC triggers for AC updates with EES.
2) The EES sends the AC information notification to the EAS:
2ch-a) Charging Data Request [Event]: The EES generates charging data related to AC information notification and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
2ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
2ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.6 UE location obtaining charging
5.2.4.2.6.1 General
The clauses below describe the UE location obtaining charging message flows.
For UE location obtaining charging, the following scenarios specified in 3GPP TS 32.290 [6] are supported:
– IEC;
– PEC.
5.2.4.2.6.2 UE location request charging – IEC
Figure 5.2.4.2.6.2-1 describes a UE location request charging message flow in IEC charging.
Figure 5.2.4.2.6.2-1: Charging for UE location request – IEC
1) The EAS sends the UE location request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to UE location request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES checks the UE location with 3GPP network.
3) The EES sends the UE location response to the EAS.
5.2.4.2.6.3 UE location request charging – PEC
Figure 5.2.4.2.6.3-1 describes a UE location request charging message flow in PEC charging.
Figure 5.2.4.2.6.3-1: Charging for UE location request – PEC
1) The EAS sends the UE location request to the EES.
2) The EES checks the UE location with 3GPP network.
3) The EES sends the UE location response to the EAS:
3ch-a) Charging Data Request [Event]: The EES generates charging data related to UE location response and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
3ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
3ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.6.4 UE location subscription charging – IEC
Figure 5.2.4.2.6.4-1 describes a UE location subscription charging message flow in IEC charging.
Figure 5.2.4.2.6.4-1: Charging for UE location subscription – IEC
1) The EAS sends the UE location subscribe request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to UE location subscribe request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES subscribes to UE location from 3GPP Core Network.
3) The EES may subscribe to UE expected behaviour analytics (UE mobility) from 3GPP Core Network.
4) The EES sends the UE location subscribe response to the EAS.
5.2.4.2.6.5 UE location subscription charging – PEC
Figure 5.2.4.2.6.5-1 describes a UE location subscription charging message flow in PEC charging.
Figure 5.2.4.2.6.5-1: Charging for UE location subscription – PEC
1) The EAS sends the UE location subscribe request to the EES.
2) The EES subscribes to UE location from 3GPP Core Network.
3) The EES may subscribe to UE expected behaviour analytics (UE mobility) from 3GPP Core Network (see 3GPP TS 23.558 [9]).
4) The EES sends the UE location subscribe response to the EAS:
4ch-a) Charging Data Request [Event]: The EES generates charging data related to UE location subscribing and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
4ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
4ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.6.6 UE location subscription update charging – IEC
Figure 5.2.4.2.6.6-1 describes a UE location subscription update charging message flow in IEC charging.
Figure 5.2.4.2.6.6-1: Charging for UE location subscription – IEC
1) The EAS sends the UE location subscription update request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to UE location subscription update request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES updates the UE location subscription to 3GPP Core Network.
3) The EES may subscribe to updated UE expected behaviour analytics (UE mobility) from 3GPP Core Network (see 3GPP TS 23.558 [9]).
4) The EES sends the UE location subscription update response to the EAS.
5.2.4.2.6.7 UE location subscription update charging – PEC
Figure 5.2.4.2.6.7-1 describes a UE location subscription update charging message flow in PEC charging.
Figure 5.2.4.2.6.7-1: Charging for UE location subscription – PEC
1) The EAS sends the UE location subscription update request to the EES.
2) The EES updates the UE location subscription to 3GPP Core Network.
3) The EES may subscribe to updated UE expected behaviour analytics (UE mobility) from 3GPP Core Network (see 3GPP TS 23.558 [9]).
4) The EES sends the UE location subscription update response to the EAS:
4ch-a) Charging Data Request [Event]: The EES generates charging data related to UE location subscription update and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
4ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
4ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.6.8 UE location notification charging – PEC
Figure 5.2.4.2.6.8-1 describes a UE location notification charging message flow in PEC charging.
Figure 5.2.4.2.6.8-1: Charging for UE location notification – PEC
1) The EES detects the UE location.
2) The EES sends the UE location notification to the EAS:
2ch-a) Charging Data Request [Event]: The EES generates charging data related to UE location notification and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
2ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
2ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.7 ACR management events subscription charging
5.2.4.2.7.1 General
The clauses below describe the ACR management events subscription charging message flows.
For ACR management events subscription charging, the following scenarios specified in 3GPP TS 32.290 [6] are supported:
– IEC;
– PEC.
5.2.4.2.7.2 ACR management events subscription charging – IEC
Figure 5.2.4.2.7.2-1 describes an ACR management events subscription charging message flow in IEC charging.
Figure 5.2.4.2.7.2-1: Charging for ACR management event subscription – IEC
1) The EAS sends the ACR management event subscribe request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to ACR management event subscribe request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES checks the user plane path management event of the requesting UE with 3GPP Core Network.
3) The EES may subscribe to UE expected behaviour analytics (UE mobility) from 3GPP Core Network.
4) The EES sends the ACR management event subscribe response to the EAS.
5.2.4.2.7.3 ACR management events subscription charging – PEC
Figure 5.2.4.2.7.3-1 describes an ACR management events subscription charging message flow in PEC charging.
Figure 5.2.4.2.7.3-1: Charging for ACR management event subscription – PEC
1) The EAS sends the ACR management event subscribe request to the EES.
2) The EES checks the user plane path management event of the requesting UE with 3GPP Core Network.
3) The EES may subscribe to UE expected behaviour analytics (UE mobility) from 3GPP Core Network.
4) The EES sends the ACR management event subscribe response to the EAS:
4ch-a) Charging Data Request [Event]: The EES generates charging data related to ACR management event subscribing and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
4ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
4ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.7.4 ACR management events subscription update charging – IEC
Figure 5.2.4.2.7.4-1 describes an ACR management events subscription update charging message flow in IEC charging.
Figure 5.2.4.2.7.4-1: Charging for ACR management event subscription update – IEC
1) The EAS sends the ACR management event subscription update request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to ACR management event subscription update request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES checks the user plane path management event of the requesting UE with 3GPP Core Network.
3) The EES updates UE expected behaviour analytics (UE mobility) to 3GPP Core Network.
4) The EES sends the ACR management event subscription update response (see 3GPP TS 23.558 [9]) to the EAS.
5.2.4.2.7.5 ACR management events subscription update charging – IEC
Figure 5.2.4.2.7.5-1 describes an ACR management events subscription update charging message flow in IEC charging.
Figure 5.2.4.2.7.5-1: Charging for ACR management event subscription update – PEC
1) The EAS sends the ACR management event subscription update request to the EES.
2) The EES checks the user plane path management event of the requesting UE with 3GPP Core Network.
3) The EES updates UE expected behaviour analytics (UE mobility) to 3GPP Core Network.
4) The EES sends the ACR management event subscription update response to the EAS:
4ch-a) Charging Data Request [Event]: The EES generates charging data related to ACR management event subscription update and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
4ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
4ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.8 Session with QoS charging
5.2.4.2.8.1 General
The clauses below describe the Session with QoS charging message flows.
For Session with QoS charging, the following scenarios specified in 3GPP TS 32.290 [6] are supported:
– IEC;
– PEC.
5.2.4.2.8.2 Session with QoS creation charging – IEC
Figure 5.2.4.2.8.2-1 describes a Session with QoS creation charging message flow in IEC charging.
Figure 5.2.4.2.8.2-1: Charging for creation of Session with QoS – IEC
1) The EAS sends the Session with QoS create request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to Session with QoS create request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES subscribes to PDU session status monitoring and request data session with specific QoS from 3GPP 5G Core Network.
3) The EES sends Session with QoS create response to the EAS.
5.2.4.2.8.3 Session with QoS creation charging – PEC
Figure 5.2.4.2.8.3-1 describes a Session with QoS creation charging message flow in PEC charging.
Figure 5.2.4.2.8.3-1: Charging for creation of Session with QoS – PEC
1) The EAS sends the Session with QoS create request to the EES.
2) The EES subscribes to PDU session status monitoring and request data session with specific QoS from 3GPP 5G Core Network.
3) The EES sends Session with QoS create response to the EAS:
3ch-a) Charging Data Request [Event]: The EES generates charging data related to Session with QoS creation and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
3ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
3ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.8.4 Session with QoS update charging – IEC
Figure 5.2.4.2.8.4-1 describes a Session with QoS update charging message flow in IEC charging.
Figure 5.2.4.2.8.4-1: Charging for update of Session with QoS – IEC
1) The EAS sends the Session with QoS update request to the EES:
1ch-a) Charging Data Request [Event]: The EES generates charging data related to Session with QoS update request and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
1ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
1ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
2) The EES updates data session with specific QoS with 3GPP 5G Core Network.
3) The EES sends Session with QoS update response to the EAS.
5.2.4.2.8.5 Session with QoS update charging – PEC
Figure 5.2.4.2.8.5-1 describes a Session with QoS update charging message flow in PEC charging.
Figure 5.2.4.2.8.5-1: Charging for update of Session with QoS – PEC
1) The EAS sends the Session with QoS update request to the EES.
2) The EES updates data session with specific QoS with 3GPP 5G Core Network.
3) The EES sends Session with QoS update response to the EAS:
3ch-a) Charging Data Request [Event]: The EES generates charging data related to Session with QoS update and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
3ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
3ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.2.8.6 Session with QoS notification charging – PEC
Figure 5.2.4.2.8.6-1 describes a Session with QoS notification charging message flow in PEC charging.
Figure 5.2.4.2.8.6-1: Charging for Session with QoS notification – PEC
1) The EES detects User Plane event for Session with QoS from 3GPP 5G Core Network.
2) The EES sends Session with QoS notification to EAS:
2ch-a) Charging Data Request [Event]: The EES generates charging data related to Session with QoS notification and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
2ch-b) Create CDR: The CHF stores received information and creates a CDR related to the event.
2ch-c) Charging Data Response [Event]: The CHF informs the EES on the result of the request.
5.2.4.3 CDR generation
5.2.4.3.1 Introduction
The CHF CDRs for edge enabling services charging 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 generating the CHF CDR.
5.2.4.3.2 Triggers for CHF CDR
5.2.4.3.2.1 General
An edge enabling services charging CHF CDR is used to collect charging information related to edge enabling services chargeable events for IEC and PEC.
5.2.4.3.2.2 Triggers for CHF CDR generation
A CHF CDR shall be generated by the CHF for each received Charging Data Request [Event].
5.2.4.4 Ga record transfer flows
For Ga protocol application refer to 3GPP TS 32.295 [5].
5.2.4.5 Bee CDR file transfer
For Bee protocol application refer to 3GPP TS 32.297 [4].