Content for TS 29.222 Word version: 18.4.0
4 Overview
4.1 Introduction
4.2 Service Architecture
4.3 Functional Entities
4.3.1 API invoker
4.3.2 CAPIF core function
4.3.3 API exposing function
4.3.4 API publishing function
4.3.5 API management function
...
...
4 Overview p. 17
4.1 Introduction p. 17
In 3GPP, there are multiple northbound API-related specifications. To avoid duplication and inconsistency of approaches between different API specifications and to specify common services (e.g. authorization), 3GPP has considered in TS 23.222 the development of a common API framework (CAPIF) that includes common aspects applicable to any northbound service APIs.
The present document specifies the APIs needed to support CAPIF.
4.2 Service Architecture p. 17
Clause 6 of TS 23.222 specifies the functional entities and domains of the functional model.
4.3 Functional Entities p. 17
4.3.1 API invoker p. 17
The API invoker is typically provided by a 3rd party application provider who has service agreement with PLMN operator or SNPN. The API invoker may reside within the same trust domain as the PLMN operator network or SNPN.
The API invoker supports several capabilities as defined in TS 23.222.
4.3.2 CAPIF core function p. 17
The CAPIF core function (CCF) supports the capabilities as defined in TS 23.222.
4.3.3 API exposing function p. 17
The API exposing function (AEF) is the provider of the Service APIs and is also the service communication entry point of the service API to the API invokers as defined in TS 23.222.
4.3.4 API publishing function p. 17
The API publishing function (APF) enables the API provider to publish the Service APIs information as defined in TS 23.222.
4.3.5 API management function p. 17
The API management function (AMF) enables the API provider to perform administration of the Service APIs. The API capabilities are defined in TS 23.222.
