5.1 Edge Computing charging principles
32.2573GPPCharging managementEdge computing domain chargingRelease 17Telecommunication managementTS
5.1.1 Overview
The charging for Edge Computing domain includes charging for the following aspects:
– 5GS usage for Edge Computing (in clause 5.1.2);
– Edge enabling infrastructure resource usage (in clause 5.1.3);
– Edge application server deployment (in clause 5.1.4); and
– Edge enabling services usage (in clause 5.1.5).
5.1.2 Charging principles for 5GS usage for Edge Computing
5.1.2.1 General
The charging for 5GS usage for Edge Computing is based on the charging functions and principles for 5G data connectivity charging specified in 3GPP TS 32.255 [11].
And, the charging information for PDU sessions and service data flows are correlated to each edge application.
The charging functions for 5GS usage for Edge Computing supports both subscriber based charging and inter-provider based charging.
The charging for 5GS usage for each application should be able to take the monitored QoS (e2e packet delay in 5GS, see 3GPP TS 23.501 [8]) into account.
5.1.2.2 Requirements
The following are high-level charging requirements specific to the charging for 5GS usage for Edge Computing, derived from the requirements in 3GPP TS 23.501 [8], 3GPP TS 23.548 [10], and based on the 5G data connectivity charging requirements specified in 3GPP TS 32.255 [11]:
– The SMF shall be able to provide the information for correlating the PDU session and service data flow to the edge application for charging.
– The SMF should be able to report the monitored QoS result (e2e packet delay in 5GS, see 3GPP TS 23.501 [8]) along with the 5GS usage for each edge application.
5.1.2.3 Charging information
The charging information for 5GS usage for Edge Computing is collected for each UE and each edge application by the SMFs, and are specified in 3GPP TS 32.255 [11].
5.1.3 Charging principles for edge enabling infrastructure resource usage
5.1.3.1 General
In the present specification, the charging is specified for the usage of edge enabling infrastructure resources in the EDN of an ECSP to run the virtualized EAS (i.e. EAS is implemented as VNF) provided by an ASP.
The charging for edge enabling infrastructure resources usage, is based on the MnS(s) for performance assurance of Edge Computing specified in 3GPP TS 28.538 [12], including following resources usage for EAS:
– mean virtual CPU usage;
– mean virtual memory usage;
– mean virtual disk usage;
– data volumes.
The time window during which the charging for edge enabling infrastructure resource usage needs to be enabled, and the criteria (e.g. thresholds) for triggering the charging may be locally configured to CEF, and cannot be controlled by CHF.
5.1.3.2 Requirements
The following are high-level charging requirements specific to the edge enabling infrastructure resources charging:
– The CEF shall be able to consume the MnS (see 3GPP TS 28.538 [12]) to collect the following performance measurements about the usage of enabling infrastructure resources that are supporting to run the virtualized EAS, and enable converged charging when the CEF has fetched the performance data file containing these measurements or the CEF receives the performance data of these measurements by the reportStreamData operation from MnS producer:
– mean virtual CPU usage (see 3GPP TS 28.552 [13]);
– mean virtual memory usage (see 3GPP TS 28.552 [13]);
– mean virtual disk usage (see 3GPP TS 28.552 [13]);
– data volumes (see 3GPP TS 28.552 [13]).
5.1.3.3 Charging information
Charging information for edge enabling infrastructure resources usage charging is collected for each EAS by the CEF from the MnS, with the information identifying the EDN where the edge enabling infrastructure resources are allocated and the information indicating the collection period of the measurements related to the edge enabling infrastructure resources usage.
5.1.3.4 CHF selection
The CHF Address(es) selection by the CEF is done during the EAS deployment process based on the following options:
– NRF based discovery.
– CEF locally provisioned charging characteristics.
The priority order between these options depends on Operator’s policies.
Once selected, these CHF Address(es) shall be used as long as the EAS is deployed in the EDN.
5.1.4 Charging principles for edge application server deployment
5.1.4.1 General
In the present specification, the charging is specified for deployment of virtualized EAS in the EDN by an ECSP for an ASP.
The charging for edge application server deployment, is based on the MnS(s) for LCM (LifeCycle Management) of Edge Computing specified in 3GPP TS 28.538 [12], including following deployment activities for EAS:
– EAS instantiation;
– EAS upgrade;
– EAS termination.
5.1.4.2 Requirements
The following are high-level charging requirements specific to the EAS deployment charging:
– The CEF shall be able to consume the MnS (see 3GPP TS 28.538 [12]) to receive the notifications about EAS deployment, and enable charging for the EAS deployment which includes:
– EAS instantiation (see 3GPP TS 28.538 [12]);
– EAS upgrade (see 3GPP TS 28.538 [12]);
– EAS termination (see 3GPP TS 28.538 [12]).
5.1.4.3 Charging information
Charging information for EAS deployment charging is collected for each EAS by the CEF from the MnS.
The CEF collects the following charging information for converged charging of EAS deployment charging:
– EAS deployment requirements: the requirements for EAS deployment (e.g. the topological or geographical service areas, software image information), see 3GPP TS 28.538 [12];
– EAS: the charging information identifying the EAS which the LCM is for;
– EDN: the charging information identifying the EDN where the EAS is/was deployed;
– LCM start time: the charging information indicating the start time of the LCM process;
– LCM end time: the charging information indicating the end time of the LCM process.
5.1.5 Charging principles for edge enabling services
5.1.5.1 General
In the present specification, the charging is specified for edge enabling services provided by an ECSP to an ASP.
The charging for edge enabling services, is based on the edge application enabling functionalities specified in 3GPP TS 23.558 [9], including the services directly provided by ECSP to ASP, and the 3GPP 5GC NF services exposed by ECSP to ASP:
– Edge enabling services directly provided by ECSP to ASP:
– EAS registration;
– EAS discovery;
– Support to Service Continuity;
– Application Client information subscription/notification;
– Edge enabling services exposed by ECSP to ASP:
– Obtaining UE location;
– ACR management events subscription;
– Session with QoS.
5.1.5.2 Requirements
The following are high-level charging requirements specific to the edge enabling services charging:
– The EES shall support converged charging for edge enabling services using service based interface.
– The EES shall support converged charging per EAS registration.
– The EES shall support converged charging per EAS discovery.
– The EES shall support converged charging per Service Continuity support.
– The EES shall support converged charging per Application Client information exposure.
– The EES shall support converged charging per UE location Obtaining.
– The EES shall support converged charging ACR management events subscription.
– The EES shall support converged charging per Session with QoS.
5.1.5.3 Charging information
Charging information for edge enabling services charging is collected for each EAS by EES(es).
The EES collects the following charging information for converged charging of edge enabling services charging:
– EAS: the charging information identifying the EAS for which the edge enabling service is provided;
– EDN: the charging information identifying the EDN where the EAS is/was deployed;
– EES: the charging information indicating the EES which triggers the charging;
– Triggering event: the triggering events of charging for edge enabling services;
– Triggering event specific information: the charging information specific to the triggering event of charging for edge enabling services.
5.1.5.4 CHF selection
The CHF Address(es) selection by the CEF is done during the EAS deployment process based on the following options:
– NRF based discovery.
– CEF locally provisioned charging characteristics.
The priority order between these options depends on Operator’s policies.
Once selected, these CHF Address(es) shall be used as long as the EAS is deployed in the EDN.