name: PGW-U
full_form: Packet Data Network Gateway - User plane
context: Figure 4.3.3.2-1 represents the Roaming architecture with local breakout and Figure 4.3.3.2-2 represents the Roaming architecture with home-routed traffic for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. Figure 4.3.3.2-1: Local breakout roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN NOTE 1: There can be another UPF (not shown in the figure above) between the N3IWF/TNGF and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards the additional UPF, if needed. NOTE 2: S9 interface from EPC is not required since no known deployment exists. NOTE 3: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. Figure 4.3.3.2-2: Home-routed roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN NOTE 4: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN.
description: The Packet Data Network Gateway - User plane (PGW-U) is a network function within the Evolved Packet Core (EPC) architecture that plays a crucial role in managing user plane data for roaming scenarios, particularly in interworking between 5G Core (5GC) via non-3GPP access and EPC/Evolved Universal Terrestrial Radio Access Network (E-UTRAN). It is involved in both local breakout and home-routed traffic architectures.
explanation: PGW-U is classified as a Network Function because it serves as an essential component in handling user plane data for roaming scenarios, aligning with the 3GPP's specifications for efficient network operations. Its role in managing data for interworking between different network architectures highlights its importance as a network function.
section_title: 4.3.3.2 Roaming architecture
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,B-Network Function,O,O,B-Interface,O,O,O,O,O,O,O,O,B-Interface,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,B-Network,I-Network,I-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O