0% found this document useful (0 votes)
25 views

ADS and SystemVue Integration

Uploaded by

BUNNGA SARITH
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
25 views

ADS and SystemVue Integration

Uploaded by

BUNNGA SARITH
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 171

Advanced Design

System 2020

ADS and SystemVue Integration

PDF Generated on
Apr 07, 2019
Notices
© Keysight Technologies Incorporated, 2002-2019

1400 Fountaingrove Pkwy., Santa Rosa, CA 95403-1738, United States All rights reserved.

No part of this documentation may be reproduced in any form or by any means (including electronic storage
and retrieval or translation into a foreign language) without prior agreement and written consent from
Keysight Technologies, Inc. as governed by United States and international copyright laws.

Restricted Rights Legend


If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is
delivered and licensed as "Commercial computer software" as defined in DFAR 252.227-7014 (June 1995),
or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in
FAR 52.227-19 (June 1987) or any equivalent agency regulation or contract clause.

Use, duplication or disclosure of Software is subject to Keysight Technologies' standard commercial license
terms, and non-DOD Departments and Agencies of the U.S. Government will receive no greater than
Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no
greater than Limited Rights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b)(2)
(November 1995), as applicable in any technical data.

Portions of this software are licensed by third parties including open source terms and conditions.

For detail information on third party licenses, see Notice.


ADS and SystemVue Integration

Contents
ADS and SystemVue Integration ..................................................................................................... 6
Install VTB ......................................................................................................................................6
Uninstall VTB .................................................................................................................................6
ADS and SystemVue Compatibility ...............................................................................................6
Contents.........................................................................................................................................6
Verification Test Bench.................................................................................................................... 7
Verification Test Bench (VTB) and Verification Test Bench (VTB) Component ............................7
Creating VTBs ............................................................................................................................. 7
Built-in VTB Components ........................................................................................................... 7
Customized VTB Components .................................................................................................... 8
Selecting and Placing the VTB Components ............................................................................. 9
Specifying the VTB Component Parameters.............................................................................. 9
Viewing the VTB Property Summary ........................................................................................ 10
Linking to the Envelope Controller ........................................................................................... 12
5G Advanced Modem Workspaces .............................................................................................15
5G Advanced Modem Workspaces .......................................................................................... 15
FBMC_Rx_AWGN ...................................................................................................................... 17
FBMC_Tx ................................................................................................................................... 20
FBMC_Tx_Source ...................................................................................................................... 25
3GPP_NR_DL_Tx ....................................................................................................................... 27
3GPP_NR_DL_Tx_Source .......................................................................................................... 33
3GPP_NR_UL_Tx ....................................................................................................................... 36
3GPP_NR_UL_Tx_Source .......................................................................................................... 42
Bluetooth Workspaces ................................................................................................................45
Bluetooth Workspaces ............................................................................................................. 45
Bluetooth_BDR_Source ............................................................................................................ 47
Bluetooth_BDR_Tx .................................................................................................................... 50
Bluetooth_CoACInterferencePerformance ............................................................................... 53
Bluetooth_EDR_Sensitivity ....................................................................................................... 56
Bluetooth_EDR_Source............................................................................................................. 59
Bluetooth_EDR_Tx..................................................................................................................... 62

3
ADS and SystemVue Integration

Bluetooth_LE_Source................................................................................................................ 65
Bluetooth_LE_Tx........................................................................................................................ 68
Bluetooth_withWLANInterference............................................................................................ 71
Communications Workspaces .....................................................................................................74
Communications Workspaces .................................................................................................. 74
ACPR_Measurement ................................................................................................................. 75
EVM_Measurement ................................................................................................................... 77
QAM16_SER_vs_EbNo .............................................................................................................. 79
DigitalMod Workspaces...............................................................................................................82
DigitalMod Workspaces............................................................................................................ 82
DigitalMod_Tx ........................................................................................................................... 83
DigitalMod_Tx_Source .............................................................................................................. 87
LTE Advanced Workspaces..........................................................................................................89
LTE Advanced Workspaces....................................................................................................... 89
LTE_Advanced_BS_CA_Tx ......................................................................................................... 90
LTE_Advanced_BS_CA_Tx_Source ............................................................................................ 94
LTE Workspaces ...........................................................................................................................97
LTE Workspaces ........................................................................................................................ 97
3GPP_LTE_BS_AdjacentChannelSelectivity ............................................................................. 99
3GPP_LTE_BS_InChannelSelectivity....................................................................................... 102
3GPP_LTE_BS_ReferenceSensitivity....................................................................................... 105
3GPP_LTE_BS_Tx..................................................................................................................... 108
3GPP_LTE_BS_Tx_Source ....................................................................................................... 112
3GPP_LTE_UE_AdjacentChannelSelectivity ........................................................................... 115
3GPP_LTE_UE_ReferenceSensitivity....................................................................................... 118
3GPP_LTE_UE_Tx..................................................................................................................... 121
3GPP_LTE_UE_Tx_Source ....................................................................................................... 124
NB IoT Workspaces....................................................................................................................126
NB IoT Workspaces................................................................................................................. 126
LTE_Advanced_NBIoT_DL_Tx .................................................................................................. 127
LTE_Advanced_NBIoT_UL_Tx .................................................................................................. 129
RADAR Workspaces...................................................................................................................131
RADAR Workspaces................................................................................................................ 131

4
ADS and SystemVue Integration

Radar_Tx Analysis ................................................................................................................... 132


Radar_Tx_Source .................................................................................................................... 137
WLAN 11ac Workspaces ...........................................................................................................139
WLAN 11ac Workspaces ........................................................................................................ 139
WLAN_802.11ac_AdjacentChannelRejection ........................................................................ 141
WLAN_802.11ac_NonadjacentChannelRejection .................................................................. 143
WLAN_802.11ac_ReferenceSensitivity .................................................................................. 145
WLAN_802.11ac_Tx ................................................................................................................ 147
WLAN_802.11ac_Tx_Source ................................................................................................... 150
WLAN 11ad Workspaces ...........................................................................................................152
WLAN 11ad Workspaces ........................................................................................................ 152
WLAN_11ad_RxSensitivity...................................................................................................... 153
WLAN_11ad_Tx ....................................................................................................................... 157
WLAN_11ad_Tx_Source .......................................................................................................... 160
RF-SystemVue Co-simulation ..................................................................................................... 163
RF-SystemVue Co-simulation ...................................................................................................163
Basic Co-simulation................................................................................................................ 164
Advanced Co-simulation ........................................................................................................ 168
Model Export................................................................................................................................ 169
Model Export..............................................................................................................................169
Exporting Fast Circuit Envelope Models....................................................................................170
Exporting Fast Circuit Envelope Models................................................................................. 170

5
ADS and SystemVue Integration

ADS and SystemVue Integration


Keysight EEsof provides a way to combine the capabilities of ADS and SystemVue. The following
features are supported:
Create VTBs in SystemVue to be used in GoldenGate and ADS to verify the performance of the circuit.
Enable the circuit designers to make use of sources and measurement setups from SystemVue.

Install VTB
From ADS 2017, to install files that are required for the VTB functionality you need to download a
separate VTB installer (for Windows only). For Linux, the VTB installer is bundled with ADS installer.
It is recommended to download compatible ADS and VTB installers to the same directory. After the
download, run the ADS installer. This process will automatically install the VTB functionality.
If you have already installed ADS and find VTB functionality is missing, then you need to download and
install the VTB.

Uninstall VTB
When you uninstall ADS, the VTB add-on is also uninstalled.

ADS and SystemVue Compatibility


The following table lists the compatible versions of ADS and SystemVue.

ADS Version SystemVue Version

2016.01 2015.01

2017 2016.08

2017 Update 1 2018

2019 2018

2019 Update 1 2018 Update 1

Contents
Verification Test Bench
RF-SystemVue Co-simulation
Model Export

Related Topics
Using Verification Test Benches (VTBs) Example

6
ADS and SystemVue Integration

Verification Test Bench

Verification Test Bench (VTB) and Verification Test Bench (VTB)


Component
The Verification Test Bench (VTB) is a SystemVue Data Flow design in a SystemVue workspace. The
Verification Test Bench (VTB) component is a regular component in the ADS simulation
environment, which is linked to the Verification Test Bench (VTB) in the SystemVue. VTBs enable
the circuit designer to make use of sources and measurement setups from SystemVue and verify the
performance of a circuit using real world complex modulated signals conforming to advanced
wireless standards such as 2G/3G/4G/5G.

From ADS 2017, to install files that are required for the VTB functionality you need to download a
separate VTB installer (for Windows only). For Linux, the VTB installer is bundled with ADS installer.
It is recommended to download compatible ADS and VTB installers to the same directory. After the
download, run the ADS installer. This process will automatically install the VTB functionality.
If you have already installed ADS and find VTB functionality is missing, then you need to download and
install the VTB.

Creating VTBs
VTBs are created by a system designer in a compatible SystemVue environment and then used by a
circuit designer working in ADS . For information on how to create a VTB, refer to the SystemVue
documentation.

For the list of compatible versions, see ADS and SystemVue Compatibility.

In a schematic design, you can use only one VTB at a time. Using more than one VTB displays the
following error message “Envelope 'VTB1_Env': multiple VTB components are found in the design, VTB1,
VTB2”.

Built-in VTB Components


ADS provides some built-in VTB components for the standard wireless standards from SystemVue.
They can be accessed from the component palette list or the component library browser in a
Schematic view . Following are the list of built-in VTBs available with ADS:
5G Advanced Modem Workspaces
Bluetooth Workspaces
Communications Workspaces
DigitalMod Workspaces
LTE Advanced Workspaces
LTE Workspaces
NB IoT Workspaces

7
ADS and SystemVue Integration

RADAR Workspaces
WLAN 11ac Workspaces
WLAN 11ad Workspaces

The corresponding SystemVue workspaces for these builtin-VTB components are installed in your
$HPEESOF_DIR/SystemVue.

Customized VTB Components


You can create VTBs in a compatible SystemVue and then use it in your design. For more
information on how to create VTBs, refer to Creating a VTB in the SystemVue documentation. For
the list of compatible versions, see ADS and SystemVue Compatibility.

It is recommended to run the VTB in SystemVue before integration. For running the VTB, you may
need to bypass the SVE_Link device. Reset the SVE_Link device state before saving the VTB file to
be used in ADS.

Each VTB is represented as a single file. After the VTB creation, the file is stored in a directory from
where it can be read/accessed to be used in the design.

Importing Customized VTBs

To import a custom VTB, do the following:


1. Click the Library view tab from the ADS Main window.
Select a Library and right-click to select Configure Library.
or
Select DesignKits > Manage Libraries from the ADS Main window.
Click Configure Library from the Manage Libraries dialog box.
The Library Configuration Editor dialog box is displayed.
2. Click the VTB tab.

3. Click Browse or specify the VTB file name (*.wsv) associated with the library.
If the VTB exists, the Import this VTB option will be automatically enabled and selected.

8
ADS and SystemVue Integration

4. Click Apply followed by OK.


The VTB will be added in the library as a symbol view.
You can import only one *.wsv file per library. If a library already contains custom VTB
components, and you want to import another *.wsv file into the same library, you will be
prompted to delete the existing VTB components in that library. If you do not want to delete
them, you need to create a new library to import the *.wsv file.

Selecting and Placing the VTB Components


For the built-in VTB components, do the following:
Select and place a VTB component through the component palette list.
or
Select Insert > Component> Component Library.
The Component Library window is displayed.
Select and place a VTB component from the ads_verification_test_bench library available under
the ADS Analog/RF Libraries.

For the customized VTB components, do the following:


Enter the VTB name in the Component History and press Enter in the Schematic view.
Click to place the VTB at the desired location in the design.
or
Expand the custom Library cell and drag-drop the VTB at the desired location in the design.

Specifying the VTB Component Parameters


After placing the VTB component, double-click to view the VTB-specific parameters under the
Parameters tab as shown in the following figure.

9
ADS and SystemVue Integration

For information on each of the parameters, see the parameters section of the built-in VTB
components. You can either specify a value or use equation, nominal, sweep, optimization, or
statistical design variables with nominal value to set the VTB parameters.

Viewing the VTB Property Summary


The VTB associated properties are displayed under the VTB Summary tab as shown in the following
figure.

10
ADS and SystemVue Integration

It indicates the SystemVue workspace, the design flow analysis, and the test description. It also lists
the port properties and you can query the carrier frequency of the ports from the SystemVue
engine.

The following table describes the options available under the VTB Summary tab.

Option Description

Filename and path Displays the SystemVue workspace name and location.

Analysis name Displays the VTB name, which is the data flow analysis name in the
SystemVue workspace.

VTB description Displays the description of the Verification Test Bench.

11
ADS and SystemVue Integration

Option Description

Calculate Port's Carrier Frequency Query the port's carrier frequencies from the SystemVue Engine. It is
an expensive calculation, which blocks the UI until it finishes. The
calculation is not available if the parameters contain expressions.

Name Name of the ports.

Type Type of the ports, either is input or output.

PortZ Impedance of the ports. It can be modified in the Parameters tab.

FCarrier Carrier frequency of the ports.

Sample Rate Sample rate of the ports.

Linking to the Envelope Controller


The Envelope Controller tab is used to link the VTB with the Envelope controller for the
cosimulation. It will set up Envelope controller with the fundamental frequencies as the port's

12
ADS and SystemVue Integration

carrier frequencies.

To place the Envelope Controller, click Insert Envelope Controller on Schematic. The following
steps will take place:
Before placing the controller, the simulator checks whether there are any active Envelope controllers
on the schematic. If an active Envelope controller already exists on the schematic, Remove Envelope
Controllers dialog box is displayed. It allows you to either keep the existing controller or insert a new

13
ADS and SystemVue Integration

one.

Calculate the port's carrier frequencies if required (for example, you modified the parameters).
Once the port's carrier frequencies are available, Insert Envelope Controller dialog box is displayed
with default fundamentals for the controller. If the port's carrier frequencies are the same, there will be
only one fundamental for Envelope controller by default. Otherwise, there will be multiple
fundamentals, each one corresponding to one port's carrier frequency.

After you click OK, an Envelope controller with initial fundamental setup will be inserted on the
schematic. Select Do not show this dialog again to avoid the dialog box to be displayed again.

See Also

Using Verification Test Benches (VTBs)


Example

14
ADS and SystemVue Integration

5G Advanced Modem Workspaces

5G Advanced Modem Workspaces


VTB workspaces are provided to analyze FBMC transmitter and receiver characteristics respectively

Tx
Transmitter characteristics
FBMC_Tx
FBMC_Tx_Source
3GPP_NR_DL_Tx
3GPP_NR_DL_Tx_Source
3GPP_NR_UL_Tx
3GPP_NR_UL_Tx_Source

Rx
Receiver characteristics
FBMC_Rx_AWGN

In current implementation, there are only one input port and one output port in the SVE_Link model
used in LTE workspaces, which means the DUT (design in ADS/GoldenGate environment) should only
have one input and one output. In Tx examples, the DUT is connected after the modulator. In Rx
examples, the DUT is connected before the demodulator in the Rx chain. Please refer to the help
document of each workspace for more information. in which you can find the detailed schematic.

How to set SVE_Link properties in LTE workspaces

Users can optionally define the SVE_Link properties by setting DefineProperties to YES.
When DefineProperties is set to YES, parameters related to SVE_Link properties,
including InFeedbackLoop, SampleRate, and InputFcs, can be defined by values or expressions.
InFeedbackLoop: Specify whether the SVE_Link is in a feedback loop: NO, YES. In current FBMC
examples, there is no feedback loop, hence InFeedbackLoop is set to NO.
SampleRate: Sample rate of the signal. In FBMC examples, in the Equations tab of the
design, SamplingRate of the FBMC system is calculated from SampleRate and OversampRatio.
InputFcs: Array of characterization frequencies of input envelope signals. In current FBMC examples,
there is only one input port in SVE_Link model, hence InputFcs is set to [FCarrier_In].

Otherwise, when DefineProperties is set to NO, the VTB process will analyze the full design and
provide such information to the integrating tool.

15
ADS and SystemVue Integration

References
1. PHYDYAS, “FBMC physical layer: a primer”, June 2010.
2. 5GNOW_D3.1_v1.0, “5G Waveform Candidate Selection D3.1”, Nov. 2013.

16
ADS and SystemVue Integration

FBMC_Rx_AWGN

5G_FBMC_Rx_AWGN_Analysis
This workspace provides a VTB test bench to measure the performance of FBMC receiver in AWGN
channel.
A simple design to use this VTB is shown below.

17
ADS and SystemVue Integration

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

In order to see attenuation of the spectrum, the OversampleRatio parameter is used to define
oversample ratio.

The number of simulated frames is set by parameter NumFrames.

Parameter Details
1. FBMC Parameters
SNR: Signal to noise ratio used for BER measurement.
NumFrames: Number of FBMC frames for simulation.
2. Advanced Parameters
The following parameters are not exposed in ADS/GoldenGate environment. The default values
of these parameters will be used in simulation. To change them, please open the workspace in
SystemVue, go to the Parameters tab of the design and change the Default Value there.

NumEqualizerTaps: Number of taps used in equalization for which 0 for one tap, 1 for two taps and
2 for three taps.
Tmax: The maximum delay of multipath and the unit of it is second.
Fmax: The maximum Doppler frequency and the unit of it is Hz.
PhaseTrackingEnable: Using pilot to do phase tracking or not. PhaseTrackingEnable should be
disabled when PilotEnable is set to No.
For detail on other parameter, please refer to FBMC_Tx.

Simulation Results

Try to change the parameters, run 5G_FBMC_Rx_AWGN_Analysis and check the simulation results.
Graph Spectrum shows the spectrum of the transmitted signal
Graph Constellation shows the constellation of the demodulation FBMC signal
Table BER lists the BER of FBMC receiver when SNR = 10

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation. The DUT is shorted to get the following ideal results. The same results
will be displayed in SystemVue environment if the SVE_Link model is disabled to short.

18
ADS and SystemVue Integration

Reference
1. PHYDYAS, “FBMC physical layer: a primer”, June 2010
2. 5GNOW_D3.1_v1.0, “5G Waveform Candidate Selection D3.1”, Nov. 2013

19
ADS and SystemVue Integration

FBMC_Tx

5G_FBMC_Tx_Analysis
This VTB design provides a VTB test bench to measure the FBMC transmitter characteristics
including spectrum, waveform and CCDF.
A simple design to use this VTB is shown below.

20
ADS and SystemVue Integration

The center frequency of the input signal to DUT( SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

In order to see attenuation of the spectrum, the OversampleRatio parameter is used to define
oversample ratio.

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. FBMC Parameters
SampleRate: basic sample rate without oversample in FBMC system
ModeType: modulation type of constellation.
IdleInterval: idle time at the begin of each frame and the units is second.
OversampleRatio: Over-sampling ratio option. Oversampling ratio 1, ratio 2, ratio 4, ratio 8, ration
16, ratio 32 and ration 64 are supported in this downlink source
3. Advanced Parameters
The following parameters are not exposed in ADS/GoldenGate environment. The default values
of these parameters will be used in simulation. To change them, please open the workspace in
SystemVue, go to the Parameters tab of the design and change the Default Value there.

PilotEnable: Whether use pilots in data symbols or not.


PilotIndex: To set the index of subcarriers in data symbols used for pilot when PilotEnable is set to
Yes.
PilotSequese: Pilot value sequence and active only when PilotEnable is set to Yes. The length of it
should be equal to the length of PilotIndex.
FilterOverlapFactor: Filter overlap factor for FBMC systems.
FilterCoef: Filter coefficients of the filter bank used in FBMC systems. The length of FilterCoef
should be equal to FilterOverlapFactor.
ZC_RootIndex1: Root index for the first ZC sequence used in this example.
ZC_RootIndex2: Root index for the second ZC sequence used in this example.
FilterBankStructure: Two filter bank implementation structures could be used in FBMC systems. And
0 is for Extended_IFFT and 1 is for PPN_IFFT.
NumPreambleSyms: Number of preamble symbols in one frame.
NumDateSyms: Number of preamble symbols in one frame.
NumSubcarriers: Number of subcarriers in one preamble symbol or in one data symbol.
ActiveSubcAlloc: Active subcarriers index in data symbols.

21
ADS and SystemVue Integration

Simulation Results

Try to change the parameters, run 5G_FBMC_Tx_Analysis and check the simulation results.
Graph Spectrum shows the spectrum of the transmitted signal
Graph CCDF shows the Complementary Cumulative Distribution Function of the transmitted signal.
Graph Waveform shows the transmitted time domain waveform

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation. The DUT is shorted to get the following ideal results. The same results
will be displayed in SystemVue environment if the SVE_Link model is disabled to short.

22
ADS and SystemVue Integration

23
ADS and SystemVue Integration

Reference
1. PHYDYAS, “FBMC physical layer: a primer”, June 2010
2. 5GNOW_D3.1_v1.0, “5G Waveform Candidate Selection D3.1”, Nov. 2013

24
ADS and SystemVue Integration

FBMC_Tx_Source

5G_FBMC_Tx_Source_Analysis
This workspace provides a VTB test bench to generate the FBMC transmitter signal.
A simple design to use this VTB is shown below.

25
ADS and SystemVue Integration

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

In order to see attenuation of the spectrum, the OversampleRatio parameter is used to define
oversample ratio.

Parameter Details

For details on other parameters, please refer to FBMC_Tx.

Simulation Results

Try to change the parameters, run 5G_FBMC_Tx_Source_Analysis and check the simulation results.
Graph Spectrum shows the spectrum of the transmitted signal

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

Reference
1. PHYDYAS, “FBMC physical layer: a primer”, June 2010.
2. 5GNOW_D3.1_v1.0, “5G Waveform Candidate Selection D3.1”, Nov. 2013.

26
ADS and SystemVue Integration

3GPP_NR_DL_Tx

NR_DL_Tx_Analysis

This workspace provides a VTB test bench to measure 3GPP new radio (NR) transmitter

characteristics including spectrum, waveform, CCDF, EVM.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.

RF distortions in the modulator can be simulated by setting parameters GainImbalance,


PhaseImbalance, etc.

27
ADS and SystemVue Integration

There is no SSB for Numerology 2 (60kHz) according to the specification. And SSB for 240kHz is not
supported now. When the Numerology is set 2 and 4, SSB_Enable should be set to NO.
Synchronization is done using different pilot according to SyncType. Please do not use SSB to do
synchronization when SSB_Enable is set to NO and it is the same case for PDSCH_DMRS. BWP is
defined occupy the whole bandwidth of component carrier. Frequency location of SSB in
component carrier are defined by SSB_RBOffset. SSB RB offset is according to the beginning of
component carrie. RB offset of SSB is based on 15kHz for Numerology 0 and Numerology1, and
based on 60kHz for Numerology 3 which is defined in specification 38.211. PDSCH_RBOffset and
PDSCH_NumRBs define the frequency location of PDSCH in BWP. PDSCH RB offset is according to
the beginning of BWP. Please make sure BWP and SSB is in the component carrier
(CarrierNumRBs) and PDSCH is in the BWP. A low pass filter is added in EVM model and and the
bandwidth of this filter is set as the same of bandwidth of component carrier.

SignalPower is defined the power of PDSCH, if SSB is in the location of PDSCH, SignalPower equals
to the power of the transmitter. If SSB is outside PDSCH, signal power of transmitter is a bit bigger
than SignalPower.

The number of simulated frames for EVM measurements is set by parameter NumFrames.

The measurement length of EVM model is set to one frame.

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. LTE Parameters
CarrierNumRBs: Number of RBs in one component carrier based on specific numerology
OversamplingOption: Over-sampling ratio option.
Numerology: Numerology for BWP, support one numerology now
SSB_Enable: SS/PBCH bolck enable or not
SSB_RBOffset: The starting RB index of resource blocks allocated to SS/PBCH bolck in the whole
bandwidth based on 15kHz or 60kHz
SSB_Lmax: Number of SS/PBCH bolck candidates for a half frame with SS/PBCH bolcks.
PDSCH_Enagle: Enable or disable PDSCH and its DMRS transmission
PDSCH_RBOffset: The starting RB index of resource blocks allocated to the user
PDSCH_NumRBs: Number of resource blocks(RBs) for each PDSCH
Modulation: Modulation orders in each slot(1:QPSK;2:16QAM;3:64QAM;4:256QAM)
SyncType: Synchronization type, synchronization by SSB or by PDSCH_DMRS
NumFrames: Number of frames for EVM measurement
ReportEVMIndB: specifies the EVM units in dB or not and is only valid for the result in dataset

28
ADS and SystemVue Integration

Advanced Parameters
The following parameters are not exposed in ADS/GoldenGate environment. The default values
of these parameters will be used in the simulation. To change them, please open the workspace
in SystemVue, go to the Parameters tab of the design and change the Default Value there. To
expose them to ADS/GoldenGate environment, please also open the workspace in SystemVue,
go to Parameters tab and change the Hide Condition to false or simply delete the Hide
Condition.

BWP_RBOffset: The starting RB index of resource blocks allocated to every BWP in the whole
bandwidth. The default value is set to 0. Please also update the value of BWP_NumRBs, because the
default of BWP_NumRBs is set to CarrierNumRBs.
SSB_Periodicity: SS/PBCH block transmission period. The default value is set to 5 ms. Active, only
when SSB_Enable is set to YES.
PDSCH_StartOFDMSym: The index for the first OFDM symbol allocated to each PDSCH. The default
value is set to 0.
PDSCH_NumOFDMSyms: Number of OFDM symbols for each PDSCH. The default value is set to 14.
PDSCH is occupy all symbols in the slots.

Simulation Results

Try to change the parameters, run NR_DL_Tx_Analysis and check the simulation results.
Graph CCDF shows the Complementary Cumulative Distribution Function of the transmitted signal
Graph Constellation shows the constellation of each physical channel and signal. The constellation of
PDSCH, PBCH, PSS and SSS are included. PDSCH DMRS is shown in PDSCH channel and PBCH DMRS
is shown in PBCH. If Modulation is changed, please select different input for PDSCH constellation.
Table Error Summary shows average EVM, peak EVM, frequency errors and other measured results of
each frame got from EVM model
Table EVM lists EVM of each physical channel and signal
Graph NormalizedEqualizerChannelFrequencyResponse shows the normalized equalizer channel
frequency response got from EVM model for all valid subcarrier of PDSCH and SSB. It is the average
channel frequency response in one slot which means the value on one subcarrier is the average of all
values on that subcarrier in all symbols in one slot.
Graph Spectrum shows the spectrum of the transmitted signal
Graph Waveform shows the transmitted time domain waveform

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation. The DUT is shorted to get the following ideal results. The same results
will be displayed in SystemVue environment if the SVE_Link model is disabled to short.

29
ADS and SystemVue Integration

30
ADS and SystemVue Integration

31
ADS and SystemVue Integration

Reference
1. 3GPP TS 38.211 v15.0.0 "Physical Channels and Modulation", Dec. 2017.

32
ADS and SystemVue Integration

3GPP_NR_DL_Tx_Source

NR_DL_Tx_Source_Analysis

This workspace provides a VTB test bench to generate 3GPP new radio (NR) downlink signal.

The schematic of the design is shown below.

The centre frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while centre frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.

33
ADS and SystemVue Integration

RF distortions in the modulator can be simulated by setting parameters GainImbalance,


PhaseImbalance, etc.

There is no SSB for Numerology 2 (60kHz) according to the specification. And SSB for 240kHz is not
supported now. When the Numerology is set 2 and 4, SSB_Enable should be set to NO. BWP is
defined occupy the whole bandwidth of component carrier. Frequency location of SSB in
component carrier are defined by SSB_RBOffset. SSB RB offset is according to the beginning of
component carrie. RB offset of SSB is based on 15kHz for Numerology 0 and Numerology1, and
based on 60kHz for Numerology 3 which is defined in specification 38.211. PDSCH_RBOffset and
PDSCH_NumRBs define the frequency location of PDSCH in BWP. PDSCH RB offset is according to
the beginning of BWP. Please make sure BWP and SSB is in the component carrier
(CarrierNumRBs) and PDSCH is in the BWP. A low pass filter is added in EVM model and and the
bandwidth of this filter is set as the same of bandwidth of component carrier.

SignalPower is defined the power of PDSCH, if SSB is in the location of PDSCH, SignalPower equals
to the power of the transmitter. If SSB is outside PDSCH, signal power of transmitter is a bit bigger
than SignalPower.

A sink is used to save the generate signal from 0 to TimeStop.

Parameter Details
TimeStop: Stop time of data collection. Range: (0:+∞)
For details on other parameters, please refer to 3GPP_NR_DL_Tx.

Simulation Results

Try to change the parameters, run NR_DL_Tx_Source_Analysis and check the simulation results.
Graph Waveform shows the transmitted time domain waveform

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

34
ADS and SystemVue Integration

Reference
1. 3GPP TS 38.211 v15.0.0 "Physical Channels and Modulation", Dec. 2017.

35
ADS and SystemVue Integration

3GPP_NR_UL_Tx

NR_UL_Tx_Analysis

This VTB design measures 3GPP 5G NR uplink transmitter characteristics, including spectrum,
waveform, CCDF, and EVM according to 3GPP TS 38.101.

The schematic of the design is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT(SVE_Link in the design) is set by
FCarrier_Out.

36
ADS and SystemVue Integration

RF distortions in the modulator can be simulated by setting parameters GainImbalance,


PhaseImbalance, etc.

The signal's full bandwidth is determined by CarrierNumRBs and Numerology. Bandwidth =


CarrierNumRBs * 12 * 15kHz * 2^Numerology. PUSCH can take entire or partial of the bandwidth,
whose loaction is defined by PUSCH_RBOffset and PUSCH_NumRBs. Note, PUSCH_RBOffset +
PUSCH_NumRBs should not be greater than CarrierNumRBs.

Modulation determines the modulation format.

The number of simulated frames for EVM measurements is set by NumFrames.

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
Power: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
2. NR Parameters
CarrierNumRBs: Number of RBs in one component carrier based on specific numerology
OversamplingOption: Over-sampling ratio option.
Numerology: Numerology for BWP, support one numerology now
PUSCH_RBOffset: The starting RB index of resource blocks allocated to the PUSCH
PUSCH_NumRBs: Number of resource blocks(RBs) for the PUSCH
Modulation: Modulation orders in each slot(0:pi/4 BPSK;1:QPSK;2:16QAM;3:64QAM;4:256QAM)
NumFrames: Number of frames for EVM measurement.
ReportEVMIndB: The EVM unit in dB or percentage.

Simulation Results

Try to change the parameters, run NR_UL_Tx_Analysis and check the simulation results.
Graph CCDF shows the Complementary Cumulative Distribution Function of the transmitted signal
Graph Constellation shows the constellation of PUSCH.
Table Error Summary shows average EVM(dB), peak EVM(dB), frequency errors(Hz), IQ Offset(dB),
Symbol Clock Error, Sync Correlation and Time Offset(s) of PUSCH.
Table EVM shows average EVM in dB of PUSCH and DMRS of PUSCH.
Graph NormalizedEqualizerChannelFrequencyResponse shows the normalized equalizer channel
frequency response of PUSCH.
Graph Spectrum shows the spectrum of the aggregated signal
Graph Waveform shows the transmitted time domain waveform

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation. The DUT is shorted to get the following ideal results. The same results
will be displayed in SystemVue environment if the SVE_Link model is disabled to short.

37
ADS and SystemVue Integration

38
ADS and SystemVue Integration

39
ADS and SystemVue Integration

References
1. 3GPP TS 38.211 v15.0.0, "Physical Channels and Modulation", December 2017.
2. 3GPP TS 38.211 v1.2.0, "Physical Channels and Modulation", November 2017.
3. 3GPP TS 38.212 v15.0.0, "Multiplexing and channel coding", December 2017.
4. 3GPP TS 38.213 v15.0.0, "Physical layer procedures for control", December 2017.
5. 3GPP TS 38.214 v15.00, "Physical layer procedures for data", December 2017

40
ADS and SystemVue Integration

6. 3GPP TS 38.101 v15.0.0, "User Equipment(UE) radio transmission and reception", December 2017.

41
ADS and SystemVue Integration

3GPP_NR_UL_Tx_Source

NR_UL_Tx_Source_Analysis

This VTB design displays 3GPP 5G NR uplink transmitting signal.

The schematic is shown below,

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT(SVE_Link in the design) is set by
FCarrier_Out.

42
ADS and SystemVue Integration

The signal's full bandwidth is determined by CarrierNumRBs and Numerology. Bandwidth =


CarrierNumRBs * 12 * 15kHz * 2^Numerology. PUSCH can take entire or partial of the bandwidth,
whose loaction is defined by PUSCH_RBOffset and PUSCH_NumRBs. Note, PUSCH_RBOffset +
PUSCH_NumRBs should not be greater than CarrierNumRBs.

Modulation determines the modulation format.

The number of frames to output is set by NumFrames.

RF distortions in the modulator can be simulated by setting parameters GainImbalance,


PhaseImbalance, etc.

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
Power: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
2. NR Parameters
CarrierNumRBs: Number of RBs in one component carrier based on specific numerology
OversamplingOption: Over-sampling ratio option.
Numerology: Numerology for BWP, support one numerology now
PUSCH_RBOffset: The starting RB index of resource blocks allocated to the PUSCH
PUSCH_NumRBs: Number of resource blocks(RBs) for the PUSCH
Modulation: Modulation orders in each slot(0:pi/4 BPSK;1:QPSK;2:16QAM;3:64QAM;4:256QAM)
NumFrames: Number of frames for waveform.

Simulation Results

Try to change the parameters, run NR_UL_Tx_Source_Analysis and check the graph of
Waveform which shows the transmitted time domain waveform

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

43
ADS and SystemVue Integration

References
1. 3GPP TS 38.211 v15.0.0, "Physical Channels and Modulation", December 2017.
2. 3GPP TS 38.211 v1.2.0, "Physical Channels and Modulation", November 2017.
3. 3GPP TS 38.212 v15.0.0, "Multiplexing and channel coding", December 2017.
4. 3GPP TS 38.213 v15.0.0, "Physical layer procedures for control", December 2017.
5. 3GPP TS 38.214 v15.00, "Physical layer procedures for data", December 2017

44
ADS and SystemVue Integration

Bluetooth Workspaces

Bluetooth Workspaces
VTB workspaces are provided to analyze Bluetooth transmitter and receiver characteristics
according to [1] [2] and [3]

Tx
Bluetooth_BDR_Source

Bluetooth_BDR_Tx

Bluetooth_EDR_Source

Bluetooth_EDR_Tx

Bluetooth_LE_Source

Bluetooth_LE_Tx

Rx
Bluetooth_CoACInterferencePerformance

Bluetooth_EDR_Sensitivity

Bluetooth_withWLANInterference

In current implementation, there are only one input port and one output port in the SVE_Link model
used in Bluetooth workspaces, which means the DUT (design in ADS/GoldenGate environment) should
only have one input and one output. In Tx examples, the DUT is connected after the modulator. In Rx
examples, the DUT is connected before the demodulator in the Rx chain. Please refer to the help
document of each workspace for more information. in which you can find the detailed schematic.

How to set SVE_Link properties in Bluetooth workspaces


Users can optionally define the SVE_Link properties by setting DefineProperties to YES. When
DefineProperties is set to YES, parameters related to SVE_Link properties, including
InFeedbackLoop, SampleRate, and InputFcs, can be defined by values or expressions.
InFeedbackLoop: Specify whether the SVE_Link is in a feedback loop: NO, YES. In WLAN 802.11ac
examples, there is no feedback loop, hence InFeedbackLoop is set to NO.
SamplesRae: Sample of the signal. In Bluetooth examples, in the Equations tab of the design,
SampleRate is calculated as SamplesPerSym x 1e6.

45
ADS and SystemVue Integration

InputFcs: Array of characterization frequencies of input envelope signals. In WLAN 802.11ac examples,
there is only one input port in SVE_Link model, hence InputFcs is set to [FCarrier_In].

Otherwise when DefineProperties is set to NO, the VTB process will analyze the full design and
provide such information to the integrating tool.

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

46
ADS and SystemVue Integration

Bluetooth_BDR_Source

Bluetooth_BDR_Source_Analysis

This workspace provides a VTB test bench to generate Bluetooth basic data rate signal.

A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.

The transmitted signal mean power is set by SignalPower.

47
ADS and SystemVue Integration

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

A sink is used to save the generated signal from 0 to TimeStop.

To generate the BDR signal used to measure the modulation characteristics DeltaF1 and DeltaF2,
the defined payload data patterns should be used by set the parameter PayloadDataPatten in the
schematic and run the Analysis.

For DeltaF1, we should set the PayloadDataPatten as 0 i.e. (1 1 1 1 0 0 0 0)


For DeltaF2, we should set the PayloadDataPatten as 1 i.e. (1 0 1 0 1 0 1 0)
To generate the BDR signal used to measure the BER, the PayloadDataPattern should be set to 2
(PN9) or 3 (PN15).

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
Bluetooth Parameters
LinkType: the link type of the packet. It can be set to SCO, ACL or eSCO.
SCOPacketType: packet type for SCO Basic. The supported SCO packet type are: 5;HV1;6;HV2;7;HV3.
This parameter is active only in case of LinkType is set to SCO.
ACLPacketType: packet type for ACL Basic. The supported ACL packet type are 4;DH1; 10;DM3;
11;DH3; 14;DM5; 15;DH5. This parameter is active only in case of LinkType is set to ACL.
eSCOPacketType: packet type for eSCO Basic. The supported eSCO packet type are: 7;EV3; 12;EV4;
13;EV5. This parameter is active only in case of LinkType is set to eSCO.
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for pattern (1 1 1 1 0 0 0 0); 1 for pattern (1 0 1 0 1 0 1 0);
2 for PN9 and 3 for PN15

Simulation Results

Try to change the parameters, run Bluetooth_BDR_Source_Analysis and check the simulation
results.
Graph BDR_Waveform shows the transmitted time domain waveform

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

48
ADS and SystemVue Integration

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

49
ADS and SystemVue Integration

Bluetooth_BDR_Tx

Bluetooth_BDR_Tx_Analysis
This workspace provides a VTB test bench to analyze output power, modulation
characteristics, ICFT(initial carrier frequency tolerance) and the carrier frequency drift of Bluetooth
basic data rate source.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.
The transmitted signal mean power is set by SignalPower.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

50
ADS and SystemVue Integration

The number of bursts for measurements is specified by MeasBurst.

Try to change the parameters, run Bluetooth_BDR_Tx_Analysis and check the simulation results.

To measure the modulation characteristics DeltaF1 and DeltaF2, the defined payload data patterns
should be used by set the parameter PayloadDataPatten in the schematic and run the Analysis.

For DeltaF1, we should set the PayloadDataPatten as 0 i.e. (1 1 1 1 0 0 0 0)


For DeltaF2, we should set the PayloadDataPatten as 1 i.e. (1 0 1 0 1 0 1 0)
In the case of modulation characteristics test, the reported BER results are not correct. To measure
the BER, the PayloadDataPattern should be set to 2 (PN9) or 3 (PN15).

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. Bluetooth Parameters
LinkType: the link type of the packet. It can be set to SCO, ACL or eSCO.
SCOPacketType: packet type for SCO Basic. The supported SCO packet type are: 5;HV1;6;HV2;7;HV3.
This parameter is active only in case of LinkType is set to SCO.
ACLPacketType: packet type for ACL Basic. The supported ACL packet type are 4;DH1; 10;DM3;
11;DH3; 14;DM5; 15;DH5. This parameter is active only in case of LinkType is set to ACL.
eSCOPacketType: packet type for eSCO Basic. The supported eSCO packet type are: 7;EV3; 12;EV4;
13;EV5. This parameter is active only in case of LinkType is set to eSCO.
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for pattern (1 1 1 1 0 0 0 0); 1 for pattern (1 0 1 0 1 0 1 0);
2 for PN9 and 3 for PN15

Simulation Results

Try to change the parameters, run Bluetooth_BDR_Tx_Analysis and check the simulation results.

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.
Table BDR_ICFT shows initial carrier frequency tolerance of the transmitted signal
Table BDR_MaxDriftRes lists carrier frequency drift for each burst
Table BDR_ModCharacteristics shows the modulation characteristics of each burst
Graph BDR_PowerRes shows the power of the transmitted signal
Graph BDR_Waveform shows the transmitted time domain waveform

51
ADS and SystemVue Integration

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

52
ADS and SystemVue Integration

Bluetooth_CoACInterferencePerformance

Bluetooth_EDR_CoACInterference_Analysis
This workspace provides a VTB test bench to analyze Bluetooth Rx performance in the presence of
co-/adjacent channel Bluetooth interference.
A simple design to use this VTB is shown below.

The test procedure refers to 5.1.24 TP/RCV/CA/09/C (EDR C/I Performance).


The default wanted signal and interferer are pi/4-DQPSK modulated packet 2-DH5. To test 8DPSK
signal, please reset the packet type in Parameters.
This design gives the co-channel interference test of the lowest operation frequency using a minimum
number of 16 000 000 payload bits as the default configuration. The operation frequency and signal
power of the wanted signal and interferer are set in the Parameters. Users can change the
parameters for other test case with reference 5.1.24 TP/RCV/CA/09/C (EDR C/I Performance) of
Bluetooth Test Specification Ver. 1.2/2.0/2.0+EDR/2.1/2.1+EDR.

53
ADS and SystemVue Integration

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.

The transmitted wanted signal mean power is set by SignalPower.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

The number of bursts for BER measurements is specified by MeasBurst.

Try to change the parameters, run Bluetooth_EDR_CoACInterference_Analysis and check the


simulation results.

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. Bluetooth Parameters
LinkType: the link type of the packet. It can be set to ACL or eSCO.
ACLPacketType: packet type for ACL EDR. The supported ACL packet type are: 4:2DH1; 8:3DH1;
10:2DH3; 11:3DH3; 14: 2DH5; 15:3DH5. This parameter is active only in case of LinkType is set to ACL.
eSCOPacketType: packet type for eSCO EDR. The supported eSCO packet type are: 6:2EV3; 7:3EV3;
12: 2EV5; 13:3EV5. This parameter is active only in case of LinkType is set to eSCO.
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for PN9 and 1 for PN15

Simulation Results

Try to change the parameters, run Bluetooth_EDR_CoACInterference_Analysis and check the


simulation results.

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

54
ADS and SystemVue Integration

Table EDR_CoACInterference_BER shows the decoded bits error rate of the transmitted signal with co-
channel or adjacent channel interference.
Graph EDR_CoCInterference_Spectrum_Power shows the spectrum of the wanted signal and the
interfering signal.

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

55
ADS and SystemVue Integration

Bluetooth_EDR_Sensitivity

Bluetooth_EDR_Sensitivity_Analysis
This workspace provides a VTB test bench to analyze EDR Sensitivity using a non-ideal transmitter
of the Bluetooth EDR signals.
A simple design to use this VTB is shown below.

The test procedure refers to 5.1.22 RCV/CA/07/C (EDR Sensitivity).


The packet type is 2-DH5 with pi/4- DQPSK modulation and with the maximum length payload
containing PN9. To test other packet type, please reset the LinkType and ACLPacketType or
eSCOPacketType.
The input power to the receiver is -70dBm
This examples gives one step of Sensitivity test procedure with the lowest operation frequency using
20 packets according to Table 5.9 in 5.1.22 RCV/CA/07/C (EDR Sensitivity). To complete all test steps
of 5.1.22 RCV/CA/07/C (EDR Sensitivity), please reset the FCarrier_In_Offset, ModulationIndex

56
ADS and SystemVue Integration

according to Table 5.9 in 5.1.22 RCV/CA/07/C (EDR Sensitivity) and run Bluetooth_EDR_Sensitivity
Analysis.
To get the mid and highest operating frequency test result, please re-set the FCarrier_In and other
parameters in the Parameters and run it.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.

The transmitted wanted signal mean power is set by SignalPower.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

The number of bursts for BER measurements is specified by MeasBurst.

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. Bluetooth Parameters
LinkType: the link type of the packet. It can be set to ACL or eSCO.
ACLPacketType: packet type for ACL EDR. The supported ACL packet type are: 4:2DH1; 8:3DH1;
10:2DH3; 11:3DH3; 14: 2DH5; 15:3DH5. This parameter is active only in case of LinkType is set to ACL.
eSCOPacketType: packet type for eSCO EDR. The supported eSCO packet type are: 6:2EV3; 7:3EV3;
12: 2EV5; 13:3EV5. This parameter is active only in case of LinkType is set to eSCO.
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for PN9 and 1 for PN15

Simulation Results

Try to change the parameters, run Bluetooth_EDR_Sensitivity_Analysis and check the simulation
results.

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

57
ADS and SystemVue Integration

Table EDR_BER shows the decoded bits error rate of the transmitted signal with specific Noise figure.

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

58
ADS and SystemVue Integration

Bluetooth_EDR_Source

Bluetooth_EDR_Source_Analysis
This workspace provides a VTB test bench to generate Bluetooth Enhanced Data Rate signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.
The transmitted signal mean power is set by SignalPower.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

A sink is used to save the generated signal from 0 to TimeStop.

59
ADS and SystemVue Integration

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. Bluetooth Parameters
LinkType: the link type of the packet. It can be set to ACL or eSCO.
ACLPacketType: packet type for ACL EDR. The supported ACL packet type are: 4:2DH1; 8:3DH1;
10:2DH3; 11:3DH3; 14: 2DH5; 15:3DH5. This parameter is active only in case of LinkType is set to ACL.
eSCOPacketType: packet type for eSCO EDR. The supported eSCO packet type are: 6:2EV3; 7:3EV3;
12: 2EV5; 13:3EV5. This parameter is active only in case of LinkType is set to eSCO.
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for PN9 and 1 for PN15.

Simulation Results

Try to change the parameters, run Bluetooth_EDR_Source_Analysis and check the simulation
results.
Graph EDR_Waveform shows the transmitted time domain waveform

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

60
ADS and SystemVue Integration

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

61
ADS and SystemVue Integration

Bluetooth_EDR_Tx

Bluetooth_EDR_Tx_Analysis
This workspace provides a VTB test bench to analyze output power, carrier frequency stability and
modulation accuracy and BER of the Bluetooth Enhanced Data Rate signals.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.
The transmitted signal mean power is set by SignalPower.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

62
ADS and SystemVue Integration

The number of bursts for measurements is specified by MeasBurst.

Try to change the parameters, run Bluetooth_EDR_Tx_Analysis and check the simulation results.

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. Bluetooth Parameters
LinkType: the link type of the packet. It can be set to ACL or eSCO.
ACLPacketType: packet type for ACL EDR. The supported ACL packet type are: 4:2DH1; 8:3DH1;
10:2DH3; 11:3DH3; 14: 2DH5; 15:3DH5. This parameter is active only in case of LinkType is set to ACL.
eSCOPacketType: packet type for eSCO EDR. The supported eSCO packet type are: 6:2EV3; 7:3EV3;
12: 2EV5; 13:3EV5. This parameter is active only in case of LinkType is set to eSCO.
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for PN9 and 1 for PN15

Simulation Results

Try to change the parameters, run Bluetooth_EDR_Tx_Analysis and check the simulation results.

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.
Table EDR_BER_Res shows the decoded bits error rate of the transmitted signal
Table EDR_FCStability_ModAccuracy lists carrier frequency stability for each burst
Table EDR_PowerRes shows the Power of each burst
Graph EDR_Spectrum_Power shows the spectrum of the transmitted signal
Graph EDR_Waveform shows the transmitted time domain waveform

63
ADS and SystemVue Integration

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

64
ADS and SystemVue Integration

Bluetooth_LE_Source

Bluetooth_LE_Source_Analysis
This workspace provides a VTB test bench to generate Bluetooth Low Energy signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.
The transmitted signal mean power is set by SignalPower.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

A sink is used to save the generated signal from 0 to TimeStop.

65
ADS and SystemVue Integration

To generate the BDR signal used to measure the modulation characteristics DeltaF1 and DeltaF2,
the defined payload data patterns should be used by set the parameter PayloadDataPatten in the
schematic and run the Analysis.

For DeltaF1, we should set the PayloadDataPatten as 0 i.e. (1 1 1 1 0 0 0 0)


For DeltaF2, we should set the PayloadDataPatten as 1 i.e. (1 0 1 0 1 0 1 0)
To generate the LE signal used to measure the BER, the PayloadDataPattern should be set to 2
(PN9) or 3 (PN15).

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. Bluetooth Parameters
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for pattern (1 1 1 1 0 0 0 0); 1 for pattern (1 0 1 0 1 0 1 0);
2 for PN9 and 3 for PN15

Simulation Results

Try to change the parameters, run Bluetooth_LE_Source_Analysis and check the simulation results.
Graph LE_Waveform shows the transmitted time domain waveform

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

66
ADS and SystemVue Integration

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

67
ADS and SystemVue Integration

Bluetooth_LE_Tx

Bluetooth_LE_Tx_Analysis
This workspace provides a VTB test bench to analyze output power, modulation
characteristics, ICFT(initial carrier frequency tolerance) and the carrier frequency drift of Bluetooth
Low Energy signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.
The transmitted signal mean power is set by SignalPower.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

68
ADS and SystemVue Integration

The number of bursts for measurements is specified by MeasBurst.

Try to change the parameters, run Bluetooth_LE_Tx_Analysis and check the simulation results.

To measure the modulation characteristics DeltaF1 and DeltaF2, the defined payload data patterns
should be used by set the parameter PayloadDataPatten in the schematic and run the Analysis.

For DeltaF1, we should set the PayloadDataPatten as 0 i.e. (1 1 1 1 0 0 0 0)


For DeltaF2, we should set the PayloadDataPatten as 1 i.e. (1 0 1 0 1 0 1 0)
In the case of modulation characteristics test, the reported BER results are not correct. To measure
the BER, the PayloadDataPattern should be set to 2 (PN9) or 3 (PN15).

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. Bluetooth Parameters
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for PN9, 1 for pattern (11110000); 2 for pattern
(10101010); 3 for PN15, 4 for (11111111), 5 for (00000000), 6 for (00001111) and 7 for (0101010101)

Simulation Results

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.
Table LE_BER shows the BER
Table LE_ICFT shows initial carrier frequency tolerance of the transmitted signal
Table LE_MaxDriftRes lists carrier frequency drift for each burst
Table LE_ModCharacteristics shows the modulation characteristics of each burst
Table LE_PeakPower shows the peak power of the transmitted signal
Graph LE_Spectrum_Power shows the spectrum of the transmitted signal
Graph LE_Waveform shows the transmitted time domain waveform

69
ADS and SystemVue Integration

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

70
ADS and SystemVue Integration

Bluetooth_withWLANInterference
Bluetooth_EDR_withWLANInterference_AnalysisThis workspace provides a VTB test bench to
analyze Bluetooth Rx performance in the presence of adjacent channel WLAN interference..

A simple design to use this VTB is shown below.

The test procedure refers to 5.1.24 TP/RCV/CA/09/C (EDR C/I Performance).


The Bluetooth signal operation frequency is 2.405 GHz. and the interferer is the WLAN 11n 20MHz
signal which works on 2.417 GHz.
In the default test configuration, Bluetooth packet type is 3-DH5 with 8DPSK modulation and with the
maximum length payload containing PN9. To test other packet type, please reset the LinkType and
ACLPacketType or eSCOPacketType.
The operation frequency and signal power of the wanted signal and interferer as well as the number of
test bursts are set in the Parameters. Users can edit the Parameters for other test case

71
ADS and SystemVue Integration

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.

The transmitted wanted signal mean power is set by SignalPower.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

The number of bursts for BER measurements is specified by MeasBurst.

Try to change the parameters, run Bluetooth_EDR_withWLANInterference_Analysis and check the


simulation results.

Parameter Details
1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. Bluetooth Parameters
LinkType: the link type of the packet. It can be set to ACL or eSCO.
ACLPacketType: packet type for ACL EDR. The supported ACL packet type are: 4:2DH1; 8:3DH1;
10:2DH3; 11:3DH3; 14: 2DH5; 15:3DH5. This parameter is active only in case of LinkType is set to ACL.
eSCOPacketType: packet type for eSCO EDR. The supported eSCO packet type are: 6:2EV3; 7:3EV3;
12: 2EV5; 13:3EV5. This parameter is active only in case of LinkType is set to eSCO.
SamplesPerSym: number of samples per symbol.
ModulationIndex: the modulation index of GFSK.
PayloadDataPattern: payload data pattern. 0 for PN9 and 1 for PN15

Simulation Results
Try to change the parameters, run Bluetooth_EDR_withWLANInterference_Analysis and check the
simulation results.

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

72
ADS and SystemVue Integration

Table EDR_withWLANInterference_BER shows the decoded bits error rate of the transmitted signal
with co-channel or adjacent channel interference.
Graph EDR_withWLANInterference_Spectrum_Power shows the spectrum of the wanted signal and
the interfering signal.

Reference
1. BLUETOOTH SPECIFICATION Version 2.1 + EDR, 26 July 2007.
2. BLUETOOTH SPECIFICATION Version 4.0 + EDR, 30 June 2010.
3. BLUETOOTH TEST SPECIFICATION Ver. 1.2/2.0/2.0 + EDR/2.1/2.1 + EDR, 27 December

73
ADS and SystemVue Integration

Communications Workspaces

Communications Workspaces
A single workspace (VTB_Example) is provided with a few simple VTB designs that demonstrate the
basic VTB features. These VTB designs are provided just for demonstration purposes. In order to run
them, you ONLY need the basic SystemVue license. There are three VTB designs inside this
workspace:
EVM_Measurement
QAM16_SER_vs_EbNo
ACPR_Measurement

74
ADS and SystemVue Integration

ACPR_Measurement

ACPR_Measurement_Analysis
This VTB design demonstrates how VTBs can be set up to post-process simulation data. It measures
ACPR for a modulated signal. The symbol rate and the modulation format of the signal can be set
using VTB parameters. The modulator output power is also set using a VTB parameter. The signal at
the output of the modulator goes through a non-linear amplifier whose output 1 dB compression
point is a VTB parameter.
ACPR is measured by computing the spectrum power in different bands using a custom ACPR
function defined inside the SystemVue workspace.

This ACPR function is for demonstration purposes only. It does NOT comply with any standard.

Parameter Details
Modulation: Modulation format (choose from BPSK, QPSK, 8-PSK, 16-PSK, 16-QAM, 32-QAM, 64-
QAM, 128-QAM, 256-QAM, 512-QAM, 1024-QAM, Star 16-QAM, Star 32-QAM)
SymbolRate: Symbol rate
FCarrier: Carrier frequency
RF_Power: Modulator output power delivered to a load of RefR
P1dB: Output 1 dB compression point
RefR: Reference resistance for power calibration

Simulation Results

Simulation results include the output spectrum and a table of four ACPR values, for the two
adjacent channels above (MyACPRPlus1_dB, MyACPRPlus2_dB) and below (MyACPRMinus1_dB,
MyACPRMinus2_dB) the main channel.

75
ADS and SystemVue Integration

Change the P1dB parameter and observe the changes in the spectrum and ACPR values.

76
ADS and SystemVue Integration

EVM_Measurement

EVM_Measurement_Analysis
This VTB design performs an EVM measurement on a modulated signal. The symbol rate and
modulation format of the signal can be set through the VTB parameters. The modulator output
power, as well as certain modulation impairments, can also be set using the VTB parameters.

Parameter Details
Modulation: Modulation format (choose from BPSK, QPSK, 8-PSK, 16-PSK, 16-QAM, 32-QAM, 64-
QAM, 128-QAM, 256-QAM, 512-QAM, 1024-QAM, Star 16-QAM, Star 32-QAM)
SymbolRate: Modulated signal symbol rate
FCarrier: Carrier frequency
RF_Power: Modulator output power delivered to a load of RefR
RefR: Reference resistance for power calibration
GainImb: Modulator gain imbalance
PhaseImb: Modulator phase imbalance
IQ_Offset: Complex IQ offset
NoiseDensity: Noise density (Power/Hz)
NumSymbols: Number of symbols used for EVM measurement

Simulation Results

The simulation results include an errors summary table and a trajectory plot. Please note that in the
errors summary table the IQ Offset, Gain Imb, and Droop are shown in linear scale (absolute values).
To see them in dB you need to apply the 20*log10() function.

77
ADS and SystemVue Integration

78
ADS and SystemVue Integration

QAM16_SER_vs_EbNo

QAM16_SER_vs_EbNo_Analysis
This VTB design uses the BER_IS model to efficiently compute a BER waterfall curve for a 16-QAM
system. VTB parameters include the signal symbol rate, modulator output power, and range of SNR
values over which BER is computed.
This VTB design is NOT designed to handle DUTs that introduce arbitrary delays, phase rotations, etc.

Parameter Details
SymbolRate: 16-QAM symbol rate
FCarrier: Carrier frequency
RF_Power: Modulator output power delivered to a load of RefR
RefR: Reference resistance for power calibration
DUT_Gain: DUT linear power gain
SNR_Start: SNR start value
SNR_Step: SNR step value
SNR_NumSteps: SNR number of steps

DUT_Gain is the linear power gain of the DUT that is connected to the VTB. This is needed so that
the values at the input of the VTB (output of the DUT) are scaled properly before they are processed
to compute BER (the default detection thresholds used by the BER_IS model assume input signal
levels equally spaced between -1 and 1).
SNR values refer to Eb/No

Simulation Results

Simulation results include the simulated BER curve along with the theoretical BER curve. Note that
by default the graph is NOT using a logarithmic scale on the y-axis.

79
ADS and SystemVue Integration

To see the typical BER waterfall curve change the y-axis to use a log scale

80
ADS and SystemVue Integration

81
ADS and SystemVue Integration

DigitalMod Workspaces

DigitalMod Workspaces
VTB workspaces are provided to analyze the most basic digital modulation signal transmitter.

Tx
DigitalMod_Tx
DigitalMod_Tx_Source

82
ADS and SystemVue Integration

DigitalMod_Tx

DigitalMod_Tx_Analysis
This VTB design demonstrates the signal generation of the most common modulation formats. The
message is modulated with the specified format and up-converted into RF signal.

Schematic

A simple design to use this VTB is shown below.

Parameter Details
1. FCarrier_In: The frequency of the carrier of the input end, [0, inf).
2. FCarrier_Out: The frequency of the carrier of the output end, [0, inf).
3. SignalPower: The power of transmit signal power over 50ohm, (-inf, inf).
4. SymbolRate: The symbol rate of the current communication system, (0, inf).
5. OVSR: The oversampling ratio, that is the number of samples that each symbol lasts, [1, inf).

83
ADS and SystemVue Integration

6. ModType: The digital modulation format. BPSK, QPSK, 8-PSK, 16-PSK, 16-QAM, 32-QAM, 64-QAM,
128-QAM, 256-QAM, 512-QAM, 1024-QAM, 2048-QAM, 4096-QAM, 16-APSK, 32-APSK, Star 16-QAM,
Star 32-QAM, Custom APSK, DQPSK, pi/4 DQPSK, Offset QPSK, SOQPSK-MIL, SOQPSK-TG, D8PSK,
EDGE-8PSK, pi/8 D8PSK, MSK, GMSK, M-ary CPM, Multi-h CPM, CQPSK, pi/4-CQPSK, IJF-OQPSK,
FQPSK, EFQPSK, 2FSK, 4FSK, 8FSK, 16FSK, DBPSK, pi/2 DBPSK
7. StopTime: The stop time of data collection in seconds, [0, inf).
8. FilterType: The type of pulse shaping filter.
9. FilterLength: The length of pulse shaping filter, [1, inf).
10. FilterCoeffcient: The coefficient of the current type of pulse shaping filter, [0, 1].

84
ADS and SystemVue Integration

Simulation Results

85
ADS and SystemVue Integration

The spectrum, CCDF and waveform are plotted in figures.

86
ADS and SystemVue Integration

DigitalMod_Tx_Source

DigitalMod_Tx_Source_Analysis
This workspace provides a VTB test bench for generating the most common digital modulation
signal.

Schematic

A simple design to use this VTB is shown below.

Parameter Details
1. FCarrier_In: The frequency of the carrier of the input end, [0, inf).
2. FCarrier_Out: The frequency of the carrier of the output end, [0, inf).
3. SignalPower: The power of transmit signal power over 50ohm, (-inf, inf).
4. SymbolRate: The symbol rate of the current communication system, (0, inf).
5. OVSR: The oversampling ratio, that is the number of samples that each symbol lasts, [1, inf).

87
ADS and SystemVue Integration

6. ModType: The digital modulation format. BPSK, QPSK, 8-PSK, 16-PSK, 16-QAM, 32-QAM, 64-QAM,
128-QAM, 256-QAM, 512-QAM, 1024-QAM, 2048-QAM, 4096-QAM, 16-APSK, 32-APSK, Star 16-QAM,
Star 32-QAM, Custom APSK, DQPSK, pi/4 DQPSK, Offset QPSK, SOQPSK-MIL, SOQPSK-TG, D8PSK,
EDGE-8PSK, pi/8 D8PSK, MSK, GMSK, M-ary CPM, Multi-h CPM, CQPSK, pi/4-CQPSK, IJF-OQPSK,
FQPSK, EFQPSK, 2FSK, 4FSK, 8FSK, 16FSK, DBPSK, pi/2 DBPSK
7. StopTime: The stop time of data collection in seconds, [0, inf).
8. FilterType: The type of pulse shaping filter.
9. FilterLength: The length of pulse shaping filter, [1, inf).
10. FilterCoeffcient: The coefficient of the current type of pulse shaping filter, [0, 1].

Simulation Results

The waveform of I and Q are plotted separately.

88
ADS and SystemVue Integration

LTE Advanced Workspaces

LTE Advanced Workspaces


VTB workspaces are provided to analyze LTE-Advanced transmitter characteristics for a base station
according to [1].
LTE_Advanced_BS_CA_Tx
LTE_Advanced_BS_CA_Tx_Source

In the current implementation, there are only one input port and one output port in the SVE_Link model
used in LTE Advanced workspaces, which means the DUT (design in ADS/GoldenGate environment)
should only have one input and one output. In Tx examples, the DUT is connected after the modulator.
Please refer to the help document of each workspace for more information. in which you can find the
detailed schematic.

How to set SVE_Link properties in LTE workspaces


Users can optionally define the SVE_Link properties by setting DefineProperties to YES. When
DefineProperties is set to YES, parameters related to SVE_Link properties, including
InFeedbackLoop, SampleRate, and InputFcs, can be defined by values or expressions.
InFeedbackLoop: Specify whether the SVE_Link is in a feedback loop: NO, YES. In LTE Advanced Tx
examples, there is no feedback loop, hence InFeedbackLoop is set to NO.
SampleRate: Sample rate of the signal. In LTE Advanced examples, the sample rate is set by parameter
OutputSampleRate. Hence, SampleRate is directly set to OutputSampleRate.
InputFcs: Array of characterization frequencies of input envelope signals. In current LTE Advanced
examples, there is only one input port in SVE_Link model, hence, InputFcs is set to [FCarrier_In].

Otherwise, when DefineProperties is set to NO, the VTB process will analyze the full design and
provide such information to the integrating tool.

References
1. 3GPP TS 36.104 v10.0.0 "Base Station (BS) radio transmission and reception", December 2010.

89
ADS and SystemVue Integration

LTE_Advanced_BS_CA_Tx

LTE_Advanced_BS_CA_Tx_Analysis
This VTB design measures LTE Advanced base station transmitter characteristics with carrier
aggregation, including spectrum, waveform, CCDF, EVM and ACLR according to [1].
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT( SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT( SVE_Link in the design) is set by FCarrier_Out.
The sampling rate of the aggregated signal is explicitly specified by OutputSampleRate. Make sure
the sampling rate is sufficient to analyze the aggregated signal and can be handled by SystemVue
simulation. However, large OutputSampleRate would significantly slow down the simulation. The
transmitted signal of each component carrier would be resampled and combined in model

90
ADS and SystemVue Integration

SSignalCombiner. Also, make sure OutputSampleRate is multiple of the base sample rate of each
component carrier.

By default, two component carriers are transmitted. The frequency of each component carrier (CC)
is set by CC#_FCarrier. By setting those center frequencies, this design can generate either
contiguous or noncontiguous aggregated signal either intra-band or inter-band. Again, please make
sure OutputSampleRate is sufficient to analyze the aggregated signal.

Component carrier 0 would always be transmitted, while other component carriers can be turned
off by set CC#_Enable to NO. Up to 5 component carriers are supported. Each component carrier
can be configured independently. Please open the workspace in SystemVue then you can find
parameters to configure each component carrier.

The ideal lowpass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter. The
number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping would be
applied. The same spectrum shaping is implemented for each component carrier.

Users can select one component carrier for EVM measurement by setting parameter CCToMeas. It
should be set in the range [0,4]. By default, a ParksMcClellan bandpass filter is used before EVM
measurement. This filter can be disabled by setting EnableRxFilter to NO.

The number of simulated frames for EVM measurements is set by parameter NumFrames.

Parameter Details
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
OutputSampleRate: User specified output sample rate of the aggregated signal. Range: (0:+∞)
CC#_Enable: Enable transmission of component carrier#. Component carrier 0 is always transmitted
CC#_FreqOffset: Frequency offset of component carrier# relative to FCarrier_In. Range: (-FCarrier_In:
+∞)
CCToMeas: Choose which component carrier to measure EVM. Range: [0,4]
EnableRxFilter: Whether enables Rx Filter for the measured component carrier or not
For details on other parameters, refer to 3GPP_LTE_BS_Tx.

Simulation Results

Try to change the parameters, run LTE_Advanced_BS_CA_Tx_Analysis and check the simulation
results.
Graph CCDF shows the Complementary Cumulative Distribution Function of the transmitted signal
Graph Constellation shows the constellation of each physical channel and signal of component carrier
0
Table ErrorSummary shows average EVM, peak EVM, frequency errors and other measured results of
each frame of component carrier 0
Table EVM lists EVM of each physical channel and signal of component carrier 0 according to section
6.5 of 3GPP TS 36.104
Graph NormalizedEqualizerChannelFrequencyResponse shows the normalized equalizer channel
frequency response of component carrier 0

91
ADS and SystemVue Integration

Graph RBErrorMagSpectrum shows the error magnitude spectrum of each RB of component carrier 0
Graph Spectrum shows the spectrum of the aggregated signal
Graph Waveform shows the transmitted time domain waveform
EVM is reported in % in this example, i.e. if the result is displayed as 0.187, it means EVM =
0.187%.
If EVM on PDSCH (for different modulation schemes) is better than the limits below [1], then
EVM_PassFailFlag is set to true(1), otherwise, it is set to false(0).

Modulation scheme for PDSCH Required EVM [%]

QPSK 17.5 %

16QAM 12.5 %

64QAM 8%

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation. The DUT is shorted to get the following ideal results. The same results will
be displayed in SystemVue environment if the SVE_Link model is disabled to short.

92
ADS and SystemVue Integration

Reference
1. 3GPP TS 36.104 v10.0.0 "Base Station (BS) radio transmission and reception", December 2010.

93
ADS and SystemVue Integration

LTE_Advanced_BS_CA_Tx_Source

LTE_Advanced_BS_CA_Tx_Source_Analysis
This VTB workspace is used to generate LTE-Advanced downlink carrier aggregation signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT( SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT( SVE_Link in the design) is set by FCarrier_Out.
The sampling rate of the aggregated signal is explicitly specified by OutputSampleRate. Make sure
the sampling rate is sufficient to analyze the aggregated signal and can be handled by SystemVue
simulation. However, large OutputSampleRate would significantly slow down the simulation. The
transmitted signal of each component carrier would be resampled and combined in model

94
ADS and SystemVue Integration

SignalCombiner. Also please make sure OutputSampleRate is multiple of the base sample rate of
each component carrier.

Up to 5 component carriers are supported. The frequency of each component carrier (CC) is set by
CC0_FCarrier, CC1_FCarrier, CC2_FCarrier, CC3_FCarrier and CC4_FCarrier respectively. By setting
those center frequencies, this design can generate either contiguous or non-contiguous aggregated
signal either intra-band or inter-band. Again, please make sure OutputSampleRate is sufficient to
analyze the aggregated signal.

Component carrier 0 would always be transmitted, while other component carriers can be turned
off by set CC#_Enable to NO. Each component carrier can be configured independently.

The ideal lowpass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter. The
number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping would be
applied. The same spectrum shaping is implemented for each component carrier.

A sink is used to save the generated signal from 0 to TimeStop.

Parameter Details
TimeStop: Stop time of data collection. Range: (0:+∞)
For details on other parameters, please refer to LTE_Advanced_BS_CA_Tx.

Simulation Results

Try to change the parameters, run LTE_Advanced_BS_CA_Tx_Source_Analysis and check the


simulation results.
Graph Waveform shows the transmitted time domain waveform

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

95
ADS and SystemVue Integration

Reference
1. 3GPP TS 36.104 v10.0.0 "Base Station (BS) radio transmission and reception", December 2010.

96
ADS and SystemVue Integration

LTE Workspaces

LTE Workspaces
VTB workspaces are provided to analyze LTE transmitter and receiver characteristics for both user
equipment and base station according to [1] and [2], respectively

UE Tx
User Equipment Transmitter characteristics according to section 6 of [1]
3GPP_LTE_UE_Tx
3GPP_LTE_UE_Tx_Source

UE Rx
User Equipment Receiver characteristics according to section 6 of [1]
3GPP_LTE_UE_ReferenceSensitivity
3GPP_LTE_UE_AdjacentChannelSelectivity

BS Tx
Base Station Transmitter characteristics according to section 6 of [2]
3GPP_LTE_BS_Tx
3GPP_LTE_BS_Tx_Source

BS Rx
Base Station Receiver characteristics according to section 7 of [2]
3GPP_LTE_BS_ReferenceSensitivity
3GPP_LTE_BS_InChannelSelectivity
3GPP_LTE_BS_AdjacentChannelSelectivity

In the current implementation, there are only one input port and one output port in the SVE_Link model
used in LTE workspaces, which means the DUT (design in ADS/GoldenGate environment) should only
have one input and one output. In Tx examples, the DUT is connected to the modulator. In Rx examples,
the DUT is connected before the demodulator in the Rx chain. Refer to the help document of each
workspace for more information. in which you can find the detailed schematic.

97
ADS and SystemVue Integration

How to set SVE_Link properties in LTE workspaces


Users can optionally define the SVE_Link properties by setting DefineProperties to YES. When
DefineProperties is set to YES, parameters related to SVE_Link properties, including
InFeedbackLoop, SampleRate, and InputFcs, can be defined by values or expressions.
InFeedbackLoop: Specify whether the SVE_Link is in a feedback loop: NO, YES. In LTE Tx examples, e.g.
3GPP_LTE_BS_Tx, there is no feedback loop, hence InFeedbackLoop is set to NO. In LTE Rx examples,
e.g. 3GPP_LTE_UE_ReferenceSensitivity, HARQ feedback could be enabled by setting parameter
UE1_HARQ_Enable to YES, hence, InFeedbackLoop is set to UE1_HARQ_Enable.
SampleRate: Sample rate of the signal. In LTE examples, in the Equations tab of the design,
SamplingRate of the LTE system is calculated from Bandwidth and OversamplingOption. Hence,
SampleRate is directly set to SamplingRate. The base sample rate of 1.4MHz, 3MHz, 5MHz, 10MHz,
15MHz and 20MHz LTE systems are 1.92MHz, 3.84 MHz, 7.68 MHz, 15.36 MHz, 23.04 MHz and 30.72
MHz, respectively.
InputFcs: Array of characterization frequencies of input envelope signals. In current LTE examples,
there is only one input port in SVE_Link model, hence, InputFcs is set to [FCarrier_In].

Otherwise, when DefineProperties is set to NO, the VTB process will analyze the full design and
provide such information to the integrating tool.

References
1. 3GPP TS 36.101 v9.3.0 "User Equipment (UE) radio transmission and reception", March 2010.
2. 3GPP TS 36.104 v9.3.0 "Base Station (BS) radio transmission and reception", March 2010.

98
ADS and SystemVue Integration

3GPP_LTE_BS_AdjacentChannelSelectivity

LTE_BS_AdjacentChannelSelectivity_Analysis
This workspace provides a VTB test bench of Adjacent Channel Selectivity (ACS) of LTE BS receiver
according to section 7.5 of 3GPP TS 36.104. Adjacent channel selectivity (ACS) is a measure of the
receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an
adjacent channel signal with a specified center frequency offset of the interfering signal to the band
edge of a victim system. The interfering signal shall be an E-UTRA signal as specified in Annex C of
3GPP TS 36.104.
A simple design to use this VTB is shown below.

The wanted and the interfering signal should be configured according to Table 7.5.1-3, Table
7.5.1-4 and Table 7.5.1-5 for Wide Area BS, Local Area BS and Home BS, respectively.

99
ADS and SystemVue Integration

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.

RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

The wanted signal mean power is set by parameter P_WantedSig, while the interfering signal mean
power is set by parameter P_Interferer.

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

The interfering signal center frequency offset is set by parameter Foffset_Interferer.


Foffset_Interferer ≤ 0 indicates the center frequency of the interferer is lower than the lower edge of
the wanted signal, otherwise, the center frequency of the interferer is higher than the upper edge of
the wanted signal.

The bandwidth of the interfering signal is determined by the bandwidth of the wanted signal
according to Table 7.5.1-3 ~ Table 7.5.1-5, i.e. if Bandwidth of the wanted signal is smaller than
5MHz, the interfering signal would have the same bandwidth as the wanted signal, otherwise, the
bandwidth of the interfering signal is 5MHz.

HARQ retransmission can be enabled by setting HARQ_Enable to YES. When HARQ retransmission
is enabled, EnableTxFilter should be set to NO as ideal lowpass filter is not supported in HARQ
retransmission in current SystemVue version. A number of HARQ processes is 8 for FDD and 7 for
TDD. A maximum number of HARQ transmissions is set to 4. The redundancy version sequence is
set to [0,1,2,3].

A Parks-McClellan bandpass filter centered at FCarrier_Out is used on the receiver side. The
PassBandwidth is set to the transmission bandwidth of the wanted signal, and the StopBandwidth
is set to the channel bandwidth. For example, if Bandwidth of wanted signal is 5MHz, then
PassBandwidth = 4.5MHz, StopBandwidth = 5MHz. This filter could be disabled by setting
parameter EnableRxFilter to NO.

By default, the reference measurement channels specified in Annexes A of 3GPP TS 36.104 are
used. If you want to customize the test configuration, please open this workspace in SystemVue
and set UseFRC to NO and set the payload configuration and RB allocation.

The number of simulated frames is set by parameter NumFrames.

Parameter Details
P_WantedSig: Wanted signal mean power over 50ohm. Range: (-∞:+∞)
P_Interferer: Interfering signal means power over 50ohm. Range: (-∞:+∞)

100
ADS and SystemVue Integration

FOffset_Interfer: The interfering signal center frequency offset. Foffset_Interferer<0 indicates the center
frequency of the interferer is lower than the lower edge of the wanted signal, otherwise, the center
frequency of the interferer is higher than the upper edge of the wanted signal. Range: (-FCarrier_In:+∞)
EnableRxFilter: Whether to enable Rx bandpass filter or not
For details on other parameters, refer to 3GPP_LTE_UE_Tx.
When HARQ is turned on, the dynamic range used for fast circuit envelope extraction (in ADS
and GoldenGate) might not be exactly the same as the actual dynamic range during VTB
simulation

Simulation Results

Try to change the parameters, run LTE_BS_AdjacentChannelSelectivity_Analysis and check the


simulation results in table ThroughputFraction to see whether the throughput meets the
requirements. The throughput shall be ≥ 95% of the maximum throughput of the reference
measurement channels.

If ThroughputFraction > 95%, PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Reference
1. 3GPP TS 36.104 v9.3.0 "Base Station (BS) radio transmission and reception", March 2010.

101
ADS and SystemVue Integration

3GPP_LTE_BS_InChannelSelectivity

LTE_BS_InChannelSelectivity_Analysis
This workspace provides a VTB test bench of In-Channel Selectivity (ICS) of LTE BS receiver
according to section 7.4 of 3GPP TS 36.104. In-channel selectivity (ICS) is a measure of the receiver
ability to receive a wanted signal at its assigned resource block locations in the presence of an
interfering signal received at a larger power spectral density. In this condition, a throughput
requirement shall be met for a specified reference measurement channel. The interfering signal
shall be an E-UTRA signal as specified in Annex C and shall be time aligned with the wanted signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while center
frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

102
ADS and SystemVue Integration

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

The wanted signal mean power is set by parameter P_WantedSig, while the interfering signal mean
power is set by parameter P_Interferer.

Wanted and interfering signal is placed adjacently around Fc. The type of the interfering signal is
determined by the bandwidth of the wanted signal according to Table 7.4.1-1 ~ Table 7.4.1-3. The
RB allocation of wanted signal and interfering signal are set as follows.

Wanted Signal Wanted Signal RB Interfering Signal Interfering Signal RB Allocation


Bandwidth (MHz) Allocation [Start RB, Bandwidth (MHz) [Start RB, NumRBs]
NumRBs]

1.4 [0,3] 1.4 [3,3]

3 [0,9] 3 [9,6]

5 [0,15] 5 [15,10]

10 [0,25] 10 [25,25]

15 [23,25] 15 [38,25]

20 [25,25] 20 [50,25]

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

HARQ retransmission can be enabled by setting HARQ_Enable to YES. When HARQ retransmission
is enabled, EnableTxFilter should be set to NO as ideal lowpass filter is not supported in HARQ
retransmission in current SystemVue version. A number of HARQ processes is 8 for FDD and 7 for
TDD. A maximum number of HARQ transmissions is set to 4. The redundancy version sequence is
set to [0,1,2,3].

By default, the reference measurement channels specified in Annexes A of 3GPP TS 36.104 are
used. If you want to customize the test configuration, please open this workspace in SystemVue
and set UseFRC to NO and set the payload configuration and RB allocation.

The number of simulated frames is set by parameter NumFrames.

Parameter Details
1. RF Parameters

103
ADS and SystemVue Integration

P_WantedSig: Wanted signal mean power over 50ohm. Range: (-∞:+∞)


P_Interferer: Interfering signal mean power over 50ohm. Range: (-∞:+∞)
2. Advanced Parameters
The following parameters are not exposed in ADS/GoldenGate environment. The default values
of these parameters will be used in the simulation. To change them, please open the workspace
in SystemVue, go to the Parameters tab of the design and change the Default Value there. To
expose them to ADS/GoldenGate environment, please also open the workspace in SystemVue,
go to Parameters tab and change the Hide Condition to false or simply delete the Hide
Condition.

WantedSig_StartRB: First RB of the wanted signal


WantedSig_NumRBs: Number of RBs allocated to wanted signal
Interferer_StartRB: First RB of the interfering signal
Interferer_NumRBs: Number of RBs allocated in interfering signal
For details on other parameters, please refer to 3GPP_LTE_UE_Tx and
3GPP_LTE_BS_ReferenceSensitivity.
When HARQ is turned on, the dynamic range used for fast circuit envelope extraction (in ADS
and GoldenGate) might not be exactly the same as the actual dynamic range during VTB
simulation

Simulation Results

Try to change the parameters, run LTE_BS_InChannelSelectivity_Analysis and check the simulation
results in table ThroughputFraction to see whether the throughput meets the requirements. The
throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels.

If ThroughputFraction > 95%, PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Reference
1. 3GPP TS 36.104 v9.3.0 "Base Station (BS) radio transmission and reception", March 2010.

104
ADS and SystemVue Integration

3GPP_LTE_BS_ReferenceSensitivity

LTE_BS_ReferenceSensitivity_Analysis
This workspace provides a VTB test bench of reference sensitivity power level of LTE base station
receiver according to section 7.2 of [1]. The reference sensitivity power level PREFSENS is the
minimum mean power received at the antenna connector at which a throughput requirement shall
be met for a specified reference measurement channel.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

105
ADS and SystemVue Integration

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

The transmitted signal mean power is set by SignalPower.

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

HARQ retransmission can be enabled by setting UE1_HARQ_Enable to YES. When HARQ


retransmission is enabled, EnableTxFilter should be set to NO as ideal lowpass filter is not
supported in HARQ retransmission in current SystemVue version. A number of HARQ processes is 8
for FDD and 7 for TDD. A maximum number of HARQ transmissions is set to 4. The redundancy
version sequence is set to [0,1,2,3].

By default, the reference measurement channels specified in Annexes A of 3GPP TS 36.104 are
used. If you want to customize the test configuration, please open this workspace in SystemVue
and set UseFRC to NO and set the payload configuration and RB allocation.

The number of simulated frames is set by parameter NumFrames.

Parameter Details
UseFRC: Whether use FRC (fixed reference measurement channels) as defined in the specification or
not. The default value is set to YES.
Payload_Config: Payload configuration type. It indicates the meaning of Payload as 0 for MCS index, 1
for Transport block size, 2 for Code rate. The default value is set to Code rate. Active only when
UseFRC is set to NO
Payload: Specify the payload of each frame according to the selection of Payload_Config. The default
value is set to 1/3 (code rate). Active only when UseFRC is set to NO
For details on other parameters, please refer to LTE Parameters.
When HARQ is turned on, the dynamic range used for fast circuit envelope extraction (in ADS
and GoldenGate) might not be exactly the same as the actual dynamic range during VTB
simulation

Simulation Results

Try to change the parameters, run LTE_BS_ReferenceSensitivity_Analysis and check the simulation
results in table ThroughputFraction to see whether the throughput meets the requirements. The
throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as
specified in Annexes A of 3GPP TS 36.104.

If ThroughputFraction > 95%, PassFailFlag is set to true(1), otherwise, it is set to false(0).

106
ADS and SystemVue Integration

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Reference
1. 3GPP TS 36.104 v9.3.0 "Base Station (BS) radio transmission and reception", March 2010.

107
ADS and SystemVue Integration

3GPP_LTE_BS_Tx

LTE_BS_Tx_Analysis
This workspace provides a VTB test bench for measuring base station transmitter characteristics
including spectrum, waveform, CCDF, EVM and ACLR according to [1].
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

E-UTRA Test Models are provided in this workspace according to [2] for both FDD and TDD. You can
select TestModel and Bandwidth to configure different ETMs.

108
ADS and SystemVue Integration

The transmitted signal mean power is set by SignalPower. SignalPower specifies the mean power
of the transmitted signal when all RBs (resource blocks) are allocated.

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

The number of simulated frames for EVM measurements is set by parameter NumFrames.

Parameter Details

1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+∞)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+∞)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-∞:+∞)
PhaseImbalance: Phase imbalance. Range: (-∞:+∞)
I_OriginOffset: I origin offset. Range: (-∞:+∞)
Q_OriginOffset: Q origin offset. Range: (-∞:+∞)
IQ_Rotation: IQ rotation. Range: (-∞:+∞)
2. LTE Parameters
FrameMode: frame mode of LTE, the type is enum and it can be selected as FDD and TDD. FDD
supports frame structure typ1 and TDD supports frame structure type 2
Bandwidth: bandwidth of LTE, the type is enum and it can be selected as BW 1.4 MHz, BW 3 MHz,
BW 5 MHz, BW 10 MHz, BW 15 MHz and BW 20 MHz
OversamplingOption: Over-sampling ratio option. Oversampling ratio 1, ratio 2, ratio 4 and ratio 8
are supported in this downlink source
TestModel: E-UTRA test model type, can be selected from ETM 1.1, ETM 1.2, ETM2, ETM 3.1, ETM
3.2 and ETM 3.3
EnableTxFilter: Whether enable the Tx spectrum shaping filter (an ideal low pass FIR filter) or not
FIR_Taps: Number of taps of the ideal low pass filter. Range: [1:1000]
NumFrames: Number of frames for EVM measurement. Range: [1:+∞)
3. Advanced Parameters
The following parameters are not exposed in ADS/GoldenGate environment. The default values
of these parameters will be used in the simulation. To change them, please open the workspace
in SystemVue, go to the Parameters tab of the design and change the Default Value there. To
expose them to ADS/GoldenGate environment, please also open the workspace in SystemVue,
go to Parameters tab and change the Hide Condition to false or simply delete the Hide
Condition.

UseTestModel: Whether user E-TM or not. The default value is set to YES. If you want to customize
the generated signal other than using the pre-defined test models, please set this parameter to NO.
The following parameters are only active when UseTestModel is set to NO
TDD_Config: Downlink and uplink allocations for TDD. The default value is set to Config 0. Active,
only when FrameMode is set to TDD and UseTestModel, is set to NO
SpecialSF_Config: Special subframe configurations for TDD. The default value is set to Config 4.
Active, only when FrameMode is set to TDD and UseTestModel, is set to NO
FullRB_Alloc: Whether allocates all RBs or not. The default value is set to YES, i.e. all RBs will be
occupied no matter which Bandwidth is selected. If it is set to NO, the RB allocation will be

109
ADS and SystemVue Integration

determined by StartRB and NumRBs. RB allocation will be kept the same in all downlink subframes.
Active only when UseTestModel is set to NO
StartRB: The first RB to be allocated. The default value is set to 0. Active only when FullRB_Alloc is
set to NO and UseTestModel is set to NO. Range: [0:NumTotalRBs], where NumTotalRBs is the total
number of RBs and is different for each Bandwidth.
NumRBs: Number of RBs to be allocated. The default value is set to 25. Active only when
FullRB_Alloc is set to NO and UseTestModel is set to NO. Range: [0:NumTotalRBs]. In addition, the
RB allocation specified by StartRB and NumRBs should not be out of the range determined by
Bandwidth.
UE1_MappingType: The modulation orders, for which 0 for QPSK, 1 for 16QAM, 2 for 64QAM. The
default value is set to 0. Active only when UseTestModel is set to NO. Range: [0:2]
PDCCH_SymsPerSF: Number of OFDM symbols for PDCCH. The default value is set to 0. Active only
when UseTestModel is set to NO. Range: [0:4]

Simulation Results

Try to change the parameters, run LTE_BS_Tx_Analysis and check the simulation results.
Table ACLR shows Adjacent Channel Leakage power Ratio as defined in section 6.6.2 of 3GPP TS
36.104
Graph CCDF shows the Complementary Cumulative Distribution Function of the transmitted signal
Graph Constellation shows the constellation of each physical channel and signal
Table ErrorSummary shows average EVM, peak EVM, frequency errors and other measured results of
each frame got from EVM model
Table EVM lists EVM of each physical channel and signal according to section 6.5 of 3GPP TS 36.104
Graph NormalizedEqualizerChannelFrequencyResponse shows the normalized equalizer channel
frequency response got from EVM model
Graph RBErrorMagSpectrum shows the error magnitude spectrum of each RB got from EVM model
Graph Spectrum shows the spectrum of the transmitted signal
Graph Waveform shows the transmitted time domain waveform
EVM is reported in % in this example, i.e. if the result is displayed as 0.187, it means EVM =
0.187%.
If EVM on PDSCH (for different modulation schemes) is better than the limits below [1], then
EVM_PassFailFlag is set to true(1), otherwise, it is set to false(0).

Modulation scheme for PDSCH Required EVM [%]

QPSK 17.5 %

16QAM 12.5 %

64QAM 8%

If ACLR > 45dB, then ACLR_PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation. The DUT is shorted to get the following ideal results. The same results

110
ADS and SystemVue Integration

will be displayed in SystemVue environment if the SVE_Link model is disabled to short.

Reference
1. 3GPP TS 36.104 v9.3.0 "Base Station (BS) radio transmission and reception", March 2010.
2. 3GPP TS 36.141 v8.5.0 "Base Station (BS) conformance testing", December 2009.
3. 3GPP TS 36.211 v9.1.0, "Physical Channels and Modulation", March 2010.
4. 3GPP TS 36.213 v8.8.0, "Physical Layer Procedures", September 2009.

111
ADS and SystemVue Integration

3GPP_LTE_BS_Tx_Source

LTE_BS_Tx_Source_Analysis
This workspace provides a VTB test bench to generate the LTE downlink signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

E-UTRA Test Models are provided in this workspace according to [2] for both FDD and TDD. You can
select TestModel and Bandwidth to configure different ETMs.

112
ADS and SystemVue Integration

The transmitted signal mean power is set by SignalPower. SignalPower specifies the mean power
of the transmitted signal when all RBs (resource blocks) are allocated.

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

A sink is used to save the generate signal from 0 to TimeStop.

Parameter Details
TimeStop: Stop time of data collection. Range: (0:+∞)
For details on other parameters, please refer to 3GPP_LTE_BS_Tx.

Simulation Results

Try to change the parameters, run LTE_BS_Tx_Source_Analysis and check the simulation results.
Graph Waveform shows the transmitted time domain waveform

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

Reference
1. 3GPP TS 36.104 v9.3.0 "Base Station (BS) radio transmission and reception", March 2010.
2. 3GPP TS 36.141 v8.5.0 "Base Station (BS) conformance testing", December 2009.
3. 3GPP TS 36.211 v9.1.0, "Physical Channels and Modulation", March 2010.

113
ADS and SystemVue Integration

4. 3GPP TS 36.213 v8.8.0, "Physical Layer Procedures", September 2009.

114
ADS and SystemVue Integration

3GPP_LTE_UE_AdjacentChannelSelectivity

LTE_UE_AdjacentChannelSelectivity_Analysis
This workspace provides a VTB test bench of Adjacent Channel Selectivity (ACS) of LTE user
equipment receiver according to section 7.5 of [1]. Adjacent Channel Selectivity (ACS) is a measure
of a receiver's ability to receive a E-UTRA signal at its assigned channel frequency in the presence
of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned
channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the
receive filter attenuation on the adjacent channel(s).
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

115
ADS and SystemVue Integration

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

The wanted signal mean power is set by parameter P_WantedSig, while the interfering signal mean
power is set by parameter P_Interferer. P_WantedSig and P_Interferer specify the mean power of
the wanted signal and interfering signal when all RBs (resource blocks) are allocated.

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

The interfering signal center frequency offset is set by parameter Foffset_Interferer.


Foffset_Interferer ≤ 0 indicates the center frequency of the interferer is lower than center frequency
of the wanted signal by Foffset_Interferer, otherwise, the center frequency of the interferer is higher
than the center frequency of the wanted signal by Foffset_Interferer. FCarrier_Interferer =
FCarrier_Tx + Foffset_Interferer.

The bandwidth of the interfering signal is determined by the bandwidth of the wanted signal
according to Table 7.5.1-2 ~ Table 7.5.1-3 of [1], i.e. if Bandwidth of the wanted signal is smaller
than 5MHz, the interfering signal would have same bandwidth as the wanted signal, otherwise, the
bandwidth of the interfering signal is 5MHz.

HARQ retransmission can be enabled by setting UE1_HARQ_Enable to YES. When HARQ


retransmission is enabled, EnableTxFilter should be set to NO as ideal lowpass filter is not
supported in HARQ retransmission in current SystemVue version. Number of HARQ processes is 8
for FDD and 7 for TDD. Maximum number of HARQ transmissions is set to 4. The redundancy
version sequence is set to [0,1,2,3].

A Parks-McClellan bandpass filter centered at FCarrier_Out is used in the receiver side. The
PassBandwidth is set to the transmission bandwidth of the wanted signal, and the StopBandwidth
is set to the channel bandwidth. For example, if Bandwidth of wanted signal is 5MHz, then
PassBandwidth = 4.5MHz, StopBandwidth = 5MHz. This filter could be disabled by setting
parameter EnableRxFilter to NO.

By default, the reference measurement channels specified in Annexes A of 3GPP TS 36.104 are
used. If you want to customized the test configuration, please open this workspace in SystemVue
and set UseFRC to NO and set the payload configuration and RB allocation.

The number of simulated frames is set by parameter NumFrames.

Parameter Details
P_WantedSig: Wanted signal mean power over 50 ohm. Range: (-∞:+∞)
P_Interferer: Interfering signal mean power over 50 ohm. Range: (-∞:+∞)
FOffset_Interfer: The interfering signal center frequency offset. Range: (-FCarrier_In:+∞)

116
ADS and SystemVue Integration

EnableRxFilter: Whether enable Rx bandpass filter or not


For details on other parameters, please refer to 3GPP_LTE_BS_Tx and
3GPP_LTE_UE_ReferenceSensitivity.
When HARQ is turned on, the dynamic range used for fast circuit envelope extraction (in ADS
and GoldenGate) might not be exactly the same as the actual dynamic range during VTB
simulation

Simulation Results

Try to change the parameters, run LTE_UE_AdjacentChannelSelectivity_Analysis and check the


simulation results in table ThroughputFraction to see whether the throughput meets the
requirements. The throughput shall be ≥ 95% of the maximum throughput of the reference
measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 of [1].

If ThroughputFraction > 95%, PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Reference
1. 3GPP TS 36.101 v9.3.0 "User Equipment (UE) radio transmission and reception", March 2010.

117
ADS and SystemVue Integration

3GPP_LTE_UE_ReferenceSensitivity

LTE_UE_ReferenceSensitivity_Analysis
This workspace provides a VTB test bench of reference sensitivity power level of LTE UE receiver
according to section 7.3 of 3GPP TS 36.101. The reference sensitivity power level REFSENS is the
minimum mean power applied to both the UE antenna ports at which the throughput shall meet or
exceed the requirements for the specified reference measurement channel.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

118
ADS and SystemVue Integration

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

The transmitted signal mean power is set by SignalPower. SignalPower specifies the mean power
of the transmitted signal when all RBs (resource blocks) are allocated.

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

HARQ retransmission can be enabled by setting UE1_HARQ_Enable to YES. When HARQ


retransmission is enabled, EnableTxFilter should be set to NO as ideal lowpass filter is not
supported in HARQ retransmission in current SystemVue version. Number of HARQ processes is 8
for FDD and 7 for TDD. Maximum number of HARQ transmissions is set to 4. The redundancy
version sequence is set to [0,1,2,3].

By default, the reference measurement channels specified in Annexes A.3.2 of 3GPP TS 36.101 are
used. If you want to customized the test configuration, please open this workspace in SystemVue
and set UseFRC to NO and set the payload configuration and RB allocation.

The number of simulated frames is set by parameter NumFrames.

Parameter Details
1. RF Parameters
NF: Noise figure in receiver. Range: [0:+∞)
For details on other parameters, please refer to RF Parameters.
2. LTE Parameters
HARQ_Enable: specify whether closed-loop HARQ transmission is enabled.
When HARQ is turned on, the dynamic range used for fast circuit envelope extraction (in ADS
and GoldenGate) might not be exactly the same as the actual dynamic range during VTB
simulation

For details on other parameters, please refer to LTE Parameters.


3. Advanced Parameters
UseFRC: Whether use FRC (fixed reference measurement channels) as defined in the specification
or not. The default value is set to YES.
UE1_Config: Payload configuration type. It indicates the meaning of Payload as 0 for MCS index, 1
for Transport block size, 2 for Code rate. The default value is set to Code rate. Active only when
UseFRC is set to NO
UE1_Payload: Specify the payload of each frame according to the selection of Payload_Config. The
default value is set to 1/3 (code rate). Active only when UseFRC is set to NO
For details on other parameters, please refer to Advanced Parameters.

Simulation Results

Try to change the parameters, run 3GPP_LTE_UE_ReferenceSensitivity_Analysis and check the


simulation results in table ThroughputFraction to see whether the throughput meets the

119
ADS and SystemVue Integration

requirements. The throughput shall be ≥ 95% of the maximum throughput of the reference
measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 of [1].

If ThroughputFraction > 95%, PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Reference
1. 3GPP TS 36.101 v9.3.0 "User Equipment (UE) radio transmission and reception", March 2010.

120
ADS and SystemVue Integration

3GPP_LTE_UE_Tx

LTE_UE_Tx_Analysis
This workspace provides a VTB test bench to measure user equipment transmitter characteristics
including spectrum, waveform, CCDF, EVM and ACLR according to [1].
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

121
ADS and SystemVue Integration

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

The number of simulated frames for EVM measurements is set by parameter NumFrames.

Parameter Details
MappingType: The modulation orders, for which 0 for QPSK, 1 for 16QAM, 2 for 64QAM. Range: [0:2].
For details on other parameters, please refer to 3GPP_LTE_BS_Tx.

Simulation Results

Try to change the parameters, run LTE_UE_Tx_Analysis and check the simulation results.
Table ACLR shows Adjacent Channel Leakage power Ratio
Graph CCDF shows the Complementary Cumulative Distribution Function of the transmitted signal
Graph Constellation shows the constellation of each physical channel and signal
Table ErrorSummary shows average EVM, peak EVM, frequency errors and other measured results of
each frame
Table EVM lists EVM of each physical channel and signal
Graph NormalizedEqualizerChannelFrequencyResponse shows the normalized equalizer channel
frequency response
Graph RBErrorMagSpectrum shows the error magnitude spectrum of each RB got from EVM model
Graph Spectrum shows the spectrum of the transmitted signal
Graph Waveform shows the transmitted time domain waveform
EVM is reported in % in this example, i.e. if the result is displayed as 0.187, it means EVM =
0.187%.
If EVM (for different modulation schemes) is better than the limits below [1], then
EVM_PassFailFlag is set to true(1), otherwise, it is set to false(0).

Modulation scheme for PDSCH Required EVM [%]

QPSK 17.5 %

16QAM 12.5 %

64QAM 8%

If ACLR > 45dB, then ACLR_PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation. The DUT is shorted to get the following ideal results. The same results will

122
ADS and SystemVue Integration

be displayed in SystemVue environment if the SVE_Link model is disabled to short.

Reference
1. 3GPP TS 36.104 v9.3.0 "Base Station (BS) radio transmission and reception", March 2010.

123
ADS and SystemVue Integration

3GPP_LTE_UE_Tx_Source

LTE_UE_Tx_Source_Analysis
This workspace provides a VTB test bench to generate LTE uplink signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

124
ADS and SystemVue Integration

The ideal low pass filter for spectrum shaping can be turned on/off by parameter EnableTxFilter.
The number of taps can be set by FIR_Taps. If EnableTxFilter is set to NO, no spectrum shaping
would be applied.

A sink is used to save the generated signal from 0 to TimeStop.

Parameter Details
TimeStop: Stop time of data collection. Range: (0:+∞)
For details on other parameters, please refer to 3GPP_LTE_UE_Tx.

Simulation Results

Try to change the parameters, run LTE_UE_Tx_Source_Analysis and check the simulation results.
Graph Waveform shows the transmitted time domain waveform

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

Reference
1. 3GPP TS 36.104 v9.3.0 "Base Station (BS) radio transmission and reception", March 2010.

125
ADS and SystemVue Integration

NB IoT Workspaces

NB IoT Workspaces
VTB workspaces are provided to analyze NB IoT transmitter characteristics for both user equipment
and base station, respectively

UE Tx
LTE_Advanced_NBIoT_DL_Tx

BS Tx
LTE_Advanced_NBIoT_UL_Tx

In the current implementation, there are only one input port and one output port in the SVE_Link model
used in NB IoT workspaces, which means the DUT (design in ADS/GoldenGate environment) should only
have one input and one output. In the examples, the DUT is connected to the modulator.

How to set SVE_Link properties in NB IoT workspaces


Users can optionally define the SVE_Link properties by setting DefineProperties to YES. When
DefineProperties is set to YES, parameters related to SVE_Link properties, including
InFeedbackLoop, SampleRate, and InputFcs, can be defined by values or expressions.
InFeedbackLoop: Specify whether the SVE_Link is in a feedback loop: NO, YES. In NBIoT examples,
there is no feedback loop, hence InFeedbackLoop is set to NO.
SampleRate: Sample rate of the signal. In NB IoT examples, in the Equations tab of the design,
SamplingRate of the NBIoT system is calculated from BaseSampleRate and OversamplingOption.
Hence, SampleRate is directly set to SamplingRate. The base sample rate for downlink is 1.92MHz. For
uplink, it's 1.92MHz for 15kHz subcarrier spacing and it's 240kHz for 3.75kHz subcarrier spacing.
InputFcs: Array of characterization frequencies of input envelope signals. In current NB IoT examples,
there is only one input port in SVE_Link model, hence, InputFcs is set to [FCarrier_In].

Otherwise, when DefineProperties is set to NO, the VTB process will analyze the full design and
provide such information to the integrating tool.

References

126
ADS and SystemVue Integration

LTE_Advanced_NBIoT_DL_Tx

NBIoT_DL_Tx_Analysis
This example workspace provides a VTB test bench to measure spectrum, CCDF and EVM of an
LTE Advanced NBIoT downlink transmitter.

The center frequency of


the input signal to DUT (SVE_Link in the design) is set by FCarrier_In, while center frequency of the
output signal from DUT (SVE_Link in the design) is set by FCarrier_Out.

RF distortions in the modulator can be simulated by setting parameters GainImbalance,


PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

127
ADS and SystemVue Integration

Please note that those parameters with hide condition set to true will not be shown in ADS/
GoldenGate environment.

Try to change the parameters, run NBIoT_DL_Tx_Analysis and check the simulation results.
Graph CCDF shows the Complementary Cumulative Distribution Function of the transmitted signal
Graph Spectrum shows the spectrum of the transmitted signal
Graph Waveform shows the transmitted time domain waveform

128
ADS and SystemVue Integration

LTE_Advanced_NBIoT_UL_Tx

NBIoT_UL_Tx_Analysis
This example workspace provides a VTB test bench to measure spectrum, CCDF and EVM of an
LTE Advanced NBIoT uplink transmitter.

The center frequency of the input signal to DUT (SVE_Link in the design) is set by FCarrier_In,
while center frequency of the output signal from DUT (SVE_Link in the design) is set by
FCarrier_Out.

RF distortions in the modulator can be simulated by setting parameters GainImbalance,


PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

129
ADS and SystemVue Integration

Please note that those parameters with hide condition set to true will not be shown in ADS/
GoldenGate environment.

Try to change the parameters, run NBIoT_UL_Tx_Analysis and check the simulation results.
Graph CCDF shows the Complementary Cumulative Distribution Function of the transmitted signal
Graph Spectrum shows the spectrum of the transmitted signal
Graph Waveform shows the transmitted time domain waveform

130
ADS and SystemVue Integration

RADAR Workspaces

RADAR Workspaces
VTB workspaces are provided to analyze the Radar signal transmitter.

Tx
Radar_Tx Analysis
Radar_Tx_Source

131
ADS and SystemVue Integration

Radar_Tx Analysis

Radar_Tx_Analysis
This workspace provides a VTB test bench to measure Radar transmitter characteristics including
spectrum, waveform, and ACF.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

Several Radar signal Models are provided in this workspace. You can select SignalType to configure
different Radar signals including BarkerCode, FrankCode, CW, PloyTimeCode, FSK, LFM and PULSE
signals. When the Radar signal type is selected, corresponding parameters are valid.

132
ADS and SystemVue Integration

The transmitted signal mean power is set by SignalPower. SignalPower specifies the mean power
of the transmitted.

Parameter Details

1. RF Parameters
FCarrier_In: Carrier frequency of the input signal to DUT(SVE_Link). Range: (0:+Inf)
FCarrier_Out: Carrier frequency of the output signal from DUT(SVE_Link). Range: (0:+Inf)
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-Inf:+Inf))
MirrorSignal: Mirror signal about carrier
GainImbalance: Gain imbalance in dB. Range: (-Inf:+Inf))
PhaseImbalance: Phase imbalance. Range: (-Inf:+Inf))
I_OriginOffset: I origin offset. Range: (-Inf:+Inf))
Q_OriginOffset: Q origin offset. Range: (-Inf:+Inf))
IQ_Rotation: IQ rotation. Range: (-Inf:+Inf))
2. Measurement Parameters
StopTime: Stop time of data collection. Range: (0:+Inf)
3. Radar Parameters
PRI is used to specify the pulse repetition interval. Range: (0:+Inf)
SubPulseWidth is used to specify the width of each sub-pulse(code). Range: (0:+Inf)
SamplingRate is used to specify the baseband sampling rate. Range: (0:+Inf)
SignalType is used to specify the active radar signal source type.
BarkerCode_CodeLength is used to specify the length of Barker code and the final Barker code is
constructed by CodeLength number of sub-pulses with a pulse width of CodeLength x
SubPulseWidth; valid when SignalType=BarkerCode;
FrankCodeType is used to specify the Frank and P code type; valid when SignalType=FrankCode;
PolyTimeCodeType is used to specify the PolyTimeCode type; valid when
SignalType=PolyTimeCode;
CW_WaveformType is used to specify the CW waveform type; valid when SignalType=CW;
FSK_CodeType is used to specify the FSK type; valid when SignalType=FSK;
CostasType is used to specify the Costas code type; valid when SignalType=FSK; Note that this
parameter is applicable only for the Radar_Tx_Source_Analysis VTB.
4. Advanced Parameters
The following parameters are not exposed in ADS/GoldenGate environment. The default values
of these parameters will be used in the simulation. To change them, please open the workspace
in SystemVue, go to the Parameters tab of the design and change the Default Value there. To
expose them in ADS/GoldenGate environment, please also open the workspace in SystemVue,
go to Parameters tab and change the Hide Condition to false or simply delete the Hide
Condition.

FrankCode_M is used to specify the number of step frequency and the number of samples per
frequency; valid when SignalType=FrankCode; Range: (0, +Inf). The default value is set to 2.
PolyTimeCode_NumberOfSegment is the number of step frequency segment; valid when
SignalType=PolyTimeCode. The default value is set to 4.
PolyTimeCode_DeltaF is the modulation bandwidth; valid when SignalType=PolyTimeCode; Range
Range: (0:+Inf). The default value is set to 1e3.
PolyTimeCode_OverallCodePeriod is the subpulse width; valid when SignalType=PolyTimeCode;
Range: (0:+Inf). The default value is set to 1e-6s.
PolyTimeCode_NumberOfPhase is the number of phase state; valid when
SignalType=PolyTimeCode; Range: (0:+Inf). The default value is set to 2.
CW_Amplitude is used to specify the radar Transmit waveform Magnitude; valid when
SignalType=CW; Range: (0:+Inf). The default value is set to 1.

133
ADS and SystemVue Integration

CW_Period is used to specify Waveform period; valid when SignalType=CW; Range: (0:+Inf). The
default value is set to 1e-4.
CW_LowerFreq is used to specify Start Frequence; valid when SignalType=CW; Range: (0:+Inf). The
default value is set to 10e3.
CW_DeltaFreq is used to specify the delta frequency; valid when SignalType=CW; Range: (0:+Inf).
The default value is set to 50e3.
CostasSequenceDeltaFreq is used to specify the delta frequency of Costas Sequence; valid when
SignalType=FSK and FSKType=Costas; Range: (0:+Inf). The default value is set to 1e6.
LFM_Bandwidth is an array parameter to specify different pulse bandwidth for each staggering PRI
group; valid when SignalType=LFM; Range: (0:+Inf). The default value is set to 5e6.
FM_Offset is an array parameter to specify different frequency domain offset for each staggering
PRI group; valid when SignalType=LFM; Range: (0:+Inf). The default value is set to 0.
FSK_CodeLength is used to specify the number of phases; valid when SignalType=FSK. The default
value is set to Length13.
ACF_NumSamples: Number of samples used to calculate the ACF (auto-correlation function). The
default value is set to 130.
The following parameters cannot be exposed in ADS/GoldenGate environment. The default
values of these parameters will be used in the simulation. To change them, please open the
workspace in SystemVue, go to the Equation tab of the design and change the Default Value
there.

PRI_Combination is an array parameter to specify pulse numbers for each staggering PRI group; for
each element, Range: (0:+Inf). The default value is set to PRI_Combination = 1.
FSK_FHSequence is an array parameter used to specify frequence hopping sequence. For each
element, Range: (0: +Inf). The default value is set to FSK_FHSequence = [1e6, 2e6, 3e6];
FSK_TimeIntervals is an array parameter used to specify Frequence Hopping Time Intervals
Sequence. For each element, Range: (0: +Inf). The default value is set to FSK_TimeIntervals = [1e-5,
1e-5, 1e-5];
CostasSequence is an array parameter used to specify Frequence Hopping Sequence. For each
element, Range: (0: +Inf). The default value is set to CostasSequence = [2,4, 8, 5, 10, 9, 7, 3, 6, 1];
CostasTimePeriod is used to specify Subpulse duration period. Range: (0:+Inf). The default value is
set to CostasTimePeriod = 1e-5;
FSK_FSKPSKSequence is an array parameter used to specify specify FSK/PSK Sequence. For each
element, Range: (0: +Inf). The default value is set to FSK_FSKPSKSequence = [2,4, 8, 5, 10, 9, 7, 3,
6, 1]*1e5;
FSK_FSKPSKSubTimePeriod is used to specify FSK/PSK Subpulse duration period. Range: (0: +Inf).
The default value is set to FSK_FSKPSKSubTimePeriod = 1e-5;

Simulation Results

Try to change the parameters, run Radar_Tx_Analysis and check the simulation results.
Graph ACF shows ACF(auto-correlation function) of the Radar signal.
Graph Spectrum shows the spectrum of the transmitted signal.
Graph WaveformReal shows the real part of transmitted time domain waveform.
Graph WaveformImag shows the image part of transmitted time domain waveform.

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation. The DUT is shorted to get the following ideal results. The same results
will be displayed in SystemVue environment if the SVE_Link model is disabled to short.

134
ADS and SystemVue Integration

135
ADS and SystemVue Integration

Reference
1. Nadav Levanon and Eli Mozeson, Radar Signals, Wiley, New York, 2004.
2. Phillip E. Pace, Detecting and Classifying Low Probability of Intercept Radar, ARTECH HOUSE, MA ,
2009
3. Mark Richards, Fundamentals of Radar Signal Processing, Mcgraw-Hill, New York, 2005
4. Merrill I. Skolnik, Introduction to Radar Systems, Third Edition, Mcgraw-Hill, New York, 2001.

136
ADS and SystemVue Integration

Radar_Tx_Source

Radar_Tx_Source_Analysis
This workspace provides a VTB test bench to generate the Radar signals.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

Several Radar signal Models are provided in this workspace. You can select SignalType to configure
different Radar signals. The supported Radar signal type include BarkerCode, FrankCode, CW,
PolyTimeCode, FSK, LFM and PULSE signals.

137
ADS and SystemVue Integration

The transmitted signal mean power is set by SignalPower. SignalPower specifies the mean power
of the transmitted signal.

Parameter Details

For details on other parameters, please refer to Radar_Tx Analysis.

Simulation Results

Try to change the parameters, run Radar_Tx_Source_Analysis and check the simulation results.
The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation. The DUT is shorted to get the following ideal results. The same results
will be displayed in SystemVue environment if the SVE_Link model is disabled to short.

Reference
1. Nadav Levanon and Eli Mozeson, Radar Signals, Wiley, New York, 2004.
2. Phillip E. Pace, Detecting and Classifying Low Probability of Intercept Radar, ARTECH HOUSE, MA ,
2009
3. Mark Richards, Fundamentals of Radar Signal Processing, Mcgraw-Hill, New York, 2005
4. Merrill I. Skolnik, Introduction to Radar Systems, Third Edition, Mcgraw-Hill, New York, 2001.
Graph Waveform shows the transmitted time domain waveform

138
ADS and SystemVue Integration

WLAN 11ac Workspaces

WLAN 11ac Workspaces


VTB workspaces are provided to analyze WLAN 802.11ac transmitter and receiver characteristics
according to [1].

Tx
WLAN_802.11ac_Tx
WLAN_802.11ac_Tx_Source

Rx
WLAN_802.11ac_ReferenceSensitivity
WLAN_802.11ac_AdjacentChannelRejection
WLAN_802.11ac_NonadjacentChannelRejection

In current implementation, there are only one input port and one output port in the SVE_Link model
used in WLAN 802.11ac workspaces, which means the DUT (design in ADS/GoldenGate environment)
should only have one input and one output. In Tx examples, the DUT is connected after the modulator. In
Rx examples, the DUT is connected before the demodulator in the Rx chain. Please refer to the help
document of each workspace for more information. in which you can find the detailed schematic.

In current SystemVue implementation, Bandwidth 80+80 MHz is not supported in the WLAN 802.11ac
receiver and EVM model. So there is no option of BW 80+80 MHz in RX VTBs for analyzing WLAN
802.11ac receiver characteristics.

How to set SVE_Link properties in LTE workspaces


Users can optionally define the SVE_Link properties by setting DefineProperties to YES. When
DefineProperties is set to YES, parameters related to SVE_Link properties, including
InFeedbackLoop, SampleRate, and InputFcs, can be defined by values or expressions.
InFeedbackLoop: Specify whether the SVE_Link is in a feedback loop: NO, YES. In WLAN 802.11ac
examples, there is no feedback loop, hence InFeedbackLoop is set to NO.
SampleRate: Sample rate of the signal. In WLAN 802.11ac examples, in the Equations tab of the
design, SampleRate is calculated from Bandwidth and OversampleRation.
InputFcs: Array of characterization frequencies of input envelope signals. In WLAN 802.11ac examples,
there is only one input port in SVE_Link model, hence InputFcs is set to [FCarrier_In].

Otherwise when DefineProperties is set to NO, the VTB process will analyze the full design and
provide such information to the integrating tool.

139
ADS and SystemVue Integration

Reference
1. IEEE P802.11ac/D1.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications", May 2011.

140
ADS and SystemVue Integration

WLAN_802.11ac_AdjacentChannelRejection

WLAN_802.11ac_ACR_Analysis
This workspace provides a VTB test bench to analyze Rx adjacent channel rejection of the 802.11ac
one antenna receiver. Adjacent channel rejection for W MHz channels (where W is 20, 40, 80 or
160) shall be measured by setting the desired signal’s strength 3 dB above the rate dependent
sensitivity specified in Table 22-21 (Receiver minimum input level sensitivity) of [1] and raising the
power of the interfering signal of W MHz bandwidth until 10% PER is caused for a PSDU length of
4096 octets. The power difference between the interfering and desired channel is the corresponding
adjacent channel rejection. The center frequency of the adjacent channel shall be placed W MHz
away from the center frequency of the desired signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.

141
ADS and SystemVue Integration

The wanted signal mean power is set by parameter P_WantedSig, while the interfering signal mean
power is set by parameter P_InterferingSig.

A Butterworth IIR bandpass filter centered at FCarrier_Out is used in the receiver side. The
PassBandwidth is set to the bandwidth of the wanted signal, the PassAtten is set to 3 and Order is
set to 5. This filter could be disabled by setting parameter EnableRxFilter to NO.

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

The number of frames to be simulated is specified by NumFrames.

Parameter Details
P_WantedSig: Wanted signal mean power over 50 ohm. Range: (-∞:+∞)
P_InterferingSig: Interfering signal mean power over 50 ohm. Range: (-∞:+∞)
EnableRxFilter: Whether enable Rx band pass filter or not
For details on other parameters, please refer to WLAN_802.11ac_Tx.

Simulation Results

Try to change the parameters, run WLAN_802.11ac_ACR_Analysis and check the simulation results
in table FER to see whether the FER meets the requirements. The FER shall be ≤ 10%.

If FER < 10%, then PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Reference
1. IEEE P802.11ac/D1.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", May 2011.

142
ADS and SystemVue Integration

WLAN_802.11ac_NonadjacentChannelRejection

WLAN_802.11ac_NonACR_Analysis
This workspace provides a VTB test bench to analyze Rx nonadjacent channel rejection of the
802.11ac one antenna receiver. Nonadjacent channel rejection for W MHz channels (where W is 20,
40, 80 or 160) shall be measured by setting the desired signal’s strength 3 dB above the rate-
dependent sensitivity specified in Table 22-21 (Receiver minimum input level sensitivity) of [1]\, and
raising the power of the interfering signal of W MHz bandwidth until a 10% PER occurs for a PSDU
length of 4096 octets. The power difference between the interfering and desired channel is the
corresponding nonadjacent channel rejection. The center frequency of the nonadjacent channel
shall be placed 2×W MHz or more away from the center frequency of the desired signal.
A simple design to use this VTB is shown below.

143
ADS and SystemVue Integration

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
The wanted signal mean power is set by parameter P_WantedSig, while the interfering signal mean
power is set by parameter P_InterferingSig.

A Butterworth IIR bandpass filter centered at FCarrier_Out is used in the receiver side. The
PassBandwidth is set to the bandwidth of the wanted signal, the PassAtten is set to 3 and Order is
set to 5. This filter could be disabled by setting parameter EnableRxFilter to NO.

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

RF distortions can be introduced by setting parameters GainImbalance, PhaseImbalance, etc.

The number of frames to be simulated is specified by NumFrames.

Parameter Details

For details on parameters, please refer to WLAN_802.11ac_AdjacentChannelRejection.

Simulation Results

Try to change the parameters, run WLAN_802.11ac_NonACR_Analysis and check the simulation
results in table FER to see whether the FER meets the requirements. The FER shall be ≤ 10%.

If FER < 10%, then PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Reference
1. IEEE P802.11ac/D1.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", May 2011.

144
ADS and SystemVue Integration

WLAN_802.11ac_ReferenceSensitivity

WLAN_802.11ac_ReferenceSensitivity

WLAN11ac_ReferenceSensitivity_Analysis
This workspace provides test bench to analyze receiver minimum input sensitivity of the 802.11ac
signals. The packet error rate (PER) shall be less than 10% for a PSDU length of 4096 octets with
the rate-dependent input levels listed in Table 22-21 (Receiver minimum input level sensitivity) of
[1]. The test applies to non-STBC modes, 800 ns GI and BCC.
For example, for 80MHz, 64QAM, Rate 2/3, the minimum sensitivity is -60 dBm.

A simple design to use this VTB is shown below.

145
ADS and SystemVue Integration

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set by parameter NF.

The number of frames to be simulated is specified by NumFrames.

Parameter Details
NF: Noise figure in receiver. Range: [0:+∞)
NumFrames: number of frames to be simulated. Range: [1:+∞)
For details on other parameters, please refer to WLAN_802.11ac_Tx.

Simulation Results

Try to change the parameters, run WLAN11ac_ReferenceSensitivity_Analysis and check the


simulation results in table FER to see whether the FER meets the requirements.

If FER < 10%, then PassFailFlag is set to true(1), otherwise, it is set to false(0).

The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Reference
1. IEEE P802.11ac/D1.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", May 2011.

146
ADS and SystemVue Integration

WLAN_802.11ac_Tx

WLAN11ac_1Ant_Analysis
This workspace provides a VTB test bench to analyze the CCDF, EVM, PAPR, spectrum and
waveform of the signal generated by WLAN 802.11ac single antenna transmitter.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

147
ADS and SystemVue Integration

The number of OFDM data symbols in each frame is dertermined by CodingType and
MPDUDataLength. The other parameters related to the determination of number of OFDM symbols
in a frame include AggregatedMPDU, NumMPDUPerUser, MPDUMACHeader and ShortGI. These
parameters are set to use default values: AggregatedMPDU = 1, NumMPDUPerUser = 1,
MPDUMACHeader = 0 and ShortGI = 0. To change those parameters, please open this workspace in
SystemVue, go to the Equations tab of the design and change the formulas.

The number of frames for EVM measurements is specified by FrameToAverage.

Parameter Details
1. RF Parameters
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
For details, please refer to RF Parameters.
2. WLAN 802.11ac Parameters
IdleInterval: idle interval between two frame packets. Range: [0:+∞)
Bandwidth: bandwidth of WLAN 11 ac, the type is enum and it can be selected as BW 20 MHz, BW
40 MHz, BW 80 MHz, BW 160 MHz and BW 80+80 MHz for Source. The receiver and EVM model
does not support BW 80+80 MHz at present.
OversampleRatio: Over-sampling ratio option, the type is enum and it can be selected as x1 , x2, x4
and x8 in the Source and Receiver.
MCS: Modulation coding scheme for the user.The supported MCSs for different Bandwidth and
number of spatial streams are defined according to Section 22.5 [1]. Range [0:9].
CodingType: coding type for all users for which 0 means binary convolutional code (BCC) and 1
means low density parity check (LDPC) code.
MPDUDataLength: Data length of MPDU. Range [0:11426].
NumFrames: Number of frames for EVM measurements. Range: [1:+∞)
CompensateIQMismatch: If set YES, the demodulation tries to compensate for IQ Gain Imbalance,
IQ Quadrature Error, and IQ Timing Skew found in the input signal. This allows for EVM
computations which exclude any IQ impairments: NO, YES

Simulation Results

Try to change the parameters, run WLAN11ac_1Ant_Analysis and check the simulation results.

Graph Tx_CCDF shows the Complementary Cumulative Distribution Function of the transmitted
signal
Table Tx_EVM lists average EVM and EVM for each frame
Table Tx_PAPR shows the Peak to Average Power Ratio
Graph Tx_Spectrum shows spectrum of the transmitted signal
Graph Tx_SpectrumMask shows whether the spectrum mask is met
Graph Tx_Waveform shows the transmitted time domain waveform

148
ADS and SystemVue Integration

RCE is reported in dB in this example.


If data RCE is better than the limits below [1], then RCE_PassFailFlag is set to true(1), otherwise, it is set
to false(0).

MCS Modulation Coding rate Relative constellation error (dB)

0 BPSK 1/2 -5

1 QPSK 1/2 -10

2 QPSK 3/4 -13

3 16-QAM 1/2 -16

4 16-QAM 3/4 -19

5 64-QAM 2/3 -22

6 64-QAM 3/4 -25

7 64-QAM 5/6 -27

8 256-QAM 3/4 -30

9 256-QAM 5/6 -32

The following graphs would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation. The DUT is shorted to get the following ideal results. The same results
will be displayed in SystemVue environment if the SVE_Link model is disabled to short.

Reference
1. IEEE P802.11ac/D1.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", May 2011.

149
ADS and SystemVue Integration

WLAN_802.11ac_Tx_Source

WLAN11ac_Tx_1Ant_Source_Analysis
This workspace provides a VTB test bench to generate WLAN 802.11ac signal.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

The number of OFDM data symbols in each frame is dertermined by CodingType and
MPDUDataLength. The other parameters related to the determination of number of OFDM symbols
in a frame include AggregatedMPDU, NumMPDUPerUser, MPDUMACHeader and ShortGI. These

150
ADS and SystemVue Integration

parameters are set to use default values: AggregatedMPDU = 1, NumMPDUPerUser = 1,


MPDUMACHeader = 0 and ShortGI = 0. To change those parameters, please open this workspace in
SystemVue, go to the Equations tab of the design and change the formulas.

A sink is used to save the generated signal from 0 to TimeStop.

Parameter Details
TimeStop: Stop time of data collection. Range: (0:+∞)
For details on other parameters, please refer to WLAN_802.11ac_Tx.

Simulation Results

Try to change the parameters, run WLAN11ac_1Ant_Source_Analysis and check the simulation
results.
Graph Tx_Waveform shows the transmitted time domain waveform

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

Reference
1. IEEE P802.11ac/D1.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", May 2011.

151
ADS and SystemVue Integration

WLAN 11ad Workspaces

WLAN 11ad Workspaces


VTB workspaces are provided to analyze WLAN 11ad transmitter and receiver characteristics
according to [1].

Tx
WLAN 11ad transmitter characteristics according to section 21 of [1]
WLAN_11ad_Tx
WLAN_11ad_Tx_Source

Rx
WLAN 11ad receiver characteristics according to section 21 of [1]
WLAN_11ad_RxSensitivity

In current implementation, there is only one input port and one output port in the SVE_Link model used
in WLAN 11ad workspaces, which means the DUT (design in ADS/GoldenGate environment) should only
have one input and one output. In Tx examples, the DUT is connected after the modulator. In Rx
examples, the DUT is connected before the demodulator in the Rx chain. Please refer to the help
document of each workspace for more information in which you can find the detailed schematic.

How to set SVE_Link properties in LTE workspaces


Users can optionally define the SVE_Link properties by setting DefineProperties to YES. When
DefineProperties is set to YES, parameters related to SVE_Link properties, including
InFeedbackLoop, SampleRate, and InputFcs, can be defined by values or expressions.
InFeedbackLoop: Specify whether the SVE_Link is in a feedback loop: NO, YES. In WLAN 802.11ad
examples, there is no feedback loop, hence InFeedbackLoop is set to NO.
SampleRate: Sample rate of the signal. In WLAN 802.11ad examples, in the Equations tab of the
design, SampleRate is calculated from MCS and OversampleRation.
InputFcs: Array of characterization frequencies of input envelope signals. In WLAN 802.11ad examples,
there is only one input port in SVE_Link model, hence InputFcs is set to [FCarrier_In].

Otherwise when DefineProperties is set to NO, the VTB process will analyze the full design and
provide such information to the integrating tool.

References
1. IEEE P802.11ad/D4.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", July 2011.

152
ADS and SystemVue Integration

WLAN_11ad_RxSensitivity

WLAN_11ad_RxSensitivity_Analysis
This workspace provides a test bench of reference sensitivity power level of WLAN 11ad receiver
according to section 21.3.3 of [1]. The reference sensitivity power level is the minimum mean power
received at the antenna connector at which a PER requirement shall be met for a specified MCS.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.
In our implementation, the output signal from WLAN_11ad_Source is the 1x-sampled complex
baseband signals. Then the signal is oversampled in the filter models with the oversample ratio

153
ADS and SystemVue Integration

specified in the OversampleOption parameter. With the default, the pre-configured filter types for
both SC and OFDM modulation are as follows:
SC: RaisedCosine filter with SymbolRate = 1.76e9 Hz, RollOff (Alpha) = 0.5
OFDM: Flat Top filter with PassFreq = 2.5e9 Hz, Order = 96

For MCS 13 to 24, the OFDM modulation is used and for other case, SC modulation is used.

The received signal mean power is set by SignalPower. Please refer to the last table to set this
parameter for all MCS

An AddNDensity model with NDensity = -173.975dBm is used to introduce thermal noise for room
temperature (T = 300K). The noise figure is set to 10.

The number of frames to be simulated is specified by NumTestFrames.

Parameter Details
FramesToMeas: number of frames to be simulated. Range: [1:+∞)
For details on other parameters, please refer to WLAN_11ad_Tx.

Simulation Results

For MCS0, the PER shall be less than 5% for a PSDU length of 256 octets specified by parameter
PSDU_Len. For the other MCSs, the PER shall be less than 1% for a PSDU length of 4096 octets
specified by parameter PSDU_Len.
Try to change the parameters, run WLAN_11ad_RxSensitivity_Analysis and check the simulation
results in table FER to see whether the FER meets the requirements.
The following table would be shown in ADS/GoldenGate DDS tool automatically when the adx file is
imported after simulation.

Table 21-3 of the section 21.3.3.9 of [1] listed the MCS dependent input levels. It assumes 5 dB
implementation loss and 10 dB noise factor (Noise Figure). But in the current implementation, for
some MCS cases (MCS 13 ~ 24), the implementation loss of the receiver is more than 5 dB and for
other cases, the implementation is less than 5 dB. Here we listed the actual input level for all MCS
in the implementation.

154
ADS and SystemVue Integration

MCS Index Receive Sensitivity (dBm) Actual Input Level (dBm)

0 -78 -79

1 -68 -70

2 -67 -69

3 -65 -67

4 -64 -66

5 -62 -64

6 -63 -65

7 -62 -64

8 -61 -63

9 -59 -61

10 -55 -57

11 -54 -56

12 -53 -55

13 -66 -62.5

14 -64 -61.5

15 -63 -60.5

16 -62 -60.5

17 -60 -59

18 -58 -57

155
ADS and SystemVue Integration

19 -56 -55

20 -54 -53

21 -53 -52

22 -51 -50

23 -49 -48

24 -47 -46

25 -64 -66

26 -60 -62

27 -57 -59

28 -57 -59

29 -57 -59

30 -57 -59

31 -57 -59

Reference
1. IEEE P802.11ad/D4.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", July 2011.

156
ADS and SystemVue Integration

WLAN_11ad_Tx

WLAN_11ad_Tx_Analysis
This workspace provides a VTB test bench to analyze the CCDF, EVM, spectrum and waveform of
the signal generated by WLAN 802.11ad transmitter.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

157
ADS and SystemVue Integration

In our implementation, the output signal from WLAN_11ad_Source is the 1x-sampled complex
baseband signals. Then the signal is oversampled in the filter models with the oversample ratio
specified in the OversampleOption parameter. With the default, the pre-configured filter types for
both SC and OFDM modulation are as follows:
SC: RaisedCosine filter with SymbolRate = 1.76e9 Hz, RollOff (Alpha) = 0.5
OFDM: Flat Top filter with PassFreq = 2.5e9 Hz, Order = 96
For MCS 13 to 24, the OFDM modulation is used and for other case, SC modulation is used.

The number of frames for EVM measurements is specified by FrameToMeas.

Parameter Details
1. RF Parameters
SignalPower: Transmitted signal mean power over 50 ohm. Range: (-∞:+∞)
For details, please refer to RF Parameters.
2. WLAN 11ad Parameters
OversampleRatio: Over-sampling ratio option, the type is integer and it can be set to 0 ~ 3 which
means x1 , x2, x4 and x8 in the Source and Receiver
InterpacketGap: idle interval between two packets. Zeros will be inserted during this interval.
Range: [0:+∞).
PSDU_Len: the PHY PSDU length in octets. For non-Control PHY modes it is limited to the range
[0:262143]. For Control PHY modes (MCS 0), it is limited to the range[4:1023]
MCS: modulation and coding scheme. For MCS 0~12 and MCS 25~31, it is single carrier modulation
and the output sample rate is 1.76GHz. For MCS 13~24, it is OFDM modulation and the output
sample rate is 2.64GHz.
FramesToMeas: Number of frames for EVM measurements. Range: [1:+∞)

Simulation Results

Try to change the parameters, run WLAN_11ad_Tx_Analysis and check the simulation results.

Graph Tx_Waveform shows the transmitted time domain waveform


Graph Tx_CCDF shows the Complementary Cumulative Distribution Function of the transmitted
signal
Table Tx_EVM lists average EVM and EVM for each frame
Graph Tx_Spectrum shows spectrum of the transmitted signal

Graph Tx_Constellation shows constellation symbols of the transmitted data symbols

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

158
ADS and SystemVue Integration

Reference
1. IEEE P802.11ad/D4.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", July 2011.

159
ADS and SystemVue Integration

WLAN_11ad_Tx_Source

WLAN_11ad_Tx_Source_Analysis
This workspace provides a VTB test bench to generate WLAN 802.11ad signal following the TGad
Draft Amendment (P802.11ad/D4.0) July. 2011.
A simple design to use this VTB is shown below.

The center frequency of the input signal to DUT(SVE_Link in the design) is set by FCarrier_In, while
center frequency of the output signal from DUT(SVE_Link in the design) is set by FCarrier_Out.
RF distortions can be simulated by setting parameters GainImbalance, PhaseImbalance, etc.

The transmitted signal mean power is set by SignalPower.

160
ADS and SystemVue Integration

In our implementation, the output signal from WLAN_11ad_Source is the 1x-sampled complex
baseband signals. Then the signal is oversampled in the filter models with the oversample ratio
specified in the OversampleOption parameter. With the default, the pre-configured filter types for
both SC and OFDM modulation are as follows:
SC: RaisedCosine filter with SymbolRate = 1.76e9 Hz, RollOff (Alpha) = 0.5
OFDM: Flat Top filter with PassFreq = 2.5e9 Hz, Order = 96

For MCS 13 to 24, the OFDM modulation is used and for other case, SC modulation is used.
A sink is used to save the generated signal from 0 to TimeStop.

Parameter Details
TimeStop: Stop time of data collection. Range: (0:+∞)

For details on other parameters, please refer to WLAN_11ad_Tx.

Simulation Results

Try to change the parameters, run WLAN_11ad_Tx_Source_Analysis and check the simulation
results.
Graph Tx_Waveform shows the transmitted time domain waveform

161
ADS and SystemVue Integration

The following graph would be shown in ADS/GoldenGate DDS tool automatically when the adx file
is imported after simulation.

Reference
1. IEEE P802.11ad/D4.0, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
specifications", July 2011.

162
ADS and SystemVue Integration

RF-SystemVue Co-simulation

RF-SystemVue Co-simulation
In ADS design environment, the circuit designers can use the Verification Test Bench (VTB) as
sources/sinks and measurement setups from SystemVue to verify the performance of a circuit using
real world complex modulated signals conforming to advanced wireless standards such as 2G/3G/
4G.

The VTB only supports Circuit Envelope - SystemVue cosimulation as shown in the following figure.
It does not support other simulation types such as Transient.

SystemVue creates source signals with a time step computed by SystemVue and simulates until all
of the data is collected by the sinks. In this mode, the Circuit Envelope stop time and time step are
given by SystemVue and cannot be set by the user. The sources and sinks are internally managed
by the SystemVue Engine while the circuit is simulated by ADS. The source ports and sink
terminations do not generate any thermal noise in the Circuit Envelope simulation. Only those
circuit components that are present in the circuit schematic will generate noise, assuming that the
Circuit Envelope controller has the "Turn on all noise option" enabled. If thermal noise is desired on
the input signal or output sinks, it should be generated by the SystemVue design.

If the SystemVue design cannot be modified, then this noise can be added to the circuit schematic
by adding a noise voltage source between the VTB and the circuit; an example is shown below.

163
ADS and SystemVue Integration

Basic Co-simulation
After creating the circuit design, insert a VTB component as a source/sink in the circuit to verify its
performance.

Setting up the VTB Component


You can modify the VTB component by double-clicking the component. For information on each of
the parameters, see the parameters section of the built-in VTB components.

Setting up the Envelope Controller


It is advisable to insert an Envelope controller from the VTB component. This will ensure that the
controller contains the default fundamental frequencies, which work well for most of the designs.
Once the Envelope controller is available, double-click the controller to modify its parameters.

164
ADS and SystemVue Integration

Times Are not Editable

When the design is in the VTB mode, the Stop Time and Time step of the controller are determined
by the SystemVue engine during cosimulation and are not editable.

165
ADS and SystemVue Integration

Fast Envelope Setup

The Fast Envelope cosimulation, results in better performance. To enable the fast envelope
cosimulation, do the following:
1. Click the Fast Cosim tab.
2. Select Enable fast cosimulation.

3. Set the parameters appropriately for cosimulation.

166
ADS and SystemVue Integration

Other Envelope Parameters

You can also modify other envelope parameters. For information, see Envelope Simulation
Parameters.

The RF simulation output by default is disabled on the Envelope controller. If you enable it by modifying
the Output tab of the Envelope controller, it will affect the cosimulation performance and create a huge
RF simulation dataset.

Specifying the Simulation Settings


The Simulation Settings is used to specify the dataset and the Data Display similar to the regular
ADS simulation.

For the cosimulation, there are two different datasets:


Results from RF Simulator: the dataset name is the one specified in the Simulation Settings. In the
above example, the name is cell_1.ds
Results from SystemVue Engine: the dataset name is the one specified with additional
<cellname>_VTB, for example: cell_1_VTB.ds

RF-SystemVue cosimulation does not support Remote, Distributed, or Simulation Manger mode.

167
ADS and SystemVue Integration

Simulating the Design

Click the Simulate icon or select Simulate > Simulate from the Schematic view to start the
simulation. This co-simulation can take very long to complete. The status window will indicate the
progress of the simulation.

Viewing the VTB Results


Once the simulation finishes, the simulation results from the SystemVue engine will be
automatically displayed in the Data Display (DDS), if the Open Data Display when simulation
completes option is selected in the Simulation Settings dialog box.
To view the RF simulation results after the simulation has run:
Select Window > New Data Display Window from the Schematic view.
or
Click the New Data Display Window icon from the toolbar.
The Data Display window is displayed.

The RF simulation output by default is disabled on the Envelope controller. To output it, you need to
modify the Output tab of Envelope controller.

Advanced Co-simulation

Supported Advanced Simulation Controllers


Parameter Sweep with RF-SystemVue Co-simulation
Monte Carlo with RF-SystemVue Co-simulation

Limitations
MeasEqn can only measure RF simulation results.
VTB parameter PortZ is not supported with Parameter Sweep.
Optimization, Yield, YieldOptim, Doe, Sensitivity are not supported.

168
ADS and SystemVue Integration

Model Export

Model Export
With the ADS and SystemVue integration, comprehensive verification of RFIC and Mixed-Signal
designs is possible using SystemVue. From ADS 2017 update 0.3, ADS can create and export
behavioral models to be used by SystemVue. Following is the supported method for model export.
Exporting Fast Circuit Envelope Models

ADS always performs a full envelope simulation before the export procedure. This allows the
verification of the circuit. It is assumed that the circuit is working fine, before the export procedure.
The normal ADS result structure is available after the verification simulation.

169
ADS and SystemVue Integration

Exporting Fast Circuit Envelope Models

Exporting Fast Circuit Envelope Models


ADS creates an FCE model file after performing a standard fast envelope simulation (Fast Envelope
= Level 1 or Level 3). This file can be transferred to SystemVue, and used with the
FastCircuitEnvelope model of the Data Flow Library. For more information, refer to the SystemVue
documentation.

How to Generate an FCE Model File


To generate an FCE model file, perform the following steps:
1. Create or open a schematic.
2. Add Circuit Envelope simulation controller.
3. Configure the CE controller parameters and on the Env Setup tab, make the following settings:
a. Select Enable Fast Envelope.
b. Select the Modeling level option.
c. Select the Modeling accuracy option.
For more information on CE parameters, see Envelope Simulation Parameters.
4. Run the simulation.

After simulating the design, an *.fce model file is created in the data directory. Invoke SystemVue
and instantiate a FastCircuitEnvelope model to configure the settings and run the behavioral model
with SystemVue. For more information, refer to the SystemVue documentation.

170
This information is subject to
change without notice.

www.keysight.com

You might also like