The IRI-POI present in the EES is provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.
The POI in the EES shall support the identifier types given in Table 7.14.1-1.
Table 7.14.1-2 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI in the EES.
If the IRI-POI in the EES receives an ActivateTask message and the ListOfServiceTypes parameter contains a ServiceType that is not supported, the IRI-POI in the EES shall reject the task with an appropriate error as described in ETSI TS 103 221-1 [7] clause 6.2.1.2.
One of the target identifiers listed in the paragraph above.
M
DeliveryType
Set to "X2Only".
M
ListOfDIDs
Delivery endpoints for LI_X2 for the IRI-POI in the EES. These delivery endpoints are configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.
The MDF2 listed as the delivery endpoint over LI_X2 for xIRI generated by the EES shall be provisioned over LI_X1 by the LIPF.
The target identities listed in clause 7.14.1.1 shall apply for the provisioning of MDF2.
Table 7.14.1-3 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF2.
One or more of the target identifiers listed in clause 7.14.1.1.
M
DeliveryType
Set to "X2Only". (Ignored by the MDF2).
M
ListOfDIDs
Delivery endpoints of LI_HI2. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.
Details of where to send the IRI for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations authorised by the ListOfDIDs field in the ActivateTask Message.
C
ServiceScoping
Using the format defined in ETSI TS 103 221-1 [7] include the service scoping as applicable to this LIID based on the service scoping listed above the table.
C
When an additional warrant is activated on a target UE and the LIPF uses the same XID for the additional warrant, the MDF2 shall be able to generate and deliver IRI message for each additional warrant without receiving a corresponding xIRI.
The IRI-POI present in the EES shall send the xIRIs over LI_X2 for each of the events listed in clause 7.14.4 of TS 33.127, the details of which are described in the following clauses.
The IRI-POI in the EES shall generate an xIRI containing an EESEECRegistration record when the IRI-POI present in the EES detects that an EEC has registered, updated its registration or deregistered. The IRI-POI present in the EES shall generate the xIRI for the following events:
EES returns Eees_EECRegistration_Request response towards the EEC confirming the registration of the EEC for the target UE to the EES (as defined in clause 5.2.2.2 of TS 24.558).
EES returns Eees_EECRegistration_Update response towards the EEC confirming the update of the registration information of the EEC for the target UE at the EES (as defined in clause 5.2.2.3 of TS 24.558).
EES returns Eees_EECRegistration_Deregister response towards the EEC confirming the deregistration of the EEC for the target UE from a given EES (as defined in clause 5.2.2.4 of TS 24.558).
Types of registration. Possible values are: "Registration", "Registration Update", "Deregistration".
M
eECID
Unique identifier of the EEC.
M
gPSI
GPSI of the target UE, if available.
C
aCProfiles
Profiles of application clients (ACs) for which the EEC provides edge enabling services, if available. See Table 7.14.2-2.
C
eECServiceContSupport
ACR (Application Context Relocation) scenarios supported by the EEC for service continuity if any.
C
expirationTime
Expiration time for the registration. If absent for registration types "Registration" and "Registration Update", registration of EEC never expires.
C
eECContextID
Unique identifier of the EEC context if available.
C
srcEESID
Identifier of the EES providing the EEC context identifier, if available.
C
unfulfilledACProfiles
If requirements indicated in the AC profile(s) cannot be fulfilled for some of the AC profile(s), the EES shall include "unfulfilledAcProfiles" attribute containing the list of ACIDs of such AC Profile(s) and appropriate reasons, if available.
C
failureResponse
Cause information when the registration, registration update or deregistration has failed, if available.
The IRI-POI in the EES shall generate an xIRI containing an EESEASDiscovery record when the IRI-POI present in the EES detects that an EEC has requested a one-time EAS discovery information. The IRI-POI present in the EES shall generate the xIRI for the following events:
EES returns Eees_EASDiscovery_Request response to the EEC containing a one-time EAS discovery information (as defined in clause 5.3.2.2 of TS 24.558).
The IRI-POI in the EES shall generate an xIRI containing an EESEASDiscoverySubscription record when the IRI-POI present in the EES detects that an EEC has requested to subscribe, update subscription and unsubscribe to EAS discovery information reporting. The IRI-POI present in the EES shall generate the xIRI for the following events:
EES returns Eees_EASDiscovery_Subscribe response to the EEC confirming its subscription to EAS discovery information reporting (as defined in clause 5.3.2.3 of TS 24.558).
EES returns Eees_EASDiscovery_UpdateSubscription response to the EEC confirming the update of its subscription at the EES for EAS discovery information reporting (as defined in clause 5.3.2.5 of TS 24.558).
EES returns Eees_EASDiscovery_Unsubscribe response to the EEC confirming the deletion of an existing subscription at the EES to EAS discovery information reporting (as defined in clause 5.3.2.6 of TS 24.558)
Subscription type, i.e. "Subscription", "Subscription Update" or "Unsubscription".
M
eASEventType
Event type for which the EEC shall be notified
M
eASDiscoveryFilter
Set of characteristics to determine required EASs, if available.
C
eASDynamicInfoFilter
List of EAS dynamic information required by the EEC per EAS, if available. See Table 7.14.2-11.
C
eECServiceContSupport
ACR scenarios supported by the EC for service continuity if any.
C
expirationTime
Expiration time for the subscription. If absent for subscription types "Subscription" and "Subscription Update", EAS discovery subscription from EEC never expires.
C
subscriptionId
Subscription identity, if available.
C
failureResponse
Cause information when the discovery request has failed, if available.
The IRI-POI in the EES shall generate an xIRI containing an EESEASDiscoveryNotification record when the IRI-POI present in the EES detects that the EES has notified a previously subscribed EEC on EAS discovery information. The IRI-POI present in the EES shall generate the xIRI for the following events:
EES receives an Eees_EASDiscovery_Notify response from an EEC confirming that the subscribed EEC has received EAS discovey information (as defined in clause 5.3.2.4 of TS 24.558).
The IRI-POI in the EES shall generate an xIRI containing an EESAppContextRelocation record when the IRI-POI present in the EES detects that an EEC has requested ACR (Application Context Relocation) determination.or ACR initiation. The IRI-POI present in the EES shall generate the xIRI for the following events:
EES returns Eees_AppContextRelocation_Determine response to the EEC confirming that EEC has carried out ACR determination (as defined in clause 5.5.2.2 of TS 24.558). EEC requests that the EES evaluates if ACR is needed and subsequently initiate the ACR procedure if required.
EES returns Eees_AppContextRelocation_Initiate response to the EEC confirming that EEC has carried out ACR initiation (as defined in clause 5.5.2.3 of TS 24.558). EEC requests initiation of an ACR procedure.
The IRI-POI in the EES shall generate an xIRI containing an EESACRSubscription record when the IRI-POI present in the EES detects that an EEC has requested to subscribe, update subscription and unsubscribe to ACR events. The IRI-POI present in the EES shall generate the xIRI for the following events:
EES returns Eees_ACREvents_Subscribe response to the EEC confirming its subscription for reporting of ACR information notification (as defined in clause 5.4.2.2 of TS 24.558).
EES returns Eees_ACREvents_UpdateSubscription response to the EEC confirming the update of its subscription for reporting of ACR information notification (as defined in clause 5.4.2.4 of TS 24.558).
EES returns Eees_ACREvents_Unsubscribe response to the EEC confirming the deletion of an existing subscription at the EES to ACR events (as defined in clause 5.4.2.5 of TS 24.558)
Subscription type, i.e. "Subscription", "Subscription Update" or "Unsubscription".
M
expirationTime
Expiration time for the subscription. If absent for subscription types "Subscription" and "Subscription Update", application context relocation subscription from EEC never expires.
C
eASIDs
List of identifier of the EASs, if available.
M
aCIDs
List of identifier of the ACs, if available.
C
eventIDs
Specifies the events for which EEC is subscribing.
M
subscriptionId
Subscription identity, if available
C
failureResponse
Cause information when the discovery request has failed, if available.
The IRI-POI in the EES shall generate an xIRI containing an EESACRNotification record when the IRI-POI present in the EES detects that the EES has notify a previously subscribed EEC on EAS discovery information. The IRI-POI present in the EES shall generate the xIRI for the following events:
EES receives an Eees_ACREvents_Notify response from an EEC confirming that the subscribed EEC has received a notification of the ACR information events from EES (as defined in clause 5.4.2.2 of TS 24.558).
The IRI-POI in the EES shall generate an xIRI containing an EESEECContextRelocation record when the IRI-POI present in the EES detects that the EES has sent or received the EEC context relocation information. The IRI-POI present in the EES shall generate the xIRI for the following events according to its new serving EE (referred to as target EES in TS 24.558 or current serving EES (referred to as source EES in TS 24.558) role:
Target EES (T-EES) receives an Eees_EECContextRelocation_Pull response from a Source EES (S-EES) upon request from the T-EES to S-EES (as defined in clause 5.10.2.2 of TS 29.558).
T-EES sends an Eees_EECContextRelocation_Push response to a S-EES upon request from the S-EES to T-EES (as defined in clause 5.10.2.3 of TS 29.558).
S-EES sends an Eees_EECContextRelocation_Pull response to a T-EES.
S-EES receives an Eees_EECContextRelocation_Push response from a T-EES.
The IRI-POI in the AES shall generate an xIRI containing an EESStartOfInterceptionWithRegisteredEEC record when the IRI-POI present in the EES detects that interception is activated on a UE which EEC has already registered with an EES.
Profiles of application clients (ACs) for which the EEC provides edge enabling services, if available. See Table 7.14.2-2.
C
eECServiceContSupport
ACR scenarios supported by the EEC for service continuity if any.
C
expirationTime
Expiration time for the registration. If absent for registration types "Registration" and "Registration Update", registration of EEC never expires.
C
eECContextID
Unique identifier of the EEC context, if available.
C
srcEESID
Identifier of the EES providing the EEC context identifier, if available.
C
unfulfilledACProfiles
If requirements indicated in the AC profile(s) cannot be fulfilled for some of the AC profile(s), the EES shall include "unfulfilledAcProfiles" attribute containing the list of ACIDs of such AC Profile(s) and appropriate reasons, if available.
C
timeOfRegistration
Time at which the last registration occurred, if available.
When an xIRI is received over LI_X2 from the IRI-POI in the EES, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).
The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the EES event was observed (i.e. the timestamp field of the xIRI).
The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to Table 7.14.2-19.
The threeGPP33128DefinedIRI field (see ETSI TS 102 232-7 [10] clause 15) shall be populated with the BER-encoded IRIPayload.
When an additional warrant is activated on a target UE and the LIPF uses the same XID for the additional warrant, the MDF2 shall be able to generate and deliver the IRI message containing the EESStartOfInterceptionWithRegisteredEEC record to the LEMF associated with the additional warrant without receiving a corresponding xIRI. The payload of the EESStartOfInterceptionWithRegisteredEEC record is specified in Table 7.14.2-18. The MDF2 shall generate and deliver the IRI message containing the EESStartOfInterceptionWithRegistered record for each of the registrations to the LEMF associated with the new warrant.
MDF2 delivers the IRI to the LEMF with GPSI as the target identity if and only if GPSI is present in the xIRI.
