3 Definitions and abbreviations
23.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: 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.
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.
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: An entity capable of granting access to a protected resource related to the invoked API.
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.
Subscriber-aware northbound API access: An API invocation scenario where the API invoker needs an authorization from the resource owner.
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 [6] apply:
Offline charging
Online charging
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
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
RPC Remote Procedure Call
SCEF Service Capability Exposure Function
SCS Service Capability Server
SNA Subscriber-aware northbound API access
UDDI Universal Description, Discovery and Integration
URI Uniform Resource Identifier
WSDL Web Services Description Language