Methods performed by a UE and a base station

Abstract

A method performed by a user equipment (UE) includes receiving, from a base station, a logged measurement message with a logged measurement configuration. The method also initiates a minimization of drive test (MDT) session in response to receiving the logged measurement message. The method also determines a state of a UE component and, when the state satisfies a state criterion, selects a set of logged measurement types from a plurality of logged measurement types based on a measurement priority of each logged measurement type. When the state satisfies the state criterion, the method additionally generates MDT records at each of a plurality of logging instances based on measurement values collected for the set of logged measurement types. The method also transmits the MDT records of each logging instance to the base station after completion of the MDT session.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority under 35 U.S.C. § 119 to Indian Patent Application No. 202041027774, filed June 30, 2020, entitled “ENHANCED MINIMIZATION OF DRIVE TEST (MDT) FRAMEWORK,” the disclosure of which is hereby expressly incorporated by reference in its entirety. TECHNICAL FIELD

[0003] Aspects of the disclosure relate generally to wireless communication, and more particularly to techniques and apparatuses for minimization of drive test (MDT) framework. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP). Narrowband (NB)-Internet of Things (IoT) and enhanced Machine-Type Communications (eMTC) are sets of enhancements to LTE for machine type communications.

[0005] The wireless communications network can include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A user equipment (UE) can communicate with a base station (BS) via the downlink and uplink. The downlink (or forward link) refers to the communications link from the BS to the UE, and the uplink (or reverse link) refers to the communications link from the UE to the BS. As will be described in more detail, a BS can be referred to as a Node B, an evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a New Radio (NR) BS, a 5G Node B, and / or the like.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate on a municipal, national, regional, and even global level. New Radio (NR), which can also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP- OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. SUMMARY

[0007] In aspects of the disclosure, a method performed by a user equipment (UE) includes receiving, from a base station, a logged measurement message with a logged measurement configuration. The method further includes initiating a minimization of drive tests (MDT) session in response to receiving the logged measurement message. The method further includes determining a state of a UE component. The method additionally includes selecting a set of logged measurement types from a plurality of logged measurement types based on a measurement priority of each logged measurement type when the state satisfies a state criterion. The method further includes generating an MDT record at each logged instance of a plurality of logged instances based on measurement values collected for the set of logged measurement types when the state satisfies the state criterion. The method further includes transmitting the MDT record of each logged instance to the base station after completion of the MDT session.

[0008] In other aspects of the disclosure, a method performed by a user equipment (UE) includes receiving, from a base station, a logged measurement message with a logged measurement configuration. The method further includes initiating a minimization of drive tests (MDT) session in response to receiving the logged measurement message. The method further includes generating an MDT record at each logged instance of a plurality of logged instances based on measurement values collected for a plurality of logged measurement types configured by the logged measurement configuration. The method additionally includes filtering the MDT record of each logged instance to remove logged measurement types based on a measurement threshold after completion of the MDT session. The method further includes transmitting the filtered MDT record of each logged instance to the base station.

[0009] In other aspects of the disclosure, a method performed by a user equipment (UE) includes receiving, from a base station, a logged measurement message with a logged measurement configuration. The method also includes initiating a minimization of drive test (MDT) session in response to receiving the logged measurement message. The method also includes determining whether to perform measurements for a plurality of logged measurement types configured by the logged measurement configuration based on mobility of the UE. The method also includes generating MDT records based on the determined measurements to be performed. The method also includes transmitting the generated MDT records to the base station.

[0010] In other aspects of the disclosure, a method performed by a base station includes transmitting, to a user equipment (UE), a radio resource control (RRC) message with a logged measurement configuration, the logged measurement configuration including a minimization of drive test (MDT) measurement priority assigned to each of a plurality of measurement types. The method also includes receiving, from the UE, MDT records generated based on the logged measurement configuration.

[0011] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, or processing system as substantially described with reference to and as illustrated by the drawings and specification.

[0012] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions are not to be BRIEF DESCRIPTION OF DRAWINGS

[0013] So that the features and advantages of the present disclosure can be understood in detail, a more particular description will be rendered by reference to certain aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings are not intended to be exhaustive or limiting of the present disclosure, as aspects can be modified or designed in a variety of equivalent ways. The same reference numerals in different drawings can identify the same or similar elements.

[0014] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network, in accordance with various aspects of the present disclosure.

[0015] Figure 2 is a block diagram conceptually illustrating an example of a base station in communication with a user equipment (UE) in a wireless communication network, in accordance with various aspects of the present disclosure.

[0016] Figure 3 is a timing diagram illustrating an example of a minimization of drive tests (MDT) procedure.

[0017] Figure 4A An example of a logged measurement configuration message is shown.

[0018] Figure 4B Examples of a Bluetooth measurement information element and a wireless local area network measurement information element are shown.

[0019] Figure 5 An example of a logged measurement configuration including a measurement priority information element, in accordance with aspects of the present disclosure, is shown.

[0020] Figure 6 An example of a logged measurement configuration including a measurement threshold information element, in accordance with aspects of the present disclosure, is shown.

[0021] Figure 7 、 8 , 9, 10, and 11 are flow diagrams illustrating example processes performed, for example, by a user equipment, in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION

[0022] Various aspects of the disclosure are more fully described below with reference to the figures. The disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure whether implemented independently of, or combined with, any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using, in addition to or in place of the aspects set forth herein, other structures, functionalities, or structures and functions. It should be understood that any aspect of the disclosure disclosed can be embodied by one or more elements of a claim.

[0023] Several aspects of telecommunication systems will now be presented with reference to various apparatus and techniques. These apparatus and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and / or the like (collectively referred to as "elements"). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. It should be noted that while aspects can be described herein using terminology commonly associated with a 5G or later wireless technology, aspects of the present disclosure can be applied to other generations of mobile communication systems, such as, but not limited to, 3G and / or 4G technologies.

[0024] It should be noted that while aspects can be described herein using terminology commonly associated with a 5G or later wireless technology, aspects of the present disclosure can be applied to other generations of mobile communication systems, such as, but not limited to, 3G and / or 4G technologies.

[0025] The network consumes resources in collecting data to improve network quality. A minimization of drive tests (MDT) function can be specified to offload a portion of data collection (e.g., radio measurement collection) to a user equipment (UE). The network can configure an MDT session and propagate the MDT session configuration via a control plane, such as with radio resource control (RRC) messaging. For example, a base station can send an MDT logging message including a logging measurement configuration to a UE. In response to receiving the MDT logging message, the UE can initiate the MDT session. During the MDT session, the UE generates an MDT log including information elements based on measurements configured in the logging measurement configuration. Measurement values can be collected at each of a plurality of logging instances until the MDT session is complete. After the MDT session is complete, the UE can send a report to the base station indicating successful collection of the MDT log. The UE can then send the collected MDT log in response to receiving a request from the base station. The MDT session and reporting of the MDT log can be configured separately by the base station. Network coverage can be improved based on measurement values provided in the MDT log reported by the UE.

[0026] As network technology advances, the size of the MDT log increases. However, the amount of data allocated for MDT log transmission can be limited. Thus, the MDT log can be segmented and sent via multiple uplink messages. It is desirable to reduce the size of the MDT log, thereby reducing segmentation and also reducing network overhead.

[0027] Additionally, measurement collection for the MDT log can increase resources used by the UE, such as processor load, memory, and / or power. Increased resource usage can increase the thermal level of the UE and / or decrease the battery level. It is desirable to reduce the amount of resources used by the UE when collecting measurement values for the MDT log.

[0028] Aspects of the disclosure relate to removing redundant information from MDT records to reduce the size of the MDT records while also reducing the number of resources used by UEs when collecting measurements for the MDT records.

[0029] Figure 1 FIG. 1 is a schematic diagram illustrating a network 100 in which aspects of the disclosure can be implemented. The network 100 can be a 5G or NR network or some other wireless network, such as an LTE network. The wireless network 100 can include a number of BSs 110, shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd, and other network entities. A BS is an entity that communicates with user equipment (UEs) and can also be referred to as a base station, a NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit and receive point (TRP), etc. Each BS can provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0030] BSs can provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., several kilometers in radius) and can allow unrestricted access by UEs with service subscriptions with the network provider. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UEs with service subscriptions with the network provider. A femto cell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs having service subscriptions with the network provider. A BS for a macro cell can be referred to as a macro BS. A BS for a pico cell can be referred to as a pico BS. A BS for a femto cell can be referred to as a femto BS or a home BS. In the example shown in FIG. 1, a BS can be referred to as a gNB, which can operate in mmW frequencies and / or near mmW frequencies. A gNB can operate in a mmW or near mmW cellular network. Figure 1 In the example shown in FIG. 1, the BS 110a can be a macro BS for a macro cell 102a, the BS 110b can be a pico BS for a pico cell 102b, and the BS 110c can be a femto BS for a femto cell 102c. A BS can support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” can be used interchangeably herein.

[0031] In some aspects, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile BS. In some aspects, the BSs can be interconnected to one another and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as a direct physical connection, a virtual network, and / or the like using any appropriate transport network).

[0032] Wireless network 100 can also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, a relay station 1 lOd can communicate with macro BS 110a and a UE 120d in order to facilitate communications between the BS 110a and UE 120d. A relay station can also be referred to as a relay BS, a relay base station, a relay, and / or the like.

[0033] Wireless network 100 can be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and / or the like. These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference. For example, macro BSs can have a high transmit power level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 Watts).

[0034] As one example, the BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and the core network 130 can exchange communication via backhaul links 132 (e.g., SI, etc.). The base stations 110 can also communicate with one another (e.g., directly or indirectly via the core network 130) via other backhaul links (e.g., X2, etc.). The UEs 120 (e.g., 120a, 120b, 120c) can move in and out of the coverage areas of the BSs 110.

[0035] The core network 130 can be an evolved packet core (EPC), which can include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME can be the control node that processes the signaling between the UEs 120 and the EPC. All user IP packets can be transferred through the S-GW, which itself can be connected to the P-GW. The P-GW can provide IP address allocation as well as other functions. The P-GW can be connected to the operator's IP services. The operator's IP services can include the Internet, an intranet, an IP multimedia subsystem (IMS), and a packet-switched (PS) streaming service.

[0036] The core network 130 can provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations 110 or access network controllers (ANC) can interface with the core network 130 through backhaul links 132 (e.g., SI, S2, etc.) and can perform radio

[0037] The UEs 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be stationary or mobile. A UE can also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc. A UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0038] The UEs 120 can include an MDT logging module 140. For brevity, only one UE 120d is shown including the MDT logging module 140. The MDT logging module 140 can be configured to perform one or more of the processes 700, 800, 900, 1000, 1100 described in Figures 7-11 ​

[0039] The core network 130 or the base stations 110 (not shown) can include a MDT information element (IE) module 138 configured to receive MDT records from the UE 120. The MDT IE module 138 can identify missing information elements from the MDT records. If the information elements are missing, the MDT IE module 138 can use the measurement values of the information elements received in a previous MDT record.

[0040] Some UEs can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, e.g., robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that can communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node can provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Internet-of-Things (IoT) devices, and / or can be implemented as NB-IoT (narrowband internet of things) devices. Some UEs can be considered Customer Premises Equipment (CPE). The UE 120 can be included in a housing that houses components of the UE 120, such as processor components, memory components, and / or the like.

[0041] In general, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a particular radio access technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, an air interface, etc. A frequency can also be referred to as a carrier, a frequency channel, etc. Each frequency channel can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0042] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another). For example, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere as being performed by the base station 110. For example, the base station 110 can configure the UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE), or via system information (e.g., system information block (SIB)).

[0043] As indicated above, Figure 1 are provided by way of example only. Other examples can differ from what is described Figure 1 without departing from the spirit of the disclosure.

[0044] Figure 2 A block diagram of a design 200 of base station 110 and UE 120, which can be one of the base stations and one of the UEs in Figure 1 , is shown. Base station 110 can be equipped with T antennas 234a through 234t, and UE 120 can be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.

[0045] At base station 110, a transmit processor 220 can receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. Reducing the MCS decreases throughput but increases reliability of transmission. Transmit processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and can provide T output symbol streams to T modulators (MOD) 232a through 232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t can be transmitted via T antennas 234a through 234t, respectively. According to various aspects described in more detail below, the synchronization signals can be generated with location encoding to convey additional information.

[0046] At the UE 120, the antennas 252a through 252r can receive the downlink signals from the base station 110 and / or other base stations and can provide received signals to the demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 can obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The channel processor can determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 can be included in a housing.

[0047] On the uplink, at the UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from the controller / processor 280. Transmit processor 264 can also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, the uplink signals from UE 120 and other UEs can be received by the antennas 234, processed by demodulators 254, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. The receive processor 238 can provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The base station 110 can include a communication unit 244 and communicate to the core network 130 via the communication unit 244. The core network 130 can include a communication unit 294, a controller / processor 290, and a memory 292.

[0048] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components in FIG. 10 can perform one or more techniques associated with removing redundant information elements (e.g., a logged measurement type of a log) from a logged measurement report, as described in more detail elsewhere. For example, controller / processor 280 of UE 120, controller / processor 240 of base station 110, and / or any other component in FIG. 10 can perform Figure 2 operations of the processes illustrated by FIG. 10 and / or other processes as described. Figures 7-11 Memory 242 and 282 can store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 can schedule UEs for data transmission on the downlink and / or uplink.

[0049] In some aspects, UE 120 can include means for receiving, means for initiating, means for determining, means for selecting, means for generating, means for filtering, means for collecting, means for setting, means for bypassing, means for performing, means for obtaining, means for configuring, and / or means for transmitting. Such means can include one or more components of UE 120, core network 130, or base station 110 described in connection with Figure 2 FIG. 10, for example.

[0050] As indicated above, this description has been presented for the purpose of Figure 2 illustration and description. It is not intended to be exhaustive or to Figure 2 limit the example to the precise form disclosed.

[0051] Networks consume resources, such as capital resources and operational resources, to collect data for network improvement. A minimization of drive tests (MDT) function can be specified to offload a portion of data collection (e.g., radio measurement collection) to user equipment (UE). A network can configure an MDT session and propagate the MDT session configuration via a control plane, such as with radio resource control (RRC) messaging. For example, a base station can transmit an MDT logging message including a logging measurement configuration to a UE. In response to receiving the MDT logging message, the UE can initiate the MDT session.

[0052] During the MDT session, the UE generates an MDT log including information elements based on measurement values configured in the logging measurement configuration. The measurement values can be collected at each of a plurality of logging instances until the MDT session is complete. After the MDT session is complete, the UE can transmit a report to the base station indicating successful collection of the MDT log. The UE can then transmit the collected MDT log in response to receiving a request from the base station. The MDT session and reporting of the MDT log can be separately configured by the base station. Network coverage can be improved based on the measurement values provided in the MDT log reported by the UE.

[0053] With advancements in network technology, the size of MDT records has increased. However, the amount of data allocated for MDT record transmission may be limited. Therefore, MDT records can be segmented and sent via multiple uplink messages. Reducing the size of MDT records is desirable, thereby reducing segmentation and network overhead. Aspects of this disclosure relate to removing redundant information from MDT records to reduce their size.

[0054] Additionally, the collection of measurements for MDT recordings may increase resource consumption by the UE, such as processor load, memory, and / or power. Increased resource usage can increase the UE's thermal level and / or decrease battery level. It is desirable to reduce the amount of resources used by the UE when collecting measurements for MDT recordings.

[0055] As described, the UE can be configured to perform measurements during an MDT session when it is idle at each of multiple recording intervals (e.g., time points). Measurement values ​​for each recording interval can be collected and stored in a measurement record for reporting to the base station. For ease of explanation, the measurement record is referred to as an MDT record. An MDT record can also be referred to as a measurement report. Measurement values ​​can be referred to as MDT measurement values. An MDT record may include one or more MDT measurement values.

[0056] Figure 3 This is a timing diagram 300 illustrating an example of an MDT process. (See diagram 300.) Figure 3 As shown, at time t1, the UE is in Radio Resource Control (RRC) connection mode. When in RRC connection mode, the UE can establish user plane (UP) and control plane connections with the network. For ease of explanation, the network will be referred to as the base station (shown as...). Figure 3 (BS in the text). UE can be as referenced. Figure 1 The UE 120 described herein, and the base station may be as referenced Figure 1 The base station 110 is described.

[0057] In some cases, base station 110 can obtain information from the Mobility Management Entity (MME) during the initial context establishment process. Figure 3 The UE capability information provided in the initial context establishment request message (not shown) includes recorded MDT support capability information. At time t2, base station 110 sends a measurement configuration message including recorded measurement configuration. The measurement configuration received at time t2 may be a LoggedMeasurementConfiguration information element. Additionally, the measurement configuration can configure UE 120 to perform measurements for multiple measurement types included in the measurement configuration.

[0058] At time t3, the UE 120 enters an RRC idle state. Based on the measurement configuration received at time t2, the UE 120 initiates an MDT session at time t4. That is, the UE 120 initiates the MDT session after entering the RRC idle state. At time t5, the UE 120 generates MDT records at each logging instance for the duration of the MDT session based on MDT measurement values collected at the logging instances. That is, at time t5, the UE 120 performs MDT measurements for one or more information elements configured by the measurement configuration received at time t2. The MDT records can be generated at an RRC level of the UE 120. The logging instances and the duration of the MDT session can be configured by the base station 110.

[0059] As shown in FIG. 15B, at time t6, the MDT session is complete and the UE 120 stores the MDT records. The MDT records can be stored for a period of time, such as 48 hours. The size of each MDT record can be different. For example, in a regular system, the size of the MDT records can be 64 KB or 3 MB. Figure 3

[0060] At time t7, the UE 120 enters an RRC connected mode. Upon entering the RRC connected mode, the UE 120 sends a message to the base station 110 indicating that it has validly stored the MDT records (time t8). The indication can be provided via a logged measurement available information element, such as logMeasAvailable. The information element can be provided in an RRC connection complete message, such as an RRCConnectionSetupComplete message sent during connection setup, an RRCConnectionReconfigurationComplete message sent during handover, or an RRCConnectionReestablishmentComplete message sent during connection reestablishment.

[0061] In response to receiving the indication of validly stored MDT records, the base station 110 sends a request message requesting transmission of the MDT records (time t9). At time t10, in response to receiving the request message, the UE 120 generates a UE information confirmation message including the collected MDT records. The UE information confirmation message can be a type of RRC message.

[0062] The information confirmation message generated at time t10 can not include all of the collected MDT records because lower layers of the network connection limit the size of the RRC message. In some cases, the size is limited to 8188 bytes. Based on the limit, at time t10, the UE 120 segments the MDT records into multiple segments (time t11). The UE 120 sends the segments to the base station 110 (time t12). The segments can be sent in a series of RRC messages. Figure 3 ​The MDT records can be segmented into segments (not shown). For example, if the MDT records are 64 KB, the UE 120 can segment the MDT records into eight segments, where each segment is 8 KB. As described, the size of the MDT records can vary. Thus, the segments can be larger or smaller than 8 KB. In the current example, at time tl 1, the UE 120 transmits one segment of one of the collected MDT records. In response to receiving the one segment of one of the collected MDT records, at time t12, the base station 110 transmits a message requesting transmission of the MDT record. At time t13, the UE 120 generates a second UE information confirmation message including a segment of one of the collected MDT records. The segment is transmitted in the second UE information message at time t14. The procedure described for times t10-t14 can be repeated until all of the MDT records are transmitted.

[0063] In improved LTE releases, such as Release 13 and beyond, the measurement configuration, such as the LoggedMeasurementConfiguration information element, can configure the UE to include wireless local area network (WLAN) measurements and / or Bluetooth TM (BT) information elements in the MDT records. For example, the LoggedMeasurementConfiguration message can include a UE-BasedNetwPerfMeasParameters-v1530 information element that defines optional measurement parameters for wireless local area network (WLAN) and Bluetooth TM (BT), such as loggedMeasBT-r15, loggedMeasWLAN-r15, immMeasBT-r15, and immMeasWLAN-r15. As a result of the new measurement parameters, the size of the MDT records has grown, increasing the number of RRC message segments for each MDT record collected by the UE.

[0064] Figure 4A An example of a LoggedMeasurementConfiguration message is shown. As shown in Figure 4A The LoggedMeasurementConfiguration message can also include information elements (IEs) for WLAN and BT, such as bt-NameList-r15 and wlan-NameList-r15, as shown in Figure 4A The bt-NameList-r15 and wlan-NameList-r15 IEs are optional, as shown in

[0065] As described, the UE can obtain MDT measurement values for the information elements configured in the measurement configuration. Figure 4BExamples of Bluetooth information elements are shown. As shown in Figure 4B Bluetooth information elements (shown as LogMeasResultListBT) provide Bluetooth measurement values. The Bluetooth information elements can provide a Bluetooth public address of a Bluetooth beacon (shown as bt-Addr-r15), and can also optionally provide a received signal strength indicator (RSSI) (shown as rssi-BT-r15).

[0066] Figure 4B Examples of WLAN information elements are also shown. As shown in Figure 4B WLAN information elements (shown as LogMeasResultListWLAN-r15) provide WLAN measurement values. The WLAN information elements can provide a WLAN identifier (shown as wlan-Identifiers-r15), a received signal strength indicator (RSSI) (shown as rssiWLAN-r15), and a round trip time (RTT) (shown as rtt-WLAN-r15). The RSSI and RTT can be optional.

[0067] As described, to reduce network bandwidth and to reduce the number of resources consumed by the UE (e.g., processing power, transmission resources, memory, etc.), it is desirable to reduce MDT record fragmentation. Aspects of the present disclosure are directed to reducing the number of fragments resulting from fragmenting RRC messages that include MDT records. In some implementations, the MDT records include one or more information elements for MDT measurement values, such as NR information elements, WLAN information elements, and / or BT information elements. Aspects of the present disclosure are not limited to MDT records having NR information elements, WLAN information elements, and / or BT information elements. Other information elements can be included as additions or alternatives to NR information elements, WLAN information elements, and / or BT information elements. Manufacturers (e.g., original equipment manufacturers (OEMs)) and / or network operators can request information elements for MDT measurement values.

[0068] As described, current 3GPP standard releases, such as Release 15, do not specify techniques for reducing MDT record fragmentation. In some configurations, fragmentation is reduced by filtering (e.g., removing) redundant information elements from one or more MDT records. In some examples, the redundant information elements can include, for example, a serving cell identifier (ID) (e.g., identity), a neighbor cell ID, a carrier frequency, an inter radio access technology (IRAT) ID, a WLAN ID, and / or a BT ID.

[0069] Additionally, MDT measurement collection can cause increased heat levels, reduced battery levels, and / or other undesirable conditions at the UE. In conventional systems, for example, a UE can stop performing MDT measurements based on a state of a UE component when a battery level is below a threshold.

[0070] According to aspects of the present disclosure, a measurement priority is specified for each logged measurement type. For example, a measurement priority can be added to logged measurement types, such as serving cell measurements, neighbor cell measurements, Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) measurements, WLAN measurements, BT measurements, location measurements, and / or other measurements. Aspects of the present disclosure are not limited to the measurement types described above. Other measurement types, such as future measurement types, are also contemplated. The measurement priority can be included as an information element, such as MDT measurement priority. The measurement priority information element can be added to each measurement type in logged measurement configuration messages sent from a base station.

[0071] A UE can reduce the scope of MDT measurement collection based on the measurement priority. For example, if a UE is operating in a limited power mode (e.g., a battery level is less than a threshold), the UE can collect a limited number of MDT measurement values. In some examples, the UE collects MDT measurement values for logged measurement types assigned with the highest measurement priority. In other examples, the UE can perform measurements for measurement types corresponding to the top X measurement priorities, where X can be implementation specific. The value of X can be adjusted based on a battery level or battery condition, for example.

[0072] As described, MDT logging can include a limited number of MDT measurement values based on the measurement priority and a state of a UE component, such as a battery level, a thermal state of a processor, and / or a state of another component. The state is not limited to a battery level or a thermal condition. Other conditions are contemplated. The state can be configured based on OEM and / or network operator configuration.

[0073] Figure 5 An example of a logged measurement configuration (shown as LoggedMeasurementConfiguration-r10-IEs) including a measurement priority information element is shown in accordance with aspects of the present disclosure. As shown in Figure 5 As shown in Table 1, a measurement priority information element (shown as mdt_meas_Priority) can be added to logged measurement types, such as serving cell measurements, neighbor cell measurements, location measurements, MBSFN measurements, WLAN measurements, and / or BT measurements. The measurement priority information element can associate a priority value, such as an integer between 0 and 7, with each measurement type. In some configurations, the measurement priority information element is optional.

[0074] In some implementations, measurement priorities are configured by an original equipment manufacturer (OEM) and / or a network operator via an encrypted file system (EFS) method. For example, the OEM can configure measurement priorities via an over-the-air update.

[0075] As described, the network can improve coverage based on MDT records received from the UE. Network coverage information in the MDT records can identify locations that experience less than a power threshold of cell power, less than a coverage threshold of coverage, and / or greater than an interference threshold of interference. Thus, measurements that identify locations that experience greater than a power threshold of cell power, greater than a coverage threshold of coverage, and / or less than an interference threshold of interference can not be useful to the network.

[0076] In some configurations, the MDT records are filtered to exclude (e.g., remove) measurement types above a measurement threshold at each record instance. That is, if the measurement result is above the threshold, the measurement type can not provide value for the MDT report. The measurement type of each record can have a defined threshold. For example, the MDT records of each record instance can be filtered to remove measurement types that can not be useful for improving network coverage. The MDT records can be filtered after the MDT session is complete. The network can configure the threshold value based on threshold criteria to receive the report.

[0077] As one example, the MDT records can be filtered to remove signal strength measurement types (e.g., reference signal received power (RSRP) measurements or reference signal received quality (RSRQ) measurements) that are greater than a signal strength threshold. In this example, the received signal strength can be measured for a serving cell, WLAN, and / or neighbor cell. The filtered MDT records can include signal strength measurement types for a cell that have a received signal power less than the signal strength threshold. In some configurations, the signal strength measurement type is excluded if the measurement value is above the corresponding threshold for all measurement types. The threshold is not limited to signal strength measurement types, other measurement types are considered, such as interference.

[0078] As described, the MDT records can be filtered to remove signal strength or signal quality measurement types for a serving cell and / or other measurement types that are greater than a defined threshold. The measurement types can be defined for, for example, a serving cell, a neighbor cell, a WLAN, BT, and / or MBSFN.

[0079] As described, the UE can report only information elements for cells that are below a signal power threshold to reduce the size of the MDT records. Reducing the size of the MDT records can also improve UE power savings. Aspects of the disclosure are not limited to filtering information elements based only on a signal power threshold. Other measurement thresholds can be specified.

[0080] In some configurations, a measurement threshold information element, such as a MDT measurement threshold, can be added to each measurement type in a logged measurement configuration. The measurement types can include, for example, serving cell, neighbor cell, WLAN, BT, and / or MBSFN. Figure 6 An example of a logged measurement configuration including a measurement threshold information element (shown as LoggedMeasurementConfiguration-r10-IE) is shown in accordance with aspects of the present disclosure. As shown in Figure 6 As shown in the middle, a measurement threshold information element (shown as mdt_meas_Threshold_Index) can be added to different measurement type information elements, such as Mdt_serving_Threshold, MDT_Neighbor_Threshold, MDT_MBSFN_meas_threshold, Mdt_wlan_meas_threshold, and Mdt_bt_meas_Threshold. Each measurement threshold information element can be assigned a threshold value based on an index (shown as mdt_meas_Threshold_Index), such as an integer between 0 and 7. A table can relate the measurement values to the index.

[0081] Additionally or alternatively, the measurement threshold can be configured by the OEM and / or network operator via an encrypted file system (EFS) method. For example, the OEM can configure the measurement priority via over-the-air updates.

[0082] Other inputs from the UE, such as battery power, thermal conditions, and / or other inputs, can be considered in determining whether to send the MDT record. In some configurations, measurements are performed based on the measurement priority of the logged measurement type. Further, information elements in the MDT record are filtered based on the measurement threshold. For example, based on the status of the UE components (e.g., battery level), the MDT measurements can be performed based on the assigned measurement priority of the logged measurement type. At each logging interval, the performed MDT measurements can be collected into the MDT record. After the MDT session, the MDT record can be filtered to remove information elements based on one or more thresholds. For example, signal strength measurement values greater than a signal strength threshold can be removed from the MDT record.

[0083] As described, MDT measurements can improve network coverage. During a period of logging instances, MDT measurements from a stationary UE can be redundant. That is, one or more MDT measurements can be the same when the UE is stationary. Thus, the MDT measurements can fail to improve network coverage.

[0084] In some configurations, a sensor of the UE, such as a location sensor (e.g., a global positioning system (GPS) sensor), determines whether the UE is stationary. The UE can be stationary if a distance traveled over a motion state evaluation period is less than a distance threshold. Alternatively, the sensor can determine that the UE is moving. When the UE is stationary, one or more information elements can be removed from one or more MDT records.

[0085] In some configurations, mobility of the UE can be determined at each of a plurality of motion state evaluation periods. The motion state evaluation periods can be specified during the MDT session. As one example, at a current motion state evaluation period (e.g., a first motion state evaluation period), based on location sensor information (e.g., global positioning system (GPS) information), the MDT logging module (such as the MDT logging module 140 described) determines whether the UE is stationary or moving. Figure 1

[0086] In one example, if the UE is stationary, the MDT logging module schedules a subsequent motion state evaluation period (e.g., a second motion state evaluation period). The time period between the current motion state evaluation period and the subsequent motion state evaluation period can be a first logging instance quantity. The MDT logging module can collect MDT measurements (e.g., generate MDT records) during the first logging instance quantity. At the subsequent motion state evaluation period, the MDT logging module determines whether the UE is moving or stationary.

[0087] If the UE is stationary at the subsequent motion state evaluation period (e.g., the second motion state evaluation period), the MDT logging module schedules another subsequent motion state evaluation period (e.g., a third motion state evaluation period). In this example, the time period between the second motion state evaluation period and the third motion state evaluation period can be a second logging instance quantity. The first logging instance quantity is less than or equal to the second logging instance quantity. The MDT logging module does not collect MDT measurements during. The process described above for the first motion state evaluation period is repeated at the time period of the third motion state evaluation period.

[0088] ​Alternatively, if the UE is mobile at a subsequent motion state evaluation period (e.g., a second motion state evaluation period), the MDT logging module schedules another subsequent motion state evaluation period (e.g., a fourth motion state evaluation period). The motion state evaluation periods can be implementation specific. The time period between the evaluation periods can also be implementation specific. In this example, the time period between the second motion state evaluation period and the fourth motion state evaluation period can be the first logging instance quantity. As described, the MDT logging can collect measurements during the first logging instance quantity. The process described above for the first motion state evaluation period is repeated at the time period of the third motion state evaluation period.

[0089] As another example, if the UE is mobile at the first motion state evaluation period, the MDT logging module schedules a subsequent motion state evaluation period. In this example, the time period between the first motion state evaluation period and the subsequent motion state evaluation period is the first logging instance quantity. As described, the MDT logging can collect measurements during the first logging instance quantity. The process described above for the first motion state evaluation period is repeated at the time period of the subsequent motion state evaluation period.

[0090] As noted above, Figures 3-6 are provided as examples. Other examples can differ from what is described Figures 3-6 without departing from the spirit of the disclosure.

[0091] Figure 7 is a flow diagram that illustrates an example process 700 performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 700 is an example of reducing redundant measurement types from MDT logging.

[0092] As Figure 7 shown in FIG. 15, at block 702, process 700 receives, from a base station, a logging measurement message including a logging measurement configuration. The measurement configuration can configure the UE to perform measurements for a plurality of measurement types included in the measurement configuration. Further, at block 704, process 700 initiates a minimization of drive test (MDT) session in response to receiving the logging measurement message.

[0093] At block 706, process 700 determines a state of a UE component. For example, the process can determine a state of a battery, and the state can be a battery level. In other examples, the process can determine a state of a processor, and the state can be a heat level.

[0094] Further, at block 708, process 700 selects a set of logged measurement types from the plurality of logged measurement types based on a measurement priority of each logged measurement type when the UE state satisfies a state criterion.

[0095] Additionally, at block 710, the process 700 generates MDT records at each of a plurality of logging instances based on measurement values collected for a set of logged measurement types when the UE state satisfies a state criterion. In some cases, the method can satisfy the state criterion when a battery level is below a threshold. In other examples, the process can satisfy the state criterion when a thermal level is greater than a threshold. The UE can collect measurement values at each logging instance for the set of logged measurement types from the logged measurement types. The logged measurement types can include serving cell measurements, neighbor cell measurements, wireless local area network (WLAN) measurements, Bluetooth measurements, location measurements, multimedia broadcast multicast service single frequency network (MBSFN) measurements, and / or implementation-specific measurements. In some aspects, the UE receives a message from an original equipment manufacturer or network operator indicating a measurement priority for each logged measurement type. In other aspects, the UE determines the measurement priority for each logged measurement type from a logging measurement configuration.

[0096] Finally, at block 712, the process 700 transmits the MDT records for each logging instance to a base station after completing the MDT session. Due to the reduction in redundant measurement types, the transmitted MDT records are smaller than the MTD records without prioritization.

[0097] Figure 8 FIG. 8 is a flow chart illustrating an example process 800 performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 800 is an example of reducing redundant measurement types from MDT records.

[0098] As Figure 8 As shown in block 802, the process 800 receives a logging measurement message including a logging measurement configuration from a base station. The measurement configuration can configure the UE to perform measurements for a plurality of measurement types included in the measurement configuration. Additionally, at block 804, the process 800 initiates a minimization of drive tests (MDT) session in response to receiving the logging measurement message.

[0099] At block 806, the process 800 generates MDT records at each of a plurality of logging instances based on measurement values collected for logged measurement types configured by the logging measurement configuration. The UE can collect measurement values at each logging instance for the set of logged measurement types from the logged measurement types. The logged measurement types can include serving cell measurements, neighbor cell measurements, wireless local area network (WLAN) measurements, Bluetooth measurements, location measurements, multimedia broadcast multicast service single frequency network (MBSFN) measurements, and / or implementation-specific measurements.

[0100] Further, at block 808, the process 800 filters the MDT records for each logged instance to remove logged measurement types based on a measurement threshold after completion of the MDT session. For example, the filtering can remove a transmit power measurement value that is greater than a transmit power threshold. In some aspects, the UE can determine the measurement threshold from the logging measurement configuration. In other aspects, the UE can receive a message from a network operator or original equipment manufacturer (OEM) indicating the measurement threshold.

[0101] Finally, at block 810, the process 800 transmits the filtered MDT records for each logged instance to the base station. Due to the reduction in redundant measurement types, the transmitted MDT records are smaller than the MTD records without filtering.

[0102] Figure 9 FIG. 9 is a flow chart illustrating an example process 900 performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 900 is an example of reducing redundant measurement types from MDT records.

[0103] As Figure 9 As shown in block 902, the process 900 receives a logging measurement message including a logging measurement configuration from a base station. The measurement configuration can configure the UE to perform measurements for a plurality of measurement types included in the measurement configuration. At block 904, the process 900 initiates a minimization of drive test (MDT) session in response to receiving the logging measurement message.

[0104] Further, at block 906, the process 900 determines whether to perform measurements for the plurality of logged measurement types configured by the logging measurement configuration based on mobility of the UE. In some configurations, a sensor of the UE, such as a location sensor (e.g., a global positioning system (GPS) sensor), determines whether the UE is stationary. The UE can be stationary if a distance traveled is less than a distance threshold for a motion state evaluation period. Alternatively, the sensor can determine that the UE is mobile.

[0105] Further, at block 908, the process 900 generates MDT records based on the performed measurements. One or more information elements can be removed from one or more MDT records when the UE is stationary. Finally, at block 910, the process 900 transmits the generated MDT records to the base station. Due to the reduction in redundant measurement types, the transmitted MDT records are smaller than the MDT records without the mobility determination.

[0106] Figure 10 FIG. 10 is a flow chart illustrating an example process 1000 performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 1000 is an example of reducing redundant measurement types from MDT records.

[0107] As Figure 10As shown in FIG. 10, at block 1002, the process 1000 receives, from a base station, a logged measurement message including a logged measurement configuration. The measurement configuration can configure the UE to perform measurements for a plurality of measurement types included in the measurement configuration. Further, at block 1004, the process 1000 initiates a minimization of drive test (MDT) session in response to receiving the logged measurement message.

[0108] Additionally, at block 1006, the process 1000 determines a state of a UE component. For example, the process can determine a state of a battery, and the state can be a battery level. In other examples, the process can determine a state of a processor, and the state can be a heat level.

[0109] Further, at block 1008, the process 1000 selects a set of logged measurement types based on a measurement priority of each logged measurement type when the UE state satisfies a state criterion. Further, at block 1010, the process 1000 generates MDT records at each logged instance of a plurality of logged instances based on collected measurement values for the set of logged measurement types when the UE state satisfies the state criterion. In some cases, the method can satisfy the state criterion when the battery level is below a threshold. In other cases, the process can satisfy the state criterion when the heat level is greater than a threshold.

[0110] Further, at block 1012, the process 1000 filters the MDT records of each logged instance based on a measurement threshold to remove collected measurement values after completion of the MDT session. For example, the filtering can remove a transmit power measurement value that is greater than a transmit power threshold. Finally, at block 1014, the process 1000 transmits the filtered MDT records of each logged instance to the base station. The transmitted MDT records are less than the MDT records without filtering due to the reduction of redundant measurement types.

[0111] Figure 11 is a flow chart illustrating an example process 1100 performed, for example, by a base station, in accordance with various aspects of the present disclosure. The example process 1100 is an example of reducing redundant measurement types from MDT records.

[0112] As Figure 11As shown in FIG. 11, at block 1102, the process 1100 transmits, to a user equipment (UE), a radio resource control (RRC) message including a logged measurement configuration, the logged measurement configuration including a minimization of drive test (MDT) measurement priority assigned to each measurement type in a measurement type group. The MDT measurement priority can be indicated in an additional information element. The measurement types include a serving cell measurement type, a neighbor cell measurement type, a location measurement type, a multimedia broadcast multicast service single frequency network (MBSFN) measurement type, a wireless local area network (WLAN) measurement type, and / or a Bluetooth measurement type. In some aspects, the MDT measurement priority is an integer. The MDT log can include a subset of the measurement types configured in the logged measurement configuration. At block 1104, the process 1100 receives, from the UE, an MDT log generated based on the logged measurement configuration.

[0113] The processes 700, 800, 900, 1000, and 1100 described above can be performed by one or more components of a UE, such as the UE 120 of FIG. 1. Figure 1 For example, the processes 700, 800, 900, 1000, and 1100 can be performed by the antennas 252a, the antennas 252r, the DEMOD / MOD 254a, the DEMOD / MOD 254r, the MIMO detector 256, the TX MIMO processor 266, the receive processor 258, the transmit processor 264, the controller processor 280, and / or the memory 282 of the UE.

[0114] Implementations are described in the following numbered clauses:

[0115] 1. A method performed by a user equipment (UE), comprising:

[0116] receiving, from a base station, a logged measurement message including a logged measurement configuration;

[0117] initiating a minimization of drive test (MDT) session in response to receiving the logged measurement message;

[0118] determining a status of a UE component;

[0119] selecting, when the status satisfies a status criterion, a set of logged measurement types from a plurality of logged measurement types based on a measurement priority of each logged measurement type;

[0120] generating, when the status satisfies the status criterion, an MDT record at each logged instance of a plurality of logged instances based on measurement values collected for the set of logged measurement types; and

[0121] transmitting, to the base station, the MDT record of each logged instance after completion of the MDT session.

[0122] 2. The method of clause 1, further comprising collecting, at each logging instance, measurement values for a set of logged measurement types of the logging from the plurality of logged measurement types, wherein the plurality of logged measurement types comprises serving cell measurements, neighbor cell measurements, wireless local area network (WLAN) measurements, Bluetooth measurements, location measurements, multimedia broadcast multicast service single frequency network (MBSFN) measurements, and / or implementation-specific measurements.

[0123] 3. The method of clause 1 or 2, wherein the measurement priority for each logged measurement type in the set of logged measurement types satisfies a priority criterion.

[0124] 4. The method of any of the preceding clauses, further comprising setting the priority criterion to a range of highest priority values.

[0125] 5. The method of any of the preceding clauses, wherein the range is based on the state.

[0126] 6. The method of any of the preceding clauses, wherein the UE component comprises a battery and the state comprises a battery level, and the method further comprises satisfying the state criterion when the battery level is less than a threshold.

[0127] 7. The method of any of the preceding clauses, wherein the UE component comprises a processor and the state comprises a thermal level, and the method further comprises satisfying the state criterion when the thermal level is greater than a threshold.

[0128] 8. The method of any of the preceding clauses, further comprising receiving a message from an original equipment manufacturer or network operator indicating the measurement priority for each logged measurement type in the plurality of logged measurement types.

[0129] 9. The method of any of the preceding clauses, further comprising determining the measurement priority for each logged measurement type in the plurality of logged measurement types according to the logged measurement configuration.

[0130] 10. The method of any of the preceding clauses, wherein the state comprises a configuration provided by an original equipment manufacturer (OEM) or network operator.

[0131] 11. The method of any of the preceding clauses, wherein the plurality of logged measurement types is a subset of logged measurement types configured in the logged measurement configuration.

[0132] 12. The method of any of the preceding clauses, further comprising:

[0133] filtering the MDT records of each logged instance based on a measurement threshold to remove collected measurements after completion of the MDT session; and

[0134] sending the filtered MDT records of each logged instance to the base station.

[0135] 13. A method performed by a user equipment (UE), comprising:

[0136] receiving a logging measurement message from a base station including a logging measurement configuration;

[0137] initiating a minimization of drive test (MDT) session in response to receiving the logging measurement message;

[0138] generating MDT records at each of a plurality of logged instances based on measurements collected for a plurality of logged measurement types configured by the logging measurement configuration;

[0139] filtering the MDT records of each logged instance based on a measurement threshold to remove logged measurement types after completion of the MDT session; and

[0140] sending the filtered MDT records of each logged instance to the base station.

[0141] 14. The method of clause 13, wherein the logged measurement types include signal strength measurements of at least one of a serving cell, a neighbor cell, an inter radio access technology (IRAT) cell, a multimedia broadcast multicast service single frequency network (MBSFN) cell, a wireless local area network (WLAN) cell, a Bluetooth cell, or a combination thereof, and the measurement threshold includes a signal strength / signal quality measurement threshold.

[0142] 15. The method of clause 13 or 14, wherein the filtering includes removing transmit power measurement values that are greater than a transmit power threshold.

[0143] 16. The method of any of clauses 13-15, further comprising determining the measurement threshold from the logging measurement configuration.

[0144] 17. The method of any of clauses 13-16, further comprising receiving a message from a network operator or original equipment manufacturer (OEM) indicating the measurement threshold.

[0145] 18. A method performed by a user equipment (UE), comprising:

[0146] receiving a logging measurement message from a base station including a logging measurement configuration;

[0147] initiating a minimization of drive test (MDT) session in response to receiving the logged measurement message;

[0148] determining whether to perform measurements for a plurality of logged measurement types configured by the logged measurement configuration based on mobility of the UE;

[0149] generating MDT records based on the determined measurements to be performed; and

[0150] sending the generated MDT records to the base station.

[0151] 19. The method of clause 18, wherein determining whether to perform the measurements comprises:

[0152] determining that the UE is stationary at a first time period during the MDT session;

[0153] determining whether the UE is stationary at a second time period, a time difference between the first time period and the second time period comprising a first number of logging instances;

[0154] when the UE is stationary at the second time period, bypassing measurements of a plurality of information elements for a second number of logging instances after the second time period; and

[0155] when the UE is mobile at the second time period, performing the measurements of the plurality of information elements for the second number of logging instances after the second time period.

[0156] 20. The method of clause 18 or 19, further comprising performing measurements of the plurality of information elements at each logging instance and a first number of logging instances corresponding to the first time period.

[0157] 21. The method of any of clauses 18-20, wherein the first number of logging instances is less than or equal to the second number of logging instances.

[0158] 22. The method of any of clauses 18 or 20-21, wherein determining whether to perform the measurements comprises:

[0159] determining that the UE is moving at a first time period during the MDT session;

[0160] determining whether the UE is stationary at a second time period, a time difference between the first time period and the second time period comprising a first number of logging instances;

[0161] performing the measurements of the plurality of measurement types within a second number of logging instances after the second time period when the UE is moving at the second time period.

[0162] 23. The method of any of clauses 18-22, further comprising determining the mobility based on positioning sensor measurements.

[0163] 24. The method of any of clauses 18-23, further comprising obtaining the positioning sensor measurements at each motion state evaluation period.

[0164] 25. The method of any of clauses 18-24, further comprising configuring a subsequent motion state evaluation period after a current motion state evaluation period based on whether the UE is stationary or moving.

[0165] 26. A method performed by a base station, comprising:

[0166] transmitting, to a user equipment (UE), a radio resource control (RRC) message including a logged measurement configuration, the logged measurement configuration including a minimization of drive tests (MDT) measurement priority assigned to each of a plurality of measurement types; and

[0167] receiving, from the UE, an MDT log generated based on the logged measurement configuration.

[0168] 27. The method of clause 26, further comprising transmitting the MDT measurement priority in an additional information element.

[0169] 28. The method of clause 26 or 27, wherein the plurality of measurement types includes at least one of a serving cell measurement type, a neighbor cell measurement type, a position measurement type, a multimedia broadcast multicast service single frequency network (MBSFN) measurement type, a wireless local area network (WLAN) measurement type, or a Bluetooth measurement type.

[0170] 29. The method of any of clauses 26-28, wherein the MDT measurement priority includes an integer.

[0171] 30. The method of any of clauses 26-29, wherein the MDT log includes a subset of the plurality of measurement types configured in the logged measurement configuration.

[0172] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be possible in light of the above disclosure or from practicing the aspects. It is intended that the scope of the aspects disclosed herein be limited only by the claims.

[0173] As used herein, the term “component” is intended to be broadly interpreted to include hardware, firmware, and / or combinations of hardware and software. As used herein, a “processor” is implemented in hardware, firmware, and / or combinations of hardware and software.

[0174] Some aspects are described herein in connection with thresholds. As used herein, satisfying a threshold can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and / or the like, depending on the context.

[0175] It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in different forms of hardware, firmware, and / 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 limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it being understood that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0176] Even if a particular feature is expressly identified in the claims and / or the specification as having a certain combinations with other features, that feature does not necessarily exclude from the scope of the disclosure other combinations of the feature with other disclosure features. In fact, many of the features can be combined in ways not expressly identified in the claims and / or specification. Although each dependent claim listed below can only directly depend on one claim, the disclosure of each dependent claim encompasses combinations of the features of each dependent claim with each other claim in the set of claims. A phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any of the possible individual permutations, e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c.

[0177] 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 can be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, or the like), and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and / 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.

Claims

1. A method performed by a user equipment (UE), comprising: receiving, from a base station, a logged measurement message comprising a logged measurement configuration; initiating a minimization of drive test (MDT) session in response to receiving the logged measurement message; determining a state of a UE component, wherein the state comprises a thermal level; satisfying a state criterion when the thermal level is greater than a threshold; selecting a set of logged measurement types from a plurality of logged measurement types based on a measurement priority of each logged measurement type of the set of logged measurement types when the state satisfies the state criterion, wherein the measurement priority of each logged measurement type of the set of logged measurement types satisfies a priority criterion, wherein the priority criterion is set to a range of highest priority values, and wherein the range is based on the state; generating MDT records at each logged instance of a plurality of logged instances based on measurement values collected for the set of logged measurement types when the state satisfies the state criterion; and sending the MDT records of each logged instance to the base station after completion of the MDT session.

2. The method of claim 1, further comprising: collecting measurement values at each logged instance for the set of logged measurement types from the plurality of logged measurement types, wherein the plurality of logged measurement types comprises serving cell measurements, neighbor cell measurements, wireless local area network (WLAN) measurements, Bluetooth measurements, location measurements, multimedia broadcast multicast service single frequency network (MBSFN) measurements, and / or implementation-specific measurements.

3. The method of claim 1, wherein, the UE component comprises a battery and the state comprises a battery level, and the method further comprises satisfying the state criterion when the battery level is less than a threshold.

4. The method of claim 1, further comprising: receiving a message from an original equipment manufacturer or a network operator indicating the measurement priority for each logged measurement type of the plurality of logged measurement types.

5. The method of claim 1, further comprising: determining the measurement priority for each logged measurement type of the plurality of logged measurement types from the logged measurement configuration.

6. The method of claim 1, wherein, the state comprises a configuration provided by an original equipment manufacturer (OEM) or a network operator.

7. The method of claim 1, wherein, the plurality of logged measurement types is a subset of logged measurement types configured in the logged measurement configuration.

8. The method of claim 1, further comprising: filtering the MDT records of each logged instance to remove collected measurement values based on a measurement threshold after completion of the MDT session; and sending the filtered MDT records of each logged instance to the base station.

9. A method performed by a base station, comprising: sending, to a user equipment (UE), a radio resource control (RRC) message comprising a logged measurement configuration, the logged measurement configuration comprising a minimization of drive test (MDT) measurement priority assigned to each measurement type of a plurality of measurement types; and ​ ​ receive, from the UE, MDT records, wherein the MDT records are generated based on the logged measurement configuration including a logged measurement type and based on the logged measurement type satisfying a priority criterion, wherein the priority criterion is set to a range of highest priority values, and wherein the range is based on a status of the UE component.

10. The method of claim 9, wherein, The plurality of measurement types includes at least one of a serving cell measurement type, a neighbor cell measurement type, a position measurement type, a Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) measurement type, a Wireless Local Area Network (WLAN) measurement type, or a Bluetooth measurement type.

11. The method of claim 9, wherein, The MDT measurement priority includes an integer.

12. The method of claim 9, wherein, The MDT records include a subset of the plurality of measurement types configured in the logged measurement configuration. The MDT records include a subset of the plurality of measurement types configured in the logged measurement configuration.

Images