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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

The ASLEP operation involves the exchange of ADD_SPACE_LINK_EVENTS_PROFILE<br />

messages. The ASLEP messages are: Add<strong>Space</strong><strong>Link</strong>EventsProfileInvocation<br />

(ASLEP-I), Add<strong>Space</strong><strong>Link</strong>EventsProfileAcknowledgedReturn (ASLEP-AR),<br />

Add<strong>Space</strong><strong>Link</strong>EventsProfileSuccessfulReturn (ASLEP-SR), and<br />

Add<strong>Space</strong><strong>Link</strong>EventsProfileFailedReturn (ASLEP-FR).<br />

The message sequence diagram for the ADD_SPACE_LINK_EVENTS_PROFILE operation<br />

conforms to the stereotyped sequence diagram for the three-phase operation procedure<br />

pattern defined in 3.4.2.3, with the following argument list:<br />

threePhaseOperationProcedurePatternSequence {UM, CM, ASLEP-I,<br />

ASLEP-AR, ASLEP-SR,<br />

ASLEP-FR}<br />

The activity diagram for the ADD_SPACE_LINK_EVENTS_PROFILE operation conforms<br />

to the stereotyped activity diagram for the three-phase operation procedure pattern defined in<br />

3.4.2.4, with the following argument list:<br />

threePhaseOperationProcedurePatternActivity {UM, CM, ASLEP-I,<br />

ASLEP-SR, ASLEP-SR,<br />

ASLEP-FR,<br />

aepRoutineTimeout,<br />

aepUrgentTimeout}<br />

5.6.3 REQUIREMENTS<br />

5.6.3.1 UM Requirements for the ADD_SPACE_LINK_EVENTS_PROFILE Operation<br />

Table 5-45: UM Requirements for the ASLEP Operation<br />

ASLEPU-1<br />

ASLEPU-2<br />

ASLEPU-3<br />

ASLEPU-4<br />

ASLEPU-5<br />

UM shall conform to all ASLEP-I Data Set Composition and Relationship Requirements when<br />

creating and transmitting an ASLEP-I as specified in table 5-54 and table 5-57.<br />

UM shall conform to all Invoker Requirements for Three-Phase Operation Procedures as specified<br />

in 3.4.2.6.1.<br />

UM should send ASLEP-I messages that are valid with respect to all service management<br />

validation requirements for CM as defined in table 5-54.<br />

UM shall validate that a received ASLEP-AR, ASLEP-SR or ASLEP-FR conforms to all<br />

ASLEP-AR, ASLEP-SR or ASLEP-FR syntactic validation requirements specified in table 5-59,<br />

table 5-60, or table 5-62, respectively. If the return fails any of the syntactic validation<br />

requirements, UM shall process the message set containing the syntactically invalid return in<br />

accordance with the Invoker Requirements for Three-Phase Operation Procedures.<br />

UM shall validate that a received ASLEP-AR, ASLEP-SR or ASLEP-FR conforms to all<br />

ASLEP-AR, ASLEP-SR or ASLEP-FR service management validation requirements specified<br />

in table 5-59, table 5-60, or table 5-62, respectively. If the return fails any of the service<br />

management validation requirements, UM shall process the service management-invalid return in<br />

accordance with the Invoker Requirements for Three-Phase Operation Procedures.<br />

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

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

Saved successfully!

Ooh no, something went wrong!