Tech-invite  3GPPspecsRELsGlossariesSIP

full Contents for  TS 23.222  Word version:   17.0.0

Top   None   None   Next
0…   4…   5   6…   6.3…   7…   8…   8.5…   8.9…   8.13…   8.17…   8.21…   8.25…   9…   10…   11…   A   B…   B.2   B.3   C…   D…


0  IntroductionWord-p. 10
In 3GPP, there are multiple northbound API-related specifications (e.g. APIs for Service Capability Exposure Function (SCEF) functionalities defined in 3GPP TS 23.682, API for the interface between MBMS service provider and BM-SC defined in 3GPP TR 26.981). To avoid duplication and inconsistency of approach between different API specifications, 3GPP has considered the development of a common API framework (CAPIF) that includes common aspects applicable to any northbound service APIs.
The present document specifies the functional model, procedures and information flows needed to support the CAPIF, and the guidelines for consistent northbound API (service and CAPIF APIs) development in 3GPP.
It is possible to use the CAPIF defined common aspects for other APIs as well, apart from northbound APIs.
1  ScopeWord-p. 11
The present document specifies the architecture, procedures and information flows necessary for the CAPIF. The aspects of this specification include identifying architecture requirements for the CAPIF (e.g. registration, discovery, identity management) that are applicable to any service APIs when used by northbound entities, as well as any interactions between the CAPIF and the service APIs themselves. The common API framework applies to both EPS and 5GS, and is independent of the underlying 3GPP access (e.g. E-UTRA, NR).
2  References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]  3GPP TR 21.905 "Vocabulary for 3GPP Specifications".
[2]  3GPP TS 23.682 "Architecture enhancements to facilitate communications
with packet data networks and applications".
[3]  3GPP TS 23.501 "System Architecture for the 5G System; Stage 2".
[4]  3GPP TS 23.502 "Procedures for the 5G System; Stage 2".
[5]  3GPP TR 26.981 "MBMS Extensions for Provisioning and Content Ingestion".
[6]  3GPP TS 32.240 "Telecommunication management; Charging management; Charging architecture and principles".
[7]  ETSI GS MEC 011 (V1.1.1): "Mobile Edge Computing (MEC); Mobile Edge Platform Application Enablement".
[8]  ETSI GS MEC 009 (V1.1.1): "Mobile Edge Computing (MEC); General Principles for Mobile Edge Service APIs".
[9]  OMA-ER_Autho4API-V1_0-20141209-A: "Authorization Framework for Network APIs".
[10]  OMA-TS-REST_NetAPI_Common-V1_0-20180116-A: "Common definitions for RESTful Network APIs".
[11]  OMA-TS-NGSI_Registration_and_Discovery-V1_0-20120529-A: "NGSI Registration and Discovery".
[12]  3GPP TS 33.122 "Security Aspects of Common API Framework for 3GPP Northbound APIs".
3  Definitions and abbreviationsWord-p. 12
3.1  Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 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.
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.
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.
Northbound API:
A service API exposed to higher-layer API invokers.
One time registration process that enables the API invoker to subsequently access the CAPIF and the service APIs.
The object or component of the API on which the operations are acted upon.
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.
PLMN trust domain:
The entities protected by adequate security and controlled by the PLMN operator or a trusted 3rd party of the PLMN.
3rd party trust domain:
The entities protected by adequate security and controlled by the 3rd party.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 32.240 apply:
  • Offline charging
  • Online charging
3.2  Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 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.
5G System
API Exposing Function
Application Function
Application Program Interface
Application Server
Broadcast Multicast Service Centre
Common API Framework
Charging Data Record
Create, Read, Update, Delete
Distributed Denial of Service
Evolved Universal Terrestrial Radio Access
Evolved Packet System
European Telecommunications Standards Institute
Group Specification
Internet Protocol
Multimedia Broadcast and Multicast Service
Multi-access Edge Computing
Network Exposure Function
Next Generation Service Interfaces
New Radio
Open Mobile Alliance
Operations, Administration and Maintenance
OMA Web Services
Protocol Converter
Public Land Mobile Network
REpresentational State Transfer
Remote Procedure Call
Service Capability Exposure Function
Service Capability Server
Universal Description, Discovery and Integration
Uniform Resource Identifier
Web Services Description Language

Up   Top   ToC