Cellular coverage ends at the last tower. Devices working past that edge, ships at sea, sensors on remote infrastructure, and fleets crossing dead zones, have historically gone dark the moment the tower dropped out of range. Satellite IoT and direct-to-device connectivity are closing that gap, letting a standard device link straight to a satellite when terrestrial coverage runs out.

Satellite connectivity does not need to replace the cellular network to change how devices are built; it only needs to become the fallback a device reaches for automatically the moment the tower disappears.

What Is Satellite IoT and Direct-to-Device Connectivity?

Satellite IoT is the practice of connecting internet of things (IoT) devices directly to orbiting satellites for data transmission, with no ground-based cellular tower in the path. Direct-to-device (D2D) connectivity is the form that matters most here: a standard, unmodified device connecting to a satellite the same way it would connect to a cell tower, with no separate terminal or dish. For a broader primer, our guide to satellite communications covers the fundamentals.

Two orbital approaches sit behind satellite IoT connectivity, and they trade off along the same axis:

• Geostationary (GEO) satellites: fewer satellites cover a wider footprint each, at the cost of higher latency, since the signal travels much further to reach orbit and return.
• Low-Earth orbit (LEO) satellites: lower latency and faster data, paid for with large constellations and a radio that has to correct for Doppler shift as each satellite crosses overhead.

Three standards make direct-to-device satellite links workable. NB-IoT (narrowband IoT) and LTE-M, a low-power variant of LTE (Long Term Evolution), both run over satellite, and the 5G non-terrestrial network (NTN) specification folds satellite into the same standard as terrestrial 5G rather than treating it as a separate system.

Will Satellite Replace or Coexist With Terrestrial Networks?

Satellite is not positioned to replace terrestrial cellular. It is built to extend it, because satellite capacity, cost, and latency cannot yet match a terrestrial tower for dense, high-bandwidth traffic. Three constraints keep cellular in the primary role:

• Capacity: one satellite covers a footprint far larger than a cell tower, but shares that footprint across every device in view, which limits it to short, infrequent messages rather than sustained data.
• Cost and power: a satellite link draws more transmit power and more expensive spectrum access than a terrestrial connection, so a device defaults to cellular whenever a tower is in reach.
• Latency: a GEO satellite adds hundreds of milliseconds of round-trip delay from distance alone, which rules it out for time-sensitive traffic.

The result is a hybrid model. A device connects to cellular by default and falls back to satellite automatically the moment terrestrial coverage drops, using power-saving protocols so the satellite link does not drain the battery while idle. For a logistics operator, that fallback is what keeps a vehicle reporting across a dead zone, enhancing fleet visibility from the control centres rather than losing the asset until it returns to coverage. The same fallback logic underpins the wide-area sensor networks behind building smart cities. In some deployments, the satellite carries backhaul instead, moving traffic from a remote cell site to the core rather than linking to the device directly, and satellite backhaul of that kind extends a terrestrial network without changing the device at all.

The deeper shift is architectural. NTN standards fold satellite into the same network core as cellular, so IoT platforms treat a satellite-connected device the same as a cellular one. The device stops asking which network it is on and asks only whether it is connected.

What This Means for RF Engineering

Supporting both networks on one device is a harder radio frequency (RF) problem than supporting cellular alone, because satellite and cellular do not share a spectrum, a link budget, or an antenna requirement. Building a dual-mode satellite and cellular radio places four demands on the hardware:

• Link budget: a satellite link has to close over a distance many times greater than a terrestrial one, so the receiver front end and transmit power have to be engineered for a far weaker received signal.
• Antenna pattern: a terrestrial antenna favours the horizon, while a satellite antenna has to see the sky, which usually means two separate antenna designs on one board rather than a single shared element.
• Doppler correction: a LEO satellite moves fast enough overhead that the received frequency shifts as it passes, and the radio has to track and correct that shift in real time.
• Radio coexistence: a device already balancing cellular, GNSS (global navigation satellite system), Wi-Fi, and Bluetooth Low Energy now has to fit a satellite radio onto the same board without one radio desensitising another.

None of these are solved by firmware after the fact. They are set in the board layout, the antenna placement, and the front-end component selection, which is where a satellite IoT device either holds its link or loses it in the field.

Designing and Manufacturing the Hardware Behind Satellite-Ready Devices

PCI is the electronics manufacturing services (EMS) partner that designs and builds hybrid satellite and cellular hardware for devices meant to operate past the reach of a tower. That work spans the parts of the problem set during design:

• Dual-mode RF design: electronic and RF hardware design for combined satellite and cellular radios, with the link budgets and coexistence worked out from the first board revision.
• Antenna engineering: separate sky-facing and horizon-facing antenna designs resolved on the same board.
• Power architecture: supply designed for the higher transmit demands of a satellite link without compromising idle battery life.
• Certification: test and certification support, including PTCRB certification, which qualifies a cellular device for use on a live network.

These sit within PCI's broader EMS capability, backed by over 50 years of experience taking connected hardware from design to scaled production.

Conclusion

Satellite IoT is not replacing terrestrial cellular. It is becoming the fallback a device reaches for the moment the tower disappears, which makes dual-network capability a hardware question long before it is a coverage question. Getting the RF, the antennas, and the power architecture right is what decides whether a device holds that fallback link in the field. To design and build satellite-ready hardware, or to fold connectivity into a wider deployment through our Internet of Things (IoT) Smart Manufacturing Solutions, talk to PCI as your electronics manufacturing partner.

Frequently Asked Questions

What Is the Satellite Direct-to-Device Connectivity?

Satellite direct-to-device (D2D) connectivity lets a standard, unmodified device connect straight to a satellite, the same way it would connect to a cell tower, with no separate satellite dish or terminal in between. It gives devices a path to the network in places where terrestrial coverage does not reach, such as open water, remote sites, and the coverage gaps between towers.

Will Satellite Internet Replace Cellular Networks?

No. Satellite is set to extend cellular coverage, not replace it. A terrestrial tower still carries dense, high-bandwidth traffic at lower cost, power, and latency than a satellite link can, so devices default to cellular and fall back to satellite only when terrestrial coverage drops. Non-terrestrial network standards make that handover part of one connected system rather than two separate ones.