Thanks Thanks:  3
Showing results 1 to 3 of 3

Thread: Ask_How to Get MDT (Minimization of Drive Test) Data

  1. #1
    Member Reputation: 80
    Join Date
    2010-01-23
    Posts
    31


    Default Ask_How to Get MDT (Minimization of Drive Test) Data

    Hi Nokia Expert.


    I just Activated MDT (Minimization of Drive Test) Feature on eNodeB..

    How to get MDT Log?

    Thanks in Advance

  2. Thanks radio_network thanked for this post
  3. # ADS
    Circuit advertisement
    Join Date
    Always
    Posts
    Many
     

  4. #2
    Senior Member Reputation: 499
    Join Date
    2019-04-04
    Location
    War
    Posts
    513


    Default Re: Ask_How to Get MDT (Minimization of Drive Test) Data

    Hello, can you told more about this feature, what it make?

  5. #3
    Member Reputation: 80
    Join Date
    2010-01-23
    Posts
    31


    3 out of 3 members found this post helpful.

    Default Re: Ask_How to Get MDT (Minimization of Drive Test) Data

    Quote Originally Posted by macro View Post
    Hello, can you told more about this feature, what it make?
    LTE953: MDT (Minimization of Drive Test)

    Introduction to the feature

    This feature is introduced as an alternative for expensive drive tests performed during network deployment and optimization. The solution focuses on coverage optimization in the intra-frequency LTE network.

    End-user benefits

    This feature does not affect the end-user experience.

    Operator benefits

    This feature provides the following benefits to the operator:
    • A simple method for analyzing the network behavior in a certain area for coverage optimization purposes
    • Automated collection of trace data together with the UE measurements in the form of preconfigured profiles
    • OPEX and CAPEX savings as a result of reducing resources needed to evaluate the service and network performance (reduction of expensive drive tests)

    Functional description
    The feature offers a predefined set of MDT profiles available at the NetAct TraceViewer application. The profiles were designed to cover the following use cases:
    • detection of coverage problems in the neighbor cell
    • detection of coverage problems in the traced cell
    • monitoring the coverage quality of the traced cell
    One predefined profile covers both detection use cases. The second profile covers the monitoring use case. For each use case, there is a set of RRC, S1AP, and X2AP protocol messages that need to be collected for further analysis. The solution is based on data that is collected using the following features:


     LTE433: Cell Trace
     LTE644: Configurable cell trace content
     LTE570: Periodic UE Measurements

    By selecting an MDT profile, the corresponding configuration of the trace feature (together with the additional features) and the UE measurements is done for the selected area. The monitoring use case is based on periodic UE measurements. Some modifications to LTE570: Periodic UE Measurements feature configuration are introduced (the reportAmount and reportInterval parameter value ranges are extended) to collect either more measurements per UE with a longer interval or less measurements with a shorter interval. As the UE measurement requests might cause quite a big load in the network, it is not recommended to apply it in the whole network at the same time. The collected data is available in the NetAct TraceViewer or a 3rd party protocol analyzer.

    The LTE953: MDT feature is active when the actMDTCellTrace parameter value is set to true. If the actMDTCellTrace parameter value is set to false during an active trace session, all the MDT trace sessions will be stopped and MTRACE objects are not deleted. In this case, the TraceViewer might not show the correct status of the trace session that has been stopped. Therefore, it is recommended to delete first the MTRACE objects before setting the actMDTCellTrace parameter value to false.

    System impact

    Interdependencies between features

    This feature is based on the following features:
    LTE433: Cell Trace
    LTE459: Timing Advance Evaluation
    LTE644: Configurable cell trace content
    LTE162: Cell Trace with IMSI
    LTE570: Periodic UE Measurements


    The LTE953: MDT feature replaces LTE570: Periodic UE Measurements, so if the LTE953 is deployed in the network, the LTE570 is not available. The activation of periodic UE measurements is done together with the activation of cell trace with the MDT profile.



    Impact on interfaces

    This feature has no impact on interfaces.

    Impact on network and network element management tools

    The MDT profiles can be selected using the NetAct TraceViewer application. The user selects the profile during the trace session creation. The profile includes:
     the selection of protocol messages to be traced
     the configuration of periodic intra-frequency UE measurements (in the monitoring use case)

    Impact on system performance and capacity

    The impact on system performance and capacity is comparable to the impact caused by LTE570: Periodic UE Measurements and LTE433: Cell Trace.

  6. Thanks slava121, mbo thanked for this post

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •