Content for &nbsp; TS 23.222 &nbsp; Word version:&nbsp; 18.2.0

For registration of API provider domain functions on the CAPIF core function, the API management function sends a registration request to the CAPIF core function. The registration request contains a list of information about all the API provider domain functions, which require registration on the CAPIF core function.

The CAPIF core function validates the received request and generates the identity and other security related information for all the API provider domain functions listed in the registration request.

The CAPIF core function sends the generated information in the registration response message to the API management function.

Table 8.29.2.1-1: Registration update request

The API management function configures the received information to the individual API provider domain functions.

8.29 Update registration information of the API provider domain functions on the CAPIF |R16| p. 88

8.29.1 General p. 88

The procedure in this subclause corresponds to the architectural requirements for update of the registration information of the API provider domain functions on the CAPIF.

8.29.2 Information flows p. 88

8.29.2.1 Registration request p. 88

Table 8.29.2.1-1 describes the information flow, registration update request, from the API management function to the CAPIF core function.

Information Element	Status	Description
List of API provider domain functions requiring update	M	List of API provider domain functions requiring updates, including role (e.g. AEF, APF, AMF) and, if required, specific security information.
Security information	M	Information for CAPIF core function to validate the registration request

8.29.2.2 Registration update response p. 88

Table 8.29.2.2-1 describes the information flow, registration update response, from the CAPIF core function to the API management function.

Table 8.29.2.2-1: Registration response

Information Element	Status	Description
List of identities	M (1)	List of identities, for each successfully updated API provider domain function and any specific security information.
Security information	O	Information to be used by the API provider domain function in subsequent CAPIF API invocations. Provided when registration update is successful.
Reason	O (2)	Information related to registration update result specific to individual API provider domain functions. Provided when the registration fails.
NOTE 1: Information element shall be present when at least one registration update request is successful. NOTE 2: Information element may be present when at least one registration update requests fail.

8.29.3 Procedure p. 89

Figure 8.29.3-1 illustrates the procedure for updating the registration information of the API provider domain functions on the CAPIF core function.

Reproduction of 3GPP TS 23.222, Fig. 8.29.3-1: Procedure for update of registration information of API provider domain functions on CAPIF

Figure 8.29.3-1: Procedure for update of registration information of API provider domain functions on CAPIF

For updating the registration information of API provider domain functions on the CAPIF core function, the API management function sends a registration update request to the CAPIF core function. The registration update request contains a list of information about all the API provider domain functions, which require registration update on the CAPIF core function.

The CAPIF core function validates the received request and updates the identity and other security related information for all the API provider domain functions listed in the registration request.

The CAPIF core function sends the updated information in the registration update response message to the API management function.

Table 8.30.2.1-1: Deregistration request

The API management function configures the received information to the individual API provider domain functions.

8.30 Deregistering the API provider domain functions on the CAPIF |R16| p. 90

8.30.1 General p. 90

The procedure in this subclause corresponds to the architectural requirements for deregistering the API provider domain functions on the CAPIF. This procedure deregisters the API provider domain functions as authorized users of the CAPIF functionalities.

8.30.2 Information flows p. 90

8.30.2.1 Deregistration request p. 90

Table 8.30.2.1-1 describes the information flow, deregistration request, from the API management function to the CAPIF core function.

Information Element	Status	Description
Security information	M	Information for CAPIF core function to validate the deregistration request

8.30.2.2 Deregistration response p. 90

Table 8.30.2.2-1 describes the information flow, deregistration response, from the CAPIF core function to the API management function.

Table 8.30.2.2-1: Deregistration response

Information Element	Status	Description
Result	M	Indicates the success or failure of the deregistration operation

8.30.3 Procedure p. 90

Figure 8.30.3-1 illustrates the procedure for deregistering API provider domain functions on the CAPIF core function.

Reproduction of 3GPP TS 23.222, Fig. 8.30.3-1: Procedure for deregistration of API provider domain functions on CAPIF

Figure 8.30.3-1: Procedure for deregistration of API provider domain functions on CAPIF

For deregistration of API provider domain functions on the CAPIF core function, the API management function sends a deregistration request to the CAPIF core function.

The CAPIF core function validates the received request and processes the deregistration request.

The CAPIF core function sends a deregistration response message to the API management function.

Figure 8.31.3-1: Procedure for API invoker obtaining authorization from resource owner

The API management function processes the deregistration to the individual API provider domain functions.

8.31 API invoker obtaining authorization from resource owner |R18| p. 91

8.31.1 General p. 91

CAPIF may authorize the API invoker to invoke the service API based on the authorization information from the resource owner given before the API invocation.

Clause 8.31.3 shows the procedure for obtaining the authorization information.

8.31.2 Information flows p. 91

8.31.3 Procedure p. 91

Figure 8.31.3-1 illustrates the procedure for API invoker obtaining authorization from resource owner.

Pre-conditions:

The resource owner can communicate with the API invoker.

Reproduction of 3GPP TS 23.222, Fig. 8.31.3-1: Procedure for API invoker obtaining authorization from resource owner

The API invoker requests authorization information to invoke the service API.

Figure 8.32.3-1: Procedure for obtaining authorization information in a nested API invocation

The API invoker sends service API invocation request to the API exposing function with the authorization information received in step 1.

8.32 Reducing authorization information inquiry in a nested API invocation |R18| p. 92

8.32.1 General p. 92

The nested API invocation scenario is a scenario where the first API invocation towards the API exposing function 1 triggers this API exposing function to request another API invocation towards the API exposing function 2, which is in the same API provider domain that the API exposing function 1. Some service APIs may require invoking another service APIs. For example, if the API invoker invokes SEAL locationInfoRetrieval API, the location management server (acting as an API exposing server for the API invoker and as an API invoker for the NEF) may invoke NEF API to retrieve UE location information from 5GC. The CAPIF may reduce the authorization information inquiries for a nested API invocation scenario using procedure described in clause 8.32.3.

8.32.2 Information flows p. 92

8.32.3 Procedure p. 92

Figure 8.32.3-1 illustrates the procedure to obtain authorization information in a nested API invocation, in which an API exposing function receiving the service API invocation request interacts with another API exposing function to provide the service.

Pre-conditions:

The resource owner can communicate with the API invoker.
The API exposing functions 1 and 2 are in the same trust domain.

Reproduction of 3GPP TS 23.222, Fig. 8.32.3-1: Procedure for obtaining authorization information in a nested API invocation

The API invoker requests authorization information to invoke the service API exposed by the API exposing function 1.

The API invoker sends service API invocation request to the API exposing function 1 with the authorization information received in step 1.

Based on the service API invocation request, the API exposing function 1 decides to invoke another service API exposed by the API exposing function 2.