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

TS 24.549
Network Slice Capability Enablement
Service Enabler Architecture Layer for Verticals (SEAL);
Protocol specification

3GPP‑Page   ETSI‑search   CONTENT↓
V18.1.0 (PDF)  2024/03  … p.
V17.3.0  2023/03  19 p.
Rapporteur:
Dr. Atarius, Roozbeh
Motorola Mobility UK Ltd.

Content for  TS 24.549  Word version:  17.2.0

Here   Top

1  Scope  p. 6

The present document specifies the protocol aspects of the SEAL service for the network slice capability enablement to support re-mapping of a vertical application to different slices over the 3GPP system. The protocol aspects specify the User Equipment (UE) supporting the client functionality of this SEAL service and the network supporting the server functionality of this SEAL service, where the client functionality and server functionality are specified in TS 23.434.
The present document is also applicable to the application server supporting the Vertical Application Layer server (VAL server) functionality for a specific Vertical Application Layer service (VAL service). The specification for the VAL server for a specific VAL service is out of scope of the present document.
Up

2  References  p. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows;".
[2A]
TS 23.502: "Procedures for the 5G System (5GS); Stage 2".
[3]
TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".
[3A]
TS 24.546: "Configuration management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification;".
[4]
TS 24.547: "Identity management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification;".
[5]
OMA OMA-TS-XDM_Group-V1_1_1-20170124-A: "Group XDM Specification".
[6]
RFC 4825:  "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".
[7]
RFC 6750:  "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
[8]
RFC 7231:  "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
[9]
RFC 7252:  "The Constrained Application Protocol (CoAP)".
[10]
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
[11]
RFC 8323:  "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets".
Up

3  Definitions

3.1  Terms  p. 7

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
SEAL network slice capability enablement client:
An entity that provides the client side functionalities corresponding to the SEAL network slice capability enablement service.
SEAL network slice capability enablement server:
An entity that provides the server side functionalities corresponding to the SEAL network slice capability enablement service.
For the purposes of the present document, the following terms and definitions given in TS 23.434 apply:
SEAL client
SEAL server
SEAL service
VAL server
VAL service
VAL user
Vertical
Vertical application
Up

3.2  Abbreviations  p. 7

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5GCN
5G Core Network
AF
Application Function
DNN
Data Network Name
HTTP
Hypertext Transfer Protocol
PCF
Policy Control Function
SEAL
Service Enabler Architecture Layer
SNSCE-C
SEAL Network Slice Capability Enablement Client
SNSCE-S
SEAL Network Slice Capability EnablementServer
S-NSSAI
Single Network Slice Selection Assistance Information
UE
User Equipment
URSP
UE Route Selection Policy
VAL
Vertical Application Layer
XCAP
XML Configuration Access Protocol
XDMC
XML Document Management Client
XDMC
XML Document Management Server
XML
Extensible Markup Language
Up

4  General description  p. 7

The present document enables a SEAL Network Slice Capability Enablement Client (SNSCE-C) and a Vertical Application Layer server (VAL server) that communicate with a SEAL Network Slice Capability Enablement Server (SNSCE-S). The network slice capability enablement is a SEAL service that provides the network slice capability enablement related capabilities to one or more vertical applications.
In a trusted network, the network slice capability enablement can be used to re-map a vertical application to different slices based on the configuration of the SNSCE-S for updating the application traffic. Therefore, the SNSCE-S acts as an Application Function (AF) and influences the UE's URSP rules for the application traffic by providing guidance on the route selection descriptors S-NSSAI and DNN.
Up

5  Functional entities  p. 8

5.1  SEAL network slice capability enablement client (SNSCE-C)  p. 8

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:
  1. shall support the role of XCAP client as specified in IETF RFC 4825;
  2. shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1-20170124-A [5];
  3. 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
  4. shall support procedure in clause 6.2.2.2.
To be compliant with the CoAP procedures in the present document the SNSCE-C:
  1. shall support the role of CoAP client as specified in IETF RFC 7252;
  2. should support CoAP over TCP and Websocket as specified in IETF RFC 8323;
  3. 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
  4. shall support procedure in clause 6.2.2.4.
Up

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

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:
  1. shall support the role of XCAP server as specified in IETF RFC 4825;
  2. shall support the role of XDMS as specified in OMA OMA-TS-XDM_Group-V1_1_1-20170124-A [5];
  3. shall provide the 5GC network a guidance for route selection descriptors to assign new S-NSSAI and DNN;
  4. shall support procedure in clause 6.2.1.1; and
  5. shall support procedure in clause 6.2.2.3.
To be compliant with the CoAP procedures in the present document the SNSCE-S shall:
  1. shall support the role of CoAP client as specified in IETF RFC 7252;
  2. shall support CoAP over TCP and Websocket as specified in IETF RFC 8323;
  3. shall provide the 5GC network a guidance for route selection descriptors to assign new S-NSSAI and DNN;
  4. shall support procedure in clause 6.2.1.2; and
  5. shall support procedure in clause 6.2.2.5.
Up

6  Network slice capability enablement procedures  p. 9

6.1  General  p. 9

The network slice capability enablement procedures is a SEAL service providing capabilities for network slice re-mapping from one VAL service to one or more other VAL services, TS 23.434. The network server entity, providing the functionality for the network slice re-mapping, acts as an AF communicating with 5GCN to provide guidance to update and modify the S-NSSAIs and the DNNs of the route selection descriptors of the URSP rules, TS 24.526, for one or more application traffics per UE.
Up

6.2  On-network procedures  p. 9

6.2.1  General  p. 9

6.2.1.1  Authenticated identity in HTTP request  p. 9

Upon receiving an HTTP POST request from SNSCE-C, the SNSCE-S shall authenticate the identity of the sender of the HTTP POST request is authorized as specified in TS 24.547, and if authentication is successful, the SNSCE-S shall use the identity of the sender of the HTTP POST request as an authenticated identity.

6.2.1.2  Authenticated identity in CoAP request  p. 9

Upon receiving a CoAP request from SNSCE-C, the SNSCE-S shall authenticate the identity of the sender of the CoAP request is authorized as specified in TS 24.547, and if authentication is successful, the SNSCE-S shall use the identity of the sender of the CoAP request as an authenticated identity.

6.2.2  Event triggered network slice adaptation  p. 9

6.2.2.1  General  p. 9

These clauses describes the procedures on the client and server side when a request for network slice configuration is sent by the client to the server. The network slice configuration request may cause a network slice adaptation and sent by the SNSCE-C acting as application client requesting a new or a change in network slice configuration.

6.2.2.2  SNSCE client HTTP procedure  p. 9

In order to request for the network slice adaptation, the SNSCE-C shall send an HTTP PUT request message according to procedures specified in IETF RFC 7231. In the HTTP PUT request message, the SNSCE-C:
  1. shall set the Request-URI to the URI identifying the SNSCE-S according to the pattern"{apiRoot}/­su_nsc/­val-services/­{valServiceId}/­configurations/­{configurationId}", where:
    1. {valServiceId} set to the identity of "VAL service ID" of the VAL application; and
    2. {configurationId} set to the identity of "slice adaptation" configuration,
  2. shall set the "Host" header field to the URI identifying of SNSCE-S and the port information;
  3. shall include an Authorization header field with the "Bearer" authentication scheme set to an access token of the "bearer" token type as specified in IETF RFC 6750;
  4. shall include the parameters for:
    1. VAL UEs of the VAL UE List; and
    2. requested S-NSSAI,
    as specified in Table A.2-1 of Annex A serialized into a JavaScript Object Notation (JSON) structure as specified in IETF RFC 8259; and
  5. may include the parameters for:
    1. requested DNN; and
    2. configuration cause,
    as specified in Table A.2-1 of Annex A serialized into a JavaScript Object Notation (JSON) structure as specified in IETF RFC 8259.
Up

6.2.2.3  SNSCE server HTTP procedure  p. 10

Upon receipt an HTTP PUT request:
  1. with a Request-URI according to "{apiRoot}/­su_nsc/­val-services/­{valServiceId}/­configurations/­{configurationId}" identifying:
    1. "valServiceId" identifying the VAL application; and
    2. "configurationId" identifying the slice adaptation configuration; and
  2. with a body containing:
    1. VAL UE list with one or more VAL UEs;
    2. requested S-NSSAI;
    3. optionally requested DNN; and
    4. optionally configuration cause,
the SNSCE-S shall determine the sender identity as specified in clause 6.2.1.1 to confirm whether the sender is authorized or not. If:
  1. the sender is not an authorized user, the SNSCE-S shall respond with an HTTP 403 (Forbidden) response message and avoid the rest of steps; or
  2. the sender is an authorized user, the SNSCE-S:
    1. shall attempt to update the network S-NSSAI for one or more VAL UEs with the identities listed in the VAL UE list for the VAL service, identified by VAL service ID by using the parameters for requested S-NSSAI, requested DNN and configuration cause from the HTTP PUT request message;
    2. shall send the updated network S-NSSAI and any DNN to the PCF, if the update is successful, TS 23.434; and
    3. shall send an HTTP 200 response message containing the successful status or an error response for the failure status of the requested network slice adaptation to the SNSCE-C.
Up

6.2.2.4  SNSCE client CoAP procedure  p. 10

In order to request for the network slice adaptation, the SNSCE-C shall send a CoAP POST request message. In the CoAP POST request message, the SNSCE-C:
  1. shall set the CoAP URI identifying a network configuration e.g. the network slice adaptation for a given VAL group containing one or more VAL UEs for a given VAL service according to the API URI definition in Annex B.2, by setting:
    1. the "apiRoot" to the SNSCE-S URI;
    2. the "valServiceId" to the value identifying the given VAL service;
    3. the "ConfigId" to the value identifying the network slice adaptation; and
    4. the "configuration" to include:
      1. the VAL group ID of the VAL group containing one or more VAL UEs;
      2. the requested S-NSSAI;
      3. optionally the requested DNN; and
      4. optionally the requested configuration cause;
  2. shall set the "Uri-Host" and "Uri-Port" Options to the URI identifying of SNSCE-S and the port information; and
  3. shall send the request protected with the relevant ACE profile (OSCORE profile or DTLS profile) as described in TS 24.547.
Up

6.2.2.5  SNSCE server CoAP procedure  p. 11

Upon receiving a CoAP PUT request, where the CoAP URI of the request identifies a network slice configuration as the network slice adaptation of one or more VAL UEs for a given VAL service as described in Annex B.2, the SNSCE-S shall determine the identity of the sender as specified in clause 6.2.1.2 to confirm whether the sender is authorized or not. If:
  1. the sender is not an authorized user, the SNSCE-S shall respond with a CoAP 4.03 (Forbidden) response message and avoid the rest of steps; or
  2. the sender is an authorized user, the SNSCE-S:
    1. shall attempt to update the network S-NSSAI for one or more VAL UEs with the identities listed in the VAL UE list for the VAL service, identified by VAL service ID by using the parameters for requested S-NSSAI, requested DNN and configuration cause from the CoAP PUT request message;
    2. shall send the updated network S-NSSAI and any DNN to the PCF, if the update is successful, TS 23.434; and
    3. shall send a CoAP 2.04 (Changed) response message indicating the successful status or an error response for the failure status of the requested network slice adaptation to the SNSCE-C.
Up

6.3  Off-network procedures  p. 11

The off-network procedures are out of scope of the present document in this release of the specification.

A (Normative)  HTTP resource representation and encoding  p. 12

A.1  General  p. 12

The information in this annex provides a description for the HTTP parameters transmitted by the SNSCE-C to the SNSCE-S to trigger a network slice configuration such as the network slice adaptation for one or more VAL UEs within a VAL service.

A.2  Resource representation and APIs for event triggered network slice configuration  p. 12

A.2.1  ETN_Configuration API  p. 12

A.2.1.1  API URI  p. 12

The HTTP URIs used in HTTP requests from SNSCE-C towards the SNSCE-S shall have the Resource URI structure as defined in clause B.2.1.2.2.2 which is {apiRoot}/­su_nsc/­<apiVersion>/­val-services/­{valServiceId}/­configurations/­{ConfigurationId}, where
  1. {valServiceId} is set to the value of the "VAL Service ID" of the VAL application; and
  2. {ConfigurationId} is set to the identity of the configuration.
Up

A.2.1.2  Resources  p. 12

A.2.1.2.1  Overview  p. 12
The Resource URI structure of the ETN_Configuration API is as shown in Figure A.2.1.2.1-1:
Reproduction of 3GPP TS 24.549, Fig. A.2.1.2.1-1: Resource URI structure of the ETN_Configuration API
Figure A.2.1.2.1-1: Resource URI structure of the ETN_Configuration API
Up
Table A.2.1.2.1-1 provides an overview of the resources and applicable HTTP method.
Resource name Resource URI HTTP method Description
Configuration/val-services/­{valServiceId}/­configurations/­{configurationId}PUT (NOTE)Performs configuration.
NOTE:
In this release, the only configuration is the slice adaptation as described in TS 23.434.
Up
A.2.1.2.2  Resource: Configuration  p. 13
A.2.1.2.2.1  Description  p. 13
The Configuration resource allows an SNSCE-C a specific configuration identified by a configuration ID, to send an HTTP request containing:
  1. a list of one or more VAL UEs;
  2. a requested S-NSSAI;
  3. optionally a requested DNN; and
  4. optionally a requested configuration cause,
for a specific VAL service identified by a VAL service ID, toward a SNSCE-S to perform a network triggered slice configuration for the list of one or more VAL UEs for that specific VAL service.
Up
A.2.1.2.2.2  Resource Definition  p. 13
The SNSCE-C uses the parameters shown in Table A.2.1.2.2.2-1 to communicate with the SNSCE-S in order to trigger a network slice configuration for one or more VAL UEs within a VAL service.
Parameter Description
VAL UE ListREQUIRED. Represents a space-separated list of VAL UE Ids within a given VAL service, for which a given network slice configuration trigger applies.
Requested S-NSSAIREQUIRED. The new S-NSSAI which is requested.
Requested DNN OPTIONAL. The new DNN which is requested.
Configuration causeOPTIONAL. Indicates the cause for the configuration.
Up

B (Normative)  CoAP resource representation and encoding  p. 14

B.1  General  p. 14

The information in this Annex provides a description of CoAP resource representation and encoding transmitted by the SNSCE-C to the SNSCE-S to trigger a network configuration i.e. the network slice configuration in this case for one or more VAL UEs within a VAL service.The general rules for resource URI structure, cache usage, error handling and common data types are described in Annex C.1 of TS 24.546.

B.2  Resource representation and APIs for event triggered network slice configuration  p. 14

B.2.1  ETN_Configuration API  p. 14

B.2.1.1  API URI  p. 14

The CoAP URIs used in CoAP requests from SNSCE-C towards the SNSCE-S shall have the Resource URI structure as defined in clause C.1.1 of TS 24.546 with the following clarifications:
  • the <apiName> shall be "su_nsc";
  • the <apiVersion> shall be "v1"; and
  • the <apiSpecificSuffixes> shall be set as described in clause B.2.1.2.
Up

B.2.1.2  Resources  p. 14

B.2.1.2.1  Overview  p. 14
The Resource URI structure of the ETN_Configuration API is as shown in Figure B.2.1.2.1-1:
Reproduction of 3GPP TS 24.549, Fig. B.2.1.2.1-1: Resource URI structure of the ETN_Configuration API
Figure B.2.1.2.1-1: Resource URI structure of the ETN_Configuration API
Up
Table B.2.1.2.1-1 provides an overview of the resources and applicable CoAP method.
Resource name Resource URI CoAP method Description
Configuration/val-services/{valServiceId}/configurations/{configurationId}PUT (NOTE)Performs configuration.
NOTE:
In this release, the only configuration is the slice adaptation as described in TS 23.434.
Up
B.2.1.2.2  Resource: Configuration  p. 15
B.2.1.2.2.1  Description  p. 15
The Configuration resource allows an SNSCE-C a specific configuration identified by a configuration ID, to send a CoAP request containing:
  1. a list of one or more VAL UEs;
  2. a requested S-NSSAI;
  3. optionally a requested DNN; and
  4. optionally a requested configuration cause,
for a specific VAL service identified by a VAL service ID, toward a SNSCE-S to perform a network triggered slice configuration for the list of one or more VAL UEs for that specific VAL service.
Up
B.2.1.2.2.2  Resource Definition  p. 15
Resource URI:
{apiRoot}/su_nsc/<apiVersion>/­val-services/­{valServiceId}/­configurations/­{configurationId}
This resource shall support the resource URI variables defined in the Table B.2.1.2.2.2-1.
Name Data Type Definition
apiRootstringSee clause B.1.1
apiVersionstringSee clause B.2.1.1
valServiceIdstringIdentifier of a VAL service.
configurationIdstringIdentifier of a configuration
Up
B.2.1.2.2.3  Resource Standard Method  p. 15
B.2.1.2.2.3.1  PUT  p. 15
This operation is to update a given configuration for one or more VAL UEs for a given VAL service which is provided by the SNSCE-S.
This method shall support the request data structures specified in Table B.2.1.2.2.3.1-1, the response data structures and response codes specified in Table B.2.1.2.2.3.1-2.
Attribute name Data type P Cardinality Description Applicability
VAL UE ListstringM1..N Represents a space-separated of VAL UE IDs within a given VAL service, for which a given network slice configuration trigger applies. The VAL service is identified by the value "valServiceId" and the network slice configuration is identified by the value "configurationId".
Requested S-NSSAIstringM1The new S-NSSAI which is requested.
Requested DNNstringO1The new DNN which is requested.
configuration causestringO1Indicates the cause for the configuration.
Data type P Cardinality Response Codes (NOTE) Description
n/aM12.04 Changed The configuration of the VAL UEs with VAL UE List within the VAL service identified by the value "valServiceId" and for the network slice configuration identified by the value "configurationId", was successfull.
NOTE:
The mandatory CoAP error status codes for the PUT method listed in Table B.1.3-1 shall also apply.
Up

B.2.1.3  Error Handling  p. 16

General error responses are defined in clause B.2.1.3.

$  Change history  p. 17

Up   Top