NAS-RAI (Non-Access Stratum RAI) used on NB-IoT with nRF9161/51

[fdup78]

Hello,

NAS-RAI (Non-Access Stratum RAI) used on NB-IoT Control Plane : on nRF9160 it was controllable via the AT%XRAI command, using the <rai> parameter :

0 – Undefined, default

3 – Control plane one response

4 – Control plane no response

Is this NAS-RAI over NB-IoT feature also available with latest nRF9161/51 version (SDK 2.6.1) ?

What is the equivalent AT command(s) on nRF9161/51 ?

[Achim Kraus]

Not sure, if Please consolidate nRF9160 documentation about CP-RAI and AS-RAI is valid for mfw-2.0.1.

If so, the below table may help to migrate the CP-RAI (NAS-RAI?) options to AS-RAI.

RAi option	AS-RAI	AS-RAI using CP-RAI implicit (fallback)
RAI_SO_LAST	works	works
RAI_SO_ONE_RESP	doesn't work	works
RAI_SO_NO_DATA	works	doesn't work

Especially in the case of CP-RAI/ONE_RESPONSE you need both, "ONE_RESPONSE" (before sending the message) and "NO_DATA" (after receiving the response), otherwise it would fail either with CP-RAI or AS-RAI. And you may need to  check the times between the last sent/received message and RRC Idle to see, if it works as intended.

[Øyvind]

Achim Kraus have you been able to get your hands on a newer nRF9161 to test mfw 2.0.1?

[Achim Kraus]

I've tried to test with a nRF9161-DK v0.9.1, nRF9161 LACA ADA, mfw_nrf91x1_2.0.1.

That combination is not able to register at 26202 using LTE-M (the only Rel 14 network here in south germany).

+CEREG: 2,"B982","031D7801",7
I 02.836 : LTE cell changed: n.a
I 02.836 : LTE Mode: none
+CEREG: 2

Using the same SIM card, a nRF9160-DK, v1.1.0, nRF9160 SICA B1A, mfw_nrf9160_1.3.5, that combination registers in that network.

+CEREG: 5,"B982","031D7801",7,,,"00000000","00111001"

So I'm only able to test the behavior with Rel 13. CP-RAI.

(Not sure, seems, that is not longer possible to drag&drop a modem mtrace. My browser shows "An error occurred. Please try again or contact your administrator". I tried it a couple of times and I consider, it's an issues on Nordic's side.)

[Øyvind]

Achim Kraus said:

That combination is not able to register at 26202 using LTE-M (the only Rel 14 network here in south germany).

That's interesting. Could you please register a new DevZone ticket and provide the steps that you used, i.e. what app, what SIM? 

Achim Kraus said:

Not sure, seems, that is not longer possible to drag&drop a modem mtrace

I've seen this issue before. Will report to our admin right away, as this should not be an issue. What happens if you choose Insert --> Image/Video/File and manually insert it?

[Achim Kraus]

I'm not really able to spend that much time in it, at least not for now.

The nRF9161 and mfw 2.0.1 is not currently the focus of my interest.

" Insert --> Image/Video/File"

Strange, seems not to work from my side.

[Achim Kraus]

Testing with a nRF9161-DK v0.9.1, nRF9161 LACA ADA, mfw_nrf91x1_2.0.0 and 26202 LTE-M works. Maybe the 2.0.1 has an issue. I'm still not able to upload modem traces.

The results with 1.3.6 and 2.0.0:

RAi option	AS-RAI	AS-RAI using CP-RAI implicit (fallback)
RAI_SO_LAST	works	works
RAI_SO_ONE_RESP	doesn't work	works
RAI_SO_NO_DATA	works	works

Seems, that "NO_DATA" (now) works also for CP-RAI.

[Øyvind]

Achim Kraus said:

Strange, seems not to work from my side.

Sorry to hear that. If you want you can try to send the file to me directly in a PM to see if that helps. But I understand if you are not able to spend a lot of time on this issue, but it would be good to verify RAI support in your network. 

Achim Kraus said:

Testing with a nRF9161-DK v0.9.1, nRF9161 LACA ADA, mfw_nrf91x1_2.0.0 and 26202 LTE-M works. Maybe the 2.0.1 has an issue. I'm still not able to upload modem traces.

If there is an issue with mfw 2.0.1, then it would be very good with modem traces. 

[Achim Kraus]

Øyvind said:

If there is an issue with mfw 2.0.1, then it would be very good with modem traces. 

It looks like.

I tried to send the modem trace via a "message". Not sure, if that works. Looks like the same function and issue as for tickets.

[Achim Kraus]

trace-2024-06-30T14-24-14.950Z.mtrace

Maybe uploading a trace with windows works.

[Achim Kraus]

The upload issue was caused by Ubuntu 22.04 and Firefox from snap. That blocks files in the ".config" folder and sub-folder. Moving the file to the home makes it possible to upload it.

[Øyvind]

Thanks! That is good information to be aware of

[Achim Kraus]

Just if someone reads it, the issue of mfw 2.0.1 with 26202 LTE-M (Rel 14) is fixed with mfw 2.0.2