UNIT 4

Implementation of IoT with Raspberry Pi

Introduction to Internet of Things 1

IO
T
 Creating an interactive environment
 Network of devices connected
together

Introduction to Internet of Things 2

IOT: Remote Data Logging
 Collect data from the devices in the network
 Send the data to a server/remote machine
 Control the network remotely

Introduction to Internet of Things 3

IOT: Remote Data Logging

System Overview:
 A network of Temperature and humidity sensor connected with
Raspberry Pi
 Read data from the sensor
 Send it to a Server
 Save the data in the server

Introduction to Internet of Things 4

IOT: Remote Data Logging
( contd..)
Requirements
 DHT Sensor
 4.7K ohm resistor
 Jumper wires
 Raspberry Pi

Introduction to Internet of Things 5

DHT
Sensor
 Digital Humidity and
Temperature Sensor (DHT)
 PIN 1, 2, 3, 4 (from left to
right)
 PIN 1- 3.3V-5V Power
supply
 PIN 2- Data
 PIN 3- Null
 PIN 4- Ground

Introduction to Internet of Things 6

Sensor- Raspberry Pi
Interface
 Connect pin 1 of DHT sensor to the 3.3V pin of Raspberry Pi
 Connect pin 2 of DHT sensor to any input pins of Raspberry Pi, here
we have used pin 11
 Connect pin 4 of DHT sensor to the ground pin of the Raspberry Pi

Introduction to Internet of Things 7

 Read Data from the Sensor
Adafruit provides a library to work with the DHT22 sensor

Install the library in Raspberry Pi

Use the function Adafruit_DHT.read_retry() to read data from the sensor

Source: ADAFRUIT DHTXX SENSORS, Lady Ada, 2012-07-29

Introduction to Internet of Things 8

Program: DHT22 interfaced with Raspberry
Pi
Code Output

Introduction to Internet of Things 9

Sending Data to a Server

Sending data to Server using network protocols

 Create a server and client
 Establish connection between the server and the client
 Send data from the client to the server

Introduction to Internet of Things 10

Sending Data to a Server (contd..)

Socket Programming:
 Creates a two-way communication between two nodes in a network
 The nodes are termed as Server and Client
 Server performs the task/service requested by the client

Introduction to Internet of Things 11

Sending Data to a Server (contd..)

Creating a socket:
s = socket.socket (SocketFamily, SocketType, Protocol=0)

 SocketFamily can be AF_UNIX or AF_INET

 SocketType can be SOCK_STREAM or SOCK_DGRAM
 Protocol is set default to 0

Source: PYTHON NETWORK PROGRAMMING, TutorialsPoint

Introduction to Internet of Things 12

Sending Data to a Server (contd..)

Server:
s = socket.socket() # creating a socket object
host = socket.gethostname() # local machine name/address
port = 12321 # port number for the server
s.bind((host, # bind to the port
port)) s.listen(5) # waiting for the client to
while True: connect
c, addr = # accept the connection request from the client
print ‘Connected to', addr
s.accept()
c.send(‘Connection Successful')
c.close() #close the socket
Source: PYTHON NETWORK PROGRAMMING, TutorialsPoint

Introduction to Internet of Things 13

 Sending Data to a Server (contd..)
Client:

s = socket.socket() # creating a socket object

host = socket.gethostname() # getting local machine name
port = 12345 # assigning a port
s.connect((host, port))
print s.recv(1024)
s.close

Source: PYTHON NETWORK PROGRAMMING, TutorialsPoint

Introduction to Internet of Things 14

Sending Data to a Server (contd..)
Client Code: Obtain readings from the sensor

def sensordata():
GPIO.setmode(GPIO.BOARD)
GPIO.setwarnings(False)
sensor = Adafruit_DHT.AM2302
humidity, temperature = Adafruit_DHT.read_retry(sensor,17)
return(humidity, temperature)

This function returns the values from the DHT sensor

Introduction to Internet of Things 15

Sending Data to a Server (contd..)
Client Code: Connecting to the server and sending the data

sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) #create UDP socket

server_address = ('10.14.3.194', 10001)
try:
while (1):
h,t = sensordata()
message = str(h)+','+str(t)
#Send data
print >>sys.stderr,
'sending "%s"' % message
sent = sock.sendto(message, server_address)
finally:
print >>sys.stderr, 'closing socket'
sock.close()

Introduction to Internet of Things 16

Sending Data to a Server (contd..)
Server Code: Receive data from client and save it
# Create a UDP socket
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
# Bind the socket to the port
server_address = ('10.14.3.194', 10001)
sock.bind(server_address)
while True:
data, address = sock.recvfrom(4096)
with open(“Datalog.txt","a") as f:
mess=str(data)
f.write(mess)
print mess
f.close()

Introduction to Internet of Things 17

Resul
t
 The client takes reading from
the sensor and sends it to the
server
 The server receives the
data from the client and
saves it in a text file
DataLog.txt

Introduction to Internet of Things 18

Implementation of IoT with Raspberry Pi: Part

Introduction to Internet of Things 1

IO
Internet Of Things
T
 Creating an interactive environment
 Network of devices connected
together

Introduction to Internet of Things 2

IOT: Remote Data Logging
 Collect data from the devices in the network
 Send the data to a server/remote machine
 Processing the data
 Respond to the network

Introduction to Internet of Things 3

IOT: Remote Data Logging

System Overview:
 A network of Temperature and humidity sensor connected with
Raspberry Pi
 Read data from the sensor
 Send it to a Server
 Save the data in the server
 Data Splitting
 Plot the data

Introduction to Internet of Things 4

IOT: Remote Data Logging
( contd..)
Requirements
 DHT Sensor
 4.7K ohm resistor
 Jumper wires
 Raspberry Pi

Introduction to Internet of Things 5

DHT
Sensor
 Digital Humidity and
Temperature Sensor (DHT)
 PIN 1, 2, 3, 4 (from left to
right)
 PIN 1- 3.3V-5V Power
supply
 PIN 2- Data
 PIN 3- Null
 PIN 4- Ground

Introduction to Internet of Things 6

Sensor- Raspberry Pi
Interface
 Connect pin 1 of DHT sensor to the 3.3V pin of Raspberry Pi
 Connect pin 2 of DHT sensor to any input pins of Raspberry Pi, here
we have used pin 11
 Connect pin 4 of DHT sensor to the ground pin of the Raspberry Pi

Introduction to Internet of Things 7

Read Data from the Sensor

Use the Adafruit library for DHT22 sensor to read the sensor
data

Introduction to Internet of Things 8

Sending Data to a Server
 Sending data to server using socket programming
 Create a client and server
 Establish connection between the two
 Send data from the client to the server
 Save the data in a file

Introduction to Internet of Things 9

Data Processing

Data from the client needs to be processed before it can be

used further
 Data splitting/filtering
 Data plotting

Introduction to Internet of Things 10

 Data Processing
Data splitting/filtering:
 Data from the client is saved in a text file
 The values are separated by a comma(‘ , ’)
message = str(h)+','+str(t)
 Split() function can be used to split a string into multiple strings depending on the type of
separator/delimiter specified.
Example:
Data= ‘sunday,monday,tuesday’ #Data is a string with 3 words separated by a comma
Data.split(“,”) # split the data whenever a “,” is found
[‘sunday’,’monday’,’tuesday’] # Gives 3 different strings as output

Source: HOW TO USE SPLIT IN PYTHON, PythonForBeginners, Sep 26, 2012

Introduction to Internet of Things 11

Data Processing

Plotting the data:

 MATPLOTLIB is a python library used to plot in 2D
 Plot(x,y): plots the values x and y
 xlabel(‘X Axis'): Labels the x-axis
 ylabel(‘Y Axis'): Labels the y-axis
 title("Simple Plot"): Adds title to the plot

Source: MATPLOTLIB, John Hunter, Darren Dale, Eric Firing, Michael Droettboom and the Matplotlib development team, 2012 - 2016

Introduction to Internet of Things 12

Data Processing (contd..)

Plotting the data:

import matplotlib.pyplot as myplot
myplot.plot([1,2,3,4])
myplot.ylabel(‘Y-Axis’)
myplot.show()
By default the values are taken for y-axis, values for x-axis are generated automatically starting
from 0

Source: MATPLOTLIB, John Hunter, Darren Dale, Eric Firing, Michael Droettboom and the Matplotlib development team, 2012 - 2016

Introduction to Internet of Things 13

Data Processing (contd..)

Basic Plot:

Introduction to Internet of Things 14

Data Proceessing (contd..)

Some other common functions used in plotting:

 figure(): Creates a new figure
 grid(): Enable or disable axis grids in the plot
 ion(): turns on the interactive mode
 subplot(): Adds subplot in a figure
 Close(): Close the current figure window
 Scatter(): make a scatter plot of the given points

Source: MATPLOTLIB, John Hunter, Darren Dale, Eric Firing, Michael Droettboom and the Matplotlib development team, 2012 - 2016

Introduction to Internet of Things 15

Sending Data to a Server (contd..)
sock = socket.socket(socket.AF_INET,
Client: socket.SOCK_DGRAM) #create UDP socket
server_address = ('10.14.3.194', 10001)
try:
def sensordata(): while (1):
GPIO.setmode(GPIO.BOARD) h,t = sensordata()
GPIO.setwarnings(False) message = str(h)+','+str(t) #Send data
sensor = Adafruit_DHT.AM2302 print >>sys.stderr, 'sending "%s"' % message
sent = sock.sendto(message, server_address)
humidity, temperature =
finally:
Adafruit_DHT.read_retry(sensor,17)
print >>sys.stderr, 'closing socket'
return(humidity, temperature) sock.close()

Introduction to Internet of Things 16

Sending Data to a Server (contd..)

•Server: ax.grid()
ax = fig.add_subplot(122)
ax.plot(hum,i, c='b', marker=r'$\Phi$')
• def coverage_plot(data,i): plt.xlabel('Humidity ($\%$)')
hum=data.split(",")[0] ax.grid()
• tem=data.split(",")[1] fig.show()
fig.canvas.draw(
• print 'temp='+(str(tem))+'iter='+str(i) )
plt.ion()
fig=plt.figure(num=1,figsize=(6,6)) sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
• plt.title(' IoT Temperature and Humidity Monitor')
ax = fig.add_subplot(121) # Bind the socket to the port
• ax.plot(tem,i, c='r', marker=r'$\Theta$') server_address = ('10.14.3.194', 10001)
plt.xlabel('Temp ($^0 C$)’) sock.bind(server_address)

Introduction to Internet of Things 17

Sending Data to a Server (contd..)
Server:
i=0
while True:
data, address = sock.recvfrom(4096)
with open("DataLog.txt","a") as f:
mess=str(data)
f.write(mess)
coverage_plot(mess,i)
print mess
i+=1
f.close()

Introduction to Internet of Things 18

Output
 The Reading from the sensor is
sent to the Server and saved
in a text file.
 Two different plots for
temperature and humidity
data

Introduction to Internet of Things 19

Output

Introduction to Internet of Things 20

Software- Defined Networking –
Part I
Restructuring the Current Network
Infrastructure

Introduction to Internet of Things 1

Overview of Current Network

User II
User I

Introduction to Internet of Things 2

Overview of Current Network
OSPF Protocol executing
at the switches

User II
User I

Introduction to Internet of Things 3

Overview of Current Network

Open Shortest Path First (OSPF) is an Interior Gateway

Protocol (IGP) that runs on switches and is used to enable
routing. To execute OSPF on a routing switch, you can::
OSPF Protocol executing at the switches

User II

User I

the switch has been attacked!

Introduction to Internet of Things 4

Overview of Current Network
OSPF Protocol executes
at the switches

User II
User I
the switch has been attacked!
needs to route through an alternate path!
Present: No centralized control.

Introduction to Internet of Things 5

Limitations in Current Network

app
app OS
OS hardware app
hardware OS
app
OS hardware
app
hardware
OS app
hardware OS Switches forward traffic
hardware in a distributed manner.
They do not have a
global view of the
network

Introduction to Internet of Things 6

Limitations in Current Network
 Vendor-specific architecture of switches limits dynamic
configuration according to application-specific requirements.
 Switches are required to configure according to the installed
operating system (OS).
 Centralized control is not feasible in traditional network.

Introduction to Internet of Things 7

Limitations in Current Network

Routing, mobility
Thousands app app app
management, etc.
lines of
code Cost-expensive Operating system

Millions of gates, Specialized packet

~10GB RAM forwarding hardware

Introduction to Internet of Things 8

Current Network to SDN
app
app OS
app OS app
OS OS
hardware
hardware
app hardware
hardware app
OS OS

hardware
hardware

Introduction to Internet of Things 9

Current Network to SDN

app app app

Operating system

packet packet packet

forwardin forwardin forwardin
g g g
hardware hardware hardware

Introduction to Internet of Things 10

Origin of
SDN
 2006: At Stanford university, a team proposes a clean-slate security architecture
(SANE) to control security policies in a centralized manner instead of doing it at
edges.
 2008: The idea of software-defined network is originated from OpenFlow project
(ACM SIGCOMM 2008).
 2009: Stanford publishes OpenFlow V1.0.0 specs.
 June 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.

Introduction to Internet of Things 11

SDN Architecture
Network Function
Virtualization

Notes
- Northbound API
- Southbound API
(via OpenFlow)

Introduction to Internet of Things 12

Basic Concepts of
SDN
 Separate control logic from hardware switches
 Define the control logic in a centralized manner
 Control the entire network including individual switches
 Communication between the application, control, and data
planes are done through APIs

Introduction to Internet of Things 13

Components/Attributes of SDN
 Hardware switches
 Controller
 Applications
 Flow-Rules
 Application programming interfaces (APIs)

Introduction to Internet of Things 14

Current Status of
SDN
 Companies such as Google have started to implement SDN at
their datacenter networks.
 It is required to change the current network with SDN in a
phased manner.
 Operational cost and delay caused due to link failure can be
significantly minimized.

Introduction to Internet of Things 15

Challenge
s
 Rule placement
 Controller placement

Introduction to Internet of Things 16

Rule Placement I
 Switches forward traffic based on a rule – ‘Flow-Rule’ –
defined by the centralized controller.
 Traditionally, Routing Table in every switch (L3 switch/router).
 SDN maintains Flow Table at every switch.
 Flow-Rule: Every entry in the Flow Table.
 Each rule has a specific format, which is also defined by a
protocol (e.g., OpenFlow).

Introduction to Internet of Things 17

Rule Placement II

Example of a flow-rule based on OpenFlow protocol

Source: http://networkstatic.net/wp-content/uploads/2013/06/OFP_normal_rules.png

Introduction to Internet of Things 18

Rule Placement Challenges I
 Size of ternary content-addressable memory (TCAM) is limited
at the switches.
 Limited number of rules can be inserted.
 Fast processing is done using TCAM at the switches.
 TCAM is very cost-expensive.

Introduction to Internet of Things 19

Rule Placement Challenges II
 On receiving a request, for which no flow-rule is present in
the switch, the switch sends a PACKET-IN message to the
Controller
controller.
 The controller decides a suitable
flow-rule for the request.
 The flow-rule is inserted at the
switch.
 Typically, 3-5ms delay is involved in a
new rule placement
Introduction to Internet of Things 20
Rule Placement III
 How to define/place the rules at switches, while considering
available TCAM.
 How to define rules, so that less number of PACKET-IN
messages are sent to controller.

Introduction to Internet of Things 21

OpenFlow Protocol I
 Only one protocol is available for rule placement – OpenFlow.
 It has different versions – 1.0, 1.1, 1.2, 1.3, etc. – to have
different number of match-fields.

Source: http://networkstatic.net/wp-content/uploads/2013/06/OFP_normal_rules.png

Introduction to Internet of Things 22

OpenFlow Protocol II
 Different match-fields
 Source IP
 Destination IP
 Source Port
 Priority
 etc.

Introduction to Internet of Things 23

OpenFlow Protocol III

How much time a flow-rule is to be kept at the switch?

 Hard timeout
 All rules are deleted from the switch at hard timeout.
 This can used to reset the switch.
 Soft timeout
 If NO flow is received associated with a rule for a particular time, the
rule is deleted.
 This is used to empty the rule-space by deleting an unused rule.

Introduction to Internet of Things 24

OpenFlow Protocol IV
 SDN is NOT OpenFlow
 SDN is a technology/concept
 OpenFlow is a protocol used to communicate between data-plane and
control-plane.
 We may have other protocols for this purpose. However, OpenFlow is
the only protocol present today.

Introduction to Internet of Things 25

OpenFlow Switch Software
 Indigo: Open source, it runs on Mac OS X.
 LINC: Open source, it runs on Linux, Solaris, Windows, MacOS, and
FreeBSD.
 Pantou: Turns a commercial wireless router/access point to an
OpenFlow enabled switch. OpenFlow runs on OpenWRT.
 Of13softswitch: User-space software switch based on Ericsson
TrafficLab 1.1 softswitch.
 Open vSwitch: Open Source, it is the MOST popular one present
today.

Introduction to Internet of Things 26

Summar
y
 Basics of SDN
 Challenges present in SDN
 Rule Placement with OpenFlow
 Controller Placement – to be discussed in next lecture

Introduction to Internet of Things 27

Software- Defined Networking – Part
II Restructuring the Current Network
Infrastructure

Introduction to Internet of Things 1

SDN - Recap
 SDN – restructuring current network infrastructure
 Architecture of SDN – Application, Control and Infrastructure
layers
 Rule Placement – TCAM and Delay
 OpenFlow protocol – flow-rule and math-fields

Introduction to Internet of Things 2

APIs in
SDN
 Southbound API
 Used to communicate between control layer and infrastructure layer.
 OpenFlow protocol is used.
 Northbound API
 Used to communicate between control layer and application layer.
 Standard APIs are used.
 East-Westbound APIs
 Used to communicate among multiple controllers in the control layer.

Introduction to Internet of Things 3

Controller Placement I
 Controllers define flow-rule according to the application-
specific requirements.
 The controllers must be able to handle all incoming requests
from switches.
 Rule should be placed without incurring much delay.
 Typically, a controller can handle 200 requests in a second
(through a single thread).

Introduction to Internet of Things 4

Controller Placement II
 The controllers are logically connected to the switches in one-
hop distance.
 Physically, they are connected to the switches in multi-hop distance.
 If we have a very small number of controllers for a large
network, the network might be congested with control
packets (i.e., PACKET-IN messages).

Introduction to Internet of Things 5

 Flat Architecture

Packet-IN
Flow-Rule

Introduction to Internet of Things 6

Hierarchical (tree) Architecture

Introduction to Internet of Things 7

Ring Architecture

Introduction to Internet of Things 8

Mesh Architecture

User II
User I

Introduction to Internet of Things 9

Control Mechanisms
 Distributed
 The control decisions can be taken in a distributed manner
 Ex: each subnetwork is controlled by different controller
 Centralized
 The control decisions are taken in a centralized manner.
 Ex: A network is controlled by a single controller.

Introduction to Internet of Things 10

Backup Controller
 If a controller is down, what will happen?
 Backup controller is introduced
 Replica of the main controller is created
 If the main controller is down, backup controller controls the network
to have uninterrupted network management.

Introduction to Internet of Things 11

Security I
 Enhanced security using SDN
 Firewall
 Proxy
 HTTP
 Intrusion detection system (IDS)

12
Security II

Example of potential data plane ambiguity to implement the policy chain

Firewall-IDS-Proxy in the example topology.

Source: SIMPLE-fying Middlebox Policy Enforcement Using SDN,

SIGCOMM 2013

Introduction to Internet of Things 13

Experimenting with SDN
 Simulator/Emulator
 Infrastructure deployment – MUST be supported with OpenFlow
 Controller placement – MUST support OpenFlow
 Remote – controller can be situated in a remote place, and communicated
using IP address and port number
 Local

Introduction to Internet of Things 14

Switch Deployment
 Mininet
 Used to create a virtual network with OpenFlow-enabled switches
 Based on Python language
 Supports remote and local controllers

Introduction to Internet of Things 15

Controller Configuration Software
 Pox
 Nox
 FloodLight
 OpenDayLight [Popular!]
 ONOS [Popular!]

Introduction to Internet of Things 16

Summar
y
 Performance of SDN depends on rule placement and
controller placement in the network.
 Control message overhead may be increased due to
additional number of packets (PACKET-IN messages).
 Unified network management is possible using SDN, while
leveraging global view of the network.

Introduction to Internet of Things 17

Software- Defined IoT Networking –
Part I Recent Advances of SDN in
IoT

Introduction to Internet of Things 1

 IoT
Architecture

Source: https://image.slidesharecdn.com Source: http://www.luxhotels.info/p/46800/internet-of-things-iot/

Introduction to Internet of Things 2

Benefits of Integrating SDN in
IoT
 Intelligent routing decisions can be deployed using SDN
 Simplification of information collection, analysis and decision
making
 Visibility of network resources – network management is
simplified based on user, device and application-specific
requirements
 Intelligent traffic pattern analysis and coordinated
decisions

Introduction to Internet of Things 3

SDN for IoT
I

Source: https://image.slidesharecdn.com

Introduction to Internet of Things 4

SDN for IoT
II

Control of end-devices, such as sensors

and actuators

Introduction to Internet of Things 5

SDN for IoT
III

Ru le-placement at access devices,

w hile considering mobility and
terogeneity of end-users
he

Introduction to Internet of Things 6

SDN for IoT
IV

Rule-placement and traffic

engineering at backbone networks

Introduction to Internet of Things 7

SDN for IoT
V

Flow classification and enhanced

security at data center networks

Introduction to Internet of Things 8

Wireless Sensor Network I
 Challenges
 Real-time programming of sensor nodes
 Vendor-specific architecture
 Resource constrained – heavy computation cannot be performed
 Limited memory – cannot insert too many control programs

Introduction to Internet of Things 9

Wireless Sensor Network II
 Opportunities
 Can we program the sensor nodes in real-time?
 Can we change the forwarding path in real-time?
 Can we integrate different sensor nodes in a WSN?

Introduction to Internet of Things 10

Software- Defined
WSN I
 Sensor OpenFlow (Luo et al., IEEE Comm. Letters ’12)
 Value-centric data forwarding
 Forward the sensed data if exceeds a certain value
 ID-centric data forwarding
 Forward the sensed data based on the ID of the source node

Real-life implementation of such method NOT done

Introduction to Internet of Things 11

Software- Defined WSN
II
 Soft-WSN (Bera et al., IEEE SJ ’16)
 Sensor Device Management
 Sensor management
 Multiple sensors can be implemented in a single sensor board
 Sensors can be used depending on application-specific requirements
 Delay management
 Delay for sensing can be changed dynamically in real-time
 Active-Sleep Management
 States of active and sleep mode can be changed dynamically

Introduction to Internet of Things 12

Software- Defined WSN
III
 Soft-WSN
 Topology Management
 Node-specific management – forwarding logic of a particular sensor can
be modified
 Network-specific management
 Forward all traffic of a node in the network
 Drop all traffic of a node in the network

Experimental results show that network performance can be improved using

software-defined WSN over traditional WSN

Introduction to Internet of Things 13

Soft-WSN: Result
I

Packet delivery ratio in the network increases using Soft-WSN

compared to the traditional WSN.

Introduction to Internet of Things 14

Soft-WSN: Result
II

Number of replicated data packets is reduced using Soft-WSN over

the traditional WSN.

Introduction to Internet of Things 15

Soft-WSN: Result
III

Number of control messages in the network is higher using Soft-WSN over the
traditional WSN. This is due to the PACKET-IN message in the network. Each time a
node receives a new packet, it asks the controller for getting adequate forwarding logic.

Introduction to Internet of Things 16

Software- Defined WSN
III
 SDN-WISE (Galluccio et al., IEEE INFOCOM ’15)
 A software-defined WSN platform is designed
 Flow-table for rule placement at sensor nodes is designed
 Any programming language can be used through API to program the
nodes in real-time

Introduction to Internet of Things 17

SDN-WISE Protocol Stack
 Sensor node includes
 IEEE 802.15.4 protocol
 Micro control unit (MCU)
 Above IEEE 802.15.4 stack,
Forwarding layer consists of
Flow-rules.
 INPP – In Network Packet
Processing

Source: Galluccio et al., IEEE INFOCOM ’15

Introduction to Internet of Things 18

Summar
y
 SDN is useful to manage and control IoT network
 Wireless sensor nodes and network can be controlled using
SDN-based applications
 Network performance can be improved significantly using
SDN-based approaches over the traditional approaches

Introduction to Internet of Things 19