1 / 6

Presented on: October 8, 2012

Trickle: A Self-Regulating Algorithm for Code Propagation and Maintenance in Wireless Sensor Networks. Presented on: October 8, 2012. Problem. Wireless Sensor Networks

ethel
Download Presentation

Presented on: October 8, 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Trickle: A Self-Regulating Algorithm for Code Propagation and Maintenance in Wireless Sensor Networks Presented on: October 8, 2012

  2. Problem Wireless Sensor Networks Consist of large no. of small, resource-constrained computing nodes, Operate unattended for long durations, scale and embedded nature REQUIRE CODE to be PROPAGATED over the Network.

  3. Problem (continued) • Codes need to be propagated QUICKLY and EFFICIENTLY • Maintenance of a consistent code image throughout the Network + Low power radios (high loss, transient disconnection)

  4. Algorithm Requirements • Algorithm needs to have three properties • Low Maintenance • Rapid Propagation • Scalability • Maintain its other properties in wide ranges of network density

  5. Experimental Methodology Three Different Platforms: 1. Abstract Simulation High level abstract algorithm simulator: Trickle-specific, quickly evaluates change in algo behavior 2. TOSSIM A bit-level simulator for TinyOS, a sensor network operating system 3.Tiny OS nodes Used for empirical studies

  6. Trickle To exchange code metadata -“Polite Gossip” policy • If a node hears gossip with same metadata, it keeps quiet. • If it hears an old gossip, it broadcasts a code update. • Nodes adjust the length of their gossiping attention spans, communicating more often when there is new code.

More Related