Presentation is loading. Please wait.

Presentation is loading. Please wait.

SGSS Extensions to and Modifications of CCSDS Space Communication Cross Support Service Management 15 - 19 October 2012 John Pietras Global Science and.

Similar presentations


Presentation on theme: "SGSS Extensions to and Modifications of CCSDS Space Communication Cross Support Service Management 15 - 19 October 2012 John Pietras Global Science and."— Presentation transcript:

1 SGSS Extensions to and Modifications of CCSDS Space Communication Cross Support Service Management October 2012 John Pietras Global Science and Technology, Inc, Greenbelt, MD, USA

2 2 SCCS-SM Lifecycle 2

3 SCCS-SM Lifecycle Addressed by SCCS-SM Blue-1 3

4 4 SCCS-SM Lifecycle Addressed by SGSS

5 5 Service Agreement  SGSS adds a new information entity – the Mission Profile  Conceptually could be considered part of the Service Agreement  SGSS Service Agreement will be extended to address SN/SGSS-specific details  E.g., PN coding

6 6 Configuration Profiles  SGSS excludes the standard add and delete operations but includes a new modify operation  Modify is essentially the same as add but the total number and names are constrained  Space Communication Service Profile  GD is extending the existing CCSDS 401-based Space Link Carrier profiles (and agreements) to include CDMA parameters  Possible alternative for CCSDS Next Gen SM would be to base configuration profiles on CCSDS Data Transmission an PN Ranging for 2 GHz CDMA Link for Data Relay Satellite Blue Book, which already standardizes a subset of SN RF modulation terminology  Support for IP over CCSDS Current ICD based on draft material provided by SGSS-Standards liaison  Support for IP over HDLC will still be required No reference specification for IP over HDLC  SLE Transfer Service Profiles  ROCF  EFCLTU

7 Service Packages (1 of 3)  SGSS replaces the CCSDS Service Package Request with the Flexible Service Package Request  Increased flexibility in scheduling  Scheduling windows A series of time-defined windows that specify when the requested Service Package can be scheduled  Resource constraints Allow multiple types/instances of SN resources to be specified as required, preferred, acceptable or unacceptable o Generalization of SCCS-SM antenna selection  Recurring schedule requests  A form of rule-based scheduling in which the rules are conveyed as part of a recurring schedule request  SGSS does not use CTSP operation  Service Package Request organized as one or more Event requests (new SGSS capability)  Wait listing  UM can flag a service request to be put on a wait list if it cannot be scheduled during the initial scheduling attempt  CM will attempt to schedule the request until the wait list expiration time specified in the service request 7

8 Service Packages (2 of 3)  Alternatives  Allows Event requests within a Service Package request to be linked such that if the first request in the chain cannot be scheduled, the alternatives will be followed until one can be scheduled or the end of the chain is reached  Allows Space Communication Service requests within an Event request to be linked for alternative selection  Specification of timing relationships among services in service request  Coupled to the start time of another service  Bound to be within the period of another service  Specification of timing relationships among Events in service request  Coupled to the start time of another Event  Bound to be within the period of another Event  Use freeze interval for Service Package modification 8

9 9  Waitlisting and recurrent requests change semantics of Create Service Package Successful Return and Service Package Modified  In CCSDS , a successful return (SR) is used to indicate that a Service Package has been successfully scheduled  In SGSS extended CCSDS-SM, an SR is returned under any of the following conditions A specific time type Service Package has been successfully scheduled` A specific time type Service Package Request has not been scheduled but has been waitlisted One or more occurrences of a recurrent time type Service Package have been successfully scheduled No occurrences of a recurrent time type Service Package have been successfully scheduled for the current scheduling period, but the request is still valid for future scheduling periods  In extended CCSDS-SM, the Service Package Modified operation is being extended to be used when: A Service Package Request has come off the waitlist and onto the schedule A Service Package has been scheduled based on a recurrent request  In extended CCSDS-SM, the Service Package Cancelled operation is being extended to be used when a waitlisted Service Package Request fails to be scheduled by the latest possible time for scheduling the request  Query Flexible Service Package operation is extended to allow multiple Service Packages to be retrieved  Used to convey the Active Schedule to users Service Packages (3 of 3)

10 10 SCCS-SM Information Entities and Management Services: Trajectory Predictions A Trajectory Prediction defines the course of the mission (user/customer) spacecraft over a period of time  A Trajectory Prediction can be either:  A single state vector to be propagated  A set of vectors that form an ephemeris  State vectors and ephemeris data conform to Orbit Data Messages, CCSDS B-2  Trajectory Prediction service (optional)  Used to add, delete, and extend trajectory prediction information

11 SCCS-SM Supports Different Uses and Operations Concepts for Trajectory Predictions  Trajectory predictions have different uses in different TT&C networks  DSN uses different grades of trajectory predictions for long-range planning and view-period generation as well as generation of actual spacecraft acquisition data (pointing angles, Doppler compensation offsets, etc.)  SN equivalent of Trajectory Predictions (IIRVs) are currently used for spacecraft acquisition data generation View period information is supplied via TSWs supplied by the MOCs  The Trajectory Prediction Service supports multiple operational profiles for updating predicted trajectories  DSN generates a specific trajectory prediction (state vector or ephemeris) for each Service Package Service Packages are tightly coupled to individually-identified Trajectory Predictions  SN and NEN update predicted trajectories asynchronously with respect to requested/scheduled Service Packages Trajectory predictions are appended to the running trajectory, dropped off after their time of applicability The TT&C network (e.g., SN) uses the running trajectory to generate pointing angles, Doppler compensation, etc., to support Service Packages

12 Trajectory Predictions 12  GD currently plans to have one default trajectory prediction for each spacecraft  MOC updates the single default TP via the Extend Trajectory Prediction ETP operation  ATP is not available to define the creator of the TP  GD must either exempt TPs from ownership enforcement if ATP is not used or specify default “owners” in the Service Agreement  For contingency trajectory changes, MOC must provide updated vectors via ETP in real time  If MOCs are not be able to replace TPs quickly enough, SGSS may have to implement ATP  Use of Query TP to retrieve Relay Satellite vectors  SN must provide TDRS state vectors to user missions so that they know where to point their spacecrafts’ antennas  The TDRSs are given “well known” TPids and their vectors are then queriable via the QTP  “Lack of Vector” notification (current DAS capability, to be extended to all Events/Service Packages in SGSS)  If Trajectory Prediction data is not available at TBD minutes before the start of execution of a Service Package, the “owner” is notified

13 Planning Information  SGSS Query Planning Aid operation allows UM to request:  TDRS Unused Time  Resource Unused Time  TDRS visibility Generated by Flight Dynamics Facility and merely passed through SGSS  Ground source RFI  Mutual RFI  Calendar operations allow SGSS operators and users to add, delete, replace and query long-term items on an open, text-based calendar  Major maintenance operations  Major mission phases (e.g., launch) 13

14 Real-time Service Monitor and Control 14  CCSDS’ current plans are to implement real-time service monitoring and control via SLE-like Cross Support Transfer Services (CSTSes):  Monitored Data CSTS  Service Control CSTS  No plans in CCSDS to add monitor and control operations to SCCS-SM XML message interface  SGSS E-06 ICD adds new monitor and control operations top to the SM XML message interface  Apply Change to Service Package  Apply Service Package Reconfiguration Request  Service Package Schedule Status Report  Service Package Status Report

15 15 Service Accounting  SGSS - User MOC ICD includes the following new operations:  Find Stored Reports  Get Stored Report  Delete Stored Report  Generate Dynamic Report  Report types are currently TBD

16 Service Agreement and Configuration Profile Service Operations Summary Comparison 16 SGSS Extended CCSDS-SM operations SCCS-SM-B-1 operations Legend: Essentially equivalent Requires extension Not required by SN/SGSS new with SN/SGSS

17 17 Service Package Planning, Scheduling, and Execution Operations 17 SCCS-SM-B-1 operations Legend: Essentially equivalent Requires extension Not required by SN/SGSS new with SN/SGSS SGSS Extended CCSDS-SM operations May be needed

18 18 Trajectory Prediction Service Operations Summary Comparison SGSS Extended CCSDS-SM operations SCCS-SM-B-1 operations Legend: Essentially equivalent Requires extension Not required by SN/SGSS new with SN/SGSSMay be needed


Download ppt "SGSS Extensions to and Modifications of CCSDS Space Communication Cross Support Service Management 15 - 19 October 2012 John Pietras Global Science and."

Similar presentations


Ads by Google