Slide 1
IoT and M2M
Sheela N Rao
Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 2
M2M and IoT
M2M is a direct communication between devices using wired
or wireless communication channels.
M2M refers to the interaction of 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.
IoT is the network of physical devices embedded with
sensors, software and electronics,
Enabling these devices to communicate with each other and
exchange data over a computer network.
The things in the IoT refer to hardware devices uniquely
identifiable through a network platform within the Internet
infrastructure.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 3
Machine to machine (M2M)
Eg: Machine to machine communication can
include industrial instrumentation,
Enabling a sensor or meter to communicate the
information it records (such as temperature, inventory
level, etc.) to application software
Application Software can use it for suitable purpose
(such as adjusting an industrial process based on
temperature or placing orders to restock inventory).
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 4
Machine to Machine (M2M)
M2M is also called Networking of machines or devices
for remote monitoring and control along with data
exchange.
An M2M area network comprises of machines (or
M2M nodes) which have embedded hardware
modules for sensing, actuation and communication.
The communication protocols provides connectivity
between M2M nodes within an M2M area network.
Various communication protocols can be used for M2M
local area networks such as ZigBee, Bluetooh, ModBus, M-
Bus, Wirless M-Bus, Power Line Communication (PLC),
6LoWPAN, IEEE 802.15.4, etc.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 5
M2M Area Network M2M Core Network
M2M Wired Network
Gateway
Application
1
Communication Protocols
Application
2
M2M Wireless Network
Gateway
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 6
The communication network provides connectivity to
remote M2M area networks.
The communication network can use either wired or
wireless networks (IP based).
The M2M area networks use either proprietary
(owned by the designer) or non-IP based
communication protocols,
Since non-IP based protocols are used within M2M
area networks,
M2M nodes within one network cannot communicate with
nodes in an external network.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 7
M2M gateways are used to enable the communication
between remote M2M area networks
Communication between M2M node and M2M
gateway is based on the communication protocol that
is native (local) to M2M area network.
Gateways act as proxy by performing translations
from/to native (local) protocols to/from Internet
Protocol(IP)
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 8
M2M Gateway
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 9
Difference between IoT and M2M
1. Communication Protocols:
M2M and IoT differs in the way communication takes
place between the machines and devices
M2M uses either proprietary or non-IP based
communication protocols for communication within the
M2M area networks
IoT uses IP based communication protocols
M2M focus is on Protocols below network layer
ZigBee, Bluetooth, ModBus, M-Bus,
Power Line
Communication (PLC), 6LoWPAN, IEEE 802.15.4 etc.
IoT focus is on Protocol above network layer.
HTTP, CoAP, WebSockets, MQTT, DDS etc.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 10
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 11
2. Machine in M2M vs Things in IoT
Things in IoT –
Physical objects that have unique identifiers (IP address or
MAC address)
Can sense and communicate with external environment, user
applications or their physical states
Have software components for accessing, processing and
storing sensor information or controlling actuators.
IoT system can have heterogeneous things. Like home
automation system will have fire alarm, door alarm, lighting
control, temperature control etc.
Machines in M2M –
Homogeneous machines within an M2M area network
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 12
4. Applications
M2M – One to one, On premises application
IoT – Cloud based application
5. Hardware vs Software Emphasis
M2M – Emphasis is on Hardware
IoT – Emphasis is on Software (and Hardware)
IoT
devices run specialized software for sensor data collection,
data analysis, interfacing with the cloud through IP based
communication.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 13
5. Data Collection and Analysis
M2M data is collected in point solutions and on-
premises storage infrastructure.
IoT data is collected from cloud (public, private or
hybrid)
Data can be analyzed and results can be stored in cloud
database.
Data and analysis results are visualized with the cloud based
applications.
Centralized controller will be aware of the status of all the end
nodes and sends control commands to the nodes.
Observer nodes will process information and use it for
different applications but do not perform control function.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 14
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 15
SDN – Software Defined Networking
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 16
Software-defined networking (SDN)
It is a technology which is
An approach to network management
That enables dynamic, programmatically efficient network
configuration
In order to improve network performance and monitoring
Making it more like cloud computing than traditional
network management.
It is a networking architecture that separates the
control plane from the data plane and centralizes the
network controller.
Separation of control plane and data (forwarding)
plane is called disaggregation
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 17
Conventional Networking
Conventional network architecture are built with
specialized hardware (switches, routers etc.)
Network devices are becoming more and more complex
due to
Increasing number of distributed protocols being used.
Proprietary hardware and interfaces being used
Control plane and data plane are coupled
Control plane is the part of the network that carries the
signalling and routing message traffic
Data plane is the part of the network that carries the payload
data traffic.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 18
Limitations of Conventional Network Architectures
Complex Network Devices
Conventional networks are becoming more and more
complex due to more protocols being implemented to
improve link speed and reliability.
Interoperability is limited due to lack of standard and open
interfaces.
Network devices use proprietary hardware and software
and have slow product life-cycles that limits the innovation.
Suites static traffic patterns and large protocol designed for
specific application.
IoT applications use dynamic traffic pattern – making
changes to meet this is difficult
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 19
Management Overhead
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
Virtualization technology used in cloud computing requires large
number of virtual host that need access to network.
IoT applications are hosted in the cloud and distributed across
multiple virtual machines that require huge amount of data
exchange.
All this require large scalability and easy to manage network with
less manual intervention.
This is not supported in conventional network architectures
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 20
SDN Architecture
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 21
Key Elements of SDN
Centralized Network Controller
Network administrators can rapidly configure the network.
With the use of decoupled control and data planes and
centralized network controller
Programmable Open APIs
SDN architecture supports programmable open APIs for interface
between the SDN application and control layers (Northbound
interface).
Standard Communication Interface (OpenFlow)
SDN architecture uses a standard communication interface
between the control and infrastructure layers (Southbound
interface).
OpenFlow, defined by the Open Networking Foundation (ONF) is
the broadly accepted SDN protocol for the Southbound interface.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 22
OpenFlow
Allows Forwarding (Data) plane to be
accessed and manipulated.
Identifies network traffic based on pre-
defined match rules.
Flow can be programmed statically or
dynamically
OpenFlow switch consists of one or more
Flow Table and Group Table - to perform
packet lookup and forwarding
OpenFlow is implemented on both the
sides of the interface between controller
and network devices.
The controller manages the switch
through the OpenFlow switch protocol.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 23
The controller can add,
update and delete flow
entries in the flow table.
Each Flow table contains a set
of flow entries.
Each Flow entry consists of
Match fields,
Counters
Set of instructions to apply to
matching packet
Matching starts at the first
flow table and may continue
to additional flow tables of
the pipelines.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 24
Comparison
Conventional Network SDN
1. Hardware Based Networking Software Based Networking
2. Data and Control Plane are mounted on Data and Control Planes are decoupled by
same plane. New Protocol for every API or OpenFlow
service.
3. Static or manual configuration and Automatic reconfiguration and repolicing
reconfiguration takes time logically centralized
4. All packets are lead in the same way Block specific packets are prioritized
5. Provides limited information about Global or comprehensive view of the
networks network is provided
6. Difficult to replace existing program with Easy to program according to application
new ideas and works and user needs. Quick software upgrades
can be done
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 25
Advantages
Centralization of control
Simplification of control
Traffic programmability
Greater agility (Swift operation)
Capacity to generate policy-driven network
supervision
Ability to implement network automation
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 26
NFV – Network Function Virtualization
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 27
NFV and SDN are beneficial to each other but not
dependent.
NFV can provide infrastructure on which SDN can
work
NFV is Proposed by members of the European
Telecommunications Standards Institute in October
2012,
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 28
NFV Architecture
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 29
Key Elements of NFV architecture
Virtualized Network Function (VNF)
Software implementation of network function which is capable
of running over the NFV Infrastructure (NFVI)
Softwares to carry out specific networking tasks, such as
routing or load balancing.
An individual VNF can span multiple VMs, and administrators
can chain VNFs together to deliver broader network services.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 30
NFV Infrastructure (NFVI)
Provides the underlying structure to host the VMs and run the
VNF applications.
Includes compute, network and storage resources that are
virtualized
Consists of hypervisor-based virtualization layer that abstracts
the resources and makes them available to the VNFs.
The NFVI can span multiple locations to support a distributed
network.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 31
NFV Management and Orchestration (NFV MANO)
This unit focuses on all virtualization-specific management
tasks
The MANO framework handles all VNF-related tasks, such as
chaining, connectivity and lifecycle management.
Covers the orchestration and life-cycle management of
physical and /or software resources that supports the
infrastructure virtualization and life-cycle management
It is also responsible for managing, monitoring and optimizing
NFVI hardware and virtual resources.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Slide 32
Highlights
NFV consists 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.
Network can be easily tested and upgraded by
installing new softwares, keeping hardware same.
Virtualization network functions reduces the
equipment costs and power consumption
NFV is applicable only to data plane and control plane
functions in fixed and mobile networks.
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
Sheela N Rao, Dept. of EI, SJCE, JSSSTU, Mysuru
