Emergency response MAC protocol (ER-MAC) for wireless sensor networks

Files in this item

Icon
Name: 2010_IPSN.pdf
Size: 155.5Kb
Format: PDF
Description: Accepted version
View/Open

Emergency response MAC protocol (ER-MAC) for wireless sensor networks

Sitanayah, Lanny; Sreenan, Cormac J.; Brown, Kenneth N.
Date: 2010-04
Copyright: © ACM New York, NY, USA ©2010. This is the author's version of the work. It is posted here for your personal use. Not for redistribution. The definitive Version of Record was published in IPSN '10 Proceedings of the 9th ACM/IEEE International Conference on Information Processing in Sensor Networks, http://dx.doi.org/10.1145/10.1145/1791212.1791256
Related: https://dl.acm.org/citation.cfm?id=1791256
Citation: Sitanayah, L., Sreenan, C. J. and Brown, K. N. (2010) 'Emergency response MAC protocol (ER-MAC) for wireless sensor networks', Poster Abstract, Proceedings of the 9th ACM/IEEE International Conference on Information Processing in Sensor Networks, Stockholm, Sweden, 12-16 April, 1791256: ACM, pp. 364-365. doi: 10.1145/1791212.1791256
Published Version: 10.1145/1791212.1791256

Abstract:

We introduce ER-MAC, a hybrid MAC protocol for emergency response wireless sensor networks. ER-MAC is designed as a hybrid of the TDMA and CSMA approaches, giving it the flexibility to adapt to traffic and topology changes. It adopts a TDMA approach to schedule collision-free slots. Nodes wake up for their scheduled slots, but otherwise sleep to conserve energy. When an emergency occurs, nodes that participate in the emergency monitoring change their MAC behaviour by allowing contention in TDMA slots. Simulations in ns-2 show that ER-MAC outperforms Z-MAC with higher delivery ratio, lower latency, and lower energy consumption.

Show full item record

This item appears in the following Collection(s)

This website uses cookies. By using this website, you consent to the use of cookies in accordance with the UCC Privacy and Cookies Statement. For more information about cookies and how you can disable them, visit our Privacy and Cookies statement