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

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

2) The DAG function parses the request and selects the processing centre by making<br />

use of the DAX function to optimise the hosted-processing activities based on the<br />

physical location of the items to process;<br />

3) The DAG function triggers hosted-processing activities by making use of the DPC<br />

function interface(s);<br />

4) During the processing, the DAG function tunnels the monitoring and control flow<br />

between the MMUS client and the DPC server(s);<br />

5) At the term of the processing, the DAG function collects the hosted-processing output<br />

products and makes them available for download;<br />

6) The MMUS function is invoked to trigger the effective download of the products.<br />

6.11 Multi-Mission User Services (MMUS) Operations<br />

6.11.1 PRINCIPLES<br />

6.11.1.1 Client/Server Approach<br />

The MMUS function follows a client/server approach as described in [RD-44]. The MMUS<br />

function client side is in charge of handling the user interactions meanwhile the server side<br />

implements the logic function behind the scenes.<br />

The MMUS function client-side, as explained in the following sections, supported by other<br />

<strong>PDGS</strong> functions, represents the <strong>PDGS</strong> front-end towards the users. As described in [RD-44],<br />

the MMUS function, the MMUS function client-side is separated into:<br />

‣ Web Browser Client: supporting the product discovery request by the user and<br />

subsequent product download;<br />

‣ Download Manager: supporting the automation of the products download and hostedprocessing<br />

requests.<br />

The MMUS function server side, interfaces with other <strong>PDGS</strong> functions for the autonomous<br />

reception of the relevant information to conform the <strong>Sentinel</strong>-2 product catalogue. As<br />

described in [RD-44], the MMUS function server side is separated into several components<br />

here highlighted the ones with direct interaction with the other <strong>PDGS</strong> functions:<br />

‣ ngEO-Feed: for the autonomous collection of the <strong>Sentinel</strong>-2 catalogue data (products<br />

metadata and associated browse images);<br />

‣ ngEO-Catalogue: to catalogue the <strong>Sentinel</strong>-2 production based on the supplied<br />

metadata;<br />

‣ ngEO-Browse Images Archive: to archive the <strong>Sentinel</strong>-2 browse images of the<br />

available production;<br />

‣ Gateway towards the SSO infrastructure for the users authorisation and<br />

authentication;<br />

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