Section: 4.9.2.3.2 The target AMF is not in the PLMN of the N3IWF (i.e. N3IWF in HPLMN)
Content: Figure 4.9.2.3.2-1: Handover of a PDU Session procedure from untrusted non-3GPP access with N3IWF in the HPLMN to 3GPP access (home routed roaming) 1. If the UE is not registered via 3GPP access, the UE shall initiate Registration procedure as defined in clause 4.2.2.2.2. This includes the retrieval of the SMF-IDs corresponding to each of the PDU Sessions. 2. The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified clause 4.3.2.2.2 (PDU Session Establishment for Home Routed Roaming). 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 non-3GPP AN by performing steps 3-12 specified in clause 4.12.7 with the following exceptions: - the H-SMF interfaces the source AMF (in the home PLMN). The H-SMF shall not send the N1 SM Container (PDU Session Release Command) to the UE; - The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed. - Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the H-SMF to the source AMF indicates the PDU Session is moved to different access. The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from to untrusted non-3GPP access to 3GPP access.