• State Verified Answer
  • Replies 6 replies
  • Subscribers 69 subscribers
  • Views 7866 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 128507
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

How different is a Mesh packet from BLE advertising packet?

Mitch996

Hi, I want to confirm if the Mesh packet is a "special" form of advertising packet or it is completely different, i.e. all the headers and addresses etc are changed.

By reading relevant document I get the impression that the 2 are completely different - instead of a packet which is "embedded" inside the payload of an advertising packet, or a packet which alters the fields of an advertising packet to different values but preserved all the formats for an advertising packet.

This means it could be extremely problematic if I want to adopt it to android, which offers very limited capability for me to customize what packet it sends out (with the latest android release that could be a different story).

Any insight?

Parents
  • 0

    Hi Mitch,

    my interpretation of the Bluetooth Mesh Profile Specification is that is a standard non-connectable and non-scannable undirected advertising packet with the AD type is set to "Mesh Message", see screenshot below.

    image description

    Not all smartphones will be able to support the Advertisement Bearer(the Mesh Message AD type might not be an option available in the stack), but the Bluetooth Mesh also specifies a GATT bearer, which essentially allows you to tunnel mesh packets through a regular BLE connection.

    I recommend that you take a look at the GATT Bearer section and the GATT Proxy Service sections in the Bluetooth Mesh Profile, available here.

    Best regards

    Bjørn

  • 0 in reply to bjorn-spockeli

    @bjorn-spockeli Thank you for the detailed answer! Regarding question #2, I think since the softdevice with both provisioner boards and provisionee boards are the same, the role-switching could be completed with some de-initialization and re-initializations.

    Nevertheless, one last thing, let's say I have a net work of as much as 100 nodes, and I'm relying on the board (the nrf52 series chip) to do the provisioning. Will it be too much workload for the chip? Can it handle the situation? I know the nrf52 chip usese cortex M4 and can run up to 64Mhz but I still wanna be certain.

    Edit: all information regarding the network of course, will be stored in the tablet, not in the board.

Reply
  • 0 in reply to bjorn-spockeli

    @bjorn-spockeli Thank you for the detailed answer! Regarding question #2, I think since the softdevice with both provisioner boards and provisionee boards are the same, the role-switching could be completed with some de-initialization and re-initializations.

    Nevertheless, one last thing, let's say I have a net work of as much as 100 nodes, and I'm relying on the board (the nrf52 series chip) to do the provisioning. Will it be too much workload for the chip? Can it handle the situation? I know the nrf52 chip usese cortex M4 and can run up to 64Mhz but I still wanna be certain.

    Edit: all information regarding the network of course, will be stored in the tablet, not in the board.

Children
No Data
Related