Content for TS 29.435 Word version: 18.1.1
1 Scope
2 References
3 Definitions, symbols and abbreviations
3.1 Definitions
3.2 Symbols
3.3 Abbreviations
4 Overview
...
...
1 Scope p. 24
The present document specifies the stage 3 protocol and data model for the Network Slice Capability Exposure (NSCE) Server Services, for enabling the support of Network Slice Capability Exposure (NSCE) Server services for vertical applications. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NSCE Server.
The stage 2 application layer architecture, functional requirements, procedures and information flows necessary for enabling Network Slice Capability Exposure (NSCE) are specified in TS 23.435.
The common protocol and interface aspects for API definition are specified in clause 5.2 of TS 29.122.
2 References p. 25
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 29.122: "T8 reference point for Northbound Application Programming Interfaces (APIs)".
[3]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[4]
OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0 .
[5]
TR 21.900: "Technical Specification Group working methods".
[6]
TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".
[7]
TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
[8]
TS 33.122: "Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs".
[9]
RFC 6749: "The OAuth 2.0 Authorization Framework".
[10]
RFC 9113: "HTTP/2".
[11]
RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[12]
RFC 9457: "Problem Details for HTTP APIs".
[13]
TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[14]
TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".
[15]
TS 29.549: "Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification".
[16]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[17]
TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[18]
TS 29.572: "5G System; Location Management Services; Stage 3".
[19]
TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[20]
TS 29.531: "5G System; Network Slice Selection Services; Stage 3".
[21]
TS 33.501: "Security architecture and procedures for 5G System".
[22]
TS 28.104: "Management and orchestration; Management Data Analytics (MDA)".
[23]
TS 28.552: "Management and orchestration; 5G performance measurements".
[24]
TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[25]
TS 29.558: "Enabling Edge Applications; Application Programming Interface (API) specification; Stage 3".
[26]
TS 29.520: "5G System; Network Data Analytics Services; Stage 3".
3 Definitions, symbols and abbreviations p. 27
3.1 Definitions p. 27
For the purposes of the present document, the terms and definitions 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.
For the purpose of the present document, the terms and definitions specified in clause 3.1 of TS 23.435 and clause 3.1 of TS 29.549 also apply, including the ones referencing other specifications.
3.2 Symbols p. 27
Void
3.3 Abbreviations p. 27
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.
NSCE
Network Slice Capability Enablement
SEAL
Service Enabler Architecture Layer for Verticals
4 Overview p. 28
The Network Slice Capability Enablement (NSCE) Server forms part of the SEAL Enabler Layer defined in TS 23.434 and aims to ensure the efficient use and deployment of network slice capability exposure capabilities to vertical applications. The NSCE Server services expose network slicing capabilities based on the 5GS management system services (e.g., MnS services) and the 5GS network services (e.g., NEF APIs, NWDAF APIs, NSACF APIs).The NCSE Server supports for this purpose, among other functionalities defined in TS 23.435, the following functionalities:
- network slice API configuration and translation management;
- network slice lifecycle management;
- network slice policy management;
- network slice optimization management;
- network slice management service discovery management;
- network slice related performance and analytics monitoring management;
- network slice information collection management;
- network slice predictive modification management;
- multiple network slice coordinated resource optimization management;
- network slice adaptation management;
- network slice related communication services management;
- network slice modification in Inter-PLMN continuity management;
- network slice diagnostics management;
- network slice fault management;
- network slice requirements verification and alignment management;
- network slice information retrieval and delivery management; and
- network slice allocation management.
