Iot Fundamentals: A Comprehensive Introduction To Iot Theory & Applications
Iot Fundamentals: A Comprehensive Introduction To Iot Theory & Applications
04
03
Smart Objects: The “Things” in
IoT
01 02
IoT Network Architecture and
Introduction to IoT Design
Introduction to IoT
60%
Cisco Systems predicts that by 2020,
this number will reach 50 billion. A 50%
Similarly, sensors are often used to control the heating, ventilation, and air-conditioning
makes them easier,
(HVAC) system. Temperature sensors are spread throughout the building and are used to cheaper, and more
influence the building management system’s (BMS’s)control of air flow into a room efficient to manage
Data Volume
Legacy device
support
CPU , Memory &
Security link constrained
networks
Scale
Analyzed real time
Data
Scale
The scale of a typical IT network is on the order of
several thousand devices typically printers, mobile
wireless devices, laptops, servers, and so on.
consider what happens when the scale of a network
goes from a few thousand endpoints to a few million.
How many IT engineers have ever designed a network
that is intended to support millions of routable IP
endpoints?.
Based on scale requirements of this order, IPv6 is the
natural foundation for the IoT network layer.
Security
IoT systems require
consistent mechanisms of authentication, encryption, and intrusion
prevention techniques.
For optimum security, IoT systems must:
Be able to identify and authenticate all entities involved in the IoT
service (that is, gateways, endpoint devices, home networks, roaming
networks, service platforms)
Ensure that all user data encrypted
Comply with local data protection legislation .
Establish rules based security policies.
Take a holistic, network-level approach to security.
Constrained Devices and Networks
oMost IoT sensors are designed for a single job, and they are
typically small and inexpensive.
oThis means they often have limited power, CPU, and memory,
and they transmit only when there is something important.
oBecause of the massive scale of these devices and the large,
uncontrolled environments where they are usually deployed,
the networks that provide connectivity also tend to be very
lossy and support very low data rates.
o IoT requires a new breed of connectivity technologies that
meet both the scale and constraint limitations.
Data
IoT devices generate a mountain of data
In IoT the data is like gold, as it is what enables businesses
to deliver new IoT services that enhance the customer experience, reduce
cost,
and deliver new revenue opportunities.
Unlike IT networks, IoT systems are designed to stagger data
consumption throughout the architecture, both to filter and reduce
unnecessary data going upstream and to provide the fastest possible
response to devices when necessary
Legacy Device Support
Supporting legacy devices in an IT organization is not usually a big problem
As IoT networks are deployed, they need to support the older devices already
present on the
network, as well as devices with new capabilities. In many cases, legacy
devices are so old that they don’t even support IP. For example, a factory may
replace machines only once every 20 years—or perhaps even longer However,
many of these legacy machines might support older protocols, such as serial
interfaces, and use RS- 232. In this case, the IoT network must either be capable of
some type of protocol translation or use a gateway device to connect these legacy
endpoints to the IoT network.
IoT Architectures
The aforementioned challenges and requirements of IoT systems have
driven a whole new discipline of network architecture. In the past several
years, architectural standards and frameworks have emerged to address the
challenge of designing massive-scale IoT networks.
The foundational concept in all these architectures is supporting data,
process, and the functions that endpoint devices perform. Two of the best-
known architectures are those supported by oneM2M and the IoT World
Forum (IoTWF), discussed in the following sections.
The oneM2M IoT Standardized
Architecture
One of the greatest challenges in designing an IoT architecture is
dealing with the heterogeneity of devices, software, and access
methods.
By developing a horizontal platform architecture, oneM2M is
developing standards that allow interoperability at all levels of the IoT
stack. For example, you might want to automate your HVAC system by
connecting it with wireless temperature sensors spread throughout
your office. You decide to deploy sensors that use LoRaWAN
technology The problem is that the LoRaWAN network and the
BACnet system that your HVAC and BMS run on are completely
different systems and have no natural connection point.
This is where the oneM2M common services architecture comes in.
The oneM2M architecture divides IoT functions into three major domains:
1-Applications layer: The oneM2M architecture gives major attention to
connectivity between devices and their applications. This domain
includes the application-layer protocols and attempts to standardize
northbound API definitions for interaction with business intelligence (BI)
systems. Applications tend to be industry-specific and have their own
sets of data models, and thus they are shown as vertical entities.
2-Services layer: This layer is shown as a horizontal framework
across
the vertical industry applications. At this layer, horizontal modules
include the physical network that the IoT applications run on, the
underlying management protocols, and the hardware. Examples
include
backhaul communications via cellular, MPLS networks, VPNs, and
so
On.
Network layer:
This is the communication domain for the IoT devices
and endpoints. It includes the devices themselves and the
communications network that links them.
In other cases, machine-to-machine communication is not necessary,
and the devices simply communicate through a field area network (FAN)
to use-case-specific apps in the IoT application domain.
Therefore, the device domain also includes the gateway device, which
provides communications up into the core network and acts as a
demarcation point between the device and network
domains.
The IoT World Forum (IoTWF) Standardized
Architecture
In 2014 the IoTWF architectural
committee (led by Cisco, IBM,
Rockwell
Automation, and others) published a
seven-layer IoT architectural
reference model. Each of the seven
layers is broken down into specific
functions, and security encompasses
the entire model.
layers of the IoT Function
Cyber Emergency