Using Ruckus Custom Indicators

Packets captured on Ruckus APs include some information that is not available when capturing from other Wi-Fi devices. This additional information is stored in the Per-Packet Information (PPI) header that precedes the over-the-air content.
  1. The PPI:802.11-Common Header antenna signal and antenna noise fields of packets transmitted by the AP contain the next-to-lowest byte and the lowest byte, respectively, of the antenna pattern used to transmit the packet. On some APs, the pattern value may contain more significant bits, which are not stored in this header. If the packet is 802.11n, it will also contain the full antenna pattern value in the header described below.
  2. The PPI:802.11n-MAC+PHY Header EVM-3 field of packets transmitted by the AP contains the full antenna pattern used to transmit the packet (similar to above, except this 32-bit field can accommodate the complete value).
  3. The PPI:802.11n-MAC+PHY Header MAC Flags field’s upper bits convey additional TX and RX descriptor indicators described in the table below.

Ruckus-defined indicators conveyed in MAC Flags

TX Indicator Bit RX Indicator
Sounding (0=not; 1=yes) 31 Sounding (0=not; 1=yes)
TxBF (0=not applied; 1=yes) 30 unassigned
Ness (#ext spatial streams) 28-29 Ness (#ext spatial streams)
STBC (0=not applied; 1=yes) 27 STBC (0=not applied; 1=yes)
LDPC (0=not applied; 1=yes) 26 LDPC (0=not applied; 1=yes)
LDPC indicator valid 25 LDPC indicator valid
unassigned 24 unassigned
RTS HTC TRQ 23 HW Upload Data
RTS HTC MRQ 22 HW Upload Data Valid
RTS HTC MSI 20-21 HW Upload Data Type
RTS enabled 19 unassigned
Calibrating 18 unassigned

Limitation: The AP can report RX EVM values or the RX LDPC indicator, but not both. When packet capture is invoked from the ZD UI, the software selects RX EVM values. Therefore, the RX LDPC indicator is not reported, and the LDPC indicator valid bit will be zero. The RX LDPC indicator is available when invoking packet capture from the AP command line interface.