Description
Multi-Path TCP (MPTCP) is an extension to the standard Transmission Control Protocol (TCP) that enables the simultaneous use of multiple network paths between two communicating hosts. Unlike regular TCP, which establishes a single connection over one source-destination IP address pair, MPTCP sets up a master TCP connection and then establishes additional subflows across different available interfaces or IP addresses. These subflows are aggregated into a single logical connection visible to the application, which continues to use a standard socket interface. The protocol manages the splitting and recombining of data across the subflows, ensuring in-order delivery to the application while optimizing the use of available bandwidth.
Architecturally, MPTCP operates at the transport layer, with extensions to the TCP option field to carry connection management information. Key components include the MPTCP-capable endpoints and, optionally, middleboxes like proxies that support the extension. The protocol uses a cryptographic token to securely associate multiple subflows with the same connection. A path manager component at each endpoint discovers available interfaces and IP addresses, and a scheduler decides how to distribute data across the subflows based on factors like path latency and congestion. A congestion control algorithm, typically coupled but not locked, manages congestion on each subflow independently while aiming for fairness with regular TCP flows on shared links.
In a 3GPP context, MPTCP is particularly relevant for User Equipment (UE) with multiple radio access technologies, such as 5G NR, LTE, and Wi-Fi. The UE can establish subflows over each activated PDU session or access network. The 3GPP architecture supports MPTCP through enhancements in the User Plane, such as defining how the UPF handles multiple tunnels corresponding to the subflows. The protocol's ability to migrate traffic from one path to another provides seamless mobility, for instance, when a UE moves out of Wi-Fi coverage, the cellular subflow can take over without interrupting the application session. This requires coordination with the 3GPP core's session management to manage IP address changes and PDU session continuity.
Purpose & Motivation
MPTCP was developed to overcome the limitations of traditional TCP, which is restricted to a single path per connection, making it unable to leverage the multiple network interfaces commonly available on modern devices. This single-path constraint leads to suboptimal resource utilization, as bandwidth from additional interfaces remains unused. It also results in poor resilience; if the single path fails, the TCP connection breaks, requiring application-layer recovery. MPTCP solves these problems by enabling concurrent use of multiple paths, thereby increasing aggregate throughput, improving reliability through path redundancy, and enhancing mobility by allowing connection migration.
The motivation for standardizing MPTCP within 3GPP, starting in Release 16, stems from the proliferation of multi-RAT devices and the need for efficient traffic aggregation and seamless session continuity in 5G networks. Prior solutions, like link aggregation at lower layers or application-level multiplexing, were either non-standard or inefficient. MPTCP provides a standardized, transport-layer solution that is transparent to most applications. It addresses specific 5G use cases such as enhanced mobile broadband (eMBB) requiring high throughput, ultra-reliable low-latency communications (URLLC) requiring resilience, and support for access traffic steering, switching, and splitting (ATSSS) functions.
Historically, IETF developed the base MPTCP protocol. 3GPP's work integrates and profiles MPTCP for the cellular ecosystem, defining how it interacts with 3GPP-specific functions like PDU sessions, QoS flows, and network-based traffic steering. This integration ensures that MPTCP operations are aligned with cellular network policies, charging, and security models, enabling operators to offer enhanced services that leverage multiple accesses in a controlled and efficient manner.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (245 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the MPTCP function was introduced through the foundational support for a **multi-homed IPv6 PDU Session**, enabling a UE to use multiple IP addresses over different access paths concurrently. This was technically underpinned by referencing IETF RFC 7157 for IPv6 multihoming and integrating the necessary routing rules and session management corrections to handle the associated protocol stacks and interworking.
- Fixes for CP protocol stack TS 23.501CR0083
- UE support for Multi-homed IPv6 PDU Session TS 23.501CR0105
- Correction to Providing AF request to multiple PCFs TS 23.501CR0161
- Correction on Control Plane protocol stacks TS 23.501CR0240
- Update for providing policy requirements to multiple UEs TS 23.501CR0280
- Avoid the case the one UE MAC shared by multiple Ethernet PDU Sessions TS 23.501CR0406
+ 20 more changes
In Release 16, key enhancements for MPTCP included the introduction of a PCC rule specifically for non-MPTCP traffic to enable policy control differentiation and clarifications on Reflective QoS for MPTCP to ensure proper quality-of-service handling. Furthermore, the release provided a clarification about an MA PDU Session using only MPTCP functionality and defined QoS aspects for link-specific multipath and MPTCP proxy addresses within the MA PDU session framework.
- QoS for Multi-Access PDU Session TS 23.501CR0770
- Protocol stack for W-5GAN support TS 23.501CR0961
- Multiple Access PDU Session TS 24.501CR1122
- Procedure for Multiple Access upgrade of PDU Session TS 24.501CR1269
- Port management information container: Delivery via the NAS protocol and coding TS 24.501CR1470
- Add performance measurements extension to support multiple tenants environment TS 28.552CR0140
+ 57 more changes
In Release 17, the MPTCP function was enhanced by incorporating the latest IETF RFC 8684, "TCP Extensions for Multipath Operation with Multiple Addresses," as the definitive base protocol. This update provided the standardized technical foundation for multipath TCP operations within the 5G system architecture. The release also included protocol impacts on the N4 interface to support these transport capabilities for multicast-broadcast services.
- Multimedia Priority Service (MPS) Phase 2 support for Data Transport Service TS 23.501CR2536
- Function Description for Multi-SIM devices TS 23.501CR2553
- Support multiple NSACFs for one S-NSSAI during UE mobility TS 23.501CR2909
- Definitions and abbreviations for Multi-USIM in 5GS TS 24.501CR3119
- Using Service Request procedure for removing paging restrictions in 5GS for a Multi-USIM UE TS 24.501CR3226
- Multi-USIM UE support indications in 5GS TS 24.501CR3121
+ 42 more changes
In Release 18, MPTCP enhancements were focused on enabling multi-modal services and improving traffic routing for complex network scenarios. Specifically, the Npcf_SMPolicyControl service was updated to support multi-modal flows, allowing for policy control across different transport paths concurrently. Furthermore, support was added for DNS traffic routing in multiple DNN networks sharing the same IP address range, optimizing path selection and session continuity.
- Multiple NSACF architecture enhancement TS 23.501CR3785
- KI#4: Support for Centralized NSACF in a PLMN with multi-service areas TS 23.501CR3822
- Policy control enhancements to support multi-modal flows TS 23.501CR3864
- Support for 5G VN group with multiple SMF(Set)s TS 23.501CR4306
- Protocol error handling enhancements for Type 6 IE container IEs TS 24.501CR5031
- Indicating Uplink data status IE in REGISTRATION REQUEST message after failure of resumption of the RRC connection for UE that has joined Multicast session TS 24.501CR5320
+ 52 more changes
In Release 19, the key new feature for MPTCP is the introduction of explicit **support for MPTCP and MPQUIC-UDP steering functionalities**. This builds upon the existing IETF-defined Multipath TCP extensions (RFC 8684) referenced in the specifications. The release also enhances support for multiplexed media flows, including differentiated QoS handling and the introduction of (S)RTP Multiplexed Media Information, which work alongside the new multipath transport steering capabilities.
- Control Plane and User Plane Protocol stacks involving the MWAB node TS 23.501CR5561
- General description of relaying media related information over N6 using an encapsulation protocol TS 23.501CR5711
- Update for Support differentiated QoS handling for multiplexed media flows TS 23.501CR5783
- Support Differentiated QoS handling for encrypted multiplexed media flows TS 23.501CR6042
- Enhancement of 5G ProSe capability for multi-hop relays TS 24.501CR6552
- (S)RTP multiplexed media information support TS 24.501CR6576
+ 42 more changes
In Release 20, the MPTCP function was enhanced to support charging aspects for multi-modality services through the addition of new information elements. Furthermore, corrections were made to the Energy Consumption calculation methodology to accurately account for scenarios involving redundant transmission or a PDU Session with multiple PDU Session Anchors. These updates ensure proper network resource accounting and energy efficiency reporting for multi-path connections.
Explore further
Broader topics and technologies where MPTCP plays a role.
Defining Specifications
3GPP specifications that define or reference MPTCP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 24.193 vj50 | ATSSS Procedures Specification | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 28.552 vk10 | 5G Performance Management Measurements | Rel-20 |
| TS 29.244 vj40 | PFCP Specification for Control/User Plane Separation | Rel-19 |
| TS 29.512 vj40 | 5G Session Management Policy Control Service | Rel-19 |
| TS 32.255 vk10 | Telecom Management; Charging for 5G Data Connectivity | Rel-20 |