Hi,
for example:
Hi,
for example:
Hi,
The network layer will neither transmit nor relay messages that are addressed to a unicast address on the node itself. This includes messages originating on the same node, and it also holds for messages over the GATT bearer; messages will not be relayed if they are addressed to elements on the node itself.
Regards,
Terje
Hi,
The network layer will neither transmit nor relay messages that are addressed to a unicast address on the node itself. This includes messages originating on the same node, and it also holds for messages over the GATT bearer; messages will not be relayed if they are addressed to elements on the node itself.
Regards,
Terje
OK, got it, the messages that are addressed to a unicast address on the node itself will not be sent to the air.
But the messages that are addressed to a unicast address on the other node(target node) will be sent to the air and will be relayed by the other nodes(relay nodes) in the same mesh network, am I right?
Yes. It is implemented exactly as per specification. See: https://www.bluetooth.com/specifications/specs/html/?src=MshPRT_v1.1/out/en/index-en.html#UUID-e526affc-e131-135e-36bf-12c41f9ddff8
Hi,
ShawnL said:But the messages that are addressed to a unicast address on the other node(target node) will be sent to the air and will be relayed by the other nodes(relay nodes) in the same mesh network, am I right?
For the most part, yes.
There are other messages which could be held back, namely messages for connected GATT devices (if the node is a GATT proxy), and messages for LPNs in a current friendship (if the node is a Friend node). Such messages are delivered over GATT bearer in a connection event (for GATT proxy), or over ADV bearer in a poll event (for Friend).
For relays, those will also time out if TTL gets exhausted.
Apart from that, messages would be sent over-the-air.
Regards,
Terje
Very clear.
Thank you.