Module-3 Core IoT Functional Stack

Download as pdf or txt
Download as pdf or txt
You are on page 1of 67

Anjuman-i-Islam’s

M.H.Saboo Siddik College of


Engineering

Department of computer Engineering

Subject: Internet of Things (CSDLO6011)


Sem: V

Presented by: Prof. Ansari Fatima Anees


MODULE-3

The Core IoT Functional


Stack
A RECALL???
SIMPLIFIED IOT ARCHITECTURE
? This IoT framework highlights the fundamental
building blocks that are common to most IoT
systems and it is intended to helps in designing
an IoT network.

? This framework is presented as two parallel


stacks:
1. The IoT Data Management and Compute
Stack (covered in Module 1)
2. Core IoT Functional Stack.
A SIMPLIFIED IOT ARCHITECTURE
? The intention of this architecture is to simplify
the IoT architecture into its most basic building
blocks
? and then to use it as a foundation to understand
key design and deployment principles that are
applied to industry-specific use cases.
THE CORE IOT FUNCTIONAL STACK

? IoT networks are built around the concept of “things,”


or smart objects performing functions and delivering
new connected services.
? These objects are “smart” because they use a
combination of contextual information and configured
goals to perform actions.
? These actions can be self-contained (that is, the
smart object does not rely on external systems for its
actions); however, in most cases, the “thing” interacts
with an external system to report information that
the smart object collects, to exchange with other
objects, or to interact with a management platform.
? In this case, the management platform can be used to
process data collected from the smart object and also
guide the behavior of the smart object.
THE CORE IOT FUNCTIONAL STACK

? The core Iot functional stack consist of three


layers:

1. Layer 1: Things: Sensors and Actuators Layer


2. Layer 2: Communications Network Layer
3. Layer 3: Applications and Analytics Layer
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER
? From an architectural standpoint, the variety of
smart object types, shapes, and needs drive the
variety of IoT protocols and architectures.
? There are many ways to classify smart objects. One
architectural classification could be:
1. Battery-powered or power-connected
2. Mobile or static
3. Low or high reporting frequency
4. Simple or rich data
5. Report range
6. Object density per cell
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER
■ Battery-powered or power-connected:

▪ This classification is based on whether the


object carries its own energy supply or
receives continuous power from an external
power source.
▪ Battery-powered things can be moved more easily
than line-powered objects.
▪ However, batteries limit the lifetime and amount of
energy that the object is allowed to consume, thus
driving transmission range and frequency.
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER

■ Mobile or static:
▪ This classification is based on whether the
“thing” should move or always stay at the
same location.
▪ A sensor may be mobile because it is moved from
one object to another (eg. a viscosity sensor
moved from batch to batch in a chemical plant) or
because it is attached to a moving object (eg. a
location sensor on moving goods in a warehouse
or factory floor).
▪ The frequency of the movement may also vary,
from occasional to permanent. The range of
mobility (from a few inches to miles away) often
drives the possible power source.
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER

■ Low or high reporting frequency:

▪ This classification is based on how often the


object should report monitored parameters.
▪ A rust sensor may report values once a month.
▪ A motion sensor may report acceleration several
hundred times per second.
▪ Higher frequencies drive higher energy
consumption, which may create constraints on
the possible power source (and therefore the
object mobility) and the transmission range.
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER
■ Simple or rich data:
▪ This classification is based on the quantity of
data exchanged at each report cycle.
▪ A humidity sensor in a field may report a simple daily
index value (on a binary scale from 0 to 255), while an
engine sensor may report hundreds of parameters, from
temperature to pressure, gas velocity, compression
speed, carbon index, and many others.
▪ Richer data typically drives higher power consumption.
▪ This classification is often combined with the previous
to determine the object data throughput (low
throughput to high throughput).
▪ A medium-throughput object may send simple data at
rather high frequency (in which case the flow structure
looks continuous), or may send rich data at rather low
frequency (in which case the flow structure looks
bursty).
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER

■ Report range:

▪ This classification is based on the distance at


which the gateway is located.
▪ For example, for your fitness band to communicate
with your phone, it needs to be located a few meters
away at most. The assumption is that your phone
needs to be at visual distance for you to consult the
reported data on the phone screen.
▪ If the phone is far away, you typically do not use it, and
reporting data from the band to the phone is not
necessary.
▪ By contrast, a moisture sensor in the asphalt of a road
may need to communicate with its reader several
hundred meters or even kilo meters away.
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER

■ Object density per cell:

▪ This classification is based on the number


of smart objects over a given area,
connected to the same gateway.
▪ An oil pipeline may utilize a single sensor at key
locations every few miles.
▪ By contrast, telescopes like the SETI Colossus
telescope at the Whipple Observatory deploy
hundreds, and sometimes thousands, of mirrors
over a small area, each with multiple gyroscopes,
gravity, and vibration sensors.
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER

▪ The initial task in network architectural is to


determine which technology should be used to
allow smart objects to communicate.
▪ This determination depends on the way the
“things” are classified.
▪ Different factors like mobility and throughput
are considered for the same.
▪ For example, some industries (such as
manufacturing and utilities) may include objects
in various categories, matching different needs.
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER

▪ First step in designing an IoT network is to


examine the requirements in terms of mobility
and data transmission (how much data, how
often).
▪ For example, a battery-operated highly mobile
object (like a heart rate monitor, for example)
likely has a small form factor. A small sensor is
easier to move or integrate into its
environment. At the same time, a small and
highly mobile smart object is unlikely to require
a large antenna and a powerful power
source. This constraint will limit the
transmission range and, therefore, the type of
network protocol available for its connections.
LAYER 1: THINGS: SENSORS AND ACTUATORS LAYER

▪ The criticality of data may also influence the


architecture.
▪ For example, a missing monthly report from an
asphalt moisture sensor may simply flag an
indicator for sensor (or battery) replacement.
▪ A multi-mirror gyroscope report missing for more
than 100 ms may render the entire system
unstable or unusable.
▪ These sensors either need to have a constant
source of power (resulting in limited mobility) or
need to be easily accessible for battery
replacement (resulting in limited transmission
range).
LAYER 2: COMMUNICATIONS NETWORK LAYER
▪ When smart objects are not self-contained, they
need to communicate with an external system.
▪ Once the form factors of the smart objects is
determined over its transmission capabilities
(transmission range, data volume and frequency,
sensor density and mobility), they ready to
connect the object and communicate.
▪ In many cases, this communication uses a
wireless technology.
▪ This layer has four sublayers:

■ Access network sublayer


■ Gateways and backhaul network sublayer
■ Network transport sublayer
■ IoT network management sublayer
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Access network sublayer:

▪ There is a direct relationship between the IoT


network technology and the type of connectivity
topology this technology allows.
▪ Each technology was designed with a certain
number of use cases in mind (what to connect,
where to connect, how much data to transport
at what interval and over what distance).
▪ These use cases determined the frequency band
that was expected to be most suitable, the frame
structure matching the expected data pattern
(packet size and communication intervals), and
the possible topologies that these use cases
illustrate.
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:


▪ As IoT continues to grow exponentially, it
encounters a wide variety of applications and
special use cases.
▪ For each of them, an access technology will be
required.
▪ IoT sometimes reuses existing access
technologies whose characteristics match more or
less closely the IoT use case requirements.
▪ Whereas some access technologies were
developed specifically for IoT use cases, others
were not.
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:

▪ One key parameter determining the choice of


access technology is the range between the
smart object and the information collector.
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:


LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Access network sublayer:
▪ Range estimates are grouped by category names
that illustrate the environment where data
collection over that range is expected.
▪ Common groups are as follows:
PAN (personal area network):
Scale of a few meters. This is the personal space
around a person. A common wireless technology for
this scale is Bluetooth.

HAN (home area network):


Scale of a few tens of meters. At this scale, common
wireless technologies for IoT include ZigBee and
Bluetooth Low Energy (BLE).
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:


NAN (neighborhood area network):
Scale of a few hundreds of meters. The term
NAN is often used to refer to a group of house
units from which data is collected.

FAN (field area network):


Scale of several tens of meters to several
hundred meters. FAN typically refers to an
outdoor area larger than a single group of house
units. The FAN is often seen as “open space”
(and therefore not secured and not controlled).
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:


LAN (local area network):
Scale of up to 100 m. This term is very common
in networking, and it is therefore also commonly
used in the IoT space when standard
networking technologies (such as Ethernet or
IEEE 802.11) are used.
Other networking classifications, such as MAN
(metropolitan area network, with a range of up
to a few kilometers) and WAN (wide area
network, with a range of more than a few
kilometers), are also commonly used
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:

W???
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:


▪ Similar achievable distances do not mean
similar protocols and similar characteristics.
Each protocol uses a specific frame format
and transmission technique over a specific
frequency (or band).
▪ Similar ranges also do not mean similar
topologies.
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:

topology and range

both are same or different???


LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Access network sublayer:

Topology describes the organization of the


nodes.

Range is dictated by factors such as the


frequency or operation, the signal structure,
and operational bandwidth.

For example, both IEEE 802.15.4 and LoRaWAN


implement star topologies, but the range of IEEE
802.15.4 is a few tens of meters, while LoRaWAN
can achieve a successful signal over many
kilometers. The bandwidth and signal structure
(modulation) are very different.
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Gateways and backhaul network sublayer:

▪ Data collected from a smart object may need to


be forwarded to a central station where data is
processed.
▪ As this station is often in a different location
from the smart object, data directly received
from the sensor through an access technology
needs to be forwarded to another medium (the
backhaul) and transported to the central
station.
▪ The gateway is in charge of this inter-medium
communication
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Gateways and backhaul network sublayer:

▪ The gateway communicates directly with the


smart objects.
▪ The role of the gateway is to forward the
collected information through a longer-range
medium (called the backhaul) to a headend
central station where the information is
processed.
▪ This information exchange is a Layer 7
(application) function, which is the reason this
object is called a gateway. On IP networks, this
gateway also forwards packets from one IP
network to another, and it therefore acts as a
router.
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Gateways and backhaul network sublayer:

▪ In most cases, the smart objects are static or


mobile within a limited area.
▪ The gateway is often static.
▪ However, some IoT technologies do not apply this
model.
▪ For example, dedicated short-range
communication (DSRC) allows vehicle-to-vehicle
and vehicle-to infrastructure communication.
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Gateways and backhaul network sublayer:

▪ In DSRC model, the smart object’s position relative


to the gateway is static.
▪ The car includes sensors and one gateway.
▪ Communication between the sensors and the
gateway may involve wired or wireless technologies.
▪ Sensors may also be integrated into the road
infrastructure and connect over a wired or wireless
technology to a gateway on the side of the road.
▪ A wireless technology (DSRC operates in the upper
5 GHz range) is used for backhaul communication,
peer-to-peer, or mesh communication between
vehicles.
▪ The range at which DSRC can communicate is
limited.
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Gateways and backhaul network sublayer:

▪ For IoT architectures, the choice of a backhaul


technology depends on the communication
distance and also on the amount of data that
needs to be forwarded.
▪ Eg
▪ when the environment is stable (for example,
factory or oil and gas field), Ethernet can be used
as a backhaul.
▪ In unstable or changing environments (for
example, open mines) where cables cannot safely
be run, a wireless technology is used. Eg WiFi
University Questions
Q1. Discuss in brief -Gateways and
Backhaul Sublayer in Core IoT Functional
stack. [ May 2022- 5 marks]
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Network transport sublayer:
▪ In a hierarchical communication architecture in which a
series of smart objects report to a gateway that conveys the
reported data over another medium and up to a central
station.
▪ However, practical implementations are often flexible, with
multiple transversal communication paths.
▪ For example, consider the case of IoT for the energy grid. Your
house may have a meter that reports the energy consumption to
a gateway over a wireless technology.
▪ Other houses in your neighborhood (NAN) make the same
report, likely to one or several gateways. The data to be
transported is small and the interval is large
▪ If your power consumption becomes unusually high, the utility
headend application server may need on-demand reporting from
your meter at short intervals to follow the consumption trend.
▪ From a standard vertical push model, the transport structure
changes and becomes bidirectional (downstream pull model
instead of upstream push)
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Network transport sublayer:


▪ To allow for such communication structure, a

network protocol with specific characteristics


needs to be implemented.
▪ The protocol needs to be open and standard

based to accommodate multiple industries and


multiple media.
▪ Scalability (to accommodate thousands or

millions of sensors in a single network) and


security are also common requirements.
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Network transport sublayer:


▪ For communication to be successful, network

and transport layer protocols such as IP and


UDP must be implemented to support the
variety of devices to connect and media to use.
▪ IP and UDP are the protocols that matches all

these requirements.
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ IoT network management sublayer:
▪ IP, TCP, and UDP bring connectivity to IoT

networks.
▪ Upper-layer protocols need to take care of data

transmission between the smart objects and other


systems.
▪ Multiple protocols have been created to solve IoT

data communication problems.


▪ Some networks rely on a push model (that is, a

sensor reports at a regular interval or based on a


▪ local trigger), whereas others rely on a pull model

(that is, an application queries the sensor


▪ over the network), and multiple hybrid approaches

are also possible.


LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Network transport sublayer:
▪ Some IoT implementers have suggested HTTP for

the data transfer phase.


▪ The sensor could use the client part to establish a
connection to the IoT central application (the
server), and then data can be exchanged.
▪ HTTP is used in some IoT applications, but HTTP

was not designed to operate in constrained


environments with low memory, low power, low
bandwidth, and a high rate of packet failure.
▪ Despite these limitations, other web-derived
protocols have been suggested for the IoT space.
▪ One example is WebSocket.
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ Network transport sublayer:

▪ WebSocket is part of the HTML5 specification,


and provides a simple bidirectional connection
over a single connection.
▪ Some IoT solutions use WebSocket to manage
the connection between the smart object and an
external application.
▪ WebSocket is often combined with other
protocols, such as MQTT (Message Queue
Telemetry Transport) to handle the IoT-specific
part of the communication.
LAYER 2: COMMUNICATIONS NETWORK LAYER

■ Network transport sublayer:


▪ MQTT uses a broker-based architecture.

▪ The sensor can be set to be an MQTT publisher

(publishes a piece of information), the


application that needs to receive the
information can be set as the MQTT subscriber,
and any intermediary system can be set as a
broker to relay the information between the
publisher and the subscriber(s).
▪ MQTT runs over TCP.

▪ A consequence of the reliance on TCP is that an

MQTT client typically holds a connection open


to the broker at all times.
LAYER 2: COMMUNICATIONS NETWORK LAYER
■ IoT network management sublayer:
? To respond to the limits of web-based protocols,
another protocol was created by the IETF
Constrained Restful Environments (CoRE) working
group: Constrained Application Protocol
(CoAP).
? CoAP uses some methods similar to those of HTTP
(such as Get, Post,Put, and Delete) but implements
a shorter list, thus limiting the size of the header.
CoAP also runs on UDP (whereas HTTP typically
uses TCP).
? CoAP also adds a feature that is lacking in HTTP
and very useful for IoT: observation.
? Observation allows the streaming of state changes
as they occur, without requiring the receiver to
query for these changes.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER

▪ At the upper layer, an application needs to


process the collected data, not only to control
the smart objects when necessary, but to make
intelligent decision based on the information
collected and, in turn, instruct the “things” or
other systems to adapt to the analyzed
conditions and change their behaviors or
parameters.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER

Analytics Versus Control Applications


▪ As IoT network spans more than a few sensors, the
power of the Internet of Things appears in the
applications that make use of the information
exchanged with the smart objects.
▪ Multiple applications can help increase the
efficiency of an IoT network.
▪ Each application collects data and provides a range
of functions based on analyzing the collected data.
▪ From an architectural standpoint, one basic
classification can be as follows:
1. Analytics application
2. Control application
LAYER 3: APPLICATIONS AND ANALYTICS LAYER

Analytics Versus Control Applications


? Analytics application:
▪ This type of application collects data from multiple
smart objects, processes the collected data, and
displays information resulting from the data that
was processed.
▪ The display can be about any aspect of the IoT
network, from historical reports, statistics, or
trends to individual system states.
▪ The important aspect is that the application
processes the data to convey a view of the network
that cannot be obtained from solely looking at the
information displayed by a single smart object.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER

Analytics Versus Control Applications


? Control application:
▪ This type of application controls the behavior of the
smart object or the behavior of an object related to
the smart object.
▪ For example, a pressure sensor may be connected to a
pump. A control application increases the pump speed
when the connected sensor detects a drop in pressure.
▪ Control applications are very useful for controlling
complex aspects of an IoT network with a logic that
cannot be programmed inside a single IoT object,
either because the configured changes are too
complex to fit into the local system or because the
configured changes rely on parameters that include
elements outside the IoT object.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER

Analytics Versus Control Applications


▪ Many advanced IoT applications include both
analytics and control modules.
▪ In most cases, data is collected from the smart
objects and processed in the analytics module.
▪ The result of this processing may be used to modify
the behavior of smart objects or systems related to
the smart objects.
▪ The control module is used to convey the
instructions for behavioral changes.
▪ When evaluating an IoT data and analytics
application, you need to determine the relative
depth of the control part needed for your use case
and match it against the type of analytics provided.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER

Data Versus Network Analytics


▪ Analytics is a term that describes

processing information to make sense of


collected data.
▪ In IoT, a possible classification of the

analytics function is as follows:


1. Data analytics:
2. Network analytics:
LAYER 3: APPLICATIONS AND ANALYTICS LAYER

Data analytics:
▪ This type of analytics processes the data

collected by smart objects and combines it to


provide an intelligent view related to the IoT
system.
▪ For example, a dashboard can display an

alarm when a weight sensor detects that a


shelf is empty in a store. (simple use case)
▪ For example, temperature, pressure, wind,

humidity, and light levels collected from


thousands of sensors may be combined and
then processed to determine the likelihood of a
storm and its possible path. (complex use case)
LAYER 3: APPLICATIONS AND ANALYTICS LAYER

Data analytics:
▪ Data analytics can also monitor the IoT

system itself.
▪ For example, a machine or robot in a

factory can report data about its own


movements.
▪ This data can be used by an analytics

application to report degradation in the


movement speeds, which may be
indicative of a need to service the robot
before a part breaks.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Network analytics:
▪ Most IoT systems are built around smart
objects connected to the network.
▪ A loss or degradation in connectivity is
likely to affect the efficiency of the system.
▪ Such a loss can have dramatic effects.
▪ For example, open mines use wireless
networks to automatically pilot dump
trucks. A lasting loss of connectivity may
result in an accident or degradation of
operations efficiency (automated dump
trucks typically stop upon connectivity loss).
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Network analytics:
▪ Loss of connectivity means that data
stops being fed to data analytics
platform, and the system stops making
intelligent analyses of the IoT system.
▪ A similar consequence is that the control
module cannot modify local object
behaviors anymore.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Data Versus Network Analytics

▪ Most analytics applications employ both data and


network analytics modules.

▪ When architecting an IoT system, one need to evaluate


the need for each one.
▪ Network analytics is necessary for connected systems.
▪ However, the depth of analysis depends on use cases.

▪ A basic connectivity view may be enough if the smart


objects report occasional status, without expectation for
immediate action based on this report.

▪ Detailed analysis and trending about network


performance are needed if the central application is
expected to pilot in near-real-time connected systems.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Data Analytics Versus Business Benefits

▪ Data analytics is a field where the value of


IoT is booming.
▪ Almost any object can be connected, and
multiple types of sensors can be installed on a
given object.
▪ Collecting and interpreting the data
generated by these devices is where the value
of IoT is realized.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Data Analytics Versus Business
Benefits
▪ From an architectural standpoint, ,we can define
static IoT network where a clear list of elements
to monitor and analytics to perform are
determined.
▪ Such static systems provides a clear view of the
state of the operation.
▪ However, a smarter architectural choice may be to
allow for an open system where the network is
engineered to be flexible enough that other
sensors may be added in the future, and where
both upstream and downstream operations are
allowed.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Data Analytics Versus Business Benefits

▪ This flexibility allows for additional


processing of the existing sensors and also
deeper and more efficient interaction with the
connected objects.

▪ This enhanced data processing can result in


new added value for businesses that are not
envisioned at the time when the system is
initially deployed.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Data Analytics Versus Business Benefits
▪ An example of a flexible analytics and control
application is Cisco Jasper, which provides a turnkey
cloud-based platform for IoT management and
monetization.

▪ Example
▪ Vending machines deployed throughout a city. At a
basic level, these machines can be connected, and
sensors can be deployed to report when a machine is
in an error state. A repair person can be sent to
address the issue when such a state is identified. This
type of alert is a time saver and avoids the need for
the repair team to tour all the machines in turn when
only one may be malfunctioning
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Data Analytics Versus Business Benefits
This alert system may also avoid delay
between the time when a machine goes into
the error state and the time when a repair
team visits the machine location.
LAYER 3: APPLICATIONS AND ANALYTICS LAYER
Data Analytics Versus Business Benefits
▪ With a flexible platform machine sensors can be
improved to also report when an item is sold.
▪ The central application can then be enhanced to
process this information and analyze what item is
most sold, in what location, at what times.
▪ This new view of the machines may allow for an
optimization of the items to sell in machines in a
given area. Systems may be implemented to
adapt the goods to time, season, or location—or
many other parameters that may have been
analyzed.
▪ Architecting open systems opens the possibility for
new applications.
SMART SERVICES

▪ The ability to use IoT to improve operations is


often termed “smart services.”
▪ Fundamentally, smart services use IoT and aim
for efficiency.
▪ For example, sensors can be installed on
equipment to ensure ongoing conformance with
regulations or safety requirements.
▪ This angle of efficiency can take multiple forms,
from presence sensors in hazardous areas to
weight threshold violation detectors on trucks.
SMART SERVICES
▪ Smart services can also be used to measure the
efficiency of machines by detecting machine
output, speed, or other forms of usage
evaluation.
▪ Entire operations can be optimized with IoT.
▪ Examples:
✔ In hospitality, presence and motion sensors can
evaluate the number of guests in a lobby and
redirect personnel accordingly.
SMART SERVICES
✔ In a store , if a customer is detected as staying
longer than the typical amount of time in front of
a shelf. Personnel can be deployed to provide
assistance.
✔ Movement of people and objects on factory floors
can be analyzed to optimize the production flow.
✔ sensors can be integrated in a light bulb. A sensor
can turn a light on or off based on the presence of
a human in the room.
✔ An even smarter system can use smarter sensors
that analyze multiple parameters to detect human
mood and modify accordingly the light color to
adapt to the learned preferences, or to convey
either a more relaxing or a more dynamic
environment.
SMART SERVICES
✔ smart grid applications can coordinate the
energy consumption between houses to regulate
the energy demand from the grid.
✔ washing machine may be turned on at night
when the energy demand for heating and
cooling is lower.
✔ A traffic jam is detected and anticipated
automatically by public transportation, and the
system can temporarily reroute buses or
regulate the number of buses servicing a
specific line based on traffic and customer
quantity, instantaneous or learned over
trending.
SMART SERVICES

▪ Architecting open IoT systems allows for


increased efficiency over time.

▪ When building an IoT network, one should


make sure to keep the system open for the
possibility of new smart objects and more traffic
on the system.
Thank You

You might also like