OPS Forum CCSDS spacecraft monitoring & control 04.05.2007

CCSDS Spacecraft Monitoring & Control: a step towards the future

CCSDS Spacecraft Monitor & Control Working Group (SM&C)Mario Merri (ESA), Chair

SpacecraftMonitoring& Control

Working Group

OPS-G Forum - CCSDS SM&C: a step towards the future4 May 2007

2

Presentation Motivations and Agenda

Communicate and promote our standardisation effortShare SM&C approach with decision makers for future missionsDissipate unjustified fears (e.g. re-use of legacy systems, pre-defined system architecture, prescribed functionalities)Share benefits of application-level services and not only communication protocol standardisation

Agenda covers main SM&C WG responsibility, i.e. standardisation in the context of:

Spacecraft Monitoring & Control (SM&C)Status, strategy and outlookOverviewPrototype

XML Telemetric and Command Exchange (XTCE)Very brief status and outlook


Working Group


3

SM&C in Numbers

3 year lifetime(started in Dec 2003)

10 active Space Agencies1 partner standardization

organization7 CCSDS workshops42 telecons

OMG: R. Andzik (RT Logic), B Kizzort (Harris Corp.)

■ XTCE Splinter Group

ASI: C Labonia

BNSC: R Thompson (deputy chairman), S James

CNES: B Béhal, E Poupart, R Soumagne

CSA: P Melanson

DLR: H Hoffman

ESA: M Merri (chair), M Schmidt, A Ercolani, I Dankiewicz, S Cooper

FSA: L Kudrin

INPE: PG Milani, AM Ambrosio

JAXA: T Yamada

NASA/GSFC: D Smith, M Kearney, JK Marquart, JS Gal-Edd, C Fatig, R Jones, K RiceNASA/JPL: A Oyake, P Shames


Working Group


4

SM&C in Numbers



organization7 CCSDS workshops42 telecons2 published GBs3 internal Reviews (SM&C)2 Agencies Reviews (XTCE)3 advanced draft HP SM&C

RBs

Mission Operations Service Concept, CCSDS 520.0-G-2, August 2006

http://public.ccsds.org/publications/archive/520x0g2.pdfWeb hits: 158 in Feb 06; 259 in Jan 07

XML TELEMETRIC AND COMMAND EXCHANGE (XTCE), CCSDS 660.0-G-1, July 2006

http://public.ccsds.org/publications/archive/660x0g1.pdfWeb hits: 303 in Feb 07; 445 in Jan 07

SM&C Message Abstraction Layer (ESA)SM&C Common Service (ESA)SM&C Core Service (ESA)

OMG-approved XTCE specs is currently under adoption by CCSDS


Working Group


5

SM&C in Numbers



organization7 CCSDS workshops42 telecons2 published GBs3 internal Reviews (SM&C)2 Agencies Reviews (XTCE)3 advanced draft HP SM&C

RBs2 versions of SM&C prototype1 advanced draft XTCE MB

Simulator(ESA)

Simulator(ESA)

Apex(SciSys)

Apex(SciSys)

X3DMon(Logica)

X3DMon(Logica)

Aggregations

Actions

Verification

Alerts

Status

Behaviour

Violations

Actions

Verification

Alerts

MCS(CNES)

MCS(CNES)

V2: Jan 07

(BNSC/Logica)

(BNSC/SciSys)

Simulator(ESA)

Simulator(ESA)

Apex(SciSys)

Apex(SciSys)

X3DMon(Logica)

X3DMon(Logica)

Actions

Status

V1: Jun 06(BNSC/SciSys)

(BNSC/Logica)


Working Group


6

SM&C in Numbers



organization7 CCSDS workshops42 telecons2 published GBs2 Agencies Reviews (XTCE)3 internal Reviews (SM&C)3 advanced draft HP SM&C

RBs2 versions of SM&C prototype1 advanced draft XTCE MB4 initial draft SM&C RBs

SM&C Time Service (CSA)SM&C Remote Software Management (BNSC)SM&C Automation Service (CNES)SM&C Planning Service (BNSC)


Working Group


7

Spacecraft Monitoring and Control

What it isComprises application level services that are needed to monitor, control and operate a remote system including:

Classical TM monitoringTC generation (manual, pre-planned, automatic, time-tagged, …)Remote software managementTime managementMission product data managementMission planning and automationOrbit, Attitude and Position determinationStandard interaction with the operator… more to come

What it is notDoes not prescribe the system architecture and functionality

service provider/consumer may be located differently depending on the specific deploymentNo predefinition of applications’ implementation, but only of their management interfaces

Does not prescribe the technology to be used

Must allow expansion to accommodate future needs


Working Group


8

What Do we Want to Achieve?

Prepare for the futureFuture missions will be more complex and require more collaboration across organisation

Better interoperability between systems (e.g. X monitoring its lander via Y’s orbiter, Z submitting planning requests for its payload on W’s S/C, …)Scalability

Expandable systemsDifficult to predict now what will be needed tomorrow

Protect from technology evolutionReplace implementation technology without major system redesign

Reduce cost (i.e. schedule, risks, …) of[On-board and Ground-based] system development

Facilitate availability of generic software infrastructureFacilitate availability of new, state-of-the-art, plug-in [commercial] components

Re-use components (including legacy systems)… and mission operations

Re-use operational concepts across missionsIncrease operational commonality across components (less training costs)


Working Group


9

How Can Standardisation Help?

Standardisation of interfaces for SM&CReduce cost of Flight Components and Ground Segment InfrastructureEnable “plug and play” architecture with components from different Agencies, systems and suppliers

SM&C Framework technology keywordsService Oriented ArchitecturePlug & PlayLayeringIsolation and Grouping of generic and common servicesPublish/SubscribeTechnology Adapters (e.g. integration of legacy systems)


Working Group


10

Why Application-Level Service Standardisation?

Protocol-Level standardisationis necessary (allows communication), but not sufficient for seamless plug-in of components and interoperabilitysome commercial world examples:

Bluetooth/InfraredUSBInternet (HTTP and TCP/IP)

Application-Level service standardisation

allows seamless plug-in of components and interoperabilityExamples

Calendar/Contacts/To do List/…managementPlug & Play of modern memory stickse.g. tailor-made holidays package (Expedia, LastMinutes, …)

Application Level Services

Generic Interaction Patterns

ConsumerApplication

ProviderApplication

Infrastructure ServicesMessage Exchange; File Transfer; Mail

Communications Services

SM&C Service Framework

SM&C Specific Applications

Technology Specific Infrastructure

? ?


Working Group


11

Integrated Systems vs. Modular Components


Working Group


12

Service-Oriented Architecture: Plug-in Components

Components

Services

Infrastructure


Working Group


13

Benefits of the SOA ApproachComponents exchangeable for others supporting same Service Interfaces

Plug-and-play interoperability of MCS components

Common Service FrameworkRe-use of common infrastructure across multiple systemsIndependence of mission configuration data and history from system implementation

Infrastructure Implementation can be changed without change to core Applications

Independence of core application software from underlying implementation technology – platform and communications

Components rapidly deployable in different combinationsReduced mission-specific deployment costs

Extensible: easy to add new componentsScope to evolve a system, by replacing components or changing underlying technologies

Success is dependent on the Granularity of the service architecture selected


Working Group


14

Goals of an SOA for Mission Operations (MO)

Standard “System of Systems”Enabler for Interoperability between AgenciesEnabler for Re-usable Product DevelopmentFlexible Deployment of Existing Infrastructure

Evolution not RevolutionShould not Prescribe implementation architecture:Systems (legacy or otherwise) only need to standardise at exposed interoperable interfacesExtensible to support New Technologies and Capabilities

CoherenceServices should work together to form a coherent system

Future-ProofingAbstraction from Comms Infrastructure TechnologyPortability of service-related Configuration Data and Historical Logs


Working Group


15

Relationship to other CCSDS Standards

Ground SegmentGround Segment Flight SegmentFlight Segment

ApplicationApplication Application Application Application Application Application

Mission Operations Services

GroundServices:

WSDL/SOAP/CORBA

Space Link Services:SLS, SIS, AMS, Other

On-boardServices:

SOIS


Working Group


16

I GraciouslyAccept

I GraciouslyAcceptShe has

Accepted I Shall Accept

End-to-End Communication:Information Concepts (Invitation: Who, What, Where, When)

Standard Pattern of Interaction (Invite, Respond)

Transport Layer:Packaging

PhysicalCommunications

Infrastructure

End-to-End Services and Layering

I shall Invite my

Sweetheart to a Ball

My Beau has Invited me to

a Ball

I’ll Invite my Girlfriend to a

Party

Hey, Babe,Wanna Come

to a Party?

Hey, Babe,Wanna Come

to a Party?My Boyfriend has Invited

me to a Party

I’ll Invite my Girlfriend to a

Rave

U 12 Come 2 Rave? You

Have Mail

My Boyfriend has Invited

me to a Rave

MissionOperations

MissionOperations

Thou art Invitedto a

Banquet

Thou art Invitedto a

Banquet

I shall Invite my Lady to a

Feast

My Lord has Invited me to

a Feast


Working Group


17

SM&C Service Layering (a)

SM&C: Mission Operations Services

SM&C: Common Services

ConsumerApplication

ProviderApplication

TechnologyAdaptors

SAP: Service Access PointPlug-inApplications

SM&C MO ServiceFramework

MO DomainSpecificApplications

TechnologySpecificInfrastructure



SM&C: Message Abstraction LayerMessage Exchange; File Transfer; Mail

Interoperable Protocol (PDUs)


Working Group


18

Identified SM&C MO Services

4Buffer: catalogue; retrieve; clearRemote Buffer Management

4Message/Alarm/Query: notify; operator responseOperator Interaction

4Orbit/Attitude/Predicted Events: determination, propagation, manoeuvre preparation

Flight Dynamics

3Position: tracking, ranging, onboard positioningLocation

3Data Product [Payload Data File]: directory; transferData Product Management

2Procedure/Function: control; progress reportingAutomation

3Schedule: distribute; edit; control; progress reportingScheduling

3Planning Request/Goal: request; responsePlanning

2On-board Software: load; dumpSoftware Management

2Time: report; set; correlate; notifyTime

1Parameters: publish status; setActions [Commands]: publish status; invoke/sendAlerts [Events]: notify; raise

Core Monitoring & Control

PriorityService Objects and OperationsName


Working Group


19

External UserMission Exploitation

Spacecraft

Ground Station

OCC

OB Data ProductStorageSpacecraft M&C OB Procedure

ExecutionOB Schedule

Execution OB Software

Tracking &Ranging

MissionPlanning

MissionData

Processing

ExternalUser

StationM&C

StationScheduling

OperationsPlanning

FlightDynamics

OperationsAutomation

OperatorInteraction

Analysis &Reporting

OB SoftwareManagement

Spacecraft M&CProxy

OB ScheduleProxy

OB ProcedureProxy

OB Data ProductProxy

OB SoftwareProxy

SM&C MO Services Deployment

Autom.Schedule

Products

Software

Location

Flt. Dyn.

SLE-Man

Planning

Reports

Interact.Time

M&C


Working Group


20

SM&C Common Services

MOServiceProvider

MOService

Consumer

MOService Directory

Common ServicesDirectoryAuthenticationSession Control

Common ServicesDirectoryAuthenticationSession Control

PUBLISH

LOOKUP

INVOKE


Working Group


21

SM&C Service Layering (b)

SM&C: Mission Operations Services

SM&C: Common Services

ConsumerApplication

ProviderApplication

TechnologyAdaptors

SAP: Service Access PointPlug-inApplications

SM&C MO ServiceFramework

MO DomainSpecificApplications

TechnologySpecificInfrastructure



SM&C: Message Abstraction LayerMessage Exchange; File Transfer; Mail

Interoperable Protocol (PDUs)


Working Group


22

Message Abstraction Layer (1)

Generic Interaction Patterns (InP)limited set used by MO services in the SM&C frameworkEach operation of a service uses one InP

seq SEND

ProviderConsumer

send SEND InP

REQUEST InP

ProviderConsumer

seq REQUESTrequest

response


Working Group


23

Message Abstraction Layer (2)

seq PUBLISH SUBSCRIBE

ProviderConsumer Broker

register

acknowledge

*publish

*notify

deregister

acknowledge

PUBLISH-SUBSCRIBE InP

Generic Interaction Patterns (InP)

Other features:Multiplicity of services (Session, Domain, Network Zone)Security and access controlQuality of Service


Working Group


24

Message Abstraction Layer (3)Interoperability (language and encoding/transport)

Application InteroperabilityApplication Interoperability


Entity InteroperabilityEntity Interoperability

Consumer Application in C++Consumer Application in C++

Mission Operations Service in C++Mission Operations Service in C++

Messaging Abstraction Layer in C++Messaging Abstraction Layer in C++

Encoding to XMLEncoding to XML

SOAP Message TransportSOAP Message Transport

Provider Application in JavaProvider Application in Java

Mission Operations Service in JavaMission Operations Service in Java

Messaging Abstraction Layer in JavaMessaging Abstraction Layer in Java



Protocol and Transport BridgingProtocol and Transport Bridging





Consumer Application in C++Consumer Application in C++

Mission Operations Service in C++Mission Operations Service in C++

Messaging Abstraction Layer in C++Messaging Abstraction Layer in C++



Messaging Abstraction Layer in CMessaging Abstraction Layer in C



Provider Application in JavaProvider Application in Java

Mission Operations Service in JavaMission Operations Service in Java

Messaging Abstraction Layer in JavaMessaging Abstraction Layer in Java

Encoding to Space PacketsEncoding to Space Packets

AMS Message TransportAMS Message Transport

Encoding to Space PacketsEncoding to Space Packets

AMS Message TransportAMS Message Transport

Between implementation languages

Between encoding and transport technologies


Working Group


25

SM&C CCSDS Books

Mission OperationsServices

Core, Automation, Scheduling, Time,…

Messaging Abstraction LayerGeneric Interaction Patterns

Consumer/Provider

Mission OperationsService Framework

CommonServices

Directory, Authentication

Messaging Technology

API

API

Language Specific APIsJava, C++, …

Technology BindingAMS, JMS, XML, …

BindingEncoding


Working Group


26

SM&C MO Service Prototype V2 Context

SM&C CoreSM&C MAL

AMS/JMS/SOAP

Network

Plug-in BNSC

SIM/ESA

SM&C CoreAdapter

SM&C MALAMS/JMS/SOAP

MCS 1/CNESSM&C CoreSM&C MAL

AMS/JMS/SOAP

MCS 2/JPLSM&C CoreSM&C MAL

AMS/JMS/SOAP


Working Group


27

Conclusions and Outlook

The Mission Operations Services will provide a framework for development of

Interoperable systems (across and within Agencies)Re-usable componentsSystems-of-Systems

At the last CCSDS workshop (Jan 07), NASA agreed to increase support to the SM&C effort while continuing to identify the candidate enabling technologies for the future Constellation Programme

Target planSM&C Message Abstraction Layer - end 2007SM&C Common Service - Q2/2008SM&C Core Service - Q2/2008