DLE

Data Length Extension (DLE)

DLE (Data Length Extension) is a Bluetooth 4.2 feature that increases the maximum Link Layer PDU payload from 27 bytes to 251 bytes. This single change can improve BLE data throughput by up to 2.5x without any changes to the application-level protocol.

Why DLE Matters

In Bluetooth 4.0/4.1, every Link Layer PDU carried at most 27 bytes of payload (plus 4 bytes MIC if encrypted). With a typical Connection Interval of 30 ms and one packet per event, effective throughput was limited to roughly 6-7 kbps. The overhead of L2CAP and ATT headers further reduced usable bandwidth.

DLE increases the payload capacity to 251 bytes per PDU. Combined with multiple packets per Connection Event, this dramatically improves throughput. A single connection event with DLE can transfer over 10x more data than without it.

Negotiation

DLE is negotiated after connection establishment using the LE_Set_Data_Length HCI command. Both devices exchange their supported maximum TX and RX payload sizes, and the link uses the minimum of both devices' capabilities. This negotiation is automatic in most BLE stacks, but application developers can trigger it explicitly for optimal performance.

DLE vs MTU

DLE and MTU operate at different layers and should both be maximized for best throughput:

When MTU exceeds the DLE size, L2CAP segments the ATT payload across multiple Link Layer PDUs. When DLE is large enough to carry the full ATT payload, no segmentation is needed, reducing overhead.

Throughput Impact

Hardware Support

DLE is supported by virtually all BLE chips shipping since 2016, including the nRF52832, nRF52840, ESP32, and CC2642R. It is automatically enabled in most SDKs but should be verified via HCI log analysis when debugging throughput issues.