Module 2 :

Reference Architecture
Phases of IOT Architecture
There are different phases in the architecture of IoT but they can vary according to the
situations but generally, there are these four phases in the architecture of IoT

Networked Devices
• These are the physical devices which include sensors, actuators, and transducers.
• These are the actual devices that collect and send the data for processing.
• They are capable of receiving real-time data and they can convert the physical
quantities into electrical signals which can be sent through a network.
Data Aggregation
• It is a very important stage as it includes converting the raw data collected by
sensors into meaningful data which can be used to take actions.
• It also includes Data Acquisition Systems and Internet Gateways.
• It converts the Analog signals provided by sensors into digital signals.
Final Analysis
• This is a stage that includes edge IT analytics and the processing of data to make
it more efficient and fully capable of execution.
• It also includes managing and locating all the devices correctly
Cloud Analysis
• The final data is received here and analyzed closely and precisely in data centers.
• They process and clean the data to make it free from any kind of errors and
missing values. After this stage, data is ready to be sent back and executed to
perform operations.
Reference Model and
Architecture:
•An ARM consists of two main parts: a Reference model and a Reference
Architecture.
•A reference model describes the domain using a number of sub-models

Reference Model
Reference Architecture
1 Reference Architecture
• An IoT reference architecture serves as a foundational blueprint that outlines the
essential components and interactions within an IoT system.
• It provides a solid starting point for designing and implementing IoT solutions.
Purpose and Benefits of Using a Reference
• A reference architecture serves as a standardized blueprint that provides a clear
structure and guidelines for designing and implementing an IoT system.
• It enables consistency, promotes best practices, and facilitates communication and
collaboration among stakeholders.
• By leveraging a reference architecture, developers can reduce design complexity,
ensure interoperability, and accelerate the development process, ultimately leading to
more efficient and reliable IoT solutions.
Layers of IoT Reference Architecture
Perception Layer:
• This layer comprises the physical devices or sensors that collect
data from the environment or interact with the physical world.
• These devices can include temperature sensors, motion
detectors, cameras, and other IoT:enabled devices.
Network Layer:
• The network layer facilitates the connectivity and
communication between the IoT devices and the cloud or other
data processing components.
• It includes protocols, gateways, routers, and other networking
infrastructure to ensure seamless data transfer and reliable
connections.
Data Processing Layer:
• This layer involves processing and analyzing the data collected from IoT
devices.
• It may include edge computing devices or cloud:based platforms where
data is aggregated, filtered, transformed, and analyzed to derive valuable
insights.
Application Layer:
• The application layer encompasses the software applications or services
that utilize the processed IoT data to provide specific functionalities or
address specific use cases.
• These applications can range from real:time monitoring and control systems
to predictive analytics, machine learning algorithms, and automation
Benefits of Using IoT Reference
Architecture
• Common Framework: IoT reference architecture provides a
standardized framework for designing and implementing IoT
solutions, ensuring consistency and interoperability across systems.
• Security and Scalability: The architecture serves as a foundation for
implementing robust security and scalability measures, safeguarding
IoT systems against threats and enabling future growth.
• Cost Efficiency: By leveraging a reference architecture, organizations
can avoid reinventing the wheel and utilize existing technologies and
expertise, reducing the cost of development and deployment.
• Faster Time to Market: Utilizing a reference architecture accelerates
the implementation of IoT solutions, enabling organizations to get
their systems up and running more quickly and efficiently.
2 IOT Reference Model
• IoT domain model
The domain model captures the basic attributes of the main concepts and
the relationship between these concepts. A domain model also serves as
a tool for human communication between people working in the domain
in question and between people who work across different domains.
• Information Model
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 Modeling Language (UML) diagrams.
High-level IoT Information Model
• Functional model
• 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. The Functional View is typically derived from the Functional Model
in conjunction with high-level requirements.
• 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.
• 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 (e.g. processing or
storage Resources).
• 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, i.e. the Association objects for the IoT
Information Model. Associations between Virtual Entities can be static or dynamic depending on the
mobility of the Physical Entities related to the corresponding Virtual Entities.
• 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 such as the IoT Process Management FG when, for example, service requests from Applications or
the IoT Process Management are directed to the Resources implementing the necessary Services.
• 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, Composed Services) with the Enterprise (Business) Processes.
• Management functional group
• The Management FG includes the necessary functions for enabling fault and performance monitoring of the system,
configuration for enabling the system to be flexible to changing User demands, and accounting for enabling
subsequent billing for the usage of the system. Support functions such as management of ownership, administrative
domain, rules and rights of functional components, and information stores are also included in the Management FG.
• Security functional group
• The Security FG contains the functional components that ensure the secure operation of the system as well as the
management of privacy. The Security FG contains components for Authentication of Users (Applications, Humans),
Authorisation of access to Services by Users, secure communication (ensuring integrity and confidentiality of
messages) between entities of the system such as Devices, Services, Applications, and last but not least, assurance of
privacy of sensitive information relating to Human Users.
• Application functional group
• The Application FG is just a placeholder that represents all the needed logic for creating an IoT application. The
applications typically contain custom logic tailored to a specific domain such as a Smart Grid
• Communication model
• Safety
• the IoT Reference Model can only provide IoT-related guidelines for ensuring a safe system to
the extent possible and controllable by a sys- tem designer.
Eg: smart grid.
• Privacy
• Because interactions with the physical world may often include humans, protecting the User
privacy is of utmost importance for an IoT system. The IoT-A Privacy Model depends on the
following functional components: Identity Management, Authentication, Authorisation, and
Trust & Reputation
• Trust
• Generally, an entity is said to ‘trust’ a second entity when the first entity makes the
assumption that the second entity will behave exactly as the first entity expects.”
• Security
• The Security Model for IoT consists of communication security that focuses mostly on the
confidentiality and integrity protection of interacting entities and functional components
such as Identity Management, Authentication, Authorisation, and Trust & Reputation.
Views
• Views are useful for reducing the complexity of the Reference Architecture blue
prints by addressing groups of concerns one group at a time.

• 1) Functional View: Description of what the system does, and its main functions.
• 2) Information View: Description of the data and information that the system
• handles.
• 3) Development View: defines how to implement the system.
• 4) Operational View: defines how to keep the system alive in the field.
•
5) Deployment View: defines how to transition the system to live operation
various views in IoT
1) Development View:
The Development View defines how to implement the system. The Development
View addresses the concerns of developers and testers.
All software projects involve some amount of new code being written.This view
provides a stable environment for more detailed design work.

2) Deployment View:
The Deployment View defines how to transition the system to live operation.
Focuses on aspects of the system important after the system has been built and is ready to
be put into live operation.
It defines
-The physical environment it will run in.
-Hardware and hosting environment (processing nodes, network interconnections, disk
storage).
-Technical environment requirements for each processing node.
- Mapping of elements to the runtime environment that will execute them.
It is needed when the system has-
-Complex runtime dependencies.
3) Operational View:
• The Operational View defines how to keep the system alive in the field
• It identifies a system-wide strategy for addressing operational concerns.
• It helps to ensure system is a reliable and effective part of its environment.
• For packaged software, it helps to illustrate the types of issues that could occur
• once installed.
• It documents how the system can be architected to reduce or address these
• concerns.
• The Operational View is the often least well-defined view, as many of the details
• are not fully-defined until construction is underway

4) Functional view:
• The functional view for the IoT Reference Architecture is presented in Fig ,and is
• adapted from IoT- A architecture.
• It consists of the Functional Groups (FGs) presented earlier in the IoT Functional
• Model, each of which includes a set of Functional Components (FCs).
Functional view
• 5) Information view:
• The information view consists of
• (a) The description of the information handled in the IoT System, and
• (b) The way this information is handled in the system;
• in other words, the information life cycle and flow (how information is
created,
• processed, and deleted), and the information handling components
Real-World Design Constraints:
The real world design constraints are mostly applied to devices and network
components. It’s classified into two types:-
Design Constraints

1) Functional Constraints 2)Non-Functional Constraints:

1) Technical constraints 2)Non-Technical constraints

Functional
Constraints:
• Functional design constraints in IoT refer to the specific requirements
and limitations that govern the functionality and operation of IoT
systems. Here are some common functional design constraints in IoT:
• - Specific sensing and actuating capabilities: Sensing principle and data
requirements: Sometimes continuous sampling of sensing data is
required. For some applications, sampling after specific intervals is
required. The parameters like higher network throughput, data loss,
energy use, etc are decided based on sensing principle.
• -Programming and embedded intelligence: Devices in the IoT are
heterogeneous such as various computational architectures, including
MCUs (8-, 16-,32- bit, ARM, 8051, RISC, Intel, etc.), signal conditioning
(e.g. ADC), and memory (ROM, S/F/D) RAM, etc.), communications
media, peripheral components (sensors, actuators, buttons, screens,
• Data Collection and Processing: IoT systems need to efficiently collect
and process data froma variety of sensors and devices. Design
constraints include defining the types of data to be collected,
determining the frequency and volume of data, and establishing the
processing requirements for real-time or batch processing.
• -Gateway: Gate way devices or proxies are selected according to need
of data transitions.
• Device Compatibility: IoT systems often involve multiple devices from
different manufacturers with varying communication protocols and
data formats. Design constraints include ensuring device
compatibility, defining communication standards or protocols, and
establishing mechanisms for device discovery, registration, and
integration.
Non-Functional Constraints:
• Non functional constraints are having two types:
1) Technical constraints
2) Non-Technical constraints
1)Technical constraints:
• Technical constraints in IoT refer to the limitations and
considerations related to the underlying technology and
infrastructure of IoT systems.
• These constraints impact the design, implementation,
and performance of IoT solutions.
• Network Bandwidth: IoT devices generate and transmit large
amounts of data, which can strain network bandwidth. Technical
constraints include the availability and capacity of the network
infrastructure to handle data traffic efficiently and ensure timely
delivery of data.
• Security and Privacy: IoT systems face significant security and privacy
challenges due to the large attack surface and potential vulnerabilities
of connected devices. Technical constraints involve implementing
robust security measures, including authentication, encryption,
secure communication protocols, and intrusion detection systems, to
protect data and devices from unauthorized access and attacks.
• Connectivity: IoT devices require reliable and secure connectivity to
transmit data to the cloud or other systems. Design constraints
include determining the connectivity requirements (e.g., Wi-Fi,
cellular, LPWAN), ensuring network coverage and quality, and
establishing mechanisms for seamless and robust communication.
• Interoperability: IoT devices come from different manufacturers and may use
various
communicationprotocolsanddataformats.Thearchitectureshouldsupportintero
perabilityby providing mechanisms to integrate heterogeneous devices and
systems seamlessly.
• Integration with existing systems : IoT systems must be able to integrate with
existing systems, such as enterprise resource planning (ERP) systems,
customer relationship management (CRM) systems, and supply chain
management (SCM) systems. This requires the use of common interfaces and
protocols.
• Maintenance and repair: IoT devices may be deployed in remote or hard-to-
reach areas,where maintenance and repair may be difficult. This constraint
must be considered during the design phase to ensure that the devices can be
easily maintained and repaired, or that they have failover mechanisms in
place to ensure continuity of service.
2) Non-Technical Constraints:
• Legal and regulatory compliance: IoT deployments must adhere to various laws and regulations,
including consumer protection, data privacy, security, and product safety. Complying with legal
requirements and industry standards is a non-negotiable constraint that must be considered during the
design and implementation phases.
• -Cultural and social factors: IoT systems may encounter cultural or social barriers that can impact user
acceptance and adoption. Factors like cultural norms, language barriers, and accessibility requirements
must be considered to design inclusive IoT solutions that cater to diverse user needs.
• -Interoperability and standardization: IoT involves a multitude of devices, platforms, and
communication protocols. Interoperability challenges can arise due to the lack of standardized
interfaces and protocols. Ensuring compatibility and interoperability between different IoT devices and
systems is a non-technical constraint that needs to be addressed to facilitate seamless integration.
• -Cost: IoT devices must be designed to be cost-effective, as they are often deployed in large numbers.
This requires the use of low-cost components, efficient manufacturing processes, and streamlined
supply chains.
• -Ethical considerations: IoT devices and systems can raise ethical concerns,
particularly regarding issues like surveillance, consent, and data ownership. Designing
IoT systems that respect ethical principles and prioritize the well-being and autonomy
of individuals is a significant constraint.
• -Social acceptance and trust: Widespread adoption of IoT technologies depends on
public acceptance and trust. Concerns regarding privacy, security, and the potential
impact on employment or societal structures must be addressed to gain public trust
and ensure social acceptance.
• -Business models and economic viability: Developing sustainable business models for
IoT solutions is crucial. The cost of devices, infrastructure, maintenance, and
connectivity must be balanced with potential revenue streams and return on
investment (ROI). Understanding the economic viability and ensuring scalability is a
non-technical constraint that influences IoT implementation.
IoT Visualization
• IoT Visualization is the use of visual representation techniques such as charts, graphs,
and maps to analyze and display data collected from IoT devices. It is a crucial aspect
of the Internet of Things (IoT) as it helps to make sense of the vast amounts of data
generated by connected devices.
• Importance of IoT Visualization
• The importance of IoT Visualization lies in its ability to transform raw data into
actionable insights that can drive business decisions. By providing real-time insights
into the performance of connected devices and systems, IoT visualization can help
organizations optimize their operations, improve efficiency, and enhance the customer
experience.
• IoT Visualization can also aid in identifying patterns and trends in data that might not
be immediately apparent through text-based reports. This can lead to a more
comprehensive understanding of the data and enable better decision-making.
Types of IoT Visualization
• Real-time dashboards : These are interactive interfaces that display
real-time data from IoT devices in a visual format. They can be
customized to show key performance indicators (KPIs), trends, and
alerts, allowing users to quickly identify and respond to issues as they
arise.
• Heat maps and choropleths: These are geographic visualizations that
use color-coded maps to display IoT data in specific regions or areas.
Heat maps show the concentration or density of IoT data, while
choropleths display IoT data on a per-capita or per-unit area basis.
• Graphs and charts: These are traditional visualization techniques that
use graphs and charts to display trends, patterns, and relationships in
IoT data. Common types of graphs and charts used in IoT Visualization
include line graphs, bar charts, and pie charts.
• 3D visualizations: These are immersive visualizations that use 3D
models and virtual reality (VR) technologies to provide a more
realistic and interactive view of IoT data. They are useful for
visualizing complex and detailed IoT data in a way that is more easily
understandable.
• Maps and geospatial visualizations: These are visualizations that use
maps and geospatial data to display IoT data in a spatial context. They
can be used to analyze data from IoT devices that are distributed
across large geographic areas, such as weather sensors or traffic
monitoring devices.
Thank you