RAN-Centric Data Collection for Dual Connectivity (DC) / Carrier Aggregation (CA)

Abstract

The present disclosure provides systems, methods, and devices for wireless communication, including computer programs encoded on a computer storage medium. In one aspect of the present disclosure, a method for wireless communication includes: determining, by a user equipment (UE), minimized drive test (MDT) results, and determining, by the UE, early measurement results. The method further includes: transmitting, by the UE, a report including the MDT results, the early measurement results, or a combination thereof. Other aspects and features are also claimed and described.

Description

Technical Field

[0001] Broadly speaking, aspects of the present disclosure relate to wireless communication systems, and more particularly, aspects of the present disclosure relate to (but are not limited to) data collection for dual connectivity (DC) / carrier aggregation (CA). Background Art

[0002] Wireless communication networks have been widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcasting, and so on. These wireless networks can be multi-access networks that support multiple users by sharing available network resources. These networks, which are typically multi-access networks, support communication for multiple users by sharing available network resources.

[0003] A wireless communication network can include multiple base stations or Node Bs that support communication for multiple user equipments (UEs). The UE can communicate with the base station via the downlink and the uplink. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station.

[0004] The base station can send data and control information to the UE on the downlink, and / or receive data and control information from the UE on the uplink. On the downlink, transmissions from the base station may encounter interference caused by transmissions from neighboring base stations or transmissions from other radio frequency (RF) transmitters. On the uplink, transmissions from the UE may encounter interference from uplink transmissions of other UEs communicating with neighboring base stations or other wireless RF transmitters. Such interference can degrade the performance on the downlink and the uplink.

[0005] With the continuous increase in the demand for mobile broadband access, the more UEs accessing long-distance wireless communication networks and the more short-distance wireless systems deployed in the community, the more likely the network is to experience interference and congestion. Continued research and development of wireless technologies can not only meet the growing demand for mobile broadband access, but also enhance and improve the user's mobile communication experience. For example, research and development have helped to advance new radio (NR) technologies that utilize beam management, bandwidth part (BWP), RRC_INACTIVE, multi-radio access technology (RAT) dual connectivity (MR-DC), and dual connectivity (DC) / carrier aggregation (CA). However, combining NR technologies with traditional technologies brings various challenges and obstacles. For illustration purposes, there are challenges in integrating NR technologies into devices and improving device performance with respect to NR technologies. As a specific but non-limiting example, integrating NR technologies into devices has been shown to be related to battery life, throughput, latency, and reliability. Summary of the Invention

[0006] To provide a basic understanding of the technology discussed, some aspects of the present disclosure are summarized below. This summary is not an exhaustive overview of all the expected features of the present disclosure, nor is it intended to identify the key or important elements of all aspects of the present disclosure, or to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a generalized form as a prelude to the detailed description that follows.

[0007] In one aspect of the present disclosure, a method for wireless communication includes: determining, by a user equipment (UE), a minimized drive test (MDT) result; and determining, by the UE, an early measurement result. The method further includes: transmitting, by the UE, a report including the MDT result, the early measurement result, or a combination thereof.

[0008] In another aspect of the present disclosure, an apparatus for wireless communication includes: means for determining, by a user equipment (UE), a minimized drive test (MDT) result. The apparatus further includes: means for determining, by the UE, an early measurement result. The apparatus further includes: means for transmitting, by the UE, a report including the MDT result, the early measurement result, or a combination thereof.

[0009] In another aspect of the present disclosure, program code is recorded on a non-transitory computer-readable medium. The program code includes: determining a minimized drive test (MDT) result, determining an early measurement result, and initiating transmission of a report including the MDT result, the early measurement result, or a combination thereof.

[0010] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor and a memory coupled to the processor. The processor is configured to: determine a minimized drive test (MDT) result, and determine an early measurement result. The processor is further configured to: initiate transmission of a report including the MDT result, the early measurement result, or a combination thereof.

[0011] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes an interface configured for wireless communication (e.g., a transmitter, a receiver, etc.) and a processor system coupled to the interface. The processor system is configured to: determine a minimized drive test (MDT) result, determine an early measurement result, and initiate transmission of a report including the MDT result, the early measurement result, or a combination thereof.

[0012] In another aspect of the present disclosure, a method for wireless communication includes: sending, by a network entity, a measurement configuration message. The measurement configuration message includes: a storage configuration for minimized drive test (MDT) results, early measurement results, or a combination thereof; a reporting configuration for the MDT results, the early measurement results, or a combination thereof; or a combination of the storage configuration and the reporting configuration. The method further includes: receiving, by the network entity, the MDT results, the early measurement results, or a combination thereof.

[0013] In another aspect of the present disclosure, a device for wireless communication includes: a unit for sending, by a network entity, a measurement configuration message. The measurement configuration message includes: a storage configuration for minimized drive test (MDT) results, early measurement results, or a combination thereof; a reporting configuration for the MDT results, the early measurement results, or a combination thereof; or a combination of the storage configuration and the reporting configuration. The device further includes: a unit for receiving, by the network entity, the MDT results, the early measurement results, or a combination thereof.

[0014] In another aspect of the present disclosure, program code is recorded on a non-transitory computer-readable medium. The program code includes: code for sending a measurement configuration message. The measurement configuration message includes: a storage configuration for minimized drive test (MDT) results, early measurement results, or a combination thereof; a reporting configuration for the MDT results, the early measurement results, or a combination thereof; or a combination of the storage configuration and the reporting configuration. The program code further includes: code for receiving the MDT results, the early measurement results, or a combination thereof.

[0015] In another aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor and a memory coupled to the processor. The processor is configured to: initiate the transmission of a measurement configuration message. The measurement configuration message includes: a storage configuration for minimized drive test (MDT) results, early measurement results, or a combination thereof; a reporting configuration for the MDT results, the early measurement results, or a combination thereof; or a combination of the storage configuration and the reporting configuration. The processor is further configured to receive the MDT results, the early measurement results, or a combination thereof.

[0016] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. An interface configured for wireless communication (e.g., a transmitter, a receiver, etc.) and a processor system coupled to the interface. The processor system is configured to initiate the transmission of a measurement configuration message. The measurement configuration message includes: a storage configuration for minimizing drive test (MDT) results, early measurement results, or a combination thereof; a reporting configuration for the MDT results, the early measurement results, or a combination thereof; or a combination of the storage configuration and the reporting configuration. The processor system is further configured to receive the MDT results, the early measurement results, or a combination thereof.

[0017] In another aspect of the present disclosure, a method for wireless communication includes: generating, by a user equipment (UE), a radio link failure (RLF) report based on the detection of a primary cell group (MCG) fast recovery failure. The RLF report includes MCG failure information, MCG recovery failure information, or a combination thereof. The method further includes: sending, by the UE, the RLF report to a secondary cell group (SCG).

[0018] In another aspect of the present disclosure, an apparatus for wireless communication includes: a unit for generating, by a user equipment (UE), a radio link failure (RLF) report based on the detection of a primary cell group (MCG) fast recovery failure. The RLF report includes MCG failure information, MCG recovery failure information, or a combination thereof. The apparatus further includes: a unit for sending, by the UE, the RLF report to a secondary cell group (SCG).

[0019] In another aspect of the present disclosure, program code is recorded on a non-transitory computer-readable medium. The program code includes: code for generating, based on the detection of a primary cell group (MCG) fast recovery failure, a radio link failure (RLF) report. The RLF report includes MCG failure information, MCG recovery failure information, or a combination thereof. The program code further includes: code for initiating the transmission of the RLF report to a secondary cell group (SCG).

[0020] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor and a memory coupled to the processor. The processor is configured to: generate, based on the detection of a primary cell group (MCG) fast recovery failure, a radio link failure (RLF) report. The RLF report includes MCG failure information, MCG recovery failure information, or a combination thereof. The processor is further configured to initiate the transmission of the RLF report to a secondary cell group (SCG).

[0021] In another aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes an interface (e.g., a transmitter, a receiver, etc.) configured for wireless communication and a processor system coupled to the interface. The processor system is configured to: generate a radio link failure (RLF) report based on the detection of a primary cell group (MCG) fast recovery failure. The RLF report includes MCG failure information, MCG recovery failure information, or a combination thereof. The processor system is further configured to initiate the transmission of the RLF report to a secondary cell group (SCG).

[0022] In another aspect of the present disclosure, a method for wireless communication includes: determining, by a user equipment (UE) configured for dual connectivity (DC), a bearer type of the UE. The method further includes: transmitting, from the UE, an uplink (UL) latency measurement based on the bearer type.

[0023] In a further aspect of the present disclosure, a device for wireless communication includes: a unit for determining, by a user equipment (UE) configured for dual connectivity (DC), a bearer type of the UE. The device further includes: a unit for transmitting, from the UE, an uplink (UL) latency measurement based on the bearer type.

[0024] In a further aspect of the present disclosure, program code is recorded on a non-transitory computer-readable medium. The program code includes: code for determining a bearer type of a user equipment (UE) configured for dual connectivity (DC); code for initiating the transmission of an uplink (UL) latency measurement based on the bearer type.

[0025] In a further aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor and a memory coupled to the processor. The processor is configured to: determine a bearer type of a user equipment (UE) configured for dual connectivity (DC); initiate the transmission of an uplink (UL) latency measurement based on the bearer type.

[0026] In another aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes an interface (e.g., a transmitter, a receiver, etc.) configured for wireless communication and a processor system coupled to the interface. The processor system is configured to: determine a bearer type of a user equipment (UE) configured for dual connectivity (DC); and initiate the transmission of an uplink (UL) latency measurement based on the bearer type.

[0027] After understanding the following description of specific examples in conjunction with the accompanying drawings, other aspects, features, and implementations will become apparent to those of ordinary skill in the art. Although features are discussed with respect to some aspects and drawings below, all implementations may include one or more of the advantageous features discussed herein. In other words, although one or more examples are discussed as having certain advantageous features, one or more of these features may also be used according to these individual examples. In a similar manner, although the exemplary implementations are discussed below as device, system, or method implementations, these exemplary implementations may be implemented using a variety of devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] A further understanding of the nature and advantages of the present disclosure can be obtained by referring to the following drawings. In the drawings, like components or features have the same reference numerals. Additionally, each of the same type of components may be distinguished by adding a dashed line after the reference numeral and a second label for differentiating similar components. If only the first reference numeral is used in the specification, the description may apply to any one of the similar components having the same first reference numeral, regardless of the second reference numeral.

[0029] Figure 1 is a block diagram showing details of a wireless communication system according to some aspects of the present disclosure.

[0030] Figure 2 is a block diagram conceptually showing a design of a base station and a user equipment (UE) configured according to some aspects.

[0031] Figure 3 is a block diagram showing an illustrative implementation of a system configured to provide data collection for a user equipment (UE), where the UE may be configured for dual connectivity (DC) / carrier aggregation (CA) according to some aspects.

[0032] Figure 4 is a block diagram showing another illustrative implementation of a system configured to provide data collection for a UE, where the UE may be configured for dual connectivity (DC) / carrier aggregation (CA) according to some aspects.

[0033] Figure 5 is a block diagram showing another illustrative implementation of a system configured to provide data collection for a UE, where the UE may be configured for dual connectivity (DC) / carrier aggregation (CA) according to some aspects.

[0034] Figure 6 is a flowchart showing an example block performed by a UE according to some aspects.

[0035] Figure 7is a flowchart showing example boxes performed by a UE according to some aspects.

[0036] Figure 8 is a flowchart showing example boxes performed by a UE according to some aspects.

[0037] Figure 9 is a flowchart showing example boxes performed by a network entity according to some aspects.

[0038] Figure 10 is a block diagram conceptually showing a design of a UE configured according to some aspects.

[0039] Figure 11 is a block diagram conceptually showing a design of a network entity configured according to some aspects. Detailed Description

[0040] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. On the contrary, the detailed description includes specific details for the purpose of providing a thorough understanding of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every instance and in some instances, for clarity of presentation, well-known structures and components are shown in block diagram form.

[0041] The present disclosure provides systems, devices, methods, and computer-readable media for radio access network (RAN)-centric data collection for a UE configurable for DC / CA operation. The data collection can be used to improve device (e.g., UE) performance such as battery life, throughput, latency, reliability, and new radio (NR) features and / or characteristics (e.g., beam management, bandwidth part (BWP), RRC_INACTIVE, multi-radio access technology (RAT) dual connectivity (MR-DC), and dual connectivity (DC) / carrier aggregation (CA)). The data collection and operation improvement can also result in reduced capital expenditure (CAPEX) and operating expenditure (OPEX) for the operator, e.g., through more accurate base station deployment and operation and less human resource intervention. For illustration purposes, the present disclosure describes the collection, storage, reporting, or combination thereof of DC / CA early measurement results associated with recorded minimized drive test (MDT). As another example, the present disclosure describes radio link failure (RLF) reporting configured to support fast master cell group (MCG) recovery failure via a secondary cell group (SCG). Additionally, the present disclosure also describes single-connection layer 2 (L2) measurements configured to support uplink (UL) latency measurements for a UE configured for dual connectivity (DC) operation.

[0042] In some embodiments, the UE may be configured to perform early measurements, e.g., an early measurement configuration for an idle / inactive UE to measure a resident frequency, a non-resident frequency, or a combination thereof. Such early measurements may enable faster DC / CA setup. The UE may be configured to record available early measurement results with one or more MDT results. For illustration purposes, the UE may record available early measurement results along with location information for MDT. The early measurement records and the recorded MDT may have the same or different recording intervals (if both early measurement and MDT recording are configured). The early measurement results may be recorded when available. If there are no available early measurement results (e.g., when the UE is outside the valid area or a recorded timer expires), the log or log entry may remain blank.

[0043] In some embodiments, to support early measurements of the UE, the network (NW) may configure the UE to store, report, or a combination thereof, the measurement results and the recorded MDT measurement results. For illustration purposes, the NW may indicate to the UE in an information request (e.g., UEinformationRequest) whether to report the recorded MDT measurement results, the early measurement results, or a combination thereof. In some embodiments, the early measurement results and the MDT measurement results may be stored in a single log / file. Alternatively, the early measurement results and the MDT measurement results may be stored in separate logs / files (e.g., two or more separate log files). When stored in separate log files, the UE may be configured to provide the early measurement results and the MDT measurement results either separately or together.

[0044] In some embodiments, the UE may be configured to generate an RLF report via the SCG to support fast MCG recovery failure. For illustration purposes, the UE may be configured to support fast MCG recovery via the SCG. For example, based on the detection of an MCG failure, the UE may not trigger radio resource control (RRC) connection reconstruction. Instead, the UE triggers an MCG failure recovery process, where a failure information message is sent to the network via the SCG. Based on the sending of the MCG failure indication, the UE starts a timer, and based on the expiration of the timer, the UE initiates an RRC connection reconstruction process.

[0045] The UE can be configured to perform data collection to generate an RLF report in case of a failure of fast MCG recovery via the SCG. For example, based on the expiration of a protection timer, RLF in the MCG and SCG, and the UE's inability to apply the RRC reconfiguration message as a response to indicate fast MCG failure information, a fast MCG recovery failure may occur or be detected. The RLF report can include MCG failure information, MCG recovery failure-related information, or a combination thereof. The MCG failure information can include available measurement results of the MCG, MCG link failure reasons, available measurement results of the SCG, available measurement results of one or more non-serving cells, or a combination thereof. The MCG recovery failure information can include available measurement results of the SCG, available measurement results of the MCG, measurement results of the available SN configuration, MCG recovery failure reasons (e.g., protection timer expiration indication, SCG link failure detection, etc.), recovery type (e.g., recovery via split signaling radio bearer (SRB) or signaling radio bearer type 3 (SRB3)), or a combination thereof.

[0046] In some embodiments, the UE can be configured to measure the uplink (UL) average packet data convergence protocol (PDCP) packet queuing delay measurement (D1) for dual connectivity (DC) operation. For example, when configured with a non-split bearer, the UE can receive a configuration for D1 measurement from the secondary node (SN) or the master node (MN). The UE can report the average UL PDCP packet queuing delay to the node from which it received the measurement configuration (e.g., SN or MN). As another example, when configured with a split bearer supported by one PDCP entity and multiple radio link control (RLC) entities, the UE can calculate the UL average PDCP packet queuing delay. For illustration purposes, in some embodiments, the UE can calculate a single D1 value and may not distinguish between PDCP packets sent to the MN or SN. In such an implementation, the UE can send a report (e.g., D1 report) to the node from which it received its configuration, or to both the MN and SN. In other embodiments, the UE can calculate (e.g., average) the PDCP packet queuing delay separately for packets sent to the MN and SN. In such an implementation, the UE can report the two D1 values along with the MN D1 and SN D1 indicators to the same node from which it received its configuration. Alternatively, the UE can report the two D1 values separately to the MN and SN, e.g., report MN D1 to the MN and report SN D1 to the SN.

[0047] Accordingly, the present disclosure describes RAN - centric data collection for a UE configurable for DC / CA operation. This data collection can be advantageously used to improve device (e.g., UE) performance such as battery life, throughput, latency, reliability, and new radio (NR) features and / or capabilities (e.g., beam management, bandwidth part (BWP), RRC_INACTIVE, multi - radio access technology (RAT) dual - connectivity (MR - DC), and dual - connectivity (DC) / carrier aggregation (CA)). The data collection and operation improvement can also result in reduced capital expenditure (CAPEX) and operating expenditure (OPEX) for the operator, e.g., through more accurate base station deployment and operation and less human resource intervention.

[0048] The present disclosure generally relates to providing or participating in communication between two or more wireless devices in one or more wireless communication systems (which are also referred to as wireless communication networks). In various implementations, these techniques and apparatuses can be used in wireless communication networks such as: code - division multiple - access (CDMA) networks, time - division multiple - access (TDMA) networks, frequency - division multiple - access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single - carrier FDMA (SC - FDMA) networks, LTE networks, GSM networks, fifth - generation (5G) or new radio (NR) networks (sometimes referred to as “5G NR” networks / systems / devices), and other communication networks. As described herein, the terms “network” and “system” can often be used interchangeably.

[0049] For example, a CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, etc. UTRA includes Wideband CDMA (WCDMA) and Low Chip Rate (LCR). CDMA 2000 covers the IS - 2000, IS - 95, and IS - 856 standards.

[0050] A TDMA network can implement radio technologies such as GSM, for example. 3GPP has defined standards for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN), which is also known as GERAN. GERAN is the radio component of GSM / EDGE, and the network that connects base stations (e.g., Ater and Abis interfaces) and base station controllers (A interface, etc.). The radio access network represents a component of the GSM network through which telephone calls and packet data are routed between the Public Switched Telephone Network (PSTN) and the Internet and the user's handheld device (also known as the user terminal or user equipment (UE)). The network of a mobile phone operator can include one or more GERANs, which can be coupled to the Universal Terrestrial Radio Access Network (UTRAN) in the case of a UMTS / GSM network. The operator network can also include one or more LTE networks and / or one or more other networks, or a combination thereof. Various different network types can use different Radio Access Technologies (RATs) and Radio Access Networks (RANs).

[0051] An OFDMA network can implement radio technologies such as evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM, etc. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long-Term Evolution (LTE) is a version of UMTS that employs E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization called the "3rd Generation Partnership Project" (3GPP), and CDMA2000 is described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or are about to be developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration among telecommunications union groups aimed at specifying globally applicable third-generation (3G) mobile phone specifications. 3GPP Long-Term Evolution (LTE) is a 3GPP plan aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP specifies the specifications for next-generation mobile networks, mobile systems, and mobile devices. The present disclosure focuses on the development of wireless technologies from LTE, 4G, 5G, NR, and the shared access to the wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces.

[0052] The 5G network takes into account various deployments, various spectrums, and various services and devices that can be implemented using an OFDM-based unified air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide the following coverage: (1) Ultra-large Internet of Things (IoT) with ultra-high density (e.g., ~1M nodes / km 2 ), ultra-low complexity (e.g., ~10s of bits / second), ultra-low energy (e.g., battery life of about 10 years or more), and deep coverage with the ability to reach challenging locations; (2) Critical mission control including strong security to protect sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1ms), and providing a wide range of mobility or lack thereof to users; (3) Enhanced mobile broadband, which includes extremely high capacity (e.g., ~10 Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, user experience rates above 100 Mbps), and improved discovery and optimized depth perception.

[0053] 5G NR devices, networks, and systems can be implemented to use an optimized OFDM-based waveform. These features can include scalable parameter sets and transmission time intervals (TTIs); a general, flexible framework for efficient multiplexing of services and features with a dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) design; and improved radio technologies such as massive multiple input, multiple output (MIMO), powerful millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of parameter sets in 5G NR, as well as the scaling of subcarrier spacing, can efficiently address the operation of diverse services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments implemented with less than 3 GHz FDD / TDD, the subcarrier spacing can be 15 kHz for bandwidths such as 1, 5, 10, 20 MHz, etc. For other various outdoor and small cell coverage deployments with TDD above 3 GHz, the subcarrier spacing can be 30 kHz for 80 / 100 MHz bandwidths. For other various indoor broadband implementations using TDD in the unlicensed part of the 5 GHz band, the subcarrier spacing can be 60 kHz for 160 MHz bandwidths. Finally, for various deployments using mmWave components for transmission with TDD at 28 GHz, the subcarrier spacing can be 120 kHz for 500 MHz bandwidths.

[0054] The scalable parameter sets of 5G NR facilitate scalable TTIs for various latency and Quality of Service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. The efficient reuse of long and short TTIs allows transmissions to start at symbol boundaries. 5G NR also considers a self - contained integrated sub - frame design where the uplink / downlink scheduling information, data, and acknowledgments are present in the same sub - frame. The self - contained integrated sub - frame supports communication in license - exempt or contention - based shared spectrum, adaptive uplink / downlink, and in this case, can be flexibly configured on a per - cell basis to dynamically switch between uplink and downlink to meet current traffic demands.

[0055] For clarity, certain aspects of these devices and techniques are described below with reference to exemplary LTE implementations or in an LTE - centric manner, and LTE terms may be used as illustrative examples in parts of the following description; however, the description is not intended to be limited to LTE applications. In fact, the present disclosure relates to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces, such as those of 5G NR.

[0056] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate in any combination of licensed spectrum or license - exempt spectrum depending on load and availability. Thus, it will be apparent to those of ordinary skill in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications in addition to the specific examples provided.

[0057] While aspects and implementations are described herein by way of illustration of some examples, those of ordinary skill in the art will appreciate that additional implementations and use cases can be implemented in many different arrangements and scenarios. The innovations described herein can be implemented across multiple different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, the implementations and / or uses can be implemented by way of integrated chip implementations and / or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, AI-enabled devices, etc.) or combinations thereof. While some examples may be specific to a use case or application, or may not be specific to a use case or application, a wide variety of applicability of the innovations described may occur. The scope of implementation can range from chip-level or modular components to non-modular, non-chip-level implementations, and can also be an aggregated, distributed, or OEM device or system that includes one or more of the aspects described. In some practical settings, devices that include the aspects and features described may also necessarily include other components and features for implementing and practicing the claimed and described aspects. The innovations described herein can be practiced in a wide variety of implementations having different sizes, shapes, and configurations, including large / small devices, chip-level components, multi-component systems (e.g., RF chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0058] Figure 1 FIG. 100 shows a wireless network 100 that communicates according to some aspects. The wireless network 100 can include, for example, a 5G wireless network. As those of ordinary skill in the art will appreciate, Figure 1 components that appear in FIG. 100 may have related counterparts in other network arrangements, including, for example, cellular network arrangements and non-cellular network arrangements (e.g., device-to-device or peer-to-peer or ad hoc network arrangements, etc.).

[0059] Figure 1The wireless network 100 shown in [Figure 0] includes a plurality of base stations 105 and other network entities. A base station can be a station that communicates with a UE, and it can also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, and so on. Each base station 105 can provide communication coverage for a specific geographical area. In 3GPP, depending on the context in which the term "cell" is used, the term "cell" can refer to the specific geographical coverage area of the base station, and / or the base station subsystem serving that coverage area. In the implementation of the wireless network 100 herein, the base stations 105 can be associated with the same operator or different operators (e.g., the wireless network 100 can include multiple operator wireless networks), and can use one or more (e.g., one or more frequency bands in licensed spectrum, unlicensed spectrum, or a combination thereof) of the same frequency as adjacent cells to provide wireless communication. In some examples, a single base station 105 or UE 115 can be operated by more than one network operation entity. In other examples, each base station 105 and UE 115 can be operated by a single network operation entity.

[0060] Base stations can provide communication coverage for macro cells or small cells (e.g., pico cells or femto cells) and / or other types of cells. Generally, a macro cell covers a relatively large geographical area (e.g., with a radius of several kilometers), which allows UEs with a service subscription to the network provider to access without restriction. Generally, small cells such as pico cells cover a relatively small geographical area, which allows UEs with a service subscription to the network provider to access without restriction. In addition, small cells such as femto cells generally cover a relatively small geographical area (e.g., a home), which, in addition to unrestricted access, also provides restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, etc.). The base station for a macro cell can be called a macro base station. The base station for a small cell can be called a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105-a - 105c are macro base stations implementing one of 3-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105-a - 105c make full use of their higher-dimensional MIMO capabilities to increase coverage and capacity by using 3D beamforming in elevation and azimuth beamforming. Base station 105f is a small cell base station, and the small cell base station can be a home node or a portable access point. A base station can support one or more (e.g., two, three, four, etc.) cells.

[0061] The wireless network 100 can support synchronous or asynchronous operations. For synchronous operations, base stations can have similar frame timings, and transmissions from different base stations are approximately aligned in time. For asynchronous operations, base stations can have different frame timings, and transmissions from different base stations are not aligned in time. In some scenarios, the network can be enabled or configured to handle dynamic switching between synchronous and asynchronous operations.

[0062] UEs 115 are dispersed throughout the wireless network 100, and each UE can be stationary or mobile. It should be understood that although in the standards and specifications promulgated by the 3rd Generation Partnership Project (3GPP), mobile devices are commonly referred to as user equipment (UEs), those of ordinary skill in the art may also refer to such devices as mobile stations (MSs), user stations, mobile units, user units, radio units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile user stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handheld devices, terminals, user agents, mobile clients, clients, or some other suitable term. Within this document, a "mobile" device or UE does not necessarily need to have the ability to move and can be stationary. Some non-limiting examples of mobile devices, such as examples that can include one or more of the UEs 115, include mobile stations, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, wireless local loop (WLL) stations, laptop computers, personal computers (PCs), notebooks, netbooks, smart books, tablet devices, and personal digital assistants (PDAs). Mobile devices can also be "Internet of Things" (IoT) or "Internet of Everything" (IoE) devices, such as automobiles or other transportation vehicles, satellite radios, Global Positioning System (GPS) devices, logistics controllers, drones, multi-rotor helicopters, helicopters, smart energy or security devices, solar panels or solar arrays, municipal lighting, water, or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammalian implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video, and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE can be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE can be a device that does not include a UICC. In some aspects, a UE that does not include a UICC can also be referred to as an IoE device. Figure 1The UEs 115-a - 115d in the example shown are examples of mobile smart phone type devices accessing the wireless network 100. The UE can also be a machine specifically configured to implement connected communication, which includes machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), and so on. Figure 1 The UEs 115e - 115k shown in the figure are examples of various machines configured to access the wireless network 100.

[0063] A mobile device such as the UE 115 can communicate with any type of base station, whether it is a macro base station, a pico base station, a femto base station, a repeater, and so on. In Figure 1 the figure, lightning (e.g., communication link) indicates a wireless transmission between the UE and the serving base station, or a desired transmission between base stations, and a backhaul transmission between base stations, where the serving base station is the base station designated to serve the UE on the downlink and / or uplink. Backhaul communication between the base stations of the wireless network 100 can occur using wired and / or wireless communication links.

[0064] When operating in the wireless network 100, the base stations 105-a - 105c use 3D beamforming and collaborative spatial technologies (e.g., coordinated multipoint (CoMP) or multi-connection) to serve the UEs 115-a and 115-b. The macro base station 105d performs backhaul communication with the base stations 105-a - 105c and the small cell base station 105f. The macro base station 105d also transmits multicast services subscribed to and received by the UEs 115c and 115d. Such multicast services can include mobile TV or streaming video, or can include other services for providing community information (e.g., weather emergencies or alerts such as amber alerts or gray alerts).

[0065] The wireless network 100 may support mission-critical communications for mission-critical devices (e.g., UE 115e, which is a drone) with ultra-reliable and redundant links. The redundant communication links with UE 115e include communication links from macro base stations 105d and 105e, and small cell base station 105f. Other machine type devices such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device) may communicate directly with base stations such as small cell base station 105f and macro base station 105e via the wireless network 100, or in a multi-hop configuration, by communicating with another user equipment that relays its information to the network. For example, UE 115f transmits temperature measurement information to smart meter UE 115g, and then reports it to the network via small cell base station 105f. In a vehicle-to-vehicle (V2V) mesh network, for example, between UEs 115i - 115k communicating with macro base station 105e, the wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD / FDD communications.

[0066] Figure 2 A block diagram showing the design of base station 105 and UE 115 is presented, where base station 105 and UE 115 can be Figure 1 one of the base stations in Figure 1 and one of the UEs in Figure 1 For the restricted association scenario (as described above), base station 105 can be small cell base station 105f in Figure 2 , and UE 115 can be UE 115c or UE115D operating in the service area of base station 105f. To access small cell base station 105f, UE 115c or 115D will be included in the list of accessible UEs of small cell base station 105f. Base station 105 can also be some other type of base station, or another network entity (e.g., network, network core, network core device, etc.). As Figure 2 shown, base station 105 can be equipped with antennas 234a to 234t, and UE 115 can be equipped with antennas 252a to 252r for facilitating wireless communications.

[0067] At base station 105, transmit processor 220 may receive data from data source 212 and control information from controller / processor 240. The control information may be for physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), physical downlink control channel (PDCCH), enhanced physical downlink control channel (EPDCCH), MTC physical downlink control channel (MPDCCH), etc. The data may be for PDSCH, etc. Transmit processor 220 may process the data and control information (e.g., encode and symbol map) to obtain data symbols and control symbols respectively. In addition, transmit processor 220 may also generate reference symbols, e.g., for primary synchronization signal (PSS) and secondary synchronization signal (SSS) and cell-specific reference signal. Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on these data symbols, control symbols, and / or reference symbols (if any) and provide output symbol streams to these modulators (MOD) 232a to 232t. Each modulator 232 may process its respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may additionally or alternatively process (e.g., convert to analog signal, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t respectively.

[0068] At UE 115, antennas 252a to 252r may receive downlink signals from base station 105 and provide the received signals to demodulators (DEMOD) 254a to 254r respectively. Each demodulator 254 may condition (e.g., filter, amplify, down-convert, and digitize) its respective received signal to obtain input samples. Each demodulator 254 may further process these input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 may obtain the received symbols from demodulators 254a to 254r, perform MIMO detection (if any) on the received symbols, and provide the detected symbols. Receive processor 258 may process (e.g., demodulate, de-interleave, and decode) the detected symbols, provide the decoded data for UE115 to data sink 260, and provide the decoded control information to controller / processor 280.

[0069] On the uplink, at the UE 115, the transmit processor 264 may receive data (e.g., for the physical uplink shared channel (PUSCH)) from the data source 262, receive control information (e.g., for the physical uplink control channel (PUCCH)) from the controller / processor 280, and process the data and control information. In addition, the transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be precoded (if any) by the TX MIMO processor 266, further processed (e.g., for SC-FDM, etc.) by the modulators 254a to 254r, and sent back to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected (if any) by the MIMO detector 236, and further processed by the receive processor 238 to obtain the decoded data and control information sent by the UE 115. The processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240.

[0070] The controller / processors 240 and 280 may direct the operations of the base station 105 and the UE 115, respectively. The controller / processor 240 and / or other processors and modules at the base station 105 and / or the controller / processor 280 and / or other processors and modules at the UE 115 may perform or direct the execution of various processes for implementing the techniques described herein, such as for performing or directing Figures 6 - 9 the execution of the functional modules shown in, and / or for implementing other processes for the techniques described herein. The memories 242 and 282 may store data and program codes for the base station 105 and the UE 115, respectively. The scheduler 244 may schedule data transmissions for the UE on the downlink and / or uplink.

[0071] Wireless communication systems operated by different network operating entities (e.g., network operators) may share spectrum. In some instances, a network operating entity may be configured to use the entire specified shared spectrum for at least a period of time before another network operating entity uses the entire specified shared spectrum during a different period of time. Thus, to allow a network operating entity to use the entire specified shared spectrum and to mitigate interference communication between different network operating entities, certain resources (e.g., time) may be partitioned and allocated to different network operating entities for certain types of communication.

[0072] For example, specific time resources reserved for exclusive communication can be allocated to a network operation entity so that the network operation entity can use the entire shared spectrum. Other time resources can also be allocated to the network operation entity, during which the entity is given priority over other network operation entities to use the shared spectrum for communication. If the network operation entity with priority does not utilize these time resources that are preferentially used by the network operation entity, other network operation entities can use them on an opportunistic basis. Additional time resources can be allocated to any network operator for opportunistic use.

[0073] The access to the shared spectrum and the arbitration of time resources among different network operation entities can be centrally controlled by a separate entity, determined autonomously according to a predefined arbitration scheme, or determined dynamically based on the interaction between the radio nodes of network operators.

[0074] In some cases, the UE 115 and the base station 105 can operate in a shared radio spectrum band that includes licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 105 can traditionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 can perform a listen-before-talk (LBT) process (e.g., clear channel assessment (CCA)) before communication to determine whether the shared channel is available. The CCA can include an energy detection process to determine whether there is any other active transmission. For example, a device can infer that a change in the received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, signal power concentrated in a specific bandwidth and exceeding a predetermined noise floor can indicate another wireless transmitter. The CCA can also include the detection of a specific sequence indicating channel use. For example, another device can send a specific preamble before sending a data sequence. In some cases, the LBT process can include: a wireless node adjusting its own backoff window based on the amount of energy detected on the channel and / or the acknowledgment / negative acknowledgment (ACK / NACK) feedback for its own transmitted packets (as a proxy for collisions).

[0075] In some embodiments, the UE 115 may be configured for DC operation or DC / CA operation. In such an implementation, the UE 115 is configured for radio access network (RAN)-centric data collection. For illustration purposes, the UE 115 may be configured to collect, store, report, or a combination thereof, DC / CA early measurement results associated with recorded minimized drive test (MDT). As another example, the UE 115 may be configured for data collection to generate a radio link failure (RLF) report that is configured to support fast primary cell group (MCG) recovery failure via a secondary cell group (SCG). Additionally or alternatively, when the UE 115 is configured for dual connectivity (DC) operation, the UE 115 may be configured to perform data collection for uplink (UL) latency measurement.

[0076] Figure 3 FIG. 3 is a block diagram of an exemplary wireless communication system 300 configured to provide data collection to a user equipment (UE) configurable for dual connectivity / carrier aggregation (DC / CA). In some examples, the wireless communication system 300 may implement aspects of the wireless network 100. The wireless communication system 300 includes a UE 115 and a network entity 350. As an illustrative, non-limiting example, the network entity 350 may include or correspond to a base station 105, a network, a network core, or another network device. Although one UE and one network entity are shown, in other implementations, the wireless communication system 300 may include more than one UE, more than one network entity, or both.

[0077] The UE 115 may include various components (e.g., structured, hardware components) for performing one or more functions described herein. For example, these components may include a processor 312, a memory 314, a transmitter 315, a receiver 316, and a timer 317. The processor 312 may be configured to execute instructions stored in the memory 314 to perform the operations described herein. In some embodiments, the processor 312 includes or corresponds to the controller / processor 280, and the memory 314 includes or corresponds to the memory 282.

[0078] The memory 314 may include one or more modes 318, location information 319, one or more measurement results 320, and one or more log intervals 323. The modes 318 may include one or more modes of the UE 115, such as an active mode or an inactive mode. As an illustrative, non-limiting example, the inactive mode may include an idle mode, an inactive mode, a low power mode, or another mode.

[0079] Location information 319 may indicate the location of UE 115. For example, the location information may include GPS data. One or more measurement results 320 may include a log of one or more entries. The measurement results 320 may include or indicate early measurement data 321, MDT data 322, or a combination thereof. The early measurement data 321 may include one or more measurements of a resident frequency, a non-resident frequency, or a combination thereof. The MDT data 322 may include one or more MDT results. One or more logging intervals 323 may indicate a first interval for performing measurements to generate the early measurement data 321, a second interval for determining the MDT data 322, or a combination thereof. In some embodiments, the first interval and the second interval are the same interval. Additionally or alternatively, the first interval and the second interval occur simultaneously. In other embodiments, the first interval and the second interval are different.

[0080] The transmitter 315 is configured to send data to one or more other devices, and the receiver 316 is configured to receive data from one or more other devices. For example, the transmitter 315 may send data, while the receiver 316 may receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, UE 115 may be configured to send or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the foregoing, or any other communication network now known or later developed that permits two or more electronic devices to communicate. In some embodiments, the transmitter 315 and the receiver 316 may be replaced by a transceiver. Additionally or alternatively, the transmitter 315, the receiver 316, or both may include or correspond to one or more components of the UE 115 described with reference Figure 2 to. The timer 317 may be configured to enable UE 115 to track or determine one or more time periods, or the expiration of one or more time periods.

[0081] The network entity 320 may include various components (e.g., structured, hardware components) for performing one or more functions described herein. For example, these components may include a processor 362, a memory 364, a transmitter 366, and a receiver 368. The processor 362 may be configured to execute instructions stored in the memory 364 to perform the operations described herein. In some embodiments, the processor 362 includes or corresponds to the controller / processor 240, and the memory 364 includes or corresponds to the memory 242.

[0082] The transmitter 366 is configured to send data to one or more other devices, and the receiver 368 is configured to receive data from one or more other devices. For example, the transmitter 366 can send data while the receiver 368 can receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, the network entity 350 can be configured to send or receive data via a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network that allows two or more electronic devices to communicate, whether now known or later developed. In some embodiments, the transmitter 356 and the receiver 368 can be replaced by a transceiver. Additionally or alternatively, the transmitter 366, the receiver 368, or both can include or correspond to one or more components of the base station 105 described with reference to Figure 2 one or more components of the base station 105.

[0083] In a particular implementation, the wireless communication system 300 includes a 5G network. For example, the UE 115 can include a 5G UE (e.g., a UE configured to operate according to a 5G network). The network entity 350 can include a 5G base station (e.g., a base station configured to operate according to a 5G network).

[0084] In some embodiments, the UE 115 can be configured for early measurements, such as early measurement configuration for idle / inactive UEs to measure resident frequencies, non-resident frequencies, or a combination thereof. Such early measurements (e.g., 321) can enable faster DC / CA setup. The UE 115 can be configured to record available early measurement results with one or more MDT results (e.g., 322). For illustration purposes, the UE 115 can record available early measurement results with the location information of the MDT (e.g., 319). The early measurement records and the recorded MDTs may have the same or different recording intervals (e.g., 323) (if both early measurements and MDT recording are configured simultaneously). The early measurement results (e.g., 321) can be recorded when available. If there are no available early measurement results (e.g., when the UE 115 is outside the valid area or the recording timer expires), the log or the log entry can remain blank.

[0085] In some embodiments, to support early measurements performed by UE 115, the network (NW) (e.g., network entity 350) may configure UE 115 to store, report, or a combination of both the early measurement results (e.g., 321) and the recorded MDT measurement results (e.g., 322). For illustration, the NW may indicate in measurement configuration 370 whether to report the recorded MDT measurement results, the early measurement results, or a combination thereof to the UE. For example, measurement configuration 370 may include an information request, such as UEinformationRequest. In some embodiments, the early measurement results (e.g., 321) and the MDT measurement results (e.g., 322) may be stored in a single log / file. Alternatively, the early measurement results (e.g., 321) and the MDT measurement (e.g., 322) results may be stored in different logs / files (e.g., two or more separate log files). When stored as separate log files, UE 115 may be configured to provide the early measurement results and the MDT measurement results either separately or together.

[0086] During operation of the wireless communication system 300, UE 115 receives measurement configuration 370 from network entity 350. Measurement configuration 370 may include a storage configuration, a reporting configuration, or a combination of both. The storage configuration may indicate to store the minimized drive test (MDT) results in a first log file, the intervals for measuring the MDT measurements, the early measurement results in a second log file, the intervals for measuring the early measurement results, whether to store the MDT results and the early measurement results in the same log, or a combination thereof. The reporting configuration may indicate to transmit the MDT results and the early measurement results in the same report message or in separate report messages.

[0087] UE 115 may identify the storage configuration, the reporting configuration, or both based on measurement configuration 370. UE 115 may generate or populate measurement results 320 based on the storage configuration. For example, when UE 115 is in an inactive state, UE 115 may generate or populate measurement results 320. For illustration, UE 115 may determine the minimized drive test (MDT) results, the early measurement results, or both. The early measurement data 321 may be determined according to a first interval (e.g., 323), and the MDT data 322 may be determined according to a second interval (e.g., 323). UE 115 may generate a first log of one or more MDT result entries and a second log of one or more early measurement result entries. In some embodiments, UE 115 may also generate or populate location information 319.

[0088] The UE 115 may send one or more measurement logs 372 (e.g., reports) including MDT data 322, early measurement data 321, or a combination thereof. The UE 115 may generate one or more measurement logs 372 (e.g., reports) based on a reporting configuration. In some embodiments, the UE 115 may send a first report including MDT data 322 and a second report including early measurement data 321. The first report may be sent before, after, or at the same time as the second report.

[0089] Accordingly, the present disclosure describes RAN - centric data collection for UEs configurable for DC / CA operation. For example, the operations described herein provide for the collection, storage, reporting, or a combination thereof, of DC / CA early measurement results associated with recorded minimized drive test (MDT). The data collection can be advantageously used to improve device (e.g., UE) performance such as battery life, throughput, latency, reliability, and new radio (NR) capabilities and / or features.

[0090] Figure 4 FIG. 7 is a block diagram of an exemplary wireless communication system 400 configured to provide data collection to a user equipment (UE) configurable for DC / CA. In some examples, the wireless communication system 400 may implement aspects of the wireless network 100 or the wireless communication system 300. The wireless communication system 400 includes a UE 115, a first network entity 450, and a second network entity 452. By way of illustrative, non - limiting example, the network entities 450, 452 may include or correspond to a base station 105, a network, a network core, or another network device. In some embodiments, the first network entity 450 includes or corresponds to a master cell group (MCG), and the second network entity 452 includes or corresponds to a secondary cell group (SCG). Although one UE and two network entities are shown, in other implementations, the wireless communication system 400 may include more than one UE, one network, or more than two network entities or both.

[0091] The UE 115 may include various components (e.g., structured, hardware components) for performing one or more functions described herein. For example, these components may include a processor 312, a memory 314, a transmitter 315, a receiver 316, a timer 317, and a fault detector 421. The processor 312 may be configured to execute instructions stored in the memory 314 to perform the operations described herein. In some embodiments, the processor 312 includes or corresponds to the controller / processor 280, and the memory 314 includes or corresponds to the memory 282.

[0092] The memory 314 may include a recovery procedure 422, an RRC configuration or (re)configuration 423, failure information 424, a protection time 427, and bearer information 428. The recovery procedure 422 may include information or instructions executed by the UE 115 in response to the detection of a radio link failure. For example, the recovery procedure 422 may include or correspond to a fast MCG recovery. The RRC configuration 423 may include one or more RRC configurations received from a network such as a first network entity 450 or a second network entity 452. In some embodiments, at least one RRC configuration may be received via a configuration message 470.

[0093] The failure information 424 may be generated by a failure detector 421. The failure information 424 may include MCG failure information 425 and MCG recovery failure information 426. The MCG failure information 425 may include available measurement results of the MCG, MCG link failure causes, available measurement results of the SCG, available measurement results of non-serving cells, or a combination thereof. The MCG recovery failure information 426 may include available measurement results of the SCG, available measurement results of the MCG, available secondary node (SN) measurement results, or a combination thereof. Additionally or alternatively, the MCG recovery failure information 426 may include an MCG recovery failure cause, such as a protection timer expiration indication or an SCG link failure detection, a signaling radio bearer type (e.g., split SRB or SRB type 3 (SRB3)), or a combination thereof.

[0094] The protection time 427 may indicate a protection time for performing or completing a fast MCG recovery procedure. The bearer information 428 may include or indicate the bearer type of the UE 115, such as a split signaling radio bearer (SRB) or a signaling radio bearer type 3 (SRB3).

[0095] The transmitter 315 is configured to send data to one or more other devices, and the receiver 316 is configured to receive data from one or more other devices. For example, the transmitter 315 may send data, while the receiver 316 may receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, the UE 115 may be configured to send or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the foregoing, or any other communication network now known or later developed that permits two or more electronic devices to communicate. In some embodiments, the transmitter 315 and the receiver 316 may be replaced with a transceiver. Additionally or alternatively, the transmitter 315, the receiver 316, or both may include or correspond to one or more components of the UE 115 described with reference to Figure 2 those described.

[0096] The timer 317 can be configured to enable the UE 115 to track or determine one or more time periods, or to track or determine the expiration of one or more time periods. The fault detector 421 can be configured to detect or determine a radio link failure, such as a radio link failure between the UE 115 and the first network entity 450 or between the UE 115 and the second network entity 452.

[0097] The first network entity 450 can include various components (e.g., structured, hardware components) for performing one or more functions described herein. For example, these components can include a processor 362, a memory 364, a transmitter 366, and a receiver 368. The processor 362 can be configured to execute instructions stored in the memory 364 to perform the operations described herein. In some embodiments, the processor 362 includes or corresponds to the controller / processor 240, and the memory 364 includes or corresponds to the memory 242.

[0098] The transmitter 366 is configured to send data to one or more other devices, and the receiver 368 is configured to receive data from one or more other devices. For example, the transmitter 366 can send data, while the receiver 368 can receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, the first network entity 450 can be configured to send or receive data via a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the foregoing, or any other communication network now known or later developed that permits two or more electronic devices to communicate. In some embodiments, the transmitter 356 and the receiver 368 can be replaced with a transceiver. Additionally or alternatively, the transmitter 366, the receiver 368, or both can include or correspond to one or more components of the base station 105 described with reference to Figure 2 the base station 105 described.

[0099] The second network entity 452 can also include one or more components, such as a processor, a memory, a transmitter, a receiver, etc., which are not shown for convenience. The second network entity 452 can include one or more components described with reference to the second network entity 450. In some embodiments, the first network entity 450 and the second network entity 452 are included in the same device or correspond to the same device.

[0100] In certain implementations, wireless communication system 400 includes a 5G network. For example, UE 115 may include a 5G UE (e.g., a UE configured to operate according to a 5G network). Network entities 450, 452 may include 5G base stations (e.g., base stations configured to operate according to a 5G network).

[0101] In some embodiments, UE 115 may be configured to generate an RLF report (e.g., 472) to support fast MCG recovery failure via an SCG (e.g., 452). For example, based on the detection of an MCG failure by a failure detector 421, UE 115 may not trigger radio resource control (RRC) connection reconstruction. Instead, UE 115 may trigger an MCG failure recovery process (e.g., 422) in which a failure information message is sent to the network via an SCG (e.g., 452). Based on the sending of the MCG failure indication, UE 115 starts a timer 317, and based on the expiration of the time period, UE 115 may initiate an RRC connection reconstruction process (e.g., 422).

[0102] In some embodiments, UE 155 may be configured to: perform data collection to generate an RLF report (e.g., 472) in the case of a fast MCG recovery failure via an SCG (e.g., 452). For example, a fast MCG recovery failure may occur or be detected based on the expiration of a protection timer, an RLF in both the MCG and SCG, or UE 115's inability to apply an RRC reconfiguration message in response to sending a fast MCG failure information indication. The RLF report (e.g., 472) may include MCG failure information 425, MCG recovery failure related information 426, or a combination thereof. The MCG failure information 425 may include available measurement results of the MCG, MCG link failure causes, available measurement results of the SCG, available measurement results of one or more non-serving cells, or a combination thereof. The MCG recovery failure information 426 may include available measurement results of the SCG, available measurement results of the MCG, measurement results of available SN configurations, MCG recovery failure causes (e.g., protection timer expiration indication, SCG link failure detection, etc.), recovery type (e.g., recovery via split signaling radio bearer (SRB) or signaling radio bearer type 3 (SRB3)), or a combination thereof.

[0103] During operation of wireless communication system 400, UE 115 may detect a radio link failure and may perform a fast MCG recovery process. As part of the MCG recovery, UE 115 may receive a configuration message 470 from a first network entity 450 or a second network entity 452. The configuration message may include an RRC configuration. UE 115 may detect a failure of the fast MCG recovery process.

[0104] Based on the detection of fast MCG recovery failure, UE 115 may generate and send a failure report 472. UE 115 may perform one or more operations to recover the MCG connection, recover the SCG connection, or both.

[0105] Accordingly, the present disclosure describes RAN - centric data collection for a UE configurable for DC / CA operations. For example, the operations described herein provide a radio link failure (RLF) report that is configured to support fast master cell group (MCG) recovery failure via a secondary cell group (SCG). The data collection can be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, and new radio (NR) capabilities and / or features.

[0106] Figure 5 FIG. 7 is a block diagram of an exemplary wireless communication system 500 configured to provide data collection to a user equipment (UE) configurable for dual - connection / carrier aggregation (DC / CA). In some examples, the wireless communication system 500 may implement aspects of the wireless network 100 or the wireless communication systems 300, 400. The wireless communication system 500 includes a UE 115, a first network entity 550, and a second network entity 552. By way of illustrative, but not limiting, example, the network entities 550, 552 may include or correspond to a base station 105, a network, a network core, or another network device. In some embodiments, the first network entity 550 includes or corresponds to a master node (MN), and the second network entity 552 includes or corresponds to a secondary node (SN). Although one UE and two network entities are shown, in other implementations, the wireless communication system 500 may include more than one UE, one network entity, or more than two network entities, or both.

[0107] UE 115 may include a variety of components (e.g., structured, hardware components) for performing one or more functions described herein. For example, these components may include a processor 312, a memory 314, a transmitter 315, and a receiver 316. The processor 312 may be configured to execute instructions stored in the memory 314 to perform the operations described herein. In some embodiments, the processor 312 includes or corresponds to a controller / processor 280, and the memory 314 includes or corresponds to a memory 282.

[0108] The memory 314 may include information 428 and one or more D1 measurements 520 carried thereon. The one or more D1 measurements 520 may include latency information 521 (e.g., MN information 522, SN information 523, or a combination thereof). The latency information 521 may include a UL average packet data convergence protocol (PDCP) packet queuing delay measurement (D1). The MN information 522 includes the average PDCP packet queuing delay of packets transmitted to the first network entity 550. The SN information 523 includes the average PDCP packet queuing delay of packets transmitted to the second network entity 552. In some embodiments, the latency information 521 may include the average PDCP packet queuing delay of packets transmitted to both the first network entity 550 and the second network entity 552.

[0109] The transmitter 315 is configured to send data to one or more other devices, and the receiver 316 is configured to receive data from one or more other devices. For example, the transmitter 315 may send data while the receiver 316 may receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, the UE 115 may be configured to send or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the foregoing, or any other communication network now known or later developed that permits two or more electronic devices to communicate. In some embodiments, the transmitter 315 and the receiver 316 may be replaced with a transceiver. Additionally or alternatively, the transmitter 315, the receiver 316, or both may include or correspond to one or more components of the UE 115 described with reference to Figure 2 the components described.

[0110] The first network entity 550 may include various components (e.g., structured, hardware components) for performing one or more functions described herein. For example, such components may include a processor 362, a memory 364, a transmitter 366, and a receiver 368. The processor 362 may be configured to execute instructions stored in the memory 364 to perform the operations described herein. In some embodiments, the processor 362 includes or corresponds to the controller / processor 240, and the memory 364 includes or corresponds to the memory 242.

[0111] The transmitter 366 is configured to send data to one or more other devices, and the receiver 368 is configured to receive data from one or more other devices. For example, the transmitter 366 may send data, while the receiver 368 may receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, the first network entity 550 may be configured to send or receive data via a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the foregoing, or any other communication network now known or later developed that permits two or more electronic devices to communicate. In some embodiments, the transmitter 356 and the receiver 368 may be replaced with a transceiver. Additionally or alternatively, the transmitter 366, the receiver 368, or both may include or correspond to one or more components of the base station 105 described with reference to Figure 2 one or more components of the base station 105 described with reference to

[0112] The second network entity 552 may also include one or more components (not shown for convenience) such as a processor, a memory, a transmitter, a receiver, and the like. The second network entity 552 may include one or more components as described with reference to the second network entity 550. In some embodiments, the first network entity 550 and the second network entity 552 are included in the same device or correspond to the same device.

[0113] In a particular implementation, the wireless communication system 500 includes a 5G network. For example, the UE 115 may include a 5G UE (e.g., a UE configured to operate according to a 5G network). The network entities 550, 552 may include 5G base stations (e.g., base stations configured to operate according to a 5G network).

[0114] In some embodiments, the UE 115 may be configured to measure an uplink (UL) average packet data convergence protocol (PDCP) packet queuing delay measurement (D1) (e.g., 521) for dual connectivity (DC) operation. For example, when configured for a non-split bearer, the UE 115 may receive a configuration (e.g., 570) for D1 measurement from a secondary node (SN) (e.g., 552) or a master node (MN) (e.g., 550). The UE 115 may report the average UL PDCP packet queuing delay to the node (e.g., SN or MN) (e.g., 570) from which the UE 115 receives the measurement configuration. As another example, when configured for a split bearer with one PDCP entity and multiple radio link control (RLC) branches, the UE 115 may calculate the UL average PDCP packet queuing delay. For illustration, in some embodiments, the UE 115 may calculate a single D1 value and may not distinguish between PDCP packets transmitted to the MN (e.g., 550) or the SN (e.g., 552). In such an implementation, the UE 115 may send a report 572 (e.g., D1 report) to the node (e.g., 570) from which the UE 115 receives its UE configuration or to both the MN (e.g., 550) and the SN (e.g., 552). In other implementations, the UE 115 may separately calculate (e.g., average) the PDCP packet queuing delay for packets transmitted to the MN and the SN. In such an implementation, the UE 115 may report two D1 values along with MN D1 and SN D1 indicators to the same node from which the UE 115 receives its configuration. Alternatively, the UE 115 may report the two D1 values separately to the MN and the SN, e.g., report MN D1 to the MN and report SN D1 to the SN.

[0115] During operation of the wireless communication system 400, the UE 115 determines the bearer type of the UE 115. For example, the UE 115 may determine the bearer type based on the bearer information 428. The bearer type may include a non-split bearer type or a split bearer type.

[0116] The UE 115 may perform one or more layer 2 measurements. Based on the one or more layer 2 measurements, the UE 115 may generate a UL delay measurement 520. The UL delay measurement 520 may include or correspond to a D1 measurement 520, delay information 521, MN information 522, SN information, or a combination thereof.

[0117] The UE 115 may send an uplink (UL) delay measurement based on the bearer type. In some embodiments, sending the UL delay measurement includes: sending one or more measurement reports (e.g., one or more measurement reports 572).

[0118] In some embodiments, method 800 may include: when the UE 115 (e.g., bearer type) includes a non-split bearer, sending the UL delay measurement to the SN or MN (e.g., 570) from which the UE 115 received the configuration message.

[0119] In other implementations, when the UE 115 (e.g., bearer type) includes a split bearer with one PDCP entity and multiple RLC supports, the UE 115 determines the UL delay measurements for the MN and the SN. For example, the UL delay measurement may be a single value. In such an implementation, the UL delay measurement is sent to the SN or MN from which the UE 115 received the configuration message (e.g., 570). Alternatively, the UL delay measurement may be sent to both the SN and the MN.

[0120] In other implementations, when the UE 115 includes a split bearer with one PDCP entity and multiple RLC supports, the UE 115 may calculate a first UL delay measurement for the MN and calculate a second UL delay measurement for the SN. In some embodiments, the UE 115 may send the first UL delay measurement, the MN indicator corresponding to the first UL delay measurement, the second UL delay measurement, the SN indicator corresponding to the second UL delay measurement, or a combination thereof, to the SN or MN from which the UE received the configuration message. In other embodiments, sending the UL delay measurement includes: sending the first UL delay measurement to the MN and sending the second UL delay measurement to the SN.

[0121] Thus, the present disclosure describes radio access network (RAN)-centric data collection for a UE configurable for DC / CA operation. For example, the operations described herein provide Layer 2 (L2) measurements configured to support uplink (UL) delay measurements for a UE configured for dual connectivity (DC) operation. This data collection can be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, and new radio (NR) capabilities and / or features.

[0122] Figures 6 - 8 is a flowchart showing an example method performed by a UE for communication. For example, example blocks of these methods may cause the UE to perform data collection associated with dual connectivity (DC) / carrier aggregation (CA) operations in accordance with some aspects of the present disclosure. Also refer to the UE 115 as shown in Figure 10 to describe these example blocks. Figure 10 is a block diagram conceptually showing an example design of a UE configured to perform data collection associated with dual connectivity (DC) / carrier aggregation (CA) operations, according to one aspect of the present disclosure. The UE 115 includes as for Figure 2 or Figures 3 - 5The structure, hardware, and components shown in UE 115. For example, UE 115 includes a controller / processor 280 for executing logic or computer instructions stored in a memory 282 and for controlling the components of UE 115 that provide the features and functionality of UE 115. Under the control of the controller / processor 280, UE 115 transmits and receives signals via radio devices 1001a-r and antennas 252a-r. As Figure 2 shown for UE115 in

[0123] As shown in the figure, the memory 282 may include measurement logic 1002, a position detector 1003 (e.g., a Global Positioning System (GPS)), a fault detector 1004, a failure report generator 10005, bearer logic 1006, a delay report generator 1007, and a timer 1008. The measurement logic 1002 may be configured to monitor or measure data and generate or calculate the measured data (e.g., result data). For example, the data monitored, measured, generated, or calculated by the measurement logic 1002 may include or correspond to measurement results 320, early measurement data 321, MDT data 322, measurement logs 372, failure information 424, MCG failure information 425, MCG recovery failure information 426, failure reports 472, D1 measurements 520, delay information 521, MN information 522, SN information 523, or a combination thereof. Additionally or alternatively, the measurement logic 1002 may be configured to generate one or more messages or one or more reports, such as a measurement log 372 or a measurement report 572. The position detector 1003 (e.g., a Global Positioning System (GPS)) may be configured to determine, receive, or identify location information 319. The fault detector 1004 may be configured to detect communication link failures. In some embodiments, the fault detector 1004 is configured to generate fault data, such as failure information 424, MCG failure information 425, MCG recovery failure information 426, failure reports 472. The failure report generator 1005 may be configured to generate failure reports, such as failure reports 472. The bearer logic 1006 may be configured to perform one or more operations based on bearer information (e.g., bearer information 428). The delay report generator 1007 may be configured to generate one or more delay reports, such as a measurement report 572. The timer 1008 may include or correspond to time 317. In some aspects, the measurement logic 1002, the position detector 1003 (e.g., a Global Positioning System (GPS)), the fault detector 1004, the failure report generator 10005, the bearer logic 10006, the delay report generator 1007, the timer 1008, or a combination thereof may include or correspond to the processor 302. The UE 115 may receive signals and / or send signals to one or more network entities (e.g., the base station 105, network entities 350, 450, 452, 550, 552, the core network, core network devices, or network entities as shown in Figure 11 the figure).

[0124] Reference Figure 6, the figure shows an example flowchart of method 600 for UE operations for communication. In some embodiments, method 600 may be performed by UE 115. In other implementations, method 600 may be performed by a device configured for wireless communication. For example, the device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations of method 600. In other implementations, method 600 may be performed or implemented using a non-transitory computer-readable medium having program code recorded thereon. The program code may be computer-executable program code for causing a computer to perform the operations of method 600.

[0125] As shown in block 602, the UE determines a minimized drive test (MDT) result. The MDT result may include or correspond to MDT data 322. For example, UE 115 may use measurement logic 1002 to determine the MDT result.

[0126] At 604, the UE determines an early measurement result. The early measurement result may include or correspond to early measurement data 321. The early measurement result may include dual connectivity / carrier aggregation (DC / CA) early measurement results, which may be determined when the UE is in an inactive state (e.g., idle state, low power state, or inactive state or a combination thereof). Additionally or alternatively, the early measurement result may include a serving frequency measurement, a non-serving frequency measurement, or a combination thereof. For example, UE 115 may use measurement logic 1002 to determine the early measurement result.

[0127] At 606, the UE transmits a report including the MDT result, the early measurement result, or a combination thereof. The report may include or correspond to measurement log 372. The report may be generated using measurement logic 1002. In some embodiments, the UE may receive an information request for one or more MDT results, one or more early measurement results, or a combination thereof from a network entity. As an illustrative non-limiting example, the network element may include or correspond to base station 105, network entities 350, 450, 452, 550, 552, 1105, a network device, or a network core. In such an implementation, the UE may transmit the report in response to the information request. UE 115 may use radio devices 1001a-r and antennas 252a-r to transmit the report.

[0128] In some embodiments, method 600 includes: the UE determines location information associated with the MDT. The location information may include or correspond to location information 319. For example, UE 115 may use location detector 1003 to determine the location information. In some such implementations, method 600 further includes: the UE stores the early measurement result together with the location information.

[0129] In some embodiments, early measurement result information is determined according to a first interval, MDT result information is determined according to a second interval, or a combination thereof. The first interval and the second interval may include or correspond to the logging interval 323. The first interval and the second interval may be the same interval or different intervals. The UE 115 may use the timer 1008 to determine the expiration of a time period corresponding to the first interval or the second interval.

[0130] In some embodiments, method 600 may include: the UE generating a first log of one or more MDT result entries, generating a second log of one or more early measurement result entries, or a combination thereof. The first log and the second log may include or correspond to the measurement results 320. In some embodiments, when early measurement results are not available, the UE may generate blank early measurement result entries. The UE 115 may use the measurement logic 1002 to generate the first log, the second log, or a combination thereof.

[0131] In some embodiments, method 600 may include: the UE receiving a measurement configuration message from a network element. As an illustrative non-limiting example, the network element may include or correspond to the base station 105, network entities 350, 450, 452, 550, 552, 1105, network devices, or the network core. The measurement configuration message may include or correspond to the measurement configuration 370. The measurement configuration message may include a storage configuration, a reporting configuration, or a combination thereof. The UE 115 may use the radio devices 1001a-r and the antennas 252a-r to receive the measurement configuration report. In some such implementations, method 600 further includes: the UE storing the MDT results and the early measurement results in the same log file based on the measurement configuration message. Alternatively, method 600 may include: the UE storing the MDT results in a first log file and storing the early measurement results in a second log file based on the measurement configuration message. In some such implementations, sending a report includes: sending a first report including the MDT results, sending a second report including the early measurement results, or a combination thereof.

[0132] Thus, method 600 enables radio access network (RAN)-centric data collection for UEs configurable for DC / CA operation. For example, the operations described herein provide the collection, storage, reporting, or a combination thereof of DC / CA early measurement results associated with logged minimized drive test (MDT). This data collection can be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, and new radio (NR) capabilities and / or features.

[0133] Reference Figure 7, the figure shows an example flowchart of a method 700 for UE operation in communication. In some embodiments, method 700 may be performed by UE 115. In other implementations, method 700 may be performed by a device configured for wireless communication. For example, the device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations of method 700. In other implementations, method 700 may be performed or implemented using a non-transitory computer-readable medium having program code recorded thereon. The program code may be computer-executable program code for causing a computer to perform the operations of method 700.

[0134] As shown at block 702, the UE generates a radio link failure (RLF) report based on the detection of a primary cell group (MCG) fast recovery failure. The RLF report may include or correspond to a failure report 472. The RLF report may include MCG failure information, MCG recovery failure information, or a combination thereof. The MCG failure information and the MCG recovery failure information may include or correspond to MCG failure information 425 and MCG recovery failure information 426, respectively. UE 115 may use measurement logic 1002, a fault detector 1004, a failure report generator 1005, or a combination thereof to generate the RLF report. In some embodiments, the UE is in a dual connectivity / carrier aggregation (DC / CA) configuration.

[0135] In some embodiments, the MCG failure information includes available measurement results of the MCG, MCG link failure causes, available measurement results of the secondary cell group (SCG), available measurement results of non-serving cells, or a combination thereof. Additionally or alternatively, the MCG recovery failure information includes available measurement results of the SCG, available measurement results of the MCG, available secondary node (SN) measurement results, or a combination thereof. As an illustrative non-limiting example, the MCG recovery failure information may include an MCG recovery failure cause, such as a protection timer expiration indication or an SCG link failure detection. Additionally or alternatively, the MCG recovery failure information may include a signaling radio bearer type, such as a split SRB or a signaling radio bearer type 3 (SRB3), as an illustrative non-limiting example.

[0136] At 704, method 700 further includes: the UE sending the RLF report to a secondary cell group (SCG). The SCG may include or correspond to a network entity, such as base station 105, network entities 350, 450, 452, 550, 552, 1105, network equipment, or a network core, as an illustrative non-limiting example. UE 115 may use radio devices 1001a-r and antennas 252a-r to send the RLF report.

[0137] In some embodiments, method 700 further includes: detecting a failure of fast MCG recovery. The fast MCG recovery failure can be detected based on expiration of a guard time, radio link failure (RLF) of both MCG and SCG, or failure to apply a radio resource control (RRC) reconfiguration message.

[0138] Accordingly, method 700 enables radio access network (RAN)-centric data collection for a UE configurable for DC / CA operation. For example, the operations described herein provide a radio link failure (RLF) report that is configured to support fast master cell group (MCG) recovery failure via a secondary cell group (SCG). This data collection can be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, and new radio (NR) capabilities and / or features.

[0139] Reference Figure 8 , which illustrates an example flowchart of a method 800 for UE operation in communication. In some embodiments, method 800 can be performed by UE 115. In other implementations, method 800 can be performed by a device configured for wireless communication. For example, the device can include at least one processor and a memory coupled to the processor. The processor can be configured to perform the operations of method 800. In other implementations, method 800 can be performed or implemented using a non-transitory computer-readable medium having program code recorded thereon. The program code can be computer-executable program code for causing a computer to perform the operations of method 800.

[0140] As shown at block 802, method 800 includes: determining, by a user equipment (UE) configured for dual connectivity (DC), a bearer type of the UE. As an illustrative non-limiting example, the bearer type can include a non-split bearer type or a split bearer type. The bearer type can include or correspond to bearer information 428. UE 115 can use bearer logic 1006 to determine the bearer type.

[0141] In some embodiments, method 800 can include: performing one or more layer 2 measurements and generating, by the UE, a UL latency measurement based on the one or more layer 2 measurements. UE 115 can use measurement logic 1002 to perform these measurements. UE 115 can generate a UL latency measurement.

[0142] At 804, method 800 includes: sending, from a UE, bearer type-based uplink (UL) latency measurements. For example, the UL latency measurements may include or correspond to D1 measurements 520, latency information 521, MN information 522, SN information, or a combination thereof. The UL latency measurements may include UL average packet data convergence protocol (PDCP) packet queuing latency measurements (D1). The UE 115 may use radio devices 1001a-r and antennas 252a-r to send the UL latency measurements. In some embodiments, sending the UL latency measurements includes sending one or more measurement reports, such as one or more measurement reports 572.

[0143] In some embodiments, method 800 may include: when the UE includes a non-split bearer, receiving, by the UE, a configuration message from a secondary node (SN) or a master node (MN). The configuration message may include or correspond to a measurement configuration message 570. Sending the UL latency measurements to the SN or MN from which the UE received the configuration message.

[0144] In some embodiments, method 800 may include: when the UE includes a split bearer with one PDCP entity and multiple RLC supports, calculating UL latency measurements for the MN and the SN. For example, the UL latency measurements may be a single value. In some embodiments, method 800 further includes: receiving, by the UE, a configuration message from the SN or MN, and sending the UL latency measurements to the SN or MN from which the UE received the configuration message. Alternatively, the UL latency measurements may be sent to the SN and the MN.

[0145] In other implementations, method 800 may include: when the UE includes a split bearer with one PDCP entity and multiple RLC supports, calculating a first UL latency measurement for the MN and calculating a second UL latency measurement for the SN. In some embodiments, method 800 further includes: receiving, by the UE, a configuration message from the SN or MN. In some such implementations, sending the UL latency measurements includes: sending the first UL latency measurement, an MN indicator corresponding to the first UL latency measurement, the second UL latency measurement, an SN indicator corresponding to the second UL latency measurement, or a combination thereof, to the SN or MN from which the UE received the configuration message. In other implementations, sending the UL latency measurements includes: sending the first UL latency measurement to the MN, and sending the second UL latency measurement to the SN.

[0146] Accordingly, method 800 enables RAN - centric data collection for a UE configurable for DC / CA operations. For example, the operations described herein provide Layer 2 (L2) measurements that are configured to support uplink (UL) latency measurements for UEs configured for dual - connectivity (DC) operations. This data collection can be advantageously used to improve device (e.g., UE) performance such as battery life, throughput, latency, reliability, and new radio (NR) capabilities and / or features.

[0147] It should be noted that one or more blocks (or operations) referred to Figures 6 - 8 in the description can be combined with one or more blocks (or operations) in another figure. For example, Figures 6 - 8 one or more of the blocks of Figure 2 or Figures 3 - 5 can be combined with one or more blocks (or operations) of another of Figures 1 - 8 and Figure 10 In addition or alternatively, one or more operations referred to above in Figures 1 - 8 and Figure 10 can be combined with one or more operations referred to in Figure 11 the description.

[0148] Figure 9 is a flowchart showing an example method 900 for communication performed by a network entity. For example, according to some aspects of the present disclosure, example blocks of method 900 can cause the network entity to transmit a configuration message. These example blocks will also be described with respect to Figure 11 the network entity 1105 shown. Figure 11 is a block diagram conceptually showing an example design of a network entity 1105 (e.g., base station 105, network entities 350, 450, 452, 550, 552, 1105, a network or a core network, as illustrative non - limiting examples).

[0149] The network entity 1105 includes the structures, hardware, and components as shown for the Figures 2 - 5 network entities (e.g., 105, 350, 450, 452, 550, 552) of Figures 2 - 5 . For example, the network entity 1105 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and controls components that provide the characteristics and functions of the network entity 1105. Under the control of the controller / processor 240, the network entity 1105 transmits and receives signals via radio devices 1101a - t and antennas 234a - t. As Figure 2As shown for network entity 1105 (e.g., 105), radio units 1101a-t include various components and hardware, which include modulators / demodulators 232a-t, transmit processors 220, TX MIMO processors 230, MIMO detectors 236, and receive processors 238. As shown, memory 242 may include configuration generator 1102, communication logic 1103, and timer 1104. Configuration generator 1102 may be configured to generate one or more configurations or configuration messages, such as measurement configuration 370, configuration message 470, or measurement configuration message 570. Communication logic 1103 may enable network entity 1105 to perform one or more operations for wireless communication. Timer 1104 may be configured to enable network entity 1105 to determine the expiration of one or more time periods. In some aspects, configuration generator 1102, communication logic 1103, and timer 1104, or combinations thereof, may include or correspond to processor 362. Network entity 1105 may receive signals from and / or send signals to a UE (e.g., UE 115 as shown in Figure 10 ).

[0150] Reference Figure 9 , which shows an example flowchart of method 900 for network entity operations for communication. In some embodiments, method 900 may be performed by network entity 601 (e.g., 105, 140, 442). In other implementations, method 900 may be performed by a device configured for wireless communication. For example, the device may include at least one processor, and a memory coupled to the processor. The processor may be configured to perform the operations of method 900. In other implementations, method 900 may be performed or implemented using a non-transitory computer-readable medium having program code recorded thereon. The program code may be computer-executable program code for causing a computer to perform the operations of method 900.

[0151] As shown at block 902, method 900 includes: a network entity sending a measurement configuration message. The measurement configuration message may include or correspond to measurement configuration 307. For example, network entity 1105 may use configuration generator 1102 to generate the measurement configuration message. Network entity 1105 may use radio devices 1101a-t, antennas 234a-t, and communication logic 1103 to send the measurement configuration message.

[0152] The measurement configuration message may include a storage configuration, a reporting configuration, or a combination thereof. The storage configuration may include a storage configuration for minimized drive test (MDT) results, early measurement results, or a combination thereof. The reporting configuration may include a reporting configuration for MDT results, early measurement results, or a combination thereof. Additionally or alternatively, the measurement configuration message may include an information request for one or more MDT results, one or more early measurement results, or a combination thereof.

[0153] At 904, method 900 further includes: a network entity receiving MDT results, early measurement results, or a combination thereof. In some embodiments, the early measurement results include dual connectivity / carrier aggregation (DC / CA) early measurement results. The MDT results, early measurement results, or a combination thereof received by the network entity may include or correspond to measurement log 372. For illustration purposes, network entity 601 may use radio devices 1101a-t, antennas 234a-t, and communication logic 1103 to receive MDT results, early measurement results, or a combination thereof. The MDT results, early measurement results, or a combination thereof may be received from a UE such as UE 115.

[0154] In some embodiments, the storage configuration indicates storing minimized drive test (MDT) results and early measurement results in a single log file. In other implementations, the storage configuration indicates storing MDT results in a first log file and early measurement results in a second log file. Additionally or alternatively, the reporting configuration may indicate transmitting MDT results and early measurement results in the same reporting message or in separate reporting messages.

[0155] Thus, method 900 enables RAN-centric data collection for UEs configurable for DC / CA operation. For example, the operations described herein provide for the collection, storage, reporting, or a combination thereof of DC / CA early measurement results associated with recorded minimized drive test (MDT). This data collection can be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, and new radio (NR) capabilities and / or features.

[0156] It should be noted that one or more blocks (or operations) referenced Figure 9 may be combined with one or more blocks (or operations) in another figure. For example, Figure 9 one or more blocks of Figure 2 or Figures 3 - 5 may be combined with one or more blocks (or operations) of another of Figures 1 - 5 , 9, and Figure 11 Additionally or alternatively, one or more operations referenced above Figure 10 may be combined with one or more operations referenced

[0157] In some aspects, data collection for dual connectivity (DC) / carrier aggregation (CA) may include a wireless device receiving: minimized drive test (MDT) results determined by a user equipment (UE); early measurement results; and sending a report including the MDT results, the early measurement results, or a combination thereof. In some embodiments, the wireless device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the wireless device. In other embodiments, program code is recorded on a non-transitory computer-readable medium, and the program code may be executed by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

[0158] In a first aspect, the early measurement results include dual connectivity / carrier aggregation (DC / CA) early measurement results.

[0159] In a second aspect, either alone or in combination with the first aspect, the early measurement results include resident frequency measurements, non-resident frequency measurements, or a combination thereof; and the early measurement results are determined by the UE in an inactive state.

[0160] In a third aspect, either alone or in combination with one or more of the first to second aspects, it may include: determining location information associated with the MDT; and storing the early measurement results together with the location information.

[0161] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the early measurement result information is determined according to a first interval; and the MDT result information is determined according to a second interval.

[0162] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first interval and the second interval are the same interval.

[0163] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the first interval and the second interval are different.

[0164] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, it may include: generating a first log of one or more MDT result entries; and generating a second log of one or more early measurement result entries.

[0165] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, it may include: generating blank early measurement result entries when the early measurement results are not available.

[0166] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, it may include: receiving a measurement configuration message from a network element, the measurement configuration message including a storage configuration, a reporting configuration, or a combination thereof.

[0167] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, it may include: storing the MDT result and the early measurement result in the same log file based on the measurement configuration message.

[0168] In an eleventh aspect, either alone or in combination with one or more of the first to ninth aspects, it may include: storing the MDT result in a first log file and storing the early measurement result in a second log file based on the measurement configuration message.

[0169] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, sending the report includes: sending a first report including the MDT result; sending a second report including the early measurement result; or a combination thereof.

[0170] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, it may include: receiving an information request for one or more MDT results, one or more early measurement results, or a combination thereof from a network entity.

[0171] In some aspects, data collection for dual connectivity (DC) / carrier aggregation (CA) may include a wireless device: receiving a measurement configuration message sent by a network entity, the measurement configuration message including: a storage configuration for a minimized drive test (MDT) result, an early measurement result, or a combination thereof; a reporting configuration for the MDT result, the early measurement result, or a combination thereof; or a combination of the storage configuration and the reporting configuration; and receiving the MDT result, the early measurement result, or a combination thereof from the network entity. In some embodiments, the wireless device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the wireless device. In other embodiments, program code is recorded on a non-transitory computer-readable medium, and the program code can be executed by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

[0172] In a fourteenth aspect, the early measurement result includes a dual connectivity / carrier aggregation (DC / CA) early measurement result.

[0173] In a fifteenth aspect, either alone or in combination with the fourteenth aspect, the storage configuration indicates that the minimized drive test (MDT) results and the early measurement results are stored in a single log file.

[0174] In a sixteenth aspect, either alone or in combination with one or more of the fourteenth to fifteenth aspects, the storage configuration indicates that the MDT results are stored in a first log file and the early measurement results are stored in a second log file.

[0175] In a seventeenth aspect, either alone or in combination with one or more of the fourteenth to sixteenth aspects, the reporting configuration indicates that the MDT results and the early measurement results are sent in the same report message or in separate report messages.

[0176] In an eighteenth aspect, either alone or in combination with one or more of the fourteenth to seventeenth aspects, the measurement configuration message includes an information request for one or more MDT results, one or more early measurement results, or a combination thereof.

[0177] In some aspects, data collection for dual connectivity (DC) / carrier aggregation (CA) may include a wireless device performing the following operations: generating a radio link failure (RLF) report by a user equipment (UE) based on detection of a primary cell group (MCG) fast recovery failure, the RLF report including MCG failure information, MCG recovery failure information, or a combination thereof; and sending the RLF report by the UE to a secondary cell group (SCG). In some embodiments, the wireless device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the wireless device. In other embodiments, program code is recorded on a non-transitory computer-readable medium, and the program code may be executed by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

[0178] In a nineteenth aspect, the UE is in a dual connectivity / carrier aggregation (DC / CA) configuration.

[0179] In a twentieth aspect, either alone or in combination with the nineteenth aspect, the MCG failure information includes available measurement results of the MCG, MCG link failure causes, available measurement results of the SCG, available measurement results of non-serving cells, or a combination thereof.

[0180] In a twenty-first aspect, either alone or in combination with one or more of the nineteenth to twentieth aspects, the MCG recovery failure information includes: available measurement results of the SCG, available measurement results of the MCG, available serving node (SN) measurement results, or a combination thereof.

[0181] In a twenty-second aspect, either alone or in combination with one or more of the nineteenth to twenty-first aspects, the MCG recovery failure information includes the reason for the MCG recovery failure.

[0182] In a twenty-third aspect, either alone or in combination with one or more of the nineteenth to twenty-second aspects, the reason for the MCG recovery failure includes a protection timer expiration indication or an SCG link failure detection.

[0183] In a twenty-fourth aspect, either alone or in combination with one or more of the nineteenth to twenty-third aspects, the MCG recovery failure information includes the signaling radio bearer type.

[0184] In a twenty-fifth aspect, either alone or in combination with one or more of the nineteenth to twenty-fourth aspects, the signaling radio bearer (SRB) type includes a split SRB or SRB type 3 (SRB3).

[0185] In a twenty-sixth aspect, either alone or in combination with one or more of the nineteenth to twenty-fifth aspects, the fast MCG recovery failure is based on the expiration of the protection time, the radio link failure (RLF) of both the MCG and the SCG, or the failure of applying a radio resource control (RRC) reconfiguration message.

[0186] In some aspects, data collection for dual connectivity (DC) / carrier aggregation (CA) may include a wireless device performing the following operations: determining, by a user equipment (UE) configured for dual connectivity (DC), the bearer type of the UE; and transmitting, from the UE, uplink (UL) delay measurements based on the bearer type. In some embodiments, the wireless device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the wireless device. In other embodiments, program code is recorded on a non-transitory computer-readable medium, and the program code may be executed by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

[0187] In a twenty-seventh aspect, the bearer type includes a non-split bearer type or a split bearer type.

[0188] In a twenty-eighth aspect, either alone or in combination with the twenty-seventh aspect, the UL delay measurement includes an UL average packet data convergence protocol (PDCP) packet queuing delay measurement (D1).

[0189] In a twenty-ninth aspect, either alone or in combination with one or more of the twenty-seventh to twenty-eighth aspects, it may include: performing one or more Layer 2 measurements; and generating the UL delay measurement based on the one or more Layer 2 measurements.

[0190] In a thirtieth aspect, either alone or in combination with one or more of the twenty-seventh to twenty-ninth aspects, it may include: when the UE includes a non-split bearer, receiving a configuration message from a secondary node (SN) or a master node (MN); and wherein, sending the UL delay measurement to the SN or MN from which the UE receives the configuration message.

[0191] In a thirty-first aspect, either alone or in combination with one or more of the twenty-seventh to twenty-ninth aspects, it may include: when the UE includes a split bearer with one PDCP entity and multiple RLC supports, calculating the UL delay measurement for the MN and the SN.

[0192] In a thirty-second aspect, either alone or in combination with the thirty-first aspect, the UL delay measurement is a single value.

[0193] In a thirty-third aspect, either alone or in combination with one or more of the thirty-first to thirty-second aspects, it may include: receiving a configuration message from the SN or the MN; and wherein, sending the UL delay measurement to the SN or MN from which the UE receives the configuration message.

[0194] In a thirty-fourth aspect, either alone or in combination with one or more of the thirty-first to thirty-third aspects, sending the UL delay measurement to the SN and the MN.

[0195] In a thirty-fifth aspect, either alone or in combination with one or more of the thirty-first to thirty-second aspects, it may include: when the UE includes a split bearer with one PDCP entity and multiple RLC supports: calculating a first UL delay measurement for the MN; and calculating a second UL delay measurement for the SN.

[0196] In a thirty-sixth aspect, either alone or in combination with the thirty-fifth aspect, it may include: receiving a configuration message from the SN or the MN; and wherein, sending the UL delay measurement includes: sending the first UL delay measurement, an MN indicator corresponding to the first UL delay measurement, the second UL delay measurement, and an SN indicator corresponding to the second UL delay measurement to the SN or MN from which the UE receives the configuration message.

[0197] In a thirty-seventh aspect, either alone or in combination with the thirty-fifth aspect, sending the UL delay measurement includes: sending the first UL delay measurement to the MN; and sending the second UL delay measurement to the SN.

[0198] Those of ordinary skill in the art should understand that information and signals can be represented using any of a variety of different technologies and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0199] As described herein Figures 1 - 11 The functional blocks and modules described herein include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software codes, firmware codes, etc., or any combination thereof. In addition, the features discussed herein can be implemented by dedicated processor circuits, by executable instructions, and / or their combination.

[0200] Those of ordinary skill in the art should also understand that the various exemplary logical blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the above description of the various exemplary components, blocks, modules, circuits, and steps has been presented generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system. Skilled artisans can implement the described functionality in a flexible manner for each particular application, but such implementation decisions should not be construed as departing from the scope of the present disclosure. Skilled artisans should also readily recognize that the order or combination of the components, methods, or interactions described herein is merely exemplary, and the components, methods, or interactions of the various aspects of the present disclosure can be combined or performed in a manner different from those shown and described herein.

[0201] A general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, can be used to implement or perform the various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure herein. The general-purpose processor can be a microprocessor, or, alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, several microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0202] The steps of the methods or algorithms described in connection with the content disclosed herein can be directly embodied as hardware, software modules executed by a processor, or a combination of both. The software modules can be located in a RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable hard disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. The ASIC can be located in a user terminal. Of course, the processor and the storage medium can also exist as discrete components in the user terminal.

[0203] In one or more exemplary designs, the functions described herein can be implemented in hardware, software, firmware, or any combination thereof using computer-executable instructions. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. The computer-readable medium includes computer storage media and communication media, where the communication media includes any medium that facilitates the transfer of a computer program from one place to another. The computer-readable storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other medium that can be used to carry or store desired program code units in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Additionally, a connection can be properly termed a computer-readable medium. By way of example, if the software is transmitted using coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL) from a website, server, or other remote source, then the coaxial cable, fiber optic cable, twisted pair, or DSL is included in the definition of the medium. As used herein, disk and optical disk include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), hard disk, solid state disk, and Blu-ray disk, where disks typically reproduce data magnetically, while optical disks optically reproduce data with lasers. Combinations of the above should also be included within the scope of protection of computer-readable media.

[0204] As used herein, which includes the claims, when the term "and / or" is used in a list of two or more items, it means any one of the listed items, or any combination of two or more of the listed items. For example, if a complex is described as including components A, B, and / or C, the complex can include only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Additionally, as used herein, which includes the claims, the "or" used in list items that end with "at least one of" indicates a disjunctive list, such that for example the list "at least one of A, B, or C" means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C), or any one of any combination thereof.

[0205] The foregoing has been described surrounding the present disclosure so as to enable any ordinary person skilled in the art to make or use the present disclosure. Various modifications to the disclosed content will be readily apparent to those of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described in this application, but is consistent with the broadest scope of the principles and novel features disclosed herein.

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: Receiving a measurement configuration message from a network entity, the measurement configuration message comprising: A storage configuration for minimized drive test (MDT) results, early measurement results, or a combination thereof; A reporting configuration for the MDT results, the early measurement results, or a combination thereof; or A combination of the storage configuration and the reporting configuration; Determining minimized drive test (MDT) results; Determining early measurement results, wherein the early measurement results are determined by the UE in an inactive state, and wherein the early measurement results include dual connectivity / carrier aggregation (DC / CA) early measurement results; and Sending a report comprising the MDT results, the early measurement results, or a combination thereof, wherein the early measurement result information is determined according to a first interval, and the MDT result information is determined according to a second interval.

2. The method according to claim 1, wherein: The early measurement results include resident frequency measurements, non-resident frequency measurements, or a combination thereof.

3. The method according to claim 1, further comprising: Determining location information associated with the MDT; And Storing the early measurement results together with the location information.

4. The method according to claim 1, wherein The first interval and the second interval are the same interval.

5. The method according to claim 1, further comprising: Generating a first log of one or more MDT result entries; And Generating a second log of one or more early measurement result entries.

6. The method according to claim 1 further comprises: Generating blank early measurement result entries when the early measurement results are not available.

7. The method according to claim 1, wherein, Sending the report comprises: Sending a first report comprising the MDT results; Sending a second report comprising the early measurement results; or A combination thereof.

8. A method for wireless communication performed by a network entity, the method comprising: Sending a measurement configuration message to a user equipment (UE), the measurement configuration message comprising: A storage configuration for minimized drive test (MDT) results, early measurement results, or a combination thereof; A reporting configuration for the MDT results, the early measurement results, or a combination thereof; or A combination of the storage configuration and the reporting configuration, wherein the early measurement result information is determined according to a first interval, and the MDT result information is determined according to a second interval; and Receiving the MDT results, the early measurement results, or a combination thereof, wherein the early measurement results are determined by the UE in an inactive state, and wherein the early measurement results include dual connectivity / carrier aggregation (DC / CA) early measurement results.

9. According to the method described in claim 8, wherein, The storage configuration indicates storing the minimized drive test (MDT) results and the early measurement results in a single log file.

10. The method according to claim 8, wherein, The storage configuration indicates storing the MDT results in a first log file and storing the early measurement results in a second log file.

11. The method according to claim 8, wherein: The reporting configuration is configured to indicate sending the MDT results and the early measurement results in the same report message or in separate report messages; or The measurement configuration message includes an information request for one or more MDT results, one or more early measurement results, or a combination thereof.

12. A user equipment (UE) configured for wireless communication, the UE comprising: at least one processor; and a memory coupled to the at least one processor, wherein the at least one processor is configured to: receive a measurement configuration message from a network entity, the measurement configuration message including: a storage configuration for minimized drive test (MDT) results, early measurement results, or a combination thereof; a reporting configuration for the MDT results, the early measurement results, or a combination thereof; or a combination of the storage configuration and the reporting configuration; determine minimized drive test (MDT) results; determine early measurement results, wherein the early measurement results are determined by the UE in an inactive state, and wherein the early measurement results include dual connectivity / carrier aggregation (DC / CA) early measurement results; and initiate transmission of a report including the MDT results, the early measurement results, or a combination thereof, wherein the early measurement result information is determined according to a first interval, and the MDT result information is determined according to a second interval.

13. The UE according to claim 12, wherein: the early measurement results include a resident frequency measurement, a non-resident frequency measurement, or a combination thereof.

14. The UE according to claim 12, wherein, the at least one processor is configured to: determine location information associated with the MDT; and store the early measurement results together with the location information.

15. The UE according to claim 12, wherein, the first interval and the second interval are different.

16. The UE according to claim 12, wherein, the at least one processor is configured to: generate a first log of one or more MDT result entries; and generate a second log of one or more early measurement result entries.

17. The UE according to claim 12, wherein, the at least one processor is configured to: generate blank early measurement result entries when the early measurement results are not available.

18. The UE according to claim 12, wherein To send the report, the at least one processor is configured to: initiate transmission of a first report including the MDT results; initiate transmission of a second report including the early measurement results; or a combination thereof.

Images