Transmit power used - Verizon vs AT&T

RE: Transmit power used - Verizon vs AT&T

Stian Røed Hafskjold — Fri, 14 Feb 2020 13:05:17 GMT

Sorry, that's not possible. You can do a modem trace and send it to us for analysis: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect

RE: Transmit power used - Verizon vs AT&T

jbrzozoski — Tue, 11 Feb 2020 18:22:17 GMT

Is there any way to tell from the application layer what cDRX setting is in use? We'd like to be able to see it, even if we can't control it.

RE: Transmit power used - Verizon vs AT&T

Stian Røed Hafskjold — Thu, 31 Oct 2019 07:05:24 GMT

This is another network parameter. RRC connection timeout, or cDRX timeout. You can ask if this is configurable as well.

RE: Transmit power used - Verizon vs AT&T

Joshua — Wed, 30 Oct 2019 16:12:04 GMT

Hi Stain, I will reach out to Verizon and see if this is a configurable parameter.

In general is it expected that a data transmission would take a total of about 9 seconds? This seems like a very long time and if we are able to reduce this time it would greatly improve our battery life.

RE: Transmit power used - Verizon vs AT&T

Stian Røed Hafskjold — Wed, 30 Oct 2019 07:56:09 GMT

Hi, this is probably because of the eDRX interval in RRC connected mode (aka cDRX). I'm guessing that in the AT&T network you have a cDRX interval of 0.32 seconds which seems to be the standard, and in the Verizon network it's a lot faster. You should check with the network operator and get the parameters they are using in your region, and check if it's possible to request a different interval. Other than that it could be NB-IoT vs M1, but it looks to me that both plots are showing M1? NB-IoT has a slower transfer rate and the radio is powered on for a longer time each interval.