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 64 of 350 4 PDGS OPERATION BASELINE 4.1 Assumptions High-level assumptions taken and having an impact on the settled PDGS operation baseline are enumerated hereafter. [Assumption-01] The Sentinel-2B satellite will be identical to Sentinel-2A satellite. [Assumption-02] Seven (7) years of active mission operations plus a possible 5 years extension are considered for each Sentinel-2 satellite. [Assumption-03] Sentinel-2B will be launched 18-30 months after Sentinel-2A. 18 months is the planned value [TBC] at Sentinel-2 GS PDR. [Assumption-04] 5.5 to 10.5 years of parallel Sentinel-2A and Sentinel-2B active mission operations (nominal or extended mission duration) plus 18 months Sentinel-2B active mission operations are envisaged. [Assumption-05] Twenty-Five (25) years of mission operations from archive are considered. [Assumption-06] The X/Ka-band ground stations network will be selected at a later stage. A minimum four X-band receiving PDGS Core Ground Stations baseline scenario is assumed in this document. This configuration is sufficient to downlink the Sentinel-2 data as per baseline scenario such as the one defined in [RD-01]. The selection of more stations will substantially enhance the performance of the baseline scenario but is not strictly required for baseline operations. [Assumption-07] All data handled by the Sentinel-2 PDGS is assumed to be UNCLASSIFIED (according to [RD-21]). [Assumption-08] Sentinel-2 X-Band data will not be encrypted (according to the GSC Security Work Group Meeting #4, held on 30.01.2008, GM-MN-ESA-SY- 0015) [Assumption-09] It will be possible to use the EDRS Programme capacity to support both the Sentinel-2 payload data downlink (data relay function), as well as PDGS data circulation and dissemination activities (cf. [RD-47]). [Assumption-10] EDRS capabilities and services will be preliminarily validated as part of EDRS commissioning activities which will be carried out by the EDRS program in coordination with the Sentinel programs. Those activities will make use an EDRS provided validation framework on ground that will not require specific PDGS hardware or pre-deployed facilities apart from a front-end reception equipment to perform compatibility testing of the datarelay multicast link. [Assumption-11] The OCP will, when activated in alternative or in parallel to the XBS, transparently carries the dual 280Mbps downlink channels via the GEO transponders, in turn relaying in real-time the data stream in Ka-Band to GEO pointing ground-stations. Specific receiving equipment, still procured via the EDRS program, will provide the adequate Ka-Band demodulation 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 65 of 350 capabilities on ground and restore the dual 280Mbps data-streams ready for front-end processing. The dual 280Mbps channels restored after the EDRS ground equipment will be clear of any encryption. [Assumption-12] The apportioned availability to Sentinel-2 for data-relay downlinks via the EDRS constellation will be pre-defined at static times phased along the Sentinel-2 orbit repeat cycle, following a preliminary agreement with the EDRS exploitation segment in coordination with Sentinel-1. [Assumption-13] The Sentinel-2 mission can use operationally the EDRS 230Mbps datarepatriation multicast link for a third of the total time (cf. [RD-46]). [Assumption-14] The operation constraints of the OCP will be later characterised by a welldefined operation duty-cycle and an overall limit to the overall number of operation switches sized for the OCP lifetime, similarly to the XBS. [Assumption-15] The MSI timeline received on-ground after downlink will be provided with a granularity of exactly one MSI on-board scene (corresponding to 3.48 seconds of instrument operation and about 23km on ground along-track) as corresponding to the minimum indivisible packet size of the MSI. A playback-stop commanded while an MSI scene is being downlinked will effectively stop the playback and transmission only after the MSI scene has been entirely transmitted. [Assumption-16] The on-board recording of the ancillary data does not require specific scheduling at PDGS mission-planning level as being either entirely autonomous on-board or systematically triggered and maintained through FOS flight operation procedures. The ancillary data is recorded continuously including when the MSI is not operating, or when it is operating in standby or idle modes. [Assumption-17] The XBS can remain in operation mode without the necessity of a temporary transition to standby even when the MMFU is not feeding data to the XBS e.g. during the time separating two successive data-downlinks to ground-stations. In this case, it is assumed idle transfer frames are transmitted instead. [Assumption-18] During orbit control and in case of attitude problems, the MSI shutter shall be closed to protect the instrument. This constraint will be managed by the FOS. [Assumption-19] In response to potential X-Band access conflicts between Sentinels, a conflict-free coordination among Sentinels will result in a predefined allocation of downlink passes available for Sentinel-2. This allocation will be static to a large extent (e.g. on a six to three months basis at least) and will be settled after the selection of the CGS network, or in-any case at the time of the Sentinel-2 PDGS deployment phase. 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 5 and 6:
Page 7 and 8:
Page 9 and 10: 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 59: 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 111 and 112:
GSC Sentinel-2 PDGS OCD Issue 1 Rev
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

Create successful ePaper yourself

Delete template?

Save as template?