1. BOF on waveform generator – July ‘06
doc.: IEEE /0xxxr0
July 2006
BOF on waveform generator – July ‘06
Date:
Authors:
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 < 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 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
Micha Anholt,Metalink
Micha Anholt,Metalink

2. BOF on Phy Transmitter waveform generator
July 2006
BOF on Phy Transmitter waveform generator
Micha Anholt - Metalink
Micha Anholt,Metalink

3. July 2006
Purpose
Fill in the gap for transmit waveform examples as in Annex G A
Improve standard comprehensibility by creating implementation examples. Those examples create a unambiguous interpretation of the standard.
Micha Anholt,Metalink

4. Scope Informative (not normative) part of the spec.
July 2006
Scope
Informative (not normative) part of the spec.
Source code supporting all n phy modes mandatory and optional, including legacy a modes.
No mac elements. At least until phy part is complete.
Micha Anholt,Metalink

5. Why all phy modes? Because we can!!! (It’s only software)
July 2006
Why all phy modes?
Because we can!!! (It’s only software)
So that no feature is discriminated by not getting into the code.
Micha Anholt,Metalink

6. July 2006
Open questions
How is the waveform generator source code going to become a part of the standard?
This is TBD. The chair will investigate
Since the standard is distributed electronically this should not be a big issue.
Micha Anholt,Metalink

7. Proposed course of action
July 2006
Proposed course of action
Get feedback from members during this meeting.
Get support by means of straw poll in the current meeting.
Prepare a submission by next IEEE meeting with a complete implementation for review by the interested group. **
Review the proposal in the next IEEE meeting and submit to TGn as part of the standard.
Micha Anholt,Metalink

8. Implementation description
July 2006
Implementation description
Matlab based
This is a commonly used language among engineers working in this field.
Input – all packet parameters
Optional inputs :intermediate signals requested
Output – samples at 20Mhz/40Mhz according to the defined mode.
Optional output: intermediate signal in their appropriate representation.
Micha Anholt,Metalink

9. July 2006
Straw poll
Are you in principle in favor of a phy tx waveform generator added as an informative annex to the standard
Yes 29
No 0
Abstain 5
Micha Anholt,Metalink