ops forum virtual space system 07.11.2008

Nuno Sebastião (OPS-GIC), Mauro Pecchioli (OPS-GIC)

A Virtual Space System supporting Ground Validation

@ Copyright European Space Agency, 2008OPS-G Forum 07 November 2008 Slide 2

Outline of this Presentation

• The way we got here– The need for a Ground Systems

Validation Infrastructure

• Ground Systems Verification and Validation

– Concepts– Use cases– Current Status

• Operational Usage– Integration with Operational

Simulator Development

• Demo• Schedule• Summary


The way we got here


Motivation

Current Situation• Testing of ground systems

relies on multiple tools

• Many tools are specific for the system under test.

• Tools are often targeted at a specific validation phase or test scenario

• Each tool has its specific user interface and configuration data

• The same functionality is implemented by different tools in different ways

• The operational simulator is used for ground systems integration testing

Implications• Testers must familiarise with

different testing approaches and interfaces

• Configuration and test data must be developed and maintained multiple times

• Re-use of tests and data in different phases and for different systems is difficult

• Operational simulator is not mature enough at the time when it is required for systems testingAs many tests require generic TM/TC simulation capabilities, improvement is possible


The Process

1. Identify use cases, building upon the concepts introduced with PSS MkIII

2. Define test configurations that can support these use cases

3. Derive the requirements on a generic simulator and its components to support these test scenarios (GSTVi system)


GSTVi Objectives

One tool supporting the full cycle of ground systems technical validation

Isolated System Technical Validation

End to end Test Environment

Reduce effort to set-up test campaigns

Enable ‘delayed’ development of operational simulators

Augmented systems quality

Automated Verification of Systems Under Test using Automated Regression Testing (ART) Framework


GSTVi Definition Process


Use Case Analysis

• 14 Use Cases were selected to drive specification and design of GSTVi

• Use Case Specification:– Objective

– Systems and components under test

– Functionality to be tested

– External systems involved

– Interfaces to be supported

• Assemblies of GSTVi Components that can support these Use cases were defined

GS

TV

i

Ground Station Components

StationM&C

IFMSTCDS

TMTCS

Example – Ground Station Stand-alone Test

TM TC


Use Case / Assembly Coverage

MCS Component Test

NIS Component Test

TMTCS Component Test

IFMS/TCDS Component Test

Mission Simulator Component Test

EGSE Component Test

NIS Connectivity Test

TM/TC End-to-End Test

Simulation Campaign

Long Loop Mission Readiness Test (MRT)

Ground Station Stand-alone Test

Pre-pass Data Flow Test

MCS Isolated Testing

NIS Isolated Testing

TMTCS Isolated Testing

Ground Station Stand-alone Testing

Simulator Stand-alone Testing

NIS Connectivity Testing

Portable Satellite Simulator (PSS)

Long Loop Operational Simulation

ASSEMBLIESUSE CASE

Operational Simulation

Support of SVT´s NDIU Lite Test Assembly


Development Approach

• SIMSAT 4 based (Linux SLES 9 64 bits)

• Developed using the SMP2 Standard

• Extends SIMSAT 4 MMI with GSTVi specific Views

• Many GSTVi components have been derived from existing software and only a few are new developments

• GSTVi R1 use existing, proven ground models


GSTVi Overview


SIMULATION InfrastructureU

nifi

ed M

odellin

g

Fram

ew

ork (U

MF)

Simsat Runtime

Space Models (Generic Models, Emulators,

Specific Models)

Simulator Reference Architecture

Ground Models(Station back-end, Control Center)

GSTVi

Multi-purpose Operational Simulator

Simulus Tevalis UMF


MC

S

NIS

TM

TC

S

IFM

S/T

CD

SE

GS

E/F

EE

Sp

acecraft

TM/TC Spacecraft Model

MCS Model

NIS Model

TIF

EGSE / FEE I/F

Ground System under Test

GSTVi Component

Space/Ground I/F

SGM (SLE Model)

MCS DIF

IMBU (H/W)

IMBU I/FAIV System

Real Systems Simulated Systems

The big picture

Ground Segment Test and Validation Infrastructure


GSTVi Concepts

TTSCM

TT

C S

treams

GEM NISM

MCSM


Space Link Model

Ground Equipment Model

Network Interface Model

Mission Control System Model


GSTVi Concepts

TTSCM

TT

C stream

s

GEM NISM

MCSM


Space Link Model




NIS


GSTVi Concepts

TTSCM

TT

C S

treams

GEM NISM

MCSM


Space Link Model




MCS


GSTVi Concepts

TTSCM

TT

C S

treams

GEM NISM

MCSM


Space Link Model




MCS

MCSDIF


GSTVi Concepts

TTSCM

TT

C S

treams

GEM NISM

MCSM


Space Link Model




TMTCSBaseband Processing

TCDSIFMS

TM Channel Decoding IF & Modem Subsystem

IMBU

IMBU I/F

MCSDIF


GSTVi Concepts

TTSCM

TT

C S

treams

GEM NISM

MCSM


Space Link Model




TMTCSBaseband Processing

IMBU I/F TIF

MCSDIF


GSTVi Concepts

TTSCM

TT

C S

treams

GEM NISM

MCSM


Space Link Model




MISSIONSIMULATOR

IMBU I/F TIF

MCSDIF


GSTVi Concepts

TTSCM

TT

C S

treams

GEM NISM

MCSM


Space Link Model




IMBU I/F TIF

MCSDIF

ConfigurationDatabase

SCOS 2000MIB


Brief Component Description

• TM/TC S/C Model– Simulates the on-board processing of TM/TC data. – The level of simulation expected from the Model, frame, packet, or

parameter level, is configurable by the user.

• Supports the simulation of a limited number of PUS services, including amongst others:– command verification, – House Keeping telemetry generation, and – Time Reporting.

• The spacecraft behaviour simulation is supported by a mechanism that allows triggering of an action on receipt of telecommands that match given templates. Actions can be:– Modification of a telemetry parameter value within the model, – the execution of a script, – and/or the generation of telemetry packets.

S/C Models



• Spacecraft Specific Model Extension (SSME)– Extension mechanism allowing for the increase in the

accuracy of the spacecraft simulation by actual simulation of the spacecraft equipments.

– In order to support the development of a SSME by the user, the GSTVi provides a development environment for the model extensions, which relies on the simulation toolkit provided in the underlying simulation environment.

S/C Models



• MCS Direct Interface (DIF)– MCS Direct interface to a S/C Model via the TTC STREAMS communication

mechanism. – It provides the same interface as the NIS, and acts as an interface to a

telemetry source and telecommand sink. – It provides command uplink verification simulation, and supports the

injection of various transmission failures.

• TMTCS Interface (TIF)– Directly interfaces TMTCS to the S/C Model. – The component receives CLTU’s from TMTCS through an IFMS interface,

and transmits TC transfer frames to the S/C Model via TTC STREAMS.

• TMTCS SLE Ground Model (SGM)– This component supports the testing of the OCC components. It provides

an interface between a NIS and the S/C Model. – It simulates the functional behaviour of the TMTCS related to:

• the processing of TM/TC data, including the simulation of SLE services from the provider side, • the TMTCS files management, and the• exchange of monitoring and control data according to the standard M&C I/F used by STC.

Ground Models



• MCS Model• It provides a basic model of a SCOS-2000-based Mission Control System, easy

to configure, that can be used as a source of telecommand and a sink for telemetry.

• The MCS Model supports three levels of simulation: frame-level simulation, packet-level simulation, and parameter-level simulation.

• NIS Model• This component simulates the functional behaviour of the NIS related to the

processing of TM/TC data, including the simulation of a SLE user.

• On the OCC components side, it provides to a MCS an interface for telecommand transmission and telemetry and administrative messages reception.

• On the Ground Model side, it provides an interface to TMTCS for transmission of telemetry and reception of telecommand.

OCC Models


GSTVi

Operational Usage


Who are the costumers?

• Mission Data Systems (OPS-GD/FCT)

• Ground Stations (OPS-GF, OPS-ON)

• Infrastructure (OPS-GI)

@ Copyright European Space Agency, 2008

SCOS 2000 MIB

OPS-G Forum 07 November 2008 Slide 28

Configuration process

GSTVi Configuration

Data

RF Characteristics

SICF Files


Who Supplies the configuration Data?

Item Supplier

Mission SCOS 2000 MIB

Mission FCT (OPS-GD)

RF Characteristics OPS-ONV, OPS-ONF

SICF Files OPS-ONV


How do we configure GSTVi?

Infrastructure (OPS-GI)

Ground Station(OPS-GS/ON)

Mission Data Systems (OPS-GD + FCT)

Includes On-site support


GSTVi

Demo

@ Copyright European Space Agency, 2008

GSTVi Demo

• Mission Configuration Editor Demo (Both integrated and in a standalone browser).

• A Simsat foundation (Simsat Runtime Perspective)

• GSTVi Perspectives (S/C Model, SGM, NIS, MCS)

• Start MCS Model Processing (Show MCS Perspective)

• Load some commands in the Manual Stack and dispatch them

• Observe the TC reception on board the S/C (Frames received increased)

• Switch back to Command Verification View in MCS and verify that commands were successfully received on board the S/C (Stage 3 verification report).

• Show TM flowing out through the chain (S/C Model, SGM, NIS, SCOS).

OPS-G Forum 07 November 2008 Slide 32


GSTVi

Schedule


GSTVi Delivery Schedule

• PA Delivery -> Nov. 2008

• FA Delivery -> March. 2009

• EOW Delivery ->Oct. 2009


GSTVi

SummarySummary


The Way Forward

• Start with GSTVi for data systems development and testing– Consequence: Sim development can start later.

• Replace GSTVi TM/TC model with a mission specific high-fidelity simulator (using GETS in D1 to avoid immaturity of OBSW)

• Shorter development cycles through reuse of models and reference architecture.


Conclusions

• GSTVi: – Supports the technical validation of data systems involved

in TM/TC data exchange– Supports the full cycle of validation campaigns, from

isolated testing up to end-to-end ground segment tests– Builds upon the concepts introduced with PSS MkIII and

the operational experience gained with it– It relies on the general simulators infrastructure (SIMSAT,

SMP2, Ground Models)– It supports the operational simulator development

lifecycle– It provides a comfortable environment to execute tests

manually and automatically.


Thank you for your attention !

Let’s build the future

Let’s continue to build the future


Backups


Assembly A - MCS Isolated Testing (replayed TM)

Ground Model(MCS DIF)

DRRGSTVi SMP2 Model

SMP2 Interface

Other Component

External InterfaceSIMSAT

TM Path

TC Path

Mission Control System

TM Files

Component Under Test

LAN

This assembly allows testing the Mission Control System using the MCS DIF ground model. The MCS DIF replays telemetry frames read from a file and sends these frames to the MCS. The MCS DIF uses the services of the TM/TC data recorder and replayer (DRR) for reading the telemetry files.


Assembly B – MCS Isolated Testing (Simulated and replayed TM)

This assembly allows testing the Mission Control System using the MCS DIF ground model. The telemetry can be real-time simulated telemetry generated by the SCM and SSME GSTVi models, or can be telemetry read from a file via the TM/TC data recorder and replayer (DRR).

Ground Model

(MCS DIF)DRR

GSTVi SMP2 Model

SMP2 Interface

Other Component


TM Path

TC Path


TM Files

TT

C S

treams

SCM

User Supplied SMP2 Model

Component Under TestSSME

LAN


Assembly C – MCS Isolated Testing (Simulated and replayed TM – 2 sources)

This assembly allows testing the Mission Control System using the MCS DIF ground model. The telemetry can be real-time simulated telemetry generated by the SCM and SSME GSTVi models, or can be telemetry read from a file via the TM/TC data recorder and replayer (DRR). The telemetry can be read from a file by the MCS DIF or by the SCM.

Ground Model

(MCS DIF)DRR

GSTVi SMP2 Model

SMP2 Interface

Other Component


TM Path

TC Path


TM Files

TT

C S

treams

SCMUser Supplied SMP2 Model

Component Under TestSSME

DRR

TM Files

LAN


Assembly E – TMTCS Isolated Testing

This assembly allows testing the TMTCS in complete isolation from the rest of the ground segment using the TMTCS Interface (TIF) ground model to interface to the spacecraft, and the NIS and MCS model to simulate the mission control system. On the spacecraft side, the telemetry can be telemetry generated in real-time by the SCM and SSME GSTVi models, or can be telemetry read from a file via the TM/TC data recorder and replayer (DRR).

Ground Model(TIF)

DRR

GSTVi SMP2 Model

SMP2 Interface

Other Component

External Interface

SIMSAT

TM Path

TC Path

TMTCS

TM Files

TT

C S

treams

SCM



SSME

NISM

MCSM

LAN/WAN

LAN


Assembly F – G/S Stand-Alone Testing

This assembly allows testing the IFMS, TCDS and TMTCS ground station equipment in isolation from the rest of the ground segment. The IFMS/TCDS interfaces to the GSTVi IMBU hardware unit at baseband/IF level for exchange of telemetry and telecommand data. The TMTCS interfaces to the NIS and MCS models which simulate the mission control system. On the spacecraft side, the telemetry can be telemetry generated in real-time by the SCM and SSME GSTVi models, or can be telemetry read from a file via the TM/TC data recorder and replayer (DRR).

DRR

GSTVi SMP2 Model

SMP2 Interface

Other components

External Interface

SIMSAT

TM Path

TC Path

TMTCS

TM Files

SCM



SSME

NISM

MCSM

IFMS/TCDS

IMBU I/F

IMBU

LAN

LAN/WAN


Assembly H – NIS Connectivity Testing

This assembly allows testing the NIS and the connectivity between the NIS and the TMTCS located at the ground station and between the NIS and the mission control system. The NIS interfaces to the MCS model which simulates the mission control system. On the spacecraft side, the telemetry can be telemetry generated in real-time by the SCM and SSME GSTVi models, or can be telemetry read from a file via the TM/TC data recorder and replayer (DRR).

TMTCSTIF DRR

GSTVi SMP2 Model

SMP2 Interface

Other Component

External Interface

SIMSAT

TM Path

TC Path

TMTCS

TM Files

TT

C S

treams

SCM



SSME

MCSM

LAN LAN

NIS LAN/WAN


Assembly I – PSS

This assembly allows testing the TM/TC path through the full integrated ground segment and running data flow tests from the station front-end down to the MCS. The IFMS/TCDS interfaces to the spacecraft simulator via the IMBU and the IMBU I/F model. On the spacecraft side, the telemetry can be telemetry generated in real-time by the SCM and SSME GSTVi models, or can be telemetry read from a file via the TM/TC data recorder and replayer (DRR).

DRR

GSTVi SMP2 Model

SMP2 Interface

Other Component

External Interface

SIMSAT

TM Path

TC Path

TM Files

SCM



SSME

IFMS/TCDS

IMBU I/F

IMBU

LAN

TMTCSNIS

MCS

LAN/WAN

LAN


Assembly K – Long Loop Operational Simulation

This assembly allows testing the full set of ground data systems, including the actual G/S components sitting at the ground station and the OCC in realistic operational scenarios involving the operational spacecraft simulator. In this assembly, the GSTVi is only used to relay the telemetry and telecommand data. The IFMS/TCDS interfaces to the operational simulator via the IMBU, the IMBU I/F model and the SLE ground model (SGM). The SCM is only used for updating telemetry frame counters and generating idle frames when needed.

GSTVi SMP2 Model

SMP2 Interface

Other Component

External Interface

SIMSAT

TM Path

TC Path

SCM



IFMS/TCDS

IMBU I/F

IMBU

LAN

TMTCSNIS

MCS

LAN/WAN

LAN

LAN/WAN SGM

OperationalSimulator

TTC Streams


Assembly M – NDIU Ultra-Light

This assembly allows running system validation tests (SVT) in order to test the OCC components of the ground segment using the S/C interfacing to GSTVi via the FEE. This assembly also allows using the simulated spacecraft (SCM) in order to run data flow tests prior to the System Validation Tests. Switching the telemetry and telecommand flow from the simulated spacecraft (SCM) to the S/C via the FEE and the EGSE/FEE interface and vice-versa is possible at real time.

Ground Model

(MCSDIF)

EGSE/FEE I/F

GSTVi SMP2 Model

SMP2 Interface

FEE

Software Component


TM Path

TC Path

TT

C S

treams

Component under Test

LAN LAN

MCS

SCM


SSME

Other Component


Assembly N – Operational Spacecraft Simulator Testing

This assembly allows testing the operational spacecraft model part of the operational simulator. The operational spacecraft model does not interface to the mission control centre via the SLE ground model and the NIS, but via the MCSDIF model. The GSTVi MCS model simulates the mission control centre.

Ground Model

(MCSDIF)

GSTVi SMP2 ModelSMP2 Interface

Other Component

External Interface

SIMSAT

TM Path

TC Path


MCSM LAN

Operational SpacecraftSimulator

TT

C S

treams


Assembly Z – GSTVi Isolated Testing

This assembly is a specific test configuration used to test the Mission Configuration Database (MCDB) and the correct installation of GSTVi and MCDB on the target workstation. This assembly is not meant to be used for testing of the ground segment since it only uses simulation components. The TM/TC data recorder may be used by both by the MCS model and SCM to record the data sent and received by these models for further inspection and checking.

SLE Ground Model(SGM)

GSTVi SMP2 Model

SMP2 Interface

Software Component


TM Path

TC Path

TT

C S

treams

LAN

SCMUser Supplied SMP2 Model

SSME

MCSM

DRR

TM Files

TC Files

DRR

TC Files

TM Files

NISM LAN

ops forum virtual space system 07.11.2008

Technology

gstvi concepts opsg

test data

gstvi overview opsg

test functionality

test configurations

end test environment

different systems

setup test campaigns