1. MD CSTS prototype status 2012 : MD user (NASA) based on NASA Fw development MD provider (CNES) based on ESA Fw development NASA/ESA Fw interoperability tests NASA/CNES MD interoperability tests 2015 : FW prototype upgrade completed by ESA (last version of specification) NASA/ESA Fw interoperability tests made during spring meeting in Pasadena (only for forward services) MD service user prototype (ESA) MD service provider prototype (CNES) Both based on ESA Fw development (CSTS API v1.4 september 2015) On MD provider prototype, the update work is started and delivery of MD prototype is foreseen by mid- december ESA/CNES MD interoperability tests (can be scheduled beginning of 2016). We will need a TCP/IP link between CNES and ESA.

2. MD CSTS prototype architecture

3. MD CSTS prototype configuration Configuration files : Proxy : PROXY_USER_Config.txt, PROXY_PROV_Config.txt Service element : SE_USER_Config.txt, SE_PROV_Config.tx Configuration values for MDS : MDS_SM.xml Service instance configuration : SICF,txt Configuration for MD simulation (simulation of parameters and events) : MDS_data.xml PublishedIdOIDMapping.xml (contains all the published identifiers definitions) Example of PublishedIdOIDMapping.xml file : …………….

4. Interoperability tests Approach for interoperability tests A set of tests is described in the document « framework and MD prototypes interoperability test report », Draft of this document can be found at : Work Environment (CWE) > Cross Support Services Area (CSS) > Documents > CSS-CSTS > CWE Private > CSTS prototypes > yellow book test report_02Work Environment (CWE)Cross Support Services Area (CSS)Documents CSS-CSTSCWE Private Document based on an initial test plan proposed by Tim Ray for the 2012 version of FW and MD prototypes. Test plan updated following the last version of FW specification. Test scenarios CSTS API : 10 tests. These tests use BDD procedure in order to validate the Complete and Real-time data delivery modes. Done between NASA and ESA with the 2012 version of FW; do we pass again these tests in order to validate the return services part of the 2015 FW version ? MD CSTS service : 29 tests.

5. Interoperability tests CSTS MD service Prototype tests TEST 1 – ON-CHANGE-OPTION CYCLIC REPORT WITH THE DEFAULT LIST OF PARAMETER TEST 2 – ON-CHANGE-OPTION CYCLIC REPORT WITH NAMED INDIVIDUAL PARAMETERS TEST 2 – ON-CHANGE-OPTION CYCLIC REPORT WITH NAMED INDIVIDUAL PARAMETERS TEST 3 – ON-CHANGE-OPTION CYCLIC REPORT WITH LABELED INDIVIDUAL PARAMETERS TEST 3 – ON-CHANGE-OPTION CYCLIC REPORT WITH LABELED INDIVIDUAL PARAMETERS TEST 4 – ON-CHANGE-OPTION CYCLIC REPORT WITH LIST NAME TEST 4 – ON-CHANGE-OPTION CYCLIC REPORT WITH LIST NAME TEST 5 – ON-CHANGE-OPTION CYCLIC REPORT WITH FUNCTIONAL RESOURCE NAME TEST 5 – ON-CHANGE-OPTION CYCLIC REPORT WITH FUNCTIONAL RESOURCE NAME TEST 6 – ON-CHANGE-OPTION CYCLIC REPORT WITH FUNCTIONAL RESOURCE TYPE TEST 6 – ON-CHANGE-OPTION CYCLIC REPORT WITH FUNCTIONAL RESOURCE TYPE TEST 7 – ON-CHANGE-OPTION CYCLIC REPORT WITH PROCEDURE TYPE TEST 7 – ON-CHANGE-OPTION CYCLIC REPORT WITH PROCEDURE TYPE TEST 8 – ON-CHANGE-OPTION CYCLIC REPORT WITH PROCEDURE INSTANCE IDENTIFIER TEST 8 – ON-CHANGE-OPTION CYCLIC REPORT WITH PROCEDURE INSTANCE IDENTIFIER TEST 9 – MULTIPLE CONCURRENT (INTERLEAVED) ON-CHANGE-OPTION CYCLIC REPORTS TEST 9 – MULTIPLE CONCURRENT (INTERLEAVED) ON-CHANGE-OPTION CYCLIC REPORTS TEST 10 – ON-CHANGE-OPTION CYCLIC REPORT WITH NEGATIVE RETURN TEST 10 – ON-CHANGE-OPTION CYCLIC REPORT WITH NEGATIVE RETURN TEST 11 – INFORMATION QUERY WITH THE DEFAULT LIST OF PARAMETERS TEST 11 – INFORMATION QUERY WITH THE DEFAULT LIST OF PARAMETERS TEST 12 – INFORMATION QUERY WITH NAMED INDIVIDUAL PARAMETERS TEST 12 – INFORMATION QUERY WITH NAMED INDIVIDUAL PARAMETERS TEST 13 – INFORMATION QUERY WITH LABELED INDIVIDUAL PARAMETERS TEST 13 – INFORMATION QUERY WITH LABELED INDIVIDUAL PARAMETERS TEST 14 – INFORMATION QUERY WITH LIST NAME TEST 14 – INFORMATION QUERY WITH LIST NAME TEST 15 – INFORMATION QUERY WITH FUNCTIONAL RESOURCE NAME TEST 15 – INFORMATION QUERY WITH FUNCTIONAL RESOURCE NAME TEST 16 – INFORMATION QUERY WITH FUNCTIONAL RESOURCE TYPE TEST 16 – INFORMATION QUERY WITH FUNCTIONAL RESOURCE TYPE TEST 17 – INFORMATION QUERY WITH PROCEDURE TYPE TEST 17 – INFORMATION QUERY WITH PROCEDURE TYPE TEST 18 – INFORMATION QUERY WITH PROCEDURE INSTANCE IDENTIFIER TEST 18 – INFORMATION QUERY WITH PROCEDURE INSTANCE IDENTIFIER TEST 19 – INFORMATION QUERY WITH NEGATIVE RETURN TEST 19 – INFORMATION QUERY WITH NEGATIVE RETURN TEST 20 – NOTIFICATION WITH THE DEFAULT LIST OF EVENTS TEST 20 – NOTIFICATION WITH THE DEFAULT LIST OF EVENTS TEST 21 – NOTIFICATION WITH NAMED INDIVIDUAL EVENTS TEST 21 – NOTIFICATION WITH NAMED INDIVIDUAL EVENTS TEST 22 – NOTIFICATION WITH LABELED INDIVIDUAL EVENTS TEST 22 – NOTIFICATION WITH LABELED INDIVIDUAL EVENTS TEST 23 – NOTIFICATION WITH LIST NAME TEST 23 – NOTIFICATION WITH LIST NAME TEST 24 – NOTIFICATION WITH FUNCTIONAL RESOURCE NAME TEST 24 – NOTIFICATION WITH FUNCTIONAL RESOURCE NAME TEST 25 – NOTIFICATION WITH FUNCTIONAL RESOURCE TYPE TEST 25 – NOTIFICATION WITH FUNCTIONAL RESOURCE TYPE TEST 26 – NOTIFICATION WITH PROCEDURE TYPE TEST 26 – NOTIFICATION WITH PROCEDURE TYPE TEST 27 – NOTIFICATION WITH PROCEDURE INSTANCE IDENTIFIER TEST 27 – NOTIFICATION WITH PROCEDURE INSTANCE IDENTIFIER TEST 28 – NOTIFICATION WITH NEGATIVE RETURN TEST 28 – NOTIFICATION WITH NEGATIVE RETURN TEST 29 – ON-CHANGE-OPTION CYCLIC REPORT BEHAVIOR FOLLOWING ON-CHANGE-OPTION PARAMETER VALUE TEST 29 – ON-CHANGE-OPTION CYCLIC REPORT BEHAVIOR FOLLOWING ON-CHANGE-OPTION PARAMETER VALUE

6. MDS test scenarios Credentials: Credentials will be used for ‘BIND_ONLY’. The following values will be used: User-identifier = “CSTS-USER” User-password = (in hexadecimal) ffdf01449809e4e5e677818892 Provider-identifier = “CSTS-PROVIDER” Provider-password = (in hexadecimal) 000102030405060708090a0b0c0d0e0f Bind-Invocation: Initiator-Identifier = “CSTS-USER” Responder-Port-Identifier = CSTS_PT1 Service-Type = Service-Instance-Identifier has 3 attributes: –Spacecraft-Name = “SAT” –Antenna-Identifier = “ANT” –Transfer-Service-profile-identifier = “mds01” MD-CSTS OID = {iso identified-organisation(3) standards-producing-organisation(112) ccsds(4) css(4) csts(1) framework(1) services(2) mdService(1)}

7. MDS test scenarios Start-Invocation for On-change-option cyclic report and Information Query procedures : Default list of parameters : [{FCLTU Transfer Service Provider}:{numberOfCltusRadiated}] [{RAF Transfer Service Provider}:{numberOfFramesDelivered}] [{Return TM Synchronization and Decoding }:{symbolSynchronizerLockStatus}] Parameter list name : "Space-Link_Status" {Forward space link carrier transmission}:{actual-transmit-frequency} {Forward space link carrier transmission}:{ production-status} {Return space link carrier reception}:{actual-receive-frequency} {Return space link carrier reception}:{production-status} Specific labeled individual parameters : {Antenna}:{actual-elevation} { Return TM Synchronization and Decoding }:{number-of-rs-errors-corrected} {FCLTU TS Provider} : {numberOfCltusRadiated} {RAF TS provider}:{si-state} For specific named individual parameters, the instance number must be added to the above labeled individual parameters, for example : [[{Antenna}:1]:{actual-elevation}]

8. MDS test scenarios Start-Invocation for the Notification procedure : Default list of events : [{Return TM Synchronization and Decoding}:{lossOfFrameLock}], [{Return TM Synchronization and Decoding}:{FrameLockAcquired}] Event list name “service status”: {svcProductionStatus}:{svcProductionConfigured} {svcProductionStatus}:{svcProductionInterrupted} {svcProductionStatus}:{svcProductionHalted} {svcProductionStatus}:{svcProductionOperational} Specific labeled individual events : [{Return TM Synchronization and Decoding}:{FrameLockAcquired}] {svcProductionStatus}:{svcProductionInterrupted} {svcProductionStatus}:{svcProductionOperational} For specific named individual events, the instance number must be added to the above labeled individual events, for example : [[{svcProductionStatus}:1]:{svcProductionOperational}]

9. MDS test scenarios Scenarios from test1 to test8 (on-change-option cyclic report), test11 to test18 (information query) : MD-CSTS User ---------------- Bind invocation -----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Bind return ------------------------ MD-CSTS Provider MD-CSTS User ---------------- Start invocation ----------------------------> MD-CSTS Provider delivery-cycle = 5 seconds list-of-parameters = ‘null’ (default list) / named parameters / labeled parameters/ list name / functional resource name / functional resource type / procedure type / procedure instance Id MD-CSTS User <--------------- positive Start return ------------------------ MD-CSTS Provider MD-CSTS User <--------------- Transfer Data invocation ----------------- MD-CSTS Provider 5 seconds MD-CSTS User <--------------- Transfer Data invocation ----------------- MD-CSTS Provider 5 seconds …… MD-CSTS User ---------------- Stop invocation ----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Stop return ---------------------- MD-CSTS Provider MD-CSTS User ---------------- UnBind invocation -----------------------> MD-CSTS Provider MD-CSTS User <--------------- positive UnBind return ------------------ MD-CSTS Provider

10. MDS test scenarios Scenarios from test20 to test27 (notification procedure) : MD-CSTS User ---------------- Bind invocation -----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Bind return ------------------------ MD-CSTS Provider MD-CSTS User ---------------- Start invocation ----------------------------> MD-CSTS Provider list-of-events = ‘null’ (default list) / named events / labeled events/ list name / functional resource name / functional resource type / procedure type / procedure instance Id MD-CSTS User <--------------- positive Start return ------------------------ MD-CSTS Provider event notification generated by the MDS provider simulator MD-CSTS User <--------------- Notify invocation ----------------- MD-CSTS Provider event notification generated by the MDS provider simulator MD-CSTS User <--------------- Notify invocation ----------------- MD-CSTS Provider MD-CSTS User ---------------- Stop invocation ----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Stop return ---------------------- MD-CSTS Provider MD-CSTS User ---------------- UnBind invocation -----------------------> MD-CSTS Provider MD-CSTS User <--------------- positive UnBind return ------------------ MD-CSTS Provider

11. MDS test scenarios Scenario for test9 (multiple concurrent on-change-option cyclic report) : MD-CSTS User ---------------- Bind invocation -----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Bind return ------------------------ MD-CSTS Provider MD-CSTS User ---------------- Start invocation ----------------------------> MD-CSTS Provider delivery-cycle = 5 seconds list-of-parameters = ‘null’ (default list) MD-CSTS User <--------------- positive Start return ------------------------ MD-CSTS Provider MD-CSTS User <--------------- Transfer Data invocation ----------------- MD-CSTS Provider default list every 5 seconds MD-CSTS User ---------------- Start invocation ----------------------------> MD-CSTS Provider delivery-cycle = 8 seconds list-of-parameters = named parameter MD-CSTS User <--------------- positive Start return ------------------------ MD-CSTS Provider MD-CSTS User <--------------- Transfer Data invocation ----------------- MD-CSTS Provider default list every 5 seconds and named parameter every 8 seconds MD-CSTS User ---------------- Stop invocation 1rst instance ---------> MD-CSTS Provider MD-CSTS User <--------------- positive Stop return ---------------------- MD-CSTS Provider MD-CSTS User <--------------- Transfer Data invocation ----------------- MD-CSTS Provider named parameter every 8 seconds MD-CSTS User ---------------- Stop invocation 2nd instance ---------> MD-CSTS Provider MD-CSTS User <--------------- positive Stop return ---------------------- MD-CSTS Provider MD-CSTS User ---------------- UnBind invocation -----------------------> MD-CSTS Provider MD-CSTS User <--------------- positive UnBind return ------------------ MD-CSTS Provider

12. MDS test scenarios Scenarios for test10, test19 and test28 (negative return for on-change-option cyclic report, information query and notification) : MD-CSTS User ---------------- Bind invocation -----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Bind return ------------------------ MD-CSTS Provider MD-CSTS User ---------------- Start invocation ----------------------------> MD-CSTS Provider delivery-cycle = 5 seconds list-of-parameters = ‘null’ (default list) / named parameters / labeled parameters/ list name / functional resource name / functional resource type / procedure type / procedure instance Id MD-CSTS User <--------------- negative Start return ------------------------ MD-CSTS Provider Messages : default list not defined, unknown parameter identifier, unknown list name, unknown functional resource name, unknown functional resource type, unknown procedure type, unknown procedure instance identifier, out-of-range …… MD-CSTS User ---------------- Stop invocation ----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Stop return ---------------------- MD-CSTS Provider MD-CSTS User ---------------- UnBind invocation -----------------------> MD-CSTS Provider MD-CSTS User <--------------- positive UnBind return ------------------ MD-CSTS Provider

13. MDS test scenarios Scenario for test29 (of modification on-change-option parameter value) : MD-CSTS User ---------------- Bind invocation -----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Bind return ------------------------ MD-CSTS Provider MD-CSTS User ---------------- Start invocation ----------------------------> MD-CSTS Provider delivery-cycle = 1 second (MDS prototype provider generates new parameter values every 5 seconds by default) list-of-parameters = ‘null’ (default list) On-change-option = TRUE MD-CSTS User <--------------- positive Start return ------------------------ MD-CSTS Provider MD-CSTS User <--------------- Transfer Data invocation ----------------- MD-CSTS Provider default list every 5 seconds MD-CSTS User ---------------- Stop invocation ----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Stop return ---------------------- MD-CSTS Provider MD-CSTS User ---------------- Start invocation ----------------------------> MD-CSTS Provider delivery-cycle = 1 second list-of-parameters = ‘null’ (default list) On-change-option = FALSE MD-CSTS User <--------------- positive Start return ------------------------ MD-CSTS Provider MD-CSTS User <--------------- Transfer Data invocation ----------------- MD-CSTS Provider default list every 1 second (identical values are displayed) MD-CSTS User ---------------- Stop invocation ----------------------------> MD-CSTS Provider MD-CSTS User <--------------- positive Stop return ---------------------- MD-CSTS Provider MD-CSTS User ---------------- UnBind invocation -----------------------> MD-CSTS Provider MD-CSTS User <--------------- positive UnBind return ------------------ MD-CSTS Provider