RF Wireless World

Browse articles, tutorials, tools, and vendors.

Bluetooth MTU vs MPS: Key Differences & Optimization

By RF Wireless Expert Team

To optimize your data throughput, you need to understand how the Bluetooth Logical Link Control and Adaptation Protocol (L2CAP) handles data. Specifically, you need to understand two critical parameters viz. MTU (Maximum Transmission Unit) and MPS (Maximum PDU Payload Size).

While they sound similar, they serve entirely different purposes in the Bluetooth protocol stack. Here is exactly how they work, how they differ and how you can use them to optimize your application.

What is MTU (Maximum Transmission Unit)?

In the Bluetooth specification, MTU refers to the maximum size of a Service Data Unit (SDU) that the upper layer application can accept.

Think of the MTU as the maximum size of the complete “box” of data your application wants to hand off to the Bluetooth stack, or the maximum size of the box it is willing to receive from the remote device.

Key facts of MTU:

  • It is Asymmetric and Informational: MTU isn’t strictly negotiated. Instead, each device independently declares the maximum MTU it can receive.
  • Minimum Requirements: All Bluetooth Low Energy (LE) implementations must support a minimum MTU of 23 bytes (octets), while Basic Rate/Enhanced Data Rate (BR/EDR) must support at least 48 bytes.
  • Exceeding the Limit: If a device attempts to send an SDU that is larger than the receiver’s declared MTU, the receiver will abruptly disconnect the channel.

What is MPS (Maximum PDU Payload Size)?

MPS operates one layer deeper. It defines the maximum payload size of a Protocol Data Unit (PDU) that the L2CAP layer is capable of accepting.

If the MTU is the complete “box” of data from the application, the MPS determines the size of the “shipping envelopes” that L2CAP uses to actually send that data over the air.

Key facts of MPS:

  • Segmentation: If your application tries to send a packet (SDU) that is larger than the MPS, L2CAP performs a process called Segmentation and Reassembly (SAR). It chops the large SDU into smaller, MPS sized PDU segments, transmits them and the receiving device stitches them back together.
  • Limits: Like MTU, the absolute minimum MPS for LE connections is 23 bytes, but it can theoretically be configured up to 65,533 bytes.
  • Basic Mode Rule: If your connection is using Basic L2CAP mode (where segmentation is not used), the MTU and MPS are forced to be the exact same value.

How MTU and MPS Work Together (Segmentation)

To visualize how these two parameters interact, imagine you want to send a 500 byte data payload from Device A to Device B.

  1. Device B has told Device A: “My MTU is 600 bytes, and my MPS is 200 bytes.”
  2. Because your 500-byte payload is smaller than Device B’s 600-byte MTU, the application layer accepts the data.
  3. However, the data must pass through the L2CAP layer, which enforces the 200-byte MPS limit.
  4. The L2CAP layer breaks your 500-byte SDU into three separate PDUs:
    • PDU 1: 200 bytes of payload (marked as a “Start” segment)
    • PDU 2: 200 bytes of payload (marked as a “Continuation” segment)
    • PDU 3: 100 bytes of payload (marked as an “End” segment)
  5. Device B receives the three PDUs, reassembles them back into the 500 byte SDU, and hands it to the upper layer application.

Summary: The Major Differences

Following table summarize differences between MTU and MPS used in bluetooth standard.

FeatureMTU (Maximum Transmission Unit)MPS (Maximum PDU Payload Size)
Associated Data TypeSDU (Service Data Unit)PDU (Protocol Data Unit)
Protocol LayerUpper Layer / Application levelL2CAP Layer / Protocol level
What it representsThe maximum size of the complete data payload the app can handle.The maximum size of the individual chunks of data sent over the air.
Trigger for SegmentationN/A (If data > MTU, the channel disconnects).If data > MPS, the L2CAP layer chops it into smaller pieces.
Basic L2CAP ModeEquals the MPS.Equals the MTU.

How to Optimize Throughput Using MTU and MPS

If you want to maximize your data transfer speeds over Bluetooth LE, you need to minimize protocol overhead. Every time L2CAP segments an SDU into multiple PDUs, it has to attach header information to every single segment.

The Optimization Strategy:

To get the highest throughput possible, you should configure your connection so that segmentation rarely happens.

  1. Request a larger MTU so your application can send bigger blocks of data at once.
  2. Negotiate an MPS that is large enough to handle your MTU without needing to slice it into tiny pieces.
  3. Align these values with the underlying Link Layer capabilities (like the Data Length Extension feature in Bluetooth 4.2+) so that your L2CAP PDUs fit perfectly into the radio packets without requiring further fragmentation at the hardware level.

By understanding the difference between the application’s data limit (MTU) and the protocol’s chunk limit (MPS), you can fine tune your Bluetooth implementation for blazing fast, reliable data transfers.

References & Further Reading

  1. Bluetooth SIG : Bluetooth Core Specification Version 6.3, May 5, 2026.
  2. Bluetooth SIG : Bluetooth Core Specification change history
  3. Bluetooth SIG : Bluetooth Technology Overview

Continue Learning Bluetooth Basic Concepts

Continue Learning Bluetooth Technology

Compare Bluetooth With Other Technologies

Explore Deep Insight Bluetooth Technology

Keep Reading

Related Posts