Content for &nbsp; TS 23.435 &nbsp; Word version:&nbsp; 19.3.0

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). The request optionally includes the adaptation threshold of network slice adaptation as defined in Table 9.11.3.1-1.

[Optional] NSCE server collects the network slice status information, including network slice performance measurements in clause 5.1.1.1, clause 5.1.1.2, clause 5.1.1.3, in TS 28.552 and key performance indicators in clause 6.3 of TS 28.554, and network slice related E2E latency analytics report in clause 8.4.2.4.3 of TS 28.104 from network slice management functions by utilizing MnS of create MOI operation defined in clause 11.1 and MnS of streaming data reporting service or file data reporting service defined in clause 11.5 and 11.6, TS 28.532.

The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application. If network slice status from step 2 is considered, the NSCE server analyses the network slice status information before triggering the network slice configuration. If the threshold is crossed for the current network slice of adaptation and the objective network slice satisfy the requests, NSCE server triggers the network slice configuration per VAL UE within the VAL Application.

Figure 9.11.2.2-1: Network slice adaptation for VAL application

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.

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.

9.11.2.2 Procedure for VAL UE-triggered and network-based network slice adaptation for VAL application - request and response model p. 77

Figure 9.11.2.2-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.435, Fig. 9.11.2.2-1: Network slice adaptation for VAL application

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, location requirements, time window requirement, access type preference (e.g., 3GPP, non-3GPP or multi access) service operation change, or other application-related parameters.

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). The trigger may also include additional application requirements based on step1, e.g., the requested location criteria, time window.

The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application.

Figure 9.11.2.3-1: Network slice adaptation for VAL application

The NSCE server acting as AF provides the updated S-NSSAI, application requirements 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, application requirements) that can be associated with applications matching the application traffic. 5GC uses this information to update the URSP to the affected UE(s).

Step 5.

The NSCE server sends the response to the NSCE client indicating success or failure.

9.11.2.3 Procedure for VAL server-triggered and network-based network slice adaptation for VAL application - subscribe and notify model p. 78

Figure 9.11.2.3-1 illustrates the VAL server-triggered and network-based procedure with subscribe and notify model 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.435, Fig. 9.11.2.3-1: Network slice adaptation for VAL application

The VAL server sends a network slice adaptation subscribe 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). The request optionally includes the adaptation threshold of network slice adaptation as defined in Table 9.11.3.1-1.

The NSCE server confirms the subscription and returns the network slice adaptation subscribe response.

The NSCE server may interact with the 5GC and OAM to collects the network slice status and performs the network slice adaptation per VAL UE as described in step 2- step 4 in clause 9.11.2.1.

Figure 9.11.2.4-1: Network slice adaptation for VAL application

When the network slice adaptation completes, and the adaption result comes out and available, the NSCE server provides the network slice adaptation notification to the VAL server.

9.11.2.4 Procedure for VAL UE-triggered and network-based network slice adaptation for VAL application - subscribe and notify model p. 79

Figure 9.11.2.4-1 illustrates the VAL UE-triggered and network-based procedure with subscribe and notify modeld 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.435, Fig. 9.11.2.4-1: Network slice adaptation for VAL application

The NSCE client sends a network slice adaptation trigger subscribe request 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). The trigger may also include additional application requirements based on step1, e.g., the requested location criteria, time window.

The NSCE server confirms the subscription and responds with a network slice adaptation trigger subscribe response.