name: N9
full_form: Reference point between H-UPF and V-UPF
context: When the UE is registered to different PLMNs over 3GPP access and non-3GPP access, the MA PDU Session is established first over one access as specified in Figure 4.3.2.2.2-1 ("UE-requested PDU Session Establishment for home-routed roaming scenarios") and then over the other access with the following differences and clarifications: - In step 1, the UE provides Request Type as "MA PDU Request" in UL NAS Transport message and its ATSSS Capabilities, as defined in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. The UE indicates to AMF whether it supports non-3GPP access path switching. - In step 2, if the AMF supports MA PDU sessions, then the AMF selects a V-SMF, which supports MA PDU sessions. If the AMF supports non-3GPP access path switching and the UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF may select a V-SMF and H-SMF supporting non-3GPP access path switching. - In step 3, the AMF informs the V-SMF that the request is for a MA PDU Session (i.e. it includes an "MA PDU Request" indication). If the AMF supports non-3GPP access path switching while maintaining two N2 connections for non-3GPP access, the selected SMFs supports non-3GPP path switching and UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF indicates whether the UE supports non-3GPP path switching to the V-SMF. - In step 6, the V-SMF informs the H-SMF that the request is for a MA PDU Session (i.e. it includes an "MA PDU Request" indication). - In step 7, the H-SMF retrieves, via Session Management subscription data, the information whether the MA PDU session is allowed or not. - In step 9, if dynamic PCC is to be used for the MA PDU Session, the H-SMF sends an "MA PDU Request" indication to PCF in the SM Policy Control Create message and the ATSSS Capabilities of the MA PDU session. The H-SMF provides the currently used Access Type(s) and RAT Type(s) for the MA-PDU session to the PCF. The PCF decides whether the MA PDU session is allowed or not based on operator policy and subscription data. - In step 14, the V-SMF indicates support of non-3GPP path switching in the PDU Session Establishment Accept message. - In step 16, the UE receives a PDU Session Establishment Accept message, which indicates to UE that the requested MA PDU session was successfully established. This message includes the ATSSS rules for the MA PDU session, which were derived by H-SMF and may include Measurement Assistance Information. - After the MA PDU Session is successfully established on the first access, the UE shall initiate again the MA PDU Session establishment procedure in Figure 4.3.2.2.2-1 over the other access with the following differences and clarifications: - In step 1, the UE shall send another PDU Session Establishment Request over the other access containing the same PDU Session ID that was provided over the first access. The UE also provides Request Type as "MA PDU Request" in UL NAS Transport message. The UE indicates to the AMF whether it supports non-3GPP access path switching. - In step 2, if the AMF supports non-3GPP access path switching while maintaining two N2 connections for non-3GPP access, the may select a V-SMF that support non-3GPP access path switching. - In step 3, if the AMF supports non-3GPP path switching and the UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF indicates whether the UE supports non-3GPP path switching to the V-SMF. - In step 12, new UL N9 tunnel CN info is allocated by the H-SMF or by the H-UPF. - In step 14, the V-SMF indicates support of non-3GPP path switching in the PDU Session Establishment Accept message. - In step 16, the UE receives another PDU Session Establishment Accept message, which may contain updated ATSSS rules for the MA PDU session. - After step 20, two N9 tunnels between the H-UPF and two different V-UPFs as well as two N3 tunnels between different V-UPF and RAN/AN are established, or two N3 tunnels, one is between V-UPF and RAN/AN over 3GPP access and the other is between H-UPF and RAN/AN over non 3GPP access, as well as one N9 tunnel between H-UPF and V-UPF are established.
description: between H-UPF and V-UPF. The UE is registered to different PLMNs over 3GPP access and non-3GPP access, the MA PDU Session is established first over one access as specified in Figure 4.3.2.2.2-1 ("UE-requested PDU Session Establishment for home-routed roaming scenarios") and then over the other access with the following differences and clarifications: - In step 1, the UE provides Request Type as "MA PDU Request" in UL NAS Transport message and its ATSSS Capabilities, as defined in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. The UE indicates to AMF whether it supports non-3GPP access path switching. - In step 2, if the AMF supports MA PDU sessions, then the AMF selects a V-SMF, which supports MA PDU sessions. If the AMF supports non-3GPP access path switching and the UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF may select a V-SMF and H-SMF supporting non-3GPP access path switching. - In step 3, the AMF informs the V-SMF that the request is for a MA PDU Session (i.e. it includes an "MA PDU Request" indication). If the AMF supports non-3GPP access path switching while maintaining two N2 connections for non-3GPP access, the selected SMFs supports non-3GPP path switching and UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF indicates whether the UE supports non-3GPP path switching to the V-SMF. - In step 6, the V-SMF informs the H-SMF that the request is for a MA PDU Session (i.e. it includes an "MA PDU Request" indication). - In step 7, the H-SMF retrieves, via Session Management subscription data, the information whether the MA PDU session is allowed or not. - In step 9, if dynamic PCC is to be used for the MA PDU Session, the H-SMF sends an "MA PDU Request" indication to PCF in the SM Policy Control Create message and the ATSSS Capabilities of the MA PDU session. The H-SMF provides the currently used Access Type(s) and RAT Type(s) for the MA-PDU session to the PCF. The PCF decides whether the MA PDU session is allowed or not based on operator policy and subscription data. - In step 14, the V-SMF indicates support of non-3GPP path switching in the PDU Session Establishment Accept message. - In step 16, the UE receives another PDU Session Establishment Accept message, which may contain updated ATSSS rules for the MA PDU session. - After step 20, two N9 tunnels between the H-UPF and two different V-UPFs as well as two N3 tunnels between different V-UPF and RAN/AN are established, or two N3 tunnels, one is between V-UPF and RAN/AN over 3GPP access and the other is between H-UPF and RAN/AN over non 3GPP access, as well as one N9 tunnel between H-UPF and V-UPF are established.
explanation: The reference point between H-UPF and V-UPF is a critical component in the establishment of MA PDU sessions. It involves multiple steps, including the UE requesting an MA PDU session, the AMF selecting a V-SMF, and the H-SMF retrieving subscription data to determine if the session is allowed. The reference point also involves the exchange of messages between different network functions, such as the V-SMF informing the H-SMF about the request for an MA PDU session, and the PCF deciding whether the session is allowed based on operator policy and subscription data.
section_title: 4.22.2.2.2 Home-routed Roaming - UE registered to different PLMNs
biotag_Context: O,O,B-Device,O,O,O,O,O,O,B-Organization,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Connection,O,O,B-Connection,B-Protocol,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Technology,B-Connection,O,O,O,B-Network Function,O,O,O,O,O,B-Technology,B-Connection,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,B-Procedure,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Procedure,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Procedure,O,O,B-Service,I-Service,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,B-Technology,B-Connection,O,O,B-Procedure,O,O,O,B-Connection,O,O,O,B-Network Function,O,O,B-Service,O,O,O,O,O,O,B-Procedure,O,O,O,B-Technology,B-Connection,O,O,B-Procedure,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Connection,O,O,O,O,O,O,O,B-Device,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Technology,B-Connection,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Connection,O,B-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Connection,O,O,B-Connection,B-Protocol,O,O,O,B-Device,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,B-Interface,O,B-Network,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,O,O,O,O,B-Interface,O,O,O,O,B-Network Function,O,O,O,B-Organization,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Organization,O,O,O,O,O,B-Interface,O,O,B-Network Function,O,B-Network Function,O,O
biotag_Description: O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,B-Organization,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Connection,O,O,B-Connection,B-Protocol,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Technology,B-Connection,O,O,O,B-Network Function,O,O,O,O,O,B-Technology,B-Connection,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,B-Procedure,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Procedure,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Procedure,O,O,B-Service,I-Service,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,B-Technology,B-Connection,O,O,B-Procedure,O,O,O,B-Connection,O,O,O,B-Network Function,O,O,B-Service,O,O,O,O,O,O,B-Procedure,O,O,O,B-Technology,B-Connection,O,O,B-Procedure,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,O,O,O,O,B-Interface,O,O,O,O,B-Network Function,O,O,O,B-Organization,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Organization,O,O,O,O,O,B-Interface,O,O,B-Network Function,O,B-Network Function,O,O