Content for TR 23.700-95 Word version: 18.1.0

...

1 Scope p. 7

The present document studies the potential enhancements in CAPIF and application enablement frameworks (e.g. SEAL, EDGEAPP, vertical enabler layers) to support the subscriber-aware northbound API access (SNA), whose requirements are specified in TS 22.261.

This study takes into consideration the existing works for CAPIF (TS 23.222), SEAL (TS 23.434), and EDGEAPP (TS 23.558).

Any potential enhancements to security procedures related to CAPIF and application enablement frameworks (e.g. EDGEAPP, SEAL, vertical enabler layers) to support SNA are not in the scope of this study.

2 References p. 7

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 22.261: "Service requirements for the 5G system; Stage 1"

[3]

TS 23.222: "Common API Framework for 3GPP Northbound APIs"

[4]

TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows"

[5]

TS 23.558: "Architecture for enabling Edge Applications"

[6]

TS 29.513: "Policy and Charging Control signalling flows and QoS parameter mapping"

[7]

TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications"

[8]

TS 33.501: "Security architecture and procedures for 5G system"

[9]

RFC 6749: "The OAuth 2.0 Authorization Framework"

[10]

RFC 8693: "OAuth 2.0 Token Exchange"

3 Definitions of terms, symbols and abbreviations p. 7

3.1 Terms p. 7

For the purposes of the present document, the terms 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.

nested API invocation:

A series of API invocations in which the first API invocation towards the API exposing function 1 triggers this API exposing function to request another API invocation towards the API exposing function 2, which is in the same API provider domain that the API exposing function 1.

resource owner:

An entity capable of granting access to a protected resource.

3.2 Symbols p. 8

For the purposes of the present document, the following symbols apply:

3.3 Abbreviations p. 8

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

Application Function

CAPIF

Common API Framework

CCF

CAPIF Core Function

SNA

Subscriber-aware northbound API access