<?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>BLE Mesh Certification Process</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/60989/ble-mesh-certification-process</link><description>Hello, 
 we develop an open source framework that we are currently extending to also support the BLE Mesh Access Layer Models. We are currently implementing the foundation layer and model layer. Is it possible to certify this part on its own without supporting</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 May 2020 14:15:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/60989/ble-mesh-certification-process" /><item><title>RE: BLE Mesh Certification Process</title><link>https://devzone.nordicsemi.com/thread/251028?ContentTypeID=1</link><pubDate>Wed, 20 May 2020 14:15:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6501db4-28ab-43cc-9ad3-010acd70c18a</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I see. Qualification may be an issue for this kind of stack, yes. I am afraid we do not have full overview or knowledge about combining parts of Bluetooth mesh technology with other technology, and what can then be qualified. I recommend contacting a &lt;a href="https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-consultants/"&gt;Bluetooth Qualification Consultant&lt;/a&gt;, for figuring out what is possible and how to approach this.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh Certification Process</title><link>https://devzone.nordicsemi.com/thread/250763?ContentTypeID=1</link><pubDate>Tue, 19 May 2020 13:59:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f811092-abe0-454f-a1c6-c22b66474e67</guid><dc:creator>Marius Heil</dc:creator><description>&lt;p&gt;Hi, exactly ;-) We are currently implementing the Foundation and some more models on top of FruityMesh. We plan on using them for some of our projects and also plan to support the lower layers afterwards. Probably the GATT Proxy feature and the connection baerer. But that might take some time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh Certification Process</title><link>https://devzone.nordicsemi.com/thread/250761?ContentTypeID=1</link><pubDate>Tue, 19 May 2020 13:52:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ab4a1f5a-e169-412b-b5ab-6210d96650cd</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Not supporting features is perfectly fine. It is more the idea of supporting high level layers without supporting the layers further down, that is more of an issue.&lt;/p&gt;
&lt;p&gt;A bit of a shot in the dark from my side, but are you thinking of building the Access layer and Foundation Models on top of FruityMesh?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh Certification Process</title><link>https://devzone.nordicsemi.com/thread/250578?ContentTypeID=1</link><pubDate>Tue, 19 May 2020 06:58:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0cb131c7-371f-4ffc-85ca-10f1a38f8563</guid><dc:creator>Marius Heil</dc:creator><description>&lt;p&gt;Thanks, I expected something like this. I would have just handled these states correctly but would not have supported the features such as friend, GATT proxy, etc,...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh Certification Process</title><link>https://devzone.nordicsemi.com/thread/250443?ContentTypeID=1</link><pubDate>Mon, 18 May 2020 12:41:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b338ba0-cfe0-4a9d-91b2-ef4d79703dc4</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;How are you thinking to do this from a technical point of view? E.g. the foundation models has state which is used down in the transport layers (the configuration model controls heartbeat functionality which is part of one of the transport layers). Features such as relay feature, GATT proxy, Friend are also controlled from the foundation model layer. If building only the top few layers, what implementation are you using then for the bottom layers? Regardless of bearer, packets needs to be constructed, handled and parsed correctly in each layer of the stack.&lt;/p&gt;
&lt;p&gt;The mesh profile qualification, as far as I understand it, needs to cover the full stack from the bottom up to the access layer and foundation models.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>