Section: 4.9.2.4.2 The UE is roaming and the selected N3IWF is in the home PLMN
Content: Figure 4.9.2.4.2-1: Handover of a PDU Session procedure from 3GPP access to untrusted non-3GPP access with N3IWF in the HPLMN (home routed roaming) 1. If the UE is not registered via untrusted non-3GPP access, the UE shall initiate Registration procedure as defined in clause 4.12.2. This includes the retrieval of the SMF-IDs corresponding to each of the PDU Sessions. 2. The UE performs PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified in clause 4.12.5. In the Nsmf_PDUSession_Create Response the H-SMF shall include all QoS information for the QoS Flow(s) applicable to the PDU Session for the target access so that when sending the PDU Session Establishment Accept, within the N1 SM container and in the N2 SM information, the V-SMF can include all QoS information (e.g. QoS Rule(s) in N1 SM container, QFI(s) and QoS Profile(s) in N2 SM information) for the QoS Flow(s) acceptable according to VPLMN policies. 3. The H-SMF executes the release of resources in source V-SMF, V-UPF, V-AMF and 3GPP AN by performing steps 3a, 5c to 16b specified in clause 4.3.4.3 with the following exceptions: - the H-SMF indicates in the Nsmf_PDUSession_Update Request that the UE shall not be notified. This shall result in the V-SMF not sending the N1 Container (PDU Session Release Command) to the UE; - Nsmf_PDUSession_StatusNotify service operation invoked by H-SMF to V-SMF indicates PDU Session is moved to different access; - Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the V-SMF to the AMF indicates the PDU Session is moved to different access; - The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed. The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to untrusted non-3GPP access.