hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.19 Logging service API invocations
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.19.1 General
| The procedure in this subclause corresponds to the architectural requirements for logging service API invocations at AEF. The AEF can be within PLMN trust domain or within 3rd party trust domain.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.19.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.19.2.1 API invocation log request
| Table 8.19.2.1-1 describes the information flow API invocation log request from the API exposing function to the CAPIF core function.
Table 8.19.2.1-1: API invocation log request
Information element
Status
Description
API exposing identity information
M
Identity information of the AEF logging service API(s) invo... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.19.2.2 API invocation log response
| Table 8.19.2.2-1 describes the information flow API invocation log response from the CAPIF core function to the API exposing function.
Table 8.19.2.2-1: API invocation log response
Information element
Status
Description
Result
M
Indicates the success or failure of API(s) invocation log request
Cause
O
The cau... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.19.3 Procedure
| Figure 8.19.3-1 illustrates the procedure for logging service API invocations at AEF.
Pre-conditions:
1. The API invoker(s) has invoked certain service API(s).
2. Authorization details of the AEF are available with the CAPIF core function.
Figure 8.19.3-1: Procedure for logging service API invocations
1. Upon... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.20 Charging the invocation of service APIs
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 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 3rd party trust domain. The charging of the invocation of the CAPIF core function APIs and the charging of the invocation of service APIs is specif... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.20.2 Information flows
| NOTE: Charging aspects of CAPIF framework, i.e., charging architecture and information flows, are specified in 3GPP TS 32.254 [20].
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.20.3 Procedure
| NOTE: Charging aspects of CAPIF framework, i.e., charging architecture, information flows and deployment options, are specified in 3GPP TS 32.254 [20].
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.21 Monitoring service API invocation
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.21.1 General
| The procedure in this subclause corresponds to the architectural requirements for monitoring service API invocation.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.21.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.21.2.1 Monitoring service API event notification
| The information flow for the monitoring service API event notification from the CAPIF core function to the API management function is same as the event notification from the CAPIF core function to the subscribing entity. Table 8.8.2.3-1 describes the information elements which are included in the monitoring service API... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.21.2.2 Monitoring service API event notification acknowledgement
| The information flow for the monitoring service API event notification acknowledgement from the API management function to the CAPIF core function is same as the event notification acknowledgement from subscribing entity to the CAPIF core function. Table 8.8.2.4-1 describes the information elements which are included i... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.21.3 Procedure
| Figure 8.21.3-1 illustrates the procedure for monitoring service API invocation.
Pre-conditions:
1. The API management function has subscribed to monitoring event including filters such as invoker's ID and IP address, service API name and version, input parameters, and invocation result.
Figure 8.21.3-1: Procedu... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.22 Auditing service API invocation
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.22.1 General
| The procedure in this subclause corresponds to the architectural requirements for auditing service API invocation. This procedure can be used for auditing of other CAPIF interactions i.e. service API invocation events, API invoker onboarding events and API invoker interactions with the CAPIF (e.g. authentication, autho... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.22.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.22.2.1 Query service API log request
| Table 8.22.2.1-1 describes the information flow query service API log request from the API management function to the CAPIF core function.
Table 8.22.2.1-1: Query service API log request
Information element
Status
Description
Identity information
M
Identity information of the entity querying service API log requ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.22.2.2 Query service API log response
| Table 8.22.2.2-1 describes the information flow query service API log response from the CAPIF core function to the API management function.
Table 8.22.2.2-1: Query service API log response
Information element
Status
Description
Result
M
Indicates the success or failure of query service API log request
API invo... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.22.3 Procedure
| Figure 8.22.3-1 illustrates the procedure for auditing service API invocation.
Pre-conditions:
1. Service API invocation logs are available at the CAPIF core function.
2. Authorization details of the AMF are available with the CAPIF core function.
Figure 8.22.3-1: Procedure for auditing service API invocation
1... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23 CAPIF revoking API invoker authorization
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23.1 General
| The CAPIF controls the access of service API by the API invoker based on policy or usage limits. If the usage limits have exceeded, the authorization of the API invoker for accessing the service APIs is revoked. The decision to revoke the API invoker authorization may be triggered by the AEF or the CAPIF core function.... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23.2.1 Revoke API invoker authorization request
| Table 8.23.2.1-1 describes the information flow revoke API invoker authorization request from the API exposing function to the CAPIF core function or from the CAPIF core function to the API exposing function.
Table 8.23.2.1-1: Revoke API invoker authorization request
Information element
Status
Description
API invo... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23.2.2 Revoke API invoker authorization response
| Table 8.23.2.2-1 describes the information flow revoke API invoker authorization response from the CAPIF core function to the API exposing function or from the API exposing function to the CAPIF core function.
Table 8.23.2.2-1: Revoke API invoker authorization response
Information element
Status
Description
Result... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23.2.3 Revoke API invoker authorization notify
| Table 8.23.2.3-1 describes the information flow revoke API invoker authorization notify from the CAPIF core function to the API invoker.
Table 8.23.2.3-1: Revoke API invoker authorization notify
Information element
Status
Description
API invoker identity information
M
The information that determines the identity... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23.2.4 Revoke API invoker authorization notify acknowledgement
| Table 8.23.2.4-1 describes the information flow revoke API invoker authorization notify acknowledgement from the API Invoker to the CAPIF core function.
Table 8.23.2.4-1: Revoke API invoker authorization notify acknowledgement
Information element
Status
Description
Acknowledgement
M
Acknowledgement for the revok... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23.3 Procedure for CAPIF revoking API invoker authorization initiated by AEF
| Figure 8.23.3-1 illustrates the procedure for revoking API invoker authorization to access service API initiated by the AEF.
Pre-conditions:
1. The API invoker is authenticated and authorized to use the service API.
2. The AEF in the CAPIF is configured with the access policy to be applied to the service API invocat... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.23.4 Procedure for CAPIF revoking API invoker authorization initiated by CAPIF core function
| Figure 8.23.4-1 illustrates the procedure for revoking API invoker authorization to access service API initiated by the CAPIF core function. This procedure is also used for revoking API invoker authorization supporting RNAA scenarios.
Pre-conditions:
1. The API invoker is authenticated and authorized to use the servi... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.24 API topology hiding management
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.24.1 General
| The following procedure in this subclause corresponds to the architectural requirements on API topology hiding. The procedure in this subclause supports API topology hiding by dynamically configuring the address of the AEF providing the Service API to the AEF entry point providing the topology hiding. The API publishin... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.24.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.24.2.1 API topology hiding notify
| Table 8.24.2.1-1 describes the information flow API topology hiding notify from the CAPIF core function to the API exposing function.
Table 8.24.2.1-1: API topology hiding notify
Information element
Status
Description
Service API identification
M
The identification information of the service API with the API top... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.24.3 Procedure
| Figure 8.24.3-1 illustrates the procedure for API topology hiding management by API (un)publish function.
Pre-condition:
1. Authorization details of the APF are available with the CAPIF core function.
2. The API exposing function has subscribed to CAPIF event for API topology hiding status.
Figure 8.24.3-1: A... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25 Support for CAPIF interconnection
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.1 General
| The procedures in this subclause corresponds to the architectural requirements on CAPIF interconnection.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.1 Interconnection API publish request
| Table 8.25.2.1-1 describes the information flow interconnection API publish request from CAPIF core function to CAPIF core function.
Table 8.25.2.1-1: Interconnection API publish request
Information element
Status
Description
CCF information
M
The information of the CAPIF core function which publishes APIs, may ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.2 Interconnection API publish response
| Table 8.25.2.2-1 describes the information flow interconnection API publish response from CAPIF core function to CAPIF core function.
Table 8.25.2.2-1: Interconnection API publish response
Information element
Status
Description
Result
M
Indicates the success or failure of publishing the service API information
... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.3 Interconnection service API discover request
| Table 8.25.2.3-1 describes the information flow interconnection service API discover request from one CAPIF core function to another CAPIF core function.
Table 8.25.2.3-1: Interconnection service API discover request
Information element
Status
Description
CAPIF core function identity information
M
Identity infor... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.4 Interconnection service API discover response
| Table 8.25.2.4-1 describes the information flow interconnection service API discover response from one CAPIF core function to another CAPIF core function.
Table 8.25.2.4-1: Interconnection service API discover response
Information element
Status
Description
Result
M
Indicates the success or failure of the discov... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.5 Interconnection API unpublish request
| Table 8.25.2.5-1 describes the information flow interconnection API unpublish request from a CAPIF core function to another CAPIF core function.
Table 8.25.2.5-1: Interconnection API unpublish request
Information element
Status
Description
CCF information
M
The information of the CAPIF core function which unpubl... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.6 Interconnection API unpublish response
| Table 8.25.2.6-1 describes the information flow interconnection API unpublish response from a CAPIF core function to another CAPIF core function.
Table 8.25.2.6-1: Interconnection API unpublish response
Information element
Status
Description
Result
M
Indicates the success or failure of unpublishing the service A... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.7 Interconnection get service API request
| Table 8.25.2.7-1 describes the information flow interconnection get service API request from a CAPIF core function to another CAPIF core function.
Table 8.25.2.7-1: Interconnection get service API request
Information element
Status
Description
CCF information
M
The information of the CAPIF core function that wan... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.8 Interconnection get service API response
| Table 8.25.2.8-1 describes the information flow interconnection get service API response from a CAPIF core function to another CAPIF core function.
Table 8.25.2.8-1: Interconnection get service API response
Information element
Status
Description
Result
M
Indicates the success or failure of getting the service AP... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.9 Interconnection update service API request
| Table 8.25.2.9-1 describes the information flow interconnection update service API request from a CAPIF core function to another CAPIF core function.
Table 8.25.2.9-1: Interconnection update service API request
Information element
Status
Description
CCF information
M
The information of the CCF requesting the upd... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.10 Interconnection update service API response
| Table 8.25.2.10-1 describes the information flow interconnection update service API response from a CAPIF core function to another CAPIF core function.
Table 8.25.2.10-1: Interconnection update service API response
Information element
Status
Description
Result
M
Indicates the success or failure of updating the s... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.11 Interconnection revoke API invoker authorization request
| Table 8.25.2.11-1 describes the information flow interconnection revoke API invoker authorization request from one CCF to another CCF.
Table 8.25.2.11-1: Interconnection revoke API invoker authorization request
Information element
Status
Description
CCF information
M
The information of the requesting CAPIF core ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.12 Interconnection revoke API invoker authorization response
| Table 8.25.2.12-1 describes the information flow interconnection revoke API invoker authorization response from one CCF to another CCF.
Table 8.25.2.12-1: Interconnection revoke API invoker authorization response
Information element
Status
Description
Result
M
Indicates the success or failure of interconnection ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.13 Interconnection revoke API invoker authorization notify
| Table 8.25.2.13-1 describes the information flow interconnection revoke API invoker authorization notify from one CCF to another CCF.
Table 8.25.2.13-1: Interconnection revoke API invoker authorization notify
Information element
Status
Description
CCF information
M
The information of the notifying CAPIF core fun... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.14 Interconnection obtain access control policy request
| Table 8.25.2.14-1 describes the information flow interconnection obtain access control policy request from one CCF to another CCF.
Table 8.25.2.14-1: Interconnection obtain access control policy request
Information element
Status
Description
Identity information
M
Identity information of the entity requesting th... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.15 Interconnection obtain access control policy response
| Table 8.25.2.15-1 describes the information flow interconnection obtain access control policy response from one CCF to another CCF.
Table 8.25.2.15-1: Interconnection obtain access control policy response
Information element
Status
Description
Result
M
Indicates the success or failure of the obtain access contro... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.16 Interconnection API invoker obtaining authorization to access service API
| NOTE: The security aspects of this procedure are specified in clause 6.13 of 3GPP TS 33.122 [12].
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.2.17 Interconnection Authentication and authorization between the API invoker and the AEF
| NOTE: The security aspects of this procedure are specified in clause 6.13 of 3GPP TS 33.122 [12].
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3 Procedure
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.1 Service API publish for CAPIF interconnection
| This subclause describes the procedure for service API publish for CAPIF interoperation.
Pre-condition:
1. CCF-A and CCF-B connect to each other, and either belong to the single trust domain of the same CAPIF provider or trust domains of different CAPIF providers.
2. CCF-B is configured as the designated CAPIF core ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.2 Service API discovery involving multiple CCFs
| This subclause describes a procedure for service API discovery involving multiple CCFs
Pre-condition:
1. CCF-A and CCF-B connect to each other, and either belong to the single trust domain of the same CAPIF provider or trust domains of different CAPIF providers.
2. When CCF-A and CCF-B belong to trust domains of dif... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.3 Service API discovery for CAPIF interconnection
| This subclause describes a procedure for service API discovery for CAPIF interconnection. The CCF-A and the CCF-B may belong to the same CAPIF provider domain or different CAPIF provider domains. When the CCF-A and the CCF‑B belong to different CAPIF provider domains, the two CAPIF providers shall have business agreeme... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.4 Service API unpublish for CAPIF interconnection
| This clause describes the procedure for service API unpublish for CAPIF interconnection.
Pre-condition:
1. CCF-A and CCF-B connect to each other, and either belong to the single trust domain of the same CAPIF provider or trust domains of different CAPIF providers. When CCF-A and CCF-B belong to trust domains of diffe... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.5 Retrieve service APIs for CAPIF interconnection
| This clause describes the procedure to retrieve service APIs information in a CAPIF interconnection scenario.
Pre-condition:
1. CCF-A and CCF-B connect to each other, and either belong to the single trust domain of the same CAPIF provider or trust domains of different CAPIF providers. When CCF-A and CCF-B belong to t... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.6 Update service APIs for CAPIF interconnection
| Figure 8.25.3.6-1 illustrates the procedure for updating the published service APIs information by a CAPIF core function.
Pre-conditions:
1. CCF-A and CCF-B connect to each other, and either belong to the single trust domain of the same CAPIF provider or trust domains of different CAPIF providers. When CCF-A and CCF-... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.7 API invoker obtaining authorization for service API access in CAPIF interconnection
| Pre-condition:
1. The API invoker has discovered service APIs provided by an AEF via procedure defined in step 1 and 2 of clause 8.25.3.2.
2. The API invoker and the CCF-B are in the same trusted domain.
3. The AEF and the CCF-A are in the same trusted domain.
4. The CCF-A and the CCF-B are connected to each other... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.8 Procedure for CAPIF revoking API invoker authorization in CAPIF interconnection
| Pre-conditions:
1. The API invoker is authenticated by CCF-B and authorized by CCF-B and CCF-A to use the service API. The API invoker has obtained authorization to use the service API as specified in clause 8.25.3.7.
2. The CCF-B may have available access control policies corresponding to the service API.
3. The CC... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.9 Procedure for obtaining access control policy in CAPIF interconnection
| Pre-condition:
1. The AEF is hosting the service API but the policy to perform access control is not available with AEF.
2. The CCF-B has available access control policies corresponding to one or more service APIs.
3. The AEF and the CCF-A are in the same trusted domain.
Figure 8.25.3.9-1: Procedure for obtaini... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.25.3.10 Procedure for obtaining security information in CAPIF interconnection
| Pre-condition:
1. The AEF has no security information available for authentication and/or authorization.
2. The CCF-B has security information available for authentication and/or authorization corresponding to one or more service APIs.
3. The AEF and the CCF-A are in the same trusted domain.
Figure 8.25.3.10-1: ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.26 Update API invoker's API list
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.26.1 General
| The procedure in this subclause corresponds to the architectural requirements for updating the API invoker's API list on the CAPIF core function. The CAPIF enables API invoker to update its own API list e.g. subsequent to discovering new API(s).
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.26.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.26.2.1 Update API invoker API list request
| Table 8.26.2.1-1 describes the information flow update API invoker API list request from the API invoker to the CAPIF core function.
Table 8.26.2.1-1: Update API invoker API list request
Information element
Status
Description
API invoker identity information
M
Identity information of the API invoker requesting u... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.26.2.2 Update API invoker API list response
| Table 8.26.2.2-1 describes the information flow update API invoker API list response from the CAPIF core function to the API invoker.
Table 8.26.2.2-1: Update API invoker API list response
Information element
Status
Description
Result
M
Indicates the success or failure of the update operation
API information
O... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.26.3 Procedure
| Figure 8.26.3-1 illustrates the procedure for updating the API invoker API list on the CAPIF.
Pre-conditions:
1. The API invoker has been onboarded as a recognized user of the CAPIF and associated API invoker profile is provisioned.
2. The API invoker has visibility to new APIs information (e.g. updates on API catal... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.27 Dynamically routing service API invocation
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.27.1 General
| The procedure in this subclause corresponds to the architectural requirements for dynamic routing of service API invocation. The CAPIF enables dynamically routing the service API invocation request based on the detailed information of the invocation. The AEF acting as service communication entry point and the destinati... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.27.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.27.2.1 Obtain routing information request
| Table 8.27.2.1-1 describes the information flow dynamic routing information request from the API exposing function to the CAPIF core function.
Table 8.27.2.1-1: Obtain routing information request
Information element
Status
Description
Service API identification
M
The identification information of the service API... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.27.2.2 Obtain routing information response
| Table 8.27.2.2-1 describes the information flow dynamic routing information response from the CAPIF core function to the API exposing function.
Table 8.27.2.2-1: Obtain routing information response
Information element
Status
Description
Service API identification information
M
The identification information of t... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.27.3 Procedure
| Figure 8.27.3-1 illustrates the procedure for dynamically routing the service API invocation from the AEF acting as service communication entry point to the destination AEF for handling service API.
Pre-conditions:
1. The API invoker has performed the service discovery and received the details of the service API whic... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.28 Registering the API provider domain functions on the CAPIF
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.28.1 General
| 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.
NOTE: The security aspects of this procedure are specified in 3GPP T... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.28.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.28.2.1 Registration request
| Table 8.28.2.1-1 describes the information flow, registration request, from the API management function to the CAPIF core function.
Table 8.28.2.1-1: Registration request
Information element
Status
Description
List of API provider domain functions
M
List of API provider domain functions including role (e.g. AEF,... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.28.2.2 Registration response
| Table 8.28.2.2-1 describes the information flow, registration response, from the CAPIF core function to the API management function.
Table 8.28.2.2-1: Registration response
Information element
Status
Description
List of identities
M
(see NOTE 1)
List of identities, for each successfully registered API provider ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.28.3 Procedure
| Figure 8.28.3-1 illustrates the procedure for registering API provider domain functions on the CAPIF core function.
Figure 8.28.3-1: Procedure for registration of API provider domain functions on CAPIF
1. For registration of API provider domain functions on the CAPIF core function, the API management function sends... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.29 Update registration information of the API provider domain functions on the CAPIF
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.29.1 General
| 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.
NOTE: The security aspects of this procedure are specified in 3GPP TS 33.122 [12] clauses 6.6 and 6.10.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.29.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.29.2.1 Registration update request
| Table 8.29.2.1-1 describes the information flow, registration update request, from the API management function to the CAPIF core function.
Table 8.29.2.1-1: Registration update request
Information element
Status
Description
List of API provider domain functions requiring update
M
List of API provider domain func... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.29.2.2 Registration update response
| 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 update response
Information element
Status
Description
List of identities
M
(see NOTE 1)
List of identities, for each successfully updated AP... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.29.3 Procedure
| Figure 8.29.3-1 illustrates the procedure for updating the registration information of the API provider domain functions on the CAPIF core function.
Figure 8.29.3-1: Procedure for update of registration information of API provider domain functions on CAPIF
1. For updating the registration information of API provide... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.30 Deregistering the API provider domain functions on the CAPIF
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.30.1 General
| 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.
NOTE: The security aspects of this procedure are specified in 3G... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.30.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.30.2.1 Deregistration request
| Table 8.30.2.1-1 describes the information flow, deregistration request, from the API management function to the CAPIF core function.
Table 8.30.2.1-1: Deregistration request
Information element
Status
Description
Security information
M
Information for CAPIF core function to validate the deregistration request
... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.30.2.2 Deregistration response
| 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
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.30.3 Procedure
| Figure 8.30.3-1 illustrates the procedure for deregistering API provider domain functions on the CAPIF core function.
Figure 8.30.3-1: Procedure for deregistration of API provider domain functions on CAPIF
1. For deregistration of API provider domain functions on the CAPIF core function, the API management function... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.31 API invoker obtaining authorization from resource owner
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.31.1 General
| 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.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.31.2 Information flows
| NOTE: The security aspects of this procedure are specified in TS 33.122 [12].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.