Presentation on theme: "Doc.: IEEE 802.11-05/0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for 802.11n Detailed Notice: This document."— Presentation transcript:
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 1 Service Provider Requirements for n Detailed Notice: This document has been prepared to assist IEEE 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 Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at.http:// Date: Authors:
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 2 Abstract This document expands on presentation n. This document provides areas within that must be considered as to market impact of weaknesses in standard definition. The primary focus is n as this enables a true wireless high throughput triple play. An n 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.”
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 3 List of Contributors/Supporters John Egan, Infineon, Fanny Mlinarsky, Azimuth Systems,
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 4 Background slides Following slides recap needs presented in n 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 n-based systems –SPs have specific concerns as listed
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 5 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 n 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 n, 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 6 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 7 Example of Requested Evaluation Points Signal Distance & Drop - Exterior Composition and dB impact?
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 8 Example of Requested Evaluation Points Signal Distance & Drop - Interior Up to 6 walls?
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 9 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 10 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 11 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 12 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 13 TG/Standards that Impact Service Providers
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 14 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" TG Issue/Resolution/RecommendationComment 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 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 15 Handoff (AP/AP/Repeater) Issue Handoff between APs or between AP and repeater with no or minimal impact on station (ex. VoIP station crossing coverage areas) TG Issue/Resolution/RecommendationComment 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 16 Handoff (Mobile/AP) Issue Handoff 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/RecommendationComment 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 17 Repeaters Issue Use of Repeaters in the home, including crossover repeaters between 2.4 and 5.8 GHz TG Issue/Resolution/RecommendationComment 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 18 Video Transport Issues Issue QoS mandated for High Data Rate applications (video primarily) TG Issue/Resolution/RecommendationComment 11n, 11e, 11t Enable overair QoS to avoid artifacts in video sessione=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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 19 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 TG Issue/Resolution/RecommendationComment 11n, 11t Enable small packet support in standarduse small packet device flag to AP as describer in n
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 20 Handle a 2-way Mobile Video Session Issue How to handle mobile 2-way video session TG Issue/Resolution/RecommendationComment 11n, 11t Determine packet types used 11n, 11t Determine Doppler Effect for weak areas 11n Determine 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 application2 Stations embedded in one device?
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 21 Encryption Issue Encryption to meet Content Provider concerns TG Issue/Resolution/RecommendationComment 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
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 22 Distance Requirement Issue Maximize in-home distance and then determine rate TG Issue/Resolution/RecommendationComment 11n, 11t Define what are in--home disturbers on 1 floor and agree on theseSuggest 6 walls between AP and furthest station at 33m. Microwave ovens, refrigerators, DECT/Wireless 2.4 and 5.8 GHz 11n, 11t Determine multi-floor coverage possibilities1 above and 1 below, dB impact of floors and then walls
doc.: IEEE /0109r0 Submission March 2005 Brian Ford, BellSouthSlide 23 Recommendations for Action Service Provider needs go beyond n n 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 n 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