1. [Performance of ACI for 802.11clients]
Month Year
doc.: IEEE yy/xxxxr0
March 2005
[Performance of ACI for clients]
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
Craig Warren Azimuth Systems
John Doe, Some Company

2. Abstract Approach for Basic ACI in accordance with 802.11.
Month Year
doc.: IEEE yy/xxxxr0
March 2005
Abstract
Approach for Basic ACI in accordance with
Approach for Margin testing for ACI for real world performance impact..
Craig Warren Azimuth Systems
John Doe, Some Company

3. Basic ACI Configuration
March 2005
Basic ACI Configuration
Craig Warren Azimuth Systems

4. March 2005
Basic ACI Test
ACI is associated with ACR per the abg specifications. The purpose of this test is to derive ACR “Adjacent Channel Rejection” of a client. This will be done in a controlled environment so that the transmit power can be calibrated and repeatable.
The power of the transmitter will be set per the sensitivity spec for the data rate at the DUT per Table a plus 3db for OFDM and 2 Mbps sensitivity level for CCK plus 6db.
The power of the ACI per spec for OFDM “g/a” is per table 91 in a and measure the FER-per b/ PER rate is 10% for CCK and 8% for OFDM is achieved. For CCK it is set 41db above -80 RSSI sensitivity. This measurement will now be called ACR.
Low ACI
High ACI
ACR
power
channel
Thermal noise
Frequency
Craig Warren Azimuth Systems

5. Basic ACI Procedure March 2005
Calibrate the TX power of the AP’s for the DUT and ACI. For this test, a golden 3rd party sniffer shall be utilized for measurement. The measurement will need to be done for each channel and data rate setting.
Optional method is to also use a power meter / spectrum analyzer to measure the TX power and calibrate the loss of each path to match the reported RSSI value.
For b set the rate for the AP to 2mbps with fragmentation disabled.
Set the RSSI per the spec requirements example being, for b is db above the -80 sensitivity level. Then set the ACI to 41db above that so that will be RSSI of -39dbm.
Start the traffic generator for the ACI and the DUT AP1.
Begin removing path loss until the loss is >= 35db which is a passing ACR per the spec. For a,b the requirements are driven by the data rate.
FER will be derived from the AP1 “AP being used to test the DUT” statistics as (retransmitted packets / packets sent) * 100 = FER. The AP statistics are used since that is transmitter for the DUT.
If 10% is not observed, then begin decreasing the path loss until 10% is achieved. This is now the MACR “Margin Adjacent Channel Rejection” of the client.
For this test the ACI will be set to the High channel spacing run the test. Change to the Low Channel spacing and run the test. For CCX the channel spacing for a is the channel below and above. For b spacing is +/- 30Mhz. For g the spacing is +/- 25Mhz.
Craig Warren Azimuth Systems

6. Margin ACI Configuration
March 2005
Margin ACI Configuration
Craig Warren Azimuth Systems

7. March 2005
Margin ACI test
Real world issues vs specification testing enterprise has potential for having the ability of seeing 2 or even more adjacent channels.
Cold hard fact for SoHo is even a bigger nightmare. This will have same channel jammer, 5, 10, 15 Mhz channel spacing. There is no limit to how many there can be. Argument may be that the AP’s are that coming out of the box they are looking for the least congested channel. However, legacy makes this feature not available in all scenarios and makes a case for testers and developers to understand the impact on the product and user experience.
This test is to measure the ACR margin of the client to understand the impact on performance and user experience.
Craig Warren Azimuth Systems

8. Margin ACI Procedure March 2005
Follow the same steps that the Basic ACI test has done with the exception that both the high and low channels will be active at the same time.
The ACI power will be initially as distributed per the spec. The example being for OFDM setting the RSSI level for the DUT will be db above the sensitivity for 54Mbps.
The 2 ACI jammers will be power distributed per the spec. The ACI’s combined power will be = -1db per the ODFM table.
The ACI channels will have the ability to set 5Mhz spacing for the ACI.
The test here is not to measure the 10 / 8% FER/PER as done in Basic ACI, but to find that point where the throughput impacts the user experience. The purpose of this test is to understand the impact on the application layer experience for upstream and downstream. This will help equate noise impact to video and voice.
During this test Association requests will be done as well due to noisy environment impact and measuring TTC “Time to Connect” where the time from the association request gets sent to data send or recieve.
Craig Warren Azimuth Systems

9. Metrics TTC “Time To Connect
March 2005
Metrics
TTC “Time To Connect
Throughput upstream and downstream Min, Max, Avg.
Craig Warren Azimuth Systems