1. ESA PrototypeCNES/JPL Prototypes MCS MCS Adaptor SM&C Core SM&C Common SM&C Protocol CCSDS Packet TM/TC CCSDS SLE Simulator SIM Adaptor SM&C Core SM&C Common SM&C Protocol CCSDS Packet TM/TC CCSDS SLE CCSDS TM Frame/CLTU Protocol Stack: Prototype Baseline APIs Consumer Side Technology/Platform A Provider Side Technology/Platform B Each prototype should include full stack required for their technology / platform. This gives us multiple API implementations API will be a specific SAP binding for the implementation technology used, Language and possibly Platform, e.g.: Java Windows C++ Linux C++ Layer implementation depends on both the offered API and the binding to the next layer down. SM&C Core to SM&C Common should be standard. Binding to underlying Comms is specific to the protocol stack used. Each layer implementation is an adapter from the higher level API to the lower level API With intention to absorb this into AMS. Should current prototyping postpone implementation of this layer? Or only prototype those elements required to support SM&C Core + Common? PUS Packets output from SIM are interpreted by SIM Adaptor.

2. ESA PrototypeCNES/JPL Prototypes MCS MCS Adaptor SM&C Core SM&C Common CCSDS AMS Comms Layer Simulator SIM Adaptor SM&C Core SM&C Common Comms Layer Protocol Stack: AMS Variation APIs Consumer Side Technology/Platform A Provider Side Technology/Platform B AMS May offer different bindings to: CCSDS Packet TM/TC (over SLE) SCPS TCP/IP CCSDS AMS

3. ESA PrototypeCNES/JPL Prototypes MCS MCS Adaptor SM&C Core SM&C Common CCSDS Packet TM/TC CCSDS SLE Simulator SIM Adaptor SM&C Core SM&C Common CCSDS Packet TM/TC CCSDS SLE CCSDS TM Frame/CLTU Protocol Stack: Simplified/Interim Prototype Option 1 APIs Consumer Side Technology/Platform A Provider Side Technology/Platform B Interim binding of SM&C Common to CCSDS Packets in lieu of AMS. Binding would ultimately be replaced by AMS.

4. ESA PrototypeCNES/JPL Prototypes MCS MCS Adaptor SM&C Core SM&C Common TCP/IP Simulator SIM Adaptor SM&C Core SM&C Common TCP/IP Protocol Stack: Simplified/Interim Prototype Option 2 APIs Consumer Side Technology/Platform A Provider Side Technology/Platform B Interim binding of SM&C Common to TCP/IP in lieu of AMS. Does not demonstrate integration with space link protocols. Is a useful binding for ground segment and test environments

5. PUS Legacy Adapter Configuration Unmodified Simulator/SpacecraftMCS Configuration MCS MCS Adaptor SM&C Core CCSDS Packet TM/TC CCSDS SLE Simulator ECSS PUS CCSDS Packet TM/TC CCSDS SLE CCSDS TM Frame/CLTU Consumer Side Technology/Platform A Provider Side Technology/Platform B ECSS PUS Standard Binding to PUS Services for each SM&C Mission Operations Service Common/Protocol Layers by-passed