Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.435  Word version:  19.3.0

Top   Top   Up   Prev   Next
0…   4…   5…   7…   9…   9.4…   9.5…   9.6…   9.7…   9.8…   9.9…   9.10…   9.11…   9.12…   9.13…   9.14…   9.15…   9.16…   9.17…   9.18…   A…

 

5  Business models and relationships for NSCEp. 17

NSCE layer provides value added services to VAL customers, based on consuming 5GS services related to slicing (from OAM, 5GC) and based on interacting with the VAL UE side. The variety of services and the deployment aspects depend on the different assumptions for the slice owner / provider, the slice customer and the SEAL service provider. With respect to NSCE, the NSCE server belongs to the SEAL provider (as stated in clause 5 of TS 23.434) who can be either the MNO itself, or the vertical customer (e.g. factory owner, automaker X) or the edge/cloud provider (e.g. hyperscaler) who provides such platform services related to slice capability exposure to the vertical customer on top of the MNO. Thus, NSCE can play different roles based on the business models. For example, NSCE server can be:
  • deployed by NOP / MNO.
  • deployed by an Edge / Cloud Provider. In this case, it is assumed that the NSCE server is acting as an authorized AF/AS.
  • deployed by a vertical industry, which can be the end slice customer.
From business perspective, the following business model applies. In Figure 5-1, the different interactions among all the involved entities are provided. More specifically, in this model the end user is the consumer of the applications provided by the vertical/ASP and can have app-level service agreement with vertical/ASP(s).
The end user/UE also has a PLMN subscription arrangement with the MNO. The UE used by the end user is allowed to be registered on the MNO's network. MNO (via OAM) can have a slice SLA with the vertical / ASP, which is optional when vertical customer is the NSC. In addition, due to the involvement of a NSCE service provider, additional agreements can be possible between the NSCE server and VAL/ASP layer and the NOP/MNO(s):
  • the enablement service agreement between VAL/ASP layer and the NSCE service provider include the agreement on the value-added services, which in case on NSaaS these are services related to the consumed slice from NOP. So, the end customer (VAL) subscribes to NSCE server for receiving additional services for optimizing the slice utilization. In case that the NSCE server is a NSP towards VAL customer, then such agreement can relate to slice SLA (for the slice provided by the NSCE server). When the NSCE server is part of the vertical, the service agreement between VAL/ASP layer and the NSCE service provider is internal to a single organization.
  • the service agreement between MNO and NSCE service provider is for consuming 5GS services (and being also authorized to provide additional services on top). Such agreement could be also a slice SLA for the scenarios when NSCE server is the NSC of the MNO (in NSaaS model).
Reproduction of 3GPP TS 23.435, Fig. 5-1: Business relationships
Up
In case of shared RAN between operators, one NSCE service provider (slice service provider) can use NSCE to offer slice services using resources of these operators to end customer (VAL) using the shared RAN via one or both operators.
In case of national roaming between operators, one NSCE service provider (slice service provider) can use NSCE to offer slice services using resources of these operators to end customer (VAL).

6  Architectural requirementsp. 18

6.1  General Descriptionp. 18

The following clauses specify the requirements for network slice capability enablement services for application layers.

6.2  General requirementsp. 18

[AR-6.2-1]
The NSCE architecture shall support the NSCE server to communicate with the VAL server with one or more applications.
[AR-6.2-2]
The NSCE architecture shall support the NSCE server to communicate with one or more VAL servers.
[AR-6.2-3]
The NSCE architecture shall support the NSCE server to interact with 3GPP network management system(s) to consume network slice management services provided by MNO(s). The network management system(s) can belong to the same PLMN or different PLMNs on which the NSCE service provider offers its services.
[AR-6.2-4]
The APIs interactions between the vertical application server(s) and NSCE server(s) shall conform to CAPIF as specified in TS 23.222.
[AR-6.2-5]
The NSCE architecture shall support the NSCE server to communicate with one or more other NSCE server(s).
Up

6.3  Network slice Lifecycle management requirementsp. 18

[AR-6.3-1]
The NSCE architecture shall enable lifecycle management capability exposure of network slice by authorized VAL server.
[AR-6.3-2]
The NSCE architecture shall enable lifecycle management capability exposure of network slice communication service to authorized VAL server.
[AR-6.3-3]
The NSCE architecture shall support the interactions with 3GPP network management system to consume network slice lifecycle management service provided by MNO.

6.4  Performance data retrieval requirementp. 18

[AR-6.4-1]
The NSCE architecture shall support the end-to-end network slice performance and analytics monitoring capability exposure to authorized VAL server.

6.5  Network slice adaption requirementp. 18

[AR-6.5-1]
The NSCE architecture shall support the network slice adaption capability exposure to authorized VAL server.
[AR-6.5-2]
The NSCE architecture shall support the network slice adaption capability exposure to authorized NSCE client.

6.6  Network slice configuration and translation requirementp. 18

[AR-6.6-1]
The NSCE architecture shall support the network slice configuration capability exposure to authorized VAL server.
[AR-6.6-2]
The NSCE architecture shall support the network slice translation capability to enable the translation of slice API invocated by VAL server.

6.7  Multiple slices combined management requirementp. 19

[AR-6.7-1]
The NSCE architecture shall support the interactions with OAM or 5GC of 3GPP PLMN to provide multiple slices combined management service of that PLMN.
[AR-6.7-2]
The NSCE architecture shall provide multiple slices combined performance monitoring service of the PLMN and its PNI-NPNs to authorized VAL server.
[AR-6.7-3]
The NSCE architecture shall provide multiple slices coordinated resource optimization service between the PLMN and its PNI-NPNs to authorized VAL server.

6.8  Security requirementsp. 19

[AR-6.8-1]
The NSCE architecture shall provide mechanisms to authorize the usage of network slicing related services by the VAL servers and NSCE clients, conform to CAPIF as specified in TS 23.222.
[AR-6.8-2]
The NSCE architecture shall support mutual authentication and authorization check between clients and servers, servers and servers that interact, conform to CAPIF as specified in TS 23.222.
Up

Up   Top   ToC