Content for  TS 23.502  Word version:  18.5.0

The procedure is triggered by one of the following events: Step 1a. Step 1b. Step 1c. Step 1d. Step 1e.

(Slice Replacement) As in step 1h of clause 4.3.3.2 with addition:

• When the AMF determines as described in clause 5.15.19 of TS 23.501 that VPLMN S-NSSAI is to be replaced by an Alternative VPLMN S-NSSAI, and/or HPLMN S-NSSAI is to be replaced by an Alternative HPLMN S-NSSAI, the AMF invokes Nsmf_PDUSession_UpdateSMContext (SM context ID, VPLMN S-NSSAI, Alternative VPLMN S-NSSAI, HPLMN S-NSSAI, Alternative HPLMN S-NSSAI) and sends it to the V-SMF. If the AMF determines that the current PDU Session cannot be retained (e.g. the current V-SMF cannot support the Alternative VPLMN S-NSSAI), the AMF includes a release indication.
• If Alternative HPLMN S-NSSAI is received from the AMF, the V-SMF invokes an Nsmf_PDUSession_Update Request (SM context ID, HPLMN S-NSSAI, Alternative HPLMN S-NSSAI) service operation to inform the H-SMF. The H-SMF responds to the request immediately. The V-SMF forwards the release indication if it is received from the AMF.

This step is the same as steps 2 in clause 4.3.3.2 with the SMF is H-SMF.

(UE or serving network requested or HPLMN requested) The H-SMF invokes the service operation to the V-SMF. Based on operator policies and roaming agreements, the V-SMF may decide to fully accept or reject the QoS information provided by the H-SMF. The V-SMF shall also be able to accept a subset of the QoS flows requested to be created or modified within a single H-SMF request i.e. V-SMF can accept some QoS flows and reject other QoS flows in same response to H-SMF. If an Always-on PDU Session Granted indication was provided by the H-SMF to indicate that the PDU Session is to be changed to an always-on PDU Session, the V-SMF decides whether to accept or reject the request from the H-SMF based on local policies. For network slice replacement, based on the information received from the V-SMF, the H-SMF determines whether to retain the PDU Session as described in clause 5.15.19 of TS 23.501. If the H-SMF decides to retain the PDU Session, the H-SMF includes the Alternative HPLMN S-NSSAI and a cause value indicating that the PDU Session is to be retained in the Nsmf_PDUSession_Update Request message. For SSC mode 3 PDU Session if the H-SMF decides to establish a new PDU Session on the Alternative HPLMN S-NSSAI, the H-SMF includes Alternative HPLMN S-NSSAI and a cause value indicating that a new PDU Session re-establishment on the Alternative HPLMN S-NSSAI is required in the Nsmf_PDUSession_Update Request message. For SSC mode 1 and SSC mode 2 PDU session if the H-SMF decides to establish a new PDU Session on the HPLMN Alternative S-NSSAI, the H-SMF initiates release of the PDU Session as described in clause 4.3.4.3.

(HPLMN requested) These steps are executed if new QoS Flow(s) are to be created. The SMF updates the UPF with UL Packet Detection Rules of the new QoS Flow. These steps are executed if the HPLMN S-NSSAI is replaced by an Alternative HPLMN S-NSSAI and the PDU Session is retained. The SMF updates the UPF with Alternative S-NSSAI.

These steps are the same as step 3a-3b in clause 4.3.3.2 but controlled from the V-SMF. The V-SMF uses the information received in step 3 to generate any N1 and/or N2 signalling to be sent towards the UE and/or the (R)AN. For network slice replacement in step 1f, the following applies:

• If the PDU Session is to be retained and only the VPLMN S-NSSAI is to be replaced by an Alternative VPLMN S-NSSAI, the V-SMF includes Alternative VPLMN S-NSSAI in the N1 PDU Session Modification Command message and a cause value to notify the UE that the VPLMN S-NSSAI of the PDU Session is replaced with the Alternative VPLMN S-NSSAI. The V-SMF also set the S-NSSAI in N2 SM information to Alternative VPLMN S-NSSAI.
• If the PDU Session is to be retained and only the HPLMN S-NSSAI is to be replaced by an Alternative HPLMN S-NSSAI, the V-SMF includes Alternative HPLMN S-NSSAI in the N1 PDU Session Modification Command message and a cause value to notify the UE that the HPLMN S-NSSAI is replaced with the Alternative HPLMN S-NSSAI
• If the PDU Session is to be retained and both VPLMN S-NSSAI and HPLMN S-NSSAI are to be replaced, the V-SMF includes Alternative HPLMN S-NSSAI and VPLMN Alternative S-NSSAI in the N1 PDU Session Modification Command message and a cause value to notify the UE that the HPLMN S-NSSAI is replaced with the Alternative HPLMN S-NSSAI and the VPLMN S-NSSAI of the PDU Session is replaced with Alternative VPLMN S-NSSAI. The V-SMF sets the S-NSSAI in N2 SM information to Alternative VPLMN S-NSSAI.
• If a new PDU Session establishment is required, the V-SMF includes Alternative HPLMN S-NSSAI and/or Alternative VPLMN S-NSSAI in the N1 PDU Session Modification Command message and a cause value to notify the UE that a new PDU Session establishment on the HPLMN Alternative S-NSSAI and/or Alternative VPLMN S-NSSAI is required.

These steps are the same as step 4-6 in clause 4.3.3.2.

This step is the same as step 7a in clause 4.3.3.2 with the difference that the SMF is V-SMF. If the N2 SM information indicates modification failure and the V-SMF rejected the PDU session modification as described in step 7 in clause 4.3.3.2, step 9 is skipped.

are the same as step 8a-8b in clause 4.3.3.2 but executed in Visited PLMN

This step is the same as step 7b in clause 4.3.3.2 with the difference that the SMF is V-SMF.

These steps are the same as steps 8-9 in clause 4.3.3.2.

These steps are the same as step 10a-10b in clause 4.3.3.2 but executed in Visited PLMN.

V-SMF responds to the H-SMF with an Nsmf_PDUSession_Update response carrying the information like PCO provided by the UE in the SM PDU Session Modification Command Ack message from the UE to the V-SMF, Secondary RAT usage data. The H-SMF shall modify the PDU Session context. If the V-SMF has rejected QFI(s) (step3) or the (R)AN has rejected QFI(s) in step 6 of Figure 4.3.3.2-1, the H-SMF is responsible of later updating the QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) in the UE.

These steps are the same as steps 12-13 in clause 4.3.3.2 with the difference that the SMF is H-SMF.