Communication with Space Systems
Communication is a vital topic for remote systems which are usually not (directly) connected to the internet and only have 1-2 communication links during nominal operation. However, most of these systems have internet access during the development cycle. There are various standards provided by CCSDS which can be useful to determine how to communicate with the satellite and the primary On-Board Software.
Most communication with space systems is packet based. The sat-rs library provides some support
for the CCSDS space packet protocol, which the
Packet Format and TMTC Modelling chapter describes in detail.
- UDP TMTC Server. UDP is already packet based which makes it an excellent fit for exchanging space packets.
- TCP TMTC Server Components.
TCP is a stream based protocol, so the library provides building blocks to parse telecommands
from an arbitrary bytestream. Two concrete implementations are provided:
- TCP spacepackets server to parse tightly packed CCSDS Spacepackets.
- TCP COBS server to parse generic frames wrapped with the COBS protocol.
Working with telemetry and telecommands (TMTC)
The commands sent to a space system are commonly called telecommands (TC) while the data received from it are called telemetry (TM). One way to model the packet handling, which can be applied to most satellites, is to introduce the concept of a TC source and a TM sink. The TM sink is the one entity where all generated telemetry arrives in real-time. The most important task of the TM sink usually is to send all arriving telemetry to the ground segment of a satellite mission immediately.
Another important task might be to store all arriving telemetry persistently. This is especially important for space systems which do not have permanent contact like low-earth-orbit (LEO) satellites.
The diagram below shows an example of how the packet flow could look:
flowchart LR
subgraph OBSW[On-board software]
Dev[Device Handlers]
Sub[Subsystem Handlers]
Sink[TM Sink]
Radio[Radio Handler]
Udp[UDP Server]
Tcp[TCP Server]
Store[Persistent Storage]
end
Dev --> Sink
Sub --> Sink
Sink --> Radio --> Station[Ground Station]
Sink --> Udp --> UdpClient[UDP Client]
Sink --> Tcp --> TcpClient[TCP Client]
Sink --> Store
classDef creator fill:#b7e1a1,stroke:#4a8f2a,color:#000
classDef hub fill:#a9c8f0,stroke:#3a6fb0,color:#000
classDef transport fill:#d9d9d9,stroke:#7a7a7a,color:#000
classDef recipient fill:#f5c99b,stroke:#c0782a,color:#000
style OBSW fill:transparent,stroke:#888,stroke-width:2px,stroke-dasharray:6 4
class Dev,Sub creator
class Sink hub
class Radio,Udp,Tcp transport
class Station,UdpClient,TcpClient,Store recipient
The most important task of a TC source is to deliver the telecommands to the correct recipients. For component oriented software using message passing, this usually includes demultiplexing to determine where a command needs to be sent.
The diagram below shows one concrete example of how the packet flow could look.
flowchart LR
subgraph OBSW[On-board software]
Radio[Radio Handler]
Udp[UDP Server]
Tcp[TCP Server]
Source[TC Source]
Dev[Device Handlers]
Sub[Subsystem Handlers]
File[File Service Handler]
end
Station[Ground Station] --> Radio --> Source
UdpClient[UDP Client] --> Udp --> Source
TcpClient[TCP Client] --> Tcp --> Source
Source --> Dev
Source --> Sub
Source --> File
classDef creator fill:#b7e1a1,stroke:#4a8f2a,color:#000
classDef hub fill:#a9c8f0,stroke:#3a6fb0,color:#000
classDef transport fill:#d9d9d9,stroke:#7a7a7a,color:#000
classDef recipient fill:#f5c99b,stroke:#c0782a,color:#000
style OBSW fill:transparent,stroke:#888,stroke-width:2px,stroke-dasharray:6 4
class Station,UdpClient,TcpClient creator
class Source hub
class Radio,Udp,Tcp transport
class Dev,Sub,File recipient
Using a generic concept of a TC source and a TM sink as part of the software design simplifies the flexibility of the TMTC infrastructure: Newly added TM generators and TC receivers only have to forward their generated or received packets to those handler objects.