Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
CSPC-24
For each Space Link Service Request in a valid CSP-I for which handovers are permitted, CM may
schedule the resources to create multiple Space Link Service Results in accordance with the referenced
profiles, such that:
a) the set of scheduled resources associated with any one antenna constitutes a conformant resource
configuration as defined in CSPC-16 b) and is scheduled as a separate Space Link Service Result;
b) if one or more preferred antennas are specified in the Space Link Service Request and at least one
conformant resource configuration exists that uses one of the preferred antennas, use of the
conformant resource configurations that use preferred antennas is maximized;
c) the scheduledSpaceLinkSessionStartTime of the first scheduled Space Link Service
Result is greater than or equal to (spaceLinkSessionStartTime – spaceLinkSession-
StartTimeLead) and less than or equal to (spaceLinkSessionStartTime +
spaceLinkSessionStartTimeLag) of the Space Link Service Request;
d) the scheduledSpaceLinkSessionStartTime of each intermediate scheduled Space Link
Service Result and of the last scheduled Space Link Service Result overlaps the
scheduledSpaceLinkSessionStopTime of the scheduled Space Link Service Result that
immediately precedes it by at least the handoverOverlap specified in the Service Agreement;
e) the scheduledSpaceLinkSessionStopTime of the last scheduled Space Link Service
Result is greater than or equal to (scheduledSpaceLinkSessionStartTime +
minimumSessionDuration) and less than or equal to (scheduledSpaceLinkSession-
StartTime + preferredSessionDuration) of the Space Link Service Request;
f) each Space Link Service Result schedules each carrier specified by the Space Link Service Request
to the extent that the time span of the Space Link Service Result coincides with the total scheduled
duration of the carrier, where:
1) the time span of the Space Link Service Result is bounded by the scheduledSpace-
LinkSessionStartTime and scheduledSpaceLinkSessionStopTime of the
Space Link Service Result; and
2) the total scheduled duration of the carrier begins at the scheduledSpaceLinkSession-
StartTime of the first Space Link Service Result plus the carrierStartTimeOffset
specified for that carrier in the referenced Space Link Carrier Profile, and ends at the
scheduledSpaceLinkSessionStopTime of the last Space Link Service Result plus the
carrierStopTimeOffset specified for that carrier in the referenced Space Link Carrier
Profile;
g) the difference between the values of the scheduledServicePackageStartTime and the
scheduledServicePackageStopTime shall be less than
maxServicePackageTemporalSpan;
h) for each ServiceScenarioResult data set, the difference between the values of the earliest
scheduledSpaceLinkSessionStartTime and the
scheduledSpaceLinkSessionStopTime, for all SpaceLinkServiceResult data sets
contained by that ServiceScenarioResult data set, shall be less than
maxServiceScenarioTemporalSpan;
i) if a SpaceLinkEventsProfile is referenced for any return carrier(s) having a Return-
CoherenceModel or ReturnOffsetModel data set, the communicationMode parameter
of the referenced SpaceLinkEventsProfile shall be consistent with the handover times;
j) if a SpaceLinkEventsProfile is referenced, the [F|R]SpaceLinkAvailable-
ScheduledState data sets shall contain only those [F|R]SpaceLinkAvailableStates
that coincide with the scheduledCarrierStartTime and scheduledCarrierStop-
Time for each handover, where coincidence is defined to include those [F|R]SpaceLink-
AvailableStates that are partially within the handover service instance that may begin earlier
than the scheduledCarrierStartTime or extend later than the
scheduledCarrierStartTime of the handover service instance.
NOTE – Handover situations have the potential for inducing communication mode changes from 2-way
to 3-way, etc., affecting return carriers that are generated in reference to a forward carrier.
[perform operation]
CCSDS 910.11-R-2 Page 4-12 March 2008