About the Info Tab

The Info tab in the Test Session window provides the ability to monitor and "live-view" individual UE States/Information. Currently available in WiFi Offload Gateway Nodal (with RF Interface, GRE, CAPWAP, No Tunnel and Hybrid Access) and AMF Nodal, AMF Node, HA Nodal, IP Application Node with VoLTE, MME Nodal, Network Host and SGW Nodal, UPF Nodal for various Test Activity options.

NOTEs:

To enable the reporting of UE Info fields, UE Info Level should be set to > 1 on Test Server Configuration.
To enable VisionWorks features, UE Info monitoring must be enabled, UE Info Level should be set to 10 on Test Server Configuration and VisionWorks Results enabled on Customizing Report Options. For VisionWorks USER PLANE results, add the correct DMFs and enable L4-7 Per Session End of Test results. Additional configuration details can be found in the topic VisionWorks Solution.
To include IKE Keys in the info report, the UE Info Level should be set to 10 on Test Server Configuration.
When VisionWorks Results reporting is enabled, all of the Pass Fail Criteria and UE Info Criteria in the test session are included in the VisionWorks TEST.CRITS result file and additionally there are Test Case records summarizing each test case and a Test Session record summarizing the test session, as per the Data Model. The user can assign a SUT to a given Test Case or Test Session by putting the SUT name in the Test Case or Test Session name after ##, e.g. MyTestName##MySutName. If the SUT name is found in the TAS by name, the TAS will also populate the SUT_TYPE and SUT_IP with the associated values found in the TAS DB associated with that SUT. Test setup details can be found in the Visionworks Solution Topic.
The TEST.CRITS files will always be written out, even if the test does not start. (VisionWorks Results reporting must be enabled). The file will include the TEST_INIT_FAILED record.
In the Network Host test case, the UI shows number of UEs for Network Host, however it is number of Network Host Nodes and it is only enabled when Network Host number of Nodes > 0.
Network Host Test Case supports TEST.PROCS conversion only for Basic Data DMFs. Using Ping, UDP, TCP are the only ones guaranteed to report records. When Dual Stack is checked, the node count is read from the V4 node. V4 and V6 are required to have the same count.
When info_report is enabled and log level > 5, with IMS/Gm calls enabled, the TS will produce a new call.CSV file with per-call RTP KPIs in it. RTP Voice and Video KPI source file; one row per Call. Example name: 22-08-02_15.51.42__RID-819__ts0_tc0_call.csv.

NOTE: May get NULL Values for items that are not reported by your test case. When setting a UE Info Level X (1 to 10), that means that the UE Info component will include fields A, B, and C. But that does not mean the test will always report B or C, thus the UE Info report will show a column for B or C and it would be null. for example, if using level 9 and you do not do a POLQA on Default Bearer, you will get POLQA columns, but they will always be null.

The Info Tab is split into two sub tabs:

Configuration and Live view of UE Info - Setup/Live
Configuration of Pass/Fail Criteria based on the values inside the UE Info report - End of Test Criteria

UE Info Monitoring/Reporting (Setup/Live):

"Configure" the ranges of UEs to monitor and live report:

NOTES:

This feature is intended for tests with few Subscribers, as it is limited to 1000 UEs per Test Server (across all processes) to be monitored by the TS.
Window of 32 UEs that can be reported live in the GUI per TS (across all processes). This window can be changed on the fly, and can also query historical UE information from the TS.
The live data is current values, we do not maintain history in the Live reporting.
Per-Session type .csv file generated at the end of the test or during a test.
For APIs, an info_reposrt.csv file can be retrieved on a live test by Generating Per-Session Report (See respective Reference Docs GeneratePerSessionReport - Landslide Tcl API Object and Perform Function Reference). Using the RESTFul API contains reference information about the Landslide RESTFul API system. Refer to Swagger UI on Landslide Home Page, it contains the latest most accurate information for anything it covers.
At any time during the test you can generate the full .csv file to see full history of all monitored UEs.

UE Info Monitoring/Reporting Configuration tab components:

Test Case Interface	Test Case - List of available Test Cases that can be monitored. If no test cases are supported this will be displayed on Info Tab: The #UEs indicator in the test case column of the configuration provides a reference to how many are actually configured in the test case. While the test is running, we added First, Back, Next, and Last buttons to the live report view. This allows you to quickly change your subscribed reported UEs across the range of all UEs in the test case. When you click a button you are changing your UE Info configuration and sending a request to the TS to change the subscription. Your display still only refreshes on the Live Report Interval. You can click the button many times without seeing any updates, the TS will send up the update for the last received subscription at the end of the reporting interval. These buttons save you from having to open the configuration window each time just to page through all the UEs. The changes you make are persisted just the same, if you disconnect/reconnect to the test session. If your range does not line up evenly into pages, when you reach the last page, your Live Report First UE will be adjusted to be the last possible full range: "[Total UEs running in the test case] - [Live Report Total UEs] + 1". For example, if you have Starting UE=5, Total UEs 10, and there are 25 UEs in the test case, your first range would be 5-14, click next to get to 15-24, click next to get to 16-25, click back to get to 6-13, click back to get to 1-10, etc.. For example, If you only have 100 UEs and set a starting UE at 100 and # of UEs reported is 32, your range will be 100-31, but since UE 100 is last UE in test, you will only ever see UE 100, and First, Last, Forward, and Back buttons will be No-Ops. If either Live Report First UE or Live Report Total UEs == 0, then Live Reporting is disabled
Enabled	Use this Flag to Enable the Test Case for monitoring. Cannot Enable/Disable during "Live" test.
Monitor First UE	Enter First UE in the Test Case to monitor. Default = 1. Cannot edit during "Live run".
Monitor Total UEs	Enter total number of UEs to monitor. Default = 1000. Cannot edit during "Live run".
Live/ Report First UE	Enter First UE to monitor. Default = 1. Able to change during "Live" run.
Live/ Report Total UEs	Enter Total UEs to Monitor. Default = 32. Able to change during "Live" run. See Example of "Live" run below. If changed to zero during live run, reporting will stop however monitoring is still on. If total assignments to monitor exceeds the 1000/32 UE limits, this error will be displayed:
Report Interval (s)	Enter the Report Interval. How often the TS will report updated values for the UEs being monitored. If changed to zero during live run, a final update will be generated for all live UEs and periodic updates will stop. Range : 0 to 60 seconds (See Error if not in range)

Live view of UEs 3-6 on a Wifi Offload Gateway Nodal test case:

NOTE: When the Antennas report their ON/OFF status to the Info tab, they report it starting from the left and move right through all the Antennas. Once it encounters an Antenna in the off mode, it will stop scanning for Antenna status. For example, if Ant 1 and Ant 3 are turned on but Ant 2 is turned off, the Info tab will display that 1 Antenna is enabled. If Ant 1 is off and Ant 2 and Ant 3 are enabled, the Info tab will display no Antenna information.

May change the range of UEs being monitored live, by clicking on the button and changing the UE ranges.

The Live UE Info page has a few other features.

May switch current viewing Test Case , (as in Measurements/Reports.
Send request to TS to Generate the full .csv report, .
Query for historical information of selected row/cell/column, (or right-click). Can Query Historical data by UE, COL or Cell for Live Report UE's.
Table can be scroll-able (with horizontal scroll bar) in the window to expand the table columns wider or narrower than the window,

When a row, column or cell, is selected (or right-click mouse on row/cell) the Query button is enabled.

Query options:

Can Query Historical data by UE, COL or Cell for Live Report UE's.
Historical range limit: 1000,
Live UE limit: Max 32 Windows
Historical Query rows limit : Recent 200 records.

(Query selected UE's History), e.g. selected a single row, Query UE 6's history for all fields. This is just actual event recordings, time, field, new-value.

(Query selected UE's Field/Cell History), e.g. selected a single cell, Query UE 6 for TX_BIT_RATE history:

(Query selected Field/Column for all UEs), e.g. selected column, Query All UE’s for TX_BIT_RATE, see history of specific field across all live-reported UEs:

Results page is sortable by column.

The full monitored UE information results csv file will show up in end of test results:

Example content:

UE,TIME,COLUMN,VALUE

1, 09:36:24.327153,STATUS_OF_CLIENT,Idle

1, 09:36:24.327166,MAC_ADDR,f4:0f:2b:c1:4d:5c

2, 09:36:24.327756,STATUS_OF_CLIENT,Idle

2, 09:36:24.327765,MAC_ADDR,f4:0f:2b:c1:4d:5d

3, 09:36:24.327861,STATUS_OF_CLIENT,Idle

3, 09:36:24.327868,MAC_ADDR,f4:0f:2b:c1:4d:5e

4, 09:36:24.327954,STATUS_OF_CLIENT,Idle

4, 09:36:24.327958,MAC_ADDR,f4:0f:2b:c1:4d:5f

5, 09:36:24.328041,STATUS_OF_CLIENT,Idle

…

13, 09:38:43.718168,STATUS_OF_CLIENT,Idle

14, 09:38:43.933053,STATUS_OF_CLIENT,Idle

15, 09:38:44.119449,STATUS_OF_CLIENT,Idle

16, 09:38:44.319395,STATUS_OF_CLIENT,Idle

17, 09:38:44.519175,STATUS_OF_CLIENT,Idle

18, 09:38:44.719180,STATUS_OF_CLIENT,Idle

19, 09:38:44.918159,STATUS_OF_CLIENT,Idle

20, 09:38:45.118155,STATUS_OF_CLIENT,Idle

Values of STATUS_OF_CLIENT parameter when UE Info level is 10 and UE info monitoring / reporting configuration is enabled:

	Initial	Succeeded	Failed
LS start U1	Idle	Created	Failed to start
			Timeout to start
U1 registration			Failed to register
			Timeout to register
U1 read SIM			Failed to read SMS storage
			Timeout to read SMS storage
U1 attach		Connected	Failed to connect
			Timeout to connect
			Disconnected
LS get U1 ip			Failed to dhcp
			Timeout to dhcp
			Disconnected
LS & U1 ready for data traffic		Established	Disconnected

Configuration of Pass/Fail Criteria - End of Test Criteria

The End Of Test Criteria allows you to set up Pass/Fail Criteria based on the values inside the UE Info report. You define them on a test case basis via the Info Tab.

NOTEs:

Only test cases that support the UE Info Monitoring feature will show up on this tab.
The Criteria is checked once the test completes and the info file is retrieved from the Test Server.
The overall Pass/Fail Status of the test is calculated based on the ANDing of overall pass fail criteria, plus each Test Case UE Info Criteria. On the main Pass/Fail tab, there is an summary indication of Test Case UE Info Criteria Status.

The overall Pass/Fail Status of the test is calculated based on the ANDing of overall pass fail criteria, plus each Test Case UE Info Criteria. On the main Pass/Fail tab, there is an summary indication of Test Case UE Info Criteria Status.

On the End of Test Criteria sub tab, the Test Case list will indicate a summary Status for each Test Case. You can click on each Test Case to see the detailed list of criteria for that test case:

Criteria Status PENDING:

If your UE Info, info_report.csv is not produced at all or if it is empty, your UE Info Criteria status will remain PENDING, and there will be messages in your test Run Log, search for "UE Info".
If your TC doesn't have any UE Info Criteria, it's status will be PENDING.
PENDING is ignored in calculating the overall Criteria status, it is like saying we didn't do it for one reason or another.
If your UE Info Status is PENDING, but you have defined Criteria for that TC, check your setup: check your UE Info Enabler, UE Info Level, info_report itself.
You should not define UE Info Criteria until you have first configured your test, executed it and analyzed the info_report to understand what fields are there and their values.

The Test Case -level UE Info PF-Status is reported in the Run Log, and this hooks into the "failures" link on results website.

On results website you have the Criteria Failures link:

Which drives from the Run LOG:

http:///results/sms/11-29_08.44.45.AM__VoLTE-MME-AmrNb-BiDir-POLQA_10UEs_COAST4-6_wCrits_2__RID-2.log.txt

11/29 08:47:33.599:TAS: Generating final report(s)...

log: 11/29 08:47:33.599:TAS: Evaluating UE Info Criteria

log: 11/29 08:47:33.711:TAS: MME Nodal [MME Nodal]/ : FAILED

criteria: MME Nodal [MME Nodal]/ : FAILED

log: 11/29 08:47:33.711:TAS: UE Info Criteria Done

To give you just this:

http:///failedCriteria.cgi?sms+11-29_08.44.45.AM__VoLTE-MME-AmrNb-BiDir-POLQA_10UEs_COAST4-6_wCrits_2__RID-2.log.txt

Failed Criteria

criteria: MME Nodal [MME Nodal]/ : FAILED

This is in lieu of printing every single UE Info PASS Fail Criteria in the main Run Log, instead they are in a separate csv file (seen in above listing):

http:///results/sms/11-29_08.44.45.AM__VoLTE-MME-AmrNb-BiDir-POLQA_10UEs_COAST4-6_wCrits_2__RID-2__ue_info_criteria.txt

ts,tc,crit,condition,status

0,0,-1,MME Nodal [MME Nodal]/ ,FAILED

0,0,0,[ PASS if (Field.UE_IP == 26.0.0.1) ],PASSED

0,0,1,[ PASS if (Field.QCI >= 9 ( for UE <= 1 )) ],FAILED

0,0,2,[ PASS if (Field.EBI == 5 ( for UE >= 1 )) ],PASSED

0,0,3,[ PASS if (Field.PRIVATE_URI matches sip.*) ],PASSED

0,0,4,[ PASS if (Field.ECGI == 000.000.1 ( for UE-Bearer with Field.IMSI == 505024101215074 )) ],PASSED

NOTE: For UE Info Criteria to work properly, UE Info monitoring must be enabled, UE Info Level should be set to 10 on Test Server Configuration (or less if you know which fields are produced).

UE Criterion Editor

Use the UE Criterion Editor (Add/View/Edit) to create Info Pass/Fail Criteria.

Learn more about:

Example Criteria