FUNDAMENTAL of IoT
Dr P PRABAKARAN
Assistant Professor
Department of Computer Applications
School of Computing Sciences
Vels Institute of Science Technology and Advanced Studies, Chennai
ONLINE LEARNING
FUNDAMENTAL of IoT
Block -1
FUNDAMENTAL of IoT
FUNDAMENTAL OF INTERNET of THINGS
FUNDAMENTALS OF IoT
The Internet of Things (IoT) refers to a system of interrelated, internet-
connected objects that are able to collect and transfer data over a wireless
network without human intervention.
AN ARCHITECTURAL OVERVIEW
AN ARCHITECTURAL OVERVIEW
Internet of Things (IoT) technology has a wide variety of applications and use of Internet of
Things is growing so faster.
The architecture of IoT depends upon its functionality and implementation in different
sectors. Still, there is a basic process flow based on which IoT is built.
Stage IoT architecture
 Sensing Layer
 Network Layer
 Data processing Layer
 Application Layer
AN ARCHITECTURAL OVERVIEW
Sensing Layer:
Sensors, actuators, devices are present in this Sensing layer. These Sensors or Actuators
accepts data, processes data and emits data over network.
Network Layer
Internet/Network gateways, Data Acquisition System (DAS) are present in this layer. DAS
performs data aggregation and conversion function (Collecting data and aggregating data
then converting analog data of sensors to digital data etc).
AN ARCHITECTURAL OVERVIEW
Data processing Layer
This is processing unit of IoT ecosystem. Here data is analyzed and pre-processed before
sending it to data center from where data is accessed by software applications.
Application Layer
This is last layer of 4 stages of IoT architecture. Data centers or cloud is management stage of
data where data is managed and is used by end-user applications like agriculture, health
care, aerospace, farming, defense, etc.
MAIN DESIGN PRINCIPLES AND NEEDED CAPABILITIES
MAIN DESIGN PRINCIPLES AND NEEDED CAPABILITIES
Do Research On Your Target Audience
IoT development is more about experiences and services than products. So, it all boils down
to users and how they perceive and interact with devices either independently or
collectively.
Work On Delivering Contextual Experiences
People only know that devices connected to the internet (and each other) constitute an IoT
ecosystem.
MAIN DESIGN PRINCIPLES AND NEEDED CAPABILITIES
Focus On Creating Value
The onset of any new concept, product or service fetches reactions from two types of
people.
 Those who can’t wait to get hands on with it
 Those who are reluctant to use it.
Leverage The Use Of Prototype
One setback tech experts are still experiencing with IoT solutions is that an established IoT
ecosystem is difficult to upgrade or modify.
MAIN DESIGN PRINCIPLES AND NEEDED CAPABILITIES
Prioritize Security First
Digital systems come with their own set of concerns with respect to safety and security.
Implement IoT design mechanisms that identify and eliminate concerns before they creep in.
Effective Data Management
IoT system is going to generate massive amounts of data every second or minute.
Consider Human Connection
IoT is a great concept to bring people together and talk about matters that deserve attention.
IoT STANDARDS CONSIDERATIONS
Important considerations for IoT solutions
 IoT Security
 IoT Analytics
 IoT Device (Thing) Management
 Low-Power, Short-Range IoT Networks
 Low-Power, Wide-Area Networks
 IoT Processors
 IoT Operating Systems
 Event Stream Processing
 IoT Platforms
 IoT Standards and Ecosystems
IoT STANDARDS CONSIDERATIONS
IoT Security
IoT introduces a wide range of new security risks and challenges to the IoT devices
themselves, their platforms and operating systems, their communications, and even the
systems to which they're connected.
IoT Analytics
IoT business models will exploit the information collected by "things" in many ways.
IoT STANDARDS CONSIDERATIONS
IoT Device (Thing) Management
Long-lived nontrivial "things" will require management and monitoring. This includes device
monitoring, firmware and software updates, diagnostics, crash analysis and reporting,
physical management, and security management. IoT also brings new problems of scale to
the management task.
Low-Power, Short-Range IoT Networks
Selecting a wireless network for an IoT device involves balancing many conflicting
requirements, such as range, battery life, bandwidth, density, endpoint cost and operational
cost.
IoT STANDARDS CONSIDERATIONS
Low-Power, Wide-Area Networks
Traditional cellular networks don't deliver a good combination of technical features and
operational cost for those IoT applications that need wide-area coverage combined with
relatively low bandwidth, good battery life, low hardware and operating cost, and high
connection density.
IoT Processors
The processors and architectures used by IoT devices define many of their capabilities, such
as whether they are capable of strong security and encryption, power consumption, whether
they are sophisticated enough to support an operating system, updatable firmware, and
embedded device management agents.
IoT STANDARDS CONSIDERATIONS
IoT Operating Systems
Traditional operating systems (OSs) such as Windows and iOS were not designed for IoT
applications. They consume too much power, need fast processors, and in some cases, lack
features such as guaranteed real-time response.
Event Stream Processing
Some IoT applications will generate extremely high data rates that must be analyzed in real
time.
IoT STANDARDS CONSIDERATIONS
IoT Platforms
IoT provides three key platform components;
(1) low-level device control and operations such as communications, device monitoring and
management, security, and firmware updates
(2) IoT data acquisition, transformation and management.
IoT Standards and Ecosystems
Although ecosystems and standards aren't precisely technologies, most eventually
materialize as application programming interfaces (APIs).
DEVICES AND GATEWAYS
DEVICES AND GATEWAYS
Gateway provides bridge between different communication technologies which means we
can say that a Gateway acts as a medium to open up connection between cloud and
controller (sensors / devices) in Internet of Things (IoT).
It enables a connection between sensor network and Internet along with enabling IoT
communication.
As IoT devices work with low power consumption (Battery power) in other words they are
energy constrained so if they will directly communicate to cloud/internet it won’t be
effective in terms of power.
DEVICES AND GATEWAYS
Key functionalities of IoT Gateway :
 Establishing communication bridge
 Provides additional security.
 Performs data aggregation.
 Pre processing and filtering of data.
 Provides local storage as a cache/ buffer.
DEVICES AND GATEWAYS
Working of IoT Gateway :
 Receives data from sensor network.
 Performs Pre processing, filtering and cleaning on unfiltered data.
 Transports into standard protocols for communication.
 Sends data to cloud.
LOCAL AND WIDE AREA NETWORKING
Local Area Network (LAN):
LAN is a group of network devices which allow the communication between connected
devices.
Wide Area Network (WAN):
WAN covers the large area than LAN as well as MAN such as: Country/Continent etc. WAN is
expensive and should or might not be owned by one organization.
LOCAL AND WIDE AREA NETWORKING
BUSINESS PROCESSES IN IoT
IoT uses are to automate process, gather valuable information, extend business functions,
and trigger rules, source predictive analytics and big data, among other useful objectives.
Implementing IoT business processes in your companies:
 To define business process to improve and identify the problem you want to solve.
 Use an end-to-end approach.
 Get on board the right people
 Be persistent but acknowledgeable to failure
EVERYTHING AS A SERVICE (XAAS)
Everything-as-a-Service is a term for services and applications that users can access on the
Internet upon request.
In everything as a Service various number of tools and technologies and services are
provided to users as a service.
With XaaS, business is simplified as they have to pay for what they need. This everything as a
Service is also known as anything as a Service.
EVERYTHING AS A SERVICE (XAAS)
Examples of XaaS :
 Software as a Service (SaaS)
 Platform as a Service (PaaS)
 Disaster Recovery as a Service (DRaaS)
 Infrastructure as a service (IaaS)
Online Learning
FUNDAMENTAL OF INTERNET of THINGS
Block – 2
REFERENCE ARCHITECTURE
Fundamental of IoT
REFERENCE ARCHITECTURE of IoT -STATE OF THE ART
REFERENCE ARCHITECTURE of IoT -STATE OF THE ART
REFERENCE ARCHITECTURE of IoT -STATE OF THE ART
Security
The IoT process has intent: to provide enhanced insights, operational efficiencies, new
revenue streams and improved processes.
So it’s important to be overly security-concerned when considering that it might also
provide convenience in the development, build and install processes.
People and Business Process
One common cause of IoT ‘stumble’ is the way it is often started—from within one group.
This is where business units struggle most with IoT, as it takes a much larger perspective to
maximize the value to the entire business.
REFERENCE ARCHITECTURE of IoT -STATE OF THE ART
Data Abstraction
Data Abstraction collects different data pieces and makes them available for analysis. These
days every enterprise has some level of Business Intelligence (BI) skills, but it’s imperative to
engage these resources in the early stages of your project discovery.
Storage
The Cloud is often assumed with IoT projects, but it should not be a given. There are
situations where an IoT infrastructure needs to be placed on-premise.
REFERENCE ARCHITECTURE of IoT -STATE OF THE ART
Edge/Fog/Mist
Edge - There are intelligent devices at multiple points within the network. These devices,
known as the Edge. Devices that reside on the very edge of the network, pushing
intelligence and processing power closer to the source and outside of the cloud and primary
data repository.
Fog - newer than the Edge and originally introduced by Cisco to increase scalability. As its
name implies, it is closer to the ground, below the Cloud, outside the Edge. Fog nodes bring
distributed compute to the local area network level, each node taking in data from sensors
within a defined geographic area.
REFERENCE ARCHITECTURE of IoT -STATE OF THE ART
Mist: The Mist further extends the Edge and Fog models by pushing compute into the
sensors and actuator units themselves.
Network
The primary job of any network is to transfer data, route data traffic and manage
throughput. This has evolved to support different communications protocols.
Sensors
There’s virtually no end to the type of sensor that may be required for various projects, the
choices are wide open. They’re as varied as the problems they help to solve. Most look like a
postage stamp, a little widget.
REFERENCE MODEL AND ARCHITECTURE
REFERENCE MODEL AND ARCHITECTURE
IoT domain model
A domain model serves as a tool for human communication between people working in the
domain in question and between people who work across different domains.
Sensors:
These are simple or complex Devices that typically involve a transducer that converts
physical properties such as temperature into electrical signals.
REFERENCE MODEL AND ARCHITECTURE
Actuators:
These are also simple or complex Devices that involve a transducer that converts electrical
signals to a change in a physical property (e.g. turn on a switch or move a motor).
These Devices also include potential communication capabilities, storage of intermediate
commands, processing, and conversion of digital signals to analog electrical signals.
Tags:
Tags in general identify the Physical Entity that they are attached to. In reality, tags can be
Devices or Physical Entities but not both, as the domain model shows.
FUNCTIONAL VIEW OF IoT REFERENCE
The IoT Functional Model aims at describing mainly the Functional Groups (FG) and their
interaction with the ARM, while the Functional View of a Reference Architecture describes
the functional components of an FG, interfaces, and interactions between the components.
FUNCTIONAL VIEW OF IoT REFERENCE
Device functional group
The Device FG contains all the possible functionality hosted by the physical Devices that are
used for increment the Physical Entities. This Device functionality includes sensing,
actuation, processing, storage, and identification components, the sophistication of which
depends on the Device capabilities.
Communication functional group
The Communication FG abstracts all the possible communication mechanisms used by the
relevant Devices in an actual system in order to transfer information to the digital world
components or other Devices.
FUNCTIONAL VIEW OF IoT REFERENCE
IoT Service functional group
The IoT Service FG corresponds mainly to the Service class from the IoT Domain Model, and
contains single IoT Services exposed by Resources hosted on Devices or in the Network.
Virtual Entity functional group
The Virtual Entity FG corresponds to the Virtual Entity class in the IoT Domain Model, and
contains the necessary functionality to manage associations between Virtual Entities with
themselves as well as associations between Virtual Entities and related IoT Services.
FUNCTIONAL VIEW OF IoT REFERENCE
IoT Service Organization functional group
The purpose of the IoT Service Organisation FG is to host all functional components that support the
composition and orchestration of IoT and Virtual Entity services. Moreover, this FG acts as a service
hub between several other functional groups.
IoT Process Management functional group
The IoT Process Management FG is a collection of functionalities that allows smooth integration of
IoT-related services (IoT Services, Virtual Entity Services, and Composed Services) with the
Enterprise (Business) Processes.
INFORMATION VIEW OF IoT REFERENCE
Virtual Entity in the IoT Domain Model is the “Thing” in the Internet of Things, the IoT
information model captures the details of a Virtual Entity- centric model. Similar to the IoT
Domain Model, the IoT Information Model is presented using Unified Modelling Language
(UML) diagrams.
INFORMATION VIEW OF IoT REFERENCE
DEPLOYMENT AND OPERATIONAL VIEW
Addresses how an IoT system can be realized by selecting the proper technologies, devices,
resources, and services, as well as guidelines for architects/developers through the different
decisions to be made.
REAL-WORLD DESIGN CONSTRAINTS-
INTRODUCTION
The Internet of Things has been facing many areas like Information Technology, Healthcare,
Data Analytics and Agriculture. The main focus is on protecting privacy as it is the primary
reason for other challenges including government participation.
Scalability:
Billions of internet-enabled devices get connected in a huge network, large volumes of data
are needed to be processed. The system that stores, analyses the data from these IoT
devices needs to be scalable.
REAL-WORLD DESIGN CONSTRAINTS- INTRODUCTION
Interoperability:
Technological standards in most areas are still fragmented. These technologies need to be
converged. Which would help us in establishing a common framework and the standard for
the IoT devices.
Security and Personal Privacy:
There has been no research in security vulnerabilities and its improvements. It should
ensure Confidentiality, Integrity and Availability of personal data of patient.
TECHNICAL DESIGN CONSTRAINTS
Technical requirements – coverage, energy efficiency, data rate, other features relevant to
specific applications (mobility, positioning, latency, density);
Lack of encryption
Although encryption is a great way to prevent hackers from accessing data, it is also one of
the leading IoT security challenges. These drives like the storage and processing capabilities
that would be found on a traditional computer.
TECHNICAL DESIGN CONSTRAINTS
Insufficient testing and updating
With the increase in the number of IoT(internet of things) devices, IoT manufacturers are
more eager to produce and deliver their device as fast as they can without giving security
too much of although.
IoT Malware and ransomware
Increases with increase in devices. Ransomware uses encryption to effectively lock out users
from various devices and platforms and still use a user’s valuable data and info.
TECHNICAL DESIGN CONSTRAINTS
HARDWARE IS POPULAR AGAIN
IoT Hardware includes a wide range of devices such as devices for routing, bridges, sensors
etc. These IoT devices manage key tasks and functions such as system activation, security,
action specifications, communication, and detection of support-specific goals and actions.
BLE and Wireless Sensors
Bluetooth Low Energy (BLE) is a wireless data transfer technology. BLE is aimed at novel
applications in the healthcare, fitness, security, and home entertainment industries.
DATA REPRESENTATION AND VISUALIZATION
Data Visualization is referred as the process of representing information or data into a visual
context that provides useful insights from the data.
It is a way to display the vast amount of data in a meaningful way that clearly presents
trends and patterns from the raw data collected.
DATA REPRESENTATION AND VISUALIZATION
Role of data visualization in IOT
Internet of Things (IOT) and data are interlinked together as IOT is all about collecting data
and making sense of it. One of the challenges for IoT industry is data analysis and
interpretation.
The data collected is impractical if we cannot extract useful information from it and analyse
and translate that information to identify hidden trends, outliers, and patterns in data and
make data-driven decisions.
INTERACTION AND REMOTE CONTROL
There are many possible interactions between devices and users in the world of the Internet
of Things.
1. Machine-human interaction, where we use an IoT device to log data on a server, which is
then used to display a graph that can be understood and used by the final user.
2. human-machine interaction, where the user is triggering a command to a remote device,
for example, to activate a lamp remotely.
3. machine-to-machine interaction, where two or more devices are directly talking to each
other, without the intervention of any human.
INTERACTION AND REMOTE CONTROL
Remote Monitoring of IoT Devices creates remote monitoring for IoT device data
transmission or data validity.
Remote Monitoring of IoT Devices ingests real-time device data from IoT devices to assess
the state of each IoT device and send you notifications if there are data transmission issues
or out of range data.
Remote Monitoring of IoT Devices also provides a framework for collecting diagnostic
information for deriving outcome-oriented insights about the health of your assets.
INTERACTION AND REMOTE CONTROL
Remote Monitoring of IoT Devices creates remote monitoring for IoT device data
transmission or data validity.
Remote Monitoring of IoT Devices ingests real-time device data from IoT devices to assess
the state of each IoT device and send you notifications if there are data transmission issues
or out of range data.
Remote Monitoring of IoT Devices also provides a framework for collecting diagnostic
information for deriving outcome-oriented insights about the health of your assets.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
Physical Layer
Physical medium can be copper wire, fiber optic cable, twisted pair or even wireless channel.
Functions of PHY layer:
1. It converts MAC layer format suitable to be transported over the medium.
2. It adds forward error correction functionality to enable error correction at the receiver.
MAC Layer
MAC is the short form of Medium Access Control Layer. It interfaces PHY layer and Upper
layers.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
Functions of MAC layer
It incorporates MAC header at the start of upper layer IP packet and CRC (Cyclic Redundancy
check) at the end of IP packet.
Incorporates ARQ (Automatic repeat request) functionality as a means for requesting
retransmission in case of errors.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
3GPP
The 3rd Generation Partnership Project (3GPP) is a collaborative project between a groups of
telecommunications associations with the initial goal of developing globally applicable
specifications for third-generation (3G) mobile systems.
3GPP standards are designed for mobile systems based on evolved GSM core networks.
Technical Specification Groups in 3GPP
Radio Access Networks (RAN),
Services & Systems Aspects (SA),
Core Network & Terminals (CT)
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
MTC
The MTC (Machine Type Communications or Machine to Machine Communication) system is
one of the most promising technologies to provide IoT (Internet of Things) applications.
MTC describes data communication between two entities without the involvement of a
human.
MTC has great potential in a wide range of applications and services. The potential
applications are widespread across different industries, including healthcare, logistics,
manufacturing, process automation, energy, and utilities.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
IEEE 802.11
IEEE (Institute of Electrical and Electronics Engineers) 802.11 refers to the set of standards
that define communication for wireless LANs (wireless local area networks, or WLANs).
IEEE Standard for Information Technology--Telecommunications and Information Exchange
between Systems - Local and Metropolitan Area Networks--Specific Requirements - Part 11:
Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.
The IEEE developed an international standard for WLANs. The 802.11 standard focuses on the
bottom two layers of the OSI model, the physical layer (PHY) and data link layer (DLL).
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
IEEE 802.11 Architecture
Two network architectures are defined in the IEEE 802.11 standard
Infrastructure network - An infrastructure network is the network architecture for providing
communication between wireless clients and wired network resources.
Point-to-point (ad-hoc) network - An ad-hoc network is the architecture that is used to
support mutual communication between wireless clients.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
IEEE 802.11 Architecture
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
IEEE 802.15
IEEE 802.15.4 is a low-cost, low-data-rate wireless access technology for devices that are
operated or work on batteries. This describes how low-rate wireless personal area networks
(LR-WPANs) function.
Properties of IEEE 802.15
 Standardization and alliances
 Physical Layer
 MAC layer
 Topology
 Security
 Competitive Technologies
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
Advantages of IEEE 802.15.4 :
 cheap cost
 long battery life,
 Quick installation
 simple
 extensible protocol stack
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
WIRELESS HART
Wireless HART is the latest release of Highway Addressable Remote Transducer (HART)
Protocol.
WirelessHART is a Wireless Mesh Network Communications Protocol designed to meet the
needs for process automation applications.
HART encompasses the most number of field devices incorporated in any field network.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
WIRELESS HART
HART Physical Layer
Derived from IEEE 802.15.4 protocol.
It operates only in the 2.4 GHz ISM band.
Employs and exploits 15 channels of the band to increase reliability.
HART Application Layer
Handles communication between gateways and devices via a series of command and response
messages.
Responsible for extracting commands from a message, executing it and generating responses.
This layer is seamless and does not differentiate between wireless and wired versions of HART.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
WIRELESS HART
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
WIRELESS HART-ZWAVE
Z-wave is one of the Personal Area Network(PAN) technology used. Z-wave proprietary
wireless communication protocol is designed for home automation similar to zigbee.
It uses low power wireless communication technology, designed to control home based
electronic products using remote control and smoke alarm.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
WIRELESS HART-ZWAVE
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
WIRELESS HART-ZWAVE
System Specifications
Works at 868.42 MHz (in Europe) and 908.42 MHz MHz (in US) frequency range
Data rate(bandwidth) is about 9.6, 40, 200 kbps
Modulation is GFSK in the 900MHz ISM band
Range is about 30 meter(indoors) and 100 meters(outdoors)
Home automation and security
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
WIRELESS HART -BLUETOOTH LOW ENERGY
Bluetooth there are different versions based on data rate and distance coverage
requirements such as version 1.2, 2.0, 2.1, 3.0, 4.0 and 4.1. Bluetooth version 4.0 is known as
Bluetooth Low Energy (BLE).
Once the devices are connected with bluetooth link the connection is maintained even if
there is no data to be transferred.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
WIRELESS HART -BLUETOOTH LOW ENERGY
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
BLE Message Exchange
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
ZIGBEE SMART ENERGY
Zigbee devices are used everywhere including smart energy, medical and in home automation.
It has two bands of operation 868/915MHz and 2450MHz. 868/915 band provides about 20-40Kb/s
and 2450MHz band provides about 250 kb/s data rates.
Joining the Zigbee Network
There are two ways to join a zigbee network viz. MAC association and network re-join.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
ZIGBEE SMART ENERGY
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
DASH7
The Dash7 technology is promoted by DASH7 Alliance. This technology provides long battery life and
coverage of about 2Km in indoor places. Following are the features of Dash7 wireless technology.
Dash7 protocol and home automation basics in IoT,M2M
The RFID technologies such as NFC and Dash7 is widely used in WSN(wireless sensor networking).
Most of the smartphones will have these technologies integrated to provide many facilities to the
users.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
DASH7
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
DASH 7
Different gateways in DASH 7
Blinker: It only transmits and does not use a receiver.
EndPoint: It can transmit and receive the data. It also supports wake-up events.
Subcontroller: It is full featured device. It is not always active. It uses wake on scan cycles
similar to end points.
Gateway: It connects D7A network with the other network.It will always be online. It always
listens unless it is transmitting.
DASH7 defines two types of frames viz. a foreground frame and a background frame.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
NETWORK LAYER
A network is a group of two or more connected computing devices. Usually all devices in the
network are connected to a central hub.
Network-to-network connections are what make the Internet possible. The "network layer" is
the part of the Internet communications process where these connections occur, by sending
packets of data back and forth between different networks.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
NETWORK LAYER
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
NETWORK LAYER
The main functions performed by the network layer are
 Routing - When a packet reaches the router's input link, the router will move the packets
to the router's output link
 Logical Addressing - Logical addressing is also used to distinguish between source and
destination system.
 Internetworking - logical connection between different types of networks.
 Fragmentation - The fragmentation is a process of breaking the packets into the smallest
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
PHY/MAC Layer
NETWORK LAYER
The main functions performed by the network layer are
 Routing - When a packet reaches the router's input link, the router will move the packets
to the router's output link
 Logical Addressing - Logical addressing is also used to distinguish between source and
destination system.
 Internetworking - logical connection between different types of networks.
 Fragmentation - The fragmentation is a process of breaking the packets into the smallest
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
IPv4
IP stands for Internet Protocol and v4 stands for Version Four (IPv4). IPv4 was the primary
version brought into action for production within the ARPANET in 1983.
IP version four addresses are 32-bit integers which will be expressed in decimal notation.
IPv4 supports three different types of addressing modes
 Unicast Addressing Mode
 Broadcast Addressing Mode
 Multicast Addressing Mode
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
IPv4
Unicast Addressing Mode
Data is sent only to one destined host. The Destination Address field contains 32- bit IP
address of the destination host. Here the client sends data to the targeted server.
Broadcast Addressing Mode
The packet is addressed to all the hosts in a network segment. The Destination Address field
contains a special broadcast address, i.e. 255.255.255.255.
Multicast Addressing Mode
This mode is a mix of the previous two modes, i.e. the packet sent is neither destined to a
single host nor all the hosts on the segment.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
IPv4
Parts of IPv4
Network part
The network part indicates the distinctive variety that’s appointed to the network. The
network part conjointly identifies the category of the network that’s assigned.
Host Part:
The host part uniquely identifies the machine on your network. This part of the IPv4 address
is assigned to every host.
Subnet number:
This is the nonobligatory part of IPv4. Local networks that have massive numbers of hosts are
divided into subnets and subnet numbers are appointed to that.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
IPv4
Advantages of IPv4
 IPv4 security permits encryption to keep up privacy and security.
 IPV4 network allocation is significant and presently has quite 85000 practical routers.
 It becomes easy to attach multiple devices across an outsized network while not NAT.
 This is a model of communication so provides quality service also as economical
knowledge transfer.
 IPV4 addresses are redefined and permit flawless encoding.
 Routing is a lot of scalable and economical as a result of addressing is collective more
effectively.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
IPv6
 Internet Protocol Version 6 (IPv6) is a network layer protocol that enables data
communications over a packet switched network.
 Packet switching involves the sending and receiving of data in packets between two nodes
in a network.
 The working standard for the IPv6 protocol was published by the Internet Engineering Task
Force (IETF) in 1998.
 IPv6 was intended to replace the widely used Internet Protocol Version 4 (IPv4) that is
considered the backbone of the modern Internet.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
IPv6
Type of IPv6 addressing methods :
 Unicast - Unicast Address identifies a single network interface. A packet sent to a unicast
address is delivered to the interface identified by that address.
 Multicast - Multicast Address is used by multiple hosts, called as Group, acquires a
multicast destination address. These hosts need not be geographically together
 Anycast - Anycast Address is assigned to a group of interfaces. Any packet sent to an
anycast address will be delivered to only one member interface
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
6LoWPAN
The term "6LoWPAN" stands for IPv6 over Low Power Wireless Personal Area Networks. This
is open standard defined in RFC6282 by IETF. It allows IPv6 packets to be passed to/from
6LoWPAN network.
6LoWPAN provides a means of carrying packet data in the form of IPv6 over IEEE 802.15.4
and other networks.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
6LoWPAN
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
6LoWPAN
Benefits or advantages of 6LoWPAN
6LoWPAN is a mesh network which is robust, scalable and self healing.
It offers long range of communication which detects signals below noise level.
It consumes less power as it uses reduced transmission time (using short time pulses).
Hence this saves energy and consecutively battery can be used for very long duration.
It offers large network which can be used by millions of devices.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
6TiSCH
6TiSCH is a working group at the IETF, which is standardizing how to combine IEEE802.15.4
time-slotted channel hopping (TSCH) with IPv6.
The 6TiSCH protocol stack combines the ease of use of IPv6 with the industrial performance
of TSCH. 6TiSCH uses IEEE802.15.4 O-QPSK 2.4 GHz as its PHY and IEEE802.15.4e at the
Medium Access Control (MAC) layer.
6TiSCH defines an operational sub-layer (6top) which coordinates a mote’s negotiations with
its neighbors to allocate cells.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
DHCP
Dynamic Host Configuration Protocol(DHCP) is an application layer protocol which is used to
provide:
Subnet Mask (Option 1 – e.g., 255.255.255.0)
Router Address (Option 3 – e.g., 192.168.1.1)
DNS Address (Option 6 – e.g., 8.8.8.8)
Vendor Class Identifier (Option 43 – e.g., ‘unifi’ = 192.168.1.9 ##where unifi = controller)
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
DHCP
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
DHCP
Advantages
 Centralized management of IP addresses.
 Ease of adding new clients to a network.
 Reuse of IP addresses reducing the total number of IP addresses that are required.
 Simple reconfiguration of the IP address space on the DHCP server without needing to
reconfigure each client.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
ICMP
The Internet Control Message Protocol (ICMP) is a network layer protocol used by network
devices to diagnose network communication issues.
ICMP is mainly used to determine whether or not data is reaching its intended destination in
a timely manner. Commonly, the ICMP protocol is used on network devices, such as routers.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
RPL
RPL (Routing Protocol for Low-Power and Lossy Networks) is a routing protocol for wireless
networks with low power consumption and generally susceptible to packet loss.
RPL is a routing protocol that is based on the IPv6 lower power wireless personal area
network, which is connected to the IP network by the sink node.
 Distance vector;
 Source routing: allow the sender to specify the route;
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
CORPL (cognitive RPL)
CORPL protocol is the extension of the RPL protocol, which is termed as cognitive RPL. This
network protocol is designed for cognitive networks and uses DODAG topology.
CORPL protocol makes two new modifications in the RPL protocol. It uses opportunistic
forwarding to forward a packet between the nodes.
Each node of CORPL protocol keeps the information of forwarding set rather than parents
only maintaining it.
IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS
CARP
CARP (Channel-Aware Routing Protocol) is a distributed routing protocol. It is designed for
underwater communication. It has lightweight packets so that it can be used for Internet of
Things (IoT). It performs two different functionalities:
Network initialization and data forwarding. CARP protocol does not support previously
collected data.
TRANSPORT & SESSION LAYER PROTOCOLS
TRANSPORT LAYER
TCP stands for Transmission Control Protocol a communications standard that enables
application programs and computing devices to exchange messages over a network.
It is designed to send packets across the internet and ensure the successful delivery of
data and messages over networks.
TCP is one of the basic standards that define the rules of the internet and is included
within the standards defined by the Internet Engineering Task Force (IETF).
TRANSPORT & SESSION LAYER PROTOCOLS
MPTCP (Multipath TCP)
The Multipath TCP (MPTCP) project looks to change that view of networking by adding
support for multiple transport paths to the endpoints; it offers a lot of benefits, but
designing a deployable protocol for today's Internet is surprisingly hard.
MPTCP represents the most recent efforts that the Internet Engineering Task Force (IETF)
is promoting to enhance the TCP capabilities to handle multiple addresses.
Multipath TCP is particularly useful in multipath data centre and mobile phone
environments. All mobiles allow you to connect via WiFi and 3G network.
TRANSPORT & SESSION LAYER PROTOCOLS
MPTCP (Multipath TCP)
TRANSPORT & SESSION LAYER PROTOCOLS
UDP
User Datagram Protocol (UDP) is a Transport Layer protocol. UDP is a part of the Internet
Protocol suite, referred to as UDP/IP suite.
Unlike TCP, it is an unreliable and connectionless protocol. So, there is no need to
establish a connection prior to data transfer.
UDP Header
UDP header is an 8-bytes fixed and simple header, while for TCP it may vary from 20 bytes
to 60 bytes.
TRANSPORT & SESSION LAYER PROTOCOLS
UDP
TRANSPORT & SESSION LAYER PROTOCOLS
UDP
UPD features
 UDP is used when acknowledgement of data does not hold any significance.
 UDP is good protocol for data flowing in one direction.
 UDP is simple and suitable for query based communications.
 UDP is not connection oriented.
TRANSPORT & SESSION LAYER PROTOCOLS
DCCP (Datagram Congestion Control Protocol)
DCCP is acronym of Datagram Congestion Control Protocol. The DCCP Datagram Congestion
Control Protocol is a transport layer protocol in TCP/IP model.
Millions person uses internet at a time because of this a lot of data flow every time on internet
network.
The data flow generates congestion in the network. Congestion cause the internet speed slow and
poor performance occurs.
To overcome this problem DCCP Datagram Congestion Control Protocol invented by IETF (Internet
Engineering Task Force).
TRANSPORT & SESSION LAYER PROTOCOLS
DCCP (Datagram Congestion Control Protocol)
TRANSPORT & SESSION LAYER PROTOCOLS
DCCP (Datagram Congestion Control Protocol)
Function of DCCP Datagram Congestion Control Protocol
DCCP protocol provides a reliable data delivery from one device to another device. There
is no any other control system available on internet network.
TRANSPORT & SESSION LAYER PROTOCOLS
SCTP (Stream Control Transmission Protocol)
Stream Control Transmission Protocol (SCTP) is a transport-layer protocol that ensures
reliable, in-sequence transport of data.
SCTP provides multihoming support where one or both endpoints of a connection can
consist of more than one IP address.
Stream Control Transmission Protocol (SCTP) is an IP Transport Layer protocol.
SCTP exists at an equivalent level with User Datagram Protocol (UDP) and Transmission
Control Protocol (TCP), which provides transport layer functions to many Internet
applications.
TRANSPORT & SESSION LAYER PROTOCOLS
SCTP (Stream Control Transmission Protocol)
SCTP Services
 Aggregate Server Access Protocol (ASAP)
 Bearer-independent Call Control (BICC)
 Direct Data Placement Segment chunk (DDP-segment)
 Direct Data Placement Stream session control (DDP-stream)
 Diameter in a DTLS/SCTP DATA chunk (Diameter-DTLS)
TRANSPORT & SESSION LAYER PROTOCOLS
SCTP (Stream Control Transmission Protocol)
SCTP Features
Delivery of data in chunks within an independent stream eliminates unnecessary head-of-
line blocking.
Path selection and monitoring functionality to select a primary data transmission path and
test the connectivity of the transmission path.
Validation and acknowledgment mechanisms protect against flooding attacks and provide
notification of duplicated or missing data chunks.
TRANSPORT & SESSION LAYER PROTOCOLS
TLS (Transport Layer Security)
Transport Layer Security (TLS) is the most widely used protocol for implementing
cryptography on the web.
TLS uses a combination of cryptographic processes to provide secure communication over
a network.
TLS provides a secure enhancement to the standard TCP/IP sockets protocol used for
Internet communications.
The secure sockets layer is added between the transport layer and the application layer in
the standard TCP/IP protocol stack.
TRANSPORT & SESSION LAYER PROTOCOLS
DTLS (Datagram Transport Layer Security)
DTLS is a protocol based on TLS that is capable of securing the datagram transport. DTLS is
well-suited for securing applications and services that are delay-sensitive (and hence use
datagram transport), tunneling applications such as VPNs, and applications that tend to
run out of file descriptors or socket buffers.
TRANSPORT & SESSION LAYER PROTOCOLS
SESSION LAYERHTTP
Functions of Session Layer
Session Layer works as a dialog controller through which it allows systems to communicate
in either half-duplex mode or full duplex mode of communication.
This layer is also responsible for token management, through which it prevents two users
to simultaneously access or attempting the same critical operation.
This layer allows synchronization by allowing the process of adding checkpoints, which are
considered as synchronization points to the streams of data.
This layer is also responsible for session checkpointing and recovery.
TRANSPORT & SESSION LAYER PROTOCOLS
CoAP
Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with
constrained nodes and constrained networks in the Internet of Things.
CoAP is designed to enable simple, constrained devices to join the IoT even through
constrained networks with low bandwidth and low availability.
It is generally used for machine-to-machine (M2M) applications such as smart energy and
building automation.
TRANSPORT & SESSION LAYER PROTOCOLS
CoAP
TRANSPORT & SESSION LAYER PROTOCOLS
XMPP
XMPP is the Extensible Messaging and Presence Protocol, a set of open technologies for
instant messaging, presence, multi-party chat, voice and video calls, collaboration,
lightweight middleware, content syndication, and generalized routing of XML data.
Architecture of the XMPP Protocol
XMPP technologies use a decentralized client-server architecture related to the
architecture used for the World Wide Web and the email network. In decentralized client-
server architecture, client developers can focus on user experience, and server developers
can focus on reliability and scalability.
TRANSPORT & SESSION LAYER PROTOCOLS
XMPP
TRANSPORT & SESSION LAYER PROTOCOLS
AMQP
Advanced Message Queuing Protocol (AMQP) is created as an open standard protocol that
allows messaging interoperability between systems, regardless of message broker vendor
or platform used; With AMQP, you can use whatever AMQP-compliant client library you
want, and any AMQP-compliant broker you want. Message clients using AMQP are
completely agnostic.
It defines a set of messages capabilities which must be made available by an AMQP
compliant server implementation (like RabbitMQ). Including rules of how messages must
be routed and stored within the broker to follow the AMQ Model.
TRANSPORT & SESSION LAYER PROTOCOLS
AMQP
TRANSPORT & SESSION LAYER PROTOCOLS
MQTT
MQTT stands for Message Queuing Telemetry Transport. MQTT is a machine to machine
internet of things connectivity protocol.
It is an extremely lightweight and publish-subscribe messaging transport protocol.
This protocol is useful for the connection with the remote location where the bandwidth is
a premium.
It makes it easy for communication between multiple devices.
TRANSPORT & SESSION LAYER PROTOCOLS
MQTT
Architecture of MQTT
Message
Client
Server or Broker
TOPIC
TRANSPORT & SESSION LAYER PROTOCOLS
MQTT
Architecture of MQTT
SERVICE LAYER PROTOCOLS & SECURITY
Service Layer
Service Layer is an abstraction over domain logic. It defines application's
boundary with a layer of services that establishes a set of available operations
and coordinates the application's response in each operation.
Features of Service Layer Design
Faster and easy Integration with multiple applications
Light weight design to provide scalability
Self discoverable
SERVICE LAYER PROTOCOLS & SECURITY
Service Layer
Service Layer design has 3 discrete sections with a 3-Tier application:
Domain/functional Model
Series of REST Endpoints
A means for storing domain objects, or a persistence layer
SERVICE LAYER PROTOCOLS & SECURITY
Service Layer
SERVICE LAYER PROTOCOLS & SECURITY
Service Layer
oneM2M
oneM2M is the global standards initiative that covers requirements, architecture, API
specifications, security solutions and interoperability for Machine-to-Machine and IoT
technologies.
SERVICE LAYER PROTOCOLS & SECURITY
Service Layer
ETSI M2M
Existing M2M solutions are highly fragmented and typically dedicated to a single application.
(Eg. Fleet management, meter reading, vending machines)
Multitude of technical solutions and dispersed standardization activities result in the slow
development of the global M2M market.
Standardization is a key enabler to remove the technical barriers and ensure interoperable
M2M services and networks.
SERVICE LAYER PROTOCOLS & SECURITY
Service Layer
Features of ETSI M2M
Identification of the M2M application and the M2M devices
Asynchronous and synchronous communication.
Store and forward mechanism based on policies for optimizing the communication
Location information
Device management based both on OMA DM (wireless) and BBF TR-69 (wireline).
SERVICE LAYER PROTOCOLS & SECURITY
OMA (OPEN MOBILE ALLIANCE)
The OMA-DM protocol is Client-initiated remote HTTPS DM session.
OMA Device Management is a device management protocol specified by the Open Mobile
Alliance (OMA) Device Management (DM) Working Group and the Data Synchronization (DS)
Working Group.
SERVICE LAYER PROTOCOLS & SECURITY
OMA (OPEN MOBILE ALLIANCE)
OMA Device management is intended to support the following uses:
Provisioning – Configuration of the device (including first time use), enabling and disabling
features
Device Configuration – Allow changes to settings and parameters of the device
Software Upgrades – Provide for new software and/or bug fixes to be loaded on the device,
including applications and system software
Fault Management – Report errors from the device, query about status of device
SERVICE LAYER PROTOCOLS & SECURITY
OMA Features:
 Full support of the OMA-DM and OMA-CP protocol
 Extensive SDK with implementation samples
 Support of OMA-DM data model
 Support for Linux and non-Linux OS
 Provisioning
 Bootstrap
SERVICE LAYER PROTOCOLS & SECURITY
SECURITY IN IoT PROTOCOLS
IoT security refers to the methods of protection used to secure internet-connected or
network-based devices. The term IoT is incredibly broad, and with the technology continuing
to evolve, the term has only become broader.
From watches to thermostats to video game consoles, nearly every technological device has
the ability to interact with the internet, or other devices, in some capacity.
SERVICE LAYER PROTOCOLS & SECURITY
MQTT
MQTT is one of the most common security protocols used in internet of things security. It was
invented by Dr Andy Stanford-Clark and Arlen Nipper in 1999.
MQTT stands for Message Queuing Telemetry Transport and is a client-server communicating
messaging transport protocol.
The MQTT runs over TCP/IP or over other conventions that provide requested, lossless, two-
way associations.
SERVICE LAYER PROTOCOLS & SECURITY
MQTT
Features of MQTT
 Its a simple and extremely lightweight protocol with easy and fast data transmission.
 MQTT is designed for constrained devices as well as low-bandwidth, unreliable or high-latency
networks.
 Minimum use of data packets ensures less network usage.
 It’s based on the messaging technique and so, is extremely fast and reliable.
 It’s ideal for IoT applications.
SERVICE LAYER PROTOCOLS & SECURITY
CoAP (Constraint Application Protocol)
CoAP (Constraint Application Protocol) is a web transfer protocol designed for constrained
devices (like microcontrollers) and the constrained network called low power or lossy
networks.
It is also one of the most popular protocols to secure internet of things applications.
SERVICE LAYER PROTOCOLS & SECURITY
CoAP (Constraint Application Protocol)
Features of CoAP
Similar to HTTP, CoAP is based on the REST model. Clients access the resources made available by servers under URLs
using methods like GET, PUT, POST, and DELETE.
CoAP is designed to work on microcontrollers, which makes it perfect for the internet of things as it requires millions of
inexpensive nodes.
CoAP uses minimal resources, both on the device and on the network. Instead of a complex transport stack, it gets by
with UDP on IP.
CoAP is one of the most secure protocols as its default choice of DTLS parameters is equivalent to 3072-bit RSA keys.
SERVICE LAYER PROTOCOLS & SECURITY
DTLS
The DTLS (Datagram transport layer security) is an internet of things security protocol
designed to protect data communication between data-gram-based applications.
It is based on TLS (transport layer security) protocol and provides the same level of security.
SERVICE LAYER PROTOCOLS & SECURITY
DTLS
Features of DTLS
DTLS uses a retransmission timer to solve the issue of packet loss. If the timer terminates before the client
receives the confirmation message from the server, then the client retransmits the data.
The issue of reordering is solved by giving each message a specific sequence number. This helps in determining if
the next message received is in sequence or not.
If it is out of sequence, it is put in a queue and handled when the sequence number is reached.
DTLS is unreliable and does not guarantee the delivery of data, even for payload information.
SERVICE LAYER PROTOCOLS & SECURITY
6LoWPAN
6LoWPAN (IPv6 over Low Power Wireless Personal Area Networks) is a protocol for low-power networks like IoT systems and wireless sensor
networks.
Features of 6LoWPAN
6LoWPAN is used to carry data packets in the form of IPv6 over various networks.
Provides end-to-end IPv6 and hence provides direct connectivity to a wide variety of networks including direct connectivity to the Internet.
6LoWPAN is used for protecting the communications from the end-users to the sensor network.
SERVICE LAYER PROTOCOLS & SECURITY
ZigBee
ZigBee is believed to be a state-of-the-art protocol to provide security for internet of things devices
and applications.
It provides efficient machine-to-machine communication from 10–100 meters away in low-powered
embedded devices like radio systems.
It is a cost effective open-source wireless technology.
SERVICE LAYER PROTOCOLS & SECURITY
ZigBee
Features of IoT with ZigBee
ZigBee provides standardization at all layers, which enables compatibility between products from
different manufacturers.
Due to its mesh architecture, devices tend to connect with every device in the vicinity. This helps in
expanding the network and making it more flexible.
ZigBee uses “Green Power” that facilitates lower energy consumption and cost.
SERVICE LAYER PROTOCOLS & SECURITY
MAC 802.15.4
Medium access control (MAC) protocol is essential because it manages the coordination
among different IoT devices during data transmission.
However, several challenges need to be addressed at the MAC layer to provide high network
throughput, low energy consumption, and low latency.
SERVICE LAYER PROTOCOLS & SECURITY
RPL
RPL (Routing Protocol for Low-Power and Lossy Networks) is a routing protocol for wireless networks
with low power consumption and generally susceptible to packet loss.
RPL is a routing protocol that is based on the IPv6 lower power wireless personal area network, which
is connected to the IP network by the sink node.
Distance vector;
Source routing: allow the sender to specify the route;
SERVICE LAYER PROTOCOLS & SECURITY
RPL
SERVICE LAYER PROTOCOLS & SECURITY
APPLICATION LAYER
Definition
The application layer is the top-most layer in the OSI Model and is used for establishing
process-to-process communication and user services in a network.
It's the interface between user applications and the underlying network.
SERVICE LAYER PROTOCOLS & SECURITY
APPLICATION LAYER
Application layer protocols
1. Telnet - Telnet
2. FTP - File Transfer Protocol
3. TFTP - Trivial File Transfer Protocol
4. SMTP - Simple mail transfer protocol
5. SNMP - Simple network management protocol
6. DNS - Domain Name System
7. DHCP - Dynamic Host Configuration Protocol
SERVICE LAYER PROTOCOLS & SECURITY
APPLICATION LAYER
1. Telnet - Telnet
Telnet is an application protocol. It provides bidirectional interactive text orientated communication feature.
For text orientated communication telnet uses terminal connection.
2. FTP
FTP stands for File Transfer Protocol. It is a application layer protocol that is used for transforming a file from one
location to another, i.e. from one host to another host. It is a standard mechanism that is provided by TCP/IP.
SERVICE LAYER PROTOCOLS & SECURITY
APPLICATION LAYER
3. TFTP
TFTP stands for Trivial File Transfer Protocol is a application layer protocol, used for sending a file from
the server to the client. Trivial File Transfer Protocol uses the concept of UDP to share files between
server and client.
4. SMTP
SMTP stands for Simple mail transfer protocol is used to transfer the mails. It defines how both
commands and responses must be sent back and forth. It is used two times, between the sender and
the sender’s mail server and between the two mail servers.
SERVICE LAYER PROTOCOLS & SECURITY
APPLICATION LAYER
5. SNMP
SNMP stands for Simple network management protocol which is used to collect and organize the data
of managed devices on IP networks. It also modifies the information to change the behavior of the
devices.
6. DNS
DNS stands for Domain Name System is a decentralized naming system for the computers and other
devices on the internet to translate the domain name of the devices connected on the internet or any
other private network to the numerical IP addresses and vice versa.
SERVICE LAYER PROTOCOLS & SECURITY
APPLICATION LAYER
7. DHCP
DHCP stands for Dynamic Host Configuration Protocol. It is a network management protocol
present in the application layer. With its help, an Internet Protocol IP address can be assigned
to any device or node on a network dynamically so that they can communicate using this IP.
SERVICE LAYER PROTOCOLS & SECURITY
DESIGN SMART SYSTEM USING IOT COMPONENTS
1.Sensors and Devices
Devices and sensors are the “thing” part of IoT projects. These and other devices interact with
the physical environment.
It is not only important that they accurately read the phenomenon application needs, but
also, they have to be integrated with the overall system architecture too.
SERVICE LAYER PROTOCOLS & SECURITY
DESIGN SMART SYSTEM USING IOT COMPONENTS
1.Sensors and Devices
Device configuration is another important feature. Some devices provide configuration
programs while others require internal reprogramming to change their behaviour. Finally, you
must evaluate the power source the use (batteries, solar panels, AC, etc.) since it has a strong
impact in the system maintenance.
SERVICE LAYER PROTOCOLS & SECURITY
DESIGN SMART SYSTEM USING IOT COMPONENTS
2.Communications
Although the “i” in IoT stands for internet, you have different kinds of networks available for
communications among devices and with the platform.
Choosing the right networking technology depends on the characteristics and requirements of
the project. It is common to use more than one technology in an IoT project.
SERVICE LAYER PROTOCOLS & SECURITY
DESIGN SMART SYSTEM USING IOT COMPONENTS
3.Platform
The software platform of your IoT projects will be in charge of managing the devices
(onboarding process, monitoring, etc.) and receiving and processing the messages. It also
must provide APIs for reading the gathered data.
Platforms are usually deployed in the cloud, but you should check if they can be deployed on-
premises in case the project is big enough and investing in computing hardware is an option.
SERVICE LAYER PROTOCOLS & SECURITY
DESIGN SMART SYSTEM USING IOT COMPONENTS
4.Applications
All IoT projects are carried out for a purpose. Maybe the goal is receiving an alarm when a
laboratory room reaches a certain temperature or optimizing the water supply of a city.
In other cases, IoT projects are used for reducing the power consumption of a building or
predicting the maintenance of an industrial engine.
SERVICE LAYER PROTOCOLS & SECURITY
DESIGN SMART SYSTEM USING IOT COMPONENTS
4.Applications
All IoT projects are carried out for a purpose. Maybe the goal is receiving an alarm when a
laboratory room reaches a certain temperature or optimizing the water supply of a city.
In other cases, IoT projects are used for reducing the power consumption of a building or
predicting the maintenance of an industrial engine.

More Related Content

PPTX
Home automation based iot
PPTX
IoT Standards: The Next Generation
PDF
Introduction to IoT Architectures and Protocols
PDF
UNIT-5 IoT Reference Architecture.pdf
PPTX
Final year project presentation IOT Based home security system
PPTX
Home automation ppt
PDF
4th Year Project - Indoor Positioning System
PDF
Computer Network Notes (Handwritten) UNIT 2
Home automation based iot
IoT Standards: The Next Generation
Introduction to IoT Architectures and Protocols
UNIT-5 IoT Reference Architecture.pdf
Final year project presentation IOT Based home security system
Home automation ppt
4th Year Project - Indoor Positioning System
Computer Network Notes (Handwritten) UNIT 2

What's hot (20)

PPT
Sensor networks
PPTX
Application layer protocols
PPTX
4. Internet of Things - Reference Model and Architecture
PPTX
Iot architecture
PDF
Moving to Manufacture_Internet of Things (Part 02)
PDF
IoT Connectivity
PDF
Ch 6 IoT Processing Topologies and Types.pdf
PPTX
Internet of things (IoT)- Introduction, Utilities, Applications
PPTX
Raspberry Pi
PPT
THE INTERNET OF THINGS
PPTX
Gas and smoke detection system using arduino
PPTX
entities terminology
PPTX
Android Based Home Automation Control
PPTX
CLOUD COMPUTING UNIT - 3.pptx
PPTX
connecting smart object in IoT.pptx
PPTX
IoT based Flood detection system
PPTX
Overview of IoT (JNTUK - UNIT 1)
PPTX
Internet of things (IoT)
PPT
IoT with Arduino
PPSX
Smart Home Automation using Voice Assistant
Sensor networks
Application layer protocols
4. Internet of Things - Reference Model and Architecture
Iot architecture
Moving to Manufacture_Internet of Things (Part 02)
IoT Connectivity
Ch 6 IoT Processing Topologies and Types.pdf
Internet of things (IoT)- Introduction, Utilities, Applications
Raspberry Pi
THE INTERNET OF THINGS
Gas and smoke detection system using arduino
entities terminology
Android Based Home Automation Control
CLOUD COMPUTING UNIT - 3.pptx
connecting smart object in IoT.pptx
IoT based Flood detection system
Overview of IoT (JNTUK - UNIT 1)
Internet of things (IoT)
IoT with Arduino
Smart Home Automation using Voice Assistant
Ad

Similar to IoT.pptx (20)

PPTX
Modulmnbjkjnbnjnbnj,kkjebnmhnvfghjhgbcvxv
PDF
Internet of things chapter2.pdf
PDF
Iot architectures slides important.pdf
PPTX
ch2.pptx huuuuhy hhhh bjuuu huuujkjjjf hh
PPTX
ch2.pptxnnbhyyg uuggy jgugjb huuuhj hihij
PDF
Week 8 - Module 19 - PPT- Internet of Things for Libraries.pdf
PDF
Internet of Things (IoT) in smart city.pdf
PDF
Week 8 - Module 19 - PPT- Internet of Things for Libraries.pdf
PPTX
Unit - I Internet Of Things hokmjkkookkj
PPTX
Week 8 - Module 19 - PPT- Internet of Things for Libraries.pptx
PPTX
Week 8 - Module 19 - PPT- Internet of Things for Libraries.pptx
PDF
Iot 3 architectures architecture of iot.
PPTX
Internet of thing (IOT) AICT (Lec#10).pptx
PDF
IOT Material AY(24-25) Regulation R22 Syllabus
PPTX
A Methodology for Building the Internet of Things
PPTX
Module 1 Internet of Things (2).ppt.pdf on iot
PPTX
IOT TOTAL POWER POINT PRESENTATION UNITS
PPTX
IoT- Evolution of Internet of Things, Enabling. Technologies, M2M Communicati...
PDF
summaryg.pdffgdfgdfgfgfgfgfgffgfdfgfgffg
PDF
iot m1.pdf
Modulmnbjkjnbnjnbnj,kkjebnmhnvfghjhgbcvxv
Internet of things chapter2.pdf
Iot architectures slides important.pdf
ch2.pptx huuuuhy hhhh bjuuu huuujkjjjf hh
ch2.pptxnnbhyyg uuggy jgugjb huuuhj hihij
Week 8 - Module 19 - PPT- Internet of Things for Libraries.pdf
Internet of Things (IoT) in smart city.pdf
Week 8 - Module 19 - PPT- Internet of Things for Libraries.pdf
Unit - I Internet Of Things hokmjkkookkj
Week 8 - Module 19 - PPT- Internet of Things for Libraries.pptx
Week 8 - Module 19 - PPT- Internet of Things for Libraries.pptx
Iot 3 architectures architecture of iot.
Internet of thing (IOT) AICT (Lec#10).pptx
IOT Material AY(24-25) Regulation R22 Syllabus
A Methodology for Building the Internet of Things
Module 1 Internet of Things (2).ppt.pdf on iot
IOT TOTAL POWER POINT PRESENTATION UNITS
IoT- Evolution of Internet of Things, Enabling. Technologies, M2M Communicati...
summaryg.pdffgdfgdfgfgfgfgfgffgfdfgfgffg
iot m1.pdf
Ad

More from DrPrabakaranPerumal (11)

PPTX
AdvancedJava.pptx
PPTX
PPTX
EthicalHacking.pptx
PPTX
SoftwareEngineering.pptx
PPTX
SoftwareTesting.pptx
PPTX
Html-Prabakaran
PPTX
Programming in C
PPTX
Programming-in-C
PPTX
PPTX
OpeatingSystemPPT
PPTX
JavaAdvUnit-1.pptx
AdvancedJava.pptx
EthicalHacking.pptx
SoftwareEngineering.pptx
SoftwareTesting.pptx
Html-Prabakaran
Programming in C
Programming-in-C
OpeatingSystemPPT
JavaAdvUnit-1.pptx

Recently uploaded (20)

PPTX
2025 High Blood Pressure Guideline Slide Set.pptx
PPTX
CAPACITY BUILDING PROGRAMME IN ADOLESCENT EDUCATION
PDF
Everyday Spelling and Grammar by Kathi Wyldeck
PPTX
Climate Change and Its Global Impact.pptx
PDF
fundamentals-of-heat-and-mass-transfer-6th-edition_incropera.pdf
PDF
Hospital Case Study .architecture design
PDF
LIFE & LIVING TRILOGY- PART (1) WHO ARE WE.pdf
PDF
Compact First Student's Book Cambridge Official
PPT
REGULATION OF RESPIRATION lecture note 200L [Autosaved]-1-1.ppt
PDF
Disorder of Endocrine system (1).pdfyyhyyyy
PDF
faiz-khans about Radiotherapy Physics-02.pdf
PDF
Myanmar Dental Journal, The Journal of the Myanmar Dental Association (2015).pdf
PDF
LIFE & LIVING TRILOGY - PART - (2) THE PURPOSE OF LIFE.pdf
PPTX
ACFE CERTIFICATION TRAINING ON LAW.pptx
PDF
Controlled Drug Delivery System-NDDS UNIT-1 B.Pharm 7th sem
PDF
Lecture on Viruses: Structure, Classification, Replication, Effects on Cells,...
PDF
Literature_Review_methods_ BRACU_MKT426 course material
PDF
Civil Department's presentation Your score increases as you pick a category
PDF
1.Salivary gland disease.pdf 3.Bleeding and Clotting Disorders.pdf important
PDF
Journal of Dental Science - UDMY (2021).pdf
2025 High Blood Pressure Guideline Slide Set.pptx
CAPACITY BUILDING PROGRAMME IN ADOLESCENT EDUCATION
Everyday Spelling and Grammar by Kathi Wyldeck
Climate Change and Its Global Impact.pptx
fundamentals-of-heat-and-mass-transfer-6th-edition_incropera.pdf
Hospital Case Study .architecture design
LIFE & LIVING TRILOGY- PART (1) WHO ARE WE.pdf
Compact First Student's Book Cambridge Official
REGULATION OF RESPIRATION lecture note 200L [Autosaved]-1-1.ppt
Disorder of Endocrine system (1).pdfyyhyyyy
faiz-khans about Radiotherapy Physics-02.pdf
Myanmar Dental Journal, The Journal of the Myanmar Dental Association (2015).pdf
LIFE & LIVING TRILOGY - PART - (2) THE PURPOSE OF LIFE.pdf
ACFE CERTIFICATION TRAINING ON LAW.pptx
Controlled Drug Delivery System-NDDS UNIT-1 B.Pharm 7th sem
Lecture on Viruses: Structure, Classification, Replication, Effects on Cells,...
Literature_Review_methods_ BRACU_MKT426 course material
Civil Department's presentation Your score increases as you pick a category
1.Salivary gland disease.pdf 3.Bleeding and Clotting Disorders.pdf important
Journal of Dental Science - UDMY (2021).pdf

IoT.pptx

  • 1. FUNDAMENTAL of IoT Dr P PRABAKARAN Assistant Professor Department of Computer Applications School of Computing Sciences Vels Institute of Science Technology and Advanced Studies, Chennai
  • 2. ONLINE LEARNING FUNDAMENTAL of IoT Block -1 FUNDAMENTAL of IoT
  • 3. FUNDAMENTAL OF INTERNET of THINGS FUNDAMENTALS OF IoT The Internet of Things (IoT) refers to a system of interrelated, internet- connected objects that are able to collect and transfer data over a wireless network without human intervention.
  • 5. AN ARCHITECTURAL OVERVIEW Internet of Things (IoT) technology has a wide variety of applications and use of Internet of Things is growing so faster. The architecture of IoT depends upon its functionality and implementation in different sectors. Still, there is a basic process flow based on which IoT is built. Stage IoT architecture  Sensing Layer  Network Layer  Data processing Layer  Application Layer
  • 6. AN ARCHITECTURAL OVERVIEW Sensing Layer: Sensors, actuators, devices are present in this Sensing layer. These Sensors or Actuators accepts data, processes data and emits data over network. Network Layer Internet/Network gateways, Data Acquisition System (DAS) are present in this layer. DAS performs data aggregation and conversion function (Collecting data and aggregating data then converting analog data of sensors to digital data etc).
  • 7. AN ARCHITECTURAL OVERVIEW Data processing Layer This is processing unit of IoT ecosystem. Here data is analyzed and pre-processed before sending it to data center from where data is accessed by software applications. Application Layer This is last layer of 4 stages of IoT architecture. Data centers or cloud is management stage of data where data is managed and is used by end-user applications like agriculture, health care, aerospace, farming, defense, etc.
  • 8. MAIN DESIGN PRINCIPLES AND NEEDED CAPABILITIES
  • 9. MAIN DESIGN PRINCIPLES AND NEEDED CAPABILITIES Do Research On Your Target Audience IoT development is more about experiences and services than products. So, it all boils down to users and how they perceive and interact with devices either independently or collectively. Work On Delivering Contextual Experiences People only know that devices connected to the internet (and each other) constitute an IoT ecosystem.
  • 10. MAIN DESIGN PRINCIPLES AND NEEDED CAPABILITIES Focus On Creating Value The onset of any new concept, product or service fetches reactions from two types of people.  Those who can’t wait to get hands on with it  Those who are reluctant to use it. Leverage The Use Of Prototype One setback tech experts are still experiencing with IoT solutions is that an established IoT ecosystem is difficult to upgrade or modify.
  • 11. MAIN DESIGN PRINCIPLES AND NEEDED CAPABILITIES Prioritize Security First Digital systems come with their own set of concerns with respect to safety and security. Implement IoT design mechanisms that identify and eliminate concerns before they creep in. Effective Data Management IoT system is going to generate massive amounts of data every second or minute. Consider Human Connection IoT is a great concept to bring people together and talk about matters that deserve attention.
  • 12. IoT STANDARDS CONSIDERATIONS Important considerations for IoT solutions  IoT Security  IoT Analytics  IoT Device (Thing) Management  Low-Power, Short-Range IoT Networks  Low-Power, Wide-Area Networks  IoT Processors  IoT Operating Systems  Event Stream Processing  IoT Platforms  IoT Standards and Ecosystems
  • 13. IoT STANDARDS CONSIDERATIONS IoT Security IoT introduces a wide range of new security risks and challenges to the IoT devices themselves, their platforms and operating systems, their communications, and even the systems to which they're connected. IoT Analytics IoT business models will exploit the information collected by "things" in many ways.
  • 14. IoT STANDARDS CONSIDERATIONS IoT Device (Thing) Management Long-lived nontrivial "things" will require management and monitoring. This includes device monitoring, firmware and software updates, diagnostics, crash analysis and reporting, physical management, and security management. IoT also brings new problems of scale to the management task. Low-Power, Short-Range IoT Networks Selecting a wireless network for an IoT device involves balancing many conflicting requirements, such as range, battery life, bandwidth, density, endpoint cost and operational cost.
  • 15. IoT STANDARDS CONSIDERATIONS Low-Power, Wide-Area Networks Traditional cellular networks don't deliver a good combination of technical features and operational cost for those IoT applications that need wide-area coverage combined with relatively low bandwidth, good battery life, low hardware and operating cost, and high connection density. IoT Processors The processors and architectures used by IoT devices define many of their capabilities, such as whether they are capable of strong security and encryption, power consumption, whether they are sophisticated enough to support an operating system, updatable firmware, and embedded device management agents.
  • 16. IoT STANDARDS CONSIDERATIONS IoT Operating Systems Traditional operating systems (OSs) such as Windows and iOS were not designed for IoT applications. They consume too much power, need fast processors, and in some cases, lack features such as guaranteed real-time response. Event Stream Processing Some IoT applications will generate extremely high data rates that must be analyzed in real time.
  • 17. IoT STANDARDS CONSIDERATIONS IoT Platforms IoT provides three key platform components; (1) low-level device control and operations such as communications, device monitoring and management, security, and firmware updates (2) IoT data acquisition, transformation and management. IoT Standards and Ecosystems Although ecosystems and standards aren't precisely technologies, most eventually materialize as application programming interfaces (APIs).
  • 19. DEVICES AND GATEWAYS Gateway provides bridge between different communication technologies which means we can say that a Gateway acts as a medium to open up connection between cloud and controller (sensors / devices) in Internet of Things (IoT). It enables a connection between sensor network and Internet along with enabling IoT communication. As IoT devices work with low power consumption (Battery power) in other words they are energy constrained so if they will directly communicate to cloud/internet it won’t be effective in terms of power.
  • 20. DEVICES AND GATEWAYS Key functionalities of IoT Gateway :  Establishing communication bridge  Provides additional security.  Performs data aggregation.  Pre processing and filtering of data.  Provides local storage as a cache/ buffer.
  • 21. DEVICES AND GATEWAYS Working of IoT Gateway :  Receives data from sensor network.  Performs Pre processing, filtering and cleaning on unfiltered data.  Transports into standard protocols for communication.  Sends data to cloud.
  • 22. LOCAL AND WIDE AREA NETWORKING Local Area Network (LAN): LAN is a group of network devices which allow the communication between connected devices. Wide Area Network (WAN): WAN covers the large area than LAN as well as MAN such as: Country/Continent etc. WAN is expensive and should or might not be owned by one organization.
  • 23. LOCAL AND WIDE AREA NETWORKING
  • 24. BUSINESS PROCESSES IN IoT IoT uses are to automate process, gather valuable information, extend business functions, and trigger rules, source predictive analytics and big data, among other useful objectives. Implementing IoT business processes in your companies:  To define business process to improve and identify the problem you want to solve.  Use an end-to-end approach.  Get on board the right people  Be persistent but acknowledgeable to failure
  • 25. EVERYTHING AS A SERVICE (XAAS) Everything-as-a-Service is a term for services and applications that users can access on the Internet upon request. In everything as a Service various number of tools and technologies and services are provided to users as a service. With XaaS, business is simplified as they have to pay for what they need. This everything as a Service is also known as anything as a Service.
  • 26. EVERYTHING AS A SERVICE (XAAS) Examples of XaaS :  Software as a Service (SaaS)  Platform as a Service (PaaS)  Disaster Recovery as a Service (DRaaS)  Infrastructure as a service (IaaS)
  • 27. Online Learning FUNDAMENTAL OF INTERNET of THINGS Block – 2 REFERENCE ARCHITECTURE
  • 28. Fundamental of IoT REFERENCE ARCHITECTURE of IoT -STATE OF THE ART
  • 29. REFERENCE ARCHITECTURE of IoT -STATE OF THE ART
  • 30. REFERENCE ARCHITECTURE of IoT -STATE OF THE ART Security The IoT process has intent: to provide enhanced insights, operational efficiencies, new revenue streams and improved processes. So it’s important to be overly security-concerned when considering that it might also provide convenience in the development, build and install processes. People and Business Process One common cause of IoT ‘stumble’ is the way it is often started—from within one group. This is where business units struggle most with IoT, as it takes a much larger perspective to maximize the value to the entire business.
  • 31. REFERENCE ARCHITECTURE of IoT -STATE OF THE ART Data Abstraction Data Abstraction collects different data pieces and makes them available for analysis. These days every enterprise has some level of Business Intelligence (BI) skills, but it’s imperative to engage these resources in the early stages of your project discovery. Storage The Cloud is often assumed with IoT projects, but it should not be a given. There are situations where an IoT infrastructure needs to be placed on-premise.
  • 32. REFERENCE ARCHITECTURE of IoT -STATE OF THE ART Edge/Fog/Mist Edge - There are intelligent devices at multiple points within the network. These devices, known as the Edge. Devices that reside on the very edge of the network, pushing intelligence and processing power closer to the source and outside of the cloud and primary data repository. Fog - newer than the Edge and originally introduced by Cisco to increase scalability. As its name implies, it is closer to the ground, below the Cloud, outside the Edge. Fog nodes bring distributed compute to the local area network level, each node taking in data from sensors within a defined geographic area.
  • 33. REFERENCE ARCHITECTURE of IoT -STATE OF THE ART Mist: The Mist further extends the Edge and Fog models by pushing compute into the sensors and actuator units themselves. Network The primary job of any network is to transfer data, route data traffic and manage throughput. This has evolved to support different communications protocols. Sensors There’s virtually no end to the type of sensor that may be required for various projects, the choices are wide open. They’re as varied as the problems they help to solve. Most look like a postage stamp, a little widget.
  • 34. REFERENCE MODEL AND ARCHITECTURE
  • 35. REFERENCE MODEL AND ARCHITECTURE IoT domain model A domain model serves as a tool for human communication between people working in the domain in question and between people who work across different domains. Sensors: These are simple or complex Devices that typically involve a transducer that converts physical properties such as temperature into electrical signals.
  • 36. REFERENCE MODEL AND ARCHITECTURE Actuators: These are also simple or complex Devices that involve a transducer that converts electrical signals to a change in a physical property (e.g. turn on a switch or move a motor). These Devices also include potential communication capabilities, storage of intermediate commands, processing, and conversion of digital signals to analog electrical signals. Tags: Tags in general identify the Physical Entity that they are attached to. In reality, tags can be Devices or Physical Entities but not both, as the domain model shows.
  • 37. FUNCTIONAL VIEW OF IoT REFERENCE The IoT Functional Model aims at describing mainly the Functional Groups (FG) and their interaction with the ARM, while the Functional View of a Reference Architecture describes the functional components of an FG, interfaces, and interactions between the components.
  • 38. FUNCTIONAL VIEW OF IoT REFERENCE Device functional group The Device FG contains all the possible functionality hosted by the physical Devices that are used for increment the Physical Entities. This Device functionality includes sensing, actuation, processing, storage, and identification components, the sophistication of which depends on the Device capabilities. Communication functional group The Communication FG abstracts all the possible communication mechanisms used by the relevant Devices in an actual system in order to transfer information to the digital world components or other Devices.
  • 39. FUNCTIONAL VIEW OF IoT REFERENCE IoT Service functional group The IoT Service FG corresponds mainly to the Service class from the IoT Domain Model, and contains single IoT Services exposed by Resources hosted on Devices or in the Network. Virtual Entity functional group The Virtual Entity FG corresponds to the Virtual Entity class in the IoT Domain Model, and contains the necessary functionality to manage associations between Virtual Entities with themselves as well as associations between Virtual Entities and related IoT Services.
  • 40. FUNCTIONAL VIEW OF IoT REFERENCE IoT Service Organization functional group The purpose of the IoT Service Organisation FG is to host all functional components that support the composition and orchestration of IoT and Virtual Entity services. Moreover, this FG acts as a service hub between several other functional groups. IoT Process Management functional group The IoT Process Management FG is a collection of functionalities that allows smooth integration of IoT-related services (IoT Services, Virtual Entity Services, and Composed Services) with the Enterprise (Business) Processes.
  • 41. INFORMATION VIEW OF IoT REFERENCE Virtual Entity in the IoT Domain Model is the “Thing” in the Internet of Things, the IoT information model captures the details of a Virtual Entity- centric model. Similar to the IoT Domain Model, the IoT Information Model is presented using Unified Modelling Language (UML) diagrams.
  • 42. INFORMATION VIEW OF IoT REFERENCE
  • 43. DEPLOYMENT AND OPERATIONAL VIEW Addresses how an IoT system can be realized by selecting the proper technologies, devices, resources, and services, as well as guidelines for architects/developers through the different decisions to be made.
  • 44. REAL-WORLD DESIGN CONSTRAINTS- INTRODUCTION The Internet of Things has been facing many areas like Information Technology, Healthcare, Data Analytics and Agriculture. The main focus is on protecting privacy as it is the primary reason for other challenges including government participation. Scalability: Billions of internet-enabled devices get connected in a huge network, large volumes of data are needed to be processed. The system that stores, analyses the data from these IoT devices needs to be scalable.
  • 45. REAL-WORLD DESIGN CONSTRAINTS- INTRODUCTION Interoperability: Technological standards in most areas are still fragmented. These technologies need to be converged. Which would help us in establishing a common framework and the standard for the IoT devices. Security and Personal Privacy: There has been no research in security vulnerabilities and its improvements. It should ensure Confidentiality, Integrity and Availability of personal data of patient.
  • 46. TECHNICAL DESIGN CONSTRAINTS Technical requirements – coverage, energy efficiency, data rate, other features relevant to specific applications (mobility, positioning, latency, density); Lack of encryption Although encryption is a great way to prevent hackers from accessing data, it is also one of the leading IoT security challenges. These drives like the storage and processing capabilities that would be found on a traditional computer.
  • 47. TECHNICAL DESIGN CONSTRAINTS Insufficient testing and updating With the increase in the number of IoT(internet of things) devices, IoT manufacturers are more eager to produce and deliver their device as fast as they can without giving security too much of although. IoT Malware and ransomware Increases with increase in devices. Ransomware uses encryption to effectively lock out users from various devices and platforms and still use a user’s valuable data and info.
  • 48. TECHNICAL DESIGN CONSTRAINTS HARDWARE IS POPULAR AGAIN IoT Hardware includes a wide range of devices such as devices for routing, bridges, sensors etc. These IoT devices manage key tasks and functions such as system activation, security, action specifications, communication, and detection of support-specific goals and actions. BLE and Wireless Sensors Bluetooth Low Energy (BLE) is a wireless data transfer technology. BLE is aimed at novel applications in the healthcare, fitness, security, and home entertainment industries.
  • 49. DATA REPRESENTATION AND VISUALIZATION Data Visualization is referred as the process of representing information or data into a visual context that provides useful insights from the data. It is a way to display the vast amount of data in a meaningful way that clearly presents trends and patterns from the raw data collected.
  • 50. DATA REPRESENTATION AND VISUALIZATION Role of data visualization in IOT Internet of Things (IOT) and data are interlinked together as IOT is all about collecting data and making sense of it. One of the challenges for IoT industry is data analysis and interpretation. The data collected is impractical if we cannot extract useful information from it and analyse and translate that information to identify hidden trends, outliers, and patterns in data and make data-driven decisions.
  • 51. INTERACTION AND REMOTE CONTROL There are many possible interactions between devices and users in the world of the Internet of Things. 1. Machine-human interaction, where we use an IoT device to log data on a server, which is then used to display a graph that can be understood and used by the final user. 2. human-machine interaction, where the user is triggering a command to a remote device, for example, to activate a lamp remotely. 3. machine-to-machine interaction, where two or more devices are directly talking to each other, without the intervention of any human.
  • 52. INTERACTION AND REMOTE CONTROL Remote Monitoring of IoT Devices creates remote monitoring for IoT device data transmission or data validity. Remote Monitoring of IoT Devices ingests real-time device data from IoT devices to assess the state of each IoT device and send you notifications if there are data transmission issues or out of range data. Remote Monitoring of IoT Devices also provides a framework for collecting diagnostic information for deriving outcome-oriented insights about the health of your assets.
  • 53. INTERACTION AND REMOTE CONTROL Remote Monitoring of IoT Devices creates remote monitoring for IoT device data transmission or data validity. Remote Monitoring of IoT Devices ingests real-time device data from IoT devices to assess the state of each IoT device and send you notifications if there are data transmission issues or out of range data. Remote Monitoring of IoT Devices also provides a framework for collecting diagnostic information for deriving outcome-oriented insights about the health of your assets.
  • 54. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer Physical Layer Physical medium can be copper wire, fiber optic cable, twisted pair or even wireless channel. Functions of PHY layer: 1. It converts MAC layer format suitable to be transported over the medium. 2. It adds forward error correction functionality to enable error correction at the receiver. MAC Layer MAC is the short form of Medium Access Control Layer. It interfaces PHY layer and Upper layers.
  • 55. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer Functions of MAC layer It incorporates MAC header at the start of upper layer IP packet and CRC (Cyclic Redundancy check) at the end of IP packet. Incorporates ARQ (Automatic repeat request) functionality as a means for requesting retransmission in case of errors.
  • 56. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer 3GPP The 3rd Generation Partnership Project (3GPP) is a collaborative project between a groups of telecommunications associations with the initial goal of developing globally applicable specifications for third-generation (3G) mobile systems. 3GPP standards are designed for mobile systems based on evolved GSM core networks. Technical Specification Groups in 3GPP Radio Access Networks (RAN), Services & Systems Aspects (SA), Core Network & Terminals (CT)
  • 57. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer MTC The MTC (Machine Type Communications or Machine to Machine Communication) system is one of the most promising technologies to provide IoT (Internet of Things) applications. MTC describes data communication between two entities without the involvement of a human. MTC has great potential in a wide range of applications and services. The potential applications are widespread across different industries, including healthcare, logistics, manufacturing, process automation, energy, and utilities.
  • 58. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer IEEE 802.11 IEEE (Institute of Electrical and Electronics Engineers) 802.11 refers to the set of standards that define communication for wireless LANs (wireless local area networks, or WLANs). IEEE Standard for Information Technology--Telecommunications and Information Exchange between Systems - Local and Metropolitan Area Networks--Specific Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. The IEEE developed an international standard for WLANs. The 802.11 standard focuses on the bottom two layers of the OSI model, the physical layer (PHY) and data link layer (DLL).
  • 59. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer IEEE 802.11 Architecture Two network architectures are defined in the IEEE 802.11 standard Infrastructure network - An infrastructure network is the network architecture for providing communication between wireless clients and wired network resources. Point-to-point (ad-hoc) network - An ad-hoc network is the architecture that is used to support mutual communication between wireless clients.
  • 60. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer IEEE 802.11 Architecture
  • 61. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer IEEE 802.15 IEEE 802.15.4 is a low-cost, low-data-rate wireless access technology for devices that are operated or work on batteries. This describes how low-rate wireless personal area networks (LR-WPANs) function. Properties of IEEE 802.15  Standardization and alliances  Physical Layer  MAC layer  Topology  Security  Competitive Technologies
  • 62. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer Advantages of IEEE 802.15.4 :  cheap cost  long battery life,  Quick installation  simple  extensible protocol stack
  • 63. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS WIRELESS HART Wireless HART is the latest release of Highway Addressable Remote Transducer (HART) Protocol. WirelessHART is a Wireless Mesh Network Communications Protocol designed to meet the needs for process automation applications. HART encompasses the most number of field devices incorporated in any field network.
  • 64. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS WIRELESS HART HART Physical Layer Derived from IEEE 802.15.4 protocol. It operates only in the 2.4 GHz ISM band. Employs and exploits 15 channels of the band to increase reliability. HART Application Layer Handles communication between gateways and devices via a series of command and response messages. Responsible for extracting commands from a message, executing it and generating responses. This layer is seamless and does not differentiate between wireless and wired versions of HART.
  • 65. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS WIRELESS HART
  • 66. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS WIRELESS HART-ZWAVE Z-wave is one of the Personal Area Network(PAN) technology used. Z-wave proprietary wireless communication protocol is designed for home automation similar to zigbee. It uses low power wireless communication technology, designed to control home based electronic products using remote control and smoke alarm.
  • 67. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS WIRELESS HART-ZWAVE
  • 68. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS WIRELESS HART-ZWAVE System Specifications Works at 868.42 MHz (in Europe) and 908.42 MHz MHz (in US) frequency range Data rate(bandwidth) is about 9.6, 40, 200 kbps Modulation is GFSK in the 900MHz ISM band Range is about 30 meter(indoors) and 100 meters(outdoors) Home automation and security
  • 69. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS WIRELESS HART -BLUETOOTH LOW ENERGY Bluetooth there are different versions based on data rate and distance coverage requirements such as version 1.2, 2.0, 2.1, 3.0, 4.0 and 4.1. Bluetooth version 4.0 is known as Bluetooth Low Energy (BLE). Once the devices are connected with bluetooth link the connection is maintained even if there is no data to be transferred.
  • 70. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS WIRELESS HART -BLUETOOTH LOW ENERGY
  • 71. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS BLE Message Exchange
  • 72. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS ZIGBEE SMART ENERGY Zigbee devices are used everywhere including smart energy, medical and in home automation. It has two bands of operation 868/915MHz and 2450MHz. 868/915 band provides about 20-40Kb/s and 2450MHz band provides about 250 kb/s data rates. Joining the Zigbee Network There are two ways to join a zigbee network viz. MAC association and network re-join.
  • 73. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS ZIGBEE SMART ENERGY
  • 74. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS DASH7 The Dash7 technology is promoted by DASH7 Alliance. This technology provides long battery life and coverage of about 2Km in indoor places. Following are the features of Dash7 wireless technology. Dash7 protocol and home automation basics in IoT,M2M The RFID technologies such as NFC and Dash7 is widely used in WSN(wireless sensor networking). Most of the smartphones will have these technologies integrated to provide many facilities to the users.
  • 75. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS DASH7
  • 76. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS DASH 7 Different gateways in DASH 7 Blinker: It only transmits and does not use a receiver. EndPoint: It can transmit and receive the data. It also supports wake-up events. Subcontroller: It is full featured device. It is not always active. It uses wake on scan cycles similar to end points. Gateway: It connects D7A network with the other network.It will always be online. It always listens unless it is transmitting. DASH7 defines two types of frames viz. a foreground frame and a background frame.
  • 77. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS NETWORK LAYER A network is a group of two or more connected computing devices. Usually all devices in the network are connected to a central hub. Network-to-network connections are what make the Internet possible. The "network layer" is the part of the Internet communications process where these connections occur, by sending packets of data back and forth between different networks.
  • 78. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS NETWORK LAYER
  • 79. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS NETWORK LAYER The main functions performed by the network layer are  Routing - When a packet reaches the router's input link, the router will move the packets to the router's output link  Logical Addressing - Logical addressing is also used to distinguish between source and destination system.  Internetworking - logical connection between different types of networks.  Fragmentation - The fragmentation is a process of breaking the packets into the smallest
  • 80. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS PHY/MAC Layer NETWORK LAYER The main functions performed by the network layer are  Routing - When a packet reaches the router's input link, the router will move the packets to the router's output link  Logical Addressing - Logical addressing is also used to distinguish between source and destination system.  Internetworking - logical connection between different types of networks.  Fragmentation - The fragmentation is a process of breaking the packets into the smallest
  • 81. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS IPv4 IP stands for Internet Protocol and v4 stands for Version Four (IPv4). IPv4 was the primary version brought into action for production within the ARPANET in 1983. IP version four addresses are 32-bit integers which will be expressed in decimal notation. IPv4 supports three different types of addressing modes  Unicast Addressing Mode  Broadcast Addressing Mode  Multicast Addressing Mode
  • 82. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS IPv4 Unicast Addressing Mode Data is sent only to one destined host. The Destination Address field contains 32- bit IP address of the destination host. Here the client sends data to the targeted server. Broadcast Addressing Mode The packet is addressed to all the hosts in a network segment. The Destination Address field contains a special broadcast address, i.e. 255.255.255.255. Multicast Addressing Mode This mode is a mix of the previous two modes, i.e. the packet sent is neither destined to a single host nor all the hosts on the segment.
  • 83. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS IPv4 Parts of IPv4 Network part The network part indicates the distinctive variety that’s appointed to the network. The network part conjointly identifies the category of the network that’s assigned. Host Part: The host part uniquely identifies the machine on your network. This part of the IPv4 address is assigned to every host. Subnet number: This is the nonobligatory part of IPv4. Local networks that have massive numbers of hosts are divided into subnets and subnet numbers are appointed to that.
  • 84. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS IPv4 Advantages of IPv4  IPv4 security permits encryption to keep up privacy and security.  IPV4 network allocation is significant and presently has quite 85000 practical routers.  It becomes easy to attach multiple devices across an outsized network while not NAT.  This is a model of communication so provides quality service also as economical knowledge transfer.  IPV4 addresses are redefined and permit flawless encoding.  Routing is a lot of scalable and economical as a result of addressing is collective more effectively.
  • 85. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS IPv6  Internet Protocol Version 6 (IPv6) is a network layer protocol that enables data communications over a packet switched network.  Packet switching involves the sending and receiving of data in packets between two nodes in a network.  The working standard for the IPv6 protocol was published by the Internet Engineering Task Force (IETF) in 1998.  IPv6 was intended to replace the widely used Internet Protocol Version 4 (IPv4) that is considered the backbone of the modern Internet.
  • 86. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS IPv6 Type of IPv6 addressing methods :  Unicast - Unicast Address identifies a single network interface. A packet sent to a unicast address is delivered to the interface identified by that address.  Multicast - Multicast Address is used by multiple hosts, called as Group, acquires a multicast destination address. These hosts need not be geographically together  Anycast - Anycast Address is assigned to a group of interfaces. Any packet sent to an anycast address will be delivered to only one member interface
  • 87. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS 6LoWPAN The term "6LoWPAN" stands for IPv6 over Low Power Wireless Personal Area Networks. This is open standard defined in RFC6282 by IETF. It allows IPv6 packets to be passed to/from 6LoWPAN network. 6LoWPAN provides a means of carrying packet data in the form of IPv6 over IEEE 802.15.4 and other networks.
  • 88. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS 6LoWPAN
  • 89. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS 6LoWPAN Benefits or advantages of 6LoWPAN 6LoWPAN is a mesh network which is robust, scalable and self healing. It offers long range of communication which detects signals below noise level. It consumes less power as it uses reduced transmission time (using short time pulses). Hence this saves energy and consecutively battery can be used for very long duration. It offers large network which can be used by millions of devices.
  • 90. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS 6TiSCH 6TiSCH is a working group at the IETF, which is standardizing how to combine IEEE802.15.4 time-slotted channel hopping (TSCH) with IPv6. The 6TiSCH protocol stack combines the ease of use of IPv6 with the industrial performance of TSCH. 6TiSCH uses IEEE802.15.4 O-QPSK 2.4 GHz as its PHY and IEEE802.15.4e at the Medium Access Control (MAC) layer. 6TiSCH defines an operational sub-layer (6top) which coordinates a mote’s negotiations with its neighbors to allocate cells.
  • 91. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS DHCP Dynamic Host Configuration Protocol(DHCP) is an application layer protocol which is used to provide: Subnet Mask (Option 1 – e.g., 255.255.255.0) Router Address (Option 3 – e.g., 192.168.1.1) DNS Address (Option 6 – e.g., 8.8.8.8) Vendor Class Identifier (Option 43 – e.g., ‘unifi’ = 192.168.1.9 ##where unifi = controller)
  • 92. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS DHCP
  • 93. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS DHCP Advantages  Centralized management of IP addresses.  Ease of adding new clients to a network.  Reuse of IP addresses reducing the total number of IP addresses that are required.  Simple reconfiguration of the IP address space on the DHCP server without needing to reconfigure each client.
  • 94. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS ICMP The Internet Control Message Protocol (ICMP) is a network layer protocol used by network devices to diagnose network communication issues. ICMP is mainly used to determine whether or not data is reaching its intended destination in a timely manner. Commonly, the ICMP protocol is used on network devices, such as routers.
  • 95. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS RPL RPL (Routing Protocol for Low-Power and Lossy Networks) is a routing protocol for wireless networks with low power consumption and generally susceptible to packet loss. RPL is a routing protocol that is based on the IPv6 lower power wireless personal area network, which is connected to the IP network by the sink node.  Distance vector;  Source routing: allow the sender to specify the route;
  • 96. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS CORPL (cognitive RPL) CORPL protocol is the extension of the RPL protocol, which is termed as cognitive RPL. This network protocol is designed for cognitive networks and uses DODAG topology. CORPL protocol makes two new modifications in the RPL protocol. It uses opportunistic forwarding to forward a packet between the nodes. Each node of CORPL protocol keeps the information of forwarding set rather than parents only maintaining it.
  • 97. IOT DATA LINK LAYER & NETWORK LAYER PROTOCOLS CARP CARP (Channel-Aware Routing Protocol) is a distributed routing protocol. It is designed for underwater communication. It has lightweight packets so that it can be used for Internet of Things (IoT). It performs two different functionalities: Network initialization and data forwarding. CARP protocol does not support previously collected data.
  • 98. TRANSPORT & SESSION LAYER PROTOCOLS TRANSPORT LAYER TCP stands for Transmission Control Protocol a communications standard that enables application programs and computing devices to exchange messages over a network. It is designed to send packets across the internet and ensure the successful delivery of data and messages over networks. TCP is one of the basic standards that define the rules of the internet and is included within the standards defined by the Internet Engineering Task Force (IETF).
  • 99. TRANSPORT & SESSION LAYER PROTOCOLS MPTCP (Multipath TCP) The Multipath TCP (MPTCP) project looks to change that view of networking by adding support for multiple transport paths to the endpoints; it offers a lot of benefits, but designing a deployable protocol for today's Internet is surprisingly hard. MPTCP represents the most recent efforts that the Internet Engineering Task Force (IETF) is promoting to enhance the TCP capabilities to handle multiple addresses. Multipath TCP is particularly useful in multipath data centre and mobile phone environments. All mobiles allow you to connect via WiFi and 3G network.
  • 100. TRANSPORT & SESSION LAYER PROTOCOLS MPTCP (Multipath TCP)
  • 101. TRANSPORT & SESSION LAYER PROTOCOLS UDP User Datagram Protocol (UDP) is a Transport Layer protocol. UDP is a part of the Internet Protocol suite, referred to as UDP/IP suite. Unlike TCP, it is an unreliable and connectionless protocol. So, there is no need to establish a connection prior to data transfer. UDP Header UDP header is an 8-bytes fixed and simple header, while for TCP it may vary from 20 bytes to 60 bytes.
  • 102. TRANSPORT & SESSION LAYER PROTOCOLS UDP
  • 103. TRANSPORT & SESSION LAYER PROTOCOLS UDP UPD features  UDP is used when acknowledgement of data does not hold any significance.  UDP is good protocol for data flowing in one direction.  UDP is simple and suitable for query based communications.  UDP is not connection oriented.
  • 104. TRANSPORT & SESSION LAYER PROTOCOLS DCCP (Datagram Congestion Control Protocol) DCCP is acronym of Datagram Congestion Control Protocol. The DCCP Datagram Congestion Control Protocol is a transport layer protocol in TCP/IP model. Millions person uses internet at a time because of this a lot of data flow every time on internet network. The data flow generates congestion in the network. Congestion cause the internet speed slow and poor performance occurs. To overcome this problem DCCP Datagram Congestion Control Protocol invented by IETF (Internet Engineering Task Force).
  • 105. TRANSPORT & SESSION LAYER PROTOCOLS DCCP (Datagram Congestion Control Protocol)
  • 106. TRANSPORT & SESSION LAYER PROTOCOLS DCCP (Datagram Congestion Control Protocol) Function of DCCP Datagram Congestion Control Protocol DCCP protocol provides a reliable data delivery from one device to another device. There is no any other control system available on internet network.
  • 107. TRANSPORT & SESSION LAYER PROTOCOLS SCTP (Stream Control Transmission Protocol) Stream Control Transmission Protocol (SCTP) is a transport-layer protocol that ensures reliable, in-sequence transport of data. SCTP provides multihoming support where one or both endpoints of a connection can consist of more than one IP address. Stream Control Transmission Protocol (SCTP) is an IP Transport Layer protocol. SCTP exists at an equivalent level with User Datagram Protocol (UDP) and Transmission Control Protocol (TCP), which provides transport layer functions to many Internet applications.
  • 108. TRANSPORT & SESSION LAYER PROTOCOLS SCTP (Stream Control Transmission Protocol) SCTP Services  Aggregate Server Access Protocol (ASAP)  Bearer-independent Call Control (BICC)  Direct Data Placement Segment chunk (DDP-segment)  Direct Data Placement Stream session control (DDP-stream)  Diameter in a DTLS/SCTP DATA chunk (Diameter-DTLS)
  • 109. TRANSPORT & SESSION LAYER PROTOCOLS SCTP (Stream Control Transmission Protocol) SCTP Features Delivery of data in chunks within an independent stream eliminates unnecessary head-of- line blocking. Path selection and monitoring functionality to select a primary data transmission path and test the connectivity of the transmission path. Validation and acknowledgment mechanisms protect against flooding attacks and provide notification of duplicated or missing data chunks.
  • 110. TRANSPORT & SESSION LAYER PROTOCOLS TLS (Transport Layer Security) Transport Layer Security (TLS) is the most widely used protocol for implementing cryptography on the web. TLS uses a combination of cryptographic processes to provide secure communication over a network. TLS provides a secure enhancement to the standard TCP/IP sockets protocol used for Internet communications. The secure sockets layer is added between the transport layer and the application layer in the standard TCP/IP protocol stack.
  • 111. TRANSPORT & SESSION LAYER PROTOCOLS DTLS (Datagram Transport Layer Security) DTLS is a protocol based on TLS that is capable of securing the datagram transport. DTLS is well-suited for securing applications and services that are delay-sensitive (and hence use datagram transport), tunneling applications such as VPNs, and applications that tend to run out of file descriptors or socket buffers.
  • 112. TRANSPORT & SESSION LAYER PROTOCOLS SESSION LAYERHTTP Functions of Session Layer Session Layer works as a dialog controller through which it allows systems to communicate in either half-duplex mode or full duplex mode of communication. This layer is also responsible for token management, through which it prevents two users to simultaneously access or attempting the same critical operation. This layer allows synchronization by allowing the process of adding checkpoints, which are considered as synchronization points to the streams of data. This layer is also responsible for session checkpointing and recovery.
  • 113. TRANSPORT & SESSION LAYER PROTOCOLS CoAP Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained networks in the Internet of Things. CoAP is designed to enable simple, constrained devices to join the IoT even through constrained networks with low bandwidth and low availability. It is generally used for machine-to-machine (M2M) applications such as smart energy and building automation.
  • 114. TRANSPORT & SESSION LAYER PROTOCOLS CoAP
  • 115. TRANSPORT & SESSION LAYER PROTOCOLS XMPP XMPP is the Extensible Messaging and Presence Protocol, a set of open technologies for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data. Architecture of the XMPP Protocol XMPP technologies use a decentralized client-server architecture related to the architecture used for the World Wide Web and the email network. In decentralized client- server architecture, client developers can focus on user experience, and server developers can focus on reliability and scalability.
  • 116. TRANSPORT & SESSION LAYER PROTOCOLS XMPP
  • 117. TRANSPORT & SESSION LAYER PROTOCOLS AMQP Advanced Message Queuing Protocol (AMQP) is created as an open standard protocol that allows messaging interoperability between systems, regardless of message broker vendor or platform used; With AMQP, you can use whatever AMQP-compliant client library you want, and any AMQP-compliant broker you want. Message clients using AMQP are completely agnostic. It defines a set of messages capabilities which must be made available by an AMQP compliant server implementation (like RabbitMQ). Including rules of how messages must be routed and stored within the broker to follow the AMQ Model.
  • 118. TRANSPORT & SESSION LAYER PROTOCOLS AMQP
  • 119. TRANSPORT & SESSION LAYER PROTOCOLS MQTT MQTT stands for Message Queuing Telemetry Transport. MQTT is a machine to machine internet of things connectivity protocol. It is an extremely lightweight and publish-subscribe messaging transport protocol. This protocol is useful for the connection with the remote location where the bandwidth is a premium. It makes it easy for communication between multiple devices.
  • 120. TRANSPORT & SESSION LAYER PROTOCOLS MQTT Architecture of MQTT Message Client Server or Broker TOPIC
  • 121. TRANSPORT & SESSION LAYER PROTOCOLS MQTT Architecture of MQTT
  • 122. SERVICE LAYER PROTOCOLS & SECURITY Service Layer Service Layer is an abstraction over domain logic. It defines application's boundary with a layer of services that establishes a set of available operations and coordinates the application's response in each operation. Features of Service Layer Design Faster and easy Integration with multiple applications Light weight design to provide scalability Self discoverable
  • 123. SERVICE LAYER PROTOCOLS & SECURITY Service Layer Service Layer design has 3 discrete sections with a 3-Tier application: Domain/functional Model Series of REST Endpoints A means for storing domain objects, or a persistence layer
  • 124. SERVICE LAYER PROTOCOLS & SECURITY Service Layer
  • 125. SERVICE LAYER PROTOCOLS & SECURITY Service Layer oneM2M oneM2M is the global standards initiative that covers requirements, architecture, API specifications, security solutions and interoperability for Machine-to-Machine and IoT technologies.
  • 126. SERVICE LAYER PROTOCOLS & SECURITY Service Layer ETSI M2M Existing M2M solutions are highly fragmented and typically dedicated to a single application. (Eg. Fleet management, meter reading, vending machines) Multitude of technical solutions and dispersed standardization activities result in the slow development of the global M2M market. Standardization is a key enabler to remove the technical barriers and ensure interoperable M2M services and networks.
  • 127. SERVICE LAYER PROTOCOLS & SECURITY Service Layer Features of ETSI M2M Identification of the M2M application and the M2M devices Asynchronous and synchronous communication. Store and forward mechanism based on policies for optimizing the communication Location information Device management based both on OMA DM (wireless) and BBF TR-69 (wireline).
  • 128. SERVICE LAYER PROTOCOLS & SECURITY OMA (OPEN MOBILE ALLIANCE) The OMA-DM protocol is Client-initiated remote HTTPS DM session. OMA Device Management is a device management protocol specified by the Open Mobile Alliance (OMA) Device Management (DM) Working Group and the Data Synchronization (DS) Working Group.
  • 129. SERVICE LAYER PROTOCOLS & SECURITY OMA (OPEN MOBILE ALLIANCE) OMA Device management is intended to support the following uses: Provisioning – Configuration of the device (including first time use), enabling and disabling features Device Configuration – Allow changes to settings and parameters of the device Software Upgrades – Provide for new software and/or bug fixes to be loaded on the device, including applications and system software Fault Management – Report errors from the device, query about status of device
  • 130. SERVICE LAYER PROTOCOLS & SECURITY OMA Features:  Full support of the OMA-DM and OMA-CP protocol  Extensive SDK with implementation samples  Support of OMA-DM data model  Support for Linux and non-Linux OS  Provisioning  Bootstrap
  • 131. SERVICE LAYER PROTOCOLS & SECURITY SECURITY IN IoT PROTOCOLS IoT security refers to the methods of protection used to secure internet-connected or network-based devices. The term IoT is incredibly broad, and with the technology continuing to evolve, the term has only become broader. From watches to thermostats to video game consoles, nearly every technological device has the ability to interact with the internet, or other devices, in some capacity.
  • 132. SERVICE LAYER PROTOCOLS & SECURITY MQTT MQTT is one of the most common security protocols used in internet of things security. It was invented by Dr Andy Stanford-Clark and Arlen Nipper in 1999. MQTT stands for Message Queuing Telemetry Transport and is a client-server communicating messaging transport protocol. The MQTT runs over TCP/IP or over other conventions that provide requested, lossless, two- way associations.
  • 133. SERVICE LAYER PROTOCOLS & SECURITY MQTT Features of MQTT  Its a simple and extremely lightweight protocol with easy and fast data transmission.  MQTT is designed for constrained devices as well as low-bandwidth, unreliable or high-latency networks.  Minimum use of data packets ensures less network usage.  It’s based on the messaging technique and so, is extremely fast and reliable.  It’s ideal for IoT applications.
  • 134. SERVICE LAYER PROTOCOLS & SECURITY CoAP (Constraint Application Protocol) CoAP (Constraint Application Protocol) is a web transfer protocol designed for constrained devices (like microcontrollers) and the constrained network called low power or lossy networks. It is also one of the most popular protocols to secure internet of things applications.
  • 135. SERVICE LAYER PROTOCOLS & SECURITY CoAP (Constraint Application Protocol) Features of CoAP Similar to HTTP, CoAP is based on the REST model. Clients access the resources made available by servers under URLs using methods like GET, PUT, POST, and DELETE. CoAP is designed to work on microcontrollers, which makes it perfect for the internet of things as it requires millions of inexpensive nodes. CoAP uses minimal resources, both on the device and on the network. Instead of a complex transport stack, it gets by with UDP on IP. CoAP is one of the most secure protocols as its default choice of DTLS parameters is equivalent to 3072-bit RSA keys.
  • 136. SERVICE LAYER PROTOCOLS & SECURITY DTLS The DTLS (Datagram transport layer security) is an internet of things security protocol designed to protect data communication between data-gram-based applications. It is based on TLS (transport layer security) protocol and provides the same level of security.
  • 137. SERVICE LAYER PROTOCOLS & SECURITY DTLS Features of DTLS DTLS uses a retransmission timer to solve the issue of packet loss. If the timer terminates before the client receives the confirmation message from the server, then the client retransmits the data. The issue of reordering is solved by giving each message a specific sequence number. This helps in determining if the next message received is in sequence or not. If it is out of sequence, it is put in a queue and handled when the sequence number is reached. DTLS is unreliable and does not guarantee the delivery of data, even for payload information.
  • 138. SERVICE LAYER PROTOCOLS & SECURITY 6LoWPAN 6LoWPAN (IPv6 over Low Power Wireless Personal Area Networks) is a protocol for low-power networks like IoT systems and wireless sensor networks. Features of 6LoWPAN 6LoWPAN is used to carry data packets in the form of IPv6 over various networks. Provides end-to-end IPv6 and hence provides direct connectivity to a wide variety of networks including direct connectivity to the Internet. 6LoWPAN is used for protecting the communications from the end-users to the sensor network.
  • 139. SERVICE LAYER PROTOCOLS & SECURITY ZigBee ZigBee is believed to be a state-of-the-art protocol to provide security for internet of things devices and applications. It provides efficient machine-to-machine communication from 10–100 meters away in low-powered embedded devices like radio systems. It is a cost effective open-source wireless technology.
  • 140. SERVICE LAYER PROTOCOLS & SECURITY ZigBee Features of IoT with ZigBee ZigBee provides standardization at all layers, which enables compatibility between products from different manufacturers. Due to its mesh architecture, devices tend to connect with every device in the vicinity. This helps in expanding the network and making it more flexible. ZigBee uses “Green Power” that facilitates lower energy consumption and cost.
  • 141. SERVICE LAYER PROTOCOLS & SECURITY MAC 802.15.4 Medium access control (MAC) protocol is essential because it manages the coordination among different IoT devices during data transmission. However, several challenges need to be addressed at the MAC layer to provide high network throughput, low energy consumption, and low latency.
  • 142. SERVICE LAYER PROTOCOLS & SECURITY RPL RPL (Routing Protocol for Low-Power and Lossy Networks) is a routing protocol for wireless networks with low power consumption and generally susceptible to packet loss. RPL is a routing protocol that is based on the IPv6 lower power wireless personal area network, which is connected to the IP network by the sink node. Distance vector; Source routing: allow the sender to specify the route;
  • 143. SERVICE LAYER PROTOCOLS & SECURITY RPL
  • 144. SERVICE LAYER PROTOCOLS & SECURITY APPLICATION LAYER Definition The application layer is the top-most layer in the OSI Model and is used for establishing process-to-process communication and user services in a network. It's the interface between user applications and the underlying network.
  • 145. SERVICE LAYER PROTOCOLS & SECURITY APPLICATION LAYER Application layer protocols 1. Telnet - Telnet 2. FTP - File Transfer Protocol 3. TFTP - Trivial File Transfer Protocol 4. SMTP - Simple mail transfer protocol 5. SNMP - Simple network management protocol 6. DNS - Domain Name System 7. DHCP - Dynamic Host Configuration Protocol
  • 146. SERVICE LAYER PROTOCOLS & SECURITY APPLICATION LAYER 1. Telnet - Telnet Telnet is an application protocol. It provides bidirectional interactive text orientated communication feature. For text orientated communication telnet uses terminal connection. 2. FTP FTP stands for File Transfer Protocol. It is a application layer protocol that is used for transforming a file from one location to another, i.e. from one host to another host. It is a standard mechanism that is provided by TCP/IP.
  • 147. SERVICE LAYER PROTOCOLS & SECURITY APPLICATION LAYER 3. TFTP TFTP stands for Trivial File Transfer Protocol is a application layer protocol, used for sending a file from the server to the client. Trivial File Transfer Protocol uses the concept of UDP to share files between server and client. 4. SMTP SMTP stands for Simple mail transfer protocol is used to transfer the mails. It defines how both commands and responses must be sent back and forth. It is used two times, between the sender and the sender’s mail server and between the two mail servers.
  • 148. SERVICE LAYER PROTOCOLS & SECURITY APPLICATION LAYER 5. SNMP SNMP stands for Simple network management protocol which is used to collect and organize the data of managed devices on IP networks. It also modifies the information to change the behavior of the devices. 6. DNS DNS stands for Domain Name System is a decentralized naming system for the computers and other devices on the internet to translate the domain name of the devices connected on the internet or any other private network to the numerical IP addresses and vice versa.
  • 149. SERVICE LAYER PROTOCOLS & SECURITY APPLICATION LAYER 7. DHCP DHCP stands for Dynamic Host Configuration Protocol. It is a network management protocol present in the application layer. With its help, an Internet Protocol IP address can be assigned to any device or node on a network dynamically so that they can communicate using this IP.
  • 150. SERVICE LAYER PROTOCOLS & SECURITY DESIGN SMART SYSTEM USING IOT COMPONENTS 1.Sensors and Devices Devices and sensors are the “thing” part of IoT projects. These and other devices interact with the physical environment. It is not only important that they accurately read the phenomenon application needs, but also, they have to be integrated with the overall system architecture too.
  • 151. SERVICE LAYER PROTOCOLS & SECURITY DESIGN SMART SYSTEM USING IOT COMPONENTS 1.Sensors and Devices Device configuration is another important feature. Some devices provide configuration programs while others require internal reprogramming to change their behaviour. Finally, you must evaluate the power source the use (batteries, solar panels, AC, etc.) since it has a strong impact in the system maintenance.
  • 152. SERVICE LAYER PROTOCOLS & SECURITY DESIGN SMART SYSTEM USING IOT COMPONENTS 2.Communications Although the “i” in IoT stands for internet, you have different kinds of networks available for communications among devices and with the platform. Choosing the right networking technology depends on the characteristics and requirements of the project. It is common to use more than one technology in an IoT project.
  • 153. SERVICE LAYER PROTOCOLS & SECURITY DESIGN SMART SYSTEM USING IOT COMPONENTS 3.Platform The software platform of your IoT projects will be in charge of managing the devices (onboarding process, monitoring, etc.) and receiving and processing the messages. It also must provide APIs for reading the gathered data. Platforms are usually deployed in the cloud, but you should check if they can be deployed on- premises in case the project is big enough and investing in computing hardware is an option.
  • 154. SERVICE LAYER PROTOCOLS & SECURITY DESIGN SMART SYSTEM USING IOT COMPONENTS 4.Applications All IoT projects are carried out for a purpose. Maybe the goal is receiving an alarm when a laboratory room reaches a certain temperature or optimizing the water supply of a city. In other cases, IoT projects are used for reducing the power consumption of a building or predicting the maintenance of an industrial engine.
  • 155. SERVICE LAYER PROTOCOLS & SECURITY DESIGN SMART SYSTEM USING IOT COMPONENTS 4.Applications All IoT projects are carried out for a purpose. Maybe the goal is receiving an alarm when a laboratory room reaches a certain temperature or optimizing the water supply of a city. In other cases, IoT projects are used for reducing the power consumption of a building or predicting the maintenance of an industrial engine.