4 Overview

23.5583GPPArchitecture for enabling Edge ApplicationsRelease 18TS

4.1 General

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.

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 3GPP TS 23.401 [11] and 3GPP TS 23.501 [2]; and

– Edge management layer, specified in 3GPP TS 28.538 [22].

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

4.2 Service provisioning

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

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

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

The edge enabler layer exposes services towards the EASs. 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 3GPP TS 23.222 [6].

4.6 Support for service continuity

When a UE moves to a new location, different EASs can be more suitable for serving the UE. 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. Support for service continuity is further specified in clause 8.8.

4.7 Security

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

The Edge Enabler Layer can interact with the EAS 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

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