A.4 Deployment of EES in relation with SEAL services and Application Enabler Services

23.5583GPPArchitecture for enabling Edge ApplicationsRelease 18TS

A.4.1 General

The illustration of layered application architecture with the generic SEAL and Application Enabler server functions available in the cloud is shown in Figure A.4.1-1.

Figure A.4.1-1: Illustration of a layered application architecture with generic SEAL and Application Enabler server functions available in the cloud

The examples of application specific client are V2X application specific client, FF application specific client, UAS application specific client or other vertical application specific client residing on the UE. Similarly, the application specific server could be e.g. V2X application specific server, FF application specific server, UAS application specific server or other vertical application specific server.

The UE may consist of an application enabler client. The examples of application enabler client include V2X application enabler client, FF application enabler client, UAS application enabler client or other vertical application enabler client residing on the UE. Similarly, the application enabler server could be V2X application enabler server, FF application enabler Server, UAS application enabler server or other vertical application enabler server.

The illustration of layered application architecture with generic SEAL and Application Enabler server functions available in the edge is shown in Figure A.4.1-2.

Figure A.4.1-2: Illustration of layered application architecture with generic SEAL and Application Enabler server functions available in the edge

While the server functions of an application specific server can be made available only as an EAS, it is also possible that certain application specific server functions are available both at the edge and in the cloud. Similarly, the server functions of an application enabler server can be made available only as an EAS, it is also possible that certain application enabler server functions are available both at the edge and in the cloud. When the server functions of an application are both available at the edge and the cloud, there may be a need for interaction between the two corresponding application servers, which is out of scope of this specification.

NOTE 1: The details of a specific vertical application architecture based on the generic layered application architecture with server functions of an application available in the edge and the cloud is out of scope of this specification.

NOTE 2: When UE is in the coverage of the EDN due to which certain server functions are available both at the edge and in the cloud, then whether UE connects to the server functions available at the edge or directly to the cloud is out of scope of the present document.

A.4.2 Deployment of SEAL services

There are several options to support SEAL service APIs to be exposed to the EAS.

The EES can act as the CAPIF core function, and the SEAL servers acting the AEF and publish the SEAL service API to the EES. Further, the SEAL service APIs is discovered by the EASs acting as the API invoker during the service API discover procedure as specified in 3GPP TS 23.222 [6].

The EES can act as the API topology hiding entry and re-expose SEAL service APIs as specified in 3GPP TS 23.434 [13] to EAS via EDGE-3 which utilizes the CAPIF-2/2e reference point as specified in 3GPP TS 23.222 [6].

A.4.3 Deployment of Application Enabler services

There are several options to support vertical application enabler server (e.g., V2X application enabler server) APIs to be exposed to the EAS.

The EES can act as the CAPIF core function, and the vertical application enabler server acting the AEF and publish the vertical application enabler server APIs to the EES. Further, the vertical application enabler server APIs is discovered by the EASs acting as the API invoker during the service API discover procedure as specified in 3GPP TS 23.222 [6].

The EES can act as the API topology hiding entry and re-exposes vertical application enabler server APIs, e.g., VAE server APIs as specified in 3GPP TS 23.286 [14] to EAS via EDGE-3 which utilizes the CAPIF-2/2e reference point as specified in 3GPP TS 23.222 [6].