CCSDS Reference Architecture Notes from SAWG discussion & from SEA Report to CESG/CMC 12 & 17 Nov 2014

CCSDS Reference Architecture Notes CCSDS overall problem: WG overlaps, persistence, WGs that live in their own space and (often/largely) ignore others, no analytical mechanism for managing boundaries CCSDS process: create BoF, define charter, establish scope, create WG, define initial product set, evolve WG, re-define & extend product set, persist for a long time (or, seldom, go out of business) ECSS Process: create stand-alone WG, set context, provide guidance & lessons learned, go out of business, hand-over to a technical area (TA) lead, revisit in 3-5 years, open once => leading to data repository instead of document structure Discussed possible use of Mike Kearney’s Area/WG “color chart” as a definition of CCSDS scope Discussed possible use of RASDS connectivity end-to-end diagrams from the Space Communications Cross Support Architecture documents (SCCS-ADD & ARD) as a definition of the CCSDS scope and to define relationships between

System Architecture BoF (SAWG restart) Goals: Create CCSDS Reference Architecture for CMC (“cartoon” and formal model) 1.5 WY Develop a formal ontology for CCSDS and related XML schema guidelines 2+ WY Refresh Reference Architecture for Space Data Systems (RASDS) 1-2 WY Develop a process for sustaining the reference architecture, ontology and schema 0.5 WY BoF Status: Discussed CCSDS Reference Architecture, two possible initial approaches were discussed. Propose doing it in 2 stages, initial quick “cartoon” form and a more accurate, modeled, SysML version, and reviewed with WGs, CESG & CMC. Need agreement on approach before work is initiated. Discussed development of a formal ontology (terms, cleaned up definitions, sources, and especially relationships) from the existing CCSDS Glossary (SANA version). Agreement that this would improve overall CCSDS standards once developed and integrated into WG processes. Interest & support from two outside sources: ECSS and SC14. Discussed refresh of RASDS MB (overdue for 5 year review). Agreement on value of adding three new viewpoints: service, operations, and physical. Interest from two sources: CCSDS and users, and SC14. Agreement that developing a SysML/UML annex would be useful. Discussed development of XML style & structure guidelines, integration of the formal ontology terms in the development of improved schema, and content and structure validation tools. New source of support: API Academy Resolution: SAWG wishes to restart and develop this set of standards and guidelines. Some external resources appear to be available, but agency involvement is sought. Systems Engineering Area Report

ABA Earth-Space Link Terminal ABA Earth User Node ABA Space User Node Ground-Space CCSDS Protocols Terrestrial WAN VC X&Y ABA RF & Mod IP TCP C & S F-Frame Production VC X&Y CMD VC Y VC X AOS/TC RF & Mod C & S SPP Space SPP Application Space File Application To VC X VC X&Y To VC Y User File Application IP TCP F-Frame AOS/TC SPP User SPP Application CMD CFDP IPSEC SDLS File Secure CFDP SDLS IPSEC 1.Each protocol element maps directly to one or more standards 2.Relations ships are explicit, show requires / provided service & interfaces 3.May be mapped to WG as a separate (and flexible) step 4.Applications layer (MOIMS & SOIS) should be built on top of this and use it CCSDS Ref Arch, Option 2 Show stacks of standards and relationships

CCSDS Ref Arch, Option 2 Example: Mission Operations / SOIS Interfaces Space User Node Earth User Node User Frame Processing User Radiometric Processing Space Link Flight Dynamics Mission Planning Mission Schedule Execution Mission Monitor & Control SPP over TM/TC/AOS Frame Processing RadiometricPr ocessing (Real-time) SM&C MO Applications (MAL Compliant) MAL & Transport Adapter for SPP, or whatever Flight Dynamics Control Space Schedule Execution Space Monitor & Control SOIS Applications (FW Compliant) SCCS-ADD Fwd / Ret Space Link Services Spacecraft Subnets & Devices SOIS Application Support Services SOIS Subnetwork Layer Services SM&C MO Applications (MAL Compliant) User File/Packet Processing MAL & Transport Adapter for SOIS

CCSDS Ref Arch, Option 2 Example: Cross Support / Mission Operations Interfaces ABA ESLT Earth User Node User Service Management Application (Planning & Scheduling) User Application (Packet Processing) User RCF Application (Frame Processing) User Radiometric Data Processing User Service Monitor Data Processing User F-CLTU Application (CLTU Processing) Service Delivery (SD) Interfaces Service Management (SM) Interface (I/F) Flight Dynamics Mission Planning Mission Schedule Execution Mission Monitor & Control SM over HTTP F-CLTU over TCP R-CF over TCP MD-CSTS over TCP TD-CSTS over TCP SLE F-CLTU Processing SLE RCF Processing (Frame De- Muxing) TD-CSTS Processing (Real-time Radiometric Data) Service Management Processing (Monitor Data) Service Management Processing (Network Scheduling) SM&C MO Applications (MAL Compliant) MAL & Transport Adapter for SPP