Radio access network (RAN) centric data collection for dual connectivity (DC) / carrier aggregation (CA)

Abstract

The invention relates to radio access network (RAN) centric data collection for dual connectivity (DC) / carrier aggregation (CA). This disclosure provides systems, methods, and apparatus, including computer programs encoded on a computer storage medium, for wireless communication. In one aspect of the present disclosure, a method for wireless communication includes determining, by a user equipment (UE), a minimization of 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. Other aspects and features are also claimed and described.

Description

[0001] This application is a divisional application of the Chinese patent application with the application date of February 15, 2020, application number 202080096021.1, and invention name “Radio Access Network (RAN)-centric Data Collection for Dual Connectivity (DC) / Carrier Aggregation (CA)”. Technical Field

[0002] Generally speaking, aspects of the present disclosure relate to wireless communication systems. More specifically, but not limited to, aspects of the present disclosure relate to data collection for dual connectivity (DC) / carrier aggregation (CA). Background Art

[0003] Wireless communication networks are widely deployed to provide various communication services, such as voice, video, packet data, messaging, broadcast, and so on. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. These networks, which are typically multiple-access networks, support communication for multiple users by sharing the available network resources.

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

[0005] A base station may send data and control information to a UE on the downlink and / or receive data and control information from a UE on the uplink. On the downlink, transmissions from a base station may encounter interference from transmissions from neighboring base stations or from other wireless radio frequency (RF) transmitters. On the uplink, transmissions from a UE may encounter interference from uplink transmissions from other UEs communicating with neighboring base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.

[0006] As the demand for mobile broadband access continues to increase, the more UEs accessing long-range wireless communication networks and the more short-range wireless systems deployed in the community, the greater the likelihood of network interference and congestion. Continuing to research and develop wireless technologies will not only meet the growing demand for mobile broadband access, but also improve and enhance the user's mobile communication experience. For example, research and development has helped advance new radio (NR) technology that utilizes 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 technology with traditional technology presents various challenges and obstacles. For the sake of illustration, there are challenges in combining NR technology in a device and improving device performance relative to NR technology. As a specific and non-limiting example, incorporating NR technology into a device has been shown to be related to battery life, throughput, latency, and reliability. Summary of the Invention

[0007] To provide a basic understanding of the technology discussed, the following summarizes some aspects of the present disclosure. This summary is not an exhaustive overview of all anticipated features of the present disclosure, nor is it intended to identify 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 summarized form as a prelude to the detailed description that follows.

[0008] In one aspect of the present disclosure, a method for wireless communication includes: determining, by a user equipment (UE), a minimization of drive test (MDT) result; determining, by the UE, an early measurement result; and 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, an apparatus for wireless communication includes: means for determining, by a user equipment (UE), a minimization of drive test (MDT) result; means for determining, by the UE, an early measurement result; and means for transmitting, by the UE, a report including the MDT result, the early measurement result, or a combination thereof.

[0010] In another aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon, the program code including determining a minimization of 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.

[0011] 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 minimization of drive tests (MDT) result and 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.

[0012] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus 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 minimization of drive tests (MDT) results, determine early measurement results, and initiate transmission of a report including the MDT results, the early measurement results, or a combination thereof.

[0013] In another aspect of the present disclosure, a method for wireless communication includes: transmitting, by a network entity, a measurement configuration message. The measurement configuration message includes: a storage configuration for minimization of drive tests (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 also includes: receiving, by the network entity, the MDT results, the early measurement results, or a combination thereof.

[0014] In another aspect of the present disclosure, an apparatus for wireless communication includes: means for transmitting, by a network entity, a measurement configuration message. The measurement configuration message includes: a storage configuration for minimization of drive tests (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 apparatus also includes means for receiving, by the network entity, the MDT results, the early measurement results, or a combination thereof.

[0015] In another aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon. The program code includes code for sending a measurement configuration message. The measurement configuration message includes a storage configuration for minimization of drive tests (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 also includes code for receiving 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. The apparatus includes at least one processor and a memory coupled to the processor. The processor is configured to initiate transmission of a measurement configuration message. The measurement configuration message includes: a storage configuration for minimization of drive tests (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.

[0017] 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 initiate transmission of a measurement configuration message. The measurement configuration message includes: a storage configuration for minimization of drive tests (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.

[0018] 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 detection of a master cell group (MCG) fast recovery failure. The RLF report includes MCG failure information, MCG recovery failure information, or a combination thereof. The method also includes transmitting, by the UE, the RLF report to a secondary cell group (SCG).

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

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

[0021] 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 a radio link failure (RLF) report based on detection of a master cell group (MCG) fast recovery failure. The RLF report includes MCG failure information, MCG recovery failure information, or a combination thereof. The processor is further configured to initiate transmission of the RLF report to a secondary cell group (SCG).

[0022] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus 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 detection of a master 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 transmission of the RLF report to a secondary cell group (SCG).

[0023] 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 also includes sending, from the UE, an uplink (UL) delay measurement based on the bearer type.

[0024] In another aspect of the present disclosure, an apparatus for wireless communication includes: means for determining, by a user equipment (UE) configured for dual connectivity (DC), a bearer type of the UE. The apparatus also includes means for sending, from the UE, an uplink (UL) delay measurement based on the bearer type.

[0025] In another aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon, the program code including code for determining a bearer type of a user equipment (UE) configured for dual connectivity (DC); and code for initiating transmission of an uplink (UL) delay measurement based on the bearer type.

[0026] 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, by a user equipment (UE) configured for dual connectivity (DC), a bearer type of the UE; and initiate transmission of an uplink (UL) delay measurement based on the bearer type.

[0027] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus 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 transmission of an uplink (UL) delay measurement based on the bearer type.

[0028] After understanding the description of the following specific examples in conjunction with the accompanying drawings, other aspects, features, and embodiments will become apparent to those of ordinary skill in the art. Although features are discussed with respect to certain aspects and drawings below, all embodiments 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 embodiments are discussed below as being implemented as devices, systems, or methods, these exemplary embodiments may be implemented using a variety of devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] A further understanding of the nature and advantages of the present disclosure may be obtained by referring to the following drawings. In the drawings, similar components or features are given the same reference numerals. In addition, components of the same type may be distinguished by following the reference numeral with a dashed line and a second reference numeral to distinguish the similar components. If only the first reference numeral is used in the specification, the description applies to any similar component having the same first reference numeral, regardless of the second reference numeral.

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

[0031] Figure 2 is a block diagram conceptually illustrating a design of a base station and a user equipment (UE) configured in accordance with some aspects.

[0032] Figure 3 is a block diagram showing an illustrative embodiment of a system configured to provide data collection for a user equipment (UE), wherein the UE may be configured for dual connectivity (DC) / carrier aggregation (CA), in accordance with some aspects.

[0033] Figure 4 is a block diagram illustrating another illustrative embodiment of a system configured to provide data collection for a UE that may be configured for dual connectivity (DC) / carrier aggregation (CA), in accordance with some aspects.

[0034] Figure 5is a block diagram illustrating another illustrative embodiment of a system configured to provide data collection for a UE that may be configured for dual connectivity (DC) / carrier aggregation (CA), in accordance with some aspects.

[0035] Figure 6 is a flow diagram illustrating example blocks executed by a UE, according to some aspects.

[0036] Figure 7 is a flow diagram illustrating example blocks executed by a UE, according to some aspects.

[0037] Figure 8 is a flow diagram illustrating example blocks executed by a UE, according to some aspects.

[0038] Figure 9 is a flow diagram illustrating example blocks executed by a network entity, according to some aspects.

[0039] Figure 10 is a block diagram conceptually illustrating a design of a UE configured in accordance with some aspects.

[0040] Figure 11 is a block diagram conceptually illustrating a design of network entities configured in accordance with some aspects. DETAILED DESCRIPTION

[0041] The detailed description below, in conjunction with the accompanying drawings, is intended only to illustrate various configurations and is not intended to limit the scope of the present disclosure. Rather, the detailed description includes specific details to provide 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 case. In some instances, well-known structures and components are shown in block diagram form for clarity.

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

[0043] In some embodiments, the UE may be configured to perform 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 may enable faster DC / CA setup. The UE may be configured to log available early measurement results with one or more MDT results. For illustration purposes, the UE may log available early measurement results along with location information for MDT. Early measurement logging and logged MDT may have the same or different logging intervals (if both early measurement and MDT logging are configured). Early measurement results may be logged when available. If no early measurement results are available (e.g., when the UE is outside the valid area or the logging timer expires), the log or log entry may remain blank.

[0044] In some embodiments, to support early measurements by the UE, the network (NW) may configure the UE to store, report, or a combination of measurement results and logged MDT measurement results. For illustration, the NW may indicate to the UE in an information request (e.g., UEinformationRequest) whether to report logged MDT measurement results, 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 as separate log files, the UE may be configured to provide the early measurement results and the MDT measurement results separately or together.

[0045] 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 MCG fast recovery via the SCG. For example, based on the detection of an MCG failure, the UE may not trigger a radio resource control (RRC) connection reestablishment. Instead, the UE triggers an MCG failure recovery procedure, in which a failure information message is sent to the network via the SCG. Based on sending the MCG failure indication, the UE starts a timer, and based on the expiration of the timer, the UE initiates an RRC connection reestablishment procedure.

[0046] The UE may be configured to perform data collection to generate an RLF report in the event of a fast MCG recovery failure via the SCG. For example, a fast MCG recovery failure may occur or be detected based on expiration of a protection timer, RLF in the MCG and SCG, or the UE's inability to apply an RRC reconfiguration message as a response to sending a fast MCG failure information indication. The RLF report may include MCG failure information, MCG recovery failure related information, or a combination thereof. The MCG failure information may include available measurement results of the MCG, the cause of the MCG link failure, 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 may include available measurement results of the SCG, available measurement results of the MCG, measurement results of available SN configurations, causes of MCG recovery failure (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.

[0047] In some embodiments, the UE may be configured to measure an uplink (UL) average Packet Data Convergence Protocol (PDCP) packet queuing delay measurement (D1) for dual connectivity (DC) operation. For example, when configured as a non-split bearer, the UE may receive a configuration for the D1 measurement from a secondary node (SN) or a primary node (MN). The UE may report the average UL PDCP packet queuing delay to the node (e.g., SN or MN) from which the UE received the measurement configuration. As another example, when configured as a split bearer supported by one PDCP entity and multiple radio link controls (RLCs), the UE may calculate the UL average PDCP packet queuing delay. For illustration, in some embodiments, the UE may calculate a single D1 value and may not distinguish between PDCP packets transmitted to the MN or SN. In such an implementation, the UE may send a report (e.g., a D1 report) to the node from which it received its configuration, or to both the MN and the SN. In other embodiments, the UE may calculate (e.g., average) the PDCP packet queuing delay separately for packets transmitted to the MN and the SN. In such an implementation, the UE may report both D1 values along with the MN D1 and SND1 indicators to the same node from which the UE received its configuration. Alternatively, the UE may report the two D1 values to the MN and SN separately, e.g., reporting MN D1 to the MN and SN D1 to the SN.

[0048] Thus, the present disclosure describes radio access network (RAN)-centric data collection for UEs that can be configured 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) functionality and / or features (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). Data collection and operational improvements can also lead to reduced capital expenditure (CAPEX) and operating expenditure (OPEX) for operators, for example, through more accurate base station deployment and operation and less human resource intervention.

[0049] The present disclosure generally relates to providing or participating in communications between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various implementations, these techniques and apparatuses may 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" are often used interchangeably.

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

[0051] TDMA networks can, for example, implement radio technologies such as GSM. 3GPP defines standards for the GSM EDGE (Enhanced Data Rates for GSM Evolution) radio access network (RAN), 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 interfaces, etc.). The radio access network represents the component of the GSM network through which phone calls and packet data are routed between the public switched telephone network (PSTN) and the internet and user handsets (also known as user terminals or user equipment (UE)). A mobile phone operator's network may include one or more GERANs, which, in the case of a UMTS / GSM network, may be coupled to a universal terrestrial radio access network (UTRAN). The operator's network may also include one or more LTE networks and / or one or more other networks, or a combination thereof. Various network types may use different radio access technologies (RATs) and radio access networks (RANs).

[0052] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE802.20, Flash-OFDM, and the like. 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 uses 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 either known or are about to be developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunications consortium groups whose goal is to define globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP specifies specifications for the next generation of mobile networks, mobile systems, and mobile devices. This disclosure focuses on the evolution of wireless technologies from LTE, 4G, 5G, NR, and shared access to wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces.

[0053] 5G networks consider a variety of deployments, various spectrums, and a variety of services and devices that can be implemented using a unified air interface based on OFDM. 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 extend to provide the following coverage: (1) Coverage with ultra-high density (e.g., ~1M nodes / km) 2 (1) include ultra-low complexity (e.g., ~10s of bits / second), ultra-low energy (e.g., about 10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) include mission-critical control with 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 provide users with a wide range of mobility, or lack thereof; (3) have enhanced mobile broadband, including extremely high capacity (e.g., ~10Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, user experience rates above 100Mbps), and depth perception with improved discovery and optimization.

[0054] 5G NR devices, networks, and systems can be implemented to use optimized OFDM-based waveforms. These features may include scalable numerologies and transmission time intervals (TTIs); a common, flexible framework for efficient multiplexing of services and features with dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) design schemes; and improved wireless technologies such as massive multiple-input, multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of numerologies in 5G NR, as well as the scalability of subcarrier spacing, can efficiently address diverse services operating across different spectrums and 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 over bandwidths of 1, 5, 10, 20 MHz, and so on. For other various outdoor and small cell coverage deployments with TDD greater than 3 GHz, the subcarrier spacing can be 30 kHz over 80 / 100 MHz bandwidth. For various other indoor broadband implementations using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing can be 60 kHz over a 160 MHz bandwidth. Finally, for various deployments using the mmWave component for transmission with TDD at 28 GHz, the subcarrier spacing can be 120 kHz over a 500 MHz bandwidth.

[0055] 5G NR’s scalable parameter set facilitates 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. Efficient multiplexing of long and short TTIs allows transmissions to start on symbol boundaries. 5G NR also considers a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink, in which case it can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic needs.

[0056] For clarity, certain aspects of these apparatus and techniques are described below with reference to exemplary LTE implementations or in an LTE-centric manner, and LTE terminology may be used as an illustrative example in portions of the following description; however, the description is not intended to be limited to LTE applications. Rather, 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.

[0057] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate with any combination of licensed spectrum or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to one of ordinary skill in the art that the systems, apparatus, and methods described herein can be applied to other communication systems and applications beyond the specific examples provided.

[0058] Although various aspects and embodiments are described in this application by way of illustration of some examples, it will be understood by those skilled in the art 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, and packaging arrangements. For example, embodiments and / or uses can be implemented by integrated chip embodiments and / or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, AI-enabled devices, etc.) or combinations thereof. Although some examples may or may not be specifically targeted at use cases or applications, a variety of applicability of the described innovations 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 aggregated, distributed, or OEM devices or systems that include one or more of the described aspects. In some actual settings, the devices that include the described aspects and features may also necessarily include other components and features for implementing and practicing the claimed and described aspects. The innovations described herein may be practiced in a wide variety of implementations of 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, and the like.

[0059] Figure 1 1 shows a wireless network 100 for communicating according to some aspects. The wireless network 100 may, for example, comprise a 5G wireless network. As will be appreciated by those of ordinary skill in the art, Figure 1 The components appearing in may have related counterparts in other network arrangements, including, for example, cellular network arrangements and non-cellular network arrangements (eg, device-to-device or peer-to-peer or ad hoc (self-organizing) network arrangements, etc.).

[0060] Figure 1The wireless network 100 shown in FIG includes multiple base stations 105 and other network entities. A base station can be a station that communicates with a UE and can also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the specific geographic coverage area of a base station and / or the base station subsystem serving that coverage area, depending on the context in which the term is used. In implementations 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 provide wireless communications using one or more of the same frequencies as neighboring cells (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof). In some examples, a single base station 105 or UE 115 can be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 can be operated by a single network operating entity.

[0061] A base station may provide communication coverage for a macro cell or a small cell (e.g., a pico cell or a femto cell) and / or other types of cells. Typically, a macro cell covers a relatively large geographic area (e.g., a radius of several kilometers), which allows unrestricted access to UEs that have a service subscription with a network provider. Typically, a small cell such as a pico cell covers a relatively small geographic area, which allows unrestricted access to UEs that have a service subscription with a network provider. In addition, a small cell such as a femto cell typically covers a relatively small geographic area (e.g., a home), and in addition to unrestricted access, it also provides restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105-a-105c are macro base stations that implement one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105-a-105c take full advantage of their higher-dimensional MIMO capabilities to increase coverage and capacity by utilizing 3D beamforming in both elevation and azimuth beamforming. Base station 105f is a small cell base station, which can be a home node or portable access point. A base station can support one or more (e.g., two, three, four, etc.) cells.

[0062] Wireless network 100 can support synchronous or asynchronous operation. For synchronous operation, base stations can have similar frame timing, and transmissions from different base stations are approximately aligned in time. For asynchronous operation, base stations can have different frame timing, 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 operation.

[0063] UEs 115 are dispersed throughout wireless network 100, and each UE may be either stationary or mobile. It should be understood that while mobile devices are generally referred to as user equipment (UE) in standards and specifications promulgated by the Third Generation Partnership Project (3GPP), persons of ordinary skill in the art may also refer to such devices as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handheld devices, terminals, user agents, mobile clients, clients, or some other appropriate terminology. Within this document, a "mobile" device or UE need not necessarily have mobility capabilities and may be stationary. Some non-limiting examples of mobile devices, such as those that may include one or more of UEs 115, include mobile stations, cellular (cell) phones, smartphones, Session Initiation Protocol (SIP) phones, wireless local loop (WLL) stations, laptop computers, personal computers (PCs), notebook computers, netbooks, smart books, tablet devices, and personal digital assistants (PDAs). The mobile device may also be an "Internet of Things" (IoT) or "Internet of Everything" (IoE) device, such as a car or other vehicle, satellite radio, global positioning system (GPS) device, logistics controller, drone, multicopter, helicopter, smart energy or security equipment, 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, the UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, the UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The example UEs 115-a-115d shown in FIG are examples of mobile smartphone-type devices accessing the wireless network 100. A UE may also be a machine specifically configured to implement connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), and the like. Figure 1 The UEs 115e - 115k shown in FIG. 1 are examples of various machines configured to enable access to the wireless network 100 .

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

[0065] When operating in wireless network 100, base stations 105-a-105c use 3D beamforming and coordinated spatial techniques (e.g., coordinated multipoint (CoMP) or multi-connectivity) to serve UEs 115-a and 115-b. Macro base station 105d performs backhaul communications with base stations 105-a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information (e.g., weather emergencies or warnings such as amber alerts or gray alerts).

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

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

[0068] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller / processor 240. The control information may be for the physical broadcast channel (PBCH), the physical control format indicator channel (PCFICH), the physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), the physical downlink control channel (PDCCH), the enhanced physical downlink control channel (EPDCCH), the MTC physical downlink control channel (MPDCCH), etc. The data may be for the PDSCH, etc. The transmit processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. In addition, the transmit processor 220 may also generate reference symbols, such as for the primary synchronization signal (PSS), the secondary synchronization signal (SSS), and the cell-specific reference signal. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, and / or reference symbols (if any) and provide output symbol streams to the modulators (MODs) 232a through 232t. Each modulator 232 may process a 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, amplify, filter, and frequency upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

[0069] At UE 115, antennas 252a through 252r can receive downlink signals from base station 105 and provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain received symbols from demodulators 254a through 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. Receive processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 115 to data sink 260, and provide decoded control information to controller / processor 280.

[0070] 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 and control information (e.g., for the Physical Uplink Control Channel (PUCCH)) from the controller / processor 280 and process the data and control information. The transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266 (if applicable), further processed by the modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted 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 by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240 .

[0071] The controllers / processors 240 and 280 may direct the operation 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 performing or directing the execution of various processes for implementing the techniques described herein. Figure 6-9 , and / or other processing for implementing the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

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

[0073] For example, a network operating entity may be allocated specific time resources reserved for exclusive communications, allowing the network operating entity to use the entire shared spectrum. Other time resources may also be allocated to the network operating entity, giving it priority over other network operating entities for communication using the shared spectrum. If a prioritized network operating entity does not utilize these time resources, which were prioritized for use by that network operating entity, other network operating entities may use them on an opportunistic basis. Additional time resources may be allocated to any network operator for opportunistic use.

[0074] Access to shared spectrum and arbitration of time resources between different network operating entities can be centrally controlled by a single entity, determined autonomously according to a pre-defined arbitration scheme, or dynamically determined based on interactions between wireless nodes of the network operator.

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

[0076] 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 data collection centric to the radio access network (RAN). For illustration, the UE 115 may be configured to collect, store, report, or a combination thereof, DC / CA early measurement results associated with logged minimization of drive tests (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 master 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) delay measurements.

[0077] Figure 3 is a block diagram of an exemplary wireless communication system 300 configured to provide data collection to a user equipment (UE) that may be configured 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. By way of illustrative and 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.

[0078] The UE 115 may include various components (e.g., structural, 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.

[0079] 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. Mode 318 may include one or more modes, such as an active mode or an inactive mode, of UE 115. As illustrative, non-limiting examples, an inactive mode may include an idle mode, an inactive mode, a low power mode, or another mode.

[0080] 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. Measurement results 320 may include or indicate early measurement data 321, MDT data 322, or a combination thereof. Early measurement data 321 may include one or more measurement values for a resident frequency, a non-resident frequency, or a combination thereof. MDT data 322 may include one or more MDT results. One or more log intervals 323 may indicate a first interval used to perform measurements to generate early measurement data 321, a second interval used to determine 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.

[0081] 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 can send data, and the receiver 316 can receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, the UE 115 can 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 above, or any other communication network now known or later developed that allows two or more electronic devices to communicate. In some embodiments, the transmitter 315 and the receiver 316 can be replaced with a transceiver. Additionally or alternatively, the transmitter 315, the receiver 316, or both can include or correspond to reference Figure 2 One or more components of the described UE 115. The timer 317 may be configured to enable the UE 115 to track or determine one or more time periods, or the expiration of one or more time periods.

[0082] The network entity 320 may include various components (e.g., structural, 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.

[0083] 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, and 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 foregoing, or any other communication network now known or later developed that allows 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 reference Figure 2 One or more components of base station 105 are described.

[0084] In certain implementations, the wireless communication system 300 includes a 5G network. For example, the UE 115 may include a 5G UE (e.g., a UE configured to operate in accordance with a 5G network). The network entity 350 may include a 5G base station (e.g., a base station configured to operate in accordance with a 5G network).

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

[0086] 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 thereof, early measurement results (e.g., 321) and logged MDT measurement results (e.g., 322). For illustration, the NW may indicate to the UE in measurement configuration 370 whether to report logged MDT measurement results, early measurement results, or a combination thereof. For example, measurement configuration 370 may include an information request, such as a 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 results (e.g., 322) may be stored in different logs / files (e.g., two or more separate log files). When stored in separate log files, UE 115 may be configured to provide the early measurement results and the MDT measurement results separately or together.

[0087] During operation of the wireless communication system 300, the UE 115 receives a measurement configuration 370 from the network entity 350. The measurement configuration 370 may include a storage configuration, a reporting configuration, or a combination thereof. The storage configuration may indicate whether to store minimization of drive tests (MDT) results in a first log file, an interval for measuring MDT measurement values, storing early measurement results in a second log file, an interval for measuring early measurement results, whether to store MDT results and early measurement results in the same log file, or a combination thereof. The reporting configuration may indicate whether to transmit the MDT results and early measurement results in the same report message or in separate report messages.

[0088] UE 115 may identify a storage configuration, a 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, UE 115 may generate or populate measurement results 320 while UE 115 is in an inactive state. For illustration, UE 115 may determine minimization of drive tests (MDT) results, early measurement results, or both. Early measurement data 321 may be determined based on a first interval (e.g., 323), and MDT data 322 may be determined based on 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.

[0089] The UE 115 may transmit 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 implementations, the UE 115 may transmit a first report including the MDT data 322 and a second report including the early measurement data 321. The first report may be transmitted before, after, or simultaneously with the second report.

[0090] Thus, the present disclosure describes radio access network (RAN)-centric data collection for UEs that can be configured for DC / CA operation. For example, the operations described herein provide for the collection, storage, reporting, or a combination thereof of DC / CA early measurements associated with logged Minimization of Drive Tests (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) functionality and / or features.

[0091] Figure 4 is a block diagram of an exemplary wireless communication system 400 configured to provide data collection to a user equipment (UE) that can be configured for DC / CA. In some examples, the wireless communication system 400 can implement aspects of the wireless network 100 or the wireless communication system 300. The wireless communication system 400 includes a UE 115 and a first network entity 450 and a second network entity 452. As illustrative and non-limiting examples, the network entities 450, 452 may include or correspond to the 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 primary 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, more than two network entities, or both.

[0092] The UE 115 may include various components (e.g., structural, 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.

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

[0094] The failure information 424 may be generated by the 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 SCG link failure detection, a signaling radio bearer type (e.g., split SRB or SRB type 3 (SRB3)), or a combination thereof.

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

[0096] 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 can send data, and the receiver 316 can receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, the UE 115 can 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 above, or any other communication network now known or later developed that allows two or more electronic devices to communicate. In some embodiments, the transmitter 315 and the receiver 316 can be replaced with a transceiver. Additionally or alternatively, the transmitter 315, the receiver 316, or both can include or correspond to reference Figure 2 One or more components of the UE 115 are described.

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

[0098] The first network entity 450 may include various components (e.g., structural, 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.

[0099] 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, and 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 allows 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 reference Figure 2 One or more components of a base station 105 are described.

[0100] The second network entity 452 may further include one or more components, such as a processor, memory, transmitter, receiver, etc., which are not shown for convenience. The second network entity 452 may 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.

[0101] In a specific implementation, the wireless communication system 400 includes a 5G network. For example, the UE 115 may include a 5G UE (e.g., a UE configured to operate in accordance with a 5G network). The network entities 450, 452 may include a 5G base station (e.g., a base station configured to operate in accordance with a 5G network).

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

[0103] In some embodiments, the UE 155 may be configured to perform data collection to generate an RLF report (e.g., 472) in the event 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 expiration of a protection timer, RLF in both the MCG and the SCG, or an inability of the UE 115 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, the cause of the MCG link failure, 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 reasons (e.g., protection timer expiration indication, SCG link failure detection, etc.), recovery type (e.g., recovery by splitting signaling radio bearer (SRB) or signaling radio bearer type 3 (SRB3)), or a combination thereof.

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

[0105] Upon detection of a fast MCG recovery failure, the UE 115 may generate and send a failure report 472. The UE 115 may perform one or more operations to restore the MCG connection, restore the SCG connection, or both.

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

[0107] Figure 5 is a block diagram of an exemplary wireless communication system 500 configured to provide data collection to a user equipment (UE) that may be configured for dual connectivity / 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 and 400. The wireless communication system 500 includes a UE 115 and a first network entity 550 and a second network entity 552. As illustrative and non-limiting examples, the network entities 550 and 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, more than two network entities, or both.

[0108] The UE 115 may include various components (e.g., structural, 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 the controller / processor 280, and the memory 314 includes or corresponds to the memory 282.

[0109] The memory 314 may include bearer information 428 and one or more D1 measurements 520. The one or more D1 measurements 520 may include delay information 521 (e.g., MN information 522, SN information 523, or a combination thereof). The delay 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 for packets transmitted to the first network entity 550. The SN information 523 includes the average PDCP packet queuing delay for packets transmitted to the second network entity 552. In some embodiments, the delay information 521 may include the average PDCP packet queuing delay for packets transmitted to the first network entity 550 and the second network entity 552.

[0110] 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 can send data, and the receiver 316 can receive data via a network (e.g., a wired network, a wireless network, or a combination thereof). For example, the UE 115 can 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 above, or any other communication network now known or later developed that allows two or more electronic devices to communicate. In some embodiments, the transmitter 315 and the receiver 316 can be replaced with a transceiver. Additionally or alternatively, the transmitter 315, the receiver 316, or both can include or correspond to reference Figure 2 One or more components of the UE 115 are described.

[0111] The first network entity 550 may include various components (e.g., structural, 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.

[0112] 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, and 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 550 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 allows 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 reference Figure 2 One or more components of base station 105 are described.

[0113] 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, etc. 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.

[0114] In a specific 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 in accordance with a 5G network). The network entities 550, 552 may include a 5G base station (e.g., a base station configured to operate in accordance with a 5G network).

[0115] 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 as a non-split bearer, the UE 115 may receive a configuration for the D1 measurement (e.g., 570) from a secondary node (SN) (e.g., 552) or a primary 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 received the measurement configuration. As another example, when configured as a split bearer with one PDCP entity and multiple radio link control (RLC) legs, 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., a D1 report) to the node (e.g., 570) from which the UE 115 received the UE configuration, or to both the MN (e.g., 550) and the SN (e.g., 552). In other implementations, the UE 115 may calculate (e.g., average) the PDCP packet queuing delay for packets transmitted to the MN and the SN separately. In such an implementation, the UE 115 may report both D1 values along with the MN D1 and SN D1 indicators to the same node from which the UE 115 received its configuration. Alternatively, the UE 115 may report both D1 values to the MN and the SN separately, e.g., reporting MN D1 to the MN and SN D1 to the SN.

[0116] During operation of the wireless communication system 400, the UE 115 determines a bearer type for 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.

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

[0118] The UE 115 may send an uplink (UL) delay measurement based on the bearer type. In some implementations, sending the UL delay measurement includes sending one or more measurement reports (eg, one or more measurement reports 572).

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

[0120] 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 measurement for both the MN and the SN. For example, the UL delay measurement can be a single value. In such an implementation, the UL delay measurement is sent to the SN or the MN from which the UE 115 receives the configuration message (e.g., 570). Alternatively, the UL delay measurement can be sent to both the SN and the MN.

[0121] In other implementations, when UE 115 includes split bearers supported by one PDCP entity and multiple RLC entities, UE 115 may calculate a first UL delay measurement for the MN and a second UL delay measurement for the SN. In some implementations, UE 115 may send the first UL delay measurement, an MN indicator corresponding to the first UL delay measurement, the second UL delay measurement, an SN indicator corresponding to the second UL delay measurement, or a combination thereof, to the SN or the MN from which the UE received the configuration message. In other implementations, 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.

[0122] Thus, the present disclosure describes radio access network (RAN)-centric data collection for UEs that can be configured for DC / CA operation. For example, the operations described herein provide Layer 2 (L2) measurements configured to support uplink (UL) delay measurements for UEs 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) functionality and / or features.

[0123] Figure 6-8 is a flow chart illustrating an example method for communication performed by a UE. For example, example blocks of these methods may enable a UE to perform data collection associated with dual connectivity (DC) / carrier aggregation (CA) operations according to some aspects of the present disclosure. Figure 10 These example blocks are described with reference to the UE 115 shown in FIG. Figure 10 is a block diagram conceptually illustrating an example design of a UE configured to perform data collection associated with dual connectivity (DC) / carrier aggregation (CA) operation according to one aspect of the present disclosure. Figure 2 or Figure 3-5For example, the UE 115 includes a controller / processor 280 for executing logic or computer instructions stored in a memory 282 and controlling the components of the UE 115 that provide the features and functions of the UE 115. Under the control of the controller / processor 280, the UE 115 transmits and receives signals via the radios 1001a-r and the antennas 252a-r. Figure 2 As shown for UE 115 , radios 1001 a - r may include various components and hardware, including modulators / demodulators 254 a - r , a MIMO detector 256 , a receive processor 258 , a transmit processor 264 , and a TX MIMO processor 266 .

[0124] As shown, the memory 282 may include measurement logic 1002, a location 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 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 log 372, failure information 424, MCG failure information 425, MCG recovery failure information 426, failure report 472, D1 measurement 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 the measurement log 372 or the measurement report 572. The location detector 1003 (e.g., a global positioning system (GPS)) can be configured to determine, receive, or identify location information 319. The fault detector 1004 can be configured to detect a communication link failure. 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, and failure report 472. The failure report generator 1005 can be configured to generate a failure report, such as failure report 472. The bearer logic 1006 can be configured to perform one or more operations based on the bearer information (e.g., bearer information 428). The delay report generator 1007 can be configured to generate one or more delay reports, such as measurement report 572. The timer 1008 can include or correspond to time 317. In some aspects, the measurement logic 1002, the location detector 1003 (e.g., 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 data from one or more network entities (e.g., base station 105, network entity 350, 450, 452, 550, 552, core network, core network device, or other such entity). Figure 11 The network entity shown receives signals and / or sends signals to it.

[0125] refer to Figure 6, which illustrates an example flow chart of a method 600 of UE operation for communication. In some embodiments, method 600 may be performed by UE 115. In other implementations, method 600 may be performed by an apparatus configured for wireless communication. For example, the apparatus 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.

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

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

[0128] At 606, the UE sends a report including the MDT results, early measurement results, or a combination thereof. The report may include or correspond to the measurement log 372. The report may be generated using the 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 illustrative, non-limiting examples, the network element may include or correspond to the base station 105, the network entity 350, 450, 452, 550, 552, 1105, a network device, or a network core. In such an implementation, the UE may send the report in response to the information request. The UE 115 may send the report using the radios 1001a-r and antennas 252a-r.

[0129] In some implementations, method 600 includes the UE determining location information associated with 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 also includes the UE storing the early measurement results along with the location information.

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

[0131] 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 measurement results 320. In some embodiments, when early measurement results are unavailable, the UE may generate a blank early measurement result entry. UE 115 may use measurement logic 1002 to generate the first log, the second log, or a combination thereof.

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

[0133] 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 for the collection, storage, reporting, or a combination thereof of DC / CA early measurements associated with logged Minimization of Drive Tests (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) functionality and / or features.

[0134] refer to Figure 7, which shows an example flow chart of a method 700 of UE operation for communication. In some embodiments, method 700 may be performed by UE 115. In other implementations, method 700 may be performed by an apparatus configured for wireless communication. For example, the apparatus 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.

[0135] As shown at block 702, the UE generates a radio link failure (RLF) report based on detection of a master cell group (MCG) fast recovery failure. The RLF report may include or correspond to 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. The UE 115 may generate the RLF report using measurement logic 1002, failure detector 1004, failure report generator 1005, or a combination thereof. In some embodiments, the UE is in a dual connectivity / carrier aggregation (DC / CA) configuration.

[0136] In some embodiments, 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. 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 SRB type 3 (SRB3), as an illustrative, non-limiting example.

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

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

[0139] Thus, method 700 enables radio access network (RAN)-centric data collection for UEs that can be configured for DC / CA operation. For example, the operations described herein provide radio link failure (RLF) reporting that is configured to support fast master cell group (MCG) recovery failure via 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) functions and / or features.

[0140] refer to Figure 8 , which shows an example flow chart of a method 800 of UE operation for communication. In some embodiments, method 800 may be performed by UE 115. In other implementations, method 800 may be performed by an apparatus configured for wireless communication. For example, the apparatus may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations of method 800. In other implementations, method 800 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 800.

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

[0142] In some implementations, method 800 may include performing one or more layer 2 measurements and generating, by the UE, an UL delay measurement based on the one or more layer 2 measurements. The UE 115 may perform these measurements using measurement logic 1002. The UE 115 may generate the UL delay measurement.

[0143] At 804, method 800 includes transmitting, from the UE, an uplink (UL) delay measurement based on the bearer type. For example, the UL delay measurement may include or correspond to a D1 measurement 520, delay information 521, MN information 522, SN information, or a combination thereof. The UL delay measurement may include a UL average Packet Data Convergence Protocol (PDCP) packet queuing delay measurement (D1). The UE 115 may transmit the UL delay measurement using radios 1001a-r and antennas 252a-r. In some embodiments, transmitting the UL delay measurement includes transmitting one or more measurement reports, such as one or more measurement reports 572.

[0144] In some embodiments, the 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 primary node (MN). The configuration message may include or correspond to the measurement configuration message 570. The UL delay measurement is sent to the SN or MN from which the UE receives the configuration message.

[0145] In some embodiments, method 800 may include: when the UE includes split bearers supported by one PDCP entity and multiple RLC entities, calculating, by the UE, UL delay measurements for both the MN and the SN. For example, the UL delay measurement may be a single value. In some embodiments, method 800 may also include: receiving, by the UE, a configuration message from the SN or the MN, and sending the UL delay measurement to the SN or the MN from which the UE received the configuration message. Alternatively, the UL delay measurement may be sent to both the SN and the MN.

[0146] In other implementations, method 800 may include, when the UE includes split bearers supported by one PDCP entity and multiple RLC entities, calculating a first UL delay measurement for the MN and calculating a second UL delay measurement for the SN. In some embodiments, method 800 further includes, receiving, by the UE, a configuration message from the SN or the MN. In some such implementations, 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, an SN indicator corresponding to the second UL delay measurement, or a combination thereof, to the SN or the MN from which the UE received the configuration message. In other implementations, 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.

[0147] Thus, method 800 enables radio access network (RAN)-centric data collection for UEs that can be configured for DC / CA operation. 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) 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) functionality and / or features.

[0148] It should be noted that reference Figure 6-8 One or more blocks (or operations) described in FIG. 1 may be combined with one or more blocks (or operations) in another figure. For example, Figure 6-8 One or more boxes can be combined with Figure 2 or Figure 3-5 Alternatively or additionally, the above reference Figure 1-8 and Figure 10 One or more of the operations described may be combined with reference to Figure 11 Combines one or more operations described.

[0149] Figure 9 900 is a flow chart illustrating an example method 900 for communication performed by a network entity. For example, according to some aspects of the present disclosure, example blocks of the method 900 may enable the network entity to transmit a configuration message. Figure 11 The network entity 1105 is shown to illustrate these example blocks. Figure 11 is a block diagram conceptually illustrating an example design of a network entity 1105 (e.g., base station 105, network entity 350, 450, 452, 550, 552, 1105, network, or core network, as illustrative, non-limiting examples).

[0150] The network entity 1105 includes Figure 2-5 105, 350, 450, 452, 550, 552. 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 features and functions of the network entity 1105. Under the control of the controller / processor 240, the network entity 1105 transmits and receives signals via radios 1101a-t and antennas 234a-t. Figure 2105 , the radio units 1101a-t include various components and hardware including modulators / demodulators 232a-t, transmit processors 220, TX MIMO processors 230, MIMO detectors 236, and receive processors 238. As shown, the memory 242 may include a configuration generator 1102, communication logic 1103, and a timer 1104. The 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. The communication logic 1103 may enable the network entity 1105 to perform one or more operations for wireless communication. The timer 1104 may be configured to enable the network entity 1105 to determine the expiration of one or more time periods. In some aspects, the configuration generator 1102, the communication logic 1103, and the timer 1104, or a combination thereof, may include or correspond to the processor 362. The network entity 1105 may receive a UE (e.g., a UE) from which the UE may receive a MIMO signal. Figure 10 UE 115) shown in FIG receives signals and / or sends signals to the UE.

[0151] refer to Figure 9 , which shows an example flow chart of a 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 an apparatus configured for wireless communication. For example, the apparatus 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.

[0152] 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 generate the measurement configuration message using configuration generator 1102. Network entity 1105 may use radios 1101a-t, antennas 234a-t, and communication logic 1103 to send the measurement configuration message.

[0153] 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 minimization of drive tests (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.

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

[0155] In some implementations, the storage configuration directs that Minimization of Drive Test (MDT) results and early measurement results be stored in a single log file. In other implementations, the storage configuration directs that MDT results be stored in a first log file and early measurement results be stored in a second log file. Additionally or alternatively, the reporting configuration may direct that MDT results and early measurement results be transmitted in the same report message or in separate report messages.

[0156] Thus, method 900 enables radio access network (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 measurements associated with logged Minimization of Drive Tests (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) functionality and / or features.

[0157] It should be noted that reference Figure 9 One or more blocks (or operations) described in FIG. 1 may be combined with one or more blocks (or operations) in another figure. For example, Figure 9 One or more boxes can be combined with Figure 2 or Figure 3-5 Alternatively or additionally, the above reference Figure 1-5 , 9 and Figure 11 One or more of the operations described may be combined with reference to Figure 10 Combines one or more operations described.

[0158] In some aspects, data collection for dual connectivity (DC) / carrier aggregation (CA) may include a wireless device receiving: a minimization of drive tests (MDT) result determined by a user equipment (UE); determining an early measurement result; and sending a report including the MDT result, the early measurement result, 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, a non-transitory computer-readable medium has program code recorded thereon, the program code being executable by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

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

[0160] In a second aspect, alone or in combination with the first aspect, the early measurement result comprises a resident frequency measurement, a non-resident frequency measurement, or a combination thereof; and the early measurement result is determined by the UE in an inactive state.

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

[0162] In a fourth aspect, 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.

[0163] In a fifth aspect, 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.

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

[0165] In a seventh aspect, 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.

[0166] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the method may include generating a blank early measurement result entry when the early measurement result is not available.

[0167] In a ninth aspect, 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 storage configuration, reporting configuration, or a combination.

[0168] In a tenth aspect, 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.

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

[0170] In the twelfth aspect, 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.

[0171] In a thirteenth aspect, 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.

[0172] In some aspects, data collection for dual connectivity (DC) / carrier aggregation (CA) may include: a wireless device sending a measurement configuration message by a network entity, the measurement configuration message including: a storage configuration for minimization of drive tests (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; and receiving the MDT results, the early measurement results, or a combination thereof by 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, a non-transitory computer-readable medium has program code recorded thereon, the program code being executable by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

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

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

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

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

[0177] In an eighteenth aspect, 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.

[0178] In some aspects, data collection for dual connectivity (DC) / carrier aggregation (CA) may include a wireless device performing the following operations: generating, by a user equipment (UE), a radio link failure (RLF) report based on detection of a master cell group (MCG) fast recovery failure, the RLF report including MCG failure information, MCG recovery failure information, or a combination thereof; and sending, by the UE, the RLF report 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, a non-transitory computer-readable medium has program code recorded thereon, the program code being executable by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

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

[0180] In the twentieth aspect, 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.

[0181] In aspect 21, alone or in combination with one or more of aspects 19 to 20, 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.

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

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

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

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

[0186] In aspect 26, alone or in combination with one or more of aspects 19 to 25, the fast MCG recovery failure is based on expiration of a protection time, RLF of both the MCG and the SCG, or failure to apply a radio resource control (RRC) reconfiguration message.

[0187] 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), a bearer type of the UE; and sending, from the UE, an uplink (UL) delay measurement 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, a non-transitory computer-readable medium has program code recorded thereon, the program code being executable by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

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

[0189] In a twenty-eighth aspect, alone or in combination with the twenty-seventh aspect, the UL delay measurement comprises a UL average Packet Data Convergence Protocol (PDCP) packet queuing delay measurement (D1).

[0190] In aspect 29, alone or in combination with one or more of aspects 27 to 28, 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.

[0191] In the thirtieth aspect, alone or in combination with one or more of aspects twenty-seven to twenty-ninth, 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 the UL delay measurement is sent to the SN or MN from which the UE receives the configuration message.

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

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

[0194] In aspect 33, alone or in combination with one or more of aspects 31 to 32, it may include: receiving a configuration message from the SN or the MN; and wherein the UL delay measurement is sent to the SN or MN from which the UE receives the configuration message.

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

[0196] In aspect 35, alone or in combination with one or more of aspects 31 to 32, it may include: when the UE includes a split bearer having 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.

[0197] In aspect 36, alone or in combination with aspect 35, 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, the MN indicator corresponding to the first UL delay measurement, the second UL delay measurement, and the SN indicator corresponding to the second UL delay measurement to the SN or MN from which the UE receives the configuration message.

[0198] In aspect 37, alone or in combination with aspect 35, 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.

[0199] It will be understood by those skilled in the art that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0200] This article is in Figure 1-11 The functional blocks and modules described herein include processors, electronic devices, hardware devices, electronic components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof. In addition, the features discussed herein may be implemented by dedicated processor circuits, by executable instructions, and / or a combination thereof.

[0201] Those skilled in the art will also understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can all be implemented as electronic hardware, computer software, or a combination thereof. In order to clearly represent this interchangeability between hardware and software, the various exemplary components, blocks, modules, circuits, and steps above have been generally described around their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. A skilled person can implement the described functions in a flexible manner for each specific application, but such implementation decisions should not be interpreted as departing from the scope of protection of the present disclosure. A skilled person will also readily recognize that the order or combination of components, methods, or interactions described herein is merely exemplary, and that components, methods, or interactions of various aspects of the present disclosure can be combined or performed in a manner different from that shown and described herein.

[0202] A general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or any combination thereof for performing the functions described herein may be used to implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure herein. A general purpose processor may be a microprocessor, or the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0203] The steps of the method or algorithm described in conjunction with the disclosure herein may be directly embodied as hardware, a software module executed by a processor, or a combination of the two. The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, 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 may 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 may also be an integral part of the processor. The processor and storage medium may be located in an ASIC. The ASIC may be located in a user terminal. Of course, the processor and storage medium may also be present in the user terminal as discrete components.

[0204] In one or more exemplary designs, the functions described herein can be implemented by computer-executable instructions using hardware, software, firmware, or any combination thereof. 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. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of a computer program from one place to another. A computer-readable storage medium can be any available medium that a general-purpose or special-purpose computer can access. For example, but not limitation, such a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, 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 can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. In addition, a connection can be appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL), then the coaxial cable, fiber optic cable, twisted pair, or DSL is included in the definition of the medium. As used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), hard disks, solid-state drives, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of protection of computer-readable media.

[0205] As used herein, including the claims, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items is used, or any combination of two or more of the listed items is used. For example, if a compound is described as containing components A, B, and / or C, the compound can contain 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. Furthermore, as used herein, including the claims, "or" used in a list item ending with "at least one of" indicates a disjunctive list, so that, for example, the list "at least one of A, B, or C" means: any one of A or B or C or AB or AC or BC or ABC (i.e., A and B and C), or any combination thereof.

[0206] The above description focuses on the present disclosure to enable anyone skilled in the art to implement or use the present disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is intended to be consistent with the broadest scope of the principles and novel features disclosed herein.

Claims

1. A method for wireless communication, the method comprising: generating, by a user equipment (UE), a radio link failure (RLF) report based on detection of a master cell group (MCG) fast recovery failure, the RLF report including MCG failure information, MCG recovery failure information, or a combination thereof; as well as The RLF report is sent by the UE to a secondary cell group (SCG).

2. The method according to claim 1, wherein The UE is in dual connectivity / carrier aggregation (DC / CA) configuration.

3. The method according to any one of claims 1 or 2, wherein: The MCG failure information includes available measurement results of the MCG, MCG link failure reasons, available measurement results of the SCG, available measurement results of non-serving cells, or a combination thereof.

4. The method according to any one of claims 1 to 3, wherein: 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.

5. The method according to any one of claims 1 to 4, wherein: The MCG recovery failure information includes the reason for the MCG recovery failure.

6. The method according to claim 5, wherein: The MCG recovery failure reason includes a protection timer expiration indication or an SCG link failure detection.

7. The method according to any one of claims 1 to 6, wherein: The MCG recovery failure information includes a signaling radio bearer type.

8. The method according to claim 7, wherein: The signaling radio bearer (SRB) type includes a split SRB or an SRB type 3 (SRB3).

9. The method according to any one of claims 1 to 8, wherein: The fast MCG recovery failure is based on expiration of a guard time, RLF of both the MCG and the SCG, or failure to apply a radio resource control (RRC) reconfiguration message.

10. An apparatus configured for wireless communication, comprising: means for generating, by a user equipment (UE), a radio link failure (RLF) report based on detection of a master cell group (MCG) fast recovery failure, the RLF report including MCG failure information, MCG recovery failure information, or a combination thereof; as well as means for sending, by the UE, the RLF report to a secondary cell group (SCG).

11. The device according to claim 10, wherein The UE is in dual connectivity / carrier aggregation (DC / CA) configuration.

12. The device according to any one of claims 10 to 11, wherein The MCG failure information includes available measurement results of the MCG, MCG link failure reasons, available measurement results of the SCG, available measurement results of non-serving cells, or a combination thereof.

13. The device according to any one of claims 10 to 12, wherein 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.

14. The device according to any one of claims 10 to 13, wherein The MCG recovery failure information includes the reason for the MCG recovery failure.

15. A computer program comprising program instructions, which, when executed by a computer, execute all the steps of the method according to any one of claims 1 to 9.

Images