1 / 9

CCSDS Standard On-Board InterfaceS (SOIS)

CCSDS Standard On-Board InterfaceS (SOIS). Rick Schnurr NASA – Goddard Space Flight Center CCSDS – SOIS Sub-Network working group chair 2006 MAPLD International Conference Washington, D.C. September 25, 2006. CCSDS-SOIS Goal. To develop standards that will: Improve:

garron
Télécharger la présentation

CCSDS Standard On-Board InterfaceS (SOIS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CCSDS Standard On-Board InterfaceS (SOIS) Rick Schnurr NASA – Goddard Space Flight Center CCSDS – SOIS Sub-Network working group chair 2006 MAPLD International Conference Washington, D.C. September 25, 2006

  2. CCSDS-SOIS Goal • To develop standards that will: • Improve: • Process of spacecraft development and integration • Quality of the finished product • Facilitate adoption of new technologies • Hardware & software • Support international onboard interface interoperability.

  3. SOIS - Approach • To standardise interfaces between items of spacecraft equipment by: • Specifying well-defined standard service interfaces and protocols • Allow standardized access to sensors, actuators and generic spacecraft functions • Spacecraft applications to be developed independently of the mechanisms that provide these services. • Applications are insulated from the specifics of a particular spacecraft implementation • may be reused across different spacecraft platforms with little regard of implementation details

  4. SOIS - Architecture

  5. SOIS Sub-Network Architecture • SOIS Sub-Network defines abstract service interface • Abstract because it is not Bus/LAN specific. • Mapping describes how services are implemented on a specific bus • Maps Sub-Network services onto a Data-Link using Sub-Network Convertence functions or Data Link specific functions.

  6. PDU encapsulation Others – USB, IEEE-802.11, One Wire Ethernet CAN IEEE-1394 MIL-STD-1553 SpaceWire Link Redundancy Retry Priority Address Translation PNP Support Resource Reservation Protocol Multiplex Fragmentation Sub-Network Architecture SOIS - Subnetwork Services: Sub Network Time Distribution Service Packet Transfer Service Get/Set Parameter Service Memory Read/Write Service Device Discovery Service Test Service Bus Mapping Sub-Network Convergence functions Standard Data Links

  7. SOIS Sub-Network Architecture • SpaceWire already supports most mapping functions defined. • In many cases more than one mapping function exits for each block • Example, GAP vs RMAP • Mapping from SOIS services is a priority of the CCSDS-SOIS sub-network working group

  8. SOIS support for CCSDS SOIS Mapping • Protocol Mux – SpaceWire Standard • Fragmentation – Not needed • Reliability – GOES reliability protocol • GET/SET and Memory Read – GAP or RMAP • PNP – some work in progress could be deferred • Address translation – needed • Priority – needed • Resource reservation - needed

  9. Conclusion • CCSDS SOIS Sub-network services and required mapping functions are well defined at this point. • Packet service and quality of service model are also mostly complete • Mapping SpaceWire to CCSDS SOIS is a logical next step. • Input from the SpaceWire community is desired.

More Related