Transcript Feedback on SOIS Architecture Intro v1.0

CCSDS SOIS Application Support Services WG
Feedback on SOIS Reference Communications Architecture
10th March 2014
Overview
• Introduction
• Feedback
» European Spacecraft Primes’ Feedback on SOIS Reference
Communications Architecture, Felice Torelli (ESA)
› Plus earlier feedback on Subnetwork Services from ESA studies
» Feedback on SOIS, Peter Mendham (Bright Ascension)
» Feedback on Capturing MIL-STD-1553B Device Interfaces in
EDS, Richard Melvin/Stuart Fowell (SCISYS)
» Mapping Serial RapidIO to the SOIS Reference
Communications Architecture, Charles "Patrick" Collier (AFRL
Space Vehicles)
• Discussion on way forward & Planning
» Initiate 5-yearly Review of SOIS Subnetwork Services Magenta
Books
04 August 2016
SCISYS Presentation Title
2
History Lesson (Part 1)
• SOIF starting in pre-2000
» CCSDS P1K SOIF 3rd Meeting October 2000 in Toulouse,
France
• Slow start, Initial focus was on a set of concrete
protocols to run over different buses
• Too heavyweight for typical spacecraft
» Optimal subnetwork-specific solutions already exist
» No requirement for a network
› Is this still the case with e.g. PUS Packets sent to/from instruments
and AOCS devices with minimal involvement of avionics & e.g. MO
Services?
• Re-focus on generic service primitive specifications with
mappings onto subnetwork-specific protocols
» Mappings not standardised
04 August 2016
SCISYS Presentation Title
3
History Lesson (Part 2)
• SOIS Green Book Issue 1 published June 2007
• Subnetwork Magenta Books published December 2009
• Application Support Magenta Books published from
January 2011 to October 2014
» Packet Store Services added through ESA/NASA feedback
• SOIS Green Book Issue 2 published December 2013
» Updated to reflect Subnetwork and Application Support
Services as published
» New topics of Electronic Data Sheets and Common Dictionary
of Terms added
04 August 2016
SCISYS Presentation Title
4
• Apart from primarily EDS R&D studies, SOIS has not been
adopted
• Why?
» Not required? Business as usual by Spacecraft manufacturers?
» Produced by small number of Agency representatives? Little mission
engineers, spacecraft manufacturer, flight software, avionic device
developer involvement?
» Wrong things standardised? Messaging done in different ways by
different software architectures. Can a software architecture be
standardised?
» To abstract? Service primitives, no protocols, not mappings to real buses
» Wrong architecture? Where does DDPS actually fit? Synchronous and
asynchronous buses and networks?
• Do we need SOIS to be on an actual mission as a reference?
» Is this practical or will it only be individual services, e.g. File Services?
» Would this invalidate the EDS work (with all development so far being
focussed on Cmd and Data Acq Services to avionic devices
04 August 2016
SCISYS Presentation Title
5
Way Forward?
• CCSDS Procedures
» 5 yearly review of Subnetwork Services Magenta Books
» Pink sheets for Application Support Services
• What to change? E.g.
» Synchronous bus profile, focus on MIL-STD-1553B but with a
view to e.g. TTEthernet
» Asynchronous bus profile, focus on SpaceWire networks
» Determine where DDPS fits
» Tidy up and ensure terminology is consistent, e.g.
› OSI primitive naming
› Consistent terminology and interaction patterns
- Taking account of varying comments from Peter Shames over the
various Red Book reviews
› Publish example blocking API? What colour book is this?
04 August 2016
SCISYS Presentation Title
6
Feedback presentations…
04 August 2016
SCISYS Presentation Title
7