Mars network relay operations involve the coordination of lander and orbiter teams through long-term and short-term planning, tactical changes and post-pass analysis. Much of this coordination is managed through email traffic and point-to-point file data exchanges. It is often difficult to construct a complete and accurate picture of the relay situation at any given moment, as there is no centralized store of correlated relay data. The Mars Relay Operations Service (MaROS) is being implemented to address the problem of relay coordination for current and next-generation relay missions. The service is provided for the purpose of coordinating communications sessions between landed spacecraft assets and orbiting spacecraft assets at Mars. The service centralizes a set of functions previously distributed across multiple spacecraft operations teams, and as such greatly improves visibility into the end-to-end strategic coordination process. Most of the process revolves around the scheduling of communications sessions between the spacecraft during periods of time when a landed asset on Mars is geometrically visible by an orbiting spacecraft. These "relay" sessions are used to transfer data both to and from the landed asset via the orbiting asset on behalf of Earth-based spacecraft operators. This paper will discuss the relay coordination problem space, overview the architecture and design selected to meet system requirements, and describe the first phase of system implementation
Implementation of a Relay Coordination System for the Mars Network
2010 IEEE Aerospace Conference ; 2010 ; Big Sky, MT, United States
2010-03-06
Aufsatz (Konferenz)
Keine Angabe
Englisch
Mars Relay Coordination Lessons Learned
British Library Conference Proceedings | 2005
|Mars relay coordination lessons learned
Tema Archiv | 2005
|Mars relay coordination lessons learned
IEEE | 2005
|Replenishing the Mars relay network
IEEE | 2014
|Summary of the Mars Relay Network
NTRS | 2019
|