NTN shines when:<\/p>\n\n\n\n
- \n
- You track in remote or infrastructure-limited regions (pastures, mountains, sea routes)<\/li>\n\n\n\n
- You need a \u201clast resort\u201d bearer that still delivers small messages<\/li>\n\n\n\n
- You want one backend experience, even when the bearer changes (cellular today, satellite tomorrow) (2)<\/a><\/sup><\/li>\n<\/ul>\n\n\n\n
What problem does NTN solve? for tracking<\/h2>\n\n\n\n
Tracking fails in the gaps. Not because the device is \u201coffline\u201d, but because coverage is uneven, and the last 5 percent of your route is often the most crucial part.<\/p>\n\n\n\n
Your tracker only needs to send small messages, but it needs to do it reliably, even when LTE-M or NB-IoT is missing, and even when your LoRaWAN<\/a> gateways<\/a> are miles away. Hybrid terrestrial + NTN is an advantageous approach, and GSMA explicitly frames NTN as a complement to terrestrial networks, not a replacement. (2)<\/a><\/sup><\/p>\n\n\n\n
We see this pattern a lot in real deployments: animals move past the last tower, assets cross borders and roaming becomes messy, or sites are temporary (events, seasonal farms, pop-up yards).<\/p>\n\n\n\n
NTN is the practical answer when you cannot justify building infrastructure (like installing gateways<\/a>), but you still need periodic proof-of-life and location reporting.<\/p>\n\n\n\n
How does NTN (Non-Terrestrial Networks) work?<\/h2>\n\n\n\n
NTN is still \u201ccellular thinking\u201d, just with a satellite in the link.<\/p>\n\n\n\n
A tracking device: Collects position (typically GNSS) > Builds a small payload (location, state, alarms) > Sends it over an NTN link to a satellite access node > Routes back into the operator and your IoT backend (similar to how cellular does it) (1)<\/a><\/sup><\/p>\n\n\n\n
Satellite bands (FR1 NTN):<\/strong> 3GPP<\/a> introduced new NTN bands n255 (L-band) and n256 (S-band), and ETSI TS 38.108<\/a> lists their uplink and downlink ranges.<\/p>\n\n\n\n
Important reality check:<\/strong> satellite links bring longer propagation delays and higher Doppler than terrestrial links, especially with LEO constellations; that is normal. That is why NTN tracking designs usually prefer short payloads, smart scheduling with tuned report intervals, and careful power planning with event-based alerts. (3)<\/a><\/sup><\/p>\n\n\n\n
LEO (Low Earth Orbit) vs GEO (Geostationary Orbit) for tracking<\/h2>\n\n\n\n
NTNs are networks or segments of networks that use either Uncrewed Aircraft Systems (UAS) or satellites in different constellations to carry transmission equipment, such as a relay node or base station.<\/p>\n\n\n\n
In the NTN tracking world, there are four <\/strong>options for \u201cwhere is the satellite flying,\u201d and those choices show up as latency, Doppler, and how often your device can see a satellite. <\/p>\n\n\n\n
- \n
- Low Earth Orbit (LEO):<\/strong> Circular orbit in altitudes of typ. 500-2.000km (lower delay and better link budget, but a larger number of satellites needed for coverage)<\/li>\n\n\n\n
- Medium Earth Orbit (MEO):<\/strong> Circular orbit in altitudes of typ. 8.000-20.000km<\/li>\n\n\n\n
- Geostationary Earth Orbit (GEO):<\/strong> Circular orbit 35.786 km above the Earth’s equator (Note: Due to gravitational forces, a GEO satellite<\/a> is still moving within a range of a few km around its nominal orbital position).<\/li>\n\n\n\n
- Highly Elliptical Orbiting (HEO):<\/strong> Elliptical orbit around the Earth. (1)<\/a><\/sup><\/li>\n<\/ul>\n\n\n\n
Typically, for tracking, LEO and GEO are the most popular options because of their characteristics. You do not need all the math, but you do need the trade-off.<\/p>\n\n\n\n
- \n
- LEO (Low Earth Orbit):<\/strong> moving satellites, fast-changing radio conditions, better \u201cresponsiveness\u201d in many cases, but Doppler matters.<\/li>\n\n\n\n
- GEO (Geostationary Orbit):<\/strong> more static geometry, typically higher delay, best for periodic messaging and \u201cjust get it through\u201d updates.<\/li>\n<\/ul>\n\n\n\n
Why is NTN (Non-Terrestrial Networks) different?<\/h2>\n\n\n\n
Coverage comes first.<\/strong><\/p>\n\n\n\n
NTN exists because terrestrial networks have edges, and those edges are \u0430 business risk.<\/p>\n\n\n\n
Hybrid is the winning pattern.<\/strong><\/p>\n\n\n\n
Most tracking deployments do not run satellite 24\/7. They use terrestrial bearers when available, and switch to NTN only when needed. GSMA explicitly discusses hybrid cellular\/NTN approaches for IoT. (2)<\/a><\/sup><\/p>\n\n\n\n
Bands are standardized.<\/strong><\/p>\n\n\n\n
3GPP<\/a> specifies dedicated satellite operating bands in FR1 NTN such as n255 and n256<\/strong>, with uplink and downlink ranges defined in ETSI TS 38.108. (4)<\/a><\/sup><\/p>\n\n\n\n
NTN vs LTE-M \/ NB-IoT \/ LoRaWAN for tracking<\/h2>\n\n\n\n
- GEO (Geostationary Orbit):<\/strong> more static geometry, typically higher delay, best for periodic messaging and \u201cjust get it through\u201d updates.<\/li>\n<\/ul>\n\n\n\n
- Medium Earth Orbit (MEO):<\/strong> Circular orbit in altitudes of typ. 8.000-20.000km<\/li>\n\n\n\n
- Low Earth Orbit (LEO):<\/strong> Circular orbit in altitudes of typ. 500-2.000km (lower delay and better link budget, but a larger number of satellites needed for coverage)<\/li>\n\n\n\n
![\"\"](\"https:\/\/www.lansitec.com\/wp-content\/uploads\/2025\/10\/New-LiveStock-Tracking-Tag_1.png\" "\\"\\""){kind=tracking}