INTERNATIONAL DATA SPACES DEVELOPERS COMMUNITY€¦ · Certification Testing Reference Testbed Demo Centre. // 6 • Guide for new members and other interested parties to lead them

DEVELOPERS COMMUNITY

HEINRICH PETTENPOHL BONN, JUNE 26TH, 2019

INTERNATIONAL DATA SPACES

AGENDA

• Overview• Different implementations of the IDS Connector• IDSA Plugfest• Next IDSA Plugfest

www.internationaldataspaces.org // 3Legende: IDS Connector; Usage policy; Datenaustausch ohne IDS.

THE INDUSTRIAL DATA SPACE FORMS A NETWORK OF TRUSTED DATA

Industrial Data Cloud

IoT Cloud

Enterprise Cloud

DataMarketplace

Company 1 Company 2 Company n + 2Company n + 1Company n

Open Data Source

IDS

IDS IDS

IDS

IDS IDS

IDS

IDSIDS

IDS

IDS

IDS

IDS

IDSIDS

IDS

IDS

IDS

IDS IDS

www.internationaldataspaces.org // 4

THE INDUSTRIAL DATA SPACE FORMS A NETWORK OF TRUSTED DATAFOR ALL INDUSTRIES TO LINK DATA

www.industrialdataspace.org // 5

ENABLING ADOPTION AS A PARALLEL STREAM TO THE IDS DEVELOPMENT

On Boarding Community

TNO

Adoption

Definition

IDS-G Product

Topics & Requirements

Developers Community

Plugfest(testbeds)

RAM &Certification Criteria

Standards

Certification

Testing Reference

Testbed

Demo Centre

www.industrialdataspace.org // 6

• Guide for new members and other interested parties to lead them thru the first steps in implementing a connector

• Collection of important documents and other relevant sources, e. g. GitHub repositories

• How to build a connector in 2 steps1. Describe the architecture of your connector;

including concrete examples and guiding questions2. Define your execution core container; with

explanation of core container, X.509 example, example code for data route implementation using Apache Camel Route amongst others

IDS STARTER KIT

AGENDA


// 8www.internationaldataspaces.org

DIFFERENT IMPLEMENTATIONS OF THE IDS CONNECTOR

Operating System

Virtual Machine / Hardware

Application Container Management

Runtime Runtime Runtime

APIAPI DataRouter

DataBus

Custom Container

App Store Container

ExecutionCore Container

Data App Data App Execution Core

Source: https://industrialdataspace.jiveon.com/docs/DOC-2038

A Survey showed 12 different implementations:https://industrialdataspace.jiveon.com/docs/DOC-2038

10 using Server (x86), 4 Raspberry , 1 ESP8266

9 using Linux; 3 Windows 10; 1 trustme; 1 Raspbian, 1 none

8 using Docker; 1 trustme; 3 none

6 using Apache Camel & Active MQ; 6 none

4 implementations supports Apps; 5 don‘t support; 3 unknown

9 support HTTP/REST; 6 MQTT; 2 IDSCP

https://industrialdataspace.jiveon.com/docs/DOC-2038

www.internationaldataspaces.org // 9

DIFFERENT IMPLEMENTATIONS OF THE IDS CONNECTOR

Source: https://industrialdataspace.jiveon.com/docs/DOC-2038*https://industrial-data-space.github.io/trusted-connector-documentation/

5 implementations are Open Source (2 public available*), 7 are not yet decided

5 using V1.0.1, 2 using V1.0, 1 using pre 1.0, 4 with no model or unkown

5 using proprietary configuration files, 3 Docker Compose, 1 Portainer/Talend Eclipse

7 are Base Free, 3 Base, 2 Trust

AGENDA



PLUGFEST


Goals

• Consolidation of the existing implementations• Technical connection between the components• Build up a common understanding• First MVP of the IDS:

• Connectors register at CA, DAPS, Broker• Connectors exchange data

Tasks for participants

• Participants bring in their current implementations• Establish CA and register Plugfest-Connectors• Establish DAPS and register Plugfest-Connectors• Establish Broker and define registration message• Support current information model V1.0.2• Agree on data protocol


SETUP A CONNECTOR


Plugfest Q4/18


DATA EXCHANGE

Plugfest Q1/19

Plugfest Q1/19

Plugfest Q2/19


USAGE CONTROL INSIDE THE CONNECTOR

IND2UCE / MYDATA LUCON

• Fraunhofer AISEC

• TRL 3-4

• Open Source

• Dynamic UC

• Label Based

• Fraunhofer IESE

• TRL 8-9

• Closed Source / License

• Dynamic UC

• Central PEP

D°

• Fraunhofer ISST

• TRL 3-4

• TBD

• Static UC

• During Compile Time

Further Frameworks

• ?

Plugfest Q2/19


• Provided by MDM Connector in the IDS LAB https://mdm-connector.ids.isst.fraunhofer.de

• Data could be used within time interval

• Data could only be used in Germany

• Data Apps have properties (stateful, data adapter,…); Policy defines which properties are allowed for the data flow

USAGE CONTROL – USE CASES

https://mdm-connector.ids.isst.fraunhofer.de/


RESULT OF THE PLUGFEST

Source: https://www.ids.isst.fraunhofer.de/confluence/display/IDS/Plugfest

Res

ult

sQ

2/2

01

9

Clearing House Prototype is now available: https://idsa-ch.orbiter.de/about/App Store Prototype is now available: apps.ids.isst.fraunhofer.de:5000

UC App from MyData is available: https://oc.iese.de/index.php/s/ZKnhgIlbidzWiMx PW: IDSA-Plugfest-Q2


PROTOTYPED IDS SERVICES TO TEST YOURIMPLEMENTATION

Further information about the registration at and usage of these services: https://industrialdataspace.jiveon.com/docs/DOC-1996

Prototype Service Responsible Hosted at Status URL

Identity Provider AISEC AISEC Running https://industrialdataspace.jiveon.com/docs/DOC-2002

DAPS nicos AG nicos AG Running daps.dc.nicos-ag.com:8081

DAPS AISEC AISEC Running https://daps.aisec.fraunhofer.de/token

DAPS (Test) ISST IDS-LAB Running https://daps.ids.isst.fraunhofer.de/token

EIS-Broker IAIS IDS-LAB Running https://broker.ids.isst.fraunhofer.de

Echo-Connector ISST IDS-LAB Running https://echo.ids.isst.fraunhofer.de

App-Store FIT IDS-LAB Running apps.ids.isst.fraunhofer.de:5000

Clearing House AISEC/FIT/OrbiterIDS-LAB / Orbiter

Planned Q3/2019https://idsa-ch.orbiter.de/about/

AGENDA



FURTHER DEVELOPMENT OF THE PLUGFEST


PLUGFEST


How to participate? Next Plugfest

17th/ 18th September 2019, IDS Lab - Fraunhofer ISST in Dortmund

Topics:• Usage Control• Integration AppStore• API Specification• Clearing House

• Contact Heinrich Pettenpohl for onboarding

• Participate in the weekly telcos

• Notebook/computer with admin privileges

• Network/proxy configuration must be able to be changed

• Own source code of one or more IDS implementations (Connector, Broker, CA, App Store etc.)

• Corresponding development environment for customizing the sources

• Docker or VMWare/VirtualBox for Windows computers

// 21

JOIN US !@ids_association# internationaldataspaces

www.internationaldataspaces.org Ressource Hub – Press Area – Blog

HEINRICH PETTENPOHL

DEPUTY HEAD OF DEPARTMENTDIGITIZATION IN SERVICE INDUSTRIES

FRAUNHOFER INSTITUTE FOR SOFTWARE AND SYSTEMS ENGINEERING

EMIL-FIGGE-STR. 9144227 DORTMUND | GERMANY

+49 231-97677-321

INTERNATIONAL DATA SPACES DEVELOPERS COMMUNITY€¦ · Certification Testing Reference Testbed Demo Centre. // 6 • Guide for new members and other interested parties to lead them

Documents