26
January 2005 Brian Ford , Bel Slide 1 doc.: IEEE 802.11-05/1644r0 Submission Service Provider Requirements for 802.11n Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < http:// ieee802.org/guides/bylaws/sb-bylaws.pdf >, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <[email protected] > as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If Date: 2005-01-17 N am e C om pany A ddress Phone em ail Brian Ford BellSouth 725 W estPeachtree Room 7A43 Atlanta,G A 30308 (404)986-9631 [email protected] CharlesCook Q w est D enver,CO (303)896-5652 charles.cook2@ qwest.com Authors:

Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

Embed Size (px)

DESCRIPTION

doc.: IEEE /1644r0 Submission January 2005 Brian Ford, BellSouthSlide 3 Changes since rev 0

Citation preview

Page 1: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 1

doc.: IEEE 802.11-05/1644r0

Submission

Service Provider Requirements for 802.11n

Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.

Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11.

Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <[email protected]> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <[email protected]>.

Date: 2005-01-17

Name Company Address Phone email Brian Ford BellSouth 725 West Peachtree

Room 7A43 Atlanta, GA 30308

(404) 986-9631 [email protected]

Charles Cook Qwest Denver, CO (303) 896-5652 [email protected]

Authors:

Page 2: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 2

doc.: IEEE 802.11-05/1644r0

Submission

Abstract

This document proposes TGn consider the impact of an incomplete standard due to weaknesses in definition. Such a standard would have a negative impact on Service Providers, the primary link in high throughput applications, although SPs would not be at fault when 802.11n problems occur. Resolving the weaknesses should be considered as a major component of achieving “Broad Market Potential”

Page 3: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 3

doc.: IEEE 802.11-05/1644r0

Submission

Changes since rev 0

Page 4: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 4

doc.: IEEE 802.11-05/1644r0

Submission

List of Contributors/Supporters

• John Egan, Infineon

Page 5: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 5

doc.: IEEE 802.11-05/1644r0

Submission

The 802.11n consumer “food chain”

Consumer

Service Provider

Technologists (TGn)

802.11n standard

PDA

Media Server

iMac

HD TV

Laptop computer

VoIP Phone

SD TV

802.11n AP

MP3 Client

Retailers

Have need for high rate broadband for demanding content and access, otherwise why have 802.11n?

•Provide the service•Help drive demand•Get most of the complaints

Sell… no service provisioning, typically

In-home applications that will require the high data rates of 802.11n, can be mixed wired and wireless LAN – an All Media Network™ (AMN)

As far as 802.11n TG “sees”

We create innovations but users create the impact and applications

Page 6: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 6

doc.: IEEE 802.11-05/1644r0

Submission

DSL/Cable Modem Evolution

Modem Router

Modem

Modem RouterWLAN

•First modems deployed: Link in Ethernet out

•Second generation modems now defined as Gateways: Link in Ethernet ports out

•Third generation modems deployed: Gateway with WLAN AP

DSL Router

DSL Router w/ WLAN

Page 7: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 7

doc.: IEEE 802.11-05/1644r0

Submission

Some Facts…• Majority of SPs provide modem or gateway as part of service• Modem/Gateway varies by SP, service type, monthly cost, and by

geographic market• Original Modem was simple DSL/Cable to Ethernet port, bridge function• Gateways replacing modems

– Gateway is modem with Router/switch– Gateway with AP is option for some SPs, mandatory for others

• In 2003, the number of:– APs sold in NA (all types): 6,111,016 – Wireless BB Gateways (DSL/Cable w/ Router/switch, AP) sold NA: 4,284,148– Percentage ratio based on above: 70%

• Market data from Infonetics Research

Page 8: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 8

doc.: IEEE 802.11-05/1644r0

Submission

Worldwide is similar to NA Infonetics Research Chart (actual to date (Q3 04) and forecasts)

Worldwide Access Point Unit Breakdown

14%18%

14% 14% 14%

9%14%

9% 9% 9%

76%

60%

76% 76% 77%

8% 4% 5% 4% 4%0%

20%

40%

60%

80%

CY03 CY04 CY05 CY06 CY07

Calendar Year

StandaloneSOHO/consumerStandaloneSP/enterpriseWireless bb gateways

WLAN bridges

Wireless broadband gateways are Access Points with integrated router/switch capabilities and Cable/DSL uplinks that enable a group of users to share a broadband connection; can also have integrated security features such as VPN pass-through, firewalls, etc.

Page 9: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 9

doc.: IEEE 802.11-05/1644r0

Submission

Telco Broadband Initiatives

• SBC announces FTTN with 20-25M Downstream (DS) over copper to home, FTTH with ~19.5M over fiber (video separate from data and voice)

– Future GPON will have all IP triple play• BellSouth announces ~25M DS over copper. Deploying FTTCurb• Verizon announces FTTP at ~19.5M over fiber (video separate from

data and voice)– Plan to move to GPON in future

• Bell Canada announces initiative to deliver 20-25M DS over copper• KT deploys 50M DS/10-30M US over copper, moving to 100M• NTT deploys 100M DS/30-40M US over copper and FTTH with

100M PtP or PON

Page 10: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 10

doc.: IEEE 802.11-05/1644r0

Submission

Cable MSO Broadband Initiatives

• DOCSIS 2.0– Cable Labs interop tested & certified– Defined as up to 30.72M DS/30.72M US (Voice & Data) with shared

access over multiple subscribers• Have content, have delivery mechanism into the home

– However, WLAN is not a fit for RF video• Shift to digital video channels• VOD can be to wired TV (coax) or WLAN enabled devices

Page 11: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 11

doc.: IEEE 802.11-05/1644r0

Submission

It isn’t just data…• SBC announces IPTV over copper links with VoIP & data• BellSouth similar initiative, mentioned in Bill Gates keynote at CES 2005• Verizon VoiceWing VoIP offering rolling out• Internet-based streaming media use grows, requiring higher data link rates

to achieve consumer quality of experience• Vonage announces Wireless VoIP sets at CES January 2005. Vonage

expects very positive market response• Cablevision announces take rate of at ~1000 VoIP customers/day and over

250K total• Service Providers (both Cable and Telco) are a driving force for 802.11n

demand as they are the connecting service for content, their data rate provides the basis for an 802.11n market demand - i.e. low BW rates = low WLAN demand, high rates…

• SPs offering 802.11n optioned modems will drive into consumer space an adoption of Stations, building huge market dynamic and potential

Page 12: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 12

doc.: IEEE 802.11-05/1644r0

Submission

802.11n Service Provider driversService Provider, that is not the in-premises incumbent, has following options to provide in-home services

– Run cable• Costs for truck roll plus time and cable, if consumer pays is a negative = new service cost

too high versus existing• Fixed termination points counter-intuitive

– Use existing coax (if a Telco), twisted pair (if Cable MSO), or power lines• Truck roll with related expenses• Cost versus 802.11n• Fixed point termination

– Use 802.11n• Enables “connectivity anywhere” marketing by SP & consumer electronics companies

– No fixed point connections needed• Embedded Stations are consumer’s cost… reducing SP overhead• The possibility of using 802.11n depends on consumer’s ‘experience,’ QoS, BW,

coverage, and encryption

Page 13: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 13

doc.: IEEE 802.11-05/1644r0

Submission

Additional SP drivers (WLAN sets)

• Movement to VoIP drives WLAN SIP sets, creating need for more WLAN capabilities: service area, QoS, and mobility support

• Dual mode handsets allow for shifting between public cell network and WLAN. Better to have a long term technology that does not reduce WLAN air throughput. 15-20% (industry estimate) of handsets sold in US starting 2006 will be dual mode WLAN and cell

Page 14: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 14

doc.: IEEE 802.11-05/1644r0

Submission

What do Service Providers need

• Highest possible consumer satisfaction… if mobile VoIP set doesn’t work faultlessly consumers blame Service Provider or AP provider, not 802.11n TG for missing something in the standard

• QoS is primary requirement – video and high throughput data sessions (possibly mobile)

• Streaming, high data rate video delivery, error free• Management capability to the devices• Improvements to Plug n Play (out of scope of 802.11n, but needs work as

consumers have no idea what to do)• Encryption• Mobility support

– Eliminate Doppler Effect– Handoff– Mesh

• High data rate with range to enable outdoor to indoor 150M operation

Page 15: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 15

doc.: IEEE 802.11-05/1644r0

Submission

Is Multi-Dwelling Support Possible?• Curb-side or pole mounted AP• Few barriers (trees) in the way• Approx 150m service radius to

dwelling Point of Presence (Wireless NID inside closest wall)

• Similar to “Outdoor” simulation definition, yet different application

• Prefer to be able to transit through a house to far end - additional ~30m

• Want >>25M delivered to Wireless NID, what is possible?

• 150m determined by FCC as max. unbundling distance for FTTH/C

Single Family Unit

TreeTree

Curb side or polemounted AP

150m500 ft

30m/100 ft

Page 16: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 16

doc.: IEEE 802.11-05/1644r0

Submission

Link Level Throughput & Range from Wi-Fi Alliance submittal

Range

A

DC

B

Throughput

Business

Infotainment

Services

 Point A/C = 80 Mb/s at 20m.This denotes the point of link level throughput required in typical domestic settings Point B/D = 10 Mb/s at 100 m. – Need 150m and 25 Mb/sThis denotes the point of minimal link level throughput required in typical hotspot settings

Page 17: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 17

doc.: IEEE 802.11-05/1644r0

Submission

Estimated Signal Drop Parameters for 2.4 GHz

• ~9 dB drop – Exterior Wall• ~6 dB drop – Floor• ~3 dB drop – interior (sheetrock) wall

Page 18: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 18

doc.: IEEE 802.11-05/1644r0

Submission

Requested Evaluation PointsSignal Distance & Drop

Exterior AP Landscape Exterior AP Overhead

Exterior Wall

Distance = D1

Width = D2

Distance = D2

Measuringdevice

Room 1

Distance = D1

Width = D2

Distance = D2

External AP

External AP

Page 19: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 19

doc.: IEEE 802.11-05/1644r0

Submission

Requested Evaluation Points Signal Distance & Drop

Interior AP OverheadInterior AP Landscape

Interior Wall

Distance = D1

Distance = D2

Measuringdevice

Distance = D2Distance = D1

Width = D2

Width = D2

Room 1 Room 2

Internal AP Internal AP

Room 2

Room 1

Page 20: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 20

doc.: IEEE 802.11-05/1644r0

Submission

Mesh/Hand-off

• If multiple APs in adjoining/overlapping areas…– Can one be a station of another (FTTCurb scenario)– Can they be in a mesh configuration?– Can there be hand-off between them

• What are considerations if Yes– Errors– Data rate change– Presumes is high probability mobility session so need to address the small

packet definition here as well or is in event of one AP failure and another taking over service

Page 21: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 21

doc.: IEEE 802.11-05/1644r0

Submission

What this all nets out to…

• To meet Broadest Market Potential– Need to meet Service Provider needs, as they…

• Face the consumer in a high % of deployments• Will drive up mass Station deployments through AP deployments

– Provide highest consumer satisfaction experience– Plug the holes regarding mobile sessions, including hand-offs

between APs and Mesh

Page 22: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 22

doc.: IEEE 802.11-05/1644r0

Submission

Proposed Changes to Methodology & Definitions re: Doppler Effect

• Analyze impact of large packet size with errors and retransmits versus mixed packet environment where fewer retransmits occur

• Set simulations to cover moderate speed mobile sessions over range of weak signal scenarios

• To help eliminate the Doppler Effect, we propose that small packets be used for devices that are defined as able to be in mobile sessions

– Add a byte per handshake denoting device type• 0000 = Station accepts any size packet• 0001 = Station accepts only small size packets (helps handle moderate speed

mobility sessions in weak signal areas)• Other bits reserved

– Add a table per AP for tracking device types recently registered by Station identifier

• Support up to 256 recently registered Stations in FIFO stack• AP references when assembling packets for transmission

Page 23: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 23

doc.: IEEE 802.11-05/1644r0

Submission

Proposed Changes/Comments

• Develop ability to achieve highest distance/rate as an outdoor/curb-side service point

• Internal coverage Reach and Rate determinations or multi-AP use to meet real world needs for high quality in-home coverage

• Ensure highest QoS for sensitive data/video delivery (FEC, etc. included as a requirement, either by device type [more types?] or for all devices)

• Ensure encryption is sufficient to meet Content Provider concerns regarding over-air security

Page 24: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 24

doc.: IEEE 802.11-05/1644r0

Submission

Will this require a new PAR?

• No, see excerpts from PAR– 12. Scope of Proposed Project:

• The scope of this project is to define an amendment that shall define standardized modifications to both the 802.11 physical layers (PHY) and the 802.11 Medium Access Control Layer (MAC) so that modes of operation can be enabled that are capable of much higher throughputs, with a maximum throughput of at least 100Mbps, as measured at the MAC data service access point (SAP).

– 13. Purpose of Proposed Project:• The purpose of the project is to improve the 802.11 wireless local area

network (LAN) user experience by providing significantly higher throughput for current applications and to enable new applications and market segments.

Page 25: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 25

doc.: IEEE 802.11-05/1644r0

Submission

New PAR?

• Possible Confusion– Under item 18, additional explanatory notes for item 12

• “The enhancements shall be to support higher throughput. The amendment shall not redefine mechanisms in the baseline that do not pertain to higher throughput.”

– We believe this still allows changes supporting the requirements in this presentation as these requirements will facilitate new applications and higher throughput application QoS

Page 26: Doc.: IEEE 802.11-05/1644r0 Submission January 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Notice: This document has been

January 2005

Brian Ford, BellSouth

Slide 26

doc.: IEEE 802.11-05/1644r0

Submission

Conclusion

Service Providers of all types represent a substantial driver for achieving 802.11n broad market acceptance and success. Meet SP’s needs and we achieve Criteria 1 as well as eliminate the need for some future 802.11 effort to plug the holes…