Description
The Maximum Transmission Unit (MTU) is a key parameter in data communication that defines the maximum size, in bytes, of a protocol data unit (PDU) that can be transmitted in a single frame over a network link without being fragmented. In the context of 3GPP systems, MTU applies to various layers, including the IP layer (e.g., for user data packets) and link layers (e.g., for Ethernet or cellular radio bearers). It is typically measured at the IP layer, encompassing the IP header and payload, but excluding lower-layer headers like Ethernet or PPP. The MTU value is determined by the underlying network technology; for example, Ethernet commonly uses 1500 bytes, while 3GPP radio bearers may have different MTUs based on configuration and radio conditions. When a packet exceeds the MTU of a link, it must be fragmented into smaller pieces, each with its own IP header, which are reassembled at the destination. Fragmentation, however, can lead to inefficiencies due to header overhead, increased processing, and potential packet loss if fragments are dropped. To avoid fragmentation, protocols like Path MTU Discovery (PMTUD) are used to determine the smallest MTU along a path and adjust packet sizes accordingly. In 3GPP architectures, MTU considerations are critical for interfaces like S1-U (between eNB and SGW), N3 (between gNB and UPF in 5G), and Gi/SGi (between PGW/UPF and external networks). The network may enforce MTU limits via QoS parameters or bearer configurations, and devices must adapt to these constraints. MTU also impacts higher-layer protocols; for instance, TCP uses the Maximum Segment Size (MSS), derived from MTU, to optimize segment sizes and avoid fragmentation. In 5G, with support for enhanced mobile broadband (eMBB) and massive IoT, MTU settings can vary per network slice or QoS flow to balance efficiency and latency for different services. Proper MTU management ensures efficient bandwidth utilization, reduces latency, and maintains service quality across heterogeneous networks.
Purpose & Motivation
MTU exists as a fundamental networking concept to optimize data transmission efficiency and reliability across diverse network technologies with varying frame size limitations. Historically, as networks evolved from simple point-to-point links to complex internetworks, the need arose to define a maximum packet size that each link could handle without performance degradation. Without MTU, packets might be too large for certain links, causing fragmentation that increases overhead, processing load, and the risk of packet loss if any fragment is missing. In 3GPP systems, MTU is particularly important due to the resource-constrained nature of wireless links, where radio resources are scarce and must be used efficiently. Early cellular data services (e.g., GPRS) had limited MTUs, but with the advent of 3G, 4G LTE, and 5G, MTU sizes have increased to support higher throughput and lower latency applications like video streaming and real-time gaming. The concept addresses limitations of one-size-fits-all packet sizes by allowing networks to advertise their MTU capabilities, enabling endpoints to adapt dynamically. This is crucial for seamless interworking between cellular networks and fixed networks (e.g., Ethernet, DSL), ensuring end-to-end performance. MTU also plays a role in supporting new services in 5G, such as network slicing, where different slices may have distinct MTU requirements based on their use cases (e.g., large MTUs for eMBB, smaller ones for IoT). Overall, MTU solves problems related to fragmentation, interoperability, and resource optimization, making it a cornerstone of IP-based communication in 3GPP and beyond.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (19 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-15.
In Release 15, the MTU-related changes included a correction to the official name of the `maximumDataBurstVolume` attribute to ensure consistency. Furthermore, the release introduced clarifications for the authorization of the Maximum Packet Loss Rate and extended the maximum bitrate parameter within the QoS (Quality of Service) information element.
In Release 16, the MTU-related enhancements included clarifying the PCF behavior to honor UE-provided maximum packet filter support and introducing support for Maximum Supported Bandwidth and Minimum Desired Bandwidth parameters. Furthermore, corrections were made to the maximum length of the Quality of Service IE, and the maximum value for the MDBV (Maximum Data Burst Volume) was increased.
- Clarification of PCF behaviour to honor UE provided maximum packet filter support TS 29.512CR0491
- Support of Maximum Supported Bandwidth and Minimum Desired Bandwidth TS 29.514CR0159
- Correciton of the erroneous maximum length of the Quality of service IE TS 24.008CR3207
- Maximum size of EPMS/BMS messages TS 24.539CR0011
- Increasing the maximum MDBV value TS 29.512CR0345
In Release 17, the MTU (Maximum Transmission Unit) function was enhanced to explicitly support Ethernet and Unstructured PDU session types through amendments to the +CGDCONT and +CGCONTRDP AT commands. This update provided a standardized mechanism for configuring and reporting the MTU parameter specific to these session types, complementing existing bearer management procedures. Additionally, corrections were made to the description of the maximum number of packet filters within a Traffic Flow Template (TFT) and to the procedure for maximum allowed user plane latency.
- Correction on the number of the maximum size packet filters in TFT TS 24.008CR3267
- Update of C5GQOS for Subscribed maximum bit rate TS 27.007CR0714
- +CGDCONT and +CGCONTRDP amendments to support MTU for Ethernet/ unstructured PDU session TS 27.007CR0747
- Correction to the procedure of maximum allowed user plane latency TS 29.513CR0355
In Release 18, enhancements to the MTU function included network-assisted decisions for end-to-end redundant transmission via NWDAF and clarifications for configuring the maximum group data rate. Furthermore, corrections were specified for the conditions governing the reporting of the MTU size. These updates aimed to improve the control and reliability of data bearer transmissions.
- Support of Uplink Downlink transmission coordination to meet RT latency requirement TS 29.512CR1073
- Maximum Group Data Rate control TS 29.512CR1187
- NWDAF assisted decision on E2E redundant transmission TS 29.513CR0455
- Support of Uplink Downlink transmission coordination to meet RT latency requirement TS 29.514CR0505
- Clarification on configuration of maximum group data rate TS 29.512CR1133
- Corrections to the conditions for reporting of the MTU size TS 29.513CR0553
In Release 19, a correction was made regarding the maximum number of references to QosMonitoringData. The release did not introduce new MTU-specific functions or capabilities, as the grounding context and provided change titles focus on other areas such as bearer definitions, power measurements, and radio resource procedures.
- Correction to the maximum number of reference to QosMonitoringData TS 29.512CR1425
Explore further
Broader topics and technologies where MTU plays a role.
Defining Specifications
3GPP specifications that define or reference MTU, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 22.827 vh10 | Study on Audio-Visual Service Production Stage 1 | Rel-17 |
| TS 23.060 vj00 | GPRS Service Description Stage 2 | Rel-19 |
| TS 24.008 vj50 | 3GPP TS 24008: Core Network Protocols | Rel-19 |
| TS 24.502 vj20 | 5G Core Access via Non-3GPP Networks; Stage 3 | Rel-19 |
| TS 24.539 vj30 | NW-TT Protocol Aspects | Rel-19 |
| TS 26.114 vj10 | IMS Multimedia Telephony Media Handling | Rel-19 |
| TS 26.142 vj00 | 3GPP TS 26.142: Dynamic and Interactive Multimedia Scenes (DIMS) | Rel-19 |
| TR 26.906 vj00 | HEVC Evaluation for 3GPP Services | Rel-19 |
| TR 26.926 vj00 | Traffic Models & Quality Evaluation for Media/XR in 5G | Rel-19 |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 |
| TR 26.948 vj00 | Video enhancements for 3GPP Multimedia Services | Rel-19 |
| TS 27.007 vj40 | AT Command Set for UE | Rel-19 |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 |
| TS 29.061 vj00 | Packet Domain Interworking for PLMN | Rel-19 |
| TS 29.161 vc00 | 3GPP-WLAN Interworking Requirements | Rel-12 |
| TS 29.512 vj40 | 5G Session Management Policy Control Service | Rel-19 |
| TS 29.513 vj40 | 5G PCC Signalling Flows & QoS Mapping | Rel-19 |
| TS 29.514 vj40 | 5G System; Policy Authorization Service; Stage 3 | Rel-19 |
| TR 37.901 vf10 | UE Application Layer Data Throughput Performance | Rel-15 |
| TR 38.825 vg00 | Study on NR Industrial IoT | Rel-16 |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 |