Transcript ESA_ServiceInfrastructure__May2004

Service Infrastructure
within the ESA GS
Pier Giorgio Marchetti – ESA / ESRIN
+39 0694180413
Cell. +39 3485628804
[email protected]
Ground Segment Department
Infrastructure for Service Support
May 2004
adding value to data…
means supporting services
Data
Environment
User
Environment
Mission Planning
Acquisition
Archiving
Processing
Order Desk
Catalogue
Help Desk
Ordering
Dissemination
Quality Control
Service Support
Support 4 Service Providers
Support 4 users
Service
Environment
Infrastructure for Service Support
May 2004
Oxygen Ground Segment Model
Web Portal
Catalogue
Mission Planning
Data Ordering
User Services
Help Desk
Quality Control
CO-ORDINATION CENTRE
Acquisition
Archive
Dissemination
Production
Information
Mining (future)
Monitoring &
Control
Network
FACILITY
Infrastructure for Service Support
May 2004
Services Infrastructure – From …
Non EO
Data
Data
Environment
Service
Provider
Value
Adder
Value
Adder
Data
Environment
End
User
Service
Provider
Value
Adder
Distributor
End
User
User
Envir.
Infrastructure for Service Support
May 2004
User
Envir.
Data
Environment
…To - Services Infrastructure
Non EO
Data
Data
Environment
Value
Adder
IIM
IIM
Data
Environment
End
User
IIM
Service
Provider
Value
Adder
IIM
Service
Provider
Value
Adder
Distributor
End
User
User
Envir.
Infrastructure for Service Support
May 2004
User
Envir.
Data
Environment
Service ????

Service
A Service is the repeated, regulated (usually by
means of a Service Level Agreement) and agreed
(via contract or agreement) or declared (with
defined quality parameters) exploitation (for
commercial or non-commercial purposes) of a
function, processor or application. The output of a
service includes data, products, information and
solutions.

Web Services Please refer to W3C http://w3c.org
Infrastructure for Service Support
May 2004
Service Infrastructure – the users
Service Providers
Users
Service Consumers
Infrastructure for Service Support
May 2004
Service Infrastructure – the interactions
B2B
Co-operation
B2C
Service Exploitation
Users
Service Providers
Service Consumers
Infrastructure for Service Support
May 2004
SI – high level requirements

• Concentrate on supply chain
orchestration and flow control
B2B
Co-operation
B2C
Service Exploitation
• Let Users (and COTS) rule data
format issues
Service Providers
Service Consumers

Online, nrt or offline service
execution are all the same

Foster long term research & industry
growth
Users

Empower Service Providers:
• Service Providers maintain full
control over their own
infrastructure
• rely on widely accepted and open
standards (see OGC, W3C and ISO
TCs)
• “Neutral” service infrastructure

Empower GS harmonisation
• Simple catalogue service
• Order service
Shortcut data “format” issue:

Support requirements from relevant
actors and European Programmes
• EC-DG INFSO, JRC, EUSC
• Generic service activationInfrastructure for Service
May 2004
• Support
GMES, INSPIRE,…
SI – the functional objectives

Service support environment for
the integration of Earth
Observation and GIS supply
chains

Support for data providers,
service providers and end-users
alike

Supply chain orchestration uses
web services and workflow strds

Open and distributed
architecture, allowing to add
new supply chains

User driven/selected service
delivery
B2B
Co-operation
B2C
Service Exploitation
Service Providers
Service Consumers
Users
Infrastructure for Service Support
May 2004
SI – the user…

• anonymous user: can only activate free
services
B2B
Co-operation
B2C
Service Exploitation
 access via the Global, Regional or
Thematic Portal
Service Providers
• registered user: can activate free or
paying services
Service Consumers
 access via the Global, Regional or
Thematic Portal
Users

Multiple user types:
Multiple utilisation scenarios
• Service Provider co-operation
• Test and fast/cheap deployment
of new supply chains
• Simplified user access
• …
• service provider: can add new services
 access via the Global, Regional or
Thematic Portal
 access via workflow client tools
• helpdesk, administrator
 access Admin functionality on the
Global, Regional or Thematic
Portal
Infrastructure for Service Support
May 2004
SI – the architecture …
B2B
Co-operation
B2C
Service Exploitation
Service Providers
Service Consumers
Users
Global
Regional
EO
or
Service
Thematic
Infrastructure
Service
Infrastructure
Infrastructure for Service Support
May 2004
Service
Provider
Legacy
Service
Legacy
Service
Catalogue
Service
Regional or Thematic
Service Infrastructure
Toolbox
SOAP
Catalogue
Service
SOAP
Portal
SOAP
Workflows,
service data,
order data ...
AOI
Server
HTTP
HTTP OGC
WMS Server(s)
Mobile Client
Web Browser
Workflow Editor
Infrastructure for Service Support
OGC
May 2004
Gazetteer Server
Supply Chain Orchestration … 1
AOI selection
(GIM)
NPP*
Service VITO
NPP input
+ AOI description
+ required format
Format
Conversion
Service GIM
NPP-Europe
-HDF
Clipping
Service GIM
NPP-Europe
-GeoTIFF
NPP-Belgium
-GeoTIFF1
(*) NPP or Net Primary Productivity represents
repeatable estimates of the net flux of carbon.
Product is based on Végétation S10.
Infrastructure for Service Support
May 2004
Supply Chain Orchestration… 2
Combining service
Fire stations
Roads
Community boundaries
NDVI
Risk Map
LST
Fire risk map
Digital Terrain Model
Chaining
Overlaying
• GIS additional way to combine services.
• Useful for vulnerability maps, hazard maps, rescue resources
map, crisis map etc.
Infrastructure for Service Support
May 2004
Control flow
Order A
MASS User (8)
: control flow
: data flow
: XML
Portal &
Workflow
Engine
(1)
Result A
Internet
(4)
User FTP
Server
(5)
Result A1
Order A1
Result A2
(2)
Order A2
(7)
(3)
(6)
Service Provider
A1 (e.g. VITO)
(9)
Infrastructure for Service Support
Service Provider
A2 (e.g. GIM)
May 2004
User Interaction

Select service of interest

Identify time and AOI (method of selection is chosen by
SP)

Select parameters (e.g. format)

Get RFQ (if applicable)

Issue request

Check status of orders/requests

Get the output (delivery options identified by SP)
Infrastructure for Service Support
May 2004
Selection of time, AOI and parameters
Infrastructure for Service Support
May 2004
Check status of orders/requests
Infrastructure for Service Support
May 2004
Get results (service output)
Infrastructure for Service Support
May 2004
Oil spill detection
(Spacetec)
Infrastructure for Service Support
May 2004
Ship detection
(Spacetec)
Infrastructure for Service Support
May 2004
Simple Catalogue Service

Objective: Proof and test catalogue service within
environment for the orchestration of EO services

Technology: Web Services, Workflow engine

Preliminary results:
• Simple catalogue access and interoperability is made easy
• Technological homogeneity makes integration of (different) service
elements simple and their orchestration straightforward
• Exploitation of state of the art OGC standards allows seamless
integration into mapping services
Infrastructure for Service Support
May 2004
Spot “search”
results (GML)
Envisat “search”
results (GML)
Catalogue search
results (textual)
Infrastructure for Service Support
May 2004
receive
While CollectionId in request
ASYNC WRAPPER
invoke
receive
initiate( [in] searchCriteria
collectionId)
Dynamic partnerLink
assign
invoke
While CollectionId in request
receive
invoke
onResult( [in] resultList )
assign
onResult( [in] completeList )
reply
Infrastructure for Service Support
May 2004
DEALER
SEARCH
INVENTORY
PROVIDER
1…N
SERVICE
Service Provider

Enters in partnership with other service providers

orchestrates the supply chain defining which elementary
services are part of it…

authorises users to activate “his” supply chain

publishes the services from “his” infrastructure (over which
he maintains the full control)

monitors “his” service execution, state, on the workflow, on
his infrastructure

is responsible for
• defining and publishing “his” own SLA
• monitoring and respecting “his” QoS; invoicing (where applicable)
Infrastructure for Service Support
May 2004
Workflow console
to monitor service
instances
Workflow editor
to chain services
Infrastructure for Service Support
May 2004
Interface vs. SP legacy
Infrastructure
Client
HTTP
EO
Service
Infrastructure
SOAP / HTTP
Toolbox
Infrastructure for Service Support
Legacy
May 2004
Service
Provider
Legacy
Infrastructure
The Toolbox Concept

Allows easy “publishing” of any service, with minimum
assumptions on the SP available infrastructure (including
NO infrastructure)

Provide a generic gateway toward service providers’
infrastructure

Generic/Customisable Service Interface: different Back
End communication and interactions supported.

Customisation towards the SP infrastructure based on
XML scripting
Infrastructure for Service Support
May 2004
TOOLBOX Overview (1)

Based on free and Open Source software
• No additional licences are needed

Front-End supporting the communication with MASS.
• Based on Java and the SUN JWSDP
 TOMCAT
 JAXP (XML handling library)
• It implements all the MASS interfaces




Order (synchronous and asynchronous)
Request For Quotation (synchronous and asynchronous)
Search (synchronous)
Present (synchronous)
• Supports a generic service integration

Automatic WSDL creation
Infrastructure for Service Support
May 2004
TOOLBOX Overview (2)

Back-end supporting the most common
“communication mechanism”
• FTP file transfer
• HTTP
• File exchange
• Email notification
• JDBC
• Command and script invocation
• SOAP over HTTP

Products delivery supported by an internal built-in
FTP server
Infrastructure for Service Support
May 2004
Service Integration on the Service Provider Side -1

Service Configuration and test
• Possibility to create and configure a service by means of a Web
Application




Access control
A Simple SOAP client is provided for test purposes.
It includes a Catalogue test page.
On-line Service Definition Script validation.
Infrastructure for Service Support
May 2004
Service Integration on the Service Provider Side - 2

Service Execution
• Triggered by SOAP messages coming from EO Service
Infrastructure
• Support for both synchronous and asynchronous communication
mechanisms.

Service Monitoring and Control
• Possibility to monitor the status of the service by means of a Web
Application
 Requests cancellation
 Requests monitor
• Service log Monitoring
 Log based on XML
 XSLT transformations.
Infrastructure for Service Support
May 2004
Service Testing: SOAP client
Infrastructure for Service Support
May 2004
Service Test: Simple Catalogue
Infrastructure for Service Support
May 2004
Service Monitoring: Log
Infrastructure for Service Support
May 2004
Service Definition Panel
2 - define interaction method
1 - select service category
3 - describe service
4 - here the techs
Infrastructure for Service Support
5 – register!
May 2004
Operational Demonstration
 Operational
Demonstration :
• Starts in October 2004
• >30 services
• >15 service providers
• Countries already involved: Belgium, France, Germany,
Italy,(Norway), UK, Switzerland, The Netherlands,
Portugal, … others
• Open to any user and additional service providers
Infrastructure for Service Support
May 2004
Conclusions…

Service Infrastructure facilitates:
• Integration of wide range of heterogeneous EO and GIS services including
catalogues (open to geospatial local/global data/services)
• contacts between service providers and users more coherent (e.g. single
service responsibility)
• Working relationships among service providers via the flow control (basic
cooperation environment)

SI empowers service providers
• enabling to combine and chain service elements within the supply chain
• Allows re-use generic or basic services
• Efforts potential service providers limited to specific skills and added value
• Allows to broaden and improve existing services

SI empowers users
• offering services that are closer to the user’s expectations.
Infrastructure for Service Support
May 2004
Conclusions…

Future work
• Consolidate ongoing work on simple catalogue access and order
management Interface Control Documents discussed with CNES,
DLR, ASI, + others
• Get feedback on open source TOOLBOX
• Expand institutional cooperation at national and international level
EC-DGINFSO, EUSC, JRC, …
• Involve federating agencies EEA, …
• Extend collaboration with standardization bodies OGC, ISO, …
• Consolidate working relationships with relevant programmes
GMES, GSE, …
• ICD Documents & TOOLBOX available at http://earth.esa.int/rtd
Infrastructure for Service Support
May 2004
Image Information Mining Coordination Group
ASI, CNES, CNR, DLR, EC-IST, ESA, ETHZ, EUSC
http://earth.esa.int/rtd/IIMCG
 IIMCG terms of reference

Charter

For Image Information Mining (IIM) applied to Earth Observation images, the IIMCG shall:

Promote European research and development of IIM techniques

Interface with European and National programmes in the field, like the O2 (Open and Operational) ESA initiative,
the EC FP6 activities, etc.

Foster, within the members, the possibility to:

Share scientific and technical experience, data, information and applications

Identify relevant scientific and technical issues

Suggest technical directions

Suggest solutions for funding and coordination of activities

Provide a forum where interested bodies may:
•
Constantly be kept updated on ongoing activities in the field and on relevant scientific and technical issues
•
Exchange information (including gathering of suggestions and requirements)
•
Be informed on available demonstrators, prototypes, products, etc.
•
Identify and suggest / promote appropriate standards
•
Facilitate and promote the use of resulting products
Infrastructure for Service Support
May 2004
Image Information Mining Coordination Group
ASI, CNES, CNR, DLR, EC-IST, ESA, ETHZ, EUSC
http://earth.esa.int/rtd/IIMCG
IIMCG terms of reference

Establish and maintain liaison with other interested bodies and with new
sensors’ research and design (in particular for the identification of short /
medium / long term needs)

Identify research and technological issues

Define possible strategies and solutions

Suggest activities and coordination methods

Suggest standards and interfaces for possible technologies
Infrastructure for Service Support
May 2004