iOS NRF mesh connection handling on app side

RE: iOS NRF mesh connection handling on app side

user79806 — Tue, 31 May 2022 13:03:54 GMT

Thanks a lot Aleksander.

I may contact again if I run into any issues

RE: iOS NRF mesh connection handling on app side

user3284 — Tue, 31 May 2022 13:00:21 GMT

We're working on mesh library in Kotlin with API much closer to the iOS version. But it most probably wont be ready this year, and will not be backwards compatible with the current Java version.

RE: iOS NRF mesh connection handling on app side

user3284 — Tue, 31 May 2022 12:58:57 GMT

Yes, it is possible, of course. The difference is, that when you're using GATT Proxy, the mesh data are sent over Mesh Proxy Service, while provisioning over Mesh Provisioning Service. But if you'll manage to implement it in a single class, that's ok.

Also, you may also set the MeshNetworkManager as your bearer's dataDelegate (so you'll no have to call `bearerDidReceiveData` method directly) and your bearer as manager's transmitter.

RE: iOS NRF mesh connection handling on app side

user79806 — Tue, 31 May 2022 12:51:35 GMT

Hi Aleksander,

Looks like ProxyProtocolHandler is exactly what I am looking for. Thanks a lot for that.

[quote userid="79806" url="~/f/nordic-q-a/88445/ios-nrf-mesh-connection-handling-on-app-side/370206#370206"]Also when starting provisioning it expects a provisioning bearer. Does it not use the MeshNetworkManager.transmitter in that case? [/quote]

I am guessing based on your response the answer to above is it does not use.

Is it possible to have a common bearer object that can be assigned to both MeshNetworkManager.transmitter and provision function. Bearer seems to be extension of Transmitter so I think that should be possible

I'm trying to bring the interface as close to android as possible

RE: iOS NRF mesh connection handling on app side

user3284 — Tue, 31 May 2022 12:33:13 GMT

The manager gives the whole packet to the transmitter and expects a whole packet when it is received. You have to do the segmentation and slit to MTU-size packets on your own, if you're using a custom bearer. You may use ProxyProtocolHandler which can split the data for you, or implement the same functionality on your own.

The PDU type is what you get from the manager (link) when sending data. You have to pass it to the ProxyProtocolHandler here. The same applies when you receive a packet - you get it from the handler and have to pass it to the manager.

When you're doing a provisioning, you have to pass the ProvisioningBearer to provision method. In this bearer object you need to implement sending and receiving data like for normal bearer. This time it is not split into a transmitter and a callback. You still can use ProxyProvisioningHandler class to help you with SAR.

RE: iOS NRF mesh connection handling on app side

user79806 — Tue, 31 May 2022 12:21:16 GMT

Hi Aleksander, thank you for a quick reply.

The links that you shared expect a pdu type. I haven't used something like that when working with android. Also it doesn't take mtu size in iOS case so how does it do segmentation?

Also when starting provisioning it expects a provisioning bearer. Does it not use the MeshNetworkManager.transmitter in that case?

RE: iOS NRF mesh connection handling on app side

user3284 — Tue, 31 May 2022 11:53:06 GMT

Hi,

In the iOS library you don't have to use GattBearer. The MeshNetworkManager requires settings a transmitter (link) object to any Transmitter (you may implement one on your own) and you need to call bearerDidReceivedData(_:ofType) when you receive the data for the library to process. Very similar mechanism.