Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
3.3.4.3.3.2.3 Data Set Composition and Relationship Requirements
Table 3-8 defines the data set composition and relationship requirements common to all SLE-
SM successful return messages.
Table 3-8: Data Set Composition and Relationship Requirements for All
SuccessfulReturn Messages
GRD-0001 A successful return message shall contain the Stereotype Message
parameters specified in table 3-7.
[syntactic validation]
GRD-0002 The invocationMessageSequenceNumber and serviceAgreementRef parameters
shall match the messageSequenceNumber and serviceAgreementRef, respectively, of
the invocation to which the return responds.
[service management validation]
GRD-0003 If there is no private annotation information, the messagePrivateAnnotation parameter
shall have null content.
3.3.4.3.3.3 FailedReturn Message Stereotypes
3.3.4.3.3.3.1 General
Failed return messages are used to inform the invoker that the operation has failed, and to
provide an explanation as to why the operation failed.
SLE operations can fail because the invocation contains one or more errors (e.g., attempting
to perform an operation that is illegal in the given context). Some, but not all, SLE-SM
operations can also fail when an otherwise-legal invocation is denied because it cannot be
met (usually for scarcity of resource reasons). Two stereotypes are defined for these cases:
the stereotype for operations that may fail only because of errors,
and the for operations that may fail because of either
errors or denial.
Class diagrams for the and
stereotype message structures are shown in figure 3-12.
CCSDS 910.11-R-2 Page 3-23 March 2008