<?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>A couple of questions regarding mesh</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27124/a-couple-of-questions-regarding-mesh</link><description>I&amp;#39;ve read through a decent amount of the BLE Mesh spec sheet(s), but I still have a few things that I&amp;#39;m not completely sure on. If someone could answer even just a few of these questions, that would be great: 
 
 
 It sounds like a smartphone (with</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 08 Aug 2017 08:25:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27124/a-couple-of-questions-regarding-mesh" /><item><title>RE: A couple of questions regarding mesh</title><link>https://devzone.nordicsemi.com/thread/106740?ContentTypeID=1</link><pubDate>Tue, 08 Aug 2017 08:25:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:340df016-1c1f-48c2-9e6c-d64a929a92c3</guid><dc:creator>Eirik Midttun</dc:creator><description>&lt;ol&gt;
&lt;li&gt;First of all, Bluetooth 5 is unrelated to Bluetooth mesh, so this is not a concern. The phone can be a provisioner and a device. To be a node in the network the phone must implement the Mesh Proxy Service (GATT). The challenge is that currently the phone must implement the Bluetooth mesh stack as part of the app, that is, all layers above bearer. You might want to consider a proprietary GATT service working at the upper layers instead.&lt;/li&gt;
&lt;li&gt;As said in 1. it can.&lt;/li&gt;
&lt;li&gt;Blacklisting is not automatic. The spec states a procedure that is initiated by the provisioner. When and how this happens is up to the designer of the product/solution.&lt;/li&gt;
&lt;li&gt;The specification states that a node can store multiple network keys, so the answer is yes. However, the spec also states that application keys are bound to only one application key, so there are restrictions.&lt;/li&gt;
&lt;li&gt;That is basically the point with standards. Bear in mind that some things are Nordic specific, for example the DFU solution.&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>