Modeling of Bootstrapping and Registration IoT Design Patterns
57
2.0. In this metamodel, we concentrate on two categories of design patterns;
“Bootstrapping Design Patterns” and “Registration Design Patterns”.
“Bootstrapping Design Patterns” allow configuring new devices. They are
composed of “Medium Based Bootstrap Pattern” and “Remote Bootstrap Pattern”. “Medium Based Bootstrap Pattern” allows to configure a new device
on-site through a removable storage medium inserted in the device. This support contains the necessary information for configuration. “Remote Bootstrap
Pattern” is a configuration pattern used in case that a device is placed far away
and is difficult to reach. The configuration in this case is done by downloading
configuration information from a bootstrap server.
“Registration Design Patterns” allow to register the attributes and the features of a new device on the Back-end server. The registration is used to facilitate the communication and the interrogation with other connected objects.
There are many registration patterns. In this work, we present two patterns. So
“Registration Design Patterns” are composed of “Automatic Client Driven Registration Pattern” and “Server Driven Model Pattern”. The “Automatic Client
Driven Registration Pattern” allows the device to register on the Back-end server
via an API call. The “Server Driven Model Pattern” is used to create a device
model that includes its description and functionality.
The basic elements of the metamodel are:
Component and Object: Entities, that make up the architecture of an IoT
design pattern, can be either Components or Objects. All objects are components, but not all components are necessarily objects. An object can be
connected to the internet, it can receive and send data.
Port: Entities can have Ports that constitute interaction points with their environment. These Ports are related to one or more provided or required Interfaces.
Interface: The interfaces are the points of communication that allow interaction with the environment. For an entity, there are two types of interfaces.
The Provided Interfaces describe the services provided by the component.
The Required Interfaces describe the required services that other components
must provide for the good functioning of component. These interfaces are
specified via the ports.
Connector: The communication path between Entities within an architecture
is called a Connector. It ensures the link between a Provided port and a
Required port to form a complete and coherent system.
Device: A device is an Object. It is the entry point of the physical environment,
it is used to process sensor data and to control actuators.
2.2 General Pattern Model
In this section, we present two general pattern models as instances of the proposed metamodel. We have used different notations that can be used as a graphical description of the entities presented in the model. We are based on the work
of Reinfurt et al. [8].
57
2.0. In this metamodel, we concentrate on two categories of design patterns;
“Bootstrapping Design Patterns” and “Registration Design Patterns”.
“Bootstrapping Design Patterns” allow configuring new devices. They are
composed of “Medium Based Bootstrap Pattern” and “Remote Bootstrap Pattern”. “Medium Based Bootstrap Pattern” allows to configure a new device
on-site through a removable storage medium inserted in the device. This support contains the necessary information for configuration. “Remote Bootstrap
Pattern” is a configuration pattern used in case that a device is placed far away
and is difficult to reach. The configuration in this case is done by downloading
configuration information from a bootstrap server.
“Registration Design Patterns” allow to register the attributes and the features of a new device on the Back-end server. The registration is used to facilitate the communication and the interrogation with other connected objects.
There are many registration patterns. In this work, we present two patterns. So
“Registration Design Patterns” are composed of “Automatic Client Driven Registration Pattern” and “Server Driven Model Pattern”. The “Automatic Client
Driven Registration Pattern” allows the device to register on the Back-end server
via an API call. The “Server Driven Model Pattern” is used to create a device
model that includes its description and functionality.
The basic elements of the metamodel are:
Component and Object: Entities, that make up the architecture of an IoT
design pattern, can be either Components or Objects. All objects are components, but not all components are necessarily objects. An object can be
connected to the internet, it can receive and send data.
Port: Entities can have Ports that constitute interaction points with their environment. These Ports are related to one or more provided or required Interfaces.
Interface: The interfaces are the points of communication that allow interaction with the environment. For an entity, there are two types of interfaces.
The Provided Interfaces describe the services provided by the component.
The Required Interfaces describe the required services that other components
must provide for the good functioning of component. These interfaces are
specified via the ports.
Connector: The communication path between Entities within an architecture
is called a Connector. It ensures the link between a Provided port and a
Required port to form a complete and coherent system.
Device: A device is an Object. It is the entry point of the physical environment,
it is used to process sensor data and to control actuators.
2.2 General Pattern Model
In this section, we present two general pattern models as instances of the proposed metamodel. We have used different notations that can be used as a graphical description of the entities presented in the model. We are based on the work
of Reinfurt et al. [8].