29-07-2023

Architecture Reference Model

Module - 2

IoT design methodology

• Domain Model
• Information Model
• Functional Model
• Communication Model
• Trust, Security and Privacy Model

1
 29-07-2023

IoT Design Methodology

• IoT systems can be a complex and challenging task as these

systems involve interactions between various components and
wide range of choices are available for each component
• Generic design methodology which is independent of specific
product service or programming language
• IoT systems designed with this methodology will have reduced
design time, testing time, maintenance time, complexity and
better interoperability

Domain Model Specification

• Define the structure of IoT in high level
• Visual representation of how the system going to works
• The entities, objects and concepts defined in the domain
model
• Using domain model, system designers can get an
understanding of the IoT domain for which the system
is to be designed.
• The domain model captures the basic attributes of the
main concepts and the relationship between these
concepts
Ex: Pollution monitoring & weather monitoring

2
 29-07-2023

Physical Entity

Device

Virtual Entity
Sensors
Actuators

Tags

Information ModelSpecification
• Information Model defines the structure of all the
information in the IoT system
• Attributes of Virtual Entities, relations, etc.
• To define the information model, we first list the
Virtual Entities defined in the Domain Model
• Information model adds more details to the Virtual
Entities by defining their attributes and relations
• Important meta-information is, e.g., at what time a value
was measured (i.e. time stamp), the location where a
measurement took place, or the quality of the
measurement.

3
 29-07-2023

Functional Model

 The functional view defines the functions of the

IoT systems grouped into various functional
groups.

 Each functional group provides functionalities for

interacting with concepts in the domain model and
information related to the concepts.

 The functional groups in a functional view include:

• Device,
• Communication,
• Services,
• Management,
• Security,
• Application.

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

 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.

4
 29-07-2023

IoT service

 The IoT Service 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 Process Management functional group

Its collection of functionalities that allows smooth integration of IoT-

related services (IoT Services, Virtual Entity Services, Composed Services)
with the Enterprise (Business) Processes.

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

5
 29-07-2023

Security functional group

 The Security FG contains the necessary functions for ensuring the

security and privacy of an IoT system.

 The Identity Management FC manages the different identities of

the involved Services or Users in an IoT system

 The Authentication FC verifies the identity of a User and creates

an assertion upon successful verification. verifies the identity of a
User and creates an assertion upon successful verification.

 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 Key Exchange & Management is used for setting up the

necessary security keys between two communicating entities in an
IoT system.

 The Trust & Reputation FC manages reputation scores of different

interacting entities in an IoT system and calculates the service trust
levels.

6
 29-07-2023

Communication Model

1. Request & Response Model

 This model follows a client-server architecture.

 The client, when required, requests the

information from the server. This request is usually
in the encoded format.

 This model is stateless since the data between the

requests is not retained and each request is
independently handled.

 The server Categories the request, and fetches the

data from the database and its resource
representation. This data is converted to response
and is transferred in an encoded format to the
client. The client, in turn, receives the response.

7
 29-07-2023

Publisher-Subscriber Model

This model comprises three entities: Publishers, Brokers, and Consumers.

•Publishers are the source of data. It sends the data to the topic which are managed by the
broker. They are not aware of consumers.
•Consumers subscribe to the topics which are managed by the broker.
•Hence, Brokers responsibility is to accept data from publishers and send it to the appropriate
consumers.
•The broker only has the information regarding the consumer to which a particular topic belongs
to which the publisher is unaware of.

Push-Pull Model
The push-pull model constitutes data publishers, data consumers, and data queues.
•Publishers and Consumers are not aware of each other.
•Publishers publish the message/data and push it into the queue. The consumers, present on the other side,
pull the data out of the queue. Thus, the queue acts as the buffer for the message when the difference
occurs in the rate of push or pull of data on the side of a publisher and consumer.
•Queues help in decoupling the messaging between the producer and consumer. Queues also act as a
buffer which helps in situations where there is a mismatch between the rate at which the producers push
the data and consumers pull the data.

8
 29-07-2023

Exclusive Pair

•Exclusive Pair is the bi-directional model, including full-duplex communication

among client and server.
•The connection is constant and remains open till the client sends a request to close
the connection.
•The Server has the record of all the connections which has been opened.
•This is a state-full connection model and the server is aware of all open connections.
•WebSocket based communication API is fully based on this model.

Security model
Safety
the can only provide IoT-related guidelines for ensuring a safe system to the extent possible and
controllable by a system 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, Authorization, 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, Authorization, and Trust & Reputation.