1 SOIS Plenary Washington March 2008 Chris Taylor

2 Agenda for the week SOIS Plenary Tuesday 11th March AM: –SOIS Organisation –Status of Red Books (ESA) –Status of mapping onto SpaceWire & 1553, (ESA) –Status of SOIS Prototyping Activities (All) –BioNet enterprise software framework (NASA) –Strategies for alignment with the ASS/PnP SOIS efforts (NASA) –AOB Joint Application Support/Subnetwork Services WGs Tuesday PM through Thursday PM –Tuesday PM – joint AMS discussion –Wednesday AM/PM – Plug-and-Play Concept completion –Thursday – Packet Store & AOB Wireless WG – Tuesday PM Through Thursday AM SOIS Plenary Friday 14th March AM: –Working group reports –Round up

3 SOIS - A few changes Area directorChris Taylor (ESA/ESTEC) Area deputyStuart Fowell (SciSys/BNSC) Wireless WG leadPatrick Plancke (ESA/ESTEC) Wireless WG deputyKevin Gifford (NASA/UC) Application Support services LeadStuart Fowell (SciSys/BNSC) Application Support services DeputyRamon Krosley (NRL/DesignNet) Subnetwork Service LeadChris Taylor (ESA/ESTEC) Subnetwork Service DeputyGlenn Rakow (NASA/GSFC)

4 Communication Management CMD & Data Acquisition Services Time Access Service File Services Message Transfer Service Device Enumeration Service Packet Service Memory Access Service Synchronisation Service Device Discovery Service Test Service Datalink Convergence Protocols CFDP Application Layer Application Support Layer Transfer Layer Other Subnetwork Layer Network Protocol Transport Protocol MilbusSpaceWireCANWireless AMS

5 Red Book Status Application Services WG –Time Access serviceRed book 2 pending prototyping –File servicesRed book 2 pending prototyping –Device Data Pooling serviceRed book 2 pending prototyping –Message Transfer serviceRed book 1 pending prototyping –Device Access serviceRed book 2 pending prototyping –Device Enumeration servicePrepare draft –Device Virtualisation ServicePrepare draft Subnetwork Services WG –Packet serviceRed book 2 pending prototyping –Test ServiceRed book 2 pending prototyping –Memory Access serviceRed book 2 pending prototyping –Device Discovery ServiceRed book 2 pending prototyping –Synchronisation serviceRed book 2 pending prototyping All books are in the SOIS Document area (SOIS area/docs/draft docs)

6 SpaceWire Activities As part of preparation of the ECSS RMAP standard a mapping to SOIS Remote memory access is under review, no issues reported yet The SpaceWire working group has reviewed the SOIS QOS definitions with a view to preparing the requirements for a SOIS compliant SpaceWire packet protocol An issue was raised on the best effort service: –The present SOIS service requires packets to be delivered in order with possible omissions –This can cause problems for SpaceWire when alternative routing is enabled as packets may take different routes through the network –The issue is under discussion but it is currently felt that the SOIS services should be maintained in order to keep the Application implementation simple The SpaceWire requirements document is still under review will be concluded in the summer, following this work on set of SOIS compliant protocols will be initiated

7 ECSS 1553 Extensions Drafting Process Internal review study Projects experience MIL 1553 Standard ECSS-E Draft A CCSDS/SOIS Working Group Analysis and Drafting Public review ECSS secretary review Requirements Verification ECSS-E Draft B ECSS-E Draft C ECSS-E Issue 1 publication Standard verification activities Standard engineering - elaboration and maturation prototyping Modeling

8 Mapping on CCSDS SOIS Subnetwork Synchronisation Service –The time distribution functions defined by the SOIS synchronisation Service can use the Time Distribution and Synchronisation service provided by [ECSS_1553] –Event management is implemented with the Get/Set service. Packet Service –The SOIS Subnetwork packet service is implemented using the [ECSS_1553] Data Block Transfer which provides the capability to transmit SPP packets, with accurate latency and QoS control. –PUS packets embedded in SPP packets are foreseen to be used for most of the applications onboard future spacecraft

9 Mapping on CCSDS SOIS Subnetwork Memory Access Service –The SOIS Subnetwork Memory Access Service is mapped on the Get/Set service dedicated to efficient transfers between a central computer and sensors/actuators. –For accesses with less than 32 words, the service is directly mapped on a [MilBus] message, otherwise a segmentation function is provided up to a mission dependant limit. Device Discovery Service –A specific interface area is allocated to the SOIS Subnetwork Device Discovery in the [MilBus] data link address space for Terminal Management in order to exchange the Electronic Data Sheets (EDS) with discovered devices.

10 Mapping on CCSDS SOIS Subnetwork Test Service –The test service for communication devices relies on the Data Wrap- Around Service, as provided in the [MilBus] Standard, section –The sub-address 30 is allocated for this service in [ECSS_1553] which allows checking end-to-end operation of the [MilBus]. Communication Synchronisation service –All of the previously mentioned SOIS Subnetwork Services use the ECSS Communication Synchronisation Service. –This service guarantees the real-time properties of all the user services and defines a generic communication frame insuring a deterministic control of communication latencies

11 SOIS Prototyping

12 SOIS prototyping Several activities are planned or underway: –Initial SOIS prototype (SciSys, Astrium F) Initial Implementation of the complete SOIS stack in a flight representative environment (RASTA) Operation over Milbus and SpaceWire Reduced subnetwork QoS and plug and play implementation Completion 3 rd quarter 2008 –SOIS validation (release end 2008, duration 1 year) Will cover full SOIS stack and all services –Modular Architecture for Robust Computing (SEA, SciSys, Astrium UK) Define a modular architecture based on a SpaceWire network that is scalable to meet future mission needs SOIS based software and related services Completion end 2009

13 External I/F ESA Reference Avionics Test bed

14

15

16 MARC Software architecture

17 Summary We are proceeding fairly much as planned and initial feedback from implementers is positive Prototyping is now proceeding at ESA but much work remains to be performed and here we really would appreciate additional international effort The QOS definitions may need to be refined, including an update to the green book Other Green book updates may be warranted – improvement in architecture diagram, incorporation of spacelink interface, service changes etc The Wireless WG may well bring new requirements and feedback to the service definition, especially in the area of plug and play In reality, we should be shooting for Blue books at the end of 2009 Have a successful and fruitful week

18 Plenary Part 2 Organisational -Propose that subnetwork and Application working groups continue to meet in plenary -Dedicated sessions on specific topics can be held as necessary -Dedicated Subnetwork meetings can be resurrected if subnetworks changes are necessary -Wireless WG will continue to meet separately but should keep alignment with SOIS services - communication via the SOIS Application services mailing list, p lease sign-up if you haven’t already done so -Separate WG for plug and play not considered necessary -BOF should be formally dissolved -SOIS scope to be updated to include P&P

19 Plenary Part 2 Technical -As work progresses the Green book may become out of step thus giving the wrong impression to casual readers -Could anyway be improved in terms of architectural presentation and QOS -Suggest we review the existing text in background and discuss updates at next meeting (lead Taylor/Fowell) -What is the position of SOIS on the in-sequence delivery question posed by the SpaceWire WG? -SOIS related Prototyping -Seems that there are a increasing number of implementations that are SOIS related -Good advertising and should be indicated on CWE -Need to improve document library -All groups please ensure meeting docs/presentations are uploaded to CWE

20 Plenary Part 2 Wireless –Propose charter modification for blue rather than magenta