Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

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

V17.0.0 (PDF)2022/03  … p.
Rapporteur:
Mr. Atarius, Roozbeh
Motorola Mobility UK Ltd.

Content for  TS 24.549  Word version:  17.0.0

Here   Top

1  ScopeWord‑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  ReferencesWord‑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;".
[3]
TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".
[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 7231:  "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
[8]
RFC 6750:  "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
[9]
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
[10]
TS 23.502: "Procedures for the 5G System (5GS); Stage 2".
Up

3  Definitions

3.1  TermsWord‑p. 6

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  AbbreviationsWord‑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 descriptionWord‑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 entitiesWord‑p. 8

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

The SNSCE-C functional entity acts as the application client for managing network slice capabilities. To be compliant with the procedures in the present document the SNSCE-C:
  1. shall support the role of XCAP client as specified in RFC 4825;
  2. shall support the role of XDMC as specified in OMA OMA-TS-XDM_Group-V1_1_1-20170124-A [5]; and
  3. shall support S-NSSAI and DNN adaptation due to new requirements or change of requirements for one or more application.
Up

5.2  SEAL network slice capability enablement server (SNSCE-S)Word‑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 procedures in the present document the SNSCE-S shall:
  1. shall support the role of XCAP server as specified in RFC 4825;
  2. shall support the role of XDMS as specified in OMA OMA-TS-XDM_Group-V1_1_1-20170124-A [5]; and
  3. shall provide the 5GC network a guidance for route selection descriptors to assign new S-NSSAI and DNN.
Up

6  Network slice capability enablement proceduresWord‑p. 8

6.1  GeneralWord‑p. 8

The network slice capability enablement procedures is a SEAL service providing capabilities for network slice re-mapping from one VAL application to one or more other VAL applications, 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 proceduresWord‑p. 8

6.2.1  GeneralWord‑p. 8

6.2.1.1  Authenticated identity in HTTP requestWord‑p. 8

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 one or more VAL UEs of the HTTP POST request as authenticated identities.

6.2.2  Event triggered network slice adaptationWord‑p. 9

6.2.2.1  GeneralWord‑p. 9

These clauses describes the procedures on the client and server side when a request for network slice adaptation is sent by the client to the server. The network slice adaptation request may be sent by a VAL server for the adaptation of the network slice to the VAL application. The network slice adaptation request may be sent by the SNSCE-C acting as application client requesting for a new slice enablement.

6.2.2.2  Client procedureWord‑p. 9

In order to request for network slice adaptation, the SNSCE-C shall send an HTTP POST request message according to procedures specified in RFC 7231. In the HTTP POST request message, the SNSCE-C:
  1. shall set the Request-URI to the URI identifying the SNSCE-C appended with VAL service identity and the value "/UE-triggered-slice-adaptation";
  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 RFC 6750;
  4. shall include the parameters for VAL UE list and requested S-NSSAI as specified in Table A.1.2-1 of Annex A serialized into a JavaScript Object Notation (JSON) structure as specified in RFC 8259; and
  5. may include the parameters for requested DNN and slice adaptation cause as specified in Table A.1.2-1 of Annex A serialized into a JavaScript Object Notation (JSON) structure as specified in RFC 8259.
Up

6.2.2.3  Server procedureWord‑p. 9

Upon receipt an HTTP POST request from the SNSCE-C for network slice adaptation, the SNSCE-S shall determine the identity of the sender 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 slice 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 slice adaptation cause from the HTTP POST request message;
    2. shall send the updated network slice and any new DNN to the PCF, if the update is successful, TS 23.434; and
    3. shall send an HTTP 200 response message containing the successful or failure status of the requested network slice adaptation to the SNSCE-C.
Up

6.3  Off-network proceduresWord‑p. 10

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

A (Normative)  Parameters for different operationsWord‑p. 10

A.1  Event triggered network slice adaptationWord‑p. 10

A.1.1  GeneralWord‑p. 10

The information in this annex provides a normative description for the parameters which are used by the SNSCE-C to trigger a network slice adaptation for a VAL application by sending to the SNSCE-S.

A.1.2  Client side parametersWord‑p. 10

The SNSCE-C uses the parameters shown in Table A.1.2-1 to trigger network slice adaptation for a VAL application.
Parameter Description
VAL UE ListREQUIRED. Represents a space-separated list of VAL UE Ids within the VAL service, for which the network slice adaptation trigger applies.
VAL service IDREQUIRED. The VAL service ID of the VAL application
Requested S-NSSAIREQUIRED. The new S-NSSAI which is requested
Requested DNN OPTIONAL. The new DNN which is requested
Slice adaptation causeOPTIONAL. Indicates the cause for the slice adaptation.
Up

$  Change historyWord‑p. 12


Up   Top