Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.222  Word version:  19.3.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   6.3…   6.4…   7…   8…   8.5…   8.8…   8.9…   8.13…   8.17…   8.21…   8.25…   8.26…   8.28…   8.30…   9…   10…   10.4…   10.7…   11…   A   B…   B.2…   B.3…   C…   D…

 

8.28  Registering the API provider domain functions on the CAPIF |R16|p. 93

8.28.1  Generalp. 93

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

8.28.2  Information flowsp. 93

8.28.2.1  Registration requestp. 93

Table 8.28.2.1-1 describes the information flow, registration request, from the API management function to the CAPIF core function.
Information element Status Description
List of API provider domain functionsMList of API provider domain functions including role (e.g. AEF, APF, AMF) and, if required, specific security information.
API provider nameOThe API provider name uniquely identifies an API provider (e.g. Internet Service Provider).
Security informationMInformation for CAPIF core function to validate the registration request
Up

8.28.2.2  Registration responsep. 94

Table 8.28.2.2-1 describes the information flow, registration response, from the CAPIF core function to the API management function.
Information element Status Description
List of identitiesM
(see NOTE 1)
List of identities, for each successfully registered API provider domain function and any specific security information.
Security informationOInformation to be used by the API provider domain function in subsequent CAPIF API invocations. Provided when registration is successful.
ReasonO
(see NOTE 2)
Information related to registration 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 request is successful.
NOTE 2:
Information element may be present when at least one registration requests fail.
Up

8.28.3  Procedurep. 94

Figure 8.28.3-1 illustrates the procedure for registering API provider domain functions on the CAPIF core function.
Reproduction of 3GPP TS 23.222, Fig. 8.28.3-1: Procedure for registration of API provider domain functions on CAPIF
Up
Step 1.
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.
Step 2.
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.
Step 3.
The CAPIF core function sends the generated information in the registration response message to the API management function.
Step 4.
The API management function configures the received information to the individual API provider domain functions.
Up

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

8.29.1  Generalp. 95

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 flowsp. 95

8.29.2.1  Registration update requestp. 95

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 updateMList of API provider domain functions requiring updates, including role (e.g. AEF, APF, AMF) and, if required, specific security information.
Security informationMInformation for CAPIF core function to validate the registration request
Up

8.29.2.2  Registration update responsep. 95

Table 8.29.2.2-1 describes the information flow, registration update response, from the CAPIF core function to the API management function.
Information element Status Description
List of identitiesM
(see NOTE 1)
List of identities, for each successfully updated API provider domain function and any specific security information.
Security informationOInformation to be used by the API provider domain function in subsequent CAPIF API invocations. Provided when registration update is successful.
ReasonO
(see NOTE 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.
Up

8.29.3  Procedurep. 96

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
Up
Step 1.
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.
Step 2.
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.
Step 3.
The CAPIF core function sends the updated information in the registration update response message to the API management function.
Step 4.
The API management function configures the received information to the individual API provider domain functions.
Up

Up   Top   ToC