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.


GET request, ACK response message for discovery of IP address.
© Copyright Policy
Related In: Results  -  Collection

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

sensors-15-16060-f007: GET request, ACK response message for discovery of IP address.

Mentions: Figure 6 shows the CoAP message format [2]. We use the CoAP message format and extend the option delta to perform the CoMP signaling procedure. In the CoAP message format in Figure 6, we define the option delta and option length to specify the resource constraints. We extend the option delta value to support the CoMP. Table 2 shows the extended option delta and its description of the CoMP message. In the option delta, the 2048–2054 are newly defined. The range of 2048 to 64,999 of option delta gives the designated expert in CoAP standard [2]. The message type field includes CoAP methods, i.e., GET, PUT, POST, and DELETE. Figure 7, Figure 8, Figure 9, Figure 10 and Figure 11 show the CoMP message format.


CoAP-Based Mobility Management for the Internet of Things.

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

GET request, ACK response message for discovery of IP address.
© Copyright Policy
Related In: Results  -  Collection

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

sensors-15-16060-f007: GET request, ACK response message for discovery of IP address.
Mentions: Figure 6 shows the CoAP message format [2]. We use the CoAP message format and extend the option delta to perform the CoMP signaling procedure. In the CoAP message format in Figure 6, we define the option delta and option length to specify the resource constraints. We extend the option delta value to support the CoMP. Table 2 shows the extended option delta and its description of the CoMP message. In the option delta, the 2048–2054 are newly defined. The range of 2048 to 64,999 of option delta gives the designated expert in CoAP standard [2]. The message type field includes CoAP methods, i.e., GET, PUT, POST, and DELETE. Figure 7, Figure 8, Figure 9, Figure 10 and Figure 11 show the CoMP message 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.