Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
3.3.4.2.3 Data Set Composition and Relationship Requirements
Table 3-4 defines the data set composition and relationship requirements for the
SleSmMessageSet messages.
Table 3-4: Data Set Composition and Relationship Requirements for
SleSmMessageSet Documents
MSD-0001 An SleSmMessageSet document shall contain an unambiguous sleSmVersionRef
parameter.
[syntactic validation]
MSD-0002 The sleSmVersionRef parameter shall have the value of ‘1.0.0’.
[syntactic validation]
MSD-0003 An SleSmMessageSet document shall contain the sleSmCreatorName and
serviceAgreementRef parameters defined in table 3-3.
[syntactic validation]
MSD-0004 An SleSmMessageSet document shall contain exclusively:
a) one or more Invocation messages;
b) one Return message;
c) one Notification message; or
d) one Confirmation message.
[syntactic validation]
MSD-0005 Each Invocation message contained in an SleSmMessageSet document shall
conform to the data set composition and relationship requirements for that message type, as
specified in 3.3.4.3.2.
[syntactic validation]
MSD-0006 The Return message contained in an SleSmMessageSet document shall conform to the
data set composition and relationship requirements for that message type, as specified in
3.3.4.3.3.
[syntactic validation]
MSD-0007 The Notification message contained in an SleSmMessageSet document shall
conform to the data set composition and relationship requirements for that message type, as
specified in 3.3.4.3.4.
[syntactic validation]
MSD-0008 The Confirmation message contained in an SleSmMessageSet document shall
conform to the data set composition and relationship requirements for that message type, as
specified in 3.3.4.3.5.
[syntactic validation]
3.3.4.3 SLE-SM Message Set Messages
3.3.4.3.1 General
There are four generic SLE-SM message types: invocation, return, notification, and
confirmation. Concrete versions of these generic message types are defined for the SLE-SM
operations defined for the specific operations in sections 4 through 7, as appropriate.
However, to the extent that each of these generic types can be categorized in terms of use,
behavior, and parameters, the common characteristics are defined later in this section.
CCSDS 910.11-R-2 Page 3-18 March 2008