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 />

CSPD-29<br />

CSPD-30<br />

CSPD-31<br />

CSPD-32<br />

CSPD-33<br />

CSPD-34<br />

a) A <strong>Service</strong>PackageResult message shall contain a <strong>Space</strong><strong>Link</strong>SessionResult<br />

data set if the corresponding <strong>Service</strong>PackageInvocation contained a<br />

<strong>Space</strong><strong>Link</strong>Session data set.<br />

b) A <strong>Service</strong>PackageResult message shall contain a RetrievalTsResult data set if<br />

the corresponding <strong>Service</strong>PackageInvocation contained a<br />

RetrievalTsInstanceRequest data set for which the<br />

transfer<strong>Service</strong>ProfileRef references a non-bilateral Retrieval Transfer <strong>Service</strong><br />

Profile.<br />

c) A <strong>Service</strong>PackageResult message shall contain a<br />

BilateralRetrievalTsResult data set if the corresponding<br />

<strong>Service</strong>PackageInvocation contained a RetrievalTsInstanceRequest data<br />

set for which the transfer<strong>Service</strong>ProfileRef references a bilateral Retrieval<br />

Transfer <strong>Service</strong> Profile.<br />

[service management validation]<br />

The <strong>Space</strong><strong>Link</strong>SessionResult data set shall contain:<br />

a) one <strong>Service</strong>ScenarioReference data set;<br />

b) one or more <strong>Service</strong>ScenarioResult data sets;<br />

c) zero or more SlsTsInstanceResult data sets; and<br />

d) zero or more BilateralSlsTsInstanceResult data sets.<br />

[syntactic validation]<br />

The <strong>Space</strong><strong>Link</strong>SessionResult data set shall contain the same number of<br />

<strong>Service</strong>ScenarioResult data sets as the number of <strong>Service</strong>Scenario data sets contained<br />

in the corresponding <strong>Service</strong>PackageInvocation.<br />

[service management validation]<br />

For the <strong>Service</strong>ScenarioReference data set, the primeScenarioRef parameter shall<br />

have the same value as the primeScenarioRef of the <strong>Service</strong>PackageInvocation.<br />

[service management validation]<br />

Each SlsTsInstanceResult data set shall contain either:<br />

a) no SlsTsProfileRespecResult and no SlsTsProfileInEffect data sets;<br />

b) one SlsTsProfileRespecResult data set and one SlsTsProfileInEffect data<br />

set.<br />

[syntactic validation]<br />

For each SlsTsProfileRespecification data set in the corresponding<br />

<strong>Service</strong>PackageInvocation that references a non-bilateral <strong>Space</strong> <strong>Link</strong> Session Transfer<br />

<strong>Service</strong> Profile, the SlsTsInstanceResult data set with the same value for the<br />

transfer<strong>Service</strong>ProfileRef parameter shall contain one<br />

SlsTsProfileRespecResult data set and one SlsTsProfileInEffect data set.<br />

[service management validation]<br />

NOTE – SlsTsProfileRespecification data sets that reference bilateral <strong>Space</strong> <strong>Link</strong><br />

Session Transfer <strong>Service</strong> Profiles are reflected in the content of the<br />

bilateralSlsTsInstanceResultData parameter of the corresponding<br />

BilateralSlsTsInstanceResult data set. How these changes are reflected are<br />

determined bilaterally and are outside the scope of this specification.<br />

CSPD-35<br />

Each SlsTsProfileRespecResult data set shall contain one or more<br />

RespecifiedParameter data sets.<br />

[syntactic validation]<br />

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

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

Saved successfully!

Ooh no, something went wrong!