the topogoly of mesh

[Jerry]

Hi

As we know, the mesh network is contained of a number of nodes, so, if we want to get the message of the nodes on the network , i think the node which is connected with the phone will stay in a heavy traffic, and the message will lose, or delay, because all the message need to send to the phone will through this node. Have Nordic find a solution of this?

[ovrebekk]

Hi Zain

The solution to this is simply to make sure that the connection interval for the phone connection is large enough, so that it will not impact the mesh operation. As an example, if you use a connection interval of 100ms or more then the impact should be very small.

Best regards
Torbjørn

[Jerry]

OK，but i also want to know whether the node which is connected the phone can collect all the data from the network or not? Such as when i use the phone to get all the node's name and(or) state.

[ovrebekk]

Hi Zain

That should not be a problem, as you have a much more reliable and consistent link through a GATT connection than what you get with BLE mesh (in other words, I expect the mesh to be the bottle neck before the phone link).

Assuming the phone supports it you can use the data length extension feature of Bluetooth 4.2 to send large packets between the phone and the relay node, without impacting the mesh too much.

Best regards

[Jerry]

Does the Nordic mesh SDK supports the Bluetooth 4.2? I think the mesh is based for Bluetooth 4.0, isn't it?

[ovrebekk]

Bluetooth 4.2 is backwards compatible with Bluetooth 4.0, so anything running on 4.0 should run on 4.2 as well.

It is true that Bluetooth mesh only requires Bluetooth 4.0 support. This allows BT mesh to run also on older BLE systems that might not have support for Bluetooth 4.2 or 5.

Best regards