3 Definitions and abbreviations
29.2223GPPCommon API Framework for 3GPP Northbound APIsRelease 18TS
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 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 registry: API registry is a registry maintained by the CAPIF core function to store information about the service APIs based on the data models defined in this specification. The structure of the API registry is out of scope of this specification.
CAPIF administrator: An authorized user with special permissions for CAPIF operations.
PLMN trust domain: The entities protected by adequate security and controlled by the PLMN operator or a trusted 3rd party of the PLMN.
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.
Subscriber: A functional entity that subscribes to another functional entity for notifications.
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].
AEF API Exposing Function
AMF API Management Function
APF API Publishing Function
AS Application Server
CAPIF Common API Framework
CCF CAPIF Core Function
JSON JavaScript Object Notation
REST Representational State Transfer
SCEF Service Capability Exposure Function
SCS Service Capability Server