I. I NTRODUCTION
Underwater Sensor Networks (USN) are emerging as popular tools in ocean observations. Currently, there are few
testbeds. The wired ocean bottom network, NEPTUNE [1]
and the wireless acoustic Seaweb [2] are two examples. As
USNs are in the early development stage, most of the real life
experiments are concerned with the physical layer issues. On
the other hand, research is widely based on simulation studies
for synchronization, localization, medium access and routing
protocols.
In this paper, we focus on two fundamental problems:
localization and routing. Sensed data are meaningful with time
and location information, e.i, localization is essential for data
tagging. Sending the data efficiently to a sink is another major
issue in sensor networks. In USNs, more than one sink may
be employed and the underwater nodes may act as relays for
routing the data from source to sink. In this work, we combine
these two significant tasks in a framework where they mutually
help each other. We use a limited number of Mobile Beacon
and Sink (MBS) nodes. MBSs are able to move vertically in
the water column. The rest of the nodes stay under the water
and drift with the currents. MBSs periodically descent to the
same depth with the underwater sensors to localize them and
collect their data. Then, MBSs surface to receive coordinates
from the GPS and upload the data that has been collected by
the underwater sensors to a ground station. MBSs can ascent
and descent with modifying density. Real life implementation
of such floats are used in Argo project [3]. A similar technique
can be applied to MBS nodes to achieve vertical movement.
Localization is done iteratively. Initially MBS nodes are
localized via GPS. They periodically announce their coordinates while diving to the deepest level of the underwater
network. Upon hearing from several beacons (at least three
beacons for 2D and four beacons for 3D) a node is localized.
This full text paper was peer reviewed at the direction of IEEE Communications Society subject matter experts for publication in the IEEE INFOCOM 2008 proceedings.
Fig. 2.
Fig. 3.
Fig. 1.
model
This full text paper was peer reviewed at the direction of IEEE Communications Society subject matter experts for publication in the IEEE INFOCOM 2008 proceedings.
Localized nodes
1
0.9
25
Localized nodes/nodes
0.8
0.7
20
Mean Error
0.6
0.5
15
0.4
10
0.3
0.2
V. C ONCLUSION
0.1
0
50
100
150
0
200 50
nodes
100
150
200
nodes
Fig. 4. Localization success and error for the number of underwater nodes
between 50-200 and 25 MBSs.
IV. ROUTING
The underwater nodes learn the beginning of the routing
round and the ID of the potential sinks at the localization
round. Each node independently selects an MBS and forward
its data towards that MBS. The forwarding decision is taken
according to the relative position and velocity of the MBS
node. The underwater nodes benefit from mobility and try to
catch up with the MBSs. According to the catch up or pass
(C/P) algorithm, a node either carries the packet until it catches
up with the selected MBS or, if the MBS and the node is not
likely to catch up then it forwards the packet to a slower or
faster relay.
The algorithm works as follows. The source node compares
its position and velocity with the MBS. If MBS is behind and
the velocity of the MBS is larger than the node (vM BS >
vN ), then, MBS has a chance to catch up with the node. The
packet is delayed for some time. Delay is a function of the
distance in between and the difference between the velocities,
i.e., delay = f (distance, vM BS , vN ). If MBS is behind and
vM BS vN , the MBS will never catch up, so the packet is
passed to a slower neighbour. Note that, the velocity values
of the neighbours are learnt during localization. If MBS is
ahead of the forwarding node and vM BS < vN , C/P delays
the packet on the node again because this time the node can
catch up with MBS. However, if vM BS vN then, the node
is unable to reach MBS and it passes the packet to a faster
neighbour.
When the packet is carried, waiting for a possibility of
catching up, it is delayed until the forwarding zone of the
MBS (see Fig1(b)). When the node is within the forwarding
zone, geographic coordinates are used for forwarding. Because
the velocities indicate the horizontal displacement (vyi = 0)
and the packet is delayed until the x coordinates of the node
and the MBS are close enough, in the vertical axis they may
be further away. In the forwarding zone, only y coordinates
are used to reach the MBS. The node with the least vertical
distance is selected as the relay.
Note that, the delay value is bounded by some threshold
because even though the direction and the velocities of the
nodes may allow each other to catch up, the relative speed of