Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
4.8 SERVICE_PACKAGE_CANCELLED (SPC) OPERATION
4.8.1 PURPOSE
The SERVICE_PACKAGE_CANCELLED (SPC) Operation allows CM to notify UM that it
has cancelled a Service Package from its operational schedule.
4.8.2 PROCEDURE
The procedure for the SPC operation is a Notified Operation procedure, which follows the
notified operation procedure pattern specified in 3.4.3.
The SPC operation involves the exchange of the following messages:
– ServicePackageCancelledNotification (SPC-N);
– ServicePackageCancelledConfirmation (SPC-C).
The sequence and activity diagrams for the SERVICE_PACKAGE_CANCELLED are the
notified operation procedure pattern sequence and activity diagrams specified in 3.4.3.3 and
3.4.3.4, respectively, with the argument lists:
Sequence Diagram
notifiedOperationProcedurePatternSequence {CM, UM, SPC-N, SPC-C}
Activity Diagram
notifiedOperationProcedurePatternActivity {CM, UM, SPC-N, SPC-C}
4.8.3 REQUIREMENTS
4.8.3.1 UM Requirements for the SERVICE_PACKAGE_CANCELLED Operation
Table 4-74: UM Requirements for the SPC Operation
SPCU-1
SPCU-2
SPCU-3
UM shall conform to all Recipient Requirements for Notified Operation Procedures as
specified in 3.4.3.6.2.
UM shall validate that a received SPC-N conforms to all SPC-N syntactic validation
requirements specified in table 4-77. If the notification fails any of the syntactic validation
requirements, UM shall process the message set containing the syntactically invalid notification
in accordance with the Recipient Requirements for Notified Operation Procedures as defined
in table 3-37.
UM shall validate that a received SPC-N conforms to all SPC-N service management
validation requirements specified in this table and table 4-77. If the notification fails any of the
service management validation requirements, UM shall process the service managementinvalid
notification in accordance with the Recipient Requirements for Notified Operation
Procedures as defined in table 3-37.
CCSDS 910.11-R-2 Page 4-83 March 2008