UNIT-1:

INTRODUCTION
Definition:

 A dynamic global network infrastructure with self- configuring capabilities based on

standard and interoperable communication protocols
 Where,
-Physical and virtual "things" have identities, physical attributes,
-Virtual personalities
-Use intelligent interfaces,
-Are seamlessly integrated into the information network
-Often communicate data associated with users and their environments

Examples of IOT:

• Elderly Care Monitoring- Open/Close sensor, presence Sensor, Motion sensor

• Bike Helmet Crash Sensors- ICEdot Crash Sensor
• Smart Smoke Detectors
• Smart Fire Extinguishers
• Home Energy Monitoring and Control
• Smart Door Locks
• Soil monitoring
Characteristics of an IoT:

 Dynamic & Self Adapting:

IoT devices and systems may have the capability to dynamically adapt with the
changing contexts and take actions based on their operating conditions.
 Self-Configuring:
Allowing a large number of devices to work together to provide certain functionality
 Inter Operable Communication Protocols:
Support a number of interoperable communication protocols and can communicate
with other devices and also with infrastructure.
 Unique Identity:
Each IoT device has a unique identity and a unique identifier.
 Integrated into Information Network:
That allow them to communicate and exchange data with other devices and systems.
PHYSICAL DESIGN:

 The "Things" in IoT usually refers to IoT devices which have unique identities
 It can Perform:
- remote sensing,
- actuating and
- monitoring capabilities.
 Iot Devices can:
- Exchange data with other connected devices and applications (directly or
- indirectly), or
- Collect data from other devices and process the data locally or
- Send the data to centralized servers or cloud-based application back-ends for
- processing the data, or
- Perform some tasks locally and other tasks within the IoT infrastructure,
- based on temporal and space constraints

General Block Diagram of an IOT Devices:

 An IoT device consists of several interfaces for connections to other devices , both
wired and wireless. These Include:
- I/O interfaces for sensors
- Interfaces for Internet connectivity
- Memory and storage interfaces
- Audio/video interfaces.
IoT Protocols:
Link Layer Protocol

Protocols determine how data is physically sent over the networks physical layer or medium.
Link layer determines how packets are coded and signaled by the h/w device over the
medium to which the host is attached.
Network/Internet Layer Protocol

• Responsible for sending IP datagrams from source n/w to destination n/w. Performs
the host addressing and packet routing. Datagrams contains source and destination
address.
• IPv4: Internet Protocol version4 is used to identify the devices on a n/w using a
hierarchical addressing scheme. 32 bit address.
• IPv6: Internet Protocol version6 uses 128 bit address scheme.
• It operates in 2.4 GHz frequency range and data transfer 250 kb/s.

Transport Layer

• Provides end-to-end message transfer capability independent of the underlying n/w.

Set up on connection with ACK as in TCP and without ACK as in UDP. Provides
functions such as error control, segmentation, flow control and congestion control.
 • Protocols:
TCP:

Transmission Control Protocol used by web browsers, email. Connection

oriented and stateless protocol. IP Protocol deals with sending packets, TCP ensures
reliable transmission of protocols in order. Avoids n/w congestion and congestion
collapse. ·
UDP:
User Datagram Protocol is connectionless protocol. Useful in time sensitive
applications, very small data units to exchange. Transaction oriented and stateless protocol.
Does not provide guaranteed delivery
Application Layer

• Defines how the applications interface with lower layer protocols to send data over
the n/w. Enables process-to-process communication using ports.
Protocols:

• HTTP: Hyper Text Transfer Protocol that forms foundation of WWW. Follow
request response model Stateless protocol. ·
• CoAP: Constrained Application Protocol for machine-to-machine (M2M)
applications with constrained devices, constrained environment and constrained n/w.
Uses client server architecture.

LOGICAL DESIGN:

 Logical design of an IoT system refers to an abstract representation of the entities and
processes without going into the low-level specifics of the implementation.
IoT Functional blocks:
 An IoT system comprises of a number of functional blocks that provide the system the
capabilities for identification, sensing, actuation, communication, and management.
 Functional Blocks are:
 Device
 Communication
 Services
 Management
 Security
 Application
Application:
• It is an interface that provides a control system that use by users to view the status and
analyze of system.
Management:
• This block provides various functions that are used to manage an IoT system.
Services:
• This block provides some services like monitoring and controlling a device and publishing
and deleting the data and restore the system.
Communication:
• This block handles the communication between the client and cloud-based server and
sends/receives the data using protocols.
Security:
• This block is used to secure an IoT system using some functions like authorization, data
security, authentication, 2 step verification, etc.
Device:
• These devices are used to provide sensing and monitoring control functions that collect the
data from the outer environment.

IoT Communication Models:

 Request-Response
 Publish-Subscribe
 Push-Pull
 Exclusive Pair
 Request-Response

 Request-Response is a communication model in which the client sends requests to the server
and the server responds to the requests.
 When the server receives a request, it decides how to respond, fetches the data, retrieves
resource representations, prepares the response, and then sends the response to the client.

 Publish-Subscribe

 Publish-Subscribe is a communication model that involves publishers, brokers and

consumers.
 Publishers are the source of data. Publishers send the data to the topics which are
managed by the broker. Publishers are not aware of the consumers.
 Consumers subscribe to the topics which are managed by the broker.
 When the broker receives data for a topic from the publisher, it sends the data to all
the subscribed consumers.

 Push-Pull
 Push-Pull is a communication model in which the data producers push the data to
queues and the consumers pull the data from the queues. Producers do not need to be
aware of the consumers.
 Queues help in decoupling the messaging between the producers and consumers.
  Queues also act as a buffer which helps in situations when there is a mismatch
between the rate at which the producers push data and the rate rate at which the
consumers pull data.

 Exclusive Pair
 Exclusive Pair is a bidirectional, fully duplex communication model that uses a
persistent connection between the client and server.
 Once the connection is setup it remains open until the client sends a request to close
the connection.
 Client and server can send messages to each other after connection setup.

IoT Communication APIs:

 REST-based Communication APIs
- Representational State Transfer (REST)
 Web Socket-based Communication APIs
 REST-based Communication APIs

 Representational State Transfer (REST) is a set of architectural principles by which you can
design web services and web APIs that focus on a system’s resources and how resource states
are addressed and transferred.
 REST APIs follow the request-response communication model.
 The REST architectural constraints apply to the components, connectors, and data elements,
within a distributed hypermedia system.

 Web Socket-based Communication APIs

 WebSocket APIs allow bidirectional, full duplex communication between clients and servers.
 WebSocket APIs follow the exclusive pair communication model
IOT ENABLING TECHNOLOGIES

IoT is enabled by several Technologies:

 Wireless Sensor Networks
 Cloud Computing
 Big Data Analytics
 Communication Protocols
 Embedded Systems

 Wireless Sensor Networks

 A Wireless Sensor Network(WSN) comprises of distributed devices with sensors

which are used to monitor the environmental and physical conditions
 A WSN consist of a number of end-nodes and routers and a coordinator
 Each node can have several sensors attached to it.
 Each node can also acts as a routers
 Coordinator collects data from all nodes
 Coordinator acts as gateway that connects WSN to the internet.
 Data rate: up to 250KBps. Range: upto 100 Meters
 Routers are responsible for routing the data packets from end-nodes to the
coordinator.
 Some Examples of WSNs used in IoT systems are described as follows:
o Weather monitoring system use WSNs in which the nodes collect
temperature humidity and other data which is aggregated and analyzed.
o Soil moisture monitoring system use WSNs to monitor soil moisture at
various locations.
o Surveillance system use WSNs for collecting Surveillance data (such as
motion detection data)
o Structural health monitoring system use WSNs to monitor the health of
structures ( buildings, bridges) by collecting vibration data from sensor nodes
deployed at various points in the structure.

 Cloud Computing

 Cloud computing is a transformative computing paradigm that involves delivering

applications and services over the internet
 Provides computing, networking and storage resources on demand
 Cloud computing services are offered to users in different forms:
1. Infrastructure-as-a-Service(IaaS)
2. Platform-as-a-Service(PaaS)
3. Software-as-a-Service(SaaS)
IaaS: Clients can use storage to install and manage operating systems and any desired
applications.( i.e Virtual machines + virtual storage)
- Ex: Web Hosting.
Paas : Clients can install, build and modify or control applications.
- Ex: App cloud, Google App Engine
Saas : Clients can access and use software at remote location using a web browser.
- Ex: Google documents

 Big Data Analytics

 Collection of data whose volume, velocity or variety is too large and difficult
to store, manage, process and analyze the data using traditional databases.
 Big Data analytics is the process of collecting, organizing and analyzing large
sets of data to discover patterns and other useful information.
 Bigdata Analytics involves:
 Data cleansing-correcting,removing,replacing
 Data munging (Data Wrangling)-converting data from one format to
another
 Data Processing and
 Data Visualization
 Examples:
• Sensor data generated by IoT system such as weather monitoring stations.
• Machine sensor data collected from sensors embedded in industrial and energy
systems for monitoring their health and detecting Failures.
• Health and fitness data generated by IoT devices such as wearable fitness
bands
• Data generated by IoT systems for location and tracking of vehicles
• Data generated by retail inventory monitoring system

 Communication Protocols

• Communication protocols form the backbone of IoT systems and enable network
connectivity and coupling to applications
• Communication Protocols allow devices to exchange data over the network
• Other Functions
- Sequence control(ordering data packets)
- Flow control(controlling transfer rate)
- Retransmission of lost packets
• In IoT we used MQTT, COAP, AMQP etc. protocols.
  Embedded Systems:

 An Embedded System is a computer system that has computer Hardware and software
embedded to perform specific tasks
 Key components of an embedded system include:
 micro processor / micro controller
 memory- RAM, ROM, cache
 Networking units – Ethernet , WIFI adapters
 Input/output units- display , keyboard etc.,
 Storage- Flash memory

IOT LEVELS & DEPLOYMENT TEMPLATES

 An IoT system comprises of the following components:
 Device
 Resource
 Controller Service
 Database
 Web Service
 Analysis Component
 Application
 Device: An IoT device allows identification, remote sensing, actuating and remote
monitoring capabilities. You learned about various examples of IoT devices in section

 Resource: Resources are software components on the IoT device for accessing,
processing, and storing sensor information, or controlling actuators connected to the
device. Resources also include the software components that enable network access
for the device.

 Controller Service: Controller service is a native service that runs on the device and
interacts with the web services. Controller service sends data from the device to the
web service and receives commands from the application (via web services) for
controlling the device.

 Database: Database can be either local or in the cloud and stores the data generated
by the IoT device.

 Web Service: Web services serve as a link between the IoT device, application,
database and analysis components. Web service can be either implemented using
HTTP and REST principles (REST service) or using WebSocket protocol
(WebSocket service).
 Analysis Component: The Analysis Component is responsible for analyzing the IoT
data and generate results in a form which are easy for the user to understand.

 Application: IoT applications provide an interface that the users can use to control
and monitor various aspects of the IoT system. Applications also allow users to view
the system status and view the processed data.

 IoT Level-1

 A level-1 IoT system has a single node/device that performs sensing and/or
actuation, stores data, performs analysis and hosts the application
 Level-1 IoT systems are suitable for modeling low cost and low-complexity
solutions where the data involved is not big and the analysis requirements are
not computationally intensive.
 IoT Level-2

 A level-2 IoT system has a single node that performs sensing and/or actuation
and local analysis.
 Data is stored in the cloud and application is usually cloud based.
 Level-2 IoT systems are suitable for solutions where the data involved is big,
however, the primary analysis requirement is not computationally intensive
and can be done locally itself.

 IoT Level-3
 A level-3 IoT system has a single node. Data is stored and analyzed in the cloud and
application is cloud based.
 Level-3 IoT systems are suitable for solutions where the data involved is big and the
analysis requirements are computationally intensive.
 IoT Level-4

 A level-4 IoT system has multiple nodes that perform local analysis. Data is stored in
the cloud and application is cloud-based.
 Level-4 contains local and cloud based observer nodes which can subscribe to and
receive information collected in the cloud from IoT devices.
 Level-4 IoT systems are suitable for solutions where multiple nodes are required, the
data involved is big and the analysis requirements are computationally intensive.
 IoT Level-5

 A level-5 IoT system has multiple end nodes and one coordinator node.
 The end nodes that perform sensing and/or actuation.
 Coordinator node collects data from the end nodes and sends to the cloud.
 Data is stored and analyzed in the cloud and application is cloud-based.
 Level-5 IoT systems are suitable for solutions based on wireless sensor networks, in
which the data involved is big and the analysis requirements are computationally
intensive.
 IoT Level-6

 A level-6 IoT system has multiple independent end nodes that perform sensing
and/or actuation and send data to the cloud.
 Data is stored in the cloud and application is cloud-based.
 The analytics component analyzes the data and stores the results in the cloud
database.
 The results are visualized with the cloud-based application.
 The centralized controller is aware of the status of all the end nodes and sends
control commands to the nodes.
IOT & 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.
 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.
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.
 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).

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

Communication in IoT vs M2M

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.
 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 South bound 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.

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.

IOT SYSTEM MANAGEMENT WITH NETCONF-YANG

Need for IoT Systems Management:
• Automating Configuration
• Monitoring Operational & Statistical Data
• Improved Reliability
• System Wide Configurations
• Multiple System Configurations
• Retrieving & Reusing Configurations

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
o Network Management Station (NMS)
o Managed Device
o Management Information Base (MIB)
o 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.
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 validation
• Configuration database schemas
• Comparing configurations
• Role-based access control
• Consistency of access control lists:
• Multiple configuration sets
• Support for both data-oriented and task-oriented
• access control
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

• NETCONF works on SSH 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 modeling language
called YANG.
• NETCONF provides a clear separation of the configuration and state data.
• The configuration data resides within a NETCONF configuration datastore on the
server.

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.
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’).

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