1. The message that had to be decoded before it could be understood

Carl Sagan’s Contact returns as the recalled work because the signal from Vega is not just a carrier; it carries a message encoded in a format the receivers must figure out. A LEO desktop faces a smaller version of the same problem. The radio waves carry bits, but those bits are meaningless unless both ends agree on the protocol: packet format, addressing, error handling, and what to do when the link disappears.

This entry reads about communications protocols, latency tolerance, and regulatory constraints.

A spacecraft communications protocol must work over intermittent, delayed, and noisy links. Common approaches include:

  • CCSDS protocols: standards from the Consultative Committee for Space Data Systems, including telemetry, telecommand, file delivery, and proximity-1 link protocols.
  • TCP/IP over space: possible but challenging because TCP assumes continuous connectivity and reacts poorly to long delays or dropouts.
  • DTN (Delay/Disruption Tolerant Networking): store-and-forward protocols designed for intermittent links, using bundles that can be held at intermediate nodes until the next hop is available.
  • Application-specific protocols: lightweight formats for telemetry, file transfer, or commanding tailored to the mission.

For the desktop, a hybrid approach is likely: CCSDS-like framing for critical command and telemetry, and DTN or file-based delivery for larger payload data.

3. Latency and store-and-forward

Latency tolerance depends on the application. A command to take an image can tolerate seconds or minutes. A real-time control loop needs milliseconds. A customer downloading a large dataset might tolerate hours if the data is reliably delivered.

Store-and-forward is the natural pattern for LEO: data is stored on board during the gap between passes and transmitted when a link is available. The platform needs buffers large enough to hold the data and autonomy smart enough to know which data to send first.

4. Regulatory constraints

Communications from space are regulated. Key constraints include:

  • Frequency licensing: the operator must obtain authorization to transmit on specific frequencies from the relevant national regulator, such as the FCC in the United States or Roskomnadzor in Russia.
  • ITU coordination: international registration of satellite networks to avoid interference.
  • Spectrum sharing: many satellites share bands; the license may impose power limits, duty cycles, or coordination requirements.
  • Export control: radios, cryptography, and related components may be subject to export restrictions.
  • Remote sensing licenses: if the payload images Earth, additional licenses may apply.

For a multi-jurisdiction platform like the desktop, the regulatory picture is complex. The operator must choose frequencies, licensing paths, and ground station arrangements that are workable across the relevant jurisdictions.

5. On-orbit communications autonomy

A LEO platform cannot wait for a human to decide every communications action. The autonomy must:

  • predict passes and compute link budgets;
  • prioritize data queues based on value and deadline;
  • select modulation and coding for current conditions;
  • detect link dropouts and resume transmission;
  • manage multiple radios or bands if available.

This autonomy is the bridge between the physical RF layer and the operational need to move data.

6. What this changes

  • Protocols must tolerate intermittent links and variable latency.
  • Store-and-forward is the normal mode for payload data.
  • Regulatory licensing is a design constraint, not an afterthought.
  • The next entry will close the communications reading arc.