Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
Embedded devices on the
Internet of Things
Zach Shelby, Sensinode
Jan Höller, Ericsson
Internet of Things
Devices in Constrained IoT Environments
› Endless applications in the IoT domain
› Embedded low cost and low power devices
› Legacy technologies
› Current practice is stove pipe solution
– single device – single application
ETSI 3rd M2M WS | 2012-07-11 | Page 2
–
› Transformation needed
– application independent devices
– many-to-many
› IP and the Web Paradigm paves the way to hide and avoid complexity and to provide simpler lower cost solutions
What is “constrained”
Scaling NetworksLow Cost
ETSI 3rd M2M WS | 2012-07-11 | Page 3
Low Bandwidth
Battery Powered
LimitedProcessing
Constrained but still Internet
› Today - a complete IP based Web stack can be run on
small devices with microcontrollers
48 kB of Flash 8 kB of RAM
ETSI 3rd M2M WS | 2012-07-11 | Page 4
IEEE
802.15.4PLC DECTBTLE
IPv6
UDP
CoAP
Resources
6LoWPAN
/temp /light /switchInternet
8 kB of RAM
Embedded Web
› The Internet of Things will be powered by Web technology
› Technology from the IETF
– Constrained Application Protocol (CoAP)
– Web Linking
– Resource Directory
– Security
ETSI 3rd M2M WS | 2012-07-11 | Page 5
– Security
› Application Semantics
– IPSO Application
Framework
– OMA Lightweight
M2M Objects
Embedded Web in M2M Standards
SE2.0
IP RouterCoAP
HTTP
ETSI 3rd M2M WS | 2012-07-11 | Page 6
IP and Web
Web & Mobile AppsOMA Lightweight
CoAP
HTTP
There is still a role for gateways
› Traditionally bridges heterogeneous
networking technologies
› Gateways can, and do, many more
things
– local storage
– data processing, event filtering and
stream analytics
semantic annotation and metadata
IoT
Mgmt
Surveillance
Energy Mgmt
HVAC Ctrl
Access Ctrl
Applications
Service Providers
ETSI 3rd M2M WS | 2012-07-11 | Page 7
– semantic annotation and metadata
– local sensor-actuator control loops
– security perimeter
– shielding resource constrained
devices
› Multiple applications and involving
multiple stakeholders and service
providers
– Cloud based access to devices
necessary
6LoWPAN KNX BACnet ZigBee
Device
Mgmt
IoT Enablement
Gateway
Internet
Uniform IoT Resource Access
› Decouple IoT level issues
from Device level issues– IoT resource abstraction
– Separate bindings for Device
Management vs. handling IoT
resources
› Provide normalization of M2M
device capabilities– Generic Device API framework
Gateway
Cloud
Remote DeviceManagement
OSGi TR-069OMA DM
IoT ServiceEnablement
CoAP HTTP
M2M SE
mId
IMS
ETSI 3rd M2M WS | 2012-07-11 | Page 8
–
› Avoid stove pipe profiles
› Go for simple profiles that are
application independent to
ensure interoperability– IPSO Application Framework
– OMA Lightweight Objects
› Allow adaptation to different
cloud environments– Native Embedded Web Services –
IETF CoRE
– ETSI M2M mId
– OMA DM and TR-069
UP
nP
Ad
ap
ter
Bo
njo
ur
Ad
ap
ter
Zig
Be
e
Ad
ap
ter
Z-w
ave
Ad
ap
ter
Blu
eto
oth
Ad
ap
ter
Generic Device API
AN
T+
Ad
ap
ter
TR-069
Connector
SDK
Connector
Co
AP
Ad
ap
ter
OMA DM
Connector
CoAP/OMA
Lightweight
CoAP/HTTP
Proxy
ETSI M2M
mId
Connector
Embedded Web in Smart Home Demo
› Smart Energy use case
› Heterogeneous device
integration
– CoAP sensors and actuators
– Z-Wave Smart Plugs
RD Social Web Of Things Apps
SWoT
Client
Cloud enablers
ETSI 3rd M2M WS | 2012-07-11 | Page 9
–
› Uniform device exposure
– REST via HTTP and CoAP
– IPSO Application Framework
› Supported:– CoAP
– HTTP-CoAP proxying
– Local caching and Observations
– Resource Directory Z-WAVE Smart Plugs, AEON LABS
Residential M2M Gateway
Linux
OSGi
Z-wave/CoAP
HTTP-CoAP Proxy
Resource Directory
CoAP Devices: STM32W Wireless MCU&Sensors,
Smart Plugs STEVAL-IHP004V1
Embedded Web in ETSI M2M Demo
mIdPOST Links
ETSI 3rd M2M WS | 2012-07-11 | Page 10
Street Lighting M2M App
CoAP CoAP CoAP
mIamIdPOST Links
Web Linking semantics end-to-end
ETSI 3rd M2M WS | 2012-07-11 | Page 11