IOT and M2M

76

3.1 Introduction
of Internet of Thing
definition and characteristics
In Chapter-1. you learned about the
with loT'is Machine-to-Machine
is often used synonymously
(M2M).
(dot). Another loTwhich
Thoughterm and M2M are often used interchangeably, these terms have evolved
ties
some of the difterences and similarities
describes
Trom different backgrounds. This chapter
between loT and M2M.

3.2 M2M
machines (or devices) for the purpose
(M2M) refers tonetworking of
Machine-to-Machine
3.1 shows the end-to-end
control and data exchange. Figure
of remote monitoring and networks, communication network
architecture for M2M systemscomprising of M2M area
of machines (or M2M nodes
domain. An M2M area network comprises
and application actuation and communication. Various
modules for sensing,
which have embedded hardware networks such as ZigBee.
communication protocols be used for M2M local area
can
Communication (PLC), 6LoWPAN,
ModBus, M-Bus, Wirless M-Bus, Power Line
Bluetooh. between M2M
communication protocols provide connectivity
IEEE 802.15.4, etc. These to
The communication network provides connectivity
nodes within an M2M area network.
communication network can use either wired or
wireless
remote M2M area networks. The
use either proprietary or non-IP based
networks (IP-based). While the M2M area networks
IP-based networks. Since non-IP
communication protocols, the communication network uses
based protocols are used within M2M area networks, the
M2M nodes within one network
cannot communicate with nodes in an external
network. To enable the communication
between remote M2M area networks, M2M gateways are used.

Figure block diagram of an M2M gateway. The communication between

3.2 shows a

the M2M nodes and the M2M gateway is based on the communication protocols which
to
are native to the M2M area network. M2M gateway performs protocol translations
enable IP-connectivity for M2M area networks. M2M gateway acts as a proxy pertorming
translations from/to native protocols to/from Internet Protocol (IP). With an M2M gateway.
each node in an M2M area network appears as a virtualized node for external M2M are
networks.
The M2M data is gathered into point solutions such as enterprise applications, servie
management applications, or remote monitoring applications. M2M has various application
domains such as smart metering, home automation, industrial automation, smart grids, etc.
MMsolution designs (such as data collection and storage architectures and applications)
are specific to the M2M
application domain.
Bahga&Madisetti, 2015
3.3 Ditference between loT and M2M 77

M2M Area Networks M2M Core Network

Wired Network

M2M Applications
M2M Gateway

Wireless Network

M2M Gateway

AA
Figure 3.1: M2M system architecture

M2M Area Networks:

Bluetooth
ZigBee
802.15.4
6loWPAN M2M Gateway
M-Bus, Wireless M-8us
UWB
ModBus
Virtual Node
Z-Wave Native Protocol
Translation
Proxy
Protocol IP Routing
Nog

Virtual Node
Native Protocol
M2M Node Translation
Proxy
Protocol

Figure 3.2: Block diagram of an M2M gateway

3.3 Difference between loT and M2M

differ in the
Though both M2M and loT involve networking of machines or devices, they
underlying technologies, systems architectures and types of applications.

Internet of Things- A Hands-On Approach

 loT and M2M

described as follows:
Ihe differences between M2M and lo'T are

differ in how the communicati

tion
Communication Protocols: M2M and loT can

happens. M2M uses either proprietary

n-IP or non.t

between or devices
the machines protocols
based communication for communication within the M2M area netwarrless
ModBus, M-Bus,
orks
Wirle.
include ZigBce, Bluetooh, IEEE
Commonly uses M2M protocols 6LoWPAN, 802.15.4, Z-Wa we
Communication (PLC),
M-Bus. Power Line on the protocols below the
communication in
M2M is usually
etc. The focus of the protocols above
in is usually on
loT'
The focus of communication
network layer. MQTT, XMPP, DDS, AMOD
P
CoAP, WebSockets,
the network layer such as HTTP,
etc.. shown in Figure 3.3. physical obiects
"Things" in loT refers
as to
The
Machines in M2M vs Things in IoT: communicate with their external
can sense and
identifiers and
that have unique physical states. The unique
or their internal
environment (and user applications)
the IP addresses (or MAC addresses). Things have
things in IoT are
identifiers for the sensor information, or
for accessing, processing, and storing
software components
actuators connected. loT systems can
have heterogeneous things (e.g., a
controlling devices of various types, such as fire
can include IoT
home automation lolT system in contrast to loT,
lighting control devices, etc.) M2M systems,
alarms, door alarms,
within an M2M areanetwork.
typically have homogeneous machinetypes
While the emphasis of M2M is moreonhardware
Hardware vs Software Emphasis:
on software. IoT
devices run
with embedded modules, the emphasis of IoTis more
and interfacing with the
specializedsoftware for sensor data collection, data analysis
IP-based communication. Figure 3.4 shows the various components of
cloud through the
communication infrastructure and
loT systems including the things, the Internet,
applications. in
and often
Data Collection & Analysis: M2M data is collected in point solutions
on-premises storage infrastructure. In contrast to M2M, the data in IoT is collected
shows the various
in the cloud (can bepublic, private or hybrid cloud). Figure 3.5
component
loT-levels, and the loT components deployed in the cloud. The analytics
The IoT data and analysis
analyzes the data and stores the results in the cloud database.
controiuet
results are visualized with the cloud-based applications. The centralized
is aware of the status of all the end nodes and sends control commands to the noucs
Observer nodes can process information and use it for various applications, howevc
observer nodes do not perform any control functions.
APplications: M2M data is collected in point solutions and can be accesseu

on-premises applications such as diagnosis applications, service management

applications, and on-premisis enterprise applications. loT data is collectedintne cloud

2015
Bahga & Madisetti, C
3.3 Difference between loT and M2M 79

and can be accessed by cloud applications such as analytics applications, enterprise

applications, remote diagnosis and management applications, etc. Sincethe scale of
data collected in loT is so massive, cloud-based real-time and batch data analysis
frameworks are used for data analysis.

WebSockets
HTTP COAP WebSockets HTTP CoA
MQTT XMPP DDS AMQP MQTT XMPP DOS AMOP

ansp
CP UDP TCP UDP

IP4 IPv6 6LoWPAN IPv4 IPv6 6LoWPAN

M2M tinkLayer
802.3-Ethernet 802.16-WiMax 26/36/LTE- (primarily point-to polnt 802.3-Ethernet 802.16-WiMax 26/3G/LTE-
K Cellular Cellular
802.11-WiFi802.15.4-LR-WPAN 802.11-WiFi802.15.4-LR-WPAN

Figure 3.3: Communication in IoT is IP-based whereas M2M uses non-IP based networks.
Communication within M2M area networks is based on protocols below the network layer
whereas loT is based on protocols above the network layer.

Computing Infrastructure
Things Internet
& Applications
Backhaul Networks

1 Wired

Wireless

Thing

44-)
Sensors/Actuators Processing Communication

Figure 3.4: IoT components

Internet of Things - A Hands-On Approach

80 IOT and M2M

16T Level-6

Multple Monitoring
Nodes
Centralized
Controler

loT Level-5

Centrollted

Dadoase
outers/End Points
Coordinator

lOT Level-44

lOTLevels 2 &3
Hesourc

Resource

Device
Monitoring Nodes
perorm loal analysis

Monitoning Node

Figure 3.5: loT levels and loT cloud components

3.4 SDN and NFV for loT

In this section you will learn about Software Defined Networking (SDN) and Nerwo
Function Virtualization (NFV) and their applications for loT.

Bahga &Madisetti, ©
2013
3.4 SDN and NFV for loT 81

3.4.1 Software Defined Networking

Software-Defined Networking (SDN) is a networking architecture that separates the control
plane from the data plane and centralizes thenetwork controller. Figure 3.6 shows the
conventional network architecture built with specialized hardware (switches, routers, etc.)
Network devices in conventional netwok architectures are getting exceedingly complex with
the increasing number of distributed protocols being implemented and the use of proprietary
hardware and interfaces. In the conventional network architecture the control plane and data
plane are coupled. Control plane is the part of the network that carries thesignaling and
routing message traffic while the data plane is the part of the network that carries the payload
data traffic.
w

******

Network Network
Applicatior Application

Network Operanngse

pecialized PacketForwarding
Hardware

Network Network
Network Network
Application| Application Application Application

Netwo
twork OperatingSystem
SpecializedPacket 5
Specialized Packet Forwarding ware
Hardware

www
Network Network
Application Application

Specialized Packet Forwarding

Hardware

Conventional network architecture

Figure 3.6:

network architectures are as follows:

Thelimitations of the conventional getting increasingly complex
networks are
Complex Network Devices: Conventional
to improve link speeds and reliability.
with more and more protocols being implemented

Internet of Things- A Hands-On Approachn

82 loT and M2M

Applications Layer

Network Network Network Network

Application Application Application Application

Northbound Open API

Control Layer

Network Operating System

Southbound Open API (OpenFlow)

Infrastructure Layer

SimplePacket Forwarding
Hardware

Simple Packet Forwarding Simple Packet Forwarding

Hardware Hardware

Simple Packet Forwarding

Hardware

Figure 3.7: SDN architecture

SDN Architecture

Application
SDN Applications
Layer
Programmable Open APls
(Northbound Intertace)
Control
SDN Controler
Layer
Control & Data Plane Programmable
infrastructure Interface (Southbound Interface)
Network Network Network
Layer
Device Device Device

Figure 3.8: SDN layers

Interoperability is limited due to the lack of standard and open interfaces. Netwos
evices use proprietary hardware and software and have slow product life-cyct
niting innovation. The conventional
networks were well suited for statue u aftic

2015
Bahga & Madisetti, ©
3.4 SDN and NFV for loT 83

patterns and had a large number of protocols designed for specific applications. For
loT applications which are deployed in cloud computing environments, the traffic
patterns are more dynamic. Due to the complexity of conventional network devices,
making changes in the networks to meet the dynamic traffic patterns has become
increasingly difficult.
Management Overhead: Conventional networks involve significant management
overhead. Network managers find it increasingly difficult to manage multiple network
devices and interfaces from multiple vendors. Upgradation of network requires
configuration changes in multiple devices (switches, routers, firewalls, etc.)
Limited Scalability: The virtualization technologies used in cloud computing
environments has increased the number of virtual hosts requiring network access.
loT applications hosted in the cloud are distributed across multiple virtual machines
that require exchange of traffic. The analytics components of loT applications run
distributed algorithms on a large number of virtual machines that require huge amounts
of data exchange between virtual machines. Such computing environments require

highly scalable and easy to manage network architectures with minimal manual
configurations, which is becoming increasingly difficult with conventional networks.
SDN attempts to create network architectures that are simpler, inexpensive, scalable,
3.7 and 3.8 show the SDN architecture and the SDN
Figures
agile and easy to manage.
network controller is
layers in which the control and data planes are decoupled and the
centralized. Software-based SDN controllers maintain a unified view
of the network and
infrastructure
make configuration, management and provisioning simpler. The underlying
to specialized hardware in
in SDN uses simple packet forwarding hardware as opposed
conventional networks. The underlying network infrastructure
is abstracted from the
do not require implementations
applications. Network devices become simple with SDN as they
instructions from the SDN controller
of a large number of protocols. Network devices receive
and cost less as they can be
on how to forward the packets. These devices can be simpler
built from standard hardware and software components.

Kcyelements of SDN are as follows:

With decoupled control and data planes and
munrsiriaens

Centralized Network Controller:

centralized network controller, the network administrators
can rapidly configure the
APls. This
can be deployed through programmable open
network. SDN applications
as the network
administrators no longer need to wait for the
speeds up innovation
device vendors to embed new features
in their proprietary hardware.
open APls
Programmable Open APIs: SDN architecture supports programmable
controllayers (Northbound interface).
for interface between the SDN application sand
network services be
can implemented,such as routing,
With these open APIs various

Internet of Things- A Hands-On Approach

84 lOT and M2M

quality of service (QOS). access control, etc.

Standard Communication Interface (OpenFlow): SDN architecture uses a stando

communication interface between thecontrol and infrastructurelayers (Southhoun

interface). OpenFlow, which is defined by the Open Networking Foundation (ONE is
the broadly accepted SDN protocol for the Southbound intertace. With OpenFlow h
directly accessed and manipulat
the
forwarding plane of the network devices can be
OpenFlow uses the concept of flows to identify network traffic based on pre-defined
match rules. Flows can be programmed statically or dynamically by the SDN control
software. Figure 3.9 shows the components of an Openklow switch comprising of one
or more flow tables and a group table, which perform packet lookups and forwarding
and OpenFlow channel to an external controller. OpenFlow protocol is implemented
on both sides of the interface between the controller and the network devices. The
controller manages the switch via the OpenFlow switch protocol. The controller can
add. update, and delete flow entries in flow tables. Figure 3.10 shows an example of
an OpenFlow flow table. Each flow table contains a set of flow entries. Each flow
entry consists of match fields, counters, and a set of instructions to apply to matching
packets. Matching starts at the first flow table and may continue to additional flow
tables of the pipeline [83].

SDN Controller

OpenFlow
iProtocol

OpenFlow Group Table

Channel
aciainemspsdanandadis

Pipeline
Flow Table Flow Table
OpenFlow Switch

Figure 3.9: OpenFlow switch

3.4 SDN and NFV for loT
85

Acton Stats
Rule

1. Forward packet to port Packet+ byte counters

2. Encapsulate & forward to
controller
3. Drop packet
4. Send to normal processing
Pipeline

MAC Eth VLAN P IP IP TCP TCP

Switch MAC
port src dst type D src dst prot sport dport

Figure 3.10: OpenFlow flow table

3.4.2 Network Function Virtualization

Network Function Virtualization (NFV) is a technology that leverages virtualization to
consolidate the heterogeneous network devices ontoindustry standard high volume servers.
Switches and storage. NFV is complementary to SDN as NFV can providethe infrastructure
onwhich SDN can run. NEV and SDN are mutually beneficial to each other but not
dependent. Network functions can be virtualized without SDN, similarly. SDN can run
without NFV.

Virtual Network Functions

NFV
NFV Infrastructure Management
eoe

Virtual Virtual Virtual

Compute Network Storage Orchestration

Virtualization Layer

Compute Network Storage

Figure 3.l1: NFV architecture

Internet of Things- A Hands-On Approach

86 lOT and M2M

Figure 3.11 shows the NFV architecture, as being standardized by the European
Telecommunications Standards Institute (ETSI) [82]. Key clements of the NEV archito.
ecture
are as follows:
Virtualized Network Function (VNF): VNF is a software implementation
of a
network function which is capable of running overthe NFV Infrastructure (NFV
NFV Infrastructure (NFV): NFVI includes compute, network andstorageresource rces
that are virtualized.
NFV Management and Orchestration: NFV Management and Orchestration focuse
onall virtualization-specific managementtasks_and covers the orchestration and
life-cycle management of physical and/or software resources thatsupporttheinfrastruct
virtualization,and the life-cycle management of VNFs.
ictue
NFV comprises of network functions implemented in software that run on virtualized
resources in the cloud. NFV enables separation of network functions which are implemented
in software from the underlying hardware. Thus network functions can be easily tested and
upgraded by installing new software while the hardware remains the same. Virtualizing
network functions reduces the equipment costs and also reduces power consumption. The
multi-tenanted nature of the cloud allows virtualized network functions to be shared for
multiple network services. NFV is applicable only to data plane and control plane functions
in fixed and mobile networks.
Let us look at an example of how NFV can be used for virtualization of the home
networks. Figure 3.12 shows a home network with a Home Gateway that provides Wide
Area Network (WAN) connectivity to enable services such as Internet, IPTV, VolP, etc.
The Home Gateway performs various functions
including Dynamic
Host Configuration
Protocol (DHCP) server, Network Address Translation
(NAT), application specific gateway
and Firewall. The Home Gateway provides private IP addresses to each connected device
in the home. The Home
Gateway provides routing capabilities and translates the privae
IP addresses to one public address
(NAT function). The gateway also provides applicauou
specific routing for applications
such as VolP and IPTV.
Figure 3.13 shows how NFV can be used to virtualize the Home Gateway. The NFv
infrastructure in the cloud hosts a virtualized Home
Gateway. The virtualized gatew
provides private IP addresses to the devices in the home. The also
connects to network services such as
virtualized gateway
VolP and IPTV.
3.4 SDN and NFV for loT
87

Internet of Things A Hands-On Approach

88 lol and M
3.4 SDN and NFV for loT 89

Summary
In this chapter you learned about the differences and similarities between loT and M2M.
Machine-to-Machine (M2M) typically refers to networking of machines (or devices) for
the purpose of remote monitoring and control and data exchange. An M2M area network
comprises of machines (or M2M nodes) which have embedded hardware modules for sensing.
actuation and communication. M2M and loT differ in how the communication between
or non-IP based
the machines or devices happens. While M2M uses either proprietary
communication protocols for communica-
communication. While
tion within the M2M area networks, IoT uses IP-based protocols for
have the same machine
loT systems can have heterogeneous things M2M systems usually
of M2M is more on hardware with
types within an M2M area network. The emphasis
on software. M2M data is
embedded modules, whereas, the emphasis of loT is more
loT is collected
collected in point solutions and can be accessed by on-premisis applications.
and Network
in the cloud. You also learned about Software Defined Networking (SDN)
Function Virtualization (NFV) and their applications for
loT. Software-Defined Networking
the control plane from the data plane
(SDN) is a networking architecture that separates
elements of SDN include centralized network
and centralizes the network controller. Key
standard communication interface. NFV is
controller, programmable open APIs and a
virtualization to consolidate the heterogeneous network
complementary to SDN and leverages
switches and storage.
devices onto industry standard high volume servers,

Review Questions
networks?
protocols are used for M2M local
area
1. Which communication
M2M and Things in loT?
2. What the differences between Machines in
are
differ in M2M and loT?
3. How do data collection and analysis approaches
NFV?
4. What the differences between SDN and
are
various levels of loT?
5. Describe how SDN can be used for
SDN?
centralized network controller in
6. What is the function of a
loT devices?
7. Describe how NFV can be used for virtualizing