<?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>Handle Weak LTE Connection</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/114179/handle-weak-lte-connection</link><description>My application is running on a nRF9160 using NCS v1.7.0 and modem FW 1.3.0. Sometimes, when our device is in an area with bad LTE coverage, I believe we&amp;#39;re overflowing some buffer on either the modem side or somewhere deeper down in the networking stack</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 26 Aug 2024 16:40:45 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/114179/handle-weak-lte-connection" /><item><title>RE: Handle Weak LTE Connection</title><link>https://devzone.nordicsemi.com/thread/499822?ContentTypeID=1</link><pubDate>Mon, 26 Aug 2024 16:40:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:00523711-8e4b-4cad-a12f-31f3914b19ca</guid><dc:creator>Achim Kraus</dc:creator><description>&lt;p&gt;Did you try to get signal level and quality, e.g. executing&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;quot;AT+CEINFO?&amp;quot;&lt;/p&gt;
&lt;p&gt;Especially, if that shows low signal levels (&amp;lt;-130dBm), low quality (&amp;lt; 0dB) and high repetition (e.g. NB-IoT down 128, up 32) then two consequences will show:&lt;/p&gt;
&lt;p&gt;- the RTT gets up to 15s (and more)&lt;/p&gt;
&lt;p&gt;- the IP message loss gets also high (depending on the message size, in my experience 250 bytes may result in 10% lost)&lt;/p&gt;
&lt;p&gt;that may cause TCP to drop the connections. If you want/need to stick to TCP, you will need a (much) better antenna.&lt;/p&gt;
&lt;p&gt;Even if you use a UDP based protocol, you need to ensure, that the transmission timeouts are larger enough, that the lost ip-messages are retransmitted (and even with 3 retransmissions, message will get lost) and that message is rather small. Also consider, that the signal level/quality may change within a day (usually better at night) and within weeks (e.g. weather).&lt;/p&gt;
&lt;p&gt;Just a statistic from one of my test devices (UDP, CoAP/DTLS 1.2 CID):&lt;/p&gt;
&lt;p&gt;250 bytes, 15s timeout , max 3 retransmission.&lt;/p&gt;
&lt;p&gt;RTT: 12450 ms, CT: 13273 ms&lt;br /&gt;CE: down: 128, up: 32, RSRP: -126 dBm, CINR: 2 dB, SNR: 3 dB&lt;/p&gt;
&lt;p&gt;&amp;gt; 0*1471, 1*113, 2*3, 3*3, failures 8&lt;/p&gt;
&lt;p&gt;1471 within that 15s.&lt;/p&gt;
&lt;p&gt;113 with one retransmission after 15s&lt;/p&gt;
&lt;p&gt;3 with a second retransmission after 15s and 30s&lt;/p&gt;
&lt;p&gt;3 with a third retransmission after 15s, 30s, 60s&lt;/p&gt;
&lt;p&gt;8 gave up after 3 retransmissions.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>