Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
SPCU-4
SPCU-5
SPCU-6
If the servicePackageRef does not match the servicePackageId for any Service
Package within the context of the referenced Service Agreement, UM
a) shall cease processing the SPC-N;
b) should contact CM via means outside of this Recommended Standard.
[service management validation]
If the SPC-N is valid, UM shall
a) remove the Service Package from its operational schedule;
b) remove the Service Package as counting against the following parameters of the Service
Agreement:
1) maxSlsServicePackages (for an SLS Service Package);
2) maxSlsServicePackagesPerTimePeriod (for an SLS Service Package);
3) maxRtrvlServicePackages (for a Retrieval Service Package); and
4) maxRtrvlServicePackagesPerTimePeriod (for a Retrieval Service
Package).
c) return a SPC-C.
[confirm operation]
UM shall conform to all SPC-C Data Set Composition and Relationship Requirements when
creating and transmitting an SPC-C as specified in table 4-78.
4.8.3.2 CM Requirements for the SERVICE_PACKAGE_CANCELLED Operation
Table 4-75: CM Requirements for the SPC Operation
SPCC-1
SPCC-2
SPCC-3
SPCC-4
SPCC-5
CM shall conform to all Notifier Requirements for Notified Operation Procedures as specified
in 3.4.3.6.1.
CM shall conform to all SPC-N Data Set Composition and Relationship Requirements when
creating and transmitting an SPC-N as specified in table 4-77.
Upon occurrence of an event that requires the Service Package to be cancelled, CM shall
a) remove the Service Package from its operational schedule;
b) remove the Service Package as counting against the following parameters of the Service
Agreement:
1) maxSlsServicePackages (for SLS Service Packages);
2) maxSlsServicePackagesPerTimePeriod (for SLS Service Packages);
3) maxRtrvlServicePackages (for Retrieval Service Packages); and
4) maxRtrvlServicePackagesPerTimePeriod (for Retrieval Service Packages).
c) Transmit a SPC-N
[perform operation]
CM shall validate that a received SPC-C conforms to all SPC-C syntactic validation
requirements specified in table 4-78. If the confirmation fails any of the syntactic validation
requirements, CM shall process the message set containing the syntactically invalid
confirmation in accordance with the Notifier Requirements for Notified Operation Procedures
as defined in table 3-36.
CM shall validate that a received SPC-C conforms to all SPC-C service management
validation requirements specified in table 4-78. If the confirmation fails any of the service
management validation requirements, CM shall process the service management-invalid
confirmation in accordance with the Notifier Requirements for Notified Operation Procedures
as defined in table 3-36.
CCSDS 910.11-R-2 Page 4-84 March 2008