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>ESA</strong> UNCLASSIFIED – For Official Use<br />

<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 215 of 350<br />

○ Output interface to provide archived PDI and auxiliary data on request to the AI<br />

function;<br />

5.2.3.8 Data Circulation (DC) Function<br />

5.2.3.8.1 Function Objectives and High-Level Description<br />

The <strong>PDGS</strong> DC function is responsible for performing file exchange operations between subsystem<br />

interfaces within and external to a <strong>PDGS</strong> centre. File exchange circulation can be<br />

performed between electronic and media interfaces.<br />

As such, it is in charge of:<br />

○ Autonomously retrieve required files from configured source interfaces, perform file<br />

transformation operations (e.g. format conversion, compression, file renaming, etc.)<br />

when required and deliver them to configured target interfaces;<br />

○ Perform above described data circulation operations between electronic interfaces<br />

and/or media interfaces when required;<br />

5.2.3.8.2 Design Drivers and Constraints<br />

The following drivers and constraints are identified:<br />

○ Circulation operations reliability. DC function shall ensure that no file is lost during the<br />

data circulation operations due to network failures, media errors, etc.;<br />

○ Flexibility in handling interfaces of very different nature such as electronic via ground<br />

link, via EDRS broadcast and via media. Therefore this capability will require versatility<br />

in adapting to such variety of interfaces and state-of-the-art media technologies;<br />

○ Capacity to manage electronic interfaces with different connectivity requirements (e.g.<br />

secure/non secure connections, file naming conventions, different clean-up policies,<br />

etc.). Connectivity capacities will rely on standard protocols make use of standard<br />

protocols to perform data circulation operations (i.e. SFTP, FTP, SMTP, HTTP, etc);<br />

○ Adaptability to support circulation operations from different <strong>PDGS</strong> functions and<br />

capacity to integrate in a seamless manner with them;<br />

○ DC function circulation services towards the others <strong>PDGS</strong> functions aim at 99,9%<br />

reliability in average;<br />

○ Full automation of all circulation capabilities versus electronic interfaces;<br />

○ Maximised automation of circulation mechanisms via physical media aiming at a<br />

mechanical process driven by simple operational procedures modelling an automated<br />

transportation network;<br />

5.2.3.8.3 Function Interfaces<br />

The following function interfaces are identified for the DC function:<br />

○ <strong>PDGS</strong> functions requiring file-exchange capabilities;<br />

○ A reporting interface to the MCC function via the own DC function;<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!