TR-398 - Performance Test
TR-398 - Performance Test
TR-398
Wi-Fi Residential & SOHO Performance Testing
Issue: 2 Corrigendum 1
Issue Date: September 2021
Notice
The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network
system development and deployment. This Technical Report has been approved by members of the Forum.
This Technical Report is subject to change. This Technical Report is owned and copyrighted by the
Broadband Forum, and all rights are reserved. Portions of this Technical Report may be owned and/or
copyrighted by Broadband Forum members.
Intellectual Property
Recipients of this Technical Report are requested to submit, with their comments, notification of any relevant
patent claims or other intellectual property rights of which they may be aware that might be infringed by any
implementation of this Technical Report, or use of any software code normatively referenced in this
Technical Report, and to provide supporting documentation.
Terms of Use
1. License
Broadband Forum hereby grants you the right, without charge, on a perpetual, non-exclusive and worldwide
basis, to utilize the Technical Report for the purpose of developing, making, having made, using, marketing,
importing, offering to sell or license, and selling or licensing, and to otherwise distribute, products complying
with the Technical Report, in all cases subject to the conditions set forth in this notice and any relevant
patent and other intellectual property rights of third parties (which may include members of Broadband
Forum). This license grant does not include the right to sublicense, modify or create derivative works based
upon the Technical Report except to the extent this Technical Report includes text implementable in
computer code, in which case your right under this License to create and modify derivative works is limited to
modifying and creating derivative works of such code. For the avoidance of doubt, except as qualified by the
preceding sentence, products implementing this Technical Report are not deemed to be derivative works of
the Technical Report.
2. NO WARRANTIES
THIS TECHNICAL REPORT IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN
PARTICULAR, ANY WARRANTY OF NONINFRINGEMENT AND ANY IMPLIED WARRANTIES ARE
EXPRESSLY DISCLAIMED. ANY USE OF THIS TECHNICAL REPORT SHALL BE MADE ENTIRELY AT
THE USER’S OR IMPLEMENTER'S OWN RISK, AND NEITHER THE BROADBAND FORUM, NOR ANY
OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY USER,
IMPLEMENTER, OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLY
OR INDIRECTLY, ARISING FROM THE USE OF THIS TECHNICAL REPORT, INCLUDING BUT NOT
LIMITED TO, ANY CONSEQUENTIAL, SPECIAL, PUNITIVE, INCIDENTAL, AND INDIRECT DAMAGES.
All copies of this Technical Report (or any portion hereof) must include the notices, legends, and other
provisions set forth on this page.
Issue History
Comments or questions about this Broadband Forum Technical Report should be directed to
[email protected].
Table of Contents
List of Figures
Figure 1: Test setup for performance testing for single STA ............................................................................17
Figure 2: Single Chamber Implementation .......................................................................................................22
Figure 3: Multiple Chamber Implementation.....................................................................................................23
Figure 4: Wi-Fi Mesh Multiple Chamber Implementation .................................................................................24
Figure 5: Test Setup for Receiver Sensitivity ...................................................................................................30
Figure 6: Test setup of Maximum Connection Test ..........................................................................................33
Figure 7: Test setup of Maximum Throughput Test..........................................................................................35
Figure 8: Test setup of Airtime Fairness Test...................................................................................................37
Figure 9: Test setup Dual-band Throughput Test ............................................................................................40
Figure 10: Test setup of Range Versus Rate Test ...........................................................................................44
Figure 11: Test setup of Spatial Consistency Test ...........................................................................................47
Figure 12: Test Setup of AP Coexistence Test ................................................................................................58
Figure 13: Test setup by using TCP/UDP flows with separate Packet Generator/Analyzer ............................63
Figure 14: Test setup by using TCP/UDP flows with the dedicated testing equipment ...................................63
Figure 15: Test setup by using TCP/UDP flows with an independent STA ......................................................64
Figure 16: Test Setup by using level-2 Ethernet flows with a common Packet Generator/Analyzer ...............64
List of Tables
Executive Summary
TR-398 provides a set of performance test cases with pass/fail requirements for 802.11n/ac/ax
implementations according to Institute of Electrical and Electronics Engineers (IEEE) specification 802.11ac
[1].
The primary goal of TR-398 is to provide a standard set of test cases and framework to measure aspect of the
performance between Access Point (AP) (e.g., a CPE with Wi-Fi), one or more references Station (STA) (e.g.,
Personal Computer [PC], integrated testing equipment, etc.), and if applicable, one Wi-Fi repeater, under
controlled laboratory conditions. The test cases are defined for a Device Under Test (DUT – AP only), tested
against a or a set of STA.
Technical contents of TR-398 test plan include test setup information, equipment configuration requirements,
test procedures, and pass/fail requirements for each test case.
Issue 2 of this test plan updates a number of the test cases, adds additional test cases for mesh and Wi-Fi
roaming between APs, and the new 802.11ax technology.
Issue 2 Corrigendum 1 of this test plan makes corrections to several of the test cases, in support of the
Broadband Forum BBF.398 Grade Wi-Fi Program.
The primary goal of TR-398 Issue 2 Corrigendum 1 is to provide a standard set of test cases and framework
to measure aspects of the performance between AP (e.g., a CPE with Wi-Fi), one or more reference STA (e.g.,
PC, integrated testing equipment, etc.), and if applicable, one Wi-Fi repeater, under controlled laboratory
conditions. The test cases are defined for a Device Under Test (DUT – AP only), tested against a or a set of
STA. The DUT SHOULD NOT be a reference design and SHOULD contain the necessary system functionality
to execute this test plan (see section 5)
Technical content in this test plan includes test setup information, equipment configuration requirements, test
procedures, and pass/fail requirements for each test case. Specific manufacturer information for test and
measurement has not been included in this document, except in cases where the selection or use of alternate
equipment could negatively impact the results of the testing.
1.2 Scope
This Technical Report intends to provide a performance test plan for “IEEE standard for Information
technology-Telecommunications and information exchange between systems Local and metropolitan area
networks- Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer
(PHY) Specifications specification”. TR-398 Issue 2 Corrigendum 1 is specifically developed for 802.11n/ac/ax
compliant access point devices. The performance of Wi-Fi station (STA) is not in the scope of this project.
Wi-Fi Access Point devices are used in a wide variety of premises which contain many elements which will
influence Wi-Fi performance. TR-398 Issue 2 Corrigendum 1 is intended to address a generalized set of
performance test cases performed in a controlled laboratory environment. The performance test cases are
intended for the access point, to verify:
1) RF capability
2) Throughput performance
3) Spatial consistency
4) Airtime fairness
5) Connection capability
6) Stability/Robustness
Issue 2 of this test plan makes the following changes and provides the listed additional tests:
• Addition of testing and associated metrics for 802.11ax to all applicable test cases
• Updates to attenuation levels for tests using the “medium” and “long” distances
• New test case for “Dual-band Throughput”
• New test case for “Bidirectional Throughput”
• New test case for “Repeated Wi-Fi Performance”
• New test case for “Basic Roaming Performance”
SHALL This word, or the term “REQUIRED”, means that the definition is an absolute
requirement of the specification.
SHALL NOT This phrase means that the definition is an absolute prohibition of the
specification.
SHOULD This word, or the term “RECOMMENDED”, means that there could exist
valid reasons in particular circumstances to ignore this item, but the full
implications need to be understood and carefully weighed before choosing a
different course.
SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" means that there could
exist valid reasons in particular circumstances when the particular behavior
is acceptable or even useful, but the full implications need to be understood
and the case carefully weighed before implementing any behavior described
with this label.
MAY This word, or the term “OPTIONAL”, means that this item is one of an
allowed set of alternatives. An implementation that does not include this
option SHALL be prepared to inter-operate with another implementation that
does include the option.
2.2 References
The following references are of relevance to this Technical Report. At the time of publication, the editions
indicated were valid. All references are subject to revision; users of this Technical Report are therefore
encouraged to investigate the possibility of applying the most recent edition of the references listed below.
2.3 Definitions
The following terminology is used throughout this Technical Report.
CPE Customer Premises Equipment. In the context of this Technical Report, CPE is used
for any device or other equipment placed inside the premises of a Service Provider’s
customer.
Wi-Fi A name created and trademarked by the Wi-Fi Alliance to describe technology based
on IEEE 802.11 standards.
2.4 Abbreviations
This Technical Report uses the following abbreviations:
AP Access Point
DL Downlink
DTIM Delivery Traffic Indication Message
DUT Device Under Test
GE Gigabit Ethernet
GUI Graphical User Interface
ICMP Internet Control Message Protocol
IEEE Institute of Electrical and Electronics Engineers
IP Internet Protocol
IPv4 Internet Protocol version 4
LAN Local Area Network
MAC Medium Access Control
MCS Modulation and Coding Scheme
MIMO Multi-input Multi-output
MTU Maximum Transmission Unit
MU-MIMO Multi-user MIMO
PC Personal Computer
PER Packet Error Rate
PHY Physical Layer
QoS Quality of Service
RF Radio Frequency
SSID Service Set Identifier
STA Station
TCP Transmission Control Protocol
TR Technical Report
Tx Transmission
UL Uplink
UDP User Datagram Protocol
VLAN Virtual Local Area Network
WA Work Area
3.2 Security
TR-398 has no impact on Security.
3.3 Privacy
Any issues regarding privacy are not affected by TR-398.
4 Equipment Features
4.1 Device Under Test (DUT) and Station (STA)
The STA SHALL support a STA Southbound management protocol that is required for execution of this test
plan except as required to configure the STA to pass Ethernet traffic between the STA and Local Area Network
(LAN) interface(s).
5 Test Environment
The Wi-Fi performance test environment can easily be impacted by external factors and the environment, such
as existing office Wi-Fi systems, or nearby appliances (e.g., microwave ovens). The construction of the test
environment used by this test plan SHALL be constructed in a fashion to mitigate the impact of these external
factors. The test environment SHALL meet the requirements outlined in this section for all tests within this test
plan.
If the test case requires test traffic larger than 1 Gbps at the LAN interface, multiple Gigabit Ethernet ports
SHALL be employed to fulfill the test traffic demand in the test. In this case, identical traffic streams with same
Quality of Service (QoS) setting SHALL be injected to Gigabit Ethernet ports, respectively.
If the DUT supports Ethernet port with higher rate than 1Gbps (e.g., 2.5G, 5G, or 10G Ethernet, etc.), no
additional port is used in the testing.
Figure 1 shows the basic setup for passing Ethernet/IP traffic through the DUT and single STA. Appendix I
shows the instantiations of the test setups. The Packet Generator/Analyzer MAY be a discrete device from the
STA, or the Packet Generator/Analyzer may be embedded directly on the STA device. The Packet
Generator/Analyzer SHALL NOT be combined with the DUT and SHALL be a discrete device running the
testing software to generate/receive the packets for DUT.
Note: The Physical Layer Test Setup shown in Figure 1 contains any specific test setup(s) or
equipment that may be required within the Wi-Fi link, such as a channel simulator, attenuators, etc.
Downlink Uplink
traffic flow traffic flow
Physical
Layer
DUT STA
Test
Setup
The DUT and STA SHOULD support the following requirements to enable these tests.
Where the Packet Generator/Analyzer is used to implement the traffic throughout measurements within this
test plan, the following settings SHALL be used to configure the traffic generator. All throughput measurements
SHALL be the layer 4 (payload rate) for the TCP or UDP traffic streams.
Note: This leads to 1472 bytes Ethernet frame size. The size of the transmitted data is 1460 bytes
with 20-bytes IPv4 header and 8-byte UDP header.
The iPerf3 program runs as either a client or server process, where the server acts as a traffic
reflector/recipient, while the client is responsible for the definition of specific tests/measurements to perform
between the client and server processes. For the purposes of definitions below, the commands assume the
iPerf3 server process is running on the AP side and the client process is running on the STA side of the Wi-Fi
link. The client and server processes MAY be run on either side of the link during testing, provided the
uplink/downlink definitions are consistently maintained.
The iPerf3 server SHALL be started with the command iPerf3 --server.
Specific client commands for each test scenario are located below. An explanation of the commands follows,
for information only.
SERVER_IP address is the IP address of the system where the server is running.
TEST_TIME is the length of time the measurement will run for. This is set within each test case below.
The bitrate parameter is set to zero, to instruct iPerf3 to attempt to determine (measure) the maximum
throughput between the client and server.
The parallel parameter instructs iPerf3 to run ten measurement streams in parallel between the client and
server. This improves the overall accuracy of the measurement. The individual bandwidth used by each
stream can vary, and the summation/average is used to calculate the overall measurement.
The reverse parameter instructs iPerf3 to measure the bandwidth from the server to the client. The default
behaviour performs the measurement from the client to the server.
The udp parameter instructs iPerf3 to use the UDP transport instead of the default TCP transport.
The omit 2 parameter instructs iPerf3 to “discard” the first 2 seconds of the measurement, to avoid inclusion
of TCP slow start, etc.
Additional commands MAY be used to alter/direct logging or format of results, such as the --logfile or --json
options. However, any additional command SHALL NOT alter the operation or measurement traffic used by
the program.
The iPerf3 programs SHALL be run on a Linux based system, using a kernel version of 4.14 or newer. The
system SHALL include at least one processor, with two cores, of at least 2 GHz.
iPerf3 --client <SERVER_IP> --time <TEST_TIME> --bitrate <BITRATE> –reverse --udp --omit 2
The peer STAs are separated from the DUT by the Wi-Fi test channel. This separation can be defined as a
specific distance, or as a specific path-loss. The test report SHALL indicate how the Wi-Fi test channel is
established. The specific separation is defined in each test, however:
a. If distance is used, then the peer STA SHALL be placed at the same height as the DUT. Additionally,
the test report SHALL indicate the rotational orientation of both the STA and DUT. Both STA and DUT
SHALL be placed in their “upright” position, as defined by the manufacturers.
b. If external antenna is used, the antenna SHALL be adjusted perpendicularly to the horizontal plane.
c. If path-loss is used, then the peer STA SHALL be separated from the DUT by the equivalent free space
path loss at the working frequency. Free space path loss between isotropic antennas is expressed as
P_L (dB)=20 Log10 (f_GHz ) + 20 Log10 (d_meters ) + 32.45. For example, at 2.4 GHz the path loss
equivalent to a 1-meter separation is 40 dB, and at 5.2 GHz the path loss is 46.8 dB. The attenuation
value for testing SHALL be rounded to the nearest whole dB value.
d. A channel emulator (e.g., test equipment) MAY be used to implement the test channel.
e. If the test channel is created using attenuators or a channel emulator, the test equipment SHALL
support at least the same number of independent channels as the number of spatial streams being
tested.
f. The attenuators used to create signal attenuation SHALL perform flat attenuation in the frequency
bandwidth.
There are several important parameters and conditions that define a test configuration. These are:
• The test environment SHALL be free from interference, and,
• There is a certain path loss between the devices, and,
• There is the ability to modify that path loss in a controllable and repeatable fashion.
There are several ways that such an environment could be implemented. A few possible options are shown
below; either of these methods MAY be used to implement the testing defined within the document, or any
other method could be used as long as it can be shown to meet the requirements of these sections. To simplify
this document, each test case includes only a test setup figure or diagram based on the single chamber
implementation.
Within a shielded chamber, RF signals will reflect from the chamber walls, and can appear as interference to
the devices within the chamber. Any chamber used in the test plan SHOULD attenuate the reflections by at
least 20 dB to minimize the impact of these reflections.
In this implementation, it is anticipated the single chamber provides the required shielding to meeting the
ingress noise requirements. The chamber SHALL be large enough to meet the spacing requirements defined
in each test case.
The STA(s) SHALL have at least the same Wi-Fi physical layer capability (i.e., maximum spatial streams
supported and antenna number) as the DUT unless the test case specifies the capability of the STA used in
the test. The STA(s) MAY support physical layer capabilities exceeding those of the DUT.
The STA device(s) used for testing MAY be real products (i.e., a Laptop or Phone) or MAY be dedicated test
and measurement equipment that emulates the behavior of standard Wi-Fi station.
For tests that required multiple STA devices, the devices MAY be multiple discrete devices or the multiple
STA devices may be emulated by a single test and measurement device.
If the DUT supports multiple Wi-Fi channels, the DUT SHALL select channel 6 for 2.4 GHz frequency band
and channel 36 for 5 GHz frequency band. The test report SHALL document the channel used in the test
plan. If the channel is not supported due to regulatory issue, a neighbor channel SHALL be selected
accordingly. The peer STA/STAs register to the DUT to establish the link.
Note: A fixed channel facilitates good repeatability across the tests in labs.
DUT SHALL NOT use any proprietary implementation beyond the scope of Wi-Fi standard [1], e.g., 256QAM
modulation for 802.11n, etc.
the maximum allowed transmit power (Tx Power). Changes to the transmit power used by the DUT can
have an impact on the testing results within this test plan, where the distance and test channels are defined
as absolute attenuation values. In this context, the transmit power is the power delivered to the antenna by
the transmit power amplifier within the DUT.
The DUT SHALL be configured to use the transmit power identified within this section, along with the
indicated Wi-Fi channel. If the DUT cannot change the used transmit power for the indicated channel, the
following changes SHALL be applied to the testing.
• The testing SHALL be conducted using an alternate channel in the same band that supports the
required transmit power and channel width, as specified within the Tables 9, 10, and 11 below.
Note, any change to the Wi-Fi channel used for testing of the DUT will require corresponding
changes to channels used in the AP Coexistence Test Case.
• If an alternate channel or change to the transmit power level cannot be used for testing, the
attenuation values or separation distance used for each test case SHALL be changed by the
corresponding difference in power. For example, if the DUT only supports a maximum transmit
power of 16 dBm for 2.4 GHz (as opposed to the 20 dBm as specified in Table 9), the attenuations or
base distances used for each test case would be reduced by 4 dB. Or, if the DUT is only able to
transmit at a power of 26 dBm for 2.4 GHz (as opposed to the 20 dBm as specified in Table 9), the
attenuations or base distances used for each test case would be increased by 6 dB.
o Changes in the attenuation values or distances SHALL NOT be made to account for DUT
antenna design or performance. For example, the attenuation values would not be changed
for a DUT designed to conform to the 20 dBm power allowed in the USA regulatory domain,
where the STA is observed to report a lower than expected RSSI value, as this difference is
likely directly related to the DUT antenna performance.
• All changes to the channel or attenuator values used in the testing SHALL be documented in the
report.
Note, the above changes are intended to account for differences within the design and construction of the
DUT, as required by its intended regulatory domain, while not “tuning” the test environment to each individual
DUT, including its antenna and radiation pattern performance, which would obscure differences between the
“real world” performance of individual DUTs.
In general, only one operating band/mode is tested at a time, such as 802.11n on 2.4 GHz or 802.11ax on 5
GHz. To ensure the desired band/mode is being tested, the STA SHOULD support a configuration
mechanism to connect only in the desired band. If the STA does not support this configuration mechanism,
only the band/mode being tested SHALL be enabled on the DUT and all other bands/modes supported by
the DUT SHALL be disabled, unless otherwise directed within a specific test case.
All of the test cases in this test plan for 802.11n SHALL be conducted in the working frequency of 2.4 GHz.
The test plan for 802.11n working in 5 GHz is left for further study.
Table 11: Work setting configuration for 802.11ax (2.4 & 5 GHz band)
Configuration Parameters Default value
Tx Power 100 % (NOTE1)
Regulatory Domain (NOTE2)
Channel (NOTE 3) Channel 6 or 36
Chanel Width 20 MHz for 2.4 GHz
20/40/80 MHz for 5 GHz
6 Performance Tests
Chapter 6 includes a set of test cases for verification of Wi-Fi performance. Test cases are categorized into 5
sets (RF capability, Baseline performance, Coverage, Multiple STAs performance, and Stability/Robustness).
6.1 RF capability
6.1.1.1 Introduction
Receiver Sensitivity is a receiver’s ability to receive and correctly demodulate weak signals. This test provides
a simplified measurement of the receiver’s sensitivity, relative to the total attenuation inserted between the
DUT and the STA. As that attenuation is increased, the STA is limited to a single coding scheme, eventually
causing the connection to degrade. The point at which the connection degrades represents the receiver’s
approximate sensitivity. This is an approximate measurement only, where a detailed receiver sensitivity
measurement would typically be performed in a conducted test environment with calibrated transmitter power
levels. The test is repeated with multiple coding schemes, ensuring the DUT should smoothly transition
between coding schedules as the attenuation increases in normal operation.
6.1.1.2 Setup
1. The test setup (shown in Figure 5) SHALL utilize a shielded chamber (see section 5.2.1 and 5.2.2).
2. A Traffic Generator/Analyzer is connected to the station and DUT, capable of sending and receiving
Ethernet frames in order to measure packet error rate. A UDP link SHALL be established between DUT
and STA and traffic rate SHALL be set to 65% of the theoretical maximum throughput rate for each
Modulation and Coding Scheme (MCS). The direction of data packet is from STA to DUT.
3. A controllable attenuator is added to each RF path between the STA and DUT. The attenuator SHALL
support the attenuation values between 0 dB and 60 dB, in 1 dB steps.
4. The STA SHALL use omnidirectional antenna for packet transmission.
5. A rotation platform is used to rotate the DUT for angle-based data collection.
Fixed distance: 2m
DUT STA
Rotation platform
Test controller
1. Control of attenuators
Traffic generator 2. Configuration of traffic Traffic analyzer
3. Record of test results
2 802.11ac/80 MHz
Note: The test plan considers the common configurations to reduce the testing complexity.
6.1.1.4 Procedure
1. Set the rotation angle to 0 degree.
2. Configure the STA to use the MCS rate for the first test index from Table 13, Table 14, Table 15, or Table
16 applicable to the test configuration from Table 12.
3. Configure the Traffic Generator to use the test data rate from Table 13, Table 14, Table 15, or Table 16
for the configured MCS rate.
4. Allow STA to associate with the DUT.
5. Configure the attenuator(s) to 0 dB.
6. Enable packet generation from the STA to the DUT for 20 seconds.
7. Record packet error rate (PER).
8. Increase the attenuator by 1 dB and repeat steps 6-8 until the PER is greater than 10%. Record the final
attenuation value as the approximate receiver sensitivity.
9. Increase the rotation angle by 45 degrees. Repeat Step 5 through 8 until the DUT has been rotated by
360 degrees. Calculate the average receiver sensitivity.
10. Repeat steps 1 through 9 for each test index from Table 13, Table 14, Table 15, or Table 16 applicable
to each test configuration from Table 12.
11. Repeat steps 1 through 10 for each test configuration in Table 12 supported by the DUT.
Table 15: MCS and Traffic Test Configuration for 802.11ax 2.4 GHz
Data Rates (Mbps)
GI = 1600 ns
Test
MCS Index Modulation 20 MHz channel, Nss = 1
Index
Theoretical Test Configuration
4 0 BPSK 8 5.2
5 11 1024-QAM 135 87.75
Note 1: The MCS rates are defined in Ref [3].
Note 2: Data rates specified for Long Guard interval, while testing may be performed
using either guard interval, as supported by the DUT.
Table 16: MCS and Traffic Test Configuration for 802.11ax 5 GHz
Data Rates (Mbps)
GI = 1600 ns
Test
MCS Index Modulation 80 MHz channel, Nss = 1
Index
Theoretical Test Configuration
7 0 BPSK 34 22.1
8 11 1024-QAM 567 374.4
Note 1: The MCS rates are defined in Ref [3].
Note 2: Data rates specified for Long Guard interval, while testing may be performed
using either guard interval, as supported by the DUT.
6.2.1.1 Introduction
The Maximum Connection test intends to verify that the Wi-Fi AP can support 32 STAs simultaneously
connected with minimal packet loss and no disassociations taking place.
6.2.1.2 Setup
1. The test setup (shown in Figure 6) SHALL be located in anechoic shielded chamber (see section 5.2.1
and 5.2.2).
2. A Traffic Generator/Analyzer, sending the Ethernet packets, connects to the LAN interface (e.g., GE port)
of the DUT.
3. The peer STAs is put at a distance of 2 meters to the DUT (For 2.4 GHz band, 2 meters free space of
wireless channel leads to 46 dB attenuation).
4. 32 STAs are prepared and associated to DUT during the test.
5. UDP connection SHALL be used for Ethernet packet transmission in the test.
Fixed distance: 2m
DUT STA
Fixed distance: 2m
Fixed distance: 2m
STA . . . STA
Test controller
1. Control of attenuators
Traffic generator 2. Configuration of traffic Traffic analyzer
3. Record of test results
Note: The test result may be slightly affected by the capability of Peer STA. It is recommended STA
used in the test have chipsets from at least 2 different vendors.
6.2.1.4 Procedures
1. Configure the operating mode of the DUT to the first supported configuration listed above.
2. Allow the STA to associate with the DUT.
3. Simultaneously measure the downlink UDP packet loss, using a test time of 120 seconds and a
traffic rate of 2 Mbps for 802.11n, 8 Mbps for 802.11ac, 3 Mbps for 802.11ax over 2.4 GHz, or 10
Mbps for 802.11ax over 5 GHz, through each STA. Record the number of packets transmitted and
received to calculate the packet error rate.
4. Simultaneously measure the uplink UDP packet loss, using a test time of 120 seconds and a traffic
rate of 2 Mbps for 802.11n or 8 Mbps for 802.11ac, 3 Mbps for 802.11ax over 2.4 GHz, or 10 Mbps
for 802.11ax over 5 GHz, through each STA. Record the number of packets transmitted and
received to calculate the packet error rate.
5. Repeat steps 2 through 4 for each additional configuration / operating mode supported by the DUT.
6.2.2.1 Introduction
Maximum throughput test intends to measure the maximum throughput performance of the DUT. The test is
conducted with connection by air interface in short distance (by considering the actual utilization of Wi-Fi).
6.2.2.2 Setup
1. The test setup (shown in Figure 7) SHALL be located in the anechoic shielded chamber (see section
5.2.1 and 5.2.2).
2. A Traffic Generator/Analyzer, sending the Ethernet packets, connects to the LAN interface (e.g., GE
port) of the DUT. The peer STA is put at a distance of 2 meters to the DUT (For 2.4 GHz band, 2
meter free space of wireless channel leads to 46 dB attenuation).
3. TCP connection SHALL be used for Ethernet packet transmission in the test.
Fixed distance: 2m
DUT STA
Test controller
1. Control of attenuators
Traffic generator 2. Configuration of traffic Traffic analyzer
3. Record of test results
The test case SHALL be conducted on all the applicable modes of the DUT.
6.2.2.4 Procedures
1. Configure the working mode of DUT to 802.11n with default configuration.
2. Establish the LAN connection and allow STA to associate with the DUT.
3. Measure the downlink TCP throughput to the STA, using a test time of 120 seconds.
4. Measure the uplink TCP throughput to the STA, using a test time of 120 seconds.
5. Set the working mode of DUT to 802.11ac, and repeat steps 3-4 for bandwidth 80MHz.
6. Set the working mode of DUT to 802.11ax over 2.4 GHz, and repeat steps 3-4.
7. Set the working mode of DUT to 802.11ax over 5 GHz, and repeat steps 3-4.
Note: The test result MAY be slightly affected by the capability of Peer STA. The test can be conducted
with different peer STAs with chipsets from different vendors. The calculated average throughput then
can be averaged again in the dimension of chipset.
802.11ac 802.11ac
80 560 560 504 504
(Nss=2) (Nss=2)
802.11ax
802.11ax
(2.4 GHz, 20 N/A N/A 200 200
(2.4 GHz, NSS=2)
NSS=2)
802.11ax
802.11ax
(5 GHz, 80 N/A N/A 720 720
(5 GHz, NSS=2)
NSS=2)
6.2.3.1 Introduction
Wi-Fi signal transmission can be seen as a multicast process since the STAs involved share the transmission
medium. Air interface becomes a rare resource when dense connections or high throughput requests exist.
Channel condition determines the MCS selection, therefore affecting the data throughput. In general, long
distance to travel or obstacle penetration leads to larger attenuation, which makes the data rate in a low level.
Occupying excessive air time of STA with small MCS will be unfair to the STAs with large MCS (here, assuming
the QoS requirement is similar) when the air resources have already run out.
Airtime Fairness Test intends to verify the capability of Wi-Fi device to guarantee the fairness of airtime usage.
6.2.3.2 Setup
1. The test setup (shown in Figure 8) SHALL locate in the anechoic shielded chamber (see section 5.2.1
and 5.2.2).
2. Three peer STAs are used in the test. STA1 and STA2 are 802.11n/ac/ax devices with the same number
of spatial streams supported by the DUT in both 2.4 and 5GHz bands. STA3 is a legacy 802.11a/b/g,
802.11n Nss = 1, or 802.11ac Nss = 1 devices, depending on the operating mode under test. All STAs
are located in the distance of 2 meter to the DUT (For 2.4 GHz band, 2 meter free space of wireless
channel leads to 46 dB attenuation).
3. DUT is set to 2.4 GHz operating frequency band with default configuration in the beginning of the test.
4. A Traffic Generator/Analyzer, sending the Ethernet packet to each peer STA, connects to the LAN
interface (e.g., GE port) of the DUT.
5. The TCP connection SHALL be used for Ethernet packet transmission in the test.
Fixed distance: 2m
DUT STA1
Fixed distance: 2m
Fixed distance: 2m
STA3 STA2
Test controller
1. Control of attenuators
Traffic generator 2. Configuration of traffic Traffic analyzer
3. Record of test results
6.2.3.4 Procedures
1. Establish the setup using default configuration for the 802.11n 2.4 GHz frequency band with Nss = 2
operating mode. Use or configure a STA3 to only use 802.11b/g. Establish the setup using default
configuration for the 802.11n operating mode.
2. Associate STA1 and STA2 with DUT. Establish the LAN connection and wait for 10 seconds.
3. Measure the achievable downlink TCP throughput through STA1, using a test time of 120 seconds. Record
this value as STA1_Throughput_Max_DL_1.
4. Measure the achievable downlink TCP throughput through STA2, using a test time of 120 seconds. Record
this value as STA2_Throughput_Max_DL_1.
5. Configure the downlink UDP traffic streams to use a downlink data rate set to 40% of
STA1_Throughput_Max_DL_1 for STA1 and 40% of STA2_Throughput_Max_DL_1 for STA2. Record
these values as STA1_Throughput_1 and STA2_Throughput_1 respectively.
6. Simultaneously run the two UDP traffic streams for 120 seconds, recording the number of packets
transmitted, received, and dropped for each stream. Calculate the STA1_PACKET_LOSS_RATIO_1 and
STA2_PACKET_LOSS_RATIO_1, as the number of lost packets divided by the total number of packets
transmitted.
7. Measure the downlink TCP throughput to each STA1 and STA2, using a test time of 120 seconds. Record
this as STA1 _throughput_1 and STA2 _throughput_1.
8. Move STA2 to a medium distance to the DUT (equivalent to 38 [email protected] and 25 dB @5GHz attenuation
between DUT and STA2). Wait for 10 seconds.
9. Measure the achievable downlink TCP throughput through STA2, using a test time of 120 seconds. Record
this value as STA2_Throughput_Max_DL_2.
10. Configure the downlink UDP traffic streams to use a downlink data rate set to 40% of
STA1_Throughput_Max_DL_1 for STA1 and 40% of STA2_Throughput_Max_DL_2 for STA2. Record the
latter values as STA2_Throughput_2.
11. Simultaneously run the two UDP traffic streams for 120 seconds, recording the number of packets
transmitted, received, and dropped for each stream. Calculate the STA1_PACKET_LOSS_RATIO_2 and
STA2_PACKET_LOSS_RATIO_2, as the number of lost packets divided by the total number of packets
transmitted.
12. Measure the downlink TCP throughput to STA 1 and STA2, using a test time of 120 seconds. Record this
as STA1 _throughput_2 and STA2 _throughput_2.
13. Disassociate STA2 with the DUT. Replace STA 2 with STA 3, configured for the specified Wi-Fi operating
mode, and remove the attenuation. STA3 is configured to support only a 2.4 GHz connection. Establish the
Wi-Fi connection between STA3 and DUT and wait for 10 seconds.
14. Measure the achievable downlink TCP throughput through STA3, using a test time of 120 seconds. Record
this value as STA3_Throughput_Max_DL_3.
15. Configure the downlink UDP traffic streams to use a downlink data rate set to 40% of
STA1_Throughput_Max_DL_1 for STA1 and 40% of STA3_Throughput_Max_DL_3 for STA3. Record the
latter values as STA3_Throughput_3.
16. Simultaneously run the two UDP traffic streams for 120 seconds, recording the number of packets
transmitted, received, and dropped for each stream. Calculate the STA1_PACKET_LOSS_RATIO_3 and
STA3_PACKET_LOSS_RATIO_3, as the number of lost packets divided by the total number of packets
transmitted.
17. Measure the downlink TCP throughput to STA 1 and STA3, using a test time of 120 seconds. Record this
as STA1 _throughput_3 and STA3 _throughput_3.
18. Set the DUT to operating mode to 802.11ac 5 GHz frequency band with Nss = 2. Replace or reconfigure
STA3 with a STA that uses only 802.11a. Repeat steps 2 to 16. Replace STA3 with a STA that uses only
802.11a. Set the DUT to operating mode of 802.11ac. Repeat steps 2 to 7.
19. Set the DUT to operating mode to 802.11ax 2.4 GHz frequency band with Nss = 2. Replace or reconfigure
STA3 with a STA that uses only 802.11n. Repeat steps 2 to 16. Replace STA3 with a STA that uses only
802.11n. Set the DUT to operating mode of 802.11ax 2.4 GHz. Repeat steps 2 to 7.
20. Set the DUT to operating mode to 802.11ax 5 GHz frequency band with Nss = 2. Replace or reconfigure
STA3 with a STA that uses only 802.11ac. Repeat steps 2 to 16. Replace STA3 with a STA that uses only
802.11ac. Set the DUT to operating mode 802.11ax 5 GHz. Repeat steps 2 to 7.
a) For each UDP measurement, the PACKET_LOSS_RATIO SHALL be less than or equal to 1E-4. The
throughput variation of DUT SHALL meet:
For the test in 802.11n 2.4 GHz frequency band with Nss = 2:
1) The summation of STA1_throughput_1 and STA2_throughput_1 SHALL be larger than 80 90 Mbps.
2) The summation of STA1_throughput_1 STA1_throughput_2 and STA2_throughput_2 SHALL be larger
than 80 Mbps.
3) The summation of STA1_throughput_1 STA1_throughput_3 and STA3_throughput_3 SHALL be larger
than 48 60 Mbps.
For the test in 802.11ax 2.4 GHz frequency band with Nss = 2:
1) The summation of STA1_throughput_1 and STA2_throughput_1 SHALL be larger than 150 160 Mbps.
2) The summation of STA1_throughput_1 STA1_throughput_2 and STA2_throughput_2 SHALL be larger
than 130 108 Mbps.
3) The summation of STA1_throughput_1 STA1_throughput_3 and STA3_throughput_3 SHALL be larger
than 95 100 Mbps.
6.2.4.1 Introduction
The Dual-band Throughput Test is intended to measure the throughput the DUT can support when
concurrently connected to multiple stations on both the 2.4 and 5 GHz bands, each operating with two spatial
streams. The purpose of these additional test cases is to detect cross band interference of the DUT's
transmitter on the receiver. The weak link is needed to ensure DUT and STA are transmitting at the highest
power and causing the most potential interference when the receiver is more susceptible to noise (low
SNR). Note, each station is connected using either the 2.4 or 5 GHz band, but not both bands
simultaneously. This test requires at least 2 stations, located 2m from the DUT. The DUT will need to
support at least 4 independent radio chains for this test case, two operating in the 2.4 GHz band and two
operating in the 5 GHz band.
6.2.4.2 Setup
1. The test setup (shown in Figure 9) SHALL be located in the anechoic shielded chamber (see section
5.2.1 and 5.2.2), using 2 stations.
2. The peer STAs are put at a distance of 2 meters to the DUT. For 2.4 GHz band, 2 meters free space
of wireless channel leads to 46 dB attenuation.
3. Additional attenuation is added in each RF chain of STA to simulate the incremental distance.
Configure the attenuators to an initial value of 10 dB.
4. Configure one station to enable only the 2.4 GHz band, configure the other station to enable only the
5 GHz band.
5. A Traffic Generator/Analyzer, sending the Ethernet packets, connects to the LAN interface (e.g., GE
port) of the DUT.
6. TCP connections SHALL be used for Ethernet packet transmission in the test.
Fixed distance: 2m
DUT
Fixed distance: 2m STA
STA
Test controller
Traffic generator 1. Control of attenuators Traffic analyzer
2. Configuration of traffic
3. Record of test results
6.2.4.4 Procedures
1. Configure the working mode of DUT to enable both 802.11n and 802.11ac with the default
configuration (see section 5.3).
2. Establish the LAN connection and allow all STA to associate with the DUT.
3. Simultaneously measure the downlink TCP throughput to all STA, using a test time of 120 seconds.
4. Simultaneously measure the uplink TCP throughput to all STA, using a test time of 120 seconds
5. Simultaneously measure the downlink TCP throughput to the 802.11n STA and the uplink TCP
throughput to the 802.11ac STA.
6. Simultaneously measure the uplink TCP throughput to the 802.11n STA and the downlink TCP
throughput to the 802.11ac STA.
7. Repeat steps 1 through 6 with the attenuators set to 32 dB for 2.4 GHz STA and 25 dB for 5 GHz
STA.
8. Repeat steps 1 through 6 with the attenuators set to 42 dB for 2.4 GHz STA and 35 dB for 5 GHz
STA.
9. Repeat steps 1 through 8 for each configuration listed above in 6.2.4.3.
Note: The test result MAY be slightly affected by the capability of Peer STA. The test can be
conducted with different peer STAs with chipsets from different vendors. The calculated
average throughput then can be averaged again in the dimension of chipset.
Note: The simultaneous measurements imply 2 TCP measurement streams connecting two
IP hosts, each located at one STA.
6.2.5.1 Introduction
The Bidirectional Throughput Test measures the uplink and downlink simultaneously achieved through the
DUT and a station.
6.2.5.2 Setup
1. The test setup (shown in Figure 7) SHALL be located in the anechoic shielded chamber (see
section 5.2.1 and 5.2.2). The peer STA is put at a distance of 2 meters to the DUT (For 2.4 GHz
band, 2 meters free space of wireless channel leads to 46 dB attenuation).
2. Configure the DUT and STA to use the 2.4 GHz band, per the settings in Section 5.3.
3. Configure the attenuator to 10 dB.
4. A Traffic Generator/Analyzer, sending the Ethernet packets, connects to the LAN interface (e.g.,
GE port) of the DUT. TCP connections SHALL be used for Ethernet packet transmission in the
test.
6.2.5.4 Procedures
1. Establish the LAN connection and allow the STA to associate with the DUT.
2. Measure the achievable downlink TCP throughput, using a test time of 120 seconds. Record this
value as Throughput_Max_DL.
3. Measure the achievable uplink TCP throughput, using a test time of 120 seconds. Record this value
as Throughput_Max_UL.
4. Configure bidirectional UDP traffic streams to use a downlink data rate set to 45% of
Throughput_Max_DL and an uplink data rate of 45% of Throughput_Max_UL. Record these values
as Throughput_DL and Throughput_UL respectively.
5. Simultaneously run the bidirectional UDP traffic for 120 seconds, recording the number of packets
transmitted, received, and dropped in each direction.
6. Calculate the PACKET_LOSS_RATIO_DL and PACKET_LOSS_RATIO_UL as the number of lost
packets divided by the total number of packets transmitted.
7. Repeat steps 1 through 6 for attenuator settings 21 dB and 42 dB for 2.4 GHz DUT configurations or
21 dB and 35 dB for 5 GHz DUT configurations.
8. Repeat steps 1 through 7 for each configuration listed above in Section 6.2.5.3.
Note: The test result MAY be slightly affected by the capability of Peer STA. The test can be
conducted with different peer STAs with chipsets from different vendors. The calculated average
throughput then can be averaged again in the dimension of chipset.
6.3 Coverage
6.3.1.1 Introduction
Range versus rate test intends to measure the baseband and RF chain performance of Wi-Fi device. The
attenuation of signals due to increasing range is achieved by using attenuator(s) in the RF path between the
AP and STA.
6.3.1.2 Setup
1. The test setup (shown in Figure 10) SHALL locate in the anechoic shielded chamber (see section 5.2.1
and 5.2.2).
2. A Traffic Generator/Analyzer, sending the Ethernet packets, connects to the LAN interface (e.g., GE
port) of the DUT. The peer STA is located 2 meters to the DUT (46dB attenuation for 2.4 GHz, 53 dB
attenuation for 5.2 GHz).
3. Additional attenuation is added to simulate the incremental distance. The specific attenuation values
used for testing are defined in 6.3.1.3.
4. The host SHALL send the Ethernet packet at the maximum rate which the DUT can achieve
theoretically.
5. TCP connection SHALL be used for Ethernet packet transmission in the test.
Note 1: The attenuators need to be capable of providing attenuation steps between 0dB ~ 63dB for the
selected operating frequency band.
Note 2: A channel simulator, which emulates a specific real environment, MAY be used to replace the
simple attenuators for more comprehensive test.
Fixed distance: 2m
DUT STA
Test controller
1. Control of attenuators
Traffic generator 2. Configuration of traffic Traffic analyzer
3. Record of test results
2. Additional attenuation for STA RF chain during the test, see Table 24.
Table 24: Additional attenuation for STA RF chain during the test
0 dB (default), 10 dB, 21 dB, 24 dB, 27 dB, 30 dB, 33 dB, 36 dB, 39 dB, 42 dB, 45
Additional attenuation for dB, 48 dB, 51 dB, 54 dB, 57 dB, 60 dB, 63 dB
test of 802.11n and 802.11ax
2.4 GHz
Additional attenuation for test 0 dB (default), 10 dB, 21 dB, 24 dB, 27 dB, 30 dB, 33 dB, 36 dB, 39 dB, 42 dB, 45
of 802.11ac and 802.11ax 5 dB, 48 dB, 51 dB, 54 dB
GHz
6.3.1.4 Procedures
1. Configure the attenuator with 0 dB attenuation. Configure the working mode of DUT to 802.11n and
operating frequency band to 2.4 GHz with default configuration.
2. Establish the LAN connection and allow STA to associate with the DUT.
3. Measure the downlink TCP throughput to the STA, using a test time of 120 seconds.
4. Measure the uplink TCP throughput to the DUT, using a test time of 120 seconds.
5. Change the attenuation for STA RF chain according to 6.3.1.3 until the attenuation reaches to 63 dB.
Repeat step 2-4.
6. Configure the attenuator with 0 dB attenuation. Set the working mode of DUT to 802.11ac with 80MHz
bandwidth. Repeat step 2-4 for all attenuation values in section 6.3.1.3.
7. Configure the attenuator with 0 dB attenuation. Set the working mode of DUT to 802.11ax over 2.4 GHz
with 20MHz bandwidth. Repeat step 2-4 for all attenuation values in section 6.3.1.3.
8. Configure the attenuator with 0 dB attenuation. Set the working mode of DUT to 802.11ax over 5 GHz with
80MHz bandwidth. Repeat step 2-4 for all attenuation values in section 6.3.1.3.
Note: The test result MAY be slightly affected by the capability of Peer STA. The test MAY be
conducted with different peer STAs with chipsets from different vendors. The calculated average
throughput then is averaged again in the dimension of chipset.
The measured average throughput SHALL meet the performance requirement of Table 25. For each
operating mode (i.e., 802.11n or 802.11ax over 5 GHz), no more than 2 test points SHALL fall below the
throughput requirement.
6.3.2.1 Introduction
Spatial consistency test intends to verify the Wi-Fi signal consistency in spatial domain.
6.3.2.2 Setup
1. The test setup (shown in Figure 11) SHALL locate in the anechoic shielded chamber (see section 5.2.1
and 5.2.2), DUT and peer STA is in a distance of 2 meters. DUT is fixed in a two-dimensional rotation
platform.
2. A Traffic Generator/Analyzer, sending the Ethernet packet, connects to the LAN interface (e.g., GE port)
of the DUT. The Peer STA receives the Wi-Fi packet from the DUT through air interface.
3. Additional attenuation is added to simulate the incremental distance. The concrete values are defined in
6.3.2.3.
4. TCP connection SHALL be used for Ethernet packet transmission in the test.
Fixed distance: 2m
DUT STA
Rotation platform
Test controller
1. Control of attenuators
Traffic generator 2. Configuration of traffic Traffic analyzer
3. Record of test results
6.3.2.4 Procedures
1. Configure the working mode of DUT to 802.11n, operating frequency band to 2.4 GHz with default
configuration.
2. Establish the LAN connection and allow STA to associate with to the DUT.
3. Measure the downlink TCP throughput to the STA, using a test time of 60 seconds. Wait for 10 seconds.
Measure the uplink TCP throughput to the STA, using a test time of 60 seconds.
4. Rotate the DUT platform by 30° and repeat Step 3 until the platform has been rotated by 360°.
5. Increase the attenuation for each RF chain according to 6.3.2.3 and reset the position of DUT platform to
0°, until all the attenuation values have been tested. Repeat Step 2-5.
6. Set the working mode of DUT to 802.11ac with a bandwidth of 80 MHz and operating frequency to 5 GHz,
reset the position of DUT platform to 0°. Repeat Step 2-5.
7. Set the working mode of DUT to 802.11ax over 2.4 GHz with a bandwidth of 20 MHz and reset the position
of DUT platform to 0°. Repeat Step 2-5.
8. Set the working mode of DUT to 802.11ax over 5 GHz with a bandwidth of 80 MHz and reset the position
of DUT platform to 0°. Repeat Step 2-5.
Note: The test result MAY be slightly affected by the capability of Peer STA. The test MAY be
conducted with multiple peer STAs with chipsets from different vendors. The calculated average
throughput then is averaged again in the dimension of chipset.
DL UL DL UL DL UL
802.11n
802.11n (Nss=2) 20 90 90 70 70 35 35
(Nss=2)
802.11ac 802.11ac
80 500 500 400 400 300 300
(Nss=2) (Nss=2)
802.11ax 802.11ax
(2.4 GHz, (2.4 GHz, 20 150 150 100 100 35 35
Nss=2) Nss=2)
802.11ax 802.11ax
80 700 700 400 400 200 200
(5 GHz, Nss=2) (5 GHz, Nss=2)
b) If any throughput measurement fails to meet the requirements of Table 27, the following requirement
SHALL also apply, the maximum variation during rotation SHALL satisfy the requirements in Table 28:
Note: The variation at each specific attenuation is calculated as the difference between the minimum
throughput value and the average throughput value, divided by the average throughput value over all
rotations.
DL UL DL UL DL UL
11n (Nss=2) 11n (Nss=2) 20 30% 30% 30% 30% 30% 30%
11ac (Nss=2) 11ac (Nss=2) 80 40% 40% 40% 40% 40% 40%
802.11ax 802.11ax
(2.4 GHz, (2.4 GHz, 20 30% 30% 30% 30% 30%
30%
Nss=2) Nss=2)
802.11ax 802.11ax
80 40% 40% 40% 40% 40% 40%
(5 GHz, Nss=2) (5 GHz, Nss=2)
6.3.3.1 Introduction
This test case examines the maximum performance expected from a DUT supporting 802.11ax with the
following additional capabilities beyond the default configuration: 4 spatial streams, 160 MHz Channels.
This test SHALL be conditionally MANDATORY for the test plan, where each Wi-Fi configuration listed in
Table 29 supported by the DUT SHALL be tested.
6.3.3.2 Setup
1. The test setup (shown in Figure 6) SHALL be located in the anechoic shielded chamber (see section
5.2.1 and 5.2.2).
2. The peer STA is put at a distance of 2 meters to the DUT (For 2.4 GHz band, 2 meter free space of
wireless channel leads to 46 dB attenuation).
3. A Traffic Generator/Analyzer, sending the Ethernet packets, connects to the LAN interface (e.g., GE
port) of the DUT.
4. TCP connection(s) SHALL be used to measure the throughput between the STA and DUT.
6.3.3.4 Procedures
1. Configure the operating mode of the DUT and STA to the first configuration in Table 29.
2. Establish the LAN connection and allow STA to associate with the DUT.
3. Measure the downlink TCP throughput to the STA, using a test time of 120 seconds.
4. Measure the uplink TCP throughput to the STA, using a test time of 120 seconds.
5. Repeat steps 1 through 4 for each additional configuration in Table 29 supported by the DUT.
6.4.1.1 Introduction
Multiple STAs performance test intends to measure the performance of Wi-Fi device connected with multiple
STAs simultaneously. To simulate a circumstance of real environment, various levels of signals reflecting
various distance between Wi-Fi device and STA are considered in the test.
6.4.1.2 Setup
The same test setup shown in Figure 10 SHALL be used. Note the STA in Figure 10 is duplicated by 9 times
in this test.
1. Total 9 STAs are engaged in the test. Three STAs are located in a short distance to the DUT. Three STAs
are located in a medium distance to the DUT. The rest of the STAs are located in a long distance to the
DUT. The short/medium/long distance are emulated by adding additional attenuation for the signals as
follows:
a) STA in short distance: 10 dB @2.4GHz band, 10 dB @5GHz band;
b) STA in medium distance: 38 dB @2.4GHz band, 25 dB @5GHz band;
c) STA in long distance: 48 dB @2.4 GHz band, 35 dB @5GHz band.
2. A Traffic Generator/Analyzer, sending the corresponding Ethernet packets to each STA, connects to the
LAN interface (e.g., GE port) of the DUT.
3. TCP connection SHALL be used for Ethernet packet transmission in the test.
Table 31: DUT configuration for Multiple Association / Disassociation Stability Test
Wi-Fi configuration Wi-Fi configuration Bandwidth
(DUT) (Peer STA) (MHz)
802.11n (Nss=2) 802.11n (Nss=2) 20
2. The general configuration SHALL be tested if the configuration is applicable for DUT.
6.4.1.4 Procedures
1. Configure DUT working mode as 802.11n, operating frequency band as 2.4GHz with default configuration.
2. Enable the radios on the STAs with the short distance. Allow STA to associate with the DUT.
3. Measure the downlink TCP throughput to each STA, using a test time of 120 seconds. Calculate the
summation of downlink TCP throughput of the three STA in short distance. Record the result as
“Throughput_S_DL”.Wait for 10 seconds. Measure the uplink TCP throughput to each STA, using a test
time of 120 seconds. Calculate the summation uplink TCP throughput of the three STA in short distance.
Record the result as “Throughput_S_UL”.
4. Enable the radios on the STAs with the medium distance. Allow STA to associate with the DUT. Measure
the downlink TCP throughput to each STA, using a test time of 120 seconds. Calculate the summation of
downlink TCP throughput of all STA (three STA in short distance and the three STA in medium distance).
Record the result as “Throughput_SM_DL”.Wait for 10 seconds. Measure the uplink TCP throughput to
each STA, using a test time of 120 seconds. Calculate the summation of uplink TCP throughput of all STA
(the three STA in short distance and the three STA in medium distance). Record the result as
“Throughput_SM_UL”.
5. Enable the radios on the STAs with the long distance. Allow STA to associate with the DUT. Measure the
downlink TCP throughput to each STA, using a test time of 120 seconds. Calculate the summation of all
STA (downlink TCP throughput of the three STA in short distance, the three STA in medium distance and
the three STA in long distance). Record the result as “Throughput_SML_DL”.Wait for 10 seconds. Measure
the uplink TCP throughput to each STA, using a test time of 120 seconds. Calculate the summation of
uplink TCP throughput of all STA (the three STA in short distance, the three STA in medium distance and
the three STA in long distance). Record the result as “Throughput_SML_UL”.
6. Set the working mode of DUT to 802.11ac according to Table 31, and bandwidth to 80 MHz if applicable,
and repeat Step 2- 5.
7. Set the working mode of DUT to 802.11ax over 2.4 GHz according to Table 31, and bandwidth to 20 MHz
if applicable, and repeat Step 2- 5.
8. Set the working mode of DUT to 802.11ax over 5 GHz according to Table 31, and bandwidth to 80 MHz if
applicable, and repeat Step 2- 5.
Note 1: The test result MAY be slightly affected by the capability of Peer STA. The test MAY be
conducted with multiple peer STAs with chipsets from different vendors. The calculated average
throughput then is averaged again in the dimension of chipset.
Note 2: Distance MAY be simulated by using attenuators between RF output and antenna of Wi-Fi
device.
802.11n 802.11n
20 70 70 60 60 50 50
(Nss=2) (Nss=2)
802.11ac 802.11ac
80 500 500 500 500 400 400
(Nss=2) (Nss=2)
802.11ax 802.11ax
(2.4 GHz, (2.4 GHz, 20 140 140 120 120 100 100
Nss=2) Nss=2)
802.11ax 802.11ax
80 680 600 600 250 500 200
(5 GHz, Nss=2) (5 GHz, Nss=2)
6.4.2.1 Introduction
Multiple association/disassociation stability test intends to measure stability of Wi-Fi device under a dynamic
environment with frequent change of connection status.
6.4.2.2 Setup
1. The test setup (shown in Figure 6) SHALL locate in the anechoic shielded chamber (see section 5.2.1
and 5.2.2).
2. 16 peer STAs SHALL be connected to the dedicated operating frequency band (2.4 GHz or 5 GHz) and
in a short distance of 2 meter to the DUT (For 2.4 GHz band, 2 meter free space of wireless channel leads
to 46 dB attenuation). The test is only conducted for one operating frequency band in each test circle.
3. UDP connection SHALL be used for Ethernet packet transmission in the test.
Table 33: DUT configuration for Multiple Association / Disassociation Stability Test
Wi-Fi configuration Wi-Fi configuration Bandwidth
(DUT) (Peer STA) (MHz)
802.11n (Nss=2) 802.11n (Nss=2) 20
2. The general configuration SHALL be tested if the configuration is applicable for DUT.
6.4.2.4 Procedures
1. Configure the working mode of DUT as 802.11n, operating frequency as 2.4GHz with the default
configuration.
2. 8 STAs are picked for sending/receiving packet while the other 8 STAs are picked to do association/re-
association process during the test. Establish the LAN connection and allow STA to associate with the
DUT. Enable downlink UDP flow (4 Mbps @2.4GHz and 8 Mbps @5GHz) from DUT to each STA.
3. Continue monitoring the traffic flow of each STA by recording the UDP flow rate every second.
4. Disassociate the rest peer STAs. Wait for 30 seconds. Re-associate the STAs simultaneously.
5. Configure the working mode of DUT as 802.11ac, operating frequency band as 5 GHz and the channel
bandwidth to 80 MHz, respectively. Wait for 10 seconds, repeat Steps 2-4.
6. Configure the working mode of DUT as 802.11ax over 2.4 GHz, operating frequency band as 5 GHz and
the channel bandwidth to 20 MHz, respectively. Wait for 10 seconds, repeat Steps 2-4.
7. Configure the working mode of DUT as 802.11ax over 5 GHz, operating frequency band as 5 GHz and the
channel bandwidth to 80 MHz, respectively. Wait for 10 seconds, repeat Steps 2-4.
Note: The test result MAY be slightly affected by the capability of Peer STA. The test MAY be
conducted with multiple peer STAs with chipsets from different vendors.
6.4.3.1 Introduction
Downlink MU-MIMO Performance Test intends to verify the performance of Wi-Fi device when Downlink MU-
MIMO is applied. This best represents a typical deployment, where stations may only support 1x1 or 2x2 RF
chain configurations. The test is only applicable to the Wi-Fi device supporting the 802.11ac/ax. Downlink MU-
MIMO capability is also sometimes referred to as 802.11ac Wave 2. The DUT SHALL support 802.11ac/ax
MU-MIMO and at least 4 spatial streams.
This test SHALL be conditionally MANDATORY for the test plan, if the DUT supports Downlink MU-MIMO,
with at least 3 spatial streams (NSS=3) for each band to be tested, the test is required.
6.4.3.2 Setup
1. The test setup (see Figure 8) SHALL locate in the anechoic shielded chamber (see section 5.2.1 and
5.2.2).
2. The DUT and engaged peer STAs SHALL support 802.11ac or 802.11ax and MU-MIMO. One STA (STA
1) supports maximum two spatial streams while two STAs (STA 2 and STA 3) support only one spatial
stream. All STAs are located in the distance of 2 meter to the DUT (For 5.2 GHz band, 2-meter free space
of wireless channel leads to 52.8 dB attenuation) and are placed at different angles relative to the DUT,
ideally more than 45 degrees apart.
3. A Traffic Generator/Analyzer, sending the Ethernet packet to each peer STA, connects to the LAN
interface of the DUT.
4. TCP connection SHALL be used for Ethernet packet transmission in the test.
6.4.3.4 Procedures
1. Establish the setup by using the default configuration as detailed above.
2. Associate STA 1 with DUT. Establish the LAN connection and wait for 10 seconds.
3. Measure the downlink TCP throughput to STA1, using a test time of 120 seconds. Record this value as
STA1_throughput_1.
4. Disassociate STA1. Wait for 10 seconds. Associate STA 2 with DUT. Wait for 10 seconds. Measure the
downlink TCP throughput to STA2, using a test time of 120 seconds. Record this value as STA2_
throughput_1.
5. Disassociate STA 2. Wait for 10 seconds. Associate STA 3 with DUT. Wait for 10 seconds. Measure the
downlink TCP throughput to STA 3, using a test time of 120 seconds. Record this value as
STA3_throughput_1.
6. Associate STA 1 and STA 2 with the DUT (STA 3 remains associated). Simultaneously measure the
downlink TCP throughput to all STA, using a test time of 120 seconds. Record these values as
STA1_throughput_2, STA2_throughput_2 and STA3_throughput_2.
7. Disable DL MU-MIMO and wait for 10 seconds. Measure the downlink TCP throughput to each STA, using
a test time of 120 seconds. Record these values as STA1_throughput_3, STA2_throughput_3 and
STA3_throughput_3. If the DUT does not support this operation, this step and the associated test metric
SHALL NOT apply.
8. Repeat steps 1 through 7 for each DUT configuration listed above in section 6.4.3.3.
6.5 Stability/Robustness
6.5.1.1 Introduction
Long term stability test intends to measure the stability performance of Wi-Fi device under stresses that would
typically been seen under heavy user load, such as watching multiple 4k video streams. Throughput and
connection availability are continuously monitored over a period of 4 hours, during which time, the performance
must remain steady. Testing is conducted in multiple bands (2.4 GHz and 5 GHz) simultaneously.
6.5.1.2 Setup
1. The test setup (See Figure 6) SHALL be located in the anechoic shielded chamber (see section 5.2.1
and 5.2.2).
2. A total of 4 STAs SHALL be used during the test, with 2 STAs connecting within the 2.4 GHz band and 2
STAs connecting within the 5 GHz band.
3. One STA in each band SHALL be used to perform traffic performance measurements, while the other
STA in the band SHALL be used to periodically associate and disassociate from the DUT.
4. A Traffic Generator/Analyzer, establishing the Ethernet packets transmission to the STA (allocated to
receive packets), connects to the LAN interface (e.g., GE port) of the DUT.
5. UDP connections, operating at a fixed bitrate SHALL be used to measure the performance of the DUT.
If the DUT does not include multiple radios (i.e., the DUT does not support either the 2.4 or 5 GHz band), the
test SHALL be run with only the single band in operation, with a total of 2 STAs.
6.5.1.4 Procedures
1. Configure the DUT for the first operating configuration described above.
2. Configure the 2 STAs connecting to the 2.4 GHz band to associate with the DUT.
3. Configure the 2 STAs connecting to the 5 GHz band to associate with the DUT.
4. Wait for 60 seconds for the system to reach a steady state.
5. Configure two downlink UDP throughput measurements to run for 15 minutes each using a bit rate of 50
Mbps through one 2.4 GHz STA and one 5 GHz STA. While this throughput measurement is running
perform the following actions:
i. Wait 5 minutes.
ii. Toggle the association state of the second STA in each band (i.e., if the STA is currently
associated to the DUT, cause it to disassociate; or if it is disassociated, cause it to associate).
6. Record the number of lost UDP packets for each downlink measurement, recording the measurement as
PACKET_LOSS_[24 or 5]_GHZ_INTERVAL_n, where the band is indicated as 2.4 or 5 GHz and n
represents the n’th measurement interval. Calculate the PACKET_LOSS_RATIO_[24 or
5]_GHZ_INTERVAL_n as the number of lost packets divided by the total number of packets transmitted.
7. Repeat steps 4 and 5 for a total of 16 measurement intervals (4 hours of testing).
8. Repeat steps 1 through 6 for each DUT configuration defined above.
6.5.2.1 Introduction
AP coexistence test intends to verify Wi-Fi device performance with existence of alien AP. The alien AP in
the test SHALL support the same Wi-Fi standard (802.11n/802.11ac/802.11ax).
Note: This test case implements a simplified scenario where the alien network presents a 50%
utilization/contention with the DUT.
Note: When testing within the 5 GHz working frequency, 40 MHz channel bandwidths are utilized to
avoid the usage of DFS channels.
6.5.2.2 Setup
1. The test setup (show in Figure 12) SHALL locate in the anechoic shielded chamber (see section 5.2.1
and 5.2.2), DUT and peer STA is in a distance of 2 meters.
2. A host sends/receives the Ethernet packets/IP packets to DUT. The Peer STA receives/sends the Wi-Fi
packets from/to the DUT through air interface.
3. The host SHALL send the Ethernet packets/IP packets at the maximum rate which the DUT can achieve
theoretically.
4. A set of Wi-Fi interfaces/radios, supporting the same Wi-Fi standard (802.11n/802.11ac/802.11ax), are
used to generate the alien network interference, per the configurations described in Table 35. The QoS
settings on the alien network SHALL match those on the DUT.
5. TCP connection SHALL be used for Ethernet packet transmission in the test.
6. The Alien AP SHALL be the same manufacturer, model, and firmware version of the DUT and SHALL
be configured identically to the DUT except for the settings specified in Table 26 and the SSID that
SHALL be set to " BBF_Wi-Fi_Perf_Test_Alien".
Fixed distance: 2m
DUT STA
Fixed distance: 2m
Fixed distance: 2m
Alien AP Alien STA
Test controller
1. Control of attenuators
2. Configuration of traffic
Traffic generator 3. Record of test results Traffic analyzer
802.11ax 802.11ax
20
(2.4 GHz, Nss=2) (2.4 GHz, Nss=2)
802.11ax 802.11ax
80
(5GHz, Nss=2) (5GHz, Nss=2)
Note: The channel configuration of alien network MAY use either NSS = 1 or NSS
= 2.
Note: The general configuration SHALL be tested if the configuration is applicable for DUT.
2.4 GHz 6 6 7 11
44 (Note 3)
5 GHz 36 (Note 3) 36 36 (Note 2)
52
Notes:
1. If channels other than the default channels are used, the separation of the center
frequencies of the channels should be the same as the separation of the center frequencies
as defined using the default channels, and the bandwidths should be the same as in the
default test case.
2. This intends to emulate the effects of an overlapped channel (5 GHz alien configuration is
set to use a 40 MHz channel, while the DUT continues to use an 80 MHz channel).
3. When testing the adjoining channel case for the 5 GHz working frequency, two 40 MHz
channels SHALL be used to avoid the usage of DFS channels.
6.5.2.4 Procedure
1. Configure the working mode of DUT to 802.11n, operating frequency band to 2.4 GHz with default
configuration.
2. Turn off the DUT and the peer STA.
3. Turn on the alien AP and alien STA, allow the alien STA to associate with the alien AP, then wait for 10
seconds.
4. Measure the downlink TCP throughput to the alien STA, using a test time of 120 seconds. Record this
measurement as THROUGHPUT_SHORT_ALIEN.
5. If testing the 5 GHz working frequency, configure the alien AP to use the 40 MHz channel bandwidth,
measure the downlink TCP throughput to peer STA, using a test time of 120 seconds. Record this
measurement as THROUGHPUT_SHORT_ALIEN_40MHz. This value is used to calculate the
performance deduction only for the adjoining channel case; for all other tests, the DUT is configured to use
the 80 MHz channel bandwidth.
6. Turn off the alien AP and alien STA, turn on the DUT and peer STA.
7. Allow peer STA to associate with registers the DUT.
8. The channel of alien network SHALL be set to the same channel as DUT.
9. Keep the alien network radios shutdown (not transmitting any signals).
10. Wait for 10 seconds. Measure the downlink TCP throughput to peer STA, using a test time of 120 seconds.
Record this measurement as THROUGHPUT_SHORT_DUT.
11. If testing the 5 GHz working frequency, configure the DUT to use the 40 MHz channel bandwidth, measure
the downlink TCP throughput to peer STA, using a test time of 120 seconds. Record this measurement as
THROUGHPUT_SHORT_DUT_40MHz. Note, this value is used to calculate the performance deduction
only for the adjoining channel case; for all other tests, the DUT is configured to use the 80 MHz channel
bandwidth.
12. Enable the alien network radios. The alien network SHALL be configured according to Table 35. The alien
network will transmit beacon frames according to the default configuration settings of 5.3.3.
13. Wait for 10 seconds. Measure the downlink TCP throughput to peer STA, using a test time of 120 seconds.
Record this measurement as THROUGHPUT_SHORT_DUT_1.
14. Configure the alien network to transmit a UDP data stream at 40% of the measurement
THROUGHPUT_SHORT_ALIEN or THROUGHPUT_SHORT_ALIEN_40MHz, depending on the
configuration of the alien AP bandwidth (80 MHz or 40 MHz). utilize 50% of the available “air time”. This
can be achieved by packet transmission using the alien network of 1500-byte packets at one of the
following rates, depending on the configuration used for the alien network and the wireless MSC rate
selected by the transmitter: 32 Mbps for 802.11n 20MHz channels with 1 spatial stream, 90 Mbps for
802.11ac 40MHz with 1 spatial stream, 195 Mbps for 802.11ac 80MHz with 1 spatial stream, 65 Mbps for
802.11n 20MHz channels with 2 spatial streams, 180 Mbps for 802.11ac 40MHz with 2 spatial streams, or
390 Mbps for 802.11ac 80MHz with 2 spatial streams.
15. Wait for 10 seconds. Measure the downlink TCP throughput to peer STA, using a test time of 120 seconds.
Record this measurement as THROUGHPUT_SHORT_DUT_2.
16. Change the channel configuration of alien AP according to Table 35 until all the configuration has been
tested. Repeat Step 8. Stop the packet transmission for alien network.
17. Shut down the radios on the alien network.
18. Repeat steps 2 to 10 for each additional configuration listed in Table 34 above.
Wi-Fi Wi-Fi
Bandwidth
configuration configuration Alien Alien Alien
(MHz)
(DUT) (Peer STA) network network network
No alien Alien AP working working working
device turned on
(same (overlapping (adjoining
channel) channel) channel)
802.11n 802.11n <10%
20 - <5% <60 % <60%
(Nss=2) (Nss=2) <5%
802.11ac 802.11ac <10%
80 - <5 % <60 % <60 %
(Nss=2) (Nss=2) <5 %
802.11ax 802.11ax
<10%
(2.4 GHz, (2.4 GHz, 20 - <5% <60% <60%
<5%
Nss=2) Nss=2)
802.11ax 802.11ax
<10%
(5 GHz, (5 GHz, 80 - <5% <60% <60%
<5%
Nss=2) Nss=2)
Note: Percentage indicates the performance deduction referred to the case with no alien device turned on.
6.5.3.1 Introduction
When operating in environments with multiple Wi-Fi based networks the AP may be able to more reliably select
the channel with the lowest level of impairments from the adjacent networks compared to a less knowledgeable
end user. The test verifies the DUT (AP) will select a Wi-Fi channel that is not presently utilized by other
networks and will alter this channel on subsequent reboots, if the environment has changed (i.e., the channels
utilized by the adjacent network has changed).
Note, this test is not intended to verify avoidance of radar or other non-Wi-Fi signals or usage of the same
frequencies by other technology.
6.5.3.2 Setup
1. The test setup (shown in Figure 12) SHALL be located in the anechoic shielded chamber (see section
5.2.1 and 5.2.2), using 2 stations and 1 additional AP.
2. Configure the DUT to enable automatic channel selection for both its 2.4 GHz and 5 GHz radios. Note,
ensure these settings are persistently saved on the DUT.
3. Configure one station to enable only the 2.4 GHz band, use the SSID and password for the test network
per section 5.3.2.
4. Configure the additional AP to use 2.4 GHz Wi-Fi channel 6, 20 MHz channel bandwidth, and the
settings in Table 37 below.
5. Configure the second station to associate to the additional AP using the settings in Table 37 below.
6. The Ethernet traffic generator / analyzer is connected to the additional AP and STA.
6.5.3.4 Procedures
1. Power off the DUT.
2. Allow the second station to associate to the additional AP.
3. Configure the Ethernet traffic generator to run a continuous TCP throughput measurement, causing
the devices to continuously transmit over the Wireless link between the second STA and AP.
4. Power on the DUT and allow the first station to associate with the DUT.
5. Record the channel used by the DUT.
6. Repeat steps 1 through 5, with the additional AP configured to use 2.4 GHz channels 1 and 11.
7. Repeat steps 1 through 5, with the additional AP configured to use 2.4 GHz channel 1 and 40 MHz
bandwidth.
8. Repeat steps 1 through 5, using the 5 GHz band, with the additional AP configured to channels 42,
58, 106, and 122. The additional AP should be configured to use a channel bandwidth of 80 MHz.
Downlink Uplink
traffic flow traffic flow
Physical
Layer
DUT STA
Test
Setup
Figure 13: Test setup by using TCP/UDP flows with separate Packet Generator/Analyzer
Figure 13 shows typical examples when TCP/UDP flows are used in the test. Two independent Packet
Generators/Analyzers are utilized for packet generation/analysis. In this case, STA/STAs SHALL provide
interface to receive/forward packets from/to packet generation/analysis in STA side.
Downlink Uplink
traffic flow traffic flow
Physical
Layer
DUT STA
Test
Setup
Figure 14: Test setup by using TCP/UDP flows with the dedicated testing equipment
Figure 14 shows another example for usage of TCP/UDP flows. The dedicated testing equipment containing
a common Packet Generator/Analyzer and STA/STAs capability is used in the test.
Downlink Uplink
traffic flow traffic flow
Packet Generator/
Analyzer
Physical
Layer Independent
DUT
Test STA
Setup
Figure 15: Test setup by using TCP/UDP flows with an independent STA
Figure 15 shows another example for usage of TCP/UDP flows. Independent STA/STAs (i.e., being capable
to generate/analyze IP traffic) are used in the test. Additional software SHOULD be necessary to facilitate
packet generation/reception within the STA/STAs. The software is out of scope in this test plan.
Figure 16 shows a typical example when level-2 Ethernet flows are used in the test. A common Packet
Generator/Analyzer provide bidirectional packet generation/reception. In this case, STA/STAs SHALL provide
interface to receive/forward packets from/to packet generation/analysis in STA side.
Downlink Uplink
traffic flow traffic flow
Physical
Layer
DUT STA
Test
Setup
Figure 16: Test Setup by using level-2 Ethernet flows with a common Packet Generator/Analyzer
This test SHALL be OPTIONAL for the test plan and is for further study.
II.1.2 Setup
1. The test setup shown in Figure 3 “Wi-Fi Mesh Multiple Chamber Implementation” SHALL be used for this
test.
2. The “base AP” SHALL be placed in Shielded Chamber 1, and connected to the traffic generator.
3. The “Wi-Fi Repeater SHALL be placed in Shielded Chamber 2.
4. The Attn A set SHALL be configured to 10 dB.
5. The Attn B set SHALL be configured to 10 dB.
6. The Attn C set SHALL be configured to at least 60 dB.
7. The Traffic Generator/Analyzer, capable of sending the Ethernet packets, SHALL be connected to the
LAN interface (e.g., GE port) of the “base AP” and the STA.
8. The Traffic Generator/Analyzer SHALL be configured to measure the throughput using TCP sessions.
Table 39: DUT configuration for Repeated Wi-Fi Throughput Performance Test
Wi-Fi Configuration Description Attn B Values (dB)
Configuration
Config 1 802.11n, Nss = 2, BW = 20 MHz 10, 27, 36
Config 2 802.11ac, Nss = 2, BW = 80 MHz 10, 27, 36
Config 3 802.11ax 2.4 GHz, Nss = 2, BW = 20 MHz 10, 27, 36
Config 4 802.11ax 5 GHz, Nss = 2, BW = 80 MHz 10, 27, 36
II.1.4 Procedures
1. Configure the STA to operate in the first configuration mode described in Table 39.
2. Configure Attn B for the first value described in Table 39.
3. Establish the LAN connection and allow STA to associate with the DUT.
4. Measure the downlink TCP throughput to the STA, using a test time of 120 seconds.
5. Measure the uplink TCP throughput to the STA, using a test time of 120 seconds.
6. Repeat steps 2 through 5 for each attenuation value listed in Table 39 for the configured operating mode.
7. Repeat steps 1 through 6 for each configuration from Table 39 supported by the “Wi-Fi Repeater.”
Note: The tester must ensure the STA is connected to the “Wi-Fi Repeater” and not the “Base AP”
through Attn C.
Note: When developing the pass/fail metrics, the case should be considered where the back-haul link
is 802.11ac Nss=2, while the front-haul link to the STA is 802.11ax Nss=2. This case will exist for
some operators as systems roll out and should allow for those devices to pass.
Table 40: Pass/Fail requirements for Repeated Wi-Fi Throughput Performance Test Config 1
Config 1: 802.11n, Nss = 2, BW = 20 MHz
(5 out of 6 requirements MUST pass)
Attn B Value Dual-band Wi-Fi Repeater Tri-band Wi-Fi Repeater
(dB)
Downlink Uplink Throughput Downlink Throughput Uplink Throughput
Throughput Requirement Requirement (Mbps) Requirement (Mbps)
Requirement (Mbps)
(Mbps)
10 For Further Study For Further Study For Further Study For Further Study
27 For Further Study For Further Study For Further Study For Further Study
36 For Further Study For Further Study For Further Study For Further Study
Table 41: Pass/Fail requirements for Repeated Wi-Fi Throughput Performance Test Config 2
Config 2: 802.11ac, Nss = 2, BW = 80 MHz
(5 out of 6 requirements MUST pass)
Attn B Value Dual-band Wi-Fi Repeater Tri-band Wi-Fi Repeater
(dB)
Downlink Uplink Throughput Downlink Throughput Uplink Throughput
Throughput Requirement Requirement (Mbps) Requirement (Mbps)
Requirement (Mbps)
(Mbps)
10 For Further Study For Further Study For Further Study For Further Study
27 For Further Study For Further Study For Further Study For Further Study
36 For Further Study For Further Study For Further Study For Further Study
Table 42: Pass/Fail requirements for Repeated Wi-Fi Throughput Performance Test Config 3
Config 3: 802.11ax 2.4 GHz, Nss = 2, BW = 20 MHz
(5 out of 6 requirements MUST pass)
Attn B Value Dual-band Wi-Fi Repeater Tri-band Wi-Fi Repeater
(dB)
Downlink Uplink Throughput Downlink Throughput Uplink Throughput
Throughput Requirement Requirement (Mbps) Requirement (Mbps)
Requirement (Mbps)
(Mbps)
10 For Further Study For Further Study For Further Study For Further Study
27 For Further Study For Further Study For Further Study For Further Study
36 For Further Study For Further Study For Further Study For Further Study
Table 43: Pass/Fail requirements for Repeated Wi-Fi Throughput Performance Test Config 4
Config 4: 802.11ax 5 GHz, Nss = 2, BW = 80 MHz
(5 out of 6 requirements MUST pass)
Attn B Value Dual-band Wi-Fi Repeater Tri-band Wi-Fi Repeater
(dB)
Downlink Uplink Throughput Downlink Throughput Uplink Throughput
Throughput Requirement Requirement (Mbps) Requirement (Mbps)
Requirement (Mbps)
(Mbps)
10 For Further Study For Further Study For Further Study For Further Study
27 For Further Study For Further Study For Further Study For Further Study
36 For Further Study For Further Study For Further Study For Further Study
This test SHALL be OPTIONAL for the test plan and is for further study.
II.2.2 Setup
1. The test setup shown in Figure 3 “Wi-Fi Mesh Multiple Chamber Implementation” SHALL be used for this
test.
2. The “base AP” SHALL be placed in Shielded Chamber 1, and connected to the traffic generator.
3. The “Wi-Fi Repeater SHALL be placed in Shielded Chamber 2.
4. The Attn A set SHALL be configured to 10 dB.
5. The Attn B set SHALL be configured to 10 dB.
6. The Attn C set SHALL be configured to 60 dB.
7. The Traffic Generator/Analyzer, capable of sending the Ethernet packets, SHALL be connected to the
LAN interface (e.g., GE port) of the “base AP” and the STA.
8. The Ethernet traffic generator is configured to iperf3, or an equivalent substitute, to transmit one stream
of 1460-byte UDP packets at 1 Mbps from the STA. The STA MUST NOT “buffer” packets while Wi-Fi is
disconnected for the roaming event.
9. The STA SHALL have 802.11v (BSS Transition Management Messages) enabled. The DUT MAY, but is
not required, to support 802.11v.
II.2.4 Procedures
1. Configure the “base AP,” “Wi-Fi repeater,” and STA to operate in the first configuration mode described
in Table 44. Note 1
2. Configure Attn B to 10 dB and Attn C to 60 dB.
3. Establish the LAN connection and allow STA to associate with the DUT. Verify the STA is associated with
the “Wi-Fi repeater.”
4. Enable the uplink UDP transmission from the STA.
5. Decrease the value of Attn C by 1 dB
6. Wait 2 seconds
7. Increase the value of Attn B by 1 dB
8. Wait 2 second
9. Repeat steps 5 through 8 until Attn B is configured to 60 dB.
10.
Stop the UDP transmission and record the number of UDP packets that were transmitted by the STA and
the number of UDP packets received by the iperf target. Note 2
11. Restart the uplink UDP transmission from the STA.
12. Decrease the value of Attn B by 1 dB
13. Wait 2 seconds
14. Increase the value of Attn C by 1 dB
15. Wait 2 second
16. Repeat steps 5 through 8 until Attn C is configured to 60 dB.
17.
Stop the UDP transmission and record the number of UDP packets that were transmitted by the STA and
the number of UDP packets received by the iperf target. Note 2
18. Repeat steps 1 through 17 for each configuration from Table 44 supported by the “base AP” and “Wi-Fi
repeater.”
Notes:
1. The systems are configured to use a single wireless operating mode (i.e., 802.11n @ 2.4
GHz, Nss = 2, BW = 20 MHz), to reduce the measurement uncertainty between test runs,
by preventing the case where the STA roamed from one AP to the other, while also
changing operating modes.
2. It is expected for there to be lost UDP packets (i.e., a difference in the total number of
received and transmitted packets), caused by the roaming event. Each UDP packet
represents an “interval” of time the STA was disconnected from the network and blocked
from sending traffic.