1. Waveform Generator Update– September ‘06
July 2006
doc.: IEEE /0xxxr0
Sep 2006
Waveform Generator Update– September ‘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. Phy Transmitter waveform generator
Sep 2006
Phy Transmitter waveform generator
Micha Anholt - Metalink
Micha Anholt,Metalink

3. Sep 2006
Outline
Describe waveform generator plan from July that got unanimous agreement based on document 1096
Proposal for Interface and usage
Present options on how to relate the generator to the specification
Further course of action.
Micha Anholt,Metalink

4. Waveform generator plan from the San Diego meeting
Sep 2006
Waveform generator plan from the San Diego meeting
Project description from document 1096
Matlab based code
Implement all n phy modes, including legacy a modes.
Support debug vectors for intermediate signals
Progress from July to September
Methods to link the code to the spec have been explored.
Offline discussions among the phy adhoc members have been made about how to implement the code.
Micha Anholt,Metalink

5. Interface-general Command line based. (Gui available as extension).
Sep 2006
Interface-general
Command line based. (Gui available as extension).
Input – complete information on how to generate the packet.
Wherever possible and appropriate structure of input will follow TXVECTOR fields. (Suggested by Krishna Pillai)
Output – sample files, debug vectors
Sample files at 20/40/80 Mhz for all antennas
Debug vector as a structure representing a tree. (Based on suggestion by Anuj Batra)
Micha Anholt,Metalink

6. Interface-input(1) Format – Legacy,MM,GF
Sep 2006
Interface-input(1)
Format – Legacy,MM,GF
Input bits file name or auto-generate randomly
Channel bonding configuration
Ht SIG parameters
Number of transmit antennas
Micha Anholt,Metalink

7. Sep 2006
Interface-input (2)
L_Length can be supplied externally or calculated automatically
Output rate: 20/40/80 Mhz
Reserved bits
Setting the reserved bits to other than their default can be useful for testing purposes.
Spatial expansion parameters
Calibration packet – here Q matrix will be generated internally to comply with calibration packet
Use Q matrix from spec examples
Fixed matrix, same for all carriers + cdd. Suitable for spatial expansion when not using BF.
Explicit Q matrix, different for every carrier. Suitable for BF.
Micha Anholt,Metalink

8. Options on how to relate the code to the specification?
Sep 2006
Options on how to relate the code to the specification?
Explicit text
(~2000 lines -> much less than 100 pages )
Matlab code would be outlined as one long text piece.
Strong affiliation of the code to the spec.
IEEE download
Mention the link in the spec
Binary files can be added, gui interface.
Easy to update the code, without changing the spec.
This method had a strong majority within the PHY adhoc
Need to find out how to submit it.
External download
Same as the channel simulator
No need to discuss the code within IEEE.
Micha Anholt,Metalink

9. Sep 2006
Further steps
Continue to explore the technicalities of how to affiliate with the spec
Detailed interface presentation.
Propose code that will be functionally verified by the group
Review the code itself
Micha Anholt,Metalink