Content for TS 24.558 Word version: 18.5.1

3.1 Terms 3.2 Symbols 3.3 Abbreviations 4.0 General 4.1 Information applicable to APIs over EDGE-1 and EDGE-4
...

1 Scope p. 11

The present document specifies the APIs for enabling the edge applications over 3GPP networks for EDGE-1 and EDGE-4 reference points. The application layer architecture, functional requirements, procedures and information flows necessary for enabling edge applications over 3GPP networks are specified in TS 23.558. The APIs are specified as RESTful APIs except for custom operations wherever required.

The present document defines the usage and interactions of the EEL layer with SEAL services.

2 References p. 11

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.558: "Architecture for enabling Edge Applications;"

[3]

TS 29.122: "T8 reference point for Northbound APIs".

[4]

TS 29.558: "Enabling Edge Applications; Application Programming Interface (API) specification; Stage 3".
→ to date, still a draft

[5]

TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".

[6]

TS 29.572: "5G System; Location Management Services; Stage 3".

[7]

TS 33.558: "Security aspects of enhancement of support for enabling edge applications; Stage 2".

[8]

TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".

[9]

TS 23.436: "Functional architecture and information flows for Application Data Analytics Enablement Service".

[10]

TS 24.542: "Notification Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification".

[11]

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

3 Definitions of terms, symbols and abbreviations p. 12

3.1 Terms p. 12

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.

For the purposes of the present document, the following terms and definitions given in TS 23.558 apply:

Application Context

Application Context Relocation

EEC Context

Instantiable EAS

For the purposes of the present document, the following terms and definitions given in TS 23.434 apply:

SEAL service

3.2 Symbols p. 12

Void

3.3 Abbreviations p. 12

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.

Application Client

ACR

Application Context Relocation

ADAES

Application Data Analytics Enabler Server

API

Application Programming Interface

EAS

Edge Application Server

ECS

Edge Configuration Server

ECSP

Edge Computing Service Provider

EEC

Edge Enabler Client

EES

Edge Enabler Server

NAS

Non Access Stratum

NID

Network Identifier

SNPN

Stand-alone Non-Public Network

URI

Uniform Resource Locator

SEAL

Service Enabler Architecture Layer for verticals

SNM-C

SEAL Notification Management Client

4 Overview p. 12

4.0 General p. 12

In order to support the edge applications over the 3GPP systems, various features are defined to ensure the efficient use and deployment of edge applications, some of which include, registration, discovery, service provisioning, capability exposure and support for service continuity.

The present document specifies the APIs in detail, needed to support the services offered by the EES over EDGE-1 interface and offered by the ECS over EDGE-4 interface for enabling the edge applications over 3GPP network.

The EEL layer can utilize SEAL services provided by SEAL, which may include notification management (see TS 24.542).

4.1 Information applicable to APIs over EDGE-1 and EDGE-4 p. 13

The APIs as specified in this document allow secure access to the capabilities provided by the EES and ECS functional entity.

The stage-2 level requirements and signalling flows are defined in TS 23.558.

The usage of HTTP, content type, URI structure definition, notifications, error handling, feature negotiation, HTTP headers and Conventions for Open API specification files, as specified in clauses 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9 and 7.10 of TS 29.558 respectively, shall be applicable for the APIs in the current specification.