1. DSN CCSDS SLE SM Prototype Plan Erik Barkley December 2006

2. eb-2 Agenda Background Information (Why are we having this meeting?) Overview of Prototype Interoperations Plan Questions and Actions for DSN

3. eb-3 Background Information March 2006: CCSDS SMWG released draft recommendation for SLE Service management (SMWG  Service Management Working Group; http://public.ccsds.org/sites/cwe/css-sm/default.aspx) –Agency reviews held March  June 2006 –Recommendation currently being updated based on hundreds of inputs IOAG 10 meeting held October 2006 (IOAG  Interagency Operations Advisory Group; http://www.ioag.org) –Emphasized need for completion of CCSDS Service Management effort –Emphasized need for prototype interoperations –ESA, JAXA, JPL agreed to support interoperations demos ESA: Will fund prototype efforts starting January 2007 Based on “jumpstarting” previous prototype effort that achieved interoperations with JPL prototype in the autumn of 2004 Target mission identified so far: ROSETTA JAXA: Claim to be ready anytime we are Based on “handrolling” service request messages Target mission identified so far: SELENE-A JPL: Service management interface available beginning in January 2007 Based on current ongoing prototype activity –Underlying concern that if standardized service management is not achieved sooner rather than later ad-hoc interfaces will continue to proliferate Major agency alignment/agreement; we need to take advantage of it!

4. eb-4 Prototype Interoperations Plan Outline Objectives Scenarios Test Configurations Evaluation Criteria Timeline

5. eb-5 Prototype Interoperations Plan: Objectives CCSDS Level (in reference to Service Management specification) –Validate information for coordination of telemetry and command services is sufficient. –Note: Ranging/radiometric services to be added as capability becomes available –Validate document exchange protocol. –Gain experience in application of security techniques. –Provide information for best practices. –Validate feasibility of approach for deployments to flight projects of various agencies. DSN Level –Validate mapping from service level to equipment level for coordination of telemetry and command services. –Gain understanding of modifications needed for a full adoption of recommendation by internal subsystems (SPS, SSS)

6. eb-6 Prototype Interoperations Plan Scenarios (1/2): Interface Verification –Goals Exercise Trajectory Inputs and Queries Exercise Configuration Profile input and queries Exercise Event Sequence inputs and queries Exercise Service Package input and queries Exercise Error/Exception Handling Referential framework errors Service agreement violations Security violations (e.g, invald digital signature) –Test steps Conduct internal tests prior to engaging prototype partners Develop service agreements with partners Conduct success oriented message exchanges Conduct message exchanges geared for producing errors/exceptions

7. eb-7 Prototype Interoperations Plan Scenarios (2/2): Shadow Tracking

8. eb-8 Prototype Interoperations Plan: Test Configurations

9. eb-9 Prototype Interoperations Plan: Evaluation Criteria Interface Verification –"Normal" interactions result in prototype databases (UM and CM) being updated as expected. – Error conditions are properly flagged with error messages as per the recommendation. Shadow Tracking –DSN Support Product Generation Schedule request are generated in accordance with the service package parameters. To include some TBD level of equipment mapping (e.g., proper aperture, microwave configuration, etc.) DKF outputs are produced in accordance with event sequence referenced by service package. SICF outputs are produced in accordance with service package parameters. Predicts generation occurs in accordance with the configuration profile referenced by the service package. Predicts generation occurs in accordance with the trajectory referenced by the service package. –SLE Transfers Services UM is able to utilize the SLE SM coordinated SLE transfer services; ie BIND enabled over shadow-track specific provider Id, User Id, Information. (Ensure that legacy SICF allowing transfer service to not operate "by accident"). Duplicate (more or less) telemetry frames received by MDOS/Prototype partner. –Space Link Shadow track events occur/managed properly, mirror the events that occur via DSN services coordinated via existing DSN SM interface.

10. eb-10 SLE Service Management Operations Demo Plan - Timeline - Oct 2006 Jan 2007 Jul 2007Jan 2008 Technology Mapping Recommendations (Magenta Book) DSN Red-1 Compliant Prototype DSN Red-2 Compliant Prototype Concept of Operations (Green Book) SLE SM Spec (Blue Book): Red-2 Production, Agency Reviews Jul 2008 Interoperations/Demo Track Document Production Track Prototype capable of supporting Red-1 compliant interoperations; command, telemetry services Prototype capable of supporting Red-2 compliant interoperations; command, telemetry, ranging services JAXA Red-1 Compliant Prototype JAXA Red-2 Compliant Prototype Prototype capable of supporting Red-2 compliant interoperations; command, telemetry, ranging services Prototype capable of supporting Red-1 compliant interoperations; command, telemetry services ESA Red-1 Compliant Prototype ESA Red-2 Compliant Prototype Prototype capable of supporting Red-1 compliant interoperations; command, telemetry services

11. eb-11 Questions and Actions for the DSN Coordination with Interagency Level Mission Operations –Determine when the missions are able to accommodate shadow tracking activities Determine extent of shadow tracking activities –Telemetry? Command? (Note: ranging can not be addressed via near-term prototype efforts) Schedule shadow track activities via DSN/RAPS scheduling process Coordination/briefing needed for DSN operational teams? –Presumably support products distribution automatic for shadow track at DSCC (as activity on DSN 7-day schedule) –Does anything special need to be done for AMMOS (SLE RxF service originates here)? Engineering coordination –CSSXP database instance needs to be available/maintained on SPS –Testing of CSSXP inputs by SPS required Testing from two years ago went as far as control of DLF generation; things have changed since then and we need to now go all the way to SDP production (SPS SOAK begins in January) Managerial coordination –Do we need an overall POC/management lead for this effort at JPL? Ensure that partner agency are/continue to be up to speed? Ensure that DSN internal organizations are properly coordinated? Ensure that proper instrumentation/verification occurs via shadow tracking?

12. Additional Background Information

13. eb-13 CCSDS 910.11-R-1 At a Glance