hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.3.2.1 Service API publish request
| Table 8.3.2.1-1 describes the information flow service API publish request from the API publishing function to the CAPIF core function.
Table 8.3.2.1-1: Service API publish request
Information element
Status
Description
API publisher information
M
The information of the API publisher may include identity, authen... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.3.2.2 Service API publish response
| Table 8.3.2.2-1 describes the information flow service API publish response from the CAPIF core function to the API publishing function.
Table 8.3.2.2-1: Service API publish response
Information element
Status
Description
Result
M
Indicates the success or failure of publishing the service API information
Servic... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.3.3 Procedure
| Figure 8.3.3-1 illustrates the procedure for publishing the service APIs. The service API publish mechanism is supported by the CAPIF core function.
Pre-conditions:
1. Authorization details of the APF are available with the CAPIF core function.
2. API invokers may have subscribed with the CAPIF core function to obt... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.4 Unpublish service APIs
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.4.1 General
| The CAPIF supports unpublishing service APIs by the API provider. Once the service API information is unpublished, it is no more available to be discovered by API invokers. The API publishing function can be within PLMN trust domain or within 3rd party trust domain.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.4.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.4.2.1 Service API unpublish request
| Table 8.4.2.1-1 describes the information flow service API unpublish request from the API publishing function to the CAPIF core function.
Table 8.4.2.1-1: Service API unpublish request
Information element
Status
Description
API publisher information
M
The information of the API publisher may include identity, au... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.4.2.2 Service API unpublish response
| Table 8.4.2.2-1 describes the information flow service API unpublish response from the CAPIF core function to the API publishing function.
Table 8.4.2.2-1: Service API unpublish response
Information element
Status
Description
Result
M
Indicates the success or failure of unpublishing the service API information
... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.4.3 Procedure
| Figure 8.4.3-1 illustrates the procedure for unpublishing the service APIs. The service API unpublish mechanism is supported by the CAPIF core function.
Pre-conditions:
1. Authorization details of the APF are available with the CAPIF core function.
2. API invokers may have subscribed with the CAPIF core function to... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.5 Retrieve service APIs
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.5.1 General
| The CAPIF supports retrieving the published service APIs information by the API provider. The API publishing function can be within PLMN trust domain or within 3rd party trust domain.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.5.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.5.2.1 Service API get request
| Table 8.5.2.1-1 describes the information flow service API get request from the API publishing function to the CAPIF core function.
Table 8.5.2.1-1: Service API get request
Information element
Status
Description
API publisher information
M
The information of the API publisher may include identity, authentication... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.5.2.2 Service API get response
| Table 8.5.2.2-1 describes the information flow service API get response from the CAPIF core function to the API publishing function.
Table 8.5.2.2-1: Service API get response
Information element
Status
Description
Result
M
Indicates the success or failure of retrieving the service API information
Cause
O
The ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.5.3 Procedure
| Figure 8.5.3-1 illustrates the procedure for retrieving the service APIs. The service API retrieval mechanism is supported by the CAPIF core function.
Pre-condition:
1. Authorization details of the APF are available with the CAPIF core function.
Figure 8.5.3-1: Retrieve service APIs
1. The API publishing functio... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.6 Update service APIs
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.6.1 General
| The CAPIF core function allows the service API provider to update the information related to the published service API, e.g. a change in the characteristics of the service API. This procedure is initiated by the API publishing function to the CAPIF core function. The API publishing function can be within PLMN trust dom... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.6.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.6.2.1 Service API update request
| Table 8.6.2.1-1 describes the information flow service API update request from the API publishing function to the CAPIF core function.
Table 8.6.2.1-1: Service API update request
Information element
Status
Description
API publisher information
M
The information of the API publisher may include identity, authenti... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.6.2.2 Service API update response
| Table 8.6.2.2-1 describes the information flow service API update response from the CAPIF core function to the API publishing function.
Table 8.6.2.2-1: Service API update response
Information element
Status
Description
Result
M
Indicates the success or failure of updating the service API information
Cause
O
... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.6.3 Procedure
| Figure 8.6.3-1 illustrates the procedure for updating the published service APIs information. The service API update mechanism is supported by the CAPIF core function.
Pre-conditions:
1. Authorization details of the APF are available with the CAPIF core function.
2. API invokers may have subscribed with the CAPIF c... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.7 Discover service APIs
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.7.1 General
| The following procedure in this subclause corresponds to the architectural requirements on discover service APIs. This procedure may be invoked by different types of API invokers (i.e., application management client, hosted application) at different phases (i.e., hosted application development, test phase and hosted ap... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.7.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.7.2.1 Service API discover request
| Table 8.7.2.1-1 describes the information flow service API discover request from the API invoker to the CAPIF core function.
Table 8.7.2.1-1: Service API discover request
Information element
Status
Description
API invoker identity information
M
Identity information of the API invoker discovering service APIs
Q... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.7.2.2 Service API discover response
| Table 8.7.2.2-1 describes the information flow service API discover response from the CAPIF core function to the API invoker.
Table 8.7.2.2-1: Service API discover response
Information element
Status
Description
Result
M
Indicates the success or failure of the discovery of the service API information
Service AP... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.7.3 Procedure
| Figure 8.7.3-1 illustrates the procedure for discover service APIs.
The service API discovery mechanism is supported by the CAPIF core function.
Pre-conditions:
1. The API invoker is onboarded and has received an API invoker identity.
2. The CAPIF core function is configured with a discovery policy information (e.g... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8 Subscription, unsubscription and notifications for the CAPIF events
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.1 General
| The CAPIF core function enables the subscribing entity (i.e. the API invoker, the API exposing function, the API publishing function, the API management function) to subscribe to and unsubscribe from the CAPIF events such as availability events of service APIs, change in service API information, monitoring service API ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2.1 Event subscription request
| Table 8.8.2.1-1 describes the information flow for event subscription request from the subscribing entity to the CAPIF core function.
Table 8.8.2.1-1: Event subscription request
Information element
Status
Description
Identity subscription information
M
The information to determine the identity of the subscribing... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2.2 Event subscription response
| Table 8.8.2.2-1 describes the information flow for event subscription response from the CAPIF core function to the subscribing entity.
Table 8.8.2.2-1: Event subscription response
Information element
Status
Description
Result
M
Indicates the success or failure of the event subscription operation
Cause
O
The c... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2.3 Event notification
| Table 8.8.2.3-1 describes the information flow for event notification from the CAPIF core function to the subscribing entity. A notification about an event is sent to a subscribing entity if the event subscription information in the related subscription match the corresponding attributes of the event content.
Table 8.... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2.4 Event notification acknowledgement
| Table 8.8.2.4-1 describes the information flow event notification acknowledgement from the subscribing entity to the CAPIF core function.
Table 8.8.2.4-1: Event notification acknowledgement
Information element
Status
Description
Acknowledgement
M
Acknowledgement for the event notification received.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2.5 Event unsubscription request
| Table 8.8.2.5-1 describes the information flow for event unsubscription request from the subscribing entity to the CAPIF core function.
Table 8.8.2.5-1: Event unsubscription request
Information element
Status
Description
Identity information
M
The information to determine the identity of the subscribing entity
... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2.6 Event unsubscription response
| Table 8.8.2.6-1 describes the information flow for event unsubscription response from the CAPIF core function to the subscribing entity.
Table 8.8.2.6-1: Event unsubscription response
Information element
Status
Description
Result
M
Indicates the success or failure of the event unsubscription operation
Cause
O
... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2.7 Event subscription update request
| Table 8.8.2.7-1 describes the information flow for event subscription update request from the subscribing entity to the CAPIF core function.
Table 8.8.2.7-1: Event subscription update request
Information element
Status
Description
Identity information
M
The information to determine the identity of the subscribin... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.2.8 Event subscription update response
| Table 8.8.2.8-1 describes the information flow for event subscription update response from the CAPIF core function to the subscribing entity.
Table 8.8.2.2-1: Event subscription update response
Information element
Status
Description
Result
M
Indicates the success or failure of the event subscription update opera... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.3 Procedure for CAPIF event subscription
| Figure 8.8.3-1 illustrates the procedure for CAPIF events subscription.
Pre-conditions:
1. The subscribing entity has the authorization to subscribe for the CAPIF events.
Figure 8.8.3-1: Procedure for CAPIF event subscription
1. The subscribing entity sends an event subscription request to the CAPIF core functi... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.4 Procedure for CAPIF event notifications
| Figure 8.8.4-1 illustrates the procedure for CAPIF event notifications.
Pre-conditions:
1. The subscription procedure as illustrated in figure 8.8.3-1 is performed by the subscribing entity.
Figure 8.8.4-1: Procedure for CAPIF event notifications
1. The CAPIF core function may detect events to be consumed by th... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.5 Procedure for CAPIF event unsubscription
| Figure 8.8.5-1 illustrates the procedure for CAPIF event unsubscription.
Pre-condition:
1. The subscribing entity has subscribed to the CAPIF events.
Figure 8.8.5-1: Procedure for CAPIF event unsubscription
1. The subscribing entity sends an event unsubscription request to the CAPIF core function with the informa... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.8.6 List of CAPIF events
| Table 8.8.6-1 provides a non-exhaustive list of CAPIF events.
Table 8.8.6-1: List of CAPIF events
Events
Events Description
Availability of service APIs
Availability events of service APIs (e.g. active, inactive)
Service API updated
Events related to change in service API information
Monitoring service API invo... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.9 Revoking subscription of the CAPIF events
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.9.1 General
| The CAPIF core function allows to revoke subscription of CAPIF events for the subscribing entity related to the service API changes, such as availability events of service APIs, change in service API information, monitoring service API invocations, API invoker onboarding events, etc. This procedure is initiated by the ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.9.2 Information flows
| This subclause describes the information flows for CAPIF event subscription revocation.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.9.2.1 Subscription revoke notification
| Table 8.9.2.1-1 describes the information flow for subscription revoke notification from the CAPIF core function to the subscribing entity.
Table 8.9.2.1-1: Subscription revoke notification
Information element
Status
Description
Identity information
M
The information to determine the identity of the subscribing ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.9.2.2 Subscription revoke notification acknowledgement
| Table 8.9.2.2-1 describes the information flow for subscription revoke notification acknowledgement from the subscribing entity to the CAPIF core function.
Table 8.9.2.2-1: Subscription revoke notification acknowledgement
Information element
Status
Description
Acknowledgement
M
The acknowledgement for the receiv... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.9.3 Procedure
| Figure 8.9.3-1 illustrates the procedure for subscription revocation, triggered by the CAPIF core function.
Pre-conditions:
1. The subscribing entity has previously subscribed to CAPIF event(s) to the CAPIF core function.
Figure 8.9.3-1: Procedure for revoking subscription of the CAPIF events
1. The CAPIF core fu... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.10 Authentication between the API invoker and the CAPIF core function
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.10.1 General
| The procedure in this subclause corresponds to the architectural requirements for authentication between the API invoker and the CAPIF core function.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.10.2 Information flows
| NOTE: The security aspects of this procedure are specified in subclause 6.2 and subclause 6.3.1 of 3GPP TS 33.122 [12].
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.10.3 Procedure
| Figure 8.10.3-1 illustrates the procedure for authentication between the API invoker and the CAPIF core function.
Pre-conditions:
1. The API invoker is onboarded with the CAPIF core function and the API invoker profile is created.
Figure 8.10.3-1: Procedure for authentication between the API invoker and the CAPI... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.11 API invoker obtaining authorization to access service API
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.11.1 General
| The API invoker requires to execute this procedure when it needs to obtain or re-obtain (e.g. upon expiry of the authorization information) the authorization to access the service API. Once the API invoker receives the authorization to access the service API, the API invoker can perform one or multiple service API invo... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.11.2 Information flows
| NOTE: The security aspects of this procedure are specified in subclause 6.4 and subclause 6.5.2 of 3GPP TS 33.122 [12].
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.11.3 Procedure
| Figure 8.11.3-1 illustrates the procedure for obtaining authorization to access the service API.
Pre-condition:
1. The API invoker is onboarded and has received an API invoker identity.
Figure 8.11.3-1: Procedure for the API invoker obtaining authorization for service API access
1. The API invoker sends an obtain... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.12 AEF obtaining service API access control policy
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.12.1 General
| The CAPIF core function is the central repository of all the policies related to service APIs. The AEF executes this procedure when it needs to obtain the policy to perform access control on the service API invocations (e.g. when policy for performing access control on service API is unavailable at the AEF). The AEF ca... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.12.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.12.2.1 Obtain access control policy request
| Table 8.12.2.1-1 describes the information flow obtain access control policy request from the AEF to the CAPIF core function.
Table 8.12.2.1-1: Obtain access control policy request
Information element
Status
Description
AEF Identity information
M
Identity information of the entity requesting the access control p... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.12.2.2 Obtain access control policy response
| Table 8.12.2.2-1 describes the information flow obtain access control policy response from the CAPIF core function to the AEF.
Table 8.12.2.2-1: Obtain access control policy response
Information element
Status
Description
Result
M
Indicates the success or failure of the obtain access control policy operation
Ac... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.12.3 Procedure
| Figure 8.12.3-1 illustrates the procedure for obtaining policy to perform access control on the service API invocations.
Pre-conditions:
1. The AEF is hosting the service API but the policy to perform access control is not available with AEF.
2. The CAPIF core function is configured with the access control policies... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.13 Topology hiding
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.13.1 General
| The procedure in this subclause corresponds to the architectural requirements for hiding the topology of the PLMN trust domain from the API invokers accessing the service APIs from outside the PLMN trust domain.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.13.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.13.2.1 Service API invocation request (API invoker – AEF-1)
| The information flow service API invocation request from the API invoker to AEF-1 (AEF acting as service communication entry point) is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.17.2.1-1 describes the CAPIF related information elem... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.13.2.2 Service API invocation request (AEF-1 – AEF-2)
| The information flow service API invocation request from AEF-1 (AEF acting as service communication entry point) to AEF-2 (destination AEF for handling service API) is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.17.2.1-1 describes t... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.13.2.3 Service API invocation response (AEF-2 – AEF-1)
| The information flow service API invocation response from AEF-2 (destination AEF for handling service API) to AEF-1 (AEF acting as service communication entry point) is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.17.2.2-1 describes... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.13.2.4 Service API invocation response (AEF-1 – API invoker)
| The information flow service API invocation response from AEF-1 (AEF acting as service communication entry point) to the API invoker is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.17.2.2-1 describes the CAPIF related information el... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.13.3 Procedure
| Figure 8.13.3-1 illustrates the procedure for CAPIF topology hiding.
Pre-conditions:
1. The API invoker has performed the service discovery and received the details of the service API which includes the information about the service communication entry point of the AEF-1 in the CAPIF.
2. The API invoker is authentic... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.14 Authentication between the API invoker and the AEF prior to service API invocation
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.14.1 General
| The procedure in this subclause corresponds to the architectural requirements for authentication of the API invoker by the AEF.
To reduce latency during API invocation, the API invoker associated authentication information can be made available at the AEF after authentication between the API invoker and the CAPIF core... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.14.2 Information flows
| NOTE: The security aspects of this procedure are specified in subclause 6.4 and subclause 6.5.2 of 3GPP TS 33.122 [12].
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.14.3 Procedure
| Figure 8.14.3-1 illustrates the procedure for authentication between the API invoker and the AEF.
Pre-conditions:
1. Optionally, the CAPIF core function has shared the information required for authentication of the API invoker with the AEF.
Figure 8.14.3-1: Procedure for authentication between the API invoker and ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.15 Authentication between the API invoker and the AEF upon the service API invocation
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.15.1 General
| The procedure in this subclause corresponds to the architectural requirements for authentication of the API invoker by the AEF upon the service API invocation.
To reduce latency during API invocation, the API invoker associated authentication information can be made available at the AEF after authentication between th... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.15.2 Information flows
| NOTE: The security aspects of this procedure are specified in subclause 6.4 and subclause 6.5.2 of 3GPP TS 33.122 [12].
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.15.2.1 Service API invocation request with authentication information
| The information flow service API invocation request with authentication information from the API invoker to the AEF is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.15.2.1-1 describes only the CAPIF related information elements which ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.15.2.2 Service API invocation response
| The information flow service API invocation response from the AEF to the API invoker is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.15.2.2-1 describes only the CAPIF related information elements which are included in the service AP... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.15.3 Procedure
| Figure 8.15.3-1 illustrates the procedure for authentication of the API invoker by the AEF, where the authentication information is carried in the API invocation request.
Pre-conditions:
1. Optionally, the CAPIF core function has shared the information required for authentication of the API invoker with the AEF.
... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.16 Service API invocation with AEF authorization
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.16.1 General
| The procedure in this subclause corresponds to the architectural requirements to validate authorization of API invokers upon the service API invocation.
To reduce latency during API invocation, the API invoker associated authorization information can be made available at the AEF after authentication between the API in... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.16.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.16.2.1 Service API invocation request
| The information flow service API invocation request from the API invoker to the AEF is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.16.2.1-1 describes only the CAPIF related information elements which are included in the service API ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.16.2.2 Service API invocation response
| The information flow service API invocation response from the AEF to the API invoker is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.16.2.2-1 describes only the CAPIF related information elements which are included in the service AP... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.16.2.3 Obtain API invoker information request
| Table 8.16.2.3-1 describes the information flows to request security information of the API invoker using the Obtain API Invoker information request from the AEF to the CAPIF Core Function.
Table 8.16.2.3-1: Obtain API invoker information request
Information element
Status
Description
API invoker identity informat... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.16.2.4 Obtain API invoker information response
| Table 8.16.2.3-1 describes only the information flows returned from the CAPIF Core Function to the AEF with the security method(s) information for the API Invoker.
Table 8.16.2.4-1: Obtain API Invoker information response
Information element
Status
Description
Result
M
Indicates the success or failure of service... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.16.3 Procedure
| Figure 8.16.3-1 illustrates the procedure for API invoker authorization to access service APIs.
Pre-conditions:
1. The API invoker has been authenticated.
2. The API invoker associated authorization information is available at AEF.
Figure 8.16.3-1: Procedure for API invoker authorization to access service API... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.17 CAPIF access control
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.17.1 General
| The CAPIF controls the access of service API by the API invoker based on policy or usage limits.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.17.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.17.2.1 Service API invocation request
| The information flow service API invocation request from the API invoker to the AEF is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.17.2.1-1 describes only the CAPIF related information elements which are included in the service API ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.17.2.2 Service API invocation response
| The information flow service API invocation response from the AEF to the API invoker is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.17.2.2-1 describes only the CAPIF related information elements which are included in the service AP... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.17.3 Procedure
| Figure 8.17.3-1 illustrates the procedure for service API access control.
Pre-conditions:
1. The API invoker has performed the service API discovery and received the details of the service API which includes the information about the service communication entry point of the AEF in the CAPIF.
2. The API invoker is au... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.18 CAPIF access control with cascaded AEFs
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.18.1 General
| The procedure in this subclause corresponds to the architectural requirements related to some common access control requirements for service API invocations. It provides access control, based on two cascaded API Exposing Function (AEF) instances. While one AEF instance provides the entry point for the service API and a... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.18.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.18.2.1 Service API invocation request
| The information flow service API invocation request from the API invoker to the AEF and between AEFs is service API specific and the complete detail of the service API invocation request is out of scope of the present document. Table 8.17.2.1-1 describes the CAPIF related information elements which are included in the ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.18.2.2 Service API invocation response
| The information flow service API invocation response from the AEF to the API invoker and between AEFs is service API specific and the complete detail of the service API invocation response is out of scope of the present document. Table 8.17.2.2-1 describes the CAPIF related information elements which are included in th... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.18.3 Procedure
| Figure 8.18.3-1 illustrates the procedure for CAPIF access control.
Pre-conditions:
1. The API invoker has performed the service discovery and received the details of the service API which includes the information about the service communication entry point of the AEF-1 in the CAPIF.
2. The API invoker is authentica... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.