Skip to content

R1 features

Jump to bottom
rtp-calpoly edited this page Oct 13, 2014 · 2 revisions

The main objective for this software release (R1) is to provide a first software version of a system that permits:

  1. Mission Operators registering.
  2. Spacecraft Configuration.
  3. Ground Station Operators registering.
  4. Ground Station Configuration (no need for ASR rules).
  5. Spacecraft remote commanding through direct matching of compatible ground stations.

There is also to bear in mind that no security or privacy system is going to be implemented for this software release. This way, this first implementation can focus on providing a set of basic communications features between spacecraft and ground stations.

This first release will implement a very simple booking system for clients to directly make a reservation on the compatible ground stations that they required. This is more or less the definition for the scheduling services described in [AD-1], but the difference is that the N-System must not check whether the ground station will contact the spacecraft of the mission operator. Therefore, the planning and contact simulation for a given spacecraft is a task up to the spacecraft operators.

Feature 5 defines the direct data messages exchange after booking the remote utilization of a given ground station. In this case, M-Clients will start sending messages to the N-System, using as destination address the identifier of the ground station that they had previously booked. In case the ground station is not available or the booked operation slotted has not started yet, the N-System will report an error to this communication attempt. This protocol shall be defined in detail in document [AD-3].

Selected Use Cases

Management and Scheduling Services

These are the very simple management services that will permit the registration of new software clients in the system. In addition, it will also permit the configuration of spacecraft and ground stations.

The usage of the simple booking service for scheduling is also illustrated in the figures below.

Registration and configuration, mission operators

Registration and configuration, ground station operators

Typical Remote Spacecraft Operation

This is the typical remote spacecraft operation with no security or privacy mechanism. Besides, a simple error management mechanism is to be implemented.

Assisted Operation

Selected Requirements

  • General Requirements
    • USR-GEN-010, USR-GEN-020, USR-GEN-040, USR-GEN-050
    • USR-GEN-060, USR-GEN-070, USR-GEN-080, USR-GEN-090
    • USR-GEN-100, USR-GEN-110, USR-GEN-120, USR-GEN-130
  • System Access and Security Requirements
    • USR-ACC-010, USR-ACC-020, USR-ACC-060
  • Service Provision Requirements
    • USR-SRV-010, ONLY services 1, 2, 4, 6
    • Registration: USR-SRV-020, USR-SRV-050, USR-SRV-060, USR-SRV-070
    • Configuration (1): USR-SRV-080, USR-SRV-090, USR-SRV-100, USR-SRV-110
    • Configuration (2): USR-SRV-120
    • Scheduling: a new easy scheduling service for simple booking shall be defined in [AD-3].
    • Assisted Communications: USR-SRV-320, USR-SRV-350, USR-SRV-360
  • Implementation Requirements
    • USR-IMP-010, USR-IMP-030, USR-IMP-050, USR-IMP-090
    • The applicable interface definition for this requirements can be found at [AD-3]:
      • USR-IMP-040, USR-IMP-060, USR-IMP-070
Clone this wiki locally