Content for TS 23.433 Word version: 19.3.0
0…
4…
7…
8…
9.2…
9.2.2.3…
9.2.3…
9.2.4…
9.3…
9.3.2.2…
9.3.3…
9.3.4…
9.4…
9.5…
9.5.3…
9.5.4…
9.6…
9.7…
9.7.3…
9.7.4…
9.8…
9.9…
9.9.3…
9.10…
9.10.3…
9.11…
9.11.3…
9.12…
A…
C
D…
A Deployment models
B Message delivery option: Utilizing MSGin5G
B.1 General
B.2 SEALDD utilizing MSGin5G
...
...
A Deployment models p. 107
The SEALDD service can be deployed as a generic SEAL service and hence the deployment models for SEALDD service utilizes the deployment models specified in clause 8 of TS 23.434. In the context of SEALDD service the following rules apply:
- The SEAL server is the SEALDD server;
- The SEAL-S reference point is the SEALDD-S reference point; and
- The SEAL-E reference point is the SEALDD-E reference point.
B Message delivery option: Utilizing MSGin5G p. 108
B.1 General p. 108
MSGin5G provides a data delivery messaging service in 5GS especially for enabling IoT device communications. It has been specified starting with Rel-17 in TS 23.554. SEALDD is proposed as a generic data delivery enabler layer for all the verticals utilizing SEAL. It is beneficial to deploy one unified data delivery system suitable for all kinds of terminals to reduce the complexity of vertical applications.
B.2 SEALDD utilizing MSGin5G p. 108
MSGin5G functionalities described in TS 23.554 are integrated in SEALDD enabler layer. As shown in Figure B.2-1, MSGin5G client functionality is integrated in SEALDD client, and MSGin5G server functionality is integrated in SEALDD server. SEALDD server and SEALDD client can use MSGin5G functionalities to send SEALDD traffic in MSGin5G message format.
