24 Underwater Acoustic WSN Tracking

wireless-sensor-networks

target-tracking

underwater-sensing

24.1 A Clear First Route

Imagine a buoy waits for a slow sound pulse from a tag below rough water. The team must decide whether the late signal can support a safe location claim. Bandwidth means how much data a link can carry in a set time. A gateway is a device that links one network or system to another.

This page starts with one job. Name the target, the water path, and the clock. Then note sound travel time, drift, noise, motion, and contact with the surface. Look for known positions, clock checks, error bounds, data age, and custody. Last, choose publish a bounded fix, mark doubt, wait for more signs, or reject it. Keep the limit in view. Radio rules from land do not carry over to sound under water. Delay and drift must stay visible.

24.1.1 Follow One Decision

What real event starts the case?
Who needs the result?
What action may follow?
Which sign comes from the device?
How old can that sign be?
What can make it wrong?
What must still work after a fault?
Who owns the next check?
What change will force a new test?
What proof should the team keep?

A good record answers each point in plain words. It names the site and the people. It names the device and its state. It says when the event took place. It says when the result arrived. It marks doubt instead of hiding it. It also names the safe fallback. That makes the result useful without making it sound more sure than it is.

24.1.2 Know What This Route Leaves Out

This first route is a guide to the main choice. It does not model every field effect or rare fault. The Practitioner sections add sound paths, timing, location methods, buoy links, and field cases. Under the Hood adds error budgets, water models, sparse data, and recovery after lost contact. Those deeper parts add detail to this route. They do not reverse its main claim.

24.1.3 Read the Result Before You Act

Start with the source, not the final label. Check that the source belongs to this case. Check its time and state. Ask if a second source agrees. If two sources differ, keep that fact in the record. Do not force a clean answer just to fill a screen. A late result may be true about the past and still be unsafe now. A missing result is also useful news when the system shows it at once.

Next, link the result to one owned step. A person may inspect the site. A local rule may hold a safe state. A remote team may ask for more proof. The right step depends on the claim that was tested. It must not depend on a broad product label. Write down the reason for the step. Write down the time. Write down who may close the case.

24.2 Start With the Field Story

Underwater tracking starts with a difficult medium. Acoustic links are slow, variable, and energy-constrained, so every claim about localization, node drift, gateway contact, and data freshness needs stronger evidence than it would on land.

Underwater acoustic tracking is a specialized WSN vertical where the network cannot assume ordinary radio behavior, stable node placement, or immediate gateway contact. The review question is not whether acoustic networks are possible. It is whether a tracking claim remains explainable when observations are delayed, localization depends on environmental assumptions, and data may be collected through sparse buoys, mobile vehicles, or later uploads.

This chapter treats underwater tracking as an evidence review problem. It avoids universal range, speed, bandwidth, battery, and deployment-cost promises. Those values depend on water depth, salinity, temperature, sea state, hardware, mission profile, and operations constraints. A learner should instead ask which assumptions were measured, which were inferred, and how stale or uncertain evidence is labeled.

24.3 In 60 Seconds

Underwater WSN tracking usually relies on acoustic, optical, tethered, physical-collection, or hybrid paths rather than ordinary radio links. Acoustic evidence needs timing, sound-speed, multipath, Doppler, depth, clock, and path-quality context before it can support a track. Node position is part of the evidence. Anchors, buoys, AUVs, drifting sensors, and moored sensors can all move or become uncertain. Gateway custody matters because an underwater observation may be summarized by a buoy, carried by a vehicle, or uploaded after the tracked state has changed. Release readiness requires visible labels for current, delayed, ambiguous, degraded, historical, experimental, and retired tracking records.

Phoebe’s Field Notes: Why This Chapter Cannot Reuse the Radio Path-Loss Formula

The mathematical gist. For a catalog-typical 12 kHz acoustic link over 2.00 km, seawater absorption is 1.64 dB/km and total transmission loss is 69.3 dB. Sound needs 1.33 s to cross that distance; radio needs 6.67 µs. With illustrative source and noise levels, the acoustic link has 60.7 dB SNR and 50.7 dB detection margin. Lower frequency reduces absorption, but it does not remove delay or field uncertainty.

24.4 Learning Objectives

By the end of this chapter, you will be able to:

Review underwater acoustic WSN tracking claims without turning channel assumptions into proof.
Identify the evidence needed for acoustic path, localization, timing, drift, and gateway custody.
Separate local detections, acoustic ranges, track estimates, and operations labels.
Evaluate underwater worked scenarios for stale evidence, ambiguous localization, degraded gateways, and fallback behavior.
Build a release gate checklist for underwater tracking chapters, labs, and prototypes.

24.5 Underwater Acoustic WSN Tracking

24.6 Underwater Tracking Claim

Start with a claim that can be tested in the stated water environment:

Underwater tracking claim: The system can detect and report a specified underwater target, asset, node, or environmental state for a stated decision while preserving acoustic path evidence, localization uncertainty, observation time, gateway custody, stale-state labels, and operating limits.

That claim is intentionally narrower than “the network tracks everything underwater.” A hydrophone event, acoustic range, AUV contact, or buoy upload can be useful, but it becomes a tracking record only when the evidence path and its limits are visible.

Tracked object Is the record about a moving target, an underwater node, an AUV, a moored asset, a drifting marker, or an environmental event?

Observation boundary Was the evidence directly sensed, inferred from acoustic range, reconstructed from multiple nodes, or summarized by a gateway?

Decision boundary What decision does the record support, and what label appears when acoustic evidence is delayed, noisy, or environment-limited?

24.7 Underwater Evidence Map

The practical question in underwater evidence map is where observation hands responsibility to event or range. Use Figure 24.1 to inspect that hand-off before carrying the design forward.

Underwater acoustic tracking evidence map showing local observation, acoustic path, localization review, gateway custody, WSN tracking record, and operations label with timing, drift, sound-speed, fallback, and retest evidence. — Figure 24.1: Underwater acoustic tracking evidence map.

The visual path in Figure 24.1 moves from observation (identifies the field observation) through event or range (adds a distinct review condition) to clock and depth (adds a distinct review condition). Reading those labels as one chain clarifies that underwater acoustic tracking evidence map showing local observation, acoustic path, localization review, gateway custody, WSN tracking record, and operations label with timing, drift, sound-speed, fallback, and retest evidence. It therefore connects this diagram directly to the chapter’s treatment of underwater evidence map.

The map separates observation, acoustic path, localization, gateway custody, and operations label. A tracking dashboard that only shows a final point can hide the assumptions that make that point useful or unsafe.

Local observation Records hydrophone event, pressure or depth state, node id, clock source, sensor calibration, and local quality flags.

Acoustic path Records range method, sound-speed assumption, multipath risk, Doppler or motion effect, packet loss, and channel quality.

Localization review Records anchor geometry, node drift, AUV or buoy position source, uncertainty, and whether the estimate is current or historical.

Gateway custody Records whether evidence was relayed live, buffered underwater, carried by a vehicle, summarized by a buoy, or uploaded later.

24.8 Acoustic Path Review

Underwater tracking often starts with acoustic communication or acoustic ranging. A review should focus on what the acoustic path preserves and what it can distort.

Timing evidence Does the record preserve observation time, send time, receive time, clock source, and whether propagation or queueing delay changed the claim?

Environment evidence Does the system record water conditions that can affect acoustic behavior, such as depth profile, sound-speed estimate, sea state, bottom reflection, or thermocline?

Motion evidence Does the record account for target motion, node drift, AUV path, buoy movement, and Doppler-sensitive measurements?

Path quality evidence Are missed packets, multipath, weak signal, ambiguous arrival times, and one-way versus two-way ranging assumptions visible?

No acoustic path is automatically release-ready. The path is reviewable only when its timing and environmental assumptions are shown with the track.

24.9 Timing and Freshness

Underwater evidence can be valuable even when it is not live. The problem is presenting old evidence as current.

Observation time When was the event, range, or detection observed, and did the local clock remain trustworthy?

Acoustic delay How did propagation, retries, queueing, and channel access affect the age of the evidence?

Collection delay Was evidence sent to a buoy, stored until surfacing, carried by an AUV, or uploaded after the mission?

Decision time Does the dashboard label the record as current, delayed, historical, ambiguous, degraded, or needing confirmation?

The review should reject any design that updates a live track with delayed underwater evidence without showing freshness and uncertainty.

24.10 Localization and Drift

Underwater tracking depends on knowing both the target evidence and the observing node positions. Node position may be a measured state, a model output, or an assumption.

Anchor evidence Surface buoys, moored anchors, seabed references, and AUV fixes need position source, age, and uncertainty labels.

Node mobility Currents, moorings, vehicle movement, drag, cable stretch, and deployment drift can move sensors or change their geometry.

Geometry quality Localization should expose poor anchor geometry, weak range diversity, depth ambiguity, and conditions that create multiple plausible positions.

Retest trigger Storms, maintenance, anchor movement, firmware changes, new sound-speed profiles, or gateway changes should trigger localization review.

If the observing node location is uncertain, the target track should inherit that uncertainty instead of hiding it.

24.11 Localization Pattern Examples

Underwater localization schemes often appear under names such as 3-D anchor localization, AUV-assisted silent localization, HASL-style high-speed AUV localization, opportunistic localization, or self-organizing virtual architectures. Treat those names as examples of evidence patterns, not as release approval.

Ocean model Internal waves, solitons, currents, depth layers, and salinity or temperature profiles can change acoustic paths and node mobility.

Anchor economy Schemes that reduce the number of anchors must show what replaces the missing geometry: mobility prediction, repeated passes, pressure-derived depth, or delayed confirmation.

AUV custody An AUV or mobile sink may collect beacons silently, estimate position later, or upload after surfacing. The record should separate observation time from upload time.

Virtual topology A self-organizing virtual layer can help coordinate nodes, but the review should preserve formation rule, duration, broken-layer behavior, and retest trigger.

The practical review question is whether the localization record still explains its uncertainty after the water state, anchor state, vehicle path, or virtual topology changes.

24.11.1 Internal Solitons and Three-Dimensional Motion

An internal soliton is a nonlinear wave travelling along a density interface inside the water column. Its steep temperature and salinity gradient changes sound speed and can refract, focus, defocus, or scatter an acoustic path. The effect is not equivalent to adding a constant range error: a link can change as the soliton crosses the path even when transmitter and receiver have not moved. Localization records should therefore bind ranges to a sound-speed profile and observation time, and should widen uncertainty or reject a range when the profile is stale.

Node motion must also be modelled in three dimensions. A useful oceanic-forces model updates position $\mathbf{x}$ and velocity $\mathbf{v}$ from the dominant current, buoyancy, drag, wave, and tether forces:

m\frac{d\mathbf{v}}{dt}=\mathbf{F}_{\text{current}}+\mathbf{F}_{\text{buoyancy}}+\mathbf{F}_{\text{drag}}+\mathbf{F}_{\text{wave}}+\mathbf{F}_{\text{tether}}, \qquad \frac{d\mathbf{x}}{dt}=\mathbf{v}.

The point is not that every node needs a full fluid-dynamics solver. The point is that a shallow-water random walk cannot stand in for vertical drift, depth-dependent currents, or a mooring constraint. The chosen model should expose the force terms it omits and be checked against position or current observations.

24.11.2 Three-Anchor Iterative Silent Localization

Three surface anchors can provide horizontal geometry while a pressure sensor supplies depth. Let unknown node position be $\mathbf{x}=(x,y,z)$ , anchor $i$ be $\mathbf{a}_i=(x_i,y_i,z_i)$ , and corrected acoustic range be $r_i$ . The range equations are

\|\mathbf{x}-\mathbf{a}_i\|^2=r_i^2, \qquad i\in\{1,2,3\}.

Pressure fixes or tightly constrains $z$ , reducing the unknown horizontal coordinates to $x$ and $y$ . Subtracting the first squared-range equation from the other two cancels $x^2+y^2$ and produces two linear equations. Solve that initial estimate, predict anchor and node positions to the common observation time, recompute sound-speed-corrected ranges, and iterate until the position update or residual stops improving. Three anchors are enough only when geometry is not nearly collinear and the depth and timing errors are bounded.

24.11.3 HASL Cycle: AUV-Assisted Without Node Transmissions

High-speed AUV-based silent localization moves the active cost to the vehicle. Follow the cycle from the vehicle’s navigation evidence: the AUV first obtains a surface GPS fix, then tracks its submerged path with dead reckoning or inertial/navigation sensors. At constant intervals it broadcasts a beacon containing vehicle position and transmit time. Silent sensor nodes collect several of those beacons without answering, which avoids acoustic contention and reveals less about their presence.

The sensor then turns arrival timing into range-like constraints and uses its pressure-derived depth as the vertical coordinate. Once it has observations from enough geometrically diverse AUV positions, it solves its position by trilateration or nonlinear least squares. The result is not just a coordinate: the node retains residuals, AUV position age, the sound-speed assumption, and geometry quality alongside the estimate so a reviewer can judge whether the route supplied enough evidence.

“Silent” means the node does not transmit during localization; it does not mean the estimate is evidence-free. A constant beacon interval helps associate observations and predict vehicle position, but clock offset, AUV dead-reckoning drift, sound-speed variation, and a nearly straight pass can still dominate the solution.

24.11.4 Opportunistic Localization Policy

Opportunistic localization gives the two node states different objectives. An unlocalized node chooses which localized neighbors or beacon opportunities will minimize expected time to obtain sufficient geometry:

j^*=\arg\min_j\left(t_{\text{wait},j}+t_{\text{exchange},j}+t_{\text{solve},j}\right).

A localized node chooses transmit power $P_k$ to maximize localization benefit per joule, not raw reach:

P^*=\arg\max_{P_k}\frac{\mathbb{E}[\text{newly localized peers}\mid P_k]}{E_{\text{tx}}(P_k)}.

At each opportunity the node discovers state, scores candidates, selects a power or neighbor, emits or listens once, updates which peers became localized, and backs off when marginal benefit falls. The algorithm needs limits for repeated failures and for overlapping helpers that would spend energy localizing the same peer.

24.11.5 Tic-Tac-Toe Virtual Architecture

A moving underwater network should not treat a momentary neighbor graph as permanent. For nodes $i$ and $j$ with relative position $\mathbf{r}_{ij}$ , relative velocity $\mathbf{v}_{ij}$ , and usable acoustic radius $R$ , a constant-velocity connectivity duration is the positive root of

\|\mathbf{r}_{ij}+t\mathbf{v}_{ij}\|^2=R^2.

Expanding gives a quadratic in $t$ ; the first future boundary crossing estimates how long the pair can remain connected. The Tic-tac-toe pattern uses these predicted durations to form a layered virtual topology: relatively stable nodes become higher-layer coordinators or junctions, shorter-lived neighbors attach below them, and the layers are rebuilt as predicted lifetimes or measured links expire.

Formation proceeds by exchanging motion and link state, predicting pair lifetimes, selecting stable parents, checking that the layered structure reaches a gateway or collection point, and scheduling repair before the weakest required edge expires. The record should retain the prediction horizon, parent lifetime, layer changes, broken-edge behavior, and actual-versus-predicted contact duration. Otherwise “self-organizing” hides topology churn instead of managing it.

24.12 Gateway Custody Review

The underwater gateway path may be live, intermittent, mobile, or delayed. The custody record should explain what happened to the evidence after it was observed.

Gateway input: Observation id, node id, timing source, acoustic path quality, localization state, and buffer state.

Translation rule: Range conversion, track association, aggregation window, discarded evidence, and uncertainty conversion.

Output record: Track id or event id, lifecycle label, freshness, confidence, custody, environment limits, and operator-facing warning.

Fallback state: Request confirmation, mark delayed, widen the search area, hold the decision, schedule a collection pass, or retire the track.

Gateway custody is incomplete if it only says “target detected.” It must also show when evidence was observed, how it moved, what was summarized, and where the claim stops.

24.13 Error Budget and State Labels

The underwater error budget belongs inside the tracking record, not in background notes. A point estimate is a claim about observation time, acoustic path quality, sound-speed assumptions, observing-node position, and gateway custody. If any field is stale or weak, the operations label should inherit that weakness.

Evidence condition	Record label	Review action
Detection exists, but acoustic path quality is not reviewed	acoustic-unverified	Hold precise location and show only bounded event evidence
Sound-speed profile, noise, or multipath evidence is stale	environment-limited	Widen uncertainty and require a profile or path-quality refresh
Anchor, buoy, or AUV position age controls the estimate	geometry-limited	Expose anchor age, drift source, and range diversity before release
Evidence is buffered or carried before upload	historical or delayed	Keep observation time separate from upload and decision time
Several plausible locations or classes remain	ambiguous	Request confirmation, collect more ranges, or widen the search area

The record should also keep a time-stamped ledger: observation time, send or receive time, upload time, sound-speed profile id or age, path-quality state, anchor or vehicle position age, uncertainty state, custody path, discarded-evidence note, and label-transition owner. That ledger prevents a late high-quality packet, a fresh low-quality buoy relay, or an anchor-position update from silently overwriting the supported label.

24.14 Knowledge Check: Error Ledger

24.15 Release Gates

Evidence for Release Gates starts in Figure 24.2. Look at 1. Claim beside decision stated before accepting Release gates for underwater acoustic WSN tracking.

Release gate route for underwater acoustic WSN tracking showing claim fit, target definition, acoustic evidence, localization evidence, gateway custody, operations label, fallback action, monitoring, and retest trigger. — Figure 24.2: Release gates for underwater acoustic WSN tracking.

Three labels control the Figure 24.2 visual: 1. Claim names a responsibility; decision stated states the supported result; and bounded names a responsibility. The link between 1. Claim and and bounded supplies the meaning of Release gates for underwater acoustic WSN tracking. That makes decision stated a checkable part of Release Gates.

Release gates should test the full route from underwater observation to system-level decision.

Claim fit The tracked object, water environment, acoustic path, localization method, gateway path, and supported decision are stated narrowly.

Evidence preservation Timing, path quality, drift, localization uncertainty, custody, stale labels, and discarded evidence survive gateway handoff.

Stress scenes Multipath, weak signal, current drift, anchor movement, delayed vehicle upload, and gateway loss are tested.

Operations label Users can distinguish current, delayed, ambiguous, degraded, historical, experimental, and retired records.

Fallback action The system requests confirmation, widens search, schedules collection, holds decision, marks degraded, or retires the track.

Retest trigger Water profile, anchor position, mooring state, gateway firmware, mission route, or dashboard-schema changes trigger review.

24.16 Mooring Field Asset Tracking

A mooring field uses acoustic pings from fixed sensors to report the position of an underwater asset moving near several anchors.

Evidence that supports release The record shows anchor position age, acoustic path quality, range diversity, observation time, track association rule, and a degraded label when geometry is weak.

Evidence that blocks release The dashboard shows a precise current point even though one anchor drifted, path quality is poor, and the estimate uses an old sound-speed assumption.

Review decision Revise before release. Add anchor uncertainty, environment profile age, ambiguous-position labels, and fallback search-area behavior.

24.17 Worked Review: AUV Data Collection

An AUV collects buffered detections from underwater nodes and uploads them after surfacing.

Evidence that supports release The system marks uploaded records as historical or delayed, preserves node buffer custody, AUV route, collection time, and gateway upload time.

Evidence that blocks release The platform refreshes the live track map when the AUV uploads old buffered observations without showing collection delay or track age.

Review decision Hold release. Separate live state from historical detections, and expose collection custody before using the records for operational tracking.

24.18 Worked Review: Coastal Event Detection

A coastal sensor line reports acoustic events that may indicate vessel activity, equipment movement, or environmental noise.

Evidence that supports release The record separates detection from classification, preserves background-noise state, path quality, confidence, and confirmation status.

Evidence that blocks release The system labels every acoustic event as a confirmed target track even when multipath, weather, or non-target noise can explain the signal.

Review decision Use ambiguous and confirmation-required labels. Keep classification claims separate from location claims until supporting evidence is visible.

24.19 Common Underwater Tracking Mistakes

Channel assumption becomes proof The design assumes one acoustic delay, range, or bandwidth value and does not show measured environment evidence.

Node position is treated as fixed Sensors, buoys, or anchors move, but the tracking record does not carry position age or uncertainty.

Delayed upload becomes live state Buffered evidence from an AUV or buoy updates a current map without historical or delayed labels.

Multipath is hidden Reflections, ambiguous arrivals, or poor geometry are converted into a clean location without a quality warning.

Gateway loses custody The gateway drops buffer state, route, upload time, discarded evidence, or association rule.

Fallback is not defined The system does not say what to do when a gateway disappears, a node drifts, or an acoustic path becomes unreliable.

24.20 Readiness Checklist

Before approving an underwater acoustic tracking chapter, lab, or prototype review, verify these items.

Claim Is the tracked object or event defined, and is the supported decision stated without universal underwater performance promises?

Acoustic evidence Are timing, clock source, sound-speed assumption, path quality, multipath risk, and packet loss preserved?

Localization evidence Are anchor position, node drift, geometry quality, depth, uncertainty, and estimate age visible?

Gateway custody Are buffering, carried collection, buoy relay, upload time, discarded evidence, and translation rules documented?

Operations labels Can users distinguish current, delayed, ambiguous, degraded, historical, experimental, and retired records?

Release record Are fallback action, owner, monitoring signal, accepted limit, retest trigger, and environment assumptions written down?

24.21 Knowledge Check: Acoustic Evidence

24.22 Knowledge Check: Gateway Custody

24.23 Match Underwater Evidence

24.24 Order Underwater Evidence

24.25 Figure Review: Localization Under Motion

A silent node can localize without transmitting when the moving AUV leaves a sufficiently diverse, time-aligned trail of position evidence.

An AUV takes a surface fix and sends timed position beacons. A silent node listens, adds depth, solves horizontal position and labels uncertainty before contract acceptance. — Figure 24.3: AUV-assisted silent localization cycle.

In Figure 24.3, GPS FIX anchors the AUV trajectory before PASSIVE BEACON SET and TRILATERATE turn time-position pairs into a node estimate; UNCERTAINTY RECORD keeps motion and acoustic-path error attached to the result.

When several assets are already moving through the water column, localization can be opportunistic rather than organized around a dedicated anchor pass.

An unlocalized node chooses A for minimum time-to-fix; a localized node chooses P2 for more new fixes per joule. The two policies have different objectives. — Figure 24.4: Opportunistic underwater localization evidence.

The OBSERVATION POOL in Figure 24.4 is deliberately broader than the ACCEPTED SET: the geometry gate and sound-speed gate reject convenient but misleading observations before the position solve.

Long-lived underwater forwarding also needs a topology that can reform as predicted contact duration changes.

Temporary underwater layers forward toward surface sinks while predicted links outlast a 12 s custody interval. Failing 7 s and 5 s links trigger layer reassignment to a 14 s path. — Figure 24.5: Virtual underwater layers governed by custody time.

In Figure 24.5, VIRTUAL LAYER 1 offers a 28-to-22-to-18-second route that passes the CUSTODY TEST, whereas the dashed 7-to-5-second branch triggers REFORM and reassignment to the 14-second path.

24.26 Summary

Underwater acoustic tracking is a WSN vertical where acoustic path evidence, localization uncertainty, gateway custody, and operations labels are central to the tracking claim. A hydrophone event, acoustic range, or delayed AUV upload is not automatically a current track. It becomes useful only when timing, path quality, drift, localization state, custody, and uncertainty survive into the system-level record.

The right review posture is conservative. Treat underwater tracking concepts as bounded evidence systems. Preserve what was observed, how it moved through the acoustic and gateway path, how it was localized, what decision it supports, and where the claim stops.

24.27 Key Takeaway

Underwater Acoustic WSN Tracking Review should adapt tracking assumptions to the vertical’s sensing physics, communication limits, localization uncertainty, energy budget, and deployment evidence.

24.28 Concept Relationships

Tracking fundamentals WSN Tracking: Fundamentals provides the vocabulary behind observations, estimates, uncertainty, and evidence records.

Multimedia tracking Wireless Multimedia WSN Tracking reviews a neighboring vertical where custody, delay, and bounded evidence also shape the claim.

Energy prediction WSN Tracking: Energy Prediction Review explains why observation age, wake decisions, and evidence freshness must stay visible.

Production framework WSN Tracking Implementation Framework Review defines release records, validation gates, and retest triggers reused here.

24.29 What’s Next

Nanoscale tracking Nanoscale WSN Tracking Review reviews another special environment where scale, communication path, and gateway evidence dominate the claim.

Implementation framework WSN Tracking Implementation Framework Review turns vertical evidence into production gates, component contracts, and lifecycle labels.