Hello, as the title suggest, I want to implement an iPad/iPhone mesh provisioner, and this is my general idea:
- Build an App which sends and receives customized advertising packets, in accordance with the BLE Mesh specs and with reference to nordicsemi's provisioner example.
Now this is easier said than done, but first thing first, I need to get some confusion out of the way, so here are a few questions that I hope I can find answers, you are free to contribute even if you don't know for 100% sure:
-
Based on my doing the homework (reading tech docs and the example codes), all mesh date sent over the air using advertising packets are still... advertising packets, they are not so heavily customized to the point that a lot of overhead for advertising packets has been changed, is this judgement correct? (This above question is the most important one, because iOS APIs may not support a high level of customization in advertising packets)
-
If 1 is true, does that mean there should be little or no pitfalls in transmitting customized advertisement packets using high level APIs? Because after all, I'm just sending advertisement packets with customized payload. This one may be very difficult to answer but please feel free to share your expert opinion or an educated guess.
-
It appears that provisioning is done in the
nrf_mesh_process()
function, (I could be mistaken), instead of a seperate process. Does that mean I must go great lengths and extract the provisioning part of nrf_mesh_process() and translate it to the iOS platform? Or the "extraction" isn't going to be that difficult as provisioning steps are just callbacks etc. specifically designed for provisioning function, relatively isolated from the rest of the code?
4 Considering 3, are there any existing example codes/github projects out there which I can reference? Because coding all the provisioning steps alone can be quite daunting a task (again, I could be wrong). I've searched for it but there is nothing directly related to this application.
Any suggestions?
