0% found this document useful (0 votes)
23 views

Module 3 - Fog Edge Computing

Uploaded by

Shivanshu gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
23 views

Module 3 - Fog Edge Computing

Uploaded by

Shivanshu gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

MODULE 3

Topic #1
Fog/ Edge Computing

Presented by,
Dr M Zahid Ansari
Mechanical Engg., IIITDM Jabalpur
Fog/ Edge Computing

2
Fog/ Edge Computing
• Edge is the junction point between the industrial world
and the IoT world in the cloud. It can be decomposed
into three macro components

3
Cont’d
• Edge Computing is a new, upcoming component
that uses data to perform an action at site level or to
provide insights to headquarters
• The edge computing must have the following features:
– The ability to perform an action on behalf of the I-IoT
middleware, either offline or online
– The ability to host custom applications
– The ability to run analytics in standalone mode, offline, in
collaboration with the I-IoT middleware, or in collaboration
with the middleware of the local headquarters
– The ability to carry out actions or download analytics from the
I-IoT middleware
– The ability to send unstructured or a specific set of data to the
I-IoT middleware on demand or when triggered by a condition. 4
Cont’d
IoT Edge versus the IIoT Edge:
• IoT Edge manages from 10 to 50 measures per piece of device,
whereas the IIoT Edge can manage from 300 to 30,000 measures.
• IIoT Edge should also provide a simple way to configure measures
from remote sites through the Edge Manager.
• Updating the signals to be monitored is a weekly activity that
should be performed by the operations manager.
• Moreover, industrial security requires a strong cyber-security
assessment and a high-fidelity architecture because we seldom
connect the sensors over the internet directly. Fortunately, the IIoT
is less restrictive in terms of budgeting.
• From the perspective of the computational architecture on the
edge side, the IoT has introduced the concept of the Fog. The
word "fog" refers to its cloud-like properties, but closer to the
"ground", i.e. IoT devices 5
Cont’d
Fog versus the IIoT edge
• A few years ago, Cisco coined the term fog computing to
describe a layer of computing at the Edge side.
• This layer allows us to pre-process data to be transported
to the IoT Hub quickly and securely.
• Fog computing pushes the elaboration and computation
of resources to the local network and processes data in a
fog node or IoT gateway.
• In the industrial sector, the Edge has the ability to work
in collaboration with a local headquarters, where it can
find more computational resources before sending the
data to the centralized IoT Data Hub, whether this is in
the cloud or not. 6
Cont’d
• Fog computing is a decentralized computing
infrastructure in which data, compute, storage and
applications are located somewhere between the data
source and the cloud.
• Like edge computing, fog computing brings the
advantages and power of the cloud closer to where data
is created and acted upon.
• Many people use the terms fog computing and edge
computing interchangeably because both involve
bringing intelligence and processing closer to where the
data is created.
• This is often done to improve efficiency, though it might
also be done for security and compliance reasons. 7
Cont’d
• Although edge devices and sensors are where data is generated
and collected, they sometimes don't have the compute and
storage resources to perform advanced analytics and machine
learning tasks.
• Though cloud servers have the power to do this, they are often too
far away to process the data and respond in a timely manner.
• There are any number of potential use cases for fog computing.
One increasingly common use case for fog computing is traffic
control. Because sensors -- such as those used to detect traffic --
are often connected to cellular networks, cities sometimes deploy
computing resources near the cell tower.
• These computing capabilities enable real-time analytics of traffic
data, thereby enabling traffic signals to respond in real time to
changing conditions.
8
Cont’d
• Autonomous vehicles essentially function as edge devices because
of their vast onboard computing power. These vehicles must be
able to ingest data from a huge number of sensors, perform real-
time data analytics and then respond accordingly.
• Because an autonomous vehicle is designed to function without
the need for cloud connectivity, it's tempting to think of
autonomous vehicles as not being connected devices.
• Even though an autonomous vehicle must be able to drive safely in
the total absence of cloud connectivity, it's still possible to use
connectivity when available.
• Another good example of fog computing would be an embedded
application on a production line, where a temperature sensor
connected to an edge server would measure the temperature
every single second. This data would then be forwarded to the
cloud application for monitoring of temperature spikes.
9
Cont’d
• The edge computing: It is made up of the analytics running
on the Edge for filtering, aggregation, and advanced anomaly
detection. These analytics should be deployed remotely from
the cloud through the Edge Manager. The Edge Manager
running on the cloud side should also be able to request
specific actions to be carried out on the Edge side.
• It is very important to apply white-listing and input-validation
to avoid exposing the Edge to cyber attacks.
• Edge computing normally subscribes to the Data Bus exposed
by the Edge Gateway and consumes data for data processing.
• In some circumstances, edge computing invokes cloud or
local servers through a web service to run advanced
computational functions.
10
Cont’d
• Edge internet protocols: The most important protocols are:
– Message Queue Telemetry Transport (MQTT) and the secure
channel MQTTS are the most important ISO protocols for machine-
to-machine communication. The standard is ISO/IEC PRF 20922.
MQTT is based on the publish/subscribe pattern.
– Advanced Message Queuing Protocol (AMQP) was developed for
interoperability and messaging. AMQP is also based on the
publish/subscribe pattern. It is similar to MQTT, but it is a heavier
protocol.
– HTTP and HTTPS are not real protocols for IoT, but are normally used
in conjunction with the REST API to transmit data over the internet.
– The Constrained Application Protocol (CoAP) is a specific
protocol for IoT, based on the REST API.

11
Cont’d
Disadvantages of fog computing
• Physical location. Because fog computing is tied to a physical
location, it undermines some of the "anytime/anywhere" benefits
associated with cloud computing.
• Potential security issues. Under the right circumstances, fog
computing can be subject to security issues, such as Internet
Protocol (IP) address spoofing or man in the middle (MitM)
attacks.
• Startup costs. Fog computing is a solution that utilizes both edge
and cloud resources, which means that there are associated
hardware costs.
• Ambiguous concept. Even though fog computing has been around
for several years, there is still some ambiguity around the
definition of fog computing with various vendors defining fog
computing differently. 12
Cont’d
• Edge deployment and data flow scenarios : The five
most common options are the following:
– Edge on fieldbus
– Edge on OPC DCOM
– Edge on OPC Proxy
– Edge on OPC UA
– OPC UA on the controller
[Open Platform Communications (OPC);
Distributed Component Object Model (DCOM);
OPC Unified Architecture (OPC UA)]

13
Cont’d

14
Cont’d

15
Cont’d

16
Cont’d

17
Cont’d

18
Cont’d

19
Topic #2
Machine Learning and Data Science
in Industries

Presented by,
Dr M Zahid Ansari
Mechanical Engg., IIITDM Jabalpur

You might also like