Description
N3 is the user-plane reference point between the (R)AN and the UPF in the 5G system architecture. The (R)AN term covers gNBs in 5G New Radio and ng-eNBs connected to the 5G core. The UPF is the packet forwarding function that connects the 5G core to external data networks. N3 carries user-plane PDUs for one or more PDU sessions after the AMF and SMF have established the session context. In practice, N3 is the interface that makes the radio access network and the core user plane work together as a single packet path for each subscriber session.
The interface is primarily implemented with GTP-U over IP transport. Each N3 tunnel endpoint is identified by a TEID, which allows the UPF and the (R)AN to distinguish packets belonging to different PDU sessions and different QoS flows. The (R)AN maps QoS flows to data radio bearers, while the UPF maps QoS flows to packet detection and forwarding rules. GTP-U extension headers and QFI marking can be used to preserve the 5G QoS model across the N3 path. N3 is separate from N2, which carries control-plane signaling between the AMF and the (R)AN, and from N4, which carries SMF-UPF control signaling. This separation allows user data to be forwarded at high speed while control decisions are made in the core.
N3 is also central to 5G user-plane topology. A PDU session may terminate at a PSA UPF that provides the external IP anchor. In some deployments, the (R)AN connects to an intermediate UPF over N3, and the intermediate UPF connects to the PSA UPF over N9. This supports traffic steering, local breakout, edge computing, and user-plane optimization. The SMF selects the appropriate UPF and configures it over N4, while the (R)AN uses N3 to send and receive the actual user packets. As a result, N3 can be part of a simple direct path or a more complex multi-UPF chain depending on the service and location.
During mobility, N3 plays a key role in maintaining PDU session continuity. When a UE moves between cells, the (R)AN may keep the same N3 tunnel if the serving UPF remains unchanged. When the UE moves between gNBs or between 5G and E-UTRAN with an ng-eNB, the N3 endpoint may be updated so that the UPF can forward packets to the new radio node. During handover, the core may coordinate tunnel changes through N2 and N4, while N3 carries the resulting user-plane traffic. This design helps preserve active sessions even as the radio access point changes, which is essential for voice, video, and always-on data services.
From an operational perspective, N3 must support high throughput, low latency, and reliable tunneling. The interface is usually protected by network-level security rather than by UE-level security, because it connects trusted operator nodes. Transport isolation, IPsec, access control lists, and monitoring are commonly used to protect N3 traffic. The interface also supports QoS differentiation, packet loss measurement, and traffic reporting, which are important for charging, analytics, and service-level agreements. In summary, N3 is the fundamental user-plane bridge between 5G radio access and the 5G core packet forwarding layer.
Purpose & Motivation
N3 exists to provide a clean separation between radio access and core packet forwarding in the 5G architecture. In earlier generations, user-plane interfaces were often tied to specific node types and control-plane assumptions, which made flexible deployment harder. 5G required a core network that could be distributed, scaled independently, and connected to many access technologies. N3 solves this by defining a standardized user-plane path between any compliant (R)AN and any compliant UPF, regardless of whether the UPF is centralized, regional, or placed near the edge.
The motivation is also driven by the 5G QoS model and service diversity. 5G must support enhanced mobile broadband, ultra-reliable low-latency communication, massive IoT, and network slicing. These services need predictable packet handling between the radio and the core, while control-plane functions remain in the AMF and SMF. N3 allows user packets to be carried with QoS flow information and tunnel identifiers without mixing control signaling into the data path. This makes it easier to scale user-plane capacity independently from control-plane capacity.
N3 also supports modern deployment patterns such as local breakout and edge computing. If the UPF can be selected close to the user or application, N3 becomes the access-side tunnel that connects the radio node to that local core forwarding point. This reduces backhaul latency and enables traffic steering. Without a standardized N3 reference point, each deployment would need proprietary integration between radio access and core forwarding, increasing complexity and reducing multi-vendor interoperability.
What changed in its specifications
The latest release-to-release comparison of specifications that define N3. 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
- N3 counterpart in another generation: S1-U
“Both the N3IWF and the TNGF interface with the 5G Core Network CP and UP functions via the N2 and N3 interfaces, respectively.” TS 23.501
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 N3 reference point between the (R)AN and the UPF is defined for the first time in the Rel-15 system architecture specification.
- “N3: Reference point between the (R)AN and the UPF.” TS 23.501 v15.13.0
Defining Specifications
3GPP specifications that define or reference N3, 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 |