CSE88D
IOT State of Arts
UNIT III-Part III
Deployment and Operation View
• Connected and smart objects in the IoT can be realized in
many different ways and can communicate using many
different technologies.
•
• Moreover, different systems may need to communicate the
one to each other in a compliant way.
• Hence the Deployment and Operation view is very important
to address how actual system can be realized by selecting
technologies and making them communicate and operate in a
comprehensive way.
• The Deployment and Operation view aims at providing users
of the IoT Reference Model with a set of guidelines to drive
them through the different design choices that they have to
face while designing the actual implementation of their
services.
• Starting from the IoT Domain Model, we found three main
element groups : Devices, Resources, and Services highlighted
in red, blue and yellow, respectively.
• Each of them poses a different deployment problem, which, in
turn, reflects on the operational capabilities of the system.
The viewpoints used in the Deployment and Operation
view are the following:
• The IoT Domain Model diagram is used as a guideline to
describe the specific application domain.
• The Functional Model is used as a reference to the system
definition; in particular it defines Functional Groups such as
IoT Services and Connectivity groups which are fundamental
for a correct definition of the system.
• Network connectivity diagrams can be used to plan the
connectivity topology to enable the desired networking
capability of the target application; at the deployment level,
the connectivity diagram will be used to define the hierarchies
and the type of the sub-networks composing the complete
system network;
• Device Descriptions (such as datasheets and users manuals)
can be used to map actual hardware on the service and
resource requirements of the target system.
• First of all, devices in IoT systems include the whole spectrum
of technologies ranging from the simplest of the
radiofrequency tags to the most complex servers.
• The unifying characteristics are mainly two-fold: on the one
hand, every device is connected with one another forming a
part of the IoT; and, on the other hand, every device is
“smart”, even though with different degree of complexity, in
that it provides computational capabilities.
• These two characteristics are the subject of the first choices a
system designer has to make.
• The following list provides a few of the typical technologies
that can be found in IoT systems: Sensor & Actuator
Networks;
• RFIDs and smart tags;
• WiFi or other unconstrained technologies;
• Cellular networks.
• As a consequence of the coexistence of different communication
technologies in the same system, the second choice the system designer
must account for is related to communication protocols.
• In addition, in order to better understand the application, it is important to
describe it within the Functional View.
• We identified the following possibilities:
• 1.IoT protocol suite: This is the main direction supported by this
project and providing the best solution for interoperability;
•
• 2.Ad-hoc proprietary solutions: Whenever the performance
requirements of the target application are more important than the
system versatility, ad hoc solutions may be the only way to go;
•
• 3.Other standards: Depending on the target application domain,
regulations may exist forcing the system designer to adopt
standards, different from those suggested by the IoT protocol suite,
that solved a given past issue and have been maintained for
continuity.
• After having selected the devices and their
communication methods, the system designer
has to account for services and resources, as
defined in the IoT Service FG section.
• 1. On smart objects: This choice applies to simple resource
definitions and lightweight services, such as web-services that may
be realized in few tens or hundreds of bytes;
•
• 2.On gateways: Whenever the target devices are not powerful
enough to run the needed software themselves, gateways or other
more capable devices have to be deployed to assist the less capable
ones;
•
• 3.In the cloud: Software can be also deployed on web-farms. This
solution improves the availability of the services, but may decrease
the performance in terms of latency and throughput.
Trust, Security and Privacy
• Trust
• Trust in the IoT environment is a fundamental yet difficult to
obtain quality.
• As the security one, this quality is highly dependent on the
computation and communication performance of the system.
•
• In the frame of IoT moreover, M2M subjects must be enabled
to evaluate this quality in order to obtain autonomous
systems
• Security
• Security is an essential quality of an IoT system and it is tightly
related to specific security features which are often a basic
prerequisite for enabling Trust and Privacy qualities in a
system
• Privacy
• There are usually different concepts conveyed with the term
privacy, some being more from the technical side and some
more from the legal perspective, without forgetting ethical
aspects
