Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.558  Word version:  19.0.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… 
8.6.6 Session with QoS API  8.6.6.1 General  8.6.6.2 Procedures  8.6.6.2.1 General  8.6.6.2.2 Create a session  8.6.6.2.3 Update a session  8.6.6.2.4 Revoke a session  8.6.6.2.5 Notify  8.6.6.3 Information flows  8.6.6.3.1 General  8.6.6.3.2 Session with QoS create request  8.6.6.3.3 Session with QoS create response  8.6.6.3.4 Session with QoS update request  8.6.6.3.5 Session with QoS update response  8.6.6.3.6 Session with QoS revoke request  8.6.6.3.7 Session with QoS revoke response  8.6.6.3.8 Session with QoS event notification  8.6.6.4 APIs  8.6.6.4.1 General  8.6.6.4.2 Eees_SessionWithQoS_Create operation  8.6.6.4.3 Eees_SessionWithQoS_Update operation  8.6.6.4.4 Eees_SessionWithQoS_Revoke operation  8.6.6.4.5 Eees_SessionWithQoS_Notify operation  8.6.7 Application traffic influence trigger from EAS  8.6.7.1 General  8.6.7.2 Procedure  8.6.7.3 Information flows  8.6.7.3.1 General  8.6.7.3.2 Application traffic influence trigger from EAS request  8.6.7.3.3 Application traffic influence trigger from EAS response  8.6.7.4 APIs  8.6.7.4.1 General  8.6.7.4.2 Eees_TrafficInfluenceEAS_Create operation 
...

 

8.6.6  Session with QoS API  p. 136

8.6.6.1  General  p. 136

The EES exposes the Session with QoS API to the EAS in order to support the setup of a data session between AC and EAS with a specific QoS and the modification of the QoS of this data session.
The Session with QoS API exposed by the EES relies on the northbound Policy Authorization Service API exposed by the PCF as specified in TS 23.502 and TS 23.503, if the EES is connected to the PCF via the N5 reference point, or on the northbound AF Session with QoS Service API exposed by the NEF as specified in TS 23.502 and TS 23.503, if the EES is connected to the PCF via an NEF.
This API supports to apply the required QoS for both ongoing session and future session for a UE or a group of UEs.
The level of support of the Session with QoS API may change due to UE mobility between 5GC and EPC. E.g. QoS monitoring is only applicable in 5GC. If an EES exposes the Session with QoS API to EAS(s) for a UE, the EES monitors such changes and provides the available information to the EAS.
Alternatively to using the API described in the following clauses, the EAS may also act as an AF and directly access the 3GPP Core Network capabilities to request an AF session with QoS (see clause 8.7.2). For any data session between AC and EAS, the EAS shall use only one of these alternatives.
Up

8.6.6.2  Procedures  p. 136

8.6.6.2.1  General  p. 136
Void
8.6.6.2.2  Create a session  p. 136
Figure 8.6.6.2.2-1 illustrates the session with QoS create operation between the EAS and the EES. It is used to request reservation of resources for a data session between AC and EAS with a specific QoS and to subscribe to certain session with QoS event notifications.
Reproduction of 3GPP TS 23.558, Fig. 8.6.6.2.2-1: Session with QoS API: create operation
Figure 8.6.6.2.2-1: Session with QoS API: create operation
Up
Step 1.
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).
Step 2.
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:
  1. 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.
  2. the EES invokes the Event Monitoring service for PDU session status with the 3GPP Core Network, as described in TS 23.502.
  3. 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.
Step 3.
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.
Step 4.
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.
Up
8.6.6.2.3  Update a session  p. 138
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
Figure 8.6.6.2.3-1: Session with QoS API: update operation
Up
Step 1.
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.
Step 2.
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.
Step 3.
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.
Up
8.6.6.2.4  Revoke a session  p. 139
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
Figure 8.6.6.2.4-1: Session with QoS API: revoke operation
Up
Step 1.
The EAS requests a revoke of the data session with QoS between the AC and the EAS. The EAS shall include the Context ID.
Step 2.
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.
Step 3.
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.
Up
8.6.6.2.5  Notify  p. 139
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
Figure 8.6.6.2.5-1: Session with QoS API: notify operation
Up
Step 1.
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.
Step 2.
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.
Up

8.6.6.3  Information flows  p. 140

8.6.6.3.1  General  p. 140
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. 140
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
EASIDMThe identifier of the EAS.
Security credentialsMSecurity credentials of the EAS.
UE IP address (NOTE 1)OThe UE IP address.
UE ID (NOTE 1)OThe identifier of the UE (i.e. GPSI)
UE Group ID (NOTE 1)OIdentifies a group of UEs as defined in clause 7.2.7.
IP flow description (NOTE 4)OThe IP flow description for the application traffic.
Domain description (NOTE 4)OThe domain description including domain name, applicable protocol and matching criteria (e.g. TLS SNI).
URI (NOTE 4)OUniform resource identifier. It represents the application traffic URI.
Requested QoS reference (NOTE 2)ORefers to pre-defined QoS information for the data session between AC and EAS (NOTE 3).
List of alternative QoS referencesOA 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 listOA list of associated events to which the EAS subscribes (see clause 6.1.3.18 of TS 23.503).
> Event specific dataOFor usage monitoring: the sponsoring information (sponsor id, ASP id).
For QoS monitoring: Target of monitoring (DL, UL or roundtrip packet delay).
> Frequency of reportingOThe 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 AddressMThe Notification Target Address (e.g. URL) where the notifications destined for the EAS should be sent to.
DNNODNN for the data session between AC and EAS.
S-NSSAIOS-NSSAI for the data session between AC and EAS.
Requested bandwidth (NOTE 2)OBandwidth 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.
Up
8.6.6.3.3  Session with QoS create response  p. 141
Table 8.6.6.3.3-1 describes the information elements for a Session with QoS create response from the EES to the EAS.
Information element Status Description
Successful responseOIndicates that the Session with QoS create request was successful.
> Context IDMContext identifier corresponding to the information stored for the request in the EES
Failure responseOIndicates that the Session with QoS create request failed.
> CauseOIndicates the cause of Session with QoS create request failure
Up
8.6.6.3.4  Session with QoS update request  p. 142
Table 8.6.6.3.4-1 describes the information elements for a Session with QoS update request from the EAS to the EES.
Information element Status Description
Security credentialsMSecurity credentials of the EAS
Context IDMContext identifier corresponding to the information stored for the request in the EES.
Requested QoS reference (NOTE 1)ORefers to pre-defined QoS information for the data session between AC and EAS (NOTE 2).
List of alternative QoS referencesOA 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 listOA list of associated events to which the EAS subscribes (see clause 6.1.3.18 of TS 23.503).
> Event specific dataOFor usage monitoring: the sponsoring information (sponsor id, ASP id).
For QoS monitoring: Target of monitoring (DL, UL or roundtrip packet delay).
> Frequency of reportingOThe 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)OBandwidth 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).
Up
8.6.6.3.5  Session with QoS update response  p. 142
Table 8.6.6.3.5-1 describes the information elements for a Session with QoS update response from the EES to the EAS.
Information element Status Description
Successful responseOIndicates that the Session with QoS update request was successful.
Failure responseOIndicates that the Session with QoS update request failed.
> CauseOIndicates the cause of Session with QoS update request failure
Up
8.6.6.3.6  Session with QoS revoke request  p. 142
Table 8.6.6.3.6-1 describes the information elements for a Session with QoS revoke request from the EAS to the EES.
Information element Status Description
Security credentialsMSecurity credentials of the EAS
Context IDMContext identifier corresponding to the information stored for the request in the EES
Up
8.6.6.3.7  Session with QoS revoke response  p. 143
Table 8.6.6.3.7-1 describes the information elements for a Session with QoS revoke response from the EES to the EAS.
Information element Status Description
Successful responseOIndicates that the Session with QoS revoke request was successful.
Failure responseOIndicates that the Session with QoS revoke request failed.
> CauseOIndicates the cause of Session with QoS revoke request failure
Up
8.6.6.3.8  Session with QoS event notification  p. 143
Table 8.6.6.3.8-1 describes the information elements for a Session with QoS event notification from the EES to the EAS.
Information element Status Description
Context IDMContext identifier corresponding to the information stored in the EES during the initial session with QoS create request.
Event report (NOTE)MEvent 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
Up

8.6.6.4  APIs  p. 143

8.6.6.4.1  General  p. 143
Table 8.6.6.4.1-1 illustrates the API for Session with QoS.
API Name API Operations Operation Semantics Consumer(s)
Eees_SessionWithQoSCreateRequest/ ResponseEAS
Update
Revoke
NotifySubscribe/ Notify (NOTE)EAS
NOTE:
The Subscribe operation is embedded in the Request operation of the Create and Update API operation.
Up
8.6.6.4.2  Eees_SessionWithQoS_Create operation  p. 143
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. 144
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. 144
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. 144
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. 144

8.6.7.1  General  p. 144

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

Figure 8.6.7.2-1 illustrates the procedure of application traffic influence trigger from EAS.
Reproduction of 3GPP TS 23.558, Fig. 8.6.7.2-1: Application traffic influence trigger from EAS
Figure 8.6.7.2-1: Application traffic influence trigger from EAS
Up
Step 1.
The EAS sends an EAS traffic influence request.
Step 2.
The EES performs an authorization check to verify whether the EAS has the authorization to request application traffic influence.
Step 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 clause 5.6.7.1 of TS 23.501.
Step 4.
The EES sends the EAS traffic influence response.
Up

8.6.7.3  Information flows  p. 145

8.6.7.3.1  General  p. 145
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  p. 145
Information element Status Description
EASIDMIdentifier of the EAS
Security credentialsMSecurity credentials resulting from a successful authorization for the edge computing service.
Target UE Identifier(s)MIndicates the target UE(s) or any UE.
Up
8.6.7.3.3  Application traffic influence trigger from EAS response  p. 145
Information element Status Description
Successful responseOIndicates that the traffic influence request was successful.
Failure responseOIndicates that the traffic influence request has failed.
> CauseOIndicates the cause of failure
Up

8.6.7.4  APIs  p. 146

8.6.7.4.1  General  p. 146
Table 8.6.7.4.1-1 illustrates the APIs for application traffic influence trigger from EAS.
API Name API Operations Operation Semantics Consumer(s)
Eees_TrafficInfluenceEASCreateRequest/ ResponseEAS
Up
8.6.7.4.2  Eees_TrafficInfluenceEAS_Create operation  p. 146
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.

Up   Top   ToC