Unit 2: Iot Design Methodology: Dept. of Computer Science & Engineering

Dept.
of Computer Science &

Engineering.
Unit 2 : IoT Design Methodology

PLD
Internet of Thnigs by Amol Dande 1

Dept. of Computer Science &
Engineering.
 M2M
 Differences and Similarities between M2M and IoT
 SDN and NFV for IoT
 IoT Platforms Design Methodology
 IoT Design Methodology that includes:

 Purpose & Requirements Specification
 Process Specification PLD
 Domain Model Specification
 Information Model Specification
 Service Specifications
 IoT Level Specification
 Functional View Specification
 Operational View Specification
 Device & Component Integration
 Application Development

Engineering.
Introduction to M2M
 Communication between machines or devices with computing

and communication facilities.
PLD
 Free of any human intervention
 Similar to Industrial Supervisory Control & Data Acquisition
systems (SCADA)
 SCADA is designed for isolated systems using proprietary
solutions, where as M2M is designed for cross platform
integration.

Engineering.
Machine to Machine Communication
 M2M, or machine-to-machine, is a direct communication

between devices using wired or wireless communication channels.
 M2M refers to the interaction
PLDof two or more devices/machines
that are connected to each other. These devices capture data and
share with other connected devices, creating an intelligent
network of things or systems.
 Devices could be sensors, actuators, embedded systems or other
connected elements.

Engineering.
PLD

Engineering.
PLD

Engineering.
M2M Overview
Sensors
NetworksPLD
Information Extraction
Processing
Actuation

Engineering.
Applications of M2M
 Environmental Monitoring
 Civil Protection & Public Safety
 Supply Chain Management
PLD
 Energy & Utility distribution industry (Smart Grid)
 Intelligent Transportation System
 Healthcare
 Automation of building
 Military
 Agriculture
 Home Networks

Engineering.
Features of M2M
 Large number of nodes or devices

 Low cost
PLD
 Energy efficient
 Small traffic per machine/ device
 Large quantity of collective data
 M2M is free from human intervention
 Human intervention is required for operational stability &
Sustainability
Engineering.
Features of M2M
 Large number of nodes or devices

 Low cost
PLD
 Energy efficient
 Small traffic per machine/ device
 Large quantity of collective data
 M2M is free from human intervention
 Human intervention is required for operational stability &
Sustainability
Engineering.
PLD

Engineering.
PLD

Engineering.
Differences and Similarities between M2M and IoT
M2M IoT
Isolated systems of devices Integrates devices, data & applications
Limited Scalable More Scalable

PLD
Uses non-IP protocols Uses IP protocols
Cloud is not essential Cloud is essential
Main purpose is to provide multiple applications &

Main purpose is monitor & control
communications
Hardware based H/W & S/W based
It consist of
It consist only Human to human communication
machine to machine communication Machine to human communication
Machine to machine communication
Engineering.
PLD

Engineering.
PLD

Engineering.
PLD

Engineering.
PLD

Engineering.
PLD

Engineering.
PLD

Engineering.
PLD

Engineering.
PLD

Engineering.
PLD

Engineering.
Origin of SDN
 In 2006 : At Stanford University a team proposes a clean-state

security architecture (SANE) to control a security policies in
centralized manner instead of doing it at edges.
PLD
 2008 : idea of SDN is originated from OpenFlow project.
 2009 : Stanford publishes OpenFlow v1.0.0 Specifications.
 March 2009 : Nicira network is founded.
 March 2011 : Open networking foundation is formed.
 Oct 2011 : First open networking summit. Many industries
( Juniper, Cisco) announced to incorporate.

Engineering.
PLD

Engineering.
Network Function Virtualization
PLD

Engineering.
IoT Platforms
 Temboo
 Ubidots
 myDevices
 ThingSpeak
PLD
 Xively
 Kaa
 Google Cloud IoT
 Microsoft Azure IoT
 IBM Watson IoT
 Artik Cloud
 AWS IoT
Engineering.
IoT Platforms
Temboo
This is a very interesting
platform that provides services
to integrate Arduino, Raspberry,
and other platforms with PLD
different Internet services (like
SMS, Email and so on)
Temboo supports M2M applications using MQTT, CoAP, and HTTP

protocols.
Code generation: Java, C/C++, Python, and so on.
Interoperability: the integration process with other cloud services.
Data: Temboo stores and visualizes different kinds of data.

Engineering.
IoT Design Methodology

Primary goal of designing is to continuously develop IoT
best practices and make them available to the end user
in the form of framework that is:
PLD
 Technology independent
 Reusable
 Open source

Engineering.
IoT Design Methodology

Designing IoT Systems is complex & challenging task as
these systems involve interactions between various
components :
 IoT devices PLD
 Network Resources
 Analytics Components
 Application
 Database Servers

Engineering.
Why there is need of IoT Design Methodology
 IoT system designers tend is to design IoT

systems keeping specific products/services in
mind.
 For Such systems updating the
PLDsystem design to
add new features or replacing particular
product/service become very complex job.
 It might require complete redesign of system.
 The better approach in designing platform for
IoT is to propose is generic design methodology.

Engineering.
.
• Purpose & requirement Specification
.
• Process Model Specification
.
• Domain Model Specification
.
• Information Model Specification
.
• Service Specification PLD
.
• IoT Level Specification
.
• Functional View Specification
.
• Operational View Specification
.
• Device & Component Integration
. • Application Development
Engineering.
Benefits of IoT Design Methodology
 Reduced design
 Reduced testing & maintenance time
PLD
 Better interoperability
 Reduced complexity.
With the proposed methodology designers can be able to

compare various alternatives for the IoT system
components.

Engineering.
Objectives of IoT Design Methodology
 Provide a reference model of architecture based

on Interoperability, Scalability and security,
privacy. PLD
 Provides guidelines to design IoT architecture

with the definition of set of views.
 Provide a common language and concepts to
improve communication between partners.

Engineering.
Purpose & requirement Specification

The first step in IoT system design methodology is to
define purpose & requirement of the system.
In this step following parameters are captured:
 System Purpose PLD
 Behaviour and requirements
 Data collections requirements
 Data analysis requirements
 System management requirements
 Data privacy requirements
 User interface requirements
Engineering.

“While implementing any IoT project first thing is to go
through the detailing of requirements specification.”
PLD

Engineering.

“Let us consider the smart home automation”
Purpose: A home automation system that allows

controlling the home appliances remotely using web
PLD
application.
Behaviour: The home automation should have auto and

manual mode.
System Management Requirement: System should

provide remote monitoring & control functions.

Engineering.

“Let us consider the smart home automation”
Data Analysis Requirements : The system should

perform the local analysis of the data.
PLD
Application Deployment Requirement: The application

should be deployed locally on the device, but should be
accessible remotely.
Security Requirement: System should have basic user

authentication.

Engineering.
Process specification
Second step in the IoT design methodology is to define
the process specification.
PLD
In this step the use cases of the IoT system are formally
described and derived on the requirements
specifications specified in the step_1

Engineering.
Use case diagram:
To model a system, the most important aspect is to

capture the dynamic behavior. Dynamic behavior means
the behavior of the PLDsystem when it is
running/operating.
Only static behavior is not sufficient to model a system
rather dynamic behavior is more important than static
behavior.
In UML, there are five diagrams available to model the
dynamic nature and use case diagram is one of them.

Engineering.
The purposes of use case diagrams can be said

to be as follows :
 Used to gather the requirements of a system.

 Used to get an outside view
PLD of a system.
 Identify the external and internal factors
influencing the system.
 Show the interaction among the requirements are
actors.
 dynamic nature and use case diagram is one of
them.

Engineering.
Mode
Auto Manual
PLD
Light Level Light State
Store: ON Store: OFF State:

Internet of Thnigs by Amol DandeON State: OFF 41
Engineering.
Kaa Platform
PLD

Engineering.
Sensors:
PLD

Engineering.
Step 3 : Domain model specification
The third step in IoT design methodology is to define

domain model for an application.
PLD
Domain model should describe the main concepts,
entities and objects in the domain of IoT system to be
designed.
Domain model should also defines the attribute of
objects an relationship between objects.d

Engineering.
Step 3: Domain model specification
The domain model also provides the abstract

representation of the concepts, objects and entities in
the IoT domain independent of
PLD
any specific technology
or platform.
With the domain model the IoT designers can get an

understanding of the IoT domain for which system is to
be designed.

Engineering.
Domain model specification

(smart home automation)
1. Physical Entity (e.g. room, car etc)

PLD
2. Virtual Entity
3. Devices (physical things)
4. Resources
5. service

Engineering.
Step 4 Information Model specification
 Defining the information model is the 4th step in IoT

design methodology.
 Information model definesPLDthe structure of the
information in the IoT System for example the
attributes of the virtual entities, their relationship
etc…
 But it does not describe the specific of hoe the
information is being processed.

Engineering.
Step 4 Information Model specification
It is used to define the following things:
To define the information model, PLD virtual entities are

listed to define in the domain model.
Information model adds more details of the virtual
entities by defining their attributes and relationship.

Engineering.
Virtual Entity : Room Virtual Entity

Entity Type : Room Light Appliances
ID : Room-1 Entity Type: Appliance
ID : Light-1
Attribute: Light Level PLD

Attribute : State
Attribute Name: Attribute Name:Lightstate
LightLevel Attribute Type : state
Attribute Type: Level
Light : High Light: Low State: ON State: OFF

Engineering.
Step 5: Service specifications
This Is the 5th step in the IoT design methodology is to

define the service specifications.
Service specification defines PLDthe services in the IoT
system.
The different services includes service types, service

input/output, service endpoints, service schedule,
service preconditions and service effects.

Engineering.
From the process specification and information model,

identify the states and attributes.
PLD
For each state and attribute define a service, these
services either change the state or attribute values or
retrieve the current values.

Engineering.

(Smart home automation)
 The mode (auto/manual) service is a RESTful web
service that sets mode to auto or manual, or retrieves
the current mode PLD
 The mode is updated or retrieved from the status DB.

 The state service is RESTful web service that sets the
light appliance set to ON/OFF or retrieve the current
light state from the DB.

Engineering.
Step 6: IoT level specifications

 The IoT levels are generally categorized at most 5
Levels.
IoT Level-1 :
PLD
 IoT system contains single node that does the
operation sensing, actuation, stores data, perform
analysis.
 These types of IoT systems are suitable for solving the
low cost and low complexity solutions where data
involved is not too big and analysis requirements are
not intensive.
Engineering.

IoT Level-2 :
 IoT system contains single node that does the
operation sensing, actuation.
PLD
 Data is stored in the cloud and entire application is
cloud based.
 It is suitable for solutions where the data involved is
big, the primary analysis requirement is not intensive
and can be done at locally.

Engineering.

IoT Level-2 :
PLD
Monitoring node
performs analysis
Cloud Storage

Engineering.
IoT Level-2 : Cloud
APP
Local Rest Communication
Controller PLD REST/WEB

Services Socket services
Resources
DB
Devices

Engineering.

IoT Level-3 :
PLD
Web
socket
Monitoring node
performs analysis Cloud Storage
and store the data

Engineering.

IoT Level-4 :
Observer Node
Monitoring node
performs Local PLD
analysis
Cloud Storage
Observer Node
Engineering.

IoT Level-5 :
Routers/End
points
PLD
Routers/End
points Coordinator
Cloud Storage
Routers/End
points

Engineering.
Step 7: Functional View Specification

This is the 7th step in IoT platform design methodology.
The functional view defines the functions of the IoT

PLD
systems grouped in to various functions.
Each functional groups either provides functionalities or

interacting with instances of concepts defined in in
domain model specifications.
Engineering.
Step 7: Functional View Specification

The components of Functional View Spec
Device: Device Functional group
Communication: Communication
PLD
functional group
Services: The service functional group
Management: Management Functional group
Security: Security Functional Group
Application: Application Functional group

Engineering.
Step 8: Operational View Specification

This is the 8th step in the IoT Design Methodology. In
this particular step various options pertaining to the IoT
system deployment and operations are defined.
PLD
Like
Service Hosting Option
Storage Options
Device options
Application hosting options.

Engineering.
Step 8: Operational View Specification

Devices: Computing Device Raspberry Pi
Communication APIS: REST API, Communication Proctors: 802.11
IPv4, IPv6 ,TCP, Application-HTTP
Services: Controller Services on hosted devices, Native services.
PLD
Mode of Services: REST ful, Django framework.
State Services: REST ful web services along with database
Security
Authorization
management

Engineering.
Step 9: Device & Component Integration

In the 9 th step of IoT Design methodology is the integration of
devices and components.
By considering the Smart Home automation IoT System,
The devices & the components can be used in this component may
be PLD
R-pi
LDR sensor
Relay CKT
Actuator
Connecting Mechanism

Engineering.
Step 10: Application Deployment
PLD

Unit 2: Iot Design Methodology: Dept. of Computer Science & Engineering

Uploaded by

Copyright:

Available Formats

Unit 2: Iot Design Methodology: Dept. of Computer Science & Engineering

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit 2: Iot Design Methodology: Dept. of Computer Science & Engineering

Uploaded by

Copyright:

Available Formats

Dept.

of Computer Science &

Unit 2 : IoT Design Methodology

Internet of Thnigs by Amol Dande 1

 IoT Design Methodology that includes:

Internet of Thnigs by Amol Dande 2

 Communication between machines or devices with computing

Internet of Thnigs by Amol Dande 3

Machine to Machine Communication

 M2M, or machine-to-machine, is a direct communication

Internet of Thnigs by Amol Dande 4

Machine to Machine Communication

Internet of Thnigs by Amol Dande 5

Machine to Machine Communication

Internet of Thnigs by Amol Dande 6

Internet of Thnigs by Amol Dande 7

Internet of Thnigs by Amol Dande 8

 Large number of nodes or devices

 Large number of nodes or devices

Internet of Thnigs by Amol Dande 11

Internet of Thnigs by Amol Dande 12

Differences and Similarities between M2M and IoT

Limited Scalable More Scalable

Cloud is not essential Cloud is essential

Main purpose is to provide multiple applications &

Hardware based H/W & S/W based

Internet of Thnigs by Amol Dande 14

Internet of Thnigs by Amol Dande 15

Internet of Thnigs by Amol Dande 16

Internet of Thnigs by Amol Dande 17

Internet of Thnigs by Amol Dande 18

Internet of Thnigs by Amol Dande 19

Internet of Thnigs by Amol Dande 20

Internet of Thnigs by Amol Dande 21

Internet of Thnigs by Amol Dande 22

 In 2006 : At Stanford University a team proposes a clean-state

Internet of Thnigs by Amol Dande 23

Internet of Thnigs by Amol Dande 24

Network Function Virtualization

Internet of Thnigs by Amol Dande 25

Temboo supports M2M applications using MQTT, CoAP, and HTTP

Internet of Thnigs by Amol Dande 27

IoT Design Methodology

Internet of Thnigs by Amol Dande 28

IoT Design Methodology

Internet of Thnigs by Amol Dande 29

Why there is need of IoT Design Methodology

 IoT system designers tend is to design IoT

Internet of Thnigs by Amol Dande 30

Benefits of IoT Design Methodology

With the proposed methodology designers can be able to

Internet of Thnigs by Amol Dande 32

Objectives of IoT Design Methodology

 Provide a reference model of architecture based

 Provides guidelines to design IoT architecture

Internet of Thnigs by Amol Dande 33

Purpose & requirement Specification

Purpose & requirement Specification

Internet of Thnigs by Amol Dande 35