<?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>Bearer layer explanation</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46528/bearer-layer-explanation</link><description>Hi all, 
 I have a theoretical question. What is the bearer layer? There are up to 4 bearers defined in the bearer layer: Advertising, GATT, PB-ADV, PB-GATT. How to make the interpretation? In the bearer layer is defined the bearer, protocol defining</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 26 Apr 2019 15:12:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46528/bearer-layer-explanation" /><item><title>RE: Bearer layer explanation</title><link>https://devzone.nordicsemi.com/thread/184121?ContentTypeID=1</link><pubDate>Fri, 26 Apr 2019 15:12:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3c8a4b44-e23d-434c-8253-775b48178d3f</guid><dc:creator>Patrik</dc:creator><description>&lt;p&gt;&lt;span&gt;Ok, now I for sure understand it takes the packet format from BLE. The GATT bearer uses before initiating the connection non-connectable advertisements and fills the advertising channel PDU with Bluetooth mesh protocol data. Then in connection state, using the proxy protocol, it encapsulates data into Proxy PDU and Proxy PDU is encapsulated into Data channel PDU and then sent over the air.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;By PB-GATT bearer the Provisioning PDUs are encapsulated into Proxy PDU and Proxy PDU encapsulated into Data Channel PDU and sent over the air.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;By PB-ADV bearer the Provisioning PDU encapsulated into advertising channel PDU and the sent over the air.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you for claryfying guys&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bearer layer explanation</title><link>https://devzone.nordicsemi.com/thread/183997?ContentTypeID=1</link><pubDate>Fri, 26 Apr 2019 09:00:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:58cd4886-aa11-4872-ae6d-3fe8b12dfdee</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;&lt;span&gt;&amp;quot;I dont know if I am correct in the above statements. I am absolutely not sure. The bearer layer is what actually? &amp;quot;&lt;/span&gt;&lt;br /&gt;- The bearer layer defines the method of data transmission; it&amp;#39;s packet format, and whether it uses non-connectable Advertisements or a connection-based GATT transfer.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;&amp;quot;This two statements seem to me contradictory.&amp;quot;&lt;/span&gt;&lt;br /&gt;- Non-scannable means that the advertiser does not support Scan-Response packets, any scanner can receive the advertisement data and relay it. If the relay node also supports the GATT bearer then it can use that as well as relaying the advertisement via the&amp;nbsp;advertisement(ADV) bearer.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bearer layer explanation</title><link>https://devzone.nordicsemi.com/thread/183462?ContentTypeID=1</link><pubDate>Wed, 24 Apr 2019 12:43:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f407f149-3552-4f1a-9e91-147089180026</guid><dc:creator>Patrik</dc:creator><description>&lt;p&gt;Hi Jeff4BLE,&lt;/p&gt;
&lt;p&gt;I have looked at that articles. Is this flow correct?&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1556109771479v2.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bearer layer explanation</title><link>https://devzone.nordicsemi.com/thread/183290?ContentTypeID=1</link><pubDate>Wed, 24 Apr 2019 04:26:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:849d5308-a431-42b3-a57a-6eab875c37c5</guid><dc:creator>Jeff4BLE</dc:creator><description>&lt;p&gt;These are all BLE Mesh Terms. &lt;a href="https://www.bluetooth.com/bluetooth-technology/topology-options/le-mesh/mesh-glossary/#bearer_layer"&gt;Bearer Layer&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.bluetooth.com/bluetooth-technology/topology-options/le-mesh/mesh-glossary/"&gt;https://www.bluetooth.com/bluetooth-technology/topology-options/le-mesh/mesh-glossary/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;PB - is Provisioning Bearer&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.bluetooth.com/blog/provisioning-a-bluetooth-mesh-network-part-1/"&gt;https://www.bluetooth.com/blog/provisioning-a-bluetooth-mesh-network-part-1/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.novelbits.io/bluetooth-mesh-tutorial-part-2/"&gt;https://www.novelbits.io/bluetooth-mesh-tutorial-part-2/&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>