1 12 March 2008 JPL/DSN/CSSXP Overview and Findings JPL/DSN/CSSXP Overview and Findings Crystal City, USA 12 March 2008 Erik Barkley (JPL)

2 12 March 2008 CSSXP/DSN Test Configurations

3 12 March 2008 CSSXP Data Mapping Summary OEM: -- Used in determining how to point the antenna in accordance with SELENE's apparent motion over the DSN tracking station OEM + CP -- Used in controlling calculations for Doppler compensated frequency prediction to enable DSN receivers to maintain carrier lock on the SELENE signal SP + CP -- Used to produce a sequence of events used for detailed instructions for DSN internal equipment SP -- Used to generate a schedule request for scheduling the activity; In accordance with what is scheduled via the current established DSN process as CSSXP is not operational SP can also be used for producing SICF information however Used the default information SLE configuration information is not going from CSSXP to the internal operational SLE server - JPL Internal management of SLE a little too adapted for use in non-service managed environment - BIND Test done with CSSXP override SICF generated in accordance with default information

4 12 March 2008 JPL Findings

5 12 March 2008 Most Significant Finding Management of SLE Instance Configuration SLE Recommendations allow for dynamic management Practice appears to be hardcoding/fixing information as much as possible Ramifications for CS SM specification - Appears that dynamic service package Id being mapped to SLE Instance Id information is not realistic with current implementation - Should CS SM recommendation be modified or should this be considered as transition issue at the implementations that will be worked? 3-Way communication used in inter-agency setting CS SM draft recommendation does not address this Does service package need to indicate three-way reference? What would it look like at a service level? Implies exchange of uplink ramps in near-realtime if this truly to be a committed inter-agency capability - This implies near-real-time exchange of data - Seems like an expensive proposition vs. assuming a tune-out-tune-back in model when transitioning a S/C between agency networks