IoT AND M2M

UNIT -III

G Bhaskar Phani Ram

Email:g.bhaskarphaniram@vardhaman.org
VARDHAMAN COLLEGE OF
ENGINEERING
Shamshabad, Hyderabad – 501218, India.
 Contents
 IoT AND M2M:
 Introduction
 M2M
 Difference between IoT and M2M
 SDN and NFV for IoT
 IoT System Management with NETCONF- YANG-Need
for IoT Systems Management
 SNMP
 Network Operator Requirements
 NETCONF, YANG,
 IoT Systems Management with NETCONF-YANG
Introduction
 The term which is often used synonymously with IoT is
Machine to Machine(M2M)
 This Module mainly focuses on some of the similarities
between IoT and M2M.
 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.
Contd..
 An M2M area network comprises of machines( or M2M nodes) which
have embedded network modules for sensing, actuation and
communication various communication protocols can be used for
M2M LAN such as ZigBee, Bluetooth, M-bus, Wireless M-Bus etc.,
These protocols provide connectivity between M2M nodes within an
M2M area network.
 To enable the communication between remote M2M are network,
M2M gateways are used.
M2M Gate Way
Difference between IoT and M2M
 Though both M2M and IoT involve networking of machines or
devices, they differ in the underlying technologies, system
architectures and types of applications
 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
 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
 Applications
 M2M data is collected in point solutions and can be accessed by on-
premises applications such as diagnosis applications, service management
applications, and onpremisis 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.
 SDN and NFV for IoT
SDN:
 Software-Defined Networking (SDN) is a networking architecture that separates
the control plane from the data plane and centralizes the network controller.
 The below Figure shows the conventional network architecture built with a
specialized hardware(switches,routers etc.,)
Limitations of conventional network
architecture
 Complex Network Devices: Complex networks are getting
increasingly complex with more and more protocols being
implemented to improve link speeds and reliability.
 Management Overhead: Network Managers find it increasingly
difficult to manage multiple network devices and interfaces from
multiple vendors.
 Limited Scalability: The Analysis of computing environments
require highly scalable and network architectures, becoming
increasingly difficult with conventional networks.
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 (Northbound
interface).
 Standard Communication Interface
 SDN architecture uses a standard communication interface between
the control and infrastructure layers (Southbound interface)
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.
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 on all virtualization-specific management tasks
 Orchestration is the automated configuration, management, and
coordination of computer systems, applications, and services
IoT System Management with
NETCONF- YANG
G Bhaskar Phani Ram
Email:g.bhaskarphaniram@vardhaman.org
VARDHAMAN COLLEGE OF ENGINEERING
Shamshabad, Hyderabad – 501218, India.
Need for IoT Systems Management
 Managing multiple devices within a single system requires advanced
management capabilities
1. Automating Configuration : IoT system management
capabilities can helpin automating the system configuration.
2. Monitoring Operational & Statistical Data : Management
systems can help in monitoring opeartional and statistical data of a
system. This data can be used for fault diagnosis or
prognosis(Medical Condition).
3. Improved Reliability: A management system that allows
validating the system configurations before they are put into effect
can help in improving the system reliability.
4. System Wide Configurations : For IoT systems that consists of
multiple devices or nodes, ensuring system wide configuration can
be critical for the correct functioning of the system.
Contd..
5. Multiple System Configurations : For some systems it
may be desirable to have multiple valid configurations
which are applied at different times or in certain
conditions.
6. Retrieving & Reusing Configurations : Management
systems which have the capability of retrieving
configurations from devices can help in reusing the
configurations for other devices of the same type.
Simple Network Management Protocol(SNMP)
Contd..
 NMS executes SNMP commands to monitor and configure the
managed device.
 The Managed Device contains MIB which has all the information of
the device attributes to be managed.
 The SNMP agent runs on the device.
Limitations of SNMP
1. 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.
2. SNMP is a connectionless protocol which uses UDP as the
transport protocol, making it unreliable as there was no support for
acknowledgement of requests.
3. It is difficult to differentiate between configuration and state data in
MIBs.
4. Retrieving the current configuration from a device can be difficult
with SNMP.
5. Earlier versions of SNMP did not have strong security features.
Network Operator Requirements
 Ease of use: From the operators point of view, Ease of use is the
key requirements for any network management topology.
 Distinction between configuration and state data
 Fetch configuration and state data separately
 Configuration of the network as a whole: It is possible for
operators to configure the network as a whole rather than individual
devices.
 Configuration transactions across devices: Configuration
transactions across multiple devices must be supported
 Dump and restore configurations: It is possible to Dump
configurations from devices and restore configurations from devices
 Configuration validation: It is possible to validate
configurations.
Contd..
 Configuration database schemas: There is a need for
standardized database schemas or data models across operators.
 Comparing configurations: Devices should not arbitrarily
reorder data, so that it is possible to compare configurations.
 Role-based access control: Devices should support Role-based
access control model, so that a user is given the minimum access
necessary to perform a required task.
 Consistency of access control lists: It is possible to do
Consistency checks of access control across devices.
 Multiple configuration sets: It is possible to support Multiple
configuration sets of devices
 Support for both data-oriented and task oriented access
control: SNMP supports only data-oriented access control
NETCONF: Network Configuration
 It is Network Configuration Protocol
 A session based network management protocol
 Allows retrieving state or configuration data and manipulating data
on network devices
 It is a Layered Architecture
NETCONF
NETCONF RPC Commands
NETCONF
YANG
YANG MODULE Example
YANG Node Types
IoT Systems Management with NETCONF-
YANG