Future Generation Computer Systems: Moneeb Gohar Jin-Ghoo Choi Seok-Joo Koh
Future Generation Computer Systems: Moneeb Gohar Jin-Ghoo Choi Seok-Joo Koh
Future Generation Computer Systems: Moneeb Gohar Jin-Ghoo Choi Seok-Joo Koh
highlights
article info a b s t r a c t
Article history: The Constrained Application Protocol (CoAP) has been widely used, as the number of embedded sensors
Received 31 October 2017 or devices increases. To support mobility management in web based Internet-of-Things environment
Received in revised form 4 May 2018 is critical issue. For this purpose, a CoAP-based mobility management protocol, named CoMP has been
Accepted 2 June 2018
proposed, but this protocol was designed for a single sensor node mobility. However, it does not perform
Available online 6 June 2018
well in group-based mobility. To overcome this limitation, we propose a CoAP-based group mobility
management protocol, named CoMP-G. In the proposed scheme, one of the body sensor will function
Keywords:
CoAP as a coordinator and it will exchange all the control messages with web-of-things mobility management
Mobility management system (WMMS) on behalf of other body sensors. Besides, each WMMS maintains the information of the
Web-based group of body sensors. From the numerical analysis, we proved that the proposed scheme gives the best
IoT mobility performance in terms of total signaling and handover delay from the existing CoMP protocol.
WBAN © 2018 Published by Elsevier B.V.
Group mobility
1. Introduction major role in the field of health care [6–8]. Intelligent medical small
sensors can be worn on or implanted in the human body. These
Wireless Networks are the biggest components of network sensors measured the data and send it to external medical doctor.
industry where computer networking is done using wireless con- With these sensors the patient can move from place to another.
nections by connecting network nodes [1]. With passing days’ Many people die from different fatal diseases, when it is diagnosed
different devices like mobile phones are now become the basic lately. For this purpose, the Wireless Body Area Network is used to
needs. So there is a need of Internet Protocol which are especially detect early and prevent from the fatal diseases [8–10]. A wireless
designed for the mobile devices when they move from one net- body area network are the specific types of sensor network which
work to another. Nowadays, we are not limited to one network are designed to handle multiple medical sensors placed inside or
devices, such as the communication becomes Machine to Machine, outside of the body. The generalized model of WBAN is shown in
Human to Machine and Machine to Human and Human to Human, Fig. 1.
this major penetration introduced the idea of Internet of Things These days, each person has multiple devices that can commu-
(IoT) [2–5]. IoT serves in many fields like Medical sciences, elec- nicate each other. The communication pattern can be machine-to-
tronic engineering as well as mechanical engineering. IoT play a machine, human-to-machine, machine-to-human, and human-to-
human. Anything we think of can exchange information to serve
human beings. It is the concept of IoT [11]. IoT has found many
* Corresponding author. applications in various fields such as medical science, electronic
E-mail addresses: [email protected] (M. Gohar), [email protected]
(S. Koh). engineering as well as mechanical engineering [12]. Suppose we
https://doi.org/10.1016/j.future.2018.06.003
0167-739X/© 2018 Published by Elsevier B.V.
310 M. Gohar et al. / Future Generation Computer Systems 88 (2018) 309–318
protocol, named CoMP has been proposed, but this protocol was
designed for a single sensor node mobility. However, it does not
perform well in group-based mobility [18]. To overcome this lim-
itation, we propose a CoAP-based group mobility management
protocol, named CoMP-G, in which one of the sensor will function
as a coordinator and it will exchange all the control messages
with web-of-things mobility management system (WMMS) on
behalf of other body sensors. Besides, each WMMS maintains the
information of the group of mobile sensors.
The rest of this paper is organized as follows. Section 2 de-
scribes the existing candidate mobility schemes for comparison.
In Section 3 describes the proposed group-based mobility scheme.
Section 4 demonstrates the performance analysis by comparing the
proposed and existing scheme by numerical analysis and results.
Section 5 concludes this paper.
2.3. Handover operations WMMS via AR for each request on the basis of body sensor (Step
7,8).
In this section, we consider the case in which the group of We now assume that the body sensors changes its point of
sensors moves from previous AR (p-AR) to new AR (n-AR) as shown attachment in the same network domain. When the body sensors
in Fig. 4. In order to perform the handover operation, each of the is detached from p-AR and attached to n-AR and received new
body sensors first detect the radio signal strength (RSS) from the temporary address from new AR (n-AR), each body sensor notifies
previous AR. When RSS drops below by a certain threshold value,
the WMMS by sending PUT Request for Binding Update via n-AR
each of the body sensor starts handover operation by sending PUT
(Step 9,10). The WMMS update its database for each body sensor
Request for Holding to WMMS via p-AR (Step 1, 2). The WMMS
updates the H_Flag status to 1 for all the body sensors. After that, and respond with ACK Response for Binding Update to each body
the WMMS replies with ACK Response for Holding to each body sensor via n-AR (step 11,12). The body sensors also updates the
sensor via p-AR (Step 3,4). The WMMS also forwards the PUT CoAP web client by sending PUT Request for Binding Update via n-
Request for Holding on basis of each body sensor to CoAP web client AR to CoAP web client (Step 13,14,15). The CoAP web client update
via AR (Step 5,6). The CoAP client updates its cache for each sensor. its cache for each body sensor and replies with ACK Response
The CoAP web client respond with ACK Response for Holding to for Binding Update to each body sensor via n-AR (Step 16,17,18).
312 M. Gohar et al. / Future Generation Computer Systems 88 (2018) 309–318
Now, each body sensor and CoAP web client communication is 3.2. Initial registration and data delivery
established through new AR.
The main purpose of the registration phase is to reduce the
3. Proposed scheme amount of control messages. Fig. 6 shows the detail initial regis-
tration and data delivery of the proposed scheme. When a group
This section first describes the network model of the proposed of body sensors enter a CoMP AR domain and the coordinator is
attached to AR, it sends aggregated POST Request for Registration
scheme and then describing the registration and handover opera-
message, containing the information on group, to WMMS via AR
tions.
(Step 1, 2). Upon reception of this POST Request for Registration mes-
sage from the coordinator, WMMS will make group of body sensors
3.1. Network model of group mobility management using CoAP and responds with a ACK Response for Registration to coordinator
via AR (Step 3, 4).
Fig. 5 shows the network model of group mobility management On the other hand, the CoAP web client also registered with
using CoAP. We consider a group of sensors attached to human WMMS by exchanging POST Request for Registration and ACK Re-
body which monitors the measured data. One of sensor function sponse for Registration messages (Step 5,6,7,8). As the CoAP web
as a coordinator which exchange the control signaling messages client want to communicate with body sensors, it sends GET Re-
with Access Router (AR) on behalf of other sensors. The AR domain quest for Discovery message for finding group of body sensors to
contains Full-Function Device (FFD). The web-of-things mobility WMMS via AR (Step 9,10). After finding group of body sensors in
management system (WMMS) maintains the information of the the database, the WMMS replies with ACK Response for Discovery
group of sensors which is required to perform mobility as shown in message to CoAP web client via AR (Step 11,12). After discovery, the
Table 1. The IP addresses of body sensors are permanent, while the CoAP web client and coordinator can exchange the data via AR’s.
IP addresses of AR’s are temporary. H_Flag indicate the handover
status of the group of sensors. If the value of H_Flag is 1, then the 3.3. Handover operations
corresponding group of body sensors become in handover status.
If the value is 0, then the corresponding group of body sensors are In this section, we consider the case in which the group of
not in handover status. A lifetime is the time in which the binding sensors moves from previous AR (p-AR) to new AR (n-AR) as
of permanent addresses of the group of sensors and temporary shown in Fig. 7. In order to perform the handover operation, the
address of the AR are effective. coordinator first detect the radio signal strength (RSS) from the
Initially, the coordinator communicates with CoAP web client previous AR. When RSS drops below by a certain threshold value,
in the previous access router (p-AR) domain, and then it moves to the coordinator starts handover operation by sending PUT Request
a new access router (n-AR) by handover. for Holding to WMMS via p-AR (Step 1,2). The WMMS updates the
M. Gohar et al. / Future Generation Computer Systems 88 (2018) 309–318 313
Table 1
Web-of-things mobility management system (WMMS).
Group P_Addr (Sensor IP address) T_Addr (AR IP address) H_Flag Lifetime
1 P_Addr_1
1 P_Addr_2 T_Addr
1 P_Addr_3
H_Flag status to 1. After that, the WMMS replies with ACK Response (Step 9,10). The WMMS update its database and respond with ACK
for Holding to coordinator via p-AR (Step 3,4). The WMMS also
Response for Binding Update to coordinator via n-AR (step 11,12).
forwards the PUT Request for Holding for the group to CoAP web
client via AR (Step 5,6). The CoAP client updates its cache. The CoAP The coordinator also updates the CoAP web client by sending
web client respond with ACK Response for Holding to WMMS via AR PUT Request for Binding Update via n-AR to CoAP web client (Step
(Step 7,8).
We now assume that the coordinator changes its point of at- 13,14,15). The CoAP web client update its cache and replies with
tachment in the same network domain. When the coordinator ACK Response for Binding Update to coordinator via n-AR (Step
is detached from p-AR and attached to n-AR and received new
16,17,18). Now, CoAP coordinator and CoAP web client communi-
temporary address from new AR (n-AR), the coordinator notifies
the WMMS by sending PUT Request for Binding Update via n-AR cation is through new AR.
314 M. Gohar et al. / Future Generation Computer Systems 88 (2018) 309–318
For performance analysis, we compare the registration and In CoMP, the data delivery delay (DDD) from CoAP web client
handover delays for the two candidate mobility schemes: CoMP, to body sensors can be calculated as follows. First, the CoAP web
and CoMP-G. client registered with WMMS. After registration, the CoAP web
client want to communicate with body sensors. For finding the
4.1. Analysis model body sensors, CoAP web client exchanges GET Request for Discovery
and ACK Response for Discovery messages for each body sensor with
We consider a network illustrated in Fig. 8, in which each WMMS via AR. After discovery, the CoAP web client and each body
wired/wireless link is represented by bandwidth, latency, and av- sensors can exchange the data via AR’s.
erage queuing delay. We adopt a generic model for Multiple Access Thus, the data delivery delay (DDD) of CoMP can be represented
Control (MAC) scheme to focus on the analysis of registration as follows,
delay and handover delay associated with the proposed mobility
scheme. DDDCoMP = NS × {2TC -R (Sc ) + 2TAR-WMMS (Sc )}. (2)
We summarize the notations used in our analysis in Table 2.
So, we obtain the TSD of CoMP as
In the figure, we denote Tx-y (S) by the transmission delay of a
message with size S sent from x to y via the ‘wireless’ link, where TSDCoMP = RDCoMP + DDDCoMP . (3)
each message can experience the failure at the probability of q by
using ‘i.i.d’ error model. Then, Tx-y (S) can be expressed as Tx-y (S) = As shown in Fig. 4, the CoMP-G uses the aggregated POST Re-
[1/(1−q)]×[(S /Bwl )+Lwl ]. In the meantime, we denote Tx-y (S , Hx-y ) quest for Registration and ACK Response for Registration messages
M. Gohar et al. / Future Generation Computer Systems 88 (2018) 309–318 315
between coordinator and WMMS. Thus, we get the RD of COMP-G the CoAP web client by exchanging PUT Request for Binding Update
as and ACK Response for Binding Update messages. Now, each body
sensor and CoAP web client communication is established through
RDCoMP-G = 2TC -FFD (Sc ) + 2TFFD-AR (Sc ) + 2TAR-WMMS (Sc ) . (4) new AR. Accordingly, we get the HD of CoMP as follows.
In CoMP-G, the data delivery delay (DDD) from CoAP web client
HDCOMP = NS × {2TC -FFD (Sc ) + 2TFFD-AR (Sc ) + 2TAR-WMMS (Sc )
to body sensors can be calculated as follows. First, the CoAP web
client registered with WMMS. After registration, the CoAP web + 2TC -R (Sc ) + 2TAR-WMMS (Sc ) + 2TC -FFD (Sc )
client want to find the body sensors to communicate with them. + 2TFFD-AR (Sc ) + 2TAR-WMMS (Sc ) + 2TC -FFD (Sc )
For this purpose, the CoAP web client exchanges GET Request for + 2TFFD-AR (Sc ) + 2TAR-AR (Sc ) + 2TC -R (Sc )}. (7)
Discovery and ACK Response for Discovery messages for body sensor
with WMMS via AR. After discovery, the CoAP web client and each In the proposed CoMP-G scheme, when the group of sensors
moves from previous AR (p-AR) to new AR (n-AR) as shown in
body sensors can exchange the data via AR’s.
Fig. 5. Firstly, each of the body sensors detect the RSS signal, if it
Thus, the data delivery delay (DDD) of CoMP-G can be repre-
drops below by a certain threshold value, the coordinator starts
sented as follows,
handover operation by exchanging PUT Request for Holding and
DDDCoMP-G = 2TC -R (Sc ) + 2TAR-WMMS (Sc ) . (5) ACK Response for Holding with WMMS via p-AR. Then, WMMS also
exchange the PUT Request for Holding and ACK Response for Holding
So, we obtain the TSD of CoMP-G as messages with CoAP web client via AR. The CoAP client updates its
cache for the group.
TSDCoMP-G = RDCoMP-G + DDDCoMP-G . (6) When body sensors change its point of attachment and de-
tached from p-AR and attached to n-AR, coordinator exchanges
PUT Request for Binding Update and ACK Response for Binding Update
4.3. Handover delay (HD)
messages with WMMS. Coordinator updates the CoAP web client
by exchanging PUT Request for Binding Update and ACK Response for
In this section, we consider handover delay in which the group Binding Update messages. Now, each body sensor and CoAP web
of sensors moves from previous AR (p-AR) to new AR (n-AR) as client communication is established through new AR. Accordingly,
shown in Fig. 2. Each of the body sensors first detect the RSS we get the HD of CoMP-G as follows.
signal from the previous AR. When RSS drops below by a certain
threshold value, each of the body sensor starts handover operation HDCOMP-G = 2TC -FFD (Sc ) + 2TFFD-AR (Sc ) + 2TAR-WMMS (Sc )
by exchanging PUT Request for Holding and ACK Response for Holding + 2TC -R (Sc ) + 2TAR-WMMS (Sc ) + 2TC -FFD (Sc )
with WMMS via p-AR. Then, WMMS also exchange the PUT Request
for Holding and ACK Response for Holding messages for each of body
+ 2TFFD-AR (Sc ) + 2TAR-WMMS (Sc ) + 2TC -FFD (Sc )
sensor with CoAP web client via AR. The CoAP client updates its + 2TFFD-AR (Sc ) + 2TAR-AR (Sc ) + 2TC -R (Sc ) . (8)
cache for each of body sensor.
When body sensors change its point of attachment and de- 4.4. Numerical results
tached from p-AR and attached to n-AR, each body sensor ex-
changes PUT Request for Binding Update and ACK Response for Bind- Based on the equations, we compare the performance of the ex-
ing Update messages with WMMS. Each body sensor also updates isting and proposed schemes. For numerical analysis, we configure
316 M. Gohar et al. / Future Generation Computer Systems 88 (2018) 309–318
Table 3
Default parameter values.
Parameter Default Minimum Maximum
Lwl 15 1 55
Ns 10 1 50
q 0.5 0.1 0.9
HAR-WMMS 5 1 55
HAR-AR 3
HC -AR , HC -FFD , HFFD-AR 1
Tq 5
Lw 2
Sc 50 bytes
Bw l 0.25 Mbps
Bw 10 Mbps
5. Conclusion