a lightweight framework for efficient m2m device management in onem2m architecture

A Lightweight Framework for Efficient M2M A Lightweight Framework for Efficient M2M A Lightweight Framework for Efficient M2M A Lightweight Framework for Efficient M2M Device Management Device Management Device Management Device Management in oneM2M Architecturein oneM2M Architecturein oneM2M Architecturein oneM2M Architecture

Soumya Kanti Datta

Research Engineer, EURECOM, France

Email: [email protected]

IEEE Tenth International Conference on Intelligent Sensors, IEEE Tenth International Conference on Intelligent Sensors, IEEE Tenth International Conference on Intelligent Sensors, IEEE Tenth International Conference on Intelligent Sensors, Sensor NetworksSensor NetworksSensor NetworksSensor Networks and Information Processing (ISSNIP 2015)and Information Processing (ISSNIP 2015)and Information Processing (ISSNIP 2015)and Information Processing (ISSNIP 2015)

&&&&First International ConferenceFirst International ConferenceFirst International ConferenceFirst International Conference on Recent Advances in Internet of on Recent Advances in Internet of on Recent Advances in Internet of on Recent Advances in Internet of

Things (RIoT 2015)Things (RIoT 2015)Things (RIoT 2015)Things (RIoT 2015)

RoadmapRoadmapRoadmapRoadmap

• Introduction

– Connecting things to the Internet

– Challenges for M2M device management

• State-of-the-art

• M2M device & endpoint description

• Management framework

• Integration into oneM2M architecture

• Conclusion

07-Apr-15 A Lightweight Framework for Efficient M2M Device Management in oneM2M Architecture 2

Connecting ThingsConnecting ThingsConnecting ThingsConnecting Things

07-Apr-15 A Lightweight Framework for Efficient M2M Device Management in oneM2M Architecture

Source: http://www.itworld.com/

Source: Roberto Minerva, “From M2M to Virtual Continuum”,ICCE 2015, Las Vegas

3

Volume of Connected ThingsVolume of Connected ThingsVolume of Connected ThingsVolume of Connected Things


Challenges and RequirementsChallenges and RequirementsChallenges and RequirementsChallenges and Requirements

• Heterogeneity of things – Communication technology

• Bluetooth Smart, Zigbee, NFC, Modbus

– Measurement capabilities• Temperature, luminosity, precipitation

– Types of data generated • Numerical, audio, video

• High mobility

• Access control for end users

• Underlying network topology

• Automatic configuration management

• Lack of uniform description of M2M devices

• Managing legacy devices

• Ease of adding and deleting M2M device descriptions



• Introduction


– Limitations




• Conclusion


Limitations in StateLimitations in StateLimitations in StateLimitations in State----ofofofof----thethethethe----artartartart

• Lack of efficient M2M device management

framework.

– Tackled by OMA LwM2M Technical Specifications.

• Integration of such a framework in a standard

IoT architecture.

• Lightweight description of M2M devices and

endpoints for management.

– Tackled by CoRE Link Format.



• Introduction



– Utilizing CoRE Link Format



• Conclusion


Lightweight Description of M2M DevicesLightweight Description of M2M DevicesLightweight Description of M2M DevicesLightweight Description of M2M Devices

• Key for an efficient and scalable M2M device management framework.

• Utilized CoRE Link Format for the descriptions.

• Extending same description to legacy devices

– Connected to an intermediate gateway (IG) or proxy.

– It creates the configuration on behalf of legacy device.

• Advantages

– Settles the heterogeneity of devices

– Promotes interoperability among other components of IoT architecture

• Software implementation is done using JSON.


M2M Device Resource DescriptionM2M Device Resource DescriptionM2M Device Resource DescriptionM2M Device Resource Description


Type Path RT IF

Location /d/loc ipso.loc.gps / ipso.loc.xy /

ipso.loc.sem

p

id /d/id wg.dev.id rp

Name /d/n wg.dev.name p

Model /d/mdl wg.dev.model p

destination /d/dst wg.dev.destination p

Lifetime /d/lft wg.dev.lifetime p

proxy-out * /d/po wg.dev.proxy-out rp

proxy-in * /d/pi wg.dev.proxy-in rp

10

* Datta, S.K.; Bonnet, C.; Nikaein, N., "An IoT gateway centric architecture to provide novel M2M services," Internet of Things (WF-

IoT), 2014 IEEE World Forum on , vol., no., pp.514,519, 6-8 March 2014.

M2M Endpoint Resource DescriptionM2M Endpoint Resource DescriptionM2M Endpoint Resource DescriptionM2M Endpoint Resource Description


Type Path RT IF

id /e/id wg.endpoint.id rp

name /e/n wg.endpoint.name p

device /e/d wg.endpoint.device p

11

Source: Datta, S.K.; Bonnet, C., "Smart M2M Gateway Based Architecture for M2M Device and Endpoint Management," Internet of

Things(iThings), 2014 IEEE International Conference on, and Green Computing and Communications (GreenCom), IEEE and Cyber,

Physical and Social Computing(CPSCom), IEEE , vol., no., pp.61,68, 1-3 Sept. 2014

Configuration Resource DescriptionConfiguration Resource DescriptionConfiguration Resource DescriptionConfiguration Resource Description

• Exposes device and endpoint resources to the

end user for the purpose of updating them.


Type Path RT IF

Device /cf/d wg.dev p

Endpoint /cf/e wg.endpoint p

12


• Introduction




– Architecture

– Phases of operation


• Conclusion


Management FrameworkManagement FrameworkManagement FrameworkManagement Framework


• Objective: Ensuring flexibility, scalability and dynamicity

• Already developed solutions

– Representation of objects for efficient management

• Both smart and legacy ones

– Framework for connected device management

– OMA LwM2M Technical Specifications based APIs

– Entire framework is implemented using RESTful web services.

• Work under progress

– Automatic discovery of devices

14

Management FrameworkManagement FrameworkManagement FrameworkManagement Framework


Proxy LayerProxy LayerProxy LayerProxy Layer

• Unique & novel aspect

– Allow management of legacy M2M devices.

• Current standardization efforts do not consider such scenarios but

inclusion of legacy devices into IoT ecosystems is crucial.

• The proxy layer is composed of two RESTful web services –

– Proxy-in to manage legacy sensors

– Proxy-out to manage legacy actuators.

• The proxy layer creates the CoRE Link based configurations and is

responsible for registering and un-registering legacy devices.

• The proxies are not dependent on the communication protocol

used by the legacy devices.


Configuration Storage LayerConfiguration Storage LayerConfiguration Storage LayerConfiguration Storage Layer

• Contains a database to store configurations.

• Translates CoRE Link format to storage format.

• Keeps track of configuration “lifetime”

– Enables self-management


Service Enablement LayerService Enablement LayerService Enablement LayerService Enablement Layer

• Allows the end users to

– Read, write & update configurations

– Enable device discovery

– Receive notification

– Implement proper access control.

• These capabilities correspond to OMA LwM2M Technical Specifications

• Advantage

– Allow remote management of M2M devices from mobile devices of end users.


Management Framework Deployment ScenariosManagement Framework Deployment ScenariosManagement Framework Deployment ScenariosManagement Framework Deployment Scenarios

• Cloud based– For huge volume of objects deployed in a smart city

• M2M gateway based– Large enterprise consisting of hundreds of smart and

legacy objects

– Smart home with dozens of such objects

• Mobile application based– Smart home with limited number of objects can utilize a

smartphone/tablet to manage them

– Interaction over a personal area network

– Needs ultra lightweight implementation of the framework


Different Phases of OperationDifferent Phases of OperationDifferent Phases of OperationDifferent Phases of Operation

• Registration phase

– Registration of objects to the framework

• Service enablement phase

– Allows end users to discover configurations

– Configuration(s) update

– End user notification

• Un-registration phase


Registration PhaseRegistration PhaseRegistration PhaseRegistration Phase


SelfSelfSelfSelf----Management of M2M DevicesManagement of M2M DevicesManagement of M2M DevicesManagement of M2M Devices

• Necessary to manage mobile devices.

• Based on a lifetime attribute

– Each device must announce itself or update its

configuration once during the lifetime.

– Otherwise the framework removes the

configuration.

– Value can be defined/modified by developers.



• Introduction





• Conclusion


Integration into oneM2M ArchitectureIntegration into oneM2M ArchitectureIntegration into oneM2M ArchitectureIntegration into oneM2M Architecture



• Introduction





• Conclusion


ConclusionConclusionConclusionConclusion

• Contributions– M2M device management framework

• Can be deployed at a cloud system, M2M gateway and smartphones.

– CoRE Link Format based description of both smart and legacy devices.

– Management of both the smart and legacy M2M devices.

– Utilization of OMA LwM2M based M2M service enablement for end users.

– integration of the entire functionalities and the framework into oneM2M architecture.


Q/AQ/AQ/AQ/A

• Email: [email protected]

• Telephone: +33658194342

• Twitter: @skdatta2010

• Webpage: http://www.eurecom.fr/en/people/datta-

soumya-kanti


a lightweight framework for efficient m2m device management in onem2m architecture

Technology

lightweight framework

m2m device descriptions07

onem2m architecturesource

internet of things

information processing

intelligent sensors

recent advances

internet challenges