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.


Mobility management procedure of CoMP.
© Copyright Policy
Related In: Results  -  Collection

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

sensors-15-16060-f004: Mobility management procedure of CoMP.

Mentions: Figure 4 shows the detailed mobility management procedure for IP mobility management. The CoMP consists of four procedures, i.e., registration, discovery, binding, and notification, to provide mobility management for a moving CoAP node. The operation of CoMP is described in detail below. First, in Figure 4, both the CoAP client and CoAP node send the POST request message for registration to the MMS in order to register their own P_Addr and Lifetime in the MMT of the MMS. As the CoAP client attempts to communicate with the CoAP node, the CoAP client sends a GET request message to the MMS for discovery. This message includes the CoAP client’s destination IP address. In response, the CoAP client receives the current T_Addr for the CoAP node and its Lifetime in the ACK response message for discovery. Then, the CoAP client stores the T_Addr and Lifetime for the CoAP node in the LBC. Subsequently, the CoAP client can exchange data with the CoAP node directly until the Lifetime of T_Addr expires.


CoAP-Based Mobility Management for the Internet of Things.

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

Mobility management procedure of CoMP.
© Copyright Policy
Related In: Results  -  Collection

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

sensors-15-16060-f004: Mobility management procedure of CoMP.
Mentions: Figure 4 shows the detailed mobility management procedure for IP mobility management. The CoMP consists of four procedures, i.e., registration, discovery, binding, and notification, to provide mobility management for a moving CoAP node. The operation of CoMP is described in detail below. First, in Figure 4, both the CoAP client and CoAP node send the POST request message for registration to the MMS in order to register their own P_Addr and Lifetime in the MMT of the MMS. As the CoAP client attempts to communicate with the CoAP node, the CoAP client sends a GET request message to the MMS for discovery. This message includes the CoAP client’s destination IP address. In response, the CoAP client receives the current T_Addr for the CoAP node and its Lifetime in the ACK response message for discovery. Then, the CoAP client stores the T_Addr and Lifetime for the CoAP node in the LBC. Subsequently, the CoAP client can exchange data with the CoAP node directly until the Lifetime of T_Addr expires.

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.