Doc.: IEEE 802.11-05/0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 1 Thoughts on Modifications of the TGn Functional Requirements.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /90r0 Submission Nov., 2012 NICTSlide b NICT Proposal IEEE P Wireless RANs Date: Authors: Notice: This document.
Advertisements

Doc.: IEEE /0930r0 Submission July 2006 Nancy Cam-Winget, Cisco Slide 1 Editor Updates since Jacksonville Notice: This document has been prepared.
Doc.: IEEE /0024r0 Submission May 2006 Steve Shellhammer, QualcommSlide 1 Discussion of Coexistence Scenarios Notice: This document has been prepared.
Doc.: IEEE /0094r0 Submission November 2009 Steve Shellhammer, QualcommSlide 1 Comments on PAR Notice: This document has been prepared.
Doc.: IEEE /2237r0 Submission July 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D1.0 Insert and Deletion Notice: This document has been.
Doc.: IEEE /1936r0 Submission December 2006 Bruce Kraemer, Marvell Adrian Stephens, IntelSlide 1 TGn Proposed Draft Revision Notice Notice: This.
Doc.: IEEE /1528r0 Submission 22 September 2006 Naveen Kakani, Nokia, IncSlide 1 TGn PSMP adhoc Group September Closing Report Notice: This document.
Doc.: IEEE /0197r0 Submission March 2005 Nancy Cam-Winget et alSlide 1 TAP & JIT Merge Process Notice: This document has been prepared to assist.
Doc.: IEEE /2112r1 Submission Peter Loc, MarvellSlide 1 TGn LB97 Frame Format Ad Hoc San Francisco, July 2007 Notice: This document.
Doc.: IEEE /0652r1 Submission May 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D0.12 Insert and Deletion Notice: This document has been.
LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
March 2013 Opening Report Date: Authors: March 2013
IEEE White Space Radio Contribution Title
LB73 Noise and Location Categories
LB73 Noise and Location Categories
SG CUB Tentative Timeline
Waveform Generator Source Code
March 2014 Election Results
Attendance and Documentation for the March 2007 Plenary
Attendance and Documentation for the March 2007 Plenary
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
Motion to accept Draft p 2.0
November 2013 Opening Report
3GPP liaison report July 2006
(Presentation name) For (Name of group) (Presenter’s name,title)
March Opening Report Date: Authors: March 2010
On Coexistence Mechanisms
TGu-changes-from-d0-02-to-d0-03
Contribution on Location Privacy
November Opening Report
On Coexistence Mechanisms
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
July 2014 Opening Report Date: Authors: July 2014
July 2012 Opening Report Date: Authors: July 2012
Selection Procedure Recommendation
Spectrum Sensing Tiger Team
TGu-changes-from-d0-01-to-d0-02
September Opening Report
LB73 Noise and Location Categories
EC Summary of PAR Development
March 2012 Opening Report Date: Authors: March 2012
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
November Opening Report
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
TGn Proposed Draft Revision Notice
[ Policies and Procedure Summary]
November 2012 Opening Report
Draft P802.11s D1.03 WordConversion
September 2012 Opening Report
Questions to the Contention-based Protocol (CBP) Study Group
January Opening Report
EC Motions – July 2005 Plenary
TGu-changes-from-d0-04-to-d0-05
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
Selection Procedure Recommendation
May 2012 Opening Report Date: Authors: May 2012
Presentation transcript:

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 1 Thoughts on Modifications of the TGn Functional Requirements for Low Cost – Low Power Devices 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. Date: Authors:

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 2 Motivation The motivation for changing the TGn Functional Requirements is to allow for a class of lower cost, lower power devices (e.g. handhelds and printers)

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 3 Goal The Ad-Hoc committee is to develop recommended modifications to the TGn Functional Requirements which would enable such lower cost, lower power TGn devices The task group would vote to approve those changes

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 4 Suggested Process 1.Identify what class of TGn implementations are currently prevented by the Functional Requirements 2.Develop changes to the Functional Requirements to allow for these classes of implementations, while not accidentally enabling unintended consequences

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 5 Classes of Low Cost – Low Power Implementations Class 1 –Single TX RF chain and single TX antenna –Single RX RF chain and single RX antenna Class 2 –Single TX RF chain and dual (or more) TX antenna (TX antenna selection) –Single RX RF chain and dual RX antenna device (RX antenna selection) Class 3 –Single TX RF chain and single TX antenna –Dual (or more) RX RF chain and dual (or more) RX antenna (MRC)

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 6 Summary of characteristics of these classes of low cost – low power devices The identifying characteristic of these classes of devices is: –Single TX RF chain Why not use the term “Single Stream Device?” –Because single stream is not only for single TX antenna devices. So the term is too general. It could give a special exception to devices with 2 TX chains. Any decide with 2 TX chains should be able to meet the standard requirements.

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 7 Recommendation Summary Change FR1 and FR2 to allow an exception for “Single TX RF chain devices” For those class of devices change the throughput requirement from 100 Mb/s to 50 Mb/s

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 8 Recommended Change #1 Change FR1 from –“Demonstrate at least one set of conditions under which 100 Mbps at the top of the MAC SAP can be achieved. Provide all relevant information to document this” To –“Demonstrate at least one set of conditions under which 100 Mbps at the top of the MAC SAP can be achieved. Provide all relevant information to document this, with an exception for devices with only a single TX RF chain”

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 9 Recommended Change #2 Add FR1a –“For devices with only a single TX RF chain demonstrate at least one set of conditions under which 50 Mbps at the top of the MAC SAP can be achieved. Provide all relevant information to document this”

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 10 Recommended Change #3 Change FR2 from –“Proposal supports at least one mode of operation that supports 100Mbps throughput at the top of the MAC SAP in a 20MHz channel. Provide all relevant information to document this.” To –“Proposal supports at least one mode of operation that supports 100Mbps throughput at the top of the MAC SAP in a 20MHz channel. Provide all relevant information to document this, with an exception for devices with only a single TX RF chain.”

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 11 Recommended Change #4 Add FR2a –“For devices with only a single TX RF chain the proposal supports at least one mode of operation that supports 50 Mbps throughput at the top of the MAC SAP in a 20MHz channel. Provide all relevant information to document this.”

doc.: IEEE /0534r0 Submission May 2005 Steve Shellhammer, Intel CorporationSlide 12 References 1.Adrian Stephens, IEEE /813r12, TGn Functional Requirements, March 17, 2004.