RA BOF-1 RASG BOF 04 November 2009 CCSDS Reference Architecture BOF Portsmouth, Virginia, USA May 2010

RA BOF-2 RASG BOF Draft Agenda, "Super SIG" -- CCSDS Architecture; Portsmouth, VA, USA, 06 May 2010 IDTopicLeadTime (min)Planning Comments 1IntroductionE. Barkley5Review Agenda 2Recap of ESTEC MeetingsE. Barkley10 Motiviations for this BOF; programmatic considerations; What is the problem that we are to solve with this BOF/new WG? 3 RA BOF: Current Status, Progress To Date E. Barkley10 BOF composistion, activites, progress relative to conclusion of ESTEC meetings 4RA BOF: ConceptE. Barkley35 Architecture Best Practices; Key Defintions; Stakeholders, Concerns; Viewpoints + Views 5RA BOF: Initial ResultsE. Barkley20 Examples of common terms; common scenario identifications; some Enterprise comparisons; some overlap analysis; 6 ESA Lessons Learned Re Architecture Efforts N. Peccia10 Break10(Because we will need it) 7 ISA BOF: White Paper Review: SOA and Information Services Concept D. Crichton30Information Services Archiecture 8 ISA BOF: Overall Fit with Reference Archiectrue D. Crichton20 How does ISA with overall CCSDS Reference Architecture Concept? 10Discussion/ConclusionsE. Barkley30 What is the overall conclusion of Super BOF; What are the next steps?, etc. (Reserve Time) 0 Agenda

RA BOF-3 RASG BOF The “Super BOF” Tango – 27 Oct 2009 WG Goal: Define a Framework (CCSDS based model) definition that covers space and ground including: Exhaustive list of services identifying cross- support services Cross-Support & Interoperability Use cases / Operational scenarios, overlap and gap analysis (identify redundant and missing services) Business cases (based on existing and in-work services), Architecture of existing and in-work services including an information model, Abstract service definitions: rational for a service, content of service specifications, taxonomy CCSDS Reference architecture. Identify impact on existing architecture. All participants agreed that a CCSDS reference model is urgently required

RA BOF-4 RASG BOF RA BOF Background Plan: Agencies to Identify participants by late November Reality: Team not fully formed until mid January BOF Membership: Telecons every two weeks starting in late January May 2010 CCSDS Technical meetings is first face-to- face meeting for BOF AgencyRepresentative UK S.A.Roger Thompson CSALeo Hartman (Philip Melanson as alternate) CNESNicolas Champsavoir DLRSylvain Gully ESAColin Haddow JAXATakahiro Yamada NASA/JPLErik Barkley (BOF Chair)

RA BOF-5 RASG BOF Assessment of Concept Development re Goal for Eventual WG (pre May Meetings) GoalConcept Treatment So Far Exhaustive list of services identifying cross-support services Some initial example work done; Not seen as critical to developing the overall concept. Cross-Support & Interoperability Use cases / Operational scenarios A fair amount of example work done – aggregate CCSDS scenario for robotic missions developed and sent to CESG. [We will take a look] overlap and gap analysis (identify redundant and missing services) Some analysis done; overlaps can be identified but it seems that architecture will help to sort out in resolving the overlaps [We will take a look] Business cases (based on existing and in-work services Not yet addressed Architecture of existing and in-work services including an information model Not yet addressed Abstract service definitions: rational for a service, content of service specifications, taxonomy Not yet addressed CCSDS Reference architecture. Identify impact on existing architecture A fair amount of work done to develop concept of how to describe CCSDS RA [We will take a look]

RA BOF-6 RASG BOF RA CONCEPT: A GENTLE NUDGE IN THE GENERAL DIRECTION

RA BOF-7 RASG BOF CCSDS Overview: Products, Missions 53+ Standards 420+ missions 04 November 2009

RA BOF-8 RASG BOF 04 November 2009 CCSDS Overview: Scope (?)

RA BOF-9 RASG BOF CCSDS Overview: Areas and (Notional) Functions  Onboard Subnet. Services  Onboard Application Services  Wireless WG  RF & Modulation  Space Link Coding & Sync.  Multi/Hyper Data Compress.  Space Link Protocols  Ranging  High Rate Uplink  Space Link Security  CS Service Management  CS Transfer Services  Cross Support Architecture  Space Packet Protocol  Asynch Messaging  IP-over-CCSDS Links  Motion Imagery & Apps  Delay Tolerant Networking  Voice  Data Archive Ingestion  Navigation  Info. Pack. & Registries  Spacecraft Monitor & Control  Digital Repository Audit/Certification  Systems Architecture  Security  Information Architecture  Space Addressing and Naming  Delta-DOR  Time Code Formats  XML  Registries/Repositories ARCHIVE & APPLS MCC Cross Support Services Systems Engineering Spacecraft Onboard Interface Services Mission Ops & Info. Mgt. Services Space Internetworking Services Space Link Services Cross Support Services Systems Engineering Spacecraft Onboard Interface Services Mission Ops & Info. Mgt. Services Space Internetworking Services Space Link Services

RA BOF-10 RASG BOF What We Have Just Seen Are…. Different views of CCSDS…aimed at addressing different concerns (sort of): Is CCSDS effective? How Is it performing? What does the general environment look like? How is CCSDS organized? What are the functions that CCSDS standardizes? (How is CCSDS organized?)

RA BOF-11 RASG BOF Some Key Definitions from ISO and IEEE Architecture: The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution 1 Architecture description: a collection of products to document an architecture System: a collection of components organized accomplish a specific function or set of functions System Stakeholder: An individual, team, organization (or classes thereof) with interest in, or concerns relative to a system View: A representation of a whole system from the perspective of a related set of concerns. Viewpoint: A specification of the conventions for constructing and using a view. A pattern or template from which to develop individual views by establishing the purposes and audience for a view and the techniques for its creation and analysis. 1. Definitions taken from ISO/IEC 42010:2007/IEEE 1471 The viewpoint is where you look from The view is what you see

RA BOF-12 RASG BOF CCSDS RA CONCEPT (SO FAR)

RA BOF-13 RASG BOF Its Quite Simple at 10,000 m

RA BOF-14 RASG BOF Concept Component Relationships (1/4)

RA BOF-15 RASG BOF Concept Component Relationships (2/4)

RA BOF-16 RASG BOF Concept Component Relationships (3/4)

RA BOF-17 RASG BOF Concept Component Relationships (4/4)

RA BOF-18 RASG BOF Reference Architecture Description Model

RA BOF-19 RASG BOF Reference Architecture Description Model

RA BOF-20 RASG BOF Reference Architecture Description Model

RA BOF-21 RASG BOF SOME INITIAL RESULTS

RA BOF-22 RASG BOF A Trial Viewpoint Spec: Enterprise View StakeholdersConcerns Members of CMC; Members of CESG; WG Chairs Business cases (based on existing and in-work services) Accurate understanding of member agency organizations sufficient to support standardization efforts [CMC, CESG]; Cost of space missions [CMC, CESG]; Performance of space information systems [CMC, CESG]; Ease of Inter-agency inter-operability [CMC, CESG]; Best practices, well understood recommendation guidelines; [CESG, WG Chairs; CMC]; Coherent set of recommendations [CESG, WG Chairs, CMC]; Minimize cost of standards development [CMC] Modeling TechniquesAnalysis Methods a) UML Deployment Diagrams of typical member agency organizations (abstracted, based on common terminology); b) Abstract CCSDS Common Agency Deployment Diagram based on input CCSDS Member Agency inputs; c) BPMN Process Diagrams of typical memgber agency processes (abstracted, based on common terminology); d) Abstract CCSDS Common Agency Business Process Model e) UML Class diagram indicating the CCSDS maintained arcitecture viewpoints and their relationshipsa) f) UML Use Case diagrams/Use Case Database a) Comparison of member agency typical deployments and maintenance of list of commonalities and differences to derive Common Agency Deployment Diagram (CADD); b) Comparison of set of CCSDS recomendations against CADD including differences list to assess business case for subsueqnt blue book development efforts c) Camparison of member agency typical processes and maintenance of lists of commonalities and differences to derive Common Agency BPM (CABPM) d) Comparison of set CCSDS best practices against CABPM including differences list to assess business case for subequent magenta book development efforts e1) Assessment of current CCSDS "architecture" from viewpoint defintions e2) Assessment of viewpoints re anticipated CCSDS program of work

RA BOF-23 RASG BOF Resulting 1 st Quick Iteration of Model Output in (partial) conformance to Enterprise Viewpoint Spec – CNES

RA BOF-24 RASG BOF Resulting 1 st Quick Iteration of Model Output in (partial) conformance to Enterprise Viewpoint Spec – JPL

RA BOF-25 RASG BOF Resulting 1 st Quick Iteration of Model Output in (partial) conformance to Enterprise Viewpoint Spec – CNES vs JPL Some Commonalities Some Differences

RA BOF-26 RASG BOF Taxonomy + Scenarios TermDefinition Manned::Mission flown with humans in spacecraft Robotic ::Mission flown without humans in spacecraft [Manned|Robotic]::Main Objective::(Identification of) Primary goal of scenarios identified [Manned|Robotic]::Mission Classes:: (Identification of) General classification of mission types with regard to Main Objective (including examples for ea class of mission) [Manned|Robotic]::Operational Scenarios:: (Identification of) Major distinct operational phases applicable across mission classes [Manned|Robotic]::Operational Sceanrios::Derived Use Cases:: (identification of) data system behavior needed to support Operational Scenarios [Manned|Robotic]::Operational Sceanrios::Derived Use Cases:: Telecommunications:: (Identification of) system behaviors involving communications assets to support Operational Scenarios [Manned|Robotic]::Operational Sceanrios::Derived Use Cases:: Mission Operations:: (Identification of) system behaviors to involving the spacecraft to support Operational Scenarios [Manned|Robotic]::Operational Sceanrios::Derived Use Cases:: Science Operations:: (Identification of) system behaviors to support conducting science experiments, science data acquisition, archives

RA BOF-27 RASG BOF Robotic Mission Classifications (Based on Taxonomy) Mission Classes:: Class Description Earth Observation Earth Obervation missions include those missions in which space based instruments measure properties of the Earth's surfaces (land and water) and atmosphere. Navigation Navigation missions include those missions that provide a signalling environment in which mobile and stationary assets can determine their location in three dimensional space on and above the surface of the Earth. Telecommunication / Relay Telecommunications missions include space assets that provide communication links to the Earth, to other solar system bodies, to space vehicles and probes in flight and to other telecommunications space assets. Subsets of available communication links thus provide end to end communications services for specific applications. Astronomical / Astrophysical Observation Astronomical / Astrophysical observation missions include instruments that measure properties of phenomena outside the solar system. Space Platform Servicing Space Platform Servicing includes space assembly, resupply and servicing of ISS and other future earth-orbiting platforms. This class of missions also includes assembly and staging of space assets in preparation for missions beyond Earth orbit. Note that this is in the robotic class of missions in general; see the crewed mission class for further decriptions re crewed missions Solar System Body Observation / Orbiter / Flyby Solar system observation missions include space assets to observe, orbit or flyby solar system bodies as well as space assets to measure properties of the solar system environment (such as determination of the Heliopause). Solar System Body Lander/Penetrator / In-situ Exploration Solar system in-situ exploration missions include missions involving scientific and mobile assets landed on or colliding with solar system bodies. Sample return Missions that land scientific instruments on other solar system bodies and that subsequently leave with samples gathered from the surface. Technology Demonstration Missions that are primarly focused on pioneering the use of new technology or operational approaches.

RA BOF-28 RASG BOF Robotic Mission Scenarios Operational Scenarios:: Scenario Description Testing, verification, commissioning Testing, Verification, Commissioning Includes all testing, verification and characterization activities performed on operational mission systems in both the ground and space segments. This scenario also includes technology demonstration and qualification (e.g., experiments with relay satellites) and any automated testing such as health monitoring activities and built in self-tests. Launch Launch includes all activities related to preparation and execution of a spacecraft launch until the spacecraft is achieved its intended orbit or trajectory. Launch and early orbit phase (LEOP) activities are included in this scenario. Guidance + Navigation Guidance and navigation includes all activities related to achieving or maintaining a desired orbit or trajectory such as orbit insertion, orbit transfer, orbit correction and maintenance, course corrections, maneuvers and cruise, This scenario also includes attitude control. Observation Campaign Observation campaign includes all activities related to planning, preparing and executing coordinated usage of the spacecraft and its instruments to provide scientific data gathering Spacecraft emergency Spacecraft emergency includes those activities related to anmolous (not normal) spacecraft operations related to protecting the spacecraft from futher damage and recovering its normal operations. Formation flying Formation flying includes all activities related to establishing and maintaining space assets in a formation, i.e., in a desired geometric relationship. On Orbit Servicing On Orbit Serviceing includes all activities related to servicing space assets such as assembly, maintenance, repair and refueling/resupply. This scenario includes the planning, preparation and execution of these operations Remote Body Impact Remote body impact includes all activities related to planning, preparing and executing operations to cause a space asset to collide with a target solar system body. Remote Entry, Descent, Landing Remote entry, descent and landing includes all activities related to landing a space asset on a target solar system body. Remote Surface Exploration Remote surface exploration includes all activities related to operation of mission assets landed on a remote solar system body. This can be seen as an extension of the Observation Campaign scenario with added complexity of surface navigation and hazard avoidance. Earth Re-Entry, Descent, Landing Earth re-entry, descent and landing includes all activities related to space assets returning to the surface of the Earth. This scenario includes missions returning from ISS and future space platforms and sample return missions. Integration with terrestrial data systems Integration with terrestrial data systems includes all activities related to integrating mission data, e.g., earth observation, space weather and astronomy data, with the repositories, archives, processing facilities and distribution channels for the analogous data generated here on Earth. Termination / end of life Termination includes all activities related to removal of a space asset from its nominal orbit such as by re-entry into the atmosphere or removal to a higher orbit.

RA BOF-29 RASG BOF Robotic Mission Use Cases Derived Use Cases:: Telecommunications::Derived Use Case Description Direct-from-Earth, Agency Internal Direct-from-Earth, Cross Supported Direct-to-Earth, Agency Internal Direct-to-Earth, Cross Supported Space Internetworking, Cross Supported (Incl Relay) Mission Operations::Dervied Use Case Description Data management and distribution End to end mission health monitoring and fault protection Mission planning Mission communications planning Mission communications execution Tracking Data Collection, Orbit Determintation Orbit control (AOCS) Plan execution Onboard autonomy Planetary Protection Spacecraft Operational Data Gathering and Analysis Science Operations/Payload Operations::Dervied Use Case Description Payload data management and distribution Simulation and training Payload planning Payload plan execution Payload autonomy Payload health monitoring and fault management Payload data processing Payload calibration

RA BOF-30 RASG BOF Overlap Analysis – Messaging (Example) Overlap Analysis -- Messaging, Interaction Patterns AreaRecommendation Title (No)Recommendation TypeSalient Aspects for Overlap AnalysisStatusIntended Domain Applicable Reference Model Comments CSS Service Management ( B1) Blue Book Document Exchange Protocol; Interaction Patterns [Notified (out), 2-phase (inout), 3-phase (in-out-out)] State Table Definitions (Behavior); Message Composition Requirements (On-the-wire formats); Decoupled approach -- contextual references in all messages Published UM CM for coordination of TT+C Services B-2 (needs updating) Succesful inter-operations demonstrated via SMTP and HTTP transports; Formal abstract message composition via UML; Concrete message composition via XML CSSSpacelink ExtensionBlue Book(s) Message Exchange Protocol; Interaction Patterns; State Table Definitions (Behavior); Message Composition Requirements (On-the-wire formats); Tightly coupled approach -- context estalbished at via initial exchanges; session oriented Published SLE Complex MDOS for transfer of TT+C Data B-2 Succesful inter-agency interoperations via TCP/IP; Use of ASN.1 for message composition CSS Cross Support Transfer Service Blue Book(s) Message Exchange Protocol; Interaction Patterns [Unconfirmed (in/out), Confirmed (in-out) or Acknowledged (in-outout)] ; State Table Definitions (Behavior); Message Composition Requirements (On-the- wire formats); Tightly coupled approach -- context estalbished at via initial exchanges; session oriented In Work SLE Complex MDOS for transfer of TT+C Data B-2 (needs updating) Prototyping in progress; interoperations planned via TCP/IP; Use of ASN.1 for message composition; CSTS is next generation generic service to (eventually) replace SLE MOIMSMessage Abstraction LayerBlue Messaging Protocol; Interactions Patterns [send (in), Submit (in-out), Request (in-out), Invoke (in-outout), progress (in-out-N*out), publish-subscribe (in-out, N*in, N*out, in-out)]; Message Header Paramter Lists (tabular format); Decoupled approach -- contextual references in all message headers In Work End-to-End; generally for MDOS to Spacecraft (?) Terrestrial only prototyping in progress via JMS and DDS SIS Asynchronous Messaging Service Blue Messaging Protocol; Interactions Patterns are generally publish-subscribe ["send/receive, publish/subscribe, synchronous query, and announcements"]; Very detailed bit-level description of message contents; detailed tabular message type descriptions, esp for AMS maitenance (meta- data); tends to define complete infrastruture equivalent to terrestrial JMS/DDS servers; extensive defintion of protocol unique terms such as 'continuum', 'venture','cell','message space','unit' In WorkEnd-to-End ? Prototyping has occurred involving simulated spacecraft SOISMessage Transfer SerivceBlue(TBD)In Work Spacecraft, Onbaord Discussion 1) Analysis of overlap is complicated by usage of different terminology. 2) The equivalent of similar but yet slightly different messaging interaction patterns is present. 3) Some of the messaging specifications (SM, CSTS, MAL) assume usage of fairly well defined/readily available terrestrial transports such as TCP/IP, HTTP, JMS, DDS. 4) Some of the messaging specifications assume no pre-existing infrastructure and define it completely (AMS). 5) Different technologies are employed to describe on-the-"wire" data/PDUs. UML + XML + Text (SM), ASN.1 + Text (CSTS), Text + XML (MAL), Bit-level text layout (AMS). 6) Domain scopes vary from well-defined terresterial partners (SM, CSTS), to open-ended ETE (no concrete partners identified) (MAL, AMS). 7) Appear to be two competing notions of end-to-end domains (MAL, AMS). E.g, how does a MAL URI relate to an AMS 'continuum' ? 8) ETE transport questions arise: MAL defines XML, but no mapping to AMS bit-level strucutre which will be required ?

RA BOF-31 RASG BOF RA BOF – Up To the Minute Results (1/2) GoalConcept Treatment So Far Exhaustive list of services identifying cross-support services Some initial example work done; Not seen as critical to developing the overall concept. Cross-Support & Interoperability Use cases / Operational scenarios A fair amount of example work done – aggregate CCSDS scenario for robotic missions developed and sent to CESG. overlap and gap analysis (identify redundant and missing services) Priority 1 Some analysis done; overlaps can be identified but it seems that architecture will help to sort out in resolving the overlaps Business cases (based on existing and in-work services Not yet addressed Architecture of existing and in-work services including an information model Not yet addressed Abstract service definitions: rational for a service, content of service specifications, taxonomy Not yet addressed CCSDS Reference architecture. Identify impact on existing architecture A fair amount of work done to develop concept of how to describe CCSDS RA

RA BOF-32 RASG BOF Priority 1: Viewpoint Spec + Model to Support Overlap + Gap Analysis RA BOF – Up To the Minute Results (2/2)