1. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 1 User Requirements for 802.11 Ad Hoc Networking Peter Stanforth CTO MeshNetworks Inc pstanforth@meshnetworks.com

2. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 2 Introduction This presentation is a summary of a White Paper being added to document list. –It attempts to identify a number of Use Cases or User Requirements that an Ad Hoc standard should address The applications covered address Public Safety and Home Networking

3. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 3 Public Safety TIA and other groups are pushing for an ad hoc networking standard based on 802.11a running in newly defined 4.9Ghz Public Safety band &

4. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 4 Project MESA Detailed Use Case for a train wreck near a crowded football stadium Requires around 200 active users and 50Mbits data in 1sq/km Way beyond the capability of a 3G cellular system but an 802.11 based solution can provide a solution www.projectmesa.org

5. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 5 DoITT New York RFI It is anticipated that the Network(s) Features and Functional Specifications will include, but will not be limited to, the following: Traffic Signal Control to provide direct, on-line control of the traffic signals located throughout the City on a real-time basis. Wireless Emergency Service Call Boxes. Automatic Vehicle Location via the Network(s) infrastructure. Simultaneous transmission of varying file types, including large database files and large graphic files (such as building design, construction and floor plan information in AutoCAD format) as well as mug shots, fingerprints and criminal records from local, City and federal databases. Simultaneous transmission of full motion (30 frames per second) streaming video on demand, on an ad-hoc basis from multiple fixed and mobile sites, throughout the Network(s). Continuous biological, chemical, nuclear and radiological monitoring at selected sites throughout the City. Telemetry of patient vital signs, electrocardiograms, and other biometrics to receiving hospitals. Continuous monitoring of water flow and purity. White boarding capability Voice (“VoIP”) capability, with guaranteed Quality of Service, to backup emergency radio, landline or cellular services. Appears to assume 4.9Ghz 802.11a based solution

6. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 6 City Wide Data Services i 99% mobile radio coverage on roads. ii. 99% in-street coverage in the City and in certain other specified locations. iii. Proposer must define methodology and pricing structure to provide for in- building coverage. Given the limited power, and therefore range, at high data rates, the need for a large number of APs is inevitable. If only a percentage are meshed to reduce backhaul cost the overall size of the mesh is still significant - 1-2mbits/sec upstream - 10mbits/sec per incident. - Ability to support several concurrent incidents across the city

7. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 7 Digital Home Networks “every PC will be an AP” - marketing quote from major IC vendor chip announcement –The distinction between client and AP will blur quickly. Every machine in the home will likely be networked. Why not 802.11 –802.15 is headed in that direction but consumers know and understand 802.11 so why not 802.11xx? Higher Bandwidth required –54mbit OFDM = 22mbits with 802.11CSMA MAC –A single HDTV channel needs 15mbits/sec today

8. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 8 Digital Home Networks Multi Hopping a requirement in most homes –With a range of 32feet indoors most homes will require range extension through multi hopping Self Forming and healing required for consumer applications –People can’t program VCRS, they can’t be expected to deploy networks. When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for it’self. QOS –This is THE home network, voice, data,games, video etc. so QOS at a system level is needed ( Not just a link level)

9. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 9 Generic Requirements (1) Fast Route Discovery –And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability Highly Scalable –To many nodes for wide area coverage and, higher capacity, shorter links

10. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 10 Generic Requirements (2) Self Forming and Self Healing –Networks are complex and need to be established with minimal technical competence. This characteristic also assures portability QOS –Goes beyond a Link layer issue to a network or systems issue

11. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 11 Generic Requirements (3) Coexistence –A node may need to determine which network to be part of. Not only for security issues but so QOS and and users can be managed effectively

12. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 12 Summary A sense of urgency is required –The world is moving despite lack of a standard Need to defined Use Cases quickly –Different from 802.15? Need Hooks into MAC for Link quality metrics –Ref 03/03 plenary Peter Stanforth & Vann Hasty “Lower layer support for ad hoc mesh networks Solutions need to be extensible –Unlikely that everything will be in first edition

13. doc.: IEEE 802.11-04-0371-00-0mes-user-requirements.ppt Submission March 2004 Peter Stanforth, Meshnetworks Inc.Slide 13