Manual - Diversity Data and Messaging Tests

SwissQual...
Data and Messaging Tests

Manual
Manual
Test & Measurement
Data and Messaging Tests 01
The firmware of the instrument makes use of several valuable open source software packages. For information, see the "Open
Source Acknowledgement" on the user documentation CD-ROM (included in delivery).
Rohde & Schwarz would like to thank the open source community for their valuable contribution to embedded computing.
SwissQual AG
Allmendweg 8, 4528 Zuchwil, Switzerland
Phone: +41 32 686 65 65
Fax:+41 32 686 65 66
E-mail: info@swissqual.com
Internet: http://www.swissqual.com/
Printed in Germany Subject to change Data without tolerance limits is not binding.
R&S is a registered trademark of Rohde & Schwarz GmbH & Co. KG.
Trade names are trademarks of the owners.
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. SwissQuals liability for any
errors in the documents is limited to the correction of errors and the aforementioned advisory services.
Copyright 2000 - 2014 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 ExplorerTM, Diversity RangerTM, Diversity UnattendedTM, NiNA+TM, NiNATM, NQAgentTM, NQCommTM, NQDITM, NQTMTM,
NQViewTM, NQWebTM, QPControlTM, QPViewTM, QualiPoc FreeriderTM, QualiPoc iQTM, QualiPoc MobileTM, QualiPoc StaticTM, QualiWatch-MTM, QualiWatch-STM, SystemInspectorTM, TestManagerTM, VMonTM, VQuad-HDTM are trademarks of SwissQual AG.
The following abbreviations are used throughout this manual: R&S___ is abbreviated as R&S ___.
SwissQual...
Contents
Contents
1 Introduction............................................................................................ 7
1.1
Overview of a Measurement Cycle.............................................................................. 7
1.2
Reference Documentation............................................................................................9
2 Capacity Test........................................................................................10
2.1
Basic Function............................................................................................................ 10
2.2
Result Analysis........................................................................................................... 11
3 Email Receive Test...............................................................................13

3.1
Basic Function............................................................................................................ 13
3.2
Results Analysis......................................................................................................... 13
4 Email Send Test................................................................................... 15

4.1
Basic Function............................................................................................................ 15
4.2
5 FTP Test................................................................................................ 17
5.1
Basic Function............................................................................................................ 17
5.1.1
Impact of Send Buffer Size Parameter Value..............................................................18
5.1.2
FTP Over SSL...............................................................................................................18
5.2
6 GPRS Attach Test................................................................................ 21

6.1
Basic Function............................................................................................................ 21
6.2
7 GPRS Detach Test................................................................................23

7.1
Basic Function............................................................................................................ 23
7.2
8 HTTP Browser Test.............................................................................. 25

8.1
Basic Function............................................................................................................ 25
8.2
9 HTTP Transfer Test.............................................................................. 28

9.1
Basic Function............................................................................................................ 28
9.2
Manual Data and Messaging Tests 01
SwissQual...
Contents
10 IPERF Test............................................................................................ 31
10.1
IPERF Server Configuration....................................................................................... 31
10.2
Basic Function............................................................................................................ 32
11 MMS Receive Test................................................................................33

11.1
Basic Function............................................................................................................ 33
11.2
11.3
Trigger Points MMS Receiver.................................................................................... 36
12 MMS Send Test.....................................................................................37

12.1
Basic Function............................................................................................................ 37
12.2
Phone Configuration...................................................................................................37
12.3
12.4
Trigger Points MMS Sender....................................................................................... 40
13 PDP Activation Test............................................................................. 41

13.1
Basic Function............................................................................................................ 41
13.2
14 PDP Deactivation Test......................................................................... 43

14.1
Basic Function............................................................................................................ 43
14.2
15 Ping Test............................................................................................... 45
15.1
Basic Function............................................................................................................ 45
15.1.1
Maximum Duration........................................................................................................ 46
15.2
IPv6 Support................................................................................................................ 46
15.2.1
Forcing Diversity to Use a Specific IP Version for a Test..............................................48
15.2.2
IPv6 Address Format.................................................................................................... 49
15.2.3
IPv4 and IPv6 Traffic in NQDI....................................................................................... 49
15.3
Result Analysis........................................................................................................... 50
16 Ping Trace Test.................................................................................... 52

16.1
Basic Function............................................................................................................ 52
16.2
17 SMS Receive Test................................................................................ 55

17.1
Basic Function............................................................................................................ 55
SwissQual...
17.2
Contents
18 SMS Send Test..................................................................................... 57

18.1
Basic Function............................................................................................................ 57
18.2
19 UDP Downlink Test.............................................................................. 59

19.1
Basic Function............................................................................................................ 59
19.2
SwissQual...
Contents
SwissQual...
Introduction
Overview of a Measurement Cycle
1 Introduction
This document describes the Data and Messaging tests available with the Diversity
Measurement Units, SwissQuals Subscriber Experience Management system for
audio, data, messaging and video quality.
Each test is handled in a separate chapter, consisting of a description of the test flow
and the result analysis. Analysis is presented with NQDI, SwissQuals post processing
application. Were necessary and appropriate, in depth detail information is provided as
well. The appendix outlines general information as well other kind of nice to know
descriptions.
This document does not describe how to setup Diversity nor does it deal with configuring the data and messaging tests. These topics are provided in
Manual NetQual - NQView.pdf.
1.1 Overview of a Measurement Cycle

In a Diversity measurement cycle, data sessions are separated by idle periods. Each
data session contains one or more tests that are separated by pauses. You can specify
the duration of the idle periods for the data sessions and pauses between tests in
NQView.
At the end of each test, a brief pause occurs during which clean-up is performed. In
some cases, a pause is also required before a test starts, for example to detach a
device from the network. You cannot configure the length of the clean-up pause for a
test in NQView.
SwissQual...
Introduction
Overview of a Measurement Cycle
IDLE
DATA SESSION
GPRS
HTTP
FTP
P
P
P
Attach
Get
Get
Preparation
Test
Clean Up
IDLE
DATA SESSION
IDLE
A data session contains a series of one

or more tests that are separated by
pauses.
A test session includes initial preparation

(if required), the test, and a post-test
clean-up phase
GPRS Attach test

Fig. 1-1: Overview of the idle times and pauses in a measurement cycle
P = Pause
The preparation phase typically lasts approximately 100 ms and is therefore not significant.
This phase might take longer for the GPRS attach test if the test requires a preliminary
detach operation. Furthermore, Windows 7 can introduce instabilities into the test.
The duration of the clean-up phase can vary based on the type of test. The clean-up
phase of the following test types lasts is typically 1.5 seconds:
Ping
GPRS Attach
GPRS Detach
PDP Activation
PDP Deactivation
SMS Send
SMS Receive
The clean-up phase for the following test types typically lasts 3 seconds:
HTTP Transfer
HTTP Browser
FTP
Capacity
IPERF
SwissQual...
Introduction
Reference Documentation
Ping Trace
UDP
Email
MMS send
MMS receive
In the worst case, the duration of the clean-up phase might be twice as long.
The NDIS option for a task introduces an additional pause after the connection has
been established. This pause is the "NDIS post connection delay" and has a duration
of 500 ms.
Fig. 1-2: NDIS post connect delay in NQDI
Although you can change the duration of the clean-up phase and the NDIS post connect delay with Windows registry keys, SwissQual strongly recommends that you use
the default values to avoid issues with trace recording or test success rate.
1.2 Reference Documentation

Reference
Document
[1]
Manual NetQual - NQView.pdf
[2]
Manual NQDI - KPI Users Guide.pdf
SwissQual...
Capacity Test
Basic Function
2 Capacity Test
The Capacity test establishes multiple simultaneous peer connections for data transfer
to optimize network throughput.
Round Trip Time (RTT) and TCP Receive Windows Size (RWin) define the maximum
achievable throughput for a TCP/IP based connection. Modern high bandwidth networks contain diverse networking conditions and use congestion control. In such networks, the combination of RTT and RWin might not be fully optimized, which can result
in sub-optimal network utilization and lower throughput values than expected.
The Capacity test focuses on network stressing for the time period that you define.
Typically this period lasts from 30 to 90 seconds. A successful test calculates the application throughput when the test duration elapses. A test fails if the data transfer completes before the test duration elapses or when the transfer is interrupted.
Even though each connection in the Capacity test is still limited by RTT and RWin, the
sum of the multiple connections results in full network utilization.
2.1 Basic Function

The test configuration requires you to define a set of HTTP URLs. The target files,
which are transferred simultaneously during the test, can reside on different servers.
To avoid incomplete and aborted transfers during the duration of the test, use files that
are larger than 1 GB in size.
10
SwissQual...
Capacity Test
Result Analysis
Start
Data Transfer 1...n
Stop
Data Transfer 1...n
Test Duration
Data Transfer 1 (e.g. http://server1.com/file1.dat)
Data Transfer 2 (e.g. http://server1.com/file1.dat)
Data Transfer n (e.g. http://server2.com/file2.dat)
Time
Fig. 2-1: Overview of a Capacity test
An error with one or more of the simultaneous transfers results in a test failure. Similarly, if one or more of these transfers successfully completes before the test duration
elapses, the test fails.
2.2 Result Analysis

The following table describes the Capacity test data that you can analyse in NQDI.
Table 2-1: Description of the Capacity test data
Value
Description
Msg Time
Time when results arrive
Host
List of the URLs for simultaneous transfer
Operation
GET (Download) or PUT (Upload) operation
Buffer Size
Protocol for the data transfer
Local file name
PUT operation uses local buffer (recommended size 32 kb)
Remote file
name
PUT operation only
Bytes Transferred
Intermediate number of bytes that have been transferred (Last Block = 0)
State
Possible states are: In Progress, Success, Failed
Final size (Last Block = 1)
11
SwissQual...
Capacity Test
Result Analysis
Value
Description
Error
Provides information on errors that occur during the test.
Throughput
If the test state is "In Progress", this value represents the intermediate throughput in
bytes/s, which is calculated as (number of bytes transferred since last message) / (time
needed).
At the end of the test, the state changes to "Success" or "Failed". If the state is "Success", the throughput value contains the overall throughput that has been calculated
as: (total number of bytes transferred) / (total time needed). If the state is Failed, the
overall throughput cannot be considered.
Fig. 2-2: Results of Capacity test
12
SwissQual...
Email Receive Test

Basic Function
3 Email Receive Test

This test measures the application throughput when receiving Email over the POP3
protocol. The message may contain additional attachment content to increase the
amount of transferred data.
Do not use the same Email account for different tests running at the same time
because the POP3 server cannot handle multiple connections for the same user at the
same time.
3.1 Basic Function

The test client connects to the specified POP3 server and authenticates itself with
username and password. In case an Email subject line has been defined, the client
goes through all messages within the mailbox and searches for the first Email matching the subject. This search time is accounted separately. Once the message is found
the transfer begins. The time used for transfer and the Email size is then being used to
calculate the throughput value. Once the Email has been downloaded, the operation
(delete Email; delete all Emails or leave Email is performed).
Client
Port 25
SMTP
Server
Throughput
calculated and
recorded
An email with a specific subject,

title is downloaded
Fig. 3-1: Email Receive Test Basic Function
3.2 Results Analysis

The post processing application NQDI shows the following data on the result analysis
tab sheet:
Table 3-1: Email Receive Test - Result Analysis
Value
Description
Msg Time
Current timestamp of the message
POP3 Server
Name or IP address of the SMTP server
Email Address
First part of the email address. (user)
Subject
Subject entered by the user.
13
SwissQual...
Email Receive Test

Results Analysis
Value
Description
Size
Total size of the email (7-Bit encoded).
Connect Duration
Time to connect to SMTP server
Search Duration
Time to find message with same subject line
Receive Duration
Time to retrieve email.
Message Number
The message number matching the subject line (if found)
Throughput
Throughput = Size / Receive Duration
Error Code
OK, if no error has occurred; error code if an error has occurred.
Fig. 3-2: Email Receive Test - NQDI Result Analysis Window
14
SwissQual...
Email Send Test

Basic Function
4 Email Send Test

This test measures the application throughput when sending Email over the SMTP protocol. The message may contain additional attachment content to increase the amount
of transferred data. Due to security issues, the test also supports SMTP authentication.
4.1 Basic Function
Client
Port 25
SMTP
Server
Throughput
calculated and
recorded
An email with or without attachment,

with a subject title is sent
Fig. 4-1: Email Send Test Basic Function

tab sheet:
Table 4-1: Email Send Test - Result Analysis
Value
Description
Msg Time
SMTP Server
Name or IP address of the SMTP server
Email Address
First part of the email address. (user)
Subject
Subject entered by the user.
Size
Total size of the email (7-Bit encoded).
Connect Duration
Time to connect to SMTP server
Send Duration
Time to send email
Throughput
Throughput = Size / Send Duration
Error Code
OK, if no error has occurred; error code if an error has occurred.
15
SwissQual...
Email Send Test

Results Analysis
Fig. 4-2: Email Send Test - NQDI Result Analysis Window
16
SwissQual...
FTP Test
Basic Function
5 FTP Test
The FTP test is used to test the FTP service availability and to measure the application
throughput for file download or file upload. The test is successful when the desired
operation (uploading or downloading) has succeeded.
5.1 Basic Function

Before a file can be transferred over FTP, a control channel connection has to be
established to the FTP server. This control channel is used to exchange FTP commands between client and server. Commands such as user account login, directory
changing and choosing the FTP operation are applied. When it comes to a FTP GET
(file download from server) or FTP PUT (file upload to the server) operation, the data
channel is being established, which then is used to transfer the raw file data.
Client
FTP Server
Control Connection
Data Connection
Fig. 5-1: FTP Test - Basic Function
17
SwissQual...
FTP Test
Basic Function
When encountering connection problems (no or closed connections) with the selected
Active/Passive mode, try using the other mode. Firewalls and NAPT may block or
close connections.
The control channel remains open during file transfer in order to exchange other commands (such as aborting the file transfer, and so on).
Active mode: The server connects to the client on a port provided by the client.
Passive mode: The client connects to the server on a port provided by the server.
Phase
Action
Duration
MsgLogTrace
Preparation
Start test
< 100 ms
FTP Get/Put Test Started
Test
FTP GET or FTP PUT
120 s max
Clean Up
Waiting for trace/clean

up
3s
You cannot change this
value
5.1.1 Impact of Send Buffer Size Parameter Value

A simple example is FTP Uplink. Let us say the phone has a 5 kb buffer. The first FTP
packet you send for an uplink has a size of 4096 bytes. The phone buffers this request
and immediately acknowledges receipt. It, then, starts to send the info. Meanwhile, the
software thinks that it just sent 4096 bytes in a fraction of a second. We have mitigated
the impact of this phenomenon by averaging over several seconds, but this does not
fully eliminate the impact of buffering. Besides, what we are measuring in the FTP
monitor is application throughput, and this is what we are reporting.
It is possible to have application throughputs exceeding the theoretical physical limitations due to enhanced phone and PC buffering techniques.
5.1.2 FTP Over SSL

FTP tests support FTP over SSL, that is, host addresses that start with FTPS and
FTPES.
To use FTPS or FTPES, use the following formats for the host address when you
configure the test:
ftps://ip_host_address
ftpes://ip_host_address
18
SwissQual...
FTP Test
Results Analysis
Fig. 5-2: FTP over SSL address in Data test dialog box in NQView
Note: The default command port number for FTPS is 990 and for FTPES is 21. To
use a different command port number, add the a colon (:) and the number to the
end of the address, for example, ftps://80.74.152.241:992, where 992 is
the custom port number.

tab sheet:
Table 5-1: FTP Test - Result Analysis
Value
Description
Time
Operation
Operation, either PUT or GET
Filename
Name of the file transferred or received
Throughput
As long as the state is listed as In Progress, this value represents the intermediate
throughput in bytes/s, calculated as (number of bytes transferred since last message) /
(time needed).
At the end of a FTP session, the state will change to Success or Failed. In case of Success, the throughput value contains the overall throughput calculated as: (total number
of bytes transferred) / (total time needed). In case of Failed, the overall value not calculated
FTP Host
Name or IP address of the FTP host
19
SwissQual...
FTP Test
Results Analysis
Value
Description
Bytes Transferred
Intermediate number of bytes transferred
State
In Progress, Success, Failed
Error
State message: OK if successful, otherwise the appropriate error text corresponding to

the error code.
Fig. 5-3: FTP Test - NQDI Result Analysis Window
20
SwissQual...
GPRS Attach Test

Basic Function
6 GPRS Attach Test

The objective of this test is to perform a successful GPRS attach to the mobile network. The test is successful if attaching to the network succeeded. As result parameter
the duration for attaching the device is being reported. Note that this test is for mobile
communication network devices only.
6.1 Basic Function

In a first step the device will check whether or not it is already attached to the network.
Client
Network
ATTACH ACCEPT
is sent, if the attach
is successful
Application attempts to attach

to GPRS network
Fig. 6-1: GPRS Attach Test Basic Function
If yes, it will perform a GPRS detach command and afterwards start with the actual
attempt to perform a GPRS attach.
Table 6-1: Timing of actions during a GPRS Attach Test
Phase
Action
Duration
MsgLogTrace
Preparation
Start test
< 100 ms
GPRSAttach Test Started
Preparation
Opening COM Port
0.5* s
Waiting for the DevMan MobFunc service
Preparation
Detaching device
60 s max
Performing action: Detaching device
Test
Attaching device
60 s max
Sending attach command [AT

+CGATT=1]
Clean Up
Waiting for trace/

clean up
1.5 s
value

NQDI shows the following data on the "Analysis" tab.
21
SwissQual...
GPRS Attach Test

Results Analysis
Fig. 6-2: GPRS Attach Analysis window (NQDI)
22
SwissQual...
GPRS Detach Test

Basic Function
7 GPRS Detach Test

The objective of this test is to perform a successful GPRS detach to the mobile network. The test is successful if detaching to the network succeeded. In case the device
is already detached, the test is successful as well, even though, no active operation
took place. As result parameter the duration for detaching the device is being reported.
Note that this test is for mobile communication network devices only.
7.1 Basic Function

In a first step the device will check whether or not it is already detached to the network.
If yes or in case the state could not be determined, it will perform a GPRS detach command. If already detached, the test will returns successful without performing any operation.
Client
Network
DETACH ACCEPT
is sent, if the detach
is successful
Application attempts to detach

to GPRS network
Fig. 7-1: GPRS Detach Test Basic Function
Table 7-1: Timing of actions during a GPRS Detach Test
Phase
Action
Preparation
Duration
MsgLogTrace
< 100 ms
GPRSDetach Test Started
Preparation
Opening COM port
0.5* s
Waiting for the DevMan MobFunc service
Test
Detaching device
30 s max
Performing action: Detaching device
Clean Up
Waiting for trace/

clean up
1.5 s
You cannot change
this value

NQDI shows the following data on the "Analysis" tab:
23
SwissQual...
GPRS Detach Test

Results Analysis
Fig. 7-2: GPRS Detach Analysis Window (NQDI)
24
SwissQual...
HTTP Browser Test

Basic Function
8 HTTP Browser Test

The HTTP Browser test is used to download a complete web page using the http protocol. For user consideration the test also supports the download of a single specified file
which will be downloaded with the http protocol as well. The test becomes successful
when the complete web page has been downloaded. The application throughput will
then be calculated.
It is recommended to perform the test with basic and static content. Web pages containing active scripting may not be supported by the applied browser instance and
therefore might lead into an error message. This will cause the test to timeout. Disable
the active Scripting functionality within Microsofts Internet Explorer settings.
8.1 Basic Function

The test implementation uses Microsofts Internet Explorer (IE) for navigating to and
downloading the web page. On test initialization the IEs temporary file folder (cache
files) is being emptied in order to prevent the loading the page from the local file system. Also, any existing IE browser instances are being closed to avoid non-involved
HTTP traffic. Afterwards the web page is being downloaded. Once the IE instance
reports the Navigation complete event the test is considered finished. Now, application throughput is calculated and number of images is counted.
Request for HTML page is sent
Port 80
Client
Web Server
Time and HTTP

throughput is
calculated and
recorded
HTML files and other related files, such as pictures, are

received
Fig. 8-1: Test HTTP Browser Test - Basic Function

tab sheet:
25
SwissQual...
HTTP Browser Test

Results Analysis
Table 8-1: HTTP Browser Test - Result Analysis

Value
Description
Msg Time
Current timestamp when result message has been written.
URL
Uniform Resource Locator
Number of
images
Number of images within the web page.
Number of
frames
Number of frames within the web page
Total Size
Total size of web page.
Throughput
Throughput = totalSize / (time between navigate and documentComplete)
Error
0 if successful; otherwise the error code
Browser
Name and version of the Web browser
26
SwissQual...
HTTP Browser Test

Results Analysis
Fig. 8-2: HTTP Browser Test - NQDI Result Analysis Window
27
SwissQual...
HTTP Transfer Test

Basic Function
9 HTTP Transfer Test

The HTTP Transfer test calculates the available throughput of an IP link. Unlike the
HTTP Browser test, the HTTP Transfer test is not a service test.
The HTTP Transfer test downloads or uploads a file with the HTTP protocol and then
calculates the application throughput after the file transfer is complete. The test also
calculates the intermediate throughputs during the download or upload phase.
Use a file of sufficient size for the IP link that you want to test.
9.1 Basic Function

Request for HTML page is sent
Port 80
Client
Web Server
Time and HTTP

throughput is
calculated and
recorded
Any file type can be transferred

Fig. 9-1: Test HTTP Transfer Test - Basic Function
By default, you cannot upload any type of file to the HTTP server. Instead, you need to
enable this feature for the directory on the HTTP server. You can either grant universal
access to the directory or require user name and password authentication.
Table 9-1: Timing of actions during an HTTP Transfer Test
Phase
Action
Duration
MsgLogTrace
Preparation
Start test
< 100 ms
HTTPTransfer Get/Put Test Started
Test
HTTP GET
45 s max
Clean Up
Waiting for trace/

clean up
3s
You cannot change

this value
28
SwissQual...
HTTP Transfer Test

Results Analysis

The post processing application NQDI shows the data in the following table on the
result analysis tab sheet.
Table 9-2: HTTP Transfer Test - Result Analysis
Value
Description
Msg Time
Time when result message is written
Host
URL or IP address of the HTTP server
Operation
GET (Download) or PUT (Upload) operation
Buffer Size
PUT operation uses local buffer (recommended size 32 kb)
Local file name
PUT operation only
Remote file name
Path and file name on the HTTP server
Bytes Transferred
Intermediate number of bytes that have been transferred (Last Block = 0)

Final file size (Last Block = 1)
State
Possible states are: In Progress, Success, Failed
Error
State message is OK if the test is successful, otherwise the error text corresponding
to the error code is displayed.
Throughput
As long as the state is listed as In Progress, this value represents the intermediate
throughput in bytes/s, which is calculated as (number of bytes transferred since last
message) / (time needed).
At the end of the test, the state changes to Success or Failed. If the state is Success,
the throughput value contains the overall throughput that is calculated as: (total number of bytes transferred) / (total time needed). If the state is Failed, the overall value is
not calculated.
29
SwissQual...
HTTP Transfer Test

Results Analysis
Fig. 9-2: HTTP Transfer Test - NQDI Result Analysis Window
30
SwissQual...
IPERF Test
IPERF Server Configuration
10 IPERF Test
The IPERF test measures the bandwidth and the quality of a network link.
This test requires an Iperf client and server.
10.1 IPERF Server Configuration

The Iperf server has the following requirements.
Iperf server version 2.0.5
Ports 5001..500X must be open

X: Number of simultaneous clients
UDP downlink is only possible in conjunction with UDP upload
Fig. 10-1: IPERF data test definition in NQView
Diversity supports the following additional parameters:
-u: Identifies UDP protocol (Default, only supported protocol)
-b<K/M>: Desired bandwidth, default is 1 Mbit/s

K or M identifies the unit
-t: Test time, default is 10 s
-l: UDP datagram size, default is 1470 Bytes
-d: Selects simultaneous up- and download
-r: Defines UPD upload followed by UDP download
-p: Server port to connect to, default 5001
-L: Tells the server which port to connect to for downlink path
Only required if you use the r or d options
31
SwissQual...
IPERF Test
Basic Function
10.2 Basic Function
Iperf client:
iperf -c host -u
UDP uplink
UDP downlink
Iperf server:
iperf -s -u
Fig. 10-2: Iperf Test - Basic Function
The IPERF test allows you to tune various parameters to report bandwidth, delay jitter,
datagram loss, and so on.
Example:
The following commands represent an IPERF test definition with three clients on different units that connect simultaneously to the same IPERF server during a dual-test :
Client 1: iperf c hostname p 5001 d L 5001
32
SwissQual...
MMS Receive Test

Basic Function
11 MMS Receive Test

The MMS Receive test attempts to retrieve a MMS message from the network.
MMS Receive test cannot be mixed with other data tests. Only one test per job
allowed. The incoming MMS should be computed by Diversity; otherwise the error
unexpected SMS received will occur.
Before you can run an MMS Send test, you need to manually configure the MMS
options on your phone. For more information, see chapter 12.2, "Phone Configuration", on page 37.
11.1 Basic Function

This test, first, waits for an MMS notification indication sent via (usually two) SMS.
Then, a GPRS and WAP connection is established and the MMS retrieved from the
MMS Center.
Client
Network
Application attempts to
retrieve MMS
Fig. 11-1: MMS Receive Test Basic Function

tab sheet:
Table 11-1: MMS Receive Test - Result Analysis
Value
Description
Service Access duration
Duration for accessing the service
Receive Duration
Duration for sending the message
Overall Receive Duration
Overall duration
33
SwissQual...
MMS Receive Test

Results Analysis
Value
Description
Notification time
Time between sent message (sender: transmission finished) and notification indication on receiver side.
(Not used in MMS receive only tests)
End to end delivery

time
Complete time duration when starting to send message until it is fully received by
opposite site.
Error Code
State message: OK if successful, otherwise the appropriate error text corresponding to the error code.
MMS Size
Size of message
Max Send time
Timeout to send message
Pause Time Sender
Sender Number
Phone number of sender
Receiver Number
Phone number of receiver

Attachment
Not used in Diversity
Gateway
Gateway address and port number
Protocol
Protocol used to transfer data (WSP or HTTP)
Msg Time
Current timestamp of message
Side
States the sender or receiver side
MMS Id
Message payload identifier
Event
Message event
34
SwissQual...
MMS Receive Test

Results Analysis
Fig. 11-2: MMS Receive Test - NQDI Result Analysis Window
35
SwissQual...
MMS Receive Test

Trigger Points MMS Receiver
11.3 Trigger Points MMS Receiver

Log File
Diversity
NOTIFICATION
RECEIVED
Stack
Mobile Phone
Network
Notification SMS
MMS Notification ind
Open RAS
GPRS Attach Req

GPRS Attach Acc
GPRSPDP Con Req
GPRS CONNECT
WAP CONNECTED
TRANSMISSION
STARTED
GPRS Connected
Wsp connect REQ
Wsp connect REQ
Wsp connect REPLY
Wsp connect REPLY
Send MMS
GPRS PDP Con Acc
WTP/HTTP Get REQUEST
MMS Download
TRANSMISSION
FINISHED
MMS m-retrieve-conf
MMS m-retrieve-conf
Close RAS
GPRS PDP Deact Req

GPRS PDP Deact Acc
GPRS Det Req

GPRS
DISCONNECTED
GPRS Disconnected
GPRS Det Acc
Fig. 11-3: MMS Receive trigger points
36
SwissQual...
MMS Send Test

Basic Function
12 MMS Send Test

The MMS Send test sends a message text with additional multimedia object (picture)
by using the Multimedia Messaging Service (MMS). Receiver of the MMS is often
another mobile device providing MMS Receiving capabilities. This test can be used as
a send only test (Single Ended) or in conjunction with Diversity receiver device (Bside). The test objective is to test the MMS service by successfully sending a message
to a receiver number.
MMS Send test cannot be mixed with other data tests. Only one test per job allowed.
12.1 Basic Function

The message text consists of auto created identifiers and random text data which can
be used by an optional receiver for proper MMS identification. Then, the multimedia
content is being added to the message. When the message object is created, a GPRS
connection is established and the message is sent to the MMS Center (MMSC). When
transmission completed, the dial-up connection is being disconnected.
Once the SMS is constructed, it is being sent to the configured SMSC.
Client
Receiver
send MMS
Fig. 12-1: MMS Send Test Basic Function
12.2 Phone Configuration

Before you can run an MMS Send test, you need to manually configure the MMS
options on your phone.
For an MMS test on an Android phone, you need to manually configure an Internet and
an Internet + MMS APN on the phone. You also need to disable the "Auto-retrieve"
function for MMS. For a description on how to perform these actions, see the manual
for your phone.
37
SwissQual...
MMS Send Test

Results Analysis
Some phone types, use a different APN type name, for example, default,supl instead
of Internet and default,supl,mms instead of Internet + MMS.
For Nokia phones, you need to connect to the network that you want a test, send an
MMS, and then configure the phone to never download an MMS.
If this option is not available, you need to configure and select an invalid Access Point
on the phone.

Table 12-1: MMS Send Test - Result Analysis
Value
Description
Service Access
duration
Duration for accessing the service
Transmit Duration
Duration for sending the message
Overall Send Duration
Overall duration
Error Code
MMS Size
Size of message
Max Send time
Timeout to send message
Pause Time Sender
Sender Number

(Not used in MMS send only tests)
Receiver Number
Attachment
Not used in Diversity
Gateway
Gateway address and port number
Protocol
Protocol used to transfer data (WSP or HTTP)
Msg Time
Side
States the sender or receiver side
MMS Id
Message payload identifier
Event
Message event
38
SwissQual...
MMS Send Test

Results Analysis
Fig. 12-2: MMS Send Test - NQDI Result Analysis Window
39
SwissQual...
MMS Send Test

Trigger Points MMS Sender
12.4 Trigger Points MMS Sender

Log File
Diversity
START
Stack
Mobile Phone
Open RAS
Network
GPRS Attach Req

GPRS Attach Acc
GPRS PDP Con Req
GPRS Connected
GPRS CONNECT
WAP CONNECTED
TRANSMISSION
STARTED
Wsp connect REQ
Wsp connect REQ
Wsp connect REPLY
Wsp connect REPLY
Send MMS
GPRS PDP Con Acc
WTP Invoke (begin of MMS Send Req)
WTP Segmented Invoke

MMS Send Ref (begin of MMS Send Req)
TRANSMISSION
FINISHED
MMS m-send-conf
Close RAS
GPRS PDP Deact Req

GPRS PDP Deact Acc
GPRS Det Req

GPRS Disconnected
GPRS Det Acc
Fig. 12-3: MMS Sender trigger points
40
SwissQual...
PDP Activation Test

Basic Function
13 PDP Activation Test

The PDP Activation test tries to activate the PDP context. The test is successful when
the device could successfully connect to the mobile network. Note that this test can
only be performed with mobile communication network devices.
13.1 Basic Function

The application will start a dial-up session to the network. During this dial-up session,
the mobile phone will attempt PDP context activation.
Application starts a dialogue with the network
Client
Network
IP address is returned
Fig. 13-1: PDP Activation Test Basic Function
A successful PDP context activation will return an IP address to the mobile.

Phase
Action
Duration
MsgLogTrace
Preparation
Start test
< 100 ms
PDPActivation Test Started
Test
Establishing dial-up connection
120 s max
Clean Up
Waiting for trace/clean up
1.5 s
You cannot change this value

The NQDI "Analysis" tab displays the following:
41
SwissQual...
PDP Activation Test

Results Analysis
Fig. 13-2: PDP Activation Test - NQDI Result Analysis Window
42
SwissQual...
PDP Deactivation Test

Basic Function
14 PDP Deactivation Test

The PDP Deactivation test tries to deactivate the PDP context. The test is successful
when the device could successfully disconnect from the mobile network. Note that this
test can only be performed with mobile communication network devices.
14.1 Basic Function

The application will attempt to disconnect from the network by performing a PDP deactivation operation.
Client
Network
DEACTIV. ACCEPT will

be returned, if
PDPDeactivation
is successful
Application attempts a PDPDeactivation
Fig. 14-1: Deactivation Test Basic Function

Table 14-1: Timing of actions during a PDP Deactivation Test
Phase
Action
Preparation
Duration
MsgLogTrace
< 100 ms
PDPActivation Test Started
Test
Disconnecting dial-up
connection
30 s max
Clean Up

up
1.5 s
value

The NQDI "Analysis" tab displays the following:
43
SwissQual...
PDP Deactivation Test

Results Analysis
Fig. 14-2: PDP Deactivation Test - NQDI Result Analysis Window
44
SwissQual...
Ping Test
Basic Function
15 Ping Test
The ping test verifies the connectivity between two hosts within an IP data network.
The test measures the Round Trip Time (RTT) between request and reply of multiple
pings by sending ICMP messages. The test is successful when all ICMP Echo
Requests are being acknowledged by the corresponding ICMP Echo Reply message.
If any of the pings is not successfully confirmed within timeout, the test is considered
as failed.
15.1 Basic Function

The test sends the ping (ICMP Echo Request) to the target host with the configured
ICMP packet size and waits for the configured timeout duration for a successful
response. If the ICMP Echo Reply does not arrive to the client within timeout, the ping
response is considered failed.
Client
Host
ICMP Echo Request

RTT1
ICMP Echo Reply
Interval
ICMP Echo Request

RTT2
ICMP Echo Reply
Fig. 15-1: Ping Test - Basic Function
45
SwissQual...
Ping Test
IPv6 Support
The procedure is being repeated until the amount of configured ping attempts are sent
to the host. Between two attempts the pause duration (Interval time) is applied.
Table 15-1: Timing of actions during a Ping Test
Phase
Action
Duration
MsgLogTrace
Preparation
Start test
< 100 ms
Ping Test Started
Test
Ping request
21 s max
Ping reply - RTT
Clean Up

up
1.5 s
value.
15.1.1 Maximum Duration

You can define a maximum duration of 4 seconds to 23 hours 59 minutes and 59 seconds for a Ping test. Depending on the duration that you specify, the test ends when
the maximum duration expires or after the pings requests complete. For best results,
use the following equation to calculate the maximum duration for your test:
Maximum Duration = (Number of Pings) x Interval
Android smartphones use an external library for Ping tests and require a slightly longer
maximum duration than this equation calculates.
Fig. 15-2: Ping test parameters
15.2 IPv6 Support

Diversity ping and ping trace tests support Internet Control Message Protocol version 6
(ICMPv6). IPv6 is enabled by default in Windows on factory PCM reference images
46
SwissQual...
Ping Test
IPv6 Support
starting from Diversity release 12.1 onward. The protocol is enabled with the following
Windows registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\
Parameters\DisabledComponents
When the DisabledComponents key is set to 0x00000000 or is not present, IPV6 is
enabled. In older versions of PCM factory reference images, this key is set to fxffffffff to
disable IPV6.
To enable IPv6 in Windows
1. On the "Start" menu, type regedit.exe in the "Windows Search" box.
2. Go to the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\
Parameters
3. If the "DisabledComponents" key is present, right-click the key, and then click
"Modify".
4. In the "Value Data" box, type 0, and then click "OK".
Note: You can enable or disable IPV6 on each network interface separately.
To enable IPv6 on a network adapter in Windows
1. On the "Start" menu, click "Control Panel", click "Network and Internet", and then
click "Network and Sharing Center".
2. Click "Change adapter settings", right-click a device, for example, a USB network
adapter, and then click "Properties".
3. Select the check box next to "Internet Protocol Version 6 (TCP/IPv6)" and click
"OK".
47
SwissQual...
Ping Test
IPv6 Support
Fig. 15-3: Network adapter properties
Note: Do not disable Internet Protocol Version 4 as this protocol is required for
internal traffic between the controlling PC and the PCMs in a Diversity system as
well as DNS traffic.
15.2.1 Forcing Diversity to Use a Specific IP Version for a Test

You can set a Windows registry key to force Diversity to always use a specific Internet
protocol for a test.
To force Diversity to use a specific Internet protocol
1. On the "Start" menu, type regedit.exe in the "Windows Search" box.
2. Go to the following location:
On a Windows 32 bit system:

HKEY_LOCAL_MACHINE\SOFTWARE\SwissQual\Diversity\Engine
On Windows 64 bit system:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SwissQual\
Diversity\Engine
3. On the "Edit" menu, point to "New", and then click "String Value".
4. Rename the key to "ForceIPVersion".
5. Right-click the key, click "Modify", and in the "Edit String" dialog box enter the value
for the Internet protocol that you want Diversity to use.
48
SwissQual...
Ping Test
IPv6 Support
For IPv4, type 0

For IPv6, type 1
For automatic protocol selection type 2
Note: In automatic mode, Diversity attempts to connect with IPv6 before IPv4.
6. Click "OK".
15.2.2 IPv6 Address Format

You can enter a hostname or IP address in the "Host" box when you configure a test.
To use a hostname in an IPv6 test, the DNS must be able to resolve the hostname into
an IPv6 address. An example of a hostname that can resolve into an IPv6 address is
www.google.com. If you enter an IPv6 address instead, use square brackets at the
start and end of the address, for example, [2a00:1450:4001:c02::67].
For a successful IPv6 test, the client, the server, and each intermediary device in the
network must support IPv6 addresses.
For a successful IPv6 test, all of the components that are involved in the test, that is,
client and server IP addresses, test settings, network adapter settings, and the relevant
Windows registry keys, must support IPv6. Additionally, a ping trace test requires that
the intermediary hops also support IPv6 addresses.
15.2.3 IPv4 and IPv6 Traffic in NQDI

NQDI does not distinguish between IPv4 and IPv6 traffic, that is, NQDI displays both
types of traffic as consolidated IP traffic.
49
SwissQual...
Ping Test
Result Analysis
Fig. 15-4: IPv4 and IPv6 traffic throughput in NQDI
15.3 Result Analysis

tab sheet.
Table 15-2: Ping Test - Result Analysis
Value
Description
Host
Name or IP address of the host
Avg. RTT [ms]
Average Round Trip Time of all ICMP Echo request/response RTTs
No. of successful
Pings
The number of successful Pings
Packet Size [Bytes]
ICMP packet size
Time
State
Not used/Reserved
RTT [ms]
Round Trip Time of current ping
Sequence Number
Sequence number of ping for this test; starting with value 1
50
SwissQual...
Ping Test
Result Analysis
Value
Description
Msg
Error Code
0 if successful; otherwise the error code
Fig. 15-5: Ping Test - NQDI Result Analysis Window
51
SwissQual...
Ping Trace Test

Basic Function
16 Ping Trace Test

The ping trace test is used to determine the route taken to a target host within an IP
data network. The test objective is a) to compile a complete list of hosts passed
through until the target destination has been reached and b) to measure the Round
Trip Time (RTT) of all hosts passed. The test is considered successful when the target
destination could respond with the appropriate reply message.
Diversity ping trace and ping tests support Internet Control Message Protocol version 6
(ICMPv6). For more information, see chapter 15.1.1, "Maximum Duration", on page 46.
16.1 Basic Function

The test sends the ping (ICMP Echo Request) to the target host with the configured
ICMP packet size and a modified Time to Live (TTL) count value of 1 to the target
destination. The TTL value indicates how many Hosts, that is, Hop, are being passed
through, before a ICMP Time to live exceeded message occurs. If the response message arrived within configured timeout the first Hop is considered found. The RTT
value between client and that Hop is being calculated. Now, the TTL value is increased
by one and the ICMP Echo Request is sent again. These steps are being repeated
until the target destination could be reached.
Client
Hop
Hop
Host
ICMP Echo Request

(TTL=1)
RTT1
ICMP TTL Exceeded
ICMP Echo Request

(TTL=2)
RTT2
ICMP Echo Request

(TTL=1)
ICMP TTL Exceeded
ICMP Echo Request

(TTL=3)
ICMP Echo Request

(TTL=2)
RTT3
ICMP Echo Request

(TTL=1)
ICMP Echo Reply
Fig. 16-1: Ping Trace Test - Basic Function
52
SwissQual...
Ping Trace Test

Results Analysis

tab sheet:
Table 16-1: Ping Trace Test - Result Analysis
Value
Description
Time
Hop
Number of the router passed.
RTT
Round Trip Time between Client and Hop
Host
IP address of either the hop where the TTL exceeded or the target host responding with
the Echo Reply message.
DNS Name
Not used / Reserved
Status
State message: OK if successful, otherwise the appropriate (ICMP) error text.
53
SwissQual...
Ping Trace Test

Results Analysis
Fig. 16-2: Ping Trace Test - NQDI Result Analysis Window
54
SwissQual...
SMS Receive Test

Basic Function
17 SMS Receive Test

The SMS Receive test waits for an incoming SMS message. Sender/Originator of the
SMS is another mobile device providing SMS Sending capabilities within. This test can
be used as a receive only test (Single Ended) or in conjunction with Diversity sender
device. The test objective is to test the SMS service by successfully receiving a short
text message.
SMS Receive test cannot be mixed with other data tests. Only one test per job
allowed.
The incoming SMS should be computed by Diversity; otherwise the error unexpected SMS received will occur.
17.1 Basic Function

This test waits for a SMS indication and then gets the SMS from the mobile. This SMS
will be saved and the identifier used to identify the appropriate SMS send test.
Client
Network
retrieve SMS
Fig. 17-1: SMS Receive Test - Basic Function

tab sheet:
Table 17-1: SMS Receive Test - Result Analysis
Value
Description
Send Duration
Time to send the text message
End-To-End Delivery
Time
Duration between sending and receiving a message
SMS Size
Number of characters within the text message
(Not used in SMS send/receive only tests)
55
SwissQual...
SMS Receive Test

Results Analysis
Value
Description
Max Send Time
Timeout value for sending the message
Pause Time Sender
Time between sending of two messages
Sender Number
Receiver Number

(Not used in SMS receive only tests)
Error Code
Fig. 17-2: SMS Receive Test - NQDI Result Analysis Window
56
SwissQual...
SMS Send Test

Basic Function
18 SMS Send Test

The SMS Send test sends a message text by using the Short Message Service (SMS).
Receiver of the SMS is often another mobile device providing SMS Receiving capabilities. This test can be used as a send only test (Single Ended) or in conjunction with
Diversity receiver device (B-side). The test objective is to test the SMS service by successfully sending a short text message to a receiver number.
SMS Send test cannot be mixed with other data tests.
18.1 Basic Function

The message text consists of auto created identifiers and random or user defined text
data which can be used by an optional receiver for proper SMS identification. Once the
SMS is constructed, it is being sent to the configured SMSC.
Client
Receiver
Status Report will

indicate success or
failure
send SMS
Fig. 18-1: SMS Send Test Diagram

Table 18-1: SMS Send Test - Result Analysis
Value
Description
Send Duration
Time to send the text message
End-To-End Delivery
Time
Duration between sending and receiving a message
SMS Size
Number of characters within the text message
Max Send Time
Timeout value for sending the message
Pause Time Sender
Time between sending of two messages
Sender Number
(Not used in SMS send only tests)
(Not used in SMS send only tests)
57
SwissQual...
SMS Send Test

Results Analysis
Value
Description
Receiver Number
Error Code
Fig. 18-2: SMS Send test - Result Analysis Window
58
SwissQual...
UDP Downlink Test

Basic Function
19 UDP Downlink Test

The UDP Downlink (UDP DL) test measures downlink bandwidth with a series of configurable UDP packets. The test has been introduced in order to stress the network
capacity as it would be performed when running audio/visual streaming content.
Unlike other data tests, which work with any appropriate host, providing the corresponding service, such as web/http; email; , the UDP downlink test requires a special server application. That application has to be installed and start upped beforehand.
Once running, the configuration of the server application is being configured during test
initialization phase.
19.1 Basic Function

Firstly, the server application is being configured. The configuration consists of application identifier (SQUDPDL), test number, number of packets to be sent by the server,
interval, packet size and bandwidth. Once the server acknowledged the configuration,
the TCP connection is terminated. Then, after a delay of one second the server begins
sending the UDP packets towards the client with a calculated time gap of [nPackets *
packetSize / bandwidth]. Note, that the time between the packets is limited to a 10-ms
time frame. Therefore, it is not possible to specify the bandwidth for each packet size.
Request for UDP packets is sent

Single ACK packet is received
Port 80
Port 8021
Client
Server
UDP packets are received and

bandwidth performance is recorded
Fig. 19-1: UDP Downlink Test Basic Function
The client logs each packet and calculates average throughput, jitter and packet loss
for each bandwidth. As there can be delays on the network or even packet loss, the
59
SwissQual...
UDP Downlink Test

Results Analysis
client can wait an additional buffer time after the last packet should have arrived. This
simulates the buffer time used by several streaming applications.

The post processing application NQDI shows the following data on the "Analysis" tab:
Table 19-1: UDP Downlink test - Result Analysis
Value
Description
Msg Time
Host
Name or IP address of the UDP server
PacketSize
Size of each packet
Bandwidth
Bandwidth used to send packets
Throughput
Throughput = ((packetsRX-1) * packetSize) / (tLastPacket tFirstPacket)
Packets Sent
Number of packets sent
Packets Received
Number of packets received in time
Jitter
2 x standard deviation of time between packets
Error
60
SwissQual...
UDP Downlink Test

Results Analysis
Fig. 19-2: UDP Downlink Test - NQDI Result Analysis Window
61

Manual - Diversity Data and Messaging Tests

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Manual - Diversity Data and Messaging Tests

Diunggah oleh

Hak Cipta:

Format Tersedia

SwissQual...

Data and Messaging Tests

Test & Measurement

Data and Messaging Tests 01

Overview of a Measurement Cycle.............................................................................. 7

3 Email Receive Test...............................................................................13

4 Email Send Test................................................................................... 15

Impact of Send Buffer Size Parameter Value..............................................................18

FTP Over SSL...............................................................................................................18

6 GPRS Attach Test................................................................................ 21

7 GPRS Detach Test................................................................................23

8 HTTP Browser Test.............................................................................. 25

9 HTTP Transfer Test.............................................................................. 28

Manual Data and Messaging Tests 01

IPERF Server Configuration....................................................................................... 31

11 MMS Receive Test................................................................................33

Trigger Points MMS Receiver.................................................................................... 36

12 MMS Send Test.....................................................................................37

Trigger Points MMS Sender....................................................................................... 40

13 PDP Activation Test............................................................................. 41

14 PDP Deactivation Test......................................................................... 43

Forcing Diversity to Use a Specific IP Version for a Test..............................................48

IPv6 Address Format.................................................................................................... 49

IPv4 and IPv6 Traffic in NQDI....................................................................................... 49

16 Ping Trace Test.................................................................................... 52

17 SMS Receive Test................................................................................ 55

Manual Data and Messaging Tests 01

18 SMS Send Test..................................................................................... 57

19 UDP Downlink Test.............................................................................. 59

Manual Data and Messaging Tests 01

Manual Data and Messaging Tests 01

1.1 Overview of a Measurement Cycle

Manual Data and Messaging Tests 01

A data session contains a series of one

A test session includes initial preparation

GPRS Attach test

Manual Data and Messaging Tests 01

Fig. 1-2: NDIS post connect delay in NQDI

1.2 Reference Documentation

Manual NetQual - NQView.pdf

Manual NQDI - KPI Users Guide.pdf

Manual Data and Messaging Tests 01

2.1 Basic Function

Manual Data and Messaging Tests 01

Data Transfer 1 (e.g. http://server1.com/file1.dat)

Data Transfer 2 (e.g. http://server1.com/file1.dat)

Data Transfer n (e.g. http://server2.com/file2.dat)

2.2 Result Analysis

Time when results arrive

List of the URLs for simultaneous transfer

GET (Download) or PUT (Upload) operation

Protocol for the data transfer

Local file name

PUT operation uses local buffer (recommended size 32 kb)

PUT operation only

Intermediate number of bytes that have been transferred (Last Block = 0)

Possible states are: In Progress, Success, Failed

Final size (Last Block = 1)

Manual Data and Messaging Tests 01

Provides information on errors that occur during the test.

Fig. 2-2: Results of Capacity test

Manual Data and Messaging Tests 01

Email Receive Test

3 Email Receive Test