https://devzone.nordicsemi.com/f/nordic-q-a/9422/fragmentation-of-notifications---should-i-combine-themSuppose I have a lot of very small characteristics (1 or 2 bytes) to send lots of notifications on. They are all updated simultaneously, though the central doesn&#39;t care about that. When I notify them, does each notification go into a separate BLE packeten-USTelligent Community 13Fri, 25 Sep 2015 12:36:49 GMThttps://devzone.nordicsemi.com/thread/34782?ContentTypeID=1Fri, 25 Sep 2015 12:36:49 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e344fae1-4127-4ac2-aee7-e0dfdbbb4743Petter Myhre<p>With our SoftDevices each ATT packet (notification) will go into separate L2CAP packets and will be sent separately over the air.</p> <p>If the characteristic values are always notified at the same time it would be better to combine them.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/34781?ContentTypeID=1Thu, 24 Sep 2015 14:31:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:020749a2-0e4d-4625-af9a-f2c2cbbfcabeTorsten Robitzki<p>They are packet into different L2CAP packets and I think in theory there is nothing that prevents an BLE implementation from packing more than one L2CAP SDU into one link layer PDU.</p> <p>But I doubt that there are existing implementations that do this. You could just try it out. Beside your idea of using one &quot;combined&quot; characteristic, you could use one characteristic (an integer for example) that gets changed when ever any of the othere characteristics get changed.</p><div style="clear:both;"></div>