What exactly is CAP and why does satellite delivery matter?

The Common Alerting Protocol (CAP v1.2, standardised by OASIS and ITU-T as X.1303 bis) is an XML-based format that lets any authorised agency send a single structured alert message simultaneously over every compatible dissemination channel — sirens, broadcast, SMS, and satellite. Satellite delivery matters because terrestrial mobile networks are the first infrastructure to fail in earthquakes, cyclones, and floods, precisely when alerts are most needed. A sovereign satellite relay ensures the message gets through regardless of the state of the ground network.

Can a small nation afford to own this capability, or is buying it as a service the only realistic option?

A sovereign, dedicated CAP-relay nanosatellite constellation of six to twelve units in LEO is achievable for $18–40 million in capital expenditure — comparable to two or three years of commercial service fees from providers like Iridium or Inmarsat at national scale. Ownership eliminates per-message fees, removes contractual usage caps imposed during peak demand (exactly when you need unlimited throughput), and keeps encryption keys under national control. Several middle-income nations including Indonesia and Kenya have already explored this model in partnership with ESA and national space agencies.

How does a satellite-delivered CAP message actually reach a citizen?

The alert authority encodes the event in CAP XML and transmits it via a secure uplink to the constellation. Each satellite in view re-broadcasts the message on licensed downlink frequencies to a network of ground receivers — which may be dedicated pagers, compatible mobile handsets, emergency broadcast decoders in public spaces, or IoT-linked sirens. The receiver decodes the CAP message and triggers the locally configured response: audio alarm, screen display, or automated physical activation. The satellite link specifically covers areas where mobile base stations are down or were never built.

Why not just use commercial LEO constellations like Starlink or Iridium instead of building a sovereign one?

Commercial constellations offer excellent coverage, but a nation using them for life-safety alerts is accepting several sovereign risks: the operator can throttle or suspend service under their terms of use or foreign government pressure; encryption keys and message logs reside with a foreign company; and service continuity is subject to the operator's commercial viability. Sovereign ownership means the nation controls priority queuing, authentication, and availability — and the system cannot be switched off by a foreign boardroom decision during a geopolitical crisis.

What is the realistic delivery latency from hazard detection to citizen alert via a LEO CAP relay?

End-to-end latency has three components: hazard detection and human or automated decision-making (variable, typically 2–15 minutes for a well-instrumented event); CAP message encoding and uplink to the constellation (seconds); and satellite-to-receiver broadcast (under 30 seconds for a constellation with adequate coverage). The bottleneck is almost always the human or sensor-to-decision step, not the satellite link itself. A well-architected sovereign system should target sub-60-second satellite relay latency from authorised transmission to receiver activation.

How do we ensure the alert system is not exploited by a bad actor sending false warnings?

Robust CAP implementations require digital signature chains: only authorised alerting authorities hold the private signing keys, and receiver hardware validates the signature before triggering an alarm. Nations should align their signing infrastructure with standards such as NIST SP 800-57 for key management and implement a public key infrastructure that ties alert authority identities to a national or regional trust anchor. A sovereign ground segment gives the nation full control over key issuance and revocation — impossible when the signing function lives inside a foreign commercial platform.

Does satellite CAP distribution require coordination with the ITU, and how long does that take?

Yes. Any new satellite system transmitting on radio frequencies must be coordinated through the ITU Radio Regulations process, including filing a network coordination request and potentially negotiating with existing operators whose frequencies overlap. For small LEO constellations this process has historically taken three to seven years, though ITU has piloted faster pathways for non-geostationary systems under recent World Radiocommunication Conference decisions (WRC-23). Nations should begin ITU filings in parallel with satellite design, not after.

What happens when multiple hazards occur simultaneously — can the system handle compound events?

CAP v1.2 supports concurrent, independently addressed alert messages, and a sovereign constellation can broadcast multiple events simultaneously as separate message packets. The design challenge is priority queuing when bandwidth is constrained: a sovereign operator can hard-code life-safety message priority above all other traffic, which commercial operators cannot guarantee contractually. Integration with compound-event forecasting pipelines (see related pages) allows pre-staged alert drafts to be transmitted automatically when threshold conditions are met, reducing human decision latency in multi-hazard scenarios.

6.8.4Live

Common Alert Protocol Distribution

Crowd of villagers gathered around a loudspeaker receiving an emergency flood warning announcement — Satellite-relayed CAP alerts reach flood-stricken Slovenian neighborhoods like Zalec before rising waters cut off ground communications entirely.

Satellite CAP Alert: Space to Community

1
Satellite relay
Broadcasts CAP XML alert message globally
2
Ground receive
National hub decodes satellite downlink signal
3
CAP aggregation
Alerts parsed, validated, and geo-targeted
4
Multi-channel alert
SMS, radio, sirens, and apps triggered

Satellites relay standardised CAP messages from authorities to national hubs, which instantly push geo-targeted warnings across every available channel.

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

6.8.3 · Previous

National Early Warning Platforms

All in multi-hazard warning systems

6.8.5 · Next

Multi-Hazard Risk Atlases

Bring this into your sovereign programme.

All solutions Speak with engineering