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

5.3.4.3 Data Set Composition and Relationship Requirements<br />

Table 5-25 defines the data set composition and relationship requirements for the<br />

data set stereotype.<br />

Table 5-25: Data Set Composition and Relationship Requirements for the<br />

Data Set Stereotype<br />

ASLSPD-01 A data set conforming to the stereotype shall contain<br />

one or more <strong>Space</strong><strong>Link</strong>CarrierProfile data sets.<br />

[syntactic validation]<br />

ASLSPD-02 Each <strong>Space</strong><strong>Link</strong>CarrierProfile data set shall contain one and only one of the following:<br />

a) F401<strong>Space</strong><strong>Link</strong>CarrierProfile data set;<br />

b) R401<strong>Space</strong><strong>Link</strong>CarrierProfile data set;<br />

c) BilateralCarrierProfile data set.<br />

[syntactic validation]<br />

ASLSPD-03 The carrierProfileId parameter for each <strong>Space</strong> <strong>Link</strong> Carrier Profile shall be unique<br />

relative to the <strong>Service</strong> Agreement.<br />

[service management validation]<br />

ASLSPD-04 If the BilateralCarrierProfile data set is present, the content of the<br />

bilateralCarrierProfileData parameter shall conform to the data set composition and<br />

relationship requirements for the format of the Bilateral Carrier Profile indicated by parameter<br />

bilateralCarrierProfileFormatId.<br />

[service management validation]<br />

ASLSPD-05 For each BilateralTsM data set present, the content of the bilateralTsMData parameter<br />

shall conform to the data set composition and relationship requirements for the format indicated<br />

by parameter bilateralTransfer<strong>Service</strong>ProfileFormatId of the SLS Transfer<br />

<strong>Service</strong> Profile referenced by the transfer<strong>Service</strong>ProfileId parameter.<br />

[service management validation]<br />

ASLSPD-06 For each BilateralDataSink data set present, the content of the<br />

bilateralDataSinkData parameter shall conform to the data set composition and<br />

relationship requirements for the format indicated by dataSinkId parameter.<br />

[service management validation]<br />

ASLSPD-07 In each F401<strong>Space</strong><strong>Link</strong>CarrierProfile data set, the<br />

f401<strong>Space</strong><strong>Link</strong>CarrierAgreementRef parameter shall contain the value of an<br />

f401<strong>Space</strong><strong>Link</strong>CarrierAgreementId in the associated <strong>Service</strong> Agreement.<br />

[service management validation]<br />

ASLSPD-08 A F401<strong>Space</strong><strong>Link</strong>CarrierProfile data set shall contain zero or one<br />

F401Subcarrier data set.<br />

[syntactic validation]<br />

ASLSPD-09 A F401<strong>Space</strong><strong>Link</strong>CarrierProfile data set shall contain<br />

a) one F401SymbolStream data set; and<br />

b) zero or more FrequencySweepLeg data sets.<br />

[syntactic validation]<br />

ASLSPD-10 A F401SymbolStream data set shall contain one and only one of the following:<br />

a) FcltuTsM data set; or<br />

b) BilateralTsM data set.<br />

[syntactic validation]<br />

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

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

Saved successfully!

Ooh no, something went wrong!