29.11.2014 Views

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

GSC Sentinel-2 PDGS OCD - Emits - ESA

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

<strong>GSC</strong> <strong>Sentinel</strong>-2 <strong>PDGS</strong> <strong>OCD</strong><br />

Issue 1 Revision 2 (draft) - 25.07.2010<br />

GMES-GSEG-EOPG-TN-09-0008<br />

page 125 of 350<br />

To account for potential conflicts with other <strong>Sentinel</strong> missions in utilising the X-Band and<br />

EDRS resources, the available downlink-budget will be further characterised by a database of<br />

constraints applicable separately to each satellite and including:<br />

○ A list of X-Band Silent Segments: a static pattern of time segments with an N-cycles<br />

repeatability during which the XBS shall not be operating due to conflicting RF<br />

simultaneous operations with other <strong>Sentinel</strong> satellites;<br />

○ A list of Station Unavailability Segments: a static pattern of time segments with an N-<br />

cycles repeatability during which downlink activities to a given ground-station are not<br />

permitted due to conflicting acquisitions by other <strong>Sentinel</strong> satellites requiring the station<br />

resources (e.g. antenna) simultaneously;<br />

○ A list of EDRS Availability Segments: a pre-defined pattern of time segments with an<br />

N-cycles repeatability during which EDRS spacecrafts are available to relay <strong>Sentinel</strong>-2<br />

data (cf. section 4.3.11).<br />

The above constraints will be defined outside of the strict scope of the <strong>Sentinel</strong>-2 <strong>PDGS</strong>.<br />

4.5.4.2.1.3 Detailed Downlink Planning<br />

This step will define the effective downlink scenario applicable to each satellite based on the<br />

associated MSI acquisition scenario and comprehensively ensuring that all operation<br />

constraints are fulfilled. It will be applied recurrently as required by the mission planning and<br />

scheduling loop with the FOS (cf. section 4.5.3.1.1).<br />

The dynamics of the downlink scenario will be constrained by:<br />

○ The static Coarse Downlink Budget as characterised in the previous step with all its<br />

embedded constraints defining ground station, OCP and XBS usability;<br />

○ The plans for station temporary unavailability provided by the ground station operators<br />

(e.g. during maintenance periods);<br />

○ The strict satellite operation constraints related to the use of the X-Band data<br />

transmission subsystem described in sections 4.3.8.4 and the ones related to the<br />

operations of the OCP as anticipated in section 4.3.8.6.<br />

In particular, the number of on-off transitions imposed on the XBS and OCP<br />

subsystems will be minimised on a repeat-cycle basis within the duty-cycle constraints<br />

of each subsystem imposed at orbit-level. This will impose when relevant the merging<br />

of non overlapping opportunities into one single transmission segment within the dutycycle<br />

constraints. In turn, it may further reduce from the coarse figure the downlink<br />

budget available at specific orbits whenever the duty-cycle does not allow full merging<br />

of the downlink opportunities.<br />

Additional TBC conflicts brought in by OCP operations with respect to MSI imaging (cf.<br />

section 4.3.8.6) or the satellite power budget, coupled with the required TBD transitory<br />

operations of the OCP itself, will further constrain the usage of EDRS/OCP contact<br />

opportunities.<br />

○ The effective zone coverage partitioning into NRT, RT and nominal data defined in the<br />

HLOP and intersecting the MSI acquisition scenario defined in section 4.5.4.1.1.<br />

<strong>ESA</strong> UNCLASSIFIED – For Official Use<br />

© <strong>ESA</strong><br />

The copyright of this document is the property of <strong>ESA</strong>. It is supplied in confidence and shall not be reproduced, copied or<br />

communicated to any third party without written permission from <strong>ESA</strong>.

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

Saved successfully!

Ooh no, something went wrong!