Multicarrier aggregation using predicted configuration corresponding to neighboring cells

Abstract

Systems and techniques for wireless communication are provided. For example, a network device can receive information indicating a first carrier aggregation (CA) configuration including a set of secondary component carriers (SCCs) and a primary component carrier (PCC). An 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 RF chains corresponding to the predicted updated CA configuration based on the measurements of the particular neighboring cell. The network device can receive information indicating an updated CA configuration that is different from the first CA configuration and includes at least one of the predicted PCC or the predicted SCC. The network device can perform a CA tuning using the plurality of hardware register values of the RF hardware register configuration.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communications. In some specific embodiments, examples are described for configuring CA for a network device based on a predicted updated carrier aggregation (CA) configuration determined by the network device. Background Technology

[0002] Wireless communication systems are deployed to provide a variety of telecommunications services, including telephone, video, data, messaging, and broadcasting. Wireless communication systems have undergone several generations of development, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including the transitional 2.5G networks), third-generation (3G) high-speed data wireless service with internet capabilities, fourth-generation (4G) services (e.g., LTE, WiMax), and fifth-generation (5G) services (e.g., New Radio (NR)). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), etc. Summary of the Invention

[0003] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceived aspects, nor should it be considered to identify key or decisive elements relating to all conceived aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a simplified form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0004] Systems, methods, apparatuses, and computer-readable media for performing wireless communication are disclosed. According to at least one exemplary 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 indicating a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first set of secondary component carriers (SCCs) and a first primary component carrier (PCC); 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 a corresponding measurement of a specific neighboring cell in the one or more neighboring cells; determine a plurality of hardware register values ​​for configuring RF hardware registers for a radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values ​​are based on the corresponding measurement of the specific neighboring cell; receive information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs from the first CA configuration, and wherein the updated CA configuration includes at least one of a predicted PCC or a predicted SCC; and perform CA tuning using the plurality of hardware register values ​​configured in the RF hardware register configuration.

[0005] In another example, a method for wireless communication is provided, the method comprising: receiving information indicating a first carrier aggregation (CA) configuration for a network device, wherein the first CA configuration corresponds to a first set of secondary component carriers (SCCs) and a first primary component carrier (PCC); 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 a corresponding measurement of a specific neighboring cell in one or more of the neighboring cells; determining a plurality of hardware register values ​​for configuring RF hardware registers for a radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values ​​are based on the corresponding measurement of the specific neighboring cell; receiving information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs from the first CA configuration, and wherein the updated CA configuration includes at least one of a predicted PCC or a predicted SCC; and performing CA tuning using the plurality of hardware register values ​​configured in the RF hardware register configuration.

[0006] In another example, a non-transitory computer-readable storage medium includes instructions stored thereon that, when executed by at least one processor, cause the at least one processor to: receive information indicating a first carrier aggregation (CA) configuration for a network device, wherein the first CA configuration corresponds to a first set of secondary component carriers (SCCs) and a first primary component carrier (PCC); 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 a corresponding measurement of a particular neighboring cell among the one or more neighboring cells; determine a plurality of hardware register values ​​for configuring RF hardware registers for a radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values ​​are based on the corresponding measurement of the particular neighboring cell; receive information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs from the first CA configuration, and wherein the updated CA configuration includes at least one of a predicted PCC or a predicted SCC; and perform CA tuning using the plurality of hardware register values ​​configured by the RF hardware registers.

[0007] In another example, an apparatus for wireless communication is provided. The apparatus includes: components for: receiving information indicating a first carrier aggregation (CA) configuration for a network device, wherein the first CA configuration corresponds to a first set of secondary component carriers (SCCs) and a first primary component carrier (PCC); components 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 a corresponding measurement of a specific neighboring cell among the one or more neighboring cells; components for: determining a plurality of hardware register values ​​for configuring RF hardware registers for a radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values ​​are based on the corresponding measurement of the specific neighboring cell; components for: receiving information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC; and components for: performing CA tuning using the plurality of hardware register values ​​configured using the RF hardware registers.

[0008] The aspects typically include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems, as fully described herein with reference to the accompanying drawings and description, and as illustrated in the accompanying drawings and description.

[0009] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing provided in the drawings is for illustrative and descriptive purposes and not as a limitation of the definitions in the claims.

[0010] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the 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). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations.

[0011] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. 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 define the scope of the claimed subject matter. This subject matter should be understood with reference to the appropriate portions of the entire specification, any or all of the drawings, and each claim.

[0012] The foregoing and other features and aspects will become more apparent from the following description, claims and accompanying drawings. Attached Figure Description

[0013] The accompanying drawings are provided to help describe various aspects of this disclosure, and are provided for illustrative purposes only and not to limit the aspects.

[0014] Figure 1 This is a block diagram illustrating an example of a wireless communication network based on some examples; Figure 2 These are illustrations of base station and user equipment (UE) designs based on some examples, which enable the transmission and processing of signals exchanged between the UE and the base station; Figure 3 This is a diagram illustrating an example of a decomposed base station based on some examples; Figure 4 This is a block diagram illustrating the components of a user equipment (UE) based on some examples; Figure 5 This is a diagram illustrating examples of physical channels and reference signals in some example wireless networks; Figure 6 This is a diagram illustrating example timelines for carrier aggregation (CA) tuning to achieve CA configuration for a UE or network device, based on some examples. Figure 7 This is a diagram illustrating examples of multi-carrier aggregation corresponding to the primary component carrier (PCC) and secondary component carrier (SCC) associated with the radio frequency (RF) transceiver of a UE or network device, based on some examples; Figure 8 This is a diagram illustrating example timelines for CA tuning for UE or network devices within a configured time limit using the PCC tuning phase and the SCC tuning phase, based on some examples. Figure 9 This is a flowchart illustrating an example of a process for wireless communication by a network device, based on some examples; and Figure 10 This is a block diagram illustrating examples of computing systems that can be adopted by the disclosed systems and technologies, based on some examples. Detailed Implementation

[0015] Certain aspects of this disclosure are provided below for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Additionally, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure. Some aspects described herein can be applied independently, and some of them can be combined, as will be apparent to those skilled in the art. In the following description, specific details are set forth for illustrative purposes to provide a thorough understanding of various aspects of this application. However, it will be apparent that various aspects can be practiced without these specific details. The accompanying drawings and descriptions are not intended to be limiting.

[0016] The following description provides only exemplary aspects and is not intended to limit the scope, applicability, or configuration of this disclosure. Rather, the following description of the exemplary aspects will provide those skilled in the art with a description that can be used to implement the exemplary aspects. It should be understood that various changes can be made to the function and arrangement of the elements without departing from the scope of this application as set forth in the appended claims.

[0017] Wireless communication networks can be deployed to provide a variety of communication services, such as voice, video, packet data, message sending and receiving, broadcasting, any combination thereof, or other communication services. Wireless communication networks can support both access links and sidelinks for communication between wireless devices. An access link can refer to any communication link between a client device (e.g., a User Equipment (UE), 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 can support uplink signaling, downlink signaling, connection procedures, etc. An example of an access link is the Uu link or interface (also known as NR-Uu) between a 3GPP gNB and a UE.

[0018] Wireless communication networks can utilize multiple carriers within a frequency band to implement multiple access techniques, where multiple network devices (e.g., UEs) share the same carrier frequency based on access divisions in terms of time, frequency, and code. Component carriers (CCs) can be used to aggregate bandwidth portions of the spectrum and / or frequency band 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 performing uplink and downlink transmissions associated with the UE.

[0019] Carrier aggregation can also be referred to as multi-carrier aggregation (multi-CA). The aggregated carriers (e.g., the aggregated CCs) may be located within the same frequency band of the wireless communication network and / or within different frequency bands of the wireless communication network. CA performed using CCs within the same frequency band is referred to as intra-band CA. CA performed using CCs across multiple (e.g., different) frequency bands is referred to as inter-band CA. In some examples, 5G NR can utilize flexible carrier structures where the bandwidth of a CC varies up to 400 MHz in the millimeter-wave spectrum (e.g., frequency range 2 (FR2)) and up to 100 MHz in the sub-6 GHz band (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, based on network implementation of one or more frequency reuse techniques (e.g., Dynamic Spectrum Sharing (DSS), beamforming and / or massive MIMO, inter-cell interference coordination (ICIC) and / or enhanced ICIC, etc.), the same carrier can be used by multiple cells.

[0020] The CA configuration for the UE can be associated with a primary component carrier (PCC) and one or more secondary component carriers (SCCs). The PCC can be selected as the CC to be used as the primary (e.g., main) carrier to provide primary radio resources for the UE's uplink and downlink transmissions. For example, the PCC can be selected as a specific CC that has a wider bandwidth and / or stronger coverage for the UE compared to a CC configured as an SCC in the CA configuration. The PCC can be used for signaling and control functions associated with the CA configuration and its implementation at the UE, and can be used to establish initial connections to the network and subsequently manage CA-enabled communication sessions. The SCC can be configured as an additional carrier (e.g., an additional CC) that is aggregated with the PCC into a single logical channel for the UE's uplink and downlink transmissions. As previously noted, the PCC and SCC can be located in the same frequency band (e.g., in-band CA) and / or in different frequency bands (e.g., inter-band CA).

[0021] Aggregating one or more SCCs with the UE's PCC can improve the UE's overall data throughput and communication performance. In some examples, SCCs can be dynamically added to and / or removed from the CA configuration implemented by the UE. For example, SCC addition and / or removal can be performed based on network conditions, UE capabilities, UE measurement reports, etc. In some examples, adding and / or removing one or more SCCs may also be referred to as CA reconfiguration.

[0022] For example, CA reconfiguration can be performed by the UE and / or on behalf of the UE based on changed network conditions, handover, or mobility events. During a handover or mobility event, the UE can be configured to update or reconfigure its CA configuration to add and activate a new PCC (and remove the current PCC). The UE can be configured to update or reconfigure its CA configuration to add and activate one or more new SCCs. SCC addition and activation can be performed without correspondingly removing existing SCCs included in the UE's CA configuration (e.g., the total number of SCCs used for CA increases). In some examples, SCC addition and activation can be performed in conjunction with the removal of one or more existing SCCs from the UE's CA configuration (e.g., the total number of SCCs used for CA remains the same or decreases).

[0023] In some examples, carrier aggregation can be implemented and / or configured for the UE based on one or more Radio Resource Control (RRC) messages between the UE and network entities (e.g., gNB, base station, etc.). For example, one or more RRC messages may be RRC reconfiguration messages. In some cases, the UE may receive an RRC reconfiguration message indicating an updated CA configuration that corresponds to the addition and / or removal of one or more SCCs.

[0024] To implement an updated CA configuration (e.g., CA reconfiguration), the UE may perform radio frequency (RF) tuning of the SCCs included in the updated CA configuration and / or RF tuning of the PCCs. For example, the UE may perform an impact analysis to determine the specific CCs affected by the transition from the UE's current CA configuration to the updated CA configuration indicated by the RRC reconfiguration message. CCs affected by the updated CA configuration may include carriers newly added as SCCs, carriers newly added as PCCs, removed active SCCs or PCCs, etc. CCs affected by the updated CA configuration may also include one or more PCCs and / or SCCs that remain in both the UE's current CA configuration and the updated CA configuration, which must be reconfigured or retuned to accommodate the addition of one or more new SCCs.

[0025] The UE can perform RF tuning at least for the CCs affected by the updated CA configuration. RF tuning can be associated with assigning the UE's corresponding RF hardware components (e.g., corresponding RF chains) to each of the affected CCs. For example, the UE's Transceiver Resource Manager (TRM) can be configured to perform RF device allocation and probing to determine the corresponding RF paths for the new SCC Rx / Tx chains and / or PCC Rx / Tx chains. As used herein, Rx / Tx chains can also be referred to as RF chains, and vice versa. An RF chain can correspond to a sequence of hardware components used to process RF signals between the UE's antenna and digital baseband system.

[0026] For example, the UE may include a modem and / or multiple RF front-ends (RFFEs) that can be configured to support (e.g., implemented at the UE) multiple different RF band combinations. In some cases, the UE may include multiple different antennas and multiple different RF chain components (e.g., analog-to-digital converters (ADCs), low-noise amplifiers (LNAs), phase-locked loops (PLLs), wideband (WB) paths, narrowband (NB) paths, etc.). The RF chain may be implemented by the UE as a sequence of specific hardware components, each selected from multiple (or shared) instances of each hardware component in the RF chain. For example, for a given CA band combination (e.g., inter-band or intra-band with multiple SCCs), the UE may have multiple options for RF tuning.

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

[0028] After RF device allocation and probing determine the RF path for each SCC and PCC Rx / Tx chain, the UE can perform RF script construction. For example, RF script construction may correspond to implementing the RF path for each SCC and PCC Rx / Tx chain in the UE's RF hardware. In some examples, the RF script may indicate a set of settings on the UE's RF hardware for implementing a specific RF path and / or PCC or SCC RF chain. For example, the RF script may include a list of hardware register settings that need to be programmed into the UE's RF hardware to implement a specific RF path and RF chain for PCC or SCC configuration for CA. In some aspects, the RF script may be provided as a mapping between high-level settings indicating carrier configuration parameters (e.g., PCC or SCC, specific channel, bandwidth, power level, timing, and synchronization, etc.) and corresponding low-level RF hardware register values ​​used to implement the high-level settings. As used herein, the RF script may also be referred to as RF hardware register configuration, where the RF hardware register configuration includes multiple hardware register values ​​that can be used to implement a specific RF path and / or RF chain in the RF hardware of the UE or other network devices. In some respects, the terms "RF script" and "RF hardware register configuration" are used interchangeably herein. RF script construction may also be referred to as determining the RF hardware register configuration and / or determining the RF hardware register configuration.

[0029] After the RF script is constructed, the UE executes the RF script to configure the updated CA configuration's PCC chain and / or SCC chain in the UE's RF hardware. For example, after determining the RF hardware register configuration (e.g., the RF script) for implementing PCC and SCC, the UE can implement the RF hardware register configuration (e.g., execute the RF script) by writing multiple 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's RF hardware.

[0030] In many examples, RF script execution may include the UE causing an interruption on one or more subframes on a PCell (e.g., PCC) and / or an activated SCell (e.g., an activated SCC). The interruption may be uplink- and / or downlink-oriented and may also be referred to as "Rx / Tx blanking". For example, an uplink interruption of one or more subframes on a PCC may be referred to as PCC Tx blanking, and a downlink interruption of one or more subframes on a PCC may be referred to as PCC Rx blanking. An uplink interruption of one or more subframes on an SCC may be referred to as SCC Tx blanking, and a downlink interruption of one or more subframes on an SCC may be referred to as SCC Rx blanking. During RF script execution, the UE may cause an interruption (e.g., Rx / Tx blanking) of one or more subframes on a PCC and / or one or more existing SCCs (e.g., not SCCs newly added in the updated CA configuration). For example, the UE may cause an interruption when an SCell (e.g., SCC) is added or released, activated or deactivated, or during measurements of the SCC. During one or more subframes of uplink and / or downlink interruption (e.g., Rx / Tx blanking) for a specific carrier (e.g., PCC or SCC), the UE is configured not to receive or transmit on the specific carrier.

[0031] As previously noted, RRC reconfiguration requests can be used to signal and / or trigger updated CA configuration for the UE. RRC reconfiguration requests instructing updated CA configuration can be associated with processing time constraints, which can be predefined or configured processing time constraints 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 to receive uplink permission 20ms from the end of receiving the DL RRC message.

[0032] The implementation of updated CA configuration by the UE can be associated with a 20ms RF tuning window, based on using an RRC reconfiguration request (e.g., a DL RRC message) to indicate and / or signal updated CA configuration information. If the UE has not completed RF tuning to implement updated CA configuration by the end of the configured time window, UE performance may degrade (e.g., communication to the UE may be restored based on the network's 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 RF tuning for CA reconfiguration is associated with PCC interruption (e.g., Rx / Tx blanking), the UE may additionally miss receiving critical DL / UL grants from network entities (e.g., gNB, base station, etc.) and / or may miss transmissions to network entities (e.g., SCC activation MAC-CE, etc.).

[0033] Systems and technologies are required to enable CA configuration and / or CA reconfiguration for the UE within the network's configured processing time requirements. Systems and technologies are also required to enable CA configuration and / or CA reconfiguration for the UE without causing up to one or more subframe interruptions on the PCC (e.g., Rx / Tx blanking) (e.g., no uplink and / or downlink interruption of the PCC during RF script execution).

[0034] This document describes systems, apparatus, processes (also referred to as methods), and computer-readable media (collectively, “systems and techniques”) that can be used to provide optimized multicarrier configuration for carrier aggregation associated with network devices (e.g., UEs, etc.). For example, these systems and techniques can be used to implement CA configuration and / or CA reconfiguration within configured processing time limits or configured processing time requirements of the network. In some cases, these systems and techniques can be used to implement CA configuration or CA reconfiguration within RRC processing time limits configured by the network and associated with DL RRC messages indicating CA configuration or CA reconfiguration. In some aspects, these systems and techniques can be used to implement CA configuration and / or CA reconfiguration for UEs without interruption (e.g., Rx / Tx blanking) on ​​the PCC associated with carrier aggregation.

[0035] For example, this system and technology can optimize multi-carrier configuration for carrier aggregation associated with a UE or other network device by prioritizing the processing of the PCC for the updated CA configuration over the processing of one or more SCCs for the updated CA configuration. In some examples, the 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 one or more SCCs. In an exemplary example, RF hardware register script construction for the PCC only (e.g., RF hardware register configuration determination) can be performed in the first phase. Based on the completion of the RF script construction for the PCC, the UE can then perform RF hardware register script construction for the SCCs in the second phase. In some aspects, SCC RF script construction can be performed in parallel with PCC retuning, wherein PCC retuning includes RF tuning for the PCC for the updated CA configuration and is based on the PCC RF script generated during the first phase of RF script construction.

[0036] In some cases, the UE may use its TRM or RF controller to perform RF device allocation. Based on the completion of RF device allocation, RF script construction (e.g., RF hardware register configuration determination) may be performed in three steps (e.g., three phases), which are configured to prioritize and complete PCC Rx / Tx tuning first. For example, multi-phase RF script construction may be configured to prioritize PCC Rx / Tx tuning over SCC Rx / Tx tuning and complete PCC Rx / Tx tuning before SCC Rx / Tx tuning and within the RF tuning window (e.g., a 20ms DL RRC message processing time limit, etc.) used to implement the updated CA configuration. In some aspects, prioritizing and performing PCC Rx / Tx script construction and execution in the first phase may result in any PCC interruption (e.g., Rx / Tx blanking) occurring 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 network entities or missing UL transmissions to network entities, and thus can improve UE performance.

[0037] In some examples, the UE can be configured to minimize PCC disruption during RF device allocation and RF script execution associated with the implementation of 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 PCC Rx and Tx are not blanked for the target allocation (e.g., PCC downlink and uplink are not interrupted, respectively). If the UE cannot perform an allocation to avoid PCC disruption (e.g., Rx / Tx blanking), the UE can then attempt to perform an allocation to assign the PCC Rx / Tx chain to a non-shared antenna (e.g., a dedicated antenna for the PCC Rx / Tx chain).

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

[0039] The predicted updated CA configuration determined by the UE may include one or more of the predicted PCC or predicted SCC for carrier aggregation implemented at the UE. The predicted PCC or predicted SCC may be based on corresponding measurements of neighboring cells. For example, the predicted PCC or predicted SCC may correspond to the best or strongest cell among multiple neighboring cells previously measured by the UE (e.g., the best or strongest cell indicated in the UE measurement report to the network entity based on the UE's prediction will later be configured as a new PCC or SCC for the updated CA configuration used by the UE). In some aspects, the UE may be configured to pre-build a corresponding RF hardware register script for each predicted PCC and / or predicted SCC included in the corresponding predicted updated CA configuration determined by the UE. In some cases, a pre-built RF script for the predicted PCC or predicted SCC may be obtained as RF hardware register values ​​used by the UE to obtain or perform measurements of neighboring cells corresponding to the predicted PCC or predicted SCC. For example, the UE can save or store the RF hardware register configuration of neighboring cells as a pre-built RF script for the predicted PCC or predicted SCC corresponding to the neighboring cells, instead of clearing the RF hardware register configuration after the measurement is completed.

[0040] Based on receiving an RRC reconfiguration request indicating the updated CA configuration for the UE, the UE can compare the updated PCC and / or one or more updated SCCs of the updated CA configuration with the corresponding predicted PCC and SCC of a pre-built RF script generated and stored by the UE. In some cases, the UE can determine whether any SCC indicated in the updated CA configuration for the UE is a previously measured neighbor for which the pre-built RF script is available. Based on the determination that an added SCC in the updated CA configuration is a previously measured neighbor, the UE can obtain the corresponding pre-built RF script for that neighbor and execute the pre-built RF script without performing RF device allocation, probing, or RF script construction (e.g., determining RF hardware register configuration) for the added SCC in the updated CA configuration.

[0041] Other aspects of the system and technology will be described in relation to the accompanying drawings.

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

[0043] As used herein, the terms “User Equipment” (UE) and “Network Entity” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, and / or tracking device, etc.), wearable device (e.g., smartwatch, smart glasses, wearable ring, and / or extended reality (XR) device (such as virtual reality (VR) headsets, augmented reality (AR) headsets or glasses, or mixed reality (MR) headsets)), vehicle (e.g., car, motorcycle, bicycle, etc.), aircraft (e.g., airplane, jet, unmanned aerial vehicle (UAV) or drone, helicopter, airship, glider, etc.), and / or Internet of Things (IoT) device, etc., for a user to use to communicate over a wireless communication network. A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term "UE" can be interchangeably referred to as "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal," or "UT," "mobile device," "mobile terminal," "mobile station," or variations thereof. In general, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the IEEE 802.11 communication standard), etc.

[0044] Network entities can be implemented in a converged or monolithic base station architecture, or alternatively, in a decomposed 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. A base station (e.g., with a converged / monolithic or decomposed base station architecture) may operate according to one of several RATs communicating with the UE (depending on the network in which it is deployed), and may alternatively be referred to as an access point (AP), network node, NodeB (NB), evolved NodeB (eNB), next-generation eNB (ng-eNB), new radio (NR) NodeB (also known as gNB or gNodeB), etc. The base station may primarily be used to support the UE's radio access, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication links through which a UE can transmit signals to a base station are called uplink (UL) channels (e.g., reverse traffic channels, reverse control channels, access channels, etc.). The communication links through which a base station can transmit signals to a UE are called downlink (DL) or forward link channels (e.g., paging channels, control channels, broadcast channels, or forward traffic channels, etc.). As used herein, the term traffic channel (TCH) can refer to uplink, reverse or downlink, and / or forward traffic channel.

[0045] The terms "network entity" or "base station" (e.g., having a converged / monolithic or decomposed base station architecture) can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, when the term "network entity" or "base station" refers to a single physical TRP, that physical TRP may be a base station antenna corresponding to a cell (or several cell sectors) of the base station. When the term "network entity" or "base station" refers to multiple co-located physical TRPs, these physical TRPs may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When 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 via a transmission medium to a common source) or a remote radio headend (RRH) (e.g., a remote base station connected to a serving base station). Alternatively, a non-co-located physical TRP can be the serving base station from which the UE receives measurement reports and the neighboring base station where the UE is measuring its reference radio frequency (RF) signal (e.g., or simply "reference signal"). Because, as used herein, a TRP is the point by which a base station transmits and receives radio signals, references to transmitting from or receiving at a base station should be understood to refer to the specific TRP of that base station.

[0046] In some specific implementations supporting UE positioning, network entities or base stations may not support the UE's radio access (e.g., may not support data, voice, and / or signaling connections regarding the UE), but instead may transmit reference signals to the UE for measurement, and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

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

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

[0049] RF signals comprise electromagnetic waves of a given frequency that transmit information across the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a “multipath” RF signal. As used herein, where the context clearly indicates that the term “signal” refers to a wireless signal or RF signal, an RF signal may also be referred to as a “wireless signal” or simply a “signal.”

[0050] Various aspects of the systems and technologies described herein will be discussed below with reference to the accompanying drawings. According to these aspects, Figure 1 An example of a wireless communication system 100 is illustrated. The wireless communication system 100 (e.g., also referred to as a wireless wide area network (WWAN)) may include individual base stations 102 and individual UEs 104. In some aspects, base station 102 may also be referred to as a "network entity" or a "network node". One or more of base stations 102 may be implemented in an aggregated or monolithic base station architecture. Additionally or alternatively, one or more of base stations 102 may be implemented in a decomposed 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. Base station 102 may include macrocell base stations (e.g., high-power cellular base stations) and / or small cell base stations (e.g., low-power cellular base stations). On the one hand, macro cell base stations may include eNB and / or ng-eNB (where wireless communication system 100 corresponds to a Long Term Evolution (LTE) network), or gNB (where wireless communication system 100 corresponds to an NR network), or a combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

[0051] Base station 102 can collectively form a RAN and interface with core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) via backhaul link 122, and interface with one or more location servers 172 (e.g., the one or more location servers may be part of core network 170 or may be outside core network 170) via core network 170. Among other functions, base station 102 can perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC or 5GC) via backhaul link 134 (which may be wired and / or wireless).

[0052] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographical coverage area 110. In one aspect, base station 102 in each coverage area 110 can support one or more cells. A “cell” is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI)) to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). Because a cell is supported by a specific base station, the term “cell” can refer to either or both of the logical communication entity and the base station supporting the logical communication entity, depending on the context. Furthermore, since the TRP is typically the physical transmission point of the cell, the terms “cell” and “TRP” can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area of ​​a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0053] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in handover areas), some areas within geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage areas 110 of one or more macro cell base stations 102. A network that includes both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

[0054] The communication link 120 between base station 102 and UE 104 may include uplink (e.g., also referred to as the reverse link) transmission from UE 104 to base station 102 and / or downlink (e.g., also referred to as the forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. One or more carrier frequencies may be used to provide the communication link 120. Carrier allocation may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink).

[0055] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., one or more of base station 102, UE 104, etc.) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be implemented by combining signals transmitted via antenna elements of an antenna array such that some signals propagating relative to a particular orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0056] Transmitting and / or receiving devices (e.g., one or more such as base station 102 and / or UE 104) may use beam scanning technology as part of beamforming operations. For example, base station 102 (e.g., or other transmitting devices) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 104 (e.g., or other receiving devices). Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 102 (or other transmitting devices) in different directions. For example, base station 102 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission in different beam directions may be used to identify (e.g., by transmitting devices such as base station 102, or by receiving devices such as UE 104) beam directions so that base station 102 may transmit or receive later.

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

[0058] In some examples, transmissions performed by a device (e.g., by base station 102 or UE 104) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or radio frequency beamforming to generate combined beams for transmission (e.g., from base station 102 to UE 104, from transmitting device to receiving device, etc.). UE 104 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a configured number of beams across system bandwidth or one or more subbands. Base station 102 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), etc.), which may or may not be pre-decoded. UE 104 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by base station 102 in one or more directions, UE 104 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam direction for subsequent transmission or reception by UE 104), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0059] A receiving device (e.g., UE 104) may attempt multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 102. For example, the receiving device may attempt multiple receiving directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these may be referred to as “listening” according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when a data signal is received). The single receiving configuration may be aligned on a beam direction determined based on listening according to different receiving configuration directions (e.g., based on listening according to multiple beam directions and determining that the beam direction has the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality).

[0060] The wireless communication system 100 may also include a WLAN AP 150 communicating with a WLAN station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a Free Channel Assessment (CCA) or Listen-After-Talk (LBT) process before communication to determine if the channel is available. In some examples, the wireless communication system 100 may include devices (e.g., UEs, etc.) that communicate with one or more UEs 104, base stations 102, APs 150, etc., using ultra-wideband (UWB) spectrum. The UWB spectrum can range from 3.1 GHz to 10.5 GHz.

[0061] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technologies and use the same 5 GHz unlicensed spectrum as WLAN AP 150. Small cell base station 102' employing LTE and / or 5G in unlicensed spectrum can enhance coverage of the access network and / or increase the capacity of the access network. NR in unlicensed spectrum can be referred to as NR-U. LTE in unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0062] The wireless communication system 100 may also include a millimeter-wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with the UE 182. The mmW base station 180 may be implemented in a converged or monolithic base station architecture, or alternatively, in a decomposed base station architecture (e.g., including one or more of a CU, DU, RU, near-RT RIC, or non-RT RIC). Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW extends down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW and / or near-mmW radio bands has high path loss and relatively short range. mmW base station 180 and UE 182 can utilize beamforming (e.g., transmission and / or reception) on mmW communication link 184 to compensate for extremely high path loss and short range. Furthermore, it should be understood that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0063] In some aspects related to 5G, the spectrum in which wireless network nodes or entities (e.g., base stations 102 / 180, UE 104 / 182) operate is divided into multiple frequency ranges: FR1 (e.g., from 450 MHz to 6,000 MHz), FR2 (e.g., from 24,250 MHz to 52,600 MHz), FR3 (e.g., above 52,600 MHz), and FR4 (e.g., between FR1 and FR2). In multi-carrier systems 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 “SCell.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by UE 104 / 182 and the cell, where UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure in that cell. The primary carrier carries all common control channels as well as UE-specific control channels and can be a carrier on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. The secondary carrier may contain only the necessary signaling information and signals; for example, since the primary uplink and primary downlink carriers are typically UE-specific, those UE-specific signaling information and signals may not be present on the secondary carrier. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a “serving cell” (e.g., whether it is a PCell or a SCell) corresponds to the carrier frequency and / or component carrier that some base stations are using to communicate, the terms “cell”, “serving cell”, “component carrier”, “carrier frequency”, etc. can be used interchangeably.

[0064] For example, still refer to Figure 1One of the frequencies used by macro cell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macro cell base station 102 and / or mmW base station 180 may be secondary carriers ("SCell"). In carrier aggregation, each carrier of base station 102 and / or UE 104 may use up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz) of spectrum, with up to a total of Yx MHz (e.g., x component carriers) for transmission in each direction. Component carriers may or may not be adjacent to each other in the spectrum. Carrier allocation may be asymmetrical with respect to downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink). Simultaneous transmission and / or reception on multiple carriers allows UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two aggregated 20 MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (e.g., 40 MHz) compared to the data rate obtained by a single 20 MHz carrier.

[0065] To operate on multiple carrier frequencies, base station 102 and / or UE 104 may be equipped with multiple receivers and / or transmitters. For example, UE 104 may have two receivers, namely "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', while "Receiver 2" is a single-band receiver that can be tuned to only band 'Z'. In this example, if UE 104 is being served in band 'X', then band 'X' will be referred to as PCell or active carrier frequency, and "Receiver 1" will need to tune from band 'X' to band 'Y' (e.g., SCell) to measure band 'Y' (and vice versa). In contrast, regardless of whether UE 104 is being served in band 'X' or band 'Y', because "Receiver 2" is separate, UE 104 can measure band 'Z' without interrupting service on band 'X' or band 'Y'.

[0066] The wireless communication system 100 may also include a UE 164, which can communicate with the macro cell base station 102 on the communication link 120 and / or with the mmW base station 180 on the mmW communication link 184. For example, the macro cell base station 102 may support PCells 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.

[0067] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (e.g., referred to as "side links"). Figure 1 In the example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this link), and has a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (e.g., UE 190 can indirectly obtain WLAN-based Internet connectivity through this link). In one example, any well-known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct (Wi-Fi-D), Bluetooth) can be used. ® (etc.) to support D2D P2P link 192 and D2D P2P link 194.

[0068] Figure 2 A block diagram illustrating an example architecture 200 for a base station 102 and a UE 104 according to some aspects of this disclosure is provided, which enables the transmission and processing of signals exchanged between the UE and the base station. Example architecture 200 includes components of base station 102 and UE 104, which may be... Figure 1 The illustrated base station 102 includes one base station and the UE 104 includes one UE. The base station 102 may be equipped with T antennas 234a to 234t, and the UE 104 may be equipped with R antennas 252a to 252r, wherein typically T ≥ 1 and R ≥ 1.

[0069] At base station 102, transmitting processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and decoding schemes (MCS) for each UE based on a channel quality indicator (CQI) received from each UE, process (e.g., encode and modulate) the data for each UE based on the selected MCS, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., semi-static resource allocation information (SRPI) and control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Modulators 232a to 232t are shown as combined modulator-demodulators (MOD-DEMODs). In some cases, the modulators and demodulators can be separate components. Each modulator in modulators 232a to 232t can process a corresponding output symbol stream (e.g., for an orthogonal frequency division multiplexing (OFDM) scheme, etc.) to obtain an output sample stream. Each modulator in modulators 232a to 232t can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals can be transmitted from modulators 232a to 232t via T antennas 234a to 234t, respectively. Based on some aspects described in more detail below, position coding can be used to generate synchronization signals to transmit additional information.

[0070] At UE 104, antennas 252a to 252r can receive downlink signals from base station 102 and / or other base stations, and can provide the received signals to one or more demodulators (DEMODs) 254a to 254r respectively. Demodulators 254a to 254r are shown as combined modulator-demodulators (MOD-DEMODs). In some cases, the modulator and demodulator can be separate components. Each demodulator in 254a to 254r can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator in 254a to 254r can further process the input sample (e.g., for OFDM, etc.) to obtain the received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 104 to the data sink 260, and provide the decoded control information and system information to the controller / processor 280. The channel processor can determine the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or Channel Quality Indicator (CQI), etc.

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

[0072] In some respects, one or more components of UE 104 may be included in the housing. These include the controller 240 of base station 102, the controller / processor 280 of UE 104, and / or Figure 2 Any other component may perform one or more techniques associated with the implicit UCI β value determination for NR.

[0073] Memory 242 and memory 282 can store data and program code for base station 102 and UE 104, respectively. Scheduler 246 can schedule UE for data transmission on downlink, uplink and / or sidelink.

[0074] In some respects, the deployment of communication systems (such as 5G New Radio (NR) systems) can involve a variety of components or constituent parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functionality can be implemented in aggregated or decomposed architectures. For example, a BS (e.g., such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (e.g., also referred to as a standalone BS or monolithic BS) or a decomposed base station.

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

[0076] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in integrated access backhaul (IAB) networks, open radio access networks (O-RAN (e.g., network configurations such as those initiated by the O-RAN Alliance)), or virtualized radio access networks (e.g., vRAN, also known as cloud radio access networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. The various units in a decomposed base station or decomposed RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0077] Figure 3 This is an illustration of an example decomposed base station 300 architecture. The decomposed base station 300 architecture may include one or more CUs 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more decomposed base station units (e.g., 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). CUs 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links (e.g., F1 interfaces). DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. RUs 340 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 340.

[0078] Figure 3Each of the units illustrated and / or described herein (e.g., CU 310, DU 330, RU340, and near-RT RIC 325, non-RT RIC 315, and SMO frame 305) may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., a radio frequency (RF) transceiver) configured to receive signals or transmit signals to one or more other units, or both, via a wireless transmission media.

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

[0080] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, DU 330 may host one or more of the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending on a functional partition (e.g., such as that defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

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

[0082] SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces (e.g., such as the O1 interface). For virtualized network elements, SMO framework 305 can be configured to interact with a cloud computing platform (e.g., such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (e.g., such as instantiating virtualized network elements) via a cloud computing platform interface (e.g., such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RTRIC 325. In some specific implementations, SMO framework 305 can communicate with the hardware aspects of the 4G RAN (e.g., such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via an O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0083] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, for example, via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, for example, via an E2 interface, through data collection and actions that connect one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0084] 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 an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. 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 in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (e.g., reconfiguration via O1) or via the creation of RAN management policies (e.g., A1 policies).

[0085] Figure 4 An example of a computing system 470 for a wireless device 407 is illustrated. The wireless device 407 may include client devices such as UEs (e.g., UE 104, UE 152, UE 190) or other types of devices usable by an end user (e.g., a station (STA) configured to communicate using a Wi-Fi interface). For example, the wireless device 407 may include mobile phones, routers, tablet computers, laptop computers, tracking devices, wearable devices (e.g., smartwatches, glasses, extended reality (XR) devices such as virtual reality (VR), augmented reality (AR), or mixed reality (MR) devices), Internet of Things (IoT) devices, vehicles, aircraft, and / or another device configured to communicate via a wireless communication network. The computing system 470 includes software and hardware components that may be electrically coupled or communicatively coupled (e.g., or may otherwise communicate, as applicable) via a bus 489. For example, the computing system 470 includes one or more processors 484. One or more processors 484 may include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, special-purpose hardware, any combination thereof, and / or other processing devices or systems. One or more processors 484 may use bus 489 to communicate between cores and / or with one or more memory devices 486.

[0086] 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, antennas 487, one or more input devices 472 (e.g., camera, mouse, keyboard, touchscreen, touchpad, keypad and / or microphone, etc.) and one or more output devices 480 (e.g., display, speaker and / or printer, etc.).

[0087] In some aspects, computing system 470 may include one or more RF interfaces configured to transmit and / or receive radio frequency (RF) signals. In some examples, the RF interface may include components such as modem 476, wireless transceiver 478, and / or antenna 487. One or more wireless transceivers 478 may transmit and receive wireless signals (e.g., signal 488) from one or more other devices via antenna 487, 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 or range extenders, etc.), and / or cloud networks, etc. In some examples, computing system 470 may include multiple antennas or antenna arrays that facilitate simultaneous transmission and reception functionality. Antenna 487 may be an omnidirectional antenna, allowing radio frequency (RF) signals to be received and transmitted in all directions. Wireless signal 488 may be transmitted via a wireless network. The wireless network may be any wireless network, such as cellular or telecommunications networks (e.g., 3G, 4G, 5G, etc.), wireless local area networks (e.g., Wi-Fi networks), Bluetooth, etc. ™ Networks and / or other networks.

[0088] In some examples, wireless signal 488 can be transmitted directly to other wireless devices using sidelink communication (e.g., using a PC5 interface, using a DSRC interface, etc.). Wireless transceiver 478 can be configured to transmit RF signals via antenna 487 for performing sidelink communication according to one or more transmit power parameters that can be associated with one or more regulated modes. Wireless transceiver 478 can also be configured to receive sidelink communication signals with different signal parameters from other wireless devices.

[0089] In some examples, one or more wireless transceivers 478 may include an RF front end, which includes one or more components such as amplifiers, mixers for down-conversion of signals (e.g., also referred to as signal multipliers), frequency synthesizers (e.g., also referred to as oscillators) that supply signals to the mixers, baseband filters, analog-to-digital converters (ADCs), one or more power amplifiers, and other components. The RF front end typically handles the selection of wireless signals 488 and the conversion of wireless signals to baseband frequencies or intermediate frequencies, and can convert RF signals to the digital domain.

[0090] In some cases, computing system 470 may include a decoder-decoder device (or codec) configured to encode and / or decode data transmitted and / or received using one or more wireless transceivers 478. In some cases, computing system 470 may include an encryption-decryption device or component configured (e.g., according to AES and / or DES standards) to encrypt and / or decrypt data transmitted and / or received by one or more wireless transceivers 478.

[0091] One or more SIMs 474 may each securely store an International Mobile Subscriber Identity (IMSI) number and associated key assigned to a user of a wireless device 407. The IMSI and key can be used to identify and authenticate the subscriber when accessing a network provided by a network service provider or operator associated with one or more SIMs 474. One or more modems 476 may modulate one or more signals to encode information to be transmitted using one or more wireless transceivers 478. One or more modems 476 may also demodulate signals received by one or more wireless transceivers 478 to decode the transmitted information. In some examples, 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. One or more modems 476 and one or more wireless transceivers 478 may be used to transmit data from one or more SIMs 474.

[0092] The computing system 470 may also include one or more non-transitory machine-readable storage media or storage devices (e.g., one or more memory devices 486) (and / or communicate with them), which may include, but are not limited to, local and / or network-accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices such as RAM and / or ROM, which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems and / or database structures.

[0093] In various aspects, functionality may be stored in memory device 486 as one or more computer program products (e.g., instructions or code) and executed by one or more processors 484 and / or one or more DSPs 482. Computing system 470 may also include software elements (e.g., residing within one or more memory devices 486) including, for example, operating systems, device drivers, executable libraries, and / or other code, such as one or more applications that may include computer programs implementing the functionality provided by various aspects, and / or may be designed to implement methods and / or configure systems as described herein.

[0094] Figure 5 This is a schematic diagram illustrating 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 base station 102 to UE 104. One or more uplink channels and one or more uplink reference signals may carry information from UE 104 to base station 102.

[0095] In some respects, downlink channels may include one or more of the following: a Physical Downlink Control Channel (PDCCH) carrying downlink control information (DCI), a Physical Downlink Shared Channel (PDSCH) carrying downlink data, and / or a Physical Broadcast Channel (PBCH) carrying system information. In some respects, PDSCH communication may be scheduled by PDCCH communication.

[0096] In some examples, the uplink channel may include one or more of the following: a Physical Uplink Control Channel (PUCCH) carrying uplink control information (UCI), a Physical Uplink Shared Channel (PUSCH) carrying uplink data, and / or a Physical Random Access Channel (PRACH) for initial network access. In some aspects, UE 104 may send acknowledgment (ACK) or negative acknowledgment (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0097] In some cases, the downlink reference signal may include one or more of the following: Synchronization Block (SSB), Channel State Information (CSI) Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS), Positioning Reference Signal (PRS), and / or Phase Tracking Reference Signal (PTRS). In some examples, the uplink reference signal may include one or more of the following: Sounding Reference Signal (SRS), DMRS, and / or PTRS.

[0098] The SSB may carry or include information for initial network acquisition and synchronization. For example, the SSB may carry or include one or more of the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH, and / or PBCH DMRS. The SSB may 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.

[0099] CSI-RS can carry information for downlink channel estimation (e.g., downlink CSI acquisition), which can be used for scheduling, link adaptation, or beam management, etc. For example, base station 102 can configure a CSI-RS set for UE 104, and UE 104 can measure the configured CSI-RS set. Based on the CSI-RS measurement, UE 104 can perform channel estimation and report the channel estimation parameters to base station 102 (e.g., in a CSI report). For example, channel estimation parameters may include one or more of the following: Channel Quality Indicator (CQI), Pre-decoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI), Rank Indicator (RI), and / or Reference Signal Received Power (RSRP), etc.

[0100] In some examples, base station 102 may use CSI reports to select transmission parameters for downlink communication to UE 104. For example, base station 102 may use CSI reports to select transmission parameters including one or more of the following: the number of transmission layers (e.g., rank), the pre-decoding matrix (e.g., pre-decoder), the modulation and decoding scheme (MCS), and / or refined downlink beams (e.g., using beam refinement or beam management procedures), etc.

[0101] The DMRS can carry information used to estimate the radio channel for demodulating the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of the DMRS can be specific to the physical channel it is used to estimate. The DMRS is UE-specific, can be beamformed, can be confined to scheduled resources (e.g., not transmitted over broadband), and can be transmitted only when necessary. As shown, the DMRS is used for both downlink and uplink communication.

[0102] PTRS can carry information for compensating oscillator phase noise. In some cases, oscillator phase noise can increase with increasing oscillator carrier frequency. In some examples, PTRS can be used at high carrier frequencies (e.g., millimeter-wave frequencies) to mitigate oscillator phase noise. PTRS can be used to track the phase of a local oscillator and to achieve suppression of phase noise and common phase error (CPE). Figure 5 As illustrated, in some examples, one or more PTRSs can be used for both downlink communication (e.g., on PDSCH) and uplink communication (e.g., on PUSCH).

[0103] The 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., PRS) transmitted by base station 102 to improve Observed Time Difference of Arrival (OTDOA) positioning performance. In some examples, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped diagonally with frequency and time offsets to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). The PRS may be designed to improve the detectability of UE 104, which may need to detect downlink signals from multiple neighboring base stations to perform OTDOA-based positioning. Therefore, UE 104 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells) and may report Reference Signal Time Difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. In some aspects, base station 102 may calculate the positioning of UE 104 based on the RSTD measurements reported by UE 104.

[0104] In some examples, the SRS may carry information for uplink channel estimation, which can be used for scheduling, link adaptation, pre-decoder selection, and / or beam management, etc. Base station 102 may configure one or more SRS resource sets for UE 104, and UE 104 may transmit SRS on the configured SRS resource sets. The SRS resource sets may have configurable uses, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. Base station 102 may measure the SRS, perform channel estimation based on the measurement, and / or use the SRS measurement to configure communication with UE 104.

[0105] As previously noted, this document provides systems and techniques that can be used to provide optimized multi-carrier configurations for carrier aggregation (CA) associated with network devices, such as UEs. For example, these systems and techniques can be used to implement CA configuration and / or CA reconfiguration for UEs 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).

[0106] Figure 6 This is a diagram illustrating an example timeline 600 associated with CA tuning to implement CA configuration for a UE or network device, based on some examples. In some aspects, Figure 6 Example timeline 600 may also be referred to as CA tuning timeline 600. CA tuning timeline 600 may correspond to carrier aggregation configuration and / or updated carrier configuration (e.g., CA reconfiguration) provided to the UE or other network devices by network entities (e.g., gNB, base station, etc.).

[0107] In some respects, the CA tuning process and / or CA tuning timeline 600 of the figure can be determined by the UE (including...). Figures 1 to 5 The CA tuning process and / or CA tuning timeline 600 may be implemented, executed, and / or associated with any UE. For example, the CA tuning process and / or CA tuning timeline 600 may be implemented, executed, and / or associated with one or more of the UE's modem, the transceiver resource manager (TRM) associated with the UE's RF front-end (RFFE) configuration, etc.

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

[0109] For example, CA tuning timeline 600 may correspond to a UE updating or reconfiguring its carrier aggregation configuration, and may be performed based on factors such as changes in network conditions, handover, or mobility events. For example, during a handover or mobility event where a UE moves between different cells in the network and / or is configured to perform wireless communication using different cells in the network, the PCC associated with the UE's multi-carrier aggregation may be updated and / or one or more SCCs associated with the UE's multi-carrier aggregation may be updated.

[0110] For example, a UE may update or reconfigure its CA configuration to add and activate a new PCC (e.g., and remove and deactivate a previous PCC used for multicarrier aggregation). In some examples, a UE may update or reconfigure its CA configuration to add and activate one or more additional SCCs (e.g., one or more additional SCCs not previously used for multicarrier aggregation at the UE). SCC addition and activation may be performed without correspondingly removing existing SCCs included in the UE's CA configuration (e.g., increasing the total number of SCCs used for CA). In some examples, SCC addition and activation may be performed in conjunction with removing one or more existing SCCs from the UE's CA configuration (e.g., keeping the total number of SCCs used for CA the same or reducing it).

[0111] As previously noted, carrier aggregation can be implemented and / or configured for the UE based on one or more Radio Resource Control (RRC) messages between the UE and network entities (e.g., gNB, base station, etc.). For example, one or more RRC messages may be RRC reconfiguration messages. In some cases, the UE may receive an RRC reconfiguration message indicating an updated CA configuration that corresponds to the addition and / or removal of one or more SCCs.

[0112] In an exemplary example, Figure 6 The CA tuning timeline 600 may be associated with a CA tuning window 602, which represents the time window or time duration during which the UE is expected to complete processing and implement the 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 may be triggered (e.g., by the UE) by receiving an RRC reconfiguration request indicating the updated CA configuration for the UE. The receipt of the RRC reconfiguration request may correspond to the 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, wherein the CA tuning window 602 extends between the start time 652 and the end time 654.

[0113] In some aspects, the CA tuning window 602 may be determined based on the UE's configured processing time limit and / or associated with an RRC reconfiguration request sent to the UE by a network entity. For example, the CA tuning window 602 may be a predetermined (e.g., pre-configured) number of subframes, milliseconds, etc., from the end of DL reception indicating an RRC reconfiguration request for the updated CA configuration of the UE. For example, the length or duration of the CA tuning window 602 may be equal to the configured processing time limit, and the tuning window end time 654 may be offset from the tuning window start time 652 by a certain time offset (e.g., later than the tuning window start time), which is equal to the configured processing time limit.

[0114] In an exemplary example, an RRC reconfiguration request indicating an updated CA configuration is associated with a processing time limit, which is a predefined or pre-configured processing time limit provided by a 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 to receive uplink permission 20ms from the end of receiving the DL RRC message. For example, the CA tuning window 602 and the tuning window end time 654 may be determined based on the configured RRC processing time requirement (e.g., 20ms) for the DL RRC message. In some cases, the configured 20ms processing time limit may include UE functional processing time that is performed only once for all received RRC segments of the DL RRC message (e.g., the configured 20ms processing time limit may be independent of the DL RRC message size).

[0115] Based on the indication and / or signaling of updated CA configuration information using an RRC reconfiguration request (e.g., DL RRC message), the updated CA configuration implemented by the UE can correspond to the network requirement or expectation that the UE completes the processing of CA tuning timeline 600 within the configured CA tuning window 602 (e.g., complete the processing before the tuning window end time 654). Figure 6 As illustrated in the example CA tuning timeline 600, the actual total processing time 604 for implementing the updated CA configuration at the UE can be longer than the configured 20ms CA tuning window 602 (e.g., CA tuning 600 completes after the tuning window end time 654). For example, the actual processing time for implementing the updated CA configuration at the UE could be 32.3ms, exceeding the configured 20ms CA tuning window limit 602 by a window overrun time 606 of 12.3ms.

[0116] Figure 6 The CA tuning timeline 600 includes multiple 1ms subframes 605, which indicate the start and end times of example processing for different phases of CA tuning. The start time 652 of the CA tuning window 602 may be located within subframe 1 of the multiple 1ms subframes 605, and the end time 654 of the CA tuning window 602 may be located between subframes 20 and 21 of the multiple 1ms subframes 605 (e.g., corresponding to a CA tuning window duration of 20ms).

[0117] The RF_CONFIG_COMPLETE box 648 may correspond to the UE completing CA tuning to achieve (e.g., within the UE's RF hardware) the corresponding RF configuration for the updated CA configuration. Figure 6 In the example CA tuning timeline 600, the RF_CONFIG_COMPLETE box 648 occurs within subframe 33, and corresponds to a 12.3ms tuning window overrun time 606 that extends between the tuning window end time 654 and the RF_CONFIG_COMPLETE box 648 and / or the corresponding DCI-0 grant 664.

[0118] In some respects, the network (e.g., a network entity that sends the updated CA configuration corresponding to the tuning window start time 652 to the UE) expects the UE to have completed carrier aggregation processing and configuration implementation before the tuning window end time 654. For example, starting from subframe 21, the network entity expects the UE to be ready to receive downlink and / or uplink permission and to be ready to perform uplink transmissions to the network entity.

[0119] Because the total (e.g., actual) CA tuning processing time 604 exceeds the configured CA tuning window limit 602, a mismatch may occur between the network entity's expected UE readiness state for uplink transmissions to and / or downlink transmissions from the network entity and the actual UE readiness state for uplink transmissions to and / or downlink transmissions from the network entity. In an illustrative example, within the CA tuning window exceeding 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 transmissions to the network entity, etc.

[0120] If the UE has not completed RF tuning to achieve the updated CA configuration before the end time 654 of the configured tuning window 602, UE performance may degrade (e.g., due to network requirements or expectations that the UE has completed processing of the DL RRC message before the end time 654 of the configured 20ms time window 602). In some examples, where RF tuning for CA reconfiguration is associated with a PCC interruption (e.g., Rx / Tx blanking), the UE may additionally miss receiving critical DL / UL grants from network entities (e.g., gNB, base station, etc.) and / or may miss transmissions to network entities (e.g., SCC activation MAC-CE, etc.). For example, a missed DL / UL grant or transmission between the UE and a network entity may correspond to a downlink interruption 642 (e.g., also referred to as Rx blanking 642) and / or an uplink interruption 646 (e.g., also referred to as Tx blanking 646) on the UE's PCC, wherein the downlink interruption 642 or the uplink interruption 646 occurs within the CA tuning window exceeding time 606.

[0121] In some aspects, the tuning performed by the UE to achieve the updated CA configuration may include an OTA handling box 610, an RF configuration check and probe box 620 (e.g., "RF_CHECK_CONFIG REQ / CNF"), an RF hardware register script building box 630 (e.g., "RF_CONFIG REQ / CNF (split script building)"), and an RF script execution box 640 (e.g., "FW_EXEC" corresponding to executing an RF script in the UE's firmware).

[0122] OTA handling frame 610 may correspond to over-the-air (OTA) decoding of L2 and / or RRC messages received by the UE. For example, OTA handling frame 610 may correspond to RRC OTA decoding of an RRC reconfiguration request indicating an updated CA configuration for the UE. Processing associated with OTA handling frame 610 may be provided by the UE using information to determine a new or updated CA configuration for multicarrier aggregation to be implemented at the UE. For example, the UE may determine information associated with RF tuning of an SCC included in the updated CA configuration and / or information associated with RF tuning of a PCC included in the updated CA configuration.

[0123] In some respects, within and / or in parallel with OTA handling box 610 (e.g., prior to RF script construction boxes 620 and 630), the UE may perform an impact analysis to determine specific carriers (e.g., specific CCs) affected by the transition from the UE's current CA configuration to the updated CA configuration indicated by the RRC reconfiguration request. CCs affected by the updated CA configuration may include carriers newly added as SCCs, carriers newly added as PCCs, removed active SCCs or PCCs, etc. CCs affected by the updated CA configuration may also include one or more PCCs and / or SCCs that remain in both the UE's current CA configuration and the updated CA configuration, but these PCCs and / or SCCs are affected by the allocation of RF hardware components to the corresponding RF paths and RF chains used for the additional SCCs indicated in the updated CA configuration.

[0124] Based on the determined impact on existing PCCs and / or existing SCCs, the affected PCCs and / or affected SCCs will be reconfigured or retuned to accommodate the addition of one or more new SCCs, and may be included in the set of CCs determined or identified by the UE as being affected by the updated CA configuration. For example, in the RF device allocation (e.g., TRM device allocation) step, the affected carriers may be analyzed, and the corresponding reconfiguration or retuning may be determined as the corresponding RF device allocation for the RF path and / or RF chain for each affected carrier.

[0125] For example, the CA tuning timeline 600 may include RF device allocation and probe steps, which can be performed in parallel with the OTA processing 610 of the RRC reconfiguration request. For example, RF device allocation and probe may be performed by the UE's Transceiver Resource Manager (TRM) and may also be referred to as TRM device allocation and probe. In some cases, OTA processing 610 is performed between subframes 1 and 6. Figure 6 In the example, RF device allocation can be performed between subframes 4 and 6, and TRM early probing can be performed between subframes 6 and 7.

[0126] RF device allocation may include assigning the appropriate RF hardware components of the UE (e.g., appropriate RF chains) to each of the affected CCs identified as being affected by the updated CA configuration. For example, the UE's TRM may be configured to perform RF device allocation and probing to determine the appropriate RF paths for the new SCC Rx / Tx chains and / or PCC Rx / Tx chains. As used herein, Rx / Tx chains may also be referred to as RF chains, and vice versa. An RF chain may correspond to a sequence of hardware components used to process RF signals between the UE's antenna and digital baseband system. In some aspects, the UE may include a modem and / or multiple RF front-ends (RFFEs) that may be configured to support (e.g., implemented at the UE) multiple different combinations of RF bands. In some cases, the UE may include multiple different antennas and multiple different RF chain components (e.g., analog-to-digital converters (ADCs), low-noise amplifiers (LNAs), phase-locked loops (PLLs), wideband (WB) paths, narrowband (NB) paths, etc.). The RF chain can be implemented by the UE as a sequence of specific hardware components, each selected from multiple (or shared) instances of each hardware component in the RF chain. For example, for a given CA band combination (e.g., inter-band or intra-band with multiple SCCs), the UE may have multiple options for RF tuning.

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

[0128] After completing OTA handling 610 and TRM RF device allocation frames (e.g., before the end of subframe 7 and the start of subframe 8), CA tuning timeline 600 may proceed to RF script construction frames 620 and 630. For example, in some aspects, RF configuration check frame 620 and RF hardware register script construction frame 630 may correspond to RF script construction performed by the UE (e.g., determining RF hardware register configuration) (e.g., frames 620 and 630 may be included in the UE's RF split script construction process).

[0129] RF script construction can be performed based on RF device allocation information determined by the UE's TRM during OTA processing 610, where the RF device allocation information corresponds to the determination of the corresponding RF path for each SCC and PCC Rx / Tx chain in the updated CA configuration. In an exemplary example, RF script construction boxes 620 and / or 630 can be used to generate or obtain an RF hardware register script that indicates RF hardware register values ​​for implementing SCC or PCC Rx / Tx chains (e.g., SCC or PCC RF chains) in the UE's configurable RFFE, modem, TRM, antenna, and / or other RF hardware.

[0130] For example, an RF script may instruct the UE's RF hardware on a set of settings (e.g., hardware register values) for implementing a specific RF path corresponding to a PCC or SCC RF chain. For instance, an RF script may include a list of hardware register settings for specific RF paths and RF chains that need to be programmed into the UE's RF hardware to implement a PCC or SCC for CA configuration. In some aspects, an RF script may be provided as a mapping between high-level settings indicating carrier configuration parameters (e.g., PCC or SCC, specific channel, bandwidth, power level, timing, and synchronization) and corresponding low-level RF hardware register values ​​used to implement the high-level settings.

[0131] exist Figure 6 In the example CA tuning timeline 600, the RF script construction (e.g., determining the RF hardware register configuration) has not yet been completed before the end time 654 of the CA tuning window 602 (e.g., between subframes 20 and 21, i.e., 20 ms after the start time 652 of the tuning window). For example, the RF script construction box 630 completes after subframe 22, i.e., 2 ms after the end time 654 of the CA tuning window 602.

[0132] After the RF script is built (e.g., after the RF hardware register configuration is determined), the UE performs RF script execution to configure the PCC chain and / or SCC chain of the updated CA configuration in the UE's RF hardware. In many examples, RF script execution may include the UE inducing an interruption (e.g., Rx / Tx blanking) on ​​the PCC and / or on one or more existing SCCs (e.g., SCCs not newly added in the updated CA configuration) within one or more subframes. During the interruption of a particular carrier (e.g., PCC or SCC), the UE is configured not to receive or transmit on that particular carrier. For example, after the RF script building corresponding to boxes 620 and 630 is completed, the CA tuning timeline 600 includes a subsequent RF script execution box 640, in which the RF script built (e.g., generated) during boxes 620 and / or 630 is 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-end (RFFE), etc. For example, RF script construction boxes 620 and 630 can be used to determine the corresponding RF hardware register values ​​for each SCC and PCC Rx / Tx chain to be implemented for the updated CA configuration. RF script execution box 640 can be used to update or otherwise write the values ​​determined by the RF script into the UE's physical RF hardware registers.

[0133] In some aspects, RF script execution box 640 may include downlink interruption (e.g., Rx blanking) 642 of PCC for one or more subframes within one or more subframes, and / or may include uplink interruption (e.g., Tx blanking) 646 of PCC for one or more subframes within one or more subframes. For example, downlink interruption 642 occurs in subframes 29 and 30, and the UE does not perform downlink reception on any interrupted carrier during subframes 29 and 30. Uplink interruption 646 occurs in subframes 29 and 30 and may correspond to enabling discontinuous transmission (DTX), such that the UE does not perform uplink transmission on any interrupted carrier during subframes 29 and 30. Downlink interruption 642 and / or uplink interruption 646 may be performed for one or more carriers (e.g., CC) configured for carrier aggregation. For example, downlink interruption 642 and / or uplink interruption 646 can be executed against the PCC of the updated CA configuration, against one or more SCCs of the updated CA configuration, or against a combination of one or more of the PCC and one or more SCCs of the updated CA configuration.

[0134] Downlink interruption 642 and uplink interruption 646 may be performed (e.g., applied to) the PCC and one or more SCCs of the updated CA configuration implemented during CA tuning timeline 600. Rx and / or uplink interruptions may be performed during tuning steps for adding carriers (PCC or SCC) to the UE's carrier aggregation configuration, and / or during tuning steps for updating or reconfiguring CCs previously used by the UE for carrier aggregation. For example, the UE may be configured to cause uplink and downlink interruptions on the PCC and SCC to complete the configuration of a new RF device added by the updated CA configuration.

[0135] As previously noted, Figure 6 Example CA tuning timeline 600 corresponds to a total processing time 604 exceeding the CA tuning window limit 602 to window overtime 606. For example, the end-to-end RRC reconfiguration CA tuning of timeline 600 is completed within 32.3ms, which far exceeds the 20ms DL RRC processing time limit for CA tuning and reconfiguration at the UE. For example, RF script construction box 630 is not completed before the end time 654 of CA tuning window 602 (e.g., between subframes 20 and 21, i.e., 20ms after the tuning window start time 652) and is not completed until after subframe 22 (i.e., 2ms after the end time 654 of CA tuning window 602).

[0136] The longer total CA tuning timeline 604 and the corresponding window overrun time 606, combined with downlink interruption 642 and uplink interruption 646, can be associated with performance degradation at the UE during the implementation of the updated CA configuration and CA tuning process 600.

[0137] For example, based on the fact that residual processing for reconfiguring CA tuning for RRC is still being performed during window timeout 606, the UE may miss critical DL / UL grants from network entities sent by these entities during downlink interruption 642 in subframes 29-30. The UE may also miss scheduled or anticipated uplink transmissions to network entities during uplink interruption 646 in subframes 29-30. In an illustrative example, in Figure 6 Within the CA tuning timeline 600, the UE misses receiving SCC Activation MAC-CE 662 from the network entity because SCC Activation MAC-CE 662 is within a 2ms downlink interruption 642 for PCC during RF script execution 640. In some cases, the UE may experience performance issues associated with DL / UL block error rate (BLER) and missed decoding during the window exceedance time 606 and / or within the 2ms downlink interruption 642 or 2ms uplink interruption 646 (e.g., in...). Figure 6 Examples and SCC activation in MAC-CE 662, including delayed or missed SCC activation.

[0138] As previously noted, this document describes systems and techniques that can be used to provide optimized multicarrier aggregation configurations and / or reconfigurations for carrier aggregation implemented by UEs or other network devices.

[0139] In some respects, the UE or network device can be configured to implement the updated CA configuration based on prioritizing the processing of the PCC for the updated CA configuration over the processing of one or more SCCs for the updated CA configuration. For example, Figure 6 The RF tuning of blocks 620 and 630 of the CA tuning timeline 600 can be broken down into multiple steps, where each step is configured to prioritize the PCCRx and Tx chains and their corresponding RF tuning. For example, Figure 6 RF tuning blocks 620 and 630 may correspond to combined RF tuning, in which the PCC and SCC are not tuned in a specific order (e.g., the PCC and SCC may be tuned in combined RF tuning, which is not performed sequentially on a per-CC or carrier basis).

[0140] Figure 7 This is an illustration of an example of multi-carrier aggregation 700, which corresponds to PCC 712, first SCC1 715, and 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 module with either SCC1 715 or SCC2 717. SCC1 715 and SCC2 717 may be configured as consecutive intra-band CAs, wherein there is a shared RF module between the aggregated SCC1 and SCC2, but not with PCC 712.

[0141] For example, PCC 712 may be associated with a PCC RF path (e.g., RF hardware components of the UE and / or RF transceiver 740 for implementing the PCC Rx / TX chain), which includes a dedicated antenna for 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 converter (ADC) 738-1, etc., configured to output a set of PCC narrowband (NB) samples 742 corresponding to PCC 712 from the PCC RF path.

[0142] SCC1 715 and SCC2 717, as consecutive CA SCCs within the same band, can share an RF module with each other. For example, the aggregated SCC RF path may include a dedicated antenna for the SCC, 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 corresponding SCC1 narrowband (NB) samples 745 corresponding to SCC1 715 and SCC2 NB samples 747 corresponding to SCC2 717.

[0143] In an exemplary example, PCC 712 and its corresponding PCC RF chain may be tuned first, and may take precedence over the tuning of SCC1 715 and SCC2 717 on the shared SCC RF chain. For example, based at least in part on the fact that PCC 712 and SCC 715, 717 do not share RF modules or components (e.g., based at least in part on the configuration of separate PCC and SCC RF paths in RF transceiver 740), a UE including RF transceiver 740 may implement optimized CA tuning to tune PCC 712 first without affecting PCC 712, and then tune SCC 715, 717 later (e.g., after PCC 712 tuning is complete).

[0144] Figure 8 This is a diagram illustrating an example CA tuning timeline 800 used to implement an updated CA configuration for a UE or network device. The first CA tuning timeline 802 can be connected to... Figure 6 The CA tuning timeline 600 is the same as or similar to the first CA tuning timeline 800, and the CA tuning for the updated CA configuration is completed after subframe 25 (e.g., 25 ms after the RRF reconfiguration request 852 indicating the updated CA configuration for adding multiple CAs). The completion of CA tuning by the first CA tuning timeline 802 may correspond to the first RRC reconfiguration completion indication 892, which may indicate to the network entity that the UE has completed RRC reconfiguration CA tuning for both PCC and SCC.

[0145] The second CA tuning timeline 850 may be an optimized CA tuning timeline configured to prioritize processing for the PCC over processing for one or more SCCs. For example, the second CA tuning timeline 850 completes CA tuning for the same updated CA configuration after subframe 22 and completes CA tuning for the PCC after subframe 17 (e.g., 17 ms after the RRC reconfiguration request 852 for multiple CA addition). In some aspects, the second (e.g., optimized) CA tuning timeline 850 completes CA tuning for the PCC within the configured processing time limit 854 of the tuning window and sends a corresponding RRC reconfiguration completion indication 890 (e.g., completing CA tuning for the PCC and sending RRC reconfiguration completion 890 after 17 ms, which is within the 20 ms tuning window processing time limit).

[0146] In some respects, the first CA tuning timeline 802 and the second CA tuning timeline 850 may correspond to CA tuning for implementing an updated CA configuration that will change the UE from using only PCC (e.g., Figure 7 The PCC 712) was converted to use a PCC and two additional SCCs (SCC1 and SCC2, for example, Figure 7 (SCC1 715 and SCC2 717). In this example, CA tuning can correspond to changing the UE from implementing 4 Rx and Tx chains (e.g., corresponding to PCC-only configuration) to implementing 12 Rx and Tx chains (e.g., corresponding to PCC+2SCC multi-carrier CA configuration).

[0147] In some respects, the first CA tuning timeline 802 can be compared with... Figure 6 The CA tuning timeline 600 is the same as or similar to it. For example, multiple subframes 805 can be... Figure 6 Multiple 1ms subframes 605 are identical or similar. OTA processing box 810 can be related to... Figure 6 The OTA handling box 610 is the same as or similar to the RF resource allocation and impact calculation box 820. Figure 6 The RF_CHECK_CONFIG REQ / CNF box 620 is the same as or similar. In some examples, Figure 8 Processing blocks 810 and 820 can be identical for the first CA tuning timeline 802 and the second CA tuning timeline 850. The first CA tuning timeline 802 may additionally include an RF hardware register scripting construction block 830, configured for the updated CA configuration's PCC and SCC (e.g., such as...). Figure 7 The RF hardware register scripting box 830 can be used in combination with PCC 712, SCC1 715, and SCC2 717, etc., to perform RF hardware register scripting. In some respects, the RF hardware register scripting box 830 can be used with... Figure 6The RF script construction box 630 is the same as or similar to this. At box 840, the first CA tuning timeline 802 performs retuning of all carriers (e.g., retuning of PCC, SCC1, and SCC2) and completes the CA tuning process using the corresponding first RRC reconfiguration completion indication 892. In some aspects, box 840 of the first CA tuning timeline 802 may be similar to... Figure 6 The RF script execution box 640 of the CA tuning timeline 600 is the same as or similar to that of the CA tuning timeline 600.

[0148] Figure 8 The second CA tuning timeline 850 can be based on optimized CA tuning that prioritizes PCC processing over SCC processing, as described above. For example, after completing RF resource allocation and impact calculation box 820 at subframe 8, the second (e.g., optimized, PCC-prioritized, etc.) CA tuning timeline 850 can execute PCC-only RF hardware register scripting construction box 862 between subframes 9 and 13. At subframe 14, PCC (e.g., Figure 7 The RF script (such as PCC 712) is completed.

[0149] Starting from subframe 14, the second CA tuning timeline 850 enables a PCC-only retuning box 872 to perform PCC-specific RF tuning (e.g., retuning) based on the PCC RF script generated at the PCC RF script building box 862.

[0150] In parallel with PCC retuning 872, a second CA tuning timeline 850 may additionally execute an SCC-only RF hardware register script build 864 to build SCC1 (e.g., Figure 7 The corresponding first SCC RF script of SCC1 715 and SCC2 (e.g., Figure 7 The corresponding second SCC RF script for SCC2 717.

[0151] At subframe 17, the second CA tuning timeline 850 completes PCC retuning 872, and the UE is able to transmit and receive on the PCC with the updated CA configuration starting from subframe 18. Because PCC retuning 872 is completed within (e.g., before) the tuning window limit 854, the UE will not miss DL / UL grants from network entities (e.g., which are on the PCC) and will not miss transmissions destined for network entities (e.g., which may also be on the PCC).

[0152] In one exemplary example, the second CA tuning timeline may include an RRC reconfiguration completion indication 890, which is sent by the UE to the network entity to indicate that PCC retuning 872 has been completed and that the UE is ready and able to perform reception and transmission on the tuned PCC with the updated CA configuration indicated in the RRC reconfiguration request 852 received prior to subframe 1.

[0153] In the second CA tuning timeline 850, the RF script construction 864 for SCC alone can extend processing beyond the time of the RRC reconfiguration completion indication 890. While SCC tuning is in progress or not yet complete, the total bandwidth available to the UE may be relatively low, but the UE is still able to fully communicate with network entities on Rx and Tx using PCC. PCC-based retuning 872 is prioritized to complete within the tuning window limit 854, so that UE performance is unaffected and / or minimally affected when SCC tuning completes and the overall second CA tuning timeline 850 extends beyond the tuning window time limit 854.

[0154] For example, after the SCC-only RF script construction 864 is completed, the second CA tuning timeline 850 performs SCC-only retuning 874 to retune SCC1 using the corresponding SCC1 and SCC2 RF scripts generated at the SCC-only RF script construction box 864 (e.g., Figure 7 SCC1 715) and retuned SCC2 (e.g., Figure 7 (SCC2 717). In some examples, SCC retuning 874 may be completed at or within the 20ms tuning window limit 854. In some cases, SCC retuning 874 may extend beyond the tuning window limit 854, during which time the UE may communicate only on the PCC (e.g., based on PCC retuning 872, the RRC reconfiguration completion time 890 within the tuning window limit 854 is completed). In some aspects, a second CA tuning timeline 850 may perform SCC retuning 874 and RF low-power mode and dynamic activity script construction 868 in parallel, which may extend beyond the completion time of one or more subframes 805 beyond the 20ms tuning window limit 854 without affecting UE communication performance on the PCC.

[0155] In some cases, Figure 8 The optimized second CA tuning timeline 850 can be implemented by splitting the RF script construction and tuning into three steps, which can be performed after the UE TRM / RF completes the RF device allocation box 820 and the RF script can be constructed (e.g., based on RF device allocation information from the TRM).

[0156] The first phase can correspond to the PCC PRx / Tx script construction of RF script construction frame 862 and PCC retuning frame 872. If an interruption of one or more subframes is required during PCC retuning 872 (e.g., Rx / Tx blanking) (e.g., a PCC interruption of one or more subframes at the start of reconfiguration), then PCC retuning 872 and any PCC interruption are performed within the configured tuning window time limit 20ms 854, and UE performance is not affected for communication with network entities.

[0157] The second phase may correspond to the construction and execution of RF scripts for the remaining RF chains of the updated CA configuration (e.g., SCC Rx / Tx script construction box 864 and SCC retuning box 874). In some cases, the second phase may correspond to the construction and execution of scripts for the remaining RF chains of the updated CA configuration (e.g., RF chains other than the PCC PRx / Tx chain processed in the first phase), which may be executed across PCC and SCC.

[0158] The third stage may correspond to the RF script construction for power characteristics (e.g., sleep / wake, LPM, etc.) and may be implemented as the RF low-power mode and dynamic activity script construction box 868 of the second CA tuning timeline 850. The third stage may include RF script construction for power characteristics, and / or one or more dynamic activities or advanced characteristics, such as LPM, APM, MIMO, sleep / wake, etc., that can be executed and processed in parallel with PCC and / or SCC RF tuning.

[0159] In some aspects, the system and technology can be configured to provide optimized multi-carrier aggregation configuration and / or reconfiguration for carrier aggregation implemented by the UE or other network devices, based on minimizing PCC interference during RF device allocation and RF script execution under CA tuning. For example, in some cases, the UE can be configured to minimize PCC interference during RF device allocation and RF script execution associated with implementing the updated CA configuration. In an exemplary example, for blind SCC addition, the UE can implement an RF device allocation algorithm (e.g., with...) Figure 8 (Corresponding to RF resource or device allocation frame 820, etc.), the RF device allocation algorithm is configured to first attempt to determine an RF device allocation, wherein the PCC uplink and downlink are not interrupted (e.g., blanking) for the target allocation within one or more subframes. If the UE cannot perform an allocation to avoid PCC interruption, the UE may then attempt to perform an 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, Figure 7 The PCC 712 is assigned to the RF transceiver 740 and is assigned to Figure 7The SCC1 715 and SCC2 717 use different antennas. In some examples, if the UE cannot perform RF device allocation to assign a non-shared antenna to PCCPRx / Tx, the UE can fall back to performing the old allocation algorithm to assign the RF device. After completing the RF device allocation to minimize interference with the PCC, the UE can use the optimized CA tuning technique described above to continue the CA tuning process, prioritizing the processing of the PCC over the processing of the SCC.

[0160] In another exemplary example, the UE may include an RF card, RF transceiver, RFFE, etc., configured to provide support for a unified Sub-6 band (e.g., the FR1 band of 5G NR) and mmW band (e.g., the FR2 band of 5G NR). For example, the UE's RF card may support a unified Sub-6+mmW RFFE implementation, where the unified Sub-6+mmW path can be configured as a Sub-6 path, mmW path, etc. For example, the UE RF card may be configured to reserve a subset of the total available RF paths for 5G mmW CC, where RF device allocation is performed separately for mmW CC and Sub-6 and / or LTE CC. In some aspects, where the UE RF card supports a unified Sub-6+mmW RF path, each RF path may be configured for mmW CC or Sub-6 / LTE CC. The UE may be configured to reserve a subset of RF paths for mmW CC, as is also the case in examples where the UE supports a unified Sub-6+mmW RF path. In some cases, the reserved subset of the unified Sub-6+mmW path may not be used during the UE's Sub-6+LTE and / or LTE-only calls. In an exemplary example, the system and techniques can be configured such that when the UE supports a unified Sub-6+mmW RF path and it is determined that no mmW CC is configured, CA tuning is performed to allocate the PCC Rx / Tx chain to an unused reserved path during device allocation. After device allocation is completed (the PCC Rx / Tx chain is allocated to a reserved mmW path), the UE can continue the CA tuning process using the optimized CA tuning techniques described above to prioritize the processing of the PCC over the processing of the SCC.

[0161] In some respects, the UE can be configured to reduce the amount of time associated with executing RF hardware register script construction by determining one or more predicted updated CA configurations based on the UE's prior determination of one or more predicted updated CA configurations from an RRC reconfiguration instructing the UE for the updated CA configuration. For example, the UE can use measurement information associated with one or more neighboring cells to determine the predicted updated CA configuration. The measurement information can be previously obtained measurement information acquired by the UE in response to measurements requested and / or configured by a network entity.

[0162] A UE can typically receive network requests (e.g., requests from network entities) to perform one or more measurements on the UE's neighboring cells. For example, a UE can be configured by a network entity (e.g., gNB, base station, etc.) to obtain one or more measurements on one or more neighboring cells and report the measurement information in measurement reports, CSI reports, etc., sent from the UE to the network entity.

[0163] In some examples, a network entity may receive a UE measurement report corresponding to measurements of one or more neighboring cells of the UE, and the network entity may subsequently add the best cell from the measurement report as a SCC for carrier aggregation at the UE. For example, the network entity may request a measurement report from the UE when a handover or mobility event is anticipated. The UE may obtain configured measurements of one or more neighboring cells associated with the UE and may send measurement reports to the network entity. The network entity may analyze the measurement report to identify or determine one or more neighboring cells not currently included in the CA configuration for the UE, for addition to the updated CA configuration for the UE. The network entity may send an RRC reconfiguration request to the UE indicating the updated CA configuration, which includes the neighboring cell from the best measurement in the measurement report as a new SCC and / or a new PCC for carrier aggregation for the UE.

[0164] In an exemplary example, for measurements configured by a network entity, the UE may be configured to pre-build RF scripts for a set of activities of neighboring cells (e.g., where the set of activities of neighboring cells includes neighboring cells configured for carrier aggregation performed by the UE). The pre-built RF scripts may be stored locally at the UE, for example, in memory or storage elements included in the UE.

[0165] The predicted updated CA configuration determined by the UE may include one or more of the predicted PCC or predicted SCC for carrier aggregation implemented at the UE. The predicted PCC or predicted SCC may be based on corresponding measurements of neighboring cells. For example, the predicted PCC or predicted SCC may correspond to the best or strongest cell among multiple neighboring cells previously measured by the UE (e.g., the best or strongest cell indicated in the UE measurement report to the network entity based on the UE's prediction will later be configured as a new PCC or SCC for the updated CA configuration used by the UE). In some aspects, the UE may be configured to pre-build a corresponding RF hardware register script for each predicted PCC and / or predicted SCC included in the corresponding predicted updated CA configuration determined by the UE. In some cases, a pre-built RF script for the predicted PCC or predicted SCC may be obtained as RF hardware register values ​​used by the UE to obtain or perform measurements of neighboring cells corresponding to the predicted PCC or predicted SCC. For example, the UE can save or store the RF hardware register configuration of neighboring cells as a pre-built RF script for the predicted PCC or predicted SCC corresponding to the neighboring cells, instead of clearing the RF hardware register configuration after the measurement is completed. Based on receiving an RRC reconfiguration request indicating the updated CA configuration for the UE, the UE can compare the updated PCC and / or one or more updated SCCs of the updated CA configuration with the corresponding predicted PCC and SCC of the pre-built RF script generated and stored by the UE. In some cases, the UE can determine whether any SCC indicated in the updated CA configuration for the UE is a previously measured neighbor for which the pre-built RF script is available. Based on the determination that an added SCC in the updated CA configuration is a previously measured neighbor, the UE can obtain the corresponding pre-built RF script for that neighbor and execute the pre-built RF script without performing RF device allocation, probing, or RF script construction for the added SCC in the updated CA configuration.

[0166] Based on receiving an RRC reconfiguration request from a network entity indicating an updated CA configuration, the UE can examine the updated CA configuration to determine whether any SCCs indicated by the updated CA configuration are previously measured neighboring cells. For example, the UE can determine whether each of one or more SCCs included in the updated CA configuration is a carrier corresponding to a previously measured neighboring cell.

[0167] In response to determining that the updated CA configuration includes an SCC corresponding to a previously measured neighboring cell, the UE can retrieve the corresponding pre-built RF script for the previously measured neighboring cell from memory and can use (e.g., execute) the pre-built RF script to configure the SCC Rx / Tx chain for a specific SCC. In an exemplary example, the UE can reduce the total processing time for CA tuning to achieve the updated CA configuration by utilizing the pre-built RF script to implement the SCC Rx / Tx path for any SCC corresponding to a previously measured neighboring cell. After identifying one or more pre-built RF scripts that match the corresponding SCC included in the updated CA configuration, the UE can run the RF device allocation algorithm again to allocate the non-matching SCCs and / or PCCs of the updated CA configuration. The corresponding SCCs for which neighboring cells were previously measured and for which pre-built RF scripts were generated and stored do not require RF device allocation but can be used for CA tuning using the corresponding pre-built RF script.

[0168] In some aspects, the UE can be configured to reduce the amount of time associated with executing RF hardware register script construction by determining one or more predicted updated CA configurations based on the UE's prior determination of one or more predicted updated CA configurations from the network entity before receiving an RRC reconfiguration indicating an updated CA configuration for the UE. For example, as noted above, the UE can use measurement information associated with one or more of the UE's neighboring cells to determine the predicted updated CA configuration. In some aspects, the predicted updated CA configuration includes a predicted updated set of neighboring cell activities that the UE predicts will be configured by the network entity in response to the network entity receiving UE measurement reports of the UE's neighboring cells. For example, the UE can measure three neighboring cells and can determine the predicted updated CA configuration as the updated set of neighboring cell activities, which includes the best (e.g., strongest) neighboring cell among the three neighboring cells reported to the network entity in the UE measurement report. If the network entity subsequently updates the UE CA configuration to add the best neighboring cell among the three neighboring cells as an additional SCC for CA, the UE can use a pre-built RF script of the predicted updated CA configuration to perform CA tuning in a reduced amount of time.

[0169] In another exemplary example, the UE may generate and / or determine one or more predicted updated CA configurations and / or multiple predicted updated CA configurations based on measurements of the UE's neighboring cells. For example, the UE may generate multiple predicted updated CA configurations to correspond to multiple potential CA configurations using different combinations of the measured neighboring cells.

[0170] For example, a UE may currently be associated with a serving cell in band A, and a set of neighboring cells, including at least neighboring cells in bands B and C, may be measured. 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-1), and so on.

[0171] In situations where a UE may have multiple CA configurations based on different choices of the neighboring cell set measured by the UE, the optimal path selection for RF device allocation and / or RF script construction during CA tuning can be different for each of the multiple possible CA configurations. In some cases, the total number of Rx / Tx chains in the CA configuration may additionally affect the optimal path selection during RF device allocation and / or RF script construction.

[0172] In one exemplary example, the UE can be configured to perform prediction to determine a potential set of possible carriers that can be configured by the network for the UE's multi-carrier CA configuration.

[0173] In some respects, the UE can be configured to maintain a predicted set of PCell+SCell CA configurations (e.g., a set of predicted updated CA configurations), where each configuration corresponds to a different combination of PCell and SCell selected from carriers and cells measured by the UE. The predicted set of PCell+SCell configurations can also be referred to as predicted_CA_set. The UE can be configured to maintain predicted_CA_set at any given time, for example, by updating predicted_CA_set based on measurements and / or measurement reports determined at the UE.

[0174] In an exemplary example, a UE may 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 measurement of one or more neighboring cells includes a configured type of measurement event. For example, if the UE reports a measurement report with a first type of configured measurement event, the UE may add the neighboring cell corresponding to the occurrence of the measurement event to the predicted_CA_set. If the UE reports a measurement report with a second type of configured measurement event, the UE may remove the neighboring cell corresponding to the occurrence of the second type of measurement event from the predicted_CA_set.

[0175] In some respects, a measurement event can be an RRM measurement event or other measurement event defined by network configuration and / or by cellular communication standards or specifications. In some cases, a measurement event can be a configured measurement event associated with one or more of a measurement type and / or one or more thresholds. In some respects, a measurement event can be a measurement event associated with carrier aggregation and / or a measurement event associated with NR-triggered mobility.

[0176] Measurement events can be predefined and / or configured events associated with a wireless network, network entity, and / or its network equipment. For example, 5G NR utilizes measurement events A1-A6 corresponding to NR-triggered mobility (e.g., NR-to-NR), which can be used to trigger UEs to add or remove NR PSCells, add or remove NR SCells, etc. Measurement event A1 occurs when the serving cell becomes better than an absolute threshold. Measurement event A2 occurs when the serving cell becomes worse than an absolute threshold. Measurement event A3 occurs when a neighboring cell becomes better than a PCell / PSCell by a certain offset. Measurement event A4 occurs when a neighboring cell becomes better than an absolute threshold. Measurement event A5 occurs when a PCell / PSCell becomes worse than absolute threshold 1 and a neighboring cell becomes better than absolute threshold 2. Measurement event A6 occurs when a neighboring cell becomes better than a SCell by a certain offset. The measurement event set B1-B2 can correspond to inter-RAT mobility (e.g., NR-to-LTE). Measurement event B1 can occur when a neighboring cell becomes better than an absolute threshold. A B2 measurement event can occur when PCell becomes worse than absolute threshold 1 and a neighboring cell becomes better than another absolute threshold 2.

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

[0178] In an exemplary example, the UE can determine the occurrence of an A1 measurement event (the serving cell becomes better than a threshold), an A3 measurement event (the neighboring cell becomes better than the serving cell by a certain offset), an A4 measurement event (the neighboring cell becomes better than the serving cell), or an A6 measurement event (the neighboring cell becomes better than the SCell by a certain offset) corresponding to a specific neighboring cell measured by the UE. Based on determining the occurrence of the A1, A3, A4, or A6 measurement event corresponding to the measurement of the specific neighboring cell, the UE can update the predicted_CA_set to add the specific neighboring cell to the predicted_CA_set. For example, the UE can add an additional predicted updated CA configuration to the predicted_CA_set, where the specific neighboring cell is either a PCC or an SCC.

[0179] In some aspects, based on the occurrence of an A2 measurement event (e.g., the serving cell becomes inferior to a threshold) or an A5 measurement event (e.g., the serving cell becomes inferior to threshold 1 and the neighboring cell becomes superior to threshold 2) corresponding to a measurement of a specific neighboring cell, the UE may update the predicted_CA_set to remove that specific neighboring cell from the predicted_CA_set. For example, the UE may remove an updated CA configuration from the predicted_CA_set that includes one or more predictions of a specific neighboring cell as a PCC or SCC.

[0180] In some respects, the UE can be configured to perform or trigger a re-evaluation of pre-built RF scripts in response to an update to the predicted_CA_set. For example, whenever the UE updates the predicted_CA_set to add or remove a specific neighboring cell from the predicted_CA_set, the UE can determine whether pre-built RF scripts need to be performed. For example, adding a neighboring cell to the predicted_CA_set may trigger pre-built RF scripts to generate pre-built RF scripts for the added neighboring cell (as an additional SCC and / or an updated PCC in the CA configuration), etc. For example, removing a neighboring cell from the predicted_CA_set may trigger pre-built RF scripts to update one or more stored pre-built RF scripts so that they no longer include the removed neighboring cell as a PCC or SCC, etc.

[0181] In some examples, the UE can be configured to compare predicted_CA_set with the carrier aggregation combinations reported by the UE in the RRC UE Capability Report. The UE can also be configured to adjust predicted_CA_set because network entities cannot add any other aggregation combinations (e.g., CA combinations) other than those reported by the UE in the RRC UE Capability Report.

[0182] In an exemplary example, the UE can then use the updated and adjusted predicted_CA_set to perform RF script pre-construction, such that the UE obtains and stores the corresponding pre-constructed RF script for each aggregation combination represented within predicted_CA_set (e.g., each predicted updated CA configuration). The UE can execute the RF script during the CA tuning process using the pre-constructed RF script stored in predicted_CA_set, based on receiving an RRC connection reconfiguration with corresponding carrier aggregation additions, deletions, modifications, and / or handover cell changes. By performing RF script construction as RF script pre-construction in non-critical paths, the UE can reduce the total processing time of the CA tuning timeline triggered at the UE in response to RRC reconfigurations indicative of updated CA configurations for the UE. For example, when a network entity sends an RRC connection reconfiguration with carrier aggregation additions, deletions, modifications, etc., to the UE, the UE has already generated pre-constructed RF scripts for all possibilities of different aggregation combinations that can be selected by the network entity (e.g., based on the network entity selecting aggregation combinations based on measurement reports sent by the UE). Based on generating and storing pre-built RF scripts for all possible aggregation combinations represented within predicted_CA_set, the UE can guarantee the availability of matching pre-built RF scripts for PCC and SCC of various updated CA configurations that the UE can receive from the network, and can perform CA tuning by directly executing RF scripts to run (e.g., execute) the matching pre-built RF scripts.

[0183] Figure 9This is a flowchart illustrating an example of a process 900 for wireless communication. In some aspects, process 900 may be a process for wireless communication performed by a network device (e.g., a UE, etc.). For example, process 900 may be a process for wireless communication performed by a UE. In some examples, process 900 may be performed by a network device or apparatus or a component or system of a network device or apparatus (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 gate or transistor logic components, discrete hardware components, etc., any combination thereof and / or other components or systems). The operation of process 900 may be implemented in one or more processors (e.g., Figure 10 Software components that execute and run on the processor 1010 or other processor. In some examples, process 900 may be executed by the UE (including...). Figures 1 to 8 The process 900 can be executed by any UE in the UE. In some aspects, the process 900 can be executed by the UE, smartphone, mobile computing device, user computer device, etc. The process 900 can be executed by a network device (e.g., Figure 1 One or more of UEs 104, 152, 164, 182, and 190; Figure 2 UE 104; Figure 3 UE 104; Figure 4 Wireless devices 407; Figure 10 The computing system 1000; etc.) is executed by a component or system (e.g., a chipset). The network device may be a mobile device (e.g., a mobile phone), a network-connected wearable device (such as a watch), an extended reality (XR) device (such as a virtual reality (VR) device or an augmented reality (AR) device), a vehicle or a component or system of a vehicle, or other types of computing devices. The operation of process 900 may be implemented in one or more processors (e.g., Figure 4 processor 484, Figure 10 Software components that execute and run on processor 1010 and / or other processors. Furthermore, they may be transmitted, for example, via one or more antennas (e.g., Figure 2 Antenna 252, Figure 4 Antenna 487, etc.) and / or one or more transceivers (e.g., Figure 4 (e.g., wireless transceiver 478) to enable wireless devices to send and receive signals in process 1000.

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

[0185] At box 904, the network device (or a component thereof) may use measurement information associated with one or more neighboring cells of the network device to determine a predicted updated CA configuration, wherein the predicted updated CA configuration includes one or more of a predicted PCC or a predicted SCC corresponding to a corresponding measurement of a specific neighboring cell among the one or more neighboring cells. For example, the measurement information may be based on... Figure 5 The measurement of one or more downlink reference signals between base station 102 and UE 104 is associated with the measurement of downlink reference signals, etc.

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

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

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

[0189] At box 906, a network device (or a component thereof) may determine multiple hardware register values ​​for configuring the RF hardware registers of the radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the multiple hardware register values ​​are based on corresponding measurements of a particular neighboring cell.

[0190] For example, RF hardware register configuration can be an RF script build of an RF chain that implements the corresponding CA configuration for PCC and / or one or more SCCs. In some examples, RF hardware register configuration can be... Figure 6 RF hardware register configuration script build 630, Figure 8 RF hardware register configuration script to build 830, Figure 8 PCC RF hardware register configuration script to build 862 and / or Figure 8 The SCC RF hardware register configuration script is associated with the 864 and other related technologies.

[0191] In some cases, a network entity (e.g., a UE) may be configured to determine multiple predicted updated CA configurations, including the predicted updated CA configuration. The UE may be configured to determine the RF hardware register configuration of a cache corresponding to each of the multiple predicted updated CA configurations. In some cases, the multiple predicted updated CA configurations correspond to a subset of one or more neighboring cells, and each neighboring cell in the subset is associated with the occurrence of a corresponding measurement event.

[0192] In some examples, the occurrence of the corresponding measurement event includes the occurrence of a configured Radio Resource Management (RRM) measurement event. In some examples, multiple predicted updated CA configurations may be included in a predicted CA set associated with a network device (e.g., a UE), and the predicted CA set may correspond to different combinations of PCC and SCC used for carrier aggregation by the network device.

[0193] In some cases, a network entity (e.g., a UE) may be configured to determine the occurrence of configured measurement events for neighboring cells and to update the predicted CA set based on the occurrence of these events to add additional predicted updated CA configurations corresponding to the neighboring cells. For example, the configured measurement events associated with the UE updating the predicted CA set to add additional predicted updated CA configurations may include A1 measurement events, A3 measurement events, A4 measurement events, or A6 measurement events, etc.

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

[0195] At box 908, the network device (or a component thereof) may receive information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs from the first CA configuration, and wherein the updated CA configuration includes at least one of a predicted PCC or a predicted SCC.

[0196] For example, information indicating the updated CA configuration can be included in a Radio Resource Control (RRC) reconfiguration request. In some examples, information indicating the updated CA configuration can be included... Figure 8 The RRC reconfiguration request 852. In some cases, receiving information indicating the updated CA configuration may be related to... Figure 6 OTA handling 610 and / or Figure 8 The OTA handling is related to 810.

[0197] In some cases, the information indicating the updated CA configuration corresponds to: adding component carriers (CCs) to the first CA configuration, removing CCs from the first CA configuration, or modifying one or more of the first set of SCCs and the first PCC of the first CA configuration. In some examples, the information indicating the updated CA configuration corresponds to a handover of a network device (e.g., a UE) from a first cell to a second cell. The first cell may be associated with the first CA configuration, and the second cell may be associated with the updated CA configuration.

[0198] In some examples, the updated CA configuration includes additional SCCs not included in the first CA configuration or the predicted updated CA configuration. Network entities (e.g., UEs) can be configured to determine RF device allocations that include resource allocations for the additional SCC RF chains corresponding to the additional SCCs, wherein the resource allocation for the additional SCC RF chains does not affect the resource allocation for the current configuration of the PCC RF chains corresponding to the first PCC. For example, this can be based on... Figure 8 RF resource allocation 820 and / or Figure 6 The RF device (e.g., resource) allocation 620 determines the RF device allocation.

[0199] In some cases, network entities (e.g., UEs) can be configured to implement additional SCC RF chains without interruption of uplink or downlink on the PCC RF chain. For example, a UE can be configured to implement additional SCC RF chains without blanking the PCC RF chain. In some examples, uninterrupted uplink or downlink on the PCC can be achieved through parallel execution. Figure 8 The PCC retuning script for the 872 and the SCC RF hardware register configuration script for the 864 were used to build the PCC retuning script.

[0200] In some examples, network entities (e.g., UEs) can be configured to determine the updated PCC RF chain based on resource allocation for the additional SCC RF chain, wherein RF device allocation generates the updated PCC RF chain to include the non-shared antennas of the network devices. For example, resource allocation and / or RF device allocation can be combined with… Figure 6 RF allocation 620 and / or Figure 8 The RF allocation is the same as or similar to that of the 820.

[0201] At box 910, a network device (or a component thereof) may use multiple hardware register values ​​configured by the RF hardware registers to perform CA tuning.

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

[0203] In some examples, CA tuning can be with Figure 6 The CA tuner 640 is the same as or similar to it. In some examples, the CA tuner can be... Figure 8 The combination of PCC and SCC tuning 840 is the same as or similar. In an exemplary example, CA tuning can be with Figure 8 PCC tuning (e.g., retuning) 872 and / or Figure 8 The SCC tuning (e.g., retuning) 874 is the same as or similar. In some examples, a network entity (e.g., a UE) may be configured to perform CA tuning using multiple hardware register values ​​to achieve an updated CA configuration for a network device, wherein the network device does not cause uplink or downlink interruption on the PCC for the updated CA configuration.

[0204] In some cases, a network entity (e.g., a UE) may be configured to determine that an updated CA configuration corresponds to a PCC RF chain that is 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., the UE) may implement the PCC RF chain based on the PCC RF hardware register configuration, wherein RF tuning is performed on one or more SCCs of the updated CA configuration (e.g., ...). Figure 8 Prior to the SCC retuning 874, the PCC RF chain was implemented (e.g., Figure 8 PCC retuning 872).

[0205] In some examples, to implement a PCC RF chain, a network entity (e.g., a UE) can be configured to perform RF tuning for the PCC RF chain based on a PCC RF hardware register configuration. The UE can generate a corresponding SCC RF hardware register configuration corresponding to each of one or more SCCs in the updated CA configuration, where the UE performs RF tuning for the PCC RF chain in parallel (e.g., ...). Figure 8 The PCC is retuned (872) and the corresponding SCC RF hardware register configuration is generated (e.g., only for...). Figure 8 RF hardware register scripts for SCC1 and SCC2 (864).

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

[0207] In some cases, the updated CA configuration corresponds to an updated PCC RF chain, which is different from the first PCC RF chain corresponding to the first PCC. In some examples, the RF front-end of a network device (e.g., a UE) includes multiple combined RF paths, each of which can be configured as either a frequency range 1 (FR1) RF path or a frequency range 2 (FR2) RF path. For example, the RF front-end may be associated with… Figure 7 RF transceiver 740, Figure 7 This is associated with antennas, etc. In some examples, a network entity (e.g., a UE) may be configured to perform RF device allocation based on determining that the updated CA configuration does not include one or more FR2 component carriers (CCs), to allocate the updated PCC RF chain using a subset of multiple combined RF paths reserved as FR2 RF paths. In some cases, a network entity (e.g., a UE) may be configured to perform CA tuning based on the allocation of the updated PCC RF chain on reserved FR2 RF paths to achieve the updated CA configuration without interrupting the uplink or downlink of the updated PCC RF chain.

[0208] In some examples, the processes described herein (e.g., process 900 and / or other processes described herein) may be executed by a computing device or apparatus (e.g., a network node, such as a UE, a base station, a part of a base station, etc.). For example, as noted above, process 900 may be executed by a UE. In another example, it may be executed by a computing device or apparatus (e.g., a network node, such as a UE, a base station, a part of a base station, etc.). Figure 10 The computing device of the computing system 1000 shown executes process 900. For example, having Figure 10 The wireless communication device of the computing architecture shown may include components of a UE and / or network entities (e.g., base stations, gNBs, etc.) and can implement Figure 9 The operation.

[0209] In some cases, a 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 components configured to perform the steps of the processes described herein. In some examples, a computing device may include a display, one or more network interfaces configured to transmit and / or receive data, any combination thereof, and / or other components. One or more network interfaces may be configured to transmit and / or receive wired and / or wireless data, including data according to 3G, 4G, 5G, and / or other cellular standards, data according to the WiFi (802.11x) standard, and data according to Bluetooth. ™ Standard data, data according to the Internet Protocol (IP) standard, and / or other types of data.

[0210] Components of a computing device may be implemented in circuitry. For example, components may include electronic circuitry or other electronic hardware, and / or may be implemented using electronic circuitry or other electronic hardware, which may include one or more programmable electronic circuits (e.g., a microprocessor, graphics processing unit (GPU), digital signal processor (DSP), central processing unit (CPU), and / or other suitable electronic circuitry), and / or may include computer software, firmware, or any combination thereof for performing the various operations described herein, and / or may be implemented using computer software, firmware, or any combination thereof for performing the various operations described herein.

[0211] Process 900 is illustrated as a logic flowchart, the operations of which represent a sequence of operations that can be implemented in hardware, computer instructions, or combinations thereof. In the context of computer instructions, each operation represents a computer-executable instruction stored on one or more computer-readable storage media that, when executed by one or more processors, performs the described operation. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc., that perform a specific function or implement a specific data type. The order in which the operations are described is not intended to be construed as limiting, and any number of described operations can be combined in any order and / or in parallel to implement the process.

[0212] Additionally, process 900 and / or other processes described herein may be executed 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) that executes jointly on one or more processors, implemented in hardware, or implemented in a combination 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 multiple instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non-transitory.

[0213] Figure 10 These are illustrations of examples of systems used to implement certain aspects of this technology. In particular, Figure 10 An example of a computing system 1000 is illustrated. This computing system can be any computing device, such as constituting an internal computing system, a remote computing system, a camera, or any component thereof, wherein the components of the system communicate with each other using connection 1005. Connection 1005 can be a physical connection using a bus, or a direct connection to processor 1010, such as in a chipset architecture. Connection 1005 can also be a virtual connection, a networking connection, or a logical connection.

[0214] In some aspects, the computing system 1000 is a distributed system in which the functions described herein can be distributed across a data center, multiple data centers, a peer-to-peer network, etc. In some aspects, one or more system components described represent a number of such components that each perform some or all of the functions described for that component. In some aspects, components can be physical or virtual devices.

[0215] Example system 1000 includes at least one processing unit (CPU or processor) 1010 and a connection 1005 that communicatively couples various system components, including system memories 1015 such as read-only memory (ROM) 1020 and random access memory (RAM) 1025, to the processor 1010. Computing system 1000 may include a cache 1015 of high-speed memory that is directly connected to, closely proximates, or integrated into the processor 1010.

[0216] Processor 1010 may include any general-purpose processor and hardware or software services, such as services 1032, 1034, and 1036 stored in storage device 1030, which are configured to control processor 1010 and dedicated processors in which software instructions are incorporated into the actual processor design. Processor 1010 may be a substantially completely independent computing system, including multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

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

[0218] The computing system 1000 may include a communication interface 1040, which typically controls and manages user input and system output. The communication interface may perform or facilitate the receiving and / or transmitting of wired or wireless communications using wired and / or wireless transceivers, including utilizing audio jacks / plugs, microphone jacks / plugs, Universal Serial Bus (USB) ports / plugs, Apple... ™ Lightning ™ Ports / plugs, Ethernet ports / plugs, fiber optic ports / plugs, dedicated wired ports / plugs, 3G, 4G, 5G and / or other cellular data network wireless signal transmission, Bluetooth ™ Wireless signal transmission, Bluetooth ™ Low-power (BLE) wireless signal transmission, IBEACON ™Wireless signal transmission, including radio frequency identification (RFID) wireless signal transmission, near field communication (NFC) wireless signal transmission, dedicated short range communication (DSRC) wireless signal transmission, 802.11 Wi-Fi wireless signal transmission, wireless local area network (WLAN) signal transmission, visible light communication (VLC), microwave access global interoperability (WiMAX), infrared (IR) wireless signal transmission, public switched telephone network (PSTN) signal transmission, integrated services digital network (ISDN) signal transmission, ad hoc network signal transmission, radio wave signal transmission, microwave signal transmission, infrared signal transmission, visible light signal transmission, ultraviolet light signal transmission, wireless signal transmission along the electromagnetic spectrum, or some combination thereof. The communication interface 1040 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers used to determine the location of the computing system 1000 based on one or more signals received from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the U.S. Global Positioning System (GPS), Russia's Global Navigation Satellite System (GLONASS), China's BeiDou Navigation Satellite System (BDS), and Europe's Galileo GNSS. There are no limitations on operation on any particular hardware configuration, and therefore the underlying features here can be easily replaced to obtain improved hardware or firmware configurations as they are developed.

[0219] Storage device 1030 may be a non-volatile and / or non-transitory and / or computer-readable storage device, and may be a hard disk or other type of computer-readable medium capable of storing data accessible by a computer, such as magnetic tape, flash memory cards, solid-state storage devices, digital versatile discs, cartridges, floppy disks, hard disks, magnetic tapes, magnetic stripes, any other magnetic storage media, flash memory, memristor memory, any other solid-state storage, CD-ROM, rewritable CD, digital video disc (DVD), Blu-ray disc (BDD), holographic disc, another optical medium, secure digital (SD) card, micro-secure digital (microSD) card, Memory Stick. ®Cards, smart card chips, EMV chips, Subscriber Identity Module (SIM) cards, mini / micro / nano / micro SIM cards, 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, cache memory (e.g., level 1 (L1) 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 cassette and / or combinations thereof.

[0220] Storage device 1030 may include software services, servers, services, etc., which enable the system to perform functions when the code defining such software is executed by processor 1010. In some aspects, hardware services performing specific functions may include software components stored in a computer-readable medium connected to necessary hardware components, such as processor 1010, connection 1005, output device 1035, etc., to perform functions. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions and / or data. Computer-readable media may include non-transitory media in which data can be stored and which does not include carrier waves and / or transient electronic signals propagated wirelessly or via a wired connection. Examples of non-transitory media may include, but are not limited to, magnetic disks or magnetic tapes, optical storage media (such as compact discs (CDs) or digital versatile discs (DVDs)), flash memory, memory, or memory devices. Computer-readable media may store code and / or machine-executable instructions thereon, which may represent procedures, functions, subroutines, programs, routines, subroutines, modules, software packages, classes, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or hardware circuitry 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, etc.

[0221] Specific details have been provided in the foregoing description to offer a thorough understanding of the aspects and examples presented herein, but those skilled in the art will recognize that this application is not limited thereto. Therefore, although illustrative aspects of this application have been described in detail herein, it is to be understood that the various inventive concepts may be embodied and employed in various other ways, and the appended claims are not intended to be construed as including these variations unless limited by prior art. The various features and aspects of the applications described above may be used individually or in combination. Furthermore, without departing from the broader scope of the specification, aspects may be utilized in any number of environments and applications beyond those described herein. Therefore, the specification and drawings should be considered illustrative rather than restrictive. For illustrative purposes, the methods are described in a particular order. It should be understood that, in alternative aspects, the methods may be performed in a different order than described.

[0222] For clarity, in some instances, this technology may be presented as comprising various functional blocks, which include devices, device components, steps, or routines embodied in a method, either in software or a combination of hardware and software. Additional components may be used in addition to 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 to avoid obscuring these aspects in unnecessary detail. In other cases, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the aspects.

[0223] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure.

[0224] Various aspects described above can be presented as processes or methods, depicted as flowcharts, diagrams, data flow graphs, structure diagrams, or block diagrams. Although flowcharts can describe operations as sequential processes, many operations within an operation can be executed in parallel or concurrently. Furthermore, the order of operations can be rearranged. A process terminates when its operations are completed, but a process may have additional steps not included in the accompanying diagrams. Processes can correspond to methods, functions, procedures, subroutines, subroutines, etc. When a process corresponds to a function, the termination of the process can correspond to the function returning to the calling function or the main function.

[0225] The processes and methods described in the examples above can be implemented using stored computer-executable instructions or computer-executable instructions otherwise available from a computer-readable medium. Such instructions may include, for example, instructions and data that configure, or otherwise configure, a general-purpose computer, special-purpose computer, or processing device to perform a function or group of functions. The portion may be accessible via a network of the computer resources used. The computer-executable instructions may be, for example, binary, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that can be used to store the instructions, the information used, and / or information created during the methods according to the described examples include disks or optical discs, flash memory, USB devices with non-volatile memory, networked storage devices, etc.

[0226] In some respects, computer-readable storage devices, media, and memories may include cables or wireless signals containing bit streams, etc. However, when referred to, non-transitory computer-readable storage media explicitly exclude media such as energy, carrier signals, electromagnetic waves, and the signals themselves.

[0227] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and arts. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may, in some cases, be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0228] The various exemplary logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or executed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and can take any form factor of various form factors. When implemented in software, firmware, middleware, or microcode, program code or code segments (e.g., computer program products) for performing necessary tasks can be stored in a computer-readable or machine-readable medium. A processor can perform the necessary tasks. Examples of form factors include: laptop computers, smartphones, mobile phones, tablet devices, or other small form factor personal computers, personal digital assistants, rack-mounted devices, self-contained devices, etc. The functionality described herein can also be embodied in peripheral devices or interlocking cards. By further example, such functionality can also be implemented on circuit boards in different chips or different processes running on a single device.

[0229] Instructions, media for transmitting such instructions, computing resources for executing them, and other structures for supporting such computing resources are example components for providing the functionality described in this disclosure.

[0230] The techniques described herein can also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques can be implemented in any of a variety of devices, such as general-purpose computers, wireless communication devices (mobile phones), or integrated circuit devices with multiple uses, including applications in wireless communication devices (mobile phones) and other devices. Any feature described as a module or component can be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques can be implemented at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, perform one or more of the methods, algorithms, and / or operations described above. The computer-readable data storage medium can form part of a computer program product, which may include packaging material. The computer-readable medium may include 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, etc. Additionally or alternatively, the technology may be implemented at least in part by a computer-readable communication medium that carries or conveys program code in the form of instructions or data structures that can be accessed, read and / or executed by a computer, such as propagated signals or waves.

[0231] The program code can be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Such processors can be configured to perform any of the techniques described in this disclosure. A general-purpose processor may be a microprocessor; however, in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Therefore, as used herein, the term "processor" may refer to any of the foregoing structures, any combination of the foregoing structures, or any other structure or means suitable for implementing the techniques described herein.

[0232] Those skilled in the art will understand that, without departing from the scope of this description, the less than (“<”) and greater than (“>”) symbols or terms used herein may be represented by less than or equal to (“>”) respectively. ") symbol and greater than or equal to (" The symbol ) is used instead.

[0233] When a component is described as being “configured” to perform certain operations, such configuration can be achieved, for example, by designing electronic circuits or other hardware to perform the operations, by programming programmable electronic circuits (e.g., microprocessors or other suitable electronic circuits) to perform the operations, or any combination thereof.

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

[0235] The claim language or other language that states "at least one of" and / or "one or more of" in a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, the claim language that states "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, the claim language that states "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 repetition is information or data (e.g., A and A, B and B, C and C, A and A and B, etc.), or any other ordering, repetition, or combination of A, B, and C. The language "at least one of" and / or "one or more of" in a set does not limit the set to the items listed in the set. For example, the language of a claim stating "at least one of A and B" or "at least one of A or B" may refer to 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.

[0236] Claims using phrases such as "at least one processor, at least one processor is configured to," "at least one processor is configured to," "one or more processors, one or more processors are configured to," or other languages ​​indicate that one or more processors (in any combination) are capable of performing associated operations. For example, a claim using the phrase "at least one processor, the at least one processor is configured to: X, Y, and Z" means that a single processor can be used to perform operations X, Y, and Z; or that multiple processors are each assigned a specific subset of tasks to perform operations X, Y, and Z, such that the multiple processors together perform X, Y, and Z; or that a group of multiple processors work together to perform operations X, Y, and Z. In another example, a claim using the phrase "at least one processor, the at least one processor is configured to: X, Y, and Z" could mean that any single processor can perform only a subset of operations X, Y, and Z.

[0237] When referring to one or more elements that perform functions (e.g., steps of a method), one element may perform all functions, or more than one element may jointly perform these functions. When more than one element jointly performs these functions, each function does not need to be performed by every single element (e.g., different functions may be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements may perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform functions, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions.

[0238] When referring to an entity that performs or is configured to perform functions (e.g., steps of a method) (e.g., any entity or device described herein), the entity may be configured to cause one or more elements (individually or collectively) to perform those functions. 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 of those functions, and / or any combination thereof. When referring to an entity that performs functions, the entity may be configured to cause one component to perform all functions, or to cause more than one component to perform those functions collectively. When the entity is configured to cause more than one component to perform those functions collectively, each function does not need to be performed by every single component (e.g., different functions may be performed by different components), and / or each function does not need to be performed by only one component as a whole (e.g., different components may perform different sub-functions of a function).

[0239] The exemplary aspects of this disclosure include: Aspect 1. A network device for wireless communication, the network device 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 indicating a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first set of secondary component carriers (SCCs) and a first primary component carrier (PCC); 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 a corresponding measurement of a particular neighboring cell among the one or more neighboring cells; determine a plurality of hardware register values ​​for configuring RF hardware registers of a radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values ​​are based on the corresponding measurement of the particular neighboring cell; receive information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs 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 ​​configured by the RF hardware registers.

[0240] Aspect 2. The network device according to Aspect 1, wherein the network device is configured to perform CA 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 uplink or downlink interruption on the PCC for the updated CA configuration.

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

[0242] Aspect 4. The network device according to any one of Aspects 1 to 3, wherein the information indicating the updated CA configuration corresponds to: adding component carriers (CCs) to the first CA configuration, removing CCs from the first CA configuration, or modifying one or more of the first set of SCCs and the first PCC of the first CA configuration.

[0243] Aspect 5. A network device according to any one of Aspects 1 to 4, wherein the information indicating 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.

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

[0245] Aspect 7. The network device according to 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 measurement of the one or more neighboring cells based on the one or more measurement objects.

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

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

[0248] Aspect 10. The network device according to any one 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 an RF hardware register configuration of a cache corresponding to each of the plurality of predicted updated CA configurations.

[0249] Aspect 11. The network device according to aspect 10, wherein the plurality of predicted updated CA configurations correspond to a subset of the one or more neighboring cells, and wherein each neighboring cell in the subset is associated with the occurrence of a corresponding measurement event.

[0250] Aspect 12. The network device according to aspect 11, wherein the occurrence of the corresponding measurement event includes the occurrence of a configured Radio Resource Management (RRM) measurement event.

[0251] Aspect 13. A network device according to any one 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 PCC and SCC for carrier aggregation by the network device.

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

[0253] Aspect 15. The network device according to aspect 14, wherein the configured measurement event includes A1 measurement event, A3 measurement event, A4 measurement event or A6 measurement event.

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

[0255] Aspect 17. The network device according to aspect 16, wherein the occurrence of the corresponding measurement event includes either an A2 measurement event or an A5 measurement event.

[0256] Aspect 18. A network device according to any one of Aspects 1 to 17, wherein the network device is configured to: determine that the updated CA configuration corresponds to a PCC RF chain, the PCC RF chain being 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 prior to RF tuning of one or more SCCs of the updated CA configuration.

[0257] Aspect 19. The network device according to aspect 18, wherein, in order 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 a corresponding SCC RF hardware register configuration corresponding to each of the one or more SCCs in the updated CA configuration, wherein the network device performs the RF tuning for the PCC RF chain and generates the corresponding SCC RF hardware register configuration in parallel.

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

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

[0260] Aspect 22. The network device according to any one of Aspects 1 to 21, wherein: the updated CA configuration includes additional SCCs not included in the first CA configuration or the predicted updated CA configuration; and the network device is configured to determine RF device allocation, the RF device allocation including resource allocation for additional SCC RF chains corresponding to the additional SCCs, wherein the resource allocation for the additional SCC RF chains does not affect the resource allocation for the current configuration of the PCC RF chains corresponding to the first PCCs.

[0261] Aspect 23. The network device according to aspect 22, wherein the network device is configured to implement the additional SCC RF chain in the absence of uplink or downlink interruption on the PCC RF chain.

[0262] Aspect 24. A network device according to any one 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 is allocated to generate the updated PCC RF chain to include the non-shared antenna of the network device.

[0263] Aspect 25. A network device according to any one of Aspects 1 to 24, wherein: the updated CA configuration corresponds to an updated PCC RF chain, the updated PCC RF chain being different from the first PCC RF chain corresponding to the first PCC; the RF front end of the network device includes a plurality of combined RF paths, each combined RF path being 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 based on determining that the updated CA configuration does not include one or more FR2 component carriers (CCs), to allocate the updated PCC RF chain using a subset of the plurality of combined RF paths reserved as FR2 RF paths.

[0264] Aspect 26. The network device according to aspect 25, wherein the network device is configured to perform CA tuning based on the allocation of the updated PCC RF chain on the reserved FR2 RF path to achieve the updated CA configuration without interrupting the uplink or downlink of the updated PCC RF chain.

[0265] Aspect 27. A method for wireless communication by a network device, the method comprising: receiving information indicating a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first set of secondary component carriers (SCCs) and a first primary component carrier (PCC); 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 a corresponding measurement of a specific neighboring cell among the one or more neighboring cells; determining a plurality of hardware register values ​​for configuring RF hardware registers of a radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the plurality of hardware register values ​​are based on the corresponding measurement of the specific neighboring cell; receiving information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs 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 ​​configured in the RF hardware register configuration.

[0266] Aspect 28. The method according to aspect 27, wherein performing CA tuning includes 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 uplink or downlink interruption on the PCC for the updated CA configuration.

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

[0268] Aspect 30. The method according to any one of Aspects 27 to 29, wherein the information indicating the updated CA configuration corresponds to: adding component carriers (CCs) to the first CA configuration, removing CCs from the first CA configuration, or modifying one or more of the first set of SCCs and the first PCC of the first CA configuration.

[0269] Aspect 31. The method according to any one of Aspects 27 to 30, wherein the information indicating 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.

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

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

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

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

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

[0275] Aspect 37. The method according to aspect 36, wherein the multiple predicted updated CA configurations correspond to a subset of the one or more neighboring cells, and wherein each neighboring cell in the subset is associated with the occurrence of a corresponding measurement event.

[0276] Aspect 38. The method according to aspect 37, wherein the occurrence of the corresponding measurement event includes the occurrence of a configured Radio Resource Management (RRM) measurement event.

[0277] Aspect 39. The method according to any one 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 PCC and SCC for carrier aggregation by the network device.

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

[0279] Aspect 41. The method according to aspect 40, wherein the configured measurement event includes A1 measurement event, A3 measurement event, A4 measurement event or A6 measurement event.

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

[0281] Aspect 43. The method according to aspect 42, wherein the occurrence of the corresponding measurement event includes either measurement event A2 or measurement event A5.

[0282] Aspect 44. The method according to any one of Aspects 27 to 43, the method further comprising: determining that the updated CA configuration corresponds to a PCC RF chain, the PCC RF chain being 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 prior to RF tuning of one or more SCCs of the updated CA configuration.

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

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

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

[0286] Aspect 48. The method according to any one of Aspects 27 to 47, wherein the updated CA configuration includes additional SCCs not included in the first CA configuration or the predicted updated CA configuration, and wherein the method further comprises: determining an RF device allocation, the RF device allocation including 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 affect the resource allocation for the current configuration of the PCC RF chain corresponding to the first PCC.

[0287] Aspect 49. The method according to aspect 48, further comprising: implementing the additional SCC RF chain without interruption of the uplink or downlink on the PCC RF chain.

[0288] Aspect 50. The method according to any one of Aspects 48 to 49, the method 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 the non-shared antenna of the network device.

[0289] Aspect 51. The method according to any one of Aspects 27 to 50, wherein: the updated CA configuration corresponds to an updated PCC RF chain, the updated PCC RF chain being different from the first PCC RF chain corresponding to the first PCC; the RF front end of the network device includes a plurality of combined RF paths, each combined RF path being 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 based on determining that the updated CA configuration does not include one or more FR2 component carriers (CCs), to allocate the updated PCC RF chain using a subset of the plurality of combined RF paths reserved as FR2 RF paths.

[0290] Aspect 52. The method according to aspect 51, the method further comprising: performing CA tuning based on the allocation of the updated PCC RF chain on the reserved FR2 RF path to achieve the updated CA configuration without interrupting the uplink or downlink of the updated PCC RF chain.

[0291] Aspect 53. A non-transitory computer-readable storage medium comprising instructions stored thereon, the instructions causing the at least one processor, when executed by at least one processor, to perform any one of aspects 1 to 26.

[0292] Aspect 54. A non-transitory computer-readable storage medium comprising instructions stored thereon, the instructions causing the at least one processor, when executed by at least one processor, to perform any one of aspects 27 to 52.

[0293] Aspect 55. An apparatus for wireless communication, the apparatus comprising one or more components for performing operations according to any one of aspects 1 to 26.

[0294] Aspect 56. An apparatus for wireless communication, the apparatus comprising one or more components for performing operations according to any one of aspects 27 to 52.

Claims

1. A network device for wireless communication, the network device comprising: At least one memory; and At least one processor, said at least one processor being coupled to said at least one memory, wherein said network device is configured to: Receive information indicating a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first set of secondary component carriers (SCCs) and a first primary component carrier (PCC). The predicted updated CA configuration is determined 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 a corresponding measurement of a particular neighboring cell among the one or more neighboring cells. Determine multiple hardware register values ​​for configuring the RF hardware registers of the radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the multiple hardware register values ​​are based on the corresponding measurements of the particular neighboring cell; Receive information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC. as well as CA tuning is performed using the plurality of hardware register values ​​configured in the RF hardware registers.

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

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

4. The network device of claim 1, wherein the information indicating the updated CA configuration corresponds to one or more of the following: adding component carriers (CCs) to the first CA configuration, removing CCs from the first CA configuration, or modifying the first set of SCCs and the first PCC 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 The measurements of the one or more neighboring cells are obtained based on the one or more measurement objects.

6. The network device according to claim 1, wherein, To determine the predicted updated CA configuration, the network device is configured as follows: Based on the measurement information, determine the activity set of the neighboring cells included in the one or more neighboring cells; as well as The updated CA configuration for generating the prediction is to include one or more corresponding predicted SCCs corresponding to the activity set of neighboring cells.

7. The network device according to claim 6, wherein the network entity is configured as follows: The updated set of SCCs included in the updated CA configuration is compared with the one or more corresponding predicted SCCs; For each SCC included in the updated set of SCCs and the one or more corresponding predicted SCCs, CA tuning is performed using the RF hardware register configuration of the corresponding cache for each SCC.

8. The network device according to claim 1, wherein the network entity is configured as follows: Determine multiple predicted updated CA configurations, including the predicted updated CA configuration; and Determine the RF hardware register configuration of the cache corresponding to each of the updated CA configurations of the plurality of predictions.

9. The network device of claim 8, wherein the plurality of predicted updated CA configurations correspond to a subset of the one or more neighboring cells, and wherein each neighboring cell in the subset is associated with the occurrence of a corresponding 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 CA set corresponds to different combinations of PCC and SCC for carrier aggregation by the network device.

11. The network device of claim 10, wherein the network device is configured to: Determine the occurrence of configured measurement events for neighboring cells; and The predicted CA set is updated based on the occurrence of the configured measurement events to add an additional predicted updated CA configuration corresponding to the neighboring cells, wherein the configured measurement events include A1 measurement event, A3 measurement event, A4 measurement event, or A6 measurement event.

12. The network device of claim 10, wherein the network device is configured to: Determine the occurrence of configured measurement events for neighboring cells; and The predicted CA set is updated based on the occurrence of the configured measurement event to remove the predicted updated CA configuration corresponding to the neighboring cell, wherein the occurrence of the corresponding measurement event includes either the A2 measurement event or the A5 measurement event.

13. The network device according to claim 1, wherein the network device is configured to: The updated CA configuration is determined to correspond to a PCC RF chain, which is 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; as well as The PCC RF chain is implemented based on the PCC RF hardware register configuration, wherein the PCC RF chain is implemented prior to RF tuning of one or more SCCs in the updated CA configuration.

14. The network device according to claim 13, wherein, To implement the PCC RF chain, the network device is configured as follows: RF tuning for the PCC RF chain is performed based on the PCC RF hardware register configuration. as well as Generate the corresponding SCC RF hardware register configuration for each of the one or more SCCs in the updated CA configuration. The network device performs the RF tuning for the PCC RF chain in parallel and generates the corresponding SCCRF hardware register configuration.

15. The network device of claim 14, wherein the network device is configured to generate a corresponding SCC RF hardware register configuration corresponding to each of the one or more SCCs in the updated CA configuration, and wherein the corresponding 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 corresponding SCC RF chain corresponding to each of the one or more SCCs in the updated CA configuration, and wherein the corresponding SCC RF chain is implemented after the PCC RF chain is implemented.

17. The network device according to claim 1, wherein: The updated CA configuration includes additional SCCs that were not included in the first CA configuration or the predicted updated CA configuration; and The network device is configured to determine RF device allocation, which includes 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 affect the currently configured resource allocation for the 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 in the absence of uplink or downlink interruption on the PCC RF chain.

19. The network device according to claim 1, wherein: The updated CA configuration corresponds to the updated PCC RF chain, and the updated PCC RF chain is different from the first PCC RF chain corresponding to the first PCC. The RF front end of the network device includes multiple combined RF paths, each of which can be configured 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 based on determining that the updated CA configuration does not include one or more FR2 component carriers (CCs), in order to allocate the updated PCC RF chain using a subset of the multiple combined RF paths that are reserved as FR2 RF paths.

20. A method for wireless communication by a network device, the method comprising: Receive information indicating a first carrier aggregation (CA) configuration for the network device, wherein the first CA configuration corresponds to a first set of secondary component carriers (SCCs) and a first primary component carrier (PCC). The predicted updated CA configuration is determined 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 a corresponding measurement of a particular neighboring cell among the one or more neighboring cells. Determine multiple hardware register values ​​for configuring the RF hardware registers of the radio frequency (RF) chain corresponding to the predicted updated CA configuration, wherein the multiple hardware register values ​​are based on the corresponding measurements of the particular neighboring cell; Receive information indicating an updated CA configuration for the network device, wherein the updated CA configuration differs from the first CA configuration, and wherein the updated CA configuration includes at least one of the predicted PCC or the predicted SCC. as well as CA tuning is performed using the plurality of hardware register values ​​configured in the RF hardware registers.

Images