1 / 13

JAXA Prototype Test Report for the SCCS Service Management (B-1)

JAXA Prototype Test Report for the SCCS Service Management (B-1). 3rd November, 2011 JAXA ASAMA Takashi(asama.takashi@jaxa.jp). Contents. Background Test Objectives SCCS-SM Prototype Interoperability Test Report 4.1 Test Configuration 4.2 Test Items 4.3 Test Cases

isi
Download Presentation

JAXA Prototype Test Report for the SCCS Service Management (B-1)

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. JAXA Prototype Test Report for the SCCS Service Management (B-1) 3rd November, 2011 JAXA ASAMA Takashi(asama.takashi@jaxa.jp) JAXA-GN-xxx

  2. Contents Background Test Objectives SCCS-SM Prototype Interoperability Test Report 4.1 Test Configuration 4.2 Test Items 4.3 Test Cases 4.4 Anomalies 5. Comment to the schema v1.1.0 JAXA-GN-xxx

  3. 1．Background a. In March 2008, JPL and JAXA conducted the protocol validation using the prototype, which wasdeveloped 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”. b. 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. c. At the CCSDS spring meeting 2009 in Colorado Springs, JAXA proposed and coordinated preconditions and activity schedule for the second validation test using the upgraded prototype with JPL, before we start its activity. d. At the CCSDS spring meeting 2010 in Virginia, JAXA suggested the second validation test using SM Blue-1 and agreed by JPL. And JAXA coordinated the prototype testing with JPL at the meeting in Aug. 2010. e. At the last CCSDS spring meeting 2010 in Berlin, JAXA reported a problem of the difference of SOAP version between JPL and JAXA and explained the rescheduling. f. At this meeting, as the interoperability test was completed by Sep. 2011, JAXA will report the results of testing. JAXA-GN-xxx

  4. 2. Test Objectives Primary objectives of this 2nd test is the validation of the SCCSSM standard via prototyping. Specifically; a. Validate message exchange protocol b. Validate service request exchange About the test report of this second test, JAXA will add the report to the yellow book “SPACE COMMUNICATIONS SERVICE MANAGEMENT PROTOTYPE TEST PLAN AND REPORT” for SM Blue-1, receiving the support from JPL. JAXA-GN-xxx

  5. 3. SCCS-SM Prototype a. Applicable document SPACE COMMUNICATION CROSS SUPPORT SERVICE MANAGEMENT SERVICE SPECIFICATION Recommended Standard (CCSDS 910.11-B-1) August 2009. b. Applicable schema JAXA and JPL use the following latest schema: SmBlue-1Schemas-v1_1_0 (May 20th, 2011) JPL and JAXA decided to use the latest schemas. c. Function assignment JPL　： the SCCS SM service-provider (CM) prototype JAXA： the SCCS SM service-user (UM) prototype d. Target Mission :SELENE (JAXA satellite) JAXA and JPL keep the parameters of SELENE. e. Message Exchange Protocol:SOAP/Https f. SOAP: AXIS2 (SOAP1.2), JPL upgraded the CSSXP to AXIS2 (SOAP1.2) by the end of June. JAXA-GN-xxx

  6. 4. Interoperability Test Report The JAXA-JPL SCCS-SM Interoperability Test was conducted during normal working hours in the following period, and the test cases were conducted basically without voice contact between JPL and JAXA. (1) Test Period : August 31 through September 14 in 2011 (2) Test cases were:  Web Service Communication Test  Service Agreement Transaction Test  Trajectory Transaction Test  Configuration Profile Transaction Test  Service Package Transaction Test  Error Handling Test  Simulated Operation Test The final assessment of the tests was that both the prototype facilities of JPL and JAXA which are designated to support the Blue-1 of SCCS-SM could interface with each other. JAXA-GN-xxx

  7. 4.1 TestConfiguration JPL JAXA JAXA DNS JPL DNS Internet JPL-FW JAXA-FW CSSXP (CM) UMB-1 (UM) UMB-1 Terminal SCCS SM massage exchanged by SOAP/HTTPS OEM JAXA Flight Dynamics Figure 4-1 Test Configuration JAXA-GN-xxx

  8. 4.1 TestConfiguration (Cont.) JPL JAXA 137.xxx.xxx.xxx 133.xxx.xxx.xxx JPL-FW JAXA-FW CSSXP (CM) https connect UMB-1 (UM) https connect 128.xxx.xxx.xxx Figure 4-2 Interface between UMB-1 and CSSXP JAXA-GN-xxx

  9. 4.2 Test Items Table 4-1 Service operations implemented in Prototype (JPL & JAXA) JAXA-GN-xxx

  10. 4.3 Test Cases Table 4-2 Test Cases JAXA-GN-xxx

  11. 4.3 Anomalies Table 4-3 Anomalies in Test Cases JAXA-GN-xxx

  12. 5. Comment to the schema v1.1.0 There is a definition of pcmpskpm(symbolStream) in the schema of SubcarrierAgreement, but it is different from the Errata. In the item No.27 of SCCS-SM Blue-1 Errata Sheet, there is a revised description as following; " In Figure 7-2, remove composition associations between F401SubcarrierAgreement and F401SymbolStreamAgreement, and between R401SubcarrierAgreement and R401SymbolStreamAgreement. (Reason - symbol stream agreements should not be contained in subcarrier as well as carrier agreements.)“ In the schema SmSchemaServiceAgreement-v1.1.0.xsd, the following are set. JAXA-GN-xxx

  13. 5. Comment to the schema v1.1.0 (Cont.) <xsd:complexType name="R401SubcarrierAgreementType"> <xsd:complexContent> <xsd:extension base="SubcarrierAgreementType"> <xsd:sequence> <xsd:element name="pcmpskpm"> <xsd:complexType> <xsd:sequence> <xsd:element name="symbolStreamAgreement" type="R401SymbolStreamAgreementType"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> Therefore, if the R401SubcarrierAgreement doesn't have the "pcmpskpm(symbolStream)", it becomes the schema check error by all means. JAXA-GN-xxx

More Related