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

Table 6-9: OrbitBilateralMessage Data Set<br />

Name Definition/Description Data Type Units<br />

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

Agreement Parameter<br />

bilateralTraje Contains the Trajectory Prediction data in the Opaque n/a n/a<br />

ctoryData format defined by the parameter<br />

bilateralTrajectoryFormatId.<br />

bilateralTraje<br />

ctoryFormatId<br />

trajectoryStar<br />

tTime<br />

trajectoryStop<br />

Time<br />

Identification of trajectory data format other than<br />

the two <strong>CCSDS</strong> standard formats OPM and<br />

OEM. This format has to be bi-laterally agreed<br />

between UM and CM.<br />

Date and time from which the Trajectory<br />

Prediction is valid.<br />

Date and time at which the Trajectory Prediction<br />

is no longer valid.<br />

String256 n/a TrajectoryPredic<br />

tionOperationsCo<br />

nstraints:allowe<br />

dBilateralTrajec<br />

toryFormatIds<br />

UTC n/a n/a<br />

UTC n/a n/a<br />

6.3.4.3 Data Set Composition and Relationship Requirements<br />

Table 6-10 defines the data set composition and relationship requirements for the ATP-I<br />

message.<br />

Table 6-10: Data Set Composition and Relationship Requirements for ATP-I<br />

ATPD-01 The ATP-I shall contain one TrajectoryPredictionIdentification data set.<br />

[syntactic validation]<br />

ATPD-02 The ATP-I allows the selection of one Trajectory Prediction data format, hence it shall contain only one<br />

of the following data sets:<br />

a) OrbitParameterMessageText;<br />

b) OrbitParameterMessageXml;<br />

c) OrbitEphemerisMessageText;<br />

d) OrbitEphemerisMessageXml;<br />

e) OrbitBilateralMessage.<br />

[syntactic validation]<br />

ATPD-03 The parameter trajectoryFormatOptions in the <strong>Service</strong>Agreement data set (table 7-12)<br />

restricts the Trajectory Prediction format choices. This means that the ATP-I can contain:<br />

a) an OrbitParameterMessageText data set only if the trajectoryFormatOptions<br />

parameter set includes the enumeration value ‘opmText’;<br />

b) an OrbitParameterMessageXml data set only if the trajectoryFormatOptions<br />

parameter set includes the enumeration value ‘opmXml’;<br />

c) an OrbitEphemerisMessageText data set only if the trajectoryFormatOptions<br />

parameter set includes the enumeration value ‘oemText’;<br />

d) an OrbitEphemerisMessageXml data set only if the trajectoryFormatOptions<br />

parameter set includes the enumeration value ‘oemXml’;<br />

e) an OrbitBilateralMessage data set only if the trajectoryFormatOptions parameter<br />

set includes the enumeration value ‘obm’.<br />

[service management validation]<br />

ATPD-04 The trajectoryId parameter shall be unique in the context of the referenced <strong>Service</strong> Agreement.<br />

[service management validation]<br />

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

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

Saved successfully!

Ooh no, something went wrong!