MIMO Info (802.16 OFDMA)
(applies to
only)The STC Space Time Coding (STC) allows the transmitter to transmit signals (information) both in time and space, meaning the information is transmitted by two antennas at two different times consecutively./MIMO Multiple Input, Multiple Output: A physical layer (PHY) configuration in which both transmitter and receiver use multiple antennas. transmissions. The trace replaces the STC Info trace used in previous releases.
trace is a summary table of the single-value metrics relevant to multi-channelMeasurement Analysis of Multi-Antenna STC/MIMO DL-PUSC transmissions
The 89600 VSA only supports analysis of 2-Antenna STC/MIMO for DL Down Link (forward link: from base station to cell phone)-PUSC partial usage of subchannels: Some of the subchannels are allocated to the transmitter. regions, providing measurements of multi-antenna DL-PUSC transmissions. The measurement analysis provides the following information about your multi-antenna STC/MIMO transmissions:
- Verifies that the implemented pilot pattern is correct, and detect which antenna(s) are in the transmission.
- Provides metrics for transmitter chain characterization, including power, isolation, timing phase, and frequency.
- Provides transmitter quality metrics (PilotRCE, CPE).
- Provides regular RCE Relative Constellation Error is the RMS level of the Error Vector Magnitude, averaged over all subcarriers and all detected OFDM symbols. metrics for the active antenna (RCE, Data RCE, and other results which include data subcarriers will include cross channel impairments).
MIMO Info Summary Table Information:
The MIMO Info summary table provides the following STC/MIMO transmission metrics. Note that asterisks "***" will show for metrics associated with antennas not defined for the current STC mode.
|
Indicates the STC mode used by the analyzed zone (None, 2-Ant, 3-Ant, 4-Ant) are the possible values. This is either read from the DLMAP, or is present in the zone definition provided by the customer. |
|
Indicates the matrix type used by the analyzed zone (A, B, C) are the possible values. This is either read from the DLMAP, or is present in the zone definition provided by the customer. |
|
Indicates which antenna was used for the regular RCE analysis and results present on other traces. This is either determined by the user in the zone definition, or is auto-detected based on the power present in the unique pilot patterns assigned to each antenna. (Not applicable when Enable Matrix Decoder is enabled.) |
|
Indicates the data subcarrier power. (0 dB referenced to RefScPwr.) NOTE: When making measurements of data bursts which occupy fewer slots than allocated, the allocated-but-unoccupied slots will be used when computing DataScPwr. Therefore, if many slot are unoccupied, but allocated, the DataScPwr metric may appear lower than the per-subcarrier data power level if only the occupied slots were measured. This occurs automatically when an analyzed DL_PUSC data burst is detected as having allocated-but-unoccupied slots (relative to the decoded DL_MAP or the user-provided zone definition). |
|
Indicates the reference subcarrier power. RefScPwr is the RMS of the active DataSubcarriers excluding any known boosting levels. RefScPwr excludes the Pilot subcarriers (which are all boosted) and any unused subcarriers. |
|
Indicates the total power present in the pilot pattern defined for the specific antenna. |
|
Indicates the relative per-pilot-subcarrier power level. The reference level (0dB) is RefSCPwr. |
|
Indicates the residual constellation error observed on the unique pilot pattern for the specific antenna. This metric will only be computed for the active antenna. |
|
Indicates the RMS Common Pilot Error observed on the unique pilot pattern for the specified antenna. |
|
Indicates the relative timing offset between Tx/Rx paths. Tx0/Rx0 is the 0 sec reference. |
|
Indicates the relative phase offset between Tx/Rx paths. Tx0/Rx0 is the 0 deg reference. |
|
Symbol clock offset for each Tx/Rx path. |
|
Frequency Offset for each Tx/Rx path. |
See Also