Max size of data to send from one node to other ble mesh

RE: Max size of data to send from one node to other ble mesh

eric_paca — Thu, 22 Nov 2018 13:45:20 GMT

Hello leonwj,

Why is it even not feasible to send over multiple messages ?

Regards.

RE: Max size of data to send from one node to other ble mesh

Pooja — Fri, 06 Apr 2018 05:25:03 GMT

Thanks for your response.

RE: Max size of data to send from one node to other ble mesh

Thomas Stenersen — Thu, 05 Apr 2018 16:13:58 GMT

Hi Pooja,

As leonwj says, the largest single segment packet in Bluetooth Mesh v1.0 is 15 bytes, but that is not including the opcode (1-3 bytes) and application layer MIC (Message Integrity Check, sometimes known as Message Authentication Check) of 4 bytes. Both are mandatory for sending access layer data. So, the maximum effective application payload is 10 bytes. Unfortunately 1 and 2 byte opcodes are reserved for Bluetooth SIG models, so for your custom data, you'd need to resort to 3 byte opcode. In all, that reduction in data size isn't a lot compared to the 8192 bytes you want to send. With segmented messages, the maximum packet size in Bluetooth Mesh v1.0 is 384 bytes, remove 4 for the MIC and 3 for your vendor specific opcode and you're left with 377 bytes.

I would highly recommend you to consider if you really need to flood all of this data across the network or if it is possible to redesign your system to, e.g., do more local processing of the data or send delta updates.

You can read more about packet sizes, opcodes, and much more in the surprisingly easy to read Mesh Profile specification: www.bluetooth.com/.../mesh-specifications

Hope this helps,

Thomas

RE: Max size of data to send from one node to other ble mesh

Thomas Stenersen — Thu, 05 Apr 2018 16:06:26 GMT

The Instaburst feature is not dependent on any particular SoftDevice :) In the nRF5 SDK for Mesh we use a separate advertiser that's running in a SoftDevice timeslot. Also, the SoftDevice version 6 is included in the latest SDK version 15: developer.nordicsemi.com/.../

RE: Max size of data to send from one node to other ble mesh

Pooja — Fri, 30 Mar 2018 07:09:11 GMT

But Nordic Instaburst feature extension requires soft device version 6 and which is not yet released. So i am not able to use this feature. When nordic will release soft device as well as mesh sdk v1.1 ? Or there is any other solution for this?

RE: Max size of data to send from one node to other ble mesh

leonwj — Thu, 29 Mar 2018 12:17:05 GMT

You could look into the Nordic Instaburst feature extension to see what mileage that gives you.

RE: Max size of data to send from one node to other ble mesh

Pooja — Thu, 29 Mar 2018 07:19:54 GMT

Thanks for your response, 8192 size is only of one axis i have to send data of 3 axis i.e total data size is 24576. how can i manage to send that much data? It is possible to extend the payload size?

RE: Max size of data to send from one node to other ble mesh

leonwj — Thu, 29 Mar 2018 06:29:41 GMT

hello Pooja,

Bluetooth Mesh packet sizes are 15 bytes for unsegmented messages (unack'd/unreliable), however, it is also possible to send a segmented/reliable message which can consist of 12 bytes per packet (3 byte packet overhead for segmentation) with a 32 segment max, which would yield a 384 byte total message size. Obviously, segmented messages are much slower than unsegmented due to the required ack'd response from the receiver. It is not possible to send 8KBs in a single packet or even feasible to send over multiple messages. You could look into the Nordic Instaburst feature extension to see what mileage that gives you.

You should note that Bluetooth mesh in its current version (v1.0) is primarily targeted at command/control type applications and therefore the concept of flooding 8192 bytes across the mesh is not a primary or expectant use case. Hopefully Mesh v1.1 will deliver an additional bearer layer which incorporates advertising extensions and additional throughput enhancements as part of the standard but that spec is still under development with no set delivery date.

Regards,