Академический Документы
Профессиональный Документы
Культура Документы
SwissQual License AG
Allmendweg 8 CH-4528 Zuchwil Switzerland
t +41 32 686 65 65 f +41 32 686 65 66 e info@swissqual.com
www.swissqual.com
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 - 2013 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.
Contents
1
Introduction .......................................................................................................................................... 1
Overview of a Measurement Cycle........................................................................................................ 1
Reference Documentation ..................................................................................................................... 3
Contents |
CONFIDENTIAL MATERIALS
10
11
12
13
14
15
16
17
Contents |
CONFIDENTIAL MATERIALS
19
20
Reducing the Effective Pause Time ...................................................... Error! Bookmark not defined.
Figures
Figure 1-1 Overview of the idle times and pauses in a measurement cycle ..................................................... 1
Figure 1-2 NDIS post connect delay in NQDI. ................................................................................................... 2
Figure 2-1 Ping Test - Basic Function ............................................................................................................... 4
Figure 2-2 Network adapter properties .............................................................................................................. 5
Figure 2-3 IPv4 and IPv6 traffic throughput in NQDI ......................................................................................... 7
Figure 2-4 Ping Test - NQDI Result Analysis Window ...................................................................................... 8
Figure 3-1 Ping Trace Test - Basic Function ..................................................................................................... 9
Figure 3-2 Ping Trace Test - NQDI Result Analysis Window .......................................................................... 10
Figure 4-1 FTP Test - Basic Function .............................................................................................................. 11
Figure 4-2 FTP Test - NQDI Result Analysis Window..................................................................................... 13
Figure 5-1 Test HTTP Browser Test - Basic Function.................................................................................. 14
Figure 5-2 HTTP Browser Test - NQDI Result Analysis Window .................................................................... 15
Figure 6-1 Test HTTP Transfer Test - Basic Function ................................................................................. 16
Figure 6-2 HTTP Transfer Test - NQDI Result Analysis Window.................................................................... 17
Figure 7-1 Overview of a Capacity test ........................................................................................................... 18
Figure 7-2 Results of Capacity test ................................................................................................................. 20
iv
Contents |
CONFIDENTIAL MATERIALS
Tables
Table 2-1 Timing of actions during a Ping Test ................................................................................................. 4
Table 2-2 Ping Test - Result Analysis ............................................................................................................... 7
v
Contents |
CONFIDENTIAL MATERIALS
vi
Contents |
CONFIDENTIAL MATERIALS
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.
Note: Please note that 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 document [1].
Preparation
HTTP
Get
IDLE
FTP
Get
Test
pause
GPRS
Attach
pause
DATA SESSION
pause
IDLE
Clean Up
DATA SESSION
IDLE
The preparation phase typically lasts approximately 100 ms and is therefore not significant.
Important: 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:
Chapter 1 | Introduction
CONFIDENTIAL MATERIALS
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
Ping Trace
UDP
MMS send
MMS receive
Note: In the worst case, the duration of the clean-up phase might double.
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.
Note: 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.
Chapter 1 | Introduction
CONFIDENTIAL MATERIALS
Reference Documentation
Reference
Document
[1]
[2]
Chapter 1 | Introduction
CONFIDENTIAL MATERIALS
Ping Test
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
st
RTT1
ICMP Echo
Reply
Interval
ICMP Echo Re
quest
RTT2
ICMP Echo
Reply
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 2-1 Timing of actions during a Ping Test
Phase
Action
Duration
MsgLogTrace
Preparation
Start test
< 100 ms
Test
Ping request
21 s max
Clean Up
1.5* s
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 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 key is set to 0x00000000 or is not present, IPV6 is enabled.
4
Note: In older versions of PCM factory reference images, this key is set to fxffffffff to disable IPV6.
Important: 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.
HKEY_LOCAL_MACHINE\SOFTWARE\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.
Note: In automatic mode, Diversity attempts to connect with IPv6 before IPv4.
6. Click OK.
Result Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet.
Table 2-2 Ping Test - Result Analysis
Value
Description
Host
Time
State
Not used/Reserved
RTT [ms]
Sequence Number
Msg
Error Code
IPv6 Support
Diversity ping trace and ping tests support Internet Control Message Protocol version 6 (ICMPv6). For more
information, see the "IPv6 Support" section on page 4.
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 (aka 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
Host
Hop
ICMP Echo Re
quest
(TTL=1)
RTT1
ICMP TTL
Exceeded
ICMP Echo Re
quest
(TTL=2)
ICMP Echo Re
quest
(TTL=1)
RTT2
ceeded
ICMP TTL Ex
ICMP Echo Re
quest
(TTL=3)
ICMP Echo Re
quest
(TTL=2)
RTT3
ICMP Echo Re
quest
(TTL=1)
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 3-1 Ping Trace Test - Result Analysis
Value
Description
Time
Hop
Value
Description
RTT
Host
IP address of either the hop where the TTL exceeded or the target host responding with the
Echo Reply message.
DNS Name
Status
10
FTP Test
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
Important: 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).
Note: 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.
Table 4-1 Timing of actions during an FTP Test
Phase
Action
Duration
Preparation
Start test
< 100 ms
Test
120 s max
Clean Up
3* s
MsgLogTrace
FTP Get/Put Test Started
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.
Note: It is possible to have application throughputs exceeding the theoretical physical limitations due to
enhanced phone and PC buffering techniques.
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 4-2 FTP Test - Result Analysis
Value
Description
Time
Operation
Filename
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
Bytes
Transferred
State
Error
State message: OK if successful, otherwise the appropriate error text corresponding to the
error code.
12
13
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
noninvolved 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.
Web
Server
Client
Port 80
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 5-1 HTTP Browser Test - Result Analysis
Value
Description
Msg Time
Url
Number of
images
Number of
frames
Total Size
Throughput
Error
15
Basic Function
Request for HTML page is sent.
Web
Server
Client
Port 80
Note: 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 6-1 Timing of actions during an HTTP Transfer Test
Phase
Action
Duration
Preparation
Start test
< 100 ms
Test
HTTP GET
45 s max
Clean Up
3* s
MsgLogTrace
HTTPTransfer Get/Put Test Started
Results Analysis
The post processing application NQDI shows the data in the following table on the result analysis tab sheet.
Table 6-2 HTTP Transfer Test - Result Analysis
Value
Description
Msg Time
Host
Operation
Buffer Size
Value
Description
Local file
name
Remote file
name
Bytes
Transferred
State
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.
17
Capacity Test
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.
Important: To avoid incomplete and aborted transfers during the duration of the test, use files that are
larger than 1 GB in size.
Start
Data Transfer 1...n
Stop
Data Transfer 1...n
Test Duration
Time
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.
18
Result Analysis
The following table describes the Capacity test data that you can analyse in NQDI.
Table 7-1 Description of the Capacity test data
Value
Description
Msg Time
Host
Operation
Buffer Size
Bytes Transferred
State
Error
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.
19
20
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
timeframe. 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 8022
Port 8021
Server
Client
UDP packets are received and
bandwidth performance is recorded.
Figure 8-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 client can wait an additional buffer time after the
last packet should have arrived. This simulates the buffer time used by several streaming applications.
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 8-1 UDP Downlink test - Result Analysis
Value
Description
Msg Time
Host
PacketSize
Bandwidth
Value
Description
Throughput
Packets
Sent
Packets
Received
Jitter
Error
State message: OK if successful, otherwise the appropriate error text corresponding to the
error code.
22
Basic Function
The UDPPlus test requires a server application (squdpplus) which can communicate with the client (client
side starts test). When a test is started, the client connects to the server and configures a test session (TCP).
After successful server configuration, the client starts to send packets to the server using the pattern defined
in the chirp file. The client sends only packets up to the size of the buffer (buffer size is defined with the
Maximum capacity for send buffer parameter). If the capacity of the buffer is reached, client packet sending
is suspended until the corresponding reply packet is received (on match, packet is removed from buffer) or if
the packet in the buffer reached the timeout it is being deleted from the buffer and marked as lost.
The server receives each packet and sends it back. Packet size can be adjusted by the server if the
appropriate parameters have been set. The client logs each arriving packet and calculates the roundtrip time
(per packet) and throughput (per chirp file repetition). If the server receives no packets for a user defined
time, the server starts to send server generated packets to the client. If option is set, the client can handle
these sever generated packets as regular downlink response packets.
Connection request (TCP)
The send/receive
process is repeated
for all UDP packets.
Throughput and
roundtrip time are
recorded.
Configuration (TCP)
Client
represents the RTT (H, U, B) or delay (S) of the packet. Lost packets are displayed as red dots at the sent
time by the client. Lost server originated packets are not displayed.
Table 9-1 UDP Plus Test - Result Analysis
Value
Description
ReceiveTime
Type
Number
SendTime
ServerTime
Host
RTT [ms]
Delay [ms]
Repetition
Error
OK, if no error has occurred; error code if an error has occurred. Lost - if packet did not
reach the client within the test time
In the Statistics window, the following values are calculated from each repetition or from the whole test:
Table 9-2 UDP Plus Test - Values in Statistics Register
Value
Description
Lost Packets
RTT Standard
Deviation [ms]
Uplink Bandwidth
Mean [kbit/s]
Uplink Bandwidth
Standard Deviation
[kbit/s]
Uplink bandwidth standard deviation value for all type chirp file repetitions
Uplink Bandwidth
x% Value [kbit/s]
Uplink bandwidth value x% of all chirp file repetitions do not fall below
Downlink Bandwidth
Mean [kbit/s]
Downlink Bandwidth
Standard Deviation
[kbit/s]
Downlink bandwidth standard deviation value for all type chirp file repetitions
Downlink Bandwidth
x% Value [kbit/s]
Downlink bandwidth value x% of all chirp file repetitions do not fall below
The Repetition Table shows statistics values per chirp file repetition within a test:
24
Repetition
ULBandwidth [kbit/s]
DLBandwidth [kbit/s]
Lost Packets
25
10
Basic Function
SMTP
Server
Client
Port 25
The
throughput
calculated &
recorded.
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 10-1 Email Send Test - Result Analysis
Value
Description
Msg Time
SMTP
Server
Email
Address
Subject
Size
Connect
Duration
Send
Duration
Throughput
Error Code
26
27
11
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).
SMTP
Server
Client
Port 25
The
throughput
calculated &
recorded.
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 11-1 Email Receive Test - Result Analysis
Value
Description
Msg Time
POP3 Server
Email Address
Subject
Size
Connect Duration
Search Duration
Receive Duration
Message Number
Throughput
Error Code
28
29
12
Basic Function
In a first step the device will check whether or not it is already attached to the network.
Network
Client
Application attempts to attach
to GPRS network.
ATTACH ACCEPT is
sent, if the attach is
successful.
If yes, it will perform a GPRS detach command and afterwards start with the actual attempt to perform a
GPRS attach.
Table 12-1 Timing of actions during a GPRS Attach Test
Phase
Action
Duration
MsgLogTrace
Preparation
Start test
< 100 ms
Preparation
0.5* s
Preparation
Detaching device
60 s max
Test
Attaching device
60 s max
Clean Up
1.5* s
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet. The
Analysis Window displays the following:
30
31
13
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.
Network
Client
Application attempts to detach
from GPRS network.
Phase
Action
Duration
Preparation
MsgLogTrace
< 100 ms
Preparation
0.5* s
Test
Detaching device
30 s max
Clean Up
1.5* s
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
32
33
14
Basic Function
The application will start a dialup session to the network. During this dialup session, the mobile phone will
attempt PDP context activation.
Application starts a dialogue with the network.
Network
Client
IP address is returned.
Figure 14-1 PDP Activation Test Basic Function
Phase
Action
Duration
Preparation
Start test
< 100 ms
Test
120 s max
Clean Up
1.5* s
MsgLogTrace
PDPActivation Test Started
Results Analysis
The Analysis Window displays the following:
34
35
15
Basic Function
The application will attempt to disconnect from the network by performing a PDP deactivation operation.
Network
Client
Application attempts a
PDPDeactivation.
Phase
Action
Duration
Preparation
< 100 ms
Test
30 s max
Clean Up
1.5* s
MsgLogTrace
PDPActivation Test Started
Results Analysis
The Analysis Window display the following:
16
WAP Test
Basic Function
The WAP test starts by connecting to the WAP gateway (redirection is handled as needed). A GET request
for the desired URL is, then, sent to the gateway. Once the response has been received, the page is being
parsed for any Picture tag (<IMG>). For each such tag found, another request is sent to retrieve the image.
The test is finished when the last request has returned.
The throughput is calculated with the size of the downloaded page and all images divided by the time
between the request of the initial page and the response (last packet) of the last image.
Log
WAP/HTTP Server
WAP Gateway
START
WSP Connect
WAP
WSP ConnectReply
TRANS.
WSP Get
http://wap.sbb.ch
TRANS.
WSP Reply
HTTP GET
HTTP OK (+Data)
DOCUMENT
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 16-1 WAP Test - Result Analysis
Value
Description
Connect Duration
Connecting time
Download Duration
Throughput
Error Code
Value
Description
URL:
Host
Time out
Msg Time
Event
Message event
Name
Size
38
17
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.
Receiver
Client
Application attempts to
send SMS
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
39
Value
Description
Send Duration
SMS Size
Sender Number
Receiver Number
Error Code
40
18
Basic Function
This test just 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.
Network
Client
Application attempts to
retrieve SMS
Figure 18-1 SMS Receive Test - Basic Function
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 18-1 SMS Receive Test - Result Analysis
Value
Description
Send Duration
SMS Size
Sender Number
Receiver Number
Error Code
41
42
19
Before you can run an MMS Send test, you need to manually configure the MMS options on your phone.
Phone Configuration
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 user manual for your phone.
Note: Some phone types, such as the HTC sensation, use 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.
Note: If this option is not available, you need to configure and select an invalid Access Point on the phone.
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 dialup connection is being disconnected.
Once the SMS is constructed, it is being sent to the configured SMSC.
Receiver
Client
Application attempts to
send MMS
Figure 19-1 MMS Send Test Basic Function
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 19-1 MMS Send Test - Result Analysis
Value
Description
Value
Description
Transmit Duration
Overall duration
Error Code
MMS Size
Size of message
Sender Number
Receiver Number
Attachment
Gateway
Protocol
Msg Time
Side
MMS Id
Event
Message event
44
45
46
Diversity
START
Mobile Phone
Stack
Network
Open RAS
GPRS_CONNECT
Wsp connect REQ
WAP CONNECTED
TRANSMISSION STARTED
TRANSMISSION FINISHED
MMS m-send-conf
MMm-send-conf
Close RAS
47
20
Before you can run an MMS Send test, you need to manually configure the MMS options on your phone. For
more information, see the "Phone Configuration" section on page 43.
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.
Network
Client
Application attempts to
retrieve MMS
Figure 20-1 MMS Receive Test Basic Function
Results Analysis
The post processing application NQDI shows the following data on the result analysis tab sheet:
Table 20-1 MMS Receive Test - Result Analysis
Value
Description
Receive Duration
Overall duration
Notification time
Error Code
MMS Size
Size of message
Sender Number
Value
Description
Receiver Number
Attachment
Gateway
Protocol
Msg Time
Side
MMS Id
Event
Message event
49
50
51
Diversity
NOTIFICATION RECEIVED
Mobile Phone
Stack
Notification SMS
Network
Open RAS
GPRS_CONNECT
Wsp connect REQ
WAP CONNECTED
TRANSMISSION STARTED
MMS Download
TRANSMISSION FINISHED
MMS m-retrieve-conf
MMS m-retrieve-conf
Close RAS
GPRS DISCONNECTED
GPRS Disconnected
52
In order to perform data tests effectively, Firewall settings on client and server side must be configured
properly. Due to increasing IT security issues it is highly recommended to unblock only the necessary ports
and applications used for testing.
The following tables give an overview of required protocols and ports used by the data tests.
Table A-1 Port Number Listing
Server TCP
Client TCP
Incoming
Outgoing
Incoming
Outgoing
FTP
21
(P)
(A)
21
SSH
22
22
SMTP
25
25
DNS
53
53
HTTP
80
80
POP3
110
110
Authentication Service
113
113
RTSP, Control
554
554
Darwin Admin
1220
1220
UDPPlus Configuration
(S, T) 8019
(S, T) 8019
random
random
Server UDP
Client UDP
Incoming
Outgoing
DNS
53
53
Authentication Service
113
113
RTSP, Data
Incoming
6970..6989
6970..6989
Outgoing
UDP Test
8010
8010
8010
8010
UDPDl Test
8021
8021
8022
8022
UDPPlus Test
(T) 8023
(T) 8023
(T) 8024
(T) 8024
Legend:
P
Note: Not all data tests require a previous dialup. Such as GPRS and PDP Tests!
The measurement PC dials up to the Internet provider. At this point, the marker GPRS Dial is written to the
log file. This marker can be shown in the GSM Analysis window:
The GPRS markers are also visible on the test-specific tab sheet (FTP, UDP, HTTP, Email, WAP).
54
And, last but not least, they are also visible on the Map, if you choose Call Markers.
After the GPRS Dial, the mobile will start with an Attach procedure and a PDP Context Activation
process. This can be seen in the GSM Analysis window in the inter-layer table:
55
As soon as the mobile is connected to the Internet, you will get a GPRS Connect marker. If the dial-up fails,
56
you will get a GPRS Connect Failed marker. This means, that the mobile is not connected to the Internet
and that the dial-up has to be repeated.
You can search for such events, if you select the GPRS Connect Failed markers in the data selection part:
57
The minimum length of the pause between data tests in NQView is 0 seconds. Diversity automatically adds
the waiting for trace messages time to this pause to create the effective pause time. If you want to modify
the waiting for trace messages time for the following data test types, you need to create a Windows
Registry key:
HTTP Transfer
HTTP Browser
FTP
Capacity
IPERF
Ping Trace
UDP
MMS.
2. Right-click Engine, point to New, click String Value, and type WaitForEtherealMessages as the name.
3. Right-click the new WaitForEtherealMessages value and click Modify.
4. Type the length of the pause in milliseconds and click OK.
58