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

5.3.3 REQUIREMENTS<br />

5.3.3.1 UM Requirements for the ADD_SPACE_LINK_SESSION_PROFILE<br />

Operation<br />

Table 5-2: UM Requirements for the ASLSP Operation<br />

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

creating and transmitting an ASLSP-I as specified in table 5-25 and table 5-27.<br />

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

in 3.4.2.6.1.<br />

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

validation requirements for CM as defined in table 5-25 and table 5-27.<br />

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

ASLSP-AR, ASLSP-SR, or ASLSP-FR syntactic validation requirements specified in<br />

table 5-29, table 5-30, or, table 5-32, 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 />

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

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

in table 5-29, table 5-30, or, table 5-32, 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 />

5.3.3.2 CM Requirements for the ADD_SPACE_LINK_SESSION_PROFILE<br />

Operation<br />

Table 5-3: CM Requirements for the ASLSP Operation<br />

ASLSPC-01 CM shall conform to all Performer Requirements for Three-Phase Operation Procedures as<br />

specified in 3.4.2.6.2.<br />

ASLSPC-02 CM shall validate that a received ASLSP-I conforms to all ASLSP-I syntactic validation<br />

requirements specified in table 5-25 and table 5-27, Data Set Composition and Relationship<br />

Requirements for the ASLSP-I. If the ASLSP-I fails any of the syntactic requirements, CM<br />

shall process the message set containing the syntactically invalid invocation in accordance with<br />

the Performer Requirements for Three-Phase Operation Procedures.<br />

ASLSPC-03 CM shall validate that the ASLSP-I conforms to all ASLSP-I service management validation<br />

requirements specified in this table and in table 5-25 and table 5-27, Data Set Composition and<br />

Relationship Requirements. If the ASLSP-I fails any of the service management requirements,<br />

CM shall cease processing the ASLSP-I and respond to UM with an ASLSP-FR message. The<br />

content of the ASLSP-FR depends on the nature of the validation failure, and is specified<br />

table 5-31.<br />

ASLSPC-04 CM shall validate that the ASLSP-I would not cause the number of Carrier Profiles to exceed<br />

maxCarrierProfiles for the referenced <strong>Service</strong> Agreement parameter.<br />

[service management validation]<br />

ASLSPC-05 CM shall validate that each ASLSP-I parameter that is constrained by a <strong>Service</strong> Agreement<br />

parameter is consistent with the applicable <strong>Service</strong> Agreement parameter.<br />

[service management validation]<br />

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

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

Saved successfully!

Ooh no, something went wrong!