Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
ATPD-05 The format of parameters opmTextData in the OrbitParameterMessageText data set and
oemTextData in the OrbitEphemerisMessageText data set shall comply with the plain text
syntax of the Orbit Parameter Message (OPM) and the Orbit Ephemeris Message (OEM), respectively,
defined in the CCSDS Recommended Standard for Orbit Data Messages (ODM) (reference [14]).
[syntactic validation]
ATPD-06 The format of parameters opmXmlData in the OrbitParameterMessageXml data set and
oemXmlData in the OrbitEphemerisMessageXml data set shall comply with the XML Schema
syntax of the Orbit Parameter Message (OPM) and the Orbit Ephemeris Message (OEM), respectively,
defined in the CCSDS XML Specification for Navigation Data Messages (reference [16]).
[syntactic validation]
ATPD-07 The Trajectory Prediction stop time shall be a time later than the Trajectory Prediction start time.
NOTE – For the OrbitBilateralMessage data set, the Trajectory Prediction start and stop times are
represented by the parameters trajectoryStartTime and trajectoryStopTime,
respectively.
[service management validation]
6.3.5 AddTrajectoryPredictionSuccessfulReturn (ATP-SR) MESSAGE
(CM UM)
6.3.5.1 General
The AddTrajectoryPredictionSuccessfulReturn (ATP-SR) message conforms
to the data set composition and relationship requirements for, and inherits the parameters of,
the stereotype, as specified in 3.3.4.3.3.2. Figure 6-3 shows
the message structure of the ATP-SR as a class diagram.
Figure 6-3: ATP-SR Message Structure, Presented in a Class Diagram
6.3.5.2 Parameters
The parameters for the ATP-SR message are described in table 6-11 and table 6-12.
CCSDS 910.11-R-2 Page 6-9 March 2008