100.5.4 Event List
|
Event Name |
Symb. |
Extra Info1 |
Associated KPI |
Refined |
|
ABM events: Only available during logfile replay. |
||||
|
ABM Error |
|
Cause |
– |
✔ |
|
ABM Start |
|
For each ABM server: Server ID; Server IP address; Server port |
– |
✔ |
|
ABM Stop |
|
– |
– |
✔ |
|
AQM events (VoIP): Test setup in UM section "Voice Quality" |
||||
|
AQM Session Complete |
|
Phone number; Other party phone number; Log index; Synch time; Measurement type |
– |
|
|
AQM Session Failure |
|
Phone number; Other party phone number; Log index; Synch time; Measurement type |
– |
✔ |
|
AQM Session Start |
|
– |
– |
✔ |
|
AQM Session Stopped |
|
Phone number; Other party phone number; Log index; Synch time; Measurement type |
– |
|
|
Attach Failure |
|
– |
|
|
|
Attach Setup Time |
|
Time in ms |
|
|
|
DNS Host Name Resolution Failure |
|
Domain name(s); DNS server address |
– |
✔ |
|
DNS Host Name Resolution Time |
|
Domain name(s); DNS server address; Resolution time in seconds |
– |
✔ |
|
Dropbox events: Test setup in UM sections "Dropbox Logon"–"Dropbox Logoff" |
||||
|
Dropbox Logoff Attempt |
|
Timestamp |
Close and clear token information sent from OnDevice Dropbox Service. |
✔ |
|
Dropbox Logoff End |
|
Status |
Logon script activity ended. |
✔ |
|
Dropbox Logoff Error |
|
Cause |
Logoff failed. |
✔ |
|
Dropbox Logoff Start |
|
– |
Logoff script activity started. |
✔ |
|
Dropbox Logoff Success |
|
Duration of logoff procedure in seconds |
Logoff finished when Dropbox session closed. |
✔ |
|
Dropbox Logon Attempt |
|
Timestamp |
Logon request sent to Dropbox server. |
✔ |
|
Dropbox Logon End |
|
Status |
Logon script activity ended. |
✔ |
|
Dropbox Logon Error |
|
Cause |
Failure to retrieve access token. |
✔ |
|
Dropbox Logon Start |
|
– |
Logon script activity started. |
✔ |
|
Dropbox Logon Success |
|
Duration of operation procedure in seconds |
Logon finished when active session with valid access token is received. |
✔ |
|
Dropbox Operation Attempt |
|
Timestamp |
Request sent from OnDevice Dropbox Service. |
✔ |
|
Dropbox Operation End |
|
Status |
Script activity ended. |
✔ |
|
Dropbox Operation Error |
|
Cause |
Operation failed. |
✔ |
|
Dropbox Operation Start |
|
Type of operation |
Script activity started. |
✔ |
|
Dropbox Operation Success |
|
Duration of operation procedure in seconds |
Operation successfully completed. |
✔ |
|
Email receive events: Test setup in UM section "Email Receive" |
||||
|
Email Receive Data Transfer Cutoff |
|
Cause |
– (No KPIs defined for email) |
|
|
Email Receive End |
|
Outcome |
✔ |
|
|
Email Receive Error |
|
Cause |
✔ |
|
|
Email Receive First Data |
|
– |
|
|
|
Email Receive Start |
|
POP3 server IP address or host name |
✔ |
|
|
Email send events: Test setup in UM section "Messaging Activities" |
||||
|
Email Send Data Transfer Cutoff |
|
Cause |
– (No KPIs defined for email) |
|
|
Email Send End |
|
Outcome |
✔ |
|
|
Email Send Error |
|
Cause |
✔ |
|
|
Email Send First Data |
|
– |
|
|
|
Email Send Start |
|
SMTP server IP address or host name |
✔ |
|
|
Facebook events: Test setup in UM sections "Social Networking Activities"–"Facebook Logoff" |
||||
|
Facebook Logoff Attempt |
|
Timestamp |
Close and clear token information sent from on-device Facebook service. |
✔ |
|
Facebook Logoff End |
|
Timestamp; Status |
Logoff script activity ended. |
✔ |
|
Facebook Logoff Error |
|
Cause |
Logoff failed. |
✔ |
|
Facebook Logoff Start |
|
– |
Logoff script activity started. |
✔ |
|
Facebook Logoff Success |
|
Duration of logoff procedure in seconds |
Logoff finished when Facebook session closed. |
|
|
Facebook Logon Attempt |
|
Timestamp |
First HTTP Get Request sent to Facebook server. |
✔ |
|
Facebook Logon End |
|
Timestamp; Status |
Logon script activity ended. |
✔ |
|
Facebook Logon Error |
|
Cause |
Failure to retrieve access token. |
✔ |
|
Facebook Logon Start |
|
– |
Logon script activity started. |
✔ |
|
Facebook Logon Success |
|
Duration of logon procedure in seconds |
Logon finished when active session with valid access token is opened. |
|
|
Facebook Operation Attempt |
|
Timestamp; Operation type |
Request sent from on-device Facebook service. |
✔ |
|
Facebook Operation End |
|
Operation status; Operation type |
Script activity ended. |
✔ |
|
Facebook Operation Error |
|
Cause; Operation type |
Operation failed. |
✔ |
|
Facebook Operation Start |
|
Operation type |
Script activity started. |
✔ |
|
Facebook Operation Success |
|
Duration of operation in seconds; Operation type |
Operation successfully completed. |
|
|
"First" events: These events relate to TCP. |
||||
|
First ACK |
|
Service type |
TCP session establishment: ACK sent from client. |
|
|
First HTTP Get |
|
Service type |
First HTTP Get during TCP session. |
|
|
First HTTP Post |
|
Service type |
First HTTP Post during TCP session. |
|
|
First Packet With Content |
|
Service type |
First payload packet transferred during TCP session. |
|
|
First SYN |
|
Service type |
TCP session establishment: SYN sent from client. |
|
|
First SYN ACK |
|
Service type |
TCP session establishment: ACK to SYN received from server. |
|
|
FTP Service Command |
|
Service type, Command |
FTP packet containing RETR or STOR command was sent. |
|
|
FTP events, download: Test setup in UM section "FTP Download". Not obtained for SFTP. |
||||
|
FTP Download Data Transfer Cutoff A/B |
|
Cutoff point |
✔ |
|
|
FTP Download Data Transfer Time A/B |
|
Time in seconds |
✔ |
|
|
FTP Download End |
|
Outcome |
– |
✔ |
|
FTP Download Error |
|
Cause |
– |
✔ |
|
FTP Download IP Service Access Failure A/B |
|
Details of failure |
✔ |
|
|
FTP Download IP Service Setup Time A/B |
|
Time in seconds |
✔ |
|
|
FTP Download Mean Data Rate A/B |
|
Data rate in kbit/s |
✔ |
|
|
FTP Download Service Not Accessible A/B |
|
Details of failure |
✔ |
|
|
FTP Download Setup Time A/B |
|
Time in seconds |
✔ |
|
|
FTP Download Start |
|
File path and name |
– |
✔ |
|
FTP events, upload: Test setup in UM section "FTP Upload". Not obtained for SFTP. |
||||
|
FTP Upload Data Transfer Cutoff A/B |
|
Cutoff point |
✔ |
|
|
FTP Upload Data Transfer Time A/B |
|
Time in seconds |
✔ |
|
|
FTP Upload End |
|
Outcome |
– |
✔ |
|
FTP Upload Error |
|
Cause |
– |
✔ |
|
FTP Upload IP Service Access Failure A/B |
|
Details of failure |
✔ |
|
|
FTP Upload IP Service Setup Time A/B |
|
Time in seconds |
✔ |
|
|
FTP Upload Mean Data Rate A/B |
|
Data rate in kbit/s |
✔ |
|
|
FTP Upload Service Not Accessible A/B |
|
Details of failure |
✔ |
|
|
FTP Upload Setup Time A/B |
|
Time in seconds |
✔ |
|
|
FTP Upload Start |
|
File path and name |
– |
✔ |
|
Google Drive events: Test setup in UM sections "Google Drive" |
||||
|
Google Drive Operation Start |
|
– |
Google Drive Operation started. |
✔ |
|
Google Drive Operation Attempt |
|
Timestamp |
Request sent to the Google Drive server. |
✔ |
|
Google Drive Operation Success |
|
Timestamp |
Google Drive Operation succeeded. |
✔ |
|
Google Drive Operation Error |
|
Timestamp |
Google Drive Operation failed. |
✔ |
|
Google Drive Operation End |
|
Outcome |
Google Drive Operation ended. |
✔ |
|
HTTP Service Not Accessible A/B |
|
Details of failure |
✔ |
|
|
HTTP Setup Time A/B |
|
Time in seconds |
✔ |
|
|
HTTP events, Get: Test setup in UM section "HTTP Get" |
||||
|
HTTP Connection Initiation |
|
|
– |
|
|
HTTP Data Transfer Cutoff A/B |
|
Cutoff point |
✔ |
|
|
HTTP Data Transfer Time A/B |
|
Time in seconds |
✔ |
|
|
HTTP End |
|
Outcome |
– |
✔ |
|
HTTP Error |
|
Cause |
– |
✔ |
|
HTTP IP Service Access Failure A/B |
|
Details of failure |
✔ |
|
|
HTTP IP Service Setup Time A/B |
|
Time in seconds |
✔ |
|
|
HTTP Mean Data Rate A/B |
|
Data rate in kbit/s |
✔ |
|
|
HTTP Minimum Payload Reached |
|
|
|
|
|
HTTP Start |
|
IP address or host name |
– |
✔ |
|
HTTP Time to first byte |
|
Time in seconds |
– |
|
|
HTTP events, Post: Test setup in UM section "HTTP Post" |
||||
|
HTTP Post Connection Initiation |
|
|
– |
|
|
HTTP Post Data Transfer Cutoff A/B |
|
Cutoff point |
✔ |
|
|
HTTP Post Data Transfer Time A/B |
|
Time in seconds |
✔ |
|
|
HTTP Post End |
|
Outcome |
– |
✔ |
|
HTTP Post Error |
|
Cause |
– |
✔ |
|
HTTP Post IP Service Access Failure A/B |
|
Details of failure |
✔ |
|
|
HTTP Post IP Service Setup Time A/B |
|
Time in seconds |
✔ |
|
|
HTTP Post Mean Data Rate A/B |
|
Data rate in kbit/s |
✔ |
|
|
HTTP Post Start |
|
HTTP server script URL |
– |
✔ |
|
Instagram events: Test setup in UM sections "Instagram Logon"–"Instagram Logoff" |
||||
|
Instagram Logoff Attempt |
|
Timestamp |
Close and clear token information sent from on-device Instagram service. |
✔ |
|
Instagram Logoff Duration |
|
Duration of logoff procedure in seconds |
Logoff finished when Instagram session closed. |
✔ |
|
Instagram Logoff End |
|
Timestamp; Status |
Logoff script activity ended. |
✔ |
|
Instagram Logoff Error |
|
Cause |
Logoff failed. |
✔ |
|
Instagram Logoff Start |
|
– |
Logoff script activity started. |
✔ |
|
Instagram Logon Attempt |
|
Timestamp |
Logon request sent to Instagram server. |
✔ |
|
Instagram Logon Duration |
|
Duration of logon procedure in seconds |
Logon finished when active session with valid access token is opened. |
✔ |
|
Instagram Logon End |
|
Timestamp; Status |
Logon script activity ended. |
✔ |
|
Instagram Logon Error |
|
Cause |
Failure to retrieve access token. |
✔ |
|
Instagram Logon Start |
|
– |
Logon script activity started. |
✔ |
|
Instagram Operation Attempt |
|
Timestamp; Operation type |
Request sent from on-device Instagram service. |
✔ |
|
Instagram Operation Duration |
|
Duration of operation in seconds; Operation type |
Operation successfully completed. |
✔ |
|
Instagram Operation End |
|
Operation status; Operation type |
Script activity ended. |
✔ |
|
Instagram Operation Error |
|
Cause; Operation type |
Operation failed. |
✔ |
|
Instagram Operation Start |
|
Operation type |
Script activity started. |
✔ |
|
|
Time in ms |
– (unrelated to KPIs) Generated on handover and indicates time gap between last IP packet in old cell and first IP packet in new cell.2 Note: For this time to be correct, IP sniffing must not be configured for "Optimized Performance". See UM section "Start IP Sniffing". |
✔ |
|
|
"Last" events: These events relate to TCP. |
||||
|
Last Fin |
|
Service type, Receive time |
TCP session takedown: Last FIN command sent. |
|
|
Last Rst |
|
Service type, Receive time |
TCP session takedown: Last RST command sent. |
|
|
MMS receive events: Test setup in UM section "MMS Receive" |
||||
|
MMS Receive Data Transfer Cutoff |
|
– |
✔ |
|
|
MMS Receive Data Transfer Time |
|
Time in seconds |
✔ |
|
|
MMS Receive End |
|
Outcome |
– |
✔ |
|
MMS Receive Error |
|
Cause |
– |
✔ |
|
MMS Receive Start |
|
– |
– |
✔ |
|
MMS Retrieval Failure |
|
– |
✔ |
|
|
MMS Retrieval Time |
|
Time in seconds |
✔ |
|
|
MMS send events: Test setup in UM section "MMS Send" |
||||
|
MMS Send Data Transfer Cutoff |
|
– |
✔ |
|
|
MMS Send Data Transfer Time |
|
Time in seconds |
✔ |
|
|
MMS Send End |
|
Outcome |
– |
✔ |
|
MMS Send Error |
|
Cause |
– |
✔ |
|
MMS Send Failure |
|
– |
✔ |
|
|
MMS Send Start |
|
– |
– |
✔ |
|
MMS Send Time |
|
Time in seconds |
✔ |
|
|
MTSI events: Test setup in UM sections "Dial"–"How to Set Up PC Client Based VoIP Testing" |
||||
|
|
– |
✔ |
||
|
|
Time in seconds |
✔ |
||
|
|
– |
|
||
|
|
Time in seconds |
– |
|
|
|
|
– |
|
||
|
|
Time in seconds |
|
||
|
Netflix events: Test setup in UM sections "Dropbox Logon"–"Dropbox Logoff". See also Streaming events. |
||||
|
Netflix Logoff Attempt |
|
Timestamp |
CClicked on Sign Out button and wait for logoff to be completed. |
✔ |
|
Netflix Logoff End |
|
Status |
Logon script activity ended. |
✔ |
|
Netflix Logoff Error |
|
Cause |
Logoff failed. |
✔ |
|
Netflix Logoff Start |
|
– |
Logoff script activity started. |
✔ |
|
Netflix Logoff Success |
|
Duration of logoff procedure in seconds |
Logoff successfully. |
✔ |
|
Netflix Logon Attempt |
|
Timestamp |
Clicked on Sign In button and wait for logon to be completed. |
✔ |
|
Netflix Logon End |
|
Status |
Logon script activity ended. |
✔ |
|
Netflix Logon Error |
|
Cause |
Logon failed. |
✔ |
|
Netflix Logon Start |
|
– |
Logon script activity started. |
✔ |
|
Netflix Logon Success |
|
Logon duration |
Logon successfully. |
✔ |
|
Network connect events: Test setup in UM sections "Network Connect"–"Network Disconnect" |
||||
|
|
Connection type (NDIS/RAS/Wi-Fi); IP address |
✔ |
||
|
Network Connect Attempt |
|
Connection type (NDIS/RAS/Wi-Fi) |
– (unrelated to KPIs) Triggered when a "Network Connect" activity starts executing. |
✔ |
|
Network Connect Error |
|
Cause |
✔ |
|
|
|
– |
– (unrelated to KPIs) Triggered when the operational state of the .NET network interface changes to Down for a device to which "Network Connect" was previously applied.3 Generated only for NDIS connections. |
✔ |
|
|
Network Disconnect |
|
– |
– |
✔ |
|
PDP Context Activation Time |
|
Time in ms |
|
|
|
PDP Context Cutoff |
|
– |
✔ |
|
|
Ping events: Test setup in UM section "Ping" |
||||
|
Ping End |
|
Max. delay; Min. delay; Avg. delay; Success count; Failed count |
– |
✔ |
|
Ping Error |
|
Cause |
– |
✔ |
|
Ping Roundtrip Time |
|
Time in seconds; Ping size; IP address |
✔ |
|
|
Ping Start |
|
IP address or host name |
– |
✔ |
|
|
– |
– |
✔ |
|
|
|
Time in ms |
– Time from last audio-related RTP message before handover to first audio-related RTP message after handover. DTX messages are disregarded. |
✔ |
|
|
RTP Interruption Time Video |
|
Time in ms |
– Time from last video-related RTP message before handover to first video-related RTP message after handover. |
|
|
|
Time between SIP Invite and SIP Invite Response messages |
– |
✔ |
|
|
Skype events: Test setup in UM sections "Skype Logon"–"Skype Logoff" |
||||
|
Skype Logoff Attempt |
|
Timestamp |
Close and clear token information sent from on-device Skype service. |
✔ |
|
Skype Logoff Duration |
|
Duration of logoff procedure in seconds |
Logoff finished when Skype session closed. |
|
|
Skype Logoff End |
|
Timestamp; Status |
Logoff script activity ended. |
✔ |
|
Skype Logoff Error |
|
Cause |
Logoff failed. |
✔ |
|
Skype Logoff Start |
|
– |
Logoff script activity started. |
✔ |
|
Skype Logon Attempt |
|
Timestamp |
Logon request sent to Skype server. |
✔ |
|
Skype Logon Duration |
|
Duration of logon procedure in seconds |
Logon finished when active session with valid access token is opened. |
|
|
Skype Logon End |
|
Timestamp; Status |
Logon script activity ended. |
✔ |
|
Skype Logon Error |
|
Cause |
Failure to retrieve access token. |
✔ |
|
Skype Logon Start |
|
– |
Logon script activity started. |
✔ |
|
Skype Operation Attempt |
|
Timestamp; Operation type |
Request sent from on-device Skype service. |
✔ |
|
Skype Operation Duration |
|
Duration of operation in seconds; Operation type |
Operation successfully completed. |
|
|
Skype Operation End |
|
Operation status; Operation type |
Script activity ended. |
✔ |
|
Skype Operation Error |
|
Cause; Operation type |
Operation failed. |
✔ |
|
Skype Operation Start |
|
Operation type |
Script activity started. |
✔ |
|
Social network testing events: These are all for Weibo. Test setup in UM section "Weibo". |
||||
|
Social Network Service End |
|
– |
– |
|
|
Social Network Service Error |
|
Cause |
– |
|
|
Social Network Service Start |
|
– |
– |
|
|
Social Network Logon Rate |
|
Logon Success Count / Logon Attempt Count à 100 (%) |
– These events report an aggregate over the whole execution of a "Weibo" activity rather than single instances of success/failure or elapsed time. |
|
|
Social Network Weibo Average Time |
|
Weibo Total Duration / Weibo Success Count à 100 (%) |
|
|
|
Social Network Weibo Failure Rate |
|
Weibo Failure Count / (Weibo Attempt Count – Weibo Timeout Count) Ã 100 (%) (timeouts are disregarded in this calculation) |
|
|
|
Social Network Weibo Success Rate |
|
Weibo Success Count / Weibo Attempt Count à 100 (%) |
|
|
|
SRVCC events: Note that these require vocoder logs to be turned on in the device properties. Regarding Qualcomm chipset based devices, see UM section "Properties of Qualcomm Chipset Based Devices". |
||||
|
|
Time in ms |
– Time from last RTP report on LTE to first UMTS DL Vocoder Report on UTRAN/GERAN. |
✔ |
|
|
Streaming events: The set of events generated differs between streaming clients and protocols; details in section "Support for Streaming Events by Streaming Solution". For the test setup, see UM section "Streaming". |
||||
|
Streaming Buffering Time |
|
Time in seconds |
– |
✔ |
|
Streaming End |
|
Outcome |
– |
✔ |
|
Streaming Error |
|
Cause |
– |
✔ |
|
|
MOS value |
"Streaming Quality (MOS-VSQI)" Event gives average of the latest 30 values of "Streaming VSQI". See UM chapter "Video Streaming Quality Index – VSQI". |
✔ |
|
|
Streaming Quality MOS |
|
Avg. audio MOS; Avg. absolute video MOS; Avg. relative video MOS; Avg. audio–video MOS |
– Event gives overall VQmon scores for an entire streaming session. See UM chapter "VQmon Video and Audio Quality Metrics". |
|
|
|
MOS value |
– Event gives overall MTQI score for an entire streaming session. See UM chapter "Mobile TV Quality Index – MTQI". |
✔ |
|
|
Streaming Quality PEVQ-S |
|
MOS value |
– Event gives last instantaneous PEVQ-S score. See UM chapter "PEVQ-S for Streaming Video Quality". |
✔ |
|
|
MOS value |
"Streaming Quality (MOS-VSQI)" Event gives overall VSQI score for an entire streaming session. See UM chapter "Video Streaming Quality Index – VSQI". |
✔ |
|
|
Streaming Reproduction Cutoff |
|
– |
✔ |
|
|
Streaming Reproduction Start Delay |
|
Time in seconds |
✔ |
|
|
Streaming Reproduction Start Failure |
|
– |
✔ |
|
|
Streaming Service Access Time |
|
Time in seconds |
✔ |
|
|
Streaming Service Not Accessible |
|
– |
✔ |
|
|
Streaming Session Cutoff |
|
– |
✔ |
|
|
Streaming Start |
|
HTTP: File URL RTP: File path and name |
– |
✔ |
|
|
State of streaming client: one of " |
– |
✔ |
|
|
Streaming Video Play Start Failure |
|
– |
– |
✔ |
|
Streaming Video Play Start Time |
|
Time in seconds |
– |
✔ |
|
Streaming Video Session Failure |
|
– |
– |
✔ |
|
Streaming Video Session Time |
|
Time in seconds |
– |
✔ |
|
TCP events: Test setup for TCP upload/download in UM section "Network Bandwidth (Iperf)" |
||||
|
TCP Connection Idle Time Stop |
|
– |
Triggered when a previously idle TCP connection has recovered. |
|
|
|
– |
Triggered when a TCP connection has been idle longer than the maximum set in the script (FTP and HTTP activities). |
|
|
|
TCP Download End |
|
Outcome |
– (No KPIs defined for TCP) |
|
|
TCP Download Error |
|
Cause |
|
|
|
TCP Download Start |
|
IP address |
|
|
|
TCP Handshake Time |
|
IP address; Time in seconds |
✔ |
|
|
TCP Upload End |
|
Outcome |
|
|
|
TCP Upload Error |
|
Cause |
|
|
|
TCP Upload Start |
|
IP address |
|
|
|
Trace Route events: Test setup in UM section "Trace Route" |
||||
|
Trace Route End |
|
Destination; Reached (True/False) |
– (No KPIs defined for Trace Route) |
|
|
Trace Route Hop |
|
Hop sequence no.; IP address reached; Hop time |
|
|
|
Trace Route Start |
|
Destination |
|
|
|
Trace Route Timeout |
|
Hop sequence no.; IP address targeted |
|
|
|
Twitter events: Test setup in UM sections "Twitter Logon"–"Twitter Logoff" |
||||
|
Twitter Logoff Attempt |
|
Timestamp |
Close and clear token information sent from on-device Twitter service. |
✔ |
|
Twitter Logoff Duration |
|
Duration of logoff procedure in seconds |
Logoff finished when Twitter session closed. |
✔ |
|
Twitter Logoff End |
|
Timestamp; Status |
Logoff script activity ended. |
✔ |
|
Twitter Logoff Error |
|
Cause |
Logoff failed. |
✔ |
|
Twitter Logoff Start |
|
– |
Logoff script activity started. |
✔ |
|
Twitter Logon Attempt |
|
Timestamp |
Logon request sent to Twitter server. |
✔ |
|
Twitter Logon Duration |
|
Duration of logon procedure in seconds |
Logon finished when active session with valid access token is opened. |
✔ |
|
Twitter Logon End |
|
Timestamp; Status |
Logon script activity ended. |
✔ |
|
Twitter Logon Error |
|
Cause |
Failure to retrieve access token. |
✔ |
|
Twitter Logon Start |
|
– |
Logon script activity started. |
✔ |
|
Twitter Operation Attempt |
|
Timestamp; Operation type |
Request sent from on-device Twitter service. |
✔ |
|
Twitter Operation Duration |
|
Duration of operation in seconds; Operation type |
Operation successfully completed. |
✔ |
|
Twitter Operation End |
|
Operation status; Operation type |
Script activity ended. |
✔ |
|
Twitter Operation Error |
|
Cause; Operation type |
Operation failed. |
✔ |
|
Twitter Operation Start |
|
Operation type |
Script activity started. |
✔ |
|
UDP events: Test setup in UM sections "UDP", "Network Bandwidth (Iperf)" |
||||
|
UDP Download End |
|
Outcome |
– (No KPIs defined for UDP) |
|
|
UDP Download Error |
|
Cause |
|
|
|
UDP Download Start |
|
IP address |
|
|
|
UDP Download Total Packet Loss |
|
Packet loss in % |
|
|
|
UDP Upload End |
|
Outcome |
|
|
|
UDP Upload Error |
|
Cause |
|
|
|
UDP Upload Start |
|
IP address |
|
|
|
UDP Upload Total Packet Loss |
|
Packet loss in % |
|
|
|
VoIP events: Test setup in UM sections "Dial"–"How to Set Up PC Client Based VoIP Testing" |
||||
|
VoIP End |
|
Outcome |
– (KPIs based on "MTSI" events, which see) |
✔ |
|
VoIP Error |
|
Cause |
✔ |
|
|
|
Time in ms |
– (unrelated to KPIs) Generated on handover during a VoIP talkspurt and indicates time gap between last RTP packet in old cell and first RTP packet in new cell. Note: For this time to be correct, IP sniffing must not be configured for "Optimized Performance". See UM section "Start IP Sniffing". |
|
|
|
|
No. of missing RTP packets from handover start (RRC Reconfiguration Command) to successful playback of first RTP packet after handover (RRC Reconfiguration Complete) |
– |
|
|
|
VoIP Start |
|
Cause (e.g. " |
– (KPIs based on "MTSI" events, which see) |
✔ |
|
WAP events: Test setup in UM section "WAP Get" |
||||
|
WAP Activation Failure |
|
– |
|
|
|
WAP Activation Request |
|
– |
– |
|
|
WAP Activation Time |
|
Time in ms |
|
|
|
WAP End |
|
Outcome |
– |
|
|
WAP Error |
|
Cause |
– |
|
|
WAP Page Data Transfer Cutoff |
|
– |
|
|
|
WAP Page Data Transfer Time |
|
Time in seconds |
|
|
|
WAP Page First Data |
|
– |
– |
|
|
WAP Page Last Data |
|
– |
– |
|
|
WAP Page Mean Data Rate |
|
Data rate in kbit/s |
|
|
|
WAP Page Request Failure |
|
– |
|
|
|
WAP Page Request Time |
|
Time in seconds |
|
|
|
WAP Portal Access Time |
|
Time in seconds |
|
|
|
WAP Portal Not Accessible |
|
– |
|
|
|
WAP Site Access Time |
|
Time in seconds |
|
|
|
WAP Site Not Accessible |
|
– |
|
|
|
WAP Start |
|
URL; Connection method |
– |
|
|
WhatsApp events: Test setup in UM section "WhatsApp" |
||||
|
WhatsApp Operation Attempt |
|
Timestamp; Operation type |
Request sent from on-device WhatsApp service. |
✔ |
|
WhatsApp Operation End |
|
Operation status; Operation type |
Script activity ended. |
✔ |
|
WhatsApp Operation Error |
|
Cause; Operation type |
Operation failed. |
✔ |
|
WhatsApp Operation Start |
|
Operation type |
Script activity started. |
✔ |
|
WhatsApp Operation Success |
|
Operation type |
Operation successfully completed. |
✔ |
