RE: Can a proxy node also be a controller node?

Hung Bui — Mon, 06 Nov 2017 15:26:00 GMT

No, not yet.

RE: Can a proxy node also be a controller node?

kren — Mon, 06 Nov 2017 07:10:29 GMT

Does nrf mesh v0.10 support proxy?

RE: Can a proxy node also be a controller node?

Hung Bui — Fri, 03 Nov 2017 12:03:52 GMT

Hi Michael,

At section 2.3.6 in the Mesh spec you can find the definition of client and server model, I think it's self explained:

Server model: A server model is composed of one or more states spanning one or more elements. The server model defines a set of mandatory messages that it can transmit or receive, the behavior required of the element when it transmits and receives such messages, and any additional behavior that occurs after messages are transmitted or received.

Client model: A client model defines a set of messages (both mandatory and optional) that a client uses to request, change, or consume corresponding server states, as defined by a server model. The client model does not have state.

A proxy node can be a client and server, yes. Note that client, and server are model, not node. And proxy is a role a node can support.

So there is no conflict here.

I think the way the server and client model was designed is that the server is very simple and only holds states. The client is the one trigger command and request data. So communication between 2 servers is not really what designed.

However, the application is free to use access layer to send data between node. So if you don't use the client server model the way they defined in spec, it's totally fine.