182
F. Firouzi and B. Farahani
Cloud indicating that the software update was completed successfully. This message
will cause a configuration synchronization task to begin so that the physical device’s
status and the device’s digital twin can be in sync.
4.3.3 Monitoring and Control
Within a system comprised of thousands of remote devices, the secure and
efficient operation of individual devices can impact the profit margin. Seemingly
small problems can significantly impact customer satisfaction and hinder business
success. Diagnostic and monitoring tools are the key to reducing the negative impact
of device downtime caused by unpredicted operational issues or software problems.
For example, problems or issues can be detected by tracking and analyzing storage,
computing, input/output, and networking statistics at the processor task level.
The ability to download program dumps and logs is also vital to identifying and
resolving software issues because it is not possible to travel to each device to debug
them using a serial terminal. An application developer has to employ solid program
logging and device management software to ensure that the necessary debugging
information is available to be uploaded in the event of an error. In addition, the
device management software must also generate practical problem insights for
issues that occur across many devices.
Often, devices require additional configuration by the user, including attributes
such as location, name, and specific application settings. For example, in IoTbased fleet management application, a device must monitor vehicle location and
status and then send that information to the Cloud using a cellular connection.
In this context, specific parameters must be written when the device is installed,
including the distinctive truck or trailer ID (e.g., license plate number). Additional
configuration settings such as the time interval for the sending position data can
also be programmed into the device. Unless you want to preconfigure every shipped
device, it is important to be able to remotely access and manage devices to provide
on-demand support and configuration.
4.4 Data Ingestion Layer
Data ingestion is considered as the starting place and the first stage of the IoT data
pipeline in Cloud. This layer is concerned with connecting to different sources of
IoT data, bringing data (particularly, (semi-) unstructured data) into the Cloud as
well as routing data to appropriate destinations in Cloud. Note that in the ingestion
layer, data can be consumed in batches or streamed in real time. When it comes
F. Firouzi and B. Farahani
Cloud indicating that the software update was completed successfully. This message
will cause a configuration synchronization task to begin so that the physical device’s
status and the device’s digital twin can be in sync.
4.3.3 Monitoring and Control
Within a system comprised of thousands of remote devices, the secure and
efficient operation of individual devices can impact the profit margin. Seemingly
small problems can significantly impact customer satisfaction and hinder business
success. Diagnostic and monitoring tools are the key to reducing the negative impact
of device downtime caused by unpredicted operational issues or software problems.
For example, problems or issues can be detected by tracking and analyzing storage,
computing, input/output, and networking statistics at the processor task level.
The ability to download program dumps and logs is also vital to identifying and
resolving software issues because it is not possible to travel to each device to debug
them using a serial terminal. An application developer has to employ solid program
logging and device management software to ensure that the necessary debugging
information is available to be uploaded in the event of an error. In addition, the
device management software must also generate practical problem insights for
issues that occur across many devices.
Often, devices require additional configuration by the user, including attributes
such as location, name, and specific application settings. For example, in IoTbased fleet management application, a device must monitor vehicle location and
status and then send that information to the Cloud using a cellular connection.
In this context, specific parameters must be written when the device is installed,
including the distinctive truck or trailer ID (e.g., license plate number). Additional
configuration settings such as the time interval for the sending position data can
also be programmed into the device. Unless you want to preconfigure every shipped
device, it is important to be able to remotely access and manage devices to provide
on-demand support and configuration.
4.4 Data Ingestion Layer
Data ingestion is considered as the starting place and the first stage of the IoT data
pipeline in Cloud. This layer is concerned with connecting to different sources of
IoT data, bringing data (particularly, (semi-) unstructured data) into the Cloud as
well as routing data to appropriate destinations in Cloud. Note that in the ingestion
layer, data can be consumed in batches or streamed in real time. When it comes