CN101998463B

CN101998463B - Method and system for MDT (Minimization of Drive Tests)

Info

Publication number: CN101998463B
Application number: CN 200910091155
Authority: CN
Inventors: 杨晓东; 赵瑾波; 刘洋; 董书霞
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2009-08-11
Filing date: 2009-08-11
Publication date: 2013-04-24
Anticipated expiration: 2029-08-11
Also published as: CN101998463A

Abstract

The invention discloses a method for MDT (Minimization of Drive Tests), comprising the following steps that: UE (User Equipment) receives indication information for starting the MDT from a network entity; the UE measures and records measuring parameters associated with the MDT, and/or records MDT associated events, wherein the recorded contents are taken as a measuring log; and the UE reports the recorded measuring log to the network entity. The invention further discloses a system for MDT. The MDT scheme provided by the invention provides a clear MDT start triggering mechanism. Based on above invention design, the embodiment of the invention provides various selectable schemes, thus operators can select the schemes to use according to different requirements and network stages.

Description

Method and system for minimization of drive tests

Technical Field

The present invention relates to the field of mobile communications technologies, and in particular, to a minimization of drive tests method and system.

Background

In the current network optimization of the mobile communication system, a drive test mode is usually adopted to check whether the coverage quality of the network and the system performance meet the expected design requirements, namely, professional network optimization personnel drive a measuring vehicle to randomly walk, and a measuring terminal records events and measurement quantities in the walking process and provides the events and the measurement quantities for operators to use for network optimization decisions. The drive tests are all completed manually, a large amount of manpower and time are required to be invested, and a large burden is brought to the network construction and maintenance cost of an operator. On the other hand, the drive test is usually only performed outdoors, but not performed indoors and in some private areas, and the network optimization in these places is difficult to be completed through the drive test.

In order to reduce the operation and maintenance costs of the network, it is desirable to adopt some methods to reduce the labor of the manual drive test. On the other hand, it is also desirable to obtain radio measurement information of an area that cannot be reached by the normal Drive test, and based on this, a study item on Minimization of Drive Tests (MDT) of the Long Term Evolution project of the Universal Mobile Telecommunications System (Long Term Evolution-Universal Mobile Telecommunications System, LTE-UMTS) has been established in the 3GPP RAN 2.

One prior art MDT system is shown in fig. 1. The MDT system includes a network entity 101 and a User Equipment (UE)102, where the network entity 101 includes an operation and maintenance policy and requirement enhancement module (OAM policy & requirement enhancement function)103 and a log storage module (log storage)104, and the UE102 includes a logging/reporting capability module (logging) 105, a measurement logging function module (measurement logging function)106 and a measurement reporting function module (measurement reporting function) 107.

The specific signaling flow for implementing MDT is shown in fig. 1, and includes the following steps:

step 1: the logging and reporting capabilities module 105 of the UE102 reports the UE logging and reporting capabilities to the network entity 101.

Step 2: the operation maintenance policy and demand enhancement module 103 of the network entity 101 performs log configuration of the UE according to the received UE log capability information, and sends the log configuration information to the UE 102.

And step 3: the operation maintenance strategy and demand enhancement module 103 performs UE report configuration according to the received UE report capability information, and sends the report configuration information to the UE 102.

And 4, step 4: the measurement logging function 106 of the UE102 configures the log according to the received log configuration information, and the measurement report function 107 configures the report related parameters according to the received report configuration information. The measurement recording function module 106 performs wireless measurement and records a measurement log, and sends the recorded measurement log to the measurement reporting function module 107, and the measurement reporting function module 107 reports the measurement log to the network entity 101 according to the configured reporting parameters. The log storage module 104 of the network entity 101 stores the received measurement log.

The MDT system and method flow in the prior art have the following drawbacks: the MDT initiation trigger mechanism is lacking. According to the existing minimization drive test process, the UE does not know when to report the capability information and starts the minimization drive test process; there is no way for the network to trigger this flow and thus no way for the operator to control MDT, which is undesirable for the operator.

Disclosure of Invention

In view of the above, the present invention provides a method and a system for minimization of drive tests, which enable the minimization of drive tests to include an explicit trigger mechanism.

The method for minimizing the drive test provided by the embodiment of the invention comprises the following steps:

user Equipment (UE) receives indication information for starting a Minimization of Drive Test (MDT) function from a network entity;

the UE measures and records MDT related measurement parameters and/or MDT related events, and the recorded content is used as a measurement log;

and the UE reports the recorded measurement log to a network entity.

The embodiment of the invention also provides a minimization of drive tests system, which comprises user equipment and a network entity, wherein the network entity comprises:

the MDT control module is used for sending indication information for starting the MDT function or indication information for closing the MDT function to the user equipment;

the log storage module is used for receiving and storing a measurement log reported by the user equipment;

the user equipment includes:

the system comprises a measurement recording function module, a network entity and a terminal, wherein the measurement recording function module is used for receiving indication information for starting an MDT function from the network entity, measuring and recording measurement parameters related to the MDT, and/or recording events related to the MDT, and the recorded contents are used as a measurement log; or receiving an indication message for ending the MDT function from the network entity, and stopping recording the operation of the measurement log;

and the measurement report function module is used for reporting the measurement log recorded by the measurement recording function module to a network entity.

It can be seen from the above technical solutions that the MDT method and system provided in the embodiments of the present invention provide a clear MDT start trigger mechanism. And based on the above inventive concept, the embodiments of the present invention provide various alternatives for operators to choose to use according to different requirements and different network phases. In addition, the existing implementation mode is relatively complex and occupies air interface resources, while the implementation scheme provided by the invention is relatively simplified, and the air interface resources are also saved.

Drawings

FIG. 1 is a block diagram of a prior art MDT system;

fig. 2 is a block diagram of an MDT system according to an embodiment of the present invention;

fig. 3 is a block diagram of an MDT system according to a second embodiment of the present invention;

fig. 4 is a block diagram of an MDT system according to a third embodiment of the present invention;

fig. 5 is a block diagram of an MDT system according to a fourth embodiment of the present invention;

fig. 6 is a block diagram of an MDT system according to a fifth embodiment of the present invention;

fig. 7 is a block diagram of an MDT system according to a sixth embodiment of the present invention;

fig. 8 is a block diagram of an MDT system according to a seventh embodiment of the present invention.

Detailed Description

A method and system for minimization of drive tests are provided, which enable the minimization of drive tests to include an explicit trigger mechanism. Based on the inventive thought, various implementation schemes are provided for the actual operation condition of the communication system, and operators can select and use the communication system according to different requirements and different network phases.

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings.

Example one proposed MDT system is shown in fig. 2. In order to solve the problem that the network side and the operator have no way to trigger the MDT process, the MDT system is improved based on the prior art as follows:

network entity 101 adds an MDT control module 108. The MDT control module 108 is configured to implement a control function for MDT, such as triggering an MDT procedure, including starting or closing the MDT; and other related MDT control procedures, such as setting MDT for a specific area and/or a specific time period (e.g., when network load is low), etc.;

before reporting UE log and report capability information of the existing MDT realization process, related steps for triggering MDT are added. The method specifically comprises the following steps: when the operator wishes to implement control of MDT, the MDT control module 108 of the network entity 101 sends an MDT control message to the UE 102; after receiving the MDT control message, the UE102 reports the capability information related to MDT to the network entity 101, so as to perform a subsequent MDT procedure, as shown in fig. 2. The related capabilities include logging and reporting capabilities. The reception of the MDT control message by the UE102 corresponds to a trigger condition for MDT.

The MDT control module 103 of the network entity 101 may further include:

a selecting unit, configured to select the UE as the UE receiving the indication information for turning on the MDT function according to one or any combination of the following principles:

the principle of selecting a UE is determined for different user requirements and/or measurement parameters. For example, for the broadcast channel failure, it is configured how many times the accumulated failure times reach a specific value to record and report the measurement log; or starting to record and report a measurement log when the pilot frequency power is reduced to a preset threshold value; or reporting a measurement log at a specific time of day, etc.

Selecting all or part of UEs from UEs close to the cell edge or a coverage hole area;

selecting all or part of the UEs from the UEs with random access failure or conflict;

selecting a UE for friendly users or trial use;

selecting all or part of the UEs from the UEs in the network index deterioration area or the cell in which the network congestion occurs;

a UE installed on a vehicle or other vehicle is selected.

The flow for implementing MDT based on the MDT system shown in fig. 2 includes the following steps:

step 201: the operator can set which terminal and user to select MDT through network management, and set at what time to start MDT or configure to start MDT, and then send the MDT configuration information to the selected UE through the network entity. The MDT configuration information may be sent to the UE through broadcast signaling or proprietary signaling. If the signaling is broadcast signaling, the broadcast signaling carries the identity of the UE. Therefore, the UE can judge whether the signaling is sent to the UE according to whether the UE identification carried in the broadcast signaling is the same as the self identification.

The network entity may select a suitable UE for MDT according to one or any combination of the following principles:

(1) determining a principle of selecting UE for different use case requirements and measurement parameters, and reporting some measurements and LOG (LOG-assisted network) and Minimization of Drive Tests (MDT) and network optimization by the UE;

(2) UE reporting that handover and coverage optimization related measurement (RSCP/RSRQ) is close to the edge of a cell or a coverage hole is needed;

(3) all UEs or a part of them may be related to specific use cases (e.g. random access, handover parameter optimization), especially those UEs that have random access failure or collision;

(4) the general network quality index statistics can be selected and reported by friendly users, operators can give preference to some expenses, and the operators can also provide free service trial;

(5) for a network index deterioration area (such as a newly built network area), an operator can randomly extract a certain proportion of UE for tracking and measuring reporting requirements, and the proportion can be controlled by the operator; or a UE of a cell in which network congestion occurs;

(6) operators can request special user groups to report (with Global Positioning System (GPS) function, it is easy to cover large area, especially the area without fixed personnel, etc.). For example, since UEs in vehicles typically have GPS functionality, UEs installed in vehicles or other vehicles may be required to report. Preferably, the vehicle may be a vehicle providing public service or operation, such as a taxi, a sweeper, a bus, a traffic police vehicle or a patrol vehicle;

step 202: after receiving the MDT configuration information, the UE reports the related capability information supporting the MDT to the network entity. Such relevant capability information includes, but is not limited to, combinations of one or more of the following:

the terminal type of the UE (e.g. normal terminal, PDA, data card), etc.;

-a memory size;

-which measurement parameters or events can be logged;

positioning capabilities (whether positioning functionality is available, and which positioning means it supports, such as GPS, downlink Observed Time Difference Of Arrival (OTDOA), etc.);

step 203: after receiving the capability information of the UE, the network entity judges whether the MDT can be performed or not according to the capability information of the UE, and only executes the subsequent process for the user who can perform the MDT. For example, if the UE does not have the positioning function, because the UE cannot report the location information, the MDT is not meaningful, and therefore the MDT is not performed for the UE without the positioning function.

Step 204: the network entity sends the configuration information of the log report to the UE which can be MDT;

step 205: UE measures and records relevant measurement parameters or records relevant events according to the received configuration information of the log report, and the recorded content is used as a measurement log; and reporting the recorded measurement log to a network entity according to a mode configured by the configuration information of the log report.

The MDT system proposed in example two is shown in fig. 3. In this embodiment, the MDT functionality is integrated into the operation maintenance policy and requirements enhancement module 103, and the operation maintenance policy and requirements enhancement module 103 comprises an MDT control module 108.

The MDT flow based on the MDT system shown in fig. 3 is as follows:

step 301: when the UE102 performs Radio Resource Control (RRC) connection, the UE reports the related log and reporting capability information to the network entity 101.

Step 302: the MDT control module 108 of the network entity 101 determines to open MDT, and after the operation maintenance policy and requirement enhancement module 103 stores the capability reported by the UE, sends log configuration information carrying a signaling whether to open MDT to the UE 102.

Step 303: the operation maintenance strategy and demand enhancement module 103 performs UE report configuration according to the received UE report capability information, and sends the report configuration information to the UE 102.

Step 304: the measurement logging function 106 of the UE102 configures the log according to the received log configuration information, and the measurement report function 107 configures the report related parameters according to the received report configuration information. The measurement recording function module 106 performs wireless measurement and records a measurement log, and sends the recorded measurement log to the measurement reporting function module 107, and the measurement reporting function module 107 reports the measurement log to the network entity 101 according to the configured reporting parameters. The log storage module 104 of the network entity 101 stores the received measurement log.

The MDT system proposed in example three is shown in fig. 4. The network entity knows the MDT related capabilities of the UE and the measurement, logging, reporting mechanisms are configurable. This mode is applicable to some handsets customized by the operator. In this case, the UE MDT capability is known to the network side, so it is not necessary to report the UE capability. Two methods of the first embodiment can be adopted as to whether the MDT function is turned on. The embodiment can omit the logging and reporting capability module 105 at the UE side, and reduce the reporting capability process of the UE.

The MDT system of example four is shown in fig. 5. At the beginning of network deployment, aspects of network coverage are likely to be less than ideal. Conventionally, a lot of drive tests are performed to know the network coverage and adjust the relevant parameters. After the introduction of MDT, it is desirable to minimize the workload of manual drive tests. Since at this time, the operator is in a stage of not yet officially placing numbers or only slightly placing numbers, a certain amount of user terminals are generally customized by the operator and provided for friendly users or for general user trial use. The customized ue can record some information required for MDT and report the information to the network for network coverage optimization and optimization of other parameters (e.g. mobility-related parameter optimization).

Since the user terminals are customized by the operator, when the terminal is customized, requirements are made for a terminal manufacturer to write log configuration information (including a log recording mode, a log recording time, a log recording start time, and/or recording measurement parameters or events and the like) and/or report configuration information (including a recorded log reporting mode, wherein the recorded log reporting mode includes periodic reporting, absolute time based and/or terminal cache and the like) of a UE log required for performing MDT into the terminal. When an operator customizes a terminal, the operator often customizes a plurality of terminals with different capabilities, such as a common mobile phone, a PDA, a data card, and the like, log capability and storage capability of each terminal for MDT are generally different, and the operator can set log configuration information and/or report configuration information corresponding to the terminal capability according to the difference of the above capabilities of each terminal and write the log configuration information and/or report configuration information into the terminal.

Preferably, the scheme of the embodiment is generally applied to the initial stage of network deployment. In this application scenario, the network entity knows the UE MDT capability; the configuration mechanism of the log and report does not require the network to configure over the air interface. Configuration information about MDT, such as turning on and off the MDT, can be obtained in two ways:

mode 1: sending, by a network entity, to a UE over an air interface;

mode 2: and when the operator customizes the terminal, writing the MDT configuration information into the terminal.

For the mode 2, the MDT is started as long as the default terminal is connected to the network, and the MDT is closed when the default terminal is powered off; as for the mode 1, the operator may start the log and the log report according to the log configuration mode and the report configuration mode written in the terminal when customizing the terminal when the MDT needs to be performed, and close the log and the log report when the MDT is not desired to be performed.

In this case, the log recording criteria and the report reporting criteria of the UE can be completely agreed in advance, so that a large number of signaling flows can be saved, and corresponding air interface resources can be saved, and an operator is not required to configure a log configuration mode and a report configuration mode through a network, thereby providing a convenient MDT mode in an application scenario where a large number of customized terminals are used at the beginning of network deployment.

The MDT system of the fifth embodiment is shown in fig. 6, and an MDT flow implemented based on the MDT system includes the following steps:

step 401: the operator can select which terminals and which users thereof to perform MDT through network management setting, and the network entity sends UE capability query information to the selected users to query the capability information related to the MDT. The UE capability query information may be transmitted through broadcast signaling or proprietary signaling.

Step 402: after receiving the MDT configuration information, the UE reports the MDT related capability to the network entity, where the related capability includes one or more of the following combinations, but is not limited to the following information:

the terminal type of the UE (e.g. normal terminal, PDA, data card), etc.;

-a memory size;

-which measurement parameters and/or events can be recorded;

positioning capabilities (whether it has positioning functionality, and which positioning means it supports, such as GPS, OTDOA, etc.);

to conserve air interface resources, the above capabilities of the UE may be located in several levels, each level corresponding to a level indicator code, such as:

level indicator code 0 corresponds to MDT capability level 1;

level indicator 1 corresponds to MDT capability level 2;

level indicator 2 corresponds to MDT capability level 3;

the UE reports the MDT-supporting capability to the network entity, and actually, the UE sends a level indicator corresponding to its own capability level to the network entity over an air interface.

Step 403: after receiving the capability information of the UE, the network entity judges whether the MDT can be performed or not according to the capability information of the UE, and only executes the subsequent process for the user who can perform the MDT. For example, if the UE does not have the positioning function, because the UE cannot report the location information, the MDT is not meaningful, and therefore the MDT is not performed for the UE without the positioning function.

Step 404: a network entity sends MDT configuration information to UE which judges that MDT can be carried out, wherein the MDT configuration information comprises log configuration information and log report configuration information;

in implementation, to save air interface resources, MDT configuration information may be defined as several sets, each set corresponding to a configuration indicator code, for example:

the configuration indication code 0 corresponds to an MDT configuration set 1;

the configuration indication code 1 corresponds to an MDT configuration set 2;

the configuration indication code 2 corresponds to an MDT configuration set 3;

the network entity sends MDT configuration information to the UE as follows: and the network entity selects a corresponding MDT configuration set aiming at the UE and sends a configuration indication code corresponding to the selected MDT configuration set to the UE.

Step 404: and the UE inquires a corresponding MDT configuration set according to the received configuration indication code, records related measurement parameters or events according to a mode set by the MDT configuration set, takes the recorded content as a measurement log, and reports the measurement log according to a mode specified by the MDT configuration set.

The MDT system of the sixth embodiment is shown in fig. 7, and an MDT flow implemented based on the MDT system includes the following steps:

step 501: before the customized terminal enters the network, an operator and/or a UE manufacturer writes configuration information (log configuration information and log report configuration information) of MDT into the UE;

step 502: the UE executes MDT according to the configuration mode of MDT, that is, performs log of related measurement parameters or events according to the mode set by the configuration information of log, and reports the log according to the mode configured by the configuration information reported by log.

The MDT system of the seventh embodiment is shown in fig. 8, and an MDT flow implemented based on the system includes the following steps:

step 601: before the customized terminal enters the network, an operator and/or a UE manufacturer writes configuration information (configuration information of a log and configuration information of a log report) of the MDT into the UE;

step 602: before a user enters a network using an MDT terminal, a network entity is informed of configuration information of MDT (configuration information of log and/or configuration information reported by log). The operator inputs capability information of the user for MDT and the terminal used by the user, configuration information of MDT (configuration information of log and/or configuration information reported by log), etc. into the network as needed so that the network can also know the configuration information related to MDT.

Step 603: UE executes MDT according to the configuration mode of MDT, namely records related measurement parameters or events according to the mode set by the log configuration information, and reports the measurement parameters or events according to the mode configured by the configuration information of the log report;

example eight:

at the initial stage of network deployment, performing MDT configuration (including log configuration and/or log report configuration) on terminals used by friendly users or trial users in a manner of the fifth embodiment or the sixth embodiment; when the trial period or free use period of the friendly user and/or trial user is over, the friendly user or trial user is converted into a general toll user, the configuration mode in the first embodiment or the fourth embodiment may be used for configuration, at this time, the network is generally relatively stable, and generally does not need to be frequently optimized in a wide range, at this time, the operator may reconfigure the MDT for these users according to needs, such as selecting to close the MDT for these users or some of them, or modifying part of parameters in the configuration of the log and/or the configuration of the log report, and the like.

According to the embodiments provided above, the minimization of drive test system provided by the present invention includes a user equipment and a network entity, where the network entity includes:

the MDT control module is used for sending indication information for starting the MDT function or indication information for closing the MDT function to the user equipment; the indication information for turning on the MDT function or the indication information for turning off the MDT function is transmitted through a broadcast signaling or a proprietary signaling.

the user equipment includes:

The MDT control module of the network entity further comprises:

selecting corresponding UE according to actual user requirements and/or measurement parameters;

selecting a UE for friendly users or trial use;

a UE installed on a vehicle or other vehicle is selected.

Preferably, the measurement recording function module of the user equipment further includes a log configuration unit, configured to store log configuration information;

the measurement recording function module measures and records the measurement parameters related to the MDT according to the log configuration information stored in the log configuration unit and/or records the events related to the MDT;

and/or the presence of a gas in the gas,

the measurement report function module further comprises a report configuration unit for storing report configuration information; and the measurement report function module reports the measurement log recorded by the measurement recording function module to a network entity according to the report configuration information stored in the report configuration unit.

Preferably, the network entity further comprises:

the operation maintenance strategy and demand enhancement module is used for generating and sending log configuration information and/or report configuration information to the user equipment;

the log configuration unit in the user equipment is used for receiving and storing log configuration information from the network entity; the report configuration unit is used for receiving and storing report configuration information from a network entity.

The log configuration information includes:

the manner in which the log is logged, the time at which the log was logged, the time at which logging began, and/or which measurement parameters or events were logged.

The report configuration information comprises a mode of reporting the recorded log; the mode of reporting the recorded log comprises periodic reporting, absolute time based and/or terminal cache based.

The operation maintenance policy and demand enhancement module further comprises:

the system comprises a configuration indicating unit, a configuration identification code generating unit and a configuration identification code generating unit, wherein the configuration indicating unit is used for storing a preset log configuration set and/or report configuration set and a configuration identification code corresponding to the log configuration set and/or report configuration set;

and the operation maintenance strategy and demand enhancement module inquires the configuration indication unit according to the generated log configuration information and/or report configuration information, finds the corresponding configuration identification code and sends the configuration identification code to the user equipment.

In some embodiments, the MDT control module may be a sub-module in an operation and maintenance strategy and demand enhancement module.

Preferably, the operation maintenance policy and demand enhancement module of the network entity is further configured to send a message inquiring about log capability and/or reporting capability to the user equipment;

the user equipment further comprises:

and the log recording and reporting capability module is used for receiving the message of inquiring the log capability and/or the reporting capability from the network entity and reporting the log capability and/or the reporting capability information of the log recording and reporting capability module to the network entity.

Preferably, the user equipment further comprises:

and the log recording and reporting capability module is used for reporting the log capability and/or the reporting capability information to the network entity when the user equipment performs the radio resource control connection.

The logging and reporting capabilities module may further comprise:

a capability level indication unit, configured to store a preset MDT capability level and a level indication code corresponding to the MDT capability level;

the log recording and reporting capability module is used for inquiring the capability level indicating unit according to the log capability and/or reporting capability information of the log recording and reporting capability module to obtain a corresponding level indicating code, and sending the level indicating code to a network entity.

The MDT method and the MDT system provided by the embodiment of the invention provide a clear MDT starting trigger mechanism. And based on the above inventive concept, the embodiments of the present invention provide various alternatives for operators to choose to use according to different requirements and different network phases. In addition, the existing implementation mode is relatively complex and occupies air interface resources, while the implementation scheme provided by the invention is relatively simplified, and the air interface resources are also saved.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.

Claims

1. A minimization of drive tests method, characterized by, comprising the steps of:

and the UE reports the recorded measurement log to a network entity.

2. The method of claim 1, wherein after the step of reporting the recorded measurement log to a network entity by the UE, the method further comprises:

and the UE receives indication information for closing the MDT function from the network entity and stops recording the measurement log.

3. The method according to claim 1 or 2, wherein the indication information for turning on the MDT function or the indication information for turning off the MDT function from the network entity is sent through broadcast signaling or proprietary signaling.

4. The method of claim 1, wherein before the UE receives the indication information for turning on the MDT function from the network entity, the method further comprises the following steps:

the network entity selects the UE as the UE for receiving the indication information of starting the MDT function according to one or any combination of the following principles:

selecting a UE for friendly users or trial use;

a UE installed on a vehicle or other vehicle is selected.

5. The method of claim 1, wherein the step of the UE measuring and logging MDT-related measurement parameters and/or logging MDT-related events is preceded by the step of:

the UE receives log configuration information and/or report configuration information from a network entity.

6. The method of claim 5, wherein the log configuration information comprises:

7. The method of claim 5, wherein the reporting configuration information includes a manner of reporting the logged log; the mode of reporting the recorded log comprises periodic reporting, absolute time based and/or terminal cache based.

8. The method according to claim 5, wherein the log configuration information and/or the report configuration information from the network entity is a configuration indicator code corresponding to a predefined MDT configuration set.

9. The method according to any of claims 5 to 8, wherein before the UE receives the log configuration information and/or the report configuration information from the network entity, further comprising:

the UE receives a message of inquiring log capability and/or reporting capability from a network entity and reports the log capability and/or reporting capability information of the UE to the network entity; or,

and when the UE performs the radio resource control connection, reporting the log capability and/or the report capability information to a network entity.

10. The method of claim 9, wherein the log capability and/or report capability information reported by the UE to the network entity is a level indicator code corresponding to a predefined MDT capability level.

11. The method of claim 10, wherein the MDT capability level corresponds to a capability set consisting of a terminal type, a memory size, a recordable measurement parameter and/or event, and/or a positioning capability of the UE.

12. The method according to claim 1, wherein the UE measures and logs MDT related measurement parameters, and/or logs MDT related events as:

and the UE measures and records the measurement parameters related to the MDT according to the log configuration information which is pre-configured in the local area, and/or records the events related to the MDT.

13. The method of claim 1, wherein the reporting, by the UE, the recorded measurement log to a network entity is: and the UE reports the recorded measurement log to a network entity according to the configuration information of the log report which is pre-configured in the local.

14. The method according to claim 12 or 13, wherein the step of the UE measuring and logging MDT related measurement parameters and/or logging MDT related events is preceded by the further step of: and the UE reports the log configuration information which is pre-configured in the local and/or the configuration information of the log report to the network entity.

15. A minimization of drive tests system comprising a user equipment and a network entity, wherein the network entity comprises:

the user equipment includes:

16. The system of claim 15, wherein the indication information for turning on the MDT function or the indication information for turning off the MDT function is sent through broadcast signaling or dedicated signaling.

17. The system of claim 15, wherein the MDT control module of the network entity further comprises:

selecting a UE for friendly users or trial use;

a UE installed on a vehicle or other vehicle is selected.

18. The system of claim 15,

the measurement recording function module of the user equipment further comprises a log configuration unit used for storing log configuration information;

and/or the presence of a gas in the gas,

19. The system of claim 18, wherein the network entity further comprises:

the log configuration unit is used for receiving and storing log configuration information from a network entity;

the report configuration unit is used for receiving and storing report configuration information from a network entity.

20. The system of claim 18, wherein the log configuration information comprises:

21. The system of claim 18, wherein the reporting configuration information includes a manner of reporting the logged records; the mode of reporting the recorded log comprises periodic reporting, absolute time based and/or terminal cache based.

22. The system of claim 19, wherein the operation maintenance policy and demand enhancement module further comprises:

23. The system of claim 19, wherein the MDT control module is a sub-module of an operation and maintenance strategy and demand enhancement module.

24. The system according to claim 19, 22 or 23, wherein the operation maintenance policy and requirements enhancement module of the network entity is further configured to send a message inquiring about log capabilities and/or reporting capabilities to the user equipment;

the user equipment further comprises:

25. The system according to any one of claims 16 to 23, wherein the user equipment further comprises:

26. The system of claim 24, wherein the logging and reporting capability module further comprises: