8.20 Charging the invocation of service APIs

23.2223GPPCommon API Framework for 3GPP Northbound APIsRelease 18TS

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

8.20.1 General

The procedure in this subclause corresponds to the architectural requirements for charging the invocation of service APIs. The AEF can be within PLMN trust domain or within 3^rd party trust domain.

8.20.2 Information flows

NOTE: It is in SA5 scope to develop the charging related information flows for this procedure.

Editor’s note: Reference to the appropriate SA5 specification is needed.

8.20.3 Procedure

Figure 8.20.3-1 illustrates the procedure for charging the invocation of service APIs.

Pre-conditions:

1. Authorization details of the AEF are available with the CAPIF core function.

Figure 8.20.3-1: Procedure for charging the invocation of service APIs

1. Upon invocation of service API(s) from one more API invokers, the AEF triggers an API invocation charging request and includes API invoker information (e.g. invoker’s ID and IP address, location, timestamp) and service API information (e.g. service API name and version, invoked operation, input parameters, invocation result) towards the CAPIF core function.

NOTE: These requests can be triggered asynchronously.

2. The CAPIF core function performs a charging procedure which includes storing the information for access by authorized API management.

3. The AEF receives the API invocation charging response from the CAPIF core function.