OnDevice HTTP - User Manual

Orchestrating Network Performance
OnDevice Http User Manual

Contents
1 Overview 3
1.1 Operational and Functional Differences .......................................................... 3
1.1.1 HTTP GET - UE Download .............................................................. 3
1.1.2 HTTP GET - UE Webkit ................................................................... 3
1.1.3 HTTP POST - HTTP UE .................................................................. 4
2 Activity Configuration 5
2.1 Sample Scripts ................................................................................................ 5
2.1.3 HTTP POST - HTTP UE .................................................................. 5
2.2 Settings............................................................................................................ 6
2.2.3 HTTP POST – HTTP UE ................................................................. 7
3 Information Elements & Events 9

3.1 KPI Measurement Overview............................................................................ 9
3.2 HTTP GET ....................................................................................................... 9
3.2.1 HTTP GET Trigger Point.................................................................. 9
3.2.2 HTTP GET Operation Event ............................................................ 9
3.2.3 HTTP GET Information Element ...................................................... 9
3.2.4 HTTP GET Signaling Diagram (Single Socket) .............................10
3.2.5 HTTP Signaling Diagram (Multiple Sockets) .................................11
3.2.6 Sample Measurement ....................................................................12
3.3 HTTP POST ..................................................................................................14
3.3.1 HTTP POST Trigger Point .............................................................14
3.3.2 HTTP POST Operation Event ........................................................14
3.3.3 HTTP POST Information Element .................................................14
3.3.4 HTTP Signaling Diagram (Single Socket)......................................14
3.3.5 HTTP Signaling Diagram (Multiple Sockets) .................................15
3.3.6 Sample Measurement ....................................................................17
3.3.1 Supported HTTP KPIs ...................................................................19
3.3.2 Supported HTTP POST KPIs ........................................................20
3.3.3 Supported HTTP End Result .........................................................20
3.3.4 Supported HTTP Post End Result .................................................21
TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 1

OnDevice Http User Manual, Version 1.0
3.3.5 Limited KPIs for HTTP Get (Proceed without IPSniffer) ................22
3.3.6 Limited KPIs for HTTP Post (Proceed without IPSniffer) ...............22
4 Highlights 23
4.1 Limitations .....................................................................................................23

1 Overview
OnDevice HTTP Service is a service that used to measure the network performance on
HTTP protocol. The functionality that it provides include HTTP download, HTTP upload
and Web browsing.
1.1 Operational and Functional Differences

There are 3 OnDevice HTTP solutions as below.
 HTTP GET - UE Download : OnDevice file download
 HTTP GET - UE Webkit : OnDevice web browsing
 HTTP POST - UE HTTP : OnDevice file upload
1.1.1 HTTP GET - UE Download

UE Download solution is a solution to perform file download via HTTP GET.
1.1.2 HTTP GET - UE Webkit

UE Webkit solution is a solution that browse a web page via HTTP GET. The content of
the web page will be displayed as a floating window. There are 2 types of web pages
that supported, which is static web page and live web page.
1.1.2.1 Static Web Page Test

The content of the web page is static and will not change once the page download
finish. The download session considered as completed when there is a download
finish notification received (For time-based measurement it is upon the maximum
transfer duration ended).

1.1.2.2 Live Web Page Test

The content of the web page is dynamic and it keeps refresh after the page download
finish. The download session considered as completed when receive the download
finish notification, minimum payload was downloaded and silence time accomplished.
1.1.3 HTTP POST - HTTP UE

HTTP UE (upload) is a solution to perform a file upload via HTTP POST.

2 Activity Configuration
2.1 Sample Scripts

Sample Script Sample Script Screenshot
http_get_ue_download.tsc

http_get_ue_webkit.tsc
2.1.3 HTTP POST - HTTP UE

http_post_ue_http.tsc

2.2 Settings

Property Description
URL Main URL of web page or file to download. – In post-processing, the HTTP
Get session will be classified as “File Transfer” if the downloaded file has one
of the following extensions: .7z, .avi, .bmp, .dat, .jpg, .mp3, .mpg, .png, .rar,
.txt, .wav, or .zip. If the file has some other extension, the session will count
as “Web Browsing”. It allows multiple Urls that separated by comma.
Example; http://testbenchmark.com/content/1M.zip,
http://testbenchmark.com/content/3M.zip,
http://testbenchmark.com/content/10M.zip,
End Session After If set to True, the HTTP session is ended automatically after a user-specified
Time length of time, indicated in the Timefield. The duration is counted from the
moment the first HTTP packet is received from the server.
Time The predefined time to end the session
Concurrent The mode to be used for concurrent downloads. Multiple Files mode will
Download download multiple files concurrently, while Multiple Parts mode will download
one file with multiple threads.
Number Of Number of file(s) to be downloaded in parallel.

Downloads
Number Of Threads Number of threads(s) to be used in parallel.
Consider Any Indicating whether the test is considered failed if one of the download/thread
Download Thread failed.
Failure As Failed
Measurement
Indicating whether the test should proceed if the IPCapture service failed to
Proceed Without IP
start.
Sniffer If set to True, the test will proceed with Limited KPIs provided. Refer to 3.3.5
section for the supported KPIs.
If set to False, the test will stop with error message, Failed to start
IPCapture Service.

URL URL to perform the HTTP GET

Example; http://testbenchmark.com/kepler
moment the first HTTP packet is received from the server.
Show Window Show or hide the browser window that display the content of the web page
Web Page Type The type of the target web page. It could be either Static web page or Live
web page.

Render Time The rendering time for the webpage to load before the browser being close
upon finished download. Only available for Static web page.
Web Page Payload The expected web page payload size to be downloaded. The value will be
Size used for the calculation of the compression ratio. The payload size for Kepler
reference web page should be 815,804 bytes and payload size for
Smartphones Kepler reference web page should be 145,256 bytes.
Minimum Payload Predefined payload that must be downloaded from the live web page, to
indicate the download is completed.
Silence Time Predefined silence duration that used to indicate the download is completed
for live web page. The download will be considered as completed if there is
no packet received within the duration. Set ‘0’ to disable the timeout.
Maximum Wait Time Maximum duration that should wait before the minimum payload is
downloaded and predefined silence time fulfilled. Set ‘0’ to disable the
timeout
Maximum Session Maximum duration for the download session to be completed. Set ‘0’ to
Time disable the timeout
Clear Cache Clear the cache before start the download.
Clear Cookies Clear the cookies before start the download.

Proceed Without IP
start.
IPCapture Service.
2.2.3 HTTP POST – HTTP UE

URL The URL of the web page to which the file will be uploaded.
Example; http://testbenchmark.com/content/Upload.html
moment the first HTTP packet is sent to the server.
Amount of Data to Size of the file to upload to the URL. A temporary data file of the specified
Upload size will be created. It is possible to indicate the unit as follows: B = byte, K =
kilobyte, M = megabyte, G = gigabyte, T = terabyte. Alternatively, lowercase
letters can be used with no difference in meaning. If you do not specify a unit,
the number you enter is interpreted as a byte count.
Concurrent Upload The mode to be used for concurrent uploads. Multiple Files mode will upload
multiple files concurrently, while Multiple Parts mode will upload one file with
multiple threads.
Number Of Uploads Number of file(s) to be uploaded in parallel.
Number Of Threads Number of threads(s) to be used in parallel.
Consider Any Indicating whether the test is considered failed if one of the download/thread
Upload Thread failed.
Failure As Failed
Measurement

Proceed Without IP
start.
IPCapture Service.

3 Information Elements & Events

3.1 KPI Measurement Overview
Throughput measurement for HTTP Get is measured on TCP level. In order to measure
in TCP level, IP Sniffing service will be running at the background to sniff the HTTP Get
traffic. Those important measurement elements (i.e. KPI Trigger Point, timestamp and
bytes transferred) will be retrieved directly from the captured IP packets by inspecting
all the packets.
3.2 HTTP GET
3.2.1 HTTP GET Trigger Point

Trigger Point Abstract Description Technical Description
Tr-1 Script activity start TEMS script activity been trigger to start
Tr-2 Start HTTP connection First Syn flag been triggered
Tr-3 Send Operation request First HTTP GET request sent
Operation successfully Received success response

Tr-4
completed
Tr-5 Operation failed Received error response
3.2.2 HTTP GET Operation Event

Events Description Start Trigger End Trigger
HTTP Start Script activity started. Tr-1 -
First SYN Operation start Tr-2 -
First SYN ACK Operation received Server SYN ACK Tr-2 -
First ACK Operation ACK to Server Tr-2 -
First HTTP GET Operation first HTTP GET request Tr-3 Tr-4
First Packet With Operation received first packet with

Tr-1 Tr-4
Content payload
HTTP Error Operation failed. Tr-1 Tr-5
HTTP End Script activity ended. Tr-1 Tr-4 or Tr-5
3.2.3 HTTP GET Information Element

Information Elements Description
HTTP Average Throughput The average throughput for HTTP download
Percentage of HTTP downloads that could not be completed although they

HTTP Data Transfer Cutoff Ratio
were started successfully.
HTTP Get Session Failure Ratio The failure rate of the HTTP GET session.

Percentage of HTTP download attempts where, after successful PDP

HTTP IP Service Access Failure
context activation, the HTTP service itself could not be accessed. (This IE is
Ratio
meaningful only for UMTS.)
HTTP Received Number of bytes received over HTTP.
Percentage of HTTPdownload attempts where the HTTP service could not

be accessed, due to a failure that occurred either during PDP context
HTTP Service Non-Accessibility
activation or during the service access procedure itself. (This IE is
meaningful only for UMTS.)
HTTP Throughput Instantaneous HTTPdownload throughput
HTTP Trasnfer Time Elapsed time for current HTTP download session.
3.2.4 HTTP GET Signaling Diagram (Single Socket)

Diagram below shows the HTTP Get signaling. The normal flow of browsing or
downloading a file is as below;
DNS -> TCP Handshake -> GET Request -> GET Response 200 OK and Start Transfer -> End
For throughput measurement, it start measures upon getting the GET Response with
200 OK. From there onwards, throughput will be updated in every second of interval.
HTTP Client DNS Server HTTP Server KPI Trigger
DNS Query
DNS Response
TCP SYN First SYN

TCP SYN-ACK First SYN-ACK
TCP ACK
HTTP GET First HttpGet
HTTP 200 OK First Packet With Content

P0
HTTP payload
HTTP payload
P1: Payload Update (every sec)
P4: Payload Update up to last payload packet

HTTP payload Last Packet
TCP FIN

3.2.5 HTTP Signaling Diagram (Multiple Sockets)

Diagram below shows the HTTP Get signaling for Multiple Sockets. The trigger points is
configurable to use either the first connection or the last connection (use last connection
by default).
3.2.2.1 Use last connection as trigger points:

3.2.2.2 Use first connection as trigger points:
3.2.6 Sample Measurement
3.2.6.1 Application Layer Throughput Downlink

Application Layer Throughput Downlink is the current throughput for the period of 1
second.
𝑃𝑎𝑦𝑙𝑜𝑎𝑑𝑃1
𝐴𝑝𝑝𝑙𝑖𝑐𝑎𝑡𝑖𝑜𝑛𝐿𝑎𝑦𝑒𝑟𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡𝐷𝑜𝑤𝑛𝑙𝑖𝑛𝑘𝑃1 = 𝑇𝑖𝑚𝑒𝑃1 − 𝑇𝑖𝑚𝑒𝑃0
q
𝑃𝑎𝑦𝑙𝑜𝑎𝑑𝑃2 − 𝑃𝑎𝑦𝑙𝑜𝑎𝑑𝑃1
𝐴𝑝𝑝𝑙𝑖𝑐𝑎𝑡𝑖𝑜𝑛𝐿𝑎𝑦𝑒𝑟𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡𝐷𝑜𝑤𝑛𝑙𝑖𝑛𝑘𝑃2 =
𝑇𝑖𝑚𝑒𝑃2 − 𝑇𝑖𝑚𝑒𝑃1

3.2.6.2 Http Average Throughput

Http Average Throughput is the average throughput since the first Get Response with
200 OK.
𝐻𝑡𝑡𝑝𝐴𝑣𝑒𝑟𝑎𝑔𝑒𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡𝑃1 =
𝐻𝑡𝑡𝑝𝐴𝑣𝑒𝑟𝑎𝑔𝑒𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡𝑃2 =

3.3 HTTP POST

Throughput measurement for HTTP Post is measured on TCP level. In order to measure
in TCP level, IP Sniffing service will be running at the background to sniff the HTTP Post
traffic. Those important measurement elements (i.e. KPI Trigger Point, timestamp and
bytes transferred) will be retrieved directly from the captured IP packets by inspecting
all the packets.
3.3.1 HTTP POST Trigger Point

Trigger Point Abstract Description Technical Description
Tr-1 Script activity start TEMS script activity been trigger to start
Tr-2 Start HTTP connection First Syn flag been triggered
Tr-3 Send Operation request First HTTP POST request sent
Operation successfully Received success response

Tr-4
completed
Tr-5 Operation failed Received error response
3.3.2 HTTP POST Operation Event

Events Description Start Trigger End Trigger
HTTP Post Start Script activity started. Tr-1 -
First SYN Operation start Tr-2 -
First SYN ACK Operation received Server SYN ACK Tr-2 -
First ACK Operation ACK to Server Tr-2 -
First HTTP POST Operation first HTTP POST request Tr-3 Tr-4
First Packet With Operation received first packet with

Tr-1 Tr-4
Content payload
HTTP Error Operation failed. Tr-1 Tr-5
HTTP End Script activity ended. Tr-1 Tr-4 or Tr-5
3.3.3 HTTP POST Information Element

Information Elements Description
HTTP Post Average Throughput Average throughput for HTTPupload.
HTTP Post File Size Sent Size of file uploaded over HTTP.
HTTP Post File Transfer Time Time taken by the browser to complete the HTTP upload.
HTTP Post Throughput Instantaneous HTTP upload throughput.
3.3.4 HTTP Signaling Diagram (Single Socket)

Diagram below shows the HTTP Post signaling. The normal flow of uploading a file is
as below;
DNS -> TCP Handshake -> POST Request -> Start Transfer -> End

For throughput measurement, it start measures upon getting the First Uploaded Byte
after the POST Request. From there onwards, throughput will be updated in every
second of interval.
HTTP Client DNS Server HTTP Server KPI Trigger
DNS Query
DNS Response
TCP SYN First SYN

TCP SYN-ACK First SYN-ACK
TCP ACK
HTTP POST First HttpPost
Upload Data First Packet With Content

P0
Upload Data
TCP ACK
Upload Data
Upload Data
TCP ACK
TCP ACK
Upload Data
Upload Data P3: Payload Update (every sec)
P4: Payload Update up to last payload packet

TCP ACK Last Packet
HTTP 200 OK
TCP FIN
3.3.5 HTTP Signaling Diagram (Multiple Sockets)

Diagram below shows the HTTP Post signaling for multiple sockets. The trigger points
is configurable to use either the first connection or the last connection (use last
connection by default).
3.3.5.1 Use last connection as trigger points:


3.3.5.2 Use first connection as trigger points:
3.3.6 Sample Measurement
3.3.6.1 Application Layer Throughput Uplink

Application Layer Throughput Uplink is the current throughput for the period of 1
second.
𝐴𝑝𝑝𝑙𝑖𝑐𝑎𝑡𝑖𝑜𝑛𝐿𝑎𝑦𝑒𝑟𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡𝑈𝑝𝑙𝑖𝑛𝑘𝑃1 =

𝑃𝑎𝑦𝑙𝑜𝑎𝑑𝑃2 − 𝑃𝑎𝑦𝑙𝑜𝑎𝑑𝑃1
𝐴𝑝𝑝𝑙𝑖𝑐𝑎𝑡𝑖𝑜𝑛𝐿𝑎𝑦𝑒𝑟𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡𝑈𝑝𝑙𝑖𝑛𝑘𝑃2 =
3.3.6.2 Http Post Average Throughput

Http Post Average Throughput is the average throughput since the First Uploaded
Byte.
𝐻𝑡𝑡𝑝𝑃𝑜𝑠𝑡𝐴𝑣𝑒𝑟𝑎𝑔𝑒𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡𝑃1 =
𝐻𝑡𝑡𝑝𝑃𝑜𝑠𝑡𝐴𝑣𝑒𝑟𝑎𝑔𝑒𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡𝑃2 =

3.3.1 Supported HTTP KPIs

Table below shows the list of supported KPIs for each HTTP solution. Please refer to
the KPI Markers diagram for the Start/Stop Trigger.
 - SUPPORT both HTTP and HTTPS

 - ONLY Support HTTP
 - ONLY Support HTTP and HTTPS (Applicable for Samsung Android Device only)
 - ONLY applicable if IP Capture Service is available on the device. Otherwise,
ONLY produce final result upon service end
KPIs UE Download UE Webkit
1 HTTP IP Service Setup Time

Method A
 
2 HTTP IP Service Setup Time

Method B
 
3 HTTP IP Service Access Failure

Method A
 
4 HTTP IP Service Access Failure

Method B
 
5 HTTP Data Transfer Time

 
Method A
6 HTTP Data Transfer Time

Method A
 
7 HTTP Data Transfer Cutoff

Method A
 
8 HTTP Data Transfer Cutoff

Method B
 
9 HTTP Mean Data Rate Method

A
 
10 HTTP Mean Data Rate Method

B
 
11 HTTP Service Not Accessible

Method A
12 HTTP Service Not Accessible

Method B
13 HTTP Setup Time Method A
14 HTTP Setup Time Method B
15 HTTP Technical Browsing Time 

16 HTTP User Browsing Time 

3.3.2 Supported HTTP POST KPIs

Table below shows the list of supported KPIs for each HTTP solution. Please refer to
the KPI Markers diagram for the Start/Stop Trigger.

 - ONLY Support HTTP and HTTPS (Applicable for Samsung Android Device only)
 - ONLY applicable if IP Capture Service is available on the device. Otherwise,
ONLY produce final result upon service end
KPIs HTTP UE
1 HTTP Post IP Service Setup

Time Method A

3 HTTP Post IP Service Access

Failure Method A

5 HTTP Post Data Transfer Time


Method A
7 HTTP Post Data Transfer Cutoff

Method A

9 HTTP Post Mean Data Rate

Method A

3.3.3 Supported HTTP End Result

 - ONLY applicable if IP Capture Service is available on the device.
Streaming End Result UE Download UE Webkit
1 Service Status  
2 Session Identity  
3 Time Based Measurement  
5 Service Bearer  
6 Date Ratio Bearer  
9 LTE Serving Cell Count  
Average
10 Multi Sockets 

11 Web Compression Ratio 
3.3.4 Supported HTTP Post End Result

 - ONLY applicable if IP Capture Service is available on the device.
Streaming End Result UE Download
1 Service Status 
2 Session Identity 
3 Time Based Measurement 
5 Service Bearer 
6 Date Ratio Bearer 
9 LTE Serving Cell Count 
Average
10 Multi Sockets 

3.3.5 Limited KPIs for HTTP Get (Proceed without IPSniffer)

Table below shows the list of limited KPIs supported for HTTP UE Download and
HTTP UE Webkit without IPSniffer.
KPIs UE Download UE Webkit
1 HTTP Received  
2 HTTP Throughput  
3 HTTP Transfer Time  
4 HTTP Average Throughput  
* The payload getting from test without IPSniffer will be slighly higher compare with the payload
getting from test with IPSniffer, as the total payload without IPSniffer include the calculation of
packet overhead for transmitting the payload.
3.3.6 Limited KPIs for HTTP Post (Proceed without IPSniffer)

Table below shows the list of limited KPIs supported for HTTP Post without IPSniffer.
KPIs UE Post
1 HTTP Post File Size Sent 

2 HTTP Post Average Throughput 
3 HTTP Post Throughput 
4 HTTP Transfer Time 
* The payload getting from test without IPSniffer will be slighly higher compare with the payload
getting from test with IPSniffer, as the total payload without IPSniffer include the calculation of
packet overhead for transmitting the payload.

4 Highlights
4.1 Limitations
Limitations
1 Internet Explorer and the TEMS browser cannot run concurrently on the same device.
On the other hand, when either Internet Explorer alone or the TEMS browser alone is used,
there are no restrictions on HTTP session concurrency, neither for a single device nor for
multiple devices.
2 HTTP Get with Browser Client set to “Internet Explorer” does not work under Windows 10,
neither with Internet Explorer itself nor with the Microsoft Edge browser (which is the default one
in Windows 10).
3 HTTP Post with HTTP Post Type set to “Internet Explorer” does not work under Windows 10,
neither with Internet Explorer itself nor with the Microsoft Edge browser (which is the default one
in Windows 10).


OnDevice HTTP - User Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OnDevice HTTP - User Manual

Uploaded by

Copyright:

Available Formats

Orchestrating Network Performance

OnDevice Http User Manual

3 Information Elements & Events 9

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 1

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 2

1.1 Operational and Functional Differences

1.1.1 HTTP GET - UE Download

1.1.2 HTTP GET - UE Webkit

1.1.2.1 Static Web Page Test

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 3

1.1.2.2 Live Web Page Test

1.1.3 HTTP POST - HTTP UE

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 4

2.1.1 HTTP GET - UE Download

2.1.2 HTTP GET - UE Webkit

2.1.3 HTTP POST - HTTP UE

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 5

2.2.1 HTTP GET - UE Download

Time The predefined time to end the session

Number Of Number of file(s) to be downloaded in parallel.

Number Of Threads Number of threads(s) to be used in parallel.

2.2.2 HTTP GET - UE Webkit

URL URL to perform the HTTP GET

Time The predefined time to end the session

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 6

Clear Cache Clear the cache before start the download.

Clear Cookies Clear the cookies before start the download.

2.2.3 HTTP POST – HTTP UE

Time The predefined time to end the session

Number Of Uploads Number of file(s) to be uploaded in parallel.

Number Of Threads Number of threads(s) to be used in parallel.

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 7

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 8

3 Information Elements & Events

3.2 HTTP GET

3.2.1 HTTP GET Trigger Point

Tr-2 Start HTTP connection First Syn flag been triggered

Tr-3 Send Operation request First HTTP GET request sent

Operation successfully Received success response

Tr-5 Operation failed Received error response

3.2.2 HTTP GET Operation Event

HTTP Start Script activity started. Tr-1 -

First SYN Operation start Tr-2 -

First SYN ACK Operation received Server SYN ACK Tr-2 -

First ACK Operation ACK to Server Tr-2 -

First Packet With Operation received first packet with

HTTP Error Operation failed. Tr-1 Tr-5

HTTP End Script activity ended. Tr-1 Tr-4 or Tr-5

3.2.3 HTTP GET Information Element

HTTP Average Throughput The average throughput for HTTP download

Percentage of HTTP downloads that could not be completed although they

TEMS™ – now part of InfoVista www.infovista.com | www.tems.com | 9

Percentage of HTTP download attempts where, after successful PDP

HTTP Received Number of bytes received over HTTP.

Percentage of HTTPdownload attempts where the HTTP service could not

HTTP Throughput Instantaneous HTTPdownload throughput

3.2.4 HTTP GET Signaling Diagram (Single Socket)

HTTP Client DNS Server HTTP Server KPI Trigger

TCP SYN First SYN

HTTP GET First HttpGet

HTTP 200 OK First Packet With Content

P2: Payload Update (every sec)

P3: Payload Update (every sec)