Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
3.3.3.2 Receiver Requirements for the SLE-SM Document Exchange Protocol
Table 3-2: Receiver Requirements for the SLE-SM Document Exchange Protocol
MPR-0001 The Receiver shall validate that any document received on the message set port conforms to all
SleSmMessageSet syntactic validation requirements specified in table 3-4, Data Set
Composition and Relationship Requirements for SleSmMessageSet Documents). If the
document fails any of the syntactic requirements, the Receiver shall deem the document to be
invalid, discard the document, and send an UnrecognizedMessageSetResponse to the
exception response port of the Sender. The Receiver is not required to further interpret or act
upon the invalid document.
[syntactic validation]
MPR-0002 If the sleSmCreatorName (table 3-3) is not known to the Receiver as a legitimate creator of
SLE-SM message sets, the Receiver shall deem the message set to be invalid, discard the message
set, and send an UnrecognizedMessageSetResponse to the exception response port of the
Sender. The Receiver is not required to further interpret or act upon the invalid message set.
[Authorization validation]
MPR-0003 If the serviceAgreementRef (table 3-3) references a Service Agreement that is not
supported by the Receiver, the Receiver shall deem the message set to be invalid, discard the
message set, and send an UnrecognizedMessageSetResponse to the exception response
port of the Sender. The Receiver is not required to further interpret or act upon the invalid
message set.
[Authorization validation]
MPR-0004 If the sleSmCreatorName is not authorized in the context of the referenced Service
Agreement, the Receiver shall deem the message set to be invalid, discard the message set, and
send an UnrecognizedMessageSetResponse to the exception response port of the Sender.
The Receiver is not required to further interpret or act upon the invalid message set.
[Authorization validation]
MPR-0005 If the communication-service-provided Source identification associated with the Message Set is
not authorized to send Message Sets using the sleSmCreatorName in the context of the
referenced Service Agreement, the Receiver shall deem the message set to be invalid, discard the
message set, and send an UnrecognizedMessageSetResponse to the exception response
port of the Sender. The Receiver is not required to further interpret or act upon the invalid
message set.
[Authorization validation]
MPR-0006 If the messageSequenceNumber (table 3-5) of any invocation message in a message set is not
greater than the messageSequenceNumber of all valid invocation messages received in
previous message sets with that sleSmCreatorName and serviceAgreementRef, the
Receiver shall deem each such message invalid and shall send an InvalidMessageResponse
to the exception response port of the Sender. The Receiver is not required to further interpret or
act upon the invalid invocation message, and the messageSequenceNumber of the invalid
invocation message shall not be used to determine sequence integrity of subsequent invocation
messages.
[Sequence validation]
MPR-0007 If the messageSequenceNumbers of two or more invocation messages in a message set are
the same, the Receiver shall deem the same-numbered messages that appear after the first such
instance to be invalid, and for each such invalid message shall send an
InvalidMessageResponse (3.3.4.4) to the exception response port of the Sender. The
Receiver is not required to further interpret or act upon the invalid invocation message.
[Sequence validation]
CCSDS 910.11-R-2 Page 3-15 March 2008