Sending 10 KB over a link built for 20 bytes
A BLE write carries about 20 bytes by default. Our payloads were around 10 KB. Here is the fragmentation layer that bridges the two.
Surendra — Tejvon
Senior Android & BLE Engineer
Bluetooth Low Energy was designed for small readings: a heart rate, a temperature, a switch state. By default a single write carries about 20 bytes of payload. On a connected hardware project we worked on, the app and the device had to exchange payloads of around 10 KB.
The first step is to negotiate a larger MTU, the maximum size of one packet. That helps, but you cannot rely on it. Different phones and devices agree on different sizes, and some stay close to the minimum. So the protocol has to work at any MTU and simply go faster when a larger one is available.
We built a fragmentation and reassembly layer. The sender splits a payload into chunks sized to the negotiated MTU, with a small header on each so the receiver knows the order and when the message is complete. The receiver collects the chunks, rebuilds the payload and only then hands it to the rest of the app.
Two details matter more than the splitting itself. Chunks must be written one at a time through a queue, because BLE stacks drop writes that overlap. And the rebuilt payload must be verified with a checksum before anyone trusts it, because a single missing chunk produces data that looks valid and is not.
The rest of the app never sees any of this. It sends a message and receives a message. Keeping fragmentation in one layer meant we could tune chunk sizes and timing later without touching a single feature.
Topics
Working on a similar challenge?
Let's discuss the architecture before you build.
BLE system design, OTA reliability, and connected product engineering — this is what TEJVON does every day.
Book a Technical Consultation