23.05.2015 Views

Space Link Extension - Service Management - CCSDS

Space Link Extension - Service Management - CCSDS

Space Link Extension - Service Management - CCSDS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT<br />

NOTE – Submission of trajectory data occurs on the order of months, days or minutes<br />

in advance of the support period to which the trajectory data applies.<br />

b) DELETE_TRAJECTORY_PREDICTION (DTP)—to delete a Trajectory Prediction<br />

that currently resides at CM;<br />

c) QUERY_TRAJECTORY_PREDICTION (QTP)—to query the content of a<br />

Trajectory Prediction that resides at CM.<br />

No Trajectory Prediction operations can be performed by UM.<br />

2.2.5.1 Storage Area at CM<br />

UM is responsible for managing the Trajectory Predictions resident at CM. UM must keep<br />

track of the expiration dates for the Trajectory Predictions and add and delete as necessary.<br />

CM will not notify UM when Trajectory Predictions resident at CM expire.<br />

There is a limited amount of storage space available at CM for Trajectory Predictions. The<br />

maximum allowed storage area is defined in the applicable <strong>Service</strong> Agreement. CM will<br />

reject new Trajectory Predictions once this storage space is exceeded.<br />

2.2.5.2 Trajectory Prediction Validation<br />

When UM requests the addition of a new Trajectory Prediction, the validation performed by<br />

CM is limited, i.e., checking of storage space available at CM, sanity checking of time<br />

window, conformance to indicated format, uniqueness of Trajectory Prediction identifier.<br />

Further locally-defined checks may be performed by CM as part of the validation of a<br />

<strong>Service</strong> Package that references the Trajectory Prediction.<br />

Requests for deletion of Trajectory Predictions that are referenced by pending or executing<br />

<strong>Service</strong> Packages will be rejected.<br />

To allow UM to keep track of referenced Trajectory Predictions, the<br />

QUERY_TRAJECTORY_PREDICTION operation returns the list of pending or executing<br />

<strong>Service</strong> Packages that reference the queried Trajectory Prediction.<br />

2.2.6 SERVICE AGREEMENT SERVICE<br />

The negotiation and generation of the <strong>Service</strong> Agreement are beyond the scope of this<br />

Recommended Standard. For this reason, there is only one <strong>Service</strong> Agreement operation that<br />

CM can perform when invoked by UM:<br />

QUERY_SERVICE_AGREEMENT (QSA)—to query the content of a <strong>Service</strong><br />

Agreement that resides at CM. The QSA operation has been defined to support the<br />

return of <strong>Service</strong> Agreement data either in the format defined in this Recommended<br />

Standard or in a bilaterally agreed format.<br />

No <strong>Service</strong> Agreement operations can be performed by UM.<br />

<strong>CCSDS</strong> 910.11-R-2 Page 2-13 March 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!