A4.Pilot Pioneer Operation Guide V10.4 PDF
A4.Pilot Pioneer Operation Guide V10.4 PDF
A4.Pilot Pioneer Operation Guide V10.4 PDF
Contents
Contents
1 Product Overview .................................................................................................................. 1
4.7.1 5G NR Report.................................................................................................... 84
5 Appendix ............................................................................................................................... 85
5.1.2 MOS.................................................................................................................... 87
5.1.6 Ping..................................................................................................................... 93
1 Product Overview
1.1 Introduction to Pilot Pioneer
Pilot Pioneer is a real-time multi-technology mobile network and services performance, test and
measurement solution. Pilot Pioneer runs on MS Windows 10/8/7 operating system, and utilizes
the latest smartphone test devices and frequency scanners for the measurement collection.
2 Software Installation
Users need to install required drivers and components before installing Pilot Pioneer.
2. Antivirus software in the computer may cause installation failure or abnormal operation,
please close the antivirus software and re-install Pioneer Drivers or add Pioneer Drivers to
5. Select components to install on the Choose Components window that appears, and click Next.
The components that are selected by default are required to run Pilot Pioneer. Users may
Note: If your PC has already installed the components and drivers, it is unnecessary to re-install
Component Description
The basic component of Microsoft .net framework.
Microsoft .net Framework4
Users need to install it for the first use of Pilot Pioneer.
Event speech engine program, based on which the audio
Event Speech Engine Pack alarm can be reported for events in Pilot Pioneer. It is
recommended to install.
MOS Driver and POLQA MOS test driver. Users may install it based on the actual
Environment test requirements.
TCP/IP sniffer component. Users may install it based on
TCP/IP Monitor Pack
the actual test requirements.
Windows and R&S Scanner SDK Components for R&S scan test. Users may install it
Pack based on the actual test requirements.
Microsoft XML package. Users need to install it for the
Microsoft XML 4 Pack
first use of Pilot Pioneer.
Run Selected Components The default system component. Users need to install it.
6. Install the selected components. The figure below shows the Installation Wizard windows for
7. After the installation is completed, click Finish on the Pioneer Drivers Setup window.
3. Select a dongle type based on the actual situation. Users must select Dongle Driver, and
5. After the installation is completed, click Finish on the Pilot Pioneer Setup window.
Note: There are three solutions for 5G test, i.e. 5G hard dongle (i.e. Blue Hard Dongle, and
Black Hard Dongle) & 5G protection key (i.e. Soft Dongle). Users may select one solution as
required.
http://61.143.60.83:8000/home) to activate and update 5G protection key online. Please see the
3. Copy the license activation key that is received in mailbox to DingLi Products License
Client, and click Login.
5. After the 5G protection key is activated, a successful activation prompt will be displayed
in the interface.
4. After the 5G protection key is updated, a successful activation prompt will be displayed in
the interface.
*Note: After 5G protection key is activated or updated successfully, start Pilot Pioneer. If users
can successfully start Pilot Pioneer, 5G protection key is activated or updated successfully;
otherwise, please contact DingLi technical support.
Pioneer. If no dongle is inserted, users may not run the Pilot Pioneer software.
Figure 2-22 Hardware dongle (Black Hard Dongle)
The “License Query” interface where users can view the Key ID, expiration data and other
permissions information (e.g. terminals, RATs, services, functions, reports and analysis), and online
upgrade option, is shown as follow. If the user wants the access to the online upgrade function,
he/she needs to select "HASP Dongle Driver and Update Tool" on Figure 2-5 installation interface.
Figure 2-24 License Query
3 Test Procedure
3.1 Project Management
The Project is the basic unit for data management and maintenance in Pilot Pioneer. Pilot Pioneer
operations are based on projects. Therefore, a new project must be created before users can perform
In addition, the external devices, test plan, test data, site database, and the workspaces can be saved
as projects. Once a saved project is opened, all relevant information will be loaded automatically.
Users may click New/Open Project ( ) on the Menu bar to create a new project. If the user
creates, edits and then saves a new project, a dialog box which informs the user to whether save the
edited new project will appear.
In addition, if the user uses Pilot Pioneer for the first time or does not save any project before, the
software will automatically create a new project.
to open the recently saved project? Users may click Yes to open it or click No to create a new project.
Users can also click beside the button to view the previous saved projects.
Users may click the Save Project button ( ) on the Toolbar to save a project. When users
terminate the software, Pilot Pioneer will display a dialog box for users to select whether to save a
drivers are installed. Otherwise, Pilot Pioneer may not collect data or control test devices.
There are two device configuration methods: automatic detection and manual configuration. For
GPS and test devices, users may use the one-click automatic detection method. However, in some
special cases (e.g. automatic detection failed) or for some special test devices (e.g. scanner), users
After the required drivers have been installed, users need to make sure that the device port has
been identified by the computer and detected by Pilot Pioneer in either mode.
Right-click Computer and select Manage, click Device Manager, and make sure that the device
❖ Detect devices
Click Test on the navigation pane. If Pilot Pioneer detects a device, a corresponding message will
be displayed. See the figure below (the number N indicates that a number of N devices have been
4. Select I accept the terms in the license agreement, and click Next in the License
Agreement window.
6. Click Finish in the InstallShield Wizard Completed window to complete the installation.
handset settings.
1. Dial *#0808# in the handset.
3. Start Pioneer Tools to check the connection status of Pilot Pioneer and the handset. If
the handset is connecting to the Pilot Pioneer, Service Status will be displayed as
“Waiting…” in Pioneer Tools.
© DingLi 24-06-2020 DL1104PG 21
Test Procedure
Automatically Detect Device: Click (Automatic Detection) button to identify the handset’s
Note: Please add the device manually and enter relevant port information for the handset that is
connected to Pilot Pioneer for the first time. (Trace Port corresponding to MSM port, 5G Trace
Manually Add Device: Click (Add Device) button to enter Manual Configuration
window, and select corresponding handset model and ports. (4GTrace port
2. Device Connection:
• Start PioneerTools.
disconnect the device from Pilot Pioneer, close all programs in the handset, restart
PioneerTools, and click (Connect) in Pilot Pioneer to connect the device to Pilot
Pioneer again.
handset settings.
2. Install HiSilicon driver (Connect the phone with PC in ‘Transfer files’ mode and run the Hisuite
to install driver). After finish, reconnect and switch to ‘Charge only’ mode.
window, select corresponding handset model and ports, and click OK.
6. Click (Connect) in Pilot Pioneer to connect the device to Pilot Pioneer, and PioneerTools
will automatically be enabled and popped up. View if the License Status is displayed as “Valid”
Note: Please add the device manually and enter relevant port information for the handset that is
connected to Pilot Pioneer for the first time. (Trace Port corresponding to Application Interface
port)
Manually Add Device: Click (Add Device) button to enter Manual Configuration
window, and select corresponding handset model and ports. (Trace port
2. Device Connection:
• Start PioneerTools.
disconnect the device from Pilot Pioneer, close all programs in the handset, restart
PioneerTools, and click (Connect) in Pilot Pioneer to connect the device to Pilot
Pioneer again.
automatically. ④Install HiSuite on the PC and disable the function Automatically Start When
2. Enable the 5G function under Settings> Mobile network>Mobile data in the phone.
3. Set the handset to data centric mode: ①Dial *#*#2846579159#*#* on the handset; ② Select
6. Set the handset’s service domain to PS only: ① Dial *#*#2846579159#*#* on the handset;
7. Connect the handset to the PC with USB cable and enable the test port: ① Dial
Click Test, and click the Automatic Detection icon ( ; shortcut key: F5) on the toolbar to
If the device is used for the first time, users need to select the correct handset model (such as
SAMSUNG Note 10+5G here as an example) when the window as shown in the figure below is
displayed:
After the automatic detection is completed, the device will be listed under Handset on the Test
window. Users may click Yes on the dialog box as shown in the figure below to directly connect
It is recommended to double click the connected device to verify the configuration information
after the automatic detection. The figure below shows the correct configuration for a test device:
Users may configure devices manually after devices are connected or when automatic detection fails.
1. Click Test, and double-click Handset to enter the Manual Configuration window.
2. Configure required information based on the actual situation, e.g. device name, trace port for
data collection, AT port, Modem, and Network (highest network technology supported by the
device).
3. Click OK to complete the configuration and exit the device configuration, or click Apply to
exclamation mark (see the figure below). In this case, users may try to plug out and plug in the
After the handset is successfully connected to Pilot Pioneer, the corresponding 5G NSA Events
After adding devices, choose Test> Handset, and click a device under Handset. Test template
1. Click Test, click a device, and then the default test plan templates will be displayed under
TestPlan.
2. If the required test service is not available under Test Plan, click or right-click a test
template and select Add to enter the Add Test Plan window, select the test service type, and
then click OK.
Figure 3-25 Add a test plan
After adding a test plan, users may double click it or right-click it and select Edit to configure
select multiple (at least two) configured test plans to execute them based on the sequence.
1. Add multiple test plans and configure required information by referring to the instructions in
section 3.3.1.
2. Select multiple test plans as required. This way, Pilot Pioneer will execute the selected test
services by sequence.
For example, Pilot Pioneer will execute the Call, FTP Upload, and FTP Download by
sequence if these test plans are selected as shown in the figure below:
users may perform FTP Download and FPT Upload tests simultaneously.
1. Click or right-click a test template and select Add to enter the Add Test Plan window.
2. Select multiple services (at least two) for Multi-service tests, and then select Multi-RAB.
Note: If the Multi-RAB option turns grey and is invalid, it indicates that the selected services
3. Click OK to add the services into the test plan list in the navigation pane.
4. Double click or right click the added test plan to configure required information, and click OK.
Figure 3-29 Configure required information
settings. Users may configure required information based on the actual test requirements.
to collect test information, observe real time status, and save test information into log files.
aware that the data collection options need to be configured before recording the data. Users may
click button on the top right corner, and then select Configuration>Options to enter the
select the NR frame information which need to be collected. Users can also keep the default settings.
Figure 3-33 Data collection configuration
1. Configure the device and test plans by referring to section 3.2 and section 3.3 herein
respectively.
2. Click on the tool bar (shortcut key: F6) to enter the connection mode.
Once the device is successfully connected to Pilot Pioneer, the software will display the current
test information, and the user can start to perform various tests.
If the connection failed, a message box as shown in the figure below will be displayed.
➢ If users click Ignore, Pilot Pioneer will ignore the device with the connection failure, and
➢ If users click Reconnect, Pilot Pioneer will try to reconnect the device with connection
failure.
➢ If users click Disconnect, Pilot Pioneer will disconnect all devices and go back to the
disconnected mode.
Note: Users may check the device driver, plug out and plug in the derive, or restart the
➢ Users may identify the probable root cause according to the connecting information as shown
in the Figure 3-35, or send the error code to DingLi technical support if there is only error code
➢ If the failed-connection device is enabled, please view the corresponding port information in
➢ If there is abnormal port information, please plug out and plug in the device, or restart the
If the connection is successful, the workspace will display information status windows such as
Message, Event List, Line Chart, Map and Device Control by default if there are none loaded
previously.
directory.
Users may click the Start Recording icon ( ) on the toolbar, or press the shortcut key F7 to enter
Users may set the logfile name as required. The log file name consists of the user defined part and
The log file is saved in the LogData directory in the installation path of Pilot Pioneer by default.
The *.ddib logfiles in the LogData directory are decoded files, while the *.rcu log files in
\LogData\BackupLogFiles are non-decoded files. Users may edit the target directory for the
logfiles to save.
Name Description
VoLTE Test
(Save VoLTE Save the frame information during VoLTE test. It is recommended to
information)
Test Save some additional information to the logfiles, e.g. province, city,
1. Users may also click on the tool bar or press the shortcut key F8 to open the window.
2. Click Test Plan to modify or verify test plan corresponding to the selected device before the
test starts.
3. For mobile to mobile call test and MO-MT MOS test, select MT terminal under Dialed MS
for the selected device. Users only need to configure test information for MO terminal.
• / / : to start, stop or pause the service test corresponding to the selected device.
• Click after the service test has started to pause the service test, and the icon will be
changed into which indicates that the service test has been paused. Users may click
• Tag: to add tags for the selected device on the Event window. Options: Insert Start/End
Users may also view the service test information on this window, e.g. test count, test failure count,
etc.
❖ For AT Cmd option, users may enter AT command in AT Cmd window as shown below,
and then click Send to send AT command. The AT commands will be displayed in the right
pane of the AT Cmd window, and the send result in the left pane.
For more details about AT Cmd configuration, please refer to section 3.4.6
Figure 3-40 AT Cmd window
users may lock the network and cell, force reselection, and force handover, etc. Different test
1. Connect the test device and enter the Connection or Recording mode.
2. Select a device, and click the drop-down arrow ( ) next to a command to send the force
command to the device. For some commands (e.g. SetAPN, Lock Band, Lock Cell, etc.), the
3. After the force command is executed, corresponding Force Event will be recorded to the
Event window. Users may observe the Layer 3 message, network/cell information, or device
The table below describes the force commands for Samsung Note10+ 5G:
connection)
Lock/unlock Auto Network Mode Enable the device to support any network.
device.
1. Click on the tool bar (shortcut key: F6) to enter the connection mode, or click the Start
Recording icon ( ) on the toolbar (shortcut key: F7) to enter the recording mode.
2. Click on the tool bar or press the shortcut key F8 to open the window shown as below.
4. Select a terminal that needs AT command control under Device List, and then click Connect
5. Select a AT command from Default drop-down list box, and then click Send to send the
command to the terminal; or select Custom from Default drop-down list box, enter the user-
defined command in CMD box, and then click Send to send the command.
Users may right click the custom command in CMD box, and select Set as Default to add the
6. Set interval to send AT command(s) sequentially in a cycle manner under Start cycle to send
interval option.
7. View the AT command in the right pane of the AT Cmd window, and send result in the left pane.
All or multiple AT command execution records and results can be copied, exported, cleared, etc.
etc. or import the offline maps as required. The offline map format includes MapInfo(*. Tab,
iBWave(*.ibwc).
Load online maps: Click the drop-down arrow as shown in the figure below on the Map window to
Cancel online maps loading: Click the button in the online maps list.
1. Click Layer tab, and then double click the offline map format based on actual situation under
3. Drag the offline map which has been imported in the software to the Map window, to display
If the user wants to delete the imported offline map, he/she may right click the offline map which
database samples in *.txt and *.xls format. Before importing the cell site database to the software,
users need to complete the database based on the actual cell sites information for the test.
After configuring cell site database, click Layer tab, double click the network technology
corresponding to the cell site database which needs to be imported under Site or right click the
network technology to select Import, and then select a cell site database file from local PC.
Pilot Pioneer supports various network-based cell site databases import. Once the cell site database
is imported to the software, Pilot Pioneer will automatically identify and match the mandatory
information written in cell site database. If the software fails to identify and match the mandatory
information, there will be a manual configuration window for users to match the information
manually.
➢ Cell Settings
Users can also click button on the Map window to set such information as cell display,
Pilot Pioneer V10.4 supports entire or partial dedicated cell site database export, which facilitate
users' subsequent database use and information sharing. To export cell site database, follow the
Method one: Right click the cell site database that the customer wants to export under Site, and then
select Export.
Method two: Right click Site or the network technology corresponding to the cell site database
which needs to be exported, select Site Data Base Manager, select all or partial cell sites in the
Users need to right click Site, cell site database which needs to be deleted, or the network technology
corresponding to the cell site database which needs to be deleted, and then select Close.
Pilot Pioneer.
➢ Common Pinpointing
2. Drag the imported indoor map from Layer tab to the Map window.
3. Click the drop-down arrow beside button in Map window, and select Pinpoint to
2. Drag the imported indoor map from Lay tab to the Map window.
3. Click the drop-down arrow beside button in Map window, and select Customize Path
4. Left click the mouse to customize a path on the indoor map, and then double click the mouse to
5. Click the drop-down arrow beside button in Map window, and select Pin point
6. Click the button in the tool bar in Map window to pinpoint a predefined test route on
➢ Remove, restore pinpoints on the test route and inverse the removal
Users may click to remove all pinpoints on the test route, click to restore the pinpoints
Figure 3-52 Remove, restore pinpoints on the test route and inverse the removal
scene, users may collect and save some test information that they focus on as required, and to view
1. Click the drop-down arrow next to and open a scene as required to view various test
2. Directly drag the logfiles under Data List to the scene windows on the Workspace to display
Note: As CSFB and VOLTE test scenes load MO and MT test data synchronously, users need to
drag both MO and MT test data to the upper zone and lower zone in the scene window respectively.
Network. After the logfile is decoded, only the network technology related to the logfile will be
displayed under Network. Pilot Pioneer displays test information tab according to the network
2. Select a window, and double click the information windows (e.g. Message, Event List, Line
Chart, Map, Table, Statistics) under Network to display the test information in the
corresponding windows. Or directly drag logfiles under Data List to the windows to
During real-time test information display, users may click on a window or right lick to select
Freeze window to view the test information. Users may also click on the tool bar to freeze
all windows on the workspace. The information can be synchronized to all windows after users
freeze a window.
All the test data will be stored in the location set by the user in accordance with section 3.4.1.1
herein, or users may right click the logfile under Data List and select Open Log Path to view the
All the non-decoded data (in the format such as RCU, DCF, etc, but except *. ddib format) will be
Users may right click the logfile under Data List and select Test Plan Log to view test plan
information.
Users may right click the logfile under Data List and select Test Information to view general test
information, such as terminal name, test start time, test duration, test distance, etc.
1. Double click the information windows which the user wants to replay under Network.
2. Click the button on tool bar to display replay icon, such as the pause button, speed
3. Slide (left or right) the speed toolbar and position toolbar to synchronize the information in
2. Select an imported logfile, open windows (e.g. Message or Table) as required, and click
icon to replay the data.
Scanner Data:
Handset Data
Click Lay Control icon ( ) to enter the Layer Manager window, and set the X or Y axis
Export File Struct: Set the template to export scanner source file.
the cursor over Parameter and click the icon in the position marked as 1 in
✓ Define filter conditions as required in the page that appears, e.g. define the filter name
in the position marked as 2 and define the expression as the filter condition in the
✓ Click Save to save the settings. The defined conditions will be dispalyed in the
appear.
Select data to export: Select a start data as required, and then click Copy Data icon; select an end
Select Partition>Partition By Region, and click Add to import the *.zdf logfile that is saved in the
previous step (the customized region logfile exported from Pilot Pioneer).
network problems through the analysis of measurement samples, events, parameters, etc. Analysis
function such as Measurement Over Distance Analysis, Coverage Rate Analysis, Antenna Feeder
Reversed Analysis, Parameter Quadrant Analysis, Diff Value Analysis, etc. is supported. Hereinafter,
we take Antenna Feeder Reversed Analysis, Measurement Over Distance Analysis and Overlapping
information as required.
4.7.1 5G NR Report
5 Appendix
5.1 Default Test Plans
5.1.1 Call
Figure 5-1 Call test settings window
The parameters as shown in the rectangle are mandatory. Users need to set the parameters based
on the actual test requirements. For other parameters, users may keep the default settings. The
5.1.2 MOS
Figure 5-2MOS test settings window
The parameters as shown in the rectangle are mandatory. Users need to set the parameters based
on the actual test requirements. For other parameters, users may keep the default settings. The
The parameters as shown in the rectangle are mandatory. Users need to set the parameters based
on the actual test requirements. For other parameters, users may keep the default settings. The
General
Server Host The FTP server IP address.
Options Port The FTP server access port number.
The FTP server username.
Username Attention: Make sure that user has the right to do the
corresponding test.
Password The password for the FTP server account.
Test File to
The download file path on the FTP server.
Options Download
Directory The local path for the downloaded file.
Cycle Count The number of test cycles.
Infinite Select this option to test indefinitely.
Duration (s) The download duration after selecting By Time.
By Time The settings for Duration takes effect only after this option is
© DingLi 24-06-2020 DL1104PG 89
Appendix
The parameters as shown in the rectangle are mandatory. Users need to set the parameters based
© DingLi 24-06-2020 DL1104PG 90
Appendix
on the actual test requirements. For other parameters, users may keep the default settings. The
General
Server Host The FTP server IP address.
Options Port The FTP server access port number.
The FTP server username.
Username Attention: Make sure that user has the right to do the
corresponding test.
Password The password for the FTP server account.
Test Upload File The local path of the file to be uploaded.
Options Directory The local path for the downloaded file.
Cycle Count The number of test cycles.
Infinite Select this option to test indefinitely.
Duration (s) The download duration after selecting By Time.
The settings for Duration takes effect only after this option is
selected, and the test will be terminated when the duration
By Time exceeds this specified value. Otherwise, the test will proceed
until the file is completely downloaded or the duration exceeds
the value specified by Timeout.
The maximum time, in seconds, for each FTP Upload test to
complete. If the specified file is not completely uploaded to the
Timeout (s)
FTP server during this specified time, the upload will be
terminated.
The time, in seconds, to be allowed between successive FTP
Interval (s)
tests.
Failure The interval between the end of a failed test and the start of the
Interval (s) next test.
Advanced
Test Thread Count The thread count.
Options No Data
The timeout, in seconds, when no data is received.
Timeout (s)
The parameters as shown in the rectangle are mandatory. Users need to set the parameters based
on the actual test requirements. For other parameters, users may keep the default settings. The
5.1.6 Ping
Figure 5-6 Ping test settings window
The parameters as shown in the rectangle are mandatory. Users need to set the parameters based
on the actual test requirements. For other parameters, users may keep the default settings.The
General
Packet Size
The size of packets to be sent in the Ping test. The unit is Byte.
Test (B)
Options Timeout The maximum time, in milliseconds, for each Ping test to
(ms) complete.
The time, in seconds, to be allowed between successive Ping
Interval (ms)
tests.
Cycle Count The number of test cycles.
5.1.7 PBM
Figure 5-7 PBM test settings window
The parameters as shown in the rectangle are mandatory. Users need to set the parameters based
on the actual test requirements. For other parameters, users may keep the default settings. The
The parameters as shown in the rectangle are mandatory. Users need to set the parameters based
on the actual test requirements. For other parameters, users may keep the default settings. The
General
URL Address The URL address of the video file.
Quality Select a play quality based on the selected video type.
Play Type Select a play type: By time or By percentage.
Video play duration. Unit: seconds. This option is available
Play Duration
only when By time is selected as the Play Type.
The settings for Play Duration takes effect only after this
option is selected, and the test will be terminated when the
By Time duration exceeds this specified value. Otherwise, the test will
proceed until the file is completely played or the duration
exceeds the value specified by Timeout.
The video play will be terminated when the actual play
Play
percentage exceeds this user-defined value. This option is
Percentage (%)
Test available when By percentage is selected as the Play Type.
The settings for Play Percentage takes effect only after this
Options
option is selected, and the test will be terminated when the
By Percentage play percentage exceeds this specified value. Otherwise, the
test will proceed until the file is completely played or the
duration exceeds the value specified by Timeout.
The maximum time, in seconds, for each Video Play test to
Timeout (s)
complete.
Failure The interval between the end of a failed test and the start of
Intervals (s) the next test.
Cycle Count The number of test cycles.
Advanced
5.1.9 UDP
Figure 5-9 UDP settings window
All items in the above interface are mandatory, and need to be configured as required. The
2. Make sure the device driver is normal under the Device Manager of the PC.
4. Make sure the LTE network is normal. Enable Mobile Data on the mobile phone, and check if
the 4G network icon is displayed on top of the phone screen, or check if the device can access
the network. Then disable Mobile Data. If LTE network exception occur, check the LTE
Radio Measurement window on Pilot Pioneer to judge whether the current signal strength and
failure still occurs, users may verify the driver and the system environment on the PC. Follow
© DingLi 24-06-2020 DL1104PG 98
Appendix
a. If the force commands are executed successfully, but the dial-up connection duration
exceeds 20 seconds, Pilot Pioneer will report a dial-up failure during service tests as the
dial-up timeout value is set to 20 seconds by default. In this case, users may do as
follows:
• Disconnect the USB cable from the PC, and restart the phone and PC.
b. If the force commands are executed successfully, users may directly start the service test.
c. If the force commands are executed unsuccessfully, it is recommended to plug out and
plug in the phone or restart the phone. Users may wait for one to two minutes and observe
Examples:
• For FTP test failure, users may use File Zilla to conduct tests with the same test task
configuration after the dial-up connection is established. If the test is successful, then
the problem may be caused by the Pilot Pioneer software. If the test is failed, the
problem may not be caused by Pilot Pioneer software.
• For dial-up connection failure during test task execution, users may enable Mobile
Data on the phone and check the accessibility of the internet.
• For voice call failure, users may manually dial up the numbers and check if the test is
successful.
column.
2. Event window: Check the call process events, e.g. Call Attempt, Call Established, Call
End. Abnormal events (e.g. Blocked Call, Dropped Call) will be highlighted (in red).
5.4.2 MOS
1. Device Control window: Check if service failure information is displayed under the Fail
2. Event window: Check the call process events, e.g. Call Attempt, Call Established, Call
End. Abnormal events (e.g. Blocked Call, Dropped Call) will be highlighted (in red).
Check the MOS result (POLQA/PESQ Result) and if the MOS score is too low (lower
than 2.4 by default) or varies widely. Abnormal events (e.g. MOS Double Mute, MOS
Single Mute, MOS Value Too Low) will be highlighted (in red).
information (instantaneous and average data throughput) will be displayed under the
Other Info column. If the service execution is failed, the failure count will be displayed
2. Event window: Check the key events, e.g. Network Connect Start, Network Connect
Success, FTP Download First Data, FTP Download Last Data, etc. Abnormal events (e.g.
Network Connect Failed, FTP Download Drop) will be highlighted (in red).
information (instantaneous and average data throughput) will be displayed under the
Other Info column. If the service execution is failed, the failure count will be displayed
2. Event window: Check the key events, e.g. Network Connect Start, Network Connect
Success, FTP Upload First Data, FTP Upload Last Data, etc. Abnormal events (e.g.
Network Connect Failed, FTP Upload Drop) will be highlighted (in red).
5.4.5 Ping
1. Device Control window: If the service test execution is normal, the information about the
© DingLi 24-06-2020 DL1104PG 100
Appendix
success rate, average delay, maximum and minimum values will be displayed under the
Other Info column. If the service execution is failed, the failure count will be displayed
2. Event window: Check the key events, e.g. Network Connect Start, Network Connect
Success, Ping Start, Ping Success, etc. Abnormal events (e.g. Network Connect Failed,
2. Device Control window: If the service test execution is normal, data throughput
information (instantaneous and average data throughput) will be displayed under the
Other Info column. If the service execution is failed, the failure count will be displayed
3. Event window: Check the key events, e.g. Network Connect Start, Network Connect
Success, HTTP Page First Data, HTTP Page Last Data, etc. Abnormal events (e.g.
Network Connect Failed, HTTP Page Drop) will be highlighted (in red).
5.4.7 PBM
1. Device Control window: If the service test execution is normal, data throughput
information (instantaneous and average data throughput) will be displayed under the
Other Info column. If the service execution is failed, the failure count will be displayed
2. Event window: Check the key events, e.g. Network Connect Start, Network Connect
Success, PBM Finish etc. Abnormal events (e.g. PBM Failure) will be highlighted (in
red).
2. Device Control window: If the service test execution is normal, data throughput
information (instantaneous and average data throughput) will be displayed under the
Other Info column. If the service execution is failed, the failure count will be displayed
3. Event window: Check the key events, e.g. Network Connect Start, Network Connect
Success, Video Play First Data, Video Play Last Data, Video Play vMOS Report, Video
Play Finish, etc. Abnormal events (e.g. Network Connect Failed, Video Play Drop) will be
5.4.9 UDP
Users may pay attention to the following items to judge whether the UDP service test execution is
normal.
1. Event window: Check the key events, e.g. UDP Connect Start, UDP Connect Success, UDP
Start, UDP End, UDP Finish, UDP Disconnect, etc. Abnormal events (e.g. UDP Connect
2. Device Control window: If the service test execution is normal, data throughput
information (instantaneous data throughput) will be displayed under the Other Info column.
3. Throughput window: Check whether the throughput in PHY, MAC, etc. layer is 0.