Content for TS 29.222 Word version: 18.4.0
1 Scope p. 15
The present specification describes the protocol for the Common API Framework (CAPIF) for 3GPP Northbound APIs. The CAPIF and the related stage 2 architecture and functional requirements are defined in TS 23.222.
2 References p. 15
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[3]
Open API: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0 .
[4]
RFC 9112: "HTTP/1.1".
[5]
RFC 9110: "HTTP Semantics".
[6] Void.
[7] Void.
[8]
RFC 9111: "HTTP Caching".
[9] Void.
[10]
RFC 9113: "HTTP/2".
[11] Void.
[12]
RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[13]
RFC 6455: "The Websocket Protocol".
[14]
TS 29.122: "T8 reference point for northbound Application Programming Interfaces (APIs)".
[15]
TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[16]
TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs".
[17] Void.
[18]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[19]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
[20]
RFC 7239: "Forwarded HTTP Extension".
[21] Void.
[22]
W3C HTML 4.01 Specification:, https://www.w3.org/TR/2018/SPSD-html401-20180327/ .
[23]
RFC 6749: "The OAuth 2.0 Authorization Framework".
[24]
RFC 7519: "JSON Web Token (JWT)".
[25]
RFC 7515: "JSON Web Signature (JWS)".
[26]
TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3".
[27]
TR 21.900: "Technical Specification Group working methods".
[28]
TS 29.510: "5G System; Network Function Repository Services; Stage 3"
[29]
RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile".
[30]
TS 29.572: "5G System; Location Management Services; Stage 3".
3 Definitions and abbreviations p. 16
3.1 Definitions p. 16
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.
For the purposes of the present document, the terms and definitions given in clause 3 of TS 23.222 shall also apply:
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.
Subscriber:
A functional entity that subscribes to another functional entity for notifications.
3.2 Abbreviations p. 16
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.
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
RNAA
Resource owner-aware Northbound API Access
SCEF
Service Capability Exposure Function
SCS
Service Capability Server
SNPN
Stand-alone Non-Public Network
