UE network minimization of drive tests (MDT)

Abstract

Apparatus, methods, and computer program products for wireless communication are provided. An example method may include receiving a Minimum Drive Test (MDT) configuration from a network node, wherein the MDT configuration configures a UE to perform a set of MDT measurements for a threshold time period following the receipt of the MDT configuration. The example method may also include sending an indication to the network node that the UE cannot perform the set of MDT measurements within the threshold time period.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of Indian Patent Application Serial No. 202411004575, filed on January 23, 2024, entitled “UE-NETWORK MINIMIZATION OFDRIVE TESTS (MDT)”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to wireless communication systems with minimized drive test (MDT). Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR are based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, methods, computer-readable media, and apparatuses are provided at a user equipment (UE). The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to receive a Minimum Drive Test (MDT) configuration from a network node, wherein the MDT configuration configures the UE to perform a set of MDT measurements within a threshold time period following the receipt of the MDT configuration. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to send an indication to the network node that the UE cannot perform the set of MDT measurements within the threshold time period.

[0008] In another aspect of this disclosure, methods, computer-readable media, and apparatuses are provided at a network entity. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to send an MDT configuration to a UE, wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time period following receipt of the MDT configuration. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to receive from the UE an indication that the UE cannot perform the MDT measurement set within the threshold time period.

[0009] In another aspect of this disclosure, methods, computer-readable media, and apparatus at a UE are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured, individually or in any combination, to receive an MDT configuration associated with a first subscriber identity from a network node, based at least in part on information stored in the at least one memory. The at least one processor is configured, individually or in any combination, to perform the MDT measurement set based on a second subscriber identity, based at least in part on the information stored in the at least one memory, either based on (1) the UE cannot perform an MDT measurement set based on the first subscriber identity within a threshold time period, (2) signal fluctuations reach a threshold, or (3) the UE is in a mobility state or at a specific location. The at least one processor is configured, individually or in any combination, to send an indication to the network node of the MDT measurement set performed based on the second subscriber identity, based at least in part on the information stored in the at least one memory.

[0010] In another aspect of this disclosure, methods, computer-readable media, and apparatuses are provided at a network entity. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to transmit MDT configuration associated with a first subscriber identity associated with the UE for a UE. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to receive from the UE an indication of a set of MDT measurements based on a second subscriber identity associated with the UE.

[0011] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0012] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0013] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0014] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0015] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0016] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0017] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0018] Figure 4 This is a diagram illustrating an example of positioning based on positioning signal measurements.

[0019] Figure 5 This is a diagram illustrating an example of multiple UEs configured to perform Minimum Drive Test (MDT).

[0020] Figure 6 This is a diagram illustrating example communication between a network entity and a UE.

[0021] Figure 7This is a diagram illustrating example communication between a network entity and a UE having a first subscriber identification component and a second subscriber identification component.

[0022] Figure 8 This is a flowchart of a wireless communication method.

[0023] Figure 9 This is a flowchart of a wireless communication method.

[0024] Figure 10 This is a flowchart of a wireless communication method.

[0025] Figure 11 This is a flowchart of a wireless communication method.

[0026] Figure 12 This is a flowchart of a wireless communication method.

[0027] Figure 13 This is a flowchart of a wireless communication method.

[0028] Figure 14 These are illustrations of examples of hardware implementations of example devices and / or network entities.

[0029] Figure 15 This is a diagram illustrating an example of the hardware implementation of a sample network entity. Detailed Implementation

[0030] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0031] Networks can configure minimum drive tests (MDTs) for a set of UEs in a geographic area based on various factors associated with network optimization. UEs configured for MDT measurements are assumed to perform measurements and report them to the network within time windows and time intervals. However, in some scenarios, UEs configured using MDT may fail to perform MDT measurements, and when the network is about to use MDT measurements, it may be unable to obtain reports from those UEs, leading to inefficiencies at the network level. The aspects presented in this paper enable UEs to notify the network that they cannot perform MDT measurements based on their configured MDT settings. This allows the network to select other UEs to perform MDT measurements or operate in other ways based on this information, rather than blindly waiting for potentially unavailable MDT measurements.

[0032] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0033] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0034] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0035] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0036] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0037] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0038] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0039] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0040] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0041] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0042] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0043] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0044] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 111, via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0045] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0046] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and may be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0047] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each direction, the total number of carriers used for transmission can be up to [number missing]. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number] carriers. YA spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0048] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0049] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0051] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0052] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0053] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0054] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0055] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that processes signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0056] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0057] Refer again Figure 1 In some aspects, UE 104 may include MDT component 198. In some aspects, MDT component 198 may be configured to receive MDT configuration from a network node, wherein the MDT configuration configures the UE to perform an MDT measurement set for a threshold time period after receiving the MDT configuration. In some aspects, MDT component 198 may be configured to send an indication to the network node that the UE cannot perform the MDT measurement set for the threshold time period. In some aspects, MDT component 198 may be configured to receive an MDT configuration associated with a first subscriber identity from the network node. In some aspects, MDT component 198 may be configured to perform an MDT measurement set based on a second subscriber identity based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity for the threshold time period, (2) signal fluctuation reaches a threshold, or (3) the UE is in a mobility state or in a specific location. In some aspects, MDT component 198 may be configured to send an indication to the network node of the MDT measurement set performed based on the second subscriber identity.

[0058] In some aspects, base station 102 may include MDT component 199. In some aspects, MDT component 199 may be configured to transmit MDT configuration to a UE, wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time period after receiving the MDT configuration. In some aspects, MDT component 199 may be configured to receive from the UE an indication that the UE cannot perform the MDT measurement set within the threshold time period. In some aspects, MDT component 199 may be configured to transmit MDT configuration associated with a first subscriber identity associated with the UE to the UE. In some aspects, MDT component 199 may be configured to receive from the UE an indication of an MDT measurement set based on a second subscriber identity associated with the UE.

[0059] While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0060] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be included in, or may be a component of: a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. Alternatively, a network node may be a base station or a network entity. Furthermore, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In other aspects of this example, the first network node, the second network node, and the third network node may differ from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a wider example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where the UE is configured to receive information from the base station and the first network node is configured to receive information from the second network node, the first network node may refer to the first UE configured to receive information, the first base station, the first device, the first equipment, the first computing system, a first set of one or more components or a first processing entity, etc.; and the second network node may refer to the second UE, the second base station, the second device, the second equipment, the second computing system, a second set of one or more components or a second processing entity, etc.

[0061] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0062] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured using slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured using slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured using any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured using the slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0063] Figures 2A to 2DThe frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0064]

[0065] Table 1: Parameter Set, SCS, and CP

[0066] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For the extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols per slot and 2 slots per subframe. µ One time slot. The subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0067] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0068] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0069] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 coherent REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0070] like Figure 2CAs illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0071] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0072] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0073] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from channel estimator 374 are used to determine the decoding and modulation scheme, as well as for spatial processing. The channel estimates can be derived from a reference signal and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0074] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0075] The controller / processor 359 may be associated with at least one memory 360 storing program code and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0076] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0077] The TX processor 368 can use the reference signal transmitted from the base station 310 or the channel estimate derived from feedback by the channel estimator 358 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0078] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0079] The controller / processor 375 may be associated with at least one memory 376 storing program code and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0080] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to combine Figure 1 The MDT component 198 is used to perform various aspects.

[0081] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to combine Figure 1 The MDT component 199 is used to perform various aspects.

[0082] Figure 4 Figure 400 illustrates an example of positioning based on location signal measurements. The location signal can be any reference signal that can be measured to calculate the positioning or location attributes of a wireless device, such as a Positioning Reference Signal (PRS), Sounding Reference Signal (SRS), Channel State Information (CSI) Reference Signal (CSI-RS), or Synchronization and Signal Block (SSB). Wireless device 402 can be a base station (such as a TRP), or a UE with a known location / position (such as a Positioning Reference Unit (PRU)), or a UE with a high-accuracy sensor (e.g., a GNSS sensor or GPS sensor) that can identify the UE's location. Wireless device 406 can be a base station or a UE with a known location / position. Wireless device 404 can be a UE or TRP configured to perform positioning to collect data (e.g., collect data to train an artificial intelligence machine learning (AI / ML or AIML) model, test the location signal strength, or test the location noise attributes in an area). Wireless device 404 can be at time T... SRS_TX Send UL-SRS 412, and at time T PRS_RX Receives DL Positioning Reference Signal (PRS) (DL-PRS) 410. Wireless device 406 can receive the DL positioning reference signal (PRS) at time T. SRS_RX Receive UL-SRS 412, and at time T PRS_TX Send DL-PRS 410. Wireless device 404 may receive DL-PRS 410 before sending UL-SRS 412, or may send UL-SRS 412 before receiving DL-PRS 410. In both cases, the location server (e.g., location server 168, LMF 166) or wireless device 404 may base its communication on ||T. SRS_RX - T PRS_TX | - |T SRS_TX -T PRS_RX || to determine RTT 414. Therefore, multi-RTT positioning can utilize the UE Rx-Tx time difference measurement (i.e., |T) of downlink signals received from multiple radio devices 402, 406 and measured by radio device 404. SRS_TX - T PRS_RX|) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement of the uplink signal transmitted from wireless device 404 at multiple wireless devices 402, 406 (i.e., |T) SRS_RX - T PRS_TX |) and UL-SRS-RSRP. Wireless device 404 can use auxiliary data received from the location server to measure the UE Rx-Tx time difference (and optionally, the DL-PRS-RSRP of the received signal), and wireless devices 402 and 406 use auxiliary data received from the location server to measure the gNB Rx-Tx time difference (and optionally, the UL-SRS-RSRP of the received signal). The measurements can be used at the location server or wireless device 404 to determine the RTT. The RTT can be used to estimate the location of wireless device 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0083] DL-AoD positioning can utilize the measured DL-PRS-RSRP of downlink signals received at wireless device 404 from multiple wireless devices 402, 406. Wireless device 404 can use auxiliary data received from a positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurement, together with the azimuth departure (A-AoD), zenith departure (Z-AoD), and / or other configuration information, can be used to locate wireless device 404 relative to neighboring wireless devices 402, 406.

[0084] DL-TDOA positioning can utilize the DL Reference Signal Time Difference (RSTD) (and optionally, DL-PRS-RSRP) of downlink signals received at wireless device 404 from multiple wireless devices 402, 406. Wireless device 404 can use auxiliary data received from a positioning server to measure the DL RSTD (and optionally, DL-PRS-RSRP) of the received signals, and the resulting measurement, along with other configuration information, can be used to locate the position / location of wireless device 404 relative to neighboring wireless devices 402, 406.

[0085] UL-TDOA positioning can utilize the UL relative time of arrival (RTOA) (and optionally, UL-SRS-RSRP) of the uplink signal transmitted from wireless device 404 at multiple wireless devices 402, 406. Wireless devices 402, 406 can use auxiliary data received from a positioning server to measure the UL-RTOA (and optionally, UL-SRS-RSRP) of the received signal, and the resulting measurement can be used, along with other configuration information, to estimate the location of wireless device 404.

[0086] UL-AoA positioning utilizes the azimuth angle (A-AoA) and zenith angle (Z-AoA) of the uplink signal transmitted from wireless device 404, measured at multiple wireless devices 402 and 406. Wireless devices 402 and 406 can use auxiliary data received from a positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurements, along with other configuration information, can be used to estimate the position of wireless device 404.

[0087] Additional positioning methods can be used to estimate the location of the wireless device 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various technologies can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / improve measurements, and / or replace / provide missing information.

[0088] Figure 5Figure 500 illustrates an example of multiple UEs configured to perform MDT. MDT is a technique in which a radio device can perform specific measurements (e.g., Reference Received Power (RSRP), Reference Signal Strength Indicator (RSSI), Signal-to-Interference and Noise Ratio (SINR), Reference Received Quality (RSRQ), etc.) and report specific failures associated with those measurements (e.g., Radio Link Failure (RLF), Secondary Cell Group (SCG) failure, Random Access Channel (RACH) failure). In some aspects, network operators can equip vehicles with radio devices configured to perform such measurements and can drive the vehicles to different locations within the area of ​​the base station / TRP to identify locations where radio signal coverage may be weaker than at other locations. In some aspects, the network can configure multiple UEs to perform such specific measurements and report such specific failures. In other words, the network can configure multiple UEs (such as UE 506, UE 508, and / or UE 510) to perform one or more MDTs. The network can configure the UEs via radio transmission. For example, network node 502 may transmit MDT configuration via signal set 503, and / or network node 504 may transmit MDT configuration via signal set 505. Network node 502 may be a base station or a TRP. Network node 504 may be a base station or a TRP. The network may configure the UE to report the results of the MDT with associated parameters and the location calculated via a positioning method (e.g., Wireless Wide Area Network (WWAN), Wireless Local Area Network (WLAN), Global Navigation Satellite System (GNSS), 5G, LTE). For example, UE 506 may report the results of the MDT via signal set 507, UE 508 may report the results of the MDT via signal set 509, and / or UE 510 may report the results of the MDT via signal set 511 based on specific triggers (such as RLF, SCG failure, RACH failure, etc.), and these results may be measurement logs. The signal sets may include information about the results of the MDT (e.g., indications) and may be transmitted via Media Access Control (MAC) control element (MAC-CE) or UE Assistance Information (UAI). In some respects, the result of an MDT may be referred to as an "MDT measurement," and the MDT measurement may be linked to information about the UE's location at the time of triggering (e.g., associated with parameters indicating that information). By including location information, the network can correlate the UE's calculated location with the MDT measurement for better network planning and to tune one or more network configurations to provide improved network coverage and performance. In some respects, the MDT measurement may be linked to at least one timestamp associated with the measurement. In some respects, the MDT measurement may be performed based on a specific subscriber identity.As used herein, the term “subscriber identity” or “SUB” may refer to an identity associated with a data subscription service used by a UE, enabling a network service provider to charge the UE and provide data connectivity services to the UE. For example, a subscriber identity may be associated with a subscriber identity module (SIM), an embedded SIM, or a different type of identity. As used herein, the term “MDT configuration” (which may also be referred to as “recorded measurement configuration”) may refer to a configuration that configures one or more UEs to perform MDT measurements and may include parameters such as: (1) a threshold time during which the UE may perform the measurement before receiving the MDT configuration, (2) a threshold time during which the UE may report the measurement before receiving the MDT configuration, (3) information about the specific measurement to be performed, such as the measurement type, information about the RS used for the measurement (e.g., time or frequency, RS type, etc.), triggers for the MDT measurement (e.g., location information associated with the MDT, events associated with the MDT, such as RLF, SCG failure, RACH failure, etc.), and / or (4) a list of adjacent RATs and frequencies for MDT reporting or other MDT configuration parameters.

[0089] While multiple UEs can be configured to perform and report MDT results, some UEs may have different mobility conditions and scenarios than others. For example, UE 506 may camp for extended periods (e.g., 30 minutes) to ensure that MDT measurements are appropriately correlated with the location calculated by UE 506. In other words, the location reported by UE 506 can reflect the correct / accurate location at the occurrence of the configured events of interest (e.g., RLF, SCG failure, RACH). In another example, UE 508 may travel at a moderate speed, while UE 510 may travel at a higher speed. When such UEs report MDT measurements, the location obtained by initiating a session after the configured event may not accurately reflect the location where the reported event occurred. This mismatch between location and the configured event can cause the network to make incorrect decisions, resulting in suboptimal configuration. UE 510 might take a period of time (e.g., a fraction of a second) to obtain an accurate location, which could translate into a significant location error mismatch. While mismatches for UE 508 may not cause problems because UE 508 travels at a moderate speed, mismatches for UE 510 could lead to configurations that cause severe performance degradation. For example, the network might incorrectly boost the transmit power it uses, resulting in power consumption, or it might incorrectly report strong signals, leading to coverage holes. Therefore, under certain conditions, a UE might not be in a state where performing MDT measurements would be effective, thus preventing the UE from performing MDT measurements. Furthermore, a UE might be unable to perform MDT measurements due to a lack of time, resources, or connectivity. In some aspects, even if a UE is able to perform some MDT measurements, it might fail to perform the configured MDT measurements within a threshold time, potentially preventing the UE from performing MDT measurements at all. As used herein, the term “UE cannot perform MDT measurement” refers to a situation where the UE is unable to perform or report MDT measurement based on MDT configuration for various reasons, such as (1) the UE does not have the time, resources (such as low battery, overheating, the UE determining not to perform MDT measurement to prevent power consumption due to MDT measurement, or other UE factors that the UE may determine not to perform MDT measurement) or connectivity to perform or report MDT measurement within a threshold time, (2) the UE is in a state in which MDT measurement may be invalid (such as a mobility state), (3) the UE is in a location in which MDT measurement may be invalid, and / or (4) the UE cannot perform or report MDT measurement for a specific subscriber identity, etc.

[0090] Furthermore, depending on whether the UE will enter an idle state to perform MDT measurements and send the results, reporting of MDT measurements may be delayed (and this delay is more likely to occur, especially when the device is in a mobile state). For example, the UE can enter an idle state to perform MDT measurements and send the results, allowing the UE to maintain the connection for ongoing data. There may also be locations where RS fluctuations may be high (e.g., other events in the cell or area used for serving neighbors). In different scenarios, the UE can use alternative methods to perform and report MDT measurements to collect MDT reports (e.g., regarding a second subscriber identity) without affecting currently ongoing activities on the first subscriber identity.

[0091] As previously described, a network can configure an MDT (Multi-Target Measurement) for a set of UEs in a geographic area based on various factors associated with network optimization, and UEs configured for MDT measurements can be assumed to perform measurements and report them to the network within time windows and time intervals. However, in some scenarios, UEs configured using MDT may fail to perform MDT measurements, and when the network is to use MDT measurements, it may be unable to obtain reports from those UEs, resulting in inefficiency at the network level. The aspects presented herein enable UEs to notify the network that they cannot perform MDT measurements based on their configured MDT settings, allowing the network to select other UEs to perform MDT measurements or operate in other ways based on this information, rather than blindly waiting for potentially unavailable MDT measurements. The aspects presented herein enable intelligent coordination between the UE and the network for recorded measurements, ensuring timely reporting of optimized MDT measurements in the area with informed / informed selection of UEs for MDT, achieving better network planning to avoid delays in MDT reporting, saving network resources and time, accelerating MDT measurements through the use of secondary subscriber identities, and enabling more timely reporting of MDT measurements.

[0092] In some aspects, the UE can announce support for MDT. For example, UE 510 can send a set of signals 511 including UE capabilities. UE capabilities can indicate that UE 510 is capable of performing MDT. In some aspects, UE capabilities can indicate that UE 510 is capable of performing MDT under a second subscriber identity in various situations. In some aspects, based on the fact that UE capabilities can indicate that UE 510 is capable of performing MDT under a second subscriber identity in various situations, the network may be more likely (e.g., by assigning higher weights) to select UE 510 to perform MDT measurements. Network node 504 can receive the set of signals 511. Network node 504 can configure an RSRP threshold or an RSSI threshold for UE 510. Network node 504 can send a set of signals 505 including the configured thresholds. For example, signal set 505 can include an MDT configuration that includes an indicator of the configured thresholds. UE 510 can receive the configured thresholds. UE 510 can measure pilot signals (e.g., SSB, PRS) from the TRP, such as signal set 503 from network node 502 or signal set 505 from network node 504. If UE 510 performs a measurement less than or equal to a threshold (e.g., RSRP < 0.05), x or RSRP x If so, UE 510 can perform location positioning more frequently than before (for example, UE 510 can perform location positioning every 5 seconds instead of every 30 seconds).

[0093] In some respects, UE 510 may be unable to perform MDT measurements for various reasons, such as (1) the UE cannot perform the set of MDT measurements based on a first subscriber identity within a threshold time period, (2) signal fluctuations reach a threshold, or (3) the UE is in a mobility state or in a specific location (e.g., within area 520, which the network or the UE may know is unsuitable for MDT measurements). In some respects, UE 510 may alternatively perform the set of MDT measurements based on a second subscriber identity. In some respects, UE 510 may send an indication to network node 504 or network node 502 via signal 511, via MAC-CE or UAI, to indicate that UE 510 cannot perform MDT measurements based on the MDT configuration. In some respects, UE 510 may use UAI to indicate to the network that UE 510 cannot perform MDT measurements. In some respects, UE 510 may use MAC-CE to indicate to the network that UE 510 cannot perform MDT measurements. In some respects, the UE may include indications in the form of bitmasks or flags in the MAC-CE or UAI (e.g., a single bit indicating true or false, where a true flag indicates that the UE is able to perform the MDT measurement set within a threshold time, or a false flag indicates that the UE is not able to perform the MDT measurement set within a threshold time).

[0094] In some respects, an example UAI, including an indication that the UE cannot perform the MDT measurement set within a threshold time, can be used to indicate UE auxiliary information to the network. UEAssistanceInformation The message may be associated with Signaling Radio Bearer (SRB) 1 or SRB3, with the RLC Serving Access Point (SAP) protocol in Acknowledgment Mode (AM), and with the Dedicated Control Channel (DCCH). This includes indications that the UE cannot perform the MDT measurement set within a threshold time. UEAssistanceInformation The message format can be: UEAssistanceInformation information

[0095] The Boolean flag for the measurement status recorded by the UE can be a single bit indicating true or false, where a true flag indicates that the UE can perform the MDT measurement set within a threshold time, or a false flag indicates that the UE cannot perform the MDT measurement set within a threshold time.

[0096] In some respects, UE 510 may be unable to perform the configured MDT measurement set on a first subscriber identity, which may be the currently active subscriber identity. For example, UE 510 may be unable to perform the configured MDT measurement set on the first subscriber identity because (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within a threshold time, (2) signal fluctuations reach a threshold, or (3) the UE is in a mobility state or in a specific location. In some respects, UE 510 may alternatively perform the MDT measurement set based on a second subscriber identity and transmit the MDT measurement set to the network via signal set 511. In some respects, the triggering of performing MDT measurements on the second subscriber identity may be time-based, urgency-based (e.g., as indicated by the network in the MDT configuration), or signal measurement-based (e.g., RSRP / RSRQ / RSSI / SINR fluctuations exceeding a threshold on the serving cell or neighboring cells). In some respects, the triggering of performing MDT measurements may be UE-based configuration without network signaling. In some respects, the triggering of performing MDT measurements may be UE-based configuration based on network configuration.

[0097] In some respects, the first condition for triggering the use of a second subscriber identity to perform MDT measurements can be based on the time (t1) that has elapsed since the UE was in a connected state after receiving the MDT configuration. When the elapsed time (t1) is longer than the threshold time configured for recording measurements to begin after receiving the MDT configuration, the UE can use the second subscriber identity to perform MDT measurements.

[0098] In some respects, the second condition for triggering the use of a second subscriber identity to perform MDT measurements may be based on (1) the UE being in a mobility state (e.g., based on information from one or more sensors) and / or (2) signal fluctuations exceeding a threshold (e.g., RSRP / RSRQ / RSSI / SINR fluctuations exceeding a threshold).

[0099] In some aspects, the third condition used to trigger the execution of MDT measurements using a second subscriber identity can be based on a timer (T) from the network in the MDT configuration, which can indicate the maximum allowed time elapsed before the start of the MDT measurement or the maximum allowed time elapsed for an MDT report readiness indication to the network. For example, a portion of the MDT configuration may include the following format: Recorded measurement configuration - r18 { … loggedmeasStartTime or loggedmeasreportTime T The location used to trigger MDT (which can be a sensitive location identified by NW for MDT reporting - as a new deployment or other local factor) } The parameter loggedmeasStartTime or loggedmeasreportTime T can indicate the maximum allowed time elapsed before the start of an MDT measurement or the maximum allowed time elapsed for an MDT report to be ready for delivery to the network.

[0100] In some aspects, the fourth condition for triggering the execution of MDT measurements using a second subscriber identity can be based on the UE's location within a specific area configured based on network signaling or configured in the absence of network signaling. For example, if the UE is in a specific area, the UE can perform MDT measurements based on a second subscriber identity. In some aspects, the specific area can be configured by the UE's manufacturer. In one embodiment, the aspects presented herein can include UE-based improvements to MDT measurements. First, the UE can indicate the MDT measurement status, for example, that the requested measurement cannot be performed due to UE-side reasons (e.g., power, bandwidth, etc.). Second, the UE can perform measurements on a second subscriber identity, for example, not in an idle state. Third, the network can indicate a maximum time delay before the measurement begins or otherwise notify the network.

[0101] Figure 6 Figure 600 illustrates an example communication between network entity 604 and UE 602.

[0102] At 610, UE 602 can receive MDT configuration from network entity 604.

[0103] At 620, UE 602 can identify that the UE cannot perform the MDT measurement set within a threshold time based on the MDT configuration.

[0104] At 630, UE 602 may send an indication to network entity 604 that the UE cannot perform the MDT measurement set within a threshold time. In some aspects, UE 602 may send the indication to network entity 604 based on an identifier. In some aspects, to send the indication that the UE cannot perform the MDT measurement set within the threshold time, UE 602 may send the indication via MAC-CE. In some aspects, MAC-CE includes a single bit for indication, wherein the single bit represents a true flag indicating that the UE can perform the MDT measurement set within the threshold time or a false flag indicating that the UE cannot perform the MDT measurement set within the threshold time. In some aspects, MAC-CE includes a bitmask for indication. In some aspects, to send the indication that the UE cannot perform the MDT measurement set within the threshold time, UE 602 may send the indication via UAI. In some respects, the UAI includes a single bit for indication, wherein the single bit represents a true flag indicating that the UE is able to perform the MDT measurement set within a threshold time or a false flag indicating that the UE cannot perform the MDT measurement set within a threshold time.

[0105] Figure 7 Figure 700 illustrates an example communication between network entity 704 and UE 702 having a first subscriber identification component 701 and a second subscriber identification component 703.

[0106] At 710, UE 702 can receive MDT configuration from network entity 704.

[0107] At 720, UE 702 may determine one or more of the following: (1) the UE cannot perform the MDT measurement set based on the first subscriber identity associated with the first subscriber identification component 701 within the threshold time, (2) the signal fluctuation reaches the threshold, or (3) the UE is in a mobility state or in a specific location.

[0108] At 730, based on determination, UE 702 can perform MDT measurement set based on the second subscriber identity associated with the second subscriber identity component 703.

[0109] At 740, UE 702 can send an instruction to network entity 704 for the set of MDT measurements performed based on the second subscriber identity.

[0110] In some aspects, the MDT configuration includes a threshold time. In some aspects, to send an indication of the executed MDT measurement set, the UE may send the indication via MAC-CE or UAI. In some aspects, the threshold time corresponds to a first maximum time before starting the execution of the MDT measurement set or a second maximum time before reporting the MDT measurement set. In some aspects, to execute the MDT measurement set based on a second subscriber identity, UE 702 may execute the MDT measurement set based on the second subscriber identity within the threshold time if the UE cannot execute the MDT measurement set based on the first subscriber identity within the threshold time. In some aspects, to execute the MDT measurement set based on the second subscriber identity, UE 702 may execute the MDT measurement set based on the second subscriber identity based on signal fluctuation reaching a threshold, where the threshold corresponds to an RSRP threshold, RSSI threshold, SINR threshold, or RSRQ threshold.

[0111] In some respects, in order to perform an MDT measurement set based on a second subscriber identity, UE 702 may perform an MDT measurement set based on the second subscriber identity, based on the fact that the UE is in a mobility state and based on data from at least one sensor.

[0112] In some respects, in order to perform an MDT measurement set based on a second subscriber identity, UE 702 may perform an MDT measurement set based on a specific location of the UE, wherein the specific location is within a configuration area associated with the second subscriber identity.

[0113] Figure 8 This is a flowchart 800 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, UE 506, UE 508, UE 510, UE 602, UE 702; device 1404).

[0114] At 802, the UE can receive an MDT configuration from a network node, wherein the MDT configuration configures the UE to perform a set of MDT measurements within a threshold time period following the receipt of the MDT configuration. For example, UE 602 can receive an MDT configuration (e.g., 610) from a network node (e.g., 604), wherein the MDT configuration configures the UE to perform a set of MDT measurements within a threshold time period following the receipt of the MDT configuration. In some aspects, 802 can be performed by MDT component 198.

[0115] At 806, the UE may send an indication to the network node that the UE cannot perform the MDT measurement set within the threshold time. For example, UE 602 may send an indication to the network node (e.g., 604) that the UE cannot perform the MDT measurement set within the threshold time (e.g., 630). In some aspects, 806 may be performed by the MDT component 198.

[0116] Figure 9 This is a flowchart 900 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, UE 506, UE 508, UE 510, UE 602, UE 702; device 1404).

[0117] At 902, the UE can receive an MDT configuration from a network node, wherein the MDT configuration configures the UE to perform a set of MDT measurements within a threshold time period following the receipt of the MDT configuration. For example, UE 602 can receive an MDT configuration (e.g., 610) from a network node (e.g., 604), wherein the MDT configuration configures the UE to perform a set of MDT measurements within a threshold time period following the receipt of the MDT configuration. In some aspects, 902 can be performed by MDT component 198.

[0118] At 904, the UE can identify, based on its MDT configuration, that it cannot perform the MDT measurement set within a threshold time period. For example, UE 602 can identify (e.g., at 620) that it cannot perform the MDT measurement set within a threshold time period based on its MDT configuration. In some aspects, 904 can be performed by MDT component 198.

[0119] At 906, the UE may send an indication to the network node that the UE cannot perform the MDT measurement set within a threshold time. For example, UE 602 may send an indication to the network node (e.g., 604) that the UE cannot perform the MDT measurement set within the threshold time (e.g., 630). In some aspects, 906 may be performed by the MDT component 198. In some aspects, to send the indication that the UE cannot perform the MDT measurement set within the threshold time, the UE may send the indication to the network node based on an identifier. In some aspects, to send the indication that the UE cannot perform the MDT measurement set within the threshold time, the UE may send the indication via MAC-CE. In some aspects, MAC-CE includes a single bit for indication, wherein the single bit represents a true flag indicating that the UE can perform the MDT measurement set within the threshold time or a false flag indicating that the UE cannot perform the MDT measurement set within the threshold time. In some aspects, MAC-CE includes a bitmask for indication. In some aspects, in order to send an indication that the UE cannot perform the MDT measurement set within a threshold time, the UE may send the indication via the UAI. In some aspects, the UAI includes a single bit for indication, wherein the single bit represents a true flag indicating that the UE can perform the MDT measurement set within the threshold time or a false flag indicating that the UE cannot perform the MDT measurement set within the threshold time.

[0120] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be performed by network entities (e.g., base station 102, network node 502, network node 504, network entity 604, network entity 704, network entity 1402, network entity 1502).

[0121] At 1002, a network entity can send an MDT configuration to the UE, wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time period following the receipt of the MDT configuration. For example, network entity 604 can send an MDT configuration 610 to the UE 602, wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time period following the receipt of the MDT configuration. In some aspects, 1002 can be performed by MDT component 199.

[0122] At 1006, the network entity can receive from the UE an indication that the UE cannot perform the MDT measurement set within a threshold time. For example, network entity 604 can receive the indication from the UE that the UE cannot perform the MDT measurement set within a threshold time (e.g., 630). In some aspects, 1006 may be performed by the MDT component 199. In some aspects, to receive the indication that the UE cannot perform the MDT measurement set within a threshold time, the network entity may receive the indication via MAC-CE. In some aspects, MAC-CE includes a single bit for indication, wherein the single bit represents a true flag indicating that the UE can perform the MDT measurement set within the threshold time or a false flag indicating that the UE cannot perform the MDT measurement set within the threshold time. In some aspects, MAC-CE includes a bitmask for indication. In some aspects, to receive the indication that the UE cannot perform the MDT measurement set within a threshold time, the network entity may receive the indication via UAI. In some respects, the UAI includes a single bit for indication, wherein the single bit represents a true flag indicating that the UE is able to perform the MDT measurement set within a threshold time or a false flag indicating that the UE cannot perform the MDT measurement set within a threshold time.

[0123] Figure 11 This is a flowchart 1100 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, UE 506, UE 508, UE 510, UE 602, UE 702; device 1404).

[0124] At 1102, the UE can receive the MDT configuration associated with the first subscriber identity from the network node. For example, UE 702 can receive the MDT configuration associated with the first subscriber identity (e.g., 710) from the network node (e.g., 704). In some aspects, 1102 can be performed by the MDT component 198.

[0125] At 1104, the UE may perform an MDT measurement set based on a second subscriber identity based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within a threshold time period, (2) the signal fluctuation reaches a threshold, or (3) the UE is in a mobile state or in a specific location. For example, UE 702 may perform an MDT measurement set based on a second subscriber identity based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within a threshold time period, (2) the signal fluctuation reaches a threshold, or (3) the UE is in a mobile state or in a specific location (e.g., at 730). In some aspects, 1104 may be performed by MDT component 198.

[0126] At 1106, the UE may send an indication to the network node of the set of MDT measurements performed based on the second subscriber identity (e.g., 740). For example, UE 702 may send an indication to the network node (e.g., 704) of the set of MDT measurements performed based on the second subscriber identity (e.g., 740). In some aspects, 1106 may be performed by the MDT component 198.

[0127] Figure 12 This is a flowchart 1200 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, UE 506, UE 508, UE 510, UE 602, UE 702; device 1404).

[0128] At 1202, the UE can receive the MDT configuration associated with the first subscriber identity from the network node. For example, UE 702 can receive the MDT configuration associated with the first subscriber identity (e.g., 710) from the network node (e.g., 704). In some aspects, 1202 can be performed by the MDT component 198.

[0129] At 1204, the UE may perform an MDT measurement set based on a second subscriber identity based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within a threshold time period, (2) the signal fluctuation reaches a threshold, or (3) the UE is in a mobile state or in a specific location. For example, UE 702 may perform an MDT measurement set based on a second subscriber identity based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within a threshold time period, (2) the signal fluctuation reaches a threshold, or (3) the UE is in a mobile state or in a specific location (e.g., at 730). In some aspects, 1204 may be performed by MDT component 198.

[0130] In some aspects, to perform an MDT measurement set based on a second subscriber identity, the UE can perform an MDT measurement set based on the second subscriber identity at 1204A, based on the UE's inability to perform an MDT measurement set based on the first subscriber identity within a threshold time period, and within the threshold time period. In some aspects, to perform an MDT measurement set based on a second subscriber identity, the UE can perform an MDT measurement set based on the second subscriber identity at 1204B, based on signal fluctuations reaching a threshold, where the threshold corresponds to an RSRP threshold, RSSI threshold, SINR threshold, or RSRQ threshold. In some aspects, to perform an MDT measurement set based on a second subscriber identity, the UE can perform an MDT measurement set based on the second subscriber identity at 1204C, based on the UE being in a mobility state and based on data from at least one sensor. In some aspects, to perform an MDT measurement set, the UE can perform an MDT measurement set based on the second subscriber identity at 1204D, based on the UE being in a specific location, where the specific location is within a configuration area associated with the second subscriber identity.

[0131] At 1206, the UE may send an indication to the network node of the set of MDT measurements performed based on the second subscriber identity (e.g., 740). For example, UE 702 may send an indication to the network node (e.g., 704) of the set of MDT measurements performed based on the second subscriber identity (e.g., 740). In some aspects, 1206 may be performed by the MDT component 198.

[0132] In some aspects, the MDT configuration includes a threshold time, and wherein, in order to send an indication of the executed MDT measurement set, the UE may send an indication of the executed MDT measurement set via MAC-CE or UAI. In some aspects, the threshold time corresponds to a first maximum time before the execution of the MDT measurement set begins or a second maximum time before the MDT measurement set is reported.

[0133] Figure 13This is a flowchart 1300 of a wireless communication method. The method can be performed by network entities (e.g., base station 102, network node 502, network node 504, network entity 604, network entity 704, network entity 1402, network entity 1502).

[0134] At 1302, a network entity may send an MDT configuration associated with the first subscriber identity associated with the UE to the UE. For example, network entity 704 may send an MDT configuration associated with the first subscriber identity associated with the UE to the UE (e.g., 710). In some aspects, 1302 may be performed by MDT component 199.

[0135] At 1306, the network entity can receive from the UE an indication of the MDT measurement set based on a second subscriber identity associated with the UE. For example, network entity 704 can receive from the UE an indication of the MDT measurement set based on a second subscriber identity associated with the UE. In some aspects, 1306 can be performed by MDT component 199.

[0136] In some aspects, the MDT measurement set is based on (1) the UE cannot perform the MDT measurement set based on a first subscriber identity within a threshold time period, (2) signal fluctuation reaches a threshold, or (3) the UE is in a mobile state or in a specific location, and the MDT measurement set is based on a second subscriber identity. In some aspects, the MDT configuration includes a threshold time period, and wherein, in order to receive an indication of the performed MDT measurement set, the network entity may receive an indication of the performed MDT measurement set via MAC-CE or UAI. In some aspects, the threshold time period corresponds to a first maximum time before the start of the execution of the MDT measurement set or a second maximum time before the reporting of the MDT measurement set. In some aspects, the MDT measurement set is based on the UE's inability to perform the MDT measurement set based on a first subscriber identity within a threshold time period. In some aspects, the MDT measurement set is based on signal fluctuation reaching a threshold, wherein the threshold corresponds to an RSRP threshold, RSSI threshold, SINR threshold, or RSRQ threshold. In some aspects, the MDT measurement set is based on the UE being in a mobile state and based on data from at least one sensor. In some respects, the MDT measurement set is based on the UE being in a specific location, where the specific location is within a configured area associated with a second subscriber identity.

[0137] Figure 14Figure 1400 illustrates an example of a hardware implementation of device 1404. Device 1404 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1404 may include at least one cellular baseband processor 1424 (also referred to as a modem) coupled to one or more transceivers 1422 (e.g., cellular RF transceivers). Cellular baseband processor 1424 may include at least one on-chip memory 1424'. In some aspects, device 1404 may also include one or more Subscriber Identity Module (SIM) cards 1420 and at least one application processor 1406 coupled to a Secure Digital Card (SD) card 1408 and a screen 1410. Application processor 1406 may include on-chip memory 1406'. In some aspects, device 1404 may also include a Bluetooth module 1412, a WLAN module 1414, an SPS module 1416 (e.g., a GNSS module), one or more sensor modules 1418 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1426, a power supply 1430, and / or a camera 1432. Bluetooth module 1412, WLAN module 1414, and SPS module 1416 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 1412, WLAN module 1414, and SPS module 1416 may include their own dedicated antennas and / or communicate using antenna 1480. Cellular baseband processor 1424 communicates with UE 104 and / or RU associated with network entity 1402 via transceiver 1422 through one or more antennas 1480. Cellular baseband processor 1424 and application processor 1406 may each include computer-readable media / memory 1424', 1406'. Additional memory module 1426 may also be considered computer-readable media / memory. Each computer-readable media / memory 1424', 1406', 1426 may be non-transitory. Cellular baseband processor 1424 and application processor 1406 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by cellular baseband processor 1424 / application processor 1406, the software causes cellular baseband processor 1424 / application processor 1406 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by cellular baseband processor 1424 / application processor 1406 during software execution.Cellular baseband processor 1424 / application processor 1406 may be a component of UE 350 and may include at least one of memory 360 and / or TX processor 368, RX processor 356 and controller / processor 359. In one configuration, device 1404 may be at least one processor chip (modem and / or application) and may include only cellular baseband processor 1424 and / or application processor 1406, while in another configuration, device 1404 may be the entire UE (e.g., see below). Figure 3 The UE 350 includes an additional module of the device 1404.

[0138] As discussed above, MDT component 198 can be configured to receive MDT configuration from a network node, wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time period after receiving the MDT configuration. In some aspects, MDT component 198 can be configured to send an indication to the network node that the UE cannot perform the MDT measurement set within the threshold time period. In some aspects, MDT component 198 can be configured to receive an MDT configuration associated with a first subscriber identity from the network node. In some aspects, MDT component 198 can be configured to perform an MDT measurement set based on a second subscriber identity based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within the threshold time period, (2) signal fluctuation reaches a threshold, or (3) the UE is in a mobility state or at a specific location. In some aspects, MDT component 198 can be configured to send an indication to the network node of an MDT measurement set performed based on the second subscriber identity. MDT component 198 may reside within cellular baseband processor 1424, application processor 1406, or both cellular baseband processor 1424 and application processor 1406. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, apparatus 1404 may include various components configured for various functions. In one configuration, apparatus 1404 (and particularly cellular baseband processor 1424 and / or application processor 1406) may include components for receiving MDT configuration from a network node, wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time after receiving the MDT configuration. In some aspects, apparatus 1404 may include components for sending an indication to the network node that the UE cannot perform the MDT measurement set within the threshold time. In some aspects, apparatus 1404 may include components for identifying, based on MDT configuration, that a UE cannot perform an MDT measurement set within a threshold time period. In some aspects, apparatus 1404 may include components for sending an indication to a network node that a UE cannot perform an MDT measurement set within a threshold time period based on the identification. In some aspects, apparatus 1404 may include components for sending an indication via MAC-CE that a UE cannot perform an MDT measurement set within a threshold time period. In some aspects, apparatus 1404 may include components for sending an indication via UAI that a UE cannot perform an MDT measurement set within a threshold time period. In some aspects, apparatus 1404 may include components for receiving, from a network node, an MDT configuration associated with a first subscriber identity.In some aspects, apparatus 1404 may include components for performing an MDT measurement set based on a second subscriber identity, based on (1) the UE cannot perform an MDT measurement set based on a first subscriber identity within a threshold time period, (2) signal fluctuation reaches a threshold, or (3) the UE is in a mobility state or at a specific location. In some aspects, apparatus 1404 may include components for sending an indication to a network node of the MDT measurement set performed based on the second subscriber identity. In some aspects, apparatus 1404 may include components for sending an indication of the performed MDT measurement set via MAC-CE or UAI. In some aspects, apparatus 1404 may include components for performing an MDT measurement set based on a second subscriber identity within a threshold time period, based on the UE's inability to perform an MDT measurement set based on a first subscriber identity within a threshold time period. In some aspects, apparatus 1404 may include components for performing a set of MDT measurements based on a second subscriber identity, based on signal fluctuations reaching a threshold, wherein the threshold corresponds to a Reference Signal Received Power (RSRP) threshold, a Received Signal Strength Indicator (RSSI) threshold, a Signal-to-Interference and Noise Ratio (SINR) threshold, or a Reference Signal Received Quality (RSRQ) threshold. In some aspects, apparatus 1404 may include components for performing a set of MDT measurements based on a second subscriber identity, based on the UE being in a mobility state and based on data from at least one sensor. In some aspects, apparatus 1404 may include components for performing a set of MDT measurements based on a second subscriber identity, based on the UE being in a specific location, wherein the specific location is within a configuration area associated with the second subscriber identity. These components may be components 198 of apparatus 1404 configured to perform the functions described by these components. As described above, apparatus 1404 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, these components may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions described therein.

[0139] Figure 15Figure 1500 illustrates an example of a hardware implementation of network entity 1502. Network entity 1502 may be a BS, a component of a BS, or implement BS functionality. Network entity 1502 may include at least one of CU 1510, DU 1530, or RU 1540. For example, depending on the layer functionality processed by component 199, network entity 1502 may include: CU 1510; both CU 1510 and DU 1530; each of CU 1510, DU 1530, and RU 1540; DU 1530; both DU 1530 and RU 1540; or RU 1540. CU 1510 may include at least one CU processor 1512. CU processor 1512 may include on-chip memory 1512'. In some aspects, CU 1510 may also include an additional memory module 1514 and a communication interface 1518. CU 1510 communicates with DU 1530 via a midhaul link (such as an F1 interface). DU 1530 may include at least one DU processor 1532. DU processor 1532 may include on-chip memory 1532'. In some aspects, DU 1530 may also include an additional memory module 1534 and a communication interface 1538. DU 1530 communicates with RU 1540 via a fronthaul link. RU 1540 may include at least one RU processor 1542. RU processor 1542 may include on-chip memory 1542'. In some aspects, RU 1540 may also include an additional memory module 1544, one or more transceivers 1546, an antenna 1580, and a communication interface 1548. RU 1540 communicates with UE 104. On-chip memories 1512', 1532', 1542' and additional memory modules 1514, 1534, 1544 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1512, 1532, and 1542 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0140] As discussed above, MDT component 199 can be configured to send an MDT configuration to a UE, wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time period after receiving the MDT configuration. In some aspects, MDT component 199 can be configured to receive from the UE an indication that the UE cannot perform the MDT measurement set within the threshold time period. In some aspects, MDT component 199 can be configured to send an MDT configuration associated with a first subscriber identity associated with the UE to the UE. In some aspects, MDT component 199 can be configured to receive from the UE an indication of an MDT measurement set based on a second subscriber identity associated with the UE. MDT component 199 may be located within one or more processors of one or more of CU 1510, DU 1530, and RU 1540. Component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1502 may include various components configured for various functions. In one configuration, network entity 1502 may include components for transmitting an MDT configuration to a UE, wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time period after receiving the MDT configuration. In some aspects, network entity 1502 may include components for receiving from the UE an indication that the UE cannot perform the MDT measurement set within the threshold time period. In some aspects, network entity 1502 may include components for receiving, via UAI, an indication that the UE cannot perform the MDT measurement set within the threshold time period. In some aspects, network entity 1502 may include components for receiving, via MAC-CE, an indication that the UE cannot perform the MDT measurement set within the threshold time period. In some aspects, network entity 1502 may include components for transmitting an MDT configuration associated with a first subscriber identity associated with the UE to the UE. In some aspects, network entity 1502 may include components for receiving from the UE an indication of an MDT measurement set based on a second subscriber identity associated with the UE. In some aspects, network entity 1502 may include components for transmitting MDT configuration associated with a first subscriber identity associated with the UE. In some aspects, network entity 1502 may include components for receiving from the UE an indication of an MDT measurement set based on a second subscriber identity associated with the UE. In some aspects, network entity 1502 may include components for receiving an indication of the performed MDT measurement set via MAC-CE or UAI. These components may be components 199 of network entity 1502 configured to perform the functions described therein.As described above, network entity 1502 may include TX processor 316, RX processor 370, and controller / processor 375. Therefore, in one configuration, these components may be TX processor 316, RX processor 370, and / or controller / processor 375 configured to perform the functions described therein.

[0141] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0142] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to execute a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices through a set of devices. A device configured to “output” data (such as transmission, signaling, or messaging) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to “receive” data (such as transmission, signaling, or messaging) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data.Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to or will later be known to a person skilled in the art are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., cannot replace the word “component.” Therefore, no claim element will be construed as a functional component unless the element is expressly recited using the phrase “component for…”.

[0143] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise stated otherwise.

[0144] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0145] Aspect 1 is a method for wireless communication performed by a user equipment (UE), the method comprising: receiving a minimized drive test (MDT) configuration from a network node, wherein the MDT configuration configures the UE to perform an MDT measurement set for a threshold time period following the receipt of the MDT configuration; and sending an indication to the network node that the UE cannot perform the MDT measurement set for the threshold time period.

[0146] Aspect 2 is the method according to any one of Aspect 1, the method further comprising: identifying, based on the MDT configuration, that the UE cannot perform the MDT measurement set within the threshold time; wherein sending the indication that the UE cannot perform the MDT measurement set within the threshold time further comprises: sending the indication that the UE cannot perform the MDT measurement set within the threshold time to the network node based on the identification.

[0147] Aspect 3 is the method according to any one of Aspect 1, wherein sending the indication that the UE cannot perform the MDT measurement set within the threshold time further includes: sending the indication that the UE cannot perform the MDT measurement set within the threshold time via a Media Access Control (MAC) control element (MAC-CE).

[0148] Aspect 4 is the method according to aspect 3, wherein the MAC-CE includes a single bit for the indication, wherein the single bit represents a true flag indicating that the UE is capable of performing the MDT measurement set within the threshold time or a false flag indicating that the UE is not capable of performing the MDT measurement set within the threshold time.

[0149] Aspect 5 is the method according to aspect 3, wherein the MAC-CE includes a bitmask for the indication.

[0150] Aspect 6 is the method according to any one of Aspects 1 to 2, wherein sending the indication that the UE cannot perform the MDT measurement set within the threshold time further includes: sending the indication that the UE cannot perform the MDT measurement set within the threshold time via UE Assist Information (UAI).

[0151] Aspect 7 is the method according to aspect 6, wherein the UAI includes a single bit for the indication, wherein the single bit represents a true flag indicating that the UE is capable of performing the MDT measurement set within the threshold time or a false flag indicating that the UE is not capable of performing the MDT measurement set within the threshold time.

[0152] Aspect 8 is a method according to any one of Aspects 1 to 7, wherein transmitting the indication that the UE cannot perform the MDT measurement set within the threshold time further comprises: transmitting the indication that the UE cannot perform the MDT measurement set within the threshold time via at least one of a transceiver or an antenna.

[0153] Aspect 9 is a method for wireless communication performed by a network entity, the method comprising: transmitting a Minimum Drive Test (MDT) configuration to a User Equipment (UE), wherein the MDT configuration configures the UE to perform an MDT measurement set within a threshold time period following receipt of the MDT configuration; and receiving from the UE an indication that the UE cannot perform the MDT measurement set within the threshold time period.

[0154] Aspect 10 is the method according to aspect 9, wherein receiving the indication that the UE cannot perform the MDT measurement set within the threshold time further includes: receiving the indication that the UE cannot perform the MDT measurement set within the threshold time via a Media Access Control (MAC) control element (MAC-CE).

[0155] Aspect 11 is the method according to aspect 10, wherein the MAC-CE includes a single bit for the indication, wherein the single bit represents a true flag indicating that the UE is capable of performing the MDT measurement set within the threshold time or a false flag indicating that the UE is not capable of performing the MDT measurement set within the threshold time.

[0156] Aspect 12 is the method according to aspect 10, wherein the MAC-CE includes a bitmask for the indication.

[0157] Aspect 13 is the method according to any one of Aspect 9, wherein receiving the indication that the UE cannot perform the MDT measurement set within the threshold time further comprises: receiving the indication that the UE cannot perform the MDT measurement set within the threshold time via UE Assist Information (UAI).

[0158] Aspect 14 is the method according to aspect 13, wherein the UAI includes a single bit for the indication, wherein the single bit represents a true flag indicating that the UE is capable of performing the MDT measurement set within the threshold time or a false flag indicating that the UE is not capable of performing the MDT measurement set within the threshold time.

[0159] Aspect 15 is the method according to aspects 9 to 14, wherein receiving the indication that the UE cannot perform the MDT measurement set within the threshold time further includes: receiving the indication that the UE cannot perform the MDT measurement set within the threshold time via at least one of a transceiver or an antenna.

[0160] Aspect 16 is a method for wireless communication performed by a user equipment (UE), the method comprising: receiving from a network node a minimized drive test (MDT) configuration associated with a first subscriber identity; performing the MDT measurement set based on a second subscriber identity based on (1) the UE cannot perform an MDT measurement set based on the first subscriber identity within a threshold time, (2) signal fluctuation reaches a threshold, or (3) the UE is in a mobility state or in a specific location; and sending to the network node an indication of the MDT measurement set performed based on the second subscriber identity.

[0161] Aspect 17 is the method according to aspect 16, wherein the MDT configuration includes the threshold time, and wherein sending the indication for the executed MDT measurement set further includes: sending the indication for the executed MDT measurement set via a Media Access Control (MAC) Control Element (MAC-CE) or UE Assistance Information (UAI).

[0162] Aspect 18 is the method according to aspect 17, wherein the threshold time corresponds to a first maximum time before the execution of the MDT measurement set or a second maximum time before the reporting of the MDT measurement set.

[0163] Aspect 19 is a method according to any one of Aspects 16 to 18, wherein performing the MDT measurement set based on the second subscriber identity further includes: performing the MDT measurement set based on the first subscriber identity based on the UE being unable to perform the MDT measurement set based on the second subscriber identity within the threshold time period.

[0164] Aspect 20 is a method according to any one of aspects 16 to 19, wherein performing the MDT measurement set based on the second subscriber identity further includes: performing the MDT measurement set based on the second subscriber identity based on the signal fluctuation reaching the threshold, wherein the threshold corresponds to a reference signal received power (RSRP) threshold, a received signal strength indicator (RSSI) threshold, a signal-to-interference and noise ratio (SINR) threshold, or a reference signal received quality (RSRQ) threshold.

[0165] Aspect 21 is a method according to any one of aspects 16 to 20, wherein performing the MDT measurement set based on the second subscriber identity further includes: performing the MDT measurement set based on the second subscriber identity based on the UE being in the mobility state and based on data from at least one sensor.

[0166] Aspect 22 is a method according to any one of aspects 16 to 21, wherein performing the MDT measurement set further comprises: performing the MDT measurement set based on the second subscriber identity based on the UE being in the specific location, wherein the specific location is within a configuration area associated with the second subscriber identity.

[0167] Aspect 23 is a method for wireless communication performed by a network entity, the method comprising: transmitting a minimized road test (MDT) configuration associated with a first subscriber identity associated with the user equipment (UE); and receiving from the UE an indication of an MDT measurement set based on a second subscriber identity associated with the UE.

[0168] Aspect 24 is the method according to aspect 23, wherein the MDT measurement set is based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within a threshold time, (2) the signal fluctuation reaches a threshold, or (3) the UE is in a mobility state or in a specific location, and the MDT measurement set is based on the second subscriber identity.

[0169] Aspect 25 is the method according to aspect 24, wherein the MDT configuration includes the threshold time, and wherein receiving the indication for the executed MDT measurement set further includes receiving the indication for the executed MDT measurement set via a Media Access Control (MAC) Control Element (MAC-CE) or UE Assistance Information (UAI).

[0170] Aspect 26 is the method according to aspect 25, wherein the threshold time corresponds to a first maximum time before the execution of the MDT measurement set or a second maximum time before the reporting of the MDT measurement set.

[0171] Aspect 27 is a method according to any one of Aspects 24 to 26, wherein the MDT measurement set is based on the fact that the UE cannot perform the MDT measurement set based on the first subscriber identity within the threshold time period.

[0172] Aspect 28 is a method according to any one of Aspects 24 to 27, wherein the MDT measurement set is based on the signal fluctuation reaching the threshold, wherein the threshold corresponds to a reference signal received power (RSRP) threshold, a received signal strength indicator (RSSI) threshold, a signal-to-interference and noise ratio (SINR) threshold, or a reference signal received quality (RSRQ) threshold.

[0173] Aspect 29 is a method according to any one of aspects 24 to 28, wherein the MDT measurement set is based on the UE being in the mobility state and based on data from at least one sensor.

[0174] Aspect 30 is the method according to any one of Aspects 24 to 29, wherein the MDT measurement set is based on the UE being in the specific location, wherein the specific location is within a configuration area associated with the second subscriber identity.

[0175] Aspect 31 is an apparatus for wireless communication at a wireless device, the apparatus including at least one memory and at least one processor, the at least one processor being coupled to the at least one memory and being based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in combination to implement any one of aspects 1 to 30.

[0176] Aspect 31 is the apparatus according to aspect 30, the apparatus further comprising one or more transceivers or one or more antennas coupled to the at least one processor.

[0177] Aspect 32 is an apparatus for wireless communication at a wireless device, the apparatus including components for implementing any one of aspects 1 to 30.

[0178] Aspect 33 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 30.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured, individually or in any combination, based at least in part on stored information stored in the at least one memory, to cause the UE to: Receive a Minimum Drive Test (MDT) configuration from a network node, wherein the MDT configuration configures the UE to perform a set of MDT measurements within a threshold time period following the receipt of the MDT configuration; and Send an indication to the network node that the UE cannot perform the MDT measurement set within the threshold time.

2. The apparatus of claim 1, wherein the at least one processor is configured, individually or in any combination, to cause the UE to: Based on the MDT configuration, identify that the UE cannot perform the MDT measurement set within the threshold time; In order to send the indication that the UE cannot perform the MDT measurement set within the threshold time, the at least one processor is configured individually or in any combination to cause the UE to send the indication to the network node based on the identifier that the UE cannot perform the MDT measurement set within the threshold time.

3. The apparatus of claim 1, wherein, in order to send the indication that the UE cannot perform the MDT measurement set within the threshold time, the at least one processor is configured individually or in any combination to cause the UE to: The indication that the UE cannot perform the MDT measurement set within the threshold time is sent via a Media Access Control (MAC) control element (MAC-CE).

4. The apparatus of claim 3, wherein the MAC-CE includes a single bit for the indication, wherein the single bit represents a true flag indicating that the UE is capable of performing the MDT measurement set within the threshold time or a false flag indicating that the UE is not capable of performing the MDT measurement set within the threshold time.

5. The apparatus of claim 3, wherein the MAC-CE includes a bitmask for the indication.

6. The apparatus of claim 1, wherein, in order to send the indication that the UE cannot perform the MDT measurement set within the threshold time, the at least one processor is configured individually or in any combination to cause the UE to: The indication that the UE cannot perform the MDT measurement set within the threshold time is sent via UE Assist Information (UAI).

7. The apparatus of claim 6, wherein the UAI includes a single bit for the indication, wherein the single bit represents a true flag indicating that the UE is capable of performing the MDT measurement set within the threshold time or a false flag indicating that the UE is not capable of performing the MDT measurement set within the threshold time.

8. The apparatus of claim 1, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to transmit the indication that the UE cannot perform the MDT measurement set within the threshold time, the at least one processor is configured individually or in any combination to cause the UE to transmit the indication that the UE cannot perform the MDT measurement set within the threshold time via the transceiver or the antenna.

9. An apparatus for wireless communication at a network entity, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and based at least in part on information stored in the at least one memory, the at least one processor is configured individually or in any combination to cause the network entity to: Send a Minimum Drive Test (MDT) configuration to the User Equipment (UE), wherein the MDT configuration configures the UE to perform a set of MDT measurements within a threshold time period following receipt of the MDT configuration; and The UE receives an indication that it cannot perform the MDT measurement set within the threshold time.

10. The apparatus of claim 9, wherein, in order to receive the indication that the UE cannot perform the MDT measurement set within the threshold time, the at least one processor is configured individually or in any combination to cause the network entity to: The indication that the UE cannot perform the MDT measurement set within the threshold time is received via a Media Access Control (MAC) control element (MAC-CE).

11. The apparatus of claim 10, wherein the MAC-CE includes a single bit for the indication, wherein the single bit represents a true flag indicating that the UE is capable of performing the MDT measurement set within the threshold time or a false flag indicating that the UE is not capable of performing the MDT measurement set within the threshold time.

12. The apparatus of claim 10, wherein the MAC-CE includes a bitmask for the indication.

13. The apparatus of claim 9, wherein, in order to receive the indication that the UE cannot perform the MDT measurement set within the threshold time, the at least one processor is configured individually or in any combination to cause the network entity to: The indication that the UE cannot perform the MDT measurement set within the threshold time is received via UE Assist Information (UAI).

14. The apparatus of claim 13, wherein the UAI includes a single bit for the indication, wherein the single bit represents a true flag indicating that the UE is capable of performing the MDT measurement set within the threshold time or a false flag indicating that the UE is not capable of performing the MDT measurement set within the threshold time.

15. The apparatus of claim 9, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to receive the indication that the UE cannot perform the MDT measurement set within the threshold time, the at least one processor is configured individually or in any combination to cause the network entity to receive the indication that the UE cannot perform the MDT measurement set within the threshold time via the transceiver or the antenna.

16. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured, individually or in any combination, based at least in part on stored information stored in the at least one memory, to cause the UE to: Receive the Minimum Drive Test (MDT) configuration associated with the first subscriber's identity from the network node; Based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within the threshold time, (2) the signal fluctuation reaches the threshold, or (3) the UE is in a mobile state or in a specific location, the MDT measurement set is performed based on the second subscriber identity. as well as Send an instruction to the network node for the set of MDT measurements performed based on the second subscriber identity.

17. The apparatus of claim 16, wherein the MDT configuration includes the threshold time, and wherein, in order to send the indication to the set of MDT measurements performed, the at least one processor is configured individually or in any combination to cause the UE to: The indication of the set of MDT measurements performed is sent via a Media Access Control (MAC) control element (MAC-CE) or UE Assistance Information (UAI).

18. The apparatus of claim 17, wherein the threshold time corresponds to a first maximum time before the execution of the MDT measurement set begins or a second maximum time before the reporting of the MDT measurement set, and the apparatus further comprises at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to transmit the indication of the executed MDT measurement set, the at least one processor is configured individually or in any combination to cause the UE to transmit the indication of the executed MDT measurement set via at least one of the transceiver or the antenna.

19. The apparatus of claim 16, wherein, in order to perform the MDT measurement set based on the second subscriber identity, the at least one processor is configured individually or in any combination to cause the UE to: The UE cannot perform the MDT measurement set based on the first subscriber identity within the threshold time period, and the MDT measurement set is performed based on the second subscriber identity within the threshold time period.

20. The apparatus of claim 16, wherein, in order to perform the MDT measurement set based on the second subscriber identity, the at least one processor is configured individually or in any combination to cause the UE to: Based on the signal fluctuation reaching the threshold, the MDT measurement set is performed based on the second subscriber identity, wherein the threshold corresponds to the reference signal received power (RSRP) threshold, the received signal strength indicator (RSSI) threshold, the signal-to-interference and noise ratio (SINR) threshold, or the reference signal received quality (RSRQ) threshold.

21. The apparatus of claim 16, wherein, in order to perform the MDT measurement set based on the second subscriber identity, the at least one processor is configured individually or in any combination to cause the UE to: The MDT measurement set is performed based on the UE being in the mobility state and based on data from at least one sensor, and based on the second subscriber identity.

22. The apparatus of claim 16, wherein, in order to perform the MDT measurement set, the at least one processor is configured individually or in any combination to cause the UE to: The MDT measurement set is performed based on the UE being in the specific location and based on the second subscriber identity, wherein the specific location is within a configuration area associated with the second subscriber identity.

23. An apparatus for wireless communication at a network entity, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and based at least in part on information stored in the at least one memory, the at least one processor is configured individually or in any combination to cause the network entity to: Send a minimized road test (MDT) configuration associated with a first subscriber identity associated with the user equipment (UE); and The UE receives an indication of an MDT measurement set based on a second subscriber identity associated with the UE.

24. The apparatus of claim 23, wherein the MDT measurement set is based on (1) the UE cannot perform the MDT measurement set based on the first subscriber identity within a threshold time period, (2) the signal fluctuation reaches a threshold, or (3) the UE is in a mobility state or in a specific location, and the MDT measurement set is based on the second subscriber identity.

25. The apparatus of claim 24, wherein the MDT configuration includes the threshold time, and wherein, in order to receive the indication of the set of MDT measurements performed, the at least one processor is configured individually or in any combination to cause the network entity to: The instruction for the set of MDT measurements performed is received via a Media Access Control (MAC) control element (MAC-CE) or UE Assistance Information (UAI).

26. The apparatus of claim 25, wherein the threshold time corresponds to a first maximum time before the execution of the MDT measurement set begins or a second maximum time before the reporting of the MDT measurement set, and the apparatus further comprises at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to receive the indication of the executed MDT measurement set, the at least one processor is configured individually or in any combination to cause the network entity to receive the indication of the executed MDT measurement set via at least one of the transceiver or the antenna.

27. The apparatus of claim 24, wherein the MDT measurement set is based on the fact that the UE cannot perform the MDT measurement set based on the first subscriber identity within the threshold time period.

28. The apparatus of claim 24, wherein the MDT measurement set is based on the signal fluctuation reaching the threshold, wherein the threshold corresponds to a reference signal received power (RSRP) threshold, a received signal strength indicator (RSSI) threshold, a signal-to-interference and noise ratio (SINR) threshold, or a reference signal received quality (RSRQ) threshold.

29. The apparatus of claim 24, wherein the MDT measurement set is based on the UE being in the mobility state and on data from at least one sensor.

30. The apparatus of claim 24, wherein the MDT measurement set is based on the UE being in the specific location, wherein the specific location is within a configuration area associated with the second subscriber identity.

Images