Multiprotocol BLE/Thread

[Alain]

Hello,

I have read with a lot of interest the documentation associated to the "multiprotocol support" associated to the nRF5 SDK for Thread v0.10.0. As far as I understood, to show the behaviour of the "dynamic multiprotocol (BLE/Thread)" mode, you have an example where you have a board Client MTD which support BLE and Thread. This Client is able to receive BLE requests from a phone and is also able to send a COAP request to a Server. It uses time slicing to support both protocol in parallel.

My question is : a) In this example, does the Server supports also "dual mode" (BLE/Thread) or only Thread ? As far as I understood, in your example, the Server is only running the Thread stack. is it correct ?

b) Can this kind of application be performed also with a Server and supporting BLE and Thread using time slicing as done on the Client part ? If so how can we sure that the server receives the COAP request send by the Client? The first COAP request send by the Client is usually multicast of type Non Confirmable, and so it may happen that when the Client send this request to the Server, if this server is doing BLE activity, it may never receive this request...Is this assumption correct ?

Thanks a lot for your clarifications,

[Alain]

Thanks a lot for your response.

In the example "BLE UART and Thread MTD CoAP Client Example" you need two nRF52840 boards. After reading your doc, it seems that both boards doesn't use the same firmware. The client (board 1) has a firmware which support BLE and Thread while the server (board 2) supports only Thread. Is it correct ? Is it possible to have the same kind of application with the Server supporting concurrently BLE and Thread and not only Thread. Thanks a lot, Best Regards,