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

3.4.3.6 Requirements<br />

3.4.3.6.1 Notifier Requirements for Notified Operation Procedures<br />

Table 3-36: Notifier Requirements for the Notified Operation Procedures<br />

CNN-0001<br />

CNN-0002<br />

CNN-0003<br />

CNN-0004<br />

CNN-0005<br />

CNN-0006<br />

CNN-0007<br />

CNN-0008<br />

CNN-0009<br />

The Notifier shall format the Notification and transmit it to the Recipient’s message set port in<br />

conformance with the Sender Requirements for the SLE-SM Document Exchange Protocol (3.3.3.1).<br />

The Notifier shall set the confirmation timer to the value of the messageTimestamp of the<br />

Notification message plus the confirmationTimeout for the referenced <strong>Service</strong>Agreement.<br />

The Notifier shall validate a Confirmation received from the Recipient in accordance with the<br />

Receiver Requirements for the SLE-SM Document Exchange Protocol.<br />

The Notifier shall validate exception responses received from the Recipient on the exception response<br />

port in accordance with the Sender Requirements for the SLE-SM Document Exchange Protocol.<br />

If a received Confirmation fails any service management validation requirement specified for its<br />

notified operation type, the Confirmation shall be deemed to be service management-invalid. The<br />

Notifier is not required to further interpret or act upon the service management-invalid Confirmation.<br />

For each syntactically valid UnrecognizedMessageSetResponse received on the exception<br />

response port, the Notifier shall attempt to correlate the content of the UnrecognizedMessage-<br />

SetResponse with a Notification awaiting confirmation. If correlation is successful, the<br />

Notifier shall inform the Recipient, by bilaterally agreed means, of the operation that emitted the<br />

Notification. The Notifier is not required to further interpret or act upon any Unrecognized-<br />

MessageSetResponse that cannot be correlated.<br />

For each syntactically valid InvalidMessageResponse received on the exception response port,<br />

the Invoker shall attempt to correlate the content of the InvalidMessageResponse with a<br />

Notification awaiting confirmation. If correlation is successful, the Notifier shall inform the<br />

Recipient, by bilaterally agreed means, of the operation that emitted the Notification. The<br />

Notifier is not required to further interpret or act upon any InvalidMessageResponse that<br />

cannot be correlated.<br />

The Notifier shall confirm that the invocationMessageSequenceNumber and<br />

<strong>Service</strong>AgreementRef parameters of a Confirmation match the messageSequence-<br />

Number and <strong>Service</strong>AgreementRef, respectively, of a Notification for which the Notifier<br />

is awaiting a Confirmation, in order to associate a Confirmation with a Notification.<br />

NOTE – This is a necessary but not sufficient condition for acceptance of a Confirmation for a<br />

notification. There are additional operation-level matching criteria that must also be met, as<br />

specified under the requirements for the specific operations.<br />

If a validated Confirmation is not received for a Notification by the time the associated<br />

confirmation timer expires, the Notifier shall inform the Recipient, by bilaterally agreed means, of the<br />

operation that emitted the Notification.<br />

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

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

Saved successfully!

Ooh no, something went wrong!