1 / 15

Do You See What I See (DYSWIS)

Do You See What I See (DYSWIS). Aditya Muthyala (am3551) School of Engineering and Applied Science Columbia University, Fall 2011. Requirements. Wireless Network Diagnosis Monitoring data and matching patterns Peer Probing to conclude on the root cause of the issue. Challenges.

neal
Download Presentation

Do You See What I See (DYSWIS)

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. Do You See What I See(DYSWIS) Aditya Muthyala (am3551) School of Engineering and Applied Science Columbia University, Fall 2011

  2. Requirements • Wireless Network Diagnosis • Monitoring data and matching patterns • Peer Probing to conclude on the root cause of the issue

  3. Challenges • Needed a rich and well maintained API to monitor the wireless metrics • Microsoft Native Wifi API was a solution • API supported only C/C++ • JNI bridging used to exchange data to and from native code

  4. Design • Monitor the wireless interface metrics • Transmitted frame counts • Bytes exchanged • Signal quality • Error counts • Exchange data with peers • Diagnosis Engine

  5. System Architecture

  6. System Requirements • Native WifiApi (Windows) • Windows 7/XP(SP3)

  7. Implementation • Metrics Monitor • Collected from Native Wifi API by Microsoft • 10 minute average stored at a time • Written in C++ • Packet Capture • Used to monitor the number of bytes exchanged • Written in Java

  8. Simulation and Testing

  9. Challenges • Simulating real world scenarios is difficult • Tried to use network simulators • Some did not provide the metrics we require • Others concentrated on simulating mobility • No proper representation of results

  10. Simulation Environment and metrics • Environment • Network nodes (laptops) • Network router • Metrics • Signal quality • Error counts/transmitted counts • Bytes exchanged

  11. Simulation results Signal Strength Time Interval

  12. Signal Strength Time Interval

  13. Observations • Signal Quality remains constant for static environment • Signal quality variations are too high in case of RF interference • FCS grows linearly with time. No plausible conclusion reached • No threshold on bytes transferred

  14. Algorithm

  15. Future Work • Packet Capture from non participating nodes • Monitor Received Packet counts and FCS errors to diagnose Packet drops • Signal quality variations due to various RF interferences

More Related