Proceedings of the 8th International Conference on the Internet of Things 2018
DOI: 10.1145/3277593.3277606
|View full text |Cite
|
Sign up to set email alerts
|

An architecture for IoT clock synchronization

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
8
2

Relationship

0
10

Authors

Journals

citations
Cited by 37 publications
(11 citation statements)
references
References 16 publications
0
11
0
Order By: Relevance
“…It is worth mentioning that the use of 32-bit single-precision floating-point format is common not only for the resourceconstrained sensor node platforms (e.g., TelosB [12] and MicaZ [18]) but also for the lightweight Arduino boards [19], which are frequently used as hardware platforms for Internet of Things (IoT) prototyping as discussed in [20].…”
Section: Impact Of Limited Precision Floating-point Arithmetic On Hig...mentioning
confidence: 99%
“…It is worth mentioning that the use of 32-bit single-precision floating-point format is common not only for the resourceconstrained sensor node platforms (e.g., TelosB [12] and MicaZ [18]) but also for the lightweight Arduino boards [19], which are frequently used as hardware platforms for Internet of Things (IoT) prototyping as discussed in [20].…”
Section: Impact Of Limited Precision Floating-point Arithmetic On Hig...mentioning
confidence: 99%
“…More explicitly in the IoT domain, Sridhar et al describe the CheepSync time synchronization protocol [18] for Bluetooth Low Energy (BLE) platforms. S. K. Mani et al [19] developed a synchronization system, including a lightweight client, a new packet exchange protocol called SPoT. In another work, R. Gore et al [20] proposed a lightweight clock synchronization algorithm called CoSiNeT for IIoT field devices.…”
Section: Related Workmentioning
confidence: 99%
“…Furthermore, time-keeping devices are known to drift apart, especially when subjected to harsh environmental conditions [78], which showcases the need for effective communication-based synchronization [79]. For reference, under normal conditions, the resonator of an Arduino Uno or Mega, operating at 16 MHz, lose 10s of seconds per day, a performance that is fairly poor [80] for time-critical applications. The significance of this deviation might not impact that many agricultural applications, but it is clear that even if the clocks of two nodes are synchronized at a certain point in time, their indications will eventually drift apart, creating the need for regular repeats of the synchronization process.…”
Section: Synchronization In Wsnsmentioning
confidence: 99%