GSC Sentinel-2 PDGS OCD - Emits - ESA

More documents

Recommendations

Info

GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 58 of 350 commanding, to artificially append a margin of three imaging scenes covering the discontinuity boundaries (cf. [RD-41]). 3.5.5 SCHEDULING The Sentinel-2 mission aims for a high autonomy with enhanced pre-programming, so that the nominal spacecraft operations will execute according to a sequence of commands uploaded from ground typically once every 14 days. Two schedule references are supported: - The Mission Timeline (MTL) based on a time-code referenced on the on-board clock; - The Orbit Position Schedule (OPS). To a large extent, spacecraft scheduling will require that the sensor measurements or downlink events to ground-stations precisely correspond to their on-ground related features such as the sensor overflying a specific area on earth or the satellite being effectively visible within a given ground-station mask. On the other hand, the varying nature of the spacecraft low earth orbit, as perturbed through atmospheric-drag and geo-gravitational forces, induces that spacecraft positioning cannot be predicted with the required precision in the long-term. The OPS scheduling approach precisely answers to the varying geo-positioning paradigm outlined above in that it allows commands to execute relatively to the spacecraft position within the orbit, the accurate positioning being measured autonomously on-board through the GPS embedded hardware. Hence, whilst the classical MTL-based scheduling will allow for accurate commanding of onboard operations at specific times, it is not well adapted to long-term operation schedules for which the OPS approach will generally be preferred. 3.5.6 COMMANDING AND CONTROL For commanding and control, the Sentinel-2 satellites are interfaced from ground via the S- Band channel activated by schedule during pre-defined S-Band ground-station contact periods, primarily using the TMTC and ranging ground-station at Kiruna (Sweden). During those periods, commanding can be performed (TC) and telemetry (TM) is received with an apportioned data-rate on the S-Band link of 64kbps for uplink and 128kbps or 2048kbps configurable for downlink. In particular, the TC link is used for providing schedule increments to the spacecraft (cf. 3.5.5), upload on-board software patches or configuration parameters (cf. 3.5.2.4) and overall control of the spacecraft in-orbit (e.g. manoeuvre commanding). The TM link is used for TC acknowledge, general spacecraft monitoring, downlink of on-board software configuration, and basic satellite orbit ranging and datation activities. S-Band communication with the spacecraft is made following the CCSDS Packet Utilisation Standard (PUS) services. ESA UNCLASSIFIED – For Official Use © ESA The copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied or communicated to any third party without written permission from ESA.
GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 59 of 350 3.6 Ground-Segment The Sentinel-2 Ground-Segment (GS) is composed of the FOS and the PDGS. During Phase-E1 of each satellite unit, the CNES centre in Toulouse (CNES/CST) will also be considered an integral part of the Sentinel-2 GS as providing dedicated services on-ground for commissioning the spacecrafts until the start of Phase-E2 operations. The specific role of CNES/CST during commissioning phase is detailed in section 4.2.5. The FOS is responsible for all flight operations of the Sentinel-2 spacecrafts including satellite tasking, telecommanding and telemetry monitoring, flight dynamics monitoring and orbit control. It will be operated at ESA’s European Space Operations Centre (ESOC) in Darmstadt in Germany during the entire Sentinel-2 mission. FOS responsibilities are further detailed in section 4.2.4. The PDGS is responsible for payload and downlink planning, data acquisition and processing of the Sentinel-2 satellite data, while contributing to the overall monitoring of the payload and platform in coordination with the FOS. The PDGS is a distributed ground-system including ground-stations, processing centres and embedding all additional third-party centres falling in the scope of its responsibilities for Sentinel-2 (e.g. auxiliary data providers). The GSCDA system is not considered part of the Sentinel-2 mission GS as providing multimission services within the GSC and as such is not strictly dedicated to Sentinel-2. 3.7 Mission Evolution with EDRS 3.7.1 REVIEW OF EDRS PLANNED SERVICES FOR GMES The current plan for EDRS services provisions for: ○ An initial data-relay capacity to be reached with a piggyback EDRS payload carried on-board a non dedicated satellite to be launched in 2013, ○ A second data-relay capacity, equivalent and complementing the first one, by the launch of an EDRS-dedicated spacecraft in 2015. Both missions aim for a 15 years lifetime such that a dual EDRS capacity would be available between 2015 and 2028, and a single one in the periods 2013-2015 and 2028-2030. As stated in [RD-26], the GMES Sentinels missions are intended as one of the main customers of EDRS services. Similarly to Sentinel-2, the Sentinel-1 spacecrafts will carry a OCP enabling data-relay communications from space. Sentinel-3 will not carry an OCP. The data-relay capacity will be sized to carry at least 50% of each of the Sentinel-1 and Sentinel-2 missions generated data, considering two spacecraft units operating contemporaneously for each mission. Besides data-relay capabilities provided as part of baseline services, the EDRS service envelope provisions for extended services with dual objectives: ○ Repatriation services, providing a shared capacity to be used within to the GSC Sentinels PDGSs for ground-to-ground multicast data communications, for instance to ESA UNCLASSIFIED – For Official Use © ESA The copyright of this document is the property of ESA. It is supplied in confidence and shall not be reproduced, copied or communicated to any third party without written permission from ESA.
Page 1 and 2:
document title/ titre du document P
Page 3 and 4: GSC Sentinel-2 PDGS OCD issue 1 rev
Page 27 and 28: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 33 and 34: [RD-33] Sentinel-2 MSI - Level 2A A
Page 37 and 38: LES LGS Land Equipped Sites Local G
Page 47 and 48: 3.5.2 MULTI-SPECTRAL INSTRUMENT CHA
Page 53: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 67 and 68: ESA UNCLASSIFIED - For Official Use
Page 97 and 98: Table 4-5 Radiometric image quality
Page 99 and 100: Product- Type On-Line retention Off
Page 103 and 104: 4.5.1.5 Scalability and Flexibility
Page 105 and 106:
GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
ESA UNCLASSIFIED - For Official Use
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
4.6.3 OPERATIONAL TRANSFER BASELINE
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Product- Type Identifier S2MSI0 S2M
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
○ Effective processing resources
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
o preserving integrity of exchanged
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
6 DETAILED OPERATIONS CONCEPTS GSC
Page 245 and 246:
o Report generation frequency and c
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
○ MSI L1A, L1B, L1C and TCI produ
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Some relevant use cases are present
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Two main mapping services have been
Page 327 and 328:
The requirement on the cloud covera
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
show all

GSC Sentinel-2 PDGS OCD - Emits - ESA

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?