IoT-NTN in 2026: Complete Guide to LTE-M, NB-IoT and Satellite IoT Architecture

Introduction: What Is IoT-NTN?

The Internet of Things (IoT) is transforming how industries monitor equipment, track assets, manage agriculture, measure environmental conditions and operate connected devices. However, traditional terrestrial cellular networks cannot provide reliable coverage everywhere. Remote agricultural fields, oceans, deserts, mountainous regions, mining sites and isolated industrial locations may remain outside conventional cellular coverage.

IoT-NTN (Internet of Things over Non-Terrestrial Networks) addresses this connectivity challenge by extending cellular IoT technologies through satellite-based and other non-terrestrial communication platforms. It enables supported IoT devices to exchange information with a cellular network when conventional ground-based coverage is unavailable or insufficient.IoT-NTN

The 3rd Generation Partnership Project (3GPP) introduced standardized support for IoT connectivity over non-terrestrial networks in Release 17. This work extends LTE-based low-power wide-area technologies, particularly LTE-M and Narrowband Internet of Things (NB-IoT), to satellite environments.IoT-NTN

Unlike a conventional terrestrial IoT connection, where a device communicates directly with a nearby cellular base station, an IoT device operating over a transparent satellite payload sends its radio signal through a satellite platform. The signal is relayed toward an NTN Gateway and then processed by a ground-based LTE eNB.

This architecture combines established LTE radio access and Evolved Packet Core (EPC) networking with satellite connectivity. It provides a standardized foundation for extending IoT services into areas where terrestrial infrastructure is difficult, expensive or impractical to deploy.IoT-NTN

In this guide, we will explore the complete architecture, the functions of each network component, uplink and downlink data flows, the differences between LTE-M and NB-IoT, technical challenges, practical applications and the role of satellite IoT in the evolving 5G and 6G ecosystem.

IoT-NTN Satellite Network

Table of Contents

1. What Is IoT-NTN?

2. Why Is Satellite IoT Important?

3. Understanding the IoT-NTN Architecture

4. Major Components of the IoT-NTN Network

5. How IoT-NTN Uplink Communication Works

6. How IoT-NTN Downlink Communication Works

7. The Role of LTE-M and NB-IoT

8. IoT-NTN vs NR-NTN: Key Differences

9. Transparent Payload vs Regenerative Payload

10. Technical Challenges in Satellite IoT

11. Real-World Applications of IoT-NTN

12. Advantages and Limitations

13. IoT-NTN and the Future of 5G/6G

14. Skills Required for IoT-NTN Engineers

15. Frequently Asked Questions

16. Conclusion

    
    

1. What Is IoT-NTN?

IoT-NTN refers to the use of non-terrestrial networks to support cellular IoT communications based on LTE-M and NB-IoT. Non-terrestrial networks use communication platforms such as satellites and, in broader NTN architectures, high-altitude platforms to provide connectivity beyond the reach of conventional terrestrial infrastructure.

The technology builds on existing LTE-based IoT radio interfaces while introducing enhancements needed to address satellite-specific challenges. These include longer propagation delays, differences in satellite movement, extended radio paths and changing coverage conditions.IoT-NTN

In a conventional LTE network, an IoT device communicates with an eNB through a terrestrial radio link. The eNB connects to the EPC, which routes user traffic toward the appropriate data network.

In a transparent satellite architecture, the device's radio signal travels through a satellite payload that relays the signal toward a ground gateway. The ground-based eNB performs the principal cellular baseband processing, allowing the system to retain much of the established LTE network architecture.

Key characteristics

• Uses LTE-M and NB-IoT radio technologies with NTN-specific enhancements.

• Supports communication through suitable satellite or non-terrestrial platforms.

• Can extend IoT coverage into remote areas without requiring a local terrestrial base station at every location.

• Can reuse established LTE radio access and EPC architecture.

• Supports IP-based application connectivity through the packet core.

• Requires appropriate satellite coverage, compatible devices, supported frequency bands and a suitable service deployment.

An important distinction is that IoT-NTN is not simply an ordinary LTE connection transmitted through any satellite. The radio interface, timing behavior, device capabilities and network configuration must support the relevant NTN requirements.IoT-NTN

2. Why Is Satellite IoT Important?

Terrestrial cellular networks are designed around geographically distributed base stations connected through transport infrastructure. Although this approach works well in populated areas, it becomes challenging in locations where installing and maintaining ground infrastructure is difficult.

Satellite connectivity offers an alternative way to extend communications over large geographical areas.

2.1 Connectivity beyond terrestrial coverage

Consider a soil-moisture sensor installed on a farm located far from a cellular tower. The sensor may need to report measurements periodically, but installing a dedicated base station could be economically impractical.

A supported satellite-connected IoT device can transmit its information through a compatible NTN service, allowing the data to reach a ground network and an agricultural application.

2.2 Lower-power IoT communication

LTE-M and NB-IoT were developed for low-power wide-area applications. They support device categories and operating modes suited to applications that exchange relatively small amounts of information rather than continuously streaming high-bandwidth data.

Satellite communication still consumes energy, and actual battery life depends on coverage, transmission conditions, reporting frequency and implementation. Nevertheless, these technologies provide a useful foundation for applications that do not require continuous broadband connectivity.

2.3 Support for remote industries

Potential applications include agricultural monitoring, maritime asset tracking, environmental sensing, industrial telemetry and infrastructure monitoring.

The important benefit is the combination of standardized cellular IoT communication and an extended service footprint. The exact coverage, supported devices and service availability depend on the satellite operator and the deployed network.

3. Understanding the IoT-NTN Architecture

The architecture discussed in this article focuses on a transparent satellite payload with a ground-based LTE eNB and EPC.

A simplified representation is:

IoT-NTN UE ⇄ Transparent NTN Payload ⇄ NTN Gateway ⇄ IoT-NTN eNB ⇄ EPC ⇄ Data Network

For uplink communication, information travels from the device toward the application. For downlink communication, application data travels in the opposite direction.

3.1 IoT-NTN UE

The User Equipment (UE) is the IoT device that communicates with the network. It may be a sensor, tracker, meter or another compatible device implementing the required LTE-M or NB-IoT functionality.

The UE performs radio processing, encodes information according to the applicable protocol, transmits radio signals and receives information sent by the network.

Depending on its implementation, it may send user data, access-stratum signaling, non-access-stratum signaling and other protocol information.

3.2 Transparent NTN payload

The transparent payload acts primarily as a radio relay. It receives the uplink radio signal, performs applicable radio-frequency operations and retransmits the signal toward the ground gateway.

On the downlink, it receives the signal from the gateway and relays it toward the IoT device.

Depending on the implementation, operations can include frequency translation, filtering and amplification. The payload does not perform the complete LTE eNB baseband processing in the architecture considered here.

This distinction is fundamental: the satellite relays the radio signal, while the ground eNB handles the principal cellular radio processing.

3.3 NTN Gateway

The NTN Gateway provides the radio-frequency connection between the satellite payload and the terrestrial network infrastructure.

On the uplink, it receives the signal relayed by the satellite and delivers it to the ground-based eNB. On the downlink, it transmits the signal received from the terrestrial network toward the satellite.

The feeder link between the gateway and a transparent payload is implementation-specific in the architecture described here. Its detailed implementation is not equivalent to the standardized UE-to-satellite service link.

3.4 IoT-NTN eNB

The evolved Node B (eNB) is the LTE base station responsible for radio access processing.

It processes uplink signals received through the gateway, handles relevant radio protocols and forwards user traffic toward the EPC. For downlink communication, it schedules transmissions, selects applicable radio parameters and generates the LTE-M or NB-IoT radio signal.

Because the eNB remains on the ground, its integration with the terrestrial transport network and core network can follow established LTE deployment principles, with the required NTN configuration and enhancements.

3.5 Evolved Packet Core

The EPC provides packet-core connectivity for the LTE-based system.

Important components include:

• Serving Gateway (S-GW): Routes user-plane packets between the radio access network and the packet core.

• Packet Data Network Gateway (P-GW): Connects the EPC to external packet data networks and supports relevant IP connectivity functions.

• Mobility Management Entity (MME): Handles control-plane mobility and session-related procedures in the LTE/EPC architecture.

• Home Subscriber Server (HSS): Stores subscriber-related information used by the network.

The precise signaling and user-plane procedures depend on the deployed configuration. The components listed above describe the traditional EPC context relevant to the architecture in this guide.

3.6 Application or data network

The external data network hosts the service that consumes or generates IoT data. It may include an IoT platform, industrial monitoring system, cloud application, analytics service or asset-management platform.

An Access Point Name (APN) identifies the relevant packet data network connection in the LTE/EPC context.

For example, an environmental sensor may send a temperature measurement to a cloud application, where the information is stored, analyzed and presented on a dashboard.

4. How IoT-NTN Uplink Communication Works

Uplink communication means sending information from the IoT device toward the network or application.

Consider a remote temperature sensor that needs to report a reading to a monitoring platform.

Step 1: The UE generates information

The sensor measures temperature and generates data for transmission. Depending on the application, the device may also send status information, alarms or protocol signaling.

The UE prepares the information using its supported LTE-M or NB-IoT protocol stack.

Step 2: LTE-M or NB-IoT radio processing takes place

The UE performs the necessary baseband processing to prepare the transmission. This includes the applicable coding, modulation and physical-layer operations for the selected radio technology.

The UE's radio-frequency subsystem then transmits the resulting signal over the supported service link.

Step 3: The transparent payload receives the signal

The satellite payload receives the uplink radio-frequency signal transmitted by the device.

In the architecture described here, the payload observes the relevant uplink channel bandwidth and relays the composite signal from the IoT-NTN cell.

Depending on the implementation, it can translate the signal's frequency to the carrier frequency used for the feeder link. RF filtering and amplification may also be applied.

Step 4: The signal reaches the NTN Gateway

The transparent payload relays the signal to the ground gateway over the feeder link.

The gateway receives the RF signal and supplies it to the ground-based LTE eNB for cellular processing.

Step 5: The eNB processes the uplink

The eNB performs the relevant baseband and protocol processing to recover information transmitted by the UE.

After the appropriate radio and protocol processing, user-plane traffic is forwarded toward the EPC.

The eNB also handles applicable signaling and radio-resource procedures. User data and control signaling follow their respective protocol paths rather than being treated as identical traffic.

Step 6: The EPC routes the IP packets

For IP-based user traffic, the eNB forwards packets toward the appropriate S-GW. The S-GW forwards them toward the P-GW through the applicable bearer and core-network interfaces.

The P-GW provides connectivity to the relevant external data network, selected according to the network configuration and APN.

Step 7: The application receives the data

The application receives the measurement and can store it, display it, trigger an alert or use it for analytics.

The complete uplink path can therefore be summarized as:

IoT Device → Satellite Service Link → Transparent Payload → Feeder Link → NTN Gateway → LTE eNB → S-GW → P-GW → IoT Application

The satellite transports the radio signal, while the ground eNB and EPC perform their respective network functions.

5. How IoT-NTN Downlink Communication Works

Downlink communication is the reverse process: information travels from an application or data network toward the IoT device.

Suppose an industrial monitoring application needs to send a configuration update to a supported remote sensor.

Step 1: The application generates a packet

The data network generates the IP packet containing the information intended for the IoT device.

The packet enters the EPC through the relevant packet data network connection.

Step 2: The P-GW forwards the packet

The P-GW routes the packet toward the appropriate S-GW using the configured user-plane path.

The packet may travel through a GTP-based S5/S8 bearer, depending on the EPC deployment.

Step 3: The S-GW forwards the packet to the eNB

The S-GW forwards the packet to the relevant eNB over the applicable user-plane connection, traditionally using the S1-U interface.

The eNB identifies the appropriate UE context and prepares the radio transmission.

Step 4: The eNB schedules radio resources

The eNB scheduler determines the radio resources and transmission parameters appropriate for the selected device and transmission.

These decisions may include the available resource allocation, transport-block size and modulation and coding scheme (MCS), subject to the radio technology, channel conditions and applicable procedures.

For a downlink transmission, the device monitors the relevant control-channel signaling, including the Physical Downlink Control Channel (PDCCH) where applicable, to identify its scheduling information.

Step 5: The signal travels to the NTN Gateway

The eNB generates the relevant LTE-M or NB-IoT downlink radio signal and supplies it through the terrestrial transport and gateway arrangement.

The NTN Gateway transmits the signal toward the transparent payload over the feeder link.

Step 6: The transparent payload relays the signal

The payload receives the downlink RF signal and performs the applicable RF operations. These may include frequency translation, filtering and amplification, depending on the implementation.

It then transmits the signal toward the IoT-NTN coverage area.

Step 7: The UE receives and processes the data

The intended UE receives the downlink signal and performs the necessary LTE-M or NB-IoT baseband processing to recover the transmitted information.

The device can then apply the configuration update, acknowledge the message or deliver the information to its application.

The downlink path can be summarized as:

IoT Application → P-GW → S-GW → LTE eNB → NTN Gateway → Transparent Payload → Satellite Service Link → IoT Device

Uplink and downlink use the same broad network architecture but perform different radio, scheduling and packet-routing operations.

6. The Role of LTE-M and NB-IoT

LTE-M and NB-IoT are complementary cellular IoT technologies designed for low-power, wide-area connectivity.

Both provide a foundation for satellite IoT, but their capabilities and design priorities differ.

Feature	LTE-M	NB-IoT
Technology family	LTE-based eMTC	Narrowband LTE-based IoT
Primary focus	Low-power IoT with greater flexibility for mobility and throughput	Low-data-rate IoT with narrowband operation
Bandwidth characteristics	Wider than NB-IoT	Narrowband operation
Typical application profile	Trackers, mobile assets and connected equipment	Meters, fixed sensors and periodic telemetry
NTN support	Requires compatible LTE-M NTN implementation	Requires compatible NB-IoT NTN implementation
Device power consumption	Depends on coverage, traffic and configuration	Depends on coverage, traffic and configuration
Satellite suitability	Suitable for supported use cases and deployments	Suitable for supported use cases and deployments

Neither technology is universally better. The appropriate choice depends on data volume, mobility requirements, latency expectations, device capabilities, coverage and the satellite service being deployed.

For example, an asset-tracking application with mobility requirements may favor LTE-M if the complete service supports the required behavior. A sensor sending small periodic measurements may be a candidate for NB-IoT.

In either case, terrestrial compatibility alone does not guarantee satellite compatibility. The device, radio interface, supported bands and network must implement the relevant NTN capabilities.

7. IoT-NTN vs NR-NTN: Key Differences

IoT-NTN and NR-NTN both extend cellular radio access through non-terrestrial networks, but they use different radio technology families.

Parameter	IoT-NTN	NR-NTN
Radio technology	LTE-M and NB-IoT	5G New Radio
Radio access node in the architecture discussed	eNB	gNB
Core-network context	EPC for the LTE architecture described here	Commonly 5G Core in a 5G-system deployment
Main target	Low-power IoT and small-data communication	Broader 5G services, subject to implementation
Service link	Enhanced LTE-M or NB-IoT radio interface	NTN-capable NR radio interface
Transparent payload option	Yes	Yes
Ground-based radio processing	LTE eNB	NR gNB
Typical use cases	Remote sensors, telemetry and IoT tracking	Supported broadband, IoT and other NR services

A critical point is that the distinction between IoT-NTN and NR-NTN is primarily the radio technology and corresponding system architecture, not simply the presence of a satellite.

Both can use transparent payloads. However, their radio procedures, protocol stacks, network interfaces and applicable standards differ.

8. Transparent Payload vs Regenerative Payload

Satellite payload architecture affects where radio processing occurs.

Transparent payload

A transparent payload primarily relays the radio signal between the service link and feeder link.

Its functions can include frequency translation, RF filtering and amplification. In the architecture described in this article, the eNB remains on the ground and performs the principal LTE baseband processing.

Advantages include a comparatively simple satellite payload and the ability to maintain many network-processing functions on the ground.

Regenerative payload

A regenerative payload performs additional processing onboard the satellite. Depending on the architecture, it may include some or more radio access network functions.

This changes how the satellite platform interacts with ground gateways and the rest of the network. It can enable architectural options that are not available in the same way with a purely transparent relay.

Regenerative architectures also introduce additional requirements for onboard processing, software, platform resources and network integration.

Comparison table

Parameter	Transparent payload	Regenerative payload
Main satellite role	RF relay	Relay plus additional onboard processing
Main radio-processing location	Ground eNB in this architecture	Depends on the functions deployed onboard
Satellite processing complexity	Generally lower	Generally higher
Ground eNB dependency	Central to the described architecture	Depends on the functional split
Maintenance model	Many changes can be made on ground equipment	Onboard functions may require additional operational planning
Feeder-link visibility	Direct gateway visibility is required in the described arrangement	Requirements depend on architecture and supported operating modes

The main limitation of transparent payloads

A transparent payload generally requires the NTN platform to have direct visibility of an appropriate NTN Gateway for the feeder-link connection in the architecture described here.

Gateway visibility, gateway placement, satellite coverage and feeder-link availability therefore influence service continuity.

A transparent architecture can simplify the satellite platform, but it does not eliminate satellite-link constraints or the need for NTN-specific radio enhancements.

9. Technical Challenges in Satellite IoT

Extending LTE-based IoT communication to satellite environments introduces several engineering challenges.

9.1 Propagation delay

A satellite link generally introduces more propagation delay than a short terrestrial radio path. The magnitude depends on the satellite orbit, the geometry of the connection and the complete end-to-end route.

This affects timing-sensitive radio procedures and can influence application response times.

9.2 Satellite movement and changing coverage

Some satellite systems have moving coverage footprints, while other configurations seek to maintain Earth-fixed coverage using appropriate beam management.

As a satellite moves, the relative geometry between the UE, satellite and gateway can change. The network and device must support the relevant NTN mobility and timing behavior.

9.3 Frequency and Doppler effects

Relative movement can introduce Doppler frequency shifts. Frequency uncertainty and timing differences must be addressed through appropriate NTN-specific mechanisms.

The details depend on the supported radio technology, orbit, terminal capabilities and implementation.

9.4 Link budget and radio conditions

The received signal level depends on factors such as transmit power, antenna characteristics, path loss, frequency, atmospheric conditions and receiver performance.

Satellite IoT devices may have compact antennas and limited power budgets, so link-budget analysis is important when selecting the service, device and deployment configuration.

9.5 Device power consumption

Low-power operation is an important IoT requirement. However, a satellite connection can require additional energy when the device faces difficult radio conditions, repeated transmission attempts or longer access procedures.

Battery-life estimates must therefore account for real operating conditions rather than relying only on terrestrial network figures.

9.6 Gateway and feeder-link availability

The transparent architecture depends on a suitable gateway connection. Gateway visibility and feeder-link availability can affect the ability to relay traffic between the satellite and terrestrial network.

9.7 End-to-end interoperability

A working service requires more than a compatible radio module. The UE, satellite payload, gateway, eNB, EPC and application environment must work together using supported configurations.

Testing should cover radio access, timing, signaling, packet delivery, failure scenarios and application-level behavior.

10. Real-World Applications of IoT-NTN

The technology is relevant wherever devices need to transmit relatively small amounts of information from locations that are poorly served by terrestrial networks.

10.1 Smart agriculture

Agricultural sensors can monitor soil conditions, temperature, humidity and water availability. Satellite connectivity can help connect supported devices in remote fields.

The resulting data can inform irrigation decisions and improve visibility into field conditions.

10.2 Maritime asset tracking

Ships, buoys and other maritime assets can operate beyond terrestrial cellular coverage. Supported satellite IoT services can transmit location, status and sensor measurements to monitoring applications.

The exact device and service requirements depend on the maritime use case.

10.3 Environmental monitoring

Remote weather stations and environmental sensors can report temperature, water levels, air-quality measurements and other observations.

This is particularly relevant when the monitoring site is located far from terrestrial communication infrastructure.

10.4 Remote infrastructure

Oil and gas installations, pipelines, power infrastructure and remote industrial equipment may require periodic telemetry from geographically isolated locations.

Satellite IoT can provide an alternative connectivity path where a suitable service is available.

10.5 Logistics and asset management

Containers, trailers and other mobile assets may require tracking or condition monitoring across regions with inconsistent terrestrial coverage.

LTE-M may be relevant for supported mobility-oriented use cases, while the final choice depends on device and satellite-service capabilities.

10.6 Disaster monitoring

After a natural disaster, terrestrial infrastructure may be damaged or inaccessible. Satellite-connected IoT devices can support monitoring applications when compatible equipment and network service remain available.

This should not be interpreted as a guarantee of uninterrupted connectivity during every disaster: satellite availability, gateway operation, device power and environmental conditions still matter.

11. Advantages and Limitations

Key advantages

• Extended reach: Supports connectivity in areas beyond conventional cellular coverage.

• Standardized cellular foundation: Builds on LTE-M and NB-IoT technologies.

• Ground-based network processing: A transparent architecture keeps the main eNB processing on the ground.

• Remote monitoring: Enables supported sensors to report information from isolated locations.

• Potential infrastructure savings: Can reduce the need to build terrestrial infrastructure in some remote locations.

• Multiple industry applications: Can support agriculture, maritime operations, environmental sensing and industrial telemetry.

Important limitations

• Satellite coverage requirements: Service depends on the satellite network and its coverage footprint.

• Propagation delay: Satellite paths generally introduce additional latency.

• Power constraints: Device energy consumption depends on actual link and traffic conditions.

• Specialized device requirements: The UE must support the relevant NTN capabilities.

• Feeder-link dependency: Transparent architectures depend on an appropriate gateway connection.

• Service availability and cost: Commercial availability, subscription terms and regional coverage vary.

• Limited suitability for high data rates: LTE-M and NB-IoT target IoT communication, not unrestricted broadband applications.

A sound engineering design evaluates these limitations against the actual application requirements instead of assuming that satellite connectivity is the best solution for every IoT deployment.

12. IoT-NTN and the Future of 5G/6G

Non-terrestrial connectivity is an important part of the broader effort to integrate satellite and terrestrial communication systems.

3GPP Release 17 established standardized NTN support for both NR-based services and LTE-based IoT technologies. Subsequent releases continue to evolve NTN capabilities and investigate additional architectural and performance improvements.

The broader direction is toward more integrated connectivity across terrestrial and non-terrestrial infrastructure. This can help service providers support devices in locations where terrestrial coverage is limited.

For IoT, the long-term opportunity is not necessarily to replace terrestrial networks. It is to complement them, allowing supported devices to use suitable connectivity according to the application, location and available service.

In 2026, engineers working in this area should understand both the established LTE/EPC architecture and the NTN-specific radio and system considerations. Knowledge of NR-NTN and 5G Core can also be valuable when working across different satellite-network architectures.

However, individual capabilities and commercial deployment status must be verified against the applicable release, specification and operator implementation. A feature under study or standardization should not automatically be treated as universally available in deployed networks.

13. Skills Required for IoT-NTN Engineers

Engineers entering satellite IoT and NTN development benefit from a combination of cellular protocol knowledge and satellite communication fundamentals.

Recommended technical skills

LTE and LTE-M fundamentals: Understand LTE architecture, radio procedures, protocol layers and the differences between LTE-M and conventional LTE operation.

NB-IoT protocol knowledge: Learn narrowband radio operation, device procedures, signaling and the requirements of low-power IoT communication.

RAN architecture: Understand the roles of the UE, eNB, radio interface, scheduling, physical-layer processing and network signaling.

EPC and packet-core fundamentals: Study the MME, HSS, S-GW, P-GW, bearer architecture and packet-routing procedures.

NTN architecture: Understand transparent and regenerative payloads, service links, feeder links, gateways, satellite movement, propagation delay and Doppler effects.

Protocol testing and troubleshooting: Learn how to analyze signaling messages, radio logs, packet flows and failures across the device, radio access network and core network.

Satellite link-budget fundamentals: Understand the relationship between frequency, path loss, antenna gain, transmit power, receiver performance and link margin.

5G and 6G evolution: Develop familiarity with NR-NTN, 5G Core and the evolution of integrated terrestrial and non-terrestrial networks.

A practical learning plan should connect protocol theory with call flows, log analysis, architecture diagrams and test scenarios.

14. Frequently Asked Questions

Q1. What does IoT-NTN stand for?

IoT-NTN stands for Internet of Things over Non-Terrestrial Networks. It extends supported cellular IoT connectivity through non-terrestrial communication infrastructure.

Q2. Which technologies are used in IoT-NTN?

The principal LTE-based technologies are LTE-M, also known as enhanced Machine-Type Communication (eMTC), and NB-IoT.

Q3. Which 3GPP release introduced IoT-NTN support?

3GPP Release 17 introduced standardized support for NB-IoT and LTE-M operation over NTN, alongside NR-based NTN developments.

Q4. What is the role of a transparent satellite payload?

A transparent payload primarily relays radio signals between the UE-facing service link and the gateway-facing feeder link. Depending on the implementation, it may perform frequency translation, filtering and amplification.

Q5. Does the eNB remain on the ground?

Yes. In the transparent-payload architecture described in this article, the LTE eNB is ground-based and performs the principal cellular baseband processing.

Q6. What is the difference between the service link and the feeder link?

The service link connects the IoT device to the satellite payload. The feeder link connects the satellite payload to the NTN Gateway. Their frequencies, radio configurations and implementation details depend on the network design.

Q7. How does user data reach the Internet?

In the EPC architecture described here, uplink user traffic is processed by the ground eNB and routed through the S-GW and P-GW toward the appropriate external data network. Downlink packets follow the reverse user-plane path.

Q8. Is IoT-NTN the same as NR-NTN?

No. IoT-NTN uses LTE-M and NB-IoT, whereas NR-NTN uses 5G New Radio. Both can support non-terrestrial connectivity, but their radio technologies and corresponding protocols differ.

Q9. Can IoT-NTN work everywhere?

Not automatically. Connectivity depends on satellite coverage, supported frequencies, device compatibility, gateway availability, regulatory conditions and the commercial service offered in a particular region.

Q10. What should an engineer learn to work on satellite IoT?

Start with LTE, LTE-M, NB-IoT, RAN architecture and EPC. Then learn NTN architecture, satellite link budgets, timing and Doppler considerations, protocol testing and packet-flow troubleshooting.

Conclusion

IoT-NTN extends LTE-based IoT connectivity beyond the reach of conventional terrestrial infrastructure by integrating supported LTE-M and NB-IoT radio technologies with non-terrestrial communication platforms.

In a transparent-payload architecture, the UE transmits through the satellite service link, the payload relays the radio signal toward an NTN Gateway, and the ground-based eNB performs the main radio processing. The EPC then routes user traffic toward the appropriate application or data network. Downlink communication follows the reverse path.

Understanding this architecture requires knowledge of the radio interface, satellite payload, feeder link, gateway, eNB and EPC, together with the timing and link-budget challenges associated with satellite communication.

As terrestrial and non-terrestrial networks continue to evolve, engineers who understand LTE-based IoT, NR-NTN, core-network architecture and protocol testing will be better prepared to contribute to satellite connectivity projects.

Want to build your knowledge of 4G, 5G, NTN and telecom protocol testing? Explore the technical training programs offered by Apeksha Telecom / The Telecom Gurukul and strengthen your understanding of cellular architecture, protocol analysis and emerging telecom technologies.

External References

For further technical reading, consult the following standards resources.

• 3GPP TR 36.763: Study on NB-IoT/eMTC Support for Non-Terrestrial Networkshttps://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3747

• 3GPP Work Item 860033: Study on NB-IoT/eMTC Support for NTNhttps://portal.3gpp.org/desktopmodules/WorkItem/WorkItemDetails.aspx?workitemId=860033

• 3GPP Specifications Portal: Official specifications for LTE, NR and related cellular technologieshttps://www.3gpp.org/DynaReport/Specs.htm

• ETSI Standards: Telecommunications standards and technical specificationshttps://www.etsi.org/standards