webinar on 2nd open call - platforms - slideset
TRANSCRIPT
© 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
© 2017 – The symbIoTe Consortium3
• 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
© 2017 – The symbIoTe Consortium4
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
© 2017 – The symbIoTe Consortium
Project Overview & OC2 summary
symbIoTe
Sergios Soursos, Intracom Telecom
Grant Agreement No 688156
© 2017 – The symbIoTe Consortium6
• 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
© 2017 – The symbIoTe Consortium7
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
© 2017 – The symbIoTe Consortium8
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
© 2017 – The symbIoTe Consortium9
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 federatewith, available during
symbIoTe trials!At least 10 devices of at lest 3 different
types!
© 2017 – The symbIoTe Consortium
L1-compliant platforms
symbIoTe
Szymon Mueller, PSNC
Poznań Supercomputing and Networking Center
Grant Agreement No 688156
© 2017 – The symbIoTe Consortium11
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 6Platform 2
© 2017 – The symbIoTe Consortium12
In L1 platform integrate with symbIoTe Cloud and register themselves and their resources in symbIoTeCore
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
© 2017 – The symbIoTe Consortium13
symbIoTe L1 in action
symbIoTe Cloud
IoT Platforms
Applications symbIoTe Core
Query Engine Metainformation
Repository
SEARCH
USESHARE
© 2017 – The symbIoTe Consortium14
Cloud Domain
Async. Messaging (AMQP)
RAPPlugin
symbIoTe L1 in action
RegistrationHandler
PlatformAAM
(security)Monitoring
Interworking Interface
An IoT platform is extended by symbIoTe components
Platform 5
ResourceAccessProxy
Specifically written forparticular platform
MyPlatformCloud Domain components
are integrating Platform with symbIoTe
© 2017 – The symbIoTe Consortium15
1. Installation of required tools (JDK, RabbitMQ, MongoDB, Nginx)
2. Download symbIoTe Cloud components from githubhttps://github.com/symbiote-h2020/SymbioteCloud
3. Configuration of the components and writing platform-specific plugin
4. Registration of the platform in the symbIoTe CoreAdministration portal
5. Starting symbIoTe Cloud of the platform
6. Registration of the platform’s resources in the Core
Integration process
© 2017 – The symbIoTe Consortium16
• 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 platformsand 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 wellas 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
© 2017 – The symbIoTe Consortium17
• If your platform is not covered by aforementioned informationmodels symbIoTe is providing support for extending our basemodels– 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 describeyour resources in the details required by a platform
– Best Practice Information Model mentioned before is in fact a specificPlatform Information Model covering a set of IoT domains
Information models support
© 2017 – The symbIoTe Consortium18
Showcase - Administration
Allows registering of new users (platform
owners)
Platform owners areable to create their
platform in the Core
© 2017 – The symbIoTe Consortium19
Showcase – Search Web AppAllows specifying
filtering options, eg. observed properties
Shows resources whichare fulfilling the criteria
on the map
Table displays moredetails about found
resources
Observation data is obtained from the
platform
© 2017 – The symbIoTe Consortium
L2-compliant platforms
symbIoTe
Joaquin Iranzo, Atos
Grant Agreement No 688156
© 2017 – The symbIoTe Consortium21
• 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
© 2017 – The symbIoTe Consortium22
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 sameEcosystem.
Motivating example
© 2017 – The symbIoTe Consortium23
• 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?
© 2017 – The symbIoTe Consortium24
Federation scenario
Platform A
Resources
Resources
Federated Platform 1
Platform B
Resources
Resources
Platform C
Resources
Resources
Co
re S
erv
ice
s
Federated Platform 2
Federation information
Membership information
© 2017 – The symbIoTe Consortium25
Federation creation
Create
Federation information
Administrator Core Services
Platform A
Resources
Resources
Platform B
Resources
Resources
Federated Platforms
JoinJoin
© 2017 – The symbIoTe Consortium26
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
© 2017 – The symbIoTe Consortium27
How To Become L2-compliant
Co
re S
erv
ice
sP
latf
orm
Se
rvic
es
ResourceAccessProxy
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
Inte
rwo
rkin
g In
terf
ace
Core Interface
User/App
Platform owner
Compatibility layer
(Optional)
Co
re In
terf
ace
Interfaces
RAP Plugin
Core Bartering and Trading
Install &
configure
Integrate & use
Implement
© 2017 – The symbIoTe Consortium28
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?
© 2017 – The symbIoTe Consortium
L3/L4-compliant platforms
symbIoTe
Matteo Pardi, Nextworks
Grant Agreement No 688156
© 2017 – The symbIoTe Consortium30
• 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
© 2017 – The symbIoTe Consortium31
• 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)
© 2017 – The symbIoTe Consortium32
• The Smart Space allows a Smart Device to be accessed from components inside and outsidethe 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)
© 2017 – The symbIoTe Consortium33
• A device that can directlyinteract 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)
© 2017 – The symbIoTe Consortium34
• 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)
© 2017 – The symbIoTe Consortium35
• SSP Middleware installation
• RAP plugin implementation
• Platform/SDEV Agent implementation
How To Become L3/L4-compliant
© 2017 – The symbIoTe Consortium36
• 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
© 2017 – The symbIoTe Consortium
Thank you!
Questions?
www.symbiote-h2020.eu
@symbiote_h2020
H2020 symbIoTe
github.com/symbiote-h2020
© 2017 – The symbIoTe Consortium
OC2 – Management Issues
symbIoTe
Maria Bianco,
CNIT National Inter-University Consortium for Telecommunications
Grant Agreement No 688156
© 2017 – The symbIoTe Consortium39
Open Call - How to apply
Access to F6S Platform
https://www.f6s.com/opencall2symbiote-platforms
Open Call Documentation
www.symbiote-h2020.eu
© 2017 – The symbIoTe Consortium40
• 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
© 2017 – The symbIoTe Consortium41
Application details 1/3
Describe your profile and Create your Team!
Who you are and tell usabout your team –provide a complete Company profile!
- 2 or 3 Key Expertise - Established
company/start-up
Ask your co-workers to login into F6S
© 2017 – The symbIoTe Consortium42
Application details 2/3
6 Main Sections
AUTO SAVE FUNC: do NOT press SUBMIT before the Application is finalised
Limited number of Characters
A. Basic InfoB. IoT SolutionC. Innovation and ImpactD. ImplementationE. Data ManagementF. Miscellaneous
Topic Selection
© 2017 – The symbIoTe Consortium43
Application details 3/3
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 Report2. Final Report
Template available in symbIoTe Standard Extension Contract
Budget BreakDown
© 2017 – The symbIoTe Consortium44
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
© 2017 – The symbIoTe Consortium45
IPR management in SymbIoTe Open Calls: definition of general Principles
• Results are owned by the Party or by the symbIoTe Beneficiary thatgenerates them
• Joint Ownership of results: Third Party and Beneficiaries contributingin a indivisible part of the results -> jointly owned by them in equal sharesor differently ruled with a joint ownership agreement
• Access Rights to Background: only if needed for implementation ofthe Extension. If needed: on royalty-free basis, solely to the extentNeeded to implement its tasks in the Extension;
• Ruled by the Agreement between Third Party and symbIoTeCoordinator symbIoTe Standard Extension Contract
IPR Management
© 2017 – The symbIoTe Consortium46
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
© 2017 – The symbIoTe Consortium47
• 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 businesschampion
– an initial briefing in order to discuss and focus the work tobe performed during the Extension.
– Selected Third Parties can contact the Supporting Team onper-need basis on technical and business matters.
After the Deadline?
© 2017 – The symbIoTe Consortium
Thank you!
Questions?
www.symbiote-h2020.eu
@symbiote_h2020
H2020 symbIoTe
github.com/symbiote-h2020