27
March 2 005 Brian Ford , Bel Slide 1 doc.: IEEE 802.11-05/0109r3 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 [email protected] CharlesCook Q w est 1801 California Street 26th Floor D enver,CO 80027 (303)896-5652 [email protected] Bob R. M iller A T& T Florham Park, N J 973-236-6920 [email protected] Authors:

Doc.: IEEE 802.11-05/0109r3 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/0109r3 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/0109r3

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]

Bob R. Miller AT&T Florham Park, NJ 973-236-6920 [email protected]

Authors:

Page 2: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Abstract

This presentation expands and provides details on presentation 11-05-1644-01-000n regarding Service Provider concerns over weaknesses/gaps within 802.11 that have negative market impact.

The presentation’s primary focus is 802.11n as it enables a true wireless triple play of voice, data and video delivery. If 802.11n does not address the issues listed, there will be a negative impact on Service Providers supplying the network link in high throughput applications.

Resolving the weaknesses should be considered a major component of achieving “Broad Market Potential” and a truly “market-enabling standard.”

Not resolving the issues will lead to proprietary solutions being promoted into the market, the opposite goal of a standards effort.

Page 3: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

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

• Larry Green, [email protected]

• L. Ji, [email protected]

• W. T. Marshall, [email protected]

• Fanny Mlinarsky, [email protected]

• H. R. Worstell, [email protected]

Page 4: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

What do Service Providers need (in priority order)

Highest possible consumer satisfaction… if WLAN doesn’t work faultlessly consumers blame Service Provider or set provider

1. QoS - primary requirement – video and high throughput data sessions (possibly pedestrian-speed mobile)1. Streaming, high data rate video delivery, error free, with WLAN bandwidth priority

2. Management capability of WLAN resources/bandwidth3. Reach versus rate, surrender some rate to get best reach

1. Longer Range with high data rate to enable extended range applications• Target reach/rates ~150m@45 Mbps and ~300m@25 Mbps

4. Mobility support1. Reduce Doppler Effect – ex. support for WLAN sets in pedestrian speed sessions2. Handoff3. Mesh4. Tight integration with mobile services to support IMS/MMS

5. Validate Encryption meets Content Provider requirements6. Testability of any functionality to ensure qualification and certification

► 802.11 action eliminates the need for proprietary solutions, boosts the market

Page 5: Doc.: IEEE 802.11-05/0109r3 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/0109r3

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 6: Doc.: IEEE 802.11-05/0109r3 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/0109r3

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 7: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Estimate Signal Drop Parameters for 2.4 & 5 GHz

• Estimated drops at 2.4 GHz, do we use these?– ~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

• Small cell outdoor environment also requires further characterization

Page 8: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Single Family Unit

TreeTree

Curb side or polemounted AP

150m500 ft

30m/100 ft

300m1000 ft

Is Multi-Dwelling Support Possible?• Curb-side or pole mounted AP

• Few barriers (trees) in the way

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

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

• Service Radius to dwelling Point of Presence goals

– 150m @ target 45 Mbps over MAC

– ~300m @ 25 Mbps over MAC

• Initiate further study to determine if 802.16 is valid option versus 802.11 for external applications

Page 9: Doc.: IEEE 802.11-05/0109r3 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/0109r3

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 10: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Mesh/Hand-off/Overlap

• If multiple APs in adjoining/overlapping areas…– Can one AP 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?• BSS coverage shaping via channel/Tx power/direction assignment • Data forwarding path

– Can there be hand-off between them• What are considerations if Yes

– Errors, high error rate, even at fast handoff, is unacceptable– 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

– Interference between APs on unassociated LANs in MDU environment with overlapping coverage areas

Page 11: Doc.: IEEE 802.11-05/0109r3 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/0109r3

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, QoS between APs and Mesh

Page 12: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Details

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

• Following slides cover issues with associated TG following the priority order established earlier, although management is across all aspects

Page 13: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

TG/Standards that Impact Service Providers

.11i enhancedsecurity

.11v networkmanagement

.11s MeshNetworking

.11e QOS MACenhancements

.11t performancetesting

.11w SecurityManagement

Frames

.11r fast roaming

.11k radio resourcemeasurement

Service ProviderRequirements .11nHigh Throughput

Page 14: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

QoS Metrics

Issue Set QoS requirements for application/session types

TG Issue/Resolution/Recommendation Comment

11n, 11e, 11t Delay, jitter, error rates by application

11n, 11eQoS for high traffic environments to ensure no artifacts on video, etc.

Must be interference immune

11n, 11e QoS versus HandoffMust mandate no reduction in QoS below a defined level

11n, 11e, 11t  QoS for small packet with forwarding rate and throughput  

11n, 11e, 11k QoS/BW management for multi-AP environment where each one is on a separate LAN, unable to be co-managed

 Example is Multi-Dwelling Unit (MDU) where each apartment dweller has an 802.11n WLAN. QoS for each apartment owner’s video streams, etc. is required.

Page 15: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Video Transport Issues

Issue QoS mandated for High Data Rate applications (video primarily)

TG Issue/Resolution/Recommendation Comment

11n, 11e, 11t

Enable overair guaranteed, not prioritized QoS to avoid artifacts in video session. Dynamic polling by AP based on real-time video

traffic volume dynamics not a pre-determined static schedule

e=QoS enhancements, t=testingCurrent 11e HCCA QoS scheme only supports statically scheduled polling by AP, which is not well suited for (compressed) video streams whose instantaneous data rate may vary greatly at different times

11n, 11v, 11tManage LAN traffic to prevent impact of non-video related packets on video packets

t=testing, v=network management

    

    

Page 16: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Handle a 2-way Mobile Video Session

Issue How to handle mobile 2-way video session

TG Issue/Resolution/Recommendation Comment

11n, 11t Determine packet types used  

11n, 11t Determine Doppler Effect for weak areas  

11n Determine how to handle and QoS  

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

Handle fast retransmit of lost packets in streaming video. Special transmission profile for special application classes

 May need special adaptive link layer data transmission redundancy/recovery mechanism tailored for special application classes

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

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

 11n Set application flags for packet type, not by device

 By making this application registration of packet type versus device, enables multi-function device definition with best WLAN performance

Page 17: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Mobile Wireless LAN Station Support

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

TG Issue/Resolution/Recommendation Comment

11n, 11t Enable small packet support in standarduse small packet device flag to AP as describer in 11-05-1644-01-000n

11r, 802.21Additional link layer triggers exposed for network layer mobility mechanisms such as Mobile IP  

 11n, 11t  Handling jitter and errors  Set threshold for acceptable performance

 11n Set application flags for packet type, not by device

 By making this application registration of packet type versus device, enables multi-function device definition with best WLAN performance

Page 18: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Distance Requirement

Issue Maximize in-home distance and then determine rate

TG Issue/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 possibilities1 above and 1 below, dB impact of floors and then walls

11n  Define target maximum outdoor coverage radius

Requires balance of user expectation of performance, technical viability, and economics (e.g. wireless + FTTC bundled costs)

     

Page 19: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

Large Area Deployment Support

Issue Maximize in-home distance and then determine rate

TG Issue/Resolution/Recommendation Comment

11n, 11e, 11k, 11v

Coordination function for Co-channel BSSs, what and how.

Limited available spectrum may not be sufficient to create enough spatial separation to avoid interferences among nearby co-channel BSSs. Current TGs focus on intra-BSS operations. Additional services and access to services needed for coordination function.

11k, 11vMeasurement based automatic configuration of radio (channel, power, etc)

     

     

Page 20: Doc.: IEEE 802.11-05/0109r3 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/0109r3

Submission

External AP reach into the home

IssueReach must be 150m @4 5 Mbps and 300m @25 Mbps above the MAC measured within the home after signal penetration of "typical outside wall"

TG Issue/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 suchAluminum siding and foil faced insulation may be problematic

11n, 11e, 11t QoS to ensure confidence of service delivery

 Separate access and traffic mechanisms to provide load-independent application for service, eliminate QoS traffic impacts by those wishing to enter system

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

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, w=security of management frames

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

Interoperability with legacy Wi-Fi equipmentLarge deployment of Wi-Fi equipment. How to integrate or at least co-exist

Page 21: Doc.: IEEE 802.11-05/0109r3 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/0109r3

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)

TG Issue/Resolution/Recommendation Comment

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

Agree on maximum allowed errors, jitter rate, delay  

11nDifferentiate 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, 11v, 11r, 11s, 11k, 11w

 Pre-handoff authorization enabled to shorten handoff interruption time

 

Page 22: Doc.: IEEE 802.11-05/0109r3 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/0109r3

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  

11nDetermine data link between repeater and main AP and management of repeater by main AP

 

11nDefine 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, 11w

Frequency crossover management  WLAN handover

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

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

 Determine Maximum number of hops for QoS

Page 23: Doc.: IEEE 802.11-05/0109r3 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/0109r3

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)

TG Issue/Resolution/Recommendation Comment

11r Agree on maximum allowed errors for call in progress  

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

 

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

 

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

 

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

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

March 2005

Brian Ford, BellSouth

Slide 24

doc.: IEEE 802.11-05/0109r3

Submission

Encryption

Issue Encryption to meet Content Provider (CP) concerns

TG Issue/Resolution/Recommendation Comment

11n Determine what needs are  

11n, 11w Analyze needs versus existing standards  11w is seen as extending work of 11i

11nLiaise with CPs to determine agreement on means to reach satisfactory results

 

11n, 11w Incorporate changes  11w is seen as extending work of 11i

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

March 2005

Brian Ford, BellSouth

Slide 25

doc.: IEEE 802.11-05/0109r3

Submission

Testability Requirement

• Objective test methodology for performance verification is key to enabling:– Performance optimization (if you can’t measure it, you can’t improve it)– Verification of performance requirements– Effective comparison of products from different vendors

• Design 11n devices for testability in cooperation with TGT• Important to agree on measurement methodology for

– Rate vs. range (reach)– Voice and video quality vs. range– Throughput of STAs– Forwarding rate of APs and repeaters as a function of packet size, data load and client load– Performance of voice and data services as a function of call load, AV stream load, background

data load and client load – QoS performance and QoS impact on above measurements– Security settings impact on above measurements– Handoff time– QoS vs. handoff

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

March 2005

Brian Ford, BellSouth

Slide 26

doc.: IEEE 802.11-05/0109r3

Submission

Wrap Up

• Service Provider needs go beyond 802.11n extending eventually to 4G framework

• 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

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

March 2005

Brian Ford, BellSouth

Slide 27

doc.: IEEE 802.11-05/0109r3

Submission

Actions

1. WNG assesses SP requirements1. Determine 802.11 validity by concern

1. Agree on prioritization and what is mandatory for TGn to do2. Determine what may be out of scope for 802.11

2. Recommend future action1. TGn focal points with mandatory action required to complete effort2. Appoint TGn as oversight group to manage completion of work by

other TGs3. Other TG action items4. Liaison/joint efforts between TGs or TGs and outside groups5. Refer to 802.11 any that should be for a new SG

2. TGn assumes role of responsibility for resolving issues agreed upon before TGn work completed