1. Smart Sensor Node Impact  GPS leveraged for geo-referenced identity, and low power communications synchronization. Up to 100x communications power reduction.  Standard APIs implemented as Java class libraries and browser-based user interfaces provide code mobility, code reuse, and platform independence.  High-level spatial and context “anycast” addressing enables dynamic specialization for augmented awareness and collaborative consensus applications. New Ideas  Power-aware link and routing protocols. Exploit fine- grained power control of radios for energy efficient connectivity. Maximize sensor network’s operational lifetime through energy-aware routing.  GPS-aware link protocols. GPS-synchronized ultra-low-power communication.  Spatial addressing and connectivity. High-level addressing, unicast, multicast, anycast, and gathercast communication based on spatial referencing of the nodes.  Mobile code and web technology. Embedded Java APIs for code portability and browser-based topographical map interface for visualizing dynamic data from sensor net. Milestones Sensor Control API SpecificationFY00 Q1 Topographical Map Interface Definition FY00 Q1 Network Services API SpecificationFY00 Q2 GPS-Aware Link Protocol ExperimentFY01 Q4 Network Services PDA/Laptop ExperimentFY01 Q4 Integrated Sensor-Kit ExperimentFY02 Q4 Smart Sensor Node Event Target COTS PDA Brian Schott PI, Bob Parker (USC/ISI), Mani Srivastava (UCLA) Co-PI, Mark Jones (Virginia Tech) Co-PI Dynamic Sensor Networks

2. Approach to GUI Front-End One aspect of the DSN project is the design and implementation of a map-based GUI front-end for the sensor network This GUI front-end should support –multiple query languages formulated under SenseIT –multiple sensor platforms developed under SenseIT –multiple local applications that perform specialized processing on sensor results (e.g., may want to do image processing on an image taken off the sensor net) –execution on a variety of operating systems and platforms including PDAs, laptops, PCs, and workstations

3. Progress on Map-Based GUI Design The GUI accepts user queries and presents results in a map-based context –satellite imagery –topographical maps Formulates queries in the query language(s) expected by the query manager Allows multiple local plug- in applications to send queries and use XML to display results on the GUI Prototype available for demonstration

4. Expected User Queries “Are there any X’s in area Y right now?” (One-time) –X could be a single thing (a T-72), a collection (tracked vehicles), or simply anything anomalous (GUI will allow for combinations) –The GUI doesn’t know what an X is, but it does know how to express that in the query language and which local application to interface with for X’s; if X was poison gas, then the correct local application would be told and it would give the GUI the correct display (different than we’d expect for T-72 query) –The GUI will let the user specify the area Y on the map/photo using a pen or mouse or Y could be “where I am now” “Let me know if/when you see any X’s in Y?” (Persistent) –X is the same as above, Y could be “where I am” but moving –The GUI does know that the query is persistent, but it is the job of the query manager to handle this persistence; need to eventually work out how to express the change in Y to the query manager

5. Short Term Issues Browsers: We have evaluated the browsers that are available on the various types of platforms and determined that they do not present a standard set of features –Java 2 presents a well-structured multi-layer graphical interface that provides all of the functionality we need without using a browser JVM: The Sun JVM is available on several platforms, but is not currently available on PDAs –we expect that Sun’s JVM reference implementation for WinCE will be available soon –we are currently developing on laptops XML: We have evaluated XML and find it to be very suitable for the communication between applications and the GUI

6. Long-Term Issues #1 Application Interface: Need to specify the XML interface to applications in a flexible format GPS/Radio Interface: The PDA/laptop version of the front-end should have an interface to a GPS/radio unit –allows a user to place themselves within the proper context in the sensor network –allows a user to communicate with the network –don’t foresee problems in talking to the API of the particular units, but need to work out the physical interfaces to the different platforms Query Language: Need to get specifications on the query language(s) to allow formulation of queries by the GUI

7. Long-Term Issues #2 Source of Map Information: The GUI will allow multiple map/photo formats and contexts –satellite imagery, topographical maps, city maps, etc. –need a source of correlated images –will investigate GIS systems/formats as a possible management system for information BBN Openmap: We are currently investigating this package to see how it can apply to this project