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

SLE-SM<br />

Operation<br />

Procedure<br />

W<br />

(2 Phase)<br />

two-phase operation<br />

procedure pattern<br />

SLE-SM<br />

Operation<br />

Procedure<br />

X<br />

(3 Phase)<br />

SLE-SM<br />

Operation<br />

Procedure<br />

Y<br />

(3 Phase)<br />

three-phase operation<br />

procedure pattern<br />

SLE-SM<br />

Operation<br />

Procedure<br />

Z<br />

(Notified)<br />

notified operation<br />

procedure pattern<br />

invocations<br />

and returns<br />

notifications<br />

and confirmations<br />

SLE-SM document exchange protocol<br />

SLE-SM<br />

message sets<br />

authenticated, recognized<br />

source identification<br />

SLE-SM exception<br />

responses<br />

underlying communication service<br />

Figure 3-1: Relationship among SLE-SM Operation Procedures, Document<br />

Exchange Protocol, and Underlying Communication <strong>Service</strong><br />

3.2 UNDERLYING COMMUNICATION SERVICE<br />

The underlying communication service is used to exchange SLE-SM documents among SLE-<br />

SM application entities. The underlying communication service maintains the relationship<br />

among each SLE-SM application entity and the identification of the ports through which it<br />

communicates with other SLE-SM application entities. The underlying communication<br />

service establishes and maintains the communication association between each pair of<br />

communication entities.<br />

NOTE – The underlying communication service may be built upon connectionless<br />

protocols such as UDP or SMTP, but if so then the underlying communication<br />

service must include a ‘sublayer’ that maintains the association. Alternatively, if<br />

no such automated association maintenance capability is provided by the<br />

underlying communication service itself, the communications association has to<br />

be established, maintained, and terminated by manually executed procedures.<br />

At a minimum, the underlying communication service must authenticate the Source of each<br />

document carried by the service and validate that the Source is recognized by the Destination<br />

as an entity that is permitted to send documents to it. As used in this Recommended<br />

Standard, Source and Destination refer to the communicating entities as they are known to<br />

the underlying communication service. Documents for which the Source cannot be<br />

authenticated and recognized are dropped by the communication service. There is no<br />

requirement on the underlying communication service to notify the Source when a document<br />

is dropped because of failure to authenticate the Source or recognize it on behalf of the<br />

intended Destination. Only when the underlying communication service authenticates the<br />

Source and recognizes it as a legitimate Source for the intended Destination does it deliver<br />

the document to the Destination.<br />

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

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

Saved successfully!

Ooh no, something went wrong!