Content for  TS 23.558  Word version:  19.4.0

This clause describes the reference points of the architecture for enabling edge applications.

EDGE-1 reference point enables interactions between the EES and the EEC. It supports:

1. registration and de-registration of the EEC to the EES;
2. retrieval and provisioning of EAS configuration information;
3. discovery of EASs available in the EDN; and
4. service continuity procedures (e.g. ACR initiation).

EDGE-2 reference point enables interactions between the EES and the 3GPP Core Network functions and APIs for retrieval of network capability information. It supports:

• access via SCEF and NEF APIs as defined in TS 23.501, TS 23.502, TS 29.522, TS 23.682, TS 29.122; or
• direct access to core network functions with the EES deployed within the MNO trust domain (see clause 5.13 of TS 23.501, TS 23.503, TS 23.682).

EDGE-3 reference point enables interactions between the EES and the EASs. It supports:

1. registration of EASs with availability information (e.g. time constraints, location constraints);
2. de-registration of EASs from the EES;
3. discovery of T-EAS information to support ACT;
4. providing access to network capability information (e.g. location information);
5. requesting the setup of a data session between AC and EAS with a specific QoS and receiving QoS related information; and
6. service continuity procedures (e.g. ACR status).

EDGE-4 reference point enables interactions between the ECS and the EEC. It supports:

1. provisioning of Edge configuration information to the EEC.

EDGE-5 reference point enables interactions between AC(s) and the EEC. It supports:

1. registration, registration update and de-registration of AC to the EEC;
2. EAS discovery by the AC;
3. ACR triggering by the AC;
4. EEC services subscription; and
5. UE ID request.

EDGE-6 reference point enables interactions between the ECS and the EES. It supports:

1. registration of EES information to the ECS;
2. de-registration of EES information from the ECS;
3. retrieval of the T-EES information from the ECS; and
4. subscription and notification for service continuity related events.

EDGE-7 reference point enables interactions between the EAS and the 3GPP Core Network functions and APIs for retrieval of network capability information. It supports:

• access via SCEF and NEF APIs as defined in TS 23.501, TS 23.502, TS 29.522, TS 23.682, TS 29.122; or
• direct access to core network functions with the EAS deployed within the MNO trust domain (see clause 5.13 of TS 23.501, TS 23.682).

EDGE-8 reference point enables interactions between the ECS and the 3GPP Core Network functions and APIs for retrieval of network capability information. It supports:

• access via SCEF and NEF APIs as defined in TS 23.501, TS 23.502, TS 29.522, TS 23.682, TS 29.122; or
• direct access to core network functions with the ECS deployed within the MNO trust domain (see clause 5.13 of TS 23.501, TS 23.682).

EDGE-9 reference point enables interactions between two EESs. EDGE-9 reference point may be provided between EES within different EDN (Figure 6.5.10-1) and within the same EDN (Figure 6.5.10-2).

EDGE-9 supports:

1. discovery of T-EAS information to support ACR;
2. EEC context relocation procedures; and
3. transparent transfer of the application context during EELManagedACR.

NM-UU reference point is as specified in TS 23.434.

NM-S reference point is as specified in TS 23.434, where EES or ECS acts VAL server.

NM-C reference point is as specified in TS 23.434, where EEC acts as VAL client.

ECI-1 enables interaction between CAS and EES. ECI-1 supports:

1. notifying the CAS about selection of an EES to provide edge enabler services;
2. discovery of T-EAS to support ACT from CAS to T-EAS; and
3. selected T-EAS declaration where CAS acts as S-EAS.

ECI-1 supports:

1. ACR status update between EES and CAS as specified in clause 8.8.2A.6; and
2. T-EAS discovery procedure initiated by CAS as specified in clause 8.8.2A.6.

ECI-2 enables interaction between CAS and ECS.

ECI-3 enables interaction between CES and ECS. ECI-3 supports:

1. T-EES retrieval procedure.

ECI-4 enables interaction between CES and EES. ECI-4 supports:

1. EEC context relocation procedure; and
2. ACR parameter information procedure.

CLOUD-1 enables interaction between CAS and CES. CLOUD-1 supports:

1. providing access to network capability information (e.g. location information);
2. requesting the setup of a data session between AC and CAS with a specific QoS and receiving QoS related information; and
3. service continuity procedures (e.g. ACR status).

CLOUD-2 enables interaction between CES and CES.

CLOUD-3 enables interaction between CAS and the 3GPP core network.

CLOUD-4 enables interaction between CES and the 3GPP core network.

EDGE-10 reference point enables interactions between the ECS and another ECS. It supports:

1. service provisioning information retrieval.
2. registration and de-registration of the ECS to the ECS acting as edge repository; and
3. retrieval or discovery of information about other ECS(s) of the federation.

The cardinality rules are applied to the architecture specified in clause 6.2. The cardinality rules are classified as functional entity cardinality and reference point cardinality. The functional entity cardinality specifies the multiplicity of the functional entity that can exist as per the architecture. The reference point cardinality specifies the multiplicity of source and target functional entities that can exist in a relationship defined by the reference point in the architecture.

The Figure 6.7.1-1 shows the capability exposure for enabling edge applications.

Capability exposure includes the 3GPP core network (i.e. 5GC, EPC), ECS and the EES capability exposure, to fulfil the needs of the edge service operations. The capability exposure functionality is utilized by the functional entities (i.e. EES, EAS and ECS) depicted in the architecture for enabling the edge applications.

Table 6.7.2-1 summarizes the APIs exposed by the ECS.

Table 6.7.2-2 summarizes the APIs exposed by the EES.

Table 6.7.2-3 summarizes the APIs exposed by the CAS.

Table 6.7.2-4 summarizes the APIs exposed the EEC.

Table 6.7.2-5 summarizes the EES APIs re-used by the CES.

The Figure 6.8.1-1 shows the capability exposure for enabling cloud applications with edge applications, when CES is used.

To enable the interworking with Cloud Application Server (CAS) and Cloud Enabler Server (CES) residing in the cloud DN, the edge enablement layer may include, in addition to the capability exposure described in clause 6.7.1, the CES capability exposure, which is utilized by the CAS for enabling edge applications.

The Figure 6.9.1-1 shows the capability exposure for enabling cloud applications with edge applications.

The Cloud Application Server residing in the cloud DN, outside the EDN, may need to interact with the EEL entities for enabling edge applications.