LTE433 which collect useful data for determining the problem with

more accuracy.

It works with Cell trace together and reports L3 and coverage related
information.

Working points
- Can our device report MDT ? , can our commercial user can
support it ?
o 3GPP R10 UE capabilities
- How we can see swap geographically ?

LTE433 Cell Trace

LTE2202 Addition of MAC measurements to cell trace
LTE953 collect and send to L3 analyser L3 messages

https://www.finetopix.com/showthread.php/51409-Nokia-features-
LTE953-vs-LTE1049

LNBTS
actMDTloggedCellTrace = True

MDT collects data directly from regular UEs and it is less expensive than DT
In TraceViewer, it is possible to configure Trace Session with MDT settings.
The LTE953: MDT (Minimization of Drive Test) feature must be enabled to activate the LTE1308:
MDT Cell Trace Enhancements feature. The actMDTCellTrace LNBTS parameter is used to
enable thefeature.
•preconfiguration

The actCellTraceLNBTS parameter value is set to true.

LTE1308: MDT Cell Trace Enhancements feature is enabled (actMDTCellTrace parameter is set totrue).

 Immediate MDT - functionality that involves measurements performed by the UE in

the CONNECTED state, and reporting of the measurements to eNodeB or RNC available at
the time of reporting conditions as well as measurement by the network for MDT purposes.
 Logged MDT - functionality that involves measurement logging by UE in the Idle
mode, CELL_PCH and URA_PCH states (when UE is in UTRA) for reporting to eNodeB or
RNC at a later point of time.

LTE 1049 feature:

Nokia tracing features support two ways of trace management:

• Signaling Based Activation
• Management Based Activation

There are two modes concerning Minimization of Drive Test

Immediate MDT - functionality that involves measurements performed by the UE in the CONNECTED
state, and reporting of the measurements to eNodeB or RNC available at the time of reporting
conditions as well as measurement by the network for MDT purposes.

Logged MDT - functionality that involves measurement logging by UE in the Idle mode, CELL_PCH and
URA_PCH states (when UE is in UTRA) for reporting to eNodeB or RNC at a later point of time.

The Subscriber/Cell trace functionality is reused and extended to support MDT

The solutions requiring location information should take into account the power consumption of the
UE because of the need to run its positioning components.

Cell trace with IMSI:

The mechanism works as follows: 1. The eNodeB sends the Trace Recording Session Reference, the
Trace Reference, and the Trace Collection Entity (TCE) address to the MME via the S1AP connection.
2. When the MME receives this new S1AP signaling message: a. it checks the IMSI and IMEI of a
certain call from its database. b. it sends the IMSI and IMEI numbers together with the Trace
Recording Session Reference and Trace Reference to the TCE.
The TCE handles this information and assigns the IMSI/ IMEI number to each trace record
accordingly.

LTE 644 : Configurable cell trace content:

MDT-UE Measurement logs

This chapter describes Logged MDT Trace functionality.

Logged MDT Trace is a feature introduced for MDT-UE Measurement logs (LTE 1049) feature. It
allows eNodeB to support the configuration and retrieval of user equipment (UE) measurement logs as
well as to report those with a Cell Trace.
Note:
TraceViewer does not support automatic IP address and port number change for ongoing
Logged MDT traces. Such traces must be created again with the new IP address and port number
configuration.
Logged MDT functionality

Because of the continuous changes in the network and optimization needs, Minimization of Drive
Tests (MDT) has been proposed to gather information directly from regular user equipments (UEs).
When UEs on different eNodeBs are configured as MDT measurements, Logged MDT Trace function
can collect drive tests from the network and minimize Drive Test (DT) effort. For more information
about MDT functionality in TraceViewer, see Minimization of Drive Tests.

For Logged MDT Trace feature, available mode for MDT measurements is Logged MDT. In this mode,
capable UEs collect MDT measurements in the RRC Idle state and store them in the internal memory
for a further use.

Note:
UEs can store MDT measurements for no longer than 48 hours.
Note:
Only capable UEs should be configured for the Logged MDT mode.
Logged MDT can be initiated via Management Based Activation (MBA) without targeting any specific
UE, by the cell traffic trace. MBA is an area-based trace session and it enables sending Trace Session
Activation message towards eNodeB. Optionally, location information (GNSS) is also possible for
Logged MDT Trace feature.

Note:
It is mandatory to obtain subscriber consent before activation of MDT functionality because of the
privacy and legal obligations.
Activation of MDT-UE Measurement Logs feature

As mentioned previously, the initiation of Logged MDT for MBA requires particular EUs to
support MDT measurements in the RRC Idle state. To activate Logged MDT Trace feature on desired
UEs, user must perform the following actions:

1. Configure specific parameters on LNBTS and specific parameters on CTRLTS in CM

Editor.

2. Activate LTRACE in TraceViewer.

To configure proper managed object, specific settings related to LNBTS and CTRLTS must be
provided in CM Editor, not in TraceViewer. For more information about LNBTS and CTRLTS
configuration procedure, see Configuring and activating LTRACE.

After proper LNBTS and CTRLTS configuration, before Logged MDT initiation, it is also mandatory to
activate LTRACE which sends and receives configuration under the same cell. This procedure is
available directly from TraceViewer application.
Note:
In one cell only one LTRACE can exist.
Activating LTRACE requires providing specific settings in TraceViewer, in the New Cell Trace window
for LTE BTS Logged MDT. For more information about activating LTRACE, see Configuring and
activating LTRACE.
After activation of Logged MDT Trace feature, capable UEs send capability responses about ability to
perform MDT measurements in the RRC Idle state.

For more general information about activating a trace on eNodeB, provisioning changes to the network
and managing LTRACE object, see also Precondition for LTE cell trace activation.

Logged MDT Management Based Initiation

During the Logged MDT initiation for MBA, operator provides the MDT Trace Session Activation
message towards eNodeB in NetAct, third party tool or BTSSM. This message is received by eNodeB
which checks if particular UE can or cannot perform MDT measurements and sends configuration
message to capable UEs by RRC signaling procedure. After that, Logged MDT MBA trace session
starts and when desired UEs are in the RRC Connected state, they can obtain collected configuration
messages.
Note:
In the RRC Idle state, a capable UE is able to collect MDT measurements but to obtain collected
configuration settings from eNodeB (and also to send MDT logs), UE should be in the RRC
Connected state.
When capable UE turns to the RRC Idle state, it collects and stores MDT measurements. After that, it
reports that logs can be sent. When it turns to the RRC Connected state again, particular eNodeBs
requests Logged MDT from capable UEs and logged data is retrieved.
Note:
As logged data from capable UEs must be retrieved, it is necessary to select the Configure and
retrieve option in the New Cell Trace window to enable eNodeB sending configuration messages
as well as retrieving MDT reports from capable UEs. For more information about it, see Creating a
Logged MDT Cell Trace on LNBTS network element.
Collected Logged MDT data is sent to TraceViewer towards eNodeBs and can be analyzed in
the Trace Analysis window.
Note:
ENodeB transfer message request occurs in logs.
Parent topic: Supported SRAN features
TraceViewer Overview • DN09106629 • trccudodocs-22.0.16.23
© 2021 Nokia. All rights reserved.