PPT ON
Internet of Things(IOT)
B.TECH V Semester (R 18)
(2020-2021)
MODULE – II
IoT AND M2M
SYLLABUS :
MODULE-I IoT AND M2M
Introduction, M2M, difference between IoT and M2M, software
defined networking (SDN) and network function virtualization (NFV)
for IoT, basics of IoT system management with NETCONF- YANG.
UNIT- II
IoT AND M2M
4
Machine-to-Machine (M2M)
Machine-to-Machine (M2M) refers to networking of machines (or
devices) for the purpose of remote monitoring and control and data
exchange.
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,
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 (IPbased).
While the M2M area networks use either proprietary or non-IP
based communication protocols, the communication network
uses IP-based networks
Difference between IoT and M2M
1. 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.
2. 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
3. Hardware vs Software Emphasis
While the emphasis of M2M is more on hardware with
embedded modules, the emphasis of IoT is more on
software.
4. 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
3. 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
premisis 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.
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
Communication in IoT vs M2M
Software Defined Network
Software Defined Network
Software Defined Network
Software Defined Network
Software Defined Network
Software Defined Network
SDN Architecture
Software Defined Network
Software Defined Network
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 configuration, management
and provisioning simpler.
The underlying infrastructure in SDN uses simple packet
forwarding hardware as opposed to specialized hardware
in conventional networks.
Key elements of SDN
1. Centralized Network Controller
With decoupled control and data planes and
centralized network controller, the network
administrators can rapidly configure the network.
2. Programmable Open APIs
SDN architecture supports programmable open APIs
for interface between the SDN application and control
layers (Northbound interface).
3. Standard Communication Interface (OpenFlow)
SDN architecture uses a standard communication
interface between the control and infrastructure layers
(Southbound interface).
Key elements of SDN
OpenFlow, which is defined by the Open Networking
Foundation (ONF) is the broadly accepted SDN
protocol for the Southbound interface.
Network Function Virtualization (NFV)
Network Function Virtualization (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 and SDN are mutually beneficial to each other but
not dependent.
Key elements of NFV
1. Virtualized Network Function (VNF):
VNF is a software implementation of a network function
which is capable of running over the NFV Infrastructure
(NFVI).
2. NFV Infrastructure (NFVI):
NFVI includes compute, network and storage resources
that are virtualized. Standard Communication Interface
(OpenFlow)
3. NFV Management and Orchestrat
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 enables separation of network functions which
are implemented in software from the underlying
hardware.
Therefore network functions can be easily tested and
upgraded by installing new software while the
hardware remains the same.
NFV Use Case(Conventional home automation Architecture)
Key elements of NFV
NFV can be used to virtualize the Home Gateway.
The home gateway performs various functions including
DHCP server, Network Address Translation, application
specific gateway and firewall.
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.
Need for IoT Systems Management
Automating Configuration:
Automating the system configuration ensures that all devices
have the same configuration and variations or errors due to
manual configurations are avoided.
Monitoring Operational & Statistical Data
Improved Reliability
System Wide Configurations
Multiple System Configurations
Retrieving & Reusing Configurations
Managing a device with SNMP
Need for IoT Systems Management
SNMP is a well-known and widely used network
management protocol that allows monitoring and
configuring network devices such as routers, switches,
servers, printers, etc.
SNMP component include
Network Management Station (NMS)
Managed Device
Management Information Base (MIB)
SNMP Agent that runs on the device
Limitations of SNMP
SNMP is stateless in nature and each SNMP request
contains all the information to process the request. The
application needs to be intelligent to manage the device.
SNMP is a connectionless protocol which uses UDP as the
transport protocol, making it unreliable as there was no
support for acknowledgement of requests.
MIBs often lack writable objects without which device
configuration is not possible using SNMP.
It is difficult to differentiate between configuration and
state data in MIBs.
Retrieving the current configuration from a device can be
difficult with SNMP. Earlier versions of SNMP did not
have strong security features.
Earlier versions don’t have security present versions
Network Operator Requirements
Ease of use
Distinction between configuration and state data
Fetch configuration and state data separately
Configuration of the network as a whole
Configuration transactions across devices
Configuration deltas
Dump and restore configurations
Configuration database schemas
Comparing configurations
Role-based access control
Consistency of access control list
Multiple configuration sets.
Support for both data oriented and task oriented access control.
NETCONF protocol Layers
NETCONF Protocol
Network Configuration Protocol (NETCONF) is a session based
network management protocol.
NETCONF allows retrieving state or configuration data and
manipulating configuration data on network devices.
NETCONF works on SSH(Secure Shell Transport Protocol)
protocol.
Transport layer provides end to end connectivity and ensure
reliable delivery of messages.
NETCONF uses XML-encoded Remote Procedure calls(RPCs) for
framing request and response messages.
NETCONF protocol provides various operations to retrieve and
edit configuration data from network devices.
NETCONF Protocol
YANG Module Example
This YANG module is a YANG version of the toaster MIB
The toaster YANG module begins with the header information
followed by identity declarations which define various bread types.
The leaf nodes (‘toasterManufacturer’, ‘toasterModelNumber’ and
oasterStatus’) are defined in the ‘toaster’ container.
Each leaf node definition has a type and optionally a description
and default value.
The module has two RPC definitions (‘make-toast’ and
‘cancel-toast’).
YANG Module Example
IoT Systems Management with NETCONF-YANG
IoT Systems Management with NETCONF-YANG
Management System
Management API
Transaction Manager
Rollback Manager
Data Model Manager
Configuration Validator
Configuration Database
Configuration API
Data Provider API
UNIT-III
IoT Platforms Design Methodology
56
