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

Table 4-98: ProposedTsMap Data Set<br />

Parameter Name<br />

transfer<strong>Service</strong>-<br />

InstanceNumberRef<br />

Parameter Definition/Description<br />

The value of a transfer<strong>Service</strong>InstanceNumber<br />

parameter of one of the ProposedSlsTsInstance or<br />

ProposedBilateralSlsTsInstance data sets for<br />

this <strong>Service</strong> Package.<br />

Data<br />

Type<br />

Data<br />

Units<br />

UTC n/a n/a<br />

Applicable<br />

<strong>Service</strong><br />

Agreement<br />

Parameter<br />

4.11.4.3 Data Set Composition and Relationship Requirements<br />

Table 4-99 defines the data set composition and relationship requirements for the<br />

Proposed<strong>Service</strong>Package messages.<br />

Table 4-99: Data Set Composition and Relationship Requirements for CTSP-I<br />

CTSPD-1<br />

CTSPD-2<br />

CTSPD-3<br />

CTSPD-4<br />

A CTSP-I message shall contain:<br />

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

b) one Proposed<strong>Space</strong><strong>Link</strong>Session data set.<br />

[syntactic validation]<br />

In the <strong>Service</strong>PackageIdentification data set, the servicePackageId shall be unique<br />

with respect to all other servicePackageId parameters relative to the <strong>Service</strong> Agreement.<br />

[service management validation]<br />

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

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

b) zero or more ProposedSlsTsInstance data sets; and<br />

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

[syntactic validation]<br />

The Proposed<strong>Service</strong>Scenario data set shall contain:<br />

a) one Proposed<strong>Space</strong><strong>Link</strong><strong>Service</strong> data set: and<br />

b) one or more TrajectoryReference data sets.<br />

NOTE – The potential inclusion of multiple TrajectoryReference data sets supports the cases<br />

where a single (tentative) <strong>Service</strong> Package does not correspond to a single trajectory file.<br />

CTSPD-5<br />

CTSPD-6<br />

CTSPD-7<br />

[syntactic validation]<br />

The Proposed<strong>Space</strong><strong>Link</strong><strong>Service</strong> data set shall contain one or more ProposedCarrier<br />

data sets.<br />

[syntactic validation]<br />

The Proposed<strong>Space</strong><strong>Link</strong><strong>Service</strong> data set shall contain one ProposedCarrier data set for<br />

each <strong>Space</strong><strong>Link</strong>CarrierProfile data set in the <strong>Space</strong> <strong>Link</strong> Session Profile that is referenced<br />

by the <strong>Space</strong><strong>Link</strong>SessionProfileRef parameter of the Proposed<strong>Space</strong><strong>Link</strong><strong>Service</strong> data set.<br />

[service management validation]<br />

Each ProposedCarrier data set shall contain zero or more TsMapResult data sets.<br />

[syntactic validation]<br />

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

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

Saved successfully!

Ooh no, something went wrong!