Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.558  Word version:  17.4.0

Top   Top   Up   Prev   Next
0…   5…   6…   7…   8…   8.4…   8.5…   8.6…   8.6.3…   8.6.6…   8.7…   8.8…   8.8.3…   8.8.4…   8.9…   A…   B…   C…   D…

 

8.6.3  ACR management eventsp. 88

8.6.3.1  Generalp. 88

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

8.6.3.2.1  Generalp. 89
Void
8.6.3.2.2  Subscribep. 89
Figure 8.6.3.2.2-1 illustrates the subscribe operation between the EAS and the EES for ACR management event notifications.
Copy of original 3GPP image for 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 Identifier 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.
  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.
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 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.
  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 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 to respond to the EAS.
    The EES stores the subscription related to the EAS.
Step 3.
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 4.
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 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. 90
Figure 8.6.3.2.3-1 illustrates the notify operation between the EES and the EAS for continuous ACR management event notifications.
Copy of original 3GPP image for 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 the UE (e.g. receiving User plane path management event notification for the UE from the 3GPP core network).
  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.
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.
Step 3.
If the EAS had included Indication of EAS Acknowledgement within ACR path 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.
Up
8.6.3.2.4  Subscription updatep. 91
Figure 8.6.3.2.4-1 illustrates the subscription update operation between the EAS and the EES for ACR management event notifications.
Copy of original 3GPP image for 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 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 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. 92
Figure 8.6.3.2.5-1 illustrates the unsubscribe operation between the EAS and the EES for ACR management event notifications.
Copy of original 3GPP image for 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. 93

8.6.3.3.1  Generalp. 93
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. 93
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 (i.e. internal group ID or external group ID)
Event ID(s)MEvent ID:
  • user plane path change
  • ACR monitoring
  • ACR facilitation
  • ACT start/stop
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.
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" 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" event.
Up
8.6.3.3.3  ACR management event subscribe responsep. 94
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. 95
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
> 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.
UEID (NOTE 2)OThe identifier of the UE
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" event.
NOTE 2:
This IE shall be present only in case of "ACT start/stop" events.
Up
8.6.3.3.5  ACR management event subscription update requestp. 95
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. 95
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. 96
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. 96
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. 96

8.6.3.4.1  Generalp. 96
Table 8.6.3.4.1-1 illustrates the API for ACR management event.
API Name API Operations Operation Semantics Consumer(s)
Eees_ACRManagementEventSubscribeSubscribe/NotifyEAS
Notify
UpdateSubscription
Unsubscribe
Up
8.6.3.4.2  Eees_ACRManagementEvent_Subscribe operationp. 97
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. 97
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. 97
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. 97
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.

8.6.4  AC information exposure APIp. 97

8.6.4.1  Generalp. 97

AC information exposure enables EASs to obtain information about capabilities of ACs from the EESs. This information may facilitate communications between EASs and ACs, e.g. push notifications. The information shared is subject to access control as well as privacy and security mechanisms.

8.6.4.2  Proceduresp. 97

8.6.4.2.1  Generalp. 97
Void
8.6.4.2.2  Subscribep. 97
Figure 8.6.4.2.2-1 illustrates the AC information subscription procedure between the EAS and the EES.
Pre-conditions:
  1. The EAS is registered with the EES; and
  2. The AC Profiles of the ACs on the UE are available at the EEC on the UE.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.6.4.2.2-1: AC information subscription
Figure 8.6.4.2.2-1: AC information subscription
(⇒ copy of original 3GPP image)
Up
Step 1.
The EAS sends an AC information subscription request to the EES. The request may contain filters to retrieve information about particular ACs e.g. AC profile parameters or parameter ranges to be matched, specific UE Identifiers, location ranges, etc.
Step 2.
Upon receiving the request from the EAS, the EES performs an authorization check to verify whether the EAS has authorization to perform the operation. The EES determines the matching AC information corresponding to the filter provided and composes a result. The EES stores the subscription information for future processing.
Step 3.
The EES sends an AC information subscription response to the EAS with the result composed in step 2.
Up
8.6.4.2.3  Notifyp. 98
Figure 8.6.4.2.3-1 illustrates the AC information notification procedure between the EES and the EAS.
Pre-conditions:
  1. The EAS subscribed for AC information at the EES.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.6.4.2.3-1: AC information notification
Figure 8.6.4.2.3-1: AC information notification
(⇒ copy of original 3GPP image)
Up
Step 1.
The EES is triggered for AC information updates, e.g. it receives an EEC registration request, it determines if it matches the filter provided by the EAS, e.g. if the AC Geographical Service Area is included in the EAS provided Geographical Service Area.
Step 2.
The EES sends an AC information notification to the EAS.
8.6.4.2.4  Subscription updatep. 99
Figure 8.6.4.2.4-1 illustrates the AC information subscription update procedure between the EAS and the EES.
Pre-conditions:
  1. The EAS has subscribed for AC information as described in clause 8.6.4.2.2.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.6.4.2.4-1: AC information subscription update
Up
Step 1.
The EAS sends an AC information subscription update request to the EES. The request may contain updated filters to retrieve information about particular ACs e.g. AC profile parameters or parameter ranges to be matched, specific UE Identifiers, location ranges, etc.
Step 2.
Upon receiving the request from the EAS, the EES performs an authorization check to verify whether the EAS has authorization to perform the operation. If authorized, the EES updates the stored subscription information.
Step 3.
The EES sends an AC information subscription update response to the EAS.
Up
8.6.4.2.5  Unsubscribep. 99
Figure 8.6.4.2.5-1 illustrates the AC information unsubscribe procedure between the EAS and the EES.
Pre-conditions:
  1. The EAS has subscribed for AC information as described in clause 8.6.4.2.2.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.6.4.2.5-1: AC information unsubscribe
Figure 8.6.4.2.5-1: AC information unsubscribe
(⇒ copy of original 3GPP image)
Up
Step 1.
The EAS sends an AC information unsubscribe request to the EES.
Step 2.
Upon receiving the request from the EAS, the EES performs an authorization check to verify whether the EAS has authorization to perform the operation. If authorized, the EES cancels the subscription as requested in step 1.
Step 3.
The EES sends an AC information unsubscribe response to the EAS.

8.6.4.3  Information flowsp. 100

8.6.4.3.1  Generalp. 100
Void
8.6.4.3.2  AC information subscription requestp. 100
Table 8.6.4.3.2-1 describes the information flow for an AC information subscription request from the EAS to the EES.
Information element Status Description
EASIDMThe identifier of the EAS
Security credentialsMSecurity credentials of the EAS
Subscription typeM Choice of "One time" or "Event based" determining the type of processing requested
Notification Target AddressMThe Notification Target Address (e.g. URL) where the notifications destined for the EAS should be sent to.
FiltersO List of characteristics for discovery purposes, as detailed in Table 8.6.4.3.2-2.
Event conditionsOParameters indicating event conditions e.g. number of notifications instances, subscription timeout, etc.
Information element Status Description
ACID(s)OList of identities of AC(s) to be matched
UE ID(s)OList of UE identifiers to be matched
AC Type(s)OList of categories or types of ACs (e.g. V2X) to be matched
ECSP ID(s)OIdentifier(s) for the ECSP associated with the EEC.
Operation ScheduleOEAS operation schedule (e.g. time windows) to be matched
Geographical Service AreaOEAS service area for identifying UEs with matching expected geographical location(s) (e.g. route). This geographic information can express a geographic point, polygon, route, signalling map, or waypoint set.
Topological Service AreaO EAS service area for identifying UEs with matching expected topological location(s). See possible formats in Table 8.2.7-1.
Maximum AC Service KPIs (NOTE)O Maximum value for identifying the ACs to be matched. Both Minimum required AC Service KPIs and Expected AC Service KPIs from the AC Profiles provided during registration (Table 8.4.2.3.2-1) and/or discovery subscription (Table 8.5.3.4-1) need to be lower than this value.
Min AC Service KPIs (NOTE)O Minimum value for identifying the ACs to be matched. Both Minimum required AC Service KPIs and Expected AC Service KPIs from the AC Profiles provided during registration (Table 8.4.2.3.2-1) and/or discovery subscription (Table 8.5.3.4-1) need to be greater than this value.
UE location(s)OList of locations (e.g. routes) of the UE(s) for which the request applies
NOTE:
Maximum and minimum AC Service KPIs values may be provided for any IEs from Table 8.2.3-1.
Up
8.6.4.3.3  AC information subscription responsep. 101
Table 8.6.4.3.3-1 describes the information flow for the AC information subscription response from EAS to the EES.
Information element Status Description
Successful responseOIndicates that the subscription request was successful.
> Subscription IDMSubscription identifier corresponding to the subscription.
Failure responseOIndicates that the subscription request failed.
> CauseOIndicates the cause of subscription request failure
Up
8.6.4.3.4  AC information notificationp. 101
Table 8.6.4.3.4-1 describes the information flow for an AC information notification from the EES to the EAS.
Information element Status Description
Subscription IdentifierMSubscription identifier for which the notification is generated.
List of clientsOList of clients matched based on the given filtering criteria, with elements listed below
>AC Profile(s)M Profiles of ACs as described in Table 8.2.2-1.
>UE ID(s)OUE identifier for the UE hosting the AC
>UE location(s)OUE location for the UE hosting the AC
Up
8.6.4.3.5  AC information subscription update requestp. 102
Table 8.6.4.3.5-1 describes the information flow for an AC information subscription update request from the EAS to the EES.
Information element Status Description
Security credentialsMSecurity credentials of the EAS
Subscription IDMSubscription identifier corresponding to the subscription.
FilterO List of characteristics for discovery purposes, as detailed in Table 8.6.4.3.2-2.
Event conditionsOParameters indicating event conditions e.g. number of notifications instances, subscription timeout, etc.
Up
8.6.4.3.6  AC information subscription update responsep. 102
Table 8.6.4.3.6-1 describes the information flow for the AC information subscription update response from EAS to the EES.
Information element Status Description
Successful responseOIndicates that the subscription update request was successful.
Failure responseOIndicates that the subscription update request failed.
> CauseOIndicates the cause of subscription update request failure
Up
8.6.4.3.7  AC information unsubscribe requestp. 102
Table 8.6.4.3.7-1 describes the information flow for an AC information unsubscribe request from the EAS to the EES.
Information element Status Description
Security credentialsMSecurity credentials of the EAS
Subscription IdentifierMSubscription identifier for the corresponding subscription request.
Up
8.6.4.3.8  AC information unsubscribe responsep. 102
Table 8.6.4.3.8-1 describes the information flow for the AC information unsubscribe response from EAS to the EES.
Information element Status Description
Successful responseOIndicates that the unsubscribe request was successful.
Failure responseOIndicates that the unsubscribe request failed.
> CauseOIndicates the cause of unsubscribe request failure
Up

8.6.4.4  APIsp. 103

8.6.4.4.1  Generalp. 103
Table 8.6.4.4.1-1 illustrates the API for AC information exposure.
API Name API Operations Operation Semantics Consumer(s)
Eees_AppClientInformationSubscribeSubscribe/NotifyEAS
Notify
UpdateSubscription
Unsubscribe
Up
8.6.4.4.2  Eees_AppClientInformation_Subscribe operationp. 103
API operation name:
Eees_AppClientInformation_subscribe
Description:
The consumer subscribes to receive an AC information.
Inputs:
Outputs:
See clause 8.6.4.2.2 for details of usage of this operation.
8.6.4.4.3  Eees_AppClientInformation_Notify operationp. 103
API operation name:
Eees_AppClientInformation_Notify
Description:
The consumer is notified of an event by the EES.
Inputs:
Outputs:
None.
See clause 8.6.4.2.3 for details of usage of this operation.
8.6.4.4.4  Eees_AppClientInformation_UpdateSubscription operationp. 103
API operation name:
Eees_AppClientInformation_UpdateSubscription
Description:
The consumer updates an existing subscription for AC information.
Inputs:
Outputs:
See clause 8.6.4.2.4 for details of usage of this operation.
8.6.4.4.5  Eees_AppClientInformation_Unsubscribe operationp. 103
API operation name:
Eees_AppClientInformation_Unsubscribe
Description:
The consumer unsubscribes for the previously subscribed events.
Inputs:
Outputs:
See clause 8.6.4.2.5 for details of usage of this operation.

8.6.5  UE Identifier APIp. 104

8.6.5.1  Generalp. 104

EES exposes UE Identifier API to the EAS in order to provide an identifier uniquely identifying a UE. This API is used by an EAS to obtain the identifier of the UE if the EAS does not have it. This identifier, called UE ID, is used by the EAS to invoke capability APIs specific to UEs over EDGE-3. The UE ID is specific to the given EAS and it is represented as a GPSI assigned by the 3GPP Core Network.

8.6.5.2  Procedurep. 104

Figure 8.6.5.2-1 illustrates the interactions between the EES and the EAS.
Pre-conditions:
  1. The EAS is authorized to discover and to use UE Identifier API provided by the EES.
Copy of original 3GPP image for 3GPP TS 23.558, Fig. 8.6.5.2-1: UE Identifier API
Figure 8.6.5.2-1: UE Identifier API
(⇒ copy of original 3GPP image)
Up
Step 1.
The EAS invokes UE Identifier API exposed by the EES
Step 2.
The EES uses the received user information in the step 1 (e.g. IP address) and obtains the UE identifier by interacting with NEF as specified in clause 4.15.10 of TS 23.502.
Step 3.
The EES provides the obtained UE identifier as UE ID to the EAS.
Step 4.
The EAS uses the UE ID received in step 3 to invoke capability exposure API(s) provided by the EES over EDGE-3.
Up

8.6.5.3  Information flowsp. 104

8.6.5.3.1  Generalp. 104
The following information flows are specified for UE Identifier API:
  • UE Identifier request and response.
8.6.5.3.2  UE Identifier API requestp. 105
Information element Status Description
User informationMInformation about the User or UE available in the EAS, e.g. IP address.
EAS IDMIdentifier of the EAS providing the application services.
EAS Provider IDOIdentifier of the ASP that provides the EAS.
Security CredentialsMSecurity credentials of the EAS.
Up
8.6.5.3.3  UE Identifier API responsep. 105
Information element Status Description
Successful responseOIndicates that the UE identifier request was successful.
> UE IDMIdentifier uniquely identifying the UE.
Failure responseOIndicates that the UE identifier request failed.
> CauseOIndicates the cause of UE identifier request failure
Up

8.6.5.4  APIsp. 105

8.6.5.4.1  Generalp. 105
Table 8.6.5.4.1-1 illustrates the APIs for UE Identifier.
API Name API Operations Operation Semantics Consumer(s)
Eees_UEIdentifierGetRequest/ResponseEAS
Up
8.6.5.4.2  Eees_UEIdentifier_Get operationp. 105
API operation name:
Eees_UEIdentifier_Get
Description:
The consumer requests identifier of a UE.
Inputs:
Outputs:
See clause 8.6.5.2 for details of usage of this operation.

Up   Top   ToC