4 layer Arch & Reference Arch of IoT.pdf

1
1
IOT-AN ARCHITECTURAL OVERVIEW
Unit Structure :
1.0 Objectives
1.1 Introduction
1.2 Building architecture
1.3 Main design principles and needed capabilities
1.4 An IoT architecture outline
1.5 Standards considerations
Summary
List of References
Unit End Exercises
1.0 OBJECTIVES
• To understand the working of an IoT system and components
• To get familiar with the building blocks and the architectural
functioning mechanism of IoT
• To acquaint with the design principles and considerations when
developing an IoT prototype
1.1 INTRODUCTION
What is Internet of Things? - the idea of connecting any gadget to the
Internet and other linked devices (as long as it has an on/off switch). The
Internet of Things (IoT) is a vast network of interconnected devices and
people, all of which gather and exchange information about their
environments and how they are used.
How does it function? Connected to an Internet of Things platform, which
combines data from many devices and applies analytics to share the most
useful information with applications created to answer particular needs, are
gadgets and objects having built-in sensors.
These robust IoT solutions can precisely identify which information is
helpful and which may be safely disregarded. This data can be used to
identify trends, generate recommendations, and identify potential issues
before they arise.
For instance, a company that makes cars might want to know which add-
ons, like leather seats or alloy wheels, are the most popular. Technology
based on the Internet of Things makes it feasible to:

2
Architecturing of IoT 1] Employ sensors to identify which showroom spaces are the busiest
and where clients remain the longest;
2] Analyze the sales data to determine which components are selling the
quickest;
3] Automatically match supply and sales data to ensure that in-demand
items don't run out of stock.
Making informed decisions about which components to stock up on based
on real-time information using the data collected by linked devices helps
save time and money.
The ability to improve procedures comes with the insight sophisticated
analytics offers. You can automate some jobs thanks to smart devices and
systems, especially if they are monotonous, time-consuming, repetitive, or
even hazardous.
1.2 BUILDING ARCHITECTURE
The IoT system's fundamental building parts include sensors, processors,
gateways, and applications. To create a useful IoT system, each of these
nodes must have unique properties.
Figure 1: Simplified block diagram of the basic building blocks of the IoT
1] Sensors
• They make up the IoT devices' front end. These are the system's
purported "Things." Their primary function is to gather data
from their environment (sensors) or to disseminate data to their
environment (actuators).
• To be easily recognized across a wide network, these must be
uniquely recognizable devices having a unique IP address.

3
IoT-An Architectural
Overview
• They must be active, which means they must be able to gather
data in real time. Depending on the user's demands, these can
either function independently (autonomous in nature) or be
modified to function independently (user-controlled).
• Gas sensors, water quality sensors, moisture sensors, and other
types of sensors are examples.
2] Processors
• The IoT system's brain is its processor. Their primary duty is to
process the information obtained by the sensors and separate the
useful information from the vast amounts of raw information
gathered. In a single sentence, we may claim that it offers the
data intelligence.
• Most processors operate in real-time and are simple for
programs to regulate. They are also in charge of encrypting and
decrypting data in order to secure the data.
• Because they have processors attached to them, embedded
hardware devices, microcontrollers, etc., are the ones that
process the data.
3] Gateways
• Gateways are in charge of sending the processed data to the
appropriate areas for proper utilization.
• In other words, we can say that a gateway facilitates the
communication of data between two points. It gives the data
network connectivity. Any IoT system must have network
connectivity in order to interact.
• Network gateways include LAN, WAN, PAN, etc.
4] Applications
• Another component of an IoT system is applications. Apps are
necessary for the effective use of all obtained data.
• These cloud-based applications are in charge of giving the
obtained data an effective meaning. Users control applications,
which are used to deliver certain services.
• Applications include things like security systems, industrial
control hubs, and apps for home automation.
The far right component in Figure 2 represents the application end of the
Internet of Things architecture.

4
Architecturing of IoT
Figure 2: Basic building blocks of IoT
The information obtained by the sensing node (end node) is processed
initially, and then via connectivity it reaches the embedded processing
nodes which can be any embedded hardware devices where it is processed
again. The data is transferred to the application node for proper application
of the acquired data as well as for data analysis via big data after passing
via the connectivity nodes once more. The remote cloud-based processing
can be any software at this point.
1.3 MAIN DESIGN PRINCIPLES AND NEEDED
CAPABILITIES
Designing IoT solutions presents whole new design difficulties for
designers that are primarily focused on building SW services, screen-based
user interfaces, or physical goods. IoT solutions are made up of several
components, including physical devices like sensors, actuators, and
interactive devices, the network that connects them, the data collected from
these devices and analyzed to produce a meaningful experience, and last but
not least, the actual physical environment in which the user interacts with
the solution. You must do a variety of design tasks, including service and
business design as well as industrial product design. The whole user
experience (UX) of the IoT system is influenced by all of these aspects, and
designing in this environment may seem fairly daunting. Following points
represents the design principles and considerations of IoT.
1] Focus on value
User research and service design are more important than ever in the
IoT age. Early adopters are eager to test out new technology, while
many others are hesitant to do so and cautious when using it because
they lack confidence in it. You must go deeply into user demands to
identify where a problem actually merits solving and what the
solution's true end user value is if you want your IoT solution to be
broadly embraced. Also, you need to be aware of any potential
obstacles to the adoption of your particular solution as well as new
technology in general. You also need to conduct study to choose your
feature set. You must carefully consider which features to include and
in what order, as things that might be valuable and highly relevant for

5
Overview
tech early adopters may not be appealing to the majority of consumers
and vice versa.
2] Take a holistic view
IoT solutions frequently include both physical and digital touchpoints,
as well as a variety of devices with various capabilities. The answer
might also be offered in conjunction with a variety of other service
providers. It is not sufficient to effectively design just one of the
touchpoints; rather, you must consider the entire system, the function
of each device and service, and the conceptual model of how the user
understands and perceives the system. To produce a memorable
experience, the entire system must operate without a hitch.
3] Put safety first
IoT solutions are used in the real world, so when something goes
wrong, the repercussions could be severe. Building trust should be
one of your major design drivers because consumers of IoT solutions
may have different comfort levels with new technology. You must
take care to ensure that every interaction with the product or service
strengthens rather than undermines the trust because it is established
gradually and lost easily. What does it actually mean? Understanding
potential mistake scenarios connected to the use environment,
hardware, software, and network, as well as user interactions, is the
first step in trying to prevent them. The user must be properly
informed about mistake circumstances and assisted in recovering if
they continue to occur. Second, it involves making data security and
privacy important design components. Users must have the
confidence that their personal information is secure, that their homes,
places of employment, and ordinary items cannot be compromised,
and that their loved ones are not in danger. Thirdly, quality assurance
is essential, and it should concentrate on evaluating the entire system
in a real-world setting rather than just the SW.
4] Consider the text
At the nexus of the physical and digital worlds are IoT solutions.
Digital interface commands may have real-world consequences, but
unlike digital commands, real-world consequences often cannot be
reversed. Many unanticipated events can occur in the real world, but
users still need to feel secure and in control. Several kinds of criteria
for the design are also imposed by the context. Depending on the
physical environment, the objective can be to reduce user distraction
or, for example, to design equipment that can withstand changing
weather conditions. IoT solutions are often multi-user systems in
homes, offices, and public spaces, making them less personal than,
say, screen-based solutions used in smartphones. This also considers
the social context in which the solution is utilized and its design needs.

6
Architecturing of IoT 5] Build a strong band
No matter how carefully you design things and try to establish trust,
something unexpected will happen at some point and your solution is
going to fail in some way because of the real-world environment of
IoT solutions. It is crucial in times like this that you have developed
a powerful brand that connects with them on an authentic level. They
will be more understanding of system flaws and continue to use your
solution if they feel a connection to your brand. Trust should be a
crucial component of your brand and one of its basic brand principles.
This is something you must keep in mind while you create your brand.
This core principle should be mirrored in all other aspects of the
brand, such as color scheme, writing style, images, etc.
6] Prototype early and often
Normally, HW and SW have lifespans that are somewhat dissimilar,
but since a successful IoT solution requires both HW and SW
components, the lifespans should be coordinated. IoT solutions are
also difficult to upgrade because once a connected object is installed,
it is difficult to replace it with a newer model, especially if the user
must pay for the upgrade. Moreover, the connected object's software
may be difficult to update for security and privacy concerns. It's
essential to get the solution right from the start of implementation due
to these factors and to prevent expensive hardware iterations. From a
design standpoint, this means that early project stages require quick
prototyping and iteration of both the HW and the entire solution. We
need new, inventive approaches to fake the solution and prototype it.
7] Use data responsibly
IoT systems can potentially produce enormous amounts of data. The
goal is to discover the data points required to make the solution work
and be valuable, not to collect as much data as you can. The designer
must comprehend the potential of data science and how to interpret
the data because the volume of data may be enormous. Data science
offers several chances to lower user friction, i.e., to consume less time,
energy, and attention, or to experience less stress. It can be used to
understand intent from partial or insufficient input, to automate
repetitive context-dependent judgements, to filter out noise from
relevant signals, and more. Designing successful IoT services requires
a thorough understanding of the data that is available and how it can
be used to benefit the user.
1.4 AN IOT ARCHITECTURE OUTLINE
The complex arrangement of elements that make up IoT networking
systems, including sensors, actuators, cloud services, protocols, and layers,
is referred to as IoT architecture. It is typically separated into layers that let
administrators assess, keep an eye on, and uphold the integrity of the
system. Data moves from connected devices to sensors, through a network,

7
Overview
to the cloud for processing, analysis, and storage in a four-step process
known as the IoT architecture. The Internet of Things is poised to expand
much further with time, offering users fresh and enhanced experiences.
Different layers of IoT architecture
IoT technology has been more well-liked recently and has a wide range of
uses. IoT apps function in accordance with how they were created
depending on the many application domains. There isn't a set standard
defined architecture of work, nevertheless, that is rigidly followed
everywhere. Depending on the particular business job at hand, different
architectural layers and levels of complexity are used. The most common
and standard architecture is a four-layer one.
As you can see from the above image, there are four layers present i.e., the
Perception Layer, Network Layer, Processing Layer, and Application
Layer.
1] Perception/ Sensing layer
Any IoT system's first layer is made up of "things" or endpoint devices
that act as a link between the real world and the digital one. The

8
Architecturing of IoT physical layer, which contains sensors and actuators capable of
gathering, accepting, and processing data across a network, is referred
to as perception. Wireless or wired connections can be used to connect
sensors and actuators. The components' range and locations are not
constrained by the design.
2] Network layer
An overview of the data flow throughout the programme is given by
the network layers. Data Acquisition Systems (DAS) and
Internet/Network gateways are present in this tier. Data aggregation
and conversion tasks are carried out by a DAS (collecting and
aggregating data from sensors, then converting analogue data to
digital data, etc.). Data gathered by the sensor devices must be
transmitted and processed. The network layer performs that function.
It enables connections and communication between these gadgets and
other servers, smart gadgets, and network gadgets. Also, it manages
each device's data transmission.
3] Processing layer
The IoT ecosystem's processing layer functions as its brain. Before
being transported to the data center, data is typically evaluated, pre-
processed, and stored here. It is then retrieved by software
applications that handle the data and prepare future actions. This is
where edge analytics or edge IT comes into play.
4] Application layer
The application layer, which provides the user with application-
specific services, is where user interaction occurs. A dashboard that
displays the status of the devices in a system or a smart home
application where users may turn on a coffee maker by touching a
button in an app are two examples. The Internet of Things can be used
in a variety of applications, including smart homes, smart cities, and
smart health.
Stages of IoT solutions architecture
How can organizations take advantage of the IoT layers after learning about
them and how can they increase the value of IoT? Although linked devices
and protocols are referred to as part of the Internet of Things (IoT), the data
produced by these devices is actually siloed, fragmented, and isolated. As a
result, these fragmented insights do not alone offer sufficient data to support
an IoT strategy that entails a large resource investment. Enterprises must
leverage device and system synergies and allow devices to freely interact in
order to benefit from IoT. Make sure your infrastructure is compatible with
the IoT architecture. The various phases of IoT architecture implementation
in businesses are as follows:

9
Overview
• Connected objects/devices
The physical layer within the environment must be built as a first step
towards IoT architecture. The Internet of Things would not exist
without "smart" or linked objects. On the perception layer, these are
frequently wireless sensors or actuators.
Sensors gather and process environmental data to make it useful for
additional research. The change that the sensors register is measured
by actuators. Wired or wireless connections can be made between
sensors and actuators to accomplish sensing and actuation. Sensors
and actuators can be connected using Personal Area Networks (PANs)
and Local Area Networks (LANs).
• Internet gateway
After properly completing step one, the next task is to set up an
internet gateway. We need a way to convert analogue data that is
being collected by the sensors and actuators into digital data so that
we can process it. The internet gateway is used to do this activity.
Before being transferred to the cloud, raw data from the devices will
be received at the internet gateway stage and pre-processed.
Analog data can be transformed into digital data using data
acquisition systems. It establishes connections with the sensors and
actuators, collects all the data, and transforms it into digital form so
that the internet gateway may send it across the network. It is in charge
of conversion and data aggregation. To improve performance and
effectiveness, we can also add extra features like analytics and
security.
• Edge IT systems
Pre-processing and improved data analytics are part of the third stage
of an IoT architecture. Edge IT systems are essential in easing the
burden on the main IT infrastructure due to the sizeable volume of
data collected by IoT systems and the ensuing bandwidth
requirements. Machine learning and visualization techniques are used
by edge IT systems to derive insights from gathered data. While
visualization tools make the data more comprehensible, machine
learning algorithms offer insights into the data.
The system's speed, as well as the LAN or routers' bandwidth, would
suffer if data is sent directly to the server or data center. Analog data
is produced very quickly and takes up a lot of storage space. As a

10
Architecturing of IoT result, it is always advised to convert data to digital format. Only the
necessary data is processed and communicated to data centers and
servers because the majority of the data acquired by sensors and
actuators is not valuable to the enterprise.
• Data centers and cloud storage
The data is delivered to the data centers and servers for final analysis
and reporting once it has been appropriately preprocessed, examined,
and any gaps have been filled. The management services area includes
data centers and cloud services, which often handle data using
analytics, device management, and security controls. Data can also be
transferred to end-user applications like healthcare, retail,
environment, emergency, energy, etc. thanks to the cloud.
The data might be transmitted to data centers or cloud-based servers for
final processing after analysis. Hardware expenses can be reduced by using
the cloud platform, but data security is still a worry. Physical servers and
data centers are safer, but they are also more expensive.
1.5 STANDARDS CONSIDERATIONS
Manufacturers who want to maintain their competitiveness in their sector
must connect their devices to the Internet of Things (IoT). IoT capabilities
expand the options available to users. Additionally, it enables the
manufacturer to maintain contact with their clientele while they explore new
product use cases and applications that present them with opportunities for
new revenue streams. There are ten considerations to make while creating
your first Internet of Things device:
1] Cost
IoT or "smart" products benefit producers and customers equally,
although they are more expensive. Consider networking in your next
product because both Ethernet and wireless technology have dropped
below $10.
2] Network
The network technology you choose for your IoT product has
concerns with gateways and routers as well as distance. Ethernet/Wi-
Fi is required if you need to connect to the Internet; ZigBee, Z-Wave,
and Bluetooth are available if you are self-contained in a room or
building. Remember that the FCC must approve all wireless
technology.
3] Features
Businesses may now add features to their products that were either
impossible or unimaginable without an IoT-connected product. For
updates, maintenance, and new revenue opportunities, you can obtain
direct access to the consumer with the help of these capabilities.

11
Overview
4] User interface
It matters how a user interacts with a product. On the product, are you
intending to use buttons, LEDs, or a display? What web and app
interfaces will you offer as well?
5] Power
The choice of a power source should be among the first. All design
choices must take power conservation into account if the item will be
battery-powered. Many networking technologies won't operate well
on batteries. Power selection is also influenced by communication
frequency.
6] Size
Size does matter. Think about how the size of the device will be
affected by the network. Certain networks' requirements for
connectors and antennae will increase the size.
7] Antenna
Whether inside or exterior to the product, an antenna is used by all
wireless networks. If the enclosure is plastic, the antenna is
increasingly being moved inside. External antennas would be
necessary for all metal enclosures.
8] Cloud
Products have a user interface to the product and the data thanks to
cloud applications. There are public clouds and private clouds. Most
clouds have a common API that you may use to create your
application.
9] Interoperability
Is communication between your product and those of other vendors
required? If so, you must use a common set of protocols, like Apple's
HomeKit, to interact with other devices.
10] Security
You must incorporate as many layers of security as you can because
security is starting to become a serious concern. The bare minimum
is SSL and a password.
SUMMARY
Rapid technological development in the modern era has connected people
and things worldwide. IoT solutions have ingrained themselves into our
daily lives in recent years. For instance, you can instantly get a response or
results by simply speaking or tapping the screen of your smartphone.
Regardless of how IoT architecture varies from project to project, managing

12
Architecturing of IoT vast amounts of data will always be a crucial component of every IoT
project.
Enterprises can automate business operations by employing technology like
cloud platforms, embedded devices with sensors and actuators, and internet-
based communication. The insights drawn from IoT data sets will become
a useful source of information for businesses thanks to big data analytics.
We may anticipate the deployment of IoT systems in an increasing number
of consumer, commercial, industrial, and infrastructural applications in the
near future. In terms of technology and device connectivity, the upcoming
years will see the emergence of a whole new ecosystem.
LIST OF REFERENCES
1] From Machine-to-Machine to the Internet of Things: Introduction to
a New Age of Intelligence, Jan Holler, Vlasios Tsiatsis, Catherine
Mulligan, Stefan Avesand, Stamatis Karnouskos, David Boyle,1st
Edition, Academic Press, 2014.
2] Learning Internet of Things, Peter Waher, PACKT publishing,
BIRMINGHAM – MUMBAI,2015.
3] Building the Internet of Things with IPv6 and MIPv6: The Evolving
World of M2M. Communications, Daniel Minoli, Wiley
Publications,2013.
4] Internet of Things (A Hands-onApproach), Vijay Madisetti and
ArshdeepBahga,1st Edition, VPT, 2014.
5] http://www.cse.wustl.edu/~jain/cse570-15/ftp/iot_prot/index.html.
UNIT END EXERCISES
1] Define IoT and its functioning.
2] Write a note on building blocks of IoT architecture.
3] What are the main design principles and needed capabilities of an
IoT system?
4] Describe an IoT architecture
5] What are the standards considerations of an IoT system?


13
2
IOT ARCHITECTURE-STATE OF THE ART
Unit Structure :
2.0 Objectives
2.1 Introduction: State of the art
2.2 Reference Model and architecture
2.3 Functional View
2.4 Information View
2.5 Deployment and Operational View
Summary
List of References
Unit End Exercises
2.0 OBJECTIVES
• To understand the state of art of an IoT system
• To get familiar with the IoT reference model architectural layers
• To acquaint with the different views associated with an IoT system
2.1 INTRODUCTION: STATE OF THE ART
The Internet of Things (IoT) can be viewed as a dynamic, worldwide
networked infrastructure that controls autonomous items in a highly
intelligent manner. As a result, new apps and services that can enhance
human lives can be developed by connecting IoT devices that share
information. At the beginning, Kevin Ashton, the founder of the MIT Auto
Identification Center, originally suggested the idea of the IoT in 1999. The
Internet of Things has the potential to revolutionize the world, much like
the Internet did, according to Ashton. possibly even more so Eventually, the
International Telecommunication Union (ITU) formally introduced the
Internet of Things in 2005. There are numerous definitions of the IoT
offered by numerous organizations and researchers.
However, the ITU's 2012 definition is the one that is most frequently used.
According to what was said, there would be "a global infrastructure for the
information society, enabling improved services by connecting (physical
and virtual) things based on, existing and developing, interoperable
information and communication technologies." Moreover, Guillemin and
Friess in have offered one of the most straightforward formulations that
accurately sum up the Internet of Things. According to the statement, "The
Internet of Things enables people and things to be connected Whenever,
Anywhere, with Anything and Anybody, ideally via Any Path/Network and
Any Service." Many academics have offered many definitions of the
Internet of Things (IoT) system from various angles, but the most crucial

14
Architecturing of IoT point on which most experts have agreed is that the IoT was developed to
build a better world for all people.
Figure 1. The IoT can connect anything in anywhere using any path
2.2 REFERENCE MODEL AND ARCHITECTURE
In October 2014, the IoT reference model was announced by the IoT World
Forum (IWF) architecture committee. The industry may speed IoT
deployments with the support of this model, which serves as a common
framework. This reference model aims to promote and consolidate IoT
deployment model development and collaboration. The IoT's seven-level
architecture model is depicted in Figure 2. This reference model has seven
layers, with each layer offering more details to help build a standard
nomenclature. The initial step in enabling suppliers to develop IoT solutions
that are compatible and interoperable is provided by this document, which
also defines where particular types of processing are optimized across
various layers of the system. In addition, this model made the IoT as a real
and approachable system, instead of simply conceptual.
Figure 2: The IoT World Forum Reference Model

15
IoT Architecture-
State of the Art
The physical layer of the Open System Interconnection (OSI) model of the
network architecture is analogous to Layer 1. It is made up of mechanical
components and object-controlling controllers. These things stand in for the
Internet of Things and encompass a variety of information-sending and -
receiving gadgets. For instance, sensors that gather various types of data
about the surroundings.
Layer 2 deals with connectivity and communication. This layer consists of
the hardware components used to build local and wide-area networks and
enable Internet connectivity, such as routers, switches, gateways, and
firewalls. Moreover, this layer facilitates communication between devices
and with application platforms like PCs, remote controls, and cellphones.
The edge computing layer's function is to transform network data flows into
data that can be stored and processed at a higher level. Processing
components at this layer may handle large amounts of data and carry out
data transformation activities, which leads to the storage of much smaller
amounts of data.
The data buildup occurs at layer 4. This layer is responsible for storing data
from various IoT devices. The edge computing layer, which takes in
enormous amounts of data and stores it in storage so that higher levels can
access it, filters and processes this data. The edge computing layer may be
supplying data for storage in a variety of forms and from heterogeneous
processors. Although the data abstraction layer gathers and organizes stored
data so that programs can access it in a more manageable and effective
manner.
Information interpretation takes place at layer 6, which is the application
layer. Numerous applications that use IoT input data or manage IoT devices
fall under this layer. The collaboration and processes layer identifies people
who can interact and work together to improve the utility of the IoT system.
Several applications are used on this layer to share data and manage
information via the Internet. Table 1 lists the layers of the IoT architecture
along with what each layer does.
Table 1. A summary of IoT architecture layers with its functions

16
Architecturing of IoT 2.3 FUNCTIONAL VIEW
In order to address the concerns of concrete IoT architecture and
stakeholders, the reference architecture is presented as a set of architectural
views mainly the functional view; information view; deployment and
operational view.
The functional view provides the description of what the system does, and
its main functions.
Figure 3: The IoT functional view
Device and Application functional group
• Device FG contains the Sensing, Actuation, Tag, Processing, Storage
FCs, or simply components.
• These components represent the resources of the device attached to
the Physical Entities of interest. The Application FG contains either
standalone applications (e.g. for iOS, Android, Windows phone), or
Business Applications that connect the IoT system to an Enterprise
system
Communication functional group
• The Communication FG contains the End-to-End Communication,
Network Communication, and Hop by-Hop communication
components
• The Hop-by-Hop Communication is applicable in the case that
devices are equipped with mesh radio networking technologies such
as IEEE 802.15.4 for which messages have to traverse the mesh from
node to-node (hop-by-hop) until they reach a gateway node which
forwards the message (if needed) further to the Internet

17
IoT Architecture-
State of the Art
Network FC
• The Network FC is responsible for message routing & forwarding and
the necessary translations of various identifiers and addresses.
• The translations can be (a) between network layer identifiers to MAC
and/or physical network identifiers, (b) between high-level human
readable host/node identifiers to network layer addresses (e.g. Fully
Qualified Domain Names (FQDN) to IP addresses, a function
implemented by a Domain Name System (DNS) server), (c)
translation between node/service identifiers and network locators in
case the higher layers above the networking layer use node or service
identifiers that are decoupled from the node addresses in the network
(e.g. Host Identity Protocol)
End to End Communication
• The End-to-End Communication FC is responsible for end-to-end
transport of application layer messages through diverse network and
MAC/PHY layers.
• In turn, this means that it may be responsible for end to-end
retransmissions of missing frames depending on the configuration of
the FC.
• For example, if the End-to-End Communication FC is mapped in an
actual system to a component implementing the Transmission Control
Protocol (TCP) protocol, reliable transfer of frames dictates the
retransmission of missing frames
IoT Service functional group- The IoT Service FC
• IoT Service functional group-The IoT Service FG consists of two
FCs: The IoT Service FC and the IoT Service Resolution FC
• The IoT Service FC is a collection of service implementations, which
interface the related and associated Resources.
• For a Sensor type of a Resource, the IoT Service FC includes Services
that receive requests from a User and returns the Sensor Resource
value in synchronous or asynchronous (e.g. subscription/notification)
fashion.
IoT Service functional group
• The IoT Service Resolution FC-The IoT Service Resolution FC
contains the necessary functions to realize a directory of IoT Services
that allows dynamic management of IoT Service descriptions and
discovery/lookup/resolution of IoT Services by other Active Digital
Artifacts.
• Dynamic management includes methods such as
creation/update/deletion (CUD) of Service description, and can be
invoked by both the IoT Services themselves, or functions from the
Management FG.

18
Architecturing of IoT • The discovery/lookup and resolution functions allow other Services
or Active Digital Artifacts to locate IoT Services by providing
different types of information to the IoT Service Resolution FC.
Virtual Entity functional group
• The Virtual Entity FG contains functions that support the interactions
between Users and Physical Things through Virtual Entity services.
• An example of such an interaction is the query to an IoT system of
the form, “What is the temperature in the conference room Titan?”
• The Virtual Entity is the conference room “Titan,” and the conference
room attribute of interest is “temperature.”
• The Virtual Entity Service FC enables the interaction between Users
and Virtual Entities by means of reading and writing the Virtual Entity
attributes (simple or complex), which can be read or written. The
Virtual Entity Registry FC maintains the Virtual Entities of interest
for the specific IoT system and their associations. The component
offers services such as creating/reading/updating/deleting Virtual
Entity descriptions and associations.
Virtual Entity resolution functional group
• The Virtual Entity Resolution FC maintains the associations between
Virtual Entities and IoT Services, and offers services such as
creating/reading/updating/deleting associations as well as lookup and
discovery of associations.
• The Virtual Entity and IoT Service Monitoring FC includes: (a)
functionality to assert static Virtual Entity - IoT Service associations,
(b) functionality to discover new associations based on existing
associations or Virtual Entity attributes such as location or proximity,
and (c) continuous monitoring of the dynamic associations between
Virtual Entities and IoT Services and updates of their status in case
existing associations are not valid any more.
IoT process management functional group
• The IoT Process Management FG aims at supporting the integration
of business processes with IoT-related services.
• It consists of two FCs: i] The Process Modeling FC provides that right
tools for modeling a business process that utilizes IoT-related
services.
ii] The Process Execution FC contains the execution environment of the
process models created by the Process Modelling FC and executes the
created processes by utilizing the Service Organization FG in order to
resolve high-level application requirements to specific IoT services.

19
IoT Architecture-
State of the Art
Service Organization functional group
• The Service Organization FG acts as a coordinator between different
Services offered by the system. It consists of the following FCs: The
Service Composition FC manages the descriptions and execution
environment of complex services consisting of simpler dependent
services. An example of a complex composed service is a service
offering the average of the values coming from a number of simple
Sensor Services.
• The Service Orchestration FC resolves the requests coming from IoT
Process Execution FC or User into the concrete IoT services that fulfil
the requirements.
• The Service Choreography FC is a broker for facilitating
communication among Services using the Publish/Subscribe pattern.
Security functional group
• The Security FG contains the necessary functions for ensuring the
security and privacy of an IoT system.
• It consists of the following FCs:
• The Identity Management FC manages the different identities of the
involved Services or Users in an IoT system in order to achieve
anonymity.
• The Authentication FC verifies the identity of a User and creates an
assertion upon successful verification.
• It also verifies the validity of a given assertion.
• The Authorization FC manages and enforces access control policies.
It provides services to manage policies (CUD), as well as taking
decisions and enforcing them regarding access rights of restricted
resources. The term “resource” here is used as a representation of any
item in an IoT system that needs a restricted access.
• Such an item can be a database entry (Passive Digital Artifact), a
Service interface, a Virtual Entity attribute (simple or complex), a
Resource/Service/Virtual Entity description, etc.
• The Key Exchange & Management is used for setting up the
necessary security keys between two communicating entities in an
IoT system. This involves a secure key distribution function between
communicating entities.
• The Trust & Reputation FC manages reputation scores of different
interacting entities in an IoT system and calculates the service trust
levels.

20
Architecturing of IoT Management functional group
• The Management FG contains system-wide management functions
that may use individual FC management interfaces. It is not
responsible for the management of each component, rather for the
management of the system as a whole. It consists of the following
FCs:
• The Configuration FC maintains the configuration of the FCs and the
Devices in an IoT system (a subset of the ones included in the
Functional View).
• The component collects the current configuration of all the FCs and
devices, stores it in a historical database, and compares current and
historical configurations.
• The component can also set the system-wide configuration (e.g. upon
initialization), which in turn translates to configuration changes to
individual FCs and devices.
• The Fault FC detects, logs, isolates, and corrects system-wide faults
if possible. This means that individual component fault reporting
triggers fault diagnosis and fault recovery procedures in the Fault FC.
• The Member FC manages membership information about the relevant
entities in an IoT system. Example relevant entities are the FGs, FCs,
Services, Resources, Devices, Users, and Applications. Membership
information is typically stored in a database along with other useful
information such as capabilities, ownership, and access rules & rights,
which are used by the Identity Management and Authorization FCs.
• The State FC is similar to the Configuration FC, and collects and logs
state information from the current FCs, which can be used for fault
diagnosis, performance analysis and prediction, as well as billing
purposes. This component can also set the state of the other FCs based
on system-wise state information.
• The Reporting FC is responsible for producing compressed reports
about the system state based on input from FCs.
2.4 INFORMATION VIEW
Information view provides description of the data and information that the
system handles.
• 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
lifecycle and flow (how information is created, processed, and
deleted), and the information handling components.
• The pieces of information handled by an IoT system it can be

21
IoT Architecture-
State of the Art
• Virtual Entity context information, i.e. the attributes (simple or
complex) as represented by parts of the IoT Information model.
• IoT Service output itself is another important part of information
generated by an IoT system. For example, this is the information
generated by interrogating a Sensor or a Tag Service
• Virtual Entity descriptions in general, which contain not only the
attributes coming from IoT Devices (e.g. ownership information).
• Associations between Virtual Entities and related IoT Services
2.5 DEPLOYMENT AND OPERATIONAL VIEW
• Deployment and Operational View provides description of the main
real world components of the system such as devices, network routers,
servers, etc.
• Devices that form networks in the M2M Area Network domain must
be selected, or designed, with certain functionality in mind.
• At a minimum, they must have an energy source (e.g. batteries,
increasingly EH), computational capability (e.g. an MCU),
appropriate communications interface (e.g. a Radio Frequency
Integrated Circuit (RFIC) and front end RF circuitry), memory
(program and data), and sensing (and/or actuation) capability.
• These must be integrated in such a way that the functional
requirements of the desired application can be satisfied
SUMMARY
It is difficult to predict the many applications of IoT
once it has reached the stage of ubiquitous expansion.
- “The Technical Foundations of IoT”, Adryan, Obermaier, and Fremantle
The Internet of Things will succeed when it blends into the background and
we stop noticing how new it is to have something connected to the Internet
that interacts with other systems, services, and gadgets. While some goods
are beginning to accomplish this, others still have a way to go. The
development of serverless computing platforms as well as the concepts and
design patterns of reactive systems will be crucial to the success of the IoT.
The Internet of Things (IoT) is thought to be the next step in the
development of the Internet. To promote information sharing, it has the
ability to connect and communicate with practically all real-world objects
over the Internet. The Internet of Things (IoT) can gather, analyze, and
deploy a significant quantity of data with the use of sensors. This data will
then be transformed into knowledge and information that can be utilized to
develop new applications and services that can enhance our quality of life.
The IoT system has been reviewed in this essay. The IoT's cutting-edge

22
Architecturing of IoT layered architecture is described. In addition, IoT essential features and
different communication technologies are presented.
LIST OF REFERENCES
1] From Machine-to-Machine to the Internet of Things: Introduction to
a New Age of Intelligence, Jan Holler, Vlasios Tsiatsis, Catherine
Mulligan, Stefan Avesand, Stamatis Karnouskos, David Boyle,1st
Edition, Academic Press, 2014.
2] Learning Internet of Things, Peter Waher, PACKT publishing,
BIRMINGHAM – MUMBAI,2015.
3] Building the Internet of Things with IPv6 and MIPv6: The Evolving
World of M2M. Communications, Daniel Minoli, Wiley
Publications,2013.
4] Internet of Things (A Hands-onApproach), Vijay Madisetti and
ArshdeepBahga,1st Edition, VPT, 2014.
5] http://www.cse.wustl.edu/~jain/cse570-15/ftp/iot_prot/index.html.
UNIT END EXERCISES
1] Discuss the state of the art of an IoT architecture.
2] Explain the reference Model and architecture.
3] Discuss the functional view of an IoT system.
4] Explain the Information view of an IoT system.
5] Write a note on Deployment and Operational view of an IoT system.


4 layer Arch & Reference Arch of IoT.pdf

More Related Content

Similar to 4 layer Arch & Reference Arch of IoT.pdf (20)

More from sendilkumar66 (6)

Recently uploaded (20)

4 layer Arch & Reference Arch of IoT.pdf