Target tracking in WSNs activates only sensors near a moving target, keeping 80-95% of nodes asleep to extend network lifetime from weeks to years. Prediction-based tracking (Kalman filters) achieves 1-2 meter accuracy for linear motion at 100 mW per node, while cluster-based approaches reduce tracking messages by 70% by confining communication to local clusters that hand off as targets cross boundaries.
32.1 Learning Objectives
By the end of this chapter series, you will be able to:
Explain Tracking Fundamentals: Describe the principles of object tracking in wireless sensor networks
Differentiate Tracking Approaches: Contrast prediction-based, cluster-based, and tree-based tracking mechanisms
Implement Tracking Algorithms: Build basic tracking algorithms for mobile targets
Evaluate Energy Trade-offs: Quantify energy consumption vs tracking accuracy trade-offs in deployment scenarios
Diagnose Tracking Challenges: Troubleshoot challenges like target handoff, occlusion, and multiple targets
MVU: Minimum Viable Understanding
Core concept: WSN tracking uses prediction-based algorithms to continuously monitor moving targets by selectively activating only the sensors along the predicted path. Why it matters: Keeping all sensors active for tracking drains batteries in days; selective activation achieves 85-95% energy savings while maintaining accuracy. Key takeaway: Predict where the target will be, wake only nearby sensors, and handle handoffs smoothly to avoid losing the target during sensor transitions.
The Challenge: Tracking Moving Targets with Fixed Sensors
The Problem: Mobile tracking is fundamentally harder than static monitoring because the target moves unpredictably through a network of fixed sensors:
Target mobility: Object moves between sensor detection ranges continuously
Sensor uncertainty: Cannot predict which sensors will detect the target next
Energy waste: Keeping all sensors active drains batteries in days, not months
Handoff risk: Losing the target during sensor-to-sensor transitions
The Solution: This chapter series introduces prediction-based tracking with selective sensor activation — algorithms that use motion models (Kalman filters) to forecast target position, wake only relevant sensors, and achieve 85-95% energy savings while maintaining tracking accuracy.
32.2 Chapter Series Overview
This topic has been organized into focused chapters for easier learning:
Think of WSN tracking like a relay race of security guards watching a moving target.
Imagine you have 100 security guards scattered across a large park, and a VIP is walking through. You don’t need all guards watching at once—just the ones near the VIP. As the VIP moves, guards “hand off” responsibility to the next guards in the path.
Three ways to track:
Push-based - Sensors constantly report “I see something!” (proactive)
Poll-based - Base station asks “Anyone see anything?” (reactive)
Guided - “Target was at A, so check sensors near B next” (smart)
Key insight: The challenge isn’t just “find the target”—it’s “find the target efficiently without draining everyone’s batteries.”
Video: WSN Tracking Demo
Video: WSN Target Tracking Example
Sensor Squad: Why Tracking is Like a Relay Race
Imagine a relay race at school, but instead of passing a baton, the Sensor Squad passes “tracking responsibility!”
Sammy the Sensor stood at one end of the park. “I can see the puppy running this way!” As the puppy ran past, Sammy called out to the next sensor: “It’s heading your way at 3 meters per second, going northeast!”
The next sensor, already awake thanks to Max the Microcontroller’s PREDICTION, picked up tracking seamlessly. “Got it! I see the puppy now! Next sensor, wake up – it’ll reach you in 5 seconds!”
“This is called a HANDOFF,” explained Max. “Each sensor only watches when the puppy is nearby, then passes the job to the next one.”
Bella the Battery was thrilled: “Instead of all 100 sensors watching all day, only 3-4 are awake at any time! My energy lasts MONTHS instead of days!”
Lila the LED asked: “But what if the puppy changes direction suddenly?”
Max smiled: “That’s our RECOVERY plan! We do an expanding ring search – wake sensors in growing circles from where we last saw the puppy. We almost always find it within seconds!”
The Three Big Ideas:
Push = sensors shout “I see it!” immediately (fast but tiring)
Poll = base station asks “Anyone see it?” when needed (slow but energy-saving)
Guided = sensors direct a drone to catch it (needs a mobile tracker)
Putting Numbers to It
The 80-95% sleep fraction extends lifetime dramatically. With 100 sensors at 50 mW active, 0.1 mW sleep:
Lifetime ratio: \(28.5 / 1.48 = 19.3\times\) longer! With solar recharge (100 mW/day), selective lasts indefinitely while always-on dies in hours.
32.4 Motivating Case Studies
These real-world scenarios illustrate why tracking system design choices matter enormously for both cost and reliability.
32.5 Worked Example: Cost of Tracking 50 Forklifts in a Warehouse
A logistics company needs to track 50 forklifts in a 20,000 m2 warehouse. They are comparing three approaches: UWB high-precision, BLE zone-level, and camera-based. The comparison reveals how tracking requirements drive architecture and cost.
Requirement Profile
Requirement
Value
Why It Matters
Accuracy needed
2-3 m (aisle-level, not centimeter)
Knowing which aisle a forklift is in suffices for dispatching
Update rate
Every 5 seconds
Forklifts move at 8 km/h max; 5s updates track position to within 11 m
Number of targets
50 concurrent
All forklifts operating during peak shift
Infrastructure budget
$50,000 one-time
Mid-range industrial deployment
Operating cost target
<$500/month ongoing
Excludes labor for manual tracking
Option Comparison
Factor
UWB (Decawave)
BLE (iBeacon)
Camera + CV
Anchors/cameras needed
80 anchors (1 per 250 m2)
40 beacons (1 per 500 m2)
30 cameras (1 per 670 m2)
Per-anchor/camera cost
$120
$25
$350
Infrastructure cost
$9,600
$1,000
$10,500
Tag/device per forklift
$45 (UWB tag)
$8 (BLE tag)
$0 (camera-based)
Tag cost (50 units)
$2,250
$400
$0
Server/gateway
$3,000 (UWB location engine)
$1,500 (BLE gateway + software)
$8,000 (GPU server for CV)
Installation labor
$5,000
$2,000
$6,000
Total one-time cost
$19,850
$4,900
$24,500
Accuracy achieved
10-30 cm
2-5 m
1-2 m
Monthly operating cost
$100 (cloud license)
$50 (battery replacement 10%/mo)
$200 (GPU electricity + cloud)
Battery life per tag
2 years
6-12 months
N/A
Decision: BLE at $4,900 meets the 2-3 m accuracy requirement at 1/4 the cost of UWB and 1/5 the cost of cameras. UWB’s 10-30 cm precision is wasted when aisle-level tracking suffices. Camera-based tracking avoids tags entirely but requires expensive GPU processing and fails in dusty/obstructed warehouse aisles.
Key Lesson: Over-specifying accuracy is the most expensive mistake in tracking system design. Each order of magnitude improvement in precision roughly doubles infrastructure cost. Always start from the business question (“which aisle is the forklift in?”) rather than the technology specification (“we need centimeter accuracy”).
32.6 Worked Example: When Tracking Fails – Hospital Asset Loss Analysis
A 600-bed hospital deployed RFID + BLE tracking for 2,400 mobile assets (infusion pumps, wheelchairs, ventilators, defibrillators). Despite 99.2% detection rate (any tagged asset near any reader triggers a detection), tracking continuity averaged only 73% – meaning 27% of the time, the system could not tell staff which floor an asset was on.
Why 99.2% Detection but Only 73% Tracking?
Failure Mode
Frequency
Assets Lost
Why Detection Succeeded but Tracking Failed
Elevator transit
340 events/day
15-45 sec each
Elevator shaft blocks BLE. Asset “disappears” from floor 3 and “appears” on floor 7 with no path – system cannot distinguish from a stolen asset
Metal cart shielding
Constant (180 carts)
420 assets at any time
Carts with metal sides attenuate BLE signal. Reader detects asset intermittently at 1-2 m but not reliably at 5 m, causing repeated lost-found-lost oscillations
Crowded hallways
Peak hours (7-9 AM, 3-5 PM)
200+ assets simultaneously
Body absorption reduces BLE range by 40%. During shift change, hallway readers are overwhelmed by 50+ concurrent tags, causing MAC-layer collisions
Cross-floor bleed
Constant
~60 false assignments
BLE signals penetrate thin floors. A pump on floor 4 is occasionally detected by a reader on floor 5, causing “teleportation” in the tracking log
The Fix: Layered Tracking Architecture
The hospital upgraded from pure-BLE to a three-tier system:
Tier
Technology
Purpose
Coverage
Coarse (building-level)
LoRaWAN (1 gateway per building)
Confirm asset is in hospital vs. removed
100% – penetrates all walls
Medium (floor-level)
BLE zone detection (readers at stairwells + elevators)
Determine which floor
94% – fails only during extended elevator rides
Fine (room-level)
UWB anchors in high-value zones only (OR, ICU, pharmacy)
Locate within 50 cm
99.5% in covered zones (15% of hospital area)
The three-tier approach cost $85,000 more than BLE-only ($210,000 vs $125,000) but raised tracking continuity from 73% to 96%. The remaining 4% gap (elevator transit) was addressed with a software prediction model: if an asset disappears from floor 3’s elevator lobby, it will reappear at another floor’s elevator lobby within 120 seconds – no alarm needed.
Annual ROI: The hospital previously lost $380,000/year replacing “missing” assets that were actually in the building but untraceable. At 96% tracking, losses dropped to $52,000/year. Payback on the $85,000 upgrade: 3.1 months.
32.7 Quick Reference: Key Concepts
Concept
Definition
Object Tracking
Continuous monitoring of target locations as they move through WSN coverage
Localization
Determining physical position using trilateration, multilateration, or proximity
Prediction Models
Algorithms forecasting future positions based on movement patterns
Energy-Efficient Tracking
Selective sensor activation to minimize power consumption
Handoff Protocols
Mechanisms for transferring tracking responsibility between sensors
Tracking Accuracy
Measure of how closely estimated positions match actual positions
32.8 Selective Activation Lifetime Calculator
Explore how the sleep fraction transforms sensor network lifetime. Adjust the sliders to see why keeping 95% of nodes asleep can extend battery life by 10-20×.
Show code
viewof fund_n_sensors = Inputs.range([10,500], {value:100,step:10,label:"Total sensors in network"})viewof fund_active_mw = Inputs.range([10,200], {value:50,step:5,label:"Active power per sensor (mW)"})viewof fund_sleep_mw = Inputs.range([0.01,5], {value:0.1,step:0.01,label:"Sleep power per sensor (mW)"})viewof fund_sleep_pct = Inputs.range([50,99], {value:95,step:1,label:"Sleep fraction (% nodes sleeping)"})viewof fund_battery_mah = Inputs.range([500,20000], {value:2000,step:500,label:"Battery capacity (mAh)"})viewof fund_battery_v = Inputs.range([1.5,7.4], {value:3.7,step:0.1,label:"Battery voltage (V)"})
1. Prioritizing Theory Over Measurement in WSN Tracking: Fundamentals
Relying on theoretical models without profiling actual behavior leads to designs that miss performance targets by 2-10×. Always measure the dominant bottleneck in your specific deployment environment — hardware variability, interference, and load patterns routinely differ from textbook assumptions.
2. Ignoring System-Level Trade-offs
Optimizing one parameter in isolation (latency, throughput, energy) without considering impact on others creates systems that excel on benchmarks but fail in production. Document the top three trade-offs before finalizing any design decision and verify with realistic workloads.
3. Skipping Failure Mode Analysis
Most field failures come from edge cases that work in the lab: intermittent connectivity, partial node failure, clock drift, and buffer overflow under peak load. Explicitly design and test failure handling before deployment — retrofitting error recovery after deployment costs 5-10× more than building it in.
🏷️ Label the Diagram
Code Challenge
32.9 Summary
This chapter introduced the fundamentals of WSN target tracking:
The Tracking Challenge: Mobile targets move unpredictably through fixed sensor networks, requiring prediction-based selective activation to avoid draining batteries in days.
Three Formulations: Push-based (proactive, real-time, higher energy), poll-based (on-demand, energy-efficient, higher latency), and guided (active interception with mobile trackers).
Key Concepts: Object tracking, localization, prediction models, energy-efficient activation, handoff protocols, and tracking accuracy are the building blocks for all WSN tracking systems.
Chapter Series Structure: This fundamentals overview leads into detailed chapters on problem formulations, algorithm components, energy-efficient prediction, and interactive demos.
Test Your Understanding
Question 1: What is the fundamental challenge that makes WSN tracking harder than static environmental monitoring?
Tracking requires more expensive sensors
The target moves unpredictably, requiring continuous prediction, sensor handoffs, and selective activation to avoid wasting energy
Tracking systems cannot use wireless communication
Static monitoring is always less accurate than tracking
Answer
b) The target moves unpredictably. Static monitoring measures fixed phenomena (temperature, humidity) at known locations. Tracking requires continuously estimating where a moving target IS and WHERE it will be next, coordinating sensor handoffs as the target crosses coverage zones, and selectively activating sensors along predicted paths. Without prediction, keeping all sensors active would drain batteries in days.
Question 2: A factory manager wants to track 20 forklifts in a 10,000 square meter warehouse. Battery life is the top priority. Which tracking formulation should they choose?
Push-based – for real-time forklift positions
Poll-based – query only when a specific forklift’s position is needed
Guided – use a drone to follow each forklift
All three simultaneously for maximum coverage
Answer
b) Poll-based tracking. Since battery life is the top priority and the manager only needs forklift positions occasionally (e.g., when dispatching a task or locating a specific forklift), poll-based tracking keeps sensors sleeping most of the time. The query latency of a few seconds is acceptable for warehouse logistics. Push-based would waste energy sending continuous updates that nobody reads.