Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  18.0.0

Top   Top   Up   Prev   Next
0…   4…   6…   6.4…   6.5…   7…   8…   8.2.2…   9…   9.3…   9.3.6…   9.4…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.4…   11…   11.3…   12…   13…   14…   14.3…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6…   14.4…   15…   A…

 

15  Service-based interface representation of the functional model for SEAL servicesWord‑p. 174

15.1  GeneralWord‑p. 174

The functional models for SEAL services is represented using functional entities and reference points between the functional entities as specified in subclause 6. The vertical applications consume the SEAL services in the form of APIs. Each SEAL service offers these APIs on a service-based interface to all its consumer entities.

15.2  Functional model representationWord‑p. 174

Figure 15.2-1 illustrates the service-based interface representation of the functional model for SEAL services.
Reproduction of 3GPP TS 23.434, Fig. 15.2-1: SEAL generic functional model representation using service-based interfaces
Up
The SEAL function(s) exhibit the service-based interfaces which are used for providing and consuming SEAL services. The service APIs are specified for each SEAL function enabled over the service-based interface. The service-based interfaces of specific SEAL services are specified in this document. All the interactions with SEAL are governed based on the reference point interactions of the functional models specified in subclause 6. VAL function represents the functionalities of the VAL server.
The service APIs offered by the SEAL function(s) are published and discovered on the CAPIF core function as specified in TS 23.222.
Up

15.3  Service-based interfacesWord‑p. 174

Table 15.3-1 specifies the service-based interfaces supported by SEAL.
Service-based interface Application functionEntity Mapping server entity APIs offered
SlmLocation management functionLocation Management ServerSpecified in subclause 9.4
SgmGroup management functionGroup management serverSpecified in subclause 10.4
ScmConfiguration management functionConfiguration management serverSpecified in subclause 11.4
SimIdentity management functionIdentity management serverSpecified in subclause 12.4
SkmKey management functionKey management serverSpecified in subclause 13.4
SnrmNetwork resource management functionNetwork resource management serverSpecified in subclause 14.4
SnsceNetwork slice capability enablement functionNetwork slice capability enablement serverSpecified in subclause 16.4
CccfCAPIF core functionNot applicableSpecified in subclause 10 of TS 23.222
Up

16  Network slice capability enablement |R17|Word‑p. 175

16.1  GeneralWord‑p. 175

The network slice capability enablement is a SEAL service that offers network slice capability enablement capabilities, such as support for vertical application to slice re-mapping (which can be defined as the mapping of the UEs running a vertical application to different slice), to one or more vertical applications. In particular, network slice capability enablement uses a network-based mechanism to apply the slice re-mapping based on the network slice capability enablement server configuration, where the network slice capability enablement server acting as AF influences the URSP rules for the application traffic per UE by providing a guidance on the route selection parameters (including the S-NSSAI and DNN mapping).
Up

16.2  Functional modelWord‑p. 175

16.2.1  GeneralWord‑p. 175

The functional model for the network slice capability enablement is based on the generic functional model specified in clause 6.2. It is organized into functional entities to describe a functional architecture which addresses the support for network slice capability enablement aspects for vertical applications. Since the slicing is a feature which considers the Uu interfaces, only the on-network functional model is specified in this clause.
Up

16.2.2  Functional model descriptionWord‑p. 175

Figure 16.2.2-1 illustrates the generic functional model for network slice capability enablement.
Reproduction of 3GPP TS 23.434, Fig. 16.2.2-1: Functional model for network slice capability enablement
Up
The network slice capability enablement client communicates with the network slice capability enablement server over the NSCE-UU reference point. The network slice capability enablement client provides the support for network slice capability enablement functions to the VAL client(s) over NSCE C reference point. The VAL server(s) communicates with the network slice capability enablement server over the NSCE-S reference point. It is assumed that the network slice capability enablement server is deployed at the 5G system domain. The network slice capability enablement server, acting as AF, may communicate with the 5G Core Network functions via NEF (N33) reference point (for interactions with PCF).
Up

16.2.3  Functional entities descriptionWord‑p. 176

16.2.3.1  GeneralWord‑p. 176

The functional entities for network slice capability enablement SEAL service are described in the following subclauses.

16.2.3.2  Network slice capability enablement serverWord‑p. 176

The network slice capability enablement server functional entity provides the enablement of the network slicing aspects to support the VAL applications. Such enablement supports the mapping or migration of one or more vertical applications to one or more network slices (from a set of network slices, as provided by the 3GPP network system) as described in procedure in clauses 16.3.2.3 and 16.3.2.4. Such adaptation assumes that the UE is subscribed to more than one slice and is done via providing a guidance to update the URSP rules at the 5GS (denoted in clause 16.3.3 as network-based mechanism).
Up

16.2.3.3  Network slice capability enablement clientWord‑p. 176

The network slice capability enablement client functional entity acts as the application client for the slice enablement. The network slice capability enablement client interacts with the network slice capability enablement server to trigger a network slice adaptation due to an application requirement change. This trigger may be due to an application QoS requirement change, a service operation change. The NSCE client may receive a network slice / DNN re-mapping notification from the NSCE server. The NSCE client may optionally notify the VAL client on the network slice / DNN re-mapping.
Up

16.2.4  Reference points descriptionWord‑p. 176

16.2.4.1  GeneralWord‑p. 176

The reference points for the functional model for network slice capability enablement are described in the following subclauses.

16.2.4.2  NSCE-UUWord‑p. 177

The interactions related to network slice capability enablement functions between the network slice capability enablement server and the network slice capability enablement client are supported by NSCE-UU reference point. This reference point utilizes Uu reference point as described in TS 23.501.

16.2.4.3  NSCE-CWord‑p. 177

The interactions related to network slice capability enablement functions between the VAL client(s) and the network slice capability enablement client within a VAL UE are supported by the NSCE-C reference point. The NSCE client may receive an application requirement change over NSCE-C. Further, the NSCE client may provide a notification on the network slice adaptation upon successful adaptation of the slice to application mapping.

16.2.4.4  NSCE-SWord‑p. 177

The interactions related to network slice capability enablement functions between the VAL server(s) and the network slice capability enablement server are supported by the NSCE-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in TS 23.222.

16.2.4.5  N33Word‑p. 177

The reference point N33 supports the interactions between the network slice capability enablement server and the NEF and is specified in TS 23.501. N33 is used for the network-based mechanism for slice re-mapping, where NSCE server acting as AF influences the URSP rules for the application traffic per UE by providing a guidance on the route selection parameters (including the S-NSSAI and DNN mapping), as specified in clause 4.15.6.10 of TS 23.502, clause 6.6.2.2 of TS 23.503, clause 6.2.4 of TS 23.548.
Up

16.3  Procedures and information flows for network slice capability enablementWord‑p. 177

16.3.1  GeneralWord‑p. 177

16.3.2  Network slice adaptation for VAL applicationWord‑p. 177

16.3.2.1  GeneralWord‑p. 177

This subclause describes the procedure for network slice adaptation at the Network Slice Capability Enablement (NSCE) server, based on a request from a VAL server to adapt the network slice for the VAL application. This request is handled between the NSCE server and the NSCE client per each VAL UE of the VAL application.

16.3.2.2  Information flowsWord‑p. 177

16.3.2.2.1  Network slice adaptation requestWord‑p. 177
Table 16.3.2.2.1-1 describes the information flow network slice adaptation request from the VAL server to the NSCE server.
Information Element Status Description
VAL service IDMThe VAL service ID of the VAL application for which the network slice adaptation may corresponds to.
List of VAL UE IDsMList of the VAL UE IDs within the VAL service for which the slice adaptation request corresponds
Network slice adaptation causeOThe cause which necessitates the network slice change (e.g. VAL service profile change, VAL service operation change).
Requested S-NSSAIOIndication of the new S-NSSAI which is requested.
Requested DNNOIndication of the new DNN which is requested.
Up
16.3.2.2.2  Network slice adaptation responseWord‑p. 178
Table 16.3.2.2.2-1 describes the information flow network slice adaptation response from the NSCE server to the VAL server.
Information Element Status Description
ResultMResult includes success or failure of the network slice adaptation with the underlying network.
Up
16.3.2.2.3  Network slice adaptation triggerWord‑p. 178
Table 16.3.2.2.3-1 describes the information flow Network slice adaptation trigger from the NSCE client to the NSCE server.
Information Element Status Description
VAL UE ID(s)MThe VAL UE ID(s) within the VAL service, for which the network slice adaptation trigger applies
VAL service IDMThe VAL service ID of the VAL application for which the network slice configuration may corresponds to.
Requested S-NSSAIMIndication of the new S-NSSAI which is requested.
Requested DNNOIndication of the new DNN which is requested.
Up
16.3.2.2.4  Network slice adaptation notificationWord‑p. 178
Table 16.3.2.2.4-1 describes the information flow network slice adaptation notification from the NSCE server to the NSCE client and optionally to the VAL client.
Information Element Status Description
ResultMResult includes success or failure of the network slice adaptation.
Up

16.3.2.3  Procedure for VAL server-triggered and network-based network slice adaptation for VAL applicationWord‑p. 178

Figure 16.3.2.3-1 illustrates the VAL server-triggered and network-based procedure where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application.
Reproduction of 3GPP TS 23.434, Fig. 16.3.2.3-1: Network slice adaptation for VAL application
Up
Step 1.
The VAL server sends a network slice adaptation request to the NSCE server for the VAL application (and the VAL UEs within the VAL application). This request may be in the form of exact requested network slice (and optionally DNN) for all the VAL UEs of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN).
Step 2.
The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application.
Step 3.
The NSCE server acting as AF provides the updated S-NSSAI and DNN per VAL UE. In particular, NSCE server sends this information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in clause 4.15.6.10 of TS 23.502, clause 6.6.2.2 of TS 23.503, clause 6.2.4 of TS 23.548). This guidance may update the route selection parameters to indicate different sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic.
Step 4.
Upon successful adaptation of the route selection parameters, the NSCE server provides a network slice adaptation response to the VAL server, providing information on the fulfilment of the network slice adaptation request per VAL application.
Up

16.3.2.4  Procedure for VAL UE-triggered and network-based network slice adaptation for VAL applicationWord‑p. 179

Figure 16.3.2.4-1 illustrates the VAL UE-triggered and network-based procedure where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application.
Pre-condition:
  • The NSCE client has connected to the NSCE server;
Reproduction of 3GPP TS 23.434, Fig. 16.3.2.4-1: Network slice adaptation for VAL application
Up
Step 1.
The VAL client provides a new application requirement to the NSCE client, indicating a new service profile for the VAL application. This may be in the form of a change at the application QoS requirements, service operation change, or other application-related parameters.
Step 2.
The NSCE client sends a network slice adaptation trigger to the NSCE server for the VAL application. This trigger may be in the form of exact requested network slice (and optionally DNN) for the VAL UE of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN).
Step 3.
The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application.
Step 4.
The NSCE server acting as AF provides the updated S-NSSAI and DNN per VAL UE. In particular, NSCE server sends this information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in clause 4.15.6.10 of TS 23.502, clause 6.6.2.2 of TS 23.503, clause 6.2.4 of TS 23.548). This guidance may update the route selection parameters to indicate different sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic.
Step 5.
The NSCE server may send a notification to the NSCE client indicating success or failure.
Up

16.4  SEAL APIs for network slice capability enablementWord‑p. 180

16.4.1  GeneralWord‑p. 180

Table 16.4.1-1 illustrates the SEAL APIs for network slice capability enablement.
API Name API Operations Known Consumer(s) Communication Type
SS_NetworkSliceAdaptationNetwork_slice_adaptationVAL serverRequest /Response
Up

16.4.2  SS_NetworkSliceAdaptation APIWord‑p. 181

16.4.2.1  GeneralWord‑p. 181

API description:
This API enables the VAL server to communicate with the network slice capability enablement server for network slice adaptation over NSCE-S.

16.4.2.2  Network_Slice_AdaptationWord‑p. 181

API operation name:
Network_Slice_Adaptation
Description:
Requesting for network slice adaptation.
Known Consumers:
VAL server.
Inputs:
Outputs:
See subclause 16.3.2.3 for the details of usage of this API operation.

Up   Top   ToC