• State Not Answered
  • Replies 6 replies
  • Subscribers 71 subscribers
  • Views 155 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 337295
Options

nRF9160 Modem transition to Idle state

Abdullah Javed

Hi,
we are using custom PCB with nRF9160.

we are writing a firmware for radio test lab. We are using LTE asynchronous in our firmware and LTE-M mode. We want the modem to stay connected to network for at-least 30 minutes. But we are facing an issue, where the modem goes to idle state after some time, and goes to connected state again, and then repeats this behavior as you can see in the image below. We believe this is due to the Network Inactivity timer

Our goal is to ensure that the modem remains connected to the network without entering the idle state during the test, maintaining a continuous connection. We do not want the modem to transition into idle mode due to inactivity.

We would like to handle this behavior at the firmware level. Is it possible to configure the modem to stay connected at all times and avoid transitioning into the idle state? If so, could you provide guidance on how we can modify the firmware or settings to achieve this? Is there any configuration or function in LTE Link controller API?

Thank you for your support.

Best regards,
Abdullah











Parents
  • 0

    Not sure, what you consider to achieve.

    In "RRC Active" (connected), the delays receiving data are pretty short. In "RRC Idle", these delays are longer (depends on eDRX or not), in my experience (south germany) it's about 2.5s without eDRX.

    If your device doesn't transmit something for these 30 minutes, why do you consider, that 2.5s delay will harm? And did you measure the energy consumption in "RRC active"? If you really need to stay "RRC active", you will need quite a lot of energy.

  • 0 in reply to Achim Kraus

    Hi Achim,

    This firmware is specifically for radio testing of the LTE connection (nRF9160). Power consumption is not an issue here, as we have a separate main firmware that handles that aspect.

    For this radio test firmware, transitioning to the Idle state affects our testing, so we need the RRC to remain active for at least 30 minutes. Currently, we are not explicitly sending or receiving any data, and it spends quite a long time in the Idle state.

    Best regards,
    Abdullah

  • 0 in reply to Abdullah Javed

    Hi Abdullah,

    RRC connection release is controlled by the network. You cannot force modem to keep connection alive because modem always releases the connection when requested by the network.
    If you are using some kind of tester/simulator, it might be possible to achieve what you want from the tester side. Another possibility is to use Production Test Image (PTI) modem firmware which is intended for production testing. It supports AT commands for Tx and Rx RF testing. This is common way of doing RF testing.

    Best regards,
    Dejan

Reply
  • 0 in reply to Abdullah Javed

    Hi Abdullah,

    RRC connection release is controlled by the network. You cannot force modem to keep connection alive because modem always releases the connection when requested by the network.
    If you are using some kind of tester/simulator, it might be possible to achieve what you want from the tester side. Another possibility is to use Production Test Image (PTI) modem firmware which is intended for production testing. It supports AT commands for Tx and Rx RF testing. This is common way of doing RF testing.

    Best regards,
    Dejan

Children
No Data
Related