<?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>Can you do GATT caching with a 4.2 server and a 5.1 client?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/81518/can-you-do-gatt-caching-with-a-4-2-server-and-a-5-1-client</link><description>We have a device based on NRF52832, SDK 13.0, Softdevice S132 v4.0.5. We can&amp;#39;t upgrade the Softdevice at this time but we can modify the firmware if necessary. 
 We know that Bluetooth 5.1 has a feature to allow for GATT caching to speed up the connection</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 15 Nov 2021 15:45:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/81518/can-you-do-gatt-caching-with-a-4-2-server-and-a-5-1-client" /><item><title>RE: Can you do GATT caching with a 4.2 server and a 5.1 client?</title><link>https://devzone.nordicsemi.com/thread/339069?ContentTypeID=1</link><pubDate>Mon, 15 Nov 2021 15:45:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b09a683e-e9c4-4084-97a1-7664231e781f</guid><dc:creator>Andres</dc:creator><description>&lt;p&gt;Kenneth,&lt;/p&gt;
&lt;p&gt;Thank you for your helpful answers.&lt;/p&gt;
&lt;p&gt;Andres&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can you do GATT caching with a 4.2 server and a 5.1 client?</title><link>https://devzone.nordicsemi.com/thread/338331?ContentTypeID=1</link><pubDate>Wed, 10 Nov 2021 09:55:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f627f18-b1e5-47d6-be0b-a0ea6eb46a76</guid><dc:creator>Kenneth</dc:creator><description>[quote user="aaguirre"]You raise an interesting point, is it correct that a softdevice that supports BLE 5.1 will still not be able to handle GATT caching?[/quote]
&lt;p&gt;It&amp;#39;s an optional feature, so you are right.&lt;/p&gt;
[quote user="aaguirre"]Is there a document that may explain more about what features Nordic supports for BLE 5.1?[/quote]
&lt;p&gt;You would need to go into the main&amp;nbsp;page of each of the softdevice specifications to get the hightligthed supported features, e.g.:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/sds_s132/SDS/s1xx/s130.html"&gt;https://infocenter.nordicsemi.com/topic/sds_s132/SDS/s1xx/s130.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I think it&amp;#39;s the second time I have seen a request for GATT caching so it doesn&amp;#39;t seem as feature that is much used, so I guess the additional softdevice size, development and test time have not been prioritized as important enough to go into a softdevice release (at least not yet).&lt;/p&gt;
&lt;p&gt;I am not sure if I have a quick fix for you either, you could possible do it the other way around, e.g. that the mobile phone is the GATT server and the nRF is the GATT client, then you could potentially do some &amp;quot;shortcuts&amp;quot;, for instance if you reconnect to a previously connected mobile phone you can read a specific characteristic directly from the nRF to &amp;quot;see&amp;quot; if the GATT table have changed.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can you do GATT caching with a 4.2 server and a 5.1 client?</title><link>https://devzone.nordicsemi.com/thread/338228?ContentTypeID=1</link><pubDate>Tue, 09 Nov 2021 14:50:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:59311555-9db4-4cf9-988a-e0f24b3f00f4</guid><dc:creator>Andres</dc:creator><description>&lt;p&gt;Hi Kenneth,&lt;/p&gt;
&lt;p&gt;Our product does not support bonding. And it&amp;nbsp;is going to be very difficult to upgrade to a recent softdevice for a number of reasons.&lt;/p&gt;
&lt;p&gt;My next option is the source of my question, namely, continue with a softdevice which supports BLE 4.2 and find out if a central running BLE 5.1 will be able to do the GATT caching.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You raise an interesting point, is it correct that a softdevice that supports BLE 5.1 will still not be able to handle GATT caching? Is there a document that may explain more about what features Nordic supports for BLE 5.1?&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;Andres&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can you do GATT caching with a 4.2 server and a 5.1 client?</title><link>https://devzone.nordicsemi.com/thread/338198?ContentTypeID=1</link><pubDate>Tue, 09 Nov 2021 14:03:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a071e494-a45c-445c-a656-deb536479d40</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Are you sure GATT caching is the feature you are looking for? If your product support bonding this is indirectly already covered by the fact that the peer devices should for instance cache the system attributes and re-enable them when the link is re-encrypted, and thereby will already know the GATT table of the peer device and can for instance receive notifications without doing a new discovery of the GATT table. The only advantage of GATT caching is if your product are not supporting bonding, then GATT caching can be used to avoid re-encrypting the link after connection, thereby saving a few connection intervals on each re-connection, overall I think GATT caching is not used much, and it is (afaik) not supported by any nordic softdevice. This means that for any re-connection with a peer that does not support bonding you will need to do a new GATT table discovery, this is the default case.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>