E6567E cdma2000/1xEV-DO/LTE Wireless Test Manager

 

Last updated: Dec/2012

Copyright 1999-2012 Agilent Technologies

All Rights Reserved

 

This document describes the features that are in the Agilent Technologies E6567E cdma2000/1xEV-DO/LTE Wireless Test Manager releases. This document contains the original features, as well as enhancements that have been added over time. To get answers to frequently asked questions, as well as details on how to fix known problems, go to the web page http://www.agilent.com/find/E6567D or http://www.agilent.com/find/E6567E and select the Technical Support link.

 

Select the appropriate link below to view the required release.

 

E.02.00 Release – Dec 2012 (Support E6621A PXT LTE4 release, additional LTE Bandwidth: 1.4MHz, 3MHz, 15.MHz, LTE Blind Channel/BW Handover, LTE Loop for channel/band handovers, new LTE TCs support)

 

E.01.00 Release – May 2012 (Support E6621A PXT LTE3 release, LTE TDD measurements and more)

 

 

D.01.01 Release – Feb 2012 (update release)

 

D.01.00 Release – July 2011 (initial release)

 

Contact Information

Service and Support

 

 

E.02.00 Release – Dec 2012 (Support E6621A PXT LTE4 release, additional LTE Bandwidth: 1.4MHz, 3MHz, 15.MHz, LTE Blind Channel Handover, LTE DL EARFCN Loop)

E6621A/PXT Requirements: WTM E.02.00 is compatible with E6621A release versions v6.4.1.x (LTE4 releases)

 

Additional functionality to E.01.00 Release – May 2012 as following:

 

1.     New LTE Test Steps:

·         LTE Blind Channel Handover

This test step has been added to perform blind frequency/channel handovers on the same LTE operating band using LTE4 PXT feature.

The blind handover works with one scenario and using the destination channel/frequency message overwrites.

·         LTE Channel Bandwidth Handover

This test step has been added to perform channel bandwidth on the same LTE operating band/frequency

The bandwidth handover works with one PXT scenario having one handover RRC Message per channel bandwidth.

·         LTE General On/Off Time Mask

This test step has been added to support test case 6.3.4.1 General ON/OFF time mask defined in TS 36.521-1.

·         LTE Aggregate Power Control Tolerance

This test step has been added to support test case 6.3.5.3 Aggregate Power Control Tolerance defined in TS 36.521-1.

2.     Modified test steps:

·         LTE Initial Setup

- Chan bandwidth setting has been extended to include all the bandwidths: 1.4MHz, 3.0MHz, 5MHz, 10MHz, 15MHz, 20MHz.

- Transmission Mode has been added: TM1, TM2, TM3, TM4, TM6.

·         Start Loop

Start Loop has been extended for LTE channel and band handovers.

The new Loop Parameters implying a blind handover at every loop iteration are:

- LTE DL EARFCN: indicating new DL EARFCN

- LTE DL/UL EARFCN Table:  each entry in the table indicates new DL/UL EARFCN

- LTE Band Table:  each entry in the table indicates new Band and DL/UL EARFCN

E.01.00 Release – May 2012 (E6621A PXT LTE3 release, LTE TDD measurements and more)

Supported E6621A Firmware and Hardware

E6621A/PXT Requirements: WTM E.01.00 is compatible with E6621A release versions v6.3.1.x (LTE3 releases)

 

Additional functionality to D.01.01 Release – Feb 2012 as following:

3.     E6621A LTE3 compatibility

WTM full compatibility with E6621A LTE3 release (support of PXT release 6.3.1.0 and above)

4.     LTE-TDD Support

Support of all LTE test steps in LTE-TDD:

·         LTE UE Maximum Output Power

·         LTE Maximum Power Reduction

·         LTE Minimum Output Power

·         LTE Frequency Error

·         LTE Error Vector Magnitude

·         LTE Carrier Leakage

·         LTE EVM Equalizer Spectrum Flatness

·         LTE Occupied Bandwidth

·         LTE Spectrum Emission Mask

·         LTE Adjacent Channel Leakage Power Ratio

·         LTE Reference Sensitivity Level

·         LTE Maximum Input Level

·         LTE Tiered RX Reference Sensitivity Search

·         LTE Tiered RX Reference Sensitivity Search AT UE Power

·         LTE Quick Test

·         LTE Initial Setup

·         LTE PXT Reset

·         LTE PXT Emulation Run State

·         LTE UE Connect

·         LTE UE Disconnect

·         LTE Channel Handover

·         LTE Band Handover

5.     LTE Overwrite parameters:

 

"Overwrite" means that the user can set this parameter dynamically without change of the PXT user scenario.

For example, a user can use the same LTE test plan for different LTE channel bandwidths, LTE operating bands, and so on.

 

The LTE Initial Setup test step has been modified / extended for the following parameters in table below.

 

 

DL Channel (extended)

extended to supoprt new LTE bands

0:5379 or 5730:8689 or  36000:45589

E UTRA Band (extended)

extended to support new LTE bands:

1.:25 or 33..43

Channel Bandwidth (new)

new parameter: 5 MHz, 10 MHz, 20 MHz

Scenario File Name Prefix (modified)

new default PXT scenario: FDD_NonCombined_v6.3

pMax (new)

new parameter: -50..30

p0 NominalPUSCH (new)

new parameter: -126..24

P0 UE PUSCH (new)

new parameter: -8..7

NS Value Additional Spectrum Emission (new)

new parameter: 1..32

Sec Authentication Algorithm  (new)

Dummy, MILENAGE

Security Key Option  (new)

OP, OPc

Sec OP Value (new)

String (128 bits)

Sec OPc Value (new)

String (128 bits)

 

6.     Modified test steps

·         LTE EVM Equalizer Spectrum Flatness

This test step has been modified to be aligned with 36.521-1 and display Range 1 and/or Range 2 Spectrum Flatness Max Peak to Peak (dB) depending on the uplink signal frequency:

·         LTE Tiered RX Reference Sensitivity Search

RSRP measurements have been added so WTM user might wish to turn on/off the RSRP (reference signal received power) UE measurements while searching for the reference sensitivity of the device under test.

·         LTE Tiered RX Reference Sensitivity Search AT UE Power

RSRP measurements have been added so WTM user might wish to turn on/off the RSRP (reference signal received power) UE measurements while searching for the reference sensitivity of the device under test at a specified UE power.

7.     New LTE Test Steps

 

·         LTE Channel Handover

This test step has been added to perform blind frequency/channel handovers on the same LTE operating band

 

·         LTE Band Handover

This test step has been added to perform a band handover (blind frequency handover) to a specified new frequency of potentially a different LTE operating band.

 

·         Send Receive GPIB With Wait Timer

This test step is similar to old “Send Receive GPIB” test step. The difference is that this new test step has a new table “GPIB Commands with Specs and Wait Timer” in which one column in the data base has been added “Wait Time (Seconds)”. After executing the SCPI command WTM will wait the configured amount of time before proceeding to the next row in the table for the following SCPI command to send.

8.     New LTE Test Plans and Database:

 

Two new LTE test plans have been created and database have been updated to allow the user to reuse this LTE test plan for any channel bandwidths and any LTE operating bands

 

                - LTE FDD Test Plan: standard default LTE FDD testing

                - LTE TDD Test Plan: standard default LTE TDD testing

                - Database: has been modified for new parameters and new default test points

 

D.01.01 Release – Feb 2012 (update release)

 

Same functionality as D.01.00 Release – July 2011 with the following bug fix:

- Fixed WTM Fails to Initialize = FIXED (WIN 7 issue)
If there are processes running on the computer that have names longer than 15 characters, WTM fails with the following message when trying to read those processes:  "Error occurred during initialization of WTM".  The cause of this error is a known issue with .NET Framework 1.1.  Microsoft has documented this issue at the following:

http://support.microsoft.com/kb/952262.

 

DLL details: New WTM Framework 1.9.3

 

- Fixed Send Receive GPIB with E6621A.

- Fixed E6621A setting of user defined security K value

 

D.01.00 Release – July 2011

 

D.01.00 Release – Overview

Wireless Test Manager Modifications

Supported 8960 Test Applications

Supported E6621A Firmware and Hardware

 

Known Issues

Installation Issues

Uninstalling older software versions

Uninstalling all software versions

The USB security key is not recognized after installation

Back-up language files

??? <reference number> being displayed in the WTM UI

Other Issues

Issues known at shipment release

Issues discovered after release

E6621A Issues

 

Component Release Information

 

D.01.00 Release – Overview

 

To see the latest information for the E6567D go to the Agilent Technologies web site http://www.agilent.com/find/E6567D.

 

Wireless Test Manager Modifications

1.     Added support for the E6621A PXT

2.     Added new LTE Test Steps that use the E6621A PXT

3.     Added support for Windows 7 operation system

Supported 8960 Test Applications

 

The following TA’s are supported by the D.01.00 release of the E6567D.
 

E1987A

A.05.18 or later

E1962B

B.12.12 or later

E1966A

A.07.13 or later

 Supported E6621A Firmware and Hardware

 

The following is required for the E6621A PXT to be supported by the D.01.00 release of the E6567D:
 

E6621A

PXT Wireless Communications Test Set

-

E6621A-503 (default opt.)

Frequency range from 500 MHz to 3 GHz

100

E6621A-506

Frequency range from 500 MHz to 6 GHz

140

 

N6051A

LTE RF parametric test with test mode signaling

-

N6051A-1FP

LTE RF Tx and Rx Measurements  - fixed, perpetual license

20

 

Known Issues

Installation Issues 

Uninstalling older software versions 

If the non-NET versions of Wireless Test Manager are uninstalled after the NET version of Wireless Test Manager is installed, the non-NET Wireless Test Manager selection will remain in the Start Programs Menu. You can safely delete this menu item if you desire.

Uninstalling all software versions 

To completely remove both non-NET versions of Wireless Test Manager and the NET version of Wireless Test Manager, first uninstall all versions of the NET version of Wireless Test Manager (See ReadMe.txt section 1.3) prior to uninstalling the non-NET Wireless Test Manager. 

The USB security key is not recognized after installation 

Situation: You try to run Wireless Test Manager(WTM), but WTM prompts you with the message "No security or incorrect security key found." even though the security key is inserted into a USB port; or when you insert the security key into a USB port, the Windows Found New Hardware Wizard appears and wants you to install a device driver for the security key.
 

Solution: This problem is usually caused when the key was in the USB port during the WTM installation. This interferes with the installation of the Sentinel Security Key files.  Perform the following steps to correct the problem:

 

a.     Cancel or exit from any prompts.

b.     Remove the USB security key from the USB port.

c.     Close all applications that are running.

d.     Check to see that the SentinelKeyW.DLL is installed in the Windows System32 directory.  If the file is not present in the System32 directory, copy the SentinelKeyW.dll from the Sentinel directory on the Wireless Test Manager installation CD to the Windows System32 directory on your PC.  

e.     Run the SentinelSystemDriverInstaller.exe program in the Sentinel directory on the WTM installation CD to reinstall the drivers.

f.      Insert the Security Key into a USB port on your PC.   

g.     The Security Key should be recognized next time you run Wireless Test Manager.   

 

Back-up language files 

Back-up files were created for the language files located in the directories below the ".../WirelessTestManager/Common/" level in case they are written over when installing an older version of the Wireless Test Manager. The release date of this version of the WTM is appended to the name of these language files.

 

??? <reference number> being displayed in the WTM UI 

Situation1: If any E656xA application (VB6 WTM) is installed after an E656xC/N588xA application (.NET WTM) has been installed, the Agilent WTM framework language files (.lng) will be overwritten by the older language files. This will result in ‘??? <reference number>’ showing up on some WTM user interface objects. This is due to old language files not containing the new messages added in .NET WTM.
 

Situation2: If E6560C 1.0 application is installed after any newer E656xC/N588xA application has been installed.
 

Solution: Restore the backup language file for the appropriate UI (Exec & wizard) that was created when the E656xA or E6560C 1.0 application was installed.

 

Example: If the E6562A application is installed after the E6562C then a file called 'English10152004.lng' (where 10152004 is the file date of the E6562C installed language file) will need to be renamed or copied to replace the 'English.lng' in the default installation directory 'C:\Program Files\Agilent\WirelessTestManager\Common\ExecLocalization'. The 'English10152004.lng' file in the default installation directory 'C:\Program Files\Agilent\WirelessTestManager\Common\WizardLocalization' will also need to be renamed or copied to replace the 'English.lng' in that directory.

 

Other Issues

Issues known at shipment release

The localization utility tool (LocalizeUtility.exe) may not work if Visual Studio .Net is not installed.

Issues discovered after release

To find the latest information about component and application release notes, visit the following Agilent Technologies web site http://www.agilent.com/find/E6567D and look for any release note information.

E6621A Issues             

 

·         WTM will only support a GPIB interface on the E6621A.

·         WTM will not support Debug mode with the E6621A.

 

 Component Release Information

 

 The following components will be installed with the Development installation of this release:

 

<Target Directory>\E6567E\RunTime

E6567E_CDMA_LTE_SAM_Net.exe

Agilent.WTM.cmctaMoM.dll

Agilent.WTM.xmctaMoM.dll

 

Revision 1.3.0.0

Revision 2.2.0.0

Revision 2.2.0.0

 

 

<Target Directory>\Common

Agilent.WTM.cmctaMoM.dll

Agilent.WTM.xmctaMoM.dll

TestPlanMover.exe

LocalizeUtility.exe

WTMDataAnalyzer.exe

 

Revision 2.2.0.0

Revision 2.2.0.0

Revision 1.5.0.0

Revision 1.1.0.0

Revision 1.3.0.0

 

 

<Target Directory>\Common\NETWizards

 Agilent.WTM.AddInstrumentControl.dll

 Agilent.WTM.AddWirelessTest.dll

 Agilent.WTM.AddInstrumentControl05.dll

 Agilent.WTM.AddWirelessTest05.dll

 

Revision 1.2.0.0

Revision 1.2.0.0

Revision 1.0.0.0

Revision 1.0.0.0

 

 

<Target Directory>\Common\NetWTMVersion1.X\Assemblies

 Agilent.WTM.Exec.dll

 Agilent.WTM.ag34970MoM.dll

 Agilent.WTM.gpioMoM.dll

 Agilent.WTM.psmtMoM.dll

 Agilent.WTM.MoMMUIServices.dll

 Agilent.WTM.MSJRO.Interop.dll

 Agilent.WTM.PathEffectServices.Interop.dll

 ScDerivedControls.dll

 ScUserControls.dll

 Agilent.WTM.ag14565BMoM.dll

ag14565BSignedInterop.dll

 

 

Revision 1.9.3.0

Revision 1.1.0.0

Revision 1.1.0.0

Revision 1.3.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.0.0

Revision 1.0.1389.23550

Revision 1.0.1389.23557

Revision 1.1.0.0

Revision 1.1.0.0

 

 

<Target Directory>\WINNT\Assembly (Win2k)

<Target Directory>\WINDOWS\Assembly (XP)

 Agilent.WTM.ag34970MoM.dll

 Agilent.WTM.Exec.dll

 Agilent.WTM.gpioMoM.dll

 Agilent.WTM.psmtMoM.dll

 Agilent.WTM.MoMMUIServices.dll

 Agilent.WTM.MSJRO.Interop.dll

 Agilent.WTM.PathEffectServices.Interop.dll

 policy.1.0. Agilent.WTM.ag34970MoM

 policy.1.0. Agilent.WTM.ag34970MoM

 policy.1.0. Agilent.WTM.Exec

 policy.1.0. Agilent.WTM.Exec

 policy.1.1. Agilent.WTM.Exec

 policy.1.2. Agilent.WTM.Exec

 policy.1.3. Agilent.WTM.Exec

 policy.1.4. Agilent.WTM.Exec

 policy.1.5. Agilent.WTM.Exec

 policy.1.6. Agilent.WTM.Exec

 policy.1.7. Agilent.WTM.Exec

 policy.1.8. Agilent.WTM.Exec

 policy.1.9. Agilent.WTM.Exec

 policy.1.9.1 Agilent.WTM.Exec

 policy.1.0. Agilent.WTM.gpioMoM

 policy.1.0. Agilent.WTM.gpioMoM

 policy.1.0. Agilent.WTM.MoMMUIServices

 policy.1.0. Agilent.WTM.PathEffectServices.Interop

 policy.1.0. Agilent.WTM.psmtMoM

 policy.1.0. Agilent.WTM.psmtMoM

 policy.1.1. Agilent.WTM.psmtMoM

              policy.1.2. Agilent.WTM.psmtMoM

 policy.2.6. Agilent.WTM.MSJRO.Interop

 ScDerivedControls.dll

 ScUserControls.dll

Agilent.WTM.ag14565BMoM.dll

ag14565BSignedInterop.dll

 

 

 

Revision 1.1.0.0

Revision 1.8.0.0

Revision 1.1.0.0

Revision 1.3.0.0

Revision 1.0.0.0

Revision 2.6.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.1.0.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.9.3.0

Revision 1.0.0.0

Revision 1.1.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.0.0.0

Revision 1.3.0.0

Revision 1.3.0.0

Revision 1.3.0.0

Revision 2.6.0.0

Revision 1.0.1389.23550

Revision 1.0.1389.23557

Revision 1.1.0.0

Revision 1.1.0.0

 

 

C:\Program Files\Common Files\Agilent Shared\Wireless

 PathEffectSvc.dll

 

Revision 1.1.0.0

 

 

 

 

 

 

 

CONTACT INFORMATION

Service and Support

 

To find information about technical support, equipment service and repair, and training, visit the following Agilent Technologies web site:

 

 For product information:                   http://www.agilent.com/find/E6567D or http://www.agilent.com/find/E6567E

 

 For Agilent contact information:       http://www.agilent.com/find/contactus