1 / 15

Internet-based Fault Recovery for Home Wireless LANs

Internet-based Fault Recovery for Home Wireless LANs. Author: Unknown Presenter: Thomas Donahoe. EWLAN vs RWLAN. No private wired connection Not centralized No coordination. High speed wired backbone Centralized controller Admin coordinates wireless. EWLAN Benefits for RWLAN.

nero-cross
Download Presentation

Internet-based Fault Recovery for Home Wireless LANs

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. Internet-based Fault Recovery for Home Wireless LANs Author: Unknown Presenter: Thomas Donahoe

  2. EWLAN vs RWLAN • No private wired connection • Not centralized • No coordination • High speed wired backbone • Centralized controller • Admin coordinates wireless

  3. EWLAN Benefits for RWLAN • Internet as the backbone • Decentralized approach • Automated (no admin) RxIP: a decentralized network diagnostic and recovery tool, initially targeted at hidden terminal mitigation

  4. RxIP: How will it work? 1. Detect hidden terminal problem 2. Isolate the hidden terminal 3. Recover by coordination (token system)

  5. Is there a hidden terminal? Asymmetry delivery ratio or bitrate for upload vs download AP 1 AP 2 Fail! Success! Success! Collision! A B

  6. Is there a hidden terminal? Where is AP1’s DATA? I hear A’s ACK AP 1 AP 2 ACK DATA A B

  7. Which is the hidden terminal? • RxIP AP’s record timestamp • Challenge-response protocol via the internet H.T.?

  8. Which is the hidden terminal? • Loss + Concurrent (Collision) • Success + Concurrent (No Collision) • Loss + Not Concurrent • Success + Not Concurrent H.T.? • Saturation Counter

  9. Recovery By Coordination • Token passed back and forth • AP’s “purchase” transmission timeslot • Abstain notification

  10. Recovery By Coordination • More HT = more complicated • Must purchase from every partner

  11. RxIP: What else? • Ideal token passing (NP hard) • No deadlock • Token loss • Incrementally deployable • Internet latency

  12. Evaluation

  13. Evaluation

  14. Evaluation

  15. Questions?

More Related