A Mechanism for Reliable Mobility Management for Internet of Things Using CoAP
AbstractUnder unreliable constrained wireless networks for Internet of Things (IoT) environments, the loss of the signaling message may frequently occur. Mobile Internet Protocol version 6 (MIPv6) and its variants do not consider this situation. Consequently, as a constrained device moves around different wireless networks, its Internet Protocol (IP) connectivity may be frequently disrupted and power can be drained rapidly. This can result in the loss of important sensing data or a large delay for time-critical IoT services such as healthcare monitoring and disaster management. This paper presents a reliable mobility management mechanism in Internet of Things environments with lossy low-power constrained device and network characteristics. The idea is to use the Internet Engineering Task Force (IETF) Constrained Application Protocol (CoAP) retransmission mechanism to achieve both reliability and simplicity for reliable IoT mobility management. Detailed architecture, algorithms, and message extensions for reliable mobility management are presented. Finally, performance is evaluated using both mathematical analysis and simulation. View Full-Text
Scifeed alert for new publicationsNever miss any articles matching your research from any publisher
- Get alerts for new papers matching your research
- Find out the new papers from selected authors
- Updated daily for 49'000+ journals and 6000+ publishers
- Define your Scifeed now
Chun, S.-M.; Park, J.-T. A Mechanism for Reliable Mobility Management for Internet of Things Using CoAP. Sensors 2017, 17, 136.
Chun S-M, Park J-T. A Mechanism for Reliable Mobility Management for Internet of Things Using CoAP. Sensors. 2017; 17(1):136.Chicago/Turabian Style
Chun, Seung-Man; Park, Jong-Tae. 2017. "A Mechanism for Reliable Mobility Management for Internet of Things Using CoAP." Sensors 17, no. 1: 136.
Note that from the first issue of 2016, MDPI journals use article numbers instead of page numbers. See further details here.