Mission Operations Services by the CCSDS: a step towards the future. CCSDS Spacecraft Monitor & Control Working Group (SM&C) Mario Merri (ESA), Chair

Transcription

1 Mission Operations Services by the CCSDS: a step towards the future CCSDS Spacecraft Monitor (SM&C) Mario Merri (ESA), Chair

2 Presentation Motivations and Agenda Communicate and promote our standardisation effort Share SM&C approach with decision makers for future missions Dissipate 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 (SM&C) Status, strategy and outlook Overview Prototype XML Telemetric and Command Exchange (XTCE) Very brief status and outlook 2

3 SM&C in Numbers 3 year lifetime (started in Dec 2003) 10 active Space Agencies 1 partner standardization organization 7 CCSDS workshops 40 telecons ASI: C Labonia XTCE Splinter Group BNSC: R Thompson (deputy chairman), B Harnett 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: DC Lokerson, F Johnson, JK Marquart, JS Gal-Edd, C Fatig, R Jones, K Rice NASA/JPL: A Oyake, P Shames, J Moholt 3 OMG: G Simon (Lockheed Martin), B Kizzort (Harris Corp.)

4 SM&C in Numbers 3 year lifetime (started in Dec 2003) 10 active Space Agencies 1 partner standardization organization 7 CCSDS workshops 40 telecons 2 published GBs 2 Agencies Reviews (XTCE) 2 internal Reviews (SM&C) 3 advanced draft HP SM&C RBs Mission Operations Service Concept, CCSDS G-2, August rchive/520x0g2.pdf Web hits: 158 in Feb 06; 259 in Jan 07 XML TELEMETRIC AND COMMAND EXCHANGE (XTCE), CCSDS G-1, July rchive/660x0g1.pdf Web 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) 4

5 SM&C in Numbers 3 year lifetime (started in Dec 2003) 10 active Space Agencies 1 partner standardization organization 7 CCSDS workshops 40 telecons 2 published GBs 2 Agencies Reviews (XTCE) 2 internal Reviews (SM&C) 3 advanced draft HP SM&C RBs 2 versions of SM&C prototype 1 advanced draft XTCE MB Apex Apex (BNSC/SciSys) (SciSys) (SciSys) X3DMon (BNSC/Logica) (Logica) (Logica) Apex Apex (BNSC/SciSys) (SciSys) (SciSys) Verification Actions Status Behaviour Actions Status MCS MCS (CNES) (CNES) Verification Actions Aggregations V1: Jun 06 Simulator (ESA) (ESA) V2: Jan 07 Simulator (ESA) (ESA) Violations X3DMon (BNSC/Logica) (Logica) (Logica) Alerts Alerts 5

6 SM&C in Numbers 3 year lifetime (started in Dec 2003) 10 active Space Agencies 1 partner standardization organization 7 CCSDS workshops 40 telecons 2 published GBs 2 Agencies Reviews (XTCE) 2 internal Reviews (SM&C) 3 advanced draft HP SM&C RBs 2 versions of SM&C prototype 1 advanced draft XTCE MB 4 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) 6

7 Spacecraft and Control What it is Comprises application level services that are needed to monitor, control and operate a remote system including: Classical TM monitoring TC generation (manual, pre-planned, automatic, time-tagged, ) Remote software management Time management Mission product data management Mission planning and automation Orbit, Attitude and Position determination Standard interaction with the operator more to come What it is not Does not prescribe the system architecture and functionality service provider/consumer may be located differently depending on the specific deployment No predefinition of applications implementation, but only of their management interfaces Does not prescribe the technology to be uded Must allow expansion to accommodate future needs 7

8 What Do we Want to Achieve? Prepare for the future Future 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 systems Difficult to predict now what will be needed tomorrow Protect from technology evolution Replace 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 infrastructure Facilitate 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 missions Increase operational commonality across components (less training costs) 8

9 How Can Standardisation Help? Standardisation of interfaces for SM&C Reduce cost of Flight Components and Ground Segment Infrastructure Enable plug and play architecture with components from different Agencies, systems and suppliers SM&C Framework technology keywords Service Oriented Architecture Plug & Play Layering Isolation and Grouping of generic and common services Publish/Subscribe Technology Adapters (e.g. integration of legacy systems) 9

10 Why Application-Level Service Standardisation? Protocol-Level standardisation is necessary (allows communication), but not sufficient for seamless plug-in of components and interoperability some commercial world examples: Bluetooth/Infrared USB Internet (HTTP and TCP/IP) Consumer Application Provider Application Application Level Services?? Generic Interaction Patterns Application-Level service standardisation allows seamless plug-in of components and interoperability Examples Calendar/Contacts/To do List/ management Plug & Play of modern memory sticks e.g. tailor-made holidays package (Expedia, LastMinutes, ) Infrastructure Services Message Exchange; File Transfer; Mail Communications Services Technology Specific Infrastructure SM&C Specific Applications SM&C Service Framework 10

11 Integrated Systems vs. Modular Components 11

12 Service-Oriented Architecture: Plug-in Components Services Components Infrastructure 12

13 Benefits of the SOA Approach Components exchangeable for others supporting same Service Interfaces Plug-and-play interoperability of MCS components Common Service Framework Re-use of common infrastructure across multiple systems Independence 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 combinations Reduced mission-specific deployment costs Extensible: easy to add new components Scope to evolve a system, by replacing components or changing underlying technologies Success is dependent on the Granularity of the service architecture selected 13

14 End-to-End Services and Layering End-to-End Communication: Information Concepts (Invitation: Who, What, Where, When) Standard Pattern of Interaction (Invite, Respond) Mission Operations Transport Layer: Packaging Physical Communications Infrastructure Mission Operations I shall Invite She has my Lady to a Accepted Feast Thou I Graciously art Invited Accept to a Banquet Thou I Graciously art Invited Accept to a Banquet My Lord has I Invited Shall Accept me to a Feast 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 14

15 SM&C Service Layering (a) MO Domain Specific Applications Plug-in Applications SM&C MO Service Framework Technology Adaptors Technology Specific Infrastructure Consumer Application SAP: Service Access Point SM&C: Mission Operations Services SM&C: Common Services SM&C: Message Abstraction Layer Message Exchange; File Transfer; Mail Infrastructure Services Message Exchange; File Transfer; Mail Provider Application Communications Services Interoperable Protocol (PDUs) 15

16 Identified SM&C MO Services Name Core Service Objects and Operations Parameters: publish status; set Actions [Commands]: publish status; invoke/send Alerts [Events]: notify; raise Priority 1 Time Software Management Planning Request Scheduling Time: report; set; correlate; notify On-board Software: load; dump Planning Request/Goal: request; response Schedule: distribute; edit; control; progress reporting Automation Procedure/Function: control; progress reporting 2 Data Product Management Data Product [Payload Data File]: directory; transfer 3 Location Position: tracking, ranging, onboard positioning 3 Flight Dynamics Orbit/Attitude/Predicted Events: determination, propagation, manoeuvre preparation 4 Operator Interaction Message/Alarm/Query: notify; operator response 4 Remote Buffer Management Buffer: catalogue; retrieve; clear 4 16

17 SM&C Common Services MO Service Consumer LOOKUP MO Service Directory INVOKE PUBLISH Common Common Services Services Directory Directory Authentication Authentication Session Session Control Control MO Service Provider 17

18 SM&C Service Layering (b) MO Domain Specific Applications Plug-in Applications SM&C MO Service Framework Technology Adaptors Technology Specific Infrastructure Consumer Application SAP: Service Access Point SM&C: Mission Operations Services SM&C: Common Services SM&C: Message Abstraction Layer Message Exchange; File Transfer; Mail Infrastructure Services Message Exchange; File Transfer; Mail Provider Application Communications Services Interoperable Protocol (PDUs) 18

19 Message Abstraction Layer (1) Generic Interaction Patterns (IP) limited set used by MO services in the SM&C framework Each operation of a service uses one IP Consumer Provider seq SEND send SEND IP Consumer Provider seq PROGRESS progress acknowledge *progress update PROGRESS IP progress return 19

20 Message Abstraction Layer (2) Generic Interaction Patterns (IP) Consumer Broker Provider seq PUBLISH SUBSCRIBE register acknowledge *notify deregister *publish PUBLISH- SUBSCRIBE IP acknowledge Other features: Multiplicity of services (Session, Domain, Network Zone) Security and access control Quality of Service 20

21 Message Abstraction Layer (3) Interoperability (language and encoding/transport) Application Interoperability Application 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 XML Encoding to XML SOAP Message Transport SOAP Message Transport Application Interoperability Application Interoperability Provider Application in Java Provider Application in Java Mission Operations Service in Java Mission Operations Service in Java Messaging Abstraction Layer in Java Messaging Abstraction Layer in Java Encoding to XML Encoding to XML SOAP Message Transport SOAP Message Transport Entity Interoperability Entity Interoperability Application Interoperability Application Interoperability Application Interoperability Application Interoperability Consumer Application in C++ Consumer Application in C++ Provider Application in Java Provider Application in Java Mission Operations Service in C++ Mission Operations Service in C++ Protocol and Transport Bridging Protocol and Transport Bridging Mission Operations Service in Java Mission Operations Service in Java Messaging Abstraction Layer in C++ Messaging Abstraction Layer in C++ Messaging Abstraction Layer in C Messaging Abstraction Layer in C Messaging Abstraction Layer in Java Messaging Abstraction Layer in Java Encoding to XML Encoding to XML Encoding to XML Encoding to XML Encoding to Space Packets Encoding to Space Packets Encoding to Space Packets Encoding to Space Packets SOAP Message Transport SOAP Message Transport SOAP Message Transport SOAP Message Transport AMS Message Transport AMS Message Transport AMS Message Transport AMS Message Transport Entity Interoperability Entity Interoperability Entity Interoperability Entity Interoperability 21

22 SM&C CCSDS Books Consumer/Provider Language Specific APIs Java, C++, API Common Services Directory, Authentication Mission Operations Services Core, Automation, Scheduling, Time, Mission Operations Service Framework Technology Binding AMS, JMS, XML, Messaging Abstraction Layer Generic Interaction Patterns API Binding Encoding Messaging Technology 22

23 Conclusions and Outlook The Mission Operations Services will provide a framework for development of Interoperable systems (across and within Agencies) Re-usable components Systems-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 plan SM&C Message Abstraction Layer - end 2007 SM&C Common Service - Q2/2008 SM&C Core Service - Q2/