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

UM invokes the ADD_SPACE_LINK_SESSION_PROFILE, ADD_SLS_TRANSFER_-<br />

SERVICE_PROFILE, ADD_RETRIEVAL_TRANSFER_SERVICE_PROFILE, or<br />

ADD_SPACE_LINK_EVENTS_PROFILE operation to add a new profile to the set of<br />

Configuration Profiles on record at the SLE Complex. Each new Profile is validated by CM<br />

against the previously negotiated <strong>Service</strong> Agreement to determine if the parameter values are<br />

within the scope of the agreement. If they are, CM accepts the new profile and informs UM.<br />

If the request is invalid, CM rejects the new profile and informs UM, citing the reason(s) for<br />

rejection.<br />

UM invokes the DELETE_SPACE_LINK_SESSION_PROFILE, DELETE_-<br />

TRANSFER_SERVICE_PROFILE, or DELETE_SPACE_LINK_EVENTS_PROFILE<br />

operation to delete no-longer-needed profiles. Normally CM will comply with the<br />

invocation, delete the profile, and confirm the deletion to UM. However, under some<br />

circumstances (such as the Profile being cited by an active or forthcoming <strong>Service</strong> Package),<br />

CM will refuse to delete and will inform UM of the failure of the deletion invocation and<br />

provide the reason for failure.<br />

UM invokes the QUERY_SPACE_LINK_SESSION_PROFILE, QUERY_TRANSFER_-<br />

SERVICE_PROFILE or QUERY_SPACE_LINK_EVENTS_PROFILE operation to query<br />

the content of a specified profile on record at CM. This invocation provides a mechanism for<br />

validating consistency between UM and CM databases.<br />

The configuration parameters explicitly specified in the<br />

ADD_SPACE_LINK_SESSION_PROFILE (ASLSP) and QSLSP operations, and their<br />

allowed ranges of values, are conformant with the <strong>CCSDS</strong> standards for RF and modulation<br />

systems (reference [15]), channel coding (references [5] and [7]), telemetry framing<br />

(references [3] and [6]) and the RAF, RCF, and communications link transmission unit<br />

(CLTU) SLE transfer services (references [9], [10], and [12]). However, it is possible for<br />

space link service providers to use SLE-SM even though their services are not conformant<br />

with some or all of these <strong>CCSDS</strong> standards. The ASLSP operation supports the submission<br />

of Carrier Profiles characterizing other space link service configurations, as long as UM and<br />

CM agree on the format and content of those Carrier Profiles by means outside the scope of<br />

this standard. Similarly, the QSLSP operation allows for UM to query the contents of such<br />

bilaterally agreed Carrier Profiles.<br />

2.2.5 TRAJECTORY PREDICTION SERVICE<br />

The SLE-SM Trajectory Prediction operations are used to manage the spacecraft trajectory<br />

data that are employed by CM to derive the pointing angles and Doppler compensation<br />

settings needed to acquire the spacecraft.<br />

There are three Trajectory Prediction operations that CM can perform when invoked by UM:<br />

a) ADD_TRAJECTORY_PREDICTION (ATP)—to add a new Trajectory Prediction at<br />

CM;<br />

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

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

Saved successfully!

Ooh no, something went wrong!