Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Interface

N4

Reference point between the SMF and the UPF

Interface →

N4 is the 5G control-plane reference point between the SMF and the UPF, using PFCP to create, modify, and delete packet inspection and forwarding rules in the user plane.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
2 specs
N4 Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

N4 is the control-plane reference point between the SMF and the UPF in the 5G core. It is not a user-plane interface; instead, it carries signaling that tells the UPF how to inspect, forward, classify, and report packets. The SMF is responsible for session management, UPF selection, PDU session establishment, and policy enforcement. The UPF is responsible for packet forwarding, QoS enforcement, traffic detection, and charging data generation. N4 connects these two functions so that the control plane can dynamically program the user plane.

The protocol used on N4 is PFCP, defined in 3GPP TS 29.244. PFCP operates over UDP and can be secured with transport-level protection such as TLS. It has two major categories of operation: node-level and session-level. Node-level messages manage associations between SMFs and UPFs, heartbeat, node reports, and packet detection function updates. Session-level messages establish, modify, and delete PDU session contexts inside the UPF. During session establishment, the SMF provides the UPF with tunnel endpoint identifiers for N3, N9, and N6, along with rules for how packets should be handled.

A key concept in N4 is the packet forwarding control model. The SMF installs PDRs, which define how incoming packets are detected and which forwarding action should be applied. FARs tell the UPF what to do with matching packets, such as forward, drop, buffer, or duplicate. QERs define QoS enforcement parameters, including bit rates and QoS characteristics. URRs define usage reporting, and BARs can define buffering actions. These rules allow the UPF to apply service-specific handling without the SMF being involved in every packet. N4 therefore makes the UPF programmable and scalable.

N4 is essential for control-user plane separation. In 5G, the UPF can be deployed independently from the SMF, allowing operators to scale user-plane capacity near the edge while keeping control functions centralized or distributed as needed. The SMF uses N4 to select the appropriate UPF for a session, update it during mobility, and configure traffic steering. For example, when a UE moves to a new area, the SMF may relocate the PSA UPF and use N4 to update the UPF context. When local breakout is needed, the SMF may insert an intermediate UPF and configure N4 rules for branching and traffic filtering.

N4 also supports charging, lawful interception, and network analytics. The UPF can generate usage reports based on URRs installed by the SMF, and these reports can be used for online or offline charging. The SMF can also configure traffic detection and forwarding rules that support lawful interception or service-specific measurement. Because N4 is a control interface, its reliability and security are critical. Operators protect it with network isolation, authentication, authorization, and encryption where applicable. In summary, N4 is the programming interface that connects 5G session management logic to the actual packet forwarding engine.

N4 also includes mechanisms for resilience and session recovery. If a UPF restarts or an association is disrupted, the SMF can recover session contexts using PFCP session report and node report procedures. This helps maintain PDU sessions after failures or planned maintenance. The interface can also support scenarios where multiple SMFs interact with the same UPF, although a given session is controlled by the SMF that owns it. This flexibility is important in large networks where UPFs may serve many regions and many control-plane nodes. By separating session ownership from physical user-plane capacity, N4 enables operators to build resilient, multi-vendor 5G core deployments.

Purpose & Motivation

N4 exists to enable the control-user plane separation that is fundamental to the 5G core. In earlier architectures, session control and packet forwarding were more tightly coupled, which made it difficult to scale the user plane independently or place it close to the edge. N4 solves this by defining a standardized protocol through which the SMF can program the UPF. The SMF can remain a centralized or distributed control function, while the UPF can be deployed where traffic needs to be processed, filtered, forwarded, or anchored.

The motivation is also driven by the need for dynamic traffic steering and service-based architecture. 5G services require rapid session establishment, mobility updates, QoS changes, and local breakout. A static forwarding configuration cannot support these needs efficiently. N4 allows the SMF to install packet detection, forwarding, QoS, and reporting rules on demand. This makes the UPF a programmable data-plane node rather than a fixed router. It also supports multi-vendor interoperability because operators can select SMF and UPF implementations independently as long as they conform to PFCP and the relevant 3GPP specifications.

N4 also addresses charging and policy enforcement. The UPF must generate usage information that can be correlated with subscriber sessions and policy decisions. N4 gives the SMF a way to configure reporting rules and tunnel endpoints so that the UPF can produce the data needed for online charging, offline charging, and lawful interception. By placing this control on a dedicated reference point, 5G avoids mixing user traffic with management signaling and improves scalability, reliability, and security.

What changed in its specifications

The latest release-to-release comparison of specifications that define N4. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

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 →
TS 29.244Rel-18 → Rel-19

Rel-19 adds MPQUIC-based steering for multi-access PDU sessions and SMF restoration with alternative-SMF handling. It also adds RTP header handling rules, Media over QUIC payload handling, and N6 delay measurement between UPF and endpoints.

Full comparison in TS 29.244 →

Technology family

Core network interfaces and reference points · Core Network

  1. R97 Gi, Gn, Gp
  2. Rel-7 Gx
  3. Rel-8 S1-MME, S1-U, S11, S5, S8, SGi
  4. Rel-15 N11, N2, N3, N4, N6, N7, N9

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 sources

Documented 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.

Rel-15 introduced

N4 is defined for the first time as the reference point between the SMF and the UPF in the Rel-15 5G system architecture.

Defining Specifications

3GPP specifications that define or reference N4, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read