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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

DSPU-3<br />

DSPU-4<br />

DSPU-5<br />

UM should transmit the DSP-I before expiration of the<br />

min<strong>Service</strong>DefinitionLeadTime parameter of the <strong>Service</strong> Agreement.<br />

UM shall validate that a received DSP-SR or DSP-FR conforms to all DSP-SR or DSP-FR<br />

syntactic validation requirements specified in table 4-53 or table 4-56, respectively. If the<br />

return fails any of the syntactic validation requirements, UM shall process the message set<br />

containing the syntactically invalid return in accordance with the Invoker Requirements for<br />

Two-Phase Operation Procedures.<br />

UM shall validate that a received DSP-SR or DSP-FR conforms to all DSP-SR or DSP-FR<br />

service management validation requirements specified in table 4-53 or table 4-56, respectively.<br />

If the return fails any of the service management validation requirements, UM shall process the<br />

service management-invalid return in accordance with the Invoker Requirements for Two-<br />

Phase Operation Procedures.<br />

4.5.3.2 CM Requirements for the DELETE_SERVICE_PACKAGE Operation<br />

Table 4-51: CM Requirements for the DSP Operation<br />

DSPC-1<br />

DSPC-2<br />

DSPC-3<br />

DSPC-4<br />

DSPC-5<br />

DSPC-6<br />

DSPC-7<br />

CM shall conform to all Performer Requirements for Two-Phase Operation Procedures as<br />

specified in 3.4.1.6.2.<br />

CM shall validate that a received DSP-I conforms to all DSP-I syntactic validation<br />

requirements specified in this table and table 4-52, Data Set Composition and Relationship<br />

Requirements for the DSP-I. If the DSP-I fails any of the syntactic requirements, CM shall<br />

process the message set containing the syntactically invalid invocation in accordance with the<br />

Performer Requirements for Two-Phase Operation Procedures.<br />

CM shall validate that the DSP-I conforms to all DSP-I service management validation<br />

requirements specified in table 4-52, Data Set Composition and Relationship Requirements. If<br />

the DSP-I fails any of the service management requirements, CM shall cease processing the<br />

DSP-I and respond to UM with a DSP-FR message.<br />

NOTE – The content of the DSP-FR depends on the nature of the validation failure, and is<br />

specified in table 4-48<br />

CM shall validate that the scheduled<strong>Service</strong>PackageStopTime (for an SLS <strong>Service</strong><br />

Package) or scheduledAccessStopTime (for a Retrieval <strong>Service</strong> Package) for the<br />

referenced <strong>Service</strong> Package has not already passed.<br />

[service management validation]<br />

If the SLE Complex has locally defined DSP-I relationship requirements in addition to those<br />

specified in this Recommended Standard, CM shall validate that the DSP-I conforms to all<br />

such local requirements.<br />

[service management validation]<br />

CM shall validate that the sleSmCreatorName associated with the DSP-I is the same as<br />

the sleSmCreatorName of the <strong>Service</strong> Package associated with the servicePackageId<br />

referenced by the servicePackageRef in the DSP-I.<br />

[service management validation]<br />

If the SLE Complex has locally defined DSP-I requirements in addition to those specified in<br />

this Recommended Standard that could cause a DSP-I to be denied, CM shall validate that the<br />

DSP-I conforms to all such local requirements.<br />

[service management validation]<br />

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

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

Saved successfully!

Ooh no, something went wrong!