<?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>High Latency in NB-IoT communication using Telefonica DE</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/101068/high-latency-in-nb-iot-communication-using-telefonica-de</link><description>Hello, 
 in Germany, O2/Telefonica (MCC+MNC: 26203) recently launched its NB-IoT network on a larger scale. Unfortunately, we see very high latencies (20-30s) in UDP communication with the nRF9160 compared to the other available networks (Vodafone-26202</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 03 Jul 2023 10:11:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/101068/high-latency-in-nb-iot-communication-using-telefonica-de" /><item><title>RE: High Latency in NB-IoT communication using Telefonica DE</title><link>https://devzone.nordicsemi.com/thread/434159?ContentTypeID=1</link><pubDate>Mon, 03 Jul 2023 10:11:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e0dcdb2-0b1c-4430-96fa-6eb7ea447a7d</guid><dc:creator>lobaro-theo</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;thank you.&lt;/p&gt;
&lt;p&gt;Over other channels I got also the information that this issue has been fixed in the O2/Telefonica network for 1/2 basestation vendors. So it might be solved in the future once they update also the 2nd vendor of base stations.&lt;/p&gt;
&lt;p&gt;Thank you for your reply and ruling out a malfunction of the modem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High Latency in NB-IoT communication using Telefonica DE</title><link>https://devzone.nordicsemi.com/thread/433965?ContentTypeID=1</link><pubDate>Fri, 30 Jun 2023 13:58:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a81b197b-e1c1-478c-b7f6-d1839eec9317</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Hi, and sorry for the delay.&lt;/p&gt;
&lt;p&gt;Due to summer vacations, it is harder than usual to find someone who can study the traces.&lt;/p&gt;
&lt;p&gt;However, I got an answer in the end.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In NB-IoT, the network can automatically allocate uplink (UL) resources for a device (UE, short for User Equipment, in LTE-spec-speach) to send data or UE can request UL resources with RACH procedure. logicalChannelSR-ProhibitTimer (~16 s) is started when data becomes available and timer expiry will trigger RACH procedure if NW has not allocated UL resources before that. After each UL allocation retxBSR-Timer is started (~16s) and timer expiry will also trigger RACH procedure if there is data waiting for transmission.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;In this case, one UL allocation is received after successful PDN activation. There is no data available for transmission yet and padding is sent instead, and the retxBSR timer is started. &lt;span&gt;After that socket is opened and data is sent, but the network does not send new UL allocations, so no data is sent before the retxBSR timer expires and the UE requests UL resources.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The modem team means that the device works as expected. To reach fluent data flow with this NW configuration NW should allocate UL resources more frequently. After a successful PDN activation only one UL allocation is received.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High Latency in NB-IoT communication using Telefonica DE</title><link>https://devzone.nordicsemi.com/thread/432362?ContentTypeID=1</link><pubDate>Wed, 21 Jun 2023 13:36:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d6477f1-c9ef-461b-b3ba-e4df792c7a06</guid><dc:creator>lobaro-theo</dc:creator><description>&lt;p&gt;Yes it has been tested 1.3.5 also with same behavior, since the trace collector v2 (preview) app does not have support for it (yet) we used the 1.3.4.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High Latency in NB-IoT communication using Telefonica DE</title><link>https://devzone.nordicsemi.com/thread/432358?ContentTypeID=1</link><pubDate>Wed, 21 Jun 2023 13:32:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4c74285-b5a9-42ad-8090-f4bc1db62885</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Hi, I&amp;#39;ll give the traces to the modem team so they can analyse them.&lt;/p&gt;
&lt;p&gt;In the mean time, could you check if you see the same behaviour happens with modem FW v1.3.5?&lt;/p&gt;
&lt;p&gt;I expect it to be something caused by the network, and not the modem FW, but it would be nice to have it confirmed.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Didrik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>