M2M and IoT Design Methodologies

By
Mr.S.Selvaraj
Asst. Professor(SRG) / CSE
Kongu Engineering College
14ITO01 – Internet of Things
Unit II – IoT Design Methodology

M2M and IoT Design
Methodologies
Unit 2
Courtesy to the author of the book shown in right side.

Contents
1. M2M
2. Difference between M2M and IoT
3. Software Defined Networks (SDN)
4. Network Function Virtualization (NFV)
5. IoT Platform Design Methodologies
1/7/2021 3M2M and IoT Design Methodologies

1. M2M
• Machine-to-Machine (M2M) refers
networking of machines (devices) for the
purpose of
– Remote Monitoring and Control
– Data Exchange.

M2M Architecture
1/7/2021 M2M and IoT Design Methodologies 5
• M2M Systems Comprising of 4 parts,
– M2M Area Network
– M2M Core Network (Communication Network)
– M3M Gateways
– M2M Applications

M2M Area Network
• M2M Area Network comprises of machines (or M2M
Nodes) which have embedded hardware modules for
– Sensing
– Actuation
– Communication
• Various Communication Protocols can be used for
M2M LAN such as Zigbee, Bluetooth, ModBus, M-Bus,
Wireless M-Bus, Power Line Communication(PLC),
6LoWPAN, IEEE 802.15.4, etc.
• These Communication Protocols provide connectivity
between M2M Nodes within an M2M area network.

M2M Core Network(Communication N/w)
• The communication network provides connectivity to
remote M2M area networks.
• The communication network can use either wired or
wireless networks (IP-based).
• While the M2M area networks use either proprietary
or non-IP based communication protocols, the
communication network uses IP-based networks.
• Since non-IP based protocols are used within M2M
area networks, the M2M nodes within one network
cannot communicate with nodes in an external
network.

M2M Gateways
• To enable the communication between remote M2M area networks, M2M
gateways are used.
• The communication between the M2M nodes and the M2M Gateway is
based on the communication protocols which are native to the M2M area
networks.
• M2M gateways performs protocol translations to enable IP-connectivity
for M2M Area Networks.
• M2M gateway act as a proxy performing translations from/to native
protocols to/from Internet Protocol(IP).
• With M2M gateway, each node in an M2M area network appears as
virtualized node for external M2M area networks.

M2M Application
• M2M data is gathered into point
solutions such as
– Enterprise Applications
– Service Management Applications
– Remote Monitoring Applications
• M2M has various application domains
such as
– Smart Metering
– Home Automation
– Industrial Automation
– Smart Grids, etc.
• M2M solution designs (such as data
collection, storage architecture and
applications) are specific to the M2M
application domain.

Difference between M2M and IoT
Unit 2

Difference between M2M and IoT
• Both M2M and IoT involve networking of
machines or devices, but differ in
– Technology
– System Architecture
– Types of Applications

M2M vs IoT

Difference in M2M and IoT
• Communication Protocols
• Machines vs Things
• Hardware vs Software
• Data Collection & Analysis
• Applications

Communication in IoT vs M2M
M2M IOT
M2M uses either proprietary or non-
IP based communication protocols
within M2M area networks and M2M
communication network uses IP-based
networks.
IoT uses IP based communication
protocols.
Focus of Communication in M2M –
below network layer.
Focus of Communication in IoT -
above network layer.
M2M commonly uses Zigbee,
Bluetooth, ModBus, M-Bus, Wireless
M-Bus, Power Line communication
(PLC), 6LoWPAN, IEEE 802.15.4, etc
IoT Commonly uses HTTP, CoAP,
Websockets, MQTT, XMPP, DDS,
AMQP, TCP, UDP,etc.
It supports Point-to-Point
Communication.
It supports Cloud Communication.

Communication in IoT vs M2M

Machines in M2M vs Things in IoT
Machines in M2M Things in IOT
M2M uses homogeneous
machine types within a M2M area
network .
IoT systems can have heterogeneous
things.
(Ex: HA includes Fire Alarm, Door
Alarm, Lighting Control, etc)
Machines in M2Mrefers
to two machines “communicating,”
or exchanging data, without human
interfacing or interaction.
Things in IoT refers to physical objects
that have unique identifiers and can
sense and communicate with their
external network. (Ex for UI: IP Address,
MAC Address)
M2M have hardware
components to communicate.
Things have Software Components for
accessing, processing, and storing sensor
information, or controlling actuators.
It is less scalable It is more scalable

Hardware vs Software Emphasis
M2M IOT
The emphasis of M2M is more
on hardware with embedded
modules
The emphasis of IoT is more on
software and less on hardware.
Minimal Software Usage IoT devices run specialized software for
sensor data collection, data analysis and
interfacing with cloud.
Data Collection in M2M is tiny. Data collected in IoT is massive, cloud
based analysis is used.

Data Collection & Analysis
• M2M data is collected in point solutions and often in
on-premises storage infrastructure.
– Point Solution means, Solving one particular problem
without regard to related issues. Point solutions are widely
used to fix a problem or implement a new service quickly.
• IoT data is collected in the cloud (can be public, private
or hybrid cloud).
– Cloud based analysis
– Cloud based storage
– Cloud based application

On-premises
• “On premises” also referred to as “on-premise,” “on-
premises,” or “on-prem,” is a method of deploying software.
With on-prem, the computer programs are installed right on
the user’s computer through CDs or USB drives.
• Whereas with off-premise, the installer can be anywhere on
the Web.
• Many companies opt for on-prem because it doesn’t require
third-party access, gives owners physical control over the
server hardware and software, and does not require them to
pay month after month for access.
• Example:
• Think of how you buy your fast food meal. You could buy it and
eat it “on premise” at the fast food restaurant. Or you can call
and order your meal, and have it delivered to your home.

Applications
• M2M data is collected in point solutions and can
be accessed by on-premises applications such as
– diagnosis applications
– service management applications, and
– on-premises enterprise applications.
• IoT data is collected in the cloud and can be
accessed by cloud applications such as
– IoT analytics applications
– enterprise applications
– remote diagnosis and management applications, etc.

Final Words
• In a nutshell, both technologies enable machines to
communicate, collect, store, and exchange data;
autonomously make corresponding decisions; and
perform tasks with very minimal human
intervention.
• However, M2M and IoT are not synonymous. They
are different solutions for the enterprise.
• M2M and IoT primarily vary in terms of how they
achieve connectivity, what they aim to connect,
how scalable they are, and how data is utilized.

Software Defined Networks (SDN)
Unit 2

Need of Network Devices

List of Network Devices

Repeater

HUB

Bridge

Switch

Router

Firewall

Gateway

Think !!!! How a network
administrator can able to manage?

Solution is ....
• Network Management Protocols
– SNMP (Simple Network Management Protocol)
– ICMP (Internet Control Message Protocol)
– CDP (CISCO Discovery Protocol)
• Network Monitoring Tools and Software's
• Network Architectures like SDN,NFV,etc

Conventional Network Architecture
• Conventional architecture built with specialized
hardware (Switch, Router, etc).
• Here network devices are getting exceedingly
complex with the increasing number of
distributed protocols being implemented and
the use of propitiatory hardware and interface.
• In CNA, the control plane and data plane are
coupled.
• Control plane – carries the signalling and routing
message traffic.
• Data plane – carries the payload data traffic.

Conventional Network Architecture

Limitations of CNA
• (1) Complex Network Design
– More and more protocols being implemented to improve
link speed and reliability.
– Interoperability is limited due to lack of standard and
open interface.
– Use of propitiatory hardware and software and have slow
product life cycle.
• The CNA is well suited for
– Static traffic pattern.
– Design a specific application with large no. of protocols.
• For IoT applications which are deployed in cloud
computing environment,
– The traffic pattern are more dynamic.

Limitations of CNA
• (2)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.
• In CNA, there is a (3)limited scalability issue.
 In IoT, Virtualization technologies used in Cloud
Computing environments has increased the
number of virtual hosts.
 Distributed algorithms are helps to exchange huge
amount of data.
 So scalability is achieved in IoT.

SDN
• SDN architecture are
– Simpler
– Inexpensive
– Scalable
– Agile
– Easy to manage
• Software-Defined Networking (SDN) is a
– networking architecture that separates the control plane from
the data plane and
– centralizes the network controller.
• Software-defined networking (SDN) technology 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 - Wikipedia

SDN Architecture

SDN Layers

SDN Advantages
• Software-based SDN controllers maintain a unified view of
the network and make configuration, management and
provisioning simpler.
• The underlying infrastructure in SDN uses simple packet
forwarding hardware as opposed to specialized hardware
in conventional networks.
• The underlying network infrastructure is abstracted from
the applications.
• Network devices
– become simple with SDN as they do not require
implementations of large no.of protocols.
– receive instructions from the SDN controller on how to forward
the packets.
– can be simpler and cost less as they can be built from standard
hardware and software components.

SDN issues
• However, the intelligent centralization has its
own drawbacks when it comes to
– Security
– Scalability and
– Elasticity
• Research of SDN continues as
many emulators are being developed for
research purposes, like
– vSDNEmul
– EstiNet
– Mininet

Key Elements of SDN
• Centralized Network Controller
– With decoupled control and data planes and centralized
network controller, the network administrators can rapidly
configure the network.
• Programmable Open APIs
– Interface between the SDN application and control layers
(Northbound interface).
– Various n/w services can be implemented such as routing,
QoS, etc.
• Standard Communication Interface (OpenFlow)
– Interface between the control and infrastructure layers
(Southbound interface).
– OpenFlow, which is defined by the Open Networking
Foundation (ONF) is the broadly accepted SDN protocol for
the Southbound interface.

OpenFlow
• SDN was commonly associated with
the OpenFlow protocol.
• It’s for remote communication with network plane
elements for the purpose of determining the path
of network packets across network switches.
• With OpenFlow, the forwarding plane of the network
devices can be directly accessed and manipulated.
• Uses the concept of flows to identify network traffic
based on pre-defined match rules.
• Flows can be programmed statistically or dynamically
by SDN control software.

OpenFlow Switch and Flow Table

SDN Revolution

Network Virtual Function (NFV)
Unit 2

Network Virtual Function (NFV)
• Network Function Virtualization (NFV) is a
technology that leverages virtualization to
consolidate the heterogeneous network devices
onto industry standard high volume servers,
switches and storage.
• NFV is complementary to SDN as NFV can
provide the infrastructure on which SDN can run.
• Network functions can be visualized without SDN,
similarly, SDN can run without NFV.
• NFV architecture is standardized by ETSI.

NFV Architecture

Key Elements of NFV
• Virtualized Network Function (VNF):
– VNF is a software implementation of a network function
which is capable of running over the NFV Infrastructure
(NFVI).
• NFV Infrastructure (NFVI):
– NFVI includes compute, network and storage resources
that are virtualized.
• NFV Management and Orchestration:
– NFV Management and Orchestration focuses on all
virtualization-specific management tasks and covers the
orchestration and life-cycle management of physical
and/or software resources that support the infrastructure
virtualization, and the life-cycle management of VNFs.

NFV Advantages
• NFV comprises of network functions
implemented in software that run on virtualized
resource in the cloud.
• NFV enables separation of network functions
which are implemented in software from the
underlying hardware.
• NFV is applicable only on data plane and control
plane functions in fixed and mobile networks.

NFV Example

Conventional Home Network Architecture

Home Gateway
• Home gateway performs various functions like
– DHCP
– NAT
– Application specific gateway and firewall.
– Private IP address to each connected device in the house.
– Routing capabilities
– Translation of private IP address into Public IP address.

Home Network with Virtualized Home Gateway

Virtualized Home Gateway
• NFV can be used to virtualize the Home Gateway.
• The NFV infrastructure in the cloud hosts a virtualized
Home Gateway.
• The virtualized gateway provides private IP addresses
to the devices in the home.
• The virtualized gateway also connects to network
services such as VoIP and IPTV.

Thank You

M2M and IoT Design Methodologies

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to M2M and IoT Design Methodologies

Similar to M2M and IoT Design Methodologies (20)

More from Selvaraj Seerangan

More from Selvaraj Seerangan (20)

Recently uploaded

Recently uploaded (20)

M2M and IoT Design Methodologies