Content for TS 23.558 Word version: 19.0.0

0… 5… 6… 6.2a… 6.2b… 6.3… 6.4… 7… 8… 8.3… 8.3.3… 8.3.3.3… 8.4… 8.4.3… 8.4.4… 8.5… 8.6… 8.6.3… 8.6.4… 8.6.6… 8.7… 8.8… 8.8.2.5… 8.8.2A… 8.8.3… 8.8.4… 8.8.5… 8.9… 8.14… 8.14.3… 8.15… 8.17… 8.17.3… 8.17.4… 8.18… 8.19… 8.20… 9… A… A.4… A.5… B…

3.1 Terms 3.2 Symbols 3.3 Abbreviations 4.1 General 4.2 Service provisioning 4.3 Registration 4.4 EAS discovery 4.5 Capability exposure to EAS and EEC 4.6 Support for service continuity 4.7 Security 4.8 Dynamic EAS instantiation triggering 4.9 Charging 4.10 Common EAS discovery
...

0 Introduction p. 17

Edge Computing is a network architecture concept that enables cloud computing capabilities and service environments, which are deployed close to the UE. It promises several benefits such as lower latency, higher bandwidth, reduced backhaul traffic and prospects for new services compared to the cloud environments. This technical specification provides application layer architecture and related procedures for enabling edge applications over 3GPP networks.

1 Scope p. 18

The present document specifies the application layer architecture, procedures and information flows necessary for enabling edge applications over 3GPP networks. It includes architectural requirements for enabling edge applications, application layer architecture fulfilling the architecture requirements and procedures to enable the deployment of edge applications.

2 References p. 18

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.501: "System architecture for the 5G System (5GS); Stage 2".

[3]

TS 23.502: "Procedure for the 5G System (5GS); Stage 2".

[4]

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

[5]

TS 29.122: "T8 reference point for northbound Application Programming Interfaces (APIs)".

[6]

TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".

[7]

TS 23.271: "Functional stage 2 description of Location Services (LCS)".

[8]

TS 36.305: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN".

[9]

TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".

[10]

TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN".

[11]

TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".

[12]

TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".

[13]

TS 23.434: "Service enabler architecture layer for verticals; Functional architecture and information flows; Stage 2".

[14]

TS 23.286: "Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows ".

[15]

ETSI ISG MEC ETSI GS MEC 003 V2.1.1 (2019-01), "Multi-access Edge Computing (MEC); Framework and Reference Architecture"

[16] Void

[17]

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

[18]

TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".

[19]

GSMA PRD OPG.02 Operator Platform Telco Edge Requirements version 4.0, available at https://www.gsma.com/futurenetworks/resources/operator-platform-telco-edge-requirements/

[20]

TS 23.548: "5G System Enhancements for Edge Computing".

[21]

TS 23.032: "Universal Geographical Area Description (GAD)".

[22]

TS 28.538: "Management and orchestration; Edge Computing Management".

[23]

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

[24]

TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".

[25]

TS 32.257: "Telecommunication management;Charging management;Edge computing domain charging".

[26]

TS 23.433: "Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications".

[27]

TR 23.958: "Edge Application Standards in 3GPP and Alignment with External Organizations".

[28]

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

3 Definitions of terms, symbols and abbreviations p. 19

3.1 Terms p. 19

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.

Application Context:

A set of data about the Application Client that resides in the Edge Application Server.

Application Context Relocation:

Refers to the end-to-end service continuity procedure described in clause 8.8.

Application Context Transfer:

Refers to the transfer of the Application Context between the source Edge Application Server and the target Edge Application Server, which is a part of the service continuity procedure described in clause 8.8.

Application Server:

Application software resident in the cloud performing the server function.

Associated EES:

One or multiple EES(s) which support all bundled EAS within the same EDN, and each EES of the associated EES(s) serving all or part of EAS list of the bundle EAS.

Common EAS:

An EAS which can serve a group of UEs using the same application.

Common EES:

An EES which has a Common EAS registered with it.

Edge Computing:

A concept, as described in TS 23.501, that enables operator and 3rd party services to be hosted close to the UE's access point of attachment, to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.

Edge Computing Service Provider:

A mobile network operator or a 3rd party service provider offering Edge Computing service.

Edge Data Network:

A local Data Network that supports the architecture for enabling edge applications.

EEC Context:

A set of data about the Edge Enabler Client that resides in the Edge Enabler Server.

Edge Enabler Layer:

Refers to the overall functionality provided by the entities such as Edge Enabler Client, Edge Enabler Server, Edge Configuration Server and Cloud Enabler Server, in support of applications as per the architecture defined in clause 6.

Edge Hosting Environment:

An environment providing support required for Edge Application Server's execution.

Instantiable EAS:

EAS type for which the instantiation trigger from the Edge Enabler Layer is considered by the ECSP management system for instantiating EAS.

Main EAS:

An EAS in EAS bundle taking the role of controlling the ACR for EAS bundle in network side decided ACR scenario.

Partner ECS:

Refers to an ECS deployed by a partner ECSP.

Partner ECSP:

An ECSP with whom there is a service level agreement for resource sharing for roaming or federation or both.

3.2 Symbols p. 20

None.

3.3 Abbreviations p. 20

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

ACID

Application Client Identification

ACR

Application Context Relocation

ACT

Application Context Transfer

AEF

API Exposing Function

Application Function

APN

Access Point Name

ASP

Application Service Provider

CAPIF

Common API Framework

CAS

Cloud Application Server

CES

Cloud Enabler Server

Data Network

DNAI

Data Network Access Identifier

DNN

Data Network Name

H-ECS

Home Edge Configuration Server

H-EES

Home Edge Enabler Server

EAS

Edge Application Server

EASID

Edge Application Server Identification

ECI

Edge and Cloud Interworking

ECS

Edge Configuration Server

ECS-ER

Edge Configuration Server - Edge Repository

ECSP

Edge Computing Service Provider

EDN

Edge Data Network

EEC

Edge Enabler Client

EECID

Edge Enabler Client Identification

ENS

Edge Node Sharing

ETSI

European Telecommunications Standards Institute

EEL

Edge Enabler layer

EES

Edge Enabler Server

EESID

Edge Enabler Server Identification

FQDN

Fully Qualified Domain Name

GPSI

Generic Public Subscription Identifier

GSM

Global System for Mobile Communications

GSMA

GSM Association

LADN

Local Area Data Network

MEC

Multi-access Edge Computing

NEF

Network Exposure Function

Operator Platform

OPG

Operator Platform Group

PCF

Policy Control Function

PSA

PDU Session Anchor

S-EAS

Source Edge Application Server

S-EES

Source Edge Enabler Server

SCEF

Service Capability Exposure Function

SEAL

Service Enabler Layer Architecture

SMF

Session Management Function

SSID

Service Set Identifier

T-EAS

Target Edge Application Server

T-EES

Target Edge Enabler Server

TAI

Tracking Area Identity

URSP

UE Route Selection Policy

V-ECS

Visited Edge Configuration Server

V-EES

Visited Edge Enabler Server

4 Overview p. 21

4.1 General p. 21

For edge computing, it is essential that the ACs are able to locate and connect with the most suitable application server available in the EDN, depending on the needs of the application. The edge enabler layer exposes APIs to support such capabilities.

The edge computing capabilities supported by 3GPP are illustrated in the Figure 4.1-1.

Reproduction of 3GPP TS 23.558, Fig. 4.1-1: Overview of 3GPP edge computing

Figure 4.1-1: Overview of 3GPP edge computing

The application layer is a consumer of 3GPP specified edge computing capabilities. The 3GPP edge computing capabilities are typically organized as follows:

Edge enabler layer, specified in this specification;
Edge hosting environment, details of which are outside the scope of 3GPP;
3GPP transport layer, specified in TS 23.401 and TS 23.501; and
Edge management layer, specified in TS 28.538.

Following clauses provide an overview of the features of edge enabler layer.

The edge computing features defined in this specification are applicable to PLMN(s) and to SNPN(s) as 3GPP transport layer. In this specification, when PLMN is mentioned, it is also applicable for SNPN unless stated otherwise.

4.2 Service provisioning p. 22

Service provisioning procedures supply the information required by the UE to access the edge services. The procedure takes UE's location, service requirements, service preferences and connectivity information into account to provide the required configuration. Service provisioning procedures are specified in clause 8.3.

4.3 Registration p. 22

Registration procedures specified in clause 8.4, allow entities (e.g. UE and Application Server) in the edge enabler layer to provide information about itself to other entities of the edge enabler layer.

4.4 EAS discovery p. 22

EAS discovery procedures enable the UE to obtain information about suitable EASs of interest (specified as discovery filters) in the EDN. EAS discovery procedures are specified in clause 8.5.

4.5 Capability exposure to EAS and EEC p. 22

The edge enabler layer exposes services towards the EASs and EECs. The exposed capabilities include the services of the Edge Enabler Layer and the re-exposed and enhanced services of the 3GPP core network. The capabilities exposed by the edge enabler layer are specified in clause 8.6 and the 3GPP network capability exposure is specified in clause 8.7. Other application layer capabilities like application enabler services and SEAL services may be exposed via edge enabler layer as per CAPIF as illustrated in Annex A.4.

The edge enabler layer also supports for an EAS to expose its Service APIs (i.e., EAS Service APIs) towards the other EASs via CAPIF as specified in TS 23.222 by deploying CAPIF core function within the EES to support publish and discovery of EAS Service APIs. The details are provided in Annex A.5.4.

4.6 Support for service continuity p. 22

When a UE moves to a new location, different EASs can be more suitable for serving the UE. When no suitable EAS can be found for serving the UE, the service session may transition to a CAS. Such transitions can result from a non-mobility event also, requiring support from the edge enabler layer to maintain the continuity of the service. Support for service continuity provides several features for minimizing the application layer service interruption by replacing the S-EAS connected to the AC in the UE, with a T-EAS or CAS. Support for service continuity is further specified in clause 8.8.

4.7 Security p. 22

The edge enabler layer supports secure communication amongst the enabler layer entities. Clause 8.11 provides details on EEC authentication and authorization.

4.8 Dynamic EAS instantiation triggering p. 22

The Edge Enabler Layer can interact with the ECSP management system to trigger instantiation of a suitable EAS as per application needs. Details of the EAS instantiation triggering are specified in clause 8.12.

4.9 Charging p. 22

The general architecture and principles applicable for charging of Edge enabling services provided by an ECSP to an ASP, is specified in TS 32.240.

4.10 Common EAS discovery |R19| p. 23

For the purpose of Common EAS discovery, it is relevant whether the deployment is with or without ECS-ER.