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

Content of<br />

additional-<br />

Information<br />

diagnostic<br />

value Definition/Description Rqmt<br />

‘nonconformant<br />

1) the contents of the parameter ATPC-09<br />

If one of the following occurs:<br />

to data set opmTextData in the<br />

composition OrbitParameterand<br />

MessageText data set do<br />

relationship<br />

requirements<br />

not meet the OPM data set<br />

of indicated<br />

composition and relationship<br />

format’<br />

requirements;<br />

ATPC-10<br />

2) the contents of the parameter<br />

opmXmlData in the<br />

OrbitParameter-<br />

MessageXml data set do not<br />

meet the OPM data set<br />

composition and relationship ATPC-11<br />

requirements;<br />

3) the contents of the parameter<br />

oemTextData in the<br />

OrbitEphemerisMessag<br />

eText data set do not meet<br />

the OEM data set composition ATPC-12<br />

and relationship requirements;<br />

4) the contents of the parameter<br />

oemXmlData in the<br />

OrbitEphemerisMessag<br />

eXml data set do not meet the<br />

OEM data set composition ATPC-13<br />

and relationship requirements;<br />

5) the contents of the parameter<br />

bilateralTrajectoryD<br />

ata in the Orbit-<br />

BilateralMessage data<br />

set do not meet the relevant<br />

data set composition and<br />

‘operation<br />

timeout’<br />

‘parameter<br />

value not<br />

supported by<br />

referenced<br />

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

Agreement’<br />

‘trajectoryId<br />

already in<br />

use’<br />

‘other’<br />

relationship requirements.<br />

When the operation cannot be<br />

completed before the disposition<br />

timer expires.<br />

The value of the identified parameter<br />

is not within the values permitted by<br />

the referenced <strong>Service</strong> Agreement.<br />

There is a Trajectory Prediction with<br />

this identifier already registered at<br />

CM for the referenced <strong>Service</strong><br />

Agreement.<br />

An error condition that is private to<br />

the CM has occurred.<br />

2PP-0103<br />

in<br />

table 3-29<br />

ATPC-06<br />

ATPD-03<br />

Parameter or Data<br />

Set Identified by<br />

erroredItem<br />

For cases 2) and 4)<br />

listed on the left,<br />

which adopt the XML<br />

format,<br />

erroredItem will<br />

contain the value of<br />

the non-conformant<br />

parameter (the one<br />

that failed validation).<br />

For cases 1) and 3)<br />

listed on the left,<br />

which adopt the plain<br />

text format,<br />

erroredItem is not<br />

applicable. Any<br />

further information<br />

about nonconformance<br />

will be<br />

conveyed via the<br />

contents of<br />

additionalInfor<br />

mation.<br />

not applicable<br />

identification of the<br />

parameter in violation<br />

For cases 1) and 3)<br />

listed on the left,<br />

additionalInform<br />

ation shall specify<br />

the non-conformant<br />

field(s) that caused<br />

ATP-I to fail<br />

validation.<br />

not required<br />

not required<br />

ATPD-04 trajectoryId not required<br />

ATPC-08<br />

identification of the<br />

parameter in violation<br />

CM-internal reason for<br />

invalidation<br />

<strong>CCSDS</strong> 910.11-R-2 Page 6-12 March 2008

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

Saved successfully!

Ooh no, something went wrong!