hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.5.1 Introduction
| This subclause specifies the OAM aspects including performance monitoring, fault monitoring, policy configurations, and certain lifecycle management aspects such as monitoring the running status of service APIs and related operations.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.5.2 Requirements
| [AR-4.5.2-a] The CAPIF shall provide mechanisms to monitor the status of service APIs, e.g. starting and stopping access of the service APIs.
[AR-4.5.2-b] The CAPIF shall provide mechanisms to monitor and report the performance of the service APIs.
[AR-4.5.2-c] The CAPIF shall provide mechanisms to monitor and report... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.5.3 Requirements for 3rd party API providers
| [AR-4.5.3-a] The CAPIF shall provide mechanisms to configure policies related to 3rd party service APIs by the authorized users.
[AR-4.5.3-b] The CAPIF shall provide mechanisms to monitor faults, performance and status of the 3rd party service APIs by the authorized users.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.6 Service API invocation monitoring
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.6.1 Introduction
| The CAPIF includes monitoring functions. This enables API provider to monitor service API invocations, to determine critical aspects such as system load, API usage information, uncover potential overload and attacks (e.g. DDoS) conditions.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.6.2 Requirements
| [AR-4.6.2-a] The CAPIF shall provide mechanisms to capture service API invocation events and make them available to service API provider.
[AR-4.6.2-b] The CAPIF shall provide mechanisms to notify events related to overload and threat conditions (e.g. system load, resource usage information).
[AR-4.6.2-c] The CAPIF sh... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.7 Logging
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.7.1 Introduction
| The CAPIF supports the ability to log events and store the corresponding logs. This enables the API providers to use the logs for the purpose of tracing back and statistical analysis.
The following events in CAPIF are supported for logging:
- Service API invocation events;
- API invoker onboarding events; and
- API... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.7.2 Logging events related to service API invocations
| [AR-4.7.2-a] The CAPIF shall provide mechanisms for service API invocation event logging and storage functionality.
[AR-4.7.2-b] The service API invocation log shall be stored for a configurable time period, according to the service API provider's policy.
[AR-4.7.2-c] The service API invocation log shall be stored se... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.7.3 Logging events related to API invoker onboarding
| [AR-4.7.3-a] The CAPIF shall provide mechanisms for API invoker onboarding event logging and storage functionality.
[AR-4.7.3-b] The API invoker onboarding log shall be stored at least for the duration during which the onboarding is valid.
[AR-4.7.3-c] The API invoker onboarding log shall be stored securely, and shal... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.7.4 Logging events related to API invoker interaction with the CAPIF
| [AR-4.7.4-a] The CAPIF shall provide mechanisms for the event logging of API invoker interactions with the CAPIF (e.g. authentication, authorization, discover service APIs).
[AR-4.7.4-b] The API invoker interactions log shall be stored for a configurable time period.
[AR-4.7.4-c] The API invoker interactions log shal... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.8 Auditing service API invocation
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.8.1 Introduction
| The CAPIF includes auditing capabilities. This enables the service API provider to identify illegal service API invocations e.g. by querying the service API invocation log.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.8.2 Requirements
| [AR-4.8.2-a] The CAPIF shall provide mechanisms to query the service API invocation log, by CAPIF administrators.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.9 Onboarding API invoker
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.9.1 Introduction
| This subclause specifies the requirements related to onboarding API invoker to the CAPIF.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.9.2 Requirements
| [AR-4.9.2-a] The CAPIF shall provide the capability to onboard new API invokers.
[AR-4.9.2-b] The CAPIF shall support granting an API invoker's request to onboard with the CAPIF administrator.
[AR-4.9.2-c] The CAPIF shall support offboarding an API invoker from the CAPIF.
[AR-4.9.2-d] The CAPIF shall support updatin... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.10 Policy configuration
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.10.1 Introduction
| This subclause specifies the policy configuration related requirements.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.10.2 Requirements
| [AR-4.10.2-a] The CAPIF shall support policy configurations (e.g. related to the protection of platforms and network, specific functionalities exposed, message payload size or throughput).
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.11 Protocol design
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.11.1 Introduction
| In order for the CAPIF to be common across all present and future API invokers for various usages and purposes, a minimum common protocol stack model is necessary so that all API invokers that use the common-framework-based API need to support only one and the same set of protocols, e.g. security layer protocol(s). Ext... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.11.2 Requirements
| [AR-4.11.2-a] The CAPIF shall support a minimum common protocol stack model common for all API implementations to be based on.
[AR-4.11.2-b] The CAPIF shall support a common security mechanism for all API implementations to provide confidentiality and integrity protection.
[AR-4.11.2-c] The CAPIF shall be extensible ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.12 Interconnection between the CAPIF providers
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.12.1 Introduction
| Two organizations with a business relationship that have each deployed CAPIF may need to interoperate to allow API invokers in each trust domain to utilize service APIs from both CAPIFs as illustrated in figure 4.12.1-1.
Figure 4.12.1-1: Interconnection between the CAPIF providers
NOTE: From each CAPIF provider's p... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.12.2 Requirements
| [AR-4.12.2-a] The CAPIF shall provide mechanisms to enable the API invokers of the CAPIF provider to discover and invoke the service APIs of the 3rd party CAPIF provider.
[AR-4.12.2-b] The CAPIF shall provide mechanisms to enable a CAPIF provider to publish, retrieve unpublish and update service APIs in a 3rd party CA... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.13 Identities
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.13.1 Introduction
| This subclause specifies the identities related requirements.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.13.2 Requirements
| [AR-4.13.2-a] The CAPIF shall support uniform addressing (e.g. identity) for communication within the same trust domain or from the 3rd party trust domain.
[AR-4.13.2-b] The CAPIF shall support identities for uniquely identifying each service API.
[AR-4.13.2-c] The CAPIF shall support identities for uniquely identify... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.14 API provider domain interactions
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.14.1 Introduction
| This subclause specifies the API provider domain interactions related requirements.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.14.2 Requirements
| [AR-4.14.2-a] The CAPIF shall enable interactions between multiple API exposing functional entities within the same trust domain.
[AR-4.14.2-b] The CAPIF shall enable interactions of multiple API exposing functional entities between trust domains.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.15 Dynamic routing of service API invocation
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.15.1 Introduction
| This subclause specifies the dynamic routing of service API invocation related requirements.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.15.2 Requirements
| [AR-4.15.2-a] The CAPIF shall provide a mechanism to support the dynamic routing of service API invocation.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.16 Registering API provider domain functions
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.16.1 Introduction
| This subclause specifies the requirements related to registration of API provider domain functions on the CAPIF core function.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.16.2 Requirements
| [AR-4.16.2-a] The CAPIF shall provide the capability to register API provider domain functions.
[AR-4.16.2-b] The CAPIF shall support the capability to update the registration information of the API provider domain functions.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.17 Resource owner-aware northbound API invocation
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.17.1 Introduction
| This subclause specifies requirements related to the resource owner-aware northbound API invocation.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 4.17.2 Requirements
| [AR-4.17.2-a] The CAPIF shall support applications on the UE acting as an API invoker.
[AR-4.17.2-b] The CAPIF shall support the authentication of the resource owner.
[AR-4.17.2-c] The CAPIF shall provide mechanisms to manage (provide, obtain, revoke) resource owner authorization for API invoker(s) to access (API pro... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 5 Involved business relationships
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 5.1 Basic CAPIF business relationships
| Figure 5.1-1 shows the typical business relationships in CAPIF.
Figure 5.1-1: Business relationships in CAPIF
The API invoker has service agreement with a CAPIF provider and consumes the CAPIF APIs and service APIs. There are various API invokers like application management client (used by application developers, ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 5.2 CAPIF business relationships for RNAA
| Figure 5.2-1 shows the CAPIF business relationships for the resource owner-aware northbound API access (RNAA).
Figure 5.2-1: CAPIF business relationships for RNAA
The business relationships the API invoker, the CAPIF provider, and the API provider follow the description in the clause 5.1. In addition to them, the ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6 Functional model
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.1 General
| The Common API framework (CAPIF) functional architecture is described in this subclause. The CAPIF architecture is defined as service-based and interactions between the CAPIF functions are represented in two ways:
- A service-based representation, where CAPIF functions enable other authorized CAPIF functions to access... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.2 Functional model description
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.2.0 Functional model description for the CAPIF
| Figure 6.2.0-1 shows the reference point based functional model for the CAPIF.
Figure 6.2.0-1: Functional model for the CAPIF
The CAPIF is hosted within the PLMN operator network (or even an SNPN). The API invoker is typically provided by a 3rd party application provider who has service agreement with PLMN operator... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.2.1 Functional model description to support 3rd party API providers
| Figure 6.2.1-1 shows the functional model for the CAPIF to support 3rd party API providers.
Figure 6.2.1-1: Functional model for the CAPIF to support 3rd party API providers
The CAPIF core function in the PLMN trust domain supports service APIs from both the PLMN trust domain and the 3rd party trust domain having b... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.2.2 Functional model description to support CAPIF interconnection
| Figure 6.2.2-1 shows the architectural model for the CAPIF interconnection which allows API invokers of a CAPIF provider to utilize the service APIs from the 3rd party CAPIF provider.
Figure 6.2.2-1: High level functional architecture for CAPIF interconnection with multiple CAPIF provider domains
Figure 6.2.2-2 sho... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.2.3 Functional model description to support RNAA
| Figure 6.2.3-1 shows the architectural model for the RNAA which allows the resource owner to provide authorization to access their resources through Service API invocation.
Figure 6.2.3-1: High level functional architecture for CAPIF supporting RNAA
The authorization function is an internal entity of the CAPIF core... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3 Functional entities description
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3.1 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3.2 API invoker
| The API invoker is typically provided by a 3rd party application provider who has service agreement with PLMN operator. The API invoker may reside within the same trust domain as the PLMN operator network. The API invoker may be either an application on a server or an application on a UE.
The API invoker supports the ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3.3 CAPIF core function
| The CAPIF core function consists of the following capabilities:
- Authenticating the API invoker based on the identity and other information required for authentication of the API invoker;
- Mutual authentication with the API invoker;
- Publishing, storing, retrieving, unpublishing, updating and discovering of servi... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3.4 API exposing function
| The API exposing function is the provider of the service APIs and is also the service communication entry point of the service API to the API invokers. The API exposing function consists of the following capabilities:
- Authenticating the API invoker based on the identity and other information required for authenticat... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3.5 API publishing function
| The API publishing function enables the API provider to publish the service APIs information in order to enable the discovery of service APIs by the API invoker. The API publishing function consists of the following capability:
- Publishing the service API information of the API provider to the CAPIF core function; an... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3.6 API management function
| The API management function enables the API provider to perform administration of the service APIs. The API management function consists of the following capabilities:
- Auditing the service API invocation logs received from the CAPIF core function;
- Monitoring the events reported by the CAPIF core function;
- Conf... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3.7 Authorization function
| The authorization function has the following capabilities:
- Acts in an authorization server role as specified in clause 1.1 of IETF RFC 6749 [14],
- Verifies authorization information for service APIs, upon request from AEF (when the AEF does not have information required to authorize the service API invocation),
-... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.3.8 Resource owner function
| The resource owner function is responsible for interactions with the resource owner, when needed for the resource owner network resource consumption during obtain service API authorization procedure, e.g. in a similar way to the resource owner's user agent shown in clause 4.1 of IETF RFC 6749 [14].
The resource owner... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4 Reference points
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.1 General
| The reference points for CAPIF are described in the following subclauses.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.2 Reference point CAPIF-1 (between the API invoker and the CAPIF core function)
| The CAPIF-1 reference point, which exists between the API invoker and the CAPIF core function, is used for the API invoker within the PLMN trust domain to discover service APIs, to authenticate and to get authorization.
The CAPIF-1 reference point supports:
- Onboarding the new API invokers and offboarding API invoke... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.3 Reference point CAPIF-1e (between the API invoker and the CAPIF core function)
| The CAPIF-1e reference point, which exists between the API invoker and the CAPIF core function, is used for the API invoker outside the PLMN trust domain to discover service APIs, to authenticate and to get authorization.
The CAPIF-1e reference point supports all the functions of CAPIF-1.
NOTE: The security aspects o... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.4 Reference point CAPIF-2 (between the API invoker and the API exposing function)
| The CAPIF-2 reference point, which exists between the API invoker and the API exposing function belonging to the same trust domain, is used for the API invoker to communicate with the service APIs.
The CAPIF-2 reference point supports:
- Authenticating the API invoker based on the identity and credentials of the API ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.5 Reference point CAPIF-2e (between the API invoker and the API exposing function)
| The CAPIF-2e reference point, which exists between the API invoker and the API exposing function belonging to a different trust domain, is used for the API invoker to communicate with the service APIs.
The CAPIF-2e reference point supports all the functions of CAPIF-2.
NOTE: The security aspects of CAPIF-2e are speci... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.6 Reference point CAPIF-3 (between the API exposing function and the CAPIF core function)
| The CAPIF-3 reference point, which exists between the API exposing function and the CAPIF core function, is used for exercising access and policy related control for service API communications initiated by the API invoker.
The CAPIF-3 reference point supports:
- Authenticating the API invoker based on the identity an... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.7 Reference point CAPIF-4 (between the API publishing function and the CAPIF core function)
| The CAPIF-4 reference point, which exists between the API publishing function and the CAPIF core function, is used for publishing the service API information.
The CAPIF-4 reference point supports:
- Publishing the service APIs information by the API publishing function.
NOTE: The security aspects of CAPIF-4 are spec... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.8 Reference point CAPIF-5 (between the API management function and the CAPIF core function)
| The CAPIF-5 reference point, which exists between the API management function and the CAPIF core function, is used for management of service API, API invoker and API provider domain function information.
The CAPIF-5 reference point supports:
- Accessing the service API invocation logs by the API management function;
... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.9 Reference point CAPIF-3e (between the API exposing function and the CAPIF core function)
| The CAPIF-3e reference point, which exists between the API exposing function within the 3rd party trust domain and the CAPIF core function within the PLMN trust domain, is used for exercising access and policy related control for service API communications initiated by the API invoker.
The CAPIF-3e supports all the fu... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.10 Reference point CAPIF-4e (between the API publishing function and the CAPIF core function)
| The CAPIF-4e reference point, which exists between the API publishing function within the 3rd party trust domain and the CAPIF core function within the PLMN trust domain, is used for publishing the service API information.
The CAPIF-4e reference point supports all the functions of CAPIF-4.
NOTE: The security aspects ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.11 Reference point CAPIF-5e (between the API management function and the CAPIF core function)
| The CAPIF-5e reference point, which exists between the API management function within the 3rd party trust domain and the CAPIF core function within the PLMN trust domain, is used for management of service API, API invoker and API provider domain function information.
The CAPIF-5e reference point supports all the funct... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.12 Reference point CAPIF-7 (between the API exposing functions)
| The CAPIF-7 reference point, which exists between the API exposing functions belonging to the same trust domain, is used for the forwarding or routing or nesting of the API invoker's service API invocation from one API exposing function to the other API exposing function deployed in the PLMN trust domain.
The CAPIF-7 ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.13 Reference point CAPIF-7e (between the API exposing functions)
| The CAPIF-7e reference point, which exists between the API exposing functions belonging to different trust domains, is used for the forwarding or routing of the API invoker's service API invocation from one API exposing function to the other API exposing function between different trust domains.
The CAPIF-7e reference... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.14 Reference point CAPIF-6 (between the CAPIF core functions of the same CAPIF provider)
| The CAPIF-6 reference point exists between the CAPIF core functions within the same trust domain of CAPIF provider.
The CAPIF-6 reference point supports:
- Publishing the service APIs information;
- Discovering the service APIs information;
- Obtaining security information for the API invoker upon accessing the ser... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.15 Reference point CAPIF-6e (between the CAPIF core functions of different CAPIF providers)
| The CAPIF-6e reference point exists between the CAPIF core function within the 3rd party trust domain and the CAPIF core function within the PLMN trust domain.
The CAPIF-6e reference point supports all the functions of CAPIF-6.
NOTE: The security aspects of CAPIF-6e are specified in 3GPP TS 33.122 [12], clauses 6.6, ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.4.16 Reference point CAPIF-8 (between the CAPIF core function and the resource owner function)
| The CAPIF-8 reference point exists between the CAPIF core function and the resource owner function.
The CAPIF-8 reference point supports:
- Providing authorization for resource access; and
- Managing and revoking the provided authorization.
NOTE: The functionalities over CAPIF-8 is FFS and out of scope of the curre... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 6.5 Service-based interfaces
| The CAPIF architecture contains the following service-based interfaces:
- Cccf: Service-based interface exhibited by CAPIF core function.
- Caef: Service-based interface exhibited by API exposing function.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 7 Application of functional model to deployments
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 7.1 General
| The CAPIF deployments in centralized and distributed models are described in clause 7.2 and clause 7.3. The multiple CCFs deployment is described in clause 7.4.
The RNAA deployments are described in clause 7.5.
The CAPIF deployment models shown are not exhaustive.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 7.2 Centralized deployment
| The CAPIF can be deployed centrally as illustrated in the figure 7.2-1.
Figure 7.2-1: Centralized deployment of CAPIF
In one centralized deployment, the CAPIF core function and the API provider domain functions are co-located. The API invoker can interact independently with the CAPIF core function and the API ex... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 7.3 Distributed deployment
| The CAPIF can be deployed in a distributed manner illustrated in the figure 7.3-1.
Figure 7.3-1: Distributed deployment of the CAPIF within PLMN trust domain
In distributed deployment, the CAPIF core function and the API provider domain functions are not co-located. The CAPIF core function interacts with the API ... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 7.4 Multiple CCFs deployment
| Multiple CAPIF core functions may be deployed within the PLMN trust domain as illustrated in the figure 7.4-1. For simplicity, the API invoker is not shown.
Figure 7.4-1: Multiple CCFs deployment within the PLMN trust domain
In the distributed deployment, the CAPIF core function 1 and the CAPIF core function 2 inte... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 7.5 RNAA deployments
| CAPIF supports RNAA and has enabled API invoker(s) to have authorized access to resources of a resource owner provided by service APIs offered by the AEF. The CCF acts as the Authorization Function and supports the authentication and authorization of API invoker(s). After checking the resource owner authorization infor... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8 Procedures and information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.1 Onboarding the API invoker to the CAPIF
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.1.1 General
| The procedure in this subclause corresponds to the architectural requirements for onboarding the API invoker to the CAPIF. The CAPIF enables a one time onboarding process that enrolls the API invoker as a recognized user of the CAPIF, which may be triggered by the API invoker via CAPIF-1 or CAPIF-1e, or may be based on... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.1.2 Information flows
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.1.2.1 Onboard API invoker request
| Table 8.1.2.1-1 describes the information flow onboard API invoker request from the API invoker to the CAPIF core function.
Table 8.1.2.1-1: Onboard API invoker request
Information element
Status
Description
Onboarding information
M
The information of the API invoker including enrolment details, required for onb... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.1.2.2 Onboard API invoker response
| Table 8.1.2.2-1 describes the information flow onboard API invoker response from the CAPIF core function to the API invoker.
Table 8.1.2.2-1: Onboard API invoker response
Information element
Status
Description
Onboarding status
M
The result of onboarding request i.e., success indication is included if the API in... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.1.3 Procedure
| Figure 8.1.3-1 illustrates the procedure for onboarding the API invoker to the CAPIF. The security aspects of this procedure are specified in subclause 6.1 of 3GPP TS 33.122 [12].
Pre-conditions:
1. The API invoker is not a recognized user of the CAPIF.
2. The API invoker has visibility to APIs information (e.g., AP... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.2 Offboarding the API invoker from the CAPIF
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.2.1 General
| This subclause defines the procedure for offboarding the API invoker from the CAPIF. The offboarding process makes the API invoker no longer a recognized user of the CAPIF. The procedure is triggered by the API invoker over CAPIF-1 or CAPIF-1e.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.2.2 Information flows
| This subclause describes the information flows for the API invoker offboarding.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.2.2.1 Offboard API invoker request
| Table 8.2.2.1-1 describes the information flow offboard API invoker request from the API invoker to the CAPIF core function.
Table 8.2.2.1-1: Offboard API invoker request
Information element
Status
Description
API invoker identity information
M
Identity information of the API invoker requesting offboarding
Rea... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.2.2.2 Offboard API invoker response
| Table 8.2.2.2-1 describes the information flow offboard API invoker response from the CAPIF core function to the API invoker.
Table 8.2.2.2-1: Offboard API invoker response
Information element
Status
Description
Result
M
Indicates the success or failure of the offboarding operation
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.2.3 Procedure
| Figure 8.2.3-1 illustrates the procedure for offboarding the API invoker from the CAPIF, triggered by the API invoker. The security aspects of this procedure are specified in subclause 6.8 of 3GPP TS 33.122 [12].
Pre-conditions:
1. The API invoker has been onboarded as a recognized user of the CAPIF.
Figure 8.2.3-... |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.3 Publish service APIs
| |
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.3.1 General
| The CAPIF supports publishing service APIs by the API provider. The API publishing function can be within PLMN trust domain or within 3rd party trust domain.
|
3326ac7824310bad2504c57adb52d51e | 23.222 | 8.3.2 Information flows
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.