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.


LBC schema.
© Copyright Policy
Related In: Results  -  Collection

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

sensors-15-16060-f003: LBC schema.

Mentions: As shown in Figure 2, the network architecture of a CoAP node is comprised of CoAP and CoMP at the application layer, UDP at the transport layer, a 6LoWPAN at the network layer, and IEEE 802.15.4 at MAC layer. CoAP is composed of the message layer and request/response layer. The CoMP makes use of GET, POST, PUT, and DELETE methods at the CoAP Request/Response layer in order to provide mobility management functionality. The CoAP node contains a local binding cache (LBC), which includes P_Addr, T_Addr, Lifetime, and H_Flag. In order to provide the mobility management function, the CoMP refers to the LBC table, whose schema is shown in Figure 3. The meanings of those fields on LBC are the same as those in MMT. The Lifetime value of “0” at LBC indicates that an LBC entry for the CoAP node must be deleted and retrieved from the entry of the CoAP node in the MMT of the WMMS. A key feature of CoMP is the use of hold mode, i.e., H_Flag, to prevent packet losses while a CoAP node is moving among different wireless networks.


CoAP-Based Mobility Management for the Internet of Things.

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

LBC schema.
© Copyright Policy
Related In: Results  -  Collection

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

sensors-15-16060-f003: LBC schema.
Mentions: As shown in Figure 2, the network architecture of a CoAP node is comprised of CoAP and CoMP at the application layer, UDP at the transport layer, a 6LoWPAN at the network layer, and IEEE 802.15.4 at MAC layer. CoAP is composed of the message layer and request/response layer. The CoMP makes use of GET, POST, PUT, and DELETE methods at the CoAP Request/Response layer in order to provide mobility management functionality. The CoAP node contains a local binding cache (LBC), which includes P_Addr, T_Addr, Lifetime, and H_Flag. In order to provide the mobility management function, the CoMP refers to the LBC table, whose schema is shown in Figure 3. The meanings of those fields on LBC are the same as those in MMT. The Lifetime value of “0” at LBC indicates that an LBC entry for the CoAP node must be deleted and retrieved from the entry of the CoAP node in the MMT of the WMMS. A key feature of CoMP is the use of hold mode, i.e., H_Flag, to prevent packet losses while a CoAP node is moving among different wireless networks.

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.