Content for &nbsp; TS 23.558 &nbsp; Word version:&nbsp; 19.3.0

The EAS requests establishment of a data session between the AC and the EAS with a specific QoS (either QoS reference or bandwidth). If the data session can adjust to different QoS parameter combinations, the request may include a list of alternative QoS references in a priority order. The EAS shall include the UE's IP address, UE ID or UE Group ID, the DNN and S-NSSAI used for the data session between AC and EAS. With the same request the EAS subscribes to receive certain session with QoS event notifications (e.g. notifications related to QoS monitoring, usage monitoring for sponsored data connectivity and/or QoS targets can no longer (or can again) be fulfilled).

The EES checks if the EAS is authorized for this operation for the UE. If authorized, then the following services of 3GPP CN may be used by the EES:

the EES invokes the PFD management procedure with the 3GPP Core Network as described in TS 23.682 and TS 23.502 with an application id. At least one of the IP flow description, domain description or URI sent by the EAS is used for requesting PFD management service. Further the EES provides the same application id for requesting data session with specific QoS in step 2c or step 4.

NOTE 1:
PFD management can be optionally supported in MNO. If EES cannot invoke step 2a, it responds EAS with appropriate error.

NOTE 2:
The EES can map the EASID into the application id that is used to invoke the PFD management procedure.
the EES invokes the Event Monitoring service for PDU session status with the 3GPP Core Network, as described in TS 23.502.
the EES invokes the Policy Authorization Create service or the AF Session with QoS service with the 3GPP Core Network (PCF or NEF, respectively) as described in TS 23.501 and TS 23.502, providing the specific QoS (QoS reference or bandwidth) to the PCF as described in clause 6.1.3.22 of TS 23.503. Additionally, the EES may subscribe to notifications of resource allocation outcome and to other events described in clause 6.1.3.18 of TS 23.503, e.g. notifications of when the QoS targets can no longer (or can again) be fulfilled.

The usage of step 2b and step 2c is as follows:

If the request is for a group of UEs identified by the UE Group ID or for a single UE identified by the UE ID, then EES executes step 2b. If UE (single UE or UE group member) already has ongoing PDU session, then UE IP address is retrieved in step 2b. Further the EES executes step 2c; otherwise the EES waits for further notification for PDU session status in step 4.
If the request is for a single UE identified by the IP address, then EES executes step 2c.

If the operation in step 2 is successful, the EES responds with a Context ID and a Result. The Context ID is to be used by the EAS for further requests (e.g. session with QoS update requests) pertaining to the same UE. If the EAS is not authorized or any other failure happens during the operation, the EES provides a rejection response with cause information.

Figure 8.6.6.2.3-1: Session with QoS API: update operation

When the EES receives the corresponding UE IP address for the single UE or UE group member from the PDU session status notification sent by the 3GPP Core Network, the EES requests data session with specific QoS as described in step 2c.

8.6.6.2.3 Update a session p. 146

Figure 8.6.6.2.3-1 illustrates the session with QoS update request operation between the EAS and the EES. It is used to request a modification of the QoS of the data session between AC and EAS.

Reproduction of 3GPP TS 23.558, Fig. 8.6.6.2.3-1: Session with QoS API: update operation

The EAS requests a modification of the QoS of the data session between the AC and the EAS, e.g. by including a different QoS reference or different bandwidth value. The EAS shall include the Context ID.

The EAS may also request a modification of the event monitoring by subscribing to new events and updating or removing subscriptions to existing events.

The EES checks if there is a context for the Context ID available and whether the EAS is authorized for this operation. If yes and the UE IP address is known by the EES, the EES invokes the Policy Authorization Update service or AF Session with QoS Update service with the 3GPP Core Network (PCF or NEF, respectively) as described in TS 23.501 and TS 23.502, providing the updated information to the PCF or NEF, respectively. The EES may subscribe to additional events or unsubscribe to certain events, if necessary.

Figure 8.6.6.2.4-1: Session with QoS API: revoke operation

If the operation is successful, the EES responds with a Context ID and a Result. If the EAS is not authorized or any other failure happens during the operation, the EES provides a rejection response with cause information.

8.6.6.2.4 Revoke a session p. 147

Figure 8.6.6.2.4-1 illustrates the session with QoS revoke operation between the EAS and the EES. It is used to revoke the data session between AC and EAS with a specific QoS and to unsubscribe to the related session with QoS event notifications.

Reproduction of 3GPP TS 23.558, Fig. 8.6.6.2.4-1: Session with QoS API: revoke operation

The EAS requests a revoke of the data session with QoS between the AC and the EAS. The EAS shall include the Context ID.

The EES checks if there is a context for the Context ID available and whether the EAS is authorized for this operation. If yes, then the EES unsubscribes from the PDU session status monitoring (if applicable) and invokes the Policy Authorization Delete service or AF Session with QoS Revoke service with the 3GPP Core Network (PCF or NEF, respectively) as described in TS 23.501 and TS 23.502. This deletes the application session context at the PCF or NEF and removes the subscription to any session with QoS event notifications.

Figure 8.6.6.2.5-1: Session with QoS API: notify operation

8.6.6.2.5 Notify p. 147

Figure 8.6.6.2.5-1 illustrates the notify operation between the EES and the EAS for session with QoS event notifications.

Reproduction of 3GPP TS 23.558, Fig. 8.6.6.2.5-1: Session with QoS API: notify operation

The EES detects a user plane event associated with the established session (i.e. it receives a Policy Authorization Notify operation from the PCF or an AF Session with QoS Notify operation from the NEF as described in TS 23.501 and TS 23.502). The EES determines to notify the session with QoS event notification information (e.g., resource allocation outcome or information that the QoS targets can no longer (or can again) be fulfilled) to the EASs which have subscribed to the session with QoS event notification.

Table 8.6.6.3.2-1: Session with QoS create request

The EES sends a session with QoS event notification to the EAS. The EES includes the session with QoS event notification information of the UE.

8.6.6.3 Information flows p. 148

8.6.6.3.1 General p. 148

The following information flows are specified for Session with QoS API:

Session with QoS create request and response;
Session with QoS update request and response;
Session with QoS revoke request and response; and
Session with QoS event notification.

8.6.6.3.2 Session with QoS create request p. 148

Table 8.6.6.3.2-1 describes the information elements for a Session with QoS create request from the EAS to the EES.

Information element	Status	Description
EASID	M	The identifier of the EAS.
Security credentials	M	Security credentials of the EAS.
UE IP address (NOTE 1)	O	The UE IP address.
UE ID (NOTE 1)	O	The identifier of the UE (i.e. GPSI)
UE Group ID (NOTE 1)	O	Identifies a group of UEs as defined in clause 7.2.7.
IP flow description (NOTE 4)	O	The IP flow description for the application traffic.
Domain description (NOTE 4)	O	The domain description including domain name, applicable protocol and matching criteria (e.g. TLS SNI).
URI (NOTE 4)	O	Uniform resource identifier. It represents the application traffic URI.
Requested QoS reference (NOTE 2)	O	Refers to pre-defined QoS information for the data session between AC and EAS (NOTE 3).
List of alternative QoS references	O	A list of alternative QoS references, referring to pre-defined QoS information for the data session between AC and EAS and containing one or more QoS reference parameters in a prioritized order (NOTE 3).
Event list	O	A list of associated events to which the EAS subscribes (see clause 6.1.3.18 of TS 23.503).
> Event specific data	O	For usage monitoring: the sponsoring information (sponsor id, ASP id). For QoS monitoring: Target of monitoring (DL, UL or roundtrip packet delay).
> Frequency of reporting	O	The reporting frequency (e.g. event triggered) and additional related data (e.g. threshold, minimum waiting time) as described in clause 6.1.3.21 of TS 23.503, applicable for QoS monitoring event.
Notification Target Address	M	The Notification Target Address (e.g. URL) where the notifications destined for the EAS should be sent to.
DNN	O	DNN for the data session between AC and EAS.
S-NSSAI	O	S-NSSAI for the data session between AC and EAS.
Requested bandwidth (NOTE 2)	O	Bandwidth requested for the data session between AC and EAS.
NOTE 1: Only one of UE IP address, UE ID or UE Group ID shall be provided. NOTE 2: Only one of requested QoS reference or requested bandwidth shall be provided. NOTE 3: The pre-defined QoS information may be configured in the EES or in the 3GPP Core Network (see clause 6.1.3.22 of TS 23.503). NOTE 4: At least one of these information elements shall be present.

8.6.6.3.3 Session with QoS create response p. 149

Table 8.6.6.3.3-1 describes the information elements for a Session with QoS create response from the EES to the EAS.

Table 8.6.6.3.3-1: Session with QoS create response

Information element	Status	Description
Successful response	O	Indicates that the Session with QoS create request was successful.
> Context ID	M	Context identifier corresponding to the information stored for the request in the EES
Failure response	O	Indicates that the Session with QoS create request failed.
> Cause	O	Indicates the cause of Session with QoS create request failure

8.6.6.3.4 Session with QoS update request p. 150

Table 8.6.6.3.4-1 describes the information elements for a Session with QoS update request from the EAS to the EES.

Table 8.6.6.3.4-1: Session with QoS update request

Information element	Status	Description
Security credentials	M	Security credentials of the EAS
Context ID	M	Context identifier corresponding to the information stored for the request in the EES.
Requested QoS reference (NOTE 1)	O	Refers to pre-defined QoS information for the data session between AC and EAS (NOTE 2).
List of alternative QoS references	O	A list of alternative QoS references, referring to pre-defined QoS information for the data session between AC and EAS and containing one or more QoS reference parameters in a prioritized order (NOTE 2).
Event list	O	A list of associated events to which the EAS subscribes (see clause 6.1.3.18 of TS 23.503).
> Event specific data	O	For usage monitoring: the sponsoring information (sponsor id, ASP id). For QoS monitoring: Target of monitoring (DL, UL or roundtrip packet delay).
> Frequency of reporting	O	The reporting frequency (e.g. event triggered) and additional related data (e.g. threshold, minimum waiting time) as described in clause 6.1.3.21 of TS 23.503, applicable for QoS monitoring event.
Requested bandwidth (NOTE 1)	O	Bandwidth requested for the data session between AC and EAS
NOTE 1: Only one of requested QoS reference or requested bandwidth shall be provided. NOTE 2: The pre-defined QoS information may be configured in the EES or in the 3GPP Core Network (see clause 6.1.3.22 of TS 23.503).

8.6.6.3.5 Session with QoS update response p. 150

Table 8.6.6.3.5-1 describes the information elements for a Session with QoS update response from the EES to the EAS.

Table 8.6.6.3.5-1: Session with QoS update response

Information element	Status	Description
Successful response	O	Indicates that the Session with QoS update request was successful.
Failure response	O	Indicates that the Session with QoS update request failed.
> Cause	O	Indicates the cause of Session with QoS update request failure

8.6.6.3.6 Session with QoS revoke request p. 150

Table 8.6.6.3.6-1 describes the information elements for a Session with QoS revoke request from the EAS to the EES.

Table 8.6.6.3.6-1: Session with QoS event API revoke request

Information element	Status	Description
Security credentials	M	Security credentials of the EAS
Context ID	M	Context identifier corresponding to the information stored for the request in the EES

8.6.6.3.7 Session with QoS revoke response p. 151

Table 8.6.6.3.7-1 describes the information elements for a Session with QoS revoke response from the EES to the EAS.

Table 8.6.6.3.7-1: Session with QoS revoke response

Information element	Status	Description
Successful response	O	Indicates that the Session with QoS revoke request was successful.
Failure response	O	Indicates that the Session with QoS revoke request failed.
> Cause	O	Indicates the cause of Session with QoS revoke request failure

8.6.6.3.8 Session with QoS event notification p. 151

Table 8.6.6.3.8-1 describes the information elements for a Session with QoS event notification from the EES to the EAS.

Table 8.6.6.3.8-1: Session with QoS event notification

Information element	Status	Description
Context ID	M	Context identifier corresponding to the information stored in the EES during the initial session with QoS create request.
Event report (NOTE)	M	Event reporting information as specified in clause 6.1.3.18 of TS 23.503.
NOTE: Only the following events are applicable: Reporting Usage for Sponsored Data Connectivity Service Data Flow deactivation Resource allocation outcome QoS targets can no longer (or can again) be fulfilled QoS Monitoring parameters

8.6.6.4 APIs p. 151

8.6.6.4.1 General p. 151

Table 8.6.6.4.1-1 illustrates the API for Session with QoS.

Table 8.6.6.4.1-1: Eees_SessionWithQoS API

API Name	API Operations	Operation Semantics	Consumer(s)
Eees_SessionWithQoS	Create	Request/ Response	EAS
	Update
	Revoke
	Notify	Subscribe/ Notify (NOTE)	EAS
NOTE: The Subscribe operation is embedded in the Request operation of the Create and Update API operation.

8.6.6.4.2 Eees_SessionWithQoS_Create operation p. 151

API operation name:

Eees_SessionWithQoS_Create

Description:

The consumer requests a data session with the UE with a specific QoS and may also subscribe to certain event notifications related to the user plane traffic.

Inputs:

See clause 8.6.6.3.2.

Outputs:

See clause 8.6.6.3.3.

See clause 8.6.6.2.2 for details of usage of this operation.

8.6.6.4.3 Eees_SessionWithQoS_Update operation p. 152

API operation name:

Eees_SessionWithQoS_Update

Description:

The consumer requests a modification of the QoS of the data session with the UE and may also update event notifications related to the user plane traffic.

Inputs:

See clause 8.6.6.3.4.

Outputs:

See clause 8.6.6.3.5.

See clause 8.6.6.2.3 for details of usage of this operation.

8.6.6.4.4 Eees_SessionWithQoS_Revoke operation p. 152

API operation name:

Eees_SessionWithQoS_Revoke

Description:

The consumer requests a revoke of the data session with QoS with the UE and unsubscribes to all related event notifications.

Inputs:

See clause 8.6.6.3.6.

Outputs:

See clause 8.6.6.3.7.

See clause 8.6.6.2.4 for details of usage of this operation.

8.6.6.4.5 Eees_SessionWithQoS_Notify operation p. 152

API operation name:

Eees_SessionWithQoS_Notify

Description:

The consumer is notified by the EES of an event related to the user plane traffic.

Inputs:

See clause 8.6.6.3.8.

Outputs:

None.

See clause 8.6.6.2.5 for details of usage of this operation.

8.6.7 Application traffic influence trigger from EAS |R18| p. 152

8.6.7.1 General p. 152

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 p. 152

8.6.7.2.1 Procedure of application traffic influence trigger from EAS p. 152

Figure 8.6.7.2.1-1 illustrates the procedure of application traffic influence trigger from EAS.

Reproduction of 3GPP TS 23.558, Fig. 8.6.7.2.1-1: Application traffic influence trigger from EAS

Figure 8.6.7.2.1-1: Application traffic influence trigger from EAS

The EAS sends an EAS traffic influence request.

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

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

Figure 8.6.7.2.2-1: Application traffic influence update trigger from EAS

The EES sends the EAS traffic influence response.

8.6.7.2.2 Procedure of application traffic influence update trigger from EAS p. 153

Figure 8.6.7.2.2-1 illustrates the procedure of application traffic influence update trigger from EAS.

Reproduction of 3GPP TS 23.558, Fig. 8.6.7.2.2-1: Application traffic influence update trigger from EAS

The EAS sends an EAS traffic influence update request providing the corresponding transaction ID, and updated target UE Identifier(s).

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

Upon successful authorization, the EES do the update accordingly. For those UE(s) to be deleted, the EES invokes the Nnef_TrafficInfluence_Delete or Npcf_PolicyAuthorization_Delete Request to delete the original request to delete the traffic influence for EAS. For those UE(s) to be added, the EES invokes the Nnef_TrafficInfluence_Create or Npcf_PolicyAuthorization_Create.

Figure 8.6.7.2.3-1: Application traffic influence cancellation trigger from EAS

The EES sends the EAS traffic influence update response.

8.6.7.2.3 Procedure of application traffic influence cancellation trigger from EAS p. 154

Figure 8.6.7.2.3-1 illustrates the procedure of application traffic influence cancellation trigger from EAS.

Reproduction of 3GPP TS 23.558, Fig. 8.6.7.2.3-1: Application traffic influence cancellation trigger from EAS

The EAS sends an EAS traffic influence cancellation request providing the corresponding transaction ID.

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

Upon successful authorization, the EES includes transaction ID in the Nnef_TrafficInfluence_Delete Request to the NEF, or Npcf_PolicyAuthorization_Delete Request to the PCF, to delete the traffic influence for EAS as described in clause 5.6.7.1 of TS 23.501.