1

About This Release

The information in this document describes the TEMS Investigation 6.1 release.

1.1.

PC Hardware and Software Requirements

This section summarizes the requirements on the computer on which TEMS Investigation is to be installed. TEMS Investigation 6.1 is designed to run on a standard PC and interfaces with the connected devices through serial or USB ports. Administrator rights are not needed to run the application (only to install it). Data Collection Requirements Processor and RAM requirements are strongly dependent on what external devices are connected and what tasks they perform. Two examples of recommended configurations are given here. -- One phone with default logs enabled (where applicable) and one GPS: 1.0 GHz Pentium class processor, 256 MB RAM -- Multiple phones with default logs enabled (and at most two phones engaging in data service testing), one scanner, and one GPS: 2.0 GHz Pentium class processor, 512 MB RAM Other hardware requirements: -- USB ports for phones (except Sony Ericsson GSM phones), PCTel SeeGull LX Tri-band scanner, and hardware key. USB ports are not needed if only Route Analysis and network licenses are used. At least one free USB port is needed on the machine hosting the license server. -- Serial ports for Sony Ericsson GSM phones -- Serial port for PCTel SeeGull LX WCDMA scanner -- PC card slot for external FireWire card or built-in FireWire (IEEE 1394) port needed for Rohde & Schwarz scanner -- Sound card and loudspeakers for event audio indications -- Enough disk space to accommodate temporary files created during logfile recording and replay: see section 6.1 under Data Collection. If floating licenses are to be used a machine is also needed to host the license server. Route Analysis Requirements The Route Analysis application will run smoother the more RAM the PC has. General Requirements -- Graphics: 1024 x 768 (SVGA) with at least 16 bit colors (High Color) PC Software Requirements -- Internet Explorer 5.0 or higher required for Report Generator and online help. For the RAN Tuning tool in Route Analysis, one of the following is also needed: -- Microsoft Office XP, Microsoft Office 2000, or Microsoft Office 2003

-- Microsoft Word, Microsoft Excel, and Microsoft Graph (from Office tools) -- MDAC (included on installation CD) or Microsoft Access

1.2.

OS Requirements

The following operating systems are supported: -- Windows XP Professional with Service Pack 2 -- Windows XP Tablet PC Edition with Service Pack 2 -- Windows 2000 with minimum Service Pack 4 Installation under other operating systems is not supported.

1.3.

Phone and Scanner Software Requirements

The following phone and scanner software is recommended for this release: LG U8130: 101_1022/LD_ANDREA_CRH109338_R7E_EC_041002_1036 Motorola E1000: 83.39.01 Motorola A845, 74.07.23 Motorola A835, 72.32.0F Nokia 6230 EU: 05.35/NTM 16.6.0102 Nokia 6230 US: 05.35/NTM 16.8.0102 Nokia 6630: 4.03.18/16.9.0004 Nokia WCDMA 1900: 03.07/16.5.0100 Nokia 6650, software version 05.41/16.3.0101 Nokia 6651, software version 03.07/16.5.0100 Nokia 7600, software version 04.05/16.4.0101 Nokia DKU-2 Cable: Driver version 144.5 (earlier versions of DKU-2 drivers need to be upgraded to this version) Qualcomm TM6250: 6.1.34 Qualcomm TM6250 (US): WZ 4.2.30 Qualcomm TM6200: WZ 5.1.38 Rohde & Schwarz TSMU: V10 SeeGull LX GSM/WCDMA 900/1800/1900: 5.1 (Embedded SW Ver........: 02.05.17.00) SeeGull LX WCDMA 1900/2100: 5.1 (Embedded SW Ver........: 02.05.17.00) Sony Ericsson T610/T616/T618: R1G Sony Ericsson V800: R1S025/LD_VIOLETTA_CRH109338_R7F_EC_ISO Sony Ericsson V802SE: R1G001/LD_VIOLETTA_CRH109338_R7E_EC_ISO Sony Ericsson TEMS V800: CXC 126 620 R2A

Sony Ericsson Z800i: R1Y005, CXC1250046_EU_1_V Sony Ericsson Z1010: R1C Sony Ericsson S710a: TBS The following Qualcomm MSM6200 chipset based UEs have been certified: Samsung Z105; SW 5.1.34 Vodafone Mobile Connect Card, SW:3.1.2d Note: The non-compact format of the Nokia protocol has been removed, so the Nokia 6200 (US) and 6220 (EU) phones are no longer supported, nor are Nokia 6650 and Nokia WCDMA 1900 (6651) with software older than T-15.

2.

Installation

The installation is automatic. Just insert the CD and follow the on-screen instructions. If the installation should not start automatically, double-click the file TEMS Investigation 6.1.exe on the CD. After installation, the TEMS Investigation applications can be started from the Start menu. Click Start and select Programs > TEMS Products > TEMS Investigation 6.0 Data Collection/Route Analysis. All USB drivers for mobiles and equipment cases will be automatically installed in the directory <install dir>\Drivers. With network-based licenses, additional software needs to be installed on the machine hosting the license server. See the separate description for this installation, titled Floating License Installation Instruction.

3.

New Features in TEMS Investigation 6.1

For more information, see the TEMS Investigation 6.1 Product Description.

3.1.

General New Features

-- New user terminals Support for new user terminals: Sony Ericsson TEMS V800, New software for Nokia 6630, Qualcomm TM6250 (US), Sony Ericsson S710a. -- Support for HTU & MTU logfiles from TEMS Automatic 4.1

4.
No changes.

Removed Features

5.

Corrected Bugs

-- Inconsistency between the User Manual and data reported for some throughput information elements -- NACC support flag is not decoded -- Although TIG 5.1.1 documentation says IE RxLev(dBm) has values from -120 to -10, it maxes out on -43dBm for theT610 and -48dBm for the T610 and -48dBm for the Nokia 6230 EU -- Broken logfile generates crash -- Pathloss value doesn't stay visible -- IEs dealing with the Cell Id are empty

-- New Qualcomm USB driver 2.0.20 -- Filemarks are not showing on the map while collecting data with TIG 5.1.2. -- New HASP driver 4.96 -- WCDMA CW Scanning isn't possible to start. FQ out of range -- Increased number FTP session failures -- Missing Call End Event in swapped logfile -- HASP Key Reader info is cut -- Connect issue with V800 as MS2 -- Event "MS out of memory" comes too often -- All GSM neighbors are reported to RxLev-120 using E1000 -- On the scan bar chart, I could not make it show the bars or list ordered by RxLev -- IE Str Sc Aggr Ec from CPICH scanner (UARFCN 10838) shows greater values than RSSI from CW scanner (same UARFCN) -- RAN Tuning Report: Same cells are listed several times, due to that we got a table over 11 pages. -- Fixed speed and lack of GPS positioning after disconnect problems on scanner -- The client will get a message that says un-revocable error. Then the program will close down -- Route legend says all scanned signals are above -29dBm. -- Disconnect of V800 -- MS1 disconnect in TI 6.0 (V802) -- RAN Tuning Report: Not possible to generate a RAN Tuning Report with a larger amount of files. -- When looking at pilot coverage -> coverage class in Route Analysis map window all plots on the map is green. -- If C/I on BCCH carrier is exported and Show changed IE values only is selected, the IE shall only be displayed on the row where the message update the IE. C/I on BCCH is shown on almost every message -- Not possible to run Route Analysis on trial license -- Route Analysis: The user-defined event editor displays "Unexpected token" when using '%' as format. -- Lat/Lon removed in TI 6.0

6.
6.1.
Data Collection

Known Bugs and Limitations

PC Application Related

-- Since new workspaces are supplied, user-created workspaces from previous versions of TEMS Investigation WCDMA or GSM need to be recreated. -- Problems may arise when TEMS Investigation is run on slow computers. The symptoms of these problems are repeated disconnects of connected handsets or long processing times.

-- Windows may have problems resolving all USB driver connections if multiple UEs are connected in a single action, e.g. through a USB hub. This will show in the Device Manager as yellow exclamation marks. Pulling the USB cables from the UEs and then plugging them back in one at a time can solve the problem. -- On some computers, problems with the serial port will cause "Resynch" reports to appear in the Mode Report message window. To resolve these problems, take the following steps: -- Disable the computer's IR port. -- Turn power management off. See the Getting Started Manual, chapter 3. -- (Dell computers only:) From the Start menu, choose: Programs > Dell Open Manage Client > Disable Dell Open Manage Client. -- Reboot. -- Do not install any software that periodically scans the COM/USB ports on computers to which you intend to connect TEMS equipment. The reason is that these programs may cause difficult connect problems in TEMS Investigation. -- Firewalls and other security products may prevent the TEMS Investigation from running two or more data sessions at the same time. -- Some GPS units may be erroneously identified as a "MS Serial Ballpoint" device in Windows 2000. Use the Device Manager to disable the device. Note: Do not remove the device, as it will then be reinstalled at next reboot. -- Virtual IR ports or virtual Bluetooth ports should not be installed on the computer. -- To run a command sequence with voice call commands (such as Dial and End Call) with the Motorola A835/A845 or the Nokia 6650/7600/WCDMA 1900, there is a need to also connect DC1, e.g. the "A835/A845 Data Cable" device, to the modem port. -- When you save a command sequence to a .csq file, an FTP or HTTP server user name and password given in a command are saved with the file (encrypted). Note that another user who runs your command sequence will be accessing the server using the same user name and password. -- "Wait (ALL)" in the command sequence works as follows: When a phone (or whatever equipment is used in the sequence) reaches the Wait (ALL) command, a countdown begins which is specific to that device and independent of any other devices. If another device reaches the Wait (ALL) command at a different time, its countdown will always be at a different stage. Therefore, as long as several devices are waiting simultaneously, flickering of the counter may occur. -- When a blocked call occurs, or when the RF conditions are too bad to make a video call, the command sequence will reach a state where it does not continue. -- The Handset Control tool in Data Collection only works for Sony Ericsson GSM phones (e.g. T610, T68). -- During logfile recording as well as during logfile replay, temporary files are created by the application to enable the user to browse the history of the logfile. These files can become very large (10-15 times the logfile size), the exact size depending on the number of devices connected to the application at recording time. The temporary files are named according to the format temsn and created in the Windows temp directory (default: c\path\tmp, where the path is defined by the environment variable TMP; in both Windows 2000 and Windows XP, the TMP variable can be modified from the Control Panel: System Properties > Advanced > Environment Variables). Make sure there is plenty of space on the disk where the temp directory resides. -- The temporary files are removed when the application is exited; however, if the application terminates abnormally, this might not happen. The files must then be removed manually.

-- Negative frame numbers may occur occasionally during replay of older logfiles. These frame numbers should be regarded as invalid. -- When using the serving cell indication in the Map window to show the strongest scanned CPICH, this works only for the 1st UMTS frequency (the one decoded into the information elements named 1st). -- Interpolation of GPS positions does not work with the PCTel SeeGull LX scanner GPS. -- Using Word as editor in Outlook on machines where TEMS Investigation is installed may completely disable all reading of e-mail. This situation is irreversible; a reinstallation of the operating system may be needed. To make sure that Word is not used as e-mail editor in Outlook, enter the Tools menu, choose Options, and click the Mail Format tab; under Message format, uncheck the option Use Microsoft Word.... Route Analysis -- When loading a number of logfiles into the project (i.e. in the Navigator), the first logfile will automatically load in all presentation windows except the Map window. In the latter, logfiles need to be loaded explicitly. -- Devices in logfiles from previous versions of TEMS Investigation GSM/TEMS Investigation WCDMA may not always be correctly identified. Older Samsung phones, for example, may appear as Unknown CLSID Unsupported. -- If one message causes more than one event to be generated, all presentation windows will show only one of the events. Only in the Navigator, in the tree structure contained within the logfile, do all events appear. -- The legend in the Map window flickers when items are selected/deselected. Whenever a checkbox on the Legend tab is checked or unchecked, the contents of that window pane are redrawn. -- Changing the presentation in a slave map window sometimes adds an offset to the plot in the master window from which the slave was created. (An easy workaround is to close the slave, refresh the master, and open a new slave.) -- The spider cursor does not show at the outset in the Map window, nor does it appear when selecting objects directly on the map. However, when a sample is selected in a different presentation window (e.g. a line chart or a message window), the spider cursor does appear around the corresponding point of the route. -- It is possible to delete columns in the Events window but not to add them again. -- The Events window cannot show both MS and DC events at the same time. -- Care should be taken when comparing (for example) events in the RAN Tuning report with events shown during replay in Data Collection. RAN Tuning calculates statistics only on complete calls and data sessions. Calls and data sessions that are set up before the logfile recording is started, or end after the logfile recording is stopped, are not used for calculating statistics. -- The report generated with the RAN Tuning tool will differ slightly from reports generated with TEMS DeskCat. This is because of a different approach to handling of events. -- Events in the MID/MIF files generated by the RAN Tuning tool may sometimes be associated with

the wrong MS/DC device. For example, a RAS Dial event from DC1 may be given as originating from MS2 in the MID/MIF files (UE Event Plot). -- To avoid long processing times in RAN Tuning tool, the selected cell files/clusters should match as closely as possible the area where the selected logfiles were recorded.

6.2.

Phone Related

Sony Ericsson T610/T616/T618 -- The auto detect function detects these phones as devices without scanning capabilities. If scanning is to be done with these phones, they must be disconnected and then reconnected manually. Sony Ericsson V800/V802SE/Z1010 -- Auto Answer in command sequences does not always work. -- Some invalid (negative) frame numbers may appear in logfile export output. This affects logfiles produced in TEMS Investigation WCDMA 3.x with the Sony Ericsson Z1010. Qualcomm Chipset Based Phones -- An inter-RAT handover can be performed without any handover command from the network. In this case, no event is generated, and pre-handover IE values are not cleared in presentation windows. For example, WCDMA IEs in the Line Chart WCDMA window do not become invalid after handover to GSM, but freeze at their final values (flat lines drawn in chart). -- The hardware information and the number of UEs used is sometimes missing in the logfile information (accessed by clicking the Information [i] button on the Replay toolbar). -- AT commands in command sequences are not always executed. -- If video calls are iterated, there must be a Wait of about 5 seconds after the End Call command. This is needed for the camera to initialize and for the phone to enter the correct state for the next video call. -- In Route Analysis, Samsung phones are detected as Qualcomm TM6200 phones. -- Video call initialization in the Samsung SGH-Z105 may require special configuration of the phone menus by means of an INI file (msswcdma.ini) which must be placed directly under c:\. The precise settings needed in the INI file are operator-dependent; here is an example: [Samsung_Video] Samsung_Video_Menu = 1 ; use shortcut 1 to find video telephony menu Samsung_Video_Menu_Jumps = 3 ; make 3*2 jumps backwards to find Camera/Video Recorder item -- Answer Call in command sequences is not supported for Vodafone MCC. Nokia 6230/6650/7600/WCDMA 1900

-- The Network Monitor needs to be disabled when running TEMS Investigation. -- The Nokia 6650, Nokia 7600 and Nokia WCDMA 1900 UE can only handle a combination of two simultaneous logs from the set {cell (intra-frequency), cell (inter-frequency), Tx Power}. By default, cell (intra-frequency) and Tx Power are chosen. To be able to log intra-frequency and interfrequency neighbors instead of Tx Power and intra-frequency neighbors, do as follows: Move the file Nokia.ini (located in <install dir>\Drivers\6650\) to c:\ and reconnect the device. You can restore the default behavior by removing Nokia.ini again and performing another disconnect + connect. -- The SAN list reported by Nokia 6650/7600/WCDMA 1900 is sorted by the phone in Ec/No order. This means that it is possible for a neighbor cell to be the first element from time to time. This behavior also affects the coloring in the Line Chart WCDMA, so it looks as if a cell reselection has occurred. -- It is not possible to have multiple Nokia 6650/7600/WCDMA 1900 dial-up connections on the same computer. -- BLER is averaged over all transport channels, not reported for each transport channel separately. -- It is not possible to lock on band or channel with the Nokia 6650/WCDMA 1900/Nokia 7600. -- AMR must be turned on in the Nokia 6230 as it is not activated by default. -- When the Nokia 6230 is locked on a channel, it reports no neighbors. -- When the Nokia 6230 is used on the 1900 band, neighbors are not selectable with the lock on channel function. The problem can be circumvented by manually selecting the desired channels. -- Auto answer does not work with the Nokia 6230. -- When locking a Nokia phone on a GSM control channel (e.g. RAT state = GSM and lock on frequency band), the phone stays only for a short while on the ARFCN it has locked on, and then moves on to a different channel. -- See also the document TEMS Investigation GSM - Nokia 6230 Release Notes. Motorola A835/A845/E1000 -- The Motorola A845 may sometimes send invalid data to the PC, causing the PC application to freeze. -- If Enhanced Field Engineering Mode (EFEM) has been turned on, the way to turn it off is to push the middle menu button and then the left menu button, and set Availability of EFEM Screens to Off. -- EFEM needs to be disabled when running TEMS Investigation. LG U8130 -- Auto Answer and Answer Call do not work properly. When answering fails (the phone does not respond to the AT command "ATA"), TEMS Investigation freezes for 10 seconds. -- The APN must be set before a data session is started, since the settings are lost at the end of each session.

-- When several voice or data calls are performed in a row, a Wait (10 seconds) must be inserted after each Hangup or End Call command. This is because the phone always tries to do PS Attach at the end of a voice or data call, and during this period the phone is too busy to do anything else.

6.3.
Rohde & Schwarz TSMU

Scanner Related

-- Configuration settings specific to the TSMU (i.e. those that have no counterpart for PCTel scanners) are not saved in the workspace. See the Data Collection Users Manual, sections 8.4.3 and 8.7.3. -- The procedure for upgrading the scanner software is described in the document Rohde & Schwarz TSMU SW upgrade instruction which is delivered with the scanner and available on the TEMS TSMU CD accompanying the scanner. -- The procedure for upgrading the scanner firmware is described on this web page: www.ericsson.com/services/tems/support/investigation/ sup_ti_wcdma_swhw.shtml -- To determine the firmware version, a crossed serial cable (DTE-DTE) is needed in order to extract a text dump from the scanner. The information found there is also essential when contacting TEMS Support. The procedure is described in the Getting Started Manual. -- If the scanner loses power while connected to TEMS Investigation, the application needs to be restarted. The reason is that the API does not handle this type of error. PCTel SeeGull LX -- If you do not disconnect the scanner properly from within TEMS Investigation, problems may arise when you try to connect it again. For example, if you remove the cable from the serial port without first disconnecting the scanner in the application, measurements will continue to run in the scanner, and when it is connected to the port again the connect might fail. There are two ways to solve the problem: either connect the scanner manually in TEMS Investigation, or turn the scanner off and on to make the connect function work again. -- In the event of an error report from the hardware during a measurement, all further measurements are suspended until the power to the scanner is manually recycled. There is no recovery from errors reported by hardware. -- In the CW scan, a -65 dBc spurious response exists +1.4 MHz from the un-modulated input signal. -- The Spectrum Analyzer can sometimes return spurious responses (-62 dBc) when a very strong input tone is present. -- When CPICH scanning multiple frequencies, the sample rate per frequency will be decreased compared to the single-frequency measurement. When scanning 4 frequencies, the sample rate is decreased to only one measurement per frequency over a two-second period, which means that it no longer makes any sense to choose the "Sub" data mode, It is then better to choose the "Full" data mode and also get the synchronization channel measurements.

6.4.

GPS Related

-- Garmin Street Pilot 2650 will put out invalid positions on its interface during dead reckoning although positions are presented on the display of the GPS. These invalid positions will cause the PC application to correctly interpolate the positions during the time when no valid position data is available from the GPS. -- The events GPS Connected and GPS Disconnected are intended for drive testing and are generated only during recording. They do not appear during replay and post-processing. -- The positioning capabilities of the USB GPS (KRE 105 074) may not be adequate for all needs. See further "Product Specification USB GPS Receiver" (USB_specification100502.doc) available on the GPS CD.

7.

Contact Information

For customer support contact information, please visit our website on the Internet: www.ericsson.com/tems.