This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bulk data transfer Bluetooth

I've looked at how other projects handle sending large amounts of data and they all use a derivative of the TX/RX scheme that is used in the image transfer demo. The Peripheral waits for a command on the RX characteristic and the notifies the Central on the TX characteristic. It seems like this is a wheel that every company needs to reinvent to add bulk data transfer to their design. Object Transfer Service (OTS ) seems to be a SIG compliant solution to this problem. Does OTS need to be implemented in the phone OS to work? Is the cost/benefit of using OTS not worth it? Is there a better solution than OTS? Am I missing something?

  • Hello,

    I see that there is an OTS example in SDK15.

    SDK\examples\ble_peripheral\experimental\ble_app_ots

    SDK\examples\ble_central\experipmental\ble_app_ots_c

    The example is also described here.

     

    I haven't studied how the OTS service works in detail (you can find it here). However, I see that the OTS service in the SDK does not follow the spec yet (see here).

    I believe you would need an app to use OTS on a phone, although I haven't tried it. As mentioned, our OTS implementation is not following the spec yet. I wasn't able to connect to it with anything else than the central OTS example.

    However, I would agree that it is unnecessary that everyone has to reinvent the wheel. I will talk to someone who has worked with the OTS example, and check what the plan for this is.

     

    Best regards,

    Edvin

  • I spoke to an OTS guy.

    The OTS service requires L2CAP connection oriented channels. Some phones, but not all supports this. Basically, the OTS service is not standard BLE, which is why the RX / TX scheme is used a lot.

     

    Best regards,

    Edvin

Related