IOT & M2M

 Introduction
 M2M Vs IoT
 SDN & NFV
 IoT System Management
 SNMP
 Network Operator Requirements
 NETCONF
 YANG
 NETOPEER
1
 INTRODUCTION

IoT
 M2M
 TV-Remote
 Mobile-AC

2
 MACHINE-TO-MACHINE (M2M)

 Machine-to-Machine
(M2M) refers to
networking of machines
(or devices)
 for the purpose of remote
monitoring and control
and dataexchange.
3
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, 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.

4
 MACHINE-TO-MACHINE (M2M)

 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.
5
DIFFERENCE BETWEEN IOT &MACHINE-TO-MACHINE (M2M)

6
DIFFERENCE BETWEEN IOT &MACHINE-TO-MACHINE (M2M)

7
IOT & MACHINE-TO-MACHINE (M2M) COMMUNICATION

10
 Communication in M2M Communication in IoT
● IoT communication relies on internet-based
● M2M communication involves direct, point-to- protocols (e.g., MQTT, HTTP, CoAP) to connect
point communication between devices, often devices globally.
without internet.
● Data is sent to cloud platforms for storage,
● Data is typically exchanged using proprietary processing, and analytics, enabling smart
protocols like MODBUS or via cellular SMS/USSD. decision-making.
● Operates through localized systems or central ● Uses wireless technologies like Wi-Fi,
servers, with less emphasis on cloud integration. Bluetooth, Zigbee, and cellular networks
(4G/5G).
● Often uses wired connections or cellular networks,
with limited focus on wireless flexibility. ● Designed for scalability, allowing seamless
integration of new devices into a network.
● Security relies on isolation of systems, making it
less complex but often less adaptable. ● Security depends on encryption and advanced
protocols to protect data in transit and storage.
● Primarily used for industrial automation, remote
monitoring, and utility control. ● Focuses on enabling smart ecosystems like
smart homes, healthcare, and connected
 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
configuration, management and
provisioning simpler.
 The underlying infrastructure in SDN uses
simple packet forwarding hardware as
opposed to specialized hardware in
conventional networks.

12
To understand software-defined networks, we need to understand the
various planes involved in networking.
1. Data Plane
2. Control Plane

Data plane:
All the activities involving as well as resulting from data packets sent
by the end-user belong to this plane. This includes:
Forwarding of packets.
Segmentation and reassembly of data.
Replication of packets for multicasting.

Control plane:
All activities necessary to perform data plane activities but do not
involve end-user data packets belong to this plane. In other words,
this is the brain of the network. The activities of the control plane
include:
Making routing tables.
Setting packet handling policies.
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 (OpenFlow)
 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.

14
 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.

15
 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.

16
NVF-USE CASE

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

18
NEED FOR IOT SYSTEM MANAGEMENT

 Automating Configuration
 Monitoring Operational & Statistical Data
 Improved Reliability
 System Wide Configurations
 Multiple System Configurations
 Retrieving & Reusing Configurations

19
 SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP)

 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

20
 DRAWBACKS 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.

21
 NETWORK OPERATOR REQUIREMENTS

 Ease of use
 Configuration validation
 Distinction between configuration and
state data  Configuration database schemas
 Fetch configuration and state data  Comparing configurations
separately
 Role-based access control
 Configuration of the network as a whole
 Consistency of access control lists:
 Configuration transactions across
services  Multiple configuration sets
 Configuration deltas  Support for both data-oriented and
 Dump and restore configurations task oriented access control

22
 NETCONF

 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

23
 NETCONF

 NETCONF works on SSH (Secure Shell) transport 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.
 The RPC layer provides mechanism for encoding of RPC calls and notifications.
 NETCONF provides various operations to retrieve and edit configuration data from network devices.
 The Content Layer consists of configuration and state data which is XML-encoded.
 The schema of the configuration and state data is defined in a data modelling language called YANG.
 NETCONF provides a clear separation of the configuration and state data.
 The configuration data resides within a NETCONF configuration data store on the server.

24
 YANG
 Yet Another Next Generation (YANG)
 YANG is a data modeling language used to model configuration and state data manipulated by the NETCONF
protocol
 YANG modules contain the definitions of the configuration data, state data, RPC calls that can be issued and
the format of the notifications.
 YANG modules defines the data exchanged between the NETCONF client and server.
 A module comprises of a number of 'leaf' nodes which are organized into a hierarchical tree structure.
 The 'leaf' nodes are specified using the 'leaf' or 'leaf-list' constructs.
 Leaf nodes are organized using 'container' or 'list' constructs.
 A YANG module can import definitions from other modules.
 Constraints can be defined on the data nodes, e.g. allowed values.
 YANG can model both configuration data and state data using the 'config' statement.

25
 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
26
5/24/
NETOPEER-NETCONF-YANG

27
5/24/