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

Glossary term · Core Network

Multi-access PDN connection

Multi-access Packet Data Network Connection

Core Network →

Multi-access PDN connection is a PDN connection whose IP flows can be routed over 3GPP access, WLAN access, or both, with each flow using only one access at a time.

Introduced
Rel-13
Where
Core Network › 5G Core
Specifications
3 specs
Multi-access PDN connection Description Purpose Neighbours Specifications

Description

A Multi-access PDN Connection is defined in 3GPP TS 23.161 (architecture enhancements for multi-access) and TS 24.161 (protocol aspects), with foundational study in TR 23.861. It is a PDN connection in the Evolved Packet Core (EPC) that can carry IP flows over both 3GPP access (LTE/5G NR) and non-3GPP access (WLAN/Wi-Fi). The key property is that, at any single moment, each individual IP flow is routed over exactly one access, but different flows of the same PDN connection can use different accesses, and flows can be moved between accesses based on policy, link quality, or user preference.

The architecture builds on the concept of multiple packet data network connections and on the S2a/S2b interfaces for trusted and untrusted WLAN access. A UE establishes a PDN connection through the 3GPP access and then adds a WLAN access path to the same PDN connection. The PGW (PDN Gateway) anchors the connection and acts as the IP mobility anchor, so the UE's IP address remains stable even as flows move between accesses. The ANDSF (Access Network Discovery and Selection Function) or, in 5G, the PCF provides policies that determine which flows should use which access, based on criteria such as application type, subscriber tier, network load, or Wi-Fi signal quality.

Flow mobility is the central mechanism. The UE and network use IP flow mobility (IFOM) procedures defined in TS 23.261 to bind specific IP flows to specific accesses. The UE can request that a flow be moved, or the network can initiate the move via policy. The PGW maintains binding information that maps each flow (identified by source/destination IP address and port, and protocol) to an access. When a flow moves, the PGW updates its binding and routes packets accordingly, while keeping the same IP address for the UE. This allows, for example, a video stream to be moved to Wi-Fi while a voice call remains on cellular.

Multi-access PDN connections also support access aggregation in some configurations, where a single flow can be split across accesses (though the definition states each flow is routed over only one access at a time, aggregation is handled by higher-layer mechanisms such as MPTCP). The connection can be used with both trusted and untrusted WLAN access, with different security procedures (e.g., IPSec for untrusted access).

In the 5G era, the concept evolved into Multi-Access PDU (MA-PDU) sessions under ATSSS (Access Traffic Steering, Switching, and Splitting), but the Multi-access PDN Connection remains the EPC-era foundation. It is significant because it allows operators to leverage Wi-Fi for capacity and coverage while maintaining a consistent IP anchor and policy control, improving user experience and network efficiency.

Purpose & Motivation

Multi-access PDN Connection was created to address the growing demand for mobile data and the desire to leverage Wi-Fi networks for capacity and coverage. Before its introduction, a UE could have separate PDN connections over cellular and Wi-Fi, but there was no standardized way to route individual IP flows of the same connection across both accesses while keeping a stable IP address. This limited the ability to seamlessly offload traffic or to use Wi-Fi for specific applications without breaking sessions.

The feature was motivated by operator strategies to integrate Wi-Fi into their networks, reducing cellular congestion and improving indoor coverage. It also addressed the need for policy-driven traffic steering, where the operator can decide which flows use which access based on subscription, application, or network conditions. By anchoring the connection at the PGW and using flow bindings, the feature provides IP address continuity, which is essential for applications that cannot tolerate address changes.

The Multi-access PDN Connection also laid the groundwork for later 5G features such as ATSSS, which extends the concept to PDU sessions with more advanced steering, switching, and splitting capabilities. It represents an important step in the evolution toward heterogeneous, multi-access networks.

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-13 Initial

Multi-access PDN Connection was introduced, defining a PDN connection whose IP flows can be routed over 3GPP or WLAN access, with each flow using only one access at a time, based on TS 23.161 and TS 24.161.

The definition carried over unchanged; the feature continued to support flow mobility across 3GPP and WLAN access.

The definition carried over unchanged; no textual revision was recorded in the quoted definition.

The definition carried over unchanged; the concept remained stable as 5G ATSSS work progressed in parallel.

The definition carried over unchanged; the EPC-era feature continued to be referenced alongside 5G multi-access enhancements.

The definition carried over unchanged; no textual revision was recorded in the quoted definition.

The definition carried over unchanged; the term remained stable in the specifications.

Defining Specifications

3GPP specifications that define or reference Multi-access PDN connection, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.161 vj00 Network-based IP Flow Mobility (NBIFOM) Rel-19 read
TS 23.861 vd00 Network-Based IP Flow Mobility (NBIFOM) Rel-13 read
TS 24.161 vj00 Network-Based IP Flow Mobility (NBIFOM) Rel-19 read