2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 1 Validation Test Coordination for the SCCS Service Management (R-3.4) 20. April 2009 JAXA YAGI SUZUKI JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 2 Contents 1 Background 2 Objectives 3 Preconditions 4 Test Plan 5 Test Configuration 6 Security:Encryption 7 Bi-lateral information 8 Schedule JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 3 1 ． Background a. Interoperability test activity by participant agencies of the CCSDS to validate the Service Management was determined at a meeting of the IOAG-10 on October, b. In March 2008, JPL and JAXA conducted the protocol validation using the prototype, which was developed in compliance with the CCSDS Service Management(R-1), and we also conducted the tracking activities using the JPL DSN and the JAXA satellite “SELENE”. c. At the IOAG-12 in September 2008, JPL and JAXA agreed to conduct a second validation test between JPL and JAXA using a prototype, which is compliant with the Service Management Red-2. d. At the CCSDS SMWG in Berlin, Germany in autumn 2008, JAXA reported that JAXA and JPL will conduct a second validation test using upgraded prototype in August e. And now, at the CCSDS SMWG in Colorado Springs, USA in spring 2009, JAXA is going to coordinate preconditions and activity schedule for the second validation test using the upgraded prototype with JPL, before we start its activity. JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 4 2. Objectives Primary Objectives Validation of the SCCS SM standard via prototyping Specifically; a. Validate message exchange protocol b. Validate service request exchange JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 5 3. Preconditions a. Applicable document SPACE COMMUNICATION CROSS SUPPORT SERVICE MANAGEMENT SERVICE SPECIFICATION Draft Recommended Standard (CCSDS R-2.1) b. Applicable schema W3cSchemaMappingOfSccsSmDataSets-v0_5_0 c. Function assignment JAXA ： the SCCS SM service-user prototype JPL ： the SCCS SM service-provider prototype d. Target Mission : SELENE but this interoperability activities (e.g. Shadow tracking) will not use the satellite in orbit. Change the current applicable document from “CCSDS R-2.1” to “CCSDS R-3.4”, which is the latest recommendation as of May Change the current applicable schema from “W3cSchemaMappingOfSccsSmDataSets-v0_5_0” to “SmRed-3Schemas-v0_6_1”, which is the latest schema as of end of April (CCSDS R-3.4) SmRed-3Schemas-v0_6_1) JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 6 4. Test Plan a.DATA INTERFACE TEST This test is conducted to verify the SCCS-SM interface between the service-provider prototype and the service-user prototype. SCCS-SM message exchange is handled by SMTP. Table 3-1 Service operations planned to be implemented into JAXA SCCS-SM Service user Prototype JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 7 b. INTEROPERABILITY TEST The purpose of this test is to confirm that JAXA and JPL can perform the service request according to the scenario, which is assumed the service request in the cross support, by exchanging messages of the Service Management using the prototype. (JAXA would like to determine the scenario and a method of the validation by coordination with JPL.) JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 8 5 ． Test Configuration Figure 4-1 Test Configuration for SM(R-3.3) JPL JAXA / Tsukuba SCCS SM Service-Provider Prototype SCCS SM Service-User Prototype (UMR-3.3) Internet JAXA Flight Dynamics system OEM SCCS SM massage exchanged by SMTP by SOAP/HTTPS JAXA thinks that this protocol change will impact the activity schedule at JAXA because the JAXA UMR staff members have never developed systems by using SOAP/HTTPS, and they don’t have enough knowledge of SOAP/HTTPS. For this reason, JAXA predicts our proposed development period will be extended for at least three months, and thus, the start of the test with JPL, which was originally intended in late August, will be consequently postponed until late November 2009 (See Chapter 8). Change the data transfer protocol from SMTP to SOAP/HTTPS in response to the results of the prototype interoperations conducted between JPL and ESA in JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 9 Figure 5-1 SM massage exchange by SSL comunication JPL JAXA / Tsukuba SCCS SM Service-Provider Prototype SCCS SM Service-User Prototype (UMR-1) SM massage exchanged by SMTP 6 ． Security:Encryption In the JPL-JAXA test in March 2008, we took security measures by using Xml encryption. For the second test in 2009, JAXA wants to use HTTPS, which is one of the secure communication protocols, for taking new security measures. JPL JAXA / Tsukuba SCCS SM Service-Provider Prototype SCCS SM Service-User Prototype (UMR-3.3) SM massage exchanged by SOAP/HTTPS Encrypted Xml Non Encrypted Xml SSL comunication Test in March 2008 Test in 2009 JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 10 7 ． Bi-lateral information As described in the preceding chapter, we exchanged the SM message using SMTP in the JPL-JAXA test in March However, for the communication by SMTP, we couldn’t transfer trajectory data because there was a limit to the transmission of a large amounts of data due to the communication restrictions within JAXA. In order to resolve this communication restriction, JAXA compressed the large amounts of trajectory data, and then we succeeded in message exchange as bi-lateral information. JAXA expects that bi-lateral information will not be used for the test in 2009 because we think there will no restriction for the SMTP communication by changing the communication protocol to SOAP/HTTPS. JAX-GN-134

2009 Spring CCSDS meeting ( Colorado Springs,USA ) SMWG 11 8 ． Schedule Table 6-1 Schedule for SCCS SM (R-3.3) Validation test JAXA would like to propose the following schedule change of activities: JAX-GN-134