5 Functional entities

24.5493GPPNetwork slice capability enablement- Service Enabler Architecture Layer for Verticals (SEAL)Protocol specificationRelease 17Stage 3TS

The SNSCE-C functional entity acts as the application client for managing network slice capabilities.

To be compliant with the HTTP procedures in the present document the SNSCE-C:

a) shall support the role of XCAP client as specified in IETF RFC 4825 [6];

b) shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1-20170124-A [5];

c) shall support route selection descriptors configuration e.g. S-NSSAI and DNN adaptation due to new requirements or change of requirements for one or more application; and

d) shall support procedure in clause 6.2.2.2.

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

a) shall support the role of CoAP client as specified in IETF RFC 7252 [9];

b) should support CoAP over TCP and Websocket as specified in IETF RFC 8323 [11];

c) shall support route selection descriptors configuration e.g. S-NSSAI and DNN adaptation due to new requirements or change of requirements for one or more application; and

d) shall support procedure in clause 6.2.2.4.

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

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.

5.2 SEAL network slice capability enablement server (SNSCE-S)

The SNSCE-S is a functional entity which provides slice capability enablement to administer the network slice for one or more vertical applications.

To be compliant with the HTTP procedures in the present document the SNSCE-S shall:

a) shall support the role of XCAP server as specified in IETF RFC 4825 [6];

b) shall support the role of XDMS as specified in OMA OMA-TS-XDM_Group-V1_1_1-20170124-A [5];

c) shall provide the 5GC network a guidance for route selection descriptors to assign new S-NSSAI and DNN;

d) shall support procedure in clause 6.2.1.1; and

e) shall support procedure in sublcuase 6.2.2.3.

To be compliant with the CoAP procedures in the present document the SNSCE-S shall:

a) shall support the role of CoAP client as specified in IETF RFC 7252 [9];

b) shall support CoAP over TCP and Websocket as specified in IETF RFC 8323 [11];

c) shall provide the 5GC network a guidance for route selection descriptors to assign new S-NSSAI and DNN;

d) shall support procedure in clause 6.2.1.2; and

e) shall support procedure in clause 6.2.2.5.

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