.

Unit-III

IoT and M2M

1
 IoT and M2M

Outline

• M2M
• Differences and Similarities between M2M and IoT
• SDN and NFV for IoT

2
 (Machine-to-Machine) M2M
What is M2M?

•Devices with sensors – Think of a gadget that can measure something: your fridge tracking
temperature, a tank measuring water level, or a wearable tracking your heartbeat.

•They send data to each other or a central hub – These devices use networks (like Wi-Fi,
cellular, Bluetooth, or even satellite) to share what they measured.

•Smart software makes decisions – The data gets sent to an app or system, which then
watches for specific values or patterns and acts automatically.

3
 (Machine-to-Machine) M2M
Everyday example
A smart thermostat notices the room is too cold.
It automatically tells the heater to warm up the room.
No one touched an app or dial — the devices handled it themselves.

That's M2M in action! Sensors → network → smart reaction.

Real-World Examples
Smart meters: Electric or water meters send usage info to utilities automatically for billing.
Industrial machines: Factories have sensors that spot problems early and alert
maintenance.
Fleet management: Trucks share their location and fuel levels to optimize routes.
Smart cities: Streetlights dim or brighten based on how dark or busy an area is.
4
 (Machine-to-Machine) M2M
Machine-to-Machine (M2M) refers to networking of machines (or devices) for the purpose of
remote monitoring, control and data exchange.

5
 (Machine-to-Machine) M2M
An M2M area network comprises of machines (or M2M nodes) which have embedded
hardware modules for sensing, actuation and communication.
• Various communication protocols can be used for M2M local area networks such as ZigBee,
Bluetooh, ModBus, M-Bus, Wireless M-Bus, Power Line Communication (PLC), 6LoWPAN,
IEEE 802.15.4, etc.
• The communication network provides connectivity to remote M2M area networks.
• The communication network can use either wired or wireless networks (IPbased).
• 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.

• To enable the communication between remote M2M area networks, M2M gateways are
used. 6
M2M Gateway

7
 Difference between M2M and IoT
Communication Protocols

• M2M and IoT can differ in how the communication between the machines or devices
happens.
• M2M uses either proprietary or non-IP based communication protocols for communication
within the M2M area networks.

Machines in M2M vs Things in IoT

• The "Things" in IoT refers to physical objects that have unique identifiers and can sense and
communicate with their external environment (and user applications) or their internal
physical states.
• M2M systems, in contrast to IoT, typically have homogeneous machine types within an
M2M area network. 8
 Difference between M2M and IoT
Hardware vs Software Emphasis

• While the emphasis of M2M is more on hardware with embedded modules, the emphasis
of IoT is more on software.

Data Collection & Analysis

• M2M data is collected in point solutions and often in on-premises storage infrastructure.
• In contrast to M2M, the data in IoT is collected in the cloud (can be public, private or
hybrid cloud).

9
 Difference between M2M and IoT

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
analytics applications, enterprise applications, remote diagnosis and management
applications, etc.

10
Communication in IoT vs M2M

11
 SDN

Software-Defined Networking (SDN) is a networking architecture that separates the

control plane from the data plane and centralizes the network controller.

• Software-based SDN controllers maintain a unified view of the network and make confi
-guration, management and provisioning simpler.

• The underlying infrastructure in SDN uses simple packet forwarding hardware as

opposed to specialized hardware in conventional networks.

12
 WHAT IS SDN ?
Imagine a city’s traffic system:
The control plane is like all the stoplights and road signs—they decide how cars should
flow.
The data plane is the cars driving through the city—they follow the rules from the signs.
In traditional networks, each traffic light (router or switch) decides its timing
independently.
In SDN, one central "traffic control center" (the SDN controller) makes all decisions and
tells each light what to do

13
SDN Made Simple – Three Layers, One Smart Way
A typical SDN network is made up of three layers:

Applications Layer: Network apps like firewalls, security tools, and traffic managers that
request specific behaviors.

Control Layer: The centralized controller (the “brain”) that decides how traffic should
flow.

Infrastructure Layer: The simple hardware—switches or routers—that follow the

controller’s instructions and forward data

These layers communicate using APIs—northbound (to applications) and southbound (to
hardware)
14
SDN

15
 SDN UTILITIES
•One Control Panel: Instead of configuring each network device one by one, you manage
everything from a single console.
•Automatic and Flexible: Need to change network rules? Just update software—nothing
needs unplugging or rewiring.
•Cheaper Hardware: Since intelligence is in software, network switches can be simple—and
less expensive.
•Faster Reaction: If there’s unusual traffic or a security issue, it’s easier to detect and fix from
one central place.
•Works With Any Brand: Open standards let you mix different vendors’ devices together
using the same controller

16
 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

• SDN architecture supports programmable open APIs for interface between the SDN
application and control layers (Northbound interface).

Standard Communication Interface (Open Flow)

• SDN architecture uses a standard communication 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.
17
SDN vs. Traditional Networks

18
 SDN

Real-World Examples

•A Cloud Data Center: Instead of manually reconfiguring dozens of switches whenever

you launch a new app, SDN lets you spin up virtual networks instantly via software.

•Google’s Network: Google rewrote how their network worked using SDN tech like
OpenFlow—this let them manage huge traffic flows much more efficiently.

•Virtualized Networks: With SDN, you can build a virtual network (like a software version
of your network) that works on top of existing infrastructure—even hiding differences in
hardware or locations

19
 NVF
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.

20
 NVF
NFV is like turning specialized network hardware into software apps. Instead of using
dedicated devices (like physical firewalls, routers, or load balancers), NFV runs these as
virtual apps on standard servers—imagine downloading network features instead of buying
expensive appliances.
•These virtual apps are called Virtual Network Functions (VNFs)—they perform the same jobs
but inside virtual machines (VMs) or containers.
•The physical servers and virtualization layer—plus storage and networking—make up the NFV
Infrastructure (NFVi).
•An orchestration system called MANO (Management, Automation, and Network
Orchestration) handles deploying, monitoring, and managing all VNFs.
•Before NFV: You had a separate physical machine for each job—like a standalone firewall box,
router box, load balancer box.
•With NFV: You install apps on a single computer that can do all those jobs. If you need more
power, you install more instances—no hardware change required. 21
 NVF Benefits

•Save Money: Run several network functions on one inexpensive server. No more buying
many specialized devices.
•Move Fast: Need a new network function? Spin up a virtual machine instantly—no waiting
for hardware delivery or installation.
•Easy to Scale: When traffic spikes, you can add virtual instances quickly (scale horizontally)
or allocate more power to an instance (scale vertically).
•Vendor Freedom: VNFs from different providers can run on the same infrastructure,
reducing vendor lock-in.

22
SDN vs NVF

23