A Time Synchronization Protocol for Energy-Constrained Wireless Networks

KIPS Transactions on Software and Data Engineering, Vol. 4, No.9, pp.385-392, September 2015
10.3745/KTSDE.2015.4.9.385, Full Text

Abstract

In IoT(Internet of Things), it is important for wireless networks to communicate data created among resource-constrained wireless nodes, where time synchronization is needed for meaningful data creation and transmission. Time Synchronization by flooding is one of the mostly used protocols for WSN(Wireless Sensor Networks). Even though this type of scheme has some advantages over other types (i.e. a simple algorithm and independency of topology and so on), too many data transmission is required, leading to large power consumption. So, reducing transmission data is an important issue for energy efficiency in this kind of networks. In this paper, a new Flooding-based time synchronization protocol is proposed to use energy efficiently by reducing a transmitted traffic. The proposed scheme``s performance has been evaluated and compared with an representative scheme, FTSP(Flooding Time Synchronization Protocol) by simulation. The results are shown that the proposed scheme is better than FTSP.


Statistics

Show / Hide Statistics

Statistics (Cumulative Counts from October 15, 2016)

Multiple requests among the same browser session are counted as one view. If you mouse over a chart, the values of data points will be shown.


Cite this paper

[KIPS Transactions Style]
S. K. Bae, "A Time Synchronization Protocol for Energy-Constrained Wireless Networks," KIPS Transactions on Software and Data Engineering, Vol.4, No.9, pp.385-392, 2015, DOI: 10.3745/KTSDE.2015.4.9.385.

[IEEE Style]
Shi Kyu Bae, "A Time Synchronization Protocol for Energy-Constrained Wireless Networks," KIPS Transactions on Software and Data Engineering, vol. 4, no. 9, pp. 385-392, 2015. DOI: 10.3745/KTSDE.2015.4.9.385.

[ACM Style]
Bae, S. K. 2015. A Time Synchronization Protocol for Energy-Constrained Wireless Networks. KIPS Transactions on Software and Data Engineering, 4, 9, (2015), 385-392. DOI: 10.3745/KTSDE.2015.4.9.385.