S. Rinaldi, P. Bellagente, P. Ferrari, A. Flammini, E. Sisinni
{"title":"Are Cloud Services Aware of Time? An Experimental Analysis oriented to Industry 4.0","authors":"S. Rinaldi, P. Bellagente, P. Ferrari, A. Flammini, E. Sisinni","doi":"10.1109/ISPCS.2019.8886642","DOIUrl":null,"url":null,"abstract":"In the last years, the industrial automation has experienced a deep transformation known as Industry4.0, and it is driven by Internet of Things (IoT) paradigm. The IoT-based automation is based on well-defined data models, which make easy the interaction among devices. Generally, the data generated by IoT sensors are elaborated to obtain value added services (such as predictive maintenance), exploiting cloud services and remote servers. An accurate timestamp of the data generated by sensors is required to maintain an adequate level of such services: an “easy” task in the case of a new deployment, but a nightmare when existing plants or machinery are retrofitted. In this case, the data are timestamped at cloud level, using the remote time. In such situations, a knowledge of the sense of time of cloud services is fundamental to guarantee the quality of data elaboration. The target of the research is an experimental characterization and a comparison of time awareness of different commercial cloud service providers (i.e. Amazon AWS, Google Cloud and Microsoft Azure). The characterization highlights as, generally, the performance provided by different platform is comparable each other. The time offset of NTP (Network Time Protocol) clients running on different Virtual Machines (VMs) has an uncertainty ranging from 0.05 ms up to 0.6 ms depending by the client configuration. Such results demonstrate that extreme care must be taken when using the time of remote VMs.","PeriodicalId":193584,"journal":{"name":"2019 IEEE International Symposium on Precision Clock Synchronization for Measurement, Control, and Communication (ISPCS)","volume":"545 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2019 IEEE International Symposium on Precision Clock Synchronization for Measurement, Control, and Communication (ISPCS)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ISPCS.2019.8886642","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 2
Abstract
In the last years, the industrial automation has experienced a deep transformation known as Industry4.0, and it is driven by Internet of Things (IoT) paradigm. The IoT-based automation is based on well-defined data models, which make easy the interaction among devices. Generally, the data generated by IoT sensors are elaborated to obtain value added services (such as predictive maintenance), exploiting cloud services and remote servers. An accurate timestamp of the data generated by sensors is required to maintain an adequate level of such services: an “easy” task in the case of a new deployment, but a nightmare when existing plants or machinery are retrofitted. In this case, the data are timestamped at cloud level, using the remote time. In such situations, a knowledge of the sense of time of cloud services is fundamental to guarantee the quality of data elaboration. The target of the research is an experimental characterization and a comparison of time awareness of different commercial cloud service providers (i.e. Amazon AWS, Google Cloud and Microsoft Azure). The characterization highlights as, generally, the performance provided by different platform is comparable each other. The time offset of NTP (Network Time Protocol) clients running on different Virtual Machines (VMs) has an uncertainty ranging from 0.05 ms up to 0.6 ms depending by the client configuration. Such results demonstrate that extreme care must be taken when using the time of remote VMs.