Reasons of having Models and elements in Nrf Mesh Protocol

[bivay]

I have one doubt that why there is elements or models in Bluetooth, it can be simple as sending messages and then translate them into useful work, in this single element and model needed, no need to worry about future expansion in code side if it provisioned or not.

I searched many time for this reason but didn't get answer. I asked Bluettoth SIG about it, but didn't get response from there.

How models are better than one single model with only trans receive of messages and then use message as need.

I didn't means that Models are wrong or anything else, and I know if it is standard, then there must be reason for it. I want to know that reason.

Please if anybody have knowledge about logic behind models, then please explain.

Thank You

Bivay

[tesc]

Hi,

Compatibility is important for instance if you make switches, or if you make light bulbs. In order for the switch to toggle the light bulb, they must both understand the same messages. The concept of "Models" ensures this. It lets the provisioner configure devices from different manufacturers, so that they communicate with each other (using the same model).

On the one hand, making your own protocol on top of a simple model should be OK. It means you add an extra "abstraction layer" on top of what is described in the Bluetooth mesh specification, but there is nothing preventing you from doing so.

On the other hand, implementing what you need directly as models would be more idiomatic use of Bluetooth mesh, and you would likely avoid some overhead.

In the end, the choice is yours.

Regards,
Terje

[bivay]

Thanks for great explanation.