Manual - NetQual - Test Manager

WHEN QUALITY MATTERS

NetQual TestManager Manual

March 2011

SwissQual® License AG Allmendweg 8 CH-4528 Zuchwil Switzerland

t +41 32 686 65 65 f +41 32 686 65 66 e [email protected] www.swissqual.com

Part Number: 15-070-200612 REV 10.6

SwissQual has made every effort to ensure that eventual instructions contained in the document are adequate and free of errors and omissions. SwissQual will, if necessary, explain issues which may not be covered by the documents. SwissQual’s liability for any errors in the documents is limited to the correction of errors and the aforementioned advisory services.

Copyright 2000 - 2011 SwissQual AG. All rights reserved.

No part of this publication may be copied, distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language without the prior written permission of SwissQual AG.

Confidential materials.

All information in this document is regarded as commercial valuable, protected and privileged intellectual property, and is provided under the terms of existing Non-Disclosure Agreements or as commercial-in-confidence material.

When you refer to a SwissQual technology or product, you must acknowledge the respective text or logo trademark somewhere in your text.

SwissQual®, Seven.Five®, SQuad®, QualiPoc®, NetQual®, VQuad®, Diversity® as well as the following logos are registered trademarks of SwissQual AG.

Diversity Explorer™, Diversity Ranger™, Diversity Unattended™, NiNA+™, NiNA™, NQAgent™, NQComm™, NQDI™, NQTM™, NQView™, NQWeb™, QPControl™, QPView™, QualiPoc Freerider™, QualiPoc iQ™, QualiPoc Mobile™, QualiPoc Static™, QualiWatch-M™, QualiWatch-S™, SystemInspector™, TestManager™, VMon™, VQuad-HD™ are trademarks of SwissQual AG.

SwissQual acknowledges the following trademarks for company names and products:

Adobe®, Adobe Acrobat®, and Adobe Postscript® are trademarks of Adobe Systems Incorporated.

Apple is a trademark of Apple Computer, Inc.

DIMENSION®, LATITUDE®, and OPTIPLEX® are registered trademarks of Dell Inc.

ELEKTROBIT® is a registered trademark of Elektrobit Group Plc.

Google® is a registered trademark of Google Inc.

Intel®, Intel Itanium®, Intel Pentium®, and Intel Xeon™ are trademarks or registered trademarks of Intel Corporation.

INTERNET EXPLORER®, SMARTPHONE®, TABLET® are registered trademarks of Microsoft Corporation.

Java™ is a U.S. trademark of Sun Microsystems, Inc.

Linux® is a registered trademark of Linus Torvalds.

Microsoft®, Microsoft Windows®, Microsoft Windows NT®, and Windows Vista® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries U.S.

NOKIA® is a registered trademark of Nokia Corporation.

Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.

SAMSUNG® is a registered trademark of Samsung Corporation.

SIERRA WIRELESS® is a registered trademark of Sierra Wireless, Inc.

TRIMBLE® is a registered trademark of Trimble Navigation Limited.

U-BLOX® is a registered trademark of u-blox Holding AG.

UNIX® is a registered trademark of The Open Group.


© 2000 - 2011 SwissQual AG

Contents | CONFIDENTIAL MATERIALS

ii

Contents 1 Introduction .......................................................................................................................................... 1

System Overview ................................................................................................................................... 1

Network Overview .................................................................................................................................. 2

Campaigns, Tasks, Jobs, Tests ............................................................................................................ 3

2 Starting TestManager .......................................................................................................................... 4

Prerequisite Software ............................................................................................................................ 4

Before You Start .................................................................................................................................... 4

User Accounts ....................................................................................................................................... 4

Connecting to a Database ..................................................................................................................... 4

3 TestManager Overview ....................................................................................................................... 5

Navigation Pane .................................................................................................................................... 5

Workspace View .................................................................................................................................... 5

4 Single Unit Overview ........................................................................................................................... 6

5 Network Configuration ........................................................................................................................ 7

Operators ............................................................................................................................................... 7 Providers ................................................................................................................................................ 7

Subscribers ............................................................................................................................................ 7

Access Points ........................................................................................................................................ 8

Servers .................................................................................................................................................. 9

Logins .................................................................................................................................................... 9

6 System Configuration – Units and Devices .................................................................................... 10

Connection Profiles.............................................................................................................................. 10

Time Sync Profiles ............................................................................................................................... 10

General System Settings Tab ........................................................................................................ 10

GPS Settings Tab ........................................................................................................................... 11

NTP Settings Tab ........................................................................................................................... 11

QualiPoc SMS Profiles ........................................................................................................................ 12 QualiPoc Unit Profiles .......................................................................................................................... 13

Diversity Upload Profiles ..................................................................................................................... 14

Diversity Unit Profiles........................................................................................................................... 14

General Tab.................................................................................................................................... 14

Diversity Explorer Tab .................................................................................................................... 15 Unit Software Updates ......................................................................................................................... 15

Adding Updates .............................................................................................................................. 15

Executing Updates ......................................................................................................................... 15




iii

Unit Groups .......................................................................................................................................... 15

General Tab.................................................................................................................................... 16 Group Specific Tabs ....................................................................................................................... 16

Diversity Benchmarker Settings ..................................................................................................... 17

Remote Control Tab ....................................................................................................................... 17

Units ..................................................................................................................................................... 17

General Tab.................................................................................................................................... 17

Connection Tab .............................................................................................................................. 18 Diversity Tab................................................................................................................................... 19

QualiPoc Tab .................................................................................................................................. 19

Actions Tab..................................................................................................................................... 19

Special Config Tab ......................................................................................................................... 21

Devices ................................................................................................................................................ 21 General Tab.................................................................................................................................... 21

Remoting Tab ................................................................................................................................. 22

Subscribers Tab ............................................................................................................................. 22

ISDN Device ........................................................................................................................................ 22

General Tab.................................................................................................................................... 22

ISDN Settings Tab .......................................................................................................................... 22 PSTN Device ....................................................................................................................................... 24

PSTN Settings Tab ......................................................................................................................... 24

Mobile Device ...................................................................................................................................... 24

Mobile Settings Tab ........................................................................................................................ 24

Datacard Device .................................................................................................................................. 24

Datacard Settings Tab .................................................................................................................... 24 Dial-Up Device ..................................................................................................................................... 25

Network Adapter Device ...................................................................................................................... 25

Scanner Device ................................................................................................................................... 25

Scanner Tab ................................................................................................................................... 25

Configuration Tab ........................................................................................................................... 25 GPS Device ......................................................................................................................................... 27

Serial Port Tab ............................................................................................................................... 27

QualiPoc Device .................................................................................................................................. 27

Mobile Settings Tab ........................................................................................................................ 27

Device Overview Page ........................................................................................................................ 28

Trace Masks List Page ........................................................................................................................ 28

7 Job and Test Configuration .............................................................................................................. 29

Timings Tab ......................................................................................................................................... 29

Data, Video Over IP ....................................................................................................................... 29




iv

Intrusive Job Type ............................................................................................................................... 30

Timings Tab .................................................................................................................................... 31 Intrusive Tests Tab ......................................................................................................................... 33

Non-Intrusive Job Type ....................................................................................................................... 35

General Tab.................................................................................................................................... 35

Timings Tab .................................................................................................................................... 35

Non-Intrusive Tests Tab ................................................................................................................. 36

Call to Any Number Job Type .............................................................................................................. 36 General Tab.................................................................................................................................... 36

Timings Tab .................................................................................................................................... 36

Call to Any Number Tests Tab ....................................................................................................... 37

Access Test Job Type ......................................................................................................................... 37

General Tab.................................................................................................................................... 37 Timings Tab .................................................................................................................................... 37

Access Test Tests Tab ................................................................................................................... 37

Data Job Type ..................................................................................................................................... 38

General Tab.................................................................................................................................... 38

Timings Tab .................................................................................................................................... 39

Data Tests Tab ............................................................................................................................... 39 Ping ................................................................................................................................................ 40

Ping Trace ...................................................................................................................................... 40

FTP ................................................................................................................................................. 40

HTTP Browser ................................................................................................................................ 41

HTTP Transfer ................................................................................................................................ 42

UDP Downlink ................................................................................................................................ 43 UDP Plus ........................................................................................................................................ 43

Email Send ..................................................................................................................................... 44

Email Receive ................................................................................................................................ 45

GPRS Attach + Detach .................................................................................................................. 45

PDP Activation and Deactivation ................................................................................................... 46 SMS Send ...................................................................................................................................... 46

SMS Receive .................................................................................................................................. 46

SMS Push....................................................................................................................................... 46

MMS Send ...................................................................................................................................... 47

MMS Receive ................................................................................................................................. 47

WAP ............................................................................................................................................... 47 Video over IP Job ................................................................................................................................ 48

Forcing Job .......................................................................................................................................... 48

Tests ............................................................................................................................................... 48




v

Upload Job ........................................................................................................................................... 48

8 Campaign and Task Configuration .................................................................................................. 49

Campaign ............................................................................................................................................ 49

Task ..................................................................................................................................................... 49

Jobs Tab ......................................................................................................................................... 54

Advanced Tab ................................................................................................................................ 54

Task List .............................................................................................................................................. 55

Triggers ................................................................................................................................................ 55 Time Trigger (Schedule) ................................................................................................................. 55

Once ............................................................................................................................................... 55

Daily ................................................................................................................................................ 56

Weekly ............................................................................................................................................ 56

Delayed .......................................................................................................................................... 56 Speed Trigger ................................................................................................................................. 56

Forcings ............................................................................................................................................... 57

Static Forcing.................................................................................................................................. 57

Bands Tab ...................................................................................................................................... 57

ARFCN Tab .................................................................................................................................... 57

UARFCN Tab ................................................................................................................................. 58 Applications ......................................................................................................................................... 58

Data Recording Profiles ....................................................................................................................... 58

General Tab.................................................................................................................................... 58

Application Tab ............................................................................................................................... 58

Device Tab ..................................................................................................................................... 59

Scanner Tab ................................................................................................................................... 59 Level Tab ........................................................................................................................................ 59

Device Groups ..................................................................................................................................... 60

Device Overview .................................................................................................................................. 60

9 Database Administration .................................................................................................................. 61

Connect to Database Server ............................................................................................................... 61 Create a New Database ...................................................................................................................... 61

Restore an Existing Database ............................................................................................................. 61

Update, Delete or Backup a Database ................................................................................................ 61

Note for Database Backup ............................................................................................................. 61

10 Special Views ..................................................................................................................................... 63

Drive Test View .................................................................................................................................... 63 System Status View ............................................................................................................................. 63

11 TestManager Settings ....................................................................................................................... 64




vi

GeneralSettings.xml File ..................................................................................................................... 64

UserSettings_<username>.xml ........................................................................................................... 64 Single User Mode ........................................................................................................................... 64

Multi-User Mode ............................................................................................................................. 65

[dboTM].Settings Table ....................................................................................................................... 65

12 Troubleshooting ................................................................................................................................ 66

General ................................................................................................................................................ 66

Log Files and Backups of the Database ........................................................................................ 66 At Startup ............................................................................................................................................. 66

License ........................................................................................................................................... 66

Possible Error Messages ............................................................................................................... 66

During Configuration of the System ..................................................................................................... 67

PCM Beeps and Then Shuts Down ............................................................................................... 67

Figures Figure 1-1 Overview of Diversity system components ...................................................................................... 1

Figure 1-2 Diversity system hardware ............................................................................................................... 2

Figure 6-1 WCDMA Example 1: Center Frequency in Band #2 ...................................................................... 26

Figure 6-2 WCMDA Example 2: Center Frequency in Band #1 ...................................................................... 26

Figure 7-1 Record Hangover ........................................................................................................................... 30

Figure 7-2 Task and Call durations ................................................................................................................. 33 Figure 7-3 Max Call Setup Time and Alerting Timeout effect on call setup behavior ..................................... 33

Figure 8-1 Jobs arranged sequentially ............................................................................................................ 52

Figure 8-2 Overlapping Multi-RAB jobs ........................................................................................................... 53

Figure 8-3 Two data windows in parallel with the same speech window ........................................................ 53

Figure 8-4 Same as Figure 8-3 except that second job has two consecutive windows .................................. 53

Figure 8-5 Stream PC NoRef (QT) job with two overlapping Nina+ windows ................................................. 54 Figure 8-6 Windows for forcing jobs ................................................................................................................ 54



Chapter 1 | Introduction CONFIDENTIAL MATERIALS

1

1 Introduction The NetQual TestManager Manual consists of a practical hands-on section and a section that provides a detailed description of the system components.

NetQual TestManager manages tests for voice, data, and video quality measurements within telecommunication networks.

After you install TestManager, you need to perform the following tasks:

• Connect to a database

• Configure the network settings

• Configure the hardware settings, for example, units and devices

• Add triggers, forcings, applications, and data recording profiles as needed

• Configure jobs with tests

• Assign the jobs to tasks with devices and other setting profiles that you have also configured in TestManager

• Start the tasks

System Overview

Figure 1-1 Overview of Diversity system components

A Diversity system contains the following components:

• TestManager (TM): Software that creates and manages Diversity and QualiPoc tests.

• TestManager database: Software that stores the configuration settings from the TM.

• NQComm: Software that allows communication between TM and a measurement unit. NQComm loads the data from the database, converts the data into the appropriate file format and then sends the files to the unit for further processing.

• NQView: Software that displays live and replay measurement data from measurement devices.

TestManager

DB

NQComm

TestManager

Web-Browser

Measurement unit

(A-side)

Measurement unit

B-side

NQView Optimizer




2

• NQView Optimizer: Software to manage simplified measurements.

• Control Base Module (CBM): Hardware that supplies the Diversity Benchmark system with power and controls the system LAN. The CBM is always at the left end of the system.

• Measurement Unit: Hardware that controls the devices that run the test scenarios. Receives instructions and configuration files from TM.

• Device: Hardware attached to a unit to perform certain tests, for example, a mobile phone to perform speech tests. Some devices, such as ISDN, PSTN and scanner devices occupy a PCM slot in the Diversity system and are assigned to the PCM on the left.

Note: In a Diversity system, you cannot operate a device without a unit, which is also valid for all unit types. A device specifies the connectivity variant of the unit, , for example, the mobile device, the datacard, the GPS, the network adapter, the wireless network adapter, and so on.

Figure 1-2 Diversity system hardware

Network Overview In TM, you need to provide information about the following aspects of the mobile network where you will run your Quality of Service (QoS) tests:

• Operator: Maintains the software and hardware on the network. Each operator has a unique MCC/MNC on GSM and UMTS networks, or SID/NID on CDMA networks

• Provider: Offers services such as WAP, GPRS, and so on. The provider might also be responsible for customer relations and accounting. In some networks, the provider and the operator can be the

Unit: PCM

Device: MCM

Device: ISDN Board

System CBM




3

same company.

• Subscriber: Owns a mobile phone and uses the services/access points that are offered by the provider on the network. In GSM networks, subscribers are identified by their SIM cards. For PSTN/ISDN devices, Diversity uses the board and channel numbers for identification. In TestManager, you must assign a mobile phone or datacard device to a subscriber. Based on this information, TestManager implicitly knows which operator, provider, or access points information is associated with the device.

• Access Point: Provides access to services, such as GPRS, MMS, and SMS, that are offered by the provider. WLAN access points are handled as well, independent of providers.

Campaigns, Tasks, Jobs, Tests A campaign is a collection of tasks that allows you to start the tasks simultaneously. You can not assign a task to more than one campaign.

A task is a collection of jobs that are, depending on the job type, assigned to one or two devices. For additional functionality, you can also use triggers (scheduling, speed), filter, and network forcing.

A job is an ordered collection of tests for the same type of application, such as voice quality tests and data tests. A job also contains job options, which are the timings and the settings that apply to the tests in the job. You can only run a job on one unit type. When you define a task, you can only combine corresponding units and jobs.

A test contains the actual test that is performed on the network. Each test can have different test types. For example, an intrusive job can contain the following test types:

• Speech

• Speech Wideband

• Advanced Echo Check (AEC)

• Round Trip Time

• Noise suppression

• DTMF



Chapter 2 | Starting TestManager CONFIDENTIAL MATERIALS

4

2 Starting TestManager This chapter describes how to configure TestManager to work with a database. The first time that you start TestManager, you need to connect to an existing database or to create a new database.

Prerequisite Software

• MS-SQL server with access rights set so that TestManager can create and delete a database as well as insert, update, and delete table entries. TestManager stores the Diversity dependent settings in a database on this server.

• NQComm that has access to the same MS-SQL server as TestManager.

Before You Start

• (Benchmarking Systems Only) Turn on the units and wait until the status of the units changes to Ready.

• Start NQComm on the control PC and click the Start/Stop Remote Scan icon .

User Accounts

• TM can be used in single-user mode with automatic login or in multi-user mode with required login per user. The TM login is not the same as the login for the database server that is necessary for TM use.

• User credentials must be set by the TM administrator on the server where the TM service is running.

• Each user has its own settings for initial view, list settings etc. that are stored in his settings file.

Connecting to a Database For a detailed description on how to create and manage a database, see “Database Administration” on page 61.



Chapter 3 | TestManager Overview CONFIDENTIAL MATERIALS

5

3 TestManager Overview After you connect to the database, the TestManager window opens. At this point, you need to start NQComm, connect to the same database and start the remote scan.

For more information, see the Installation - Diversity Platform and Applications.pdf manual.

• To quit TestManager, click Exit at the top right of the workspace.

Note: The view has an automatic refresh. If needed, the timeout can be configured individually per installation.

Navigation Pane The Navigation pane on the left side of the window contains the main commands for TestManager.

• To view the options for a command, click the command in the Navigation pane.

• To return to the Overview page, click Overview on the TestManager title bar.

Workspace View The workspace occupies the main part of the TestManager window. The name of the current workspace is shown at the top left of the title bar. The Status bar at the bottom of the window shows the login status of the database.

• To reload the data, click Refresh at the top right of the workspace.

• To change back to the Overview workspace, click Overview on the title bar.

The application (App) and the database (DB) version information are shown at the bottom of the Navigation pane. The Status bar shows the connection status of the database.



Chapter 4 | Single Unit Overview CONFIDENTIAL MATERIALS

6

4 Single Unit Overview This special overview can be used to obtain information on a per-unit/per-device-level. The unit grouping is displayed as tree view, and a click to an item in the tree loads the corresponding data in the details section of the view.

• The groups are defined in the “System Configuration – Units and Devices” (see page 10).

• A unit can be assigned to a group. If not, it will show up in a dynamic group called “Unassigned units”. This special group will only show up if there are any unassigned units at all.

• All parent items inherit the worst status of their sub-items. The state is shown as coloured bullet per item in the tree view. If unsure what the colour means, move the mouse over the text of the tree item - a hint will show.

• Only enabled units/devices are shown, but all of them (the system overview doesn't show scanners and GPS receivers). Like this, an overview regarding the whole system configuration can be achieved.

• Units can 'timeout' which means if they did not get in contact within a certain period of time, their status changes to 'Timeout1' first and 'Timeout2' later. The default values are 30 minutes for level 1 and 10 hours for level 2. These timeout levels can be adjusted in the corresponding unit profiles.




Chapter 5 | Network Configuration CONFIDENTIAL MATERIALS

7

5 Network Configuration To specify the settings for your network, click Network configuration in the Navigation pane. Before you can configure your hardware for tests, you need to create a representation of your network in TM.

Tip: To use the same configuration for multiple systems, configure your network settings in TM, export the settings as a configuration file, and then import the settings on the remaining systems.

Operators

Setting Description

Operator Name of the operator

Display name Name that is shown on the mobile phone display.

Technology Choose the supported network technologies.

MCC Mobile Country Code

MNC Mobile Network Code

SID System ID

NID Network ID

NCC Assigned Network Color Code from BSIC (GSM). Allowed are single values (1) or ranges (1-3), both separated with ‘;’.

GSM channels UMTS channels LTE channels

Allowed are single values (1) or ranges (1-3), both separated with ‘;’.

Important: It is necessary to enter assigned values for NCC, GSM/UMTS/LTE channels to obtain top channel measurement data when using a scanner device. For scanner configuration details, see "Scanner Device" on page 25.

Providers

A provider supplies the services that are available on the network. Although you can use the same name for a provider and an operator, the provider can not offer the same services to the same operator. You define the services that a provider supplies when you add specific access points, for example, MMS, SMS, and WAP. You need to add at least one provider for each operator that you add.

Setting Description

Provider Name of the provider

Assigned operator Operator that you assign the provider to.

Access Points Defined access points for the provider (this is for information purposes only)

Subscribers A subscriber is the end-user side of the network. For example, in GSM Networks, the subscriber is the SIM card. You assign a subscriber to a mobile phone device when you configure the hardware settings for the device in TestManager.




8

Setting Description

Subscriber This name is displayed in other parts of the application, such as the mobile phone device.

Assigned provider Provider to which the subscriber is assigned.

Subscriber identity For the “Mobile” type, the subscriber identity is the IMSI.

Access Points An access point defines the services that are offered by the provider. For each service, you need to add one access point to the provider.

Note: The Circuit Switch (CS) is not currently used.

Setting Description

Access point Display name

Assigned provider Provider that the access point is assigned to (except for WLAN access points)

Type Select one of the following access point types: • GPRS • WAP • MMS • CS • SMSC • CDMA • WLAN (provider optional)

Note: WLAN access points usually do not belong to a provider and are therefore not visible in the tree view. They only show up in the list of access points.

APN Access point name of the network

Phone number By default, the phone number for GPRS is *99# . This number is used to initialize the internal phone modem. For CS and SMSC, this value is used as the actual phone number to reach the service.

Username Username to access the service If login information is not required, leave this box empty.

Password Password to access the service If login information is not required, leave this box empty.

AT command string If this box has not yet been filled in and the APN is entered, this field is automatically filled in automatically with the AT command string. This string is used on the phone to connect to the access point.

Network A special tab page is rendered for all network settings. This page is only visible if the type of access point can have such settings.

WLAN A special tab page is rendered for all WLAN settings. This page is only visible if the type of access point is WLAN.




9

Servers A server defines a part of the network that is widely used in TM, for example, connection profiles as part of the unit setup use it as well as the application profiles as part of the task setup. Servers in the TM way of use are network-connected computer appliances that provide specific services for other clients on the network, for example, file servers, web servers, IMS servers etc..

Setting Description

Server name Display name

Protocol Protocol used by the server. Per protocol a server entry must be defined.

Note: The protocol also defines the default port that is used for that server.

Host Hostname or IP address of the server (host [:port] is allowed).

Passive mode Only applies for the FTP protocol type.

Authentication The server accepts either login based authentication (by far the most used case) and/or access device authentication.

Note: The login data is separated from the server because many users have the same login data for several servers. See "Logins".

Login trials Defines how many times a login should be tried.

Login timeout Defines a timeout criteria for the login process.

Logins A login defines the credential with which one can connect to a server. As credentials are often the same for different servers/services, the logins can be defined separately.

Setting Description

Login name Display name

User name Name used for logging in.

Password The password is shown in plain text. Login information in TM must be accessible for all users. These are not private (and therefore secret) credentials.

Identification This value can be left blank or used as needed. For certain uses, the identification differs from the user name, for example, when the identification is a phone number for IMS services.

Remote directory Used for connections to file servers, for example, FTP, where a directory change has to be done after the login.



Chapter 6 | System Configuration – Units and Devices CONFIDENTIAL MATERIALS

10

6 System Configuration – Units and Devices To establish a connection between the TestManager and a unit, you need to add the unit, and then configure the connection settings. The actual connection is established by NQComm.

• To configure the Diversity hardware, click System configuration in the Navigation pane.

On the System Configuration page, you can configure the Diversity hardware that is in use. The tooltip (hint) shows you a short description of the kind of hardware that you can configure.

You can modify the settings for a selected unit or device in the Details box on each page.

In order to be able to configure a unit, profiles are used. These store information about connections, time synchronization, SMS settings, GPS setting etc.. If you want to group your units, for example, for the Single unit overview or the System Inspector, the you have to add unit groups as well.

Important: Ensure that you define the required profiles and groups before you add a unit. Each profile is not necessarily used in every case and grouping is optional, except for Benchmarker systems. You also need to disable all non-functional devices in the system configuration, for example, a device that does not have a SIM card. Otherwise the Diversity software tries to initialize and reboot the device on a regular basis, which can have a significant impact on the measurement performance of the PC or PCM.

Connection Profiles These profiles store all necessary information about possible connection types. The possible values are obvious and not explained further except these two:

• Diversity FTP (System default profile): By default, the value for host is the computer name. This profile is the default FTP connection for Diversity benchmarking systems.

• No Connection/DTMF (System default profile): Choose this option if your system does not have access to an IP enabled network. Instead, the Diversity Voice Servers are controlled with DTMF tones that are sent to an ISDN or PSTN device, which are normally used as B-side devices to perform intrusive tests.

Time Sync Profiles Each unit must synchronize to a time source in order to deliver accurate timestamps. Time sync profiles define the synchronization sources.

Important: The PCM in slot 0, that is, the PCM that is directly attached to the CBM, uses the time synchronization that you define in the profile. The remaining PCMs in the system synchronize time with the PCM in slot 0.

General System Settings Tab

Setting Description

Sync to external source Synchronizes time with an external source. If you do not select this option, the unit uses the internal clock.

Important: If you do not select this option, the remaining settings are ignored. If you select this option, you need to select at least one source.

Port Internal port for Diversity software.

Protocol At the moment, only UDP is supported.




11

Setting Description

Time sync difference If out of sync by more than this threshold, the unit is no longer time synchronized.

Broadcast interval Interval in which the time is broadcasted to the other attached units (in case of a multi unit system).

GPS Settings Tab Important: GPS time synchronization is only possible if the active GPS device is connected to the first PCM. Passive GPS controllers only receive position information from the active GPS and cannot provide time information. Passive controllers also have a latency problem since the controllers receive information from another PCM.

Setting Description

GPS sync enabled Enables GPS time synchronization

GPS sync name The name for the GPS configuration file that is used by the Diversity software. This name also appears in the Diversity log files.

Sync priority Priority of the GPS time provider in relation to other time providers, currently just the NTP server. The smaller the number is, the higher the priority.

GPS leap correction enabled

Applies GPS leap correction.

GPS leap correction For an explanation of why this setting is necessary, go to: http://tf.nist.gov/general/leaps.htm

NTP Settings Tab

Setting Description

NTP sync enabled Enables NTP time synchronization

NTP sync name The name for the NTP configuration file that is used by the Diversity software. This name also appears in the Diversity log files.

Sync priority Priority of the NTP time provider in relation to other time providers, currently just GPS. The smaller the number is, the higher the priority.

NTP server 0-2 NTP server addresses For a list of all public NTP servers, go to: http://www.pool.ntp.org/

Note: In QualiPoc Freerider mode, you only need NTP server 0, that is, NTP servers 1-2 are not used.

http://tf.nist.gov/general/leaps.htm

http://www.pool.ntp.org/




12

QualiPoc SMS Profiles These profiles are only used for QualiPoc units.

Setting Description

Serving cell info interval

Interval in minutes between serving cell information SMS, which requires the Via SMS option.

Note: SMSs are not sent during a measurement.

If you set the interval value to 0, the serving cell information is uploaded to the FTP server by each status communication or file upload; however, if the Via SMS option is enabled, an SMS is not sent.

GPS position info interval

Interval in minutes between position messages, which requires the Via SMS option.

Note: SMSs are not sent during a measurement.

If you set the interval value to 0, the GPS information is uploaded to the FTP server by each status communication or file upload; however, if the Via SMS option is enabled, an SMS is not sent.

Send unit alerts Unit sends the following alarms as SMS messages: • Low RAM or Flash memory condition • Failed data connections (for example, GPRS) • Reboots • QPControl start and exit • Job failures and drops

To use the Send unit alerts option, your also need to enable the Via SMS option. The alarms are not sent during a status communication or file upload.

Note: The alarms are always sent by SMS even if you enable the Via FTP option.

Send network alerts When checked, network coverage alarms are created based on the next two criteria (see below). By the next possibility these alarms are uploaded to the FTP server. This requires an enabled “Via FTP” option.

Note: These alarms are not sent by SMS even if the Via SMS option is enabled.

Low RF coverage threshold

• The alert will be raised if the RxLev / RSSI value is below the threshold for the defined duration.

• The alert will be cleared if the RxLev / RSSI value is above or equal the threshold for the defined duration.

Low RF coverage duration

Send result summaries

When checked, the unit will send a summary of the test result after each test. This requires an enabled “Via FTP” and / or “Via SMS” option. In case both options are enabled “Via FTP” is used as default and “Via SMS” as backup.

Via SMS This option enables the sending of the information SMS (serving cell and GPS position), the unit alerts and the result summaries via SMS

SMSC number • Number of the short message center.




13

Setting Description

SMSC keyword • The SMS gateway uses the keyword to forward the content of the SMS to the corresponding FTP/HTTP server. Although the keyword is not mandatory in all cases, you still need to enter the keyword to ensure the proper SMS message format.

Important: The keyword must not contain a space.

Via FTP This option enables the sending of the network alerts and the result summaries via FTP.

QualiPoc Unit Profiles QualiPoc unit profiles define common unit properties.

Setting Description

Operation mode Select the unit’s operation mode. The following table explains the details of each mode:

Mode Log display in front

Hardware watchdog

Backlight Local configuration

Monitoring yes no no yes

Static yes yes yes yes

Mobile yes yes no yes

Friendly user

no no no no

Freerider yes yes no yes

Poll interval Number of minutes between polls of the FTP server If set to 0, the unit will never poll and depend on SMS notifications entirely.

Poll delay Number of minutes to delay the first polling after starting the QPControl application.

Reboot interval Number of hours between forced reboots.

Upload duration Number of seconds the device can use after a completed task to upload its results.

Important: The duration is not considered by the QualiPoc devices but only in TM to do collision check validation for tasks – the upload duration is added to the overall task duration to determine the overall time that a device is in use. If the QualiPoc device is not able to upload its results before the next task is due, the next task won’t be started at all.

Note: This value is only used if no upload task for that same device is scheduled/running.

Timeout 1 Defines after which time of no contact to the unit it gets in the timeout 1 state.




14

Setting Description

Timeout 2 Defines after which time of no contact to the unit it gets in the timeout 2 state. If the unit is in that second timeout state, something went possibly wrong and the unit should be checked physically.

Status communication This flag allows the unit to do a status communication after each test. By a status communication the NTP time synchronization is done (if enabled) and some status information about the system are uploaded to the FTP server. There is no upload of measurement and log files.

Note: This value is only used if an upload task has not been scheduled or is currently running on the same device. If an upload task is running, TM uploads the status information with the measurement files.

Low memory behavior Select which kinds of messages and/or files should be deleted if the free unit memory is smaller than 500 kBytes.

Diversity Upload Profiles

Setting Description

Upload during measurement

Uploading over the cellular network during a measurement can influence the result. If you don't want this, disable this option.

Upload original files As the original non-reduced measurement files can be very large, this option handles if they are uploaded or not. This option is useful when WLAN connectivity exists, but uploading via cellular network could take extremely long; therefore it's not recommended.

Diversity Unit Profiles

General Tab

Setting Description

Timeout 1 Amount of time to wait for contact with the unit before entering the timeout 1 state.

Timeout 2 Amount of time to wait for contact with the unit before entering the timeout 2 state. If the unit is in this state, you need to physically check the unit for the cause of the problem.

Note: This value must be greater than the heartbeat interval.

Data reduction duration [%]

Value in percent that TM uses to calculate the data reduction time during which the units reduce the data before uploading. Even if a data recording profile in the task has been used, the units still require this time to reduce the data. This value prevents the units from being overloaded with tasks and provides enough time for the data reduction to complete, that is, to avoid resource conflicts such as CPU time, disk input and output, and so on.

Low disk behavior Settings for actions that occur when the disk approaches low capacity.

Maintenance schedule

Select a schedule that is based on when the actions that you select are executed.




15

Diversity Explorer Tab

Setting Description

Power up delay Amount of time to wait after the ignition is turned on before the unit turns on.

Power down delay Amount of time to wait before the unit powers down after the ignition is turned off.

Switch-off voltage If the supply voltage goes below this value, the unit is powered down. Brownouts and the timing of brownouts are automatically handled by the UPS of the unit..

Heartbeat interval If powered down, the unit still sends heartbeat messages in this interval to signal its existence.

Unit Software Updates Unit updates can include SwissQual software updates, for example, QualiPoc Controller software, Diversity software), operating system updates, antivirus software updates, and so on. In general, you can include anything that is executable on the target unit in the software update for the unit.

Important: For this feature to work properly, you need to ensure that you enter the name of the SQL server when you log in to the server, and not "localhost" or the IP address of the server. For more information, see the "Connecting to a Database" section on page 4. The reason that you need to enter this information is that the Microsoft bcp utility , which inserts the binary update files into the database, requires a valid host name.

Adding Updates

Setting Description

Update file Selection of a specific update file that will be sent to the units selected when executing an update. The file must be in a special format represented by its name. TM checks for the correct file type.

Executing Updates

Setting Description

Available updates Selection of the update to transmit.

Units updateable List of all units that can be updated with the selected update file.

Units to update Units that will be updated on execute.

Other active units List of units that are not updateable because running on an even older version than the one to be updated or units that have already been updated.

Unit Groups Groups provide a useful overview of the units in your system. You can assign units to groups, which become the basis for the unit overview and system configuration tree views.




16

General Tab

Setting Description

Group name Display name

Parent group Select a parent group for the group.

Group type • Standard: For normal grouping and action triggering

• Diversity Benchmarker: Parent group for PCM units that displays the physical configuration of a Benchmarker system and stores the respective hardware settings

• Diversity Q: Parent group for PC units that displays the configuration of a Benchmarker system and stores the hardware and software settings of the virtual PCs from the carry case

• QualiPoc Freerider: Parent group for QualiPoc Freerider units which displays the configuration of a Benchmarker system and stores the hardware settings

Action buttons Although these actions can also be triggered at the unit level, only the group specific actions are described in this section. For information on the remaining actions, consult the section for the corresponding unit type in this document.

Important: The actions that you assign to a group are triggered on all of the units in the group, which can result in unforeseen consequences.

Update configuration • Force: Forces a configuration update on each unit

• Required only: Only updates the configuration on units that require an update.

Change GPS state If you move a system from a location with a GPS signal to a location without a GPS signal or the other way around., this action simplifies the change of the GPS state. If GPS is enabled and a signal is not present, a Benchmarker system will not allow the measurements to start, due to the missing location data, time synchronization, and so on..

Important: This action only applies to Benchmarker systems.

Group Specific Tabs

Setting Description

System ID Numerical ID of the system which must be unique within the network where the system resides. If you do not provide an ID, TM assigns the next possible value based on the existing systems.

Time synchronization All units in a group have the same time synchronization settings.




17

Diversity Benchmarker Settings

Setting Description

GPS source Select the GPS device, that is, an internal GPS receiver or an external RS-232 connector.

Note: If you choose the external option, you need to connect a GPS receiver to your system to receive GPS location information.

Switch off voltage [mV]

Specifies the threshold value for the input voltage of the DCM below which the Benchmarker system shuts down after the timeout value is reached. The default value is 10500 mV. The CBM measures this voltage at the input of the DCM. To disable the brownout protection for a vehicle battery, for example, in an office environment, set this value to 0.

Switch off timeout [s] If the input voltage of the unit drops below the threshold value for the amount of time that you enter in this box, the units shut down.

Remote Control Tab

Setting Description

Enabled Allows you to control the system remotely. Such a system does not have a permanent NQComm connection and instead communicates with TM through the media server as QualiPoc does.

Important: You can only use this option on a system that has a Remote Link Module (RLM).

Subscriber Subscriber that the RLM uses.

Access point Name of the access point that the subscriber uses to establish data connections to the media server. If you do not provide a name, you have to manually configure the access point on the RLM, which is not recommended.

Upload profile Defines how the unit uploads the measurement data.

Units

General Tab

Setting Description

Unit name Type the name of the unit

Computer name Type the name to identify the computer on the network. If you do not provide a name, the system automatically uses the unit name as the computer name.

Note: Diversity Explorer and QualiPoc use the computer name for the directory name of the unit on the FTP server.

You can only use the following character set for the computer name: a-z, A-Z, 0-9, -, _, .




18

Setting Description

Unit type Based on this setting the corresponding tabs for each type will open.

Group Assigns a unit to a group. The available groups and subgroups are indented for easier recognition.

Note: Benchmarker system units must have a system group as a parent because values that you set for the group are replicated on each unit.

Region If used, this field allows a more specific way to describe the unit's location. This value can be used in NQDI 's data selection.

Time synchronization Defines how a unit synchronizes time. In a Benchmarker system, each unit inherits the time setting from the group.

Time zone (offset to UTC) [min]

Difference in minutes between the time zone that you are in and Coordinated Universal Time (UTC). Locations that are east of Greenwich (London, UK) have positive offsets and locations west of Greenwich have negative offsets. For more information, go to: http://en.wikipedia.org/wiki/Coordinated_Universal_Time

Daylight saving time Specifies that the current time zone is in daylight savings time.

Note: You must change this option when daylight savings time starts or ends.

Meas. filename ID Name of the measurement file that contains the customer ID and the system ID of the license file. To ensure that DTMF configuration calls for double-sided tests remain as short as possible, these values are not transmitted. If you run double-sided multichannel campaigns with B-sides that have no connection, that is, status and job transfer connection for the unit is "No connection/DTMF", then all A-side units must have a Measurement filename ID. The B-side device receives this information with the campaign file and can then correctly name the measurement files.

Note: This value is not needed for QualiPoc units or double-sided testing with disconnected units.

Unit enabled A unit can be disabled. If so, it won't show in the unit overview or the single unit overview.

Update unit immediately

Automatically updates the unit with the new settings after the settings are saved to the database. This option requires that NQComm is on.

Connection Tab All connection settings are doubled because of the way the communication server is accessed:

• Different IP addresses (multi-homing)

• Different protocols

• Different logins

Setting Description

http://en.wikipedia.org/wiki/Coordinated_Universal_Time




19

Setting Description

NQComm control Connection between NQComm and the unit.

Important: Units that have the value "No connection" are considered standalone and are not shown in the main unit overview. Such units cannot report their actual state to NQComm. QualiPoc and Explorer units are always shown in the overview.

Unit control Connection that is used by the unit to communicate with NQComm.

Job transfer send If the job is sent by the A-side unit to the B-side unit (and not by NQComm), this setting tells the A-side how to reach the B-side unit.

Job transfer listen Connection on which the unit listens for a job.

NQComm result Connection through which NQComm fetches the result files.

Unit result Connection through which the unit uploads the result files.

Diversity Tab

Setting Description

Diversity unit profile Select the unit profile that you want to apply.

PCM slot number The numbering for the PCM slots starts with slot 0 to the right of the CBM and increments by one for each slot as you move to the right. This option is only available for PCM units.

Info section The values in this area are only visible after you complete the first hardware detection.

QualiPoc Tab

Setting Description

QualiPoc unit profile Selection of the unit profile to be applied.

SMS profile Selection of the SMS profile to be applied.

Info section The values in this area are only visible after TM polls the unit for the first time.

Actions Tab

Setting Description

Execute unit action The possible actions are shown in the combobox. Afterwards the action can be triggered by this button. The possible actions that are not self-explanatory are described hereafter.




20

Setting Description

Start hardware detection Detects the configuration of the unit and the configuration of the devices that are attached to the unit. The detection adds new units and devices to the system and updates previously detected units or devices. This process can take up to five minutes to complete. During this time, do not click Start hardware detection again. If you want to monitor the progress of the hardware detection, go to the Overview and check the status of the unit. When the status changes to “Ready”, the hardware detection is complete.

Note: After running the detection for the first time, the selection to the right of the button becomes enabled and the type of any further hardware detection can be selected.

Important: After running the detection and setting up all necessary things, either the unit or the devices must be updated to enable measuring.

Get measurement files If you disabled the result connection for NQComm on the connection tab, you can click this button to manually retrieve the files.

Get debug log files Get all debug log files from the current unit. NQComm receives a zipped file and unpacks this file in the directory defined in NQComm as “Measurement files directory”

Poll Sends a notification SMS to the QualiPoc unit which causes it to poll at the next possible moment.

Cleanup inbox Sends a notification SMS to the QualiPoc unit which causes it to delete its messages inbox.

Export configuration Exports the unit configuration as a zip-file which you can use to configure a disconnected unit. Only use this option after you set up the complete TestManager environment for the system, that is, system configuration, tasks, and campaigns. The zip file contains the following information:

• Unit configuration • B-side task files • B-side campaign files

Use the Diversity Maintenance Centre on the disconnected unit to import the zip file.

Unit configuration only If a unit is used in tasks and campaigns, the export includes the settings that are necessary to render the unit fully functional, for example, if you want the full configuration settings for a disconnected land unit. Use this option if you only want the unit configuration and nothing else.

Update position The position values for latitude, longitude and altitude are optional and the values will be added to the position history of the unit. The position can be set manually if the unit doesn't have GPS and can not report its position.

Note: If the values are ok in terms of format and content, the information will be stored. The fields will be reset to an empty value after successful saving – they do not show the last position of the unit. This value can be seen in the Single unit overview.

Latitude Latitude entered as decimal value with a range of -180 to 180.

Longitude Longitude entered as decimal value with a range of -180 to 180.

Altitude Height above sea level




21

Special Config Tab

Setting Description

Special config A unit can use settings that are not in the TestManager database, but rather in the Windows Registry or in a special settings file on the unit. To make these settings persistent, TestManager moves the settings step by step into this field or generates proper unit settings from the field by adding new options to this tab. For example, you can use this field to create custom Windows Registry settings.

To create a custom registry setting on the Special Config tab 1. Open the Windows Registry Editor.

2. Right-click the node that you want to include and then click Export.

3. Save the *.reg file and then open the file in a text editor.

4. Select all of the text and press CTRL+C to copy the text to the clipboard.

5. In TestManager, select the unit that you want to add the setting to.

6. On the Special Config tab for the unit, press CTRL+V to paste the node.

7. Click Update.

Devices All possible devices are shown as icons on top.

General Tab

Setting Description

Device name Name of the device which is used in combination with the unit name in the task configuration.

Customizable ID Can be left blank; in this case the ID will be set automatically. In a pure benchmarking setup, multiple system are used, each with its own TestManager setup. In order to be capable of bringing the result data together, customizable IDs for devices and tasks can be used. As these two IDs are part of the measurement result file names, the corresponding files can be collected and evaluated. Using these IDs in a customized way means putting a meta layer over multiple Benchmarker systems.

Manufacturer/Model Select the type of device from the list.

Device enabled You can disable single devices of a unit. If a device is disabled, the configuration of the device is not sent to the unit.




22

Remoting Tab

Setting Description

Mode active Checks if the device is connected to the unit and delivers data. passive Obtains data from a remote active device that you select from the list.

Note: Only for device type "Scanner" a passive device can be entered. The units of the same Benchmarker system do not receive automatically scanner data. However, the units of a Benchmarker system automatically receive GPS data if a GPS device is connected on any of the units.

Important: Once the device is saved, the mode can not be changed anymore.

Subscribers Tab This tab is only available if the device supports a subscriber.

Setting Description

Subscriber The main subscriber for the device, the SIM card of which is in the first available slot.

SIM multiplexer Type of SIM multiplexer device.

Subscriber 2 - 6 If a SIM multiplexer is present, specifies the slot that the SIM card is in.

ISDN Device You can use ISDN devices for Intrusive and Non-Intrusive job types or as a definition for an answering station.

General Tab

Setting Description

Device name Name of the device, which is used in combination with the unit name in the task configuration. “ISDN 0/1” refers to board 0 and channel 1.

ISDN Settings Tab

Setting Description




23

Setting Description

Phone number Phone number of the ISDN device.

Important: You can only enter numbers in this box. At the moment, the capi DLL does not support the international number format so you can not enter a plus (+) sign.

Dial-out prefix Prefix to be used if this device is dialing out. Possible values are:

• 0 - 9

• # * (standard DTMF tones)

• ~ (wait for dial-tone)

Channel One ISDN controller has two B channels and one D channel (for control only, not configurable). The “Channel” assignment resembles the following list:

Device Board (Controller)

Channel (MSN)

ISDN 0/0 0 0

ISDN 0/1 0 1

ISDN 1/0 1 0

ISDN 1/1 1 1

Board Physical ISDN card If a unit has more than one board, increase this number to identify the board on the system. For example, the first board is 0, the second Board is 1, and so on.

Important: If you use boards from different manufacturers, start at 0 for each manufacturer.

DTMF scan If you select this option, the system configures the device with the DTMF settings.

Called party check Ensures that the ISDN device only accepts incoming calls that correspond to the phone number hat you entered for this device.

Calling party check Ensures that the ISDN device only accepts incoming calls that correspond to the phone number hat you entered for the calling device.

Answering station If the device is used as an answering station, then this flag must be set. All other options no longer apply. The flag prevents writing a job file. As answering station, the device can only be used as B-side device with a QualiPoc device as A-side.

Multi-line This option can only be set when the Answering station option is used as well. It states that the answering station has multiple lines. This enables the use of this device in multiple jobs at the same time.

Important: Using this option disables the schedule collision checking of that device. It will not be checked at all, because of its multiple lines it can handle multiple calls at once.




24

PSTN Device See the "ISDN Device" section on page 22 for information on all the PSTN device settings that are not covered in the following sections.

PSTN Settings Tab

Setting Description

Dial-out prefix Prefix to be used if this device is dialing out. Possible values are:

• 0 - 9

• @ (pause of 1 second)

• , (pause of 500 milliseconds)

• #, * (standard DTMF tones)

Mobile Device

Mobile Settings Tab

Setting Description

Subscriber Choose a subscriber from the list. For a description on how to add a subscriber to this list, see "Subscriber" on page 7. Each subscriber provides different access points, such as GPRS and WAP for the tests.

MCM Check this if a mobile connection module is used with the device.

COM port control COM port that controls the mobile phone (dial, version query, and so on). This value is inserted by hardware detection or manually.

COM port trace COM port that receives trace information from a trace enabled mobile phone, for example, a Nokia 6680. This value is inserted by hardware detection or manually.

COM port dialup COM port that performs data and other types of tests. This value is inserted by hardware detection or manually.

IMEI IMEI number of the device You can leave this box empty or enter the 15-digit IMEI number. This value is inserted by the pre-configuration.

DTMF scan If this option is selected, the system configures the unit with the DTMF settings.

Datacard Device

Datacard Settings Tab This section describes the settings that apply to mobile devices.

Setting Description

Adapter If the datacard is as network adapter, enter the name of the datacard that appears in Windows Network Connections.




25

Dial-Up Device A dial-up device is a substitute for any device that can establish a dial-up connection and run data jobs. The device must contain a modem that accepts AT commands.

Setting Description

Dial-up network entry Name that is found in Windows Network Connections.

IMEI IMEI number of the device You can leave this box empty or enter the 15-digit IMEI number. This value is inserted by the pre-configuration.

Network Adapter Device

Setting Description

Adapter Name of the adapter in Windows Network Connections

Scanner Device You can use a scanner to gain additional mobile network data while another test runs, for example, an intrusive speech test. An active scanner must always be added through hardware detection. It is necessary to read the options the scanner is capable of.

To add a passive scanner, click the Add Scanner Device icon and enter the details for the scanner.

Important: The load of the scanner is checked when its configuration is saved. You can check the current load during configuration by using the Check load button.

Scanner Tab

Setting Description

COM port Serial COM port to which the scanner device is connected.

Baud rate Transfer rate of the data. The current scanner software only works with 115200.

Timing mode • GPS only -> chip timing derived from GPS signal

• GPS priority -> scanner is having timing mode "GPS only" as higher priority mode over timing mode "Sync Ch" which “kicks in” when GPS signal is lost. (Sync Ch indicates timing acquired from Sync Channel Message.)

Configuration Tab Configure all scans that are needed. Scans can be added, deleted or updated. By clicking on the scan, its details are loaded in the top section of the tab..

WCDMA Examples The following figures show which areas are scanned when you select the 5MHz or 15MHz bands.




26

center frequency

sampling frequency node

sampling area [5 MHz]

Sampling Area 1: Start Frequency 2110.0 Mhz (125 Nodes @ 40 kHz)Sampling Area 2: Start Frequency 2115.0 Mhz (125 Nodes @ 40 kHz)Sampling Area 2: Start Frequency 2120.0 Mhz (125 Nodes @ 40 kHz)

10562 10587 10612 10637 10662 10687 10712 10737 1076210562 10787 10812 10837

10550

MHz2120 2125 2130 2135 2140 2145 2150 2155 2160 2165 21702110

10575 10600 10625 10650 10675 10700 10725 10750 10775 10800 10825 10850

2115

10562 10587 10612

Example 1: center frequency in band #2

Figure 6-1 WCDMA Example 1: Center Frequency in Band #2

In Example 1 the 5MHz range of the center frequency (or channel) is 2115 MHz to 2120 MHz and the 15MHz range is 2110 to 2125MHz.

center frequency

sampling frequency node

sampling area [5 MHz]

Sampling Area 1: Start Frequency 2110.0 Mhz (125 Nodes @ 40 kHz)Sampling Area 2: Start Frequency 2115.0 Mhz (125 Nodes @ 40 kHz)Sampling Area 2: Start Frequency 2120.0 Mhz (125 Nodes @ 40 kHz)

10562 10587 10612 10637 10662 10687 10712 10737 1076210562 10787 10812 10837

10550

MHz2120 2125 2130 2135 2140 2145 2150 2155 2160 2165 21702110

10575 10600 10625 10650 10675 10700 10725 10750 10775 10800 10825 10850

2115

10562 10587 10612

Example 2: center frequency in band #1

Figure 6-2 WCMDA Example 2: Center Frequency in Band #1

In Example 2 the 15MHz range is the same as in Example 1 since the scanner is not allowed to scan below 2110MHz.

Top Channels Tab Selection of operators to be considered for the measurement data of top channels. Only active operators that have set the corresponding values for channel measurement are shown in the list. For example if an




27

operator has values set for NCC and GSM channels and the scanner supports GSM, the operator is shown in the list.

If the scanner setup has an operator in its settings that has been deactivated or deleted in the meantime, it will be corrected automatically by the TM. Only valid operator settings are used for measurements.

Important: See the settings for channel assignment in the "Operators" section on page 7.

Info Tab After you connect the scanner to the unit, the Info tab displays the manufacturer and serial number information for the scanner.

GPS Device The configuration for the GPS connected to a Benchmarker system is inherited by all units in that system.

Important: There can be only 1 GPS per unit or Diversity Benchmarker or Diversity Q system. If you want to connect and use an external GPS, you must first delete the existent GPS and afterwards add your external device manually. If you run an automatic hardware detection, the same will apply. If more than 1 GPS device is found, only the first reported device will be entered.

Serial Port Tab

Setting Description

COM port COM port where the GPS is attached.

Baud rate Sets the maximum rate, in bits per second (bps), for data transfer through the serial port.

Parity Select the type of error checking that you want to use. The GPS device must have the same parity setting that you select here.

Data bits Select the number of data bits that you want to use for each character that is transmitted and received. Most characters are transmitted in seven or eight data bits. The GPS device must have the same data bit setting that you select here.

Stop bits Changes the time interval in bits per second between the transmission of each character.

QualiPoc Device

Mobile Settings Tab

Setting Description

Default access point Access points that a QualiPoc device uses to connect to the FTP server. Except for a WiFi APN, the default access point must belong to the same operator as the main Subscriber, that is, the SIM card in slot 0 of the SIM multiplexer.

Fallback access point Access point that the device tries to connect to if the default access point is inaccessible.

Trace masks




28

Setting Description

IMEI IMEI number of the device. You can leave this box empty or type the 15-digit IMEI number. The value that you enter is inserted by the pre-configuration.

GPS type Lists the GPS types that are available. The GPS positions are written to the measurement file, except if you select None.

Valid position required

Delays a measurement until a valid GPS position is received.

Device Overview Page The device overview page contains a read-only list of the devices that are in your Diversity system. The list provides information about which tasks a device runs and where applicable, which subscriber the device uses. If the subscriber column contains the text "Subscriber not set", you need to assign a subscriber to the device before you can run a task. If the column contains "N/A", you do not need to assign a subscriber to the device.

Trace Masks List Page The trace masks list determines which trace messages that the mobile phone or data card saves to the measurement file.

You need to specify a different trace mask configuration for each device, for example, for the Nokia 6680 or for a device that contains the Qualcomm chipset (mainly UMTS/WCDMA devices).

Note: The assignment of a trace mask is optional. If unassigned, the system will use a default mask.

To define a trace mask for a device 1. In the Navigation pane, click System configuration, click Trace masks list, and then click Add trace

mask.

2. In the Trace mask name box, type the name for the trace mask.

3. In the Device box, click the device that you want to create the mask for.

4. On the tabs shown (for example, Trace, FTD) select the options for the trace mask.

To assign a trace mask configuration to a device 1. In the Navigation pane, click System configuration.

2. In the workspace area, click the unit that the device is attached to, and then click the device, for example, a mobile phone.

3. In the Details area, click the Masks tab.

4. In the Trace masks box, click the mask that you want to use.

Note: If the list is empty, you need to define a trace mask for the selected device type.



Chapter 7 | Job and Test Configuration CONFIDENTIAL MATERIALS

29

7 Job and Test Configuration A job is a collection of similar tests that share the same timing and job options. The tests that are defined in a job are executed consecutively. The job options are located on the General tab. Each job is of a specific type, that is, an intrusive job can only contain intrusive tests. Additionally, each job must be defined for a specific unit type since some test settings for different unit types require different values and interaction.

You need to specify the following settings for a job:

• Job options • Tests • Timings

Note: The timings for most jobs are similar.

You can configure the following job types in TestManager:

• Intrusive: A typical double-ended telephony job that establishes a voice or video-call between an A-side and a B-side measurement unit and then sends voice samples between the two units.

• Non intrusive: A single-ended telephony job that establishes a voice call to a defined far-end side. Instead of a measurement probe, the far-end side can be a voice box, a service number, or an answering voice call. The job evaluates the listening quality of the voice signal that is received by the measurement unit from the test number. The signal is evaluated with NiNA+. You only need one unit for this type of job.

• Access test: Attempts to call a number, and after the connection is made, the job stops. You only need one unit for this type of job.

• Call to any number: A call is made to any number. The job maintains the connection for a period of time and then disconnects. You do not need a dedicated B-side unit.

• Call from any number: • Data: IP tests such as FTP, HTTP, and so on. • Video over IP: Video streaming test that is designed for a PC. The test uses a phone or data card as a

modem and plays the video on the PC where the measurement probe runs. • Idle: The mobile device stays in idle mode and only idle trace data and scanner data are collected. • Scanner only: Only scanner data is collected. • Forcing: Allows you to define a job that forces a device into a defined technology or band. • Upload: Units receive instruction as to when to upload result files.

To add a job 1. In the Navigation pane, click Tasks, and then click Jobs.

2. Click Add Job.

3. Specify the settings for the job, and then click Add.

Timings Tab The parameters that are available on the Timings tab are similar for all job types, except for Intrusive jobs.

Data, Video Over IP

Setting Description




30

Setting Description

Initial pre connect delay Delay time before the connection attempt (dial-up) begins. 00:00:00 indicates that this setting is not used.

Post connect delay Delay time after a successful connect attempt. 00:00:00 indicates that this setting is not used.

Max connection attempts

Defines the maximum number of connection attempts per Window.

Connection reattempt delay

Delay time before another connection attempt is being started. 00:00:00 indicates that this setting is not used.

Intrusive Job Type For more information, see Manual - Voice Tests.pdf

Setting Description

Test seq. repetition Allows you to quickly create long calls by repeating the job for the number of times that you specify.

Record HO Record Hang-Over - see Figure 7-1 on page 30. The default value is 2000 ms, however, 1000 ms is usually sufficient for M2L calls. The Record HO covers the signal delay on the channel. To prevent clipping at the end of the audio recordings, do not enter a value that is close to 0 ms.

Allow call re-establishment

Keeps the VoiceEngine open if a connection drops and waits for the mobile phone to re-establish the call, so that the measurements can continue. At the end of the Call Duration that you specify on the Timings tab, the phone drops the call.

Note: Only some network operators allow mobile phones to re-establish a dropped call.

In both cases, the call status changes to “Dropped”.

Figure 7-1 Record Hangover

You can use the voice channel of a video call connection to run each of the intrusive measurements. For more information refer to ‘Manual – Video telephony.pdf’

Setting Description

Recording Time

Record Hangover (Default: 2 sec)

Playback Time

Sample Length

Test Duration

0.5 s




31

Setting Description

No Video Call Establishes a common voice call

Phone to Phone Allows the establishment of a video call from one mobile phone to another. The transmission and capture of the voice sample is the same as a voice call.

Phone to Responder Mobile phone calls a responder station that plays out a (pre-stored) audio and video clip from its own memory. The voice signal is captured in the same was as a common voice or video call. You can also capture the phone display with a camera if you have the dedicated hardware

Stack to Stack (half duplex)

Emulates the video telephony client on the measurement probe. This video stack mode bypasses the internal phone VT client and runs these software components on the host PCM. The mode allows for full access to the audio and video signals at the digital capturing interfaces as well as traces the H.324 protocol information. In the half-duplex mode the video clip is only sent in the same direction as voice is sent too.

Stack to Stack (full duplex)

In the full-duplex mode the video is transmitted simultaneously in both directions whilst voice is transmitted in one only (voice remains half-duplex).

Phone to Stack Inserts the video stream directly into the protocol that is received on the mobile phone. The display of the phone is captured by a camera.

Save video files Specifies the settings for saving video recordings as AVI files. Be aware that these files can be quite large.

Timings Tab

Call Window Timings Area

Setting Description

Window Duration [s] Time in seconds for a Mobile Originated Calls (MOC) or Mobile Terminated Calls (MTC) window. For NetQual, MOC means A to B and MTC means B to A. Within a window, the system performs 0 or more tests calls. Such calls can either be started and terminated by the mobile unit. This parameter is extremely important and is always respected during the test session to keep the A-side and the B-side synchronized.

Use Call Duration to Abort Call

Terminates the call when the pre-configured call duration expires and makes the Dedicated Mode part of a test fixed. If you want the call to terminate after the tests are completed, clear the check mark from this box.

Note: If you clear the check mark, the duration of a test depends on the Call Setup Time and on the Calculation Time of the algorithm, both of which are not fixed. As a result, the ratio between Dedicated Mode and Idle Mode of a test is not fixed.

Call Duration [s] Time in seconds between the Dial command and Disconnect.

Pause Duration [s] Time in seconds between the last call termination and the next Dial command.

1st Call Setup Delay [s] Time in seconds between the start of a new window and the first call setup.




32

Setting Description

Guard Time [s] Time in seconds before the end of the window where all ongoing calls are disconnected by the system to ensure that the next measurement window can start immediately.

No Call Setup Time [s] Time in seconds before the end of the window where no new calls are started.

Average Call Setup Time [s]

Time in seconds, which is used to calculate the remaining time for the tests within a call. This value directly affects the Total Duration.

Example • Call Duration = 120 sec • Average Call Setup Time = 10 sec • Approximately 5 seconds is needed to perform audio synchronization before the real tests can start

As a result, the call is online for 105 seconds during which the tests can be performed.

General Settings Area

Setting Description

MOC:MTC Ratio Specify the ratio of MOC windows to MTC windows.

Important: For QualiPoc speech tests, you must set this parameter to 1:0.

Example • 1:1 1x MOC window followed by 1x MTC window, followed by 1x MOC window, and so on. • 0:1 Only MTC windows • 1:0 Only MOC windows • 2:1 2x MOC windows followed by 1x MTC window, followed by 2x MOC windows, and so on.

Call Failure Behavior Area

Setting Description

Pause after Failed Call [s]

Time in seconds that the system to pause after a failed call setup. This can be different from the normal pause time between calls.

Max Failed Calls Maximum number of consecutive failed calls.

Important: In the case of a failed call, the Window duration always applies. The A-side and the B-side must remain synchronized during the whole test, even if a failed call occurs. By definition, a failed call can not be acknowledged by the B-side.

Pause after Max Failed Calls [s]

Time in seconds that the system pauses before the next call setup after the maximum number of failed calls is reached.

Max Call Setup Time [s] Maximum time in seconds for call setup.




33

Setting Description

Alerting Timeout [s] Time in seconds between Channel Request and Alerting. If this value is > 0, then the call terminates if the alerting signal is not received within the specified time after a channel request.

Note: This parameter is only applicable for mobile devices.

No Connection Timeouts [s]

If MOC or MTC calls occur within this time, the system stops.

Figure 7-2 Task and Call durations

This shows how the parameters “Max Call Setup time” and “Alerting timeout” affect to the call setup behavior.

Figure 7-3 Max Call Setup Time and Alerting Timeout effect on call setup behavior

Intrusive Tests Tab Intrusive tests are designed to measure the quality of a connection. These tests use the following algorithms:

• Speech: Measures the Listening Quality (LQ) in the traditional telephone band (300 … 3400Hz, narrowband)

Call duration

1st call delay

max. CS time Sample & Eval Sample & Eval Sample & Eval Sample & Eval

Task duration

Call duration

Window duration

Guard time

Max Call Setup Time

Alerting timeout

Connection

Request

Start

Call

Alerting Connected

Terminate Call if no Connect

received

Terminate Call if no Alerting (or Connect)

received




34

• Speech-Wideband: Measures the Listening Quality (LQ) in wideband mode (50 … 14000Hz).

Note: The voice signal sent into the channel and the applied LQ measure are different for narrowband and wideband tests. If you measure a narrowband channel in wideband mode, the test counts the bandwidth limitation of the channel as degradation. For more information, see Transition to the new version of Squad and Wideband Voice Test.pdf

• Noise suppression: Narrowband test that evaluates the qualitative performance of noise suppression systems in the handset or a channel. For this reason, the test interlaces voice samples with background noise to the channel and measures the quality of noise reduction.

• Advanced Echo Check active (AECa): Narrowband test that evaluates the qualitative performance of Echo Cancellation systems in a handset or a channel. The test actively inserts an echo to simulate an echo-generating handset at the far end side and measures the delay and return loss of the remaining echo.

• Advanced Echo Check passive (AECp): Narrowband test that measures the delay and return loss of an echo that is caused by any component on the network. The far end side is considered as ‘perfect’ and does not generate an echo.

• Round Trip Time: Measures the voice signal roundtrip time by an inband measurement. For an assumed symmetric delay in both directions, half of the round trip time can be considered as one-way signal delay.

• DTMF: Tests the transmission of DTMF tones

Note: The settings are similar for all intrusive test types except for Advanced Echo Check (active) and Round Trip Time.

Setting Description

Test name Name of the test. You can use any name.

Intrusive test type Select the type of test that you want to create.

Direction A to B: Test sample is sent from the A-Device to the B-Device. This setting is also known as uplink if the A-device is a mobile. B to A: Test sample is sent from the B-Device to the A-Device. This setting is also known as downlink.

Save WAV files Specify the save options for the resulting wav files. All: Saves all the wav files None: Does not save the wav files LQ <=: Saves the wav files that are below the LQ threshold value that you enter.

Reference sample Select the reference voice sample that you want to use for the test. The samples are in different languages.

Duration approx [s] The system calculates the amount of time needed for the tests depending on the reference sample.

Note: Make sure that the test is defined correctly on both side, as above if the A-side sends a sample, then the B-side must be set to record. The test order and the samples must always be the same on both sides.

Acoustic Echo Active Test To create an echo on the receiving end of the test, the SQUAD Acoustic Echo Check (AEC) requires more information than the other intrusive tests.




35

Setting Description

Reference sample Select the sound sample file to cause the echo for the test.

Double talk sample Select one of the three double talk samples to challenge the EC.

Note: The filename of the sample includes the percentage of active speech in the sample.

Type Select the echo type to define the echo-path response. In addition to the nine responses that are defined in ITU-T G.168, you can also select a plain reflection as well as dry and hollow reverb.

Attenuation [dB] Specify the amount in decibels to attenuate the sound level of the reference sample. This setting is comparable to a selectable TCL.

Echo delay [ms] Specify the delay in milliseconds for the echo. To estimate the tail length of an echo canceller, define a series of SQuad AEC active measurements in a job and increase the echo delay of successive tests.

Non-Intrusive Job Type

General Tab

Setting Description

Video call Sets up a video call instead of a normal voice call.





Timings Tab

Setting Description

Window duration Overall window duration. If you want to add a job to a fixed window task, you need to specify the window duration. To disable this option, enter 00:00:00.

Guard time Ensures that the next window can start properly unconnected.

Invalid connection time Suppresses a connection attempt when the amount of time left in a window is not sufficient to start a new session. To disable this option, enter 00:00:00.

Pause between cycles This pause applies if a task has multiple cycles.

Max. connect timeout If the call is not answered by the called party within the amount of time that you specify in this box, the call is aborted and the job fails.




36

Non-Intrusive Tests Tab • Only one NiNA+ test type is available for a non-intrusive job.

For more information, see “Manual - NiNA+ Voice Test Results Description.pdf”.

Setting Description

Test name You can use any name to identify the test.

Non-Intrusive test type The only option is NiNA+

Call duration Amount of time before a call is disconnected.

Interval time Specify the interval at which the algorithm evaluates the recorded signal.

Number to call Specify the number that you want the device to dial.

Save WAV files Specify the save options for the resulting wav files. All: Saves all the wav files None: Does not save the wav files Limited: Saves the wav files that are below the threshold value that you enter in this box.

Call to Any Number Job Type This job type tests enables a call connection for a specified amount of time and then disconnects the call. As a result, you can test if a network and mobile phone can successfully connect.

General Tab

Setting Description





Make calls in non service area

Mobile phone tries to establish a call even in the absence of coverage.


Timings Tab

Setting Description






37

Setting Description


Pause after last test This pause value only applies to the last test in the test sequence of a job and only has an affect if the job is used in a “sequential” task.


Call to Any Number Tests Tab

Setting Description

Test name You can use any name to identify the test.

Duration Amount of time before the call disconnects.

Number Specify the number that you want the device to dial.

Access Test Job Type This job type test the validity of phone numbers and the ability of the receiving end to answer calls. When a successful connection is made, the test stops.

Note: You can only use one unit for this type of job.

General Tab

Setting Description


Timings Tab

Setting Description




Pause after last test This pause value only applies to the last test in the test sequence of a job and only has an affect if the job is used in a “sequential” task.


Access Test Tests Tab

Setting Description




38

Setting Description

Test name You can use any name for the test.

Number Specify the number that you want the device to dial.

Data Job Type Before you use this job type, see Manual - Data and Video Tests.pdf for more information on data jobs.

General Tab

Setting Description

Test seq. repetition Specifies how often to repeat the sequence of defined tests.




39

Timings Tab Important: The window timings settings are not considered yet by QualiPoc devices for data jobs.

Setting Description

Initial pre connect delay Delay time before the connection attempt (dial-up) begins. 00:00:00 indicates that this setting is not used.

Post connect delay Delay time after a successful connect attempt. 00:00:00 indicates that this setting is not used.

Max connection attempts

Defines the maximum number of connection attempts per Window.

Connection reattempt delay

Delay time before another connection attempt is being started. 00:00:00 indicates that this setting is not used.

Pause between cycles This pause applies if a task has multiple cycles. If randomization is used, the Duration becomes the minimum and together with the Maximum the randomization range is given.

Data Tests Tab This job type allows data tests based on IP enabled devices. The following tests are available:

• Ping: Measures the roundtrip time (RTT) for multiple pings.

• Ping Trace: Measures RTT for any hop to the destination.

• FTP: Measures throughput for up- and download files.

• UDP downlink: Measures downlink bandwidth with UDP.

• GPRS attach: Tests whether mobile is able to attach to GPRS.

• GPRS detach: Test whether mobile is able to detach from GPRS.

• PDP activation: Tests PDP Context activation for GPRS. PDP deactivation: Tests PDP Context deactivation for GPRS.

• PDP deactivation:

• HTTP Browser: Measures time and throughput for getting one complete HTML page through HTTP.

• HTTP Transfer: Measures throughput for up- and download files.

• Email send: Measures throughput for email sends.

• Email receive: Measures throughput for email receives.

• WAP: Measure the performance of the WAP service

• MMS send: Tests MMS Send function.

• MMS receive: Tests MMS Receive function.

• SMS send: Tests SMS Send function.

• SMS receive: Tests SMS Receive function.

• UDP plus: Measures downlink/uplink bandwidth/delay with UDP.

Setting Description

Test name Name of the test. Any name is allowed to identify the test.




40

Setting Description

Data test type Choose what should be measured.

Pause [s] This allows you to indicate how much time (in seconds) you want the application to wait before starting the next test.

Random Apply a random pause between the defined tests. In that case the value of 'Pause' becomes the minimum and together with the value of Maximum the range for randomization is given.

Maximum [s] Maximum value for pause randomization between tests.

Ping

Setting Description

Host You will need to enter the host address (may also be an IP address).

Number of Pings This specifies the number of Ping packets to be sent.

Interval This parameter allows you to specify the time the application will wait after a ping has returned (echo) or timed out before sending the next ping.

Packet Size This parameter indicates the size of the packet you want to send. The default packet Size is 32 bytes. The maximum size recommended is 1000 bytes.

Timeout The timeout parameter refers to each ping. If a ping does not return within this period, it is recorded as lost. The test will still go on, even if pings are lost.

In the Ping test, the option Max duration is not available. It will automatically calculate this from the timeout, number of pings and interval.

Ping Trace

Setting Description

Host You will need to enter the host address (may also be an IP address).

Packet Size This parameter indicates the size of the packet you want to send. The default packet Size is 32 bytes. The maximum size recommended is 1000 bytes.

Timeout The timeout parameter refers to each ping. If a ping does not return within this period, it is recorded as lost. The test will still go on, even if pings are lost.

The PingTrace test has all the same parameters as the Ping test, except that, in the PingTrace test, the Max Duration is available. You can set a maximum time for the whole test (default is 00:01:00 = 1 minute). Once this period of time expires, the test will end.

FTP

Setting Description

Host IP address or host name of the FTP server.

Operation Select GET (Download) or a PUT (Upload) operation. The GET operation downloads a specific file from the FTP server. The PUT uploads a local file to the FTP server.




41

Setting Description

Mode Active means the server establishes the transmission connection (client listening), Passive lets the client connect to the server for data transmission (server listening). If you encounter connection problems (no/ closed connections) with the one mode, try using the other mode. Firewalls and NAT may block or close connections.

Local file Put: Name of the file to be uploaded from the local drive to the server. Get: Name that the received file gets when stored locally. This value can be left blank; in that case, the file name is the same as the original one.

Remote file Put: Name that the uploaded file gets when stored on the remote server. This value can be left blank; in that case, the file name is the same as the original one. Get: Name of the file to be downloaded from the remote server.

User User name of the FTP account.

Password Password of the FTP account.

Buffer size Size of FTP buffer for upload tests. Minimum is 4096 bytes (default value), maximum is 65536 bytes. The field is disabled for download tests and shows the default value.

Note: The buffer size only applies for non QualiPoc devices. QualiPoc uses a fixed buffer size of 4096 bytes because of memory restrictions on certain devices.

Time window If set to a value greater than 00:00:00, this activates the check for transmission timeout. If the measured bytes are lower than the threshold in the given time window, the test will be dropped and marked as failed.

Byte threshold Minimum count of bytes that have to be transferred in the time window.

HTTP Browser

General Tab

Setting Description

Host You can specify just the address of the web server (123.123.123.123) or you can include a directory (123.123.123.123/website). You can also specify the protocol (http://www.swissqual.com or https://www.swissqual.com). If the protocol is not specified, http:// is used.

Remote File You can indicate a specific HTML file for the application to download. If this parameter is left blank, the application will download the default HTML file (for example, index.html) from the specified Host.

HTTP Proxy If a proxy is used, enter its address here.

HTTP Proxy Port Port of the proxy

http://www.swissqual.com/

https://www.swissqual.com/




42

QualiPoc Tab

Setting Description

Cycles Number of repetitions for that URL

Max download time per cycle

Maximum time for the download of that URL

Pause between pages in 1 cycle

Pause between the repetitions of that URL

Keyword Keyword for which all downloaded pages will be scanned for

Dynamic URL Links to follow on that URL, one per line.

Note: Certain scripts embedded in accessed pages may block this test and let it timeout finally. If this phenomenon occurs, open Internet Explorer, select menu Tools Internet Options, select the Security tab, click Custom Level button, set Scripting ActiveScripting to Disable. Click OK buttons to return to Internet Explorer and close it. After that, this test should work. Alternatively, configure this test with another URL.

HTTP Transfer

Setting Description

Host You can specify just the address (hostname or IP address) of the web server (123.123.123.123) or you can include a directory (123.123.123.123/website). You can also specify the protocol (http://www.swissqual.com or https://www.swissqual.com). If the protocol is not specified, http:// is used.

Operation Select GET (Download) or a PUT (Upload) operation. The GET operation downloads a specific file from the server. The PUT uploads a local file to the server.

Local file Put: Name of the file to be uploaded from the local drive to the server. Get: Name that the received file gets when stored locally. This value can be left blank; in that case, the file name is the same as the original one.

Remote file Put: Name that the uploaded file gets when stored on the remote server. This value can be left blank; in that case, the file name is the same as the original one. Get: Name of the file to be downloaded from the remote server.

User Password

User name if login credentials are needed.

Buffer size Size of buffer for upload tests. Minimum is 4096 bytes (default value), maximum is 65536 bytes. The field is disabled for download tests and shows the default value.

Note: The buffer size only applies for non QualiPoc devices. QualiPoc uses a fixed buffer size of 4096 bytes because of memory restrictions on certain devices.

Time window If set to a value greater than 00:00:00, this activates the check for transmission timeout. If the measured bytes are lower than the threshold in the given time window, the test will be dropped and marked as failed.

Byte threshold Minimum count of bytes that have to be transferred in the time window.

http://www.swissqual.com/

https://www.swissqual.com/




43

UDP Downlink

Setting Description

Number of Packets Number of packets to be transmitted.

Packet Size The size of the packets in bytes.

Bandwidth This parameter allows you to specify at what bandwidth you want the application to download the UDP packets.

Timeout This indicates the time (in seconds) which the application will wait for the UDP packets to return. If no packet returns within this period, the application will record packet loss and end the test.

The UDP downlink test measures downlink bandwidth with UDP packets. Usually this test is used to verify an offered downlink bandwidth (generally for data or video streams) can be reached by the customer.

UDP Plus

General Tab

Setting Description

Host IP address or host name of the server.

Chirp file Specifies the name of the chirp file (containing the packet pattern) to be used.

Cycles Specifies the number of times the chirp file pattern should be repeated within the test.

Server TCP Port This parameter must be set to the port number on which the UDP Plus server application is waiting on for a test session.

Server UDP Port This parameter specifies the UDP port the server application shall use on the server side for the test.

Client UDP Port This parameter specifies the UDP port the client application shall use for the test.

Server Password The server application can only be accessed using a password. Default is “testpw”.

Timeout This indicates the time the application will wait for the UDP Plus packets to return. If no packet returns within this time, the application will end the test.

Advanced Server Config Tab

Setting Description

H-Packet reply size Defines the new packet size to which the server will adjust the H-packets before sending them back to the client. If the value is zero, no adjustment will take place (H-packet: RTT).

U-Packet reply size Defines the new packet size to which the server will adjust the U-packets before sending them back to the client. If the value is zero, no adjustment will take place (U-packet: Uplink).

B-Packet reply size Defines the new packet size to which the server will adjust the B-packets before sending them back to the client. If the value is zero, no adjustment will take place (B-packet: Downlink).




44

Setting Description

Overall packet reply size Defines the new packet size to which the server will adjust all received packets before sending them back to the client. If the value is zero, no adjustment will take place. This value is the least significant and can be ‘overwritten’ by the above described parameter values.

Enable auto size shrinking for entire packet reply

If checked the server can shrink packets to the new defined packet size, before they are sent back to the client. In case that the option is not checked, shrinking is not allowed and therefore the packet will not be cut.

Packet timeout Time after which the server application starts to send server generated packets if client packets no longer reach the server.

Packet interval Time interval between the packets sent by the server.

Packet count Total number of server generated packets the server sends.

Packet size Defines the packet size used for server generated packets.

Handle packets as B-reply packets

If checked, the client will handle the received server generated packets like downlink packets. Otherwise no test calculations will be performed.

Client Limitations Tab

Setting Description

Maximum capacity for send buffer

Defines the maximum size of the send-buffer.

Maximum time per packet in send buffer

Defines the maximum time a sent client-packet can wait for its corresponding reply-packet to arrive. If time is up, the packet is being deleted from the buffer and marked as lost.

Note: The expression “size” means packet payload size. The actual transferred data consists of packet payload, UDP header (8 Bytes) and IP header (20 Bytes).

The UDP test measures round-trip time and throughput by round-tripping UDP packets. Both round-trip time and throughput are recorded.

UDP Plus is a slightly more flexible UDP test where UDP traffic may be predefined within a chirp file.

This test type requires a special license and is not part of the standard data test package.

Email Send

Setting Description

SMTP Sever You need to indicate the SMTP server. This may be a SwissQual MediaServer or the SMTP server given by the operator/provider. If you need to use a special port other than the default (port 25), then you can simply add it with a colon: server:port.

Email address When using a SwissQual Media Server (IPServer), just enter the account name (for example, ‘gprs22’); otherwise, use a fully-qualified email address (for example, ‘[email protected]’).

Subject This parameter allows you to give the email message you are sending a subject title. This facilitates receiving this same email message in the “Email receive” test.




45

Setting Description

Attachment You can send/receive an attachment within an email message. This parameter is not available with the Receive function. The application will retrieve the first available email message on the POP3 server which may or may not have an attachment. This is the email message you would have previously sent with a Send text.

Text size This parameter indicates the size of the email to be sent. This parameter is not available with the Receive function. The application will retrieve the first available email on the POP3 server, whatever its size may be. This is the normally the email you would have sent with a Send text previously.

Use SMTP authentication

When your SMTP server requires authentication, check this checkbox and enter username/password.

Username Username for SMTP authentication.

Password Password for SMTP authentication.

The Email test measures send/receive time for email. You would normally set up one test to send an email and a second test to receive the email.

Email Receive

Setting Description

Server Your Email server. If you need to use a special port other than the default (port 110), then you can simply add it with a colon: server:port.

Subject This parameter allows you to specify which email to download from the server. You need to indicate the subject title of the specific email.

Note: Do not use the same user account for different tests that run at the same time. The server might not be able to handle multiple connections for the same user at the same time.

GPRS Attach + Detach

Setting Description

Attempts This parameter allows you to indicate how many times you would like the application to test the attachment/detachment process. At the moment, only 1 attempt is allowed. Therefore, the field is not editable.

Timeout This parameter indicates the amount of time the application will wait for a positive response from the network. If there is no positive response from the network within this period, then the test has failed.

SwissQual recommends that you use the following test sequence for the GPRS Attach/Detach test:

1. Start with a GPRS Attach test

2. Then PDP Activation test

3. After this, you may include any other data tests, such as FTP or HTTP or Email etc.

4. Next, PDP Deactivation test

5. Finally, GPRS Detach test.

This recommended test sequence will give you a more complete and connected picture of the performance of the network.




46

PDP Activation and Deactivation It is recommended that the PDP Activation/Deactivation test be used in the following test sequence:

1. Start with a GPRS Attach test

2. Then PDP Activation test

3. After this, you may include any other data tests, such as FTP or HTTP or Email etc.

4. Next, PDP Deactivation test

5. Finally, GPRS Detach test.

This recommended test sequence will give you a more complete and connected picture of the performance of the network.

SMS Send

Setting Description

Timeout Timeout before the SMS is sent.

Number This parameter indicates the receiver’s phone number.

Direction • double sided: The test is meant to be used with 2 devices in a task and doesn’t need a number here.

• single sided: A number must be given, the task only contains the A-side device.

• back to sender: No number must be given, the number of the A-side device of the task is used.

SMS length Sets the number of characters to be sent in the message. Min. is 42 (sum of header and checksum trailer used by SwissQual), max. is 160.

Use custom text Check this option if you want to use a custom text instead of the default text.

Custom text Enter your SMS text here. The text entered will be truncated or replicated in order to fill the "body" part of the SMS, depending on the specified maximum SMS length.

Service preference Choose which service should be used to send SMS. If “Packet domain preferred” or “Circuit switched preferred” is selected the test tries to send it using this service but it may also be sent with another service.

SMS Receive

Setting Description

Service preference Choose which service should be used to receive SMS. If “Packet domain preferred” or “Circuit switched preferred” is selected the test tries to send it using this service but it may also be received with another service.

SMS Push

Setting Description

Request text Text needed for the corresponding service.




47

Setting Description

Validity Sets the Validity Period of the SMS message.

Max. send time Maximum allowed sending time for the SMS message.

Responses Number of expected responses. At least 1 response must be defined.

Type Defines the type of response. [SMS, MMS or BIO]

Size (bytes) Defines the size of the response. [0 = don’t care]

Content type Selection of the expected answer content type. Can be either in text or binary (hexadecimal) form.

Content "Can be text" or something in hex, for example, "2A".

MMS Send

Setting Description

Timeout Timeout before the MMS is sent.

Number This parameter indicates the receiver’s phone number..

Double-sided If checked, the test is meant to be used with 2 devices in a task and doesn’t need a number here.

Picture This parameter indicates which file to send for the MMS Send test.

Delivery Report You can indicate whether or not you want the test to wait for a delivery report.

Protocol Specifies the transmission protocol for the message, that is, WAP or HTTP

Note: You can not use this protocol with QualiPoc.

MMS Receive

Setting Description

Timeout The receive timeout is the period to wait for an incoming message.

Protocol Specify whether WAP or HTTP is used to receive the message

Important: MMS receive test can not be mixed with other data tests. You can only have one MMS receive test per session.

WAP

General Tab Please refer to the HTTP Browser test.

QualiPoc Tab Please refer to the HTTP Browser test.

Note: The WAP gateway as well as the dialup settings (APN, username, password, etc.) has to be configured in the Provider & Access Point configuration.




48

Video over IP Job For a full description on the streaming service tests, see the Manual – Streaming Service Test.pdf document.

Forcing Job The forcing job is a functional job and can not be used for measuring or testing. It allows having forcing function at job level rather than task level. This is especially useful if in the same task different band/technologies should be used.

Note: In a task the forcing job only applies to the A-side device.

Tests

Static Forcing Static forcing is used to force a trace-capable mobile phone (for example, Nokia 6680) to a certain technology and/or band. It is call “static” because the forced technology, band can not be changed during the execution of a task.

Upload Job

The upload job is used to instruct a unit to upload its result files. Like this, uploading can be scheduled.



Chapter 8 | Campaign and Task Configuration CONFIDENTIAL MATERIALS

49

8 Campaign and Task Configuration This chapter describes how to configure campaigns and tasks. A campaign contains one or more tasks that you can start simultaneously. If the tasks in a campaign are not scheduled, then all tasks run in parallel at the same time. Each task contains one or more jobs while each job contains one or more tests.

Campaign

Setting Description

Campaign name Display name

Execution type • Asynchronous: NQComm starts each task as if the task were not part of a campaign. The campaign is only a wrapper to provide an easier start for multiple tasks.

• Multichannel: All B-side devices must be on the same unit. The first device that completes the configuration call successfully triggers the remaining devices in the campaign to start. Use this execution type to speed up the campaign start in regions where network coverage is low.

Available tasks List of tasks that are not in a campaign.

Tasks in campaign List of grouped tasks in the campaign.

Note: The campaign list view automatically refreshes. If you want, you can change the refresh timeout.

Task

Setting Description

Task name Display name

Customizable ID Can be left blank; in this case the ID will be set automatically. A pure benchmarking setup involves multiple systems each with a separate TestManager installation. In order to be capable of bringing the result data together, customizable IDs for devices and tasks can be used. As these two IDs are part of the measurement result file names, the corresponding files can be collected and evaluated. Using these IDs in a customized way means putting a meta layer over multiple Benchmarker systems.

Device Definition of the device(s) to be used in that task. The selection contains device groups as well on top of it if there are some.

Important: You can use device groups instead of single devices. If such a group is used, you only need to enter it for the A-side. The B-side will be handled automatically. Once a task containing a device group is started, the task will be multiplied and started in “single-mode” per device like a normal task would, too. Device groups can not be used for jobs that needs access points unless all devices of that group use the same provider.

Forcing Defines the static forcing to be used.

Data recording Defines the data recording profile to be used.




50

Setting Description

Schedule A task can be scheduled. If this is the case, a special validation will be done to evaluate if there are possible collisions at run time with other tasks that use the same device(s). If found, a warning will be shown.

Important: While saving, collisions are only warned. When trying to start a task that has a scheduling collision, this will not be possible.

Duration The task duration defines, how long the task will run.

• This value limits strictly the execution of all jobs in that task.

• Duration 00:00:00 means the task will run infinitely.

• Every scheduled task must have a duration.

Data reduction duration The time that is used by the unit to reduce the data before the results are transferred. This duration is calculated automatically based on the unit type and the corresponding percentage setting in the unit profile.

Important: If the percentage in the unit profile for the data reduction calculation is changed, all tasks must be edited and saved again in order for the new profile setting to be applied.

Upload duration QualiPoc devices need time to upload the results after the task. The default duration can be set in the QP unit profiles.

• This value only applies for QualiPoc devices. All other devices have a value of 00:00:00 in that field.

• When adding a task the profile upload duration is used if the task upload duration is 0. If the profile upload duration is 0, too, then no change is done and no warning is shown. Automatic change and warning if needed.

• When adding a task with task upload duration > 0 and a running upload task is found, a warning is shown. No automatic change, only warning.

• When editing a task, no warnings or changes are done whatsoever to the task upload duration. No automatic change, no warning.

• When starting a task with task upload duration > 0 and a running upload task is found, a warning is shown. No automatic change, only warning.

• When starting a task with task upload duration = 0 and no running upload task is found, a warning is shown. No automatic change, only warning.

The task upload duration is added to the task duration for schedule collision checking.

Cycles Each cycle represents a complete measuring session.

• This value limits strictly the execution of all jobs in that task.

• Cycles 0 means that the task execution is not limited in terms of repetitions.

• If the value is set, the task will stop after the defined number of sessions.




51

Setting Description

Job execution Best Effort

In general, multiple jobs per task are allowed except for QualiPoc devices which only support one job per task. If the jobs do not have window timing, the jobs are started in best effort manner, that is, each job is executed as fast as possible based on the location of the job in the sequence. This job execution type will write the measurements results into one file (per device). For further information about the window concept please refer to DVE - Window Handling.doc.

Job execution Fixed window

Multiple jobs per task are allowed except for QualiPoc devices. All jobs in the task must have window timing. The jobs are executed in sequence or with Multi-RAB. Multi-RAB allows for the simultaneous execution of a voice window and a data window. So during a call, a data test can be performed. Multi-RAB is only supported by a selected range of devices. If you use Multi-RAB with a device that does not support this feature, the dual dialup fails. When this type is active a link below the drop-down list will show up. Click it to edit the necessary timings of the jobs in that task. For further information about the window concept please refer to DVE - Window Handling.doc.

Fixed window task configuration: When the job execution type of a task is “Fixed window”, a link appears below the drop-down list. Clicking on it will bring you to another page where the timings for all jobs in the job-list can be edited.

These timings are necessary to control when exactly a measurement is performed. So for example in a Multi-RAB scenario the call should start right away but the data test should be started 1 minute later to simulate a user that needs to lookup some data on the internet while he is on the phone.

On the following pages there are some examples of configurations and what they mean also what causes the problems and how they can be solved.

For further information about the Windowing Concept please refer to DVE - Window Handling.doc.

Note: The Gantt chart will only show as many windows as necessary for each job to detect all possible overlapping.

Additional Job Settings Fixed window tasks require a few more settings to each job defined in the task. These settings are used to define when exactly a job is executed in relation to the start of the task.

Setting Description

Initial window delay This field defines the delay until the first window of the current job is started. This value is used to control that no windows of different jobs overlap. For Multi-RAB jobs this time can be used for example to delay a speech job until the data job is ready (transferring data).




52

Setting Description

Pause after consecutive windows

This is the pause after all consecutive windows have been executed. No windows of the current job are executed until this pause is over. The reason why only the first job’s pause can be edited is as follows: All jobs in a task have to repeat themselves as they started, that is, if these pauses would be editable for all jobs, it would be possible to configure a scenario that is always changing. This would lead to unexpected overlapping after a certain time. So for all, except the first, jobs this time is calculated according to the set “Initial window delay” and “consecutive windows”.

Consecutive windows Indicates how many windows should be executed in consecutive order. There is no pause between consecutive windows.

Window This field is for informational purpose only. It shows the window duration of the current job.

Task with optimal arrangement of the jobs (windows) The following configuration was achieved by clicking on the “Arrange jobs sequentially” link. It will arrange all jobs so they are optimal distributed and don't have a collision/overlapping.

Figure 8-1 Jobs arranged sequentially

In a Multi-RAB scenario the jobs can overlap.




53

Figure 8-2 Overlapping Multi-RAB jobs

The next screen shot shows an example of a configuration where two data windows are parallel to the same speech window. This is not possible due to representational limitations in NQDI. Only one data window per speech window is allowed in Multi-RAB.

Note: The data window is always the master window/session in NQDI.

Figure 8-3 Two data windows in parallel with the same speech window

The next figure shows the same problem as the one before, just that there is a second, consecutive window during the same speech window. It is a little bit hard to see on the screen shot, but the second job has 2 consecutive windows defined.

Figure 8-4 Same as Figure 8-3 except that second job has two consecutive windows

The following scenario shows that the first window of the “Streaming PC NoRef (QT)” job has an overlapping




54

with 2 “Nina+” windows. This is not valid since NQDI uses the data window as master (and it can have only one speech window at the same time).

Figure 8-5 Stream PC NoRef (QT) job with two overlapping Nina+ windows

If forcing jobs are used, it may look like the following figure. The forcing jobs do not repeat at the same rate as the other jobs, they are executed every other cycle. The easiest way to achieve such a configuration is to click on “Arrange jobs sequentially”, then choose the “Pause after consecutive windows” for the forcings and change the “Initial window delay” of the second forcing to a multiple of the proposed value. Then click the refresh button above the chart.

Figure 8-6 Windows for forcing jobs

Jobs Tab You can add jobs to the task, change their execution order or delete them from the list. By clicking on the job, its details are displayed in the top section of this tab.

Setting Description

Job Selection of the job to be added to the task.

Access point Per job definition of the access points to be used.

Application Per job definition of the application type to be used, for example, IMS applications.

Advanced Tab

Setting Description




55

Setting Description

Triggers in general • Time trigger (Schedule on top page) • Speed trigger • Location trigger • Service state trigger

The task is only executed if the requirements of all triggers are fulfilled. The time trigger, better known as schedule, is special because of its importance - that's why it's positioned in the top part of the view.

Data connection Defines whether the data connection device is treated as a dialup device (PPP) or a network adapter (NDIS).

• PPP: Dialup network entry • NDIS: Network Driver Interface Specification

Task List You can edit, delete, start, stop, and reset the tasks in idle status in this list, whereas you can only view tasks that have a different status in read-only mode. The statuses of the tasks can be separated in the task status and the measurement file status. Each of them is displayed with a separate indicator.

Important: If an error occurred during the execution of the task and it was not stopped correctly, there is still the possibility to reset the status by clicking on the reset-icon. Please use this option carefully and only if you are sure that the job configured in the task is not running anymore on the device(s). Otherwise, a conflict may occur on the device(s). The reset either puts the task in idle or running mode, depending on its last status at the moment of the reset action.

Tasks with device groups are “master tasks” and will create as many “child tasks” as there are devices in the used group. Any child task can be handled individually as long as the master task is in a running state. As soon as the master task is stopped, all child tasks are stopped as well and deleted.


Triggers Triggers serve the goal of starting or stopping a measurement based on certain conditions.

Time Trigger (Schedule)

Repeat Task All types of scheduling (following sections) have the common feature “Repeat task”. If enabled, the task is repeated every x hours for the defined duration. The maximum duration is 23 hours and 59 minutes to prevent overlapping if the schedule type is “Daily” or “Weekly”.

Once If a task should run at a certain time and only once, this scheduling type is sufficient. The task will only run once at the specified date and time (unless “Repeat task” is checked).




56

Daily If you wish to perform tasks daily, every other day or every 4th day then choose “Daily” as “Schedule type”. It will allow you to specify the interval in which the tasks are executed.

Weekly Weekly allows you to perform tasks only on selected days of the week. For example, you want to measure the performance of your network for a specific type of test only on the weekends over a longer period.

Important: The first day of the week depends on the regional settings on the system where the measurements are executed. This is valid for all unit types. In MS Windows, the current setting can be found in the registry under: HKEY_CURRENT_USER\Control Panel\International > iFirstDayOfWeek 0 = Monday 6 = Sunday

Delayed The actual start of the task can be delayed with this scheduling type. After the user clicks on the start button, the task is delayed by the specified amount of time. This can be a very useful feature if you have a test scenario where for example Task 1 runs first, then Task 2 (10 minutes later), Task 3 (20 minutes later), etc. and these tasks have to be performed randomly, not scheduled.

Speed Trigger

Setting Description

GPS signal valid

Speed threshold [km/h] Logging continues until the speed drops below this threshold.

Measurement stop timer Time after which measurements are stopped once the speed threshold has fallen below the threshold.

Measurement start timer Time after which measurements are continued once the speed threshold has been passed.

GPS signal invalid

Speed threshold [km/h] In case we lose GPS signal, for example, inside a tunnel, the latest valid speed will be checked. If it is over the threshold, logging continues, otherwise the measurements are stopped

Measurement stop timer We need to differentiate between sudden GPS signal loss and other situations (ex tunnels). Therefore we use this timer.

If the speed stays below the speed threshold for the predefined period of time, measurements are stopped.

Example:

in a covered train station for example, in absence of a GPS signal and even if the last valid speed was above the threshold, measurements can be stopped once this timer is elapsed.

Note: If the timer values are set to 00:00:00, they won't have any impact. This means the measurements are stopped/started immediately when thresholds are reached.




57

Forcings

Static Forcing Static forcing is used to force a trace-capable device to a certain technology and/or band. It is called “static” because the forced technology/band and other settings can not be changed during the execution of a task.

Setting Description

Forcing name Display name

Technology The technology can either be forced or set as preferred.

Bands Tab

Setting Description

GSM Defines if certain bands of GSM are forced.

WCDMA Defines if certain bands of WCDMA are forced. The listing of the bands is not done after the band frequency but corresponding to the operating band number: http://en.wikipedia.org/wiki/UMTS_frequency_bands

ARFCN Tab

Setting Description

Forcing Defines if this forcing detail is used or not.

Channel The forced channel.




58

UARFCN Tab

Setting Description

Forcing Defines if this forcing detail is used or not.

Frequency The forced frequency.

Use scrambling code Defines if the scrambling code is forced or not.

Scrambling code The actual scrambling code to be used.

Applications Applications can be used in the task to execute jobs, for example, IMS applications.

Setting Description

Application name Display name

Application type Only supported types are listed.

Connection Select all necessary items needed for connectivity, for example, a server and a login profile.

Data Recording Profiles Data recording profiles can be used in the task in order to obtain more measurement data than normal (= bigger files) and/or to reduce the collected data (= smaller files). If no data recording profile is applied, then all data are collected as usual.

General Tab

Setting Description

Keep original data Check this box to keep a file as collected without application of the recording profile (filename extension *.sqzo (like original)). With that, in case of significant reduction, a later in-depth analysis remains possible.

Measurement file size reduction

Allows you to choose the relevant options during replay in NQView.

Application Tab

Setting Description

PCAP file generation Select if you want to produce files in PCAP format of the TCP transactions for later analysis. PCAP files can be collected per

• Session: The file includes the whole measurement session.

• Measurement: A file is created per measurement.

If disabled, the SnapLen is not considered, no PCAP file is made.




59

Setting Description

SnapLen [bytes] Number of bytes of header data to be captured per packet. This option can greatly reduce the size of the PCAP file. With this value set to 0, the full packet is captured.

IP protocol information Keeps IP and TCP trace information.

Audio recordings Keeps the original audio recording files.

Video recordings Keeps the original video recording files.

SQuad details Includes the SQuad details

Device Tab

Setting Description

HSDPA packet details Select if you want to have detailed information about every HSDPA Transport Block (TB) transferred.

Note: With this option enabled the MF file is inflated significantly.

Averaging Defines the values that you want to average as well as sets the time frame for the averaging. To obtain information on each change, select the Details option .When you select this option, data might be written more frequently than the averaging time interval.

Scanner Tab

Setting Description

Excluding of data Define what kind of scanner data is excluded from the measurement file.

Averaging At the moment, this setting is not applicable. As the scanner of a Benchmarker system is running permanently, it can't receive settings per task. The scanner broadcasts its results on a permanent basis. The individual tasks are "observers" of that scanner signal and simply include the data in their measurement files. This option is a subject of change in later versions.

Level Tab

Setting Description

Data collection level The level is a general setting all messages that are collected are associated with a certain level. Choose the desired level in the drop down list. Refer to the NQDI user manual for further information about it.

Note: The level has to be less or equal than the smallest event level in the selected events. Selecting an event with a level less than the general level doesn't make sense - the data would be included anyway because of the general data collection level.




60

Setting Description

Keep data around events

If the general data collection level is set to a low level like 1 or 2 but more detailed information around certain events (for example, dropped call) is needed then choose that event, the desired range (Unit type and scope) and data depth (level) around it and add it to the list at the bottom. (In situation of overlap of the ranges of two actual events the highest level (more data) prevails).

Device Groups Putting together devices in groups is helpful when the same task is to be executed on different devices. Like this, the task definition has only to be done once.

Device Overview

This simple view shows what devices are used in what tasks.



Chapter 9 | Database Administration CONFIDENTIAL MATERIALS

61

9 Database Administration The database administration can be used to create, update, delete, and backup TestManager databases. All SQL scripts needed for the creation and update process are located in the sub-directory “DBScripts” in the folder of the executable of the TestManager.

Connect to Database Server To access the database administration form, go to the “Overview” and click “Change database”. This will take you to the database login, now click the link “Database administration (create, update and delete)”. Now enter the server details and click on <Connect>. After the connection to SQL server was successfully established the other fields are enabled.

Create a New Database To create a new database, enter the name and click on <Create>.You can not leave the name blank. When creating a database, follow consistent naming conventions and ensure that each name uses allowed characters. Names can not use characters such as / : * # ? “ < > |. As a general rule, use alphabetic and numeric characters and avoid using symbol characters.

Restore an Existing Database

You can restore databases from backup files (.bak). Enter the name you want in the corresponding field and select the restore file in the other browsable field. The file will be uploaded to the host where TestManager is running and executed.

Important: TestManager and the MS SQL server must be installed on the same machine, otherwise the restore functionality is not usable. If a database with the selected name already exists, all data will be overwritten by the restore! Existing connections of other users will be closed, the existing database will be put in single user mode before the restore happens.

Update, Delete or Backup a Database To update a database to a newer version (usually more fields for more functionality were added) or to delete a database, select a database from the drop down list. To update, choose the version to update to and click <Update>. To delete, just click the <Delete> button. To backup click the <Backup> button. Once the operation is done, a message box will show if it was successfully or what kind of error occurred.

Important: TestManager backs up the selected database before an update action. If problems during the update occur, a full restore is possible.

Note for Database Backup Since the backup is performed with functionality of the SQL server some restrictions apply. In other words the SQL Server writes the backup file and needs access to the given directory.

By default, the backups are saved into the default backup directory of the SQL server.

If needed, the backup directory can be changed. Keep in mind that it must be a local folder on the machine where SQL server is installed (limitation of SQL server). Change it as follows:

• Open the GeneralSettings.xml file located in the C:\Documents and Settings\All Users\Application Data\SwissQual\Diversity\NQTM\settings directory

• Then add or modify the tag “<DBBackupPathOnSQLServer>” so it contains the UNC string to a shared



Chapter 9 | Database Administration CONFIDENTIAL MATERIALS

62

directory where the SQL Server has access to or a directory on the SQL Server itself. See the example below for details.

Save the XML file and restart the TestManager Service.

GeneralSettings.xml example:

<XMLConfigurationBasePath> ..\Configuration </XMLConfigurationBasePath>

<DBBackupPathOnSQLServer>\\computername\shared dir </DBBackupPathOnSQLServer>

</Paths>



Chapter 10 | Special Views CONFIDENTIAL MATERIALS

63

10 Special Views This chapter describes the simplified drive test views that are available in TestManager.

Drive Test View The Drive Test view is a simplified TestManager view with limited interactions and larger font.

• To access the drive test view, open a browser and go to the following URL:

http://<IP of TM installation>:8080/?drivetest

System Status View The System Status view is a colour-coded view where green indicates that the system is working properly and red indicates an error. If the view is red, the driver need to call the home base for support.

• To view the system status you can use the following URL:

http://<IP of TM installation>:8080/?systemstatus

Note: If you want to change the states that cause this view to turn red, contact SwissQual support.



Chapter 11 | TestManager Settings CONFIDENTIAL MATERIALS

64

11 TestManager Settings This chapter describes the following configuration files which you can use to specify the settings for TestManager.

• GeneralSettings.xml: Contains the system wide settings in XML format. TestManager loads this file at the service start before the database is connected.

Note: Some of the values in this file are deprecated because the values have been transferred to the [dboTM].Settings table.

• UserSettings_<username>.xml: This file contains the settings for each user in XML format. TestManager loads this file when a user logs in and before the database is connected for the user session.

• <dboTM>.Settings: Table in the TestManager database that contains the settings that are applied after the database connection has been established. New system-wide settings in future release will be stored in this table instead of the GeneralSettings.xml file.

The following sections only describe the more important TestManager settings that you can customize.

GeneralSettings.xml File This configuration file is in the following location on the PC that contains TestManager:

C:\Documents and Settings\All Users\Application Data\SwissQual\Diversity\NQTM\Settings

The following XML schema defines structure and the content of this file:

C:\Program Files\SwissQual\Diversity\NQTM\Specifications\NQTMSettings.xsd

Each file contains annotations to explain some of the settings, such as the following values:

• Single and Multi-User modes, including automated logon for TestManager in single user mode

• Server settings, for example, the listening port

• Refresh intervals for lists

UserSettings_<username>.xml This configuration file is in the following location on the PC that contains TestManager:

C:\Documents and Settings\All Users\Application Data\SwissQual\Diversity\NQTM\Settings

The following XML schema defines the structure and content of this file:

C:\Program Files\SwissQual\Diversity\NQTM\Specifications\NQTMSettings.xsd

Each file contains annotations to explain some of the settings, such as the following values:

• Username and password

• Initial view after you log in, for example, the Unit Overview, Single Unit Overview, the Campaign list, and so on

• Number of units in each row in the overview You can use this value to display the size of a Benchmarker system as well as to optimize the display according to your monitor size

Single User Mode By default, the UserSettings_admin.xml file contains the user information. If you change the value of the LogoSequence node in the GeneralSettings.xml file to "AdminAutoLogon", TestManager automatically logs



Chapter 11 | TestManager Settings CONFIDENTIAL MATERIALS

65

the user on as an administrator.

Multi-User Mode If you want to restrict TestManager access to users with a UserSettings_<username>.xml file, change the value of the LogonSequence node in the GeneralSettings.xml file to "NoAdminAutoLogon".

To add another user, duplicate the UserSettings_admin.xml file, add the relevant user information to the file, and then add the username to the filename, for example, UserSettings_<username>.xml.

[dboTM].Settings Table This table only contains one record that has the following settings:

• GPSLeapSeconds: Whenever IERS (http://iers.org) changes the GPS leap seconds, SwissQual modifies this value with the next TestManager database update. If you do not want to install this update, you can manually edit this value. For more information on GPS leap seconds, go to: http://en.wikipedia.org/wiki/International_Earth_Rotation_and_ Reference_Systems_Service

Important: If you enter an incorrect value, you can render your measurement data useless.

• DisableCampaignCRC: Disables the checksum calculation during the campaign export process if "True". "False" is not recommended.

• ShowCustomID: Set this value to "True" to use custom ID parameters for devices, tasks, and campaigns. The custom ID is shown as a column on the corresponding list views. The default value of "False" does not display this column.

http://iers.org/

http://en.wikipedia.org/wiki/International_Earth_Rotation_and_%0bReference_Systems_Service

http://en.wikipedia.org/wiki/International_Earth_Rotation_and_%0bReference_Systems_Service



Chapter 12 | Troubleshooting CONFIDENTIAL MATERIALS

66

12 Troubleshooting This chapter describes how to troubleshoot problems that you might encounter when you use TestManager.

General

Log Files and Backups of the Database For best results, include the following files when you open a support request for TestManager:

• C:\Documents and Settings\All Users\Application Data\SwissQual\Diversity\Log\ NQTM.log

• C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Backup \<yourDBname>.bak You can create this TestManager database backup file with the SQL management console or with TestManager database administration.

• C:\Program Files\SwissQual\Diversity\NQTM\NQTM_Service.elf

Note: This file is only present if the error could not be written to the NQTM.log file, for example, during the TestManager startup.

At Startup TestManager verifies if the necessary files and settings are available present during the startup process.

If you encounter error or warning messages during this process, you can view this information after you log in to TestManager.

Important: If you click Continue using the TestManager, be aware that the TestManager might not work correctly.

If you want to solve the problem, stop the TestManager Windows service, that is, NQTM_Service and then perform the necessary actions, for example, install the missing software component. To verify the solution, restart the TestManager Windows service and log in to TestManager.

To stop and start the TestManager Windows service 1. On the Start menu, click Control Panel, double-click Administrative Tools, and then double-click

Services.

2. In the list of services, right-click NQTM_Service, and click Stop or Start.

License If the computer does not contain the proper TestManager license, obtain the license from SwissQual support, stop the TestManager Windows service, install the license, and then start the TestManager Windows service. For a description on how to stop and start this service, see the "At Startup" section. For information on how to install the license, see the Installation - Diversity Platform and Applications.pdf document.

Possible Error Messages

MSXML Errors Microsoft “MSXML 4.0 SP2 Parser and SDK” is not installed on the TestManager Server.



Chapter 12 | Troubleshooting CONFIDENTIAL MATERIALS

67

Parser error message: Class not registered, ClassID: {88D969C0-F192-11D4-A65F-0040963251E5}

TestManager requires these Microsoft XML Core Services to read XML files. If the parser has not been installed on your computer or if the computer has an older version, you need to install this software. For information on how to install the Microsoft XML Core Services, see the Installation - Diversity Platform and Applications.pdf document.

File Does Not Exist Error: Necessary file “C:\Program Files\SwissQual\Diversity\NQTM\ settings\DeviceCapabilities.xml does not exist.

If this file is missing, you cannot configure devices or start tasks correctly. If you cannot find the file on your computer, reinstall TestManager.

Schema is Not Valid File “C:\Program Files\SwissQual\Diversity\NQTM \settings\DeviceCapabilities.xml” does not support the XML specification. You may not be able to configure devices or start tasks.

Error: XML file does not match specification.

XML file: “C:\Program Files\SwissQual\Diversity\NQTM \settings\DeviceCapabilities.xml”

XML spec: “C:\Program Files\SwissQual\Diversity\Specification \SwissQual\Device\DeviceCapabilities.xsd”

Parser error message: The attribute ‘id’ on this element is not defined in the DTD/Schema.

These errors indicate that XML file cannot be validated by the relevant schema (XSD) file. To solve this problem, you need to take the following actions:

• Uninstall TestManager • Empty the contents of the C:\Program Files\SwissQual\Diversity\NQTM folder • Reinstall TestManager

During Configuration of the System

PCM Beeps and Then Shuts Down If the PCMs are powered by the car battery and the battery voltage drops below the threshold value for a specific amount of time, the Diversity System automatically shuts down to protect the CBM. These values are part of the unit configuration in TestManager.

If you use the Diversity System in an office environment, you can specify a threshold voltage of “0” to disable the automatic shutdown.

Important: You must re-specify this value if you move the system into a vehicle.

Manual - NetQual - Test Manager

Documents

Transcript of Manual - NetQual - Test Manager