Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
CSPC-27
CSPC-28
CSPC-29
CSPC-30
If the CSP-I is valid and is for a Retrieval Transfer Service Service Package, CM:
a) shall reserve the resources to provide the retrieval transfer service instance in accordance with the
referenced profile, such that:
1) the scheduledAccessStartTime is equal to accessStartTime of the corresponding
RetrievalTsInstanceRequest; and
2) the scheduledAccessStopTime is equal to accessStopTime of the corresponding
RetrievalTsInstanceRequest;
3) the providerId and providerPortId are assigned;
b) shall assign a unique (within the scope of the Service Package) Transfer Service Instance Number
to the retrieval transfer service instance;
c) shall issue a CSP-SR message specifying the scheduled access start and stop times associated
with the transfer service instance.
[perform operation]
If the CSP-I is valid and is for an SLS Transfer Service Service Package, CM shall count the Service
Package as applying against the following parameters of the Service Agreement:
a) maxSlsServicePackages; and
b) maxSlsServicePackagesPerTimePeriod.
[perform operation]
If the CSP-I is valid and is for a Retrieval Transfer Service Service Package, CM shall count the
Service Package as applying against the following parameters of the Service Agreement:
a) maxRtrvlServicePackages; and
b) maxRtrvlServicePackagesPerTimePeriod.
[perform operation]
CM shall conform to all CSP-SR, CSP-FR, and CSP-AR Data Set Composition and Relationship
Requirements when creating and returning a CSP-AR (see table 4-19), CSP-SR (see table 4-40), and
CSP-FR (see tables 4-38 and 4-39).
4.3.4 MESSAGE STEREOTYPE
4.3.4.1 General
The message stereotype is an extension of the
message stereotype defined in the Document Exchange Protocol
(section 3). This stereotype captures all the minimum parameters and data set relationships
that are common among invocation messages that create or update a Service Package, in
addition to the parameters of an Invocation message. By itself, this particular stereotype
does not constitute a message per the Document Exchange Protocol. The stereotype is
applied to CreateServicePackageInvocation message and the
ReplaceServicePackageInvocation message, which are specified in subsequent
subsections. Any message that applies the
stereotype also conforms to the data set composition and relationship requirements for, and
inherits the parameters of, the stereotype as specified in 3.3.4.3.2.
Figure 4-4 shows the message structure of the
message stereotype as a class diagram.
CCSDS 910.11-R-2 Page 4-14 March 2008