1. 802.11 TGn Beamforming and Adaptation Ad hoc - Calibration-
May 2006
doc.: IEEE /0528r0
Nov 2006
TGn Beamforming and Adaptation Ad hoc - Calibration-
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
Tomoya Yamaura (Sony)
Bruce Kraemer, Marvell

2. May 2006
doc.: IEEE /0528r0
Nov 2006
Abstract
I presented 06/1411r2 at Portland, to improve calibration related texts.
Then, we update it and r3 was posted
This document summarize proposed changes, and further discussion
Referred document
TGn draft D1.05
06/1411r2, and r3 (our proposal to modify calibration specification)
06/0541r11 (Solicited comment spreadsheet)
Tomoya Yamaura (Sony)
Bruce Kraemer, Marvell

3. Re-cap of proposed changes in 1411r2
Nov 2006
Re-cap of proposed changes in 1411r2
Clean-up informative text at (introduction of calibration)
Improved procedural description in (procedure for calibration)
Add capability description
Modify Calibration Sequence to fix within existing rule
Add Calibration Sequence definition using NDP
As a result of requested change above…
Modify rules of NDP to have one exception
Add “Channel Bandwidth” for “Reciprocity Correction” and “MIMO Reciprocal Channel Measurement”
Change definition of PCAL
Have a two separate subfields of “Calibration Complete” and “Channel Width” in MIMO Control field, instead of dual use.
Change the meaning of “Segment Sequence” to decremental manner, and describe this is also used for CSI FB and Non-Compressed Steering FB.
Tomoya Yamaura (Sony)

4. Differences from 06/1411 r2 to r3 [1]
Nov 2006
Differences from 06/1411 r2 to r3 [1]
Completely remove “Reciprocity Correction” and “MIMO Reciprocal Channel Measurement”
As a result, Calibration Sequence also updated.
This may bring procedural problem, explained later.
Change MIMO Control field
Remove “Calibration Complete” and “Calibration Sequence” subfields
“Calibration Sequence” subfield in HTC still exists.
Have a two separate subfields of “Coefficient Size” and “Codebook Information”, instead of dual use.
This is not related calibration, but handling at once would make thing easier for the editor.
Remove “Explicit Channel Feedback” subfield, because it is not necessary anymore.
Rename “Segment Sequence” to “Remaining Matrix Segment”
Meaning is the same as proposed in 1411r2.
As a result of them, I added many editorial changes.
Change the meaning of “Segment Sequence” to decremental manner, and describe this is also used for CSI FB and Non-Compressed Steering FB.
Tomoya Yamaura (Sony)

5. Differences from 06/1411 r2 to r3 [2]
Nov 2006
Differences from 06/1411 r2 to r3 [2]
Add definition PCAL of for 1 stream.
Change description regarding sounding dimension from
The number of long training field to obtain MIMO channel estimation sent in the sounding PPDU should be determined by N_{TX} at the STA transmitting the sounding frame. To
The number of long training fields used to obtain MIMO channel estimation that are sent in the sounding PPDU shall be determined by the number of transmit chains, NTX, used in sending these long training fields at the STA transmitting the sounding PPDU. The transmit chains used at the calibration initiator are those for which calibration is required.The calibration responder may train up to maximum available transmit chains to maximize the quality of the resulting calibration, though the number of spatial time stream for data symbols shall be determined by the rule described in 9.6.
Tomoya Yamaura (Sony)

6. Differences from 06/1411 r2 to r3 [3]
Nov 2006
Differences from 06/1411 r2 to r3 [3]
Add description to explicitly indicate same antenna index shall be used during calibration receiving sounding and transmitting sounding;
The row order in the CSI feedback matrix transmitted from STA B shall correspond to the association of the rows of the spatial mapping matrix (21-71) to its transmit antennas. For example, the receive antenna at STA B associated with the i-th row in the CSI feedback matrix in each subcarrier is the same as its transmit antenna associated with the i-th row in the spatial mapping matrix used for transmitting the sounding response with Calibration Position set to 2.
Try to fix editorial bugs (in D1.05 and 1411r2)
Tomoya Yamaura (Sony)

7. Proposed Calibration Sequence [1]
Nov 2006
Proposed Calibration Sequence [1]
Tomoya Yamaura (Sony)

8. Proposed Calibration Sequence [2]
Nov 2006
Proposed Calibration Sequence [2]
Tomoya Yamaura (Sony)

9. Discussing items To resolve CID#7371, we proposed as follows.
Nov 2006
Discussing items
To resolve CID#7371, we proposed as follows.
TGn Editor: Change paragraph starting from line-52, page-143 (under ) to the following;
Only the current TXOP holder or RD responder may transmit an NDP. A TxOP holder shall not set to 1 the NDP Announcement and RDG/More PPDU fields simultaneously, except for during calibration sounding exchange. An RD responder shall not set to 1 the NDP Announcement and set to 0 the RDG/More PPDU fields simultaneously.
Removing CSD issue
The calibration responder shall not remove the spatial mapping from the CSI to be fed back to the initiator of the frame exchange. Before computing the correction matrices, the calibration initiator of this frame exchange shall itself be responsible for accounting for the spatial mapping in both its local channel estimate as well as in the quantized fed back to it.
Tomoya Yamaura (Sony)

10. Explicit Channel Feedback
Nov 2006
Need your input [1]
Now, MIMO Control field would be;
Many reserved bits at separated location.
Can we re-order these subfield, such as; B0 B1 B2 B3
B B5 B6 B7
B B9
B B11
B B13
B14
B15
1 octet
4 octet
Nc Index
Nr Index
Calibration Sequence
Reserved
Calibration Complete / Channel Width
Explicit Channel Feedback
Grouping (Ng)
Coefficient Size / Codebook Information
Reserved Codebook Information
MCMR Remaining Matrix Segment Sequence
Sounding Timestamp ? B0 B1 B2 B3 B4
B B6
B B11
B B9
B B15
1 octet
4 octet
Nc Index
Nr Index
Channel Width
Grouping (Ng)
Coefficient Size
Codebook Information
Reserved
Remaining
Matrix
Segment
Sounding Timestamp
Tomoya Yamaura (Sony)

11. Nov 2006
Need your input [2]
“Remaining Matrix Segment” shown previous slide has 1 octets, but actually, it need only two bits.
Can we use “Reserved” bits instead of 1 octet ?
If we do so, which “reserved” bit ?
After removing “MIMO Reciprocal Channel Measurement” and “Reciprocal Correction”, HT Action field value would become the left table. Can we re-order it as right table ?
Action field Value
Meaning
Notify Channel WIdth 1
SM Power Save 2
PSMP action frame 3
Set PCO Phase 4
Reserved 5 6
MIMO CSI Matrices 7
MIMO Non-compressed Steering 8
MIMO Compressed Steering 9
Ant. Selection Indices Feedback
10-255
Action field Value
Meaning
Notify Channel WIdth 1
SM Power Save 2
PSMP action frame 3
Set PCO Phase 4
MIMO CSI Matrices 5
MIMO Non-compressed Steering 6
MIMO Compressed Steering 7
Ant. Selection Indices Feedback
8-255
Reserved ?
Tomoya Yamaura (Sony)

12. Resolved Comments [1] Nov 2006
6797, 7278 : require better other frame sequence definition for calibration
Counter. Different frame exchange sequence is defined as shown in 06/1411r3.
7140, 660, 1235, 2257, 2258, 4222, 2680, 3967, 11893, 11905: require better expression, and/or to add missed specification
Counter. Clearer text is provided as shown in 06/1411r3
7661: Figure is too busy
Counter. Simplified figures are provided as shown in 06/1411r3.
661, 4637, 7906, 7919, 10075, 722: related to the definition of “Reciprocity Correction”
Counter. “Reciprocity Correction” is removed entirely as shown in 06/1411r3.
2269: Move procedural description to clause 9
Counter. Conceptually accepted for calibration related subclause in general, but specified text in this comment is removed, because “Reciprocity Correction” is removed
Tomoya Yamaura (Sony)

13. are now assigned to Frame Format ad hoc.
Nov 2006
Resolved Comments [2]
7371 : requires to allow NDP for all STAs
Counter. The rule for allowing NDP from responder during calibration is added as shown in 06/1411r3.
But it is only during calibration,
1236, 2268, 3810, 7820: require better expression, and/or to add missed specification
Counter. “Reciprocity Correction” is removed entirely as shown in 06/1411r3.
3973: requires the definition of MIMO Reciprocal Channel
Note: CID# 1236, 2268, 3810, 7820, 660, 1235, 2257, 2258, and 4222
are now assigned to Frame Format ad hoc.
Tomoya Yamaura (Sony)

14. Resolved Comments [3] Nov 2006
Comments listed here (related to Reciprocity Correction) are already resolved and their resolutions are APPROVED by TGn.
1237, 2263, 2266, 2267, 3811, 4223, 4224, 4225, 4749, 5648, 5650, 5651, 5652, 5653, 7249, 7599, 7821, 8774, 8778, 10169, 11393, 11394, 11395,
Comments listed here (related to MIMO Reciprocal Channel Measurement) are already resolved and their resolutions are APPROVED by TGn.
2250, 2251, 2252, 2253, 2255, 2256, 2259, 2260, 2261, 2262, 2264, 3805, 3806, 3807, 3809, 4217, 4218, 4220, 4221, 7130, 7818, 7819,
However, 06/1411r3 proposed to remove subclauses related to these comments.
I guess we need another motion to replace approved resolutions, such as
Move to replace approved resolutions to comments listed below with “ Counter. Quoted subclauses are removed as shown in 1411r3. List of CIDs…. ”
Tomoya Yamaura (Sony)