an iot gateway centric architecture to provide novel m2m services

An IoT Gateway Centric Architecture to Provide Novel M2M

Services Soumya Kanti Datta

Research Engineer

EURECOM, France

Email: [email protected]

IEEE World Forum on Internet

of Things (WF-IoT 2014)

Contents

• Introduction

– M2M & IoT

– Key Elements

– Sensor Markup Language

• Proposed IoT Architecture

• Prototype Implementation

• Conclusion

8-Mar-14 An IoT Gateway Centric Architecture to Provide Novel M2M Services 2

Introduction


M2M Communication

• Communication between two or more entities that do not necessarily need any direct human intervention [ETSI].

• Information exchange between a Subscriber station and a Server in the core network (through a base station) or between Subscriber station, which may be carried out without any human interaction [IEEE 802.16p].

IoT

• A global network infrastructure, linking physical and virtual objects through the exploitation of data capture and communication capabilities [EU FP7 CASAGRAS].

• A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on, existing and evolving, interoperable information and communication technologies [ITU-T Y.2060]

Key M2M Elements


Internet of Things (IoT)

• To achieve the IoT – Things need to be connected to software

– Things need to be made available to be used together as a system

• M2M architecture and protocols address the first item

• Second item is a challenge


Sensor Markup Language (SenML)

• Represents simple sensor measurements and device parameters.

• Implemented using JSON/XML/EXI.


Source: Media Types for Sensor Markup Language (SENML) draft-jennings-senml-10

Contents

• Introduction


– M2M Devices and Endpoints

– Wireless Gateway

– Mobile Application

– Novel Services


• Conclusion


Gateway Centric IoT Architecture


M2M Devices and Endpoints

• Smart M2M Device

– Interface of this device allows sensor metadata to be read by GET request.

• Legacy device

– Sends sensor measurement to proxy-in of WG or Intermediate Sensor Gateway (ISG) over Modbus.

– Proxy-in or ISG creates metadata

• SenML is used to represent metadata


Wireless Gateway

• Backbone of the architecture

• Designed and implemented as a web application based on REST paradigm

• Web services are categorised into two interfaces

– North

– South


North Interface


Device and Endpoint Discovery

• Clients do not have any information on the M2M devices and endpoints initially.

• Clients establish a connection to WG to retrieve a list of connected devices and endpoints.

• The list is maintained in a local database.

• Addition or removal of devices and endpoints automatically updates the local database.

• Clients also learn about actuator capabilities.

North Interface


Reporting sensor metadata

• After discovery phase, client selects sensors.

• A GET request is sent to WG to retrieve the metadata

South Interface


Proxy-in

• M2M device is actually connected to a proxy-in which registers the device.

• It facilitates real time interaction between the clients and sensors.

• Proxy-in collects sensor metadata either using a GET request or getting a push notification from the M2M device itself.

Proxy-out

• It links clients with actuators.

• The proxy-out receives the URI of actuator.

• There is a protocol that translates the HTTP payload into M2M device specific command which the actuator will understand.

Provision for Actuator

• Novel aspect: extension of SenML Capabilities. • We have added the following

– Interface definition to differentiate between sensor and actuator

– Type – Supported functionalities

• For light – on, off and dim

– Allowed range of values • Could be discreet or continuous

– Unit – Location

• Destination URI of the actuator


Mobile Application

• Performs the following

– Dynamic discovery of M2M devices and endpoints

– Receive and display sensor measurements

– Control actuators


Contents

• Introduction



– Android application

– Wireless Gateway

– Use cases

• Conclusion


Prototype Implementation

• Mobile application Connect and Control Things (CCT)

– developed using cross platform tools PhoneGap 2.9.0 and JQuery Mobile 1.3.1.

• Wireless gateway is running in a Google App Engine

• Tested with real and simulated M2M devices and Endpoints


CCT


Simulated Sensors


Use case with a sensor


Use case with an actuator


PUSH Notification


Contents

• Introduction



• Conclusion


Conclusion

• Attempt to integrate endpoints with web services.

• Extended SenML capabilities to control actuators.

• Connect & control both smart & legacy devices.

• The system provides an incremental methodology to add new services and functionalities.

• Future direction

– Access rights for multiple users

– Security & privacy concerns


Requesting actuator update

Req PUT /proxyout1.mydomain.com/dev1.mynetwork.net

<senml bn=urn:dev:mac:6399877>

<e n="temp" t="0" v=“20" u="Cel" xbif=“a”/>

</senml>

Resp 204 No Content.

26 4/7/2015

an iot gateway centric architecture to provide novel m2m services

Technology

iot architecture m2m

system m2m architecture

iot things

internet of things iot

key m2m elements

advanced services

internet of things wfiot

wireless gateway backbone