Building the Environment for
the Things as a Service
IoT CoAP Plugtests™ & Workshop
November 27th 2012
Introduction
The BETaaS FP7 project The BETaaS FP7 project –– Facts
•
•
•
•
•
•
•
Start date: 1/10/12
End date: 31/3/15 (30 months)
End date: 31/3/15 (30 months)
Cost: 3,376,640 €
Funding: 2,515,000 €
Estimated effort: 441 PM
Estimated effort: 441 PM
Call identifier: FP7‐ICT‐2011‐8
Website: www.betaas.eu
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
3
The BETaaS FP7 project The BETaaS FP7 project ––
Partners
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
4
Context: toward an M2M reference
Context: toward an M2M reference model
The old M2M approach
• IoT market is growing at a fast rate
market is growing at a fast rate
– Billions of M2M connected devices in the next decades…
decades
– … thousands of M2M vertical solutions? Unacceptable
bl
M2M Services
Things
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
6
The horizontal solution
• Common reference model offering service p
capabilities
– Interoperability
– Fast deployment
Fast deployment
– Reduced complexity
–…
Applications
M2M Services
• Example
Things
– ETSI M2M
27th Nov – IoT CoAP Plugtests™ & Workshop
Common Reference Model
BETaaS
7
The role of BETaaS
The role of BETaaS
• Define an ecosystem for development and p y
pp
deployment of M2M applications
– Working on top of already existing M2M frameworks (e g ETSI M2M)
frameworks (e.g., ETSI M2M)
• Focus on M2M applications
– Applications as real drivers of innovation
– High level services to build M2M applications
g
pp
– Enabler of the local cloud model
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
8
The BETaaS
The BETaaS concept
Build a service platform for the IoT and the M2M over a local cloud of gateways
a local cloud of gateways
BETaaS Key Points
• Things as a Service (
Things as a Service (TaaS
TaaS) reference ) reference model
• Local cloud of gateways
g
y
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
11
BETaaS Key Points: Key Points: TaaS
TaaS
• BETaaS must be a reference model for M2M pp
applications
– Applications can be built on top of BETaaS, ignoring M2M specific requirements
ignoring M2M specific requirements
• Services use the TaaS as a reference model
– Adaptation layers will make BETaaS
Adaptation layers will make BETaaS operable with operable with
different M2M implementations
– Support for semantic data in high level services
f
h hl l
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
12
The BETaaS
The BETaaS architecture
Service Module 1
Service Module 2
…
Service Module N
Service
Layer
TaaS (Things as a Service)
(Things as a Service)
Logical
Layer
Adaptation Layers
M2M Framework
Physical
Layer
Things
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
13
BETaaS Key Points: local cloud
• BETaaS operates distributedly over a local g
y
cloud of gateways
– BETaaS gateway: logical entity that contributes to the service of the BETaaS instance
the service of the BETaaS
– BETaaS instance (or local cloud): the interconnection of the BETaaS gateways, offering interconnection of the BETaaS
gateways offering
services to BETaaS applications
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
14
The BETaaS
The BETaaS layers
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
15
BETaaS Gateways
• Washing Machine
• Car Charger
• Garage Door
• Alarm System Alarm System
Control
• Air Conditioning Control
• Temperature
• Humidity
• Lights Control
• Motion Detector
• Television 27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
16
The Local Cloud of Gateways
• Alarm System Control
• Air Conditioning Control
• Washing Machine
g
• Car Charger
• Garage Door
• Temperature
• Humidity
• Lights Control
• Motion Detector Any
Business
Logic
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
17
Applications are the center
Service
Di
Discovery
• New available services
p
y
• “Temperature now ready”
Semantic p
description
• Implementation independence
l
i i d
d
• “Temperature for kitchen”
Single Entry Single
Entry
Point
• Applications only see BETaaS
Applications only see BETaaS
• “Service provided by any GW”
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
18
Distributed vs
Distributed vs Centralized
Centralized cloud approach
Internet
Distributed local cloud approach
Local end-toend service
Application
Gateway
Things
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
Things
19
The local service
• BET
BETaaSS is a distributed platform running on a local cloud of i di ib d l f
i
l l l d f
gateways
– Scalabilityy
• Gateway‐centric infrastructure
• Data aggregated and elaborated locally
– Security
• Service obtained from the local cloud
– Reliability
• Remote links and remote resources are not needed
Remote links and remote resources are not needed
• Redundancy comes at a low cost
• Local caches
– QoS
Q S
• Low end‐to‐end latency and high throughput
• High scalability for performance
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
20
Context and resource awareness
• Context awareness
– Information acquires different meanings depending on the context
h
– Resource discovery and data aggregation
– E.g.: The semantic object “Temperature sensor” can be associated to different real devices depending on the availability within the current context
the availability within the current context.
• Resource awareness
– Awareness of resources available in the local context A
f
il bl i th l l
t t
• Computational capabilities, storage capabilities, connectivity, power supply
po
e supp y
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
21
BETaaS simple example
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
22
Simple example call flow
Device registration
M2M framework
Successfully Registered
Semantic and
High Level
service
APIs
Subscribe to “temperature”
Data subscription
service
y Subscribed
Successfully
New measurement
M2M fframework
k
Data notification
service
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
23
Use cases
BETaaS deployment
• BETaaS can run on any capable device
– TV Top Boxes
TV Top Boxes
– Home routers
– Smartphone / Tablets
S
t h
/ T bl t
– Laptops / Desktops
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
25
Home Automation Use Cases
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
26
Parking Service readyy
Smart City Use Cases Mobility
Ultra Parking Mobility
Service?
Service??
Office
Service
ready
Asking BETaaS
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
27
Conclusions
BETaaS impact
• Advanced service modules
– Semantic support
– Context awareness
• The BETaaS platform
– TaaS reference model for M2M applications
• TestBeds for two use cases
for two use cases
– Home automation
– Smart City
Smart City
• Open source release to the community
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
29
BETaaS Benefits
• Interoperability between different M2M implementations
– A
Applications consistently and seamlessly li ti
i t tl
d
l l
use the same services on top of TaaS
• Distributed over local clouds
– Highly scalable and efficient
– Context awareness
27th Nov – IoT CoAP Plugtests™ & Workshop
BETaaS
Services
Services
TaaS
TaaS
ETSI M2M A. L.
IoT‐A A. L.
ETSI M2M
IoT‐A
30
Vincenzo Pii
Intecs S.p.A.
Software Engineer
[email protected]
Thank you
Thank you