Smart M2M gateway based architecture for m2m device and endpoint management

Smart M2M Gateway based Architecture for M2M Device and Endpoint Management

Soumya Kanti Datta

Research Engineer, EURECOM, France

Email: [email protected]

IEEE International Conference on Internet of Things

(iThings 2014)

Outline

• Introduction

• IoT architecture to manage M2M devices

• M2M device configuration management

• Interaction using a mobile client

• Implementation of Lightweight FI-WARE Generic Enablers

• Performance evaluation

• Conclusion

01-Sept-14 Smart M2M Gateway based Architecture for M2M Device and Endpoint Management 2

Introduction


• Managing the huge volume of M2M devices facilitates

– Discovery of M2M devices and services

– Easy access for end users

– High mobility

M2M Gateway Based Management

• Why M2M gateway – Settles the heterogeneity between M2M devices and

internet – Things do not have the capability to connect to the Internet

on their own – Gateway is indispensable to connect legacy things and

things in Smart Home domain

• We propose – M2M gateway based device and endpoint management – Lightweight CoRE Link based description – SenML based metadata exchange [1]


[1] Datta, Soumya Kanti; Bonnet, Christian; Nikaein, Navid, "CCT: Connect and Control Things: A novel mobile application to manage M2M devices and endpoints," Intelligent Sensors, Sensor Networks and Information Processing (ISSNIP), 2014 IEEE Ninth International Conference on , pp.1,6, 21-24 April 2014

Outline

• Introduction






• Conclusion


ETSI based IoT Architecture


Outline

• Introduction






• Conclusion


CoRE Link Based Function Set

Function Set Root Path Resource Type

Device /d wg.dev

Endpoint /e wg.endpoint

Unit /unit wg.senml.unit

Configuration /cf wg.config


M2M 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

Endpoint /d/end wg.dev.endpoint p

destination /d/dst wg.dev.destination p

proxy-out [2] /d/po wg.dev.proxy-out rp

proxy-in [2] /d/pi wg.dev.proxy-in rp


[2] 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 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

senml /e/senml wg.endpoint.senml rp


Unit Resource Description


Type Path RT IF

Unit /unit/{senml.unit} wg.senml.unit rp

ui-graphical /unit/{senml.unit}/gr wg.senml.gr rp

allowed-range

/unit/{senml.unit}/ar wg.senml.ar rp

allowed-list /unit/{senml.unit}/al wg.senml.al rp

Configuration Resource Description

• The configuration file can be created and/or updated from the mobile clients.

• Access to the resources is restricted to authorized clients as determined by the access rights.


Type Path RT IF

Device /cf/d wg.dev p

Endpoint /cf/e wg.endpoint p

Unit /cf/unit wg.unit p

Outline

• Introduction






• Conclusion


Example Scenario


• CoRE Link based descriptions – Pushed to the south

interface of the gateway.

– Locally stored.

• Mobile client – Issues a GET request to

north interface of the gateway.

– Gateway responds with the M2M device and endpoint configurations.

Retrieving M2M Device Configurations


Retrieving M2M Endpoint Configuration

User selects the “Device 2” which queries for the configuration of its endpoints


Note: “xif” is an interface definition introduced by us to differentiate between different types of endpoints like sensors (s), actuators (a), RFID tag (r) and transducers (t).

Unit Resource Description


• Note: – Range of operation is 10 to 30 degree Celsius.

– Sensor measurement is represented by a slider.

• This drives the UI components of the mobile device from the M2M gateway.

Updating Configuration at M2M Gateway

• Consider the “location” attribute is empty.

• It can be updated from mobile clients – “Building-A” in this case

– Done using HTTP POST

• Only a some of the attributes can be updated – Location, name, proxy


Outline

• Introduction






• Conclusion


FI-WARE Generic Enablers

• FI-WARE is an initiative that provides an open cloud-based infrastructure to

– Create and deliver cost-effective applications and services for future internet.

– Build Generic Enablers (GE) for IoT service enablement.

• Generic Enablers

– Allow physical things to be available, searchable, accessible and usable by high level applications.

– Consists of a set of functionalities, APIs and interoperable interfaces compliant with open specifications.


IoT Gateway and Backend GEs

• IoT Gateway GE – Provides inter-networking, protocol conversion &

network traffic optimization for IoT backend.

– Implements CoRE Link based Description APIs.

– Additional capabilities • Gateway based M2M device discovery.

• Integration of legacy endpoints into the IoT ecosystem.

• IoT Backend GE – Typically addresses domain specific applications.

• Enables Android application to provide M2M services to end-users.


Data/Context Management GEs

• Generate M2M data – Combine sensor measurement with additional

data e.g. unit, type, id, name, version and timestamp to create metadata.

• Collect context information – Timestamp and location of M2M devices.

• Generate new information – Semantic reasoning on the M2M data to generate

it’s meaning. [3]


[3] Gyrard, A.; Bonnet, C.; Boudaoud, K., "Enrich machine-to-machine data with semantic web technologies for cross-domain applications," Internet of Things (WF-IoT), 2014 IEEE World Forum on, pp.559,564, 6-8 March 2014

Interface to Networks and Devices (I2ND) Architecture GEs

• Connected Device Interface (CDI) GE – It equips the mobile clients with real time and remote access to M2M

devices and endpoints.

– Implemented as the mobile application “Connect and Control Things”.

• Service Capability, Connectivity and Control (S3C) GE – Runs in Service Capabilities Layer (SCL) and offers

• Self-adaptive framework for battery and context aware mobile application development. [4]

• Framework to optimize the mobile application development using cross platform tools. [5]

• API for dynamic M2M device discovery.

• Ecosystem of mobile applications to serve different IoT domains (under development)


[4] Soumya Kanti Datta, Christian Bonnet, Navid Nikaein, "Self-Adaptive Battery and Context Aware Mobile Application Development", in 10th IEEE International Wireless Communication and Mobile Computing Conference, August 4-8, 2014, Cyprus. [5] Dalmasso, I; Datta, S.K.; Bonnet, C.; Nikaein, N., "Survey, comparison and evaluation of cross platform mobile application development tools," Wireless Communications and Mobile Computing Conference (IWCMC), 2013 9th International , vol., no., pp.323,328, 1-5 July 2013

Outline

• Introduction






• Conclusion


Performance Evaluation

• Addressing the scalability issue with huge volume of M2M devices and endpoints

• Size of configuration file < 1KB.

– M2M gateway with internal memory 10MB can store and manage 10,000 configuration files.

• The presented concept can be utilized in

– Smart Home, Healthcare domain etc.


Outline

• Introduction






• Conclusion


Conclusion

• CoRE Link Format based lightweight description

• Internal structure of the M2M gateway, web services, APIs and interactions

• ETSI compliant architecture

• Lightweight implementation of FI-WARE Generic enablers




Q/A

• Email: [email protected]

• Publication repository: http://www.eurecom.fr/en/people/datta-soumya-kanti/publications


mailto:[email protected]



http://www.eurecom.fr/en/people/datta-soumya-kanti/publications





Technology

Smart M2M gateway based architecture for m2m device and endpoint management