Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.558  Word version:  19.2.0

Top   Top   Up   Prev   Next
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…   E…

 

6.4  Service-based interfacesp. 39

The architecture for enabling edge applications contains the following service-based interfaces:
Eecs:
Service-based interface exhibited by ECS.
Eees:
Service-based interface exhibited by EES.

6.5  Reference Pointsp. 39

6.5.1  Generalp. 39

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

6.5.2  EDGE-1p. 39

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).

6.5.3  EDGE-2p. 39

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:
Up

6.5.4  EDGE-3p. 39

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).
Up

6.5.5  EDGE-4p. 40

EDGE-4 reference point enables interactions between the ECS and the EEC. It supports:
  1. provisioning of Edge configuration information to the EEC.

6.5.6  EDGE-5p. 40

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.

6.5.7  EDGE-6p. 40

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.

6.5.8  EDGE-7p. 40

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:
Up

6.5.9  EDGE-8p. 40

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:
Up

6.5.10  EDGE-9p. 41

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).
Reproduction of 3GPP TS 23.558, Fig. 6.5.10-1: Inter-EDN EDGE-9
Up
Reproduction of 3GPP TS 23.558, Fig. 6.5.10-2: Intra-EDN EDGE-9
Up
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.

6.5.11  NM-UU |R18|p. 41

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

6.5.12  NM-S |R18|p. 41

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

6.5.13  NM-C |R18|p. 42

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

6.5.14  ECI-1 |R18|p. 42

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.
Up

6.5.15  ECI-2 |R18|p. 42

ECI-2 enables interaction between CAS and ECS.

6.5.16  ECI-3 |R18|p. 42

ECI-3 enables interaction between CES and ECS.
ECI-3 supports:
  1. T-EES retrieval procedure.

6.5.17  ECI-4 |R18|p. 42

ECI-4 enables interaction between CES and EES.
ECI-4 supports:
  1. EEC context relocation procedure; and
  2. ACR parameter information procedure.

6.5.18  CLOUD-1 |R18|p. 42

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).

6.5.19  CLOUD-2 |R18|p. 42

CLOUD-2 enables interaction between CES and CES.

6.5.20  CLOUD-3 |R18|p. 43

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

6.5.21  CLOUD-4 |R18|p. 43

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

6.5.22  EDGE-10 |R18|p. 43

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.

6.6  Cardinality rulesp. 43

6.6.1  Generalp. 43

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.
Up

6.6.2  Functional Entity Cardinalityp. 43

6.6.2.1  Generalp. 43

6.6.2.2  ACp. 43

The following cardinality rules apply for ACs:
  1. one or more ACs may be located in a UE.

6.6.2.3  EECp. 43

The following cardinality rules apply for EECs:
  1. One or more EEC(s) may be located in a UE.

6.6.2.4  ECSp. 43

The following cardinality rules apply for ECSs:
  1. One or more ECS(s) may be deployed to support one EDN;
  2. One ECS may be deployed to support one or more EDN(s);
  3. One or more ECS(s) may be deployed by a PLMN operator; and
  4. One or more ECS(s) may be deployed by an ECSP.
Following cardinality rule apply to the ECS that supports edge repository functionality and acts as an ECS-ER:
  1. One ECS-ER may be deployed by a PLMN operator; and
  2. One ECS-ER may be deployed by an ECSP.

6.6.2.5  EESp. 44

The following cardinality rules apply for EES:
  1. One or more EES(s) may be located in an EDN; and
  2. One or more EES(s) may be located in an EDN per ECSP.

6.6.2.6  EASp. 44

The following cardinality rules apply for EASs:
  1. One or more EAS(s) may be located in an EDN.

6.6.2.7  CES |R18|p. 44

The following cardinality rules apply for CES:
  1. One CES may be located in a cloud DN per ECSP.

6.6.2.8  CAS |R18|p. 44

The following cardinality rules apply for CASs:
  1. One or more CAS(s) may be located in a cloud DN.

6.6.3  Reference Point Cardinalityp. 44

6.6.3.1  Generalp. 44

Void.

6.6.3.2  EDGE-1 (Between EEC and EES)p. 44

The following cardinality rules apply for EDGE-1:
  1. One EEC may communicate with one or more EES(s) for one or more AC concurrently; and
  2. One EES may communicate with one or more EEC(s) concurrently.

6.6.3.3  EDGE-3 (Between EAS and EES)p. 44

The following cardinality rules apply for EDGE-3:
  1. One EAS may communicate with only one EES within the same EDN; and
  2. One EES may communicate with one or more EAS(s) concurrently.

6.6.3.4  EDGE-4 (Between EEC and ECS)p. 44

The following cardinality rules apply for EDGE-4:
  1. One EEC may communicate with one or more ECS(s) concurrently; and
  2. One ECS may communicate with one or more EEC(s) concurrently.

6.6.3.5  EDGE-5 (Between AC and EEC)p. 45

The following cardinality rules apply for EDGE-5:
  1. One AC may communicate with only one EEC; and
  2. One EEC may communicate with one or more AC(s) concurrently.

6.6.3.6  EDGE-6 (Between EES and ECS)p. 45

The following cardinality rules apply for EDGE-6:
  1. One EES may communicate with one or more ECS(s) concurrently; and
  2. One ECS may communicate with one or more EES(s) concurrently.

6.6.3.7  EDGE-9 (Between EES and EES)p. 45

The following cardinality rules apply for EDGE-9:
  1. One EES may communicate with one or more EES(s) concurrently.

6.6.3.8  EDGE-10 (Between ECS and ECS) |R18|p. 45

Following cardinality rules apply for EDGE-10:
  1. One ECS may communicate with one or more ECS(s) concurrently.

6.6.3.9  ECI-1 (Between CAS and EES) |R18|p. 45

The following cardinality rules apply for ECI-1:
  1. One CAS may communicate with one or more EES(s) concurrently; and
  2. One EES may communicate with one or more CAS(s) concurrently.

6.6.3.10  ECI-2 (Between CAS and ECS) |R18|p. 45

The following cardinality rules apply for ECI-2:
  1. One CAS may communicate with one or more ECS(s) concurrently; and
  2. One ECS may communicate with one or more CAS(s) concurrently.

6.6.3.11  ECI-3 (Between CES and ECS) |R18|p. 45

The following cardinality rules apply for ECI-3:
  1. One CES may communicate with one or more ECS(s) concurrently; and
  2. One ECS may communicate with one or more CES(s) concurrently.

6.6.3.12  ECI-4 (Between CES and EES) |R18|p. 45

The following cardinality rules apply for ECI-4:
  1. One CES may communicate with one or more EES(s) concurrently; and
  2. One EES may communicate with one or more CES(s) concurrently.

6.6.3.13  CLOUD-1 (Between CAS and CES) |R18|p. 46

The following cardinality rules apply for CLOUD-1:
  1. One CAS may communicate with only one CES within the same cloud DN; and
  2. One CES may communicate with one or more CAS(s) concurrently.

6.6.3.14  CLOUD-2 (Between CES and CES) |R18|p. 46

The following cardinality rules apply for CLOUD-2:
  1. One CES may communicate with one or more CES(s) concurrently.

6.7  Capability exposure for enabling edge applicationsp. 46

6.7.1  Generalp. 46

The Figure 6.7.1-1 shows the capability exposure for enabling edge applications.
Reproduction of 3GPP TS 23.558, Fig. 6.7.1-1: Capability exposure for enabling edge applications
Up
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.

6.7.2  APIs provided by the Edge Enabler Layerp. 46

Table 6.7.2-1 summarizes the APIs exposed by the ECS.
API Name Known Consumers References
Eecs_ServiceProvisioningEEC 8.3
Eecs_EESRegistrationEES 8.4.4
Eecs_TargetEESDiscoveryEES, CES 8.8.3.3
Eecs_ECSRegistrationECS 8.17.2.2
Eecs_ECSDiscoveryECS 8.17.2.3
Eecs_ECSServiceProvisioningECS 8.17.2.4
Eecs_EASInfoManagementEES 8.20.2
Eecs_ACREventsEES 8.8.3.11
Table 6.7.2-2 summarizes the APIs exposed by the EES.
API Name Known Consumers References
Eees_EECRegistrationEEC 8.4.2
Eees_EASRegistrationEAS 8.4.3
Eees_EASDiscoveryEEC 8.5
Eees_UELocationEAS 8.6.2
Eees_ACRManagementEventEAS, EES, CAS 8.6.3
Eees_AppClientInformationEAS 8.6.4
Eees_UEIdentifierEEC, EAS 8.6.5
Eees_SessionWithQoSEAS 8.6.6
Eees_TrafficInfluenceEASEAS 8.6.7
Eees_TargetEASDiscoveryEAS, EES, CAS 8.8.3.2
Eees_AppContextRelocationEEC, EAS, EES 8.8.3.4
Eees_ACREventsEEC 8.8.3.5
Eees_EELManagedACREES, EAS 8.8.3.6
Eees_SelectedTargetEASEAS, CAS, EES 8.8.3.7
Eees_ACRStatusUpdateEAS, CAS, EES 8.8.3.8
Eees_ACRParameterInformationEES, CES 8.8.3.9
Eees_EECContextPullEES 8.9.4.2
Eees_EECContextPushEES 8.9.4.3
Eees_EASInformationProvisioningEEC, EES 8.15
Eees_CommonEasAnnouncementEES 8.19
Table 6.7.2-3 summarizes the APIs exposed by the CAS.
API Name Known Consumers References
Ecas_SelectedEESEES 8.8.3.10
Table 6.7.2-4 summarizes the APIs exposed the EEC.
API Name Known Consumers References
Eeec_ACRegistrationAC 8.14.4.2
Eeec_EASDiscoveryAC 8.14.4.3
Eeec_ACRTriggerAC 8.14.4.4
Eeec_ServicesAC 8.14.4.5
Eeec_UEIdAC 8.14.4.6
Table 6.7.2-5 summarizes the EES APIs re-used by the CES.
API Name Known Consumers References
Eees_EASRegistrationCAS 8.4.3
Eees_UELocationCAS 8.6.2
Eees_ACRManagementEventCAS 8.6.3
Eees_AppClientInformationCAS 8.6.4
Eees_UEIdentifierCAS 8.6.5
Eees_SessionWithQoSCAS 8.6.6
Eees_TrafficInfluenceEASCAS 8.6.7
Eees_TargetEASDiscoveryEES 8.8.3.2
Eees_AppContextRelocationCAS 8.8.3.4
Eees_ACREventsEEC 8.8.3.5
Eees_SelectedTargetEASCAS 8.8.3.7
Eees_ACRStatusUpdateCAS 8.8.3.8
Eees_ACRParameterInformationEES 8.8.3.9
Eees_EECContextPushEES 8.9.4.3
Up

Up   Top   ToC