1. Calibration using NDP Date: 2007-12-10 Authors: December 2006
Month Year
doc.: IEEE yy/xxxxr0
December 2006
Calibration using NDP
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
STMicroelectronics
John Doe, Some Company

2. December 2006
NDP rules
Section (D1.07) defines two simple rules about the use of NDP. The intent is to make the behavior at the transmitter/receiver always predictable:
A STA that transmits an NDP shall start the transmission of the NDP as follows:
a SIFS interval after sending a +HTC frame that does not require an immediate response with the NDP Announcement field set to 1
a SIFS interval after successfully receiving a correctly formed and addressed immediate response to a +HTC frame that requires an immediate response with the NDP Announcement field set to 1
On the receiver side this means that:
if a STA receives a +HTC frame with NDP set and Normal ACK policy, it expects an NDP within a SIFS from the response (i.e. after the ACK)
if a STA receives a +HTC frame with NDP set and No ACK policy, it expects an NDP within a SIFS from the current received frame
STMicroelectronics

3. Issue related to NDP rules
December 2006
Issue related to NDP rules
In the procedure in Figure-n55 (section ) STA A doesn't respect the rule 2):
Even if the frame with Calibration Position=1 (i.e. Cal Start) has the NDP flag set and requires Immediate ACK, the NDP is not sent by STA A within a SIFS from the ACK
STMicroelectronics

4. RDG rules Section 9.14.3 says: December 2006
"After transmitting a PPDU containing one or more +HTC MPDUs in which the RDG/More PPDU field set to 0, the RD responder shall not transmit any more PPDUs within the current response burst.“
STMicroelectronics

5. December 2006
Issues related to RDG
In the procedure in Figure-n55 STA B sets the RDG/More PPDU bit to zero in its ACK frame, and according to the rule described above, it shouldn’t be allowed to send any other PPDU (i.e. NDP from STA B is not allowed)
Why to require an optional feature (i.e. RDG) to implement another optional feature (i.e. Calibration)? It seems that we are adding an unnecessary complexity
STMicroelectronics

6. A slightly new approach
December 2006
A slightly new approach
We suggest to re-consider the definition of sounding frame in case of NDP:
At least from a MAC perspective, a +HTC frame with NDP and No-ACK policy followed by an NDP frame within a SIFS is a "single" frame (obviously this implies that the Duration/ID value in the +HTC frame must cover the following NDP)
According to this new definition, we don't need to use RDG since the response from STA B in Figure-n55 is not a response burst any more but just a single MAC frame
STA A can now use SIFS instead of PIFS (there is no need for RDG error recovery) thus respecting the rule 2) in section
The frame exchange sequence doesn’t need to be changed and the overall procedure is simplified
STMicroelectronics

7. New proposal for Calibration using NDP
December 2006
New proposal for Calibration using NDP
Non NDP + HTC
NDP announcement bit = 1
ACK Policy: Normal
Calibration Position = 1
TRQ = 1 (i.e. sounding request)
No need for RDG
Non NDP + HTC
ACK Policy: No ACK
Calibration Position = 3
QoS Null + HTC
Calibration Start
NDP
QoS Null + HTC
Sounding Complete AP
SIFS
SIFS
SIFS
SIFS
ACK + HTC
NDP
QoS Null + HTC MA
CSI Feedback
STA
Non NDP + HTC
Calibration Position = 2
NDP announcement bit = 1
Non NDP + HTC
MA = 1 (i.e. Management Action frame)
At MAC level this is a single response frame
STMicroelectronics