1. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Self Forming Self Healing Networks Peter Stanforth & Vann Hasty MeshNetworks Inc. 11-03-216r0-w-meshnetworks_tutorial.ppt

2. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Contact Information Peter Stanforthpstanforth@meshnetworks.compstanforth@meshnetworks.com Vann Hasty vhasty@meshnetworks.comvhasty@meshnetworks.com www.meshnetworks.com

3. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Beyond peer to peer 802.11 MAC “ad hoc” a network composed solely of stations within mutual communication range of each other.

4. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Self Forming, A.K.A. Ad hoc networks Multi hop networks Mesh networks Viral networks

5. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Nothing New! DARPA and the US Military has a long history of ad hoc networking dating back to Packet Radio experiments over 20 years ago

6. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Potentially no infrastructure Communities (Schools, clubs, social groups) Location for parents? Generation that readily accepts technology Multi player games, chat, IM Applications: Kids & Games

7. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Instant Deployment Accurate and fast Location Voice, Data and Video 802.11a based 4.9Ghz band solutions Applications: Emergency Service

8. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Rapid deployment High bandwidth No LOS requirement Little RF and infrastructure planning No Right Of Way issues All you can eat billing options Applications: Last Mile

9. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Based on 802.11b, or802.11a, Short range High data rate Fixed or portable Self deploying & Self organizing - Zigbee initiative BroadBand backbone (cable, DSL, Utility) The BroadBand Home

10. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Future: Intelligent Highways 802.11a based DSRC plus Ad hoc networking

11. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Why an ad hoc network? The belief in its ability to significantly improve the capability of any RF modulation scheme by:  Requiring less power  Having the ability to be rapidly deployed and reconfigured  Providing better frequency reuse  Not requiring Lines of Sight (LOS)  Being able to load balance around congestion  Providing redundancy to deal with failure  Requiring less centralized infrastructure  Providing capacity and scalability improvements

12. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks 802.11 and ad hoc networking Many companies today are providing ad hoc networking for standard 802.11 devices. Implementing routing at layer 2.5 or 3 Demonstrable advantages to adding ad hoc routing including range, capacity and scalability improvements.

13. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Client Meshing Example Extends range between 802.11 devices Off-loads traffic from APs via peer-to-peer links Increases data rates to distant clients Reduces number of APs and associated costs

14. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Infrastructure Meshing Example Backhaul is minimized Increased AP location flexibility Can create Hot Zones not just Hot Spots Deployment costs are reduced Leverages 802.11 standards No new client software

15. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Implications for 802.11 There is no Silver Bullet! ONE SIZE FITS ALL

16. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Implications for 802.11 There is no Silver Bullet! General class of routing algorithms Proactive Low latency not scalable Reactive Highly scalable unpredictable latency ONE SIZE FITS ALL

17. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Implications for 802.11 There is no Silver Bullet! Type of Network PAN, LAN, WAN ONE SIZE FITS ALL

18. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Some lessons learned Feedback from MAC/LLC to Routing Immediate feedback of TX/RX status is critical in developing a reliable network. Feedback from the PHY A normalized measure of the number of corrected error bits in a received message can be used to predict a degrading link

19. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Some lessons learned MAC layer Management entity control Fine grained control of the data rate selection on a per packet basis is needed to select routes with the highest end to end throughput. Transmit power control allows optimal frequency reuse Basic MAC Functions Power Save mode needs enhancement to minimize timing delays in terminals more than 1 hop from an AP. Group traffic needs to be able to be extended beyond basic data rates for routing protocols that build and distribute topology information

20. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Some lessons learned Security Almost everything today is focused on infrastructure mode of operation, access control, link layer (node to node) and higher layer (IPSEC) considerations

21. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Some lessons learned Routing metrics information about other nodes including their congestion status, battery status and is needed to allow Location Based Services Need to be more robust than RSSI measurement as this is too easily attenuated. To use TOF/TOA the timing becomes critical, the turn around time must be deterministic

22. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Implications for 802.11 There are many enhancements that can be made to the existing standards efforts to improve the capability and interoperability of ad hoc networks. Do this before being drawn into holy wars on different routing protocols!

23. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Implications for 802.11 Step 1 Define a better interface between the MAC and higher layers The capabilities include standard definition of, and access to, the radio link measurements, not only RSSI but number of retransmissions and error correction done on received packets A standard way of controlling power/data rate of the transmitter is also needed to allow the option of multi- hopping at high data rates or single hopping at lower rates Some of this is ongoing in 802.11k

24. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Implications for 802.11 Step 2 Extend the existing MAC to allow information pertinent to ad hoc networks to be pass across the network efficiently The key information needed relates to neighbor discovery, identification of APs (and other network resources), battery awareness - crucial in mobile ad hoc networks, the ability to support location awareness This would provide common basic building blocks for ad hoc routing protocols

25. doc.: IEEE 802.11-03/216 SubmissionPeter Stanforth, Vann Hasty, MeshNetworks Implications for 802.11 Step 3 Define interoperability between multiple ad hoc protocols/networks This will not be easy! There are as many protocols as companies and solutions today and the trick is to get them all to co- exist peacefully