Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
Package. This capability supports the mode of operation wherein UM needs to
schedule the space link weeks or months in advance, and only needs to be concerned
about the details of the transfer services for contacts once the space link carriers are
scheduled.
In response to a CSP-I, CM acknowledges the invocation. An acknowledgement is followed
by a successful return or a failed return at or before the expected disposition time.
The Service Package is generated by CM as a result of the successful performance of a
CREATE_SERVICE_PACKAGE operation. A CreateServicePackageSuccessful-
Return (CSP-SR) contains the successfully scheduled Service Package, and indicates that
the resources needed to support all of the scenarios in the Service Package are being held in
reserve and will be applied at the specified time. It contains the definition of the space link
carrier start and stop times and service instance provision periods (given the time window
options defined in the CSP-I) and the provider-specific information required for the service
provision to take place, e.g., provider access information. It also contains details of events
which affect availability or configuration of the space link, if event sequences were specified
for the service package.
A CreateServicePackageFailedReturn (CSP-FR) indicates that some aspect of
the CSP-I could not be accommodated within the time window specified. Each failed return
identifies the reason(s) for failure.
2.2.3.3 REPLACE_SERVICE_PACKAGE
UM invokes the REPLACE_SERVICE_PACKAGE operation to modify one or more
parameters of an already created Service Package. Such a modification might be driven, for
example, by an updated ‘acquisition of signal’ or ‘loss of signal’ calculation, or by the need
to complement a partial Service Package with transfer service configuration details. This
allows the UM to update a Service Package without releasing any already allocated resources
but simply to add, remove, or change certain parameters and invoke any necessary reprocessing
by CM.
The ReplaceServicePackageInvocation (RSP-I) has almost exactly the same
information as the CSP-I, the only difference being that whereas the CSP-I contains the
identifier of the new Service Package to be created, the RSP-I contains a reference to the
identifier of the existing Service Package that is to be replaced.
Invocation of the RSP operation triggers revalidation of the Service Package as CM
determines if the new space link and transfer service configuration(s) can be supported using
the resources already allocated to the Service Package or other resources as necessary. If the
replacement is successful, the original Service Package is deleted and the replacement takes
its place. If the replacement fails, CM retains the original Service Package and informs UM
of the reason for rejecting the replacement.
CCSDS 910.11-R-2 Page 2-8 March 2008