symbIoTe 2nd Open Call Webinar Summary

© 2017 – The symbIoTe Consortium
2nd Open Call Webinar
Topics: symbIoTe-OC2-L1, symbIoTe-OC2-L2 and
symbIoTe-OC2-L3/4
symbIoTe
20 December 2017
Grant Agreement No 688156

© 2017 – The symbIoTe Consortium2
Meet the team!
Maria Bianco
Open Call Manager
CNIT
Sergios Soursos
Project Coordinator
ICOM
Symon Mueller
L1 Expert
PSNC
Joaquin Iranzo
L2 Expert
ATOS
Matteo Pardi
L3/4 Expert
NXW

• The webinar will be recorded
• Slides and video will be made available
through our web site (Slideshare and YouTube)
• We will take questions in Q&A periods; to ask
questions please use the chat/IM
• Please mute your microphones!
Logistics

Agenda
Time: Session Presenter
10:30 – 10:35 Welcome & Logistics Maria
10:35 – 10:45 symbIoTe intro & 2nd Open Call summary Sergios
10:45 – 11:00 L1 platforms Szymon
11:00 – 11:15 L2 platforms Joaquin
11:15 – 11:30 L3/4 Platforms Matteo
11:30 – 11:40 Q&A
11:40 – 11:55 Management Issues Maria
11:55 – 12:00 Q&A
12:00 End of Webinar

Project Overview & OC2 summary
symbIoTe
Sergios Soursos, Intracom Telecom

• symbiosis of smart objects across IoT environments
• interoperability and mediation framework
• aims at the collaboration of vertical IoT platforms
towards the creation of cross-domain applications
The symbIoTe Approach
Smart Residence
EduCampus
Smart Stadium
Smart Mobility and
Ecological Routing
Smart Yachting

symbIoTe in a Nutshell
• not yet another IoT platform
• a middleware that offers a unified way for
– exposing of IoT resources to third party applications
– sharing IoT resources between federation members
– trusted discovery and secure access to IoT resources
– flexible integration of smart space infrastructure
– does not interfere with the actual data exchange
• addresses the needs of
– developers for rapid cross-platform application
development
– small IoT platform providers for optimal collaboration and
cooperation on top of the available often fallow resources
– SMEs for overcoming IoT market barriers

IoT interoperability – the symbIote way
- Resource registry
- Resource search
- Semantic mapping
- Secure access
- Domain Enablers
Level - 1
- Platform federation
- Resource bartering
Level - 2
- Gateway interworking
- Local interactions
Level - 3
- Device migration
- Device roaming
Level - 4

Topic ID Applicants Budget per
Extension
# of
Extensions
Use Cases
symbIoTe-
OC2-L1
IoT Platform
owners
€40,000 ≤ 2 Smart Residence,
Smart Stadium, Smart
City
symbIoTe-
OC2-L2
IoT Platform
owners
€50,000 ≤ 4 Smart Campus, Smart
City, Smart Residence
symbIoTe-
OC2-L3/4
IoT gateway/
smart device
manufacturers
€40,000 ≤ 4 Challenge event
symbIoTe-
OC2-Apps
Mobile app
companies
€20,000 ≤ 3 Smart Residence,
Smart Stadium, Smart
City
symbIoTe-
OC2-Trials
End user
communities
€15,000 ≤ 3 symbIoTe Trials
(Vienna, Zagreb,
Porto)
OC2 summary Real deployments,
available during symbIoTe
trials! Similar or
complementary use cases
Real deployments,
Select the platform
you want to federate
with, available during
symbIoTe trials!At least 10 devices of
at lest 3 different
types!

L1-compliant platforms
symbIoTe
Szymon Mueller, PSNC
Poznań Supercomputing and Networking Center

symbIoTe L1 in action
Platform 1
Platform 3
Platform 4
Platform 5
IoT landscape today:
many independent, vertical platforms with
non-standardized interfaces and information models
Platform 6
Platform 2

In L1 platform integrate with symbIoTe Cloud and
register themselves and their resources in symbIoTe
Core
symbIoTe Core – can be thought as a central
repository of meta-information about platforms,
resources and models
symbIoTe Cloud – a set of components running on
the platform side that provide communication with
real platform through common interface
High level overview of L1

symbIoTe Cloud
IoT Platforms
Applications symbIoTe Core
Query Engine Metainformation
Repository
SEARCH
USE
SHARE

Cloud Domain
Async. Messaging (AMQP)
RAP
Plugin
Registration
Handler
Platform
AAM
(security)
Monitoring
Interworking Interface
An IoT platform is extended by symbIoTe components
Platform 5
Resource
Access
Proxy
Specifically written for
particular platform
MyPlatform
Cloud Domain components
are integrating Platform
with symbIoTe

1. Installation of required tools (JDK, RabbitMQ, MongoDB,
Nginx)
2. Download symbIoTe Cloud components from github
https://github.com/symbiote-h2020/SymbioteCloud
3. Configuration of the components and writing platform-
specific plugin
4. Registration of the platform in the symbIoTe Core
Administration portal
5. Starting symbIoTe Cloud of the platform
6. Registration of the platform’s resources in the Core
Integration process

• symbIoTe is offering a set of information models
– Core Information Model (CIM) – defines most basic entities, relations
and properties in the IoT domain, such as Resource, Stationary Sensor,
Actuator, Location, Property
– Meta Information Model (MIM) – stores metadata about platforms
and resources within symbIoTe components, such as Platform, User,
Information Model
– Best Practice Information Model (BIM) – contains additional units of
measuerement and properties (such as temperature, humidity) as well
as definitions used in specific domains of IoT use cases, such as smart
mobility, smart residence, smart yachting, smart stadium, e.g. RGB
Light actuator, Retailer Device, Smart Yachting Service etc.
Information models support

• If your platform is not covered by aforementioned information
models symbIoTe is providing support for extending our base
models
– Each platform can specify it’s own Platform Information Model (PIM)
which must be aligned with Core- and Meta- Information Models
– After registering new PIM it is validated and can be used to describe
your resources in the details required by a platform
– Best Practice Information Model mentioned before is in fact a specific
Platform Information Model covering a set of IoT domains
Information models support

Showcase - Administration
Allows registering of
new users (platform
owners)
Platform owners are
able to create their
platform in the Core

Showcase – Search Web App Allows specifying
filtering options, eg.
observed properties
Shows resources which
are fulfilling the criteria
on the map
Table displays more
details about found
resources
Observation data is
obtained from the
platform

L2-compliant platforms
symbIoTe
Joaquin Iranzo, Atos

• Extension of interoperability solution designed
on L1.
• Creation of IoT federation
– Distributed management of federation lifecycle and
quality of the shared resources.
– Management of access and policies for the federated
resources.
– Bartering scenarios to improve the federation
relationships.
• Setting-up of heterogeneous ecosystems
– Lower the (technical) barrier for resource exchange.
– Easy to grow it up.
Overview

Two universities has a good relationships and
collaboration in several fields.
Students want to upgrade their experiments using
other universities resources in order to share
knowledge and improve their work…. however they
need to stop and modify their experiments: two
different accounts, incompatible interfaces
and data models…
Basically, two universes completely
different for the same
Ecosystem.
Motivating example

• Provide tools for managing
platform-to-platform federation
(lightweight federation figure).
• Sharing resources between two or
more platforms at the same level.
• Platforms can consume and/or offer resources (“Prosumers”).
• Same access to all the federated resources.
• Authentication & authorizations
distributed policies rules.
• Introduction of quality of services at
federation level.
• Calculation of trust at different levels (resources, platform and
federation)
• Alternative relationships between federation members free
access and bartering scenarios.
• Creation of dynamic ecosystems.
What does L2 offer?

Federation scenario
Platform A
Resources
Resources
Federated Platform 1
Platform B
Resources
Resources
Platform C
Resources
Resources
CoreServices
Federated Platform 2
Federation
information
Membership
information

Federation creation
Create
Federation
information
Administrator Core Services
Platform A
Resources
Resources
Platform B
Resources
Resources
Federated Platforms
JoinJoin

Federated Platforms
Resource Management in L2
Platform owner A Platform owner B
Platform A
Resources
Resource A
Platform B
Resources
Resource B
User/App
Register Register
notify
searchaccess access
access access

How To Become L2-compliant
CoreServicesPlatformServices
Resource
Access
Proxy
AAM
Monitoring
Administration
Core Anomaly
Detection
Cloud-Core Interface
Registry
Federation
Manager
Bartering and
Trading Manager
(BTM)
Platform
Registry
Subscription
Manager
Trust
Manager
Optimization
Manager
SLA
Engine
Interworking Interface
InterworkingInterface
Core Interface
User/App
Platform
owner
Compatibility
layer
(Optional)
CoreInterface
 Interfaces
RAP
Plugin
Core Bartering
and Trading
 Install &
configure
 Integrate & use
 Implement

To make platforms Level 2 compliant:
• Install and configure the symbIoTe Components
of the Platform Services (Platform Cloud Domain -
CLD)
• Integrate the platform with the core services and
the interworking interfaces.
• Set up the federation and share their resources
(implementation RAP plugin).
• (Optional) Integration of native application.
• Provide feedback and comments to improve and
simplify the process of creating IoT federation L2.
How to federate a platform?

L3/L4-compliant platforms
symbIoTe
Matteo Pardi, Nextworks

• Smart Space Domain:
refers to integration of
platforms and devices
within smart spaces, to
simplify the local
integration and dynamic
reconfiguration of IoT
resources
Smart Space & Device Domains
• Smart Device Domain: the way device can
do roaming and smart objects interact with
visited smart spaces

• Environment where one or
more IoT platforms provide
coordinated services
– related to a physical space
(home, building, vessel)
– or even a broader area
(campus, city)
• Role of the Smart Space
– Provide a container for one
or more IoT platforms
– Provide a reference (anchor)
for Smart Devices
– Notify symbIoTe Core of new
resources
– Notify local IoT platforms of
new resources
symbIoTe Smart Spaces (1/2)

• The Smart Space allows a Smart Device to be
accessed from components inside and outside
the space itself
• Provide uniform access to associated
resources, regardless of the owning IoT
platform
• Resources can be registered with the
symbIoTe Core, providing a transparent
extension for Smart Devices
symbIoTe Smart Spaces (2/2)

• A device that can directly
interact with a SSP
– any mobile device running a
proper symbIoTe app can be
considered an SDEV
– any third party device with an
appropriate wrapper can be
considered an SDEV
• SDEVs interact with symbIoTe
without a platform
symbIoTe Smart Devices (1/2)

• SDEVs can move across Smart Spaces
• L3-compliance: Smart Devices can be
dynamically configured to become part
of the Smart Space
• L4-compliance: Smart Devices are
nomadic, so they associate with the host
SSP, but they keep their identity
symbIoTe Smart Devices (2/2)

• SSP Middleware installation
• RAP plugin implementation
• Platform/SDEV Agent implementation
How To Become L3/L4-compliant

• No differences between L3/L4-
compliance implementations
• Smart Devices specify whether they roam
or not (L3/L4) during symbIoTe
registration process
Differences between L3/L4

Thank you!
Questions?
www.symbiote-h2020.eu
info@symbiote-h2020.eu
@symbiote_h2020
H2020 symbIoTe
github.com/symbiote-h2020

OC2 – Management Issues
symbIoTe
Maria Bianco,
CNIT National Inter-University Consortium for Telecommunications

Open Call - How to apply
Access to F6S Platform
https://www.f6s.com/opencall2symbiote-platforms
Open Call Documentation
www.symbiote-h2020.eu

• Eligibility Criteria
– Start ups, SMEs, companies or research
institutes/organizations, with legal entity already established
– European Member States and Associated Countries
• Funding conditions
– Total Budget : 540.000 euro
– «Platforms» Total Budget: 440.000 euro
– Max Funding per Extension - L1, L3/4 : 40.000 euro
– Max Funding per Extension – L2: 50.000 euro
– Eligible costs: Personnel and Travel costs
• Deadline: 31° January 2018 17:00 CET (Brussels time)
Main Constraints

Application details 1/3
Describe your profile and Create your Team!
Who you are and tell us
about your team –
provide a complete
Company profile!
- 2 or 3 Key Expertise
- Established
company/start-up
Ask your co-workers to
login into F6S

6 Main Sections
AUTO SAVE FUNC: do NOT press SUBMIT
before the Application is finalised
Limited number of Characters
A. Basic Info
B. IoT Solution
C. Innovation and Impact
D. Implementation
E. Data Management
F. Miscellaneous
Topic Selection

Focus: Section D. Implementation
DURATION: Up 6 Months
DELIVERABLE: any tangible output
(Report, Software or Report +
Software) describing your results
2 Additional Deliverables are
MANDATORY for proceeding the
Scheduled Payments !!
1. Intermediate Report
2. Final Report
Template available in symbIoTe
Standard Extension Contract
Budget BreakDown

Evaluation Criteria
Section A
– Team Expertise
Section B
– Impact of IoT solution: it includes also the Complementary Technical
Description
– Business vision and ambition
– Maturity of the IoT solution and approach
Section C
– Offered resources/services and alignment with symbIoTe vision
– Extent of potential benefits from the involved IoT solution
Section D
– Feasibility of work plan: It includes the List of Deliverables and
requested budget
Section E:
– Soundness of approach with respect to management of
sensitive/private data, if applicable
Specifications Available on
the Web site

IPR management in SymbIoTe Open Calls: definition of general
Principles
• Results are owned by the Party or by the symbIoTe Beneficiary that
generates them
• Joint Ownership of results: Third Party and Beneficiaries contributing
in a indivisible part of the results -> jointly owned by them in equal shares
or differently ruled with a joint ownership agreement
• Access Rights to Background: only if needed for implementation of
the Extension. If needed: on royalty-free basis, solely to the extent
Needed to implement its tasks in the Extension;
• Ruled by the Agreement between Third Party and symbIoTe
Coordinator symbIoTe Standard Extension Contract
IPR Management

License
OPEN source license: BSD 3-Clause License
symbIoTe uses it for components on the platform side and platform-
specific extensions
It is business friendly and does not imply that an IoT platform owner
needs to open source its platform nor its symbIoTe-specific extension.
This license is specified e.g. here https://github.com/symbiote-
h2020/SymbioteCloud/blob/master/LICENSE.txt
Licenses per each component also in our github repository here
https://github.com/symbiote-h2020

• Evaluation
– 1 symbIoTe expert and 2 external experts
• Communication of Funding: Beginning of March ‘18
• Support in Implementation phase by symbIoTe
– Supporting Team: 1 technical champion and 1 business
champion
– an initial briefing in order to discuss and focus the work to
be performed during the Extension.
– Selected Third Parties can contact the Supporting Team on
per-need basis on technical and business matters.
After the Deadline?

… and good luck with your submissions!
Thank you for attending our webinar!

symbIoTe 2nd Open Call Webinar Summary

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (15)

Ähnlich wie symbIoTe 2nd Open Call Webinar Summary

Ähnlich wie symbIoTe 2nd Open Call Webinar Summary (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

symbIoTe 2nd Open Call Webinar Summary

Hinweis der Redaktion