IOT Reference Model

••A reference model describes the domain using a number of sub-models

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

UML Class diagram main modelling concepts

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 worldsinteractFor the IoT
Domain Model, three kinds of Device types are the most important:
1)Sensors: to covert physical properties to electrical signals.
2)Actuators: to convert electrical signals to physical properties.
3)Tags: to uniquely identify any physical entity.

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 Modelling Language
(UML) diagrams.
Communication model
Safety
TheIoT Reference Model can only provide IoT-related guidelines for ensuring a safe system to
the extent possible and controllable by a system designer.
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.
----X---
Explain IoT reference architecture’s deployment and operational view.
 Deployment and the operational view are very important in addressing how the actual
system can be realized by selecting technologies and making them communicate and
operate in a comprehensive way.
 This view depends upon actual use case and requirements.
 Let’s take an example of the parking lot system.

 As we can see in the figure, there are two sensor nodes #1 and #2, each of which is
connected to eight car presence sensors.
 They are also connected to the payment stations through wireless or wired
communication.
 The payment station acts both as a user interface for the device to pay and get a payment
receipt as well as a communication gateway that connects the two sensor nodes and
payment interface physical devices with the internet through WAN.
  The occupation sign also acts as a communication gateway for the actuator node, and we
assume that because of the deployment, a direct connection to the payment station is not
feasible.
 The physical gateway devices connect through WAN to the internet and towards a data
center where the parking lot management system software is hosted as one of the virtual
machines on a platform as service configurations.
 The two main applications connected to this management system are human user mobile
phone applications and parking operation center applications.
---X---

Explain IoT architecture outline with a diagram.

 The assets of interest are the real world objects and entities that are subject to being
monitored and controlled, as well as having digital representation and identities.
 The resource layer provides different capabilities such as sensing, actuation, and
embedded identities. Sensors and actuators in the devices that may be smartphones, smart
meters, other sensors and actuators deliver these functions.
  The purpose of communication layer is to provide the means for connectivity between the
resources on one end and the different computing instances that host and execute the
service support and application logic on the other hand. It can use LAN or WAN.
 Service support layer is generally executed in data centers or server farms inside the
organizations or in a cloud environment. Few examples include software upgrades,
remote diagnostics and recovery services.
 The data information layer provides a more abstract set of functions as its main purpose
is to capture knowledge and provide advanced control logic support.
 The application layer provides specific IoT applications. There is an open-ended array of
applications and typical examples include smart metering in the smart grid.
 In the business layer, the integration of the IoT application and business processes occur.
It focuses on supporting the core business or operations of any enterprise that is interested
in IoT applications.
 Apart from the functional layers, there are three functional groups across different layers:
1)Management:
 As the name implies, the management group deals with the management of system
solution related to maintenance, administration, operation, and provisioning. This
includes management of devices, communication networks and general IT infrastructure
in the organization.
2)Security:
 Security is the protection of the system, its information, and services from the external
threats and any other harm. Authorization, authentication, identity management, and trust
are main capabilities.
3)Data and services:

 Data and service processing can, from a topological perspective, be done in a very
distributed fashion and at different levels of complexity.
-----X-----
Discuss the functional view of IoT.
Functional view describes system’s runtime functional components, their responsibilities, default
functions, interfaces and primary interactions.
Device functional group
The Device FG contains all the possible functionality hosted by the physical Devices. 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.(lan,wan,wifi,zigbee)
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,
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. 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. 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.
Application functional group
The Application FG is just a placeholder that represents all the needed logic for creating an IoT
application.
-----X----
Explain ETSI M2M High-Level Architecture.
  A high-level architecture of an M2M system consists of a device and gateway domain
and a network domain.
 The device and gateway domain consist the following elements:
1)M2M device runs M2M device operations using M2M device service capabilities
layer(DSCL).
2)M2M gateway runs M2M gateway applications using M2M gateway service capabilities
layer(GSCL).
3)M2M area network provides connectivity based on personal or local area network technologies
between M2M devices and M2M gateways.
The network domain contains the following elements:
1)M2M Access network:
 It allows M2M devices and M2M gateways to communicate with the core network.
 It uses any one of the solutions such as Satellite, Digital Subscriber Line(DSL), WiFi,
WiMax etc. that can be optimized for M2M communication when needed.
2)M2M Core network:
  This network enables interconnection with other networks, provides IP connectivity or
other connectivity options, service and control functions and roaming.
3)M2M Network Capabilities Layer:
 It provides M2M functions which are shared by different M2M applications.
4)M2M Applications:
 They run the service logic and use M2M service capabilities via open interfaces.
5)M2M Network Management Function:
 They consist of all the functions required to manage access and core networks.
6)M2M Management Function:
M2M management functions consist of all the functions used to facilitate the bootstrapping of
permanent M2M service layer security credentials required to manage M2M service capabilities
in the network domain.
----X----
Explain IoT domain model notations and semantics.
 Unified Modelling Language(UML) is used to show relationships between the main
concepts of the IoT domain model.
 Each class in UML is a set of objects that have similar structure, behavior, and properties.
 Each class contains the name and a set of attributes.
 The interaction with the physical world is the key for IoT and it needs to be captured in
the domain model.
 The domain model represents the main concepts of IoT and the relationships between
them.
 As shown in the diagram, a physical entity can contain another physical entity. For
example, a building contains several floors and each floor has several rooms.
 The physical entity is represented in the digital world as the virtual entity.
 A virtual entity can be a database entry, an image or avatar or any other digital unit.
 The relations between the services and entities are represented using associations.
 These associations can be static or dynamic.
  Three types of devices are very important in IoT domain model:
1)Sensors: to covert physical properties to electrical signals.
2)Actuators: to convert electrical signals to physical properties.
3)Tags: to uniquely identify any physical entity.
---X---
Information Model or Informational View
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 Modelling Language
(UML) diagrams.
High-level IoT Information Model
Relationship between core concepts of IoT Domain Model and 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.