UNIT -I

INTRODUCTION TO INTERNET OF THINGS

1. Explain the evolution of IoT.

2. Write in detail about the IoT Architecture.
3. Discuss the fog computing with neat diagram.
4. Explain Edge Computing with an example.
5. Compare and contrast Cloud Vs Fog Vs Edge computing in IoT.
6. Describe the seven layers of IoT Reference model designed by IoTWF.
7. Illustrate the oneM2M IoT standardized architecture and explain the
layers with neat diagram.
8. Describe the Core IoT Functional Stack.
1. Explain the evolution of IoT.
The evolution of IoT as it stands today began just a few decades ago with the development of
ARPANET, the first connected network and the granddad of today’s ‘Internet’. The history of IoT
starts from here and follows a timeline of milestone moments which we will chronicle below:
• 1982 – A graduate student in Carnegie Mellon University’s computer science department wants
to know if his department’s soda vending machine has cold soda bottles but doesn’t want to go
all the way there to check as the machine is quite a distance from his classroom. So, with the
help of two fellow students and a research engineer, he develops a code that can let anyone on
the university ARPANET monitor the status of the vending machine; whether it has soda bottles
and whether they are cold or not. The evolution of IoT began here.
• 1989 – English computer scientist Tim Berners Lee proposes the framework of the World Wide
Web and lays the foundation of the Internet.
• 1990 – MIT’s John Romkey invents a toaster that can be turned on or off via the Internet. It was
connected to a computer as there was no Wi-Fi then, but this toaster is considered to be the
world’s first IoT device – the first ‘thing’ in the Internet of Things.
• 1993 – Quentin Stafford-Fraser and Paul Jardetzky from the University of Cambridge build the
Trojan Room Coffee Pot in their computer laboratory where an image of its interior is uploaded
to the building’s server thrice every minute for people to check the level of coffee when they
want a cup.
• 1999 – Current Executive Director of Auto-ID Labs at MIT, Kevin Ashton, coins the term Internet
of Things (IoT) in a presentation he makes at Proctor & Gamble about linking RFIDs in their
supply chain to the internet.
• 2003-2004 – The term IoT starts to be used widely in mainstream publications like The
Guardian and Scientific American.
• 2005 – The United Nations International Telecommunications Union acknowledges the impact
of IoT in its report.
• 2008 – The first IoT conference is held in Zurich, bringing together researchers and
practitioners from academia and industry to take part in the sharing of knowledge. In the same
year, the US National Intelligence Council recognized IoT as one of the six disruptive civil
technologies. The Evolution of IoT gained popularity from this point onwards.
• 2011 – The Cisco Internet Business Solutions Group (CIBSG) announces in their white paper
that the true birth of IoT was between 2008 and 2009 where the number of things connected
to the internet exceeded the number of people connected to it.
• 2012 and beyond – Companies like Apple and Samsung make waves with their smartphones,
there is a proliferation of AI-powered personal assistants like Google Home and Amazon Alexa,
 we all start to have devices that control individual things in our home, all working in concert
with our computers and phones to share data and interact. Today, all our devices work in
tandem over the internet.
• The future seems ripe with a host of endless possibilities which only go to show that the
evolution of IoT and the growth of IoT technologies has gone past the point of no return.
Technology today not only pushes past barricades we once thought insurmountable but also
moves us towards a world where equal access to the internet and its resulting technological
marvels will be available to everyone. IoT will continue to evolve in many ways which will amaze
and astound us, ultimately creating a truly limitless potential for everyone.

2. Write in detail about the IoT Architecture.

Fig. Four stage IoT architecture

The architecture of IoT is divided into 4 different layers i.e. Sensing Layer, Network Layer, Data
processing Layer, and Application Layer.
Sensing Layer:
• The sensing layer is the first layer of the Internet of Things architecture and is responsible
for collecting data from different sources.
• This layer includes sensors and actuators that are placed in the environment to gather
information about temperature, humidity, light, sound, and other physical parameters.
• Wired or wireless communication protocols connect these devices to the network layer.
Network Layer:
• The network layer of an IoT architecture is responsible for providing communication and
connectivity between devices in the IoT system.
• It includes protocols and technologies that enable devices to connect and communicate with
each other and with the wider internet.
• Examples of network technologies that are commonly used in IoT include WiFi, Bluetooth,
Zigbee, and cellular networks such as 4G and 5G technology.
• Additionally, the network layer may include gateways and routers that act as intermediaries
between devices and the wider internet, and may also include security features such as
encryption and authentication to protect against unauthorized access.
Data processing Layer:
• The data processing layer of IoT architecture refers to the software and hardware
components that are responsible for collecting, analyzing, and interpreting data from IoT
devices.
• This layer is responsible for receiving raw data from the devices, processing it, and making
it available for further analysis or action.
• The data processing layer includes a variety of technologies and tools, such as data
management systems, analytics platforms, and machine learning algorithms.
• These tools are used to extract meaningful insights from the data and make decisions based
on that data.
• Example of a technology used in the data processing layer is a data lake, which is a
centralized repository for storing raw data from IoT devices.
Application Layer:
• The application layer of IoT architecture is the topmost layer that interacts directly with the
end-user.
• It is responsible for providing user-friendly interfaces and functionalities that enable users
to access and control IoT devices.
• This layer includes various software and applications such as mobile apps, web portals, and
other user interfaces that are designed to interact with the underlying IoT infrastructure.
• It also includes middleware services that allow different IoT devices and systems to
communicate and share data seamlessly.
• The application layer also includes analytics and processing capabilities that allow data to
be analyzed and transformed into meaningful insights.
• This can include machine learning algorithms, data visualization tools, and other advanced
analytics capabilities.
3. Discuss the fog computing with neat diagram.

Fog computing places resources like storage and processing closer to where data is generated,
using devices like routers to speed up responses, save bandwidth, and enhance security. It
complements cloud computing by handling quick, local tasks, while the cloud manages extensive
processing and storage.
1. Features of Fog Computing
Fog nodes (FNs) are placed near devices to improve service and resource use, like storage and
networking. Here’s how fog computing is different from cloud computing:
• Location Awareness and Low Latency: FNs provide services based on where devices
are, resulting in very quick responses and better real-time decisions.
• Geographic Distribution: FNs are located in different places to ensure good data
transfer between them and IoT devices.
• Decentralization: Multiple FNs work together on big computing tasks, so there’s no need
for a central server.
• Real-Time Services: FNs deliver instant responses, which is important for systems that
need quick actions.
• Efficient Cloud Storage Use: FNs handle and filter data locally, sending only the
necessary information to the cloud.
• Heterogeneity: FNs come in different types and can use both wired and wireless
connections.
• Mobility Support: FNs connect directly with mobile devices, allowing for tracking of user
location and identity.
2. Fog Computing Architecture
• The fog computing architecture is divided into three tiers: edge, fog, and cloud, each with
increasing processing and storage capabilities.
• The edge level is where IoT devices like mobile phones and sensors are located. It has
minimal processing and storage, mainly handling basic tasks and data collection.
• The fog level sits between the edge and cloud. It includes Fog Nodes (FNs) such as routers
and gateways, offering more processing power and storage. These nodes handle some tasks
locally, reducing latency and load on the cloud.
• The cloud level is the most powerful tier, located furthest from the edge. It provides
substantial processing and storage resources and supports advanced services such as
Infrastructure as a Service (IaaS), Software as a Service (SaaS), and Platform as a Service
(PaaS). The cloud handles tasks that require extensive computational power and large-
scale data storage, which are beyond the capabilities of the fog level.
• Fog nodes connect IoT devices and cloud servers using various methods, including wireless (e.g.,
Bluetooth, Zigbee) and wired (e.g., optical fiber, Ethernet) connections, depending on system
needs.

Fig. 2 Fog Architecture

3. WORKING OF FOG COMPUTING
• Introducing a fog layer between the centralized cloud and end devices greatly improves
system performance. Here’s how fog computing integrates with cloud computing:
• Data from end devices and IoT gadgets, such as mobile phones, cameras, and laptops, is
directed to the nearest fog server for processing. This fog server, located in the second layer,
handles the data before it reaches the cloud.
• Data requiring quick responses or sensitive to latency is prioritized by the fog servers. Once
processed, results or actions are sent back to the end devices. Additionally, condensed data
is transmitted to cloud servers in the third layer for further analysis, ensuring only refined
data is stored in the cloud.
• If fog servers face resource limitations or lack necessary information, they can seek
assistance from neighbouring servers or forward the request to cloud servers in the third
layer. Data that is less time-sensitive is typically sent to the cloud for processing and storage.
After processing, responses are delivered to users through the fog servers.
Advantages
• Faster response times with local data processing.
• Saves bandwidth by reducing data sent to the cloud.
• Improved security with local data handling.
• Scalable by adding more fog nodes.
Disadvantages
• Complex to manage multiple fog nodes.
• Limited processing power compared to the cloud.
• Challenging security management across many nodes.
• Compatibility issues between different fog nodes.
Applications
• Smart Cities: Manages real-time data for traffic control and public safety.
• Healthcare: Enables remote monitoring and quick analysis of patient data.
• Industrial Automation: Improves operations with local data processing from machinery.
• Connected Vehicles: Enhances real-time communication and processing for autonomous
driving.

4. Explain Edge Computing with an example.

Edge computing is a distributed computing method that brings data processing and storage
closer to where the data is generated. This improves response times and saves bandwidth by using
edge devices with computing capabilities, which allows for faster data processing than fog devices,
often at a lower cost. This approach also makes better use of edge devices.
Today's edge devices are equipped with advanced features like artificial intelligence. Edge
computing leverages this intelligence to reduce the load on network and cloud servers. It also
provides hardware security and low power consumption and can enhance security by encrypting
data closer to the network core.
Although edge computing is similar to fog computing, there are key differences. Edge devices
have limited resources and cannot replace cloud or fog computing but can complement these
technologies.
Edge computing focuses on processing and storing data close to users and their applications.
This reduces latency and offers protection against internet disruptions. It can drive advancements
in areas like smart homes, autonomous vehicles, surgical robotics, and real-time gaming.
As an alternative to cloud computing, edge computing supports applications needing high-
speed and continuous availability. By reducing dependency on internet connectivity, it prevents
slowdowns or failures that occur when internet connections are unreliable. This proximity to data
sources enhances performance and availability of applications.
EDGE COMPUTING ARCHITECTURE
Following are the fundamental components constituting an edge ecosystem:
• Edge Devices: Specialized equipment designed for specific purposes, equipped with limited
computational capabilities.
• Edge Nodes: Devices, servers, or gateways responsible for executing edge computing tasks.
• Edge Servers: Computers situated in facilities near edge devices. These systems manage
application workloads and shared services, necessitating higher computational power
compared to edge devices.
• Edge Gateways: Edge servers tasked with network operations such as tunneling, firewall
management, protocol translation, and wireless connections. These gateways can also support
application workloads.
• Cloud: A public or private cloud serving as a storage repository for containerized workloads,
encompassing applications and machine learning models. Additionally, the cloud hosts and
operates applications responsible for managing edge nodes.

Fig. Edge Computing Architecture

Device Edge refers to the physical location where edge devices operate, such as cameras, sensors,
and industrial machinery. These devices have the computing power needed to collect and transmit
data.
Local Edge is a system that supports applications and network tasks and has two layers:
• Application Layer: Handles applications that need more processing power than edge
devices can provide. This layer manages tasks like advanced video analytics or complex IoT
processing.
• Network Layer: Manages network components such as routers and switches, either
physical or virtual.
The Cloud or Nexus is where processing tasks are handled beyond the capability of edge nodes.
This layer operates either in an on-site data center or in cloud infrastructure.
 Virtualization stands as a critical component within an expansive edge computing infrastructure.
This technology simplifies the deployment and operation of numerous applications on edge
servers.
APPLICATIONS OF EDGE COMPUTING
• Smart Manufacturing: Enables predictive maintenance by analyzing real-time data from
machinery sensors, reducing downtime and improving efficiency.
• Telemedicine and Healthcare: Supports remote patient monitoring and wearable devices,
allowing real-time data analysis for timely medical interventions and personalized care.
• Autonomous Vehicles: Processes sensor data for quick decision-making on navigation,
collision avoidance, and road safety.
• Retail and Inventory Management: Enhances inventory tracking through data analysis from
sensors and cameras, optimizing supply chain operations and reducing stockouts.
• Smart Cities: Powers real-time processing for traffic management, waste management,
environmental monitoring, and public safety.
• Content Delivery and Streaming: Improves content delivery networks (CDNs) by caching
and serving content closer to users, reducing latency for smoother streaming.
• Energy Management: Optimizes energy grids and renewable sources with real-time
monitoring and control, enhancing efficiency and reliability.
• Edge AI and Surveillance: Facilitates AI-driven video analytics for real-time object detection,
facial recognition, and threat identification, boosting security.
• Fleet Management: Analyzes vehicle data in real-time for route optimization, driver
monitoring, and efficient logistics.
• Gaming and AR/VR: Reduces latency in cloud gaming and augmented/virtual reality,
ensuring smoother, more responsive experiences.
• Patient Monitoring: Processes data from hospital monitoring devices to detect unusual
trends and generate alerts.
• Oil and Gas Monitoring: Provides real-time analytics in remote locations to prevent failures
and shut down equipment before disasters occur.

5. Compare and contrast Cloud Vs Fog Vs Edge computing in IoT.

Edge computing, cloud computing, and fog computing are all about where computing and
storage resources are placed in relation to the data they handle. They each have their own specific
roles but share a common goal of improving how data is processed and managed. The key difference
between them is where the resources are located. Edge computing brings computing power close
to where the data is created, like on devices or local servers. Fog computing works between the
edge and the cloud, handling data closer to the source but not as locally as edge computing. Cloud
computing involves centralizing resources in large data centers, which process and store data from
various locations.

Fig. Comparison of Fog Vs Cloud Vs Edge Computing

EDGE COMPUTING
• Edge computing places computing and storage resources right where data is generated. This
means processing data close to its source, at the "edge" of the network.
• For example, a wind turbine might have a small setup of servers and storage installed on it. This
setup processes data from sensors within the turbine itself.
• Similarly, a railway station might use local computing and storage to handle data from track
and rail traffic sensors.
• The processed results can then be sent to a central data center for human review, archiving,
and combining with other data for more detailed analysis.
CLOUD COMPUTING
• Cloud computing involves a vast, scalable setup of computing and storage resources located in
various global regions. Cloud providers offer a range of pre-packaged services, making it a
popular choice for IoT operations.
• Despite its extensive resources and services, the nearest cloud facility may still be hundreds of
miles from where data is collected. This means data connections depend on internet reliability,
which can affect performance.
• In practice, cloud computing often serves as an alternative to or a complement for traditional
data centers. It brings centralized computing closer to data sources but not all the way to the
network edge.
FOG COMPUTING
• Fog computing provides a middle ground between the cloud and the edge. It addresses situations
where a cloud data center might be too distant and edge computing might be too limited or
dispersed.
• Fog computing places computing and storage resources closer to where data is generated, but not
necessarily right at the data source. It is useful in
environments with extensive data, such as smart
buildings, cities, or utility grids.
• For example, in a smart city, fog computing can
manage data from various sources like public transit,
municipal utilities, and city services. Since a single
edge deployment can't handle such large volumes of
data, fog computing uses multiple fog nodes across
the area to collect, process, and analyze the
information.
Edge and fog computing addresses three principal
network limitations: bandwidth, latency and
congestion or reliability.
Bandwidth: Bandwidth refers to the amount of
data a network can handle over time, usually
measured in bits per second. Networks, especially
wireless ones, have limited bandwidth. This means
there's a cap on how much data or how many
devices can use the network simultaneously. While
increasing bandwidth can help, it’s expensive and
Fig. Edge to Cloud Architectural Layer doesn't fully address other network issues.

Latency: Latency is the delay in sending data from one point to another. Although data transmission
ideally happens at the speed of light, long distances and network congestion can slow down this
process. This delay affects real-time analytics and decision-making, which can be critical in
scenarios like autonomous vehicles.
Congestion: The internet is a global network of networks that can become congested with high data
volumes from billions of devices. This congestion can lead to slow data transfers and
retransmissions. Network outages can worsen congestion and even cut off communication for some
users, rendering IoT applications ineffective during such outages.
6. Describe the seven layers of IoT Reference model designed by IoTWF.

The IoT World Forum (IoTWF) Standardised Architecture is a set of rules that enable those
who deal with the Internet of Things (IoT) to accomplish their jobs better. These recommendations
were developed in 2014 by a consortium of large corporations, including Cisco and IBM. These
guidelines are super important in the IoT world b ecause they provide a way for people to create
and connect IoT systems. It's like having a map to build and grow IoT projects, making them work
well together and making it easier for everyone to use.
IoTWF architecture consists of seven layers, each layer specifying a different purpose. The
seven layers of the IoTWF Standardized Architecture include –

Fig. IoTWF Architecture

1. Physical Devices and Controllers (Things)
These are the actual "things" of the Internet of Things. These might be physical assets such
as machines or equipment. These "things" in the tech sector might also be sensors and devices
linked to these assets. Although they may not yet have sensors, we are heading towards increasingly
interconnected systems.
2. Connectivity
This layer bridges the gap between the Edge Node device and the cloud, ensuring that the
data can run smoothly. It is an important aspect since it ensures that data from the field may reach
its destination in the cloud or on-premise. This layer functions as a transportation system for your
IoT data, and it may take various routes, such as highways or backroads, to deliver your data where
it needs to go.
3. Edge Computing
This layer, also known as "Cloud Edge" or "Cloud Gateway" computing, is crucial in any IoT
system. Edge computing is a type of computing that occurs at or near the network's edge/at the
device layer. Several important tasks take place in this layer –
• Protocol conversion - Protocol conversion is similar to having a translator ensure that data
speaks the correct language while flowing between different portions of the IoT system.
• Routing - Consider routing to be traffic control. It routes data to the appropriate locations
for processing and analysis.
• Fast Decision-Making - This layer is likewise in charge of making rapid decisions to keep
things operating smoothly and with low delays.
4. Data Accumulation
IoT systems create large amounts of data, and this layer acts as a data storage warehouse. It is
necessary since this layer stores incoming data and prepares data for future processing. Once the
data is ready, it is sent to the next levels for analysis and decision-making.
5. Data Abstraction
We're finally making sense of the data. We collect similar data from a variety of sources, prioritise
critical information, and prepare data for a variety of applications.
6. Application Layer
The Application Layer is where the real action happens. It's fairly simple, and here's what it does:
• Control and Data Logic - Consider this layer to be the control centre for your IoT system.
It's where all the smart decisions are made.
• Wide Range of Functions - This layer performs a wide range of functions, including
monitoring how everything works, optimising processes to improve them, managing alarms when
something goes wrong, analysing data to find important patterns, setting up control rules, and even
handling logistics and understanding consumer behaviour.
7. Collaboration and Processes
Finally, this layer integrates everything. It is the point at which individuals engage with the IoT
system. Data and apps are used to make choices, optimise operations, and generate value. This layer
connects technology to real-world advantages such as enhancing businesses or improving our lives.

7. Illustrate the oneM2M IoT standardized architecture and explain the layers
with neat diagram.

• In an effort to standardize the rapidly growing field of machine-to-machine (M2M)

communications, the European Telecommunications Standards Institute (ETSI) created the
M2M Technical Committee in 2008. The goal of this committee was to create a common
architecture that would help accelerate the adoption of M2M applications and devices.
 • Over time, the scope has expanded to include the Internet of Things. 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.
• The oneM2M architecture divides IoT functions into three major domains: the application
layer, the services layer, and the network layer.

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.
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. Riding on top is the common services layer.
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. Embodiments of this
communications infrastructure include wireless mesh technologies, such as IEEE 802.15.4, and
wireless point-to-multipoint systems, such as IEEE 801.11ah.
M2M Advantages
• Modular Standardisation: The framework refers to a modular standardisation plan,
enabling it to support additional common service functionalities and IoT requirements in the
future. Given the rapid advancement of IoT technologies, this flexibility is essential.
• Vendor Independence: This means that developers can use different suppliers for various
parts of their project and can follow different methods to build those parts. They don't have
to depend only on one supplier. It allows developers greater flexibility and independence in
deciding which elements and techniques are perfect for their projects.
• Lower costs: OneM2M offers a toolbox of functions that programmers can use. Because of
this, businesses won't need to invest as much money upfront in their IoT initiatives (smart
gadgets).
• Interoperability: OneM2M guidelines ensure that various IoT devices and apps may
communicate with one another without difficulty, much like individuals from many nations
speaking a common language. As a result, any IoT app can quickly locate and interact with
any IoT device, enabling smooth IoT integration.
The oneM2M IoT Standardised Architecture offers a standardized architecture that improves
interoperability and makes it easier to design IoT applications. It facilitates easy connection and
data sharing between IoT devices and applications from different manufacturers and domains by
splitting IoT functions into three layers: application, services, and network. The growth of IoT
technology across businesses depends on the general acceptance of this standardized methodology.

8. Describe the Core IoT Functional Stack.

The Core IoT Functional Stack represents the foundational framework of Internet of Things
(IoT) networks, organizing how smart devices interact and function within a connected
environment. IoT networks are built around “things” or smart objects that utilize contextual
information and configured goals to perform actions. These objects often rely on various layers to
ensure effective communication, data processing, and management. The stack is structured into
three primary layers:
Layer 1: Things: Sensors and Actuators Layer
At this layer, the physical devices need to fit the constraints of the environment in which they are deployed
while still being able to provide the information needed.
• Battery-powered or power-connected: Devices may be battery-powered, offering mobility but
limited by energy constraints, or connected to a continuous power source, providing longer
operation but less mobility.
• Mobile or static: Devices can be mobile, moving from one location to another, or static, fixed in
one place.
• Low or high reporting frequency: Devices vary in how often they report data, affecting energy
use and transmission range. High frequency requires more power.
• Simple or rich data: Devices can report simple data infrequently or complex data more often.
Rich data typically needs more power.
• Report range: The distance devices need to communicate with a gateway varies from a few
meters to several kilometers.
• Object density per cell: The number of devices per area affects network design, from sparse
sensor placements to dense installations like in telescopes.
Layer 2: Communications Network Layer
When smart objects are not self-contained, they need to communicate with an external system. In many
cases, this communication uses a wireless technology. This layer has four sublayers:
• Access Network Sublayer: The last mile of the IoT network is the access network, typically
using wireless technologies such as 802.11ah, 802.15.4g, and LoRa. Sensors connected to the
access network may also be wired. IoT uses various technologies suited to different scales:
o PAN (Personal Area Network): Short-range communication (e.g., Bluetooth).
o HAN (Home Area Network): Home-scale networks (e.g., ZigBee, BLE).
o NAN (Neighborhood Area Network): Covers several homes or a small community.
o FAN (Field Area Network): Large outdoor areas, such as agricultural fields.
o LAN (Local Area Network): Standard local networks (e.g., Ethernet, Wi-Fi).
• Point-to-Point Topologies: Devices communicate directly with one other device. This is less
common in IoT but can refer to single connections between devices and gateways.
• Point-to-Multipoint Topologies: One device (gateway) communicates with multiple other
devices (sensors). This is common in IoT networks where a gateway collects data from several
sensors.
• Gateways and Backhaul Sublayer: A common communication system organizes multiple
smart objects in a given area around a common gateway. The gateway communicates directly
with the smart objects and forwards the collected information through a longer-range medium
(backhaul) to a headend central station where the information is processed. The gateway also
acts as a router in IP networks.
 • Network Transport Sublayer: Ensures communication using network and transport layer
protocols such as IP and UDP to support various devices and media.
• IoT Network Management Sublayer: Uses additional protocols like CoAP and MQTT for
managing data exchange and network operations.
Layer 3: Applications and Analytics Layer
At this upper layer, applications process the collected data to control smart objects when necessary and
make intelligent decisions based on the information. This layer instructs the “things” or other systems to
adapt to analyzed conditions and change their behaviors or parameters.
• Analytics Applications: Process and analyze data from multiple devices to provide insights,
trends, and system status.
• Control Applications: Manage and control device behavior based on real-time data, enabling
automated responses to specific conditions.
• Data vs. Network Analytics:
o Data Analytics: Analyzes collected data to provide actionable insights and predictions.
o Network Analytics: Monitors network performance and connectivity, ensuring efficient
system operation and identifying issues.