MDT Data Collection Guide
Issue 01
Date 2017-02-15
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 01 (2017-02-15) Huawei Proprietary and Confidential i
Copyright © Huawei Technologies Co., Ltd.
MDT Data Collection Guide
Author
Prepared By Jia Mingbo (employee ID: 00295291) Date 2017-02-15
Reviewed By Date
Approved By Date
Change History
Date Revision CR ID Section Change Description Author
Version Number
2017-02-15 1.00 Completed the draft. Jia Mingbo (employee
ID: 00295291)
Issue 01 (2017-02-15) Huawei Proprietary and Confidential ii
Copyright © Huawei Technologies Co., Ltd.
MDT Data Collection Guide Contents
Contents
1 Engineering Guidelines for MDT Data Collection Enabling .............................................. 1
1.1 Enabling Suggestions.................................................................................................................................................... 1
1.2 Enabling Requirements ................................................................................................................................................. 1
1.2.1 Hardware ................................................................................................................................................................... 1
1.2.2 License ....................................................................................................................................................................... 2
1.3 MDT Activation and Deactivation ................................................................................................................................ 2
1.3.1 MDT Activation ......................................................................................................................................................... 2
1.3.2 (Optional) Activation Observation ............................................................................................................................. 2
1.3.3 MDT Deactivation ..................................................................................................................................................... 3
1.4 MDT Data Collection Subscription Guide .................................................................................................................... 3
2 (Optional) Compatibility Issue .................................................................................................. 7
Issue 01 (2017-02-15) Huawei Proprietary and Confidential iii
Copyright © Huawei Technologies Co., Ltd.
MDT Data Collection Guide 1 Engineering Guidelines for MDT Data Collection Enabling
1 Engineering Guidelines for MDT Data
Collection Enabling
1.1 Enabling Suggestions
When Minimization of Drive Tests (MDT) is to be enabled on commercial networks, you
are advised to gradually enable this function by cluster instead of enabling it on the
entire network at one attempt because MDT measurement reports (MRs) are of a large
number.
You can use the following formula to calculate the number of reported MDT MRs:
Number of MDT MRs = Number of selected UEs x Number of times MRs are reported
If the number of times MRs are reported is "infinite", the number of times the UE reports MRs need to
be calculated using the following formulas:
− Number of times a UE reports MRs = Average UE online duration/MR reporting period
− Average UE online duration = L.E –
RAB.SessionTime.UE.HighPrecision/L.Traffic.User.Avg/1000s
Subscription of MDT inter-frequency measurement and A2 events has impacts on
network performance. You are advised to subscribe these events only when
inter-frequency MDT data needs to be analyzed in the case of network problems and
cancel the subscription after required data is collected.
To enable MDT, the number of MDT-capable UEs in each cell must be greater than five.
You are advised to enable MDT in outdoor scenarios where macro eNodeBs are mainly
used. Under indoor-distributed eNodeBs, most UEs cannot receive GPS information and
receive little MDT data with valid location information, resulting in limited network
improvement effects.
1.2 Enabling Requirements
1.2.1 Hardware
The eNodeB version must be V100R011C00 or later.
The U2000 version must be V200R016C00 or later.
It is recommended that the Trace Server be co-deployed with the U2000 in an ATAE
cluster system or independently deployed in an ATAE cluster system.
MDT Data Collection Guide 1 Engineering Guidelines for MDT Data Collection Enabling
The UE version must be R10 or later.
1.2.2 License
None
1.3 MDT Activation and Deactivation
1.3.1 MDT Activation
On the U2000, run the following commands to activate MDT measurement control.
Specifically:
Run the following command for each eNodeB with standalone MDT to be activated:
MOD GLOBALPROCSWITCH:PrivateMdtUeSelSwitch=ON;
If logged MDT event blocks are to be collected, run ADD TCEIPMAPPING for each
eNodeB with standalone MDT to be activated, to construct the mapping between Traffic
Channel Element (TCE) IDs and IP addresses for the eNodeB on the U2000. The number of
TCE IDs depends on that of Trace Server IP addresses in use. The TCE IP is consistent with
the value of TCEIPMAPPING.TceIpV4Addr or TCEIPMAPPING.TceIpV6Addr.
ADD TCEIPMAPPING: TceId=0, IPMode=IPv4, TceIpV4Addr="xxx.xxx.xxx.xxx";
Figure 1-1 MML command interface
1.3.2 (Optional) Activation Observation
You can check whether standalone MDT takes effect using either of the following methods:
On the U2000, observe tracing messages of the MDT cell.
Issue 01 (2017-02-15) Huawei Proprietary and Confidential 2
Copyright © Huawei Technologies Co., Ltd.
MDT Data Collection Guide 1 Engineering Guidelines for MDT Data Collection Enabling
On the U2000, choose Monitor > Signaling Trace > Signaling Trace Management >
S1 Interface Trace/UU Interface Trace, to create trace tasks. You can determine that
standalone MDT takes effect when both of the following conditions are met for the same
user (you can identify users based on the call ID):
− The S1AP_INITAIL_CONTEXT_SETUP_REQ message traced over the S1 interface
does not carry the Management Based MDT Allowed parameter.
− The RRC_LOGGED_MEAS_CFG or RRC_CONN_RECFG message traced over the
Uu interface carries the includeLocationInfo parameter.
Use the U2000 cell trace browse function.
After MDT is successfully subscribed 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 browse tasks. If you can
view the reported MDT data, standalone MDT takes effect.
1.3.3 MDT Deactivation
After MDT is unsubscribed on the U2000, run the following command to deactivate MDT
measurement control for each eNodeB enabled with standalone MDT:
MOD GLOBALPROCSWITCH:PrivateMdtUeSelSwitch=off;
1.4 MDT Data Collection Subscription Guide
You can subscribe to MDT data collection on the NIC or U2000. Note that logged MDT data
can be collected only by the U2000. This section describes how to subscribe to MDT data
collection on the U2000.
The MDT data is saved in the following path on the U2000:
/export/home/sysm/internalftp/internalfiles/enodeb/data/enodeb_sig/
Step 1 On the U2000, choose Monitor > Signaling Trace > Signaling Trace Management > Cell
Trace, to create a trace task.
Figure 1-2 Cell Trace interface
Issue 01 (2017-02-15) Huawei Proprietary and Confidential 3
Copyright © Huawei Technologies Co., Ltd.
MDT Data Collection Guide 1 Engineering Guidelines for MDT Data Collection Enabling
Step 2 In the Cell Trace interface, perform the following configurations:
Set Trace Name randomly.
Set Cell trace ID randomly.
Select Select by NE, and then select eNodeBs for data collection.
Figure 1-3 Select cells interface
Sometimes, Select by NE is unavailable because the U2000 is lack of the batch subscription license. In
this case, manually select corresponding cells or buy the corresponding license.
Set Cell-level traced UE count to the recommended value 400 (the maximum value).
Set TCE IP as required.
Set Trace Depth to the default value Medium.
Set Message Type to the event block to be enabled with data collection.
Set Trace Depth as required.
The following figures show the Cell Trace interface.
Issue 01 (2017-02-15) Huawei Proprietary and Confidential 4
Copyright © Huawei Technologies Co., Ltd.
MDT Data Collection Guide 1 Engineering Guidelines for MDT Data Collection Enabling
Figure 1-4 Cell Trace interface
Step 3 Click Setting.
The sampling period configuration interface is displayed.
PERIOD_INTRA_FREQ_MR_MDT
PERIOD_LOGGED_MDT_MEASUREMENT
Issue 01 (2017-02-15) Huawei Proprietary and Confidential 5
Copyright © Huawei Technologies Co., Ltd.
MDT Data Collection Guide 1 Engineering Guidelines for MDT Data Collection Enabling
PERIOD_PRIVATE_UE_MEASUREMENT
PERIOD_PRIVATE_UE_MEASUREMENT_MDT
----End
Issue 01 (2017-02-15) Huawei Proprietary and Confidential 6
Copyright © Huawei Technologies Co., Ltd.
MDT Data Collection Guide 2 (Optional) Compatibility Issue
2 (Optional) Compatibility Issue
At a site, after intra-frequency MRs and intra-frequency MR_MDT events are subscribed,
some UEs do not respond to the measurement control delivered by the eNodeB. As a result,
only a few intra-frequency MRs are reported, and the proportion that the RSRP value is
invalid increases.
Preventive measure:
On the eNodeB, run the following commands:
ADD ABLMSG: RuleIndex=0, RuleCfgType=ALL, MsgItfType=RRC, MsgType=54,
MsgOpType=MODIFY, MatchCount=ONE, MatchFieldOffSet1=32, MatchLen1=8,
MatchContent1="0x02", ModifyCount=TWO, ModifyFieldOffSet1=228640, ModifyLen1=32,
ModifyContent1="0xFFFFFFFF", ModifyFieldOffSet2=59078, ModifyLen2=1,
ModifyContent2="0xff";
ADD ABLMSG: RuleIndex=1, RuleCfgType=ALL, MsgItfType=RRC, MsgType=54,
MsgOpType=MODIFY, MatchCount=ONE, MatchFieldOffSet1=32, MatchLen1=8,
MatchContent1="0x03", ModifyCount=TWO, ModifyFieldOffSet1=228640, ModifyLen1=32,
ModifyContent1="0xFFFFFFFF", ModifyFieldOffSet2=59078, ModifyLen2=1,
ModifyContent2="0xff";
1. The commands are executed when intra-frequency MRs and intra-frequency MR_MDT events are
subscribed, to prevent the problem that the proportion of invalid RSRP values increases.
2. After the commands are executed, a small number of UEs may experience call drops and
re-establishments due to implementation mechanisms. After the commands are executed at a site,
KPIs related to call drops and re-establishments do not fluctuate. The risks are low.
3. Rollback scripts:
RMV ABLMSG: RuleIndex = 0;
RMV ABLMSG: RuleIndex = 1;
After the rollback scripts are executed, run LST ABLMSG. If no query result is returned, the
debugging messages are successfully removed.
