Minimization of drive test reporting and logging

Abstract

Example embodiments of the present disclosure relate to minimization of drive test (MDT) logging and reporting. According to example embodiments, a user equipment (UE) may be provided. The UE may be configured to receive a radio resource control (RRC) message comprising one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receive a measurement report comprising at least one of signal strength, data volume, and network congestion; and determine, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.

Description

MINIMIZATION OF DRIVE TEST REPORTING AND LOGGINGTECHNICAL FIELD

[0001] The present disclosure relates to minimization of drive test (MDT) reporting and logging.BACKGROUND

[0002] The information disclosed in this background section is only for the enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0003] In the related art, minimization of drive test (MDT) is a method of collecting network performance data from a user equipment (UE) in a telecommunications network, in order to optimize network performance and reduce the need of a standard drive test (e.g., testing network strength by driving around in a vehicle). This may be provided, for example, in a standard such as 3GPP. It may be implemented in telecommunications systems such as LTE and 5G.

[0004] The UE may collect measurements such as network strength, network quality, and location information and log them. In immediate MDT reporting, the UE may report the measurements to the network in real-time when connected. In logged MDT reporting, the UE may record the measurements, and send them to the network later when in an inactive state.SUMMARY

[0005] In the related art, MDT lacks flexibility to switch between different reporting methods based on real-time network conditions. Immediate MDT supports real-time datacollection, but does not support data logging. Logged MDT supports data logging, but is limited to non-connected states.

[0006] Accordingly, there is a need for a more adaptive MDT reporting method which can dynamically switch between reporting methods in order to combine the advantages of both immediate and logged MDT.

[0007] Example embodiments of the present disclosure provide a system, method, and device for minimization of drive test (MDT) reporting and logging. According to example embodiments, a user equipment (UE) may be provided. The UE may be configured to receive a radio resource control (RRC) message comprising one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receive a measurement report comprising at least one of signal strength, data volume, and network congestion; and determine, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.

[0008] Based on the above example embodiments, example effects which may be achieved by embodiments of the present disclosure may include a flexible framework for dynamic switching between different reporting and logging methods for MDT based on real-time network conditions and UE capabilities.

[0009] According to example embodiments, method may be provided, the method including: receiving, by a user equipment (UE), a radio resource control (RRC) message including one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receiving, by the UE, a measurement report including at least one of signal strength, data volume, and network congestion; and determining, by the UE,based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.

[0010] According to example embodiments, a non-transitory computer-readable recording medium having recorded thereon instructions executable to perform a method may be provided, the method including: receiving, by a user equipment (UE), a radio resource control (RRC) message including one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receiving, by the UE, a measurement report including at least one of signal strength, data volume, and network congestion; and determining, by the UE, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.

[0011] Additional aspects will be set forth in part in the description that follows and, in part, will be apparent from the description, or may be realized by practice of the presented embodiments of the disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0013] FIG. 1 illustrates an example callflow diagram for configuring a UE for adaptive MDT, according to one or more example embodiments;

[0014] FIG. 2 illustrates an example callflow diagram for configuring a UE for hybrid MDT, according to one or more example embodiments;

[0015] FIG. 3 illustrates a block diagram of an example method for switching between reporting methods for MDT, according to one or more example embodiments;

[0016] FIG. 4 illustrates a block diagram of an example method for switching between immediate, logged, and hybrid MDT, according to one or more example embodiments;

[0017] FIG. 5 illustrates a block diagram of an example device for implementing one or more example embodiments; and

[0018] FIG. 6 illustrates a block diagram of an example environment for implementing one or more example embodiments.DETAILED DESCRIPTION

[0019] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to one of the various embodiments. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0020] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limited to the described implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It isunderstood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0021] Even though particular combinations of features are disclosed in the claims and / or in the specification, these combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the claim set.

[0022] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B]”, “[A] and / or [B]”, or “at least one of [A] or [B]”, are to be understood as including only A, only B, or both A and B.

[0023] It shall be noted that, descriptions of example embodiments of the present disclosure may include terms and names defined in one or more standard organizations, such as the 3rd Generation Partnership Project (3GPP) standard organization, the European Telecommunications Standards Institute (ETSI) standard organization, the Open Radio Access Network (0-RAN) Alliance standard organization, and the like.

[0024] According to example embodiments, an adaptive MDT reporting mechanism may be implemented. Dynamic switching allows for switching between periodic, event-based, andnetwork-request based reporting based on real-time network conditions. This may allow for the most efficient reporting method at a given time. A decision engine may be included within the user equipment (UE) which allows for continuous monitoring of network conditions (e.g., signal strength, network load, UE mobility) and select the optimal reporting method based on predefined criteria and thresholds.

[0025] The criteria for switching may be set as thresholds for each different reporting method. For example, thresholds for signal strength, data volume, and network congestion levels may be included. As an example, periodic reporting may be used when there is stable conditions, and event-based reporting may be used when significant changes in signal strength or network events occur. Example embodiments may implement a feedback loop from the network to the UE to allow the network to request changes in the reporting method based on broader network insights and requirements.

[0026] According to example embodiments, a hybrid MDT system may also be implemented which combines functionality of immediate and logged MDT. Specifically, an algorithm may be used to decide when to log data locally, and when to report it immediately based on network requirements and UE capabilities. For example, the UE can log data during high mobility scenarios, and report it once stable connectivity is achieved. The UE may be able to log data during non-connected states and immediately report critical data during connected states. This may ensure that no data is lost during transitions between connectivity states and provide a continuous data stream. Protocols for transitioning between logged and immediate reporting may also be defined to ensure seamless integration and minimal disruption to ongoing data collection.

[0027] Based on the above example embodiments, example effects which may be achieved by embodiments of the present disclosure may include a flexible framework for dynamic switchingbetween different reporting and logging methods for MDT based on real-time network conditions and UE capabilities.

[0028] It is contemplated that features, advantages, and significances of example embodiments described hereinabove are merely a portion of the present disclosure, and are not intended to be exhaustive or to limit the scope of the present disclosure. Further descriptions of the features, components, configuration, operations, and implementations of the example embodiments of the present disclosure are provided in the following.

[0029] FIG. 1 illustrates an example callflow diagram for configuring a UE for adaptive MDT, according to one or more example embodiments.

[0030] The RRC message may be sent from base station 100 to user equipment (UE) 110. Base station 100 may be, for example, a node such as gNodeB or eNodeB (for 5G and LTE respectively).

[0031] At step 1, base station 100 may send an RRC reconfiguration message including MDT reporting parameters to UE 110. Specifically, the adaptive MDT parameters may include a possible reporting method (chosen from a list of periodic, event-based, and network-request), along with decision criteria. The decision criteria may include, for example, a signal strength threshold (e.g., a percentage from 0 to 100), a data volume threshold (e.g., data volume in units of bytes), and a network congestion level (for example, preset based on low, medium, or high values).

[0032] At step 2, UE 110 may receive a measurement report. The measurement report may include an identifier, a result, as well as the relevant parameters corresponding to the decision criteria in the RRC reconfiguration message (e.g., the signal strength, data volume threshold, and network congestion level).

[0033] At step 3, UE 110 may switch the reporting method based on comparing the MDT reporting parameters to the measurement report. As an example, if signal strength is strong and data volume is low, then periodic reporting may be selected since the UE may consider that the conditions are stable by comparing the values from the measurement report to the threshold values defined from the RRC reconfiguration message.

[0034] As another example, a feedback loop may be implemented from the network to the UE for requesting changes in the reporting method. In this case, if the network congestion is high, the reporting method may be event-based. It should be appreciated that the logic / algorithm for selecting the reporting method may be implemented by a person skilled in the art based on the specific deployment scenario and network architecture.

[0035] At step 4, an MDT report may be sent using the updated MDT reporting method from step 3 by UE 110 to base station 100.

[0036] FIG. 2 illustrates an example callflow diagram for configuring a UE for hybrid MDT, according to one or more example embodiments.

[0037] The RRC message may be sent from base station 100 to UE 110, similar to FIG. 1.

[0038] At step 1, base station 100 may send an RRC reconfiguration message including hybrid MDT parameters. The hybrid MDT parameters may include an MDT mode as a list of possible values (immediate, logged, or hybrid), as well as transition criteria. The transition criteria may include a signal strength threshold (0 to 100), a mobility status (stationary, low speed, high speed), and a connectivity state (e.g., connected and disconnected).

[0039] At step 2, UE 110 may receive a measurement report. The measurement report may include an identifier, a result, as well as the relevant parameters corresponding to the transitioncriteria in the RRC reconfiguration message (e.g., the signal strength, mobility status, and connectivity state).

[0040] At step 3, UE 110 may switch between MDT mode based on comparing the measurement report to the hybrid MDT parameters. In a “logged” mode, UE 110 may be configured to log the data and send it later when there is connectivity. In a “immediate” mode, UE 110 may be configured to immediately send the data in MDT reporting. In a “hybrid” mode, UE may be able to readily switch between the “logged” state and the “immediate” state. The logic for deciding whether to switch the MDT mode may be implemented using an algorithm based on the hybrid MDT parameters and transition criteria.

[0041] At step 4a, if it was determined that MDT mode should be in logged MDT mode, data is logged locally by UE 110 and sent later to base station 100 when there is connectivity.

[0042] As an alternative to step 4a, in step 4b, if it was determined that MDT mode should be in immediate MDT mode, data is immediately sent as an MDT report to base station 100 by UE 110. In this case, if the immediate report fails, the UE should log the data and retry transmission once connectivity is restored.

[0043] FIG. 3 illustrates a block diagram of an example method 300 for switching between reporting methods for MDT, according to one or more example embodiments.

[0044] At operation S301, the UE receives an RRC message including MDT reporting parameters. The MDT reporting parameters may include a list of MDT reporting methods and decision criteria. The list of MDT reporting methods may include periodic reporting, event based reporting, and network request based reporting. The decision criteria may include signal strength threshold, data volume threshold, and network congestion level threshold values.

[0045] At operation S302, the UE receives a measurement report. The measurement report may include at least one of signal strength, data volume, and network congestion.

[0046] At operation S303, the UE determines the MDT reporting should be switched based on comparing parameters to the measurement report. Specifically, this may be made based on comparing the measurement values received in the measurement report to the threshold values in the decision criteria.

[0047] FIG. 4 illustrates a block diagram of an example method 400 for switching between immediate, logged, and hybrid MDT, according to one or more example embodiments.

[0048] At operation S401, the UE receives an RRC message including hybrid MDT parameters. The hybrid MDT parameters may include an MDT mode as a list of possible values (immediate, logged, or hybrid), as well as transition criteria. The transition criteria may include a signal strength threshold (0 to 100), a mobility status (stationary, low speed, high speed), and a connectivity state (e.g., connected and disconnected).

[0049] At operation S402, the UE receives a measurement report. The measurement report may further include a mobility status and connectivity state, which may be similar to the measurement report received in operation S302.

[0050] At operation S403, the UE determines the MDT mode should be switched based on comparing hybrid MDT parameters to the measurement report. Specifically, this may be made based on comparing the measurement values received in the measurement report to the threshold values in the transition criteria. It should be appreciated that in the case MDT reporting fails for immediate MDT, the UE may be configured to switch to logged MDT and periodically reattempt transmission.

[0051] Based on the above example embodiments, example effects which may be achieved by embodiments of the present disclosure may include a flexible framework for dynamic switching between different reporting and logging methods for MDT based on real-time network conditions and UE capabilities.

[0052] FIG. 5 illustrates a block diagram of an example device 500 for implementing one or more example embodiments. As shown in FIG. 5, the device 500 includes processor 510, a memory 520, a storage component 530, an input component 540, an output component 550, a communication interface 560, and a bus 570.

[0053] The processor 510, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 510 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 510 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0054] Memory 520 includes a non-transitory computer readable medium. Memory 520 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 510. The memory 520 comprises machine-readable instructions which are executable by the processor 510. These machine-readable instructions when executed by the processor 510 cause the processor 510 to perform one or more method steps of an embodiment described above.

[0055] Storage component 530 stores information and / or software related to the operation and use of the device 500. For example, storage component 530 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0056] Input component 540 is configured to receive information, such as user input. For example, the input component 540 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 540 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0057] Output component 550 is configured to provide output information from the device 500. For example, the output component 550 may be, but not limited to, a display, a speaker, an instruction device to an external device, and / or one or more light-emitting diodes (LEDs).

[0058] Communication interface 560 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 560 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 500 and other devices. In other words, the standard of the communication interface 560 is not limited.

[0059] The bus 570 acts as an interconnect between the processor 510, the memory 520, the storage component 530, the input component 540, the output component 550, and the communication interface 560 of the device 500. The bus 570 may include a wired interconnection or a wireless interconnection.

[0060] The number and arrangement of components shown in FIG. 5 are provided as an example. In practice, device 500 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 5. Additionally, or alternatively, a set of components (e.g., one or more components) of device 500 may perform one or more functions described as being performed by another set of components of device 500. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 500 in communication with one another.

[0061] Example embodiments of the present disclosure may be implemented in any suitable type of environment. In the following, an example environment (in which the example embodiments may be implemented) is described.

[0062] FIG. 6 illustrates a block diagram of an example environment 600 for implementing in which systems and / or method, described herein, may be implemented. The implementation environment 600 includes a UE (User equipment) 610, a service environment 620, and a network 630. The service environment 620 include one or more sub-environments 621. To illustrate this, FIG. 6 shows, for convenience, examples of a 1st sub-environment 621-1, a 2nd sub-environment 621-2, and an N-th sub-environment 621-N (where N is any natural number).

[0063] The UE 610 is connected to the network 630, and the network 630 is connected to the service environment 620. The connections may be wired, wireless, or a combination of both wired and wireless. The UE 610 and the service environment 620 are connected via the network 630.

[0064] The UE 610 is a device that communicates with the service environment 620. The UE 610 receives information from the service environment 620 and / or sends information to the service environment 620. Also, the UE 610 may generate and / or store information to betransmited, as necessary. Also, the UE 610 may store and / or process information that is received, as necessary.

[0065] The example of FIG. 6 refers to the “UE”. However, it should be understood by those skilled in the art that general terms such as “user device,” “terminal,” “terminal device,” “communication device,” and “communication terminal” can be used interchangeably with the term “UE.”

[0066] For example, the UE 610 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smart phone, a radiotelephone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device.

[0067] The service environment 620 is an environment that communicates with the UE 610 to provide one or more services. The service environment 620 receives information from the UE 610 and / or sends information to the UE 610. Also, the service environment 620 may generate and / or store information to be transmitted, as necessary. Also, the service environment 620 may store and / or process information that is received, as necessary. For example, the service environment 620 may provide computing resources as one of the services. It should be noted that the service is not limited to being provided to the UE; it may also be provided to devices other than the UE. For example, based on communication from the UE, the service may perform processes such as anomaly detection or traffic analysis and notify the results to a predetermined destination.

[0068] The example FIG. 6 refers to the “service environment”. The term "service environment" is used to refer to the broader context within which services operate. For example, cloud environments, platforms, computing systems, network systems, and cloud systems generallyrepresent the environments in which services are conducted, and these are included within the "service environment." However, the "service environment" is not limited to these examples.Additionally, the specific types of environments within the "service environment" are not restricted. For instance, cloud environments and cloud systems can be categorized as private cloud, public cloud, hybrid cloud, or multi-cloud, all of which are included within the "service environment."

[0069] The one or more services provided by the service environment 620 is not specifically limited and can be adjusted according to the embodiments. For example, the services may include a service that provides information to the UE 610, a service that stores information from the UE 610, or a service that performs processing based on information from the UE 610 and returns the results of the processing.

[0070] In an embodiment, the Service Environments 620 may also provide computing resources as the service. The computing resources can be hardware resources and / or software resources. For example, applications, processors, memory, and storage can be included in the provided computing resources. Each computing resource can communicate with other computing resources via wired connections, wireless connections, or a combination of wired and wireless connections.

[0071] The provided computing resources can be actual resources (also referred to as physical resources) and / or virtual resources. Furthermore, means of virtualization for virtual resources can be selected as appropriate. That is, in this disclosure, the use of adjectives such as "Virtual" or "Virtualized" to describe names does not imply that they are virtualized by a specific means of virtualization. For example, “virtual machine” refers to software that operates like an actual computer, realized through means of virtualization, and it is not intended to exclude those realized by specific means of virtualization such as Hypervisors or Containers. Conversely, whenmeans of virtualization such as Hypervisors or containers are mentioned in this disclosure, it is merely cited as a general method of implementation. It should also be interpreted that embodiments implemented with other virtualization means are also disclosed. Also, the services may also be provided using resources virtualized by different means.

[0072] The service environment 620 includes one or more devices, such as servers and network devices, which provide services or perform processes. The placement of these devices within the service environment 620 can be determined as appropriate. Additionally, if the service environment 620 includes one or more sub-environments 621, the placement of devices can be determined based on predetermined policies for each sub-environment 621. For example, devices related to the first service may be placed in the 1st sub-environment 621-1, and devices related to the second service may be placed in the 2nd sub -environment 621-2. In another example, devices expected to have a higher load than a predetermined threshold may be placed in the 1st subenvironment 621-1, while devices expected to have a lower load than the predetermined threshold may be placed in the 2nd sub-environment 621-2. In this way, specific devices can be placed in specific sub -environments 621. Conversely, each sub-environment 621 can be specialized for a particular purpose.

[0073] In an embodiment, all processes executed in a single service may run within a single service environment, or in multiple service environments. Multiple processes executed in a single service could be provided by different service environments.

[0074] The network 630 is a network that exchanges information between the UE 610 and the service environment 620. The network 630 includes one or more wired and / or wireless networks.

[0075] For example, the network 630 may include a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, a non-terrestrial network (NTN), and / or a combination of these or other types of networks.

[0076] The network 630 can be a part of a network. For example, in a 5G network that includes a RAN, a transport network, and a core network, the network 630 can be at least one of the RAN, the transport network, or the core network. For example, the service environment 620 could be in the core network, in which case the network 630 could correspond to a network that is a combination of a RAN and a transport network and is part of the 5G network.

[0077] The number and arrangement of devices and networks shown in FIG. 6 are provided as an example. It should be understood that any changes that may be implemented by those skilled in the art, such as the addition or rearrangement of well-known devices or networks at the time of implementation, are included in this disclosure.Various Aspects of Embodiments

[0078] It is contemplated that the example embodiments described hereinabove with reference to FIG. 1 to FIG. 6 are merely examples of possible embodiments of the present disclosure, and are not intended to limit or restrict the scope of the present disclosure.

[0079] Specifically, the foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired frompractice of the implementations.

[0080] Some embodiments may relate to a device (e.g., node, etc.), a system, a method, and / or a computer-readable medium at any possible technical detail level of integration. Further, one or more of the above components described above may be implemented as instructions stored on a computer-readable medium and executable by at least one processor (and / or may include at least one processor). The computer-readable medium may include a computer-readable non- transitory storage medium (or media) having computer-readable program instructions thereon for causing a processor to carry out operations.

[0081] The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), electrically erasable programmable read-only memory (EEPROM), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through afiber-optic cable), or electrical signals transmitted through a wire.

[0082] Computer-readable program instructions described herein can be downloaded to respective computing / processing devices from a computer-readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computing / processing device.

[0083] Computer-readable program code / instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object-oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the "C" programming language or similar programming languages.

[0084] The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet ServiceProvider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer-readable program instructions by utilizing state information of the computer- readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.

[0085] These computer-readable program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer- readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function / act specified in the flowchart and / or block diagram block or blocks.

[0086] The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0087] The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). The method, computer system, and computer-readable medium may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustration, and combinations of blocks in the block diagrams and / or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

[0088] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limited to the implementations. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0089] In view of the above, various further respective aspects and features of embodiments of the present disclosure may be defined by the following items:Item [1]: A user equipment (UE) configured to: receive a radio resource control (RRC) message including one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receive a measurement report including at least one of signal strength, data volume, and network congestion; and determine, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.Item [2]: The UE according to Item [1], wherein the list of MDT reporting methods includes periodic reporting, event based reporting, and network request based reporting.Item [3]: The UE according to any one of Items [l]-[2], wherein the decision criteria includes a signal strength threshold, a data volume threshold, and a network congestion level threshold.Item [4]: The UE according to any one ofltems [l]-[3], wherein the RRC message further includes hybrid MDT parameters including a list of MDT modes and transition criteria, wherein the UE is further configured to: determine, based on comparing the hybrid MDT parameters to the measurement report, that an MDT mode of the UE should be switched to a different MDT mode.Item [5]: The UE according to Item [4], wherein the transition criteria includes a signal strength threshold, a mobility status, and a connectivity state.Item [6]: The UE according to Item [4], wherein the MDT mode includes immediate MDT, loggedMDT, and hybrid MDT which can readily switch between both immediate MDT and logged MDT.Item [7]: The UE according to Item [6], wherein if setting the logging frequency of the UE fails, the UE is configured to reattempt setting the logging frequency of the UE after a predetermined period of time.Item [8] : A method including: receiving, by a user equipment (UE), a radio resource control (RRC) message including one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receiving, by the UE, a measurement report including at least one of signal strength, data volume, and network congestion; and determining, by the UE, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.Item [9]: The method according to Item [8], wherein the list of MDT reporting methods includes periodic reporting, event based reporting, and network request based reporting.Item

[0010] : The method according to any one of Items [8]-[9], wherein the decision criteria includes a signal strength threshold, a data volume threshold, and a network congestion level threshold.Item

[0011] : The method according to any one of Items [8]-

[0010] , wherein the RRC message further includes hybrid MDT parameters including a list of MDT modes and transition criteria, wherein the method further includes determining, by the UE, based on comparing the hybrid MDT parameters to the measurement report, that an MDT mode of the UE should be switched to a different MDT mode.Item

[0012] : The method according to Item

[0011] , wherein the transition criteria includes a signal strength threshold, a mobility status, and a connectivity state.Item

[0013] : The method according to Item

[0011] , wherein the MDT mode includes immediate MDT, logged MDT, and hybrid MDT which can readily switch between both immediate MDT and logged MDT.Item

[0014] : The method according Item

[0013] , wherein if MDT reporting fails for immediate MDT, the UE is configured to switch to logged MDT and periodically reattempt transmission.Item

[0015] : A non-transitory computer-readable recording medium having recorded thereon instructions executable to perform a method including: receiving, by a user equipment (UE), a radio resource control (RRC) message including one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receiving, by the UE, a measurement report including at least one of signal strength, data volume, and network congestion; and determining, by the UE, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.Item

[0016] : The non-transitory computer-readable recording medium according to Item

[0015] , wherein the list of MDT reporting methods includes periodic reporting, event based reporting, and network request based reporting.Item

[0017] : The non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0016] , wherein the decision criteria includes a signal strength threshold, a data volume threshold, and a network congestion level threshold.Item

[0018] : The non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0017] , wherein the RRC message further includes hybrid MDT parameters including a list of MDT modes and transition criteria, wherein the method further includes determining, by the UE, based on comparing the hybrid MDT parameters to the measurement report, that an MDT mode of the UE should be switched to a different MDT mode.Item

[0019] : The non-transitory computer-readable recording medium according to Item

[0018] , wherein the transition criteria includes a signal strength threshold, a mobility status, and a connectivity state.Item

[0020] : The non-transitory computer-readable recording medium according to Item

[0018] , wherein the MDT mode includes immediate MDT, logged MDT, and hybrid MDT which can readily switch between both immediate MDT and logged MDT.

[0090] It will be apparent that within the scope of the appended clauses, the present disclosures may be practiced otherwise than as specifically described herein.

Claims

What is claimed is:

1. A user equipment (UE) configured to: receive a radio resource control (RRC) message comprising one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receive a measurement report comprising at least one of signal strength, data volume, and network congestion; and determine, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.

2. The UE as claimed in claim 1, wherein the list of MDT reporting methods comprises periodic reporting, event based reporting, and network request based reporting.

3. The UE as claimed in claim 1, wherein the decision criteria comprises a signal strength threshold, a data volume threshold, and a network congestion level threshold.

4. The UE as claimed in claim 1, wherein the RRC message further comprises hybrid MDT parameters including a list of MDT modes and transition criteria, wherein the UE is further configured to: determine, based on comparing the hybrid MDT parameters to the measurement report, that an MDT mode of the UE should be switched to a different MDT mode.

5. The UE as claimed in claim 4, wherein the transition criteria comprises a signal strength threshold, a mobility status, and a connectivity state.

6. The UE as claimed in claim 4, wherein the MDT mode comprises immediate MDT, logged MDT, and hybrid MDT which can readily switch between both immediate MDT and logged MDT.

7. The UE as claimed in claim 6, wherein if MDT reporting fails for immediate MDT, the UE is configured to switch to logged MDT and periodically reattempt transmission.

8. A method comprising: receiving, by a user equipment (UE), a radio resource control (RRC) message comprising one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receiving, by the UE, a measurement report comprising at least one of signal strength, data volume, and network congestion; and determining, by the UE, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.

9. The method as claimed in claim 8, wherein the list of MDT reporting methods comprises periodic reporting, event based reporting, and network request based reporting.

10. The method as claimed in claim 8, wherein the decision criteria comprises a signal strength threshold, a data volume threshold, and a network congestion level threshold.

11. The method as claimed in claim 8, wherein the RRC message further comprises hybrid MDT parameters including a list of MDT modes and transition criteria, wherein the method further comprises determining, by the UE, based on comparing the hybrid MDT parameters to the measurement report, that an MDT mode of the UE should be switched to a different MDT mode.

12. The method as claimed in claim 11, wherein the transition criteria comprises a signal strength threshold, a mobility status, and a connectivity state.

13. The method as claimed in claim 11, wherein the MDT mode comprises immediate MDT, logged MDT, and hybrid MDT which can readily switch between both immediate MDT and logged MDT.

14. The method as claimed in claim 13, wherein if MDT reporting fails for immediate MDT, the UE is configured to switch to logged MDT and periodically reattempt transmission.

15. A non-transitory computer-readable recording medium having recorded thereon instructions executable to perform a method comprising:receiving, by a user equipment (UE), a radio resource control (RRC) message comprising one or more minimization of drive test (MDT) reporting parameters including a list of MDT reporting methods and decision criteria; receiving, by the UE, a measurement report comprising at least one of signal strength, data volume, and network congestion; and determining, by the UE, based on comparing the MDT reporting parameters to the measurement report, that an MDT reporting method of the UE should be switched to a different MDT reporting method.

16. The non-transitory computer-readable recording medium as claimed in claim 15, wherein the list of MDT reporting methods comprises periodic reporting, event based reporting, and network request based reporting.

17. The non-transitory computer-readable recording medium as claimed in claim 15, wherein the decision criteria comprises a signal strength threshold, a data volume threshold, and a network congestion level threshold.

18. The non-transitory computer-readable recording medium as claimed in claim 15, wherein the RRC message further comprises hybrid MDT parameters including a list of MDT modes and transition criteria, wherein the method further comprises determining, by the UE, based on comparing the hybrid MDT parameters to the measurement report, that an MDT mode of the UE should be switched to a different MDT mode.

19. The non-transitory computer-readable recording medium as claimed in claim 18, wherein the transition criteria comprises a signal strength threshold, a mobility status, and a connectivity state.

20. The non-transitory computer-readable recording medium as claimed in claim 18, wherein the MDT mode comprises immediate MDT, logged MDT, and hybrid MDT which can readily switch between both immediate MDT and logged MDT.

Images