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 />

supported-operation validation to the appropriate operation applications, as defined in the<br />

procedure patterns in 3.4 and the specific operations defined in sections 4 through 7 of this<br />

Recommended Standard.<br />

3.3.2.4 Sender Receives and Validates SLE-SM Exception Responses<br />

3.3.2.4.1 General<br />

If the Sender sent a message set that was unrecognizable to the Receiver or that contained<br />

messages that were invalid to the Receiver, the Sender receives one or more exception<br />

responses (UnrecognizedMessageSetResponse or InvalidMessageResponse)<br />

from the Receiver via the Sender’s exception response port.<br />

NOTE – ‘Sender’ herein refers to the transmitter of the original message set, and not to the<br />

transmitter of the exception response(s) (which is the Receiver).<br />

3.3.2.4.2 Exception Response Validation<br />

Upon receipt of a document at the Sender’s exception response port, the Sender shall perform<br />

syntactic validation and InvalidMessageResponse authorization validation (as<br />

appropriate). These validation steps are described in subsequent paragraphs.<br />

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

ensure that the document is a properly formatted exception response, either an<br />

UnrecognizedMessageSetResponse or an InvalidMessageResponse. If the<br />

Sender cannot syntactically validate the SLE-SM document, the Sender shall terminate<br />

processing of the document and has no further obligation for interpreting and acting upon the<br />

document. However, the Sender may perform locally defined troubleshooting activities.<br />

Authorization validation. If the syntactically valid SLE-SM document contains an<br />

InvalidMessageResponse, the Sender shall perform authorization validation of the<br />

message to ensure (a) that the Receiver is authorized to use the sleSmCreatorName (see<br />

table 3-3) in the InvalidMessageResponse that contains the message, (b) that the<br />

<strong>Service</strong> Agreement identified by the serviceAgreementRef (table 3-3) in the<br />

InvalidMessageResponse is supported by the Sender, and (c) that the Receiver is<br />

authorized to send messages in the context of the <strong>Service</strong> Agreement identified by the<br />

serviceAgreementRef in the InvalidMessageResponse. If the Sender is unable<br />

to validate the authorization of the Receiver, the Sender terminates processing of the<br />

InvalidMessageResponse, after which the Sender has no further obligation for<br />

interpreting and acting upon the message. However, the Sender may perform locally defined<br />

troubleshooting activities such as contacting the source of the unauthorized Invalid-<br />

MessageResponse.<br />

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

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

Saved successfully!

Ooh no, something went wrong!