<?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>Sequence Number in BLE Mesh - nRF Connect SDK 1.9.1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/101312/sequence-number-in-ble-mesh---nrf-connect-sdk-1-9-1</link><description>Hi, 
 
 I am application developer , we are using nrf connect sdk1.9.1 version and nrf 52 chip . I want to know concept of sequence number when I am generating the packet from mobile app. Based on our implementation there are two type of packets we are</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 30 Jun 2023 01:09:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/101312/sequence-number-in-ble-mesh---nrf-connect-sdk-1-9-1" /><item><title>RE: Sequence Number in BLE Mesh - nRF Connect SDK 1.9.1</title><link>https://devzone.nordicsemi.com/thread/433811?ContentTypeID=1</link><pubDate>Fri, 30 Jun 2023 01:09:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:837cbeaa-e8b2-42c3-beb6-a9a06d5762ea</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;From the Mesh Profile Specification - Section 3.8.3:&lt;/p&gt;
&lt;div title="Page 103"&gt;
&lt;div&gt;
&lt;div&gt;
&lt;p&gt;&lt;span&gt;The sequence number, a 24-bit value contained in the SEQ field of the Network PDU, is primarily designed to protect against replay attacks. Elements within the same node may or may not share the sequence number space with each other. Having a different sequence number in each new Network PDU for every message source (identified by the unicast address contained in the SRC field) is critical for the security of the mesh network.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;With a 24-bit sequence number, an element can transmit 16,777,216 messages before repeating a nonce. If an element transmits a message on average once every five seconds (representing a fairly high frequency message for known use cases), the element can transmit for 2.6 years before the nonce repeats.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Each element shall use strictly increasing sequence numbers for the Network PDUs it generates. Before the sequence number approaches the maximum value (0xFFFFFF), the element shall update the IV Index using the IV Update procedure (see Section &lt;/span&gt;&lt;span&gt;3.10.5&lt;/span&gt;&lt;span&gt;). This is done to ensure that the sequence number will never wrap around.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Br,&amp;nbsp;&lt;br /&gt;Joakim&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>