Internet of Things Architecture

(Elliott) #1

  1. Define gateways and other bridging solutions.


5.4.3.1 Guidelines for using the IoT Communication Model


Since the IoT Communication Model aims at providing an overall framework for
communication in IoT systems, it requires well-defined domain and information
definitions. This can be achieved following the examples of the previous
sections. Starting from those, it is possible to identify all the sub-systems, the
complete system is composed of, where we define homogeneous sub-system
as a set of system elements sharing the same communication technology and
sharing similar hardware capability.


Once the sub-systems have been defined, it is possible to analyze capabilities
and constraints for each of them. By capabilities and constraints we intend
communication specific parameters such as data rate, delays, medium reliability
(channel errors) and technology specific parameters such as the available
memory, computational power and supported functionalities.


Modelling
Rule 4

Identify homogeneous sub-systems from the complete
domain model and determine their capabilities and
constraints.

Subsequently, it is possible to analyse communication requirements deriving
from both services in the domain definition and interaction patterns from the
information model. The main goal of the IoT Communication Model is to identify
a set of interoperable protocol stacks and topologies with the following
characteristics:



  1. Each stack must grow from a specific communication technology;

  2. Interoperability shall be enforced in the lowest possible layer of stack;

  3. The combination of identified stacks and topologies must satisfy all the
    requirements.


Modelling
Rule 5

Use existing standard communication mechanisms and
related protocols whenever possible. If this is not possible
then each of the sub-system is the starting point for building
a protocol stack which is both technology specific and
interoperability prone.

This rule enforces technology optimizations and ensures feasibility in all the
subsystems.

Free download pdf