Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
3.3.3 REQUIREMENTS
3.3.3.1 Sender Requirements for the SLE-SM Document Exchange Protocol
Table 3-1: Sender Requirements for the SLE-SM Document Exchange Protocol
MPS-0001 The Sender shall format the SLE-SM message set in accordance with the Data Set Composition
and Relationship Requirements for SLE-SM Message Sets (table 3-4) when creating an SLE-SM
message set.
MPS-0002 The Sender shall use only sleSmCreatorName (table 3-3) values for which it is authorized.
MPS-0003 The Sender shall use only sleSmCreatorName values that are authorized in the context of the
referenced Service Agreement (that is, that named by the serviceAgreementRef (table 3-3).
MPS-0004 The Sender shall send messages only for those operations that are permitted under the referenced
Service Agreement.
MPS-0005 The Sender shall increment the messageSequenceNumber values of invocation messages in
the order in which the invocations are to be processed by the Receiver, with respect to the same
sleSmCreatorName and serviceAgreementRef.
MPS-0006 The Sender shall increment the messageSequenceNumber values of return, notification, and
confirmation messages in the order in which the messages are generated, with respect to the same
sleSmCreatorName and serviceAgreementRef.
MPS-0007 The Sender shall validate that any document received on the exception response port conforms to
all syntactic validation requirements specified in table 3-25, Data Set Composition and
Relationship Requirements for SleSmExceptionResponses. If the document fails to be
syntactically validated as an SleSmExceptionResponse, the Sender shall discard the
document. The Sender is not required to further interpret or act upon the syntactically invalid
document.
[syntactic validation]
MPS-0008 For each syntactically valid InvalidMessageResponse received on the exception response
port, if the sleSmCreatorName (table 3-3) is not known to the Sender as a legitimate creator
of SLE-SM documents, the Sender shall deem the InvalidMessageResponse to be invalid.
The Sender is not required to further interpret or act upon the invalid InvalidMessageResponse.
[Authorization validation]
MPS-0009 For each syntactically valid InvalidMessageResponse received on the exception response
port, if the serviceAgreementRef (table 3-3) references a Service Agreement that is not
supported by the Sender, the Sender shall deem the InvalidMessageResponse to be invalid.
The Sender is not required to further interpret or act upon the invalid InvalidMessageResponse.
[Authorization validation]
MPS-0010 For each syntactically valid InvalidMessageResponse received on the exception response
port, if the sleSmCreatorName is not authorized in the context of the referenced Service
Agreement, the Sender shall deem the InvalidMessageResponse to be invalid. The Sender
is not required to further interpret or act upon the invalid InvalidMessageResponse.
[Authorization validation]
CCSDS 910.11-R-2 Page 3-14 March 2008