5 Services offered by the CHF

32.2913GPP5G system, charging serviceCharging managementRelease 17Stage 3Telecommunication managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1 Introduction

The following services are provided by the CHF.

Table 5.1-1: NF Services provided by CHF

Service Name	Description	Consumer
Nchf_ConvergedCharging service	This service provides a converged charging for session and event based NF services, with and without quota management, as well as charging information record generation	SMF, SMSF, AMF, NEF, PGW-C+SMF, IMS-Node, CEF, MnS Producer, 5G DDNMF
Nchf_OfflineOnlyCharging service	This service provides an offline only charging for session based NF service.	SMF
Nchf_SpendingLimitControl	This service enables the PCF to retrieve policy counter status information per UE from the CHF by subscribing to spending limit reporting (i.e. notifications of policy counter status changes).	PCF

Service Name

Description

Consumer

Nchf_ConvergedCharging service

This service provides a converged charging for session and event based NF services, with and without quota management, as well as charging information record generation

SMF, SMSF, AMF, NEF, PGW-C+SMF, IMS-Node, CEF,

MnS Producer, 5G DDNMF

Nchf_OfflineOnlyCharging service

This service provides an offline only charging for session based NF service.

SMF

Nchf_SpendingLimitControl

This service enables the PCF to retrieve policy counter status information per UE from the CHF by subscribing to spending limit reporting (i.e. notifications of policy counter status changes).

PCF

The "Nchf_SpendingLimitControl" service is defined in 29.594 [301].

5.2 Nchf_ConvergedCharging service

5.2.1 Service description

This service provides charging in converged charging scenario by the CHF to the NF service consumer as defined in subclause 6.2 in 3GPP TS 32.290[58].

It includes the following functionalities:

– Create resource at service establishment or no existing ChargingData resource, and may allocate quotas based on the request from NF consumer;

– During the service consumption lifecycle, update resource upon receiving the quota usage or service usage report under a number of circumstances and allocate subsequent quotas based on the request from NF consumer;

– Release upon service termination, Unit Count Inactivity Timer expiry or error response; and

– Notify NF Service Consumer of the re-authorisation triggers when CHF determines rating conditions is affected, or the abort triggers when CHF determines to terminate the charging service.

– Charging information record generation

5.2.2 Service operations

5.2.2.1 Introduction

The service operations defined for Nchf_ ConvergedCharging are shown in table 5.2.2.1-1.

Table 5.2.2.1-2: Nchf_ ConvergedCharging Operations

Service Operation Name	Description	Initiated by	Corresponding Converged charging messages in 3GPP TS 32.290[58]
Nchf_ ConvergedCharging_Create	First Interrogation of unit reservation; And/or initial report of service usage.	NF consumer	Charging Data Request/Response [Initial]
Nchf_ ConvergedCharging_Create	One Time request for the service.	NF consumer	Charging Data Request/Response [Event]
Nchf_ ConvergedCharging_Update	Intermediate Interrogation for subsequent units reservation when: the granted service unitfor one rating group are spent expiry of granted service units validity time service events occur, which might affect the rating of the current service And/or Intermediate report of service usage.	NF consumer	Charging Data Request/Response [Update]
Nchf_ ConvergedCharging_Release	Final Interrogation without any unit reservation And/or last report of service usage.	NF consumer	Charging Data Request/Response [Termination]
Nchf_ ConvergedCharging_Notify	Request that the user be re-authorized or the charging session context be terminated.	CHF	Charging Notify Request/Response

5.2.2.2 Nchf_ConvergedCharging_Create Operation

The Nchf_ConvergedCharging_Create service operation provides means for NF (CTF) to request quotas for service delivery or initial report of service usage.

The following procedures using the Nchf_ConvergedCharging_Create service operation are supported:

– No existing charging data resource.

Figure 5.2.2.2-1: Nchf_ ConvergedCharging_Create Service Operation

1. NF (CTF) sends a Nchf_ConvergedCharging_Create request to the CHF to create resource for charging. Requested quota and notification URI for Nchf_ConvergedCharging_Notify service operation are included in the request body.

2a. At successful operation, "201 Created" response is returned. In the "201 Created" response, the CHF includes a Location header field and the allocated quota in the body. The Location header field shall contain the URI of the created resource. The NF (CTF) shall use the URI received in the Location header in subsequent requests to the CHF for the same PDU session.

2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.2.3.1-3 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.1.7.3-1.

5.2.2.3 Nchf_ConvergedCharging_Update Operation

The Nchf_ConvergedCharging_Update service operation provides means for NF (CTF) to update the charging data.

The following procedures using the Nchf_ConvergedCharging_Update service operation are supported:

– the granted service units for one rating group are spent

– expiry of granted service units’ validity time

– charging events occur, which might affect the rating of the current service

– receiving re-authorization notification from CHF

Figure 5.2.2.3-1: Nchf_ConvergedCharging_Update Service Operation

1. NF (CTF) sends a Nchf_ConvergedCharging_Update request to the CHF. The {ChargingDataRef } in the URI identifies the "Charging Data" to be updated. The requested service unit and previous used service unit is included in the request body.

2a. At successful operation, "200 OK" response is returned. The CHF includes the granted service unit in the "200 OK" response.

2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.2.2-2 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.1.7.3-1.

5.2.2.4 Nchf_ConvergedCharging_Release Operation

The Nchf_ConvergedCharging_Release service operation provides means for NF (CTF) to terminate charging Session.

The following procedures using the Nchf_ConvergedCharging_Release service operation are supported:

– Expiry of unit count inactivity timer in NF Consumer.

– Abort notification is received from CHF.

– Service termination in NF Consumer.

Figure 5.2.2.4-1: Nchf_ConvergedCharging_Release Service Operation

1. NF(CTF) sends a Nchf_ConvergedCharging_Release request to the CHF. The {ChargingDataRef } in the URI identifies the "Charging Data" to be updated and then released. The final used service unit is included in the request body.

2a. At successful operation, "204 No Content" response is returned.

2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.3.2-2 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.1.7.3-1.

5.2.2.5 Nchf_ConvergedCharging_Notify Operation

The Nchf_ConvergedCharging_Notify service operation provides means for CHF to notify the NF(CTF) to update or terminate charging of the PDU Session.

The following procedures using the Nchf_ConvergedCharging_Notify service operation are supported:

– CHF determines re-authorization.

– CHF determines abort of charging.

Figure 5.2.2.5-1: Nchf_ConvergedCharging_Notify Service Operation

1. The CHF sends a Nchf_ConvergedCharging_Notify request to the NF (CTF). The {notifyUri} identifies the notification URI which is sent in the Nchf_ConvergedCharging_Create and can be sent in Nchf_ConvergedCharging_Update request. The notification type is included in the request body.

2a. At successful operation, "204 No Content" response is returned.

2b. On failure , one of the HTTP status code listed in Table 6.1.5.2.3.1-2 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.1.7.3-1.

After successful operation, when the NF Service Consumer receives a Charging Notify Request while not waiting for any Charging Data Response from the CHF, CTF can send a new Charging Data Request.

5.3 Nchf_OfflineOnlyCharging service

5.3.1 Service description

This service provides charging in offline only charging scenario by the CHF to the NF service consumer (i.e. SMF) as defined in subclause 6.5 in 3GPP TS 32.290 [58].

It includes the following functionalities:

– Create resource at service establishment based on the request from NF consumer;

– During the service consumption lifecycle, update resource based on the request from NF consumer;

– Release upon service termination;

– Charging information record generation.

5.3.2 Service Operations

5.3.2.1 Introduction

The service operations defined for Nchf_OfflineOnlyCharging are shown in table 5.3.2.1-3.

Table 5.3.2.1-4: Nchf_OfflineOnlyCharging Operations

Service Operation Name	Description	Initiated by	Corresponding Offline only charging messages in 3GPP TS 32.290[58]
Nchf_OfflineOnlyCharging_Create	Initial report of service usage.	NF consumer	Charging Data Request/Response [Initial]
Nchf_OfflineOnlyCharging_Update	Intermediate report of service usage.	NF consumer	Charging Data Request/Response [Update]
Nchf_OfflineOnlyCharging_Release	Last report of service usage.	NF consumer	Charging Data Request/Response [Termination]

5.3.2.2 Nchf_OfflineOnlyCharging_Create Operation

The Nchf_OfflineOnlyCharging_Create operation provides means for NF (CTF) to request initial report of service usage.

The following procedures using the Nchf_OfflineOnlyCharging_Create service operation are supported:

– No existing charging data resource.

Figure 5.3.2.2-1: Nchf_OfflineOnlyCharging_Create Service Operation

1. NF (CTF) sends a Nchf_OfflineOnlyCharging_Create request to the CHF to create resource for starting charging.

2a. At successful operation, "201 Created" response is returned. In the "201 Created" response, the CHF includes a Location header field in the body. The Location header field shall contain the URI of the created resource. The NF (CTF) shall use the URI received in the Location header in subsequent requests to the CHF for the same PDU session.

2b. On failure or redirection, one of the HTTP status code listed in Table 6.2.3.2.3.1-3 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.2.7.3-1.

5.3.2.3 Nchf_OfflineOnlyCharging_Update Operation

The Nchf_OfflineOnlyCharging_Update operation provides means for NF (CTF) to update the charging data.

The following procedures using the Nchf_OfflineOnlyCharging_Update service operation are supported:

– charging events occur.

Figure 5.3.2.3-1: Nchf_OfflineOnlyCharging_Update Service Operation

1. NF (CTF) sends a Nchf_OfflineOnlyCharging_Update request to the CHF. The {OfflineChargingDataRef} in the URI identifies the "Offline Only Charging Data" to be updated. The used service unit is included in the request body.

2a. At successful operation, "200 OK" response is returned.

2b. On failure or redirection, one of the HTTP status code listed in Table 6.2.3.3.4.2.2-2 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.2.7.3-1.

5.3.2.4 Nchf_OfflineOnlyCharging_Release Operation

The Nchf_OfflineOnlyCharging_Release service operation provides means for NF (CTF) to terminate charging Session.

The following procedures using the Nchf_OfflineOnlyCharging_Release service operation are supported.

Figure 5.3.2.4-1: Nchf_OfflineOnlyCharging_Release Service Operation

1. NF(CTF) sends a Nchf_OfflineOnlyCharging_Release request to the CHF. The {OfflineChargingDataRef} in the URI identifies the "Offline Only Charging Data" to be updated and then released. The final used service unit is included in the request body.

2a. At successful operation, "204 No Content" response is returned.

2b. On failure or redirection, one of the HTTP status code listed in Table 6.2.3.3.4.3.2-2 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.2.7.3-1.