8.6.7 Application traffic influence trigger from EAS

23.5583GPPArchitecture for enabling Edge ApplicationsRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.6.7.1 General

An EAS can explicitly request EES to influence the EAS traffic from UE(s) with necessary information. Then the EES can trigger the AF request to influence traffic routing towards the 3GPP CN for one or more UE(s) accessing the EAS.

8.6.7.2 Procedure

Figure 8.6.7.2-1 illustrates the proceduce of application traffic influence trigger from EAS.

Figure 8.6.7.2-1: Application traffic influence trigger from EAS

1. The EAS sends an EAS traffic influence request.

2. The EES performs an authorization check to verify whether the EAS has the authorization to request application traffic influence.

3. Upon successful authorization, the EES includes target DNAI, traffic descriptor information and N6 routing information at target DNAI in the Nnef_TrafficInfluence_Create/Update Request to the NEF, or Npcf_PolicyAuthorization_Create/Update Request to the PCF, to influence the traffic for EAS as described in 3GPP TS 23.501, clause 5.6.7.1.

4. The EES sends the EAS traffic influence response.

8.6.7.3 Information flows

8.6.7.3.1 General

The following information flows are specified for application traffic influence trigger from EAS:

– Application traffic influence trigger from EAS request and response.

8.6.7.3.2 Application traffic influence trigger from EAS request

Table 8.6.7.3.2-1: application traffic influence trigger from EAS request

Information element	Status	Description
EASID	M	Identifier of the EAS
Security credentials	M	Security credentials resulting from a successful authorization for the edge computing service.
Target UE Identifier(s)	M	Indicates the target UE(s) or any UE.

8.6.7.3.3 Application traffic influence trigger from EAS response

Table 8.6.7.3.3-2: application traffic influence trigger from EAS response

Information element	Status	Description
Successful response	O	Indicates that the traffic influence request was successful.
Failure response	O	Indicates that the traffic influence request has failed.
> Cause	O	Indicates the cause of failure

8.6.7.4 APIs

8.6.7.4.1 General

Table 8.6.7.4.1-1 illustrates the APIs for application traffic influence trigger from EAS.

Table 8.6.7.4.1-1: Eees_TrafficInfluenceEAS API

API Name

API Operations

Operation

Semantics

Consumer(s)

Eees_TrafficInfluenceEAS

Create

Request/Response

EAS

8.6.7.4.2 Eees_TrafficInfluenceEAS_Create operation

API operation name: Eees_TrafficInfluenceEAS_Create

Description: The consumer requests traffic influence for EAS via EES.

Inputs: See clause 8.6.7.3.2.

Outputs: See clause 8.6.7.3.3.

See clause 8.6.7.2 for details of usage of this operation.