<?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>Best solution to BLE-enabled device as central and peripheral?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13689/best-solution-to-ble-enabled-device-as-central-and-peripheral</link><description>After seeing a few answers here (and elsewhere) which were very helpful to understanding the scope of my problem: 
 devzone.nordicsemi.com/.../ 
 forums.adafruit.com/viewtopic.php 
 devzone.nordicsemi.com/.../ 
 ...I&amp;#39;m curious if anyone has suggestions</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 May 2016 20:53:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13689/best-solution-to-ble-enabled-device-as-central-and-peripheral" /><item><title>RE: Best solution to BLE-enabled device as central and peripheral?</title><link>https://devzone.nordicsemi.com/thread/52318?ContentTypeID=1</link><pubDate>Mon, 09 May 2016 20:53:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c6e0689-e29e-47ab-80ae-2406660d09e5</guid><dc:creator>James Yu</dc:creator><description>&lt;p&gt;Yes that is correct based on your description of your application.&lt;/p&gt;
&lt;p&gt;The phone does not need to advertise, it just needs to discover and use the services on the smartwatch.&lt;/p&gt;
&lt;p&gt;As an example take a look at the Glucose service below:
&lt;a href="https://developer.bluetooth.org/gatt/services/Pages/ServiceViewer.aspx?u=org.bluetooth.service.glucose.xml"&gt;developer.bluetooth.org/.../ServiceViewer.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Pretend the smartwatch implements this service, then the smartwatch can send glucose measurements to the phone using the Glucose Measurement characteristic, and the phone can send data to the smartwatch using the Record Access Control Point characteristic.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best solution to BLE-enabled device as central and peripheral?</title><link>https://devzone.nordicsemi.com/thread/52316?ContentTypeID=1</link><pubDate>Mon, 09 May 2016 19:13:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1d09b22-cc41-46e3-b999-688b5189e275</guid><dc:creator>Ross Llewallyn</dc:creator><description>&lt;p&gt;So, if I were to summarize, the benefits afforded by getting a chip that can serve as both central and peripheral are not the ones I need. I can program the smart watch to use the service as the client? Or does the phone have to advertise it?&lt;/p&gt;
&lt;p&gt;I&amp;#39;m aware at this point we&amp;#39;re getting away from the original question, though. Thank you both for the replies.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best solution to BLE-enabled device as central and peripheral?</title><link>https://devzone.nordicsemi.com/thread/52317?ContentTypeID=1</link><pubDate>Mon, 09 May 2016 12:48:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31f8973c-4c3d-43cd-aec1-8a25d184e2da</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;What James says is true. In addition you should know that the GATT server / client capabilities is not linked directly to the Peripheral / Central roles. So a Peripheral can also be the Gatt Client while the Central is the Gatt Server. E.g. most ANCS applications.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best solution to BLE-enabled device as central and peripheral?</title><link>https://devzone.nordicsemi.com/thread/52319?ContentTypeID=1</link><pubDate>Fri, 06 May 2016 17:19:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:efd605cd-6a51-4b96-afee-7a8b22019cc5</guid><dc:creator>James Yu</dc:creator><description>&lt;p&gt;So if I understand correctly you have a smart watch that you want to communicate with a mobile phone.&lt;/p&gt;
&lt;p&gt;In this case it is sufficient for the smartwatch to be the peripheral and the phone to be the central all the time. The smartwatch can send notifications to the phone, and the phone can read and write to the smartwatch.&lt;/p&gt;
&lt;p&gt;Notifications from the phone can be achieved using writes, so there is really no need to reverse the roles.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>