Network search behavior

Hello,

I've the following: NCS V2.2.0, Modem FW 1.3.3. I'm currently testing the system in bad network conditions. To test this i wrap the product in a lot of aluminum foil, in combination with an isolated USB port to connect to the debug and modem trace uart. I've set a data profile using %XDATAPRF=0, so I expect a search pattern of AT%PERIODICSEARCHCONF=0,0,0,1,"0,10,40,,5","1,300,600,1800,1800,3600"

But this is not the case:

[2023-01-31 21:13:52.243] <inf> cellular: Network registration status: LTE_LC_NW_REG_SEARCHING
[2023-01-31 21:14:12.910] <inf> cellular: LTE cell changed: Cell ID: 7677543, Tracking area: 1312
[2023-01-31 21:14:12.910] <inf> cellular: LTE mode update: NB-IOT
[2023-01-31 21:14:12.910] <inf> cellular: RRC mode: Connected
[2023-01-31 21:14:12.910] <inf> cellular: RRC mode: Idle
[2023-01-31 21:14:12.910] <inf> cellular: LTE cell changed: Cell ID: -1, Tracking area: -1
[2023-01-31 21:14:14.017] <inf> cellular: LTE mode update: none
[2023-01-31 21:14:14.017] <inf> cellular: Network registration status: LTE_LC_NW_REG_NOT_REGISTERED
[2023-01-31 21:17:22.279] <inf> cellular: Network registration status: LTE_LC_NW_REG_SEARCHING
[2023-01-31 21:17:54.175] <inf> cellular: LTE cell changed: Cell ID: 7677543, Tracking area: 1312
[2023-01-31 21:17:54.175] <inf> cellular: LTE mode update: NB-IOT
[2023-01-31 21:17:54.175] <inf> cellular: RRC mode: Connected
[2023-01-31 21:17:54.175] <inf> cellular: RRC mode: Idle
[2023-01-31 21:17:55.438] <inf> cellular: LTE cell changed: Cell ID: -1, Tracking area: -1
[2023-01-31 21:17:55.438] <inf> cellular: LTE mode update: none
[2023-01-31 21:17:55.438] <inf> cellular: Network registration status: LTE_LC_NW_REG_NOT_REGISTERED
[2023-01-31 21:20:33.403] <inf> cellular: Network registration status: LTE_LC_NW_REG_SEARCHING
[2023-01-31 21:21:01.386] <inf> cellular: LTE cell changed: Cell ID: 7677543, Tracking area: 1312
[2023-01-31 21:21:01.386] <inf> cellular: LTE mode update: NB-IOT
[2023-01-31 21:21:01.386] <inf> cellular: RRC mode: Connected
[2023-01-31 21:21:01.386] <inf> cellular: RRC mode: Idle
[2023-01-31 21:21:01.386] <inf> cellular: LTE cell changed: Cell ID: -1, Tracking area: -1

It keeps searching quite aggressive, this is draining the battery and is undesired. Our product sits outside and can be covered by snow for a long time, if the modem keeps searching this aggressive the battery will not survive the winter.

I've captured the wireshark log and can see that every search results in 'No suitable cells in tracking area'. I do use a roaming sim card. When i remove the foil the device connects without problems. Questions:

1. Why does the modem search so aggressive when receiving EMM cause 15?

2. Why is PERIODICSEARCHCONF completely ignored? I what conditions does the modem follow the set pattern?

3. Who sends this 'Cause: No Suitable Cells In tracking area (15)' message? Is it the network? How can I see which network? The roaming sim should have access to almost all networks in the area.

  • Hello,

    I have forwarded you questions to the experts and will get back to you with their responses.

    Best regards,

    Michal

  • I have gotten answers from an expert for your three questions. This is what they said:

    1. Why does the modem search so aggressive when receiving EMM cause 15?

    After EMM cause #15 "No suitable cells in tracking area" modem will try to search for other - suitable - tracking area from the same network. This is why there is an immediate search after the reject.

    2. Why is PERIODICSEARCHCONF completely ignored? I what conditions does the modem follow the set pattern?

    %PERIODICSEARCHCONF is used in periodic searches. It is not related to above scenario for example. Periodic search state is entered after modem has scanned all supported bands and no suitable cell was found. Then modem continues to search for a suitable cell periodically - at that point the %PERIODICSEARCHCONF is followed.

    3. Who sends this 'Cause: No Suitable Cells In tracking area (15)' message? Is it the network? How can I see which network? The roaming sim should have access to almost all networks in the area.

    This is reject cause from network. You can use %XMONINTOR for reading the current network (identified with PLMN ID), but this is not that straight forward because after the reject is received it may be already too late to read the current network (because scan may have been already started). Therefore, what you can do is to subscribe +CEREG notifications and always after receiving one you can use %XMONITOR for reading the PLMN ID of the current network. This way, the previous %XMONITOR result before the reject should show the related PLMN ID i.e. the network that sent the reject. 

    Note that even though SIM card subscription has access to a network, there may be tracking areas in that network where there is no access. Reject cause #15 refers to such scenario.

    Best regards,

    Michal

  • After EMM cause #15 "No suitable cells in tracking area" modem will try to search for other - suitable - tracking area from the same network. This is why there is an immediate search after the reject.

    A NB-IoT device is not supposed to move, so the chance of finding another tracking area is very slim? In case of my test device this will loop and drain the battery.

    %PERIODICSEARCHCONF is used in periodic searches. It is not related to above scenario for example. Periodic search state is entered after modem has scanned all supported bands and no suitable cell was found. Then modem continues to search for a suitable cell periodically - at that point the %PERIODICSEARCHCONF is followed.

    So this only works in case of CEREG:4? And not in case of receiving a EMM cause of the network.

Related