hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
3 Definitions and abbreviations
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
API: The means by which an API invoker can access the service.
API invoker: The entity which invokes the CAPIF or service APIs.
API invoker profile: The set of information associated to an API invoker that allows that API invoker to utilize CAPIF APIs and service APIs.
API exposing function: The entity which provides the service communication entry point for the service APIs.
API exposing function location: The location information (e.g. civic address, GPS coordinates, data center ID) where the API exposing function providing the service API is located.
API category: A name used to group service APIs by the service domain in which they are used (e.g., IoT, V2X). The CAPIF core function maintains a list of API category names.
API management function: The entity which enables the API provider to perform administration of the service APIs.
API publishing function: The entity that enables the API provider to publish the Service APIs information in order to enable the discovery of APIs by the API invoker.
Authorization function: The entity which issues access tokens to the API invokers after successfully authenticating the resource owner and obtaining authorization.
CAPIF administrator: An authorized user with special permissions for CAPIF operations.
Common API framework: A framework comprising common API aspects that are required to support service APIs.
Designated CAPIF core function: The CAPIF core function which is configured as the serving CAPIF core function for interconnection.
Network Slice Info: Network slice information of service API which include a list of network slice related identifiers, as described in clause 8.4 of 3GPP TS 23.435 [13]).
Northbound API: A service API exposed to higher-layer API invokers.
Onboarding: One time registration process that enables the API invoker to subsequently access the CAPIF and the service APIs.
Resource: The object or component of the API on which the operations are acted upon.
Resource owner: A UE user or an MNO subscriber capable of granting access to a protected resource related to the invoked API via resource owner function.
Resource owner function: The entity that enables the authorization for resource access and managing and revoking authorization for resource access.
Resource owner-aware northbound API access: An API invocation scenario where the API invoker needs an authorization from the resource owner.
Service API: The interface through which a component of the system exposes its services to API invokers by abstracting the services from the underlying mechanisms.
Serving Area Information: The location information for which the service APIs are being offered to.
CAPIF provider domain: A domain that contains an instance of CAPIF core function and may contain API provider domains and API invokers. The CAPIF provider could be a PLMN, SNPN or 3rd party. Throughout this document, PLMN trust domain is often used as the typical deployment of a CAPIF provider domain however SNPN trust domain or 3rd party trust domain are applicable as well.
PLMN trust domain: The entities protected by adequate security and controlled by the PLMN operator or a trusted 3rd party of the PLMN.
SNPN trust domain: The entities protected by adequate security and controlled by the SNPN operator or a trusted 3rd party of the SNPN. 3rd party trust domain: The entities protected by adequate security and controlled by the 3rd party.
Application management client: The application developers utilize the CAPIF APIs using an application management client as an API invoker to obtain the service APIs information to implement the application program. Such application programs are hosted on cloud, edge or on a UE.
Hosted applications: The hosted applications (which are programmed to utilize the service APIs) as an API invoker invoke the CAPIF APIs and service APIs as per the application business logic.
Channel Aggregator Platform: The Channel Aggregator aggregates the APIs from one or more southbound CAPIF providers with the intention to re-expose such APIs or expose value-added APIs developed using the APIs from the southbound CAPIF providers to the northbound side Application management client or Hosted applications. The Channel Aggregator Platform as API invoker invokes the CAPIF APIs and service APIs as per its business logic.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 32.240 [6] apply:
Offline charging
Online charging
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
5GS 5G System
AEF API Exposing Function
AF Application Function
AMF API Management Function
APF API Publishing Function
API Application Program Interface
AS Application Server
BM-SC Broadcast Multicast Service Centre
CAPIF Common API Framework
CDR Charging Data Record
CRUD Create, Read, Update, Delete
DDoS Distributed Denial of Service
E-UTRA Evolved Universal Terrestrial Radio Access
EPS Evolved Packet System
ETSI European Telecommunications Standards Institute
GS Group Specification
IP Internet Protocol
MBMS Multimedia Broadcast and Multicast Service
MEC Multi-access Edge Computing
NEF Network Exposure Function
NGSI Next Generation Service Interfaces
NR New Radio
OMA Open Mobile Alliance
OAM Operations, Administration and Maintenance
OWSER OMA Web Services
PC Protocol Converter
PLMN Public Land Mobile Network
REST REpresentational State Transfer
RNAA Resource owner-aware Northbound API Access
RO Resource Owner
ROF Resource Owner Function
RPC Remote Procedure Call
SCEF Service Capability Exposure Function
SCS Service Capability Server
SNPN Stand-alone Non-Public Network
UDDI Universal Description, Discovery and Integration
URI Uniform Resource Identifier
WSDL Web Services Description Language
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4 Architectural requirements
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.1 General
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.1.1 Introduction
|
This subclause specifies the general requirements for CAPIF architecture.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.1.2 Requirements
|
[AR-4.1.2-a] The CAPIF shall provide mechanisms (e.g. publish service APIs, authorization, logging, charging) to support service API operations.
[AR-4.1.2-b] The CAPIF shall enable API invoker(s) to discover and communicate with service APIs from the API providers.
[AR-4.1.2-c] Reference points between CAPIF and external applications shall be provided as APIs.
[AR-4.1.2-d] Reference points internal to CAPIF may be provided as APIs.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.1.3 Requirements for supporting 3rd party API providers
|
[AR-4.1.3-a] The CAPIF shall provide mechanisms (e.g. publish service APIs, authorization, logging, charging) to support service API operations from trusted 3rd party API providers.
[AR-4.1.3-b] The CAPIF shall enable API invoker(s) to discover and communicate with service APIs from trusted 3rd party API providers.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.2 Service API publish and discover
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.2.1 Introduction
|
This subclause specifies the service API publish and discover related requirements.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.2.2 Requirements
|
[AR-4.2.2-a] The CAPIF shall provide a mechanism to publish the service API information to be used by the API invokers to discover and subsequently invoke the service API.
[AR-4.2.2-b] The CAPIF shall provide a mechanism for the API invokers to discover the published service API information as specified in [AR-4.2.2-a] according to the API invokers' interest.
[AR-4.2.2-c] The CAPIF shall provide a mechanism to restrict the discovery of the published service API information by the API invokers, based on configured policies.
[AR-4.2.2-d] The CAPIF shall provide a mechanism to configure policies to restrict the discovery of the published service API information.
[AR-4.2.2-e] The CAPIF shall provide mechanism to support Serving Area Information related to service APIs.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.2.3 Requirements for 3rd party API providers
|
[AR-4.2.3-a] The CAPIF shall provide a mechanism to publish the service API information of the 3rd party API providers.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.3 Security
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.3.1 Introduction
|
This subclause specifies the security related requirements for API invokers.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.3.2 Requirements
|
[AR-4.3.2-a] The CAPIF shall provide mechanisms to hide the topology of the PLMN trust domain from the API invokers accessing the service APIs from outside the PLMN trust domain.
[AR-4.3.2-b] The CAPIF shall provide mechanisms to authenticate API invokers prior to accessing the service APIs.
[AR-4.3.2-c] The CAPIF shall provide mechanisms to authenticate API invokers upon the service API invocation.
[AR-4.3.2-d] The CAPIF shall provide mechanisms to authorize API invokers to access the service APIs.
[AR-4.3.2-e] The CAPIF shall provide mechanisms to validate authorization of the API invokers upon the service API invocation.
[AR-4.3.2-f] The CAPIF shall provide mechanisms for mutual authentication between the CAPIF and the API invoker.
[AR-4.3.2-g] The CAPIF shall provide mechanisms to control the service API access for every API invocation.
[AR-4.3.2-h] The communication between the CAPIF and the API invoker shall be confidentiality protected.
[AR-4.3.2-i] The communication between the CAPIF and the API invoker shall be integrity protected.
[AR-4.3.2-j] The CAPIF shall provide mechanisms to authenticate the service API publishers to publish and manage the service API information.
[AR-4.3.2-k] The CAPIF shall provide mechanisms to authorize the service API publishers to publish and manage service API information.
[AR-4.3.2-l] The CAPIF shall provide mechanisms to validate authorization of the service API publishers to publish and manage service API information.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.3.3 Additional requirements for 3rd party API provider
|
[AR-4.3.3-a] The CAPIF shall provide mechanisms to hide the topology of the 3rd party API provider trust domain from the API invokers accessing the service APIs from outside the 3rd party API provider trust domain.
[AR-4.3.3-b] The CAPIF shall provide authorization mechanism for service APIs from the 3rd party API providers.
[AR-4.3.3-c] The CAPIF shall provide data confidentiality (across API providers) for data (e.g. logging, charging) related to service APIs from multiple API providers.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.4 Charging
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.4.1 Introduction
|
This subclause specifies the charging related requirements for the usage of service APIs.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.4.2 Requirements
|
[AR-4.4.2-a] The CAPIF shall support online and offline charging for service APIs usage.
[AR-4.4.2-b] The CAPIF shall provide mechanisms to record the usage (e.g. invocation count) of the service APIs for charging purpose, on a per API invoker basis.
[AR-4.4.2-c] The CAPIF shall provide mechanisms to record timestamp of the service API invocation.
[AR-4.4.2-d] The CAPIF shall provide mechanisms to record the service API related information, e.g. API location.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.4.3 Requirements for 3rd party API providers
|
[AR-4.4.3-a] The CAPIF shall support online and offline charging for 3rd party API providers' service APIs usage.
[AR-4.4.3-b] The CAPIF shall provide mechanisms to query charging related information of the 3rd party service APIs by the authorized users.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.5 Operations, Administration and Maintenance
| |
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
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 the fault information about the service APIs.
[AR-4.5.2-d] The CAPIF shall provide mechanisms to record change events of service APIs, e.g. service APIs relocation.
[AR-4.5.2-e] The CAPIF shall provide mechanisms to configure policies related to service APIs.
|
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.6 Service API invocation monitoring
| |
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
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 shall provide mechanisms to allow service API provider to apply monitoring filters based on criteria such as API invoker's ID and IP address, service API name and version, invoked operation, input parameters, and invocation result.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.7 Logging
| |
654592d6e30fb2596cb6e134b557471f
|
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 invoker interactions with the CAPIF (e.g. authentication, authorization, discover service APIs).
|
654592d6e30fb2596cb6e134b557471f
|
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 securely, and shall only be accessed by CAPIF administrators of the service API provider.
|
654592d6e30fb2596cb6e134b557471f
|
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 shall only be accessed by CAPIF administrators.
|
654592d6e30fb2596cb6e134b557471f
|
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 shall be stored securely, accessed only by CAPIF administrators.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.8 Auditing service API invocation
| |
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.9 Onboarding API invoker
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.9.1 Introduction
|
This subclause specifies the requirements related to onboarding API invoker to the CAPIF.
|
654592d6e30fb2596cb6e134b557471f
|
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 updating an API invoker's API list e.g., subsequent to discovery of new API(s).
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.10 Policy configuration
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.10.1 Introduction
|
This subclause specifies the policy configuration related requirements.
|
654592d6e30fb2596cb6e134b557471f
|
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).
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.11 Protocol design
| |
654592d6e30fb2596cb6e134b557471f
|
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). Extensibility of this model allows evolution and re-use.
|
654592d6e30fb2596cb6e134b557471f
|
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 to support different protocol stack models, including related security mechanisms, in addition to the minimum common protocol stack model.
NOTE: Potentially, Stage 3 needs to consider all CAPIF APIs for protocol extensibility.
[AR-4.11.2-d] CAPIF APIs and associated information flows shall be extensible to support vendor-specific functionality.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.12 Interconnection between the CAPIF providers
| |
654592d6e30fb2596cb6e134b557471f
|
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 perspective the other CAPIF provider is a 3rd party.
|
654592d6e30fb2596cb6e134b557471f
|
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 CAPIF provider.
[AR-4.12.2-c] The CAPIF shall provide mechanisms for authentication, authorization, authorization revocation for access to the service APIs exposed by a 3rd party CAPIF provider.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.13 Identities
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.13.1 Introduction
|
This subclause specifies the identities related requirements.
|
654592d6e30fb2596cb6e134b557471f
|
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 API.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.14 API provider domain interactions
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.14.1 Introduction
|
This subclause specifies the API provider domain interactions related requirements.
|
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.15 Dynamic routing of service API invocation
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.15.1 Introduction
|
This subclause specifies the dynamic routing of service API invocation related requirements.
|
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.16 Registering API provider domain functions
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.16.1 Introduction
|
This subclause specifies the requirements related to registration of API provider domain functions on the CAPIF core function.
|
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.17 Resource owner-aware northbound API invocation
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
4.17.1 Introduction
|
This subclause specifies requirements related to the resource owner-aware northbound API invocation. In the current release, the scope of API invoker on a UE in Resource owner-aware northbound API access is limited to accessing its own resources only, i.e., resource owner is a user of the UE hosting the API invoker that can authorize the API access.
|
654592d6e30fb2596cb6e134b557471f
|
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 provider domain hosted) resources owned by resource owners.
[AR-4.17.2-d] The CAPIF shall provide a mechanism to enable API invoker on a UE to access resources of another UE or group of UE(s) with resource owner authorization.
[AR-4.12.2-e] The CAPIF shall enable API invokers to access (API provider domain hosted) resources via the service APIs exposed by a 3rd party CAPIF provider with resource owner authorization.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
5 Involved business relationships
| |
654592d6e30fb2596cb6e134b557471f
|
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, application service provider), hosted applications (on cloud, edge or UE), and channel aggregator (who aggregates the CAPIF APIs and/or the service APIs). For more details about these API invoker roles, please refer to Annex F.
The API provider hosts one or more service APIs and has a service API arrangement with CAPIF provider to offer the service APIs to the API invoker.
The CAPIF provider and the API provider can be part of the same organization (e.g. PLMN operator), in which case the business relationship between the two is internal to a single organization. The CAPIF provider and the API provider can be part of different organizations, in which case the business relationship between the two must exist.
|
654592d6e30fb2596cb6e134b557471f
|
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 resource owner is an entity capable of granting access to a protected resource related to the resource exposed by the API provider. The API invoker and the resource owner can be the same entity or separate entities. In the current release, the resource owner is a user of a UE and can provide authorization information using the UE.
The CAPIF provider and the API provider can belong to the same organization (e.g. PLMN operator), in which case the service API arrangement is not required explicitly.
The CAPIF provider and the API provider (e.g. 3rd party CAPIF provider or 3rd party API provider) can belong to different organizations, in which case the service API arrangement is required. The specification of service API arrangement is out of scope of 3GPP.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
6 Functional model
| |
654592d6e30fb2596cb6e134b557471f
|
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 their services;
- A reference point representation, where interactions between any two CAPIF functions (e.g. CCF, AEF) is shown by an appropriate point-to-point reference point (e.g. CAPIF-3).
The CAPIF functional architecture can be adopted by any 3GPP functionality providing 3GPP northbound service APIs.
NOTE 1: The terms “functional architecture” and “functional model” mean the same and have been used interchangeably in this specification.
NOTE 2: The functional model described in this specification applies to both PLMN(s) and to SNPN(s).
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
6.2 Functional model description
| |
654592d6e30fb2596cb6e134b557471f
|
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. The API invoker may reside within the same trust domain as the PLMN operator network.
In a reference point based model, the API invoker within the PLMN trust domain interacts with the CAPIF via CAPIF-1 and CAPIF-2. The API invoker from outside the PLMN trust domain interacts with the CAPIF via CAPIF-1e and CAPIF-2e. The API exposing function, the API publishing function and the API management function of the API provider domain (together known as API provider domain functions) within the PLMN trust domain interacts with the CAPIF core function via CAPIF-3, CAPIF-4 and CAPIF-5 respectively.
Figure 6.2.0-2: Functional model for interactions between API exposing functions
As illustrated in figure 6.2.0-2, the interactions between the API exposing functions within the PLMN trust domain is via CAPIF-7.
The CAPIF core function provides CAPIF APIs to the API invoker over CAPIF-1 and CAPIF-1e. The API exposing function provides the service APIs to the API invoker over CAPIF-2 and CAPIF-2e.
NOTE 1: The communication between the API exposing function and the CAPIF core function, between the API publishing function and the CAPIF core function and between the API management function and the CAPIF core function over CAPIF-3, CAPIF-4 and CAPIF-5 respectively can be API based.
The detailed information of the APIs provided by the CAPIF core function is specified in clause 10.
The security aspects of CAPIF reference points are specified in 3GPP TS 33.122 [12].
Figure 6.2.0-3 illustrates the CAPIF functional model using service-based interfaces.
Figure 6.2.0-3: CAPIF functional model representation using service-based interfaces
Table 6.2.0-1 specifies the service-based interfaces supported by CAPIF.
Table 6.2.0-1: Service-based interfaces supported by CAPIF
Service-based interface
Entity
APIs offered
Cccf
CAPIF core function
Specified in subclause 10
Caef
API exposing function
Specified in subclause 11
|
654592d6e30fb2596cb6e134b557471f
|
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 business relationship with PLMN. The API invokers may exist within the PLMN trust domain, or within the 3rd party trust domain or outside of both the PLMN trust domain and the 3rd party trust domain. The API provider domain 1 offers the service APIs from the PLMN operator. The API provider domain 2 offers the service APIs from the 3rd party. When the 3rd party API provider is a trusted 3rd party of the PLMN, the API provider domain 1 also offers the service APIs from the 3rd party.
The API invoker 2 within the PLMN trust domain interacts with the CAPIF core function via CAPIF-1, and invokes the service APIs in the PLMN trust domain via CAPIF-2 and invokes the service APIs in the 3rd party trust domain via CAPIF-2e. The API invoker 3 within the 3rd party trust domain interacts with the CAPIF core function via CAPIF-1e, and invokes the service APIs in the PLMN trust domain via CAPIF-2e and invokes the service APIs in 3rd party trust domain via CAPIF-2. The API invoker 1 from outside the PLMN trust domain and 3rd party trust domain, interacts with the CAPIF core function via CAPIF-1e and invokes the service APIs in the PLMN trust domain and the service APIs in the 3rd party trust domain via CAPIF-2e.
The API exposing function, the API publishing function and the API management function of the API provider domain 1 within the PLMN trust domain interacts with the CAPIF core function via CAPIF-3, CAPIF-4 and CAPIF-5 respectively. The API exposing function, the API publishing function and the API management function of the API provider domain 2 within the 3rd party trust domain interacts with the CAPIF core function in the PLMN trust domain via CAPIF-3e, CAPIF-4e and CAPIF-5e respectively. The API exposing function within the PLMN trust domain and the 3rd party trust domain provides the service APIs to the API invoker, offered by the respective trust domains.
The interactions between the API exposing functions within the PLMN trust domain is via CAPIF-7 (not shown in the figure 6.2.1-1 for simplicity). The API exposing function within the PLMN trust domain interacts with the API exposing function in the 3rd party trust domain via CAPIF-7e.
NOTE 1: The communication between the API exposing function and the CAPIF core function, between the API publishing function and the CAPIF core function and between the API management function and the CAPIF core function over CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e respectively can be API based.
The detailed information of the APIs provided by the CAPIF core function is specified in clause 10.
NOTE 2: The security aspects of CAPIF reference points are under SA3 responsibility and out of scope of the present document.
|
654592d6e30fb2596cb6e134b557471f
|
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 shows the architectural model for the CAPIF interconnection within the same CAPIF provider domain, which allows API invokers of CAPIF core function 1 to utilize the service APIs from CAPIF core function 2, where both CAPIF core function 1 and CAPIF core function 2 are hosted within the trust domain of the CAPIF provider A.
Figure 6.2.2-2: High level functional architecture for CAPIF interconnection within a CAPIF provider domain
The CAPIF provider A and CAPIF provider B host the CAPIF in their trust domains. A business relationship exists between the CAPIF providers.
The CAPIF providers in their respective trust domain hosts multiple CAPIF instances where each CAPIF instance consists of the CAPIF core function (local), the API provider domain and the API invokers. All interactions within the CAPIF instance is according to the functional model specified in clause 6.2.0.
When multiple CAPIF instances are deployed by a CAPIF provider there may be a hierarchy associated with the multiple CAPIF core function deployed which allows:
- the designated CAPIF core function of the CAPIF provider A to interconnect with the designated CAPIF core function of the CAPIF provider B; and
- within CAPIF provider A, one or more CAPIF core function interacts with the designated CAPIF core function 1.
The designated CAPIF core function of the CAPIF provider A provides the information about the CAPIF instances and service APIs deployed by the CAPIF provider A to the designated CAPIF core function of the CAPIF provider B and vice versa over CAPIF-6e reference point.
The CAPIF core function 2 of CAPIF provider A provides the information about the service APIs to the CAPIF core function 1 over CAPIF-6 reference point.
NOTE 1: Void
The API invokers may exist within the trust domain of CAPIF provider A, or within the trust domain of CAPIF provider B or outside of the trust domains of both CAPIF provider A and CAPIF provider B. The API invoker of a CAPIF provider is onboarded with the CAPIF core function in the corresponding trust domain of the CAPIF provider.
NOTE 2: For sake of simplicity, the service API interactions of API invokers of the CAPIF provider B are not shown. From each CAPIF provider's perspective the other CAPIF provider is a 3rd party.
One or more CAPIF core function can publish service APIs to the designated CAPIF core function over CAPIF-6 reference point and, also discover the service APIs from the designated CAPIF core function and vice versa over CAPIF-6 reference point.
The API invoker within the trust domain of CAPIF provider A interacts with the CAPIF core function of the CAPIF provider A via CAPIF-1 and discovers the service APIs of both CAPIF providers, and invokes the service APIs in the trust domain of CAPIF provider A via CAPIF-2 and invokes the service APIs in the trust domain of CAPIF provider B via CAPIF-2e. The API invoker from outside the trust domain of CAPIF providers, interacts with the CAPIF core function of th CAPIF provider A via CAPIF-1e and invokes the service APIs in the trust domain of the CAPIF providers via CAPIF-2e.
NOTE 3: The communication between the CAPIF core function of the CAPIF providers over CAPIF-6 or CAPIF-6e can be API based.
The detailed information of the APIs provided by the CAPIF core function is specified in clause 10.
NOTE 4: The security aspects of CAPIF reference points are under SA3 responsibility and out of scope of the present document.
NOTE 5: All interactions among entities within the CAPIF provider domains (regardless if CAPIF is deployed in a PLMN, SNPN or 3rd party network) are ruled by the functional model in clause 6.2.0, the support of 3rd party API providers is as in clause 6.2.1, whereas the interconnection among CCFs is according to this clause.
|
654592d6e30fb2596cb6e134b557471f
|
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 function and performs API invoker authorization based on the API invoker authorization policies available in the CCF and the RO authorization information obtained via the ROF.
The resource owner function interacts with the authorization function in the CAPIF core function via CAPIF-8. The authorization function in the CAPIF core function interacts with the resource owner function to obtain the resource owner authorization. The CAPIF core function (authorization function) uses resource owner authorization information obtained via the ROF as part of the processing of the authorization requests received from API invokers.
The API exposing function (e.g. NEF, SCEF) interacts with the authorization function in the CAPIF core function via CAPIF-3. The API exposing function acts as an authorization enforcement point according to the authorization token received from the API invoker.
NOTE 1: RNAA is supported for both 4G and 5G networks.
The API invoker interacts with authorization function in the CAPIF core function via CAPIF-1/CAPIF-1e.
NOTE 2: In the current release, 3rd party API providers (i.e., API providers outside the PLMN trust domain) are not supported for RNAA.
NOTE 3: The interaction between resource owner function and CCF over CAPIF-8 is not specified in the current release of the specification.
NOTE 4: The authorization information from the resource owner used by CCF (described in 3GPP TS 33.122 [12]) is independent from the user consent information used from user subscription data at UDM/UDR (described in Annex V of 3GPP TS 33.501 [16]). In the current release of 3GPP specifications, no synergy between CCF and UDM is specified.
The security aspects of CAPIF supporting RNAA are specified in 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
6.3 Functional entities description
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
6.3.1 General
|
Each subclause is a description of a functional entity and does not imply a physical entity.
|
654592d6e30fb2596cb6e134b557471f
|
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 following capabilities:
- Triggering API invoker onboarding/offboarding;
- Supporting the authentication by providing the API invoker identity and other information required for authentication of the API invoker;
- Supporting mutual authentication with CAPIF;
- Obtaining the authorization prior to accessing the service API;
- Discovering service APIs information; and
- Invoking the service APIs.
NOTE: The details of the specific service APIs are out of scope of the present document.
|
654592d6e30fb2596cb6e134b557471f
|
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;
- Supporting mutual authentication with the API invoker;
- Publishing, storing and supporting the discovery of service APIs information;
- Controlling the service API access based on PLMN operator configured policies;
- Storing the logs for the service API invocations and providing the service API invocation logs to authorized entities;
- Charging based on the logs of the service API invocations;
- Monitoring the service API invocations;
- Onboarding a new API invoker and offboarding an API invoker;
- Storing policy configurations related to CAPIF and service APIs;
- Support accessing the logs for auditing (e.g. detecting abuse);
- Supports publishing, retrieving, unpublishing, updating,and discovering service APIs information with another CAPIF core function in CAPIF interconnection; and
- Supports slice related API exposure in, e.g., API publish, API discovery, API invoker authorization, API access control.
|
654592d6e30fb2596cb6e134b557471f
|
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 authentication of the API invoker provided by the CAPIF core function;
- Validating the authorization provided by the CAPIF core function;
- Logging the service API invocations at the CAPIF core function; and
- Hiding the topology of the PLMN trust domain from API invokers, depending on configured policy.
|
654592d6e30fb2596cb6e134b557471f
|
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; and
- Retrieving service API information from the CAPIF core function.
|
654592d6e30fb2596cb6e134b557471f
|
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;
- Configuring the API provider policies to the CAPIF core function;
- Monitoring the status of the service APIs;
- Onboarding new API invokers and offboarding API invokers; and
- Registering and maintaining registration information of the API provider domain functions on the CAPIF core function.
NOTE: The API invoker onboarding/offboarding in the API management function is out of the scope of the current release.
|
654592d6e30fb2596cb6e134b557471f
|
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),
- Uses the RO authorization information (such as user consent) obtained via ROF, when legally required, as part of the authorization of the API invoker to access the RO resources related to a service API.
NOTE 1: In the current release, the authorization function is an internal entity of the CAPIF core function.
NOTE 2: The persistent storage of the resource owner authorization data is subject to local/regional regulations and is not in scope of this specification.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
6.3.8 Resource owner function
|
The resource owner function is responsible for interactions with the resource owner in a similar way to the resource owner's user agent shown in clause 4.1 of IETF RFC 6749 [14]. The resource owner function enables the following:
- Authorization for resource access; and
- Managing and revoking authorization for resource access.
NOTE: The procedures corresponding to these capabilities of the resource owner function are FFS and out of scope of the current release of the specification.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
6.4 Reference points
| |
654592d6e30fb2596cb6e134b557471f
|
23.222
|
6.4.1 General
|
The reference points for CAPIF are described in the following subclauses.
|
654592d6e30fb2596cb6e134b557471f
|
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 invokers;
- Authenticating the API invoker based on the identity and credentials of the API invoker;
- Mutual authentication between the API invoker and the CAPIF core function;
- Providing authorization for the API invoker prior to accessing the service API;
- Providing authorization for the API invoker based on RNAA; and
- Discovering the service APIs information.
NOTE: The security aspects of CAPIF-1 are specified in subclause 6.2 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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 of CAPIF-1e are specified in subclause 6.3 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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 invoker;
- Authorization verification for the API invoker upon accessing the service API; and
- Invocation of service APIs.
NOTE 1: The aspects related to the specific service API invocation in reference point CAPIF-2 are out of scope of the present document.
NOTE 2: The security aspects of CAPIF-2 are specified in subclause 6.4 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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 specified in subclause 6.5 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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 and credentials of the API invoker;
- Providing authorization for the API invoker prior to accessing the service API;
- Authorization verification for the API invoker upon accessing the service API;
- Authorization verification for the API invoker based on RNAA;
- Controlling the service API access based on PLMN operator configured policies;
- Logging the service API invocations; and
- Charging the service API invocations.
NOTE: The security aspects of CAPIF-3 are specified in subclause 6.6 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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 specified in subclause 6.6 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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;
- Enabling the API management function to monitor the events reported due to the service APIs invocations;
- Onboarding new API invokers by provisioning the API invoker information at the CAPIF core function, requesting explicit grant of new API invokers onboarding and confirming onboarding success;
- Offboarding API invokers;
- Enabling the API management function to configure policies at the CAPIF core function e.g. service API invocation throttling, blocking API invocation for certain duration;
- Enabling the API provider to monitor the status of service APIs (e.g. pilot or live status, start or stop status of service API);
- Registering API provider domain functions on the CAPIF core function; and
- Update of the registration information of API provider domain functions on the CAPIF core function.
NOTE 1: The security aspects of CAPIF-5 are specified in subclause 6.6 of 3GPP TS 33.122 [12].
NOTE 2: The API invoker onboarding/offboarding over CAPIF-5 is out of the scope of the current release.
|
654592d6e30fb2596cb6e134b557471f
|
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 functions of CAPIF-3.
NOTE: The security aspects of CAPIF-3e are specified in clause 6.10 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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 of CAPIF-4e are specified in clause 6.10 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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 functions of CAPIF-5.
NOTE: The security aspects of CAPIF-5e are specified in clause 6.10 of 3GPP TS 33.122 [12].
|
654592d6e30fb2596cb6e134b557471f
|
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 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 reference point supports all the functions of CAPIF-2.
The CAPIF-7 reference point supports invocation of service APIs originated by the API invoker using CAPIF-2.
NOTE 1: The aspects related to the specific service API invocation in reference point CAPIF-7 are out of scope of the present document.
NOTE 2: The security aspects of CAPIF-7 are the responsibility of SA3.
|
654592d6e30fb2596cb6e134b557471f
|
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 point supports all the functions of CAPIF-2e.
NOTE: The security aspects of CAPIF-7e are the responsibility of SA3.
|
654592d6e30fb2596cb6e134b557471f
|
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; and
- Discovering the service APIs information.
|
654592d6e30fb2596cb6e134b557471f
|
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 will be specified by SA3.
Editor's note: Reference to the appropriate SA3 specification is needed.
|
654592d6e30fb2596cb6e134b557471f
|
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 current release of the specification.
|
654592d6e30fb2596cb6e134b557471f
|
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.
|
654592d6e30fb2596cb6e134b557471f
|
23.222
|
7 Application of functional model to deployments
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.