How to close down nrf9161 so that it reconnects COAP quickly

RE: How to close down nrf9161 so that it reconnects COAP quickly

Achim Kraus — Fri, 11 Apr 2025 12:16:27 GMT

Take my measurements (nRF9151-DK, German network operator) just as example, that It's worth to do own measurements.

If your network operator doesn't support RAI, then on/off takes about 25% less.

If your network operator supports AS-RAI, then on/off is about the same.

If your network operator supports AS-RAI and eDRX, then on/off takes about 100% more.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Achim Kraus — Fri, 11 Apr 2025 12:10:39 GMT

devzone.nordicsemi.com/.../ppk2_2D00_rai.ppk2

Always on, RAI. That takes about 120mAs per Exchange every 15s.

devzone.nordicsemi.com/.../ppk2_2D00_rai_2D00_edrx.ppk2

Always on, RAI, eDRX. That takes about 60mAs per Exchange every 15s.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Achim Kraus — Fri, 11 Apr 2025 12:08:50 GMT

Some ppk files from a LTE-M network.

devzone.nordicsemi.com/.../ppk2_2D00_on_2D00_off.ppk2

Switch on/off. That takes about 130mAs per Exchange every 15s.

devzone.nordicsemi.com/.../ppk2_2D00_no_2D00_rai.ppk2

Always on, no RAI. That takes about 160mAs per Exchange every 15s.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Ed Holbrook — Fri, 11 Apr 2025 07:26:52 GMT

Thanks, Achim Kraus - that makes a lot of sense!

RE: How to close down nrf9161 so that it reconnects COAP quickly

Achim Kraus — Thu, 10 Apr 2025 15:48:00 GMT

Some calculations:

For a nRF9151 the "best cases" are around 30-50mAs for exchanging a message, and about 8µA as quiescent current. Assuming a send interval of 15s results then in 4*60*50mAs => 12 As per h compared to 28,8 mAs quiescent power in one hour.

Switching off also comes with some power consumption and it would be required to consider that vs. the power consumption in RRC active.

All in all:

The easiest way is to use a PPK II and measure the alternatives.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Achim Kraus — Thu, 10 Apr 2025 15:39:34 GMT

The network operators have introduced PSM, RAI and eDRX in order to manage the network connectivity and the power consumption.

That works in general pretty well. A Thingy:91 runs from battery sending every hour a message for a year (depending on the radio signal level).

For NB-IoT my experience is, that the networks supports mainly PSM and CP-RAI.

For LTE-M it's PSM. In some cases also AS-RAI.

And also in some cases eDRX.

Which combination results with the transmission pattern in which power consumption is not easy to say. But the PPK II is pretty cheap, so it's possible to measure alternative approaches and go for the best one.

Fast send interval an long sleeps on demand:

Usually the device stays RRC active after sending some messages for a couple of seconds. If RAI is supported, that could be shorted. If not, then I would start with measuring the difference between just send (without off/on) and on-send-off. I guess the difference will be small compared to the overall energy consumption sending every 15s.

Only if RAI is supported, the device will enter RRC idle fast enough, that eDRX will start to make sense, if available. Use the next longer interval, e.g. 15s => 20.48s. But don't expect too large savings.

For the long sleep you may either switch OFF/ON or use PSM with 1 days interval.

In cases of some network loss after PSM you may need to be aware, the calling "sendto" may return success (immediately) but later fails when actually reattaching the network. That requires mostly to resend the message after the device has re-attached successful.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Ed Holbrook — Thu, 10 Apr 2025 15:13:20 GMT

Hi Achim Kraus ,

Thanks for your guidance and support so far! Things seem to be better with the system now, but I've been thinking about what you said about Netwoerk Operators not supporting registering every 15 seconds. Do you know if there is any guidance about this anywhere? I'm looking at our whole system and am trying to understand what "sweetspots" we moght want to investigate. For instance, if the customer wants to update every (say) 20 seconds, then we might not want to go into a "deep" sleep and turn everything off. However, if the customer wants to go to sleep overnight (say for 6 hours), turning off would probably be a good idea! Somewhere inbetween is a "changeover" point. I just don't know where to look!

Any thoughts?

Many thanks,

Ed.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Ed Holbrook — Wed, 02 Apr 2025 15:21:34 GMT

thanks - will do!

RE: How to close down nrf9161 so that it reconnects COAP quickly

Achim Kraus — Wed, 02 Apr 2025 14:20:15 GMT

You're welcome.

Just one remark: some MNO don't support to register ever 15s to there network. Keep that in mind, when you're in trouble.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Ed Holbrook — Wed, 02 Apr 2025 14:01:37 GMT

Thanks Achim - I'll give it a try!

RE: How to close down nrf9161 so that it reconnects COAP quickly

Achim Kraus — Wed, 02 Apr 2025 09:52:55 GMT

[quote userid="134221" url="~/f/nordic-q-a/120355/how-to-close-down-nrf9161-so-that-it-reconnects-coap-quickly/530186"]nrf_modem_lib_dfu_handler();[/quote]

Do you mean "nrf_modem_lib_init()"?

The time "getaddrinfo()" requires is mainly to wait for the successful network registration. If you put a "wait for modem connection being marked by a semaphore" before that loop, the loop itself will require less time (but the overall will be the same).

I don't close the UDP socket, but I also don't deactive LTE. In a loop with an interval of 15s, I'm not sure, if that off/on pays-off.

In my experience, it's not required to call "lte_lc_offline()" before "lte_lc_power_off()".

[quote userid="134221" url="~/f/nordic-q-a/120355/how-to-close-down-nrf9161-so-that-it-reconnects-coap-quickly/530186"]As for why - we are looking at having our system turned right off apart from a very low power PIC device, which will result even lower power usage - especially overnight when the system could be turned off for number of hours.[/quote]

A nRF9160/61/51 has quiescent current of 3-4µA. I'm not sure, if switching it off over night really save that much energy. But it's your decision.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Ed Holbrook — Wed, 02 Apr 2025 09:35:06 GMT

Hi Achim,

Thanks for your answer. I'll have more of a look at the code.

As for why - we are looking at having our system turned right off apart from a very low power PIC device, which will result even lower power usage - especially overnight when the system could be turned off for number of hours.

Do you know if I have the correct sequence of calls?

When initially turning on, I call:

nrf_modem_lib_dfu_handler();

lte_lc_connect_async();

getaddrinfo() (looping until an address is found - this is where it can get "stuck" for minutes)

I then have a possible loop polling (say) once every 15 seconds:

lte_lc_func_mode_set(LTE_LC_FUNC_MODE_NORMAL)

wait for modem connection being marked by a semaphore

Set up socket to COAP server

Handle receiving / sending of COAP messages

Close socket to COAP server

lte_lc_func_mode_set(LTE_LC_FUNC_MODE_DEACTIVATE_LTE);

sleep for (say) 15 seconds before looping

When turning off, I call:

lte_lc_offline();

lte_lc_power_off();

nrf_modem_lib_shutdown();

Many thanks,

Ed.

RE: How to close down nrf9161 so that it reconnects COAP quickly

Achim Kraus — Tue, 01 Apr 2025 15:49:50 GMT

In my experience, calling "lte_lc_power_off()" saves the current state and allows the modem to startup again fast. As you already detected, "lte_lc_power_off()" takes in some case a lot of time to deregister from the network (see nRF9160 - CFUN=0 - order of operations? it's also not possible to start it and then short the timeout, because that will not save the current state to the NVM). So, there will be the one or the other pain.

Anyway, I'm not sure, why you want to power it off all. PSM is usually wide supported and that obsoletes such power downs. So do you have any special requirements, why you don't want to use PSM?

RE: How to close down nrf9161 so that it reconnects COAP quickly

Ed Holbrook — Tue, 01 Apr 2025 08:56:01 GMT

Sample Output:

*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x1
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0x10000
[00:00:00.752,471] <inf> display_it8951: Could not connect to display - HW Busy
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
[00:00:00.753,112] <inf> nrf_whisper1: Stating nrf_whisper, version: v1.0.3
[00:00:01.664,581] <inf> wcp_time: Update IMEI
[00:00:01.665,191] <inf> wcp_time: IMEI Number: 358299840119099
[00:00:01.685,302] <inf> nrf_whisper1: Configure Modem
[00:00:01.685,302] <inf> wcp_coap: Set DNS server to Google
[00:00:01.691,864] <inf> wcp_coap: DNS set to Google
[00:00:01.691,864] <inf> wcp_coap: Connect to LTE network
[00:00:01.743,713] <inf> wcp_coap: lte_lc_connect_async - returned: 0
[00:00:01.743,713] <inf> nrf_whisper1: Resolve Server
[00:00:01.743,927] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:01.743,957] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:02.744,293] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:02.744,323] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:03.744,689] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:03.744,689] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:04.745,025] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:04.745,056] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:05.745,391] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:05.745,391] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:06.745,727] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:06.745,758] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:07.746,093] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:07.746,093] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:08.746,429] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:08.746,459] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:09.746,795] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:09.746,795] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:10.747,131] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:10.747,161] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:11.747,497] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:11.747,497] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:12.747,833] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:12.747,863] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:13.748,504] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:13.748,504] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:14.748,840] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:14.748,870] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:15.749,206] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:15.749,237] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:16.749,542] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:16.749,572] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:17.749,908] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:17.749,908] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:18.750,305] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:18.750,335] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:19.750,701] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:19.750,701] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:20.751,037] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:20.751,068] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:21.751,403] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:21.751,403] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:22.751,739] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:22.751,770] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:23.752,258] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:23.752,258] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:24.752,563] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:24.752,593] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:25.752,929] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:25.752,929] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:26.753,265] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:26.753,295] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:27.753,631] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:27.753,631] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:28.753,967] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:28.753,997] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:29.754,333] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:29.754,333] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:30.754,669] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:30.754,699] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:31.755,065] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:31.755,065] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:32.755,371] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:32.755,401] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:33.755,767] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:33.755,767] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:34.756,103] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:34.756,134] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:35.756,469] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:35.756,469] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:36.756,805] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:36.756,805] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:37.757,171] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:37.757,171] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:38.757,507] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:38.757,537] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:39.758,331] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:39.758,361] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:40.758,666] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:40.758,697] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:41.759,185] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:41.759,185] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:42.759,490] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:42.759,521] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:43.759,857] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:43.759,857] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:44.760,192] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:44.760,223] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:45.760,559] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:45.760,559] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:46.760,894] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:46.760,925] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:47.761,260] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:47.761,260] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:48.761,718] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:48.761,749] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:49.762,115] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:49.762,115] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:50.762,573] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:50.762,603] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:51.762,969] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:51.762,969] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:52.763,305] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:52.763,336] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:53.763,671] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:53.763,671] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:54.764,007] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:54.764,007] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:55.764,373] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:55.764,373] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:56.764,709] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:56.764,739] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:57.765,075] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:57.765,075] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:58.765,533] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:58.765,563] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:00:59.765,930] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:00:59.765,930] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:00.766,387] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:00.766,418] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:01.766,784] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:01.766,784] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:02.767,120] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:02.767,150] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:03.767,486] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:03.767,486] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:04.768,188] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:04.768,218] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:05.768,554] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:05.768,585] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:06.768,890] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:06.768,890] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:07.769,256] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:07.769,256] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:08.769,897] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:08.769,927] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:09.770,294] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:09.770,294] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:10.770,751] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:10.770,782] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:11.771,148] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:11.771,148] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:12.771,606] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:12.771,636] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:13.780,761] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:13.780,761] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
+CEREG: 2,"2437","07D5BA1F",9
[00:01:14.191,009] <inf> wcp_coap: Network registration status: 2
[00:01:14.191,009] <inf> wcp_coap: LTE cell changed: Cell ID: 131447327, Tracking area: 9271
[00:01:14.781,280] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:14.781,280] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
+CSCON: 1
[00:01:14.932,861] <inf> wcp_coap: RRC mode: Connected
[00:01:15.781,585] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:15.781,616] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
[00:01:16.781,951] <err> wcp_coap: ERROR: getaddrinfo failed -11
[00:01:16.781,951] <inf> nrf_whisper1: Failed to resolve server name - retry in 1 second
+CEREG: 5,"2437","07D5BA1F",9,,,"11100000","00101000"
[00:01:17.554,534] <inf> wcp_coap: Network registration status: 5
[00:01:17.554,565] <inf> wcp_coap: Network registration status: Connected - roaming
[00:01:17.555,541] <inf> wcp_coap: PSM parameter update: TAU: 28800, Active time: -1
%XTIME: ,"52401080210580","01"
	:
	: