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…

 

9  Usage of SEAL services |R18|p. 272

9.1  Notification management servicep. 272

9.1.1  Generalp. 272

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 flowsp. 272

The following information flows of notification management service of SEAL as specified in TS 23.434 are applicable for the EEL:
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.
Up

9.1.3  Proceduresp. 273

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

Up   Top   ToC