embedded devices on the internet of things
Post on 28-Jan-2015
121 Views
Preview:
DESCRIPTION
TRANSCRIPT
Zach Shelby, SensinodeJan Höller, Ericsson
Embedded devices on theInternet of Things
ETSI 3rd M2M WS | 2012-07-11 | Page 2
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
› 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
ETSI 3rd M2M WS | 2012-07-11 | Page 3
What is “constrained”
Low Bandwidth
Scaling Networks
Battery Powered
Low Cost
LimitedProcessing
ETSI 3rd M2M WS | 2012-07-11 | Page 4
Constrained but still Internet
› Today - a complete IP based Web stack can be run on small devices with microcontrollers
IEEE 802.15.4
PLC DECTBTLE
IPv6
UDP
CoAP
Resources
6LoWPAN
/temp /light /switchInternet
48 kB of Flash 8 kB of RAM
ETSI 3rd M2M WS | 2012-07-11 | Page 5
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
› Application Semantics– IPSO Application
Framework– OMA Lightweight
M2M Objects
ETSI 3rd M2M WS | 2012-07-11 | Page 6
Embedded Web in M2M Standards
IP and Web
Web & Mobile Apps
SE2.0
IP Router
OMA Lightweight
CoAP
HTTP
CoAP
HTTP
ETSI 3rd M2M WS | 2012-07-11 | Page 7
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– 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
DeviceMgmt
IoT Enablement
Gateway
IoTMgmt
Internet
Surveillance
Energy Mgmt
HVAC Ctrl
Access Ctrl
ApplicationsService Providers
ETSI 3rd M2M WS | 2012-07-11 | Page 8
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
› 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
Gateway
UP
nP
A
da
pte
r
Bo
njo
ur
Ad
ap
ter
Zig
Be
eA
da
pte
r
Z-w
av
e
Ad
ap
ter
Blu
eto
oth
Ad
ap
ter
Generic Device API
AN
T+
Ad
ap
ter
TR-069Connector
Cloud
Remote DeviceManagement
OSGi TR-069
SDKConnector
Co
AP
Ad
ap
ter
OMA DMConnector
OMA DM
CoAP/OMALightweight
IoT ServiceEnablement
CoAP HTTP
CoAP/HTTPProxy
ETSI M2MmId
Connector
M2M SE
mId
IMS
ETSI 3rd M2M WS | 2012-07-11 | Page 9
Embedded Web in Smart Home Demo
› Smart Energy use case
› Heterogeneous device integration
– CoAP sensors and actuators– Z-Wave Smart Plugs
› Uniform device exposure– REST via HTTP and CoAP– IPSO Application Framework
› Supported:– CoAP
– HTTP-CoAP proxying
– Local caching and Observations
– Resource DirectoryZ-WAVE Smart Plugs, AEON LABS
Residential M2M Gateway
Linux
OSGi
Z-wave/CoAP
HTTP-CoAP Proxy
Resource Directory
RDSocial Web Of Things
Apps
SWoT Client
Cloud enablers
CoAP Devices: STM32W Wireless MCU&Sensors, Smart Plugs STEVAL-IHP004V1
ETSI 3rd M2M WS | 2012-07-11 | Page 10
Embedded Web in ETSI M2M Demo
Street Lighting M2M App
CoAP CoAP CoAP
mIamIdPOST Links
Web Linking semantics end-to-end
ETSI 3rd M2M WS | 2012-07-11 | Page 11
top related