March 2004

Peter Stanforth Meshnetworks Inc

Slide 1

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

User Requirements for 80211Ad Hoc Networking

Peter StanforthCTO

MeshNetworks Incpstanforthmeshnetworkscom

March 2004

Peter Stanforth Meshnetworks Inc

Slide 2

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Introductionbull This presentation is a summary of a

White Paper being added to document listndash It attempts to identify a number of Use

Cases or User Requirements that an Ad Hoc standard should address

bull The applications covered address Public Safety and Home Networking

March 2004

Peter Stanforth Meshnetworks Inc

Slide 3

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Public Safetybull TIA and other groups

are pushing for an ad hoc networking standard based on 80211a running in newly defined 49Ghz Public Safety band

amp

March 2004

Peter Stanforth Meshnetworks Inc

Slide 4

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Project MESAbull Detailed Use Case for a

train wreck near a crowded football stadium

bull Requires around 200 active users and 50Mbits data in 1sqkm

bull Way beyond the capability of a 3G cellular system but an 80211 based solution can provide a solution

wwwprojectmesaorg

March 2004

Peter Stanforth Meshnetworks Inc

Slide 5

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

DoITT New York RFIIt is anticipated that the Network(s) Features and Functional Specifications will include but will not be limited to the following 1048766 Traffic Signal Control to provide direct on-line control of the traffic signals located throughout the City on a real-time basis 1048766 Wireless Emergency Service Call Boxes 1048766 Automatic Vehicle Location via the Network(s) infrastructure 1048766 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 1048766 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) 1048766 Continuous biological chemical nuclear and radiological monitoring at selected sites throughout the City 1048766 Telemetry of patient vital signs electrocardiograms and other biometrics to receiving hospitals 1048766 Continuous monitoring of water flow and purity 1048766 White boarding capability 1048766 Voice (ldquoVoIPrdquo) capability with guaranteed Quality of Service to backup emergency radio landline or cellular services

Appears to assume49Ghz 80211a based solution

March 2004

Peter Stanforth Meshnetworks Inc

Slide 6

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

City Wide Data Servicesi 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-2mbitssec upstream - 10mbitssec per incident - Ability to support several concurrent incidents across the city

March 2004

Peter Stanforth Meshnetworks Inc

Slide 7

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull ldquoevery PC will be an APrdquo - marketing quote

from major IC vendor chip announcementndash The distinction between client and AP will blur

quickly Every machine in the home will likely be networked

bull Why not 80211ndash 80215 is headed in that direction but consumers

know and understand 80211 so why not 80211xxbull Higher Bandwidth required

ndash 54mbit OFDM = 22mbits with 80211CSMA MACndash A single HDTV channel needs 15mbitssec today

March 2004

Peter Stanforth Meshnetworks Inc

Slide 8

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull Multi Hopping a requirement in most homes

ndash With a range of 32feet indoors most homes will require range extension through multi hopping

bull Self Forming and healing required for consumer applicationsndash People canrsquot program VCRS they canrsquot be expected to

deploy networks When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for itrsquoself

bull QOSndash This is THE home network voice datagames video

etc so QOS at a system level is needed ( Not just a link level)

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 2

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Introductionbull This presentation is a summary of a

White Paper being added to document listndash It attempts to identify a number of Use

Cases or User Requirements that an Ad Hoc standard should address

bull The applications covered address Public Safety and Home Networking

March 2004

Peter Stanforth Meshnetworks Inc

Slide 3

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Public Safetybull TIA and other groups

are pushing for an ad hoc networking standard based on 80211a running in newly defined 49Ghz Public Safety band

amp

March 2004

Peter Stanforth Meshnetworks Inc

Slide 4

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Project MESAbull Detailed Use Case for a

train wreck near a crowded football stadium

bull Requires around 200 active users and 50Mbits data in 1sqkm

bull Way beyond the capability of a 3G cellular system but an 80211 based solution can provide a solution

wwwprojectmesaorg

March 2004

Peter Stanforth Meshnetworks Inc

Slide 5

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

DoITT New York RFIIt is anticipated that the Network(s) Features and Functional Specifications will include but will not be limited to the following 1048766 Traffic Signal Control to provide direct on-line control of the traffic signals located throughout the City on a real-time basis 1048766 Wireless Emergency Service Call Boxes 1048766 Automatic Vehicle Location via the Network(s) infrastructure 1048766 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 1048766 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) 1048766 Continuous biological chemical nuclear and radiological monitoring at selected sites throughout the City 1048766 Telemetry of patient vital signs electrocardiograms and other biometrics to receiving hospitals 1048766 Continuous monitoring of water flow and purity 1048766 White boarding capability 1048766 Voice (ldquoVoIPrdquo) capability with guaranteed Quality of Service to backup emergency radio landline or cellular services

Appears to assume49Ghz 80211a based solution

March 2004

Peter Stanforth Meshnetworks Inc

Slide 6

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

City Wide Data Servicesi 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-2mbitssec upstream - 10mbitssec per incident - Ability to support several concurrent incidents across the city

March 2004

Peter Stanforth Meshnetworks Inc

Slide 7

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull ldquoevery PC will be an APrdquo - marketing quote

from major IC vendor chip announcementndash The distinction between client and AP will blur

quickly Every machine in the home will likely be networked

bull Why not 80211ndash 80215 is headed in that direction but consumers

know and understand 80211 so why not 80211xxbull Higher Bandwidth required

ndash 54mbit OFDM = 22mbits with 80211CSMA MACndash A single HDTV channel needs 15mbitssec today

March 2004

Peter Stanforth Meshnetworks Inc

Slide 8

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull Multi Hopping a requirement in most homes

ndash With a range of 32feet indoors most homes will require range extension through multi hopping

bull Self Forming and healing required for consumer applicationsndash People canrsquot program VCRS they canrsquot be expected to

deploy networks When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for itrsquoself

bull QOSndash This is THE home network voice datagames video

etc so QOS at a system level is needed ( Not just a link level)

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 3

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Public Safetybull TIA and other groups

are pushing for an ad hoc networking standard based on 80211a running in newly defined 49Ghz Public Safety band

amp

March 2004

Peter Stanforth Meshnetworks Inc

Slide 4

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Project MESAbull Detailed Use Case for a

train wreck near a crowded football stadium

bull Requires around 200 active users and 50Mbits data in 1sqkm

bull Way beyond the capability of a 3G cellular system but an 80211 based solution can provide a solution

wwwprojectmesaorg

March 2004

Peter Stanforth Meshnetworks Inc

Slide 5

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

DoITT New York RFIIt is anticipated that the Network(s) Features and Functional Specifications will include but will not be limited to the following 1048766 Traffic Signal Control to provide direct on-line control of the traffic signals located throughout the City on a real-time basis 1048766 Wireless Emergency Service Call Boxes 1048766 Automatic Vehicle Location via the Network(s) infrastructure 1048766 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 1048766 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) 1048766 Continuous biological chemical nuclear and radiological monitoring at selected sites throughout the City 1048766 Telemetry of patient vital signs electrocardiograms and other biometrics to receiving hospitals 1048766 Continuous monitoring of water flow and purity 1048766 White boarding capability 1048766 Voice (ldquoVoIPrdquo) capability with guaranteed Quality of Service to backup emergency radio landline or cellular services

Appears to assume49Ghz 80211a based solution

March 2004

Peter Stanforth Meshnetworks Inc

Slide 6

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

City Wide Data Servicesi 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-2mbitssec upstream - 10mbitssec per incident - Ability to support several concurrent incidents across the city

March 2004

Peter Stanforth Meshnetworks Inc

Slide 7

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull ldquoevery PC will be an APrdquo - marketing quote

from major IC vendor chip announcementndash The distinction between client and AP will blur

quickly Every machine in the home will likely be networked

bull Why not 80211ndash 80215 is headed in that direction but consumers

know and understand 80211 so why not 80211xxbull Higher Bandwidth required

ndash 54mbit OFDM = 22mbits with 80211CSMA MACndash A single HDTV channel needs 15mbitssec today

March 2004

Peter Stanforth Meshnetworks Inc

Slide 8

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull Multi Hopping a requirement in most homes

ndash With a range of 32feet indoors most homes will require range extension through multi hopping

bull Self Forming and healing required for consumer applicationsndash People canrsquot program VCRS they canrsquot be expected to

deploy networks When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for itrsquoself

bull QOSndash This is THE home network voice datagames video

etc so QOS at a system level is needed ( Not just a link level)

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 4

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Project MESAbull Detailed Use Case for a

train wreck near a crowded football stadium

bull Requires around 200 active users and 50Mbits data in 1sqkm

bull Way beyond the capability of a 3G cellular system but an 80211 based solution can provide a solution

wwwprojectmesaorg

March 2004

Peter Stanforth Meshnetworks Inc

Slide 5

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

DoITT New York RFIIt is anticipated that the Network(s) Features and Functional Specifications will include but will not be limited to the following 1048766 Traffic Signal Control to provide direct on-line control of the traffic signals located throughout the City on a real-time basis 1048766 Wireless Emergency Service Call Boxes 1048766 Automatic Vehicle Location via the Network(s) infrastructure 1048766 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 1048766 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) 1048766 Continuous biological chemical nuclear and radiological monitoring at selected sites throughout the City 1048766 Telemetry of patient vital signs electrocardiograms and other biometrics to receiving hospitals 1048766 Continuous monitoring of water flow and purity 1048766 White boarding capability 1048766 Voice (ldquoVoIPrdquo) capability with guaranteed Quality of Service to backup emergency radio landline or cellular services

Appears to assume49Ghz 80211a based solution

March 2004

Peter Stanforth Meshnetworks Inc

Slide 6

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

City Wide Data Servicesi 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-2mbitssec upstream - 10mbitssec per incident - Ability to support several concurrent incidents across the city

March 2004

Peter Stanforth Meshnetworks Inc

Slide 7

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull ldquoevery PC will be an APrdquo - marketing quote

from major IC vendor chip announcementndash The distinction between client and AP will blur

quickly Every machine in the home will likely be networked

bull Why not 80211ndash 80215 is headed in that direction but consumers

know and understand 80211 so why not 80211xxbull Higher Bandwidth required

ndash 54mbit OFDM = 22mbits with 80211CSMA MACndash A single HDTV channel needs 15mbitssec today

March 2004

Peter Stanforth Meshnetworks Inc

Slide 8

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull Multi Hopping a requirement in most homes

ndash With a range of 32feet indoors most homes will require range extension through multi hopping

bull Self Forming and healing required for consumer applicationsndash People canrsquot program VCRS they canrsquot be expected to

deploy networks When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for itrsquoself

bull QOSndash This is THE home network voice datagames video

etc so QOS at a system level is needed ( Not just a link level)

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 5

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

DoITT New York RFIIt is anticipated that the Network(s) Features and Functional Specifications will include but will not be limited to the following 1048766 Traffic Signal Control to provide direct on-line control of the traffic signals located throughout the City on a real-time basis 1048766 Wireless Emergency Service Call Boxes 1048766 Automatic Vehicle Location via the Network(s) infrastructure 1048766 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 1048766 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) 1048766 Continuous biological chemical nuclear and radiological monitoring at selected sites throughout the City 1048766 Telemetry of patient vital signs electrocardiograms and other biometrics to receiving hospitals 1048766 Continuous monitoring of water flow and purity 1048766 White boarding capability 1048766 Voice (ldquoVoIPrdquo) capability with guaranteed Quality of Service to backup emergency radio landline or cellular services

Appears to assume49Ghz 80211a based solution

March 2004

Peter Stanforth Meshnetworks Inc

Slide 6

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

City Wide Data Servicesi 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-2mbitssec upstream - 10mbitssec per incident - Ability to support several concurrent incidents across the city

March 2004

Peter Stanforth Meshnetworks Inc

Slide 7

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull ldquoevery PC will be an APrdquo - marketing quote

from major IC vendor chip announcementndash The distinction between client and AP will blur

quickly Every machine in the home will likely be networked

bull Why not 80211ndash 80215 is headed in that direction but consumers

know and understand 80211 so why not 80211xxbull Higher Bandwidth required

ndash 54mbit OFDM = 22mbits with 80211CSMA MACndash A single HDTV channel needs 15mbitssec today

March 2004

Peter Stanforth Meshnetworks Inc

Slide 8

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull Multi Hopping a requirement in most homes

ndash With a range of 32feet indoors most homes will require range extension through multi hopping

bull Self Forming and healing required for consumer applicationsndash People canrsquot program VCRS they canrsquot be expected to

deploy networks When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for itrsquoself

bull QOSndash This is THE home network voice datagames video

etc so QOS at a system level is needed ( Not just a link level)

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 6

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

City Wide Data Servicesi 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-2mbitssec upstream - 10mbitssec per incident - Ability to support several concurrent incidents across the city

March 2004

Peter Stanforth Meshnetworks Inc

Slide 7

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull ldquoevery PC will be an APrdquo - marketing quote

from major IC vendor chip announcementndash The distinction between client and AP will blur

quickly Every machine in the home will likely be networked

bull Why not 80211ndash 80215 is headed in that direction but consumers

know and understand 80211 so why not 80211xxbull Higher Bandwidth required

ndash 54mbit OFDM = 22mbits with 80211CSMA MACndash A single HDTV channel needs 15mbitssec today

March 2004

Peter Stanforth Meshnetworks Inc

Slide 8

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull Multi Hopping a requirement in most homes

ndash With a range of 32feet indoors most homes will require range extension through multi hopping

bull Self Forming and healing required for consumer applicationsndash People canrsquot program VCRS they canrsquot be expected to

deploy networks When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for itrsquoself

bull QOSndash This is THE home network voice datagames video

etc so QOS at a system level is needed ( Not just a link level)

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 7

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull ldquoevery PC will be an APrdquo - marketing quote

from major IC vendor chip announcementndash The distinction between client and AP will blur

quickly Every machine in the home will likely be networked

bull Why not 80211ndash 80215 is headed in that direction but consumers

know and understand 80211 so why not 80211xxbull Higher Bandwidth required

ndash 54mbit OFDM = 22mbits with 80211CSMA MACndash A single HDTV channel needs 15mbitssec today

March 2004

Peter Stanforth Meshnetworks Inc

Slide 8

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull Multi Hopping a requirement in most homes

ndash With a range of 32feet indoors most homes will require range extension through multi hopping

bull Self Forming and healing required for consumer applicationsndash People canrsquot program VCRS they canrsquot be expected to

deploy networks When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for itrsquoself

bull QOSndash This is THE home network voice datagames video

etc so QOS at a system level is needed ( Not just a link level)

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 8

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Digital Home Networksbull Multi Hopping a requirement in most homes

ndash With a range of 32feet indoors most homes will require range extension through multi hopping

bull Self Forming and healing required for consumer applicationsndash People canrsquot program VCRS they canrsquot be expected to

deploy networks When the Superbowl is interrupted by the Microwave oven the network will have to figure it out for itrsquoself

bull QOSndash This is THE home network voice datagames video

etc so QOS at a system level is needed ( Not just a link level)

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 9

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (1)bull Fast Route Discovery

ndash And even faster route switching (or Hand Off) to deal with interference and congestion with minimum impact on latency and reliability

bull Highly Scalablendash To many nodes for wide area coverage

and higher capacity shorter links

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 10

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (2)bull Self Forming and Self Healing

ndash Networks are complex and need to be established with minimal technical competence This characteristic also assures portability

bull QOSndash Goes beyond a Link layer issue to a

network or systems issue

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 11

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Generic Requirements (3)bull Coexistence

ndash 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

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 12

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

Summarybull A sense of urgency is required

ndash The world is moving despite lack of a standardbull Need to defined Use Cases quickly

ndash Different from 80215bull Need Hooks into MAC for Link quality

metricsndash Ref 0303 plenary Peter Stanforth amp Vann Hasty ldquoLower layer

support for ad hoc mesh networksbull Solutions need to be extensible

ndash Unlikely that everything will be in first edition

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13

March 2004

Peter Stanforth Meshnetworks Inc

Slide 13

doc IEEE 80211-04-0371-00-0mes-user-requirementsppt

Submission

• User Requirements for 80211 Ad Hoc Networking
• Introduction
• Public Safety
• Project MESA
• DoITT New York RFI
• City Wide Data Services
• Digital Home Networks
• Slide 8
• Generic Requirements (1)
• Generic Requirements (2)
• Generic Requirements (3)
• Summary
• Slide 13