This document briefly describes some considerations and variants for the communication architecture for the HSI mission.
Introduction and rationale
This document is to be an introduction of work that has to be performed in order to derive a communication arctitecture for the HSI and SDR missions, commonly referred to as MASSIVE missions.
Communication Architecture Overview
Consisting of:
Spacecraft TT&C (operations, strongly linked to satellite bus)
Own agreements with ground station network operators (KSAT, Leaf.space, others)
Agreements and services from satellite bus provider
Ground station and operations software
This links to:
Satellite operations tied to
Onboard operation system
Satellite providers operation methodology and ground (station) software
Payload operations tied to
Satellite providers data distrbution architecture through own/3rd party ground stations
Direct access from our own ground station
Satellite operation software (cannot be changed by us)
The satellite bus suppliers will, depending on our needs, deliver software for operating the satellites. When their specification is known, we can derive the need for our own mission planning/scheduling software.
Own payload/mission operation software
Software for interpreting data/distribute data will be needed and should be agnostic wrt. the operations software.
The Norwegian company Statsat are doing operations of the AIS-satellites and NORSat satellites. They now have four satellites operational, and a staff of only four-five people doing everything. They are in the process of re-writing their software based on the 5-6 years of experience they now have, in order to further simplify and stream-line operations. They are delivering an operational service for Kystverket, in addition to more ad-hoc support to research teams with other payloads on the NORSats. It could be very beneficial to try partner with them on mission software and control room ops.