1 — Autonomous local network
The city keeps operating if Earth contact disappears.
MARS BIBLE — REFERENCE GUIDE
Mars communications architecture: from local networks to the Deep Space Network
Rovers, habitats, orbital relays, UHF, X-band, large Earth antennas, store-and-forward and redundancy: design communication as permanent infrastructure.
ESTABLISHED FACTACTIVE ENGINEERINGPROSPECTIVE CHOICE
Why this deserves a full guide
Mars communication is not a single Mars-to-Earth arrow. A rover talks to an orbiter; the orbiter stores and forwards; large Earth antennas receive; a habitat then distributes data locally. Commands and software travel in the opposite direction through scheduled windows.
The current Mars Relay Network is already an early form of that architecture. NASA Science’s 2026 page describes an international four-orbiter relay constellation after MAVEN ended and explains why surface missions benefit from orbiters with more power, larger radios and better Earth contact.
1. Separate networks by scale
Inside a habitat, distances are metres and data rates can be huge. Base-to-mine links span kilometres, surface-to-orbiter visibility changes with orbit, and Earth links cross tens to hundreds of millions of kilometres. One technology cannot optimize every scale.
A hierarchy combines fiber and local radio, surface links, orbital relays and interplanetary communications, each with suitable power, antennas, bands and protocols.
2. Why the rover prefers the orbiter
Perseverance uses UHF around 400 MHz for orbiter relay and NASA lists rates up to roughly 2 Mbit/s under suitable conditions. The local distance is tiny compared with Earth.
Direct X-band remains important for telemetry and backup, but the small rover cannot match an orbiter designed with more power and stronger deep-space communications.
3. Store-and-forward accepts delay
The orbiter is not always overhead. Data waits on the rover, transfers during a pass, waits on the orbiter, and later travels to Earth. Production and path availability are decoupled.
A settlement can use the same principle at scale: urgent traffic gains priority while bulk files wait for suitable windows. The network becomes digital logistics.
4. The 2026 network shows that relays age
NASA declared MAVEN ended on June 3, 2026 and other orbiters absorbed relay demand. Orbital infrastructure is not permanent.
A human settlement must launch replacements before failure, maintain compatible standards and preserve spare capacity rather than wait for outages.
5. Deep Space Network: giant Earth segment
JPL operates DSN complexes in California, Spain and Australia, spaced so Earth rotation passes deep-space tracking from one complex to another.
The DSN provides communications and radio navigation, and will remain a major Earth-side dependency for Mars settlement unless comparable alternatives are built.
6. Capacity and priorities
Emergency alerts, medical results and safe-mode commands cannot wait behind non-urgent video. Traffic classes need explicit priority and reserved capacity.
Buffers, queues and emergency paths must be managed so bulk transfers cannot starve critical packets.
7. Path redundancy
Habitats may have primary and backup antennas, surface relays and multiple orbiters, but common power, software or location can defeat apparent redundancy.
Geographic diversity matters too: one local accident or power failure should not remove every communication path.
8. Solar conjunction and degraded seasons
When the Sun lies near the Earth-Mars line of sight, missions reduce complex commanding. A settlement should treat such periods as planned degraded-network seasons.
Caches, local procedures and pre-authorized decisions allow continued operations when Earth contact is reduced.
9. Cybersecurity and operational sovereignty
Networks commanding life-support and vehicles require authentication, segmentation and recovery. Earth cybersecurity response is delayed by light time.
Local teams need authority and tools to isolate compromised segments and restore trusted configurations.
10. The city local network
Fiber can link habitats, compute centers, power plants and laboratories while radio provides mobility and backup. Local services must not require Earth for every lookup or procedure.
Maps, medical data, manufacturing models, software and scientific databases need replicated local copies. Earth synchronization enriches local knowledge rather than replacing it.
11. Capacity grows faster than population
A few rovers mostly return telemetry and images; a city creates industrial, educational, medical, social and machine-to-machine traffic.
Architecture must add relay satellites, antennas and capacity without replacing the entire network. Open interfaces reduce lock-in.
12. Toward a Mars-orbit-Earth backbone
Long-term Mars settlement will likely need orbiters dedicated primarily to relay instead of science missions carrying relay as a secondary function.
A backbone can improve availability and data rate but cannot remove light time. Its purpose is a Mars-appropriate network, not a copy of terrestrial Internet behavior.
18. Network governance allocates scarce capacity
When capacity is constrained, technical design meets governance. Medical diagnostics, science, industrial backups and personal communication may compete. Opaque rules create conflict, while purely automatic rules can miss human context.
A settlement should publish priority classes, maintain exception procedures and log allocation decisions. Resilience is not merely having two antennas; it includes institutions capable of allocating scarce communication capacity transparently and reversibly.
17. Optical communications are a complement, not magic
NASA has demonstrated deep-space optical communications with DSOC and continues developing laser communications for higher data return. Narrow optical beams can support very high throughput, but they demand precise pointing and ground optical links are affected by clouds and atmospheric conditions.
A Mars architecture may therefore combine robust radio with high-rate optical links instead of treating one as an instant replacement for the other. Acquisition, optical ground stations, weather diversity and fallback paths belong in the architecture.
16. From telemetry to city-scale traffic
Robotic missions mainly exchange commands, telemetry and science data. A city adds medical data, education, delayed calls, software updates, backups, industrial models, large scientific files, entertainment and continuous machine-to-machine traffic.
Traffic classes need explicit service priorities. Non-urgent video should never delay a depressurization alarm or safety command. Congestion control becomes part of life-support architecture.
15. Contact windows follow orbital geometry
A low Mars orbiter is visible to a rover only during part of each pass. Contact duration depends on altitude, orbital geometry, terrain, antenna pattern and minimum elevation. Network planning therefore resembles a dynamic logistics schedule in which stored data waits for suitable passes.
Multiple orbiters in different planes can improve contact frequency, but every additional spacecraft creates launch, software, spectrum and replacement obligations. Coverage should be measured as achieved availability rather than satellite count.
14. Modulation and coding put bits on a wave
A carrier wave by itself is not a file transfer. A transmitter varies signal properties according to a modulation scheme and protects information using coding. Higher throughput in a difficult channel requires tradeoffs among robustness, power, spectral efficiency and complexity.
Error-correcting codes are especially valuable when retransmission is expensive in time. A receiver can reconstruct some corrupted information without asking for the same packet again. A Mars city therefore needs expertise in the digital layer as well as antennas and transmitters.
13. Frequency, band and channel are not synonyms
Frequency tells how many wave cycles occur each second. A band is a range of frequencies. A channel is an organized slice of that resource used for a link. A real communication design also specifies modulation, bandwidth, coding, power, polarization and regulatory constraints.
Changing band does not magically make the network faster. Performance depends on the full link budget, available bandwidth, noise, antenna gain, pointing and coding. The best band for a rover-to-orbiter hop is not necessarily the best band for an orbiter-to-Earth link.
23. Minimum operational glossary
Uplink sends toward a spacecraft or Mars; downlink returns data. A relay receives then retransmits. Store-and-forward keeps data until a path becomes available. Bandwidth is the frequency resource used by a signal.
Data rate is information per unit time. Latency is delay. Quality of service defines traffic priority. Path redundancy provides alternative routes. A single point of failure is one component whose loss can end the entire service.
22. Last-resort communications
Main communications can fail because of power loss, antenna faults or relay loss. A last-resort path may offer very low data rate yet preserve health status, coordinates, emergency requests and minimal commands.
It must be exercised. An unused spare antenna, obsolete software or expired cryptographic key is not real redundancy.
21. Data synchronization and conflicts
Mars and Earth may edit local copies of the same document before the next synchronization. The system then needs explicit conflict rules: which version wins, how changes merge and how decisions are recorded.
This matters for procedures, software, medical databases and manufacturing models. Versioned replication is more realistic than pretending a remote file behaves like a terrestrial network drive.
20. Vital messages versus large files
A pressure alarm may be only a few bytes yet matter more than a multi-gigabyte science image. Priority does not follow volume. Routers and protocols should reserve minimum capacity for life-critical traffic.
At the same time, permanently starving science in the name of safety destroys mission value. Quality-of-service rules need measurable thresholds and transparent emergency policies.
19. Queue example: average throughput matters
Suppose a base creates 50 gigabytes while only 10 gigabytes can be transmitted. Forty remain queued. If the next contact can send 30 gigabytes but 20 new gigabytes are created meanwhile, the queue becomes 40 + 20 − 30 = 30 gigabytes. Capacity must therefore be compared with traffic generation over time.
A network sized only by peak instantaneous rate can accumulate permanent backlog. Operators need queue size, data age and recovery time as health metrics.
27. Communications operations become a permanent profession
A city network needs spectrum planning, relay scheduling, key management, anomaly response, antenna maintenance, software upgrades and traffic policy. These are continuous services, not tasks performed only during spacecraft arrival.
The Mars Bible should therefore treat communications staff and facilities as civic infrastructure. As the settlement grows, network operations centers, training, spare equipment and documented procedures become as normal as power-grid operations.
26. Optical and radio links can form a layered service
Radio links remain valuable for robust command, acquisition and operation through conditions that challenge narrow optical beams. Optical links can add very high data return when geometry, pointing and Earth weather permit. A layered design can schedule bulk transfers over optical while preserving radio command paths.
This is more realistic than declaring that lasers will simply replace radio. High-capacity systems need diversity because the reasons for optical outage and radio degradation are not identical. Diversity is useful precisely when failure modes differ.
25. Interoperability is strategic resilience
Mars infrastructure will likely include equipment built by different organizations and generations. Shared relay protocols, frequency coordination, authentication methods and data interfaces make it possible for new spacecraft to use existing infrastructure and for old assets to remain useful longer.
Closed or undocumented interfaces can turn one supplier into a long-term single point of failure. A city-scale architecture should therefore treat interoperable standards and test facilities as part of resilience, even when proprietary internal implementations remain.
24. Capacity planning needs a growth model
A settlement should forecast traffic by source: crew, science, industrial telemetry, software distribution, medical imaging, autonomous vehicles and backups. Machine traffic may grow faster than population because every new pump, rover and laboratory becomes a network node. Capacity planning therefore needs scenarios rather than a simple number of inhabitants.
The model should include degraded periods, not only average demand. A relay outage can create backlog that must later be drained while new traffic continues arriving. Reserve capacity is what allows the network to recover instead of remaining permanently congested after one bad week.
EXPERT LAYER — SYSTEM ARCHITECTURE
Treat data as cargo that needs multiple routes
A mature Mars communication architecture can store, prioritize, retransmit and reroute. Availability matters as much as peak data rate.
2 — Multiple orbital relays
No single orbiter becomes a global single point of failure.
3 — Degraded direct Earth path
A minimal direct link preserves command and telemetry when relay is unavailable.
4 — Storage and priority
Data waits safely and life-critical traffic goes first.
Check before depending on the system
- at least two critical traffic paths
- independent power for main stations
- enough storage for outages
- tested priority rules
- encryption and authentication
- inventory of Earth dependencies
- orbiter replacement plan
What this changes for a real Mars city
A real Mars society cannot treat communication as an optional commercial service. It is life-supporting infrastructure carrying commands, diagnostics, knowledge, coordination and the connection to Earth. Unlike electrical energy, a lost orbital contact window cannot be stored for later.
A reference network should therefore be judged by availability, margin, recovery time, degraded capability and path diversity—not merely impressive peak throughput.
Learn the calculations in Space Academy
Institutional and primary sources
Go further with Arcadia
This public guide stands on its own. Arcadia — Manual of the First Martian City develops these systems as an integrated city architecture.