# Distributed Group-Based Mobility Management Scheme in Wireless Body Area Networks

Authors: Moneeb Gohar; Hind Ahmed M. Alrubaish; Ruba Suliman M. Alowaid; Jin-Ghoo Choi
Journal: Wireless Communications and Mobile Computing
 (2017)

---

## Abstract

For group-based mobility management in 6LoWPAN-based wireless body area networks (WBAN), some schemes using the Proxy Mobile IPv6 (PMIP) have been proposed. However, the existing PMIP-based mobility schemes tend to induce large registration delay and handover delay. To overcome such limitations, we propose a new distributed group-based mobility management scheme, in which the Local Mobility Anchor (LMA) function is implemented by each Mobile Access Gateway (MAG) and the handover operation is performed between two neighboring MAGs without the help of LMA. Besides, each MAG maintains the information of the group of mobile sensors and aggregates the Authentication-Authorization-Accounting (AAA) query messages for a group of mobile sensors as a “single” message to decrease the control overhead. By numerical analysis, it is shown that the proposed scheme can reduce the registration and handover delays, compared to the existing PMIP-based mobility schemes.


---

## Body

## 1. Introduction

World population growth is facing challenges like increase of life expectancy leading to aging population and rise in healthcare costs. These challenges have triggered the introduction of novel technology-driven enhancements to current healthcare practices such as small and intelligent medical sensors which can be worn on or implanted in the human body. These sensors send their data to an external medical server. With these sensors, the patient experiences greater physical mobility. On the other hand, millions of people die from different fatal diseases like cancer and cardiovascular disease every year. This is because many people are diagnosed when it is too late. However, it is possible to utilize the latest technological advances in wireless body area network (WBAN) systems for the early detection and prevention of potential diseases that may occur later in people’s lives. This can be done by using the sensors nodes on WBAN for continuous monitoring of health conditions [1–3].In WBAN, sensors can be attached to the human body or clothes [4, 5]. These sensors can be used to measure the parameters associated with the human body. The measured values can be gathered and transmitted to the main server healthcare applications.The IP shortage problem can be solved through IPv6 addresses, because it has large address spaces. Recently, Low-power Wireless Personal Area Networks (LoWPANs) have attracted lots of attention because of the Internet of Things (IOTs). The Internet Engineering Task Force (IETF) has set up a working group recently for IPv6 over Low-power Wireless Personal Area Networks (6LoWPANs) [6], in which it is possible to connect wireless sensor nodes to IPv6 networks. However, the wireless sensors nodes are unable to hold the complete IPv6 address because the maximum packet size of IEEE 802.15.4 is 127 bytes. For this purpose, the 6LoWPAN adds an adaptation layer between MAC and the network layer to compress the 40-byte IPv6 packet header into 2 bytes for incoming communication and decompress it for the outgoing interface.In mobile environments, it is required to provide sensor nodes with mobility management, such as handover control. The host-based approaches such as Mobile IPv6 (MIPv6) [7], Hierarchal Mobile IPv6 (HMIPv6) [8], and Fast Mobile IPv6 (FMIPv6) [9] are unsuitable to be applied in Internet Protocol (IP) based wireless sensor networks. All of the sensors have mobility stack and have actively participated in mobility related signaling. The network-based approaches, such as Proxy Mobile IPv6 (PMIPv6), can be considered as the most suitable approach for the mobility management in 6LoWPAN based WBAN.Recently, several schemes have been proposed to support mobility in the 6LoWPAN-based WBAN [10, 11], which usually use the Proxy Mobile IPv6 (PMIP) protocol [12]. These schemes reduce the registration and handover delays, but there remains much room for improvement in the delay performance.In this paper, we propose an enhanced group-based mobility scheme for 6LoWPAN-based WBAN by using the distributed PMIP approach so as to further reduce registration and handover delays. In the proposed scheme, the Local Mobility Anchor (LMA) function is implemented by each Mobile Access Gateway (MAG), and MAGs perform the handover control operations for the group of sensors. The MAGs also perform the aggregation of Authentication-Authorization-Accounting (AAA) query messages incurred by the movement of the group of sensor nodes. Different from the standard PMIP protocol, each MAG does not perform the binding update and deregistration operations with LMA, since it has the LMA functionality.The rest of this paper is organized as follows. Section2 describes the related works and existing mobility schemes for comparison and motivation. Section 3 describes the proposed distributed group-based mobility scheme. Section 4 demonstrates the performance analysis by comparing the proposed and existing schemes by numerical analysis. Section 5 presents the numerical results and discussion. Section 6 concludes this paper.


## 2. Related Works

In this section, first related works are described and then the existing group-based mobility schemes are considered for comparison in this paper.


### 2.1. Related Works

Reference [13] provides a survey of sensor devices and protocols on physical layer, data link layer, and radio technology aspects of body area networks. This paper also highlighted some of the design challenges and open issues on body area networks that still need to be addressed. In [14], it is shown that IPv6 over Low-power Wireless Personal Area Networks (6LoWPANs) is suitable for wireless body sensor networks because the sensors are based on IEEE 802.15.4 standard. The 6LoWPAN mobility has been an important solution in wireless body sensor networks. Most of the existing host-based mobility [7–9, 15] protocols for IPv6 are unsuitable for 6LoWPAN based wireless sensor networks, because they are tunnel based approaches, which shows that all of the mobile sensors actively participated in mobility related signaling in order to ensure the continuity of communications. The network-based approach [12, 16] is suitable to handle the mobility management of 6LoWPAN based body sensors. On behalf of sensors, the network node exchanges the mobility related signaling and there is no need to perform Duplicate Address Detection (DAD) of the IP address and thus it reduces the control signaling cost and handover latency of each sensor. In [17], the author highlighted the requirements and resources for adapting the existing solutions to 6LoWPAN based on the notion that single mobile node’s perspective is still a challenge and further researches are required. Therefore, [18] proposed a scheme to support Internet Protocol (IP) wireless sensor networks in which the packet format in ingress interface is to deal with the handoff procedure. In [17], it is also shown that multihop communications are not supported by Proxy Mobile IP (PMIP) protocol. Hence, in [19], a multihop communication scheme has been proposed in the ingress interface by using mesh routing. But this scheme is only on single mobile node perspective. So, if there is a group of mobile nodes moving around together, then this scheme [19] has no effective solution. In [20], a 6LoWPAN based mobility scheme has been proposed which depends on the dispatch types. But this scheme does not have a clear improvement on reducing handover delay. From the network-based perspective, in [21], a Network Mobility (NEMO) [10] based 6LoWPAN mobility scheme has been proposed, in which a mobile router performs the handoff and modifies the 6LoWPAN dispatch. However, this protocol overloaded the mobile router. To maintain the sessions while reducing the handover delay and signaling cost of group-based mobility in 6LoWPAN-based wireless sensor body area networks is an important issue. Therefore, [22] considered lots of correlated sensor nodes moving together and performed handoff together at the same time in PMIPv6 environment. The Local Mobility Anchor (LMA) calculates the SNR value for each sensor and makes a group of sensors with similar SNR values. This protocol sends Proxy Binding Ack (PBA) per group which can reduce the handoff signaling cost and save some additional unnecessary handoff messages such as Proxy Binding Update (PBU) and deregistration PBU (DeReg PBU). However, this protocol does not reduce the Router Solicitation (RS) and Router Advertisement (RA) messages in case body sensors move in the PMIPv6 domain together. Therefore, this protocol is not suitable for the 6LoWPAN-based wireless sensor body network. So, in [23], network architecture is proposed which integrates NEMO and 6LoWPAN. The mechanism of group mobility management and the signaling process containing the registration at the home network, association negotiation, handoff between different access routers, and packet routing are discussed. However, this protocol increases the burden of the sensor router due to connection and support for other normal sensor nodes inside the group. This protocol is designed for MIPv6, not for PMIPv6.


### 2.2. Existing Group-Based Mobility Schemes for Comparison

#### 2.2.1. PMIP [12]

In this scheme, the standard PMIP is used for the group-based mobility support [11]. As shown in Figure 1, when a set of body sensors are detached from a previous MAG (p-MAG), the p-MAG sendsderegistration (DeReg) messages to LMA for each body sensor. When the body sensors are attached to a new MAG (n-MAG), each body sensor sends aRouter Solicitation (RS) message to n-MAG via thecoordinator and Full-Function Device (FFD) which are preconfigured in the 6LoWPAN network [6].Figure 1
Existing PMIP mobility schemes.Upon reception of RS messages from body sensors, n-MAG will send theAuthentication-Authorization-Accounting (AAA) query messages for authentication for all body sensors. After authentication, AAA server responds withAAA reply messages, containing the LMA address, to n-MAG. Then, n-MAG will sendProxy Binding Update (PBU) messages to LMA for each body sensor. Now, LMA will perform the AAA query operation with AAA server by exchangingAAA query andreply messages for each sensor. After that, LMA sendsProxy Binding Ack (PBA) messages to n-MAG in response to each respectivePBU message. Finally, n-MAG responds withRouter Advertisement (RA) messages to the body sensors.


#### 2.2.2. PMIP-Group [10]

The standard PMIP-based scheme has a drawback that a lot ofDeReg,PBU, andPBA messages are exchanged between LMA and MAGs (p-MAG and n-MAG) for all body sensors.To enhance this PMIP scheme [12], the PMIP-Group [10] was proposed, in which a singleDeReg message is exchanged between p-MAG and LMA by aggregating the associated messages from all sensors, as shown in Figure 2. In case of handover to n-MAG, thePBU andPBA messages are also aggregated between LMA and n-MAG. By this aggregation, the number ofPBU andPBA messages can be reduced between LMA and n-MAG.Figure 2
Existing PMIP-Group mobility schemes.


#### 2.2.3. PMIP-Coordinator [11]

The PMIP-Group [7] scheme tends to exchange manyRS/RA messages between sensors and MAGs (p-MAG and n-MAG). The PMIP-Coordinator scheme [11] was proposed for further enhancement of PMIP-Group scheme [10]. In this scheme, thecoordinator will communicate with n-MAG on behalf of the body sensors, as shown in Figure 3.Figure 3
Existing PMIP-Coordinator mobility schemes.When thecoordinator is attached to n-MAG, then it sends a singleRouter Solicitation (RS) message, which contains the associated group information, MN-IDs, and link-layer address, to n-MAG, by way of FFD at a time. Then, n-MAG responds with aRouter Advertisement (RA) message to the coordinator in response to theRS message.


## 2.1. Related Works

Reference [13] provides a survey of sensor devices and protocols on physical layer, data link layer, and radio technology aspects of body area networks. This paper also highlighted some of the design challenges and open issues on body area networks that still need to be addressed. In [14], it is shown that IPv6 over Low-power Wireless Personal Area Networks (6LoWPANs) is suitable for wireless body sensor networks because the sensors are based on IEEE 802.15.4 standard. The 6LoWPAN mobility has been an important solution in wireless body sensor networks. Most of the existing host-based mobility [7–9, 15] protocols for IPv6 are unsuitable for 6LoWPAN based wireless sensor networks, because they are tunnel based approaches, which shows that all of the mobile sensors actively participated in mobility related signaling in order to ensure the continuity of communications. The network-based approach [12, 16] is suitable to handle the mobility management of 6LoWPAN based body sensors. On behalf of sensors, the network node exchanges the mobility related signaling and there is no need to perform Duplicate Address Detection (DAD) of the IP address and thus it reduces the control signaling cost and handover latency of each sensor. In [17], the author highlighted the requirements and resources for adapting the existing solutions to 6LoWPAN based on the notion that single mobile node’s perspective is still a challenge and further researches are required. Therefore, [18] proposed a scheme to support Internet Protocol (IP) wireless sensor networks in which the packet format in ingress interface is to deal with the handoff procedure. In [17], it is also shown that multihop communications are not supported by Proxy Mobile IP (PMIP) protocol. Hence, in [19], a multihop communication scheme has been proposed in the ingress interface by using mesh routing. But this scheme is only on single mobile node perspective. So, if there is a group of mobile nodes moving around together, then this scheme [19] has no effective solution. In [20], a 6LoWPAN based mobility scheme has been proposed which depends on the dispatch types. But this scheme does not have a clear improvement on reducing handover delay. From the network-based perspective, in [21], a Network Mobility (NEMO) [10] based 6LoWPAN mobility scheme has been proposed, in which a mobile router performs the handoff and modifies the 6LoWPAN dispatch. However, this protocol overloaded the mobile router. To maintain the sessions while reducing the handover delay and signaling cost of group-based mobility in 6LoWPAN-based wireless sensor body area networks is an important issue. Therefore, [22] considered lots of correlated sensor nodes moving together and performed handoff together at the same time in PMIPv6 environment. The Local Mobility Anchor (LMA) calculates the SNR value for each sensor and makes a group of sensors with similar SNR values. This protocol sends Proxy Binding Ack (PBA) per group which can reduce the handoff signaling cost and save some additional unnecessary handoff messages such as Proxy Binding Update (PBU) and deregistration PBU (DeReg PBU). However, this protocol does not reduce the Router Solicitation (RS) and Router Advertisement (RA) messages in case body sensors move in the PMIPv6 domain together. Therefore, this protocol is not suitable for the 6LoWPAN-based wireless sensor body network. So, in [23], network architecture is proposed which integrates NEMO and 6LoWPAN. The mechanism of group mobility management and the signaling process containing the registration at the home network, association negotiation, handoff between different access routers, and packet routing are discussed. However, this protocol increases the burden of the sensor router due to connection and support for other normal sensor nodes inside the group. This protocol is designed for MIPv6, not for PMIPv6.


## 2.2. Existing Group-Based Mobility Schemes for Comparison

### 2.2.1. PMIP [12]

In this scheme, the standard PMIP is used for the group-based mobility support [11]. As shown in Figure 1, when a set of body sensors are detached from a previous MAG (p-MAG), the p-MAG sendsderegistration (DeReg) messages to LMA for each body sensor. When the body sensors are attached to a new MAG (n-MAG), each body sensor sends aRouter Solicitation (RS) message to n-MAG via thecoordinator and Full-Function Device (FFD) which are preconfigured in the 6LoWPAN network [6].Figure 1
Existing PMIP mobility schemes.Upon reception of RS messages from body sensors, n-MAG will send theAuthentication-Authorization-Accounting (AAA) query messages for authentication for all body sensors. After authentication, AAA server responds withAAA reply messages, containing the LMA address, to n-MAG. Then, n-MAG will sendProxy Binding Update (PBU) messages to LMA for each body sensor. Now, LMA will perform the AAA query operation with AAA server by exchangingAAA query andreply messages for each sensor. After that, LMA sendsProxy Binding Ack (PBA) messages to n-MAG in response to each respectivePBU message. Finally, n-MAG responds withRouter Advertisement (RA) messages to the body sensors.


### 2.2.2. PMIP-Group [10]

The standard PMIP-based scheme has a drawback that a lot ofDeReg,PBU, andPBA messages are exchanged between LMA and MAGs (p-MAG and n-MAG) for all body sensors.To enhance this PMIP scheme [12], the PMIP-Group [10] was proposed, in which a singleDeReg message is exchanged between p-MAG and LMA by aggregating the associated messages from all sensors, as shown in Figure 2. In case of handover to n-MAG, thePBU andPBA messages are also aggregated between LMA and n-MAG. By this aggregation, the number ofPBU andPBA messages can be reduced between LMA and n-MAG.Figure 2
Existing PMIP-Group mobility schemes.


### 2.2.3. PMIP-Coordinator [11]

The PMIP-Group [7] scheme tends to exchange manyRS/RA messages between sensors and MAGs (p-MAG and n-MAG). The PMIP-Coordinator scheme [11] was proposed for further enhancement of PMIP-Group scheme [10]. In this scheme, thecoordinator will communicate with n-MAG on behalf of the body sensors, as shown in Figure 3.Figure 3
Existing PMIP-Coordinator mobility schemes.When thecoordinator is attached to n-MAG, then it sends a singleRouter Solicitation (RS) message, which contains the associated group information, MN-IDs, and link-layer address, to n-MAG, by way of FFD at a time. Then, n-MAG responds with aRouter Advertisement (RA) message to the coordinator in response to theRS message.


## 2.2.1. PMIP [12]

In this scheme, the standard PMIP is used for the group-based mobility support [11]. As shown in Figure 1, when a set of body sensors are detached from a previous MAG (p-MAG), the p-MAG sendsderegistration (DeReg) messages to LMA for each body sensor. When the body sensors are attached to a new MAG (n-MAG), each body sensor sends aRouter Solicitation (RS) message to n-MAG via thecoordinator and Full-Function Device (FFD) which are preconfigured in the 6LoWPAN network [6].Figure 1
Existing PMIP mobility schemes.Upon reception of RS messages from body sensors, n-MAG will send theAuthentication-Authorization-Accounting (AAA) query messages for authentication for all body sensors. After authentication, AAA server responds withAAA reply messages, containing the LMA address, to n-MAG. Then, n-MAG will sendProxy Binding Update (PBU) messages to LMA for each body sensor. Now, LMA will perform the AAA query operation with AAA server by exchangingAAA query andreply messages for each sensor. After that, LMA sendsProxy Binding Ack (PBA) messages to n-MAG in response to each respectivePBU message. Finally, n-MAG responds withRouter Advertisement (RA) messages to the body sensors.


## 2.2.2. PMIP-Group [10]

The standard PMIP-based scheme has a drawback that a lot ofDeReg,PBU, andPBA messages are exchanged between LMA and MAGs (p-MAG and n-MAG) for all body sensors.To enhance this PMIP scheme [12], the PMIP-Group [10] was proposed, in which a singleDeReg message is exchanged between p-MAG and LMA by aggregating the associated messages from all sensors, as shown in Figure 2. In case of handover to n-MAG, thePBU andPBA messages are also aggregated between LMA and n-MAG. By this aggregation, the number ofPBU andPBA messages can be reduced between LMA and n-MAG.Figure 2
Existing PMIP-Group mobility schemes.


## 2.2.3. PMIP-Coordinator [11]

The PMIP-Group [7] scheme tends to exchange manyRS/RA messages between sensors and MAGs (p-MAG and n-MAG). The PMIP-Coordinator scheme [11] was proposed for further enhancement of PMIP-Group scheme [10]. In this scheme, thecoordinator will communicate with n-MAG on behalf of the body sensors, as shown in Figure 3.Figure 3
Existing PMIP-Coordinator mobility schemes.When thecoordinator is attached to n-MAG, then it sends a singleRouter Solicitation (RS) message, which contains the associated group information, MN-IDs, and link-layer address, to n-MAG, by way of FFD at a time. Then, n-MAG responds with aRouter Advertisement (RA) message to the coordinator in response to theRS message.


## 3. Distributed Group-Based Mobility Management Scheme

This section first introduces the network model of the proposed scheme and then describes the initial registration and handover operations.


### 3.1. Network Model

Figure4 shows the network model for the proposed scheme. We consider a group of IPv6 over Low-power Wireless Personal Area Network (6LoWPAN) sensors attached to the human body. One of them acts as a coordinator, and only the coordinator can exchange the control signaling messages with the Mobile Access Gateway (MAG) on behalf of the other sensors. The 6LoWPAN domain contains a Full-Function Device (FFD). In the proposed scheme, the Local Mobility Anchor (LMA) function is implemented by each MAG, and the handover operation is performed between two neighboring MAGs without the help of LMA for the group of sensors. Each MAG maintains the information of the group of sensors and aggregates theAuthentication-Authorization-Accounting (AAA) query messages to the AAA server in the authentication process. Each MAG does not perform the binding update and deregistration operation with LMA, since it has the LMA functionality.Figure 4
Network model for the proposed scheme.Initially, the coordinator communicates with the correspondent node (CN) in the previous Mobile Access Gateway (p-MAG) domain, and then it moves to a new Mobile Access Gateway (n-MAG) by handover.


### 3.2. Initial Registration

The aim of the registration phase is to reduce the amount of control messages. Figure5 illustrates the initial registration of the proposed scheme. When a group of body sensors enter a PMIP domain and the coordinator is attached to MAG/LMA, it sends an aggregatedRouter Solicitation (RS) message, containing the information on group, MN-IDs, and Link-Layer Addresses (LLAs), to MAG/LMA (Step1).Figure 5
Initial registration.Upon reception of thisRS message from the coordinator, MAG/LMA sends an aggregatedAAA querymessage with all LLAs for authentication to the AAA server. The aggregatedAAA query message is different from the previous schemes, in that it contains LLAs of a group of sensors.After authentication, the AAA server responds with a “single”AAA reply message to MAG/LMA (Steps2 and 3). After that, MAG initiates the DHCP solicitation procedure to request home network prefixes (HNPs) for the body sensors one by one. Then, the DHCP server replies with the unique HNPs for each body sensor. The MAG creates the binding cache entry; store the home network prefix information. The DHCP server also configures the respective Home-of-Address (HoA) from those prefixes and sends it to MAG. Then, the MAG/LMA responds to the coordinator with an RA message as a response to theRS message (Step4).


### 3.3. Handover Operations

The body sensors perform active scans periodically with nearby FFDs by sending a beacon request. The nearby FFDs receive the beacon request from the body sensors and advertise the beacon message containing their MAG-IDs to the body sensors. The body sensors receive the beacon message and decide whether it still resides in the same MAG or has moved to another MAG by comparing the current MAG-IDs with the previous MAG-IDs. If the current MAG-ID and previous MAG-ID are the same, then the movement represents intra-PAN mobility. On the other hand, if the current MAG-ID is different from the previous MAG-ID, then the body sensors are able to detect its movement from the old MAG to the new MAG.Figure6 shows the detailed signaling flow for the handover procedure. We now assume that the coordinator changes its point of attachment in the same network domain. When the coordinator is detached from p-MAG/LMA and attached to n-MAG/LMA, then the coordinator sends an aggregatedRS message to n-MAG/LMA (Step1). After that, n-MAG/LMA will exchange the aggregatedAAA query andreply messages with AAA server (Steps2 and 3). After authentication, n-MAG sends aProxy Binding Update (PBU) message to p-MAG/LMA for handover control (Step4). Now, n-MAG/LMA obtains the location of p-MAG/LMA from theRS message. After that, the p-MAG/LMA responds withProxy Binding Ack (PBA) to n-MAG/LMA (Step5). ThePBA message shall include the information of CN-MAG/LMA address, which is recorded into the mapping table of p-MAG/LMA. So, the handover tunnel is established between p-MAG/LMA and n-MAG/LMA for data forwarding. After establishment of handover tunnel, n-MAG responds to the coordinator with aRouter Advertisement (RA) message (Step6).Figure 6
Handover operations.Now, n-MAG/LMA sends aPBU message to CN-MAG/LMA for route optimization (Step7). On reception of thePBU message, CN-MAG/LMA will update its mapping table and send aPBA to n-MAG/LMA (Step8). n-MAG/LMA and CN-MAG/LMA will now use the optimized route.


## 3.1. Network Model

Figure4 shows the network model for the proposed scheme. We consider a group of IPv6 over Low-power Wireless Personal Area Network (6LoWPAN) sensors attached to the human body. One of them acts as a coordinator, and only the coordinator can exchange the control signaling messages with the Mobile Access Gateway (MAG) on behalf of the other sensors. The 6LoWPAN domain contains a Full-Function Device (FFD). In the proposed scheme, the Local Mobility Anchor (LMA) function is implemented by each MAG, and the handover operation is performed between two neighboring MAGs without the help of LMA for the group of sensors. Each MAG maintains the information of the group of sensors and aggregates theAuthentication-Authorization-Accounting (AAA) query messages to the AAA server in the authentication process. Each MAG does not perform the binding update and deregistration operation with LMA, since it has the LMA functionality.Figure 4
Network model for the proposed scheme.Initially, the coordinator communicates with the correspondent node (CN) in the previous Mobile Access Gateway (p-MAG) domain, and then it moves to a new Mobile Access Gateway (n-MAG) by handover.


## 3.2. Initial Registration

The aim of the registration phase is to reduce the amount of control messages. Figure5 illustrates the initial registration of the proposed scheme. When a group of body sensors enter a PMIP domain and the coordinator is attached to MAG/LMA, it sends an aggregatedRouter Solicitation (RS) message, containing the information on group, MN-IDs, and Link-Layer Addresses (LLAs), to MAG/LMA (Step1).Figure 5
Initial registration.Upon reception of thisRS message from the coordinator, MAG/LMA sends an aggregatedAAA querymessage with all LLAs for authentication to the AAA server. The aggregatedAAA query message is different from the previous schemes, in that it contains LLAs of a group of sensors.After authentication, the AAA server responds with a “single”AAA reply message to MAG/LMA (Steps2 and 3). After that, MAG initiates the DHCP solicitation procedure to request home network prefixes (HNPs) for the body sensors one by one. Then, the DHCP server replies with the unique HNPs for each body sensor. The MAG creates the binding cache entry; store the home network prefix information. The DHCP server also configures the respective Home-of-Address (HoA) from those prefixes and sends it to MAG. Then, the MAG/LMA responds to the coordinator with an RA message as a response to theRS message (Step4).


## 3.3. Handover Operations

The body sensors perform active scans periodically with nearby FFDs by sending a beacon request. The nearby FFDs receive the beacon request from the body sensors and advertise the beacon message containing their MAG-IDs to the body sensors. The body sensors receive the beacon message and decide whether it still resides in the same MAG or has moved to another MAG by comparing the current MAG-IDs with the previous MAG-IDs. If the current MAG-ID and previous MAG-ID are the same, then the movement represents intra-PAN mobility. On the other hand, if the current MAG-ID is different from the previous MAG-ID, then the body sensors are able to detect its movement from the old MAG to the new MAG.Figure6 shows the detailed signaling flow for the handover procedure. We now assume that the coordinator changes its point of attachment in the same network domain. When the coordinator is detached from p-MAG/LMA and attached to n-MAG/LMA, then the coordinator sends an aggregatedRS message to n-MAG/LMA (Step1). After that, n-MAG/LMA will exchange the aggregatedAAA query andreply messages with AAA server (Steps2 and 3). After authentication, n-MAG sends aProxy Binding Update (PBU) message to p-MAG/LMA for handover control (Step4). Now, n-MAG/LMA obtains the location of p-MAG/LMA from theRS message. After that, the p-MAG/LMA responds withProxy Binding Ack (PBA) to n-MAG/LMA (Step5). ThePBA message shall include the information of CN-MAG/LMA address, which is recorded into the mapping table of p-MAG/LMA. So, the handover tunnel is established between p-MAG/LMA and n-MAG/LMA for data forwarding. After establishment of handover tunnel, n-MAG responds to the coordinator with aRouter Advertisement (RA) message (Step6).Figure 6
Handover operations.Now, n-MAG/LMA sends aPBU message to CN-MAG/LMA for route optimization (Step7). On reception of thePBU message, CN-MAG/LMA will update its mapping table and send aPBA to n-MAG/LMA (Step8). n-MAG/LMA and CN-MAG/LMA will now use the optimized route.


## 4. Performance Analysis

For performance analysis, we compare the registration and handover delays for the four candidate mobility schemes: PMIP, PMIP-Group, PMIP-Coordinator, and the proposed scheme.


### 4.1. Analysis Model

We consider a network illustrated in Figure7, in which each wired/wireless link is represented by bandwidth, latency, and average queuing delay. We adopt a generic model for Multiple Access Control (MAC) scheme to focus on the analysis of registration delay and handover delay associated with the proposed mobility scheme.Figure 7
Network model for performance analysis.We summarize the notations used in our analysis in the Parameters Used for Analysis.In Figure7, we denote by Tx-y(S) the transmission delay of a message with size S sent from x to y via the “wireless” link, where each message can experience the failure at the probability of q by using “iid” error model. Then, Tx-y(S) can be expressed as Tx-y(S)=[1/(1-q)]×[(S/Bwl)+Lwl]. In the meantime, we denote by Tx-y(S,Hx-y) the transmission delay of a message with size S sent from x to y via the “wired” link, where Hx-y represents the number of wired hops between node x and node y. Then, Tx-y(S,Hx-y) is expressed as Tx-y(S,Hx-y)=Hx-y×[(S/Bw)+Lw+Tq].


### 4.2. Registration Delay (RD)

As shown in Figure1, when the body sensors are attached to a MAG, they sendRS messages to MAG via the coordinator and FFD. After that, MAG performs the AAA operations for authentication for all body sensors. Then, MAG performs thePBU operation with LMA for all body sensors. Now, LMA performs the AAA operations with AAA server for all body sensors. After authentication, LMA responds with thePBA message to MAG. Now, MAG will respond with theRA messages to all of the body sensors. Accordingly, we get the RD of PMIP as follows:(1)RDPMIP=NS×2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+2TMAG-LMASc+2TLMA-AAASc.As shown in Figure2, the whole operations of PMIP-Group are the same as those of PMIP. Different from PMIP, the PMIP-Group scheme uses the aggregatedPBU andPBA messages between LMA and MAGs. Accordingly, we get the RD of PMIP-Group as follows:(2)RDPMIP-Group=NS×2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+2TLMA-AAASc+2TMAG-LMASc.As shown in Figure3, the PMIP-Coordinator uses the aggregatedRS andRA messages between MAG and the coordinator. Thus, we get the RD of PMIP-Coordinator as (3)RDPMIP-Coordinator=2TC-FFDSc+2TFFD-MAGSc+2TMAG-LMASc+NS×2TMAG-AAASc+2TLMA-AAASc.In the proposed scheme, when the coordinator is attached to n-MAG, then it sends an aggregatedRS message on behalf of all body sensors to n-MAG by way of FFD. After that, n-MAG performs the AAA operations with AAA server. Based on this, n-MAG performs the authentication process and responds with an aggregatedRA message to the coordinator. Thus, we get the RD of the proposed scheme as follows:(4)RDProposed  Scheme=2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc.


### 4.3. Handover Delay (HD)

The handover delay is defined as the gap between the time that body sensors cannot receive the packets from p-MAG and the time that body sensors receive the first packet from n-MAG.As shown in Figure1, when the body sensors are detached from p-MAG, then p-MAG will sendDeReg messages to LMA for body sensors. When the body sensors are attached to n-MAG, they sendRS messages to n-MAG by way of the coordinator and FFD. After that, n-MAG performs the AAA query and reply operations with AAA server for authentication for all body sensors, and then n-MAG performs thePBU operations with LMA for all body sensors. Now, LMA performs the AAA query/reply operations with AAA server for all body sensors. After authentication, LMA responds with thePBA message to n-MAG. The handover tunnel will be established between n-MAG and LMA. After the tunnel establishment, n-MAG responds with theRA messages to all body sensors. Accordingly, we get the HD of PMIP as follows:(5)HDPMIP=NS×2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+4TMAG-LMASc+2TLMA-AAASc+TMAG-LMASd.As shown in Figure2, the PMIP-Group scheme uses the aggregatedDeReg andPBU/PBA messages. Accordingly, we get the HD of PMIP-Group as follows:(6)HDPMIP-Group=NS×2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+2TLMA-AAASc+4TMAG-LMASc+TMAG-LMASd.As shown in Figure3, the PMIP-Coordinator scheme uses the aggregatedRS andRA messages between MAG and the coordinator. Accordingly, we can get the HD of PMIP- Coordinator as follows:(7)HDPMIP-Coordinator=2TC-FFDSc+2TFFD-MAGSc+4TMAG-LMASc+NS×2TMAG-AAASc+2TLMA-AAASc+TMAG-LMASd.In the proposed scheme, when the coordinator is attached to n-MAG, it sends an aggregatedRS message on behalf of body sensors to n-MAG by way of FFD. After that, n-MAG performs the AAA operations with the AAA server by aggregation. Then, n-MAG exchanges thePBU andPBA messages with p-MAG for establishment of a handover tunnel. After tunnel establishment, n-MAG responds with an aggregatedRA message to the coordinator. Accordingly, we get the HD of the proposed scheme as follows:(8)HDProposed  Scheme=2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+2TMAG-MAGSc+TMAG-MAGSd.


## 4.1. Analysis Model

We consider a network illustrated in Figure7, in which each wired/wireless link is represented by bandwidth, latency, and average queuing delay. We adopt a generic model for Multiple Access Control (MAC) scheme to focus on the analysis of registration delay and handover delay associated with the proposed mobility scheme.Figure 7
Network model for performance analysis.We summarize the notations used in our analysis in the Parameters Used for Analysis.In Figure7, we denote by Tx-y(S) the transmission delay of a message with size S sent from x to y via the “wireless” link, where each message can experience the failure at the probability of q by using “iid” error model. Then, Tx-y(S) can be expressed as Tx-y(S)=[1/(1-q)]×[(S/Bwl)+Lwl]. In the meantime, we denote by Tx-y(S,Hx-y) the transmission delay of a message with size S sent from x to y via the “wired” link, where Hx-y represents the number of wired hops between node x and node y. Then, Tx-y(S,Hx-y) is expressed as Tx-y(S,Hx-y)=Hx-y×[(S/Bw)+Lw+Tq].


## 4.2. Registration Delay (RD)

As shown in Figure1, when the body sensors are attached to a MAG, they sendRS messages to MAG via the coordinator and FFD. After that, MAG performs the AAA operations for authentication for all body sensors. Then, MAG performs thePBU operation with LMA for all body sensors. Now, LMA performs the AAA operations with AAA server for all body sensors. After authentication, LMA responds with thePBA message to MAG. Now, MAG will respond with theRA messages to all of the body sensors. Accordingly, we get the RD of PMIP as follows:(1)RDPMIP=NS×2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+2TMAG-LMASc+2TLMA-AAASc.As shown in Figure2, the whole operations of PMIP-Group are the same as those of PMIP. Different from PMIP, the PMIP-Group scheme uses the aggregatedPBU andPBA messages between LMA and MAGs. Accordingly, we get the RD of PMIP-Group as follows:(2)RDPMIP-Group=NS×2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+2TLMA-AAASc+2TMAG-LMASc.As shown in Figure3, the PMIP-Coordinator uses the aggregatedRS andRA messages between MAG and the coordinator. Thus, we get the RD of PMIP-Coordinator as (3)RDPMIP-Coordinator=2TC-FFDSc+2TFFD-MAGSc+2TMAG-LMASc+NS×2TMAG-AAASc+2TLMA-AAASc.In the proposed scheme, when the coordinator is attached to n-MAG, then it sends an aggregatedRS message on behalf of all body sensors to n-MAG by way of FFD. After that, n-MAG performs the AAA operations with AAA server. Based on this, n-MAG performs the authentication process and responds with an aggregatedRA message to the coordinator. Thus, we get the RD of the proposed scheme as follows:(4)RDProposed  Scheme=2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc.


## 4.3. Handover Delay (HD)

The handover delay is defined as the gap between the time that body sensors cannot receive the packets from p-MAG and the time that body sensors receive the first packet from n-MAG.As shown in Figure1, when the body sensors are detached from p-MAG, then p-MAG will sendDeReg messages to LMA for body sensors. When the body sensors are attached to n-MAG, they sendRS messages to n-MAG by way of the coordinator and FFD. After that, n-MAG performs the AAA query and reply operations with AAA server for authentication for all body sensors, and then n-MAG performs thePBU operations with LMA for all body sensors. Now, LMA performs the AAA query/reply operations with AAA server for all body sensors. After authentication, LMA responds with thePBA message to n-MAG. The handover tunnel will be established between n-MAG and LMA. After the tunnel establishment, n-MAG responds with theRA messages to all body sensors. Accordingly, we get the HD of PMIP as follows:(5)HDPMIP=NS×2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+4TMAG-LMASc+2TLMA-AAASc+TMAG-LMASd.As shown in Figure2, the PMIP-Group scheme uses the aggregatedDeReg andPBU/PBA messages. Accordingly, we get the HD of PMIP-Group as follows:(6)HDPMIP-Group=NS×2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+2TLMA-AAASc+4TMAG-LMASc+TMAG-LMASd.As shown in Figure3, the PMIP-Coordinator scheme uses the aggregatedRS andRA messages between MAG and the coordinator. Accordingly, we can get the HD of PMIP- Coordinator as follows:(7)HDPMIP-Coordinator=2TC-FFDSc+2TFFD-MAGSc+4TMAG-LMASc+NS×2TMAG-AAASc+2TLMA-AAASc+TMAG-LMASd.In the proposed scheme, when the coordinator is attached to n-MAG, it sends an aggregatedRS message on behalf of body sensors to n-MAG by way of FFD. After that, n-MAG performs the AAA operations with the AAA server by aggregation. Then, n-MAG exchanges thePBU andPBA messages with p-MAG for establishment of a handover tunnel. After tunnel establishment, n-MAG responds with an aggregatedRA message to the coordinator. Accordingly, we get the HD of the proposed scheme as follows:(8)HDProposed  Scheme=2TC-FFDSc+2TFFD-MAGSc+2TMAG-AAASc+2TMAG-MAGSc+TMAG-MAGSd.


## 5. Numerical Results and Discussion

Based on the analysis given so far, we now compare the performances of the candidate schemes.For numerical analysis, by referring to [24], the default value of each parameter is configured as follows: HMAG-LMA=HMAG-MAG=5, HMAG-AAA=HLMA-AAA=5, Lwl = 10 ms, Lw = 2 ms, q = 0.5, Tq = 5 ms, NS = 10, Sc = 96 bytes, Sd = 200 bytes, Bwl =11 Mbps, and Bw =100 Mbps. Among these parameters, we note that Lwl, Tq, and Ns may depend on the network conditions. Thus, we will compare the performances of candidate schemes by varying those parameter values.


### 5.1. Registration Delay

Figure8 shows the impact of wireless link delay (Lwl) on registration delay. From the figure, we can see that the registration delay linearly increases as Lwl gets larger, for all candidate schemes. It is shown that the proposed scheme gives better performance than the existing schemes. This is because the proposed scheme uses the LMA functionality over MAG, and thus the PBU and PBA operations are not required between LMA and MAG. In the proposed scheme, the MAG also performs aggregated AAA query and reply operations.Figure 8
Impact ofLwl on registration delay.Figure9 compares the registration delay for different average queuing delay (Tq) at each node. It is shown in the figure that the registration delay linearly increases as Tq gets larger, for all candidate schemes. We can see that the proposed scheme gives the best performance among the candidate schemes. This is because each MAG implements the LMA functionality.Figure 9
Impact ofTq on registration delay.Figure10 illustrates the impact of the number of sensors (Ns) on registration delay. In the figure, the handover delay linearly increases as Ns gets larger, for the existing schemes. It is shown that the proposed scheme is not affected by Ns. This is because the amounts of the AAA query and reply messages for each registration are constant no matter what the number of the body sensors is. Besides, the proposed scheme also uses the LMA functionality over MAG, and thus the PBU and PBA operations are not required between LMA and MAG. Hence, each body sensor needs to transmit a smaller amount of control messages and incurs lower registration delay as the number of body sensors increases.Figure 10
Impact ofNs on registration delay.


### 5.2. Handover Delay

Figure11 illustrates the impact of wireless link delay (Lwl) on handover delay. In the figure, the handover delay linearly increases as Lwl gets larger, for all candidate schemes. It is shown that the proposed scheme gives better performance than the existing schemes. This is because the LMA function is implemented by each MAG and the handover operation is performed between two neighboring MAGs without the help of LMA.Figure 11
Impact ofLwl on handover delay.Figure12 shows the impact of average queuing delay (Tq) on handover delay. It is shown in the figure that the handover delay linearly increases as Tq gets larger, for all the candidate schemes. We can see that the proposed scheme gives the best performance among the candidate schemes.Figure 12
Impact ofTq on handover delay.Figure13 shows the impact of the number of sensors (Ns) on handover delay. In the figure, the handover delay linearly increases as Ns gets larger, for the existing schemes. It is shown that the proposed scheme is not affected by Ns. This is because the amounts of the AAA query and reply messages for each handoff are constant no matter what the number of the body sensors is. Besides, the proposed scheme also implemented the LMA functionality over MAG, and the handover operation is performed between two neighboring MAGs without the help of LMA and thus the deregistration operations are not required between LMA and p-MAG. Hence, each body sensor needs to transmit a smaller amount of control messages and incurs lower handover delay as the number of body sensors increases.Figure 13
Impact ofNs on handover delay.


## 5.1. Registration Delay

Figure8 shows the impact of wireless link delay (Lwl) on registration delay. From the figure, we can see that the registration delay linearly increases as Lwl gets larger, for all candidate schemes. It is shown that the proposed scheme gives better performance than the existing schemes. This is because the proposed scheme uses the LMA functionality over MAG, and thus the PBU and PBA operations are not required between LMA and MAG. In the proposed scheme, the MAG also performs aggregated AAA query and reply operations.Figure 8
Impact ofLwl on registration delay.Figure9 compares the registration delay for different average queuing delay (Tq) at each node. It is shown in the figure that the registration delay linearly increases as Tq gets larger, for all candidate schemes. We can see that the proposed scheme gives the best performance among the candidate schemes. This is because each MAG implements the LMA functionality.Figure 9
Impact ofTq on registration delay.Figure10 illustrates the impact of the number of sensors (Ns) on registration delay. In the figure, the handover delay linearly increases as Ns gets larger, for the existing schemes. It is shown that the proposed scheme is not affected by Ns. This is because the amounts of the AAA query and reply messages for each registration are constant no matter what the number of the body sensors is. Besides, the proposed scheme also uses the LMA functionality over MAG, and thus the PBU and PBA operations are not required between LMA and MAG. Hence, each body sensor needs to transmit a smaller amount of control messages and incurs lower registration delay as the number of body sensors increases.Figure 10
Impact ofNs on registration delay.


## 5.2. Handover Delay

Figure11 illustrates the impact of wireless link delay (Lwl) on handover delay. In the figure, the handover delay linearly increases as Lwl gets larger, for all candidate schemes. It is shown that the proposed scheme gives better performance than the existing schemes. This is because the LMA function is implemented by each MAG and the handover operation is performed between two neighboring MAGs without the help of LMA.Figure 11
Impact ofLwl on handover delay.Figure12 shows the impact of average queuing delay (Tq) on handover delay. It is shown in the figure that the handover delay linearly increases as Tq gets larger, for all the candidate schemes. We can see that the proposed scheme gives the best performance among the candidate schemes.Figure 12
Impact ofTq on handover delay.Figure13 shows the impact of the number of sensors (Ns) on handover delay. In the figure, the handover delay linearly increases as Ns gets larger, for the existing schemes. It is shown that the proposed scheme is not affected by Ns. This is because the amounts of the AAA query and reply messages for each handoff are constant no matter what the number of the body sensors is. Besides, the proposed scheme also implemented the LMA functionality over MAG, and the handover operation is performed between two neighboring MAGs without the help of LMA and thus the deregistration operations are not required between LMA and p-MAG. Hence, each body sensor needs to transmit a smaller amount of control messages and incurs lower handover delay as the number of body sensors increases.Figure 13
Impact ofNs on handover delay.


## 6. Conclusions

In this paper, we proposed a distributed group-based mobility management scheme in 6LoWPAN-based wireless body area networks. In the proposed scheme, the LMA function is implemented by each MAG, and the handover operation is performed between the two neighboring MAGs. Furthermore, the MAG aggregates the AAA query messages for the group of moving sensors. From the numerical results, we see that the proposed scheme can provide better performance than the existing schemes in terms of registration and handover delays.



---

*Source: 4180801-2017-05-23.xml*