Professional Documents
Culture Documents
Octobox
Octobox
The throughput software controls programmable attenuators, turntable, interference generator and a traffic
generator. Test traffic can be generated using octoScope’s multiPerf, iperf or IxChariot to produce throughput vs.
path loss plots, such as the one shown in Figures 2 and 3.
Figure 2: Browser-based real-time plot of throughput vs. path loss. In this example two measurements are overlaid
on the same plot to show beamforming gains. Path loss incremented by 5 dB every 30 seconds.
The plot shown in Figure 2 is a real-time plot that updates every second in a browser as the test runs. The plot shown
in Figure 3 is an Excel plot based on saved data that is averaged over some specified time period for each point.
Figure 3: Saved Excel-based plot of throughput vs. path loss. If the turntable is used, every point on the plot can be
averaged vs DUT (device under test) rotation.
Figure 4: Plot of throughput vs. path loss vs. orientation; nulls in the DUT antenna field can be seen at some
orientations of the DUT
To test a link of two or more real devices, you can use a STACK testbed (Figure 5). This testbed can demonstrate
how diverse chipsets or devices interact. We refer to one of the devices as the DUT (device under test) and the other
as its partner. The partner exchanges test traffic with the DUT. If the DUT is an AP, the partner is typically a client.
Figure 5: STACK-38P-TT throughput testbed block diagram (left); photos (right). The DUT is typically placed on a
turntable in the top box and the partner device resides in the bottom chamber coupled either via RF cabling or OTA.
Figure 6: PAL38-TT testbed. octoPal serves as the partner device eliminating the need for a second chamber.
octoPal is controllable via a web-browser or API, as described below. It is an embedded Linux device that
automatically runs a traffic endpoint, supporting several mainstream traffic generators, including octoScope’s
multiPerf, iperf, AT4 and IxChariot.
octoPal couples to the DUT over the air. Its RF ports connect via a quadAtten (Figure 6) or via an MPE2 (Figure 7) to
the antennas inside the DUT chamber.
Figure 7:
PAL testbed
configured
with MPE2 to
provide both
path loss and
multipath
between
octoPal and
the DUT.
The DUT and the partner device are connected either through a quadAtten or through an MPE2 multipath emulator.
Traffic generator software, such as octoScope’s multiPerf, iperf or IxChariot, is used to send traffic between the DUT
and the partner device via TCP/UDP/IP. If the DUT is a client (e.g. phone, tablet or PC), the partner is typically an
access point (AP) or a base station. If the DUT is an AP or a base station, the partner is typically a client. The traffic
flows between the partner and the DUT via an RF link formed by the octoBox testbed.
Figure 8:
Traffic is
controlled
by the
octoScope
automation
software,
which
supports
common
traffic
generators:
multiPerf,
iperf, and
IxChariot
You can run TCP/UDP/IP traffic between multiple pairs of devices. For example, when testing a phone, the traffic
endpoint can reside in the phone, as shown in Figure 9. In this example testbed, the phone can communicate with
any of the 3 eNBs or with the partner AP. The handoff/handover can be controlled by varying the path loss between
the phone and the 4 connected networks via programmable attenuators.
Figure 9: Example of a
handoff/handover test
configuration involving Wi-
Fi and cellular/LTE
networks.
To set up LOS conditions, we use either a stand-alone quadAtten or the attenuators built into the MPE2. For NLOS
conditions, the multipath subsystem of the MPE2 is switched in-line with the programmable attenuators, as shown in
Figure 11.
In a Wi-Fi test configuration where the partner device is coupled conductively and the DUT is coupled OTA, with the
two devices connected via LOS path with attenuators set to zero dB, the DUT’s RSSI is typically -20 to -30 dBm. This
is the top of the dynamic range of most Wi-Fi receivers.
When the MPE2 multipath subsystem is switched in (Figure 11), the wireless link matches an IEEE model of a typical
house with a broadband frequency response characterized by multipath nulls, as shown in Figure 12.
The nulls in the multipath response introduce an extra 25 to 30 dB of loss as measured by the receiver RSSI. This is
a typical loss across a wall in a house. In real life conditions, when devices are in the same room, LOS signal
dominates and when they are separated by one or more walls, NLOS signal dominates. The NLOS channel modeled
by the MPE2 multipath subsystem is shown in Figure 12.
How does the software transition from LOS and NLOS conditions while measuring throughput?
When making a throughput vs. range measurement, the octoScope software can increase LOS attenuation step by
step until it reaches the path loss of the multipath subsystem, for example from 0 dB to 30 dB. At this point, the
software switches the attenuators back to 0 dB and switches the multipath subsystem into the signal path so that the
RSSI at the DUT makes a smooth transition between LOS and NLOS conditions, as though we have been ‘moving’
the devices in the test link gradually away from one another and then across a wall from one another.
octoBox is the only wireless testbed on the market capable of this powerful measurement across the entire dynamic
range of the DUT and over both LOS and NLOS conditions.
With the MPE2 in the testbed, the total dynamic range of the RF link is about 90 dB. With only the quadAtten in the
testbed, the dynamic range of the RF link is 60 dB.
In real-life installations, particularly in apartment or office buildings, there may be 30 or more Wi-Fi networks in-range
of one another. The spectral skirts of adjacent channels can impact throughput, particularly if the signal in the test
channel is attenuated with respect to the interfering ACI (adjacent channel interference). Adding ACI or CCI (co-
channel interference) to the throughput testbed lets you qualify the impact of interference on throughput. The iGen
can generate common sources of interference, including Bluetooth, baby monitors, radar and other sources.
Traffic Interference,
example of 2 Bluetooth frequency hopping
adjacent channel interference
interferers
iGen has two subsystems: Wi-Fi and a frequency synthesizer, as shown in Figure 14 on the left. The Wi-Fi
subsystem is based on the most popular Qualcomm chipset that can be programmed to function as any legacy device
to replay captured traffic in any of the 802.11a/b/g/n/ac formats. The frequency synthesizer subsystem emulates
On/Off Keying (OOK) waveforms to model common interference, including pulsed waveforms, such as radar;
frequency hopping waveforms, such as Bluetooth and baby monitors; or swept waveforms such as microwave ovens.
iGen has a built-in RF switch to switch between the traffic and waveform interference and a built-in RF attenuator to
control the power of the interference.
Do the octoPal, quadAtten and iGen modules couple uncontrolled surrounding interference into the testbed?
octoPal is based on a popular Qualcomm chipset and can act as a client, AP or a test instrument. It is controllable via
a browser-based user interface and an open API (applications programming interface). The API enables you to
automate and easily sequence through important performance tests in the ideal conditions and in the presence of
controllable impairments. The octoPal datasheet provides further details.
Figure 16: octoPal browser-based user interface showing the available settings including the 802.11 interface type,
channel, priority, number of MIMO streams and other useful settings for a variety of test scenarios.
The iGen interference generator is also browser and API controllable, allowing you to create powerful automated test
scenarios and comprehensive test suites. See the iGen user interface screen shots below and refer to the iGen
datasheet for further details on the iGen interference gen
Figure 17: iGen browser-based user interface showing traffic setting menu on the left and waveform interference
settings on the right.
1. Reduce test time from weeks to Complete isolation and repeatable RF environment minimizes
hours time-consuming open-air testing. Test automation accelerates
data collection and improves test coverage and product quality.
2. Demonstrate highest achievable Ideal MIMO environment for highest possible throughput
performance Supports latest technologies, such as 160 MHz 802.11ac,
802.11ax, MU-MIMO, Beamforming, and beyond
3. Take meaningful measurements on Exercise programmable range of condition from best MIMO
real devices environment to challenging real-life impairments.
To learn more, view our instructional videos featuring the octoBox test configurations.
CONTACT
octoScope, Inc.
305 Foster Street
Littleton, MA 01460
Tel: +1.978.222.3114
[email protected]