Independent MDT (ERAN12.1 04)

eRAN
Independent MDT Feature

Parameter Description
Issue 04
Date 2017-12-06
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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: http://www.huawei.com
Email: support@huawei.com
Issue 04 (2017-12-06) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
Independent MDT Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Privacy Statement........................................................................................................................................................... 1
1.3 Disclaimer.......................................................................................................................................................................2
1.4 Intended Audience.......................................................................................................................................................... 2
1.5 Change History............................................................................................................................................................... 3
1.6 Differences Between eNodeB Types.............................................................................................................................. 4
2 Overview......................................................................................................................................... 5
2.1 Background.....................................................................................................................................................................5
2.2 Introduction.................................................................................................................................................................... 5
2.3 Benefits........................................................................................................................................................................... 5
2.4 Architecture.................................................................................................................................................................... 5
3 Technical Description...................................................................................................................7
4 Related Features...........................................................................................................................15
5 Network Impact........................................................................................................................... 16
6 Engineering Guidelines............................................................................................................. 17
6.1 When to Use................................................................................................................................................................. 17
6.2 Required Information................................................................................................................................................... 18
6.3 Planning........................................................................................................................................................................ 18
6.3.1 RF Planning............................................................................................................................................................... 18
6.3.2 Network Planning...................................................................................................................................................... 18
6.3.3 Hardware Planning.................................................................................................................................................... 18
6.4 Deployment.................................................................................................................................................................. 18
6.4.1 Process....................................................................................................................................................................... 18
6.4.2 Requirements............................................................................................................................................................. 18
6.4.3 Data Preparation and Feature Activation...................................................................................................................19
6.4.3.1 Data Preparation..................................................................................................................................................... 20
6.4.3.2 Using the CME....................................................................................................................................................... 20
6.4.3.3 Using MML Commands......................................................................................................................................... 21
6.4.3.4 MML Command Examples.................................................................................................................................... 21
6.4.4 Activation Observation..............................................................................................................................................21
Issue 04 (2017-12-06) Huawei Proprietary and Confidential ii

eRAN
Independent MDT Feature Parameter Description Contents
6.4.5 Deactivation...............................................................................................................................................................22
6.4.5.1 Using the CME....................................................................................................................................................... 23
6.4.5.2 Using MML Commands......................................................................................................................................... 23
6.4.5.3 MML Command Examples.................................................................................................................................... 23
6.5 Performance Monitoring...............................................................................................................................................23
6.6 Parameter Optimization................................................................................................................................................ 23
6.7 Possible Issues.............................................................................................................................................................. 24
7 Parameters..................................................................................................................................... 25
8 Counters........................................................................................................................................ 33
9 Glossary......................................................................................................................................... 34
10 Reference Documents............................................................................................................... 35
Issue 04 (2017-12-06) Huawei Proprietary and Confidential iii

eRAN
Independent MDT Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the Independent Minimization of Drive Test (MDT) feature,
including its technical principles, related features, network impact, and engineering
guidelines.
Feature compatibility with specific terminal models is not presented in this document. For
compatibility information, contact Huawei engineers.
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
1.2 Privacy Statement

Privacy Data List and Purpose
MDT collects personal data and privacy information, as listed in Table 1-1.
Table 1-1 Privacy data list and purpose
Privacy Data Type Application Scenario and Purpose
UE location MDT tracking records UE locations for DTs

and network optimization.
Privacy Protection
l Obtaining consent from data subjects for the collection of privacy data
Issue 04 (2017-12-06) Huawei Proprietary and Confidential 1

eRAN
According to the standard process specified in 3GPP Specifications, the eNodeB

performs MDT to collect UE locations only if the operator has obtained user consent and
configured user authorization in subscription information on the EPC side.
l Obtaining privacy data
The eNodeB performs MDT to collect locations of authorized UEs. According to the
standard process specified in 3GPP Specifications, a UE is considered authorized if the
IE Management Based MDT Allowed is contained in S1 signaling on the EPC side.
l Privacy data storage
Storage and access of UE locations collected by MDT require accounts and passwords
authorized by the operator. Accesses to UE locations are recorded in logs.
l Protection for exported privacy data
Exporting MDT data requires accounts and passwords authorized by the operator. All
operations are recorded in logs, and FTP transmission supports SFTP secure
transmission.
l Transfer of privacy data to third parties or cross-border privacy data export
The eNodeB neither transfers UE locations collected by MDT to third parties nor exports
such UE locations in another country.
l Privacy data deletion
UE locations collected by MDT are automatically deleted when the disk is full.
Suggestions on Privacy Data Operations

l The operator should obtain user authorization for collection of privacy data and perform
MDT to collect only data of authorized UE.
l Exported UE locations collected by MDT must be protected.
l Exporting MDT data, which contains UE locations, from operator networks must comply
with local laws.
Privacy Data Operation Statement

UE locations contained in MDT data are privacy data and may incur legal risks. Use such data
according to local industry laws.
1.3 Disclaimer
The MDT function obtains network quality test data, such as signal quality and signal
strength, from UEs with or without authorization. Consult lawyers before deploying
independent MDT on the networks. Penalties or prosecution may be imposed if the use of
independent MDT violates any laws applicable in the region, state, or country. Huawei is not
responsible for any losses, damages, or other liabilities of any sort that may incur for using the
Independent MDT feature in violation of laws.
1.4 Intended Audience

This document is intended for personnel who:
l Need to understand the feature described herein

eRAN
l Work with Huawei products
1.5 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN12.1 04 (2017-12-06)
This issue includes the following changes.
Change Type Change Description Paramete Affected Entity

r Change
Feature change None None N/A
Editorial Added a privacy statement. For None N/A

change details, see 1.2 Privacy
Statement.
eRAN12.1 03 (2017-08-30)

r Change
Editorial Revised descriptions in this None N/A

change document to improve
readability.
eRAN12.1 02 (2017-05-31)

r Change

eRAN

r Change
Editorial Revised descriptions in 3 None N/A

change Technical Description.
eRAN12.1 01 (2017-03-08)
This issue does not include any changes.
eRAN12.1 Draft A (2016-12-30)

eRAN 12.1 Draft A (2016-12-30) introduces the following changes to Issue 02 (2016-04-20)
of eRAN11.1.

r Change
Feature change Added the MDT whitelist None Macro, micro, and
function. For details, see 3 LampSite eNodeBs
Technical Description.
Editorial Revised descriptions in this None N/A

change document to improve
readability.
1.6 Differences Between eNodeB Types

Feature Support by Macro, Micro, and LampSite eNodeBs
The macro, micro, and LampSite eNodeBs all support this feature.
Function Implementation in Macro, Micro, and LampSite eNodeBs

This feature is implemented in the same way on macro, micro, and LampSite eNodeBs.

eRAN
Independent MDT Feature Parameter Description 2 Overview
2 Overview
2.1 Background
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. MDT automatically collects, reports, and preprocesses measurement data,
requiring less labor, equipment, and time than traditional manual DTs. However, MDT
requires that the mobility management entity (MME) supports the authentication function and
that UEs authorize the use of the MDT function, limiting the amount of MDT data to be
collected. To improve data collection efficiency, Huawei has introduced the Independent
MDT feature.
2.2 Introduction
With Independent MDT, the eNodeB selects UEs to automatically collect measurement data
without requiring authentication from the MME or the UEs. Telecom operators can use the
collected data to optimize networks, evaluate user experience, and address customer
complaints.
2.3 Benefits
This feature provides the following benefits:
l Lower labor, equipment, and time costs than manual DTs
l Extensive accurate DT data
l Exemption from authorization of UEs for MDT
2.4 Architecture
Figure 2-1 illustrates the network architecture for MDT data collection.

eRAN
Independent MDT Feature Parameter Description 2 Overview
Figure 2-1 Network architecture for MDT data collection
Table 2-1 describes the functional units involved.
Table 2-1 Functional units

Functional Unit 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
HSS Stores and transfers MDT authorization data

Independent MDT does not require the HSS to transfer
authorization data.
MME Delivers MDT authorization data

During management-based MDT data collection, the MME is
no longer required to deliver MDT contract data, reducing
operator-user contract costs.
Trace server (TS) Combines and delivers subscription tasks from the U2000,
and receives and stores MDT data reported by the eNodeB
The TS transmits data to the network optimization plane over
the northbound interface.
U2000 Subscribes to and controls MDT data
Network optimization Analyzes and displays MDT data

plane Either Huawei Nastar or a third-party network optimization
tool can be used as the network optimization plane.

eRAN
Independent MDT Feature Parameter Description 3 Technical Description
3 Technical Description
Figure 3-1 illustrates the MDT data collection principles.
Figure 3-1 MDT data collection principles
The MDT data collection procedure is as follows:

1. The operator creates MDT subscription tasks on the U2000 client.
During the subscription, the operator should select the events listed in Table 3-1.

eRAN
Table 3-1 MDT events

Meas MDT Huawei Northbo Descript Parameter Setting
ureme Mode MDT und ion
nt in Event MDT
Item Protoc Name Event
in ol Name
Protoc
ol
M1 Immedi PERIOD_I M1 Intra- Intra- l Period: 5120 ms,

ate NTRAFRE Freq frequenc 10,240 ms, 1 min
MDT Q_MR_M MDT y MDT l Number of times:
DT measure eight, sixteen, thirty-
ment two, sixty-four,
event infinite
Recommended values:
l 10,240 ms (period)
l Sixteen (number of
times)
M1 Immedi PERIOD_I M1 Inter- Inter- l Period: 5120 ms,

ate NTERFRE Freq frequenc 10,240 ms, 1 min
MDT Q_MR_M MDT y MDT l Number of times:
DT measure eight, sixteen, thirty-
ment two, sixty-four,
event infinite
Recommended values:
times)
M2 Other PERIOD_ M2 MDT UE MDT l Period: 5120 ms,

MDT PRIVATE_ event: 10,240 ms, 1 min
UE_MEAS measure l Number of times:
UREMEN ment of eight, sixteen, thirty-
T_MDT UE two, sixty-four,
power infinite
headroo
m Recommended values:
times)

eRAN

nt in Event MDT
in ol Name
Protoc
ol
M1 Logged PERIOD_ LOGGED Logged l Period: 5120 ms,

MDT LOGGED_ MDT MDT 10,240 ms, 20480 ms,
MDT_ME event: 30720 ms, 40960 ms,
ASUREM After 61440 ms
ENT measure l Connection duration:
ment of a 10 min, 20 min, 40
UE in the min, 60 min, 90 min,
idle state, 120 min
the
measure Recommended values:
ment l 10,240 ms (period)
result is l 10 min (connection
logged duration)
and the
log file is
temporari
ly saved
in the UE
memory.
The UE
reports
the log
file the
next time
it enters
the active
state.

eRAN

nt in Event MDT
in ol Name
Protoc
ol
M1 Other RLF_REP RLF Radio No parameters involved

MDT ORT Report link
MDT failure
MDT
event:
measure
ment data
of the
serving
cell,
neighbori
ng cells,
and the
UE's
location
in the
case of a
radio link
failure
(RLF)
M4/M Immedi PERIOD_ M4/M5 Traffic l Period: 5120 ms,

5 ate PRIVATE_ MDT volume/ 10,240 ms, 1 min
MDT THROUG Throughp l Number of times:
HPUT_ME ut: eight, sixteen, thirty-
ASUREM measure two, sixty-four,
ENT_MD ment of infinite
T UE
traffic Recommended values:
volume 10,240 ms (period)
and Sixteen (number of times)
throughp
ut.

eRAN

nt in Event MDT
in ol Name
Protoc
ol
M1 Other PRIVATE_ RCEF Connecti No parameters involved

MDT CONNEST Report on setup
_FAIL_RE MDT failure
PORT MDT
event:
measure
ment of
the
serving
cell,
neighbori
ng cells,
and the
UE's
location
in the
case of a
connectio
n setup
failure
M1 Immedi PERIOD_ M1 A2 A2 MDT l Period: 5120 ms,

ate A2_EVEN MDT event: 10,240 ms, 1 min
MDT T_MDT periodic l Number of times:
reporting eight, sixteen, thirty-
of A2 two, sixty-four,
MRs infinite
after the
A2 Recommended values:
measure l 10,240 ms (period)
ment l Sixteen (number of
threshold times)
is
reached

eRAN

nt in Event MDT
in ol Name
Protoc
ol
M3 Immedi PERIOD_ M3 MDT MDT l Period: 5120 ms,

ate PRIVATE_ uplink 10,240 ms, 1 min
MDT UL_NI_PR frame l Number of times:
B_MR noise eight, sixteen, thirty-
measure two, sixty-four,
ment infinite
Recommended values:
times)
NOTE
For details about 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.
2. The U2000 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 U2000.
4. The eNodeB selects UEs to collect MDT events based on MDT subscription tasks. Table
3-2 describes how an eNodeB selects UEs.
Table 3-2 Selecting UEs

Subscribing to MDT Events How to Select UEs
Intra-frequency, inter-frequency, and A2 The eNodeB selects UEs based on

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

capability messages contain the
loggedMeasurementsIdle-r10 IE.
Other MDT events Without being selected by the eNodeB,

UEs proactively report these events to the
eNodeB.

eRAN
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 plane (Huawei Nastar or a third-party network optimization
analysis tool) obtains MDT data from the TS for geographic display, helping operators
optimize networks.
NOTE
Huawei Nastar has an independent MDT event subscription interface, which delivers subscription
tasks and receives MDT reports through the TS. For detailed operations, see Nastar-related
documents.
Selecting UEs for Collection of Intra-Frequency, Inter-Frequency, and A2 MDT

Events
To collect intra-frequency, inter-frequency, and A2 MDT events, the eNodeB selects UEs as
follows:
1. The eNodeB checks whether GLOBALPROCSWITCH.PrivateMdtUeSelSwitch has
been turned on.
– If this switch has been turned on, Independent MDT is enabled.
When Independent MDT is enabled, the eNodeB considers all UEs to be candidate
MDT UEs, regardless of whether they are MDT-authorized UEs.
– If this switch has been turned off, MDT is enabled.
When MDT is enabled, the eNodeB checks whether UEs are MDT-authorized. If
they are, the eNodeB considers them to be candidate MDT UEs.
NOTE
l 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.
l Each time the eNodeB checks whether UEs are MDT-authorized, it also checks the inter-
frequency EARFCN capabilities of newly accessing UEs.
2. In every connection duration specified by the period and number of times, the eNodeB
selects UEs based on Cell-level traced UE count and using the following MDT UE
selection policies:
– Polling selection: The eNodeB randomly selects candidate MDT UEs in the active
state and with GNSS capabilities one by one.
– Capability-preferred selection: The eNodeB sorts UEs based on their measurement-
related capabilities and preferentially selects high-capability UEs.
n 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 TS36.331 V11.7.0.
○ loggedMeasurementsIdle-r10: indicates that the UE supports MDT-
related measurement in idle mode.
○ standaloneGNSS-Location-r10: indicates that the UE supports reporting
of longitude and latitude information in the MDT data.
○ Inter-frequency measurement and periodic intra-frequency measurement
capabilities
n When receiving a measurement task, the UE does not report MDT
measurement result if it does not have the related measurement capability.

eRAN
n 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
l If MDT events that require UE measurement are enabled, for example, the intra-frequency, inter-
frequency, and A2 MDT events, RRC connection reestablishments may increase if UEs supporting
MDT but not able to report MDT data are selected, causing an increase in the call drop rate. If there
are such UEs that may deteriorate KPIs on the live network, enable the MDT whitelist function
according to instructions in Terminal Awareness Differentiation Feature Parameter Description.
l If the number of periodic measurements for MDT events is infinite:
1. When the number of UEs in the cell is less than Cell-level traced UE count, 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 Cell-level traced UE count, the
eNodeB selects UEs for measurement only once and does not perform polling selection.
Activating UE GPS
Before collecting MDT intra-frequency measurement events, inter-frequency MDT
measurement events, and MDT A2 events, you can set the Active UE GPS parameter to true.
Then the eNodeB delivers the reconfiguration message IE obtainLocationConfig to instruct
MDT-authorized UEs to proactively enable GPS.
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(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:
Step 1 The eNodeB sends a Huawei-proprietary positioning request to the MME.
Step 2 The MME forwards the request to the positioning server.
Step 3 The positioning server and MME exchange positioning-assisted information through NAS
messages.
Step 4 The MME sends Huawei-proprietary messages carrying UE locations to the eNodeB.
----End

eRAN
Independent MDT Feature Parameter Description 4 Related Features
4 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

eRAN
Independent MDT Feature Parameter Description 5 Network Impact
5 Network Impact
System Capacity
When Independent MDT is enabled, reporting MDT data consumes Uu interface resources,
increasing the CPU usage by up to 5%.
Network Performance
When Independent MDT is enabled, intra-frequency or inter-frequency MDT measurement
may conflict with handover measurement, decreasing the access and handover success rates
by up to 0.5%.
Inter-frequency measurement causes UEs to enter the GAP state, and some subframes will be
temporarily unable to transmit data, slightly decreasing the average cell throughput.
Subscribing to the Logged MDT event may result in a slight decrease in the RRC connection
setup success rate if certain UEs are not compatible with this event.

eRAN
Independent MDT Feature Parameter Description 6 Engineering Guidelines
6 Engineering Guidelines
6.1 When to Use

l If Independent MDR is enabled, a large number of MDT MRs will be reported. For
commercial networks, enable this feature on a per cluster basis, not for the entire
network. It is recommended that the following MDT events be triggered:
– Intra-frequency measurement
– Radio link failure
– Connection setup failure
– Traffic volume/throughput
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
In the formula above, the average UE online duration is obtained using the following
formula:
L.E-RAB.SessionTime.UE.HighPrecision/L.Traffic.User.Avg/1000s
l Set the number of times for MDT event reporting to the same as the number of times for
MR reporting if both the MR and MDT functions are enabled.
l Do not enable the 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.
l Subscribing to the Logged MDT event may result in a slight decrease in the RRC
connection setup success rate when certain UEs are not compatible with this event. You
are advised to test compatibility of mainstream UEs with this event and add compatible
UEs in the MDT whitelist. MDT measurements are performed only for UEs in this
whitelist to avoid a negative network impact. For how to add such UEs in the whitelist,
see whitelist control in Terminal Awareness Differentiation Feature Parameter
Description.

eRAN
l Enable Independent MDT when there are more than 10 UEs supporting MDT per cell.
l Enable Independent MDT on networks where a large number of the eNodeBs are
outdoor macro base stations. Most UEs receive little MDT data from distributed
eNodeBs so this feature has little network optimization effect in such scenarios.
6.2 Required Information

Before deploying this feature, collect the following information:
l Number of UEs supporting MDT
l Sites vulnerable to network performance issues or customer complaints
6.3 Planning
6.3.1 RF Planning
N/A
6.3.2 Network Planning

N/A
6.3.3 Hardware Planning

N/A
6.4 Deployment
6.4.1 Process
Perform the following operations:
1. Set PrivateMdtUeSelSwitch to ON(On).
2. Subscribe to MDT tasks on the U2000.
6.4.2 Requirements
Hardware
l eNodeB
V100R011C00 or later
l TS
It is recommended that the TS be deployed in cluster mode based on the Advanced
Telecommunications Application Environment (ATAE), either co-deployed with the
U2000 or separated.
l UE
UEs must comply with 3GPP R10 or later, and support MDT.

eRAN
l Network optimization analysis tool

For example, Huawei Nastar
License
None
6.4.3 Data Preparation and Feature Activation

Step 1 Set Private MDT UE Selection Switch to ON(On).
Step 2 Subscribe to MDT tasks on the U2000.
On the U2000 client, choose Signaling Trace > Signaling Trace Management > Cell Trace
to create a trace task. In the Cell Trace dialog box, specify the following parameters: Trace
name, Cell trace ID, Select cells, Cell-level traced UE count., TCE IP (consistent with the
setting of TCEIPMAPPING.TceIpV4Addr or TCEIPMAPPING.TceIpV6Addr for the
eNodeB), Trace Depth, and Trace Duration.
NOTE
l Anywhere from 5 to 100 cells can be traced simultaneously on the U2000, depending on the license
and the TS deployment mode.
l The data for a maximum of 400 UEs can be collected. (If the corresponding parameter is set to 0, the
number of UEs is infinite.)
l For details about MDT subscription and analysis, see iManager U2000 MBB Network System Online
Help for V200R016.
l If maximum-depth traced signaling data is collected with the MDT data, the UE selection method
used by the maximum-depth traced signaling data is preferred. Specifically, UEs that have accessed
the network most recently and are in RRC_CONNECTED mode are selected. For details about
maximum-depth signaling data trace, see section 5.3 in 3GPP TS 32.422 V11.8.1.
Step 3 Set event parameters for subscription tasks.
After you select an MDT event, click Setting. The Parameter Settings dialog box is
displayed. Specify Measurement report period, Measurement report times, MDT UE
selection method, and Active UE GPS.
NOTE
l Subscription to MDT events by cell tracing is subject to the U2000 specification expressed in terms
of the number of UEs that can be traced, and event M3 cannot be subscribed by cell tracing. The TS
can be used to subscribe to MDT events. For details about the U2000 specification expressed in
terms of the number of UEs that can be traced during cell tracing and TS operations, see iManager
U2000 MBB Network Management System Product Documentation.
l If Measurement report times is set to Infinite, UEs in RRC_CONNECTED mode may keep
reporting measurement data indefinitely, which increases the power consumption of the UEs.
l If MDT UE selection method is set to different values for different MDT events, the eNodeB will
use the polling method to select UEs.
l If Active UE GPS is set to true for some MDT events but to false for others, the eNodeB considers
the GPS function unable to be activated for all MDT events.
----End

eRAN
6.4.3.1 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for
a specific feature deployment scenario.
Required Data
Table 6-1 Parameter in the GLOBALPROCSWITCH MO
Parameter Name Parameter ID Setting Notes
Private MDT UE Selection GLOBALPROCSWITCH. To enable Independent

Switch PrivateMdtUeSelSwitch MDT, set this parameter to
ON(On). To enable MDT,
set this parameter to
OFF(Off).
Scenario-specific Data
To collect logged MDT events, configure mapping between the Trace Collection Entity (TCE)
IDs and IP addresses. When initiating logged MDT subscription, specify which TCE to
receive reported data. When requesting subscriptions, the U2000 transfers TCE IP parameters
to the eNodeB.
Table 6-2 Parameters in the TCEIPMAPPING MO
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.TceIpV4 Set this parameter based on

Addr the configuration.
TCE IPv6 Address TCEIPMAPPING.TceIpV6 Set this parameter based on

Addr the configuration.
6.4.3.2 Using the CME

l Fast batch activation
This feature can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/batch configuration

eRAN
This feature can be activated for a single eNodeB or a batch of eNodeBs on the CME.
For detailed operations, see CME-based Feature Configuration.
6.4.3.3 Using MML Commands

Step 1 Run the MOD GLOBALPROCSWITCH command with the Private MDT UE Selection
Switch parameter set to ON(On).
MOD GLOBALPROCSWITCH: PrivateMdtUeSelSwitch=ON;
Step 2 To collect logged MDT events, run the ADD TCEIPMAPPING command to add a mapping
between the TCE ID and IP address. The number of TCE IDs is determined by the number of
IP addresses for the TCEs onsite.
ADD TCEIPMAPPING: TceId=0, IPMode=IPv4, TceIpV4Addr="192.168.1.168";
----End
6.4.3.4 MML Command Examples

//Enabling Independent Minimization of Drive Tests
MOD GLOBALPROCSWITCH:PrivateMdtUeSelSwitch=ON;
//Collecting Logged MDT events

ADD TCEIPMAPPING: TceId=0, IPMode=IPv4, TceIpV4Addr="192.168.1.168";
6.4.4 Activation Observation

Observe the traced messages from MDT cells on the U2000 to determine whether the
Independent MDT feature has taken effect.
Step 1 On the U2000 client, 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 UE (UEs can be
identified using Call ID). If the following conditions are met, this feature has taken effect:
l The S1AP_INITAIL_CONTEXT_SETUP_REQ message traced over the S1 interface
does not contain the Management Based MDT Allowed parameter.
l 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
includeLocationInfo parameter.
Figure 6-1 Messages traced over the S1 interface

eRAN
Figure 6-2 Messages traced over the Uu interface
----End
Cells can also be traced using the U2000 to determine whether MDT has taken effect.
Step 1 After MDT subscription is successful on the U2000, 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 the Independent MDT feature has taken effect. The following
figure illustrates an example.
Figure 6-3 Cell trace browse
----End
6.4.5 Deactivation
Step 1 On the U2000 client, choose Signaling Trace > Signaling Trace Management > Cell Trace.
Right-click the trace task and choose Stop from the shortcut menu to cancel the subscription
task.

eRAN
Step 2 Set Private MDT UE Selection Switch to OFF(Off).
----End
6.4.5.1 Using the CME

For detailed operations, see CME-based Feature Configuration.
6.4.5.2 Using MML Commands

Run the MOD GLOBALPROCSWITCH command with the Private MDT UE Selection
Switch parameter set to OFF(Off).
6.4.5.3 MML Command Examples

MOD GLOBALPROCSWITCH:PrivateMdtUeSelSwitch=Off;
6.5 Performance Monitoring

View the status of MDT subscription tasks or observe MDT counters to monitor the MDT
status on the U2000.
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, as
shown in the following figure.
2. Observe the MDT counters listed in Table 6-3.
Table 6-3 MDT counters

Counter ID Counter Name Counter Description
1526739732 L.MeasCtrl.MDTMeas.N Number of times MDT

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

Num measurement reports are
sent in a cell
NOTE
L.MeasCtrl.MDTReport.Num only measures the number of MDT measurement reports containing the
longitude and latitude.
6.6 Parameter Optimization

N/A

eRAN
6.7 Possible Issues

If no MDT data is reported, perform the troubleshooting as follows:
1. Check whether MDT tasks have been successfully subscribed to and whether an
eNodeB/U2000 fault alarm has been reported.
2. If MDT task subscription failed, resubscribe to the MDT tasks. If an eNodeB/U2000
fault alarm was 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
Independent MDT Feature Parameter Description 7 Parameters
7 Parameters
Table 7-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
GlobalP Private MOD None None Meaning: Indicates whether to use a private
rocSwitc MdtUeS GLOBA mechanism for management-based MDT data
h elSwitch LPROC collection. If this parameter is set to ON, the eNodeB
SWITC does not use authentication information to select UEs.
H If this parameter is set to OFF, the eNodeB selects
LST UEs in accordance with 3GPP specifications. This
GLOBA parameter applies only to LTE FDD and LTE TDD.
LPROC GUI Value Range: OFF(Off), ON(On)
SWITC Unit: None
H
Actual Value Range: OFF, ON
Default Value: OFF(Off)

eRAN

nd
GlobalP Protocol MOD LOFD-0 SRVCC Meaning:

rocSwitc MsgOpt GLOBA 01022/ to Indicates whether to optimize protocol messages sent
h Switch LPROC TDLOF UTRAN by the eNodeB. This parameter provides the following
SWITC D-00102 SRVCC options:
H 2 to
LST LOFD-0 RrcSetupOptSwitch: If this option is selected,
GERAN
GLOBA 01023/ optimization of RRCConnectionSetup messages is
Ultra- enabled. In this case, IEs with protocol-defined default
LPROC TDLOF
Flash values are no longer included in the
SWITC D-00102
CSFB to RRCConnectionSetup messages. For details about the
H 3
GERAN protocol-defined default settings, see 3GPP TS
LOFD-0 36.331. This option applies only to LTE FDD and LTE
Flash
81283/ TDD.
CS
TDLOF
Fallback IucsRrcRecfgMcCombSwitch: If this option is
D-08120
to selected, the eNodeB includes the radio resource
3
GERAN configuration and measurement configuration for a
LOFD-0
PS Inter- UE in one RRCConnectionReconfiguration message
01053/
RAT during initial access. This option applies only to LTE
TDLOF
Mobility FDD and LTE TDD.
D-00105
3 between
RcrpRrcRecfgMcCombSwitch: If this option is
E-
LOFD-0 selected, the eNodeB includes the radio resource
UTRAN
01020/ configuration and measurement configuration for a
and
TDLOF UE in one RRCConnectionReconfiguration message
GERAN
D-00102 during RRC connection reestablishment. The option
0 PS Inter- will not take effect on the interaction of RRC
RAT connection reestablishment and other signaling
TDLOF Mobility procedures. This option applies only to LTE FDD and
D-00101 between LTE TDD.
9/ E-
LOFD-0 UTRAN RrcRecfgMcOptSwitch: If this option is selected, the
01019 and cell measurement configurations with the CIO of 0
LBFD-0 UTRAN (indicated by cellIndividualOffset) are no longer
02007/ included in the measurement configurations delivered
RRC to UEs. This option applies only to LTE FDD and LTE
TDLBF
Connect TDD.
D-00200
ion
7
Manage IdleCsfbRedirectOptSwitch: If this option is selected
LBFD-0 ment and the preferred CSFB policy is redirection, during
02018/ CSFB of UEs in idle mode, the eNodeB no longer
Mobility
TDLBF activates the security mode or performs RRC
Manage
D-00201 connection reconfiguration, but sends a redirection
ment
8 message. This option applies only to LTE FDD and
LOFD-0 CS LTE TDD.
01033/ Fallback
to UlNasBufferSwitch: If this option is selected, the
TDLOF eNodeB buffers uplink NAS messages sent by the UE
D-00103 UTRAN
before the UE-associated logical S1 connection is
3 CS available and sends these messages after the UE-
Fallback associated logical S1 connection is available. If this

eRAN

nd
LOFD-0 to option is deselected, the eNodeB releases this UE after

01034/ GERAN the procedures end. This option applies only to LTE
TDLOF RAN FDD and LTE TDD.
D-00103 Sharing IratMeasCfgTransSwitch: If this option is selected, the
4 with Handover Required message that the eNodeB sends to
LOFD-0 Commo a BSC contains the IE IRAT Measurement
01036/ n Configuration. This option applies only to LTE FDD
TDLOF Carrier and LTE TDD.
D-00103
6 GeranAnrMcOptSwitch: This option controls whether
measurement configuration optimization takes effect
when ANR with GERAN is enabled. If this option is
deselected, the optimization does not take effect. That
is, when an eNodeB delivers measurement
configuration to UEs to perform CGI reading for ANR
with GERAN, the carrierFreqs IE can contain multiple
GERAN frequencies. If this option is selected, the
optimization takes effect, and the carrierFreqs IE
contains only one GERAN frequency. This option
applies only to LTE FDD and LTE TDD.
InactDiscardSwitch: This option specifies whether to
terminate the ongoing signaling flow when the UE
inactivity timer expires. If this option is deselected,
the ongoing flow is terminated and the eNodeB
directly releases the UE. If this option is selected, the
ongoing flow is not terminated and the timer is
restarted. This option applies only to LTE FDD and
LTE TDD.
SRVCCHoBasedUeCapSwitch: If this option is
selected, the eNodeB determines whether to trigger an
SRVCC based only on UE's SRVCC capabilities, not
the SRVCCOperationPossible IE that the MME sends
to the eNodeB. If this option is deselected, the
eNodeB determines whether to trigger an SRVCC
based on the SRVCCOperationPossible IE that the
MME sends to the eNodeB. This option applies only
to LTE FDD and LTE TDD.
L2GPLMNChooseOptSwitch: This option specifies
whether to enable target PLMN ID optimization for
handovers to GERAN. If this option is selected, the
eNodeB takes the NCL-defined PLMN IDs and
includes them in the handover request messages or
RIM request messages. If this option is deselected, the
optimization is not activated. This option applies only
HoInRrcRecfgMcCombSwitch: If this option is
selected, after a UE is handed over to a cell, the cell

eRAN

nd
delivers the radio resource configuration and

measurement configuration in a single RRC
Connection Reconfiguration message to the UE
during the resource reconfiguration procedure. This
option applies only to LTE FDD and LTE TDD.
UeCapEnquiryCombSwitch: If this option is selected
and a UE sends an Attach Request message to an
eNodeB during initial access, the eNodeB directly
queries capabilities of the UE after the RRC
connection for the UE is established. This option does
not apply to subsequent UE capability query induced
by the CA extended frequency band combination
query. If this option is deselected and a UE sends an
Attach Request message to an eNodeB during initial
access, the eNodeB does not query capabilities of the
UE until the MME sends a UE context setup request
to the eNodeB. This option applies only to LTE FDD
and LTE TDD.
UeTraceOptSwitch: If this option is selected, the
eNodeB does not handle the DEACTIVATE TRACE
message sent by the MME or stop the UE tracing task
in the eNodeB until the UE is released or handed over
to a cell served by another eNodeB. This option
PaDistributeMechOptSwitch: If this option is selected,
the PaPcOff parameter value is taken as the PA value
in the RRCConnectionSetup or RRC Connection
Reestablishment message. If this option is deselected,
the PA value is set to -3 dB by default. This option
InactReSyncCompatSwitch: If this option is selected
and the eNodeB determines that the UE inactivity
timer expires and the resynchronization procedure is
being performed, the eNodeB preferentially processes
the resynchronization procedure and the timer restarts.
If this option is deselected, the optimization does not
take effect. That is, the UE is directly released when
the UE inactivity timer expires. This option applies
only to LTE FDD and LTE TDD.
VolteX2HoDelayOptSwitch: If this option is selected,
when receiving a VoLTE UE handover complete
message, the target eNodeB for an X2-based handover
starts to send uplink data with QCI of 1. If this option
is deselected, the target eNodeB for an X2-based
handover starts to send uplink data with QCI of 1 after
receiving an MME PATH SWITCH REQUEST

eRAN

nd
ACKNOWLEDGE message. This option applies only

UeUtranCapEnquiryOptSwitch: When a serving cell
is not configured with neighboring UTRAN cells, the
eNodeB does not query UE's UTRAN capability if
this option is selected. If this option is deselected, this
optimization does not take effect. This option applies
only to LTE TDD.
FreqRandomOptSwitch: If this option is selected, the
eNodeB randomly selects a target frequency when
there are multiple candidate frequencies with the same
priority. If this option is deselected, this optimization
function does not take effect. This option applies only
MrMdtMeasOptSwitch: If this option is selected,
measurement configurations related to MR and MDT
based on Intra-Frequency and Inter-Frequency are
delivered separately. If this option is deselected, this
optimization does not take effect. This option applies
only to LTE FDD and LTE TDD.
GUI Value Range: RrcSetupOptSwitch,
IucsRrcRecfgMcCombSwitch,
RcrpRrcRecfgMcCombSwitch,
RrcRecfgMcOptSwitch, IdleCsfbRedirectOptSwitch,
UlNasBufferSwitch, IratMeasCfgTransSwitch,
GeranAnrMcOptSwitch, InactDiscardSwitch,
SRVCCHoBasedUeCapSwitch,
L2GPLMNChooseOptSwitch,
HoInRrcRecfgMcCombSwitch,
UeCapEnquiryCombSwitch, UeTraceOptSwitch,
PaDistributeMechOptSwitch, InactReSyncCompatS-
witch, VolteX2HoDelayOptSwitch,
UeUtranCapEnquiryOptSwitch,
FreqRandomOptSwitch, MrMdtMeasOptSwitch
Unit: None
Actual Value Range: RrcSetupOptSwitch,
IucsRrcRecfgMcCombSwitch,
RcrpRrcRecfgMcCombSwitch,
RrcRecfgMcOptSwitch, IdleCsfbRedirectOptSwitch,
UlNasBufferSwitch, IratMeasCfgTransSwitch,
GeranAnrMcOptSwitch, InactDiscardSwitch,
SRVCCHoBasedUeCapSwitch,
L2GPLMNChooseOptSwitch,
HoInRrcRecfgMcCombSwitch,
UeCapEnquiryCombSwitch, UeTraceOptSwitch,
PaDistributeMechOptSwitch, InactReSyncCompatS-

eRAN

nd
witch, VolteX2HoDelayOptSwitch,
UeUtranCapEnquiryOptSwitch,
FreqRandomOptSwitch, MrMdtMeasOptSwitch
Default Value: RrcSetupOptSwitch:Off,
IucsRrcRecfgMcCombSwitch:Off,
RcrpRrcRecfgMcCombSwitch:Off,
RrcRecfgMcOptSwitch:Off, IdleCsfbRedirectOptS-
witch:Off, UlNasBufferSwitch:On,
IratMeasCfgTransSwitch:Off,
GeranAnrMcOptSwitch:Off, InactDiscardSwitch:Off,
SRVCCHoBasedUeCapSwitch:Off,
L2GPLMNChooseOptSwitch:Off,
HoInRrcRecfgMcCombSwitch:Off,
UeCapEnquiryCombSwitch:Off,
UeTraceOptSwitch:Off, PaDistributeMechOptS-
witch:On, InactReSyncCompatSwitch:Off,
VolteX2HoDelayOptSwitch:Off, UeUtranCapEnquir-
yOptSwitch:Off, FreqRandomOptSwitch:Off,
MrMdtMeasOptSwitch:Off
MmeFea MdtEna MOD None None Meaning: Indicates whether the MME at the other end
tureCfg ble MMEFE of the S1 interface supports Huawei-proprietary
ATURE positioning procedures, which are included in
CFG minimization of drive tests (MDT). The value
LST DISABLE indicates that the MME does not support
MMEFE the procedures and therefore the eNodeB cannot
ATURE obtain UE location information from the MME
CFG through the procedures. The value ENABLE indicates
the opposite. This parameter applies only to LTE FDD
and LTE TDD.
GUI Value Range: DISABLE(Disable),
ENABLE(Enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: DISABLE(Disable)

eRAN

nd
TceIpM TceIpV4 ADD None None Meaning: Indicates the IPv4 address of the TCE.
apping Addr TCEIP GUI Value Range: Valid IP address
MAPPI
NG Unit: None
MOD Actual Value Range: Valid IP address

TCEIP Default Value: 0.0.0.0
MAPPI
NG
LST
TCEIP
MAPPI
NG
TceIpM TceIpV6 ADD None None Meaning: Indicates the IPv6 address of the TCE.
apping Addr TCEIP GUI Value Range: Valid IP address
MAPPI
NG Unit: None
MOD Actual Value Range: Valid IP address

TCEIP Default Value: 0:0:0:0:0:0:0:0
MAPPI
NG
LST
TCEIP
MAPPI
NG
TceIpM TceId ADD None None Meaning: Indicates the ID of the TCE for MDT. This
apping TCEIP parameter applies only to LTE FDD and LTE TDD.
MAPPI GUI Value Range: 0~255
NG
Unit: None
LST
TCEIP Actual Value Range: 0~255
MAPPI Default Value: None
NG
MOD
TCEIP
MAPPI
NG
RMV
TCEIP
MAPPI
NG

eRAN

nd
TceIpM IPMode ADD None None Meaning: Indicates the IP address version. IPv4
apping TCEIP indicates that the IP version is IPv4. IPv6 indicates
MAPPI that the IP version is IPv6.
NG GUI Value Range: IPv4(IPv4 Address), IPv6(IPv6
MOD Address)
TCEIP Unit: None
MAPPI
NG Actual Value Range: IPv4, IPv6
LST Default Value: IPv4(IPv4 Address)

TCEIP
MAPPI
NG

eRAN
Independent MDT Feature Parameter Description 8 Counters
8 Counters
Table 8-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526727378 L.Traffic.User.Avg Average number of Multi-mode: None RRC Connection

users in a cell GSM: None Management
UMTS: None RRC Connection
Management
LTE:
LBFD-002007
TDLBFD-002007
1526735160 L.E- Total duration of Multi-mode: None Radio Bearer

RAB.SessionTime. UE data GSM: None Management
UE.HighPrecision transmission time Radio Bearer
with the precision UMTS: None
Management
of 100 milliseconds LTE:
in a cell LBFD-002008 Basic Scheduling
TDLBFD-002008 Basic Scheduling
LBFD-002025
TDLBFD-002025
1526739732 L.MeasCtrl.MDTM Number of times None None

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

eport.Num MDT measurement
reports are sent in a
cell

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

eRAN
Independent MDT Feature Parameter Description 10 Reference Documents
10 Reference Documents
[1] 3GPP TS 37.320, "Minimization of Drive Tests (MDT); Overall description"

[2] 3GPP TS 36.331, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio
Resource Control (RRC); Protocol specification"
[3] 3GPP TS 32.422, "Trace control and configuration management"


Independent MDT (ERAN12.1 04)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Independent MDT (ERAN12.1 04)

Hochgeladen von

Copyright:

Verfügbare Formate

eRAN

Independent MDT Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2017-12-06) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue 04 (2017-12-06) Huawei Proprietary and Confidential ii

Issue 04 (2017-12-06) Huawei Proprietary and Confidential iii

1 About This Document

1.2 Privacy Statement

Table 1-1 Privacy data list and purpose

Privacy Data Type Application Scenario and Purpose

UE location MDT tracking records UE locations for DTs

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 1

According to the standard process specified in 3GPP Specifications, the eNodeB

Suggestions on Privacy Data Operations

Privacy Data Operation Statement

1.4 Intended Audience

l Need to understand the feature described herein

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 2

l Work with Huawei products

1.5 Change History

Change Type Change Description Paramete Affected Entity

Feature change None None N/A

Editorial Added a privacy statement. For None N/A

Change Type Change Description Paramete Affected Entity

Feature change None None N/A

Editorial Revised descriptions in this None N/A

Change Type Change Description Paramete Affected Entity

Feature change None None N/A

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 3

Change Type Change Description Paramete Affected Entity

Editorial Revised descriptions in 3 None N/A

eRAN12.1 Draft A (2016-12-30)

Change Type Change Description Paramete Affected Entity

Editorial Revised descriptions in this None N/A

1.6 Differences Between eNodeB Types

Function Implementation in Macro, Micro, and LampSite eNodeBs

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 4

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 5

Figure 2-1 Network architecture for MDT data collection

Table 2-1 describes the functional units involved.

Table 2-1 Functional units

UE Measures and reports MDT data to the eNodeB

HSS Stores and transfers MDT authorization data

MME Delivers MDT authorization data

U2000 Subscribes to and controls MDT data

Network optimization Analyzes and displays MDT data

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 6

Figure 3-1 illustrates the MDT data collection principles.

Figure 3-1 MDT data collection principles

The MDT data collection procedure is as follows:

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 7

Table 3-1 MDT events

M1 Immedi PERIOD_I M1 Intra- Intra- l Period: 5120 ms,

M1 Immedi PERIOD_I M1 Inter- Inter- l Period: 5120 ms,

M2 Other PERIOD_ M2 MDT UE MDT l Period: 5120 ms,

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 8

Meas MDT Huawei Northbo Descript Parameter Setting

M1 Logged PERIOD_ LOGGED Logged l Period: 5120 ms,

Issue 04 (2017-12-06) Huawei Proprietary and Confidential 9

Meas MDT Huawei Northbo Descript Parameter Setting