Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
4 SERVICE PACKAGE OPERATIONS
4.1 GENERAL
There are seven Service Package operations that CM can perform when invoked by UM:
– CREATE_SERVICE_PACKAGE—to request creation of a Service Package at CM;
– REPLACE_SERVICE_PACKAGE—to replace parameters or references in an existing
Service Package at CM (this induces re-processing by CM);
– DELETE_SERVICE_PACKAGE—to delete a Service Package at CM;
– SELECT_ALTERNATE_SCENARIO—to invoke an alternate scenario of an existing
Service Package at CM;
– QUERY_SERVICE_PACKAGE—to query the content of an existing Service Package
at CM.
– APPLY_NEW_TRAJECTORY—to apply a new trajectory to an existing Service
Package at CM.
– APPLY_NEW_SPACE_LINK_EVENTS_PROFILE—to apply a new Space Link
Events Profile to an existing Service Package at CM.
There are two Service Package operations that CM can perform autonomously and notify
UM:
– SERVICE_PACKAGE_CANCELLED—to notify the UM of a cancelled (by CM)
Service Package;
– SERVICE_PACKAGE_MODIFIED—to notify the UM of a modification (by CM) to
a Service Package;
There is one Service Package operation that UM can perform when invoked by CM:
– CONFIRM_TENTATIVE_SERVICE_PACKAGE—to confirm acceptance of a
Service Package that has been proposed by CM based on rules previously specified
by UM.
The lifecycle of a service package, as created and held by CM, is modeled as a state machine
and is shown in figure 4-1 through figure 4-3, and in table 4-1.
Note that any service management messages which fail validation at the level of the
Document Exchange Protocol are never associated to a Service Package, cannot affect the
state of a Service Package, and do not appear in the state machine.
CCSDS 910.11-R-2 Page 4-1 March 2008