CSCI 7143-002: Wireless Sensor Networks
Department of Computer Science, University of Colorado at Boulder
|Abstract: Wireless sensor networks (WSNs) have become one of the hottest areas of research in computer science. WSNs consist of many small distributed wireless computers that sense their environments and self-organize to form multi-hop wireless networks capable of relaying their data to a backbone server. Exciting applications of WSNs have been demonstrated thus far, some of which will be studied in this course, and include a WSN to monitor wildland forest fires, a volcano WSN, a habitat monitoring application for seabirds off the coast of Maine, and an application that localizes snipers by their acoustic footprint.||
Night view of the wildland fire where we deployed our wireless sensor network for weather monitoring.
Helicoptering in to deploy the sensor nodes.
In this graduate seminar, we will
We will study how the unique constraints of sensor networks - wireless, low power, small form factor, limited memory/CPU - affect the design of networking protocols, operating systems, applications, middleware. We will construct real sensor networks using standard commercial sensor nodes and develop hands-on familiarity with sensor systems. A thorough understanding of TCP/IP networking, wireless networking, and operating system concepts is a prerequisite.
|Schedule & Location:||TTH 2-3:15
pm, ECEE 265 (may change to ECOT 831)
|Course number:||CSCI 7143-002, Call # 85084. See also the CS Web site and select Courses.|
standing, and strong understanding of TCP/IP and wireless
undergrads should contact the instructor.
|Instructor:||Professor Rick Han, http://www.cs.colorado.edu/~rhan|
|Office Hours:||Monday 11-12
noon, Wednesday 2-3 pm, in ECCR 1B06 - note that this is different (and
across the hallway) from my office
|Readings:||selected papers, TBD.|
|Class Web site:||http://www.cs.colorado.edu/~rhan/CSCI_7143_001_Fall_2006/home.htm|
Students will be asked to:
design and build an innovative research project for presentation at the end of the semester. Students should organize themselves into research project teams. A final project presentation will be required, and a final written report will be submitted.
for each research paper in the assigned reading list:
participate in the class discussion of each paper
provide written summaries of each paper before class
volunteer to present in class certain of the papers on the reading list, on a rotating basis
develop software programs on sensor nodes
Final project presentation to class
25% Final project report
20% Class presentation of papers
15% Paper reviews and participation in discussion
15% Programming projects on sensors
Religious observances policy.
Discrimination and Sexual Harassment policy.
Classroom Behavior policy.
be asked to build/create an innovative research project for
presentation at the
end of the semester. Students will form
teams of 2-3 members and work on projects as a team.
Teams and projects will be decided according to the timeline
below. Read ahead to topics that you'd be interested to do a
A list of suggested project ideas will be available later.
Students are welcome to formulate their own project ideas.
Each team will be required to present their project to the class at the end of the course. A final project report written in the style of a conference paper will be handed in following the presentation. If the final project is sufficiently innovative, and is accepted as a paper at a conference, then I'll pay for your trip to that conference (Past projects have led to publications at conferences in Monterrey, California, and Athens, Greece).
Timeline for Project Presentations:
Paper Reviews and Presentations
Students are required to read, present, and discuss graduate-level research papers throughout the semester. An average of 2-3 papers per week will be read. Written reviews of each paper to be discussed in class are due prior to the start of that class, and should be emailed to the instructor firstname.lastname@example.org. Late reviews will not be accepted. For each paper, students should write a review answering each of the following questions:
What problems (with prior work or the lack thereof) were addressed or surveyed by the authors?
What solutions were proposed or surveyed by the authors?
What are the technical strengths and main contributions of the paper's proposed solutions?
What are the technical weaknesses of the paper's proposed solutions? What suggestions do you have to improve upon the paper's ideas?
Each paper to be discussed in class will be assigned to a student to present in class. Assignments will rotate thoughout the class. Papers will be assigned approximately one week in advance of the presentation date. The presenter of a given paper must email their Powerpoint slides to the instructor email@example.com by midnight of the night before the presentation. The in-class presenter of a particular paper does not have to submit written reviews for any of the papers reviewed that same day in class. The paper schedule may vary over the course of the semester, e.g. as new papers become published at the most recent conferences.
There will be one or two software programming projects in which students will build applications on actual physical sensor nodes, deployed outdoors and/or indoors. Some examples of such projects could be:
Build a multicast routing protocol for indoor sensor networks.
Build a sense-and-forward application that takes GPS location data and forwards it back to a base station using the previously built multicast routing protocol.
We will likely be programming in C on MANTIS OS on TELOSB motes. The late policy on programs is 10% off the grade if late within one day, 20% off the grade for two days late. Programs that are submitted more than two days late will no longer be accepted. Programs should be emailed to the instructor. More information will be available on the Announcements web page.
As the class progresses, announcements will be posted on the Announcements Web page of the class Web site.