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.

1.4.5Live

Remote Workforce Mobility

Field worker using a laptop and satellite communication device at an outdoor remote work site — An engineer or architect planning at a construction site gains reliable connectivity through satellite direct-to-device networks.

Satellite Direct-to-Device Remote Worker Connectivity

1
LEO Constellation
Low-orbit satellites beam broadband directly downward
2
Direct Downlink
Signal reaches device without ground gateway
3
Edge Processing
On-device compression prioritises work traffic
4
Remote Worker
Laptop, tablet, or rugged phone stays online

LEO satellites beam data directly to worker devices, enabling full productivity at any remote location worldwide.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

1.4.4 · Previous

Consumer NTN Connectivity

All in direct-to-device ecosystems

1.4.6 · Next

Automotive Satellite Connectivity

Bring this into your sovereign programme.

All solutions Speak with engineering