Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Nordic Bluetooth Mesh compared to Bluetooth Specification

Hello, can  you say me:

1) which Stack parts in Mesh SDK: nrf5_SDK_for_Mesh_v2.0.1  are implemented in harmony with Bluetooth Mesh Profile Specification and which are not ?

2) Why are you using Time-slot API ?  

3) Which part from BLE SDK do you use in Mesh SDK ?

4) Do the Nodes with Relay feature have to be ON all the time or are there any  possibilities to use "Time slots" to save energy . Are there another energy saving features despite low power node to make the whole mesh as low energy as possible ?

  • Hi,

    1) The nRF5 SDK for Mesh v2.0.1 is a qualified Bluetooth Mesh stack. The optional additional Nordic Advertiser Extensions (Instaburst) feature is not, and so if you enable that one you will have a stack that is not qualified.

    2) We use the time-slot API of the SoftDevice so that you can run the Bluetooth Mesh ADV bearer (which does not rely on the SoftDevice) concurrently with BLE.

    3) The dependency on the nRF5 SDK is mostly for the SoftDevice, and for providing libraries and drivers that you can use for your application.

    4) The Relay nodes should be on all the time, that is the purpose of that role in Bluetooth Mesh. In addition to Friend/Low Power Node (which is a feature to come in a later release of our nRF5 SDK for Mesh) you can use the proxy feature (present in nRF5 SDK for Mesh v2.0.1). That way a node can join over traditional BLE. (This is basically what the friendship feature does. Depending on your time frame you may want to wait for friendship support in the nRF5 SDK for Mesh, so that you can use a Low Power Node.)

    Regards,
    Terje

  • Thank you for the fast answer. Regarding point 2:

    Do I undestand it correct ?

    Mesh-Bearer consist of two parts:
    Mesh ADV bearer
    Mesh GATT bearer use Proxy protocol so a BLE connection can  be established.
    And you also have concurrently the SoftDevice (BLE Stack) .
    But in the past you hadn‘t this proxy feature thats why your used SoftDevice?
    Will you keep the SoftDevice in the future ?

    Best Regards,

    Andreas

  • Hi,

    Almost correct.

    The SoftDevice is there both for concurrent BLE and for GATT bearer. Yes, it will stay.

    Regards,
    Terje

Related