Limits...
CoAP-Based Mobility Management for the Internet of Things.

Chun SM, Kim HS, Park JT - Sensors (Basel) (2015)

Bottom Line: In this article, we propose a mobility management protocol, named CoMP, which can effectively retrieve the sensing data of sensor nodes while they are moving.The numerical analysis and simulation have been done for performance evaluation in terms of the handover latency and packet loss.The results show that the proposed CoMP is superior to previous mobility management protocols, i.e., Mobile IPv4/v6 (MIPv4/v6), Hierarchical Mobile IPv4/v6 (HMIPv4/v6), in terms of the handover latency and packet loss.

View Article: PubMed Central - PubMed

Affiliation: School of Electronics Engineering, College of IT Engineering, Kyungpook National University, Daegu 702-701, Korea. smchun@ee.knu.ac.kr.

ABSTRACT
Most of the current mobility management protocols such as Mobile IP and its variants standardized by the IETF may not be suitable to support mobility management for Web-based applications in an Internet of Things (IoT) environment. This is because the sensor nodes have limited power capacity, usually operating in sleep/wakeup mode in a constrained wireless network. In addition, sometimes the sensor nodes may act as the server using the CoAP protocol in an IoT environment. This makes it difficult for Web clients to properly retrieve the sensing data from the mobile sensor nodes in an IoT environment. In this article, we propose a mobility management protocol, named CoMP, which can effectively retrieve the sensing data of sensor nodes while they are moving. The salient feature of CoMP is that it makes use of the IETF CoAP protocol for mobility management, instead of using Mobile IP. Thus CoMP can eliminates the additional signaling overhead of Mobile IP, provides reliable mobility management, and prevents the packet loss. CoMP employs a separate location management server to keep track of the location of the mobile sensor nodes. In order to prevent the loss of important sensing data during movement, a holding mode of operation has been introduced. All the signaling procedures including discovery, registration, binding and holding have been designed by extending the IETF CoAP protocol. The numerical analysis and simulation have been done for performance evaluation in terms of the handover latency and packet loss. The results show that the proposed CoMP is superior to previous mobility management protocols, i.e., Mobile IPv4/v6 (MIPv4/v6), Hierarchical Mobile IPv4/v6 (HMIPv4/v6), in terms of the handover latency and packet loss.

No MeSH data available.


Handover delay timeline of CoMP.
© Copyright Policy
Related In: Results  -  Collection

License
getmorefigures.php?uid=PMC4541868&req=5

sensors-15-16060-f013: Handover delay timeline of CoMP.

Mentions: The handover delay at a CoAP node side is the time interval during which the CoAP node cannot send or receive any packets during a handoff, and is composed of both L2 and L3 handover latencies [22,23,24]. Figure 13 shows the handover delay timeline caused by executing the CoMP. The white small circle indicates the time line during the handover of CoAP node between WSN BS1 and WSN BS2. The total handover delay, i.e., the packet reception latency tp, consists of the link setup time (tL2), which is caused by an L2 handover; the IP connectivity latency (tIP); and the location update latency (tBU). Here, tIP is the sum of tMD, tAC, and tBU, where tMD represents the movement detection delay; tAC, the address configuration; DAD, the delay; and tBU, the BU delay between the CoAP node and WMMS.


CoAP-Based Mobility Management for the Internet of Things.

Chun SM, Kim HS, Park JT - Sensors (Basel) (2015)

Handover delay timeline of CoMP.
© Copyright Policy
Related In: Results  -  Collection

License
Show All Figures
getmorefigures.php?uid=PMC4541868&req=5

sensors-15-16060-f013: Handover delay timeline of CoMP.
Mentions: The handover delay at a CoAP node side is the time interval during which the CoAP node cannot send or receive any packets during a handoff, and is composed of both L2 and L3 handover latencies [22,23,24]. Figure 13 shows the handover delay timeline caused by executing the CoMP. The white small circle indicates the time line during the handover of CoAP node between WSN BS1 and WSN BS2. The total handover delay, i.e., the packet reception latency tp, consists of the link setup time (tL2), which is caused by an L2 handover; the IP connectivity latency (tIP); and the location update latency (tBU). Here, tIP is the sum of tMD, tAC, and tBU, where tMD represents the movement detection delay; tAC, the address configuration; DAD, the delay; and tBU, the BU delay between the CoAP node and WMMS.

Bottom Line: In this article, we propose a mobility management protocol, named CoMP, which can effectively retrieve the sensing data of sensor nodes while they are moving.The numerical analysis and simulation have been done for performance evaluation in terms of the handover latency and packet loss.The results show that the proposed CoMP is superior to previous mobility management protocols, i.e., Mobile IPv4/v6 (MIPv4/v6), Hierarchical Mobile IPv4/v6 (HMIPv4/v6), in terms of the handover latency and packet loss.

View Article: PubMed Central - PubMed

Affiliation: School of Electronics Engineering, College of IT Engineering, Kyungpook National University, Daegu 702-701, Korea. smchun@ee.knu.ac.kr.

ABSTRACT
Most of the current mobility management protocols such as Mobile IP and its variants standardized by the IETF may not be suitable to support mobility management for Web-based applications in an Internet of Things (IoT) environment. This is because the sensor nodes have limited power capacity, usually operating in sleep/wakeup mode in a constrained wireless network. In addition, sometimes the sensor nodes may act as the server using the CoAP protocol in an IoT environment. This makes it difficult for Web clients to properly retrieve the sensing data from the mobile sensor nodes in an IoT environment. In this article, we propose a mobility management protocol, named CoMP, which can effectively retrieve the sensing data of sensor nodes while they are moving. The salient feature of CoMP is that it makes use of the IETF CoAP protocol for mobility management, instead of using Mobile IP. Thus CoMP can eliminates the additional signaling overhead of Mobile IP, provides reliable mobility management, and prevents the packet loss. CoMP employs a separate location management server to keep track of the location of the mobile sensor nodes. In order to prevent the loss of important sensing data during movement, a holding mode of operation has been introduced. All the signaling procedures including discovery, registration, binding and holding have been designed by extending the IETF CoAP protocol. The numerical analysis and simulation have been done for performance evaluation in terms of the handover latency and packet loss. The results show that the proposed CoMP is superior to previous mobility management protocols, i.e., Mobile IPv4/v6 (MIPv4/v6), Hierarchical Mobile IPv4/v6 (HMIPv4/v6), in terms of the handover latency and packet loss.

No MeSH data available.