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

6.5.3 REQUIREMENTS<br />

6.5.3.1 UM Requirements for the QUERY_TRAJECTORY_PREDICTION Operation<br />

Table 6-22: UM Requirements for the QTP Operation<br />

QTPU-01 UM shall conform to all Invoker Requirements for Two-Phase Operation Procedures as specified in 3.4.1.6.1.<br />

QTPU-02 UM shall conform to all QTP-I Data Set Composition and Relationship Requirements when creating<br />

and transmitting a QTP-I as specified in table 6-24.<br />

QCPU-03 UM should send QTP-I messages that are valid with respect to all service management validation<br />

requirements for CM as defined in table 6-23.<br />

QTPU-04 UM shall validate that a received QTP-SR or QTP-FR conforms to all QTP-SR or QTP-FR syntactic<br />

validation requirements specified in table 6-26 and table 6-28, respectively. If the return fails any of the<br />

syntactic validation requirements, UM shall process the message set containing the syntactically invalid<br />

return in accordance with the Invoker Requirements for Two-Phase Operation Procedures.<br />

QTPU-05 UM shall validate that a received QTP-SR or QTP-FR conforms to all QTP-SR or QTP-FR service<br />

management validation requirements specified in table 6-26 and table 6-28, respectively. If the return<br />

fails any of the service management validation requirements, UM shall process the service management<br />

invalid return in accordance with the Invoker Requirements for Two-Phase Operation Procedures.<br />

QTPU-06 If the OrbitBilateralMessage data set is used in the QTP-SR, then UM shall validate that the<br />

OrbitBilateralMessage data set composition and relationship requirements for the format<br />

indicated by parameter bilateralTrajectoryFormatId are met.<br />

[service management validation]<br />

6.5.3.2 CM Requirements for the QUERY_TRAJECTORY_PREDICTION Operation<br />

Table 6-23: CM Requirements for the QTP Operation<br />

QTPC-01 CM shall conform to all Performer Requirements for Two-Phase Operation Procedures as specified in 3.4.2.6.2.<br />

QTPC-02 CM shall conform to all QTP-SR and QTP-FR Data Set Composition and Relationship Requirements<br />

when creating and transmitting a QTP-SR and QTP-FR, as specified in table 6-26 and table 6-28,<br />

respectively.<br />

QTPC-03 CM shall validate that a received QTP-I conforms to all QTP-I syntactic validation requirements<br />

specified in table 6-24, Data Set Composition and Relationship Requirements for the QTP-I. If the<br />

QTP-I fails any of the syntactic requirements, CM shall process the message set containing the<br />

syntactically invalid invocation in accordance with the Performer Requirements for Two-Phase<br />

Operation Procedures.<br />

QTPC-04 CM shall validate that the QTP-I conforms to all QTP-I service management validation requirements<br />

specified in this table and table 6-24, Data Set Composition and Relationship Requirements for the QTP-<br />

I. If the QTP-I fails any of the service management requirements, CM shall cease processing the QTP-<br />

I and respond to UM with an QTP-FR message. The content of the QTP-FR depends on the nature of<br />

the validation failure, and is specified in table 6-27.<br />

QTPC-05 If the SLE Complex has locally defined QTP-I relationship requirements in addition to those specified<br />

in this standard, CM shall validate that the QTP-I conforms to all such local requirements.<br />

[service management validation]<br />

QTPC-06 If the QTP-I is valid, CM shall create a copy of the requested Trajectory Prediction and return it in a QTP-SR.<br />

[perform operation]<br />

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

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

Saved successfully!

Ooh no, something went wrong!