Content for TS 23.558 Word version: 19.0.0
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…
9 Usage of SEAL services
9.1 Notification management service
9.1.1 General
9.1.2 Information flows
9.1.3 Procedures
...
...
9 Usage of SEAL services |R18| p. 267
9.1 Notification management service p. 267
9.1.1 General p. 267
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.
9.1.2 Information flows p. 267
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 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.
9.1.3 Procedures p. 267
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.
