Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.558  Word version:  19.1.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…

 

8.6.3  ACR management eventsp. 118

8.6.3.1  Generalp. 118

The EES exposes ACR management event notifications of one or more UEs to an EAS. EES also uses ACR management event notifications to inform the EAS of the need to start an ACT or cancel a previously started ACT. ACR management event notifications exposed by the EES may rely on the NEF northbound API for monitoring event of user plane path management event.
This capability exposed by the EES supports:
  • "User plane path change". This event supports to detect user plane path change for the application traffic and report the corresponding notification with user plane path change to the EAS.
  • "ACR monitoring". This event supports to detect user plane path change for the application traffic, discover the T-EAS(s), and report the corresponding notification with the discovered T-EAS(s).
  • "ACR facilitation". This event supports to detect user plane path change for the application traffic, make the decision for ACR, discover the T-EAS(s), influence the traffic for the selected T-EAS and report the corresponding notification with the selected T-EAS.
  • "ACT start/stop". This event informs the EAS the need to start or stop an ACT towards or from another EAS for a particular UE. The "ACT start" can also inform the EAS of the ACR parameters.
  • "ACR Selection". This event informs the EAS about the selected ACR scenario list for each AC using the EAS.
The availability of the ACR management event notifications relying on the user plane path management event notification service exposed by 5GC may change due to UE mobility between 5GC and EPC. If an EES exposes ACR event notifications to EAS(s) for a UE by relying on the 3GPP Core Network northbound API for user plane path management notifications, the EES monitors the availability of the northbound API for UE(s) served by the EAS (e.g. by utilizing Nnef_APISupportCapability as described in TS 23.502) and provides the availability information to the EAS accordingly. If CAPIF is supported, the EES determines if the ACR management event API is available and able to be exposed to the EAS for a UE via the Availability of service APIs event notifications provided by the CAPIF core function as defined in TS 23.222.
Up

8.6.3.2  Proceduresp. 119

8.6.3.2.1  Generalp. 119
Void
8.6.3.2.2  Subscribep. 119
Figure 8.6.3.2.2-1 illustrates the subscribe operation between the EAS and the EES for ACR management event notifications.
Reproduction of 3GPP TS 23.558, Fig. 8.6.3.2.2-1: ACR management event API: Subscribe operation
Up
Step 1.
The EAS sends ACR management event subscribe request (e.g. tracking the UE's user plane path change continuously). The EAS shall include UE Identifier or UE Group ID for "user plane path change", "ACR monitoring" and "ACR facilitation" events.
  1. The EAS may include the "user plane path change" event to indicate the EES to notify the EAS when the EES detects there is a user plane path change for the application traffic and the EAS may include Subscription Type (Early and/or Late notification defined in clause 5.6.7 of TS 23.501) and/or Indication of EAS Acknowledgement in the event subscription.
  2. The EAS may include the "ACR monitoring" event to indicate the EES to notify the EAS when the EES detects there is a need for the ACR (e.g. when T-EAS is available at the target DNAI). The EAS may also include the Event Filters to specify the conditions to match for notifying the event, e.g., inter-EDN mobility, intra-EDN mobility.
  3. The EAS may include the "ACR facilitation" event to request the EES to make the decision for ACR, discover the T-EAS(s), influence the traffic for the selected T-EAS and notify the S-EAS of the selected T-EAS. If required, the EAS can add an indication to request service continuity planning.
  4. The EAS may include the "ACT start/stop" event to indicate the EES to notify the EAS of the need for start or stop ACT to or from another EAS for a particular UE. The EES may also use "ACT start" event to notify the EAS of the ACR parameters.
  5. The EAS may include the "ACR Selection" event to indicate the EES to notify the EAS of the selected ACR scenario list applicable to ACs using the EAS.
Step 2.
The EES checks if the EAS is authorized for this operation.
If authorized, and if the subscription in step 1 includes at least one of the "user plane path change", "ACR monitoring" and "ACR facilitation" events, the EES may invoke the PFD management procedure with the 3GPP Core Network as described in TS 23.682 and TS 23.502 with an application id. The traffic filter information sent by the EAS is used in requesting PFD management service. Further the EES provides the same application id for requesting user plane path management event service.
Step 3.
If the subscription in step 1 includes at least one of the "user plane path change", "ACR monitoring" and "ACR facilitation" events, the EES checks if there exists a subscription with the 3GPP core network for the user plane path management event notifications corresponding to the UE information obtained in step 1 as described in TS 23.501 and TS 23.502, which may be triggered by other EAS for the same UE. The EES checks the availability of the user plane path management event service for the UE(s).
  1. if a subscription with 3GPP core network does not exist, then the EES subscribes with the 3GPP core network (PCF, NEF or SCEF+NEF) for the user plane path management event notifications of the UE(s) as described in TS 23.501 and TS 23.502 If the EAS provides Subscription Type and/or Indication of EAS Acknowledgement, the EES include the type of subscription and/or the indication of "AF acknowledgement to be expected" as information on AF subscription to corresponding SMF events within the AF Request;
  2. if a subscription with 3GPP core network exists, then the EES uses the locally cached user plane path management event notification information of the UE(s) to respond to the EAS.
    The EES stores the subscription related to the EAS.
Step 4.
If the event is "user plane path change", the EES may subscribe to UE expected behaviour analytics (UE mobility and UE communication) for the group of UEs as described in TS 23.288.
Step 5.
If EAS is authorized, the EES responds with ACR management event subscribe response. If EAS is not authorized, the EES provides a rejection response with cause information.
If the target UE(s) and the 3GPP network support mobility between 5GC and EPC, the EES monitors the availability of the user plane path management event notification from the 3GPP network by utilizing Nnef_APISupportCapability or Availability of service APIs event notifications provided by the CAPIF core function.
Up
8.6.3.2.3  Notifyp. 120
Figure 8.6.3.2.3-1 illustrates the notify operation between the EES and the EAS for continuous ACR management event notifications.
Reproduction of 3GPP TS 23.558, Fig. 8.6.3.2.3-1: ACR management event API: Notify operation
Up
Step 1.
The EES detects the ACR management event of a UE (e.g. receiving User plane path management event notification for a UE from the 3GPP core network) , or receiving ACR request from the EEC, or when the selected ACR scenario list for a particular AC changes.
  1. If "user plane path change" Event is subscribed, the EES may cache the detected User plane path management event notification locally with timestamp as the latest information of the UE(s) and start the notification aggregation for a group of UEs. The EES decides whether to aggregate and the aggregation period based on the analytics result received from the 3GPP Core Network, local policy and User Plane path management subscription information received from the EAS. The EES determines to notify the user plane path management event notification information (e.g., DNAI) to the EASs which has subscribed for the "user plane path management" event.
  2. If "ACR monitoring" Event is subscribed, based on the detected user plane path change report sent from the 3GPP core network, the EES checks whether the target DNAI is in the EAS profile of the subscribing EAS, if not it further checks whether a T-EAS is available at the target DNAI as described in steps 2-4 of clause 8.8.3.2. If a T-EAS is available, the EES notifies the EAS with T-EAS endpoint; otherwise this event notification will not be sent. Also, when the EES receives the ACR request from the EEC, the EES decides to send the notification to the EAS.
  3. If "ACR facilitation" Event is subscribed, based on the detected user plane path change report sent from the 3GPP core network, the EES checks whether the target DNAI is in the EAS profile of the subscribing EAS, if not it further checks whether a T-EAS is available at the target DNAI as described in steps 2-4 of clause 8.8.3.2. If a T-EAS is available, the EES selects the T-EAS from the discovered EAS list and applies the AF traffic influence with the N6 routing information of the selected T-EAS in the 3GPP Core Network. The EES also notifies the S-EAS with the selected T-EAS endpoint.
  4. If "ACT start/stop" event is subscribed, during the ACR launch if the EEC indicates the need to notify the EAS in the ACR request as described in clause 8.8.3.4, the EES shall send notification to the EAS to inform it about the need to start or stop the ACT to or from another EAS. The EES may include a service continuity planning indication so that the EES will monitor UE location. The notification message includes ACR identity (ACID, UE ID, S-EAS endpoint and T-EAS endpoint).
  5. If "ACR Selection" event is subscribed, the EES shall send notification to the EAS to update the selected ACR scenario list applicable for a particular AC (ACID, UE ID) if an update was received as described in clause 8.15.2.2.
Step 2.
The EES sends ACR management event notification to the EAS. The EES includes the ACR management event notification information of the UE(s) and optionally the timestamp. If the event triggering the notification is DNAI change, the timestamp can be included to indicate the age of the user plane path management event notification information. The EES may only provide part of information included in the user plane path management event notification from 3GPP network (e.g. target DNAI). If the EAS had provided "Indication of EAS acknowledgement", the EES waits for acknowledgement from the EAS before it sends AF acknowledgement to the 3GPP core network.
If the event is "ACT start/stop", the notification shall include the endpoint address of the other EAS and the UE ID. The "ACT start" notification may include ACR parameters as per clause 8.8.3.9. Upon receiving the notification about the start of the ACR execution with "ACT start" event, the S-EAS avoids triggering a second ACR execution for the same identity (ACID, UE ID, S-EAS endpoint and T-EAS endpoint) until the current ACR execution is completed.
If the event is "ACR Selection", the notification shall include the selected ACR scenario list, ACID and UE ID. Upon receiving the notification, the EAS determines if it should perform ACR detection and/or ACR decision for a particular AC (ACID, UE ID).
Step 3.
If the EAS had included Indication of EAS Acknowledgement within ACR management event subscribe request described in clause 8.6.3.2.1, the EAS sends EAS Acknowledgement as a response to ACR management event notification to the EES either immediately or after the required ACT is completed. The EAS may reply in negative, e.g., the EAS may determine not to perform ACR. Then, the EES sends the AF acknowledgement to the 3GPP core network.
If the EAS had included Indication of EAS acknowledgement for service continuity planning within ACR management event subscribe request described in clause 8.6.3.2.1, the EAS sends EAS Acknowledgement as a response to ACR management event notification for service continuity planning of which detailed procedure is described in step 4 of clause 8.8.3.9.
Up
8.6.3.2.4  Subscription updatep. 122
Figure 8.6.3.2.4-1 illustrates the subscription update operation between the EAS and the EES for ACR management event notifications.
Reproduction of 3GPP TS 23.558, Fig. 8.6.3.2.4-1: ACR management event API: Subscription update operation
Up
Step 1.
The EAS sends ACR management event subscription update request to update an existing subscription. The subscription update request may include Event ID, Event Filter, Event Report, Subscription Type (Early and/or Late notification defined in clause 5.6.7 of TS 23.501) and/or Indication of EAS Acknowledgement.
Step 2.
The EES checks if the EAS is authorized for the operation.
If authorized and if the subscription in step 1 includes only "ACT start/stop" event, the EES stores the updated subscription related to the EAS and step 3 is skipped.
If authorized, and if the subscription in step 1 includes at least one of the "user plane path change", "ACR monitoring" and "ACR facilitation" events, the EES checks if there exists a subscription with the 3GPP core network for the user plane path management event notifications corresponding to the updated information obtained in step 1 as described in TS 23.501 and TS 23.502, which may be triggered by other EAS for the same UE.
  1. if a subscription with 3GPP core network does not exist corresponding to the updated information, then the EES subscribes with the 3GPP core network (PCF, NEF or SCEF+NEF) for the user plane path management event notifications of the UE(s) as described in TS 23.501 and TS 23.502 If the EAS provides Subscription Type and/or Indication of EAS Acknowledgement, the EES includes the type of subscription and/or the indication of "AF acknowledgement to be expected" as information on AF subscription to corresponding SMF events within the AF Request;
  2. if a subscription with 3GPP core network exists corresponding to the updated information, then the EES uses the locally cached user plane path management event notification information of the UE(s) to respond to the EAS.
The EES stores the updated subscription related to the EAS.
Step 3.
The EES may update the subscription to the UE expected behaviour analytics.
Step 4.
The EES responds with ACR management event subscription response.
Up
8.6.3.2.5  Unsubscribep. 123
Figure 8.6.3.2.5-1 illustrates the unsubscribe operation between the EAS and the EES for ACR management event notifications.
Reproduction of 3GPP TS 23.558, Fig. 8.6.3.2.5-1: ACR management event API: Unsubscribe operation
Up
Step 1.
The EAS sends ACR management event unsubscribe request to the EES to cancel the ACR management event subscription.
Step 2.
The EES checks if another EAS requires to track the UE's user plane path change or not. If not, the EES unsubscribes the user plane path management event notifications from the 3GPP core network for the corresponding UE.
Step 3.
The EES unsubscribes from the UE expected behaviour analytics, if applicable.
Step 4.
The EES checks if the EAS is authorized for the operation. If authorized, the EES removes the subscription related to the EAS and sends ACR management event unsubscribe response to the EAS.
Up

8.6.3.3  Information flowsp. 124

8.6.3.3.1  Generalp. 124
The following information flows are specified for ACR management event API:
  • ACR management event subscription, notification, subscription update and unsubscribe.
8.6.3.3.2  ACR management event subscribe requestp. 124
Table 8.6.3.3.2-1 describes the information elements for an ACR management event subscribe request from the EAS to the EES.
Information element Status Description
EASIDMThe identifier of the EAS.
Security credentialsMSecurity credentials of the EAS .
UE ID (NOTE 1)OThe identifier of the UE (i.e. GPSI or identity token).
UE Group ID (NOTE 1)OIdentifies a group of UEs as defined in clause 7.2.7.
Event ID(s)MEvent ID:
  • user plane path change
  • ACR monitoring
  • ACR facilitation
  • ACT start/stop
  • ACR selection
Indication of service continuity planning (NOTE 3)OIndicates that whether the service continuity planning is required i.e. whether EES shall monitor UE entering the predicted location.
Traffic filter informationO The traffic filter information includes IP flow description, domain description (domain name, applicable protocol and matching criteria) or URI.
Applicable for the "user plane path change" event, the "ACR monitoring" event and "ACR facilitation" event.
Event Report (NOTE 2)OEvent Reporting Information as specified in TS 23.502
Notification Target AddressMNotification Target Address of the EAS where the notification is to be sent by the EES
Type of subscriptionO Indicates Early and/or Late notification to inform if the notification needs to be received before and/or after UP path configuration. Applicable for the "user plane path change" event.
Indication of EAS acknowledgementO This IE indicates the EES to include indication of "AF acknowledgement to be expected" within the AF request for subscribing UP path management events to 3GPP network and that the EAS will provide an acknowledgement as a response for the notifications of UP path management events to the EES. Applicable for the "user plane path change" event.
Indication of EAS acknowledgement for service continuity planningOThis IE indicates that the EAS will provide an acknowledgement as a response to the notification of ACR management notification related to service continuity planning.
Event FilterOEvent filter as specified in TS 23.501
EAS characteristics for ACRO Set of characteristics to determine required EAS as detailed in Table 8.5.3.2-2.
Applicable for the "ACR monitoring" event and "ACR facilitation" event.
NOTE 1:
Either UE ID or UE Group ID shall be provided if the Event ID(s) includes any of the "user plane path change", "ACR monitoring" and "ACR facilitation" events. UE ID or UE Group ID are not applicable to "ACT start/stop" and "ACR selection" event.
NOTE 2:
This IE shall be present if the Event ID(s) includes any of the "user plane path change", "ACR monitoring" and "ACR facilitation" events. This IE is not applicable to "ACT start/stop" and "ACR selection" event.
NOTE 3:
This IE is applicable for "ACR monitoring", "ACR facilitation".
Up
8.6.3.3.3  ACR management event subscribe responsep. 125
Table 8.6.3.3.3-1 describes the information elements for an ACR management event subscribe response from the EES to the EAS.
Information element Status Description
Successful response (NOTE)OIndicates that the subscription request was successful.
> Subscription IDMSubscription identifier corresponding to the subscription.
> Expiration timeOIndicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time.
If the Expiration time IE is not included, it indicates that the subscription never expires.
Failure response (NOTE)OIndicates that the subscription request failed.
> CauseOIndicates the cause of subscription request failure
NOTE:
One of these IEs shall be present in the message.
Up
8.6.3.3.4  ACR management event notificationp. 126
Table 8.6.3.3.4-1 describes the information elements for an ACR management event notification from the EES to the EAS.
Information element Status Description
Subscription IDMSubscription identifier corresponding to the subscription stored in the EES for the request
List of event notificationsMA list of event notifications for one or more UEs.
> Event IDMThe event ID for which the notification is triggered:
  • user plane path change
  • ACR monitoring
  • ACR facilitation
  • ACT start/stop
  • ACR Selection
> Event report (NOTE 1)OEvent reporting information as specified in clause 5.2.8.3.1 of TS 23.502
> TimestampOThe timestamp of each event report.
> EAS endpointO The T-EAS endpoint shall be included for the "ACR monitoring" event and "ACR facilitation" event.
In case of "ACT start/stop" event, the endpoint address of the EAS to or from which the ACT is needed to start/stop.
> Indication of service continuity planningOIndicating EES will monitor UE entering the predicted location.
> Selected ACR scenario list (NOTE 2)OThe list of ACR scenarios.
> EAS bundle list (NOTE 2)OThe EAS bundle list.
>> EAS ID (NOTE 4)MEAS ID in a bundle.
>> DNAIs and service area of the EASOc For the EAS ID in a bundle, it includes the DNAIs and/or service area, as described in "EAS Geographical Service Area" IE, "EAS Topological Service Area" IE and "List of EAS DNAI(s)" IE of Table 8.2.4-1.
> ACR parameters (NOTE 3)OACR parameters.
>> Prediction expiration timeOThe estimated time the UE may reach the Predicted/Expected UE location or EAS service area at the latest.
UEIDOThe identifier of the UE.
ACIDOThe identifier of the AC.
NOTE 1:
This IE shall be present if the Event ID(s) includes any of the "user plane path change", "ACR monitoring" and "ACR facilitation" events. This IE is not applicable to "ACT start/stop" and "ACR Selection" events.
NOTE 2:
This IE shall be present only in case of "ACR Selection" event.
NOTE 3:
This IE is applicable only when the ACT start event notification is used to send ACR parameters to the T-EAS as per clause 8.8.3.9.
NOTE 4:
Main EAS ID in a bundle does not need to be included.
Up
8.6.3.3.5  ACR management event subscription update requestp. 127
Table 8.6.3.3.5-1 describes the information elements for an ACR management event subscribe request from the EAS to the EES.
Information element Status Description
Security credentialsMSecurity credentials of the EAS
Subscription IDMThe identifier of the subscription to be updated.
Event ID(s) (NOTE)OEvent ID(s) as specified in TS 23.501
Event Report (NOTE)OEvent Reporting Information as specified in TS 23.502
Type of subscription (NOTE)OIndicates Early and/or Late notification to inform if the notification needs to be received before and/or after UP path configuration.
Indication of EAS acknowledgement (NOTE)O This IE indicates the EES to include indication of "AF acknowledgement to be expected" within the AF request for subscribing UP path management events to 3GPP network and that the EAS will provide an acknowledgement as a response for the notifications of UP path management events to the EES.
Event Filter (NOTE)OEvent filter as specified in TS 23.501
EAS characteristics for ACR (NOTE)O Set of characteristics to determine required EAS as detailed in Table 8.5.3.2-2.
Applicable for the "ACR monitoring" event and "ACR facilitation" event.
NOTE 1:
At least one of these IEs shall be present in the message.
Up
8.6.3.3.6  ACR management event subscription update responsep. 128
Table 8.6.3.3.6-1 describes the information elements for an ACR management event subscription update response from the EES to the EAS.
Information element Status Description
Successful response (NOTE 2)OIndicates that the subscription update request was successful.
> Expiration time (NOTE 1)OIndicates the expiration time of the updated subscription. To maintain an active subscription, a subscription update is required before the expiration time.
Failure response (NOTE 2)OIndicates that the subscription update request failed.
> CauseOIndicates the cause of subscription update request failure
NOTE 1:
If the Expiry time IE is not included, it indicates that the subscription never expires.
NOTE 2:
One of these IEs shall be present in the message.
Up
8.6.3.3.7  ACR management event unsubscribe requestp. 128
Table 8.6.3.3.7-1 describes the information elements for an ACR management event unsubscribe request from the EAS to the EES.
Information element Status Description
Security credentialsMSecurity credentials of the EAS
Subscription IDMSubscription identifier corresponding to the subscription stored in the EES for the request
Up
8.6.3.3.8  ACR management event unsubscribe responsep. 128
Table 8.6.3.3.8-1 describes the information elements for an ACR management event unsubscribe response from the EES to the EAS.
Information element Status Description
Successful response (NOTE)OIndicates that the unsubscribe request was successful.
Failure response (NOTE)OIndicates that the unsubscribe request failed.
> CauseOIndicates the cause of unsubscribe request failure
NOTE:
One of these IEs shall be present in the message.
Up

8.6.3.4  APIsp. 129

8.6.3.4.1  Generalp. 129
Table 8.6.3.4.1-1 illustrates the API for ACR management event.
API Name API Operations Operation Semantics Consumer(s)
Eees_ACRManagementEvent SubscribeSubscribe/ NotifyEAS
Notify
UpdateSubscription
Unsubscribe
Up
8.6.3.4.2  Eees_ACRManagementEvent_Subscribe operationp. 129
API operation name:
Eees_ACRManagementEvent_subscribe
Description:
The consumer subscribes to receive an ACR management event.
Inputs:
Outputs:
See clause 8.6.3.2.2 for details of usage of this operation.
8.6.3.4.3  Eees_ACRManagementEvent_Notify operationp. 129
API operation name:
Eees_ACRManagementEvent_Notify
Description:
The consumer is notified of an event by the EES.
Inputs:
Outputs:
None.
See clause 8.6.3.2.3 for details of usage of this operation.
8.6.3.4.4  Eees_ACRManagementEvent_UpdateSubscription operationp. 129
API operation name:
Eees_ACRManagementEvent_UpdateSubscription
Description:
The consumer updates an existing subscription for an ACR management event.
Inputs:
Outputs:
See clause 8.6.3.2.4 for details of usage of this operation.
8.6.3.4.5  Eees_ACRManagementEvent_Unsubscribe operationp. 130
API operation name:
Eees_ACRManagementEvent_Unsubscribe
Description:
The consumer unsubscribes for the previously subscribed events.
Inputs:
Outputs:
See clause 8.6.3.2.5 for details of usage of this operation.

Up   Top   ToC