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

ASLSPD-29 In each RafTsM data set, the value of the transfer<strong>Service</strong>ProfileRef attribute shall<br />

match the value of the transfer<strong>Service</strong>ProfileId of a previously-defined SLS Transfer<br />

<strong>Service</strong> Profile that defines an RAF SLS transfer service profile.<br />

[service management validation]<br />

ASLSPD-30 In each RcfTsM data set, the value of the transfer<strong>Service</strong>ProfileRef attribute shall<br />

match the value of the transfer<strong>Service</strong>ProfileId of a previously-defined SLS Transfer<br />

<strong>Service</strong> Profile that defines an RCF SLS transfer service.<br />

[service management validation]<br />

ASLSPD-31 In each BilateralTsM data set contained by an RafProd data set, the value of the<br />

transfer<strong>Service</strong>ProfileRef attribute shall match the value of the<br />

transfer<strong>Service</strong>ProfileId of a previously-defined SLS Transfer <strong>Service</strong> Profile that<br />

defines a bilateral SLS transfer service profile that is appropriate for use with a return carrier.<br />

[service management validation]<br />

NOTE – The means by which the appropriateness is determined is itself defined bilaterally and<br />

is outside the scope of this Recommended Standard.<br />

ASLSPD-32 In each CcsdsDataSink data set and BilateralDataSink, the value of the<br />

dataSinkId shall be unique within the context of the <strong>Space</strong> <strong>Link</strong> Session Profile.<br />

[service management validation]<br />

ASLSPD-33<br />

a) A BilateralCarrierProfile data set shall contain at least one of the following:<br />

1) FcltuTsM data set;<br />

2) RafTsM data set;<br />

3) RcfTsM data set;<br />

4) BilateralTsM data set;<br />

5) DataSink data set; and/or<br />

6) BilateralDataSink data set.<br />

b) A BilateralCarrierProfile data set may contain more than one of any of the<br />

above-specified data sets.<br />

[syntactic validation]<br />

ASLSPD-34 Each BilateralCarrierProfile data set shall contain transfer service mapping (TsM)<br />

and Data Sink data sets that are appropriate for that BilateralCarrierProfile data set.<br />

[service management validation]<br />

NOTE – The means by which the appropriateness is determined is itself defined bilaterally and<br />

is outside the scope of this Recommended Standard.<br />

ASLSPD-35 A RafProd data set shall contain one of the following combinations of data sets:<br />

a) one FecfOnly data set;<br />

b) one ReedSolomonCoding data set;<br />

c) one TurboCoding data set; or<br />

d) one ReedSolomonCoding data set and one TurboCoding data set.<br />

All other combinations of FecfOnly data set, ReedSolomonCoding data set, and<br />

TurboCoding data set (including none) are invalid.<br />

[syntactic validation]<br />

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

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

Saved successfully!

Ooh no, something went wrong!