# An ID/Locator Separation Based Group Mobility Management in Wireless Body Area Network

Authors: Moneeb Gohar; Jin-Ghoo Choi; Seok-Joo Koh
Journal: Journal of Sensors
 (2015)

---

## Abstract

Mobility management in wireless sensor network is the most important factor to be considered for applications such as healthcare system. Recently, Identifier (ID)/Locator (LOC) separation based mobility management scheme has been proposed for wireless sensor network. However, it does not perform well in group-based mobility management in wireless body area network, and thus it tends to induce large registration, packet delivery, and handover delays. To overcome these limitations, we propose a group-based mobility management scheme based on ID/LOC separation concept for ID-based communications with location-based routing to reduce the number of control messages. In the proposed scheme, each sensor device has a globally unique device identifier (GDID) which contains the information of its home network domain. For handover support, each access gateway maintains its home GDID register (HGR) and visiting GDID register (VGR) which are used to keep the GDID-locator (LOC) mappings for primary mobile devices in the distributed manner. Besides, in the proposed scheme, only the coordinator will send Router Solicitation and Router Advertisement messages to reduce the control messages further. By numerical analysis, we show that the proposed scheme can significantly reduce the registration, packet delivery, and handover delays, compared to the existing schemes.


---

## Body

## 1. Introduction

Wireless body area networks (WBANs) are emerging as an important part of the daily life for ambient assistive living. A WBAN typically consists of lightweight, low power sensors that operate in the proximity of the human body. These sensors can be attached to human body or clothes [1–3] and can be used to measure the parameters associated with human body, typically observing physiological signals emanating from different body organs, body motions, and the surrounding environment. The measured values can be gathered and transmitted to the main server by using the IPv6 over low power wireless personal area network (6LoWPAN) [4, 5], in which it is possible to connect wireless sensor nodes to IPv6 networks. In mobile environments, it is required to provide these sensor nodes with mobility management, such as handover control.Many IPv6-based mobility management protocols have attracted much interest in 6LoWPAN networks. We can classify the protocols into the host-based schemes and the network-based schemes. For example, Mobile IPv6 (MIPv6) is a host-based protocol [6] and Proxy Mobile IPv6 (PMIPv6) is a network-based protocol [7]. In host-based mobility schemes, the sensor exchangesBinding Update (BU) andBinding Acknowledgment (BA) messages with its Home Agent (HA), when it moves from one mobility domain to another. On the other hand, in network-based mobility schemes, when a sensor changes the domain, the protocols do not require any mobility-related signaling. Instead, a mobile access gateway (MAG) is responsible for detecting movement and exchanging signaling messages on behalf of the sensors. It is noted that PMIPv6 can be considered as the most suitable mobility scheme in 6LoWPAN-WBAN. However, the conventional PMIPv6 [7] scheme has a drawback that a lot ofProxy Binding Update (PBU) andProxy Binding Ack (PBA) messages should be exchanged between LMA and MAGs for all body sensors. To enhance this conventional PMIP scheme, the PMIP-Group [8] was proposed, in which a singleDe-Registration (DeReg) message is exchanged between MAG and LMA by aggregating the associated messages from all sensors. The PMIP-Coordinator scheme [9] was proposed for further enhancement of group-based mobility support in 6LoWPAN-based WBAN network. In this scheme, theCoordinator will communicate with MAG on behalf of the body sensor. The PMIP-Coordinator still has large registration and handover delay.The Identifier (ID)/Locator (LOC) based mobility management scheme has been proposed for 6LoWPAN wireless sensor network [10]. In this scheme each primary mobile device (PMD) or 6LoWPAN sensor has a 128-bit global unique device identifier (GDID), which is used for end-to-end communication, and a link-layer address can be used as the access identifier (AID). Each local network domain will have a local home mobility agent and a local visited mobility agent, which are configured based on the logical overlay network that supports the distributed mapping management. However, this scheme does not perform well in group-based wireless body area network, because each sensor sendsRouter Solicitation (RS) andRouter Advertisement (RA) messages to PMD. In addition, for location update and discovery, the additional control messages are exchanged between access gateway and distributed local mapping agents. This tends to induce large registration and handover delays. For this reason, how to decrease the times of exchanging the control messages in case that a number of sensors are attached on one PMD is an important issue.To overcome these limitations, we propose a group-based mobility management scheme based on the ID/LOC separation concept. In the proposed scheme, each sensor and each primary mobile device has a globally unique device identifier (GDID) which contains the information of home network domain. For handover support, each access gateway maintains “home GDID register” and “visiting GDID register” that are used to keep the GDID-global locator (GLOC) mappings for primary mobile devices in the distributed manner. The proposed scheme also reduces the number of control messages, includingRS/RA. This is because only theCoordinator will exchangeRS/RAmessages with PMD, instead of each sensor.The rest of this paper is organized as follows. In Section2, we review the existing ID/LOC schemes for 6LoWPAN-WBAN networks. In Section 3, we describe the proposed ID/LOC scheme in detail. The performances of the existing and proposed schemes are analyzed in Section 4 in terms of the registration delay, packet delivery delay, and the handover delay. We provide the numerical results and discuss them in Section 5. Finally, we conclude this research in Section 6.


## 2. Related Works

In conventional PMIPv6 scheme [7], a lot ofProxy Binding Update (PBU) andProxy Binding Ack (PBA) messages are exchanged between LMA and MAGs for all body sensors. To enhance this conventional PMIP scheme, the PMIP-Group [8] was proposed, in which a singleDe-Registration (DeReg)message is exchanged between MAG and LMA for all body sensors.The PMIP-Coordinator scheme [9] was proposed for further enhancement of PMIP-Group scheme. In this scheme, theCoordinator will communicate with MAG on behalf of the body sensor.As shown in Figure1, when theCoordinator is detached from previous MAG (p-MAG), a singleDeRegmessage is exchanged between p-MAG and LMA by aggregating the associated messages from all sensors.Figure 1
PMIP-Coordinator.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 PMD at a time. Upon reception ofRS 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 send aggregatedProxy Binding Update (PBU) message to LMA for all body sensors. Now, LMA will perform the AAA query operation with AAA server by exchangingAAA query andreplymessages for each sensor. After that, LMA sends aggregatedProxy Binding ACK (PBA) message to n-MAG in response to the respective aggregatedPBU message. Then, n-MAG responds with aRouter Advertisement (RA) message to theCoordinator in response to theRS message.If PMD wants to communicate with the corresponding PMD (C-PMD), then PMD will send a data packet to LMA directly and LMA will forward the data packet to corresponding MAG (c-MAG) and further to C-PMD.The ID/LOC-based mobility management scheme has been proposed for 6LoWPAN wireless sensor network [10]. In this paper, we will consider it for 6LoWPAN-based wireless body area network. In the ID/LOC scheme, each primary mobile device (PMD), such as smartphone or tablet PC and 6LoWPAN sensor, has a 128-bit globally unique device identifier (GDID), which is used for end-to-end communication, and a link-layer addresses can be used as the access identifier (AID). Each local network domain will have the home and visited distributed local mobility management agents, which are based on the logical overlay network that supports the distributed mapping management. The device ID can be generated through cryptographical generated address (CGA).As shown in Figure2, when the body sensors are attached to PMD, then all body sensors generate their IDs and sendRouter Solicitation (RS) messages to PMD. Upon reception ofRS messages from body sensors, PMD will send theLocation Update Requestto access gateway (AGW). Then, the AGW will update its GDID-global locator (GLOC) mapping table and also GDID-access identifier (AID) mapping table. After that, the AGW responds withLocation Update Response message to PMD. After location update, the AGW also performs theLocation Update Request and Responsemessages with distributed local mapping agent (DLMA) for adding GDID-GLOC mapping for global communication.Figure 2
ID-LOC registration and handover operations.When PMD moves from the previous access gateway (p-AGW) to a new access gateway (n-AGW), the PMD will sendAttachment Trigger to n-AGW. AfterAttachment Trigger, n-AGW sendsDevice Context Request message to p-AGW. Then, p-AGW will send theLocation Update Request message to home DLMA (H-DLMA). The H-DLMA updates the information and responds withLocation Update Response message to p-AGW. After receiving theLocation Update Response, the p-AGW will sendDevice Context Reply message to n-AGW.As shown in Figure3, PMD wants to communicate with a particular PMD that is residing in the corresponding gateway (c-AGW). The PMD will send aDevice ID Request message to AGW. After receiving theDevice ID Request from PMD, the AGW will look up its mapping table, whether the request ID exists or not. If there is no information, then AGW sends aLocation Discovery Request message to corresponding DLMA (C-DLMA). The C-DLMA will look up its mapping table and reply with aLocation Discovery Response message to AGW. Upon the receipt of theLocation Discovery Response message from the CDLMA, the AGW will add the information in its mapping table. Then, the AGW sendsRoute Setup Request message to c-AGW. After that, the c-AGW performs theGDID Discovery Query and Reply messages with corresponding PMD (C-PMD). After that, the c-AGW responds withRoute Setup Complete message to AGW. After that, the AGW responds withDevice ID Response message to PMD. Now, the data packets will be forwarded to C-PMD via AGW and c-AGW.Figure 3
ID-LOC packet delivery operations.


## 3. Proposed Scheme

In this section, we describe the proposed ID/LOC-based 6LoWPAN-WBAN mobility management scheme. To this end, first we need to specify the network model.


### 3.1. Network Model

The proposed ID/LOC-based 6LoWPAN wireless body area network mobility management scheme is shown in Figure4. In the model, we consider a group of 6LoWPAN sensors that are attached to human body, and one of them acts asCoordinator and only theCoordinator can exchange the control signaling messages with the primary mobile device (PMD). In the proposed scheme, each sensor or PMD has a 128-bit globally unique device identifier (GDID) [10]. The link-layer addresses can be used as the access identifier (AID). The GDID contains the information about its home network domain. As for locators, the location of PMDs is identified by local locators (LLOC) and global locators (GLOC). The local locators are the AIDs of PMDs, and it is used within the home domain. The GLOC represents the IP address of access gateways (AGW), and it is used for interdomain communication. Each AGW keeps home GDID register (HGR) and visiting GDID register (VGR). HGR keeps track of the GDID-LOC mapping information for PMDs and VGR maintain the list of GDID-LLOC mapping information for the visited PMDs.Figure 4
Network model for proposed scheme.In the proposed scheme, only one timeRouter Solicitation (RS) andRouter Advertisement (RA) messages are sent byCoordinator and thus reduce lots of control messages.Initially, the PMD communicates with correspondent PMD (C-PMD) in the previous AGW (p-AGW) domain. Now, the PMD moves to a new AGW (n-AGW) by handover. In addition, we assume that each PMD moves around only within its home domain.


### 3.2. Comparison of Existing and Proposed Schemes

Before describing the proposed scheme in detail, we compare the considered mobility management schemes in the architectural perspective in Table1.Table 1
Comparison of mobility management architectures.
Relevant protocols
PMIP-Coordinator [9]
ID-LOC-based scheme [10]
Proposed scheme
Mobility agent
LMA
DLMA, AGW
AGW
Identifier/Locators
HoA, CoA
GDID, AID, GLOC
GDID, GLOC, LLOC (AID)
RS/RA message exchange
Between coordinator and PMD (one time)
Between body sensors and PMD (each body sensor)
Between Coordinator and PMD (one time)In the viewpoint of the mobility management, PMIP-Coordinator is the centralized architectures, in which all the control and data traffic are processed by a centralized agent such as LMA. Data packets are delivered to the centralized agents first and forwarded to the corresponding host. In PMIP-Coordinator, the identifier corresponds to HoA and the locator does CoA. In PMIP-Coordinator, theCoordinator will exchangeRS/RA messages only one time with mobile access gateway (MAG) on behalf of the body sensors.In ID-LOC-based scheme, the GDID is used as identifier, and AID and GLOC are used for locators. The DLMA and AGW are used to manage the mobility of PMDs. In ID-LOC-based scheme, the body sensors exchangeRS/RA messages with PMD.On the other hand, in the proposed schemes, the GDID is used as identifier and LLOC and GLOC are used for locators. The AGW manages the mobility for PMDs. In the proposed scheme, theCoordinator exchangesRS/RA messages with PMD only one time on behalf of body sensors. The proposed scheme is described in the subsequent sections.


### 3.3. Initial Registration

The initial registration procedure of the proposed scheme is shown in Figure5.Figure 5
Initial registration.In the figure, when theCoordinator is attached to PMD, theCoordinator sends aRouter Solicitation (RS) message containing the information on the group, MN-IDs (GDID), and Link-Layer Addresses (AIDs) to PMD (Step  1). Upon reception of theRS message from theCoordinator, the PMD responds withRAmessage toCoordinator(Step  2). Then, PMD sendsLocation Update Request message to AGW. On the reception of this message, the AGW will update its home GDID register (HGR) which maintains GDID-LOC mapping table as shown in Table 2. Then, AGW responds withLocation Update Response to PMD (Steps 3 and 4).Table 2
Home GDID register (HGR).
Number
ID
LOC
Domain
1
GDID1
LLOC (AID) of PMD,
Home
2
GDID2
GLOC of AGW
Visiting
3
⋯
⋯
⋯


### 3.4. Packet Delivery Operation

In Figure6, PMD wants to communicate with a particular PMD that is residing in the corresponding gateway (c-AGW). The PMD will sendDevice ID Request message to AGW (Step  1). Next, the AGW will check whether the GDID belongs to the same domain with the corresponding PMD or not. Note that an AGW can determine this, based on GDID, since GDID contains information about its home domain. Then, AGW sendsLocation Discovery Request message to c-AGW. The c-AGW will look up its HGR mapping table and reply withLocation Discovery Response message to AGW (Steps 2 and 3). Upon the receipt of theLocation Discovery Response message from the c-AGW, the AGW will add the information in its mapping table. After that, the AGW responds withDevice ID Response message to PMD (Step  4). Now, the data packets will be forwarded to C-PMD via AGW and c-AGW.Figure 6
Packet delivery operation.


### 3.5. Handover Operation

When PMD moves from the previous access gateway (p-AGW) to a new access gateway (n-AGW) in the same home network domain, the PMD will sendAttachment Trigger to n-AGW (Step  1). AfterAttachment Trigger, the n-AGW will update its visiting GDID register (VGR) which maintains GDID-LLOC (AID) mapping table as shown in Table 3. Then, n-AGW sendsLocation Update Request message to previous AGW (p-AGW). The p-AGW will update its HGR and responds withLocation Update Response message to n-AGW (Steps  2 and 3). TheLocation Update Response message shall include the information of corresponding-AGW (c-AGW) address, which is recorded in the mapping table of p-AGW.Table 3
Visiting GDID register (VGR).
Number
ID
LLOC(in the visited domain)
Home domain
1
GDID1
LLOC1 (AID) of PMD
GLOC1(AGW of GDID1)
2
GDID2
LLOC2 (AID) of PMD
GLOC2(AGW of GDID2)
3
⋯
⋯
⋯Now, n-AGW sends aLocation Update Request message to c-AGW for route optimization. On the reception of theLocation Update Request message, c-AGW will update its mapping table and send aLocation Update Response to n-AGW. n-AGW and c-AGW will now use the optimized route (Steps 4 and 5).


## 3.1. Network Model

The proposed ID/LOC-based 6LoWPAN wireless body area network mobility management scheme is shown in Figure4. In the model, we consider a group of 6LoWPAN sensors that are attached to human body, and one of them acts asCoordinator and only theCoordinator can exchange the control signaling messages with the primary mobile device (PMD). In the proposed scheme, each sensor or PMD has a 128-bit globally unique device identifier (GDID) [10]. The link-layer addresses can be used as the access identifier (AID). The GDID contains the information about its home network domain. As for locators, the location of PMDs is identified by local locators (LLOC) and global locators (GLOC). The local locators are the AIDs of PMDs, and it is used within the home domain. The GLOC represents the IP address of access gateways (AGW), and it is used for interdomain communication. Each AGW keeps home GDID register (HGR) and visiting GDID register (VGR). HGR keeps track of the GDID-LOC mapping information for PMDs and VGR maintain the list of GDID-LLOC mapping information for the visited PMDs.Figure 4
Network model for proposed scheme.In the proposed scheme, only one timeRouter Solicitation (RS) andRouter Advertisement (RA) messages are sent byCoordinator and thus reduce lots of control messages.Initially, the PMD communicates with correspondent PMD (C-PMD) in the previous AGW (p-AGW) domain. Now, the PMD moves to a new AGW (n-AGW) by handover. In addition, we assume that each PMD moves around only within its home domain.


## 3.2. Comparison of Existing and Proposed Schemes

Before describing the proposed scheme in detail, we compare the considered mobility management schemes in the architectural perspective in Table1.Table 1
Comparison of mobility management architectures.
Relevant protocols
PMIP-Coordinator [9]
ID-LOC-based scheme [10]
Proposed scheme
Mobility agent
LMA
DLMA, AGW
AGW
Identifier/Locators
HoA, CoA
GDID, AID, GLOC
GDID, GLOC, LLOC (AID)
RS/RA message exchange
Between coordinator and PMD (one time)
Between body sensors and PMD (each body sensor)
Between Coordinator and PMD (one time)In the viewpoint of the mobility management, PMIP-Coordinator is the centralized architectures, in which all the control and data traffic are processed by a centralized agent such as LMA. Data packets are delivered to the centralized agents first and forwarded to the corresponding host. In PMIP-Coordinator, the identifier corresponds to HoA and the locator does CoA. In PMIP-Coordinator, theCoordinator will exchangeRS/RA messages only one time with mobile access gateway (MAG) on behalf of the body sensors.In ID-LOC-based scheme, the GDID is used as identifier, and AID and GLOC are used for locators. The DLMA and AGW are used to manage the mobility of PMDs. In ID-LOC-based scheme, the body sensors exchangeRS/RA messages with PMD.On the other hand, in the proposed schemes, the GDID is used as identifier and LLOC and GLOC are used for locators. The AGW manages the mobility for PMDs. In the proposed scheme, theCoordinator exchangesRS/RA messages with PMD only one time on behalf of body sensors. The proposed scheme is described in the subsequent sections.


## 3.3. Initial Registration

The initial registration procedure of the proposed scheme is shown in Figure5.Figure 5
Initial registration.In the figure, when theCoordinator is attached to PMD, theCoordinator sends aRouter Solicitation (RS) message containing the information on the group, MN-IDs (GDID), and Link-Layer Addresses (AIDs) to PMD (Step  1). Upon reception of theRS message from theCoordinator, the PMD responds withRAmessage toCoordinator(Step  2). Then, PMD sendsLocation Update Request message to AGW. On the reception of this message, the AGW will update its home GDID register (HGR) which maintains GDID-LOC mapping table as shown in Table 2. Then, AGW responds withLocation Update Response to PMD (Steps 3 and 4).Table 2
Home GDID register (HGR).
Number
ID
LOC
Domain
1
GDID1
LLOC (AID) of PMD,
Home
2
GDID2
GLOC of AGW
Visiting
3
⋯
⋯
⋯


## 3.4. Packet Delivery Operation

In Figure6, PMD wants to communicate with a particular PMD that is residing in the corresponding gateway (c-AGW). The PMD will sendDevice ID Request message to AGW (Step  1). Next, the AGW will check whether the GDID belongs to the same domain with the corresponding PMD or not. Note that an AGW can determine this, based on GDID, since GDID contains information about its home domain. Then, AGW sendsLocation Discovery Request message to c-AGW. The c-AGW will look up its HGR mapping table and reply withLocation Discovery Response message to AGW (Steps 2 and 3). Upon the receipt of theLocation Discovery Response message from the c-AGW, the AGW will add the information in its mapping table. After that, the AGW responds withDevice ID Response message to PMD (Step  4). Now, the data packets will be forwarded to C-PMD via AGW and c-AGW.Figure 6
Packet delivery operation.


## 3.5. Handover Operation

When PMD moves from the previous access gateway (p-AGW) to a new access gateway (n-AGW) in the same home network domain, the PMD will sendAttachment Trigger to n-AGW (Step  1). AfterAttachment Trigger, the n-AGW will update its visiting GDID register (VGR) which maintains GDID-LLOC (AID) mapping table as shown in Table 3. Then, n-AGW sendsLocation Update Request message to previous AGW (p-AGW). The p-AGW will update its HGR and responds withLocation Update Response message to n-AGW (Steps  2 and 3). TheLocation Update Response message shall include the information of corresponding-AGW (c-AGW) address, which is recorded in the mapping table of p-AGW.Table 3
Visiting GDID register (VGR).
Number
ID
LLOC(in the visited domain)
Home domain
1
GDID1
LLOC1 (AID) of PMD
GLOC1(AGW of GDID1)
2
GDID2
LLOC2 (AID) of PMD
GLOC2(AGW of GDID2)
3
⋯
⋯
⋯Now, n-AGW sends aLocation Update Request message to c-AGW for route optimization. On the reception of theLocation Update Request message, c-AGW will update its mapping table and send aLocation Update Response to n-AGW. n-AGW and c-AGW will now use the optimized route (Steps 4 and 5).


## 4. Performance Analysis

In this section, we analyze the performances of candiate mobility management schemes: PMIP-Coordinator, ID-LOC-based scheme, and proposed scheme. As performance metrics, we consider the delays associated with registration, packet delivery, and handover delay, since such delays are very impormant in mobility management.


### 4.1. Analysis Model

We define several notations for analysis and summarize them in the Notations section. We illustrate the considered network model in Figure8.In Figure8, we denote by T
x
-
y
(
S
) the transmission delay of a message with size S from node x to node y via awireless link. It can be expressed asT
x
-
y
S
=
(
1
-
q
)
/
(
1
+
q
)
·
S
/
B
w
l
+
L
w
l. In the meantime, we denote by T
x
-
y
(
S
,
H
x
-
y
) the transmission delay of a message with size S from node x to node y via awired link, where H
x
-
y represents the number of wired hops between node x to nodey. Note that it is expressed as T
x
-
y
S
,
H
x
-
y
=
H
x
-
y
·
S
/
B
w
+
L
w
+
T
q.


### 4.2. Analysis of Registration Delay (RD)

#### 4.2.1. PMIP-Coordinator

As shown in Figure1, whenCoordinator is attached to MAG, then it sendsRS message to MAG by way PMD. After that, the MAG performsAuthentication-Authorization-Accounting (AAA) query and reply operation with AAA server for authentication for all body sensors. Then, the MAG performs theAAA query operation with AAA server, and then MAG performs aggregatedPBU operation with LMA. Then, LMA performs theAAA query andreply operations with AAA server for each body sensor. After authentication, LMA respond with aggregatedPBA to MAG. Now, the MAG responds with aggregatedRA message toCoordinator. Accordingly, we get the RD of PMIP-Coordinator as follows:(1)
RD
PMIP-Coordinator
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
N
S
×
2
T
GW-AAA
S
c
+
2
T
LMA-AAA
S
c
.


#### 4.2.2. ID-LOC-Based Scheme

As shown in Figure2, when body sensors are attached to PMD, then it performsRS andRA messages to PMD by way ofCoordinator. After that, the PMD performsLocation Update Request andResponse operation with AGW. Then, the AGW also performs theLocation Update Request andResponse operation with H-DLMA. Accordingly, we get the RD of ID-LOC-based scheme as follows:(2)
RD
ID-LOC
=
N
S
×
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
.


#### 4.2.3. Proposed Scheme

As shown in Figure5, whenCoordinator is attached to PMD, then it performs aggregatedRSandRA messages to PMD. After that, the PMD performsLocation Update Request andResponse operation with AGW. Accordingly, we get the RD of proposed scheme as follows:(3)
RD
Proposed
scheme
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
.


### 4.3. Analysis of Packet Delivery Delay (PDD)

#### 4.3.1. PMIP-Coordinator

When PMD wants to communicate with particular C-PMD, PMD will forward the data packets to LMA and the LMA will forward the data packet to c-AGW and further to C-PMD. Accordingly, we get the PDD of PMIP-Coordinator as follows:(4)
PDD
PMIP-Coordinator
=
2
T
PMD-GW
S
d
+
2
T
GW-LMA
/
DLMA
S
d
.


#### 4.3.2. ID-LOC-Based Scheme

When PMD wants to communicate with particular C-PMD, PMD will sendDevice ID Request message to AGW. If there is no information, then AGW performsLocation Discovery RequestandResponse message with C-DLMA. Then, AGW sendsRoute Setup Request message to c-AGW. After that, the c-AGW performs theGDID Discovery Query and Reply messages with corresponding PMD (C-PMD). After that, the c-AGW responds withRoute Setup Complete message to AGW. After that, the AGW responds withDevice ID Response message to PMD. Now, the data packets will be forwarded to C-PMD via AGW and c-AGW: (5)
PDD
ID-LOC
=
4
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
2
T
GW-GW
S
c
+
2
T
PMD-GW
S
d
+
T
GW-GW
S
d
.


#### 4.3.3. Proposed Scheme

When PMD wants to communicate with particular C-PMD, PMD will sendDevice ID Request message to AGW. If there is no information, then AGW performsLocation Discovery RequestandResponse message with c-AGW. After that, the AGW responds withDevice ID Response message to PMD. Now, the data packets will be forward to C-PMD via AGW and c-AGW: (6)
PDD
Proposed
Scheme
=
2
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
2
T
PMD-GW
S
d
+
T
GW-GW
S
d
.


### 4.4. Analysis of Handover Delay (HD)

#### 4.4.1. PMIP-Coordinator

As shown in Figure1, when theCoordinator is detached from p-MAG, then p-MAG will send aggregatedDeReg message to LMA. WhenCoordinator is attached to n-MAG, then it sendsRS message to n-MAG by way PMD. After that, the n-MAG performsAAA query andreply operation with AAA server for authentication for all body sensors. Then, the n-MAG performs theAAA query operation with AAA server, and then n-MAG performs aggregatedPBU operation with LMA. Then, LMA performs theAAA query andreply operations with AAA server for each body sensor. After authentication, LMA responds with aggregatedPBA to n-MAG. The handover tunnel is established between n-MAG and LMA. After tunnel establishment, the n-MAG responds with aggregatedRA message toCoordinator. Accordingly, we get the HD of PMIP-Coordinator as follows:(7)
HD
PMIP-Coordinator
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
4
T
GW-LMA
/
DLMA
S
c
+
N
S
×
2
T
GW-AAA
S
c
+
2
T
LMA-AAA
S
c
+
T
GW-LMA
/
DLMA
S
d
.


#### 4.4.2. ID-LOC-Based Scheme

As shown in Figure2, when PMD is attached with n-AGW, then PMD will sendAttachment Trigger to n-AGW. After that, the n-AGW performsDevice Context Request andReply messages with p-AGW. Then, p-AGW performsLocation Update Request andResponsemessages with H-DLMA. Accordingly, we get the HD of ID-LOC-based scheme as follows:(8)
HD
ID-LOC
=
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
T
GW-GW
S
d
.


#### 4.4.3. Proposed Scheme

As shown in Figure7, when PMD is attached with n-AGW, then PMD will sendAttachment Trigger to n-AGW. After that, the n-AGW performsLocation Update Request andResponse messages with p-AGW. Accordingly, we get the HD of proposed scheme as follows:(9)
HD
Proposed
Scheme
=
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
T
GW-GW
S
d
.Figure 7
Handover operation.Figure 8
Network model for performance analysis.


## 4.1. Analysis Model

We define several notations for analysis and summarize them in the Notations section. We illustrate the considered network model in Figure8.In Figure8, we denote by T
x
-
y
(
S
) the transmission delay of a message with size S from node x to node y via awireless link. It can be expressed asT
x
-
y
S
=
(
1
-
q
)
/
(
1
+
q
)
·
S
/
B
w
l
+
L
w
l. In the meantime, we denote by T
x
-
y
(
S
,
H
x
-
y
) the transmission delay of a message with size S from node x to node y via awired link, where H
x
-
y represents the number of wired hops between node x to nodey. Note that it is expressed as T
x
-
y
S
,
H
x
-
y
=
H
x
-
y
·
S
/
B
w
+
L
w
+
T
q.


## 4.2. Analysis of Registration Delay (RD)

### 4.2.1. PMIP-Coordinator

As shown in Figure1, whenCoordinator is attached to MAG, then it sendsRS message to MAG by way PMD. After that, the MAG performsAuthentication-Authorization-Accounting (AAA) query and reply operation with AAA server for authentication for all body sensors. Then, the MAG performs theAAA query operation with AAA server, and then MAG performs aggregatedPBU operation with LMA. Then, LMA performs theAAA query andreply operations with AAA server for each body sensor. After authentication, LMA respond with aggregatedPBA to MAG. Now, the MAG responds with aggregatedRA message toCoordinator. Accordingly, we get the RD of PMIP-Coordinator as follows:(1)
RD
PMIP-Coordinator
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
N
S
×
2
T
GW-AAA
S
c
+
2
T
LMA-AAA
S
c
.


### 4.2.2. ID-LOC-Based Scheme

As shown in Figure2, when body sensors are attached to PMD, then it performsRS andRA messages to PMD by way ofCoordinator. After that, the PMD performsLocation Update Request andResponse operation with AGW. Then, the AGW also performs theLocation Update Request andResponse operation with H-DLMA. Accordingly, we get the RD of ID-LOC-based scheme as follows:(2)
RD
ID-LOC
=
N
S
×
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
.


### 4.2.3. Proposed Scheme

As shown in Figure5, whenCoordinator is attached to PMD, then it performs aggregatedRSandRA messages to PMD. After that, the PMD performsLocation Update Request andResponse operation with AGW. Accordingly, we get the RD of proposed scheme as follows:(3)
RD
Proposed
scheme
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
.


## 4.2.1. PMIP-Coordinator

As shown in Figure1, whenCoordinator is attached to MAG, then it sendsRS message to MAG by way PMD. After that, the MAG performsAuthentication-Authorization-Accounting (AAA) query and reply operation with AAA server for authentication for all body sensors. Then, the MAG performs theAAA query operation with AAA server, and then MAG performs aggregatedPBU operation with LMA. Then, LMA performs theAAA query andreply operations with AAA server for each body sensor. After authentication, LMA respond with aggregatedPBA to MAG. Now, the MAG responds with aggregatedRA message toCoordinator. Accordingly, we get the RD of PMIP-Coordinator as follows:(1)
RD
PMIP-Coordinator
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
N
S
×
2
T
GW-AAA
S
c
+
2
T
LMA-AAA
S
c
.


## 4.2.2. ID-LOC-Based Scheme

As shown in Figure2, when body sensors are attached to PMD, then it performsRS andRA messages to PMD by way ofCoordinator. After that, the PMD performsLocation Update Request andResponse operation with AGW. Then, the AGW also performs theLocation Update Request andResponse operation with H-DLMA. Accordingly, we get the RD of ID-LOC-based scheme as follows:(2)
RD
ID-LOC
=
N
S
×
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
.


## 4.2.3. Proposed Scheme

As shown in Figure5, whenCoordinator is attached to PMD, then it performs aggregatedRSandRA messages to PMD. After that, the PMD performsLocation Update Request andResponse operation with AGW. Accordingly, we get the RD of proposed scheme as follows:(3)
RD
Proposed
scheme
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
.


## 4.3. Analysis of Packet Delivery Delay (PDD)

### 4.3.1. PMIP-Coordinator

When PMD wants to communicate with particular C-PMD, PMD will forward the data packets to LMA and the LMA will forward the data packet to c-AGW and further to C-PMD. Accordingly, we get the PDD of PMIP-Coordinator as follows:(4)
PDD
PMIP-Coordinator
=
2
T
PMD-GW
S
d
+
2
T
GW-LMA
/
DLMA
S
d
.


### 4.3.2. ID-LOC-Based Scheme

When PMD wants to communicate with particular C-PMD, PMD will sendDevice ID Request message to AGW. If there is no information, then AGW performsLocation Discovery RequestandResponse message with C-DLMA. Then, AGW sendsRoute Setup Request message to c-AGW. After that, the c-AGW performs theGDID Discovery Query and Reply messages with corresponding PMD (C-PMD). After that, the c-AGW responds withRoute Setup Complete message to AGW. After that, the AGW responds withDevice ID Response message to PMD. Now, the data packets will be forwarded to C-PMD via AGW and c-AGW: (5)
PDD
ID-LOC
=
4
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
2
T
GW-GW
S
c
+
2
T
PMD-GW
S
d
+
T
GW-GW
S
d
.


### 4.3.3. Proposed Scheme

When PMD wants to communicate with particular C-PMD, PMD will sendDevice ID Request message to AGW. If there is no information, then AGW performsLocation Discovery RequestandResponse message with c-AGW. After that, the AGW responds withDevice ID Response message to PMD. Now, the data packets will be forward to C-PMD via AGW and c-AGW: (6)
PDD
Proposed
Scheme
=
2
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
2
T
PMD-GW
S
d
+
T
GW-GW
S
d
.


## 4.3.1. PMIP-Coordinator

When PMD wants to communicate with particular C-PMD, PMD will forward the data packets to LMA and the LMA will forward the data packet to c-AGW and further to C-PMD. Accordingly, we get the PDD of PMIP-Coordinator as follows:(4)
PDD
PMIP-Coordinator
=
2
T
PMD-GW
S
d
+
2
T
GW-LMA
/
DLMA
S
d
.


## 4.3.2. ID-LOC-Based Scheme

When PMD wants to communicate with particular C-PMD, PMD will sendDevice ID Request message to AGW. If there is no information, then AGW performsLocation Discovery RequestandResponse message with C-DLMA. Then, AGW sendsRoute Setup Request message to c-AGW. After that, the c-AGW performs theGDID Discovery Query and Reply messages with corresponding PMD (C-PMD). After that, the c-AGW responds withRoute Setup Complete message to AGW. After that, the AGW responds withDevice ID Response message to PMD. Now, the data packets will be forwarded to C-PMD via AGW and c-AGW: (5)
PDD
ID-LOC
=
4
T
PMD-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
2
T
GW-GW
S
c
+
2
T
PMD-GW
S
d
+
T
GW-GW
S
d
.


## 4.3.3. Proposed Scheme

When PMD wants to communicate with particular C-PMD, PMD will sendDevice ID Request message to AGW. If there is no information, then AGW performsLocation Discovery RequestandResponse message with c-AGW. After that, the AGW responds withDevice ID Response message to PMD. Now, the data packets will be forward to C-PMD via AGW and c-AGW: (6)
PDD
Proposed
Scheme
=
2
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
2
T
PMD-GW
S
d
+
T
GW-GW
S
d
.


## 4.4. Analysis of Handover Delay (HD)

### 4.4.1. PMIP-Coordinator

As shown in Figure1, when theCoordinator is detached from p-MAG, then p-MAG will send aggregatedDeReg message to LMA. WhenCoordinator is attached to n-MAG, then it sendsRS message to n-MAG by way PMD. After that, the n-MAG performsAAA query andreply operation with AAA server for authentication for all body sensors. Then, the n-MAG performs theAAA query operation with AAA server, and then n-MAG performs aggregatedPBU operation with LMA. Then, LMA performs theAAA query andreply operations with AAA server for each body sensor. After authentication, LMA responds with aggregatedPBA to n-MAG. The handover tunnel is established between n-MAG and LMA. After tunnel establishment, the n-MAG responds with aggregatedRA message toCoordinator. Accordingly, we get the HD of PMIP-Coordinator as follows:(7)
HD
PMIP-Coordinator
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
4
T
GW-LMA
/
DLMA
S
c
+
N
S
×
2
T
GW-AAA
S
c
+
2
T
LMA-AAA
S
c
+
T
GW-LMA
/
DLMA
S
d
.


### 4.4.2. ID-LOC-Based Scheme

As shown in Figure2, when PMD is attached with n-AGW, then PMD will sendAttachment Trigger to n-AGW. After that, the n-AGW performsDevice Context Request andReply messages with p-AGW. Then, p-AGW performsLocation Update Request andResponsemessages with H-DLMA. Accordingly, we get the HD of ID-LOC-based scheme as follows:(8)
HD
ID-LOC
=
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
T
GW-GW
S
d
.


### 4.4.3. Proposed Scheme

As shown in Figure7, when PMD is attached with n-AGW, then PMD will sendAttachment Trigger to n-AGW. After that, the n-AGW performsLocation Update Request andResponse messages with p-AGW. Accordingly, we get the HD of proposed scheme as follows:(9)
HD
Proposed
Scheme
=
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
T
GW-GW
S
d
.Figure 7
Handover operation.Figure 8
Network model for performance analysis.


## 4.4.1. PMIP-Coordinator

As shown in Figure1, when theCoordinator is detached from p-MAG, then p-MAG will send aggregatedDeReg message to LMA. WhenCoordinator is attached to n-MAG, then it sendsRS message to n-MAG by way PMD. After that, the n-MAG performsAAA query andreply operation with AAA server for authentication for all body sensors. Then, the n-MAG performs theAAA query operation with AAA server, and then n-MAG performs aggregatedPBU operation with LMA. Then, LMA performs theAAA query andreply operations with AAA server for each body sensor. After authentication, LMA responds with aggregatedPBA to n-MAG. The handover tunnel is established between n-MAG and LMA. After tunnel establishment, the n-MAG responds with aggregatedRA message toCoordinator. Accordingly, we get the HD of PMIP-Coordinator as follows:(7)
HD
PMIP-Coordinator
=
2
T
C-PMD
S
c
+
2
T
PMD-GW
S
c
+
4
T
GW-LMA
/
DLMA
S
c
+
N
S
×
2
T
GW-AAA
S
c
+
2
T
LMA-AAA
S
c
+
T
GW-LMA
/
DLMA
S
d
.


## 4.4.2. ID-LOC-Based Scheme

As shown in Figure2, when PMD is attached with n-AGW, then PMD will sendAttachment Trigger to n-AGW. After that, the n-AGW performsDevice Context Request andReply messages with p-AGW. Then, p-AGW performsLocation Update Request andResponsemessages with H-DLMA. Accordingly, we get the HD of ID-LOC-based scheme as follows:(8)
HD
ID-LOC
=
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
2
T
GW-LMA
/
DLMA
S
c
+
T
GW-GW
S
d
.


## 4.4.3. Proposed Scheme

As shown in Figure7, when PMD is attached with n-AGW, then PMD will sendAttachment Trigger to n-AGW. After that, the n-AGW performsLocation Update Request andResponse messages with p-AGW. Accordingly, we get the HD of proposed scheme as follows:(9)
HD
Proposed
Scheme
=
T
PMD-GW
S
c
+
2
T
GW-GW
S
c
+
T
GW-GW
S
d
.Figure 7
Handover operation.Figure 8
Network model for performance analysis.


## 5. Numerical Results and Discussion

Based on the analytical equations given in Section4, we compare the performances of the considered mobility management schemes. In the numerical results, the default value of each parameter has been configured as follows, referring to [11]; that is, H
DLMS-DLMS
=
5, H
GW-LMA
/
DLMS
=
5, H
GW-GW
=
5, H
GW-AAA
=
5, and H
LMA-AAA
=
5, and L
w
l
=
10
(
ms
), L
w
=
2
(
ms
), q
=
0.5, N
S
=
10, T
q
=
5
(
ms
), S
c
=
96
(
bytes
), S
d
=
200
(
bytes
), B
w
l
=
11
(
Mbps
), and B
w
=
100
(
Mbps
), where N
S denotes the number of sensors in the network. Among the various parameters, we note that L
w
l, T
q, N
S, and H
GW-LMA
/
DLMA can depend on the network conditions. Thus, we evaluate the performances of the considered schemes by varying the values of these parameters.


### 5.1. Registration Delay

We show the impact of the delay of wireless links (L
w
l) on the registration delay in Figure 9. We can see that the registration delay increases linearly as L
w
l becomes larger in every considered scheme. In particular, the PMIP-Coordinator mobility scheme is more sensitive to the delay of wireless links than the ID-LOC mobility scheme, since they exchange the signaling messages for the registration over wireless links and also perform AAA query operation with AAA server for each body sensor. The PMIP-Coordinator also performsPBU/PBA operation with LMA for binding. While ID-LOC mobility scheme performs better than PMIP-Coordinator, this is because there is no AAA query operation with AAA server, since it performsRS/RA messages with PMD for each body sensors over wireless link. We observe that the proposed scheme performs best among the candidate schemes. This is because theCoordinator performsRS/RA messages with PMD and also there is no binding operation with DLMA, since the binding operation performs with AGW.Figure 9
Impact ofL
w
l on the registration delay.Figure10 compares the registration delays of candidate schemes by varying the average queuing delay (T
q) at each node. For the two schemes, PMIP-Coordinator and ID-LOC-based scheme, the registration delay increases linearly as T
q increase because the two schemes exchange the signaling messages with AAA, LMA, and DLMA over the wired network. In contrast, proposed scheme is not affected by the average queuing delay at all since it exchanges the signaling messages for the registration over wireless links only. We can see that the proposed scheme performs well compared to the existing schemes.Figure 10
Impact ofT
q on the registration delay.We next illustrate the registration delay for different number of sensors in the network (N
S) in Figure 11. We observe that the PMIP-Coordinator gives worse performances than the ID-LOC-based scheme. This is because of the signaling messages for authentication with AAA server by GW and LMA for each body sensor. In contrast, the proposed scheme is not affected by the number of sensors. This is because onlyCoordinator can exchange theRS/RA messages with PMD on behalf of body sensors.Figure 11
Impact ofN
S on the registration delay.


### 5.2. Packet Delivery Delay

We illustrate the packet delivery delay for different hop counts between GW and LMA/DLMA (H
GW-LMA
/
DLMA) in Figure 12. We can see that H
GW-LMA
/
DLMA affects the performances of the existing mobility schemes significantly. We observe that ID-LOC-based scheme performs poorly compared to the PMIP-Coordinator scheme. This is because there is query operation before data delivery, while PMIP-Coordinator relies on LMA in the distance for the registration and the data delivery. We can see in the figure that the proposed scheme is not affected with H
GW-LMA
/
DLMA, since AGW maintains HGR and VGR.Figure 12
Impact ofH
GW-LMA
/
DLMA on the packet delivery delay.


### 5.3. Handover Delay

The delay of wireless links (L
w
l) gives a significant impact on the handover delay for the three candidate schemes, as shown in Figure 13. In particular, the PMIP-Coordinator mobility scheme is more sensitive to the delay of wireless links than the ID-LOC mobility scheme, since the signaling messages exchanged over the wireless links spends much time in configuring a new care-of-address through the duplicate address detection procedure by handover. The PMIP-Coordinator also performsPBU/PBA operation with LMA for binding. While ID-LOC mobility scheme performs better than PMIP-Coordinator, this is because there is no AAA query operation with AAA server, since it performsRS/RA messages with PMD for each body sensor over wireless link. We can see in the figure that proposed scheme performs best among the candidate schemes.Figure 13
Impact ofL
w
l on the handover delay.Figure14 shows the impact of the average queuing delay (T
q) on the handover delay. The delay rises up linearly as T
q increases in all the schemes. We observe that the PMIP-Coordinator performs worst while consuming much time in the duplicate address detection procedure.Figure 14
Impact ofT
q on the handover delay.We illustrate the handover delay for different hop counts between GW and LMA/DLMA (H
GW-LMA
/
DLMA) in Figure 15. We can see that H
GW-LMA
/
DLMA affects the performances of the existing mobility schemes significantly, since they rely on LMA/DLMA in the distance for the registration and the data delivery.Figure 15
Impact ofH
GW-LMA
/
DLMA on the handover delay.Table4 summarizes the improvement of the proposed scheme from the existing schemes in terms of average percentage based on parameters.Table 4
Improvement of proposed scheme from existing schemes in average percentage.
Parameters
Registration delay
Handover delay
Packet delivery delay
From PMIP-Coordinator
From ID-LOC
From PMIP-Coordinator
From ID-LOC
From PMIP-Coordinator
From ID-LOC
L
wl
6.7%
15.6%
8.5%
67.2%
X
X
T
q
4.5%
15.13%
8.2%
66%
X
X
N
s
1%
4.1%
X
X
X
X
H
GW-LMA/DLMA
X
X
6.4%
42.6%
136.1%
44.7%


## 5.1. Registration Delay

We show the impact of the delay of wireless links (L
w
l) on the registration delay in Figure 9. We can see that the registration delay increases linearly as L
w
l becomes larger in every considered scheme. In particular, the PMIP-Coordinator mobility scheme is more sensitive to the delay of wireless links than the ID-LOC mobility scheme, since they exchange the signaling messages for the registration over wireless links and also perform AAA query operation with AAA server for each body sensor. The PMIP-Coordinator also performsPBU/PBA operation with LMA for binding. While ID-LOC mobility scheme performs better than PMIP-Coordinator, this is because there is no AAA query operation with AAA server, since it performsRS/RA messages with PMD for each body sensors over wireless link. We observe that the proposed scheme performs best among the candidate schemes. This is because theCoordinator performsRS/RA messages with PMD and also there is no binding operation with DLMA, since the binding operation performs with AGW.Figure 9
Impact ofL
w
l on the registration delay.Figure10 compares the registration delays of candidate schemes by varying the average queuing delay (T
q) at each node. For the two schemes, PMIP-Coordinator and ID-LOC-based scheme, the registration delay increases linearly as T
q increase because the two schemes exchange the signaling messages with AAA, LMA, and DLMA over the wired network. In contrast, proposed scheme is not affected by the average queuing delay at all since it exchanges the signaling messages for the registration over wireless links only. We can see that the proposed scheme performs well compared to the existing schemes.Figure 10
Impact ofT
q on the registration delay.We next illustrate the registration delay for different number of sensors in the network (N
S) in Figure 11. We observe that the PMIP-Coordinator gives worse performances than the ID-LOC-based scheme. This is because of the signaling messages for authentication with AAA server by GW and LMA for each body sensor. In contrast, the proposed scheme is not affected by the number of sensors. This is because onlyCoordinator can exchange theRS/RA messages with PMD on behalf of body sensors.Figure 11
Impact ofN
S on the registration delay.


## 5.2. Packet Delivery Delay

We illustrate the packet delivery delay for different hop counts between GW and LMA/DLMA (H
GW-LMA
/
DLMA) in Figure 12. We can see that H
GW-LMA
/
DLMA affects the performances of the existing mobility schemes significantly. We observe that ID-LOC-based scheme performs poorly compared to the PMIP-Coordinator scheme. This is because there is query operation before data delivery, while PMIP-Coordinator relies on LMA in the distance for the registration and the data delivery. We can see in the figure that the proposed scheme is not affected with H
GW-LMA
/
DLMA, since AGW maintains HGR and VGR.Figure 12
Impact ofH
GW-LMA
/
DLMA on the packet delivery delay.


## 5.3. Handover Delay

The delay of wireless links (L
w
l) gives a significant impact on the handover delay for the three candidate schemes, as shown in Figure 13. In particular, the PMIP-Coordinator mobility scheme is more sensitive to the delay of wireless links than the ID-LOC mobility scheme, since the signaling messages exchanged over the wireless links spends much time in configuring a new care-of-address through the duplicate address detection procedure by handover. The PMIP-Coordinator also performsPBU/PBA operation with LMA for binding. While ID-LOC mobility scheme performs better than PMIP-Coordinator, this is because there is no AAA query operation with AAA server, since it performsRS/RA messages with PMD for each body sensor over wireless link. We can see in the figure that proposed scheme performs best among the candidate schemes.Figure 13
Impact ofL
w
l on the handover delay.Figure14 shows the impact of the average queuing delay (T
q) on the handover delay. The delay rises up linearly as T
q increases in all the schemes. We observe that the PMIP-Coordinator performs worst while consuming much time in the duplicate address detection procedure.Figure 14
Impact ofT
q on the handover delay.We illustrate the handover delay for different hop counts between GW and LMA/DLMA (H
GW-LMA
/
DLMA) in Figure 15. We can see that H
GW-LMA
/
DLMA affects the performances of the existing mobility schemes significantly, since they rely on LMA/DLMA in the distance for the registration and the data delivery.Figure 15
Impact ofH
GW-LMA
/
DLMA on the handover delay.Table4 summarizes the improvement of the proposed scheme from the existing schemes in terms of average percentage based on parameters.Table 4
Improvement of proposed scheme from existing schemes in average percentage.
Parameters
Registration delay
Handover delay
Packet delivery delay
From PMIP-Coordinator
From ID-LOC
From PMIP-Coordinator
From ID-LOC
From PMIP-Coordinator
From ID-LOC
L
wl
6.7%
15.6%
8.5%
67.2%
X
X
T
q
4.5%
15.13%
8.2%
66%
X
X
N
s
1%
4.1%
X
X
X
X
H
GW-LMA/DLMA
X
X
6.4%
42.6%
136.1%
44.7%


## 6. Conclusion

In this paper, we proposed a group-based mobility management scheme, which is based on ID/LOC separation concept for ID-based communications with location-based routing to reduce the number of control messages. In the proposed scheme, the sensor node and PMD have globally unique device identifiers (GDIDs). Each GDID contains the information of the associated home network domain. For handover support, each access gateway maintains its home GDID register and its visiting GDID register. In addition, only theCoordinator can exchangeRS/RA messages with PMD instead of each sensor. The numerical analysis shows that the proposed scheme can reduce the registration delay, packet delivery delay, and the handover delay significantly, compared to the existing mobility schemes.



---

*Source: 537205-2015-08-04.xml*