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?

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
  • 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

    1. Yes, from the tablet side you'll just see the GATT Proxy Service and you'll write to and read its characteristics. The GATT Proxy Service is a standardized service, so you'll just have to add the service and the conversion from the GATT to ADV bearer is done by the service.
    2. Yes, the tablet can provision in a node via the GATT bearer and configure it as a proxy node. The tablet(provisioner) can then use the Remote provisioning feature of the Nordic Bluetooth mesh to relay provisioning messages to other devices that should be provisioned into the mesh.
Reply
    1. Yes, from the tablet side you'll just see the GATT Proxy Service and you'll write to and read its characteristics. The GATT Proxy Service is a standardized service, so you'll just have to add the service and the conversion from the GATT to ADV bearer is done by the service.
    2. Yes, the tablet can provision in a node via the GATT bearer and configure it as a proxy node. The tablet(provisioner) can then use the Remote provisioning feature of the Nordic Bluetooth mesh to relay provisioning messages to other devices that should be provisioned into the mesh.
Children
No Data
Related