<?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>Notification&amp;amp;indication The result of sending data</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/79451/notification-indication-the-result-of-sending-data</link><description>hi， 
 My application MTU exchange is 23 bytes，I send data using Notification or indication to sent 105 bytes date，I subcontracted the data into 20 bytes ot sent，How do I make sure my 105 bytes data gets sent out，What is the specification process should</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 Sep 2021 12:29:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/79451/notification-indication-the-result-of-sending-data" /><item><title>RE: Notification&amp;indication The result of sending data</title><link>https://devzone.nordicsemi.com/thread/328822?ContentTypeID=1</link><pubDate>Thu, 09 Sep 2021 12:29:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3409fbc6-7f0e-4b31-83ee-27d1b3b4a436</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is there any reason why you limit your MTU length to 23 bytes?&lt;/p&gt;
&lt;p&gt;Pretty much all BLE devices should support longer ATT MTU by now, and if you set it to 108 bytes or more you can send 105 bytes of data&amp;nbsp;in a single update, which makes your application logic simpler and the communication more efficient.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Whether or not you send it at once, or split the message into multiple 20 byte chunks, the Bluetooth stack guarantees that your packets will be received at the other end, in the same order as you send them.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The only situation in which data is not received on the other end is if the link breaks and you get a disconnect.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>