Towards application development for the internet of things

Towards Application Development for

the Internet of Things*

Pankesh Patel

ABB Corporate Research, India

* This research work is partially done at University of Paris VI and French National Institute

for Research in Computer Science & Automation (INRIA), Paris, France

Growing number of ``things”

2

Temperature

sensors Fire

alarmsSmoke

detectors

Lights

Traffic

signals

Water

leakage

detector

Smart

phones

Parking space

controller

Air pollution

controllers

Structural

health

monitors

HVAC

system

Smart

car

Image credit: http://www.libelium.com/

http://www.libelium.com/

Internet of Things (IoT)

3

“A global networked infrastructure, linking physical and virtual things

through the exploitation of data capture and communication

capability.”

[CASAGRAS project] http://www.grifs-project.eu/data/File/CASAGRAS%20FinalReport%20(2).pdf

http://www.grifs-project.eu/data/File/CASAGRAS FinalReport (2).pdf

Examples

Road traffic monitoring & controlaims to maximize the flow of vehicle on the road

Personalized HVAC system

image credit to organizations, who own copyrights of used images

Goal

5

“Enable development** of IoT applications with

minimal effort by various stakeholders* involved in

development process”

**Development -- “a set of related activities that leads to a production of a software product.’’ [Ian Sommerville,

Software Engineering (9th edition) , 2010]

*Stakeholders in software engineering to mean – people, who are involved in the application development.

Examples of stakeholders defined in [Taylor et al., Software Architecture, 2009] are software designer,

developer, domain expert, technologist, etc.

Challenges

6

Heterogeneity

Types of devices (e.g., sensor, actuator, storage, processing elements, user interfaces)

Interaction modes (e.g., publish/subscribe, request/response, command, periodic)

Data types (e.g., date, number, time, string, Boolean)

Device properties (e.g., memory, processing constraint, mobile)

Protocols (e.g., MQTT, CoAP)

Platforms (e.g., Android, JavaSE)

Spreads into the application code, Makes

the portability of code difficult


7

Heterogeneity

Large number

Application logic in terms of

a set of distributed tasks for

hundreds

to thousands of devices

To reason at such levels of number is

impractical in general


Challenges

8

Heterogeneity

Large number

Multiple expertise

Knowledge from multiple

concerns intersect

Application domain

Software design

Algorithm design,

programming languages

Platform-specific

knowledge

Clear conflict with skill possessed by

the individual developer

Deployment

area


Challenges

9

Heterogeneity

Large number

Multiple expertise

Different life-cycle phases

Software development life cycle phases -- requirement analysis, design, implementation, testing, evolution

and maintenance [Ian Sommerville, Software Engineering (9th edition) , 2010]

Design: Application logic has to be analyzed and then

separated into a set of distributed tasks.

Implementations: Application has to be implemented

for heterogeneous platforms

Deployment: Tasks of an application have to be

decomposed in a (large) number of heterogeneous

devices.

Challenges

Existing approaches

10

Node-centric programming

Think in terms of activities of individual

devices & explicitly encode their

interactions with other devices.

Write a program that reads sensing data

from sensing devices, aggregates data

pertaining to the some external events,

decides where to send it addressed by

ID & communicates with actuators if

needed

Olympus with Gaia [Ranganathan et al., Percom, 2005], Context Toolkit [Dey

et al., HCI, 2001], TinyOS [Levis et al., MDM, 2006], Physical virtual mashup

[Guinard et al., NSS, 2010]


Existing approaches

11


Database approach

Queries to SN

Collects, aggregates, &

sends data to base station

Not flexible to introduce a

customized application logic.

Stakeholder

Base station

queries

collects

result

TinyDB [Madden et al., TODS ,2005], Semantic streams [Whitehouse et al., ,

EWSN, 2006], TinyREST [Luckenbach et al., REALWSN, 2005], TinySOA

[Aviles-Lopez , SOCA, 2009]

Existing approaches

12


Database approach

Macro-programming

Abstractions for high-level

collaborative behaviors

Lack of software engineering

methodology to support life

cycle phases – results in difficult

to maintain, reuse, and

platform-dependent design

Regiment [Newton et al., IPSN, 2007], MacroLab [Hnat et al.

, SenSys, 2008]


Existing approaches

13


Database approach

Macro-programming

Model-driven development

Vertical SoC – reduce app.

development complexity

separating PIM and PSM

Horizontal SoC – separate

different aspects of a system

Transformation and

code generators

PIM

PSM

E.g., J2SE E.g., .Net

PSM…

C1 C2 Cn…

Horizontal

Separation of

Concerns (SoC)

Vertical

separation of

concerns

ATaG [Pathak et al., DCSN, 2011], RuleCaster [Bischoff et al.,

EuroSSC, 2006], DiaSuite [Cassou et al., TSE, 2012], PervML

[Serral et al., Journal of Pervasive and Mobile computing, 2010],

Pantagruel [Drey et al., Percom, 2010]


Early contributions…

14

A comprehensive approach that utilizes advantages of existing MDD and

WSN macro-programming approaches, while focusing on ease of IoT

application development.

*It includes support programs, code libraries, high-level languages or other software that help stakeholders

to develop and glue together different components of a software product [Ian Sommerville, Software

Engineering (9th edition) , 2010].

Objectives:

Separate development into different concerns (reusability)

Integrate high-level modelling languages (reduce complexity & effort)

Automate development wherever possible (reduce effort)

Development framework*

Commonality

at various levels

15

Functionality(e.g., home

fire detection

Domain

(e.g., building

HVAC)

Deployment

Room

temperature

(e.g. building

automation)

Building fire

state

“Reusability

across concerns”

ABB- BTP

officeABB-Peenya

officeimage credit to organizations, who own copyrights of used images

Domain

16

Domain

Room

temperature

(e.g. building

automation)

Actuator

Sensor Storage

Concepts that are responsible

for interacting with EoI of a

domain

- Sensor, actuator, storage

Building fire

state


Functionality

17

Domain

Room

temperature

(e.g. building

automation)

FunctionalityHome fire

detectionBuilding

HVAC

Computational

service

Actuator

StorageSensor

Computational

service

responserequestpublish/

subscribeConcepts that are responsible for

- processing data and taking decisions

Building fire

state

command


Deployment

18

Domain

Room

temperature

(e.g. building

automation)

Functionality

Deployment

Device

Device

Device

Device Device

Building fire

state

Concepts to describe various

properties of devices

Actuator

Sensor Storage

Computational

service

Computational

service

responserequestpublish/

subscribe

Home fire

detectionBuilding

HVAC

command

ABB- BTP

officeABB-Peenya

officeimage credit to organizations, who own copyrights of used images

Modeling

languages

19

Domain

(e.g. building

automation)

Functionality

ABB- BTP

officeABB-Peenya

office

Deployment

Device

Device

Device

Device

Actuator

Sensor Storage

Computational

service

Computational

service

Home fire

detectionBuilding

HVAC

Vocabulary

Language (VL)

Architecture

Language

(AL)

Deployment

Language

(DL)


20

Hello world app in building automation: Personalized HVAC system

Badge

Reader

badgeDetected

badgeDisappeared

ProfileDB

profile

Proximity

Heater

off()

setTemp()

Temperature

Controller

Device

Device

Device

Device

Device


structs:

BadgeStruct

badgeID: String;

badgeEvent:String;

TempStruct

tempValue: double;

unitOfMeasurement: String;

resources:

sensors:

BadgeReader

generate badgeDetected: BadgeStruct;

generate badgeDisappeared: BadgeStruct;

actuators:

Heater

action Off();

action SetTemp(setTemp: TempStruct);

storages:

ProfileDB

generate profile: tempStruct accessed-by

badgeID: String;

21

Hello world app in building automation: Personalized HVAC system – vocabulary language

Badge

Reader

badgeDetected

badgeDisappeared

ProfileDB

profile

Proximity

Heater

off()

setTemp()

Temperature

Controller

Device

Device

Device

Device

Device

• Abstractions to specify heterogeneous

entities

• One entity description for many instances

computationalService:

Proximity

generate tempPref:TempStruct;

consume badgeDetected from region-hops:0:Room;

consume badgeDisappeared from region-hops:0:Room;

request profile;

partition-per:Room;

TemperatureController

consume tempPref from region-hops:0:Room;

command Off() to region-hops:0:Room;

command SetTemp(setTemp) to region-hops:0:Room;

partition-per:Room;

22

Hello world app in building automation: Personalized HVAC system – architecture language

Badge

Reader

ProfileDB

profile

Heater

off()

setTemp()

Device

Device

Device

Device

Device

Proximity

Temperature

Controller

Scope of

consuming dataScope of

Deployment

To reduce scale, devices can be grouped based on their

spatial relationship

- Cluster head is elected, responsible for processing

data of that cluster.

hops:0:Room

hops:0:Room

Room

Room

badgeDetected

badgeDisappeared

23

Hello world app in building automation: Personalized HVAC system – deployment language

Badge

Reader

ProfileDB

profile

Heater

off()

setTemp()

Device

Device

Device

Device

Device

Proximity

Temperature

Controller

badgeDetected

badgeDisappeared

Device1:

region:

Building:15 ;

Floor:11;

Room:1;

type:JavaSE;

resources: BadgeReader;

mobile: false;

Device2:

region:

Building:15 ;

Floor:11;

Room:1;

type: Android;

resources: Heater;

mobile: false;

Device3:

...

Type platform a

device runs on

Location of device

Property of a device

is specified individually – Not scalable.

Domain

concern

24

Domain

expert

Vocabulary

spec.

Compilation

of vocabulary

Domain expert (e.g. biologist, medical

system designer) understands domain

concepts.

Domain concepts

using vocabulary language

Badge

Reader

badgeDetected

badgeDisappeared

ProfileDB

profile

Proximity

Heater

off()

setTemp()

Temperature

Controller


Functional

concern

25

Domain

expert

Vocabulary

spec.

Compilation

of vocabulary

Architecture

spec.

Software designer

Software designer – understands

software architecture concepts,

Specifies computational components

using Architecture language

Badge

Reader

ProfileDB

profile

Heater

off()

setTemp()

Proximity

Temperature

Controller

badgeDetected

badgeDisappeared


Functional

concern

26

Domain

expert

Vocabulary

spec.

Compilation

of vocabulary

Architecture

spec. Compilation

of architectureApplication

developer

Architecture

frameworkSoftware designer

Application

logic

Architecture framework (in object-oriented GPL)

- Contains abstract classes

- Concrete methods

- Abstract methods


Implementing

application logic

27

Proximity

consume badgeDetected from region-hops:0:Room;

partition-per:Room;Compiler

generates

public void subscribeBadgeDetected() {

PubSubMiddleware.subscribe(this, “badgeDetected",

subscriptionCondition);

}

public void notifiedReceived (String event Name, Object arg,

Device deviceInfo) {

if (eventName.equals(“badgeDetected”) {

onBadgeDetectedEvent((BadgeStruct) arg) ;

}

}

public abstract void onBadgeDetectedEvent(BadgeStruct arg);

Concrete

method for

Subscription

request

Concrete

method for

Receiving

notifications

Application

developer

Structured code: Application Developer has to

locate methods to write application logic.


Deployment

concern

28

Vocabulary

spec.

Compilation

of vocabulary

Deployment

spec.

MapperNetwork

manager

Mapper – decides device where each computational

service will be executing

Mapping

files

Compilation


developer

Application

logic

Architecture


Domain

expert

Architecture

spec.

ParserMapping Algorithm

Code Generator

Deployment Spec.

Architecture Spec.

Mapping files

Mapper

Data structures

Mappingdecisions

image credit to organizations, who

own copyrights of used images

Deployment

concern

29

computationalService:

Proximity

…


…

Architecture

specification

devices:

Device1:

…

Device2:

…

DeviceN:

…

Deployment

Specification

Mapper

Device1:

Proximity

Device2:


Mapping decision

(output in GPL)

Mapping decision

(output in GPL)

Platform

concern

30

Vocabulary

spec.

Compilation

of vocabulary

Device

developerDevice driver

Deployment

spec.

MapperNetwork

manager

Mapping

files

Compilation


developer

Application

logic

Architecture


• Device developer – understands

inputs/outputs, protocols of

device platform

Vocabulary Framework

• Abstract classes with concrete

methods, interfaces

Device Driver

Sensing/actuating

framework

Vocabulary

frameworkDomain

expert

Architecture

spec.



Implementing

device driver

31

public interface IBadgeReader {

public BadgeStruct getBadgeDetectedEvent();

public void getBadgeDetectedEvent(ListenerBadgeDetected handler);

}

Compiler

generates

BadgeReader

generate badgeDetected: BadgeStruct;

public class JavaSEBadgeReader implements IBadgeReader {

@Override

public BadgeStruct getBadgeDetectedEvent() {

// TODO: Write Device Driver

}

@Override

public void getBadgeDetectedEvent(ListenerBadgeDetected handler) {

// TODO: Write Device Driver

}

}

Device

developer

implements

interfaces



Linking

32

Domain

expert

Vocabulary

spec.

Compilation

of vocabulary

Architecture

spec. Compilation

of architecture

Deployment

spec.

Mapper

Application

developer

Application

logic

Architecture


Network

manager

Linker

Android

devices

PC

PC

Mapping

files

Combines and packs the code generated by

various stages into packages that can be

deployed on devices.

Generated code

For Device X

Middleware

Device

developerDevice driver

Vocabulary

framework

Device Driver

Sensing/actuating

framework

Middleware

Wrapper



Evaluation

33

Development effort: the effort required to create a new application.

Reusability: the extend to which software artifacts can be reused during application development.

Expressiveness: the characteristics of IoT applications that can be modeled using our approach.

Technological change support: it indicates the support provided by the approach to change the implementation platform or programming language.

While the lines of code metric is useful, a number of limitations have been noted. It depends heavily on programming

languages, styles, and stakeholder’s skills. In view of this, we have combined one of well-known metrics – Code coverage (it

defines code which is actually executed, thus it show usefulness of the generated code), with LoC.

Example: Home automation

34

Motion sensor to detect the presence of a

moving object

Stove to sense if it is turned on/off

Badge

reader

Smoke

Detector

Fire

alarmHeater

Data

storage

Temperature

sensor

Room 2(bedroom)

Room 1 (Kitchen) Room 3

(MeetingRoom)

Application1: Personalized HVAC in Bedroom

35

Badge

Reader

badgeDetected

badgeDisappeared

ProfileDB

profile

Proximity

Heater

off()

setTemp()

Temperature

Controller

Device1 Device2

Device3

Device4

Device5

• 5 entities communicating

over MQTT* protocol

*MQTT (Message Queue Telemetry Transport) is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport.

• 5 devices simulated on

a single PC.

Aim: To demonstrate automation provided by

our approach.

Entities Name Platform

Sensor Badge

Reader

Android

(Simulated)

Storage ProfileDB MySQL

Server

Computation Proximity -

Temperature

Controller

-

Actuator Heater JavaSE

(Simulated)

Results…

Lines of code using Metrics 1.3.6 Eclipse plug-in.

Code Coverage using EclEmma Eclipse plug-in

• While considering code coverage, we wanted to measure code coverage of the generated code ,

not application logic, written by Application developer, and device driver, written by Device developer.

• Lines of Device driver code vary

from one platform to other

platform.

• Lines of application logic code

depend on functionalities.

• The other portion of code is unused features (e.g., getters, setters, exception handling, etc.),

which was not executed during experiments.

LoC Wriiten

by

Stakeholder

16%

Application

specific

generated LoC

63%

Provided

Wrapper with

Runtime

System LoC

21%

Code Coverage: 84%

37


moving object


Badge

reader

Smoke

Detector

Fire

alarmHeater

Data

storage

Temperature

sensor

Room 2(bedroom)


(MeetingRoom)

Implement “Fire Mgmt.”

application

Application2: Fire Mgmt.

Application2:

Fire Mgmt.

38

Smoke

Detector

smoke

Presence

Temperature

Sensor

temperature

Measurement

Calculate

AvgTemp

FireState

Measurement

Fire

Controller

Alarm

activate()

deactivate()

Device2Device1

Device3

Device4

Device5

Device6

6 entities communicating

over MQTT protocol.

6 devices simulated on a

single PC.


Sensor Smoke

Detector

JavaSE

(Simulated)

Temperature

Sensor

JavaSE

(Simulated)

Computation CalculateAvgTemp -

FireState

Measurement

-

FireController

Actuator Alarm JavaSE

(Simulated)

Results…

39

• Device driver code varies from one platform to other platform.

• Lines of application logic code depend on functionalities.

LoC Wriiten

by

Stakeholder

17%

Application specific

generated LoC

64%

Provided

Wrapper

with

Runtime

System LoC

19%

Code Coverage: 82%

Implementing Fire Mgmt. Application

40


moving object


Badge

reader

Smoke

Detector

Fire

alarmHeater

Data

storage

Temperature

sensor

Room 2(bedroom)


(MeetingRoom)

Implement “Fire Mgmt.”

application in Room (1-3)

0

20

40

60

80

100

120

Fire detection (in

bedroom)

Fire detection (in

kitchen)

Fire detection (in

meeting room)

Lin

es

of

Co

de

Applications

Vocab. Spec. Arch. Spec. Deploy. Spec. Device Driver Application logic

Reusability

41We are assuming that device platforms remain same across deployment.

Evaluating Reusability…

42


moving object


Badge

reader

Smoke

Detector

Fire

alarmHeater

Data

storage

Temperature

sensor

Room 2(bedroom)


(MeetingRoom)

Turned on the alarm if the stove is switched on and

when no body in the kitchen – Safety in Kitchen

Manage the heating of the meeting room,

depending on the room’s temperature, when room

is occupied unexpectedly.

1

2

Applications

43

Stove

Temp

Measurement

Motion

Sensor

motion

Presence

Kitchen

State

Alarm

Activate()

Kitchen

Controller

Temperature

Sensor

Temp

Measurement

Motion

Sensor

motion

Presence

Avg

Temperature

Room

Occupancy

Heat

Regulation

Heater

SetTemp()

Heat

Controller

Safety in Kitchen

Heating control system

in Meeting room

Turned on the alarm if the stove is switched on and

when no body in the kitchen – Safety in Kitchen

Manage the heating of the meeting room,

depending on the room’s temperature, when room

is occupied unexpectedly.

12

Reusability

44 We are assuming that device platforms remain same across deployment. For simplicity, we are assuming that

one device hosts only one entity.

Application: Road traffic monitoring & control

45

• Ramp metering: It influences traffic by controlling access to the highway.

One of the techniques to control traffic:

Image credit: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.147.3471&rep=rep1&type=pdf

Usually, this kind of system is divided into disjoint sectors, with each sector usually being controlled depending

on the current status of the sector.

• Speed sensors to measure and report the speeds of vehicles.

• Presence sensors to measure and report the presence of vehicles.

• Ramp signals designed to allow or disallow cars onto the highways.

http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.147.3471&rep=rep1&type=pdf

Experiment

setup

46

Speed

sensor

Speed

Measurement

Presence

sensor

Presence

Measurement

Calculate

AvgSpeed

Calculate

AvgQueueLength

RampSignal

Controller

Ramp

Signal

signal()


Sensor Speed

Sensor

JavaSE (Simulated)

Presence

Sensor

JavaSE

(Simulated)

Computation Calculate

AvgSpeed

-

Calculate

AvgLength

-

RampSignal

Controller

-

Actuator Ramp

Signal

JavaSE

(Simulated)hops:0:Sector

Sector Sector

Sector

hops:0:Sector

hops:0:Sector hops:0:Sector

hops:0:Sector

Entities communicating over MQTT

protocol

Devices simulated on a single PC.

Results: large number

47 • Lines of Device driver code vary from one platform to other platform.

• Lines of application logic code depend on functionalities.

0

20

40

60

80

100

120

140

160

6 8 10 12 14 18 24

Lin

es

of

C

od

e

Number of Devices

Vocab. Spec. Arch. Spec. Deploy. Spec. Device Driver Application logic

Expressiveness…

48All application code is available on URL: https://github.com/pankeshlinux

Many solutions exist for developing software in specific application domains (for example HomeOS). Our approach’s

applicability is extended to beyond this particular context. Our approach is not limited to one particular domain. It can be

applied to various other domain as well.

App.

Name

Behaviors Components Platforms Runtime

System

Interaction

Modes

Topology Network

Size

Personalized

HVAC

SCC

loop

Sensor, Storage,

Computational,

Actuator

JavaSE,

Android

MQTT Event-driven,

Req.-Resp.,

Command

Static 5

Fire

Detection

SCC

loop

Sensor,

Computational,

Actuator

JavaSE, MQTT Event-driven,

Periodic,

Command

Static 8

Safety

In Kitchen

SCC

loop

Sensor,

Computational,

Actuator

JavaSE,

Android

iBICOOP Event-driven,

Periodic,

Command

Static 5

Collecting

Avg. Temp. of

Building

Regular

data

collection

Sensor,

Computational,

User Interface

JavaSE, MQTT Periodic,

Command

Static 16

Road Traffic

Monitoring &

Control

SCC

loop

Sensor,

Computational,

Actuator

JavaSE, MQTT Event-driven,

Periodic,

Command

Static 24

https://github.com/pankeshlinux

Technological change support (1/2)

6/26/201549

Vocabulary

Spec.

Architecture

spec.

Deployment

spec.

Code generator

…

Android

Plug-in

JavaSE

Plug-in

Data

Structures

Parser

JavaSE

files

Android

files

Others

Others

Implemented in ANTLR,

a parser generator from

grammar description

StringTemplateEngine,

a template engine for

generating source code

the system to be specified

independently of the platform

Technological change support (2/2)

6/26/201550

Generated code

For Device X

Runtime

System

Middleware

Wrapper

Middleware runs on each individual device and provides a

support for executing distributed tasks.

Wrapper plugs “generated code for a device” and

middleware. It implements interfaces, specified in a

support library, specific to a middleware.

The linker produces generated code for a device.

Device Wrapper for MQTT middleware is available at URL:

https://github.com/pankeshlinux/IoTSuite-TemplateV2

• Wrapper for iBICOOP middleware is available at URL:

https://github.com/pankeshlinux/ToolSuite

https://github.com/pankeshlinux/IoTSuite-TemplateV2

https://github.com/pankeshlinux/ToolSuite

Summary & future work

51

Application development challenges

Heterogeneity, large number, multiple expertise, different life-cycle phases

Existing approaches

Node-centric programming, database, macro programming, MDD

Our approach

Separation of concerns, modeling languages, automation, development framework

Early results: reduce development effort

Future work

Short term goals:

Integration of cloud-based deployment, integration of CoAPruntime system (targeted for small low power sensors, switches, valves, etc.)

Long term-goals:

Supporting testing phase, mapping algorithm, runtime adoption

52

Thanks!

Email:

[email protected]

Implementation of this work with documentations,

running on both Android and JavaSE device and MQTT

runtime system

https://github.com/pankeshlinux/IoTSuite/wiki

mailto:[email protected]

https://github.com/pankeshlinux/IoTSuite/wiki

State of the art in IoT Application

Development

53

Comparison* of our approach with state of the art in IoT

application development on various dimensions.

*This work is submitted to GPCE 2015.

Towards application development for the internet of things

Documents

Transcript of Towards application development for the internet of things