Perform authentication/authorization
of new device
Add new device to Member FC
Management FG
Add IoT Services for
device resources
IoT Service FG
Establish secure communication with device
Update other Management FCs Add entries to IoT Service Resolution FC
Figure 97 : Adding a new Device to the system - activity diagram
5.5.1.2 Changing the device configuration
In this section, we discuss how a device or a group of devices can be
configured using different FCs of the IoT Reference Architecture. Such process
involves the following steps depicted in Figure 98 :
As a pre-requisite, the communication link from the Device FG to the
various IoT Resources should be established, relying on Communication
and Security functions;
The request for a configuration change is issued by a human system
manager through a management console, or by a FC. It results in a call
to the Management: Member FC (step 1) through the
retrieveMember() interface followed by a call to Management:
Configuration FC (step 2) through the setConfiguration() interface.
Naturally, such calls are subject to access control through the Security:
Authentication and Security: Authorization FCs – not represented);
Depending on design choices made (e.g. whether the configuration of the
associated resource is part of the related IoT Service or not), the actual
configuration update on the device can be realized by either
communicating directly with the device (e.g. sending a configuration
message, steps 3‘, 4‘) or through the IoT Service associated with the
resource (steps 3-5).