Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.558  Word version:  19.3.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  9.1 Notification management service  9.1.1 General  9.1.2 Information flows  9.1.3 Procedures  10 Edge service reliability support  10.1 General 
...

 

9  Usage of SEAL services |R18|  p. 288

9.1  Notification management service  p. 288

9.1.1  General  p. 288

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

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  Procedures  p. 289

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

10  Edge service reliability support |R19|  p. 289

10.1  General  p. 289

By adopting the NF set and NF service set approach, as specified in clause 5.21.3 of TS 23.501, edge server set enable edge service producers (e.g. EES/ECS) in the data network to provide reliable services to the edge service consumers (e.g. EAS, EEC).
Equivalent edge servers may be grouped into edge server sets, e.g. several EES instances are grouped into an EES set. Edge servers within an edge server set are interchangeable because they share the same context data, and may be deployed in different locations, e.g. different data centres.
UE is not required to host multiple instances of the same EEC, but the EEC is able to perform ECS/EES re-selection due to ECS/EES service failure.
Up

Up   Top   ToC