For the purposes of the present document, the terms and definitions given in 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 TR 21.905
The means by which an API invoker can access the service.
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.
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.
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.
An entity (either a UE user or an MNO subscriber) capable of granting access to a protected resource related to the invoked API.
Resource owner-aware northbound API access:
An API invocation scenario where the API invoker needs an authorization from the resource owner.
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.
For the purposes of the present document, the following terms and definitions given in TS 32.240
For the purposes of the present document, the abbreviations given in 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 TR 21.905
API Exposing Function
Application Program Interface
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
Multimedia Broadcast and Multicast Service
Multi-access Edge Computing
Network Exposure Function
Next Generation Service Interfaces
Open Mobile Alliance
Operations, Administration and Maintenance
OMA Web Services
Public Land Mobile Network
REpresentational State Transfer
Resource owner-aware northbound API access
Remote Procedure Call
Service Capability Exposure Function
Service Capability Server
Stand-alone Non-Public Network
Universal Description, Discovery and Integration
Uniform Resource Identifier
Web Services Description Language