Internet of Things Architecture

M2M Device or gateway. This package is also called Fault and

Performance Management;

 Software/Firmware Management (SFW): Allows installation

/update/removal of application specific orSCL related software / firmware

in M2M Device or gateway;

 Area Network Management (ANW): Allows M2M Gateway-specific

configuration and M2M Area Network and Device management through a

M2M gateway;

 Service Capability Layer Management (SCL): Allows remote

configuration and retrieval of M2M Device or gateway service capability

layer parameters.

In a similar fashion, Section 4.2.2 of this document identifies different Functional
Components used for management functionalities. These include:

 Configuration: Initialising the system configuration. Gathering and

storing configurations from FCs and Devices, tracking configuration

changes;

 Fault: The goal of the Fault FC is to identify, isolate, correct and log

faults that occur in the IoT system;

 Member: This FC is responsible for the management of the membership

and associated information of any relevant entity (FG, FC, VE, IoT

Service, Device, Application, and User) to an IoT system;

 Reporting: The Reporting FC can be seen as an overlay for the other

Management FCs. It distils information provided by them. One of many

conceivable reporting goals is to determine the efficiency of the current

system;

 State: The State FC monitors and predicts state of the IoT system. For a

ready diagnostic of the system, as required by Fault FC, the past, current

and predicted (future) state of the system are provided.

When mapping these different management components, it becomes obvious
once again that the focus of ETSI M2M is narrower in terms of its scope and
therefore it is more detailed in the definition of its management capabilities and
does not include all of the functionality defined by IoT-A. For instance, there is
no equivalent to State FC in terms of its temporal distribution and the related
billing capabilities. This aspect is not really central, as it is not contradictory and
could be built upon the D&M package. In general however there is a strong
overlap, as D&M roughly relates to the Reporting FC, CFG closely resembles
Configuration, and both D&M and Fault deal with monitoring functionalities.
Error and fault handling as such is handled specifically in the Fault FC, whereas
D&M also handles performance management. On the other hand, and in line
with the general focus of ETSI-M2M, the different aspects of the Configuration