<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bulk data transfer Bluetooth</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/37252/bulk-data-transfer-bluetooth</link><description>I&amp;#39;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</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Aug 2018 14:09:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/37252/bulk-data-transfer-bluetooth" /><item><title>RE: Bulk data transfer Bluetooth</title><link>https://devzone.nordicsemi.com/thread/143399?ContentTypeID=1</link><pubDate>Wed, 08 Aug 2018 14:09:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec5590dd-91af-468f-bea2-319adb09327a</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;I spoke to an OTS guy.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bulk data transfer Bluetooth</title><link>https://devzone.nordicsemi.com/thread/143388?ContentTypeID=1</link><pubDate>Wed, 08 Aug 2018 13:48:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89754f03-c79b-4cec-ac70-db8022ae4c35</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I see that there is an OTS example in SDK15.&lt;/p&gt;
&lt;p&gt;SDK\examples\ble_peripheral\experimental\ble_app_ots&lt;/p&gt;
&lt;p&gt;SDK\examples\ble_central\experipmental\ble_app_ots_c&lt;/p&gt;
&lt;p&gt;The example is also described &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Fble_sdk_app_ots.html"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I haven&amp;#39;t studied how the OTS service works in detail (you can find it &lt;a href="https://www.bluetooth.com/specifications/gatt/viewer?attributeXmlFile=org.bluetooth.service.object_transfer.xml"&gt;here&lt;/a&gt;). However, I see that the OTS service in the SDK does not follow the spec yet (&lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Fservice_object_transfer_client.html"&gt;see here&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;I believe you would need an app to use OTS on a phone, although I haven&amp;#39;t tried it. As mentioned, our OTS implementation is not following the spec yet. I wasn&amp;#39;t able to connect to it with anything else than the central OTS example.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>