52.21.9 Log Configuration

Specifies a logmask configuration that a device should use, that is, which logs should be turned on and off. This activity is applicable to Qualcomm chipset and Samsung chipset devices, and it is described separately for each of these device categories.
This activity must precede the "Start Recording" activity to which it is to apply.

52.21.9.1. Qualcomm Chipset Devices

Configuration property:

Log Configuration Type:

Default: The log configuration currently specified in the device properties (see section "Properties of Qualcomm Chipset Based Devices") will be used.

Custom file: The device will use a log configuration described in either of the following types of file:

XML file with extension .lcp. This is normally a configuration exported from the device properties, as described in section "Working with Log Configurations".

QXDM Professional configuration file with extension .dmc.

An additional field File Path appears for pointing to the configuration file, as well as a read-only Chipset field showing what chipset type a specified configuration file is written for.

The remaining options are predefined log configurations which are optimized for KPI calculation for various forms of LTE service testing. Non-LTE logs are not affected. Full lists of selected logs are found in section "Predefined Log Configurations".

Optimized for Voice KPI reports: Configuration optimized for VoLTE.

Optimized for Data KPI reports: Configuration optimized for data service testing. The DPL log (0x11EB) is turned off so that the data service payload is not saved in the logfile.

Optimized for Voice/Data KPI reports: Configuration optimized for multi-RAB testing with VoLTE and a data service running in parallel. In this case, DPL logs (0x11EB) are transformed into SIP/RTP reports which are saved in the logfile. The original logs are then discarded in order to reduce the logfile size.

52.21.9.2. Samsung Chipset Devices

Configuration property:

Log Configuration Type:

Default: The log configuration currently specified in the device properties (see section "Properties of Samsung Chipset Based Devices") will be used.

Custom file: Not applicable to Samsung chipset devices.

The remaining options are intended for various forms of LTE service testing. There is no extensive selection of logs as in the Qualcomm case; the only modifications to the default logging are as described below.

In all "Optimized" configurations, the reporting interval is changed from the default 200 ms to 1000 ms.

Optimized for Voice KPI reports: No further changes from "Default".

Optimized for Data KPI reports: Configuration optimized for data service testing. The IP Dump report is turned off so that the data service payload is not saved in the logfile.

Optimized for Voice/Data KPI reports: Configuration optimized for multi-RAB testing with VoLTE and a data service running in parallel. In this case, IP Dump reports are transformed into SIP/RTP reports which are saved in the logfile. The original logs are then discarded in order to reduce the logfile size.