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 236 of 350 o preventing unauthorised access or usage, o preserving integrity of exchanged and stored data, o preserving systems and service availability ○ Compliance with the standard TCP/IP protocol suite; ○ The usage of new high capacity network technologies such as MPLS and CDNs. ○ The potential usage of new highly scalable media delivery content technologies (CDN). ○ The ability to support Quality of Service techniques for differentiating and prioritizing high-priority traffic. ○ The ability to integrate EDRS high-speed multicast capabilities when available. 5.2.5.5.3 Function Interfaces The following interfaces are identified: ○ TCP/IP interfaces with all centres in charge of delivering products to the end users (in particular where the following functions are deployed: Archive and Inventory (AI), Data-Access Gateway (DAG), the Front-End Services towards the end-users such as the Multi-Mission User Services (MMUS) and the On-Line Images Browser (OLIB)); ○ Possible dedicated TCP/IP interfaces with collaborative entities or GSPs; ○ TCP/IP interfaces towards the LAN and/or DCN (interconnection gateway) at each involved centre; ○ EDRS data dissemination TX and RX interfaces; ○ M&C interfaces. 5.2.5.6 Voice Communication Network (VCN) Function 5.2.5.6.1 Function Objectives and High-Level Description The Voice Communication Network (VCN) Function is in charge of supporting human communications between PDGS internal or external interfaces, possibly reusing public telephone or Voice-Over-IP (VOIP) services. 5.2.5.6.2 Design Drivers and Constraints The VCN function is aimed for cost-effectiveness and total reuse of existing public or private infrastructure. 5.2.5.6.3 Function Interfaces The VCN function is human operated. 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 237 of 350 5.3 Physical Model This section describes the decomposition of the PDGS decomposition into generic operation Centres. In turn, the so defined generic centres will be duplicated at will to build the actual operation layouts defined further down in section 5.4 5.3.1 DESIGN LOGIC The PDGS will be geographically distributed in centres interconnected via communication means. Building on the concepts defined in section 4.5.1.4, each centre will be assigned a dedicated role defining its own responsibility perimeter within the overall PDGS operations. The PDGS operations will then result from the coordinated operations of the various centres enabled via the parallel operations of a shared communication infrastructure. The centre roles will be defined by aggregating one or several primary Functions defined in the functional layout (cf. section 5.2). Some generic functions will be operated in every centre as globally supporting the centre operations. Others will be combined such as to specialise the different centre roles. As primarily focussed on data-access performance and flexibility, the federative model introduced in section 4.5.1.4 and cascaded down in the functional design makes the primary basis for the definition of the physical layout. Several drivers are highlighted as particularly relevant in this respect; ○ The data-access performance and scalability considering the high volumes to be managed and an exponential growth of the user demands as justified in section 4.3.5.3; ○ The guaranteed availability of the data in the long-term provisioning for redundancy of the data itself as well as the associated data-access services; ○ The distinct levels of timeliness to be guaranteed at the data-access interfaces considering ground station downstream connectivity and communication performance between remote acquisition, processing and archiving centres; ○ The enabling of evolutions via collaborative opportunities focussing on enhancing the data-access performance. In addition, the programmatic constraints impose an overall flexible, scalable and transportable solution in view of accommodating the initial PDGS set-up whilst provisioning for mission evolutions by further reshaping the PDGS layout. 5.3.2 CENTRE DESIGN This section details the design of each type of centre. Each design is depicted in a dedicated schema using the following conventions: ○ Centre interfaces are represented by yellow squares; ○ External interfaces are represented with a blue background; ○ PDGS internal interfaces or centres are represented with a green background; 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:
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:
Page 113 and 114:
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: GSC Sentinel-2 PDGS OCD Issue 1 Rev
Page 183 and 184: ESA UNCLASSIFIED - For Official Use
Page 191 and 192: 5 PDGS DESIGN GSC Sentinel-2 PDGS O
Page 207 and 208: ○ Effective processing resources
Page 231: o preserving integrity of exchanged
Page 243 and 244: 6 DETAILED OPERATIONS CONCEPTS GSC
Page 245 and 246: o Report generation frequency and c
Page 251 and 252: ○ MSI L1A, L1B, L1C and TCI produ
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?