Description
The User Plane Function (UPF) is a fundamental network function within the 5G Core (5GC) based on the Service-Based Architecture (SBA). It is responsible for all tasks related to the processing and forwarding of user data packets. The UPF acts as the interconnect point between the Radio Access Network (RAN) – either NG-RAN or non-3GPP access – and external Data Networks (DNs), such as the internet or operator services. Its architecture is designed to be highly flexible and distributable, allowing multiple UPF instances to be deployed in different parts of the network (e.g., central, regional, edge locations) to meet diverse latency and bandwidth requirements.
How the UPF works is governed by rules installed by the Session Management Function (SMF). The SMF provisions Packet Detection Rules (PDRs), Forwarding Action Rules (FARs), QoS Enforcement Rules (QERs), and Usage Reporting Rules (URRs) into the UPF via the N4 interface. Upon receiving a packet, the UPF inspects it (matching against PDRs) and executes the associated actions. These actions can include forwarding the packet to a specific tunnel or interface (FAR), applying QoS marking and rate limiting (QER), measuring traffic volume for charging (URR), and even duplicating packets for analytics or redundancy. A single UE session may involve multiple UPFs, such as a branching point UPF for multi-homed connectivity or an intermediate UPF for localized breakouts.
Key components of the UPF's role include being the anchor point for mobility—both intra-system and between 3GPP and non-3GPP access. It provides the external PDU Session interface, making it the official 'exit point' of the 5G network. Furthermore, the UPF is the critical enabler for several advanced 5G capabilities. For Network Slicing, different UPF instances can be dedicated to specific slices, providing isolated data paths. For Edge Computing, the UPF can be deployed at the network edge to locally route traffic to nearby application servers, drastically reducing latency. It also performs deep packet inspection for application-aware steering and supports features like traffic aggregation and IPv6 multi-homing.
Purpose & Motivation
The UPF was created as part of the clean-slate design of the 5G Core network to address the limitations of the 4G EPC's user plane, particularly the split SGW/PGW architecture. The motivations were to achieve greater flexibility, scalability, and support for new service paradigms. Key problems it solves include: enabling ultra-low latency services by allowing decentralized deployment at the network edge; providing the architectural foundation for end-to-end network slicing by offering an isolatable data plane component; and supporting a wider range of access technologies (5G NR, LTE, Wi-Fi, fixed) with a unified anchor point.
Historically, the 4G EPC gateways (SGW, PGW) were monolithic entities with control and user plane tightly coupled, making them difficult to scale independently and deploy flexibly. The 5G design principles of cloud-nativity, SBA, and Control and User Plane Separation (CUPS) directly led to the UPF's creation. The UPF is a pure, scalable user plane element that can be instantiated on demand anywhere in the network cloud. This addresses the need for a dynamic, software-driven architecture capable of supporting diverse 5G use cases, from enhanced mobile broadband (eMBB) to massive IoT (mIoT) and critical communications, each with distinct bandwidth, latency, and reliability requirements.
What changed in its specifications
The latest release-to-release comparison of specifications that define UPF. Each summary describes the whole specification, not only this term.
Rel-19 added IMS disaster prevention and restoration enhancements to TS 23.380, including detection of EPC/5GC NF failures, restoration of IMS sessions, and PCRF/PCF bypass procedures.
Full comparison in TS 23.380 →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 →Architecture
Where it sits in the network
- Mobile Network → 5G Core → UPF (User Data & Packet Gateway)
- Mobile Network → NG-RAN → UPF (5G Core (context))
Evolution Lineage
- Evolved from: S-GW (4G→5G), PGW (4G→5G)
- Network evolution overview →
Technology family
Core network elements and functions · Core Network
- Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
- Phase 2 SMS-GMSC, SMS-IWMSC
- R96 GGSN, SGSN
- R99 3G-SGSN, GLR, IM-GSN, IM-MSC
- Rel-4 CS-MGW, GMSC Server, MSC Server
- Rel-5 HSS, SLF
- Rel-6 3GPP AAA Server
- Rel-7 PCEF, PCRF
- Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
- Rel-9 HLR-FE, HSS-FE, UDR
- Rel-10 L-GW
- Rel-11 TDF
- Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
- Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
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.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 6 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 UPF is specified for the first time in Rel-15, with its service area, packet handling, QoS enforcement, Ethernet PDU support and N4/PFCP behaviour defined, and 5G UPF introduced into TS 29.244.
- 5G UPF Introduction TS 29.244CR0199
- “If no matching DL PDR is found, the UPF shall discard the DL data packet.” TS 23.501 v15.13.0
- “An SMF and UPF may support Ethernet PDU sessions, as specified in clause 5.6.10.2 of 3GPP TS 23.501[28].” TS 29.244 v15.10.0
In Rel-16 the UPF gained new functions: ATSSS-LL, MPTCP Proxy and PMF support, VLAN tag handling for Ethernet/5G-VN, UE IP address allocation by the UPF, and QoS monitoring.
- “The UPF may support MPTCP Proxy functionality, which communicates with the MPTCP functionality in the UE by using the MPTCP protocol” TS 23.501 v16.20.0
- “the UPF supports Performance Measurement Functionality (PMF), which may be used by the UE to obtain access performance measurements” TS 23.501 v16.20.0
- “The UPF performs QoS monitoring per the request received from SMF during PDU Session Establishment or Modification procedure.” TS 28.552 v16.20.0
In Rel-17 the UPF gained new behaviour: allocating internal resources by S-NSSAI and Network Instance, supporting multiple NW-TTs, forwarding (g)PTP messages, buffering uplink packets, and adapting PMF handling and SMF-set procedures.
- “The UPF may use parameters listed above in bullets 1) (e.g. S-NSSAI) and 2) (e.g. Network Instance in PDR/FAR(s)) for determining internal UPF resources.” TS 23.501 v17.15.0
- “When the buffering of uplink packets is stopped the UPF shall forward all buffered uplink packets before it forwards any new uplink packets.” TS 23.501 v17.15.0
- The introduction of UPF Service TS 23.502CR2687
Rel-18 extends the UPF with a direct event exposure service (Nupf_EventExposure), an MPQUIC Proxy, TSN transport network interworking, and Forwarding Policy based traffic steering.
- “The UPF may expose information by means of UPF Event Exposure service as described in TS 23.502 [3] clause 5.2.26.2, via a service-based interface directly.” TS 23.501 v18.12.0
- “The UPF may support the MPQUIC Proxy functionality, which communicates with the MPQUIC functionality in the UE by using the QUIC protocol” TS 23.501 v18.12.0
- Update Architecture for UPF SBI interface TS 23.501CR4937
In Rel-19 the UPF gained new capabilities: MPQUIC-UDP/IP/E proxy functionalities, NAT information exposure, direct UPF event exposure to SMF, and PDU Set Importance based transport level packet marking.
- “The UPF may support one or more of the MPQUIC Proxy functionalities (i.e. the MPQUIC-UDP, MPQUIC-IP, MPQUIC-E Proxy functionalities)” TS 23.501 v19.9.0
- “a UPF supporting NAT information exposure functionality can register this capability with the NRF and the UPF can expose mapping between public and private IP addresses” TS 23.501 v19.9.0
- “UPF performs transport level packet marking in DL on a per QoS Flow basis (optionally taking into account PDU Set Importance, if applicable)” TS 23.501 v19.9.0
UPF gained new behaviours in Rel-20: node-level abnormal-traffic mitigation rules, abnormal traffic pattern event exposure, SCONE rate signal marking, and satellite-based local switching.
- “The UPF may be provisioned by SMF with Packet Detection Rules for a PDU Session to detect abnormal traffic.” TS 23.501 v20.3.0
- “the UPF shall detect SCONE packets in the traffic flows identified by the PDRs and update the Rate Signal field” TS 29.244 v20.1.0
- New event ID of UPF for abnormal UP traffic TS 23.502CR5633
Defining Specifications
3GPP specifications that define or reference UPF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.380 vk00 | IMS Restoration Procedures | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.527 vk00 | 5G Restoration Procedures for N4 Interface | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 read |
| TS 24.193 vk10 | ATSSS Stage 3 Procedures | Rel-20 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.502 vk00 | Non-3GPP Access Network Discovery and Selection | Rel-20 read |
| TS 26.113 vj20 | Real-Time Media Communication Protocols and APIs | Rel-19 read |
| TS 26.501 vk00 | 5G Media Streaming Architecture | Rel-20 read |
| TS 26.522 vj40 | RTP for XR in 5G Systems | Rel-19 read |
| TS 26.802 vk00 | 5G Media Streaming Multicast Enhancements | Rel-20 read |
| TR 26.803 vh00 | 5G Media Streaming Extensions for Edge Processing | Rel-17 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TR 26.806 vi00 | Technical Report on Smartly Tethering AR Glasses | Rel-18 read |
| TS 26.822 vj30 | Study on 5G RTP Configurations Phase 2 | Rel-19 read |
| TR 26.857 vi00 | Technical Report on Media Service Enablers | Rel-18 read |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 read |
| TR 26.919 vj00 | Study on 5G Conversational Media Handling | Rel-19 read |
| TR 26.926 vj00 | Traffic Models & Quality Evaluation for Media/XR in 5G | Rel-19 read |
| TS 26.942 vk00 | Sustainable Media Metrics and Architectural Impacts for 5G | Rel-20 read |
| TS 28.802 vf00 | Management Study for 5G Network Architecture | Rel-15 read |
| TR 28.822 vh00 | Charging for 5G LAN Services Study | Rel-17 read |
| TR 28.833 vi01 | Technical Report on 5G LAN-type Service Management | Rel-18 read |
| TR 28.836 vi00 | Technical Report on Intent Driven Management | Rel-18 read |
| TS 28.874 vj10 | Study on Management Aspects of NTN Phase 2 | Rel-19 read |
| TS 29.244 vk10 | PFCP for Control and User Plane Separation | Rel-20 read |
| TS 29.502 vk10 | 5G SMF Service Based Interface Stage 3 | Rel-20 read |
| TS 29.508 vk10 | Session Management Event Exposure Service | Rel-20 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 29.513 vk10 | 5G PCC Signalling Flows | Rel-20 read |
| TS 29.514 vk10 | Policy Authorization Service | Rel-20 read |
| TS 29.519 vk10 | 5G UDR Policy and Application Data Services | Rel-20 read |
| TS 29.520 vk10 | 5G NWDAF Services | Rel-20 read |
| TS 29.523 vk10 | Policy Control Event Exposure Service | Rel-20 read |
| TS 29.532 vk00 | Nmbsmf Service Based Interface Specification | Rel-20 read |
| TS 29.552 vk10 | 5G Network Data Analytics Procedures | Rel-20 read |
| TS 29.561 vk10 | 5G Network Interworking Procedures | Rel-20 read |
| TS 29.564 vk10 | Nupf Service Based Interface | Rel-20 read |
| TS 29.574 vk10 | DCCF Service Based Interface | Rel-20 read |
| TS 29.575 vk10 | ADRF Service Based Interface | Rel-20 read |
| TS 29.585 vj00 | TSN Interworking Protocol for 5G System | Rel-19 read |
| TR 29.820 vh00 | Study on PFCP Best Practice | Rel-17 read |
| TS 29.866 vj00 | IMS Disaster Prevention & Restoration Enhancement | Rel-19 read |
| TS 29.889 vj10 | Study on UPF data collection for AI/ML | Rel-19 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 29.892 vg00 | Study on User Plane Protocol in 5GC | Rel-16 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.255 vk30 | 5G Data Connectivity Converged Charging | Rel-20 read |
| TS 32.279 vj00 | 5G MBS Session Converged Charging | Rel-19 read |
| TS 32.899 vf10 | 5G Charging Architecture Study | Rel-15 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.501 vk30 | 5G Security Architecture | Rel-20 read |
| TS 33.515 vk00 | 5G SMF Security Assurance Specification | Rel-20 read |
| TR 33.739 vi10 | Study on security enhancement of support for | Rel-18 read |
| TS 33.749 vj00 | Study on security aspects of edge computing enhancement | Rel-19 read |
| TS 33.835 vg10 | Study on authentication and key management for apps | Rel-16 read |
| TR 33.851 vh10 | Security for Industrial IoT in 5G | Rel-17 read |
| TS 33.861 vg10 | CIoT Security Evolution for 5G System | Rel-16 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.305 vj30 | NG-RAN UE Positioning Stage 2 | Rel-19 read |
| TS 38.410 vj20 | NG-RAN; NG General Aspects and Principles | Rel-19 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |
| TS 38.414 vj00 | NG Interface User Plane Protocol | Rel-19 read |
| TS 38.415 vj10 | PDU Session User Plane Protocol | Rel-19 read |
| TS 38.423 vj40 | NG-RAN Xn Application Protocol | Rel-19 read |