Scribd
Upload
5 views

test1 (1)

The document outlines the IoT reference model, detailing the domain model that captures the relationships between key concepts such as devices, sensors, actuators, and tags. It also describes the IoT reference architecture, which serves as a standardized blueprint for designing IoT systems, consisting of multiple layers including perception, network, data processing, and application layers. The architecture aims to enhance consistency, interoperability, and efficiency in IoT solution development.

Uploaded by

govindanm223
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views

test1 (1)

The document outlines the IoT reference model, detailing the domain model that captures the relationships between key concepts such as devices, sensors, actuators, and tags. It also describes the IoT reference architecture, which serves as a standardized blueprint for designing IoT systems, consisting of multiple layers including perception, network, data processing, and application layers. The architecture aims to enhance consistency, interoperability, and efficiency in IoT solution development.

Uploaded by

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

3.2.

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.

Model notation and semantics

Main concepts

The IoT is a support infrastructure for enabling objects and places in


the physical world to have a corresponding representation in the digital
world.
Physical vs. Virtual World
The Devices are physical artefacts with which the physical and virtual
worlds interact. Devices as mentioned before can also be Physical Entities for
certain types of applications, such as management applications when the
interesting entities of a system are the Devices themselves and not the
surrounding environment.
For the IoT Domain Model, three kinds of Device types are the
most important:

Sensors:
 These are simple or complex Devices that typically involve a
transducer that converts physical properties such as temperature into
electrical signals.
 These Devices include the necessary conversion of analog electrical
signals into digital signals, e.g. a voltage level to a 16-bit number,
processing for simple calculations, potential storage for intermediate
results, and potentially communication capabilities to transmit the
digital representation of the physical property as well receive
commands.
 A video camera can be another example of a complex sensor that
could detect and recognise people.
Actuators:
 These are also simple or complex Devices that involve a transducer
that converts electrical signals to a change in a physical property (e.g.
turn on a switch or move a motor).
 These Devices also include potential communication capabilities,
storage of intermediate commands, processing, and conversion of
digital signals to analog electrical signals.
Tags:
 Tags in general identify the Physical Entity that they are attached to. In
reality, tags can be Devices or Physical Entities but not both, as the
domain model shows.
 An example of a Tag as a Device is a Radio Frequency Identification
(RFID) tag, while a tag as a Physical Entity is a paper-printed
immutable barcode or Quick Response (QR) code.
 Either electronic Devices or a paper-printed entity tag contains a
unique identification that can be read by optical means (bar codes or
QR codes) or radio signals (RFID tags).
 The reader Device operating on a tag is typically a sensor, and
sometimes a sensor and an actuator combined in the case of writable
RFID tags.

3.3 IOT 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
IoT reference architectures typically consist of multiple layers that
work together to enable the functioning of an IoT system.
A commonly used layered structure includes the following:
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.

You might also like