Description
A Multi-Access PDU Session (MA PDU Session) is a type of Protocol Data Unit (PDU) Session in the 5G System that can be established over multiple access networks. Specifically, it can use one access network at a time (either 3GPP or non-3GPP) or simultaneously use one 3GPP access network (e.g., NR or LTE) and one non-3GPP access network (e.g., Wi-Fi or wireline). This capability is defined in 3GPP TS 23.501 and related specifications such as TS 29.512 (N4 interface) and TS 29.561 (Interworking with Non-3GPP Networks). The MA PDU Session is a cornerstone of 5G's support for access traffic steering, switching, and splitting (ATSSS), which allows the network to dynamically route traffic across available accesses based on operator policies, link quality, and service requirements.
The architecture of an MA PDU Session involves several key network functions. The SMF (Session Management Function) manages the session and enforces ATSSS policies. The UPF (User Plane Function) handles the user plane traffic and may perform measurements to support traffic steering. For non-3GPP access, the N3IWF (Non-3GPP InterWorking Function) or TNGF (Trusted Non-3GPP Gateway Function) provides connectivity. The UE (User Equipment) must support the ATSSS feature and the Multi-Access PDU Session procedures, including the ability to maintain simultaneous connectivity over both accesses. The AMF (Access and Mobility Management Function) coordinates registration and mobility across both accesses.
The MA PDU Session can be established with different modes of operation. In the single-access mode, the session uses only one access at a time, but can switch between accesses based on triggers such as signal strength or policy. In the multi-access mode, both accesses are active simultaneously, and traffic can be split at the IP flow level or even within a flow using MPTCP (Multipath TCP) or QUIC. This allows for improved throughput, reliability, and seamless handover between accesses. The ATSSS rules are provided by the SMF to the UE and UPF, specifying how to steer traffic (e.g., active-standby, smallest delay, load balancing).
The MA PDU Session offers several benefits. It enhances user experience by providing seamless connectivity when moving between 3GPP and non-3GPP accesses, without dropping sessions. It enables operators to leverage both licensed and unlicensed spectrum, improving capacity and coverage. It also supports new use cases such as Fixed Wireless Access (FWA) and enhanced mobile broadband (eMBB) with multi-access aggregation. Furthermore, it simplifies network operations by unifying session management across heterogeneous accesses, as opposed to maintaining separate sessions for each access.
However, deploying MA PDU Sessions requires careful consideration of policy and charging, as well as support in the UE and network. 3GPP has specified the necessary signaling in TS 24.501 (NAS) and TS 24.193 (ATSSS). The feature has evolved since its introduction in Release 16, with subsequent releases refining procedures and adding support for additional access types and steering modes. As 5G evolves towards 6G, the concept of multi-access sessions is expected to expand further, integrating satellite and other non-terrestrial networks.
Purpose & Motivation
The MA PDU Session was introduced in Release 16 to address the growing need for seamless integration of multiple access technologies in 5G networks. Prior to this, 3GPP systems supported interworking between 3GPP and non-3GPP accesses but typically through separate PDU Sessions that required complex handover procedures and could result in service interruption. The MA PDU Session provides a unified session that can span both access types, enabling smoother mobility and better resource utilization.
The primary motivation was to enable operators to leverage both licensed and unlicensed spectrum effectively, improving capacity and coverage. With the explosion of data traffic, operators needed ways to offload traffic to Wi-Fi or other non-3GPP accesses without sacrificing session continuity. The MA PDU Session allows for dynamic traffic steering, which can optimize network performance and user experience. Additionally, it supports use cases like Fixed Wireless Access where a single session can be maintained across different access technologies.
Another key driver was the desire to simplify the core network architecture. Instead of maintaining separate session management contexts for each access, a single MA PDU Session can be managed by a single SMF, reducing signaling overhead and complexity. This also facilitates policy and charging consistency across accesses. The MA PDU Session thus represents a significant step towards a truly converged network where access technologies are transparent to the user and services are delivered seamlessly.
What changed in its specifications
The latest release-to-release comparison of specifications that define MA PDU Session. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds multi-access ATSSS capabilities, QoS monitoring with available-bitrate parameters, and XR/media policy provisioning such as data burst size and expedited transfer. It also adds local offloading management, non-3GPP device information, and URSP provisioning in EPS support.
Full comparison in TS 29.512 →Technology family
Sessions, bearers and QoS · Core Network
- R96 PDP context
- R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
- Rel-7 IP-CAN bearer, IP-CAN session, QCI
- Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
- Rel-9 Evolved ARP
- Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
- Rel-16 MA PDU Session
- MA PDU Session builds on PDU Session
“This component in the UE initiates the establishment of one or more multipath QUIC connections, after the establishment of the MA PDU Session” TS 23.501
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 4 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-16 defines the MA PDU Session for the first time: a PDU Session using one access at a time or both 3GPP and non-3GPP simultaneously, with ATSSS procedures for establishment and release.
- “MA PDU Session: A PDU Session that provides a PDU connectivity service, which can use one access network at a time, or simultaneously one 3GPP access network and one non-3GPP access network.” TS 23.501 v16.20.0
- “a MA PDU Session is a PDU Session associated with two independent N3/N9 tunnels between the PSA and RAN/AN and with multiple access types” TS 23.502 v16.19.0
- Introduction of ATSSS Procedures including Multi-Access PDU Session Establishment TS 23.502CR0866
Rel-17 extends MA PDU Session so its 3GPP access leg can use an EPC PDN Connection alongside non-3GPP access in 5GC, and adds NSAC handling and EPS mobility behaviour for it.
- “A Multi-Access PDU Session may for the 3GPP access use user-plane resources of an associated PDN Connection on 3GPP access in EPC” TS 23.501 v17.15.0
- “the SMF should keep the user-plane resources over non-3GPP access in 5GC and use the PDN Connection as the 3GPP access leg of the MA PDU Session” TS 23.502 v17.15.0
- Support for MA PDU Session with 3GPP access in EPC TS 24.301CR3591
Rel-18 extends MA PDU Session to combine a 3GPP access connected to 5GC with a non-3GPP access connected to EPC (previously unsupported), and adds MPQUIC steering capability determination.
- “A MA PDU Session may also be a PDU Session associated with one 3GPP access connected to EPC and one non-3GPP access connected to 5GC” TS 23.502 v18.14.0
- “Clause 4.22.2.4 specifies the MA PDU Session establishment procedure with non-3GPP access connected to EPC and 3GPP access connected to 5GC.” TS 23.502 v18.14.0
- Determining the ATSSS capabilities of a MA PDU Session when the UE supports MPQUIC TS 23.501CR4457
MA PDU Session handling was extended in Rel-19: MPQUIC-UDP, MPQUIC-IP and MPQUIC-E functionalities are added, including Ethernet MA PDU Sessions, with new SMF capability determination and PCF steering rules.
- “Either ATSSS-LL or MPQUIC-E functionality is enabled in the 5GC for MA PDU Session of type Ethernet.” TS 23.501 v19.9.0
- “If MA PDU Session is capable of supporting both MPQUIC-E and ATSSS-LL functionalities in the uplink and downlink” TS 23.503 v19.8.0
- MA PDU Session and PDN connections updates due to MPQUIC-IP/MPQUIC-UDP/MPQUIC-E TS 23.502CR4980
Defining Specifications
3GPP specifications that define or reference MA PDU Session, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 29.561 vk10 | 5G Network Interworking Procedures | Rel-20 read |