The notification management is a SEAL service that offers the notification functionality. This service enables EEC to subscribe and receive notifications from the EES and ECS, and thereby offloading the complexity of delivery and reception of notifications to the edge enabler layer.

The following information flows of notification management service of SEAL as specified in TS 23.434 are applicable for the EEL:

• Create notification channel request specified in clause 17.3.2.1 of TS 23.434;
• Create notification channel response specified in clause 17.3.2.2 of TS 23.434;
• Open notification channel specified in clause 17.3.2.3 of TS 23.434;
• Notification message specified in clause 17.3.2.4 of TS 23.434.

The usage of the above information flows are clarified as below:

• The Callback URL is the address (e.g. Notification Target Address) where the notifications destined for the EEC;
• VAL Application ID is EECID;
• VAL Service ID is ECS ID or EES ID;
• VAL client is the EEC;
• VAL server is the EES or ECS.

The following procedures of notification management service of SEAL as specified in TS 23.434 are applicable for the edge enabler layer:

• Procedure for creating notification channel to receive notifications, specified in clause 17.3.3 of TS 23.434.

This procedure is applicable for EDN deployment with gNB on satellite. A satellite EDN may be deployed as described in Annex A.2.5. The service provisioning procedure for satellite EDN is same as clause 8.3.3.2.2 and clause 8.3.3.2.3 with the following clarifications. When UE connects to the satellite, the service provisioning request message contains the UE serving Satellite ID (i.e., serving gNB corresponding Satellite ID). If the service provisioning request message contains the UE serving Satellite ID, then the ECS determines the EES where the Satellite ID in the EES profile matches the UE serving Satellite ID. When UE connects to the satellite, and the service provisioning request message does not contain the UE serving Satellite ID, then service provisioning response message contains the list of EES along with the EES Satellite ID, and then the EEC determine EES where the Satellite ID in the EES profile matches the UE serving Satellite ID.

This procedure is applicable for EDN deployment with gNB on satellite. A satellite EDN may be deployed as described in Annex A.2.5. The service provisioning procedure for satellite EDN is same as clause 8.3.3.2.2 and clause 8.3.3.2.3 with the following clarifications.When EEC sends the service request message to the ECS and the request message contains the UE location, predicted/expected UE location, Prediction expiration time, then the ECS determines a list of EES where the Satellite coverage availability information in EES profile matches the UE location, predicted/expected UE location, Prediction expiration time, and EES Satellite coverage availability information. Alternatively, the ECS may query external server with the UE current location and UE predicted/expected location to obtain a list of Satellite IDs and Trajectory IDs corresponding the UE location and the UE trajectory, then the ECS determines list of EES based on the Satellite IDs and Trajectory IDs in EES profiles by matching with the Satellite IDs and Trajectory IDs obtained from external server for the UE. The "Expected AC Geographical Service Area" in the AC profile, as specified in clause 8.2.2, is used by the ECS to request the external server (managed by the satellite service provider or operator) for such satellite IDs and trajectory IDs. When ECS sends the service provisioning response which contains a list of EES information which EES is deployed on MEO or LEO satellites, the EEC determines the EES determine EES where the Satellite ID in the EES profile matches the UE serving Satellite ID. In addition, when a serving satellite is providing EES and EAS, and due to discontinuous coverage the same satellite comes back for serving, then the EEC connects to same EES and EAS (i.e. to which the EEC had previously connected to), without needing to discover EES and EAS endpoints again.