Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
ATPC-06
ATPC-07
ATPC-08
ATPC-09
ATPC-10
ATPC-11
ATPC-12
ATPC-13
ATPC-14
CM shall validate that each ATP-I parameter that is constrained by a Service Agreement parameter is
consistent with the applicable Service Agreement parameter.
[service management validation]
CM shall validate that all ATP-I parameter values that are related to each other (as defined in the Data
Set Composition and Relationship Requirements) contain mutually compatible values.
[service management validation]
If the SLE Complex has locally defined ATP-I relationship requirements in addition to those specified
in this standard, CM shall validate that the ATP-I conforms to all such local requirements.
[service management validation]
If the OrbitParameterMessageText data set is used in the ATP-I, then CM shall validate that the
contents of parameter opmTextData meet any data composition and relationship requirements defined
for the Orbit Parameter Message (OPM) in the CCSDS Recommended Standard for Orbit Data Messages
(ODM) (reference [14]).
[service management validation]
If the OrbitParameterMessageXml data set is used in the ATP-I, then CM shall validate that the
contents of parameter opmXmlData meet any data composition and relationship requirements defined
for the Orbit Parameter Message (OPM) in the CCSDS Recommended Standard for Orbit Data Messages
(ODM) (references [14] and [16]).
[service management validation]
If the OrbitEphemerisMessageText data set is used in the ATP-I, then CM shall validate that the
contents of parameter oemTextData meet any data composition and relationship requirements defined
for the Orbit Ephemeris Message (OEM) in the CCSDS Recommended Standard for Orbit Data
Messages (ODM) (reference [14]).
[service management validation]
If the OrbitEphemerisMessageXml data set is used in the ATP-I, then CM shall validate that the
contents of parameter oemXmlData meet any data composition and relationship requirements defined
for the Orbit Ephemeris Message (OEM) in the CCSDS Recommended Standard for Orbit Data
Messages (ODM) (references [14] and [16]).
[service management validation]
If the OrbitBilateralMessage data set is used in the ATP-I, then CM shall validate that the
OrbitBilateralMessage data set composition and relationship requirements for the format
indicated by parameter bilateralTrajectoryFormatId are met.
[service management validation]
If the ATP-I passes syntactic and service management validation, CM shall:
a) add the Trajectory Prediction to the set of Trajectory Predictions resident at CM;
b) count the Trajectory Prediction as applying against the maxSizeTrajectoryFilestore
parameter of the Service Agreement; and
c) return an ATP-SR message.
[perform operation]
6.3.4 AddTrajectoryPredictionInvocation (ATP-I) MESSAGE (UM CM)
6.3.4.1 General
The AddTrajectoryPredictionInvocation (ATP-I) 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.2. Figure 6-2 shows the ATP-I
message structure as a class diagram.
CCSDS 910.11-R-2 Page 6-5 March 2008