Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Status of Object Transfer Service?

Hi, we are evaluating possibly using OTS in our product. We are currently on SDK 15.3.0 and when I look at the documentation:

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/service_object_transfer.html?cp=6_5_0_3_3_17

there is a warning "currently this module does not qualified to follow the Object Transfer specification."

I was hoping to get some clarity as to what that means, does that mean that the service is fully implemented but not formally qualified? Or does it mean that it is a work in progress with known missing functionality? In that case, what functionality is missing? What are the plans moving forward, it seems the text is the same for SDK 16.0.0?

Kind regards

Parents
  • After investigation, all the mandatory characteristics are present, but the main.c is not setting the object name (meaning it is empty) nor the object type UUID (since Bluetooth SIG has still not published them). 

    There is another deviation from the Object Transfer Service Specification, the example does not support security at all, but the specification mandates encryption. Should not very problematic, need to add the Peer Manager, by checking with another example using it (e.g. HRS or HID examples). 

    It otherwise seems to be compliant, at least for the server side.

Reply
  • After investigation, all the mandatory characteristics are present, but the main.c is not setting the object name (meaning it is empty) nor the object type UUID (since Bluetooth SIG has still not published them). 

    There is another deviation from the Object Transfer Service Specification, the example does not support security at all, but the specification mandates encryption. Should not very problematic, need to add the Peer Manager, by checking with another example using it (e.g. HRS or HID examples). 

    It otherwise seems to be compliant, at least for the server side.

Children
No Data
Related