Nodes close to a fixed base station forward many other nodes' packets and can fail first.
Mobile Sink Path Planning in WSNs
Compare static, fixed-route, TSP-style, adaptive, and rendezvous collection strategies.
Mobile Sink Path Planning in WSNs
Move the collector through a sensor field and watch the trade-off shift: static sinks minimize delay but create relay hot spots, while mobile sinks reduce sensor forwarding energy at the cost of tour time, contact windows, and movement energy.
A mobile sink shortens sensor radio hops but each node waits until the next visit.
Being near a node is not enough if the radio link cannot drain its buffer before the sink leaves.
Adaptive routes may accept a small detour to collect urgent or nearly full buffers earlier.
Adaptive priority tour
The collector inserts high-risk buffers early, then resumes broad coverage.
Path diagnosis
Adaptive routing is the best fit because urgent data is active and buffer pressure matters more than a perfectly short tour.
Energy diagnosis
Mobile collection removes repeated multi-hop forwarding, so sensor energy is lower than the static hot-spot baseline.
Buffer diagnosis
Two sensors are close to the selected buffer limit. Increase dwell time, range, or buffer size if the route cannot visit sooner.
| Strategy | Route behavior | Best use | Main risk | Current fit |
|---|
Technical accuracy notes
- The TSP style route uses a nearest-neighbor teaching heuristic, not an exact Traveling Salesman optimum.
- Mobile sinks reduce sensor forwarding energy when nodes can upload directly or through short rendezvous relays, but they increase collection delay.
- Static sinks can be better in dense deployments where average path length is short and the hot-spot problem is weak.
- Delivery is limited by buffer capacity and by contact capacity: link rate multiplied by dwell time.
- Movement energy is shown separately from sensor energy because vehicle, robot, and UAV platforms have different power budgets.
Formula trace
route_distance_m = sum Euclidean segment distances
cycle_time_min = route_distance_m / sink_speed_mps / 60 + dwell_s * stops / 60
buffer_needed_kB = readings_per_min * payload_kB * wait_min
contact_capacity_kB = link_kbps * dwell_s / 8
delivery_ratio = min(buffer_capacity, contact_capacity) / buffer_needed
Guided checks
- Select Static sink in the sparse vineyard and compare the sensor energy index with Adaptive.
- Switch to Dense factory floor and observe why static collection becomes less harmful.
- Turn on Blocked corridor and compare TSP style with Adaptive priority.
- Lower the sensor buffer and increase reading rate until delivery begins to fall.
Common design trap
- Shortest route is not enough. If the route repeats too slowly, the last-visited sensors can overflow before the sink returns.
- Large radio range helps collection, but real deployments must budget for interference, contention, scheduling, and regulatory limits.
- UAV mobile sinks are not free. High movement power can erase the sensor energy gain unless the data deadline and route justify the flight.