<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xml:lang="en" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Sensors</journal-id>
<journal-title>Sensors</journal-title>
<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="doi">10.3390/s120505486</article-id>
<article-id pub-id-type="publisher-id">sensors-12-05486</article-id>
<article-categories>
<subj-group>
<subject>Article</subject></subj-group></article-categories>
<title-group>
<article-title>Localization with a Mobile Beacon in Underwater Acoustic Sensor Networks</article-title></title-group>
<contrib-group>
<contrib contrib-type="author">
<name><surname>Lee</surname><given-names>Sangho</given-names></name></contrib>
<contrib contrib-type="author">
<name><surname>Kim</surname><given-names>Kiseon</given-names></name><xref ref-type="corresp" rid="c1-sensors-12-05486"><sup>*</sup></xref></contrib>
<aff id="af1-sensors-12-05486">School of Information and Mechatronics, Department of Nanobio Materials and Electronics, WCU, Gwangju Institute of Science and Technology (GIST), 1 Oryong-dong, Buk-Gu, Gwangju 500-712, Korea; E-Mail: <email>faith.kskim@gist.ac.kr</email></aff></contrib-group>
<author-notes>
<corresp id="c1-sensors-12-05486">
<label>*</label>Author to whom correspondence should be addressed; E-Mail: <email>kskim@gist.ac.kr</email>.</corresp></author-notes>
<pub-date pub-type="collection">
<year>2012</year></pub-date>
<pub-date pub-type="epub">
<day>27</day>
<month>04</month>
<year>2012</year></pub-date>
<volume>12</volume>
<issue>5</issue>
<fpage>5486</fpage>
<lpage>5501</lpage>
<history>
<date date-type="received">
<day>21</day>
<month>03</month>
<year>2012</year></date>
<date date-type="rev-recd">
<day>23</day>
<month>04</month>
<year>2012</year></date>
<date date-type="accepted">
<day>23</day>
<month>04</month>
<year>2012</year></date></history>
<permissions>
<copyright-statement>© 2012 by the authors; licensee MDPI, Basel, Switzerland.</copyright-statement>
<copyright-year>2012</copyright-year>
<license>
<p>This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution license (http://creativecommons.org/licenses/by/3.0/).</p></license></permissions>
<abstract>
<p>Localization is one of the most important issues associated with underwater acoustic sensor networks, especially when sensor nodes are randomly deployed. Given that it is difficult to deploy beacon nodes at predetermined locations, localization schemes with a mobile beacon on the sea surface or along the planned path are inherently convenient, accurate, and energy-efficient. In this paper, we propose a new range-free Localization with a Mobile Beacon (LoMoB). The mobile beacon periodically broadcasts a beacon message containing its location. Sensor nodes are individually localized by passively receiving the beacon messages without inter-node communications. For location estimation, a set of potential locations are obtained as candidates for a node's location and then the node's location is determined through the weighted mean of all the potential locations with the weights computed based on residuals.</p></abstract>
<kwd-group>
<kwd>localization</kwd>
<kwd>range-free</kwd>
<kwd>mobile beacon</kwd>
<kwd>underwater acoustic sensor networks</kwd></kwd-group></article-meta></front>
<body>
<sec sec-type="intro">
<label>1.</label>
<title>Introduction</title>
<p>For a long time, there has been significant interest in monitoring underwater environments to collect oceanographic data and to explore underwater resources. These harsh underwater environments have limited human access and most of them remain poorly understood. Recent advances in hardware and network technology had enabled sensor networks capable of sensing, data processing, and communication. A collection of sensor nodes, which have a limited sensing region, processing power, and energy, can be randomly deployed and connected to form a network in order to monitor a wide area. Sensor networks are particularly promising for use in underwater environments where access is difficult [<xref ref-type="bibr" rid="b1-sensors-12-05486">1</xref>–<xref ref-type="bibr" rid="b3-sensors-12-05486">3</xref>]. In underwater acoustic sensor networks (UASN), localization of sensor nodes is essential because it is difficult to accurately deploy sensor nodes to predetermined locations. In addition, all the information collected by sensor nodes may be useless unless the location of each sensor node is known [<xref ref-type="bibr" rid="b4-sensors-12-05486">4</xref>].</p>
<p>To localize unknown nodes, static beacons [<xref ref-type="bibr" rid="b5-sensors-12-05486">5</xref>–<xref ref-type="bibr" rid="b11-sensors-12-05486">11</xref>] or a mobile beacon [<xref ref-type="bibr" rid="b12-sensors-12-05486">12</xref>–<xref ref-type="bibr" rid="b16-sensors-12-05486">16</xref>] can be used; typically, buoys are used for static beacons and an autonomous underwater vehicle (AUV) for a mobile beacon. The use of a mobile beacon has a similar effect to the use of many static beacons. For this reason, localization using a mobile beacon is inherently more accurate and cost-effective than localization using static beacons. Further, the vehicle can be conveniently maneuvered on the sea surface or underwater, based on a planned or random path, as shown in <xref ref-type="fig" rid="f1-sensors-12-05486">Figure 1</xref>.</p>
<p>Localization schemes can also be classified as range-based or range-free schemes. Range-based schemes use the distance and/or angle information measured by the Time of Arrival (ToA), Time Difference of Arrival (TDoA), Angle of Arrival (AoA), or Received Signal Strength Indicator (RSSI) techniques. In underwater environments, range-based schemes that use the ToA and TDoA techniques have been proposed [<xref ref-type="bibr" rid="b5-sensors-12-05486">5</xref>–<xref ref-type="bibr" rid="b10-sensors-12-05486">10</xref>,<xref ref-type="bibr" rid="b13-sensors-12-05486">13</xref>–<xref ref-type="bibr" rid="b15-sensors-12-05486">15</xref>]. Time synchronization between sensor nodes is typically required for the ToA and TDoA techniques [<xref ref-type="bibr" rid="b6-sensors-12-05486">6</xref>]. However, precise time synchronization is challenging in underwater environments [<xref ref-type="bibr" rid="b17-sensors-12-05486">17</xref>]. In addition, even though the ToA and TDoA techniques are used without time synchronization, the techniques are based on the speed of sound and this varies with temperature, pressure, salinity, and depth. In contrast to range-based schemes, range-free schemes localize a sensor node by deducing distance information instead of measuring distances [<xref ref-type="bibr" rid="b11-sensors-12-05486">11</xref>,<xref ref-type="bibr" rid="b12-sensors-12-05486">12</xref>,<xref ref-type="bibr" rid="b16-sensors-12-05486">16</xref>]. Because range-free schemes do not require additional devices in order to measure distances and do not suffer from distance measurement errors, range-free schemes are a promising approach for underwater sensor networks [<xref ref-type="bibr" rid="b16-sensors-12-05486">16</xref>].</p>
<p>Localization is one of the challenges associated with underwater sensor networks and many studies have focused on localization in recent years. Among these studies, LDB is a range-free localization scheme with a mobile beacon [<xref ref-type="bibr" rid="b16-sensors-12-05486">16</xref>]. In LDB, sensor nodes can localize themselves through passively listening to beacons sent by an AUV that has an acoustic directional transceiver. Because sensor nodes just receive the beacons from the AUV without inter-node communications, LDB is energy-efficient because it reduces the energy consumption due to transmitting; the power consumed by transmitting is often 100 times higher than the power consumed by receiving [<xref ref-type="bibr" rid="b18-sensors-12-05486">18</xref>]. In addition, because a sensor node can localize itself using its own received beacons from the AUV independently of the other sensor nodes, LDB has fine-grained accuracy even in sparse networks. The depth of a sensor node is directly determined by using a cheap pressure sensor. After the first and last received beacons, which are called beacon points, from the AUV are projected onto the horizontal plane on which a sensor node resides, the 2D location of a sensor node can be determined based on the distance between the two projected beacon points. At this point, the location of the sensor node remains ambiguous, because the two projected beacon points provide two possible node locations. If the sensor node obtains two more beacon points, the ambiguity can be resolved. The first two beacon points are used for location computation and the other two beacon points are used for resolving the ambiguity. However, if the two beacon points for location computation have a large error, the error in the estimated sensor location also increases. Even though the location of a sensor node can be simply computed from the first two beacon points, the use of just two points out of all the beacon points can make localization very error-prone. To improve the localization accuracy in challenging underwater environments, we propose a new localization scheme LoMoB that obtains a set of potential locations as candidates for a node's location using the bilateration method and then localizes the sensor node through the weighted mean of all the potential locations with the weights computed based on residuals.</p></sec>
<sec>
<label>2.</label>
<title>Related Work</title>
<p>In this section, we briefly explain LDB in the viewpoint of system environment, beacon point selection, and location estimation [<xref ref-type="bibr" rid="b16-sensors-12-05486">16</xref>].</p>
<sec>
<label>2.1.</label>
<title>System Environment</title>
<p>In LDB, an AUV with a directional transceiver moves at a fixed depth in water and broadcasts its location, which called a beacon, and the angle of its transceiver's beam (<italic>a</italic>) at regular intervals, called beacon distance (<italic>d</italic>), as shown in <xref ref-type="fig" rid="f2-sensors-12-05486">Figure 2(a)</xref>. When the AUV sends a beacon, the sensor nodes that fall in the conical beam receive the beacon; e.g., in <xref ref-type="fig" rid="f2-sensors-12-05486">Figure 2(a)</xref>, the sensor node in red can receive the beacon <italic>B</italic><sub>2</sub> and the sensor node in blue can receive the beacons <italic>B</italic><sub>1</sub>, <italic>B</italic><sub>2</sub>, and <italic>B</italic><sub>3</sub>. The conical beam forms circles with different radii according to the depth of the sensor nodes, as shown in <xref ref-type="fig" rid="f2-sensors-12-05486">Figure 2(a)</xref>. When the <italic>z</italic> coordinates of the AUV and a sensor node are <italic>z<sub>A</sub></italic> and <italic>z<sub>s</sub></italic> and the angle of the transceiver's beam is <italic>a,</italic> the radius of the circle formed by the beam for the sensor node is given as follows:
<disp-formula id="FD1">
<label>(1)</label>
<mml:math id="mm1" display="block">
<mml:semantics id="sm1">
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:mi>b</mml:mi></mml:msub>
<mml:mo>=</mml:mo>
<mml:mo>tan</mml:mo>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>a</mml:mi>
<mml:mo>/</mml:mo>
<mml:mn>2</mml:mn>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>×</mml:mo>
<mml:mrow>
<mml:mo>|</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mi>A</mml:mi></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mi>s</mml:mi></mml:msub></mml:mrow>
<mml:mo>|</mml:mo></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula></p></sec>
<sec>
<label>2.2.</label>
<title>Beacon Point Selection</title>
<p>From the viewpoint of a sensor node located at (<italic>x, y, z<sub>s</sub></italic>), when a beacon is within the circle centered at (<italic>x, y, z<sub>A</sub></italic>) with a radius <italic>r<sub>b</sub></italic>, the sensor node can receive the beacon; e.g., in <xref ref-type="fig" rid="f2-sensors-12-05486">Figure 2(b)</xref>, the sensor node receives the beacons <italic>B</italic><sub>1</sub> to <italic>B</italic><sub>6</sub>. Among the series of received beacons, the first beacon is defined as the first-heard beacon point and the last beacon is defined as the last-heard beacon point. The location of a sensor node is estimated using only the beacon points, and not all the received beacons.</p>
<p>Because the sensor depth is known from the pressure sensor, the beacon points can be projected onto the horizontal plane in which the sensor node resides, as shown in <xref ref-type="fig" rid="f2-sensors-12-05486">Figure 2(b)</xref>. After projection, 3D localization is transformed into a 2D localization problem.</p></sec>
<sec>
<label>2.3.</label>
<title>Location Estimation</title>
<p>We describe location estimation based on the projected beacon points. As shown in <xref ref-type="fig" rid="f3-sensors-12-05486">Figure 3(a)</xref>, the projected first-heard beacon point is denoted by <italic>F</italic> and the projected last-heard beacon point is denoted by <italic>L.</italic> The projected point of the beacon received just before the first-heard beacon point is defined as the projected prior-heard beacon point <italic>F</italic>′ (e.g., in <xref ref-type="fig" rid="f2-sensors-12-05486">Figure 2(b)</xref>, the projected point of <italic>B</italic><sub>0</sub>), and the projected point of the beacon after the last-heard beacon point is defined as the projected post-heard beacon point <italic>L</italic>′ (e.g., in <xref ref-type="fig" rid="f2-sensors-12-05486">Figure 2(b)</xref>, the projected point of <italic>B</italic><sub>7</sub>).</p>
<p>Four circles are then drawn with radius <italic>r<sub>b</sub></italic> centered at the four points <italic>F</italic>′, <italic>F, L</italic>, and <italic>L</italic>′. Because the sensor node should be located outside the circles centered at <italic>F</italic>′ and <italic>L</italic>′ and inside the circles centered at <italic>F</italic> and <italic>L</italic>, the intersection areas <italic>ABCD</italic> and <italic>A</italic>′<italic>B</italic>′<italic>C</italic>′<italic>D</italic>′ represent possible locations of the sensor node. One of the two points, <italic>S̃</italic> and <italic>S̃</italic>′, within the two areas will be estimated as the location of the sensor node. Here, <italic>S̃</italic> is the midpoint of <italic>B</italic> and <italic>D</italic> and <italic>S̃</italic>′ is the midpoint of <italic>B</italic>′ and <italic>D</italic>′. When just one projected first-heard beacon point and one projected last-heard beacon point are used, two possible node locations are found. The choice between the two points <italic>S̃</italic> and <italic>S̃</italic>′ can be made after an additional two beacon points are obtained, as shown in <xref ref-type="fig" rid="f3-sensors-12-05486">Figure 3(b)</xref>. In LDB, the first two beacon points are used to compute two possible points for the location of a sensor node based on geometric constraints and the next two beacon points are used for the choice between the two possible points.</p></sec></sec>
<sec>
<label>3.</label>
<title>LoMoB Localization Scheme</title>
<p>In this section, we explain the system environment, beacon point selection, and location estimation method for LoMoB. Because LoMoB can be applied to systems that use either a directional transceiver or an omnidirectional transceiver, we explain LoMoB for both systems. In addition, because LoMoB improves LDB, we explain LoMoB by comparing and contrasting it with LDB.</p>
<sec>
<label>3.1.</label>
<title>System Environment</title>
<p>LoMoB considers a system that uses an omnidirectional transceiver in addition to a system that uses a directional transceiver [<xref ref-type="bibr" rid="b19-sensors-12-05486">19</xref>]. Because the system environment using a directional transceiver was explained in Section 2, we explain here the system environment using an omnidirectional transceiver.</p>
<p>A mobile beacon moves on the sea surface or underwater. When a mobile beacon has an omnidirectional transceiver, 3D movement of the mobile beacon is possible whereas a mobile beacon that has a directional transceiver is restricted to 2D movement at a fixed depth. The mobile beacon is assumed to know its own location and to broadcast a beacon containing its location information at regular distance intervals, which are called the beacon distance <italic>d</italic>. When the mobile beacon transmits a beacon, the sensor nodes that are located within the communication range of the mobile beacon receive the beacon; e.g., in <xref ref-type="fig" rid="f4-sensors-12-05486">Figure 4(a)</xref>, the sensor node in red can receive the beacon <italic>B</italic><sub>2</sub> and the sensor node in blue can receive the beacons <italic>B</italic><sub>1</sub> and <italic>B</italic><sub>2</sub>. Here, the communication range <italic>r</italic> is assumed to be constant in 3D [<xref ref-type="bibr" rid="b11-sensors-12-05486">11</xref>,<xref ref-type="bibr" rid="b12-sensors-12-05486">12</xref>,<xref ref-type="bibr" rid="b20-sensors-12-05486">20</xref>]. In addition, because movement of a mobile beacon in a straight line is more controllable than curved movement, the mobile beacon is assumed to follow the random waypoint (RWP) model [<xref ref-type="bibr" rid="b21-sensors-12-05486">21</xref>]; the mobile beacon moves in a series of straight paths to random destinations.</p></sec>
<sec>
<label>3.2.</label>
<title>Beacon Point Selection</title>
<p>From the viewpoint of a sensor node, the sensor node can receive a beacon when the beacon is within the communication range of the sensor node; e.g., in <xref ref-type="fig" rid="f4-sensors-12-05486">Figure 4(b)</xref>, the sensor node receives the beacons <italic>B</italic><sub>1</sub> to <italic>B</italic><sub>6</sub>. The selection of beacon points from the received beacons is performed as in LDB. When a sensor node receives the first beacon from a mobile beacon, the first beacon is selected as a beacon point; <italic>i.e., B</italic><sub>1</sub> in <xref ref-type="fig" rid="f4-sensors-12-05486">Figure 4(b)</xref>. If the sensor node receives no further beacons during a predefined time after receiving its last beacon, the last beacon is selected as a beacon point; <italic>i.e., B</italic><sub>6</sub> in <xref ref-type="fig" rid="f4-sensors-12-05486">Figure 4(b)</xref>. The above process is repeated each time the mobile beacon passes through the communication sphere of the sensor node.</p>
<p>As shown in <xref ref-type="fig" rid="f4-sensors-12-05486">Figure 4(b)</xref>, the beacon points do not lie exactly on the communication sphere of the sensor node, because the sensor node receives a beacon at every beacon distance <italic>d</italic>. When the communication range of the sensor node is <italic>r</italic>, the beacon points are located between the distances <italic>r</italic> − <italic>d</italic> and <italic>r</italic> from the sensor node. Based on the distance range between a beacon point and a sensor node, the middle value of the range, <italic>r</italic> − <italic>d</italic>/2, is estimated as the distance between the beacon point and sensor node in order to minimize the error in the estimated distance.</p>
<p>Sensor nodes are assumed to have a pressure sensor, and therefore they are assumed to know their depth [<xref ref-type="bibr" rid="b22-sensors-12-05486">22</xref>]. With this depth information, the beacon points can be projected onto the horizontal plane in which the sensor node resides, as shown in <xref ref-type="fig" rid="f4-sensors-12-05486">Figure 4(b)</xref>. When the <italic>z</italic> coordinates of a sensor node and the <italic>i<sup>th</sup></italic> beacon point are <italic>z<sub>s</sub></italic> and <italic>z<sub>i</sub></italic>, the distance 
<inline-formula>
<mml:math id="mm2" display="inline">
<mml:semantics id="sm2">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>i</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> between the sensor node and the <italic>i<sup>th</sup></italic> projected beacon point is 
<inline-formula>
<mml:math id="mm3" display="inline">
<mml:semantics id="sm3">
<mml:mrow>
<mml:msqrt>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>r</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi>d</mml:mi>
<mml:mo>/</mml:mo>
<mml:mn>2</mml:mn>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>−</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mi>i</mml:mi></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mi>s</mml:mi></mml:msub>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt></mml:mrow></mml:semantics></mml:math></inline-formula>.</p>
<p>For a system using a directional transceiver, all the projected beacon points are located between the distances <italic>r<sub>b</sub></italic> − <italic>d</italic> and <italic>r<sub>b</sub></italic> from a sensor node; here, <italic>r<sub>b</sub></italic> is the radius of the circle formed by the beam for the sensor node. Subsequently, all the estimated distances between the sensor node and projected beacon points are identically <italic>r<sub>b</sub></italic> − <italic>d</italic>/2.</p></sec>
<sec>
<label>3.3.</label>
<title>Location Estimation</title>
<p>In this subsection, we explain how to estimate the location of a sensor node based on the distances between the sensor node and the projected beacon points. First, potential locations are obtained as candidates for the location of the sensor node. Second, the location of the sensor node is estimated using the weighted mean of the potential locations.</p>
<sec>
<label>3.3.1.</label>
<title>Obtaining potential locations</title>
<p>After estimating the distances between a sensor node and projected beacon points, the following equations need to be solved for localization:
<disp-formula id="FD2">
<label>(2)</label>
<mml:math id="mm4" display="block">
<mml:semantics id="sm4">
<mml:mrow>
<mml:mrow>
<mml:mo>{</mml:mo>
<mml:mrow>
<mml:mtable columnalign="left">
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msqrt>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>y</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msqrt>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>y</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mspace width="1.5em"/>
<mml:mo>⋮</mml:mo></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msqrt>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mi>N</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>y</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mi>N</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>N</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow></mml:mrow>
<mml:mo>⇔</mml:mo>
<mml:mrow>
<mml:mo>{</mml:mo>
<mml:mrow>
<mml:mtable columnalign="left">
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>y</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>1</mml:mn>
<mml:mrow>
<mml:mo>′</mml:mo>
<mml:mn>2</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>y</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>2</mml:mn>
<mml:mrow>
<mml:mo>′</mml:mo>
<mml:mn>2</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mspace width="1.5em"/>
<mml:mo>⋮</mml:mo></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mi>N</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>y</mml:mi>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mi>N</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mo>′</mml:mo>
<mml:mn>2</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula>where (<italic>x, y</italic>) is the location of a sensor node, 
<inline-formula>
<mml:math id="mm5" display="inline">
<mml:semantics id="sm5">
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mi>i</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo>,</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mi>i</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:semantics></mml:math></inline-formula> is the location of the <italic>i<sup>th</sup></italic> projected beacon point, <italic>N</italic> is the number of the projected beacon points, and 
<inline-formula>
<mml:math id="mm6" display="inline">
<mml:semantics id="sm6">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>i</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> is the estimated distance between a sensor node and the <italic>i<sup>th</sup></italic> projected beacon point.</p>
<p>Let us explain how to estimate the location of a sensor node based on the bilateration method with <xref ref-type="fig" rid="f5-sensors-12-05486">Figures 5</xref> and <xref ref-type="fig" rid="f6-sensors-12-05486">6</xref>. When <italic>N</italic> projected beacon points are obtained, <italic>N</italic> circles can be drawn satisfying <xref ref-type="disp-formula" rid="FD2">Equation (2)</xref>; <italic>i.e.</italic>, four circles with centers 
<inline-formula>
<mml:math id="mm7" display="inline">
<mml:semantics id="sm7">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>, 
<inline-formula>
<mml:math id="mm8" display="inline">
<mml:semantics id="sm8">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>, 
<inline-formula>
<mml:math id="mm9" display="inline">
<mml:semantics id="sm9">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>3</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>, and 
<inline-formula>
<mml:math id="mm10" display="inline">
<mml:semantics id="sm10">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>4</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and radii 
<inline-formula>
<mml:math id="mm11" display="inline">
<mml:semantics id="sm11">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>, 
<inline-formula>
<mml:math id="mm12" display="inline">
<mml:semantics id="sm12">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>, 
<inline-formula>
<mml:math id="mm13" display="inline">
<mml:semantics id="sm13">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>3</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>, and 
<inline-formula>
<mml:math id="mm14" display="inline">
<mml:semantics id="sm14">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>4</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> can be drawn, as shown in <xref ref-type="fig" rid="f5-sensors-12-05486">Figure 5</xref>. The points of intersection of the <italic>N</italic> circles that are near the sensor node are obtained as potential locations for the sensor node's estimated location, as shown in <xref ref-type="fig" rid="f5-sensors-12-05486">Figure 5</xref>; some or all of the potential locations may overlap. However, because a potential location can be either of the two intersection points of two circles, a decision process is needed; here, because the intersection points are obtained using just two of many projected beacon points, this method is called bilateration [<xref ref-type="bibr" rid="b23-sensors-12-05486">23</xref>]. One of the two intersection points of the two circles with centers at two projected beacon points is closer to the circles with centers at the other projected beacon points than the other intersection point; <italic>i.e., C</italic><sub>12</sub>(1) is closer to the two circles with centers 
<inline-formula>
<mml:math id="mm15" display="inline">
<mml:semantics id="sm15">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>3</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and 
<inline-formula>
<mml:math id="mm16" display="inline">
<mml:semantics id="sm16">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>4</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> than <italic>C</italic><sub>12</sub>(2) in <xref ref-type="fig" rid="f6-sensors-12-05486">Figure 6</xref>. When <italic>C<sub>jk</sub></italic>(1) and <italic>C<sub>jk</sub></italic>(2) are the intersection points of the circles with centers 
<inline-formula>
<mml:math id="mm17" display="inline">
<mml:semantics id="sm17">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>j</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and 
<inline-formula>
<mml:math id="mm18" display="inline">
<mml:semantics id="sm18">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>k</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and the following inequality is satisfied, <italic>C<sub>jk</sub></italic>(1) is selected as the potential location <italic>P̂<sub>jk</sub></italic>; otherwise, <italic>C<sub>jk</sub></italic>(2) is selected.</p>
<disp-formula id="FD3">
<label>(3)</label>
<mml:math id="mm19" display="block">
<mml:semantics id="sm19">
<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:mi>i</mml:mi>
<mml:mo>≠</mml:mo>
<mml:mi>j</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>k</mml:mi></mml:mrow>
<mml:mi>N</mml:mi></mml:munderover>
<mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:mrow>
<mml:mrow>
<mml:mo>‖</mml:mo>
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>i</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>C</mml:mi>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mn>1</mml:mn>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mo>‖</mml:mo></mml:mrow>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>i</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow>
<mml:mo stretchy="false">|</mml:mo></mml:mrow>
<mml:mo>&lt;</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:mo>,</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo>≠</mml:mo>
<mml:mi>j</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>k</mml:mi></mml:mrow>
<mml:mi>N</mml:mi></mml:munderover>
<mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">|</mml:mo>
<mml:mrow>
<mml:mrow>
<mml:mo>‖</mml:mo>
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>i</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>C</mml:mi>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mn>2</mml:mn>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mo>‖</mml:mo></mml:mrow>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>i</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow>
<mml:mo stretchy="false">|</mml:mo></mml:mrow></mml:mrow></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula>
<p>In rare cases, the number of intersection points between two circles can be one or zero. If there is one intersection point, this single point becomes the potential location. If there is no intersection point, which occurs when the distance between the two beacon points 
<inline-formula>
<mml:math id="mm20" display="inline">
<mml:semantics id="sm20">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>j</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and 
<inline-formula>
<mml:math id="mm21" display="inline">
<mml:semantics id="sm21">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>k</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> is larger than 
<inline-formula>
<mml:math id="mm22" display="inline">
<mml:semantics id="sm22">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>j</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>k</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>, the point that divides the line segment 
<inline-formula>
<mml:math id="mm23" display="inline">
<mml:semantics id="sm23">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>j</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>k</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> joining the points 
<inline-formula>
<mml:math id="mm24" display="inline">
<mml:semantics id="sm24">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>j</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and 
<inline-formula>
<mml:math id="mm25" display="inline">
<mml:semantics id="sm25">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mi>k</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> into a 
<inline-formula>
<mml:math id="mm26" display="inline">
<mml:semantics id="sm26">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>j</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo>:</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>k</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> ratio becomes the potential location. In these two cases, a decision process is not needed.</p></sec>
<sec>
<label>3.3.2.</label>
<title>Estimating the Location of a Sensor Node Using the Weighted Mean</title>
<p>The location of a sensor node can be estimated using all the potential locations. The location of a sensor node can simply be estimated as the mean of all the potential locations. However, to improve the estimation accuracy, a weighted mean of the potential locations can be used instead. Here, the weight is determined based on a residual, which we define here. Given <italic>x̂</italic> as a solution of <italic>x</italic> at <italic>f</italic>(<italic>x</italic>) = <italic>b</italic>, the residual is <italic>b</italic> − <italic>f</italic>(<italic>x̂</italic>), which indicates how far <italic>f</italic>(<italic>x̂</italic>) is from the correct value of <italic>b</italic>, and the error is <italic>x̂</italic> − <italic>x</italic>. As we do not know <italic>x</italic>, we cannot compute the error, but we can compute the residual. From <xref ref-type="disp-formula" rid="FD2">Equation (2)</xref> <italic>N</italic> residuals associated with the potential location <italic>P<sub>jk</sub></italic>(<italic>x̂<sub>jk</sub>, ŷ<sub>jk</sub></italic>) can be computed as follows:
<disp-formula id="FD4">
<label>(4)</label>
<mml:math id="mm27" display="block">
<mml:semantics id="sm27">
<mml:mrow>
<mml:mrow>
<mml:mo>{</mml:mo>
<mml:mrow>
<mml:mtable>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msub>
<mml:mover accent="true">
<mml:mi>ɛ</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mn>1</mml:mn>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>|</mml:mo>
<mml:mrow>
<mml:msqrt>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msub>
<mml:mover accent="true">
<mml:mi>x</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msub>
<mml:mover accent="true">
<mml:mi>y</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow>
<mml:mo>|</mml:mo></mml:mrow></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msub>
<mml:mover accent="true">
<mml:mi>ɛ</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mn>2</mml:mn>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>|</mml:mo>
<mml:mrow>
<mml:msqrt>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msub>
<mml:mover accent="true">
<mml:mi>x</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msub>
<mml:mover accent="true">
<mml:mi>y</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow>
<mml:mo>|</mml:mo></mml:mrow></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msub>
<mml:mover accent="true">
<mml:mi>ɛ</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>N</mml:mi>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>|</mml:mo>
<mml:mrow>
<mml:msqrt>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msub>
<mml:mover accent="true">
<mml:mi>x</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>x</mml:mi>
<mml:mi>N</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup>
<mml:mo>+</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msub>
<mml:mover accent="true">
<mml:mi>y</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>y</mml:mi>
<mml:mi>N</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo></mml:mrow>
<mml:mn>2</mml:mn></mml:msup></mml:mrow></mml:msqrt>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mi>N</mml:mi>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow>
<mml:mo>|</mml:mo></mml:mrow></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula>Because the accuracy of a potential location is expected to be inversely proportional to the sum of the residuals, the reciprocal of the sum of the residuals represents a weighting factor. The weight for the potential location <italic>P<sub>jk</sub></italic>(<italic>x̂<sub>jk</sub>, ŷ<sub>jk</sub></italic>) is defined as follows:
<disp-formula id="FD5">
<label>(5)</label>
<mml:math id="mm28" display="block">
<mml:semantics id="sm28">
<mml:mrow>
<mml:msub>
<mml:mi>w</mml:mi>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mn>1</mml:mn>
<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:mrow>
<mml:mi>N</mml:mi></mml:munderover>
<mml:mrow>
<mml:msub>
<mml:mover accent="true">
<mml:mi>ɛ</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>i</mml:mi>
<mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula>Finally, the location of a sensor node is estimated as the weighted mean of all the potential locations.</p>
<disp-formula id="FD6">
<label>(6)</label>
<mml:math id="mm29" display="block">
<mml:semantics id="sm29">
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:mover accent="true">
<mml:mi>x</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mo>,</mml:mo>
<mml:mover accent="true">
<mml:mi>y</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:munderover>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>−</mml:mo>
<mml:mn>1</mml:mn></mml:mrow></mml:munderover>
<mml:mrow>
<mml:munderover>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>=</mml:mo>
<mml:mi>j</mml:mi>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mi>N</mml:mi></mml:munderover>
<mml:mrow>
<mml:msub>
<mml:mi>w</mml:mi>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:msub>
<mml:mover accent="true">
<mml:mi>x</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mover accent="true">
<mml:mi>y</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub>
<mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mrow></mml:mrow>
<mml:mrow>
<mml:munderover>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
<mml:mo>−</mml:mo>
<mml:mn>1</mml:mn></mml:mrow></mml:munderover>
<mml:mrow>
<mml:munderover>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>=</mml:mo>
<mml:mi>j</mml:mi>
<mml:mo>+</mml:mo>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mi>N</mml:mi></mml:munderover>
<mml:mrow>
<mml:msub>
<mml:mi>w</mml:mi>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>k</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mrow></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula>
<p>Less than three beacon points may be acquired for some sensor nodes in certain circumstances. In this case, because the location of a sensor node cannot be estimated through <xref ref-type="disp-formula" rid="FD6">Equation (6)</xref>, another approach is needed. When just two beacon points 
<inline-formula>
<mml:math id="mm30" display="inline">
<mml:semantics id="sm30">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and 
<inline-formula>
<mml:math id="mm31" display="inline">
<mml:semantics id="sm31">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> are acquired for a sensor node, the intersection points <italic>C</italic><sub>12</sub>(1) and <italic>C</italic><sub>12</sub>(2) of two circles with centers 
<inline-formula>
<mml:math id="mm32" display="inline">
<mml:semantics id="sm32">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and 
<inline-formula>
<mml:math id="mm33" display="inline">
<mml:semantics id="sm33">
<mml:mrow>
<mml:mi>B</mml:mi>
<mml:msubsup>
<mml:mi>P</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and radii 
<inline-formula>
<mml:math id="mm34" display="inline">
<mml:semantics id="sm34">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>1</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> and 
<inline-formula>
<mml:math id="mm35" display="inline">
<mml:semantics id="sm35">
<mml:mrow>
<mml:msubsup>
<mml:mi>r</mml:mi>
<mml:mn>2</mml:mn>
<mml:mo>′</mml:mo></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula> are obtained. Because there are no other beacon points available to the decision-making process, the neighboring sensor nodes can play the role of an additional beacon point in order to estimate the sensor location. The sensor node can receive the location information of neighboring sensor nodes by sending a request to the neighboring sensor nodes that know their location after localization. The sensor node just knows that the neighboring sensor nodes are within the communication range without the distance information between the sensor node and the neighboring sensor nodes. If one of the intersection points is close to the sensor node, more sensor nodes among neighboring sensor nodes of the sensor node are expected to be within the communication range of the intersection point, compared to the other intersection point. By comparing the number of neighboring sensor nodes of the sensor node within the communication range for each intersection point, one of the two intersection points that has more neighboring sensor nodes of the sensor node is estimated as the location of the sensor node. When a sensor node has less than two beacon points, the estimated locations of the neighboring sensor nodes can be used. In this case, the location of the sensor node is estimated as the midpoint of all the neighboring sensor nodes.</p>
<p>It is noteworthy that the main feature of LoMoB that can improve LDB is the use of the weighted mean of all the potential locations. In LDB, when a sensor node has four projected beacon points <italic>F</italic><sub>1</sub>, <italic>L</italic><sub>1</sub>, <italic>F</italic><sub>2</sub>, and <italic>L</italic><sub>2</sub>, as shown in <xref ref-type="fig" rid="f3-sensors-12-05486">Figure 3(b)</xref>, two possible points are obtained based on <italic>F</italic><sub>1</sub> and <italic>L</italic><sub>1</sub> and one point between the two is estimated as the location of the sensor node based on <italic>F</italic><sub>2</sub> and <italic>L</italic><sub>2</sub>. Here, the error in the estimated location depends largely on the distance between <italic>F</italic><sub>1</sub> and <italic>L</italic><sub>1</sub> [<xref ref-type="bibr" rid="b16-sensors-12-05486">16</xref>]. If <italic>F</italic><sub>1</sub> and <italic>L</italic><sub>1</sub> are located very close to each other, the location error is expected to be large. In this case, a better choice may be that <italic>F</italic><sub>2</sub> and <italic>L</italic><sub>2</sub> (or another two projected beacon points) are used for the two possible points, rather than <italic>F</italic><sub>1</sub> and <italic>L</italic><sub>1</sub>. However, the selection of two projected beacon points for the possible points has not yet been studied. If the errors of the beacon points <italic>F</italic><sub>1</sub> and <italic>L</italic><sub>1</sub> increase because of some factors such as irregularities in the radius of the circle formed by the transceiver's beam and the location error of a mobile beacon, the errors of the two possible points also increase, which results in an increase of the location error. Even though more beacon points, in addition to <italic>F</italic><sub>1</sub>, <italic>L</italic><sub>1</sub>, <italic>F</italic><sub>2</sub>, and <italic>L</italic><sub>2</sub>, are obtained, the localization accuracy is not improved because the additional beacon points are not used for localization. As in LDB, LoMoB obtains two intersection points based on two beacon points and determines one point between the two as a potential location for the location of the sensor node based on the other beacon points. However, compared to LDB, LoMoB estimates the location of a sensor node based on all the potential locations, not just one potential location. In addition, potential locations with a high weight contribute more to the estimation of the location of the sensor node than other potential locations. For these reasons, LoMoB is expected to improve LDB in challenging underwater environments even though LoMoB uses just four beacon points, as does LDB. If more than four beacon points are used, the localization accuracy is expected to improve further.</p></sec></sec></sec>
<sec>
<label>4.</label>
<title>Performance Evaluations</title>
<p>In this section, we first describe the simulation parameters, then introduce the metric to evaluate the localization accuracy and, finally, we compare the localization accuracy of LoMoB with that of LDB through simulations.</p>
<sec>
<label>4.1.</label>
<title>Simulation Setup</title>
<p>The sensing space for UASN is a rectangular parallelepiped of 1 km × 1 km × 100 m, in which 100 sensor nodes are randomly deployed. A mobile beacon is assumed to move linearly at a velocity of 1 m/s and broadcasts a beacon at every beacon interval, <italic>i.e.</italic>, each 1 s. To fairly compare LoMoB and LDB, we assume that a mobile beacon has a directional transceiver and just four beacon points are used for localization because LDB works for a system using a directional transceiver and uses four beacon points. The angle of the directional transceiver's beam is 60°. Because it is more convenient to move a mobile beacon on the sea surface than underwater in real underwater environments, the mobile beacon is assumed to move on the sea surface.</p>
<p>In LoMoB and LDB, localization begins by selecting beacon points. Any projected beacon points that are not exactly on the circle formed by the transceiver's beam for a sensor node cause an estimation error of the distance between the projected beacon point and the sensor node, which results in an error in the estimated location. The beacon distance causes projected beacon points to be located not exactly on the circle formed by the beam. In addition, the phenomena such as reflection, diffraction, and refraction in underwater environments cause irregularities in the radius of the circle formed by the beam. To improve the reality of our simulations, irregularities in the radius of the circle are modeled as <italic>r̂</italic> = <italic>r</italic> + <italic>e<sub>r</sub></italic>, where <italic>e<sub>r</sub></italic> is a random value with the Gaussian distribution <italic>N</italic> (0, 
<inline-formula>
<mml:math id="mm36" display="inline">
<mml:semantics id="sm36">
<mml:mrow>
<mml:msubsup>
<mml:mi>σ</mml:mi>
<mml:mi>r</mml:mi>
<mml:mn>2</mml:mn></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>). Because the GPS error in a mobile beacon, water fluctuations, and tidal currents can cause errors in the location of the mobile beacon, we assume the location information broadcasted from a mobile beacon is error prone [<xref ref-type="bibr" rid="b24-sensors-12-05486">24</xref>]. The location error of a mobile beacon is modeled as <bold>x̂<sub>m</sub></bold> = <bold>x<sub>m</sub></bold> + <bold>e<sub>m</sub></bold>, where <bold>x̂<sub>m</sub></bold> = [<italic>x̂, ŷ</italic>]<sup>T</sup> is the measured location of the mobile beacon located at <bold>x<sub>m</sub></bold> = [<italic>x, y</italic>]<sup>T</sup> and <bold>e<sub>m</sub></bold> = [<italic>e<sub>x</sub>, e<sub>y</sub></italic>]<sup>T</sup> is a random vector whose <italic>e<sub>x</sub></italic> and <italic>e<sub>y</sub></italic> are independent and identical random values with the Gaussian distribution <italic>N</italic>(0, 
<inline-formula>
<mml:math id="mm37" display="inline">
<mml:semantics id="sm37">
<mml:mrow>
<mml:msubsup>
<mml:mi>σ</mml:mi>
<mml:mi>m</mml:mi>
<mml:mn>2</mml:mn></mml:msubsup></mml:mrow></mml:semantics></mml:math></inline-formula>). We use Matlab to perform these simulations.</p></sec>
<sec>
<label>4.2.</label>
<title>Metrics</title>
<p>To compare the localization accuracy of LoMoB and LDB, we define the average location error as follows:
<disp-formula id="FD7">
<label>(7)</label>
<mml:math id="mm38" display="block">
<mml:semantics id="sm38">
<mml:mrow>
<mml:msub>
<mml:mi>e</mml:mi>
<mml:mrow>
<mml:mtext mathvariant="italic">average</mml:mtext></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mn>1</mml:mn>
<mml:mi>N</mml:mi></mml:mfrac>
<mml:munderover>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>k</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>‖</mml:mo>
<mml:mrow>
<mml:msub>
<mml:mover accent="true">
<mml:mi>x</mml:mi>
<mml:mo>^</mml:mo></mml:mover>
<mml:mi>k</mml:mi></mml:msub>
<mml:mo>−</mml:mo>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mi>k</mml:mi></mml:msub></mml:mrow>
<mml:mo>‖</mml:mo></mml:mrow></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula>where <bold>x̂<sub>k</sub></bold> = (<italic>x̂<sub>k</sub>, ŷ<sub>k</sub></italic>) is the estimated location of a sensor node that is located at <bold>x<sub>k</sub></bold> = (<italic>x<sub>k</sub>, y<sub>k</sub></italic>) and <italic>N</italic> is the number of sensor nodes.</p>
<p>Because the average location error may be seriously affected by a small number of large location errors, the ratio of localized sensor nodes with location errors below a given threshold can be used as an additional metric for evaluating the localization accuracy. The ratio of localized sensor nodes below a given threshold allows the localization accuracy to be assessed in greater depth than the average location error alone.</p></sec>
<sec sec-type="results">
<label>4.3.</label>
<title>Simulation Results</title>
<p>Because the beacon distance, irregularities in the radius of the circle formed by the transceiver's beam, and the location error of a mobile beacon all influence the accuracy of distance estimation between a sensor node and a projected beacon point, the localization accuracy is analyzed with respect to these factors.</p>
<p><xref ref-type="fig" rid="f7-sensors-12-05486">Figure 7(a)</xref> compares the average location error as a function of the beacon distance and <xref ref-type="fig" rid="f7-sensors-12-05486">Figure 7(b)</xref> compares the ratio of localized sensor nodes with location errors below 10 m. The average location error of LDB is shown to fluctuate more and to be larger than that of LoMoB. As the beacon distance increases, the performance gap between LoMoB and LDB tends to widen. <xref ref-type="fig" rid="f7-sensors-12-05486">Figure 7</xref> demonstrates that LoMoB is less vulnerable to the beacon distance than LDB.</p>
<p>In real underwater environments, the radius of the circle formed by the transceiver's beam is expected to fluctuate. Irregularities in the radius of the circle cause sensor nodes to provide erroneous estimates of distances between the projected beacon points and a sensor node, in addition to the error associated with the beacon distance. <xref ref-type="fig" rid="f8-sensors-12-05486">Figure 8(a)</xref> compares the average location error as a function of the standard deviation <italic>σ<sub>r</sub></italic> in the radius of the circle and <xref ref-type="fig" rid="f8-sensors-12-05486">Figure 8(b)</xref> compares the ratio of localized sensor nodes with location errors below 10 m. As shown in the figures, the average location error increases as irregularities in the radius of the circle increase. LoMoB has 32.4%–45.8% smaller location errors than LDB. The ratios of localized sensor nodes show a maximum difference of 7.4%. LoMoB is verified to be more tolerant to irregularities in the radius of the circle formed by the transceiver's beam than LDB.</p>
<p>A mobile beacon is generally assumed to know its own location. In reality, the location information of a mobile beacon may be erroneous. As well as irregularities in the radius of the circle formed by the transceiver's beam, the location error of a mobile beacon needs to be considered because this also causes erroneous estimation of the distances between the projected beacon points and a sensor node. <xref ref-type="fig" rid="f9-sensors-12-05486">Figure 9(a)</xref> compares the average location error according to the standard deviation <italic>σ<sub>m</sub></italic> in the location error of a mobile beacon and <xref ref-type="fig" rid="f9-sensors-12-05486">Figure 9(b)</xref> compares the ratio of localized sensor nodes with location errors below 10 m. LoMoB improves the average location error by 21.5%–32.4% compared to LDB. The ratios of localized sensor nodes show a maximum difference of 4.3%. In addition, <xref ref-type="fig" rid="f10-sensors-12-05486">Figure 10</xref> shows the average location error of LDB and LoMoB applying a simple mean and the weighted mean; if all the weights are equal, then the weighted mean is the same as the simple mean. LoMoB applying a simple mean and the weighted mean improves the average location error by 14.3%–26.9% and 21.5%–32.4%, respectively. This indicates that the use of all the potential locations in LoMoB is the main factor to improve LDB and the use of the weights results in additional increase in the localization accuracy.</p>
<p>The localization accuracy performance of LoMoB and LDB was compared through the average location error and the ratio of localized sensor nodes with location errors below 10 m according to the beacon distance, irregularities in the radius of the circle formed by the transceiver's beam, and the location error of a mobile beacon. The simulation results verify that LoMoB is more tolerant to estimation errors of the distances between the projected beacon points and a sensor node. Subsequently, LoMoB is more promising than LDB in harsh underwater environments.</p></sec></sec>
<sec sec-type="conclusions">
<label>5.</label>
<title>Conclusions</title>
<p>In this paper, we proposed a range-free localization scheme for UASN with a mobile beacon that provides the potential locations with weighting factors according to residuals and estimates the location of a sensor node through the weighted mean of the potential locations. Because LoMoB localizes a sensor node based on the weights of the potential locations, it improves the localization accuracy and is more tolerant to errors in the estimation of the distance between projected beacon points and sensor nodes. Simulation results show that LoMoB significantly improves the localization accuracy of LDB, especially in underwater environments that cause irregularities in the radius of the circle formed by the transceiver's beam and the location error of a mobile beacon. Our simulations demonstrated that LoMoB is more robust with respect to errors in distance estimation than LDB.</p></sec></body>
<back>
<ack>
<p>This work was supported by the World-Class University Program through the National Research Foundation of Korea (R31-10026), and Grant (K20903001804-11E0100-00910) funded by the Ministry of Education, Science, and Technology (MEST), also by a grant (07SeaHeroB01-03) from Plant Technology Advancement Program funded by Ministry of Construction and Transportation.</p></ack>
<ref-list>
<title>References</title>
<ref id="b1-sensors-12-05486"><label>1.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Mohamed</surname><given-names>N.</given-names></name><name><surname>Jawhar</surname><given-names>I.</given-names></name><name><surname>Al-Jaroodi</surname><given-names>J.</given-names></name><name><surname>Zhang</surname><given-names>L.</given-names></name></person-group><article-title>Sensor network architectures for monitoring underwater pipelines</article-title><source>Sensors</source><year>2011</year><volume>11</volume><fpage>10738</fpage><lpage>10764</lpage><pub-id pub-id-type="doi">10.3390/s111110738</pub-id><pub-id pub-id-type="pmid">22346669</pub-id></citation></ref>
<ref id="b2-sensors-12-05486"><label>2.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Yang</surname><given-names>X.</given-names></name><name><surname>Ong</surname><given-names>K.G.</given-names></name><name><surname>Dreschel</surname><given-names>W.R.</given-names></name><name><surname>Zeng</surname><given-names>K.</given-names></name><name><surname>Mungle</surname><given-names>C.S.</given-names></name><name><surname>Grimes</surname><given-names>C.A.</given-names></name></person-group><article-title>Design of a wireless sensor network for long-term, <italic>in-situ</italic> monitoring of an aqueous environment</article-title><source>Sensors</source><year>2002</year><volume>2</volume><fpage>455</fpage><lpage>72</lpage><pub-id pub-id-type="doi">10.3390/s21100455</pub-id></citation></ref>
<ref id="b3-sensors-12-05486"><label>3.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Sozer</surname><given-names>E.M.</given-names></name><name><surname>Stojanovic</surname><given-names>M.</given-names></name><name><surname>Proakis</surname><given-names>J.G.</given-names></name></person-group><article-title>Underwater acoustic networks</article-title><source>IEEE J. Ocean. Eng.</source><year>2000</year><volume>25</volume><fpage>72</fpage><lpage>83</lpage><pub-id pub-id-type="doi">10.1109/48.820738</pub-id></citation></ref>
<ref id="b4-sensors-12-05486"><label>4.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Teymorian</surname><given-names>A.Y.</given-names></name><name><surname>Cheng</surname><given-names>W.</given-names></name><name><surname>Ma</surname><given-names>L.</given-names></name><name><surname>Cheng</surname><given-names>X.</given-names></name><name><surname>Lu</surname><given-names>X.</given-names></name><name><surname>Lu</surname><given-names>Z.</given-names></name></person-group><article-title>3D underwater sensor network localization</article-title><source>IEEE Trans. Mob. Comput.</source><year>2009</year><volume>8</volume><fpage>1610</fpage><lpage>1621</lpage><pub-id pub-id-type="doi">10.1109/TMC.2009.80</pub-id></citation></ref>
<ref id="b5-sensors-12-05486"><label>5.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Zhou</surname><given-names>Z.</given-names></name><name><surname>Cui</surname><given-names>J.</given-names></name><name><surname>Zhou</surname><given-names>S.</given-names></name></person-group><article-title>Efficient localization for large-scale underwater sensor networks</article-title><source>Ad Hoc Netw.</source><year>2010</year><volume>8</volume><fpage>267</fpage><lpage>279</lpage><pub-id pub-id-type="doi">10.1016/j.adhoc.2009.08.005</pub-id></citation></ref>
<ref id="b6-sensors-12-05486"><label>6.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Cheng</surname><given-names>X.</given-names></name><name><surname>Shu</surname><given-names>H.</given-names></name><name><surname>Liang</surname><given-names>Q.</given-names></name><name><surname>Du</surname><given-names>D.H.-C.</given-names></name></person-group><article-title>Silent positioning in underwater acoustic sensor networks</article-title><source>IEEE Trans. Veh. Technol.</source><year>2008</year><volume>57</volume><fpage>1756</fpage><lpage>1766</lpage><pub-id pub-id-type="doi">10.1109/TVT.2007.912142</pub-id></citation></ref>
<ref id="b7-sensors-12-05486"><label>7.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Cheng</surname><given-names>W.</given-names></name><name><surname>Thaeler</surname><given-names>A.</given-names></name><name><surname>Cheng</surname><given-names>X.</given-names></name><name><surname>Liu</surname><given-names>F.</given-names></name><name><surname>Lu</surname><given-names>X.</given-names></name><name><surname>Lu</surname><given-names>Z.</given-names></name></person-group><article-title>Time-Synchronization Free Localization in Large Scale Underwater Acoustic Sensor Networks</article-title><conf-name>Proceedings of the 29th IEEE ICDCS</conf-name><conf-loc>Montreal, QC, Canada</conf-loc><conf-date>22–26 June 2009</conf-date><fpage>80</fpage><lpage>87</lpage></citation></ref>
<ref id="b8-sensors-12-05486"><label>8.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Cui</surname><given-names>J.H.</given-names></name><name><surname>Zhou</surname><given-names>Z.</given-names></name><name><surname>Bagtzoglou</surname><given-names>A.</given-names></name></person-group><article-title>Scalable Localization with Mobility Prediction for Underwater Sensor Networks</article-title><conf-name>Proceedings of the 2nd ACM International Workshop on UnderWater Networks</conf-name><conf-loc>Montreal, QC, Canada</conf-loc><conf-date>14 September 2007</conf-date><fpage>2198</fpage><lpage>2206</lpage></citation></ref>
<ref id="b9-sensors-12-05486"><label>9.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Mirza</surname><given-names>D.</given-names></name><name><surname>Schurgers</surname><given-names>C.</given-names></name></person-group><article-title>Motion-Aware Self-Localization for Underwater Networks</article-title><conf-name>Proceedings of the 3rd ACM International Workshop on UnderWater Networks</conf-name><conf-loc>San Francisco, CA, USA</conf-loc><conf-date>15 September 2008</conf-date><fpage>51</fpage><lpage>58</lpage></citation></ref>
<ref id="b10-sensors-12-05486"><label>10.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Mirza</surname><given-names>D.</given-names></name><name><surname>Schurgers</surname><given-names>C.</given-names></name></person-group><article-title>Collaborative Localization for Fleets of Underwater Drifters</article-title><conf-name>Proceedings of the IEEE OCEANS</conf-name><conf-loc>Vancouver, BC, Canada</conf-loc><conf-date>30 September–4 October 2007</conf-date><fpage>1</fpage><lpage>6</lpage></citation></ref>
<ref id="b11-sensors-12-05486"><label>11.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Chandrasekhar</surname><given-names>V.</given-names></name><name><surname>Seah</surname><given-names>W.</given-names></name></person-group><article-title>An Area Localization Scheme for Underwater Sensor Networks</article-title><conf-name>Proceedings of the IEEE OCEANS Asia Pacific Conference</conf-name><conf-loc>Sydney, Australia</conf-loc><conf-date>16–19 May 2006</conf-date><fpage>1</fpage><lpage>8</lpage></citation></ref>
<ref id="b12-sensors-12-05486"><label>12.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Zhou</surname><given-names>Y.</given-names></name><name><surname>He</surname><given-names>J.</given-names></name><name><surname>Chen</surname><given-names>K.</given-names></name><name><surname>Chen</surname><given-names>J.</given-names></name><name><surname>Liang</surname><given-names>A.</given-names></name></person-group><article-title>An area localization Scheme for large scale Underwater Wireless Sensor Networks</article-title><conf-name>Proceedings of the WRI International Conference on Communications and Mobile Computing</conf-name><conf-loc>Kunming, China</conf-loc><conf-date>6–8 January 2009</conf-date><fpage>543</fpage><lpage>547</lpage></citation></ref>
<ref id="b13-sensors-12-05486"><label>13.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Erol</surname><given-names>M.</given-names></name><name><surname>Vieira</surname><given-names>L.</given-names></name><name><surname>Gerla</surname><given-names>M.</given-names></name></person-group><article-title>Localization with DiveNRise (DNR) Beacons for Underwater Acoustic Sensor Networks</article-title><conf-name>Proceedings of the 2nd ACM International Workshop on UnderWater Networks</conf-name><conf-loc>Montreal, QC, Canada</conf-loc><conf-date>14 September 2007</conf-date><fpage>97</fpage><lpage>100</lpage></citation></ref>
<ref id="b14-sensors-12-05486"><label>14.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Erol</surname><given-names>M.</given-names></name><name><surname>Vieira</surname><given-names>L.F.M.</given-names></name><name><surname>Caruso</surname><given-names>A.</given-names></name><name><surname>Paparella</surname><given-names>F.</given-names></name><name><surname>Gerla</surname><given-names>M.</given-names></name><name><surname>Oktug</surname><given-names>S.</given-names></name></person-group><article-title>Multi Stage Underwater Sensor Localization Using Mobile Beacons</article-title><conf-name>Proceedings of the 2nd International Conference on Sensor Technologies and Applications</conf-name><conf-loc>Cap Esterel, France</conf-loc><conf-date>25–31 August 2008</conf-date><fpage>710</fpage><lpage>714</lpage></citation></ref>
<ref id="b15-sensors-12-05486"><label>15.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Erol</surname><given-names>M.</given-names></name><name><surname>Vieira</surname><given-names>L.</given-names></name><name><surname>Gerla</surname><given-names>M.</given-names></name></person-group><article-title>AUV-Aided Localization for Underwater Sensor Networks</article-title><conf-name>Proceedings of the International Conference on Wireless Algorithms, Systems and Applications</conf-name><conf-loc>Chicago, IL, USA</conf-loc><conf-date>1–3 August 2007</conf-date><fpage>44</fpage><lpage>54</lpage></citation></ref>
<ref id="b16-sensors-12-05486"><label>16.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Luo</surname><given-names>H.</given-names></name><name><surname>Guo</surname><given-names>Z.</given-names></name><name><surname>Dong</surname><given-names>W.</given-names></name><name><surname>Hong</surname><given-names>F.</given-names></name><name><surname>Zhao</surname><given-names>Y.</given-names></name></person-group><article-title>LDB: Localization with directional beacons for sparse 3D underwater acoustic sensor networks</article-title><source>J. Netw.</source><year>2010</year><volume>5</volume><fpage>28</fpage><lpage>38</lpage></citation></ref>
<ref id="b17-sensors-12-05486"><label>17.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Syed</surname><given-names>A.A.</given-names></name><name><surname>Heidemann</surname><given-names>J.</given-names></name></person-group><article-title>Time Synchronization for High Latency Acoustic Networks</article-title><conf-name>Proceedings of the 25th IEEE International Conference on Computer Communications</conf-name><conf-loc>Barcelona, Spain</conf-loc><conf-date>23–29 April 2006</conf-date><fpage>1</fpage><lpage>12</lpage></citation></ref>
<ref id="b18-sensors-12-05486"><label>18.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Syed</surname><given-names>A.A.</given-names></name><name><surname>Ye</surname><given-names>W.</given-names></name><name><surname>Heidemann</surname><given-names>J.</given-names></name></person-group><article-title>T-Lohi: A New Class of MAC Protocols for Underwater Acoustic Sensor Networks</article-title><conf-name>Proceedings of the 27th IEEE International Conference on Computer Communications</conf-name><conf-loc>Phoenix, AZ, USA</conf-loc><conf-date>13–18 April 2008</conf-date><fpage>231</fpage><lpage>235</lpage></citation></ref>
<ref id="b19-sensors-12-05486"><label>19.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Won</surname><given-names>T.-H.</given-names></name><name><surname>Park</surname><given-names>S.-J.</given-names></name></person-group><article-title>Design and implementation of an omni-directional underwater acoustic micro-modem based on a low-power micro-controller unit</article-title><source>Sensors</source><year>2012</year><volume>12</volume><fpage>2309</fpage><lpage>2323</lpage><pub-id pub-id-type="doi">10.3390/s120202309</pub-id><pub-id pub-id-type="pmid">22438765</pub-id></citation></ref>
<ref id="b20-sensors-12-05486"><label>20.</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Lurton</surname><given-names>X.</given-names></name></person-group><source>An Introduction to Underwater Acoustics—Principles and Applications</source><publisher-name>Springer, Praxis Publishing</publisher-name><publisher-loc>Berlin, Germany</publisher-loc><year>2002</year></citation></ref>
<ref id="b21-sensors-12-05486"><label>21.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Broch</surname><given-names>J.</given-names></name><name><surname>Maltz</surname><given-names>D.A.</given-names></name><name><surname>Johnson</surname><given-names>D.B.</given-names></name><name><surname>Hu</surname><given-names>Y.C.</given-names></name><name><surname>Jetcheva</surname><given-names>J.G.</given-names></name></person-group><article-title>A Performance Comparison of Multi-Hop Wireless <italic>Ad Hoc</italic> Network Routing Protocols</article-title><conf-name>Proceedings of the ACM International Conference on Mobile Computing Networking</conf-name><conf-loc>Dallas, TX, USA</conf-loc><conf-date>July 1998</conf-date><fpage>85</fpage><lpage>97</lpage></citation></ref>
<ref id="b22-sensors-12-05486"><label>22.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Isik</surname><given-names>M.T.</given-names></name><name><surname>Akan</surname><given-names>O.B.</given-names></name></person-group><article-title>A three dimensional localization algorithm for underwater acoustic sensor networks</article-title><source>IEEE Trans. Wirel. Commun.</source><year>2009</year><volume>8</volume><fpage>4457</fpage><lpage>4463</lpage><pub-id pub-id-type="doi">10.1109/TWC.2009.081628</pub-id></citation></ref>
<ref id="b23-sensors-12-05486"><label>23.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Cheng</surname><given-names>W.</given-names></name><name><surname>Teymorian</surname><given-names>A.Y.</given-names></name><name><surname>Ma</surname><given-names>L.</given-names></name><name><surname>Cheng</surname><given-names>X.</given-names></name><name><surname>Lu</surname><given-names>X.</given-names></name><name><surname>Lu</surname><given-names>Z.</given-names></name></person-group><article-title>Underwater Localization in Sparse 3D Acoustic Sensor Networks</article-title><conf-name>Proceedings of the 27th IEEE International Conference on Computer Communications</conf-name><conf-loc>Phoenix, AZ, USA</conf-loc><conf-date>13–18 April 2008</conf-date><fpage>798</fpage><lpage>806</lpage></citation></ref>
<ref id="b24-sensors-12-05486"><label>24.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>He</surname><given-names>T.</given-names></name><name><surname>Huang</surname><given-names>C.</given-names></name><name><surname>Blum</surname><given-names>B.M.</given-names></name><name><surname>Stankovic</surname><given-names>J.A.</given-names></name><name><surname>Abdelzaher</surname><given-names>T.F.</given-names></name></person-group><article-title>Range-free localization schemes for large scale sensor networks</article-title><source>ACM Trans. Embed. Comput. Syst.</source><year>2005</year><volume>4</volume><fpage>877</fpage><lpage>906</lpage><pub-id pub-id-type="doi">10.1145/1113830.1113837</pub-id></citation></ref></ref-list>
<sec sec-type="display-objects">
<title>Figures</title>
<fig id="f1-sensors-12-05486" position="float">
<label>Figure 1.</label>
<caption>
<p>Movement of a mobile beacon for localization in underwater environments.</p></caption>
<graphic xlink:href="sensors-12-05486f1.gif"/></fig>
<fig id="f2-sensors-12-05486" position="float">
<label>Figure 2.</label>
<caption>
<p>System environment and beacon point selection and projection for LDB. (<bold>a</bold>) System environment with an AUV that has a directional transceiver; (<bold>b</bold>) Selection and projection of beacon points from among the received beacons.</p></caption>
<graphic xlink:href="sensors-12-05486f2.gif"/></fig>
<fig id="f3-sensors-12-05486" position="float">
<label>Figure 3.</label>
<caption>
<p>Location estimation with projected beacon points based on geometric constraints. (<bold>a</bold>) Location estimation based on two projected beacon points; (<bold>b</bold>) Location decision using two additional projected beacon points.</p></caption>
<graphic xlink:href="sensors-12-05486f3.gif"/></fig>
<fig id="f4-sensors-12-05486" position="float">
<label>Figure 4.</label>
<caption>
<p>System environment, beacon point selection, and projection for LoMoB. (<bold>a</bold>) System environment with a mobile beacon that has an omnidirectional transceiver; (<bold>b</bold>) Selection and projection of beacon points from among the received beacons.</p></caption>
<graphic xlink:href="sensors-12-05486f4.gif"/></fig>
<fig id="f5-sensors-12-05486" position="float">
<label>Figure 5.</label>
<caption>
<p>Estimation of the sensor node location using projected beacon points.</p></caption>
<graphic xlink:href="sensors-12-05486f5.gif"/></fig>
<fig id="f6-sensors-12-05486" position="float">
<label>Figure 6.</label>
<caption>
<p>Selection of a potential location between two intersection points.</p></caption>
<graphic xlink:href="sensors-12-05486f6.gif"/></fig>
<fig id="f7-sensors-12-05486" position="float">
<label>Figure 7.</label>
<caption>
<p>Localization accuracy as a function of beacon distance. (<bold>a</bold>) Average location error; (<bold>b</bold>) Ratio of localized sensor nodes.</p></caption>
<graphic xlink:href="sensors-12-05486f7.gif"/></fig>
<fig id="f8-sensors-12-05486" position="float">
<label>Figure 8.</label>
<caption>
<p>Localization accuracy as a function of standard deviation <italic>σ<sub>r</sub></italic> in the radius of the circle formed by the transceiver's beam. (<bold>a</bold>) Average location error; (<bold>b</bold>) Ratio of localized sensor nodes.</p></caption>
<graphic xlink:href="sensors-12-05486f8.gif"/></fig>
<fig id="f9-sensors-12-05486" position="float">
<label>Figure 9.</label>
<caption>
<p>Localization accuracy as a function of standard deviation <italic>σ<sub>m</sub></italic> in the location error of a mobile beacon. (<bold>a</bold>) Average location error; (<bold>b</bold>) Ratio of localized sensor nodes.</p></caption>
<graphic xlink:href="sensors-12-05486f9.gif"/></fig>
<fig id="f10-sensors-12-05486" position="float">
<label>Figure 10.</label>
<caption>
<p>Comparison between simple mean and weighted mean.</p></caption>
<graphic xlink:href="sensors-12-05486f10.gif"/></fig></sec></back></article>
