How To Configure And Use Subnet For Mesh 3.10

[listenYes]

Hi

I want to create this example:

A major network,it include the subnet A and subnet B.

One node X,it belong to subnet A and subnet B.

If the node X was a function node(such as temperature or lux sensor node).It should sending temperature message to both subnet A and subnet B.

If the node X was a border router node(Temporarily called this name).It should transmission all message for subnet A and subnet B.

such as:The first floor was subnet A(it have OnOff node O),the second floor was subnet B(it have light node L),node X is between the first floor and the second floor.

Now,if I wan to control the node L,but my location was first floor.The APP connect the node O(PB_GATT),the control message from subnet A to subnet B,it relay through the node X.

I have the following questions:

1.How to create subnet for one network?

2.The subnet A adn subnet B node,that would unicast address can  overlap?(such as subnet A&B it both have unicast address is 0x0001 node)

3.How to configure the node X.

4.When the node X was border router node,it how to transmission message.

5.How to choose the subnet,when sending message to a subnet.

[Bjørn Kvaale]

1) I would strongly recommend taking a look at this tutorial, which explains how you can setup a network where nodes have the same network key (are a part of the same mesh network & have access to the network layer of the mesh stack), but are bound to different application keys. That way, nodes that are bound to one application key are able to send messages to each other via the access layer, but are not able to receive messages by nodes that are bound to a different application key. You should be able to do something similar via nRF Mesh.

Otherwise, it should also be possible to have different network keys for each subnetwork so that the two networks do not have access to each other's network key layers too. This would most likely involve some changes needed to the nRF Mesh code or the interactive pyaci code. Take a look at section 2.2.1 network & subnets from the mesh profile spec for more information.

2) No, each node will be given a different unicast address by the provisioner.

3) The gateway specification is not part of the Bluetooth Mesh specification unfortunately. You will need to figure this part out yourself. The border router you are referring to is part of the Thread specification, not the Bluetooth Mesh specification.

4) As stated in 3, the gateway is not part of the Mesh spec. You will need to figure this out yourself unfortunately.

5) I do not understand the question unfortunately. Could you please elaborate?