Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 24.549  Word version:  18.2.1

Top   Top   None   None   Next
1…   7…

 

1  Scopep. 9

The present document specifies the protocol aspects of the SEAL service for the network slice capability enablement to support identifying network slices with capabilities for vertical applications in the 3GPP system based on 5GS management system services and 5GS network services. 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 and TS 23.435.
The present document is applicable to the application servers 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  Referencesp. 9

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".
[1A]
TR 21.900: "Technical Specification Group working methods".
[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]  Void.
[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 9110:"HTTP  Semantics".
[8A]
RFC 9111:  "HTTP Caching".
[8B]
RFC 9112:  "HTTP/1.1".
[8C]
RFC 9113:  "HTTP/2".
[9]  Void.
[10]
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
[11]  Void.
[12]
OMA OMA-TS-XDM_Core-V2_1-20120403-A: "XML Document Management (XDM) Specification".
[13]
TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".
[14]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[15]
TS 26.531: "Data Collection and Reporting; General Description and Architecture".
[16]
TS 26.532: "Data Collection and Reporting; Protocols and Formats".
[17]
TS 29.122: "T8 reference point for Northbound Application Programming Interfaces (APIs)".
[18]
TS 29.435: "Service Enabler Architecture Layer for Verticals (SEAL); Network Slice Capability Enablement (NSCE) Server Services; Stage 3".
[19]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[20]
TS 29.549: " Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification".
[21]
TS 33.434: "Service Enabler Architecture Layer for Verticals (SEAL); Security Aspects".
[22]
OpenAPI Specification: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
Up

3  Definitions of terms, symbols and abbreviationsp. 10

3.1  Termsp. 10

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
For the purposes of the present document, the following terms and definitions given in TS 26.532 apply:
Data Collection Client
Data Collection AF
Up

3.2  Abbreviationsp. 11

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
EDN
Edge Data Network
ETN
Event Triggered Network
HTTP
Hypertext Transfer Protocol
KQI
Key Quality Indicator
NSCE
Network Slice Capability Enablement
PCF
Policy Control Function
QoE
Quality of Experience
SEAL
Service Enabler Architecture Layer
SNSCE-C
SEAL Network Slice Capability Enablement Client
SNSCE-S
SEAL Network Slice Capability Enablement Server
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
XDMS
XML Document Management Server
XDMC
XML Document Management Server
XML
Extensible Markup Language
Up

4  General descriptionp. 11

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 entitiesp. 11

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

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 RFC 4825;
  2. shall support the role of XDMC as specified in OMA OMA-TS-XDM_Core-V2_1 [12]; and
  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.
Up

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

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 RFC 4825;
  2. shall support the role of XDMS as specified in OMA OMA-TS-XDM_Core-V2_1 [12]; and
  3. shall provide the 5GC network a guidance for route selection descriptors to assign new S-NSSAI and DNN.
Up

6Void


Up   Top   ToC