Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
Notes on the Service Package Lifecycle table:
1. For brevity, responses (e.g., CSP-AR, CSP-SR, CSP-FR) are abbreviated to the
suffix, where the operation is unambiguously identified by the invocation.
2. * = cannot happen; indicates protocol failure; reject.
3. Each transition to Scheduled goes to Defined if all items are defined, otherwise to
Pending.
4. The RSP, QSP, SAS, ANSLEP, and ANT three-phase operations do not affect the SP
lifecycle until (and unless) they are successfully performed. Service Management
validation of RSP, ANSLEP, and ANT invocations takes place independently of, and
in parallel to, the state machine.
4.2 OWNERSHIP OF SERVICE PACKAGES
If the Service Package is originally created via an invocation of the
CREATE_SERVICE_PACKAGE operation, the Service Package is owned by the UM entity
associated with the sleSmCreatorName used in the SleSmMessageSet that contains
the CreateServicePackageInvocation message.
If the Service Package is originally created by CM via a rule-based process and proposed to
UM via an invocation of the CONFIRM_TENTATIVE_SERVICE_PACKAGE operation, the
Service Package is owned by the UM entity associated with the
proposedServicePackageOwnerName specified in the Service Agreement.
4.3 CREATE_SERVICE_PACKAGE (CSP) OPERATION
4.3.1 PURPOSE
The CREATE_SERVICE_PACKAGE (CSP) operation allows UM to request that CM add a
Service Package to its operational schedule.
4.3.2 PROCEDURE
The procedure for the CSP operation is a three-phase operation procedure, which follows the
three-phase operation procedure pattern specified in 3.4.2.
The CSP operation involves the exchange of the following messages:
– CreateServicePackageInvocation (CSP-I);
– CreateServicePackageAcknowledgedReturn (CSP-AR);
CCSDS 910.11-R-2 Page 4-5 March 2008