23
March 2 005 Brian Ford , Bel Slide 1 doc.: IEEE 802.11-05/0109r0 Submission Service Provider Requirements for 802.11n Detailed 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-03-16 N am e C om pany A ddress Phone em ail Brian Ford BellSouth 725 W estPeachtree Room 7A 43 A tlanta,G A 30308 (404)986-9631 Brian.ford@ bellsouth .com CharlesCook Q w est 1801 California Street 26th Floor D enver,CO 80027 (303)896-5652 charles.cook2@ qwest .com Authors:

Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

Embed Size (px)

Citation preview

Page 1: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 1

doc.: IEEE 802.11-05/0109r0

Submission

Service Provider Requirements for 802.11n Detailed

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-03-16

Name Company Address Phone email Brian Ford BellSouth 725 West Peachtree

Room 7A43 Atlanta, GA 30308

(404) 986-9631 [email protected]

Charles Cook Qwest 1801 California Street 26th Floor Denver, CO 80027

(303) 896-5652 [email protected]

Authors:

Page 2: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 2

doc.: IEEE 802.11-05/0109r0

Submission

Abstract

This document expands on presentation 11-05-1644-01-000n. This document provides areas within 802.11 that must be considered as to market impact of weaknesses in 802.11 standard definition. The primary focus is 802.11n as this enables a true wireless high throughput triple play. An 802.11n that does not address the issues presented will have a negative impact on Service Providers, the primary link in high throughput applications. Resolving the weaknesses should be considered as a major component of achieving “Broad Market Potential” and a truly “market-enabling standard.”

Page 3: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 3

doc.: IEEE 802.11-05/0109r0

Submission

List of Contributors/Supporters• John Egan, Infineon, [email protected]

• Fanny Mlinarsky, Azimuth Systems, [email protected]

Page 4: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 4

doc.: IEEE 802.11-05/0109r0

Submission

Background slides

• Following slides recap needs presented in 11-05-1644-01-000n

• Summary of messages– Service Providers will be impacted by the standards weaknesses

– Service Providers deploy standards-based systems, systems that require non-standard functions to meet needs are unacceptable

– High Throughput APs and Stations will drive broad market acceptance and use of WLAN, placing SPs in a position to face consumer complaints over issues unresolved in the standards, and so unresolved in 802.11n-based systems

– SPs have specific concerns as listed

Page 5: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 5

doc.: IEEE 802.11-05/0109r0

Submission

What do Service Providers need• Highest possible consumer satisfaction… if WLAN VoIP set doesn’t work

faultlessly consumers blame Service Provider or set 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– Tight integration with mobile services to support IMS/MMS

• Long Range with high data rate to enable outdoor to indoor 150m operation

Page 6: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 6

doc.: IEEE 802.11-05/0109r0

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 7: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 7

doc.: IEEE 802.11-05/0109r0

Submission

Example of Requested Evaluation Points Signal Distance & Drop - Exterior

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

Composition and dB impact?

Page 8: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 8

doc.: IEEE 802.11-05/0109r0

Submission

Example of Requested Evaluation Points Signal Distance & Drop - Interior

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 1Up to 6 walls?

Page 9: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 9

doc.: IEEE 802.11-05/0109r0

Submission

Estimated Signal Drop Parameters for 2.4 GHz

• ~9 dB drop – Exterior Wall

• ~6 dB drop – Floor

• ~3 dB drop – interior (sheetrock) wall

• What is 5.8 GHz dB drop by wall/floor/exterior wall

Page 10: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 10

doc.: IEEE 802.11-05/0109r0

Submission

Mesh/Hand-off

• If multiple APs in adjoining/overlapping areas…– Can one be a station of another (FTTCurb scenario, AP and

STB/AP are typical scenarios)• Repeater or another AP

– Can they be in a mesh configuration?– Can there be hand-off between them

• What are considerations if Yes– Errors– Data rate change– Security and how this is handled in a hand-off– 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 11: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 11

doc.: IEEE 802.11-05/0109r0

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 12: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 12

doc.: IEEE 802.11-05/0109r0

Submission

Details

• TG efforts and standards to be evaluated as to changes needed to meet SP requirements

• Following slides cover individual issues with associated TG effort or standard

Page 13: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 13

doc.: IEEE 802.11-05/0109r0

Submission

TG/Standards that Impact Service Providers

.11i enhancedsecurity

.11v networkmanagement

.11s MeshNetworking

.11e QOS MACenhancements

.11t performancetesting

.11r fast roaming.11k radio resource

measurment

OperatorRequirements .11nHigh Throughput

Page 14: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 14

doc.: IEEE 802.11-05/0109r0

Submission

External AP reach into the home

Issue

Reach must be 150m with 20-25Mbps above the MAC measured within the home after signal penetration of "typical outside wall"

TGIssue/Resolution/Recommendation Comment

11n

Work to determine what is possible, reach is most important factor  

11n

Determine use of Beamforming versus MIMO in this context  

11n

Determine what is definition of outside wall and components of such Aluminum siding and foil faced insulation may be problematic

11n, 11e, 11tQoS to ensure confidence of service delivery  

11n, 11r, 11i, 11s, 11k, 11v, 11t

Use of AP or repeater in the home to regenerate signal and provide coverage, enable hand-off from external to internal AP

r=fast roaming (between AP and repeater), i=security, s=mesh, k=resource measurement, v=network management, t=testing

Page 15: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 15

doc.: IEEE 802.11-05/0109r0

Submission

Handoff (AP/AP/Repeater)

IssueHandoff between APs or between AP and repeater with no or minimal impact on station (ex. VoIP station crossing coverage areas)

TGIssue/Resolution/Recommendation Comment

11n, 11t, 11e, 11v, 11r, 11s, 11k

Agree on maximum allowed errors  

11n

Differentiate between repeater and second AP (Mesh) as to topology and methodology of handoff

 

11n, 11t, 11e, 11v, 11r, 11s, 11k

Adjust appropriate definitions  

 11n, 11t, 11e, 11i, 11v, 11r, 11s, 11k

 Pre-handoff authorization enabled to shorten handoff interruption time

 

Page 16: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 16

doc.: IEEE 802.11-05/0109r0

Submission

Handoff (Mobile/AP)

IssueHandoff between AP and Mobile service with no or minimal impact on station (ex. Dual mode station crossing coverage areas while in a call or idle)

TGIssue/Resolution/Recommendation Comment

Agree on maximum allowed errors for call in progress  

While on a Mobile call and shifting onto AP coverage, includes security, Mesh, fast handoff, identification, pre-handoff authorization

 

While on a WLAN call and shifting from AP to Mobile Carrier, includes security, Mesh, fast handoff, identification, pre-handoff authorization

 

  Idle set on WLAN needs to send “I am available” message to Mobile Carrier periodically

 

 AP must notify Mobile Carrier it is operational and able to make/take handoffs

Page 17: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 17

doc.: IEEE 802.11-05/0109r0

Submission

RepeatersIssue Use of Repeaters in the home, including crossover repeaters between 2.4 and 5.8 GHz

TG Issue/Resolution/Recommendation Comment

11n Define repeater  

11n

Determine data link between repeater and main AP and management of repeater by main AP

 

11n

Define radio spectrum use between repeater and main AP, and determine impact n throughput at repeater and main AP

May want reduced rate or reach at repeater to enable maximum rate/reach at main AP

11n, 11t, 11e, 11v, 11r, 11s, 11k

Frequency crossover management  

11n, 11t, 11e, 11v, 11r, 11s, 11k

Define methodology of handoff between repeater and main AP, between repeater and other repeater (2 scenarios… on same main AP or other main AP), between repeater and other main AP

 

Page 18: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 18

doc.: IEEE 802.11-05/0109r0

Submission

Video Transport Issues

IssueQoS mandated for High Data Rate applications (video primarily)

TGIssue/Resolution/Recommendation Comment

11n, 11e, 11t

Enable overair QoS to avoid artifacts in video session e=QoS enhancements, t=testing

11n, 11v, 11t

Manage LAN traffic to prevent impact of non-video related packets on video packets

t=testing, v=network management

    

    

Page 19: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 19

doc.: IEEE 802.11-05/0109r0

Submission

Mobile Wireless LAN Station Support

Issue

Support for small, random packets in weak signal areas while station is mobile (WLAN SIP sets) to eliminate Doppler Effect

TGIssue/Resolution/Recommendation Comment

11n, 11t

Enable small packet support in standard use small packet device flag to AP as describer in 11-05-1644-01-000n

    

    

    

Page 20: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 20

doc.: IEEE 802.11-05/0109r0

Submission

Handle a 2-way Mobile Video Session

IssueHow to handle mobile 2-way video session

TGIssue/Resolution/Recommendation Comment

11n, 11tDetermine packet types used  

11n, 11tDetermine Doppler Effect for weak areas  

11nDetermine how to handle  

11n, 11t, 11r, 11s, 11k, 11v, 11i, 11e

Handle fast retransmit of lost packets in streaming video  

11n, 11t, 11r, 11s, 11k, 11v, 11i, 11e

Use of 2 APs with this application 2 Stations embedded in one device?

Page 21: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 21

doc.: IEEE 802.11-05/0109r0

Submission

Encryption

Issue

Encryption to meet Content Provider concerns

TG

Issue/Resolution/Recommendation Comment

11n

Determine what needs are  

11n, 11i

Analyze needs versus existing standards  

11n

Liaise with CPs to determine agreement on means to reach satisfactory results

 

11n, 11i

Incorporate changes  

Page 22: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 22

doc.: IEEE 802.11-05/0109r0

Submission

Distance Requirement

IssueMaximize in-home distance and then determine rate

TGIssue/Resolution/Recommendation Comment

11n, 11t

Define what are in--home disturbers on 1 floor and agree on these Suggest 6 walls between AP and furthest station at 33m. Microwave ovens, refrigerators, DECT/Wireless sets @ 2.4 and 5.8 GHz

11n, 11t

Determine multi-floor coverage possibilities 1 above and 1 below, dB impact of floors and then walls

    

    

Page 23: Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document

March 2005

Brian Ford, BellSouth

Slide 23

doc.: IEEE 802.11-05/0109r0

Submission

Recommendations for Action

• Service Provider needs go beyond 802.11n

• 802.11n should be focal point as is “enabling standard”

• Requires liaison and inter-TG work to ensure complete resolution of issues– 802.11n should lead this

• 802.11n should down select then add this work as mandatory for TGn completion of its task

• WiMax not taken into account. Requires further study and decision if this is a valid focal point