Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
6 years, 8 months ago.
Any plans to release Mesh stack compatible to BT SIG Mesh specification?
Hi,
BT SIG released a specification covering BLE MESH in July 2017. Nordic and other vendors of BT chips have started distributing SW stack compatible to the specification. Are any plans to include implementation of BLE Mesh into mbed eco-system?
One more question: the specification is about "broadcasting" type of mesh, thus it works over three BT broadcast channels. The specification states that only 11 bytes of the payload are allowed - that is done to be compatible with BT 4.2. On another hand, BT 5.0 offers extended advertising where payload size can be much larger. As a user, I would like to have BLE Mesh which is compliant to BT SIG Mesh specification but with an ability to use extended functionality proposed by BT 5.0.
Thanks in advance!
Question relating to:
1 Answer
6 years, 8 months ago.
Hi Andrey,
There is no plan for Bluetooth mesh integration at the moment however it is more than likely that this feature will be part of the mbed OS BLE offer.
Quote:
One more question: the specification is about "broadcasting" type of mesh, thus it works over three BT broadcast channels. The specification states that only 11 bytes of the payload are allowed - that is done to be compatible with BT 4.2.
More than 11 bytes of useful payload are allowed in a packet, indeed it can go up to 384 bytes. However it is true that the maximum PDU for an unsegmented packet is 11 bytes. If a PDU is larger than that (or if it needs acknowledgement) then it has to be segmented into multiple mesh network packet. The segmentation/reassembly process is handled by the lower transport layer. As a user you won't see it.
Quote:
On another hand, BT 5.0 offers extended advertising where payload size can be much larger. As a user, I would like to have BLE Mesh which is compliant to BT SIG Mesh specification but with an ability to use extended functionality proposed by BT 5.0.
As soon as you start using extended advertising offered by Bluetooth 5, 4.x nodes are out of the game and cannot relay the data to other nodes or receive extended advertising.
It would be an option if the Bluetooth mesh wasn't a flood mesh network and nodes were keeping track of other nodes in a routing table but it is not the case.