Description
N6 is the 3GPP reference point that connects a User Plane Function (UPF) in the 5G Core (5GC) to an external Data Network (DN). In the 5G System architecture, the UPF is the PDU Session anchor for a UE's PDU Session, and N6 is the logical boundary where 3GPP-managed user-plane processing ends and external IP or Ethernet connectivity begins. Although it is called a reference point, N6 is not necessarily a dedicated physical port; it can be realized through virtual network interfaces, VLANs, VXLANs, IP routing domains, or other transport mechanisms selected by the operator. Its main role is to carry user traffic from the 5GC to the Internet, enterprise networks, IMS, edge applications, or private data networks after the UPF has applied session, QoS, routing, and policy functions.
From a functional perspective, N6 is the egress point for user-plane packets that have already been received from the radio access network over N3. The gNB terminates the radio bearer and forwards user data to the selected UPF using GTP-U tunnels. The UPF then performs packet detection, applies forwarding rules, classifies flows, enforces QoS, and finally forwards the packets toward the DN over N6. For IP-type PDU Sessions, N6 typically carries ordinary IP packets. For Ethernet-type PDU Sessions, it can carry Ethernet frames. The UPF may also perform address handling, traffic filtering, and mapping between internal 5G QoS identifiers and external network conditions, although the exact implementation of these functions is operator-specific and not fully standardized by 3GPP.
N6 is controlled indirectly by the SMF through the N4 interface. The SMF selects the UPF, establishes the PDU Session context, and installs packet detection rules, forwarding action rules, and QoS enforcement rules that determine how traffic should be treated before it reaches N6. The DN itself is outside the 3GPP control domain, so N6 acts as a demarcation point for security, charging, lawful intercept, and network slicing isolation. A network slice may have a dedicated UPF and a dedicated N6 connection to a slice-specific DN, or multiple slices may share a UPF with logical separation enforced through routing, firewalling, and traffic steering. This makes N6 important for enterprise connectivity, where a slice can provide a private path to a corporate network while maintaining isolation from public Internet traffic.
In roaming scenarios, N6 appears in both home-routed and local-breakout architectures. In home-routed roaming, the PDU Session is anchored in the HPLMN, and the HPLMN UPF connects to the DN through N6, while the VPLMN transports user traffic to the anchor. In local breakout, the VPLMN UPF may connect directly to a local DN through N6, reducing latency and backhaul load. This flexibility is one reason N6 is a fundamental part of 5G architecture: it allows the operator to place the user-plane anchor close to the service, the user, or the policy enforcement point, depending on the use case.
N6 also supports mobility and session continuity. When a UE moves between cells, gNBs, or access types, the N3 termination point may change, but the PDU Session anchor and its N6 connection to the DN can remain stable. This means applications in the DN continue to see the same IP or Ethernet endpoint as long as the session remains anchored at the same UPF. For edge computing, a UPF may use N6 to connect to a local DN while another UPF uses N6 to a central DN, enabling selective traffic steering. Overall, N6 is the final user-plane interface in the 5GC that determines how mobile traffic reaches external services, and it is central to service delivery, isolation, and flexible UPF placement.
Purpose & Motivation
N6 exists to provide a clear, standardized boundary between the 3GPP user-plane core and external data networks. In earlier mobile architectures, the packet gateway or PGW had a similar role through SGi, but 5G introduced a more service-based and flexible user plane. The 5G Core separates session management from packet forwarding, and the UPF can be instantiated as a virtualized network function. N6 allows operators to place the UPF at different network locations while preserving a consistent reference point to the DN. This is important because 5G services range from public Internet access to ultra-low-latency edge applications, private enterprise networks, and network slices with strict isolation requirements.
The motivation for N6 is also related to network slicing and distributed UPF deployment. A single monolithic gateway is not efficient for all traffic types: some sessions benefit from a central anchor, while others need local breakout near a factory, campus, or mobile edge cloud. N6 gives the architecture a way to express that the UPF can connect to different DNs depending on session policy, slice, DNN, or operator strategy. It also simplifies integration with external networks because the DN side is outside 3GPP control and can be IP, Ethernet, or another transport network. By defining N6 as a reference point rather than a fixed physical interface, 3GPP supports diverse implementations while preserving architectural clarity.
Without a well-defined N6 boundary, operators would struggle to separate mobile user-plane processing from external service networks. Charging, QoS mapping, lawful intercept, firewalling, and slice isolation all need a known demarcation point. N6 provides that demarcation and enables the UPF to act as the anchor for PDU Sessions, making it possible to maintain service continuity while the radio access network changes. It is therefore a foundational interface for delivering 5G connectivity to the wider Internet and to private networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define N6. Each summary describes the whole specification, not only this term.
Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Technology family
Core network interfaces and reference points · Core Network
- N6 counterpart in another generation: SGi
“A Traffic Endpoint can correspond to a GTP-u endpoint, an SGi or an N6 endpoint.” TS 29.244
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 1 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
The N6 reference point between the UPF and a Data Network is defined for the first time in the Rel-15 specification.
- “N6: Reference point between the UPF and a Data Network.” TS 23.501 v15.13.0
Defining Specifications
3GPP specifications that define or reference N6, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |