<?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>Time sychronization in BLE communication</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120723/time-sychronization-in-ble-communication</link><description>Hi 
 I am developing some nodes that all using BLE in nordic chip, I want each node get some data at the same time and send to one central device, the central device can fuse the same time data together and send to a computer to do some process. I am</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 17 Apr 2025 00:27:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120723/time-sychronization-in-ble-communication" /><item><title>RE: Time sychronization in BLE communication</title><link>https://devzone.nordicsemi.com/thread/532083?ContentTypeID=1</link><pubDate>Thu, 17 Apr 2025 00:27:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a427bfc5-7a9d-4894-aefe-eb6a7f5f85c8</guid><dc:creator>Ziyao Zhou</dc:creator><description>&lt;p&gt;Thank you so much for your reply!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Time sychronization in BLE communication</title><link>https://devzone.nordicsemi.com/thread/532075?ContentTypeID=1</link><pubDate>Wed, 16 Apr 2025 20:17:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a3aea7f-581f-414c-ad98-3b07529855a3</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hello Ziyao,&lt;/p&gt;
&lt;p&gt;This highly depends on the data rate and number of nodes, requirement for latency and packet losses.&lt;br /&gt;Below I list a few potential technologies and&amp;nbsp;some relevant overviews. You can use this as a starting point and look further into each technology to see which suits your need best.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Periodic Advertising with Response
&lt;ul&gt;
&lt;li&gt;Precise/strict packet timing,&amp;nbsp;no timestamp needed, as data can only be transferred in specific timeslot.&lt;/li&gt;
&lt;li&gt;Packet losses possible.&lt;/li&gt;
&lt;li&gt;Limited throughput.&lt;/li&gt;
&lt;li&gt;Reference time synchronization might not be necessary, but also possible thanks to strict packet schedule.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;BLE Connection
&lt;ul&gt;
&lt;li&gt;No timing guaranteed at application layer, timestamp needed.&lt;/li&gt;
&lt;li&gt;Packet losses not possible, the connection itself is terminated in case of loss.&lt;/li&gt;
&lt;li&gt;High throughput.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Reference time synchronization might be a challenge. Refer:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/97532/ble-time-synchronization-between-devices"&gt;BLE Time Synchronization between devices&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Bluetooth Mesh with Time Models
&lt;ul&gt;
&lt;li&gt;No timing guaranteed at application layer, timestamp needed.&lt;/li&gt;
&lt;li&gt;Packet losses possible.&lt;/li&gt;
&lt;li&gt;Limited throughput.&lt;/li&gt;
&lt;li&gt;Time Models provide a mean for reference time synchronization.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>