1.4.5 — Direct-to-Device Ecosystems — maturity: live
Remote Workforce Mobility
Providing persistent, device-native satellite connectivity to workers operating in mines, pipelines, forestry blocks, offshore platforms and other infrastructure beyond terrestrial network reach.
When your workforce operates beyond cellular reach, satellite-native mobility is no longer a perk — it is an operational lifeline that a sovereign nation should not outsource.
Nations that extract resources, manage critical infrastructure or deploy defence and emergency personnel across remote terrain face a blunt operational problem: the workers are where the networks are not. Terrestrial LTE and 5G coverage economics never justify towers at a drill site 400 km from the nearest city, a forestry coupe in mountainous terrain, or an offshore gas platform. The result is a workforce that is effectively dark — unable to report incidents, receive safety instructions, or confirm task completion in real time. That silence carries legal liability, productivity loss and, at the extreme end, preventable fatalities.
Direct-to-device (D2D) NTN satellites dissolve that gap without requiring workers to carry specialist satellite terminals. Modern LEO constellations operating in Band 255 (n255) NTN spectrum, or leveraging 3GPP Release 17 NTN standards, can push IoT-grade messaging and, in the near term, broadband data directly to ruggedised 4G/5G handsets and wearables already in workers' pockets. The satellite stack adds the downlink margin — typically 20–25 dB above a standard cellular link budget — needed to close the link to a phone-sized antenna. Onboard edge processing handles store-and-forward where constellation gaps exist, and multi-orbit architectures (LEO for latency, MEO for coverage persistence) can be combined for critical sites.
The operational outcome is a workforce that is always reachable and always reporting. Supervisors in a central operations centre see live location, fatigue-sensor telemetry and task status for every person on a remote site. Emergency SOS reaches a national coordination centre in under 60 seconds. Incident response times collapse. Regulators receive automatic shift-end compliance logs. For a sovereign operator, this infrastructure doubles as a national asset: the same constellation that tracks a miner in a remote pit can serve military logistics convoys, disaster-relief teams and border-patrol units on the same frequencies and the same ground segment.
Frequently asked
Why can't we just buy airtime from Iridium or Inmarsat and call it done?
You can — and many nations do during early stages. The problem is that the vendor controls the encryption keys, the routing logs, the pricing, and the service continuity decision. In a geopolitical crisis or a trade dispute, that vendor may be compelled by its home government to degrade or terminate service. Owning the constellation means your workers stay connected regardless of third-party politics.
What device does the worker actually carry?
Modern NTN-capable handsets using 3GPP Release 17 NTN profiles work with existing LTE and 5G NR radios; no specialist satphone is required. For rugged environments, purpose-built devices from companies like Garmin, Somewear, or Iridium's Go! ecosystem remain options. A sovereign programme should specify open chipset standards (e.g. Qualcomm Snapdragon X75 NTN) to avoid single-vendor lock-in.
How does LEO compare to GEO for mobile worker connectivity?
GEO at 35,786 km introduces ~600 ms round-trip latency, which makes voice calls uncomfortable and real-time telemetry unreliable. LEO at 500–1,200 km delivers 30–80 ms latency, supporting voice-over-IP, push-to-talk, and lightweight video. The trade-off is that LEO requires a constellation of tens to hundreds of satellites to achieve continuous coverage, whereas a single GEO satellite covers a hemisphere.
What spectrum bands are used and who controls them?
NTN services for direct-to-device use L-band (1–2 GHz) and S-band (2–4 GHz) for their resilience to foliage and weather, with some systems using Ka-band for backhaul. Spectrum is licensed nationally but coordinated through ITU's Radio Regulations. A sovereign operator must file for orbital and frequency coordination under Article 9 and protect its filing from competing networks — a process that takes years and requires sustained political engagement at ITU.
Can a small nation afford to build this?
A 24-satellite LEO constellation using microsatellites (50–150 kg) can be built for $150–400 million depending on domestic industrial capacity — comparable to one or two years of airtime payments to a large commercial operator for a substantial remote workforce. Multilateral approaches, such as a regional consortium of smaller nations, can split capex while preserving shared sovereignty over the data and routing.
How do we handle emergency escalation — does this replace our emergency comms system?
No, and it should not try to. Remote workforce mobility is an operational, day-to-day capability. Emergency escalation — distress signalling, SAR coordination, mass casualty notification — requires dedicated capacity with guaranteed QoS and integration with COSPAS-SARSAT and national emergency management frameworks. The two systems should interoperate but be engineered and funded separately.
What cybersecurity obligations apply to satellite-connected field workers?
For maritime workers, IMO MSC.428(98) mandates cyber risk management in Safety Management Systems. For aviation, ICAO Annex 10 governs data-link security. For onshore industries, national frameworks typically reference NIST SP 800-53 or ISO/IEC 27001. The satellite link itself must use end-to-end encryption — relying solely on the space segment's native encryption is insufficient against nation-state intercept.
How long does it take to build and launch a sovereign NTN constellation?
Realistically, 5–8 years from programme authority to initial operational capability, assuming the nation has or is building domestic launch access. Procuring commercial rideshare launches (e.g. SpaceX Transporter) can compress the timeline to 3–5 years for a small constellation. Spectrum filing and ITU coordination often run in parallel and are typically the critical path item.