Date post: | 16-Feb-2017 |
Category: |
Technology |
Upload: | iot-epi |
View: | 153 times |
Download: | 0 times |
Co-funded by theEuropean
Commission
IoT-EPI OverviewIoT Architectural Approach
22 June 2016, Common Worksop, Valencia, Spain
Ovidiu Vermesan UNIFY-IoT
Co-funded by theEuropean
Commission
IoT Architecture Project Mapping
Co-funded by theEuropean
Commission
IoT Architecture Project Mapping
Co-funded by theEuropean
Commission
IoT Architecture Project Mapping
Co-funded by theEuropean
Commission
IoT Architecture Project Mapping
Co-funded by theEuropean
Commission
IoT Architecture Project Mapping
Co-funded by theEuropean
Commission
IoT Architecture Project Mapping
Co-funded by theEuropean
Commission
IoT Architecture Project Mapping
Co-funded by theEuropean
Commission
Thank You!
Co-funded by theEuropean
Commission
VICINITY Architecture approach
Štefan Vanya & Viktor Oravec , VICINITY, bAvenir, Slovakia
IoT-EPI Common Workshop, 22-23 June, 2016Valencia, Spain
Co-funded by theEuropean
Commission
What is the aim of the VICINITY project?
“Interoperability as a service, from bottom-up”:
VICINITY will build and demonstrate a bottom-up ecosystem of decentralised interoperability
of IoT infrastructures, where users (and entities) can share access to their smart objects without losing over data.
Co-funded by theEuropean
Commission
VICINITY Architecture approach Isolated IoT
infrastructures or Smart Entities
Build IoT "social" network via VICINITY
Explore VICINITY, expand IoT „social“
network
Co-funded by theEuropean
Commission
Who will be involved in Business scenario?
ABC ACME Inc.
ReagonNo technical roles are
necessary for this scenario.
Co-funded by theEuropean
Commission
Missing data in existing IoT infrastructure
Co-funded by theEuropean
Commission
Login to VICINITY
Co-funded by theEuropean
Commission
Search for partners, devices, services
Co-funded by theEuropean
Commission
Create social network between partners
Co-funded by theEuropean
Commission
Get data in your IoT infrastructure
Processing shared data and consuming shared services in local infrastructure.
Co-funded by theEuropean
Commission
What is the way forward?01interoperability
02semantic auto-discovery & configuration
03added value services on IoT
04spinning the ecosystem
Co-funded by theEuropean
Commission
Thank you!
Co-funded by theEuropean
Commission
Logical VICINITY Solution architecture
Co-funded by theEuropean
Commission
Back-up: Technical architecture approach
Co-funded by theEuropean
Commission
TagITSmart architectureSrdjan Krco, TagItSmart coordinator
DunavNET, Serbia
IoT-EPI Common Workshop, 22-23 June, 2016Valencia, Spain
Co-funded by theEuropean
Commission
Architecture design approach
• IoT-ARM as the guideline• But not building a platform
• Creating TagItSmart specific components, modules, functions • Embeddable into any platform
Co-funded by theEuropean
Commission
Ecosystem creation approach
• Piggybacking on established ecosystems• Provide plugins to enable inclusion of SmartTags
• FIWARE, Unity3D, SocIoTal, Evrything, RunMyProcess, iotNET• And potentially Big IoT, symbIoTe, InterIOT, Vicinity, bIoTope• Leveraging Agile tools
Co-funded by theEuropean
Commission
TagItSmart components
• Device layer• SmartTag reader, SW component for smartphones and embedded readers
• Service layer• SmartTag data model• Service composition module
• Security• Authentication mechanism• Secure transmissions
Co-funded by theEuropean
Commission
Thank You!
Co-funded by theEuropean
Commission
symbIoTe Architecture:Initial Version
Ivana Podnar Žarko, symbIoTe, University of Zagreb, Croatia
IoT-EPI Common Workshop, 22-23 June, 2016Valencia, Spain
Co-funded by theEuropean
Commission
Presentation Outline
• symbIoTe Vision• Major Requirements• Architectural Approach• Further Details on Architecture• Project Assets• Conclusion
Co-funded by theEuropean
Commission
Vision
Interoperability and mediation framework which will enable IoT platforms to
cooperate/collaborateCreate an ecosystem for next-generation cross-
platform IoT applications
Co-funded by theEuropean
Commission
MajorRequirements
Application and Cloud Domain
Resource discovery and unified access across
multiple IoT platforms
Platform federation for resource bartering/trading
Security: authenticated and authorized access to virtual
IoT resources
Smart Space and Device Domain
Hierarchical, adaptive and dynamic IoT environments
Authorized access to physical IoT resources
Seamless roaming of smart objects across smart spaces
(IoT) Resource: sensors and actuators (both virtual and physical)Smart Space: an environment with IoT infrastructure operated by 1 to n platforms
Co-funded by theEuropean
Commission
Approach
symbIoTe Core Services
Enablers’ spaceCross-Platform
Applications
IoT Platforms Space
Smart Spaces
Interworking interface/API
Smart Devices
Application
Domain
Cloud Domain
High-level interface/API
Smart Space Domain
Smart Device
Uniform access to virtual resources
(as services)
Resource discovery across registered
platforms
Domain specific backend services
(“virtual IoT platforms”)
Mobile & Web Apps Use symbIoTe Core Services to find adequate resources, redirected to platforms when using resources
Discovery and registration of new devices, dynamic configuration,
documented interfaces
Roaming devices between smart spaces/platforms
Co-funded by theEuropean
Commission
symbIoTe Core Services
symbIoTe Registry
symbIoTe Search Engine
Resource Monitor
Authentication and Authorization
Resource Access andStatistics
Cross-Platform Applications
IoT Platform A
Interworking interface/API
IoT Platform B
Interworking interface/API
Authentication and Authorization
Manager
Bartering and Trading
Application and Cloud Domain
FederationManager
Authentication and Authorization
Manager
Bartering and Trading
FederationManager
RegistrationHandler
RegistrationHandler
RESTful interfaceoneM2M REST API?OGC SensorThings API?
Native Applications
Extended set of available resources through federation
Work in progress
Co-funded by theEuropean
Commission
Project Assets
• OpenIoT: interoperabilty using semantic sensor descriptions (SSNO)• BETaaS: Building the Environment for the Things as a Service
Open-source solutions
• symbIoTe (NXW): unified software platform for home automation• MoBaaS (UW): mobility management platform with routing services, integration
with FI-WARE Generic Enablers• nAssist (S&C): home automation system, focus on energy management
Closed proprietary solutions
Co-funded by theEuropean
Commission
Conclusion
• Cross-layer approach• Architectural design driven by use cases• Semantic interoperability: symbIoTe Core Services and interworking
interface/API• Organizational interoperability: platform federation within the Cloud
Domain
Co-funded by theEuropean
Commission
Thank You!
Co-funded by theEuropean
Commission
bIoTope ArchitectureKary Främling, bIoTope, Aalto University, Finland
IoT-EPI Common Workshop, 22-23 June, 2016Valencia, Spain
Co-funded by theEuropean
Commission
bIoTope use cases
Co-funded by theEuropean
Commission
Example: Car arriving in town
Co-funded by theEuropean
Commission
IoT CRUD
Create
Read
Update
Delete
1. New ”system” appears
2. Read/subscribeto data,
information, events, …
3. Write data, information,
events, …
4. Remove ”system” or parts of it
with O-MI and O-DF
1. ”Publish” with O-MI write
2. O-MI read/subscription
3. Update with O-MI write
4. No O-MI delete yet
Co-funded by theEuropean
Commission
IoT stack
41
ApplicationDifferent ”platforms”
Taxonomies/OntologiesO-DEF / domain vocabularies /
proprietary vocabularies
Generic IoT Data DescriptionOpen Data Format (O-DF)
Generic IoT MessagingOpen Messaging Interface (O-MI)
Internet CommunicationHTTP/HTTPS/SMTP/TCP/XMPP/FTP…
Lower-level CommunicationISO-OSI model layers 1-6
Generic: OpenIoT, IBM Bluemix, …Domain/company-specific: Energy providers, Fleet management, …
Standards from ISO, SAE, IEEE, The Open Group (or proprietary)
Like HTML for Web
Support necessary IoT operations:subscription, persistence, piggy-backing, callback, …
O-MI can use any of these, and even non-internet communication such as USB sticks and possible future networks
MQTTUses TCP/IP
Co-funded by theEuropean
Commission
bIoTope Big Picture
42
P1
P2
P3
P4
P5
UC1 UC2UC3
DS
DE
Storage & Sensing & Actuation Layer
SR
O-MI/O-DF
Coordination layer/Ecosystem Coordinator
Platform/Tool O-MI/O-DF Compliant Wrapper
Smart Connectedobjects
Wrapper Generator
SR SR
SR
IoT EPIecosystems
SR
Data ContextKnowledge
WSNWSN
OpenFlexibleVersatileHeterogeneous
bIoTope ecosystementry point
Co-funded by theEuropean
Commission
Thank You!
Co-funded by theEuropean
Commission
BIG IoT Architectural Approach
Dr. Arne Bröring, Siemens AGTechnical Coordinator BIG IoT
IoT-EPI MeetingValencia 22.06.2016
Co-funded by theEuropean
Commission
Problem: Missing Interoperability
Dr. Arne Bröring - Siemens AG
Co-funded by theEuropean
Commission
Goals• Do:
• Enable syntactic & semantic interoperability of IoT platforms• Lowering market entry barriers• Fostering an open IoT ecosystems
• Don’t:• Develop yet another platform.• Instead: reusing & building up on existing methods to
allow interweaving of platforms, things, and users.Dr. Arne Bröring - Siemens AG
Co-funded by theEuropean
Commission
Approach
Dr. Arne Bröring, Siemens AG
Co-funded by theEuropean
Commission
Provider Platform
BOSCH SI ConnectedCity Platform
BOSCH CR Distributed Smart Object Platform
CSI Smart Data Platform
ECONAIS Wubby Platform
NUIG OpenIoT Platform
VODAFONE Mobile Analytics Platform
VMZ TIC Platform
WorldSensing Smart Traffic Platform
BIG IoT Marketplace
Aim: Ignite an Ecosystem with BIG IoT Platforms
Application
Application
…
Service
Service
…
Dr. Arne Bröring - Siemens AG
Co-funded by theEuropean
Commission
so far …
BIG IoT API
Usage Example: Platform Interoperability
P1OpenIoTPlatform
Barcelona Piedmont
P2CSI Smart Data
Platform
BarcelonaParking Service
Barcelona Parking
Application
PiedmontParking
Application
PiedmontParking Service
Parking Service
… with BIG IoTFind Free Parking
Application
Dr. Arne Bröring - Siemens AG
Co-funded by theEuropean
Commission
I need to build:
Usage Example 2: Service Discovery
BIG IoT Marketplace
Parking PaymentService
Free Parking Lot Service
Parking ReservationService
Smart Parking Application
Required functionality:- Find free parking- Reserve parking spot- Pay for parkingsearch
… … …Each service has syntactic & semantic description
ServiceDeveloper
Dr. Arne Bröring - Siemens AG
Co-funded by theEuropean
Commission
Conceptual Model
Co-funded by theEuropean
Commission
Component Model
Co-funded by theEuropean
Commission
Your Service / Application
YourService / Platform
Ideas for Collaboration
Cloud-based Agent
GatewayGateway Level
Cloud Level
Device Level
IoT Platform
Gateway-based Agent
ApplicationsApplication Level
BIG IoT Marketplace
BIG IoT Provider Lib
BIG IoT Consumer Lib
Auth
entic
ation
Disc
over
y
Acco
untin
gAc
coun
ting
Regi
stra
tion
Auth
entic
ation
Acce
ss
Thank you for your attention!Questions?
On the Web: http://big-iot.euOn Twitter: @BIG_IoT
Dr. Arne BröringSiemens AG
Co-funded by theEuropean
Commission
•Launched Spring 2015
•160 Members
• Collaborations with:
IETF/IRTF, oneM2M,
OCF, IIC, AIOTI, OPC Foundation, Industrie 4.0
•Working on use cases, requirements, and technology elements
•W3C WoT Webpage: https://www.w3.org/WoT/
Web of Things IG
Dr. Arne Bröring - Siemens AG
Co-funded by theEuropean
Commission
Discovery Security
Thing Description
W3C WoT aims at:
Standardizing building blocks for an open application layer to enable cross domain IoT applications. CoAP
IPv6 / 6LoWPAN
DTLS
Core Link
IoT Building Blocks,
e.g. from IETF
UDP
WoT Building Blocks,
e.g. from W3C
TCP
APIs
Web of Things IG
Dr. Arne Bröring - Siemens AG
Co-funded by theEuropean
Commission
W3C WoT in BIG IoT
Jelena Mitic, Dr. Arne Bröring - Siemens AG
Service / Application
Platform / Service
BIG IoT Marketplace
BIG IoT Provider Lib
BIG IoT Consumer Lib
Authentication
Discove
ry
Accounting
Accounting
Registra
tion
Authentication
Access
TD used as payload.
TD used for searching.
TD describes interface.
Co-funded by theEuropean
Commission
Registration Description{ "@context": [ "http://w3c.github.io/wot/w3c-wot-td-context.jsonld", { "km4c": "http://www.disit.org/km4city/schema#", "qu": "http://purl.oclc.org/NET/ssnx/qu/qu#", "unit": "http://purl.oclc.org/NET/ssnx/qu/unit#", "ssn": "http://purl.oclc.org/NET/ssnx/ssn#", } ], "name": "Smart Data Platform (CSI Piedmont)", "uris": [ "http://api.smartdatanet.it/api/", "ws://stream.smartdatanet.it/ws/", ], "encodings": ["JSON", "XML"], "properties": [ { "@type": "qu:Frequency", "name": "Traffic counter Montalto Dora", "qu:unitKind": "unit:hertz", "hrefs": [ "ds_Trfl_375/Measures", "topic/output.quadrante.2d5dbb35" ], "@reverse": { "ssn:observes": { "@id": "2d5dbb35", "@type": "km4c:TrafficSensor" } } }...
Based on
Web of Things‘Thing Description
Import of additionalVocabularies.
Setting the base URIsof the platform.
Description of the “Offering”.
Co-funded by theEuropean
Commission
Ecosystem: Roles
Jelena Mitic, Dr. Arne Bröring - Siemens AG
Co-funded by theEuropean
Commission
AGILE ArchitectureIoT Architectural Approaches
Charalampos Doukas, Fabio AntonelliCREATE-NET, IT
IoT-EPI Common Workshop, 22-23 June, 2016Valencia, Spain
Co-funded by theEuropean
Commission
AGILE Overview• The modular gateway will be delivered into 2 versions: • a) the makers-friendly version for easily and fast prototyping
IoT solution and b) the industrial version aimed for M2M and industrial use cases
• An expansion module (shield) will be designed for being plugged on top of the RasbperryPi that will allow to easily plug modules, so as existing RaspberryPi can become AGILE gateway
• In the industrial AGILE gateway every main architectural element is a module that is designed following a commons set of rules that ensures interoperability and expandability. In this vision also the power supply and the enclosure are considered as modules and the device is tailored to specific needs
Carrier Module
CPU ModuleStandard COM Express
Rev.2.1
Board Management
Module(BMM)
IntegratedPower supply
N x miniPCIeslots
expansion
GPS module (?)
I/O Expansion Module (CANBus,
I/O expander)
Optional PoE
custom internal
expansion
User I/O
Alternate Power supply
eMMCFlash
SATA DRIVE(Drive bay?)
IntegratedMicroSDCard Slot
Maintenance I/O
Dumb I/O Panel (e.g. for user I/O)
Integrated module
Internal expansion
External expansion
Co-funded by theEuropean
Commission
AGILE Architecture
AGILE Gateway
AGILE Cloud
Co-funded by theEuropean
Commission
AGILE Architecture
Co-funded by theEuropean
Commission
AGILE Architecture
Co-funded by theEuropean
Commission
Thank You!
Co-funded by theEuropean
Commission
IoT-EPI Architectural approach
15:30 - 17:00Arkady Zaslavsky, CSIRO, bIoTope & Raffaele Gravina, UNICAL, INTER-IoT
IoT-EPI Common Workshop, 22-23 June, 2016Valencia, Spain
Co-funded by theEuropean
CommissionPartner Name: CSIRO
• Pros & Cons of cross-project architecture collaboration, sharing,.. • What architectural approach is appropriate ? Cloud, Fog, Edge ? • Domain-specific vs general-purpose ? • Which RA approach to follow ? IoT-A, ITU, ISO, IEEE, NIST, ETSI,
IIoT ?• What is an IoT Platform ? Do we agree with Saverio’s definitions ?
Is focus on a specific layer justified ? Eg, analytics or data or device ?
IoT Architecture session: 15.30 – 17.00
Co-funded by theEuropean
CommissionPartner Name: CSIRO
• How IoT platforms intended for deployment in IoT EPI projects comply with what we heard in the morning session (Saverio) ?
• OpenIoT has been flagged by at least 4 (+1 FoF) IoT EPI projects. What's the status of these deployments ? How can OpenIoT and other EU project outcomes be maintained and continued ?
• Architecture Diversity vs uniformity ??• H2IoT vs M2M ? Human-driven interaction or a machine-driven ?• If a specific (proprietary) tool is used for the project lifetime what to do in
the project afterlife ?• Why some vendors rename their data stream engines into IoT platforms ?
More questions
Co-funded by theEuropean
CommissionPartner Name: CSIRO
• Unique elements of IoT EPI projects that can contribute to complementarity ?
• Inter-IoT – CASE tool – under development – • bIoTope – O-MI/O-DF (TOG), XaaS (context, security & privacy, UI)• Vicinity – bottom-up – No coordination ? No centralised authority ?
Challenges of bottom-up approach ?• SymbIoTe – mediation framework, device roaming, • TagITSmart – IoT-ARM, plugins, QR codes• Agile – IoT gateway, existing tools & platforms• Big IoT – syntactic & semantic interoperability, marketplace, language ?
More questions
Co-funded by theEuropean
CommissionPartner Name: CSIRO
• Regular discussion item at IoT EPI meetings/workshops ?• White paper on IoT EPI architectural approaches and RA - Mid-2017 ?• SIG within TF02 ?• Awareness of project approaches and best practice sharing - web-page
Next steps