<?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>Does Nordic Semiconductor have the hardware we need to realize our project?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/1558/does-nordic-semiconductor-have-the-hardware-we-need-to-realize-our-project</link><description>Hi, 
 we’re a group of students at NTNU in Trondheim doing a project regarding bike and pedestrian registration. So far we want to make a solution based on iBeacon and Bluetooth Low Energy (BLE) . This is what we have outlined: 
 
 Placing BLE modules</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 09 Feb 2014 13:16:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/1558/does-nordic-semiconductor-have-the-hardware-we-need-to-realize-our-project" /><item><title>RE: Does Nordic Semiconductor have the hardware we need to realize our project?</title><link>https://devzone.nordicsemi.com/thread/6889?ContentTypeID=1</link><pubDate>Sun, 09 Feb 2014 13:16:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:575e6cbf-a679-49fb-85e2-57a3a3ccc641</guid><dc:creator>Per Kjellsen</dc:creator><description>&lt;p&gt;Thanks for the very good and helpful answer. I guess we better give ourselves some homework exercises from now on. ;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does Nordic Semiconductor have the hardware we need to realize our project?</title><link>https://devzone.nordicsemi.com/thread/6888?ContentTypeID=1</link><pubDate>Sat, 08 Feb 2014 19:55:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:46ab6a96-1bc9-4687-8796-c9aa8cf6c783</guid><dc:creator>Janek Mann</dc:creator><description>&lt;p&gt;Sheesh, do your own homework won&amp;#39;t you? ;)&lt;/p&gt;
&lt;p&gt;Anyway, a few notes to get you started:
An iBeacon, strictly speaking, won&amp;#39;t know that it has been observed by the phone. It is continuously advertising its UUID and Major/Minor IDs and the phone will observe these advertisements without needing to communicate back to the iBeacon. So iBeacon won&amp;#39;t do what you want but regular BLE could (your app can stay in the background, be woken by iOS when your BLE module has been scanned, make connection to the BLE module and exchange its own identifier).&lt;/p&gt;
&lt;p&gt;Integrating a BLE module with a GPRS module is a non-trivial exercise. Nordic&amp;#39;s dev kits support BLE, obviously, but not GPRS so you&amp;#39;d have to look elsewhere for that.&lt;/p&gt;
&lt;p&gt;Have you considered inverting your system? It&amp;#39;s comparatively trivial for the app on the phone to make connection to your server and report the ids of the iBeacon it has ranged. This also would make it easier for the users to keep control over their own data, as you propose in point 5, and the BLE module side need never know (and can&amp;#39;t leak) the id of the user.&lt;/p&gt;
&lt;p&gt;Depending on your comfort level with embedded development, you could actually prototype the whole system using iOS devices (which can act as iBeacons, BLE device &amp;amp; host) before proceeding to an embedded implementation. The NRF51822 dev kits can act as iBeacons (see other posts on this forum) so may be a suitable option for that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>