5G SMF Session Management: PDU Sessions, QoS Flows & PFCP Protocol
Published June 21, 2026 • 7 min read • Telecom Insights
The 5G Session Management Function (SMF) is the control-plane entity responsible for managing PDU (Protocol Data Unit) Sessions — the 5G equivalent of 4G LTE's EPS Bearers. The SMF handles session establishment, modification, and release; IP address allocation (from the UPF or external DHCP); QoS flow management; and UPF selection and control via the PFCP (Packet Forwarding Control Protocol) on the N4 interface.
Key Takeaway: A single SMF instance manages up to 1–2 million concurrent PDU Sessions, each with up to 64 QoS Flows, translating to tens of millions of N4 rules installed across a cluster of UPFs — an enormous state management challenge.
PDU Session Lifecycle
A PDU Session provides end-to-end IP connectivity between the UE and a Data Network (DN). The session lifecycle: (1) Establishment — triggered by UE request via NAS SM message, the SMF selects a UPF, allocates IP address, and installs N4 rules; (2) Modification — adds/removes QoS Flows, changes UPF (SSC mode 2/3), or inserts I-UPF for mobility; (3) Release — UE-initiated, network-initiated (e.g., subscription change), or implicit (radio link failure). The SMF supports three SSC (Session and Service Continuity) modes: SSC Mode 1 (fixed UPF anchor — IP preserved), Mode 2 (break-before-make — IP changes), Mode 3 (make-before-break — temporary dual connectivity).
QoS Flow Architecture
The 5G QoS model is flow-based rather than bearer-based. Each PDU Session contains one or more QoS Flows, identified by QFI (QoS Flow Identifier). Each QoS Flow is characterised by a 5QI (5G QoS Identifier) that defines: resource type (GBR, non-GBR, Delay-Critical GBR), priority level, packet delay budget (PDB, 10–300 ms), packet error rate (PER, 10−2 to 10−5), and averaging window. The SMF maps QoS Flows to AN (Access Network) resources by signalling the QoS profile to the gNB, and to CN resources by installing corresponding N4 rules at the UPF.
PFCP (N4) Interface: Rules Installation
The SMF controls the UPF via the PFCP (Packet Forwarding Control Protocol) on the N4 interface — defined by 3GPP TS 29.244. PFCP uses a node-level association between SMF and UPF, established via PFCP Association Setup/Update messages. The SMF installs PDRs (Packet Detection Rules) — defining traffic filters (IP 5-tuple, application ID) — and associated FARs (Forwarding Action Rules) — instructing the UPF to forward, drop, buffer, or duplicate matching packets. QERs (QoS Enforcement Rules) define MBR/GBR limits, and URRs (Usage Reporting Rules) define volume/time thresholds for offline/online charging. PFCP over SCTP provides reliable delivery with heartbeat-based liveness detection.
ULCL and Multi-Homed Sessions
For edge computing scenarios, the SMF can configure an ULCL (Uplink Classifier) UPF that diverts specific traffic flows to a local DN while forwarding other flows to the central UPF anchor. The SMF installs PDRs at the ULCL UPF matching the target application traffic (e.g., based on destination IP or FQDN resolved via DNS inspection) and steers matching packets to the local N6 interface. Multi-homed PDU Sessions (IPv6 only) use a Branching Point UPF that routes traffic to different DNs based on the UE's source IPv6 prefix — useful for simultaneous access to local and central services.
SMF Selection and Load Balancing
Multiple SMF instances serve a network, with the AMF selecting an SMF based on: DNN, S-NSSAI, UE location, and SMF load/capacity. The NRF provides the set of available SMFs meeting the selection criteria. Within the SMF set, load balancing (round-robin, least-loaded, hash-based) distributes new sessions. For stateful failover, SMF instances share session state via the UDSF (Unstructured Data Storage Function) or through direct inter-SMF context transfer — enabling another SMF to assume control of orphaned sessions when an SMF instance fails.
The SMF is the session-state anchor of the 5G core — managing millions of stateful sessions with complex rule sets across a distributed UPF fabric. Its design for horizontal scalability and geographic redundancy is essential for carrier-grade 5G deployments.
