It also provides
a lot of commands to manage metadata.
2. High Level Queries: TinyDB uses a SQL-like declarative query language
that allows users to describe the data they want, without requiring users
to say how to obtain it. This makes it easier for users to write applications,
and helps guarantee that the applications continue to run e?±ciently as the
sensor network changes.
3. Network Topology: TinyDB manages the underlying radio network by
tracking neighbors, maintaining routing tables, and ensuring that every
mote in the network can e?±ciently and (relatively) reliably deliver its data
to users.
4. Multiple Queries: TinyDB allows multiple queries to be run on the same
set of motes at the same time. Queries can have di?®erent sample rates and
access di?®erent sensor types, and TinyDB e?±ciently balances work among
queries when possible, which increases the speed and e?±ciency of query
processing.
5. Incremental Deployment: To expand a TinyDB sensor network, users
simply download the standard TinyDB code to new motes, and TinyDB
does the rest. No programming or configuration of the new motes is required
beyond installing TinyDB.
The Architecture of TinyDB
322
Chapter 12 Data Management in Sensor Networks
TinyDB consists of three major parts: Client, TinyDB Server and Sensor
networks (Figure 18). The client connects with a base station node via serial
port, and sensor nodes connect with each other via wireless networks.
Pages:
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518