Internet of Things &

Applications
Chapter 2: M2M

Abhishek Vaghela
E&C Department
M2M
● The term often used synonymously with IoT is Machine - to -
Machine (M2M).

● Though IoT and M2M are often used interchangeably , these

terms are evolved from different background.

● Machine-to-Machine (M2M) refers to networking of machines (or

devices) for the purpose of remote monitoring and control and
data exchange.
M2M
● The term often used synonymously with IoT is Machine - to -
Machine (M2M).

● Though IoT and M2M are often used interchangeably , these

terms are evolved from different background.

● Machine-to-Machine (M2M) refers to networking of machines (or

devices) for the purpose of remote monitoring and control and
data exchange.
M2M System Architecture
M2M System Architecture
• 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, Wirless 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 (IP- based).

• While the M2M area networks use either proprietary or non-IP based communication
protocols, the communication network uses IP-based networks.
M2M gateway
● 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.
Difference between IoT and M2M
● 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.
Difference between IoT and M2M
● 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).
Difference between IoT and M2M
● 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
Communication in IoT vs M2M
Software Defined Networking
● Software-Defined Networking (SDN) is a networking architecture that separates the
control plane from the data plane and centralizes the network controller.

Data plane refers to all the functions and processes that forward
packets/frames from one interface to another. Control plane refers to
all the functions and processes that determine which path to use
Routing protocols are examples..
 Conventional Network Architecture
• Figure shows the conventional
network architecture.

• Built with switches / routers

• N/W devices in conventional N/W are

getting exceedingly complex with
increasing number of distributed
protocols being implemented as their
proprietary hardware and interfaces.

• In conventional n/w control plane and

data plane are coupled.

• Control plane is the part of the n/w

that carries the signaling and routing
message traffic while the data plane
is the part of the n/w that carries the
payload data traffic.
Limitations of the conventional n/w architecture

● Complex Network Devices

○ More Protocols , Increasing Link Speed and reliability
● Management Overhead
● Multiple network devices, Upgradation

● Limited Scalability
SDN Architecture

SDN Layer

SDN Architecture
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
● Standard Communication Interface (OpenFlow)
○ SDN architecture uses a standard communication interface between the control and
infrastructure layers OpenFlow, which is defined by the Open Networking Foundation (ONF) is
the broadly accepted SDN protocol for the Southbound interface.
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.

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 Use Case
● 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.

Home n/w architecture with virtualized home gateway

Conventional home n/w architecture
● The analog input gives us a value between 0 and 1023, 0 being no voltage and 1023 being
5V. To figure out what this voltage converts to in degrees Celsius we will need to first find the
percentage of 5V on the input. This can be done by dividing the sensor Input by 1024.
● As we know from the datasheet, the sensor will output 0 – 1.75V over a range of 175 degrees
(-50° to 125°) so that means every 0.01V equals 1 degree. We will need to convert the
percentage of input to voltage by multiplying by 5V.
● Since we are not measuring 0° – 175° we will need to shift the output value so that the
minimum reading of -50° equals a voltage reading of 0. We do this by subtracting 0.5 from
the output voltage. Our new value now ranges from -0.5 to 1.25 (which looks remarkably
similar to our temperature range!)
● To convert from millivolts to degrees Celsius we will need to multiply by 100.
CODE
PIR Sensor
Ultrasonic Sensor
Temperature Sensor Interfacing
pinMode(2, OUTPUT)

digitalWrite(2, HIGH)

Serial.begin(9600)
digitalRead(2)

analogRead(A2)
 Temperature Sensor Interfacing with Arduino

The sensor can measure a fairly wide range of temperature (-50°C to 125°
C), is fairly precise (0.1°C resolution)
Switch Interface