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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT<br />

NOTE – The Sender process that generates the message set is external to (that is, not a<br />

part of) the SLE-SM document exchange protocol.<br />

Each message in a message set is given a messageSequenceNumber. For invocation<br />

messages, the messageSequenceNumber indicates the order in which the messages are<br />

to be processed by the Receiver. A Sender application process that requires invocation<br />

messages to be processed by the Receiver in a certain sequence must order the message-<br />

SequenceNumbers of the message in the desired order. For other message types (returns,<br />

notifications, and confirmations), the messageSequenceNumber indicates the order in<br />

which the messages are created.<br />

Message sets containing multiple messages may only be created for the transmission of<br />

invocation messages. The other message types (returns, notifications, and confirmations)<br />

shall be sent individually in separate message sets.<br />

3.3.2.3 Receiver Receives and Validates SLE-SM Message Set<br />

Upon receipt of a document via the Receiver’s SLE-SM message set port, the Receiver shall<br />

perform message set validation. Message set validation consists of several validation steps<br />

(syntactic, authorization, sequencing of invocation messages within the message set, and<br />

verification of support for the invoked operation), some of which are performed only when<br />

certain message types are contained in the message set. These validation steps are described<br />

in subsequent paragraphs.<br />

Syntactic validation. The Receiver shall perform syntactic validation of the document to<br />

ensure that the document is a properly formatted SLE-SM message set of a version that is<br />

supported by the Receiver. If the Receiver cannot syntactically validate the message set, the<br />

Receiver shall generate and send an UnrecognizedMessageSetResponse exception<br />

response to the exception response port of the Sender, after which the Receiver has no further<br />

obligation for interpreting and acting upon the document.<br />

Authorization validation. Once the received document has been validated as a syntactically<br />

correct message set, the Receiver shall perform authorization validation of the message set to<br />

ensure (a) that the communication service-provided identifier of the Source of the message<br />

set is authorized to use the sleSmCreatorName (see table 3-3) contained in the message<br />

set, (b) that the <strong>Service</strong> Agreement identified by the serviceAgreementRef (table 3-3)<br />

in the message set is supported by the Receiver, and (c) that the sleSmCreatorName in<br />

the message set is authorized to send messages in the context of the <strong>Service</strong> Agreement<br />

identified by the serviceAgreementRef in the message set. If the Receiver is unable to<br />

validate the authorization of the Sender of the message set, the Receiver shall send an<br />

UnrecognizedMessageSetResponse exception response with appropriate diagnostic<br />

information (as specified in table 3-23) to the exception response port of the Sender, after<br />

which the Receiver has no further obligation for interpreting and acting upon the message<br />

set.<br />

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

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

Saved successfully!

Ooh no, something went wrong!