Please consolidate nRF9160 documentation about CP-RAI and AS-RAI

Knowing, that the AS-RAI implementation is experimental, I would still prefer to have more documentation about the details.

I already asked for these details in an other issue (see Details of AS-RAI and CP-RAI fallback ) but for me there are still some gaps.

The above referred thread discussed, that requesting to use Rel. 14 AS-RAI, the modem falls back to Rel. 13 CP_RAI, if AS-RAI isn't supported by the network provider. So far, so good. The nasty point seems to be, that you can't use this fallback without knowing that, because the supported options seems to differ for AS-RAI and CP-RAI and a function to see, that the modem decided to fall back, is missing.

My results (the trace are provided in the referred thread):

With Rel. 14 AS-RAI only the SO_RAI_NO_DATA seems to work, with SO_RAI_ONE_RESP I had no success.

With requesting Rel. 14 AS-RAI, but fallback to Rel. 13 CP-RAI, SO_RAI_NO_DATA doesn't work, but SO_RAI_ONE_RESP is now working.

My questions:

1. Please document, which options are working in which mode (SO_RAI_NO_DATA, SO_RAI_LAST, SO_RAI_ONE_RESP combined with Rel. 14 AS-RAI, AS-RAI fallback to CP-RAI).

2. Is it possible the check, if the modem falls back to Rel. 13 CP-RAI? Especially, if the first question shows, that there are no common supported options, such a function helps to implement a working application.

Thanks in advance. 

Parents
  • Just an update:

    mfw 1.3.5, NCS 2.4.2

    Doing some comparison tests with TCP and UDP, I stumbled over a nice update to TCP/AS-RAI.

    If you enable AS-RAI (AT%REL14FEAT=0,1,0,0,0 + AT%RAI=1) closing the TCP socket seems to already trigger SO_RAI_NO_DATA. In networks with AS-RAI my modem gets idle in 2-3s after closing. In networks without AS-RAI it takes about 10-12s (that depends on the network setting of the provider).

Reply
  • Just an update:

    mfw 1.3.5, NCS 2.4.2

    Doing some comparison tests with TCP and UDP, I stumbled over a nice update to TCP/AS-RAI.

    If you enable AS-RAI (AT%REL14FEAT=0,1,0,0,0 + AT%RAI=1) closing the TCP socket seems to already trigger SO_RAI_NO_DATA. In networks with AS-RAI my modem gets idle in 2-3s after closing. In networks without AS-RAI it takes about 10-12s (that depends on the network setting of the provider).

Children
Related