NTN Support and Application Feasibility on nRF9151

[Priyesh Shahi]

Inquiry: NTN Support and Application Feasibility on nRF9151

I would like to seek clarification regarding Non-Terrestrial Network (NTN) support on the nRF9151.

There have been discussions and references suggesting NTN capability on the nRF9151, and I would like to better understand the current level of support and practical limitations.

Specifically, I am interested in the following:

1. Resource Availability

• Which nRF Connect SDK versions include sample applications or support for NTN on nRF9151?

• Are there example projects, reference code, or documentation demonstrating NTN connectivity in practice?

• If official samples are not yet available, is there a roadmap or expected timeline for when they might be provided?

• What type of antenna is required or recommended for NTN operation on the nRF9151?

2. Application Feasibility

We are currently using the nRF9151 with a Hologram eSIM in India, and our solution is working reliably:

• connectivity

• Cellular IoT stack

• Data transmission to a CoAP server

Given this setup:

• Is a similar application architecture feasible over NTN?

• Can CoAP-based data transmission be supported over NTN in a comparable manner?

3. SDK Support and Examples

• I could not find any nRF Connect SDK samples, documentation, or application notes specifically related to NTN on nRF9151

• Are there any example applications, experimental features, or recommended references available?

• If not, could you please advise on the current status and roadmap for NTN support on nRF9151?

Any guidance, documentation links, or clarification would be greatly appreciated.

Thank you for your support.

[Benjamin]

Hi Priyesh,
To fill out some more information not already answered by Achim:

Which nRF Connect SDK versions include sample applications or support for NTN on nRF9151?

The NCS version you need is v3.2.0. 

We recommend starting with either of this two options:

• The Serial Modem Application (modem only apporach, AT commands)
• Asset Tracker Template configured for satellite connectivity.

Note: To ensure NTN support is correctly implemented, please refer to our dedicated NTN use case doc and NTN and TN use case doc, as the standard template is not configured for NTN by default.

If official samples are not yet available, is there a roadmap or expected timeline for when they might be provided?

Please reach out to the regional sales manager for your area as we cannot talk about roadmap on DevZone.

What type of antenna is required or recommended for NTN operation on the nRF9151?

We recommend reaching out to our antenna solution partners. They are equipped to provide detailed guidance on the most suitable antenna for your specific application.

NTN NB-IoT require optimal link conditions, and the choice of antenna depends on multiple factors, including whether the application supports both LTE and NTN or NTN alone, as well as the physical constraints of the product.

For applications targeting both LTE and NTN, it is essential to select a wideband antenna that can meet the performance and form factor requirements of both technologies. The antenna must support a broad frequency range to satisfy the performance criteria of LTE networks and the relevant satellite operators.

The nRF9151 SMA DK includes Taoglas (LTE/NTN/NR+) and Kyocera (GNSS) antennas.

If not, could you please advise on the current status and roadmap for NTN support on nRF9151?

The alpha version of the NTN modem FW is now public and can be downloaded here. This firmware is only for nRF9151 LACA A1 SiP.

Regards,
Benjamin

[Priyesh Shahi]

Hi Benjamin,

Thanks for the info.

Quick question:

Can we connect to a CoAP server over NTN like we do on cellular, or is NTN only for location updates?
Is custom payload upload supported beyond basic asset tracking?

Regards ,
Priyesh

[Benjamin]

Hi,
You could use AT+COPS? to check what type of network you are connected to. The value for NTN NB-IoT is 14.

I guess you are referring to the %LOCATION set command? What specific questions do you have?

Best regards,
Benjamin

[Priyesh Shahi]

Hi Benjamin,

Thank you for the clarification regarding AT+COPS?.

In my testing, I set the location of the room where the board was initially operating, and NTN connectivity worked there as expected. However, I then moved approximately 30 km away from that location, and the device continued to connect successfully using the same previously configured location.

This is where my confusion arises — how is the device able to connect to NTN with an incorrect location configured? Does the modem internally determine or refine its location even if the %LOCATION value is not accurate? Or is the configured location only used as an initial hint for acquisition?

Best regards,

Priyesh

[Benjamin]

Hi Priyesh,
That sounds strange indeed. If the modem is moved more than 400m during or in between connections you need to update the location. This can be done externally by using the %LOCAITON command or internally using a procedure involving the GPS. What exact firmware are you using?

Could you share a modem trace? That will help us see what exactly is going on.

Best regards,
Benjamin

[Priyesh Shahi]

Yes that's why i was thinking that it may be not ntn but the cellular. I have already added the code above. 

[Benjamin]

Yes, but I am referring to a modem trace. We'll need it to see the full picture. You can find instructions for enabling it in the DevAcademy. Please upload the file here so we can inspect it.