General Technical Specifications for

OnDeviceOttSupplementaryActionService

www.Infovista.com | 1
Copyright Infovista Sweden AB 2022

TEMS is a trademark of Infovista. All other trademarks are the property of their respective holders.
No part of this document may be reproduced in any form without the written permission of the copyright holder.

The contents of this document are subject to revision without notice due to continued progress in methodology, design and
manufacturing. Infovista shall have no liability for any error or damage of any kind resulting from the use of this document.

www.Infovista.com | 2
Contents
1 Introduction 4
2 KPIs 5
2.1 Events 5
2.2 Information Elements 7
3 Configurations 8
3.1 Common Configurations 8
4 Known Limitations 10
4.1 Available KPIs 10
4.2 Available Configurations 10
4.3 Supported OTT Supplementary Action Applications 10
4.4 Install atx-agent 10
5 Other Notes 11

www.Infovista.com | 3
1 Introduction
This document provides information for understanding and implementing support for TEMS OnDevice OTT
Supplementary Action service.

www.Infovista.com | 4
2 KPIs

2.1 Events

Events

DNS Host Name Resolution Time

DNS resolution duration.

DNS Host Name Resolution Failure

DNS resolution failed.

First ACK

First DNS Request

First HTTP GET

First Packet with Content

First SYN

First SYN ACK

HTTP Time to First Byte

Elapsed time from First DNS Request to First Packet with Content.

HTTP Time to First Byte Failure

Missing First Packet with Content trigger after receiving First DNS Request.

Supplementary Action Attempt

Attempting to perform supplementary action.

Supplementary Action End

Supplementary Action activity ended.

Supplementary Action Error

Supplementary Action activity failed.

Supplementary Action Start

Supplementary Action activity started.

Supplementary Action Success

Supplementary Action activity successful.

Supplementary Action State Changed: End Configuration Phase

State changed from Start Configuration Phase to End Configuration Phase.

www.Infovista.com | 5
Supplementary Action State Changed: Start Configuration Phase
State changed to Start Configuration Phase.

Supplementary Action State Changed: Test Phase End

State changed to Test Phase End

Supplementary Action State Changed: Test Phase Start

State changed to Start Test Phase.

Supplementary Action Configuration Phase Complete

The configuration phase is completed.

Supplementary Action Test Phase Complete

The test phase is completed. The test phase starts from the launching of the OTT application and ends when the
OTT application is closed.

Supplementary Action UI Automation Action: First Action

First UI Automation Action for OTT Supplementary Action

Supplementary Action UI Automation Action: Last Action

Last UI Automation Action for OTT Supplementary Action

Supplementary Action UI Automation Action: Launch Intent

Android Intent launched to open the OTT application on the device.

www.Infovista.com | 6
2.2 Information Elements

Information Elements

OnDevice Version
The ODM version used for the test

OTT Supplementary Action Configuration Phase Duration

The time is takes to complete the configuration phase.

OTT Supplementary Action Operation Duration

The time is takes to complete the entire OTT Supplementary Action operation, from Begin Event to End Event.

OTT Supplementary Action Operation Success Ratio

The success ratio is calculated based on the number of Success Event over the number of Begin Event.

OTT Supplementary Action Test Phase Duration

The time is takes to complete the test phase.

OTT Supplementary Action First To Last Duration

The time is takes to complete the entire OTT Supplementary Action operation, from First Action to Last Action.

www.Infovista.com | 7
3 Configurations

3.1 Common Configurations

Parameter Description Default Value

-pwis Proceed without IP Sniffer (eg: -pwis True)

When set to True, ODM will continue the test even when IP Sniffer Service is False
not available.

-nat Network Access Timeout (eg: -nat 5)

Sets the maximum wait time in seconds to get network access. 5
When omitted, defaults to 5s.

-dnst DNS Timeout (eg: -dnst 10)

Sets the maximum wait time in seconds to get network access. 0
Omit or set to 0 to disable.

-ttfbt Time to First Byte Timeout (eg: -ttfbt 15)

Sets the maximum wait time in seconds to reach First Packet with Content
0
state after First DNS Request state is reached. If exceeded, the test will fail.
Omit or set to 0 to disable.

-cs Chunk Size (eg: -cs 100000)

Sets the chunk size in bytes. A chunk report will be created every time the
payload reaches the given chunk size.
0
The chunk size will dramatically affect the performance if is set too small.
Recommended value to be above 10000 bytes.
Omit or set to 0 to disable.

-a Action To Be Performed (eg: -a loadfeed)

Sets the supplementary action of the test. Example login logoff loadfeed N/A
This is a mandatory parameter.

-m Message (eg: -m Testing)

Sets the message to the post or comment section. It is parameter for post or N/A
comment purpose. Available for certain app like Facebook.

-u User Name (eg: -u [email protected])

Sets the user name for login app. Example Netflix user account for login Netflix N/A
app.

-pnm Profile User Name (eg: -pnm Test)

N/A
Sets the profile name for Netflix to select when launching Netflix app.

-pwd Password (eg: -pwd password) N/A

www.Infovista.com | 8
 Sets the password for login app. Example Netflix password for login Netflix
app.

-pgn Page Profile Name (eg: -pgn News)

N/A
Sets the page name to load feed. Example Facebook page.

-st Search Text (eg: -st Testing)

Sets the text used to search in twitter. It is parameter for search purpose. N/A
Available for certain app like Twitter.

-ht Search Hashtag (eg: -ht car)

Sets the text used to search hashtag in instagram. It is parameter for search N/A
purpose. Available for certain app like Instagram

www.Infovista.com | 9
4 Known Limitations

4.1 Available KPIs

The list of supported KPIs in 2.1 provides the KPIs that are available and supported in
OnDeviceOttSupplementaryActionService.

4.2 Available Configurations

The list of supported configurations in 3.1 provides the configurations that are available and supported in
OnDeviceOttSupplementaryActionService.

However, the actual list of configurations for each OTT Supplementary Action application can be more or less,
depending on the limitation of the Supplementary Action application itself. The configurations that are not
available or added extra for each Supplementary Action application will be listed in the technical specification
document for each Supplementary Action application.

4.3 Supported OTT Supplementary Action Applications

Only OTT Supplementary Action applications that can be controlled and properly automated using UI automation
are supported by OnDeviceOttSupplementaryActionService.

Applications that use APIs for interfacing is not supported.

4.4 Install atx-agent

The first release of OnDeviceOttSupplementaryActionService will not auto install the atx-agent for Commercial
and Connectable devices. In the event the atx-agent is not yet installed on the device, user must first download
the atx-agent from the 3rd Party Components and install it with the following commands:

adb push <atx-agent file full path> /data/local/tmp

For example:
adb push C:\Users\kgoh\Downloads\atx-agent\atx-agent /data/local/tmp

adb shell chmod 777 /data/local/tmp/atx-agent

www.Infovista.com | 10
5 Other Notes

www.Infovista.com | 11