Multi-carrier aggregation using predicted configurations corresponding to neighboring cells

Abstract

Systems and techniques are provided for wireless communications. For example, a network device can receive information indicative of a first carrier aggregation (CA) configuration including a primary component carrier (PCC) and a set of secondary component carriers (SCCs). A predicted updated CA configuration can be generated to include a predicted PCC or a predicted SCC, based on measurements of a particular neighboring cell. A plurality of hardware register values can be determined for implementing an RF chain corresponding to the predicted updated CA configuration, based on the measurements of the particular neighboring cell. The network device can receive information indicative of an updated C A configuration different from the first C A configuration and including at least one of the predicted PCC or the predicted SCC. The network device can perform C A tuning using the plurality of hardware register values of the RF hardware register configuration.

Description

MULTI-CARRIER AGGREGATION USING PREDICTED CONFIGURATIONSCORRESPONDING TO NEIGHBORING CELLSFIELD

[0001] Aspects of the present disclosure generally relate to wireless communication. In some implementations, examples are described for configuring carrier aggregation (CA) for a network device based on predicted updated CA configurations determined by the network device.INTRODUCTION

[0002] Wireless communications systems are deployed to provide various telecommunication services, including telephony, video, data, messaging, broadcasts, among others. Wireless communications systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second- generation (2G) digital wireless phone service (including interim 2.5G networks), a third- generation (3G) high speed data, Internet-capable wireless service, a fourth-generation (4G) service (e.g., Long-Term Evolution (LTE), WiMax), and a fifth-generation (5G) service (e.g., New Radio (NR)). There are presently many different types of wireless communications systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communication (GSM), etc.SUMMARY

[0003] The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

[0004] Disclosed are systems, methods, apparatuses, and computer-readable media for performing wireless communication. According to at least one illustrative example, a network device for wireless communication is provided. The network device includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to: receive information indicative of a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs); determine a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated C A configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells; determine a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell; receive information indicative of an updated CA configuration for the network device, wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and perform CA tuning using the plurality of hardware register values of the RF hardware register configuration.

[0005] In another example, a method for wireless communication is provided, the method including: receiving information indicative of a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs); determining a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells; determining a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell; receiving information indicative of an updated CA configuration for the network device,wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and performing CA tuning using the plurality of hardware register values of the RF hardware register configuration.

[0006] In another example, a non-transitory computer-readable storage medium comprising instructions stored thereon which, when executed by at least one processor, causes the at least one processor to: receive information indicative of a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs); determine a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells; determine a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell; receive information indicative of an updated CA configuration for the network device, wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and perform CA tuning using the plurality of hardware register values of the RF hardware register configuration.

[0007] In another example, an apparatus is provided for wireless communication. The apparatus includes: means for receiving information indicative of a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs); means for determining a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells; means for determining a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain corresponding to the predicted updated CAconfiguration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell; means for receiving information indicative of an updated CA configuration for the network device, wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and means for performing CA tuning using the plurality of hardware register values of the RF hardware register configuration.

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

[0009] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

[0010] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects may be implemented via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-levelcomponents. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying size, shape, and constitution.

[0011] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire specification of this patent, any or all drawings, and each claim.

[0012] The foregoing, together with other features and aspects, will become more apparent upon referring to the following specification, claims, and accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

[0014] FIG. 1 is a block diagram illustrating an example of a wireless communication network, in accordance with some examples;

[0015] FIG. 2 is a diagram illustrating a design of a base station and a User Equipment (UE) device that enable transmission and processing of signals exchanged between the UE and the base station, in accordance with some examples;

[0016] FIG. 3 is a diagram illustrating an example of a disaggregated base station, in accordance with some examples;

[0017] FIG. 4 is a block diagram illustrating components of a user equipment (UE), in accordance with some examples;

[0018] FIG. 5 is a diagram illustrating an example of physical channels and reference signals in a wireless network, in accordance with some examples;

[0019] FIG. 6 is a diagram illustrating an example timeline for earner aggregation (CA) tuning to implement a CA configuration for a UE or network device, in accordance with some examples;

[0020] FIG. 7 is a diagram illustrating an example of multi-carrier aggregation corresponding to a primary component carrier (PCC) and secondary component carriers (SCCs) associated with a radio frequency (RF) transceiver of a UE or network device, in accordance with some examples;

[0021] FIG. 8 is a diagram illustrating an example timeline for CA tuning using a PCC tuning phase and an SCC tuning phase to implement a CA configuration for a UE or network device within a configured time limit, in accordance with some examples;

[0022] FIG. 9 is a flowchart diagram illustrating an example of a process for wireless communications by a network device, in accordance with some examples; and

[0023] FIG. 10 is a block diagram illustrating an example of a computing system, which may be employed by the disclosed systems and techniques, in accordance with some examples.DETAILED DESCRIPTION

[0024] Certain aspects of this disclosure are provided below for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure. Some of the aspects described herein may be applied independently and some of them may be applied in combination as would be apparent to those of skill in the art. In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of aspects of the application. However, it will be apparent that various aspects may be practiced without these specific details. The figures and description are not intended to be restrictive.

[0025] The ensuing description provides example aspects only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the example aspects will provide those skilled in the art with an enablingdescription for implementing an example aspect. It should be understood that various changes may be made in the function and arrangement of elements without departing from the scope of the application as set forth in the appended claims.

[0026] Wireless communication networks can be deployed to provide various communication services, such as voice, video, packet data, messaging, broadcast, any combination thereof, or other communication services. A wireless communication network may support both access links and sidelinks for communication between wireless devices. An access link may refer to any communication link between a client device (e.g., a user equipment (UE), a station (STA), or other client device) and a base station (e.g., a 3GPP gNB for 5G / NR, a 3GPP eNB for 4G / LTE, a Wi-Fi access point (AP), or other base station). For example, an access link may support uplink signaling, downlink signaling, connection procedures, etc. An example of an access link is a Uu link or interface (also referred to as an NR-Uu) between a 3 GPP gNB and a UE.

[0027] A wireless communication network can utilize multiple carriers within frequency bands to implement multiple access techniques, where multiple network devices (e.g., UEs, etc.) share the same carrier frequency based on dividing access in time, frequency, code, etc. Component carriers (CCs) can be used as bandwidth parts for aggregating spectrum and / or frequency bands to increase bandwidth and support higher data rates to individual UEs or other network devices. For example, carrier aggregation (CA) can be implemented for a UE to aggregate multiple carriers into a single logical channel for use in performing uplink and downlink transmissions associated with the UE.

[0028] Carrier aggregation may also be referred to as multi carrier aggregation (multi CA). The aggregated carriers (e.g., aggregated CCs) can be within the same frequency band and / or can be within different frequency bands of the wireless communication network. CA performed using CCs within the same frequency band can be referred to as intra-band CA. CA performed using CCs across multiple (e.g., different) frequency bands can be referred to as inter-band CA. In some examples, 5G NR may utilize a flexible carrier structure, where CCs vary in bandwidth up to 400 MHz in the mmWave spectrum (e.g., frequency range 2 (FR2)) and up to 100 MHz in the sub-6 GHz bands (e.g., frequency range 1 (FR1 )). A single cell of the network can operate on one or more carriers, across one or more frequency bands. In some cases, the same carrier can be used by multiple cells, based on the network implementing one or more frequency reusetechniques (e.g., dynamic spectrum sharing (DSS), beamforming and / or massive multiple input multiple output (MIMO), inter-cell interference coordination (ICIC) and / or enhanced ICIC, etc.).

[0029] A C A configuration for a UE can be associated with a primary component carrier (PCC) and one or more secondary component carriers (SCCs). The PCC can be selected as a CC that will be used as the main (e.g., primary) carrier for providing primary radio resources for the uplink and downlink transmissions of the UE. For example, the PCC may be selected as a particular CC with a wider bandwidth and / or stronger coverage to the UE than the CCs configured as SCCs of the CA configuration. The PCC can be used for signaling and control functions associated with the CA configuration and implementation thereof at the UE, and may be used to establish the initial connection with the network and to subsequently manage the CA-enabled communication session. SCCs can be configured as additional carriers (e.g., additional CCs) that are aggregated with the PCC into a single logical channel for the uplink and downlink transmissions of the UE. As noted previously, the PCC and SCCs may be within the same frequency band (e.g., intra-band CA) and / or may be within different frequency bands (e.g., inter-band CA).

[0030] The aggregation of one or more SCCs with the PCC of the UE can be used to increase the overall data throughput and communications performance of the UE. In some examples, SCCs can be dynamically added and / or removed from the CA configuration implemented by aUE. For example, SCC addition and / or SCC removal can be performed based on network conditions, UE capabilities, UE measurement reports, etc. In some examples, the addition and / or removal of one or more SCCs can also be referred to as a CA reconfiguration.

[0031] For example, CA reconfiguration may be performed by and / or for a UE based on changing network conditions, handover or mobility events, etc. During handover or mobility events, the UE may be configured to update or reconfigure its CA configuration to add and activate a new PCC (and remove the current PCC). The UE may be configured to update or reconfigure its CA configuration to add and activate one or more new SCCs. SCC addition and activation may be performed without a corresponding removal of an existing SCC included in the UE CA configuration (e.g., total number of SCCs used for CA increases). In some examples, SCC addition and activation can be performed incombination with the removal of one or more existing SCCs from the UE CA configuration (e.g., total number of SCCs used for CA stays the same or decreases).

[0032] In some examples, carrier aggregation can be implemented and / or configured for a UE based on one or more radio resource control (RRC) messages between the UE and a network entity (e.g., gNB, base station, etc.). For example, the one or more RRC messages can be RRC reconfiguration messages. In some cases, the UE can receive an RRC reconfiguration message indicative of an updated CA configuration, corresponding to the addition and / or removal of one or more SCCs.

[0033] To implement an updated CA configuration (e.g., CA reconfiguration), a UE may perform radio frequency (RF) tuning of the SCCs included in the updated CA configuration and / or may perform RF tuning of the PCC. For example, the UE can perform an impacts analysis to determine the particular CCs that are affected by the transition from the current CA configuration of the UE to the updated CA configuration indicated by the RRC reconfiguration message. The CCs impacted by the updated CA configuration can include carriers that are newly added as SCC, a carrier newly added as a PCC, an active SCC or PCC that is removed, etc. The CCs impacted by the updated CA configuration can also include one or more of the PCC and / or SCCs that are maintained in both the current and updated CA configurations for the UE, that must be reconfigured or re-tuned to accommodate the addition of one or more new SCCs.

[0034] The UE can perform RF tuning for at least the CCs that the UE determines are impacted by the updated CA configuration. The RF tuning can be associated with allocating respective RF hardware components of the UE (e.g., a respective RF chain) to each of the impacted CCs. For example, a transceiver resource manager (TRM) of the UE can be configured to perform RF device allocation and scouting to determine respective RF paths for the new SCCs Rx / Tx chains and / or the PCC Rx / Tx chains. As used herein, an Rx / Tx chain may also be referred to as an RF chain, and vice versa. An RF chain can correspond to a sequence of hardware components used to processed RF signals between an antenna and digital baseband system of the UE.

[0035] For example, a UE may include a modem and / or multiple RF front-ends (RFFEs) that can be configured to support (e.g., implement at the UE) a plurality of different RF band combinations. In some cases, a UE can include a plurality of different antennas and a plurality of different RF chain components (e.g., analog-to-digitalconverters (ADCs), low-noise amplifiers (LNAs), phase-locked loops (PLLs), wide-band (WB) paths, narrow-band (NB) paths, etc.) An RF chain can be implemented by the UE as a sequence of particular hardware components each selected from multiple (or shared) instances of each hardware component of the RF chain. For example, a UE may have multiple choices for RF tuning for a given CA band combination (e.g., inter-band or intraband with multiple SCCs).

[0036] In some aspects, RF tuning associated with an updated CA configuration for a UE (e.g., indicated based on an RRC reconfiguration from a network entity) can include TRM device allocation (e.g., RF device allocation) and scouting to determine a corresponding RF path for the new SCCs Rx / Tx chains and the PCC Rx / Tx chains. The TRM device allocation can be an RF device allocation performed by the TRM of the UE, and may be used to allocate the discrete RF hardware components of the UE to a particular SCC or PCC Rx / Tx chain. For example, the UE may implement a respective RF chain for each SCC of the one or more SCCs of the CA configuration, and may implement a respective RF chain for the PCC of the CA configuration. In some cases, the Rx / Tx for a particular SCC and / or for the PCC can be isolated to a corresponding RF antenna of a plurality of RF antennas of the UE. For example, the UE may allocate a respective RF chain (e.g., terminating in a corresponding RF antenna) for the PCC and for each SCC of the CA configuration. The UE may additionally allocate the respective PCC and SCC RF chains such that the RF chains do not share any RF path downstream (e.g., LN A, PLL, WB paths, NB paths, etc.) for analog and digital RF processing.

[0037] After RF device allocation and scouting to determine the RF paths for each SCC and PCC Rx / Tx chain, the UE may perform RF script building. For example, RF script building may correspond to the implementation of the RF path for each SCC and PCC Rx / Tx chain in the RF hardware of the UE. In some examples, an RF script can be indicative of a set of settings on the RF hardware of the UE for implementing a particular RF path and / or PCC or SCC RF chain. For example, an RF script can include a listing of hardware register settings that need to be programmed into the RF hardware of the UE in order to implement the particular RF path and RF chain for the PCC or SCC of the CA configuration. In some aspects, an RF script can be provided as a mapping between high- level settings indicative of configuration parameters for a carrier (e.g., PCC or SCC, the particular channel, bandwidth, power level, timing and synchronization, etc.) and the corresponding low-level RF hardware register values for implementing the high-levelsetting(s). As used herein, an RF script may also be referred to as an RF hardware register configuration, where the RF hardware register configuration includes a plurality of hardware register values that can be used to implement a particular RF path and / or RF chain in the RF hardware of a UE or other network device. In some aspects, the terms “RF script” and “RF hardware register configuration” may be used interchangeably herein. RF script building can also be referred to as determining RF hardware register configurations and / or the determination of RF hardware register configurations.

[0038] After RF script building, the UE performs RF scripts execution to configure the PCC and / or SCC chains of the updated CA configuration in the RF hardware of the UE. For example, after determining the RF hardware register configurations (e.g., RF scripts) for implementing the PCC and SCCs of the earner aggregation, the UE can implement the RF hardware register configurations (e.g., execute the RF scripts) by writing the plurality of hardware register values included in each RF hardware register configuration (e.g., included in each RF script) to the corresponding hardware registers of the UE RF hardware.

[0039] In many examples, RF scripts execution may include the UE causing interruptions on the PCell (e.g., PCC) and / or activated SCells (e.g., activated SCCs) for one or more subframes. The interruption may be for uplink and / or downlink, and may also be referred to as “Rx / Tx blanking.” For example, an interruption of one or more subframes for uplink on the PCC can be referred to as PCC Tx blanking, an interruption of one or more subframes for downlink on the PCC can be referred to as PCC Rx blanking. An interruption of one or more subframes for uplink on an SCC can be referred to as SCC Tx blanking, and an interruption of one or more subframes for downlink on an SCC can be referred to as SCC Rx blanking. During RF script execution, the UE may cause interruptions of one or more subframes (e.g., Rx / Tx blanking) on the PCC and / or on one or more existing SCCs (e.g., SCCs that are not newly added in the updated CA configuration). For example, the UE may cause interruptions at SCell (e.g., SCC) addition or release, activation or deactivation, during measurements on SCC, etc. During the interruptions of one or more subframes for uplink and / or downlink (e.g., Rx / Tx blanking) of a particular carrier (e.g., PCC or SCC), the UE is configured to not receive or transmit on the particular carrier.

[0040] As noted previously, RRC reconfiguration requests can be used to signal and / or cause an updated CA configuration for a UE. The RRC reconfiguration request indicative of the updated CA configuration may be associated with a processing time limit, which may be a pre-defined or configured processing time limit provided by the wireless communication standard or specification. For example, 4G / LTE and 5G / NR utilize a 20 millisecond (ms) RRC processing time requirement for DL RRC messages, where the UE is expected to be ready for the reception of uplink grant for the UE 20ms from the end of reception of the DL RRC message.

[0041] Based on updated CA configuration information being indicated and / or signaled using an RRC reconfiguration request (e.g., a DL RRC message), implementing the updated CA configuration by the UE may be associated with a 20ms RF tuning window. If the UE has not completed RF tuning to implement the updated CA configuration by the end of the configured time window, the UE performance can degrade (e.g., based on the network resuming communications to the UE based on the requirement or expectation that the UE has completed processing of the DL RRC message by the end of the configured 20ms time window). In some examples, where the RF tuning for the CA reconfiguration is associated with PCC interruptions (e.g., Rx / Tx blanking), the UE may additionally miss the reception of key DL / UL grants from the network entity (e.g., gNB, base station, etc.) and / or may miss transmissions to the network entity (e.g., SCC activation MAC-CE, etc.).

[0042] There is a need for systems and techniques that can be used to implement CA configuration and / or CA reconfiguration for a UE within a configured processing time requirement of the network. There is a further need for systems and techniques that can be used to implement CA configuration and / or CA reconfiguration for a UE without interruptions of one or more subframes (e.g., Rx / Tx blanking) on the PCC (e.g., without uplink and / or downlink interruptions of the PCC during RF scripts execution).

[0043] Systems, apparatuses, processes (also referred to as methods), and computer- readable media (collectively referred to as “systems and techniques”) are described herein that can be used to provide optimized multi-carrier configuration for carrier aggregation associated with a network device (e.g., UE, etc.). For example, the systems and techniques can be used to implement a CA configuration and / or CA reconfiguration within a configured processing time limit or configured processing time requirement of thenetwork. In some cases, the systems and techniques can be used to implement the CA configuration or CA reconfiguration within an RRC processing time limit configured by the network and associated with a DL RRC message indicative of the CA configuration or CA reconfiguration. In some aspects, the systems and techniques can be used to implement CA configuration and / or CA reconfiguration for a UE without interruptions (e.g., Rx / Tx blanking) on the PCC associated with the carrier aggregation.

[0044] For example, the systems and techniques can implement optimized multi-carrier configuration for carrier aggregation associated with a UE or other network device based on prioritizing processing for the PCC of the updated CA configuration ahead of processing for one or more SCCs of the updated CA configuration. In some examples, an RF tuning phase associated with implementing the updated CA configuration can be performed using a first RF tuning phase corresponding to the PCC and a second RF tuning phase corresponding to the one or more SCCs. In one illustrative example, RF hardware register script building (e.g., RF hardware register configuration determination) can be performed in a first phase for the PCC only. Based on completing the RF script building for the PCC, the UE can subsequently perform RF hardware register script building for the SCCs in a second phase. In some aspects, the SCC RF script building can be performed in parallel with a PCC retune, where the PCC retune comprises RF tuning for the PCC of the updated CA configuration and is based on the PCC RF script generated during the first phase of RF script building.

[0045] In some cases, the UE can perform RF device allocation using a TRM or RF controller of the UE. Based on completing RF device allocation, RF script building (e.g., (e.g., RF hardware register configuration determination) can be performed in three steps (e.g., three phases) configured to prioritize and complete the PCC Rx / Tx tuning first. For example, the multi-stage RF script building can be configured to prioritize and complete the PCC Rx / Tx tune ahead of the SCCs Rx / Tx tune, and within the network-configured RF tune window for implementing the updated CA configuration (e.g., the 20 ms DL RRC message processing time limit, etc.). In some aspects, prioritizing and performing PCC Rx / Tx script building and executing in the first phase can cause any PCC interruptions (e.g., Rx / Tx blanking) to occur at the beginning of the CA reconfiguration process, and within the 20ms processing time limit. PCC interruptions (e.g., Rx / Tx blanking) within the configured processing time limit are not associated with the UE missing UL / DL grants from the network entity or missing UL transmissions to the network entity, and the UEperformance can thereby be improved.

[0046] In some examples, the UE can be configured to minimize disruption to the PCC during RF device allocation and RF scripts execution associated with implementing the updated CA configuration. For example, for blind SCC addition, the UE can implement an RF device allocation algorithm configured to first attempt to determine an RF device allocation where the PCC Rx and Tx are not blanked (e.g., PCC downlink and uplink are not interrupted, respectively) for the target allocation. If the UE is unable to perform allocation to avoid PCC interruption (e.g., Rx / Tx blanking), the UE may next attempt to perform allocation to assign the PCC Rx / Tx chain to a non-shared antenna (e.g., a dedicated antenna for the PCC Rx / Tx chain).

[0047] In some examples, the UE can be configured to reduce an amount of time associated with performing the RF hardware register script building (e.g., determining the RF hardware register configurations for PCC and / or SCCs), based on the UE determining one or more predicted updated CA configurations prior to receiving the RRC reconfiguration from the network entity indicative of an updated CA configuration for the UE. For example, the UE can determine predicted updated CA configurations using measurement information associated with one or more neighboring cells of the UE. The measurement information can be previously obtained measurement information obtained by the UE in response to a measurement requested and / or configured by the network entity.

[0048] The predicted updated CA configurations determined by the UE can include one or more of a predicted PCC or a predicted SCC for the carrier aggregation implemented at the UE. The predicted PCC or predicted SCC can be based on corresponding measurements of a neighboring cell. For example, the predicted PCC or predicted SCC can correspond to a best or strongest cell of a plurality of neighboring cells previously measured by the UE (e.g., based on the UE predicting that the best or strongest cell indicated in the UE measurement report to the network entity will later be configured as a new PCC or SCC of an updated C A configuration for the UE). In some aspects, the UE can be configured to pre-build a corresponding RF hardware register script for each predicted PCC and / or predicted SCC included in a respective predicted updated CA configuration determined by the UE. In some cases, the pre-built RF script for the predicted PCC or predicted SCC can be obtained as the RF hardware register values usedby the UE to obtain or perform the measurements of the neighbonng cell corresponding to the predicted PCC or predicted SCC. For example, rather than clearing the RF hardware register configuration after completing the measurement, the UE can save or store the RF hardware register configuration for the neighboring cell as the pre-built RF script for a predicted PCC or predicted SCC corresponding to the neighboring cell.

[0049] Based on receiving an RRC reconfiguration request indicative of an updated CA configuration for the UE, the UE can compare an updated PCC and / or one or more updated SCCs of the updated C A configuration to the corresponding predicted PCCs and SCCs of the pre-built RF scripts generated and stored by the UE. In some cases, the UE can determine whether any of the SCCs indicated in the updated CA configuration for the UE are previously measured neighbors for which a pre-built RF script is available. Based on determining that an added SCC of the updated CA configuration is a previously measured neighbor, the UE can obtain the corresponding pre-built RF script for the neighbor and may execute the pre-built RF script without performing RF device allocation, scouting, or RF script building (e.g., determining RF hardware register configurations) for the added SCC of the updated CA configuration.

[0050] Further aspects of the systems and techniques will be described with respect to the figures.

[0051] As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

[0052] As used herein, the terms “user equipment” (UE) and “network entity” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, and / or tracking device, etc.), wearable (e.g., smartwatch, smart-glasses, wearable ring, and / or an extended reality (XR) device such as a virtual reality (VR) headset, an augmented reality (AR) headset or glasses, or a mixed reality (MR) headset), vehicle (e.g., automobile, motorcycle, bicycle, etc.), aircraft (e.g., an airplane, jet, unmanned aerial vehicle (UAV) or drone, helicopter, airship, glider, etc.), and / or Internet of Things (loT) device, etc., used by a user to communicate over a wireless communications network. A UE may be mobileor may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on IEEE 802.11 communication standards, etc.), and so on.

[0053] A network entity can be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or aNon-Real Time (Non- RT) RIC. A base station (e.g., with an aggregated / monolithic base station architecture or disaggregated base station architecture) may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB (NB), an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for the supported UEs. In some systems, a base station may provide edge node signaling functions while in other systems it may provide additional control and / or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, or a forward traffic channel, etc.). The term traffic channel (TCH), as used herein, can refer to either an uplink, reverse or downlink, and / or a forward traffic channel.

[0054] The term “network entity” or “base station” (e.g., with an aggregated / monolithic base station architecture or disaggregated base station architecture) may refer to a singlephysical transmit receive point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term “network entity” or “base station” refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term “network entity” or “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (e.g., a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (e.g., a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals (e.g., or simply “reference signals”) the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station.

[0055] In some implementations that support positioning of UEs, a network entity or base station may not support wireless access by UEs (e.g., may not support data, voice, and / or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and / or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and / or as a location measurement unit (e.g., when receiving and measuring signals from UEs).

[0056] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first networknode may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.

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

[0058] An RF signal comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.

[0059] Various aspects of the systems and techniques described herein will be discussed below with respect to the figures. According to various aspects, FIG. 1 illustrates an example of a wireless communications system 100. The wireless communications system 100 (e.g., which may also be referred to as a wireless wide area network (WWAN)) can include various base stations 102 and various UEs 104. In some aspects, the base stations 102 may also be referred to as “network entities” or “network nodes.” One or more of the base stations 102 can be implemented in an aggregated or monolithic base station architecture. Additionally, or alternatively, one or more of the base stations 102 can be implemented in a disaggregated base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a Near-Real Time (Near- RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC. The base stations 102 can include macro cell base stations (e.g., high power cellular base stations) and / or small cell base stations (e.g., low power cellular base stations). In an aspect, the macro cell base station may include eNBs and / or ng-eNBs where the wireless communications system 100 corresponds to a long-term evolution (LTE) network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0060] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaullinks 122, and through the core network 170 to one or more location servers 172 (e.g., which may be part of core network 170 or may be external to core network 170). In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC or 5GC) over backhaul links 134, which may be wired and / or wireless.

[0061] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by abase station 102 in each coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI), a cell global identifier (CGI)) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband loT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” may be used interchangeably. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.

[0062] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. Forexample, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

[0063] The communication links 120 between the base stations 102 and the UEs 104 may include uplink (e.g., also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (e.g., also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 may be provided using one or more earner frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., a greater or lesser quantity of carriers may be allocated for downlink than for uplink).

[0064] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., one or more of the base stations 102, UEs 104, etc.) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be implemented based on combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0065] A transmitting device and / or a receiving device (e.g., such as one or more of base stations 102 and / or UEs 104) may use beam sweeping techniques as part of beamforming operations. For example, a base station 102 (e.g., or other transmitting device) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 104 (e.g., or other receiving device). Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by base station 102 (or other transmitting device) multiple times in different directions. For example, the base station 102 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by atransmitting device, such as a base station 102, or by a receiving device, such as a UE 104) a beam direction for later transmission or reception by the base station 102.

[0066] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a base station 102 in a single beam direction (e.g., a direction associated with the receiving device, such as a UE 104). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted in one or more beam directions. For example, a UE 104 may receive one or more of the signals transmitted by the base station 102 in different directions and may report to the base station 104 an indication of the signal that the UE 104 received with a highest signal quality or an otherwise acceptable signal quality.

[0067] In some examples, transmissions by a device (e.g., by a base station 102 or a UE 104) may be performed using multiple beam directions, and the device may use a combination of digital preceding or radio frequency beamforming to generate a combined beam for transmission (e.g., from a base station 102 to a UE 104, from a transmitting device to a receiving device, etc.). The UE 104 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across a system bandwidth or one or more sub-bands. The base station 102 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), etc.), which may be precoded or unprecoded. The UE 104 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multipanel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted in one or more directions by a base station 102, a UE 104 may employ similar techniquesfor transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 104) or for transmitting a signal in a single direction (e.g., for transmitting data to a receiving device).

[0068] A receiving device (e.g., a UE 104) may try multiple receive configurations (e.g., directional listening) when receiving various signals from the base station 102, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal qualify based on listening according to multiple beam directions).

[0069] The wireless communications system 100 may further include a WLAN AP 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 Gigahertz (GHz)). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available. In some examples, the wireless communications system 100 can include devices (e.g., UEs, etc.) that communicate with one or more UEs 104, base stations 102, APs 150, etc., utilizing the ultra- wideband (UWB) spectrum. The UWB spectrum can range from 3.1 to 10.5 GHz.

[0070] The small cell base station 102' may operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensedfrequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE and / or 5G in an unlicensed frequency spectrum, may boost coverage to and / or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0071] The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and / or near mmW frequencies in communication with a UE 182. The mmW base station 180 may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture (e.g., including one or more of a CU, a DU, a RU, a Near-RT RIC, or a Non-RT RIC). Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW and / or near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (e g., transmit and / or receive) over an mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[0072] In some aspects relating to 5G, the frequency spectrum in which wireless network nodes or entities (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges, FR1 (e.g., from 450 to 6,000 Megahertz (MHz)), FR2 (e.g., from 24,250 to 52,600 MHz), FR3 (e.g., above 52,600 MHz), and FR4 (e.g., between FR1 and FR2). In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE104 / 182 and the cell in which the UE 104 / 182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection reestablishment procedure. The primary carrier carries all common and UE-specific control channels and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary' carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell may have different downlink primary earners. The same is true for the uplink primary carriers. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (e.g., whether a PCell or an SCell) corresponds to a carrier frequency and / or component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component earner,” “carrier frequency,” and the like can be used interchangeably.

[0073] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and / or the mmW base station 180 may be secondary carriers (“SCells”). In carrier aggregation, the base stations 102 and / or the UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100 MHz) bandwidth per earner up to a total of Yx MHz (e.g., x component carriers) for transmission in each direction. The component carriers may or may not be adjacent to each other on the frequency spectrum. Allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., a greater or lesser quantity of carriers may be allocated for downlink than for uplink). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (e.g., 40 MHz), compared to that attained by a single 20 MHz carrier.

[0074] In order to operate on multiple carrier frequencies, a base station 102 and / or a UE 104 can be equipped with multiple receivers and / or transmitters. For example, a UE 104 may have two receivers, “Receiver 1” and “Receiver 2,” where “Receiver 1” is a multi-band receiver that can be tuned to band (e.g., carrier frequency) ‘X’ or band ‘Y,’ and “Receiver 2” is a one-band receiver tunable to band Z’ only. In this example, if the UE 104 is being served in band ‘X,’ band ‘X’ would be referred to as the PCell or the active earner frequency, and “Receiver 1” would need to tune from band ‘X’ to band ‘Y’ (e.g., an SCell) in order to measure band ‘Y’ (and vice versa). In contrast, whether the UE 104 is being served in band ‘X’ or band ‘Y,’ because of the separate “Receiver 2,” the UE 104 can measure band ‘Z‘ without interrupting the service on band ‘X’ or band ‘Y’

[0075] The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and / or the mmW base station 180 over an mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164.

[0076] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (e.g., referred to as “sidelinks”). In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (e.g., through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), Wi-Fi Direct (Wi-Fi-D), Bluetooth®, and so on.

[0077] FIG. 2 illustrates a block diagram of an example architecture 200 of a base station 102 and a UE 104 that enables transmission and processing of signals exchanged between the UE and the base station, in accordance with some aspects of the present disclosure. Example architecture 200 includes components of a base station 102 and a UE 104, which may be one of the base stations 102 and one of the UEs 104 illustrated in FIG. 1. Base station 102 may be equipped with T antennas 234a through 234t, and UE 104 may be equipped with R antennas 252a through 252r, where in general T>1 and R>1.

[0078] At base station 102, a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and / or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and / or the like) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS)) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS)). Atransmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. The modulators 232a through 232t are shown as a combined modulator-demodulator (MOD-DEMOD). In some cases, the modulators and demodulators can be separate components. Each modulator of the modulators 232a to 232t may process a respective output symbol stream (e.g., for an orthogonal frequencydivision multiplexing (OFDM) scheme and / or the like) to obtain an output sample stream. Each modulator of the modulators 232a to 232t may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals may be transmitted from modulators 232a to 2321 via T antennas 234a through 2341, respectively. According to certain aspects described in more detail below, the synchronization signals can be generated with location encoding to convey additional information.

[0079] At UE 104, antennas 252a through 252r may receive the downlink signals from base station 102 and / or other base stations and may provide received signals to one or more demodulators (DEMODs) 254a through 254r, respectively. The demodulators 254a through 254r are shown as a combined modulator-demodulator (MOD-DEMOD). In some cases, the modulators and demodulators can be separate components. Each demodulator of the demodulators 254a through 254r may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator of the demodulators 254a through 254r may further process the input samples (e.g., forOFDM and / or the like) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 104 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. A channel processor may determine reference signal received power (RSRP), received signal strength indicator (RS SI), reference signal received quality (RSRQ), channel quality indicator (CQI), and / or the like.

[0080] On the uplink, at UE 104, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and / or the like) from controller / processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals (e.g., based on a beta value or a set of beta values associated with the one or more reference signals). The symbols from transmit processor 264 may be precoded by a TX-MIMO processor 266, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, and / or the like), and transmitted to base station 102. At base station 102, the uplink signals from UE 104 and other UEs may be received by antennas 234a through 234t, processed by demodulators 232a through 232t, detected by a MIMO detector 236 (e.g., if applicable), and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 104. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller (e.g., processor) 240. Base station 102 may include communication unit 244 and communicate to a network controller 231 via communication unit 244. Network controller 231 may include communication unit 294, controller / processor 290, and memory 292.

[0081] In some aspects, one or more components of UE 104 may be included in a housing. Controller 240 of base station 102, controller / processor 280 of UE 104, and / or any other component(s) of FIG. 2 may perform one or more techniques associated with implicit UCI beta value determination for NR.

[0082] Memories 242 and 282 may store data and program codes for the base station 102 and the UE 104, respectively. A scheduler 246 may schedule UEs for data transmission on the downlink, uplink, and / or sidelink.

[0083] In some aspects, deployment of communication systems, such as 5G new radio (NR) systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (e.g., such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmit receive point (TRP), or a cell, etc.) may be implemented as an aggregated base station (e.g., also known as a standalone BS or a monolithic BS) or a disaggregated base station.

[0084] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be colocated with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0085] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (e.g., such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (e.g., vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0086] FIG. 3 is a diagram illustrating an example disaggregated base station 300 architecture. The disaggregated base station 300 architecture may include one or more central units (CUs) 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units (e.g., such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 325 via an E2 link, or a Non-Real Time (Non-RT) RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an Fl interface. The DUs 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RUs 340 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 340.

[0087] Each of the units (e.g., the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305) illustrated in FIG. 3 and / or described herein may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (e g., collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (e.g., such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0088] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU-UP)), control plane functionality (e.g., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP unitsand one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with the DU 330, as necessary, for network control and signaling.

[0089] The DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 330 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

[0090] Lower-layer functionality can be implemented by one or more RUs 340. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (e.g., such as performing fast Fourier transform (FFT), inverse FFT (1FFT), digital beamforming, physical randomaccess channel (PRACH) extraction and filtering, or the like), or both, based on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 340 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable the DU(s) 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0091] The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (e.g., such as an 01 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (e.g., such as an open cloud (O-Cloud) 390) to performnetwork element life cycle management (e.g., such as to instantiate virtualized network elements) via a cloud computing platform interface (e.g., such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with one or more RUs 340 via an 01 interface. The SMO Framework 305 also may include aNon-RT RIC 315 configured to support functionality of the SMO Framework 305.

[0092] The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (e.g., such as via an Al interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (e.g., such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

[0093] In some implementations, to generate AI / ML models to be deployed in the Near- RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from nonnetwork data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 305 (e.g., such as reconfiguration via 01) or via creation of RAN management policies (e.g., such as Al policies).

[0094] FIG. 4 illustrates an example of a computing system 470 of a wireless device 407. The wireless device 407 may include a client device such as a UE (e.g., UE 104, UE 152, UE 190) or other type of device (e.g., a station (STA) configured to communicationusing a Wi-Fi interface) that may be used by an end-user. For example, the wireless device 407 may include a mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., a smart watch, glasses, an extended reality (XR) device such as a virtual reality (VR), augmented reality (AR), or mixed reality (MR) device, etc.), Internet of Things (loT) device, a vehicle, an aircraft, and / or another device that is configured to communicate over a wireless communications network. The computing system 470 includes software and hardware components that may be electrically or communicatively coupled via a bus 489 (e.g., or may otherwise be in communication, as appropriate). For example, the computing system 470 includes one or more processors 484. The one or more processors 484 may include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, dedicated hardware, any combination thereof, and / or other processing device or system. The bus 489 may be used by the one or more processors 484 to communicate between cores and / or with the one or more memory devices 486.

[0095] The computing system 470 may also include one or more memory devices 486, one or more digital signal processors (DSPs) 482, one or more SIMs 474, one or more modems 476, one or more wireless transceivers 478, an antenna 487, one or more input devices 472 (e.g., a camera, a mouse, a keyboard, a touch sensitive screen, a touch pad, a keypad, a microphone, and / or the like), and one or more output devices 480 (e.g., a display, a speaker, a printer, and / or the like).

[0096] In some aspects, computing system 470 may include one or more radio frequency (RF) interfaces configured to transmit and / or receive RF signals. In some examples, an RF interface may include components such as modem(s) 476, wireless transceiver(s) 478, and / or antennas 487. The one or more wireless transceivers 478 may transmit and receive wireless signals (e.g., signal 488) via antenna 487 from one or more other devices, such as other wireless devices, network devices (e.g., base stations such as eNBs and / or gNBs, Wi-Fi access points (APs) such as routers, range extenders or the like, etc.), cloud networks, and / or the like. In some examples, the computing system 470 may include multiple antennas or an antenna array that may facilitate simultaneous transmit and receive functionality. Antenna 487 may be an omnidirectional antenna such that radio frequency (RF) signals may be received from and transmitted in all directions. The wireless signal 488 may be transmitted via a wireless network. The wireless network may be any wireless network, such as a cellular or telecommunications network (e.g., 3G, 4G,5G, etc.), wireless local area network (e.g., a Wi-Fi network), a Bluetooth™ network, and / or other network.

[0097] In some examples, the wireless signal 488 may be transmited directly to other wireless devices using sidelink communications (e.g., using a PC5 interface, using a DSRC interface, etc.). Wireless transceivers 478 may be configured to transmit RF signals for performing sidelink communications via antenna 487 in accordance with one or more transmit power parameters that may be associated with one or more regulation modes. Wireless transceivers 478 may also be configured to receive sidelink communication signals having different signal parameters from other wireless devices.

[0098] In some examples, the one or more wireless transceivers 478 may include an RF front end including one or more components, such as an amplifier, a mixer (e.g., also referred to as a signal multiplier) for signal down conversion, a frequency synthesizer (e.g., also referred to as an oscillator) that provides signals to the mixer, a baseband filter, an analog-to-digital converter (ADC), one or more power amplifiers, among other components. The RF front-end may generally handle selection and conversion of the wireless signals 488 into a baseband or intermediate frequency and may convert the RF signals to the digital domain.

[0099] In some cases, the computing system 470 may include a coding-decoding device (or CODEC) configured to encode and / or decode data transmited and / or received using the one or more wireless transceivers 478. In some cases, the computing system 470 may include an encryption-decryption device or component configured to encrypt and / or decrypt data (e.g., according to the AES and / or DES standard) transmited and / or received by the one or more wireless transceivers 478.

[0100] The one or more SIMs 474 may each securely store an international mobile subscriber identity (IMSI) number and related key assigned to the user of the wireless device 407. The IMSI and key may be used to identify and authenticate the subscriber when accessing a network provided by a network service provider or operator associated with the one or more SIMs 474. The one or more modems 476 may modulate one or more signals to encode information for transmission using the one or more wireless transceivers 478. The one or more modems 476 may also demodulate signals received by the one or more wireless transceivers 478 in order to decode the transmited information. In some examples, the one or more modems 476 may include a Wi-Fi modem, a 4G (or LTE)modem, a 5G (or NR) modem, and / or other types of modems. The one or more modems 476 and the one or more wireless transceivers 478 may be used for communicating data for the one or more SIMs 474.

[0101] The computing system 470 may also include (and / or be in communication with) one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 486), which may include, without limitation, local and / or network accessible storage, a disk drive, a drive array, an optical storage device, a solid- state storage device such as a RAM and / or a ROM, which may be programmable, flash- updateable, and / or the like. Such storage devices may be configured to implement any appropriate data storage, including without limitation, various file systems, database structures, and / or the like.

[0102] In various aspects, functions may be stored as one or more computer-program products (e.g., instructions or code) in memory device(s) 486 and executed by the one or more processor(s) 484 and / or the one or more DSPs 482. The computing system 470 may also include software elements (e.g., located within the one or more memory devices 486), including, for example, an operating system, device drivers, executable libraries, and / or other code, such as one or more application programs, which may comprise computer programs implementing the functions provided by various aspects, and / or may be designed to implement methods and / or configure systems, as described herein.

[0103] FIG. 5 is a diagram illustrating an example 500 of physical channels and reference signals in a wireless network. In some examples, one or more downlink channels and one or more downlink reference signals may carry information from a base station 102 to a UE 104. One or more uplink channels and one or more uplink reference signals may carry information from UE 104 to base station 102.

[0104] In some aspects, a downlink channel may include one or more of a physical downlink control channel (PDCCH) that carries downlink control information (DCI), a physical downlink shared channel (PDSCH) that carries downlink data, and / or a physical broadcast channel (PBCH) that carries system information, among other examples. In some aspects, PDSCH communications may be scheduled by PDCCH communications.

[0105] In some examples, an uplink channel may include one or more of a physical uplink control channel (PUCCH) that carries uplink control information (UCI), a physical uplink shared channel (PUSCH) that carries uplink data, and / or a physical random accesschannel (PRACH) used for initial network access, among other examples. In some aspects, UE 104 may transmit acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in UCI on the PUCCH and / or the PUSCH.

[0106] In some cases, a downlink reference signal may include one or more of a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), and / or a phase tracking reference signal (PTRS), among other examples. In some examples, an uplink reference signal may include one or more of a sounding reference signal (SRS), a DMRS, and / or a PTRS, among other examples.

[0107] An SSB may carry or include information used for initial network acquisition and synchronization. For example, an SSB can carry or include one or more of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and / or a PBCH DMRS. An SSB may also be referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, base station 102 may transmit multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0108] A CSI-RS may cany information used for downlink channel estimation (e g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, among other examples. For example, base station 102 can configure a set of CSI-RSs for UE 104, and UE 104 can measure the configured set of CSI-RSs. Based on the CSI-RS measurements, UE 104 can perform channel estimation and report channel estimation parameters to base station 102 (e.g., in a CSI report). For example, the channel estimation parameters can include one or more of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), and / or a reference signal received power (RSRP), among other examples.

[0109] In some examples, base station 102 can use the CSI report to select transmission parameters for downlink communications to UE 104. For example, base station 102 can use the CSI report to select transmission parameters that include one or more of a quantity of transmission layers (e.g., a rank), a precoding matrix (e.g., a precoder), a modulation and coding scheme (MCS), and / or a refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), among other examples.

[0110] A DMRS may carry information used to estimate a radio channel for demodulation of an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of a DMRS may be specific to a physical channel for which the DMRS is used for estimation. DMRSs are UE-specific, can be beamformed, can be confined in a scheduled resource (e.g., rather than transmitted on a wideband), and can be transmitted only when necessary. As shown, DMRSs are used for both downlink communications and uplink communications.10111] APTRS can carry information used to compensate for oscillator phase noise. In some cases, oscillator phase noise may increase as an oscillator carrier frequency increases. In some examples, a PTRS can be utilized at high carrier frequencies (e.g., such as millimeter wave frequencies) to mitigate oscillator phase noise. The PTRS may be used to track the phase of the local oscillator and to enable suppression of phase noise and common phase error (CPE). As illustrated in FIG. 5, in some examples one or more PTRSs can be used for both downlink communications (e.g., on the PDSCH) and uplink communications (e.g., on the PUSCH).

[0112] A PRS may carry information associated with timing or ranging measurements of UE 104. For example, UE 104 may utilize one or more signals (e.g., PRSs) transmitted by base station 102 to improve an observed time difference of arrival (OTDOA) positioning performance. In some examples, a PRS may be a pseudo-random Quadrature Phase Shift Keying (QPSK) sequence mapped in diagonal patterns with shifts in frequency and time to avoid collision with cell-specific reference signals and control channels (e.g., a PDCCH). A PRS can be designed to improve detectability by UE 104, which may need to detect downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Accordingly, UE 104 may receive a PRS from multiple cells (e.g., a reference cell and one or more neighbor cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRSs received from the multiple cells. In some aspects, base station 102 can calculate a position of UE 104 based on the RSTD measurements reported by UE 104.

[0113] In some examples, an SRS can cany information used for uplink channel estimation, which may be used for scheduling, link adaptation, precoder selection, and / or beam management, among other examples. Base station 102 can configure one or more SRS resource sets for UE 104, and UE 104 can transmit SRSs on the configured SRSresource sets. An SRS resource set may have a configured usage, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operations, uplink beam management, among other examples. Base station 102 may measure the SRSs, may perform channel estimation based on the measurements, and / or may use the SRS measurements to configure communications with UE 104.

[0114] As noted previously, systems and techniques are provided herein that can be used to provide optimized multi-carrier configuration for carrier aggregation (CA) associated with a network device (e.g., such as a UE, etc.). For example, the systems and techniques can be used to implement a CA configuration and / or CA reconfiguration for the UE within a configured processing time (e.g., a configured processing time limit or time window, such as a network-defined DL RRC processing time limit, etc.).

[0115] FIG. 6 is a diagram illustrating an example timeline 600 associated with CA tuning to implement a CA configuration for a UE or network device, in accordance with some examples. In some aspects, the example timeline 600 of FIG. 6 may also be referred to as a CA tuning timeline 600. The CA tuning timeline 600 can correspond to a carrier aggregation configuration and / or an updated carrier configuration (e.g., a CA reconfiguration) provided to a UE or other network device, by a network entity (e.g., gNB, base station, etc.).

[0116] In some aspects, the CA tuning process and / or CA tuning timeline 600 of FIG. can be implemented by, performed by, and / or associated with a UE, including any of the UEs of FIGS. 1-5. For example, the CA tuning process and / or CA tuning timeline 600 can be implemented by, performed by, and / or associated with one or more of a modem of a UE, a transceiver resource manager (TRM) associated with RF front end (RFFE) configurations of a UE, etc.

[0117] The CA tuning timeline 600 can correspond to the UE being configured to implement an updated CA configuration. As used herein, an updated CA configuration can refer to a new CA configuration for a UE (e.g., where the UE previously did not have or implement a CA configuration) and / or can refer to an updated CA configuration for a UE (e.g., a CA reconfiguration that updates the current CA configuration of the UE).

[0118] For example, CA tuning timeline 600 can correspond to a UE updating or reconfiguring its carrier aggregation configuration, and may be performed based on (e.g., in response to) factors such as changing network conditions, handover or mobility events,etc. For example, during handover or mobility events where a UE moves between and / or is configured to perform wireless communication using different cells of the network, the PCC associated with multi-carrier aggregation by the UE may be updated and / or one or more SCCs associated with the multi-carrier aggregation by the UE may be updated.

[0119] For example, the UE may update or reconfigure its CA configuration to add and activate a new PCC (e.g. , and to remove and deactivate the previous PCC used for multicarrier aggregation). In some examples, the UE may update or reconfigure its CA configuration to add and activate one or more additional SCCs (e.g., one or more additional SCCs that were not previously used for multi-carrier aggregation at the UE). SCC addition and activation may be performed without a corresponding removal of an existing SCC included in the UE CA configuration (e.g., the total number of SCCs used for CA increases). In some examples, SCC addition and activation can be performed in combination with the removal of one or more existing SCCs from the UE CA configuration (e.g., the total number of SCCs used for CA stays the same or decreases).

[0120] As noted previously, carrier aggregation can be implemented and / or configured for a UE based on one or more radio resource control (RRC) messages between the UE and a network entity (e.g., gNB, base station, etc.). For example, the one or more RRC messages can be RRC reconfiguration messages. In some cases, the UE can receive an RRC reconfiguration message indicative of an updated CA configuration, corresponding to the addition and / or removal of one or more SCCs.

[0121] In one illustrative example, the CA tuning timeline 600 of FIG. 6 can be associated with a CA tuning window 602, representing a time window or time duration in which the UE is expected to complete the processing and implementation of an updated CA configuration signaled to the UE by a network entity. In some aspects, the CA tuning window 602 of the CA tuning timeline 600 can be triggered by the reception (e.g., by the UE) of an RRC reconfiguration request indicative of an updated CA configuration for the UE. The reception of the RRC reconfiguration request can correspond to a start time 652 of the configured CA tuning window 602. The CA tuning window 602 may also be referred to as an RF tuning window and / or a carrier aggregation RF tuning window. The CA tuning window 602 and the start time 652 may be associated with a corresponding tuning window end time 654, where the CA tuning window 602 extends between the start time 652 and the end time 654.

[0122] In some aspects, the CA tuning window 602 can be determined based on a configured processing time limit of the UE and / or associated with the RRC reconfiguration request transmitted to the UE by the network entity. For example, the CA tuning window 602 can be a pre-determined (e.g., pre-configured) number of subframes, milliseconds, etc., from the end of the DL reception of the RRC reconfiguration request indicative of the updated C A configuration for the UE. F or example, the length or duration of the CA tuning window 602 can be equal to the configured processing time limit, and the tuning window end time 654 can be offset from (e.g., later than) the tuning window start time 652 by a time offset equal to the configured processing time limit.

[0123] In one illustrative example, the RRC reconfiguration request indicative of the updated CA configuration is associated with a processing time limit that is a pre-defined or pre-configured processing time limit provided by the wireless communication standard or specification. For example, 4G / LTE and 5G / NR utilize a 20 millisecond (ms) RRC processing time requirement for DE RRC messages, where the UE is expected to be ready for the reception of an uplink grant for the UE 20ms from the end of reception of the DL RRC message. For example, the CA tuning window 602 and tuning window end time 654 can be determined based on the configured RRC processing time requirement for a DL RRC message (e.g., 20ms). In some cases, the configured 20ms processing time limit can include the processing time of UE functionalities that are performed only once for all received RRC segments of the DL RRC message (e g., the configured 20ms processing time limit can be independent of the DL RRC message size).

[0124] Based on updated CA configuration information being indicated and / or signaled using an RRC reconfiguration request (e.g., a DL RRC message), implementing the updated CA configuration by the UE can correspond to a network requirement or expectation that the UE complete processing for the CA tuning timeline 600 within the configured C A tuning window 602 (e.g., complete processing by the tuning window end time 654). As illustrated in the example C A tuning timeline 600 of FIG. 6, the actual total processing time 604 of the CAtune to implement the updated CA configuration at the UE may be longer than the configured 20ms C A tuning window 602 (e.g., the C A tuning 600 is completed after the tuning window end time 654). For example, the actual processing time for implementing the updated CA configuration at the UE can be 32.3ms, which exceeds the configured 20ms CA tuning window limit 602 by a 12.3ms window exceeded time 606.

[0125] The CA tuning timeline 600 of FIG. 6 includes a plurality of 1ms subframes 605, indicative of an example processing time start and end for the different stages of the CA tune. The start time 652 for CA tuning window 602 can be within subframe 1 of the plurality of 1ms subframes 605, and the end time 654 for CA tuning window 602 can be between subframes 20 and 21 of the plurality of 1ms subframes 605 (e.g., corresponding to a CA tuning window duration of 20ms).

[0126] The RF CONFIG COMPLETE block 648 can correspond to the UE completing the CA tuning to implement (e.g., within the RF hardware of the UE) the corresponding RF configuration for the updated CA configuration. In the example CA tuning timeline 600 of FIG. 6, the RF_CONFIG_COMPLETE block 648 occurs within subframe 33, and corresponds to a 12.3ms tuning window exceeded time 606 that runs between the tuning window end time 654 and the RF CONFIG COMPLETE block 648 and / or corresponding DCI-0 grant 664.

[0127] In some aspects, the network (e.g., the network entity that transmitted the updated CA configuration to the UE corresponding to the tuning window start time 652) expects the UE to have completed the carrier aggregation processing and configuration implementation by the tuning window end time 654. For example, beginning from the subframe 21, the network entity expects the UE shall be ready for the reception of downlink and / or uplink grants, and shall be ready to perform uplink transmissions to the network entity.

[0128] Based on the total (e.g., actual) CA tune processing time 604 exceeding the configured CA tuning window limit 602, a mismatch can occur between the network entity expectation of the UE state of readiness for uplink and / or downlink transmission to and from the network entity, and the actual UE state of readiness for the uplink and / or downlink transmission to and from the network entity. In one illustrative example, within the CA tuning window exceeded time 606, the UE may miss one or more DL / UL grants from the network entity, may miss one or more DL transmissions from the network entity, may miss one or more UL transmission to the network entity, etc.

[0129] If the UE has not completed RF tuning to implement the updated CA configuration by the end time 654 of the configured tuning window 602, the UE performance can degrade (e.g., based on the network resuming communications to the UE based on the requirement or expectation that the UE has completed processing of theDL RRC message by the end time 654 of the configured 20ms time window 602). In some examples, where the RF tuning for the CA reconfiguration is associated with PCC interruption (e.g., Rx / Tx blanking), the UE may additionally miss the reception of key DL / UL grants from the network entity (e.g., gNB, base station, etc.) and / or may miss transmissions to the network entity (e.g., SCC activation MAC-CE, etc.). For example, the missed DL / UL grants or transmissions between the UE and the network entity may correspond to downlink interruption 642 (e.g., also referred to as Rx blanking 642) and / or uplink interruption 646 (e.g., also referred to as Tx blanking 646) on the PCC of the UE, where the downlink interruption 642 or uplink interruption 646 occurs within the CA tuning window exceeded time 606.

[0130] In some aspects, the tuning performed by the UE to implement an updated CA configuration can include an OTA handling block 610, an RF configuration check and scouting block 620 (e.g., “RF CHECK CONFIG REQ / CNF”), an RF hardware register script building block 630 (e.g., “RF CONFIG REQ / CNF (split script build)”), and an RF scripts execution block 640 (e.g., “FW_EXEC” corresponding to execution of the RF scripts in firmware of the UE).

[0131] The OTAhandling block 610 can correspond to over-the-air (OTA) decoding of L2 and / or RRC messages received by the UE. For example, the OTAhandling block 610 can correspond to the RRC OTA decode of the RRC reconfiguration request indicative of the updated CA configuration for the UE. The processing associated with the OTA handling block 610 can be used by the UE to determine information of the new or updated CA configuration that is to be implemented at the UE for multi-carrier aggregation. For example, the UE can determine information associated with RF tuning of the SCCs included in the updated CA configuration and / or information associated with RF tuning of the PCC included in the updated CA configuration.

[0132] In some aspects, within OTA handling block 610 and / or in parallel with OTA handling block 610 (e.g., before RF script building blocks 620 and 630), the UE can perform an impacts analysis to determine the particular carriers (e.g., particular CCs) that are affected by the transition from the current CA configuration of the UE to the updated CA configuration indicated by the RRC reconfiguration request. The CCs impacted by the updated CA configuration can include carriers that are newly added as SCCs, a carrier newly added as a PCC, an active SCC or PCC that is removed, etc. The CCs impacted bythe updated CA configuration can also include one or more of the PCC and / or SCCs that are maintained in both the current and updated CA configurations for the UE, but are impacted by the allocation of RF hardware components to the respective RF paths and RF chains for the additional SCCs indicated in the updated CA configuration.

[0133] Based on the determined impact to the existing PCC and / or existing SCCs, the impacted PCC and / or impacted SCCs will be reconfigured or re-tuned to accommodate the addition of one or more new SCCs, and can be included in the set of CCs determined or identified by the UE as impacted by the updated CA configuration. For example, the impacted carriers can be analyzed and a corresponding reconfiguration or re-tuning can be determined as a corresponding RF device allocation for the RF path and / or RF chain of each impacted carrier, at an RF device allocation (e.g., TRM device allocation) step.

[0134] For example, the CA tuning timeline 600 can include an RF device allocation and scouting step, which may be performed in parallel with the OTA handling 610 of the RRC reconfiguration request. For example, the RF device allocation and scouting can be performed by a transceiver resource manager (TRM) of the UE, and may also be referred to as TRM device allocation and scouting. In some cases, the OTA handling 610 is performed between subframes 1-6. In the example of FIG. 6, the RF device allocation can be performed between subframes 4-6, and the TRM early scouting can be performed between subframes 6-7.

[0135] The RF device allocation can comprise allocating respective RF hardware components of the UE (e g., a respective RF chain) to each of the impacted CCs determined to be affected by the updated CA configuration. For example, the TRM of the UE can be configured to perform RF device allocation and scouting to determine respective RF paths for the new SCCs Rx / Tx chains and / or the PCC Rx / Tx chains. As used herein, an Rx / Tx chain may also be referred to as an RF chain, and vice versa. An RF chain can correspond to a sequence of hardware components used to processed RF signals between an antenna and digital baseband system of the UE. In some aspects, UE may include a modem and / or multiple RF front-ends (RFFEs) that can be configured to support (e.g., implement at the UE) a plurality of different RF band combinations. In some cases, a UE can include a plurality of different antennas and a plurality of different RF chain components (e.g., analog-to-digital converters (ADCs), low-noise amplifiers (LNAs), phase-locked loops (PLLs), wide-band (WB) paths, narrow-band (NB) paths,etc.) An RF chain can be implemented by the UE as a sequence of particular hardware components each selected from multiple (or shared) instances of each hardware component of the RF chain. For example, a UE may have multiple choices for RF tuning for a given CA band combination (e.g., inter-band or intra-band with multiple SCCs).

[0136] The TRM device allocation can be an RF device allocation performed by the TRM of the UE, and may be used to allocate the discrete RF hardware components of the UE to a particular SCC or PCC Rx / Tx chain. For example, the UE may implement a respective RF chain for each SCC of the one or more SCCs of the CA configuration, and may implement a respective RF chain for the PCC of the C A configuration. In some cases, the Rx / Tx for a particular SCC and / or for the PCC can be isolated to a corresponding RF antenna of a plurality of RF antennas of the UE. For example, the UE may allocate a respective RF chain (e.g., terminating in a corresponding RF antenna) for the PCC and for each SCC of the CA configuration. The UE may additionally allocate the respective PCC and SCC RF chains such that the RF chains do not share any RF path downstream (e.g., LNA, PLL, WB paths, NB paths, etc.) for analog and digital RF processing.

[0137] After the OTA handling 610 processing and the TRM RF device allocation blocks are completed (e.g., by the end of subframe 7, before the start of subframe 8), the CA tuning timeline 600 can proceed to RF script building blocks 620 and 630. For example, in some aspects, the RF configuration check block 620 and the RF hardware register script building block 630 can correspond to RF script building (e.g., determining RF hardware register configurations) performed by the UE (e.g., block 620 and block 630 can be included in an RF split script building process of the UE).

[0138] The RF script building can be performed based on RF device allocation information determined by the TRM of the UE during the OTA handling 610, where the RF device allocation information corresponds to a determination of the respective RF paths for each SCC and PCC Rx / Tx chain of the updated CA configuration. In one illustrative example, the RF script building blocks 620 and / or 630 can be used to generate or obtain an RF hardware register script that is indicative of RF hardware register values for implementing an SCC or PCC Rx / Tx chain (e.g., an SCC or PCC RF chain) in the configurable RFFE, modem, TRM, antennas, and / or other RF hardware of the UE.

[0139] For example, an RF script can be indicative of a set of settings (e.g., hardware register values) on the RF hardware of the UE for implementing a particular RF pathcorresponding to a PCC or SCC RF chain. For example, an RF script can include a listing of hardware register settings that need to be programmed into the RF hardware of the UE in order to implement the particular RF path and RF chain for the PCC or SCC of the CA configuration. In some aspects, an RF script can be provided as a mapping between high- level settings indicative of configuration parameters for a carrier (e.g., PCC or SCC, the particular channel, bandwidth, power level, timing and synchronization, etc.) and the corresponding low-level RF hardware register values for implementing the high-level setting(s).

[0140] In the example CA tuning timeline 600 of FIG. 6, the RF script building (e g., determining RF hardware register configurations) has not been completed by the CA tuning window 602 end time 654 (e.g., between subframes 20 and 21, 20ms after the tuning window start time 652). For example, the RF script building block 630 is completed after subframe 22, 2ms after the CA tuning window 602 end time 654.

[0141] After RF script building (e.g., after determining RF hardware register configurations), the UE performs RF script execution to configure the PCC and / or SCC chains of the updated CA configuration in the RF hardware of the UE. In many examples, RF scripts execution may include the UE causing interruptions for one or more subframes (e.g., Rx / Tx blanking) on the PCC and / or on one or more existing SCCs (e.g., SCCs that are not newly added in the updated CA configuration). During interruptions of a particular carrier (e.g., PCC or SCC), the UE is configured to not receive or transmit on the particular carrier. For example, after completion of the RF script building corresponding to blocks 620 and 630, the CA tuning timeline 600 includes a subsequent RF script execution block 640, where the RF scripts built (e.g., generated) during blocks 620 and / or 630 are executed by the UE firmware to implement the PCC and / or SCC RF paths and Rx / Tx chains for the updated CA configuration in the hardware registers of the UE RF hardware components, RF front-ends (RFFEs), etc. For example, the RF script building blocks 620 and 630 can be used to determine the respective RF hardware register values for each SCC and PCC Rx / Tx chain that is to be implemented for the updated CA configuration. The RF script execution block 640 can be used to update or otherwise write the determined values of the RF scripts into the physical RF hardware registers of the UE.

[0142] In some aspects, the RF script execution block 640 can include one or more subframes of downlink interruption (e.g., Rx blanking) 642 of the PCC for one or moresubframes and / or can include one or more subframes of uplink intermption (e.g., Tx blanking) 646 of the PCC for one or more subframes. For example, the downlink interruption 642 occurs for subframes 29 and 30, and the UE does not perform downlink reception on any interrupted carriers during subframes 29 and 30. The uplink interruption 646 occurs for subframes 29 and 30, and may correspond to discontinuous transmission (DTX) being enabled such that the UE does not perform uplink transmission on any interrupted carriers during subframes 29 and 30. The downlink interruption 642 and / or uplink interruption 646 can be performed for one or more carriers (e.g., CCs) of the carrier aggregation configuration. For example, the downlink interruption 642 and / or uplink interruption 646 can be performed for the PCC of the updated CA configuration, can be performed for one or more SCCs of the updated CA configuration, or can be performed for a combination of one or more of the PCC and one or more SCCs of the updated CA configuration.

[0143] The downlink interruption 642 and uplink interruption 646 can be performed for (e.g., applied to) the PCC and the one or more SCCs of the updated CA configuration being implemented during the CA tuning timeline 600. Rx and / or uplink interruption may be performed during the tuning step for earner addition (PCC or SCC addition) to the carrier aggregation configuration of the UE, and / or may be performed during the tuning step for updating or reconfiguring a CC previously used by the UE for carrier aggregation. For example, the UE may be configured to cause interruptions for uplink and downlink on the PCC and the SCCs in order to complete the configuration for the new RF devices being added by the updated CA configuration.

[0144] As noted previously, the example C A tuning timeline 600 of FIG. 6 corresponds to a total processing time 604 that exceeds the CA tuning window limit 602 by a window exceeded time 606. For instance, the end-to-end RRC reconfiguration C A tune of timeline 600 is completed in 32.3ms, which far exceeds the 20ms DL RRC processing time limit for C A tuning and reconfiguration at the UE. For example, the RF script building block 630 has not completed by the CA tuning window 602 end time 654 (e.g., between subframes 20 and 21, 20ms after the tuning window start time 652), and is not completed until after subframe 22, 2ms after the CA tuning window 602 end time 654.

[0145] The longer total C A tune timeline 604 and corresponding window exceeded time 606, in combination with the downlink interruption 642 and uplink interruption 646, canbe associated with performance degradation at the UE when implementing the updated CA configuration and Ca tuning process 600.

[0146] For example, based on still performing the remaining processing for the RRC reconfiguration CA tune during the window exceeded time 606, the UE may miss key DL / UL grants from the network entity that are transmitted by the network entity during the downlink interruption 642 on subframes 29-30. The UE may miss scheduled or expected uplink transmissions to the network entity during the uplink interruption 646 on subframes 29-30. In one illustrative example, within the CA tuning timeline 600 of FIG. 6, the UE misses the reception of an SCC activation MAC-CE 662 from the network entity, as the SCC activation MAC-CE 662 is within the 2ms downlink interruption 642 for PCC during RF scripts execution 640. In some cases, the UE may experience performance issues associated with DL / UL block error rate (BLER) and missed decodes during the window exceeded time 606 and / or within the 2ms downlink interruption 642 or 2ms uplink interruption 646 (e.g., delayed or missed SCCs activation, in the example of FIG. 6 and the SCC activation MAC-CE 662).

[0147] As noted previously, systems and techniques are described herein that can be used to provide optimized multi-carrier aggregation configuration and / or reconfiguration for carrier aggregation implemented by a UE or other network device.

[0148] In some aspects, the UE or network device can be configured to implement an updated CA configuration based on prioritizing processing for the PCC of the updated CA configuration ahead of processing for one or more SCCs of the updated CA configuration. For example, the RF tuning of blocks 620 and 630 of the CA tuning timeline 600 of FIG. 6 can be split into multiple steps, where each step is configured to prioritize processing for the PCC Rx and Tx chains and the corresponding RF tuning thereof. For example, the RF tuning blocks 620 and 630 of FIG. 6 may correspond to combined RF tuning, where the PCC and SCCs are not tuned in a particular sequential order (e.g., the PCC and SCCs may be tuned in a combined RF tuning that is not sequential on a per CC or earner basis).

[0149] FIG. 7 is a diagram illustrating an example of multi-carrier aggregation 700 corresponding to a PCC 712, a first SCC1 715, and a second SCC2 717 associated with an RF transceiver 740 that may be included in a UE or network device. In one illustrative example, PCC 712 may be an inter-band carrier that does not share a common RF modulewith either of SCC1 715 or SCC2 717. SCC1 715 and SCC2 717 may be configured in intra-band contiguous CA with shared RF modules between the aggregated SCC1 and SCC2. but not shared with the PCC 712.

[0150] For example, the PCC 712 can be associated with a PCC RF path (e.g., the RF hardware components of the UE and / or RF transceiver 740 for implementing a PCC Rx / TX chain) that includes a dedicated antenna for the PCC 712, a first set of switches 722-1, a first external low-noise amplifier (eLNA) 724-1, a first internal low-noise amplifier (iLNA) 734-1, a first phase-locked loop (PLL) 736-1, a first analog-to-digital converted (ADC) 738-1, etc., configured to output from the PCC RF path a set of PCC narrow-band (NB) samples 742 corresponding to the PCC 712.

[0151] SCC1 715 and SCC2 717, as intra-band contiguous CA SCCs, may share RF modules with one another. For example, the aggregated SCC RF path can include a dedicated antenna for the SCCs, a second set of switches 722-2, a second eLNA 724-2, a second iLNA 734-2, a second PLL 736-2, a second ADC 738-2, and a rotator to split the RF path into the respective SCC1 narrow-band (NB) samples 745 corresponding to SCC1 715 and SCC2 NB samples 747 corresponding to SCC2 717.

[0152] In one illustrative example, the PCC 712 and corresponding PCC RF chain can be tuned first, and may be prioritized over the tuning of the SCC1 715 and SCC2 717 on the shared SCC RF chain. For example, based at least in part on the PCC 712 and SCCs 715, 717 not sharing RF modules or components (e.g., based at least in part on the configuration of separate PCC and SCC RF paths in the RF transceiver 740), the UE including the RF transceiver 740 can implement optimized CA tuning to tune the PCC 712 first and to subsequently tune the SCCs 715, 717 later (e.g., after completing the PCC 712 tune) without impact to the PCC 712.

[0153] FIG. 8 is a diagram illustrating example C A tune timelines 800 for implementing an updated CA configuration for a UE or network device. A first CA tune timeline 802 can be the same as or similar to the CA tune timeline 600 of FIG. 6, and completes the CA tune for the updated CA configuration after subframe 25 (e.g., 25ms after the RRF reconfiguration request for multi-CA addition 852, which is indicative of the updated CA configuration). The completion of the CA tune by the first CA tune timeline 802 can correspond to a first RRC reconfiguration complete indication 892, which may indicateto the network entity that the UE has completed the RRC reconfiguration CA tune for the PCC and SCCs.

[0154] A second CAtune timeline 850 can be an optimized CAtune timeline configured to prioritize processing for the PCC ahead of processing for the one or more SCCs. For example, the second CA tune timeline 850 completes the CA tune for the same updated CA configuration after subframe 22, and completes the CA tune for the PCC after subframe 17 (e.g., Ums after the RRC reconfiguration request for multi-CA addition 852). In some aspects, the second (e.g., optimized) CA tune timeline 850 completes the CA tune for the PCC, and transmits a corresponding RRC reconfiguration complete indication 890, within the configured processing time limit 854 for the tuning window (e.g., completes the CAtune for the PCC and transmits the RRC reconfiguration complete 890 after Ums, which is within the 20ms tuning window processing time limit).

[0155] In some aspects, the first CAtune timeline 802 and the second CAtune timeline 850 can correspond to CA tuning to implement an updated CA configuration that transitions the UE from using a PCC only (e.g., PCC 712 of FIG. 7) to using the PCC and two additional SCCs, SCC1 and SCC2 (e.g., SCC1 715 and SCC2 717 of FIG. 7). The CA tuning in this example can correspond to transition the UE from implementing 4 Rx and Tx chains (e.g., corresponding to the PCC only configuration) to the UE implementing 12 Rx and Tx chains (e.g., corresponding to the PCC+2SCCs multi-carrier CA configuration).

[0156] In some aspects, the first CA tune timeline 802 can be the same as or similar to the CA tune timeline 600 of FIG. 6. For example, the plurality of subframes 805 can be the same as or similar to the plurality of 1ms subframes 605 of FIG. 6. An OTA handling block 810 can be the same as or similar to the OTA handling block 610 of FIG. 6. An RF resource allocation and impacts computation block 820 may be the same as or similar to the RF CHECK CONFIG REQ / CNF block 620 of FIG. 6. In some examples, the processing blocks 810 and 820 of FIG. 8 can be the same for the first CA tune timeline 802 and the second CAtune timeline 850. The first CAtune timeline 802 can additionally include RF hardware register script building block 830, configured to perform RF hardware register script building for the combination of the PCC and SCCs of the updated CA configuration (e.g., such as the PCC 712, SCC1 715 and SCC2 717 of FIG. 7, etc.). In some aspects, the RF hardware register script building block 830 can be the same as orsimilar to the RF script building block 630 of FIG. 6. At block 840, the first CA tune timeline 802 performs retuning of all carriers (e.g., retuning of the PCC, SCC1, SCC2) and completes CA tune processing with the corresponding first RRC reconfiguration complete indication 892. In some aspects, block 840 of the first CAtune timeline 802 can be the same as or similar to the RF script execution block 640 of the CA tune timeline 600 of FIG. 6.

[0157] The second CAtune timeline 850 of FIG. 8 can be an optimized CAtune based on prioritizing processing for the PCC ahead of the SCCs, as noted above. For example, after completing the RF resource allocation and impacts computation block 820 at subframe 8, the second (e.g., optimized, PCC-prioritized, etc.) CAtune timeline 850 can perform PCC-only RF hardware register script building block 862 between subframes 9- 13. At subframe 14, the RF script for the PCC (e.g., PCC 712 of FIG. 7, etc.) is complete.

[0158] Beginning from subframe 14, the second CA tune timeline 850 can implement a PCC-only retune block 872, to perform RF tuning (e.g., retune) for the PCC based on the PCC RF script generated at PCC RF script building block 862.

[0159] In parallel with the PCC retune 872, the second CA tune timeline 850 can additionally perform SCC-only RF hardware register script building 864 to build a respective first SCC RF script for SCC1 (e.g., SCC1 715 of FIG. 7) and a respective second SCC RF script for SCC2 (e.g., SCC2 717 of FIG. 7).

[0160] At subframe 17, the second CA tune timeline 850 completes the PCC retune 872, and the UE is able to transmit and receive on the PCC of the updated CA configuration from subframe 18 onwards. Because the PCC retune 872 completes within (e.g., before) the tuning window limit 854, the UE does not miss DL / UL grants from the network entity (e.g., which are over the PCC) and does not miss transmissions to the network entity (e.g., which may also be over the PCC).

[0161] In one illustrative example, the second CA tune timeline can include an RRC reconfiguration complete indication 890 that is transmitted by the UE to the network entity to indicate that the PCC retune 872 has been completed, and that the UE is ready and able to perform reception and transmission on the tuned PCC of the updated CA configuration indicated in the RRC reconfiguration request 852 received prior to subframe 1.

[0162] In the second CA tune timeline 850, the SCC-only RF script building 864 may extend processing beyond the time of the RRC reconfiguration complete indication 890. The total bandwidth available to the UE may be relatively lower while SCC tuning is in progress or not yet completed, but the UE is able to fully communicate on Rx and Tx with the network entity using the PCC. Based on the PCC retune 872 being prioritized to complete within the tuning window limit 854, the UE performance is not impacted and / or is relatively less impacted when the completion of the SCC tune and overall second CA tune timeline 850 extend past the tuning window time limit 854.

[0163] For example, after the SCC-only RF script building 864 is completed, the second CA tune timeline 850 performs SCC-only retuning 874 to retune SCC1 (e.g., SCC1 715 of FIG. 7) and to retune SCC2 (e.g., SCC2 717 of FIG. 7) using respective SCC1 and SCC2 RF scripts generated at the SCC-only RF script building block 864. In some examples, the SCC retuning 874 may be completed at or within the 20ms tuning window limit 854. In some cases, the SCC retuning 874 may extend past the tuning window limit 854, during which time the UE may communicate on the PCC only (e.g., based on the PCC retune 872 completing at the RRC reconfiguration complete time 890, within the tuning window limit 854). In some aspects, the second CAtune timeline 850 can perform the SCC retuning 874 in parallel with RF low-power mode and dynamic activity script building 868, which may extend to a completion time that is one or more subframes 805 beyond the 20ms tuning window limit 854 without impact to the UE communications performance on the PCC.

[0164] In some cases, the optimized second CA tune timeline 850 of FIG. 8 can be implemented based on splitting RF script building and tuning into three steps, which may be performed after the UE TRM / RF completes the RF device allocation block 820 and RF scripts can be built (e.g., based on the RF device allocation information from the TRM).

[0165] A first phase can correspond to the PCC PRx / Tx script build of PCC-only RF script building block 862 and the PCC retune block 872. If interruption (e.g., Rx / Tx blanking) of one or more subframes is required during the PCC retune 872 (e.g., PCC interruption of one or more subframes at the beginning of reconfiguration), the UE performance is not impacted for communications with the network entity, based on thePCC retune 872 and any PCC interruptions being performed within the configured tuning window 20ms time limit 854.

[0166] A second phase can correspond to perform the RF script building and execution for the remaining RF chains of the updated CA configuration (e.g., SCC Rx / Tx script building block 864 and SCC retuning block 874). In some cases, the second phase can correspond to script building and execution for the rest of the RF chains of the updated CA configuration (e.g., other than the PCC PRx / Tx chain processed in the first phase), which may be performed across the PCC and SCCs.

[0167] A third phase can correspond to RF script building for power features (e g., sleep / wakeup, LPM, etc.), and may be implemented as the RF low-power mode and dynamic activity script building block 868 of the second C A tune timeline 850. The third phase can include RF script building for power features, and / or one or more dynamic activity or advanced features such as LPM, APM, MIMO, Sleep / Wakeup, etc., that are able to be performed and processed in parallel with the PCC and / or SCC RF tune.

[0168] In some aspects, the systems and techniques can be configured to provide optimized multi-carrier aggregation configuration and / or reconfiguration for earner aggregation implemented by a UE or other network device, based on minimizing PCC disruption during RF device allocation and RF scripts execution for the CA tune. For example, in some cases, the UE can be configured to minimize disruption to the PCC during RF device allocation and RF scripts execution associated with implementing the updated CA configuration. In one illustrative example, for blind SCC addition, the UE can implement an RF device allocation algorithm (e.g., corresponding to the RF resource or device allocation block 820 of FIG. 8, etc.) that is configured to first attempt to determine an RF device allocation where the PCC uplink and downlink are not interrupted (e.g., blanked) for one or more subframes for the target allocation. If the UE is unable to perform allocation to avoid PCC interruption, the UE may next attempt to perform allocation to assign the PCC PRx / Tx chain to a non-shared antenna (e.g., a dedicated antenna for the PCC PRx / Tx chain). For example, the PCC 712 of FIG. 7 is allocated to a different antenna of the RF transceiver 740 than the antenna allocated to the SCC1 715 and SCC2 717 of FIG. 7. In some examples, if the UE is unable to perform RF device allocation to assign a non-shared antenna to the PCC PRx / Tx, the UE can fallback to performing a legacy allocation algorithm to assign RF devices. After completing the RFdevice allocation to minimize disruption to the PCC, the UE may continue the CA tune process using the optimized CA tuning techniques described above to prioritize processing of the PCC ahead of the SCCs.

[0169] In another illustrative example, a UE may include an RF card, RF transceiver, RFFE, etc., that is configured to provide support for unified Sub-6 frequency bands (e g., FR1 bands of 5G NR) and mmW frequency bands (e.g., FR2 bands of 5G NR). For example, an RF card of the UE may support unified Sub-6+mmW RFFE implementations, where a unified Sub-6+mmW path can be configured as a Sub-6 path, as a mmW path, etc. For example, UE RF cards may be configured to reserve a subset of a plurality of total available RF paths for 5G mmW CCs, with RF device allocation performed separately for mmW CCs and Sub-6 and / or LTE CCs. In some aspects, where the UE RF card supports unified Sub-6+mmW RF paths, each RF path can be configured for a mmW CC or Sub-6 / LTE CCs. The UE may be configured to reserve a subset of RF paths for mmW CCs, including in examples where the UE supports unified Sub-6+mmW RF paths. In some cases, the reserved subset of unified Sub-6+mmW paths may sit unused during Sub-6+LTE and / or LTE-only calls by the UE. In one illustrative example, the systems and techniques can be configured to perform CA tuning to allocate PCC Rx / Tx chains to the unused, reserved paths during device allocation when the UE supports unified Sub-6+mmW RF paths and determines that there are no mmW CCs configured. After completing the device allocation with PCC Rx / Tx chains allocated to the reserved mmW paths, the UE may continue the C A tune process using the optimized CA tuning techniques described above to prioritize processing of the PCC ahead of the SCCs.

[0170] In some aspects, the UE can be configured to reduce an amount of time associated with performing the RF hardware register script building, based on the UE determining one or more predicted updated CA configurations prior to receiving the RRC reconfiguration from the network entity indicative of an updated C A configuration for the UE. For example, the UE can determine predicted updated CA configurations using measurement information associated with one or more neighboring cells of the UE. The measurement information can be previously obtained measurement information obtained by the UE in response to a measurement requested and / or configured by the network entity.

[0171] A UE may often receive a network request (e. g. , a request from a network entity) to perform one or more measurements of neighboring cells of the UE. For example, a UE can be configured by a network entity (e.g., gNB, base station, etc.) to obtain one or more measurements of one or more neighboring cells, and to report the measurement information in a measurement report, CSI report, etc., transmitted from the UE to the network entity .

[0172] In some examples, the network entity may receive the UE measurement report corresponding to measurements of one or more neighboring cells of the UE, and the network entity may subsequently add the best cells from the measurement report as SCCs for carrier aggregation at the UE. For instance, the network entity can request a measurement report from the UE in anticipation of a handover or mobility event. The UE can obtain the configured measurements of one or more neighboring cells associated with the UE, and can transmit the measurement report to the network entity. The network entity may analyze the measurement report to identify or determine one or more neighbonng cells not currently included in a CA configuration for the UE for addition to an updated CA configuration for the UE. The network entity can transmit an RRC reconfiguration request to the UE indicative of the updated CA configuration that includes the best measured neighboring cell from the measurement report as a new SCC and / or a new PCC for the UE’s carrier aggregation.

[0173] In one illustrative example, for measurements configured by a network entity; the UE can be configured to pre-build RF scripts for the active set of neighboring cells (e.g., where the active set of neighboring cells includes the neighboring cells that are configured for carrier aggregation performed by the UE). The pre-built RF scripts can be stored locally at the UE, for example in a memory or storage element included in the UE.

[0174] A predicted updated CA configurations determined by the UE can include one or more of a predicted PCC or a predicted SCC for the carrier aggregation implemented at the UE. The predicted PCC or predicted SCC can be based on corresponding measurements of a neighboring cell. For example, the predicted PCC or predicted SCC can correspond to a best or strongest cell of a plurality of neighboring cells previously measured by the UE (e.g., based on the UE predicting that the best or strongest cell indicated in the UE measurement report to the network entity will later be configured as a new PCC or SCC of an updated C A configuration for the UE). In some aspects, the UEcan be configured to pre-build a corresponding RF hardware register script for each predicted PCC and / or predicted SCC included in a respective predicted updated CA configuration determined by the UE. In some cases, the pre-built RF script for the predicted PCC or predicted SCC can be obtained as the RF hardware register values used by the UE to obtain or perform the measurements of the neighboring cell corresponding to the predicted PCC or predicted SCC. For example, rather than clearing the RF hardware register configuration after completing the measurement, the UE can save or store the RF hardware register configuration for the neighboring cell as the pre-built RF script for a predicted PCC or predicted SCC corresponding to the neighboring cell. Based on receiving an RRC reconfiguration request indicative of an updated CA configuration for the UE, the UE can compare an updated PCC and / or one or more updated SCCs of the updated C A configuration to the corresponding predicted PCCs and SCCs of the pre-built RF scripts generated and stored by the UE. In some cases, the UE can determine whether any of the SCCs indicated in the updated CA configuration for the UE are previously measured neighbors for which a pre-built RF script is available. Based on determining that an added SCC of the updated CA configuration is a previously measured neighbor, the UE can obtain the corresponding pre-built RF script for the neighbor and may execute the pre-built RF script without performing RF device allocation, scouting, or RF script building for the added SCC of the updated CA configuration.

[0175] Based on receiving an RRC reconfiguration request indicative of an updated CA configuration from a network entity, the UE can check the updated CA configuration to determine whether any of the SCCs indicated by the updated CA configuration are previously measured neighboring cells. For instance, the UE can determine whether each SCC of one or more SCCs included in the updated CA configuration are carriers that correspond to a previously measured neighboring cell.

[0176] In response to determining that the updated CA configuration includes an SCC that corresponds to a previously measured neighboring cell, the UE can obtain from memory the corresponding pre-built RF script for the previously measured neighboring cell and may use (e.g., execute) the pre-built RF script to configure the SCC Rx / Tx chain for the particular SCC. In one illustrative example, the UE can reduce the total processing time for CA tuning to implement the updated CA configuration by utilizing the pre-built RF scripts to implement SCC Rx / Tx paths for the any SCCs that correspond to previously measured neighboring cells. After identifying one or more pre-built RF scripts that matchto respective SCCs included in the updated CA configuration, the UE can run the RF device allocation algorithm again to allocate the non-matching SCCs and / or the PCC of the updated CA configuration. The respective SCCs for which a neighboring cell was previously measured, and a pre-built RF script was generated and stored, do not require RF device allocation and can instead utilize the corresponding pre-built RF script for CA tuning.

[0177] In some aspects, the UE can be configured to reduce an amount of time associated with performing the RF hardware register script building, based on the UE determining one or more predicted updated CA configurations prior to receiving the RRC reconfiguration from the network entity indicative of an updated C A configuration for the UE. For example, the UE can determine predicted updated CA configurations using measurement information associated with one or more neighboring cells of the UE, as noted above. In some aspects, the predicted updated CA configuration comprises one predicted updated CA configuration, where the UE predicts an updated active set of neighboring cells that will be configured by the network entity in response to the network entity receiving the UE measurement report of its neighboring cells. For example, the UE may measure three neighboring cells, and can determine the predicted updated CA configuration as an updated active set of neighboring cells that includes the best (e g., strongest) one of the three neighboring cells as reported to the network entity within the UE measurement report. If the network entity subsequently updates the UE CA configuration to add the best one of the three neighboring cells as an additional SCC for CA, the UE can use the pre-built RF scripts of the predicted updated CA configuration to perform the C A tune in a reduced amount of time.

[0178] In another illustrative example, the UE may generate and / or determine one or more and / or a plurality of predicted updated CA configurations, based on measurements of neighboring cells of the UE. For example, the UE can generate the plurality of predicted updated CA configurations to correspond to a plurality of potential CA configurations using different combinations of the measured neighboring cells.

[0179] For example, a UE may currently be associated with a Band A serving cell, and may measure a set of neighboring cells that includes at least a Band B and a Band C neighboring cell. A first predicted CA configuration may correspond to Band A (PCell) +Band B (SCell-1). A second predicted CA configuration may correspond to Band A (PCell) + Band C(SCell-l), etc.

[0180] Where multiple CA configurations are possible for the UE, based on different selections from the set of neighboring cells measured by the UE, the optimal path selection for RF device allocation and / or RF script building during CA tuning can be different for each possible CA configuration of the multiple possible CA configurations. In some cases, the total number of Rx / Tx chains of the CA configuration may additionally impact the optimal path selection during RF device allocation and / or RF script building.

[0181] In one illustrative example, the UE can be configured to implement prediction to determine a potential set of possible carriers that can be configured by the network for the UE’s multi-carrier CA configuration.

[0182] In some aspects, the UE can be configured to maintain a predicted set of PCell+SCells CA configurations (e.g., a set of predicted updated CA configurations), where each configuration corresponds to a different combination of PCell and SCells selected from earners and cells measured by the UE. The predicted set of PCell+SCells configurations may also be referred to as the predicted_CA_set. The UE can be configured to maintain the predicted_CA_set for any given moment in time, for example based on updating the predicted_CA_set in response to measurements and / or measurement reports determine at the UE, etc.

[0183] In one illustrative example, the UE can be configured to measure one or more neighboring cells (e.g., based on a measurement request from a network entity) and determine whether the corresponding measurement report for the measurements of the one or more neighboring cells includes a configured type of measurement event. For example, if a measurement report with a first type of configured measurement event is reported by the UE, the UE can add the neighboring cell corresponding to the occurrence of the measurement event to the predicted_CA_set. If a measurement report with a second type of configured measurement event is reported by the UE, the UE can remove the neighboring cell corresponding to the occurrence of the second type of measurement event from the predicted_CA_set.

[0184] In some aspects, the measurement event can be an RRM measurement event or other measurement event configured by the network and / or defined by the cellular communications standard or specification. In some cases, the measurement event can bea configured measurement event associated with one or more of a measurement type and / or one or more threshold values. In some aspects, the measurement event can be a measurement event associated with carrier aggregation and / or can be a measurement event associated with NR-triggered mobility.

[0185] Measurement events can be pre-defined events and / or configured events associated with a wireless network, network entities, and / or network devices thereof. For example, 5G NR utilizes measurement events A1-A6 corresponding to NR triggered mobility (e.g., NR to NR), which may be used to trigger a UE to add or remove an NR PSCell, to add or remove an NR SCell, etc. The Al measurement event occurs when the serving cell becomes better than an absolute threshold. The A2 measurement event occurs when the serving cell becomes worse than an absolute threshold. The A3 measurement event occurs when a neighbor cell becomes offset better than PCell / PSCell. The A4 measurement event occurs when a neighbor cell becomes better than an absolute threshold. The A5 measurement event occurs when a PCell / PSCell becomes worse than an absolute thresholdl and a neighbor cell becomes better than an absolute threshold2. The A6 measurement event occurs when a neighbor cells becomes offset by an amount better than the SCell. A set of measurement events B1-B2 can correspond to inter-RAT mobility (e.g., NR to LTE). The Bl measurement event can occur when a neighbor cell becomes better than an absolute threshold. The B2 measurement event can occur when a PCell becomes worse than an absolute threshold 1 and a neighbor cell becomes better than another absolute threshold2, etc.

[0186] In some aspects, a UE can determine that a configured measurement event (e.g., a configured RRM measurement event, etc.) has occurred, based on one or more measurements determined by or otherwise obtained by the UE. Based on determining the occurrence of the configured measurement event, the UE can update the predicted_CA_set (e.g., the UE can update the plurality of predicted updated CA configurations) to add or remove the corresponding neighboring cell that was measured and triggered the occurrence of the configured measurement event.

[0187] In one illustrative example, the UE can determine the occurrence of an Al measurement event (serving cell becomes better than a threshold), an A3 measurement event (neighbor cell becomes offset better than serving cell), an A4 measurement event (neighbor cell becomes better than serving cell), or an A6 measurement event (neighborcell becomes offset better than SCell) corresponding to a particular neighboring cell measured by the UE. Based on determining the occurrence of the Al, A3, A4, or A6 measurement event corresponding to measurements of the particular neighboring cell, the UE can update the predicted_CA_set to add the particular neighboring cell to the predicted_CA_set. For example, the UE can add to the predicted_CA_set an additional predicted updated C A configuration with the particular neighboring cell as a PCC or SCC.

[0188] In some aspects, based on determining the occurrence of an A2 measurement event (e.g., serving cell becomes worse than a threshold) or an A5 measurement event (e.g., serving cell becomes worse than thresholdl and neighbor cell becomes better than threshold2) corresponding to measurements of a particular neighboring cell, the UE can update the predicted_CA_set to remove the particular neighboring cell from the predicted_CA_set. For example, the UE can remove from the predicted_CA_set one or more predicted updated CA configurations that include the particular neighboring cell as either PCC or SCC.

[0189] In some aspects, the UE can be configured to perform or trigger re-evaluation for RF script pre-building in response to updating the predicted CA set. For example, whenever the UE updates the predicted_C A_set to add or remove a particular neighboring cell to or from the predicted_CA_set (respectively), the UE can determine whether RF script pre-building needs to be performed. For example, the addition of a neighboring cell to the predicted_CA_set can trigger RF script pre-building to generate a pre-built RF script for the added neighboring cell as an additional SCC and / or as an updated PCC for the CA configuration, etc. The removal of a neighboring cell from the predicted_CA_set can trigger RF script pre-building to update one or more stored pre-built RF scripts to no longer include the removed neighboring cell as PCC or SCC, etc.

[0190] In some examples, the UE can be configured to compare the predicted_CA_set against a UE-reported carrier aggregation combination in an RRC UE capability report. The UE may further be configured to adjust the predicted_CA_set as the network entity is not able to add any other aggregation combinations (e.g., CA combinations) other than the one(s) reported by the UE in the RRC UE capability report.

[0191] In one illustrative example, the UE can subsequently use the updated and adjusted predicted_CA_set to perform RF script pre-building, such that the UE obtains and stores a corresponding pre-built RF script for each aggregation combination (e.g.,each predicted updated CA configuration) represented within the predicted_CA_set. The UE can use the stored pre-built RF scripts for the predicted_CA_set for RF scripts execution during the CA tuning process based on receiving an RRC connection reconfiguration with a corresponding carrier aggregation addition, deletion, modification, and / or handover cell change. By performing RF script building as RF script pre-building in a non-critical path, the UE can reduce the total processing time for the CA tuning timeline that is triggered at the UE in response to the RRC reconfiguration indicative of the updated CA configuration for the UE. For example, when the network entity transmits to the UE an RRC connection reconfiguration with carrier aggregation addition, deletion, modification, etc., the UE has already generated a pre-built RF script for all possibilities of the different aggregation combinations that may be selected by the network entity (e g., based on the network entity selecting the aggregation combinations based on the measurement reports transmitted by the UE). Based on generating and storing a pre-built RF script for all possible aggregation combinations represented within the predicted_CA_set, the UE can guarantee the availability of a matching pre-built RF script for the PCC and SCCs of the various updated CA configurations that the UE may receive from the network, and can perform CA tuning by proceeding directly to RF script execution to run (e.g., execute) the matching pre-built RF scripts.

[0192] FIG. 9 is a flowchart diagram illustrating an example of a process 900 for wireless communications. In some aspects, the process 900 can be a process for wireless communications by a network device (e.g., a UE, etc.). For example, the process 900 can be a process for wireless communications by a UE. In some examples, the process 900 can be performed by a network device or apparatus or a component or system (e.g., one or more chipsets, one or more processors such as one or more CPUs, DSPs, NPUs, NSPs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gates or transistor logic components, discrete hardware components, etc., any combination thereof, and / or other component or system) of the network device or apparatus. The operations of the process 900 may be implemented as software components that are executed and run on one or more processors (e.g., processor 1010 of FIG. 10 or other processor(s)). In some examples, the process 900 can be performed by a UE, including any of the UEs of FIGS. 1-8. In some aspects, the process 900 can be performed by a UE, smartphone, mobile computing device, user computer device, etc. The process 900 can be performed by a component or system (e.g., a chipset) of a network device (e.g., one or more of UEs 104,152, 164, 182, 190 of FIG. 1; UE 104 of FIG. 2; UE(s) 104 of FIG. 3; wireless device 407 of FIG. 4; computing system 1000 of FIG. 10; etc.). The network device may be a mobile device (e.g., a mobile phone), a network-connected wearable such as a watch, an extended reality (XR) device such as a virtual reality (VR) device or augmented reality (AR) device, a vehicle or component or system of a vehicle, or other type of computing device. The operations of the process 900 may be implemented as software components that are executed and run on one or more processors (e.g., processor 484 of FIG. 4, processor 1010 of FIG. 10, and / or other processor(s)). Further, the transmission and reception of signals by the wireless device in the process 1000 may be enabled, for example, by one or more antennas (e g., antennas 252 of FIG. 2, antenna 487 of FIG. 4, etc.) and / or one or more transceivers (e.g., wireless trans ceiver(s) 478 of FIG. 4, etc.).

[0193] At block 902, the network device (or component thereof) can receive information indicative of a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs). For example, the network device can be a UE and can receive the information indicative of the first CA configuration from a network entity (e.g., base station, gNB, etc.). In some cases, the first CA configuration can correspond to a PCC the same as or similar to the PCC 712 of FIG. 7, and / or can correspond to one or more SCCs the same as or similar to one or more of the first SCC 715 and / or the second SCC 717 of FIG. 7, etc.

[0194] At block 904, the network device (or component thereof) can determine a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells. For example, the measurement information can be associated with measurements based on one or more of the downlink reference signals between the base station 102 and the UE 104 of FIG. 5, etc.

[0195] In some cases, the measurement information associated with the one or more neighboring cells can correspond to a measurement report associated with measurements of the one or more neighboring cells by the network device. For example, the network device (e.g., UE) can determine the predicted updated CA configuration usingmeasurement information associated with and / or included within and / or corresponding to a measurement report generated by the UE. The UE can transmit the measurement report to a base station, which may be the same as a base station from which the UE receives the information indicative of the first CA configuration for the UE.

[0196] In some examples, the network device (e.g., UE) can be configured to receive one or more measurement objects corresponding to the one or more neighboring cells, and to obtain the measurements of the one or more neighboring cells based on the one or more measurement objects. For example, the UE can receive the one or more measurement objects from the base station from which the UE receives the information indicative of the first CA configuration for the UE.

[0197] In some cases, to determine the predicted updated CA configuration, the network device (e.g., UE) can be configured to determine, based on the measurement information, an active set of neighboring cells included in the one or more neighboring cells. The UE can generate the predicted updated C A configuration to include one or more respective predicted SCCs corresponding to the active set of neighboring cells. In some examples, the network entity (e.g., UE) can be configured to compare an updated set of SCCs included in the updated CA configuration to the one or more respective predicted SCCs. For each SCC included in the updated set of SCCs and the one or more respective predicted SCCs, the UE can perform CA tuning using a respective cached RF hardware register configuration corresponding to each SCC. For example, the RF hardware register configuration can correspond to the RF script 630 of FIG. 6, the RF hardware register script(s) 830, 862, 864, etc., of FIG. 8, etc.

[0198] At block 906, the network device (or component thereof) can determine a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell.

[0199] For example, the RF hardware register configuration can be an RF script build for implementing an RF chain of a PCC and / or one or more SCCs of a respective CA configuration. In some examples, the RF hardware register configuration can be associated with the RF hardware register configuration script building 630 of FIG. 6, the RF hardware register configuration script building 830 of FIG. 8, the PCC RF hardwareregister configuration script building 862 of FIG. 8, and / or the SCC RF hardware register configuration script building 864 of FIG. 8, etc.

[0200] In some cases, the network entity (e.g., UE) can be configured to determine a plurality of predicted updated CA configurations including the predicted updated CA configuration. The UE can be configured to determine a cached RF hardware register configuration corresponding to each respective predicted updated C A configuration of the plurality of predicted updated CA configurations. In some cases, the plurality of predicted updated CA configurations corresponds to a subset of the one or more neighboring cells, and wherein each neighboring cell of the subset is associated with an occurrence of a respective measurement event.

[0201] In some examples, the occurrence of the respective measurement event comprises an occurrence of a configured radio resource management (RRM) measurement event. In some examples, the plurality of predicted updated CA configurations can be included in a predicted CA set associated with the network device (e.g., UE), and the predicted CA set can correspond to different combinations of PCCs and SCCs for carrier aggregation by the network device.

[0202] In some cases, the network entity (e.g., UE) can be configured to determine an occurrence of a configured measurement event for a neighboring cell, and may update the predicted CA set to add an additional predicted updated CA configuration corresponding to the neighboring cell and based on the occurrence of the configured measurement event. For example, the configured measurement event associated with the UE updating the predicted CA set to add an additional predicted updated CA configuration can comprise an Al measurement event, an A3 measurement event, an A4 measurement event, or an A6 measurement event, etc.

[0203] In some examples, the network entity (e.g., UE) can be configured to determine an occurrence of a configured measurement event for a neighboring cell, and can update the predicted CA set to remove a predicted updated CA configuration corresponding to the neighboring cell, based on the occurrence of the configured measurement event. For example, the configured measurement event associated with the UE updating the predicted CA set to remove a predicted updated CA configuration can comprise one of an A2 measurement event or an A5 measurement event.

[0204] At block 908, the network device (or component thereof) can receive information indicative of an updated CA configuration for the network device, wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted see.

[0205] For example, the information indicative of the updated CA configuration can be included in a Radio Resource Control (RRC) reconfiguration request. In some examples, the information indicative of the updated CA configuration can be included in the RRC reconfiguration request 852 of FIG. 8. In some cases, receiving the information indicative of the updated CA configuration can be associated with the OTA handling 610 of FIG. 6 and / or the OTAhandlmg 810 of FIG. 8.

[0206] In some cases, the information indicative of the updated CA configuration corresponds to an addition of a component carrier (CC) to the first CA configuration, a removal of a CC from the first CA configuration, or a modification of one or more of the first PCC and the first set of SCCs of the first CA configuration. In some examples, the information indicative of the updated CA configuration corresponds to a handover of the network device (e.g., UE) from a first cell to a second cell. The first cell can be associated with the first C A configuration and the second cell can be associated with the updated CA configuration.

[0207] In some examples, the updated CA configuration includes an additional SCC not included in the first CA configuration or the predicted updated C A configuration. The network entity (e.g., UE) can be configured to determine an RF device allocation comprising a resource allocation for an additional SCC RF chain corresponding to the additional SCC, where the resource allocation for the additional SCC RF chain does not impact a currently configured resource allocation for a PCC RF chain corresponding to the first PCC. For example, the RF device allocation can be determined based on the RF resource allocation 820 of FIG. 8 and / or the RF device (e.g., resource) allocation 620 of FIG. 6.

[0208] In some cases, the network entity (e.g., UE) can be configured to implement the additional SCC RF chain without an interruption for uplink or downlink on the PCC RF chain. For example, the UE can be configured to implement the additional SCC RF chain without blanking of the PCC RF chain. In some examples, not interrupting uplink ordownlink on the PCC can be based on performing the PCC retune 872 and the SCC RF hardware register configuration script building 864 of FIG. 8 in parallel.

[0209] In some examples, the network entity (e.g., UE) can be configured to determine an updated PCC RF chain based on the resource allocation for the additional SCC RF chain, where the RF device allocation generates the updated PCC RF chain to include a non-shared antenna of the network device. For example, the resource allocation and / or RF device allocation can be the same as or similar to the RF allocation 620 of FIG. 6 and / or 820 of FIG. 8.

[0210] At block 910, the network device (or component thereof can perform CA tuning using the plurality of hardware register values of the RF hardware register configuration.

[0211] For example, the CA tuning can be performed within a configured tuning window limit, such as the configured tuning window 602 of FIG. 6 (e.g., associated with the tuning window start time 652 and the tuning window end time 654 of FIG. 6), and / or the configured tuning window of FIG. 8, associated with the tuning window start time 852 and the tuning window limit time (e.g., tuning window end time) 854 of FIG. 8, etc. In some examples, the tuning window is a 20ms RRC reconfiguration window.

[0212] In some examples, the CA tuning can be the same as or similar to the CA tuning 640 of FIG. 6. In some examples, the CA tuning can be the same as or similar to the combined PCC and SCCs tuning 840 of FIG. 8. In one illustrative example, the CA tuning can be the same as or similar to the PCC tuning (e.g., retune) 872 of FIG. 8, and / or the SCCs tuning (e.g., retuning) 874 of FIG. 8. In some examples, the network entity (e.g., UE) can be configured to perform CA tuning using the plurality of hardware register values to implement the updated CA configuration for the network device, where the network device does not cause an interruption for uplink or downlink on a PCC of the updated CA configuration.

[0213] In some cases, the network entity (e.g., UE) can be configured to determine the updated CA configuration corresponds to a PCC RF chain different from the RF chain corresponding to the predicted updated CA configuration, and may generate a PCC RF hardware register configuration corresponding to the PCC RF chain of the updated CA configuration. The network entity (e.g., UE) can implement the PCC RF chain based on the PCC RF hardware register configuration, where the PCC RF chain is implemented(e.g., PCC retune 872 of FIG. 8) before RF tuning of one or more SCCs (e.g., SCC retune 874 of FIG. 8) of the updated CA configuration.

[0214] In some examples, to implement the PCC RF chain, the network entity (e.g., UE) can be configured to perform RF tuning for the PCC RF chain based on the PCC RF hardware register configuration. The UE can generate respective SCC RF hardware register configurations corresponding to each SCC of the one or more SCCs of the updated CA configuration, where the UE performs the RF tuning for the PCC RF chain (e.g., PCC retune 872 of FIG. 8) and generates the respective SCC RF hardware register configurations (e.g., RF hardware register script building for SCC1 and SCC2 only 864 of FIG. 8) in parallel.

[0215] In some cases, the network entity (e.g., UE) can be configured to generate a respective SCC RF hardware register configuration corresponding to each SCC of the one or more SCCs of the updated CA configuration, where the respective SCC RF hardware register configuration is generated after the PCC RF chain is implemented. In some examples, the network entity (e.g., UE) can be configured to implement a respective SCC RF chain corresponding to each SCC of the one or more SCCs of the updated CA configuration, wherein the respective SCC RF chain is implemented after the PCC RF chain is implemented.

[0216] In some cases, the updated CA configuration corresponds to an updated PCC RF chain different from a first PCC RF chain corresponding to the first PCC. In some examples, an RF front end of the network device (e.g., UE) includes a plurality of combined RF paths each configurable as a frequency range 1 (FR1) RF path or a frequency range 2 (FR2) RF path. For example, the RF front end can be associated with the RF transceiver 740 of FIG. 7, the antennas of FIG. 7, etc. In some examples, the network entity (e.g., UE) can be configured to perform RF device allocation to allocate the updated PCC RF chain using a subset of the plurality of combined RF paths reserved as FR2 RF paths, based on a determination the updated CA configuration does not include one or more FR2 component carriers (CCs). In some cases, the network entity (e.g., UE) can be configured to perform CA tuning to implement the updated CA configuration without an interruption on uplink or downlink for the updated PCC RF chain, based on the allocation of the updated PCC RF chain on a reserved FR2 RF path.

[0217] In some examples, the processes described herein (e.g., process 900 and / or other process described herein) may be performed by a computing device or apparatus (e.g., a network node such as a UE, base station, a portion of a base station, etc.). For instance, as noted above, the process 900 may be performed by a UE. In another example, the process 900 may be performed by a computing device with the computing system 1000 shown in FIG. 10. For instance, a wireless communication device with the computing architecture shown in FIG. 10 may include the components of a UE and / or a network entity (e.g., base station, gNB, etc.) and may implement the operations of FIG. 9.

[0218] In some cases, the computing device or apparatus may include various components, such as one or more input devices, one or more output devices, one or more processors, one or more microprocessors, one or more microcomputers, one or more cameras, one or more sensors, and / or other component(s) that are configured to carry out the steps of processes described herein. In some examples, the computing device may include a display, one or more network interfaces configured to communicate and / or receive the data, any combination thereof, and / or other component(s). The one or more network interfaces may be configured to communicate and / or receive wired and / or wireless data, including data according to the 3G, 4G, 5G, and / or other cellular standard, data according to the WiFi (802.1 lx) standards, data according to the Bluetooth™ standard, data according to the Internet Protocol (IP) standard, and / or other types of data.

[0219] The components of the computing device may be implemented in circuitry. For example, the components may include and / or may be implemented using electronic circuits or other electronic hardware, which may include one or more programmable electronic circuits (e.g., microprocessors, graphics processing units (GPUs), digital signal processors (DSPs), central processing units (CPUs), and / or other suitable electronic circuits), and / or may include and / or be implemented using computer software, firmware, or any combination thereof, to perform the various operations described herein.

[0220] The process 900 is illustrated as a logical flow diagram, the operation of which represent a sequence of operations that may be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer- readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines,programs, objects, components, data structures, and the like that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations may be combined in any order and / or in parallel to implement the processes.

[0221] Additionally, the process 900 and / or other process described herein, may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware, or combinations thereof. As noted above, the code may be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non- transitory.

[0222] FIG. 10 is a diagram illustrating an example of a system for implementing certain aspects of the present technology. In particular, FIG. 10 illustrates an example of computing system 1000, which may be for example any computing device making up internal computing system, a remote computing system, a camera, or any component thereof in which the components of the system are in communication with each other using connection 1005. Connection 1005 may be a physical connection using a bus, or a direct connection into processor 1010, such as in a chipset architecture. Connection 1005 may also be a virtual connection, networked connection, or logical connection.

[0223] In some aspects, computing system 1000 is a distributed system in which the functions described in this disclosure may be distributed within a datacenter, multiple data centers, a peer network, etc. In some aspects, one or more of the described system components represents many such components each performing some or all of the function for which the component is described. In some aspects, the components may be physical or virtual devices.

[0224] Example system 1000 includes at least one processing unit (CPU or processor) 1010 and connection 1005 that communicatively couples various system components including system memory 1015, such as read-only memory (ROM) 1020 and random access memory (RAM) 1025 to processor 1010. Computing system 1000 may include acache 1015 of high-speed memory connected directly with, in close proximity to, or integrated as part of processor 1010.

[0225] Processor 1010 may include any general-purpose processor and a hardware service or software service, such as services 1032, 1034, and 1036 stored in storage device 1030, configured to control processor 1010 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. Processor 1010 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

[0226] To enable user interaction, computing system 1000 includes an input device 1045, which may represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc. Computing system 1000 may also include output device 1035, which may be one or more of a number of output mechanisms. In some instances, multimodal systems may enable a user to provide multiple types of input / output to communicate with computing system 1000.

[0227] Computing system 1000 may include communications interface 1040, which may generally govern and manage the user input and system output. The communication interface may perform or facilitate receipt and / or transmission wired or wireless communications using wired and / or wireless transceivers, including those making use of an audio jack / plug, a microphone jack / plug, a universal serial bus (USB) port / plug, an Apple™ Lightning™ port / plug, an Ethernet port / plug, a fiber optic port / plug, a proprietary wired port / plug, 3G, 4G, 5G and / or other cellular data network wireless signal transfer, a Bluetooth™ wireless signal transfer, a Bluetooth™ low energy (BLE) wireless signal transfer, an IBEACON™ wireless signal transfer, a radio-frequency identification (RFID) wireless signal transfer, near-field communications (NFC) wireless signal transfer, dedicated short range communication (DSRC) wireless signal transfer, 802.11 Wi-Fi wireless signal transfer, wireless local area network (WLAN) signal transfer, Visible Light Communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), Infrared (IR) communication wireless signal transfer, Public Switched Telephone Network (PSTN) signal transfer, Integrated Services Digital Network (ISDN) signal transfer, ad-hoc network signal transfer, radio wave signal transfer, microwavesignal transfer, infrared signal transfer, visible light signal transfer, ultraviolet light signal transfer, wireless signal transfer along the electromagnetic spectrum, or some combination thereof. The communications interface 1040 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers that are used to determine a location of the computing system 1000 based on receipt of one or more signals from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the US-based Global Positioning System (GPS), the Russia-based Global Navigation Satellite System (GLONASS), the China-based BeiDou Navigation Satellite System (BDS), and the Europe-based Galileo GNSS. There is no restnction on operating on any particular hardware arrangement, and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

[0228] Storage device 1030 may be a non-volatile and / or non-transitory and / or computer-readable memory device and may be a hard disk or other types of computer readable media which may store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, a floppy disk, a flexible disk, a hard disk, magnetic tape, a magnetic strip / stripe, any other magnetic storage medium, flash memory, memristor memory, any other solid-state memory, a compact disc read only memory (CD-ROM) optical disc, a rewritable compact disc (CD) optical disc, digital video disk (DVD) optical disc, a blu- ray disc (BDD) optical disc, a holographic optical disk, another optical medium, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Stick® card, a smartcard chip, a EMV chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, another integrated circuit (IC) chip / card, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash EPROM (FLASHEPROM), cache memory (e.g., Level 1 (LI) cache, Level 2 (L2) cache, Level 3 (L3) cache, Level 4 (L4) cache, Level 5 (L5) cache, or other (L#) cache), resistive random-access memory (RRAM / ReRAM), phase change memory (PCM), spin transfer torque RAM (STT-RAM), another memory chip or cartridge, and / or a combination thereof.

[0229] The storage device 1030 may include software services, servers, services, etc., that when the code that defines such software is executed by the processor 1010, it causes the system to perform a function. In some aspects, a hardware service that performs a particular function may include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 1010, connection 1005, output device 1035, etc., to carry out the function. The term “computer- readable medium” includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other mediums capable of storing, containing, or carrying instruction(s) and / or data. A computer-readable medium may include a non- transitory medium in which data may be stored and that does not include carrier waves and / or transitory electronic signals propagating wirelessly or over wired connections. Examples of anon-transitory medium may include, but are not limited to, a magnetic disk or tape, optical storage media such as compact disk (CD) or digital versatile disk (DVD), flash memory, memory or memory devices. A computer-readable medium may have stored thereon code and / or machine-executable instructions that may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc., may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, or the like.

[0230] Specific details are provided in the description above to provide a thorough understanding of the aspects and examples provided herein, but those skilled in the art will recognize that the application is not limited thereto. Thus, while illustrative aspects of the application have been described in detail herein, it is to be understood that the inventive concepts may be otherwise variously embodied and employed, and that the appended claims are intended to be construed to include such variations, except as limited by the prior art. Various features and aspects of the above-described application may be used individually or jointly. Further, aspects may be utilized in any number of environments and applications beyond those described herein without departing from the broader scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive. For the purposes of illustration, methodswere described in a particular order It should be appreciated that in alternate aspects, the methods may be performed in a different order than that described.

[0231] For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software. Additional components may be used other than those shown in the figures and / or described herein. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the aspects in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the aspects.

[0232] Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0233] Individual aspects may be described above as a process or method which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

[0234] Processes and methods according to the above-described examples may be implemented using computer-executable instructions that are stored or otherwise available from computer-readable media. Such instructions may include, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or a processing device to perform a certain function or group of functions. Portions of computer resources used may be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, source code. Examples of computer- readable media that may be used to store instructions, information used, and / or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory', networked storage devices, and so on.

[0235] In some aspects the computer-readable storage devices, mediums, and memories may include a cable or wireless signal containing a bitstream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy carrier signals, electromagnetic waves, and signals per se.

[0236] Those of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, in some cases depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

[0237] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and may take any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-program product) may be stored in a computer-readable or machine-readable medium. Aprocessor(s) may perform the necessary tasks. Examples of form factors include laptops, smart phones, mobile phones, tablet devices or other small form factor personal computers, personal digitalassistants, rackmount devices, standalone devices, and so on. Functionality described herein also may be embodied in peripherals or add-in cards. Such functionality may also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

[0238] The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are example means for providing the functions described in the disclosure.

[0239] The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of a variety of devices such as general purposes computers, wireless communication device handsets, or integrated circuit devices having multiple uses including application in wireless communication device handsets and other devices. Any features described as modules or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques may be realized at least in part by a computer- readable data storage medium comprising program code including instructions that, when executed, performs one or more of the methods, algorithms, and / or operations described above. The computer-readable data storage medium may form part of a computer program product, which may include packaging materials. The computer-readable medium may comprise memory or data storage media, such as random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, magnetic or optical data storage media, and the like. The techniques additionally, or alternatively, may be realized at least in part by a computer-readable communication medium that carries or communicates program code in the form of instructions or data structures and that may be accessed, read, and / or executed by a computer, such as propagated signals or waves.

[0240] The program code may be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, an application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Such a processor may be configured to perform any of the techniques described in this disclosure.A general-purpose processor may be a microprocessor; but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure, any combination of the foregoing structure, or any other structure or apparatus suitable for implementation of the techniques described herein.

[0241] One of ordinary skill will appreciate that the less than (“<”) and greater than (“>”) symbols or terminology used herein may be replaced with less than or equal to (“<”) and greater than or equal to (“>”) symbols, respectively, without departing from the scope of this description.

[0242] Where components are described as being “configured to” perform certain operations, such configuration may be accomplished, for example, by designing electronic circuits or other hardware to perform the operation, by programming programmable electronic circuits (e.g., microprocessors, or other suitable electronic circuits) to perform the operation, or any combination thereof.

[0243] The phrase “coupled to” or “communicatively coupled to” refers to any component that is physically connected to another component either directly or indirectly, and / or any component that is in communication with another component (e.g., connected to the other component over a wired or wireless connection, and / or other suitable communication interface) either directly or indirectly.

[0244] Claim language or other language reciting “at least one of’ a set and / or “one or more” of a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, claim language reciting “at least one of A and B” or “at least one of A or B” means A, B, or A and B. In another example, claim language reciting “at least one of A, B, and C” or “at least one of A, B, or C” means A, B, C, or A and B, or A and C, or B and C, A and B and C, or any duplicate information or data (e.g., A and A, B and B, C and C, A and A and B, and so on), or any other ordering, duplication, or combination of A, B, and C. The language “at least one of’ a set and / or “one or more” of a set does not limit the set to the items listed in the set. For example, claim language reciting “at least one of A and B” or “at least one of A or B” may mean A,B, or A and B, and may additionally include items not listed in the set of A and B. The phrases “at least one” and “one or more” are used interchangeably herein.

[0245] Claim language or other language reciting “at least one processor configured to,” “at least one processor being configured to,” “one or more processors configured to,” “one or more processors being configured to,” or the like indicates that one processor or multiple processors (in any combination) can perform the associated operation(s). For example, claim language reciting “at least one processor configured to: X, Y, and Z” means a single processor can be used to perform operations X, Y, and Z; or that multiple processors are each tasked with a certain subset of operations X, Y, and Z such that together the multiple processors perform X, Y, and Z; or that a group of multiple processors work together to perform operations X, Y, and Z. In another example, claim language reciting “at least one processor configured to: X, Y, and Z” can mean that any single processor may only perform at least a subset of operations X, Y and Z.

[0246] Where reference is made to one or more elements performing functions (e.g., steps of a method), one element may perform all functions, or more than one element may collectively perform the functions. When more than one element collectively performs the functions, each function need not be performed by each of those elements (e.g., different functions may be performed by different elements) and / or each function need not be performed in whole by only one element (e.g., different elements may perform different sub-functions of a function). Similarly, where reference is made to one or more elements configured to cause another element (e.g., an apparatus) to perform functions, one element may be configured to cause the other element to perform all functions, or more than one element may collectively be configured to cause the other element to perform the functions.

[0247] Where reference is made to an entity (e.g., any entity or device described herein) performing functions or being configured to perform functions (e.g., steps of a method), the entity may be configured to cause one or more elements (individually or collectively) to perform the functions. The one or more components of the entity may include at least one memory, at least one processor, at least one communication interface, another component configured to perform one or more (or all) of the functions, and / or any combination thereof. Where reference to the entity performing functions, the entity may be configured to cause one component to perform all functions, or to cause more than onecomponent to collectively perform the functions. When the entity is configured to cause more than one component to collectively perform the functions, each function need not be performed by each of those components (e.g., different functions may be performed by different components) and / or each function need not be performed in whole by only one component (e.g., different components may perform different sub-functions of a function).

[0248] Illustrative aspects of the disclosure include:

[0249] Aspect 1. A network device for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the network device is configured to: receive information indicative of a first earner aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs); determine a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells; determine a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell; receive information indicative of an updated CA configuration for the network device, wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and perform CA tuning using the plurality of hardware register values of the RF hardware register configuration.

[0250] Aspect 2. The network device of Aspect 1, wherein the network device is configured to perform CA tuning using the plurality of hardware register values to implement the updated C A configuration for the network device, and wherein the network device does not cause an interruption for uplink or downlink on a PCC of the updated CA configuration.

[0251] Aspect 3. The network device of any of Aspects 1 to 2, wherein the information indicative of the updated CA configuration is included in a Radio Resource Control (RRC) reconfiguration request.

[0252] Aspect 4. The network device of any of Aspects 1 to 3, wherein the information indicative of the updated CA configuration corresponds to an addition of a component carrier (CC) to the first CA configuration, a removal of a CC from the first CA configuration, or a modification of one or more of the first PCC and the first set of SCCs of the first CA configuration.

[0253] Aspect 5. The network device of any of Aspects 1 to 4, wherein the information indicative of the updated CA configuration corresponds to a handover of the network device from a first cell to a second cell, and wherein the first cell is associated with the first CA configuration and the second cell is associated with the updated CA configuration.

[0254] Aspect 6. The network device of any of Aspects 1 to 5, wherein the measurement information associated with the one or more neighboring cells corresponds to a measurement report associated with measurements of the one or more neighboring cells by the network device.

[0255] Aspect 7. The network device of Aspect 6, wherein the network device is configured to: receive one or more measurement objects corresponding to the one or more neighboring cells; and obtain the measurements of the one or more neighboring cells based on the one or more measurement objects.

[0256] Aspect 8. The network device of any of Aspects 1 to 7, wherein, to determine the predicted updated CA configuration, the network device is configured to: determine, based on the measurement information, an active set of neighboring cells included in the one or more neighboring cells; and generate the predicted updated CA configuration to include one or more respective predicted SCCs corresponding to the active set of neighboring cells.

[0257] Aspect 9. The network device of Aspect 8, wherein the network entity is configured to: compare an updated set of SCCs included in the updated CA configuration to the one or more respective predicted SCCs; for each SCC included in the updated setof SCCs and the one or more respective predicted SCCs, perform CA tuning using a respective cached RF hardware register configuration corresponding to each SCC.

[0258] Aspect 10. The network device of any of Aspects 1 to 9, wherein the network entity is configured to: determine a plurality of predicted updated CA configurations including the predicted updated CA configuration; and determine a cached RF hardware register configuration corresponding to each respective predicted updated CA configuration of the plurality of predicted updated CA configurations.

[0259] Aspect 11. The network device of Aspect 10, wherein the plurality of predicted updated CA configurations corresponds to a subset of the one or more neighboring cells, and wherein each neighboring cell of the subset is associated with an occurrence of a respective measurement event.

[0260] Aspect 12. The network device of Aspect 11, wherein the occurrence of the respective measurement event comprises an occurrence of a configured radio resource management (RRM) measurement event.

[0261] Aspect 13. The network device of any of Aspects 10 to 12, wherein the plurality of predicted updated CA configurations are included in a predicted CA set associated with the network device, and wherein the predicted CA set corresponds to different combinations of PCCs and SCCs for carrier aggregation by the network device.

[0262] Aspect 14. The network device of Aspect 13, wherein the network device is configured to: determine an occurrence of a configured measurement event for a neighboring cell; and update the predicted CA set to add an additional predicted updated CA configuration corresponding to the neighbonng cell and based on the occurrence of the configured measurement event.

[0263] Aspect 15. The network device of Aspect 14, wherein the configured measurement event comprises an Al measurement event, an A3 measurement event, an A4 measurement event, or an A6 measurement event.

[0264] Aspect 16. The network device of any of Aspects 13 to 15, wherein the network device is configured to: determine an occurrence of a configured measurement event for a neighboring cell; and update the predicted CA set to remove a predicted updated CA configuration corresponding to the neighboring cell, based on the occurrence of the configured measurement event.

[0265] Aspect 17. The network device of Aspect 16, wherein the occurrence of the respective measurement event comprises one of an A2 measurement event or an A5 measurement event.

[0266] Aspect 18. The network device of any of Aspects 1 to 17, wherein the network device is configured to: determine the updated CA configuration corresponds to a PCC RF chain different from the RF chain corresponding to the predicted updated CA configuration; generate a PCC RF hardware register configuration corresponding to the PCC RF chain of the updated CA configuration; and implement the PCC RF chain based on the PCC RF hardware register configuration, wherein the PCC RF chain is implemented before RF tuning of one or more SCCs of the updated CA configuration.

[0267] Aspect 19. The network device of Aspect 18, wherein, to implement the PCC RF chain, the network device is configured to: perform RF tuning for the PCC RF chain based on the PCC RF hardware register configuration; and generate respective SCC RF hardware register configurations corresponding to each SCC of the one or more SCCs of the updated C A configuration, wherein the network device performs the RF tuning for the PCC RF chain and generates the respective SCC RF hardware register configurations in parallel.

[0268] Aspect 20. The network device of any of Aspects 18 to 19, wherein the network device is configured to: generate a respective SCC RF hardware register configuration corresponding to each SCC of the one or more SCCs of the updated CA configuration, wherein the respective SCC RF hardware register configuration is generated after the PCC RF chain is implemented.

[0269] Aspect 21. The network device of any of Aspects 18 to 20, wherein the network device is configured to: implement a respective SCC RF chain corresponding to each SCC of the one or more SCCs of the updated CA configuration, wherein the respective SCC RF chain is implemented after the PCC RF chain is implemented.

[0270] Aspect 22. The network device of any of Aspects 1 to 21, wherein: the updated CA configuration includes an additional SCC not included in the first CA configuration or the predicted updated CA configuration; and the network device is configured to determine an RF device allocation comprising a resource allocation for an additional SCC RF chain corresponding to the additional SCC, wherein the resource allocation for theadditional SCC RF chain does not impact a currently configured resource allocation for a PCC RF chain corresponding to the first PCC.

[0271] Aspect 23. The network device of Aspect 22, wherein the network device is configured to implement the additional SCC RF chain without an interruption for uplink or downlink on the PCC RF chain.

[0272] Aspect 24. The network device of any of Aspects 22 to 23, wherein the network device is configured to determine an updated PCC RF chain based on the resource allocation for the additional SCC RF chain, and wherein the RF device allocation generates the updated PCC RF chain to include a non-shared antenna of the network device.

[0273] Aspect 25. The network device of any of Aspects 1 to 24, wherein: the updated CA configuration corresponds to an updated PCC RF chain different from a first PCC RF chain corresponding to the first PCC; an RF front end of the network device includes a plurality of combined RF paths each configurable as a frequency range 1 (FR1) RF path or a frequency range 2 (FR2) RF path; and the network device is configured to perform RF device allocation to allocate the updated PCC RF chain using a subset of the plurality of combined RF paths reserved as FR2 RF paths, based on a determination the updated CA configuration does not include one or more FR2 component carriers (CCs).

[0274] Aspect 26. The network device of Aspect 25, wherein the network device is configured to perform CA tuning to implement the updated CA configuration without an interruption on uplink or downlink for the updated PCC RF chain, based on the allocation of the updated PCC RF chain on a reserved FR2 RF path.

[0275] Aspect 27. A method for wireless communication by a network device, the method comprising: receiving information indicative of a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs); determining a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells; determining a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain correspondingto the predicted updated CA configuration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell; receiving information indicative of an updated CA configuration for the network device, wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and performing CA tuning using the plurality of hardware register values of the RF hardware register configuration.

[0276] Aspect 28. The method of Aspect 27, wherein performing CA tuning comprises using the plurality of hardware register values to implement the updated CA configuration for the network device, wherein performing CA tuning does not cause an interruption for uplink or downlink on a PCC of the updated CA configuration.

[0277] Aspect 29. The method of any of Aspects 27 to 28, wherein the information indicative of the updated CA configuration is included in a Radio Resource Control (RRC) reconfiguration request.

[0278] Aspect 30. The method of any of Aspects 27 to 29, wherein the information indicative of the updated CA configuration corresponds to an addition of a component carrier (CC) to the first CA configuration, a removal of a CC from the first CA configuration, or a modification of one or more of the first PCC and the first set of SCCs of the first CA configuration.

[0279] Aspect 31. The method of any of Aspects 27 to 30, wherein the information indicative of the updated CA configuration corresponds to a handover of the network device from a first cell to a second cell, and wherein the first cell is associated with the first CA configuration and the second cell is associated with the updated CA configuration.

[0280] Aspect 32. The method of any of Aspects 27 to 31, wherein the measurement information associated with the one or more neighboring cells corresponds to a measurement report associated with measurements of the one or more neighboring cells by the network device.

[0281] Aspect 33. The method of Aspect 32, further comprising: receiving one or more measurement objects corresponding to the one or more neighboring cells; and obtainingthe measurements of the one or more neighboring cells based on the one or more measurement objects.

[0282] Aspect 34. The method of any of Aspects 27 to 33. wherein determining the predicted updated CA configuration includes: determining, based on the measurement information, an active set of neighboring cells included in the one or more neighboring cells; and generating the predicted updated CA configuration to include one or more respective predicted SCCs corresponding to the active set of neighboring cells.

[0283] Aspect 35. The method of Aspect 34, further comprising: comparing an updated set of SCCs included in the updated CA configuration to the one or more respective predicted SCCs; for each SCC included in the updated set of SCCs and the one or more respective predicted SCCs, performing CA tuning using a respective cached RF hardware register configuration corresponding to each SCC.

[0284] Aspect 36. The method of any of Aspects 27 to 35, further comprising: determining a plurality of predicted updated CA configurations including the predicted updated CA configuration; and determining a cached RF hardware register configuration corresponding to each respective predicted updated CA configuration of the plurality of predicted updated CA configurations.

[0285] Aspect 37. The method of Aspect 36, wherein the plurality of predicted updated CA configurations corresponds to a subset of the one or more neighboring cells, and wherein each neighboring cell of the subset is associated with an occurrence of a respective measurement event.

[0286] Aspect 38. The method of Aspect 37, wherein the occurrence of the respective measurement event comprises an occurrence of a configured radio resource management (RRM) measurement event.

[0287] Aspect 39. The method of any of Aspects 36 to 38, wherein the plurality of predicted updated CA configurations are included in a predicted CA set associated with the network device, and wherein the predicted CA set corresponds to different combinations of PCCs and SCCs for carrier aggregation by the network device.

[0288] Aspect 40. The method of Aspect 39, further comprising: determining an occurrence of a configured measurement event for a neighboring cell; and updating thepredicted CA set to add an additional predicted updated CA configuration corresponding to the neighboring cell and based on the occurrence of the configured measurement event.

[0289] Aspect 41. The method of Aspect 40, wherein the configured measurement event comprises an Al measurement event, an A3 measurement event, an A4 measurement event, or an A6 measurement event.

[0290] Aspect 42. The method of any of Aspects 39 to 41, further comprising: determining an occurrence of a configured measurement event for a neighboring cell; and updating the predicted CA set to remove a predicted updated CA configuration corresponding to the neighboring cell, based on the occurrence of the configured measurement event.

[0291] Aspect 43. The method of Aspect 42, wherein the occurrence of the respective measurement event comprises one of an A2 measurement event or an A5 measurement event.

[0292] Aspect 44. The method of any of Aspects 27 to 43, further comprising: determining the updated CA configuration corresponds to a PCC RF chain different from the RF chain corresponding to the predicted updated CA configuration; generating a PCC RF hardware register configuration corresponding to the PCC RF chain of the updated CA configuration; and implementing the PCC RF chain based on the PCC RF hardware register configuration, wherein the PCC RF chain is implemented before RF tuning of one or more SCCs of the updated CA configuration.

[0293] Aspect 45. The method of Aspect 44, wherein implementing the PCC RF chain includes: performing RF tuning for the PCC RF chain based on the PCC RF hardware register configuration; and generating respective SCC RF hardware register configurations corresponding to each SCC of the one or more SCCs of the updated CA configuration, wherein the network device performs the RF tuning for the PCC RF chain and generates the respective SCC RF hardware register configurations in parallel.

[0294] Aspect 46. The method of any of Aspects 44 to 45, further comprising: generating a respective SCC RF hardware register configuration corresponding to each SCC of the one or more SCCs of the updated CA configuration, wherein the respective SCC RF hardware register configuration is generated after the PCC RF chain is implemented.

[0295] Aspect 47. The method of any of Aspects 44 to 46, further comprising: implementing a respective SCC RF chain corresponding to each SCC of the one or more SCCs of the updated CA configuration, wherein the respective SCC RF chain is implemented after the PCC RF chain is implemented.

[0296] Aspect 48. The method of any of Aspects 27 to 47, wherein the updated CA configuration includes an additional SCC not included in the first CA configuration or the predicted updated CA configuration, and wherein the method further includes determining an RF device allocation comprising a resource allocation for an additional SCC RF chain corresponding to the additional SCC, wherein the resource allocation for the additional SCC RF chain does not impact a currently configured resource allocation for a PCC RF chain corresponding to the first PCC.

[0297] Aspect 49. The method of Aspect 48, further comprising implementing the additional SCC RF chain without an interruption for uplink or downlink on the PCC RF chain.

[0298] Aspect 50. The method of any of Aspects 48 to 49, further comprising determining an updated PCC RF chain based on the resource allocation for the additional SCC RF chain, wherein the RF device allocation generates the updated PCC RF chain to include a non-shared antenna of the network device.

[0299] Aspect 51. The method of any of Aspects 27 to 50, wherein: the updated CA configuration corresponds to an updated PCC RF chain different from a first PCC RF chain corresponding to the first PCC; an RF front end of the network device includes a plurality of combined RF paths each configurable as a frequency range 1 (FR1) RF path or a frequency range 2 (FR2) RF path; and the network device is configured to perform RF device allocation to allocate the updated PCC RF chain using a subset of the plurality of combined RF paths reserved as FR2 RF paths, based on a determination the updated CA configuration does not include one or more FR2 component carriers (CCs).

[0300] Aspect 52. The method of Aspect 51 , further comprising performing CA tuning to implement the updated CA configuration without an interruption on uplink or downlink for the updated PCC RF chain, based on the allocation of the updated PCC RF chain on a reserved FR2 RF path.

[0301] Aspect 53. A non-transitory computer-readable storage medium comprising instructions stored thereon which, when executed by at least one processor, causes the at least one processor to perform operations according to any of Aspects 1 to 26.

[0302] Aspect 54. A non-transitory computer-readable storage medium comprising instructions stored thereon which, when executed by at least one processor, causes the at least one processor to perform operations according to any of Aspects 27 to 52.

[0303] Aspect 55. An apparatus for wireless communication comprising one or more means for performing operations according to any of Aspects 1 to 26.

[0304] Aspect 56. An apparatus for wireless communication comprising one or more means for performing operations according to any of Aspects 27 to 52.

Claims

CLAIMSWhat is claimed is:

1. A network device for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the network device is configured to: receive information indicative of a first earner aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs); determine a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells; determine a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain corresponding to the predicted updated C A configuration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell; receive information indicative of an updated CA configuration for the network device, wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and perform CA tuning using the plurality of hardware register values of the RF hardware register configuration.

2. The network device of claim 1, wherein the network device is configured to perform C A tuning using the plurality' of hardware register values to implement the updated CA configuration for the network device, and wherein the network device does not cause an interruption for uplink or downlink on a PCC of the updated CA configuration.

3. The network device of claim 1, wherein the information indicative of the updated CA configuration is included in a Radio Resource Control (RRC) reconfiguration request.

4. The network device of claim 1, wherein the information indicative of the updated CA configuration corresponds to an addition of a component carrier (CC) to the first CA configuration, a removal of a CC from the first CA configuration, or a modification of one or more of the first PCC and the first set of SCCs of the first CA configuration.

5. The network device of claim 1, wherein the measurement information associated with the one or more neighboring cells corresponds to a measurement report associated with measurements of the one or more neighboring cells by the network device, and wherein the network device is configured to: receive one or more measurement objects corresponding to the one or more neighboring cells; and obtain the measurements of the one or more neighboring cells based on the one or more measurement objects.

6. The network device of claim 1, wherein, to determine the predicted updated CA configuration, the network device is configured to: determine, based on the measurement information, an active set of neighboring cells included in the one or more neighboring cells; and generate the predicted updated CA configuration to include one or more respective predicted SCCs corresponding to the active set of neighboring cells.

7. The network device of claim 6, wherein the network entity is configured to: compare an updated set of SCCs included in the updated CA configuration to the one or more respective predicted SCCs; for each SCC included in the updated set of SCCs and the one or more respective predicted SCCs, perform CA tuning using a respective cached RF hardware register configuration corresponding to each SCC.

8. The network device of claim 1, wherein the network entity is configured to: determine a plurality of predicted updated CA configurations including the predicted updated CA configuration; and determine a cached RF hardware register configuration corresponding to each respective predicted updated CA configuration of the plurality of predicted updated CA configurations.

9. The network device of claim 8, wherein the plurality of predicted updated CA configurations corresponds to a subset of the one or more neighboring cells, and wherein each neighboring cell of the subset is associated with an occurrence of a respective measurement event.

10. The network device of claim 8, wherein the plurality of predicted updated CA configurations are included in a predicted CA set associated with the network device, and wherein the predicted C A set corresponds to different combinations of PCCs and SCCs for carrier aggregation by the network device.

11. The network device of claim 10, wherein the network device is configured to: determine an occurrence of a configured measurement event for a neighboring cell; and update the predicted CA set to add an additional predicted updated CA configuration corresponding to the neighboring cell and based on the occurrence of the configured measurement event, wherein the configured measurement event comprises an Al measurement event, an A3 measurement event, an A4 measurement event, or an A6 measurement event.

12. The network device of claim 10, wherein the network device is configured to: determine an occurrence of a configured measurement event for a neighboring cell; and update the predicted CA set to remove a predicted updated CA configuration corresponding to the neighboring cell, based on the occurrence of the configured measurement event, wherein the occurrence of the respective measurement event comprises one of an A2 measurement event or an A5 measurement event.

13. The network device of claim 1, wherein the network device is configured to: determine the updated CA configuration corresponds to a PCC RF chain different from the RF chain corresponding to the predicted updated CA configuration; generate a PCC RF hardware register configuration corresponding to the PCC RF chain of the updated CA configuration; and implement the PCC RF chain based on the PCC RF hardware register configuration, wherein the PCC RF chain is implemented before RF tuning of one or more SCCs of the updated CA configuration.

14. The network device of claim 13, wherein, to implement the PCC RF chain, the network device is configured to: perform RF tuning for the PCC RF chain based on the PCC RF hardware register configuration; and generate respective SCC RF hardware register configurations corresponding to each SCC of the one or more SCCs of the updated CA configuration, wherein the network device performs the RF tuning for the PCC RF chain and generates the respective SCC RF hardware register configurations in parallel.

15. The network device of claim 14, wherein the network device is configured to generate a respective SCC RF hardware register configuration corresponding to each SCC of the one or more SCCs of the updated CA configuration, and wherein the respective SCC RF hardware register configuration is generated after the PCC RF chain is implemented.

16. The network device of claim 14, wherein the network device is configured to implement a respective SCC RF chain corresponding to each SCC of the one or more SCCs of the updated CA configuration, and wherein the respective SCC RF chain is implemented after the PCC RF chain is implemented.

17. The network device of claim 1, wherein: the updated CA configuration includes an additional SCC not included in the first CA configuration or the predicted updated CA configuration; and the network device is configured to determine an RF device allocation comprising a resource allocation for an additional SCC RF chain corresponding to theadditional SCC, wherein the resource allocation for the additional SCC RF chain does not impact a currently configured resource allocation for a PCC RF chain corresponding to the first PCC.

18. The network device of claim 17, wherein the network device is configured to implement the additional SCC RF chain without an interruption for uplink or downlink on the PCC RF chain.

19. The network device of claim 1, wherein: the updated CA configuration corresponds to an updated PCC RF chain different from a first PCC RF chain corresponding to the first PCC; an RF front end of the network device includes a plurality of combined RF paths each configurable as a frequency range 1 (FR1) RF path or a frequency range 2 (FR2) RF path; and the network device is configured to perform RF device allocation to allocate the updated PCC RF chain using a subset of the plurality of combined RF paths reserved as FR2 RF paths, based on a determination the updated CA configuration does not include one or more FR2 component carriers (CCs).

20. A method for wireless communication by a network device, the method comprising: receiving information indicative of a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first primary component carrier (PCC) and a first set of secondary component carriers (SCCs); determining a predicted updated CA configuration using measurement information associated with one or more neighboring cells of the network device, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to respective measurements of a particular neighboring cell of the one or more neighboring cells; determining a plurality of hardware register values of a radio frequency (RF) hardware register configuration for an RF chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values is based on the respective measurements of the particular neighboring cell;receiving information indicative of an updated CA configuration for the network device, wherein the updated CA configuration is different from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and performing C A tuning using the plurality of hardware register values of the RF hardware register configuration.

Images