Proposal for live telemetry data transfer

network

#1

Dear community,

Ever asked yourself how is it technically possible that ESA satellites can be controlled through NASA’s Deep Space Network?
The key is interoperability and standards.

ESA, NASA and many other public and private space organizations use the CCSDS Space Link Extension (SLE) services to route radio link frames between Ground Stations and Mission Control Centers.
An overview here: https://public.ccsds.org/Pubs/910x0g2.pdf

Although very successful and widely used among agencies and commercial entities, SLE is not well known to many others, including, likely, you!

Based on the great work in the scope of NASA’s open source multi-mission operations system (https://github.com/NASA-AMMOS/AIT-DSN),
we at LibreCube have created an SLE User package in Python that you can find here: https://gitlab.com/librecube/lib/python-sle-user
The SLE User sits typically at the Mission Control Center, to connect to remote Ground Stations that host an SLE Provider.

The SLE User, however, is only part of the solution.
Our team at VisionSpace Technologies has created an open source SLE Provider application: https://github.com/visionspacetec/sle-provider
Currently it supports Cortex baseband equipment, but work is underway to connect it with off-the-shelf, low-cost Software Defined Radios.

We are proposing the integration of the SLE services with SatNOGS, to enable live telemetry flow to data centers and mission control software.
The implemented SLE Provider and User are not limited to CCSDS compliant frames.

Interested? Try it out yourself, and get in contact with us!

Milenko Starcik @milenko
VisionSpace Technologies GmbH

Artur Scholz @artur
LibreCube Initiative


#2

It sounds really interesting! I think that at some point SatNOGS Network will have to implement such an interface towards the goal of adding transmitting capabilities. Of course, to get there we will have to solve a bunch of open issues like scheduling, link handovers as well as legal stuff.


#3

Hi @Acinonyx!

Great to hear that you see a need for this.

In the current version, there are no legal problems with forwarding frames and transmitting them, because the service for it has not been implemented yet.
When the frame forwarding service will be implemented in the future it will only be activated if you create an forward session on the SLE Provider and make it accessible to the public network SLE User.

The SLE Provider is designed to support simultaneous connection with multiple clients, each having different permissions.
A “Service Instance” (a scheduled pass with some properties like return or forward link) is bound to an SLE User and its traffic can be encrypted.
Using this you can have a public connection to the SatNOGS Network, hosting an SLE User and to your Mission Control System (MCS) at the same time. The SatNOGS User would only have a return telemetry service instance and the MCS could have return and forwarding service instances.
Because of the point-to-point architecture the delays for the MCS are kept low and also no telecommand data is ever being passes using the SatNOGS Network.

I hope this resolved some of your concerns but if anything remains unclear do not hesitate to ask :slight_smile: