5 Functional entities

24.5443GPPGroup Management - Service Enabler Architecture Layer for Verticals (SEAL)Protocol specificationRelease 17TS

5.1 SEAL group management client (SGM-C)

The SGM-C is a functional entity that acts as the application client for management of groups.

To be compliant with the HTTP procedures in the present document, a SGM-C:

– shall support the role of XCAP client as specified in IETF RFC 4825 [3];

– shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1 [4];

– shall support the procedure in clause 6.2.2;

– shall support the procedure in clause 6.2.3;

– shall support the procedure in clause 6.2.4;

– shall support the procedure in clause 6.2.5;

– shall support the procedure in clause 6.2.6;

– shall support the procedure in clause 6.2.7; and

– shall support the procedure in clause 6.2.8.

To be compliant with the CoAP procedures in the present document the SGM-C:

– shall support the role of CoAP client as specified in IETF RFC 7252 [15];

– shall support the capability to observe resources as specified in IETF RFC 7641 [17];

– shall support the block-wise transfer as specified in IETF RFC 7959 [16];

– may support the robust block transfer as specified in IETF draft draft-ietf-core-new-block-14 [20];

– should support CoAP over TCP and Websocket as specified in IETF RFC 8323 [18];

– shall support CBOR encoding as specified in IETF RFC 8949 [19];

– shall support the procedures in clause 6.2.2;

– shall support the procedure in clause 6.2.3;

– shall support the procedure in clause 6.2.4;

– shall support the procedure in clause 6.2.5;

– shall support the procedure in clause 6.2.6;

– shall support the procedure in clause 6.2.7; and

– shall support the procedure in clause 6.2.8.

NOTE 1: The security mechanism to be supported for the CoAP procedures is described in 3GPP TS 24.547 [5].

NOTE 2: Support for TCP for the CoAP procedures is required if the client connects over the network which blocks or impedes the use of UDP, e.g. when NATs are present in the communication path.

NOTE 3: The CoAP protocol supports mechanism for reliable message exchange over UDP. Use of TCP can also be beneficial if reliable transport is required for other reasons, e.g. better observability of resources. Usage of CoAP over TCP is an implementation choice.

NOTE 4: Support for the robust block transfer mechanism for the CoAP procedures is beneficial in environments where packet loss is highly asymmetrical and where performance optimization of block transfers is required.

5.2 SEAL group management server (SGM-S)

The SGM-S functional entity provides for management of groups supported within the vertical application layer.

To be compliant with the HTTP procedures in the present document, a SGM-S:

– shall support the role of XCAP server as specified in IETF RFC 4825 [3];

– shall support the role of Group XDMS as specified in OMA OMA-TS-XDM_Group-V1_1_1 [4];

– shall support the procedure in clause 6.2.2;

– shall support the procedure in clause 6.2.3;

– shall support the procedure in clause 6.2.4;

– shall support the procedure in clause 6.2.5;

– shall support the procedure in clause 6.2.6;

– shall support the procedure in clause 6.2.7; and

– shall support the procedure in clause 6.2.8.

To be compliant with the CoAP procedures in the present document the SGM-C:

– shall support the role of CoAP server as specified in IETF RFC 7252 [15];

– shall support the capability to observe resources as specified in IETF RFC 7641 [17];

– shall support the block-wise transfer as specified in IETF RFC 7959 [16];

– shall support the robust block transfer as specified in IETF draft draft-ietf-core-new-block-14 [20];

– shall support CoAP over TCP and Websocket as specified in IETF RFC 8323 [18];

– shall support CBOR encoding as specified in IETF RFC 8949 [19];

– shall support the procedures in clause 6.2.2;

– shall support the procedure in clause 6.2.3;

– shall support the procedure in clause 6.2.4;

– shall support the procedure in clause 6.2.5;

– shall support the procedure in clause 6.2.6;

– shall support the procedure in clause 6.2.7; and

– shall support the procedure in clause 6.2.8.

NOTE: The security mechanism to be supported for the CoAP procedures is described in 3GPP TS 24.547 [5]