Separating the user plane from the control plane turned a fixed network element into a placement decision. The user plane function can sit in a national data centre, at a regional edge, or at the cell site itself — and that choice determines latency, backhaul cost, operational burden and whether local traffic ever leaves the building. It is also where 5G and Wi-Fi converge.
The 5G core separates signalling from data. Session management, policy and authentication happen in control-plane functions; the user plane function is the element every user packet physically passes through.
Its work is forwarding, tunnel termination toward the radio network, quality-of-service enforcement, usage measurement for charging, and the point at which traffic leaves for an external data network. The control plane instructs it; it does not make session decisions itself.
Because it is separate, it can be placed anywhere the operator chooses. That is the whole point of the separation, and it is a more consequential decision than the specification makes it look.
| Position | What it buys | What it costs |
|---|---|---|
| Central data centre | Few instances, simple operations, straightforward security boundary | Every packet traverses the backhaul to reach the internet and back; latency floor set by distance |
| Regional edge | Materially lower latency and reduced transport load, still a manageable instance count | More sites to secure, monitor and update; regional traffic engineering becomes a real task |
| Cell site or enterprise premises | Lowest achievable latency and true local breakout — traffic between two devices need never leave the site | An instance per location: hardware, physical security, lifecycle and update across a large estate |
The right answer is rarely uniform. Most networks run a small number of central instances for general traffic and push user plane out only where a specific application justifies the operational burden.
A device with both cellular and Wi-Fi has historically treated them as separate networks with separate addresses and separate sessions. Convergence means treating them as two paths to the same session, and the user plane function is where those paths come together.
Access traffic steering, switching and splitting is the mechanism. Steering chooses which access carries a flow. Switching moves an established flow between accesses without breaking it. Splitting uses both simultaneously for a single flow, with a multipath transport reassembling at the anchor.
That anchor is the user plane function. It terminates both the 3GPP path and the non-3GPP path — the latter reached through an interworking function — and presents one session to the data network. Which is why placement and convergence are the same conversation: the anchor has to be somewhere sensible relative to both accesses.
The practical constraints are unglamorous. Splitting a flow across two paths of different latency requires reordering and buffering. Device support varies. And a Wi-Fi network the operator does not control offers none of the guarantees the scheduler provides on licensed spectrum, so the steering policy has to assume the worse path can degrade without warning.
The element in the 5G core that every user packet passes through. It forwards traffic, terminates tunnels toward the radio network, enforces quality of service, measures usage for charging, and provides the exit point to external data networks. Control-plane functions instruct it; it does not make session decisions itself.
Because it sets the latency floor and determines how much traffic crosses the backhaul. A central instance is simplest to operate but forces every packet to travel to a data centre and back; an instance at the cell site gives the lowest latency and true local breakout at the cost of managing many instances.
Terminating traffic at or near the site rather than carrying it to a central core. It allows devices on the same site to communicate without their traffic leaving, which reduces latency and transport cost and can satisfy data residency requirements.
Only where something justifies it — a latency budget that distance would exceed, traffic that should not leave the premises, constrained backhaul, or a residency obligation. Otherwise the operational burden of an instance per location outweighs the benefit.
Through access traffic steering, switching and splitting. Steering selects which access carries a flow, switching moves a flow between accesses without breaking it, and splitting uses both at once with a multipath transport reassembling at a common anchor — which is the user plane function.
Two paths with different latency need reordering and buffering when a flow is split. Device support for the capability varies. And a Wi-Fi network the operator does not control offers none of the scheduling guarantees licensed spectrum does, so steering policy has to assume that path can degrade without warning.
Written for engineers. Share it with one.
How Wi-Fi reaches the core.
TECHNOLOGYWhy the split exists at all.
PRODUCTLocal core and breakout.
KNOWLEDGESharing the radio network.
TECHNOLOGYRU, DU, CU and the haul between.
SOLUTIONCoverage layers together.
Tell us the specification, the constraint and the deadline. Programmes that cross silicon, radio, embedded and AI are where Faststream is strongest.