Sensor Proxy Mobile IPv6 (SPMIPv6)—A Novel Scheme for Mobility Supported IP-WSNs
Identifieur interne : 000597 ( Pmc/Corpus ); précédent : 000596; suivant : 000598Sensor Proxy Mobile IPv6 (SPMIPv6)—A Novel Scheme for Mobility Supported IP-WSNs
Auteurs : Md. Motaharul Islam ; Eui-Nam HuhSource :
- Sensors (Basel, Switzerland) [ 1424-8220 ] ; 2011.
Abstract
IP based Wireless Sensor Networks (IP-WSNs) are gaining importance for their broad range of applications in health-care, home automation, environmental monitoring, industrial control, vehicle telematics and agricultural monitoring. In all these applications, mobility in the sensor network with special attention to energy efficiency is a major issue to be addressed. Host-based mobility management protocols are not suitable for IP-WSNs because of their energy inefficiency, so network based mobility management protocols can be an alternative for the mobility supported IP-WSNs. In this paper we propose a network based mobility supported IP-WSN protocol called Sensor Proxy Mobile IPv6 (SPMIPv6). We present its architecture, message formats and also evaluate its performance considering signaling cost, mobility cost and energy consumption. Our analysis shows that with respect to the number of IP-WSN nodes, the proposed scheme reduces the signaling cost by 60% and 56%, as well as the mobility cost by 62% and 57%, compared to MIPv6 and PMIPv6, respectively. The simulation results also show that in terms of the number of hops, SPMIPv6 decreases the signaling cost by 56% and 53% as well as mobility cost by 60% and 67% as compared to MIPv6 and PMIPv6 respectively. It also indicates that proposed scheme reduces the level of energy consumption significantly.
Url:
DOI: 10.3390/s110201865
PubMed: 22319386
PubMed Central: 3274018
Links to Exploration step
PMC:3274018Le document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en">Sensor Proxy Mobile IPv6 (SPMIPv6)—A Novel Scheme for Mobility Supported IP-WSNs</title>
<author><name sortKey="Islam, Md Motaharul" sort="Islam, Md Motaharul" uniqKey="Islam M" first="Md. Motaharul" last="Islam">Md. Motaharul Islam</name>
</author>
<author><name sortKey="Huh, Eui Nam" sort="Huh, Eui Nam" uniqKey="Huh E" first="Eui-Nam" last="Huh">Eui-Nam Huh</name>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">PMC</idno>
<idno type="pmid">22319386</idno>
<idno type="pmc">3274018</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3274018</idno>
<idno type="RBID">PMC:3274018</idno>
<idno type="doi">10.3390/s110201865</idno>
<date when="2011">2011</date>
<idno type="wicri:Area/Pmc/Corpus">000597</idno>
<idno type="wicri:explorRef" wicri:stream="Pmc" wicri:step="Corpus" wicri:corpus="PMC">000597</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title xml:lang="en" level="a" type="main">Sensor Proxy Mobile IPv6 (SPMIPv6)—A Novel Scheme for Mobility Supported IP-WSNs</title>
<author><name sortKey="Islam, Md Motaharul" sort="Islam, Md Motaharul" uniqKey="Islam M" first="Md. Motaharul" last="Islam">Md. Motaharul Islam</name>
</author>
<author><name sortKey="Huh, Eui Nam" sort="Huh, Eui Nam" uniqKey="Huh E" first="Eui-Nam" last="Huh">Eui-Nam Huh</name>
</author>
</analytic>
<series><title level="j">Sensors (Basel, Switzerland)</title>
<idno type="eISSN">1424-8220</idno>
<imprint><date when="2011">2011</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc><textClass></textClass>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en"><p>IP based Wireless Sensor Networks (IP-WSNs) are gaining importance for their broad range of applications in health-care, home automation, environmental monitoring, industrial control, vehicle telematics and agricultural monitoring. In all these applications, mobility in the sensor network with special attention to energy efficiency is a major issue to be addressed. Host-based mobility management protocols are not suitable for IP-WSNs because of their energy inefficiency, so network based mobility management protocols can be an alternative for the mobility supported IP-WSNs. In this paper we propose a network based mobility supported IP-WSN protocol called Sensor Proxy Mobile IPv6 (SPMIPv6). We present its architecture, message formats and also evaluate its performance considering signaling cost, mobility cost and energy consumption. Our analysis shows that with respect to the number of IP-WSN nodes, the proposed scheme reduces the signaling cost by 60% and 56%, as well as the mobility cost by 62% and 57%, compared to MIPv6 and PMIPv6, respectively. The simulation results also show that in terms of the number of hops, SPMIPv6 decreases the signaling cost by 56% and 53% as well as mobility cost by 60% and 67% as compared to MIPv6 and PMIPv6 respectively. It also indicates that proposed scheme reduces the level of energy consumption significantly.</p>
</div>
</front>
<back><div1 type="bibliography"><listBibl><biblStruct><analytic><author><name sortKey="Akyildiz, I F" uniqKey="Akyildiz I">I.F. Akyildiz</name>
</author>
<author><name sortKey="Su, W" uniqKey="Su W">W. Su</name>
</author>
<author><name sortKey="Sankarasubramaniam, Y" uniqKey="Sankarasubramaniam Y">Y. Sankarasubramaniam</name>
</author>
<author><name sortKey="Cayirci, E" uniqKey="Cayirci E">E. Cayirci</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Kemal, A" uniqKey="Kemal A">A. Kemal</name>
</author>
<author><name sortKey="Mohamed, Y" uniqKey="Mohamed Y">Y. Mohamed</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Luo, X" uniqKey="Luo X">X. Luo</name>
</author>
<author><name sortKey="Zheng, K" uniqKey="Zheng K">K. Zheng</name>
</author>
<author><name sortKey="Pan, Y" uniqKey="Pan Y">Y. Pan</name>
</author>
<author><name sortKey="Wu, Z" uniqKey="Wu Z">Z. Wu</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Rodrigues" uniqKey="Rodrigues">Rodrigues</name>
</author>
<author><name sortKey="Joel, J P C" uniqKey="Joel J">J.P.C. Joel</name>
</author>
<author><name sortKey="Neves" uniqKey="Neves">Neves</name>
</author>
<author><name sortKey="Paulo, A C S" uniqKey="Paulo A">A.C.S. Paulo</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Montenegro, G" uniqKey="Montenegro G">G. Montenegro</name>
</author>
<author><name sortKey="Kushalnagar, N" uniqKey="Kushalnagar N">N. Kushalnagar</name>
</author>
<author><name sortKey="Hui, J W" uniqKey="Hui J">J.W. Hui</name>
</author>
<author><name sortKey="Culler, D E" uniqKey="Culler D">D.E. Culler</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Kushalnagar, N" uniqKey="Kushalnagar N">N. Kushalnagar</name>
</author>
<author><name sortKey="Montenegro, G" uniqKey="Montenegro G">G. Montenegro</name>
</author>
<author><name sortKey="Schumacher, C" uniqKey="Schumacher C">C. Schumacher</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Zach, S" uniqKey="Zach S">S. Zach</name>
</author>
<author><name sortKey="Carsten, B" uniqKey="Carsten B">B. Carsten</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Kim, E" uniqKey="Kim E">E. Kim</name>
</author>
<author><name sortKey="Kaspar, D" uniqKey="Kaspar D">D. Kaspar</name>
</author>
<author><name sortKey="Chevrollier, N" uniqKey="Chevrollier N">N. Chevrollier</name>
</author>
<author><name sortKey="Vasseur, J P" uniqKey="Vasseur J">J.P. Vasseur</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Hui, J W" uniqKey="Hui J">J.W. Hui</name>
</author>
<author><name sortKey="Culler, D E" uniqKey="Culler D">D.E. Culler</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Kong, K S" uniqKey="Kong K">K.-S. Kong</name>
</author>
<author><name sortKey="Lee, W" uniqKey="Lee W">W. Lee</name>
</author>
<author><name sortKey="Han, Y H" uniqKey="Han Y">Y.-H. Han</name>
</author>
<author><name sortKey="Shin, M K" uniqKey="Shin M">M.-K. Shin</name>
</author>
<author><name sortKey="You, H R" uniqKey="You H">H.R. You</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Gundavelli, S" uniqKey="Gundavelli S">S. Gundavelli</name>
</author>
<author><name sortKey="Leung, K" uniqKey="Leung K">K. Leung</name>
</author>
<author><name sortKey="Devarapalli, V" uniqKey="Devarapalli V">V. Devarapalli</name>
</author>
<author><name sortKey="Chowdhury, K" uniqKey="Chowdhury K">K. Chowdhury</name>
</author>
<author><name sortKey="Patil, B" uniqKey="Patil B">B. Patil</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Kim, M S" uniqKey="Kim M">M.S. Kim</name>
</author>
<author><name sortKey="Lee, S K" uniqKey="Lee S">S.K. Lee</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Chalmers, R C" uniqKey="Chalmers R">R.C. Chalmers</name>
</author>
<author><name sortKey="Almeroth, K C" uniqKey="Almeroth K">K.C. Almeroth</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Kim, J H" uniqKey="Kim J">J.H. Kim</name>
</author>
<author><name sortKey="Hong, C S" uniqKey="Hong C">C.S. Hong</name>
</author>
<author><name sortKey="Taeshik, S" uniqKey="Taeshik S">S. Taeshik</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Yang, S" uniqKey="Yang S">S. Yang</name>
</author>
<author><name sortKey="Park, S" uniqKey="Park S">S. Park</name>
</author>
<author><name sortKey="Lee, E J" uniqKey="Lee E">E.J. Lee</name>
</author>
<author><name sortKey="Ryu, J H" uniqKey="Ryu J">J.H. Ryu</name>
</author>
<author><name sortKey="Kim, B S" uniqKey="Kim B">B.S. Kim</name>
</author>
<author><name sortKey="Kim, H S" uniqKey="Kim H">H.S. Kim</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Hwang, S M" uniqKey="Hwang S">S.M. Hwang</name>
</author>
<author><name sortKey="Kim, K J" uniqKey="Kim K">K.J. Kim</name>
</author>
<author><name sortKey="Islam, M M" uniqKey="Islam M">M.M. Islam</name>
</author>
<author><name sortKey="Huh, E N" uniqKey="Huh E">E.N. Huh</name>
</author>
<author><name sortKey="Huang, W" uniqKey="Huang W">W. Huang</name>
</author>
<author><name sortKey="Foo, V" uniqKey="Foo V">V. Foo</name>
</author>
<author><name sortKey="Tolstikov, A" uniqKey="Tolstikov A">A. Tolstikov</name>
</author>
<author><name sortKey="Aung, A" uniqKey="Aung A">A. Aung</name>
</author>
<author><name sortKey="Jayachandran, M" uniqKey="Jayachandran M">M. Jayachandran</name>
</author>
<author><name sortKey="Biswas, J" uniqKey="Biswas J">J. Biswas</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Bag, G" uniqKey="Bag G">G. Bag</name>
</author>
<author><name sortKey="Hamid, M" uniqKey="Hamid M">M. Hamid</name>
</author>
<author><name sortKey="Saif Shams, S M" uniqKey="Saif Shams S">S.M. Saif Shams</name>
</author>
<author><name sortKey="Kim, H K" uniqKey="Kim H">H.K. Kim</name>
</author>
<author><name sortKey="Yoo, S W" uniqKey="Yoo S">S.W. Yoo</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Johnson, D" uniqKey="Johnson D">D. Johnson</name>
</author>
<author><name sortKey="Perkins, C" uniqKey="Perkins C">C. Perkins</name>
</author>
<author><name sortKey="Arkko, J" uniqKey="Arkko J">J. Arkko</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Devarapalli, V" uniqKey="Devarapalli V">V. Devarapalli</name>
</author>
<author><name sortKey="Wakikawa, R" uniqKey="Wakikawa R">R. Wakikawa</name>
</author>
<author><name sortKey="Petrescu, A" uniqKey="Petrescu A">A. Petrescu</name>
</author>
<author><name sortKey="Thubert, P" uniqKey="Thubert P">P. Thubert</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Soliman, H" uniqKey="Soliman H">H. Soliman</name>
</author>
<author><name sortKey="Castelluccia, C" uniqKey="Castelluccia C">C. Castelluccia</name>
</author>
<author><name sortKey="Malki, K El" uniqKey="Malki K">K. El Malki</name>
</author>
<author><name sortKey="Bellier, L" uniqKey="Bellier L">L. Bellier</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Akyildiz, I F" uniqKey="Akyildiz I">I.F. Akyildiz</name>
</author>
<author><name sortKey="Lin, Y B" uniqKey="Lin Y">Y.B. Lin</name>
</author>
<author><name sortKey="Lai, W R" uniqKey="Lai W">W.R. Lai</name>
</author>
<author><name sortKey="Chen, R J" uniqKey="Chen R">R.J. Chen</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Chiang, K H" uniqKey="Chiang K">K.H. Chiang</name>
</author>
<author><name sortKey="Shenoy, N" uniqKey="Shenoy N">N. Shenoy</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Bhavneet, S" uniqKey="Bhavneet S">S. Bhavneet</name>
</author>
<author><name sortKey="Hardeep, S" uniqKey="Hardeep S">S. Hardeep</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Heinzelman, W R" uniqKey="Heinzelman W">W.R. Heinzelman</name>
</author>
<author><name sortKey="Chandrakasan, A" uniqKey="Chandrakasan A">A. Chandrakasan</name>
</author>
<author><name sortKey="Balakrishnan, H" uniqKey="Balakrishnan H">H. Balakrishnan</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Pathan, A S K" uniqKey="Pathan A">A.S.K. Pathan</name>
</author>
<author><name sortKey="Hong, C S" uniqKey="Hong C">C.S. Hong</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Razzaque, M A" uniqKey="Razzaque M">M.A. Razzaque</name>
</author>
<author><name sortKey="Hong, C S" uniqKey="Hong C">C.S. Hong</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Dhanajay, S" uniqKey="Dhanajay S">S. Dhanajay</name>
</author>
<author><name sortKey="Lee, H J" uniqKey="Lee H">H.J. Lee</name>
</author>
<author><name sortKey="Chung, W Y" uniqKey="Chung W">W.Y. Chung</name>
</author>
</analytic>
</biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="research-article"><pmc-dir>properties open_access</pmc-dir>
<front><journal-meta><journal-id journal-id-type="nlm-ta">Sensors (Basel)</journal-id>
<journal-title-group><journal-title>Sensors (Basel, Switzerland)</journal-title>
</journal-title-group>
<issn pub-type="epub">1424-8220</issn>
<publisher><publisher-name>Molecular Diversity Preservation International (MDPI)</publisher-name>
</publisher>
</journal-meta>
<article-meta><article-id pub-id-type="pmid">22319386</article-id>
<article-id pub-id-type="pmc">3274018</article-id>
<article-id pub-id-type="doi">10.3390/s110201865</article-id>
<article-id pub-id-type="publisher-id">sensors-11-01865</article-id>
<article-categories><subj-group subj-group-type="heading"><subject>Article</subject>
</subj-group>
</article-categories>
<title-group><article-title>Sensor Proxy Mobile IPv6 (SPMIPv6)—A Novel Scheme for Mobility Supported IP-WSNs</article-title>
</title-group>
<contrib-group><contrib contrib-type="author"><name><surname>Islam</surname>
<given-names>Md. Motaharul</given-names>
</name>
</contrib>
<contrib contrib-type="author"><name><surname>Huh</surname>
<given-names>Eui-Nam</given-names>
</name>
<xref ref-type="corresp" rid="c1-sensors-11-01865"><sup>*</sup>
</xref>
</contrib>
<aff id="af1-sensors-11-01865">Department of Computer Engineering, College of Electronics and Information, Kyung Hee University, Yongin-si, 446-701, Korea; E-Mail:<email>motahar@khu.ac.kr</email>
</aff>
</contrib-group>
<author-notes><corresp id="c1-sensors-11-01865"><label>*</label>
Author to whom correspondence should be addressed; E-Mail: <email>johnhuh@khu.ac.kr</email>
; Tel.: +82-31-201-3778; Fax: +82-31-204-3778.</corresp>
</author-notes>
<pub-date pub-type="collection"><year>2011</year>
</pub-date>
<pub-date pub-type="epub"><day>1</day>
<month>2</month>
<year>2011</year>
</pub-date>
<volume>11</volume>
<issue>2</issue>
<fpage>1865</fpage>
<lpage>1887</lpage>
<history><date date-type="received"><day>18</day>
<month>12</month>
<year>2010</year>
</date>
<date date-type="rev-recd"><day>20</day>
<month>1</month>
<year>2011</year>
</date>
<date date-type="accepted"><day>23</day>
<month>1</month>
<year>2011</year>
</date>
</history>
<permissions><copyright-statement>© 2011 by the authors; licensee MDPI, Basel, Switzerland.</copyright-statement>
<copyright-year>2011</copyright-year>
<license><license-p><pmc-comment>CREATIVE COMMONS</pmc-comment>
This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution license (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/3.0/">http://creativecommons.org/licenses/by/3.0/</ext-link>
).</license-p>
</license>
</permissions>
<abstract><p>IP based Wireless Sensor Networks (IP-WSNs) are gaining importance for their broad range of applications in health-care, home automation, environmental monitoring, industrial control, vehicle telematics and agricultural monitoring. In all these applications, mobility in the sensor network with special attention to energy efficiency is a major issue to be addressed. Host-based mobility management protocols are not suitable for IP-WSNs because of their energy inefficiency, so network based mobility management protocols can be an alternative for the mobility supported IP-WSNs. In this paper we propose a network based mobility supported IP-WSN protocol called Sensor Proxy Mobile IPv6 (SPMIPv6). We present its architecture, message formats and also evaluate its performance considering signaling cost, mobility cost and energy consumption. Our analysis shows that with respect to the number of IP-WSN nodes, the proposed scheme reduces the signaling cost by 60% and 56%, as well as the mobility cost by 62% and 57%, compared to MIPv6 and PMIPv6, respectively. The simulation results also show that in terms of the number of hops, SPMIPv6 decreases the signaling cost by 56% and 53% as well as mobility cost by 60% and 67% as compared to MIPv6 and PMIPv6 respectively. It also indicates that proposed scheme reduces the level of energy consumption significantly.</p>
</abstract>
<kwd-group><kwd>wireless sensor network</kwd>
<kwd>SPMIPv6</kwd>
<kwd>IP-WSN</kwd>
<kwd>IETF</kwd>
<kwd>6LoWPAN</kwd>
<kwd>IEEE 802.15.4</kwd>
<kwd>IP sensor node</kwd>
</kwd-group>
</article-meta>
</front>
<body><sec><label>1.</label>
<title>Introduction</title>
<p>Recent advancement in micro-electro-mechanical and wireless communication systems have enabled the development of low cost, low power, multifunctional sensor nodes that are small in size and can communicate over short distances [<xref ref-type="bibr" rid="b1-sensors-11-01865">1</xref>
,<xref ref-type="bibr" rid="b2-sensors-11-01865">2</xref>
]. A sensor network is a special type of communication network that is composed of a large number of tiny sensor nodes that are densely deployed either inside the phenomenon or very close to it [<xref ref-type="bibr" rid="b1-sensors-11-01865">1</xref>
]. Sensors are generally equipped with data processing and communication capabilities. The sensing circuitry senses the environment surrounding the sensor and transforms them into an electric signal. The sensor sends such signal, usually via radio transmitter, to the sink node either directly or through other sensor nodes.</p>
<p>In the past, applications of sensor networks were thought to be very specific. The communication protocol of sensor network was also very simple and straightforward. Some researchers were even against the use of the internetworking concept in WSNs for reasons such as the resource constraints for layered architecture, the configuration problems of large numbers of devices, the essence of sensor nodes’ distinct identity, <italic>etc.</italic>
But with the advent of the Internet of things and federated IP-WSNs, this demand is going to be blurred. The huge number of IPv6 addresses, the necessity for end to end communication and advancement of micro-electronics have changed the concept of the research community. Now a tiny sensor node can hold a compatible TCP/IP protocol stack [<xref ref-type="bibr" rid="b3-sensors-11-01865">3</xref>
], so we can now think of using the concept of internetworking protocols in IP-WSNs [<xref ref-type="bibr" rid="b4-sensors-11-01865">4</xref>
]. We can easily think of providing IPv6 address to individual sensor nodes since it provides around 6 × 10<sup>23</sup>
addresses per square meter of the Earth’s space.</p>
<p>The IPv6 over low power wireless personal area network (6LoWPAN) working group of the Internet Engineering Task Force (IETF) defines the manner in which IPv6 communication is to be carried out over IEEE 802.15.4 interface [<xref ref-type="bibr" rid="b5-sensors-11-01865">5</xref>
,<xref ref-type="bibr" rid="b6-sensors-11-01865">6</xref>
]. Although 6LoWPAN helps making the wide implementation of IP-WSN a reality and its end to end communication to the external world feasible, excessive signaling costs for sensor nodes because of too much tunneling through the air makes it difficult. Excessive signaling costs therefore become a barrier for the application of IP-WSNs especially in the case of the mobility scenario of individual sensor nodes or groups of nodes in different areas such as in a patient’s body sensor network, in industrial automation, <italic>etc</italic>
. [<xref ref-type="bibr" rid="b7-sensors-11-01865">7</xref>
]. Nowadays most of the communication protocols are host based, which is practically infeasible for IP-WSNs since individual nodes need to participate in mobility related signaling. PMIPv6 which is a network based protocol, provides mobility support to any IPv6 host within a restricted and topologically localized portion of the network, without requiring the host to participate in any mobility-related signaling.</p>
<p>6LoWPAN based IP-WSNs may use the sensor network compatible PMIPv6 to introduce and to enhance the mobility scenario in a localized domain. With this thinking in mind, in this work we focus on the mobility in IP-WSNs with attention paid to an energy efficient network based communication protocol for IP-WSNs. In this regard, we have proposed the SPMIPv6 for IP-WSNs. In our proposed scheme we use sensor network-based localized mobility anchors, mobile access gateways, and multiple smart and fully functional sensor nodes which are IPv6 header stack-enabled. These all IP devices including the sensor nodes make it feasible to implement the SPMIPv6 protocol over IP-WSNs.</p>
<p>There are different application areas where IP-WSNs can be used such as industrial control, structural monitoring, healthcare, smart home, vehicle telematics, agricultural monitoring <italic>etc</italic>
. [<xref ref-type="bibr" rid="b8-sensors-11-01865">8</xref>
]. In these scenarios, node to node communication is very important since these are the collaborative functions. In these cases IP-WSNs based on a mesh approach can enhance the communication scenario significantly, whereby individual sensor nodes can act as routers or fully functional devices, which is discussed in the route over routing issue in 6LoWPAN [<xref ref-type="bibr" rid="b8-sensors-11-01865">8</xref>
,<xref ref-type="bibr" rid="b9-sensors-11-01865">9</xref>
]. Moreover SPMIPv6 based IP-WSNs facilitate node to node seamless communication in different cases of the individual sensor node and sensor network mobility scenarios.</p>
<p>The main contributions of this paper are as follows:
<list list-type="alpha-lower"><list-item><p>A novel IP-WSN architecture solely based on PMIPv6 and named SPMIPv6 is proposed for energy efficient mobility of individual sensor nodes or a group of sensor nodes. To the best of our knowledge this is the first paper reporting on a sensor network based localized mobility management protocol in an IP-WSN domain with special consideration to energy efficiency.</p>
</list-item>
<list-item><p>We address the applicability of mobility issues of individual or group of IP sensor nodes in a patient care scenario.</p>
</list-item>
<list-item><p>We propose functional architecture, and the respective message formats, sequence diagram, network model and evaluate the performance of the proposed protocol architecture.</p>
</list-item>
<list-item><p>Mathematical analysis and simulation experiments are conducted to show the effectiveness of the proposed scheme. Our simulation results show that the proposed scheme effectively reduces the signaling cost and mobility cost in terms of the number of IP-WSNs and hops as compared to MIPv6 and PMIPv6, respectively. There is also a significant improvement in energy consumption for data payload and IP-WSN node density in the network.</p>
</list-item>
</list>
</p>
<p>The rest of the paper is organized as follows. Section 2 reviews background data related to PMIPv6 and 6LoWPAN. The proposed SPMIPv6 protocol architecture, along with its mobility scenarios, sequence diagram and message formats are presented in Section 3. Section 4 describes performance analysis and evaluation, Section 5 shows the experimental results, and finally Section 6 concludes the paper.</p>
</sec>
<sec><label>2.</label>
<title>Background</title>
<sec><label>2.1.</label>
<title>Overview of PMIPv6</title>
<p>The foundation of PMIPv6 is based on MIPv6 in the sense that it extends MIPv6 signaling and reuses many concepts such as the home agent (HA) functionality [<xref ref-type="bibr" rid="b10-sensors-11-01865">10</xref>
,<xref ref-type="bibr" rid="b11-sensors-11-01865">11</xref>
]. However, PMIPv6 is designed to provide network-based mobility management support to a Mobile Node (MN) in a topologically localized domain [<xref ref-type="bibr" rid="b12-sensors-11-01865">12</xref>
]. Therefore, an MN is free from participation in any mobility-related signaling, and the proxy mobility agent in the serving network performs mobility-related signaling on behalf of the MN. Once an MN enters its PMIPv6 domain and performs access authentication, the serving network ensures that the MN is always on its home network and can obtain its home address on any access network. The serving network assigns a unique home network prefix to each MN, and conceptually this prefix always follows the MN wherever it moves within a PMIPv6 domain. From the perspective of the MN, the entire PMIPv6 domain appears as its home network. Accordingly, it is needless to configure the care of address at the MN. The new functional entities of PMIPv6 are the mobile access gateway (MAG) and local mobility anchor (LMA) [<xref ref-type="bibr" rid="b13-sensors-11-01865">13</xref>
]. The MAG typically runs on the access router (AR). The main role of the MAG is to detect the MN’s movements and initiate mobility-related signaling with the LMA on behalf of the MN. In addition, the MAG establishes a tunnel with the LMA for enabling the MN to use an address from it home network prefix and emulates the MN’s home network on the access network for each MN. On the other hand, the LMA is similar to the HA in MIPv6. However, it has additional capabilities required to support PMIPv6. The main role of the LMA is to maintain reachability to the MN’s address while it moves around within a PMIPv6 domain, and the LMA includes a binding cache entry for each currently registered MN. The binding cache entry maintained at the LMA is more extended than that of the HA in MIPv6 with some additional fields such as the MN identifier, the MN’s home network prefix, a flag indicating a proxy registration, and the interface identifier of the bidirectional tunnel between the LMA and MAG. Such information associates an MN with its serving MAG, and enables the relationship between the MAG and LMA to be maintained.</p>
</sec>
<sec><label>2.2.</label>
<title>6LoWPAN</title>
<p>The 6LoWPAN working group of the IETF has defined an adaptation layer for sending IPv6 packets over IEEE 802.15.4. The goal of 6LoWPAN is to reduce the sizes of IPv6 packets to make them fit in 127 byte IEEE 802.15.4 frames. The 6LoWPAN proposal consists of a header compression scheme, a fragmentation scheme, and a method for framing IPv6 link local addresses into IEEE 802.15.4 networks [<xref ref-type="bibr" rid="b5-sensors-11-01865">5</xref>
,<xref ref-type="bibr" rid="b6-sensors-11-01865">6</xref>
]. The proposal also specifies enhanced scalabilities and mobility of sensor networks. The challenge to 6LoWPAN lies in the sizable differences between an IPv6 network and an IEEE 802.15.4 network. The IPv6 network defines a maximum transmission unit as 1,280 bytes, whereas the IEEE 802.15.4 frame size is 127 octets. Therefore, the adaptation layer between the IP layer and the MAC layer must transport IPv6 packets over IEEE 802.15.4 links. The adaptation layer is responsible for fragmentation, reassembly, header compression and decompression, mesh routing, and addressing for packet delivery under the mesh topology. The 6LoWPAN protocol supports a scheme to compress the IPv6 header from 40 bytes to 2 bytes [<xref ref-type="bibr" rid="b7-sensors-11-01865">7</xref>
,<xref ref-type="bibr" rid="b14-sensors-11-01865">14</xref>
].</p>
</sec>
<sec><label>2.3.</label>
<title>Related Work</title>
<p>In comparison to conventional WSNs, IP-WSN provides flexibility to access and manage individual sensor nodes locally or from remote sites through the Internet. This specific issue provides great significance to different mission specific applications. Our paper focuses on the energy efficient mobility of both IP sensor nodes and sensor networks which is based on PMIPv6 and 6LoWPAN. There are few approaches proposed in the literature regarding IP-WSNs and their mobility issues. RFC 5213 gives a complete description of PMIPv6 [<xref ref-type="bibr" rid="b11-sensors-11-01865">11</xref>
]. RFC 4944 depicts the overall aspects of 6LoWPAN, the packet format provided by IETF to ensure IPv6 communication over low-power, wireless personal area networks. In [<xref ref-type="bibr" rid="b9-sensors-11-01865">9</xref>
] the authors represent the overall scenario for extending IP to LoWPAN such as 6LoWPAN adaptation layer, header format encapsulation and compression and finally focus on addressing, routing, auto configuration and neighbor discovery issues. In [<xref ref-type="bibr" rid="b14-sensors-11-01865">14</xref>
], its authors propose a network mobility protocol to support 6LoWPAN, but they do not consider the 6LoWPAN node mobility. The respective authors only consider network mobility which is performed with the help of mobile routers as well as they also do not consider unique addresses for each sensor node. In [<xref ref-type="bibr" rid="b8-sensors-11-01865">8</xref>
] the authors describe some real life design and application spaces for 6LoWPANs which show the importance of 6LoWPANs in near future. In [<xref ref-type="bibr" rid="b15-sensors-11-01865">15</xref>
] the authors propose a dual addressing scheme for 6LoWPAN-based WSNs. It combines a global unicast address to cope with association link changes and node mobility, and it links local addresses to reduce the overhead. Although our proposed scheme considers global unicast address only, it is energy efficient because of using SPMIPv6 for communication protocol.</p>
</sec>
</sec>
<sec><label>3.</label>
<title>Proposed SPMIPv6 Protocol</title>
<sec><label>3.1.</label>
<title>SPMIPv6 Protocol Architecture</title>
<p>To introduce energy efficient mobility we propose Sensor Proxy Mobile IPv6 (SPMIPv6) for IP-WSN. It is a localized mobility management protocol based on PMIPv6. The SPMIPv6 architecture consists of a sensor network-based localized mobility anchor (SLMA), a sensor network-based mobile access gateway (SMAG) and many fully functional IPv6 header stack enabled IP sensor nodes. We discuss the individual module of the proposed architecture with the help of <xref ref-type="fig" rid="f1-sensors-11-01865">Figure 1</xref>
.</p>
<sec><label>3.1.1.</label>
<title>SLMA</title>
<p>The SLMA acts as a topological anchor point for the entire SMAG and IP sensor nodes. The main role of the SLMA is to maintain accessibility to the sensor node while the node moves within or outside of the SPMIPv6 domain. The SLMA includes a binding cache entry for each sensor node, encapsulations and decapsulation section and SMAG information table. The binding cache entry at the SLMA is used for holding the information of the mobile sensor node. It includes different information such as a sensor node address, the sensor node’s home network prefix, and a flag bit indicating sensor proxy registration.</p>
<p>The SLMA has sufficient memory to hold all of these necessary records. It has sufficient power supply and processing capability. It also acts as the interfacing device between SPMIPv6 domain and PMIPv6 domain. As an interfacing entity, it facilitates the communication of the IP-WSN with the Internet world. In this scheme, authentication, authorization, and accounting (AAA) service has been integrated within SLMA. We name this integrated service as sensor network based authentication, authorization, and accounting (SAAA) schemes. The SAAA scheme helps the SMAG and sensor node to obtain secured mobility in the SPMIPv6 domain. It also facilitates authentication services for each fully functional sensor nodes.</p>
</sec>
<sec><label>3.1.2.</label>
<title>SMAG</title>
<p>The SMAG acts like a sink node in a traditional sensor network. In SPMIPv6 it acts like an access gateway router with a main function of detecting sensor node movement and initiating mobility-related signaling with the sensor node’s SLMA on behalf of the sensor node. It can move with its member sensor node as a small IP-WSN domain similar to the body sensor network of a patient. It consists of different functional module such as routing, neighbor discovery, sensor information table, adaptation module and interfacing module to the sensor node and SLMA. Routing module performs the efficient data transmission among individual sensor node and facilitates the end to end communication. Neighbor discovery module performs neighbor discovery and duplicate address detection functionality. Adaptation module performs the task of transmitting IPv6 packet over IEEE 802.15.4 link as mentioned in 6LoWPAN adaptation layer. The sensor information table provides the up to date information of sensor nodes to the SLMA. It works with the close association of the binding cache entry of the SLMA, and the two interfacing modules communicate with the SLMA and the sensor nodes.</p>
</sec>
<sec><label>3.1.3.</label>
<title>IP-Sensor Node</title>
<p>SPMIPv6 domain consists of numerous sensor nodes based on IPv6 addresses. We consider the domain as a federated IP sensor domain. There are two types of sensor node. One type contains the tiny TCP/IP communication protocol stack with adaptation layer and IEEE 802.15.4 interface. This type can forward information to other node of similar type as well as information sensing from the environment. Actually this type of sensor node acts as a mini sensor router. The other type of sensor node has the protocol stack and environment sensing capability but can forward the sensed information to nearby mini sensor router node. However, both of these types are able to perform end to end communication.</p>
</sec>
</sec>
<sec><label>3.2.</label>
<title>Operational Architecture of SPMIPv6</title>
<p><xref ref-type="fig" rid="f2-sensors-11-01865">Figure 2</xref>
shows the detail operational architecture of the SPMIPv6 which includes SLMA, SMAG and IP sensor nodes. And it shows how these entities communicate each other by different types of interfaces. The SMAG needs two or more interfaces for the communication with different access network such as SPMIPv6 based IP-WSN and external PMIPv6 network. It includes the network layer, adaptation layer and physical layer functionality. The network layer provides different functionality such as addressing, routing, neighbor discovery and the data structure for holding IP sensor node information. The most important layer is adaptation that ensures mesh routing, compression and decompression, and fragmentation and reassembly. The physical layer provides access to different physical interfaces. SLMA holds network related information such as binding cache entry, encapsulation and decapsulation. Binding cache entry provides data structure to hold different information such as new SPMIPv6 flag, link local address for each interface, home prefix, bi-directional tunnel interface identifier, access technology and time stamp. Finally, the IP sensor node works as a very smart tiny 6LoWPAN based node. It holds a tiny TCP/IP protocol stack. Moreover it holds the basic functionality of adaptation layer. All the sensor nodes consist of IPv6 addresses for local and global communications.</p>
</sec>
<sec><label>3.3.</label>
<title>Application Scenarios of IP-WSN based on SPMIPv6</title>
<p>This section includes different SPMIPv6 based IP-WSN applications scenarios [<xref ref-type="bibr" rid="b8-sensors-11-01865">8</xref>
] briefly. A complete description is beyond the scope of this paper.</p>
<sec><label>3.3.1.</label>
<title>Industrial Monitoring</title>
<p>SPMIPv6 based IP-WSN applications for industrial monitoring can be related with a broad range of methods to increase productivity, energy efficiency, and safety of industrial operations in engineering facilities and manufacturing plants. Many industries currently use time-consuming and expensive manual monitoring to predict failures and to schedule maintenance or replacements in order to avoid costly manufacturing downtime. A SPMIPv6 based IP-WSN could be inexpensively installed and provide more frequent and more reliable data. The deployment of SPMIPv6 based IP-WSNs can reduce equipment downtime and eliminate manual equipment monitoring that is costly to be carried out. Additionally, data analysis functionality can be placed into the network, eliminating the need for manual data transfer and analysis.</p>
</sec>
<sec><label>3.3.2.</label>
<title>Structural Monitoring</title>
<p>Intelligent monitoring in facility management can make safety checks and periodic monitoring of the architecture status highly efficient. Powered nodes can be included in the design phase of a construction or battery-equipped nodes can be added afterwards. All nodes are static and manually deployed. Some data such as normal room temperature is not critical for security protection, but event-driven emergency data must be handled in very critical manner.</p>
</sec>
<sec><label>3.3.3.</label>
<title>Healthcare</title>
<p>SPMIPv6 based IP-WSNs are envisioned to be heavily used in healthcare environments. Although hospital scenarios can be handled differently, IP-WSN provides great potential to ease the development of new services by getting rid of cumbersome wires and simplifying patient care in hospitals and for home care as the World is rapidly graying. The worldwide population of elderly people over age 65 is expected to be more than double from 357 million to 761 million by 2025 [<xref ref-type="bibr" rid="b16-sensors-11-01865">16</xref>
]. The speed with which this age-structural change is taking place implies an urgent need for solutions that will relieve the mounting pressure on our health-care systems as well as support a better quality of life and quality of care for our aged.</p>
</sec>
<sec><label>3.3.4.</label>
<title>Connected Home</title>
<p>The connected home or smart home is with no doubt an area where SPMIPv6 based IP-WSN can be used to support an increasing number of services: home safety/security, home automation and control, personal healthcare, smart appliances and home entertainment systems. In home environments SPMIPv6 based IP-WSN networks typically comprise a few dozen units and probably in the near future a few hundreds of nodes of various natures: IP sensors, actuators and connected objects.</p>
</sec>
<sec><label>3.3.5.</label>
<title>Vehicle Telematics</title>
<p>SPMIPv6 based IP-WSN play an important role in intelligent transportation systems. Incorporated in roads, vehicles, and traffic signals, they contribute to the improvement of safety of transporting systems. Through traffic or air-quality monitoring, they increase the possibilities in terms of traffic flow optimization and help reducing road congestion.</p>
</sec>
<sec><label>3.3.6.</label>
<title>Agricultural Monitoring</title>
<p>Accurate temporal and spatial monitoring can significantly increase agricultural productivity. Due to natural limitations, such as a farmers’ inability to check the crop at all times of day or inadequate measurement tools, luck often plays too large a role in the success of harvests. Using a SPMIPv6 based IP-WSN, indicators such as temperature, humidity, soil condition, can be automatically monitored without labor intensive field measurements. For example, SPMIPv6 based IP-WSN could provide precise information about crops in real time, enabling businesses to reduce water, energy, and pesticide usage and enhancing environment protection. The sensing data can be used to find optimal environments for the plants. In addition, the data on the planting condition can be saved by sensor tags, which can be used in supply chain management.</p>
</sec>
</sec>
<sec><label>3.4.</label>
<title>Mobility Scenario of IP-WSN Based on SPMIPv6</title>
<p>To represent mobility scenarios, we consider a state-of-the-art technology based patient care unit in a specialized hospital. <xref ref-type="fig" rid="f3-sensors-11-01865">Figure 3</xref>
represent such type of scenario where a patient can get special care both in the hospital and personal home care and from a remote specialized hospital. In this scenario, we try to depict different type of mobility in SPMIPv6 environment [<xref ref-type="bibr" rid="b17-sensors-11-01865">17</xref>
]. Sensor nodes are deployed on the body of the patients as well as all over the environment. The patient care unit ensures real time care and observation of the patients from a central specialized doctor’s forum. In case of emergency, patient can move from one place to another with its complete set-up so that seamless connectivity with the sophisticated medical equipment remains established and doctor can monitor the patient online from the central doctor’s research group. All the floors are considered as single SPMIPv6 domain. Inside the SPMIPv6 domain there are six floors considered as individual SMAG domain.</p>
<p>The mobility issue considered in this scenario are: Case-I: Movement of nodes within the same SMAG domain of the SPMIPv6 domain, Case-II: Movement of nodes between different SMAGs of the same SPMIPv6 domain, Case-III: Movement of nodes between different SMAGs of different SPMIPv6 domains, Case-IV: Movement of a SMAG-based personal area network (PAN) within the same SPMIPv6 domain, Case-V: Movement of a SMAG-based PAN between different SPMIPv6 domains, Case-VI: Patient monitoring in personal home environment. These scenarios are explained below:
<list list-type="simple"><list-item><p>Case-I: In this case, the mobility of the nodes will be handled by the appropriate SMAG, without the involvement of the SLMA. This, the simplest mobility scenario, arises frequently in hospital management: a patient can move within the PAN of a single branch of the hospital for different purposes such as exercise and getting fresh air.</p>
</list-item>
<list-item><p>Case-II: In this case, mobility will be handled by the appropriate SMAG with minimal initiative from the SLMA. The initial coordination will be performed by the SLMA alone; then the SMAG will oversee the remaining procedures. In our hospital management model, a patient can move from one PAN to another PAN in the same branch of the hospital.</p>
</list-item>
<list-item><p>Case-III: In this case, mobility is inter-domain, using the public PMIPv6 domain. The LMA, AAA, and SLMA will coordinate with one other. In our hospital management model, a patient can move on an emergency basis from one PAN of a hospital branch to a PAN of another branch of the same hospital.</p>
</list-item>
<list-item><p>Case-IV: In this case, mobility is based on the network mobility (NEMO) protocol [<xref ref-type="bibr" rid="b14-sensors-11-01865">14</xref>
], confined to the same domain. Only the SLMA and corresponding SMAGs will be involved. In our hospital management model, a patient with the whole set up can move from one PAN to another PAN.</p>
</list-item>
<list-item><p>Case-V: This case is also based on NEMO protocol, but is much different from Case-IV. In our hospital management model, a patient can move on an emergency basis with its whole setup from one branch of a hospital to the more specialized branch of the same hospital.</p>
</list-item>
<list-item><p>Case-VI: Due to the increasing number of aging demographic group, we consider this case so that a patient can be monitor continuously from the patient’s personal environment as discussed in our recent paper.</p>
</list-item>
</list>
</p>
<p>Although some of the mobility scenarios may seem complicated in case of IP based wireless sensor network, still they have been considered for the future research. Because of the essence of huge deployment of IP sensor network in health care, departmental store and industrial automation, this mobility scenario will eventually come true in the near future.</p>
</sec>
<sec><label>3.5.</label>
<title>Message Flow in SPMIPv6</title>
<p>In the SPMIPv6 architecture authentication features are integrated in SLMA instead of performing these two functions separately. Proxy binding update message and SAAA query message are combined together and named as binding update and authentication query. As well as SAAA reply and proxy binding acknowledge message are merged together and named as binding acknowledge and authentication reply. For this reason the number of communications is greatly reduced in SPMIPv6 with comparison to conventional PMIPv6. The reduced communication scenario has been drawn and compared with the conventional PMIPv6 sequence diagram. The steps of the sequence diagram in both PMIPv6 and SPMIPv6 are discussed below.</p>
<p><xref ref-type="fig" rid="f4-sensors-11-01865">Figure 4(a)</xref>
depicts the sequence diagram of the message flow with respect to PMIPv6. For the simplicity in <xref ref-type="fig" rid="f4-sensors-11-01865">Figure 4(a)</xref>
, we combine more than one communication within single step.</p>
<list list-type="simple"><list-item><p>Step 1: When a sensor node first attaches to a SMAG domain, the access authentication procedure is performed using the sensor node address.</p>
</list-item>
<list-item><p>Step 2: After successful access authentication, the SMAG obtains the sensor node’s profile from the AAA service policy store. This profile contains the sensor node’s address, SLMA address, supported address configuration mode, and other associated information.</p>
</list-item>
<list-item><p>Step 3: The SMAG sends a proxy binding update (PBU) message, including the MN address, to the sensor node’s SLMA on behalf of the sensor node.</p>
</list-item>
<list-item><p>Step 4: Once the SLMA receives the PBU message, it checks the policy store to ensure that the sender is authorized to send the PBU message. If the sender is a trusted SMAG, the SLMA accepts the PBU message.</p>
</list-item>
<list-item><p>Step 5: The SLMA sends a proxy binding acknowledgment (PBA) message, including the MN’s home network prefix option, and establishes a route for the sensor node’s home network prefix over the tunnel to the SMAG.</p>
</list-item>
</list>
<p><xref ref-type="fig" rid="f4-sensors-11-01865">Figure 4(b)</xref>
shows the sequence diagram of the overall message flow with respect to SPMIPv6. The number of communications is noticeably reduced in SPMIPv6 with comparison to conventional PMIPv6 shown in <xref ref-type="fig" rid="f4-sensors-11-01865">Figure 4(a)</xref>
.</p>
<list list-type="simple"><list-item><p>Step 1: When the location of an IP sensor node is changed, it sends solicitation message for the nearest SMAG discovery mechanism.</p>
</list-item>
<list-item><p>Step 2: SMAG sends binding update and authentication query to SLMA integrated with SAAA.</p>
</list-item>
<list-item><p>Step 3: In response to the binding update and authentication query message, SLMA integrated with SAAA send back binding acknowledge and authentication reply message.</p>
</list-item>
<list-item><p>Step 4: Finally SMAG send the advertisement message to respective IP sensor node. And thus the IP sensor node is connected to the nearest SMAG.</p>
</list-item>
<list-item><p>Step 5: Now the sensor node is able to communicate with the corresponding node based on SPMIPv6. Thus data can be transmitted from IP sensor node to correspondence node and <italic>vice versa</italic>
.</p>
</list-item>
</list>
</sec>
<sec><label>3.6.</label>
<title>Proxy Binding Message Format of SPMIPv6</title>
<p>In the proposed proxy binding update (PBU) and proxy binding acknowledgement (PBA) messages in <xref ref-type="fig" rid="f5-sensors-11-01865">Figure 5</xref>
, we have specified a flag bit S. If this S flag is set, it indicates SMIPv6 operations. If the S bit is not set, this indicates non-SPMIPv6 operations. The meanings and descriptions of the other flags are described in different request for comments (RFC) [<xref ref-type="bibr" rid="b11-sensors-11-01865">11</xref>
,<xref ref-type="bibr" rid="b18-sensors-11-01865">18</xref>
–<xref ref-type="bibr" rid="b20-sensors-11-01865">20</xref>
]. The mobility options header plays an important role for the different types of mobility scenario. Some of the mobility header options are hand off indicators options, access technology type options, link layer identifier options, link local address options and time stamp options.</p>
</sec>
<sec><label>3.7.</label>
<title>Gateway Router Solicitation and Advertisement Message Format of SPMIPv6</title>
<p><xref ref-type="fig" rid="f6-sensors-11-01865">Figure 6</xref>
depicts router solicitation (RS) and router advertisement (RA) message format of SPMIPv6. <xref ref-type="fig" rid="f6-sensors-11-01865">Figure 6</xref>
(a) shows the RS message which is sent by IP-WSN sensor node. The IEEE 802.15.4 MAC header’s source and destinations address set to the source and destination sensor node’s MAC address. Dispatch of IP-WSN addressing header indicates the compressed IPv6 header. Header compression section compresses different fields of IP-WSN addressing header. Router solicitation message’s RS options enable IP-WSN gateway to obtain the sensor node’s MAC address, link-local address and sensor node’s ID. The RA message format has two options such as home network prefix (HNP) and address options. The HNP options are used to emulate IP-WSN sensor node’s home network.</p>
</sec>
</sec>
<sec><label>4.</label>
<title>Performance Analysis and Evaluation</title>
<p>For analyzing signaling costs, we use a two-dimensional (2D) random walk model [<xref ref-type="bibr" rid="b21-sensors-11-01865">21</xref>
–<xref ref-type="bibr" rid="b23-sensors-11-01865">23</xref>
] based on the properties of regular, absorbing Markov chains. Random walk mobility models are designed for dynamic location areas and are suitable for modeling user movement when mobility is generally confined to a limited geographical area. Such scenarios include homes, vehicles, hospitals, and department stores.</p>
<sec><label>4.1.</label>
<title>Network Mobility Model</title>
<p>Mobility of sensor nodes and the network is the major advantage of IP-WSNs over conventional static wireless sensor networks. In this paper, mobility is the key concern in the design and performance analysis of IP-WSNs. The mobility model plays a key role in studying different mobility management strategies such as registration, handoff, and authentication <italic>etc.</italic>
A mobility model with minimum assumptions and simple to analyze is very useful for an IP-WSN. Most of wireless network performance studies assume that the coverage areas are configured as a hexagonal or square shaped. We assume that IP-WSN networks to be configured with hexagonal topology. Sensor nodes for an IP-WSN area are assumed to have identical movement patterns within and across IP-WSN. A 2D hexagonal random walk mobility model can be used to study the movement pattern of the movable sensor nodes. In this paper, we will use a network model subject to some modification for the six-layer personal area network model, with n = 6. In our network model, an IP-WSN consists of a cluster of hexagonal sensor nodes as shown in <xref ref-type="fig" rid="f7-sensors-11-01865">Figure 7</xref>
[<xref ref-type="bibr" rid="b21-sensors-11-01865">21</xref>
].</p>
<p>The SMAG at the center of the IP-WSN area is sublayer 0. The six-subarea clusters are shown in <xref ref-type="fig" rid="f7-sensors-11-01865">Figure 7</xref>
; lines 1–3 divide the cluster into six equal pieces. Exchange of any two pieces has no effect on the structure of the cluster. Sensor nodes in cells of the same type will leave the cells with the same routing pattern. A sensor node can move to any one of its six neighbors with a uniform probability of 1/6. Each sensor node is denoted by , where x indicates that the SMAG is in subarea x, and y is one of the types of subarea x. States <5, 0>, <5, 1>, <5, 2>, <5, 3> and <5, 4> are in the boundary of the IP-WSN and therefore called the boundary states. The state transition diagram of the regular Markov chain corresponding to the random walk model for the six-layer IP-WSN area is shown in <xref ref-type="fig" rid="f7-sensors-11-01865">Figure 7</xref>
. Movement into any boundary state indicates inter-IP-WSN mobility, which can be used to study binding update costs.</p>
</sec>
<sec sec-type="methods"><label>4.2.</label>
<title>Analysis of Signaling Costs</title>
<p>The state transition diagram in <xref ref-type="fig" rid="f7-sensors-11-01865">Figure 7</xref>
shows that there are no transient sets in the model, but only a single ergodic set with only one cyclic class. Hence, the properties of regular Markov chains can be exploited to analyze the behavior of the proposed model [<xref ref-type="bibr" rid="b22-sensors-11-01865">22</xref>
].</p>
<p>Let P be the regular transition probability matrix; then the steady state probability vector π can be solved using the following equations:
<disp-formula><mml:math id="M1"><mml:mrow><mml:mi>π</mml:mi>
<mml:mi>P</mml:mi>
<mml:mo>=</mml:mo>
<mml:mi>π</mml:mi>
<mml:mo> </mml:mo>
<mml:mo> </mml:mo>
<mml:mtext>and </mml:mtext>
<mml:mo> </mml:mo>
<mml:munderover><mml:mo>∑</mml:mo>
<mml:mrow><mml:mi>i</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mi>m</mml:mi>
</mml:munderover>
<mml:mrow><mml:msub><mml:mrow><mml:mi>π</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>Here, m is the number of states and P is the fundamental matrix for the regular Markov chain. This is given by:
<disp-formula><mml:math id="M2"><mml:mrow><mml:mi>Z</mml:mi>
<mml:mo>=</mml:mo>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msub><mml:mi>Z</mml:mi>
<mml:mi mathvariant="italic">ij</mml:mi>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
<mml:mo>=</mml:mo>
<mml:msup><mml:mrow><mml:mrow><mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:mi>I</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi>P</mml:mi>
<mml:mo>+</mml:mo>
<mml:mi>A</mml:mi>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mo>−</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:math>
</disp-formula>
where
<list list-type="order"><list-item><p><italic>A</italic>
is a limiting matrix determined by <italic>P</italic>
, and the powers of <italic>P<sup>n</sup>
</italic>
approach the probability matrix <italic>A</italic>
;</p>
</list-item>
<list-item><p>Each row of <italic>A</italic>
consists of the same probability vector π = {π<sub>1</sub>
,π<sub>2</sub>
,.....π<sub><italic>n</italic>
</sub>
}, <italic>i.e.</italic>
, <italic>A</italic>
= ξπ, where ξ is the column vector with all entries equal to 1; and</p>
</list-item>
<list-item><p><italic>I</italic>
is the identity matrix.</p>
</list-item>
</list>
</p>
<p>The matrix <italic>Z</italic>
can be used to study the behavior of the regular Markov chain, and, using this matrix, one can compute the mean number of times that the process is in a particular state.</p>
<p>Let <italic>Y<sub>j</sub>
</italic>
(<italic>k</italic>
) is the number of times that a process is in state <italic>S<sub>j</sub>
</italic>
in the first <italic>k</italic>
steps; then <italic>M<sub>i</sub>
</italic>
[<italic>y</italic>
(<italic>k</italic>
)], the mean number of times the process is in state <italic>S<sub>j</sub>
</italic>
starting from state <italic>S<sub>i</sub>
</italic>
, is given by:
<disp-formula><mml:math id="M3"><mml:mrow><mml:msub><mml:mi>M</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mrow><mml:mo>[</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi>y</mml:mi>
</mml:mrow>
<mml:mi>j</mml:mi>
</mml:msub>
<mml:msup><mml:mrow></mml:mrow>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo>]</mml:mo>
</mml:mrow>
<mml:mo>→</mml:mo>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mi>Z</mml:mi>
<mml:mi mathvariant="italic">ij</mml:mi>
</mml:msub>
<mml:mo>−</mml:mo>
<mml:msub><mml:mrow><mml:mi>π</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:mi>k</mml:mi>
<mml:msub><mml:mrow><mml:mi>π</mml:mi>
</mml:mrow>
<mml:mi>j</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>The total number of boundary updates in <italic>k</italic>
steps, starting from state <italic>S<sub>i</sub>
</italic>
, can be computed from the total number of times that the process is in the boundary states starting from state <italic>S</italic>
<sub><italic>j</italic>
</sub>
, the initial state. The average number of location updates (<italic>U</italic>
<sub><italic>bu</italic>
</sub>
) in the analytical model, is given by:
<disp-formula><mml:math id="M4"><mml:mrow><mml:msub><mml:mi>U</mml:mi>
<mml:mi mathvariant="italic">bu</mml:mi>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:msub><mml:mi>M</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msub><mml:mi>y</mml:mi>
<mml:mn>1</mml:mn>
</mml:msub>
<mml:msup><mml:mrow></mml:mrow>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mi>M</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msub><mml:mi>y</mml:mi>
<mml:mn>2</mml:mn>
</mml:msub>
<mml:msup><mml:mrow></mml:mrow>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:msub><mml:mi>M</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msub><mml:mi>y</mml:mi>
<mml:mn>3</mml:mn>
</mml:msub>
<mml:msup><mml:mrow></mml:mrow>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:msub><mml:mi>M</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msub><mml:mi>y</mml:mi>
<mml:mn>4</mml:mn>
</mml:msub>
<mml:msup><mml:mrow></mml:mrow>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
<disp-formula><mml:math id="M5"><mml:mrow><mml:mrow><mml:mtext>So</mml:mtext>
<mml:mo>:</mml:mo>
<mml:mtext> </mml:mtext>
</mml:mrow>
<mml:msub><mml:mi>U</mml:mi>
<mml:mi mathvariant="italic">bu</mml:mi>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:munderover><mml:mo>∑</mml:mo>
<mml:mrow><mml:mi>n</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mn>4</mml:mn>
</mml:munderover>
<mml:mrow><mml:msub><mml:mrow><mml:mi>M</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi>y</mml:mi>
</mml:mrow>
<mml:mi>n</mml:mi>
</mml:msub>
<mml:msup><mml:mrow></mml:mrow>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
where 1, 2, 3 and 4 are the boundary states in the model:</p>
<p>Generalizing:
<disp-formula><mml:math id="M6"><mml:mrow><mml:msub><mml:mi>U</mml:mi>
<mml:mi mathvariant="italic">bu</mml:mi>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:munderover><mml:mo>∑</mml:mo>
<mml:mrow><mml:mi>n</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mi>α</mml:mi>
</mml:munderover>
<mml:mrow><mml:msub><mml:mi>M</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi>y</mml:mi>
</mml:mrow>
<mml:mi>n</mml:mi>
</mml:msub>
<mml:msup><mml:mrow></mml:mrow>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mi>k</mml:mi>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:msup>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>We can use the above equation to determine the number of binding update messages. Because we need to send a binding update message whenever the sensor node moves between IP-WSNs, each time a node enters a boundary state, a binding update message is generated. Therefore, we need to determine the expected number of times that the process enters into a boundary state within k steps.</p>
<p>Thus, sensor nodes need to send <italic>U<sub>bu</sub>
</italic>
binding update messages, given that the sensor node experiences a total of k transitions between SMAGs. Therefore, the ratio of intra-IP-WSN mobility is denoted as <italic>M</italic>
<sub>int<italic>ra_IP_WSN</italic>
</sub>
and is expressed by:
<disp-formula><mml:math id="M7"><mml:mrow><mml:msub><mml:mrow><mml:mi>M</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>int</mml:mtext>
<mml:mi mathvariant="italic">ra</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi mathvariant="italic">IP</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi mathvariant="italic">WSN</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:mi>k</mml:mi>
<mml:mo>−</mml:mo>
<mml:msub><mml:mi>U</mml:mi>
<mml:mi mathvariant="italic">bu</mml:mi>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:mo>/</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>The ratio of inter-IP-WSN mobility is denoted as <italic>M</italic>
<sub>int<italic>er_IP_WSN</italic>
</sub>
and is expressed by:
<disp-formula><mml:math id="M8"><mml:mrow><mml:msub><mml:mrow><mml:mi>M</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>int</mml:mtext>
<mml:mi mathvariant="italic">er</mml:mi>
<mml:mo>_</mml:mo>
<mml:mi mathvariant="italic">IP</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi mathvariant="italic">WSN</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:msub><mml:mrow><mml:mi>U</mml:mi>
</mml:mrow>
<mml:mrow><mml:mi mathvariant="italic">bu</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>/</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
</sec>
<sec sec-type="methods"><label>4.3.</label>
<title>Signaling Cost Analysis of IP-WSN</title>
<p>We have evaluated our proposed model based on signaling cost, mobility cost and energy consumption. In the subsequent section we discuss the signaling cost analysis and energy consumption analysis with the help of different parameters mentioned in <xref ref-type="table" rid="t1-sensors-11-01865">Table 1</xref>
. Mobility cost is evaluated based on signaling cost. To evaluate total signaling costs, we compare the results of our analytical model with those of MIPv6 and PMIPv6.</p>
<p><xref ref-type="fig" rid="f8-sensors-11-01865">Figure 8</xref>
depicts the analytical model for the performance analysis of the proposed model. It consists of two different SPMIPv6 domains which are connected over the PMIPv6 based inter network. This Figure is the analytical representation of <xref ref-type="fig" rid="f1-sensors-11-01865">Figure 1</xref>
. We may consider the individual SPMIPv6 domains as the different floors of the patient care unit. Distance between SMAG and IP sensor node is denoted by D<sub>sn-smag</sub>
and the distance between SMAG and SLMA is denoted by D<sub>smag-slma.</sub>
The corresponding node (CN) considered as the specialist doctor is communicating with the visiting doctor. There are some visiting doctors who take the patient in continuous basis. In this analytical model, different distances are used for calculating signaling cost. The cost is incurred due to transmission of data and control signal. The cost will vary dew to different types of signal transmission. There may be five types of mobility scenario which has already been discussed in the earlier section. If patients move to a remote site then the signal will be transmitted through PMIPv6 domain. Other wise signal transmission will be restricted with in the SPMIPv6 domain.</p>
<p>From <xref ref-type="disp-formula" rid="FD1">Equation (1)</xref>
the total signaling cost (SC<sub>mipv6</sub>
) of the proposed scheme based on MIPv6 is calculated by summing up the individual cost of intra-IP-WSN mobility (M<sub>intra-ip-wsn</sub>
. C<sub>sd</sub>
) and inter-IP-WSN mobility (M<sub>inter-ip-wsn</sub>
.(C<sub>sd</sub>
+ C<sub>bu</sub>
)). Where, C<sub>sd and</sub>
C<sub>bu</sub>
are the sensor mobility cost and binding update cost respectively:
<disp-formula id="FD1"><label>(1)</label>
<mml:math id="M9"><mml:mrow><mml:msub><mml:mrow><mml:mrow><mml:mtext>SC</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>mipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>intra-ip-wsn</mml:mtext>
</mml:mrow>
<mml:mtext>. </mml:mtext>
</mml:mrow>
</mml:msub>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>sd</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>inter-ip-wsn</mml:mtext>
</mml:mrow>
<mml:mo>.</mml:mo>
</mml:mrow>
</mml:msub>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>sd</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>bu</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
where C<sub>sd</sub>
and C<sub>bu</sub>
are calculated in term of MIPv6 as follows:
<disp-formula><mml:math id="M10"><mml:mrow><mml:mtable columnalign="center"><mml:mtr><mml:mtd><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>sd</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo>α</mml:mo>
<mml:mo>.</mml:mo>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mrow><mml:mtext>RS</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>mipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mrow><mml:mtext>RA</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>mipv6</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">D</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>sn-smag</mml:mtext>
</mml:mrow>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mtd>
</mml:mtr>
<mml:mtr><mml:mtd><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>bu</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo>α</mml:mo>
<mml:mo>.</mml:mo>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mrow><mml:mtext>BU</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>mipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mrow><mml:mtext>BA</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>mipv6</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">D</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>sn-smag</mml:mtext>
</mml:mrow>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:mrow><mml:mo>β</mml:mo>
</mml:mrow>
<mml:mo>.</mml:mo>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mrow><mml:mtext>BU</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>mipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mrow><mml:mtext>BA</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>mivp6</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">D</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>smag-slma</mml:mtext>
</mml:mrow>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>From <xref ref-type="disp-formula" rid="FD2">Equation (2)</xref>
the total signaling cost (SC<sub>pmipv6</sub>
) of the proposed scheme based on PMIPv6 is calculated by summing up the individual cost of intra-IP-WSN mobility (M<sub>intra-ip-wsn</sub>
. C<sub>sd</sub>
) and inter-IP-WSN mobility (M<sub>inter-ip-wsn</sub>
.(C<sub>sd</sub>
+ C<sub>bu</sub>
)). Where, C<sub>sd and</sub>
C<sub>bu</sub>
are the sensor mobility cost and binding update cost respectively:
<disp-formula id="FD2"><label>(2)</label>
<mml:math id="M11"><mml:mrow><mml:msub><mml:mrow><mml:mrow><mml:mtext>SC</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>pmipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>intra-ip-wsn </mml:mtext>
</mml:mrow>
<mml:mo>⋅</mml:mo>
</mml:mrow>
</mml:msub>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>sd</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>inter-ip-wsn</mml:mtext>
</mml:mrow>
<mml:mo>⋅</mml:mo>
</mml:mrow>
</mml:msub>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>sd</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>bu</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
where C<sub>sd</sub>
and C<sub>bu</sub>
are calculated in term of PMIPv6 as follows:
<disp-formula><mml:math id="M12"><mml:mrow><mml:mtable><mml:mtr><mml:mtd><mml:mrow><mml:msub><mml:mi mathvariant="normal">C</mml:mi>
<mml:mtext>sd</mml:mtext>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo>α</mml:mo>
<mml:mo>.</mml:mo>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mtext>RS</mml:mtext>
<mml:mrow><mml:mtext>pmipv</mml:mtext>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mtext>RA</mml:mtext>
<mml:mrow><mml:mtext>pmipv</mml:mtext>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:msub><mml:mi mathvariant="normal">D</mml:mi>
<mml:mtext>sn-smag</mml:mtext>
</mml:msub>
</mml:mrow>
</mml:mtd>
</mml:mtr>
<mml:mtr><mml:mtd><mml:mrow><mml:msub><mml:mi mathvariant="normal">C</mml:mi>
<mml:mtext>bu</mml:mtext>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mo>β</mml:mo>
<mml:mo>.</mml:mo>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mtext>PBU</mml:mtext>
<mml:mrow><mml:mtext>pmipv</mml:mtext>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mtext>PBA</mml:mtext>
<mml:mrow><mml:mtext>pmipv</mml:mtext>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
<mml:msub><mml:mi mathvariant="normal">D</mml:mi>
<mml:mtext>smag-slma</mml:mtext>
</mml:msub>
</mml:mrow>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>From <xref ref-type="disp-formula" rid="FD3">Equation (3)</xref>
the total signaling cost (SC<sub>spmipv6</sub>
) of the proposed scheme based on SPMIPv6 is calculated by summing up the individual cost of intra-IP-WSN mobility (M<sub>intra-ip-wsn</sub>
. C<sub>sd</sub>
) and inter-IP-WSN mobility (M<sub>inter-ip-wsn</sub>
.(C<sub>sd</sub>
+ C<sub>bu</sub>
)). Where, C<sub>sd and</sub>
C<sub>bu</sub>
are the sensor mobility cost and binding update cost respectively:
<disp-formula id="FD3"><label>(3)</label>
<mml:math id="M13"><mml:mrow><mml:msub><mml:mrow><mml:mrow><mml:mtext>SC</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>spmipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>intra-ip-wsn</mml:mtext>
</mml:mrow>
<mml:mtext> </mml:mtext>
<mml:mo>⋅</mml:mo>
<mml:mtext> </mml:mtext>
</mml:mrow>
</mml:msub>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>sd</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">M</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>inter-ip-wsn </mml:mtext>
</mml:mrow>
<mml:mo>⋅</mml:mo>
</mml:mrow>
</mml:msub>
<mml:mrow><mml:mo>(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>sd</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>bu</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo>)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:math>
</disp-formula>
where C<sub>sd</sub>
and C<sub>bu</sub>
are calculated in term of SPMIPv6 as follows:
<disp-formula><mml:math id="M14"><mml:mrow><mml:mtable columnalign="center"><mml:mtr><mml:mtd><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>sd</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mrow><mml:mo>α</mml:mo>
</mml:mrow>
<mml:mo>.</mml:mo>
<mml:mo>(</mml:mo>
<mml:msub><mml:mrow><mml:mrow><mml:mtext>RS</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>spmipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:msub><mml:mrow><mml:mrow><mml:mtext>RA</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>spmipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>)</mml:mo>
<mml:mo> </mml:mo>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">D</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>sn-smag</mml:mtext>
</mml:mrow>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mtd>
</mml:mtr>
<mml:mtr><mml:mtd><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">C</mml:mi>
</mml:mrow>
<mml:mrow><mml:mtext>bu</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mo>=</mml:mo>
<mml:mrow><mml:mo>β</mml:mo>
</mml:mrow>
<mml:msub><mml:mrow><mml:mrow><mml:mtext>.(PBU</mml:mtext>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>spmipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:msub><mml:mrow><mml:mrow><mml:mrow><mml:mo>+</mml:mo>
<mml:mtext>PBA</mml:mtext>
</mml:mrow>
</mml:mrow>
</mml:mrow>
<mml:mrow><mml:mtext>spmipv6</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mtext>) </mml:mtext>
<mml:msub><mml:mrow><mml:mi mathvariant="normal">D</mml:mi>
</mml:mrow>
<mml:mrow><mml:mrow><mml:mtext>smag-slma</mml:mtext>
</mml:mrow>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
</sec>
<sec sec-type="methods"><label>4.4.</label>
<title>Energy Consumption analysis of IP-WSN</title>
<p>For energy consumption analysis, we consider an IP-WSN with densely deployed IP sensing devices. The network consists of two types of IP sensing device: fully functional IP sensing devices (IP-FFD) and reduced functional IP sensing devices (IP-RFD). IP-FFD holds the complete 6LoWPAN protocol stack and performs the routing functions. IP-RFD performs the sensing functions and forwards the data to the IP-FFD. We have followed the energy consumption model used in [<xref ref-type="bibr" rid="b2-sensors-11-01865">2</xref>
,<xref ref-type="bibr" rid="b24-sensors-11-01865">24</xref>
–<xref ref-type="bibr" rid="b27-sensors-11-01865">27</xref>
]. <xref ref-type="table" rid="t2-sensors-11-01865">Table 2</xref>
represents the used parameter values in the energy consumption model. Here, E<sup>tx</sup>
and E<sup>rx</sup>
is the distance-independent amount of energy consumed by the transmitter and receiver electronics and the digital processing of each. Here α and β are path loss exponent (2 < α < 5) and a constant [J/bit m<sup>2</sup>
], r is a transmission range. L<sub>ctrl</sub>
is the length of control packets in bits, L<sub>E</sub>
is the energy needed by the transmitter device to transmit or receive a packet, and T is the time period between two consecutive topological changes of the IP-WSN. <italic>nffd</italic>
<sub><italic>p</italic>
</sub>
(<italic>d<sub>i</sub>
</italic>
) indicates the number of fully functional neighboring node for a path p and range d:
<disp-formula><mml:math id="M15"><mml:mrow><mml:mi>E</mml:mi>
<mml:mo>=</mml:mo>
<mml:msup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mrow><mml:mi mathvariant="italic">tx</mml:mi>
</mml:mrow>
</mml:msup>
<mml:mo>+</mml:mo>
<mml:mo>β</mml:mo>
<mml:mo>*</mml:mo>
<mml:msup><mml:mrow><mml:mi>d</mml:mi>
</mml:mrow>
<mml:mo>α</mml:mo>
</mml:msup>
<mml:mo>+</mml:mo>
<mml:msup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mrow><mml:mi mathvariant="italic">rx</mml:mi>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>Since same type of transmitting and receiving device is concerned in IP-WSN:
<disp-formula><mml:math id="M16"><mml:mrow><mml:mtable columnalign="left"><mml:mtr><mml:mtd><mml:mrow><mml:msup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mrow><mml:mi mathvariant="italic">tx</mml:mi>
</mml:mrow>
</mml:msup>
<mml:mo>=</mml:mo>
<mml:msup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mrow><mml:mi mathvariant="italic">rx</mml:mi>
</mml:mrow>
</mml:msup>
<mml:mo>=</mml:mo>
<mml:msub><mml:mi>E</mml:mi>
<mml:mi mathvariant="italic">dec</mml:mi>
</mml:msub>
</mml:mrow>
</mml:mtd>
</mml:mtr>
<mml:mtr><mml:mtd><mml:mrow><mml:mi>E</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>2</mml:mn>
<mml:mo>*</mml:mo>
<mml:msub><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mrow><mml:mi mathvariant="italic">dec</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>+</mml:mo>
<mml:mo>β</mml:mo>
<mml:mo>*</mml:mo>
<mml:msup><mml:mrow><mml:mi>d</mml:mi>
</mml:mrow>
<mml:mo>α</mml:mo>
</mml:msup>
</mml:mrow>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:math>
</disp-formula>
<disp-formula><mml:math id="M17"><mml:mrow><mml:mtable columnalign="center"><mml:mtr><mml:mtd><mml:mrow><mml:msubsup><mml:mi>C</mml:mi>
<mml:mi>i</mml:mi>
<mml:mi mathvariant="italic">ctrl</mml:mi>
</mml:msubsup>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>r</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msub><mml:mi>L</mml:mi>
<mml:mi mathvariant="italic">ctrl</mml:mi>
</mml:msub>
<mml:mo>*</mml:mo>
<mml:mo>β</mml:mo>
<mml:mo>*</mml:mo>
<mml:msup><mml:mrow><mml:mi>r</mml:mi>
</mml:mrow>
<mml:mo>α</mml:mo>
</mml:msup>
<mml:mo>+</mml:mo>
<mml:mrow><mml:mo stretchy="false">(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi>n</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>r</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>*</mml:mo>
<mml:msub><mml:mi>L</mml:mi>
<mml:mi mathvariant="italic">ctrl</mml:mi>
</mml:msub>
<mml:mo>*</mml:mo>
<mml:msub><mml:mrow><mml:mi>L</mml:mi>
</mml:mrow>
<mml:mi>E</mml:mi>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
<mml:mfrac><mml:mn>1</mml:mn>
<mml:mi>T</mml:mi>
</mml:mfrac>
</mml:mrow>
</mml:mtd>
</mml:mtr>
<mml:mtr><mml:mtd><mml:mrow><mml:msubsup><mml:mi>C</mml:mi>
<mml:mi>i</mml:mi>
<mml:mtext>inf</mml:mtext>
</mml:msubsup>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>p</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:munderover><mml:mo>∑</mml:mo>
<mml:mrow><mml:mi>i</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
<mml:mo>,</mml:mo>
<mml:mo> </mml:mo>
<mml:mi>j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>2</mml:mn>
</mml:mrow>
<mml:mi>N</mml:mi>
</mml:munderover>
<mml:mrow><mml:mrow><mml:mo stretchy="false">(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="italic">nffd</mml:mi>
</mml:mrow>
<mml:mi>p</mml:mi>
</mml:msub>
<mml:mrow><mml:mo stretchy="false">(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi>d</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>*</mml:mo>
<mml:msub><mml:mi>L</mml:mi>
<mml:mi mathvariant="italic">data</mml:mi>
</mml:msub>
<mml:mo>*</mml:mo>
<mml:mo>β</mml:mo>
<mml:msub><mml:mrow><mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow><mml:mi>i</mml:mi>
<mml:mo>,</mml:mo>
<mml:mo> </mml:mo>
<mml:mi>j</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msup><mml:mrow></mml:mrow>
<mml:mo>α</mml:mo>
</mml:msup>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:mrow><mml:mo stretchy="false">(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi>n</mml:mi>
</mml:mrow>
<mml:mi>p</mml:mi>
</mml:msub>
<mml:mrow><mml:mo stretchy="false">(</mml:mo>
<mml:mrow><mml:msub><mml:mrow><mml:mi>d</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo>*</mml:mo>
<mml:msub><mml:mrow><mml:mi>L</mml:mi>
</mml:mrow>
<mml:mrow><mml:mi mathvariant="italic">data</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
<mml:mo>*</mml:mo>
<mml:msub><mml:mrow><mml:mi>L</mml:mi>
</mml:mrow>
<mml:mi>E</mml:mi>
</mml:msub>
</mml:mrow>
</mml:mtd>
</mml:mtr>
<mml:mtr><mml:mtd><mml:mrow><mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">total</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>p</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:munderover><mml:mo>∑</mml:mo>
<mml:mrow><mml:mi>i</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mi>N</mml:mi>
</mml:munderover>
<mml:mrow><mml:mrow><mml:mo stretchy="false">[</mml:mo>
<mml:mrow><mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">ctrl</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>r</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
<mml:mo>+</mml:mo>
<mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mtext>inf</mml:mtext>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>p</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:mrow>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>So energy consumed by MIPv6 scheme can be calculated by the following mathematical derivation. Here
<inline-formula><mml:math id="M18"><mml:mrow><mml:msubsup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">mipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:math>
</inline-formula>
indicates energy consumption by the MIPv6 scheme:
<disp-formula><mml:math id="M19"><mml:mrow><mml:msubsup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">mipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mi>S</mml:mi>
<mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">mipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>*</mml:mo>
<mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">total</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>p</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>Energy consumed by PMIPv6 scheme can be calculated by the following mathematical derivation. Here
<inline-formula><mml:math id="M20"><mml:mrow><mml:msubsup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">pmipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:math>
</inline-formula>
indicates energy consumption by PMIPv6 scheme:
<disp-formula><mml:math id="M21"><mml:mrow><mml:msubsup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">pmipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mi>S</mml:mi>
<mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">pmipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>*</mml:mo>
<mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">total</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>p</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
<p>Finally energy consumed by SPMIPv6 scheme can be calculated in the same way. Here
<inline-formula><mml:math id="M22"><mml:mrow><mml:msubsup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">spmipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
</mml:mrow>
</mml:math>
</inline-formula>
indicates energy consumption by SPMIPv6 scheme:
<disp-formula><mml:math id="M23"><mml:mrow><mml:msubsup><mml:mrow><mml:mi>E</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">spmipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mi>S</mml:mi>
<mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">spmipv</mml:mi>
<mml:mn>6</mml:mn>
</mml:mrow>
</mml:msubsup>
<mml:mo>*</mml:mo>
<mml:msubsup><mml:mrow><mml:mi>C</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
<mml:mrow><mml:mi mathvariant="italic">total</mml:mi>
</mml:mrow>
</mml:msubsup>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>p</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
</mml:mrow>
</mml:math>
</disp-formula>
</p>
</sec>
</sec>
<sec><label>5.</label>
<title>Experimental Results</title>
<p>In this section, we present the results of experiments evaluating the performance of our scheme, and compare the performance of our proposed scheme to MIPv6 and PMIPv6. First, we evaluate the performance of our proposed approach by mathematical analysis. Then, we set signaling cost and mobility related cost for the number of IP based sensor nodes and number of hops traverse during the mobility phase in order to evaluate the consequences of our proposed scheme with PMIPv6 and MIPv6. Finally, we summarize the key characteristics of our proposed approach as compared to PMIPv6 & MIPv6 approach.</p>
<p>We have implemented the model and evaluate the parameter such as the signaling cost and mobility related cost as presented in this paper. The experiments were conducted on a computer with AMD Athlon™ 2.5 GHz CPU and 2 GB primary memory. We use network simulator tool NS2 on VMware based Linux Fedora 4.</p>
<p>The <xref ref-type="fig" rid="f9-sensors-11-01865">Figure 9</xref>
depicts the signaling cost with respect to the number of IP-WSN node in term of the MIPv6, PMIPv6 and SPMIPv6. Signaling cost increases as the number of IP-WSN nodes increases. However, SPMIPv6 incurs much less signaling cost compared to MIPv6 and PMIPv6 as the number of IP-WSN nodes increases. The SPMIPv6 scheme reduces signaling cost by 60% and 56% with respect to MIPv6 and PMIPv6 in terms of the number of IP-WSN nodes.</p>
<p><xref ref-type="fig" rid="f10-sensors-11-01865">Figure 10</xref>
depicts the signaling cost with respect to the numbers of hops the data or signal traverses to reach the destination node. In this case we consider a maximum 15 hops. Signaling cost increases linearly as the number of hops increases. The proposed scheme shows better performance with respect to both PMIPv6 and MIPv6. In all cases signaling cost increases in a linear pattern. SPMIPv6 scheme reduces signaling cost by 56% and 53% with respect to MIPv6 and PMIPv6 in terms of the number of hops.</p>
<p><xref ref-type="fig" rid="f11-sensors-11-01865">Figure 11</xref>
shows the mobility cost with respect to the number of mobile sensor nodes in both MIPv6 PMIPv6 and SPMIPv6. Mobility cost increases as the number of mobile sensor node increases. SPMIPv6 enjoy less mobility cost with respect to MIPv6 and PMIPv6.</p>
<p>Difference of mobility cost becomes more reasonable when the number of mobile sensor node increases. The SPMIPv6 scheme reduces signaling cost by 62% and 57% with respect to MIPv6 and PMIPv6 in terms of the number of IP-WSN nodes.</p>
<p><xref ref-type="fig" rid="f12-sensors-11-01865">Figure 12</xref>
shows the mobility cost with respect to number of hops used by the mobile sensor nodes in MIPv6, PMIPv6 and SPMIPv6. Mobility cost increases exponentially as the number of hops increases. In this scenario also, our proposed scheme (SPMIPv6) enjoys less mobility cost with respect to MIPv6 and PMIPv6. Proposed SPMIPv6 scheme reduces 67% and 60% mobility cost with respect to MIPv6 and PMIPv6 in terms of the number of hops.</p>
<p>The <xref ref-type="fig" rid="f13-sensors-11-01865">Figure 13</xref>
shows the energy consumption with respect to payload. Energy consumption is linear in MIPv6, PMIPv6 and SPMIPv6. However, due to fragmentation overhead, energy consumption increased rapidly and then it represents the linear characteristics again.</p>
<p>The <xref ref-type="fig" rid="f14-sensors-11-01865">Figure 14</xref>
depicts the energy consumption with respect to the IP-WSN node density in terms of the MIPv6, PMIPv6 and SPMIPv6. Energy consumption increases as the IP-WSN node density increases. Our proposed scheme increases the performance linearly compared to MIPv6 and PMIPv6. Therefore, the energy consumption increases more rapidly as the density of IP-WSN node increases.</p>
</sec>
<sec><label>6.</label>
<title>Conclusions</title>
<p>In this paper we present a sensor proxy mobile IPv6 protocol that enhances the mobility issue in IP-WSNs. Mobility in sensor networks is the most challenging issue that must be addressed with special attention to energy efficiency. Since SPMIPv6 is a sensor network-based localized mobility management protocol, it meets the demands for energy efficiency in terms of reducing signaling costs and mobility costs. Here we also present its architecture and messages formats and evaluate its performance by analyzing signaling costs and mobility costs. Our experiments show that SPMIPv6 reduces both signaling cost and mobility cost in comparison to MIPv6 and PMIPv6. In this paper, we focus on a 6LoWPAN based IP-WSN of the same vendor and protocol stack. In future we will focus on sensor networks consisting of multi vendors and heterogeneous protocol stacks.</p>
</sec>
</body>
<back><ack><p>We would like to pay our highest level of gratitude to the anonymous reviewers for their very useful comments that helped us enrich the quality and presentation of the paper a lot. This work was supported by a grant from the Kyung Hee University in 2010 (KHU-20101372).</p>
</ack>
<ref-list><title>References</title>
<ref id="b1-sensors-11-01865"><label>1.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Akyildiz</surname>
<given-names>I.F.</given-names>
</name>
<name><surname>Su</surname>
<given-names>W.</given-names>
</name>
<name><surname>Sankarasubramaniam</surname>
<given-names>Y.</given-names>
</name>
<name><surname>Cayirci</surname>
<given-names>E.</given-names>
</name>
</person-group>
<article-title>A survey on sensor networks</article-title>
<source>IEEE Communication. Magazine</source>
<year>2002</year>
<volume>40</volume>
<fpage>102</fpage>
<lpage>114</lpage>
</element-citation>
</ref>
<ref id="b2-sensors-11-01865"><label>2.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kemal</surname>
<given-names>A.</given-names>
</name>
<name><surname>Mohamed</surname>
<given-names>Y.</given-names>
</name>
</person-group>
<article-title>A survey on routing protocols for wireless sensor networks</article-title>
<source>Ad Hoc Network</source>
<year>2005</year>
<volume>3</volume>
<fpage>325</fpage>
<lpage>349</lpage>
</element-citation>
</ref>
<ref id="b3-sensors-11-01865"><label>3.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Luo</surname>
<given-names>X.</given-names>
</name>
<name><surname>Zheng</surname>
<given-names>K.</given-names>
</name>
<name><surname>Pan</surname>
<given-names>Y.</given-names>
</name>
<name><surname>Wu</surname>
<given-names>Z.</given-names>
</name>
</person-group>
<article-title>A TCP/IP implementation for wireless sensor networks</article-title>
<conf-name>Proceedings of IEEE International Conference on Systems, Man, and Cybernetics</conf-name>
<conf-loc>Hague, Netherland</conf-loc>
<conf-date>10–13 October 2004</conf-date>
<fpage>6081</fpage>
<lpage>6086</lpage>
</element-citation>
</ref>
<ref id="b4-sensors-11-01865"><label>4.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Rodrigues</surname>
</name>
<name><surname>Joel</surname>
<given-names>J.P.C.</given-names>
</name>
<name><surname>Neves</surname>
</name>
<name><surname>Paulo</surname>
<given-names>A.C.S.</given-names>
</name>
</person-group>
<article-title>A survey on IP-based wireless sensor network solutions</article-title>
<source>Int. J. Commun. Syst</source>
<year>2010</year>
<volume>8</volume>
<fpage>963</fpage>
<lpage>981</lpage>
</element-citation>
</ref>
<ref id="b5-sensors-11-01865"><label>5.</label>
<element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Montenegro</surname>
<given-names>G.</given-names>
</name>
<name><surname>Kushalnagar</surname>
<given-names>N.</given-names>
</name>
<name><surname>Hui</surname>
<given-names>J.W.</given-names>
</name>
<name><surname>Culler</surname>
<given-names>D.E.</given-names>
</name>
</person-group>
<article-title>Transmission of IPv6 Packets over IEEE802.15.4 Networks</article-title>
<source>IETF</source>
<comment>RFC 4944</comment>
<year>2007</year>
</element-citation>
</ref>
<ref id="b6-sensors-11-01865"><label>6.</label>
<element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Kushalnagar</surname>
<given-names>N.</given-names>
</name>
<name><surname>Montenegro</surname>
<given-names>G.</given-names>
</name>
<name><surname>Schumacher</surname>
<given-names>C.</given-names>
</name>
</person-group>
<article-title>IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals</article-title>
<source>IETF</source>
<comment>RFC 4919</comment>
<year>2007</year>
</element-citation>
</ref>
<ref id="b7-sensors-11-01865"><label>7.</label>
<element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Zach</surname>
<given-names>S.</given-names>
</name>
<name><surname>Carsten</surname>
<given-names>B.</given-names>
</name>
</person-group>
<source>6LoWPAN: The Wireless Embedded Internet, David Hutchison, Serge Fdida, Joe Sventek</source>
<publisher-name>John Wiley & Sons Ltd</publisher-name>
<publisher-loc>Chichester, West Sussex, UK</publisher-loc>
<year>2009</year>
</element-citation>
</ref>
<ref id="b8-sensors-11-01865"><label>8.</label>
<element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Kim</surname>
<given-names>E.</given-names>
</name>
<name><surname>Kaspar</surname>
<given-names>D.</given-names>
</name>
<name><surname>Chevrollier</surname>
<given-names>N.</given-names>
</name>
<name><surname>Vasseur</surname>
<given-names>J.P.</given-names>
</name>
</person-group>
<source>Design and Application Spaces for 6LoWPANs</source>
<comment>IETF Internet-Draft</comment>
<month>7</month>
<year>2009</year>
</element-citation>
</ref>
<ref id="b9-sensors-11-01865"><label>9.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Hui</surname>
<given-names>J.W.</given-names>
</name>
<name><surname>Culler</surname>
<given-names>D.E.</given-names>
</name>
</person-group>
<article-title>Extending IP to low-power, wireless personal area networks</article-title>
<source>Int. Comput. IEEE</source>
<year>2008</year>
<volume>12</volume>
<fpage>37</fpage>
<lpage>45</lpage>
</element-citation>
</ref>
<ref id="b10-sensors-11-01865"><label>10.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kong</surname>
<given-names>K.-S.</given-names>
</name>
<name><surname>Lee</surname>
<given-names>W.</given-names>
</name>
<name><surname>Han</surname>
<given-names>Y.-H.</given-names>
</name>
<name><surname>Shin</surname>
<given-names>M.-K.</given-names>
</name>
<name><surname>You</surname>
<given-names>H.R.</given-names>
</name>
</person-group>
<article-title>Mobility management for all-IP mobile networks: mobile IPv6 <italic>vs.</italic>
proxy mobile IPv6</article-title>
<source>IEEE Wirel. Commun.</source>
<year>2008</year>
<volume>15</volume>
<fpage>36</fpage>
<lpage>45</lpage>
</element-citation>
</ref>
<ref id="b11-sensors-11-01865"><label>11.</label>
<element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Gundavelli</surname>
<given-names>S.</given-names>
</name>
<name><surname>Leung</surname>
<given-names>K.</given-names>
</name>
<name><surname>Devarapalli</surname>
<given-names>V.</given-names>
</name>
<name><surname>Chowdhury</surname>
<given-names>K.</given-names>
</name>
<name><surname>Patil</surname>
<given-names>B.</given-names>
</name>
</person-group>
<article-title>Proxy Mobile IPv6</article-title>
<source>IETF</source>
<comment>RFC 5213</comment>
<year>2008</year>
</element-citation>
</ref>
<ref id="b12-sensors-11-01865"><label>12.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kim</surname>
<given-names>M.S.</given-names>
</name>
<name><surname>Lee</surname>
<given-names>S.K.</given-names>
</name>
</person-group>
<article-title>A novel load balancing scheme for PMIPv6 based networks</article-title>
<source>Int. J. Electron. Commun</source>
<year>2009</year>
<volume>64</volume>
<fpage>579</fpage>
<lpage>583</lpage>
</element-citation>
</ref>
<ref id="b13-sensors-11-01865"><label>13.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Chalmers</surname>
<given-names>R.C.</given-names>
</name>
<name><surname>Almeroth</surname>
<given-names>K.C.</given-names>
</name>
</person-group>
<article-title>A mobility gateway for small-device networks</article-title>
<conf-name>Proceedings of Second IEEE Annual Conference on Pervasive Computing and Communications</conf-name>
<publisher-loc>Washington, DC, USA</publisher-loc>
<month>6</month>
<year>2004</year>
</element-citation>
</ref>
<ref id="b14-sensors-11-01865"><label>14.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kim</surname>
<given-names>J.H.</given-names>
</name>
<name><surname>Hong</surname>
<given-names>C.S.</given-names>
</name>
<name><surname>Taeshik</surname>
<given-names>S.</given-names>
</name>
</person-group>
<article-title>A Lightweight NEMO protocol to support 6LoWPAN</article-title>
<source>ETRI J</source>
<year>2008</year>
<volume>30</volume>
<fpage>685</fpage>
<lpage>695</lpage>
</element-citation>
</ref>
<ref id="b15-sensors-11-01865"><label>15.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Yang</surname>
<given-names>S.</given-names>
</name>
<name><surname>Park</surname>
<given-names>S.</given-names>
</name>
<name><surname>Lee</surname>
<given-names>E.J.</given-names>
</name>
<name><surname>Ryu</surname>
<given-names>J.H.</given-names>
</name>
<name><surname>Kim</surname>
<given-names>B.S.</given-names>
</name>
<name><surname>Kim</surname>
<given-names>H.S.</given-names>
</name>
</person-group>
<article-title>Dual addressing scheme in IPv6 over IEEE802.15.4 Wireless Sensor Network</article-title>
<source>ETRI J</source>
<year>2008</year>
<volume>30</volume>
<fpage>674</fpage>
<lpage>684</lpage>
</element-citation>
</ref>
<ref id="b16-sensors-11-01865"><label>16.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Hwang</surname>
<given-names>S.M.</given-names>
</name>
<name><surname>Kim</surname>
<given-names>K.J.</given-names>
</name>
<name><surname>Islam</surname>
<given-names>M.M.</given-names>
</name>
<name><surname>Huh</surname>
<given-names>E.N.</given-names>
</name>
<name><surname>Huang</surname>
<given-names>W.</given-names>
</name>
<name><surname>Foo</surname>
<given-names>V.</given-names>
</name>
<name><surname>Tolstikov</surname>
<given-names>A.</given-names>
</name>
<name><surname>Aung</surname>
<given-names>A.</given-names>
</name>
<name><surname>Jayachandran</surname>
<given-names>M.</given-names>
</name>
<name><surname>Biswas</surname>
<given-names>J.</given-names>
</name>
</person-group>
<article-title>Multi-modal Sensing Smart Spaces Embedded with WSN Based Image Camera</article-title>
<conf-name>Proceedings of the 3rd International Conference on Pervasive Technologies Related to Assistive Environments</conf-name>
<conf-loc>Samos, Greece</conf-loc>
<year>2010</year>
</element-citation>
</ref>
<ref id="b17-sensors-11-01865"><label>17.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Bag</surname>
<given-names>G.</given-names>
</name>
<name><surname>Hamid</surname>
<given-names>M.</given-names>
</name>
<name><surname>Saif Shams</surname>
<given-names>S.M.</given-names>
</name>
<name><surname>Kim</surname>
<given-names>H.K.</given-names>
</name>
<name><surname>Yoo</surname>
<given-names>S.W.</given-names>
</name>
</person-group>
<article-title>Inter-PAN Mobility Support for 6LoWPAN</article-title>
<conf-name>Proceedings of IEEE Computer Society Third International Conference on Convergence and Hybrid Technology</conf-name>
<conf-loc>Busan, South Korea</conf-loc>
<conf-date>November 2008</conf-date>
</element-citation>
</ref>
<ref id="b18-sensors-11-01865"><label>18.</label>
<element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Johnson</surname>
<given-names>D.</given-names>
</name>
<name><surname>Perkins</surname>
<given-names>C.</given-names>
</name>
<name><surname>Arkko</surname>
<given-names>J.</given-names>
</name>
</person-group>
<article-title>Mobility Support in IPv6</article-title>
<source>IETF</source>
<comment>RFC 3775</comment>
<year>2004</year>
</element-citation>
</ref>
<ref id="b19-sensors-11-01865"><label>19.</label>
<element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Devarapalli</surname>
<given-names>V.</given-names>
</name>
<name><surname>Wakikawa</surname>
<given-names>R.</given-names>
</name>
<name><surname>Petrescu</surname>
<given-names>A.</given-names>
</name>
<name><surname>Thubert</surname>
<given-names>P.</given-names>
</name>
</person-group>
<article-title>Network Mobility (NEMO) Basic Support Protocol</article-title>
<source>IETF</source>
<comment>RFC 3963</comment>
<year>2005</year>
</element-citation>
</ref>
<ref id="b20-sensors-11-01865"><label>20.</label>
<element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Soliman</surname>
<given-names>H.</given-names>
</name>
<name><surname>Castelluccia</surname>
<given-names>C.</given-names>
</name>
<name><surname>Malki</surname>
<given-names>K. El</given-names>
</name>
<name><surname>Bellier</surname>
<given-names>L.</given-names>
</name>
</person-group>
<article-title>Hierarchical Mobile IPv6 Mobility Management (HMIPv6)</article-title>
<source>IETF</source>
<comment>RFC 4140</comment>
<year>2005</year>
</element-citation>
</ref>
<ref id="b21-sensors-11-01865"><label>21.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Akyildiz</surname>
<given-names>I.F.</given-names>
</name>
<name><surname>Lin</surname>
<given-names>Y.B.</given-names>
</name>
<name><surname>Lai</surname>
<given-names>W.R.</given-names>
</name>
<name><surname>Chen</surname>
<given-names>R.J.</given-names>
</name>
</person-group>
<article-title>A new random walk model for PCS networks</article-title>
<source>IEEE J. Sel. Area Commun</source>
<year>2000</year>
<volume>18</volume>
<fpage>1254</fpage>
<lpage>1259</lpage>
</element-citation>
</ref>
<ref id="b22-sensors-11-01865"><label>22.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Chiang</surname>
<given-names>K.H.</given-names>
</name>
<name><surname>Shenoy</surname>
<given-names>N.</given-names>
</name>
</person-group>
<article-title>A 2D Random walk mobility model for location management studies in wireless network</article-title>
<source>IEEE Trans. Veh. Tech</source>
<year>2004</year>
<volume>53</volume>
<fpage>413</fpage>
<lpage>424</lpage>
</element-citation>
</ref>
<ref id="b23-sensors-11-01865"><label>23.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Bhavneet</surname>
<given-names>S.</given-names>
</name>
<name><surname>Hardeep</surname>
<given-names>S.</given-names>
</name>
</person-group>
<article-title>Location management in cellular networks</article-title>
<source>World Acad. Sci. Eng. Technol</source>
<year>2007</year>
<volume>25</volume>
<fpage>314</fpage>
<lpage>319</lpage>
</element-citation>
</ref>
<ref id="b24-sensors-11-01865"><label>24.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Heinzelman</surname>
<given-names>W.R.</given-names>
</name>
<name><surname>Chandrakasan</surname>
<given-names>A.</given-names>
</name>
<name><surname>Balakrishnan</surname>
<given-names>H.</given-names>
</name>
</person-group>
<article-title>Energy-Efficient Communication Protocol for Wireless Micro sensor Networks</article-title>
<conf-name>Proceedings of the 33rd Annual Hawaii International Conference on System Sciences</conf-name>
<conf-loc>Hawaii, USA</conf-loc>
<conf-date>January 2000</conf-date>
</element-citation>
</ref>
<ref id="b25-sensors-11-01865"><label>25.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Pathan</surname>
<given-names>A.S.K.</given-names>
</name>
<name><surname>Hong</surname>
<given-names>C.S.</given-names>
</name>
</person-group>
<article-title>SERP: secure energy-efficient routing protocol for densely deployed wireless sensor networks</article-title>
<source>Ann. Telecommun</source>
<year>2008</year>
<volume>63</volume>
<fpage>529</fpage>
<lpage>541</lpage>
</element-citation>
</ref>
<ref id="b26-sensors-11-01865"><label>26.</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Razzaque</surname>
<given-names>M.A.</given-names>
</name>
<name><surname>Hong</surname>
<given-names>C.S.</given-names>
</name>
</person-group>
<article-title>Analysis of energy-tax for multipath routing in wireless sensor networks</article-title>
<source>Ann. Telecommun</source>
<year>2009</year>
<volume>65</volume>
<fpage>117</fpage>
<lpage>127</lpage>
</element-citation>
</ref>
<ref id="b27-sensors-11-01865"><label>27.</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Dhanajay</surname>
<given-names>S.</given-names>
</name>
<name><surname>Lee</surname>
<given-names>H.J.</given-names>
</name>
<name><surname>Chung</surname>
<given-names>W.Y.</given-names>
</name>
</person-group>
<article-title>An Energy Consumption Technique for Global Healthcare Monitoring Applications</article-title>
<conf-name>Proceedings of International Conference on Information Sciences</conf-name>
<conf-loc>Seoul, Korea</conf-loc>
<conf-date>November 24–26, 2009</conf-date>
</element-citation>
</ref>
</ref-list>
</back>
<floats-group><fig id="f1-sensors-11-01865" position="float"><label>Figure 1.</label>
<caption><p>Sensor Proxy Mobile IPv6 Architecture.</p>
</caption>
<graphic xlink:href="sensors-11-01865f1"></graphic>
</fig>
<fig id="f2-sensors-11-01865" position="float"><label>Figure 2.</label>
<caption><p>Operational Architecture of SPMIPv6.</p>
</caption>
<graphic xlink:href="sensors-11-01865f2"></graphic>
</fig>
<fig id="f3-sensors-11-01865" position="float"><label>Figure 3.</label>
<caption><p>Mobility scenario in SPMIPv6-based patient care unit.</p>
</caption>
<graphic xlink:href="sensors-11-01865f3"></graphic>
</fig>
<fig id="f4-sensors-11-01865" position="float"><label>Figure 4.</label>
<caption><p><bold>(a)</bold>
Sequence diagram in PMIPv6. <bold>(b)</bold>
Sequence diagram in SPMIPv6.</p>
</caption>
<graphic xlink:href="sensors-11-01865f4"></graphic>
</fig>
<fig id="f5-sensors-11-01865" position="float"><label>Figure 5.</label>
<caption><p><bold>(a)</bold>
SPMIPv6 PBU Message Format. <bold>(b)</bold>
SPMIPv6 PBA Message Format.</p>
</caption>
<graphic xlink:href="sensors-11-01865f5"></graphic>
</fig>
<fig id="f6-sensors-11-01865" position="float"><label>Figure 6.</label>
<caption><p><bold>(a)</bold>
SPMIPv6 Router Solicitation (RS) Message Format. <bold>(b)</bold>
SPMIPv6 Router Advertisement (RA) Message Format.</p>
</caption>
<graphic xlink:href="sensors-11-01865f6"></graphic>
</fig>
<fig id="f7-sensors-11-01865" position="float"><label>Figure 7.</label>
<caption><p>Type Classification and State diagram of a six-sublayer PAN area model.</p>
</caption>
<graphic xlink:href="sensors-11-01865f7"></graphic>
</fig>
<fig id="f8-sensors-11-01865" position="float"><label>Figure 8.</label>
<caption><p>Analytical model for the performances analysis of SPMIPv6.</p>
</caption>
<graphic xlink:href="sensors-11-01865f8"></graphic>
</fig>
<fig id="f9-sensors-11-01865" position="float"><label>Figure 9.</label>
<caption><p>Number of IP-WSN nodes <italic>vs.</italic>
Signaling Cost.</p>
</caption>
<graphic xlink:href="sensors-11-01865f9"></graphic>
</fig>
<fig id="f10-sensors-11-01865" position="float"><label>Figure 10.</label>
<caption><p>Number of Hops <italic>vs.</italic>
Signaling Cost.</p>
</caption>
<graphic xlink:href="sensors-11-01865f10"></graphic>
</fig>
<fig id="f11-sensors-11-01865" position="float"><label>Figure 11.</label>
<caption><p>Number of IP-WSN nodes <italic>vs.</italic>
Mobility Cost.</p>
</caption>
<graphic xlink:href="sensors-11-01865f11"></graphic>
</fig>
<fig id="f12-sensors-11-01865" position="float"><label>Figure 12.</label>
<caption><p>Number of Hops <italic>vs.</italic>
Mobility Cost.</p>
</caption>
<graphic xlink:href="sensors-11-01865f12"></graphic>
</fig>
<fig id="f13-sensors-11-01865" position="float"><label>Figure 13.</label>
<caption><p>Data payload <italic>vs.</italic>
Energy consumption.</p>
</caption>
<graphic xlink:href="sensors-11-01865f13"></graphic>
</fig>
<fig id="f14-sensors-11-01865" position="float"><label>Figure 14.</label>
<caption><p>Node Density <italic>vs.</italic>
Energy Consumptions.</p>
</caption>
<graphic xlink:href="sensors-11-01865f14"></graphic>
</fig>
<table-wrap id="t1-sensors-11-01865" position="float"><label>Table 1.</label>
<caption><p>System Parameters.</p>
</caption>
<table frame="hsides" rules="groups"><thead><tr><th align="left" valign="middle" rowspan="1" colspan="1"><bold>Symbol</bold>
</th>
<th align="left" valign="middle" rowspan="1" colspan="1"><bold>Description</bold>
</th>
</tr>
</thead>
<tbody><tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>BU</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Binding Update Message</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>BA</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Binding Acknowledgement Message</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>PBU</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Proxy Binding Update Message</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>PBA</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Proxy Binding Acknowledge Message</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>D<sub>smag_slma</sub>
</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Distance between SMAG and SLMA</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>D<sub>sn_smag</sub>
</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Distance between SN and SMAG</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>α</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Unit transmission cost in a wireless link</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>β</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Unit transmission cost in a wired link</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>RS</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Router Solicitation Message</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>RA</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Router Advertisement Message</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>C<sub>sd</sub>
</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Sensor Mobility Cost</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>C<sub>bu</sub>
</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">Binding Update Cost</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="t2-sensors-11-01865" position="float"><label>Table 2.</label>
<caption><p>Parameter values.</p>
</caption>
<table frame="hsides" rules="groups"><thead><tr><th align="left" valign="middle" rowspan="1" colspan="1"><bold>Parameter</bold>
</th>
<th align="left" valign="middle" rowspan="1" colspan="1"><bold>Value</bold>
</th>
</tr>
</thead>
<tbody><tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>No of IP-WSN Node (N)</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">25∼120</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>Network Area (A)</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">120 × 120 M</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>Node density (ρ)</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">0.00173∼0.00833</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>Initial Energy</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">2 J</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>Transmit/Receive electronics (L<sub>E</sub>
)</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">50 nJ bit<sup>−1</sup>
m<sup>2</sup>
</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>Transmission Power</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">5.85 × 10<sup>−5</sup>
W</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>Number of SMAG</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">1–10</td>
</tr>
<tr><td align="left" valign="top" rowspan="1" colspan="1"><bold>Transmission range (r)</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">25 m</td>
</tr>
<tr content-type="background-color:#E6EED5"><td align="left" valign="top" rowspan="1" colspan="1"><bold>Packet size</bold>
</td>
<td align="left" valign="top" rowspan="1" colspan="1">2 KB</td>
</tr>
</tbody>
</table>
</table-wrap>
</floats-group>
</pmc>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/TelematiV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000597 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 000597 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Ticri/CIDE |area= TelematiV1 |flux= Pmc |étape= Corpus |type= RBID |clé= PMC:3274018 |texte= Sensor Proxy Mobile IPv6 (SPMIPv6)—A Novel Scheme for Mobility Supported IP-WSNs }}
Pour générer des pages wiki
HfdIndexSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/RBID.i -Sk "pubmed:22319386" \ | HfdSelect -Kh $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd \ | NlmPubMed2Wicri -a TelematiV1
![]() | This area was generated with Dilib version V0.6.31. | ![]() |