MDT Feature Parameter Description: Issue Date

eRAN
MDT Feature Parameter Description
Issue 03
Date 2020-10-31
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. i

eRAN
MDT Feature Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN16.1 03 (2020-10-31)..................................................................................................................................................1
1.2 eRAN16.1 02 (2020-08-31)..................................................................................................................................................1
1.3 eRAN16.1 01 (2020-03-30)..................................................................................................................................................2
1.4 eRAN16.1 Draft A (2020-01-20)........................................................................................................................................ 2
2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Applicable RAT......................................................................................................................................................................... 4
3 Overview....................................................................................................................................5
4 MDT.............................................................................................................................................6
4.1 Principles.................................................................................................................................................................................... 6
4.1.1 MDT Architecture................................................................................................................................................................. 6
4.1.2 MDT Events............................................................................................................................................................................ 7
4.1.3 Activating UE GPS............................................................................................................................................................. 13
4.1.4 Management-based MDT............................................................................................................................................... 14
4.1.5 Signaling-based MDT....................................................................................................................................................... 16
4.2 Network Analysis.................................................................................................................................................................. 17
4.2.1 Benefits................................................................................................................................................................................. 17
4.2.2 Impacts.................................................................................................................................................................................. 19
4.3 Requirements......................................................................................................................................................................... 19
4.3.1 Licenses................................................................................................................................................................................. 19
4.3.2 Software................................................................................................................................................................................19
4.3.3 Hardware.............................................................................................................................................................................. 19
4.3.4 Others.................................................................................................................................................................................... 20
4.4 Operation and Maintenance............................................................................................................................................. 20
4.4.1 Data Configuration........................................................................................................................................................... 20
4.4.1.1 Data Preparation............................................................................................................................................................ 20
4.4.1.2 Using MML Commands............................................................................................................................................... 21
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 21
4.4.2 Activation Verification..................................................................................................................................................... 21
4.4.3 Network Monitoring......................................................................................................................................................... 22
4.4.4 Possible Issues.................................................................................................................................................................... 22
Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
MDT Feature Parameter Description Contents
5 Glossary................................................................................................................................... 23
6 Reference Documents...........................................................................................................24
Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
MDT Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN16.1 03 (2020-10-31)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
● Revised MDT event names. For details, see 4.1.2 MDT Events.
● Revised the descriptions of network impacts of MDT. For details, see 4.2.2
Impacts.
1.2 eRAN16.1 02 (2020-08-31)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in the document.
Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
MDT Feature Parameter Description 1 Change History
1.3 eRAN16.1 01 (2020-03-30)

This issue does not include any changes.
1.4 eRAN16.1 Draft A (2020-01-20)

This issue introduces the following changes to eRAN15.1 01 (2019-06-06).
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added the function of None FDD ● 3900 and 5900

customizing the number TDD series base
of cell-level traced UEs for stations
MDT. For details, see 4.1.4 ● DBS3900
Management-based LampSite and
MDT. DBS5900
LampSite
● BTS3911E
Changed the name of None FDD ● 3900 and 5900

U2020 to MAE-Access and TDD series base
the name of CME to MAE- stations
Deployment. ● DBS3900
LampSite and
DBS5900
LampSite
● BTS3911E
Canceled the compatibility None FDD BTS3912E

with the BTS3912E as of
this version.
Editorial Changes
None

eRAN
MDT Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a
description does not apply to all RATs, the specific RAT that it does apply to will
be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-
MIMO", "TDD cells" indicates that this function cannot be used in non-TDD cells.

eRAN
MDT Feature Parameter Description 2 About This Document
2.2 Applicable RAT

This document applies to FDD/TDD.

eRAN
MDT Feature Parameter Description 3 Overview
3 Overview
After a network is deployed, multiple drive tests (DTs) must be performed to

provide a reference for network optimization and to achieve the best possible
network coverage and performance. Minimization of Drive Tests (MDT)
automatically collects, reports, and preprocesses measurement data, requiring less
labor, equipment, and time than traditional manual DTs.
MDT can be classified into two types based on the measurement reporting mode:
● Immediate MDT
Collects measurement data of UE in connected mode.
● Logged MDT
Collects measurement data of UE in idle mode.
MDT can be classified into two types based on the data collection object:
● Management-based MDT
Collects MDT data of UEs in an area specified by the TA or ECGI list.
Management-based MDT can be logged or immediate MDT.
● Signaling-based MDT
Collects MDT data of UEs specified by the international mobile subscriber
identity (IMSI) or international mobile equipment identity (IMEI). Signaling-
based MDT can be logged or immediate MDT.
NOTE
● Currently, Huawei core network does not support the delivery of signaling-based MDT
tasks to UEs specified by the IMEI.
● The eNodeB collects MDT location information only from MDT UEs subscribed on the
core network.

eRAN
MDT Feature Parameter Description 4 MDT
4 MDT
4.1 Principles
During MDT, commercial or test UEs report their geographic locations and signal
strength of the serving cell and neighboring cells to the network. MDT results
directly reflect network coverage. This section describes how to collect MDT data
of UEs in a specific area or MDT data of specific UEs.
4.1.1 MDT Architecture

Figure 4-1 illustrates the network architecture for MDT data collection.
Figure 4-1 MDT data collection architecture
Table 4-1 describes the functional units involved.
Table 4-1 Functional units
Functional Entity Description
UE Measures and reports MDT data to the eNodeB.
eNodeB Collects MDT data and reports it to the trace server

(TS) based on MDT subscription tasks.
Core network Consists of the HSS and MME.
HSS Stores and transfers MDT subscription data.

eRAN
Functional Entity Description
MME Delivers MDT UE subscription information during

management-based MDT data collection; delivers
MDT UE and MDT configuration information during
signaling-based MDT data collection.
TS Combines and delivers upper-layer subscription tasks,

and receives and stores MDT data reported by the
eNodeB. Transmits data to the network optimization
plane over the northbound interface.
MAE Subscribes to and controls MDT data.
Network optimization Analyzes and displays MDT data. Either Huawei

plane Discovery or a third-party network optimization tool
can be used as the network optimization plane.
4.1.2 MDT Events

The MAE collects MDT data by subscribing to MDT events. Different MDT events
correspond to different data types. Table 4-2 lists supported MDT events. In the
following table, only the LOGGEG MDT event is in logged MDT mode in 3GPP
specifications, and other MDT events are in immediate MDT mode.
Table 4-2 MDT events

Huawei MDT Event Northb Meas Meaning
Name ound urem
MDT ent
Event Item
Name in
Proto
col
PERIOD_INTRAFREQ_ M1 M1 Intra-frequency MDT measurement

MR_MDT Intra- event
Freq
MDT
PERIOD_INTERFREQ_ M1 M1 Inter-frequency MDT measurement

MR_MDT Inter- event
Freq
MDT
PERIOD_INTER_RAT_ M1 M1 MDT GU inter-RAT measurement

MR_MDT inter- event
RAT
MDT

eRAN

Name ound urem
MDT ent
Event Item
Name in
Proto
col
PRIVATE_GU_MEASU M1 GU M1 MDT GU MR event

REMENT_REPORT_M event
DT MR
PERIOD_PRIVATE_UE M2 M2 UE MDT event: UE power headroom

_MEASUREMENT_M MDT measurement by the eNodeB
DT
PERIOD_LOGGED_M LOGGE M1 Logged MDT event: After

DT_MEASUREMENT D MDT measurement of a UE in the idle
state, the measurement result is
logged and the log file is temporarily
saved in the UE memory. The UE
reports the measurement result the
next time it enters the active state.
RLF_REPORT RLF M1 Radio link failure MDT event:

Report measurement data of the serving cell,
MDT neighboring cells, and the UE's
location in the case of a radio link
failure (RLF)
PERIOD_PRIVATE_TH M4/M5 M4/ Traffic volume/Throughput: UE traffic

ROUGHPUT_MEASU MDT M5 volume and throughput measurement
REMENT_MDT by the eNodeB
PRIVATE_CONNEST_ RCEF M1 Connection setup failure MDT event:

FAIL_REPORT Report measurement of the serving cell,
MDT neighboring cells, and the UE's
location in the case of a connection
setup failure
PERIOD_A2_EVENT_ M1 A2 M1 A2 MDT event: periodic reporting of

MDT MDT A2 MRs after the A2 measurement
threshold is reached
PERIOD_PRIVATE_UL M3 M3 MDT uplink PRB noise interference

_NI_PRB_MR MDT measurement
PERIOD_PRIVATE_UL
_NI_PRB_MDT
PERIOD_PRIVATE_TH M6 DL M6 Downlink data delay measurement

ROUGHPUT_MEASU MDT
REMENT_MDT
PERIOD_UE_ULPDCP M6 UL M6 Uplink data delay measurement

Delay_MDT MDT

eRAN

Name ound urem
MDT ent
Event Item
Name in
Proto
col
PERIOD_PRIVATE_PK M7 M7 Measurement of uplink and downlink

TLOSSRATE_MR MDT UE packet loss rate
PERIOD_PRIVATE_UE M2-Ext None Measurement and reporting of the

_MEASUREMENT_M MDT uplink and downlink BLER, the
DT number of used uplink and downlink
PRBs, CQI, and RANK
PERIOD_PRIVATE_TH M5-Ext None Uplink and downlink MCS

ROUGHPUT_MEASU MDT measurement
REMENT_MDT
PERIOD_UE_MultiRR UE None Measurement of the uplink RSRP of

U_UL_RSRP_MR periodic each RRU serving an SFN cell
SFN UL
RSRP
MDT
MDT Event Parameter Configuration

(1) M1 intra-frequency MDT
Management-based MDT:
● Period: 5120 ms, 10,240 ms (recommended), or 1 min
● Number of times: eight, sixteen (recommended), thirty-two, sixty-four, or
infinite
Signaling-based MDT:
● Period: 1024 ms, 2048 ms, 5120 ms, 10,240 ms, 1 min, 6 min, 12 min, 30 min,
or 60 min
● Number of times: one, two, four, eight, sixteen, thirty-two, sixty-four, or
infinite
(2) M1 inter-frequency MDT
infinite
or 60 min

eRAN

infinite
(3) M5-Ext MDT
infinite
● Not supported
(4) M2 MDT
infinite
● Period: 1024 ms
● Number of times: infinite
(5) Logged MDT
● Period: 5120 ms, 10,240 ms (recommended), 20,480 ms, 30,720 ms, 40,960
ms, or 61,440 ms
● Connection duration: 10 min (recommended), 20 min, 40 min, 60 min, 90
min, or 120 min
● Period: 5120 ms, 10,240 ms, 20,480 ms, 30,720 ms, 40,960 ms, or 61,440 ms
● Connection duration: 10 min, 20 min, 40 min, 60 min, 90 min, or 120 min
(6) RLF Report MDT
● No parameters involved
● Not supported
(7) M4/M5 MDT
infinite

eRAN
● Period: 1024 ms, 2048 ms, 5120 ms, 10,240 ms, or 1 min
(8) RCEF Report MDT
● No parameters involved
● Not supported
(9) M1 A2 MDT
infinite
or 60 min
infinite
(10) M3 MDT (uplink PRB noise)
infinite
● Period: 1000 ms or 10,000 ms
(11) UE periodic SFN UL RSRP MDT
infinite
● Not supported
(12) M6 DL MDT
infinite

eRAN
● Not supported
(13) M6 UL MDT

infinite
● Uplink delay threshold: 30 ms (recommended), 40 ms, 50 ms, 60 ms, 70 ms,
80 ms, 90 ms, 100 ms, 150 ms, 300 ms, 500 ms, or 750 ms
● Not supported
(14) M7 MDT

infinite
● Not supported
(15) M2-Ext MDT

infinite
● Not supported
(16) MDT GU inter-RAT measurement event
● Period: 10s
● Number of times: sixteen
● Not supported

eRAN
NOTE
● For detailed MDT event descriptions, see sections 5.5 and 5.6.6 in 3GPP TS 36.331
V11.7.0 and section 5.2 in 3GPP TS37.320 V11.3.0.
● If a cell has subscribed to the MDT RLF event and a UE that experienced an RLF in the
cell reestablishes a connection to another cell, the target cell must be configured as an
external cell of the previous cell so that the MDT RLF event can be reported.
● If the MDT M3 event PERIOD_PRIVATE_UL_NI_PRB_MR_MDT is subscribed and some
PRBs within the cell bandwidth are unavailable due to functions or features such as
inband NB-IoT or compact bandwidth, an invalid value will be reported as the
measurement result of the uplink interference occurring in these PRBs.
● After receiving instructions of canceling subscription to the MDT intra-frequency
measurement event, MDT inter-frequency measurement event, and MDT A2 event, the
eNodeB does not send measurement control messages to remove related measurement
configurations on UEs until the UEs report the corresponding MDT measurement
reports.
● When the same UE is selected for both management- and signaling-based MDT, MDT
data is separately reported if the same events are subscribed to and the same
parameter configurations are used; if the same events are subscribed to but the
reporting periods are different, events M2, M3, M4, and M5 are reported by the period
of management-based subscription, and event M1 is reported separately by periods of
both management- and signaling-based MDT.
● For signaling-based MDT, Huawei core network does not support the delivery of events
M3, M4, and M5 subscription tasks.
● MDT GU inter-RAT measurement events and MDT GU MR events are subscribed to only
on the NIC.
4.1.3 Activating UE GPS

Before collecting MDT intra-frequency measurement events, MDT inter-frequency
measurement events, MDT A2 events, and M6 UL MDT events, you can choose
whether to enable the GPS function of UEs by setting the Active UE GPS
parameter. If this parameter is set to true and UEs are MDT-authorized, the
eNodeB delivers the reconfiguration message IE obtainLocationConfig to instruct
UEs to proactively enable the GPS function.
The UE response to the GPS activation command depends on the UE

manufacturer. For security reasons, an eNodeB cannot proactively activate GPS for
unauthorized MDT UEs. If a UE does not support reporting of longitude and
latitude, set the MmeFeatureCfg.MdtEnable parameter to ENABLE, which will
allow the MME to support a Huawei proprietary positioning function. With the
Huawei-proprietary function, the eNodeB can obtain UE locations from the MME.
To support the Huawei proprietary positioning function, Huawei MME and
positioning server are required and the UE capability message sent to the eNodeB
must have the A-GNSS-ProvideCapabilities IE. The Huawei-proprietary positioning
procedure is as follows:
1. The eNodeB sends a Huawei-proprietary positioning request to the MME.

2. The MME forwards the request to the positioning server.
3. The positioning server and MME exchange positioning-assisted information of
UEs through NAS messages.
4. The MME sends Huawei-proprietary messages carrying UE locations to the
eNodeB.

eRAN
4.1.4 Management-based MDT

Figure 4-2 shows principles of management-based MDT.
Figure 4-2 Data collection process of management-based MDT
1. An operator creates MDT subscription tasks on the MAE.

During the subscription, the operator can select the events listed in Table 4-2.
2. The MAE delivers MDT subscription data to the TS.
3. The TS forwards the subscription data to the eNodeB. After the subscription is
complete, a subscription success message is returned to the MAE.
4. The eNodeB selects UEs to collect MDT events based on MDT subscription
tasks, as shown in Table 4-3. The UE authorization information is transmitted
by the core network to the eNodeB.
5. UEs report MDT data to the eNodeB.
6. The eNodeB saves the MDT data and sends it to the TS.
7. The network optimization platform (Huawei Discovery or a third-party
network optimization analysis tool) obtains MDT data from the TS for
geographic display, helping operators optimize networks.

eRAN
Table 4-3 Selecting UEs
Subscribed MDT Event How to Select UEs
Intra-frequency, inter-frequency, A2, The eNodeB selects UEs based on

and M6 UL MDT events associated parameter settings. For
details, see Selecting UEs for
Collection of Intra-Frequency, Inter-
Frequency, A2, and M6 UL MDT
Events.
Logged MDT events The eNodeB selects UEs of which the

capability messages contain the
loggedMeasurementsIdle-r10 IE.
Other MDT events The eNodeB does not select UEs. UEs
proactively report these events to the
eNodeB.
NOTE
Huawei Discovery has a separate MDT event subscription interface, which delivers
subscription tasks and receives MDT reports through the TS. For detailed operations, see
Discovery documents.
Selecting UEs for Collection of Intra-Frequency, Inter-Frequency, A2, and M6

UL MDT Events
To collect intra-frequency, inter-frequency, A2, and M6 UL MDT events, the
eNodeB selects UEs as follows:
1. The eNodeB checks whether UEs are MDT-authorized. If they are, the eNodeB
considers them as candidate MDT UEs.
– UEs are identified as MDT-authorized when the MME sends the Initial UE
Context Setup Request message carrying the Management Based MDT
Allowed field to the eNodeB.
– Each time the eNodeB checks whether UEs are MDT-authorized, it also
checks the neighboring EARFCN capabilities of UEs newly accessing the
network.
2. In every connection duration determined based on the reporting interval and
number of times measurement is performed, the eNodeB selects UEs based
on the value of Cell-level traced UEs and using the following MDT UE
selection policies:
– In this mode, UEs that support certain measurement capabilities, as listed
below, are preferentially selected. Such UEs are hereinafter referred to as
MDT UEs. For details about UE measurement capabilities, see section
6.3.6 in 3GPP TS 36.331 V11.7.0.
▪ loggedMeasurementsIdle-r10 indicates that the UE supports MDT-

related measurement in idle mode.

eRAN
▪ standaloneGNSS-Location-r10 indicates that the UE supports

reporting of longitude and latitude information in MDT data.
▪ ul-PDCP-Delay-r13 indicates that the UE supports measurement of

the uplink PDCP delay.
▪ Inter-frequency measurement and periodic intra-frequency

measurement capabilities
– When receiving a measurement task, the UE does not report MDT data if
it does not support the related measurement capability. The UE must
support the capability indicated by ul-PDCP-Delay-r13 for reporting of the
M6 UL MDT event.
– If the MrMdtMeasOptSwitch option of the
GlobalProcSwitch.ProtocolMsgOptSwitch parameter is selected and
both common measurement reports and MDT events are subscribed for
MDT UEs, the eNodeB will deliver both common and MDT measurement
configurations to such UEs, which then send both common and MDT
measurement reports based on the measurement configurations.
NOTE
● If MDT events that require UE measurement are enabled, for example, intra-frequency,
inter-frequency, and A2 MDT events, RRC connection reestablishment may increase if
UEs supporting MDT but not able to report MDT data are selected, causing a slight
increase in the call drop rate. If there are such UEs that may cause KPI deterioration on
the live network, enable OSS subscription to trigger the periodic strongest-cell inter-
frequency measurement blacklist function according to instructions in Terminal
Awareness Differentiation.
● If the number of periodic measurements for MDT events is infinite: (1) when the
number of UEs in the cell is smaller than the value of Cell-level traced UEs, the
eNodeB will select UEs that newly access the cell for measurement; (2) when the
number of UEs in the cell is greater than or equal to the value of Cell-level traced UEs,
the eNodeB select UEs for measurement only once and does not perform polling
selection.
● The number of cell-level traced UEs for MDT is specified by the UEs parameter in the
MDT Parameters Settings area. The default value of this parameter is equal to the
number of cell-level traced UEs. If the number of cell-level traced UEs for MDT is
customized, the value of this parameter must be less than or equal to that of Cell-level
traced UEs.
A smaller value of the number of cell-level traced UEs for MDT results in less reported
MDT data.
4.1.5 Signaling-based MDT

Figure 4-3 shows principles of signaling-based MDT.

eRAN
Figure 4-3 Data collection process of signaling-based MDT
1. The EMS on the core network side starts the signaling-based MDT task for a
specific UE (specified by the IMSI) and sends the UE IMSI and configuration
information of the signaling-based MDT task to the HSS. During the
subscription, the operator can select the events listed in Table 4-2.
2. If the UE has not attached to the network during task delivery, the HSS sends
task configurations to the MME during the attach procedure. If the UE has
attached to the network, the HSS instructs the MME to start task
configuration for the UE.
3. The MME informs the eNodeB to start the signaling-based MDT task using an
S1 Initial Context Setup Request/Trace Start message.
4. The eNodeB starts the signaling-based MDT task and delivers measurement
configurations to UEs over the air interface.
5. The UE reports MDT data to the eNodeB.
6. The eNodeB stores and sends signaling-based MDT data to the signaling
tracing module of the MAE and the TS.
7. The network optimization platform can obtain MDT data from the TS for
geographic display and optimize the network based on the data.
4.2 Network Analysis
4.2.1 Benefits
Gains
MDT offers the following benefits:
● MDT automatically collects, reports, and pre-processes measurements, which
requires lower labor, equipment, and time costs than manual DTs

eRAN
● MDT collects more extensive and accurate data than traditional DTs.
Expected Gains
● For commercial networks, it is recommended that this feature be enabled on
a per cluster basis, instead of on the entire network. This is because a large
number of MDT MRs will be reported. You are advised to trigger the following
MDT events on the networks at the same time: intra-frequency measurement,
RLF, connection setup failure, and throughput/throughput rate.
The number of MDT MRs to be reported can be calculated using the following
formula: Number of MDT MRs to be reported = Number of selected UEs x
Number of times UEs report MDT MRs.
If the number of times UEs report MDT MRs is set to "infinite", the number
must be converted as follows:
Number of times UEs report MDT MRs = Average UE online duration/Period
for reporting MRs.
Average UE online duration (unit: s) = L.E-
RAB.SessionTime.UE.HighPrecision/L.Traffic.User.Avg/1000
● The numbers of times MDT and MR events are reported must be the same. If
both MDT and MR are enabled, the number of times MDT events are reported
must be set to the number of times MR events are reported.
● Do not enable inter-frequency and A2 MDT events because these events
affect network performance. The only exception is when inter-frequency MDT
analysis is required to address network issues. Disable the events immediately
after data collection is complete.
● A slight decrease in the RRC connection setup success rate due to UEs
incompatible with subscription to the Logged MDT event can be avoided
using the following methods:
– Perform compatibility tests on mainstream UEs if only a few UEs on the
live network support MDT, and add compatible UEs to an MDT whitelist.
MDT measurement is performed only for UEs in this list, avoiding impacts
of compatibility issues on network performance.
– Add incompatible UEs to the Logged MDT blacklist. Logged MDT
measurement configurations will not be delivered to such UEs.
For how to add such UEs to the whitelist or blacklist, see Terminal Awareness
Differentiation.
● It is recommended that MDT be enabled when there are more than 10 UEs
supporting MDT per cell.
● When both intra-frequency M1 and inter-frequency M1 events are subscribed
to for the same UE in management- and signaling-based MDT and the
subscription periods are different, the measurement ID of the UE may reach
the maximum value easily if many frequencies are configured on the live
network. As a result, measurement configurations for some frequencies
cannot be delivered to this UE.
● Enable MDT on networks where a large number of the eNodeBs are outdoor
macro eNodeBs. Most UEs receive little MDT data from indoor distributed
eNodeBs so this feature has little network optimization effect in such
scenarios.

eRAN
4.2.2 Impacts
Network Impacts
● Reporting of MDT measurements consumes air interface resources, increasing
the average CPU load. In addition, the values of counters related to uplink
interference, service drop rate and RRC connection reestablishment slightly
increase, and the access success rate slightly declines.
● Intra-frequency, inter-frequency, or inter-RAT MDT measurement may conflict
with handover measurement, slightly reducing the handover success rate.
● Inter-frequency or inter-RAT measurement causes UEs to enter the GAP state,
and therefore some subframes will be unable to transmit data, slightly
reducing the cell throughput and traffic volume.
● If some UEs have compatibility issues:
– After the inter-frequency or inter-RAT immediate MDT event is subscribed
to, the access success rate and handover success rate may decline, and
the values of counters related to the service drop rate and RRC
connection reestablishment may increase.
– After the logged MDT event is subscribed to, the access success rate may
decline, and the values of counters related to the service drop rate and
RRC connection reestablishment may increase.
● Periodic UE measurements increase battery power consumption.
Function Impacts
None
4.3 Requirements
4.3.1 Licenses
This function is a basic function and is not under license control.
4.3.2 Software
Prerequisite Functions
None
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models
No requirements

eRAN
Boards
The LMPT does not support the GU inter-RAT MDT events.
RF Modules
No requirements
4.3.4 Others
● The eNodeB version is V100R011C00 or later.
● UEs are required to be compliant with 3GPP Release 10 or later and support
MDT.
● It is recommended that a network optimization analysis tool (for example,
Huawei Discovery) be deployed.
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
Table 4-4 Parameters used for activation

Parameter Name Parameter ID Setting Notes
TCE ID TceIpMapping.TceId Set this parameter

based on the
configuration.
IP Mode TceIpMapping.IPMode Set this parameter

based on the
configuration.
TCE IPv4 Address TceIpMapping.TceIpV4A Set this parameter

ddr based on the
configuration.
TCE IPv6 Address TceIpMapping.TceIpV6A Set this parameter

ddr based on the
configuration.

eRAN
Table 4-5 Parameters used for optimization
Parameter Name Parameter ID Setting Notes
Measurement CellAlgoSwitch.MeasOpt To subscribe to

Optimization Algorithm AlgoSwitch downlink SINR
Switch measurement, select
the
SINR_MEAS_CONFIG_S
W option.
4.4.1.2 Using MML Commands
Activation Command Examples

//Collecting logged MDT events
ADD TCEIPMAPPING: TceId=0, IPMode=IPv4, TceIpV4Addr="192.168.1.168";
Optimization Command Examples

//(Optional) Enabling UEs to report downlink SINR measurement results
MOD CELLALGOSWITCH: LocalCellId=0, MeasOptAlgoSwitch=SINR_MEAS_CONFIG_SW-1;
4.4.1.3 Using the MAE-Deployment

● Fast batch activation
This function can be batch activated using the Feature Operation and
Maintenance function of the MAE-Deployment. For detailed operations, see
the following section in the MAE-Deployment product documentation or
online help: MAE-Deployment Management > MAE-Deployment
Guidelines > Enhanced Feature Management > Feature Operation and
Maintenance.
● Single/Batch configuration
This function can be activated for a single base station or a batch of base
stations on the MAE-Deployment. For detailed operations, see Feature
Configuration Using the MAE-Deployment.
4.4.2 Activation Verification

Observe the traced messages from MDT cells on the MAE-Access to determine
whether MDT has taken effect.
Step 1 On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace
Management > S1 Interface Trace/UU Interface Trace to create trace tasks.
Step 2 Check the messages traced over the S1 and Uu interfaces for a specific user (users
can be identified by Call ID). If the S1AP_INITAIL_CONTEXT_SETUP_REQ message
traced over the S1 interface contains the Management Based MDT Allowed
parameter, and if the messages traced over the Uu interface include the
RRC_LOGGED_MEAS_CFG message or the RRC_CONN_RECFG message over the
Uu interface contains the ObtainLocation parameter, MDT has taken effect.
----End

eRAN
Cells can also be traced using the MAE-Access to determine whether MDT has
taken effect.
Step 1 After MDT subscription is successful on the MAE-Access, choose Monitor >
Signaling Trace > Signaling Trace Management > Cell Trace Browse. Then, click
New and select the target eNodeB and observation duration to create cell trace
browse tasks. The reported MDT events can be viewed, indicating that MDT has
taken effect.
----End
4.4.3 Network Monitoring

View the status of MDT subscription tasks or observe MDT counters to monitor
the MDT status on the MAE-Access.
1. View the status of MDT subscription tasks. If Status is displayed as Running

on the Signaling Trace Management tab page, the subscription task is
running properly.
2. Table 4-6 lists MDT counters.
Table 4-6 MDT counters
Counter ID Counter Name Counter Description
1526739732 L.MeasCtrl.MDTMeas. Number of times MDT

Num measurement
configurations are
delivered in a cell
1526739733 L.MeasCtrl.MDTReport Number of times MDT

.Num measurement reports
are sent in a cell
1526746668 L.Traffic.User.MDT.Av Average number of

g MDT-capable UEs in a
cell
NOTE
The L.MeasCtrl.MDTReport.Num counter only measures the number of MDT

measurement reports containing longitude and latitude.
4.4.4 Possible Issues

If no MDT data is reported, perform troubleshooting as follows:
1. Check whether MDT tasks have been successfully subscribed to and whether
an eNodeB/MAE fault alarm has been reported.
2. If MDT task subscription fails, resubscribe to the MDT tasks. If an
eNodeB/MAE fault alarm is reported, clear the alarm first.
3. Check whether MDT data is reported. If MDT data is reported, no further
action is required. If the problem persists, contact Huawei technical support.

eRAN
MDT Feature Parameter Description 5 Glossary
5 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
MDT Feature Parameter Description 6 Reference Documents
6 Reference Documents
● 3GPP TS 37.320, " Minimization of Drive Tests (MDT); Overall description "
● 3GPP TS 36.331, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio
Resource Control (RRC); Protocol specification"
● 3GPP TS 32.422, "Trace control and configuration management"
● Terminal Awareness Differentiation

MDT Feature Parameter Description: Issue Date

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MDT Feature Parameter Description: Issue Date

Uploaded by

Copyright:

Available Formats

eRAN

MDT Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................3

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. ii

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. iii

This chapter describes changes not included in the "Parameters", "Counters",

1.1 eRAN16.1 03 (2020-10-31)

1.2 eRAN16.1 02 (2020-08-31)

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 1

1.3 eRAN16.1 01 (2020-03-30)

1.4 eRAN16.1 Draft A (2020-01-20)

Added the function of None FDD ● 3900 and 5900

Changed the name of None FDD ● 3900 and 5900

Canceled the compatibility None FDD BTS3912E

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

Feature Differences Between RATs

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 3

2.2 Applicable RAT

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 4

After a network is deployed, multiple drive tests (DTs) must be performed to

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 5

4.1.1 MDT Architecture

Figure 4-1 MDT data collection architecture

Table 4-1 describes the functional units involved.

Table 4-1 Functional units

Functional Entity Description

UE Measures and reports MDT data to the eNodeB.

eNodeB Collects MDT data and reports it to the trace server

Core network Consists of the HSS and MME.

HSS Stores and transfers MDT subscription data.

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 6

Functional Entity Description

MME Delivers MDT UE subscription information during

TS Combines and delivers upper-layer subscription tasks,

MAE Subscribes to and controls MDT data.

Network optimization Analyzes and displays MDT data. Either Huawei

4.1.2 MDT Events

Table 4-2 MDT events

PERIOD_INTRAFREQ_ M1 M1 Intra-frequency MDT measurement

PERIOD_INTERFREQ_ M1 M1 Inter-frequency MDT measurement

PERIOD_INTER_RAT_ M1 M1 MDT GU inter-RAT measurement

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 7

Huawei MDT Event Northb Meas Meaning

PRIVATE_GU_MEASU M1 GU M1 MDT GU MR event

PERIOD_PRIVATE_UE M2 M2 UE MDT event: UE power headroom

PERIOD_LOGGED_M LOGGE M1 Logged MDT event: After

RLF_REPORT RLF M1 Radio link failure MDT event:

PERIOD_PRIVATE_TH M4/M5 M4/ Traffic volume/Throughput: UE traffic

PRIVATE_CONNEST_ RCEF M1 Connection setup failure MDT event:

PERIOD_A2_EVENT_ M1 A2 M1 A2 MDT event: periodic reporting of

PERIOD_PRIVATE_UL M3 M3 MDT uplink PRB noise interference

PERIOD_PRIVATE_TH M6 DL M6 Downlink data delay measurement

PERIOD_UE_ULPDCP M6 UL M6 Uplink data delay measurement

Issue 03 (2020-10-31) Copyright © Huawei Technologies Co., Ltd. 8

Huawei MDT Event Northb Meas Meaning

PERIOD_PRIVATE_PK M7 M7 Measurement of uplink and downlink

PERIOD_PRIVATE_UE M2-Ext None Measurement and reporting of the