23.05.2015 Views

Space Link Extension - Service Management - CCSDS

Space Link Extension - Service Management - CCSDS

Space Link Extension - Service Management - CCSDS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT<br />

stored at CM. CM re-evaluates all of the scenarios of the indicated existing <strong>Service</strong> Packages<br />

that reference the superseded events profile to ensure that it (CM) can continue to provide the<br />

agreed-upon support. If it can continue to provide the services, CM returns the updated<br />

<strong>Service</strong> Package information, indicating the new, updated events. If it cannot, CM returns the<br />

appropriate error information, but does not update the <strong>Service</strong> Package to utilize the updated<br />

events profile; i.e., the <strong>Service</strong> Package is retained as is prior to the ANSLEP-I.<br />

2.2.3.9 CONFIRM_TENTATIVE_SERVICE_PACKAGE<br />

CM invokes a CONFIRM_TENTATIVE_SERVICE_PACKAGE operation to offer a contact<br />

at a time specified within the invocation, as determined by rule-based scheduling performed<br />

by CM. All details of such rule-based scheduling are bilaterally agreed between UM and CM<br />

and are beyond the scope of the SLE <strong>Service</strong> <strong>Management</strong> Recommended Standard. A<br />

ConfirmTentative<strong>Service</strong>PackageInvocation (CTSP-I) message contains a<br />

description of the tentative <strong>Service</strong> Package, which has the following restrictions:<br />

a) the <strong>Service</strong> Package will contain precisely one service scenario;<br />

b) retrieval transfer services are not available via rule-based scheduling;<br />

c) space link event profiles are not available via rule-based scheduling;<br />

d) specification of transfer services cannot be deferred in rule-based schedules.<br />

UM confirms the service package by sending a ConfirmTentative<strong>Service</strong>-<br />

PackageSuccessfulReturn (CTSP-SR). If UM does not want to use the tentative<br />

service package, it declines by sending a ConfirmTentative<strong>Service</strong>Package-<br />

FailedReturn (CTSP-FR).<br />

2.2.3.10 SERVICE_PACKAGE_CANCELLED<br />

CM invokes a SERVICE_PACKAGE_CANCELLED operation when it is unable to continue<br />

with a commitment to provide the agreed-upon services for an existing <strong>Service</strong> Package. This<br />

may be the result either of internal CM conditions or of a <strong>Service</strong> Package that still has items,<br />

such as transfer services or event sequences deferred beyond the mutually agreed minimum<br />

service definition lead time (prior to the start time of the <strong>Service</strong> Package).<br />

This operation results in a notification to UM of the cancelled <strong>Service</strong> Package.<br />

2.2.3.11 SERVICE_PACKAGE_MODIFIED<br />

CM invokes a SERVICE_PACKAGE_MODIFIED operation only when it can continue to<br />

support the <strong>Service</strong> Package if modifications are applied. As condition of performing this<br />

operation, CM ensures that it is within all of the constraints of the CSP-I of the <strong>Service</strong><br />

Package and any subsequent RSP-I, or SAS-I, applied to the <strong>Service</strong> Package. In other<br />

<strong>CCSDS</strong> 910.11-R-2 Page 2-10 March 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!