Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
6 TRAJECTORY PREDICTION OPERATIONS
6.1 GENERAL
The Trajectory Prediction operations that may be invoked by UM are:
– ADD_TRAJECTORY_PREDICTION—to add a new Trajectory Prediction at CM;
– DELETE_TRAJECTORY_PREDICTION—to delete a Trajectory Prediction that
currently resides at CM;
– QUERY_TRAJECTORY_PREDICTION—to query the content of a Trajectory
Prediction that resides at CM.
No Trajectory Prediction operations can be invoked by CM.
Subsections 6.3 through 6.5 define those operations used by UM to create, delete and query
each Trajectory Prediction that exists at the CM.
NOTE – UM is responsible for managing the Trajectory Predictions resident at CM. UM
should keep track of the expiration dates for the Trajectory Predictions and delete
and add as necessary. CM will not notify UM when Trajectory Predictions
resident at CM expire.
There is a limited amount of storage space available at CM for Trajectory
Predictions related to a Service Agreement (i.e., as defined by parameter
maxSizeTrajectoryFilestore, specified in table 7-12). CM will reject
new Trajectory Predictions once this storage space is exceeded.
The lifecycle of a trajectory prediction, as created and held by CM, is modeled as a state
machine and is shown in figure 6-1, and in table 6-1.
CCSDS 910.11-R-2 Page 6-1 March 2008