May 200 5 Motor ola, Nokia Slide 1 doc.: IEEE 802.11-05/0433 Submission Handsets requirements for TGn 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 <stuart . kerry @ philips .com > 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-05-16 Author Name Company Address Phone Email Marc de Courville Markus Muck MOTOROLA Gif-sur-Yvette 91193 France +33 1 69352518 Marc.de. Courville @ motorola .com Markus.Muck@ motorola .com Nico van Waes NOKIA 6000 Connection Dr, Irving TX +1 9728945669 Nico. vanWaes @Nokia. com Dongjun Lee Youngsoo Kim SAMSUNG Mt. 14-1 Nongseo-Ri, Giheung-Eup,Yongin-Si, Gyeonggi-Do, Korea 449-712 +82 312809614 djthekid . lee @samsung. com KimYoungsoo @samsung. com
18
Embed
Doc.: IEEE 802.11-05/0433 Submission May 2005 Motorola, Nokia, SamsungSlide 1 Handsets requirements for TGn Notice: This document has been prepared to.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
May 2005
Motorola, Nokia, Samsung
Slide 1
doc.: IEEE 802.11-05/0433
Submission
Handsets requirements for TGn
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-05-16Author
Name Company Address Phone Email
Marc de CourvilleMarkus Muck MOTOROLA Gif-sur-Yvette 91193 France +33 1 69352518 [email protected]
■ Be alliance agnostic■ Focus only on technical requirements, not solutions■ Provide a framework and requirements to help put
into perspective the technical solutions provided to the TGn body with respect to specific handset usage models
May 2005
Motorola, Nokia, Samsung
Slide 3
doc.: IEEE 802.11-05/0433
Submission
Why care about handsets in 11n? Handsets will be the dominant WiFi platform within a few years Relegating handsets to the use of legacy WiFi will delay the
adoption rate of 11n
Requirements to support handsets are modest (not delay-inducing)
Why 11n: new project would completely miss market and raise interworking issues
May 2005
Motorola, Nokia, Samsung
Slide 4
doc.: IEEE 802.11-05/0433
Submission
Multi-mode handsets The trend in handsets is towards the combination of multiple air-interfaces to
cover the widest spectrum of throughput vs distance and connectivity to other platforms.
11n will not fill the entire needed capability space and is no threat to other air interfaces (no one size fits all)
Addition of 11n to handsets is a natural fit from both a capability and interconnectivity viewpoint
Handsets device size constraint Motivation: handsets (phone/PDA) will play a major role in the internet
anywhere anytime vision Constraints: reduce number of antennas to
■ allow to reduce overall cost and power consumption of the device (analog RF-FE)■ account for device size limitation (7cm x 4cm)
TGn needs to be scalable enough to address AP and mobile STA in an evolutionary manner
Asymmetric antenna configuration is a must
Projections:■ 1 antenna immediate and long term
low end solutions■ 2 antennas handsets: 2007-2008■ 3-4 antennas handsets (high end
PDA with larger screen): 2012
May 2005
Motorola, Nokia, Samsung
Slide 6
doc.: IEEE 802.11-05/0433
Submission
Robust lower rates for extended range Benefit from spatial
diversity: provides a link budget gain that can be used to
■ Either increase the peak data rate
■ Extend the range of coverage of classical legacy 11a/g transmission modes
Note: ■ range extension is by no
means targeting WMAN coverage (wide area), it remains for the local area business (50% increase with 2x2 solutions)
May 2005
Motorola, Nokia, Samsung
Slide 7
doc.: IEEE 802.11-05/0433
Submission
3 environments of interest for handsets:■ enterprise: lower infrastructure cost with fewer access
points for covering the same area while serving more connections (cat5e cable, labor, equipment saving)
■ home: achieve full home coverage with one access point, having 11n handsets performing e.g. VoIP telephony bridging on ADSL
■ limited outdoor (hotspot): as extension of the home or to provide solution to be coupled with 3G services
Environments considered for range extension
May 2005
Motorola, Nokia, Samsung
Slide 8
doc.: IEEE 802.11-05/0433
Submission
Challenges to grant range extension 4 main features need to be ensured
■ Ensure presence of PHY modes that • enables enough coverage for target packet error rate envisaged for handset applications: VoIP,
video streaming• do not strive for highest rates, allow a number of spatial streams lower than the number TX
antennas!■ Enable association at extended range (ER): legacy beacon doesn’t allow extended range
stations to associate■ Coexistence: if these PHY modes are not mandatory then MAC protection mechanisms
will be required to allow peaceful coexistence of extended/normal range (ER/NR) stations
■ Enable robust signaling: define an 11n specific signal field or extension of current legacy one that enables stations at a larger range to be able to understand the parameters of the incoming packets
Preambles SIG Data
The parameter definitions must be available for both, NRand ER devices
Data symbols are NR/ER mode dependent
Preambles are identical for NR/ER modes
AP
ER-STAs
NR-STAs
ER-STAs
ER-STAs
May 2005
Motorola, Nokia, Samsung
Slide 9
doc.: IEEE 802.11-05/0433
Submission
Power consumption Power consumption is THE critical factor in handset
capabilities■ Battery capacity is small (~1Ah)■ Heat dissipation is difficult■ Customer perception does not favor frequent recharging
Scope of 11n PHY naturally creates new challenges due to increased number of transceiver chains and data speeds
MAC protocols should be evaluated to examine where power efficiency can be improved or at least less deteriorated.
■ Aggregation mechanisms are prime candidates
May 2005
Motorola, Nokia, Samsung
Slide 10
doc.: IEEE 802.11-05/0433
Submission
Multi-receiver aggregation I Avoiding (blind) multi-receiver aggregation e.g. 11e APSD:
■ Minimal bandwidth efficiency■ Minimal power consumption
Using (blind) multi-receiver aggregation:■ Maximum bandwidth efficiency■ Maximum power consumption
Above mutually exclusive benefits can both substantially be achieved by resource announcements in multi-receiver aggregates
■ Allows devices without data in aggregate to stop receiving■ Allows devices with data in aggregate to receive only part of the
aggregate■ Allows reverse link scheduling for increased reverse link efficiency
in both power and throughput
May 2005
Motorola, Nokia, Samsung
Slide 11
doc.: IEEE 802.11-05/0433
Submission
Multi-receiver aggregation II
Example of power consumption vs time
Listen Rx TxSIFS SIFS RxACK
Listen Rx aggregate with or without address list Tx RxACK