8.15 EAS Information provisioning
23.5583GPPArchitecture for enabling Edge ApplicationsRelease 18TS
8.15.1 General
EAS information provisioning procedure allows the EEC to exchange information with the EES about selected EAS or ACR scenario selection.
When service continuity is required, service continuity scenarios may be combined to perform ACR detection in one or more of the EEC, the EES and the EAS; the related procedures are specified in clauses 8.15.2, 8.6.3 and referred to in clause 8.8.2. The selection of ACR scenario(s) may be performed by the EEC or the EES for a given AC and the selected EAS from the common supported ACR scenarios of AC, EEC, selected EES and selected EAS.
The EAS information provisioning request types supported are:
– “ACR scenario selection announcement”. Inform the EES about the EAS that has been selected by the EEC and may provide the selected ACR scenario list to the EES.
– “ACR scenario selection request”. Inform the EES to perform ACR scenario selection.
8.15.2 Procedure
8.15.2.1 General
8.15.2.2 EAS Information provisioning
Pre-conditions :
1. The EEC has performed service provisioning procedure
2. The EEC has performed the EAS discovery procedure
Figure 8.15.2.2-1: EAS information provisioning procedure
1. The EEC sends the EAS information provisioning request to the EES:
a- “ACR scenario selection announcement”. The request may include ACR scenario list selected by the EEC, EEC security credentials, selected EASID, selected EAS endpoint, EECID and ACID.
b- “ACR scenario selection request”. The request may include AC profile, EEC service continuity support, EEC security credentials, EECID and ACID.
2. Upon receiving the request from the EEC, the EES validates the EEC information request and verifies if the EEC is authorized for this operation.
a- “ACR scenario selection announcement”. The EES may send the ACR Selection notification to the selected EAS if the EAS has subscribed and if EES allows EEC based ACR scenario selection. Otherwise, EES may respond with status failure and include appropriate reason.
b- “ACR scenario selection request”. The EES selects the ACR scenario list and may send the ACR Selection notification to the selected EAS if the EAS has subscribed. The EES may include the ACR scenario list in the EAS information provisioning response.
If the request contains selected EAS ID and selected EAS Endpoint, the EES may apply the EAS traffic influence with the N6 routing information of the EAS in the 3GPP Core Network, based on application KPIs and if the EAS traffic influence was not done before.
NOTE 1: EES can also influence the EAS traffic in advance.
NOTE 2: It is up to the AC to decide when to connect to the selected EAS (either immediately or wait for a while) once the AC knows the selected EAS.
3. If the processing of the request was successful, the EES sends an EAS information provisioning response to the EEC indicating a successful status; otherwise, the EES shall indicate a failure status and include appropriate reasons.
The EEC, EES and EAS use the selected ACR scenario list to determine if they should perform ACR detection and/or ACR decision.
NOTE 3 Other ACR selection criteria are out of scope of the current specification.
NOTE 4: The common supported ACR scenarios is decided as part of the EAS discovery and selection procedure.
NOTE 5: Whether the EES or EEC selects ACR scenario(s) for each selected EAS considering AC service KPI within AC profile (e.g. connection bandwidth, request rate, response time) is implementation specific.
Editor’s note: The procedure, if the EEC or EES does not have sufficient information to decide ACR scenario selection, is FFS.
8.15.3 Information flows
8.15.3.1 General
The information flows are specified for EAS information provisioning request and response.
8.15.3.2 EAS information provisioning request
Table 8.15.3.2-1 describes the information elements for EAS information provisioning request from the EEC to the EES.
Table 8.15.3.2-1: EAS information provisioning request
|
Information element |
Status |
Description |
|
EECID |
M |
The identifier of the EEC. |
|
ACID |
M |
The identifier of the AC. |
|
Security credentials |
M |
Security credentials resulting from a successful authorization for the edge computing service. |
|
Selected EAS ID |
O |
The identifier of the selected EAS |
|
Selected EAS Endpoint |
O |
The endpoint of the selected EAS |
|
Request type |
O |
Request types: – ACR scenario selection announcement – ACR scenario selection request |
|
Selected ACR scenario list (see NOTE 1) |
O |
The list of ACR scenarios selected by the EEC |
|
AC Profile (see NOTE 2, NOTE 3) |
O |
AC Profile as described in Table 8.2.2-1 |
|
EEC Service Continuity Support (NOTE 2) |
O |
Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC. |
|
NOTE 1: The IE may be present only if Selected EASID and Selected EAS Endpoint are present and Request type is “ACR scenario selection announcement” NOTE 2: The IEs are present only if request type is “ACR scenario selection request” NOTE 3: The IE is present if AC Profile is not shared to EES previously |
||
8.15.3.3 EAS information provisioning response
Table 8.15.3.2-1 describes the information elements for EAS information provisioning response from the EES to the EEC.
Table 8.15.3.2-1: EAS information provisioning response
|
Information element |
Status |
Description |
|
Successful response (see NOTE 1) |
O |
Indicates that the request was successful. |
|
> Selected ACR scenario list (see NOTE 2) |
O |
The list of ACR scenarios selected by the EES |
|
Failure response (see NOTE 1) |
O |
Indicates that the request failed. |
|
> Cause |
O |
Indicates the failure cause. |
|
NOTE 1: One of these IEs shall be present in the message. NOTE 2: Only if request type is “ACR scenario selection request” |
||