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.


Request/Response message format.
© Copyright Policy
Related In: Results  -  Collection

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

sensors-15-16060-f006: Request/Response message format.

Mentions: In this subsection, we present the message format using CoAP. Figure 5 shows the IP address information during CoMP handover. We assume that the CoAP node moves from WSN BS1 to WSN BS2. In this situation, Cur_T_Addr and Cur_Lifetime of CoAP node are changed to New_T_Addr as a temporary IP address, i.e., T_Addr, and New_Lifetime as Lifetime, respectively. However, P_Addr as the permanent IP address, i.e., P_Addr, does not change. P_Addr, T_Addr, and Lifetime of CoAP nodes are cached on the WMMT of the WMMS. W_Addr indicates the IP address of the WMMS. Figure 6 shows the request message and response message format in the CoAP standard. The detailed information refers to the CoAP standard document [2]. The message format is based on the RESTful format.


CoAP-Based Mobility Management for the Internet of Things.

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

Request/Response message format.
© Copyright Policy
Related In: Results  -  Collection

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

sensors-15-16060-f006: Request/Response message format.
Mentions: In this subsection, we present the message format using CoAP. Figure 5 shows the IP address information during CoMP handover. We assume that the CoAP node moves from WSN BS1 to WSN BS2. In this situation, Cur_T_Addr and Cur_Lifetime of CoAP node are changed to New_T_Addr as a temporary IP address, i.e., T_Addr, and New_Lifetime as Lifetime, respectively. However, P_Addr as the permanent IP address, i.e., P_Addr, does not change. P_Addr, T_Addr, and Lifetime of CoAP nodes are cached on the WMMT of the WMMS. W_Addr indicates the IP address of the WMMS. Figure 6 shows the request message and response message format in the CoAP standard. The detailed information refers to the CoAP standard document [2]. The message format is based on the RESTful format.

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.