<?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>Hardware</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64825/hardware</link><description>how many provisioner should be set up in one bluetooth mesh network? Many provisioner and one provisioner with remote provisioning, which is better?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Aug 2020 12:42:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64825/hardware" /><item><title>RE: Hardware</title><link>https://devzone.nordicsemi.com/thread/264871?ContentTypeID=1</link><pubDate>Mon, 17 Aug 2020 12:42:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e0fadc3c-5289-4443-ba7a-2ab0c544bd1a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Tuấn,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Bluetooth SIG doesn&amp;#39;t have a clear recommendation on how many provisioners should/can be in a Bluetooth Mesh network. You can find these lines in the spec:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Although only a single Provisioner is required on a network to do provisioning, multiple Provisioners may be used. The method to share cached data and coordinate across multiple Provisioners is implementation specific.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;/em&gt;So it&amp;#39;s up to the&amp;nbsp;vendor to choose how to share cached data and to coordinate between provisioners. Some of the info that you need to share and coordinate:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;- Share network keys, device keys, composition data of all nodes.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;- Define the provisioning range of each provisioner so that they don&amp;#39;t provision new nodes to same addresses.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;- Coordinate when there is a key refresh etc.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regarding remote provisioning, it could be a solution if the provisioner(s) can&amp;#39;t cover the whole network. But remote provisioning is Nordic&amp;#39;s proprietary solution and has not been standardize by Bluetooth SIG yet.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;There isn&amp;#39;t a &amp;quot;better&amp;quot; solution, it more depends on your application requirements.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>