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 166 of 350 considered an enhancement to the PDGS data dissemination capabilities, it can be commissioned separately without any impact on on-going operations. The data-relay and repatriation links will however require dedicated validation before operational transfer. As the reshaping of the PDGS to support the EDRS scenario will require specific investments for the deployment of new facilities or the upgrade of existing ones, it is assumed that EDRS capabilities will be preliminarily validated as part of EDRS commissioning activities without requiring such investment as pre-requisite. It is hence expected that for all three services, the EDRS program will put in place a validation framework. The PDGS RP and specific front-end processing hardware will however be used in complement to this framework to support Sentinel-2 specific validation activities. The overall approach will thus result in a two-phase validation: ○ At first, the EDRS service will commissioned making use of the EDRS validation framework and the RP; ○ Once pre-qualified on this framework, the required PDGS deployment activities will follow and a second validation activity will be performed. The validation of this last step will trigger the operation transfer activities described in 4.6.5.2. As part of its nominal operations, the reference platform will pre-qualify all specific hardware required to support the EDRS scenario before deployment to the PDGS centres. The following paragraphs describe this approach as applied to the three distinct EDRS services. Although described separately they will be carried out in parallel. 4.6.5.1.1 Data-Relay Link The EDRS data-relay capability can be commissioned with Sentinel-2 at the same time and without any impact on operations. This will be achieved via the parallel downlink of the mission data routed through the XBS and OCP at selected orbits. In a preliminary step, to be carried out during the commissioning phase of the EDRS piggyback payload, the data-relay link with Sentinel-2 will be validated using the EDRS provided validation framework. For this, a PDGS provided front-end reception equipment will be installed in this framework and used to validate the data-reception compatibility. In turn the received data will be shipped to the reference platform and tested for compatibility against the Level-0 and higher level processors. In a second validation step, to be carried out at one PDGS ground facility intended to ultimately receive EDRS relayed data, the ground-reception compatibility will be commissioned and further processing will be carried out, possibly delayed after the operational processing (e.g. during idle periods) if this ground-facility happens to be reusing an X-Band facility. 4.6.5.1.2 Data-Repatriation Link It is assumed the EDRS data-repatriation link will be commissioned in a preliminary step on the EDRS validation framework without any involvement of the Sentinel-2 PDGS. Following the PDGS required hardware deployments, such as the transmission and multicast reception equipment, the data-repatriation capabilities will be validated in parallel to nominal 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.
ESA UNCLASSIFIED – For Official Use GSC Sentinel-2 PDGS OCD Issue 1 Revision 2 (draft) - 25.07.2010 GMES-GSEG-EOPG-TN-09-0008 page 167 of 350 operations by means of data-product circulation operations from the transmit stations to the receiving ones. It is assumed this can be carried out directly using the front-end datacirculation capabilities of the operational PDGS with an appropriate configuration to avoid any impact on nominal data-circulation operations by other means. 4.6.5.1.3 Data-Dissemination Link The validation of the Data-dissemination service for Sentinel-2 will be carried out similarly to the data-repatriation case. Following the PDGS required hardware deployments, such as the transmission equipment to the dissemination transponder for data-broadcasting, the datadissemination capabilities will be validated in parallel to nominal operations by means of databroadcast operations from the transmit stations to one or several test receiving stations. It is assumed this can be carried out directly using the capabilities of the operational PDGS with an appropriate configuration to avoid any impact on nominal operations. 4.6.5.2 Operational Transfer Once commissioned through the activities described above, the PDGS will be already deployed and sized to support the change of mission scenario. This presupposes that all the necessary additional hardware was pre-qualified on the RP before deployment. Depending on the requirements of this scenario, the operation transfer activity will be either gradually phased with separate phase-in activities of the data-relay and data-repatriation services or performed all at once. The data-dissemination service can be phased-in totally independently to the other ones. Regarding the required PDGS software upgrades, the baseline operational transfer approach described in section 4.6.3 will globally apply, involving preliminary reference-qualification on the RP before operational transfer as part of normal work. Finally the operational switch to the new mission scenario will be performed by applying the nominal mission configuration control procedures defined for the PDGS and outlined in section 4.5.3.3, ensuring the accurate coordination of the PDGS configuration and the mission-planning configuration applicable to the new operation scenario. 4.7 Network and Security Concepts 4.7.1 SECURITY The Sentinel-2 PDGS handles, processes, stores and exchanges information of sensitive nature, including: ○ information related to Sentinel-2 users and organisation (with profile and authentication details) ○ information regarding specific requests from the GMES Security Core Service that might be subject to restriction (e.g. users identity) The Sentinel 2 Security Concept is currently based on: ○ policies and regulations that are part to the internal ESA/EO security frameworks, © 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:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
[RD-33] Sentinel-2 MSI - Level 2A A
Page 35 and 36:
Page 37 and 38:
LES LGS Land Equipped Sites Local G
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
3.5.2 MULTI-SPECTRAL INSTRUMENT CHA
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
ESA UNCLASSIFIED - For Official Use
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Table 4-5 Radiometric image quality
Page 99 and 100:
Product- Type On-Line retention Off
Page 101 and 102:
Page 103 and 104:
4.5.1.5 Scalability and Flexibility
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 113 and 114: ESA UNCLASSIFIED - For Official Use
Page 159 and 160: 4.6.3 OPERATIONAL TRANSFER BASELINE
Page 161: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 177 and 178: Product- Type Identifier S2MSI0 S2M
Page 191 and 192: 5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 207 and 208: ○ Effective processing resources
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?